doc-el commit 965:44fe4eba78b2 - Import FreeBSD doc/ snapshot at...
freebsd-doc-el at lists.hellug.gr
freebsd-doc-el at lists.hellug.gr
Mon Oct 27 18:40:41 EET 2008
changeset: 965:44fe4eba78b2
user: ncvs
date: 2008-10-26 08:35 +0000
details: http://hg.hellug.gr/freebsd/doc-el/?cmd=changeset;node=44fe4eba78b2
description:
Import FreeBSD doc/ snapshot at 2008-10-26 08:35:01 +0000
diffs (truncated from 563 to 300 lines):
diff -r 5c37e3229483 -r 44fe4eba78b2 el_GR.ISO8859-7/books/handbook/desktop/chapter.sgml
--- a/el_GR.ISO8859-7/books/handbook/desktop/chapter.sgml Thu Oct 23 18:45:39 2008 +0000
+++ b/el_GR.ISO8859-7/books/handbook/desktop/chapter.sgml Sun Oct 26 08:35:01 2008 +0000
@@ -4,10 +4,10 @@
The FreeBSD Documentation Project
- $FreeBSD: doc/el_GR.ISO8859-7/books/handbook/desktop/chapter.sgml,v 1.3 2008/09/14 14:47:37 manolis Exp $
+ $FreeBSD: doc/el_GR.ISO8859-7/books/handbook/desktop/chapter.sgml,v 1.4 2008/10/26 08:35:01 manolis Exp $
%SOURCE% en_US.ISO8859-1/books/handbook/desktop/chapter.sgml
- %SRCID% 1.76
+ %SRCID% 1.78
-->
@@ -306,7 +306,7 @@
<application>&java;</application>. Áí áõôü äåí óõìâáßíåé, åêôåëÝóôå
ùò <username>root</username>, ôçí áêüëïõèç åíôïëÞ:</para>
- <screen>&prompt.root; <userinput>ln -s /usr/local/diablo-jre1.5.0/plugin/i386/ns7/libjavaplugin_oji.so \
+ <screen>&prompt.root; <userinput>ln -s /usr/local/diablo-jre1.6.0/plugin/i386/ns7/libjavaplugin_oji.so \
/usr/local/lib/browser_plugins/</userinput></screen>
<para>êáé Ýðåéôá åðáíåêêéíÞóôå ôï öõëëïìåôñçôÞ óáò.</para>
@@ -402,7 +402,7 @@
<para>Ï <application>Konqueror</application> õðïóôçñßæåé åðßóçò
<application>&flash;</application> êáé ïé ó÷åôéêÝò ïäçãßåò (How To)
åßíáé äéáèÝóéìåò óôï
- <ulink url="http://freebsd.kde.org/howto.php"></ulink>.</para>
+ <ulink url="http://freebsd.kde.org/howtos/konqueror-flash.php"></ulink>.</para>
</sect2>
</sect1>
@@ -1163,6 +1163,7 @@
<!--
Local Variables:
mode: sgml
+ coding: iso-8859-7
sgml-declaration: "../chapter.decl"
sgml-indent-data: t
sgml-omittag: nil
diff -r 5c37e3229483 -r 44fe4eba78b2 en_US.ISO8859-1/articles/cups/Makefile
--- a/en_US.ISO8859-1/articles/cups/Makefile Thu Oct 23 18:45:39 2008 +0000
+++ b/en_US.ISO8859-1/articles/cups/Makefile Sun Oct 26 08:35:01 2008 +0000
@@ -1,12 +1,11 @@
#
-# $FreeBSD: doc/en_US.ISO8859-1/articles/cups/Makefile,v 1.1 2008/05/31 13:30:22 remko Exp $
+# $FreeBSD: doc/en_US.ISO8859-1/articles/cups/Makefile,v 1.2 2008/10/24 23:01:06 pgj Exp $
#
# Article: CUPS on FreeBSD
DOC?= article
FORMATS?= html
-WITH_ARTICLE_TOC?= YES
INSTALL_COMPRESSED?=gz
INSTALL_ONLY_COMPRESSED?=
diff -r 5c37e3229483 -r 44fe4eba78b2 en_US.ISO8859-1/articles/cups/article.sgml
--- a/en_US.ISO8859-1/articles/cups/article.sgml Thu Oct 23 18:45:39 2008 +0000
+++ b/en_US.ISO8859-1/articles/cups/article.sgml Sun Oct 26 08:35:01 2008 +0000
@@ -7,11 +7,11 @@
<article>
<articleinfo>
<title>CUPS on FreeBSD</title>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/cups/article.sgml,v 1.1 2008/05/31 13:30:22 remko Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/cups/article.sgml,v 1.3 2008/10/24 23:18:46 pgj Exp $</pubdate>
<authorgroup>
<author>
<firstname>Chess</firstname>
- <surname>Grifin</surname>
+ <surname>Griffin</surname>
<affiliation>
<address><email>chess at chessgriffin.com</email></address>
</affiliation>
@@ -55,221 +55,219 @@
<para>The main site for <application>CUPS</application> is <ulink
url="http://www.cups.org/"></ulink>.</para>
+ </sect1>
- <sect2 id="printing-cups-install">
- <title>Installing the CUPS Print Server</title>
+ <sect1 id="printing-cups-install">
+ <title>Installing the CUPS Print Server</title>
- <para><application>CUPS</application> can be installed from ports
- or by using a precompiled binary package. To install
- <application>CUPS</application> from ports, issue the following
- command from a root terminal:</para>
+ <para><application>CUPS</application> can be installed from ports or
+ by using a precompiled binary package. To install
+ <application>CUPS</application> from ports, issue the following
+ command from a root terminal:</para>
- <screen>&prompt.root; <userinput>cd /usr/ports/print/cups && make install clean</userinput></screen>
+ <screen>&prompt.root; <userinput>cd /usr/ports/print/cups && make install clean</userinput></screen>
- <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_add -r cups</userinput></screen>
+ <screen>&prompt.root; <userinput>pkg_add -r cups</userinput></screen>
- <para>Other optional, but recommended, ports or packages are
- <application>print/gutenprint-cups</application> and
- <application>print/hplip</application>, 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
- <filename>/usr/local/etc/cups</filename>.</para>
- </sect2>
+ <para>Other optional, but recommended, ports or packages are
+ <filename role="package">print/gutenprint-cups</filename> and
+ <filename role="package">print/hplip</filename>, 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
+ <filename>/usr/local/etc/cups</filename>.</para>
+ </sect1>
- <sect2 id="printing-cups-configuring-server">
- <title>Configuring the CUPS Print Server</title>
+ <sect1 id="printing-cups-configuring-server">
+ <title>Configuring the CUPS Print Server</title>
- <para>After installation, a few files must edited in order to
- 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 cups user
- group:</para>
+ <para>After installation, a few files must edited in order to
+ 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
+ <groupname>cups</groupname> user group:</para>
- <programlisting>[system=10]
+ <programlisting>[system=10]
add path 'unlpt*' mode 0660 group cups
add path 'ulpt*' mode 0660 group cups
add path 'lpt*' mode 0660 group cups</programlisting>
- <para>Next, add two lines to <filename>/etc/rc.conf</filename>
- as follows:</para>
+ <para>Next, add two lines to <filename>/etc/rc.conf</filename> as
+ follows:</para>
- <programlisting>cupsd_enable="YES"
+ <programlisting>cupsd_enable="YES"
devfs_system_ruleset="system"</programlisting>
- <para>These two entries will start the
- <application>CUPS</application> print server on boot and invoke
- the local devfs rule created above, respectively.</para>
+ <para>These two entries will start the
+ <application>CUPS</application> print server on boot and invoke
+ the local devfs rule created above, respectively.</para>
- <para>In order to enable <application>CUPS</application> printing
- under certain µsoft.windows; clients, the line
- <programlisting>application/octet-stream</programlisting> should be
- uncommented in <filename>/usr/local/etc/cups/mime.types</filename>
- and <filename>/usr/local/etc/cups/mime.convs</filename>.</para>
+ <para>In order to enable <application>CUPS</application> printing
+ under certain µsoft.windows; clients, the line below should
+ be uncommented in
+ <filename>/usr/local/etc/cups/mime.types</filename> and
+ <filename>/usr/local/etc/cups/mime.convs</filename>:</para>
- <para>Once these changes have been made, the &man.devfs.8; and
- <application>CUPS</application> systems must both be restarted,
- either by rebooting the computer or issuing the following two
- commands in a root terminal:</para>
+ <programlisting>application/octet-stream</programlisting>
- <screen>&prompt.root; <userinput>/etc/rc.d/devfs restart</userinput>
+ <para>Once these changes have been made, the &man.devfs.8; and
+ <application>CUPS</application> systems must both be restarted,
+ either by rebooting the computer or issuing the following two
+ commands in a root terminal:</para>
+
+ <screen>&prompt.root; <userinput>/etc/rc.d/devfs restart</userinput>
&prompt.root; <userinput>/usr/local/etc/rc.d/cupsd restart</userinput></screen>
+ </sect1>
+ <sect1 id="printing-cups-configuring-printers">
+ <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>
+
+ <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 <ulink url="http://localhost:631"></ulink> 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> addresss for
+ <hostid>localhost</hostid>. 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
+ 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
+ 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 <filename
+ role="package">print/gutenprint-cups</filename> or <filename
+ role="package">print/hplip</filename> 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>
+
+ <sect1 id="printing-cups-clients">
+ <title>Configuring CUPS Clients</title>
+
+ <para>Once the <application>CUPS</application> server has been
+ configured and printers have been added and published to the
+ network, the next step is to configure the clients, or the
+ machines that are going to access the
+ <application>CUPS</application> server. If one has a single
+ desktop machine that is acting as both server and client, then
+ much of this information may not be needed.</para>
+
+ <sect2 id="printing-cups-clients-unix">
+ <title>&unix; Clients</title>
+
+ <para><application>CUPS</application> will also need to be
+ installed on your &unix; clients. Once
+ <application>CUPS</application> is installed on the clients,
+ then <application>CUPS</application> printers that are shared
+ across the network are often automatically discovered by the
+ printer managers for various desktop environments such as
+ <application>GNOME</application> or
+ <application>KDE</application>. Alternatively, one can access
+ the local <application>CUPS</application> interface on the
+ client machine at <ulink url="http://localhost:631"></ulink> 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>
+
+ <programlisting>ipp://<replaceable>server-name-or-ip</replaceable>/printers/<replaceable>printername</replaceable></programlisting>
+
+ <programlisting>http://<replaceable>server-name-or-ip</replaceable>:631/printers/<replaceable>printername</replaceable></programlisting>
+
+ <para>If the <application>CUPS</application> clients have
+ difficulty finding other <application>CUPS</application>
+ printers shared across the network, sometimes it is helpful to
+ add or create a file
+ <filename>/usr/local/etc/cups/client.conf</filename> with a
+ single entry as follows:</para>
+
+ <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
+ <application>CUPS</application> server on the network.</para>
</sect2>
- <sect2 id="printing-cups-configuring-printers">
- <title>Configuring Printers on the CUPS Print Server</title>
+ <sect2 id="printing-cups-clients-windows">
+ <title>&windows; Clients</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
More information about the Freebsd-doc-el
mailing list