From owner-freebsd-doc@FreeBSD.ORG Sun Feb 9 00:38:21 2014 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 77AF4312; Sun, 9 Feb 2014 00:38:21 +0000 (UTC) Received: from prod2.absolight.net (mx3.absolight.net [IPv6:2a01:678:2:100::25]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 32B7D1DC3; Sun, 9 Feb 2014 00:38:21 +0000 (UTC) Received: from prod2.absolight.net (localhost [127.0.0.1]) by prod2.absolight.net (Postfix) with ESMTP id D67EDBDC2E; Sun, 9 Feb 2014 01:38:17 +0100 (CET) Received: from atuin.in.mat.cc (atuin.in.mat.cc [79.143.241.205]) by prod2.absolight.net (Postfix) with ESMTPA id B4718BDC24; Sun, 9 Feb 2014 01:38:17 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by atuin.in.mat.cc (Postfix) with ESMTP id DCB9CCE2E9D8; Sun, 9 Feb 2014 01:38:16 +0100 (CET) Date: Sun, 09 Feb 2014 01:38:14 +0100 From: Mathieu Arnold To: Tom Rhodes , portmgr@FreeBSD.org, doceng@FreeBSD.org, doc@FreeBSD.org Subject: Re: Fw: [WIP]: Splitting up the porters handbook Message-ID: <0FCA77C85D8D90BD96DD85FB@atuin.in.mat.cc> In-Reply-To: <20140208105930.48523a89.trhodes@FreeBSD.org> References: <20140208105930.48523a89.trhodes@FreeBSD.org> X-Mailer: Mulberry/4.0.8 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 00:38:21 -0000 +--On 8 f=C3=A9vrier 2014 10:59:30 -0500 Tom Rhodes = wrote: | Hi, |=20 | So - today I spent a few moments (and a few for loops) splitting | up the porters-handbook into several sections. Here is the WIP | patch: |=20 | http://people.freebsd.org/~trhodes/NEW-PH.diff |=20 | Please note it DOES NOT BUILD just yet. Before I actually go | through the trouble of finishing this, is there going to be | a lot of push back? Can I continue and commit (a version that | builds of course) and then the team can work together to polish | off the rough edges with me or should I just not bother? Thanks, |=20 | I'm going to not work on this anymore today while I wait for | feedback - if it's generally positive, I'll try to finish it | up tonight/tomorrow morning and start the commits. Cheers, Splitting it would be great, it's a bit hard to find things in it right = now. --=20 Mathieu Arnold From owner-freebsd-doc@FreeBSD.ORG Sun Feb 9 01:44:53 2014 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E5B68A4A; Sun, 9 Feb 2014 01:44:53 +0000 (UTC) Received: from homiemail-a54.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by mx1.freebsd.org (Postfix) with ESMTP id C4F1A12B4; Sun, 9 Feb 2014 01:44:53 +0000 (UTC) Received: from homiemail-a54.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTP id 230D440122130; Sat, 8 Feb 2014 17:44:53 -0800 (PST) Received: from dreadnaught (ip68-100-185-59.dc.dc.cox.net [68.100.185.59]) (Authenticated sender: trhodes@fbsdsecure.org) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTPA id 5E25C4012210B; Sat, 8 Feb 2014 17:44:51 -0800 (PST) Date: Sat, 8 Feb 2014 20:44:50 -0500 From: Tom Rhodes To: Mathieu Arnold Subject: Re: Fw: [WIP]: Splitting up the porters handbook Message-Id: <20140208204450.23277805.trhodes@FreeBSD.org> In-Reply-To: <0FCA77C85D8D90BD96DD85FB@atuin.in.mat.cc> References: <20140208105930.48523a89.trhodes@FreeBSD.org> <0FCA77C85D8D90BD96DD85FB@atuin.in.mat.cc> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; x86_64-unknown-freebsd9.2) Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: doceng@FreeBSD.org, doc@FreeBSD.org, portmgr@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 01:44:54 -0000 On Sun, 09 Feb 2014 01:38:14 +0100 Mathieu Arnold wrote: > +--On 8 f=C3=A9vrier 2014 10:59:30 -0500 Tom Rhodes = wrote: > | Hi, > |=20 > | So - today I spent a few moments (and a few for loops) splitting > | up the porters-handbook into several sections. Here is the WIP > | patch: > |=20 > | http://people.freebsd.org/~trhodes/NEW-PH.diff > |=20 > | Please note it DOES NOT BUILD just yet. Before I actually go > | through the trouble of finishing this, is there going to be > | a lot of push back? Can I continue and commit (a version that > | builds of course) and then the team can work together to polish > | off the rough edges with me or should I just not bother? Thanks, > |=20 > | I'm going to not work on this anymore today while I wait for > | feedback - if it's generally positive, I'll try to finish it > | up tonight/tomorrow morning and start the commits. Cheers, >=20 > Splitting it would be great, it's a bit hard to find things in it right n= ow. >=20 Ok, I'll put it in the repo, thanks for the feedback! --=20 Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Sun Feb 9 03:56:14 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D06CFE51; Sun, 9 Feb 2014 03:56:14 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A10DF102F; Sun, 9 Feb 2014 03:56:14 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s193uEN5049078; Sun, 9 Feb 2014 03:56:14 GMT (envelope-from trhodes@freefall.freebsd.org) Received: (from trhodes@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s193uEXU049077; Sun, 9 Feb 2014 03:56:14 GMT (envelope-from trhodes) Date: Sun, 9 Feb 2014 03:56:14 GMT Message-Id: <201402090356.s193uEXU049077@freefall.freebsd.org> To: trhodes@FreeBSD.org, freebsd-doc@FreeBSD.org, mav@FreeBSD.org From: trhodes@FreeBSD.org Subject: Re: docs/185602: Possible scsi(4) typo X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 03:56:14 -0000 Synopsis: Possible scsi(4) typo Responsible-Changed-From-To: freebsd-doc->mav Responsible-Changed-By: trhodes Responsible-Changed-When: Sun Feb 9 03:55:55 UTC 2014 Responsible-Changed-Why: Over to mav for review. http://www.freebsd.org/cgi/query-pr.cgi?pr=185602 From owner-freebsd-doc@FreeBSD.ORG Sun Feb 9 04:13:54 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 794E8299; Sun, 9 Feb 2014 04:13:54 +0000 (UTC) Received: from anubis.delphij.net (anubis.delphij.net [IPv6:2001:470:1:117::25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4F8F9115E; Sun, 9 Feb 2014 04:13:54 +0000 (UTC) Received: from delphij-macbook.local (c-67-188-85-47.hsd1.ca.comcast.net [67.188.85.47]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by anubis.delphij.net (Postfix) with ESMTPSA id 91148DDFF; Sat, 8 Feb 2014 20:13:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=delphij.net; s=anubis; t=1391919233; bh=ZNhoz1r8YDkVNmvHunOXqgZlk/yWjX2aZoXc3FeciZM=; h=Date:From:Reply-To:To:Subject:References:In-Reply-To; b=cXEcwMLLiGP7UD7OZQKi7A1RDNpFy+///fwTJhyjtopI63CYWaFRLeCSDxPeausq+ XYI/thJkGJb+u1pZ/gjywt4AtbL9HtcV3V0Q7tRj6kHrLz9L+zCo6wNhrKYgPxTcGj XKa+caBLaqw1D5XYKp+ozU9RAeCQyUP740Umrvz0= Message-ID: <52F70083.2090409@delphij.net> Date: Sat, 08 Feb 2014 20:13:55 -0800 From: Xin Li Organization: The FreeBSD Project MIME-Version: 1.0 To: trhodes@FreeBSD.org, freebsd-doc@FreeBSD.org, mav@FreeBSD.org Subject: Re: docs/185602: Possible scsi(4) typo References: <201402090356.s193uEXU049077@freefall.freebsd.org> In-Reply-To: <201402090356.s193uEXU049077@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: d@delphij.net List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 04:13:54 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 2/8/14, 7:56 PM, trhodes@FreeBSD.org wrote: > Synopsis: Possible scsi(4) typo > > Responsible-Changed-From-To: freebsd-doc->mav > Responsible-Changed-By: trhodes Responsible-Changed-When: Sun Feb 9 > 03:55:55 UTC 2014 Responsible-Changed-Why: Over to mav for review. I think the change is reasonable. Note that ahc/ahd are no longer popular and we probably want to use some more modern hardware in the examples. Cheers, -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJS9wCDAAoJEJW2GBstM+nsVt0P/0FIw0Ds6y0sJvsXpMvNotdh NISh2AW5gwTPtHdSxWXVQKktMK05e0TmBmIDlSMs9HYtM6hybP4lBKnO7pbhjGFN esKJfkIXtolZYGpjCtBO2QB0x/P3aVWT9WakG2daXbDWny/jXaZ5WQ9IENJz3Aj8 CRtXeMD2Dh3JpCsK0UX6b1Ar9N86fmIKl25vYr9I9JjXWLpxByVgB0PQMYvq5r03 MgO6O4sohNzlx7hvTlximMK0lJBmcfZeAJ44EuML+Q2Ci2XzBOhAovHYQB2F54Jl +KWJn5mXybUXdRN/BY7YBfVMo6SJNG4/8NepSQEcBcqmYDlSW68PMmTOli4cV/pV KkNr8XTGgN9zFiDjg7cr91h7FJbcofYYwC+nZZeoDRMU1onFETzb61qDn3iAtKQS Dl/bNpLcbPGKTZOrc2JNR47na3yOlA2yGGi63m4qL3J41pPRKw9lX20qP+5RNeCW dBf/cQROI7J1wIOfRH/x0XXB0SYCpq7CtI+ren+ihcCkzI5azCReVTIwvy6RMPv5 N1J5EnhkhF1gyYDR0LHmqBHmhZ/7GbgtRB+ntxwOUVk0r4kbVBlHapwvHFFq2Tfx CzafH7GAEN6OW+uRxxdlTtWcFFXf4UU4qiJT/w4j7Jh/ocm2DX+9jnmBmNhqMK+e ENPcCvUsFqBN+iWP8feG =99CY -----END PGP SIGNATURE----- From owner-freebsd-doc@FreeBSD.ORG Sun Feb 9 18:57:06 2014 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BFC5E7C8 for ; Sun, 9 Feb 2014 18:57:06 +0000 (UTC) Received: from s87.loopia.se (s87.loopia.se [194.9.94.111]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7172A1C84 for ; Sun, 9 Feb 2014 18:57:05 +0000 (UTC) Received: from s87.loopia.se (localhost [127.0.0.1]) by s87.loopia.se (Postfix) with ESMTP id 9CC861D057CA for ; Sun, 9 Feb 2014 19:48:59 +0100 (CET) X-Virus-Scanned: amavisd-new at outgoing-smtp.loopia.se X-Spam-Flag: NO X-Spam-Score: 2.203 X-Spam-Level: ** X-Spam-Status: No, score=2.203 tagged_above=-999 required=15 tests=[HTML_EXTRA_CLOSE=0.001, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.001, MIME_HTML_ONLY=2.199, TVD_SPACE_RATIO=0.001] autolearn=disabled Received: from s87.loopia.se ([127.0.0.1]) by s87.loopia.se (s87.loopia.se [127.0.0.1]) (amavisd-new, port 10024) with LMTP id AS4GIYlndejL for ; Sun, 9 Feb 2014 19:48:59 +0100 (CET) Received: from s408.loopia.se (s408.loopia.se [194.9.94.234]) by s87.loopia.se (Postfix) with ESMTP id 52A501D057BB for ; Sun, 9 Feb 2014 19:48:59 +0100 (CET) Received: from s408.loopia.se (localhost [127.0.0.1]) by s408.loopia.se (8.14.7/8.14.7) with ESMTP id s19IkruT075440 for ; Sun, 9 Feb 2014 19:46:53 +0100 (CET) (envelope-from evangeline_gillespie@nifon.rs) Received: (from www@localhost) by s408.loopia.se (8.14.7/8.14.7/Submit) id s19Ikr0J075439; Sun, 9 Feb 2014 19:46:53 +0100 (CET) (envelope-from evangeline_gillespie@nifon.rs) Date: Sun, 9 Feb 2014 19:46:53 +0100 (CET) Message-Id: <201402091846.s19Ikr0J075439@s408.loopia.se> X-Authentication-Warning: s408.loopia.se: www set sender to evangeline_gillespie@nifon.rs using -f X-Loopia-Domain: nifon.rs To: doc@freebsd.org Subject: Coming over From: "Evangeline Gillespie" X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Evangeline Gillespie List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 18:57:06 -0000 Heh :) Using a micro bullet on the clit and toying [1]http://www.immobilien-borchers-littel.de/components/com_search/aabc. html References 1. http://www.immobilien-borchers-littel.de/components/com_search/aabc.html From owner-freebsd-doc@FreeBSD.ORG Sun Feb 9 22:20:01 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EBDEC850 for ; Sun, 9 Feb 2014 22:20:00 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C475E1CDA for ; Sun, 9 Feb 2014 22:20:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s19MK0DH012995 for ; Sun, 9 Feb 2014 22:20:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s19MK0sT012994; Sun, 9 Feb 2014 22:20:00 GMT (envelope-from gnats) Resent-Date: Sun, 9 Feb 2014 22:20:00 GMT Resent-Message-Id: <201402092220.s19MK0sT012994@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Jamie Landeg-Jones Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 943F476A for ; Sun, 9 Feb 2014 22:18:22 +0000 (UTC) Received: from pacha.mail.dyslexicfish.net (catnip.dyslexicfish.net [91.109.5.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 2B9811CC4 for ; Sun, 9 Feb 2014 22:18:20 +0000 (UTC) Received: from catnip.dyslexicfish.net (470130.vps-10.com [91.109.5.35] (may be forged)) by pacha.mail.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id s1972GQf067726 for ; Sun, 9 Feb 2014 07:02:17 GMT (envelope-from jamie@catnip.dyslexicfish.net) Received: (from jamie@localhost) by catnip.dyslexicfish.net (8.14.5/8.14.5/Submit) id s1972G1s067725; Sun, 9 Feb 2014 07:02:16 GMT (envelope-from jamie) Message-Id: <201402090702.s1972G1s067725@catnip.dyslexicfish.net> Date: Sun, 9 Feb 2014 07:02:16 GMT From: Jamie Landeg-Jones To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/186608: typo in 'ctime(3) man page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Jamie Landeg-Jones List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 Feb 2014 22:20:01 -0000 >Number: 186608 >Category: docs >Synopsis: typo in 'ctime(3) man page >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Sun Feb 09 22:20:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Jamie Landeg-Jones >Release: FreeBSD 10.0-STABLE amd64 >Organization: >Environment: System: FreeBSD catnip.dyslexicfish.net 10.0-STABLE FreeBSD 10.0-STABLE #0: Wed Jan 22 09:10:20 GMT 2014 root@catflap.dyslexicfish.net:/usr/obj/usr/src/sys/CATFLAP amd64 >Description: Another typo. This time in ctime.3 man page.. I realise this is in 'contrib' but there doesn't seem to be any info regarding who this is pulled from. I hope I don't get the reputation for most anal contributor :-( (Is a PR the best way to report something so insignificant? Seems like overkill... Gimme doc commit access!) Anyway.... The word 'leaves' instead of 'leave' in the following line: "-these functions leaves their result in an internal static object and return" cheers, Jamie >How-To-Repeat: man 3 ctime >Fix: apply patch (!) --- patch begins here --- --- contrib/tzcode/stdtime/ctime.3.orig 2014-02-09 06:47:03.000000000 +0000 +++ contrib/tzcode/stdtime/ctime.3 2014-02-09 06:47:47.000000000 +0000 @@ -342,7 +342,7 @@ and the .Fn \&_r variants of the other functions, -these functions leaves their result in an internal static object and return +these functions leave their result in an internal static object and return a pointer to that object. Subsequent calls to these function will modify the same object. --- patch ends here --- >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Mon Feb 10 00:27:03 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9142E150 for ; Mon, 10 Feb 2014 00:27:03 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 657B11750 for ; Mon, 10 Feb 2014 00:27:03 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.146.73]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id CCDAC5BFF8 for ; Mon, 10 Feb 2014 00:27:02 +0000 (UTC) Message-ID: <52F81CD7.1050008@allanjude.com> Date: Sun, 09 Feb 2014 19:27:03 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-doc@FreeBSD.org Subject: ZFS project branch update X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="3BGSrEJJNaJ6iO012Bk8AIIhrDki9cNVw" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 00:27:03 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --3BGSrEJJNaJ6iO012Bk8AIIhrDki9cNVw Content-Type: multipart/mixed; boundary="------------030702080803050203020007" This is a multi-part message in MIME format. --------------030702080803050203020007 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Attached find a giant white space patch, fixes every igor warning, and updates a lot of markup (acronym, application, using option instead of literal) etc. --=20 Allan Jude --------------030702080803050203020007 Content-Type: text/plain; charset=windows-1252; name="zfs.whitespace_markup.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="zfs.whitespace_markup.diff" Index: chapter.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- chapter.xml (revision 43854) +++ chapter.xml (working copy) @@ -468,9 +468,10 @@ Doing so is not recommended! Checksums take very little storage space and provide data - integrity. Many ZFS features will not work properly with - checksums disabled. There is also no noticeable performance - gain from disabling these checksums. + integrity. Many ZFS features will not + work properly with checksums disabled. There is also no + noticeable performance gain from disabling these + checksums. =20 Checksum verification is known as @@ -513,10 +514,10 @@ <command>zpool</command> Administration =20 - The administration of ZFS is divided between two main - utilities. The zpool utility which controls - the operation of the pool and deals with adding, removing, - replacing and managing disks, and the + The administration of ZFS is divided + between two main utilities. The zpool + utility which controls the operation of the pool and deals with + adding, removing, replacing and managing disks, and the zfs utility, which deals with creating, destroying and managing datasets (both filesystems and= @@ -525,12 +526,12 @@ Creating & Destroying Storage Pools =20 - Creating a ZFS Storage Pool (zpool) - involves making a number of decisions that are relatively - permanent because the structure of the pool cannot be changed - after the pool has been created. The most important decision - is what types of vdevs to group the physical disks into. See - the list of + Creating a ZFS Storage Pool + (zpool) involves making a number of + decisions that are relatively permanent because the structure + of the pool cannot be changed after the pool has been created. + The most important decision is what types of vdevs to group + the physical disks into. See the list of vdev types for details about the possible options. After the pool has been created, most vdev types do not allow additional disks to be added to @@ -542,13 +543,13 @@ created, instead the data must be backed up and the pool recreated. =20 - A ZFS pool that is no longer needed can be destroyed so - that the disks making up the pool can be reused in another - pool or for other purposes. Destroying a pool involves - unmounting all of the datasets in that pool. If the datasets - are in use, the unmount operation will fail and the pool will - not be destroyed. The destruction of the pool can be forced - with , but this can cause + A ZFS pool that is no longer needed can + be destroyed so that the disks making up the pool can be + reused in another pool or for other purposes. Destroying a + pool involves unmounting all of the datasets in that pool. If + the datasets are in use, the unmount operation will fail and + the pool will not be destroyed. The destruction of the pool + can be forced with , but this can cause undefined behavior in applications which had open files on those datasets. @@ -566,13 +567,14 @@ When adding disks to the existing vdev is not an option, as in the case of RAID-Z, the other option is to add a vdev to the pool. It is possible, but discouraged, to mix vdev types. - ZFS stripes data across each of the vdevs. For exam= ple, if - there are two mirror vdevs, then this is effectively a - RAID 10, striping the writes across the two - sets of mirrors. Because of the way that space is allocated - in ZFS to attempt to have each vdev reach - 100% full at the same time, there is a performance penalty if - the vdevs have different amounts of free space. + ZFS stripes data across each of the vdevs. + For example, if there are two mirror vdevs, then this is + effectively a RAID 10, striping the writes + across the two sets of mirrors. Because of the way that space + is allocated in ZFS to attempt to have each + vdev reach 100% full at the same time, there is a performance + penalty if the vdevs have different amounts of free + space. =20 Currently, vdevs cannot be removed from a zpool, and disks can only be removed from a mirror if there is enough remaining @@ -597,8 +599,8 @@ Dealing with Failed Devices =20 - When a disk in a ZFS pool fails, the vdev that the disk - belongs to will enter the + When a disk in a ZFS pool fails, the + vdev that the disk belongs to will enter the Degraded state. In this state, all of the data stored on the vdev is still available, but performance may be impacted because missing @@ -629,7 +631,7 @@ does not match the one recorded on another device that is part of the storage pool. For example, a mirror with two disks where one drive is starting to malfunction and cannot properly - store the data anymore. This is even worse when the data has + store the data any more. This is even worse when the data has not been accessed for a long time in long term archive storage for example. Traditional file systems need to run algorithms that check and repair the data like the &man.fsck.8; program. @@ -645,8 +647,8 @@ operation. =20 The following example will demonstrate this self-healing - behavior in ZFS. First, a mirrored pool of two disks - /dev/ada0 and + behavior in ZFS. First, a mirrored pool of + two disks /dev/ada0 and /dev/ada1 is created. =20 &prompt.root; zpool create healer<= /replaceable> mirror /dev/ada0 /d= ev/ada1 @@ -682,19 +684,20 @@ =20 Next, data corruption is simulated by writing random data to the beginning of one of the disks that make up the mirror. - To prevent ZFS from healing the data as soon as it detects it, - we export the pool first and import it again - afterwards. + To prevent ZFS from healing the data as + soon as it detects it, we export the pool first and import it + again afterwards. =20 This is a dangerous operation that can destroy vital data. It is shown here for demonstrational purposes only - and should not be attempted during normal operation of a ZFS - storage pool. Nor should this dd example - be run on a disk with a different filesystem on it. Do not - use any other disk device names other than the ones that are - part of the ZFS pool. Make sure that proper backups of the - pool are created before running the command! + and should not be attempted during normal operation of a + ZFS storage pool. Nor should this + dd example be run on a disk with a + different filesystem on it. Do not use any other disk + device names other than the ones that are part of the + ZFS pool. Make sure that proper backups + of the pool are created before running the command! =20 &prompt.root; zpool export healer<= /replaceable> @@ -704,11 +707,12 @@ 209715200 bytes transferred in 62.992162 secs (3329227 bytes/sec) &prompt.root; zpool import healer =20 - The ZFS pool status shows that one device has experienced - an error. It is important to know that applications reading - data from the pool did not receive any data with a wrong - checksum. ZFS did provide the application with the data from - the ada0 device that has the correct + The ZFS pool status shows that one + device has experienced an error. It is important to know that + applications reading data from the pool did not receive any + data with a wrong checksum. ZFS did + provide the application with the data from the + ada0 device that has the correct checksums. The device with the wrong checksum can be found easily as the CKSUM column contains a value greater than zero. @@ -732,8 +736,8 @@ =20 errors: No known data errors =20 - ZFS has detected the error and took care of it by using - the redundancy present in the unaffected + ZFS has detected the error and took + care of it by using the redundancy present in the unaffected ada0 mirror disk. A checksum comparison with the original one should reveal whether the pool is consistent again. @@ -745,17 +749,18 @@ =20 The two checksums that were generated before and after the intentional tampering with the pool data still match. This - shows how ZFS is capable of detecting and correcting any - errors automatically when the checksums do not match anymore. - Note that this is only possible when there is enough - redundancy present in the pool. A pool consisting of a single - device has no self-healing capabilities. That is also the - reason why checksums are so important in ZFS and should not be - disabled for any reason. No &man.fsck.8; or similar - filesystem consistency check program is required to detect and - correct this and the pool was available the whole time. A - scrub operation is now required to remove the falsely written - data from ada1. + shows how ZFS is capable of detecting and + correcting any errors automatically when the checksums do not + match any more. Note that this is only possible when there is + enough redundancy present in the pool. A pool consisting of a + single device has no self-healing capabilities. That is also + the reason why checksums are so important in + ZFS and should not be disabled for any + reason. No &man.fsck.8; or similar filesystem consistency + check program is required to detect and correct this and the + pool was available the whole time. A scrub operation is now + required to remove the falsely written data from + ada1. =20 &prompt.root; zpool scrub healer &prompt.root; zpool status healer<= /userinput> @@ -783,7 +788,7 @@ ada0 and corrects all data that has a wrong checksum on ada1. This is indicated by the (repairing) output from - the zpool status command. After the + zpool status. After the operation is complete, the pool status has changed to the following: =20 @@ -810,7 +815,7 @@ has been synchronized from ada0 to ada1, the error messages can be cleared from the pool status by running zpool - clear. + clear. =20 &prompt.root; zpool clear healer &prompt.root; zpool status healer<= /userinput> @@ -834,10 +839,10 @@ Growing a Pool =20 - The usable size of a redundant ZFS pool is limited by the - size of the smallest device in the vdev. If each device in - the vdev is replaced sequentially, after the smallest device - has completed the + The usable size of a redundant ZFS pool + is limited by the size of the smallest device in the vdev. If + each device in the vdev is replaced sequentially, after the + smallest device has completed the replace or resilver operation, the pool can grow based on the size of the new smallest @@ -854,13 +859,14 @@ another system. All datasets are unmounted, and each device is marked as exported but still locked so it cannot be used by other disk subsystems. This allows pools to be imported on - other machines, other operating systems that support ZFS, and - even different hardware architectures (with some caveats, see - &man.zpool.8;). When a dataset has open files, - can be used to force the export - of a pool. causes the datasets to be - forcibly unmounted, which can cause undefined behavior in the - applications which had open files on those datasets. + other machines, other operating systems that support + ZFS, and even different hardware + architectures (with some caveats, see &man.zpool.8;). When a + dataset has open files, can be used to + force the export of a pool. causes the + datasets to be forcibly unmounted, which can cause undefined + behavior in the applications which had open files on those + datasets. =20 Importing a pool automatically mounts the datasets. This may not be the desired behavior, and can be prevented with @@ -878,17 +884,17 @@ Upgrading a Storage Pool =20 After upgrading &os;, or if a pool has been imported from - a system using an older version of ZFS, the pool can be - manually upgraded to the latest version of ZFS. Consider - whether the pool may ever need to be imported on an older - system before upgrading. The upgrade process is unreversible - and cannot be undone. + a system using an older version of ZFS, the + pool can be manually upgraded to the latest version of + ZFS. Consider whether the pool may ever + need to be imported on an older system before upgrading. The + upgrade process is unreversible and cannot be undone. =20 - The newer features of ZFS will not be available until - zpool upgrade has completed. - can be used to see what new features will - be provided by upgrading, as well as which features are - already supported by the existing version. + The newer features of ZFS will not be + available until zpool upgrade has + completed. can be used to see what new + features will be provided by upgrading, as well as which + features are already supported by the existing version. =20 @@ -928,9 +934,9 @@ pools is displayed. =20 zpool history can show even more - information when the options -i or - -l are provided. The option - -i displays user initiated events as well + information when the options or + are provided. The option + displays user initiated events as well as internally logged ZFS events. =20 &prompt.root; zpool history -i @@ -943,8 +949,8 @@ 2013-02-27.18:51:13 [internal create txg:55] dataset =3D 39 2013-02-27.18:51:18 zfs create tank/backup =20 - More details can be shown by adding - -l. History records are shown in a long format, + More details can be shown by adding . + History records are shown in a long format, including information like the name of the user who issued the command and the hostname on which the change was made. =20 @@ -1051,11 +1057,12 @@ Creating & Destroying Datasets =20 Unlike traditional disks and volume managers, space - in ZFS is not preallocated. With traditional - file systems, once all of the space was partitioned and - assigned, there was no way to add an additional file system - without adding a new disk. With ZFS, new - file systems can be created at any time. Each ZFS is not preallocated. With + traditional file systems, once all of the space was + partitioned and assigned, there was no way to add an + additional file system without adding a new disk. With + ZFS, new file systems can be created at any + time. Each dataset has properties including features like compression, deduplication, caching and quoteas, as well as other useful @@ -1250,25 +1257,27 @@ ZFS Replication =20 - Keeping the data on a single pool in one location exposes + Keeping data on a single pool in one location exposes it to risks like theft, natural and human disasters. Keeping regular backups of the entire pool is vital when data needs to - be restored. ZFS provides a built-in serialization feature - that can send a stream representation of the data to standard - output. Using this technique, it is possible to not only - store the data on another pool connected to the local system, - but also to send it over a network to another system that runs - ZFS. To achieve this replication, ZFS uses filesystem - snapshots (see the section on ZFS snapshots for how they - work) to send them from one location to another. The commands - for this operation are zfs send and - zfs receive, respectively. + be restored. ZFS provides a built-in + serialization feature that can send a stream representation of + the data to standard output. Using this technique, it is + possible to not only store the data on another pool connected + to the local system, but also to send it over a network to + another system that runs ZFS. To achieve this replication, + ZFS uses filesystem snapshots (see the + section on ZFS snapshots) to send + them from one location to another. The commands for this + operation are zfs send and + zfs receive, respectively. =20 The following examples will demonstrate the functionality - of ZFS replication using these two pools: + of ZFS replication using these two + pools: =20 - &prompt.root; zpool list + &prompt.root; zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT backup 960M 77K 896M 0% 1.00x ONLINE - mypool 984M 43.7M 940M 4% 1.00x ONLINE - @@ -1277,36 +1286,42 @@ primary pool where data is written to and read from on a regular basis. A second pool, backup is used as a standby in case - the primary pool becomes offline. Note that this is not done - automatically by ZFS, but rather done by a system - administrator in case it is needed. First, a snapshot is - created on mypool to have a copy - of the current state of the data to send to the pool - backup. + the primary pool becomes unavailable. Note that this + fail-over is not done automatically by ZFS, + but rather must be done by a system administrator in the event + that it is needed. Replication requires a snapshot to provide + a consistent version of the file system to be transmitted. + Once a snapshot of mypool has been + created it can be copied to the + backup pool. + ZFS only replicates snapshots, changes + since the most recent snapshot will not be replicated. =20 - &prompt.root; zfs snapshot mypool<= /replaceable>@backup1 -&prompt.root; zfs list -t snapshot + &prompt.root; zfs snapshot mypool@backup1 +&prompt.root; zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT mypool@backup1 0 - 43.6M - =20 Now that a snapshot exists, zfs send can be used to create a stream representing the contents of - the snapshot locally or remotely to another pool. The stream - must be written to the standard output, otherwise ZFS will - produce an error like in this example: + the snapshot, which can be stored as a file, or received by + another pool. The stream will be written to standard + output, which will need to be redirected to a file or pipe + otherwise ZFS will produce an error: =20 - &prompt.root; zfs send mypool@backup1 + &prompt.root; zfs send mypool@backup1 Error: Stream can not be written to a terminal. You must redirect standard output. =20 - The correct way to use zfs send is to - redirect it to a location like the mounted backup pool. - Afterwards, that pool should have the size of the snapshot - allocated, which means all the data contained in the snapshot - was stored on the backup pool. + To backup a dataset with zfs send, + redirect to a file located on the mounted backup pool. First + ensure that the pool has enough free space to accommodate the + size of the snapshot you are sending, which means all of the + data contained in the snapshot, not only the changes in that + snapshot. =20 - &prompt.root; zfs send mypool@backup1 > /backup/backu= p1 -&prompt.root; zpool list + &prompt.root; zfs send mypool@backup1 > /backup/backup1= +&prompt.root; zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT backup 960M 63.7M 896M 6% 1.00x ONLINE - mypool 984M 43.7M 940M 4% 1.00x ONLINE - @@ -1314,9 +1329,33 @@ The zfs send transferred all the data in the snapshot called backup1 to the pool named backup. Creating - and sending these snapshots could be done automatically by a - cron job. + and sending these snapshots could be done automatically with a + &man.cron.8; job. =20 + Instead of storing the backups as archive files, + ZFS can receive them as a live file system, + allowing the backed up data to be accessed directly. + To get to the actual data contained in those streams, the + reverse operation of zfs send must be used + to transform the streams back into files and directories. The + command is zfs receive. The example below + combines zfs send and + zfs receive using a pipe to copy the data + from one pool to another. This way, the data can be used + directly on the receiving pool after the transfer is complete. + A dataset can only be replicated to an empty dataset. + + &prompt.root; zfs snapshot mypool@replica1 +&prompt.root; zfs send -v mypool@replica1 | zfs receive backup/mypool= +send from @ to mypool@replica1 estimated size is 50.1M +total estimated size is 50.1M +TIME SENT SNAPSHOT + +&prompt.root; zpool list +NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT +backup 960M 63.7M 896M 6% 1.00x ONLINE - +mypool 984M 43.7M 940M 4% 1.00x ONLINE - + ZFS Incremental Backups =20 @@ -1652,8 +1691,8 @@ When a new block is a duplicate of an existing block, ZFS writes an additional reference to the existing data instead of the whole duplicate block. - Tremendous space savings are possible if the data contains many - duplicated files or repeated information. Be warned: + Tremendous space savings are possible if the data contains + many duplicated files or repeated information. Be warned: deduplication requires an extremely large amount of memory, and most of the space savings can be had without the extra cost by enabling compression instead. @@ -1761,15 +1800,16 @@ Delegated Administration =20 A comprehensive permission delegation system allows - unprivileged users to perform ZFS administration functions. For - example, if each user's home directory is a dataset, users can - be given permission to create and destroy snapshots of their - home directories. A backup user can be given permission to use - ZFS replication features. A usage statistics script can be - allowed to run with access only to the space utilization data - for all users. It is even possible to delegate the ability to - delegate permissions. Permission delegation is possible for - each subcommand and most ZFS properties. + unprivileged users to perform ZFS + administration functions. For example, if each user's home + directory is a dataset, users can be given permission to create + and destroy snapshots of their home directories. A backup user + can be given permission to use ZFS + replication features. A usage statistics script can be allowed + to run with access only to the space utilization data for all + users. It is even possible to delegate the ability to delegate + permissions. Permission delegation is possible for each + subcommand and most ZFS properties. =20 Delegating Dataset Creation @@ -2115,8 +2155,8 @@ Log - ZFS - Log Devices, also known as ZFS Intent Log - (ZFS + Intent Log (ZIL) move the intent log from the regular pool devices to a dedicated device, typically an --------------030702080803050203020007-- --3BGSrEJJNaJ6iO012Bk8AIIhrDki9cNVw Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJS+BzXAAoJEJrBFpNRJZKfmlsP/ArJgK1smp3Ysa/n7us6J6SS O9w2fEmmo4XUzsGWzawXXuc6KoGr/e6n3NXO3dBhvPBQfZWSdc3jYGJSxsbMuql8 PHlqDEzhllhtC3UYJDKrXZADIKnkw/5tX3l0WHk+4F5oWMxfJDplgYwVP+QGYEV5 Z5ExO0eiIwc8B0qMyWoRpHKdouAaR1fDB8ShW2tBDeqp0GiNBaoW4rZJ7IZP5lRK r1CoHnnQIfWc3DNVKE8iRdHqYHy2eJ2DGtc637UYyJ2yTY+eP5OQbNwgFhM2GYI9 m39r8WFNJGeIGUIN9b+CCtMGyALfMoEhF+E1LkX/ys0COLkDMwjc0J6Eg+6Q4Pu0 ZYlTjWmgfwci6Eyowdh61Vm9Bgnz13hLuV55Wqlrq8FPv588uaYqRkf0DFj83Das sDUBCeS2oy3CcXDoFVWxFHNe5/ehSlhBDyHMt72ZClS2+N1p4os3Z7QfLu/XA42Y xmejOMbiGoQ6keM1GrOkoSC4WEL2CLATKUGfdmPESjkFPSBixG8NesWt6Czr13/n gjUojm67YlAoosyb4hFw26G+g2GfEvwnvyMrBHBQkO6DkOn+2FZYUpoOVoTS0FcQ 0Lv6Oy0tgB0Pob6664UuXHgK4jaG5sdnOJhNXlp5O2SlhAj1XG49ZTmp89V2GgTP w98hzTYmYtCNeuqK4HNT =tlaW -----END PGP SIGNATURE----- --3BGSrEJJNaJ6iO012Bk8AIIhrDki9cNVw-- From owner-freebsd-doc@FreeBSD.ORG Mon Feb 10 00:49:24 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A60A05B0 for ; Mon, 10 Feb 2014 00:49:24 +0000 (UTC) Received: from omr-d06.mx.aol.com (omr-d06.mx.aol.com [205.188.109.203]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 61B2718B6 for ; Mon, 10 Feb 2014 00:49:24 +0000 (UTC) Received: from mtaomg-maa01.mx.aol.com (mtaomg-maa01.mx.aol.com [172.26.222.143]) by omr-d06.mx.aol.com (Outbound Mail Relay) with ESMTP id 937077000411F for ; Sun, 9 Feb 2014 19:49:17 -0500 (EST) Received: from core-mma002a.r1000.mail.aol.com (core-mma002.r1000.mail.aol.com [172.29.191.133]) by mtaomg-maa01.mx.aol.com (OMAG/Core Interface) with ESMTP id 454A138000081 for ; Sun, 9 Feb 2014 19:49:17 -0500 (EST) To: freebsd-doc@FreeBSD.org Subject: Possible typo on doc/handbook/ports-using.html ? X-MB-Message-Source: WebUI X-MB-Message-Type: User MIME-Version: 1.0 From: Lampros Chaidas X-Mailer: AOL Webmail 38366-STANDARD Received: from 54.240.196.169 by webmail-d224.sysops.aol.com (149.174.160.234) with HTTP (WebMailUI); Sun, 09 Feb 2014 19:49:16 -0500 Message-Id: <8D0F4110F6167E7-2378-15694@webmail-d224.sysops.aol.com> X-Originating-IP: [54.240.196.169] Date: Sun, 9 Feb 2014 19:49:17 -0500 (EST) x-aol-global-disposition: G DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mx.aol.com; s=20121107; t=1391993357; bh=G2tSTsFkW+Qm9GvROYFPH1j4N315MaLiUGM2HO/8R0s=; h=From:To:Subject:Message-Id:Date:MIME-Version:Content-Type; b=pAk0sP33FpRjZqrsb33JEGhUiCmk76itka823P5nx+6zsLUvylGcarDPsro+ytMhn OcMliIQfz/4gBMaivUpGPMdhTizpUAAKity1VeQrj7vesyGd4Ok+SAIgcXwFc8wcyi 4IR/ivYN5An6pnNrB3irTugiTKn2Ks0tA+MINTWY= x-aol-sid: 3039ac1ade8f52f8220d2dce Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 00:49:24 -0000 Hi there, I was just reading through the documentation for getting the ports collecti= on with the subversion method and noticed the following in "Procedure 5.2. = Subversion Method" - the link is http://www.freebsd.org/doc/handbook/ports-= using.html "If the ports tree is not available,=09 Subversion can be installed as=09 = a package: # pkg install subversion If pkgng is being used to=09 manage packages, Subversion can=09 be instal= led with it instead: # pkg install subversion" It looks like it's the same command in both situations - this looks redunda= nt to me, is there a difference here that maybe I'm missing?=20 Thanks, - Lampros From owner-freebsd-doc@FreeBSD.ORG Mon Feb 10 01:03:12 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3C84C9A0 for ; Mon, 10 Feb 2014 01:03:12 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C5F8719D8 for ; Mon, 10 Feb 2014 01:03:11 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.8/8.14.8) with ESMTP id s1A137Uh001542 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 9 Feb 2014 18:03:07 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.8/8.14.8/Submit) with ESMTP id s1A136Mx001539; Sun, 9 Feb 2014 18:03:07 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 9 Feb 2014 18:03:06 -0700 (MST) From: Warren Block To: Allan Jude Subject: Re: ZFS project branch update In-Reply-To: <52F81CD7.1050008@allanjude.com> Message-ID: References: <52F81CD7.1050008@allanjude.com> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 09 Feb 2014 18:03:07 -0700 (MST) Cc: freebsd-doc@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 01:03:12 -0000 On Sun, 9 Feb 2014, Allan Jude wrote: > Attached find a giant white space patch, fixes every igor warning, and > updates a lot of markup (acronym, application, using option instead of > literal) etc. Committed with a note about how it is not necessary to separate whitespace and content patches on this chapter yet. From owner-freebsd-doc@FreeBSD.ORG Mon Feb 10 01:40:00 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9B28A1A3 for ; Mon, 10 Feb 2014 01:40:00 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7476F1BF3 for ; Mon, 10 Feb 2014 01:40:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1A1e05F085410 for ; Mon, 10 Feb 2014 01:40:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1A1e0XM085409; Mon, 10 Feb 2014 01:40:00 GMT (envelope-from gnats) Resent-Date: Mon, 10 Feb 2014 01:40:00 GMT Resent-Message-Id: <201402100140.s1A1e0XM085409@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Allan Jude Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ED47FB7 for ; Mon, 10 Feb 2014 01:37:59 +0000 (UTC) Received: from newred.freebsd.org (cgiserv.freebsd.org [IPv6:2001:1900:2254:206a::50:4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D75C21BE2 for ; Mon, 10 Feb 2014 01:37:59 +0000 (UTC) Received: from cgiserv.freebsd.org ([127.0.1.6]) by newred.freebsd.org (8.14.7/8.14.7) with ESMTP id s1A1bx4D044536 for ; Mon, 10 Feb 2014 01:37:59 GMT (envelope-from nobody@cgiserv.freebsd.org) Received: (from nobody@localhost) by cgiserv.freebsd.org (8.14.7/8.14.7/Submit) id s1A1bxDX044535; Mon, 10 Feb 2014 01:37:59 GMT (envelope-from nobody) Message-Id: <201402100137.s1A1bxDX044535@cgiserv.freebsd.org> Date: Mon, 10 Feb 2014 01:37:59 GMT From: Allan Jude To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: docs/186614: Update htdocs/features.html to include 10.x X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 01:40:00 -0000 >Number: 186614 >Category: docs >Synopsis: Update htdocs/features.html to include 10.x >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Feb 10 01:40:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Allan Jude >Release: 9.2-RELEASE >Organization: ScaleEngine Inc. >Environment: FreeBSD Trooper.HML3.ScaleEngine.net 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013 root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Reported by: mwlucas@michaelwlucas.com http://www.freebsd.org/features.html doesn't mention 10.0 I also added a section for features that are not specific to any particular version of FreeBSD, and merged the important 8.x bits into that. >How-To-Repeat: >Fix: Patch attached with submission follows: Index: features.xml =================================================================== --- features.xml (revision 43851) +++ features.xml (working copy) @@ -36,11 +36,69 @@ diverse and world-wide membership of the volunteer &os; Project.

-

&os; 9.0, brings many new features +

&os; 10.X, introduced many new features + and replaces many legacy tools with updated ones.

+ +
    +
  • bhyve: + A new BSD licensed, legacy-free hypervisor has been imported + to the &os; base system. It is currently able to run all + supported versions of &os;, and with the help of the + grub-bhyve port, OpenBSD and Linux.
    • + +
  • KMS And New drm2 Video Drivers: + The new drm2 driver provides support for AMD GPUs up-to the + Radeon HD 6000 series and provides partially support for + the Radeon HD 7000 family. &os; now also supports + Kernel-Mode-Setting for AMD and Intel GPUs.
    • + +
  • Capsicum Enabled By Default: + Capsicum has been enabled in the kernel by default, allowing + sandboxing of several programs that work within the + "capabilities mode", such as: +
      +
    • tcpdump
      • +
    • dhclient
      • +
    • hast
      • +
    • rwhod
      • +
    • kdump
      • +
    +
    • + +
  • New Binary Packaging System: + &os; now uses pkg, a vastly improved package management + system that supports multiple repositories, signed packages, + and safe upgrades. The improved system is combined with + more frequent official package builds for all supported + platforms and a new stable branch of the ports tree for + better long term support.
    • + +
  • Unmapped I/O: + The newly implemented concept of unmapped VMIO buffers + eliminates the need to perform costly TLB shootdowns for + buffer creation and reuse, reducing system CPU time by + up to 25-30% on big-SMP machines under heavy I/O load.
    • + +
+ +

&os; 9.X, brought many new features and performance enhancements with a special focus on desktop support and security features.

    +
  • OpenZFS: + &os; 9.2 includes OpenZFS v5000 (Feature Flags), including + the feature flags: +
      +
    • async_destroy
      • +
    • empty_bpobj
      • +
    • lz4_compress
      • +
    + which allow ZFS destroy operations to happen in the + background, make snapshots consume less disk space, and + offers a better compression algorithm for compressed + datasets.
    • +
  • Capsicum Capability Mode: Capsicum is a set of features for sandboxing support, using a capability model in which the capabilities are file @@ -102,32 +160,39 @@ for background fsck(8) even on unclean shutdowns.
-

&os; 8.X brought many new - features and performance enhancements. With special focus on - a new USB stack, &os; 8.X also shipped with experimental support - for NFSv4. A new TTY layer was introduced, which improves - scalability and resources handling in SMP enabled systems.

+

&os; includes a number of other great features:

    -
  • Netisr framework: has been reimplemented for - parallel threading support. This is a kernel network - dispatch interface which allows device drivers (and other - packet sources) to direct packets to protocols for directly - dispatched or deferred processing. The new implementation - supports up to one netisr thread per CPU, and several - benchmarks on SMP machines show substantial performance - improvement over the previous version.
    • +
  • Firewalls: + the base system includes IPFW and IPFilter, as well as a + modified version of the popular pf with improved SMP + performance. IPFW also includes the dummynet feature, + allowing network administrators to simular adverse network + conditions, including latency, jitter, packet loss and + limited bandwidth.
    • -
  • Jail improvements: Jails now support multiple IPv4 - and IPv6 addresses per jail, and also support SCTP. - Hierarchies of jails (jails-within-jails) are now supported, - and jails can now be restricted to subsets of available - CPUs.
    • +
  • Jails: + are a light-weight alternative to virtualization. + Allowing processes to be restricted to a namespace with + access only to the file systems and network addresses + assigned to that namespace. Jails are also Hierarchical, + allowing jails-within-jails.
    • -
  • Linux emulation: layer has been updated to version - 2.6.16 and the default Linux infrastructure port is now - emulators/linux_base-f10 (Fedora 10).
    • +
  • Linux emulation: + provides a system call translation layer that allows + unmodified Linux binaries to be run on &os; systems.
    • +
  • DTrace: + provides a comprehensive framework for tracing and + troubleshooting kernel and application performance issues + while under live load.
    • + +
  • Ports: is a collection of more than 23,000 3rd + party applications that can be easily installed and run on + &os;. The ports architecture also allows for easy + customization of the compile time options of many of the + applications.
    • +
  • Network Virtualization: A container ("vimage") has been implemented, extending the &os; kernel to maintain multiple independent instances of networking state. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Mon Feb 10 11:06:04 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9C13DE58 for ; Mon, 10 Feb 2014 11:06:04 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7A33B1E52 for ; Mon, 10 Feb 2014 11:06:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1AB64Ju079165 for ; Mon, 10 Feb 2014 11:06:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1AB64YM079163 for freebsd-doc@FreeBSD.org; Mon, 10 Feb 2014 11:06:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 10 Feb 2014 11:06:04 GMT Message-Id: <201402101106.s1AB64YM079163@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: FreeBSD doc list Subject: Current unassigned doc problem reports X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 11:06:04 -0000 (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o docs/186614 doc Update htdocs/features.html to include 10.x o docs/186608 doc typo in 'ctime(3) man page o docs/186537 doc [patch] removing obsolete vnode (9) man page reference o docs/186464 doc Online-Documentation for carp(4) is outdated p docs/186191 doc Typo in bhyveload.8 o docs/185764 doc mention of libiconv in FreeBSD 10.0 release note o docs/185531 doc etherswitchcfg(8) refers to etherswitch(4) which does o docs/185481 doc sh/bash Parameter Expansion +/- syntax not documented o docs/185422 doc [handbook] brazilian portuguese translation to "Append o docs/185421 doc [handbook] brazilian portuguese translation to "Append o docs/185392 doc [handbook] brazilian portuguese translation to "The Fr o docs/185391 doc [handbook] brazilian portuguese translation to "GEOM: o docs/185353 docs nc(1) does not exit after transfer (should be document o docs/185281 doc [handbook] brazilian portuguese translation to "Jails" o docs/185280 doc [handbook] brazilian portuguese translation to "Introd o docs/184758 doc error in rtadvd.conf example o docs/184755 doc The vmstat(8) manualpage synopsis doesn't show all opt o docs/184482 doc passwd (1) man page incorrect info about login.conf o docs/184459 doc Documentation Bug in the man Page for the who Command o docs/184110 doc blackhole(4) manpage doesn`t describe net.inet.sctp.b o docs/184051 doc Update configuration example for staging o docs/184048 doc developers handbook, 10.7 Debugging Deadlocks - must i o docs/184046 doc bhyve(4) manpage references non-existant manpages bhyv o docs/184029 doc Description of /usr/tests is missing in hier(7) o docs/183927 doc missing info about kernel toolchain in kernel building o docs/183653 doc [patch] Add some more *BSD releases to the groff_mdoc o docs/183427 doc Online man pages don't include latest release + ports o docs/183333 doc Misnamed constant in bpf(4) o docs/183246 doc FreeBSD 8.4-RELEASE Installation Instructions don't pr o docs/183024 doc textdump(4) mentions call doadump, should be textdump o docs/183002 doc Fix instructions in "6.5.3. Anti-Aliased Fonts" regard o docs/182876 doc CURRENT release notes webpage out of date and inconsis o docs/182218 doc Add an ipfilter rc.conf option in handbook for IPv6 o docs/182202 doc Handbook pkgng description doesn't mention there are n o docs/181845 doc Virtualbox Host Setup needs acd0 in /etc/devfs.conf, a o docs/181844 doc FreeBSD Handbook Virtualbox Host Section missing confi o docs/181808 doc Chapter 15.15 (Resource Limits) misses important infor o docs/181785 doc [patch] Man page for tmpfile() is inconsistent o docs/181390 doc seq(1) first appeared in 8th UNIX o docs/181376 doc CLOCK_THREAD_CPUTIME_ID is not documented in clock_get o docs/181280 doc suggestion: split zfs man page in a zfs- way o docs/181134 doc Fix example for boot0cfg utility o docs/180970 doc [request] No manpage for ps_strings o docs/180767 doc [patch] printf.3: fix off-by-one in snprintf descripti o docs/180493 doc [handbook] Single-user mode console confusion o docs/180332 doc SSD Kernel Instructions Out of Date: options MFS throw o docs/180331 doc SSD Kernel Instructions Out of Date: options MD_ROOT a o docs/180330 doc SSD Kernel Instructions Out of Date: pseudo-device no o docs/180027 doc Missing man page entries for callout_reset_sbt in time o docs/179988 doc [faq] [patch] ThwackAFAQ - sandbox p docs/179914 doc remove inactive user dougb from mergemaster maintainer o docs/179697 doc Handbook incomplete WRT Opera flash usage (linproc) o docs/179497 doc [patch] service.8 add csh completion example o docs/179246 doc [patch] gnome porting updates o docs/178818 doc gmirror(8) says to use rc.early which is no longer ava o docs/178730 doc move roff papers out of src into doc o docs/178286 doc [PATCH] document the LOCAL_* vars in build(7) o docs/178221 doc Addition to handbook jails chapter: warning about make o www/178190 doc myths web page should be updated o docs/178119 doc [ports] Porter's handbook lacks examples for using Opt o docs/177968 doc bpf(4): documentation of BIOCROTZBUF is incomplete o docs/177699 doc Documentation (handbook and manpage) for mac_biba does o docs/177514 doc [handbook] ZFS examples do not cover dataset creation o docs/177457 doc diskinfo(8): diskinfo -v shows inacurate drive size o docs/177431 doc Handbook & Announcements recommend poor dd options for o docs/177429 doc dd(1) man page is unclear about semantics of conv=sync o docs/177215 doc [handbook] [patch] FreeBSD uses SHA512 and no more MD5 o docs/176806 doc recv(2) man page grammatical fixes o docs/176648 doc restore(8) man page is misleading/confusing o docs/176645 doc The example in netmap.4 is wrong o docs/176363 doc Remove mention of 'CVSup' from "Mirroring FreeBSD arti o docs/176355 doc Attribution and correction of quote in fortune o docs/176251 doc FreeBSD Handbook assumes too much pre-knowledge o docs/176127 doc [handbook] add information about all missing mailing l o docs/176125 doc missing summary of freebsd-jail mailing list o docs/176123 doc missing summary of freebsd-sysinstall mailing list o docs/176015 doc [handbook] wrong order in docs for major upgrade o docs/175995 doc Setting MALLOC_PRODUCTION stops buildworld o docs/175983 doc man zfs are missing "hold, release" from "zfs allow" o docs/175712 doc Update 'disk naming' handbook page o docs/175687 doc pthread_setschedparam(3) may fail for undocumented rea o docs/175560 doc ugen(4) man page contains incorrect device node path o docs/175239 doc sem_wait can be interrupted o docs/175123 doc [geom] gpart list/status isn't documented in usage sec o docs/174868 doc mount(2) doesn't do a good job at describing all possi o docs/174792 doc synopsis for nsupdate(1) missing options -L, and -p o docs/174581 doc man page of recvmsg(2) does not mention return value 0 o docs/173710 doc Added section "MTP storage" to handbook o docs/173539 doc [patch] statfs(2) man page missed the error code ENOSY o docs/173321 doc ports(7) man page -- no info on building with debuggin o docs/173013 doc FreeBSD Boot Menu documentation lacks detail o docs/172927 doc ipfw(8): ipfw manual page doesn't show simpliest NAT c o docs/172913 doc [ipsec] [patch] setkey(8) is unclear on anti-replay wi o docs/172869 doc [PATCH] Add in nifty lang icons to index.html (home) o docs/172743 doc IPv6 handbooks lacks info about accepting router adver o docs/172626 doc [PATCH] modify the community/* pages to look more plea o docs/172370 doc [handbook] Handbook should be updated for Blu-Ray driv o docs/172369 doc mkisofs(8)/growisofs(1m) don't specify UDF version o docs/172368 doc mount_udf(8) doesn't specify which versions of UDF are o docs/172367 doc ata(4) man page needs an updated for Blu-Ray o docs/172330 doc [PATCH] Fix some errors introduced to announce.xml by o docs/172144 doc psignal(9) manpage is outdated for FreeBSD-9 systems o docs/172137 doc deprecated information for adduser(8) man pages o docs/171199 doc the GDB man page is outdated o docs/170691 doc Difference between zfs manpages and reality o docs/170119 doc at behaviour and man at inconsistency o docs/169712 doc [patch] porters-handbook zh_TW.Big5 apache section o docs/169711 doc [patch] porters-handbook zh_CN.GB2312 apache section o docs/169544 doc serial port console documentation changes s docs/169401 doc passify dead links in release links, move www to lists o docs/169377 doc [patch] ipmon(8) man page refers to a different facili o docs/169317 doc zfs umount refers to umount(1M) but should to umount(8 o docs/169158 doc [patch] iasl(8) man page is out of date f docs/168939 doc Port upgrade documentation missing from Application Ja o docs/168930 doc map_mincore(9) not up-to-date o docs/168915 doc size of integers used by test(1) and sh(1) is not docu o docs/168823 doc 404s in fr_FR French web pages o docs/168814 doc [patch] remove `d` negative pointer EINVAL requirement o docs/168803 doc Remove outdated smp info o docs/167429 doc geli(8) needs to mention unencrypted /etc/fstab requir o docs/166553 doc find(1): find -delete documentation is misleading o docs/166358 doc No networking in Jail build via: handbook/jail-tuning o conf/166330 doc [rc] [patch] Thin server configuration revision reques o docs/165551 doc ipfw(8): no info in "ipfw pipe show" about ipv6 o docs/165249 doc Multibyte characters in manpages still not displaying o docs/164803 doc Unclear manual page for mount_unionfs(8) o docs/164099 doc gparm(8): man page for gparm set is incorrect and inco o docs/164034 doc acl(9) documentation lacking o docs/163879 doc [handbook] handbook does not say about how to force to o docs/163830 doc device smbios: missing documentation, no manpage o docs/163149 doc [patch] Red Hat Linux/i386 9 HTML format sudo man page o docs/162765 doc [patch] lseek(2) may return successful although no see o docs/162587 doc unclear/incomplete description of per-interface statis o docs/162419 doc [request] please document (new) zfs and zpool cmdline o docs/162404 doc [handbook] IPv6 link-local address compared with IPv4 o docs/161754 doc p4tcc(4), est(4) and qpi(4) are not documented o docs/161496 doc zfs(1): Please document that sysctl vfs.usermount must o docs/160460 doc [handbook] Network setup guide suggestion o docs/160399 doc Man page for re(4) missing jumbo frames info o docs/159307 doc [patch] lpd smm chapter unconditionally installed o docs/158388 doc Incorrect documentation of LOCAL_SCRIPT in release(7) o docs/158387 doc The tree(3) man should mention the RB_FOREACH_SAFE() A o docs/157908 doc [handbook] Description of post-install should include o docs/157698 doc [patch] gpart(8) man page contains old/incorrect size o docs/157316 doc [patch] update devstat(9) man page o docs/156920 doc isspecial(3) is not helpful o docs/156815 doc chmod(1): manpage should describe that chmod kicks +t o docs/156689 doc stf(4) output-only documentation gives bad configurati f docs/156187 doc [handbook] [patch] Add bsnmpd to handbook o docs/156081 doc troff falls with troff.core with UTF-8 man with incorr o docs/155982 doc [handbook] reaper of the dead: remove reference to flo o docs/155149 doc [patch] don't encourage using xorg.conf outside of PRE o docs/154838 doc update cvs-tags information on releng_* to reflect sup o docs/153958 doc ksu man-page documented, but not installed a docs/153012 doc [patch] iostat(8) requires an argument to -c option o docs/151752 doc pw.conf(5) doesn't define format for file clearly o docs/150991 doc [patch] Install upgtfw using pkg_add as advised in upg o docs/150917 doc [patch] icmp.4, wrong description of icmplim and icmpl o docs/150255 doc dtrace description should mention makeoptions DEBUG=-g o docs/149574 doc [patch] update mi_switch(9) man page o docs/148987 doc [patch] {MD[245]|SHA_|SHA1_|SHA256_}{End|File|FileChun o docs/148984 doc [handbook] Mistake in section 16.15.4 of the handbook o docs/148680 doc [sysctl][patch] Document some sys/kern sysctls o docs/148071 doc Failover mode between wired and wireless interfaces o docs/147995 doc elf.5 man page has has missing reference o docs/146521 doc [handbook] Update IPv6 system handbook section to ment o docs/145699 doc hexdump(1) mutes all format qualifier output following o docs/145069 doc Dialup firewalling with FreeBSD article out dated. o docs/145066 doc Update for new uart dev names for serial port. s docs/144818 doc all mailinglist archives dated 19970101 contain traili o docs/143472 doc gethostname(3) references undefined value: HOST_NAME_M o docs/143416 doc [handbook] IPFW handbook page issues o docs/143408 doc man filedesc(9) is missing o docs/141032 doc misleading documentation for rtadvd.conf(5) raflags se s docs/140847 doc [request] add documentation on ECMP and new route args o docs/140444 doc [patch] New Traditional Chinese translation of custom- o docs/140375 doc [UPDATE] Updated zh_TW.Big5/articles/nanobsd o docs/139336 doc [request] ZFS documentation suggestion o docs/139165 doc gssapi.3 man page out of sync with between crypto and o docs/139018 doc translation of submitting.sgml from docproj/submitting o docs/138485 doc bpf(4) and ip(4) man pages missing important corner ca o docs/136712 doc [handbook] [patch] draft new section on gmirror per pa o docs/136666 doc [handbook] Configure serial port for remote kernel deb o docs/136035 doc ftpchroot(5) omits an important option o docs/132839 doc [patch] Fix example script in ldap-auth article o docs/132190 doc EPERM explanation for send(2), sendto(2), and sendmsg( o docs/131918 doc [patch] Fixes for the BPF(4) man page o docs/131626 doc [patch] dump(8) "recommended" cache option confusing o docs/130238 doc nfs.lockd man page doesn't mention NFSLOCKD option or o docs/129671 doc New TCP chapter for Developer's Handbook (from rwatson o docs/129464 doc using packages system o docs/129095 doc ipfw(8): Can not check that packet originating/destine o docs/128356 doc [request] add Firefox plugin for FreeBSD manual pages s docs/127844 doc Example code skeleton_capture_n.c in meteor(4) manpage o docs/126484 doc libc function res-zonscut2 is not documented f docs/122052 doc minor update on handbook section 20.7.1 o docs/121952 doc Handbook chapter on Network Address Translation wrong o docs/121585 doc [handbook] Wrong multicast specification s docs/121541 doc [request] no man pages for wlan_scan_ap o docs/121312 doc RELNOTES_LANG breaks release if not en_US.ISO8859-1 o docs/121173 doc [patch] mq_getattr(2): mq_flags mistakenly described a s docs/120917 doc [request]: Man pages mising for thr_xxx syscalls o docs/120125 doc [patch] Installing FreeBSD 7.0 via serial console and o docs/120024 doc resolver(5) and hosts(5) need updated for IPv6 o docs/119545 doc books/arch-handbook/usb/chapter.sgml formatting o docs/118214 doc close(2) error returns incomplete o docs/116588 doc No IPFW tables or dummynet in Handbook o docs/114371 doc [patch] [ip6] rtadvd.con(5) should show how to adverti o docs/114139 doc mbuf(9) has misleading comments on M_DONTWAIT and M_TR o docs/113194 doc [patch] [request] crontab.5: handling of day-in-month o docs/112579 doc [request] No ipv6 related pf examples in /usr/share/ex o docs/111425 doc Missing chunks of text in historical manpages o docs/111265 doc [request] Clarify how to set common shell variables o docs/110999 doc carp(4) should document unsupported interface types o docs/110692 doc wi(4) man page doesn't say WPA is not supported o docs/110376 doc [patch] add some more explanations for the iwi/ipw fir o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu f docs/109226 doc [request] No manual entry for sntp o docs/109201 doc [request]: manual for callbootd a docs/108980 doc list of missing man pages o docs/105608 doc fdc(4) debugging description staled o docs/104879 doc Howto: Listen to IMA ADPCM .wav files on FreeBSD box o docs/102719 doc [patch] ng_bpf(4) example leads to unneeded promiscuos o docs/101271 doc serial console documentation implies kernel rebuild re p docs/100196 doc man login.conf does explain not "unlimited" o docs/98974 doc Missing tunables in loader(8) manpage o docs/96207 doc Comments of a sockaddr_un structure could confuse one o docs/95408 doc install over serial console does not work as documente o docs/94625 doc [patch] growfs man page -- document "panic: not enough o docs/92626 doc jail manpage should mention disabling some periodic sc o docs/91149 doc read(2) can return EINVAL for unaligned access to bloc o docs/88512 doc [patch] mount_ext2fs(8) man page has no details on lar o docs/87936 doc Handbook chapter on NIS/YP lacks good information on a o docs/87857 doc ifconfig(8) wireless options order matters o docs/85128 doc [patch] loader.conf(5) autoboot_delay incompletly desc o docs/84956 doc [patch] intro(5) manpage doesn't mention API coverage o docs/84932 doc new document: printing with an Epson ALC-3000N on Free o docs/84670 doc [patch] tput(1) manpage missing ENVIRONMENT section wi o docs/84317 doc fdp-primer doesn't show class=USERNAME distinctively o docs/84271 doc [patch] compress(1) doesn't warn about nasty link hand o docs/83820 doc getino(3) manpage not installed o docs/81611 doc [patch] natd runs with -same_ports by default o docs/78480 doc Networked printer setup unnecessarily complex in handb o docs/61301 doc [patch] Manpage patch for aue(4) to enable HomePNA fun o docs/59835 doc ipfw(8) man page does not warn about accepted but mean o docs/59477 doc Outdated Info Documents at http://docs.freebsd.org/inf o docs/57298 doc [patch] add using compact flash cards info to handbook s docs/54752 doc bus_dma explained in ISA section in Handbook: should b o docs/53751 doc bus_dma(9) incorrectly documents BUS_DMA_ALLOCNOW o docs/53596 doc Updates to mt(1) manual page o docs/53271 doc bus_dma(9) fails to document alignment restrictions o docs/51480 doc Multiple undefined references in the FreeBSD manual pa o kern/51341 doc [ipfw] [patch] ipfw rule 'deny icmp from any to any ic o docs/50211 doc [patch] doc.docbook.mk: fix textfile creation o docs/48101 doc [patch] Add documentation on the fixit disk o docs/47594 doc [patch] passwd(5) incorrectly states allowed username o docs/43823 doc [patch] update to environ(7) manpage o docs/41089 doc pax(1) -B option does not mention interaction with -z o docs/40423 doc Keyboard(4)'s definition of parameters to GETFKEY/SETF o docs/36724 doc ipnat(5) manpage grammar is incomplete and inconsisten o docs/26286 doc *printf(3) etc should gain format string warnings o docs/24786 doc missing FILES descriptions in sa(4) s docs/20028 doc ASCII docs should reflect tags in the sourc 264 problems total. From owner-freebsd-doc@FreeBSD.ORG Mon Feb 10 11:30:01 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 425EA21C for ; Mon, 10 Feb 2014 11:30:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 03521132B for ; Mon, 10 Feb 2014 11:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1ABU0CU089695 for ; Mon, 10 Feb 2014 11:30:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1ABU02m089692; Mon, 10 Feb 2014 11:30:00 GMT (envelope-from gnats) Resent-Date: Mon, 10 Feb 2014 11:30:00 GMT Resent-Message-Id: <201402101130.s1ABU02m089692@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Wout Decré Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C1557FFC for ; Mon, 10 Feb 2014 11:20:15 +0000 (UTC) Received: from newred.freebsd.org (cgiserv.freebsd.org [IPv6:2001:1900:2254:206a::50:4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AB50212D4 for ; Mon, 10 Feb 2014 11:20:15 +0000 (UTC) Received: from cgiserv.freebsd.org ([127.0.1.6]) by newred.freebsd.org (8.14.7/8.14.7) with ESMTP id s1ABKEYU052846 for ; Mon, 10 Feb 2014 11:20:14 GMT (envelope-from nobody@cgiserv.freebsd.org) Received: (from nobody@localhost) by cgiserv.freebsd.org (8.14.7/8.14.7/Submit) id s1ABKECO052831; Mon, 10 Feb 2014 11:20:14 GMT (envelope-from nobody) Message-Id: <201402101120.s1ABKECO052831@cgiserv.freebsd.org> Date: Mon, 10 Feb 2014 11:20:14 GMT From: Wout Decré To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: docs/186625: Handbook rebuilding "world" upgrade procedure wrong mergemaster command X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 11:30:01 -0000 >Number: 186625 >Category: docs >Synopsis: Handbook rebuilding "world" upgrade procedure wrong mergemaster command >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: doc-bug >Submitter-Id: current-users >Arrival-Date: Mon Feb 10 11:30:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Wout Decré >Release: >Organization: Canodus >Environment: >Description: Under Procedure 23.2. Overview of Build World Process, step 9: Update any remaining configuration files. # mergemaster -p It suggests you should do the mergemaster command two times with the -p option. Before r43796, this was: # mergemaster >How-To-Repeat: Check http://www.freebsd.org/doc/handbook/makeworld.html >Fix: I think this should just be: # mergemaster >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Mon Feb 10 16:26:51 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A1A6F712 for ; Mon, 10 Feb 2014 16:26:51 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 5F2861D02 for ; Mon, 10 Feb 2014 16:26:50 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.146.73]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 164895AAAE for ; Mon, 10 Feb 2014 16:26:49 +0000 (UTC) Message-ID: <52F8FDCA.2000406@allanjude.com> Date: Mon, 10 Feb 2014 11:26:50 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-doc@freebsd.org Subject: Re: docs/185353: nc(1) does not exit after transfer (should be documented) References: <201401060008.s0608LhQ075904@freefall.freebsd.org> In-Reply-To: <201401060008.s0608LhQ075904@freefall.freebsd.org> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="v6j3lOJNWFWDFpA1pCJHgEc9pRhUmr7e6" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 16:26:51 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --v6j3lOJNWFWDFpA1pCJHgEc9pRhUmr7e6 Content-Type: multipart/mixed; boundary="------------040601080200010508080706" This is a multi-part message in MIME format. --------------040601080200010508080706 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2014-01-05 19:08, linimon@FreeBSD.org wrote: > Old Synopsis: nc does not exit after transfer > New Synopsis: nc(1) does not exit after transfer (should be documented)= >=20 > Responsible-Changed-From-To: freebsd-amd64->freebsd-docs > Responsible-Changed-By: linimon > Responsible-Changed-When: Mon Jan 6 00:07:44 UTC 2014 > Responsible-Changed-Why:=20 > reclassify. >=20 > http://www.freebsd.org/cgi/query-pr.cgi?pr=3D185353 > _______________________________________________ > freebsd-doc@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-doc > To unsubscribe, send any mail to "freebsd-doc-unsubscribe@freebsd.org" >=20 I have sent in a patch upstream to resolve this issue. Once it is committed we can import the updated version of netcat and gain the documentation fix. It is a 1 line diff to the man page, so I've attached a diff against our tree as well, for reference. --=20 Allan Jude --------------040601080200010508080706 Content-Type: text/plain; charset=windows-1252; name="contrib_netcat.nc.1.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="contrib_netcat.nc.1.diff" Index: contrib/netcat/nc.1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- contrib/netcat/nc.1 (revision 261716) +++ contrib/netcat/nc.1 (working copy) @@ -365,7 +365,7 @@ .Nm process, feeding it the file which is to be transferred: .Pp -.Dl $ nc host.example.com 1234 \*(Lt filename.in +.Dl $ nc -N host.example.com 1234 \*(Lt filename.in .Pp After the file has been transferred, the connection will close automatic= ally. .Sh TALKING TO SERVERS --------------040601080200010508080706-- --v6j3lOJNWFWDFpA1pCJHgEc9pRhUmr7e6 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJS+P3KAAoJEJrBFpNRJZKfiz0QAJ8yd2KyAs+QGRvrn+8z4qIh FV82GqgyzAVEcgoiA7VnIJJC6L1yUOLttaJVvuCii2uYmkwzBF5Jdya+umvvB73w OX9A+4K5FGxf23QsQqKcU8Qf9QxO75VL8Z9ScHmNQUXuz4kutYeWvw79kNYy/Cbu CxBLtakF/5Xf3UXK/vOvNsMkz65qoX1MOHrUjnaKTanp4vbZygKyYtzbKqD9Go5z CDxUZN5oVAo3p1HvAY5TEkWMsJ8YGQlbJWvd6uac8q74UPMyO7kJBoscTr5gTutN sSfO9/cBosnrSwrh9sjXv/j5l9OdjxYnceGz+FMBeFh/53C1Ewt1Bxi3KgX0YnS2 hoPwZm4FoSo8DL+HgMe5trSP1SzkEBQIiXeuX1gQ6ChsvMC4a+VO/RBsm+4abwxX vk2GQYCWtV2FcaoELeUzFOgHVBDVy15hywvEZQLbuiaU876ENL0wiXsc5YnarNNS Foxy76O4CIzhLKyu4SlvFaGjQSim4paasiv/0JqqqasltenggdQiOPscvu0D1y8K MRxBiNbZArYuDG/1YtOu7YRZTRjkXVluBJLsfr4gSie/2SLPs7/G+BeCUTv2M+Zh YkiYZII+C+apJyfMXz8I3r7rtMeRDJqvcx3MUL2/aF/6zN0UTsudL2JJO9XGJem1 OdA5078zOFF/3SBrt9Kk =iEdv -----END PGP SIGNATURE----- --v6j3lOJNWFWDFpA1pCJHgEc9pRhUmr7e6-- From owner-freebsd-doc@FreeBSD.ORG Mon Feb 10 16:30:01 2014 Return-Path: Delivered-To: freebsd-docs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 756458D5 for ; Mon, 10 Feb 2014 16:30:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 527BE1D3D for ; Mon, 10 Feb 2014 16:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1AGU1YJ084981 for ; Mon, 10 Feb 2014 16:30:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1AGU1sW084980; Mon, 10 Feb 2014 16:30:01 GMT (envelope-from gnats) Date: Mon, 10 Feb 2014 16:30:01 GMT Message-Id: <201402101630.s1AGU1sW084980@freefall.freebsd.org> To: freebsd-docs@FreeBSD.org From: Allan Jude Subject: Re: docs/185353: nc(1) does not exit after transfer (should be documented) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Allan Jude List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 16:30:01 -0000 The following reply was made to PR docs/185353; it has been noted by GNATS. From: Allan Jude To: bug-followup@FreeBSD.org, rol@robert-eckardt.de Cc: Subject: Re: docs/185353: nc(1) does not exit after transfer (should be documented) Date: Mon, 10 Feb 2014 11:28:30 -0500 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --XT7BEsPaqPf8iu4tkvRjj0IVfVVkg2Kte Content-Type: multipart/mixed; boundary="------------010906050000010700040805" This is a multi-part message in MIME format. --------------010906050000010700040805 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable I have sent in a patch upstream to resolve this issue. Once it is committed we can import the updated version of netcat and gain the documentation fix. It is a 1 line diff to the man page, so I've attached a diff against our tree as well, for reference. --=20 Allan Jude --------------010906050000010700040805 Content-Type: text/plain; charset=windows-1252; name="contrib_netcat.nc.1.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="contrib_netcat.nc.1.diff" Index: contrib/netcat/nc.1 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- contrib/netcat/nc.1 (revision 261716) +++ contrib/netcat/nc.1 (working copy) @@ -365,7 +365,7 @@ .Nm process, feeding it the file which is to be transferred: .Pp -.Dl $ nc host.example.com 1234 \*(Lt filename.in +.Dl $ nc -N host.example.com 1234 \*(Lt filename.in .Pp After the file has been transferred, the connection will close automatic= ally. .Sh TALKING TO SERVERS --------------010906050000010700040805-- --XT7BEsPaqPf8iu4tkvRjj0IVfVVkg2Kte Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJS+P4uAAoJEJrBFpNRJZKfxmIP/3OozGxuoBulAb7w4lkyyUy9 w+mjCk3prdvZ5ofAdx/UYVuHiw8NMj9MAY2FlAY4OXn+rZO/E0UQTcBy8j5oCSjP Ccc0sdt9jfp4itLOyzC8Kc0uU/eKM1FOFJSh5gv8uTAu8aZJ7Ep93R79k90BIHAQ j9XbBByEsapARfMWUb1GLtpAkbTPtkUHhsxzzWpm7B8Asu2E3Y7+bGz6cYDavRHO iB84kwhnEdAyJfImDbHYjq4+uL1vCwPo+yNFSf2x9oROFGiGOqxdjxQYkmis0yBE UR3CnBLSz6CfInMaCUKS1dW6LkioOU0TMVJSUnZxXBiYu3AvNYWmk6UReN88PSCa 8zlyGJ6mOELI4HnjcSMcJMzg8cjK+QUU6k/hVbphB7Lk3YkrHU4akW99ma2xVPjd 6q3xjxIDBX/Hmfh8dRzR4otX/3jWZv6DewfyHz26oPeuCje5eHgLVci0EkXrL/A6 NOK98HVLwVbXL9XDT2tbbfHJ+a4vQYLIN11BZRvnm6vn8anfWhNnmvCCjNKWwlS5 UlCjHs0h6/aOc5Zd8U3h9RJjciCc2zIpHfq7dT8x0efmGyQbcEMCSJ7sIlC+0E8I Yw75rTZWo0zOmpn/yEICcZw2NR3g3Gi9q/S7QGg3S6mOXno8e/paoiyennmhNHsq OaVJB1WZUnrMD4wjfcVj =Ecvw -----END PGP SIGNATURE----- --XT7BEsPaqPf8iu4tkvRjj0IVfVVkg2Kte-- From owner-freebsd-doc@FreeBSD.ORG Mon Feb 10 19:59:30 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5091132F; Mon, 10 Feb 2014 19:59:30 +0000 (UTC) Received: from dmz-mailsec-scanner-1.mit.edu (dmz-mailsec-scanner-1.mit.edu [18.9.25.12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id B5CF41278; Mon, 10 Feb 2014 19:59:29 +0000 (UTC) X-AuditID: 1209190c-f794a6d000000c27-c6-52f92e6d8908 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-1.mit.edu (Symantec Messaging Gateway) with SMTP id 5E.F7.03111.D6E29F25; Mon, 10 Feb 2014 14:54:21 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id s1AJsJuG030251; Mon, 10 Feb 2014 14:54:20 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id s1AJsGA1024172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 10 Feb 2014 14:54:18 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id s1AJsGOZ005546; Mon, 10 Feb 2014 14:54:16 -0500 (EST) Date: Mon, 10 Feb 2014 14:54:16 -0500 (EST) From: Benjamin Kaduk X-X-Sender: kaduk@multics.mit.edu To: Jamie Landeg-Jones Subject: Re: docs/186608: typo in 'ctime(3) man page In-Reply-To: <201402090702.s1972G1s067725@catnip.dyslexicfish.net> Message-ID: References: <201402090702.s1972G1s067725@catnip.dyslexicfish.net> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJIsWRmVeSWpSXmKPExsUixG6nrpur9zPIYMVpSYtTZ7pYLVqerGa3 eHm7kcmB2eN490JWjxmf5rMEMEVx2aSk5mSWpRbp2yVwZSw5fYa14DBnxfwLvewNjJvZuxg5 OCQETCQWXlPuYuQEMsUkLtxbzwZiCwnMZpLY38YEUiIksJFR4oEfRPgQk8TfG0ldjFxAdgOj RPfTF2A1LALaEmfOGIPUsAmoSTze28wKMVJRYvOpScwgtoiAvsSBhxvAxjML2Eosvv0YzBYG uqB5/VFGEJtTwEniwPlLYPW8Ag4SHz81sELsdZQ4eaERrF5UQEdi9f4pLBA1ghInZz5hgZhp KXHuz3W2CYxCs5CkZiFJLWBkWsUom5JbpZubmJlTnJqsW5ycmJeXWqRrqJebWaKXmlK6iREU wpySPDsY3xxUOsQowMGoxMN74dOPICHWxLLiytxDjJIcTEqivAVaP4OE+JLyUyozEosz4otK c1KLDzFKcDArifDuVgLK8aYkVlalFuXDpKQ5WJTEeRNnvAkSEkhPLEnNTk0tSC2CycpwcChJ 8HrqAjUKFqWmp1akZeaUIKSZODhBhvMADfcDqeEtLkjMLc5Mh8ifYlSUEud9owOUEABJZJTm wfXCUswrRnGgV4R5o0HaeYDpCa77FdBgJqDBR5t+gAwuSURISTUwppc7Tmfk3b/AbZaK/ZWG 6weYl1Xk/MoyYbGJmJ+cNv1Q1qPiouwVfyKKqjo2RfxRY0i0er3N5j5XRFNKzbJtch0L9R7q /Ah5wb1HseTjapH9JbutFaeX/G4pjJ3R/Tps+cTK986tBVnLFZweWZ/fs41ZKsSf6+usqRPe LZLieM1TpvdYONRHiaU4I9FQi7moOBEACWU/6AwDAAA= Cc: freebsd-doc@freebsd.org, FreeBSD-gnats-submit@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 19:59:30 -0000 On Sun, 9 Feb 2014, Jamie Landeg-Jones wrote: > >> Description: > > Another typo. This time in ctime.3 man page.. I realise this is in > 'contrib' but there doesn't seem to be any info regarding who this is > pulled from. I think that the current ~upstream for the tzcode is supposed to be https://github.com/eggert/tz/ , but I haven't checked particularly recently. (There was some excitement involving a legal action, etc., so it had gone away and/or moved.) That said, I don't see a BUGS section at all in the newctime.3 in that repo, and I also don't see the erroneous line you quote in the history of that repo, so ... I'm not sure what happened. > I hope I don't get the reputation for most anal contributor :-( Definitely not! > (Is a PR the best way to report something so insignificant? Seems like > overkill... Gimme doc commit access!) PR is fine, it gives us a place to look when we need to find things. > Anyway.... The word 'leaves' instead of 'leave' in the following line: > > "-these functions leaves their result in an internal static object and return" Thanks for pointing it out. I'll try to think about what the best route to a fix is. -Ben From owner-freebsd-doc@FreeBSD.ORG Mon Feb 10 20:00:01 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5965E4C2 for ; Mon, 10 Feb 2014 20:00:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 459E11281 for ; Mon, 10 Feb 2014 20:00:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1AK01Ik052628 for ; Mon, 10 Feb 2014 20:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1AK01pZ052627; Mon, 10 Feb 2014 20:00:01 GMT (envelope-from gnats) Date: Mon, 10 Feb 2014 20:00:01 GMT Message-Id: <201402102000.s1AK01pZ052627@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: Benjamin Kaduk Subject: Re: docs/186608: typo in 'ctime(3) man page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Benjamin Kaduk List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 20:00:01 -0000 The following reply was made to PR docs/186608; it has been noted by GNATS. From: Benjamin Kaduk To: Jamie Landeg-Jones Cc: FreeBSD-gnats-submit@freebsd.org, freebsd-doc@freebsd.org Subject: Re: docs/186608: typo in 'ctime(3) man page Date: Mon, 10 Feb 2014 14:54:16 -0500 (EST) On Sun, 9 Feb 2014, Jamie Landeg-Jones wrote: > >> Description: > > Another typo. This time in ctime.3 man page.. I realise this is in > 'contrib' but there doesn't seem to be any info regarding who this is > pulled from. I think that the current ~upstream for the tzcode is supposed to be https://github.com/eggert/tz/ , but I haven't checked particularly recently. (There was some excitement involving a legal action, etc., so it had gone away and/or moved.) That said, I don't see a BUGS section at all in the newctime.3 in that repo, and I also don't see the erroneous line you quote in the history of that repo, so ... I'm not sure what happened. > I hope I don't get the reputation for most anal contributor :-( Definitely not! > (Is a PR the best way to report something so insignificant? Seems like > overkill... Gimme doc commit access!) PR is fine, it gives us a place to look when we need to find things. > Anyway.... The word 'leaves' instead of 'leave' in the following line: > > "-these functions leaves their result in an internal static object and return" Thanks for pointing it out. I'll try to think about what the best route to a fix is. -Ben From owner-freebsd-doc@FreeBSD.ORG Mon Feb 10 20:10:01 2014 Return-Path: Delivered-To: freebsd-docs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C99F4976 for ; Mon, 10 Feb 2014 20:10:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A6F471375 for ; Mon, 10 Feb 2014 20:10:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1AKA1hk055743 for ; Mon, 10 Feb 2014 20:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1AKA1Ab055742; Mon, 10 Feb 2014 20:10:01 GMT (envelope-from gnats) Date: Mon, 10 Feb 2014 20:10:01 GMT Message-Id: <201402102010.s1AKA1Ab055742@freefall.freebsd.org> To: freebsd-docs@FreeBSD.org From: Allan Jude Subject: Re: docs/185353: nc(1) does not exit after transfer (should be documented) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Allan Jude List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Feb 2014 20:10:01 -0000 The following reply was made to PR docs/185353; it has been noted by GNATS. From: Allan Jude To: bug-followup@FreeBSD.org, rol@robert-eckardt.de, delphij@freebsd.org Cc: Subject: Re: docs/185353: nc(1) does not exit after transfer (should be documented) Date: Mon, 10 Feb 2014 15:04:09 -0500 The fix has been committed to OpenBSD. http://marc.info/?l=openbsd-cvs&m=139206012706972&w=2 There have been a few other updates to netcat in the mean time, although they are to do with FD passing, which I suspect is an OpenBSD only feature. Hopefully Xin Li or someone else can MFV and pull in the fix for the man page. -- Allan Jude From owner-freebsd-doc@FreeBSD.ORG Tue Feb 11 00:21:40 2014 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 80A3D7F4; Tue, 11 Feb 2014 00:21:40 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [208.86.227.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 50E9E1A8D; Tue, 11 Feb 2014 00:21:40 +0000 (UTC) Received: from glenbarber.us (c-71-224-221-174.hsd1.nj.comcast.net [71.224.221.174]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) (Authenticated sender: gjb) by mail0.glenbarber.us (Postfix) with ESMTPSA id 557DE210B6; Tue, 11 Feb 2014 00:21:38 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 557DE210B6 Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Mon, 10 Feb 2014 19:21:36 -0500 From: Glen Barber To: John Baldwin Subject: Re: [PATCH] Publish the project's software license policy Message-ID: <20140211002136.GK1629@glenbarber.us> References: <201402071523.58314.jhb@freebsd.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="3NJww9yp20AXRsxZ" Content-Disposition: inline In-Reply-To: <201402071523.58314.jhb@freebsd.org> X-Operating-System: FreeBSD 11.0-CURRENT amd64 User-Agent: Mutt/1.5.22 (2013-10-16) Cc: doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2014 00:21:40 -0000 --3NJww9yp20AXRsxZ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Feb 07, 2014 at 03:23:58PM -0500, John Baldwin wrote: > A few years ago the core team approved a software license policy for the= =20 > project and announced it on developers@; however, it was never published = on=20 > the website. The patch below aims to remedy that. Can someone review th= e XML=20 > to make sure it is correct? It at least builds ok for me locally. >=20 > http://people.freebsd.org/~jhb/patches/license_policy.patch >=20 Looks good to me. Glen --3NJww9yp20AXRsxZ Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJS+W0QAAoJELls3eqvi17Q29wQANLiTGw9R4g3eBkDzdWtC8tc mNmd72jwU+vd3SKVXVsx9AbKwLktXACG4L1roGlHJ0/cpjc+PprIjnaOWrNVOei5 tdeeEKWatgUk7MMES2ot2GSjEmb1XbVo5t6tET42245GkUmYF5NiP2dqRxC49ppb oDrxftA7HqZZFoaE8RW1mqFNPHYVUPPpwyFusG06IwwFGgtMFjXOM3wsZwv2mIQI zLKgk9f1EpYpe7aMUpI3grwyJfn7WOXabPK82Jgh7MBdnVlLJWrJO/aWr0A1qEM+ Kl9yI5Xy1WEz2rfzkHviospsV1t06iXqN86IzLegf7lRyBubaWbKv5bxVf2WnW8r +++XjNqi43CBNTDvAvH69MlInEXWjMMXoy0sA0uGNSXYl3BJmf7pLGKckQjkaoPX 1dURL4oYiQjg+Tvy93XopibI9Syc9MDYxEAKl2P4/dxYlPpdLx1+b/UNXO9o7Wg4 MhW8I4upSm3XjHcD56GfKcOyvwGULM2h3d15g/u1NBY7XwBzuOSEufX0EmHYcywz 24ShLCvlIG9HQRLaVT822ygyMK4RE9rual35hSaeoQKLxet6exzZLl8qGC+vB1NO kKxkX5X/6LTXmWJEBsVqTSahjgMte9j9lrp3n++nIF7g/pWKERp1k3y4xynEPdz+ GGcfCyDt5mAA5QAbcfta =baZW -----END PGP SIGNATURE----- --3NJww9yp20AXRsxZ-- From owner-freebsd-doc@FreeBSD.ORG Tue Feb 11 04:54:57 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1E21682A for ; Tue, 11 Feb 2014 04:54:57 +0000 (UTC) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id E20F2141E for ; Tue, 11 Feb 2014 04:54:56 +0000 (UTC) Received: by mail-pb0-f44.google.com with SMTP id rq2so7191446pbb.17 for ; Mon, 10 Feb 2014 20:54:50 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:mime-version:in-reply-to:content-type :content-transfer-encoding:message-id:cc:from:subject:date:to; bh=4L0Q2VOPzckYh6+ou+OJnJGcJaJVtHTXdMG+VoE+PxM=; b=ke1IGCu4QwWdlQY59mKkCWCy71LzvWpoOPumvUzhSD/MQWO/6Gf+qy2Uw52vbCm3PM JD7HyMl1BZb3c4OW04h06/IlZyO6iNW+R6T8355PnpRlPyCoeY52Pf+FusdNjKOMU7eu tVVEIbUh0NdrLX8NO+U2cgmiuTdVkK7CNx9auXDBgdweElBuUh9tnMVpaYJ470stKnzo VsXjBH5YZtIsqreJoWEXq8G/JYAV+PmgDuayo1Rx61UyJTbgAwOL6fihLiTXG0oh9uEt irLf1/UCDC/+UXNRw5DqnEwisvb2EGSLoSNslg/8Fn1jhN4bYTVqpntCsgC/fkMobYiU MvWQ== X-Gm-Message-State: ALoCoQkTZb96Ftty4CR/MGCjhOIcy/7OLI1wP6pFml1MEvO3qKoNKBNa138RtpH4pmJ5BuR5iv3C X-Received: by 10.68.0.35 with SMTP id 3mr41621496pbb.52.1392094490580; Mon, 10 Feb 2014 20:54:50 -0800 (PST) Received: from [192.168.1.120] ([69.111.244.188]) by mx.google.com with ESMTPSA id oa3sm48240094pbb.15.2014.02.10.20.54.49 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 10 Feb 2014 20:54:49 -0800 (PST) References: <8D0F4110F6167E7-2378-15694@webmail-d224.sysops.aol.com> Mime-Version: 1.0 (1.0) In-Reply-To: <8D0F4110F6167E7-2378-15694@webmail-d224.sysops.aol.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <9F71B2D3-E4A6-439B-BFFC-242303A0DE12@helfman.org> X-Mailer: iPhone Mail (11B554a) From: Jason Helfman Subject: Re: Possible typo on doc/handbook/ports-using.html ? Date: Mon, 10 Feb 2014 20:54:49 -0800 To: Lampros Chaidas Cc: "freebsd-doc@FreeBSD.org" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2014 04:54:57 -0000 > On Feb 9, 2014, at 4:49 PM, Lampros Chaidas wrote= : >=20 > Hi there, >=20 > I was just reading through the documentation for getting the ports collect= ion with the subversion method and noticed the following in "Procedure 5.2. S= ubversion Method" - the link is http://www.freebsd.org/doc/handbook/ports-us= ing.html >=20 > "If the ports tree is not available, Subversion can be installed as = a package: > # pkg install subversion > If pkgng is being used to manage packages, Subversion can be ins= talled with it instead: > # pkg install subversion" >=20 > It looks like it's the same command in both situations - this looks redund= ant to me, is there a difference here that maybe I'm missing?=20 >=20 > Thanks, > - Lampros Both statements are true, however I believe this can be reworded and condens= ed.=20 I'll put together a patch. - jgh= From owner-freebsd-doc@FreeBSD.ORG Tue Feb 11 07:21:01 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1D2FFB2E for ; Tue, 11 Feb 2014 07:21:01 +0000 (UTC) Received: from boomer.ukrhub.net (boomer.ukrhub.net [94.125.121.14]) by mx1.freebsd.org (Postfix) with ESMTP id C1B4B1098 for ; Tue, 11 Feb 2014 07:21:00 +0000 (UTC) Received: by boomer.ukrhub.net (Postfix, from userid 58) id 7484624DC30; Tue, 11 Feb 2014 09:20:53 +0200 (EET) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on boomer.ukrhub.net X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.3.1 Received: from gamma.ukrhub.net (unknown [10.100.1.91]) by boomer.ukrhub.net (Postfix) with ESMTP id 451E424DC1F; Tue, 11 Feb 2014 09:20:48 +0200 (EET) Received: from gamma.ukrhub.net (localhost [127.0.0.1]) by gamma.ukrhub.net (8.14.7/8.14.7) with ESMTP id s1B7KlD8054452 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 11 Feb 2014 09:20:48 +0200 (EET) (envelope-from ds@ukrhub.net) Received: (from ds@localhost) by gamma.ukrhub.net (8.14.7/8.14.7/Submit) id s1B7KllK054451; Tue, 11 Feb 2014 09:20:47 +0200 (EET) (envelope-from ds@ukrhub.net) Date: Tue, 11 Feb 2014 09:20:47 +0200 From: Taras Korenko To: Jason Helfman Subject: Re: Possible typo on doc/handbook/ports-using.html ? Message-ID: <20140211072047.GA54201@gamma.ukrhub.net> References: <8D0F4110F6167E7-2378-15694@webmail-d224.sysops.aol.com> <9F71B2D3-E4A6-439B-BFFC-242303A0DE12@helfman.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <9F71B2D3-E4A6-439B-BFFC-242303A0DE12@helfman.org> User-Agent: Mutt/1.5.22 (2013-10-16) Cc: freebsd-doc@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Taras Korenko List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2014 07:21:01 -0000 On Mon, Feb 10, 2014 at 08:54:49PM -0800, Jason Helfman wrote: > > > On Feb 9, 2014, at 4:49 PM, Lampros Chaidas wrote: > > > > Hi there, > > > > I was just reading through the documentation for getting the ports collection with the subversion method and noticed the following in "Procedure 5.2. Subversion Method" - the link is http://www.freebsd.org/doc/handbook/ports-using.html > > > > "If the ports tree is not available, Subversion can be installed as a package: > > # pkg install subversion > > If pkgng is being used to manage packages, Subversion can be installed with it instead: > > # pkg install subversion" > > > > It looks like it's the same command in both situations - this looks redundant to me, is there a difference here that maybe I'm missing? > > > > Thanks, > > - Lampros > > Both statements are true, however I believe this can be reworded and condensed. > > I'll put together a patch. That was introduced in [1] as an attempt to clear texts from mentioning our old package management system (aka pkg_install). 1. http://svnweb.freebsd.org/doc/head/en_US.ISO8859-1/books/handbook/ports/chapter.xml?r1=43693&r2=43747 -- WBR, Taras Korenko From owner-freebsd-doc@FreeBSD.ORG Tue Feb 11 23:20:13 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 1156BC43 for ; Tue, 11 Feb 2014 23:20:13 +0000 (UTC) Received: from build-web.stream.freebsd.org (build-web.stream.freebsd.org [IPv6:2001:1900:2254:206a::16:6504]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D5EE41D83 for ; Tue, 11 Feb 2014 23:20:12 +0000 (UTC) Received: from build-web.stream.freebsd.org ([127.0.1.2]) by build-web.stream.freebsd.org (8.14.7/8.14.7) with ESMTP id s1BNKCrQ086590 for ; Tue, 11 Feb 2014 23:20:12 GMT (envelope-from www-data@build-web.stream.freebsd.org) Received: (from www-data@localhost) by build-web.stream.freebsd.org (8.14.8/8.14.8/Submit) id s1BNKC72086588 for freebsd-doc@FreeBSD.org; Tue, 11 Feb 2014 23:20:12 GMT (envelope-from www-data) Date: Tue, 11 Feb 2014 23:20:12 GMT From: User Www-data Message-Id: <201402112320.s1BNKC72086588@build-web.stream.freebsd.org> To: freebsd-doc@FreeBSD.org Subject: FreeBSD web build failed on build-web.stream.freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 11 Feb 2014 23:20:13 -0000 ===> doc/articles/mailing-list-faq (all) ===> doc/articles/mh (all) ===> doc/articles/nanobsd (all) ===> doc/articles/new-users (all) ===> doc/articles/p4-primer (all) ===> doc/articles/pam (all) ===> doc/articles/port-mentor-guidelines (all) ===> doc/articles/portbuild (all) ===> doc/articles/pr-guidelines (all) ===> doc/articles/problem-reports (all) ===> doc/articles/rc-scripting (all) ===> doc/articles/relaydelay (all) ===> doc/articles/releng (all) ===> doc/articles/releng-packages (all) ===> doc/articles/remote-install (all) ===> doc/articles/serial-uart (all) ===> doc/articles/solid-state (all) ===> doc/articles/vm-design (all) ===> doc/articles/wp-toolbox (all) ===> doc/books (all) ===> doc/books/arch-handbook (all) ===> doc/books/design-44bsd (all) ===> doc/books/dev-model (all) ===> doc/books/developers-handbook (all) ===> doc/books/faq (all) ===> doc/books/fdp-primer (all) ===> doc/books/handbook (all) env XML_CATALOG_FILES="file:///home/www/build/head/en_US.ISO8859-1/books/handbook/catalog-cwd.xml file:///home/www/build/head/en_US.ISO8859-1/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog.xml file:///home/www/build/head/share/xml/catalog-common.xml file:///usr/local/share/xml/catalog" /usr/local/bin/xmllint --nonet --noent --valid --dropdtd --xinclude /home/www/build/head/en_US.ISO8859-1/books/handbook/book.xml > book.parsed.xml.tmp /home/www/build/head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml:1046: namespace error : Namespace prefix link for href on link is not defined link:href="&url.base;/index.html">main site or ^ /home/www/build/head/en_US.ISO8859-1/books/handbook/l10n/chapter.xml:1046: element link: validity error : No declaration for attribute link:href of element link link:href="&url.base;/index.html">main site or ^ *** [book.parsed.xml] Error code 4 Stop in /home/www/build/head/en_US.ISO8859-1/books/handbook. *** [all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/books. *** [all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1. *** [all-all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/htdocs/doc. *** [all] Error code 1 Stop in /home/www/build/head/en_US.ISO8859-1/htdocs. 8.19 real 4.51 user 3.96 sys From owner-freebsd-doc@FreeBSD.ORG Wed Feb 12 13:35:30 2014 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0308530A for ; Wed, 12 Feb 2014 13:35:30 +0000 (UTC) Received: from nm16-vm4.bullet.mail.ir2.yahoo.com (nm16-vm4.bullet.mail.ir2.yahoo.com [212.82.96.210]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 512E0128D for ; Wed, 12 Feb 2014 13:35:28 +0000 (UTC) Received: from [212.82.98.127] by nm16.bullet.mail.ir2.yahoo.com with NNFMP; 12 Feb 2014 13:35:21 -0000 Received: from [46.228.39.98] by tm20.bullet.mail.ir2.yahoo.com with NNFMP; 12 Feb 2014 13:35:21 -0000 Received: from [127.0.0.1] by smtp135.mail.ir2.yahoo.com with NNFMP; 12 Feb 2014 13:35:21 -0000 X-Yahoo-Newman-Id: 475160.87870.bm@smtp135.mail.ir2.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: f1NZCu0VM1mxsn_Yc3zMW3iMxr3q8xFSWJVJrIz8LzuxGLS LfNfxbECmf7WXY2YVg1flzJgQXINK0y0DNOpe3v9va4nSA_xq.hsdSuS3I4c UAYkZ0Yf9F7TNWxs7AEZqbGb42L3mOhSxEM9OYJYcFqwFc7s8y18IJZroX5O p6Cbw17he225N50wmcS.EAQG..5LkI1vCYbnTzUW4EhUUXip_MLzz6nPS0p. mPppOOrcC2iKSiSUhmJAt7R1OoURlV52Ll4Ua82lufYl57UwxRC8lufWPQnS FGrT2UVMmuFPsyxxNTIz_rAVX1tUjtFm6vELooPNL0ejOZWNRQ.EXVJwYwfD UMVUSBHty6fquJBNKV71NuMonlnfnoK84MZR_D7aYOBXRaR3njeKJCB9TtAe 89ed3JJu9fZvi0l4cBrxUnZWxleGhm1HcVXxD_j6y5cxcao7yiKj3CiLlCXm Gm99Eh4Yvsfj6OqsmNFWSdb4Nzo_MpgFVolNm80OrnFBP5Zl0J9U8833qxTP 528Nb9QWqALYbRBHXCUPKjl0i2F41Xg-- X-Yahoo-SMTP: FzkX6BKswBDSwRukYY4VQ3FjvMR5KTXWQ4UJJ3dJFHGZZLeeISGlhg18_6fq X-Rocket-Received: from [192.168.0.101] (ricardezdouglas@37.45.249.58 with plain [188.125.69.59]) by smtp135.mail.ir2.yahoo.com with SMTP; 12 Feb 2014 13:35:21 +0000 UTC Message-Id: From: Sarah Z To: doc@freebsd.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Beverly Date: Wed, 12 Feb 2014 14:35:27 +0100 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2014 13:35:30 -0000 OzzyRebdowt, do you live near Beverly ? From owner-freebsd-doc@FreeBSD.ORG Wed Feb 12 15:57:21 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D4D45F52; Wed, 12 Feb 2014 15:57:21 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A843B112D; Wed, 12 Feb 2014 15:57:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1CFvLmv065391; Wed, 12 Feb 2014 15:57:21 GMT (envelope-from wblock@freefall.freebsd.org) Received: (from wblock@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1CFvLfW065390; Wed, 12 Feb 2014 15:57:21 GMT (envelope-from wblock) Date: Wed, 12 Feb 2014 15:57:21 GMT Message-Id: <201402121557.s1CFvLfW065390@freefall.freebsd.org> To: wblock@FreeBSD.org, freebsd-doc@FreeBSD.org, wblock@FreeBSD.org From: wblock@FreeBSD.org Subject: Re: docs/186614: Update htdocs/features.html to include 10.x X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2014 15:57:21 -0000 Synopsis: Update htdocs/features.html to include 10.x Responsible-Changed-From-To: freebsd-doc->wblock Responsible-Changed-By: wblock Responsible-Changed-When: Wed Feb 12 15:57:00 UTC 2014 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=186614 From owner-freebsd-doc@FreeBSD.ORG Wed Feb 12 16:39:09 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 03A37CE3; Wed, 12 Feb 2014 16:39:09 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C94571526; Wed, 12 Feb 2014 16:39:08 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1CGd8E4077808; Wed, 12 Feb 2014 16:39:08 GMT (envelope-from wblock@freefall.freebsd.org) Received: (from wblock@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1CGd8sH077807; Wed, 12 Feb 2014 16:39:08 GMT (envelope-from wblock) Date: Wed, 12 Feb 2014 16:39:08 GMT Message-Id: <201402121639.s1CGd8sH077807@freefall.freebsd.org> To: wblock@FreeBSD.org, freebsd-doc@FreeBSD.org, wblock@FreeBSD.org From: wblock@FreeBSD.org Subject: Re: docs/186537: [patch] removing obsolete vnode (9) man page references X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2014 16:39:09 -0000 Synopsis: [patch] removing obsolete vnode (9) man page references Responsible-Changed-From-To: freebsd-doc->wblock Responsible-Changed-By: wblock Responsible-Changed-When: Wed Feb 12 16:38:54 UTC 2014 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=186537 From owner-freebsd-doc@FreeBSD.ORG Wed Feb 12 19:40:30 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 464B265B for ; Wed, 12 Feb 2014 19:40:30 +0000 (UTC) Received: from mail-pd0-f182.google.com (mail-pd0-f182.google.com [209.85.192.182]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 18255165C for ; Wed, 12 Feb 2014 19:40:29 +0000 (UTC) Received: by mail-pd0-f182.google.com with SMTP id v10so9510799pde.27 for ; Wed, 12 Feb 2014 11:40:23 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=4GFcm7D0mFyBKDHmTFxshWKjKQlXe2YHzYm4eNqiaZI=; b=EplfIAoOBjxoLJYJOn7d1SVBGApBTZf23ab517w9UF8e4X2CdcWNGa3WcRqP4tuCgA EqIxScxV8+TH8ISza97gOpzcbqLWm7GwjCepCKuK/47AiS8a+YVV+ZIXhNa6ZY8H6V9k TGI/Ec2PnqycLd1kEPPdBT2CNj8jS2o5zSm76tM+xJ7zkBJQYiHKN3fMCq8RErYjOIbc OmIhMx6MMtHGxXswRB1RyYcOv4XkOfugZX2fLutnpRF9GqGeXyCOFRtyiymC5DwSdXch gPiBcJHu1caC9uyOu6qI6Mc88jagi6Iut/Gg3y5isOkxQm3HKgWq7sMDUZT+8r0LaLvp S7iw== X-Gm-Message-State: ALoCoQmk/vCVwYxaaqy/f//lYijIJyjVbCrI6QzDlD9E+avLfEKakQDCF/MLwz9hUiDeigp8d3Z8 MIME-Version: 1.0 X-Received: by 10.68.190.169 with SMTP id gr9mr53234593pbc.30.1392234022830; Wed, 12 Feb 2014 11:40:22 -0800 (PST) Sender: bsd-src@helfman.org Received: by 10.70.78.136 with HTTP; Wed, 12 Feb 2014 11:40:22 -0800 (PST) In-Reply-To: <20140211072047.GA54201@gamma.ukrhub.net> References: <8D0F4110F6167E7-2378-15694@webmail-d224.sysops.aol.com> <9F71B2D3-E4A6-439B-BFFC-242303A0DE12@helfman.org> <20140211072047.GA54201@gamma.ukrhub.net> Date: Wed, 12 Feb 2014 11:40:22 -0800 X-Google-Sender-Auth: 4j4iq7Pe5MRNqZYoBFOSF-TxE2k Message-ID: Subject: Re: Possible typo on doc/handbook/ports-using.html ? From: Jason Helfman To: Taras Korenko Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freesd-doc X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2014 19:40:30 -0000 On Mon, Feb 10, 2014 at 11:20 PM, Taras Korenko wrote: > On Mon, Feb 10, 2014 at 08:54:49PM -0800, Jason Helfman wrote: > > > > > On Feb 9, 2014, at 4:49 PM, Lampros Chaidas > wrote: > > > > > > Hi there, > > > > > > I was just reading through the documentation for getting the ports > collection with the subversion method and noticed the following in > "Procedure 5.2. Subversion Method" - the link is > http://www.freebsd.org/doc/handbook/ports-using.html > > > > > > "If the ports tree is not available, Subversion can be installed > as a package: > > > # pkg install subversion > > > If pkgng is being used to manage packages, Subversion can be > installed with it instead: > > > # pkg install subversion" > > > > > > It looks like it's the same command in both situations - this looks > redundant to me, is there a difference here that maybe I'm missing? > > > > > > Thanks, > > > - Lampros > > > > Both statements are true, however I believe this can be reworded and > condensed. > > > > I'll put together a patch. > > That was introduced in [1] as an attempt to clear texts from mentioning > our old package management system (aka pkg_install). > > 1. > http://svnweb.freebsd.org/doc/head/en_US.ISO8859-1/books/handbook/ports/chapter.xml?r1=43693&r2=43747 > -- > WBR, Taras Korenko > I've just committed a fix for this. Thanks for the report! -jgh -- Jason Helfman | FreeBSD Committer jgh@FreeBSD.org | http://people.freebsd.org/~jgh | The Power to Serve From owner-freebsd-doc@FreeBSD.ORG Wed Feb 12 23:10:02 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4DB1E79A for ; Wed, 12 Feb 2014 23:10:02 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3687B18AC for ; Wed, 12 Feb 2014 23:10:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1CNA1lm000966 for ; Wed, 12 Feb 2014 23:10:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1CNA1vN000965; Wed, 12 Feb 2014 23:10:01 GMT (envelope-from gnats) Date: Wed, 12 Feb 2014 23:10:01 GMT Message-Id: <201402122310.s1CNA1vN000965@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: Allan Jude Subject: Re: docs/186464: Online-Documentation for carp(4) is outdated X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Allan Jude List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Feb 2014 23:10:02 -0000 The following reply was made to PR docs/186464; it has been noted by GNATS. From: Allan Jude To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/186464: Online-Documentation for carp(4) is outdated Date: Wed, 12 Feb 2014 18:03:38 -0500 This is a multi-part message in MIME format. --------------020801060300060708020404 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Attached is a diff to bring the carp(4) section of the handbook up to date. It pulls the conceptual stuff out into a section before the instructions, and provides separate instructions for 9.x and prior, and 10.x and later. Also adds some of the newer markup, like -- Allan Jude --------------020801060300060708020404 Content-Type: text/plain; charset=windows-1252; name="docs.carp_10x.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="docs.carp_10x.diff" Index: advanced-networking/chapter.xml =================================================================== --- advanced-networking/chapter.xml (revision 43884) +++ advanced-networking/chapter.xml (working copy) @@ -5589,15 +5589,16 @@ - Common Address Redundancy Protocol - (<acronym>CARP</acronym>) + + Common Address Redundancy Protocol + (<acronym>CARP</acronym>) + TomRhodesContributed by + AllanJudeUpdated by - - CARP @@ -5607,135 +5608,280 @@ The Common Address Redundancy Protocol (CARP) allows multiple hosts to share the - same IP address. In some configurations, - this may be used for availability or load balancing. Hosts - may use separate IP addresses, as in the - example provided here. + same IP address(es) and can be used to + achieve high availability. Hosts should also have a unique + IP address for management and configuration, + as in the example provided here. - To enable support for CARP, the &os; - kernel can be rebuilt as described in with the following option: + + Using <acronym>CARP</acronym> for High + Availability - device carp + One use of CARP is to provide server + high availability for one or more services. This example + configures failover support for three hosts, all with + unique IP addresses and providing the same + web content. These machines are load balanced with a Round + Robin DNS configuration. The master and + backup machines should be configured identically other than + their hostnames and management IP + addresses. These servers need to run the same services, such + as the web server, with the same configuration so that when + the failover happens, requests to that service will be + answered correctly and with the same content. The failover + machine has two additional CARP interfaces, + one for each of the master content server's + IP addresses. When a failure occurs, the + failover server will pick up the failed machine's + IP address. This means that the failure + should go completely unnoticed by the user. This example has + two different masters named + hosta.example.org and + hostb.example.org respectively, with + a shared slave named + hostc.example.org. - Alternatively, the if_carp.ko module - can be loaded at boot time. Add the following line to - /boot/loader.conf: + Each virtual address has a unique + identification number known as a Virtual Host IDentification + (VHID) which is used to distinguish the + virtual address across the various failover machines that + share the address on the network. - if_carp_load="YES" + - CARP functionality should now be - available and may be tuned via several &man.sysctl.8; - variables: + + Using <acronym>CARP</acronym> on &os; 10 and + Later - - - - - OID - Description - - + To enable support for CARP, load the + carp.ko kernel module by adding the + following line to + /boot/loader.conf: - - - net.inet.carp.allow - Accept incoming CARP packets. - Enabled by default. - + carp_load="YES" - - net.inet.carp.preempt - This option downs all of the - CARP interfaces on the host when one - goes down. Disabled by default. - + Alternatively, the &os; kernel can be rebuilt as + described in with the following + option: - - net.inet.carp.log - A value of 0 disables any - logging. A value of 1 enables - logging of bad CARP packets. Values - greater than 1 enable logging of - state changes for the CARP - interfaces. The default value is - 1. - + device carp - - net.inet.carp.arpbalance - Balance local network traffic using - ARP. Disabled by default. - + Set the hostname, configure the management + IP address, then configure + CARP and the IP address + to be shared by adding the required lines to + /etc/rc.conf. Here are example lines for + hosta.example.org: - - net.inet.carp.suppress_preempt - A read-only variable showing the status of - preemption suppression. Preemption can be suppressed - if the link on an interface is down. A value of - 0 means that preemption is not - suppressed. Every problem increments this - variable. - - - - + hostname="hosta.example.org" +ifconfig_em0="inet 192.168.1.3 netmask 255.255.255.0" +ifconfig_em0_alias0="vhid 1 pass testpass alias 192.168.1.50/32" - The CARP devices themselves may be - created using &man.ifconfig.8;: + On hostb.example.org, use the + following lines: - &prompt.root; ifconfig carp0 create + hostname="hostb.example.org" +ifconfig_em0="inet 192.168.1.4 netmask 255.255.255.0" +ifconfig_em0_alias0="vhid 2 pass testpass alias 192.168.1.51/32" - In a real environment, each interface has a unique - identification number known as a Virtual Host IDentification - (VHID) which is used to distinguish the - host on the network. + + It is very important that the passwords, specified by + with &man.ifconfig.8;, are + identical. The carp devices will + only listen to and accept advertisements from machines + with the correct password. The VHID + must also be unique for each machine. + - - Using <acronym>CARP</acronym> for Server - Availability + The third machine, + hostc.example.org, + should be prepared so that it may handle failover from either + of the previous host. This machine will be configured with + two CARP VHIDs, one to + handle each host. The additional advskew + parameter controls the CARP advertising + skew. By making this host advertise later, it will become a + backup, rather than the master. The appropriate + /etc/rc.conf configuration lines will be + similar to the following: - One use of CARP is to provide server - availability. This example configures failover support for - three hosts, all with unique IP - addresses and providing the same web content. These machines - act in conjunction with a Round Robin - DNS configuration. The failover machine - has two additional CARP interfaces, one - for each of the content server's - IP addresses. When a - failure occurs, the failover server will pick up the failed - machine's IP address. - This means that the failure should go completely unnoticed - by the user. The failover server requires identical content - and services as the other content servers it is expected to - pick up load for. + hostname="hostc.example.org" +ifconfig_em0="inet 192.168.1.5 netmask 255.255.255.0" +ifconfig_em0_alias0="vhid 1 advskew 100 pass testpass alias 192.168.1.50/32" +ifconfig_em0_alias1="vhid 2 advskew 100 pass testpass alias 192.168.1.51/32" + Having the two CARP + VHIDs will allow + hostc.example.org to notice and + pick up the shared IP address of either + machine, should it become unavailable. + + + The default &os; kernel has + preemption disabled. If it is enabled, + hostc.example.org may not + relinquish the IP address back to the + original master server. In this case, an administrator may + have to manually force the IP back to the + master. The following command should be issued on + hostc.example.org: + + &prompt.root; ifconfig em0 vhid 1 state backup + + + + At this point, CARP should be enabled + and available for testing. For testing, either networking + has to be restarted or the machines rebooted. + + CARP functionality should now be + available and may be tuned via several &man.sysctl.8; + variables: + + + + + + OID + Description + + + + + + net.inet.carp.allow + Accept incoming CARP packets. + Enabled by default. + + + + net.inet.carp.preempt + Allow virtual hosts to preempt each other. For + firewalls and routers with multiple interfaces, it is + desirable to failover all of the addresses running + carp together, when one of the physical interfaces + goes down. This is achieved by the use of the preempt + option. When one of the physical interfaces of the + master fails, advskew is demoted to a configured value + on all its CARP + VHIDs. Due to the preempt option, + the backup host would start announcing itself, and + thus preempt the master host on both interfaces + instead of just the failed one. Disabled by + default. + + + + net.inet.carp.log + Determines what events relating to carp vhids are + logged. A value of 0 disables any logging. A value + of 1 enables logging state changes of carp vhids. + Values above 1 enable logging of bad carp packets. + The default value is 1. + + + + net.inet.carp.demotion + This value shows current level of + CARP demotion. The value is added + to the actual advskew sent in announcements for all + VHIDs. During normal system + operation the demotion factor is zero. However, + problematic conditions raise this level: when + CARP experiences a problem with + sending announcements, when an interface running a + VHID goes down, or while the + &man.pfsync.4; interface is not synchronized. The + demotion factor can be adjusted by writing to this + &man.sysctl.8; oid. The signed value supplied to the + &man.sysctl.8; command is added to current demotion + factor. This allows the behaviour of + CARP to be controlled depending on + external conditions, for example on the status of some + daemon utility. + + + + net.inet.carp.ifdown_demotion_factor + This value is added to + net.inet.carp.demotion when an + interface running a VHID goes down. + The default value is 240 (the maximum advskew + value). + + + + net.inet.carp.senderr_demotion_factor + This value is added to + net.inet.carp.demotion when + CARP experiences errors sending its + announcements. The default value is 240 (the maximum + advskew value). + + + + + + It is also possible to trigger other actions based on + CARP events using &man.devd.8;. More + information is available in &man.carp.4;. + + + + + Using <acronym>CARP</acronym> on &os; 9 and + Earlier + + To enable support for CARP, load the + if_carp.ko kernel module by adding the + following line to + /boot/loader.conf: + + if_carp_load="YES" + + Alternatively, the &os; kernel can be rebuilt as + described in with the following + option: + + device carp + + The CARP devices themselves may be + created using &man.ifconfig.8;: + + &prompt.root; ifconfig carp0 create + + Each virtual address has a unique + identification number known as a Virtual Host IDentification + (VHID) which is used to distinguish the + virtual address across the various failover machines that + share the address on the network. + The two machines should be configured identically other - than their hostnames and VHIDs. This - example calls these machines - hosta.example.org and - hostb.example.org respectively. First, the - required lines for a CARP configuration - have to be added to /etc/rc.conf. Here - are the lines for + than their hostnames, unique IP addresses + and VHIDs. This example calls these + machines hosta.example.org and + hostb.example.org respectively. + First, the required lines for a CARP + configuration have to be added to + /etc/rc.conf. Here are example lines for hosta.example.org: hostname="hosta.example.org" -ifconfig_fxp0="inet 192.168.1.3 netmask 255.255.255.0" +ifconfig_fxp0="inet 192.168.1.3 netmask 255.255.255.0" cloned_interfaces="carp0" -ifconfig_carp0="vhid 1 pass testpass 192.168.1.50/24" +ifconfig_carp0="vhid 1 pass testpass 192.168.1.50/24" On hostb.example.org, use the following lines: hostname="hostb.example.org" -ifconfig_fxp0="inet 192.168.1.4 netmask 255.255.255.0" +ifconfig_fxp0="inet 192.168.1.4 netmask 255.255.255.0" cloned_interfaces="carp0" -ifconfig_carp0="vhid 2 pass testpass 192.168.1.51/24" +ifconfig_carp0="vhid 2 pass testpass 192.168.1.51/24" It is very important that the passwords, specified by - the option to &man.ifconfig.8;, are + with &man.ifconfig.8;, are identical. The carp devices will only listen to and accept advertisements from machines with the correct password. The VHID @@ -5742,7 +5888,7 @@ must also be unique for each machine. - The third machine, provider.example.org, + The third machine, hostc.example.org, should be prepared so that it may handle failover from either host. This machine will require two carp devices, one to handle each @@ -5749,26 +5895,26 @@ host. The appropriate /etc/rc.conf configuration lines will be similar to the following: - hostname="provider.example.org" -ifconfig_fxp0="inet 192.168.1.5 netmask 255.255.255.0" + hostname="hostc.example.org" +ifconfig_fxp0="inet 192.168.1.5 netmask 255.255.255.0" cloned_interfaces="carp0 carp1" -ifconfig_carp0="vhid 1 advskew 100 pass testpass 192.168.1.50/24" -ifconfig_carp1="vhid 2 advskew 100 pass testpass 192.168.1.51/24" +ifconfig_carp0="vhid 1 advskew 100 pass testpass 192.168.1.50/24" +ifconfig_carp1="vhid 2 advskew 100 pass testpass 192.168.1.51/24" Having the two carp devices will - allow provider.example.org to notice and pick + allow hostc.example.org to notice and pick up the IP address of either machine, should - it stop responding. + it become unavailable. The default &os; kernel may have preemption enabled. If so, - provider.example.org may not relinquish the + hostc.example.org may not relinquish the IP address back to the original content server. In this case, an administrator may have to manually force the IP back to the master. The following command should be issued on - provider.example.org: + hostc.example.org: &prompt.root; ifconfig carp0 down && ifconfig carp0 up @@ -5780,6 +5926,63 @@ and available for testing. For testing, either networking has to be restarted or the machines rebooted. + CARP functionality should now be + available and may be tuned via several &man.sysctl.8; + variables: + + + + + + OID + Description + + + + + + net.inet.carp.allow + Accept incoming CARP packets. + Enabled by default. + + + + net.inet.carp.preempt + This option downs all of the + CARP interfaces on the host when one + goes down. Disabled by default. + + + + net.inet.carp.log + A value of 0 disables any + logging. A value of 1 enables + logging of bad CARP packets. Values + greater than 1 enable logging of + state changes for the CARP + interfaces. The default value is + 1. + + + + net.inet.carp.arpbalance + Balance local network traffic using + ARP. Disabled by default. + + + + net.inet.carp.suppress_preempt + A read-only variable showing the status of + preemption suppression. Preemption can be suppressed + if the link on an interface is down. A value of + 0 means that preemption is not + suppressed. Every problem increments this + variable. + + + + + More information is available in &man.carp.4;. --------------020801060300060708020404-- From owner-freebsd-doc@FreeBSD.ORG Thu Feb 13 00:52:56 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 11D629B7; Thu, 13 Feb 2014 00:52:56 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D55D81146; Thu, 13 Feb 2014 00:52:55 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1D0qtQ5044673; Thu, 13 Feb 2014 00:52:55 GMT (envelope-from wblock@freefall.freebsd.org) Received: (from wblock@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1D0qtVJ044672; Thu, 13 Feb 2014 00:52:55 GMT (envelope-from wblock) Date: Thu, 13 Feb 2014 00:52:55 GMT Message-Id: <201402130052.s1D0qtVJ044672@freefall.freebsd.org> To: wblock@FreeBSD.org, freebsd-doc@FreeBSD.org, wblock@FreeBSD.org From: wblock@FreeBSD.org Subject: Re: docs/186464: Online-Documentation for carp(4) is outdated X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 00:52:56 -0000 Synopsis: Online-Documentation for carp(4) is outdated Responsible-Changed-From-To: freebsd-doc->wblock Responsible-Changed-By: wblock Responsible-Changed-When: Thu Feb 13 00:52:35 UTC 2014 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=186464 From owner-freebsd-doc@FreeBSD.ORG Thu Feb 13 09:16:30 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 16A6AE19; Thu, 13 Feb 2014 09:16:30 +0000 (UTC) Received: from pacha.mail.dyslexicfish.net (space.mail.dyslexicfish.net [91.109.5.35]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A541F1BF4; Thu, 13 Feb 2014 09:16:27 +0000 (UTC) Received: from catnip.dyslexicfish.net (space.mail.dyslexicfish.net [91.109.5.35]) by pacha.mail.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id s1D9GH6j037710; Thu, 13 Feb 2014 09:16:18 GMT (envelope-from jamie@catnip.dyslexicfish.net) Received: (from jamie@localhost) by catnip.dyslexicfish.net (8.14.5/8.14.5/Submit) id s1D9GFsN037708; Thu, 13 Feb 2014 09:16:15 GMT (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <201402130916.s1D9GFsN037708@catnip.dyslexicfish.net> Date: Thu, 13 Feb 2014 09:16:13 +0000 To: jamie@dyslexicfish.net, bjk@freebsd.org Subject: Re: docs/186608: typo in 'ctime(3) man page References: <201402090702.s1972G1s067725@catnip.dyslexicfish.net> In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (pacha.mail.dyslexicfish.net [91.109.5.35]); Thu, 13 Feb 2014 09:16:19 +0000 (GMT) Cc: freebsd-doc@freebsd.org, FreeBSD-gnats-submit@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 09:16:30 -0000 Benjamin Kaduk wrote: > I think that the current ~upstream for the tzcode is supposed to be > https://github.com/eggert/tz/ , but I haven't checked particularly > recently. (There was some excitement involving a legal action, etc., so > it had gone away and/or moved.) That said, I don't see a BUGS section at > all in the newctime.3 in that repo, and I also don't see the erroneous > line you quote in the history of that repo, so ... I'm not sure what > happened. Ahh. OK! Thanks. > > I hope I don't get the reputation for most anal contributor :-( > > Definitely not! ha! You haven't seen my other PR's :-) > PR is fine, it gives us a place to look when we need to find things. ok, thanks. > Thanks for pointing it out. I'll try to think about what the best route > to a fix is. no rush. hee hee. p.s. my next PRs (2 pending) are 'proper' bug fixes! cheers, Jamie From owner-freebsd-doc@FreeBSD.ORG Thu Feb 13 09:20:02 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id ACB4DEEF for ; Thu, 13 Feb 2014 09:20:02 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 991481C2C for ; Thu, 13 Feb 2014 09:20:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1D9K2Qa018173 for ; Thu, 13 Feb 2014 09:20:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1D9K2mX018172; Thu, 13 Feb 2014 09:20:02 GMT (envelope-from gnats) Date: Thu, 13 Feb 2014 09:20:02 GMT Message-Id: <201402130920.s1D9K2mX018172@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: Jamie Landeg-Jones Subject: Re: docs/186608: typo in 'ctime(3) man page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Jamie Landeg-Jones List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 09:20:02 -0000 The following reply was made to PR docs/186608; it has been noted by GNATS. From: Jamie Landeg-Jones To: jamie@dyslexicfish.net, bjk@freebsd.org Cc: FreeBSD-gnats-submit@freebsd.org, freebsd-doc@freebsd.org Subject: Re: docs/186608: typo in 'ctime(3) man page Date: Thu, 13 Feb 2014 09:16:13 +0000 Benjamin Kaduk wrote: > I think that the current ~upstream for the tzcode is supposed to be > https://github.com/eggert/tz/ , but I haven't checked particularly > recently. (There was some excitement involving a legal action, etc., so > it had gone away and/or moved.) That said, I don't see a BUGS section at > all in the newctime.3 in that repo, and I also don't see the erroneous > line you quote in the history of that repo, so ... I'm not sure what > happened. Ahh. OK! Thanks. > > I hope I don't get the reputation for most anal contributor :-( > > Definitely not! ha! You haven't seen my other PR's :-) > PR is fine, it gives us a place to look when we need to find things. ok, thanks. > Thanks for pointing it out. I'll try to think about what the best route > to a fix is. no rush. hee hee. p.s. my next PRs (2 pending) are 'proper' bug fixes! cheers, Jamie From owner-freebsd-doc@FreeBSD.ORG Thu Feb 13 10:31:35 2014 Return-Path: Delivered-To: www@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CD9AC9BA for ; Thu, 13 Feb 2014 10:31:35 +0000 (UTC) Received: from tintin.oziolab.fr (tintin.oziolab.fr [109.74.91.168]) by mx1.freebsd.org (Postfix) with ESMTP id 5A5D913D3 for ; Thu, 13 Feb 2014 10:31:35 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by tintin.oziolab.fr (Postfix) with ESMTP id 41E333A4002 for ; Thu, 13 Feb 2014 11:26:02 +0100 (CET) X-Virus-Scanned: amavisd-new at tintin.oziolab.fr Received: from tintin.oziolab.fr ([127.0.0.1]) by localhost (tintin.oziolab.fr [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QP3O++JzM72i for ; Thu, 13 Feb 2014 11:26:01 +0100 (CET) Received: from tintin.oziolab.fr (tintin.oziolab.fr [109.74.91.168]) by tintin.oziolab.fr (Postfix) with ESMTP id E63353A4001 for ; Thu, 13 Feb 2014 11:26:01 +0100 (CET) Date: Thu, 13 Feb 2014 11:26:01 +0100 (CET) From: Michel Pouzet To: www@FreeBSD.org Message-ID: <23790157.1805.1392287148815.JavaMail."Michel Pouzet"@MichelPouzet-PC> In-Reply-To: <20651608.1781.1392286915866.JavaMail."Michel Pouzet"@MichelPouzet-PC> Subject: FreeBSD Ports web search page bug MIME-Version: 1.0 X-Originating-IP: [109.74.91.188] X-Mailer: Zimbra 7.2.3_GA_2872 (Zimbra Desktop/7.2.2_11951_Windows) X-Mailman-Approved-At: Thu, 13 Feb 2014 12:55:26 +0000 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 10:31:35 -0000 Hello,=20 It seems the ports search engine does not respond the way it should :=20 Using : http://www.freebsd.org/cgi/ports.cgi?=20 searching for : php55 in "All" and section=3D"Lang"=20 search patern =3D ^php55-=20 only gives 1 result : php55-extensions-1.8=20 and=20 search patern =3D ^php55- 5=20 only gives 1 result : php55-5.5.9=20 and AFAK the first pattern "^php55-" should answer both results.=20 Hope this help :)=20 Cordialement,=20 Michel Pouzet - Oziolab=20 Oziolab - 143 avenue de Keradenec - 29000 Quimper ( Attention: nouvelle adr= esse ! )=20 T=E9l: 02 98 10 66 52 - Fax: 09 72 21 45 75 - www.oziolab.fr - mp@oziolab.f= r - skype: michelpouzet=20 From owner-freebsd-doc@FreeBSD.ORG Thu Feb 13 15:54:16 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 4F538188; Thu, 13 Feb 2014 15:54:16 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1F0631339; Thu, 13 Feb 2014 15:54:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1DFsFWi052226; Thu, 13 Feb 2014 15:54:15 GMT (envelope-from brueffer@freefall.freebsd.org) Received: (from brueffer@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1DFsFI6052225; Thu, 13 Feb 2014 16:54:15 +0100 (CET) (envelope-from brueffer) Date: Thu, 13 Feb 2014 16:54:15 +0100 (CET) Message-Id: <201402131554.s1DFsFI6052225@freefall.freebsd.org> To: wosch@FreeBSD.org, brueffer@FreeBSD.org, freebsd-doc@FreeBSD.org From: brueffer@FreeBSD.org Subject: Re: docs/59477: Outdated Info Documents at http://docs.freebsd.org/info/ X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 15:54:16 -0000 Synopsis: Outdated Info Documents at http://docs.freebsd.org/info/ State-Changed-From-To: open->closed State-Changed-By: brueffer State-Changed-When: Thu Feb 13 16:53:26 CET 2014 State-Changed-Why: We haven't served those documents at all in a long time now, I suppose this PR can be closed now. http://www.freebsd.org/cgi/query-pr.cgi?pr=59477 From owner-freebsd-doc@FreeBSD.ORG Thu Feb 13 17:40:00 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9E96738E for ; Thu, 13 Feb 2014 17:40:00 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 780B61C9C for ; Thu, 13 Feb 2014 17:40:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1DHe0pY095682 for ; Thu, 13 Feb 2014 17:40:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1DHe0HI095681; Thu, 13 Feb 2014 17:40:00 GMT (envelope-from gnats) Resent-Date: Thu, 13 Feb 2014 17:40:00 GMT Resent-Message-Id: <201402131740.s1DHe0HI095681@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-doc@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Allan Jude Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 87F8B26E for ; Thu, 13 Feb 2014 17:37:58 +0000 (UTC) Received: from newred.freebsd.org (cgiserv.freebsd.org [IPv6:2001:1900:2254:206a::50:4]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 70CBA1C80 for ; Thu, 13 Feb 2014 17:37:58 +0000 (UTC) Received: from cgiserv.freebsd.org ([127.0.1.6]) by newred.freebsd.org (8.14.7/8.14.7) with ESMTP id s1DHbwea063899 for ; Thu, 13 Feb 2014 17:37:58 GMT (envelope-from nobody@cgiserv.freebsd.org) Received: (from nobody@localhost) by cgiserv.freebsd.org (8.14.7/8.14.7/Submit) id s1DHbwQL063889; Thu, 13 Feb 2014 17:37:58 GMT (envelope-from nobody) Message-Id: <201402131737.s1DHbwQL063889@cgiserv.freebsd.org> Date: Thu, 13 Feb 2014 17:37:58 GMT From: Allan Jude To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: docs/186731: Handbook section on journals and magazines is out of date X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 17:40:00 -0000 >Number: 186731 >Category: docs >Synopsis: Handbook section on journals and magazines is out of date >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Thu Feb 13 17:40:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Allan Jude >Release: 9.2-RELEASE >Organization: ScaleEngine Inc. >Environment: FreeBSD Trooper.HML3.ScaleEngine.net 9.2-RELEASE FreeBSD 9.2-RELEASE #0 r255898: Thu Sep 26 22:50:31 UTC 2013 root@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >Description: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/bibliography-journals.html is out of date Sys Admin magazine ceased publishing in 2007: http://www.techrepublic.com/blog/data-center/sysadmin-magazine-ceases-publication/ C/C++ Users Journal (Formerly BDS C Users' Group) was discontinued in 2006: http://en.wikipedia.org/wiki/C/C%2B%2B_Users_Journal FreeX was discontinued in 2012 and became part of Admin-magazin.de: http://translate.google.com/translate?hl=en&sl=de&u=http://www.cul.de/freex.html Move all of the magazines to the magazines section and change the headings, since it mentions magazines in two places add the FreeBSD Journal and BSD Now podcast to the magazines list. >How-To-Repeat: >Fix: Patch attached with submission follows: Index: head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml =================================================================== --- head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml (revision 43884) +++ head/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml (working copy) @@ -18,10 +18,9 @@ a good users' manual. - Books & Magazines Specific to FreeBSD + Books Specific to FreeBSD - International books & - Magazines: + International books: @@ -142,8 +141,7 @@ - English language books & - Magazines: + English language books: @@ -197,12 +195,6 @@ xlink:href="http://books.mcgraw-hill.com">McGrawHill, 2003. ISBN: 0072224096 - - - BSD - Magazine, published by Software Press Sp. z o.o. - SK. ISSN 1898-9144 - @@ -566,21 +558,31 @@ - The C/C++ Users Journal. R&D - Publications Inc. ISSN 1075-2838 + Admin + Magazin (in German), published by + Medialinx AG - Sys Admin — The Journal for UNIX System - Administrators Miller Freeman, Inc., ISSN - 1061-2688 + BSD + Magazine, published by Software Press Sp. z o.o. + SK. ISSN 1898-9144 - freeX — Das Magazin für Linux - BSD - - UNIX (in German) Computer- und - Literaturverlag GmbH, ISSN 1436-7033 + BSD Now + — Video Podcast, published by + Jupiter Broadcasting LLC + + + FreeBSD + Journal, published by S&W + Publishing, sponsored by The FreeBSD Foundation + >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Thu Feb 13 20:00:48 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3E0883D8; Thu, 13 Feb 2014 20:00:48 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 122D41C09; Thu, 13 Feb 2014 20:00:48 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1DK0lmq045323; Thu, 13 Feb 2014 20:00:47 GMT (envelope-from jgh@freefall.freebsd.org) Received: (from jgh@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1DK0lj2045322; Thu, 13 Feb 2014 20:00:47 GMT (envelope-from jgh) Date: Thu, 13 Feb 2014 20:00:47 GMT Message-Id: <201402132000.s1DK0lj2045322@freefall.freebsd.org> To: jgh@FreeBSD.org, freebsd-doc@FreeBSD.org, jgh@FreeBSD.org From: jgh@FreeBSD.org Subject: Re: docs/186731: Handbook section on journals and magazines is out of date X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 20:00:48 -0000 Synopsis: Handbook section on journals and magazines is out of date Responsible-Changed-From-To: freebsd-doc->jgh Responsible-Changed-By: jgh Responsible-Changed-When: Thu Feb 13 20:00:47 UTC 2014 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=186731 From owner-freebsd-doc@FreeBSD.ORG Thu Feb 13 20:25:00 2014 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BC5C793; Thu, 13 Feb 2014 20:25:00 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 92A541E5B; Thu, 13 Feb 2014 20:25:00 +0000 (UTC) Received: from ralph.baldwin.cx (pool-173-70-85-31.nwrknj.fios.verizon.net [173.70.85.31]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 847F2B9CA; Thu, 13 Feb 2014 15:24:59 -0500 (EST) From: John Baldwin To: freebsd-doc@freebsd.org Subject: Re: [PATCH] Use a bullet list for general policies Date: Sat, 08 Feb 2014 16:25:25 -0500 Message-ID: <2667682.EQsnSbIC49@ralph.baldwin.cx> User-Agent: KMail/4.10.5 (FreeBSD/10.0-STABLE; KDE/4.10.5; amd64; ; ) In-Reply-To: <52F63858.3010202@FreeBSD.org> References: <201401311421.31347.jhb@freebsd.org> <52F63858.3010202@FreeBSD.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Thu, 13 Feb 2014 15:24:59 -0500 (EST) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 20:25:00 -0000 On Saturday, February 08, 2014 02:59:52 PM Benedict Reuschling wrote: > Am 31.01.14 20:21, schrieb John Baldwin: > > Right now the internal policies page has a paragraph that lists the > > project's policies inline in one big sentence. I find this harder > > to work with as if I'm looking for a particular policy I have to > > scan the entire sentence. I think in this case a bulleted list > > works better. The patch below changes it (note that I haven't > > reordered them, and it may be that there is a better order, though > > I'm not sure what it would be). Any objections? > > > > Index: head/en_US.ISO8859-1/htdocs/internal/policies.xml > > =================================================================== > > --- head/en_US.ISO8859-1/htdocs/internal/policies.xml (revision 43698) > > > +++ head/en_US.ISO8859-1/htdocs/internal/policies.xml (working > > copy) @@ -34,25 +34,18 @@ > > > >

    General Policies

    > > > > -

    Here you will find various things such as the - > href="new-account.html">New Account Creation Procedure, -the > > -Commit Bit Expiration Policy, -the > > -Core Bylaws, -the - > href="resources.html">Commit Bit and Project Resources Policy, > > -Core's Voting Procedures, -the - > href="fortunes.html">Fortune File Policy, -the - > href="i18n.html">Internationalization Policy, -the - > href="data.html">User Data Policy, -the - > href="hats.html">Hats Term Limits Policy, -and the - > href="../doc/en_US.ISO8859-1/articles/pr-guidelines/">Problem > > Report Handling Guidelines.

    + > > > >

    The FreeBSD Documentation Project

    > > Hmm, maybe we should group "Commit Bit Expiration Policy" and "Commit > Bit and Project Resources Policy" together as well as the "Core > Bylaws" with "Core's Voting Procedures" as they are related topics. > The rest is pretty much standalone and I can't find any other better > order. I can also live with Eitan's suggestion of having them in > alphabetical order. I did think about grouping them some, but I found that the categories I was going to use (governance, inter-developer relationships) did not lend themselves to clear separation as many of the individual items fit into multiple categories, etc. Also, this page is a bit of a dumping ground as it is. I do think it might make sense to have a page that looks a bit more like: - Project Bylaws (rename the core bylaws to this) - Team Charters - portsmgr charter - secteam charter - re charter (does this exist?) - clusteradm charter - Policies - Right now I think some of the charters are scattered into different pages which isn't but so helpful for someone who wants to get a sense of how the Project works and/or is organized. -- John Baldwin From owner-freebsd-doc@FreeBSD.ORG Thu Feb 13 21:00:02 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 9CE3A236 for ; Thu, 13 Feb 2014 21:00:02 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6E5A11322 for ; Thu, 13 Feb 2014 21:00:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1DL01SL061018 for ; Thu, 13 Feb 2014 21:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1DL01Lm061017; Thu, 13 Feb 2014 21:00:01 GMT (envelope-from gnats) Date: Thu, 13 Feb 2014 21:00:01 GMT Message-Id: <201402132100.s1DL01Lm061017@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: Allan Jude Subject: Re: docs/182202: Handbook pkgng description doesn' t mention there are no repos X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Allan Jude List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 21:00:02 -0000 The following reply was made to PR docs/182202; it has been noted by GNATS. From: Allan Jude To: bug-followup@FreeBSD.org Cc: Subject: Re: docs/182202: Handbook pkgng description doesn't mention there are no repos Date: Thu, 13 Feb 2014 15:53:52 -0500 This PR can be closed now, We've had official pkgng repos for a while now. -- Allan Jude From owner-freebsd-doc@FreeBSD.ORG Thu Feb 13 22:20:00 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BC2EE3C3; Thu, 13 Feb 2014 22:20:00 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8CB171A40; Thu, 13 Feb 2014 22:20:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1DMK0JQ088462; Thu, 13 Feb 2014 22:20:00 GMT (envelope-from brueffer@freefall.freebsd.org) Received: (from brueffer@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1DMK0IY088461; Thu, 13 Feb 2014 23:20:00 +0100 (CET) (envelope-from brueffer) Date: Thu, 13 Feb 2014 23:20:00 +0100 (CET) Message-Id: <201402132220.s1DMK0IY088461@freefall.freebsd.org> To: scottro11@gmail.com, brueffer@FreeBSD.org, freebsd-doc@FreeBSD.org From: brueffer@FreeBSD.org Subject: Re: docs/182202: Handbook pkgng description doesn't mention there are no repos X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 22:20:00 -0000 Synopsis: Handbook pkgng description doesn't mention there are no repos State-Changed-From-To: open->closed State-Changed-By: brueffer State-Changed-When: Thu Feb 13 23:18:47 CET 2014 State-Changed-Why: As Allen says, luckily there are repos now, so no need to tone things down anymore. Thanks for the contribution! http://www.freebsd.org/cgi/query-pr.cgi?pr=182202 From owner-freebsd-doc@FreeBSD.ORG Thu Feb 13 22:40:01 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 79509AF7 for ; Thu, 13 Feb 2014 22:40:01 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 649F51BF7 for ; Thu, 13 Feb 2014 22:40:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1DMe1GX094596 for ; Thu, 13 Feb 2014 22:40:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1DMe1Xt094595; Thu, 13 Feb 2014 22:40:01 GMT (envelope-from gnats) Date: Thu, 13 Feb 2014 22:40:01 GMT Message-Id: <201402132240.s1DMe1Xt094595@freefall.freebsd.org> To: freebsd-doc@FreeBSD.org Cc: From: Allan Jude Subject: Re: docs/184482: passwd (1) man page incorrect info about login.conf X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Allan Jude List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Feb 2014 22:40:01 -0000 The following reply was made to PR docs/184482; it has been noted by GNATS. From: Allan Jude To: bug-followup@FreeBSD.org, ryan_gerstenkorn@fastmail.fm Cc: Subject: Re: docs/184482: passwd (1) man page incorrect info about login.conf Date: Thu, 13 Feb 2014 17:32:47 -0500 This is a multi-part message in MIME format. --------------000406000308090404010608 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Short man page patch to remove the offending sections -- Allan Jude --------------000406000308090404010608 Content-Type: text/plain; charset=windows-1252; name="man.passwd.1.diff" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="man.passwd.1.diff" Index: usr.bin/passwd/passwd.1 =================================================================== --- usr.bin/passwd/passwd.1 (revision 261727) +++ usr.bin/passwd/passwd.1 (working copy) @@ -59,27 +59,10 @@ .Nm utility prompts for the new password twice in order to detect typing errors. .Pp -The new password should be at least six characters long (which -may be overridden using the -.Xr login.conf 5 -.Dq minpasswordlen -setting for a user's login class) and not purely alphabetic. -Its total length must be less than +The total length of the password must be less than .Dv _PASSWORD_LEN (currently 128 characters). .Pp -The new password should contain a mixture of upper and lower case -characters (which may be overridden using the -.Xr login.conf 5 -.Dq mixpasswordcase -setting for a user's login class). -Allowing lower case passwords may -be useful where the password file will be used in situations where only -lower case passwords are permissible, such as when using Samba to -authenticate Windows clients. -In all other situations, numbers, upper -case letters and meta characters are encouraged. -.Pp Once the password has been verified, .Nm communicates the new password information to --------------000406000308090404010608-- From owner-freebsd-doc@FreeBSD.ORG Fri Feb 14 14:27:38 2014 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 90DAA934; Fri, 14 Feb 2014 14:27:38 +0000 (UTC) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 62BCE1C8C; Fri, 14 Feb 2014 14:27:38 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id s1EERcTW023982; Fri, 14 Feb 2014 14:27:38 GMT (envelope-from wblock@freefall.freebsd.org) Received: (from wblock@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s1EERcdk023981; Fri, 14 Feb 2014 14:27:38 GMT (envelope-from wblock) Date: Fri, 14 Feb 2014 14:27:38 GMT Message-Id: <201402141427.s1EERcdk023981@freefall.freebsd.org> To: wblock@FreeBSD.org, freebsd-doc@FreeBSD.org, wblock@FreeBSD.org From: wblock@FreeBSD.org Subject: Re: docs/184482: passwd (1) man page incorrect info about login.conf X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 14 Feb 2014 14:27:38 -0000 Synopsis: passwd (1) man page incorrect info about login.conf Responsible-Changed-From-To: freebsd-doc->wblock Responsible-Changed-By: wblock Responsible-Changed-When: Fri Feb 14 14:27:19 UTC 2014 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=184482 From owner-freebsd-doc@FreeBSD.ORG Sat Feb 15 09:39:53 2014 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 06DC4E30 for ; Sat, 15 Feb 2014 09:39:53 +0000 (UTC) Received: from mail-pd0-x242.google.com (mail-pd0-x242.google.com [IPv6:2607:f8b0:400e:c02::242]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CAA6416C9 for ; Sat, 15 Feb 2014 09:39:52 +0000 (UTC) Received: by mail-pd0-f194.google.com with SMTP id v10so5459880pde.9 for ; Sat, 15 Feb 2014 01:39:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=return-receipt-to:from:to:subject:date:message-id:mime-version :content-type:thread-index:content-language :disposition-notification-to; bh=YJSv78pTnBw0IPmE2OQortwe99zU3owSyqs9TdAshys=; b=KSxQ7cKCYKRq1nCvhYmuYgnSSY8fzAR2xPcWFcSxK4/62trhiHvwOQzZqLnrmhBiDP r8g/BullQEaS5MdNVBsPQg+UAu6S+CXoIjKyKCQk8+VItPytgbVrVModWbOyUIPI4Jr4 QCUe1r4sXR4/Eta1aw9JYtyr+HCSHD5QgYbU8vnMhtjjw27bENI202f0nQC2w9rHdLaD 9sPexvZdRcXslYzMIqFsXkwDDtEdOVLBTYpiEAZVKQ/KTocH0gySJYh6G4tmrfxI6K5g kajSbAxneCIYzPGDcouXzwlEvE6+GaJ4PTAEZUye78uivMekeg/mui90gS1gTtx1Z2nM l7YQ== X-Received: by 10.68.75.9 with SMTP id y9mr14402976pbv.61.1392457192493; Sat, 15 Feb 2014 01:39:52 -0800 (PST) Received: from omsairam15PC ([27.124.20.62]) by mx.google.com with ESMTPSA id hb10sm25552421pbd.1.2014.02.15.01.39.50 for (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sat, 15 Feb 2014 01:39:51 -0800 (PST) From: To: Subject: RE: Website Packages & SEO Date: Sat, 15 Feb 2014 15:09:45 +0530 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac8qMdtshHqSSRiDTfuw9nIw7r6dcw== Content-Language: en-us Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.17 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Feb 2014 09:39:53 -0000 Hi, Hope you are doing well. Haven't heard back from you, just wondering if you are interested in our services. We have special discount offers. I would be happy to share our past work details, methodologies & client testimonials. Kind Regards, Saadha Business Development Manager From: saadha.development@gmail.com [mailto:saadha.development@gmail.com] Sent: Tuesday, January 07, 2014 6:07 PM To: doc@freebsd.org Subject: Website Packages & SEO Hi, We are one of the leading website design and development company based out in India, which aims to provide its customers unbeatable, qualitative services with unmatched TAT & prices so that they (our customers) can easily achieve their business goals and objectives. Please have a look on Our Best, Affordable & Unmatched prices in comparison to the market If you are Freelancer / Agency / Business Owner Looking for development help WE TAKE CARE OF ALL YOUR DEVELOPMENT NEEDS We don't compromise with Quality and the deadlines. Convert Package PSD to html conversion $35 PSD to Wordpress $90 PSD to Drupal $150 PSD to Joomla $120 Development Package Wordpress website $180 Responsive website $200 Adword Landing Page $90 Static website $150 CMS Website $125 Ecommerce website $700 Website Maintenance Package Website maintenance $10 / hr Content Writing $10/per article Ecommerce website SEO $160* per month for 10 keywords $450* per month for 40 keywords *Article writing will be charged extra With more than 50 developers working for us, we offer: - Reduced cost - Flexibility - Assured deliverability - Ease of communication - Greater control over time management. We are looking forward to a long and fruitful business relationship with you and your company. We provide advance solutions for Search Engine Marketing (SEO & SMO), Ecommerce, Web Application Development, Custom Website Design & Development, Video Marketing, Website Maintenance, Data Processing & Analysis, Web Hosting and Content Writing Solutions to build your online presence. I wish to associate & get started & AMAZE you with our work. Thank you & looking forward for an early response. With Warm Regards, Saadha Business Development Manager Email: saadha.development@gmail.com From owner-freebsd-doc@FreeBSD.ORG Sat Feb 15 20:52:22 2014 Return-Path: Delivered-To: freebsd-docs@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E06C591B for ; Sat, 15 Feb 2014 20:52:22 +0000 (UTC) Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A50E21886 for ; Sat, 15 Feb 2014 20:52:22 +0000 (UTC) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AggQAMbS/1KtJV2d/2dsb2JhbABYgwY4cb8XAQEFAYERFnSCZEA9FhgDAgECAVgGAgEBBYd8DZh2sDAXjx6EIgSJSJtFhUKDSx4 X-IronPort-AV: E=Sophos;i="4.95,851,1384300800"; d="scan'208";a="304438867" Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 15 Feb 2014 20:52:22 +0000 Received: from rtp-jclarke-89112.cisco.com (rtp-jclarke-89112.cisco.com [10.117.46.173]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id s1FKqLFJ011007 for ; Sat, 15 Feb 2014 20:52:21 GMT Message-ID: <52FFD385.3080308@freebsd.org> Date: Sat, 15 Feb 2014 15:52:21 -0500 From: Joe Marcus Clarke Organization: FreeBSD, Inc. User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-docs@freebsd.org Subject: Quick typo fix to fortune Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Feb 2014 20:52:22 -0000 Any doc committer feel like making a quick fix or approving me to do so: http://www.marcuscom.com/downloads/fortunes.diff Joe -- Joe Marcus Clarke FreeBSD GNOME Team :: gnome@FreeBSD.org FreeNode / #freebsd-gnome http://www.FreeBSD.org/gnome From owner-freebsd-doc@FreeBSD.ORG Sat Feb 15 22:48:01 2014 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D6DD549A for ; Sat, 15 Feb 2014 22:48:01 +0000 (UTC) Received: from mxout2.bln1.prohost.de (mxout2.bln1.prohost.de [91.233.87.27]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6A2071108 for ; Sat, 15 Feb 2014 22:48:00 +0000 (UTC) Received: from Voyager.local (p4FC728B5.dip0.t-ipconnect.de [79.199.40.181]) (authenticated bits=0) by mx1.bln1.prohost.de (8.14.4/8.14.4) with ESMTP id s1FMloZq000572 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Sat, 15 Feb 2014 23:47:51 +0100 Message-ID: <52FFEE9B.5030005@FreeBSD.org> Date: Sat, 15 Feb 2014 23:47:55 +0100 From: Benedict Reuschling Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.3.0 MIME-Version: 1.0 To: freebsd-doc@FreeBSD.org Subject: Re: Quick typo fix to fortune References: <52FFD385.3080308@freebsd.org> In-Reply-To: <52FFD385.3080308@freebsd.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Null-Tag: 9bc5b63fe001985c945997254b059ff1 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 15 Feb 2014 22:48:01 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am 15.02.14 21:52, schrieb Joe Marcus Clarke: > Any doc committer feel like making a quick fix or approving me to > do so: > > http://www.marcuscom.com/downloads/fortunes.diff > > Joe > Approved, good catch! Regards Benedict Reuschling -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJS/+6bAAoJEAQa31nbPD2LBb0IAJmzrAxWhl77G7mEMf9ynJJJ H3x+47WVFY/qPzT7ZQdaIL+TCWcURkCtSsAeZ0aCdMufjqggVqtSNTVB1tQGbanH UdriXFxOhpU8/Jvx/onifw16h7BzHRdoJ3L6vM751A8CBod2ncqH6r8MAwWiAKTU hfT2jXdRtbVv2kAB+L4RsQdwWdaLm7lekG3qOvSfLeJwTX0EcJ4l6O24MOL5sX8/ f6+MvuvDSdGykAGQ/q8pZDxAJ9H+cw/2ZELjuFsLs1IY8KUoUZScTLXzCs73tWc/ UH3i+bqnYEVITFdtJwSWBVkLfXSKHmWjjJbtioTvu+YBGw4mZVsaBrupIlznVOc= =hnxM -----END PGP SIGNATURE-----