Source string Read only

(itstool) path: sect2/para
Context English State
chroot into the release build hierarchy, to make it harder for the outside environment to taint this build.
<command>make world</command> in the chrooted environment.
Build of Kerberos-related binaries.
Build <filename>GENERIC</filename> kernel.
Creation of a staging directory tree where the binary distributions will be built and packaged.
Build and installation of the documentation toolchain needed to convert the documentation source (SGML) into HTML and text documents that will accompany the release.
Build and installation of the actual documentation (user manuals, tutorials, release notes, hardware compatibility lists, and so on.)
Package up distribution tarballs of the binaries and sources.
Create FTP installation hierarchy.
<emphasis>(optionally)</emphasis> Create ISO images for CDROM/DVD media.
For more information about the release build infrastructure, please see <citerefentry><refentrytitle>release</refentrytitle><manvolnum>7</manvolnum></citerefentry>.
It is important to remove any site-specific settings from <filename>/etc/make.conf</filename>. For example, it would be unwise to distribute binaries that were built on a system with <varname>CPUTYPE</varname> set to a specific processor.
Contributed Software (<quote>ports</quote>)
The <link xlink:href="">FreeBSD Ports collection</link> is a collection of over 24,000 third-party software packages available for FreeBSD. The Ports Management Team <email></email> is responsible for maintaining a consistent ports tree that can be used to create the binary packages that accompany official FreeBSD releases.
Release ISOs
Starting with FreeBSD 4.4, the FreeBSD 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 discs must contain a <filename>README.TXT</filename> file that explains the contents of the disc, a <filename>CDROM.INF</filename> file that provides meta-data for the disc so that <citerefentry><refentrytitle>bsdinstall</refentrytitle><manvolnum>8</manvolnum></citerefentry> can validate and use the contents, and a <filename>filename.txt</filename> file that provides a manifest for the disc. This <emphasis>manifest</emphasis> can be created with a simple command:
/stage/cdrom<prompt>#</prompt> <userinput>find . -type f | sed -e 's/^\.\///' | sort &gt; filename.txt</userinput>
The specific requirements of each CD are outlined below.
Disc 1
The first disc is almost completely created by <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, and as many popular third party software packages as will fit on the disc. The <filename>tools</filename> directory contains software that allow users to create installation floppies from other operating systems. This disc should be made bootable so that users of modern PCs do not need to create installation floppy disks.
If a custom kernel of FreeBSD is to be included, then <citerefentry><refentrytitle>bsdinstall</refentrytitle><manvolnum>8</manvolnum></citerefentry> and <citerefentry><refentrytitle>release</refentrytitle><manvolnum>7</manvolnum></citerefentry> must be updated to include installation instructions. The relevant code is contained in <filename>src/release</filename> and <filename>src/usr.sbin/bsdinstall</filename>. Specifically, the file <filename>src/release/Makefile</filename>, and <filename>dist.c</filename>, <filename>dist.h</filename>, <filename>menus.c</filename>, <filename>install.c</filename>, and <filename>Makefile</filename> will need to be updated under <filename>src/usr.sbin/bsdinstall</filename>. Optionally, you may choose to update <filename>bsdinstall.8</filename>.
Disc 2
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 <citerefentry><refentrytitle>bsdinstall</refentrytitle><manvolnum>8</manvolnum></citerefentry> to troubleshoot a FreeBSD 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> directory.
Multi-volume Support
<application>Sysinstall</application> supports multiple volume package installations. This requires that each disc have an <filename>INDEX</filename> file containing all of the packages on all volumes of a set, along with an extra field that indicates which volume that particular package is on. Each volume in the set must also have the <literal>CD_VOLUME</literal> variable set in the <filename>cdrom.inf</filename> file so that bsdinstall can tell which volume is which. When a user attempts to install a package that is not on the current disc, bsdinstall will prompt the user to insert the appropriate one.
FTP Sites
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 is open only to other FTP sites. This site is known as <systemitem>ftp-master</systemitem>. When the release is ready, the following files must be modified on <systemitem>ftp-master</systemitem>:
The installable FTP directory as output from <command>make release</command>.


User avatar None

New source string

FreeBSD Doc / articles_relengEnglish

New source string 9 months ago
Browse all component changes


English English
No related strings found in the glossary.

Source information

Source string comment
(itstool) path: sect2/para
Source string location
String age
9 months ago
Source string age
9 months ago
Translation file
articles/releng.pot, string 137