aboutsummaryrefslogtreecommitdiff
path: root/en_US.ISO8859-1/articles/freebsd-update-server/article.xml
diff options
context:
space:
mode:
Diffstat (limited to 'en_US.ISO8859-1/articles/freebsd-update-server/article.xml')
-rw-r--r--en_US.ISO8859-1/articles/freebsd-update-server/article.xml42
1 files changed, 13 insertions, 29 deletions
diff --git a/en_US.ISO8859-1/articles/freebsd-update-server/article.xml b/en_US.ISO8859-1/articles/freebsd-update-server/article.xml
index 7f1aff1ba7..8c2ff9996a 100644
--- a/en_US.ISO8859-1/articles/freebsd-update-server/article.xml
+++ b/en_US.ISO8859-1/articles/freebsd-update-server/article.xml
@@ -20,6 +20,7 @@
<year>2009</year>
<year>2010</year>
<year>2011</year>
+ <year>2013</year>
<holder role="mailto:jgh@FreeBSD.org">Jason Helfman</holder>
</copyright>
@@ -38,8 +39,8 @@
<abstract>
<para>This article describes building an internal &fbus.ap;.
The <ulink
- url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/">freebsd-update-server</ulink> software
- is written by &a.cperciva;, current Security Officer of &os;.
+ url="http://svnweb.freebsd.org/base/user/cperciva/freebsd-update-build/">freebsd-update-server</ulink>
+ software is written by &a.cperciva;, Security Officer Emeritus of &os;.
For users that think it is convenient to update their systems
against an official update server, building their own &fbus.ap; may
help to extend its functionality by supporting manually-tweaked
@@ -116,11 +117,11 @@
<title>Configuration: Installation &amp; Setup</title>
<para>Download the <ulink
- url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/">freebsd-update-server</ulink>
- software as a <ulink
- url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/freebsd-update-server.tar.gz?tarball=1">tar archive</ulink>,
- or use &man.csup.1; and the <literal>projects-all</literal>
- collection.</para>
+ url="http://svnweb.freebsd.org/base/user/cperciva/freebsd-update-build/">
+ freebsd-update-server</ulink> software by installing <filename
+ role="package">devel/subversion </filename>, and execute:</para>
+
+ <screen>&prompt.user; <userinput>svn co http://svn.freebsd.org/base/user/cperciva/freebsd-update-build freebsd-update-server</userinput></screen>
<para>Update <filename>scripts/build.conf</filename> appropriately.
It is sourced during all build operations.</para>
@@ -351,9 +352,9 @@ world|base|/usr/lib/libalias_ftp.a
<warning>
<para>During this second build cycle, the network time protocol
- daemon, &man.ntpd.8;, is turned off. Per &a.cperciva;, current
- Security Officer of &os;, "the <ulink
- url="&url.base;/cgi/cvsweb.cgi/projects/freebsd-update-server/">freebsd-update-server</ulink>
+ daemon, &man.ntpd.8;, is turned off. Per &a.cperciva;,
+ Security Officer Emeritus of &os;, "the <ulink
+ url="http://svnweb.freebsd.org/base/user/cperciva/freebsd-update-build/">freebsd-update-server</ulink>
build code needs to identify timestamps which are stored in files so
that they can be ignored when comparing builds to determine which
files need to be updated. This timestamp-finding works by doing two
@@ -776,7 +777,6 @@ the new builds.</screen>
}
</screen>
</listitem>
- <!-- this tip will speed up your build process, however it is not necessary -->
<listitem>
<para>Adding <option>-j <replaceable>NUMBER</replaceable></option>
flags to <maketarget>buildworld</maketarget> and
@@ -799,28 +799,12 @@ the new builds.</screen>
</listitem>
<listitem>
-<!-- Parse error. I don't understand what this paragraph suggests or
- recommends. Also, why do we need to block RSTs? I don't really
- like gratuitous blocking of RST, ICMP or other packets. Our
- kernel can rate-limit most of the "strange" packets alredy. -->
-
-<!-- there is a bug in earlier versions of the software that get the updates, and not blocking them will result in failure to update systems -->
-
- <para>Create a <ulink
- url="&url.books.handbook;/firewalls.html">firewall</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>
- on the &a.stable; in April 2009, there may be
- time-outs and failures when updating a system.</para>
- </listitem>
-
- <!-- this tip is not necessary, however if you wish to retain mirrors and redundancy, this tip will help you. -->
- <listitem>
<para>Create an appropriate <ulink
url="&url.books.handbook;/network-dns.html">DNS</ulink>
SRV record for the update server, and put others behind it with
variable weights. Using this facility will provide update
- mirrors.</para>
+ mirrors, however this tip is not necessary unless you wish to
+ provide a redundant service.</para>
<screen> _http._tcp.update.myserver.com. IN SRV 0 2 80 host1.myserver.com.
SRV 0 1 80 host2.myserver.com.