PERFORCE change 165451 for review
Rene Ladan
rene at FreeBSD.org
Mon Jun 29 22:13:43 UTC 2009
http://perforce.freebsd.org/chv.cgi?CH=165451
Change 165451 by rene at rene_self on 2009/06/29 22:13:13
IFC
Affected files ...
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#26 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/nanobsd/article.sgml#3 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/releng/article.sgml#4 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml#4 integrate
.. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#35 integrate
.. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/bibliography/chapter.sgml#6 integrate
.. //depot/projects/docproj_nl/www/en/donations/donors.sgml#16 integrate
.. //depot/projects/docproj_nl/www/en/donations/wantlist.sgml#11 integrate
.. //depot/projects/docproj_nl/www/en/favicon.ico#2 integrate
.. //depot/projects/docproj_nl/www/en/gnome/images/pav.jpg#2 delete
.. //depot/projects/docproj_nl/www/en/releng/index.sgml#26 integrate
.. //depot/projects/docproj_nl/www/share/sgml/notices.xml#3 integrate
.. //depot/projects/docproj_nl/www/share/sgml/press.xml#13 integrate
Differences ...
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#26 (text+ko) ====
@@ -1,4 +1,4 @@
-<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.862 2009/06/10 15:43:02 amdmi3 Exp $ -->
+<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml,v 1.863 2009/06/26 12:40:28 avl Exp $ -->
<!--
NOTE TO COMMITTERS: Contributors lists are sorted in alphabetical
order by first name.
@@ -7299,6 +7299,11 @@
</listitem>
<listitem>
+ <para>Oleg Alexeenkov
+ <email>proler at gmail.com</email></para>
+ </listitem>
+
+ <listitem>
<para>Oleg Kiselyov
<email>oleg at pobox.com</email></para>
</listitem>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/nanobsd/article.sgml#3 (text+ko) ====
@@ -15,7 +15,7 @@
</author>
</authorgroup>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/nanobsd/article.sgml,v 1.4 2008/08/06 22:03:49 pgj Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/nanobsd/article.sgml,v 1.5 2009/06/26 00:24:13 keramida Exp $</pubdate>
<copyright>
<year>2006</year>
@@ -220,8 +220,8 @@
<title>Configuration options</title>
<para>With configuration settings, it is possible to configure options
- passed to both the <literal>buildworld</literal>
- and <literal>installworld</literal> stages of the
+ passed to both the <maketarget>buildworld</maketarget>
+ and <maketarget>installworld</maketarget> stages of the
<application>NanoBSD</application> build process, as well as internal
options passed to the main build process of
<application>NanoBSD</application>. Through these options it is
@@ -252,18 +252,18 @@
<listitem>
<para><literal>CONF_BUILD</literal> — Options passed
- to the <literal>buildworld</literal> stage of the build.</para>
+ to the <maketarget>buildworld</maketarget> stage of the build.</para>
</listitem>
<listitem>
<para><literal>CONF_INSTALL</literal> — Options passed
- to the <literal>installworld</literal> stage of the build.</para>
+ to the <maketarget>installworld</maketarget> stage of the build.</para>
</listitem>
<listitem>
<para><literal>CONF_WORLD</literal> — Options passed to both
- the <literal>buildworld</literal> and
- the <literal>installworld</literal> stage of the build.</para>
+ the <maketarget>buildworld</maketarget> and
+ the <maketarget>installworld</maketarget> stage of the build.</para>
</listitem>
<listitem>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/releng/article.sgml#4 (text+ko) ====
@@ -9,7 +9,7 @@
]>
<article>
- <title>FreeBSD Release Engineering</title>
+ <title>&os; Release Engineering</title>
<articleinfo>
<!-- This paper was presented at BSDCon Europe in Brighton, UK on
@@ -24,9 +24,9 @@
<firstname>Murray</firstname>
<surname>Stokely</surname>
<authorblurb>
- <para>I've been involved in the development of FreeBSD based products
+ <para>I've been involved in the development of &os; based products
since 1997 at Walnut Creek CDROM, BSDi, and now Wind River Systems.
- FreeBSD 4.4 was the first official release of FreeBSD that I played
+ &os; 4.4 was the first official release of &os; that I played
a significant part in.</para>
</authorblurb>
<affiliation>
@@ -37,7 +37,7 @@
</author>
</authorgroup>
- <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/releng/article.sgml,v 1.81 2008/10/05 12:41:45 hrs Exp $</pubdate>
+ <pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/releng/article.sgml,v 1.83 2009/06/24 22:25:26 keramida Exp $</pubdate>
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
@@ -48,11 +48,11 @@
</legalnotice>
<abstract>
- <para>This paper describes the approach used by the FreeBSD
+ <para>This paper describes the approach used by the &os;
release engineering team to make production quality releases
- of the FreeBSD Operating System. It details the methodology
- used for the official FreeBSD releases and describes the tools
- available for those interested in producing customized FreeBSD
+ of the &os; Operating System. It details the methodology
+ used for the official &os; releases and describes the tools
+ available for those interested in producing customized &os;
releases for corporate rollouts or commercial
productization.</para>
</abstract>
@@ -63,54 +63,54 @@
<sect1 id="introduction">
<title>Introduction</title>
- <para>The development of FreeBSD is a very open process. FreeBSD is
+ <para>The development of &os; is a very open process. &os; is
comprised of contributions from thousands of people around the
- world. The FreeBSD Project provides anonymous
+ world. The &os; Project provides anonymous
<acronym>CVS</acronym>[1] access to the general public so that
others can have access to log messages, diffs (patches) between
development branches, and other productivity enhancements that
formal source code management provides. This has been a huge help
- in attracting more talented developers to FreeBSD. However, I
+ in attracting more talented developers to &os;. However, I
think everyone would agree that chaos would soon manifest if write
access was opened up to everyone on the Internet. Therefore only
a <quote>select</quote> group of nearly 300 people are given write
access to the <acronym>CVS</acronym> repository. These
<emphasis>committers[5]</emphasis> are responsible for the bulk of
- FreeBSD development. An elected <emphasis>core-team[6]</emphasis>
+ &os; development. An elected <emphasis>core-team[6]</emphasis>
of very senior developers provides some level of direction over
the project.</para>
<para>The rapid pace of <systemitem
- class="osname">FreeBSD</systemitem> development leaves little time
+ class="osname">&os;</systemitem> development leaves little time
for polishing the development system into a production quality
release. To solve this dilemma, development continues on two
parallel tracks. The main development branch is the
<emphasis>HEAD</emphasis> or <emphasis>trunk</emphasis> of our CVS
- tree, known as <quote>FreeBSD-CURRENT</quote> or
+ tree, known as <quote>&os;-CURRENT</quote> or
<quote>-CURRENT</quote> for short.</para>
<para>A more stable branch is maintained, known as
- <quote>FreeBSD-STABLE</quote> or <quote>-STABLE</quote> for short.
+ <quote>&os;-STABLE</quote> or <quote>-STABLE</quote> for short.
Both branches live in a master CVS repository in California and
are replicated via <application
class="software">CVSup</application>[2] to mirrors all over the
- world. FreeBSD-CURRENT[7] is the <quote>bleeding-edge</quote> of
- FreeBSD development where all new changes first enter the system.
- FreeBSD-STABLE is the development branch from which major releases
+ world. &os;-CURRENT[7] is the <quote>bleeding-edge</quote> of
+ &os; development where all new changes first enter the system.
+ &os;-STABLE is the development branch from which major releases
are made. Changes go into this branch at a different pace, and
with the general assumption that they have first gone into
- FreeBSD-CURRENT and have been thoroughly tested by our user
+ &os;-CURRENT and have been thoroughly tested by our user
community.</para>
<para>In the interim period between releases, monthly snapshots are
- built automatically by the FreeBSD Project build machines and made
+ built automatically by the &os; Project build machines and made
available for download from <systemitem
class="resource">ftp://ftp.freebsd.org/pub/FreeBSD/snapshots/</systemitem>.
The widespread availability of binary release snapshots, and the
tendency of our user community to keep up with -STABLE development
with CVSup and <quote><command>make</command>
<maketarget>world</maketarget></quote>[7] helps to keep
- FreeBSD-STABLE in a very reliable condition even before the
+ &os;-STABLE in a very reliable condition even before the
quality assurance activities ramp up pending a major
release.</para>
@@ -121,11 +121,11 @@
interface provided at <ulink
url="http://www.FreeBSD.org/send-pr.html"></ulink>.
In addition to the multitude of different technical mailing lists
- about FreeBSD, the &a.qa; provides a forum for discussing the finer
+ about &os;, the &a.qa; provides a forum for discussing the finer
points of <quote>release-polishing</quote>.</para>
<para>To service our most conservative users, individual release
- branches were introduced with FreeBSD 4.3.
+ branches were introduced with &os; 4.3.
These release branches are created shortly before a final release
is made. After the release goes out, only the most critical
security fixes and additions are merged onto the release branch.
@@ -169,7 +169,7 @@
<term><xref linkend="lessons-learned"></term>
<listitem>
- <para>Some of the lessons learned through the release of &os; 4.4.</para>
+ <para>Some of the lessons learned through the release of &os; 4.4.</para>
</listitem>
</varlistentry>
@@ -188,8 +188,8 @@
<sect1 id="release-proc">
<title>Release Process</title>
- <para>New releases of FreeBSD are released from the -STABLE branch
- at approximately four month intervals. The FreeBSD release
+ <para>New releases of &os; are released from the -STABLE branch
+ at approximately four month intervals. The &os; release
process begins to ramp up 45 days before the anticipated release
date when the release engineer sends an email to the development
mailing lists to remind developers that they only have 15 days to
@@ -291,7 +291,7 @@
vernacular for a label that identifies the source at a specific point
in time. By tagging the tree, we ensure that future release builders
will always be able to use the same source we used to create the
- official FreeBSD Project releases.</para>
+ official &os; Project releases.</para>
</sidebar>
<mediaobject>
@@ -300,7 +300,7 @@
</imageobject>
<textobject>
- <phrase>FreeBSD Development Branch</phrase>
+ <phrase>&os; Development Branch</phrase>
</textobject>
</mediaobject>
@@ -310,7 +310,7 @@
</imageobject>
<textobject>
- <phrase>FreeBSD 3.x STABLE Branch</phrase>
+ <phrase>&os; 3.x STABLE Branch</phrase>
</textobject>
</mediaobject>
@@ -320,7 +320,7 @@
</imageobject>
<textobject>
- <phrase>FreeBSD 4.x STABLE Branch</phrase>
+ <phrase>&os; 4.x STABLE Branch</phrase>
</textobject>
</mediaobject>
@@ -330,7 +330,7 @@
</imageobject>
<textobject>
- <phrase>FreeBSD 5.x STABLE Branch</phrase>
+ <phrase>&os; 5.x STABLE Branch</phrase>
</textobject>
</mediaobject>
@@ -340,7 +340,7 @@
</imageobject>
<textobject>
- <phrase>FreeBSD 6.x STABLE Branch</phrase>
+ <phrase>&os; 6.x STABLE Branch</phrase>
</textobject>
</mediaobject>
@@ -350,7 +350,7 @@
</imageobject>
<textobject>
- <phrase>FreeBSD 7.x STABLE Branch</phrase>
+ <phrase>&os; 7.x STABLE Branch</phrase>
</textobject>
</mediaobject>
</sect3>
@@ -360,7 +360,7 @@
<para>Before the final release can be tagged, built, and
released, the following files need to be modified to reflect
- the correct version of FreeBSD:</para>
+ the correct version of &os;:</para>
<itemizedlist>
<listitem>
@@ -538,7 +538,7 @@
allows tags to be manipulated with <command>cvs
tag -d <replaceable>tagname filename</replaceable></command>.
It is very important that any last minute changes be tagged
- appropriately as part of the release. FreeBSD releases must
+ appropriately as part of the release. &os; releases must
always be reproducible. Local hacks in the release
engineer's environment are not acceptable.</para>
</sect3>
@@ -549,7 +549,7 @@
<sect1 id="release-build">
<title>Release Building</title>
- <para>FreeBSD <quote>releases</quote> can be built by anyone with a
+ <para>&os; <quote>releases</quote> can be built by anyone with a
fast machine and access to a source repository. (That should be
everyone, since we offer anonymous CVS! See The Handbook for
details.) The <emphasis>only</emphasis> special requirement is
@@ -561,7 +561,7 @@
during the boot media creation phase. All of the tools necessary
to build a release are available from the CVS repository in
<filename>src/release</filename>. These tools aim to provide a
- consistent way to build FreeBSD releases. A complete release can
+ consistent way to build &os; releases. A complete release can
actually be built with only a single command, including the
creation of <acronym>ISO</acronym> images suitable for burning to
CDROM, installation floppies, and an FTP install directory. This
@@ -617,7 +617,7 @@
<para>There are many other variables available to customize the
release build. Most of these variables are documented at the
top of <filename>src/release/Makefile</filename>. The exact
- command used to build the official FreeBSD 4.7 (x86) release
+ command used to build the official &os; 4.7 (x86) release
was:</para>
<screen><command>make <literal>release CHROOTDIR=/local3/release \
@@ -717,7 +717,7 @@
<title>Building <application>&xfree86;</application></title>
<para><application>&xfree86;</application> is an important component for many desktop users.
- Prior to FreeBSD 4.6-RELEASE, releases used &xfree86;
+ Prior to &os; 4.6-RELEASE, releases used &xfree86;
3.<replaceable>X</replaceable> by default.
The easiest way to build these versions is to use the
<filename>src/release/scripts/X11/build_x.sh</filename> script.
@@ -728,13 +728,13 @@
<filename>XF86336</filename> directory of the installation
media.</para>
- <para>Beginning with FreeBSD 4.6-RELEASE, &man.sysinstall.8;
+ <para>Beginning with &os; 4.6-RELEASE, &man.sysinstall.8;
installs &xfree86; 4.<replaceable>X</replaceable> by default, as a
set of <quote>normal</quote> packages. These can either be the
packages generated by the package-building cluster or packages
built from an appropriately tagged ports tree.</para>
- <para>Beginning with FreeBSD 5.3-RELEASE, &man.sysinstall.8;
+ <para>Beginning with &os; 5.3-RELEASE, &man.sysinstall.8;
installs &xorg; packages instead of &xfree86; packages by
default.</para>
@@ -749,11 +749,11 @@
<sect2>
<title>Contributed Software (<quote>ports</quote>)</title>
- <para>The <ulink url="http://www.FreeBSD.org/ports">FreeBSD Ports
+ <para>The <ulink url="http://www.FreeBSD.org/ports">&os; Ports
collection</ulink> is a collection of over &os.numports;
- third-party software packages available for FreeBSD. The &a.portmgr;
+ third-party software packages available for &os;. The &a.portmgr;
is responsible for maintaining a consistent ports tree that can be used
- to create the binary packages that accompany official FreeBSD
+ to create the binary packages that accompany official &os;
releases.</para>
<para>The release engineering activities for our collection of
@@ -766,7 +766,7 @@
<sect2>
<title>Release ISOs</title>
- <para>Starting with FreeBSD 4.4, the FreeBSD Project decided to
+ <para>Starting with &os; 4.4, the &os; Project decided to
release all four ISO images that were previously sold on the
<emphasis>BSDi/Wind River Systems/FreeBSD Mall</emphasis>
<quote>official</quote> CDROM distributions. Each of the four
@@ -813,7 +813,7 @@
<para>The second disc is also largely created by <command>make
release</command>. This disc contains a <quote>live
filesystem</quote> that can be used from &man.sysinstall.8; to
- troubleshoot a FreeBSD installation. This disc should be
+ troubleshoot a &os; installation. This disc should be
bootable and should also contain a compressed copy of the CVS
repository in the <filename>CVSROOT</filename> directory and
commercial software demos in the <filename>commerce</filename>
@@ -824,7 +824,7 @@
<title>Discs 3 and 4</title>
<para>The remaining two discs contain additional software
- packages for FreeBSD. The packages should be clustered so that
+ packages for &os;. The packages should be clustered so that
a package and all of its <emphasis>dependencies</emphasis> are
included on the same disc. More information about the
creation of these discs is provided in the &art.re.pkgs;
@@ -858,7 +858,7 @@
<para>When the release has been thoroughly tested and packaged for
distribution, the master FTP site must be updated. The official
- FreeBSD public FTP sites are all mirrors of a master server that
+ &os; public FTP sites are all mirrors of a master server that
is open only to other FTP sites. This site is known as
<hostid>ftp-master</hostid>. When the release is ready, the
following files must be modified on <hostid>ftp-master</hostid>:</para>
@@ -903,8 +903,8 @@
</variablelist>
<para>For more information about the distribution mirror
- architecture of the FreeBSD FTP sites, please see the <ulink
- url="&url.articles.hubs;/">Mirroring FreeBSD</ulink> article.</para>
+ architecture of the &os; FTP sites, please see the <ulink
+ url="&url.articles.hubs;/">Mirroring &os;</ulink> article.</para>
<para>It may take many hours to two days after updating
<hostid>ftp-master</hostid> before a majority of the Tier-1 FTP
@@ -928,7 +928,7 @@
<sect2 id="dist-cdrom">
<title>CD-ROM Replication</title>
- <para>Coming soon: Tips for sending FreeBSD ISOs to a replicator
+ <para>Coming soon: Tips for sending &os; ISOs to a replicator
and quality assurance measures to be taken.</para>
</sect2>
@@ -938,14 +938,14 @@
<sect1 id="extensibility">
<title>Extensibility</title>
- <para>Although FreeBSD forms a complete operating system, there is
+ <para>Although &os; forms a complete operating system, there is
nothing that forces you to use the system exactly as we have
packaged it up for distribution. We have tried to design the
system to be as extensible as possible so that it can serve as a
platform that other commercial products can be built on top
of. The only <quote>rule</quote> we have about this is that if you
- are going to distribute FreeBSD with non-trivial changes, we
- encourage you to document your enhancements! The FreeBSD community
+ are going to distribute &os; with non-trivial changes, we
+ encourage you to document your enhancements! The &os; community
can only help support users of the software we provide. We
certainly encourage innovation in the form of advanced
installation and administration tools, for example, but we cannot
@@ -1002,7 +1002,7 @@
<sect2>
<title>Scripting <command>sysinstall</command></title>
- <para>The FreeBSD system installation and configuration tool,
+ <para>The &os; system installation and configuration tool,
&man.sysinstall.8;, can be scripted to provide automated installs
for large sites. This functionality can be used in conjunction
with &intel; PXE[12] to bootstrap systems from the network, or
@@ -1014,11 +1014,11 @@
<!-- Lessons Learned -->
<sect1 id="lessons-learned">
- <title>Lessons Learned from FreeBSD 4.4</title>
+ <title>Lessons Learned from &os; 4.4</title>
<para>The release engineering process for 4.4 formally began on
August 1st, 2001. After that date all commits to the
- <literal>RELENG_4</literal> branch of FreeBSD had to be explicitly
+ <literal>RELENG_4</literal> branch of &os; had to be explicitly
approved by the &a.re;. The first
release candidate for the x86 architecture was released on August
16, followed by 4 more release candidates leading up to the final
@@ -1029,11 +1029,11 @@
little over a month.</para>
<para>Our user community has made it very clear that the security
- and stability of a FreeBSD release should not be sacrificed for
- any self-imposed deadlines or target release dates. The FreeBSD
+ and stability of a &os; release should not be sacrificed for
+ any self-imposed deadlines or target release dates. The &os;
Project has grown tremendously over its lifetime and the need for
standardized release engineering procedures has never been more
- apparent. This will become even more important as FreeBSD is
+ apparent. This will become even more important as &os; is
ported to new platforms.</para>
</sect1>
@@ -1043,7 +1043,7 @@
<para>It is imperative for our release engineering activities to
scale with our growing userbase. Along these lines we are working
- very hard to document the procedures involved in producing FreeBSD
+ very hard to document the procedures involved in producing &os;
releases.</para>
<itemizedlist>
@@ -1071,7 +1071,7 @@
<listitem>
<para><emphasis>Regression Testing</emphasis> - We need better
- automated correctness testing for FreeBSD.</para>
+ automated correctness testing for &os;.</para>
</listitem>
<listitem>
@@ -1092,14 +1092,14 @@
<para>I would like to thank Jordan Hubbard for giving me the
opportunity to take on some of the release engineering
- responsibilities for FreeBSD 4.4 and also for all of his work
- throughout the years making FreeBSD what it is today. Of course
+ responsibilities for &os; 4.4 and also for all of his work
+ throughout the years making &os; what it is today. Of course
the release would not have been possible without all of the
release-related work done by &a.asami;, &a.steve;, &a.bmah;, &a.nik;,
- &a.obrien;, &a.kris;, &a.jhb; and the rest of the FreeBSD development
+ &a.obrien;, &a.kris;, &a.jhb; and the rest of the &os; development
community. I would also like to thank &a.rgrimes;, &a.phk;, and others
who worked on the release engineering tools in the very early days
- of FreeBSD. This article was influenced by release engineering
+ of &os;. This article was influenced by release engineering
documents from the CSRG[13], the NetBSD Project[10], and John
Baldwin's proposed release engineering process notes[11].</para>
</sect1>
@@ -1116,17 +1116,17 @@
<para>[3] <ulink url="http://pointyhat.FreeBSD.org"></ulink></para>
- <para>[4] FreeBSD Ports Collection
+ <para>[4] &os; Ports Collection
<ulink url="http://www.FreeBSD.org/ports"></ulink></para>
- <para>[5] FreeBSD Committers <ulink
+ <para>[5] &os; Committers <ulink
url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/articles/contributors/staff-committers.html"></ulink>
</para>
- <para>[6] FreeBSD Core Team
+ <para>[6] &os; Core Team
<ulink url="&url.base;/administration.html#t-core"></ulink></para>
- <para>[7] FreeBSD Handbook
+ <para>[7] &os; Handbook
<ulink url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook"></ulink>
</para>
@@ -1134,14 +1134,14 @@
<ulink url="http://www.gnu.org/software/gnats"></ulink>
</para>
- <para>[9] FreeBSD PR Statistics
+ <para>[9] &os; PR Statistics
<ulink url="http://www.FreeBSD.org/prstats/index.html"></ulink></para>
<para>[10] NetBSD Developer Documentation: Release Engineering
<ulink url="http://www.NetBSD.org/developers/releng/index.html"></ulink>
</para>
- <para>[11] John Baldwin's FreeBSD Release Engineering Proposal
+ <para>[11] John Baldwin's &os; Release Engineering Proposal
<ulink url="http://people.FreeBSD.org/~jhb/docs/releng.txt"></ulink>
</para>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml#4 (text+ko) ====
@@ -6,7 +6,7 @@
and Tom Rhodes <trhodes at FreeBSD.org>
For the FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml,v 1.46 2008/12/22 21:51:29 trhodes Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml,v 1.47 2009/06/29 18:51:34 manolis Exp $
-->
<chapter id="vinum-vinum">
@@ -46,7 +46,7 @@
implemented. One way some users safeguard themselves against such
issues is through the use of multiple, and sometimes redundant,
disks. In addition to supporting various cards and controllers
- for hardware RAID systems, the base FreeBSD system includes the
+ for hardware RAID systems, the base &os; system includes the
Vinum Volume Manager, a block device driver that implements
virtual disk drives. <emphasis>Vinum</emphasis> is a
so-called <emphasis>Volume Manager</emphasis>, a virtual disk
@@ -60,7 +60,7 @@
Manager.</para>
<note>
- <para>Starting with FreeBSD 5, Vinum has been rewritten in order
+ <para>Starting with &os; 5, Vinum has been rewritten in order
to fit into the GEOM architecture (<xref linkend="GEOM">),
retaining the original ideas, terminology, and on-disk
metadata. This rewrite is called <emphasis>gvinum</emphasis>
@@ -72,8 +72,8 @@
kernel module has been changed
from <filename>vinum.ko</filename>
to <filename>geom_vinum.ko</filename>, and all device nodes
- reside under <filename>/dev/gvinum</filename> instead
- of <filename>/dev/vinum</filename>. As of FreeBSD 6, the old
+ reside under <filename class="directory">/dev/gvinum</filename> instead
+ of <filename class="directory">/dev/vinum</filename>. As of &os; 6, the old
Vinum implementation is no longer available in the code
base.</para>
</note>
@@ -272,7 +272,7 @@
5. Of these, <acronym>RAID-5</acronym> is the most
interesting. As implemented in Vinum, it is a variant on a
striped organization which dedicates one block of each stripe
- to parity of the other blocks. As implemented by Vinum, a
+ to parity one of the other blocks. As implemented by Vinum, a
<acronym>RAID-5</acronym> plex is similar to a striped plex,
except that it implements <acronym>RAID-5</acronym> by
including a parity block in each stripe. As required by
@@ -394,7 +394,7 @@
<sect2>
<title>Which Plex Organization?</title>
- <para>The version of Vinum supplied with FreeBSD &rel.current; implements
+ <para>The version of Vinum supplied with &os; &rel.current; implements
two kinds of plex:</para>
<itemizedlist>
@@ -761,7 +761,7 @@
drives may be up to 32 characters long.</para>
<para>Vinum objects are assigned device nodes in the hierarchy
- <filename>/dev/gvinum</filename>. The configuration shown above
+ <filename class="directory">/dev/gvinum</filename>. The configuration shown above
would cause Vinum to create the following device nodes:</para>
<itemizedlist>
@@ -770,8 +770,8 @@
implemenation.</para></note>
<para>The control devices
- <filename>/dev/vinum/control</filename> and
- <filename>/dev/vinum/controld</filename>, which are used
+ <filename class="devicefile">/dev/vinum/control</filename> and
+ <filename class="devicefile">/dev/vinum/controld</filename>, which are used
by &man.gvinum.8; and the Vinum daemon respectively.</para>
</listitem>
@@ -779,31 +779,31 @@
<para>Device entries for each volume.
These are the main devices used by Vinum. Thus the configuration
above would include the devices
- <filename>/dev/gvinum/myvol</filename>,
- <filename>/dev/gvinum/mirror</filename>,
- <filename>/dev/gvinum/striped</filename>,
- <filename>/dev/gvinum/raid5</filename> and
- <filename>/dev/gvinum/raid10</filename>.</para>
+ <filename class="devicefile">/dev/gvinum/myvol</filename>,
+ <filename class="devicefile">/dev/gvinum/mirror</filename>,
+ <filename class="devicefile">/dev/gvinum/striped</filename>,
+ <filename class="devicefile">/dev/gvinum/raid5</filename> and
+ <filename class="devicefile">/dev/gvinum/raid10</filename>.</para>
</listitem>
<listitem>
<note><para>This only applies to the historic Vinum
implemenation.</para></note>
- <para>A directory <filename>/dev/vinum/drive</filename>
+ <para>A directory <filename class="directory">/dev/vinum/drive</filename>
with entries for each drive. These entries are in fact
symbolic links to the corresponding disk nodes.</para>
</listitem>
<listitem>
<para>All volumes get direct entries under
- <filename>/dev/gvinum/</filename>.</para>
+ <filename class="directory">/dev/gvinum/</filename>.</para>
</listitem>
<listitem>
<para>The directories
- <filename>/dev/gvinum/plex</filename>, and
- <filename>/dev/gvinum/sd</filename>, which contain
+ <filename class="directory">/dev/gvinum/plex</filename>, and
+ <filename class="directory">/dev/gvinum/sd</filename>, which contain
device nodes for each plex and for each subdisk,
respectively.</para>
</listitem>
@@ -823,7 +823,7 @@
sd length 100m drive drive4</programlisting>
<para>After processing this file, &man.gvinum.8; creates the following
- structure in <filename>/dev/gvinum</filename>:</para>
+ structure in <filename class="directory">/dev/gvinum</filename>:</para>
<programlisting>
drwxr-xr-x 2 root wheel 512 Apr 13 16:46 plex
@@ -857,14 +857,14 @@
utilities, notably &man.newfs.8;, which previously tried to
interpret the last letter of a Vinum volume name as a
partition identifier. For example, a disk drive may have a
- name like <filename>/dev/ad0a</filename> or
- <filename>/dev/da2h</filename>. These names represent
+ name like <filename class="devicefile">/dev/ad0a</filename> or
+ <filename class="devicefile">/dev/da2h</filename>. These names represent
the first partition (<devicename>a</devicename>) on the
first (0) IDE disk (<devicename>ad</devicename>) and the
eighth partition (<devicename>h</devicename>) on the third
(2) SCSI disk (<devicename>da</devicename>) respectively.
By contrast, a Vinum volume might be called
- <filename>/dev/gvinum/concat</filename>, a name which has
+ <filename class="devicefile">/dev/gvinum/concat</filename>, a name which has
no relationship with a partition name.</para>
<para>Normally, &man.newfs.8; interprets the name of the disk and
@@ -879,10 +879,10 @@
<screen>&prompt.root; <userinput>newfs /dev/gvinum/concat</userinput></screen>
<note><para>On &os; versions prior to 5.0 &man.newfs.8; requires
- an additional -v flag and the old device naming
- scheme:</para></note>
+ an additional <option>-v</option> flag and the old device naming
+ scheme:</para>
- <screen>&prompt.root; <userinput>newfs -v /dev/vinum/concat</userinput></screen>
+ <screen>&prompt.root; <userinput>newfs -v /dev/vinum/concat</userinput></screen></note>
</sect2>
</sect1>
@@ -1055,7 +1055,7 @@
start</command> command.</para>
<note><para>The following paragraphs are outlining the steps
- needed for FreeBSD.</para></note>
+ needed for &os;.</para></note>
<para>By placing the line:</para>
@@ -1081,7 +1081,7 @@
<title>Making a Vinum-based Root Volume Accessible to the
Bootstrap</title>
- <para>Since the current FreeBSD bootstrap is only 7.5 KB of
+ <para>Since the current &os; bootstrap is only 7.5 KB of
code, and already has the burden of reading files (like
<filename>/boot/loader</filename>) from the UFS filesystem, it
is sheer impossible to also teach it about internal Vinum
@@ -1235,10 +1235,10 @@
<para>The values to note are <literal>135680</literal> for the
offset (relative to partition
- <filename>/dev/da0h</filename>). This translates to 265
+ <filename class="devicefile">/dev/da0h</filename>). This translates to 265
512-byte disk blocks in <command>bsdlabel</command>'s terms.
Likewise, the size of this root volume is 245760 512-byte
- blocks. <filename>/dev/da1h</filename>, containing the
+ blocks. <filename class="devicefile">/dev/da1h</filename>, containing the
second replica of this root volume, has a symmetric
setup.</para>
==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#35 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
- $FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.1018 2009/06/11 21:03:47 zec Exp $
+ $FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.1019 2009/06/26 21:14:18 bz Exp $
-->
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
@@ -13194,6 +13194,22 @@
outbound to inbound path call detection and queuing,
which also changed the layout of struct thread.</entry>
</row>
+ <row>
+ <entry>800098</entry>
+ <entry>June 14, 2009</entry>
+ <entry>8.0-CURRENT after OpenSSL 0.9.8k import.</entry>
+ </row>
+ <row>
+ <entry>800099</entry>
+ <entry>June 22, 2009</entry>
+ <entry>8.0-CURRENT after NGROUPS update and moving
+ route virtualization into its own VImage module.</entry>
+ </row>
+ <row>
+ <entry>800100</entry>
+ <entry>June 24, 2009</entry>
+ <entry>8.0-CURRENT after SYSVIPC ABI change.</entry>
+ </row>
</tbody>
</tgroup>
</table>
==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/bibliography/chapter.sgml#6 (text+ko) ====
@@ -1,7 +1,7 @@
<!--
The FreeBSD Dutch Documentation Project
- $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/bibliography/chapter.sgml,v 1.5 2008/09/14 22:32:27 remko Exp $
+ $FreeBSD: doc/nl_NL.ISO8859-1/books/handbook/bibliography/chapter.sgml,v 1.6 2009/06/23 21:14:20 rene Exp $
%SOURCE% en_US.ISO8859-1/books/handbook/bibliography/chapter.sgml
%SRCID% 1.86
==== //depot/projects/docproj_nl/www/en/donations/donors.sgml#16 (text+ko) ====
@@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "..">
-<!ENTITY date "$FreeBSD: www/en/donations/donors.sgml,v 1.389 2009/04/24 20:20:37 wilko Exp $">
+<!ENTITY date "$FreeBSD: www/en/donations/donors.sgml,v 1.391 2009/06/26 19:01:36 rpaulo Exp $">
<!ENTITY title "Hardware Donors Page">
<!ENTITY % navinclude.about "INCLUDE">
<!ENTITY % developers SYSTEM "../developers.sgml"> %developers;
@@ -2572,6 +2572,27 @@
<td> wilko </td>
<td> Received </td>
</tr>
+
+ <tr>
+ <td> Edson Brandi <ebrandi at fugspbr.org> </td>
+ <td> BrookTree chipset TV Capture Card BT878 </td>
+ <td> lioux </td>
+ <td> Received </td>
+ </tr>
+
+ <tr>
+ <td> Charles Smeijer </td>
+ <td> HP JetDirect 175x print server </td>
+ <td> rpaulo </td>
+ <td> Received </td>
+ </tr>
+
+ <tr>
+ <td> <a href="http://www.gateworks.com/">Gateworks Corporation</a> </td>
+ <td> Cambria GW2358-4 board </td>
+ <td> rpaulo </td>
+ <td> Received </td>
+ </tr>
</table>
&footer;
==== //depot/projects/docproj_nl/www/en/donations/wantlist.sgml#11 (text+ko) ====
@@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "..">
-<!ENTITY date "$FreeBSD: www/en/donations/wantlist.sgml,v 1.475 2009/04/24 17:19:30 jkoshy Exp $">
+<!ENTITY date "$FreeBSD: www/en/donations/wantlist.sgml,v 1.476 2009/06/24 10:38:24 lioux Exp $">
<!ENTITY title "FreeBSD Developers Want List">
<!ENTITY email 'donations'>
<!ENTITY % navinclude.about "INCLUDE">
@@ -132,16 +132,6 @@
<tr>
<td>lioux</td>
<td>Brazil</td>
- <td>Network switch
- 10/100 Mbits. Network card Intel EtherExpress PCI 10/100
- Mbits</td>
- <td>Get a K6 based machine back online and add it as an
- extra terminal to FreeBSD home LAN.</td>
- </tr>
-
- <tr>
- <td>lioux</td>
- <td>Brazil</td>
<td>Books on any of the following subjects: network
protocol scheduling (bandwidth/transmission efficiency),
process scheduling, scheduling theory in general, digesting
@@ -165,15 +155,6 @@
</tr>
<tr>
- <td>lioux</td>
- <td>Brazil</td>
- <td>BrookTree chipset TV Capture Card: either BT848 or BT878
- (preferred) that already works with FreeBSD.</td>
- <td>Adding BrookTree support to graphics/ffmpeg and several
- other video processing programs.</td>
- </tr>
-
- <tr>
<td>marcel</td>
<td>CA, USA</td>
<td>1GB of low-profile PC133 SDRAM (168pin DIMM). Memory can be
==== //depot/projects/docproj_nl/www/en/favicon.ico#2 (text+ko) ====
@@ -1,10 +1,18 @@
--Œ-©--ÃÇÊÍ Ï"Ñ&Ï,Â0Ö5Ø7Ø:ÛAáIèMëMê IÞMᇟð¨°Ò-ÆÊÎÐ Ó"Õ'×+Ð#¶À-±ÍÐÔ Ö"Ù'Û#Ö ©-à-“hh¿$$h-»•33¬+6+¸ÿ+—ÿ‚™»å+ +###%%$ + g'&(œ01QÀ24hÜ7<uä=Bxå4JqÞ!I^Å27
+m++±ÿQ©óÿ°ÿÿÿÇÚÚþg+??=~Ø×ñÿ–¨îÿ”µôÿêöþÿòûÿÿ£ÍüÿNzõÿ:õÿ+
+ÿ…ÿ10}ÿ@@sÿCBlÿP[‘ÿºÀ×ÿONL”+
+H¶µÄêØßÿÿ©½õÿØãüÿëöþÿÕíþÿ¨Èûÿ‚úÿFnüÿ8üÿ+»ÿkrìÿ´»ÿÿÀÑÿÿ¸ÊëúääåøÿÿÿÿÿÿÿÿÿÿÿÿþÿÿÿýÿÿÿÿþÿÿýýþÿàáöÿÖ×õÿÐÒôÿ®êÿÄÇõÿ¼ÑëùÁÒëùöüÿÿö÷ÿÿ³·÷ÿ29Êÿ+G+==== //depot/projects/docproj_nl/www/en/releng/index.sgml#26 (text+ko) ====
@@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "..">
-<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.269 2009/06/11 06:28:50 maxim Exp $">
+<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.271 2009/06/26 11:41:18 blackend Exp $">
<!ENTITY email 're'>
<!ENTITY title "Release Engineering Information">
<!ENTITY % navinclude.developers "INCLUDE">
@@ -56,7 +56,7 @@
<tr>
<td>August 2009</td>
<td>FreeBSD 8.0</td>
- <td>code slush since June 1st</td>
+ <td>Code Freeze since June 26th</td>
</tr>
</table>
@@ -79,9 +79,12 @@
<tr>
<td><tt>HEAD</tt></td>
- <td>Open </td>
- <td>committers</td>
- <td>Active development branch for 8-CURRENT.</td>
+ <td>Frozen</td>
+ <td>&contact.re;</td>
+ <td>Active development branch for 8-CURRENT. Code Freeze in
+ preparation for 8.0-RELEASE. All commits must have
+ &contact.re; approval until after RELENG_8 branch has been
+ created.</td>
</tr>
<tr>
==== //depot/projects/docproj_nl/www/share/sgml/notices.xml#3 (text+ko) ====
@@ -2,7 +2,7 @@
<advisories>
<cvs:keywords xmlns:cvs="http://www.FreeBSD.org/XML/CVS" version="1.0">
<cvs:keyword name="freebsd">
- $FreeBSD: www/share/sgml/notices.xml,v 1.13 2009/03/23 00:10:01 cperciva Exp $
+ $FreeBSD: www/share/sgml/notices.xml,v 1.14 2009/06/24 05:45:57 cperciva Exp $
</cvs:keyword>
</cvs:keywords>
@@ -10,6 +10,26 @@
<name>2009</name>
<month>
+ <name>6</name>
+
+ <day>
+ <name>24</name>
+
+ <notice>
+ <name>FreeBSD-EN-09:04.fork</name>
+ </notice>
+
+ <notice>
+ <name>FreeBSD-EN-09:03.fxp</name>
+ </notice>
+
+ <notice>
+ <name>FreeBSD-EN-09:02.bce</name>
+ </notice>
+ </day>
+ </month>
+
+ <month>
<name>3</name>
>>> TRUNCATED FOR MAIL (1000 lines) <<<
More information about the p4-projects
mailing list