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

Correct a few typos.

Browse source 
Add a few paragraphs from the Handbook to describe how to mirror a
local CVS repository, and point to the CVSup section of the Handbook
for more details.

Note that if RELEASETAG is omitted from "make release", then a
-CURRENT snapshot will be built. (Also from Handbook).
This commit is contained in:
Murray Stokely 2002-02-13 10:34:51 +00:00
parent 619cf2ffb4
commit 6d11e7c4ba
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=12171
1 changed files with 22 additions and 9 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -129,7 +129,7 @@
<para><link linkend="release-proc">Section 2</link> discusses the
different phases of the release engineering process leading up to
the actual system build and <link linkend="release-build">section
3</link> descibes the actual build process. <link
3</link> describes the actual build process. <link
linkend="extensibility">Section 4</link> describes how the base
release may be extended by third parties and <link
linkend="lessons-learned">section 5</link> details some of the
@ -377,19 +377,19 @@
<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
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
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
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
<filename>src/release</filename>. These tools aim to provide a
consistent way to build FreeBSD 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
CDROM, installation floppies, and an FTP install directory. This
command is aptly named <quote><command>make
<literal>release</literal></command></quote>.</para>
@ -426,6 +426,19 @@
</listitem>
</itemizedlist>
<para>If you do not already have access to a local CVS
repository, then you may mirror one with <ulink
url="http://www.FreeBSD.org/handbook/synching.html#CVSUP">CVSup</ulink>.
The supplied supfile,
<filename>/usr/share/examples/cvsup/cvs-supfile</filename>, is
a useful starting point for mirroring the CVS
repository.</para>
<para>If <makevar>RELEASETAG</makevar> is omitted, then the
release will be built from the HEAD (a.k.a. -CURRENT) branch.
Releases built from this branch are normally referred to as
<quote>-CURRENT snapshots</quote>.</para>
<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
@ -438,9 +451,9 @@
RELEASETAG=RELENG_4_4_0_RELEASE</literal>
</command>
</screen>
<para>The release Makefile can be broken down into several distinct
steps.</para>
steps.</para>
<itemizedlist>
<listitem>
@ -828,7 +841,7 @@
</sect1>
<!-- Acknowledgments -->
<!-- Acknowledgements -->
<sect1 id="ackno">
<title>Acknowledgements</title>