swift       05/06/29 14:33:11

  Modified:    xml/htdocs/doc/en printing-howto.xml
  Log:
  #94346 - #62622: Rewrite on printing howto; covers more modern method of 
print installation; remove foomatic stuff as it causes more confusion than 
anything else. Make better separation of content to make future addenda easier 
to integrate.

Revision  Changes    Path
1.49      +671 -376  xml/htdocs/doc/en/printing-howto.xml

file : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/printing-howto.xml?rev=1.49&content-type=text/x-cvsweb-markup&cvsroot=gentoo
plain: 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/printing-howto.xml?rev=1.49&content-type=text/plain&cvsroot=gentoo
diff : 
http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/printing-howto.xml.diff?r1=1.48&r2=1.49&cvsroot=gentoo

Index: printing-howto.xml
===================================================================
RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v
retrieving revision 1.48
retrieving revision 1.49
diff -u -r1.48 -r1.49
--- printing-howto.xml  23 May 2005 16:56:11 -0000      1.48
+++ printing-howto.xml  29 Jun 2005 14:33:11 -0000      1.49
@@ -1,596 +1,891 @@
-<?xml version='1.0' encoding="UTF-8"?> 
-<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.48 
2005/05/23 16:56:11 swift Exp $ -->
-<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
+<?xml version='1.0' encoding="UTF-8"?>
 
-<guide link="/doc/en/printing-howto.xml"> 
+<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/printing-howto.xml,v 1.49 
2005/06/29 14:33:11 swift Exp $ -->
 
-<title>Gentoo Printing Guide</title> 
+<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
-<author title="Author"><!-- [EMAIL PROTECTED] -->
-  John P. Davis
-</author>
-<author title="Editor">
-  <mail link="[EMAIL PROTECTED]">Wesley Leggette</mail>
-</author>
-<author title="Editor">
-  <mail link="[EMAIL PROTECTED]">Carl Anderson</mail>
-</author>
-<author title="Editor">
-  <mail link="[EMAIL PROTECTED]">Heinrich Wendel</mail>
-</author>
-<author title="Editor">
+<guide link="/doc/en/printing-howto.xml">
+<title>Gentoo Printing Guide</title>
+
+<author title="Author">
   <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail>
 </author>
-<author title="Copyeditor">
-  <mail link="[EMAIL PROTECTED]">Phil Bordelon</mail>
-</author> 
 
 <abstract>
-A comprehensive printing guide for Gentoo Linux. 
-This document covers both local and network printing.
-</abstract> 
+This document covers the installation and maintenance of printers using CUPS 
and
+Samba. It covers local installation and networked installations and you'll
+also find instructions on using shared printers from other operating systems.
+</abstract>
 
+<!-- The content of this document is licensed under the CC-BY-SA license -->
+<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
 <license/>
 
-<version>1.23</version>
-<date>2005-05-23</date>
+<version>2.0</version>
+<date>2005-06-29</date>
 
-<chapter> 
-<title>Installing CUPS and foomatic</title> 
+<chapter>
+<title>Printing and Gentoo Linux</title>
 <section>
-<body> 
-
-<p>
-Setting up printing in Gentoo Linux is a relatively painless task, thanks
-to some great programs such as CUPS (the Common Unix Printing System) and 
-foomatic. Both of these programs are currently in the Portage tree, and they 
are
-very easy to set up for the end user.
-</p> 
-
-<p>
-Please be aware the cups is cross-desktop, i.e. you can follow
-these directions to get printing working under GNOME or KDE.
-There are other options, such as KDE's print setup, but I believe that 
-CUPS is the easiest to setup, and the most scalable.
-</p>
+<title>Use the Right Tools</title>
+<body>
 
 <p>
-Before emerging CUPS, it is a  good idea to add the necessary
-USE flags to <path>/etc/make.conf</path>.
+Linux has great support for printers; the right tool for the job is called CUPS
+(<uri link="http://www.cups.org";>Common Unix Printing System</uri>). Since the
+beginning of the project, back in 1999, the installation and maintenance of 
CUPS
+has improved dramatically. 
 </p>
 
-<pre caption = "Editing /etc/make.conf">
-<comment>add cups, foomaticdb, ppds and usb (if you are using a USB printer 
connection) to your existing USE var list. </comment>
-USE="cups foomaticdb ppds usb other_var1 other_var2"
-</pre>
-
 <p>
-For more information on USE variables, please see the <uri
-link="http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=2&amp;chap=2";>USE
-flags</uri> chapter in the Gentoo Handbook.
+In this document we will cover how to use CUPS to setup a local or networked 
+printer. We will not go in too much detail since the project has <uri
+link="http://www.cups.org/documentation.php";>great documentation</uri> 
available
+for advanced usage.
 </p>
 
-<pre caption = "Emerging necessary packages">
-# <i>emerge cups</i>
-# <i>emerge foomatic </i>
-</pre>
-
 </body>
 </section>
 </chapter>
 
 <chapter>
-<title>Setting up Kernel Modules</title> 
+<title>Configure your Kernel</title>
 <section>
-<title>General</title>
+<title>Introduction</title>
 <body>
 
 <p>
-Now that the necessary packages are installed, it is time to install the 
-printer.
+When you want to install a printer on your system you need to know how your
+printer will be attached to your system. Is it through a local port like LPT or
+USB, or is it networked? And if it is, does it use the Internet Printing
+Protocol (IPP) or is it through the Microsoft Windows SMB-CIFS protocol
+(Microsoft Windows Sharing)?
 </p>
 
 <p>
-Depending on what type of printer connection you will be using, it will
-be necessary to enable either parallel port or USB port printer connections
-in the kernel.
+The next few sections explain what minimal kernel configuration you need. Of
+course, this depends on how your printer is going to be attached to your 
system,
+so for your convenience we have separated the instructions:
+</p>
+
+<ul>
+  <li><uri link="#lpt">Locally Attached Printer (LPT)</uri></li>
+  <li><uri link="#usb">Locally Attached Printer (USB)</uri></li>
+  <li><uri link="#ipp">Remotely Attached Printer (IPP)</uri></li>
+  <li><uri link="#smb-cifs">Remotely Attached Printer (SMB-CIFS)</uri></li>
+</ul>
+
+<p>
+So manoeuvre to <path>/usr/src/linux</path> and run <c>make menuconfig</c> to
+enter the kernel configuration. If you used <c>genkernel</c> to configure your
+kernel, you should still perform these steps just to make sure nothing was
+missed out.
 </p>
 
-<note>
-This is only needed for local printing, if you want to print via samba, skip 
-this section.
-</note>
+<p>
+In the next configuration examples, we will add the necessary support <e>in</e>
+the kernel, not as modules. This is not mandatory; if you want you can easily
+use modular support. Don't forget to load the appropriate modules afterwards.
+We also use a 2.6 kernel configuration example; 2.4 users might find the
+appropriate configuration directives elsewhere. 
+</p>
 
-<note>
-If you are not sure on how to compile the kernel, the specific
-instructions can be found in the <uri 
-link="http://www.tldp.org/HOWTO/Kernel-HOWTO.html";>Kernel Howto</uri> 
(currently
-down for review). Make sure you find out how to compile and install new 
modules 
-without having to recompile your kernel or restart your computer. It's a real 
-timesaver.
-</note>
+<p>
+Now go to the appropriate section to configure (or check) your kernel.
+</p>
 
 </body>
 </section>
-<section>
-<title>USB Modules</title>
+<section id="lpt">
+<title>Locally Attached Printer (LPT)</title>
 <body>
 
 <p>
-To enable USB printer support, go to <c>USB support</c> and enable <c>Support 
-for USB</c> and <c>USB Printer support</c>. Enabling them both as modules will 
-install usbcore.o and printer.o in your modules directory. I suggest using 
-modules because you won't have to restart your computer. Users of a 2.6 kernel
-will find these options under <c>Device Drivers</c>.
+The LPT port is generally used to identify the parallel printer port. You need
+to enable parallel port support first, then PC-style parallel port support
+(unless you are a SPARC user) after which you enable parallel printer support.



-- 
[email protected] mailing list

Reply via email to