Date: Sat, 16 May 2009 19:41:24 GMT From: Rene Ladan <rene@FreeBSD.org> To: Perforce Change Reviews <perforce@FreeBSD.org> Subject: PERFORCE change 162174 for review Message-ID: <200905161941.n4GJfOBR065933@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=162174 Change 162174 by rene@rene_self on 2009/05/16 19:40:34 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#10 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#7 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#15 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#28 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/contributing/article.sgml#19 integrate .. //depot/projects/docproj_nl/share/sgml/man-refs.ent#17 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/portbuild/article.sgml#10 (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.36 2009/01/07 09:34:58 pav Exp $</pubdate> + <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/portbuild/article.sgml,v 1.37 2009/05/14 15:33:07 erwin Exp $</pubdate> <copyright> <year>2003</year> @@ -608,9 +608,9 @@ to identify it. You need to make sure that nothing else important is running in this tty, e.g. <command>ps -t p1</command> or whatever. If there is not, you can just kill off the whole term easily with - <command>pkill -t p1</command>; otherwise issue a + <command>pkill -t pts/1</command>; otherwise issue a <command>kill -HUP</command> in there by, for example, -<command>ps -t p1 -o pid= | xargs kill -HUP</command>. Replace +<command>ps -t pts/1 -o pid= | xargs kill -HUP</command>. Replace <replaceable>p1</replaceable> by whatever the tty is, of course.</para> <para>The ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml#7 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.190 2008/12/23 18:48:22 trhodes Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml,v 1.192 2009/05/15 13:31:51 rwatson Exp $ --> <chapter id="kernelconfig"> @@ -96,7 +96,7 @@ dynamic loadable kernel module for that functionality.</para> <para>Building a custom kernel is one of the most important rites of - passage nearly every BSD user must endure. This process, while + passage for advanced BSD users. This process, while time consuming, will provide many benefits to your &os; system. Unlike the <filename>GENERIC</filename> kernel, which must support a wide range of hardware, a custom kernel only contains support for @@ -112,9 +112,11 @@ <listitem> <para>Lower memory usage. A custom kernel often uses less memory - than the <filename>GENERIC</filename> kernel, which is important - because the kernel must always be present in real - memory. For this reason, a custom kernel is especially useful + than the <filename>GENERIC</filename> kernel by omitting unused + features and device drivers. This is important because the kernel + code remains resident in physical memory at all times, preventing + that memory from being used by applications. + For this reason, a custom kernel is especially useful on a system with a small amount of RAM.</para> </listitem> @@ -231,7 +233,7 @@ page:</para> <programlisting>Alternatively, to load the driver as a module at boot time, place the -following line in &man.loader.conf.5;: +following line in &man.loader.conf.5: if_ath_load="YES"</programlisting> @@ -495,6 +497,34 @@ architecture independent options, see <filename>/usr/src/sys/conf/NOTES</filename>.</para> + <para>As of &os; 5.0, a new <literal>include</literal> directive is + available for use in configuration files. This allows another + configuration file to be logically included in the current one, making + it easy to maintain small changes relative to an existing file. For + example, if you require a <filename>GENERIC</filename> kernel with + only a small number of additional options or drivers, this allows you + to maintain only a delta with respect to GENERIC:</para> + + <programlisting>include GENERIC +ident MYKERNEL + +options IPFIREWALL +options DUMMYNET +options IPFIREWALL_DEFAULT_TO_ACCEPT +options IPDIVERT +</programlisting> + + <para>Many administrators will find that this model offers significant + benefits over the historic writing of configuration files from scratch: + the local configuration file will express only local differences from + a <filename>GENERIC</filename> kernel and as upgrades are performed, + new features added to <filename>GENERIC</filename> will be added to the + local kernel unless specifically prevented using + <literal>nooptions</literal> or <literal>nodevice</literal>. The + remainder of this chapter addresses the contents of a typical + configuration file and the role various options and devices + play.</para> + <note> <para>To build a file which contains all available options, as normally done for testing purposes, run the following ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml#15 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.462 2009/05/09 18:14:04 jkois Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.463 2009/05/16 07:24:14 hrs Exp $ --> <appendix id="mirrors"> @@ -2431,6 +2431,15 @@ </varlistentry> <varlistentry> + <term>RELENG_7_2</term> + + <listitem> + <para>The release branch for FreeBSD-7.2, used only for + security advisories and other critical fixes.</para> + </listitem> + </varlistentry> + + <varlistentry> <term>RELENG_7_1</term> <listitem> ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#28 (text+ko) ==== @@ -1,7 +1,7 @@ <!-- The FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.1004 2009/05/08 02:22:31 sepotvin Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.1006 2009/05/15 18:52:43 jhb Exp $ --> <!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [ @@ -12501,6 +12501,14 @@ </row> <row> + <entry>702101</entry> + <entry>May 15, 2009</entry> + <entry>7.2-STABLE after ichsmb(4) was changed to + use left-adjused slave addressing to match other + SMBus controller drivers.</entry> + </row> + + <row> <entry>800000</entry> <entry>October 11, 2007</entry> <entry>8.0-CURRENT. Separating wide and single byte @@ -13048,8 +13056,16 @@ <entry>8.0-CURRENT after adding support for input lines of arbitrarily length in patch(1).</entry> </row> - - + <row> + <entry>800087</entry> + <entry>May 11, 2009</entry> + <entry>8.0-CURRENT after some VFS KPI changes. The thread + argument has been removed from the FSD parts of the VFS. + <function>VFS_*</function> functions do not need the + context any more because it always refers to + <varname>curthread</varname>. In some special cases, + the old behavior is retained.</entry> + </row> </tbody> </tgroup> </table> ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/articles/contributing/article.sgml#19 (text+ko) ==== @@ -1,4 +1,4 @@ -<!-- $FreeBSD: doc/nl_NL.ISO8859-1/articles/contributing/article.sgml,v 1.4 2009/04/30 20:44:24 rene Exp $ --> +<!-- $FreeBSD: doc/nl_NL.ISO8859-1/articles/contributing/article.sgml,v 1.5 2009/05/13 21:18:24 rene Exp $ --> <!-- %SOURCE% en_US.ISO8859-1/articles/contributing/article.sgml --> <!-- %SRCID% 1.511 --> ==== //depot/projects/docproj_nl/share/sgml/man-refs.ent#17 (text+ko) ==== @@ -20,7 +20,7 @@ lexicographical order by the entity (i.e., the dots used in place of special characters should not be expanded when comparing). - $FreeBSD: doc/share/sgml/man-refs.ent,v 1.485 2009/04/29 15:13:21 hrs Exp $ + $FreeBSD: doc/share/sgml/man-refs.ent,v 1.486 2009/05/16 10:47:00 brueffer Exp $ --> <!ENTITY man...1 "<citerefentry/<refentrytitle/[/<manvolnum/1//"> @@ -3311,6 +3311,7 @@ <!ENTITY man.bridge.4 "<citerefentry/<refentrytitle/bridge/<manvolnum/4//"> <!ENTITY man.brooktree.4 "<citerefentry/<refentrytitle/brooktree/<manvolnum/4//"> <!ENTITY man.bt.4 "<citerefentry/<refentrytitle/bt/<manvolnum/4//"> +<!ENTITY man.bwi.4 "<citerefentry/<refentrytitle/bwi/<manvolnum/4//"> <!ENTITY man.cam.4 "<citerefentry/<refentrytitle/cam/<manvolnum/4//"> <!ENTITY man.cardbus.4 "<citerefentry/<refentrytitle/cardbus/<manvolnum/4//"> <!ENTITY man.carp.4 "<citerefentry/<refentrytitle/carp/<manvolnum/4//"> @@ -3786,6 +3787,7 @@ <!ENTITY man.uplcom.4 "<citerefentry/<refentrytitle/uplcom/<manvolnum/4//"> <!ENTITY man.ural.4 "<citerefentry/<refentrytitle/ural/<manvolnum/4//"> <!ENTITY man.urio.4 "<citerefentry/<refentrytitle/urio/<manvolnum/4//"> +<!ENTITY man.urtw.4 "<citerefentry/<refentrytitle/urtw/<manvolnum/4//"> <!ENTITY man.usb.4 "<citerefentry/<refentrytitle/usb/<manvolnum/4//"> <!ENTITY man.uscanner.4 "<citerefentry/<refentrytitle/uscanner/<manvolnum/4//"> <!ENTITY man.uslcom.4 "<citerefentry/<refentrytitle/uslcom/<manvolnum/4//">
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200905161941.n4GJfOBR065933>