os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Assorted markup fixes, with the occasional spelling/punctuation fix.

Browse source
This commit is contained in:
Bruce A. Mah 2002-08-10 23:39:39 +00:00
parent 0548993ae7
commit 75e5cc7d9e
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=13830
1 changed files with 35 additions and 36 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

71
en_US.ISO8859-1/articles/releng/article.sgml
View file

@ -156,7 +156,7 @@
date when the release engineer sends an email to the development
mailing lists to remind developers that they only have 15 days to
integrate new changes before the code freeze. During this time,
many developers perform what have become know as <quote>MFC
many developers perform what have become known as <quote>MFC
sweeps</quote>. <acronym>MFC</acronym> stands for <quote>Merge
From CURRENT</quote> and it describes the process of merging a
tested change from our -CURRENT development branch to our -STABLE
@ -407,10 +407,10 @@
<para>FreeBSD <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
that the <devicename>vn</devicename> (<emphasis>On -CURRENT, this
device has been replaced by the new <devicename>md</devicename>
memory disk driver </emphasis>.) device must be available. If the
details.) The <emphasis>only</emphasis> special requirement is
that the &man.vn.4; device must be available. (On -CURRENT, this
device has been replaced by the new &man.md.4;
memory disk driver.) If the
device is not loaded into your kernel, then the kernel module
should be automatically loaded when &man.vnconfig.8; is executed
during the boot media creation phase. All of the tools necessary
@ -420,17 +420,17 @@
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
command is aptly named <quote><command>make
release</command></quote>.</para>
command is aptly named <command>make
release</command>.</para>
<sect2>
<title><quote>make release</quote></title>
<title><command>make release</command></title>
<para>To successfully build a release, you must first populate
<filename>/usr/obj</filename> by running <quote><command>make
world</command></quote> or simply
<quote><command>make
buildworld</command></quote>. The release
<filename>/usr/obj</filename> by running <command>make
world</command> or simply
<command>make
buildworld</command>. The release
target requires several variables be set properly to build a
release:</para>
@ -465,7 +465,7 @@
repository.</para>
<para>If <makevar>RELEASETAG</makevar> is omitted, then the
release will be built from the HEAD (a.k.a. -CURRENT) branch.
release will be built from the <literal>HEAD</literal> (a.k.a. -CURRENT) branch.
Releases built from this branch are normally referred to as
<quote>-CURRENT snapshots</quote>.</para>
@ -510,7 +510,7 @@
</listitem>
<listitem>
<para><quote><command>make world</command></quote>
<para><command>make world</command>
in the chrooted environment.</para>
</listitem>
@ -519,7 +519,7 @@
</listitem>
<listitem>
<para>Build <quote><filename>GENERIC</filename></quote> kernel.</para>
<para>Build <filename>GENERIC</filename> kernel.</para>
</listitem>
<listitem>
@ -630,9 +630,9 @@
<title>Disc 1</title>
<para>The first disc is almost completely created by
<quote><command>make
<literal>release</literal></command></quote>. The only changes
that should be made to the disc1 directory are the addition of
<command>make
release</command>. The only changes
that should be made to the <filename>disc1</filename> directory are the addition of
a <filename>tools</filename> directory, <application
class="software">XFree86</application>, and as many popular
third party software packages as will fit on the disc. The
@ -654,8 +654,8 @@
<sect3>
<title>Disc 2</title>
<para>The second disc is also largely created by <quote>make
release</quote>. This disc contains a <quote>live
<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
bootable and should also contain a compressed copy of the CVS
@ -689,8 +689,7 @@
FreeBSD 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>
following files must be modified on <hostid>ftp-master</hostid>:</para>
<variablelist>
<varlistentry>
@ -740,14 +739,14 @@
<para>It may take many hours after updating
<hostid>ftp-master</hostid> before a majority of the Tier-1 FTP
sites have the new software. It is imperative that the release
engineers coordinate with &a.hubs; before announcing the general
engineers coordinate with the &a.hubs; before announcing the general
availability of new software on the FTP sites.</para>
</sect2>
<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 FreeBSD ISOs to a replicator
and quality assurance measures to be taken.</para>
</sect2>
@ -777,7 +776,7 @@
additional kernel modules or userland tools be added to the
installation floppies. The <quote>quick and dirty</quote> way
to accomplish this would be to modify the staging directory of
an existing <quote>make release</quote> build hierarchy:</para>
an existing <command>make release</command> build hierarchy:</para>
<itemizedlist>
<listitem>
@ -810,15 +809,15 @@
<filename>${CHROOTDIR}/R/stage/floppies</filename>.</para>
<para>Alternatively, the
<quote><filename>boot.flp</filename></quote> make
<filename>boot.flp</filename> make
target can be called, or the filesystem
creating script,
<filename>src/release/scripts/doFS.sh</filename>, may be invoked
directly.</para>
<para>Local patches may also be supplied to the release build by
defining the <makevar>LOCAL_PATCH</makevar> variable in <quote>make
release</quote>.
defining the <makevar>LOCAL_PATCH</makevar> variable in <command>make
release</command>.
</para>
</sect2>
@ -875,20 +874,20 @@
release build are actually <quote>embarrassingly
parallel</quote>. Most of the tasks are very I/O intensive,
so having multiple high-speed disk drives is actually more important than
using multiple processors in speeding up the <quote>make
release</quote> process. If multiple disks are used for
different hierarchies in the <emphasis>chroot</emphasis>
environment, then the CVS checkout of the ports and doc trees
can be happening simultaneously to the <quote>make
<literal>world</literal></quote> on another disk. Using a
using multiple processors in speeding up the <command>make
release</command> process. If multiple disks are used for
different hierarchies in the &man.chroot.2;
environment, then the CVS checkout of the <filename>ports</filename> and <filename>doc</filename> trees
can be happening simultaneously as the <command>make
world</command> on another disk. Using a
<acronym>RAID</acronym> solution (hardware or software) can
significantly decrease the overall build time.</para>
</listitem>
<listitem>
<para><emphasis>Cross-building releases</emphasis> - Building
IA-64 or Alpha release on x86 hardware? <quote>make
TARGET=ia64 release</quote>.
IA-64 or Alpha release on x86 hardware? <command>make
TARGET=ia64 release</command>.
</para>
</listitem>