From owner-p4-projects@FreeBSD.ORG Mon Jun 29 22:13:42 2009 Return-Path: Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id F0F891065670; Mon, 29 Jun 2009 22:13:41 +0000 (UTC) Delivered-To: perforce@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id AB421106564A for ; Mon, 29 Jun 2009 22:13:41 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (repoman.freebsd.org [IPv6:2001:4f8:fff6::29]) by mx1.freebsd.org (Postfix) with ESMTP id 97CD98FC0A for ; Mon, 29 Jun 2009 22:13:41 +0000 (UTC) (envelope-from rene@FreeBSD.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.14.3/8.14.3) with ESMTP id n5TMDfDb095054 for ; Mon, 29 Jun 2009 22:13:41 GMT (envelope-from rene@FreeBSD.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.14.3/8.14.3/Submit) id n5TMDfHt095052 for perforce@freebsd.org; Mon, 29 Jun 2009 22:13:41 GMT (envelope-from rene@FreeBSD.org) Date: Mon, 29 Jun 2009 22:13:41 GMT Message-Id: <200906292213.n5TMDfHt095052@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to rene@FreeBSD.org using -f From: Rene Ladan To: Perforce Change Reviews Cc: Subject: PERFORCE change 165451 for review X-BeenThere: p4-projects@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: p4 projects tree changes List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Jun 2009 22:13:43 -0000 http://perforce.freebsd.org/chv.cgi?CH=165451 Change 165451 by rene@rene_self on 2009/06/29 22:13:13 IFC Affected files ... .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#26 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/nanobsd/article.sgml#3 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/articles/releng/article.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml#4 integrate .. //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#35 integrate .. //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/bibliography/chapter.sgml#6 integrate .. //depot/projects/docproj_nl/www/en/donations/donors.sgml#16 integrate .. //depot/projects/docproj_nl/www/en/donations/wantlist.sgml#11 integrate .. //depot/projects/docproj_nl/www/en/favicon.ico#2 integrate .. //depot/projects/docproj_nl/www/en/gnome/images/pav.jpg#2 delete .. //depot/projects/docproj_nl/www/en/releng/index.sgml#26 integrate .. //depot/projects/docproj_nl/www/share/sgml/notices.xml#3 integrate .. //depot/projects/docproj_nl/www/share/sgml/press.xml#13 integrate Differences ... ==== //depot/projects/docproj_nl/en_US.ISO8859-1/articles/contributors/contrib.additional.sgml#26 (text+ko) ==== @@ -1,4 +1,4 @@ - + - Lessons Learned from FreeBSD 4.4 + Lessons Learned from &os; 4.4 The release engineering process for 4.4 formally began on August 1st, 2001. After that date all commits to the - RELENG_4 branch of FreeBSD had to be explicitly + RELENG_4 branch of &os; had to be explicitly approved by the &a.re;. The first release candidate for the x86 architecture was released on August 16, followed by 4 more release candidates leading up to the final @@ -1029,11 +1029,11 @@ little over a month. Our user community has made it very clear that the security - and stability of a FreeBSD release should not be sacrificed for - any self-imposed deadlines or target release dates. The FreeBSD + and stability of a &os; release should not be sacrificed for + any self-imposed deadlines or target release dates. The &os; Project has grown tremendously over its lifetime and the need for standardized release engineering procedures has never been more - apparent. This will become even more important as FreeBSD is + apparent. This will become even more important as &os; is ported to new platforms. @@ -1043,7 +1043,7 @@ It is imperative for our release engineering activities to scale with our growing userbase. Along these lines we are working - very hard to document the procedures involved in producing FreeBSD + very hard to document the procedures involved in producing &os; releases. @@ -1071,7 +1071,7 @@ Regression Testing - We need better - automated correctness testing for FreeBSD. + automated correctness testing for &os;. @@ -1092,14 +1092,14 @@ I would like to thank Jordan Hubbard for giving me the opportunity to take on some of the release engineering - responsibilities for FreeBSD 4.4 and also for all of his work - throughout the years making FreeBSD what it is today. Of course + responsibilities for &os; 4.4 and also for all of his work + throughout the years making &os; what it is today. Of course the release would not have been possible without all of the release-related work done by &a.asami;, &a.steve;, &a.bmah;, &a.nik;, - &a.obrien;, &a.kris;, &a.jhb; and the rest of the FreeBSD development + &a.obrien;, &a.kris;, &a.jhb; and the rest of the &os; development community. I would also like to thank &a.rgrimes;, &a.phk;, and others who worked on the release engineering tools in the very early days - of FreeBSD. This article was influenced by release engineering + of &os;. This article was influenced by release engineering documents from the CSRG[13], the NetBSD Project[10], and John Baldwin's proposed release engineering process notes[11]. @@ -1116,17 +1116,17 @@ [3] - [4] FreeBSD Ports Collection + [4] &os; Ports Collection - [5] FreeBSD Committers [5] &os; Committers - [6] FreeBSD Core Team + [6] &os; Core Team - [7] FreeBSD Handbook + [7] &os; Handbook @@ -1134,14 +1134,14 @@ - [9] FreeBSD PR Statistics + [9] &os; PR Statistics [10] NetBSD Developer Documentation: Release Engineering - [11] John Baldwin's FreeBSD Release Engineering Proposal + [11] John Baldwin's &os; Release Engineering Proposal ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml#4 (text+ko) ==== @@ -6,7 +6,7 @@ and Tom Rhodes For the FreeBSD Documentation Project - $FreeBSD: doc/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml,v 1.46 2008/12/22 21:51:29 trhodes Exp $ + $FreeBSD: doc/en_US.ISO8859-1/books/handbook/vinum/chapter.sgml,v 1.47 2009/06/29 18:51:34 manolis Exp $ --> @@ -46,7 +46,7 @@ implemented. One way some users safeguard themselves against such issues is through the use of multiple, and sometimes redundant, disks. In addition to supporting various cards and controllers - for hardware RAID systems, the base FreeBSD system includes the + for hardware RAID systems, the base &os; system includes the Vinum Volume Manager, a block device driver that implements virtual disk drives. Vinum is a so-called Volume Manager, a virtual disk @@ -60,7 +60,7 @@ Manager. - Starting with FreeBSD 5, Vinum has been rewritten in order + Starting with &os; 5, Vinum has been rewritten in order to fit into the GEOM architecture (), retaining the original ideas, terminology, and on-disk metadata. This rewrite is called gvinum @@ -72,8 +72,8 @@ kernel module has been changed from vinum.ko to geom_vinum.ko, and all device nodes - reside under /dev/gvinum instead - of /dev/vinum. As of FreeBSD 6, the old + reside under /dev/gvinum instead + of /dev/vinum. As of &os; 6, the old Vinum implementation is no longer available in the code base. @@ -272,7 +272,7 @@ 5. Of these, RAID-5 is the most interesting. As implemented in Vinum, it is a variant on a striped organization which dedicates one block of each stripe - to parity of the other blocks. As implemented by Vinum, a + to parity one of the other blocks. As implemented by Vinum, a RAID-5 plex is similar to a striped plex, except that it implements RAID-5 by including a parity block in each stripe. As required by @@ -394,7 +394,7 @@ Which Plex Organization? - The version of Vinum supplied with FreeBSD &rel.current; implements + The version of Vinum supplied with &os; &rel.current; implements two kinds of plex: @@ -761,7 +761,7 @@ drives may be up to 32 characters long. Vinum objects are assigned device nodes in the hierarchy - /dev/gvinum. The configuration shown above + /dev/gvinum. The configuration shown above would cause Vinum to create the following device nodes: @@ -770,8 +770,8 @@ implemenation. The control devices - /dev/vinum/control and - /dev/vinum/controld, which are used + /dev/vinum/control and + /dev/vinum/controld, which are used by &man.gvinum.8; and the Vinum daemon respectively. @@ -779,31 +779,31 @@ Device entries for each volume. These are the main devices used by Vinum. Thus the configuration above would include the devices - /dev/gvinum/myvol, - /dev/gvinum/mirror, - /dev/gvinum/striped, - /dev/gvinum/raid5 and - /dev/gvinum/raid10. + /dev/gvinum/myvol, + /dev/gvinum/mirror, + /dev/gvinum/striped, + /dev/gvinum/raid5 and + /dev/gvinum/raid10. This only applies to the historic Vinum implemenation. - A directory /dev/vinum/drive + A directory /dev/vinum/drive with entries for each drive. These entries are in fact symbolic links to the corresponding disk nodes. All volumes get direct entries under - /dev/gvinum/. + /dev/gvinum/. The directories - /dev/gvinum/plex, and - /dev/gvinum/sd, which contain + /dev/gvinum/plex, and + /dev/gvinum/sd, which contain device nodes for each plex and for each subdisk, respectively. @@ -823,7 +823,7 @@ sd length 100m drive drive4 After processing this file, &man.gvinum.8; creates the following - structure in /dev/gvinum: + structure in /dev/gvinum: drwxr-xr-x 2 root wheel 512 Apr 13 16:46 plex @@ -857,14 +857,14 @@ utilities, notably &man.newfs.8;, which previously tried to interpret the last letter of a Vinum volume name as a partition identifier. For example, a disk drive may have a - name like /dev/ad0a or - /dev/da2h. These names represent + name like /dev/ad0a or + /dev/da2h. These names represent the first partition (a) on the first (0) IDE disk (ad) and the eighth partition (h) on the third (2) SCSI disk (da) respectively. By contrast, a Vinum volume might be called - /dev/gvinum/concat, a name which has + /dev/gvinum/concat, a name which has no relationship with a partition name. Normally, &man.newfs.8; interprets the name of the disk and @@ -879,10 +879,10 @@ &prompt.root; newfs /dev/gvinum/concat On &os; versions prior to 5.0 &man.newfs.8; requires - an additional -v flag and the old device naming - scheme: + an additional flag and the old device naming + scheme: - &prompt.root; newfs -v /dev/vinum/concat + &prompt.root; newfs -v /dev/vinum/concat @@ -1055,7 +1055,7 @@ start command. The following paragraphs are outlining the steps - needed for FreeBSD. + needed for &os;. By placing the line: @@ -1081,7 +1081,7 @@ Making a Vinum-based Root Volume Accessible to the Bootstrap - Since the current FreeBSD bootstrap is only 7.5 KB of + Since the current &os; bootstrap is only 7.5 KB of code, and already has the burden of reading files (like /boot/loader) from the UFS filesystem, it is sheer impossible to also teach it about internal Vinum @@ -1235,10 +1235,10 @@ The values to note are 135680 for the offset (relative to partition - /dev/da0h). This translates to 265 + /dev/da0h). This translates to 265 512-byte disk blocks in bsdlabel's terms. Likewise, the size of this root volume is 245760 512-byte - blocks. /dev/da1h, containing the + blocks. /dev/da1h, containing the second replica of this root volume, has a symmetric setup. ==== //depot/projects/docproj_nl/en_US.ISO8859-1/books/porters-handbook/book.sgml#35 (text+ko) ==== @@ -1,7 +1,7 @@ + + 800098 + June 14, 2009 + 8.0-CURRENT after OpenSSL 0.9.8k import. + + + 800099 + June 22, 2009 + 8.0-CURRENT after NGROUPS update and moving + route virtualization into its own VImage module. + + + 800100 + June 24, 2009 + 8.0-CURRENT after SYSVIPC ABI change. + ==== //depot/projects/docproj_nl/nl_NL.ISO8859-1/books/handbook/bibliography/chapter.sgml#6 (text+ko) ==== @@ -1,7 +1,7 @@