SRCS=		article.sgml

SRCS=		article.sgml

SRCS+=		${EXTRAS}

SRCS+=		${EXTRAS}

afterinstall:

afterinstall:

.for entry in ${EXTRAS}

.for entry in ${EXTRAS}

	${INSTALL_DOCS} ${.CURDIR}/${entry} ${DESTDIR}

	${INSTALL_DOCS} ${.CURDIR}/${entry} ${DESTDIR}

      Running a &fbus.ap; makes it easier to deploy security and software

      Running a &fbus.ap; makes it easier to deploy security and software

      patches to selected test machines before rolling them out to

      patches to selected test machines before rolling them out to

      production.  It also means a number of systems can be updated from the

      production.  It also means a number of systems can be updated from the

      This article outlines the steps involved in creating an internal

      This article outlines the steps involved in creating an internal

      &fbus.ap;.</para>

      &fbus.ap;.</para>

  </sect1>

  </sect1>

    <para>Here is the default <filename>build.conf</filename>, which should

    <para>Here is the default <filename>build.conf</filename>, which should

      be modified to suit your environment.</para>

      be modified to suit your environment.</para>

# Main configuration file for FreeBSD Update builds.  The

# Main configuration file for FreeBSD Update builds.  The

# release-specific configuration data is lower down in

# release-specific configuration data is lower down in

# the scripts tree.

# the scripts tree.

# Location from which to fetch releases

# Location from which to fetch releases

# Host platform

# Host platform

export HOSTPLATFORM=`uname -m`

export HOSTPLATFORM=`uname -m`

# Host name to use inside jails

# Host name to use inside jails

# Location of SSH key

# Location of SSH key

# SSH account into which files are uploaded

# SSH account into which files are uploaded

# Directory into which files are uploaded

# Directory into which files are uploaded

    <para>Parameters for consideration would be:</para>

    <para>Parameters for consideration would be:</para>

	  <para>This is the location where ISO images are downloaded from (by

	  <para>This is the location where ISO images are downloaded from (by

	    the <function>fetchiso()</function> subroutine

	    the <function>fetchiso()</function> subroutine

	    of <filename>scripts/build.subr</filename>).  The location

	    of <filename>scripts/build.subr</filename>).  The location

	    architecture-specific area

	    architecture-specific area

	    at <filename>scripts/RELEASE/ARCHITECTURE/build.subr</filename>

	    at <filename>scripts/RELEASE/ARCHITECTURE/build.subr</filename>

	    and applying local changes.</para>

	    and applying local changes.</para>

	  <para>The name of the build host.  This information will be

	  <para>The name of the build host.  This information will be

	    displayed on updated systems when issuing:</para>

	    displayed on updated systems when issuing:</para>

	  <screen>&prompt.user; <userinput>uname -v</userinput></screen>

	  <screen>&prompt.user; <userinput>uname -v</userinput></screen>

	  <para>The <application>SSH</application> key for uploading files to

	  <para>The <application>SSH</application> key for uploading files to

	    the update server.  A key pair can be created by

	    the update server.  A key pair can be created by

	    typing <command>ssh-keygen -t dsa</command>.  This parameter is

	    typing <command>ssh-keygen -t dsa</command>.  This parameter is

	  <para>The &man.ssh-keygen.1; manual page has more detailed

	  <para>The &man.ssh-keygen.1; manual page has more detailed

	    information about <application>SSH</application> and the

	    information about <application>SSH</application> and the

	    appropriate steps for creating and using one.</para>

	    appropriate steps for creating and using one.</para>

	  <para>Account for uploading files to the update

	  <para>Account for uploading files to the update

	    server.</para>

	    server.</para>

	  <para>Directory on the update server where files are uploaded

	  <para>Directory on the update server where files are uploaded

	    to.</para>

	    to.</para>

    <para>The default <filename>build.conf</filename> file shipped with

    <para>The default <filename>build.conf</filename> file shipped with

      the <application>freebsd-update-server</application> sources is

      the <application>freebsd-update-server</application> sources is

	  options for &os; 7.2-RELEASE on &arch.amd64; should be similar

	  options for &os; 7.2-RELEASE on &arch.amd64; should be similar

	  to:</para>

	  to:</para>

	<programlisting># SHA256 hash of RELEASE disc1.iso image.

	<programlisting># SHA256 hash of RELEASE disc1.iso image.

export WORLDPARTS="base catpages dict doc games info manpages proflibs lib32"

export WORLDPARTS="base catpages dict doc games info manpages proflibs lib32"

export SOURCEPARTS="base bin contrib crypto etc games gnu include krb5  \

export SOURCEPARTS="base bin contrib crypto etc games gnu include krb5  \

                lib libexec release rescue sbin secure share sys tools  \

                lib libexec release rescue sbin secure share sys tools  \

export KERNELPARTS="generic"

export KERNELPARTS="generic"

# EOL date

# EOL date

	  <para>To generate the "End of Life" number for

	  <para>To generate the "End of Life" number for

	    <filename>build.conf</filename>, refer to the "Estimated

	    <filename>build.conf</filename>, refer to the "Estimated

	    EOL" posted on the <ulink

	    EOL" posted on the <ulink

	      Security Website</ulink>.  The value

	      Security Website</ulink>.  The value

	    of <literal>EOL</literal> can be derived from the date listed on

	    of <literal>EOL</literal> can be derived from the date listed on

	    the web site, using the &man.date.1; utility, for example:</para>

	    the web site, using the &man.date.1; utility, for example:</para>

	  <screen>&prompt.user; <userinput>date -j -f '%Y%m%d-%H%M%S' '20090401-000000' '+%s'</userinput></screen>

	  <screen>&prompt.user; <userinput>date -j -f '%Y%m%d-%H%M%S' '20090401-000000' '+%s'</userinput></screen>

      </step>

      </step>

    </procedure>

    </procedure>

  </sect1>

  </sect1>

	    url="&url.books.handbook;/firewalls.html">firewall</ulink>

	    url="&url.books.handbook;/firewalls.html">firewall</ulink>

	  rule to block outgoing RST packets.  Due to a bug noted <ulink

	  rule to block outgoing RST packets.  Due to a bug noted <ulink

	    url="http://lists.freebsd.org/pipermail/freebsd-stable/2009-April/049578.html">in a posting</ulink>

	    url="http://lists.freebsd.org/pipermail/freebsd-stable/2009-April/049578.html">in a posting</ulink>

	  time-outs and failures when updating a system.</para>

	  time-outs and failures when updating a system.</para>

      </listitem>

      </listitem>