From owner-svn-doc-all@freebsd.org Sun Sep 1 06:58:25 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A3AADD085E; Sun, 1 Sep 2019 06:58:25 +0000 (UTC) (envelope-from wosch@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46LkZT3s9zz40sP; Sun, 1 Sep 2019 06:58:25 +0000 (UTC) (envelope-from wosch@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 630C4259EC; Sun, 1 Sep 2019 06:58:25 +0000 (UTC) (envelope-from wosch@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x816wP2G064674; Sun, 1 Sep 2019 06:58:25 GMT (envelope-from wosch@FreeBSD.org) Received: (from wosch@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x816wPXn064673; Sun, 1 Sep 2019 06:58:25 GMT (envelope-from wosch@FreeBSD.org) Message-Id: <201909010658.x816wPXn064673@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: wosch set sender to wosch@FreeBSD.org using -f From: Wolfram Schneider Date: Sun, 1 Sep 2019 06:58:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53346 - head/en_US.ISO8859-1/htdocs/cgi X-SVN-Group: doc-head X-SVN-Commit-Author: wosch X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/cgi X-SVN-Commit-Revision: 53346 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 06:58:25 -0000 Author: wosch Date: Sun Sep 1 06:58:24 2019 New Revision: 53346 URL: https://svnweb.freebsd.org/changeset/doc/53346 Log: add Sun UNIX 0.4 (aka SunOS 0.4) manual pages Modified: head/en_US.ISO8859-1/htdocs/cgi/man.cgi Modified: head/en_US.ISO8859-1/htdocs/cgi/man.cgi ============================================================================== --- head/en_US.ISO8859-1/htdocs/cgi/man.cgi Sat Aug 31 18:39:13 2019 (r53345) +++ head/en_US.ISO8859-1/htdocs/cgi/man.cgi Sun Sep 1 06:58:24 2019 (r53346) @@ -687,6 +687,12 @@ $manPathDefault = 'FreeBSD 12.0-RELEASE and Ports'; 'SunOS 5.5.1', "$manLocalDir/SunOS-5.5.1", 'SunOS 4.1.3', "$manLocalDir/SunOS-4.1.3", + # full name: Sun UNIX 4.2* Software Release 0.4 (*Berkeley Beta Release) + # 1/2'' Boot Tape 700-0586-01 + # alias SunOS 0.4, apparently released in April 1983 based on 4.2BSD beta + 'Sun UNIX 0.4', "$manLocalDir/Sun-UNIX-0.4", + + #'XFree86 3.2', "$manLocalDir/XFree86-3.2", 'XFree86 2.1', "$manLocalDir/XFree86-2.1", 'XFree86 3.3', "$manLocalDir/XFree86-3.3", From owner-svn-doc-all@freebsd.org Sun Sep 1 10:44:30 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C144BD65F8; Sun, 1 Sep 2019 10:44:30 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46LqbL4gmQz4B63; Sun, 1 Sep 2019 10:44:30 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 833373EE; Sun, 1 Sep 2019 10:44:30 +0000 (UTC) (envelope-from se@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x81AiUKj000669; Sun, 1 Sep 2019 10:44:30 GMT (envelope-from se@FreeBSD.org) Received: (from se@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x81AiUZb000668; Sun, 1 Sep 2019 10:44:30 GMT (envelope-from se@FreeBSD.org) Message-Id: <201909011044.x81AiUZb000668@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: se set sender to se@FreeBSD.org using -f From: Stefan Esser Date: Sun, 1 Sep 2019 10:44:30 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53347 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: se X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53347 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 10:44:30 -0000 Author: se (src,ports committer) Date: Sun Sep 1 10:44:29 2019 New Revision: 53347 URL: https://svnweb.freebsd.org/changeset/doc/53347 Log: Update my pgp key Reported by: pi Modified: head/share/pgpkeys/se.key Modified: head/share/pgpkeys/se.key ============================================================================== --- head/share/pgpkeys/se.key Sun Sep 1 06:58:24 2019 (r53346) +++ head/share/pgpkeys/se.key Sun Sep 1 10:44:29 2019 (r53347) @@ -2,14 +2,14 @@ - -sub 2048R/ACCC7EFAB7B32CCA 2015-06-05 [verfällt: 2018-06-04] +uid Stefan Eßer (FreeBSD) +sub rsa2048/ACCC7EFAB7B32CCA 2015-06-05 [E] [verfällt: 2022-08-31] ]]> - From owner-svn-doc-all@freebsd.org Sun Sep 1 10:53:45 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 4C67FD6870; Sun, 1 Sep 2019 10:53:45 +0000 (UTC) (envelope-from ashish@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Lqp11mCdz4BQS; Sun, 1 Sep 2019 10:53:45 +0000 (UTC) (envelope-from ashish@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1F5065D3; Sun, 1 Sep 2019 10:53:45 +0000 (UTC) (envelope-from ashish@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x81ArjGm006850; Sun, 1 Sep 2019 10:53:45 GMT (envelope-from ashish@FreeBSD.org) Received: (from ashish@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x81Arjuu006849; Sun, 1 Sep 2019 10:53:45 GMT (envelope-from ashish@FreeBSD.org) Message-Id: <201909011053.x81Arjuu006849@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ashish set sender to ashish@FreeBSD.org using -f From: Ashish SHUKLA Date: Sun, 1 Sep 2019 10:53:45 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53348 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: ashish X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53348 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 10:53:45 -0000 Author: ashish (ports committer) Date: Sun Sep 1 10:53:44 2019 New Revision: 53348 URL: https://svnweb.freebsd.org/changeset/doc/53348 Log: Update my PGP key Modified: head/share/pgpkeys/ashish.key Modified: head/share/pgpkeys/ashish.key ============================================================================== --- head/share/pgpkeys/ashish.key Sun Sep 1 10:44:29 2019 (r53347) +++ head/share/pgpkeys/ashish.key Sun Sep 1 10:53:44 2019 (r53348) @@ -1,23 +1,28 @@ -uid Ashish SHUKLA -uid Ashish SHUKLA -uid Ashish SHUKLA -uid Ashish SHUKLA -uid Ashish SHUKLA -uid Ashish SHUKLA -uid Ashish SHUKLA -uid Ashish SHUKLA -uid Ashish SHUKLA -uid [jpeg image of size 4655] -uid Ashish SHUKLA (FreeBSD Committer Address) -sub 4096R/F20D202D 2010-04-13 +uid Ashish SHUKLA (Lost Case) +uid Ashish SHUKLA +uid Ashish SHUKLA +uid Ashish SHUKLA +uid Ashish SHUKLA +uid Ashish SHUKLA +uid Ashish SHUKLA +uid Ashish SHUKLA +uid Ashish SHUKLA +uid Ashish SHUKLA (FreeBSD Committer Address) +uid Ashish SHUKLA (Work Address) +uid Ashish SHUKLA (Lost Case) +uid Ashish SHUKLA (Personal Email) +uid [jpeg image of size 4655] +uid Ashish SHUKLA +sub rsa4096/975CA8A8F20D202D 2010-04-13 [E] + Key fingerprint = A385 4E69 D459 F735 5136 6948 975C A8A8 F20D 202D + ]]> Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9FDD2DBEE6; Sun, 1 Sep 2019 14:48:37 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Lx113W6Dz4Nqn; Sun, 1 Sep 2019 14:48:37 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 5B2F12EEC; Sun, 1 Sep 2019 14:48:37 +0000 (UTC) (envelope-from ryusuke@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x81Embgm042860; Sun, 1 Sep 2019 14:48:37 GMT (envelope-from ryusuke@FreeBSD.org) Received: (from ryusuke@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x81EmbGd042859; Sun, 1 Sep 2019 14:48:37 GMT (envelope-from ryusuke@FreeBSD.org) Message-Id: <201909011448.x81EmbGd042859@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ryusuke set sender to ryusuke@FreeBSD.org using -f From: Ryusuke SUZUKI Date: Sun, 1 Sep 2019 14:48:37 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53349 - head/ja_JP.eucJP/books/handbook/linuxemu X-SVN-Group: doc-head X-SVN-Commit-Author: ryusuke X-SVN-Commit-Paths: head/ja_JP.eucJP/books/handbook/linuxemu X-SVN-Commit-Revision: 53349 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 14:48:37 -0000 Author: ryusuke Date: Sun Sep 1 14:48:36 2019 New Revision: 53349 URL: https://svnweb.freebsd.org/changeset/doc/53349 Log: - Merge the following from the English version: r50605 -> r53044 head/ja_JP.eucJP/books/handbook/linuxemu/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/linuxemu/chapter.xml Modified: head/ja_JP.eucJP/books/handbook/linuxemu/chapter.xml ============================================================================== --- head/ja_JP.eucJP/books/handbook/linuxemu/chapter.xml Sun Sep 1 10:53:44 2019 (r53348) +++ head/ja_JP.eucJP/books/handbook/linuxemu/chapter.xml Sun Sep 1 14:48:36 2019 (r53349) @@ -3,7 +3,7 @@ The FreeBSD Documentation Project The FreeBSD Japanese Documentation Project - Original revision: r50605 + Original revision: r53044 $FreeBSD$ --> COMPAT_LINUX - Linux ¥Ð¥¤¥Ê¥ê¸ß´¹µ¡Ç½¤Î¥ì¥¤¥ä¤Ë¤Ï¡¢(64 ¥Ó¥Ã¥È x86 ¥Û¥¹¥È¤Ë¤ª¤±¤ë) + &linux; ¥Ð¥¤¥Ê¥ê¸ß´¹µ¡Ç½¤Î¥ì¥¤¥ä¤Ë¤Ï¡¢(64 ¥Ó¥Ã¥È x86 ¥Û¥¹¥È¤Ë¤ª¤±¤ë) 32 ¤ª¤è¤Ó 64 ¥Ó¥Ã¥È Linux ¥Ð¥¤¥Ê¥ê¤Î¥µ¥Ý¡¼¥È¤¬Äɲ䵤줿¤¿¤á¡¢ ¥¨¥ß¥å¥ì¡¼¥·¥ç¥óµ¡Ç½¤ò¥«¥¹¥¿¥à¥«¡¼¥Í¥ë¤ËÀÅŪ¤Ë¥ê¥ó¥¯¤¹¤ëɬÍפϤ¢¤ê¤Þ¤»¤ó¡£ From owner-svn-doc-all@freebsd.org Sun Sep 1 15:00:18 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 885A6DC3CC; Sun, 1 Sep 2019 15:00:18 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46LxGV1KrXz4PSZ; Sun, 1 Sep 2019 15:00:18 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 11ED930BA; Sun, 1 Sep 2019 15:00:18 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x81F0HiR048747; Sun, 1 Sep 2019 15:00:17 GMT (envelope-from fox@FreeBSD.org) Received: (from fox@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x81F0Hma048746; Sun, 1 Sep 2019 15:00:17 GMT (envelope-from fox@FreeBSD.org) Message-Id: <201909011500.x81F0Hma048746@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: fox set sender to fox@FreeBSD.org using -f From: Santhosh Raju Date: Sun, 1 Sep 2019 15:00:17 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53350 - head/share/xml X-SVN-Group: doc-head X-SVN-Commit-Author: fox X-SVN-Commit-Paths: head/share/xml X-SVN-Commit-Revision: 53350 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 15:00:18 -0000 Author: fox (ports committer) Date: Sun Sep 1 15:00:17 2019 New Revision: 53350 URL: https://svnweb.freebsd.org/changeset/doc/53350 Log: Add myself (fox) as a ports committer. Approved by: philip (mentor) Modified: head/share/xml/authors.ent Modified: head/share/xml/authors.ent ============================================================================== --- head/share/xml/authors.ent Sun Sep 1 14:48:36 2019 (r53349) +++ head/share/xml/authors.ent Sun Sep 1 15:00:17 2019 (r53350) @@ -801,6 +801,9 @@ flz@FreeBSD.org"> + +fox@FreeBSD.org"> + foxfair@FreeBSD.org"> From owner-svn-doc-all@freebsd.org Sun Sep 1 15:01:22 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CF71FDC4D1; Sun, 1 Sep 2019 15:01:22 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46LxHk59MKz4PYv; Sun, 1 Sep 2019 15:01:22 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 950633100; Sun, 1 Sep 2019 15:01:22 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x81F1MXn050718; Sun, 1 Sep 2019 15:01:22 GMT (envelope-from fox@FreeBSD.org) Received: (from fox@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x81F1MKW050716; Sun, 1 Sep 2019 15:01:22 GMT (envelope-from fox@FreeBSD.org) Message-Id: <201909011501.x81F1MKW050716@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: fox set sender to fox@FreeBSD.org using -f From: Santhosh Raju Date: Sun, 1 Sep 2019 15:01:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53351 - head/en_US.ISO8859-1/articles/contributors X-SVN-Group: doc-head X-SVN-Commit-Author: fox X-SVN-Commit-Paths: head/en_US.ISO8859-1/articles/contributors X-SVN-Commit-Revision: 53351 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 15:01:22 -0000 Author: fox (ports committer) Date: Sun Sep 1 15:01:21 2019 New Revision: 53351 URL: https://svnweb.freebsd.org/changeset/doc/53351 Log: Add myself (fox) as a ports committer. Remove myself (fox) from the contrib entry. Approved by: philip (mentor) Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sun Sep 1 15:00:17 2019 (r53350) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sun Sep 1 15:01:21 2019 (r53351) @@ -9623,11 +9623,6 @@ - Santhosh Raju - santhosh.raju@gmail.com - - - Sarod Yatawatta sarod@users.sf.net Modified: head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Sun Sep 1 15:00:17 2019 (r53350) +++ head/en_US.ISO8859-1/articles/contributors/contrib.committers.xml Sun Sep 1 15:01:21 2019 (r53351) @@ -1122,6 +1122,10 @@ xmlns:xlink="http://www.w3.org/1999/xlink" version="5. + &a.fox.email; + + + &a.attilio.email; From owner-svn-doc-all@freebsd.org Sun Sep 1 15:02:11 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 25691DC64F; Sun, 1 Sep 2019 15:02:11 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46LxJg0CJXz4Plr; Sun, 1 Sep 2019 15:02:11 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DF2753267; Sun, 1 Sep 2019 15:02:10 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x81F2AR2054578; Sun, 1 Sep 2019 15:02:10 GMT (envelope-from fox@FreeBSD.org) Received: (from fox@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x81F2As9054577; Sun, 1 Sep 2019 15:02:10 GMT (envelope-from fox@FreeBSD.org) Message-Id: <201909011502.x81F2As9054577@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: fox set sender to fox@FreeBSD.org using -f From: Santhosh Raju Date: Sun, 1 Sep 2019 15:02:10 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53352 - head/share/xml X-SVN-Group: doc-head X-SVN-Commit-Author: fox X-SVN-Commit-Paths: head/share/xml X-SVN-Commit-Revision: 53352 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 15:02:11 -0000 Author: fox (ports committer) Date: Sun Sep 1 15:02:10 2019 New Revision: 53352 URL: https://svnweb.freebsd.org/changeset/doc/53352 Log: Add myself (fox) in the news entry. Approved by: philip (mentor) Modified: head/share/xml/news.xml Modified: head/share/xml/news.xml ============================================================================== --- head/share/xml/news.xml Sun Sep 1 15:01:21 2019 (r53351) +++ head/share/xml/news.xml Sun Sep 1 15:02:10 2019 (r53352) @@ -35,6 +35,20 @@ 8 + 28 + + +

New committer: + Santhosh Raju + (ports)

+ + + + + + 8 + + 25 From owner-svn-doc-all@freebsd.org Sun Sep 1 15:37:23 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 264CDDCD9F; Sun, 1 Sep 2019 15:37:23 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Ly5H0BZLz4QqW; Sun, 1 Sep 2019 15:37:23 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DA7D739B6; Sun, 1 Sep 2019 15:37:22 +0000 (UTC) (envelope-from fox@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x81FbMKT073268; Sun, 1 Sep 2019 15:37:22 GMT (envelope-from fox@FreeBSD.org) Received: (from fox@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x81FbMC0073266; Sun, 1 Sep 2019 15:37:22 GMT (envelope-from fox@FreeBSD.org) Message-Id: <201909011537.x81FbMC0073266@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: fox set sender to fox@FreeBSD.org using -f From: Santhosh Raju Date: Sun, 1 Sep 2019 15:37:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53353 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: fox X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53353 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 15:37:23 -0000 Author: fox (ports committer) Date: Sun Sep 1 15:37:22 2019 New Revision: 53353 URL: https://svnweb.freebsd.org/changeset/doc/53353 Log: Add my (fox's) PGP key and entries for the PGP key. Approved by: philip (mentor) Added: head/share/pgpkeys/fox.key (contents, props changed) Modified: head/share/pgpkeys/pgpkeys-developers.xml head/share/pgpkeys/pgpkeys.ent Added: head/share/pgpkeys/fox.key ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ head/share/pgpkeys/fox.key Sun Sep 1 15:37:22 2019 (r53353) @@ -0,0 +1,163 @@ + + + +uid Santhosh Raju (NetBSD email) +uid Santhosh Raju (FreeBSD email) +sub rsa4096/15A11655DFB8A99E 2015-05-07 [E] +sub rsa4096/D6E34FF91FEC528F 2015-05-07 [S] + +]]> + Modified: head/share/pgpkeys/pgpkeys-developers.xml ============================================================================== --- head/share/pgpkeys/pgpkeys-developers.xml Sun Sep 1 15:02:10 2019 (r53352) +++ head/share/pgpkeys/pgpkeys-developers.xml Sun Sep 1 15:37:22 2019 (r53353) @@ -1971,6 +1971,11 @@ &pgpkey.bofh; + + &a.fox.email; + &pgpkey.fox; + + &a.lbr.email; &pgpkey.lbr; Modified: head/share/pgpkeys/pgpkeys.ent ============================================================================== --- head/share/pgpkeys/pgpkeys.ent Sun Sep 1 15:02:10 2019 (r53352) +++ head/share/pgpkeys/pgpkeys.ent Sun Sep 1 15:37:22 2019 (r53353) @@ -174,6 +174,7 @@ + From owner-svn-doc-all@freebsd.org Sun Sep 1 16:36:28 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C109EDE4D0; Sun, 1 Sep 2019 16:36:28 +0000 (UTC) (envelope-from thierry@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46LzPS57b4z4VPC; Sun, 1 Sep 2019 16:36:28 +0000 (UTC) (envelope-from thierry@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8F3FC45A1; Sun, 1 Sep 2019 16:36:28 +0000 (UTC) (envelope-from thierry@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x81GaSho009939; Sun, 1 Sep 2019 16:36:28 GMT (envelope-from thierry@FreeBSD.org) Received: (from thierry@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x81GaSSt009938; Sun, 1 Sep 2019 16:36:28 GMT (envelope-from thierry@FreeBSD.org) Message-Id: <201909011636.x81GaSSt009938@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: thierry set sender to thierry@FreeBSD.org using -f From: Thierry Thomas Date: Sun, 1 Sep 2019 16:36:28 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53354 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: thierry X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53354 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 16:36:28 -0000 Author: thierry (ports committer) Date: Sun Sep 1 16:36:28 2019 New Revision: 53354 URL: https://svnweb.freebsd.org/changeset/doc/53354 Log: Refresh my key. Spotted by: pi Modified: head/share/pgpkeys/thierry.key Modified: head/share/pgpkeys/thierry.key ============================================================================== --- head/share/pgpkeys/thierry.key Sun Sep 1 15:37:22 2019 (r53353) +++ head/share/pgpkeys/thierry.key Sun Sep 1 16:36:28 2019 (r53354) @@ -3,12 +3,12 @@ sh addkey.sh thierry F1C516B3C8359753; --> uid [ultimate] Thierry Thomas uid [ultimate] [jpeg image of size 1968] -sub 4096R/32B32808E6B52F4F 2013-09-23 [expires: 2018-09-22] +uid [ultimate] keybase.io/thierry +sub 4096R/32B32808E6B52F4F 2013-09-23 [expires: 2020-10-05] ]]> From owner-svn-doc-all@freebsd.org Sun Sep 1 16:55:47 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E7DF9DF01E; Sun, 1 Sep 2019 16:55:47 +0000 (UTC) (envelope-from mp@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Lzql6ZL1z4XJ4; Sun, 1 Sep 2019 16:55:47 +0000 (UTC) (envelope-from mp@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id AD4BC496F; Sun, 1 Sep 2019 16:55:47 +0000 (UTC) (envelope-from mp@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x81Gtlp9022557; Sun, 1 Sep 2019 16:55:47 GMT (envelope-from mp@FreeBSD.org) Received: (from mp@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x81GtlLp022556; Sun, 1 Sep 2019 16:55:47 GMT (envelope-from mp@FreeBSD.org) Message-Id: <201909011655.x81GtlLp022556@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: mp set sender to mp@FreeBSD.org using -f From: Mark Peek Date: Sun, 1 Sep 2019 16:55:47 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53355 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: mp X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53355 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 16:55:48 -0000 Author: mp (src committer) Date: Sun Sep 1 16:55:47 2019 New Revision: 53355 URL: https://svnweb.freebsd.org/changeset/doc/53355 Log: Update my PGP key Modified: head/share/pgpkeys/mp.key Modified: head/share/pgpkeys/mp.key ============================================================================== --- head/share/pgpkeys/mp.key Sun Sep 1 16:36:28 2019 (r53354) +++ head/share/pgpkeys/mp.key Sun Sep 1 16:55:47 2019 (r53355) @@ -1,20 +1,20 @@ -uid Mark Peek -uid Mark Peek -uid Mark Peek -sub 4096R/F2A0C29D400364D8 2014-02-07 [expires: 2016-02-20] +uid Mark Peek +uid Mark Peek +uid Mark Peek +uid Mark Peek +uid Mark Peek +sub rsa4096/F2A0C29D400364D8 2014-02-07 [E] [expires: 2021-06-22] ]]> From owner-svn-doc-all@freebsd.org Sun Sep 1 19:40:25 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 930E6E313D; Sun, 1 Sep 2019 19:40:25 +0000 (UTC) (envelope-from dbaio@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46M3Tj3Nyyz3FQ7; Sun, 1 Sep 2019 19:40:25 +0000 (UTC) (envelope-from dbaio@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 5869566AC; Sun, 1 Sep 2019 19:40:25 +0000 (UTC) (envelope-from dbaio@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x81JePbM020603; Sun, 1 Sep 2019 19:40:25 GMT (envelope-from dbaio@FreeBSD.org) Received: (from dbaio@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x81JePPQ020602; Sun, 1 Sep 2019 19:40:25 GMT (envelope-from dbaio@FreeBSD.org) Message-Id: <201909011940.x81JePPQ020602@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: dbaio set sender to dbaio@FreeBSD.org using -f From: "Danilo G. Baio" Date: Sun, 1 Sep 2019 19:40:25 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53356 - head/en_US.ISO8859-1/articles/contributors X-SVN-Group: doc-head X-SVN-Commit-Author: dbaio X-SVN-Commit-Paths: head/en_US.ISO8859-1/articles/contributors X-SVN-Commit-Revision: 53356 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 19:40:25 -0000 Author: dbaio (ports committer) Date: Sun Sep 1 19:40:24 2019 New Revision: 53356 URL: https://svnweb.freebsd.org/changeset/doc/53356 Log: Add Martin Filla to contributors Maintainer of: deskutils/anydesk devel/raylib devel/sasm devel/zapcc emulators/anese games/openage lang/nyan net/reaver sysutils/boot-extract PR: 239940 Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Modified: head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml ============================================================================== --- head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sun Sep 1 16:55:47 2019 (r53355) +++ head/en_US.ISO8859-1/articles/contributors/contrib.additional.xml Sun Sep 1 19:40:24 2019 (r53356) @@ -6682,6 +6682,11 @@ + Martin Filla + freebsd@sysctl.cz + + + Martin Hinner mhi@linux.gyarab.cz From owner-svn-doc-all@freebsd.org Sun Sep 1 22:03:33 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9E2B4E7D00; Sun, 1 Sep 2019 22:03:33 +0000 (UTC) (envelope-from karels@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46M6fs3Rhbz3QWR; Sun, 1 Sep 2019 22:03:33 +0000 (UTC) (envelope-from karels@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 5AE2982F5; Sun, 1 Sep 2019 22:03:33 +0000 (UTC) (envelope-from karels@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x81M3XV0010702; Sun, 1 Sep 2019 22:03:33 GMT (envelope-from karels@FreeBSD.org) Received: (from karels@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x81M3XEg010701; Sun, 1 Sep 2019 22:03:33 GMT (envelope-from karels@FreeBSD.org) Message-Id: <201909012203.x81M3XEg010701@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: karels set sender to karels@FreeBSD.org using -f From: Mike Karels Date: Sun, 1 Sep 2019 22:03:33 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53357 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: karels X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53357 X-SVN-Commit-Repository: doc 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.29 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, 01 Sep 2019 22:03:33 -0000 Author: karels (src committer) Date: Sun Sep 1 22:03:32 2019 New Revision: 53357 URL: https://svnweb.freebsd.org/changeset/doc/53357 Log: Update expiration on karels@freebsd.org gpg key. Contents produced by addkey.sh. Modified: head/share/pgpkeys/karels.key Modified: head/share/pgpkeys/karels.key ============================================================================== --- head/share/pgpkeys/karels.key Sun Sep 1 19:40:24 2019 (r53356) +++ head/share/pgpkeys/karels.key Sun Sep 1 22:03:32 2019 (r53357) @@ -3,10 +3,10 @@ sh addkey.sh karels 8CCF69ECC5CF284F ; --> -sub rsa2048/B4CE5C0549FFC668 2016-06-16 [E] [expires: 2019-06-16] +sub rsa2048/B4CE5C0549FFC668 2016-06-16 [E] [expires: 2022-08-31] ]]> From owner-svn-doc-all@freebsd.org Mon Sep 2 00:25:14 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2662BCB46C; Mon, 2 Sep 2019 00:25:14 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46M9pL0FxTz42P4; Mon, 2 Sep 2019 00:25:14 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DC3059C0B; Mon, 2 Sep 2019 00:25:13 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x820PDl3093585; Mon, 2 Sep 2019 00:25:13 GMT (envelope-from wblock@FreeBSD.org) Received: (from wblock@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x820PDB9093584; Mon, 2 Sep 2019 00:25:13 GMT (envelope-from wblock@FreeBSD.org) Message-Id: <201909020025.x820PDB9093584@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: wblock set sender to wblock@FreeBSD.org using -f From: Warren Block Date: Mon, 2 Sep 2019 00:25:13 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53358 - head/en_US.ISO8859-1/books/handbook/printing X-SVN-Group: doc-head X-SVN-Commit-Author: wblock X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/handbook/printing X-SVN-Commit-Revision: 53358 X-SVN-Commit-Repository: doc 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.29 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, 02 Sep 2019 00:25:14 -0000 Author: wblock Date: Mon Sep 2 00:25:13 2019 New Revision: 53358 URL: https://svnweb.freebsd.org/changeset/doc/53358 Log: Remove extra ">" causing rendering error. Modified: head/en_US.ISO8859-1/books/handbook/printing/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/printing/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/printing/chapter.xml Sun Sep 1 22:03:32 2019 (r53357) +++ head/en_US.ISO8859-1/books/handbook/printing/chapter.xml Mon Sep 2 00:25:13 2019 (r53358) @@ -946,7 +946,7 @@ cfA005smithy dequeued instead of a specific printer name, and the command will be applied to all printers. Normal users can view status with &man.lpc.8;. Only - class="username">root can use + root can use commands which modify printer status. Show the status of all printers: From owner-svn-doc-all@freebsd.org Mon Sep 2 14:25:46 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9B780DF624; Mon, 2 Sep 2019 14:25:46 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46MXSB3YlBz3KTn; Mon, 2 Sep 2019 14:25:46 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 43BDE1B604; Mon, 2 Sep 2019 14:25:46 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x82EPkYa096340; Mon, 2 Sep 2019 14:25:46 GMT (envelope-from trasz@FreeBSD.org) Received: (from trasz@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x82EPkLl096339; Mon, 2 Sep 2019 14:25:46 GMT (envelope-from trasz@FreeBSD.org) Message-Id: <201909021425.x82EPkLl096339@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: trasz set sender to trasz@FreeBSD.org using -f From: Edward Tomasz Napierala Date: Mon, 2 Sep 2019 14:25:46 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53359 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head X-SVN-Commit-Author: trasz X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/news/status X-SVN-Commit-Revision: 53359 X-SVN-Commit-Repository: doc 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.29 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, 02 Sep 2019 14:25:46 -0000 Author: trasz Date: Mon Sep 2 14:25:45 2019 New Revision: 53359 URL: https://svnweb.freebsd.org/changeset/doc/53359 Log: Improve the instructions. Sponsored by: DARPA, AFRL Modified: head/en_US.ISO8859-1/htdocs/news/status/README Modified: head/en_US.ISO8859-1/htdocs/news/status/README ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/README Mon Sep 2 00:25:13 2019 (r53358) +++ head/en_US.ISO8859-1/htdocs/news/status/README Mon Sep 2 14:25:45 2019 (r53359) @@ -2,7 +2,8 @@ Compiling status reports - best practices 0) Timeline (relative to submission deadline) --1 month First call for reports +-1 month First call for reports - that will be January 1st, April 1st, + July 1st, and October 1st -2 weeks Reminder -1 week Reminder, and follow up with teams and individuals we expect to submit reports @@ -55,16 +56,22 @@ deadline Follow up on missing reports if at all possible. 4) Building the report: - - Fold the reports into a work-in-progress draft as they are coming in (see - point 5) for putting the report together). Commit the result and hook the - draft into the build, so you can (almost) immediately provide the - submitters a preview of their entries. This is also a good excuse to do - a acknowledgement on the receipt. - - While the report draft is kept updated, other doc-committers (wblock, + - Review and merge pull requests as they are coming in + - Review and merge reports submitted via email + - While the reports are being updated, other doc-committers (wblock, pluknet, and bjk, for example) may review the individual entries and propose fixes. + - Concatenate the reports into a draft, and add categories, such as + "# FreeBSD Team Reports #" or "# Projects #'. Consult md2docbook.py + source for the list of recognized tags - Use md2docbook.py to convert from the Markdown draft to DocBook: - https://github.com/trasz/md2docbook + https://github.com/trasz/md2docbook. Copy the generated DocBook draft + to en_US.ISO8859-1/htdocs/news/status/report-XXXX-YY-XXXX-ZZ.xml, + add it to the list in en_US.ISO8859-1/htdocs/news/status/Makefile, + run "make", and review the generated HTML file, + en_US.ISO8859-1/htdocs/news/status/report-XXXX-YY-XXXX-ZZ.html. + Adjust the Markdown source and regenerate until you are happy with + the result. - Tidy up the draft - tidy(1) may be used to get it well-formatted. Usually s without a description are missing the closing "/>" which is the cause for most of the errors you will encounter. Sometimes other closing tags are From owner-svn-doc-all@freebsd.org Mon Sep 2 15:05:34 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 806BFE06FF; Mon, 2 Sep 2019 15:05:34 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46MYL62sd4z3N7N; Mon, 2 Sep 2019 15:05:34 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 45C461BD7A; Mon, 2 Sep 2019 15:05:34 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x82F5Y7e020850; Mon, 2 Sep 2019 15:05:34 GMT (envelope-from linimon@FreeBSD.org) Received: (from linimon@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x82F5Yjb020849; Mon, 2 Sep 2019 15:05:34 GMT (envelope-from linimon@FreeBSD.org) Message-Id: <201909021505.x82F5Yjb020849@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: linimon set sender to linimon@FreeBSD.org using -f From: Mark Linimon Date: Mon, 2 Sep 2019 15:05:34 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53360 - head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Group: doc-head X-SVN-Commit-Author: linimon X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Commit-Revision: 53360 X-SVN-Commit-Repository: doc 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.29 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, 02 Sep 2019 15:05:34 -0000 Author: linimon Date: Mon Sep 2 15:05:33 2019 New Revision: 53360 URL: https://svnweb.freebsd.org/changeset/doc/53360 Log: Document OSVERSIONs 1300043 and 1300044. 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 Mon Sep 2 14:25:45 2019 (r53359) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Mon Sep 2 15:05:33 2019 (r53360) @@ -431,6 +431,21 @@ is spelled &, < is < and > is >. 13.0-CURRENT after addition of kernel-side support for in-kernel TLS. + + + 1300043 + 351698 + September 2, 2019 + 13.0-CURRENT after removal of gets(3). + + + + 1300044 + 351701 + September 2, 2019 + 13.0-CURRENT after adding sysfs create/remove functions + that handles multiple files in one call to the LinuxKPI. + From owner-svn-doc-all@freebsd.org Mon Sep 2 18:29:01 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9A1BFE5143; Mon, 2 Sep 2019 18:29:01 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Mdrs3RlNz485t; Mon, 2 Sep 2019 18:29:01 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 5A4B91E328; Mon, 2 Sep 2019 18:29:01 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x82IT1VU044101; Mon, 2 Sep 2019 18:29:01 GMT (envelope-from mandree@FreeBSD.org) Received: (from mandree@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x82IT17O044100; Mon, 2 Sep 2019 18:29:01 GMT (envelope-from mandree@FreeBSD.org) Message-Id: <201909021829.x82IT17O044100@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: mandree set sender to mandree@FreeBSD.org using -f From: Matthias Andree Date: Mon, 2 Sep 2019 18:29:01 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53361 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: mandree X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53361 X-SVN-Commit-Repository: doc 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.29 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, 02 Sep 2019 18:29:01 -0000 Author: mandree (ports committer) Date: Mon Sep 2 18:29:00 2019 New Revision: 53361 URL: https://svnweb.freebsd.org/changeset/doc/53361 Log: mandree.key: Bump expiration by two years. Reported by: pi@ Modified: head/share/pgpkeys/mandree.key Modified: head/share/pgpkeys/mandree.key ============================================================================== --- head/share/pgpkeys/mandree.key Mon Sep 2 15:05:33 2019 (r53360) +++ head/share/pgpkeys/mandree.key Mon Sep 2 18:29:00 2019 (r53361) @@ -3,11 +3,11 @@ sh addkey.sh mandree E412B156EFF3855A ; --> uid Matthias Andree -sub rsa4096/9437860BAA89B603 2015-09-09 [E] [expires: 2019-08-17] +uid Matthias Andree +sub rsa4096/9437860BAA89B603 2015-09-09 [E] [expires: 2021-09-07] ]]> From owner-svn-doc-all@freebsd.org Mon Sep 2 19:26:45 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7CF7CE6209; Mon, 2 Sep 2019 19:26:45 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Mg7T2NLvz4C1s; Mon, 2 Sep 2019 19:26:45 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 34FC01EE32; Mon, 2 Sep 2019 19:26:45 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x82JQjCv079514; Mon, 2 Sep 2019 19:26:45 GMT (envelope-from linimon@FreeBSD.org) Received: (from linimon@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x82JQjIn079513; Mon, 2 Sep 2019 19:26:45 GMT (envelope-from linimon@FreeBSD.org) Message-Id: <201909021926.x82JQjIn079513@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: linimon set sender to linimon@FreeBSD.org using -f From: Mark Linimon Date: Mon, 2 Sep 2019 19:26:45 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53362 - head/en_US.ISO8859-1/articles/committers-guide X-SVN-Group: doc-head X-SVN-Commit-Author: linimon X-SVN-Commit-Paths: head/en_US.ISO8859-1/articles/committers-guide X-SVN-Commit-Revision: 53362 X-SVN-Commit-Repository: doc 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.29 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, 02 Sep 2019 19:26:45 -0000 Author: linimon Date: Mon Sep 2 19:26:44 2019 New Revision: 53362 URL: https://svnweb.freebsd.org/changeset/doc/53362 Log: Wiki account issues have been delegated to wiki-admin@FreeBSD.org. Approved by: "just fix it" Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml Modified: head/en_US.ISO8859-1/articles/committers-guide/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/committers-guide/article.xml Mon Sep 2 18:29:00 2019 (r53361) +++ head/en_US.ISO8859-1/articles/committers-guide/article.xml Mon Sep 2 19:26:44 2019 (r53362) @@ -2173,7 +2173,7 @@ freebsd-mfc-after = 2 weeks account can follow instructions on the AboutWiki Page to obtain one. Contact - clusteradm@FreeBSD.org if you need help + wiki-admin@FreeBSD.org if you need help with your Wiki account. From owner-svn-doc-all@freebsd.org Tue Sep 3 08:57:16 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 20A4BD2F73; Tue, 3 Sep 2019 08:57:16 +0000 (UTC) (envelope-from adridg@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46N16g71Nlz43hx; Tue, 3 Sep 2019 08:57:15 +0000 (UTC) (envelope-from adridg@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D41CF315; Tue, 3 Sep 2019 08:57:15 +0000 (UTC) (envelope-from adridg@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x838vFgr069720; Tue, 3 Sep 2019 08:57:15 GMT (envelope-from adridg@FreeBSD.org) Received: (from adridg@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x838vFkX069719; Tue, 3 Sep 2019 08:57:15 GMT (envelope-from adridg@FreeBSD.org) Message-Id: <201909030857.x838vFkX069719@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: adridg set sender to adridg@FreeBSD.org using -f From: Adriaan de Groot Date: Tue, 3 Sep 2019 08:57:15 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53363 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: adridg X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53363 X-SVN-Commit-Repository: doc 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.29 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, 03 Sep 2019 08:57:16 -0000 Author: adridg (ports committer) Date: Tue Sep 3 08:57:15 2019 New Revision: 53363 URL: https://svnweb.freebsd.org/changeset/doc/53363 Log: adridg.key: Bump expiration to 18 months Modified: head/share/pgpkeys/adridg.key Modified: head/share/pgpkeys/adridg.key ============================================================================== --- head/share/pgpkeys/adridg.key Mon Sep 2 19:26:44 2019 (r53362) +++ head/share/pgpkeys/adridg.key Tue Sep 3 08:57:15 2019 (r53363) @@ -3,17 +3,11 @@ sh addkey.sh adridg 7FEA3DA6169C77D6 ; --> uid Adriaan de Groot uid Adriaan de Groot -sub dsa2048/128F00873E05AF1D 2017-06-23 [S] [expires: 2019-06-23] - Key fingerprint = E7C3 1EAE 243D 7984 15BC EF00 128F 0087 3E05 AF1D -sub dsa2048/32EE545A3E08534F 2017-06-23 [S] [expires: 2019-06-23] - Key fingerprint = D514 1A11 B0FE FAD1 FCBE 262B 32EE 545A 3E08 534F -sub rsa4096/F8B7B475F85D8C7A 2018-06-22 [E] [expires: 2019-06-22] - Key fingerprint = E32E 8CDD F2F1 E0C1 FFCC 74A6 F8B7 B475 F85D 8C7A sub rsa4096/5A80DEF53ED6FFB2 2019-06-13 [S] [expires: 2020-06-12] Key fingerprint = 52AF A9BE E0FE 37CF EF55 6FBE 5A80 DEF5 3ED6 FFB2 sub rsa4096/8A6094B85BAE0201 2019-06-13 [E] [expires: 2020-06-12] @@ -210,18 +204,18 @@ MXXgIGbCZ8SFU1Ab3MlfocN06465SZQ9Gj9QipkFFrkhcaM6sJgPNV c8zqz3UU3oycmZo3ymnpGXgcwoKQmMg0meX0NSkAXo1XeRr6XIpLuuEnI/tDVyFL GaP+Dt7Zs9Bwrv92KtS5e8/NqU5tu7gk5TCLTSNu+WkimvLrr9glPReJAlcEEwEI AEECGwMFCwkIBwMFFQoJCAsFFgIDAQACHgECF4ACGQEWIQQArNFeJaef7gKLDuV/ -6j2mFpx31gUCXQJcbgUJB4d7KQAKCRB/6j2mFpx31h47D/45MABckTUUmNcKZPgU -50XWseTzTc4b2fUZBtE3pjGqhw+yNRFeBQiV5veZiptDDyPcMzp384oLcfDP6anz -nYVUIJqw30rWK43fBckzStXt0NZ1B95mdIUqOSIgaICnSs2HDCfrsab2OONW6SXr -ZqsYVJY6EHcGUgPy0pUtvbbxsBD0ziArgbBR57UDOCDn8rwS7YlZfBz43UUMb+Ky -KXlJNgyzj3Bd5qPn/sUw1JHL/biHIOPiK+ZTpAjq6lo7bI6/R/1PsEqsyNOEV4jg -XurCZLCkBi/G3OTCBewVkVHOURhYORd5z2OpZ5K98ltY4h9+71gKWk26CgjddlGL -g6JCu3f/Pabu8t1KVMPuxxl5DNFvD0B5Sfnxmayk9JgsxCJbtuwGktSSo0NZw/hz -9PSXqBkkXJnTXtvdFRirXuYMKoiTfP1PniS4RvYQYgEXS+l+msUYoVVkmUq+pcTH -IcudPAdhq+mL7H3i8GzKKFWIpQHqfy1bih6RsAY2+EDY4iuYoGBFp7KNt5pGQTT7 -do+tzjvlwh5uQbl/htiV1krTNovR0uop1cGBIcJCRd1yOuiMJxEsy7oI58Adl/xQ -J9CvfwzFshKKPp0NtoDbET8j9wrqJvXGRpTDspUtL2omYprPMHFQ/7Y7/3GSwsvR -Sqb4MZPNjrDe5W8cVuT47GEwAbQrQWRyaWFhbiBkZSBHcm9vdCA8YWRyaWFhbkBi +6j2mFpx31gUCXW4pkgUJCNn+zQAKCRB/6j2mFpx31lNZD/9POiSqIWB2EXxN1I8w +84JI0FDfDdjdfTJI49KNDXS0Tf/9YW0hdpiDGMy6DkAcgQA63rykvQ8wcbELJCuQ +Sgeq1dVFfkOsySNJb5TZCAcKuq+JfDAsWQw5W/gIwYGlHjNYjRvzJDRH3SZiQSk7 +IteaNL8kwq5ZJPi1iXcgjA2PRavyvZRuVhzu6JWDe4ZeXwQxBaxetTxd85+eG3to +ZbaAAonYoXRpFcFYq20GEXSAjuiiwy2UW8GouMk8xEaa40mJLiannXVmB13ZSHBJ +IyGLoa85LHfHfumpPa9lclT4zwfNTUr8ZQ9r80ixYFmWIn9g71BsD/RhNDQZZNA3 +UhOUr08SQmc4xiR1n4IorgoettcbuyvgnkMkfyO7nQAiV/7XQjPxcmkH5opNBAzn +d8meoW2K6d//6zIjzmxOC3vzPTFM9izlLMwfeNncah89DZFPXMhbPi0yDZdz/AcM +0y+dAu2cMH7uYL1nlIp9Jc6lJ3fbBBqtaVpeFTIyYc+2KlNuAfwROltVq0rVBYUj +pBIrKep/8/xLG3vN5CsIb0rJgB+oy6cG+03txQorRj3uLL0sdCTOebU0m39fVuKN +/w5PgDPw6QBnJFNVBBsHTnOLY4z0nB7ElQ2c+FVARabNCyPuhSb8G5XUQnr9P5c7 +MNQvzLW6YQKMKtoZ/PYTLRxHnLQrQWRyaWFhbiBkZSBHcm9vdCA8YWRyaWFhbkBi aW9uaWNtdXR0b24ub3JnPokCPQQTAQgAJwUCV1wW5wIbAwUJA8JnAAULCQgHAwUV CgkICwUWAgMBAAIeAQIXgAAKCRB/6j2mFpx31mIzEACj+oXCk5QZ7NLxa13Uwone h2kTo+8bMhtGfPK8uIJhSM3JQ6GbxfbXEsIgUWQMz7bX5h8zlZsEsOXC/OeTbPTn @@ -369,32 +363,32 @@ u4VybIBp3JosU6o5YAjsedPnAjpmEXVyyyZ++xPM/efP8ZaEz5G57G Ob1zz7zrESdZTWMogAY+FnWV265H5uP1oPmexi6q/sK6a5+uAr1kuct/8Z/uZmoN ZjqcFS+U5b8K6sWjO4EE9hF4JZnEVKUajuWX+KChSIWtaksqrLDN0xBxY7PCRmPW XDS49heDqyfdx3BGsXiKK7GC5x4kRWPzmD0Z6/sniQJUBBMBCAA+AhsDBQsJCAcD -BRUKCQgLBRYCAwEAAh4BAheAFiEEAKzRXiWnn+4Ciw7lf+o9phacd9YFAl0CXG4F -CQeHeykACgkQf+o9phacd9b83A//XKc42k1eqsUTY5JejKkWudd4QTVlKHUniDKY -G/zEAz4q6vBiJNjU1iAQZ3ZQSzN8xonwzmlRUjGMnBCAIxXht0nzuUREvF1ZHB2K -7iDxBPTmAIVTlqxTsL1PaIPqpGzOmrwWF2qB/O2ESDm/RPqzqFd2trsz/mdkRmre -y3n+UUKg4rByOvGrW/w7JFLc+2PhzBDdAL+ADu7WuviAv1Li5ixkuSGleXgM60N1 -DE0avc3fyU8o1NdsZ5oWTryWFMK6Hwc1fojE/m//5EtY5L1b+v+6VJEKd5gYKTGj -NJ25LB3c0NRK51Yjp9AwinYfEbTVBGbuXWqQ7oMNR4hf4F3Bh3krTj7lmMqfnzSM -re7PI8/YpU6uEy88Q7Z2PB0WG2RFu20k0s6LcnUcadNWNSm2hcnXJqg7cu/Kbxd6 -OR4hdzno0fEkdp3f9McSEB0RjxsT5MPyTfHlSlPcSSlI379m8mqw0KdFwjCodpDO -OFp6Sp4zUwTl1MKekfAwxzPhzX/1jC4oq2O5WEurR2Y3vKT1YuQXPHRR+hs6aGLd -VW9WHrmsv4Aq1XJAoP8o69nIGtPeNZH9GVHo0582YTYc0DBncMteosRH3/pB+/t0 -OBpNIi2LUI7UN8RErRHm0nF3skwntYnuW4jsOMr9BDOBzS5IAsIbrruChhxLNzcv -R+43c0q0JUFkcmlhYW4gZGUgR3Jvb3QgPGFkcmlkZ0BmcmVlYnNkLm9yZz6JAlQE +BRUKCQgLBRYCAwEAAh4BAheAFiEEAKzRXiWnn+4Ciw7lf+o9phacd9YFAl1uKZcF +CQjZ/s0ACgkQf+o9phacd9b1/A/+LfaN6n8LQIuj7tHtNtvieboFKLAecbQGsalW +JC4HTsdwL5HcJjQFta7w7gYdpHGgRaeUlUKCLDWK4tIvtg+VrQQ9v9OXElBenVhm +8uoFS8jiMzODy1DzK9Z4/RmY8ALMPIfxFaGIzFNbQ17cMm4dKpBTmDzooc1TnkmL +hZJUemmV4m7NtUJI7v2ngR526MPfwIbfggpjpHHuwjfeegey7dTQQoMthyZQ6qZ6 +4S/GTTknz5y57oiNdbnF5Sxi/inhfo0l+Q7qsjt9hMWDCR7LP0UA8LusK/RLrWcK +HN5pHJFaWB0c51+0wcEmwWSSEk+gBiHe8jxY6QFHv4hZJ90RkDbwU7NY+vTSKY9U +Du4Pt+eyYBhiFI6y4k5bHI1JlLCrJnI9oWRGu9FBkHe2vk3WtAYl+ef8uXeR25oZ +gqA9F1WgYY+N9ar26Jxod0Cqim2HUSsPbFASlaRuKroepMJa5y5YJbGP6j5gBcjI +BAmPgt+axWgvWyCZuGecYe8mI2G9fM7V4XW9LiVCiy9aeF2pwQ1ZPsrC+wBe2fM6 +865k9KydVgyjH1UpmVVPXd+aK8Q9/xyxJGH34To0SuzngJuOWF6D9SFqwaXaWy69 +r31MCmSB9neMF3abKzIEDI2L3gk6MmcEjxwwZvOXzJWrIvOXbEo2nzQn+oIA82td +qvk+kl60JUFkcmlhYW4gZGUgR3Jvb3QgPGFkcmlkZ0BmcmVlYnNkLm9yZz6JAlQE EwEIAD4CGwMFCwkIBwMFFQoJCAsFFgIDAQACHgECF4AWIQQArNFeJaef7gKLDuV/ -6j2mFpx31gUCXQJcbgUJB4d7KQAKCRB/6j2mFpx31gBaEACwdRdM1NuktPYDQo5d -t82cPy2Mh3VwMbb71QgnWhS/Dx5s4ugMGqbDSNiFCRc3R6bSLwYVL5AxpvxFeA6A -Aexyn8J65eoXMzuYTH0qMyF1D7Bv4Zp2Ogps03IrduEMnlCe56TNBdYKTvwBb3VW -R1y92K6kKSYpczatOZH1k2UNAGwP8lOakY9AOVwuU5o0KF6jcfdjgZRzOXL9FFXx -oZlGXkLum1mbwdTv9Q50Z4BvFxSVT99vizYnEaPVXY/AdxeqkAu2zI22f/spH9Il -vAyy9jGPnlyITzkTFSyCOsPE5uS3ivlMOvA3vfY3igeGRhXkwEpDzIkWOLsJC5m4 -yX10388hg5/v4SQ/gnorZGNsGGfKKgyV8o1M0x246ycC8ArjFIejB8JqI78JlXKi -Jk9RQ5vbWQa+7GHVe0ct3GRifo064gwcOiZWWZ3/BU4l92hTWuSNQDKk8IPektjB -PbhyYygslEIqokvmbXIa1Ail/2Pq/T6O/QTDxQ19moIkUP4V6KTNIwbOsQOjJc0A -kR+8RhlczWF9ZzmiT4LPE20WpU1RI0d32ucQbl0lh2BwXvJG/iqz1587ZWOQZdOb -aMwpw/K1eaVMGqwx4RvATNIKFwZtMJAZkIhUo9RPl8R7JXFvedmT53JvicmcI44H -/vNbUHC2UmkJT3RVLdSO50XU97kCDQRXXBTFARAAqbwLfmKUT62+r9lIP34Wdr6O +6j2mFpx31gUCXW4plwUJCNn+zQAKCRB/6j2mFpx31r/bD/93Bsy938aMorYJeiEk +H59BBItMQjDnJw+LNUZOTAcCyx0NS1Ds2RNdeo79vyMd+rsYoDZj8B3vvMDarVnD +MjO8xdAUzBTqjHjJDmwaEldJIrec01aZWZCosN4uxkXNf4sIvFgDIH+LfwnB2uPI +Ds/3XFoFKB0XzQSp4YlA7Af6/zO7BCkUvCsgR8DNdFuOIAVVwcrvxnkgHLbA0+7i +zlgQKWsdK7lbFTTUh99s2nLCQ1AI0GK/Hv1I0kz5i6EHq6qKv/bZc8IjItS3m8BJ +AHA24dICkkenmwgeaVwrpPh3dVU7vORn7K2K8npVhAb0wZpbLvUJvFfJbfXtPrcG +PeWbQdNX1UiKO17qIEW+hw/lddRqrYYyd8i3pW7vQyv72fYAG+3BjtCgNq6cnDvj +rv7Bs9Kyr8RCrjOg2QOfn185bOYqEVSfh2NFzehdRnDz96h1MOtUHEIFtwQOE2Lp +fU7uaBzEPDt5b7GPaLkoqIwwEq27GhIBTOv0CC3zrc//QTHBe4M5xrQTLxUqgq2Q +HRrW4g5KX8kyHPeNyidVlMguXvTX8Iv+9AeHZzRpn5s5AuFh6/9c9hfiXxqIxAgk +FczqwQkFFoMUdP5zbMpJbahtjp0GRxX2iy2VwQFH/5qDAnV386L3/SaZcRMcSFca +z1fmPVrYDzfofhxalzeQJlbCf7kCDQRXXBTFARAAqbwLfmKUT62+r9lIP34Wdr6O QxZDiO49qbXUphPfyz35CNWx93g598fOOJXyw9Z3yV+cJpQY2DMGGZVf7lG0W6M3 Al6XHarJlVRxVu2BIQQJPVrWEsg3gNlNUyxYxauYni5AK0c3HELnk65WQKgW96L/ UQG+XfJMfBiini6P76xrViHtiRsxgRNME573xZyiSZ2eNiwy8JDVMYwRVcrar+LJ @@ -561,6 +555,6 @@ akjrgQszfJEzEHKFZ9lTQyCC0Tu18lNDqn6DY/j3fA15QlzrTSe/4C nwZdoNwWkpq3221jHz19PTvTYGzvpMgI3Tmb7aYm5lPT656bbnA5JO9FSAgvvUrM N6xjdp+T2qiu1IAzKNxCalHw4oRwjSOe7jR4pkjHaMm9LHHL2Fi7j8D7p/eA37rz lhi+UTQKzTd9Y3/vwa8eoF41I+ey8eOqpBO8MQ== -=vn1P +=m7i/ -----END PGP PUBLIC KEY BLOCK----- ]]> From owner-svn-doc-all@freebsd.org Tue Sep 3 12:44:04 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8EF92D9EA2; Tue, 3 Sep 2019 12:44:04 +0000 (UTC) (envelope-from mjg@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46N68N2x7zz4Jnb; Tue, 3 Sep 2019 12:44:04 +0000 (UTC) (envelope-from mjg@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 482802DC1; Tue, 3 Sep 2019 12:44:04 +0000 (UTC) (envelope-from mjg@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x83Ci46K006460; Tue, 3 Sep 2019 12:44:04 GMT (envelope-from mjg@FreeBSD.org) Received: (from mjg@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x83Ci413006459; Tue, 3 Sep 2019 12:44:04 GMT (envelope-from mjg@FreeBSD.org) Message-Id: <201909031244.x83Ci413006459@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: mjg set sender to mjg@FreeBSD.org using -f From: Mateusz Guzik Date: Tue, 3 Sep 2019 12:44:04 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53364 - head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Group: doc-head X-SVN-Commit-Author: mjg X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Commit-Revision: 53364 X-SVN-Commit-Repository: doc 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.29 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, 03 Sep 2019 12:44:04 -0000 Author: mjg (src committer) Date: Tue Sep 3 12:44:03 2019 New Revision: 53364 URL: https://svnweb.freebsd.org/changeset/doc/53364 Log: Document OSVERSION 1300045. 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 3 08:57:15 2019 (r53363) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Tue Sep 3 12:44:03 2019 (r53364) @@ -446,6 +446,13 @@ is spelled &, < is < and > is >. 13.0-CURRENT after adding sysfs create/remove functions that handles multiple files in one call to the LinuxKPI. + + + 1300045 + 351729 + September 3, 2019 + 13.0-CURRENT after adding sysctlbyname system call + From owner-svn-doc-all@freebsd.org Tue Sep 3 21:04:50 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0C058D81CC; Tue, 3 Sep 2019 21:04:50 +0000 (UTC) (envelope-from jgh@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46NKG96CgPz4NFH; Tue, 3 Sep 2019 21:04:49 +0000 (UTC) (envelope-from jgh@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B50F98F08; Tue, 3 Sep 2019 21:04:49 +0000 (UTC) (envelope-from jgh@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x83L4nhC019100; Tue, 3 Sep 2019 21:04:49 GMT (envelope-from jgh@FreeBSD.org) Received: (from jgh@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x83L4n7T019099; Tue, 3 Sep 2019 21:04:49 GMT (envelope-from jgh@FreeBSD.org) Message-Id: <201909032104.x83L4n7T019099@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: jgh set sender to jgh@FreeBSD.org using -f From: Jason Helfman Date: Tue, 3 Sep 2019 21:04:49 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53365 - head/en_US.ISO8859-1/books/porters-handbook/uses X-SVN-Group: doc-head X-SVN-Commit-Author: jgh X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/porters-handbook/uses X-SVN-Commit-Revision: 53365 X-SVN-Commit-Repository: doc 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.29 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, 03 Sep 2019 21:04:50 -0000 Author: jgh Date: Tue Sep 3 21:04:49 2019 New Revision: 53365 URL: https://svnweb.freebsd.org/changeset/doc/53365 Log: - address misleading example PR: 240301 Reported by: pauamma@gundo.com 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 Tue Sep 3 12:44:03 2019 (r53364) +++ head/en_US.ISO8859-1/books/porters-handbook/uses/chapter.xml Tue Sep 3 21:04:49 2019 (r53365) @@ -52,7 +52,7 @@ Adding an Argument - USES= gmake:lite + USES= tar:xz From owner-svn-doc-all@freebsd.org Wed Sep 4 02:10:18 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CA91EE11B0; Wed, 4 Sep 2019 02:10:18 +0000 (UTC) (envelope-from meta@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46NS2f50DNz4fvQ; Wed, 4 Sep 2019 02:10:18 +0000 (UTC) (envelope-from meta@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8EB65C6EF; Wed, 4 Sep 2019 02:10:18 +0000 (UTC) (envelope-from meta@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x842AItZ097546; Wed, 4 Sep 2019 02:10:18 GMT (envelope-from meta@FreeBSD.org) Received: (from meta@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x842AIqQ097545; Wed, 4 Sep 2019 02:10:18 GMT (envelope-from meta@FreeBSD.org) Message-Id: <201909040210.x842AIqQ097545@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: meta set sender to meta@FreeBSD.org using -f From: Koichiro Iwao Date: Wed, 4 Sep 2019 02:10:18 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53366 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: meta X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53366 X-SVN-Commit-Repository: doc 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.29 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, 04 Sep 2019 02:10:18 -0000 Author: meta (ports committer) Date: Wed Sep 4 02:10:18 2019 New Revision: 53366 URL: https://svnweb.freebsd.org/changeset/doc/53366 Log: Refresh my GPG key Modified: head/share/pgpkeys/meta.key Modified: head/share/pgpkeys/meta.key ============================================================================== --- head/share/pgpkeys/meta.key Tue Sep 3 21:04:49 2019 (r53365) +++ head/share/pgpkeys/meta.key Wed Sep 4 02:10:18 2019 (r53366) @@ -3,11 +3,11 @@ sh addkey.sh meta 9F72CDBC01BF10EB ; --> uid Koichiro IWAO -sub rsa4096/77C1E7C4CCDE08AA 2017-06-20 [E] [expires: 2019-06-20] +uid Koichiro Iwao +sub rsa4096/77C1E7C4CCDE08AA 2017-06-20 [E] [expires: 2023-06-12] ]]> From owner-svn-doc-all@freebsd.org Thu Sep 5 05:20:12 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E7673D95C8; Thu, 5 Sep 2019 05:20:12 +0000 (UTC) (envelope-from gshapiro@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46P8CJ6c8kz4GFZ; Thu, 5 Sep 2019 05:20:12 +0000 (UTC) (envelope-from gshapiro@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id ADCF1270CD; Thu, 5 Sep 2019 05:20:12 +0000 (UTC) (envelope-from gshapiro@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x855KC1q074654; Thu, 5 Sep 2019 05:20:12 GMT (envelope-from gshapiro@FreeBSD.org) Received: (from gshapiro@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x855KCdR074653; Thu, 5 Sep 2019 05:20:12 GMT (envelope-from gshapiro@FreeBSD.org) Message-Id: <201909050520.x855KCdR074653@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gshapiro set sender to gshapiro@FreeBSD.org using -f From: Gregory Neil Shapiro Date: Thu, 5 Sep 2019 05:20:12 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53367 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: gshapiro X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53367 X-SVN-Commit-Repository: doc 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.29 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, 05 Sep 2019 05:20:13 -0000 Author: gshapiro (src committer) Date: Thu Sep 5 05:20:12 2019 New Revision: 53367 URL: https://svnweb.freebsd.org/changeset/doc/53367 Log: Update my PGP key after bumping the expiration date. Modified: head/share/pgpkeys/gshapiro.key Modified: head/share/pgpkeys/gshapiro.key ============================================================================== --- head/share/pgpkeys/gshapiro.key Wed Sep 4 02:10:18 2019 (r53366) +++ head/share/pgpkeys/gshapiro.key Thu Sep 5 05:20:12 2019 (r53367) @@ -3,13 +3,13 @@ sh addkey.sh gshapiro 7B529648EE857264 ; --> uid Gregory Neil Shapiro uid Gregory Neil Shapiro -sub 4096R/E06797B94ECB7FF3 2017-08-27 [expires: 2019-08-27] -sub 4096R/389DBDBF7CB42F23 2017-08-27 [expires: 2019-08-27] +sub 4096R/E06797B94ECB7FF3 2017-08-27 [expires: 2021-08-25] +sub 4096R/389DBDBF7CB42F23 2017-08-27 [expires: 2021-08-25] ]]> From owner-svn-doc-all@freebsd.org Thu Sep 5 08:45:22 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 869FADECFB; Thu, 5 Sep 2019 08:45:22 +0000 (UTC) (envelope-from beat@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PDm22wYQz4Qj2; Thu, 5 Sep 2019 08:45:22 +0000 (UTC) (envelope-from beat@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 486F61755; Thu, 5 Sep 2019 08:45:22 +0000 (UTC) (envelope-from beat@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x858jMhO098262; Thu, 5 Sep 2019 08:45:22 GMT (envelope-from beat@FreeBSD.org) Received: (from beat@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x858jMYR098261; Thu, 5 Sep 2019 08:45:22 GMT (envelope-from beat@FreeBSD.org) Message-Id: <201909050845.x858jMYR098261@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: beat set sender to beat@FreeBSD.org using -f From: Beat Gaetzi Date: Thu, 5 Sep 2019 08:45:22 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53368 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: beat X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53368 X-SVN-Commit-Repository: doc 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.29 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, 05 Sep 2019 08:45:22 -0000 Author: beat (ports committer) Date: Thu Sep 5 08:45:21 2019 New Revision: 53368 URL: https://svnweb.freebsd.org/changeset/doc/53368 Log: Update my PGP key Modified: head/share/pgpkeys/beat.key Modified: head/share/pgpkeys/beat.key ============================================================================== --- head/share/pgpkeys/beat.key Thu Sep 5 05:20:12 2019 (r53367) +++ head/share/pgpkeys/beat.key Thu Sep 5 08:45:21 2019 (r53368) @@ -1,42 +1,65 @@ -sub rsa2048/5D496E43DD25AFED 2015-02-16 [expires: 2018-02-15] +pub rsa4096/ADA4DD51C7914099 2019-09-05 [SC] [expires: 2022-09-04] + Key fingerprint = E0AB 0418 401D F150 4C5E 9E06 ADA4 DD51 C791 4099 +uid Beat Gaetzi +sub rsa4096/63C91DF5F37C26DE 2019-09-05 [E] [expires: 2022-09-04] ]]> From owner-svn-doc-all@freebsd.org Thu Sep 5 15:28:23 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9C765EA86D; Thu, 5 Sep 2019 15:28:23 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PPj33fvPz3Q47; Thu, 5 Sep 2019 15:28:23 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 60C4863F7; Thu, 5 Sep 2019 15:28:23 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x85FSNxp039735; Thu, 5 Sep 2019 15:28:23 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x85FSNwO039734; Thu, 5 Sep 2019 15:28:23 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201909051528.x85FSNwO039734@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Thu, 5 Sep 2019 15:28:23 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53369 - head/en_US.ISO8859-1/books/arch-handbook X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/arch-handbook X-SVN-Commit-Revision: 53369 X-SVN-Commit-Repository: doc 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.29 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, 05 Sep 2019 15:28:23 -0000 Author: bcr Date: Thu Sep 5 15:28:22 2019 New Revision: 53369 URL: https://svnweb.freebsd.org/changeset/doc/53369 Log: Fix some igor warings by wrapping long lines. No functional changes. Modified: head/en_US.ISO8859-1/books/arch-handbook/book.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/book.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/book.xml Thu Sep 5 08:45:21 2019 (r53368) +++ head/en_US.ISO8859-1/books/arch-handbook/book.xml Thu Sep 5 15:28:22 2019 (r53369) @@ -11,12 +11,16 @@ $FreeBSD$ --> - - &os; Architecture Handbook - + - The FreeBSD Documentation Project + + &os; Architecture Handbook + The FreeBSD Documentation + Project + $FreeBSD$ @@ -53,10 +57,13 @@ helping with this project, send email to the &a.doc;. The latest version of this document is always available - from the FreeBSD World - Wide Web server. It may also be downloaded in a - variety of formats and compression options from the FreeBSD FTP server - or one of the numerous mirror sites. + from the FreeBSD + World Wide Web server. It may also be downloaded in + a variety of formats and compression options from the FreeBSD + FTP server or one of the numerous mirror + sites. @@ -100,14 +107,6 @@ architecture. - - * IA-64 - - Talk about the architectural specifics of - FreeBSD/ia64. - - - * SPARC64 @@ -138,10 +137,33 @@ - MarshallKirkMcKusick - KeithBostic - MichaelJKarels - JohnSQuarterman + + + Marshall + Kirk + McKusick + + + + + Keith + Bostic + + + + + Michael + J + Karels + + + + + John + S + Quarterman + + @@ -152,10 +174,12 @@ 0-201-54979-4 - Addison-Wesley Publishing Company, Inc. + Addison-Wesley Publishing Company, + Inc. - The Design and Implementation of the 4.4 BSD Operating System + The Design and Implementation of the 4.4 BSD + Operating System 1-2 From owner-svn-doc-all@freebsd.org Thu Sep 5 16:59:09 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 56047ECCFA; Thu, 5 Sep 2019 16:59:09 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PRjn1MxWz41Tn; Thu, 5 Sep 2019 16:59:09 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 133C97439; Thu, 5 Sep 2019 16:59:09 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x85Gx8ND093657; Thu, 5 Sep 2019 16:59:08 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x85Gx8dA093656; Thu, 5 Sep 2019 16:59:08 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201909051659.x85Gx8dA093656@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Thu, 5 Sep 2019 16:59:08 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53370 - head/en_US.ISO8859-1/books/arch-handbook/sound X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/arch-handbook/sound X-SVN-Commit-Revision: 53370 X-SVN-Commit-Repository: doc 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.29 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, 05 Sep 2019 16:59:09 -0000 Author: bcr Date: Thu Sep 5 16:59:08 2019 New Revision: 53370 URL: https://svnweb.freebsd.org/changeset/doc/53370 Log: Clean up some errors from textproc/igor by wrapping long lines. Event: vBSDcon Hackathon Modified: head/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml Thu Sep 5 15:28:22 2019 (r53369) +++ head/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml Thu Sep 5 16:59:08 2019 (r53370) @@ -4,16 +4,23 @@ $FreeBSD$ --> - - Sound Subsystem + + + Sound Subsystem + - Jean-FrancoisDockesContributed by + + + Jean-Francois + Dockes + + Contributed by + - - - Introduction @@ -96,7 +103,9 @@ Probing, Attaching, etc. Sound drivers probe and attach in almost the same way as any - hardware driver module. You might want to look at the ISA or PCI specific sections of the handbook for + hardware driver module. You might want to look at the ISA or PCI specific sections of the handbook for more information. However, sound drivers differ in some ways: @@ -104,9 +113,9 @@ They declare themselves as pcm - class devices, with a - struct snddev_info device private - structure: + class devices, with a struct snddev_info device + private structure: static driver_t xxx_driver = { "pcm", @@ -117,8 +126,11 @@ DRIVER_MODULE(snd_xxxpci, pci, xxx_driver, pcm_devclass, 0, 0); MODULE_DEPEND(snd_xxxpci, snd_pcm, PCM_MINVER, PCM_PREFVER,PCM_MAXVER); - Most sound driversdevice - driverssound + Most sound drivers + + device drivers + sound + need to store additional private information about their device. A private data structure is usually allocated in the attach routine. Its address is passed to @@ -134,7 +146,8 @@ The sound driver attach routine should declare its MIXER or AC97 interface to pcm by calling mixer_init(). For a MIXER interface, - this causes in turn a call to xxxmixer_init(). + this causes in turn a call to xxxmixer_init(). @@ -196,7 +209,8 @@ Interfaces The interface between the pcm core - and the sound drivers is defined in terms of kernel objects. + and the sound drivers is defined in terms of kernel objects. There are two main interfaces that a sound driver will usually provide: CHANNEL and either @@ -235,11 +249,12 @@ For sound data transfers, the pcm core and the sound drivers communicate through a shared memory area, described by a - struct snd_dbuf. + struct + snd_dbuf. - struct snd_dbuf is private to - pcm, and sound drivers obtain - values of interest by calls to accessor functions + struct snd_dbuf is + private to pcm, and sound drivers + obtain values of interest by calls to accessor functions (sndbuf_getxxx()). The shared memory area has a size of @@ -253,7 +268,8 @@ pcm initially fills up the - buffer, then calls the sound driver's + buffer, then calls the sound driver's xxxchannel_trigger() function with a parameter of PCMTRIG_START. @@ -273,8 +289,9 @@ chn_intr() arranges to copy new data to the area that was transferred to the device (now - free), and make appropriate updates to the - snd_dbuf structure. + free), and make appropriate updates to the snd_dbuf + structure. @@ -301,8 +318,8 @@ b is the address for the channel - struct snd_dbuf. It should be - initialized in the function by calling + struct snd_dbuf. + It should be initialized in the function by calling sndbuf_alloc(). The buffer size to use is normally a small multiple of the 'typical' unit transfer size for your device. @@ -491,10 +508,10 @@ The routine returns a pointer to a (usually - statically-defined) - pcmchan_caps structure (defined - in sound/pcm/channel.h. The - structure holds the minimum and maximum sampling + statically-defined) pcmchan_caps structure + (defined in sound/pcm/channel.h. + The structure holds the minimum and maximum sampling frequencies, and the accepted sound formats. Look at any sound driver for an example. @@ -626,7 +643,7 @@ xxxmixer_uninit() should ensure that all sound is muted and if possible mixer hardware - should be powered down + should be powered down. xxxmixer_reinit() should ensure that the mixer hardware is powered up and any settings not From owner-svn-doc-all@freebsd.org Thu Sep 5 17:28:51 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9DE48EE212; Thu, 5 Sep 2019 17:28:51 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PSN347rkz48Bm; Thu, 5 Sep 2019 17:28:51 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 713317A09; Thu, 5 Sep 2019 17:28:51 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x85HSpYg019120; Thu, 5 Sep 2019 17:28:51 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x85HSpG1019119; Thu, 5 Sep 2019 17:28:51 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201909051728.x85HSpG1019119@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Thu, 5 Sep 2019 17:28:51 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53371 - head/en_US.ISO8859-1/books/arch-handbook/locking X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/arch-handbook/locking X-SVN-Commit-Revision: 53371 X-SVN-Commit-Repository: doc 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.29 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, 05 Sep 2019 17:28:51 -0000 Author: bcr Date: Thu Sep 5 17:28:51 2019 New Revision: 53371 URL: https://svnweb.freebsd.org/changeset/doc/53371 Log: Fix errors reported by textproc/igor: - wrap long line - use tabs istead of spaces - straggling closing tags (like ) - add blank line after on previous line Event: vBSDcon FreeBSD Hackathon Modified: head/en_US.ISO8859-1/books/arch-handbook/locking/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/locking/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/locking/chapter.xml Thu Sep 5 16:59:08 2019 (r53370) +++ head/en_US.ISO8859-1/books/arch-handbook/locking/chapter.xml Thu Sep 5 17:28:51 2019 (r53371) @@ -5,12 +5,17 @@ $FreeBSD$ --> - + Locking Notes - SMP Next Generation Project + + SMP Next Generation Project + + This chapter is maintained by the FreeBSD SMP Next - Generation Project. + Generation Project. locking multi-processing @@ -41,7 +46,7 @@ Each mutex has several properties of interest: - + Variable Name The name of the struct mtx variable in @@ -97,8 +102,9 @@ A list of data structures or data structure members that this entry protects. For data structure members, the - name will be in the form of - structure name.member name. + name will be in the form of structure name.member name. @@ -114,17 +120,25 @@ Mutex List - locks - sched_lock + + locks + sched_lock + - locks - vm86pcb_lock + + locks + vm86pcb_lock + - locks - Giant + + locks + Giant + - locks - callout_lock + + locks + callout_lock + @@ -141,48 +155,80 @@ sched_lock - sched lock + sched lock + MTX_SPIN | - MTX_RECURSE - + MTX_RECURSE _gmonparam, cnt.v_swtch, cp_time, curpriority, - mtx.mtx_blocked, - mtx.mtx_contested, - proc.p_procq, - proc.p_slpq, - proc.p_sflag, - proc.p_stat, - proc.p_estcpu, - proc.p_cpticks - proc.p_pctcpu, - proc.p_wchan, - proc.p_wmesg, - proc.p_swtime, - proc.p_slptime, - proc.p_runtime, - proc.p_uu, - proc.p_su, - proc.p_iu, - proc.p_uticks, - proc.p_sticks, - proc.p_iticks, - proc.p_oncpu, - proc.p_lastcpu, - proc.p_rqindex, - proc.p_heldmtx, - proc.p_blocked, - proc.p_mtxname, - proc.p_contested, - proc.p_priority, - proc.p_usrpri, - proc.p_nativepri, - proc.p_nice, - proc.p_rtprio, + mtx.mtx_blocked, + mtx.mtx_contested, + proc.p_procq, + proc.p_slpq, + proc.p_sflag, + proc.p_stat, + proc.p_estcpu, + proc.p_cpticks + proc.p_pctcpu, + proc.p_wchan, + proc.p_wmesg, + proc.p_swtime, + proc.p_slptime, + proc.p_runtime, + proc.p_uu, + proc.p_su, + proc.p_iu, + proc.p_uticks, + proc.p_sticks, + proc.p_iticks, + proc.p_oncpu, + proc.p_lastcpu, + proc.p_rqindex, + proc.p_heldmtx, + proc.p_blocked, + proc.p_mtxname, + proc.p_contested, + proc.p_priority, + proc.p_usrpri, + proc.p_nativepri, + proc.p_nice, + proc.p_rtprio, pscnt, slpque, itqueuebits, @@ -194,8 +240,7 @@ idqueuebits, idqueues, switchtime, - switchticks - + switchticks setrunqueue, remrunqueue, @@ -214,8 +259,7 @@ astoff, astpending, calcru, - proc_compare - + proc_compare @@ -223,14 +267,11 @@ vm86pcb_lockvm86pcb lock - MTX_DEF - + MTX_DEF - vm86pcb - + vm86pcb - vm86_bioscall - + vm86_bioscall @@ -239,8 +280,7 @@ Giant MTX_DEF | - MTX_RECURSE - + MTX_RECURSEnearly everythinglots @@ -251,19 +291,18 @@ callout lock MTX_SPIN | - MTX_RECURSE - + MTX_RECURSE callfree, callwheel, nextsoftcheck, - proc.p_itcallout, - proc.p_slpcallout, + proc.p_itcallout, + proc.p_slpcallout, softticks, - ticks - - - + ticks + @@ -276,16 +315,23 @@ These locks provide basic reader-writer type functionality and may be held by a sleeping process. Currently they are backed by &man.lockmgr.9;. - locks - shared exclusive + + locks + shared exclusive +
Shared Exclusive Lock List - locks - allproc_lock - locks - proctree_lock + + locks + allproc_lock + + + locks + proctree_lock + + @@ -300,17 +346,20 @@ allproc zombproc pidhashtbl - proc.p_list - proc.p_hash - nextpid - + proc.p_list + proc.p_hash + nextpid + proctree_lock - proc.p_children - proc.p_sibling - + proc.p_children + proc.p_sibling @@ -320,7 +369,9 @@ Atomically Protected Variables - atomically protected variables + + atomically protected variables + An atomically protected variable is a special variable that is not protected by an explicit lock. Instead, all data @@ -332,7 +383,8 @@ - mtx.mtx_lock + mtx.mtx_lock From owner-svn-doc-all@freebsd.org Thu Sep 5 17:59:00 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 93D09EF0E7; Thu, 5 Sep 2019 17:59:00 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PT2r3SyDz4BHW; Thu, 5 Sep 2019 17:59:00 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 5921D7F7F; Thu, 5 Sep 2019 17:59:00 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x85Hx0DR037053; Thu, 5 Sep 2019 17:59:00 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x85Hx0XR037052; Thu, 5 Sep 2019 17:59:00 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201909051759.x85Hx0XR037052@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Thu, 5 Sep 2019 17:59:00 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53372 - head/en_US.ISO8859-1/books/arch-handbook/sysinit X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/arch-handbook/sysinit X-SVN-Commit-Revision: 53372 X-SVN-Commit-Repository: doc 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.29 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, 05 Sep 2019 17:59:00 -0000 Author: bcr Date: Thu Sep 5 17:58:59 2019 New Revision: 53372 URL: https://svnweb.freebsd.org/changeset/doc/53372 Log: Fix errors reported by textproc/igor: - wrap long line - use two spaces at sentence start - use tabs instead of spaces - space after content - straggling Event: vBSDcon FreeBSD Hackathon Modified: head/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.xml Thu Sep 5 17:28:51 2019 (r53371) +++ head/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.xml Thu Sep 5 17:58:59 2019 (r53372) @@ -4,26 +4,38 @@ $FreeBSD$ --> - + The SYSINIT Framework - SYSINIT - dynamic initialization - kernel initialization - dynamic - kernel modules - kernel linker + + SYSINIT + + + dynamic initialization + + + kernel initialization + dynamic + + + kernel modules + + + kernel linker + SYSINIT is the framework for a generic call sort and dispatch - mechanism. FreeBSD currently uses it for the dynamic - initialization of the kernel. SYSINIT allows FreeBSD's kernel + mechanism. FreeBSD currently uses it for the dynamic + initialization of the kernel. SYSINIT allows FreeBSD's kernel subsystems to be reordered, and added, removed, and replaced at kernel link time when the kernel or one of its modules is loaded without having to edit a statically ordered initialization routing - and recompile the kernel. This system also allows kernel modules, + and recompile the kernel. This system also allows kernel modules, currently called KLD's, to be separately compiled, linked, and initialized at boot time and loaded even - later while the system is already running. This is accomplished + later while the system is already running. This is accomplished using the kernel linker and linker sets. @@ -32,13 +44,13 @@ - Linker Set - - A linker technique in which the linker gathers - statically declared data throughout a program's source files - into a single contiguously addressable unit of - data. - + Linker Set + + A linker technique in which the linker gathers + statically declared data throughout a program's source + files into a single contiguously addressable unit of + data. + @@ -51,24 +63,25 @@ SYSINIT relies on the ability of the linker to take static data declared at multiple locations throughout a program's source and group it together as a single contiguous chunk of - data. This linker technique is called a linker - set. SYSINIT uses two linker sets to maintain two data + data. This linker technique is called a linker + set. SYSINIT uses two linker sets to maintain two data sets containing each consumer's call order, function, and a pointer to the data to pass to that function. SYSINIT uses two priorities when ordering the functions for execution. The first priority is a subsystem ID giving an - overall order for SYSINIT's dispatch of functions. Current predeclared - ID's are in <sys/kernel.h> in the enum - list sysinit_sub_id. The second priority used - is an element order within the subsystem. Current predeclared - subsystem element orders are in + overall order for SYSINIT's dispatch of functions. Current + predeclared ID's are in + <sys/kernel.h> in the enum + list sysinit_sub_id. The second priority + used is an element order within the subsystem. Current + predeclared subsystem element orders are in <sys/kernel.h> in the enum list sysinit_elem_order. - pseudo-devices + pseudo-devices - There are currently two uses for SYSINIT. Function dispatch + There are currently two uses for SYSINIT. Function dispatch at system startup and kernel module loads, and function dispatch at system shutdown and kernel module unload. Kernel subsystems often use system startup SYSINIT's to initialize data @@ -77,11 +90,11 @@ Device drivers should avoid using SYSINIT() directly. Instead drivers for real devices that are part of a bus structure should use DRIVER_MODULE() to - provide a function that detects the device and, if it is present, - initializes the device. It will do a few things specific to - devices and then call SYSINIT() itself. - For pseudo-devices, which are not part of a bus structure, - use DEV_MODULE(). + provide a function that detects the device and, if it is + present, initializes the device. It will do a few things + specific to devices and then call SYSINIT() + itself. For pseudo-devices, which are not part of a bus + structure, use DEV_MODULE(). @@ -92,15 +105,15 @@ Interface - Headers + Headers - <sys/kernel.h> + <sys/kernel.h> - Macros + Macros - SYSINIT(uniquifier, subsystem, order, func, ident) + SYSINIT(uniquifier, subsystem, order, func, ident) SYSUNINIT(uniquifier, subsystem, order, func, ident) @@ -109,14 +122,13 @@ SYSUNINIT(uniquifier, subsystem, order, func, ident)Startup The SYSINIT() macro creates the - necessary SYSINIT data in SYSINIT's startup data set for - SYSINIT to sort and dispatch a function at system startup and - module load. SYSINIT() takes a uniquifier - that SYSINIT uses to identify the particular function dispatch - data, the subsystem order, the subsystem element order, the - function to call, and the data to pass the function. All - functions must take a constant pointer argument. - + necessary SYSINIT data in SYSINIT's startup data set for + SYSINIT to sort and dispatch a function at system startup and + module load. SYSINIT() takes a uniquifier + that SYSINIT uses to identify the particular function dispatch + data, the subsystem order, the subsystem element order, the + function to call, and the data to pass the function. All + functions must take a constant pointer argument. Example of a <literal>SYSINIT()</literal> @@ -138,9 +150,7 @@ void foo_arg(void *vdata) struct foo *foo = (struct foo *)vdata; foo_data(foo); } -SYSINIT(bar, SI_SUB_FOO, SI_ORDER_FOO, foo_arg, &foo_voodoo); - - +SYSINIT(bar, SI_SUB_FOO, SI_ORDER_FOO, foo_arg, &foo_voodoo); Note that SI_SUB_FOO and SI_ORDER_FOO need to be in the @@ -153,7 +163,8 @@ SYSINIT(bar, SI_SUB_FOO, SI_ORDER_FOO, foo_arg, &f handle tuning kernel parameters. - Example of Adjusting <literal>SYSINIT()</literal> Order + Example of Adjusting <literal>SYSINIT()</literal> + Order static void mptable_register(void *dummy __unused) @@ -171,8 +182,8 @@ SYSINIT(mptable_register, SI_SUB_TUNABLES - 1, SI_ORDE Shutdown The SYSUNINIT() macro behaves similarly - to the SYSINIT() macro except that it adds - the SYSINIT data to SYSINIT's shutdown data set. + to the SYSINIT() macro except that it adds + the SYSINIT data to SYSINIT's shutdown data set. Example of a <literal>SYSUNINIT()</literal> @@ -192,8 +203,7 @@ struct foo_stack foo_stack = { void foo_flush(void *vdata) { } -SYSUNINIT(barfoo, SI_SUB_FOO, SI_ORDER_FOO, foo_flush, &foo_stack); - +SYSUNINIT(barfoo, SI_SUB_FOO, SI_ORDER_FOO, foo_flush, &foo_stack); From owner-svn-doc-all@freebsd.org Thu Sep 5 18:42:54 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 70193D037E; Thu, 5 Sep 2019 18:42:54 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PV1V26lmz4Dp0; Thu, 5 Sep 2019 18:42:54 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 2BE698882; Thu, 5 Sep 2019 18:42:54 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x85Igr9h070628; Thu, 5 Sep 2019 18:42:53 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x85IgrrJ070627; Thu, 5 Sep 2019 18:42:53 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201909051842.x85IgrrJ070627@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Thu, 5 Sep 2019 18:42:53 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53373 - head/en_US.ISO8859-1/books/handbook/zfs X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/handbook/zfs X-SVN-Commit-Revision: 53373 X-SVN-Commit-Repository: doc 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.29 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, 05 Sep 2019 18:42:54 -0000 Author: bcr Date: Thu Sep 5 18:42:53 2019 New Revision: 53373 URL: https://svnweb.freebsd.org/changeset/doc/53373 Log: Fix two textproc/igor warnings: - extra space after content - a straggling Event: vBSDcon FreeBSD Hackathon 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 Thu Sep 5 17:58:59 2019 (r53372) +++ head/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Thu Sep 5 18:42:53 2019 (r53373) @@ -3365,7 +3365,7 @@ dedup = 1.05, compress = 1.11, copies = 1.00, dedup * This may sound obvious, but if it really were so obvious then we probably would not see so many cases of people clearly not doing this. If your changes are to the @@ -4103,9 +4115,7 @@ Relnotes: yes integrated into the &os; documentation. Current Tier 2 platforms are &arch.arm;, &arch.arm64;, - &arch.ia64; (through &os; 10), &arch.mips;, - &arch.pc98; (through &os; 11), - &arch.powerpc;, and &arch.sparc64;. + &arch.mips;, &arch.powerpc;, and &arch.sparc64;. @@ -4146,9 +4156,7 @@ Relnotes: yes project. All systems not otherwise classified into a support tier - are Tier 4 systems. The &arch.ia64; platform is transitioning - to Tier 4 status in &os; 11. The &arch.pc98; platform is - transitioning to Tier 4 status in &os; 12. + are Tier 4 systems. From owner-svn-doc-all@freebsd.org Thu Sep 5 19:36:06 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C9153D1649; Thu, 5 Sep 2019 19:36:06 +0000 (UTC) (envelope-from carlavilla@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PWBt4vdMz4HVx; Thu, 5 Sep 2019 19:36:06 +0000 (UTC) (envelope-from carlavilla@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8C78B91FD; Thu, 5 Sep 2019 19:36:06 +0000 (UTC) (envelope-from carlavilla@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x85Ja6Y7000800; Thu, 5 Sep 2019 19:36:06 GMT (envelope-from carlavilla@FreeBSD.org) Received: (from carlavilla@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x85Ja6Xv000798; Thu, 5 Sep 2019 19:36:06 GMT (envelope-from carlavilla@FreeBSD.org) Message-Id: <201909051936.x85Ja6Xv000798@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: carlavilla set sender to carlavilla@FreeBSD.org using -f From: Sergio Carlavilla Delgado Date: Thu, 5 Sep 2019 19:36:06 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53375 - head/es_ES.ISO8859-1/articles/problem-reports X-SVN-Group: doc-head X-SVN-Commit-Author: carlavilla X-SVN-Commit-Paths: head/es_ES.ISO8859-1/articles/problem-reports X-SVN-Commit-Revision: 53375 X-SVN-Commit-Repository: doc 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.29 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, 05 Sep 2019 19:36:06 -0000 Author: carlavilla Date: Thu Sep 5 19:36:06 2019 New Revision: 53375 URL: https://svnweb.freebsd.org/changeset/doc/53375 Log: PR: Update the traduction to the article problem-reports Approved by: gabor Obtained from: The FreeBSD Spanish Documentation Project Added: head/es_ES.ISO8859-1/articles/problem-reports/es_ES.po (contents, props changed) Modified: head/es_ES.ISO8859-1/articles/problem-reports/Makefile head/es_ES.ISO8859-1/articles/problem-reports/article.xml Modified: head/es_ES.ISO8859-1/articles/problem-reports/Makefile ============================================================================== --- head/es_ES.ISO8859-1/articles/problem-reports/Makefile Thu Sep 5 18:56:07 2019 (r53374) +++ head/es_ES.ISO8859-1/articles/problem-reports/Makefile Thu Sep 5 19:36:06 2019 (r53375) @@ -1,15 +1,19 @@ # +# The FreeBSD Documentation Project +# The FreeBSD Spanish Documentation Project +# # $FreeBSD$ -# $FreeBSDes: doc/es_ES.ISO8859-1/articles/problem-reports/Makefile,v 1.1 2004/10/08 23:06:08 carvay Exp $ # # Article: Writing FreeBSD Problem Reports +MAINTAINER=carlavilla@FreeBSD.org + DOC?= article -FORMATS?= html +FORMATS?= html html-split WITH_ARTICLE_TOC?= YES -INSTALL_COMPRESSED?= gz +INSTALL_COMPRESSED?=gz INSTALL_ONLY_COMPRESSED?= SRCS= article.xml Modified: head/es_ES.ISO8859-1/articles/problem-reports/article.xml ============================================================================== --- head/es_ES.ISO8859-1/articles/problem-reports/article.xml Thu Sep 5 18:56:07 2019 (r53374) +++ head/es_ES.ISO8859-1/articles/problem-reports/article.xml Thu Sep 5 19:36:06 2019 (r53375) @@ -1,992 +1,413 @@ - - -
- Cómo enviar informes de problemas de &os; - + + +
- $FreeBSD$ + + Escribiendo informes de problemas de FreeBSD - - &tm-attrib.freebsd; - &tm-attrib.cvsup; - &tm-attrib.ibm; - &tm-attrib.intel; - &tm-attrib.sparc; - &tm-attrib.sun; - &tm-attrib.general; + FreeBSD is a registered trademark of the FreeBSD Foundation. + IBM, AIX, OS/2, PowerPC, PS/2, S/390, and ThinkPad are trademarks of International Business Machines Corporation in the United States, other countries, or both. + Intel, Celeron, Centrino, Core, EtherExpress, i386, i486, Itanium, Pentium, and Xeon are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. + Sun, Sun Microsystems, Java, Java Virtual Machine, JDK, JRE, JSP, JVM, Netra, OpenJDK, Solaris, StarOffice, SunOS and VirtualBox are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries. + Many of the designations used by manufacturers and sellers to distinguish their products are claimed 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. + $FreeBSD$ + + $FreeBSD$ + - Este artículo describe cómo realizar y enviar - informes de errores para el proyecto &os; de la mejor forma - posible. - &trans.es.jrh; + Este artículo describe cómo realizar y enviar informes de problemas para el proyecto FreeBSD de la mejor forma posible. - Dag-ErlingSmørgravEscrito por - + Dag-Erling Smørgrav Contributed by - $FreeBSD$ + Mark Linimon + problem reports
- Introducción + Introducción - Una de las experiencias más fustrantes que se pueden - experimentar como usuario de software es aquella en la cual el - usuario se toma la molestia de rellenar un informe de problemas - detallado para observar tras un determinado espacio de tiempo - que dicho informe se cierra con una explicación corta y abrupta - como no es un error o PR erroneo. - De forma semejante, una de las experiencias más fustrantes que - puede experimentar un desarrollador de aplicaciones consiste en - verse inundado por una cantidad ingente de informes de errores - que en realidad vienen a ser solicitudes de - soporte o ayuda, o que contienen poca o ninguna información - sobre cúal es el problema y como se puede reproducir. + Una de las experiencias más frustrantes que uno puede tener como usuario de software es enviar un informe de problemas solo para que se cierre sumariamente con una explicación breve e inútil como no es un error o PR erróneo. De manera similar, una de las experiencias más frustrantes que puede experimentar un desarrollador de aplicaciones consiste en verse inundado por una cantidad ingente de informes de problemas que en realidad vienen a ser solicitudes de soporte o ayuda, o que contienen poca o ninguna información sobre cúal es el problema y cómo reproducirlo. - Este documento intenta describir cómo escribir informes de - problemas de calidad. Usted se preguntará cómo se pueden - escribir informes de problemas de calidad. Bien, para ir - directos al grano, un informe de problemas de calidad es aquél - que se puede analizar y tratar rápidamente, para mútua - satisfacción del usuario y del desarrollador. + Este documento intenta describir cómo escribir buenos informes de problemas. ¿Qué, se preguntará, es un buen informe de problemas? Bien, para ir directos al grano, un buen informe de problemas es aquél que se puede analizar y tratar rápidamente, para mutua satisfacción del usuario y del desarrollador. - Aunque el objetivo principal de este artículo se centra en - los informes de problemas de &os; la mayoría de los conceptos se - pueden aplicar bastante bien en otros proyectos de software. + Aunque el objetivo principal de este artículo se centra en los informes de problemas de FreeBSD, la mayoría de los conceptos se pueden aplicar bastante bien en otros proyectos de software. - Dése cuenta de que este artículo se organiza de forma - temática, no cronológicamente, de tal forma que se debe - leer el documento íntegro antes de enviar informes - de problemas. No debe tratarse como un tutorial del estilo paso - a paso.
+ Tenga en cuenta que este artículo está organizado temáticamente, no cronológicamente. Lea todo el documento antes de enviar un informe de problemas, en lugar de tratarlo como un tutorial paso a paso. +
- Cuándo enviar informes de problemas + Cuándo enviar informes de problemas - Existen varios tipos de problemas y no todos ellos se - merecen la creación de un informe de problemas. Por supuesto, - nadie es perfecto, y existirán ocasiones en las que estaremos - convencidos de haber encontrado un bug en un programa - cuando realmente hemos malinterpretado la sintaxis o el funcionamiento de - dicho programa, o simplemente hemos cometido un error - tipográfico en un fichero de configuración (aunque en este - último caso podría tratarse de un indicador de - documentación escasa o que la aplicación peca de una - gestión de errores defectuosa. Incluso - teniendo estos aspectos en cuenta existen varios casos en los cuales - el envío de un informe de problemas resulta claramente - no ser la mejor forma de proceder, ya que dicho - envío puede servir para frustrar tanto a quien envía el - informe como a quien desarrolló la aplicación. - Por el contrario, también existen casos - en los que puede resultar apropiado enviar un informe de problemas sobre - algo más aparte de bugs: una mejora o una solucitud - nuevas características, por citar un par de ejemplos. + Hay muchos tipos de problemas y no todos ellos merecen la creación de un informe de problemas. Por supuesto, nadie es perfecto, y habrá ocasiones en que lo que parece ser un error en un programa es, de hecho, un malentendido de la sintaxis de un comando o un error tipográfico en un archivo de configuración (aunque en este último caso podría tratarse de un indicador de documentación escasa o que la aplicación peca de una gestión de errores defectuosa). Incluso teniendo estos aspectos en cuenta existen varios casos en los cuales el envío de un informe de problemas resulta claramente no ser la mejor forma de proceder, y solo servirá para frustrar tanto al remitente como a los desarrolladores. Por el contrario, hay casos en los que podría ser apropiado enviar un informe de problemas sobre algo más que un error: una mejora o una nueva característica, por ejemplo. - Así que ?cómo podemos determinar qué - constituye un bug y qué no? Como regla para - principiantes podemos decir que su problema - no es un bug si - se puede expresar como una pregunta (normalmente del estilo de - ?cómo hago X? o - ?donde puedo encontrar Y?). No siempre las - cosas son blancas o negras, pero la regla de las preguntas suele - cubrir una gran mayoría de casos. Si lo que se quiere es una - respuesta a una consulta, se pueden enviar dichas preguntas a la - &a.questions;. + Entonces, ¿cómo se determina qué es un error y qué no? Como regla general, el problema no es un error si puede expresarse como una pregunta (normalmente del estilo de ¿Cómo hago X? o ¿Dónde puedo encontrar Y?). Las cosas no son siempre blancas o negras, pero la regla de la pregunta cubre la gran mayoría de los casos. Al buscar una respuesta, considere plantear la pregunta a la lista de correo de preguntas generales de FreeBSD. - A continuación se muestran algunos casos en los que resulta - apropiado enviar un informe de problemas sobre algo que no se - considera un bug: + Tenga en cuenta estos factores al enviar PRs sobre ports u otro software que no sea parte de FreeBSD: - Solucitudes para mejora de características. Normalmente - es una buena idea airear estas propuestas en las listas de - distribución antes de enviar un informe de problemas. + Por favor, no envíe informes de problemas que simplemente indiquen la disponibilidad de una nueva versión de una aplicación. Los maintainers de ports son notificados automáticamente por portscout cuando una nueva versión de una aplicación esta disponible. Los parches para actualizar un port a la última versión son bien recibidos. - Notificación de actualizaciones de software que se - mantiene externamente (principalmente ports, pero también - componentes del sistema base al cargo de proyectos independientes - de &os;, como BIND o diversas utilidades GNU) + Para los ports que no están mantenidos (el MAINTAINER es ports@FreeBSD.org), es poco probable que un PR sin un parche adjunto sea cogido por un committer. Para convertirse en el maintainer de un port que no este mantenido, envíe un PR con la petición (sería ideal si viene con un parche adjunto, pero no es necesario). + + + En cualquier caso, seguir el proceso descrito en el Manual del Porter dará los mejores resultados. (Es posible que también desee leer Cómo contribuir a la colección de ports de FreeBSD). + - Otro tema es que si el sistema donde se experimentó el - bug no está medianamente actualizado se debe - considerar muy seriamente su actualización e intentar reproducir - el problema en un sistema actualizado antes de emitir el informe. - Existen pocas cosas que molesten más a un desarrollador que - recibir un informe de problemas sobre un problema que ya ha - resuelto. + Un error que no se puede reproducir rara vez se podrá arreglar. Si el error solo ocurrió una vez y no puede reproducirlo, y no parece que le ocurra a nadie más, es probable que ninguno de los desarrolladores pueda reproducirlo o descubrir qué es lo que está mal. Eso no significa que no haya ocurrido, significa que las posibilidades de que su informe de problemas lleve a la corrección del error son muy escasas. Para empeorar las cosas, a menudo, este tipo de errores son en realidad causados por fallos en los discos duros o procesadores con sobrecalentamiento, siempre debe intentar descartar estas causas, siempre que sea posible, antes de enviar un PR. - Por último, un bug que no se puede - reproducir difícilmente puede arreglarse. Si el - bug sólo ocurrió una vez y no somos capaces - de reproducirlo, y parece que no le ocurre a nadie más, - es muy probable que ni siquiera los desarrolladores puedan - reproducirlo y por lo tanto ni siquiera puedan imaginarse qué es - lo que falla. Esto no significa que el bug no haya - ocurrido, sino que las probabilidades de que nuestro informe de errores - sirva para corregir un defecto son muy pequeñas. Para complicar - más las cosas, a menudo estas clases de errores se producen - debido a fallos en los discos duros o al sobrecalentamiento del - procesador: debe intentar siempre descubrir estos - fallos, siempre que sea posible, antes de enviar un PR. -
+ A continuación, para decidir a quién debe presentar su informe de problemas, debe comprender que el software que compone FreeBSD está compuesto de varios elementos diferentes: + + + El código en el sistema base que escriben y mantienen los colaboradores de FreeBSD, como el kernel, la biblioteca de C y los controladores de dispositivos (categorizados como kern); las utilidades binarias (bin); las páginas del manual y documentación (docs); y las páginas web (www). Todos los errores en estas áreas deben informarse a los desarrolladores de FreeBSD. + + + + El código en el sistema base escrito y mantenido por otros, e importado y adaptado a FreeBSD. Los ejemplos incluyen clang1 y sendmail8. La mayoría de los errores en estas áreas deben informarse a los desarrolladores de FreeBSD; pero en algunos casos es posible que deban informarse a los autores originales si los problemas no son específicos de FreeBSD. + + + + Las aplicaciones individuales que no están en el sistema base, sino que forman parte de la colección de ports de FreeBSD (categoría ports). La mayoría de estas aplicaciones no están escritas por los desarrolladores de FreeBSD; lo que proporciona FreeBSD es simplemente un framework para instalar la aplicación. Por lo tanto, solo informe de un problema a los desarrolladores de FreeBSD cuando crea que el problema es específico de FreeBSD; de lo contrario, repórtelo a los autores del software. + + + + Después, averigüe si es un problema puntual. Existen pocas cosas que molesten más a un desarrollador que recibir un informe de problemas sobre un error que ya ha solucionado. + + Si el problema está en el sistema base, primero lea la sección de preguntas frecuentes sobre las versiones de FreeBSD, si aún no está familiarizado con el tema. FreeBSD no puede solucionar problemas en otras ramas que no sean las más recientes del sistema base, por lo que presentar un informe de error sobre una versión anterior probablemente hará que un desarrollador le aconseje que se actualice a una versión soportada para comprobar si el problema todavía sucede. El equipo Security Officer mantiene la lista de versiones soportadas. + + Si el problema está en un port, considere enviar el error al upstream. El proyecto FreeBSD no puede corregir todos los errores en todo el software. + +
Preparativos - Una buena regla que se puede seguir consiste en realizar - siempre una búsqueda antes de enviar un informe - de problemas. Quizá nuestro problema ya ha sido reportado; - quizá se está discutiendo en las listas de - distribución o fue discutido hace poco; incluso es posible que - se haya arreglado en versiones más recientes del software. - Por lo tanto, se deben consultar los sitios y fuentes más obvias - antes de proceder con el envío del informe de errores. - En &os; esto significa: + Una buena regla que se puede seguir consiste en realizar siempre una búsqueda antes de enviar un informe de problemas. Quizá nuestro problema ya ha sido reportado; quizá se está discutiendo en las listas de correo o fue discutido hace poco; incluso puede que ya esté arreglado en una versión más nueva que la que está ejecutando. Por lo tanto, se deben consultar los sitios y fuentes más obvias antes de proceder con el envío del informe de errores. En FreeBSD, esto significa: - Las - Preguntas Más - - Frecuentes (FAQ) de &os;. - Las FAQ intentan proporcionar respuestas para un - amplio rango de dudas, tales como aquellas relacionadas - con las - - compatibilidades - hardware, las - aplicaciones - de usuario y la - configuración - del kernel. + La lista de preguntas más frecuentes (FAQ) de FreeBSD. Las preguntas frecuentes intentan proporcionar respuestas a una amplia gama de preguntas, como las relacionadas con la compatibilidad del hardware, las aplicaciones de usuario y la configuración del kernel. - Las - - listas - - de correo. Si no está subscrito utilice - la - búsqueda en los archivos del sitio web de &os;. Si - el problema no se ha discutido con anterioridad en las - listas, se puede intentar enviar un mensaje y esperar unos - pocos días para ver si alguien puede aconsejarle - adecuadamente sobre algún punto que quizá haya pasado - por alto en relación con el problema. + Las listas de correo, si no está suscrito, utilice la búsqueda en los archivos del sitio web de FreeBSD. Si el problema no se ha discutido con anterioridad en las listas, se puede intentar enviar un mensaje y esperar unos pocos días para ver si alguien puede aconsejarle adecuadamente sobre algún punto que quizá haya pasado por alto en relación con el problema. - Opcionalmente, la web entera—utilice su motor de - búsqueda favorito para localizar cualquier referencia a su - problema. Incluso pueden aparecer listas de correo o grupos - de noticias de los cuales ni siquiera tuviera conocimiento - de su existencia o quizá no consideró apropiado - consultarlas al principio. + Opcionalmente, toda la web: utilice su motor de búsqueda favorito para localizar cualquier referencia al problema. Incluso puede obtener listas de correo archivadas o grupos de noticias que no conocía o en los que no había pensado buscar. + - A continuación, la búsqueda a través de - - la base de datos &os; PR (GNATS). A menos que - nuestro problema sea muy reciente o rebuscado, existe un - gran número de posibilidades de que ya haya sido informado o - reportado. + A continuación, la búsqueda a través de la base de datos de PR de FreeBSD (Bugzilla). A menos que el problema sea muy reciente o rebuscado, existe un gran número de posibilidades de que ya haya sido informado o reportado. - Lo más importante, se debería intentar comprobar - si la documentación existente en el código fuente del - programa puede resolver el problema. + Lo más importante, se debería intentar comprobar si la documentación existente en el código fuente del programa puede resolver el problema. - En el caso de las fuentes del sistema &os; debe estudiarse - cuidadosamente el contenido del fichero - /usr/src/UPDATING del sistema o su - última versión, que se encuentra en http://www.FreeBSD.org/cgi/cvsweb.cgi/src/UPDATING. - (Esta información se considera de vital importancia si se - está actualizando de una versión a otra, especialmente - si la actualización se realiza de la versión estable a - la versión &os.current;). + Para el código base de FreeBSD, debe estudiar cuidadosamente el contenido del fichero /usr/src/UPDATING del sistema o la versión más reciente en https://svnweb.freebsd.org/base/head/UPDATING?view=log. (Esta información se considera de vital importancia si se está actualizando de una versión a otra, especialmente si está actualizando a la rama de FreeBSD-CURRENT). - No obstante, si el problema se encuentra en algo que se - instaló como parte de la collección de ports de &os;, - se debe consultar el archivo - /usr/ports/UPDATING (para ports - individuales) o el archivo - /usr/ports/CHANGES (para cambios que - afectan a la colección de ports completa). http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/UPDATING - y http://www.FreeBSD.org/cgi/cvsweb.cgi/ports/CHANGES - también se encuentran disponibles a través de CVSweb. - - - + No obstante, si el problema se encuentra en algo que se instaló como parte de la colección de ports de FreeBSD, se debe consultar el archivo /usr/ports/UPDATING (para ports individuales) o el archivo /usr/ports/CHANGES (para cambios que afectan a la colección de ports completa). https://svnweb.freebsd.org/port/head/UPDATING?view=log y https://svnweb.freebsd.org/ports/head/CHANGES?view=log también están disponibles a través de svnweb. + + +
- A continuación debemos asegurarnos de que el informe de - errores llega a las personas adecuadas. - - La primera consideración llegados a este punto consiste en: - Si el problema resulta ser un bug en un software - de terceras partes (un port o un paquete que se ha instalado) - se debe informar sobre el bug al autor original del software, no - al proyecto &os;. Existen dos excepciones a esta regla: la - primera ocurre cuando el bug no se produce en otras plataformas, - en cuyo caso el problema puede residir en cómo fue migrado el - software a &os;; la segunda excepción ocurre cuando el autor - original ya ha corregido el problema y distribuido un parche o - una nueva versión de su software, pero el port de &os; - todavía no se ha actualizado. - - La segunda consideración es que el sistema de seguimiento de - bugs de &os; ordena los informes de problemas de acuerdo con la - categoría que ha seleccionado el informador. De este modo, si se - selecciona una categoría incorrecta cuando se envía el - informe de problemas, existe una gran probabilidad de que nadie se de - cuenta de su existencia durante un período de tiempo indefinido, - hasta que alguien se encarge de re-categorizarlo. - -
- Escribir el informe de problemas + Escribiendo el informe de problemas - Ahora que hemos determinado que el problema que estamos - experimentando se merece la redacción de un informe de problemas - y que se trata de un problema de &os;, es la hora de comenzar a - escribir dicho informe. Antes de pasar a describir los - mecanismos utilizados por el programa encargado de generar los - informes PR, vamos a describir una serie de trucos y consejos - que nos asegurarán la mayor efectividad posible de nuestro - informe. + Ahora que ha decidido que su problema merece un informe de problemas y que es un problema de FreeBSD, es el momento de escribir el informe de problemas propiamente dicho. Antes de pasar a describir los mecanismos utilizados por el programa encargado de generar y enviar los PRs, aquí hay algunos consejos y trucos para ayudarle a asegurarse de que su PR sea más efectivo. -
- Consejos y trucos para escribir un buen informe de - problemas +
+ Consejos y trucos para escribir un buen informe de problemas - No deje la línea de Synopsis - vacía. Los PRs se dirigen tanto a una lista de - correo mundial (donde se utiliza el campo - Synopsis para rellenar la línea - Subject: del correo) como a una base - de datos (GNATS). Cualquier persona que consulte la base - de datos por el campo sinopsis y encuentre un - PR con una línea de Asunto vacía - tiende simplemente a pasar por alto el informe. Recuerde que un - PR permanece en la base de datos hasta que alguien se encarga de - cerrar el informe; un informe anónimo normalmente se - perderá para siempre entre el ruido y tardará mucho - en cerrarse. + No deje el campo Summary vacío. Los PRs se envían a una lista de correo global (donde se utiliza el campo Summary para la línea Subject:), y se almacenan en una base de datos. Cualquiera que haga una búsqueda por el campo synopsis (sinopsis) en la base de datos y encuentre un PR con la línea del subject (asunto) en blanco tiende a omitirlo. Recuerde que los PR permanecen en esta base de datos hasta que alguien los cierra; un PR que no esté debidamente cumplimentado pasará desapercibido. - Evite utilizar una línea de - Synopsis débil.. No debe - suponerse que quien lea el PR conoce el contexto adecuado en el - que su mensaje tiene sentido, así que cuanta más - información se proporcione, mejor que mejor. - Por ejemplo, ?qué parte del sistema se ve afectado - por el informe?, ?el problema aparece cuando se está - instalando o cuando se está ejecutando?. Para - ejemplificar, en lugar de Synopsis: portupgrade is - broken, se pueden ver las ventajas que - proporciona una línea como la siguiente: - Synopsis: port sysutils/portupgrade produce un - coredump en -current. (En el caso concreto de - los ports, resulta especialmente útil poseer tanto la - categoría como el nombre del port en la línea - Synopsis.) + Rellene el campo Summary correctamente, no use descripciones vagas. No asuma que aquella persona que lea su PR entienda el contexto que motivó su envío, por lo tanto, cuanta más información proporcione, mejor. Por ejemplo, ¿en qué parte del sistema se produce el problema? ¿El problema sucede solo durante la instalación o durante la ejecución del sistema? Por ejemplo, en lugar de, Summary: portupgrade is broken, podría utilizar este otro, el cual, tiene mucha más información: Summary: port ports-mgmt/portupgrade coredumps on -current. (En el caso de los ports, es especialmente útil tener el nombre de la categoría y el nombre del port en el campo Summary). - Si se dispone de un parche, dígalo. - Un PR con un parche incluido tiene muchas más - posibilidades de ser tratado que uno que no lo tiene. Si - se include dicho parche, escriba la cadena - [patch] al comienzo de la línea - Synopsis. (Aunque no es obligatorio - utilizar dicha cadena, se trata de un estándar de facto - que se utiliza de forma mayoritaria.) - + Si tiene un parche, dígalo. Es más probable que se analice un PR con un parche incluido que uno sin él. Incluya la palabra clave patch en Bugzilla. - Si es mantenedor del port, dígalo. - Si se está manteniendo el código fuente de una - aplicación (por ejemplo, de un port), se puede - considerar la adición de la cadena - [maintainer update] al comienzo de la - línea de sinopsis, y además se debería - asignar el campo Class del PR a la cadena - maintainer-update. De esta forma - cualquier committer que maneje el PR no tendrá que - realizar comprobaciones. + Si es un maintainer, dígalo. Si mantiene una parte del código fuente (por ejemplo, un port que ya exista), debe establecer el campo Class de su PR a maintainer-update. De esta forma, cualquier committer que se ocupe de su PR no tendrá que verificarlo. + - Sea concreto. - Cuanta más información se proporcione sobre el - problema que se tiene, más posiblidades de obtener una - respuesta. + Sea concreto. Cuanta más información se proporcione sobre el problema que tiene, más posibilidades de obtener una respuesta. - Incluya la versión del &os; que se está - ejecutando (existe un lugar donde escribir esta - esta información, vea más abajo) y en - qué arquitectura. Se debe incluir si - se está ejecutando desde una release (e.g. desde un - CDROM o descarga), o si es desde un sistema mantenido - mediante &man.cvsup.1; (y, si esto último se cumple, - con qué frecuencia se realiza la actualización). Si se está siguiendo la rama &os.current;, se - trata de la primera pregunta que nos harán, - debido a que los parches (sobre todo para problemas de alto - nivel) tienden a aplicarse muy rápidamente, y se espera - de los usuarios de &os.current; un seguimiento cercano de - las actualizaciones aplicadas. + Incluya la versión de FreeBSD que está ejecutando (existe un lugar donde escribir esta información, vea a continuación) y en qué arquitectura. Debe incluir si se está ejecutando desde una release (por ejemplo, desde un CD-ROM o descarga), o si es desde un sistema mantenido por Subversion (y, si es así, en qué número de revisión se encuentra). Si está usando la rama FreeBSD-CURRENT, esa es la primera pregunta que le harán, porque las correcciones (especialmente para problemas de alto nivel) tienden a aplicarse muy rápidamente, y se espera que los usuarios de FreeBSD-CURRENT se mantengan al día. + - Incluya qué opciones globales se han especificado - en el archivo make.conf. Aviso: - Es bien conocido por todos que especificar - -O2 y valores superiores para - &man.gcc.1; produce fallos y resulta ser proclive a - errores en muchas situaciones. Aunque los - desarrolladores de &os; normalmente dan por buenos y - aceptan los parches proporcionados por el creador del - informe de problemas, normalmente no desean investigar - dichas condiciones extrañas debido simplemente a la - falta de tiempo y de voluntarios, y puede que - respondan diciendo simplemente que dicha opción de - compilación no se encuentra soportada. - + Incluya qué opciones globales ha especificado en sus ficheros make.conf, src.conf y src-env.conf. Dado el número infinito de opciones, no todas las combinaciones pueden ser totalmente compatibles. + - Si se trata de un problema del kernel, prepárese - para proporcionar la siguiente información. (No es - necesario incluir esta información por defecto, puesto - que lo único que produce es un crecimiento desmesurado - de la base de datos GNATS, pero sí puede merecer la - pena incluir resúmenes que usted considere - importantes): + Si el problema se puede reproducir fácilmente, incluya información que ayude al desarrollador a reproducirlo por sí mismo. Si se puede hacer una demostración con una entrada específica, incluya un ejemplo con esa entrada, si es posible, e incluya la salida real y la esperada. Si la información es grande o no se puede hacer pública, intente crear un archivo con lo mínimo que muestre el mismo problema y que pueda incluirse en el PR. + + + Si se trata de un problema del kernel, prepárese para proporcionar la siguiente información. (No es necesario incluir esta información por defecto, puesto que lo único que produce es un crecimiento desmesurado de la base de datos, pero sí puede merecer la pena incluir extractos que usted considere importantes): + - La configuración del kernel (incluyendo los - dispositivos hardware que se tienen - instalados) + la configuración del kernel (incluidos los dispositivos de hardware que ha instalado) - Si se tienen opciones de depuración activadas - (tales como WITNESS), y en tal - caso, si el problema persiste cuando se cambia el - valor de dichas opciones + si tiene o no opciones de depuración activadas (como WITNESS), y si es así, si el problema persiste cuando se cambia el valor de dichas opciones - Una traza de depuración, si se pudo - generar. + el texto completo de cualquier backtrace, panic u otra salida por consola, o entradas en /var/log/messages, si se generó alguna + - El hecho de que se ha leido detenidamente el - archivo src/UPDATING para - constatar que el problema no se ha identificado - allí (se garantiza que alguién le - preguntará sobre este punto) + la salida de pciconf -l y partes relevantes de su salida dmesg si su problema se relaciona con una pieza específica de hardware - Si se puede o no se puede ejecutar otro kernel - sin problemas (se trata de identificar problemas - relacionados con el hardware como discos con - errores o CPUs sobrecalentadas, que pueden - confundirse fácilmente con problemas del - kernel) + el hecho de que haya leído src/UPDATING y que su problema no esté listado (seguro que alguien le preguntará sobre este punto) + + + si puede o no ejecutar otro kernel de respaldo sin problemas (se trata de descartar problemas relacionados con el hardware, como discos con errores o CPUs con sobrecalentamiento, que pueden confundirse fácilmente con problemas del kernel) + - Si se trata de un problema relacionado con los - ports, prepárese para poder proporcionar la - información que se muestra a continuación. (No - es necesario incluir esta información por defecto, ya - que sólo produce un crecimiento indeseado de la base de - datos, pero sí se pueden incluir resúmenes de - aquellos datos que usted considere relevantes): + Si se trata de un problema relacionado con los ports, prepárese para poder proporcionar la información que se muestra a continuación. (No es necesario incluir esta información por defecto, ya que esto solo produce un crecimiento indeseado de la base de datos, pero debe incluir extractos que considere que pueden ser relevantes): - Los ports que se tiene instalados + Qué ports ha instalado + - Cualesquiera variables de entorno que - sobreescriban los valores por defecto del archivo - bsd.port.mk, tales como - PORTSDIR + Cualquier variable de entorno que sobrescriba los valores por defecto del archivo bsd.port.mk, como PORTSDIR + - El hecho de que se ha leido - ports/UPDATING y que nuestro - problema no se encuentra identificado en dicho - archivo (se garantiza que alguien puede preguntar - este hecho). + El hecho de que ha leído el archivo ports/UPDATING y que su problema no se encuentra en la lista (puede preguntar a alguien) - + + + Evitar peticiones de características vagas. Los PRs del estilo alguien debería implementar algo que haga esto, aquello y lo de más allá son informes con pocas probabilidades de obtener resultados positivos. Recuerde, el código fuente se encuentra disponible para todo el mundo, por lo tanto, si desea una característica, ¡la mejor manera de asegurarse de que se incluya es ponerse a trabajar en ella! También tenga en cuenta que para discutir este tipo de problemas resulta más adecuado utilizar la lista freebsd-questions, que una entrada en la base de datos de PR, como ya se ha comentado anteriormente. - Evitar peticiones de características - vagas. Los PRs del estilo de - alguien debería implementar algo que haga - esto y aquello y lo de más allá son - informes con pocas probabilidades de obtener resultados - positivos. Las características deben ser muy concretas y - específicas. Recuerde que el código fuente se - encuentra disponible para todo el mundo, de tal forma que si usted - necesita una característica, la mejor forma de verla - incluida en futuras versiones de la herramienta consiste - en ponerse usted mismo a trabajar sobre ella, manos a la - obra. También tenga en cuenta que para discutir este tipo - de problemas resulta más adecuado utilizar la lista - freebsd-questions, como ya se ha - comentado anteriormente. + Asegúrese que nadie más ha enviado un PR similar. Aunque esto ya se ha mencionado anteriormente, vale la pena repetirlo aquí. Solamente lleva uno o dos minutos utilizar el motor de búsqueda web en https://bugs.freebsd.org/bugzilla/query.cgi. (Por supuesto, todo el mundo es culpable de olvidarse de hacerlo de vez en cuando). - Asegúrese que nadie más ha enviado un - PR similar. Aunque esto ya se ha mencionado - anteriormente, merece la pena que se repita en este punto. - Sólamente lleva uno o dos minutos realizar una - búsqueda basada en un motor web en http://www.FreeBSD.org/cgi/query-pr-summary.cgi?query. - (Por supuesto, a todo el mundo se le puede olvidar - realizar esto de vez en cuando, pero por esa misma razón - merece la pena hacer incapié en ello) + Informe un solo problema por informe. Evite incluir dos o más problemas dentro del mismo informe, a menos que estén relacionados. Al enviar parches, evite agregar múltiples funciones o corregir varios errores en el mismo PR, a menos que estén estrechamente relacionados — ya que los PR suelen tardar más en resolverse. + - Evite peticiones controvertidas. - Si nuestro PR se dirige hacia un área o tema controvertido - en el pasado, debemos prepararnos no sólo a ofrecer - parches, si no también a justificar por qué motivo - los parches proporcionados son la Forma Correcta de - Hacerlo. Como se avisó anteriormente, una - búsqueda meticulosa en las listas de correo en los - archivos históricos sitos en http://www.FreeBSD.org/search/search.html#mailinglists - resulta siempre una buena idea y sirve para preparar - nuestro razonamiento y aprender de la experiencia y de las - decisiones tomadas en el pasado. + Evite peticiones controvertidas. Si su PR se dirige a un área que ha sido controvertida en el pasado, probablemente debería estar preparado para no solo ofrecer parches, sino también una justificación de por qué los parches son la forma correcta de hacerlo. Como se avisó anteriormente, una búsqueda meticulosa en las listas de correo utilizando los archivos históricos en https://www.FreeBSD.org/search/search.html#mailinglists es siempre una buena opción. + - Sea educado. - Casi cualquier persona que se encarge de tratar nuestro - informe de problemas trabajará en el como un voluntario. - A nadie le gusta que le digan cómo hacer las cosas cuando - ya se están haciendo de una forma determinada, - especialmente cuando la motivación para realizarlas no es - monetaria. Este hecho es bueno tenerlo en mente y - aplicarlo para cualquier proyecto de Software - Libre. + Sea educado. Practicamente cualquier persona que se encargue de tratar su PR es un voluntario. A nadie le gusta que le digan que tiene que hacer algo cuando ya lo están haciendo por alguna otra motivación que no sea la económica. Es bueno tenerlo en cuenta en todo momento en los proyectos de código abierto. + +
-
- Antes de comenzar. +
+ Antes de comenzar - Antes de ejecutar el programa &man.send-pr.1;, asegúrese - de que la variable de entorno VISUAL (o - EDITOR si la variable VISUAL no - se encuentra definida) se encuentra apuntando a algo con - sentido. + Se aplican consideraciones similares al uso del formulario de envío de PR por la aplicación web. Tenga cuidado con las operaciones de cortar y pegar que puedan cambiar los espacios en blanco u otro formato de texto. - Es importante comprobar que la entrega de correo funciona - correctamente. &man.send-pr.1; utiliza mensajes de correo para - enviar y realizar un seguimiento de los informes de problemas. - Si no se puede generar correo electrónico desde la - máquina en la que se ejecuta &man.send-pr.1;, el informe - jamás llegará a la base de datos GNATS. - Si quiere saber más sobre la - configuración del correo en &os; consulte el capítulo de - Correo Electrónico del manual de &os; en http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mail.html. + Finalmente, si el envío es largo, prepare el trabajo sin conexión, de forma que no se pierda nada si hay un problema al enviarlo.
-
+
Adjuntar parches o archivos - El programa &man.send-pr.1; posee la capacidad de adjuntar - archivos al informe de problemas. Se pueden adjuntar tantos - archivos como se quiera siempre y cuando se utilice un nombre - distinto para cada archivo (e.g. el nombre del archivo después - de eliminar el path). Simplemente basta con utilizar la opción - de línea de comandos para especificar los - nombres de todos los archivos que se desean adjuntar: + Al adjuntar un parche, asegúrese de usar svn diff o diff1 con el argumento para crear un diff unificado, y asegúrese de especificar el número de revisión SVN del repositorio contra el que modificó los archivos, para que los desarrolladores que lean su informe puedan aplicarlos fácilmente. Para problemas relacionados con el kernel o utilidades del sistema base, se prefiere un parche contra FreeBSD-CURRENT (la rama HEAD de Subversion), ya que todo el código nuevo debe aplicarse y probarse allí primero. Después de que se hayan realizado las pruebas adecuadas o importantes, se hará el merge/migración a la rama FreeBSD-STABLE. -&prompt.user; send-pr -a /var/run/dmesg -a /tmp/errors + Si adjunta un parche como parte del mensaje, en lugar de como adjunto, tenga en cuenta que uno de los problemas más comunes es la tendencia de algunos programas de correo electrónico de mostrar las tabulaciones como espacios, lo cual estropeará por completo todo lo que pretenda que forme parte de un Makefile. - No se preocupe por los archivos binarios, dichos archivos - se codifican automáticamente para no interferir con el agente - de correo. + No envíe parches como archivos adjuntos usando Content-Transfer-Encoding: quoted-printable. Esto escapará el carácter (character escaping) y todo el parche será inútil. - Si se adjunta un parche, asegúrese que se utiliza la - opción o la opción - de &man.diff.1; para crear un contexto - unificado (el contexto suele ser el preferido por quienes lo han de - recibir) y además asegúrese de especificar - los números de revisión de CVS de los archivos que se - modifican para que los desarrolladores que lean el informe - puedan aplicar dichos parches fácilmente. Para problemas - relacionados con el kernel o con las utilidades del sistema - base, se prefiere un parche contra &os.current; (la rama HEAD - del árbol CVS) ya que cualquier código nuevo debe - probar se primeramente en dicha rama. Después de comprobar su - correcto funcionamiento de una forma sustancial y extensa, - eventualmente dicho código pasará a formar parte de - &os.stable;, mediante unión o migración. + También tenga en cuenta que, incluir pequeños parches en un PR, en general, está bien, especialmente cuando soluciona el problema descrito en el PR, los parches grandes y especialmente el nuevo código que pueda requerir una revisión sustancial antes de realizar el commit deben colocarse en un servidor web o ftp, y la URL debe incluirse en el PR en lugar del parche. Los parches en el correo electrónico tienden a ser destrozados, y cuanto más grande sea el parche, más difícil será para las partes interesadas desenmarañarlo. Además, la publicación de un parche en la web le permite modificarlo sin tener que volver a enviar el parche completo en un follow-up al PR original. Finalmente, los parches grandes simplemente aumentan el tamaño de la base de datos, ya que los PR cerrados no se eliminan, sino que se guardan y simplemente se marcan como completos. - Si se envía un parte en línea, en vez de como - adjunto, tenga en cuenta que el principal problema de esta forma de - enviar los parches es que, dependiendo del lector de correo - utilizado, algunos lectores muestran los tabuladores como - espacios, lo cual arruina completamente el formato y la - indentación del parche, e invalida totalmente un parche que - forme parte de un Makefile. + También debe tener en cuenta que, a menos que se especifique explícitamente lo contrario en su PR o en el propio parche, se asumirá que los parches que envíe se licenciarán en los mismos términos que el archivo original que modificó. +
- También tenga en cuenta que mientras que la - inclusión de parches en un PR se considera como algo - positivo—particularmente cuando se soluciona el problema - que describe el informe—partes grandes y especialmente - código nuevo que puede requerir una sustancial revisión - antes de ser aplicado debería hacerse accesible a través - de otros medios, como páginas web o servidores de ftp, y - en vez de incluir el parche en el informe se puede incluir la URL. - Los parches de gran tamaño en los correos electrónicos - tienden a mezclarse o partirse, especialmente cuando GNATS los trata, - y cuanto más grande es el parche más difícil - resulta recuperar el original. También existe una ventaja - añadida a la inclusión del parche a través de una - URL, ya que de este modo se puede modificar el parche sin tener que - reenviar el informe como una respuesta al informe inicial. +
+ Rellenar el formulario - Se debe prestar atención también al hecho de que, a - menos que se especifique explícitamente lo contrario en el PR o - en el propio parche, cualquier parche enviado se supone - licenciado bajo los mismos términos y condiciones que el - archivo original que modifica.
+ + La dirección de correo electrónico que utilice pasará a ser pública y podrá estar disponible para los spammers. Debe tener implementados procedimientos de manejo de spam o usar una cuenta de correo electrónico temporal. Sin embargo, tenga en cuenta que si no utiliza una cuenta de correo electrónico válida, no podremos hacerle preguntas sobre su PR. + -
- Rellenar la plantilla + Cuando presente un error, encontrará los siguientes campos: - Cuando se ejecuta &man.send-pr.1; se nos presenta en - pantalla una plantilla. Esta plantilla consiste en una lista - de campos, algunos de los cuales se encuentran ya rellenados, - mientras que otros poseen comentarios donde se explica su - propósito o se comentan los valores aceptables. No se preocupe - por los comentarios, puesto que se borran automáticamente - antes de generar el informe. - - Al comienzo de la plantilla, justo debajo de las líneas de - SEND-PR:, se encuentran las cabeceras de - correo electrónico. Dichas cabeceras normalmente no se tienen - que modificar, a menos que se esté rellenando el informe desde - una máquina que puede enviar correo pero no puede recibirlo - directamente, en cuyo caso usted tendrá que editar los campos - From: y Reply-To: para - escribir la dirección de correo válida. También - puede enviarse una copia a usted mismo o a cualquier otra persona - rellenando el campo Cc:. - - A continuación aparecen una serie de campos de una sola - línea: - - Submitter-Id: No cambie este - campo. El valor por defecto - current-users es correcto, incluso si - se está ejecutando &os.stable;. + Synopsis: Rellene este campo con una descripción corta y precisa del problema. El campo debe ser rellenado en inglés, pues es el idioma de comunicación en el proyecto FreeBSD. La sinopsis se utiliza como subject del correo electrónico del informe de problemas, y también se utiliza en los listados y resúmenes de informes de la base de datos; informes de problemas con vagas sinopsis tienden a ser completamente ignorados. + - Originator: Se rellena - automáticamente con el campo gecos del - usuario que está actualmente dentro del sistema. Por - favor, especifique su nombre real, opcionalmente - acompañado por su dirección de correo - electrónico entre < >. + Severity: Escoga una de las opciones, Affects only me (Solo me afecta a mi), Affects some people (Afecta a algunas personas) o Affects many people (Afecta a muchas personas). No sea exagerado; absténgase de etiquetar su problema Affects many people (Afecta a muchas personas) a menos que realmente lo haga. Los desarrolladores de FreeBSD no trabajarán en su problema más rápido si infla su importancia, ya que muchas otras personas han hecho exactamente lo mismo. + - Organization: Escriba lo que - usted quiera. Este campo no se utiliza para nada - significativo. + Category: Elija una categoría apropiada. - - Confidential: Esto se rellena - automáticamente con el literal no. - Cambiar este valor carece de sentido ya que no existe - ningún informe de problemas de &os; confidencial—la - base de datos de PR se distribuye a todo el mundo de forma - pública mediante CVSup. - + Lo primero que debe hacer es decidir en qué parte del sistema se encuentra su problema. Recuerde, FreeBSD es un sistema operativo completo, instala un kernel, la biblioteca estándar, muchos controladores de periféricos y un gran número de utilidades (el sistema base). Sin embargo, hay miles de aplicaciones adicionales en la colección de ports. Primero deberá decidir si el problema está en el sistema base o en algo instalado a través de la colección de ports. - - Synopsis: Rellene este campo con - una descripción corta y precisa del problema. La sinopsis - se utiliza como subject del correo electrónico del informe - de problemas, y también se utiliza en los listados y - resúmenes de informes de la base de datos; informes de - problemas con obscuras sinopsis tienden a ser - completamente ignorados. + Aquí una descripción de las principales categorías: - Como se avisó anteriormente, si su informe de - problemas incluye un parche, por favor incluya en la - sinopsis la etiqueta [patch] al - comienzo; si usted es un mantenedor de software, también - puede añadir la cadena [maintainer - update] y asignar el campo Class - del informe al valor - maintainer-update. - - - Severity: Los valores aceptados - son non-critical, - serious o critical. - No sea exagerado; evite etiquetar el problema como - critital a menos que sea realmente algo - crítico (e.g. escalada de permisos hacia - root, kernel panic fácilmente - reproducible). Incluso debe pensarse detenidamente - etiquetar algo como serious a menos que - se trate de algo que afecte a muchos usuarios (problemas - con drivers de dispositivos particulares o con utilidades - del sistema). Los desarrolladores de &os; no van a - resolver el problema más rápido por el hecho de - variar esta etiqueta, debido a que existe mucha gente que infla - este campo inadecuadamente. De hecho, los desarrolladores - prestan muy poca atención al valor de este campo y del - siguiente precisamente por esto último. - - - Priority: Los valores aceptados - son low, medium o - high. high debe - reservarse para problemas que afecten a la mayoría de los - usuarios de &os; y medium para aquellos - problemas que afecten a varios usuarios. + + + Si hay un problema con el kernel, las bibliotecas (como la biblioteca estándar de C libc) o en un controlador de un periférico en el sistema base, en general, utilizará la categoría kern. (Hay algunas excepciones; vea más abajo). En general, estas son las cosas que se describen en la sección 2, 3 ó 4 de las páginas del manual. - - Category: Seleccione uno de los - siguientes valores (extraídos de - /usr/gnats/gnats-adm/categories): - - advocacy: para problemas - relacionados con la imagen pública de &os;. Raras veces - utilizado. - - alpha: para problemas - específicos de la plataforma Alpha. + Si el problema es con un binario como sh1 o mount8, primero deberá determinar si estos programas se encuentran en el sistema base o se añadieron a través de la colección de ports. Si no está seguro, puede hacer whereis programname. La convención de FreeBSD para la colección de ports es instalar todo por debajo de /usr/local, aunque un administrador del sistema puede sobreescribirlo. Para estos, utilizará la categoría de ports (sí, incluso si la categoría del port es www; vea más abajo). Si la ubicación es /bin, /usr/bin, /sbin, o / usr/sbin, es parte del sistema base, y debe usar la categoría bin. Estas son todas las cosas que se describen en las secciones 1 u 8 de las páginas del manual. + - amd64: para problemas - específicos de la plataforma AMD64. + Si cree que el error está en los scripts de inicio (rc), o en algún otro tipo de archivo de configuración no ejecutable, entonces la categoría correcta es conf (configuración). Estas son las cosas que se describen en la sección 5 de las páginas del manual. + - bin: para problemas con - aplicaciones de la zona de usuario del sistema - base. + Si ha encontrado un problema en el conjunto de la documentación (artículos, libros, man pages) o en el sitio web, la elección correcta es docs. - - conf: para problemas de - archivos de configuración, valores por defecto, - etc. + + Si tiene un problema con un port llamado www/algunnombredeport, esto entra en la categoría de ports. + + + - - docs: para problemas con las - páginas de manual o la documentación online. - + Hay algunas categorías más especializadas. + - gnu: para problemas - realacionados con aplicaciones gnu de &os; tales como - &man.gcc.1; o &man.grep.1;. + Si el problema se catalogará en kern pero estuviera relacionado con el subsistema USB, la elección correcta es usb. + - i386: para problemas - específicos de la plataforma &i386;. + Si el problema se catalogará en kern pero estuviera relacionado con las bibliotecas de threading, la elección correcta es threads. + - ia64: para problemas - específicos de la plataforma ia64. + Si el problema se catalogará en el sistema base, pero estuviera relacionado con nuestra interpretación de estándares, como POSIX, la elección correcta es standards. + - java: para problemas - relacionados con &java;. + Si está convencido de que el problema solo ocurrirá con la arquitectura del procesador que está utilizando, seleccione una de las categories específicas de la arquitectura: normalmente, i386 para ordenadores compatibles con Intel en modo 32 bits; amd64 para máquinas AMD que se ejecutan en modo 64 bits (esto también incluye ordenadores compatibles con Intel que se ejecutan en modo EMT64); y las menos comunes, arm o powerpc. - - kern: para problemas - relacionados con el kernel o con (no especifícos de - ninguna plataforma) controladores de - dispositivos. + + Estas categorías se utilizan con frecuencia para los problemas No lo sé. En lugar de suponer, utilice misc. + - - misc: para cualquier cosa que - no encaja en ninguna de las anteriores categorías. - (Tenga en cuenta que es muy fácil que los problemas - bajo esta categoría se pierdan en el olvido). - + + Uso correcto de la categoría de arquitectura específica - - ports: para problemas - relacionados con el árbol de ports. + Tiene un ordenador común (PC-based machine), y cree que ha encontrado un problema específico para un conjunto de chips o una placa base en particular: i386 es la categoría correcta. + - - powerpc: para problemas - específicos de la plataforma &powerpc;. - + + Uso incorrecto de la categoría de arquitectura específica - - sparc64: para problemas - específicos de la plataforma &sparc64;. - - - - standards: para problemas - relativos a la adecuación con estándares. - - - - threads: para problemas - relacionados con la implementación de threads de &os; - (especialmente en &os.current;). - - - www: para cambios o mejoras - del sitio web de &os;. - - - - Class: Se puede seleccionar uno - entre los siguientes: - - - - sw-bug: bugs de software. + Está teniendo un problema con una tarjeta periférica adicional en un bus común, o un problema con un tipo particular de unidad de disco duro: en este caso, probablemente afecte a más de una arquitectura, y kern es la categoría correcta. + *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-all@freebsd.org Thu Sep 5 19:40:44 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 39620D178C; Thu, 5 Sep 2019 19:40:44 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PWJD1Xdfz4HfQ; Thu, 5 Sep 2019 19:40:44 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1985F9208; Thu, 5 Sep 2019 19:40:44 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x85JehWE001071; Thu, 5 Sep 2019 19:40:43 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x85JehB2001070; Thu, 5 Sep 2019 19:40:43 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201909051940.x85JehB2001070@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Thu, 5 Sep 2019 19:40:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53376 - head/en_US.ISO8859-1/books/arch-handbook/boot X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/arch-handbook/boot X-SVN-Commit-Revision: 53376 X-SVN-Commit-Repository: doc 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.29 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, 05 Sep 2019 19:40:44 -0000 Author: bcr Date: Thu Sep 5 19:40:43 2019 New Revision: 53376 URL: https://svnweb.freebsd.org/changeset/doc/53376 Log: Cleanup some textproc/igor warnings where possible: - wrap long lines - spelling Event: vBSDcon FreeBSD Hackathon Modified: head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml Thu Sep 5 19:36:06 2019 (r53375) +++ head/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml Thu Sep 5 19:40:43 2019 (r53376) @@ -51,17 +51,18 @@ $FreeBSD$ booting system initialization This chapter is an overview of the boot and system - initialization processes, starting from the BIOS (firmware) - POST, to the first user process creation. Since the initial + initialization processes, starting from the + BIOS (firmware) POST, to + the first user process creation. Since the initial steps of system startup are very architecture dependent, the IA-32 architecture is used as an example. The &os; boot process can be surprisingly complex. After - control is passed from the BIOS, a considerable amount of - low-level configuration must be done before the kernel can be - loaded and executed. This setup must be done in a simple and - flexible manner, allowing the user a great deal of customization - possibilities. + control is passed from the BIOS, a + considerable amount of low-level configuration must be done + before the kernel can be loaded and executed. This setup must + be done in a simple and flexible manner, allowing the user a + great deal of customization possibilities. @@ -116,10 +117,10 @@ F5 Disk 2 boot2 - This prompt will appear if the user - presses a key just after selecting an OS to boot - at the boot0 - stage. + This prompt will appear if the user + presses a key just after selecting an OS to boot at + the boot0 + stage. >>FreeBSD/i386 BOOT Default: 1:ad(1,a)/boot/loader boot: @@ -241,12 +242,12 @@ FreeBSD clang version 3.3 (tags/RELEASE_33/final 18350 partitions . + xlink:href="http://en.wikipedia.org/wiki/Master_boot_record">. boot0 resides in the filesystem as /boot/boot0. It is a small 512-byte file, and it is exactly what &os;'s installation procedure wrote to - the hard disk's MBR if you chose the bootmanager - option at installation time. Indeed, + the hard disk's MBR if you chose the + bootmanager option at installation time. Indeed, boot0 is the MBR. @@ -895,9 +896,9 @@ read_key: Register %bx holds the memory address where the MBR will be loaded. The instruction pushing %cs onto the stack is very - interesting. In this context, it accomplishes nothing. However, as - we will see shortly, boot2, in conjunction - with the BTX server, also uses + interesting. In this context, it accomplishes nothing. + However, as we will see shortly, boot2, in + conjunction with the BTX server, also uses xread.1. This mechanism will be discussed in the next section. @@ -1000,9 +1001,10 @@ main.3: boot1 are 512 bytes each, so they fit exactly in one disk sector. boot2 is much bigger, holding both - the BTX server and the boot2 client. - Finally, a file called simply boot is 512 - bytes larger than boot2. This file is a + the BTX server and the + boot2 client. Finally, a file called + simply boot is 512 bytes larger than + boot2. This file is a concatenation of boot1 and boot2. As already noted, boot0 is the file written to the absolute @@ -1065,7 +1067,7 @@ main.3: This is necessary for legacy reasons. Interested readers should see . - and concludes with a jump to the starting point of the + and concludes with a jump to the starting point of the BTX server:
@@ -1252,8 +1254,7 @@ seta20.3:
<filename>sys/boot/i386/boot2/boot2.h</filename> - - #define XREADORG 0x725 + #define XREADORG 0x725
Recall that boot1 was relocated (i.e., @@ -1332,7 +1333,7 @@ seta20.3: BTX server. This file, which takes exactly 16 sectors, or 8192 bytes, is what is actually written to the beginning of the &os; slice - during instalation. Let us now proceed to study the + during installation. Let us now proceed to study the BTX server program. The BTX server prepares a simple @@ -1461,14 +1462,14 @@ init: cli # Disable interrupts Recall that boot1 was originally loaded to address 0x7c00, so, with this memory - initialization, that copy effectively dissapeared. However, + initialization, that copy effectively disappeared. However, also recall that boot1 was relocated to 0x700, so that copy is still in memory, and the BTX server will make use of it. Next, the real-mode IVT (Interrupt Vector - Table is updated. The IVT is an array of + Table is updated. The IVT is an array of segment/offset pairs for exception and interrupt handlers. The BIOS normally maps hardware interrupts to interrupt vectors 0x8 to @@ -1599,18 +1600,19 @@ init.4: movb $_ESP0H,TSS_ESP0+1(%di) # Set ESP0
Note that a value is given for the Privilege Level 0 stack - pointer and stack segment in the TSS. This is needed because, - if an interrupt or exception is received while executing - boot2 in Privilege Level 3, a change to - Privilege Level 0 is automatically performed by the processor, - so a new working stack is needed. Finally, the I/O Map Base - Address field of the TSS is given a value, which is a 16-bit - offset from the beginning of the TSS to the I/O Permission - Bitmap and the Interrupt Redirection Bitmap. + pointer and stack segment in the TSS. This + is needed because, if an interrupt or exception is received + while executing boot2 in Privilege Level 3, + a change to Privilege Level 0 is automatically performed by the + processor, so a new working stack is needed. Finally, the I/O + Map Base Address field of the TSS is given a + value, which is a 16-bit offset from the beginning of the + TSS to the I/O Permission Bitmap and the + Interrupt Redirection Bitmap. - After the IDT and TSS are created, the processor is ready to - switch to protected mode. This is done in the next - block: + After the IDT and TSS + are created, the processor is ready to switch to protected mode. + This is done in the next block:
<filename>sys/boot/i386/btx/btx/btx.S</filename> @@ -1633,20 +1635,22 @@ init.8: xorl %ecx,%ecx # Zero
First, a call is made to setpic to - program the 8259A PIC (Programmable Interrupt Controller). - This chip is connected to multiple hardware interrupt sources. - Upon receiving an interrupt from a device, it - signals the processor with the appropriate interrupt vector. + program the 8259A PIC (Programmable Interrupt + Controller). This chip is connected to multiple hardware + interrupt sources. Upon receiving an interrupt from a device, + it signals the processor with the appropriate interrupt vector. This can be customized so that specific interrupts are associated with specific interrupt vectors, as explained before. - Next, the IDTR (Interrupt Descriptor Table Register) and - GDTR (Global Descriptor Table Register) are loaded with the - instructions lidt and lgdt, respectively. These registers are - loaded with the base address and limit address for the IDT and - GDT. The following three instructions set the Protection Enable - (PE) bit of the %cr0 register. This - effectively switches the processor to - 32-bit protected mode. Next, a long jump is made to + Next, the IDTR (Interrupt Descriptor Table + Register) and GDTR (Global Descriptor Table + Register) are loaded with the instructions + lidt and lgdt, + respectively. These registers are loaded with the base address + and limit address for the IDT and + GDT. The following three instructions set + the Protection Enable (PE) bit of the %cr0 + register. This effectively switches the processor to 32-bit + protected mode. Next, a long jump is made to init.8 using segment selector SEL_SCODE, which selects the Supervisor Code Segment. The processor is effectively executing in CPL 0, the most privileged level, after @@ -1656,10 +1660,10 @@ init.8: xorl %ecx,%ecx # Zero privilege level of 0. Our last code block is responsible for loading the - TR (Task Register) with the segment selector for the TSS we created - earlier, and setting the User Mode environment before passing - execution control to the boot2 - client. + TR (Task Register) with the segment selector + for the TSS we created earlier, and setting + the User Mode environment before passing execution control to + the boot2 client.
<filename>sys/boot/i386/btx/btx/btx.S</filename> @@ -1698,17 +1702,18 @@ init.9: push $0x0 # general Note that the client's environment include a stack segment selector and stack pointer (registers %ss and - %esp). Indeed, once the TR is loaded with - the appropriate stack segment selector (instruction - ltr), the stack pointer is calculated and - pushed onto the stack along with the stack's segment selector. - Next, the value 0x202 is pushed onto the - stack; it is the value that the EFLAGS will get when control is - passed to the client. Also, the User Mode code segment selector - and the client's entry point are pushed. Recall that this entry - point is patched in the BTX header at link time. Finally, - segment selectors (stored in register %ecx) - for the segment registers + %esp). Indeed, once the + TR is loaded with the appropriate stack + segment selector (instruction ltr), the stack + pointer is calculated and pushed onto the stack along with the + stack's segment selector. Next, the value + 0x202 is pushed onto the stack; it is the + value that the EFLAGS will get when control is passed to the + client. Also, the User Mode code segment selector and the + client's entry point are pushed. Recall that this entry + point is patched in the BTX header at link + time. Finally, segment selectors (stored in register + %ecx) for the segment registers %gs, %fs, %ds and %es are pushed onto the stack, along with the value at %edx (0xa000). Keep in mind the various values @@ -1726,12 +1731,12 @@ init.9: push $0x0 # general various segment registers. Five values still remain on the stack. They are popped when the iret instruction is executed. This instruction first pops - the value that was pushed from the BTX header. This value is a - pointer to boot2's entry point. It is - placed in the register %eip, the instruction - pointer register. Next, the segment selector for the User - Code Segment is popped and copied to register - %cs. Remember that + the value that was pushed from the BTX + header. This value is a pointer to boot2's + entry point. It is placed in the register + %eip, the instruction pointer register. + Next, the segment selector for the User Code Segment is popped + and copied to register %cs. Remember that this segment's privilege level is 3, the least privileged level. This means that we must provide values for the stack of this privilege level. This is why the processor, besides @@ -1760,9 +1765,10 @@ init.9: push $0x0 # general loader, and then further to the kernel. Some nodes of this structures are set by boot2, the rest by the loader. This structure, among other information, contains the - kernel filename, BIOS harddisk geometry, BIOS drive number for - boot device, physical memory available, envp - pointer etc. The definition for it is: + kernel filename, BIOS harddisk geometry, + BIOS drive number for boot device, physical + memory available, envp pointer etc. The + definition for it is: /usr/include/machine/bootinfo.h: struct bootinfo { @@ -1795,8 +1801,10 @@ struct bootinfo { ino_t lookup(char *filename) and int xfsread(ino_t inode, void *buf, size_t nbyte) are used to read the content of a file into - memory. /boot/loader is an ELF binary, but - where the ELF header is prepended with a.out's struct + memory. /boot/loader is an + ELF binary, but where the + ELF header is prepended with + a.out's struct exec structure. load() scans the loader's ELF header, loading the content of /boot/loader into memory, and passing the @@ -1811,10 +1819,11 @@ struct bootinfo { <application>loader</application> Stage - loader is a BTX client as well. - I will not describe it here in detail, there is a comprehensive - manpage written by Mike Smith, &man.loader.8;. The underlying - mechanisms and BTX were discussed above. + loader is a + BTX client as well. I will not describe it + here in detail, there is a comprehensive man page written by + Mike Smith, &man.loader.8;. The underlying mechanisms and + BTX were discussed above. The main task for the loader is to boot the kernel. When the kernel is loaded into memory, it is being called by the From owner-svn-doc-all@freebsd.org Thu Sep 5 20:22:59 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id ABBB0D2704; Thu, 5 Sep 2019 20:22:59 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PXDz44z3z4KR4; Thu, 5 Sep 2019 20:22:59 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 70A8E9B21; Thu, 5 Sep 2019 20:22:59 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x85KMxDf030299; Thu, 5 Sep 2019 20:22:59 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x85KMxKD030298; Thu, 5 Sep 2019 20:22:59 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201909052022.x85KMxKD030298@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Thu, 5 Sep 2019 20:22:59 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53377 - head/en_US.ISO8859-1/books/arch-handbook/pci X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/arch-handbook/pci X-SVN-Commit-Revision: 53377 X-SVN-Commit-Repository: doc 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.29 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, 05 Sep 2019 20:22:59 -0000 Author: bcr Date: Thu Sep 5 20:22:58 2019 New Revision: 53377 URL: https://svnweb.freebsd.org/changeset/doc/53377 Log: Clean up the following igor warnings: - wrap long line - add blank line after previous line - use tabs instead of spaces - straggling Event: vBSDcon FreeBSD Hackathon Modified: head/en_US.ISO8859-1/books/arch-handbook/pci/chapter.xml Modified: head/en_US.ISO8859-1/books/arch-handbook/pci/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/arch-handbook/pci/chapter.xml Thu Sep 5 19:40:43 2019 (r53376) +++ head/en_US.ISO8859-1/books/arch-handbook/pci/chapter.xml Thu Sep 5 20:22:58 2019 (r53377) @@ -4,7 +4,9 @@ $FreeBSD$ --> - + PCI Devices PCI bus @@ -20,9 +22,10 @@ to any of them. - Sample Driver Source (<filename>mypci.c</filename>) + Sample Driver Source + (<filename>mypci.c</filename>) -/* + /* * Simple KLD to play with the PCI functions. * * Murray Stokely @@ -232,7 +235,7 @@ DRIVER_MODULE(mypci, pci, mypci_driver, mypci_devclass <filename>Makefile</filename> for Sample Driver -# Makefile for mypci driver + # Makefile for mypci driver KMOD= mypci SRCS= mypci.c @@ -251,13 +254,16 @@ SRCS+= device_if.h bus_if.h pci_if.h Additional Resources + - PCI - Special Interest Group + + PCI + Special Interest Group + PCI System Architecture, Fourth Edition by - Tom Shanley, et al. - + Tom Shanley, et al. + @@ -265,7 +271,8 @@ SRCS+= device_if.h bus_if.h pci_if.h Bus Resources - PCI busresources + PCI + busresources FreeBSD provides an object-oriented mechanism for requesting resources from a parent bus. Almost all devices will be a child member of some sort of bus (PCI, ISA, USB, SCSI, etc) and these @@ -275,18 +282,20 @@ SRCS+= device_if.h bus_if.h pci_if.h Base Address Registers - PCI busBase Address Registers + PCI busBase Address + Registers To do anything particularly useful with a PCI device you - will need to obtain the Base Address - Registers (BARs) from the PCI Configuration space. - The PCI-specific details of obtaining the BAR are abstracted in - the bus_alloc_resource() function. + will need to obtain the Base Address + Registers (BARs) from the PCI Configuration + space. The PCI-specific details of obtaining the BAR are + abstracted in the bus_alloc_resource() + function. For example, a typical driver might have something similar - to this in the attach() function: + to this in the attach() function: - sc->bar0id = PCIR_BAR(0); + sc->bar0id = PCIR_BAR(0); sc->bar0res = bus_alloc_resource(dev, SYS_RES_MEMORY, &sc->bar0id, 0, ~0, 1, RF_ACTIVE); if (sc->bar0res == NULL) { @@ -309,34 +318,33 @@ SRCS+= device_if.h bus_if.h pci_if.h sc->bar1_bh = rman_get_bushandle(sc->bar1res); Handles for each base address register are kept in the - softc structure so that they can be - used to write to the device later. + softc structure so that + they can be used to write to the device later. These handles can then be used to read or write from the - device registers with the bus_space_* - functions. For example, a driver might contain a shorthand - function to read from a board specific register like this: + device registers with the bus_space_* + functions. For example, a driver might contain a shorthand + function to read from a board specific register like + this: -uint16_t + uint16_t board_read(struct ni_softc *sc, uint16_t address) { return bus_space_read_2(sc->bar1_bt, sc->bar1_bh, address); -} - +} Similarly, one could write to the registers with: -void + void board_write(struct ni_softc *sc, uint16_t address, uint16_t value) { bus_space_write_2(sc->bar1_bt, sc->bar1_bh, address, value); -} - +} These functions exist in 8bit, 16bit, and 32bit versions - and you should use - bus_space_{read|write}_{1|2|4} - accordingly. + and you should use + bus_space_{read|write}_{1|2|4} + accordingly. In FreeBSD 7.0 and later, you can use the @@ -345,31 +353,33 @@ board_write(struct ni_softc *sc, uint16_t address, uin bus_* functions take a struct resource * pointer instead of a bus tag and handle. Thus, you could drop the bus tag and bus handle members from - the softc and rewrite the - board_read() function as: + the softc and rewrite + the board_read() function as: -uint16_t + uint16_t board_read(struct ni_softc *sc, uint16_t address) { return (bus_read(sc->bar1res, address)); -} - +} + Interrupts - PCI businterrupts + PCI + businterrupts + Interrupts are allocated from the object-oriented bus code - in a way similar to the memory resources. First an IRQ - resource must be allocated from the parent bus, and then the - interrupt handler must be set up to deal with this IRQ. + in a way similar to the memory resources. First an IRQ + resource must be allocated from the parent bus, and then the + interrupt handler must be set up to deal with this IRQ. Again, a sample from a device - attach() function says more than - words. + attach() function says more than + words. -/* Get the IRQ resource */ + /* Get the IRQ resource */ sc->irqid = 0x0; sc->irqres = bus_alloc_resource(dev, SYS_RES_IRQ, &(sc->irqid), @@ -387,67 +397,62 @@ board_read(struct ni_softc *sc, uint16_t address) if (error) { printf("Couldn't set up irq\n"); goto fail4; - } - + } Some care must be taken in the detach routine of the - driver. You must quiesce the device's interrupt stream, and - remove the interrupt handler. Once - bus_teardown_intr() has returned, you - know that your interrupt handler will no longer be called and - that all threads that might have been executing this interrupt handler - have returned. Since this function can sleep, you must not hold - any mutexes when calling this function. - + driver. You must quiesce the device's interrupt stream, and + remove the interrupt handler. Once + bus_teardown_intr() has returned, you + know that your interrupt handler will no longer be called and + that all threads that might have been executing this interrupt + handler have returned. Since this function can sleep, you + must not hold any mutexes when calling this function. DMA - PCI busDMA + PCI + busDMA + This section is obsolete, and present only for historical - reasons. The proper methods for dealing with these issues is to - use the bus_space_dma*() functions instead. - This paragraph can be removed when this section is updated to reflect - that usage. However, at the moment, the API is in a bit of - flux, so once that settles down, it would be good to update this - section to reflect that. + reasons. The proper methods for dealing with these issues is + to use the bus_space_dma*() functions + instead. This paragraph can be removed when this section is + updated to reflect that usage. However, at the moment, the + API is in a bit of flux, so once that settles down, it would + be good to update this section to reflect that. On the PC, peripherals that want to do bus-mastering DMA - must deal with physical addresses. This is a problem since - FreeBSD uses virtual memory and deals almost exclusively with - virtual addresses. Fortunately, there is a function, - vtophys() to help. + must deal with physical addresses. This is a problem since + FreeBSD uses virtual memory and deals almost exclusively with + virtual addresses. Fortunately, there is a function, + vtophys() to help. -#include <vm/vm.h> + #include <vm/vm.h> #include <vm/pmap.h> -#define vtophys(virtual_address) (...) - +#define vtophys(virtual_address) (...) The solution is a bit different on the alpha however, and - what we really want is a function called - vtobus(). + what we really want is a function called + vtobus(). -#if defined(__alpha__) + #if defined(__alpha__) #define vtobus(va) alpha_XXX_dmamap((vm_offset_t)va) #else #define vtobus(va) vtophys(va) -#endif - - +#endif Deallocating Resources It is very important to deallocate all of the resources - that were allocated during attach(). - Care must be taken to deallocate the correct stuff even on a - failure condition so that the system will remain usable while - your driver dies. - + that were allocated during attach(). + Care must be taken to deallocate the correct stuff even on a + failure condition so that the system will remain usable while + your driver dies. - From owner-svn-doc-all@freebsd.org Thu Sep 5 20:46:55 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 24126D3152; Thu, 5 Sep 2019 20:46:55 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46PXmZ6rdMz4MHL; Thu, 5 Sep 2019 20:46:54 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id CA3789EDF; Thu, 5 Sep 2019 20:46:54 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x85KksFp043224; Thu, 5 Sep 2019 20:46:54 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x85KkssJ043223; Thu, 5 Sep 2019 20:46:54 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201909052046.x85KkssJ043223@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Thu, 5 Sep 2019 20:46:54 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53378 - head/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/handbook/network-servers X-SVN-Commit-Revision: 53378 X-SVN-Commit-Repository: doc 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.29 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, 05 Sep 2019 20:46:55 -0000 Author: bcr Date: Thu Sep 5 20:46:54 2019 New Revision: 53378 URL: https://svnweb.freebsd.org/changeset/doc/53378 Log: Clean up this chapter a bit using textproc/igor output: - Use tabs instead of spaces - wrap long lines - bad indent Event: vBSDcon FreeBSD Hackathon Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Modified: head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml ============================================================================== --- head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Thu Sep 5 20:22:58 2019 (r53377) +++ head/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml Thu Sep 5 20:46:54 2019 (r53378) @@ -2252,14 +2252,14 @@ TWO (,hotel,test-domain) - - - Rocky - Hotas - - Updates by - - + + + Rocky + Hotas + + Updates by + + LDAP @@ -4371,13 +4371,13 @@ driftfile /var/db/ntp.drift example: set filter dial 0 deny udp src eq 123 - # Prevent NTP traffic from initiating dial out - set filter dial 1 permit 0 0 - set filter alive 0 deny udp src eq 123 - # Prevent incoming NTP traffic from keeping the connection open - set filter alive 1 deny udp dst eq 123 - # Prevent outgoing NTP traffic from keeping the connection open - set filter alive 2 permit 0/0 0/0 +# Prevent NTP traffic from initiating dial out +set filter dial 1 permit 0 0 +set filter alive 0 deny udp src eq 123 +# Prevent incoming NTP traffic from keeping the connection open +set filter alive 1 deny udp dst eq 123 +# Prevent outgoing NTP traffic from keeping the connection open +set filter alive 2 permit 0/0 0/0 For more details, refer to the PACKET FILTERING section in &man.ppp.8; and From owner-svn-doc-all@freebsd.org Fri Sep 6 00:01:02 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 58510D92C4; Fri, 6 Sep 2019 00:01:02 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Pd4Z1clYz4ZZ7; Fri, 6 Sep 2019 00:01:02 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 1C040C386; Fri, 6 Sep 2019 00:01:02 +0000 (UTC) (envelope-from gjb@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x86011Qd060767; Fri, 6 Sep 2019 00:01:01 GMT (envelope-from gjb@FreeBSD.org) Received: (from gjb@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x860113D060766; Fri, 6 Sep 2019 00:01:01 GMT (envelope-from gjb@FreeBSD.org) Message-Id: <201909060001.x860113D060766@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: gjb set sender to gjb@FreeBSD.org using -f From: Glen Barber Date: Fri, 6 Sep 2019 00:01:01 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53379 - head/en_US.ISO8859-1/htdocs/releases/12.1R X-SVN-Group: doc-head X-SVN-Commit-Author: gjb X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/releases/12.1R X-SVN-Commit-Revision: 53379 X-SVN-Commit-Repository: doc 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.29 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: Fri, 06 Sep 2019 00:01:02 -0000 Author: gjb Date: Fri Sep 6 00:01:01 2019 New Revision: 53379 URL: https://svnweb.freebsd.org/changeset/doc/53379 Log: Update the 12.1-RELEASE schedule to reflect the code slush is now in effect. Approved by: re (implicit) Sponsored by: Rubicon Communications, LLC (Netgate) Modified: head/en_US.ISO8859-1/htdocs/releases/12.1R/schedule.xml Modified: head/en_US.ISO8859-1/htdocs/releases/12.1R/schedule.xml ============================================================================== --- head/en_US.ISO8859-1/htdocs/releases/12.1R/schedule.xml Thu Sep 5 20:46:54 2019 (r53378) +++ head/en_US.ISO8859-1/htdocs/releases/12.1R/schedule.xml Fri Sep 6 00:01:01 2019 (r53379) @@ -65,7 +65,7 @@
- + From owner-svn-doc-all@freebsd.org Fri Sep 6 13:58:38 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9036AF4750; Fri, 6 Sep 2019 13:58:38 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Pzg23nRXz4P17; Fri, 6 Sep 2019 13:58:38 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 46A511DC57; Fri, 6 Sep 2019 13:58:38 +0000 (UTC) (envelope-from bcr@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x86DwcDs060709; Fri, 6 Sep 2019 13:58:38 GMT (envelope-from bcr@FreeBSD.org) Received: (from bcr@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x86Dwcim060708; Fri, 6 Sep 2019 13:58:38 GMT (envelope-from bcr@FreeBSD.org) Message-Id: <201909061358.x86Dwcim060708@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: bcr set sender to bcr@FreeBSD.org using -f From: Benedict Reuschling Date: Fri, 6 Sep 2019 13:58:38 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53380 - head/en_US.ISO8859-1/articles/freebsd-questions X-SVN-Group: doc-head X-SVN-Commit-Author: bcr X-SVN-Commit-Paths: head/en_US.ISO8859-1/articles/freebsd-questions X-SVN-Commit-Revision: 53380 X-SVN-Commit-Repository: doc 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.29 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: Fri, 06 Sep 2019 13:58:38 -0000 Author: bcr Date: Fri Sep 6 13:58:37 2019 New Revision: 53380 URL: https://svnweb.freebsd.org/changeset/doc/53380 Log: Cleanup this article from most (but not all) igor warnings: - wrap long lines - use tabs instead of spaces - space after content (inserting a  ) - capitalization - use two spaces at sentence start Event: vBSDcon 2019 Modified: head/en_US.ISO8859-1/articles/freebsd-questions/article.xml Modified: head/en_US.ISO8859-1/articles/freebsd-questions/article.xml ============================================================================== --- head/en_US.ISO8859-1/articles/freebsd-questions/article.xml Fri Sep 6 00:01:01 2019 (r53379) +++ head/en_US.ISO8859-1/articles/freebsd-questions/article.xml Fri Sep 6 13:58:37 2019 (r53380) @@ -1,14 +1,24 @@ -
- How to get best results from the FreeBSD-questions mailing - list - +
+ + How to get Best Results from the FreeBSD-questions Mailing + List - GregLehey -
grog@FreeBSD.org
- + + + Greg + Lehey + + +
+ grog@FreeBSD.org +
+ + &tm-attrib.freebsd; @@ -23,89 +33,100 @@ $FreeBSD$ - This document provides useful information for people looking to - prepare an e-mail to the FreeBSD-questions mailing list. Advice and - hints are given that will maximize the chance that the reader will - receive useful replies. + This document provides useful information for people + looking to prepare an e-mail to the FreeBSD-questions mailing + list. Advice and hints are given that will maximize the + chance that the reader will receive useful replies. - This document is regularly posted to the FreeBSD-questions mailing - list. + This document is regularly posted to the FreeBSD-questions + mailing list. Introduction - FreeBSD-questions is a mailing list maintained by - the FreeBSD project to help people who have questions about the normal - use of FreeBSD. Another group, FreeBSD-hackers, - discusses more advanced questions such as future development - work. + FreeBSD-questions is a mailing list + maintained by the FreeBSD project to help people who have + questions about the normal use of FreeBSD. Another group, + FreeBSD-hackers, discusses more advanced + questions such as future development work. - The term hacker has nothing to do with breaking - into other people's computers. The correct term for the latter - activity is cracker, but the popular press has not found - out yet. The FreeBSD hackers disapprove strongly of cracking - security, and have nothing to do with it. For a longer description of - hackers, see Eric Raymond's How To Become - A Hacker + The term hacker has nothing to do with + breaking into other people's computers. The correct term for + the latter activity is cracker, but the popular + press has not found out yet. The FreeBSD hackers disapprove + strongly of cracking security, and have nothing to do with it. + For a longer description of hackers, see Eric Raymond's How + To Become A Hacker - This is a regular posting aimed to help both those seeking advice - from FreeBSD-questions (the newcomers), and also those - who answer the questions (the hackers). + This is a regular posting aimed to help both those seeking + advice from FreeBSD-questions (the newcomers), + and also those who answer the questions (the + hackers). - Inevitably there is some friction, which stems from the different - viewpoints of the two groups. The newcomers accuse the hackers of being - arrogant, stuck-up, and unhelpful, while the hackers accuse the - newcomers of being stupid, unable to read plain English, and expecting - everything to be handed to them on a silver platter. Of course, there is - an element of truth in both these claims, but for the most part these - viewpoints come from a sense of frustration. + Inevitably there is some friction, which stems from the + different viewpoints of the two groups. The newcomers accuse + the hackers of being arrogant, stuck-up, and unhelpful, while + the hackers accuse the newcomers of being stupid, unable to read + plain English, and expecting everything to be handed to them on + a silver platter. Of course, there is an element of truth in + both these claims, but for the most part these viewpoints come + from a sense of frustration. - In this document, I would like to do something to relieve this - frustration and help everybody get better results from - FreeBSD-questions. In the following section, I recommend how to submit - a question; after that, we will look at how to answer one. + In this document, I would like to do something to relieve + this frustration and help everybody get better results from + FreeBSD-questions. In the following section, I recommend how to + submit a question; after that, we will look at how to answer + one. - How to subscribe to FreeBSD-questions + How to Subscribe to + FreeBSD-questions - FreeBSD-questions is a mailing list, so you need mail access. Point - your WWW browser to the information page of the FreeBSD-questions mailing list. - In the section titled Subscribing to freebsd-questions fill - in the Your email address field; the other fields are optional. - + FreeBSD-questions is a mailing list, so you need mail + access. Point your WWW browser to the information page of the + FreeBSD-questions mailing list. In the section titled + Subscribing to freebsd-questions fill + in the Your email address field; the other fields + are optional. - The password fields in the subscription form provide only mild - security, but should prevent others from messing with your - subscription. Do not use a valuable password as - it will occasionally be emailed back to you in cleartext. + The password fields in the subscription form provide only + mild security, but should prevent others from messing with + your subscription. Do not use a valuable + password as it will occasionally be emailed back + to you in cleartext. You will receive a confirmation message from - mailman; follow the included instructions - to complete your subscription. + mailman; follow the included + instructions to complete your subscription. - Finally, when you get the Welcome message from - mailman telling you the details of the list - and subscription area password, please save it. - If you ever should want to leave the list, you will need the information - there. See the next section for more details. + Finally, when you get the Welcome message + from mailman telling you the details + of the list and subscription area password, please + save it. If you ever should want to leave the + list, you will need the information there. See the next section + for more details. - How to unsubscribe from FreeBSD-questions + How to Unsubscribe from + FreeBSD-questions - When you subscribed to FreeBSD-questions, you got a welcome message - from mailman. In this message, amongst - other things, it told you how to unsubscribe. Here is a typical - message: + When you subscribed to FreeBSD-questions, you got a welcome + message from mailman. In this + message, amongst other things, it told you how to unsubscribe. + Here is a typical message: - Welcome to the freebsd-questions@freebsd.org mailing list! + Welcome to the + freebsd-questions@freebsd.org mailing list! To post to this list, send your email to: @@ -139,162 +160,175 @@ prefer. This reminder will also include instructions unsubscribe or change your account options. There is also a button on your options page that will email your current password to you. - From the URL specified in your Welcome message you - may visit the Account management page and enter a request - to Unsubscribe you from FreeBSD-questions mailing - list. + From the URL specified in your Welcome + message you may visit the Account management page + and enter a request to Unsubscribe you from + FreeBSD-questions mailing list. A confirmation message will be sent to you from - mailman; follow the included instructions - to finish unsubscribing. + mailman; follow the included + instructions to finish unsubscribing. - If you have done this, and you still can not figure out what + If you have done this, and you still cannot figure out what is going on, send a message to - freebsd-questions-request@FreeBSD.org, and they will - sort things out for you. Do not send a message to - FreeBSD-questions: they can not help you. + freebsd-questions-request@FreeBSD.org, and they + will sort things out for you. Do not send + a message to FreeBSD-questions: they cannot help you. - Should I ask <literal>-questions</literal> or - <literal>-hackers</literal>? + Should I ask <literal>-questions</literal> + or <literal>-hackers</literal>? Two mailing lists handle general questions about FreeBSD, FreeBSD-questions and - FreeBSD-hackers. In some cases, it is not really - clear which group you should ask. The following criteria should help - for 99% of all questions, however: + FreeBSD-hackers. In some cases, it is not + really clear which group you should ask. The following criteria + should help for 99% of all questions, however: If the question is of a general nature, ask - FreeBSD-questions. Examples might be questions - about installing FreeBSD or the use of a particular &unix; - utility. + FreeBSD-questions. Examples might be + questions about installing FreeBSD or the use of a + particular &unix; utility. - If you think the question relates to a bug, but you are not sure, - or you do not know how to look for it, send the message to - FreeBSD-questions. + If you think the question relates to a bug, but you are + not sure, or you do not know how to look for it, send the + message to FreeBSD-questions. If the question relates to a bug, and you are - sure that it is a bug (for example, you can - pinpoint the place in the code where it happens, and you maybe have - a fix), then send the message to + sure that it is a bug (for example, you + can pinpoint the place in the code where it happens, and you + maybe have a fix), then send the message to FreeBSD-hackers. - If the question relates to enhancements to FreeBSD, and you - can make suggestions about how to implement them, then send the - message to FreeBSD-hackers. + If the question relates to enhancements to FreeBSD, and + you can make suggestions about how to implement them, then + send the message to + FreeBSD-hackers. - There are also a number of other - specialized mailing lists, - which caters to more specific interests. - The criteria above still apply, and - it is in your interest to stick to them, since you are more likely to get - good results that way. + There are also a number of other specialized + mailing lists, which caters to more specific interests. + The criteria above still apply, and it is in your interest to + stick to them, since you are more likely to get good results + that way. - Before submitting a question + Before Submitting a Question - You can (and should) do some things yourself before asking a question - on one of the mailing lists: + You can (and should) do some things yourself before asking a + question on one of the mailing lists: - Try solving the problem on your own. If you post a question which - shows that you have tried to solve the problem, your question will - generally attract more positive attention from people reading it. - Trying to solve the problem yourself will also enhance your understanding - of FreeBSD, and will eventually let you use your knowledge to help others - by answering questions posted to the mailing lists. - + Try solving the problem on your own. If you post a + question which shows that you have tried to solve the + problem, your question will generally attract more positive + attention from people reading it. Trying to solve the + problem yourself will also enhance your understanding of + FreeBSD, and will eventually let you use your knowledge to + help others by answering questions posted to the mailing + lists. - Read the manual pages, and the FreeBSD documentation (either - installed in /usr/doc or accessible via WWW at - http://www.FreeBSD.org), especially the - handbook - and the FAQ. - + Read the manual pages, and the FreeBSD documentation + (either installed in /usr/doc or + accessible via WWW at http://www.FreeBSD.org), + especially the handbook + and the FAQ. - Browse and/or search the archives for the mailing list, to see if your - question or a similar one has been asked (and possibly answered) on the - list. You can browse and/or search the mailing list archives - at https://www.FreeBSD.org/mail - and https://www.FreeBSD.org/search/search.html#mailinglists - respectively. This can be done at other WWW sites as well, for example - at http://marc.theaimsgroup.com. - + Browse and/or search the archives for the mailing list, + to see if your question or a similar one has been asked (and + possibly answered) on the list. You can browse and/or + search the mailing list archives at https://www.FreeBSD.org/mail + and https://www.FreeBSD.org/search/search.html#mailinglists + respectively. This can be done at other WWW sites as well, + for example at http://marc.theaimsgroup.com. - Use a search engine such as Google - or Yahoo to find answers to your question. - + Use a search engine such as Google + or Yahoo to find + answers to your question. - How to submit a question + How to Submit a Question - When submitting a question to FreeBSD-questions, consider the - following points: + When submitting a question to FreeBSD-questions, consider + the following points: Remember that nobody gets paid for answering a FreeBSD - question. They do it of their own free will. You can influence this - free will positively by submitting a well-formulated question - supplying as much relevant information as possible. You can - influence this free will negatively by submitting an incomplete, - illegible, or rude question. It is perfectly possible to send a - message to FreeBSD-questions and not get an answer even if you - follow these rules. It is much more possible to not get an answer if - you do not. In the rest of this document, we will look at how to get - the most out of your question to FreeBSD-questions. + question. They do it of their own free will. You can + influence this free will positively by submitting a + well-formulated question supplying as much relevant + information as possible. You can influence this free will + negatively by submitting an incomplete, illegible, or rude + question. It is perfectly possible to send a message to + FreeBSD-questions and not get an answer even if you follow + these rules. It is much more possible to not get an answer + if you do not. In the rest of this document, we will look + at how to get the most out of your question to + FreeBSD-questions. - Not everybody who answers FreeBSD questions reads every message: - they look at the subject line and decide whether it interests them. - Clearly, it is in your interest to specify a subject. FreeBSD - problem or Help are not enough. If you provide no subject at - all, many people will not bother reading it. If your subject is not - specific enough, the people who can answer it may not read - it. + Not everybody who answers FreeBSD questions reads every + message: they look at the subject line and decide whether it + interests them. Clearly, it is in your interest to specify + a subject. FreeBSD + problem or Help are not enough. If + you provide no subject at all, many people will not bother + reading it. If your subject is not specific enough, the + people who can answer it may not read it. - Format your message so that it is legible, and - PLEASE DO NOT SHOUT!!!!!. We appreciate that a lot of people do not - speak English as their first language, and we try to make - allowances for that, but it is really painful to try to read a - message written full of typos or without any line breaks. + Format your message so that it is legible, and + PLEASE DO NOT SHOUT!!!!!. We appreciate that a lot of + people do not speak English as their first language, and we + try to make allowances for that, but it is really painful to + try to read a message written full of typos or without any + line breaks. - Do not underestimate the effect that a poorly formatted mail - message has, not just on the FreeBSD-questions mailing list. - Your mail message is all people see of you, and if it is poorly - formatted, one line per paragraph, badly spelt, or full of - errors, it will give people a poor impression of you. + Do not underestimate the effect that a poorly formatted + mail message has, not just on the FreeBSD-questions mailing + list. Your mail message is all people see of you, and if it + is poorly formatted, one line per paragraph, badly spelt, or + full of errors, it will give people a poor impression of + you. - A lot of badly formatted messages come from - bad mailers or badly - configured mailers. The following mailers are known to - send out badly formatted messages without you finding out about - them: + A lot of badly formatted messages come from bad + mailers or badly configured mailers. The following + mailers are known to send out badly formatted messages + without you finding out about them: @@ -320,86 +354,92 @@ your options page that will email your current passwor - Make sure your time and time zone are set correctly. This may - seem a little silly, since your message still gets there, but many - of the people you are trying to reach get several hundred messages a - day. They frequently sort the incoming messages by subject and by - date, and if your message does not come before the first answer, they - may assume they missed it and not bother to look. + Make sure your time and time zone are set correctly. + This may seem a little silly, since your message still gets + there, but many of the people you are trying to reach get + several hundred messages a day. They frequently sort the + incoming messages by subject and by date, and if your + message does not come before the first answer, they may + assume they missed it and not bother to look. - Do not include unrelated questions in the same message. Firstly, - a long message tends to scare people off, and secondly, it is more - difficult to get all the people who can answer all the questions to - read the message. + Do not include unrelated questions in the same message. + Firstly, a long message tends to scare people off, and + secondly, it is more difficult to get all the people who can + answer all the questions to read the message. - Specify as much information as possible. This is a difficult - area, and we need to expand on what information you need to submit, - but here is a start: + Specify as much information as possible. This is a + difficult area, and we need to expand on what information + you need to submit, but here is a start: - In nearly every case, it is important to know the version of - FreeBSD you are running. This is particularly the case for - FreeBSD-CURRENT, where you should also specify the date of the - sources, though of course you should not be sending questions - about -CURRENT to FreeBSD-questions. + In nearly every case, it is important to know the + version of FreeBSD you are running. This is + particularly the case for FreeBSD-CURRENT, where you + should also specify the date of the sources, though of + course you should not be sending questions about + -CURRENT to FreeBSD-questions. - With any problem which could be - hardware related, tell us about your hardware. In case of - doubt, assume it is possible that it is hardware. What kind of - CPU are you using? How fast? What motherboard? How much - memory? What peripherals? + + With any problem which could be + hardware related, tell us about your hardware. In case + of doubt, assume it is possible that it is hardware. + What kind of CPU are you using? How fast? What + motherboard? How much memory? What peripherals? - There is a judgement call here, of course, but the output of - the &man.dmesg.8; command can frequently be very useful, since it - tells not just what hardware you are running, but what version of - FreeBSD as well. + There is a judgement call here, of course, but the + output of the &man.dmesg.8; command can frequently be + very useful, since it tells not just what hardware you + are running, but what version of FreeBSD as well. - If you get error messages, do not say I get error - messages, say (for example) I get the error - message 'No route to host'. + If you get error messages, do not say I get + error messages, say (for example) I get + the error message 'No route to host'. If your system panics, do not say My system - panicked, say (for example) my system panicked - with the message 'free vnode isn't'. + panicked, say (for example) my system + panicked with the message 'free vnode + isn't'. - If you have difficulty installing FreeBSD, please tell us - what hardware you have. In particular, it is important to know - the IRQs and I/O addresses of the boards installed in your - machine. + If you have difficulty installing FreeBSD, please + tell us what hardware you have. In particular, it is + important to know the IRQs and I/O addresses of the + boards installed in your machine. - If you have difficulty getting PPP to run, describe the - configuration. Which version of PPP do you use? What kind of - authentication do you have? Do you have a static or dynamic IP - address? What kind of messages do you get in the log - file? + If you have difficulty getting PPP to run, describe + the configuration. Which version of PPP do you use? + What kind of authentication do you have? Do you have a + static or dynamic IP address? What kind of messages do + you get in the log file? - A lot of the information you need to supply is the output of - programs, such as &man.dmesg.8;, or console messages, which usually - appear in /var/log/messages. Do not try to copy - this information by typing it in again; it is a real pain, and you are - bound to make a mistake. To send log file contents, either make a - copy of the file and use an editor to trim the information to what - is relevant, or cut and paste into your message. For the output of - programs like &man.dmesg.8;, redirect the output to a file and - include that. For example, + A lot of the information you need to supply is the + output of programs, such as &man.dmesg.8;, or console + messages, which usually appear in + /var/log/messages. Do not try to copy + this information by typing it in again; it is a real pain, + and you are bound to make a mistake. To send log file + contents, either make a copy of the file and use an editor + to trim the information to what is relevant, or cut and + paste into your message. For the output of programs like + &man.dmesg.8;, redirect the output to a file and include + that. For example, &prompt.user; dmesg > /tmp/dmesg.out @@ -408,21 +448,22 @@ your options page that will email your current passwor - If you do all this, and you still do not get an answer, there - could be other reasons. For example, the problem is so complicated - that nobody knows the answer, or the person who does know the answer - was offline. If you do not get an answer after, say, a week, it - might help to re-send the message. If you do not get an answer to - your second message, though, you are probably not going to get one - from this forum. Resending the same message again and again will - only make you unpopular. + If you do all this, and you still do not get an answer, + there could be other reasons. For example, the problem is + so complicated that nobody knows the answer, or the person + who does know the answer was offline. If you do not get an + answer after, say, a week, it might help to re-send the + message. If you do not get an answer to your second + message, though, you are probably not going to get one + from this forum. Resending the same message again and again + will only make you unpopular. - To summarize, let's assume you know the answer to the following - question (yes, it is the same one in each case). - You choose which of these two questions you would be more prepared to - answer: + To summarize, let's assume you know the answer to the + following question (yes, it is the same one in each case). + You choose which of these two questions you would be more + prepared to answer: Message 1 @@ -437,7 +478,7 @@ so why don't you guys tell me what I doing wrong. Message 2 - Subject: Problems installing FreeBSD + Subject: Problems installing FreeBSD I've just got the FreeBSD 2.1.5 CDROM from Walnut Creek, and I'm having a lot of difficulty installing it. I have a 66 MHz 486 with 16 MB of @@ -449,29 +490,31 @@ fine, but when I try to reboot the system, I get the m - How to follow up to a question + How to Follow up to a Question - Often you will want to send in additional information to a question - you have already sent. The best way to do this is to reply to your - original message. This has three advantages: + Often you will want to send in additional information to a + question you have already sent. The best way to do this is to + reply to your original message. This has three + advantages: - You include the original message text, so people will know what - you are talking about. Do not forget to trim unnecessary text out, - though. + You include the original message text, so people will + know what you are talking about. Do not forget to trim + unnecessary text out, though. - The text in the subject line stays the same (you did remember to - put one in, did you not?). Many mailers will sort messages by - subject. This helps group messages together. + The text in the subject line stays the same (you did + remember to put one in, did you not?). Many mailers will + sort messages by subject. This helps group messages + together. - The message reference numbers in the header will refer to the - previous message. Some mailers, such as - mutt, can + The message reference numbers in the header will refer + to the previous message. Some mailers, such as mutt, can thread messages, showing the exact relationships between the messages. @@ -479,114 +522,122 @@ fine, but when I try to reboot the system, I get the m - How to answer a question + How to Answer a Question + Before you answer a question to FreeBSD-questions, + consider: - Before you answer a question to FreeBSD-questions, consider: - - A lot of the points on submitting questions also apply to - answering questions. Read them. + A lot of the points on submitting questions also apply + to answering questions. Read them. - Has somebody already answered the question? The easiest way to - check this is to sort your incoming mail by subject: then - (hopefully) you will see the question followed by any answers, all - together. + Has somebody already answered the question? The easiest + way to check this is to sort your incoming mail by subject: + then (hopefully) you will see the question followed by any + answers, all together. - If somebody has already answered it, it does not automatically - mean that you should not send another answer. But it makes sense to - read all the other answers first. + If somebody has already answered it, it does not + automatically mean that you should not send another answer. + But it makes sense to read all the other answers + first. - Do you have something to contribute beyond what has already been - said? In general, Yeah, me too answers do not help - much, although there are exceptions, like when somebody is - describing a problem they are having, and they do not know whether it is - their fault or whether there is something wrong with the hardware or - software. If you do send a me too answer, you should + Do you have something to contribute beyond what has + already been said? In general, Yeah, me too + answers do not help much, although there are exceptions, + like when somebody is describing a problem they are having, + and they do not know whether it is their fault or whether + there is something wrong with the hardware or software. If + you do send a me too answer, you should also include any further relevant information. - Are you sure you understand the question? Very frequently, the - person who asks the question is confused or does not express themselves - very well. Even with the best understanding of the system, it is - easy to send a reply which does not answer the question. This - does not help: you will leave the person who submitted the question - more frustrated or confused than ever. If nobody else answers, and - you are not too sure either, you can always ask for more + Are you sure you understand the question? Very + frequently, the person who asks the question is confused or + does not express themselves very well. Even with the best + understanding of the system, it is easy to send a reply + which does not answer the question. This does not help: you + will leave the person who submitted the question more + frustrated or confused than ever. If nobody else answers, + and you are not too sure either, you can always ask for more information. - Are you sure your answer is correct? - If not, wait a day or so. If nobody else comes up with a - better answer, you can still reply and say, for example, I - do not know if this is correct, but since nobody else has - replied, why don't you try replacing your ATAPI CDROM with - a frog?. + Are you sure your answer is correct? If not, wait a day + or so. If nobody else comes up with a better answer, you + can still reply and say, for example, I do not know + if this is correct, but since nobody else has replied, why + don't you try replacing your ATAPI CDROM with a + frog?. - Unless there is a good reason to do otherwise, reply to the - sender and to FreeBSD-questions. Many people on the - FreeBSD-questions are lurkers: they learn by reading - messages sent and replied to by others. If you take a message which - is of general interest off the list, you are depriving these people - of their information. Be careful with group replies; lots of people - send messages with hundreds of CCs. If this is the case, be sure to - trim the Cc: lines appropriately. + Unless there is a good reason to do otherwise, reply to + the sender and to FreeBSD-questions. Many people on the + FreeBSD-questions are lurkers: they learn by + reading messages sent and replied to by others. If you take + a message which is of general interest off the list, you are + depriving these people of their information. Be careful + with group replies; lots of people send messages with + hundreds of CCs. If this is the case, be sure to trim the + Cc: lines appropriately. - Include relevant text from the original message. Trim it to the - minimum, but do not overdo it. It should still be possible for - somebody who did not read the original message to understand what - you are talking about. + Include relevant text from the original message. Trim + it to the minimum, but do not overdo it. It should still be + possible for somebody who did not read the original message + to understand what you are talking about. - Use some technique to identify which text came from the original - message, and which text you add. I personally find that prepending - > to the original message - works best. Leaving white space after the - > and leave empty lines - between your text and the original text both make the result more - readable. + Use some technique to identify which text came from the + original message, and which text you add. I personally find + that prepending >  + to the original message works best. Leaving white space + after the > ; and + leave empty lines between your text and the original text + both make the result more readable. - Put your response in the correct place (after the text to which - it replies). It is very difficult to read a thread of responses - where each reply comes before the text to which it replies. + Put your response in the correct place (after the text + to which it replies). It is very difficult to read a thread + of responses where each reply comes before the text to which + it replies. - Most mailers change the subject line on a reply by prepending a - text such as Re: . If your mailer does not do it - automatically, you should do it manually. + Most mailers change the subject line on a reply by + prepending a text such as Re: . If your + mailer does not do it automatically, you should do it + manually. - If the submitter did not abide by format conventions (lines too - long, inappropriate subject line), please fix - it. In the case of an incorrect subject line (such as - HELP!!??), change the subject line to (say) - Re: Difficulties with sync PPP (was: HELP!!??). That - way other people trying to follow the thread will have less + If the submitter did not abide by format conventions + (lines too long, inappropriate subject line) + please fix it. In the case of an + incorrect subject line (such as HELP!!??), + change the subject line to (say) Re: Difficulties + with sync PPP (was: HELP!!??). That way other + people trying to follow the thread will have less difficulty following it. - In such cases, it is appropriate to say what you did and why you - did it, but try not to be rude. If you find you can not answer - without being rude, do not answer. + In such cases, it is appropriate to say what you did and + why you did it, but try not to be rude. If you find you can + not answer without being rude, do not answer. - If you just want to reply to a message because of its bad - format, just reply to the submitter, not to the list. You can just - send him this message in reply, if you like. + If you just want to reply to a message because of its + bad format, just reply to the submitter, not to the list. + You can just send him this message in reply, if you + like. From owner-svn-doc-all@freebsd.org Fri Sep 6 16:23:43 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 29051F7706; Fri, 6 Sep 2019 16:23:43 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Q2tR04T1z4Xq9; Fri, 6 Sep 2019 16:23:43 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D9E6A1F840; Fri, 6 Sep 2019 16:23:42 +0000 (UTC) (envelope-from johalun@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x86GNgq3050106; Fri, 6 Sep 2019 16:23:42 GMT (envelope-from johalun@FreeBSD.org) Received: (from johalun@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x86GNg4k050105; Fri, 6 Sep 2019 16:23:42 GMT (envelope-from johalun@FreeBSD.org) Message-Id: <201909061623.x86GNg4k050105@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: johalun set sender to johalun@FreeBSD.org using -f From: Johannes Lundberg Date: Fri, 6 Sep 2019 16:23:42 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53381 - head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Group: doc-head X-SVN-Commit-Author: johalun X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/porters-handbook/versions X-SVN-Commit-Revision: 53381 X-SVN-Commit-Repository: doc 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.29 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: Fri, 06 Sep 2019 16:23:43 -0000 Author: johalun (src committer) Date: Fri Sep 6 16:23:42 2019 New Revision: 53381 URL: https://svnweb.freebsd.org/changeset/doc/53381 Log: Document OSVERSION 1300046. 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 Fri Sep 6 13:58:37 2019 (r53380) +++ head/en_US.ISO8859-1/books/porters-handbook/versions/chapter.xml Fri Sep 6 16:23:42 2019 (r53381) @@ -453,6 +453,13 @@ is spelled &, < is < and > is >. September 3, 2019 13.0-CURRENT after adding sysctlbyname system call + + + 1300046 + 351937 + September 6, 2019 + 13.0-CURRENT after LinuxKPI sysfs improvements. +
Code slush begins 6 September 2019-6 September 2019 Release Engineers announce that all further commits to the &local.branch.stable; branch will not require explicit approval, however new features should be avoided.
From owner-svn-doc-all@freebsd.org Sat Sep 7 20:52:19 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 988A5DCBA6; Sat, 7 Sep 2019 20:52:19 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46Qmnv3bZxz3ynn; Sat, 7 Sep 2019 20:52:19 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 60335B42F; Sat, 7 Sep 2019 20:52:19 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x87KqJLH076453; Sat, 7 Sep 2019 20:52:19 GMT (envelope-from linimon@FreeBSD.org) Received: (from linimon@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x87KqJIi076436; Sat, 7 Sep 2019 20:52:19 GMT (envelope-from linimon@FreeBSD.org) Message-Id: <201909072052.x87KqJIi076436@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: linimon set sender to linimon@FreeBSD.org using -f From: Mark Linimon Date: Sat, 7 Sep 2019 20:52:19 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53382 - head/en_US.ISO8859-1/books/porters-handbook/porting-dads X-SVN-Group: doc-head X-SVN-Commit-Author: linimon X-SVN-Commit-Paths: head/en_US.ISO8859-1/books/porters-handbook/porting-dads X-SVN-Commit-Revision: 53382 X-SVN-Commit-Repository: doc 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.29 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: Sat, 07 Sep 2019 20:52:19 -0000 Author: linimon Date: Sat Sep 7 20:52:18 2019 New Revision: 53382 URL: https://svnweb.freebsd.org/changeset/doc/53382 Log: Add a new section "Cluster-Specific Considerations" to discourage the use of -march=native by default. Approved by: mat Differential Revision: D20885 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 Fri Sep 6 16:23:42 2019 (r53381) +++ head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml Sat Sep 7 20:52:18 2019 (r53382) @@ -569,6 +569,24 @@ cc -o someprogram source1.o source2.o -L/usr/local/lib + + + Cluster-Specific Considerations + + + + Some ports attempt to tune themselves to the + exact machine they are being built on by specifying + -march=native to the compiler. + This should be avoided: either list it under an + off-by-default option, or delete it entirely. + + Otherwise, the default package produced by the + build cluster might not run on every single machine + of that ARCH. + + + From owner-svn-doc-all@freebsd.org Sat Sep 7 22:11:27 2019 Return-Path: Delivered-To: svn-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0EB65DE424; Sat, 7 Sep 2019 22:11:27 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits) client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 46QpYB6VjBz4369; Sat, 7 Sep 2019 22:11:26 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C2656C2ED; Sat, 7 Sep 2019 22:11:26 +0000 (UTC) (envelope-from ler@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id x87MBQhB022163; Sat, 7 Sep 2019 22:11:26 GMT (envelope-from ler@FreeBSD.org) Received: (from ler@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id x87MBQBf022162; Sat, 7 Sep 2019 22:11:26 GMT (envelope-from ler@FreeBSD.org) Message-Id: <201909072211.x87MBQBf022162@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: ler set sender to ler@FreeBSD.org using -f From: Larry Rosenman Date: Sat, 7 Sep 2019 22:11:26 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r53383 - head/share/pgpkeys X-SVN-Group: doc-head X-SVN-Commit-Author: ler X-SVN-Commit-Paths: head/share/pgpkeys X-SVN-Commit-Revision: 53383 X-SVN-Commit-Repository: doc 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.29 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: Sat, 07 Sep 2019 22:11:27 -0000 Author: ler (ports committer) Date: Sat Sep 7 22:11:26 2019 New Revision: 53383 URL: https://svnweb.freebsd.org/changeset/doc/53383 Log: refresh my pgp key. Modified: head/share/pgpkeys/ler.key Modified: head/share/pgpkeys/ler.key ============================================================================== --- head/share/pgpkeys/ler.key Sat Sep 7 20:52:18 2019 (r53382) +++ head/share/pgpkeys/ler.key Sat Sep 7 22:11:26 2019 (r53383) @@ -3,12 +3,13 @@ sh addkey.sh ler 697C99B1AB48A77D ; --> uid Larry Rosenman uid Larry Rosenman -sub rsa2048/FD0614DC2AD28ED9 2017-01-10 [E] [expires: 2020-01-10] +uid Larry Rosenman (WhereTo Senior Site Reliability Engineer) +sub rsa2048/FD0614DC2AD28ED9 2017-01-10 [E] [expires: 2022-09-06] ]]>