From owner-svn-doc-all@FreeBSD.ORG Mon Apr 6 05:30:42 2015 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE79D17D; Mon, 6 Apr 2015 05:30:42 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D84BB2D3; Mon, 6 Apr 2015 05:30:42 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id t365UgHU098506; Mon, 6 Apr 2015 05:30:42 GMT (envelope-from eadler@FreeBSD.org) Received: (from eadler@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id t365UgOi098505; Mon, 6 Apr 2015 05:30:42 GMT (envelope-from eadler@FreeBSD.org) Message-Id: <201504060530.t365UgOi098505@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: eadler set sender to eadler@FreeBSD.org using -f From: Eitan Adler Date: Mon, 6 Apr 2015 05:30:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r46484 - head/en_US.ISO8859-1/articles/releng X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 06 Apr 2015 05:30:43 -0000 Author: eadler Date: Mon Apr 6 05:30:41 2015 New Revision: 46484 URL: https://svnweb.freebsd.org/changeset/doc/46484 Log: releng: strip some old things There is a two year old warning that this document is partly outdated and that re@ is working on updating it. I don't see many substantive commits updating this doc, so just do a drive-by and remove the obviously wrong and outdated things. - sysinstall has been replaced (and so scripting it is meaningless) - cross building is possible - drop support for disk2 and on - remove empty sections, such as the one on cd-rom replication Modified: head/en_US.ISO8859-1/articles/releng/article.xml Modified: head/en_US.ISO8859-1/articles/releng/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/releng/article.xml Mon Apr 6 05:16:09 2015 (r46483) +++ head/en_US.ISO8859-1/articles/releng/article.xml Mon Apr 6 05:30:41 2015 (r46484) @@ -5,14 +5,6 @@
&os; Release Engineering - - - - - November 2001 - BSDCon Europe - - MurrayStokely I've been involved in the development of &os; based products @@ -746,64 +738,6 @@ command: /stage/cdrom&prompt.root; find . -type f | sed -e 's/^\.\///' | sort > filename.txt - - The specific requirements of each CD are outlined below. - - - Disc 1 - - The first disc is almost completely created by - make - release. The only changes - that should be made to the disc1 directory are the addition of - a tools directory, and as many popular - third party software packages as will fit on the disc. The - tools 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 &os; is to be included, then - &man.sysinstall.8; and &man.release.7; must be updated to - include installation instructions. The relevant code is contained - in src/release and src/usr.sbin/sysinstall. - Specifically, the file src/release/Makefile, and - dist.c, dist.h, - menus.c, install.c, and - Makefile will need to be updated under - src/usr.sbin/sysinstall. Optionally, you may choose - to update sysinstall.8. - - - - - Disc 2 - - The second disc is also largely created by make - release. This disc contains a live - filesystem that can be used from &man.sysinstall.8; to - troubleshoot a &os; installation. This disc should be - bootable and should also contain a compressed copy of the CVS - repository in the CVSROOT directory and - commercial software demos in the commerce - directory. - - - - Multi-volume support - - Sysinstall supports multiple - volume package installations. This requires that each disc - have an INDEX 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 - CD_VOLUME variable set in the - cdrom.inf file so that sysinstall can - tell which volume is which. When a user attempts to install a - package that is not on the current disc, sysinstall will - prompt the user to insert the appropriate one. - @@ -882,13 +816,6 @@ time, for example make it relative to GMT. - - CD-ROM Replication - - Coming soon: Tips for sending &os; ISOs to a replicator - and quality assurance measures to be taken. - - @@ -907,25 +834,8 @@ certainly encourage innovation in the form of advanced installation and administration tools, for example, but we cannot be expected to answer questions about it. - - - Scripting <command>sysinstall</command> - - The &os; system installation and configuration tool, - &man.sysinstall.8;, can be scripted to provide automated installs - for large sites. This functionality can be used in conjunction - with &intel; PXE - - - &url.books.handbook;/network-pxe-nfs.html - - - to bootstrap systems from the network. - - - Lessons Learned from &os; 4.4 @@ -968,33 +878,12 @@ using multiple processors in speeding up the make release process. If multiple disks are used for different hierarchies in the &man.chroot.2; - environment, then the CVS checkout of the ports and doc trees + environment, then the subversion checkout of the ports and doc trees can be happening simultaneously as the make world on another disk. Using a RAID solution (hardware or software) can significantly decrease the overall build time. - - - Cross-building releases - Building - IA-64 or Alpha release on x86 hardware? make - TARGET=ia64 release. - - - - - Regression Testing - We need better - automated correctness testing for &os;. - - - - Installation Tools - Our installation - program has long since outlived its intended life span. - Several projects are under development to provide a more - advanced installation mechanism. The libh project was one - such project that aimed to provide an intelligent new package - framework and GUI installation program. -