From owner-freebsd-doc@FreeBSD.ORG Thu Oct 15 19:10:02 2009 Return-Path: Delivered-To: freebsd-doc@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B2AA7106568B for ; Thu, 15 Oct 2009 19:10:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id 870738FC19 for ; Thu, 15 Oct 2009 19:10:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.3/8.14.3) with ESMTP id n9FJA2Ys094491 for ; Thu, 15 Oct 2009 19:10:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9FJA20G094490; Thu, 15 Oct 2009 19:10:02 GMT (envelope-from gnats) Date: Thu, 15 Oct 2009 19:10:02 GMT Message-Id: <200910151910.n9FJA20G094490@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Jason Cc: Subject: Re: docs/139095: new article on creating an internal FreeBSD Update Server X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Jason List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 19:10:02 -0000 The following reply was made to PR docs/139095; it has been noted by GNATS. From: Jason To: bug-followup@FreeBSD.org, jhelfman@e-e.com Cc: Subject: Re: docs/139095: new article on creating an internal FreeBSD Update Server Date: Thu, 15 Oct 2009 11:19:26 -0700 --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline Submitting a patch to my original PR. --VS++wcV0S1rZb1Fb Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=patch *** article.sgml.orig Thu Oct 15 10:48:39 2009 --- article.sgml Thu Oct 15 11:07:31 2009 *************** *** 1,5 **** --- 1,6 ---- + %articles.ent; FreeBSD Update Server"> ]> *************** *** 62,72 **** An ssh account on a remote machine to upload the distributed updates, &man.ssh.1;. ! A web server, with over half of the the space required for the build. For instance, my builds total 4G, and the webserver space needed to distribute updates is 2.6G. --- 63,73 ---- An ssh account on a remote machine to upload the distributed updates, &man.ssh.1;. ! An Apache web server, with over half of the the space required for the build. For instance, my builds total 4G, and the webserver space needed to distribute updates is 2.6G. *************** *** 78,88 **** Configuration: Installation & Setup ! Download the freebsd-update-server software. There is a tarball that can be downloaded, or you can csup projects-all, &man.csup.1;. Update scripts/build.conf appropriately for your environment. It is sourced during build and push operations. --- 79,89 ---- Configuration: Installation & Setup ! Download the freebsd-update-server software. There is a tarball that can be downloaded, or you can csup projects-all, &man.csup.1;. Update scripts/build.conf appropriately for your environment. It is sourced during build and push operations. *************** *** 173,184 **** cc -O2 -fno-strict-aliasing -pipe unstamp.c -o unstamp install findstamps ../bin install unstamp ../bin rm -f findstamps unstamp Generating RSA private key, 4096 bit long modulus ! ...............................................................................++ ! ..................++ e is 65537 (0x10001) Public key fingerprint: 27ef53e48dc869eea6c3136091cc6ab8589f967559824779e855d58a2294de9e --- 174,185 ---- cc -O2 -fno-strict-aliasing -pipe unstamp.c -o unstamp install findstamps ../bin install unstamp ../bin rm -f findstamps unstamp Generating RSA private key, 4096 bit long modulus ! ................................................................................++ ! ...................++ e is 65537 (0x10001) Public key fingerprint: 27ef53e48dc869eea6c3136091cc6ab8589f967559824779e855d58a2294de9e *************** *** 1188,1198 **** Updates for the current release of the &os; system you are updating, and what you want to upgrade to need to be built in order for your internal &os; Update Server to properly work. This is necessary for merging of files between the releases. ! You are not ready to test the updates you've uploaded. Update client's KeyPrint and ServerName in /etc/freebsd-update.conf, and perform updates as instructed in the &os; Update instructions in the handbook. Building a Patch --- 1189,1199 ---- Updates for the current release of the &os; system you are updating, and what you want to upgrade to need to be built in order for your internal &os; Update Server to properly work. This is necessary for merging of files between the releases. ! You are now ready to test the updates you've uploaded. Update client's KeyPrint and ServerName in /etc/freebsd-update.conf, and perform updates as instructed in the &os; Update instructions in the handbook. Building a Patch *************** *** 1983,1997 **** Add make -j NUMBER to scripts/build.subr to speed up your processing. I have found that adding flags to anything other than make buildworld and make obj can be unreliable. ! Create a firewall rule to block outgoing RST packets. Due to a bug noted in this posting by the the author of freebsd-update-server, you will have many many time-outs and fail to update a system without many pains along the way. I have found that the bug still exists in my adventures with this software. ! I haven't experimented with this just yet, however if you create an SRV record for your update server, and put others behind it with variable weights, that would be the equivalent of creating mirrors. Please read the source documentation, as well, as I have not experimented with all features of the software. --- 1984,2001 ---- Add make -j NUMBER to scripts/build.subr to speed up your processing. I have found that adding flags to anything other than make buildworld and make obj can be unreliable. ! Create a firewall rule to block outgoing RST packets. Due to a bug noted in this posting by the author of freebsd-update-server, you will have many time-outs and fail to update a system. ! If you create an appropriate DNS server SRV record for your update server, and put others behind it with variable weights, that would be the equivalent of creating mirrors. ! _http._tcp.update.myserver.com. IN SRV 0 2 80 host1.myserver.com. ! SRV 0 1 80 host2.myserver.com. ! SRV 0 0 80 host3.myserver.com. Please read the source documentation, as well, as I have not experimented with all features of the software. --VS++wcV0S1rZb1Fb--