PERFORCE change 206912 for review
Rene Ladan
rene at FreeBSD.org
Sun Feb 26 12:14:50 UTC 2012
http://p4web.freebsd.org/@@206912?ac=10
Change 206912 by rene at rene_acer on 2012/02/26 12:14:46
IFC
Affected files ...
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#49 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#127 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml#6 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml#32 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/mailing-lists.ent#30 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/geom/chapter.sgml#23 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mail/chapter.sgml#23 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.sgml#33 integrate
.. //depot/projects/docproj_nl/www/share/sgml/commercial.isp.xml#29 integrate
.. //depot/projects/docproj_nl/www/share/sgml/events2012.xml#5 integrate
Differences ...
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/committers-guide/article.sgml#49 (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.310 2012/02/17 22:34:05 gjb Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/committers-guide/article.sgml,v 1.311 2012/02/24 14:10:05 gjb Exp $</pubdate>
<copyright>
<year>1999</year>
@@ -2945,7 +2945,7 @@
<para>This list is
<emphasis>not</emphasis> intended as a place for code reviews or a
- replacement for the &a.arch; or the &a.audit;. In fact
+ replacement for the &a.arch;. In fact
using it as such hurts the FreeBSD Project as it gives a sense of a
closed list where general decisions affecting all of the FreeBSD
using community are made without being <quote>open</quote>.
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#127 (text+ko) ====
@@ -1,4 +1,4 @@
-<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.1062 2012/02/18 14:08:37 pawel Exp $ -->
+<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.1063 2012/02/24 18:39:14 jgh Exp $ -->
<!--
NOTE TO COMMITTERS: Contributors lists are sorted in alphabetical
order by first name.
@@ -459,6 +459,10 @@
</listitem>
<listitem>
+ <para>Alexandros Kosiaris
+ <email>akosiaris+ports at gmail.com</email></para>
+ <listitem>
+
<para>Alexey Illarionov
<email>littlesavage at rambler.ru</email></para>
</listitem>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml#6 (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/the-website/chapter.sgml,v 1.28 2011/11/27 16:37:30 manolis Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml,v 1.32 2012/02/22 07:06:35 gjb Exp $
-->
<chapter id="the-website">
@@ -36,62 +36,58 @@
<sect1 id="the-website-prep">
<title>Preparation</title>
- <para>Use a disk with sufficient free space. You may need anything from
- 200 MB to over 500 MB, depending on the method you choose.
- This space will hold the SGML tools, a subset of the
- <application>CVS</application> tree, temporary build space and the
- installed web pages.</para>
+ <para>Use a disk with sufficient free space. You may need
+ anything from 200 MB to over 500 MB, depending on the
+ method you choose. This space will hold the SGML tools, a
+ subset of the <application>CVS</application> tree, temporary
+ build space and the installed web pages.</para>
<note>
- <para>Make sure your documentation ports are up to date! When in
- doubt, remove the old ports using &man.pkg.delete.1; command before
- installing the port. For example, we currently depend on
- jade-1.2 and if you have installed jade-1.1, please do:</para>
+ <para>Make sure your documentation ports are up to date! When
+ in doubt, remove the old ports using &man.pkg.delete.1;
+ command before installing the port. For example, we currently
+ depend on jade-1.2 and if you have installed jade-1.1, please
+ do:</para>
<screen>&prompt.root; <userinput><command>pkg_delete</command> jade-1.1</userinput></screen>
</note>
- <para>There are two methods to get the files required for the website
- build:</para>
+ <para>There are two methods to get the files required for the
+ website build:</para>
<itemizedlist>
<listitem>
- <para>Use <command>csup</command> to get a local copy of the files
- from a <application>CVSup</application> server. This is the
- easiest method, and does not require installation of additional
- software. The supfile presented in the next section will always
- checkout the latest version of the required files. This is
- sufficient if you are simply rebuilding the website and do not
- intend to commit any changes.</para>
-
- <note>
- <para>&man.csup.1; became part of the base system in
- &os; 6.2-RELEASE. If you are using an earlier version of &os;
- you will need to install <filename role="package">net/csup</filename>
- from the Ports Collection.</para>
- </note>
+ <para>Use <command>csup</command> to get a local copy of the
+ files from a <application>CVSup</application> server. This
+ is the easiest method, and does not require installation of
+ additional software. The supfile presented in the next
+ section will always checkout the latest version of the
+ required files. This is sufficient if you are simply
+ rebuilding the website and do not intend to commit any
+ changes.</para>
</listitem>
<listitem>
- <para>Use <command>cvsup</command> in <quote>cvs</quote> mode to
- create and maintain a local <application>CVS</application>
- repository with the required files. This will require you to
- install a program like
- <filename role="package">net/cvsup-without-gui</filename>, but it is
- a more flexible method if you need to have quick access to different
- revisions of the doc/www files, revision histories, or if you
- intend to commit changes to the central &os;
- <application>CVS</application> repository.</para>
+ <para>Use <command>cvsup</command> in <quote>cvs</quote> mode
+ to create and maintain a local
+ <application>CVS</application> repository with the required
+ files. This will require you to install a program like
+ <filename>net/cvsup-without-gui</filename>,
+ but it is a more flexible method if you need to have quick
+ access to different revisions of the doc/www files, revision
+ histories, or if you intend to commit changes to the central
+ &os; <application>CVS</application> repository.</para>
</listitem>
</itemizedlist>
<sect2 id="the-website-csup">
<title>Simple Method: Using <command>csup</command></title>
- <para>The <command>csup</command> command is part of the base system and
+ <para><command>csup</command> is part of the base system and
already used extensively by most people for updating the
- Ports Collection. The following sample supfile can be used to
- obtain a checkout of the files required for the website build:</para>
+ Ports Collection. The following sample supfile can be
+ used to obtain a checkout of the files required for the
+ website build:</para>
<programlisting>#
# This file checks out all collections required to rebuild
@@ -119,26 +115,25 @@
ports-base</programlisting>
- <para>You should, of course, change the <literal>default host</literal>
- entry to a <application>CVSup</application> mirror near your
- location, and the <literal>default prefix</literal> entry to the
- location where you intend to store the checked out files. Save this
- file as e.g.
- <filename><replaceable>doc-www-supfile</replaceable></filename>, and
- then execute the following command:</para>
+ <para>You should, of course, change the <literal>default
+ host</literal> entry to a <application>CVSup</application>
+ mirror near your location, and the <literal>default
+ prefix</literal> entry to the location where you intend to
+ store the checked out files. Save this file as e.g.
+ <filename><replaceable>doc-www-supfile</replaceable></filename>,
+ and then execute the following command:</para>
<screen>&prompt.root; <userinput><command>csup</command> <option>-g</option> <option>-L2</option> <replaceable>doc-www-supfile</replaceable></userinput></screen>
<para>When this command finishes, you will find the directories
- <filename class="directory">doc/</filename>,
- <filename class="directory">www/</filename> and
- <filename class="directory">ports/</filename> under the directory you
- specified in <literal>default prefix</literal>
- (<filename
+ <filename class="directory">doc/</filename>, <filename
+ class="directory">www/</filename> and <filename
+ class="directory">ports/</filename> under the directory you
+ specified in <literal>default prefix</literal> (<filename
class="directory"><replaceable>/usr/build</replaceable></filename>
- in our example). We will use this same directory for the build
- process itself, so it would be better to use a filesystem with
- sufficient free space.</para>
+ in our example). We will use this same directory for the
+ build process itself, so it would be better to use a
+ filesystem with sufficient free space.</para>
<para>That's it! You can now proceed with the
<link linkend="the-website-build">website build</link>.</para>
@@ -146,32 +141,36 @@
<sect2 id="the-website-cvsup">
<title>Advanced Method: Maintaining a Local
- <application>CVS</application> doc/www Repository</title>
+ <application>CVS</application> <literal>doc/www</literal>
+ Repository</title>
- <para>This method will give you more advanced options, but will require
- you to install the
- <filename role="package">net/cvsup-without-gui</filename> port or
+ <para>This method will give you more advanced options, but will
+ require you to install the
+ <filename>net/cvsup-without-gui</filename> port or
package.</para>
<note>
- <para>The <filename role="package">net/cvsup-without-gui</filename>
- port has a build dependency on
- <filename role="package">lang/ezm3</filename>, a Modula 3
- compiler. This compiler takes quite some time to build, and since
- most people will not need it for anything else, it is perhaps best
- to use a package to install <application>CVSup</application>.</para>
+ <para>The <filename>net/cvsup-without-gui</filename> port has
+ a build dependency on <filename
+ role="package">lang/ezm3</filename>, a Modula 3
+ compiler. This compiler takes quite some time to build,
+ and since most people will not need it for anything else, it
+ is perhaps best to use a package to install
+ <application>CVSup</application>.</para>
</note>
<para>The <application>CVSup</application> utility has a special
<quote>cvs</quote> mode that allows the retrieval of the
- <quote>,v</quote> files that make up a <application>CVS</application>
- repository. This function is not currently available in
- <application>csup</application>. For detailed information on
- <application>CVSup</application>, please read the <ulink
- url="&url.books.handbook;/synching.html#CVSUP">CVSup introduction</ulink> in the &os; Handbook.</para>
+ <quote>,v</quote> files that make up a
+ <application>CVS</application> repository. This function is
+ not currently available in <application>csup</application>.
+ For detailed information on <application>CVSup</application>,
+ please read the <ulink
+ url="&url.books.handbook;/synching.html#CVSUP">CVSup
+ introduction</ulink> in the &os; Handbook.</para>
- <para>The supfile shown below will fetch the cvs collections required
- for the website build, and create a local
+ <para>The supfile shown below will fetch the cvs collections
+ required for the website build, and create a local
<application>CVS</application> repository:</para>
<programlisting>#
@@ -201,31 +200,32 @@
cvsroot-ports
cvsroot-doc</programlisting>
- <para>You should, of course, change the <literal>default host</literal>
- entry to a <application>CVSup</application> mirror near your
- location, and the <literal>default prefix</literal> entry to the
- location where you intend to store the repository files. Save this
- file as e.g.
- <filename><replaceable>doc-www-cvsfile</replaceable></filename>, and
- then execute the following command:</para>
+ <para>You should, of course, change the <literal>default
+ host</literal> entry to a <application>CVSup</application>
+ mirror near your location, and the <literal>default
+ prefix</literal> entry to the location where you intend to
+ store the repository files. Save this file as e.g.
+ <filename><replaceable>doc-www-cvsfile</replaceable></filename>,
+ and then execute the following command:</para>
<screen>&prompt.root; <userinput><command>cvsup</command> <option>-g</option> <option>-L2</option> <replaceable>doc-www-cvsfile</replaceable></userinput></screen>
- <para>It is also advisable to set the <envar>CVSROOT</envar> environment
- variable in your shell's startup files. For example, use
- the following entry in your <filename>~/.cshrc</filename> file:</para>
+ <para>It is also advisable to set the <envar>CVSROOT</envar>
+ environment variable in your shell's startup files. For
+ example, use the following entry in
+ <filename>~/.cshrc</filename>:</para>
<programlisting>setenv <envar>CVSROOT</envar> <replaceable>/usr/dcvs</replaceable></programlisting>
- <para>If you set this variable, you may omit the <option>-d</option>
- argument (shown below) when performing repository operations using
- the <command>cvs</command> command.</para>
+ <para>If you set this variable, you may omit the
+ <option>-d</option> argument (shown below) when performing
+ repository operations using <command>cvs</command>.</para>
- <para>Currently, you will need more than 400 MB of free space to
- host the repository files. An additional 200 MB will be needed
- for the temporary build space. Once the <command>cvsup</command>
- command completes, you are ready to check out the files to your build
- directory:</para>
+ <para>Currently, you will need more than 400 MB of free
+ space to host the repository files. An additional 200 MB
+ will be needed for the temporary build space. Once
+ <command>cvsup</command> completes, you are ready to check out
+ the files to your build directory:</para>
<screen>&prompt.root; <userinput><command>mkdir</command> <replaceable>/usr/build</replaceable></userinput>
&prompt.root; <userinput><command>cd</command> <replaceable>/usr/build</replaceable></userinput>
@@ -233,24 +233,26 @@
<para>The above command is consistent with the way
<application>csup</application> checks out the files from the
- <application>CVSup</application> servers. When it completes, you
- will have a build directory with similar contents to the one used in
- the simple <application>csup</application> method.</para>
+ <application>CVSup</application> servers. When it completes,
+ you will have a build directory with similar contents to the
+ one used in the simple <application>csup</application>
+ method.</para>
- <para>You can continue to use the <command>cvsup</command> command
- shown above, to update your local <application>CVS</application>
- repository on a regular basis. After the initial somewhat lengthy
- download, regular updates will only take a few minutes.</para>
+ <para>You can continue to use <command>cvsup</command> as shown
+ above, to update your local <application>CVS</application>
+ repository on a regular basis. After the initial somewhat
+ lengthy download, regular updates will only take a few
+ minutes.</para>
</sect2>
</sect1>
<sect1 id="the-website-build">
<title>Build the Web Pages from Scratch</title>
- <para>Having completed either of the two methods, you will be ready to
- start the website build. In our example, the build directory is
- <filename
- class="directory"><replaceable>/usr/build</replaceable></filename>
+ <para>Having completed either of the two methods, you will be
+ ready to start the website build. In our example, the build
+ directory is <filename
+ class="directory"><replaceable>/usr/build</replaceable></filename>
and all the required files are already in place.</para>
<procedure>
@@ -261,10 +263,10 @@
</step>
<step>
- <para>The website build starts from the
- <filename class="directory">www/en</filename> directory by executing
- the &man.make.1; <maketarget>all</maketarget> target, to create
- the web pages.</para>
+ <para>The website build starts from the <filename
+ class="directory">www/en</filename> directory by executing
+ the &man.make.1; <maketarget>all</maketarget> target, to
+ create the web pages.</para>
<screen>&prompt.root; <userinput><command>cd</command> www/en</userinput>
&prompt.root; <userinput><command>make</command> <maketarget>all</maketarget></userinput></screen>
@@ -277,18 +279,19 @@
<procedure>
<step>
- <para>If you have moved out of the
- <filename class="directory">en</filename> directory, change back to
+ <para>If you have moved out of the <filename
+ class="directory">en</filename> directory, change back to
it.</para>
<screen>&prompt.root; <userinput><command>cd</command> <replaceable>/usr/build/www/en</replaceable></userinput></screen>
</step>
<step>
- <para>Run the &man.make.1; <maketarget>install</maketarget> target,
- setting the <makevar>DESTDIR</makevar> variable to the name of the
- directory you want to install the files to. The actual files are
- installed under <filename class="directory">$DESTDIR/data</filename>
+ <para>Run the &man.make.1; <maketarget>install</maketarget>
+ target, setting the <makevar>DESTDIR</makevar> variable to
+ the name of the directory you want to install the files to.
+ The actual files are installed under <filename
+ class="directory">$DESTDIR/data</filename>
which should be configured as your web server's document
root.</para>
@@ -296,11 +299,12 @@
</step>
<step>
- <para>If you have previously installed the web pages into the same
- directory the install process will not have deleted any old or
- outdated pages. For example, if you build and install a new copy
- of the site every day, this command will find and delete all
- files that have not been updated in three days.</para>
+ <para>If you have previously installed the web pages into the
+ same directory the install process will not have deleted any
+ old or outdated pages. For example, if you build and
+ install a new copy of the site every day, this command will
+ find and delete all files that have not been updated in
+ three days.</para>
<screen>&prompt.root; <userinput><command>find</command> <replaceable>/usr/local/www</replaceable> <option>-ctime</option> 3 <option>-print0</option> | <command>xargs</command> <option>-0</option> <command>rm</command></userinput></screen>
</step>
@@ -321,11 +325,12 @@
<screen><userinput>&prompt.root; <makevar>CVSROOT</makevar>=<replaceable>/usr/dcvs</replaceable>; <command>export</command> <makevar>CVSROOT</makevar></userinput></screen>
- <para><envar>CVSROOT</envar> is an environment variable. You must
- set it on the command line or in your dot files
- (e.g., <filename>~/.profile</filename>). The exact syntax will
- differ depending on your shell (the above example is for
- <application>bash</application> and bash-like shells).</para>
+ <para><envar>CVSROOT</envar> is an environment variable.
+ You must set it on the command line or in your dot files
+ (e.g., <filename>~/.profile</filename>). The exact syntax
+ will differ depending on your shell (the above example is
+ for <application>bash</application> and bash-like
+ shells).</para>
</listitem>
</varlistentry>
@@ -334,15 +339,15 @@
<listitem>
<para>If set and not empty, the makefiles will build and
- install only the English documents. All translations will be
- ignored. E.g.:</para>
+ install only the English documents. All translations will
+ be ignored. E.g.:</para>
<screen>&prompt.root; <userinput><command>make</command> <makevar>ENGLISH_ONLY=YES</makevar> <maketarget>all</maketarget> <maketarget>install</maketarget></userinput></screen>
<para>If you want to unset the variable
- <makevar>ENGLISH_ONLY</makevar> and build all pages, including
- translations, set the variable <makevar>ENGLISH_ONLY</makevar>
- to an empty value:</para>
+ <makevar>ENGLISH_ONLY</makevar> and build all pages,
+ including translations, set the variable
+ <makevar>ENGLISH_ONLY</makevar> to an empty value:</para>
<screen>&prompt.root; <userinput><command>make</command> <makevar>ENGLISH_ONLY=""</makevar> <maketarget>all</maketarget> <maketarget>install</maketarget> <maketarget>clean</maketarget></userinput></screen>
</listitem>
@@ -352,10 +357,13 @@
<term><makevar>WEB_ONLY</makevar></term>
<listitem>
- <para>If set and not empty, the Makefiles will build and install
- only the HTML pages from the <filename class="directory">www</filename> directory. All documents from
- the <filename class="directory">doc</filename> directory (Handbook,
- FAQ, Tutorials) will be ignored. E.g.:</para>
+ <para>If set and not empty, the Makefiles will build and
+ install only the HTML pages from the <filename
+ class="directory">www</filename> directory. All
+ documents from the <filename
+ class="directory">doc</filename>
+ directory (Handbook, FAQ, Tutorials) will be ignored.
+ E.g.:</para>
<screen>&prompt.root; <userinput><command>make</command> <makevar>WEB_ONLY=YES</makevar> <maketarget>all</maketarget> <maketarget>install</maketarget></userinput></screen>
</listitem>
@@ -368,7 +376,8 @@
<para>If set, the Makefiles will build and install only for
the languages specified by this variable inside the
<filename class="directory">www</filename> directory. All
- other languages except English will be ignored. E.g.:</para>
+ other languages except English will be ignored.
+ E.g.:</para>
<screen>&prompt.root; <userinput>make WEB_LANG="el es hu nl" all install</userinput></screen>
</listitem>
@@ -378,19 +387,21 @@
<term><makevar>NOPORTSCVS</makevar></term>
<listitem>
- <para>If set, the Makefiles will not checkout files from the ports
- CVS repository. Instead, it will copy the files from
- <filename class="directory">/usr/ports</filename> (or where the
- variable <envar>PORTSBASE</envar> points to).</para>
+ <para>If set, the Makefiles will not checkout files from the
+ ports CVS repository. Instead, it will copy the files
+ from <filename class="directory">/usr/ports</filename> (or
+ where the variable <envar>PORTSBASE</envar> points
+ to).</para>
</listitem>
</varlistentry>
</variablelist>
- <para><makevar>WEB_ONLY</makevar>, <makevar>WEB_LANG</makevar>, <makevar>ENGLISH_ONLY</makevar> and
- <makevar>NOPORTSCVS</makevar> are make variables. You can set the
- variables in <filename>/etc/make.conf</filename>,
- <filename>Makefile.inc</filename>, as environment variables on the
- command line, or in your dot files.</para>
+ <para><makevar>WEB_ONLY</makevar>, <makevar>WEB_LANG</makevar>,
+ <makevar>ENGLISH_ONLY</makevar> and
+ <makevar>NOPORTSCVS</makevar> are make variables. You can set
+ the variables in <filename>/etc/make.conf</filename>,
+ <filename>Makefile.inc</filename>, as environment variables on
+ the command line, or in your dot files.</para>
</sect1>
</chapter>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml#32 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml,v 1.218 2012/02/13 23:21:01 eadler Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/eresources/chapter.sgml,v 1.219 2012/02/24 14:10:05 gjb Exp $
-->
<appendix id="eresources">
@@ -217,11 +217,6 @@
</row>
<row>
- <entry>&a.audit.name;</entry>
- <entry>Source code audit project</entry>
- </row>
-
- <row>
<entry>&a.binup.name;</entry>
<entry>Design and development of the binary update system</entry>
</row>
@@ -516,11 +511,6 @@
</row>
<row>
- <entry>&a.testing.name;</entry>
- <entry>FreeBSD Performance and Stability Tests</entry>
- </row>
-
- <row>
<entry>&a.tilera.name;</entry>
<entry>Porting FreeBSD to the Tilera family of CPUs</entry>
</row>
@@ -949,29 +939,6 @@
</varlistentry>
<varlistentry>
- <term>&a.audit.name;</term>
-
- <listitem>
- <para><emphasis>Source code audit project</emphasis></para>
-
- <para>This is the mailing list for the FreeBSD source code
- audit project. Although this was originally intended for
- security-related changes, its charter has been expanded to
- review any code changes.</para>
-
- <para>This list is very heavy on patches, and is probably of no
- interest to the average FreeBSD user. Security discussions
- not related to a particular code change are held on
- freebsd-security. Conversely, all developers are encouraged
- to send their patches here for review, especially if they
- touch a part of the system where a bug may adversely affect
- the integrity of the system.</para>
-
-<!-- I can't actually find a charter for this, but there's this email: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=223347+225804+/usr/local/www/db/text/2000/cvs-all/20001210.cvs-all -->
- </listitem>
- </varlistentry>
-
- <varlistentry>
<term>&a.binup.name;</term>
<listitem>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/share/sgml/mailing-lists.ent#30 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
Names of FreeBSD mailing lists and related software.
- $FreeBSD: doc/en_US.ISO8859-1/share/sgml/mailing-lists.ent,v 1.88 2012/01/15 22:29:33 gjb Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/share/sgml/mailing-lists.ent,v 1.89 2012/02/24 14:10:05 gjb Exp $
-->
<!ENTITY a.mailman.listinfo "http://lists.FreeBSD.org/mailman/listinfo">
@@ -48,10 +48,6 @@
<!ENTITY a.atm "<ulink url='&a.atm.url;'>FreeBSD ATM networking mailing list</ulink>">
<!ENTITY a.atm.name "<ulink url='&a.atm.url;'>freebsd-atm</ulink>">
-<!ENTITY a.audit.url "&a.mailman.listinfo;/freebsd-audit">
-<!ENTITY a.audit "<ulink url='&a.audit.url;'>FreeBSD source code audit mailing list</ulink>">
-<!ENTITY a.audit.name "<ulink url='&a.audit.url;'>freebsd-audit</ulink>">
-
<!ENTITY a.binup.url "&a.mailman.listinfo;/freebsd-binup">
<!ENTITY a.binup "<ulink url='&a.binup.url;'>FreeBSD binary update system mailing list</ulink>">
<!ENTITY a.binup.name "<ulink url='&a.binup.url;'>freebsd-binup</ulink>">
@@ -483,10 +479,6 @@
<!ENTITY a.test "<ulink url='&a.test.url;'>FreeBSD test mailing list</ulink>">
<!ENTITY a.test.name "<ulink url='&a.test.url;'>freebsd-test</ulink>">
-<!ENTITY a.testing.url "&a.mailman.listinfo;/freebsd-testing">
-<!ENTITY a.testing "<ulink url='&a.testing.url;'>FreeBSD performance and stability testing mailing list</ulink>">
-<!ENTITY a.testing.name "<ulink url='&a.testing.url;'>freebsd-testing</ulink>">
-
<!ENTITY a.threads.url "&a.mailman.listinfo;/freebsd-threads">
<!ENTITY a.threads "<ulink url='&a.threads.url;'>FreeBSD threads mailing list</ulink>">
<!ENTITY a.threads.name "<ulink url='&a.threads.url;'>freebsd-threads</ulink>">
==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/geom/chapter.sgml#23 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Dutch Documentation Project
- $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/geom/chapter.sgml,v 1.16 2012/02/15 22:42:48 rene Exp $
+ $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/geom/chapter.sgml,v 1.17 2012/02/21 21:47:05 rene Exp $
%SOURCE% en_US.ISO8859-1/books/handbook/geom/chapter.sgml
%SRCID% 1.55
==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/mail/chapter.sgml#23 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Dutch Documentation Project
- $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.9 2012/02/19 17:02:49 rene Exp $
+ $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.10 2012/02/21 22:15:17 rene Exp $
%SOURCE% en_US.ISO8859-1/books/handbook/mail/chapter.sgml
%SRCID% 1.146
==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.sgml#33 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.sgml,v 1.15 2012/02/19 17:45:57 rene Exp $
+ $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.sgml,v 1.16 2012/02/21 22:15:17 rene Exp $
%SOURCE% en_US.ISO8859-1/books/handbook/virtualization/chapter.sgml
%SRCID% 1.32
==== //depot/projects/docproj_nl/www/share/sgml/commercial.isp.xml#29 (text+ko) ====
@@ -1,12 +1,12 @@
<?xml version="1.0"?>
<!DOCTYPE entries PUBLIC "-//FreeBSD//DTD FreeBSD XML Database for Commercial Gallery//EN"
"http://www.FreeBSD.org/XML/www/share/sgml/gallery.dtd">
-<!-- $FreeBSD: www/share/sgml/commercial.isp.xml,v 1.72 2012/02/12 14:12:00 jkois Exp $ -->
+<!-- $FreeBSD: www/share/sgml/commercial.isp.xml,v 1.73 2012/02/23 17:21:22 jkois Exp $ -->
<entries>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
- $FreeBSD: www/share/sgml/commercial.isp.xml,v 1.72 2012/02/12 14:12:00 jkois Exp $
+ $FreeBSD: www/share/sgml/commercial.isp.xml,v 1.73 2012/02/23 17:21:22 jkois Exp $
</cvs:keyword>
</cvs:keywords>
@@ -474,6 +474,22 @@
</description>
</entry>
+ <entry id="Vellance">
+ <name>Vellance B.V.</name>
+ <url>http://www.vellance.com/</url>
+ <description>
+ Vellance B.V. is a Dutch managed hosting provider located in
+ Amsterdam. Our core-business is delivering advanced <a
+ href="http://www.vellance.com">Managed hosting</a> platforms.
+ Vellance primarily works with FreeBSD (since the 90's), so it is
+ not a surprise our managed hosting platforms and Virtual
+ Enterprise Cloud environment is completely based on a FreeBSD
+ infrastructure. Next to Virtual Dedicated Servers we offer many
+ products like Private Cloud infrastructures, Media hosting,
+ datacentre facilities and hosting consultancy.
+ </description>
+ </entry>
+
<entry id="Seiretto">
<name>Seiretto - UK FreeBSD Web Hosting</name>
<url>http://www.s4servers.com/</url>
==== //depot/projects/docproj_nl/www/share/sgml/events2012.xml#5 (text+ko) ====
@@ -10,7 +10,7 @@
<events>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
- $FreeBSD: www/share/sgml/events2012.xml,v 1.4 2012/01/30 19:36:16 brueffer Exp $
+ $FreeBSD: www/share/sgml/events2012.xml,v 1.5 2012/02/24 10:21:40 jkois Exp $
</cvs:keyword>
</cvs:keywords>
@@ -41,6 +41,37 @@
</description>
</event>
+ <event id="bsdday-eu-2012">
+ <name>BSDDay.eu/2012</name>
+ <url>http://bsdday.eu/2012</url>
+ <startdate>
+ <year>2012</year>
+ <month>5</month>
+ <day>5</day>
+ </startdate>
+ <enddate>
+ <year>2012</year>
+ <month>5</month>
+ <day>5</day>
+ </enddate>
+ <location>
+ <country code="AT">Austria</country>
+ <city>Vienna</city>
+ <site>UAS Technikum Wien</site>
+ </location>
+ <description>This year Beastie joins Tux on his tour in Vienna in
+ May: another "DanuBSDCon" is coming to gather Central-European BSD
+ people to meet! The event features several BSD developers and
+ enthusiasts to tell about their work, communicate with their fellows
+ and reach their potential future partners. As usual, there are no
+ formalities, papers, registration or participation fee, however the
+ invited folks are encouraged to give a brief talk about their
+ favorite BSD-related topic. The goal is to motivate everybody,
+ especially university students to work with BSD
+ systems.
+ </description>
+ </event>
+
<event id="bsdcan-2012">
<name>BSDCan 2012</name>
<url>http://www.bsdcan.org/</url>
More information about the p4-projects
mailing list