Chapter 19. CUPS Printing Support in Samba 3.0

- The Common UNIX Print System (CUPS) has become very popular. All - major Linux distributions now ship it as their default printing - system. To many it is still a very mystical tool. Mostly, it - "just works" (TM). People tend to regard it as a "black box" - which they don't want to look into, as long as it works. But once - there is a little problem, they are in trouble to find out where to - start debugging it. Refer to the "Classical Printing" chapter also, it - contains a lot of information that is relevant for CUPS. +Chapter 19. CUPS Printing Support

Chapter 19. CUPS Printing Support
Prev	Part III. Advanced Configuration	Next

Chapter 19. CUPS Printing Support

Kurt Pfeifle

Danka Deutschland GmbH

<kpfeifle@danka.de>

Ciprian Vizitiu

drawings

<CVizitiu@gbif.org>

Jelmer R. Vernooij

drawings

The Samba Team

<jelmer@samba.org>

(3 June 2003)

Table of Contents

Introduction

Features and Benefits
Overview

Basic CUPS Support Configuration

Linking smbd with libcups.so
Simple smb.conf Settings for CUPS
More Complex CUPS smb.conf Settings

Advanced Configuration

Central Spooling vs. Peer-to-Peer Printing
Raw Print Serving Vendor Drivers on Windows Clients
Installation of Windows Client Drivers
Explicitly Enable raw Printing for application/octet-stream
Driver Upload Methods

Advanced Intelligent Printing with PostScript Driver Download

GDI on Windows -- PostScript on UNIX
Windows Drivers, GDI and EMF
UNIX Printfile Conversion and GUI Basics
PostScript and Ghostscript
Ghostscript the Software RIP for Non-PostScript Printers
PostScript Printer Description (PPD) Specification
Using Windows-Formatted Vendor PPDs
CUPS Also Uses PPDs for Non-PostScript Printers

The CUPS Filtering Architecture

MIME Types and CUPS Filters
MIME Type Conversion Rules
Filtering Overview
Prefilters
pstops
pstoraster
imagetops and imagetoraster
rasterto [printers specific]
CUPS Backends
The Role of cupsomatic/foomatic
The Complete Picture
mime.convs
Raw Printing
application/octet-stream Printing
PostScript Printer Descriptions (PPDs) for Non-PS Printers
cupsomatic/foomatic-rip Versus native CUPS Printing
Examples for Filtering Chains
Sources of CUPS Drivers/PPDs
Printing with Interface Scripts

Network Printing (Purely Windows)

From Windows Clients to an NT Print Server
Driver Execution on the Client
Driver Execution on the Server

Network Printing (Windows Clients UNIX/Samba Print +Servers)

From Windows Clients to a CUPS/Samba Print Server
Samba Receiving Jobfiles and Passing Them to CUPS

Network PostScript RIP

PPDs for Non-PS Printers on UNIX
PPDs for Non-PS Printers on Windows

Windows Terminal Servers (WTS) as CUPS Clients

Printer Drivers Running in Kernel Mode Cause Many +Problems
Workarounds Impose Heavy Limitations
CUPS: A Magical Stone?
PostScript Drivers with No Major Problems Even in Kernel +Mode

Configuring CUPS for Driver Download

cupsaddsmb: The Unknown Utility
Prepare Your smb.conf for cupsaddsmb
CUPS PostScript Driver for Windows NT/200x/XP
Recognizing Different Driver Files
Acquiring the Adobe Driver Files
ESP Print Pro PostScript Driver for Windows NT/200x/XP
Caveats to be Considered
Windows CUPS PostScript Driver Versus Adobe Driver
Run cupsaddsmb (Quiet Mode)
Run cupsaddsmb with Verbose Output
Understanding cupsaddsmb
How to Recognize If cupsaddsmb Completed Successfully
cupsaddsmb with a Samba PDC
cupsaddsmb Flowchart
Installing the PostScript Driver on a Client
Avoiding Critical PostScript Driver Settings on the Client

Installing PostScript Driver Files Manually Using rpcclient

A Check of the rpcclient man Page
Understanding the rpcclient man Page
Producing an Example by Querying a Windows Box
Requirements for adddriver and setdriver to Succeed
Manual Driver Installation in 15 Steps
Troubleshooting Revisited

The Printing *.tdb Files

Trivial Database Files
Binary Format
Losing *.tdb Files
Using tdbbackup

CUPS Print Drivers from Linuxprinting.org

foomatic-rip and Foomatic Explained
foomatic-rip and Foomatic-PPD Download and Installation

Page Accounting with CUPS

Setting Up Quotas
Correct and Incorrect Accounting
Adobe and CUPS PostScript Drivers for Windows Clients
The page_log File Syntax
Possible Shortcomings
Future Developments

Additional Material

Auto-Deletion or Preservation of CUPS Spool Files

CUPS Configuration Settings Explained
Pre-Conditions
Manual Configuration

Printing from CUPS to Windows Attached Printers

More CUPS-Filtering Chains

Common Errors

Windows 9x/ME Client Can't Install Driver
cupsaddsmb Keeps Asking for Root Password in Never-ending Loop
cupsaddsmb Errors
Client Can't Connect to Samba Printer
New Account Reconnection from Windows 200x/XP Troubles
Avoid Being Connected to the Samba Server as the Wrong User
Upgrading to CUPS Drivers from Adobe Drivers
Can't Use cupsaddsmb on Samba Server Which Is a PDC
Deleted Windows 200x Printer Driver Is Still Shown
Windows 200x/XP "Local Security Policies"
Administrator Cannot Install Printers for All Local Users
Print Change Notify Functions on NT-clients
WinXP-SP1
Print Options for All Users Can't Be Set on Windows 200x/XP
Most Common Blunders in Driver Settings on Windows Clients
cupsaddsmb Does Not Work with Newly Installed Printer
Permissions on /var/spool/samba/ Get Reset After Each Reboot
Print Queue Called lp Mis-handles Print Jobs
Location of Adobe PostScript Driver Files for cupsaddsmb

Overview of the CUPS Printing Processes

Introduction

Features and Benefits

+ The Common UNIX Print System (CUPS) + has become quite popular. All major Linux distributions now ship it as their default printing + system. To many, it is still a mystical tool. Mostly, it just works. + People tend to regard it as a “black box” + that they do not want to look into as long as it works. But once + there is a little problem, they are in trouble to find out where to + start debugging it. Refer to the chapter “Classical Printing” that + contains a lot of information that is relevant for CUPS.

- CUPS sports quite a few unique and powerful features. While their - basic functions may be grasped quite easily, they are also - new. Because they are different from other, more traditional printing - systems, it is best to try and not apply any prior knowledge about - printing upon this new system. Rather, try to understand CUPS - from the beginning. This documentation will lead you to a - complete understanding of CUPS. Let's start with the most basic - things first. -

Overview

- CUPS is more than just a print spooling system. It is a complete - printer management system that complies with the new IPP - (Internet Printing Protocol). IPP is an industry - and IETF (Internet Engineering Task Force) - standard for network printing. Many of its functions can be managed - remotely (or locally) via a web browser (giving you a - platform-independent access to the CUPS print server). Additionally, it - has the traditional command line and several more modern GUI interfaces - (GUI interfaces developed by 3rd parties, like KDE's - overwhelming KDEPrint). + CUPS sports quite a few unique and powerful features. While their + basic functions may be grasped quite easily, they are also + new. Because they are different from other, more traditional printing + systems, it is best not to try and apply any prior knowledge about + printing to this new system. Rather, try to understand CUPS + from the beginning. This documentation will lead you to a + complete understanding of CUPS. Let's start with the most basic + things first. +

Overview

+ CUPS is more than just a print spooling system. It is a complete + printer management system that complies with the new + Internet Printing Protocol (IPP). IPP is an industry + and Internet Engineering Task Force (IETF) + standard for network printing. Many of its functions can be managed + remotely (or locally) via a Web browser (giving you a + platform-independent access to the CUPS print server). Additionally, it + has the traditional command line and several more modern GUI interfaces + (GUI interfaces developed by third parties, like KDE's + overwhelming KDEPrint).

- CUPS allows creation of "raw" printers (ie: NO print file - format translation) as well as "smart" printers (i.e. CUPS does - file format conversion as required for the printer). In many ways - this gives CUPS similar capabilities to the MS Windows print - monitoring system. Of course, if you are a CUPS advocate, you would - argue that CUPS is better! In any case, let us now move on to - explore how one may configure CUPS for interfacing with MS Windows - print clients via Samba. -

Basic Configuration of CUPS support

- Printing with CUPS in the most basic smb.conf setup in Samba 3.0 (as was true for 2.2.x) only needs two - settings: printing = cups and - printcap = cups. CUPS does not need a printcap file. - However, the cupsd.conf configuration file knows of two related directives that control - how such a file will be automatically created and maintained by CUPS for the convenience of third party - applications (example: Printcap /etc/printcap and PrintcapFormat BSD). - Legacy programs often require the existence of a printcap file containing printer names or they will refuse to - print. Make sure CUPS is set to generate and maintain a printcap file! For details see - man cupsd.conf and other CUPS-related documentation, like the wealth of documents on your CUPS server - itself: http://localhost:631/documentation.html. -

Linking of smbd with libcups.so

- Samba has a very special relationship to CUPS. Samba can be compiled with CUPS library support. - Most recent installations have this support enabled. Per default CUPS linking is compiled - into smbd and other Samba binaries. Of course, you can use CUPS even - if Samba is not linked against libcups.so -- but - there are some differences in required or supported configuration - then. + CUPS allows creation of “raw” printers (i.e., no print file + format translation) as well as “smart” printers (i.e., CUPS does + file format conversion as required for the printer). In many ways + this gives CUPS similar capabilities to the MS Windows print + monitoring system. Of course, if you are a CUPS advocate, you would + argue that CUPS is better! In any case, let us now move on to + explore how one may configure CUPS for interfacing with MS Windows + print clients via Samba. +

Basic CUPS Support Configuration

+ Printing with CUPS in the most basic smb.conf setup in Samba-3.0 (as was true for 2.2.x) only needs two + settings: printing = cups and + printcap = cups. CUPS does not need a printcap file. + However, the cupsd.conf configuration file knows of two related directives that control + how such a file will be automatically created and maintained by CUPS for the convenience of third-party + applications (example: Printcap /etc/printcap and PrintcapFormat BSD). + Legacy programs often require the existence of a printcap file containing printer names or they will refuse to + print. Make sure CUPS is set to generate and maintain a printcap file. For details, see + man cupsd.conf and other CUPS-related documentation, like the wealth of documents on your CUPS server + itself: http://localhost:631/documentation.html. +

Linking smbd with libcups.so

+ Samba has a special relationship to CUPS. Samba can be compiled with CUPS library support. + Most recent installations have this support enabled. Per default, CUPS linking is compiled + into smbd and other Samba binaries. Of course, you can use CUPS even + if Samba is not linked against libcups.so but + there are some differences in required or supported configuration.

- When Samba is compiled against libcups, printcap = cups - uses the CUPS API to list printers, submit jobs, query queues, etc. Otherwise it maps to the System V - commands with an additional -oraw option for printing. On a Linux - system, you can use the ldd utility to find out details (ldd may not be present on - other OS platforms, or its function may be embodied by a different command): + When Samba is compiled against libcups, printcap = cups + uses the CUPS API to list printers, submit jobs, query queues, and so on. Otherwise it maps to the System V + commands with an additional -oraw option for printing. On a Linux + system, you can use the ldd utility to find out details (ldd may not be present on + other OS platforms, or its function may be embodied by a different command):

 root# ldd `which smbd`
 libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000)
@@ -96,726 +69,785 @@ libcrypto.so.0.9.6 => /usr/lib/libcrypto.so.0.9.6 (0x4005a000)
 libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000)
 [....]

- The line libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) shows - there is CUPS support compiled into this version of Samba. If this is the case, and printing = cups - is set, then any otherwise manually set print command in smb.conf is ignored. - This is an important point to remember! + The line libcups.so.2 => /usr/lib/libcups.so.2 (0x40123000) shows + there is CUPS support compiled into this version of Samba. If this is the case, and printing = cups + is set, then any otherwise manually set print command in smb.conf is ignored. + This is an important point to remember!

Tip

Should it be necessary, for any reason, to set your own print commands, you can do this by setting - printing = sysv. However, you will loose all the benefits + printing = sysv. However, you will loose all the benefits of tight CUPS/Samba integration. When you do this you must manually configure the printing system commands - (most important: print command; other commands are - lppause command, - lpresume command, - lpq command, - lprm command, - queuepause command and - queue resume command).

Simple `smb.conf` Settings for CUPS

- To summarize, here is the simplest printing-related setup for smb.conf to enable basic CUPS support: -

Example 19.1. Simplest printing-related smb.conf

[global]

load printers = yes

printing = cups

printcap name = cups

[printers]

comment = All Printers

path = /var/spool/samba

browseable = no

public = yes

guest ok = yes

writable = no

printable = yes

printer admin = root, @ntadmins

- This is all you need for basic printing setup for CUPS. It will print - all Graphic, Text, PDF and PostScript file submitted from Windows - clients. However, most of your Windows users would not know how to - send these kind of files to print without opening a GUI - application. Windows clients tend to have local printer drivers - installed. And the GUI application's print buttons start a printer - driver. Your users also very rarely send files from the command - line. Unlike UNIX clients, they hardly submit graphic, text or PDF - formatted files directly to the spooler. They nearly exclusively print - from GUI applications, with a "printer driver" hooked in between the - applications native format and the print data stream. If the backend - printer is not a PostScript device, the print data stream is "binary", - sensible only for the target printer. Read on to learn which problem - this may cause and how to avoid it. -

More complex `smb.conf` Settings for -CUPS

-Here is a slightly more complex printing-related setup -for smb.conf. It enables general CUPS printing -support for all printers, but defines one printer share which is set -up differently. -

Example 19.2. Overriding global CUPS settings for one printer

[global]

printing = cups

printcap name = cups

load printers = yes

[printers]

comment = All Printers

path = /var/spool/samba

public = yes

guest ok = yes

writable = no

printable = yes

printer admin = root, @ntadmins

[special_printer]

comment = A special printer with his own settings

path = /var/spool/samba-special

printing = sysv

printcap = lpstat

print command = echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ; \

echo " `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ; \

echo " `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log : rm %f

public = no

guest ok = no

writeable = no

printable = yes

printer admin = kurt

hosts deny = 0.0.0.0

hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60

-This special share is only there for testing purposes. It does not write the print job to a file. It just logs the job parameters -known to Samba into the /tmp/smbprn.log file and deletes the jobfile. Moreover, the -printer admin of this share is "kurt" (not the "@ntadmins" group); -guest access is not allowed; the share isn not published to the Network Neighbourhood (so you need to know it is there), and it only -allows access from only three hosts. To prevent CUPS kicking in and taking over the print jobs for that share, we need to set -printing = sysv and -printcap = lpstat. -

Advanced Configuration

-Before we delve into all the configuration options, let us clarify a few -points. Network printing needs to be organized and setup -correctly. Often this is not done correctly. Legacy systems -or small business LAN environments often lack design and good housekeeping. -

Central spooling vs. "Peer-to-Peer" printing

-Many small office or home networks, as well as badly organized larger -environments, allow each client a direct access to available network -printers. This is generally a bad idea. It often blocks one client's -access to the printer when another client's job is printing. It also -might freeze the first client's application while it is waiting to get -rid of the job. Also, there are frequent complaints about various jobs -being printed with their pages mixed with each other. A better concept -is the usage of a "print server": it routes all jobs through one -central system, which responds immediately, takes jobs from multiple -concurrent clients at the same time and in turn transfers them to the -printer(s) in the correct order. -

CUPS/Samba as a "spooling-only" Print Server; "raw" printing -with Vendor Drivers on Windows Clients

-Most traditionally configured UNIX print servers acting on behalf of -Samba's Windows clients represented a really simple setup. Their only -task was to manage the "raw" spooling of all jobs handed to them by -Samba. This approach meant that the Windows clients were expected to -prepare the print job file that it s ready to be sent to the printing -device. Here a native (vendor-supplied) Windows printer -driver for the target device needed to be installed on each and every -client. -

-It is possible to configure CUPS, Samba and your Windows clients in the -same, traditional and simple way. When CUPS printers are configured -for RAW print-through mode operation it is the responsibility of the -Samba client to fully render the print job (file). The file must be -sent in a format that is suitable for direct delivery to the -printer. Clients need to run the vendor-provided drivers to do -this. In this case CUPS will NOT do any print file format conversion -work. -

Driver Installation Methods on Windows Clients

-The printer drivers on the Windows clients may be installed -in two functionally different ways: -

manually install the drivers locally on each client, -one by one; this yields the old LanMan style -printing; it uses a \\sambaserver\printershare -type of connection.
- - deposit and prepare the drivers (for later download) on -the print server (Samba); this enables the clients to use -"Point and Print" to get drivers semi-automatically installed the -first time they access the printer; with this method NT/2K/XP -clients use the SPOOLSS/MS-RPC -type printing calls.

-The second method is recommended for use over the first. -

Explicitly enable "raw" printing for -application/octet-stream!

-If you use the first option (drivers are installed on the client -side), there is one setting to take care of: CUPS needs to be told -that it should allow "raw" printing of deliberate (binary) file -formats. The CUPS files that need to be correctly set for RAW mode -printers to work are: -

/etc/cups/mime.types -
/etc/cups/mime.convs

-Both contain entries (at the end of the respective files) which must -be uncommented to allow RAW mode operation. -In/etc/cups/mime.types make sure this line is -present: -

- application/octet-stream
-

-In /etc/cups/mime.convs, -have this line: -

- application/octet-stream   application/vnd.cups-raw   0   - 
-

-If these two files are not set up correctly for raw Windows client -printing, you may encounter the dreaded Unable to -convert file 0 in your CUPS error_log file. -

Note

editing the mime.convs and the -mime.types file does not -enforce "raw" printing, it only -allows it. -

Background. -CUPS being a more security-aware printing system than traditional ones -does not by default allow a user to send deliberate (possibly binary) -data to printing devices. This could be easily abused to launch a -"Denial of Service" attack on your printer(s), causing at the least -the loss of a lot of paper and ink. "Unknown" data are tagged by CUPS -as MIME type: application/octet-stream and not -allowed to go to the printer. By default, you can only send other -(known) MIME types "raw". Sending data "raw" means that CUPS does not -try to convert them and passes them to the printer untouched (see next -chapter for even more background explanations). -

-This is all you need to know to get the CUPS/Samba combo printing -"raw" files prepared by Windows clients, which have vendor drivers -locally installed. If you are not interested in background information about -more advanced CUPS/Samba printing, simply skip the remaining sections -of this chapter. -

Three familiar Methods for driver upload plus a new one

-If you want to use the MS-RPC type printing, you must upload the -drivers onto the Samba server first ([print$] -share). For a discussion on how to deposit printer drivers on the -Samba host (so that the Windows clients can download and use them via -"Point'n'Print") please also refer to the previous chapter of this -HOWTO Collection. There you will find a description or reference to -three methods of preparing the client drivers on the Samba server: -

the GUI, "Add Printer Wizard" -upload-from-a-Windows-client -method;
the commandline, "smbclient/rpcclient" -upload-from-a-UNIX-workstation -method;
- - the Imprints Toolset -method.

-These 3 methods apply to CUPS all the same. A new and more -convenient way to load the Windows drivers into Samba is provided -if you use CUPS: -

the cupsaddsmb -utility.

-cupsaddsmb is discussed in much detail further below. But we will -first explore the CUPS filtering system and compare the Windows and -UNIX printing architectures. -

Using CUPS/Samba in an advanced Way -- intelligent printing -with PostScript Driver Download

-Are you still following this? Good. Let's go into more detail then. We now know -how to set up a "dump" printserver, that is, a server which is spooling -printjobs "raw", leaving the print data untouched. -

-Possibly you need to setup CUPS in a more smart way. The reasons could -be manifold: -

Maybe your boss wants to get monthly statistics: Which -printer did how many pages? What was the average data size of a job? -What was the average print run per day? What are the typical hourly -peaks in printing? Which departments prints how -much?
Maybe you are asked to setup a print quota system: -users should not be able to print more jobs, once they have surpassed -a given limit per period?
Maybe your previous network printing setup is a mess -and shall be re-organized from a clean beginning?
Maybe you have experiencing too many "Blue Screens", -originating from poorly debugged printer drivers running in NT "kernel -mode"?

-These goals cannot be achieved by a raw print server. To build a -server meeting these requirements, you'll first need to learn about -how CUPS works and how you can enable its features. -

-What follows is the comparison of some fundamental concepts for -Windows and UNIX printing; then is the time for a description of the -CUPS filtering system, how it works and how you can tweak it. -

GDI on Windows -- PostScript on UNIX

-Network printing is one of the most complicated and error-prone -day-to-day tasks any user or an administrator may encounter. This is -true for all OS platforms. And there are reasons for this. -

-You can't expect for most file formats to just throw them towards -printers and they get printed. There needs to be a file format -conversion in between. The problem is: there is no common standard for -print file formats across all manufacturers and printer types. While -PostScript (trademark held by Adobe), and, to an -extent, PCL (trademark held by HP), have developed -into semi-official "standards", by being the most widely used PDLs -(Page Description Languages), there are still -many manufacturers who "roll their own" (their reasons may be -unacceptable license fees for using printer-embedded PostScript -interpreters, etc.). -

Windows Drivers, GDI and EMF

-In Windows OS, the format conversion job is done by the printer -drivers. On MS Windows OS platforms all application programmers have -at their disposal a built-in API, the GDI (Graphical Device -Interface), as part and parcel of the OS itself, to base -themselves on. This GDI core is used as one common unified ground, for -all Windows programs, to draw pictures, fonts and documents -on screen as well as on -paper (=print). Therefore printer driver developers can -standardize on a well-defined GDI output for their own driver -input. Achieving WYSIWYG ("What You See Is What You Get") is -relatively easy, because the on-screen graphic primitives, as well as -the on-paper drawn objects, come from one common source. This source, -the GDI, produces often a file format called EMF (Enhanced -MetaFile). The EMF is processed by the printer driver and -converted to the printer-specific file format. -

Note

- -To the GDI foundation in MS Windows, Apple has chosen to -put paper and screen output on a common foundation for their -(BSD-UNIX-based, did you know??) Mac OS X and Darwin Operating -Systems. Their Core Graphic Engine uses a -PDF derivative for all display work. -

+ (most important: + print command; other commands are + lppause command, + lpresume command, + lpq command, + lprm command, + queuepause command and + queue resume command).

Simple `smb.conf` Settings for CUPS

+ To summarize, shows simplest printing-related setup for smb.conf to enable basic CUPS support: +

Example 19.1. Simplest printing-related smb.conf

[global]

load printers = yes

printing = cups

printcap name = cups

[printers]

comment = All Printers

path = /var/spool/samba

browseable = no

public = yes

guest ok = yes

writable = no

printable = yes

printer admin = root, @ntadmins

+ This is all you need for basic printing setup for CUPS. It will print + all graphic, text, PDF, and PostScript files submitted from Windows + clients. However, most of your Windows users would not know how to + send these kinds of files to print without opening a GUI + application. Windows clients tend to have local printer drivers + installed, and the GUI application's print buttons start a printer + driver. Your users also rarely send files from the command + line. Unlike UNIX clients, they hardly submit graphic, text or PDF + formatted files directly to the spooler. They nearly exclusively print + from GUI applications with a “printer driver” hooked in between the + application's native format and the print-data-stream. If the backend + printer is not a PostScript device, the print data stream is “binary,” + sensible only for the target printer. Read on to learn which problem + this may cause and how to avoid it. +

More Complex CUPS `smb.conf` Settings

+ is a slightly more complex printing-related setup + for smb.conf. It enables general CUPS printing + support for all printers, but defines one printer share, which is set + up differently. +

Example 19.2. Overriding global CUPS settings for one printer

[global]

printing = cups

printcap name = cups

load printers = yes

[printers]

comment = All Printers

path = /var/spool/samba

public = yes

guest ok = yes

writable = no

printable = yes

printer admin = root, @ntadmins

[special_printer]

comment = A special printer with his own settings

path = /var/spool/samba-special

printing = sysv

printcap = lpstat

print command = echo "NEW: `date`: printfile %f" >> /tmp/smbprn.log ; \

echo " `date`: p-%p s-%s f-%f" >> /tmp/smbprn.log ; \

echo " `date`: j-%j J-%J z-%z c-%c" >> /tmp/smbprn.log : rm %f

public = no

guest ok = no

writeable = no

printable = yes

printer admin = kurt

hosts deny = 0.0.0.0

hosts allow = turbo_xp, 10.160.50.23, 10.160.51.60

+ This special share is only there for testing purposes. It does not write the print job to a file. It just logs the job parameters + known to Samba into the /tmp/smbprn.log file and deletes the jobfile. Moreover, the + printer admin of this share is “kurt” (not the “@ntadmins” group), + guest access is not allowed, the share isn't published to the Network Neighborhood (so you need to know it is there), and it only + allows access from only three hosts. To prevent CUPS kicking in and taking over the print jobs for that share, we need to set + printing = sysv and + printcap = lpstat. +

Advanced Configuration

+ Before we delve into all the configuration options, let us clarify a few + points. Network printing needs to be organized and setup + correctly. This frequently doesn't happen. Legacy systems + or small business LAN environments often lack design and good housekeeping. +

Central Spooling vs. “Peer-to-Peer” Printing

+ + + Many small office or home networks, as well as badly organized larger + environments, allow each client a direct access to available network + printers. This is generally a bad idea. It often blocks one client's + access to the printer when another client's job is printing. It might + freeze the first client's application while it is waiting to get + rid of the job. Also, there are frequent complaints about various jobs + being printed with their pages mixed with each other. A better concept + is the usage of a print server: it routes all jobs through one + central system, which responds immediately, takes jobs from multiple + concurrent clients at the same time, and in turn transfers them to the + printer(s) in the correct order. +

Raw Print Serving Vendor Drivers on Windows Clients

+ + + Most traditionally configured UNIX print servers acting on behalf of + Samba's Windows clients represented a really simple setup. Their only + task was to manage the “raw” spooling of all jobs handed to them by + Samba. This approach meant that the Windows clients were expected to + prepare the print job file that its ready to be sent to the printing + device. Here is a native (vendor-supplied) Windows printer + driver for the target device needed to be installed on each and every + client. +

+ It is possible to configure CUPS, Samba and your Windows clients in the + same traditional and simple way. When CUPS printers are configured + for RAW print-through mode operation, it is the responsibility of the + Samba client to fully render the print job (file). The file must be + sent in a format that is suitable for direct delivery to the + printer. Clients need to run the vendor-provided drivers to do + this. In this case, CUPS will not do any print file format conversion + work. +

Installation of Windows Client Drivers

+ The printer drivers on the Windows clients may be installed + in two functionally different ways: +

Manually install the drivers locally on each client, + one by one; this yields the old LanMan style + printing and uses a \\sambaserver\printershare + type of connection.
+ + Deposit and prepare the drivers (for later download) on + the print server (Samba); this enables the clients to use + “Point'n'Print” to get drivers semi-automatically installed the + first time they access the printer; with this method NT/200x/XP + clients use the SPOOLSS/MS-RPC + type printing calls.

+ The second method is recommended for use over the first. +

Explicitly Enable “raw” Printing for application/octet-stream

+ + + + If you use the first option (drivers are installed on the client + side), there is one setting to take care of: CUPS needs to be told + that it should allow “raw” printing of deliberate (binary) file + formats. The CUPS files that need to be correctly set for RAW mode + printers to work are: +

/etc/cups/mime.types
/etc/cups/mime.convs

+ Both contain entries (at the end of the respective files) which must + be uncommented to allow RAW mode operation. + In /etc/cups/mime.types, make sure this line is + present: -

Figure 19.1. Windows Printing to a local Printer

UNIX Printfile Conversion and GUI Basics

-In UNIX and Linux, there is no comparable layer built into the OS -kernel(s) or the X (screen display) server. Every application is -responsible for itself to create its print output. Fortunately, most -use PostScript. That gives at least some common ground. Unfortunately, -there are many different levels of quality for this PostScript. And -worse: there is a huge difference (and no common root) in the way how -the same document is displayed on screen and how it is presented on -paper. WYSIWYG is more difficult to achieve. This goes back to the -time decades ago, when the predecessors of X.org, -designing the UNIX foundations and protocols for Graphical User -Interfaces refused to take over responsibility for "paper output" -also, as some had demanded at the time, and restricted itself to -"on-screen only". (For some years now, the "Xprint" project has been -under development, attempting to build printing support into the X -framework, including a PostScript and a PCL driver, but it is not yet -ready for prime time.) You can see this unfavorable inheritance up to -the present day by looking into the various "font" directories on your -system; there are separate ones for fonts used for X display and fonts -to be used on paper. -

Background. -The PostScript programming language is an "invention" by Adobe Inc., -but its specifications have been published to the full. Its strength -lies in its powerful abilities to describe graphical objects (fonts, -shapes, patterns, lines, curves, dots...), their attributes (color, -linewidth...) and the way to manipulate (scale, distort, rotate, -shift...) them. Because of its open specification, anybody with the -skill can start writing his own implementation of a PostScript -interpreter and use it to display PostScript files on screen or on -paper. Most graphical output devices are based on the concept of -"raster images" or "pixels" (one notable exception are pen -plotters). Of course, you can look at a PostScript file in its textual -form and you will be reading its PostScript code, the language -instructions which need to be interpreted by a rasterizer. Rasterizers -produce pixel images, which may be displayed on screen by a viewer -program or on paper by a printer. -

PostScript and Ghostscript

-So, UNIX is lacking a common ground for printing on paper and -displaying on screen. Despite this unfavorable legacy for UNIX, basic -printing is fairly easy: if you have PostScript printers at your -disposal! The reason is: these devices have a built-in PostScript -language "interpreter", also called a Raster Image -Processor (RIP), (which makes them more expensive than -other types of printers); throw PostScript towards them, and they will -spit out your printed pages. Their RIP is doing all the hard work of -converting the PostScript drawing commands into a bitmap picture as -you see it on paper, in a resolution as done by your printer. This is -no different to PostScript printing of a file from a Windows origin. -

Note

- -Traditional UNIX programs and printing systems -- while -using PostScript -- are largely not PPD-aware. PPDs are "PostScript -Printer Description" files. They enable you to specify and control all -options a printer supports: duplexing, stapling, punching... Therefore -UNIX users for a long time couldn't choose many of the supported -device and job options, unlike Windows or Apple users. But now there -is CUPS.... -

Figure 19.2. Printing to a Postscript Printer

-However, there are other types of printers out there. These don't know -how to print PostScript. They use their own Page Description -Language (PDL, often proprietary). To print to them is much -more demanding. Since your UNIX applications mostly produce -PostScript, and since these devices don't understand PostScript, you -need to convert the printfiles to a format suitable for your printer -on the host, before you can send it away. -

Ghostscript -- the Software RIP for non-PostScript Printers

-Here is where Ghostscript kicks in. Ghostscript is -the traditional (and quite powerful) PostScript interpreter used on -UNIX platforms. It is a RIP in software, capable to do a -lot of file format conversions, for a very broad -spectrum of hardware devices as well as software file formats. -Ghostscript technology and drivers is what enables PostScript printing -to non-PostScript hardware. -

Figure 19.3. Ghostscript as a RIP for non-postscript printers

Tip

-Use the "gs -h" command to check for all built-in "devices" of your -Ghostscript version. If you specify e.g. a parameter of --sDEVICE=png256 on your Ghostscript command -line, you are asking Ghostscript to convert the input into a PNG -file. Naming a "device" on the commandline is the most important -single parameter to tell Ghostscript how exactly it should render the -input. New Ghostscript versions are released at fairly regular -intervals, now by artofcode LLC. They are initially put under the -"AFPL" license, but re-released under the GNU GPL as soon as the next -AFPL version appears. GNU Ghostscript is probably the version -installed on most Samba systems. But it has got some -deficiencies. Therefore ESP Ghostscript was developed as an -enhancement over GNU Ghostscript, with lots of bug-fixes, additional -devices and improvements. It is jointly maintained by developers from -CUPS, Gimp-Print, MandrakeSoft, SuSE, RedHat and Debian. It includes -the "cups" device (essential to print to non-PS printers from CUPS). -

PostScript Printer Description (PPD) Specification

-While PostScript in essence is a Page Description -Language (PDL) to represent the page layout in a -device independent way, real world print jobs are -always ending up to be output on a hardware with device-specific -features. To take care of all the differences in hardware, and to -allow for innovations, Adobe has specified a syntax and file format -for PostScript Printer Description (PPD) -files. Every PostScript printer ships with one of these files. -

-PPDs contain all information about general and special features of the -given printer model: Which different resolutions can it handle? Does -it have a Duplexing Unit? How many paper trays are there? What media -types and sizes does it take? For each item it also names the special -command string to be sent to the printer (mostly inside the PostScript -file) in order to enable it. -

-Information from these PPDs is meant to be taken into account by the -printer drivers. Therefore, installed as part of the Windows -PostScript driver for a given printer is the printer's PPD. Where it -makes sense, the PPD features are presented in the drivers' UI dialogs -to display to the user as choice of print options. In the end, the -user selections are somehow written (in the form of special -PostScript, PJL, JCL or vendor-dependent commands) into the PostScript -file created by the driver. -

Warning

- -A PostScript file that was created to contain device-specific commands -for achieving a certain print job output (e.g. duplexed, stapled and -punched) on a specific target machine, may not print as expected, or -may not be printable at all on other models; it also may not be fit -for further processing by software (e.g. by a PDF distilling program). -

CUPS can use all Windows-formatted Vendor PPDs

-CUPS can handle all spec-compliant PPDs as supplied by the -manufacturers for their PostScript models. Even if a -UNIX/Linux-illiterate vendor might not have mentioned our favorite -OS in his manuals and brochures -- you can safely trust this: -if you get hold of the Windows NT version of the PPD, you -can use it unchanged in CUPS and thus access the full -power of your printer just like a Windows NT user could! -

Tip

-To check the spec compliance of any PPD online, go to http://www.cups.org/testppd.php -and upload your PPD. You will see the results displayed -immediately. CUPS in all versions after 1.1.19 has a much more strict -internal PPD parsing and checking code enabled; in case of printing -trouble this online resource should be one of your first pitstops. -

Warning

- - -For real PostScript printers don't use the -Foomatic or cupsomatic -PPDs from Linuxprinting.org. With these devices the original -vendor-provided PPDs are always the first choice! -

Tip

-If you are looking for an original vendor-provided PPD of a specific -device, and you know that an NT4 box (or any other Windows box) on -your LAN has the PostScript driver installed, just use -smbclient //NT4-box/print\$ -U username to -access the Windows directory where all printer driver files are -stored. First look in the W32X86/2 subdir for -the PPD you are seeking. -

CUPS also uses PPDs for non-PostScript Printers

-CUPS also uses specially crafted PPDs to handle non-PostScript -printers. These PPDs are usually not available from the vendors (and -no, you can't just take the PPD of a Postscript printer with the same -model name and hope it works for the non-PostScript version too). To -understand how these PPDs work for non-PS printers we first need to -dive deeply into the CUPS filtering and file format conversion -architecture. Stay tuned. -

The CUPS Filtering Architecture

+	 application/octet-stream
+

+ + + + + In /etc/cups/mime.convs, + have this line: + + + +

+		application/octet-stream   application/vnd.cups-raw   0   - 
+

+ + If these two files are not set up correctly for raw Windows client + printing, you may encounter the dreaded Unable to + convert file 0 in your CUPS error_log file. +

Note

Editing the mime.convs and the + mime.types file does not + enforce “raw” printing, it only + allows it. +

Background. + + CUPS being a more security-aware printing system than traditional ones + does not by default allow a user to send deliberate (possibly binary) + data to printing devices. This could be easily abused to launch a + “Denial of Service” attack on your printer(s), causing at least + the loss of a lot of paper and ink. “Unknown” data are tagged by CUPS + as MIME type: application/octet-stream and not + allowed to go to the printer. By default, you can only send other + (known) MIME types “raw”. Sending data “raw” means that CUPS does not + try to convert them and passes them to the printer untouched (see the next + chapter for even more background explanations). +

+ This is all you need to know to get the CUPS/Samba combo printing + “raw” files prepared by Windows clients, which have vendor drivers + locally installed. If you are not interested in background information about + more advanced CUPS/Samba printing, simply skip the remaining sections + of this chapter. +

Driver Upload Methods

+ This section describes three familiar methods, plus one new one, by which + printer drivers may be uploaded. +

+ + If you want to use the MS-RPC type printing, you must upload the + drivers onto the Samba server first ([print$] + share). For a discussion on how to deposit printer drivers on the + Samba host (so the Windows clients can download and use them via + “Point'n'Print”), please refer to the previous chapter of this + HOWTO Collection. There you will find a description or reference to + three methods of preparing the client drivers on the Samba server: +

+ + The GUI, “Add Printer Wizard” + upload-from-a-Windows-client + method.
The command line, “smbclient/rpcclient” + upload-from-a-UNIX-workstation method.
+ + The Imprints Toolset + method.

+ These three methods apply to CUPS all the same. A new and more + convenient way to load the Windows drivers into Samba is provided + if you use CUPS: +

+ + the cupsaddsmb + utility.

+ cupsaddsmb is discussed in much detail further below. But we first + explore the CUPS filtering system and compare the Windows and UNIX printing architectures. +

Advanced Intelligent Printing with PostScript Driver Download

+ + We now know + how to set up a “dump” printserver, that is, a server which is spooling + printjobs “raw”, leaving the print data untouched. +

+ Possibly you need to setup CUPS in a smarter way. The reasons could + be manifold: +

Maybe your boss wants to get monthly statistics: Which + printer did how many pages? What was the average data size of a job? + What was the average print run per day? What are the typical hourly + peaks in printing? Which department prints how much?
Maybe you are asked to setup a print quota system: + Users should not be able to print more jobs, once they have surpassed + a given limit per period.
Maybe your previous network printing setup is a mess + and must be re-organized from a clean beginning.
Maybe you have experiencing too many “blue screens” + originating from poorly debugged printer drivers running in NT “kernel mode”?

+ These goals cannot be achieved by a raw print server. To build a + server meeting these requirements, you'll first need to learn about + how CUPS works and how you can enable its features. +

+ What follows is the comparison of some fundamental concepts for + Windows and UNIX printing; then follows a description of the + CUPS filtering system, how it works and how you can tweak it. +

GDI on Windows -- PostScript on UNIX

+ + + Network printing is one of the most complicated and error-prone + day-to-day tasks any user or administrator may encounter. This is + true for all OS platforms. And there are reasons for this. +

+ + + You can't expect most file formats to just throw them toward + printers and they get printed. There needs to be a file format + conversion in between. The problem is that there is no common standard for + print file formats across all manufacturers and printer types. While + PostScript (trademark held by Adobe) and, to an + extent, PCL (trademark held by HP) have developed + into semi-official “standards” by being the most widely used PDLs + Page Description Languages (PDLs), there are still + many manufacturers who “roll their own” (their reasons may be + unacceptable license fees for using printer-embedded PostScript + interpreters, and so on). +

Windows Drivers, GDI and EMF

+ + + + In Windows OS, the format conversion job is done by the printer + drivers. On MS Windows OS platforms all application programmers have + at their disposal a built-in API, the Graphical Device + Interface (GDI), as part and parcel of the OS itself to base + themselves on. This GDI core is used as one common unified ground for + all Windows programs to draw pictures, fonts and documents + on screen as well as on + paper (print). Therefore, printer driver developers can + standardize on a well-defined GDI output for their own driver + input. Achieving WYSIWYG (“What You See Is What You Get”) is + relatively easy, because the on-screen graphic primitives, as well as + the on-paper drawn objects, come from one common source. This source, + the GDI, often produces a file format called Enhanced + MetaFile (EMF). The EMF is processed by the printer driver and + converted to the printer-specific file format. +

Note

+ + To the GDI foundation in MS Windows, Apple has chosen to + put paper and screen output on a common foundation for their + (BSD-UNIX-based, did you know?) Mac OS X and Darwin Operating + + + + + Systems. Their Core Graphic Engine uses a + PDF derivative for all display work. +

+ +

Figure 19.1. Windows printing to a local printer.

UNIX Printfile Conversion and GUI Basics

+ + + + + In UNIX and Linux, there is no comparable layer built into the OS + kernel(s) or the X (screen display) server. Every application is + responsible for itself to create its print output. Fortunately, most + use PostScript and that at least gives some common ground. Unfortunately, + there are many different levels of quality for this PostScript. And + worse, there is a huge difference (and no common root) in the way + the same document is displayed on screen and how it is presented on + paper. WYSIWYG is more difficult to achieve. This goes back to the + time, decades ago, when the predecessors of X.org, + designing the UNIX foundations and protocols for Graphical User + Interfaces, refused to take responsibility for “paper output” + also, as some had demanded at the time, and restricted itself to + “on-screen only.” (For some years now, the “Xprint” project has been + under development, attempting to build printing support into the X + framework, including a PostScript and a PCL driver, but it is not yet + ready for prime time.) You can see this unfavorable inheritance up to + the present day by looking into the various “font” directories on your + system; there are separate ones for fonts used for X display and fonts + to be used on paper. +

Background. + + The PostScript programming language is an “invention” by Adobe Inc., + but its specifications have been published to the full. Its strength + lies in its powerful abilities to describe graphical objects (fonts, + shapes, patterns, lines, curves, and dots), their attributes (color, + linewidth) and the way to manipulate (scale, distort, rotate, + shift) them. Because of its open specification, anybody with the + skill can start writing his own implementation of a PostScript + interpreter and use it to display PostScript files on screen or on + paper. Most graphical output devices are based on the concept of + “raster images” or “pixels” (one notable exception is pen + plotters). Of course, you can look at a PostScript file in its textual + form and you will be reading its PostScript code, the language + instructions which need to be interpreted by a rasterizer. Rasterizers + produce pixel images, which may be displayed on screen by a viewer + program or on paper by a printer. +

PostScript and Ghostscript

+ + + + So, UNIX is lacking a common ground for printing on paper and + displaying on screen. Despite this unfavorable legacy for UNIX, basic + printing is fairly easy if you have PostScript printers at your + disposal. The reason is these devices have a built-in PostScript + language “interpreter,” also called a Raster Image + Processor (RIP) (which makes them more expensive than + other types of printers); throw PostScript toward them, and they will + spit out your printed pages. Their RIP is doing all the hard work of + converting the PostScript drawing commands into a bitmap picture as + you see it on paper, in a resolution as done by your printer. This is + no different to PostScript printing a file from a Windows origin. +

Note

+ + Traditional UNIX programs and printing systems while + using PostScript are largely not PPD-aware. PPDs are “PostScript + Printer Description” files. They enable you to specify and control all + options a printer supports: duplexing, stapling and punching. Therefore, + UNIX users for a long time couldn't choose many of the supported + device and job options, unlike Windows or Apple users. But now there + is CUPS. +

Figure 19.2. Printing to a PostScript printer.

+ + However, there are other types of printers out there. These do not know + how to print PostScript. They use their own Page Description + Language (PDL, often proprietary). To print to them is much + more demanding. Since your UNIX applications mostly produce + PostScript, and since these devices do not understand PostScript, you + need to convert the printfiles to a format suitable for your printer + on the host before you can send it away. +

Ghostscript the Software RIP for Non-PostScript Printers

+ + Here is where Ghostscript kicks in. Ghostscript is + the traditional (and quite powerful) PostScript interpreter used on + UNIX platforms. It is a RIP in software, capable of doing a + lot of file format conversions for a very broad + spectrum of hardware devices as well as software file formats. + Ghostscript technology and drivers are what enable PostScript printing + to non-PostScript hardware. +

Figure 19.3. Ghostscript as a RIP for non-postscript printers.

Tip

+ Use the “gs -h” command to check for all built-in “devices” + of your Ghostscript version. If you specify a parameter of + -sDEVICE=png256 on your Ghostscript command + line, you are asking Ghostscript to convert the input into a PNG + file. Naming a “device” on the command line is the most important + single parameter to tell Ghostscript exactly how it should render the + input. New Ghostscript versions are released at fairly regular + intervals, now by artofcode LLC. They are initially put under the + “AFPL” license, but re-released under the GNU GPL as soon as the next + AFPL version appears. GNU Ghostscript is probably the version + installed on most Samba systems. But it has some deficiencies. + + Therefore, ESP Ghostscript was developed as an + enhancement over GNU Ghostscript, with lots of bug-fixes, additional + devices and improvements. It is jointly maintained by developers from + CUPS, Gimp-Print, MandrakeSoft, SuSE, RedHat, and Debian. It includes + the “cups” device (essential to print to non-PS printers from CUPS). +

PostScript Printer Description (PPD) Specification

+ + While PostScript in essence is a Page Description + Language (PDL) to represent the page layout in a + device-independent way, real-world print jobs are + always ending up being output on hardware with device-specific + features. To take care of all the differences in hardware and to + allow for innovations, Adobe has specified a syntax and file format + for PostScript Printer Description (PPD) + files. Every PostScript printer ships with one of these files. +

+ PPDs contain all the information about general and special features of the + given printer model: Which different resolutions can it handle? Does + it have a Duplexing Unit? How many paper trays are there? What media + types and sizes does it take? For each item, it also names the special + command string to be sent to the printer (mostly inside the PostScript + file) in order to enable it. +

+ Information from these PPDs is meant to be taken into account by the + printer drivers. Therefore, installed as part of the Windows + PostScript driver for a given printer is the printer's PPD. Where it + makes sense, the PPD features are presented in the drivers' UI dialogs + to display to the user a choice of print options. In the end, the + user selections are somehow written (in the form of special + PostScript, PJL, JCL or vendor-dependent commands) into the PostScript + file created by the driver. +

Warning

+ + A PostScript file that was created to contain device-specific commands + for achieving a certain print job output (e.g., duplexed, stapled and + punched) on a specific target machine, may not print as expected, or + may not be printable at all on other models; it also may not be fit + for further processing by software (e.g., by a PDF distilling program). +

Using Windows-Formatted Vendor PPDs

+ CUPS can handle all spec-compliant PPDs as supplied by the + manufacturers for their PostScript models. Even if a + vendor might not have mentioned our favorite + OS in his manuals and brochures, you can safely trust this: + If you get the Windows NT version of the PPD, you + can use it unchanged in CUPS and thus access the full + power of your printer just like a Windows NT user could! +

Tip

+ To check the spec compliance of any PPD online, go to http://www.cups.org/testppd.php + and upload your PPD. You will see the results displayed + immediately. CUPS in all versions after 1.1.19 has a much more strict + internal PPD parsing and checking code enabled; in case of printing + trouble, this online resource should be one of your first pitstops. +

Warning

+ + + For real PostScript printers, do not use the + Foomatic or cupsomatic + PPDs from Linuxprinting.org. With these devices, the original + vendor-provided PPDs are always the first choice! +

Tip

+ If you are looking for an original vendor-provided PPD of a specific + device, and you know that an NT4 box (or any other Windows box) on + your LAN has the PostScript driver installed, just use + smbclient //NT4-box/print\$ -U username to + access the Windows directory where all printer driver files are + stored. First look in the W32X86/2 subdir for + the PPD you are seeking. +

CUPS Also Uses PPDs for Non-PostScript Printers

+ CUPS also uses specially crafted PPDs to handle non-PostScript + printers. These PPDs are usually not available from the vendors (and + no, you can't just take the PPD of a PostScript printer with the same + model name and hope it works for the non-PostScript version too). To + understand how these PPDs work for non-PS printers, we first need to + dive deeply into the CUPS filtering and file format conversion + architecture. Stay tuned. +

The CUPS Filtering Architecture

The core of the CUPS filtering system is based on -Ghostscript. In addition to Ghostscript, CUPS +Ghostscript. In addition to Ghostscript, CUPS uses some other filters of its own. You (or your OS vendor) may have plugged in even more filters. CUPS handles all data file formats under -the label of various MIME types. Every incoming +the label of various MIME types. Every incoming printfile is subjected to an initial -auto-typing. The auto-typing determines its given +auto-typing. The auto-typing determines its given MIME type. A given MIME type implies zero or more possible filtering chains relevant to the selected target printer. This section discusses how MIME types recognition and conversion rules interact. They are used by CUPS to automatically setup a working filtering chain for any given input data format.

-If CUPS rasterizes a PostScript file natively to -a bitmap, this is done in 2 stages: -

the first stage uses a Ghostscript device named "cups" +If CUPS rasterizes a PostScript file natively to +a bitmap, this is done in two stages: +
- The first stage uses a Ghostscript device named “cups” (this is since version 1.1.15) and produces a generic raster format -called "CUPS raster". -
- the second stage uses a "raster driver" which converts -the generic CUPS raster to a device specific raster.
-Make sure your Ghostscript version has the "cups" device compiled in -(check with gs -h | grep cups). Otherwise you +called “CUPS raster”. +
The second stage uses a “raster driver” that converts + the generic CUPS raster to a device-specific raster.

+Make sure your Ghostscript version has the “cups” device compiled in +(check with gs -h | grep cups). Otherwise you may encounter the dreaded Unable to convert file -0 in your CUPS error_log file. To have "cups" as a -device in your Ghostscript, you either need to patch GNU -Ghostscript and re-compile or use ESP Ghostscript. The -superior alternative is ESP Ghostscript: it supports not just CUPS, +0 in your CUPS error_log file. To have “cups” as a +device in your Ghostscript, you either need to patch GNU +Ghostscript and re-compile, or use ESP Ghostscript. The +superior alternative is ESP Ghostscript. It supports not just CUPS, but 300 other devices too (while GNU Ghostscript supports only about 180). Because of this broad output device support, ESP Ghostscript is -the first choice for non-CUPS spoolers too. It is now recommended by +the first choice for non-CUPS spoolers, too. It is now recommended by Linuxprinting.org for all spoolers.

- - -CUPS printers may be setup to use external -rendering paths. One of the most common ones is provided by the -Foomatic/cupsomatic concept, from Linuxprinting.org. This + + +CUPS printers may be setup to use external +rendering paths. One of the most common is provided by the +Foomatic/cupsomatic concept from Linuxprinting.org. This uses the classical Ghostscript approach, doing everything in one -step. It doesn't use the "cups" device, but one of the many +step. It does not use the “cups” device, but one of the many others. However, even for Foomatic/cupsomatic usage, best results and - + broadest printer model support is provided by ESP Ghostscript (more about cupsomatic/Foomatic, particularly the new version called now foomatic-rip, follows below). -

MIME types and CUPS Filters

- +

MIME Types and CUPS Filters

+ + CUPS reads the file /etc/cups/mime.types (and all other files carrying a *.types suffix in the same directory) upon startup. These files contain the MIME -type recognition rules which are applied when CUPS runs its +type recognition rules that are applied when CUPS runs its auto-typing routines. The rule syntax is explained in the man page for mime.types and in the comments section of the mime.types file itself. A simple rule reads like this: -

- -

+ + +

  application/pdf         pdf string(0,%PDF)

-This means: if a filename has either a -.pdf suffix, or if the magic + +This means if a filename has either a +.pdf suffix or if the magic string %PDF is right at the beginning of the file itself (offset 0 from the start), then it is -a PDF file (application/pdf). +a PDF file (application/pdf). Another rule is this: -

+ +

  application/postscript  ai eps ps string(0,%!) string(0,<04>%!)

-Its meaning: if the filename has one of the suffixes + +If the filename has one of the suffixes .ai, .eps, .ps or if the file itself starts with one of the strings %! or <04>%!, it is a generic PostScript file -(application/postscript). -

Note

-There is a very important difference between two similar MIME type in -CUPS: one is application/postscript, the other is -application/vnd.cups-postscript. While -application/postscript is meant to be device +(application/postscript). +

Warning

+Don't confuse the other mime.types files your system might be using +with the one in the /etc/cups/ directory. +

Note

+There is an important difference between two similar MIME types in +CUPS: one is application/postscript, the other is +application/vnd.cups-postscript. While +application/postscript is meant to be device independent (job options for the file are still outside the PS file -content, embedded in commandline or environment variables by CUPS), -application/vnd.cups-postscript may have the job -options inserted into the PostScript data itself (were +content, embedded in command line or environment variables by CUPS), +application/vnd.cups-postscript may have the job +options inserted into the PostScript data itself (where applicable). The transformation of the generic PostScript -(application/postscript) to the device-specific version -(application/vnd.cups-postscript) is the responsibility of the -CUPS pstops filter. pstops uses information +(application/postscript) to the device-specific version +(application/vnd.cups-postscript) is the responsibility of the +CUPS pstops filter. pstops uses information contained in the PPD to do the transformation. -

Warning

-Don't confuse the other mime.types file your system might be using -with the one in the /etc/cups/ directory.

-CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI and a -lot of image formats (GIF. PNG, TIFF, JPEG, Photo-CD, SUN-Raster, -PNM, PBM, SGI-RGB and some more) and their associated MIME types +CUPS can handle ASCII text, HP-GL, PDF, PostScript, DVI, and +many image formats (GIF. PNG, TIFF, JPEG, Photo-CD, SUN-Raster, +PNM, PBM, SGI-RGB, and more) and their associated MIME types with its filters. -

MIME type Conversion Rules

MIME Type Conversion Rules

+ + CUPS reads the file /etc/cups/mime.convs (and all other files named with a *.convs suffix in the same directory) upon startup. These files contain lines naming an input MIME type, an output MIME type, a format -conversion filter which can produce the output from the input type +conversion filter that can produce the output from the input type and virtual costs associated with this conversion. One example line reads like this: -

+ +

  application/pdf         application/postscript   33   pdftops

-This means that the pdftops filter will take -application/pdf as input and produce -application/postscript as output, the virtual + +This means that the pdftops filter will take +application/pdf as input and produce +application/postscript as output; the virtual cost of this operation is 33 CUPS-$. The next filter is more expensive, costing 66 CUPS-$: -

+ + + +

  application/vnd.hp-HPGL application/postscript   66   hpgltops

-This is the hpgltops, which processes HP-GL + +This is the hpgltops, which processes HP-GL plotter files to PostScript. -

+ + + +

  application/octet-stream

+ Here are two more examples: -

+ + + +

  application/x-shell     application/postscript   33    texttops
  text/plain              application/postscript   33    texttops

-The last two examples name the texttops filter -to work on "text/plain" as well as on "application/x-shell". (Hint: -this differentiation is needed for the syntax highlighting feature of -"texttops"). -

Filter Requirements

-There are many more combinations named in mime.convs. However, you + +The last two examples name the texttops filter +to work on text/plain as well as on application/x-shell. (Hint: +This differentiation is needed for the syntax highlighting feature of +texttops). +

Filtering Overview

+ +There are many more combinations named in mime.convs. However, you are not limited to use the ones pre-defined there. You can plug in any filter you like into the CUPS framework. It must meet, or must be made -to meet some minimal requirements. If you find (or write) a cool +to meet, some minimal requirements. If you find (or write) a cool conversion filter of some kind, make sure it complies to what CUPS -needs, and put in the right lines in mime.types +needs and put in the right lines in mime.types and mime.convs, then it will work seamlessly -inside CUPS! -

Tip

-The mentioned "CUPS requirements" for filters are simple. Take +inside CUPS. +

Filter requirements

+The mentioned “CUPS requirements” for filters are simple. Take filenames or stdin as input and write to stdout. They should take these 5 or 6 arguments: printer job user title copies options [filename] -

Printer

The name of the printer queue (normally this is the -name of the filter being run)

job

The numeric job ID for the job being -printed

user

The string from the originating-user-name -attribute

title

The string from the job-name attribute

copies

The numeric value from the number-copies -attribute

options

The job options

filename

(Optionally) The print request file (if missing, +

Printer: The name of the printer queue (normally this is the +name of the filter being run).
job: The numeric job ID for the job being +printed.
user: The string from the originating-user-name +attribute.
title: The string from the job-name attribute.
copies: The numeric value from the number-copies +attribute.
options: The job options.
filename: (Optionally) The print request file (if missing, filters expected data fed through stdin). In most -cases it is very easy to write a simple wrapper script around existing -filters to make them work with CUPS.

Prefilters

-As was said, PostScript is the central file format to any UNIX based +cases, it is easy to write a simple wrapper script around existing +filters to make them work with CUPS.

Prefilters

+ +As previously stated, PostScript is the central file format to any UNIX-based printing system. From PostScript, CUPS generates raster data to feed non-PostScript printers.

-But what is happening if you send one of the supported non-PS formats -to print? Then CUPS runs "pre-filters" on these input formats to +But what happens if you send one of the supported non-PS formats +to print? Then CUPS runs “pre-filters” on these input formats to generate PostScript first. There are pre-filters to create PS from -ASCII text, PDF, DVI or HP-GL. The outcome of these filters is always -of MIME type application/postscript (meaning that +ASCII text, PDF, DVI, or HP-GL. The outcome of these filters is always +of MIME type application/postscript (meaning that any device-specific print options are not yet embedded into the PostScript by CUPS, and that the next filter to be called is pstops). Another pre-filter is running on all supported image formats, -the imagetops filter. Its outcome is always of -MIME type application/vnd.cups-postscript -(not application/postscript), meaning it has the +the imagetops filter. Its outcome is always of +MIME type application/vnd.cups-postscript +(not application/postscript), meaning it has the print options already embedded into the file.

Figure 19.4. Prefiltering in CUPS to form Postscript

pstops

-pstopsis the filter to convert -application/postscript to -application/vnd.cups-postscript. It was said +

Figure 19.4. Pre-filtering in CUPS to form PostScript.

pstops

+pstops is the filter to convert +application/postscript to +application/vnd.cups-postscript. It was said above that this filter inserts all device-specific print options (commands to the printer to ask for the duplexing of output, or -stapling an punching it, etc.) into the PostScript file. +stapling and punching it, and so on) into the PostScript file.

Figure 19.5. Adding Device-specific Print Options

Figure 19.5. Adding device-specific print options.

-This is not all: other tasks performed by it are: +This is not all. Other tasks performed by it are:

-selecting the range of pages to be printed (if you choose to -print only pages "3, 6, 8-11, 16, 19-21", or only the odd numbered -ones) +Selecting the range of pages to be printed (if you choose to +print only pages “3, 6, 8-11, 16, 19-21”, or only the odd numbered +ones).
-putting 2 or more logical pages on one sheet of paper (the -so-called "number-up" function) -
counting the pages of the job to insert the accounting -information into the /var/log/cups/page_log -

pstoraster

-pstoraster is at the core of the CUPS filtering +Putting 2 or more logical pages on one sheet of paper (the +so-called “number-up” function). +

Counting the pages of the job to insert the accounting +information into the /var/log/cups/page_log. +

pstoraster

+pstoraster is at the core of the CUPS filtering system. It is responsible for the first stage of the rasterization process. Its input is of MIME type application/vnd.cups-postscript; its output is application/vnd.cups-raster. This output format is not yet meant to be printable. Its aim is to serve as a general purpose -input format for more specialized raster drivers, +input format for more specialized raster drivers that are able to generate device-specific printer data.

Figure 19.6. Postscript to intermediate Raster format

Figure 19.6. PostScript to intermediate raster format.

CUPS raster is a generic raster format with powerful features. It is -able to include per-page information, color profiles and more to be +able to include per-page information, color profiles, and more, to be used by the following downstream raster drivers. Its MIME type is -registered with IANA and its specification is of course completely -open. It is designed to make it very easy and inexpensive for +registered with IANA and its specification is, of course, completely +open. It is designed to make it quite easy and inexpensive for manufacturers to develop Linux and UNIX raster drivers for their printer models, should they choose to do so. CUPS always takes care -for the first stage of rasterization so these vendors don't need to care +for the first stage of rasterization so these vendors do not need to care about Ghostscript complications (in fact, there is currently more than one vendor financing the development of CUPS raster drivers).

Figure 19.7. CUPS-raster production using Ghostscript

Figure 19.7. CUPS-raster production using Ghostscript.

CUPS versions before version 1.1.15 were shipping a binary (or source -code) standalone filter, named "pstoraster". pstoraster was derived +code) standalone filter, named pstoraster. pstoraster was derived from GNU Ghostscript 5.50, and could be installed besides and in addition to any GNU or AFPL Ghostscript package without conflicting.

-From version 1.1.15, this has changed. The functions for this has been +>From version 1.1.15, this has changed. The functions for this have been integrated back into Ghostscript (now based on GNU Ghostscript version -7.05). The "pstoraster" filter is now a simple shell script calling +7.05). The pstoraster filter is now a simple shell script calling gs with the -sDEVICE=cups -parameter. If your Ghostscript doesn't show a success on asking for +parameter. If your Ghostscript does not show a success on asking for gs -h |grep cups, you might not be able to -print. Update your Ghostscript then! -

imagetops and imagetoraster

-Above in the section about prefilters, we mentioned the prefilter -that generates PostScript from image formats. The imagetoraster +print. Update your Ghostscript. +

imagetops and imagetoraster

+In the section about pre-filters, we mentioned the pre-filter +that generates PostScript from image formats. The imagetoraster filter is used to convert directly from image to raster, without the intermediate PostScript stage. It is used more often than the above -mentioned prefilters. Here is a summarizing flowchart of image file -filtering: +mentioned pre-filters. A summarizing flowchart of image file +filtering is shown in .

Figure 19.8. Image format to CUPS-raster format conversion

rasterto [printers specific]

-CUPS ships with quite some different raster drivers processing CUPS +

Figure 19.8. Image format to CUPS-raster format conversion.

rasterto [printers specific]

+CUPS ships with quite different raster drivers processing CUPS raster. On my system I find in /usr/lib/cups/filter/ these: rastertoalps, rastertobj, rastertoepson, rastertoescp, rastertopcl, rastertoturboprint, rastertoapdk, rastertodymo, -rastertoescp, rastertohp and +rastertoescp, rastertohp, and rastertoprinter. Don't worry if you have less than this; some of these are installed by commercial add-ons to CUPS (like rastertoturboprint), others (like -rastertoprinter) by 3rd party driver +rastertoprinter) by third-party driver development projects (such as Gimp-Print) wanting to cooperate as closely as possible with CUPS.

Figure 19.9. Raster to Printer Specific formats

CUPS Backends

-The last part of any CUPS filtering chain is a "backend". Backends +

Figure 19.9. Raster to printer-specific formats.

CUPS Backends

+The last part of any CUPS filtering chain is a backend. Backends are special programs that send the print-ready file to the final device. There is a separate backend program for any transfer -"protocol" of sending printjobs over the network, or for every local -interface. Every CUPS printqueue needs to have a CUPS "device-URI" +protocol of sending printjobs over the network, or for every local +interface. Every CUPS print queue needs to have a CUPS “device-URI” associated with it. The device URI is the way to encode the backend used to send the job to its destination. Network device-URIs are using two slashes in their syntax, local device URIs only one, as you can see from the following list. Keep in mind that local interface names may vary much from my examples, if your OS is not Linux: -

usb: -This backend sends printfiles to USB-connected printers. An -example for the CUPS device-URI to use is: -usb:/dev/usb/lp0 -
serial: -This backend sends printfiles to serially connected printers. -An example for the CUPS device-URI to use is: -serial:/dev/ttyS0?baud=11500 -
parallel: -This backend sends printfiles to printers connected to the -parallel port. An example for the CUPS device-URI to use is: -parallel:/dev/lp0 -
scsi: -This backend sends printfiles to printers attached to the -SCSI interface. An example for the CUPS device-URI to use is: -scsi:/dev/sr1 -
lpd: -This backend sends printfiles to LPR/LPD connected network -printers. An example for the CUPS device-URI to use is: -lpd://remote_host_name/remote_queue_name -
AppSocket/HP JetDirect: -This backend sends printfiles to AppSocket (a.k.a. "HP -JetDirect") connected network printers. An example for the CUPS -device-URI to use is: -socket://10.11.12.13:9100 -
ipp: -This backend sends printfiles to IPP connected network -printers (or to other CUPS servers). Examples for CUPS device-URIs -to use are: -ipp:://192.193.194.195/ipp -(for many HP printers) or -ipp://remote_cups_server/printers/remote_printer_name -
http: -This backend sends printfiles to HTTP connected printers. -(The http:// CUPS backend is only a symlink to the ipp:// backend.) -Examples for the CUPS device-URIs to use are: -http:://192.193.194.195:631/ipp -(for many HP printers) or -http://remote_cups_server:631/printers/remote_printer_name -
smb: -This backend sends printfiles to printers shared by a Windows -host. An example for CUPS device-URIs to use are: -smb://workgroup/server/printersharename -Or -smb://server/printersharename -or -smb://username:password@workgroup/server/printersharename -or -smb://username:password@server/printersharename. -The smb:// backend is a symlink to the Samba utility -smbspool (doesn't ship with CUPS). If the -symlink is not present in your CUPS backend directory, have your -root user create it: ln -s `which smbspool` -/usr/lib/cups/backend/smb. -

-It is easy to write your own backends as Shell or Perl scripts, if you +

usb

+ This backend sends printfiles to USB-connected printers. An + example for the CUPS device-URI to use is: + usb:/dev/usb/lp0. +

serial

+ This backend sends printfiles to serially connected printers. + An example for the CUPS device-URI to use is: + serial:/dev/ttyS0?baud=11500. +

parallel

+ This backend sends printfiles to printers connected to the + parallel port. An example for the CUPS device-URI to use is: + parallel:/dev/lp0. +

scsi

+ This backend sends printfiles to printers attached to the + SCSI interface. An example for the CUPS device-URI to use is: + scsi:/dev/sr1. +

lpd

+ This backend sends printfiles to LPR/LPD connected network + printers. An example for the CUPS device-URI to use is: + lpd://remote_host_name/remote_queue_name. +

AppSocket/HP JetDirect

+ This backend sends printfiles to AppSocket (a.k.a. "HP + JetDirect") connected network printers. An example for the CUPS + device-URI to use is: + socket://10.11.12.13:9100. +

ipp

+ This backend sends printfiles to IPP connected network + printers (or to other CUPS servers). Examples for CUPS device-URIs + to use are: + ipp:://192.193.194.195/ipp + (for many HP printers) or + ipp://remote_cups_server/printers/remote_printer_name. +

http

+ This backend sends printfiles to HTTP connected printers. + (The http:// CUPS backend is only a symlink to the ipp:// backend.) + Examples for the CUPS device-URIs to use are: + http:://192.193.194.195:631/ipp + (for many HP printers) or + http://remote_cups_server:631/printers/remote_printer_name. +

smb

+ This backend sends printfiles to printers shared by a Windows + host. An example for CUPS device-URIs that may be used includes: +

smb://workgroup/server/printersharename

smb://server/printersharename

smb://username:password@workgroup/server/printersharename

smb://username:password@server/printersharename

+ The smb:// backend is a symlink to the Samba utility + smbspool (does not ship with CUPS). If the + symlink is not present in your CUPS backend directory, have your + root user create it: ln -s `which smbspool' + /usr/lib/cups/backend/smb. +

+It is easy to write your own backends as shell or Perl scripts, if you need any modification or extension to the CUPS print system. One -reason could be that you want to create "special" printers which send -the printjobs as email (through a "mailto:/" backend), convert them to -PDF (through a "pdfgen:/" backend) or dump them to "/dev/null" (In +reason could be that you want to create “special” printers that send +the printjobs as email (through a “mailto:/” backend), convert them to +PDF (through a “pdfgen:/” backend) or dump them to “/dev/null”. (In fact I have the system-wide default printer set up to be connected to -a "devnull:/" backend: there are just too many people sending jobs -without specifying a printer, or scripts and programs which don't name +a devnull:/ backend: there are just too many people sending jobs +without specifying a printer, or scripts and programs which do not name a printer. The system-wide default deletes the job and sends a polite -mail back to the $USER asking him to always specify a correct -printername). +email back to the $USER asking him to always specify the correct +printer name.)

Not all of the mentioned backends may be present on your system or usable (depending on your hardware configuration). One test for all @@ -824,315 +856,332 @@ utility. Used with the -v parameter, it lists all available backends:

 $ lpinfo -v
-

cupsomatic/Foomatic -- how do they fit into the Picture?

-"cupsomatic" filters may be the most widely used on CUPS +

The Role of `cupsomatic/foomatic`

+ + +cupsomatic filters may be the most widely used on CUPS installations. You must be clear about the fact that these were not -developed by the CUPS people. They are a "Third Party" add-on to +developed by the CUPS people. They are a third party add-on to CUPS. They utilize the traditional Ghostscript devices to render jobs for CUPS. When troubleshooting, you should know about the difference. Here the whole rendering process is done in one stage, -inside Ghostscript, using an appropriate "device" for the target -printer. cupsomatic uses PPDs which are generated from the "Foomatic" +inside Ghostscript, using an appropriate device for the target +printer. cupsomatic uses PPDs that are generated from the Foomatic Printer & Driver Database at Linuxprinting.org.

You can recognize these PPDs from the line calling the -cupsomatic filter: -

- *cupsFilter: "application/vnd.cups-postscript 0 cupsomatic" +cupsomatic filter: + +

+ *cupsFilter: "application/vnd.cups-postscript  0  cupsomatic"

-This line you may find amongst the first 40 or so lines of the PPD + +You may find this line among the first 40 or so lines of the PPD file. If you have such a PPD installed, the printer shows up in the -CUPS web interface with a foomatic namepart for -the driver description. cupsomatic is a Perl script that runs -Ghostscript, with all the complicated commandline options -auto-constructed from the selected PPD and commandline options give to +CUPS Web interface with a foomatic namepart for +the driver description. cupsomatic is a Perl script that runs +Ghostscript with all the complicated command line options +auto-constructed from the selected PPD and command line options give to the printjob. -

-However, cupsomatic is now deprecated. Its PPDs (especially the first +

+ + However, cupsomatic is now deprecated. Its PPDs (especially the first generation of them, still in heavy use out there) are not meeting the Adobe specifications. You might also suffer difficulties when you try -to download them with "Point'n'Print" to Windows clients. A better, -and more powerful successor is now in a very stable Beta-version -available: it is called foomatic-rip. To use -foomatic-rip as a filter with CUPS, you need the new-type PPDs. These -have a similar, but different line: -

- - *cupsFilter: "application/vnd.cups-postscript 0 foomatic-rip" +to download them with “Point'n'Print” to Windows clients. A better +and more powerful successor is now in a stable beta-version: it is called foomatic-rip. To use +foomatic-rip as a filter with CUPS, you need the new-type PPDs. These +have a similar but different line: +

+ *cupsFilter: "application/vnd.cups-postscript  0  foomatic-rip"

+ The PPD generating engine at Linuxprinting.org has been revamped. The new PPDs comply to the Adobe spec. On top, they also provide a new way to specify different quality levels (hi-res photo, normal -color, grayscale, draft...) with a single click (whereas before you -could have required 5 or more different selections (media type, -resolution, inktype, dithering algorithm...). There is support for +color, grayscale, and draft) with a single click, whereas before you +could have required five or more different selections (media type, +resolution, inktype and dithering algorithm). There is support for custom-size media built in. There is support to switch -print-options from page to page, in the middle of a job. And the -best thing is: the new foomatic-rip now works seamlessly with all -legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR etc.), providing -for them access to use PPDs for their printing! -

The Complete Picture

-If you want to see an overview over all the filters and how they +print-options from page to page in the middle of a job. And the +best thing is the new foomatic-rip now works seamlessly with all +legacy spoolers too (like LPRng, BSD-LPD, PDQ, PPR and so on), providing +for them access to use PPDs for their printing. +

The Complete Picture

+If you want to see an overview of all the filters and how they relate to each other, the complete picture of the puzzle is at the end of this document. -

`mime.convs`

CUPS auto-constructs all possible filtering chain paths for any given MIME type, and every printer installed. But how does it decide in -favor or against a specific alternative? (There may often be cases, +favor or against a specific alternative? (There may often be cases where there is a choice of two or more possible filtering chains for -the same target printer). Simple: you may have noticed the figures in -the 3rd column of the mime.convs file. They represent virtual costs +the same target printer.) Simple. You may have noticed the figures in +the third column of the mime.convs file. They represent virtual costs assigned to this filter. Every possible filtering chain will sum up to -a total "filter cost". CUPS decides for the most "inexpensive" route. +a total “filter cost.” CUPS decides for the most “inexpensive” route.

Tip

The setting of FilterLimit 1000 in cupsd.conf will not allow more filters to run concurrently than will consume a total of 1000 virtual filter -cost. This is a very efficient way to limit the load of any CUPS -server by setting an appropriate "FilterLimit" value. A FilterLimit of -200 allows roughly 1 job at a time, while a FilterLimit of 1000 allows -approximately 5 jobs maximum at a time. -

"Raw" printing

-You can tell CUPS to print (nearly) any file "raw". "Raw" means it -will not be filtered. CUPS will send the file to the printer "as is" +cost. This is an efficient way to limit the load of any CUPS +server by setting an appropriate “FilterLimit” value. A FilterLimit of +200 allows roughly one job at a time, while a FilterLimit of 1000 allows +approximately five jobs maximum at a time. +

“Raw” Printing

+ You can tell CUPS to print (nearly) any file “raw”. “Raw” means it + will not be filtered. CUPS will send the file to the printer “as is” without bothering if the printer is able to digest it. Users need to take care themselves that they send sensible data formats only. Raw -printing can happen on any queue if the "-o raw" option is specified +printing can happen on any queue if the “-o raw” option is specified on the command line. You can also set up raw-only queues by simply not associating any PPD with it. This command:

 $ lpadmin -P rawprinter -v socket://11.12.13.14:9100 -E

-sets up a queue named "rawprinter", connected via the "socket" -protocol (a.k.a. "HP JetDirect") to the device at IP address + sets up a queue named “rawprinter”, connected via the “socket” + protocol (a.k.a. “HP JetDirect”) to the device at IP address 11.12.1.3.14, using port 9100. (If you had added a PPD with -P /path/to/PPD to this command line, you would -have installed a "normal" printqueue. +have installed a “normal” print queue.

-CUPS will automatically treat each job sent to a queue as a "raw" one, -if it can't find a PPD associated with the queue. However, CUPS will +CUPS will automatically treat each job sent to a queue as a “raw” one, +if it can't find a PPD associated with the queue. However, CUPS will only send known MIME types (as defined in its own mime.types file) and refuse others. -

"application/octet-stream" printing

application/octet-stream Printing

Any MIME type with no rule in the /etc/cups/mime.types file is regarded as unknown -or application/octet-stream and will not be +or application/octet-stream and will not be sent. Because CUPS refuses to print unknown MIME types per default, -you will probably have experienced the fact that printjobs originating +you will probably have experienced the fact that print jobs originating from Windows clients were not printed. You may have found an error message in your CUPS logs like: -

Unable to convert file 0 to printable format for job -

-To enable the printing of "application/octet-stream" files, edit +

+To enable the printing of application/octet-stream files, edit these two files:

/etc/cups/mime.convs
/etc/cups/mime.types

Both contain entries (at the end of the respective files) which must be uncommented to allow RAW mode operation for -application/octet-stream. In /etc/cups/mime.types +application/octet-stream. In /etc/cups/mime.types make sure this line is present: -

- application/octet-stream + + + +

+application/octet-stream

+ This line (with no specific auto-typing rule set) makes all files -not otherwise auto-typed a member of application/octet-stream. In +not otherwise auto-typed a member of application/octet-stream. In /etc/cups/mime.convs, have this line: -

- application/octet-stream   application/vnd.cups-raw   0   -
-

+ +

+application/octet-stream   application/vnd.cups-raw   0   -
+

+ + + This line tells CUPS to use the Null Filter -(denoted as "-", doing... nothing at all) on -application/octet-stream, and tag the result as -application/vnd.cups-raw. This last one is +(denoted as “-”, doing nothing at all) on +application/octet-stream, and tag the result as +application/vnd.cups-raw. This last one is always a green light to the CUPS scheduler to now hand the file over -to the "backend" connecting to the printer and sending it over. -

Note

Editing the mime.convs and the +to the backend connecting to the printer and sending it over. +

Note

Editing the mime.convs and the mime.types file does not -enforce "raw" printing, it only +enforce “raw” printing, it only allows it.

Background. CUPS being a more security-aware printing system than traditional ones does not by default allow one to send deliberate (possibly binary) -data to printing devices. (This could be easily abused to launch a +data to printing devices. (This could be easily abused to launch a Denial of Service attack on your printer(s), causing at least the loss -of a lot of paper and ink...) "Unknown" data are regarded by CUPS +of a lot of paper and ink...) “Unknown” data are regarded by CUPS as MIME type application/octet-stream. While you -can send data "raw", the MIME type for these must +can send data “raw”, the MIME type for these must be one that is known to CUPS and an allowed one. The file -/etc/cups/mime.types defines the "rules" how CUPS +/etc/cups/mime.types defines the “rules” of how CUPS recognizes MIME types. The file /etc/cups/mime.convs decides which file conversion filter(s) may be applied to which MIME types. -

PostScript Printer Descriptions (PPDs) for non-PS Printers

PostScript Printer Descriptions (PPDs) for Non-PS Printers

+ Originally PPDs were meant to be used for PostScript printers only. Here, they help to send device-specific commands and settings to the RIP which processes the jobfile. CUPS has extended this scope for PPDs to cover non-PostScript printers too. This was not -very difficult, because it is a standardized file format. In a way +difficult, because it is a standardized file format. In a way it was logical too: CUPS handles PostScript and uses a PostScript -RIP (=Ghostscript) to process the jobfiles. The only difference is: +RIP (Ghostscript) to process the jobfiles. The only difference is: a PostScript printer has the RIP built-in, for other types of printers the Ghostscript RIP runs on the host computer.

PPDs for a non-PS printer have a few lines that are unique to CUPS. The most important one looks similar to this: -

+ + + +

  *cupsFilter: application/vnd.cups-raster  66   rastertoprinter

+ It is the last piece in the CUPS filtering puzzle. This line tells the -CUPS daemon to use as a last filter "rastertoprinter". This filter -should be served as input an "application/vnd.cups-raster" MIME type -file. Therefore CUPS should auto-construct a filtering chain, which +CUPS daemon to use as a last filter rastertoprinter. This filter +should be served as input an application/vnd.cups-raster MIME type +file. Therefore, CUPS should auto-construct a filtering chain, which delivers as its last output the specified MIME type. This is then -taken as input to the specified "rastertoprinter" filter. After this -the last filter has done its work ("rastertoprinter" is a Gimp-Print +taken as input to the specified rastertoprinter filter. After this +the last filter has done its work (rastertoprinter is a Gimp-Print filter), the file should go to the backend, which sends it to the output device.

CUPS by default ships only a few generic PPDs, but they are good for several hundred printer models. You may not be able to control different paper trays, or you may get larger margins than your -specific model supports): -

Table 19.1. PPD's shipped with CUPS

PPD file	Printer type
deskjet.ppd	older HP inkjet printers and compatible
deskjet2.ppd	newer HP inkjet printers and compatible
dymo.ppd	label printers
epson9.ppd	Epson 24pin impact printers and compatible
epson24.ppd	Epson 24pin impact printers and compatible
okidata9.ppd	Okidata 9pin impact printers and compatible
okidat24.ppd	Okidata 24pin impact printers and compatible
stcolor.ppd	older Epson Stylus Color printers
stcolor2.ppd	newer Epson Stylus Color printers
stphoto.ppd	older Epson Stylus Photo printers
stphoto2.ppd	newer Epson Stylus Photo printers
laserjet.ppd	all PCL printers. Further below is a discussion of several other driver/PPD-packages suitable for use with CUPS.

Difference between cupsomatic/foomatic-rip and -native CUPS printing

-Native CUPS rasterization works in two steps. +specific model supports. See for summary information. +

Table 19.1. PPDs shipped with CUPS

PPD file	Printer type
deskjet.ppd	older HP inkjet printers and compatible
deskjet2.ppd	newer HP inkjet printers and compatible
dymo.ppd	label printers
epson9.ppd	Epson 24pin impact printers and compatible
epson24.ppd	Epson 24pin impact printers and compatible
okidata9.ppd	Okidata 9pin impact printers and compatible
okidat24.ppd	Okidata 24pin impact printers and compatible
stcolor.ppd	older Epson Stylus Color printers
stcolor2.ppd	newer Epson Stylus Color printers
stphoto.ppd	older Epson Stylus Photo printers
stphoto2.ppd	newer Epson Stylus Photo printers
laserjet.ppd	all PCL printers. Further below is a discussion + of several other driver/PPD-packages suitable for use with CUPS.

cupsomatic/foomatic-rip Versus native CUPS Printing

+ + +Native CUPS rasterization works in two steps:

-First is the "pstoraster" step. It uses the special "cups" - -device from ESP Ghostscript 7.05.x as its tool +First is the pstoraster step. It uses the special CUPS + +device from ESP Ghostscript 7.05.x as its tool.
-Second comes the "rasterdriver" step. It uses various +Second comes the rasterdriver step. It uses various device-specific filters; there are several vendors who provide good -quality filters for this step, some are Free Software, some are -Shareware/Non-Free, some are proprietary.

+quality filters for this step. Some are free software, some are +shareware/non-free and some are proprietary.

Often this produces better quality (and has several more advantages) than other methods.

Figure 19.10. cupsomatic/foomatic processing versus Native CUPS

Figure 19.10. cupsomatic/foomatic Processing versus Native CUPS.

-One other method is the cupsomatic/foomatic-rip -way. Note that cupsomatic is not made by the CUPS +One other method is the cupsomatic/foomatic-rip +way. Note that cupsomatic is not made by the CUPS developers. It is an independent contribution to printing development, -made by people from Linuxprinting.org (see also http://www.cups.org/cups-help.html). -cupsomatic is no longer developed and maintained and is no longer +made by people from Linuxprinting.org ^[4]. +cupsomatic is no longer developed and maintained and is no longer supported. It has now been replaced by -foomatic-rip. foomatic-rip is a complete re-write -of the old cupsomatic idea, but very much improved and generalized to +foomatic-rip. foomatic-rip is a complete re-write +of the old cupsomatic idea, but very much improved and generalized to other (non-CUPS) spoolers. An upgrade to foomatic-rip is strongly -advised, especially if you are upgrading to a recent version of CUPS +advised, especially if you are upgrading to a recent version of CUPS, too.

- - -Both the cupsomatic (old) and the foomatic-rip (new) methods from + + +Both the cupsomatic (old) and the foomatic-rip (new) methods from Linuxprinting.org use the traditional Ghostscript print file processing, doing everything in a single step. It therefore relies on -all the other devices built-in into Ghostscript. The quality is as +all the other devices built into Ghostscript. The quality is as good (or bad) as Ghostscript rendering is in other spoolers. The advantage is that this method supports many printer models not supported (yet) by the more modern CUPS method.

Of course, you can use both methods side by side on one system (and -even for one printer, if you set up different queues), and find out +even for one printer, if you set up different queues) and find out which works best for you.

-cupsomatic "kidnaps" the printfile after the -application/vnd.cups-postscript stage and -deviates it through the CUPS-external, system wide Ghostscript -installation: Therefore the printfile bypasses the "pstoraster" filter -(and thus also bypasses the CUPS-raster-drivers -"rastertosomething"). After Ghostscript finished its rasterization, -cupsomatic hands the rendered file directly to the CUPS backend. The -flowchart above illustrates the difference between native CUPS -rendering and the Foomatic/cupsomatic method. -

Examples for filtering Chains

+cupsomatic kidnaps the printfile after the +application/vnd.cups-postscript stage and +deviates it through the CUPS-external, system-wide Ghostscript +installation. Therefore the printfile bypasses the pstoraster filter +(and also bypasses the CUPS-raster-drivers +rastertosomething). After Ghostscript finished its rasterization, +cupsomatic hands the rendered file directly to the CUPS backend. The +flowchart in illustrates the difference between native CUPS +rendering and the Foomatic/cupsomatic method. +

Examples for Filtering Chains

Here are a few examples of commonly occurring filtering chains to illustrate the workings of CUPS.

-Assume you want to print a PDF file to a HP JetDirect-connected +Assume you want to print a PDF file to an HP JetDirect-connected PostScript printer, but you want to print the pages 3-5, 7, 11-13 -only, and you want to print them "2-up" and "duplex": -

your print options (page selection as required, 2-up, -duplex) are passed to CUPS on the commandline;
the (complete) PDF file is sent to CUPS and autotyped as -application/pdf;
the file therefore first must pass the -pdftops pre-filter, which produces PostScript -MIME type application/postscript (a preview here -would still show all pages of the original PDF);
the file then passes the pstops -filter which applies the commandline options: it selects the pages -2-5, 7 and 11-13, creates and imposed layout "2 pages on 1 sheet" and -inserts the correct "duplex" command (as is defined in the printer's -PPD) into the new PostScript file; the file now is of PostScript MIME +only, and you want to print them “two-up” and “duplex”: +
- Your print options (page selection as required, two-up, +duplex) are passed to CUPS on the command line.
- The (complete) PDF file is sent to CUPS and autotyped as +application/pdf.
- The file therefore must first pass the +pdftops pre-filter, which produces PostScript +MIME type application/postscript (a preview here +would still show all pages of the original PDF).
- The file then passes the pstops +filter that applies the command line options: it selects the pages +2-5, 7 and 11-13, creates an imposed layout “2 pages on 1 sheet” and +inserts the correct “duplex” command (as defined in the printer's +PPD) into the new PostScript file; the file is now of PostScript MIME type -application/vnd.cups-postscript;
- the file goes to the socket +application/vnd.cups-postscript.
- The file goes to the socket backend, which transfers the job to the printers.
- The resulting filter chain therefore is as drawn in the image below. -
Figure 19.11. PDF to socket chain
+ The resulting filter chain, therefore, is as drawn in . +
Figure 19.11. PDF to socket chain.
Assume your want to print the same filter to an USB-connected -Epson Stylus Photo printer, installed with the CUPS +Epson Stylus Photo printer installed with the CUPS stphoto2.ppd. The first few filtering stages are nearly the same: -
- your print options (page selection as required, 2-up, -duplex) are passed to CUPS on the commandline;
- the (complete) PDF file is sent to CUPS and autotyped as -application/pdf;
- the file therefore first must pass the -pdftops pre-filter, which produces PostScript -MIME type application/postscript (a preview here -would still show all pages of the original PDF);
- the file then passes the "pstops" filter which applies +
  - Your print options (page selection as required, two-up, +duplex) are passed to CUPS on the commandline.
  - The (complete) PDF file is sent to CUPS and autotyped as +application/pdf.
  - The file must first pass the +pdftops pre-filter, which produces PostScript +MIME type application/postscript (a preview here +would still show all pages of the original PDF).
  - The file then passes the “pstops” filter that applies the commandline options: it selects the pages 2-5, 7 and 11-13, -creates and imposed layout "2 pages on 1 sheet" and inserts the -correct "duplex" command... (OOoops -- this printer and his PPD -don't support duplex printing at all -- this option will be ignored -then) into the new PostScript file; the file now is of PostScript +creates an imposed layout “two pages on one sheet” and inserts the +correct “duplex” command... (Oops this printer and PPD +do not support duplex printing at all so this option will +be ignored) into the new PostScript file; the file is now of PostScript MIME type -application/vnd.cups-postscript;
  - the file then passes the -pstoraster stage and becomes MIME type -application/cups-raster;
  - finally, the rastertoepson filter -does its work (as is indicated in the printer's PPD), creating the -printer-specific raster data and embedding any user-selected -print-options into the print data stream;
  - the file goes to the usb backend, +application/vnd.cups-postscript.
  - The file then passes the + +pstoraster stage and becomes MIME type +application/ +cups-raster.
  - Finally, the rastertoepson filter +does its work (as indicated in the printer's PPD), creating the +rinter-specific raster data and embedding any user-selected +print-options into the print data stream.
  - The file goes to the usb backend, which transfers the job to the printers.
  - The resulting filter chain therefore is as drawn in the image below. -
  Figure 19.12. PDF to USB chain
Sources of CUPS drivers / PPDs
-On the internet you can find now many thousand CUPS-PPD files -(with their companion filters), in many national languages, -supporting more than 1000 non-PostScript models. -
- ESP -PrintPro (commercial, -non-Free) is packaged with more than 3000 PPDs, ready for -successful use "out of the box" on Linux, Mac OS X, IBM-AIX, -HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital UNIX and some + The resulting filter chain therefore is as drawn in . +
  Figure 19.12. PDF to USB chain.
Sources of CUPS Drivers/PPDs
+On the Internet you can now find many thousands of CUPS-PPD files +(with their companion filters), in many national languages +supporting more than thousand non-PostScript models. +
- ESP +PrintPro (commercial, +non-free) is packaged with more than three thousand PPDs, ready for +successful use “out of the box” on Linux, Mac OS X, IBM-AIX, +HP-UX, Sun-Solaris, SGI-IRIX, Compaq Tru64, Digital UNIX, and some more commercial Unices (it is written by the CUPS developers themselves and its sales help finance the further development of -CUPS, as they feed their creators).
- the Gimp-Print-Project - (GPL, Free Software) +CUPS, as they feed their creators).
- The Gimp-Print-Project + (GPL, free software) provides around 140 PPDs (supporting nearly 400 printers, many driven to photo quality output), to be used alongside the Gimp-Print CUPS -filters;
- TurboPrint - (Shareware, non-Free) supports +filters.
- TurboPrint + (shareware, non-free) supports roughly the same amount of printers in excellent -quality;
- OMNI - -(LPGL, Free) is a package made by IBM, now containing support for more +quality.
- OMNI + +(LPGL, free) is a package made by IBM, now containing support for more than 400 printers, stemming from the inheritance of IBM OS/2 Know-How -ported over to Linux (CUPS support is in a Beta-stage at -present);
- HPIJS - (BSD-style licenses, Free) +ported over to Linux (CUPS support is in a beta-stage at +present).
- HPIJS + (BSD-style licenses, free) supports around 150 of HP's own printers and is also providing excellent print quality now (currently available only via the Foomatic -path);
- Foomatic/cupsomatic - (LPGL, Free) from +path).
- Foomatic/cupsomatic + (LPGL, free) from Linuxprinting.org are providing PPDs for practically every Ghostscript filter known to the world (including Omni, Gimp-Print and -HPIJS).
Note
-The cupsomatic/Foomatic trick from Linuxprinting.org works -differently from the other drivers. This is explained elsewhere in this -document. -
Printing with Interface Scripts
-CUPS also supports the usage of "interface scripts" as known from +HPIJS).

Printing with Interface Scripts

+CUPS also supports the usage of “interface scripts” as known from System V AT&T printing systems. These are often used for PCL -printers, from applications that generate PCL print jobs. Interface +printers, from applications that generate PCL print jobs. Interface scripts are specific to printer models. They have a similar role as PPDs for PostScript printers. Interface scripts may inject the Escape sequences as required into the print data stream, if the user has @@ -1145,126 +1194,138 @@ the -i option: root# lpadmin -p pclprinter -v socket://11.12.13.14:9100 \ -i /path/to/interface-script

-Interface scripts might be the "unknown animal" to many. However, -with CUPS they provide the most easy way to plug in your own +Interface scripts might be the “unknown animal” to many. However, +with CUPS they provide the easiest way to plug in your own custom-written filtering script or program into one specific print queue (some information about the traditional usage of interface scripts is -to be found at http://playground.sun.com/printing/documentation/interface.html). -

Network printing (purely Windows)

+to be found at http://playground.sun.com/printing/documentation/interface.html). +

Network Printing (Purely Windows)

Network printing covers a lot of ground. To understand what exactly goes on with Samba when it is printing on behalf of its Windows -clients, let's first look at a "purely Windows" setup: Windows clients +clients, let's first look at a “purely Windows” setup: Windows clients with a Windows NT print server. -

From Windows Clients to an NT Print Server

Windows clients printing to an NT-based print server have two -options. They may -

execute the driver locally and render the GDI output -(EMF) into the printer specific format on their own, -or
send the GDI output (EMF) to the server, where the +options. They may: + + +
- Execute the driver locally and render the GDI output + (EMF) into the printer-specific format on their own. +
- Send the GDI output (EMF) to the server, where the driver is executed to render the printer specific output.
-Both print paths are shown in the flowcharts below. -

Driver Execution on the Client

-In the first case the print server must spool the file as "raw", + Both print paths are shown in the flowcharts in the figures below. +

Driver Execution on the Client

+In the first case the print server must spool the file as raw, meaning it shouldn't touch the jobfile and try to convert it in any -way. This is what traditional UNIX-based print server can do too; and -at a better performance and more reliably than NT print server. This +way. This is what a traditional UNIX-based print server can do too, and +at a better performance and more reliably than an NT print server. This is what most Samba administrators probably are familiar with. One -advantage of this setup is that this "spooling-only" print server may +advantage of this setup is that this “spooling-only” print server may be used even if no driver(s) for UNIX are available it is sufficient -to have the Windows client drivers available and installed on the +to have the Windows client drivers available; and installed on the clients.

Figure 19.13. Print Driver execution on the Client

Driver Execution on the Server

-The other path executes the printer driver on the server. The clients +

Figure 19.13. Print driver execution on the client.

Driver Execution on the Server

+ + + + + +The other path executes the printer driver on the server. The client transfers print files in EMF format to the server. The server uses the PostScript, PCL, ESC/P or other driver to convert the EMF file into the printer-specific language. It is not possible for UNIX to do the -same. Currently there is no program or method to convert a Windows +same. Currently, there is no program or method to convert a Windows client's GDI output on a UNIX server into something a printer could understand.

Figure 19.14. Print Driver execution on the Server

Figure 19.14. Print driver execution on the server.

-However, there is something similar possible with CUPS. Read on... -

Network Printing (Windows clients -- UNIX/Samba Print +However, there is something similar possible with CUPS. Read on. +

Network Printing (Windows Clients UNIX/Samba Print Servers)

Since UNIX print servers cannot execute the Win32 program code on their platform, the picture is somewhat -different. However, this doesn't limit your options all that -much. In the contrary, you may have a way here to implement printing -features which are not possible otherwise. -

From Windows Clients to a CUPS/Samba Print Server

-Here is a simple recipe showing how you can take advantage of CUPS +different. However, this does not limit your options all that +much. On the contrary, you may have a way here to implement printing +features that are not possible otherwise. +

From Windows Clients to a CUPS/Samba Print Server

+Here is a simple recipe showing how you can take advantage of CUPS' powerful features for the benefit of your Windows network printing clients:

Let the Windows clients send PostScript to the CUPS -server.
Let the CUPS server render the PostScript into device -specific raster format.

+server.

Let the CUPS server render the PostScript into device-specific raster format.

This requires the clients to use a PostScript driver (even if the printer is a non-PostScript model. It also requires that you have a -"driver" on the CUPS server. +driver on the CUPS server.

-Firstly, to enable CUPS based printing through Samba the +First, to enable CUPS-based rinting through Samba the following options should be set in your smb.conf file [global] section: -

printing = cups
printcap = cups

printing = cups

printcap = cups

When these parameters are specified, all manually set print directives -(like print command, or lppause command) in smb.conf (as well as -in samba itself) will be ignored. Instead, Samba will directly -interface with CUPS through it's application program interface (API) - +(like print command, or lppause command) in smb.conf (as well as +in Samba itself) will be ignored. Instead, Samba will directly +interface with CUPS through its application program interface (API), as long as Samba has been compiled with CUPS library (libcups) -support. If Samba has NOT been compiled with CUPS support, and if no +support. If Samba has not been compiled with CUPS support, and if no other print commands are set up, then printing will use the System V AT&T command set, with the -oraw option automatically passing through (if you want your own defined print commands to work with a Samba that has CUPS support compiled in, -simply use printing = sysv). +simply use printing = sysv).

Figure 19.15. Printing via CUPS/samba server

Samba receiving Jobfiles and passing them to CUPS

Figure 19.15. Printing via CUPS/Samba server.

Samba Receiving Jobfiles and Passing Them to CUPS

Samba must use its own spool directory (it is set -by a line similar to path = /var/spool/samba, +by a line similar to path = /var/spool/samba, in the [printers] or [printername] section of smb.conf). Samba receives the job in its own spool space and passes it into the spool directory of CUPS (the CUPS spooling directory is set by the RequestRoot directive, in a line that defaults to RequestRoot -/var/spool/cups). CUPS checks the access rights of its -spool dir and resets it to healthy values with every re-start. We have -seen quite some people who had used a common spooling space for Samba -and CUPS, and were struggling for weeks with this "problem". +/var/spool/cups). CUPS checks the access rights of its +spool dir and resets it to healthy values with every restart. We have +seen quite a few people who had used a common spooling space for Samba +and CUPS, and were struggling for weeks with this “problem.”

A Windows user authenticates only to Samba (by whatever means is configured). If Samba runs on the same host as CUPS, you only need to -allow "localhost" to print. If they run on different machines, you +allow “localhost” to print. If they run on different machines, you need to make sure the Samba host gets access to printing on CUPS. -

Network PostScript RIP: CUPS Filters on Server -- clients use -PostScript Driver with CUPS-PPDs

Network PostScript RIP

+This section discusses the use of CUPS filters on the server configuration where +clients make use of a PostScript driver with CUPS-PPDs. +

+ + + PPDs can control all print device options. They are usually provided -by the manufacturer; if you own a PostScript printer, that is. PPD +by the manufacturer, if you own a PostScript printer, that is. PPD files (PostScript Printer Descriptions) are always a component of PostScript printer drivers on MS Windows or Apple Mac OS systems. They are ASCII files containing user-selectable print options, mapped to appropriate PostScript, PCL or PJL commands for the target printer. Printer driver GUI dialogs translate these options -"on-the-fly" into buttons and drop-down lists for the user to select. +“on-the-fly” into buttons and drop-down lists for the user to select.

CUPS can load, without any conversions, the PPD file from any Windows (NT is recommended) PostScript driver and handle the options. There is -a web browser interface to the print options (select http://localhost:631/printers/ -and click on one Configure Printer button to see -it), or a commandline interface (see man lpoptions -or see if you have lphelp on your system). There are also some +a Web browser interface to the print options (select http://localhost:631/printers/ +and click on one Configure Printer button to see +it), or a command line interface (see man lpoptions +or see if you have lphelp on your system). There are also some different GUI frontends on Linux/UNIX, which can present PPD options to users. PPD options are normally meant to be evaluated by the PostScript RIP on the real PostScript printer. -

PPDs for non-PS Printers on UNIX

-CUPS doesn't limit itself to "real" PostScript printers in its usage +

PPDs for Non-PS Printers on UNIX

+ +CUPS does not limit itself to “real” PostScript printers in its usage of PPDs. The CUPS developers have extended the scope of the PPD -concept, to also describe available device and driver options for +concept to also describe available device and driver options for non-PostScript printers through CUPS-PPDs.

This is logical, as CUPS includes a fully featured PostScript @@ -1272,104 +1333,109 @@ interpreter (RIP). This RIP is based on Ghostscript. It can process all received PostScript (and additionally many other file formats) from clients. All CUPS-PPDs geared to non-PostScript printers contain an additional line, starting with the keyword -*cupsFilter . This line tells the CUPS print +*cupsFilter. This line tells the CUPS print system which printer-specific filter to use for the interpretation of the supplied PostScript. Thus CUPS lets all its printers appear as PostScript devices to its clients, because it can act as a PostScript RIP for those printers, processing the received PostScript code into a proper raster print format. -

PPDs for non-PS Printers on Windows

PPDs for Non-PS Printers on Windows

+ CUPS-PPDs can also be used on Windows-Clients, on top of a -"core" PostScript driver (now recommended is the "CUPS PostScript -Driver for WindowsNT/2K/XP"; you can also use the Adobe one, with +“core” PostScript driver (now recommended is the "CUPS PostScript +Driver for WindowsNT/200x/XP"; you can also use the Adobe one, with limitations). This feature enables CUPS to do a few tricks no other spooler can do: -

act as a networked PostScript RIP (Raster Image +
- Act as a networked PostScript RIP (Raster Image Processor), handling printfiles from all client platforms in a uniform -way;
- act as a central accounting and billing server, since -all files are passed through the pstops filter and are therefore +way.
- Act as a central accounting and billing server, since +all files are passed through the pstops filter and are, therefore, logged in the CUPS page_log file. -NOTE: this can not happen with "raw" print jobs, -which always remain unfiltered per definition;
- enable clients to consolidate on a single PostScript +Note: this cannot happen with “raw” print jobs, +which always remain unfiltered per definition.
- Enable clients to consolidate on a single PostScript driver, even for many different target printers.
Using CUPS PPDs on Windows clients enables these to control -all print job settings just as a UNIX client can do too. -

Windows Terminal Servers (WTS) as CUPS Clients

+all print job settings just as a UNIX client can do. +

Windows Terminal Servers (WTS) as CUPS Clients

This setup may be of special interest to people experiencing major -problems in WTS environments. WTS need often a multitude of +problems in WTS environments. WTS often need a multitude of non-PostScript drivers installed to run their clients' variety of different printer models. This often imposes the price of much increased instability. -

Printer Drivers running in "Kernel Mode" cause many +
Printer Drivers Running in “Kernel Mode” Cause Many Problems
-The reason is that in Win NT printer drivers run in "Kernel -Mode", this introduces a high risk for the stability of the system + In Windows NT printer drivers which run in “Kernel +Mode”, introduces a high risk for the stability of the system if the driver is not really stable and well-tested. And there are a lot of bad drivers out there! Especially notorious is the example of the PCL printer driver that had an additional sound module running, to notify users via soundcard of their finished jobs. Do I -need to say that this one was also reliably causing "Blue Screens -of Death" on a regular basis? +need to say that this one was also reliably causing “blue screens +of death” on a regular basis?
-PostScript drivers generally are very well tested. They are not known -to cause any problems, even though they run in Kernel Mode too. This -might be because there have so far only been 2 different PostScript +PostScript drivers are generally well tested. They are not known +to cause any problems, even though they also run in kernel mode. This +might be because there have been so far only two different PostScript drivers: the ones from Adobe and the one from Microsoft. Both are -very well tested and are as stable as you ever can imagine on +well tested and are as stable as you can imagine on Windows. The CUPS driver is derived from the Microsoft one. -
Workarounds impose Heavy Limitations
+
Workarounds Impose Heavy Limitations
In many cases, in an attempt to work around this problem, site -administrators have resorted to restrict the allowed drivers installed -on their WTS to one generic PCL- and one PostScript driver. This -however restricts the clients in the amount of printer options -available for them; often they can't get out more than simplex +administrators have resorted to restricting the allowed drivers installed +on their WTS to one generic PCL and one PostScript driver. This, +however, restricts the clients in the number of printer options +available for them. Often they can't get out more than simplex prints from one standard paper tray, while their devices could do much -better, if driven by a different driver! ) -
CUPS: a "Magical Stone"?
+better, if driven by a different driver! +
CUPS: A “Magical Stone”?
+ + Using a PostScript driver, enabled with a CUPS-PPD, seems to be a very elegant way to overcome all these shortcomings. There are, depending -on the version of Windows OS you use, up to 3 different PostScript +on the version of Windows OS you use, up to three different PostScript drivers available: Adobe, Microsoft and CUPS PostScript drivers. None of them is known to cause major stability problems on WTS (even if used with many different PPDs). The clients will be able to (again) chose paper trays, duplex printing and other settings. However, there is a certain price for this too: a CUPS server acting as a PostScript RIP for its clients requires more CPU and RAM than when just acting as -a "raw spooling" device. Plus, this setup is not yet widely tested, +a “raw spooling” device. Plus, this setup is not yet widely tested, although the first feedbacks look very promising. -
PostScript Drivers with no major problems -- even in Kernel -Mode
-More recent printer drivers on W2K and XP don't run in Kernel mode -(unlike Win NT) any more. However, both operating systems can still -use the NT drivers, running in Kernel mode (you can roughly tell which -is which as the drivers in subdirectory "2" of "W32X86" are "old" -ones). As was said before, the Adobe as well as the Microsoft +
PostScript Drivers with No Major Problems Even in Kernel +Mode
+ +More recent printer drivers on W200x and XP no longer run in kernel mode +(unlike Windows NT). However, both operating systems can still +use the NT drivers, running in kernel mode (you can roughly tell which +is which as the drivers in subdirectory “2” of “W32X86” are “old” +ones). As was said before, the Adobe as well as the Microsoft PostScript drivers are not known to cause any stability problems. The CUPS driver is derived from the Microsoft one. There is a simple -reason for this: The MS DDK (Device Development Kit) for Win NT (which +reason for this: The MS DDK (Device Development Kit) for Windows NT (which used to be available at no cost to licensees of Visual Studio) includes the source code of the Microsoft driver, and licensees of Visual Studio are allowed to use and modify it for their own driver development efforts. This is what the CUPS people have done. The -license doesn't allow them to publish the whole of the source code. -However, they have released the "diff" under the GPL, and if you are -owner of an "MS DDK for Win NT", you can check the driver yourself. -

Setting up CUPS for driver Download

-As we have said before: all previously known methods to prepare client -printer drivers on the Samba server for download and "Point'n'Print" -convenience of Windows workstations are working with CUPS too. These +license does not allow them to publish the whole of the source code. +However, they have released the “diff” under the GPL, and if you are +the owner of an “MS DDK for Windows NT,” you can check the driver yourself. +

Configuring CUPS for Driver Download

+As we have said before, all previously known methods to prepare client +printer drivers on the Samba server for download and Point'n'Print +convenience of Windows workstations are working with CUPS, too. These methods were described in the previous chapter. In reality, this is a -pure Samba business, and only relates to the Samba/Win client +pure Samba business and only relates to the Samba/Windows client relationship. -

cupsaddsmb: the unknown Utility

-The cupsaddsmb utility (shipped with all current CUPS versions) is an -alternative method to transfer printer drivers into the Samba +

cupsaddsmb: The Unknown Utility

+ +The cupsaddsmb utility (shipped with all current CUPS versions) is an +alternate method to transfer printer drivers into the Samba [print$] share. Remember, this share is where clients expect drivers deposited and setup for download and -installation. It makes the sharing of any (or all) installed CUPS -printers very easy. cupsaddsmb can use the Adobe PostScript driver as -well as the newly developed CUPS PostScript Driver for -WinNT/2K/XP. Note, that cupsaddsmb does +installation. It makes the sharing of any (or all) installed CUPS +printers quite easy. cupsaddsmb can use the Adobe PostScript driver as +well as the newly developed CUPS PostScript Driver for +Windows NT/200x/XP. cupsaddsmb does not work with arbitrary vendor printer drivers, but only with the exact driver files that are named in its man page. @@ -1378,23 +1444,24 @@ The CUPS printer driver is available from the CUPS download site. Its package name is cups-samba-[version].tar.gz . It is preferred over the Adobe drivers since it has a number of advantages: -

it supports a much more accurate page -accounting;
it supports banner pages, and page labels on all -printers;
it supports the setting of a number of job IPP +
- It supports a much more accurate page +accounting.
- It supports banner pages, and page labels on all +printers.
- It supports the setting of a number of job IPP attributes (such as job-priority, page-label and -job-billing)
-However, currently only Windows NT, 2000, and XP are supported by the -CUPS drivers. You will need to get the respective part of Adobe driver -too if you need to support Windows 95, 98, and ME clients. -

Prepare your `smb.conf` for cupsaddsmb

-Prior to running cupsaddsmb, you need the following settings in -smb.conf: -

Example 19.3. smb.conf for cupsaddsmb usage

[global]

load printers = yes

printing = cups

printcap name = cups

[printers]

comment = All Printers

path = /var/spool/samba

browseable = no

public = yes

# setting depends on your requirements

guest ok = yes

writable = no

printable = yes

printer admin = root

[print$]

comment = Printer Drivers

path = /etc/samba/drivers

browseable = yes

guest ok = no

read only = yes

write list = root

CUPS Package of "PostScript Driver for WinNT/2k/XP"

-CUPS users may get the exactly same packages from http://www.cups.org/software.html. +job-billing).

+However, currently only Windows NT, 2000 and XP are supported by the +CUPS drivers. You will also need to get the respective part of Adobe driver +if you need to support Windows 95, 98 and ME clients. +

Prepare Your `smb.conf` for cupsaddsmb

+Prior to running cupsaddsmb, you need the settings in +smb.conf as shown in : +

Example 19.3. smb.conf for cupsaddsmb usage

[global]

load printers = yes

printing = cups

printcap name = cups

[printers]

comment = All Printers

path = /var/spool/samba

browseable = no

public = yes

# setting depends on your requirements

guest ok = yes

writable = no

printable = yes

printer admin = root

[print$]

comment = Printer Drivers

path = /etc/samba/drivers

browseable = yes

guest ok = no

read only = yes

write list = root

CUPS “PostScript Driver for Windows NT/200x/XP”

+ +CUPS users may get the exact same packages from http://www.cups.org/software.html. It is a separate package from the CUPS base software files, tagged as -CUPS 1.1.x Windows NT/2k/XP Printer Driver for Samba -(tar.gz, 192k). The filename to download is -cups-samba-1.1.x.tar.gz. Upon untar-/unzip-ing, +CUPS 1.1.x Windows NT/200x/XP Printer Driver for Samba +(tar.gz, 192k). The filename to download is +cups-samba-1.1.x.tar.gz. Upon untar and unzipping, it will reveal these files:

 root# tar xvzf cups-samba-1.1.19.tar.gz
@@ -1404,15 +1471,15 @@ cups-samba.readme
 cups-samba.remove
 cups-samba.ss

- - + + These have been packaged with the ESP meta packager software -"EPM". The *.install and +EPM. The *.install and *.remove files are simple shell scripts, which untars the *.ss (the *.ss is -nothing else but a tar-archive, which can be untar-ed by "tar" +nothing else but a tar-archive, which can be untarred by “tar” too). Then it puts the content into -/usr/share/cups/drivers/. This content includes 3 +/usr/share/cups/drivers/. This content includes three files:

 root# tar tv cups-samba.ss
@@ -1420,7 +1487,7 @@ cupsdrvr.dll
 cupsui.dll
 cups.hlp

-The cups-samba.install shell scripts is easy to +The cups-samba.install shell scripts are easy to handle:

 root# ./cups-samba.install
@@ -1428,7 +1495,7 @@ handle:
 Installing software...
 Updating file permissions...
 Running post-install commands...
-Installation is complete.        
+Installation is complete.

The script should automatically put the driver files into the /usr/share/cups/drivers/ directory. @@ -1439,206 +1506,210 @@ into/usr/share/drivers/ instead of /usr/share/cups/drivers/. To work around this, copy/move the file (after running the ./cups-samba.install script) manually to the -right place. +correct place.

 root# cp /usr/share/drivers/cups.hlp /usr/share/cups/drivers/
-

+ This new CUPS PostScript driver is currently binary-only, but free of -charge. No complete source code is provided (yet). The reason is this: -it has been developed with the help of the Microsoft Driver -Developer Kit (DDK) and compiled with Microsoft Visual +charge. No complete source code is provided (yet). The reason is that +it has been developed with the help of the Microsoft Driver +Developer Kit (DDK) and compiled with Microsoft Visual Studio 6. Driver developers are not allowed to distribute the whole of -the source code as Free Software. However, CUPS developers released -the "diff" in source code under the GPL, so anybody with a license of +the source code as free software. However, CUPS developers released +the “diff” in source code under the GPL, so anybody with a license of Visual Studio and a DDK will be able to compile for him/herself. -

Recognize the different Driver Files

-The CUPS drivers don't support the "older" Windows 95/98/ME, but only -the Windows NT/2000/XP client: -

Windows NT, 2000, and XP are supported by:

cups.hlp
cupsdrvr.dll
cupsui.dll

-Adobe drivers are available for the older Windows 95/98/ME as well as -the Windows NT/2000/XP clients. The set of files is different for the +

Recognizing Different Driver Files

+The CUPS drivers do not support the older Windows 95/98/Me, but only +the Windows NT/2000/XP client. +

Windows NT, 2000 and XP are supported by:

cups.hlp
cupsdrvr.dll
cupsui.dll

+Adobe drivers are available for the older Windows 95/98/Me as well as +the Windows NT/2000/XP clients. The set of files is different from the different platforms. -

Windows 95, 98, and Me are supported by:

ADFONTS.MFM
ADOBEPS4.DRV
ADOBEPS4.HLP
DEFPRTR2.PPD
ICONLIB.DLL
PSMON.DLL

Windows NT, 2000, and XP are supported by:

ADOBEPS5.DLL
ADOBEPSU.DLL
ADOBEPSU.HLP

Windows 95, 98 and ME are supported by:

ADFONTS.MFM
ADOBEPS4.DRV
ADOBEPS4.HLP
DEFPRTR2.PPD
ICONLIB.DLL
PSMON.DLL

Windows NT, 2000 and XP are supported by:

ADOBEPS5.DLL
ADOBEPSU.DLL
ADOBEPSU.HLP

Note

-If both, the Adobe driver files and the CUPS driver files for the -support of WinNT/2k/XP are present in , the Adobe ones will be ignored -and the CUPS ones will be used. If you prefer -- for whatever reason --- to use Adobe-only drivers, move away the 3 CUPS driver files. The -Win95/98/ME clients use the Adobe drivers in any case. -

Acquiring the Adobe Driver Files

+If both the Adobe driver files and the CUPS driver files for the +support of Windows NT/200x/XP are present in FIXME, the Adobe ones will be ignored +and the CUPS ones will be used. If you prefer for whatever reason + to use Adobe-only drivers, move away the three CUPS driver files. The +Windows 9x/Me clients use the Adobe drivers in any case. +

Acquiring the Adobe Driver Files

Acquiring the Adobe driver files seems to be unexpectedly difficult -for many users. They are not available on the Adobe website as single -files and the self-extracting and/or self-installing Windows-exe is +for many users. They are not available on the Adobe Web site as single +files and the self-extracting and/or self-installing Windows-.exe is not easy to locate either. Probably you need to use the included native installer and run the installation process on one client once. This will install the drivers (and one Generic PostScript -printer) locally on the client. When they are installed, share the -Generic PostScript printer. After this, the client's +printer) locally on the client. When they are installed, share the +Generic PostScript printer. After this, the client's [print$] share holds the Adobe files, from -where you can get them with smbclient from the CUPS host. A more -detailed description about this is in the next (the CUPS printing) -chapter. -

ESP Print Pro Package of "PostScript Driver for -WinNT/2k/XP"

-Users of the ESP Print Pro software are able to install their "Samba -Drivers" package for this purpose with no problem. Retrieve the driver +where you can get them with smbclient from the CUPS host. +

ESP Print Pro PostScript Driver for Windows NT/200x/XP

+ +Users of the ESP Print Pro software are able to install their Samba +drivers package for this purpose with no problem. Retrieve the driver files from the normal download area of the ESP Print Pro software -at http://www.easysw.com/software.html. -You need to locate the link labelled "SAMBA" amongst the -Download Printer Drivers for ESP Print Pro 4.x +at http://www.easysw.com/software.html. +You need to locate the link labelled “SAMBA” among the +Download Printer Drivers for ESP Print Pro 4.x area and download the package. Once installed, you can prepare any driver by simply highlighting the printer in the Printer Manager GUI -and select Export Driver... from the menu. Of -course you need to have prepared Samba beforehand too to handle the -driver files; i.e. mainly setup the [print$] -share, etc. The ESP Print Pro package includes the CUPS driver files -as well as a (licensed) set of Adobe drivers for the Windows 95/98/ME +and select Export Driver... from the menu. Of +course you need to have prepared Samba beforehand to handle the +driver files; i.e., setup the [print$] +share, and so on. The ESP Print Pro package includes the CUPS driver files +as well as a (licensed) set of Adobe drivers for the Windows 95/98/Me client family. -

Caveats to be considered

Caveats to be Considered

+ Once you have run the install script (and possibly manually moved the cups.hlp file to /usr/share/cups/drivers/), the driver is ready to be put into Samba's [print$] share (which often maps to -/etc/samba/drivers/ and contains a subdir +/etc/samba/drivers/ and contains a subdirectory tree with WIN40 and -W32X86 branches): You do this by running -"cupsaddsmb" (see also man cupsaddsmb for +W32X86 branches). You do this by running +cupsaddsmb (see also man cupsaddsmb for CUPS since release 1.1.16).

Tip

- + You may need to put root into the smbpasswd file by running smbpasswd; this is especially important if you should run this whole procedure for the first time, and are not working in an environment where everything is configured for -Single Sign On to a Windows Domain Controller. +single sign on to a Windows Domain Controller.

Once the driver files are in the [print$] share and are initialized, they are ready to be downloaded and installed by -the Win NT/2k/XP clients. +the Windows NT/200x/XP clients.

Note

-Win 9x/ME clients won't work with the CUPS PostScript driver. For -these you'd still need to use the ADOBE*.* -drivers as previously. -
+Win 9x/Me clients will not work with the CUPS PostScript driver. For +these you still need to use the ADOBE*.* +drivers as previously stated. +

Note

It is not harmful if you still have the ADOBE*.* driver files from previous installations in the /usr/share/cups/drivers/ -directory. The new cupsaddsmb (from 1.1.16) will -automatically prefer "its own" drivers if it finds both. -

- -Should your Win clients have had the old ADOBE*.* +directory. The new cupsaddsmb (from 1.1.16) will +automatically prefer its own drivers if it finds both. +

Note

+ +Should your Windows clients have had the old ADOBE*.* files for the Adobe PostScript driver installed, the download and -installation of the new CUPS PostScript driver for Windows NT/2k/XP +installation of the new CUPS PostScript driver for Windows NT/200x/XP will fail at first. You need to wipe the old driver from the clients -first. It is not enough to "delete" the printer, as the driver files +first. It is not enough to “delete” the printer, as the driver files will still be kept by the clients and re-used if you try to re-install the printer. To really get rid of the Adobe driver files on the -clients, open the "Printers" folder (possibly via Start, Settings, Control Panel, Printers), -right-click onto the folder background and select Server -Properties. When the new dialog opens, select the -Drivers tab. On the list select the driver you -want to delete and click on the Delete +clients, open the Printers folder (possibly via Start > Settings > Control Panel > Printers), +right-click on the folder background and select Server +Properties. When the new dialog opens, select the +Drivers tab. On the list select the driver you +want to delete and click the Delete button. This will only work if there is not one single printer left -which uses that particular driver. You need to "delete" all printers -using this driver in the "Printers" folder first. You will need +that uses that particular driver. You need to “delete” all printers +using this driver in the Printers folder first. You will need Administrator privileges to do this. -

- +

Note

+ Once you have successfully downloaded the CUPS PostScript driver to a client, you can easily switch all printers to this one by proceeding -as described in the printing chapter: either change -a driver for an existing printer by running the "Printer Properties" +as described in . Either change +a driver for an existing printer by running the Printer Properties dialog, or use rpcclient with the -setdriver sub-command. -

Benefits of using "CUPS PostScript Driver for -Windows NT/2k/XP" instead of Adobe Driver

-You are interested in a comparison between the CUPS and the Adobe +setdriver subcommand. +

Windows CUPS PostScript Driver Versus Adobe Driver

+Are you interested in a comparison between the CUPS and the Adobe PostScript drivers? For our purposes these are the most important -items which weigh in favor of the CUPS ones: -

no hassle with the Adobe EULA
no hassle with the question “Where do I +items that weigh in favor of the CUPS ones: +
- No hassle with the Adobe EULA.
- No hassle with the question “Where do I get the ADOBE*.* driver files from?”
- - - the Adobe drivers (on request of the printer PPD + +The Adobe drivers (on request of the printer PPD associated with them) often put a PJL header in front of the main -PostScript part of the print file. Thus the printfile starts with +PostScript part of the print file. Thus, the printfile starts with <1B >%-12345X or <escape>%-12345X instead of %!PS). This leads to the CUPS daemon auto-typing the incoming file as a print-ready file, -not initiating a pass through the "pstops" filter (to speak more -technically, it is not regarded as the generic MIME type - -application/postscript, but as +not initiating a pass through the pstops filter (to speak more +technically, it is not regarded as the generic MIME-type + +application/postscript, but as the more special MIME type - -application/cups.vnd-postscript), + +application/cups.vnd-postscript), which therefore also leads to the page accounting in -/var/log/cups/page_log not +/var/log/cups/page_log not receiving the exact number of pages; instead the dummy page number -of "1" is logged in a standard setup)
- the Adobe driver has more options to "mis-configure" the +of “1” is logged in a standard setup).
- The Adobe driver has more options to misconfigure the PostScript generated by it (like setting it inadvertently to -Optimize for Speed, instead of -Optimize for Portability, which -could lead to CUPS being unable to process it)
- the CUPS PostScript driver output sent by Windows -clients to the CUPS server will be guaranteed to be auto-typed always -as generic MIME type application/postscript, -thusly passing through the CUPS "pstops" filter and logging the +Optimize for Speed, instead of +Optimize for Portability, which +could lead to CUPS being unable to process it).
- The CUPS PostScript driver output sent by Windows +clients to the CUPS server is guaranteed to auto-type +as the generic MIME type application/postscript, +thus passing through the CUPS pstops filter and logging the correct number of pages in the page_log for -accounting and quota purposes
- the CUPS PostScript driver supports the sending of -additional standard (IPP) print options by Win NT/2k/XP clients. Such +accounting and quota purposes.
- The CUPS PostScript driver supports the sending of +additional standard (IPP) print options by Windows NT/200x/XP clients. Such additional print options are: naming the CUPS standard banner pages (or the custom ones, should they be installed at the time of driver download), using the CUPS -page-label option, setting a -job-priority and setting the scheduled -time of printing (with the option to support additional -useful IPP job attributes in the future).
- the CUPS PostScript driver supports the inclusion of -the new *cupsJobTicket comments at the +page-label option, setting a +job-priority, and setting the scheduled +time of printing (with the option to support additional +useful IPP job attributes in the future).
- The CUPS PostScript driver supports the inclusion of +the new *cupsJobTicket comments at the beginning of the PostScript file (which could be used in the future for all sort of beneficial extensions on the CUPS side, but which will not disturb any other applications as they will regard it as a comment -and simply ignore it).
- the CUPS PostScript driver will be the heart of the -fully fledged CUPS IPP client for Windows NT/2K/XP to be released soon -(probably alongside the first Beta release for CUPS -1.2).

Run "cupsaddsmb" (quiet Mode)

-The cupsaddsmb command copies the needed files into your +and simply ignore it).

The CUPS PostScript driver will be the heart of the +fully fledged CUPS IPP client for Windows NT/200x/XP to be released soon +(probably alongside the first beta release for CUPS +1.2).

Run cupsaddsmb (Quiet Mode)

+ + +The cupsaddsmb command copies the needed files into your [print$] share. Additionally, the PPD associated with this printer is copied from /etc/cups/ppd/ to [print$]. There the files wait for convenient Windows client installations via Point'n'Print. Before we can run the command successfully, we need to be sure that we can authenticate -towards Samba. If you have a small network you are probably using user -level security (security = user). +toward Samba. If you have a small network, you are probably using user-level +security (security = user).

-Here is an example of a successfully run cupsaddsmb command. +Here is an example of a successfully run cupsaddsmb command:

 root# cupsaddsmb -U root infotec_IS2027
 Password for root required to access localhost via Samba: ['secret']

To share all printers and drivers, use the -a parameter instead of a printer name. Since -cupsaddsmb "exports" the printer drivers to Samba, it should be +cupsaddsmb “exports” the printer drivers to Samba, it should be obvious that it only works for queues with a CUPS driver associated. -

Run "cupsaddsmb" with verbose Output

Run cupsaddsmb with Verbose Output

+ Probably you want to see what's going on. Use the -v parameter to get a more verbose output. The -output below was edited for better readability: all "\" at the end of +output below was edited for better readability: all “\” at the end of a line indicate that I inserted an artificial line break plus some indentation here:

Warning

You will see the root password for the Samba account printed on screen. -

+ + + +

 root# cupsaddsmb -U root -v infotec_2105
 Password for root required to access localhost via GANDALF:
 Running command: smbclient //localhost/print\$ -N -U'root%secret' \
@@ -1656,11 +1727,12 @@ putting file /usr/share/cups/drivers/cupsui.dll as \W32X86/cupsui.dll
 putting file /usr/share/cups/drivers/cups.hlp as \W32X86/cups.hlp
   
 Running command: rpcclient localhost -N -U'root%secret' 
-   -c 'adddriver "Windows NT x86"   \
-   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:   \
-    RAW:NULL"'
-cmd = adddriver "Windows NT x86" \
-    "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL:RAW:NULL"
+   -c 'adddriver "Windows NT x86"   \
+   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL: \
+    RAW:NULL"'
+cmd = adddriver "Windows NT x86" \
+   "infotec_2105:cupsdrvr.dll:infotec_2105.ppd:cupsui.dll:cups.hlp:NULL: \
+	RAW:NULL"
 Printer Driver infotec_2105 successfully installed.
   
 Running command: smbclient //localhost/print\$ -N -U'root%secret' \
@@ -1684,13 +1756,14 @@ Running command: smbclient //localhost/print\$ -N -U'root%secret' \
   putting file /usr/share/cups/drivers/PSMON.DLL as \WIN40/PSMON.DLL
   
   Running command: rpcclient localhost -N -U'root%secret' \
-   -c 'adddriver "Windows 4.0"      \
-   "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP: \
+   -c 'adddriver "Windows 4.0"      \
+   "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:ADOBEPS4.HLP: \
    PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL, \
-    ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
-  cmd = adddriver "Windows 4.0" "infotec_2105:ADOBEPS4.DRV:infotec_2105.PPD:NULL:          \
-    ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,infotec_2105.PPD,ADOBEPS4.HLP,  \
-                   PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"
+    ADFONTS.MFM,DEFPRTR2.PPD,ICONLIB.DLL"'
+	cmd = adddriver "Windows 4.0" "infotec_2105:ADOBEPS4.DRV:\
+	infotec_2105.PPD:NULL:ADOBEPS4.HLP:PSMON.DLL:RAW:ADOBEPS4.DRV,\
+	infotec_2105.PPD,ADOBEPS4.HLP,PSMON.DLL,ADFONTS.MFM,DEFPRTR2.PPD,\
+	ICONLIB.DLL"
   Printer Driver infotec_2105 successfully installed.
   
   Running command: rpcclient localhost -N -U'root%secret'  \
@@ -1700,62 +1773,60 @@ Running command: smbclient //localhost/print\$ -N -U'root%secret' \

If you look closely, you'll discover your root password was transferred -unencrypted over the wire, so beware! Also, if you look further her, -you'll discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in -between. They occur, because the directories WIN40 and W32X86 already -existed in the [print$] driver download share -(from a previous driver installation). They are harmless here. -

Understanding cupsaddsmb

-What has happened? What did cupsaddsmb do? There are five stages of -the procedure +unencrypted over the wire, so beware! Also, if you look further, +you'll discover error messages like NT_STATUS_OBJECT_NAME_COLLISION in between. They occur, because the directories WIN40 and W32X86 already existed in the [print$] driver download share (from a previous driver installation). They are harmless here. +

Understanding cupsaddsmb

+ +What has happened? What did cupsaddsmb do? There are five stages of +the procedure:

- - call the CUPS server via IPP and request the -driver files and the PPD file for the named printer;
store the files temporarily in the local + + Call the CUPS server via IPP and request the +driver files and the PPD file for the named printer.
Store the files temporarily in the local TEMPDIR (as defined in -cupsd.conf);
connect via smbclient to the Samba server's +cupsd.conf).
Connect via smbclient to the Samba server's [print$] share and put the files into the - share's WIN40 (for Win95/98/ME) and W32X86/ (for WinNT/2k/XP) sub - directories;
- - connect via rpcclient to the Samba server and -execute the "adddriver" command with the correct -parameters;
- - connect via rpcclient to the Samba server a second -time and execute the "setdriver" command.

-Note, that you can run the cupsaddsmb utility with parameters to + share's WIN40 (for Windows 9x/Me) and W32X86/ (for Windows NT/200x/XP) subdirectories.

+ + Connect via rpcclient to the Samba server and +execute the adddriver command with the correct +parameters.

+ + Connect via rpcclient to the Samba server a second +time and execute the setdriver command.

Note

+You can run the cupsaddsmb utility with parameters to specify one remote host as Samba host and a second remote host as CUPS host. Especially if you want to get a deeper understanding, it is a -good idea try it and see more clearly what is going on (though in real +good idea to try it and see more clearly what is going on (though in real life most people will have their CUPS and Samba servers run on the same host):

-root# cupsaddsmb -H sambaserver -h cupsserver -v printername
-

How to recognize if cupsaddsmb completed successfully

+root# cupsaddsmb -H sambaserver -h cupsserver -v printer +

How to Recognize If cupsaddsmb Completed Successfully

You must always check if the utility completed -successfully in all fields. You need as a minimum these 3 messages -amongst the output: +successfully in all fields. You need as a minimum these three messages +among the output:

Printer Driver infotec_2105 successfully -installed. # (for the W32X86 == WinNT/2K/XP -architecture...)
Printer Driver infotec_2105 successfully -installed. # (for the WIN40 == Win9x/ME -architecture...)
Successfully set [printerXPZ] to driver +installed. # (for the W32X86 == Windows NT/200x/XP +architecture).
Printer Driver infotec_2105 successfully +installed. # (for the WIN40 == Windows 9x/Me +architecture).
Successfully set [printerXPZ] to driver [printerXYZ].

-These messages probably not easily recognized in the general -output. If you run cupsaddsmb with the -a +These messages are probably not easily recognized in the general +output. If you run cupsaddsmb with the -a parameter (which tries to prepare all active CUPS printer drivers for download), you might miss if individual printers -drivers had problems to install properly. Here a redirection of the +drivers had problems installing properly. Here a redirection of the output will help you analyze the results in retrospective.

Note

-It is impossible to see any diagnostic output if you don't run -cupsaddsmb in verbose mode. Therefore we strongly recommend to not -use the default quiet mode. It will hide any problems from you which +It is impossible to see any diagnostic output if you do not run +cupsaddsmb in verbose mode. Therefore, we strongly recommend to not +use the default quiet mode. It will hide any problems from you that might occur. -

cupsaddsmb with a Samba PDC

-You can't get the standard cupsaddsmb command to run on a Samba PDC? -You are asked for the password credential all over again and again and +

cupsaddsmb with a Samba PDC

+ +Can't get the standard cupsaddsmb command to run on a Samba PDC? +Are you asked for the password credential all over again and again and the command just will not take off at all? Try one of these variations:

@@ -1764,114 +1835,116 @@ variations:
 root# cupsaddsmb -H SAURON -U MIDEARTH\\root -h cups-server -v printername

(Note the two backslashes: the first one is required to -"escape" the second one). -

cupsaddsmb Flowchart

-Here is a chart about the procedures, commandflows and -dataflows of the "cupaddsmb" command. Note again: cupsaddsmb is -not intended to, and does not work with, "raw" queues! -

Figure 19.16. cupsaddsmb flowchart

Installing the PostScript Driver on a Client

-After cupsaddsmb completed, your driver is prepared for the clients to +“escape” the second one). +

cupsaddsmb Flowchart

+ + shows a chart about the procedures, commandflows and +dataflows of the cupaddsmb command. Note again: cupsaddsmb is +not intended to, and does not work with, raw queues! +

Figure 19.16. cupsaddsmb flowchart.

Installing the PostScript Driver on a Client

+ +After cupsaddsmb is completed, your driver is prepared for the clients to use. Here are the steps you must perform to download and install it -via "Point'n'Print". From a Windows client, browse to the CUPS/Samba -server; -

open the Printers -share of Samba in Network Neighbourhood;
right-click on the printer in -question;
from the opening context-menu select -Install... or -Connect... (depending on the Windows version you +via Point'n'Print. From a Windows client, browse to the CUPS/Samba +server: +
- + +Open the Printers +share of Samba in Network Neighborhood.
- Right-click on the printer in +question.
- From the opening context-menu select +Install... or +Connect... (depending on the Windows version you use).
After a few seconds, there should be a new printer in your -client's local "Printers" folder: On Windows +client's local Printers folder. On Windows XP it will follow a naming convention of PrinterName on -SambaServer. (In my current case it is "infotec_2105 on -kde-bitshop"). If you want to test it and send your first job from -an application like Winword, the new printer will appears in a +SambaServer. (In my current case it is "infotec_2105 on +kde-bitshop"). If you want to test it and send your first job from +an application like Winword, the new printer appears in a \\SambaServer\PrinterName entry in the -dropdown list of available printers. -
Note
- -cupsaddsmb will only reliably work with CUPS version 1.1.15 or higher -and Samba from 2.2.4. If it doesn't work, or if the automatic printer -driver download to the clients doesn't succeed, you can still manually +drop-down list of available printers. +
+ +cupsaddsmb will only reliably work with CUPS version 1.1.15 or higher +and Samba from 2.2.4. If it does not work, or if the automatic printer +driver download to the clients does not succeed, you can still manually install the CUPS printer PPD on top of the Adobe PostScript driver on clients. Then point the client's printer queue to the Samba printer share for a UNC type of connection: -
```
+
 C:\> net use lpt1: \\sambaserver\printershare /user:ntadmin
 

 should you desire to use the CUPS networked PostScript RIP
-functions. (Note that user "ntadmin" needs to be a valid Samba user
-with the required privileges to access the printershare) This would
-set up the printer connection in the traditional
+functions. (Note that user “ntadmin” needs to be a valid Samba user
+with the required privileges to access the printershare.) This
+sets up the printer connection in the traditional
 LanMan way (not using MS-RPC).
-
```

Avoiding critical PostScript Driver Settings on the -Client

-Soooo: printing works, but there are still problems. Most jobs print -well, some don't print at all. Some jobs have problems with fonts, -which don't look very good. Some jobs print fast, and some are +

Avoiding Critical PostScript Driver Settings on the Client

+Printing works, but there are still problems. Most jobs print +well, some do not print at all. Some jobs have problems with fonts, +which do not look very good. Some jobs print fast and some are dead-slow. Many of these problems can be greatly reduced or even completely eliminated if you follow a few guidelines. Remember, if your print device is not PostScript-enabled, you are treating your Ghostscript installation on your CUPS host with the output your client driver settings produce. Treat it well: -

Avoid the PostScript Output Option: Optimize -for Speed setting. Rather use the Optimize for -Portability instead (Adobe PostScript -driver).
Don't use the Page Independence: -NO setting. Instead use Page Independence -YES (CUPS PostScript Driver)
Recommended is the True Type Font -Downloading Option: Native True Type over -Automatic and Outline; you -should by all means avoid Bitmap (Adobe -PostScript Driver)
Choose True Type Font: Download as Softfont -into Printer over the default Replace by Device -Font (for exotic fonts you may need to change it back to -get a printout at all) (Adobe)
Sometimes you can choose PostScript Language -Level: in case of problems try 2 -instead of 3 (the latest ESP Ghostscript package -handles Level 3 PostScript very well) (Adobe).
Say Yes to PostScript -Error Handler (Adobe)

Installing PostScript Driver Files manually (using -rpcclient)

-Of course you can run all the commands which are embedded into the +

Avoid the PostScript Output Option: Optimize +for Speed setting. Use the Optimize for +Portability instead (Adobe PostScript +driver).
Don't use the Page Independence: +NO setting. Instead, use Page Independence +YES (CUPS PostScript Driver).
Recommended is the True Type Font +Downloading Option: Native True Type over +Automatic and Outline; you +should by all means avoid Bitmap (Adobe +PostScript Driver).
Choose True Type Font: Download as Softfont +into Printer over the default Replace by Device +Font (for exotic fonts, you may need to change it back to +get a printout at all) (Adobe).
Sometimes you can choose PostScript Language +Level: In case of problems try 2 +instead of 3 (the latest ESP Ghostscript package +handles Level 3 PostScript very well) (Adobe).
Say Yes to PostScript +Error Handler (Adobe).

Installing PostScript Driver Files Manually Using rpcclient

+Of course, you can run all the commands that are embedded into the cupsaddsmb convenience utility yourself, one by one, and hereby upload and prepare the driver files for future client downloads. -

prepare Samba (a CUPS printqueue with the name of the +
1. Prepare Samba (A CUPS print queue with the name of the printer should be there. We are providing the driver -now);
2. copy all files to - [print$]
3. - - run rpcclient adddriver -(for each client architecture you want to support):
4. - - run rpcclient +now).
5. Copy all files to + [print$].
6. + +Run rpcclient adddriver +(for each client architecture you want to support).
7. + +Run rpcclient setdriver.
- - - - - -We are going to do this now. First, read the man page on "rpcclient" + + + + + +We are going to do this now. First, read the man page on rpcclient to get a first idea. Look at all the printing related -sub-commands. enumprinters, +subcommands. enumprinters, enumdrivers, enumports, -adddriver, setdriver are amongst -the most interesting ones. rpcclient implements an important part of -the MS-RPC protocol. You can use it to query (and command) a Win NT -(or 2K/XP) PC too. MS-RPC is used by Windows clients, amongst other -things, to benefit from the "Point'n'Print" features. Samba can now -mimic this too. -
A Check of the rpcclient man Page
-First let's have a little check of the rpcclient man page. Here are +adddriver, setdriver are among +the most interesting ones. rpcclient implements an important part of +the MS-RPC protocol. You can use it to query (and command) a Windows NT +(or 200x/XP) PC, too. MS-RPC is used by Windows clients, among other +things, to benefit from the Point'n'Print features. Samba can now +mimic this as well. +
A Check of the rpcclient man Page
+ First let's check the rpcclient man page. Here are two relevant passages:
adddriver <arch> <config> Execute an -AddPrinterDriver() RPC to install the printer driver information on -the server. Note that the driver files should already exist in the -directory returned by getdriverdir. Possible +AddPrinterDriver() RPC to install the printer driver information on +the server. The driver files should already exist in the +directory returned by getdriverdir. Possible values for arch are the same as those for the -getdriverdir command. The +getdriverdir command. The config parameter is defined as follows:
```
 Long Printer Name:\
@@ -1882,70 +1955,72 @@ Help File Name:\
 Language Monitor Name:\
 Default Data Type:\
 Comma Separated list of Files
-
```
Any empty fields should be enter as the string "NULL".
Samba does not need to support the concept of Print Monitors +
Any empty fields should be enter as the string “NULL”.
Samba does not need to support the concept of Print Monitors since these only apply to local printers whose driver can make use of -a bi-directional link for communication. This field should be "NULL". +a bi-directional link for communication. This field should be “NULL”. On a remote NT print server, the Print Monitor for a driver must already be installed prior to adding the driver or else the RPC will -fail +fail.
setdriver <printername> <drivername> Execute a SetPrinter() command to update the printer driver associated with an installed printer. The printer driver must already be correctly installed on the print server. -
See also the enumprinters and enumdrivers commands for +
See also the enumprinters and enumdrivers commands for obtaining a list of installed printers and drivers. -
Understanding the rpcclient man page
+
Understanding the rpcclient man Page
The exact format isn't made too clear by the man page, since you have to deal with some parameters containing spaces. Here is a better description for it. We have line-broken the -command and indicated the breaks with "\". Usually you would type the +command and indicated the breaks with “\”. Usually you would type the command in one line without the linebreaks: -
- adddriver "Architecture" \ - "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\ - LanguageMonitorFile:DataType:ListOfFiles,Comma-separated" + +
+ adddriver "Architecture" \ + "LongPrinterName:DriverFile:DataFile:ConfigFile:HelpFile:\ + LanguageMonitorFile:DataType:ListOfFiles,Comma-separated"
-What the man pages denotes as a simple <config> -keyword, does in reality consist of 8 colon-separated fields. The -last field may take multiple (in some, very insane, cases, even -20 different additional files. This might sound confusing at first. -Note, that what the man pages names the "LongPrinterName" in -reality should rather be called the "Driver Name". You can name it +What the man pages denote as a simple <config> +keyword, in reality consists of eight colon-separated fields. The +last field may take multiple (in some very insane cases, even +20 different additional) files. This might sound confusing at first. +What the man pages names the “LongPrinterName” in +reality should be called the “Driver Name”. You can name it anything you want, as long as you use this name later in the -rpcclient ... setdriver command. For +rpcclient ... setdriver command. For practical reasons, many name the driver the same as the printer.
-True: it isn't simple at all. I hear you asking: -How do I know which files are "Driver -File", "Data File", "Config File", "Help File" and "Language -Monitor File" in each case? -- For an answer you may +It isn't simple at all. I hear you asking: +“How do I know which files are "Driver +File”, “Data File”, “Config File”, “Help File” and “Language +Monitor File" in each case?” For an answer, you may want to have a look at how a Windows NT box with a shared printer presents the files to us. Remember, that this whole procedure has -to be developed by the Samba Team by overhearing the traffic caused +to be developed by the Samba team by overhearing the traffic caused by Windows computers on the wire. We may as well turn to a Windows -box now, and access it from a UNIX workstation. We will query it +box now and access it from a UNIX workstation. We will query it with rpcclient to see what it tells us and -try to understand the man page more clearly which we've read just +try to understand the man page more clearly that we've read just now. -
Producing an Example by querying a Windows Box
- - +
Producing an Example by Querying a Windows Box
+ + We could run rpcclient with a getdriver or a getprinter -subcommand (in level 3 verbosity) against it. Just sit down at UNIX or -Linux workstation with the Samba utilities installed. Then type the +subcommand (in level 3 verbosity) against it. Just sit down at a UNIX or +Linux workstation with the Samba utilities installed, then type the following command:
```
-root# rpcclient -U'USERNAME%PASSWORD' NT-SERVER-NAME -c 'getdriver printername 3'
+root# rpcclient -U'user%secret' NT-SERVER -c 'getdriver printername 3'
 
```
-From the result it should become clear which is which. Here is an -example from my installation: -
-root# rpcclient -U'Danka%xxxx' W2KSERVER \ - -c'getdriver "DANKA InfoStream Virtual Printer" 3' - cmd = getdriver "DANKA InfoStream Virtual Printer" 3 +From the result it should become clear which is which. Here is an example from my installation: +
+ +
+root# rpcclient -U'Danka%xxxx' W200xSERVER \ + -c'getdriver "DANKA InfoStream Virtual Printer" 3' + cmd = getdriver "DANKA InfoStream Virtual Printer" 3 [Windows NT x86] Printer Driver Info 3: @@ -1970,77 +2045,82 @@ example from my installation:
Some printer drivers list additional files under the label -"Dependentfiles": these would go into the last field -ListOfFiles,Comma-separated. For the CUPS -PostScript drivers we don't need any (nor would we for the Adobe -PostScript driver): therefore the field will get a "NULL" entry. -
What is required for adddriver and setdriver to succeed
-From the manpage (and from the quoted output -of cupsaddsmb, above) it becomes clear that you +Dependentfiles and these would go into the last field +ListOfFiles,Comma-separated. For the CUPS +PostScript drivers, we do not need any (nor would we for the Adobe +PostScript driver), therefore, the field will get a “NULL” entry. +
Requirements for adddriver and setdriver to Succeed
+>From the man page (and from the quoted output +of cupsaddsmb above) it becomes clear that you need to have certain conditions in order to make the manual uploading -and initializing of the driver files succeed. The two rpcclient - +and initializing of the driver files succeed. The two rpcclient + subcommands (adddriver and setdriver) need to encounter the following -pre-conditions to complete successfully: -
- you are connected as printer admin, or root (note, -that this is not the "Printer Operators" group in -NT, but the printer admin group, as defined in +preconditions to complete successfully: +
  You are connected as printer admin or root (this is not the “Printer Operators” group in +NT, but the printer admin group as defined in the [global] section of -smb.conf);
  copy all required driver files to -\\sambaserver\print$\w32x86 and -\\sambaserver\print$\win40 as appropriate. They -will end up in the "0" respective "2" subdirectories later -- for now -don't put them there, they'll be automatically -used by the adddriver subcommand.! (if you use -"smbclient" to put the driver files into the share, note that you need -to escape the "$": smbclient //sambaserver/print\$ -U -root);
  the user you're connecting as must be able to write to +smb.conf).
  Copy all required driver files to +\\SAMBA\print$\w32x86 and +\\SAMBA\print$\win40 as appropriate. They +will end up in the “0” respective “2” subdirectories later. For now, +do not put them there, they'll be automatically +used by the adddriver subcommand. (If you use +smbclient to put the driver files into the share, note that you need +to escape the “$”: smbclient //sambaserver/print\$ -U +root.)
  The user you're connecting as must be able to write to the [print$] share and create -subdirectories;
  the printer you are going to setup for the Windows -clients, needs to be installed in CUPS already;
  - - - the CUPS printer must be known to Samba, otherwise the +subdirectories.
  The printer you are going to setup for the Windows +clients needs to be installed in CUPS already.
  + + + The CUPS printer must be known to Samba, otherwise the setdriver subcommand fails with an NT_STATUS_UNSUCCESSFUL error. To check if the printer is known by -Samba you may use the enumprinters subcommand to -rpcclient. A long-standing bug prevented a proper update of the +Samba, you may use the enumprinters subcommand to +rpcclient. A long-standing bug prevented a proper update of the printer list until every smbd process had received a SIGHUP or was restarted. Remember this in case you've created the CUPS printer just -shortly ago and encounter problems: try restarting -Samba.
Manual Driver Installation in 15 Steps
+recently and encounter problems: try restarting +Samba.

Manual Driver Installation in 15 Steps

We are going to install a printer driver now by manually executing all required commands. As this may seem a rather complicated process at first, we go through the procedure step by step, explaining every single action item as it comes up. -

Procedure 19.1. Manual Driver Installation installation

Install the Printer on CUPS

-root# lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E -P canonIR85.ppd
+
Procedure 19.1. Manual Driver Installation
Install the printer on CUPS.
+root# lpadmin -p mysmbtstprn -v socket://10.160.51.131:9100 -E \
+			-P canonIR85.ppd
 

-This installs printer with the name mysmbtstprn
+This installs a printer with the name mysmbtstprn
 to the CUPS system. The printer is accessed via a socket
 (a.k.a. JetDirect or Direct TCP/IP) connection. You need to be root
-for this step
-
(optional) Check if the Printer is recognized by
-Samba
-root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep -C2 mysmbtstprn
+for this step.
+
(Optional) Check if the printer is recognized by Samba.

+
+
+	root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost \
+  | grep -C2 mysmbtstprn
 flags:[0x800000]
 name:[\\kde-bitshop\mysmbtstprn]
 description:[\\kde-bitshop\mysmbtstprn,,mysmbtstprn]
 comment:[mysmbtstprn]
 

-This should show the printer in the list. If not, stop and re-start
-the Samba daemon (smbd), or send a HUP signal: kill -HUP
-`pidof smbd`. Check again.  Troubleshoot and repeat until
-success. Note the "empty" field between the two commas in the
-"description" line. Here would the driver name appear if there was one
-already. You need to know root's Samba password (as set by the
+This should show the printer in the list. If not, stop and restart
+the Samba daemon (smbd), or send a HUP signal: 
+
+root# kill -HUP `pidof smbd`
+
Check again. Troubleshoot and repeat until
+successful. Note the “empty” field between the two commas in the
+“description” line. The driver name would appear here if there was one already. You need to know root's Samba password (as set by the
 smbpasswd command) for this step and most of the
-following steps. Alternatively you can authenticate as one of the
-users from the "write list" as defined in smb.conf for
+following steps. Alternately, you can authenticate as one of the
+users from the “write list” as defined in smb.conf for
 [print$].
-
(optional) Check if Samba knows a Driver for the
-Printer
+
(Optional) Check if Samba knows a driver for the printer.

+	
+	
+	
 root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
 			| grep driver 
 drivername:[]
@@ -2061,13 +2141,13 @@ printprocessor:[winprint]
  result was WERR_UNKNOWN_PRINTER_DRIVER
 
 

-Neither method of the three commands shown above should show a driver.
+None of the three commands shown above should show a driver.
 This step was done for the purpose of demonstrating this condition. An
 attempt to connect to the printer at this stage will prompt the
-message along the lines: "The server has not the required printer
-driver installed".
-
Put all required Driver Files into Samba's
-[print$]
+message along the lines of: “The server does not have the required printer
+driver installed.”
+
Put all required driver files into Samba's
+[print$].
 root# smbclient //localhost/print\$ -U 'root%xxxx' \
 	-c 'cd W32X86; \
 	put /etc/cups/ppd/mysmbtstprn.ppd mysmbtstprn.PPD; \ 
@@ -2075,15 +2155,15 @@ driver installed".
 	put /usr/share/cups/drivers/cupsdrvr.dll cupsdrvr.dll; \
 	put /usr/share/cups/drivers/cups.hlp cups.hlp'
 

-(Note that this command should be entered in one long single
-line. Line-breaks and the line-end indicating "\" has been inserted
+(This command should be entered in one long single
+line. Line-breaks and the line-end indicated by “\” have been inserted
 for readability reasons.) This step is required
 for the next one to succeed. It makes the driver files physically
 present in the [print$] share. However, clients
 would still not be able to install them, because Samba does not yet
 treat them as driver files. A client asking for the driver would still
-be presented with a "not installed here" message.
-
Verify where the Driver Files are now
+be presented with a “not installed here” message.
+
Verify where the driver files are now.
 root# ls -l /etc/samba/drivers/W32X86/
 total 669
 drwxr-sr-x    2 root     ntadmin       532 May 25 23:08 2
@@ -2093,27 +2173,27 @@ drwxr-sr-x    2 root     ntadmin       670 May 16 03:15 3
 -rwxr--r--    1 root     ntadmin    215848 May 25 23:21 cupsui.dll
 -rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
 

-The driver files now are in the W32X86 architecture "root" of
+The driver files now are in the W32X86 architecture “root” of
 [print$].
-
Tell Samba that these are
-Driver Files
-(adddriver)
-root# rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" "mydrivername: \
-  cupsdrvr.dll:mysmbtstprn.PPD: \
-  cupsui.dll:cups.hlp:NULL:RAW:NULL" \
+
Tell Samba that these are driver files (adddriver).

+
+
+root# rpcclient -Uroot%xxxx -c `adddriver "Windows NT x86" \
+	"mydrivername:cupsdrvr.dll:mysmbtstprn.PPD: \
+  cupsui.dll:cups.hlp:NULL:RAW:NULL" \
   localhost
 Printer Driver mydrivername successfully installed.
 

-Note that your cannot repeat this step if it fails. It could fail even
+You cannot repeat this step if it fails. It could fail even
 as a result of a simple typo. It will most likely have moved a part of
-the driver files into the "2" subdirectory. If this step fails, you
-need to go back to the fourth step and repeat it, before you can try
-this one again. In this step you need to choose a name for your
+the driver files into the “2” subdirectory. If this step fails, you
+need to go back to the fourth step and repeat it before you can try
+this one again. In this step, you need to choose a name for your
 driver. It is normally a good idea to use the same name as is used for
-the printername; however, in big installations you may use this driver
-for a number of printers which have obviously different names. So the
+the printer name; however, in big installations you may use this driver
+for a number of printers that obviously have different names, so the
 name of the driver is not fixed.
-
Verify where the Driver Files are now
+
Verify where the driver files are now.
 root# ls -l /etc/samba/drivers/W32X86/
 total 1
 drwxr-sr-x    2 root     ntadmin       532 May 25 23:22 2
@@ -2127,12 +2207,13 @@ total 5039
 -rwxr--r--    1 root     ntadmin    215848 May 13 13:53 cupsui.dll
 -rwxr--r--    1 root     ntadmin    169458 May 25 23:21 mysmbtstprn.PPD
 

-Notice how step 6 did also move the driver files to the appropriate
-subdirectory. Compare with the situation after step 5.
-
(optional) Verify if Samba now recognizes the
-Driver
-root# rpcclient -Uroot%xxxx -c 'enumdrivers 3' localhost \
-	| grep -B2 -A5 mydrivername
+Notice how step 6 also moved the driver files to the appropriate
+subdirectory. Compare this with the situation after step 5.
+
(Optional) Verify if Samba now recognizes the driver.

+
+
+root# rpcclient -Uroot%xxxx -c 'enumdrivers 3' \
+	localhost | grep -B2 -A5 mydrivername
 Printer Driver Info 3:
 Version: [2]
 Driver Name: [mydrivername]
@@ -2142,21 +2223,26 @@ Datafile: [\\kde-bitshop\print$\W32X86\2\mysmbtstprn.PPD]
 Configfile: [\\kde-bitshop\print$\W32X86\2\cupsui.dll]
 Helpfile: [\\kde-bitshop\print$\W32X86\2\cups.hlp]
 

-Remember, this command greps for the name you did choose for the
-driver in step Six. This command must succeed before you can proceed.
-
Tell Samba which Printer should use these Driver
-Files (setdriver)
-root# rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' localhost
+Remember, this command greps for the name you chose for the
+driver in step 6. This command must succeed before you can proceed.
+
Tell Samba which printer should use these driver files (setdriver).

+
+
+root# rpcclient -Uroot%xxxx -c 'setdriver mysmbtstprn mydrivername' \
+	localhost
 Successfully set mysmbtstprn to driver mydrivername
 

-Since you can bind any printername (=printqueue) to any driver, this
-is a very convenient way to setup many queues which use the same
-driver. You don't need to repeat all the previous steps for the
-setdriver command to succeed. The only pre-conditions are:
+Since you can bind any printername (print queue) to any driver, this
+is a convenient way to setup many queues that use the same
+driver. You do not need to repeat all the previous steps for the
+setdriver command to succeed. The only preconditions are:
 enumdrivers must find the driver and
 enumprinters must find the printer.
-
(optional) Verify if Samba has this Association
-recognized
+
(Optional) Verify if Samba has recognized this association.

+
+
+
+
 root# rpcclient -Uroot%xxxx -c 'getprinter mysmbtstprn 2' localhost \
   | grep driver
 drivername:[mydrivername]
@@ -2188,169 +2274,174 @@ Printer Driver Info 3:
      Monitorname: []
      Defaultdatatype: [RAW]
  
-root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost | grep mysmbtstprn
+root# rpcclient -Uroot%xxxx -c 'enumprinters' localhost \
+	| grep mysmbtstprn
      name:[\\kde-bitshop\mysmbtstprn]
      description:[\\kde-bitshop\mysmbtstprn,mydrivername,mysmbtstprn]
      comment:[mysmbtstprn]
 
 

-
-Compare these results with the ones from steps 2 and 3. Note that
-every single of these commands show the driver is installed.  Even
+
+Compare these results with the ones from steps 2 and 3. Every one of these commands show the driver is installed. Even
 the enumprinters command now lists the driver
-on the "description" line.
-
(optional) Tickle the Driver into a correct
-Device Mode

-
-You certainly know how to install the driver on the client.  In case
+on the “description” line.
+
(Optional) Tickle the driver into a correct
+device mode.

+
+You certainly know how to install the driver on the client. In case
 you are not particularly familiar with Windows, here is a short
-recipe: browse the Network Neighbourhood, go to the Samba server, look
+recipe: Browse the Network Neighborhood, go to the Samba server, and look
 for the shares. You should see all shared Samba printers.
 Double-click on the one in question. The driver should get
-installed, and the network connection set up. An alternative way is to
-open the "Printers (and Faxes)" folder, right-click on the printer in
-question and select "Connect" or "Install". As a result, a new printer
-should have appeared in your client's local "Printers (and Faxes)"
-folder, named something like "printersharename on Sambahostname".
+installed and the network connection set up. An alternate way is to
+open the Printers (and Faxes) folder, right-click on the printer in
+question and select Connect or Install. As a result, a new printer
+should have appeared in your client's local Printers (and Faxes)
+folder, named something like printersharename on Sambahostname.
 

 It is important that you execute this step as a Samba printer admin
 (as defined in smb.conf). Here is another method
-to do this on Windows XP. It uses a commandline, which you may type
-into the "DOS box" (type root's smbpassword when prompted):
+to do this on Windows XP. It uses a command line, which you may type
+into the “DOS box” (type root's smbpassword when prompted):
 
-C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry /in /n\
-			\\sambacupsserver\mysmbtstprn"
+C:\> runas /netonly /user:root "rundll32 printui.dll,PrintUIEntry \
+	/in /n \\sambaserver\mysmbtstprn"
 

-Change any printer setting once (like changing "portrait" to
-	"landscape"), click Apply; change the setting
+Change any printer setting once (like changing portrait to
+	landscape), click on Apply; change the setting
 back.
-
Install the Printer on a Client
-("Point'n'Print")
-C:\> rundll32 printui.dll,PrintUIEntry /in /n "\\sambacupsserver\mysmbtstprn"
+
Install the printer on a client
+(Point'n'Print).

+
+	
+C:\> rundll32 printui.dll,PrintUIEntry /in /n “\\sambaserver\mysmbtstprn”
 

-If it doesn't work it could be a permission problem with the
+If it does not work it could be a permission problem with the
 [print$] share.
-
Thirteenth Step (optional): Print a Test Page
-C:\> rundll32 printui.dll,PrintUIEntry /p /n "\\sambacupsserver\mysmbtstprn"
+
(Optional) Print a test page.
+C:\> rundll32 printui.dll,PrintUIEntry /p /n "\\sambaserver\mysmbtstprn"
 

-Then hit [TAB] 5 times, [ENTER] twice, [TAB] once and [ENTER] again
+Then hit [TAB] five times, [ENTER] twice, [TAB] once and [ENTER] again
 and march to the printer.
-
Fourteenth Step (recommended): Study the Test Page

+
(Recommended) Study the test page.

 Hmmm.... just kidding! By now you know everything about printer
-installations and you don't need to read a word. Just put it in a
-frame and bolt it to the wall with the heading "MY FIRST
-RPCCLIENT-INSTALLED PRINTER" - why not just throw it away!
-
Fifteenth Step (obligatory): Enjoy. Jump. Celebrate your
-Success
-root# echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd
-

`Troubleshooting revisited`

+installations and you do not need to read a word. Just put it in a +frame and bolt it to the wall with the heading "MY FIRST +RPCCLIENT-INSTALLED PRINTER" why not just throw it away! +

(Obligatory) Enjoy. Jump. Celebrate your +success.

+root# echo "Cheeeeerioooooo! Success..." >> /var/log/samba/log.smbd
+

`Troubleshooting Revisited`

The setdriver command will fail, if in Samba's mind the queue is not already there. You had promising messages about the:

-
  Printer Driver ABC successfully installed.
-

-after the "adddriver" parts of the procedure? But you are also seeing -a disappointing message like this one beneath? -

-
+after the adddriver parts of the procedure?  But you are also seeing
+a disappointing message like this one?
+

  result was NT_STATUS_UNSUCCESSFUL
-
-

- +

+ It is not good enough that you -can see the queue in CUPS, using +can see the queue in CUPS, using the lpstat -p ir85wm command. A bug in most recent versions of Samba prevents the proper update of the queuelist. The recognition of newly installed CUPS printers -fails unless you re-start Samba or send a HUP to all smbd -processes. To verify if this is the reason why Samba doesn't -execute the setdriver command successfully, check if Samba "sees" +fails unless you restart Samba or send a HUP to all smbd +processes. To verify if this is the reason why Samba does not +execute the setdriver command successfully, check if Samba “sees” the printer: -

-root# rpcclient transmeta -N -U'root%secret' -c 'enumprinters 0'| grep ir85wm + + + +root# rpcclient transmeta -N -U'root%xxxx' -c 'enumprinters 0'|grep ir85wm printername:[ir85wm] -An alternative command could be this: - +An alternate command could be this: + + + root# rpcclient transmeta -N -U'root%secret' -c 'getprinter ir85wm' cmd = getprinter ir85wm flags:[0x800000] name:[\\transmeta\ir85wm] description:[\\transmeta\ir85wm,ir85wm,DPD] - comment:[CUPS PostScript-Treiber for WinNT/2K/XP] + comment:[CUPS PostScript-Treiber for Windows NT/200x/XP] -BTW, you can use these commands, plus a few more, of course, +By the way, you can use these commands, plus a few more, of course, to install drivers on remote Windows NT print servers too! -

**`The printing *.tdb Files`**

- - - - - - - - - - - - - +

**`The Printing *.tdb Files`**

+ + + + + + + + + + + + + Some mystery is associated with the series of files with a -tdb-suffix appearing in every Samba installation. They are +tdb suffix appearing in every Samba installation. They are connections.tdb, printing.tdb, -share_info.tdb , +share_info.tdb, ntdrivers.tdb, unexpected.tdb, -brlock.tdb , +brlock.tdb, locking.tdb, ntforms.tdb, messages.tdb , ntprinters.tdb, sessionid.tdb and secrets.tdb. What is their purpose? -

`Trivial DataBase Files`

-A Windows NT (Print) Server keeps track of all information needed to serve + Trivial Database Files + +A Windows NT (print) server keeps track of all information needed to serve its duty toward its clients by storing entries in the Windows -"Registry". Client queries are answered by reading from the registry, -Administrator or user configuration settings are saved by writing into -the Registry. Samba and UNIX obviously don't have such a kind of +registry. Client queries are answered by reading from the registry, +Administrator or user configuration settings that are saved by writing into +the registry. Samba and UNIX obviously do not have such a Registry. Samba instead keeps track of all client related information in a series of *.tdb files. (TDB = Trivial Data Base). These are often located in /var/lib/samba/ -or /var/lock/samba/ . The printing related files +or /var/lock/samba/. The printing related files are ntprinters.tdb, printing.tdb,ntforms.tdb and ntdrivers.tdb. - Binary Format + Binary Format *.tdb files are not human readable. They are -written in a binary format. "Why not ASCII?", you may ask. "After all, -ASCII configuration files are a good and proofed tradition on UNIX." --- The reason for this design decision by the Samba Team is mainly +written in a binary format. “Why not ASCII?”, you may ask. “After all, +ASCII configuration files are a good and proven tradition on UNIX.” +The reason for this design decision by the Samba team is mainly performance. Samba needs to be fast; it runs a separate smbd process for each client connection, in some -environments many thousand of them. Some of these smbds might need to +environments many thousands of them. Some of these smbds might need to write-access the same *.tdb file at the same time. The file format of Samba's *.tdb files allows for this provision. Many smbd processes may write to the same *.tdb file at the same time. This wouldn't be possible with pure ASCII files. - Losing *.tdb Files + Losing *.tdb Files It is very important that all *.tdb files remain consistent over all write and read accesses. However, it may happen that these files do get corrupted. (A -kill -9 `pidof smbd` while a write access is in +kill -9 `pidof smbd' while a write access is in progress could do the damage as well as a power interruption, etc.). In cases of trouble, a deletion of the old printing-related -*.tdb files may be the only option. You need to -re-create all print related setup after that. Or you have made a +*.tdb files may be the only option. After that you need to +re-create all print-related setup or you have made a backup of the *.tdb files in time. - Using tdbbackup -Samba ships with a little utility which helps the root user of your -system to back up your *.tdb files. If you run it -with no argument, it prints a little usage message: + Using tdbbackup + + +Samba ships with a little utility that helps the root user of your +system to backup your *.tdb files. If you run it +with no argument, it prints a usage message: root# tdbbackup Usage: tdbbackup [options] <fname...> @@ -2361,12 +2452,12 @@ with no argument, it prints a little usage message: -v verify mode (restore if corrupt) -Here is how I backed up my printing.tdb file: +Here is how I backed up my printing.tdb file: root# ls -. browse.dat locking.tdb ntdrivers.tdb printing.tdb -.. share_info.tdb connections.tdb messages.tdb ntforms.tdb -printing.tdbkp unexpected.tdb brlock.tdb gmon.out namelist.debug +. browse.dat locking.tdb ntdrivers.tdb printing.tdb +.. share_info.tdb connections.tdb messages.tdb ntforms.tdb +printing.tdbkp unexpected.tdb brlock.tdb gmon.out namelist.debug ntprinters.tdb sessionid.tdb root# tdbbackup -s .bak printing.tdb @@ -2376,850 +2467,845 @@ ntprinters.tdb sessionid.tdb -rw------- 1 root root 40960 May 2 03:44 printing.tdb -rw------- 1 root root 40960 May 2 03:44 printing.tdb.bak -

`CUPS Print Drivers from Linuxprinting.org`

-CUPS ships with good support for HP LaserJet type printers. You can +

`CUPS Print Drivers from Linuxprinting.org`

+ +CUPS ships with good support for HP LaserJet-type printers. You can install the generic driver as follows: -

+ + + root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -m laserjet.ppd The -m switch will retrieve the laserjet.ppd from the standard repository for not-yet-installed-PPDs, which CUPS typically stores in -/usr/share/cups/model. Alternatively, you may use +/usr/share/cups/model. Alternately, you may use -P /path/to/your.ppd. -The generic laserjet.ppd however does not support every special option -for every LaserJet-compatible model. It constitutes a sort of "least -denominator" of all the models. If for some reason it is ruled out to -you to pay for the commercially available ESP Print Pro drivers, your -first move should be to consult the database on http://www.linuxprinting.org/printer_list.cgi. +The generic laserjet.ppd, however, does not support every special option +for every LaserJet-compatible model. It constitutes a sort of “least common +denominator” of all the models. If for some reason +you must pay for the commercially available ESP Print Pro drivers, your +first move should be to consult the database on http://www.linuxprinting.org/printer_list.cgi. Linuxprinting.org has excellent recommendations about which driver is best used for each printer. Its database is kept current by the tireless work of Till Kamppeter from MandrakeSoft, who is also the -principal author of the foomatic-rip utility. +principal author of the foomatic-rip utility. Note - -The former "cupsomatic" concept is now be replaced by the new, much -more powerful "foomatic-rip". foomatic-rip is the successor of -cupsomatic. cupsomatic is no longer maintained. Here is the new URL -to the Foomatic-3.0 database:http://www.linuxprinting.org/driver_list.cgi. -If you upgrade to foomatic-rip, don't forget to also upgrade to the -new-style PPDs for your foomatic-driven printers. foomatic-rip will -not work with PPDs generated for the old cupsomatic. The new-style + +The former cupsomatic concept is now being replaced by the new +successor, a much +more powerful foomatic-rip. +cupsomatic is no longer maintained. Here is the new URL +to the Foomatic-3.0 database: http://www.linuxprinting.org/driver_list.cgi. +If you upgrade to foomatic-rip, remember to also upgrade to the +new-style PPDs for your Foomatic-driven printers. foomatic-rip will +not work with PPDs generated for the old cupsomatic. The new-style PPDs are 100% compliant to the Adobe PPD specification. They are -intended to be used by Samba and the cupsaddsmb utility also, to -provide the driver files for the Windows clients also! - foomatic-rip and Foomatic explained -Nowadays most Linux distros rely on the utilities of Linuxprinting.org -to create their printing related software (which, BTW, works on all -UNIXes and on Mac OS X or Darwin too). It is not known as well as it -should be, that it also has a very end-user friendly interface which -allows for an easy update of drivers and PPDs, for all supported -models, all spoolers, all operating systems and all package formats +also intended to be used by Samba and the cupsaddsmb utility, to +provide the driver files for the Windows clients! + foomatic-rip and Foomatic Explained + + +Nowadays, most Linux distributions rely on the utilities of Linuxprinting.org +to create their printing-related software (which, by the way, works on all +UNIXes and on Mac OS X or Darwin, too). It is not known as well as it +should be, that it also has a very end-user-friendly interface that +allows for an easy update of drivers and PPDs for all supported +models, all spoolers, all operating systems, and all package formats (because there is none). Its history goes back a few years. -Recently Foomatic has achieved the astonishing milestone of 1000 -listed printer models. Linuxprinting.org keeps all the +Recently, Foomatic has achieved the astonishing milestone of 1000 +listed printer models. Linuxprinting.org keeps all the important facts about printer drivers, supported models and which options are available for the various driver/printer combinations in -its Foomatic -database. Currently there are 245 drivers -in the database: many drivers support various models, and many models -may be driven by different drivers; it's your choice! - 690 "perfect" Printers -At present there are 690 devices dubbed as working "perfectly", 181 -"mostly", 96 "partially" and 46 are "Paperweights". Keeping in mind +its Foomatic +database. Currently there are 245 drivers +in the database. Many drivers support various models, and many models +may be driven by different drivers its your choice! + 690 “Perfect” Printers +At present, there are 690 devices dubbed as working perfectly, 181 +mostly, 96 partially, and 46 are paperweights. Keeping in mind that most of these are non-PostScript models (PostScript printers are -automatically supported supported by CUPS to perfection, by using -their own manufacturer-provided Windows-PPD...), and that a -multifunctional device never qualifies as working "perfectly" if it -doesn't also scan and copy and fax under GNU/Linux: then this is a -truly astonishing achievement. Three years ago the number was not -more than 500, and Linux or UNIX "printing" at the time wasn't -anywhere near the quality it is today! - How the "Printing HOWTO" started it all -A few years ago Grant Taylor +automatically supported by CUPS to perfection, by using +their own manufacturer-provided Windows-PPD), and that a +multifunctional device never qualifies as working perfectly if it +does not also scan and copy and fax under GNU/Linux then this is a +truly astonishing achievement! Three years ago the number was not +more than 500, and Linux or UNIX printing at the time wasn't +anywhere near the quality it is today. + How the Printing HOWTO Started It All +A few years ago Grant Taylor started it all. The roots of today's Linuxprinting.org are in the -first Linux Printing -HOWTO which he authored. As a side-project to this document, +first Linux Printing +HOWTO that he authored. As a side-project to this document, which served many Linux users and admins to guide their first steps in this complicated and delicate setup (to a scientist, printing is -"applying a structured deposition of distinct patterns of ink or toner -particles on paper substrates" ;-), he started to +“applying a structured deposition of distinct patterns of ink or toner +particles on paper substrates”, he started to build in a little Postgres database with information about the hardware and driver zoo that made up Linux printing of the time. This database became the core component of today's Foomatic collection of -tools and data. In the meantime it has moved to an XML representation +tools and data. In the meantime, it has moved to an XML representation of the data. - Foomatic's strange Name -"Why the funny name?", you ask. When it really took off, around spring + Foomatic's Strange Name + +“Why the funny name?” you ask. When it really took off, around spring 2000, CUPS was far less popular than today, and most systems used LPD, -LPRng or even PDQ to print. CUPS shipped with a few generic "drivers" +LPRng or even PDQ to print. CUPS shipped with a few generic drivers (good for a few hundred different printer models). These didn't support many device-specific options. CUPS also shipped with its own -built-in rasterization filter ("pstoraster", derived from +built-in rasterization filter (pstoraster, derived from Ghostscript). On the other hand, CUPS provided brilliant support for controlling all printer options through -standardized and well-defined "PPD files" (PostScript Printers +standardized and well-defined PPD files (PostScript Printers Description files). Plus, CUPS was designed to be easily extensible. -Grant already had in his database a respectable compilation -of facts about a many more printers, and the Ghostscript "drivers" -they run with. His idea, to generate PPDs from the database info +Taylor already had in his database a respectable compilation +of facts about many more printers and the Ghostscript “drivers” +they run with. His idea, to generate PPDs from the database information and use them to make standard Ghostscript filters work within CUPS, -proved to work very well. It also "killed several birds with one -stone": +proved to work very well. It also killed several birds with one +stone: It made all current and future Ghostscript filter -developments available for CUPS; It made available a lot of additional printer models -to CUPS users (because often the "traditional" Ghostscript way of -printing was the only one available); It gave all the advanced CUPS options (web interface, +developments available for CUPS. It made available a lot of additional printer models +to CUPS users (because often the traditional Ghostscript way of +printing was the only one available). It gave all the advanced CUPS options (Web interface, GUI driver configurations) to users wanting (or needing) to use -Ghostscript filters. cupsomatic, pdqomatic, lpdomatic, directomatic -CUPS worked through a quickly-hacked up filter script named cupsomatic. +Ghostscript filters. cupsomatic, pdqomatic, lpdomatic, directomatic + + + +CUPS worked through a quickly-hacked up filter script named cupsomatic. cupsomatic ran the printfile through Ghostscript, constructing automatically the rather complicated command line needed. It just -required to be copied into the CUPS system to make it work. To -"configure" the way cupsomatic controls the Ghostscript rendering +needed to be copied into the CUPS system to make it work. To +configure the way cupsomatic controls the Ghostscript rendering process, it needs a CUPS-PPD. This PPD is generated directly from the contents of the database. For CUPS and the respective printer/filter -combo another Perl script named "CUPS-O-Matic" did the PPD -generation. After that was working, Grant implemented within a few +combo, another Perl script named CUPS-O-Matic did the PPD +generation. After that was working, Taylor implemented within a few days a similar thing for two other spoolers. Names chosen for the -config-generator scripts were PDQ-O-Matic -(for PDQ) and LPD-O-Matic -(for - you guessed it - LPD); the configuration here didn't use PPDs +config-generator scripts were PDQ-O-Matic +(for PDQ) and LPD-O-Matic +(for you guessed it LPD); the configuration here didn't use PPDs but other spooler-specific files. -From late summer of that year, Till Kamppeter -started to put work into the database. Till had been newly employed by -MandrakeSoft to -convert their printing system over to CUPS, after they had seen his -FLTK-based XPP (a GUI frontend to +From late summer of that year, Till Kamppeter +started to put work into the database. Kamppeter had been newly employed by +MandrakeSoft to +convert its printing system over to CUPS, after they had seen his +FLTK-based XPP (a GUI frontend to the CUPS lp-command). He added a huge amount of new information and new printers. He also developed the support for other spoolers, like -PPR (via ppromatic), -GNUlpr and -LPRng (both via an extended -lpdomatic) and "spoolerless" printing (directomatic).... - -So, to answer your question: "Foomatic" is the general name for all -the overlapping code and data behind the "*omatic" scripts.... -- -Foomatic up to versions 2.0.x required (ugly) Perl data structures -attached the Linuxprinting.org PPDs for CUPS. It had a different -"*omatic" script for every spooler, as well as different printer -configuration files.. - The Grand Unification -achieved... -This all has changed in Foomatic versions 2.9 (Beta) and released as -"stable" 3.0. This has now achieved the convergence of all *omatic -scripts: it is called the foomatic-rip. +PPR (via ppromatic), +GNUlpr and +LPRng (both via an extended +lpdomatic) and spoolerless printing (directomatic). + +So, to answer your question: “Foomatic” is the general name for all +the overlapping code and data behind the “*omatic” scripts. +Foomatic, up to versions 2.0.x, required (ugly) Perl data structures +attached to Linuxprinting.org PPDs for CUPS. It had a different +“*omatic” script for every spooler, as well as different printer +configuration files. + The Grand Unification Achieved + +This has all changed in Foomatic versions 2.9 (beta) and released as +“stable” 3.0. It has now achieved the convergence of all *omatic +scripts and is called the foomatic-rip. This single script is the unification of the previously different spooler-specific *omatic scripts. foomatic-rip is used by all the -different spoolers alike. Because foomatic-rip can read PPDs (both the +different spoolers alike and because it can read PPDs (both the original PostScript printer PPDs and the Linuxprinting.org-generated ones), all of a sudden all supported spoolers can have the power of -PPDs at their disposal; users only need to plug "foomatic-rip" into -their system.... For users there is improved media type and source -support; paper sizes and trays are easier to configure. +PPDs at their disposal. Users only need to plug foomatic-rip into +their system. For users there is improved media type and source +support paper sizes and trays are easier to configure. -Also, the New Generation of Linuxprinting.org PPDs doesn't contain -Perl data structures any more. If you are a distro maintainer and have +Also, the New Generation of Linuxprinting.org PPDs no longer contains +Perl data structures. If you are a distro maintainer and have used the previous version of Foomatic, you may want to give the new -one a spin: but don't forget to generate a new-version set of PPDs, -via the new foomatic-db-engine! +one a spin, but remember to generate a new-version set of PPDs +via the new foomatic-db-engine! Individual users just need to generate a single new PPD specific to -their model by following -the steps outlined in the Foomatic tutorial or further -below. This new development is truly amazing. +their model by following +the steps outlined in the Foomatic tutorial or in this chapter. This new development is truly amazing. foomatic-rip is a very clever wrapper around the need to run -Ghostscript with a different syntax, different options, different -device selections and/or different filters for each different printer -or different spooler. At the same time it can read the PPD associated +Ghostscript with a different syntax, options, device selections, and/or filters for each different printer +or spooler. At the same time it can read the PPD associated with a print queue and modify the print job according to the user selections. Together with this comes the 100% compliance of the new -Foomatic PPDs with the Adobe spec. Some really innovative features of -the Foomatic concept will surprise users: it will support custom paper -sizes for many printers; and it will support printing on media drawn -from different paper trays within the same job (in both cases: even +Foomatic PPDs with the Adobe spec. Some innovative features of +the Foomatic concept may surprise users. It will support custom paper +sizes for many printers and will support printing on media drawn +from different paper trays within the same job (in both cases, even where there is no support for this from Windows-based vendor printer drivers). - Driver Development outside + Driver Development Outside Most driver development itself does not happen within Linuxprinting.org. Drivers are written by independent maintainers. -Linuxprinting.org just pools all the information, and stores it in its +Linuxprinting.org just pools all the information and stores it in its database. In addition, it also provides the Foomatic glue to integrate the many drivers into any modern (or legacy) printing system known to the world. -Speaking of the different driver development groups: most of +Speaking of the different driver development groups, most of the work is currently done in three projects. These are: - Omni --- a Free Software project by IBM which tries to convert their printer + Omni + a free software project by IBM that tries to convert their printer driver knowledge from good-ol' OS/2 times into a modern, modular, -universal driver architecture for Linux/UNIX (still Beta). This -currently supports 437 models. HPIJS -- -a Free Software project by HP to provide the support for their own +universal driver architecture for Linux/UNIX (still beta). This +currently supports 437 models. HPIJS +a free software project by HP to provide the support for their own range of models (very mature, printing in most cases is perfect and provides true photo quality). This currently supports 369 -models. Gimp-Print -- a Free software +models. Gimp-Print a free software effort, started by Michael Sweet (also lead developer for CUPS), now directed by Robert Krawitz, which has achieved an amazing level of photo print quality (many Epson users swear that its quality is better than the vendor drivers provided by Epson for the Microsoft -platforms). This currently supports 522 models. Forums, Downloads, Tutorials, Howtos -- also for Mac OS X and -commercial UNIX -Linuxprinting.org today is the one-stop "shop" to download printer -drivers. Look for printer information and tutorials -or solve printing problems in its popular forums. But -it's not just for GNU/Linux: users and admins of commercial UNIX -systems are also going there, and the relatively new Mac -OS X forum has turned out to be one of the most frequented -fora after only a few weeks. +platforms). This currently supports 522 models. Forums, Downloads, Tutorials, Howtos also for Mac OS X and Commercial UNIX +Linuxprinting.org today is the one-stop shop to download printer +drivers. Look for printer information and tutorials +or solve printing problems in its popular forums. This forum +it's not just for GNU/Linux users, but admins of commercial UNIX +systems are also going there, and the relatively new Mac +OS X forum has turned out to be one of the most frequented +forums after only a few weeks. Linuxprinting.org and the Foomatic driver wrappers around Ghostscript are now a standard toolchain for printing on all the important distros. Most of them also have CUPS underneath. While in recent years -most printer data had been added by Till (who works at Mandrake), many +most printer data had been added by Kamppeter (who works at Mandrake), many additional contributions came from engineers with SuSE, RedHat, -Connectiva, Debian and others. Vendor-neutrality is an important goal +Connectiva, Debian, and others. Vendor-neutrality is an important goal of the Foomatic project. Note Till Kamppeter from MandrakeSoft is doing an excellent job in his spare time to maintain Linuxprinting.org and Foomatic. So if you use it often, please send him a note showing your appreciation. - Foomatic Database generated PPDs + Foomatic Database-Generated PPDs The Foomatic database is an amazing piece of ingenuity in itself. Not only does it keep the printer and driver information, but it is -organized in a way that it can generate "PPD" files "on the fly" from +organized in a way that it can generate PPD files on the fly from its internal XML-based datasets. While these PPDs are modelled to the -Adobe specification of "PostScript Printer Descriptions" (PPDs), the -Linuxprinting.org/Foomatic-PPDs don't normally drive PostScript -printers: they are used to describe all the bells and whistles you -could ring or blow on an Epson Stylus inkjet, or a HP Photosmart or -what-have-you. The main "trick" is one little additional line, not -envisaged by the PPD specification, starting with the "*cupsFilter" -keyword: it tells the CUPS daemon how to proceed with the PostScript +Adobe specification of PostScript Printer Descriptions (PPDs), the +Linuxprinting.org/Foomatic-PPDs do not normally drive PostScript +printers. They are used to describe all the bells and whistles you +could ring or blow on an Epson Stylus inkjet, or a HP Photosmart, or +what-have-you. The main trick is one little additional line, not +envisaged by the PPD specification, starting with the *cupsFilter +keyword. It tells the CUPS daemon how to proceed with the PostScript print file (old-style Foomatic-PPDs named the -cupsomatic filter script, while the new-style -PPDs now call foomatic-rip). This filter +cupsomatic filter script, while the new-style +PPDs are now call foomatic-rip). This filter script calls Ghostscript on the host system (the recommended variant is ESP Ghostscript) to do the rendering work. foomatic-rip knows which filter or internal device setting it should ask from Ghostscript to convert the PostScript printjob into a raster format ready for the target device. This usage of PPDs to describe the options of non-PS -printers was the invention of the CUPS developers. The rest is easy: -GUI tools (like KDE's marvellous "kprinter", -or the GNOME "gtklp", "xpp" and the CUPS -web interface) read the PPD too and use this information to present +printers was the invention of the CUPS developers. The rest is easy. +GUI tools (like KDE's marvelous kprinter, +or the GNOME gtklp, xpp and the CUPS +Web interface) read the PPD as well and use this information to present the available settings to the user as an intuitive menu selection. -

`foomatic-rip and Foomatic-PPD Download and Installation`

-Here are the steps to install a foomatic-rip driven "LaserJet 4 Plus" -compatible printer in CUPS (note that recent distributions of SuSE, -UnitedLinux and Mandrake may ship with a complete package of -Foomatic-PPDs plus the foomatic-rip utility. going directly to -Linuxprinting.org ensures you to get the latest driver/PPD files): -

Surf to http://www.linuxprinting.org/printer_list.cgi -
Check the complete list of printers in the database: -http://www.linuxprinting.org/printer_list.cgi?make=Anyone -
There select your model and click on the -link.
You'll arrive at a page listing all drivers working -with this model (for all printers, there will always be -one recommended driver. Try this one -first).
In our case ("HP LaserJet 4 Plus"), we'll arrive here: - http://www.linuxprinting.org/show_printer.cgi?recnum=HP-LaserJet_4_Plus -
The recommended driver is "ljet4".
There are several links provided here. You should -visit them all, if you are not familiar with the Linuxprinting.org -database.
There is a link to the database page for the "ljet4": - http://www.linuxprinting.org/show_driver.cgi?driver=ljet4 +

`foomatic-rip and Foomatic-PPD Download and Installation`

+Here are the steps to install a foomatic-rip driven LaserJet 4 Plus-compatible +printer in CUPS (note that recent distributions of SuSE, UnitedLinux and +Mandrake may ship with a complete package of Foomatic-PPDs plus the +foomatic-rip utility. Going directly to +Linuxprinting.org ensures that you get the latest driver/PPD files): +

Open your browser at the Linuxprinting.org printer listpage. +
Check the complete list of printers in the +database.. +
Select your model and click on the link. +
You'll arrive at a page listing all drivers working with this +model (for all printers, there will always be one +recommended driver. Try this one first). +
In our case (HP LaserJet 4 Plus), we'll arrive at the default driver for the +HP-LaserJet 4 Plus. +
The recommended driver is ljet4.
Several links are provided here. You should visit them all if you +are not familiar with the Linuxprinting.org database. +
There is a link to the database page for the +ljet4. On the driver's page, you'll find important and detailed information about how to use that driver within the various available spoolers.
Another link may lead you to the homepage of the -driver author or the driver.
Important links are the ones which provide hints with -setup instructions for CUPS (http://www.linuxprinting.org/cups-doc.html), -PDQ (http://www.linuxprinting.org/pdq-doc.html), -LPD, LPRng and GNUlpr (http://www.linuxprinting.org/lpd-doc.html) -as well as PPR (http://www.linuxprinting.org/ppr-doc.html) -or "spooler-less" printing (http://www.linuxprinting.org/direct-doc.html -).
You can view the PPD in your browser through this -link: http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=1 -
You can also (most importantly) -generate and download the PPD: http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=0 +driver author or the driver.
Important links are the ones that provide hints with +setup instructions for CUPS, +PDQ, +LPD, LPRng and GNUlpr) +as well as PPR +or “spooler-less” printing. +
You can view the PPD in your browser through this link: +http://www.linuxprinting.org/ppd-o-matic.cgi?driver=ljet4&printer=HP-LaserJet_4_Plus&show=1 +
Most importantly, you can also generate and download +the PPD.
The PPD contains all the information needed to use our -model and the driver; this is, once installed, working transparently -for the user. Later you'll only need to choose resolution, paper size -etc. from the web-based menu, or from the print dialog GUI, or from -the commandline.
Should you have ended up on the driver's page (http://www.linuxprinting.org/show_driver.cgi?driver=ljet4), -you can choose to use the "PPD-O-Matic" online PPD generator -program.
Select the exact model and check either "download" or -"display PPD file" and click on "Generate PPD file".
If you save the PPD file from the browser view, please -don't use "cut'n'past" (since it could possibly damage line endings -and tabs, which makes the PPD likely to fail its duty), but use "Save -as..." in your browser's menu. (Best is to use the "download" option -from the web page directly).
Another very interesting part on each driver page is -the Show execution details button. If you -select your printer model and click that button, you will get -displayed a complete Ghostscript command line, enumerating all options -available for that driver/printermodel combo. This is a great way to -"Learn Ghostscript By Doing". It is also an excellent "cheat sheet" +model and the driver; once installed, this works transparently +for the user. Later you'll only need to choose resolution, paper size, +and so on from the Web-based menu, or from the print dialog GUI, or from +the command line.
If you ended up on the drivers +page +you can choose to use the “PPD-O-Matic” online PPD generator +program.
Select the exact model and check either Download or +Display PPD file and click Generate PPD file.
If you save the PPD file from the browser view, please +do not use cut and paste (since it could possibly damage line endings +and tabs, which makes the PPD likely to fail its duty), but use Save +as... in your browser's menu. (It is best to use the Download option +directly from the Web page).
Another interesting part on each driver page is +the Show execution details button. If you +select your printer model and click on that button, +a complete Ghostscript command line will be displayed, enumerating all options +available for that combination of driver and printer model. This is a great way to +“learn Ghostscript by doing”. It is also an excellent cheat sheet for all experienced users who need to re-construct a good command line for that damn printing script, but can't remember the exact -syntax. ;-)
Some time during your visit to Linuxprinting.org, save +syntax.
Some time during your visit to Linuxprinting.org, save the PPD to a suitable place on your harddisk, say /path/to/my-printer.ppd (if you prefer to install -your printers with the help of the CUPS web interface, save the PPD to -the /usr/share/cups/model/ path and re-start -cupsd).
Then install the printer with a suitable commandline, -e.g.: +your printers with the help of the CUPS Web interface, save the PPD to +the /usr/share/cups/model/ path and restart +cupsd).

Then install the printer with a suitable command line, +like this:

-root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E -P path/to/my-printer.ppd
-

Note again this: for all the new-style "Foomatic-PPDs" -from Linuxprinting.org, you also need a special "CUPS filter" named -"foomatic-rip".Get the latest version of "foomatic-rip" from: http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=0 +root# lpadmin -p laserjet4plus -v parallel:/dev/lp0 -E \ + -P path/to/my-printer.ppd +
For all the new-style “Foomatic-PPDs” +from Linuxprinting.org, you also need a special CUPS filter named +foomatic-rip.
The foomatic-rip Perlscript itself also makes some -interesting reading (http://www.linuxprinting.org/foomatic2.9/download.cgi?filename=foomatic-rip&show=1), -because it is very well documented by Till's inline comments (even +interesting reading +because it is well documented by Kamppeter's inline comments (even non-Perl hackers will learn quite a bit about printing by reading -it... ;-)
Save foomatic-rip either directly in +it).
Save foomatic-rip either directly in /usr/lib/cups/filter/foomatic-rip or somewhere in -your $PATH (and don't forget to make it world-executable). Again, -don't save by "copy'n'paste" but use the appropriate link, or the -"Save as..." menu item in your browser.
If you save foomatic-rip in your $PATH, create a symlink: -cd /usr/lib/cups/filter/ ; ln -s `which -foomatic-rip`. For CUPS to discover this new -available filter at startup, you need to re-start +your $PATH (and remember to make it world-executable). Again, +do not save by copy and paste but use the appropriate link or the +Save as... menu item in your browser.
If you save foomatic-rip in your $PATH, create a symlink: +
```
+root# cd /usr/lib/cups/filter/ ; ln -s `which foomatic-rip'
+
```
+
+CUPS will discover this new available filter at startup after restarting cupsd.

-Once you print to a printqueue set up with the Foomatic-PPD, CUPS will +Once you print to a print queue set up with the Foomatic-PPD, CUPS will insert the appropriate commands and comments into the resulting PostScript jobfile. foomatic-rip is able to read and act upon -these. foomatic-rip uses some specially encoded Foomatic comments, +these and uses some specially encoded Foomatic comments embedded in the jobfile. These in turn are used to construct -(transparently for you, the user) the complicated ghostscript command -line telling for the printer driver how exactly the resulting raster -data should look like and which printer commands to embed into the -data stream. -

-You need: -

A "foomatic+something" PPD -- but it this not enough +(transparently for you, the user) the complicated Ghostscript command +line telling the printer driver exactly how the resulting raster +data should look and which printer commands to embed into the +data stream. You need: +
- A “foomatic+something” PPD but this is not enough to print with CUPS (it is only one important -component)
- The "foomatic-rip" filter script (Perl) in -/usr/lib/cups/filters/
- Perl to make foomatic-rip run
- Ghostscript (because it is doing the main work, +component).
- The foomatic-rip filter script (Perl) in +/usr/lib/cups/filters/.
- Perl to make foomatic-rip run.
- Ghostscript (because it is doing the main work, controlled by the PPD/foomatic-rip combo) to produce the raster data -fit for your printermodel's consumption
- Ghostscript must (depending on -the driver/model) contain support for a certain "device", representing -the selected "driver" for your model (as shown by "gs --h")
- foomatic-rip needs a new version of PPDs (PPD versions -produced for cupsomatic don't work with -foomatic-rip).

`Page Accounting with CUPS`

-Often there are questions regarding "print quotas" wherein Samba users +fit for your printer model's consumption. Ghostscript must (depending on +the driver/model) contain support for a certain device representing +the selected driver for your model (as shown by gs + -h). foomatic-rip needs a new version of PPDs (PPD versions +produced for cupsomatic do not work with +foomatic-rip).

Prev	Up	Next
Chapter 18. Classical Printing Support	Home	Chapter 20. Stackable VFS modules