From owner-p4-projects@FreeBSD.ORG Sat Oct 25 20:14:42 2008 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id B527A1065671; Sat, 25 Oct 2008 20:14:42 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 7854D106569A for ; Sat, 25 Oct 2008 20:14:42 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id 6491C8FC17 for ; Sat, 25 Oct 2008 20:14:42 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id m9PKEg7m014795 for ; Sat, 25 Oct 2008 20:14:42 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id m9PKEg3x014793 for perforce@freebsd.org; Sat, 25 Oct 2008 20:14:42 GMT (envelope-from rene@FreeBSD.org) Date: Sat, 25 Oct 2008 20:14:42 GMT Message-Id: <200810252014.m9PKEg3x014793@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Cc: Subject: PERFORCE change 151916 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Oct 2008 20:14:42 -0000 http://perforce.freebsd.org/chv.cgi?CH=151916 Change 151916 by rene@rene_self on 2008/10/25 20:14:24 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cups/Makefile#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cups/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/desktop/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/ports/chapter.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#10 integrate .. //depot/projects/docproj_nl/www/share/sgml/commercial.isp.xml#4 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#13 integrate .. //depot/projects/docproj_nl/www/share/sgml/release.ent#4 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cups/Makefile#2 (text+ko) ==== @@ -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?= ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cups/article.sgml#2 (text+ko) ==== @@ -7,11 +7,11 @@
CUPS on FreeBSD - $FreeBSD: doc/en_US.ISO8859-1/articles/cups/article.sgml,v 1.1 2008/05/31 13:30:22 remko Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/cups/article.sgml,v 1.3 2008/10/24 23:18:46 pgj Exp $ Chess - Grifin + Griffin
chess@chessgriffin.com
 @@ -55,221 +55,219 @@ The main site for CUPS is . + - - Installing the CUPS Print Server + + Installing the CUPS Print Server - CUPS can be installed from ports - or by using a precompiled binary package. To install - CUPS from ports, issue the following - command from a root terminal: + CUPS can be installed from ports or + by using a precompiled binary package. To install + CUPS from ports, issue the following + command from a root terminal: - &prompt.root; cd /usr/ports/print/cups && make install clean + &prompt.root; cd /usr/ports/print/cups && make install clean - 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_add -r cups + &prompt.root; pkg_add -r cups - Other optional, but recommended, ports or 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 - /usr/local/etc/cups. - + Other optional, but recommended, ports or 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 + /usr/local/etc/cups. + - - Configuring the CUPS Print Server + + Configuring the CUPS Print Server - After installation, a few files must edited in order to - 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: + After installation, a few files must edited in order to + 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: - [system=10] + [system=10] add path 'unlpt*' mode 0660 group cups add path 'ulpt*' mode 0660 group cups add path 'lpt*' mode 0660 group cups - Next, add two lines to /etc/rc.conf - as follows: + Next, add two lines to /etc/rc.conf as + follows: - cupsd_enable="YES" + cupsd_enable="YES" devfs_system_ruleset="system" - These two entries will start the - CUPS print server on boot and invoke - the local devfs rule created above, respectively. + These two entries will start the + CUPS print server on boot and invoke + the local devfs rule created above, respectively. + + In order to enable CUPS printing + under certain µsoft.windows; clients, the line below should + be uncommented in + /usr/local/etc/cups/mime.types and + /usr/local/etc/cups/mime.convs: - In order to enable CUPS printing - under certain µsoft.windows; clients, the line - application/octet-stream should be - uncommented in /usr/local/etc/cups/mime.types - and /usr/local/etc/cups/mime.convs. + application/octet-stream - Once these changes have been made, the &man.devfs.8; and - CUPS systems must both be restarted, - either by rebooting the computer or issuing the following two - commands in a root terminal: + Once these changes have been made, the &man.devfs.8; and + CUPS systems must both be restarted, + either by rebooting the computer or issuing the following two + commands in a root terminal: - &prompt.root; /etc/rc.d/devfs restart + &prompt.root; /etc/rc.d/devfs restart &prompt.root; /usr/local/etc/rc.d/cupsd restart + - + + Configuring Printers on the CUPS Print Server - - 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. - 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. + 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 in the + browser's URL bar. If the CUPS server + is on another machine on the network, substitute the server's + local IP addresss 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 + jobs. - 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 addresss 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 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 + 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 + features. + - 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 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 - features. - + + Configuring CUPS Clients - - Configuring CUPS Clients + Once the CUPS 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 + CUPS 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. - Once the CUPS 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 - CUPS 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. + + &unix; Clients - - &unix; Clients + CUPS will also need to be + installed on your &unix; clients. Once + CUPS is installed on the clients, + then CUPS printers that are shared + across the network are often automatically discovered by the + printer managers for various desktop environments such as + GNOME or + KDE. Alternatively, one can access + the local CUPS interface on the + client machine at 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 will also need to be - installed on your &unix; clients. Once - CUPS is installed on the clients, - then CUPS printers that are - shared across the network are often automatically discovered by - the printer managers for various desktop environments such as - 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 - 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: + ipp://server-name-or-ip/printers/printername - ipp://server-name-or-ip/printers/printername + http://server-name-or-ip:631/printers/printername - http://server-name-or-ip:631/printers/printername + If the CUPS clients have + difficulty finding other CUPS + printers shared across the network, sometimes it is helpful to + add or create a file + /usr/local/etc/cups/client.conf with a + single entry as follows: - If the CUPS clients have - difficulty finding other CUPS - printers shared across the network, sometimes it is helpful to - add or create a file - /usr/local/etc/cups/client.conf with a - single entry as follows: + ServerName server-ip - ServerName (server-ip) + In this case, server-ip would be + replaced by the local IP address of the + CUPS server on the network. + - In this case, (server-ip) would be replaced by the local - IP address of the - CUPS server on the network. - + + &windows; Clients - - &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: - 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: + http://server-name-or-ip:631/printers/printername - 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 - CUPS together, which is a topic - outside the scope of this chapter. - + 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 + CUPS together, which is a topic + outside the scope of this chapter. + - - CUPS Troubleshooting + + 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 filesystem. 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 - easier configuration; once the administrator successfully - connnects to the CUPS server and - configures the clients, it is advisable to revisit this - configuration file and begin locking down access. + 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 + 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 + easier configuration; once the administrator successfully + connnects to the CUPS server and + configures the clients, it is advisable to revisit this + configuration file and begin locking down access. - # Log general information in error_log - change "info" to "debug" for + # Log general information in error_log - change "info" to "debug" for # troubleshooting... LogLevel info @@ -348,32 +346,32 @@ Order deny,allow </Limit> </Policy> - + - - Fine Tuning CUPS-Related Ports + + Fine Tuning CUPS-Related Ports - If CUPS is going to serve as the - primary printing system, then one may choose to optionally add - certain knobs to /etc/make.conf that will - emphasize CUPS over other printing - options. Some of these "knobs" that one may want to add - are: + If CUPS is going to serve as the + primary printing system, then one may choose to optionally add + certain knobs to /etc/make.conf that will + emphasize CUPS over other printing + options. Some of these knobs that one may want to + add are: - WITH_CUPS=YES + WITH_CUPS=YES CUPS_OVERWRITE_BASE=YES WITHOUT_LPR=YES - The first knob, WITH_CUPS, adds - CUPS support to ports where - applicable. The second knob, CUPS_OVERWRITE_BASE, will fix - certain symlinks and paths that would otherwise apply to the - default &os; printing system, LPR, - and will prevent these fixes from being reverted upon the next - "buildworld" system upgrade. The third knob, WITHOUT_LPR, will - prevent LPR support from being added - to ports where applicable. - + The first knob, WITH_CUPS, adds + CUPS support to ports where applicable. + The second knob, CUPS_OVERWRITE_BASE, will fix + certain symlinks and paths that would otherwise apply to the + default &os; printing system, LPR, and + will prevent these fixes from being reverted upon the next + buildworld system upgrade. The third + knob, WITHOUT_LPR, will prevent + LPR support from being added to ports + where applicable.
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/desktop/chapter.sgml#3 (text+ko) ==== @@ -1,6 +1,6 @@ @@ -285,7 +285,7 @@ plugin should be listed there now. If it is not, as root, run the following command: - &prompt.root; ln -s /usr/local/diablo-jre1.5.0/plugin/i386/ns7/libjavaplugin_oji.so \ + &prompt.root; ln -s /usr/local/diablo-jre1.6.0/plugin/i386/ns7/libjavaplugin_oji.so \ /usr/local/lib/browser_plugins/ then relaunch your browser. @@ -378,7 +378,7 @@ Konqueror also supports &flash;; a How To guide for getting &flash; support on Konqueror - is available at . + is available at . ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/ports/chapter.sgml#4 (text+ko) ==== @@ -1,7 +1,7 @@ @@ -1140,7 +1140,7 @@ another option is to execute make rmconfig which will remove all selected options and allow you to start over. All of these options, - and others, are explained in great detail in in the man page for + and others, are explained in great detail in the manual page for &man.ports.7;. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#10 (text+ko) ==== @@ -1,7 +1,7 @@ 800049 + + 8.0-CURRENT after buffer cache API change. + 800050 + + + 8.0-CURRENT after the removal of the + &man.MALLOC.9; and &man.FREE.9; macros. + 800051 + ==== //depot/projects/docproj_nl/www/share/sgml/commercial.isp.xml#4 (text+ko) ==== @@ -1,12 +1,12 @@ - + - $FreeBSD: www/share/sgml/commercial.isp.xml,v 1.37 2008/10/18 16:55:21 erwin Exp $ + $FreeBSD: www/share/sgml/commercial.isp.xml,v 1.38 2008/10/22 19:52:02 jkois Exp $ @@ -861,6 +861,17 @@ + + KwShell Internet Services + http://www.kwshell.com + + KwShell Internet Services is an Arabic based company, which + provides hosting solutions like shared and dedicated Servers. + KwShell Internet Services is also able to provide management and + support for a variety of BSD and Linux systems. + + + RootBSD http://www.rootbsd.net ==== //depot/projects/docproj_nl/www/share/sgml/news.xml#13 (text+ko) ==== @@ -25,7 +25,7 @@ - $FreeBSD: www/share/sgml/news.xml,v 1.202 2008/10/12 09:36:46 blackend Exp $ + $FreeBSD: www/share/sgml/news.xml,v 1.203 2008/10/23 08:48:05 danger Exp $ @@ -36,6 +36,18 @@ 10 + 19 + + &os; 7.1-BETA2 Available + +

The second beta release of &os; 7.1 is now available. + ISO images for Tier-1 architectures can be found on most of the &os; mirror sites.

+ + + + 12 ==== //depot/projects/docproj_nl/www/share/sgml/release.ent#4 (text+ko) ==== @@ -1,4 +1,4 @@ - +