swift       05/06/28 10:54:26

  Modified:    xml/htdocs/doc/en/handbook/draft printing-howto.xml
  Log:
  Readd using client.conf for just remote usage; using the cups interface is 
only needed if you want to be able to configure the printer afaik

Revision  Changes    Path
1.4       +45 -11    xml/htdocs/doc/en/handbook/draft/printing-howto.xml

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

Index: printing-howto.xml
===================================================================
RCS file: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/printing-howto.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- printing-howto.xml  28 Jun 2005 10:34:08 -0000      1.3
+++ printing-howto.xml  28 Jun 2005 10:54:26 -0000      1.4
@@ -1,6 +1,6 @@
 <?xml version='1.0' encoding="UTF-8"?>
 
-<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/printing-howto.xml,v 1.3 
2005/06/28 10:34:08 swift Exp $ -->
+<!-- $Header: 
/var/cvsroot/gentoo/xml/htdocs/doc/en/handbook/draft/printing-howto.xml,v 1.4 
2005/06/28 10:54:26 swift Exp $ -->
 
 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
 
@@ -303,8 +303,9 @@
 </p>
 
 <p>
-To have CUPS automatically loaded on start-up you should add it to the default
-runlevel:
+If the printer is attached to your system locally, you need to load CUPS 
+automatically on start-up. Make sure your printer is attached and powered on 
+before you start CUPS.
 </p>
 
 <pre caption="Automatically starting CUPS">
@@ -312,10 +313,6 @@
 # <i>rc-update add cupsd default</i>
 </pre>
 
-<p>
-Make sure your printer is attached and up before starting CUPS.
-</p>
-
 </body>
 </section>
 <section>
@@ -323,9 +320,9 @@
 <body>
 
 <p>
-The default CUPS configuration in <path>/etc/cups/cupsd.conf</path> is
-sufficient for most users. However, several users might need some changes to 
the
-CUPS configuration.
+The default CUPS server configuration in <path>/etc/cups/cupsd.conf</path> 
+is sufficient for most users. However, several users might need some changes 
+to the CUPS configuration.
 </p>
 
 <p>
@@ -347,6 +344,12 @@
     Windows systems to be able to access a Samba-shared printer as most Windows
     drivers are PCL drivers.
   </li>
+  <li>
+    In <uri link="#setup_remote">Setting Up a Remote Printer</uri> we
+    configure this system to use a printer attached to another system. This
+    method only changes your system to use the printer; these changes will not
+    allow you to configure the printer.
+  </li>
 </ul>
 
 </body>
@@ -437,9 +440,40 @@
 
 </body>
 </section>
+<section id="setup_remote">
+<title>Setting Up a Remote Printer</title>
+<body>
+
+<p>
+If you do not intend to configure the remote printer (available
+through the IPP protocol) on this system, you can easily set up your system to
+use the remote printer by changing the <path>/etc/cups/client.conf</path> file.
+</p>
+
+<p>
+Assuming the printer is attached to a system called 
<c>printserver.mydomain</c>,
+open up <path>/etc/cups/client.conf</path> with your favorite editor and set 
the
+<c>ServerName</c> directive:
+</p>
+
+<pre caption="Editing client.conf">
+# <i>vim /etc/cups/client.conf</i>
+
+<comment>(Substitute printserver.mydomain with your print server 
name)</comment>
+ServerName <i>printserver.mydomain</i>
+</pre>
+
+<p>
+That's it. If you do want to be able to configure the remote printer through
+your system, follow the <uri link="#configure_printer">Configuring a
+Printer</uri> instructions. If not, you're all set.
+</p>
+
+</body>
+</section>
 </chapter>
 
-<chapter id="local">
+<chapter id="configure_printer">
 <title>Configuring a Printer</title>
 <section>
 <title>Detecting the Printer</title>



-- 
[email protected] mailing list

Reply via email to