From 849ee8b516b7a273875bacefcf4092fd40303c81 Mon Sep 17 00:00:00 2001 From: Jelmer Vernooij Date: Tue, 10 Jun 2003 19:39:16 +0000 Subject: Add authors (This used to be commit 17f65e3a9357d1e1fad756617c6108bc32b6412e) --- docs/docbook/projdoc/CUPS-printing.xml | 370 ++++++++++++++++--------------- docs/docbook/projdoc/printer_driver2.xml | 1 + 2 files changed, 190 insertions(+), 181 deletions(-) (limited to 'docs/docbook/projdoc') diff --git a/docs/docbook/projdoc/CUPS-printing.xml b/docs/docbook/projdoc/CUPS-printing.xml index a51cc384be..07978441cb 100644 --- a/docs/docbook/projdoc/CUPS-printing.xml +++ b/docs/docbook/projdoc/CUPS-printing.xml @@ -9,6 +9,14 @@
kpfeifle@danka.de
+ + CiprianVizitiu + +
CVizitiu@gbif.org
+ + drawings + + (3 June 2003) @@ -16,190 +24,190 @@ -Introduction - - -Features and Benefits - - -The Common Unix Print System (CUPS) has become very popular. All -big Linux distributions now ship it as their default printing -system. But to many it is still a very mystical tool. Normally it -"just works" (TM). People tend to regard it as a sort of "black box", -which they don't want to look into, as long as it works OK. But once -there is a little problem, they are in trouble to find out where to -start debugging it. Also, even the most recent and otherwise excellent -printed Samba documentation has only limited attention paid to CUPS -printing, leaving out important pieces or even writing plain wrong -things about it. This demands rectification. But before you dive into -this chapter, make sure that you don't forget to refer to the -"Classical Printing" chapter also. It contains a lot of information -that is relevant for CUPS too. - - - -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 start understand CUPS -from the beginning. This documentation will lead you here to a -complete understanding of CUPS, if you study all of the material -contained. But lets start with the most basic things first. Maybe this -is all you need for now. Then you can skip most of the other -paragraphs. - - - - - -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). In addition it -has the traditional commandline and several more modern GUI interfaces -(GUI interfaces developed by 3rd 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. - - + Introduction + + + Features and Benefits + + + The Common Unix Print System (CUPS) has become very popular. All + big Linux distributions now ship it as their default printing + system. But to many it is still a very mystical tool. Normally it + "just works" (TM). People tend to regard it as a sort of "black box", + which they don't want to look into, as long as it works OK. But once + there is a little problem, they are in trouble to find out where to + start debugging it. Also, even the most recent and otherwise excellent + printed Samba documentation has only limited attention paid to CUPS + printing, leaving out important pieces or even writing plain wrong + things about it. This demands rectification. But before you dive into + this chapter, make sure that you don't forget to refer to the + "Classical Printing" chapter also. It contains a lot of information + that is relevant for CUPS too. + + + + 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 start understand CUPS + from the beginning. This documentation will lead you here to a + complete understanding of CUPS, if you study all of the material + contained. But lets start with the most basic things first. Maybe this + is all you need for now. Then you can skip most of the other + paragraphs. + + + + + + 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). In addition it + has the traditional commandline and several more modern GUI interfaces + (GUI interfaces developed by 3rd 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 itself doesn't need a printcap file -anymore. However, the cupsd.conf configuration -file knows two related directives: they control if such a file should -be automatically created and maintained by CUPS for the convenience of -third party applications (example: Printcap -/etc/printcap and PrintcapFormat -BSD). These legacy programs often require the existence of -printcap file containing printernames or they will refuse to -print. Make sure CUPS is set to generate and maintain a printcap! 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 <filename>libcups.so</filename> - - -Samba has a very special relationship to CUPS. The reason is: Samba -can be compiled with CUPS library support. Most recent installations -have this support enabled, and 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. - - - -If SAMBA is compiled against libcups, then 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): - - - - transmeta:/home/kurt # ldd `which smbd` - libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000) - 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! - - - Should you require -- for any reason -- to set your own -print commands, you can still do this by setting printing = -sysv. However, you'll loose all the benefits from the -close CUPS/Samba integration. You are on your own then to manually -configure the rest of 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 <filename>smb.conf</filename> Settings for CUPS - - -To summarize, here is the simplest printing-related setup -forsmb.conf to enable basic CUPS support: - - - - - [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. - - + 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 itself doesn't need a printcap file + anymore. However, the cupsd.conf configuration + file knows two related directives: they control if such a file should + be automatically created and maintained by CUPS for the convenience of + third party applications (example: Printcap + /etc/printcap and PrintcapFormat + BSD). These legacy programs often require the existence of + printcap file containing printernames or they will refuse to + print. Make sure CUPS is set to generate and maintain a printcap! 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 <filename>libcups.so</filename> + + + Samba has a very special relationship to CUPS. The reason is: Samba + can be compiled with CUPS library support. Most recent installations + have this support enabled, and 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. + + + + If SAMBA is compiled against libcups, then 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): + + + + transmeta:/home/kurt # ldd `which smbd` + libssl.so.0.9.6 => /usr/lib/libssl.so.0.9.6 (0x4002d000) + 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! + + + Should you require -- for any reason -- to set your own + print commands, you can still do this by setting printing = + sysv. However, you'll loose all the benefits from the + close CUPS/Samba integration. You are on your own then to manually + configure the rest of 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 <filename>smb.conf</filename> Settings for CUPS + + + To summarize, here is the simplest printing-related setup + forsmb.conf to enable basic CUPS support: + + + + + [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 <filename>smb.conf</filename> Settings for diff --git a/docs/docbook/projdoc/printer_driver2.xml b/docs/docbook/projdoc/printer_driver2.xml index 1fb0e838ac..ba60f72ddd 100644 --- a/docs/docbook/projdoc/printer_driver2.xml +++ b/docs/docbook/projdoc/printer_driver2.xml @@ -8,6 +8,7 @@ <address><email>kpfeifle@danka.de</email></address> </affiliation> </author> + &author.jerry; <pubdate>May 32, 2003</pubdate> </chapterinfo> -- cgit