From owner-freebsd-doc@FreeBSD.ORG Tue Oct 27 18:00:12 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 68EC1106566C for ; Tue, 27 Oct 2009 18:00:12 +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 564028FC0C for ; Tue, 27 Oct 2009 18:00:12 +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 n9RI0Abn089948 for ; Tue, 27 Oct 2009 18:00:10 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.3/8.14.3/Submit) id n9RI0AA6089947; Tue, 27 Oct 2009 18:00:10 GMT (envelope-from gnats) Date: Tue, 27 Oct 2009 18:00:10 GMT Message-Id: <200910271800.n9RI0AA6089947@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org From: Jason Helfman Cc: Subject: Re: docs/139681: [PATCH] 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 Helfman List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Oct 2009 18:00:12 -0000 The following reply was made to PR docs/139681; it has been noted by GNATS. From: Jason Helfman To: bug-followup@FreeBSD.org, jhelfman@e-e.com Cc: Subject: Re: docs/139681: [PATCH] new article on creating an internal FreeBSD Update Server Date: Tue, 27 Oct 2009 10:52:04 -0700 This is a multi-part message in MIME format. --------------010304060904030105050400 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Spelling errrors. --------------010304060904030105050400 Content-Type: text/plain; name="patch3.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="patch3.txt" *** article.sgml Tue Oct 27 10:41:08 2009 --- article.sgml.orig Tue Oct 27 10:43:28 2009 *************** *** 98,114 **** FTP ! This is where the function fetchiso() found in scripts/build.subr will contact the configured source for downloading the &os; iso. This can be configured to be an http address, as well. For my purposes, I have put the ISO's on the same server as my internal http server where I will be serving updates from, and have configured the software to look in that location. With this setup, I have altered the function to fetch the iso. By copying the source < filename>build.subr to scripts/_RELEASE_/_ARCHITECHTURE_/build.subr this file will be sourced instead of the released source for build.subr. BUILDHOSTNAME ! This is the name of the host you are building the software on, and coincidently, the name of the where the kernel will be built and displayed as a part of running: &prompt.user; uname -v --- 98,114 ---- FTP ! This is where the function fetchiso() found in scripts/build.subr will contact the configured source for downloading the &os; iso. This can be configured to be an http address, as well. For my purposes, I have put the ISO's on the same server as my internal http server where I will be serving updates from, and have configured the software to look in that location. With this setup, I have altered the function to fetch the iso. By copying the source < filename>build.subr to scripts/_RELEASE_/_ARCHITECTURE_/build.subr this file will be sourced instead of the released source for build.subr. BUILDHOSTNAME ! This is the name of the host you are building the software on, and coincidentally, the name of the where the kernel will be built and displayed as a part of running: &prompt.user; uname -v *************** *** 195,205 **** At this point, we are ready to stage a build. &prompt.user; cd ~/freebsd-update-server;sudo sh scripts/init.sh amd64 RELEASE-7.2 ! For referrence, here are the results of the init.sh run. At the end of the run, you will need to approve the build. FreeBSD/amd64 7.2-RELEASE initialization build complete. Please --- 195,205 ---- At this point, we are ready to stage a build. &prompt.user; cd ~/freebsd-update-server;sudo sh scripts/init.sh amd64 RELEASE-7.2 ! For reference, here are the results of the init.sh run. At the end of the run, you will need to approve the build. FreeBSD/amd64 7.2-RELEASE initialization build complete. Please *************** *** 267,277 **** At this point, we are ready to stage a diff build. You need to have run scripts/init.sh prior to running any diff. &prompt.user; cd ~/freebsd-update-server;sudo sh scripts/diff.sh amd64 RELEASE-7.1 7 ! For referrence, here are the results of the diff.sh run. Again, at the end of the run, you will need to approve the build. [jhelfman@server ]$ sudo sh -e scripts/approve.sh amd64 7.1-RELEASE --- 267,277 ---- At this point, we are ready to stage a diff build. You need to have run scripts/init.sh prior to running any diff. &prompt.user; cd ~/freebsd-update-server;sudo sh scripts/diff.sh amd64 RELEASE-7.1 7 ! For reference, here are the results of the diff.sh run. Again, at the end of the run, you will need to approve the build. [jhelfman@server ]$ sudo sh -e scripts/approve.sh amd64 7.1-RELEASE *************** *** 297,307 **** Tips ! If you build your own release using the native make release, freebsd-update-server code will work on your release, as well as patches. As an example I have tried this, building a release without ports or documentation, and removed the functionality pretaining to documentation in scripts/build.subr and placing it under the release directory structure. 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. --- 297,307 ---- Tips ! If you build your own release using the native make release, freebsd-update-server code will work on your release, as well as patches. As an example I have tried this, building a release without ports or documentation, and removed the functionality pertaining to documentation in scripts/build.subr and placing it under the release directory structure. 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. --------------010304060904030105050400--