Date: Sat, 23 Mar 2019 02:02:12 +0000 (UTC) From: Benedict Reuschling <bcr@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52890 - head/en_US.ISO8859-1/articles/cups Message-ID: <201903230202.x2N22C7P026341@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: bcr Date: Sat Mar 23 02:02:12 2019 New Revision: 52890 URL: https://svnweb.freebsd.org/changeset/doc/52890 Log: Wrap long lines in the CUPS article. Remove a couple of warnings that igor was giving, mostly about wrapping long lines. In one instance, there was a redundant word removed. Modified: head/en_US.ISO8859-1/articles/cups/article.xml Modified: head/en_US.ISO8859-1/articles/cups/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/cups/article.xml Sat Mar 23 00:30:37 2019 (r52889) +++ head/en_US.ISO8859-1/articles/cups/article.xml Sat Mar 23 02:02:12 2019 (r52890) @@ -1,12 +1,22 @@ <?xml version="1.0" encoding="iso-8859-1"?> <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook XML V5.0-Based Extension//EN" "http://www.FreeBSD.org/XML/share/xml/freebsd50.dtd">; -<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="en"> - <info><title>CUPS on FreeBSD</title> - +<article xmlns="http://docbook.org/ns/docbook" + xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" + xml:lang="en"> + <info> + <title>CUPS on FreeBSD</title> + <authorgroup> - <author><personname><firstname>Chess</firstname><surname>Griffin</surname></personname><affiliation> - <address><email>chess@chessgriffin.com</email></address> + <author> + <personname> + <firstname>Chess</firstname> + <surname>Griffin</surname> + </personname> + <affiliation> + <address> + <email>chess@chessgriffin.com</email> + </address> </affiliation></author> </authorgroup> @@ -25,7 +35,8 @@ </info> <sect1 xml:id="printing-cups"> - <title>An Introduction to the Common Unix Printing System (CUPS)</title> + <title>An Introduction to the Common Unix Printing System + (CUPS)</title> <indexterm><primary>printing</primary></indexterm> <indexterm><primary>CUPS</primary></indexterm> @@ -42,30 +53,33 @@ (<acronym>LPD</acronym>), Server Message Block (<acronym>SMB</acronym>), and AppSocket (aka JetDirect) protocols are also supported with reduced functionality. - <application>CUPS</application> adds network printer browsing and - PostScript Printer Description (<acronym>PPD</acronym>) based - printing options to support real-world printing under &unix;. As - a result, <application>CUPS</application> is ideally-suited for - sharing and accessing printers in mixed environments of &os;, - &linux;, &macos; X, or &windows;.</para> + <application>CUPS</application> adds network printer browsing + and PostScript Printer Description (<acronym>PPD</acronym>) + based printing options to support real-world printing under + &unix;. As a result, <application>CUPS</application> is + ideally-suited for sharing and accessing printers in mixed + environments of &os;, &linux;, &macos; X, or + &windows;.</para> - <para>The main site for <application>CUPS</application> is <uri xlink:href="http://www.cups.org/">http://www.cups.org/</uri>.</para>; + <para>The main site for <application>CUPS</application> is <uri + xlink:href="http://www.cups.org/">http://www.cups.org/</uri>.</para>; </sect1> <sect1 xml:id="printing-cups-install"> <title>Installing the CUPS Print Server</title> - <para>To install <application>CUPS</application> using a precompiled - binary, issue the following command from a root terminal:</para> + <para>To install <application>CUPS</application> using a + precompiled binary, issue the following command from a root + terminal:</para> <screen>&prompt.root; <userinput>pkg install cups</userinput></screen> <para>Other optional, but recommended, packages are <package>print/gutenprint-cups</package> and <package>print/hplip</package>, both of which add - drivers and utilities for a variety of printers. Once installed, - the <application>CUPS</application> configuration files can be - found in the directory + drivers and utilities for a variety of printers. Once + installed, the <application>CUPS</application> configuration + files can be found in the directory <filename>/usr/local/etc/cups</filename>.</para> </sect1> @@ -76,9 +90,9 @@ configure the <application>CUPS</application> server. First, create or modify, as the case may be, the file <filename>/etc/devfs.rules</filename> and add the following - information to set the proper permissions on all potential printer - devices and to associate printers with the - <systemitem class="groupname">cups</systemitem> user group:</para> + information to set the proper permissions on all potential + printer devices and to associate printers with the <systemitem + class="groupname">cups</systemitem> user group:</para> <programlisting>[system=10] add path 'unlpt*' mode 0660 group cups @@ -91,8 +105,8 @@ add path 'usb/<replaceable>X</replaceable>.<replaceabl <replaceable>Y</replaceable>, and <replaceable>Z</replaceable> should be replaced with the target USB device listed in the <filename>/dev/usb</filename> directory that - corresponds to the printer. To find the correct device, examine - the output of &man.dmesg.8;, where + corresponds to the printer. To find the correct device, + examine the output of &man.dmesg.8;, where <filename>ugen<replaceable>X</replaceable>.<replaceable>Y</replaceable></filename> lists the printer device, which is a symbolic link to a USB device in <filename>/dev/usb</filename>.</para> @@ -129,41 +143,44 @@ devfs_system_ruleset="system"</programlisting> <title>Configuring Printers on the CUPS Print Server</title> <para>After the <application>CUPS</application> system has been - installed and configured, the administrator can begin configuring - the local printers attached to the <application>CUPS</application> - print server. This part of the process is very similar, if not - identical, to configuring <application>CUPS</application> printers - on other &unix;-based operating systems, such as a &linux; - distribution.</para> + installed and configured, the administrator can begin + configuring the local printers attached to the + <application>CUPS</application> print server. This part of the + process is very similar, if not identical, to configuring + <application>CUPS</application> printers on other &unix;-based + operating systems, such as a &linux; distribution.</para> <para>The primary means for managing and administering the <application>CUPS</application> server is through the web-based interface, which can be found by launching a web browser and - entering <uri xlink:href="http://localhost:631">http://localhost:631</uri>; in the - browser's URL bar. If the <application>CUPS</application> server - is on another machine on the network, substitute the server's - local <acronym>IP</acronym> address for - <systemitem>localhost</systemitem>. The <application>CUPS</application> - web interface is fairly self-explanatory, as there are sections - for managing printers and print jobs, authorizing users, and more. - Additionally, on the right-hand side of the Administration screen + entering <uri + xlink:href="http://localhost:631">http://localhost:631</uri>; + in the browser's URL bar. If the + <application>CUPS</application> server is on another machine on + the network, substitute the server's local <acronym>IP</acronym> + address for <systemitem>localhost</systemitem>. The + <application>CUPS</application> web interface is fairly + self-explanatory, as there are sections for managing printers + and print jobs, authorizing users, and more. Additionally, on + the right-hand side of the Administration screen are several check-boxes allowing easy access to commonly-changed - settings, such as whether to share published printers connected to - the system, whether to allow remote administration of the - <application>CUPS</application> server, and whether to allow users - additional access and privileges to the printers and print + settings, such as whether to share published printers connected + to the system, whether to allow remote administration of the + <application>CUPS</application> server, and whether to allow + users additional access and privileges to the printers and print jobs.</para> <para>Adding a printer is generally as easy as clicking <quote>Add - Printer</quote> at the Administration screen of the - <application>CUPS</application> web interface, or clicking one of - the <quote>New Printers Found</quote> buttons also at the + Printer</quote> at the Administration screen of the + <application>CUPS</application> web interface, or clicking one + of the <quote>New Printers Found</quote> buttons also at the Administration screen. When presented with the <quote>Device</quote> drop-down box, simply select the desired locally-attached printer, and then continue through the process. - If one has added the <package>print/gutenprint-cups</package> or <package>print/hplip</package> ports or packages as - referenced above, then additional print drivers will be available - in the subsequent screens that might provide more stability or + If one has added the <package>print/gutenprint-cups</package> or + <package>print/hplip</package> ports or packages as referenced + above, then additional print drivers will be available in the + subsequent screens that might provide more stability or features.</para> </sect1> @@ -190,16 +207,17 @@ devfs_system_ruleset="system"</programlisting> <application>GNOME</application> or <application>KDE</application>. Alternatively, one can access the local <application>CUPS</application> interface on the - client machine at <uri xlink:href="http://localhost:631">http://localhost:631</uri>; and - click on <quote>Add Printer</quote> in the Administration + client machine at <uri + xlink:href="http://localhost:631">http://localhost:631</uri>; + and click on <quote>Add Printer</quote> in the Administration section. When presented with the <quote>Device</quote> drop-down box, simply select the networked - <application>CUPS</application> printer, if it was automatically - discovered, or select <literal>ipp</literal> or - <literal>http</literal> and enter the <acronym>IPP</acronym> or - <acronym>HTTP</acronym> <acronym>URI</acronym> of the networked - <application>CUPS</application> printer, usually in one of the - two following syntaxes:</para> + <application>CUPS</application> printer, if it was + automatically discovered, or select <literal>ipp</literal> or + <literal>http</literal> and enter the <acronym>IPP</acronym> + or <acronym>HTTP</acronym> <acronym>URI</acronym> of the + networked <application>CUPS</application> printer, usually in + one of the two following syntaxes:</para> <programlisting>ipp://<replaceable>server-name-or-ip</replaceable>/printers/<replaceable>printername</replaceable></programlisting> @@ -214,8 +232,8 @@ devfs_system_ruleset="system"</programlisting> <programlisting>ServerName <replaceable>server-ip</replaceable></programlisting> - <para>In this case, <replaceable>server-ip</replaceable> would be - replaced by the local <acronym>IP</acronym> address of the + <para>In this case, <replaceable>server-ip</replaceable> would + be replaced by the local <acronym>IP</acronym> address of the <application>CUPS</application> server on the network.</para> </sect2> @@ -223,21 +241,22 @@ devfs_system_ruleset="system"</programlisting> <title>&windows; Clients</title> <para>Versions of &windows; prior to XP did not have the - capability to natively network with <acronym>IPP</acronym>-based - printers. However, &windowsxp; and later versions do have this - capability. Therefore, to add a <application>CUPS</application> - printer in these versions of &windows; is quite easy. - Generally, the &windows; administrator will run the &windows; - <literal>Add Printer</literal> wizard, select <literal>Network - Printer</literal> and then enter the <acronym>URI</acronym> in - the following syntax:</para> + capability to natively network with + <acronym>IPP</acronym>-based printers. However, &windowsxp; + and later versions do have this capability. Therefore, to add + a <application>CUPS</application> printer in these versions of + &windows; is quite easy. Generally, the &windows; + administrator will run the &windows; <literal>Add + Printer</literal> wizard, select <literal>Network + Printer</literal> and then enter the <acronym>URI</acronym> + in the following syntax:</para> <programlisting>http://<replaceable>server-name-or-ip</replaceable>:631/printers/<replaceable>printername</replaceable></programlisting>; <para>If one has an older version of &windows; without native - <acronym>IPP</acronym> printing support, then the general means - of connecting to a <application>CUPS</application> printer is to - use <package>net/samba3</package> and + <acronym>IPP</acronym> printing support, then the general + means of connecting to a <application>CUPS</application> + printer is to use <package>net/samba3</package> and <application>CUPS</application> together, which is a topic outside the scope of this chapter.</para> </sect2> @@ -247,20 +266,21 @@ devfs_system_ruleset="system"</programlisting> <title>CUPS Troubleshooting</title> <para>Difficulties with <application>CUPS</application> often lies - in permissions. First, double check the &man.devfs.8; permissions - as outlined above. Next, check the actual permissions of the - devices created in the file system. It is also helpful to make - sure your user is a member of the <systemitem class="groupname">cups</systemitem> - group. If the permissions check boxes in the Administration - section of the <application>CUPS</application> web interface do - not seem to be working, another fix might be to manually backup - the main <application>CUPS</application> configuration file - located at <filename>/usr/local/etc/cups/cupsd.conf</filename> and - edit the various configuration options and try different + in permissions. First, double check the &man.devfs.8; + permissions as outlined above. Next, check the actual + permissions of the devices created in the file system. It is + also helpful to make sure your user is a member of the + <systemitem class="groupname">cups</systemitem> group. If the + permissions check boxes in the Administration section of the + <application>CUPS</application> web interface do not seem to be + working, another fix might be to manually backup the main + <application>CUPS</application> configuration file + located at <filename>/usr/local/etc/cups/cupsd.conf</filename> + and edit the various configuration options and try different combinations of configuration options. One sample <filename>/usr/local/etc/cups/cupsd.conf</filename> to test is listed below. Please note that this sample - <filename>cupsd.conf</filename> file sacrifices security for + <filename>cupsd.conf</filename> sacrifices security for easier configuration; once the administrator successfully connects to the <application>CUPS</application> server and configures the clients, it is advisable to revisit this
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201903230202.x2N22C7P026341>