From owner-svn-doc-all@FreeBSD.ORG Sun Sep 14 18:19:36 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 34793D8B; Sun, 14 Sep 2014 18:19:36 +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 1FC8C3EA; Sun, 14 Sep 2014 18:19:36 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8EIJao1049524; Sun, 14 Sep 2014 18:19:36 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8EIJZBm049523; Sun, 14 Sep 2014 18:19:35 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201409141819.s8EIJZBm049523@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Sun, 14 Sep 2014 18:19:35 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45606 - head/share/xml 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: Sun, 14 Sep 2014 18:19:36 -0000 Author: gjb Date: Sun Sep 14 18:19:35 2014 New Revision: 45606 URL: http://svnweb.freebsd.org/changeset/doc/45606 Log: Announce 10.1-BETA1 Approved by: re (implicit) Sponsored by: The FreeBSD Foundation Modified: head/share/xml/news.xml Modified: head/share/xml/news.xml ============================================================================== --- head/share/xml/news.xml Sat Sep 13 17:56:40 2014 (r45605) +++ head/share/xml/news.xml Sun Sep 14 18:19:35 2014 (r45606) @@ -32,6 +32,26 @@ 2014 + 9 + + + 1 + + + &os; 10.1-BETA1 Available + +

The first BETA build for the &os; 10.1 release cycle + is now available. ISO images for the amd64, armv6, i386, + ia64, powerpc, powerpc64 and sparc64 architectures are available + on most of our &os; + mirror sites.

+
+
+
+ + 8 From owner-svn-doc-all@FreeBSD.ORG Sun Sep 14 20:59:33 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 841DDB2F; Sun, 14 Sep 2014 20:59:33 +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 6ED97750; Sun, 14 Sep 2014 20:59:33 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8EKxXVx027723; Sun, 14 Sep 2014 20:59:33 GMT (envelope-from gavin@FreeBSD.org) Received: (from gavin@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8EKxXPF027722; Sun, 14 Sep 2014 20:59:33 GMT (envelope-from gavin@FreeBSD.org) Message-Id: <201409142059.s8EKxXPF027722@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gavin set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson Date: Sun, 14 Sep 2014 20:59:33 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45607 - head/en_US.ISO8859-1/htdocs/platforms 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: Sun, 14 Sep 2014 20:59:33 -0000 Author: gavin Date: Sun Sep 14 20:59:32 2014 New Revision: 45607 URL: http://svnweb.freebsd.org/changeset/doc/45607 Log: Update and clarify information about pc98's tier demotion. Submitted by: imp Modified: head/en_US.ISO8859-1/htdocs/platforms/pc98.xml Modified: head/en_US.ISO8859-1/htdocs/platforms/pc98.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/platforms/pc98.xml Sun Sep 14 18:19:35 2014 (r45606) +++ head/en_US.ISO8859-1/htdocs/platforms/pc98.xml Sun Sep 14 20:59:32 2014 (r45607) @@ -26,10 +26,14 @@

&os;/&arch.pc98; is a - Tier 2 architecture at the time of 9.0-RELEASE. Although - this was a Tier 1 for a long time since 5.0-RELEASE, it was + Tier 2 architecture at the time of 9.0-RELEASE.

+ +

Although + FreeBSD/pc98 was a Tier 1 for a long time since 5.0-RELEASE, it was downgraded due to FreeBSD no longer supporting installation from - floppy disks, and pc98 machines not supporting booting from CD/DVD.

+ floppy disks, and most pc98 machines cannot boot from CD/DVD. + Although later pc98 machines can boot from CDROM, FreeBSD's support + for that has not been integrated into bsdinstall and release tools.

&os;/&arch.pc98; Hardware Notes

From owner-svn-doc-all@FreeBSD.ORG Mon Sep 15 00:40:50 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 83FBCB43; Mon, 15 Sep 2014 00:40:50 +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 54BE0D5D; Mon, 15 Sep 2014 00:40:50 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8F0eoA8034324; Mon, 15 Sep 2014 00:40:50 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8F0entb034321; Mon, 15 Sep 2014 00:40:49 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201409150040.s8F0entb034321@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Mon, 15 Sep 2014 00:40:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45608 - in head: en_US.ISO8859-1/htdocs/releases/10.1R en_US.ISO8859-1/htdocs/releases/9.3R share/xml 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, 15 Sep 2014 00:40:50 -0000 Author: gjb Date: Mon Sep 15 00:40:49 2014 New Revision: 45608 URL: http://svnweb.freebsd.org/changeset/doc/45608 Log: - Enable the 10.1-BETA1 download link on where.html. - Remove the 9.3-{BETA,RC}* download link from the 9.3-RELEASE schedule page. Approved by: re (implicit) Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/htdocs/releases/10.1R/schedule.xml head/en_US.ISO8859-1/htdocs/releases/9.3R/schedule.xml head/share/xml/release.ent Modified: head/en_US.ISO8859-1/htdocs/releases/10.1R/schedule.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/10.1R/schedule.xml Sun Sep 14 20:59:32 2014 (r45607) +++ head/en_US.ISO8859-1/htdocs/releases/10.1R/schedule.xml Mon Sep 15 00:40:49 2014 (r45608) @@ -5,7 +5,7 @@ - + ]> Modified: head/en_US.ISO8859-1/htdocs/releases/9.3R/schedule.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/9.3R/schedule.xml Sun Sep 14 20:59:32 2014 (r45607) +++ head/en_US.ISO8859-1/htdocs/releases/9.3R/schedule.xml Mon Sep 15 00:40:49 2014 (r45608) @@ -5,7 +5,7 @@ - + ]> Modified: head/share/xml/release.ent ============================================================================== --- head/share/xml/release.ent Sun Sep 14 20:59:32 2014 (r45607) +++ head/share/xml/release.ent Mon Sep 15 00:40:49 2014 (r45608) @@ -38,8 +38,8 @@ - - + + From owner-svn-doc-all@FreeBSD.ORG Mon Sep 15 16:55:36 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ACBEBB8B; Mon, 15 Sep 2014 16:55:36 +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 97D9CECC; Mon, 15 Sep 2014 16:55:36 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8FGtaDI089476; Mon, 15 Sep 2014 16:55:36 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8FGtaq2089475; Mon, 15 Sep 2014 16:55:36 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201409151655.s8FGtaq2089475@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Mon, 15 Sep 2014 16:55:36 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45609 - head/en_US.ISO8859-1/books/handbook/zfs 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, 15 Sep 2014 16:55:36 -0000 Author: bcr Date: Mon Sep 15 16:55:36 2014 New Revision: 45609 URL: http://svnweb.freebsd.org/changeset/doc/45609 Log: Remove a dataset from the mount(8) output, as it does not exist at that point. Submitted by: Bjoern Heidotting Modified: head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Sep 15 00:40:49 2014 (r45608) +++ head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Sep 15 16:55:36 2014 (r45609) @@ -224,7 +224,6 @@ example/compressed 17547008 0 175 devfs on /dev (devfs, local) /dev/ad0s1d on /usr (ufs, local, soft-updates) example on /example (zfs, local) -example/data on /example/data (zfs, local) example/compressed on /example/compressed (zfs, local) After creation, ZFS datasets can be From owner-svn-doc-all@FreeBSD.ORG Mon Sep 15 17:09:56 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E586F7A; Mon, 15 Sep 2014 17:09:56 +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 D054C118; Mon, 15 Sep 2014 17:09:56 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8FH9u1k095027; Mon, 15 Sep 2014 17:09:56 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8FH9ugS095026; Mon, 15 Sep 2014 17:09:56 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201409151709.s8FH9ugS095026@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Mon, 15 Sep 2014 17:09:56 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45610 - head/de_DE.ISO8859-1/books/handbook/network-servers 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, 15 Sep 2014 17:09:57 -0000 Author: bcr Date: Mon Sep 15 17:09:56 2014 New Revision: 45610 URL: http://svnweb.freebsd.org/changeset/doc/45610 Log: Update to r40247: Mention that inetd must be enabled to use swat. Submitted by: Bjoern Heidotting Obtained from: The FreeBSD German Documentation Project Modified: head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml Mon Sep 15 16:55:36 2014 (r45609) +++ head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml Mon Sep 15 17:09:56 2014 (r45610) @@ -5,7 +5,7 @@ $FreeBSD$ $FreeBSDde: de-docproj/books/handbook/network-servers/chapter.xml,v 1.103 2011/12/24 15:51:18 bcr Exp $ - basiert auf: r38379 + basiert auf: r40247 --> Netzwerkserver @@ -5411,8 +5411,10 @@ DocumentRoot /www/someotherdomain.tld Das Samba Web Administration Tool (SWAT) wird als Daemon von inetd - aktiviert. Daher müssen Sie den Kommentar vor der - folgenden Zeile in /etc/inetd.conf + aktiviert. Daher müssen Sie + inetd, wie in beschrieben, aktivieren und die + folgende Zeile in /etc/inetd.conf entfernen, bevor Sie swat zur Konfiguration von Samba verwenden können: From owner-svn-doc-all@FreeBSD.ORG Mon Sep 15 17:27:58 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A303181F; Mon, 15 Sep 2014 17:27:58 +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 8D4C7343; Mon, 15 Sep 2014 17:27:58 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8FHRwnq004311; Mon, 15 Sep 2014 17:27:58 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8FHRwqx004310; Mon, 15 Sep 2014 17:27:58 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201409151727.s8FHRwqx004310@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Mon, 15 Sep 2014 17:27:58 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45611 - head/de_DE.ISO8859-1/books/handbook 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, 15 Sep 2014 17:27:58 -0000 Author: bcr Date: Mon Sep 15 17:27:58 2014 New Revision: 45611 URL: http://svnweb.freebsd.org/changeset/doc/45611 Log: Update to r43184: - Redo author entry - Bump copyright year - Remove trademark attributions terms that are no longer used in the handbook - Updates to sync this page with the latest in the english tree Submitted by: Bjoern Heidotting Minor changes by: bcr Obtained from: The FreeBSD German Documentation Project Modified: head/de_DE.ISO8859-1/books/handbook/book.xml Modified: head/de_DE.ISO8859-1/books/handbook/book.xml ============================================================================== --- head/de_DE.ISO8859-1/books/handbook/book.xml Mon Sep 15 17:09:56 2014 (r45610) +++ head/de_DE.ISO8859-1/books/handbook/book.xml Mon Sep 15 17:27:58 2014 (r45611) @@ -1,26 +1,30 @@ %chapters; - %txtfiles; -]> - - Das &os;-Handbuch - - - - The FreeBSD German Documentation Project - + %chapters; + %txtfiles; +]> + + + + + Das &os;-Handbuch + + + The FreeBSD German Documentation Project + - Februar 1999 + $FreeBSD$ $FreeBSD$ @@ -43,6 +47,8 @@ 2010 2011 2012 + 2013 + 2014 The FreeBSD German Documentation Project @@ -66,17 +72,13 @@ &tm-attrib.intuit; &tm-attrib.linux; &tm-attrib.lsilogic; - &tm-attrib.m-systems; - &tm-attrib.macromedia; &tm-attrib.microsoft; &tm-attrib.netscape; - &tm-attrib.nexthop; &tm-attrib.opengroup; &tm-attrib.oracle; &tm-attrib.powerquest; &tm-attrib.realnetworks; &tm-attrib.redhat; - &tm-attrib.sap; &tm-attrib.sun; &tm-attrib.symantec; &tm-attrib.themathworks; @@ -92,30 +94,33 @@ Willkommen bei &os;! Dieses Handbuch beschreibt die - Installation und den täglichen Umgang mit - &os; &rel2.current;-RELEASE und - &os; &rel.current;-RELEASE. - Das Handbuch ist jederzeit unter Bearbeitung - und das Ergebnis der Arbeit vieler Einzelpersonen. Dies kann - dazu führen, dass bestimmte Bereiche nicht mehr aktuell - sind und auf den neuesten Stand gebracht werden müssen. - Bei Unklarheiten empfiehlt es sich daher stets, die - - englische Originalversion des Handbuchs zu lesen. - - Wenn Sie bei der Übersetzung des Handbuchs mithelfen - möchten, senden Sie bitte - eine E-Mail an die Mailingliste &a.de.translators;. - - Die aktuelle Version des Handbuchs ist immer auf dem - &os;-Webserver - verfügbar und kann in verschiedenen Formaten und in - komprimierter Form vom &os;-FTP-Server - oder einem der vielen Spiegel - herunter geladen werden (ältere Versionen finden Sie hingegen - unter http://docs.FreeBSD.org/doc/). - Vielleicht möchten Sie das Handbuch aber auch - durchsuchen. + Installation und den täglichen Umgang mit &os; + &rel2.current;-RELEASE und &os; + &rel.current;-RELEASE. Das Handbuch ist + jederzeit unter Bearbeitung und das + Ergebnis der Arbeit vieler Einzelpersonen. Dies kann dazu + führen, dass bestimmte Bereiche nicht mehr aktuell sind und + auf den neuesten Stand gebracht werden müssen. Bei + Unklarheiten empfiehlt es sich daher stets, die + englische Originalversion des Handbuchs zu + lesen. + + Wenn Sie bei der Ãœbersetzung des Handbuchs mithelfen + möchten, senden Sie bitte eine E-Mail an die Mailingliste + &a.de.translators;. + + Die aktuelle Version des Handbuchs ist immer auf dem &os;-Webserver + verfügbar und kann in verschiedenen Formaten und in + komprimierter Form vom &os; + FTP-Server oder einem der vielen Spiegel herunter geladen werden + (ältere Versionen finden Sie hingegen unter http://docs.FreeBSD.org/doc/). + Vielleicht möchten Sie das Handbuch aber auch durchsuchen. @@ -126,12 +131,12 @@ Dieser Teil des &os;-Handbuchs richtet sich an Benutzer - und Administratoren für die &os; neu ist. Diese + und Administratoren für die &os; neu ist. Diese Kapitel - geben Ihnen eine Einführung in &os;, + geben Ihnen eine Einführung in &os;, @@ -139,27 +144,27 @@ - erklären Ihnen die Grundlagen + erklären Ihnen die Grundlagen von &unix; Systemen, - zeigen Ihnen, wie Sie die Fülle der erhältlichen + zeigen Ihnen, wie Sie die Fülle der erhältlichen Anwendungen Dritter installieren und - führen Sie in X, der Benutzeroberfläche + führen Sie in X, der Benutzeroberfläche von &unix; Systemen ein. Es wird gezeigt, wie Sie den Desktop konfigurieren, um effektiver arbeiten - zu können. + zu können. - Wir haben uns bemüht, Referenzen auf weiter vorne liegende - Textteile auf ein Minimum zu beschränken, so dass Sie - diesen Teil des Handbuchs ohne viel Blättern durcharbeiten - können. + Wir haben uns bemüht, Referenzen auf weiter vorne liegende + Textteile auf ein Minimum zu beschränken, so dass Sie + diesen Teil des Handbuchs ohne viel Blättern durcharbeiten + können. &chap.introduction; @@ -174,43 +179,43 @@ Oft benutzte Funktionen - Nach den Grundlagen beschäftigt sich das + Nach den Grundlagen beschäftigt sich das &os;-Handbuch mit oft benutzten Funktionen von &os;. Die Kapitel behandeln die nachstehenden Themen: - Zeigen Ihnen beliebte und nützliche - Werkzeuge wie Browser, Büroanwendungen und + Zeigen Ihnen beliebte und nützliche + Werkzeuge wie Browser, Büroanwendungen und Programme zum Anzeigen von Dokumenten. - Zeigen Ihnen Multimedia-Werkzeuge für + Zeigen Ihnen Multimedia-Werkzeuge für &os;. - Erklären den Bau eines angepassten &os;-Kernels, + Erklären den Bau eines angepassten &os;-Kernels, der die Systemfunktionen erweitert. - - Beschreiben ausführlich das Drucksystem, - sowohl für direkt angeschlossene Drucker als - auch für Netzwerkdrucker. - + + Beschreiben ausführlich das Drucksystem, + sowohl für direkt angeschlossene Drucker als + auch für Netzwerkdrucker. + - - Erläutern, wie Sie Linux-Anwendungen auf einem + + Erläutern, wie Sie Linux-Anwendungen auf einem &os;-System laufen lassen. - + Damit Sie einige Kapitel verstehen, sollten Sie vorher - andere Kapitel gelesen haben. Die Übersicht zu jedem - Kapitel zählt die Voraussetzungen für das + andere Kapitel gelesen haben. Die Ãœbersicht zu jedem + Kapitel zählt die Voraussetzungen für das erolgreiche Durcharbeiten des Kapitels auf. @@ -226,16 +231,16 @@ Die restlichen Kapitel behandeln alle Aspekte der &os; - Systemadministration. Am Anfang jedes Kapitels finden Sie eine - Zusammenfassung, die beschreibt, was Sie nach dem Durcharbeiten des - Kapitels gelernt haben. Weiterhin werden die Voraussetzungen - beschrieben, die für das Durcharbeiten des Kapitels - erforderlich sind. - - Diese Kapitel sollten Sie lesen, wenn Sie die Informationen - darin benötigen. Sie brauchen Sie nicht in einer bestimmten - Reihenfolge zu lesen, noch müssen Sie die Kapitel lesen, bevor - Sie anfangen, &os; zu benutzen. + Systemadministration. Am Anfang jedes Kapitels finden Sie + eine Zusammenfassung, die beschreibt, was Sie nach dem + Durcharbeiten des Kapitels gelernt haben. Weiterhin werden + die Voraussetzungen beschrieben, die für das Durcharbeiten des + Kapitels erforderlich sind. + + Diese Kapitel sollten Sie lesen, wenn Sie die + Informationen darin benötigen. Sie brauchen Sie nicht in + einer bestimmten Reihenfolge zu lesen, noch müssen Sie die + Kapitel lesen, bevor Sie anfangen, &os; zu benutzen. &chap.config; @@ -260,40 +265,40 @@ &os; ist eins der meist benutzten Betriebssysteme - für leistungsfähige Netzwerkserver. Die + für leistungsfähige Netzwerkserver. Die Kapitel in diesem Teil behandeln die nachstehenden Themen: - - Serielle Datenübertragung - - - - PPP und PPP over Ethernet - - - - Electronic-Mail - + + Serielle Datenübertragung + - + + PPP und PPP over Ethernet + + + + Electronic-Mail + + + Den Betrieb von Netzwerkdiensten - + - + Firewalls - + - - Weiterführende Netzwerkthemen - + + Weiterführende Netzwerkthemen + - Diese Kapitel sollten Sie lesen, wenn Sie die Informationen - darin benötigen. Sie brauchen Sie nicht in einer bestimmten - Reihenfolge zu lesen, noch müssen Sie die Kapitel lesen, bevor - Sie anfangen, &os; zu benutzen. + Diese Kapitel sollten Sie lesen, wenn Sie die + Informationen darin benötigen. Sie brauchen Sie nicht + in einer bestimmten Reihenfolge zu lesen, noch müssen Sie die + Kapitel lesen, bevor Sie anfangen, &os; zu benutzen. &chap.serialcomms; @@ -316,3 +321,4 @@ &chap.index; &chap.colophon; + From owner-svn-doc-all@FreeBSD.ORG Mon Sep 15 23:40:30 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6B5CDF47; Mon, 15 Sep 2014 23:40:30 +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 5704814B; Mon, 15 Sep 2014 23:40:30 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8FNeUtE080371; Mon, 15 Sep 2014 23:40:30 GMT (envelope-from gavin@FreeBSD.org) Received: (from gavin@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8FNeUml080370; Mon, 15 Sep 2014 23:40:30 GMT (envelope-from gavin@FreeBSD.org) Message-Id: <201409152340.s8FNeUml080370@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gavin set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson Date: Mon, 15 Sep 2014 23:40:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45612 - head/en_US.ISO8859-1/htdocs/platforms 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, 15 Sep 2014 23:40:30 -0000 Author: gavin Date: Mon Sep 15 23:40:29 2014 New Revision: 45612 URL: http://svnweb.freebsd.org/changeset/doc/45612 Log: Add BERI/CHERI to list of CPUs supported by FreeBSD/MIPS. Submitted by: rwatson Modified: head/en_US.ISO8859-1/htdocs/platforms/mips.xml Modified: head/en_US.ISO8859-1/htdocs/platforms/mips.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/platforms/mips.xml Mon Sep 15 17:27:58 2014 (r45611) +++ head/en_US.ISO8859-1/htdocs/platforms/mips.xml Mon Sep 15 23:40:29 2014 (r45612) @@ -63,6 +63,7 @@
  • Atheros AR71xx, AR724x, AR91xx, AR933x, AR934x
  • Cavium OCTEON
  • NetLogic XLR/XLS CPU family
  • +
  • SRI/Cambridge's BERI and CHERI open-source FPGA soft-cores
  • Note that not all peripherals are supported on all CPUs.

    From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 09:05:41 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ECDE12E3; Tue, 16 Sep 2014 09:05:41 +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 D8D5FBCC; Tue, 16 Sep 2014 09:05:41 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8G95fjO043541; Tue, 16 Sep 2014 09:05:41 GMT (envelope-from ryusuke@FreeBSD.org) Received: (from ryusuke@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8G95fNo043540; Tue, 16 Sep 2014 09:05:41 GMT (envelope-from ryusuke@FreeBSD.org) Message-Id: <201409160905.s8G95fNo043540@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: ryusuke set sender to ryusuke@FreeBSD.org using -f From: Ryusuke SUZUKI Date: Tue, 16 Sep 2014 09:05:41 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45613 - head/ja_JP.eucJP/share/xml 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: Tue, 16 Sep 2014 09:05:42 -0000 Author: ryusuke Date: Tue Sep 16 09:05:41 2014 New Revision: 45613 URL: http://svnweb.freebsd.org/changeset/doc/45613 Log: - Merge the following from the English version: r45535 -> r45606 head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml Modified: head/ja_JP.eucJP/share/xml/news.xml ============================================================================== --- head/ja_JP.eucJP/share/xml/news.xml Mon Sep 15 23:40:29 2014 (r45612) +++ head/ja_JP.eucJP/share/xml/news.xml Tue Sep 16 09:05:41 2014 (r45613) @@ -23,7 +23,7 @@ would like to work on. *** $FreeBSD$ - Original revision: r45535 + Original revision: r45606 --> @@ -34,6 +34,25 @@ 2014 + 9 + + + 1 + + + &os; 10.1-BETA1 ¸ø³« + +

    &os; 10.1 ¥ê¥ê¡¼¥¹¥µ¥¤¥¯¥ë¤«¤éºÇ½é¤Î¥Ù¡¼¥¿ÈǤ¬¸ø³«¤µ¤ì¤Þ¤·¤¿ (¥¢¥Ê¥¦¥ó¥¹)¡£ + &os; + ¥ß¥é¡¼¥µ¥¤¥È ¤«¤é amd64, i386, ia64, powerpc, powerpc64 + ¤ª¤è¤Ó sparc64 ¥¢¡¼¥­¥Æ¥¯¥Á¥ã¤Î ISO ¥¤¥á¡¼¥¸¤òÆþ¼ê¤Ç¤­¤Þ¤¹¡£

    +
    +
    +
    + + 8 From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 10:03:59 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D59BEB01; Tue, 16 Sep 2014 10:03:59 +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 BFF29182; Tue, 16 Sep 2014 10:03:59 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GA3xax071780; Tue, 16 Sep 2014 10:03:59 GMT (envelope-from delphij@FreeBSD.org) Received: (from delphij@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GA3xFV071776; Tue, 16 Sep 2014 10:03:59 GMT (envelope-from delphij@FreeBSD.org) Message-Id: <201409161003.s8GA3xFV071776@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: delphij set sender to delphij@FreeBSD.org using -f From: Xin LI Date: Tue, 16 Sep 2014 10:03:59 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45614 - in head/share: security/advisories security/patches/SA-14:19 xml 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: Tue, 16 Sep 2014 10:03:59 -0000 Author: delphij Date: Tue Sep 16 10:03:58 2014 New Revision: 45614 URL: http://svnweb.freebsd.org/changeset/doc/45614 Log: Add SA-14:19.tcp. Added: head/share/security/advisories/FreeBSD-SA-14:19.tcp.asc (contents, props changed) head/share/security/patches/SA-14:19/ head/share/security/patches/SA-14:19/tcp.patch (contents, props changed) head/share/security/patches/SA-14:19/tcp.patch.asc (contents, props changed) Modified: head/share/xml/advisories.xml Added: head/share/security/advisories/FreeBSD-SA-14:19.tcp.asc ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/advisories/FreeBSD-SA-14:19.tcp.asc Tue Sep 16 10:03:58 2014 (r45614) @@ -0,0 +1,147 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +============================================================================= +FreeBSD-SA-14:19.tcp Security Advisory + The FreeBSD Project + +Topic: Denial of Service in TCP packet processing + +Category: core +Module: inet +Announced: 2014-09-16 +Credits: Jonathan Looney (Juniper SIRT) +Affects: All supported versions of FreeBSD. +Corrected: 2014-09-16 09:48:35UTC (stable/10, 10.1-PRERELEASE) + 2014-09-16 09:48:35 UTC (stable/10, 10.1-BETA1-p1) + 2014-09-16 09:50:19 UTC (releng/10.0, 10.0-RELEASE-p9) + 2014-09-16 09:49:11 UTC (stable/9, 9.3-STABLE) + 2014-09-16 09:50:19 UTC (releng/9.3, 9.3-RELEASE-p2) + 2014-09-16 09:50:19 UTC (releng/9.2, 9.2-RELEASE-p12) + 2014-09-16 09:50:19 UTC (releng/9.1, 9.1-RELEASE-p19) + 2014-09-16 09:49:11 UTC (stable/8, 8.4-STABLE) + 2014-09-16 09:50:19 UTC (releng/8.4, 8.4-RELEASE-p16) +CVE Name: CVE-2004-0230 + +For general information regarding FreeBSD Security Advisories, +including descriptions of the fields above, security branches, and the +following sections, please visit . + +I. Background + +The Transmission Control Protocol (TCP) of the TCP/IP protocol suite +provides a connection-oriented, reliable, sequence-preserving data +stream service. New TCP connections are initiated using special SYN +flag in a datagram. Sequencing of data is controlled by 32-bit sequence +numbers, that start with a random value and are increased using modulo +2**32 arithmetic. TCP endpoints maintain a window of expected, and +thus allowed, sequence numbers for a connection. + +II. Problem Description + +When a segment with the SYN flag for an already existing connection arrives, +the TCP stack tears down the connection, bypassing a check that the +sequence number in the segment is in the expected window. + +III. Impact + +An attacker who has the ability to spoof IP traffic can tear down a +TCP connection by sending only 2 packets, if they know both TCP port +numbers. In case one of the two port numbers is unknown, a successful +attack requires less than 2**17 packets spoofed, which can be +generated within less than a second on a decent connection to the +Internet. + +IV. Workaround + +It is possible to defend against these attacks with stateful traffic +inspection using a firewall. This can be done by enabling pf(4) on +the system and creating states for every connection. Even a default +ruleset to allow all traffic would be sufficient to mitigate this +issue. + +V. Solution + +Perform one of the following: + +1) Upgrade your vulnerable system to a supported FreeBSD stable or +release / security branch (releng) dated after the correction date. + +2) To update your vulnerable system via a source code patch: + +The following patches have been verified to apply to the applicable +FreeBSD release branches. + +a) Download the relevant patch from the location below, and verify the +detached PGP signature using your PGP utility. + +# fetch http://security.FreeBSD.org/patches/SA-14:19/tcp.patch +# fetch http://security.FreeBSD.org/patches/SA-14:19/tcp.patch.asc +# gpg --verify tcp.patch.asc + +b) Apply the patch. Execute the following commands as root: + +# cd /usr/src +# patch < /path/to/patch + +c) Recompile your kernel as described in + and reboot the +system. + +3) To update your vulnerable system via a binary patch: + +Systems running a RELEASE version of FreeBSD on the i386 or amd64 +platforms can be updated via the freebsd-update(8) utility: + +# freebsd-update fetch +# freebsd-update install + +VI. Correction details + +The following list contains the correction revision numbers for each +affected branch. + +Branch/path Revision +- ------------------------------------------------------------------------- +stable/8/ r271668 +releng/8.4/ r271669 +stable/9/ r271668 +releng/9.1/ r271669 +releng/9.2/ r271669 +releng/9.3/ r271669 +stable/10/ r271667 +releng/10.0/ r271669 +- ------------------------------------------------------------------------- + +To see which files were modified by a particular revision, run the +following command, replacing NNNNNN with the revision number, on a +machine with Subversion installed: + +# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base + +Or visit the following URL, replacing NNNNNN with the revision number: + + + +VII. References + + + +The latest revision of this advisory is available at + +-----BEGIN PGP SIGNATURE----- + +iQIcBAEBCgAGBQJUGAnEAAoJEO1n7NZdz2rnHEkP/0fVx7U6l/YKVWToejpCxMLa +TS9ng0kN5GEkyYPTHbK3Pb5T2b4zhpDlhRVTDtwkP+00VXAGIAC6GiQl2QBAApgv +68cla+TU+gh2I03XxIl+eWHu4EWaYa0v2vDqL0n/XNLvcZVD3R0CC+6HHUbKm46t +dQg4olCdXdHkZleclvuYGjd+W8JfC17Xe3xshNKq7BV05XWqXrKoqxfxot8Cnxyx +n4MePoiNYn13iO5OpEWf2J6BS1JJ1M/L0CAAKGcNitD8dYMdKNEfn6tpPXHNIWGH +vUI0sD2rPRs3OWbK6Y3xmakCPK8MXjSyFNvJ2NkuU6dYdKBNHYswh46F9XP0cSDc +K5wB36R/mx5ky05HBCpAjiGh2X67Y6QtQiBq5ESltodAp1Sl966fgLnNKyIgeHr5 +51QNCXDdc7S7pE9daA/uiIEZVKH8eKYGHP53zN/tiTDVWy7yTEBIW4lhJVkHIAAt +VBvLB0efr47z6IZ92GshGKZawaPAOeuBrEtYDOdNNJeh+WhSPoE5MKfS6NiH/lRg +DorewB9KbChCUhxMCH2Pj7AxTVoe3fjWtZYRo02OHMitTTJbExsyT33vTH1Sb2LT +6lXBFFOvo5Uw8JJyykd+GXUcwe13hcroS+eqz/GE+9yReMrwd82qbiDM4VlTdVMq +trAqOw2zRyBa7R6D2+4T +=qjIZ +-----END PGP SIGNATURE----- Added: head/share/security/patches/SA-14:19/tcp.patch ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/patches/SA-14:19/tcp.patch Tue Sep 16 10:03:58 2014 (r45614) @@ -0,0 +1,17 @@ +Index: sys/netinet/tcp_input.c +=================================================================== +--- sys/netinet/tcp_input.c (revision 271383) ++++ sys/netinet/tcp_input.c (working copy) +@@ -2092,11 +2092,7 @@ tcp_do_segment(struct mbuf *m, struct tcphdr *th, + + todrop = tp->rcv_nxt - th->th_seq; + if (todrop > 0) { +- /* +- * If this is a duplicate SYN for our current connection, +- * advance over it and pretend and it's not a SYN. +- */ +- if (thflags & TH_SYN && th->th_seq == tp->irs) { ++ if (thflags & TH_SYN) { + thflags &= ~TH_SYN; + th->th_seq++; + if (th->th_urp > 1) Added: head/share/security/patches/SA-14:19/tcp.patch.asc ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/security/patches/SA-14:19/tcp.patch.asc Tue Sep 16 10:03:58 2014 (r45614) @@ -0,0 +1,16 @@ +-----BEGIN PGP SIGNATURE----- + +iQIcBAABCgAGBQJUGAnQAAoJEO1n7NZdz2rnMucQALHIm020vq4E+9LT+OhvMo2o +cAAD5W+IK4yj39jKjqyMK3Elm6iKgPYhyAZrOGxHtoDnjWXfQrKWmZFsmTXNjbHy +ramFwe6qglsZQ0mkKT36OJgVCK/vw1wUPO+CyyGD87n6XJ6uwmc7KOzWcrECuYun +rXR6IjOjyevSWsX0N+e+qN2kmry1RYfqnsg7yaNKbjO4EDr3UoCbT2Hp+sTS60gF +YnbKmCLhew0lcGXcbNmBitsj1jn/JwXnQsloKasUhkCBVBVuYs3i602FSb+szDe5 +C/KcUqETCMJleiqhf5YufkKcHtM5aQf/J9HIILmbzF8cEHRy0RPlxZrcHJIfHplu +TJWehGl6jBWpxgWS0FEPoR0fGHaGIZy72rdclLcV4uMuyvOwdJMFXEsU22FCa3Mt +w85RfsxHxxsDte8aHkyzMuN8OQVbG2RvfmfrMOCfCJvSc1QMUshkhCQgn5wj6y9z +qc4cfK8ppt15F2x1AC2uscaNghdOD6yixE8JqOjpXArXIGjkkWLB9t6sgoUiOMbS +jyaseaFisIdto0j7UJ9OnuUbDLxcQhgIk1JXNlu6Vwb4PitRKiL3Ix5CiYYB643k +iPJGcHx8JblX/z+TE5X7WA/T4TlvphthZ6QKgVmW8TMcgqrBSazEo0EN7mHeCKLo +VziBvb2zKWYjEa29uE5u +=ZTBf +-----END PGP SIGNATURE----- Modified: head/share/xml/advisories.xml ============================================================================== --- head/share/xml/advisories.xml Tue Sep 16 09:05:41 2014 (r45613) +++ head/share/xml/advisories.xml Tue Sep 16 10:03:58 2014 (r45614) @@ -11,6 +11,14 @@ 9 + 16 + + + FreeBSD-SA-14:19.tcp + + + + 9 From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 11:58:51 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EE996FCA; Tue, 16 Sep 2014 11:58:50 +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 BF110FE; Tue, 16 Sep 2014 11:58:50 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GBwoc7024493; Tue, 16 Sep 2014 11:58:50 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GBwoHU024492; Tue, 16 Sep 2014 11:58:50 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409161158.s8GBwoHU024492@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Tue, 16 Sep 2014 11:58:50 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45615 - head/en_US.ISO8859-1/books/porters-handbook/security 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: Tue, 16 Sep 2014 11:58:51 -0000 Author: mat (ports committer) Date: Tue Sep 16 11:58:50 2014 New Revision: 45615 URL: http://svnweb.freebsd.org/changeset/doc/45615 Log: igor -Ry and some other rewording and fixes. Differential Revision: https://reviews.freebsd.org/D651 Reviewed by: wblock Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/security/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/security/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/security/chapter.xml Tue Sep 16 10:03:58 2014 (r45614) +++ head/en_US.ISO8859-1/books/porters-handbook/security/chapter.xml Tue Sep 16 11:58:50 2014 (r45615) @@ -40,8 +40,8 @@ even notice the harm caused. Third, exposing a vulnerable system often assists attackers to break into other systems that could not be compromised otherwise. Therefore closing a - vulnerability alone is not enough: the audience should be - notified of it in most clear and comprehensive manner, which + vulnerability alone is not enough: notify the audience + of it in most clear and comprehensive manner, which will allow to evaluate the danger and take appropriate actions. @@ -53,21 +53,21 @@ vulnerability may initially appear in the original distribution or in the port files. In the former case, the original software developer is likely to release a patch or a new version - instantly, and you will only need to update the port promptly + instantly. Update the port promptly with respect to the author's fix. If the fix is delayed for - some reason, you should either + some reason, either mark the port as - FORBIDDEN or introduce a patch file of - your own to the port. In the case of a vulnerable port, just - fix the port as soon as possible. In either case, + FORBIDDEN or introduce a patch file + to the port. In the case of a vulnerable port, just + fix the port as soon as possible. In either case, follow the standard procedure for - submitting your change should be followed unless you have + submitting changes unless having rights to commit it directly to the ports tree. Being a ports committer is not enough to commit to an arbitrary port. Remember that ports usually have maintainers, - whom you should respect. + must be respected. Please make sure that the port's revision is bumped as soon @@ -75,11 +75,11 @@ upgrade installed packages on a regular basis will see they need to run an update. Besides, a new package will be built and distributed over FTP and WWW mirrors, replacing the vulnerable - one. PORTREVISION should be bumped unless + one. Bump PORTREVISION unless PORTVERSION has changed in the course of - correcting the vulnerability. That is you should bump - PORTREVISION if you have added a patch file - to the port, but you should not if you have updated the port to + correcting the vulnerability. That is, bump + PORTREVISION if adding a patch file + to the port, but do not bump it if updating the port to the latest software version and thus already touched PORTVERSION. Please refer to the corresponding @@ -95,9 +95,9 @@ A very important and urgent step to take as early after a security vulnerability is discovered as possible is to notify the community of port users about the jeopardy. Such - notification serves two purposes. First, should the danger be + notification serves two purposes. First, if the danger is really severe it will be wise to apply an instant workaround. - E.g., stop the affected network service or even deinstall the + For example, stop the affected network service or even deinstall the port completely until the vulnerability is closed. Second, a lot of users tend to upgrade installed packages only occasionally. They will know from the notification that they @@ -114,6 +114,7 @@ also monitor it for issues requiring their intervention. + If you have committer rights you can update the VuXML database by yourself. So you will both help the Security Officer Team and deliver the crucial information to the @@ -129,10 +130,10 @@ inside the port security/vuxml. Therefore the file's full pathname will be PORTSDIR/security/vuxml/vuln.xml. Each - time you discover a security vulnerability in a port, please - add an entry for it to that file. Until you are familiar with - VuXML, the best thing you can do is to find an existing entry - fitting your case, then copy it and use it as a + time a security vulnerability is discovered in a port, please + add an entry for it to that file. Until familiar with + VuXML, the best thing to do is to find an existing entry + fitting the case at hand, then copy it and use it as a template. @@ -141,14 +142,14 @@ The full-blown XML format is complex, and far beyond the scope of this book. However, to gain basic - insight on the structure of a VuXML entry you need only the - notion of tags. XML tag names are enclosed in angle brackets. + insight on the structure of a VuXML entry only the notion of + tags is needed. XML tag names are enclosed in angle brackets. Each opening <tag> must have a matching closing </tag>. Tags may be nested. If nesting, the inner tags must be closed before the outer ones. There is a hierarchy of - tags, i.e., more complex rules of nesting them. This is + tags, that is, more complex rules of nesting them. This is similar to HTML. The major difference is that XML is - eXtensible, i.e., based on defining + eXtensible, that is, based on defining custom tags. Due to its intrinsic structure XML puts otherwise amorphous data into shape. VuXML is particularly tailored to mark up descriptions of security @@ -206,18 +207,18 @@ </vuln> The tag names are supposed to be self-explanatory so we - shall take a closer look only at fields you will need to fill - in by yourself: + shall take a closer look only at fields which needs to be fill + in: This is the top-level tag of a VuXML entry. It has a mandatory attribute, vid, specifying a universally unique identifier (UUID) for this entry (in - quotes). You should generate a UUID for each new VuXML + quotes). Generate a UUID for each new VuXML entry (and do not forget to substitute it for the template - UUID unless you are writing the entry from scratch). You - can use &man.uuidgen.1; to generate a VuXML UUID. + UUID unless writing the entry from scratch). + use &man.uuidgen.1; to generate a VuXML UUID. @@ -234,10 +235,10 @@ important build-time configuration options. - It is your responsibility to find all such related + It is the submitter's responsibility to find all such related packages when writing a VuXML entry. Keep in mind that - make search name=foo is your friend. - The primary points to look for are as follows: + make search name=foo is helpful. + The primary points to look for are: @@ -269,8 +270,8 @@ <le>, <eq>, <ge>, and - <gt> elements. The version - ranges given should not overlap. + <gt> elements. Check the version + ranges given do not overlap. In a range specification, * (asterisk) denotes the smallest version number. In @@ -304,13 +305,13 @@ - The version ranges should allow for + The version ranges have to allow for PORTEPOCH and PORTREVISION if applicable. Please remember that according to the collation rules, a version with a non-zero PORTEPOCH is greater than any version without PORTEPOCH, - e.g., 3.0,1 is greater than + for example, 3.0,1 is greater than 3.1 or even than 8.9. @@ -318,7 +319,7 @@ This is a summary of the issue. XHTML is used in this field. At least enclosing <p> - and </p> should appear. More + and </p> has to appear. More complex mark-up may be used, but only for the sake of accuracy and clarity: No eye candy please. @@ -337,7 +338,7 @@ This is a &os; + xlink:href="http://www.freebsd.org/support.html">&os; problem report. @@ -384,7 +385,7 @@ - This is a generic URL. It should be used only if none + This is a generic URL. Only it if none of the other reference categories apply. @@ -401,37 +402,37 @@ This is the date when any information in the entry was last modified (YYYY-MM-DD). - New entries must not include this field. It should be - added upon editing an existing entry. + New entries must not include this field. Add it when + editing an existing entry. - Testing Your Changes to the VuXML Database + Testing Changes to the VuXML Database - Assume you just wrote or filled in an entry for a + Assume a new entry for a vulnerability in the package clamav that has been fixed in version 0.65_7. - As a prerequisite, you need to + As a prerequisite, install fresh versions of the ports ports-mgmt/portaudit, ports-mgmt/portaudit-db, and security/vuxml. - To run packaudit you must have + The user running packaudit must have permission to write to its DATABASEDIR, typically /var/db/portaudit. - To use a different directory set the - DATABASEDIR environment variable to a + To use a different directory, set the + DATABASEDIR environment variable to a different location. - If you are working in a directory other than - ${PORTSDIR}/security/vuxml set the - VUXMLDIR environment variable to the + If working in a directory other than + ${PORTSDIR}/security/vuxml, set the + VUXMLDIR environment variable to the directory where vuln.xml is located. @@ -444,18 +445,18 @@ &prompt.user; packaudit &prompt.user; portaudit clamav-0.65_6 - If there is none found, you have the green light to add a + If there is none found, add a new entry for this vulnerability. &prompt.user; cd ${PORTSDIR}/security/vuxml &prompt.user; make newentry - When you are done verify its syntax and formatting. + Verify its syntax and formatting: &prompt.user; make validate - You will need at least one of the following packages + At least one of these packages needs to be installed: textproc/libxml2, textproc/jade. @@ -466,8 +467,8 @@ &prompt.user; packaudit To verify that the <affected> - section of your entry will match correct package(s), issue the - following command: + section of the entry will match correct package(s), issue this + command: &prompt.user; portaudit -f /usr/ports/INDEX -r uuid @@ -476,11 +477,11 @@ understanding of the command syntax. - Make sure that your entry produces no spurious matches in + Make sure that the entry produces no spurious matches in the output. Now check whether the right package versions are matched - by your entry: + by the entry: &prompt.user; portaudit clamav-0.65_6 clamav-0.65_7 Affected package: clamav-0.65_6 (matched by clamav<0.65_7) @@ -489,8 +490,8 @@ Reference: <http://www.freebsd.org/po 1 problem(s) found. - The former version should match while the latter one - should not. + The former version matches while the latter one + does not. Finally, verify whether the web page generated from the VuXML database looks like expected: From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 12:01:30 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3D5FE37F; Tue, 16 Sep 2014 12:01:30 +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 282CA1F5; Tue, 16 Sep 2014 12:01:30 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GC1UeG026877; Tue, 16 Sep 2014 12:01:30 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GC1UPW026876; Tue, 16 Sep 2014 12:01:30 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409161201.s8GC1UPW026876@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Tue, 16 Sep 2014 12:01:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45616 - head/en_US.ISO8859-1/books/porters-handbook/special 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: Tue, 16 Sep 2014 12:01:30 -0000 Author: mat (ports committer) Date: Tue Sep 16 12:01:29 2014 New Revision: 45616 URL: http://svnweb.freebsd.org/changeset/doc/45616 Log: igor -Ry and some other rewording and fixes. Differential Revision: https://reviews.freebsd.org/D653 Reviewed by: wblock Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml Tue Sep 16 11:58:50 2014 (r45615) +++ head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml Tue Sep 16 12:01:29 2014 (r45616) @@ -10,16 +10,15 @@ Special Considerations - There are some more things you have to take into account - when you create a port. This section explains the most common - of those. + This section explains the most common things to consider when + creating a port. Staging bsd.port.mk expects ports to work with a stage directory. This means that a port - should not install files directly to the regular destination + must not install files directly to the regular destination directories (that is, under PREFIX, for example) but instead into a separate directory from which the package is then built. In many cases, this does not require @@ -42,7 +41,7 @@ The vast majority of ports do not really - need to be root. You can mostly avoid it by + need to be root. It can mostly be avoided by using USES=uidfix, and from time to time by slightly patching the port's @@ -50,7 +49,7 @@ Meta ports, or ports that do not install files themselves - but only depend on other ports, should avoid needlessly + but only depend on other ports, must avoid needlessly extracting the &man.mtree.8; to the stage directory. This is the basic directory layout of the package, and these empty directories will be seen as orphans. To prevent @@ -58,8 +57,8 @@ NO_MTREE= yes - Staging is enabled by prepending the - STAGEDIR variable to paths used in the + Staging is enabled by prepending + STAGEDIR to paths used in the pre-install, do-install, and post-install targets (see the @@ -72,21 +71,21 @@ absolute paths whenever possible. When creating a symlink, STAGEDIR - should be prepended to the target path only. For + is prepended to the target path only. For example: - ${LN} -sf libfoo.so.42 ${STAGEDIR}${PREFIX}/lib/libfoo.so + ${LN} -sf libfoo.so.42 ${STAGEDIR}${PREFIX}/lib/libfoo.so The source path - ${PREFIX}/lib/libfoo.so.42 looks fine but + ${PREFIX}/lib/libfoo.so.42 looks fine but could, in fact, be incorrect. Absolute paths can point to a wrong location, like when a remote file system has been mounted with NFS under a non-root mount point. Relative paths are less fragile, and often much shorter. - Ports that install kernel modules must prepend the - STAGEDIR variable to + Ports that install kernel modules must prepend + STAGEDIR to their destination, by default /boot/modules. @@ -106,7 +105,7 @@ distribution file. The second approach seems easier at first, but there are some serious drawbacks: - The following list is loosely based on the This list is loosely based on the Fedora and Gentoo @@ -220,7 +219,7 @@ port. If such a port does not exist yet, consider creating it. - Bundled libraries should only be used if upstream has a + Only use bundled libraries if the upstream has a good track record on security and using unbundled versions leads to overly complex patches. @@ -229,7 +228,7 @@ Shared Libraries - If your port installs one or more shared libraries, define + If the port installs one or more shared libraries, define a USE_LDCONFIG make variable, which will instruct a bsd.port.mk to run ${LDCONFIG} -m on the directory @@ -239,21 +238,21 @@ into the shared library cache. This variable, when defined, will also facilitate addition of an appropriate @exec /sbin/ldconfig -m and - @unexec /sbin/ldconfig -R pair into your - pkg-plist file, so that a user who + @unexec /sbin/ldconfig -R pair into + pkg-plist, so that a user who installed the package can start using the shared library immediately and de-installation will not cause the system to still believe the library is there. USE_LDCONFIG= yes - If you need, you can override the default directory by - setting the USE_LDCONFIG value to a list of + The default directory can be overridden by + setting USE_LDCONFIG to a list of directories into which shared libraries are to be installed. - For example if your port installs shared libraries into + For example, if the port installs shared libraries into PREFIX/lib/foo and PREFIX/lib/bar - directories you could use the following in your + use this in Makefile: USE_LDCONFIG= ${PREFIX}/lib/foo ${PREFIX}/lib/bar @@ -270,14 +269,14 @@ When installing 32-bit libraries on 64-bit system, use USE_LDCONFIG32 instead. - If the software you are porting uses If the software uses autotools, and specifically - libtool, you should add libtool, add USES=libtool. When the major library version number increments in the update to the new port version, all other ports that link to - the affected library should have their + the affected library must have their PORTREVISION incremented, to force recompilation with the new library version. @@ -291,7 +290,7 @@ profit, and so on. - It is your responsibility as a porter to read the + It is the responsibility of a porter to read the licensing terms of the software and make sure that the &os; project will not be held accountable for violating them by redistributing the source or compiled binaries @@ -300,7 +299,7 @@ In situations like this, the variables described in the - following sections can be set. + next sections can be set. <varname>NO_PACKAGE</varname> @@ -316,15 +315,16 @@ on a CD-ROM (or similar media) unless NO_CDROM is set as well. - NO_PACKAGE should also be used if the + If the binary package is not generally useful, and the application - should always be compiled from the source code. For + must always be compiled from the source code, use + NO_PACKAGE. For example, if the application has configuration information - that is site specific hard coded in to it at compile time, + that is site specific hard coded into it at compile time, set NO_PACKAGE. - NO_PACKAGE should be set to a string - describing the reason why the package should not be + Set NO_PACKAGE to a string + describing the reason why the package cannot be generated. @@ -343,9 +343,9 @@ DISTFILES will be available, and only via FTP/HTTP. - NO_CDROM should be set to a string + Set NO_CDROM to a string describing the reason why the port cannot be redistributed - on CD-ROM. For instance, this should be used if the port's + on CD-ROM. For instance, use this if the port's license is for non-commercial use only. @@ -353,13 +353,13 @@ <varname>NOFETCHFILES</varname> - Files defined in the NOFETCHFILES - variable are not fetchable from any of the + Files defined in NOFETCHFILES + are not fetchable from any of MASTER_SITES. An example of such a file is when the file is supplied on CD-ROM by the vendor. Tools which check for the availability of these files - on the MASTER_SITES should ignore these + on MASTER_SITES have to ignore these files and not report about them. @@ -371,12 +371,12 @@ DISTFILES nor distributing the binary package in any way. - NO_CDROM or - NO_PACKAGE should not be set along with - RESTRICTED since the latter variable + Do not set NO_CDROM or + NO_PACKAGE along with + RESTRICTED, since the latter variable implies the former ones. - RESTRICTED should be set to a string + Set RESTRICTED to a string describing the reason why the port cannot be redistributed. Typically, this indicates that the port contains proprietary software and that the user will need to manually download @@ -400,10 +400,10 @@ <varname>LEGAL_TEXT</varname> If the port has legal concerns not addressed by the - above variables, the variable LEGAL_TEXT - should be set to a string explaining the concern. For + above variables, set LEGAL_TEXT + to a string explaining the concern. For example, if special permission was obtained for &os; to - redistribute the binary, this variable should indicate + redistribute the binary, this variable must indicate so. @@ -482,8 +482,8 @@ IGNORE= may not be redistributed because implementation is listed in USES, the variables GMAKE (for the GNU version) or FMAKE - (for the legacy &os; version) are available. Most ports - should only use MAKE_CMD within the + (for the legacy &os; version) are available. + Only use MAKE_CMD within the application Makefiles in WRKSRC to call the make implementation expected by the @@ -497,10 +497,10 @@ IGNORE= may not be redistributed because linkend="uses-imake">USES=imake section of for more details. - If your port's source Makefile has - something else than all as the + If the port's source Makefile has + something other than all as the main build target, set ALL_TARGET - accordingly. Same goes for + accordingly. The same goes for install and INSTALL_TARGET. @@ -508,10 +508,10 @@ IGNORE= may not be redistributed because <command>configure</command> Script - If your port uses the configure - script to generate Makefile files from - Makefile.in files, set - GNU_CONFIGURE=yes. If you want to give + If the port uses the configure + script to generate Makefile from + Makefile.in, set + GNU_CONFIGURE=yes. To give extra arguments to the configure script (the default argument is --prefix=${PREFIX} --infodir=${PREFIX}/${INFO_PATH} @@ -519,7 +519,7 @@ IGNORE= may not be redistributed because --build=${CONFIGURE_TARGET}), set those extra arguments in CONFIGURE_ARGS. Extra environment variables can be passed using - CONFIGURE_ENV variable. + CONFIGURE_ENV. Variables for Ports That Use @@ -624,8 +624,8 @@ IGNORE= may not be redistributed because </table> <table frame="none" xml:id="using-cmake-user-variables"> - <title>Variables the Users can define for - <command>cmake</command> builds + Variables the Users Can Define for + <command>cmake</command> Builds @@ -653,7 +653,7 @@ IGNORE= may not be redistributed because
    - CMake supports the following + CMake supports these build profiles: Debug, Release, RelWithDebInfo and @@ -664,14 +664,14 @@ IGNORE= may not be redistributed because CFLAGS to -O2 -g and -Os -DNDEBUG correspondingly. The lower-cased value of CMAKE_BUILD_TYPE is - exported to the PLIST_SUB and should be - used if port installs *.cmake files + exported to PLIST_SUB and must be + used if the port installs *.cmake depending on the build type (see deskutils/strigi for an example). Please note that some projects may define their own build profiles and/or force particular build type by setting CMAKE_BUILD_TYPE in - CMakeLists.txt files. In order to + CMakeLists.txt. To make a port for such a project respect CFLAGS and WITH_DEBUG, the CMAKE_BUILD_TYPE definitions must be @@ -692,7 +692,7 @@ IGNORE= may not be redistributed because <literal>USES= cmake</literal> Example - The following snippet demonstrates the use of + This snippet demonstrates the use of CMake for a port. CMAKE_SOURCE_PATH is not usually required, but can be set when the sources are not located @@ -707,7 +707,7 @@ CMAKE_SOURCE_PATH= ${WRKSRC}/subp Using <command>scons</command> - If your port uses SCons, + If the port uses SCons, define USE_SCONS=yes. @@ -753,7 +753,7 @@ CMAKE_SOURCE_PATH= ${WRKSRC}/subp To make third party SConstruct respect everything that is passed to SCons in SCONS_ENV (that is, most importantly, - CC/CXX/CFLAGS/CXXFLAGS), patch the + CC/CXX/CFLAGS/CXXFLAGS), patch SConstruct so build Environment is constructed like this: @@ -842,9 +842,9 @@ CMAKE_SOURCE_PATH= ${WRKSRC}/subp autoheaderSome ports do not contain a configure script, but do - contain an autoconf template in the - configure.ac file. You can use the - following assignments to let autoconf + contain an autoconf template in + configure.ac. Use these + assignments to let autoconf create the configure script, and also have autoheader create template headers for use by the configure script. @@ -872,14 +872,14 @@ CMAKE_SOURCE_PATH= ${WRKSRC}/subp aclocalSome packages only contain - Makefile.am files. These have to be - converted into Makefile.in files using + Makefile.am. These have to be + converted into Makefile.in using automake, and the further processed by configure to generate an actual Makefile.Similarly, packages occasionally do not ship with - included aclocal.m4 files, again + an included aclocal.m4, again required to build the software. This can be achieved with aclocal, which scans configure.ac or @@ -914,8 +914,8 @@ CMAKE_SOURCE_PATH= ${WRKSRC}/subp Basic Usage - If your port requires gettext, set - USES= gettext, and your port will inherit + If the port requires gettext, set + USES= gettext, and the port will inherit a dependency on libintl.so from devel/gettext. Other values for gettext usage are listed in @@ -945,13 +945,13 @@ GNU_CONFIGURE= yes Optional Usage - Some software products allow for disabling NLS, e.g., + Some software products allow for disabling NLS. For example, through passing to - configure. In that case, your port - should use gettext conditionally, - depending on the status of the NLS - option. For ports of low to medium complexity, you can rely - on the following idiom: + configure. In that case, the port + must use gettext conditionally, + depending on the status of the NLS + option. For ports of low to medium complexity, use + this idiom: GNU_CONFIGURE= yes @@ -981,7 +981,7 @@ PLIST_SUB+= NLS="@comment " .include <bsd.port.mk> - The next item on your to-do list is to arrange so that + The next item on the to-do list is to arrange so that the message catalog files are included in the packing list conditionally. The Makefile part of this task is already provided by the idiom. It is explained @@ -994,7 +994,7 @@ PLIST_SUB+= NLS="@comment " Consequently, the lines prefixed by %%NLS%% will become mere comments in the final packing list if NLS is off; otherwise the prefix will - be just left out. All you need to do now is insert + be just left out. Then insert %%NLS%% before each path to a message catalog file in pkg-plist. For example: @@ -1002,8 +1002,8 @@ PLIST_SUB+= NLS="@comment " %%NLS%%share/locale/fr/LC_MESSAGES/foobar.mo %%NLS%%share/locale/no/LC_MESSAGES/foobar.mo - In high complexity cases, you may need to use more - advanced techniques than the recipe given here, such as + In high complexity cases, more advanced techniques + may be needed, such as dynamic packing list generation. @@ -1015,7 +1015,7 @@ PLIST_SUB+= NLS="@comment " catalog files. The target directories for them, which reside under LOCALBASE/share/locale, - should rarely be created and removed by a port. The most + must not be created and removed by a port. The most popular languages have their respective directories listed in PORTSDIR/Templates/BSD.local.dist. @@ -1031,7 +1031,7 @@ PLIST_SUB+= NLS="@comment " Using <application>Perl</application> If MASTER_SITES is set to - CPAN, the correct subdirectory should be + CPAN, the correct subdirectory is usually selected automatically. If the default subdirectory is wrong, CPAN/Module can be used to change it. MASTER_SITES can also be set to the old @@ -1050,13 +1050,13 @@ PLIST_SUB+= NLS="@comment " directory. In such case, using author's id as MASTER_SITE_SUBDIR is allowed. The CPAN:AUTHOR macro can be used, which will - be translated to the hashed author directory. (e.g., + be translated to the hashed author directory. For example, CPAN:AUTHOR will be converted to - authors/id/A/AU/AUTHOR.) + authors/id/A/AU/AUTHOR. When a port needs Perl support, - it should use USES=perl5 with the optional - USE_PERL5 like described in USES=perl5 with the optional + USE_PERL5 described in the perl5 USES description.
    @@ -1076,22 +1076,25 @@ PLIST_SUB+= NLS="@comment " PERLThe full path of the Perl 5 interpreter, either in the system or installed from a port, but - without the version number. Use this if you need to - replace #!lines in - scripts. + without the version number. Use this when the software + needs the path to the Perl + interpreter. To replace + #!lines in scripts, + use USES=shebangfix. PERL_VERSION The full version of Perl - installed (e.g., 5.8.9). + installed (for example, 5.8.9). PERL_LEVEL The installed Perl version as an integer of the form MNNNPP - (e.g., 500809). + (for example, 500809). @@ -1104,7 +1107,7 @@ PLIST_SUB+= NLS="@comment " PERL_PORT Name of the Perl port that is - installed (e.g., perl5). + installed (for example, perl5). @@ -1119,7 +1122,7 @@ PLIST_SUB+= NLS="@comment " Ports of Perl modules which do not have an official - website should link to cpan.org in + website must link to cpan.org in the WWW line of pkg-descr. The preferred URL form is http://search.cpan.org/dist/Module-Name/ @@ -1168,7 +1171,7 @@ PLIST_SUB+= NLS="@comment " X.Org Components The X11 implementation available in The Ports Collection - is X.Org. If your application depends on X components, set + is X.Org. If the application depends on X components, set USE_XORG to the list of required components. Available components, at the time of writing, are: @@ -1192,9 +1195,9 @@ PLIST_SUB+= NLS="@comment " /usr/ports/Mk/bsd.xorg.mk. The Mesa Project is an effort to provide free OpenGL - implementation. You can specify a dependency on various - components of this project with USE_GL - variable. Valid options are: + implementation. To specify a dependency on various + components of this project, use USE_GL. + Valid options are: egl, gl, glesv2, glew, glu, glut, glw and linux. For backwards compatibility, the value of yes maps to @@ -1238,7 +1241,7 @@ USE_XORG= x11 xpm Ports That Require Motif - If your port requires a Motif library, define + If the port requires a Motif library, define USES= motif in the Makefile. Default Motif implementation is @@ -1246,11 +1249,11 @@ USE_XORG= x11 xpm Users can choose x11-toolkits/lesstif instead by setting WANT_LESSTIF - variable in their make.conf. + in their make.conf. - The MOTIFLIB variable will be set by + MOTIFLIB will be set by motif.mk to reference the - appropriate Motif library. Please patch the source of your + appropriate Motif library. Please patch the source of the port to use ${MOTIFLIB} wherever the Motif library is referenced in the original Makefile or @@ -1263,7 +1266,7 @@ USE_XORG= x11 xpm If the port refers to the Motif library as -lXm in its Makefile or - Imakefile, simply substitute + Imakefile, substitute ${MOTIFLIB} for it. @@ -1285,7 +1288,7 @@ USE_XORG= x11 xpm X11 Fonts - If your port installs fonts for the X Window System, put + If the port installs fonts for the X Window System, put them in LOCALBASE/lib/X11/fonts/local. @@ -1295,7 +1298,7 @@ USE_XORG= x11 xpm Some applications require a working X11 display for compilation to succeed. This pose a problem for machines - that operate headless. When the following variable is used, + that operate headless. When this variable is used, the build infrastructure will start the virtual framebuffer X server. The working DISPLAY is then passed to the build. See Files Ports that include predefined - *.desktop files should + *.desktop must include those files in pkg-plist and install them in the $LOCALBASE/share/applications @@ -1350,14 +1353,14 @@ USE_XORG= x11 xpm - Creating Desktop Entries with the - <varname>DESKTOP_ENTRIES</varname> Macro + Creating Desktop Entries with + <varname>DESKTOP_ENTRIES</varname> Desktop entries can be easily created for applications - by using the DESKTOP_ENTRIES variable. A + by using DESKTOP_ENTRIES. A file named name.desktop - will be created, installed, and added to the + will be created, installed, and added to pkg-plist automatically. Syntax is: @@ -1376,7 +1379,7 @@ USE_XORG= x11 xpm after it has started. Programs that are not compatible with startup notifications would never clear the indicator (potentially confusing and infuriating the user), and - should have StartupNotify set to + must have StartupNotify set to false so the indicator is not shown at all. @@ -1407,12 +1410,12 @@ USE_XORG= x11 xpm Ports That Require Qt The Ports Collection provides support for Qt 4 and Qt 5 - frameworks with the - USE_QTx - variable, where x is + frameworks with + USE_QTx, + where x is 4 or 5. - USE_QTx should - be set to the list of required Qt components (libraries, + Set USE_QTx + to the list of required Qt components (libraries, tools, plugins). The Qt 4 and Qt 5 frameworks are quite similar. The main difference is the set of supported components. @@ -1494,29 +1497,29 @@ PLIST_SUB+= QT_INCDIR=${QT_INCDIR_REL} \ Some configure scripts do not support the arguments above. To suppress modification ofCONFIGURE_ENV - and CONFIGURE_ARGS, set the - QT_NONSTANDARD variable. + and CONFIGURE_ARGS, set + QT_NONSTANDARD. Component Selection Individual Qt tool and library dependencies must be - specified in the - USE_QTx - variable. Every component can be suffixed with + specified in + USE_QTx. + Every component can be suffixed with _build or _run, the - suffix indicating whether the component should be depended on + suffix indicating whether the dependency on the component is at buildtime or runtime. If unsuffixed, the component will be depended on at both build- and runtime. Usually, library - components should be specified unsuffixed, tool components - should be specified with the _build suffix - and plugin components should be specified with the + components are specified unsuffixed, tool components + are mostly specified with the _build suffix + and plugin components are specified with the _run suffix. The most commonly used components are listed below (all available components are listed in _USE_QT_ALL, _USE_QT4_ONLY, and - _USE_QT5_ONLY variables in + _USE_QT5_ONLY in /usr/ports/Mk/bsd.qt.mk):
    @@ -1784,10 +1787,10 @@ USE_QT5= buildtools_buildMissing additional include paths. Many applications come with system tray icon support, but neglect to look for - includes and/or libraries in the X11 directories. You - can tell qmake to add directories to - the include and library search paths via the command - line, for example: + includes and/or libraries in the X11 directories. To add + directories to qmake's + include and library search paths via the command + line, use:QMAKE_ARGS+= INCLUDEPATH+=${LOCALBASE}/include \ LIBS+=-L${LOCALBASE}/lib @@ -1819,11 +1822,11 @@ USE_QT5= buildtools_buildUSE_KDE4 to the list of required components. _build and _run suffixes can be used to force - components dependency type (e.g., + components dependency type (for example, baseapps_run). If no suffix is set, a - default dependency type will be used. If you want to force + default dependency type will be used. To force both types, add the component twice with both suffixes - (e.g., automoc4_build automoc4_run). The + (for example, automoc4_build automoc4_run). The most commonly used components are listed below (up-to-date components are documented at the top of /usr/ports/Mk/bsd.kde4.mk): @@ -1995,7 +1998,7 @@ USE_QT5= buildtools_buildUSE_KDE4 does not imply USE_QT4. If a port requires some - Qt 4 components, they should be specified in + Qt 4 components, specify them in USE_QT4.USES= cmake:outsource @@ -2011,14 +2014,14 @@ USE_QT4= moc_build qmake_build rcc_build Variable Definitions - If your port needs a Java™ Development Kit - (JDK™) to either build, run or even extract the - distfile, then it should define + If the port needs a Java™ Development Kit + (JDK™) to either build, run or even extract the + distfile, then define USE_JAVA. - There are several JDKs in the ports collection, from - various vendors, and in several versions. If your port must - use one of these versions, you can define which one. The + There are several JDKs in the ports collection, from + various vendors, and in several versions. If the port must + use one of these versions, define which one. The most current version, and &os; default is java/openjdk6. @@ -2037,7 +2040,7 @@ USE_QT4= moc_build qmake_build rcc_build USE_JAVA - Should be defined for the remaining variables + Define for the remaining variables to have any effect. @@ -2045,21 +2048,21 @@ USE_QT4= moc_build qmake_build rcc_build JAVA_VERSIONList of space-separated suitable Java versions for the port. An optional "+" - allows you to specify a range of versions (allowed + allows specifying a range of versions (allowed values: 1.5[+] 1.6[+] 1.7[+]). JAVA_OS - List of space-separated suitable JDK port + List of space-separated suitable JDK port operating systems for the port (allowed values: native linux). JAVA_VENDOR - List of space-separated suitable JDK port + List of space-separated suitable JDK port vendors for the port (allowed values: freebsd bsdjava sun openjdk). @@ -2067,23 +2070,20 @@ USE_QT4= moc_build qmake_build rcc_build JAVA_BUILD - When set, it means that the selected JDK port - should be added to the build dependencies of the - port. + When set, add the selected JDK port to the build + dependencies. JAVA_RUN - When set, it means that the selected JDK port - should be added to the run dependencies of the - port. + When set, add the selected JDK port to the run + dependencies. JAVA_EXTRACT - When set, it means that the selected JDK port - should be added to the extract dependencies of the - port. + When set, add the selected JDK port to the + extract dependencies. @@ -2106,61 +2106,61 @@ USE_QT4= moc_build qmake_build rcc_build JAVA_PORT - The name of the JDK port (e.g., - 'java/openjdk6'). + The name of the JDK port (for example, + java/openjdk6). JAVA_PORT_VERSION - The full version of the JDK port (e.g., - '1.6.0'). If you only need the - first two digits of this version number, use + The full version of the JDK port (for example, + 1.6.0). Only the first two + digits of this version number are needed, use ${JAVA_PORT_VERSION:C/^([0-9])\.([0-9])(.*)$/\1.\2/}. JAVA_PORT_OS - The operating system used by the JDK port - (e.g., 'native'). + The operating system used by the JDK port + (for example, 'native'). JAVA_PORT_VENDOR - The vendor of the JDK port (e.g., + The vendor of the JDK port (for example, 'openjdk'). JAVA_PORT_OS_DESCRIPTION Description of the operating system used by the - JDK port (e.g., + JDK port (for example, 'Native'). JAVA_PORT_VENDOR_DESCRIPTION - Description of the vendor of the JDK port - (e.g., 'OpenJDK BSD Porting + Description of the vendor of the JDK port + (for example, 'OpenJDK BSD Porting Team'). JAVA_HOME - Path to the installation directory of the JDK - (e.g., + Path to the installation directory of the JDK + (for example, '/usr/local/openjdk6'). JAVAC - Path to the Java compiler to use (e.g., + Path to the Java compiler to use (for example, '/usr/local/openjdk6/bin/javac'). JAR Path to the jar tool to use - (e.g., + (for example, '/usr/local/openjdk6/bin/jar' or '/usr/local/bin/fastjar'). @@ -2169,14 +2169,14 @@ USE_QT4= moc_build qmake_build rcc_build APPLETVIEWER Path to the appletviewer - utility (e.g., + utility (for example, '/usr/local/openjdk6/bin/appletviewer'). JAVA Path to the java executable. - Use this for executing Java programs (e.g., + Use this for executing Java programs (for example, '/usr/local/openjdk6/bin/java'). @@ -2242,7 +2242,7 @@ USE_QT4= moc_build qmake_build rcc_build JAVA_CLASSES - Path to the archive that contains the JDK class + Path to the archive that contains the JDK class files, ${JAVA_HOME}/jre/lib/rt.jar. @@ -2250,11 +2250,11 @@ USE_QT4= moc_build qmake_build rcc_build
    - You may use the java-debug make - target to get information for debugging your port. It will - display the value of many of the forecited variables. + Use the java-debug make + target to get information for debugging the port. It will + display the value of many of the previously listed variables. - Additionally, the following constants are defined so all + Additionally, these constants are defined so all Java ports may be installed in a consistent way: @@ -2278,7 +2278,7 @@ USE_QT4= moc_build qmake_build rcc_build JAVAJARDIR - The directory where JAR files should be + The directory where JAR files is installed. Default: ${JAVASHAREDIR}/classes. @@ -2305,37 +2305,37 @@ USE_QT4= moc_build qmake_build rcc_build When the port is to be built using Apache Ant, it has to define USE_ANT. Ant is thus considered to be the sub-make command. When no - do-build target is defined by the port, a - default one will be set that simply runs Ant according to + do-build target is defined by the port, a + default one will be set that runs Ant according to MAKE_ENV, MAKE_ARGS and ALL_TARGET. This is similar to the - USES= gmake mechanism, which is + USES= gmake mechanism, which is documented in . Best Practices - When porting a Java library, your port should install + When porting a Java library, the port has to install the JAR file(s) in ${JAVAJARDIR}, and everything else under ${JAVASHAREDIR}/${PORTNAME} (except for - the documentation, see below). In order to reduce the - packing file size, you may reference the JAR file(s) - directly in the Makefile. Just use the - following statement (where myport.jar + the documentation, see below). To reduce the + packing file size, reference the JAR file(s) + directly in the Makefile. Use this + statement (where myport.jar is the name of the JAR file installed as part of the port): - PLIST_FILES+= %%JAVAJARDIR%%/myport.jar + PLIST_FILES+= %%JAVAJARDIR%%/myport.jar When porting a Java application, the port usually installs everything under a single directory (including its *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 12:02:19 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8F6B33FE; Tue, 16 Sep 2014 12:02:19 +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 79DDF208; Tue, 16 Sep 2014 12:02:19 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GC2Jo7028461; Tue, 16 Sep 2014 12:02:19 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GC2JfV028460; Tue, 16 Sep 2014 12:02:19 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409161202.s8GC2JfV028460@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Tue, 16 Sep 2014 12:02:19 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45617 - head/en_US.ISO8859-1/books/porters-handbook/upgrading 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: Tue, 16 Sep 2014 12:02:19 -0000 Author: mat (ports committer) Date: Tue Sep 16 12:02:19 2014 New Revision: 45617 URL: http://svnweb.freebsd.org/changeset/doc/45617 Log: igor -Ry and some other rewording and fixes. Differential Revision: https://reviews.freebsd.org/D655 Reviewed by: wblock Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/upgrading/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/upgrading/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/upgrading/chapter.xml Tue Sep 16 12:01:29 2014 (r45616) +++ head/en_US.ISO8859-1/books/porters-handbook/upgrading/chapter.xml Tue Sep 16 12:02:19 2014 (r45617) @@ -11,29 +11,32 @@ Upgrading a Port - When you notice that a port is out of date compared to the - latest version from the original authors, you should first ensure - that you have the latest port. You can find them in the - ports/ports-current directory of the &os; FTP - mirror sites. However, if you are working with more than a few - ports, you will probably find it easier to use - Subversion or &man.portsnap.8; to keep - your whole ports collection up-to-date, as described in the When a port is not the most recent version available from the + authors, update the local working copy of + /usr/ports. The port might have already been + updated to the new version. + + When working with more than a few ports, it will probably be + easier to use Subversion to keep + the whole ports collection up-to-date, as described in the Handbook. This will have the added benefit of tracking all the port's dependencies. The next step is to see if there is an update already pending. - To do this, you have two options. There is a searchable interface + To do this, there are two options. There is a searchable interface to the FreeBSD - Problem Report (PR) database (also known as - GNATS). Select ports in - the dropdown, and enter the name of the port. + xlink:href="https://bugs.freebsd.org/search/">FreeBSD + Problem Report (PR) or bug database. + Select Ports Tree in + the Product dropdown, and enter the name of the port in the + Summary field. However, sometimes people forget to put the name of the port - into the Synopsis field in an unambiguous fashion. In that - case, you can try the + into the Summary field in an unambiguous fashion. In that + case, try searching in the Comment field in + the Detailled Bug Information section, or try + the &os; Ports Monitoring System (also known as portsmon). This system attempts to classify port PRs by portname. To search for PRs @@ -46,32 +49,32 @@ make maintainer. That person may already be working on an upgrade, or have a reason to not upgrade the port right now (because of, for example, stability problems of the - new version); you would not want to duplicate their work. Note + new version), and there is no need to duplicate their work. Note that unmaintained ports are listed with a maintainer of ports@FreeBSD.org, which is just the general ports mailing list, so sending mail there probably will not help in this case. If the maintainer asks you to do the upgrade or there is - no maintainer, then you have a chance to help out &os; by - preparing the update yourself! Please do this by using the + no maintainer, then help out &os; by + preparing the update! Please do this by using the &man.diff.1; command in the base system. To create a suitable diff for a single patch, copy the file that needs patching to - something.orig, save your changes to - something and then create your + something.orig, save the changes to + something and then create the patch: - &prompt.user; diff -u something.orig something > something.diff + &prompt.user; diff -u something.orig something > something.diff - Otherwise, you should either use the + Otherwise, either use the svn diff method () or copy the contents of the port to an entire different directory and use the result of the recursive &man.diff.1; - output of the new and old ports directories (e.g., if your + output of the new and old ports directories (for example, if the modified port directory is called superedit and the original is in our tree as superedit.bak, then save the result of @@ -82,16 +85,19 @@ deal with the case of new files being added or old files being deleted. Before sending us the diff, please examine the output to make sure all the changes make sense. (In particular, make - sure you first clean out the work directories with + sure to first clean out the work directories with make clean). - To simplify common operations with patch files, you can use + To simplify common operations with patch files, use + make makepatch as described in . + Other tools exists, like /usr/ports/Tools/scripts/patchtool.py. Before using it, please read /usr/ports/Tools/scripts/README.patchtool. If the port is unmaintained, and you are actively using - it yourself, please consider volunteering to become its + it, please consider volunteering to become its maintainer. &os; has over 4000 ports without maintainers, and this is an area where more volunteers are always needed. (For a detailed description of the responsibilities of maintainers, @@ -99,20 +105,19 @@ xlink:href="&url.books.developers-handbook;/policies.html#POLICIES-MAINTAINER">Developer's Handbook.) - The best way to send us the diff is by including it via - &man.send-pr.1; (category ports). If you are + To submit the diff, use the bug submit + form (category Ports Tree). If the + submitter is also maintaining the port, be sure to put [maintainer - update] at the beginning of your synopsis line and set - the Class of your PR to - maintainer-update. Otherwise, the - Class of your PR should be - change-request. Please mention any added or + update] at the beginning of the + Summary line. + Please mention any added or deleted files in the message, as they have to be explicitly - specified to &man.svn.1; when doing a commit. If the diff is - more than about 20KB, please compress and uuencode it; - otherwise, just include it in the PR as is. + specified to &man.svn.1; when doing a commit. Do not compress or + encode the diff. - Before using &man.send-pr.1;, review the Before submitting the bug, review the Writing the problem report section in the Problem Reports article. It contains far more information about how to @@ -134,7 +139,7 @@ committers understand exactly what is being changed. - Now that you have done all that, read about + Now that all of that is done, read about how to keep up-to-date in . @@ -145,8 +150,8 @@ are easier to handle than diffs between new and old directories. It is easier to see what has changed, and to update the diff if - something was modified in the Ports Collection since you - began work on it, or if the + something was modified in the Ports Collection since the + work on it began, or if the committer asks for something to be fixed. Also, a patch generated with svn diff can be easily applied with svn patch and will save some time to the @@ -159,7 +164,7 @@ - This can be anywhere you want, of course; building + This can be anywhere, of course. Building ports is not limited to within /usr/ports/. @@ -175,15 +180,15 @@ - While in the working directory, make any changes that you - would usually make to the port. If you add, move or remove a + While in the port directory, make any changes that are + needed. If adding, moving, or removing a file, use svn to track these changes: - &prompt.user; svn add new_file -&prompt.user; svn move old_name new_name -&prompt.user; svn remove deleted_file + &prompt.user; svn add new_file +&prompt.user; svn move old_name new_name +&prompt.user; svn remove deleted_file - Make sure that you check the port using the checklist in + Make sure to check the port using the checklist in and . @@ -192,8 +197,8 @@ - This will try to merge the differences between your - patch and current repository version; watch the output + This will attempt to merge the differences between the + patch and current repository version. Watch the output carefully. The letter in front of each file name indicates what was done with it. See for a complete list. @@ -213,8 +218,8 @@ G - The file was updated without problems (you will - only see this when working against a remote + The file was updated without problems (only when + working against a remote repository). @@ -239,40 +244,41 @@ &man.svn.1; was not able to merge the local changes with those from the repository. It is always a good idea to inspect the changes anyway, since &man.svn.1; does not know anything about - how a port should be, so it might (and probably will) merge + the structure of a port, so it might (and probably will) merge things that do not make sense. The last step is to make a unified &man.diff.1; of the changes: - &prompt.user; svn diff > ../`basename ${PWD}`.diff + &prompt.user; svn diff > ../`make -VPKGNAME`.diff - Any files that have been removed should be explicitly + Any files that have been removed have to be explicitly mentioned in the PR, because file removal may not be obvious to the committer. - Send your patch following the guidelines in + Send the patch following the guidelines in . - You can have patch automatically generated and the PR - pre-filled with your contact information by using - the Port Tools port - submit command. See The patch can be automatically generated and the PR + pre-filled with the contact information by using + port submit. See for more details. - The Files <filename>UPDATING</filename> and + <title><filename>UPDATING</filename> and <filename>MOVED</filename> + + <filename>/usr/ports/UPDATING</filename> + If upgrading the port requires special steps like changing configuration files or running a specific program, - you should document this in the file - /usr/ports/UPDATING. The format of + it must be documented in this file. The format of an entry in this file is as follows: YYYYMMDD: @@ -281,22 +287,42 @@ Special instructions - If you are including exact portmaster or portupgrading - instructions, please make sure to get the shell escaping - right. + + When including exact + portmaster, + portupgrade, and/or + pkg instructions, please make sure + to get the shell escaping right. For example, do + not use: + + &prompt.root; pkg delete -g -f docbook-xml* docbook-sk* docbook[2345]??-* docbook-4* + + As shown, the command will only work with + bourne shells. Instead, use the + form shown below, which will work with both + bourne shell and + c-shell: + + &prompt.root; pkg delete -g -f docbook-xml\* docbook-sk\* docbook\[2345\]\?\?-\* docbook-4\* + It is recommended that the AFFECTS line contains a glob matching all the ports affected by the entry so that automated tools can parse it as easily as possible. If an update concerns all the existing BIND 9 - versions the AFFECTS content should be - users of dns/bind9*, it should + versions the AFFECTS content must be + users of dns/bind9*, it must not be users of BIND 9 - The /usr/ports/MOVED file is used to + + + + <filename>/usr/ports/MOVED</filename> + + This file is used to list moved or removed ports. Each line in the file is made up of the name of the port, where the port was moved to, when, and why. If the port was removed, the section detailing where @@ -306,22 +332,32 @@ old name|new name (blank for deleted)|date of move|reason - The date should be entered in the form - YYYY-MM-DD. New entries should be added to - the top of the file to keep it in reverse chronological order - (the latest entries first). + The date must be entered in the form + YYYY-MM-DD. New entries are added to + the top of the file to keep it in reverse chronological order, + with the last entry first. If a port was removed but has since been restored, delete the line in this file that states that it was removed. If a port was renamed and then renamed back to its original - name, you should add a new one with the intermediate name to the + name, add a new one with the intermediate name to the old name, and remove the old entry as to not create a loop. - The changes can be validated with - Tools/scripts/MOVEDlint.awk. + + Any changes must be validated with + Tools/scripts/MOVEDlint.awk. + + If using a ports directory other than /usr/ports, use: + + + &prompt.user; cd /home/user/ports +&prompt.user; env PORTSDIR=$PWD Tools/scripts/MOVEDlint.awk + + + From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 12:41:03 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4808FE1A; Tue, 16 Sep 2014 12:41:03 +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 3246E7E2; Tue, 16 Sep 2014 12:41:03 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GCf3h1046722; Tue, 16 Sep 2014 12:41:03 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GCf3TL046721; Tue, 16 Sep 2014 12:41:03 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409161241.s8GCf3TL046721@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Tue, 16 Sep 2014 12:41:03 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45618 - head/en_US.ISO8859-1/books/porters-handbook/porting-dads 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: Tue, 16 Sep 2014 12:41:03 -0000 Author: mat (ports committer) Date: Tue Sep 16 12:41:02 2014 New Revision: 45618 URL: http://svnweb.freebsd.org/changeset/doc/45618 Log: igor -Ry and some other rewording and fixes. Differential Revision: https://reviews.freebsd.org/D647 Reviewed by: wblock Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml Tue Sep 16 12:02:19 2014 (r45617) +++ head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml Tue Sep 16 12:41:02 2014 (r45618) @@ -17,9 +17,9 @@ Here is a list of common dos and don'ts that are encountered during the porting process. Check the port against this list, but also check ports in the PR + xlink:href="https://bugs.FreeBSD.org/search/">PR database that others have submitted. Submit any - comments on ports you check as described in Bug Reports and General Commentary. Checking ports in the PR database will both make it faster for us to commit them, and @@ -35,18 +35,18 @@ build (see installing ports from a CDROM for an example of - building ports from a read-only tree). If you need to modify - one of the pkg-* - files, do so by redefining a - variable, not by writing over it. + building ports from a read-only tree). The + pkg-* files can + be modified by redefining a + variable rather than overwriting the file. <varname>WRKDIRPREFIX</varname> - Make sure your port honors WRKDIRPREFIX. - Most ports do not have to worry about this. In particular, if - you are referring to a WRKDIR of another + Make sure the port honors WRKDIRPREFIX. + Most ports do not have to worry about this. In particular, when + referring to a WRKDIR of another port, note that the correct location is WRKDIRPREFIXPORTSDIR/subdir/name/work not @@ -55,8 +55,8 @@ .CURDIR/../../subdir/name/work or some such. - Also, if you are defining WRKDIR - yourself, make sure you prepend + Also, if defining WRKDIR, + make sure to prepend ${WRKDIRPREFIX}${.CURDIR} in the front. @@ -64,7 +64,7 @@ Differentiating Operating Systems and OS Versions - You may come across code that needs modifications or + Some code needs modifications or conditional compilation based upon what version of &os; Unix it is running under. The preferred way to tell &os; versions apart are the __FreeBSD_version and @@ -87,6 +87,9 @@ /* 9.1+ release specific code here */ # endif #endif + + A complete list of __FreeBSD_version + values is available in . @@ -97,15 +100,15 @@ .include <bsd.port.mk> line. It usually can be avoided by including bsd.port.pre.mk somewhere in the middle of - your Makefile and + the Makefile and bsd.port.post.mk at the end. - + Include either the bsd.port.pre.mk/bsd.port.post.mk pair or bsd.port.mk only; do not mix these two usages. - + bsd.port.pre.mk only defines a few variables, which can be used in tests in the @@ -130,20 +133,20 @@ ARCH The architecture as returned by uname - -m (e.g., i386) + -m (for example, i386) OPSYS The operating system type, as returned by - uname -s (e.g., + uname -s (for example, FreeBSD) OSREL The release version of the operating system - (e.g., 2.1.5 or + (for example, 2.1.5 or 2.2.7) @@ -156,7 +159,7 @@ LOCALBASE - The base of the local tree (e.g., + The base of the local tree (for example, /usr/local) @@ -172,12 +175,12 @@ - If you have to define the variable - MASTERDIR, do so before including + When MASTERDIR is needed, always define + it before including bsd.port.pre.mk. - Here are some examples of things you can write after + Here are some examples of things that can be added after bsd.port.pre.mk: # no need to compile lang/perl5 if perl5 is already in system @@ -185,9 +188,8 @@ BROKEN= perl is in system .endif - You did remember to use tab instead of spaces after - BROKEN= and - :-). + Always use tab instead of spaces after + BROKEN=. @@ -213,21 +215,20 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD Do Things Rationally - The Makefile should do things simply - and reasonably. If you can make it a couple of lines shorter or - more readable, then do so. Examples include using a make + The Makefile should do things in a + simple and reasonable manner. Making it a couple of lines shorter or + more readable is always better. Examples include using a make .if construct instead of a shell if construct, not redefining - do-extract if you can redefine - EXTRACT* instead, and using + do-extract if redefining + EXTRACT* is enough, and using GNU_CONFIGURE instead of CONFIGURE_ARGS += --prefix=${PREFIX}. - If you find yourself having to write a lot of new code to - try to do something, please go back and review - bsd.port.mk to see if it contains an - existing implementation of what you are trying to do. While + If a lot of new code is needed to do something, there may + already be an implementation of it in + bsd.port.mk. While hard to read, there are a great many seemingly-hard problems for which bsd.port.mk already provides a shorthand solution. @@ -238,7 +239,7 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD CXX The port must respect both CC and - CXX variables. What we mean by this is that + CXX. What we mean by this is that the port must not set the values of these variables absolutely, overriding existing values; instead, it may append whatever values it needs to the existing values. This is so that build @@ -249,24 +250,23 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD NO_PACKAGE=ignores either cc or cxx to the Makefile. - An example of a Makefile respecting - both CC and CXX - variables follows. Note the ?=: + Here is an example of a Makefile respecting + both CC and CXX. + Note the ?=: CC?= gcc CXX?= g++ Here is an example which respects neither - CC nor CXX - variables: + CC nor CXX: CC= gcc CXX= g++ Both CC and CXX - variables can be defined on &os; systems in + can be defined on &os; systems in /etc/make.conf. The first example defines a value if it was not previously set in /etc/make.conf, preserving any system-wide @@ -277,10 +277,10 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD Respect <varname>CFLAGS</varname> - The port must respect the CFLAGS - variable. What we mean by this is that the port must not set + The port must respect CFLAGS. + What we mean by this is that the port must not set the value of this variable absolutely, overriding the existing - value; instead, it may append whatever values it needs to the + value. Instead, it may append whatever values it needs to the existing value. This is so that build options that affect all ports can be set globally. @@ -288,26 +288,26 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD NO_PACKAGE=ignores cflags to the Makefile. - An example of a Makefile respecting - the CFLAGS variable follows. Note the - +=: + Here is an example of a Makefile respecting + CFLAGS. Note the + +=: CFLAGS+= -Wall -Werror - Here is an example which does not respect the - CFLAGS variable: + Here is an example which does not respect + CFLAGS: CFLAGS= -Wall -Werror - The CFLAGS variable is defined on + CFLAGS is defined on &os; systems in /etc/make.conf. The first - example appends additional flags to the - CFLAGS variable, preserving any system-wide + example appends additional flags to + CFLAGS, preserving any system-wide definitions. The second example clobbers anything previously defined. - You should remove optimization flags from the third party - Makefiles. System + Remove optimization flags from the third party + Makefiles. The system CFLAGS contains system-wide optimization flags. An example from an unmodified Makefile: @@ -315,8 +315,8 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD CFLAGS= -O3 -funroll-loops -DHAVE_SOUND Using system optimization flags, the - Makefile would look similar to the - following example: + Makefile would look similar to this + example: CFLAGS+= -DHAVE_SOUND @@ -343,10 +343,9 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD Feedback - Do send applicable changes/patches to the original - author/maintainer for inclusion in next release of the code. - This will only make your job that much easier for the next - release. + Do send applicable changes and patches to the upstream + maintainer for inclusion in the next release of the code. + This makes updating to the next release that much easier. @@ -376,16 +375,16 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD BROKEN, FORBIDDEN, or IGNORE - In certain cases users should be prevented from installing - a port. To tell a user that a port should not be installed, - there are several make variables that can be - used in a port's Makefile. The value of - the following make variables will be the - reason that is given back to users for why the port refuses to - install itself. Please use the correct make - variable as each make variable conveys radically different - meanings to both users, and to automated systems that depend on - the Makefiles, such as + In certain cases, users must be prevented from installing + a port. There are several variables that can be used in a + port's Makefile to tell the user that the + port cannot be installed. The value of + these make variables will be the + reason that is shown to users for why the port refuses to + install itself. Please use the correct make + variable. Each variable conveys radically different + meanings, both to users and to automated systems that depend on + Makefiles, such as the ports build cluster, FreshPorts, and portsmon. @@ -397,7 +396,7 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD BROKEN is reserved for ports that currently do not compile, install, deinstall, or run - correctly. It should be used for ports where the problem + correctly. Use it for ports where the problem is believed to be temporary. If instructed, the build cluster will still attempt @@ -441,11 +440,11 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD FORBIDDEN is used for ports that contain a security vulnerability or induce grave concern regarding the security of a &os; system with a given port - installed (e.g., a reputably insecure program or a program - that provides easily exploitable services). Ports should - be marked as FORBIDDEN as soon as a + installed (for example, a reputably insecure program or a program + that provides easily exploitable services). Mark ports + as FORBIDDEN as soon as a particular piece of software has a vulnerability and there - is no released upgrade. Ideally ports should be upgraded + is no released upgrade. Ideally upgrade ports as soon as possible when a security vulnerability is discovered so as to reduce the number of vulnerable &os; hosts (we like being known for being secure), however @@ -458,8 +457,8 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD IGNORE is reserved for ports that - should not be built for some other reason. It should be - used for ports where the problem is believed to be + must not be built for some other reason. Use it + for ports where the problem is believed to be structural. The build cluster will not, under any circumstances, build ports marked as IGNORE. For instance, use @@ -497,10 +496,10 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD - If a port should be marked IGNORE + To mark a port as IGNOREd only on certain architectures, there are two other convenience variables that will automatically set - IGNORE for you: + IGNORE: ONLY_FOR_ARCHS and NOT_FOR_ARCHS. Examples: @@ -519,11 +518,10 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD If a port fetches i386 binaries and installs them, - IA32_BINARY_PORT should be set. If - this variable is set, it will be checked whether the - /usr/lib32 directory is available for - IA32 versions of libraries and whether the kernel has IA32 - compatibility compiled in. If one of these two + set IA32_BINARY_PORT. If this variable + is set, /usr/lib32 must be present + for IA32 versions of libraries and the kernel must support + IA32 compatibility. If one of these two dependencies is not satisfied, IGNORE will be set automatically. @@ -533,15 +531,16 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD Implementation Notes - The strings should not be quoted. Also, the wording of - the string should be somewhat different due to the way the - information is shown to the user. Examples: + Do not quote the values of BROKEN, + IGNORE, and related variables. Due to the + way the information is shown to the user, the wording of + messages for each variable differ: BROKEN= fails to link with base -lcrypto IGNORE= unsupported on recent versions - resulting in the following output from + resulting in this output from make describe: ===> foobar-0.1 is marked as broken: fails to link with base -lcrypto. @@ -558,11 +557,11 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD Do remember that BROKEN and FORBIDDEN are to be used as a temporary resort if a port is not working. Permanently broken ports - should be removed from the tree entirely. + will be removed from the tree entirely. When it makes sense to do so, users can be warned about a pending port removal with DEPRECATED and - EXPIRATION_DATE. The former is simply a + EXPIRATION_DATE. The former is a string stating why the port is scheduled for removal; the latter is a string in ISO 8601 format (YYYY-MM-DD). Both will be shown to the user. @@ -621,8 +620,8 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD make index, then has to run the command, further slowing down that process. - Usage of &man.sysctl.8; should always be done with the - SYSCTL variable, as it contains the fully + Only use &man.sysctl.8; through + SYSCTL, as it contains the fully qualified path and can be overridden, if one has such a special need. @@ -631,21 +630,21 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD Rerolling Distfiles Sometimes the authors of software change the content of - released distfiles without changing the file's name. You have - to verify that the changes are official and have been performed + released distfiles without changing the file's name. + Verify that the changes are official and have been performed by the author. It has happened in the past that the distfile was silently altered on the download servers with the intent to cause harm or compromise end user security. Put the old distfile aside, download the new one, unpack - them and compare the content with &man.diff.1;. If you see - nothing suspicious, you can update + them and compare the content with &man.diff.1;. If there is + nothing suspicious, update distinfo. Be sure to summarize the - differences in your PR or commit log, so that other people know - that you have taken care to ensure that nothing bad has + differences in the PR or commit log, so that other people know + that nothing bad has happened. - You might also want to contact the authors of the software + Contact the authors of the software and confirm the changes with them. @@ -653,12 +652,12 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD Avoiding Linuxisms Do not use /proc if there are any - other ways of getting the information, e.g., + other ways of getting the information. For example, setprogname(argv[0]) in - main() and then &man.getprogname.3; if - you want to know your name. + main() and then &man.getprogname.3; + to know the executable name>. - Do not rely on behaviour that is undocumented by + Do not rely on behavior that is undocumented by POSIX. Do not record timestamps in the critical path of the @@ -704,7 +703,7 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD xlink:href="https://wiki.ubuntu.com/DashAsBinSh">here. Check that headers are included in the - POSIX or man page recommended way, e.g., + POSIX or man page recommended way. For example, sys/types.h is often forgotten, which is not as much of a problem for &linux; as it is for &os;. @@ -716,9 +715,9 @@ exec %%LOCALBASE%%/bin/java -jar %%DATAD Miscellanea - The files pkg-descr and - pkg-plist should each be double-checked. - If you are reviewing a port and feel they can be worded better, + Always double-check pkg-descr and + pkg-plist. + If reviewing a port and a better wording can be achieved, do so. Do not copy more copies of the GNU General Public License From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 12:44:46 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 715A876; Tue, 16 Sep 2014 12:44:46 +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 5BC528D7; Tue, 16 Sep 2014 12:44:46 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GCik0U048115; Tue, 16 Sep 2014 12:44:46 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GCikLh048114; Tue, 16 Sep 2014 12:44:46 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409161244.s8GCikLh048114@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Tue, 16 Sep 2014 12:44:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45619 - head/en_US.ISO8859-1/books/porters-handbook/plist 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: Tue, 16 Sep 2014 12:44:46 -0000 Author: mat (ports committer) Date: Tue Sep 16 12:44:45 2014 New Revision: 45619 URL: http://svnweb.freebsd.org/changeset/doc/45619 Log: igor -Ry and some other rewording and fixes. Differential Revision: https://reviews.freebsd.org/D646 Reviewed by: wblock Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/plist/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/plist/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/plist/chapter.xml Tue Sep 16 12:41:02 2014 (r45618) +++ head/en_US.ISO8859-1/books/porters-handbook/plist/chapter.xml Tue Sep 16 12:44:45 2014 (r45619) @@ -19,45 +19,47 @@ need to change their pkg-plist depending on what options they are configured with (or version of perl, in the case of p5- - ports). To make this easy, any instances in the + ports). To make this easy, any instances in pkg-plist of %%OSREL%%, %%PERL_VER%%, and - %%PERL_VERSION%% will be substituted for + %%PERL_VERSION%% will be substituted appropriately. The value of %%OSREL%% is the - numeric revision of the operating system (e.g., + numeric revision of the operating system (for example, 4.9). %%PERL_VERSION%% and %%PERL_VER%% is the full version number - of perl (e.g., 5.8.9). + of perl (for example, 5.8.9). Several other %%VARS%% related to port's documentation files are described in the relevant section. - If you need to make other substitutions, you can set the - PLIST_SUB variable with a list of + To make other substitutions, set + PLIST_SUB with a list of VAR=VALUE pairs and instances of %%VAR%% will be - substituted with VALUE in the + substituted with VALUE in pkg-plist. - For instance, if you have a port that installs many files - in a version-specific subdirectory, you can put something - like + For instance, if a port installs many files + in a version-specific subdirectory, use a placeholder for the + version so that pkg-plist does not have to + be regenerated every time the port is updated. For + example: - OCTAVE_VERSION= 2.0.13 + OCTAVE_VERSION= ${PORTREVISION} PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION} in the Makefile and use %%OCTAVE_VERSION%% wherever the version shows - up in pkg-plist. That way, when you - upgrade the port, you will not have to change dozens (or in some - cases, hundreds) of lines in the + up in pkg-plist. When + the port is upgraded, it will not be necessary to edit dozens (or in some + cases, hundreds) of lines in pkg-plist. - If your port installs files conditionally on the options - set in the port, the usual way of handling it is prefixing the + If files are installed conditionally on the options + set in the port, the usual way of handling it is prefixing pkg-plist lines with a %%OPT%% for lines needed when the option is enabled, or %%NO_OPT%% when the option is @@ -66,13 +68,13 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSI linkend="options_sub"/> for more information. For instance, if there are files that are only installed - when the X11 option is enabled, and the + when the X11 option is enabled, and Makefile has: OPTIONS_DEFINE= X11 OPTIONS_SUB= yes - In the pkg-plist file, put + In pkg-plist, put %%X11%% in front of the lines only being installed when the option is enabled, like this : @@ -83,9 +85,9 @@ OPTIONS_SUB= yes do-install targets, by reading from PLIST and writing to TMPPLIST (default: - WRKDIR/.PLIST.mktmp). So if your port + WRKDIR/.PLIST.mktmp). So if the port builds PLIST on the fly, do so in or before - pre-install. Also, if your port + pre-install. Also, if the port needs to edit the resulting file, do so in post-install to a file named TMPPLIST. @@ -108,13 +110,13 @@ OPTIONS_SUB= yes PLIST_DIRSTRY, respectively. To take effect, PLIST_FILES, PLIST_DIRS, and PLIST_DIRSTRY must be set before - TMPPLIST is written, i.e., in + TMPPLIST is written, that is, in pre-install or earlier. - From time to time, the OPTIONS_SUB - construct is not enough, in those cases, adding a specific - TAG to the PLIST_SUB - variable inside the Makefile with a special + From time to time, using OPTIONS_SUB + is not enough. In those cases, adding a specific + TAG to PLIST_SUB + inside the Makefile with a special value of @comment, makes package tools to ignore the line. For instance, if some files are only installed when the X11 option is on and the @@ -139,8 +141,8 @@ PLIST_SUB+= X11I386="@comment " When being de-installed, A port has to remove empty directories it created. This is usually accomplished by adding @dirrm lines for all directories - that are specifically created by the port. You need to delete - subdirectories before you can delete parent + that are specifically created by the port. Subdirectories + must be deleted before deleting parent directories. : @@ -152,8 +154,8 @@ lib/X11/oneko/sounds/cat.au @dirrm lib/X11/oneko However, sometimes @dirrm will give - you errors because other ports share the same directory. You - can use @dirrmtry to remove only empty + errors because other ports share the same directory. + Use @dirrmtry to remove only empty directories without warning. @dirrmtry share/doc/gimp @@ -169,33 +171,38 @@ lib/X11/oneko/sounds/cat.au Creating Empty Directories Empty directories created during port installation need - special attention. They will not get created when installing - the package, because packages only store the files, and both - pkg add and pkg install - creates directories for them as needed. To make sure the - empty directory is created when installing the package, add - this line to pkg-plist above the - corresponding @dirrm line: + special attention. They must be present when the package + is created. If they are not created by the port code, create + them in the Makefile: + + post-stage: + @${MKDIR} ${STAGEDIR}${PREFIX}/some/directory + + Add the directory to pkg-plist + like any other. For example, if the directory has files + created when the port is used: - @exec mkdir -p %D/share/foo/templates + @dirrmtry some/directory Configuration Files - If your port installs configuration files to + If the port installs configuration files to PREFIX/etc (or elsewhere) do - not simply list them in the + not list them in pkg-plist. That will cause - pkg delete to remove the files carefully + pkg delete to remove files that have been carefully edited by the user, and a re-installation will wipe them out. - Instead, install sample file(s) as - filename.sample, - and for each sample file, add this line to your - pkg-plist. + Instead, install sample files with a + filename.sample + extension. The @sample macro automates this, + see for what it does + exactly. For each sample file, add a line to + pkg-plist: @sample etc/orbit.conf.sample @@ -209,19 +216,19 @@ lib/X11/oneko/sounds/cat.au When a port installs its configuration in a subdirectory - of ${PREFIX}/etc, it should be in + of ${PREFIX}/etc, use ETCDIR, which defaults to ${PREFIX}/etc/${PORTNAME}, it can be overridden in the ports Makefile if there is a convention for the port to use some other directory. The - %%ETCDIR%% macro should be used in its - stead in the pkg-plist file. + %%ETCDIR%% macro will be used in its + stead in pkg-plist. The sample configuration files should always have the .sample suffix. If for some historical - reason you cannot use the standard suffix, you can still use + reason using the standard suffix is not possible, use this construct: @unexec if cmp -s %D/etc/orbit.conf-dist %D/etc/orbit.conf; then rm -f %D/etc/orbit.conf; fi @@ -253,15 +260,15 @@ etc/orbit.conf-dist Dynamic Versus Static Package List A static package list is a package - list which is available in the Ports Collection either as a - pkg-plist file (with or without variable + list which is available in the Ports Collection either as + pkg-plist (with or without variable substitution), or embedded into the Makefile via PLIST_FILES, PLIST_DIRS, and PLIST_DIRSTRY. Even if the contents are auto-generated by a tool or a target in the Makefile before the inclusion into the Ports - Collection by a committer (e.g., using make + Collection by a committer (for example, using make makeplist>), this is still considered a static list, since it is possible to examine it without having to download or compile the distfile. @@ -281,8 +288,8 @@ etc/orbit.conf-dist the package list changes drastically based upon optional features of the port (and thus maintaining a static package list is infeasible), or ports which change the package list based - upon the version of dependent software used (e.g., ports which - generate docs with Javadoc). + upon the version of dependent software used. For example, ports which + generate docs with Javadoc. @@ -290,7 +297,7 @@ etc/orbit.conf-dist First, make sure the port is almost complete, with only pkg-plist missing. Running make - makeplist will show what should be put in + makeplist will show an example for pkg-plist. The output of makeplist must be double checked for correctness as it tries to automatically guess a few things, and @@ -298,12 +305,12 @@ etc/orbit.conf-dist User configuration files should be installed as filename.sample, - as it is described in . The - info/dir file should not be listed and - appropriate install-info lines should be + as it is described in . + info/dir must not be listed and + appropriate install-info lines must be added as noted in the info files section. Any libraries installed by the port - should be listed as specified in the shared libraries section. @@ -412,9 +419,9 @@ etc/orbit.conf-dist commandExecute command as part of - the unpacking process. If command contains any of the - following sequences somewhere in it, they are expanded - inline. For the following examples, assume that + the unpacking process. If command contains any of these + sequences somewhere in it, they are expanded + inline. For these examples, assume that @cwd is set to /usr/local and the last extracted file was bin/emacs. @@ -527,7 +534,7 @@ etc/orbit.conf-dist By default, directories created by a package installation are not deleted when the package is deinstalled. This provides an explicit directory cleanup method. These - directives should appear at the end of the package list. If + directives must appear at the end of the package list. If the directory is not empty a warning is printed, and the directory is not removed. @@ -542,8 +549,8 @@ etc/orbit.conf-dist - - Creating Your Own Keyword + + Creating New Keywords Package list files can be extended by keywords that are defined in the YAML file named keyword.yaml. - The file must contain at least one of the following + The file must contain at least one of the next sections: @@ -713,13 +720,19 @@ post-deinstall: | actions: [file] post-install: | - sample_file="%D/%@" + case "%@" in + /*) sample_file="%@" ;; + *) sample_file="%D/%@" ;; + esac target_file="${sample_file%.sample}" if ! [ -f "${target_file}" ]; then /bin/cp -p "${sample_file}" "${target_file}" fi pre-deinstall: | - sample_file="%D/%@" + case "%@" in + /*) sample_file="%@" ;; + *) sample_file="%D/%@" ;; + esac target_file="${sample_file%.sample}" if cmp -s "${target_file}" "${sample_file}"; then rm -f "${target_file}" From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 13:44:39 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CDE4548C; Tue, 16 Sep 2014 13:44:39 +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 B896DF1C; Tue, 16 Sep 2014 13:44:39 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GDidb5076454; Tue, 16 Sep 2014 13:44:39 GMT (envelope-from lev@FreeBSD.org) Received: (from lev@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GDiduU076451; Tue, 16 Sep 2014 13:44:39 GMT (envelope-from lev@FreeBSD.org) Message-Id: <201409161344.s8GDiduU076451@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: lev set sender to lev@FreeBSD.org using -f From: "Lev A. Serebryakov" Date: Tue, 16 Sep 2014 13:44:39 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45620 - head/share/pgpkeys 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: Tue, 16 Sep 2014 13:44:39 -0000 Author: lev (ports committer) Date: Tue Sep 16 13:44:38 2014 New Revision: 45620 URL: http://svnweb.freebsd.org/changeset/doc/45620 Log: Add my PGP key. Added: head/share/pgpkeys/lev.key (contents, props changed) Modified: head/share/pgpkeys/pgpkeys-developers.xml head/share/pgpkeys/pgpkeys.ent Added: head/share/pgpkeys/lev.key ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/pgpkeys/lev.key Tue Sep 16 13:44:38 2014 (r45620) @@ -0,0 +1,318 @@ + + + +uid Lev Serebryakov +uid Lev Serebryakov +uid Lev Serebryakov +uid Lev Serebryakov +sub 4096R/AE6ABA6A21EFC325 2013-12-01 [expires: 2023-11-29] + +]]> + Modified: head/share/pgpkeys/pgpkeys-developers.xml ============================================================================== --- head/share/pgpkeys/pgpkeys-developers.xml Tue Sep 16 12:44:45 2014 (r45619) +++ head/share/pgpkeys/pgpkeys-developers.xml Tue Sep 16 13:44:38 2014 (r45620) @@ -1711,6 +1711,11 @@ &pgpkey.johans; + + &a.lev.email; + &pgpkey.lev; + + &a.bakul.email; &pgpkey.bakul; Modified: head/share/pgpkeys/pgpkeys.ent ============================================================================== --- head/share/pgpkeys/pgpkeys.ent Tue Sep 16 12:44:45 2014 (r45619) +++ head/share/pgpkeys/pgpkeys.ent Tue Sep 16 13:44:38 2014 (r45620) @@ -238,6 +238,7 @@ + From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 15:50:37 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B54D1848; Tue, 16 Sep 2014 15:50:37 +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 9F5B1DE; Tue, 16 Sep 2014 15:50:37 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GFob1p036138; Tue, 16 Sep 2014 15:50:37 GMT (envelope-from blackend@FreeBSD.org) Received: (from blackend@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GFobxN036137; Tue, 16 Sep 2014 15:50:37 GMT (envelope-from blackend@FreeBSD.org) Message-Id: <201409161550.s8GFobxN036137@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: blackend set sender to blackend@FreeBSD.org using -f From: Marc Fonvieille Date: Tue, 16 Sep 2014 15:50:37 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45621 - head/fr_FR.ISO8859-1/books/handbook/cutting-edge 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: Tue, 16 Sep 2014 15:50:37 -0000 Author: blackend Date: Tue Sep 16 15:50:37 2014 New Revision: 45621 URL: http://svnweb.freebsd.org/changeset/doc/45621 Log: Fix a typo. Submitted by: Lucas Hosseini Modified: head/fr_FR.ISO8859-1/books/handbook/cutting-edge/chapter.xml Modified: head/fr_FR.ISO8859-1/books/handbook/cutting-edge/chapter.xml ============================================================================== --- head/fr_FR.ISO8859-1/books/handbook/cutting-edge/chapter.xml Tue Sep 16 13:44:38 2014 (r45620) +++ head/fr_FR.ISO8859-1/books/handbook/cutting-edge/chapter.xml Tue Sep 16 15:50:37 2014 (r45621) @@ -273,7 +273,7 @@ MergeChanges /etc/ /var/named/etc/Si des correctifs ont été appliqués au noyau le système devra être - redémarré. Si tout c'est bien passé le + redémarré. Si tout s'est bien passé le système est corrigé et freebsd-update pourra être exécuté chaque nuit via un processus From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 16:15:21 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 72F575A3; Tue, 16 Sep 2014 16:15:21 +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 51ED3626; Tue, 16 Sep 2014 16:15:21 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GGFLBA050036; Tue, 16 Sep 2014 16:15:21 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GGFL2w050035; Tue, 16 Sep 2014 16:15:21 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201409161615.s8GGFL2w050035@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Tue, 16 Sep 2014 16:15:21 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45622 - head/de_DE.ISO8859-1/books/handbook 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: Tue, 16 Sep 2014 16:15:21 -0000 Author: bcr Date: Tue Sep 16 16:15:20 2014 New Revision: 45622 URL: http://svnweb.freebsd.org/changeset/doc/45622 Log: Fix umlauts. Submitted by: Bjoern Heidotting Fixed by: iconv(1) Pointy hat to: bcr Obtained from: The FreeBSD German Documentation Project Modified: head/de_DE.ISO8859-1/books/handbook/book.xml Modified: head/de_DE.ISO8859-1/books/handbook/book.xml ============================================================================== --- head/de_DE.ISO8859-1/books/handbook/book.xml Tue Sep 16 15:50:37 2014 (r45621) +++ head/de_DE.ISO8859-1/books/handbook/book.xml Tue Sep 16 16:15:20 2014 (r45622) @@ -94,32 +94,32 @@ Willkommen bei &os;! Dieses Handbuch beschreibt die - Installation und den täglichen Umgang mit &os; + Installation und den täglichen Umgang mit &os; &rel2.current;-RELEASE und &os; &rel.current;-RELEASE. Das Handbuch ist jederzeit unter Bearbeitung und das Ergebnis der Arbeit vieler Einzelpersonen. Dies kann dazu - führen, dass bestimmte Bereiche nicht mehr aktuell sind und - auf den neuesten Stand gebracht werden müssen. Bei + führen, dass bestimmte Bereiche nicht mehr aktuell sind und + auf den neuesten Stand gebracht werden müssen. Bei Unklarheiten empfiehlt es sich daher stets, die englische Originalversion des Handbuchs zu lesen. - Wenn Sie bei der Ãœbersetzung des Handbuchs mithelfen - möchten, senden Sie bitte eine E-Mail an die Mailingliste + Wenn Sie bei der Übersetzung des Handbuchs mithelfen + möchten, senden Sie bitte eine E-Mail an die Mailingliste &a.de.translators;. Die aktuelle Version des Handbuchs ist immer auf dem &os;-Webserver - verfügbar und kann in verschiedenen Formaten und in + verfügbar und kann in verschiedenen Formaten und in komprimierter Form vom &os; FTP-Server oder einem der vielen Spiegel herunter geladen werden - (ältere Versionen finden Sie hingegen unter http://docs.FreeBSD.org/doc/). - Vielleicht möchten Sie das Handbuch aber auch durchsuchen. @@ -131,12 +131,12 @@ Dieser Teil des &os;-Handbuchs richtet sich an Benutzer - und Administratoren für die &os; neu ist. Diese + und Administratoren für die &os; neu ist. Diese Kapitel - geben Ihnen eine Einführung in &os;, + geben Ihnen eine Einführung in &os;, @@ -144,27 +144,27 @@ - erklären Ihnen die Grundlagen + erklären Ihnen die Grundlagen von &unix; Systemen, - zeigen Ihnen, wie Sie die Fülle der erhältlichen + zeigen Ihnen, wie Sie die Fülle der erhältlichen Anwendungen Dritter installieren und - führen Sie in X, der Benutzeroberfläche + führen Sie in X, der Benutzeroberfläche von &unix; Systemen ein. Es wird gezeigt, wie Sie den Desktop konfigurieren, um effektiver arbeiten - zu können. + zu können. - Wir haben uns bemüht, Referenzen auf weiter vorne liegende - Textteile auf ein Minimum zu beschränken, so dass Sie - diesen Teil des Handbuchs ohne viel Blättern durcharbeiten - können. + Wir haben uns bemüht, Referenzen auf weiter vorne liegende + Textteile auf ein Minimum zu beschränken, so dass Sie + diesen Teil des Handbuchs ohne viel Blättern durcharbeiten + können. &chap.introduction; @@ -179,43 +179,43 @@ Oft benutzte Funktionen - Nach den Grundlagen beschäftigt sich das + Nach den Grundlagen beschäftigt sich das &os;-Handbuch mit oft benutzten Funktionen von &os;. Die Kapitel behandeln die nachstehenden Themen: - Zeigen Ihnen beliebte und nützliche - Werkzeuge wie Browser, Büroanwendungen und + Zeigen Ihnen beliebte und nützliche + Werkzeuge wie Browser, Büroanwendungen und Programme zum Anzeigen von Dokumenten. - Zeigen Ihnen Multimedia-Werkzeuge für + Zeigen Ihnen Multimedia-Werkzeuge für &os;. - Erklären den Bau eines angepassten &os;-Kernels, + Erklären den Bau eines angepassten &os;-Kernels, der die Systemfunktionen erweitert. - Beschreiben ausführlich das Drucksystem, - sowohl für direkt angeschlossene Drucker als - auch für Netzwerkdrucker. + Beschreiben ausführlich das Drucksystem, + sowohl für direkt angeschlossene Drucker als + auch für Netzwerkdrucker. - Erläutern, wie Sie Linux-Anwendungen auf einem + Erläutern, wie Sie Linux-Anwendungen auf einem &os;-System laufen lassen. Damit Sie einige Kapitel verstehen, sollten Sie vorher - andere Kapitel gelesen haben. Die Ãœbersicht zu jedem - Kapitel zählt die Voraussetzungen für das + andere Kapitel gelesen haben. Die Übersicht zu jedem + Kapitel zählt die Voraussetzungen für das erolgreiche Durcharbeiten des Kapitels auf. @@ -234,12 +234,12 @@ Systemadministration. Am Anfang jedes Kapitels finden Sie eine Zusammenfassung, die beschreibt, was Sie nach dem Durcharbeiten des Kapitels gelernt haben. Weiterhin werden - die Voraussetzungen beschrieben, die für das Durcharbeiten des + die Voraussetzungen beschrieben, die für das Durcharbeiten des Kapitels erforderlich sind. Diese Kapitel sollten Sie lesen, wenn Sie die - Informationen darin benötigen. Sie brauchen Sie nicht in - einer bestimmten Reihenfolge zu lesen, noch müssen Sie die + Informationen darin benötigen. Sie brauchen Sie nicht in + einer bestimmten Reihenfolge zu lesen, noch müssen Sie die Kapitel lesen, bevor Sie anfangen, &os; zu benutzen. @@ -265,13 +265,13 @@ &os; ist eins der meist benutzten Betriebssysteme - für leistungsfähige Netzwerkserver. Die + für leistungsfähige Netzwerkserver. Die Kapitel in diesem Teil behandeln die nachstehenden Themen: - Serielle Datenübertragung + Serielle Datenübertragung @@ -291,13 +291,13 @@ - Weiterführende Netzwerkthemen + Weiterführende Netzwerkthemen Diese Kapitel sollten Sie lesen, wenn Sie die - Informationen darin benötigen. Sie brauchen Sie nicht - in einer bestimmten Reihenfolge zu lesen, noch müssen Sie die + Informationen darin benötigen. Sie brauchen Sie nicht + in einer bestimmten Reihenfolge zu lesen, noch müssen Sie die Kapitel lesen, bevor Sie anfangen, &os; zu benutzen. From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 16:54:54 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D533B547; Tue, 16 Sep 2014 16:54:54 +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 BF6C3B64; Tue, 16 Sep 2014 16:54:54 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GGssip068709; Tue, 16 Sep 2014 16:54:54 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GGssSr068708; Tue, 16 Sep 2014 16:54:54 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201409161654.s8GGssSr068708@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Tue, 16 Sep 2014 16:54:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45623 - head/de_DE.ISO8859-1/books/handbook/advanced-networking 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: Tue, 16 Sep 2014 16:54:55 -0000 Author: bcr Date: Tue Sep 16 16:54:54 2014 New Revision: 45623 URL: http://svnweb.freebsd.org/changeset/doc/45623 Log: Update to r39207: Correct a few entries that were mistakenly changed which would adversely affect users of 8.x and prior by noting separate rc.conf(5) entries for 8.x and earlier or 9.x and later. Submitted by: Bjoern Heidotting Obtained from: The FreeBSD German Documentation Project Modified: head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml Modified: head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml ============================================================================== --- head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml Tue Sep 16 16:15:20 2014 (r45622) +++ head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml Tue Sep 16 16:54:54 2014 (r45623) @@ -5879,13 +5879,21 @@ rl0: flags=8943<UP,BROADCAST,RUNNING, Rechners, der in Ihrem LAN als Client, aber nicht als Router verwendet wird. Um die Schnittstelle während des Systemstarts mit &man.rtsol.8; automatisch einzurichten, - fügen Sie folgende Zeile in + fügen Sie folgende Zeile für + &os; 9.x (und neuer) in /etc/rc.conf ein: ipv6_prefer="YES" - Durch die folgende Zeile weisen Sie Ihrer Schnittstelle - fxp0 die statische IP-Adresse 2001:471:1f11:251:290:27ff:fee0:2093 + Für &os; 8.x (und älter) + fügen Sie stattdessen folgende Zeile hinzu: + + ipv6_enable="YES" + + Unter &os; 9.x weisen + Sie druch die folgende Zeile Ihrer Schnittstelle + fxp0 die statische IP-Adresse + 2001:471:1f11:251:290:27ff:fee0:2093 zu: ifconfig_fxp0_ipv6="inet6 @@ -5898,6 +5906,11 @@ rl0: flags=8943<UP,BROADCAST,RUNNING, zu ändern, mit dem der Computer vernetzt ist. + Für &os; 8.x fügen + Sie dagegen folgende Zeile hinzu: + + ipv6_ifconfig_fxp0="2001:471:1f11:251:290:27ff:fee0:2093" + Um 2001:471:1f11:251::1 als Standardrouter festzulegen, fügen Sie folgende Zeile in /etc/rc.conf ein: @@ -5929,13 +5942,21 @@ rl0: flags=8943<UP,BROADCAST,RUNNING, gifconfig_gif0="MY_IPv4_ADDR REMOTE_IPv4_ADDR" Um die Ihnen zugewiesene IPv6-Adresse als Endpunkt Ihres - IPv6-Tunnels zu verwenden, fügen Sie folgende Zeile - ein: + IPv6-Tunnels zu verwenden, fügen Sie folgende Zeile für + &os; 9.x (und neuer) + ein: ifconfig_gif0_ipv6="inet6 MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR" + Für &os; 8.x (und älter) + fügen Sie folgende Zeile ein: + + ipv6_ifconfig_gif0=" +MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR" + + Nun müssen Sie nur noch die IPv6-Standardroute angeben. Diese legt das andere Ende des IPv6-Tunnels fest. From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 16:59:51 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5E99B773; Tue, 16 Sep 2014 16:59:51 +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 48DE9C09; Tue, 16 Sep 2014 16:59:51 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GGxpiC069410; Tue, 16 Sep 2014 16:59:51 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GGxp5J069409; Tue, 16 Sep 2014 16:59:51 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201409161659.s8GGxp5J069409@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Tue, 16 Sep 2014 16:59:51 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45624 - head/de_DE.ISO8859-1/books/handbook/network-servers 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: Tue, 16 Sep 2014 16:59:51 -0000 Author: bcr Date: Tue Sep 16 16:59:50 2014 New Revision: 45624 URL: http://svnweb.freebsd.org/changeset/doc/45624 Log: Update to r40525: - The nsupdate(8) man page no longer exists: nsupdate(1) replaces it. Change the reference in the "network servers" Handbook chapter. [1] - Add nsupdate(1) to the man page references file, without removing the old one so that translations don't break. Submitted by: Bjoern Heidotting Obtained from: The FreeBSD German Documentation Project Modified: head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml Tue Sep 16 16:54:54 2014 (r45623) +++ head/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml Tue Sep 16 16:59:50 2014 (r45624) @@ -5,7 +5,7 @@ $FreeBSD$ $FreeBSDde: de-docproj/books/handbook/network-servers/chapter.xml,v 1.103 2011/12/24 15:51:18 bcr Exp $ - basiert auf: r40247 + basiert auf: r40525 --> Netzwerkserver @@ -4599,7 +4599,7 @@ $include Kexample.com.+005+nnnnn.ZSK.key Weitere Informationsquellen Hilfeseiten zu BIND/named: - &man.rndc.8; &man.named.8; &man.named.conf.5; &man.nsupdate.8; + &man.rndc.8; &man.named.8; &man.named.conf.5; &man.nsupdate.1; &man.dnssec-signzone.8; &man.dnssec-keygen.8; From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 19:21:10 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 28060514; Tue, 16 Sep 2014 19:21:10 +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 ED6FBF1A; Tue, 16 Sep 2014 19:21:09 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GJL9fG037087; Tue, 16 Sep 2014 19:21:09 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GJL9lu037086; Tue, 16 Sep 2014 19:21:09 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201409161921.s8GJL9lu037086@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Tue, 16 Sep 2014 19:21:09 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45625 - head/en_US.ISO8859-1/books/porters-handbook/versions 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: Tue, 16 Sep 2014 19:21:10 -0000 Author: gjb Date: Tue Sep 16 19:21:09 2014 New Revision: 45625 URL: http://svnweb.freebsd.org/changeset/doc/45625 Log: Document __FreeBSD_version values 1100034, 1000716, 903504, 804505. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Tue Sep 16 16:59:50 2014 (r45624) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Tue Sep 16 19:21:09 2014 (r45625) @@ -3866,6 +3866,13 @@ + 804505 + September 16, 2014 + 8.4-STABLE after FreeBSD-SA-14:19 + (rev 271668). + + + 900000 August 22, 2009 9.0-CURRENT. @@ -4451,6 +4458,13 @@ + 903504 + September 16, 2014 + 9-STABLE after FreeBSD-SA-14:19 + (rev 271668). + + + 1000000 September 26, 2011 10.0-CURRENT. @@ -5119,6 +5133,13 @@ + 1000716 + September 16, 2014 + 10-STABLE after FreeBSD-SA-14:19 + (rev 271667). + + + 1100000 October 10, 2013 11.0-CURRENT @@ -5371,6 +5392,14 @@ ifa_ifwithroute (rev 271438). + + + 1100034 + September 16, 2014 + 11.0-CURRENT after FreeBSD-SA-14:19.tcp + (rev 271666). + +
    From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 19:29:23 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6891B9CD; Tue, 16 Sep 2014 19:29:23 +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 4EC32F94; Tue, 16 Sep 2014 19:29:23 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GJTNEJ041130; Tue, 16 Sep 2014 19:29:23 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GJTNRv041128; Tue, 16 Sep 2014 19:29:23 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201409161929.s8GJTNRv041128@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Tue, 16 Sep 2014 19:29:23 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45626 - in head/en_US.ISO8859-1/htdocs/releases: 10.0R 9.3R 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: Tue, 16 Sep 2014 19:29:23 -0000 Author: gjb Date: Tue Sep 16 19:29:22 2014 New Revision: 45626 URL: http://svnweb.freebsd.org/changeset/doc/45626 Log: Regen after r271687 Approved by: re (implicit) Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/htdocs/releases/10.0R/errata.html head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html Modified: head/en_US.ISO8859-1/htdocs/releases/10.0R/errata.html ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/10.0R/errata.html Tue Sep 16 19:21:09 2014 (r45625) +++ head/en_US.ISO8859-1/htdocs/releases/10.0R/errata.html Tue Sep 16 19:29:22 2014 (r45626) @@ -1,5 +1,5 @@ -FreeBSD 10.0-RELEASE Errata

    FreeBSD 10.0-RELEASE Errata

    The FreeBSD Project

    FreeBSD 10.0-RELEASE Errata

    The FreeBSD Project

    FreeBSD is a registered trademark of the FreeBSD Foundation.

    Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered @@ -13,7 +13,7 @@ as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the or the - ® symbol.

    Last modified on 2014-09-09 by gjb.
    Abstract

    This document lists errata items for FreeBSD 10.0-RELEASE, + ® symbol.

    Last modified on 2014-09-16 by gjb.
    Abstract

    This document lists errata items for FreeBSD 10.0-RELEASE, containing significant information discovered after the release or too late in the release cycle to be otherwise included in the release documentation. This information @@ -43,7 +43,8 @@ handling

    SA-14:13.pam3 June 2014

    Fix incorrect error handling in PAM policy parser

    SA-14:14.openssl5 June 2014

    Multiple vulnerabilities

    SA-14:15.iconv24 June 2014

    NULL pointer dereference and out-of-bounds array access

    SA-14:16.file24 June 2014

    Multiple vulnerabilities

    SA-14:17.kmem8 July 2014

    Kernel memory disclosure in control messages - and SCTP notifications

    SA-14:18.openssl9 September 2014

    Multiple vulnerabilities

    3. Open Issues

    • FreeBSD/i386 10.0-RELEASE running as a guest + and SCTP notifications

      SA-14:18.openssl9 September 2014

      Multiple vulnerabilities

      SA-14:19.tcp16 September 2014

      Denial of Service in TCP packet + processing.

    3. Open Issues

    • FreeBSD/i386 10.0-RELEASE running as a guest operating system on VirtualBox can have a problem with disk I/O access. It depends on some specific hardware configuration and does not depend on a @@ -107,7 +108,7 @@ boot

      4. Late-Breaking News

      No news.

    This file, and other release-related documents, can be downloaded from http://www.FreeBSD.org/snapshots/.

    For questions about FreeBSD, read the documentation before - contacting <questions@FreeBSD.org>.

    All users of FreeBSD stable should + contacting <questions@FreeBSD.org>.

    All users of FreeBSD 10.0-STABLE should subscribe to the <stable@FreeBSD.org> mailing list.

    For questions about this documentation, e-mail <doc@FreeBSD.org>.

    \ No newline at end of file Modified: head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html Tue Sep 16 19:21:09 2014 (r45625) +++ head/en_US.ISO8859-1/htdocs/releases/9.3R/errata.html Tue Sep 16 19:29:22 2014 (r45626) @@ -1,5 +1,5 @@ -FreeBSD 9.3-RELEASE Errata

    FreeBSD 9.3-RELEASE Errata

    +FreeBSD 9.3-RELEASE Errata

    FreeBSD 9.3-RELEASE Errata

    The FreeBSD Project

    FreeBSD is a registered trademark of the FreeBSD Foundation.

    Intel, Celeron, EtherExpress, i386, @@ -14,7 +14,7 @@ as trademarks. Where those designations appear in this document, and the FreeBSD Project was aware of the trademark claim, the designations have been followed by the or the - ® symbol.

    Last modified on 2014-09-09 by gjb.
    Abstract

    This document lists errata items for FreeBSD 9.3-RELEASE, + ® symbol.

    Last modified on 2014-09-16 by gjb.
    Abstract

    This document lists errata items for FreeBSD 9.3-RELEASE, containing significant information discovered after the release or too late in the release cycle to be otherwise included in the release documentation. @@ -38,7 +38,8 @@ the snapshot).

    For a list of all FreeBSD CERT security advisories, see http://www.FreeBSD.org/security/ or ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/.

    2. Security Advisories

    Problems described in the following security advisories have been fixed in 9.3-RELEASE. For more information, consult the individual advisories available from - http://security.FreeBSD.org/.

    AdvisoryDateTopic
    SA-14:18.openssl9 September 2014

    Multiple vulnerabilities

    3. Late-Breaking News

    No late-breaking news.

    < small>This file, and other release-related documents, + http://security.FreeBSD.org/.

    AdvisoryDateTopic
    SA-14:18.openssl9 September 2014

    Multiple vulnerabilities

    SA-14:19.tcp16 September 2014

    Denial of Service in TCP packet + processing.

    3. Late-Breaking News

    No late-breaking news.

    This file, and other release-related documents, can be downloaded from http://www.FreeBSD.org/releases/.

    For questions about FreeBSD, read the documentation before contacting <questions@FreeBSD.org>.

    All users of FreeBSD 9.3-STABLE should From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 20:12:18 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9A31F776; Tue, 16 Sep 2014 20:12:18 +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 83B856C7; Tue, 16 Sep 2014 20:12:18 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GKCIIS063737; Tue, 16 Sep 2014 20:12:18 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GKCIBo063736; Tue, 16 Sep 2014 20:12:18 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409162012.s8GKCIBo063736@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Tue, 16 Sep 2014 20:12:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45627 - head/en_US.ISO8859-1/books/porters-handbook/makefiles 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: Tue, 16 Sep 2014 20:12:18 -0000 Author: mat (ports committer) Date: Tue Sep 16 20:12:18 2014 New Revision: 45627 URL: http://svnweb.freebsd.org/changeset/doc/45627 Log: igor -Ry and some other rewording and fixes. Differential Revision: https://reviews.freebsd.org/D643 Reviewed by: wblock Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Tue Sep 16 19:29:22 2014 (r45626) +++ head/en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml Tue Sep 16 20:12:18 2014 (r45627) @@ -11,35 +11,34 @@ Configuring the Makefile Configuring the Makefile is pretty - simple, and again we suggest that you look at existing examples + simple, and again we suggest looking at existing examples before starting. Also, there is a sample Makefile in this handbook, so take a look and please follow the ordering of - variables and sections in that template to make your port easier + variables and sections in that template to make the port easier for others to read. - Now, consider the following problems in sequence as you - design your new Makefile: + Consider these problems in sequence during the + design of the new Makefile: The Original Source Does it live in DISTDIR as a standard gzipped tarball named something like - foozolix-1.2.tar.gz? If so, you can go on - to the next step. If not, you should look at overriding any of - the DISTVERSION, DISTNAME, + foozolix-1.2.tar.gz? If so, go on + to the next step. If not, the distribution file format might + require overriding one or more of + DISTVERSION, DISTNAME, EXTRACT_CMD, EXTRACT_BEFORE_ARGS, EXTRACT_AFTER_ARGS, - EXTRACT_SUFX, or DISTFILES - variables, depending on how alien a format your port's - distribution file is. + EXTRACT_SUFX, or + DISTFILES. - In the worst case, you can simply create your own + In the worst case, create a custom do-extract target to override the - default, though this should be rarely, if ever, - necessary. + default. This is rarely, if ever, necessary. @@ -53,17 +52,17 @@ <varname>PORTNAME</varname> and <varname>PORTVERSION</varname> - You should set PORTNAME to the base - name of your port, and PORTVERSION to the + Set PORTNAME to the base + name of the port, and PORTVERSION to the version number of the port. - - Package name should be unique among all of the ports - tree, check that there is not already a port with the same + + The package name must be unique among all of the ports + tree. Make sure that there is not already a port with the same PORTNAME and if there is add one of PKGNAMEPREFIX or PKGNAMESUFFIX. - + @@ -73,24 +72,24 @@ <varname>PORTREVISION</varname> - The PORTREVISION variable is a + PORTREVISION is a monotonically increasing value which is reset to 0 with - every increase of PORTVERSION (i.e., - every time a new official vendor release is made), and - appended to the package name if non-zero. Changes to + every increase of PORTVERSION, typically + every time there is a new official vendor release. If + PORTREVISION is non-zero, the value is + appended to the package name. Changes to PORTREVISION are used by automated tools - (e.g., pkg version, see - &man.pkg-version.8;) to highlight the fact that a new - package is available. + like &man.pkg-version.8; to determine that a new package is + available. - PORTREVISION should be increased each + PORTREVISION must be increased each time a change is made to the port that changes the generated package in any way. That includes changes that only affect a package built with non-default options. Examples of when PORTREVISION - should be bumped: + must be bumped: @@ -107,9 +106,9 @@ Changes in the packing list or the install-time - behavior of the package (e.g., change to a script which - generates initial data for the package, like ssh host - keys). + behavior of the package. For example, a change to a script which + generates initial data for the package, like &man.ssh.1; host + keys. @@ -122,7 +121,7 @@ Silent changes to the port distfile which have - significant functional differences, i.e., changes to the + significant functional differences. For example, changes to the distfile requiring a correction to distinfo with no corresponding change to PORTVERSION, where a @@ -150,30 +149,39 @@ Trivial patches to the distfile such as correction of typos, which are not important enough that users of - the package should go to the trouble of + the package have to go to the trouble of upgrading. Build fixes which cause a package to become - compilable where it was previously failing (as long as + compilable where it was previously failing. As long as the changes do not introduce any functional change on any other platforms on which the port did previously - build). Since PORTREVISION reflects + build. Since PORTREVISION reflects the content of the package, if the package was not previously buildable then there is no need to increase PORTREVISION to mark a change. - A rule of thumb is to ask yourself whether a change - committed to a port is something which everyone would - benefit from having (either because of an enhancement, fix, + A rule of thumb is to decide whether a change + committed to a port is something which some people would + benefit from having. Either because of an enhancement, fix, or by virtue that the new package will actually work at - all), and weigh that against that fact that it will cause + all. Then weigh that against that fact that it will cause everyone who regularly updates their ports tree to be - compelled to update. If yes, the - PORTREVISION should be bumped. + compelled to update. If yes, + PORTREVISION must be bumped. + + + People using binary packages will + never see the update if + PORTREVISION is not bumped. Without + increasing PORTREVISION, the + package builders have no way to detect the change and + thus, will not rebuild the package. + @@ -194,38 +202,38 @@ two version number strings. For example: &prompt.user; pkg version -t 0.031 0.29 -> + > The > output indicates that version 0.031 is considered greater than version 0.29, which may not have been obvious to the porter. - In situations such as this, the - PORTEPOCH version should be increased. + In situations such as this, + PORTEPOCH must be increased. If PORTEPOCH is nonzero it is appended to the package name as described in section 0 above. PORTEPOCH must never be decreased or reset to zero, because that would cause comparison to a - package from an earlier epoch to fail (i.e., the package - would not be detected as out of date): the new version - number (e.g., 1.0,1 in the above example) - is still numerically less than the previous version - (20000801), but the ,1 suffix is treated + package from an earlier epoch to fail. For example, the package + would not be detected as out of date. The new version + number, 1.0,1 in the above + example, is still numerically less than the previous version, + 20000801, but the ,1 suffix is treated specially by automated tools and found to be greater than the implied suffix ,0 on the earlier package. Dropping or resetting PORTEPOCH - incorrectly leads to no end of grief; if you do not - understand the above discussion, please keep after it until - you do, or ask questions on the mailing lists. + incorrectly leads to no end of grief. If the discussion + above was not clear enough, please consult the + &a.ports;. It is expected that PORTEPOCH will not be used for the majority of ports, and that sensible use of PORTVERSION can often preempt it becoming necessary if a future release of the software - should change the version structure. However, care is + changes the version structure. However, care is needed by &os; porters when a vendor release is made without an official version number — such as a code snapshot release. The temptation is to label @@ -234,11 +242,14 @@ release is made. For example, if a snapshot release is made on the date - 20000917, and the previous version of the software was - version 1.2, the snapshot release should be given a - PORTVERSION of 1.2.20000917 or similar, - not 20000917, so that the succeeding release, say 1.3, is - still a numerically greater value. + 20000917, and the previous version of the software was + version 1.2, do not use + 20000917 for + PORTVERSION. The correct way is a + PORTVERSION of + 1.2.20000917, or similar, so that the + succeeding release, say 1.3, is still a + numerically greater value. @@ -250,7 +261,7 @@ collection: PORTNAME= gtkmumble -PORTVERSION= 0.10 + PORTVERSION= 0.10 PKGNAME becomes gtkmumble-0.10. @@ -260,8 +271,8 @@ PORTVERSION= 0.10 accordingly. PORTNAME= gtkmumble -PORTVERSION= 0.10 -PORTREVISION= 1 + PORTVERSION= 0.10 + PORTREVISION= 1 PKGNAME becomes gtkmumble-0.10_1 @@ -270,9 +281,9 @@ PORTREVISION= 1 0.2 (it turns out the author actually intended 0.10 to actually mean 0.1.0, not what comes after - 0.9 - oops, too late now). Since the new minor + 0.9 - oops, too late now). Since the new minor version 2 is numerically less than the - previous version 10, the + previous version 10, PORTEPOCH must be bumped to manually force the new package to be detected as newer. Since it is a new vendor release of @@ -280,8 +291,8 @@ PORTREVISION= 1 removed from the Makefile). PORTNAME= gtkmumble -PORTVERSION= 0.2 -PORTEPOCH= 1 + PORTVERSION= 0.2 + PORTEPOCH= 1 PKGNAME becomes gtkmumble-0.2,1 @@ -291,8 +302,8 @@ PORTEPOCH= 1 variables are now: PORTNAME= gtkmumble -PORTVERSION= 0.3 -PORTEPOCH= 1 + PORTVERSION= 0.3 + PORTEPOCH= 1 PKGNAME becomes gtkmumble-0.3,1 @@ -321,9 +332,10 @@ PORTEPOCH= 1 ${PKGNAMEPREFIX}${PORTNAME}${PKGNAMESUFFIX}-${PORTVERSION}. Make sure this conforms to our guidelines for a good - package name. In particular, you are - not allowed to use a hyphen - (-) in PORTVERSION. + package name. In particular, the use of a + hyphen (-) in + PORTVERSION is not + allowed. Also, if the package name has the language- or the -compiled.specifics part (see @@ -370,8 +382,7 @@ PORTEPOCH= 1 French. The language- part is - set in the PKGNAMEPREFIX - variable. + set in PKGNAMEPREFIX. @@ -379,34 +390,30 @@ PORTEPOCH= 1 name - The first letter of the name - part should be lowercase. (The rest of the name may - contain capital letters, so use your own discretion when - converting a software name that has some capital letters - in it.) There is a tradition of naming - Perl 5 modules by prepending - p5- and converting the double-colon - separator to a hyphen. For example, the - Data::Dumper module becomes - p5-Data-Dumper. - Make sure that the port's name and version are - clearly separated and placed into the + clearly separated and placed into PORTNAME and - PORTVERSION variables. The only + PORTVERSION. The only reason for PORTNAME to contain a version part is if the upstream distribution is really named that way, as in the - textproc/libxml2 or - japanese/kinput2-freewnn ports. - Otherwise, the PORTNAME should not + textproc/libxml2 or + japanese/kinput2-freewnn ports. + Otherwise, PORTNAME cannot contain any version-specific information. It is quite normal for several ports to have the same PORTNAME, as the - www/apache* ports do; in that case, + www/apache* ports do; in that case, different versions (and different index entries) are - distinguished by the PKGNAMEPREFIX + distinguished by PKGNAMEPREFIX and PKGNAMESUFFIX values. + + There is a tradition of naming + Perl 5 modules by prepending + p5- and converting the double-colon + separator to a hyphen. For example, the + Data::Dumper module becomes + p5-Data-Dumper. @@ -419,13 +426,12 @@ PORTEPOCH= 1 (usually part of the directory name in a family of ports), the -compiled.specifics part - should state the compiled-in defaults (the hyphen is - optional). Examples are paper size and font + states the compiled-in defaults. The hyphen is + optional. Examples are paper size and font units. The -compiled.specifics - part is set in the PKGNAMESUFFIX - variable. + part is set in PKGNAMESUFFIX. @@ -446,9 +452,9 @@ PORTEPOCH= 1 beta, rc, or pre, take the first letter and put it immediately after a period. If the version string - continues after those names, the numbers should follow + continues after those names, the numbers follow the single alphabet without an extra period between - them. + them (for example, 1.0b2). The idea is to make it easier to sort ports by looking at the version string. In particular, make sure @@ -461,26 +467,28 @@ PORTEPOCH= 1 yy.mm.dd format. It is important to prefix the version with 0.0. in case a release with an actual - version number is made, which would of course be + version number is made, which would be numerically less than yyyy. - + Package name must be unique among all of the ports tree, check that there is not already a port with the same PORTNAME and if there is add one of PKGNAMEPREFIX or PKGNAMESUFFIX. - + Here are some (real) examples on how to convert the name as called by the software authors to a suitable package name: - + + Package Naming Examples + @@ -504,6 +512,15 @@ PORTEPOCH= 1 + mule-1.0.1 + (empty) + mule + 1 + 1.0.1 + mule already exists + + + EmiClock-1.0.2 (empty) emiclock @@ -608,14 +625,15 @@ PORTEPOCH= 1 - +
    If there is absolutely no trace of version information in the original source and it is unlikely that the original author will ever release another version, just set the version string to 1.0 (like the piewm example above). Otherwise, ask the - original author or use the date string + original author or use the date string the source file was + released on (0.0.yyyy.mm.dd) as the version. @@ -637,12 +655,12 @@ PORTEPOCH= 1 packages on the FTP site or the CDROM. Please take a look at the current list of categories and pick the ones that are suitable for - your port. + the port. This list also determines where in the ports tree the port - is imported. If you put more than one category here, it is - assumed that the port files will be put in the subdirectory - with the name in the first category. See + is imported. If there is more than one category here, + the port files must be put in the subdirectory + with the name of the first category. See below for more discussion about how to pick the right categories. @@ -658,8 +676,8 @@ PORTEPOCH= 1 purposes. - For non-virtual categories, you will find a one-line - description in the COMMENT in that + For non-virtual categories, there is a one-line + description in COMMENT in that subdirectory's Makefile. @@ -740,7 +758,7 @@ PORTEPOCH= 1 comms Communication software. - Mostly software to talk to your serial + Mostly software to talk to the serial port. @@ -767,9 +785,9 @@ PORTEPOCH= 1 devel Development utilities. Do not put libraries here just because they are - libraries—unless they truly do not belong - anywhere else, they should not be in this - category. + libraries. They should not be + in this category unless they truly do not belong + anywhere else. @@ -788,8 +806,10 @@ PORTEPOCH= 1 editors General editors. Specialized editors go in the section for those - tools (e.g., a mathematical-formula editor will go - in math). + tools. For example, a mathematical-formula editor will + go in math, and have + editors as a second + category. @@ -802,7 +822,7 @@ PORTEPOCH= 1 emulators Emulators for other operating systems. Terminal emulators do not - belong here—X-based ones should go to + belong here. X-based ones go to x11 and text-based ones to either comms or misc, depending on the exact @@ -824,8 +844,8 @@ PORTEPOCH= 1 ftp - FTP client and server utilities. - If your port speaks both FTP and HTTP, put it + FTP client and server utilities. + If the port speaks both FTP and HTTP, put it in ftp with a secondary category of www. @@ -984,10 +1004,10 @@ PORTEPOCH= 1 misc Miscellaneous utilities - Basically things that do not belong anywhere + Things that do not belong anywhere else. If at all possible, try to find a better - category for your port than misc, - as ports tend to get overlooked in here. + category for the port than misc, + as ports tend to be overlooked in here. @@ -1212,7 +1232,7 @@ PORTEPOCH= 1 The X Window System and friends. This category is only for software that directly supports the window system. Do not put regular X - applications here; most of them should go into other + applications here. Most of them go into other x11-* categories (see below). @@ -1288,9 +1308,9 @@ PORTEPOCH= 1 Choosing the Right Category - As many of the categories overlap, you often have to - choose which of the categories should be the primary category - of your port. There are several rules that govern this issue. + As many of the categories overlap, choosing which of the + categories will be the primary category of the port can be + tedious. There are several rules that govern this issue. Here is the list of priorities, in decreasing order of precedence: @@ -1305,16 +1325,16 @@ PORTEPOCH= 1 Language specific categories always come first. For - example, if your port installs Japanese X11 fonts, then - your CATEGORIES line would read + example, if the port installs Japanese X11 fonts, then + the CATEGORIES line would read japanese x11-fonts. Specific categories are listed before less-specific - ones. For instance, an HTML editor should be listed as + ones. For instance, an HTML editor is listed as www editors, not the other way - around. Also, you should not list + around. Also, do not list net when the port belongs to any of irc, mail, news, security, @@ -1325,49 +1345,50 @@ PORTEPOCH= 1 x11 is used as a secondary category only when the primary category is a natural - language. In particular, you should not put + language. In particular, do not put x11 in the category line for X applications. - Emacs modes should be + Emacs modes are placed in the same ports category as the application supported by the mode, not in editors. For example, an Emacs mode to edit source files - of some programming language should go into + of some programming language goes into lang. - Ports which install loadable kernel modules should + Ports installing loadable kernel modules also have the virtual category kld in their CATEGORIES line. This is one of the things handled automatically by adding - kmod to the USES - line. + USES=kmod. - misc should not appear with any - other non-virtual category. If you have - misc with something else in your - CATEGORIES line, that means you can - safely delete misc and just put the - port in that other subdirectory! + misc does not appear with any + other non-virtual category. If there is + misc with something else in + CATEGORIES, that means + misc can safely be deleted and the port + placed only in the other subdirectory. - If your port truly does not belong anywhere else, + If the port truly does not belong anywhere else, put it in misc. - If you are not sure about the category, please put a - comment to that effect in your &man.send-pr.1; submission so - we can discuss it before we import it. If you are a - committer, send a note to the &a.ports; so we can discuss it + If the category is not clearly defined, please put a + comment to that effect in the port + submission in the bug database so + we can discuss it before we import it. As a committer, + send a note to the &a.ports; so we can discuss it first. Too often, new ports are imported to the wrong category only to be moved right away. This causes unnecessary and undesirable bloat in the master source repository. @@ -1381,9 +1402,9 @@ PORTEPOCH= 1 virtual categories—those that do not have a corresponding subdirectory in the ports tree— or physical categories—those that - do. The following text discusses the issues involved in - creating a new physical category so that you can understand - them before you propose one. + do. This section discusses the issues involved in creating a + new physical category. Read it thouroughly before proposing a + new one. Our existing practice has been to avoid creating a new physical category unless either a large number of ports would @@ -1407,15 +1428,15 @@ PORTEPOCH= 1 - Propose the new category on &a.ports;. You should - include a detailed rationale for the new category, - including why you feel the existing categories are not + Propose the new category on &a.ports;. Include + a detailed rationale for the new category, + including why the existing categories are not sufficient, and the list of existing ports proposed to move. (If there are new ports pending in - GNATS that would fit this + Bugzilla that would fit this category, list them too.) If you are the maintainer and/or submitter, respectively, mention that as it may - help you to make your case. + help the case. @@ -1423,10 +1444,10 @@ PORTEPOCH= 1 - If it seems that there is support for your idea, file + If it seems that there is support for the idea, file a PR which includes both the rationale and the list of existing ports that need to be moved. Ideally, this PR - should also include patches for the following: + would also include these patches: @@ -1450,7 +1471,7 @@ PORTEPOCH= 1 - (for extra credit, you can include the other files + (for extra credit, include the other files that have to change, as per the procedure in the Committer's Guide.) @@ -1459,9 +1480,9 @@ PORTEPOCH= 1 Since it affects the ports infrastructure and involves - not only performing repo-copies but also possibly running - regression tests on the build cluster, the PR should be - assigned to the &a.portmgr;. + moving and patching many ports but also possibly running + regression tests on the build cluster, assign the PR to + the &a.portmgr;. @@ -1472,10 +1493,10 @@ PORTEPOCH= 1 - Proposing a new virtual category should be similar to the + Proposing a new virtual category is similar to the above but much less involved, since no ports will actually have to move. In this case, the only patches to include in - the PR would be those to add the new category to the + the PR would be those to add the new category to CATEGORIES of the affected ports. @@ -1489,8 +1510,8 @@ PORTEPOCH= 1 effort involved to retrofit the entire existing ports collection with any kind of reorganization is daunting to say the very least. Please read the history of these proposals in - the mailing list archives before you post this idea; - furthermore, you should be prepared to be challenged to offer + the mailing list archives before posting this idea. + Furthermore, be prepared to be challenged to offer a working prototype.
    @@ -1499,8 +1520,8 @@ PORTEPOCH= 1 The Distribution Files The second part of the Makefile - describes the files that must be downloaded in order to build - the port, and where they can be downloaded from. + describes the files that must be downloaded to build + the port, and where they can be downloaded. <varname>DISTVERSION/DISTNAME</varname> @@ -1528,9 +1549,9 @@ PORTEPOCH= 1 Only one of PORTVERSION and - DISTVERSION can be set at a time. If you - set DISTVERSION and the derived - PORTVERSION is not right, do not use + DISTVERSION can be set at a time. If + DISTVERSION does not derive a correct + PORTVERSION, do not use DISTVERSION, set PORTVERSION to the right value and set DISTNAME with PORTNAME @@ -1539,11 +1560,11 @@ PORTEPOCH= 1 version. - The following table lists some examples of - DISTVERSION and the derived - PORTVERSION: - + + Examples of <varname>DISTVERSION</varname> and the + Derived <varname>PORTVERSION</varname> + @@ -1574,19 +1595,19 @@ PORTEPOCH= 1 - +
    PKGNAMEPREFIX and PKGNAMESUFFIX do not affect DISTNAME. Also note that if WRKSRC is equal to - work/${DISTNAME} while + ${WRKDIR}/${DISTNAME} while the original source archive is named something other than ${PORTNAME}-${PORTVERSION}${EXTRACT_SUFX}, - you should probably leave DISTNAME - alone— you are better off defining - DISTFILES than having to set both + leave DISTNAME + alone— defining only + DISTFILES is easier than both DISTNAME and WRKSRC (and possibly EXTRACT_SUFX). @@ -1604,7 +1625,7 @@ PORTEPOCH= 1 FETCH if they cannot find it already on the system. - It is recommended that you put multiple sites on this + It is recommended that multiple sites are included on this list, preferably from different continents. This will safeguard against wide-area network problems. We are even planning to add support for automatically determining the @@ -1612,20 +1633,20 @@ PORTEPOCH= 1 sites will go a long way towards helping this effort. If the original tarball is part of one of the popular - archives such as SourceForge, GNU, or Perl CPAN, you may be - able refer to those sites in an easy compact form using - predefined macros (e.g., SF, - GNU or CPAN). Simply - set MASTER_SITES to one of these values. + archives such as SourceForge, GNU, or Perl CPAN, it may be + possible refer to those sites in an easy compact form using + predefined macros (for example, SF, + GNU or CPAN). + Set MASTER_SITES to one of these values. Here is an example: MASTER_SITES= GNU/make - Or you can use the older expanded format, though there - really are no reason to do so: + The older expanded format can still be used, although there + really is no reason to do so: MASTER_SITES= ${MASTER_SITE_GNU} -MASTER_SITE_SUBDIR= make + MASTER_SITE_SUBDIR= make These values and variables are defined in /usr/ports/Mk/bsd.sites.mk. There are @@ -1635,7 +1656,7 @@ MASTER_SITE_SUBDIR= makeSeveral magic macros exist for popular sites with a predictable directory structure. For these, just use the abbreviation and the system will try to - guess the correct subdirectory for you. + guess the correct subdirectory automatically. MASTER_SITES= SF @@ -1647,7 +1668,7 @@ MASTER_SITE_SUBDIR= makeThis can also be written as MASTER_SITES= SF -MASTER_SITE_SUBDIR= stardict/WyabdcRealPeopleTTS/${PORTVERSION} + MASTER_SITE_SUBDIR= stardict/WyabdcRealPeopleTTS/${PORTVERSION} Popular Magic <varname>MASTER_SITES</varname> @@ -1828,11 +1849,11 @@ MASTER_SITE_SUBDIR= stardict/WyabdcRealP this (slightly stripped for the example):</para> <programlisting>PORTNAME= pkg -PORTVERSION= 1.2.7 + PORTVERSION= 1.2.7 -USE_GITHUB= yes -GH_ACCOUNT= freebsd -GH_COMMIT= f53e577</programlisting> + USE_GITHUB= yes + GH_ACCOUNT= freebsd + GH_COMMIT= f53e577</programlisting> <para>It will automatically have <varname>MASTER_SITES</varname> set to <literal>GH @@ -1852,13 +1873,13 @@ GH_COMMIT= f53e577</programlisting> this (slightly stripped for the example):</para> <programlisting>PORTNAME= pkg-devel -PORTVERSION= 1.3.0.a.20140411 + PORTVERSION= 1.3.0.a.20140411 -USE_GITHUB= yes -GH_ACCOUNT= freebsd -GH_PROJECT= pkg -GH_TAGNAME= ${GH_COMMIT} -GH_COMMIT= 6dbb17b</programlisting> + USE_GITHUB= yes + GH_ACCOUNT= freebsd + GH_PROJECT= pkg + GH_TAGNAME= ${GH_COMMIT} + GH_COMMIT= 6dbb17b</programlisting> <para>It will automatically have <varname>MASTER_SITES</varname> set to <literal>GH @@ -1872,16 +1893,16 @@ GH_COMMIT= 6dbb17b</programlisting> <sect2 xml:id="makefile-extract_sufx"> <title><varname>EXTRACT_SUFX</varname> - If you have one distribution file, and it uses an odd + If there is one distribution file, and it uses an odd suffix to indicate the compression mechanism, set EXTRACT_SUFX. For example, if the distribution file was named foo.tar.gzip instead of the more normal - foo.tar.gz, you would write: + foo.tar.gz, write:DISTNAME= foo -EXTRACT_SUFX= .tar.gzip + EXTRACT_SUFX= .tar.gzipThe USES=tar[:xxx], @@ -1893,9 +1914,8 @@ EXTRACT_SUFX= .tar.gzip .tar.gz. - You never need to set both - EXTRACT_SUFX and - DISTFILES. + As EXTRACT_SUFX is only used in + DISTFILES, only set one of them.. @@ -1929,11 +1949,11 @@ EXTRACT_SUFX= .tar.gzipEXTRACT_ONLY.DISTFILES= source.tar.gz manual.html -EXTRACT_ONLY= source.tar.gz + EXTRACT_ONLY= source.tar.gz - If none of the - DISTFILES should be uncompressed then set - EXTRACT_ONLY to the empty string. + When none of the DISTFILES need to be + uncompressed, set EXTRACT_ONLY to the empty + string.EXTRACT_ONLY= @@ -1941,14 +1961,14 @@ EXTRACT_ONLY= source.tar.gz<varname>PATCHFILES</varname> - If your port requires some additional patches that are - available by FTP or HTTP, set PATCHFILES to + If the port requires some additional patches that are + available by FTP or HTTP, set PATCHFILES to the names of the files and PATCH_SITES to the URL of the directory that contains them (the format is the same as MASTER_SITES). If the patch is not relative to the top of the source tree - (i.e., WRKSRC) because it contains some + (that is, WRKSRC) because it contains some extra pathnames, set PATCH_DIST_STRIP accordingly. For instance, if all the pathnames in the patch have an extra foozolix-1.0/ in front of the @@ -1961,16 +1981,16 @@ EXTRACT_ONLY= source.tar.gz.bz2 or .xz. *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@FreeBSD.ORG Tue Sep 16 22:17:03 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9D8C7432; Tue, 16 Sep 2014 22:17:03 +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 892B63DD; Tue, 16 Sep 2014 22:17:03 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8GMH3Gt021477; Tue, 16 Sep 2014 22:17:03 GMT (envelope-from gavin@FreeBSD.org) Received: (from gavin@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8GMH3oR021476; Tue, 16 Sep 2014 22:17:03 GMT (envelope-from gavin@FreeBSD.org) Message-Id: <201409162217.s8GMH3oR021476@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gavin set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson Date: Tue, 16 Sep 2014 22:17:03 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45628 - head/en_US.ISO8859-1/books/handbook/security 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: Tue, 16 Sep 2014 22:17:03 -0000 Author: gavin Date: Tue Sep 16 22:17:03 2014 New Revision: 45628 URL: http://svnweb.freebsd.org/changeset/doc/45628 Log: Clarify that only 10.0-RELEASE and above can automatically generate certificates for Sendmail at the moment. Modified: head/en_US.ISO8859-1/books/handbook/security/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/security/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/security/chapter.xml Tue Sep 16 20:12:18 2014 (r45627) +++ head/en_US.ISO8859-1/books/handbook/security/chapter.xml Tue Sep 16 22:17:03 2014 (r45628) @@ -1968,7 +1968,9 @@ Email Address []: - To configure Sendmail, add the + In &os; 10.0-RELEASE and above, it is possible to create + a self-signed certificate for Sendmail + automatically. To enable this, add the following lines to /etc/rc.conf: From owner-svn-doc-all@FreeBSD.ORG Wed Sep 17 08:38:33 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id B900378C; Wed, 17 Sep 2014 08:38:33 +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 A386ECC4; Wed, 17 Sep 2014 08:38:33 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8H8cXoY011190; Wed, 17 Sep 2014 08:38:33 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8H8cXCA011188; Wed, 17 Sep 2014 08:38:33 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409170838.s8H8cXCA011188@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Wed, 17 Sep 2014 08:38:33 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45629 - in head/en_US.ISO8859-1: books/porters-handbook/special htdocs/gnome/docs 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: Wed, 17 Sep 2014 08:38:33 -0000 Author: mat (ports committer) Date: Wed Sep 17 08:38:32 2014 New Revision: 45629 URL: http://svnweb.freebsd.org/changeset/doc/45629 Log: Update the USE_AUTOTOOLS/USE_GNOME as of r368357 of the ports tree. Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml head/en_US.ISO8859-1/htdocs/gnome/docs/porting.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml Tue Sep 16 22:17:03 2014 (r45628) +++ head/en_US.ISO8859-1/books/porters-handbook/special/chapter.xml Wed Sep 17 08:38:32 2014 (r45629) @@ -783,9 +783,8 @@ CMAKE_SOURCE_PATH= ${WRKSRC}/subp At the time of writing, tool can be one of autoconf, autoheader, automake, - aclocal, libtool - (deprecated), libtoolize, - libltdl. It can also be one the older + aclocal, libtoolize. + It can also be one the older legacy of autoconf213, autoheader213, automake14, @@ -803,12 +802,11 @@ CMAKE_SOURCE_PATH= ${WRKSRC}/subp - <command>libtool</command> + <command>libtool</command> and <command>libtoolize</command> - The use of USE_AUTOTOOLS=libtool is - deprecated. Now all ports that ship with their own copy of - libtool (search for a file named ltmain.sh) need to have - USES=libtool. Also, if a port has + Ports shipping with their own copy of libtool (search for + a file named ltmain.sh) need to have + USES=libtool. If a port has USE_AUTOTOOLS=libtoolize it probably also needs USES=libtool. See the USES=libtool section in - <command>libltdl</command> + <filename>libltdl.so</filename> - Some ports make use of the libltdl + Some ports make use of the libltdl.so library package, which is part of the libtool suite. Use of this library does not automatically necessitate the use of - libtool itself, so a separate construct - is provided. + libtool itself. If the port needs + libltdl.so, add a dependency on + it: - USE_AUTOTOOLS= libltdl - - Currently, all this does is to bring in a - LIB_DEPENDS on the appropriate - libltdl port, and is provided as a - convenience function to help eliminate any dependencies on - the autotools ports outside of the - USE_AUTOTOOLS framework. There are no - optional operations for this tool. + LIB_DEPENDS= libltdl.so:${PORTSDIR}/devel/libltdl Modified: head/en_US.ISO8859-1/htdocs/gnome/docs/porting.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/gnome/docs/porting.xml Tue Sep 16 22:17:03 2014 (r45628) +++ head/en_US.ISO8859-1/htdocs/gnome/docs/porting.xml Wed Sep 17 08:38:32 2014 (r45629) @@ -332,13 +332,7 @@ GCONF_SCHEMAS= CDDB-Slave2.schemas gnome They also use the GNU configure system. If your port installs shared libraries, and includes an ltmain.sh script in its ${WRKSRC} directory, you should add - USE_AUTOTOOLS="libtool":15 to your port's Makefile. - However, if your port uses custom LIBTOOLFLAGS, you - must use USE_AUTOTOOLS="libtool":13:inc instead. If you have - to use libtool:X:inc, you must also add - lthack to USE_GNOME. In general, though, - lthack is deprecated, and should only be used if - absolutely necessary.

    + USES=libtool to your port's Makefile.

    From owner-svn-doc-all@FreeBSD.ORG Wed Sep 17 09:14:57 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D387F59B; Wed, 17 Sep 2014 09:14:57 +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 BE3AE17B; Wed, 17 Sep 2014 09:14:57 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8H9EveF029480; Wed, 17 Sep 2014 09:14:57 GMT (envelope-from dumbbell@FreeBSD.org) Received: (from dumbbell@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8H9EvPQ029479; Wed, 17 Sep 2014 09:14:57 GMT (envelope-from dumbbell@FreeBSD.org) Message-Id: <201409170914.s8H9EvPQ029479@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: dumbbell set sender to dumbbell@FreeBSD.org using -f From: Jean-Sebastien Pedron Date: Wed, 17 Sep 2014 09:14:57 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45630 - head/en_US.ISO8859-1/books/porters-handbook/versions 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: Wed, 17 Sep 2014 09:14:57 -0000 Author: dumbbell (src committer) Date: Wed Sep 17 09:14:57 2014 New Revision: 45630 URL: http://svnweb.freebsd.org/changeset/doc/45630 Log: Document __FreeBSD_version value 1100035 Tested by: mat@ Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Wed Sep 17 08:38:32 2014 (r45629) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Wed Sep 17 09:14:57 2014 (r45630) @@ -5400,6 +5400,13 @@ (rev 271666). + + 1100035 + September 17, 2014 + 11.0-CURRENT after i915 HW context support + (rev 271705). + +
    From owner-svn-doc-all@FreeBSD.ORG Wed Sep 17 18:57:46 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 8A966C92; Wed, 17 Sep 2014 18:57:46 +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 6AB9A95E; Wed, 17 Sep 2014 18:57:46 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8HIvkCi011728; Wed, 17 Sep 2014 18:57:46 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8HIvkRH011727; Wed, 17 Sep 2014 18:57:46 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201409171857.s8HIvkRH011727@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Wed, 17 Sep 2014 18:57:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45631 - head/de_DE.ISO8859-1/books/handbook/advanced-networking 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: Wed, 17 Sep 2014 18:57:46 -0000 Author: bcr Date: Wed Sep 17 18:57:45 2014 New Revision: 45631 URL: http://svnweb.freebsd.org/changeset/doc/45631 Log: Put in the missing revision r40792: Prefer the use of service(1) to explicit invocation of /etc/rc.d scripts: service(1) puts things in one place and abstracts them. Also, it's less typing and easier to autocomplete. Submitted by: Bjoern Heidotting Obtained from: The FreeBSD German Documentation Project Modified: head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml Modified: head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml ============================================================================== --- head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml Wed Sep 17 09:14:57 2014 (r45630) +++ head/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml Wed Sep 17 18:57:45 2014 (r45631) @@ -1376,7 +1376,7 @@ ifconfig_wlan0="DHCP" Nun können Sie Ihr drahtloses Gerät starten: - &prompt.root; /etc/rc.d/netif start + &prompt.root; service netif start Nachdem Sie das Gerät aktiviert haben, können Sie mit ifconfig den @@ -1512,7 +1512,7 @@ ifconfig_wlan0="WPA DHCP"Nun können Sie Ihr Netzgerät aktivieren: - &prompt.root; /etc/rc.d/netif start + &prompt.root; service netif start Starting wpa_supplicant. DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 5 DHCPDISCOVER on wlan0 to 255.255.255.255 port 67 interval 6 @@ -1715,10 +1715,9 @@ wlan0: flags=8843<UP,BROADCAST,RUNNIN ifconfig_wlan0="WPA DHCP" Nun können Sie Ihr drahtloses Gerät - über das rc.d-System aktivieren: - &prompt.root; /etc/rc.d/netif start + &prompt.root; service netif start Starting wpa_supplicant. DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 7 DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 15 @@ -1815,7 +1814,7 @@ ifconfig_wlan0="WPA DHCP"Nun können Sie Ihr drahtloses Gerät aktivieren: - &prompt.root; /etc/rc.d/netif start + &prompt.root; service netif start Starting wpa_supplicant. DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 7 DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 15 @@ -1930,7 +1929,7 @@ wlan0: flags=8843<UP,BROADCAST,RUNNIN Zuletzt müssen Sie die Netzwerkkarte noch aktivieren: - &prompt.root; /etc/rc.d/netif start + &prompt.root; service netif start Starting wpa_supplicant. DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 7 DHCPREQUEST on wlan0 to 255.255.255.255 port 67 interval 15 @@ -2328,7 +2327,7 @@ wpa_pairwise=CCMP TKIP List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2014 19:03:36 -0000 Author: bcr Date: Wed Sep 17 19:03:36 2014 New Revision: 45632 URL: http://svnweb.freebsd.org/changeset/doc/45632 Log: Update to r41816: XFree86 4.x is hardly modern. Submitted by: Bjoern Heidotting Approved by: The FreeBSD German Documentation Project Modified: head/de_DE.ISO8859-1/books/handbook/preface/preface.xml Modified: head/de_DE.ISO8859-1/books/handbook/preface/preface.xml ============================================================================== --- head/de_DE.ISO8859-1/books/handbook/preface/preface.xml Wed Sep 17 18:57:45 2014 (r45631) +++ head/de_DE.ISO8859-1/books/handbook/preface/preface.xml Wed Sep 17 19:03:36 2014 (r45632) @@ -5,7 +5,7 @@ $FreeBSD$ $FreeBSDde: de-docproj/books/handbook/preface/preface.xml,v 1.36 2011/12/24 13:06:39 bcr Exp $ - basiert auf: 1.50 + basiert auf: r41816 --> Vorwort @@ -216,9 +216,9 @@ (Das X Window System) wurde neu geschrieben. Der Schwerpunkt liegt auf modernen - Benutzeroberflächen unter &xfree86; 4.X wie + Benutzeroberflächen wie KDE und - GNOME. + GNOME unter &xorg;. From owner-svn-doc-all@FreeBSD.ORG Wed Sep 17 23:13:48 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5536C51A; Wed, 17 Sep 2014 23:13:48 +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 40D1E80F; Wed, 17 Sep 2014 23:13:48 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8HNDmCN036603; Wed, 17 Sep 2014 23:13:48 GMT (envelope-from gavin@FreeBSD.org) Received: (from gavin@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8HNDmMO036602; Wed, 17 Sep 2014 23:13:48 GMT (envelope-from gavin@FreeBSD.org) Message-Id: <201409172313.s8HNDmMO036602@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gavin set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson Date: Wed, 17 Sep 2014 23:13:48 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45633 - head/share/xml 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: Wed, 17 Sep 2014 23:13:48 -0000 Author: gavin Date: Wed Sep 17 23:13:47 2014 New Revision: 45633 URL: http://svnweb.freebsd.org/changeset/doc/45633 Log: Switch to the recommended URL for the old Google Chart API Note that this code uses the old API which is officially deprecated, however converting this to use the new Chart API will take some time. Obtained from: https://developers.google.com/chart/image/docs/making_charts Modified: head/share/xml/templates.usergroups.xsl Modified: head/share/xml/templates.usergroups.xsl ============================================================================== --- head/share/xml/templates.usergroups.xsl Wed Sep 17 19:03:36 2014 (r45632) +++ head/share/xml/templates.usergroups.xsl Wed Sep 17 23:13:47 2014 (r45633) @@ -16,7 +16,7 @@ - + &title; From owner-svn-doc-all@FreeBSD.ORG Wed Sep 17 23:33:54 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB097B40; Wed, 17 Sep 2014 23:33:54 +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 A6BAD9B4; Wed, 17 Sep 2014 23:33:54 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8HNXscs046354; Wed, 17 Sep 2014 23:33:54 GMT (envelope-from kib@FreeBSD.org) Received: (from kib@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8HNXsuM046352; Wed, 17 Sep 2014 23:33:54 GMT (envelope-from kib@FreeBSD.org) Message-Id: <201409172333.s8HNXsuM046352@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: kib set sender to kib@FreeBSD.org using -f From: Konstantin Belousov Date: Wed, 17 Sep 2014 23:33:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45634 - head/en_US.ISO8859-1/books/porters-handbook/versions 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: Wed, 17 Sep 2014 23:33:54 -0000 Author: kib (src committer) Date: Wed Sep 17 23:33:54 2014 New Revision: 45634 URL: http://svnweb.freebsd.org/changeset/doc/45634 Log: Document __FreeBSD_version 1100036. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Wed Sep 17 23:13:47 2014 (r45633) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Wed Sep 17 23:33:54 2014 (r45634) @@ -5407,6 +5407,14 @@ (rev 271705). + + 1100036 + September 17, 2014 + Version bump to have ABI note distinguish binaries + ready for strict &man.mmap.2; flags checking + (rev 271724). + + From owner-svn-doc-all@FreeBSD.ORG Thu Sep 18 12:03:41 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7B8A12AD; Thu, 18 Sep 2014 12:03:41 +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 66A9794E; Thu, 18 Sep 2014 12:03:41 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8IC3fXF095861; Thu, 18 Sep 2014 12:03:41 GMT (envelope-from mat@FreeBSD.org) Received: (from mat@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8IC3f9v095860; Thu, 18 Sep 2014 12:03:41 GMT (envelope-from mat@FreeBSD.org) Message-Id: <201409181203.s8IC3f9v095860@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: mat set sender to mat@FreeBSD.org using -f From: Mathieu Arnold Date: Thu, 18 Sep 2014 12:03:41 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45635 - head/en_US.ISO8859-1/books/porters-handbook/uses 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: Thu, 18 Sep 2014 12:03:41 -0000 Author: mat (ports committer) Date: Thu Sep 18 12:03:40 2014 New Revision: 45635 URL: http://svnweb.freebsd.org/changeset/doc/45635 Log: Add USES=autoreconf Differential Revision: https://reviews.freebsd.org/D792 Reviewed by: wblock, tijl Sponsored by: Absolight Modified: head/en_US.ISO8859-1/books/porters-handbook/uses/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/uses/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/uses/chapter.xml Wed Sep 17 23:33:54 2014 (r45634) +++ head/en_US.ISO8859-1/books/porters-handbook/uses/chapter.xml Thu Sep 18 12:03:40 2014 (r45635) @@ -56,6 +56,28 @@ gcc 4.7 based one. + + autoreconf + + (none), build + + Runs autoreconf. It encapsulates + the aclocal, + autoconf, + autoheader, + automake, autopoint, + and libtoolize commands. Each command + applies to + ${CONFIGURE_WRKSRC}/configure.ac. If + configure.ac defines subdirectories + with their own configure.ac using + AC_CONFIG_SUBDIRS, + autoreconf will recursively update + those as well. The :build argument + only adds build time dependencies on those tools but does + not run autoreconf. + + bison From owner-svn-doc-all@FreeBSD.ORG Thu Sep 18 20:37:54 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 43547EF1; Thu, 18 Sep 2014 20:37:54 +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 2D116FFF; Thu, 18 Sep 2014 20:37:54 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8IKbsQT049491; Thu, 18 Sep 2014 20:37:54 GMT (envelope-from dumbbell@FreeBSD.org) Received: (from dumbbell@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8IKbshp049490; Thu, 18 Sep 2014 20:37:54 GMT (envelope-from dumbbell@FreeBSD.org) Message-Id: <201409182037.s8IKbshp049490@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: dumbbell set sender to dumbbell@FreeBSD.org using -f From: Jean-Sebastien Pedron Date: Thu, 18 Sep 2014 20:37:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45636 - head/en_US.ISO8859-1/books/porters-handbook/versions 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: Thu, 18 Sep 2014 20:37:54 -0000 Author: dumbbell (src committer) Date: Thu Sep 18 20:37:53 2014 New Revision: 45636 URL: http://svnweb.freebsd.org/changeset/doc/45636 Log: Document __FreeBSD_version value 1000717 Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Modified: head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Thu Sep 18 12:03:40 2014 (r45635) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Thu Sep 18 20:37:53 2014 (r45636) @@ -5140,6 +5140,13 @@ + 1000717 + September 18, 2014 + 10-STABLE after i915 HW context support + (rev 271816). + + + 1100000 October 10, 2013 11.0-CURRENT From owner-svn-doc-all@FreeBSD.ORG Thu Sep 18 20:51:13 2014 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 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 67B59F40; Thu, 18 Sep 2014 20:51:13 +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 5258D289; Thu, 18 Sep 2014 20:51:13 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8IKpD7B058052; Thu, 18 Sep 2014 20:51:13 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8IKpD0k058050; Thu, 18 Sep 2014 20:51:13 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201409182051.s8IKpD0k058050@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Thu, 18 Sep 2014 20:51:13 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45637 - head/en_US.ISO8859-1/books/handbook/bibliography 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: Thu, 18 Sep 2014 20:51:13 -0000 Author: gjb Date: Thu Sep 18 20:51:12 2014 New Revision: 45637 URL: http://svnweb.freebsd.org/changeset/doc/45637 Log: Mention Design and Implementation of the FreeBSD Operating System, 2nd Ed in the bibliography. Sponsored by: The FreeBSD Foundation Modified: head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Thu Sep 18 20:37:53 2014 (r45636) +++ head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml Thu Sep 18 20:51:12 2014 (r45637) @@ -379,6 +379,14 @@ + Marshall Kirk McKusick, George V. Neville-Neil, + Robert N. M. Watson The Design and Implementation + of the FreeBSD Operating System, 2nd Ed.. + Westford, Mass. : Pearson Education, Inc., 2014. + ISBN 0-321-96897-2 + + + Stevens, W. Richard. TCP/IP Illustrated, Volume 1: The Protocols. Reading, Mass. : Addison-Wesley, 1996. ISBN 0-201-63346-9 From owner-svn-doc-all@FreeBSD.ORG Thu Sep 18 23:09:08 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2A0DB23E; Thu, 18 Sep 2014 23:09:08 +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 15A41269; Thu, 18 Sep 2014 23:09:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.9/8.14.9) with ESMTP id s8IN973D022529; Thu, 18 Sep 2014 23:09:07 GMT (envelope-from gavin@FreeBSD.org) Received: (from gavin@localhost) by svn.freebsd.org (8.14.9/8.14.9/Submit) id s8IN97lT022528; Thu, 18 Sep 2014 23:09:07 GMT (envelope-from gavin@FreeBSD.org) Message-Id: <201409182309.s8IN97lT022528@svn.freebsd.org> X-Authentication-Warning: svn.freebsd.org: gavin set sender to gavin@FreeBSD.org using -f From: Gavin Atkinson Date: Thu, 18 Sep 2014 23:09:07 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r45638 - head/en_US.ISO8859-1/htdocs 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: Thu, 18 Sep 2014 23:09:08 -0000 Author: gavin Date: Thu Sep 18 23:09:07 2014 New Revision: 45638 URL: http://svnweb.freebsd.org/changeset/doc/45638 Log: Hopefully fix the display of the most recent videos, by using protocol- relative URLs. Unfortunately, I am unable to test this fix locally at the moment. Modified: head/en_US.ISO8859-1/htdocs/community.xsl Modified: head/en_US.ISO8859-1/htdocs/community.xsl ============================================================================== --- head/en_US.ISO8859-1/htdocs/community.xsl Thu Sep 18 20:51:12 2014 (r45637) +++ head/en_US.ISO8859-1/htdocs/community.xsl Thu Sep 18 23:09:07 2014 (r45638) @@ -78,19 +78,19 @@ Loading...

    - -