From owner-svn-doc-all@freebsd.org Sat Mar 23 02:02:13 2019 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 109F41559D02; Sat, 23 Mar 2019 02:02:13 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B0CAC6FEA1; Sat, 23 Mar 2019 02:02:12 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 73F711531; Sat, 23 Mar 2019 02:02:12 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x2N22CBa026342; Sat, 23 Mar 2019 02:02:12 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x2N22C7P026341; Sat, 23 Mar 2019 02:02:12 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201903230202.x2N22C7P026341@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Sat, 23 Mar 2019 02:02:12 +0000 (UTC) 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 X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/articles/cups X-SVN-Commit-Revision: 52890 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: B0CAC6FEA1 X-Spamd-Bar: -- Authentication-Results: mx1.freebsd.org X-Spamd-Result: default: False [-2.97 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_HAM_MEDIUM(-1.00)[-0.999,0]; NEURAL_HAM_SHORT(-0.98)[-0.976,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US]; NEURAL_HAM_LONG(-1.00)[-1.000,0] X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Mar 2019 02:02:13 -0000 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 @@ -
- CUPS on FreeBSD - +
+ + CUPS on FreeBSD + - ChessGriffin -
chess@chessgriffin.com
+ + + Chess + Griffin + + +
+ chess@chessgriffin.com +
@@ -25,7 +35,8 @@ - An Introduction to the Common Unix Printing System (CUPS) + An Introduction to the Common Unix Printing System + (CUPS) printing CUPS @@ -42,30 +53,33 @@ (LPD), Server Message Block (SMB), and AppSocket (aka JetDirect) protocols are also supported with reduced functionality. - CUPS adds network printer browsing and - PostScript Printer Description (PPD) based - printing options to support real-world printing under &unix;. As - a result, CUPS is ideally-suited for - sharing and accessing printers in mixed environments of &os;, - &linux;, &macos; X, or &windows;. + CUPS adds network printer browsing + and PostScript Printer Description (PPD) + based printing options to support real-world printing under + &unix;. As a result, CUPS is + ideally-suited for sharing and accessing printers in mixed + environments of &os;, &linux;, &macos; X, or + &windows;. - The main site for CUPS is http://www.cups.org/. + The main site for CUPS is http://www.cups.org/. Installing the CUPS Print Server - To install CUPS using a precompiled - binary, issue the following command from a root terminal: + To install CUPS using a + precompiled binary, issue the following command from a root + terminal: &prompt.root; pkg install cups Other optional, but recommended, packages are print/gutenprint-cups and print/hplip, both of which add - drivers and utilities for a variety of printers. Once installed, - the CUPS configuration files can be - found in the directory + drivers and utilities for a variety of printers. Once + installed, the CUPS configuration + files can be found in the directory /usr/local/etc/cups. @@ -76,9 +90,9 @@ configure the CUPS server. First, create or modify, as the case may be, the file /etc/devfs.rules and add the following - information to set the proper permissions on all potential printer - devices and to associate printers with the - cups user group: + information to set the proper permissions on all potential + printer devices and to associate printers with the cups user group: [system=10] add path 'unlpt*' mode 0660 group cups @@ -91,8 +105,8 @@ add path 'usb/X.Y, and Z should be replaced with the target USB device listed in the /dev/usb 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 ugenX.Y lists the printer device, which is a symbolic link to a USB device in /dev/usb. @@ -129,41 +143,44 @@ devfs_system_ruleset="system" Configuring Printers on the CUPS Print Server After the CUPS system has been - installed and configured, the administrator can begin configuring - the local printers attached to the CUPS - print server. This part of the process is very similar, if not - identical, to configuring CUPS printers - on other &unix;-based operating systems, such as a &linux; - distribution. + installed and configured, the administrator can begin + configuring the local printers attached to the + CUPS print server. This part of the + process is very similar, if not identical, to configuring + CUPS printers on other &unix;-based + operating systems, such as a &linux; distribution. The primary means for managing and administering the CUPS server is through the web-based interface, which can be found by launching a web browser and - entering http://localhost:631 in the - browser's URL bar. If the CUPS server - is on another machine on the network, substitute the server's - local IP address for - localhost. The CUPS - 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 http://localhost:631 + in the browser's URL bar. If the + CUPS server is on another machine on + the network, substitute the server's local IP + address for localhost. The + CUPS 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 - CUPS 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 + CUPS server, and whether to allow + users additional access and privileges to the printers and print jobs. Adding a printer is generally as easy as clicking Add - Printer at the Administration screen of the - CUPS web interface, or clicking one of - the New Printers Found buttons also at the + Printer at the Administration screen of the + CUPS web interface, or clicking one + of the New Printers Found buttons also at the Administration screen. When presented with the Device drop-down box, simply select the desired locally-attached printer, and then continue through the process. - If one has added the print/gutenprint-cups or print/hplip 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 print/gutenprint-cups or + print/hplip ports or packages as referenced + above, then additional print drivers will be available in the + subsequent screens that might provide more stability or features. @@ -190,16 +207,17 @@ devfs_system_ruleset="system" GNOME or KDE. Alternatively, one can access the local CUPS interface on the - client machine at http://localhost:631 and - click on Add Printer in the Administration + client machine at http://localhost:631 + and click on Add Printer in the Administration section. When presented with the Device drop-down box, simply select the networked - CUPS printer, if it was automatically - discovered, or select ipp or - http and enter the IPP or - HTTP URI of the networked - CUPS printer, usually in one of the - two following syntaxes: + CUPS printer, if it was + automatically discovered, or select ipp or + http and enter the IPP + or HTTP URI of the + networked CUPS printer, usually in + one of the two following syntaxes: ipp://server-name-or-ip/printers/printername @@ -214,8 +232,8 @@ devfs_system_ruleset="system" ServerName server-ip - In this case, server-ip would be - replaced by the local IP address of the + In this case, server-ip would + be replaced by the local IP address of the CUPS server on the network. @@ -223,21 +241,22 @@ devfs_system_ruleset="system" &windows; Clients Versions of &windows; prior to XP did not have the - capability to natively network with IPP-based - printers. However, &windowsxp; and later versions do have this - capability. Therefore, to add a CUPS - printer in these versions of &windows; is quite easy. - Generally, the &windows; administrator will run the &windows; - Add Printer wizard, select Network - Printer and then enter the URI in - the following syntax: + capability to natively network with + IPP-based printers. However, &windowsxp; + and later versions do have this capability. Therefore, to add + a CUPS printer in these versions of + &windows; is quite easy. Generally, the &windows; + administrator will run the &windows; Add + Printer wizard, select Network + Printer and then enter the URI + in the following syntax: http://server-name-or-ip:631/printers/printername If one has an older version of &windows; without native - IPP printing support, then the general means - of connecting to a CUPS printer is to - use net/samba3 and + IPP printing support, then the general + means of connecting to a CUPS + printer is to use net/samba3 and CUPS together, which is a topic outside the scope of this chapter. @@ -247,20 +266,21 @@ devfs_system_ruleset="system" CUPS Troubleshooting Difficulties with CUPS 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 cups - group. If the permissions check boxes in the Administration - section of the CUPS web interface do - not seem to be working, another fix might be to manually backup - the main CUPS configuration file - located at /usr/local/etc/cups/cupsd.conf 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 + cups group. If the + permissions check boxes in the Administration section of the + CUPS web interface do not seem to be + working, another fix might be to manually backup the main + CUPS configuration file + located at /usr/local/etc/cups/cupsd.conf + and edit the various configuration options and try different combinations of configuration options. One sample /usr/local/etc/cups/cupsd.conf to test is listed below. Please note that this sample - cupsd.conf file sacrifices security for + cupsd.conf sacrifices security for easier configuration; once the administrator successfully connects to the CUPS server and configures the clients, it is advisable to revisit this