Date: Mon, 11 Aug 2008 09:32:23 GMT From: Remko Lodder <remko@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 147143 for review Message-ID: <200808110932.m7B9WN8q082272@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=147143 Change 147143 by remko@remko_nakur on 2008/08/11 09:32:04 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cvs-freebsd/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/mh/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/nanobsd/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/p4-primer/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/relaydelay/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/remote-install/article.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/Makefile#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/book.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/chapters.ent#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/dma/chapter.sgml#2 delete .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#6 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/geom/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/jails/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mac/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/ports/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/printing/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/security/chapter.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/pmake/gods/chapter.sgml#2 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#5 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/jails/chapter.sgml#10 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.sgml#6 integrate .. //depot/projects/docproj_nl/www/en/administration.sgml#2 integrate .. //depot/projects/docproj_nl/www/en/cgi/man.cgi#2 integrate .. //depot/projects/docproj_nl/www/en/projects/c99/index.sgml#2 integrate .. //depot/projects/docproj_nl/www/en/releases/index.sgml#2 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#5 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#4 (text+ko) ==== @@ -13,7 +13,7 @@ </author> </authorgroup> - <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.276 2008/07/22 17:05:47 remko Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.277 2008/08/06 22:03:48 pgj Exp $</pubdate> <copyright> <year>1999</year> @@ -256,19 +256,19 @@ to the appropriate repomeisters.</para> <itemizedlist> - <listitem><para>ncvs@ - regarding <filename role="directory"> + <listitem><para>ncvs@ - regarding <filename class="directory"> /home/ncvs</filename>, the src repository</para></listitem> - <listitem><para>pcvs@ - regarding <filename role="directory"> + <listitem><para>pcvs@ - regarding <filename class="directory"> /home/pcvs</filename>, the ports repository</para></listitem> - <listitem><para>dcvs@ - regarding <filename role="directory"> + <listitem><para>dcvs@ - regarding <filename class="directory"> /home/dcvs</filename>, the doc repository</para></listitem> - <listitem><para>projcvs@ - regarding <filename role="directory"> + <listitem><para>projcvs@ - regarding <filename class="directory"> /home/projcvs</filename>, the third party projects repository</para></listitem> </itemizedlist> @@ -2627,7 +2627,7 @@ </itemizedlist> <para>Alternatively, you can use the <command>rmport</command> - script, from <filename role="directory">ports/Tools/scripts</filename>. + script, from <filename class="directory">ports/Tools/scripts</filename>. This script has been written by &a.vd;, who is also its current maintainer, so please send questions, patches or suggestions about <command>rmport</command> to him.</para> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#4 (text+ko) ==== @@ -1,4 +1,4 @@ -<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.814 2008/07/22 15:49:47 vanhu Exp $ --> +<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.817 2008/07/31 14:40:10 flz Exp $ --> <!-- NOTE TO COMMITTERS: Contributors lists are sorted in alphabetical order by first name. @@ -833,6 +833,11 @@ </listitem> <listitem> + <para>Andrey Surkov + <email>nsand@sura.ru</email></para> + </listitem> + + <listitem> <para>Andrey Sverdlichenko <email>rblaze@users.sourceforge.net</email></para> </listitem> @@ -2263,6 +2268,11 @@ </listitem> <listitem> + <para>Dax Labrador + <email>semprix@bsdmail.org</email></para> + </listitem> + + <listitem> <para>David Yeske <email>dyeske@yahoo.com</email></para> </listitem> @@ -9184,6 +9194,11 @@ </listitem> <listitem> + <para>Terry Sposato + <email>terry@sucked-in.com</email></para> + </listitem> + + <listitem> <para>Teruaki Ata <email>PFA03027@nifty.ne.jp</email></para> </listitem> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#5 (text+ko) ==== @@ -1,4 +1,4 @@ -<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.238 2008/07/23 00:39:25 pgollucci Exp $ --> +<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.239 2008/08/09 19:21:38 sbruno Exp $ --> <!-- NOTE TO NEW COMMITTERS: Core and committers lists are sorted in alphabetical order by last name. Please keep in mind that fact while @@ -1509,6 +1509,10 @@ <listitem> <para>&a.rnoland;</para> </listitem> + + <listitem> + <para>&a.sbruno;</para> + </listitem> </itemizedlist> <!-- ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cvs-freebsd/article.sgml#2 (text+ko) ==== @@ -22,7 +22,7 @@ <holder role="mailto:stijn@win.tue.nl">Stijn Hoop</holder> </copyright> - <releaseinfo>$FreeBSD: doc/en_US.ISO8859-1/articles/cvs-freebsd/article.sgml,v 1.16 2006/01/23 00:48:35 keramida Exp $</releaseinfo> + <releaseinfo>$FreeBSD: doc/en_US.ISO8859-1/articles/cvs-freebsd/article.sgml,v 1.17 2008/08/06 22:03:48 pgj Exp $</releaseinfo> <legalnotice id="trademarks" role="trademarks"> &tm-attrib.freebsd; @@ -79,7 +79,7 @@ <screen>&prompt.user; <userinput>cvs -d <replaceable>path-to-repository</replaceable> init</userinput></screen> <para>This tells <application>CVS</application> to create the - <filename role="directory">CVSROOT</filename> administrative directory, where all the + <filename class="directory">CVSROOT</filename> administrative directory, where all the customization takes place.</para> </sect2> @@ -105,25 +105,25 @@ <sect2> <title>Getting the sources</title> - <para>Now you need to obtain the <filename role="directory">CVSROOT</filename> directory + <para>Now you need to obtain the <filename class="directory">CVSROOT</filename> directory from the FreeBSD repository. This is most easily done by checking it out from a FreeBSD anonymous CVS mirror. See <ulink url="&url.books.handbook;/anoncvs.html">the relevant chapter in the handbook</ulink> for more information. Let us assume that the - sources are stored in <filename role="directory">CVSROOT-freebsd</filename> in the + sources are stored in <filename class="directory">CVSROOT-freebsd</filename> in the current directory.</para> </sect2> <sect2> <title>Copying the FreeBSD scripts</title> - <para>Next, we will copy the FreeBSD <filename role="directory">CVSROOT</filename> + <para>Next, we will copy the FreeBSD <filename class="directory">CVSROOT</filename> sources into your own repository. If you are accustomed to <application>CVS</application>, you might be thinking that you can just import the scripts, in an attempt to make synchronizing with later versions easier. However, it turns out that <application>CVS</application> has a deficiency in this area: - when importing sources into the <filename role="directory">CVSROOT</filename> directory, + when importing sources into the <filename class="directory">CVSROOT</filename> directory, it will not update the needed administrative files. In order to make it recognize those, you will need to checkin each file after importing them, losing the value of <literal>cvs import</literal>. Therefore, @@ -131,7 +131,7 @@ <para>It does not matter if the above paragraph did not make sense to you—the end result is the same. Simply check out your - <filename role="directory">CVSROOT</filename> and copy the FreeBSD files over your + <filename class="directory">CVSROOT</filename> and copy the FreeBSD files over your local (untouched) copies:</para> <screen>&prompt.user; <userinput>cvs -d <replaceable>path-to-your-repository</replaceable> checkout CVSROOT</userinput> @@ -276,7 +276,7 @@ match one of the lines in this file are exempted from this check. You should add expressions to this file as you checkin files that cannot have a revision header. For the purpose of installing the - scripts, it may be best to exclude <filename role="directory">CVSROOT/</filename> + scripts, it may be best to exclude <filename class="directory">CVSROOT/</filename> from header checks.</para> </listitem> @@ -465,7 +465,7 @@ <para><literal>@LOG_FILE_MAP</literal> - change this array as you wish - each regexp is matched on the directory of the commit, and the commit log message gets stored in - the <filename role="directory">commitlogs</filename> subdirectory in + the <filename class="directory">commitlogs</filename> subdirectory in the filename mentioned.</para> </listitem> @@ -494,7 +494,7 @@ <literal>^CVSROOT/</literal>, and add one line with only <literal>^CVSROOT/</literal> on it. After the wrapper is installed, you can add your header to the files in the - <filename role="directory">CVSROOT</filename> directory and restore these lines, + <filename class="directory">CVSROOT</filename> directory and restore these lines, but for now they will only be in the way when you try to commit later on.</para> </step> @@ -532,7 +532,7 @@ <para>The last thing to do before you are finished, is to make sure the commitlogs can be stored. By default these are stored in the repository, in the <filename>commitlogs</filename> subdirectory - of the <filename role="directory">CVSROOT</filename> directory. This directory + of the <filename class="directory">CVSROOT</filename> directory. This directory needs to be created, so do the following:</para> <screen>&prompt.user; <userinput>mkdir commitlogs</userinput> @@ -542,7 +542,7 @@ <para>Now, after careful review, you should commit your changes. Be sure that you have granted yourself access to the - <filename role="directory">CVSROOT</filename> directory in your + <filename class="directory">CVSROOT</filename> directory in your <filename>avail</filename> before you do this, because otherwise you will lock yourself out. So make sure everything is as you intend, and then do the following:</para> @@ -571,8 +571,8 @@ <title>FreeBSD specific setup</title> <para>The FreeBSD project itself uses a slightly different setup, which - also uses files from the <filename role="directory">freebsd</filename> subdirectory of - the FreeBSD <filename role="directory">CVSROOT</filename>. The project uses this because + also uses files from the <filename class="directory">freebsd</filename> subdirectory of + the FreeBSD <filename class="directory">CVSROOT</filename>. The project uses this because of the large number of committers, which all would have to be in the same group. So, a simple wrapper was written which ensures that people have the correct credentials to commit, and then sets the group id @@ -641,7 +641,7 @@ <para>Next up is installing the wrapper to ensure you become the correct group when committing. The sources for this live in <filename>cvswrap.c</filename> in your - <filename role="directory">CVSROOT</filename>.</para> + <filename class="directory">CVSROOT</filename>.</para> <para>Compile the sources that you edited to include the correct paths:</para> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/mh/article.sgml#2 (text+ko) ==== @@ -1,4 +1,4 @@ -<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/mh/article.sgml,v 1.25 2004/08/09 19:49:16 hrs Exp $ --> +<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/mh/article.sgml,v 1.26 2008/08/06 22:03:49 pgj Exp $ --> <!-- FreeBSD Documentation Project --> <!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ @@ -540,7 +540,7 @@ </informalexample> <para>That will grab all the email in your <filename - role="directory">inbox</filename> that was sent to + class="directory">inbox</filename> that was sent to freebsd-hackers or cc'd to that list. The brace options allow you to group search criteria together. This is sometimes very necessary as in the following example</para> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/nanobsd/article.sgml#2 (text+ko) ==== @@ -15,7 +15,7 @@ </author> </authorgroup> - <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/nanobsd/article.sgml,v 1.3 2007/12/21 21:19:54 gabor Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/nanobsd/article.sgml,v 1.4 2008/08/06 22:03:49 pgj Exp $</pubdate> <copyright> <year>2006</year> @@ -104,24 +104,24 @@ <listitem> <para>The configuration file partition, which can be mounted - under the <filename role="directory">/cfg</filename> directory + under the <filename class="directory">/cfg</filename> directory at run time.</para> </listitem> </itemizedlist> <para>These partitions are normally mounted read-only.</para> - <para>The <filename role="directory">/etc</filename> and - <filename role="directory">/var</filename> directories are + <para>The <filename class="directory">/etc</filename> and + <filename class="directory">/var</filename> directories are &man.md.4; (malloc) disks.</para> <para>The configuration file partition persists under the - <filename role="directory">/cfg</filename> directory. It - contains files for <filename role="directory">/etc</filename> + <filename class="directory">/cfg</filename> directory. It + contains files for <filename class="directory">/etc</filename> directory and is briefly mounted read-only right after the system boot, therefore it is required to copy modified files - from <filename role="directory">/etc</filename> back to the - <filename role="directory">/cfg</filename> directory if changes + from <filename class="directory">/etc</filename> back to the + <filename class="directory">/cfg</filename> directory if changes are expected to persist after the system restarts.</para> <example> @@ -136,11 +136,11 @@ <note> <para>The partition containing - <filename role="directory">/cfg</filename> should be mounted + <filename class="directory">/cfg</filename> should be mounted only at boot time and while overriding the configuration files.</para> - <para>Keeping <filename role="directory">/cfg</filename> mounted at + <para>Keeping <filename class="directory">/cfg</filename> mounted at all times is not a good idea, especially if the <application>NanoBSD</application> system runs off a mass storage medium that may be adversely affected by a large number @@ -155,7 +155,7 @@ <para>A <application>NanoBSD</application> image is built using a simple <filename>nanobsd.sh</filename> shell script, which can be found in the - <filename role="directory"><replaceable>/usr</replaceable>/src/tools/tools/nanobsd</filename> + <filename class="directory"><replaceable>/usr</replaceable>/src/tools/tools/nanobsd</filename> directory. This script creates an image, which can be copied on the storage medium using the &man.dd.1; utility.</para> @@ -290,7 +290,7 @@ <para>A more useful example of a customization function is the following, which changes the default size of the - <filename role="directory">/etc</filename> directory + <filename class="directory">/etc</filename> directory from 5MB to 30MB:</para> <programlisting>cust_etc_size () ( @@ -318,7 +318,7 @@ <listitem> <para><literal>cust_install_files</literal> — Installs files from the - <filename role="directory">nanobsd/Files</filename> + <filename class="directory">nanobsd/Files</filename> directory, which contains some useful scripts for system administration.</para> </listitem> @@ -446,7 +446,7 @@ <application>NanoBSD</application> system, it is possible to use either the <filename>updatep1</filename> or <filename>updatep2</filename> script located in the - <filename role="directory">/root</filename> directory, depending + <filename class="directory">/root</filename> directory, depending from which partition is running the current system.</para> <para>According to which services are available on host serving ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/p4-primer/article.sgml#2 (text+ko) ==== @@ -23,7 +23,7 @@ </author> </authorgroup> - <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/p4-primer/article.sgml,v 1.10 2008/04/24 19:44:25 danger Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/p4-primer/article.sgml,v 1.11 2008/08/06 22:03:49 pgj Exp $</pubdate> <legalnotice id="trademarks" role="trademarks"> &tm-attrib.freebsd; @@ -220,13 +220,13 @@ <para>This will map the entire <application>Perforce</application> repository to the - <filename role="directory">Root</filename> directory of your + <filename class="directory">Root</filename> directory of your client. <emphasis>DO NOT USE THIS DEFAULT!</emphasis> The &os; repo is huge, and trying to map and sync it all will take an enormous amount of resources. Instead, only map the section of the repo that you intend to work on. For example, there is the smpng project tree at <filename - role="directory">//depot/projects/smpng</filename>. A + class="directory">//depot/projects/smpng</filename>. A mapping for this might look like:</para> <programlisting>//depot/projects/smpng/... //<replaceable>client</replaceable>/...</programlisting> @@ -306,7 +306,7 @@ <para>You can sync a subset of your tree or client by specifying a relative path to the sync command. For example, to only sync the - <filename role="directory">ufs</filename> directory of the + <filename class="directory">ufs</filename> directory of the <literal>smpng</literal> project, you might do the following:</para> @@ -336,9 +336,9 @@ <quote>depot</quote>) is a single flat tree. Every file, whether a unique creation or a derivative from a branch, is accessible via a simple path under the server <filename - role="directory">//depot</filename> directory. When you create a + class="directory">//depot</filename> directory. When you create a branch, all you are doing is creating a new path under the - <filename role="directory">//depot</filename>. This is in sharp + <filename class="directory">//depot</filename>. This is in sharp contrast to systems like CVS, where each branch lives in the same path as its parent. With <application>Perforce</application>, the server tracks the relationship between the files in the parent and @@ -811,7 +811,7 @@ Every 2 minutes, the CVS server is polled for updates in the HEAD branch, and those updates are committed to <application>Perforce</application> in the <filename - role="directory">//depot/vendor/freebsd/...</filename> tree. This + class="directory">//depot/vendor/freebsd/...</filename> tree. This tree is then available for branching and integrating to derivative projects. Any project that directly modifies that &os; source code should have this tree as its branch parent (or grandparent, @@ -862,19 +862,19 @@ <itemizedlist> <listitem> <para><filename - role="directory">//depot/projects/soc2005/<replaceable>project-name</replaceable>/...</filename></para> + class="directory">//depot/projects/soc2005/<replaceable>project-name</replaceable>/...</filename></para> </listitem> <listitem> <para><filename - role="directory">//depot/projects/soc2006/<replaceable>project-name</replaceable>/...</filename></para> + class="directory">//depot/projects/soc2006/<replaceable>project-name</replaceable>/...</filename></para> </listitem> <listitem> <para><filename - role="directory">//depot/projects/soc2007/<replaceable>project-name</replaceable>/...</filename></para> + class="directory">//depot/projects/soc2007/<replaceable>project-name</replaceable>/...</filename></para> </listitem> <listitem> <para><filename - role="directory">//depot/projects/soc2008/<replaceable>project-name</replaceable>/...</filename></para> + class="directory">//depot/projects/soc2008/<replaceable>project-name</replaceable>/...</filename></para> </listitem> </itemizedlist> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/relaydelay/article.sgml#2 (text+ko) ==== @@ -1,5 +1,5 @@ <!-- - $FreeBSD: doc/en_US.ISO8859-1/articles/relaydelay/article.sgml,v 1.8 2008/02/03 22:05:37 ceri Exp $ + $FreeBSD: doc/en_US.ISO8859-1/articles/relaydelay/article.sgml,v 1.10 2008/08/06 22:03:49 pgj Exp $ --> <!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ @@ -57,7 +57,7 @@ <title>Basic Configuration</title> <para>We need to install the threaded <command>perl</command>. - Install <filename role="port">lang/perl5.8</filename> + Install <filename role="package">lang/perl5.8</filename> with the <makevar>USE_THREADS=yes</makevar> variable set. The current version of <command>perl</command> may need to be removed first; errors will be reported @@ -66,7 +66,7 @@ <note> <para>This will require all ports which require <command>perl</command> to be rebuilt and reinstalled; - <filename role="port">ports-mgmt/portupgrade</filename> + <filename role="package">ports-mgmt/portupgrade</filename> is perfect for this. At least it will point out which ports have been removed and which will need to be reinstalled.</para> @@ -75,21 +75,21 @@ <para>Now for the database server; <application>MySQL</application> is perfect for this sort of work. Install the - <filename role="port">databases/mysql40-server</filename> + <filename role="package">databases/mysql40-server</filename> along with - <filename role="port">databases/p5-DBD-mysql40</filename>. + <filename role="package">databases/p5-DBD-mysql40</filename>. The previous port should imply the installation of - <filename role="port">databases/p5-DBI-137</filename> + <filename role="package">databases/p5-DBI-137</filename> so that knocks off another step.</para> <para>Install the <command>perl</command> based portable - server plugin, <filename role="port">net/p5-Net-Daemon</filename> + server plugin, <filename role="package">net/p5-Net-Daemon</filename> port. Most of these port installations should have been straight forward. The next step will be more involved.</para> <para>Now install the - <filename role="port">mail/p5-Sendmail-Milter</filename> + <filename role="package">mail/p5-Sendmail-Milter</filename> port. As of this writing the <filename>Makefile</filename> contains a line beginning with <makevar>BROKEN</makevar>, just remove it or comment it out. It is only marked @@ -141,7 +141,7 @@ is beyond the scope of this document.</para> <para>Change the working directory to the - <filename role="directory">relaydelay-0.04</filename> + <filename class="directory">relaydelay-0.04</filename> directory:</para> <screen>&prompt.root; <userinput>cd relaydelay-0.04</userinput></screen> @@ -164,7 +164,7 @@ <para>If everything worked correctly a new file, <filename>relaydelay.log</filename>, should exist in - <filename role="directory">/var/log</filename>. It should + <filename class="directory">/var/log</filename>. It should contain something similar to the following text:</para> <programlisting>Loaded Config File: /etc/mail/relaydelay.conf @@ -192,7 +192,7 @@ <ulink url="http://lists.puremagic.com/pipermail/greylist-users/2003-November/000327.html">; http://lists.puremagic.com/pipermail/greylist-users/2003-November/000327.html</ulink>; and save it in the - <filename role="directory">relaydelay-0.04</filename> + <filename class="directory">relaydelay-0.04</filename> directory. In the following examples this script is referred to as <filename>addlist.pl</filename>.</para> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/remote-install/article.sgml#2 (text+ko) ==== @@ -17,7 +17,7 @@ <!-- 11 April 2008 --> </author> - <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/remote-install/article.sgml,v 1.5 2008/05/03 08:26:12 loader Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/remote-install/article.sgml,v 1.6 2008/08/06 22:03:49 pgj Exp $</pubdate> <legalnotice id="trademarks" role="trademarks"> &tm-attrib.freebsd; @@ -229,10 +229,10 @@ <para>The first step is to mount the &os; installation <acronym>CD</acronym>, or the installation <acronym>ISO</acronym> image to <filename - role="directory">/cdrom</filename>. For the sake of example, + class="directory">/cdrom</filename>. For the sake of example, in this article we will assume that you have downloaded the &os; 7.0-RELEASE <acronym>ISO</acronym>. Mounting this ISO image to - the <filename role="directory">/cdrom</filename> directory is + the <filename class="directory">/cdrom</filename> directory is easy with the &man.mdconfig.8; utility:</para> <screen>&prompt.root; <userinput>mdconfig -a -t vnode -u 10 -f <replaceable>7.0-RELEASE-amd64-disc1.iso</replaceable></userinput> @@ -247,7 +247,7 @@ <para>The above <command>make</command> command has to be run from the top level of the <application>mfsBSD</application> directory tree, i.e. <filename - role="directory">~/mfsbsd-1.0-beta1/</filename>.</para> + class="directory">~/mfsbsd-1.0-beta1/</filename>.</para> </note> </sect2> @@ -317,9 +317,9 @@ introduction, this article will present how to set up a system with RAID-1 and <application>ZFS</application> capabilities. Our set up will consist of a small &man.gmirror.8; mirrored - <filename role="directory">/</filename> (root), <filename - role="directory">/usr</filename> and <filename - role="directory">/var</filename> file systems, and the rest of + <filename class="directory">/</filename> (root), <filename + class="directory">/usr</filename> and <filename + class="directory">/var</filename> file systems, and the rest of the disk space will be allocated for a &man.zpool.8; mirrored <application>ZFS</application> file system. Please note, that the <application>ZFS</application> file system will be @@ -363,11 +363,11 @@ to the &man.bsdlabel.8; manual page in order to find out how to create partitions. Create partitions <literal>a</literal> for <filename - role="directory">/</filename> (root) file system, + class="directory">/</filename> (root) file system, <literal>b</literal> for swap, <literal>d</literal> for - <filename role="directory">/var</filename>, + <filename class="directory">/var</filename>, <literal>e</literal> for <filename - role="directory">/usr</filename> and finally + class="directory">/usr</filename> and finally <literal>f</literal> which will later be used for <application>ZFS</application>.</para> </callout> @@ -417,7 +417,7 @@ <keycap>Enter</keycap>. With the help of arrow keys, move the cursor on the <literal>Install Root</literal> item, press <keycap>Space</keycap> and change it to <filename - role="directory">/mnt</filename>. Press + class="directory">/mnt</filename>. Press <keycap>Enter</keycap> to submit your changes and exit the <guimenuitem>Options</guimenuitem> menu by pressing <keycap>q</keycap>.</para> @@ -474,7 +474,7 @@ <itemizedlist> <listitem> <para>Copy the <literal>GENERIC</literal> kernel to the - <filename role="directory">/boot/kernel</filename> + <filename class="directory">/boot/kernel</filename> directory:</para> <screen>&prompt.root; <userinput>cp -Rp /boot/GENERIC/* /boot/kernel</userinput></screen> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/Makefile#2 (text+ko) ==== @@ -1,5 +1,5 @@ # -# $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/Makefile,v 1.23 2006/10/18 19:34:16 danger Exp $ +# $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/Makefile,v 1.24 2008/08/10 00:20:27 pgj Exp $ # # Build the FreeBSD Developers' Handbook. # @@ -25,7 +25,6 @@ # SGML content SRCS= book.sgml -SRCS+= dma/chapter.sgml SRCS+= introduction/chapter.sgml SRCS+= ipv6/chapter.sgml SRCS+= kernelbuild/chapter.sgml ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/book.sgml#2 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/book.sgml,v 1.55 2007/09/20 11:56:52 remko Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/book.sgml,v 1.56 2008/08/10 00:20:27 pgj Exp $ --> <!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ @@ -85,7 +85,6 @@ <part id="kernel"> <title>Kernel</title> - &chap.dma; &chap.kernelbuild; &chap.kerneldebug; ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/chapters.ent#2 (text+ko) ==== @@ -6,7 +6,7 @@ Chapters should be listed in the order in which they are referenced. - $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/chapters.ent,v 1.22 2006/10/16 19:15:36 danger Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/chapters.ent,v 1.23 2008/08/10 00:20:27 pgj Exp $ --> <!-- Part one --> @@ -22,7 +22,6 @@ <!ENTITY chap.ipv6 SYSTEM "ipv6/chapter.sgml"> <!-- Part three - Kernel --> -<!ENTITY chap.dma SYSTEM "dma/chapter.sgml"> <!ENTITY chap.kernelbuild SYSTEM "kernelbuild/chapter.sgml"> <!ENTITY chap.kerneldebug SYSTEM "kerneldebug/chapter.sgml"> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.sgml#3 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.sgml,v 1.2 2008/07/10 22:14:48 miwi Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.sgml,v 1.3 2008/08/06 22:03:49 pgj Exp $ --> <chapter id="kernelbuild"> @@ -37,7 +37,7 @@ <para>Up to version 4.X of &os; this was the recommended way to build a new kernel. It can still be used on newer versions (instead of the <quote>buildkernel</quote> target of the toplevel - <filename role="directory">/usr/src/</filename> makefiles). + <filename class="directory">/usr/src/</filename> makefiles). Building the kernel this way may be useful when working on the kernel code and it may actually be faster than the <quote>New</quote> procedure when only a single option or two were ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml#2 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml,v 1.15 2006/01/05 20:03:35 delphij Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.sgml,v 1.16 2008/08/03 09:50:20 danger Exp $ --> <chapter id="sockets"> @@ -966,6 +966,7 @@ * Programmed by G. Adam Stanislav */ #include <stdio.h> +#include <string.h> #include <sys/types.h> #include <sys/socket.h> #include <netinet/in.h> @@ -1181,6 +1182,7 @@ * June 19, 2001 */ #include <stdio.h> +#include <string.h> #include <time.h> #include <unistd.h> #include <sys/types.h> @@ -1582,7 +1584,7 @@ host = (argc > 1) ? (char *)argv[1] : "time.nist.gov"; if ((he = gethostbyname(host)) == NULL) { - perror(host); + herror(host); return 2; } ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml#3 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml,v 1.49 2008/07/23 20:39:55 pgj Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/tools/chapter.sgml,v 1.50 2008/08/06 20:44:11 pgj Exp $ --> <chapter id="tools"> @@ -138,10 +138,10 @@ <para>The Bywater Basic Interpreter can be found in the Ports Collection as - <filename role="port">lang/bwbasic</filename> + <filename role="package">lang/bwbasic</filename> and the Phil Cockroft's Basic Interpreter (formerly Rabbit Basic) is available as - <filename role="port">lang/pbasic</filename>.</para> + <filename role="package">lang/pbasic</filename>.</para> </listitem> </varlistentry> @@ -163,14 +163,14 @@ <para>Various implementations of Lisp that can run on &unix; systems are available in the Ports Collection for &os;. GNU Common Lisp can be found as - <filename role="port">lang/gcl</filename>. CLISP + <filename role="package">lang/gcl</filename>. CLISP by Bruno Haible and Michael Stoll is available as - <filename role="port">lang/clisp</filename>. + <filename role="package">lang/clisp</filename>. For CMUCL, which includes a highly-optimizing compiler too, or simpler Lisp implementations like SLisp, which implements most of the Common Lisp constructs in a few hundred lines of C code, - <filename role="port">lang/cmucl</filename> and - <filename role="port">lang/slisp</filename> are available + <filename role="package">lang/cmucl</filename> and + <filename role="package">lang/slisp</filename> are available respectively.</para> </listitem> </varlistentry> @@ -184,7 +184,7 @@ writing <acronym>CGI</acronym> scripts.</para> <para>Perl is available in the Ports Collection as - <filename role="port">lang/perl5</filename> for all + <filename role="package">lang/perl5</filename> for all &os; releases, and is installed as <command>/usr/bin/perl</command> in the base system 4.X releases.</para> </listitem> @@ -201,12 +201,12 @@ abstraction to be used in research work.</para> <para>Scheme is available from the Ports Collection as - <filename role="port">lang/elk</filename> for the + <filename role="package">lang/elk</filename> for the Elk Scheme Interpreter. The MIT Scheme Interpreter can be found in - <filename role="port">lang/mit-scheme</filename> + <filename role="package">lang/mit-scheme</filename> and the SCM Scheme Interpreter in - <filename role="port">lang/scm</filename>.</para> + <filename role="package">lang/scm</filename>.</para> </listitem> </varlistentry> @@ -218,7 +218,7 @@ facilities for processing strings and structures. The version of Icon for &os; can be found in the Ports Collection as - <filename role="port">lang/icon</filename>.</para> + <filename role="package">lang/icon</filename>.</para> </listitem> </varlistentry> @@ -235,7 +235,7 @@ <para>The latest version of Logo for &os; is available from the Ports Collection in - <filename role="port">lang/logo</filename>.</para> + <filename role="package">lang/logo</filename>.</para> </listitem> </varlistentry> @@ -253,7 +253,7 @@ <para>The latest version of Python is available from the Ports Collection in - <filename role="port">lang/python</filename>.</para> + <filename role="package">lang/python</filename>.</para> </listitem> </varlistentry> @@ -268,7 +268,7 @@ programs.</para> <para>Ruby is available from the Ports Collection as - <filename role="port">lang/ruby18</filename>.</para> + <filename role="package">lang/ruby18</filename>.</para> </listitem> </varlistentry> @@ -285,7 +285,7 @@ <para>Various versions of Tcl are available as ports for &os;. The latest version, Tcl 8.4, can be found in - <filename role="port">lang/tcl84</filename>.</para> + <filename role="package">lang/tcl84</filename>.</para> </listitem> </varlistentry> </variablelist> @@ -328,14 +328,14 @@ support in the base system, but both GNU Pascal Compiler (GPC) and the Free Pascal Compiler are available in the Ports Collection as - <filename role="port">lang/gpc</filename> and - <filename role="port">lang/fpc</filename>.</para> + <filename role="package">lang/gpc</filename> and + <filename role="package">lang/fpc</filename>.</para> <para>As the edit-compile-run-debug cycle is rather tedious when using separate programs, many commercial compiler makers have produced Integrated Development Environments (<acronym>IDE</acronym>s for short). FreeBSD does not include - an IDE in the base system, but <filename role="port">devel/kdevelop</filename> is + an IDE in the base system, but <filename role="package">devel/kdevelop</filename> is available in the Ports Collection and many use <application>Emacs</application> for this purpose. Using <application>Emacs</application> as an IDE is discussed in @@ -1431,7 +1431,7 @@ <para>Finally, if you find its text-based command-prompt style off-putting, there is a graphical front-end for it - (<filename role="port">devel/xxgdb</filename>) in the Ports + (<filename role="package">devel/xxgdb</filename>) in the Ports Collection.</para> <para>This section is intended to be an introduction to using @@ -1759,7 +1759,7 @@ <para>And doubtless many more that I have overlooked.</para> <para>Emacs can be installed on &os; using - the <filename role="port">editors/emacs</filename> + the <filename role="package">editors/emacs</filename> port.</para> <para>Once it is installed, start it up and do <userinput>C-h ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#6 (text+ko) ==== @@ -12,7 +12,7 @@ <corpauthor>The &os; Documentation Project</corpauthor> - <pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1077 2008/07/23 21:32:46 pgj Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1097 2008/08/09 23:19:31 pgj Exp $</pubdate> <copyright> <year>1995</year> @@ -368,7 +368,7 @@ not capable of identifying the difference between a real problem and a temporary problem, you should not use &os.current;. This branch sometimes evolves quite quickly - and can be un-buildable for a number of days at a time. + and can be un-buildable sometimes. People that use &os.current; are expected to be able to analyze any problems and only report them if they are deemed to be mistakes rather than <quote>glitches</quote>. @@ -425,7 +425,7 @@ <para>Official snapshots are generated each month on a regular basis for all actively developed branches. There are also daily snapshot builds of the popular &arch.i386; and - &arch.amd64 branches, hosted on <ulink + &arch.amd64; branches, hosted on <ulink url="http://snapshots.us.freebsd.org/"></ulink>. </para> </answer> @@ -630,12 +630,7 @@ <answer> <para>The project produces a wide range of documentation, available online from this link: <ulink - url="http://www.FreeBSD.org/docs.html"></ulink>. The same - documents are available as packages, that you can easily - install on your &os; system. More details on documentation - packages can be found in the next paragraphs.</para> - - <para>In addition, <link + url="http://www.FreeBSD.org/docs.html"></ulink>. In addition, <link linkend="bibliography">the Bibliography</link> at the end of this FAQ, and <ulink url="&url.books.handbook;/bibliography.html">the one in the Handbook</ulink> @@ -668,7 +663,7 @@ <listitem> <para>The document's language and encoding. These are based on the locale names you will find under - <filename>/usr/share/locale</filename> on your &os; + <filename class="directory">/usr/share/locale</filename> on your &os; system. The current languages and encodings that we have for documentation are as follows:</para> @@ -686,13 +681,13 @@ <row> <entry><literal>en_US.ISO8859-1</literal></entry> - <entry>US English</entry> + <entry>English (United States)</entry> </row> <row> <entry><literal>bn_BD.ISO10646-1</literal></entry> - <entry>Bengali (or Bangla)</entry> + <entry>Bengali or Bangla (Bangladesh)</entry> </row> <row> @@ -704,7 +699,7 @@ <row> <entry><literal>de_DE.ISO8859-1</literal></entry> - <entry>German</entry> + <entry>German (Germany)</entry> </row> <row> @@ -716,37 +711,37 @@ <row> <entry><literal>es_ES.ISO8859-1</literal></entry> - <entry>Spanish</entry> + <entry>Spanish (Spain)</entry> </row> <row> <entry><literal>fr_FR.ISO8859-1</literal></entry> - <entry>French</entry> + <entry>French (France)</entry> >>> TRUNCATED FOR MAIL (1000 lines) <<<
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200808110932.m7B9WN8q082272>