Date: Sun, 12 Feb 2012 11:07:27 GMT From: Rene Ladan <rene@FreeBSD.org> To: Perforce Change Reviews <perforce@FreeBSD.org> Subject: PERFORCE change 206164 for review Message-ID: <201202121107.q1CB7RKF055223@skunkworks.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://p4web.freebsd.org/@@206164?ac=10 Change 206164 by rene@rene_acer on 2012/02/12 11:06:49 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributing/article.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#125 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#75 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cups/article.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/dialup-firewall/article.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/releng/article.sgml#10 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/book.sgml#5 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/overview/chapter.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml#6 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/tools/chapter.sgml#6 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/book.sgml#9 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/boot/chapter.sgml#10 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.sgml#12 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/desktop/chapter.sgml#33 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/disks/chapter.sgml#24 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/filesystems/chapter.sgml#10 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/geom/chapter.sgml#12 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/install/chapter.sgml#26 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#16 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml#12 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mail/chapter.sgml#9 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/printing/chapter.sgml#9 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/x11/chapter.sgml#22 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#129 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/authors.ent#68 integrate .. //depot/projects/docproj_nl/share/mk/doc.common.mk#3 integrate .. //depot/projects/docproj_nl/share/pgpkeys/hrs.key#2 integrate .. //depot/projects/docproj_nl/share/pgpkeys/matthew.key#1 branch .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys-developers.sgml#69 integrate .. //depot/projects/docproj_nl/share/pgpkeys/pgpkeys.ent#66 integrate .. //depot/projects/docproj_nl/www/en/developers.sgml#69 integrate .. //depot/projects/docproj_nl/www/en/ports/index.sgml#2 integrate .. //depot/projects/docproj_nl/www/en/ports/references.sgml#2 integrate .. //depot/projects/docproj_nl/www/share/sgml/news.xml#130 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributing/article.sgml#4 (text+ko) ==== @@ -8,12 +8,12 @@ <articleinfo> <title>Contributing to FreeBSD</title> - <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/contributing/article.sgml,v 1.511 2009/05/13 02:05:11 keramida Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/contributing/article.sgml,v 1.512 2012/02/07 22:08:33 wblock Exp $</pubdate> <abstract> <para>This article describes the different ways in which an - individual or organization may contribute to the FreeBSD - Project.</para> + individual or organization may contribute to the FreeBSD + Project.</para> </abstract> <authorgroup> @@ -67,7 +67,7 @@ <sect1 id="contrib-what"> <title>What Is Needed</title> - + <para>The following list of tasks and sub-projects represents something of an amalgam of various <filename>TODO</filename> lists and user requests.</para> @@ -119,11 +119,13 @@ </sect2> <sect2 id="ongoing-programmer-tasks"> - <title>Ongoing Programmer Tasks</title> - <para>Most of the tasks listed here require either a considerable - investment of time, or an in-depth knowledge of the FreeBSD - kernel, or both. However, there are also many useful tasks - which are suitable for <quote>weekend hackers</quote>.</para> + <title>Ongoing Programmer Tasks</title> + + <para>Most of the tasks listed here require either a + considerable investment of time, or an in-depth knowledge of + the FreeBSD kernel, or both. However, there are also many + useful tasks which are suitable for <quote>weekend + hackers</quote>.</para> <orderedlist> <listitem> @@ -151,13 +153,14 @@ <listitem> <para>Move contributed software to - <filename class="directory">src/contrib</filename> in the source - tree.</para> + <filename class="directory">src/contrib</filename> in the + source tree.</para> </listitem> <listitem> - <para>Make sure code in <filename class="directory">src/contrib</filename> is - up to date.</para> + <para>Make sure code in + <filename class="directory">src/contrib</filename> is up + to date.</para> </listitem> <listitem> @@ -183,8 +186,8 @@ get some links about these standards at the <ulink url="&url.base;/projects/c99/index.html">FreeBSD C99 & POSIX Standards Conformance Project</ulink> web - site. Compare FreeBSD's behavior to that required by the - standard. If the behavior differs, particularly in subtle + site. Compare FreeBSD's behavior to that required by the + standard. If the behavior differs, particularly in subtle or obscure corners of the specification, send in a PR about it. If you are able, figure out how to fix it and include a patch in the PR. If you think the standard is @@ -201,11 +204,13 @@ <sect2> <title>Work through the PR Database</title> - <indexterm><primary>problem reports database</primary></indexterm> + <indexterm> + <primary>problem reports database</primary> + </indexterm> <para>The <ulink - url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">FreeBSD - PR list</ulink> shows all the current active problem reports + url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">FreeBSD + PR list</ulink> shows all the current active problem reports and requests for enhancement that have been submitted by FreeBSD users. The PR database includes both programmer and non-programmer tasks. Look through the open PRs, and see if @@ -224,13 +229,15 @@ </sect2> <sect2> - <title>Pick one of the items from the <quote>Ideas</quote> page</title> + <title>Pick one of the items from the <quote>Ideas</quote> + page</title> <para>The <ulink url="&url.base;/projects/ideas/">&os; list of - projects and ideas for volunteers</ulink> is also available for - people willing to contribute to the &os; project. The list is - being regularly updated and contains items for both programmers - and non-programmers with information about each project.</para> + projects and ideas for volunteers</ulink> is also available + for people willing to contribute to the &os; project. The + list is being regularly updated and contains items for both + programmers and non-programmers with information about each + project.</para> </sect2> </sect1> @@ -261,11 +268,11 @@ in the report. If the patch is suitable to be applied to the source tree put <literal>[PATCH]</literal> in the synopsis of the report. When including patches, <emphasis>do - not</emphasis> use cut-and-paste because cut-and-paste turns - tabs into spaces and makes them unusable. When patches are a lot - larger than 20KB, consider compressing them (eg. with &man.gzip.1; - or &man.bzip2.1;) and using &man.uuencode.1; to include their - compressed form in your problem report.</para> + not</emphasis> use cut-and-paste because cut-and-paste turns + tabs into spaces and makes them unusable. When patches are a + lot larger than 20KB, consider compressing them (eg. with + &man.gzip.1; or &man.bzip2.1;) and using &man.uuencode.1; to + include their compressed form in your problem report.</para> <para>After filing a report, you should receive confirmation along with a tracking number. Keep this tracking number so @@ -282,23 +289,25 @@ the &a.bugs;.</para> <para>See also <ulink - url="&url.articles.problem-reports;/article.html">this - article</ulink> on how to write good problem reports.</para> + url="&url.articles.problem-reports;/article.html">this + article</ulink> on how to write good problem reports.</para> </sect2> <sect2> <title>Changes to the Documentation</title> - <indexterm><primary>documentation submissions</primary></indexterm> + <indexterm> + <primary>documentation submissions</primary> + </indexterm> <para>Changes to the documentation are overseen by the &a.doc;. - Please look at the <ulink - url="&url.books.fdp-primer;/index.html">FreeBSD Documentation - Project Primer</ulink> for complete instructions. Send - submissions and changes (even small ones are welcome!) using - &man.send-pr.1; as described in <link - linkend="contrib-general">Bug Reports and General - Commentary</link>.</para> + Please look at the + <ulink url="&url.books.fdp-primer;/index.html">FreeBSD + Documentation Project Primer</ulink> for complete + instructions. Send submissions and changes (even small ones + are welcome!) using &man.send-pr.1; as described in + <link linkend="contrib-general">Bug Reports and General + Commentary</link>.</para> </sect2> <sect2> @@ -309,13 +318,13 @@ <para>An addition or change to the existing source code is a somewhat trickier affair and depends a lot on how far out of date you are with the current state of FreeBSD - development. There is a special on-going release of FreeBSD + development. There is a special on-going release of FreeBSD known as <quote>FreeBSD-CURRENT</quote> which is made available in a variety of ways for the convenience of - developers working actively on the system. See <ulink url=" - &url.books.handbook;/current-stable.html">The FreeBSD - Handbook</ulink> for more information about getting and using - FreeBSD-CURRENT.</para> + developers working actively on the system. See + <ulink url="&url.books.handbook;/current-stable.html">The + FreeBSD Handbook</ulink> for more information about getting + and using FreeBSD-CURRENT.</para> <para>Working from older sources unfortunately means that your changes may sometimes be too obsolete or too divergent for @@ -324,20 +333,20 @@ &a.current; lists, where discussions on the current state of the system take place.</para> - <para>Assuming that you can manage to secure fairly up-to-date sources - to base your changes on, the next step is to produce a set of diffs to - send to the FreeBSD maintainers. This is done with the &man.diff.1; - command.</para> + <para>Assuming that you can manage to secure fairly up-to-date + sources to base your changes on, the next step is to produce a + set of diffs to send to the FreeBSD maintainers. This is done + with the &man.diff.1; command.</para> <para>The preferred &man.diff.1; format for submitting patches - is the unified output format generated by <command>diff - -u</command>. However, for patches that substantially change a - region of code, a context output format diff generated by - <command>diff -c</command> may be more readable and thus - preferable.</para> + is the unified output format generated by <command>diff + -u</command>. However, for patches that substantially + change a region of code, a context output format diff + generated by <command>diff -c</command> may be more readable + and thus preferable.</para> <indexterm> - <primary><command>diff</command></primary> + <primary><command>diff</command></primary> </indexterm> <para>For example:</para> @@ -359,9 +368,11 @@ <screen>&prompt.user; <userinput>diff -u -r olddir newdir</userinput></screen> - <para>would do the same, except in the unified diff format.</para> + <para>would do the same, except in the unified diff + format.</para> - <para>See the manual page for &man.diff.1; for more details.</para> + <para>See the manual page for &man.diff.1; for more + details.</para> <para>Once you have a set of diffs (which you may test with the &man.patch.1; command), you should submit them for inclusion @@ -377,13 +388,14 @@ report.</para> <indexterm> - <primary><command>uuencode</command></primary> + <primary><command>uuencode</command></primary> </indexterm> <para>If you feel it appropriate (e.g. you have added, deleted, or renamed files), bundle your changes into a <command>tar</command> file and run the &man.uuencode.1; - program on it. Archives created with &man.shar.1; are also welcome.</para> + program on it. Archives created with &man.shar.1; are also + welcome.</para> <para>If your change is of a potentially sensitive nature, e.g. you are unsure of copyright issues governing its further @@ -396,7 +408,7 @@ only send mail to them where it is truly necessary.</para> <para>Please refer to &man.intro.9; and &man.style.9; for - some information on coding style. We would appreciate it if + some information on coding style. We would appreciate it if you were at least aware of this information before submitting code.</para> </sect2> @@ -417,7 +429,7 @@ copyrights for code included in FreeBSD are:</para> <orderedlist> - <indexterm><primary>BSD copyright</primary></indexterm> + <indexterm><primary>BSD copyright</primary></indexterm> <listitem> <para>The BSD copyright. This copyright is most preferred due to its <quote>no strings attached</quote> nature and @@ -428,8 +440,12 @@ something of their own into FreeBSD.</para> </listitem> - <indexterm><primary>GPL</primary><see>GNU General Public License</see></indexterm> - <indexterm><primary>GNU General Public License</primary></indexterm> + <indexterm> + <primary>GPL</primary><see>GNU General Public License</see> + </indexterm> + <indexterm> + <primary>GNU General Public License</primary> + </indexterm> <listitem> <para>The GNU General Public License, or <quote>GPL</quote>. This license is not quite as popular with us due to the @@ -440,9 +456,9 @@ contributions under this license. Code under the GPL also goes into a different part of the tree, that being <filename class="directory">/sys/gnu</filename> or - <filename class="directory">/usr/src/gnu</filename>, and is therefore easily - identifiable to anyone for whom the GPL presents a - problem.</para> + <filename class="directory">/usr/src/gnu</filename>, and + is therefore easily identifiable to anyone for whom the + GPL presents a problem.</para> </listitem> </orderedlist> @@ -514,34 +530,34 @@ <address> The FreeBSD Foundation <street>7321 Brockway Dr.</street> - <city>Boulder</city>, <state>CO</state> <postcode>80303</postcode> + <city>Boulder</city>, + <state>CO</state> <postcode>80303</postcode> <country>USA</country> - </address> - </para> + </address></para> <para>The FreeBSD Foundation is now able to accept donations through the web with PayPal. To place a donation, please - visit the Foundation <ulink - url="http://www.freebsdfoundation.org">web - site</ulink>.</para> + visit the Foundation + <ulink url="http://www.freebsdfoundation.org">web + site</ulink>.</para> <para>More information about the FreeBSD Foundation can be found in <ulink - url="http://people.FreeBSD.org/~jdp/foundation/announcement.html">The - FreeBSD Foundation -- an Introduction</ulink>. To contact + url="http://people.FreeBSD.org/~jdp/foundation/announcement.html">The + FreeBSD Foundation -- an Introduction</ulink>. To contact the Foundation by email, write to <email>bod@FreeBSDFoundation.org</email>.</para> </sect3> <sect3> <title>Donating Hardware</title> - <indexterm><primary>donations</primary></indexterm> + <indexterm><primary>donations</primary></indexterm> <para>The FreeBSD Project happily accepts donations of hardware that it can find good use for. If you are - interested in donating hardware, please contact the <ulink - url="&url.base;/donations/">Donations Liaison - Office</ulink>.</para> + interested in donating hardware, please contact the + <ulink url="&url.base;/donations/">Donations Liaison + Office</ulink>.</para> </sect3> <sect3> @@ -549,16 +565,16 @@ <para>We can always use new mirror sites for FTP, WWW or <command>cvsup</command>. If you would like to be such a - mirror, please see the <ulink - url="&url.articles.hubs;/index.html">Mirroring FreeBSD</ulink> - article for more information.</para> + mirror, please see the + <ulink url="&url.articles.hubs;/index.html">Mirroring + FreeBSD</ulink> article for more information.</para> </sect3> </sect2> </sect1> </article> -<!-- +<!-- Local Variables: mode: sgml sgml-indent-data: t ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#125 (text+ko) ==== @@ -1,4 +1,4 @@ -<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.1058 2012/01/27 14:45:43 pawel Exp $ --> +<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.1060 2012/02/09 13:54:14 matthew Exp $ --> <!-- NOTE TO COMMITTERS: Contributors lists are sorted in alphabetical order by first name. @@ -5678,6 +5678,11 @@ </listitem> <listitem> + <para>Kurt Jaeger + <email>fbsd-ports@opsec.eu</email></para> + </listitem> + + <listitem> <para>Kurt Olsen <email>kurto@tiny.mcs.usu.edu</email></para> </listitem> @@ -6465,11 +6470,6 @@ </listitem> <listitem> - <para>Matthew Seaman - <email>m.seaman@infracaninophile.co.uk</email></para> - </listitem> - - <listitem> <para>Matthew Stein <email>matt@bdd.net</email></para> </listitem> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml#75 (text+ko) ==== @@ -1,4 +1,4 @@ -<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.348 2012/01/31 22:54:32 davide Exp $ --> +<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.committers.sgml,v 1.349 2012/02/09 13:54:14 matthew Exp $ --> <!-- NOTE TO NEW COMMITTERS: Core and committers lists are sorted in alphabetical order by last name. Please keep in mind that fact while @@ -1195,6 +1195,10 @@ </listitem> <listitem> + <para>&a.matthew;</para> + </listitem> + + <listitem> <para>&a.stas;</para> </listitem> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/cups/article.sgml#5 (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.5 2010/08/29 11:48:32 pgj Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/cups/article.sgml,v 1.6 2012/02/11 04:28:17 eadler Exp $</pubdate> <authorgroup> <author> <firstname>Chess</firstname> @@ -44,7 +44,7 @@ Protocol (<acronym>IPP</acronym>) as the basis for managing print jobs and queues. The Line Printer Daemon (<acronym>LPD</acronym>), Server Message Block - (<acronym>SMB</acronym>), and AppSocket (a.k.a. JetDirect) + (<acronym>SMB</acronym>), and AppSocket (aka JetDirect) protocols are also supported with reduced functionality. <application>CUPS</application> adds network printer browsing and PostScript Printer Description (<acronym>PPD</acronym>) based ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/dialup-firewall/article.sgml#3 (text+ko) ==== @@ -22,7 +22,7 @@ </author> </authorgroup> - <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/dialup-firewall/article.sgml,v 1.43 2008/09/01 22:37:57 keramida Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/dialup-firewall/article.sgml,v 1.44 2012/02/11 04:28:17 eadler Exp $</pubdate> <legalnotice id="trademarks" role="trademarks"> &tm-attrib.freebsd; @@ -264,7 +264,7 @@ <para>This tutorial assumes that you are running <emphasis>userland-ppp</emphasis>, therefore the supplied rule set operates on the <devicename>tun0</devicename> interface, which - corresponds to the first connection made with &man.ppp.8; (a.k.a. + corresponds to the first connection made with &man.ppp.8; (aka <emphasis>user-ppp</emphasis>). Additional connections would use <devicename>tun1</devicename>, <devicename>tun2</devicename> and so on.</para> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/releng/article.sgml#10 (text+ko) ==== @@ -37,7 +37,7 @@ </author> </authorgroup> - <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/releng/article.sgml,v 1.88 2012/01/11 00:41:43 eadler Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/releng/article.sgml,v 1.89 2012/02/11 04:28:17 eadler Exp $</pubdate> <legalnotice id="trademarks" role="trademarks"> &tm-attrib.freebsd; @@ -614,7 +614,7 @@ repository.</para> <para>If <makevar>RELEASETAG</makevar> is omitted, then the - release will be built from the <literal>HEAD</literal> (a.k.a. -CURRENT) branch. + release will be built from the <literal>HEAD</literal> (aka -CURRENT) branch. Releases built from this branch are normally referred to as <quote>-CURRENT snapshots</quote>.</para> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/book.sgml#5 (text+ko) ==== @@ -27,7 +27,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/books/fdp-primer/book.sgml,v 1.33 2009/01/21 23:52:53 pgj Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/book.sgml,v 1.34 2012/02/08 22:48:06 wblock Exp $ --> <!DOCTYPE book PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ @@ -40,10 +40,11 @@ <book> <bookinfo> - <title>FreeBSD Documentation Project Primer for New Contributors</title> - + <title>FreeBSD Documentation Project Primer for New + Contributors</title> + <corpauthor>The FreeBSD Documentation Project</corpauthor> - + <copyright> <year>1998</year> <year>1999</year> @@ -60,24 +61,24 @@ <holder role="mailto:doceng@FreeBSD.org">DocEng</holder> </copyright> - <pubdate role="rcs">$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/book.sgml,v 1.33 2009/01/21 23:52:53 pgj Exp $</pubdate> + <pubdate role="rcs">$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/book.sgml,v 1.34 2012/02/08 22:48:06 wblock Exp $</pubdate> - <releaseinfo>$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/book.sgml,v 1.33 2009/01/21 23:52:53 pgj Exp $</releaseinfo> + <releaseinfo>$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/book.sgml,v 1.34 2012/02/08 22:48:06 wblock Exp $</releaseinfo> &bookinfo.legalnotice; - + <abstract> <para>Thank you for becoming a part of the FreeBSD Documentation - Project. Your contribution is extremely valuable.</para> + Project. Your contribution is extremely valuable.</para> - <para>This primer covers everything you will need to know in order - to start contributing to the FreeBSD Documentation Project, from - the tools and software you will be using (both mandatory and - recommended) to the philosophy behind the Documentation - Project.</para> + <para>This primer covers everything you will need to know in + order to start contributing to the FreeBSD Documentation + Project, from the tools and software you will be using (both + mandatory and recommended) to the philosophy behind the + Documentation Project.</para> - <para>This document is a work in progress, and is not complete. Sections - that are known to be incomplete are indicated with a + <para>This document is a work in progress, and is not complete. + Sections that are known to be incomplete are indicated with a <literal>*</literal> in their name.</para> </abstract> </bookinfo> @@ -87,10 +88,11 @@ <sect1 id="preface-prompts"> <title>Shell Prompts</title> - - <para>The following table shows the default system prompt and superuser - prompt. The examples will use this prompt to indicate which user you - should be running the example as.</para> + + <para>The following table shows the default system prompt and + superuser prompt. The examples will use this prompt to + indicate which user you should be running the example + as.</para> <informaltable frame="none" pgwide="1"> <tgroup cols="2"> @@ -100,7 +102,7 @@ <entry>Prompt</entry> </row> </thead> - + <tbody> <row> <entry>Normal user</entry> @@ -115,12 +117,12 @@ </tgroup> </informaltable> </sect1> - + <sect1 id="preface-conventions"> <title>Typographic Conventions</title> - <para>The following table describes the typographic conventions used in - this book.</para> + <para>The following table describes the typographic conventions + used in this book.</para> <informaltable frame="none" pgwide="1"> <tgroup cols="2"> @@ -134,12 +136,14 @@ <tbody> <row> <entry>The names of commands.</entry> - <entry>Use <command>ls -l</command> to list all files.</entry> + <entry>Use <command>ls -l</command> to list all + files.</entry> </row> <row> <entry>The names of files.</entry> - <entry>Edit your <filename>.login</filename> file.</entry> + <entry>Edit your <filename>.login</filename> + file.</entry> </row> <row> @@ -148,8 +152,8 @@ </row> <row> - <entry>What you type, when contrasted with on-screen computer - output.</entry> + <entry>What you type, when contrasted with on-screen + computer output.</entry> <entry><screen>&prompt.user; <userinput>su</userinput> Password:</screen></entry> @@ -157,35 +161,31 @@ <row> <entry>Manual page references.</entry> - - <entry>Use - &man.su.1; - to change user names.</entry> + <entry>Use &man.su.1; to change user names.</entry> </row> <row> <entry>User and group names</entry> - - <entry>Only <username>root</username> can do this.</entry> + <entry>Only <username>root</username> can do + this.</entry> </row> <row> <entry>Emphasis</entry> - <entry>You <emphasis>must</emphasis> do this.</entry> </row> <row> - <entry>Command line variables; replace with the real name or - variable.</entry> - - <entry>To delete a file, type <command>rm <filename><replaceable>filename</replaceable></filename></command></entry> + <entry>Command line variables; replace with the real + name or variable.</entry> + <entry>To delete a file, type <command>rm + <filename><replaceable>filename</replaceable></filename></command></entry> </row> <row> <entry>Environment variables</entry> - - <entry><envar>$HOME</envar> is your home directory.</entry> + <entry><envar>$HOME</envar> is your home + directory.</entry> </row> </tbody> </tgroup> @@ -193,52 +193,57 @@ </sect1> <sect1 id="preface-notes"> - <title>Notes, Tips, Important Information, Warnings, and Examples</title> + <title>Notes, Tips, Important Information, Warnings, and + Examples</title> - <para>Within the text appear notes, warnings, and examples.</para> + <para>Within the text appear notes, warnings, and + examples.</para> <note> - <para>Notes are represented like this, and contain information that - you should take note of, as it may affect what you do.</para> + <para>Notes are represented like this, and contain information + that you should take note of, as it may affect what you + do.</para> </note> <tip> - <para>Tips are represented like this, and contain information that you - might find useful, or lead to an easier way to do something.</para> + <para>Tips are represented like this, and contain information + that you might find useful, or lead to an easier way to do + something.</para> </tip> <important> - <para>Important information is represented like this. Typically they - flag extra steps you may need to carry out.</para> + <para>Important information is represented like this. + Typically they flag extra steps you may need to carry + out.</para> </important> <warning> - <para>Warnings are represented like this, and contain information - warning you about possible damage if you do not follow the - instructions. This damage may be physical, to your hardware or to - you, or it may be non-physical, such as the inadvertent deletion of - important files.</para> + <para>Warnings are represented like this, and contain + information warning you about possible damage if you do not + follow the instructions. This damage may be physical, to + your hardware or to you, or it may be non-physical, such as + the inadvertent deletion of important files.</para> </warning> <example> <title>A Sample Example</title> - <para>Examples are represented like this, and typically contain - examples you should walk through, or show you what the results of a - particular action should be.</para> + <para>Examples are represented like this, and typically + contain examples you should walk through, or show you what + the results of a particular action should be.</para> </example> </sect1> <sect1 id="preface-acknowledgements"> <title>Acknowledgments</title> - <para>My thanks to Sue Blake, Patrick Durusau, Jon Hamilton, Peter - Flynn, and Christopher Maden, who took the time to read early drafts - of this document and offer many valuable comments and - criticisms.</para> + <para>My thanks to Sue Blake, Patrick Durusau, Jon Hamilton, + Peter Flynn, and Christopher Maden, who took the time to read + early drafts of this document and offer many valuable comments + and criticisms.</para> </sect1> </preface> - + &chap.overview; &chap.tools; &chap.sgml-primer; @@ -255,7 +260,7 @@ &app.examples; <!-- - &index; + &index; --> </book> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/overview/chapter.sgml#3 (text+ko) ==== @@ -27,51 +27,53 @@ ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. - $FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/overview/chapter.sgml,v 1.24 2008/12/07 22:03:48 pgj Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/overview/chapter.sgml,v 1.27 2012/02/08 23:10:59 wblock Exp $ --> <chapter id="overview"> <title>Overview</title> - + <para>Welcome to the FreeBSD Documentation Project. Good quality documentation is very important to the success of FreeBSD, and the - FreeBSD Documentation Project (FDP) is how a lot of that documentation - is produced. Your contributions are very valuable.</para> - - <para>This document's main purpose is to clearly explain <emphasis>how - the FDP is organized</emphasis>, <emphasis>how to write and submit - documentation to the FDP</emphasis>, and <emphasis>how to - effectively use the tools available to you when writing - documentation</emphasis>.</para> - - <para><indexterm> - <primary>Membership</primary> - </indexterm> - Everyone is welcome to join the FDP. There is no minimum + FreeBSD Documentation Project (FDP) is how a lot of that + documentation is produced. Your contributions are very + valuable.</para> + + <para>This document's main purpose is to clearly explain + <emphasis>how the FDP is organized</emphasis>, <emphasis>how to + write and submit documentation to the FDP</emphasis>, and + <emphasis>how to effectively use the tools available to you when + writing documentation</emphasis>.</para> + + <indexterm> + <primary>Membership</primary> + </indexterm> + <para>Everyone is welcome to join the FDP. There is no minimum membership requirement, no quota of documentation you need to produce per month. All you need to do is subscribe to the &a.doc;.</para> - <para>After you have finished reading this document you should:</para> - + <para>After you have finished reading this document you + should:</para> + <itemizedlist> - <listitem> + <listitem> <para>Know which documentation is maintained by the FDP.</para> </listitem> - + <listitem> - <para>Be able to read and understand the SGML source code for the - documentation maintained by the FDP.</para> + <para>Be able to read and understand the SGML source code for + the documentation maintained by the FDP.</para> </listitem> - - <listitem> + + <listitem> <para>Be able to make changes to the documentation.</para> </listitem> - + <listitem> - <para>Be able to submit your changes back for review and eventual - inclusion in the FreeBSD documentation.</para> - </listitem> + <para>Be able to submit your changes back for review and + eventual inclusion in the FreeBSD documentation.</para> + </listitem> </itemizedlist> <sect1 id="overview-doc"> @@ -79,63 +81,65 @@ <para>The FDP is responsible for four categories of FreeBSD documentation.</para> - + <variablelist> <varlistentry> - <term>Manual pages</term> + <term>Manual pages</term> - <listitem> - <para>The English language system manual pages are not written by - the FDP, as they are part of the base system. However, the FDP can - (and has) re-worded parts of existing manual pages to make them - clearer, or to correct inaccuracies.</para> + <listitem> + <para>The English language system manual pages are not + written by the FDP, as they are part of the base system. + However, the FDP can (and has) re-worded parts of existing + manual pages to make them clearer, or to correct + inaccuracies.</para> - <para>The translation teams are responsible for translating the - system manual pages into different languages. These translations - are kept within the FDP.</para> - </listitem> + <para>The translation teams are responsible for translating + the system manual pages into different languages. These + translations are kept within the FDP.</para> + </listitem> </varlistentry> <varlistentry> - <term>FAQ</term> - - <listitem> - <para>The FAQ aims to address (in short question and answer format) - questions that are asked, or should be asked, on the various - mailing lists and newsgroups devoted to FreeBSD. The format does - not permit long and comprehensive answers.</para> - </listitem> + <term>FAQ</term> + + <listitem> + <para>The FAQ aims to address (in short question and answer + format) questions that are asked, or should be asked, on + the various mailing lists and newsgroups devoted to + FreeBSD. The format does not permit long and + comprehensive answers.</para> + </listitem> </varlistentry> <varlistentry> - <term>Handbook</term> + <term>Handbook</term> - <listitem> - <para>The Handbook aims to be the comprehensive on-line resource and - reference for FreeBSD users.</para> - </listitem> + <listitem> + <para>The Handbook aims to be the comprehensive on-line + resource and reference for FreeBSD users.</para> + </listitem> </varlistentry> - + <varlistentry> - <term>Web site</term> - - <listitem> - <para>This is the main FreeBSD presence on the World Wide Web, - visible at <ulink + <term>Web site</term> + + <listitem> + <para>This is the main FreeBSD presence on the World Wide + Web, visible at <ulink url="&url.base;/index.html">http://www.FreeBSD.org/</ulink>; - and many mirrors around the world. The web site is many people's - first exposure to FreeBSD.</para> + and many mirrors around the world. The web site is many + people's first exposure to FreeBSD.</para> </listitem> </varlistentry> </variablelist> - + <para>These four groups of documentation are all available in the FreeBSD CVS tree. This means that the logs of changes to these - files are visible to anyone, and anyone can use a program such as - <application>CVSup</application> or - <application>CTM</application> to keep local copies of - this documentation.</para> - + files are visible to anyone, and anyone can use a program such + as <application>CVSup</application> or + <application>CTM</application> to keep local copies of this + documentation.</para> + <para>In addition, many people have written tutorials or other web sites relating to FreeBSD. Some of these are stored in the CVS repository as well (where the author has agreed to this). In @@ -143,15 +147,15 @@ separate from the main FreeBSD repository. The FDP endeavors to provide links to as much of this documentation as possible.</para> - </sect1> - + </sect1> + <sect1 id="overview-before"> - <title>Before You Start</title> - - <para>This document assumes that you already know:</para> - - <itemizedlist> - <listitem> + <title>Before You Start</title> + + <para>This document assumes that you already know:</para> + + <itemizedlist> + <listitem> <para>How to maintain an up-to-date local copy of the FreeBSD documentation by maintaining a local copy of the FreeBSD CVS repository (using <application>CVS</application> @@ -160,23 +164,25 @@ <application>CVSup</application> to download just a >>> TRUNCATED FOR MAIL (1000 lines) <<<
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201202121107.q1CB7RKF055223>