PERFORCE change 181686 for review
Rene Ladan
rene at FreeBSD.org
Sun Aug 1 16:28:09 UTC 2010
http://p4web.freebsd.org/@@181686?ac=10
Change 181686 by rene at rene_acer on 2010/08/01 16:27:47
IFC
Affected files ...
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/casestudy-argentina.com/article.sgml#2 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#32 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#65 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#48 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cups/article.sgml#3 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/euro/article.sgml#2 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/ldap-auth/article.sgml#3 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/linux-comparison/article.sgml#2 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/linux-emulation/article.sgml#3 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/linux-users/article.sgml#5 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#25 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/problem-reports/article.sgml#5 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/releng-packages/article.sgml#2 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/serial-uart/article.sgml#2 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/storage-devices/article.sgml#2 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#28 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#10 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml#11 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#7 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml#14 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#32 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#19 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#83 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#41 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/solid-state/article.sgml#17 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/cutting-edge/chapter.sgml#35 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.sgml#20 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/install/chapter.sgml#13 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mirrors/chapter.sgml#53 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/x11/chapter.sgml#28 integrate
.. //depot/projects/docproj_nl/share/images/articles/releng/branches-releng8.pic#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/config-country.scr#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/dist-set.scr#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/dist-set2.scr#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/docmenu1.scr#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/main-doc.scr#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/main-keymap.scr#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/main-options.scr#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/main-std.scr#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/main1.scr#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/media.scr#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/options.scr#2 integrate
.. //depot/projects/docproj_nl/share/images/books/handbook/install/sysinstall-exit.scr#2 integrate
.. //depot/projects/docproj_nl/share/pgpkeys/andrew.key#1 branch
.. //depot/projects/docproj_nl/share/pgpkeys/bapt.key#1 branch
.. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys-developers.sgml#42 integrate
.. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys.ent#39 integrate
.. //depot/projects/docproj_nl/share/pgpkeys/tijl.key#1 branch
.. //depot/projects/docproj_nl/share/sgml/freebsd.ent#17 integrate
.. //depot/projects/docproj_nl/share/sgml/man-refs.ent#28 integrate
.. //depot/projects/docproj_nl/share/sgml/mirrors.xml#20 integrate
.. //depot/projects/docproj_nl/www/en/cgi/man.cgi#15 integrate
.. //depot/projects/docproj_nl/www/en/cgi/monthly.cgi#2 integrate
.. //depot/projects/docproj_nl/www/en/cgi/ports.cgi#4 integrate
.. //depot/projects/docproj_nl/www/en/developers.sgml#39 integrate
.. //depot/projects/docproj_nl/www/en/news/status/Makefile#10 integrate
.. //depot/projects/docproj_nl/www/en/news/status/report-2010-04-2010-06.xml#1 branch
.. //depot/projects/docproj_nl/www/en/news/status/status.sgml#11 integrate
.. //depot/projects/docproj_nl/www/en/releases/8.1R/Makefile#2 integrate
.. //depot/projects/docproj_nl/www/en/releases/8.1R/announce.sgml#1 branch
.. //depot/projects/docproj_nl/www/en/releases/8.1R/docbook.css#2 integrate
.. //depot/projects/docproj_nl/www/en/releases/8.1R/errata.html#1 branch
.. //depot/projects/docproj_nl/www/en/releases/8.1R/hardware.html#1 branch
.. //depot/projects/docproj_nl/www/en/releases/8.1R/readme.html#1 branch
.. //depot/projects/docproj_nl/www/en/releases/8.1R/relnotes-detailed.html#1 branch
.. //depot/projects/docproj_nl/www/en/releases/8.1R/relnotes.sgml#1 branch
.. //depot/projects/docproj_nl/www/en/releases/8.1R/schedule.sgml#3 integrate
.. //depot/projects/docproj_nl/www/en/releases/index.sgml#10 integrate
.. //depot/projects/docproj_nl/www/en/releng/index.sgml#37 integrate
.. //depot/projects/docproj_nl/www/en/search/web.atoz#4 integrate
.. //depot/projects/docproj_nl/www/nl/administration.sgml#21 integrate
.. //depot/projects/docproj_nl/www/share/sgml/commercial.consult.xml#24 integrate
.. //depot/projects/docproj_nl/www/share/sgml/commercial.hardware.xml#6 integrate
.. //depot/projects/docproj_nl/www/share/sgml/commercial.software.xml#5 integrate
.. //depot/projects/docproj_nl/www/share/sgml/events.xml#28 integrate
.. //depot/projects/docproj_nl/www/share/sgml/news.xml#85 integrate
.. //depot/projects/docproj_nl/www/share/sgml/release.ent#28 integrate
.. //depot/projects/docproj_nl/www/share/sgml/usergroups.xml#14 integrate
Differences ...
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/casestudy-argentina.com/article.sgml#2 (text+ko) ====
@@ -22,7 +22,7 @@
</author>
</authorgroup>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/casestudy-argentina.com/article.sgml,v 1.2 2005/09/04 22:03:59 joel Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/casestudy-argentina.com/article.sgml,v 1.3 2010/07/31 11:06:17 pgj Exp $</pubdate>
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
@@ -296,7 +296,7 @@
<para>With the adoption of FreeBSD, there was almost no additional
effort necessary to setup a working Apache, PHP and MySQL
environment in minutes. Even the upgrades from PHP4 to PHP5 were
- painless. The ports system was again extemely useful in these
+ painless. The ports system was again extremely useful in these
cases, and permitted us to do things like compress text and html
contents in Apache with just a few lines of documentation. In
addition, we have experienced excellent performance and
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#32 (text+ko) ====
@@ -9,7 +9,7 @@
<corpauthor>The &os; Documentation Project</corpauthor>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.289 2010/06/06 09:34:40 romain Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.290 2010/07/31 10:39:08 pgj Exp $</pubdate>
<copyright>
<year>1999</year>
@@ -1099,7 +1099,7 @@
and <filename>doc/share/pgpkeys/pgpkeys-developers.sgml</filename>.</para>
<para>&a.des; has
- written a shell script to make this extremely simple. See the
+ written a shell script (<filename>doc/share/pgpkeys/addkey.sh</filename>) to make this extremely simple. See the
<ulink
url="http://cvsweb.FreeBSD.org/doc/share/pgpkeys/README">README</ulink>
file for more information.</para>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#65 (text+ko) ====
@@ -1,4 +1,4 @@
-<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.928 2010/07/13 08:32:07 ashish Exp $ -->
+<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.934 2010/07/29 19:06:55 glarkin Exp $ -->
<!--
NOTE TO COMMITTERS: Contributors lists are sorted in alphabetical
order by first name.
@@ -818,11 +818,6 @@
</listitem>
<listitem>
- <para>Andrew Turner
- <email>andrew+ports at fubar.geek.nz</email></para>
- </listitem>
-
- <listitem>
<para>Andrew V. Stesin
<email>stesin at elvisti.kiev.ua</email></para>
</listitem>
@@ -1083,11 +1078,6 @@
</listitem>
<listitem>
- <para>Baptiste Daroussin
- <email>baptiste.daroussin at gmail.com</email></para>
- </listitem>
-
- <listitem>
<para>Barry Bierbauch
<email>pivrnec at vszbr.cz</email></para>
</listitem>
@@ -5157,6 +5147,11 @@
</listitem>
<listitem>
+ <para>Katalin Konkoly
+ <email>katalin.konkoly at gmail.com</email></para>
+ </listitem>
+
+ <listitem>
<para>Katsura Matsumoto
<email>katsura at cc.osaka-kyoiku.ac.jp</email></para>
</listitem>
@@ -8462,6 +8457,11 @@
</listitem>
<listitem>
+ <para>Ruslan Mahmatkhanov
+ <email>cvs-src at yandex.ru</email></para>
+ </listitem>
+
+ <listitem>
<para>Ruslan Shevchenko
<email>rssh at cam.grad.kiev.ua</email></para>
</listitem>
@@ -8482,6 +8482,11 @@
</listitem>
<listitem>
+ <para>Rusty Nejdl
+ <email>rnejdl at ringofsaturn.com</email></para>
+ </listitem>
+
+ <listitem>
<para>Ryan Grove
<email>ryan at wonko.com</email></para>
</listitem>
@@ -9603,11 +9608,6 @@
</listitem>
<listitem>
- <para>Tijl Coosemans
- <email>tijl at ulyssis.org</email></para>
- </listitem>
-
- <listitem>
<para>Tillman Hodgson
<email>tillman at seekingfire.com</email></para>
</listitem>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#48 (text+ko) ====
@@ -1,4 +1,4 @@
-<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.301 2010/07/16 00:38:23 jsa Exp $ -->
+<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.304 2010/07/28 14:51:14 bapt Exp $ -->
<!--
NOTE TO NEW COMMITTERS: Core and committers lists are sorted in
alphabetical order by last name. Please keep in mind that fact while
@@ -263,6 +263,10 @@
</listitem>
<listitem>
+ <para>&a.tijl;</para>
+ </listitem>
+
+ <listitem>
<para>&a.alc;</para>
</listitem>
@@ -283,6 +287,10 @@
</listitem>
<listitem>
+ <para>&a.bapt;</para>
+ </listitem>
+
+ <listitem>
<para>&a.davidc;</para>
</listitem>
@@ -1591,6 +1599,10 @@
</listitem>
<listitem>
+ <para>&a.andrew;</para>
+ </listitem>
+
+ <listitem>
<para>&a.gonzo;</para>
</listitem>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cups/article.sgml#3 (text+ko) ====
@@ -7,7 +7,7 @@
<article>
<articleinfo>
<title>CUPS on FreeBSD</title>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/cups/article.sgml,v 1.3 2008/10/24 23:18:46 pgj Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/cups/article.sgml,v 1.4 2010/07/31 11:06:17 pgj Exp $</pubdate>
<authorgroup>
<author>
<firstname>Chess</firstname>
@@ -141,7 +141,7 @@
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
+ local <acronym>IP</acronym> address 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.
@@ -263,7 +263,7 @@
listed below. Please note that this sample
<filename>cupsd.conf</filename> file sacrifices security for
easier configuration; once the administrator successfully
- connnects to the <application>CUPS</application> server and
+ connects to the <application>CUPS</application> server and
configures the clients, it is advisable to revisit this
configuration file and begin locking down access.</para>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/euro/article.sgml#2 (text+ko) ====
@@ -28,7 +28,7 @@
<holder>The FreeBSD Documentation Project</holder>
</copyright>
- <pubdate role="rcs">$FreeBSD: doc/en_US.ISO8859-1/articles/euro/article.sgml,v 1.11 2005/08/18 07:53:23 pav Exp $</pubdate>
+ <pubdate role="rcs">$FreeBSD: doc/en_US.ISO8859-1/articles/euro/article.sgml,v 1.12 2010/07/31 11:08:14 pgj Exp $</pubdate>
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
@@ -193,7 +193,7 @@
<para>Most keyboard maps should already be set up correctly. I.e: If you
have a german keyboard and your Umlaut keys are working, you can
safely skip this section since the keyboard already maps whatever key
- combination is necessary (e.g.: <keycombo action=simul><keycap>Alt
+ combination is necessary (e.g.: <keycombo action="simul"><keycap>Alt
Gr</keycap><keycap>e</keycap></keycombo>) to decimal value 164.
If running into problems, the best way to check is to take a look at
<filename>/usr/share/syscons/keymaps/*.kbd</filename>. The format of
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/ldap-auth/article.sgml#3 (text+ko) ====
@@ -17,7 +17,7 @@
</author>
</authorgroup>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/ldap-auth/article.sgml,v 1.2 2008/09/17 19:29:18 blackend Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/ldap-auth/article.sgml,v 1.3 2010/07/31 11:06:18 pgj Exp $</pubdate>
<copyright>
<year>2007</year>
@@ -31,7 +31,7 @@
</legalnotice>
<abstract>
- <para>This document is indended as a guide for the configuration
+ <para>This document is intended as a guide for the configuration
of an LDAP server (principally an <application>OpenLDAP</application>
server) for authentication on &os;. This is useful for situations
where many servers need the same user accounts, for example as a
@@ -286,7 +286,7 @@
<title>Entries in the Database</title>
<para>Authentication against an LDAP directory is generally
- accomplished by attempting to bind to the directory as the connectin user.
+ accomplished by attempting to bind to the directory as the connecting user.
This is done by establishing a <quote>simple</quote>
bind on the directory with the user name supplied. If there is an
entry with the <literal>uid</literal> equal to the user name and
@@ -344,7 +344,7 @@
uid: tuser
cn: tuser</programlisting>
- <para>I start my LDAP users' UIDs at 10000 to avoid colisions with
+ <para>I start my LDAP users' UIDs at 10000 to avoid collisions with
system accounts; you can configure whatever number you wish here,
as long as it's less than 65536.</para>
@@ -456,7 +456,7 @@
<para>With this configuration you should be able to authenticate
a user against an LDAP directory.
<application>PAM</application> will perform a bind with your
- credentails, and if successful will tell
+ credentials, and if successful will tell
<application>SSH</application> to allow access.</para>
<para>However it is not a good idea to allow
@@ -890,7 +890,7 @@
<option>-signkey</option>:</para>
<example id="ca-sign">
- <title>Signing as a certificate authorty</title>
+ <title>Signing as a certificate authority</title>
<screen>&prompt.user; <userinput>openssl x509 -req -days 1024 \
-in ldap-server-one.csr -CA root.crt -CAkey root.key \
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/linux-comparison/article.sgml#2 (text+ko) ====
@@ -28,7 +28,7 @@
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
- $FreeBSD: doc/en_US.ISO8859-1/articles/linux-comparison/article.sgml,v 1.10 2006/08/08 19:35:13 jcamou Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/articles/linux-comparison/article.sgml,v 1.11 2010/07/31 11:12:17 pgj Exp $
-->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
@@ -54,7 +54,7 @@
<holder role="mailto:dru at isecom.org">Dru Lavigne</holder>
</copyright>
- <releaseinfo>$FreeBSD: doc/en_US.ISO8859-1/articles/linux-comparison/article.sgml,v 1.10 2006/08/08 19:35:13 jcamou Exp $</releaseinfo>
+ <releaseinfo>$FreeBSD: doc/en_US.ISO8859-1/articles/linux-comparison/article.sgml,v 1.11 2010/07/31 11:12:17 pgj Exp $</releaseinfo>
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
@@ -546,6 +546,3 @@
</orderedlist>
</sect1>
</article>
-
-
-
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/linux-emulation/article.sgml#3 (text+ko) ====
@@ -1,4 +1,4 @@
-<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/linux-emulation/article.sgml,v 1.3 2009/07/21 15:19:50 maxim Exp $ -->
+<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/linux-emulation/article.sgml,v 1.4 2010/07/31 11:06:18 pgj Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
@@ -265,8 +265,8 @@
be usable these days.</para>
<para>&os; development happens in a central CVS repository where only
- a selected team of so called commiters can write. This repository
- posseses several branches; the most interesting are the HEAD branch,
+ a selected team of so called committers can write. This repository
+ possesses several branches; the most interesting are the HEAD branch,
in &os; nomenclature called -CURRENT, and RELENG_X branches, where X
stands for a number indicating a major version of &os;. As of
December 2006, there are development branches for 6.X development
@@ -799,7 +799,7 @@
<title>Atomic operations and memory barriers</title>
<para>Atomic operations are implemented through a set of functions
- performing simple aritmetics on memory operands in an atomic way
+ performing simple arithmetics on memory operands in an atomic way
with respect to external events (interrupts, preemption, etc.).
Atomic operations can guarantee atomicity just on small data types
(in the magnitude order of the <literal>.long.</literal>
@@ -1083,7 +1083,7 @@
internal to VFS. The &man.namei.9; syscall can cope with symlinks,
absolute and relative paths. When a path is looked up using
&man.namei.9; it is inputed to the name cache. This behaviour can
- be supressed. This routine is used all over the kernel and its
+ be suppressed. This routine is used all over the kernel and its
performance is very critical.</para>
</sect4>
@@ -1735,7 +1735,7 @@
unused. Segments are either stored in a global GDT table or in a
local LDT table. LDT is accessed via an entry in the GDT. The
LDT can store more types of segments. LDT can be per process.
- Both tables define upto 8191 entries.</para>
+ Both tables define up to 8191 entries.</para>
</sect3>
<sect3 id="linux-i386">
@@ -1826,7 +1826,7 @@
fast (the condition variables will probably end up being implemented
using signals, i.e. not fast) and simple. In 1:1 model, the
situation is also quite clear - the threads must be synchronized
- using kernel facilites (which is very slow because a syscall must be
+ using kernel facilities (which is very slow because a syscall must be
performed). The mixed M:N scenario just combines the first and
second approach or rely solely on kernel. Threads synchronization is
a vital part of thread-enabled programming and its performance can
@@ -2121,7 +2121,7 @@
performed, is. When the <varname>filename</varname> parameter is
absolute <varname>dirfd</varname> is ignored but when the path to
the file is relative, it comes to the play. The
- <varname>dirfd</varname> paramtere is a directory relative to which
+ <varname>dirfd</varname> parameter is a directory relative to which
the relative pathname is checked. The <varname>dirfd</varname>
parameter is a file descriptor of some directory or
<literal>AT_FDCWD</literal>. So for example the
@@ -2236,7 +2236,7 @@
introduce a small infrastructure. We have the ldebug facility, which
tells whether a given syscall should be debugged (settable via a
sysctl). For printing we have LMSG and ARGS macros. Those are used
- for altering a printable string for uniform debuging messages.</para>
+ for altering a printable string for uniform debugging messages.</para>
</sect3>
</sect2>
</sect1>
@@ -2256,7 +2256,7 @@
the &linux; programs included in &os; Ports Collection with
Fedora Core 4 at 2.6.16 and there are some rudimentary
reports of success with Fedora Core 6 at 2.6.16. The
- Fedora Core 6 linux_base was recently commited enabling
+ Fedora Core 6 linux_base was recently committed enabling
some further testing of the emulation layer and giving us some more
hints where we should put our effort in implementing missing
stuff.</para>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/linux-users/article.sgml#5 (text+ko) ====
@@ -19,7 +19,7 @@
<holder>The FreeBSD Documentation Project</holder>
</copyright>
- <releaseinfo>$FreeBSD: doc/en_US.ISO8859-1/articles/linux-users/article.sgml,v 1.8 2009/07/04 20:07:29 blackend Exp $</releaseinfo>
+ <releaseinfo>$FreeBSD: doc/en_US.ISO8859-1/articles/linux-users/article.sgml,v 1.10 2010/07/31 11:12:17 pgj Exp $</releaseinfo>
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
@@ -135,7 +135,7 @@
the &os; Handbook: <ulink
url="&url.base;/doc/en_US.ISO8859-1/books/handbook/packages-using.html">Using the Packages System</ulink>.</para>
</sect2>
-
+
<sect2 id="ports">
<title>Ports</title>
@@ -212,7 +212,7 @@
<listitem><simpara>You can apply your own patches if you are so
inclined.</simpara></listitem>
</itemizedlist>
-
+
<para>If you do not have any special requirements, packages will
probably suit your situation just fine. If you may ever need to
customize, ports are the way to go. (And remember, if you
@@ -278,7 +278,7 @@
<filename>/etc/rc.conf</filename>. Also, when installing additional
applications be sure to review the documentation to determine how to
enable any associated services.</para>
-
+
<para>The following snippet from <filename>/etc/rc.conf</filename> enables
&man.sshd.8; and <application>Apache 2.2</application>. It also
specifies that <application>Apache</application> should be started
@@ -295,10 +295,10 @@
system):</para>
<screen>&prompt.root; <userinput><replaceable>/etc/rc.d/sshd</replaceable> start</userinput></screen>
-
+
<para>If a service has not been enabled it can be started from the
command line using <option>forcestart</option>:</para>
-
+
<screen>&prompt.root; <userinput><replaceable>/etc/rc.d/sshd</replaceable> forcestart</userinput></screen>
</sect1>
@@ -328,7 +328,7 @@
media: Ethernet autoselect (1000baseTX <full-duplex>)
status: active</screen>
</sect2>
-
+
<sect2 id="ipaddress">
<title>IP Configuration</title>
@@ -355,7 +355,7 @@
<para>Like <application>IPTABLES</application> in &linux;, &os; also offers
a kernel level firewall; actually &os; offers three firewalls:</para>
-
+
<itemizedlist>
<listitem><simpara><ulink url="&url.base;/doc/en_US.ISO8859-1/books/handbook/firewalls-ipfw.html">IPFIREWALL</ulink></simpara></listitem>
<listitem><simpara><ulink url="&url.base;/doc/en_US.ISO8859-1/books/handbook/firewalls-ipf.html">IPFILTER</ulink></simpara></listitem>
@@ -584,7 +584,7 @@
<para>Hopefully this document has provided you with enough to get
started with &os;. Be sure to take a look at the <ulink
url="&url.base;/doc/en_US.ISO8859-1/books/handbook/index.html">&os; Handbook</ulink>
- for more indepth coverage of the topics touched on as well as
+ for more in depth coverage of the topics touched on as well as
the many topics not covered in this document.</para>
</sect1>
</article>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#25 (text+ko) ====
@@ -11,7 +11,7 @@
<corpauthor>The &os; Ports Management Team</corpauthor>
</authorgroup>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.58 2010/06/01 01:30:13 linimon Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.59 2010/07/31 11:06:18 pgj Exp $</pubdate>
<copyright>
<year>2003</year>
@@ -64,7 +64,7 @@
<filename>/usr/ports/Tools/portbuild/scripts/</filename>.</para>
<para>Typically, incremental builds are done that use previous
- packages as dependendencies; this takes less time, and puts less
+ packages as dependencies; this takes less time, and puts less
load on the mirrors. Full builds are usually only done:</para>
<itemizedlist>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/problem-reports/article.sgml#5 (text+ko) ====
@@ -7,7 +7,7 @@
<articleinfo>
<title>Writing &os; Problem Reports</title>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/problem-reports/article.sgml,v 1.61 2008/12/30 08:24:54 remko Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/problem-reports/article.sgml,v 1.62 2010/07/31 11:06:18 pgj Exp $</pubdate>
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
@@ -396,7 +396,7 @@
specific input then include an example of that input if
possible, and include both the actual and the expected
output. If this data is large or cannot be made public,
- then do try to create a minimal file that exibits the
+ then do try to create a minimal file that exhibits the
same issue and that can be included within the PR.</para>
</listitem>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/releng-packages/article.sgml#2 (text+ko) ====
@@ -21,7 +21,7 @@
</author>
</authorgroup>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/releng-packages/article.sgml,v 1.19 2006/03/12 13:45:13 remko Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/releng-packages/article.sgml,v 1.20 2010/07/31 11:06:18 pgj Exp $</pubdate>
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
@@ -209,7 +209,7 @@
<listitem><para>On your first pass through a split it is best to
fake the copying of packages and distfiles. This will save
- both time and diskspace while you do a couple of trial runs to
+ both time and disk space while you do a couple of trial runs to
make sure things fit, etc. In the
<filename>oneshot.pl</filename> set the <varname>fake</varname>
variable to 1 and instead of actually copying the files it will
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/serial-uart/article.sgml#2 (text+ko) ====
@@ -18,7 +18,7 @@
</author>
</authorgroup>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/serial-uart/article.sgml,v 1.13 2004/11/29 21:43:34 ceri Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/serial-uart/article.sgml,v 1.14 2010/07/31 11:06:18 pgj Exp $</pubdate>
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
@@ -300,7 +300,7 @@
<para>When two devices that are both DTE or both DCE must be
connected together without a modem or a similar media
- translater between them, a NULL modem must be used. The
+ translator between them, a NULL modem must be used. The
NULL modem electrically re-arranges the cabling so that
the transmitter output is connected to the receiver input
on the other device, and vice versa. Similar translations
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/storage-devices/article.sgml#2 (text+ko) ====
@@ -18,7 +18,7 @@
</author>
</authorgroup>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/storage-devices/article.sgml,v 1.15 2004/11/29 21:43:34 ceri Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/storage-devices/article.sgml,v 1.16 2010/07/31 11:06:18 pgj Exp $</pubdate>
<legalnotice id="trademarks" role="trademarks">
@@ -40,7 +40,7 @@
<para>ESDI is an acronym that means Enhanced Small Device
Interface. It is loosely based on the good old ST506/412
interface originally devised by Seagate Technology, the makers
- of the first affordable 5.25" winchester disk.</para>
+ of the first affordable 5.25" Winchester disk.</para>
<para>The acronym says Enhanced, and rightly so. In the first
place the speed of the interface is higher, 10 or 15
@@ -2099,7 +2099,7 @@
<screen>&prompt.root; <userinput>mt -f /dev/st0ctl.0 blocksize 1024</userinput></screen>
<para>Before using a mini cartridge for the first time, the
- mini cartridge must be formated. FreeBSD 2.1.0-RELEASE and
+ mini cartridge must be formatted. FreeBSD 2.1.0-RELEASE and
earlier:</para>
<screen>&prompt.root; <userinput>/sbin/scsi -f /dev/rst0.ctl -s 600 -c "4 0 0 0 0 0"</userinput></screen>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/faq/book.sgml#28 (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.1121 2010/07/15 20:39:57 pgj Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.1124 2010/07/30 21:34:30 pgj Exp $</pubdate>
<copyright>
<year>1995</year>
@@ -2197,7 +2197,7 @@
must be used. PAE stands for Physical Address Extension
and is a way for 32-bit x86 CPUs to address more than
4 GB of memory. It remaps the memory that would
- otherwise be overlayed by address reservations for
+ otherwise be overlaid by address reservations for
hardware devices above the 4 GB range and uses it as
additional physical memory (see &man.pae.4;). Using PAE
has some drawbacks; this mode of memory access is a little
@@ -4085,7 +4085,7 @@
<answer>
<para>An answer for this question can be found in the &os;
- Glosssary, see <ulink
+ Glossary, see <ulink
url="&url.books.handbook;/freebsd-glossary.html#LOR-GLOSSARY">LOR</ulink>.
</para>
</answer>
@@ -4528,7 +4528,7 @@
one should be able to refuse categories, but in practice
there are too many ports that depend on ports in other
categories. Until someone comes up with a solution for this
- problem, the general rule is is that if you want to build
+ problem, the general rule is that if you want to build
<filename>INDEX</filename>, you must have a complete copy of
the Ports Collection.</para>
@@ -9069,7 +9069,7 @@
<para>Care should be taken with this option. You should also
use this command to limit the amount of time that
- &man.ppp.8; waits for the peer to begin negotations:</para>
+ &man.ppp.8; waits for the peer to begin negotiations:</para>
<programlisting>set stopped <replaceable>N</replaceable></programlisting>
@@ -9467,7 +9467,7 @@
<quote>special cases</quote> can be found in
<filename>/usr/src/sys/netinet/libalias/alias_*.c</filename>
(<filename>alias_ftp.c</filename> is a good prototype).
- This usually involves reading certain recognised
+ This usually involves reading certain recognized
outgoing packets, identifying the instruction that tells
the outside machine to initiate a connection back to the
internal machine on a specific (random) port and setting
@@ -10145,10 +10145,10 @@
<screen>&prompt.user; <userinput>chmod g-w bar</userinput></screen>
- <para>However, the permissions on <filename>foo</filename>
+ <para>However, the permissions on <filename>bar</filename>
will not have changed.</para>
- <para>When changing modes of the file hiearchies rooted in the
+ <para>When changing modes of the file hierarchies rooted in the
files instead of the files themselves,
you have to use either <option>-H</option> or
<option>-L</option> together with the <option>-R</option>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/config/chapter.sgml#10 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.239 2009/10/25 21:21:54 keramida Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.241 2010/07/29 14:44:44 pgj Exp $
-->
<chapter id="config-tuning">
@@ -2807,6 +2807,29 @@
do not expect the problem to be resolved since there are a lot
of drivers/hardware that need more testing and work.</para>
+ <para>A common problem with suspend/resume is that many device
+ drivers do not save, restore, or reinitialize their firmware,
+ registers, or device memory properly. As a first attempt at
+ debugging the problem, try:</para>
+
+ <screen>&prompt.root; <userinput>sysctl debug.bootverbose=1</userinput>
+&prompt.root; <userinput>sysctl debug.acpi.suspend_bounce=1</userinput>
+&prompt.root; <userinput>acpiconf -s 3</userinput></screen>
+
+ <para>This test emulates suspend/resume cycle of all device
+ drivers without actually going into <literal>S3</literal> state.
+ In some cases, you can easily catch problems with this method
+ (e.g., losing firmware state, device watchdog time out, and
+ retrying forever). Note that the system will not really enter
+ <literal>S3</literal> state, which means devices may not lose
+ power, and many will work fine even if suspend/resume methods
+ are totally missing, unlike real <literal>S3</literal>
+ state.</para>
+
+ <para>Harder cases require additional hardware, i.e., serial
+ port/cable for serial console or Firewire port/cable for
+ &man.dcons.4;, and kernel debugging skills.</para>
+
<para>To help isolate the problem, remove as many drivers from
your kernel as possible. If it works, you can narrow down
which driver is the problem by loading drivers until it fails
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml#11 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml,v 1.92 2009/12/11 20:13:07 bcr Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/firewalls/chapter.sgml,v 1.93 2010/07/17 05:20:55 pgj Exp $
-->
<chapter id="firewalls">
@@ -826,9 +826,9 @@
<para><application>Syslogd</application> uses its own special
method for segregation of log data. It uses special groupings
called <quote>facility</quote> and <quote>level</quote>. IPMON
- in <option>-Ds</option> mode uses <literal>security</literal>
+ in <option>-Ds</option> mode uses <literal>local0</literal>
as the <quote>facility</quote>
- name. All IPMON logged data goes to <literal>security</literal>
+ name by default.
The following levels can be
used to further segregate the logged data if desired:</para>
@@ -854,9 +854,9 @@
<para>Add the following statement to
<filename>/etc/syslog.conf</filename>:</para>
- <programlisting>security.* /var/log/ipfilter.log</programlisting>
+ <programlisting>local0.* /var/log/ipfilter.log</programlisting>
- <para>The <literal>security.*</literal>
+ <para>The <literal>local0.*</literal>
means to write all the logged messages to the coded
file location.</para>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#7 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.394 2010/07/13 19:10:21 bcr Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.397 2010/07/28 19:32:17 blackend Exp $
-->
<chapter id="install">
@@ -1211,12 +1211,12 @@
<screen> User Confirmation Requested
Are you sure you wish to exit? The system will reboot
- (be sure to remove any floppies/CDs/DVDs from the drives).
[ Yes ] No</screen>
- <para>The install program will start again if the CDROM is left
- in the drive and &gui.yes; is selected.</para>
+ <para>The install program will start again if the
+ &gui.yes; is selected and the CDROM is left in the drive during
+ the reboot.</para>
<para>If you are booting from floppies it will be necessary to remove
the <filename>boot.flp</filename> floppy before rebooting.</para>
@@ -1947,7 +1947,7 @@
<screen> Message
Now, you need to create BSD partitions inside of the fdisk
partition(s) just created. If you have a reasonable amount of disk
- space (200MB or more) and don't have any special requirements, simply
+ space (1GB or more) and don't have any special requirements, simply
use the (A)uto command to allocate space automatically. If you have
more specific needs or just don't care for the layout chosen by
(A)uto, press F1 for more information on manual layout.
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml#14 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml,v 1.137 2009/12/04 16:46:47 roam Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml,v 1.138 2010/07/25 10:26:44 manolis Exp $
-->
<chapter id="introduction">
@@ -660,7 +660,9 @@
<para>The tree was branched again in August 2009, this time for
RELENG_8. 8.0-RELEASE, the first release of the 8.X branch, was
- released in &rel.current.date;.</para>
+ released in November 2009. The most recent
+ &rel.current;-RELEASE came out in &rel.current.date;. There will
+ be additional releases from the RELENG_8 branch.</para>
<para>For now, long-term development projects continue to take place
in the 9.X-CURRENT (trunk) branch, and SNAPshot releases of 9.X on
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#32 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.488 2010/07/13 15:11:35 ganbold Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.489 2010/07/28 14:41:34 hrs Exp $
-->
<appendix id="mirrors">
@@ -2746,6 +2746,14 @@
<variablelist>
<varlistentry>
+ <term>RELENG_8_1_0_RELEASE</term>
+
+ <listitem>
+ <para>&os; 8.1</para>
+ </listitem>
+ </varlistentry>
+
+ <varlistentry>
<term>RELENG_8_0_0_RELEASE</term>
<listitem>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml#19 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml,v 1.123 2010/07/03 16:51:32 jkois Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/network-servers/chapter.sgml,v 1.124 2010/07/23 12:48:36 jkois Exp $
-->
<chapter id="network-servers">
@@ -1709,13 +1709,14 @@
21 * * * * root /usr/libexec/ypxfr passwd.byuid</programlisting>
<para>These two lines force the slave to sync its maps with
- the maps on the master server. Although these entries are
- not mandatory, since the master server attempts to ensure
- any changes to its NIS maps are communicated to its slaves
- and because password information is vital to systems
- depending on the server, it is a good idea to force the
- updates. This is more important on busy networks where map
- updates might not always complete.</para>
+ the maps on the master server. These entries are not
+ mandatory because the master server automatically attempts
+ to push any map changes to its slaves. However, due to the
+ importance of correct password information on other clients
+ depending on the slave server, it is recommended to
+ specifically force the password map updates frequently. This
+ is especially important on busy networks where map updates
+ might not always complete.</para>
<para>Now, run the command <command>/etc/netstart</command> on the
slave server as well, which again starts the NIS server.</para>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#83 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.1065 2010/07/04 20:24:16 bcr Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.1068 2010/07/31 10:46:18 pgj Exp $
-->
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
@@ -369,12 +369,17 @@
linkend="porting-dads">DOs and DON'Ts</link> section.</para>
<para>Now that you are happy with your port, the only thing remaining
- is to put it in the main FreeBSD ports tree and make everybody else
+ is to put it in the main &os; ports tree and make everybody else
happy about it too. We do not need your <filename>work</filename>
directory or the <filename>pkgname.tgz</filename> package, so delete
- them now. Next, simply include the output of <command>shar `find
- port_dir`</command> in a bug report and send it with the
- &man.send-pr.1; program (see <ulink url="&url.articles.contributing;/contrib-how.html#CONTRIB-GENERAL">Bug
+ them now. Next, assuming your port is called oneko,
+ <command>cd</command> to the directory above where the
+ <literal>oneko</literal> directory is located, and then type the
+ following: <command>shar `find oneko` > oneko.shar</command>
+
+ <para>Include your <literal>oneko.shar</literal> file in a bug report
+ and send it with the &man.send-pr.1; program (see
+ <ulink url="&url.articles.contributing;/contrib-how.html#CONTRIB-GENERAL">Bug
Reports and General Commentary</ulink> for more information about
&man.send-pr.1;). Be sure to classify the bug report as category
<literal>ports</literal> and class
@@ -382,7 +387,7 @@
<literal>confidential</literal>!).
Also add a short description of the program you ported
to the <quote>Description</quote> field of the PR and
- the shar to the <quote>Fix</quote> field.</para>
+ the shar file to the <quote>Fix</quote> field.</para>
<note>
<para>You can make our work a lot easier, if you use a good
@@ -402,10 +407,10 @@
<para>After you have submitted your port, please be patient.
Sometimes it can take a few months before a port is included
- in FreeBSD, although it might only take a few days. You can
+ in &os;, although it might only take a few days. You can
view the list of <ulink
url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi?category=ports">ports
- waiting to be committed to FreeBSD</ulink>.</para>
+ waiting to be committed to &os;</ulink>.</para>
<para>Once we have looked at your port, we will get back to you if necessary, and put
it in the tree. Your name will also appear in the list of
@@ -616,7 +621,7 @@
<para>Unpack a copy of the tarball in a private directory and make
whatever changes are necessary to get the port to compile properly
- under the current version of FreeBSD. Keep <emphasis>careful
+ under the current version of &os;. Keep <emphasis>careful
track</emphasis> of everything you do, as you will be automating
the process shortly. Everything, including the deletion, addition,
or modification of files should be doable using an automated script
@@ -631,7 +636,7 @@
<note>
>>> TRUNCATED FOR MAIL (1000 lines) <<<
More information about the p4-projects
mailing list