From owner-freebsd-doc@FreeBSD.ORG Sun Feb 2 08:16: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 C8CB2CC5 for ; Sun, 2 Feb 2014 08:16:13 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 9D12A1736 for ; Sun, 2 Feb 2014 08:16:12 +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 E23B2576DC for ; Sun, 2 Feb 2014 08:16:02 +0000 (UTC) Message-ID: <52EDFEBD.6010506@allanjude.com> Date: Sun, 02 Feb 2014 03:15:57 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-doc@FreeBSD.org Subject: New handbook section - resizing/growing disks X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OIUQbjDiv1OfudD7mrAk754nLOlvMqv2k" 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, 02 Feb 2014 08:16:13 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --OIUQbjDiv1OfudD7mrAk754nLOlvMqv2k Content-Type: multipart/mixed; boundary="------------000407000402060501060503" This is a multi-part message in MIME format. --------------000407000402060501060503 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable The question of how to resize a disk partition/file system has come up a number of times on IRC and elsewhere. A user writing a raspberry pi image to an SD card that is larger than the image and wanting to grow the file system to use the rest of the SSD Creating a live USB system A user who rented a VPS and then paid to grow the disk from 20GB to 80GB but the default install had the swap partition at the end. So, I wrote this section for the handbook that describes how to deal with those issues. --=20 Allan Jude --------------000407000402060501060503 Content-Type: text/plain; charset=windows-1252; name="docs.growfs.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="docs.growfs.patch" Index: disks/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 --- disks/chapter.xml (revision 43726) +++ disks/chapter.xml (working copy) @@ -252,6 +252,143 @@ &prompt.root; mount /newdisk= =20 + + + Resizing and Growing Disks + + + + + Allan + Jude + + Originally contributed by + + + + + + disks + resizing + + + This section describes how to resize (grow) an existing disk + in &os;. This procedure is most common with virtual machines, + but can also apply to images written to USB devices or other + cases where the partitions written to a disk do not match the + actual size of the disk. + + Determine the device name of the disk that needs to be + resized by inspecting /var/run/dmesg.boot. + In this example, there is only one SATA disk + in the system, so the drive will appear as + ada0. + + partitions + + gpart + + + List the partitions on the disk to determine what needs to + be done to resize the desired partition: + + &prompt.root; gpart show ada0 +=3D> 34 83886013 ada0 GPT (48G) [CORRUPT] + 34 128 1 freebsd-boot (64k) + 162 79691648 2 freebsd-ufs (38G) + 79691810 4194236 3 freebsd-swap (2G) + 83886046 1 - free - (512B) + + + If the disk was formatted with the + GPT partitioning scheme, it may show + as corrupted because GPT stores a backup + of the partition table at the end of the drive, which has now + moved. + + &prompt.root; gpart recover ada0 +ada0 recovered + + + Now the additional space on the disk is available: + + &prompt.root; gpart show ada0 +=3D> 34 102399933 ada0 GPT (48G) + 34 128 1 freebsd-boot (64k) + 162 79691648 2 freebsd-ufs (38G) + 79691810 4194236 3 freebsd-swap (2G) + 83886046 18513921 - free - (8.8G) + + It is only possible to resize a partition into contiguous + free space, however the last partition on the disk is the swap + partition, rather than the partition to be resized. Since swap + does not contain any non-volatile data, it can safely be deleted + and recreated after. + + &prompt.root; swapoff /dev/ada0p3 +&prompt.root; gpart delete -i 3 ada0 +ada0p3 deleted +&prompt.root; gpart show ada0 +=3D> 34 102399933 ada0 GPT (48G) + 34 128 1 freebsd-boot (64k) + 162 79691648 2 freebsd-ufs (38G) + 79691810 22708157 - free - (10G) + + Next resize the partition, leaving room to recreate a swap + partition of the desired size. + + + There is risk involved with modifying a live file system, + it is best to perform the following steps while running off of + a live CD or USB device. However it can be done on a live + system with the following work around: + + &prompt.root; sysctl kern.geom.debugflags=3D16 + + + + &prompt.root; gpart resize -i 2 -s 47G ada0 +ada0p2 resized +&prompt.root; gpart show ada0 +=3D> 34 102399933 ada0 GPT (48G) + 34 128 1 freebsd-boot (64k) + 162 98566144 2 freebsd-ufs (47G) + 98566306 3833661 - free - (1.8G) + + Next, recreate the swap partition: + + &prompt.root; gpart add -t freebsd-swap ada0 +ada0p3 added +&prompt.root; gpart show ada0 +=3D> 34 102399933 ada0 GPT (48G) + 34 128 1 freebsd-boot (64k) + 162 98566144 2 freebsd-ufs (47G) + 98566306 3833661 3 freebsd-swap (1.8G) +&prompt.root; swapon /dev/ada0p3 + + Finally, grow the UFS file system on the resized + partition: + + + growing a live UFS file system is only possible in &os; + 10.0-RELEASE and later, for earlier versions, the file system + must not be mounted. + + + &prompt.root; growfs /dev/ada0p2 +Device is mounted read-write; resizing will result in temporary write su= spension for /. +It's strongly recommended to make a backup before growing the file syste= m. +OK to grow filesystem on /dev/ada0p2, mounted on /, from 38GB to 47GB? [= Yes/No] Yes +super-block backups (for fsck -b #) at: + 80781312, 82063552, 83345792, 84628032, 85910272, 87192512, 88474752, + 89756992, 91039232, 92321472, 93603712, 94885952, 96168192, 97450432 + + The partition has now been resized to make use of all + available space on the disk. + + + USB Storage Devices --------------000407000402060501060503-- --OIUQbjDiv1OfudD7mrAk754nLOlvMqv2k 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/ iQIcBAEBAgAGBQJS7f7BAAoJEJrBFpNRJZKfka4P/jVyZU4tXDHfRmdjOWpiSMRx gWtovqvQiQJCxrw0kQv9g9YrRrMlH/jNG4WQacHSZouXqbL599u2k+9sJwKM2Y3O h71gTs0J+/0EOljEoV+BTugQiGckSAcWmqOIaDKINNGF0p0+9GdAMTd58TYGY/K0 LeCvEaqHp1nyS0CjEuGBGJV8lkagaEmpBv0gx9F3vK88+l3K88v6nXG169cVdzOb DKTLsdYf9BevFqaEzE70ymsYA5ejFxC8Kq3FomA6olmBVHxhl+6mQV7hozP+KYYu COCjUtB08qT+scAJy3T4q1kbX1vJk0ApK55KLIA+IKrsd11+48ER7be9VcWjKHAW bH5Pm+umDDcKBNnPF08aR1LcZmzXc4D1TnKr8mpWw7ZBO/9SEvSuDlXrxcoDzNXP qiWxyzuriOO6nXCddjA3kdeCzTKMTfoQuzK5p+RelfAU3II5AfYRKKOvPbZu5Nfh 6An841aeN3WmZkOK1T42BpvKPp7OVRcoSjK4I/nfiNSiyrHLPuomvIcFd64an80e Tj7Apx3XCkel3sR9q+MwqqfqTTsmo+KfZ+fYsr48UbL7UG2NcoPEpkpnHnoyAyOD DVQw/Eknqi+jC4Ut0BF0wNxUl4VFbjFLsuUh/gwXN9EJAJx0CiCJqVln3MISPE09 +tGST72IPPH36TjoAoh7 =uKJx -----END PGP SIGNATURE----- --OIUQbjDiv1OfudD7mrAk754nLOlvMqv2k-- From owner-freebsd-doc@FreeBSD.ORG Sun Feb 2 15:30:02 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 DB1B8A3B for ; Sun, 2 Feb 2014 15:30: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 B5ABD14C2 for ; Sun, 2 Feb 2014 15:30: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 s12FU2Mm034732 for ; Sun, 2 Feb 2014 15:30:02 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s12FU2wV034731; Sun, 2 Feb 2014 15:30:02 GMT (envelope-from gnats) Resent-Date: Sun, 2 Feb 2014 15:30:02 GMT Resent-Message-Id: <201402021530.s12FU2wV034731@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 6D7BE9EF for ; Sun, 2 Feb 2014 15:21:33 +0000 (UTC) Received: from oldred.freebsd.org (oldred.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 57D2D1489 for ; Sun, 2 Feb 2014 15:21:33 +0000 (UTC) Received: from oldred.freebsd.org ([127.0.1.6]) by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id s12FLW3R008038 for ; Sun, 2 Feb 2014 15:21:32 GMT (envelope-from nobody@oldred.freebsd.org) Received: (from nobody@localhost) by oldred.freebsd.org (8.14.5/8.14.5/Submit) id s12FLWk5008019; Sun, 2 Feb 2014 15:21:32 GMT (envelope-from nobody) Message-Id: <201402021521.s12FLWk5008019@oldred.freebsd.org> Date: Sun, 2 Feb 2014 15:21:32 GMT From: Allan Jude To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: docs/186377: new handbook section - growing disks 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, 02 Feb 2014 15:30:02 -0000 >Number: 186377 >Category: docs >Synopsis: new handbook section - growing disks >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: Sun Feb 02 15:30:01 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: A new section in the freebsd handbook to cover resizing/growing a disk Applies to: raspberry pi and other embedded images file system images written to USB sticks virtual machines and VPSs where a smaller image is used, or where the disk size is increased after-the-fact >How-To-Repeat: >Fix: Patch attached with submission follows: Index: disks/chapter.xml =================================================================== --- disks/chapter.xml (revision 43726) +++ disks/chapter.xml (working copy) @@ -252,6 +252,143 @@ &prompt.root; mount /newdisk + + + Resizing and Growing Disks + + + + + Allan + Jude + + Originally contributed by + + + + + + disks + resizing + + + This section describes how to resize (grow) an existing disk + in &os;. This procedure is most common with virtual machines, + but can also apply to images written to USB devices or other + cases where the partitions written to a disk do not match the + actual size of the disk. + + Determine the device name of the disk that needs to be + resized by inspecting /var/run/dmesg.boot. + In this example, there is only one SATA disk + in the system, so the drive will appear as + ada0. + + partitions + + gpart + + + List the partitions on the disk to determine what needs to + be done to resize the desired partition: + + &prompt.root; gpart show ada0 +=> 34 83886013 ada0 GPT (48G) [CORRUPT] + 34 128 1 freebsd-boot (64k) + 162 79691648 2 freebsd-ufs (38G) + 79691810 4194236 3 freebsd-swap (2G) + 83886046 1 - free - (512B) + + + If the disk was formatted with the + GPT partitioning scheme, it may show + as corrupted because GPT stores a backup + of the partition table at the end of the drive, which has now + moved. + + &prompt.root; gpart recover ada0 +ada0 recovered + + + Now the additional space on the disk is available: + + &prompt.root; gpart show ada0 +=> 34 102399933 ada0 GPT (48G) + 34 128 1 freebsd-boot (64k) + 162 79691648 2 freebsd-ufs (38G) + 79691810 4194236 3 freebsd-swap (2G) + 83886046 18513921 - free - (8.8G) + + It is only possible to resize a partition into contiguous + free space, however the last partition on the disk is the swap + partition, rather than the partition to be resized. Since swap + does not contain any non-volatile data, it can safely be deleted + and recreated after. + + &prompt.root; swapoff /dev/ada0p3 +&prompt.root; gpart delete -i 3 ada0 +ada0p3 deleted +&prompt.root; gpart show ada0 +=> 34 102399933 ada0 GPT (48G) + 34 128 1 freebsd-boot (64k) + 162 79691648 2 freebsd-ufs (38G) + 79691810 22708157 - free - (10G) + + Next resize the partition, leaving room to recreate a swap + partition of the desired size. + + + There is risk involved with modifying a live file system, + it is best to perform the following steps while running off of + a live CD or USB device. However it can be done on a live + system with the following work around: + + &prompt.root; sysctl kern.geom.debugflags=16 + + + + &prompt.root; gpart resize -i 2 -s 47G ada0 +ada0p2 resized +&prompt.root; gpart show ada0 +=> 34 102399933 ada0 GPT (48G) + 34 128 1 freebsd-boot (64k) + 162 98566144 2 freebsd-ufs (47G) + 98566306 3833661 - free - (1.8G) + + Next, recreate the swap partition: + + &prompt.root; gpart add -t freebsd-swap ada0 +ada0p3 added +&prompt.root; gpart show ada0 +=> 34 102399933 ada0 GPT (48G) + 34 128 1 freebsd-boot (64k) + 162 98566144 2 freebsd-ufs (47G) + 98566306 3833661 3 freebsd-swap (1.8G) +&prompt.root; swapon /dev/ada0p3 + + Finally, grow the UFS file system on the resized + partition: + + + growing a live UFS file system is only possible in &os; + 10.0-RELEASE and later, for earlier versions, the file system + must not be mounted. + + + &prompt.root; growfs /dev/ada0p2 +Device is mounted read-write; resizing will result in temporary write suspension for /. +It's strongly recommended to make a backup before growing the file system. +OK to grow filesystem on /dev/ada0p2, mounted on /, from 38GB to 47GB? [Yes/No] Yes +super-block backups (for fsck -b #) at: + 80781312, 82063552, 83345792, 84628032, 85910272, 87192512, 88474752, + 89756992, 91039232, 92321472, 93603712, 94885952, 96168192, 97450432 + + The partition has now been resized to make use of all + available space on the disk. + + + USB Storage Devices >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Sun Feb 2 16:09: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 82C477DF; Sun, 2 Feb 2014 16:09: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 57029174B; Sun, 2 Feb 2014 16:09: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 s12G90Ws042862; Sun, 2 Feb 2014 16:09:00 GMT (envelope-from wblock@freefall.freebsd.org) Received: (from wblock@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id s12G90Ha042861; Sun, 2 Feb 2014 16:09:00 GMT (envelope-from wblock) Date: Sun, 2 Feb 2014 16:09:00 GMT Message-Id: <201402021609.s12G90Ha042861@freefall.freebsd.org> To: wblock@FreeBSD.org, freebsd-doc@FreeBSD.org, wblock@FreeBSD.org From: wblock@FreeBSD.org Subject: Re: docs/186377: new handbook section - growing disks 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, 02 Feb 2014 16:09:00 -0000 Synopsis: new handbook section - growing disks Responsible-Changed-From-To: freebsd-doc->wblock Responsible-Changed-By: wblock Responsible-Changed-When: Sun Feb 2 16:08:44 UTC 2014 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=186377 From owner-freebsd-doc@FreeBSD.ORG Sun Feb 2 18:59: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 ADC89AD8 for ; Sun, 2 Feb 2014 18:59:00 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 63BFB13C3 for ; Sun, 2 Feb 2014 18:59:00 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s12Iww6l017322 for ; Sun, 2 Feb 2014 11:58:58 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s12IwwDC017319 for ; Sun, 2 Feb 2014 11:58:58 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 2 Feb 2014 11:58:58 -0700 (MST) From: Warren Block To: freebsd-doc@FreeBSD.org Subject: RFC: Author information display in documents Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 02 Feb 2014 11:58:58 -0700 (MST) 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, 02 Feb 2014 18:59:00 -0000 Based on a discussion on IRC, we'd like to ask for comments from people who have authored or contributed to documentation. At present, authors add their name and sometimes a description of their work like "Contributed by" or "Rewritten by". These author attributions are often quickly outdated as numerous other contributors fix problems and modify or add new content to the same section. There is potential for improving how this information is displayed. One possibility is auto-generating an Authors page, showing a list of authors and which portions of the document they have contributed. We have not yet considered technical aspects of generating this page, or the exact output format. However, it could be similar to a table of contents or index. As an initial mockup, consider this: Authors and Contributors Susan B. Anthony Contributed By: DHCP and Why You Should Care, page 12 ATM, the Silent Killer, page 54 Edited By: PPP for Dog Owners, page 38 John Smith Contributed By: Encrypting Disks, page 19 Reinstalling FreeBSD, page 20 Recovering from Backup, page 20 Edited By: When to Use Encryption, page 18 Rewritten By: Pitfalls of Encryption, page 18 The format of the list and contents would vary depending on the media. On the web, the titles would be links to the actual sections. In both cases, individual authors would not be shown at the top of the actual chapter or section in either HTML or PDF versions. The goal is to make the contributor information more accurate, more complete, and less distracting from content. We welcome comments and suggestions on this proposal. From owner-freebsd-doc@FreeBSD.ORG Sun Feb 2 22:11:40 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 90374C9; Sun, 2 Feb 2014 22:11:40 +0000 (UTC) Received: from oak.at.net.pl (oak.at.net.pl [80.48.135.200]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4A6EC14D9; Sun, 2 Feb 2014 22:11:39 +0000 (UTC) Received: from [10.0.1.203] (zarz-prod-gw.zarzad.buligl.pl [80.48.135.2]) by oak.at.net.pl (Postfix) with ESMTPA id 078DC95837; Sun, 2 Feb 2014 23:11:41 +0100 (CET) Message-ID: <52EEC28F.1050402@talarczyk.com> Date: Sun, 02 Feb 2014 23:11:27 +0100 From: Andrzej Talarczyk User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Benedict Reuschling Subject: Re: The FreeBSD Polish Documentation Project References: <52ECDD13.6040906@talarczyk.com> <52ECEB11.7040003@FreeBSD.org> In-Reply-To: <52ECEB11.7040003@FreeBSD.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-ATnet-MailScanner-Information: Please contact the ISP for more information X-ATnet-MailScanner-ID: 078DC95837.ACCB0 X-ATnet-MailScanner: Found to be clean X-ATnet-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-2.9, required 6, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90) X-ATnet-MailScanner-From: andrzej@talarczyk.com X-Spam-Status: No 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: Sun, 02 Feb 2014 22:11:40 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 W dniu 2014-02-01 13:39, Benedict Reuschling pisze: > Hello Andrzej, > > we have some translation projects that are abandoned or at least do > not receive regular updates. It's great that you are willing to > restart the project and provide updates, which is a huge help. > > You should have a look at the Documentation Primer here, which > contains all that you need to know about making changes to our > docs: > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/ > > If you have questions about specifics, don't hesitate to ask them > here. > > You can submit patches to the polish documents as PRs and we'll > find someone to commit then. Hello Benedict, thank you for your information. I'll start up updating the Polish docs then. I'll get back to the list here when I have a significant piece ready to be committed. Regards, Andrzej -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) iEYEARECAAYFAlLuwlgACgkQyoyWfOK+cwlIxwCgxwsLTvN/CsSfCNoVmZ+Z18yh y5QAnjKRVaIbW1AF1KJTvUCVW+xzctuk =CPMY -----END PGP SIGNATURE----- From owner-freebsd-doc@FreeBSD.ORG Sun Feb 2 22:37:22 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 AC06472E; Sun, 2 Feb 2014 22:37:22 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 7D08C16AD; Sun, 2 Feb 2014 22:37:21 +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 AC1FA57CD9; Sun, 2 Feb 2014 22:37:20 +0000 (UTC) Message-ID: <52EEC89B.5000403@allanjude.com> Date: Sun, 02 Feb 2014 17:37:15 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-doc@FreeBSD.org Subject: Re: Fwd: Re: svn commit: r43697 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs References: <52EC0C48.7060507@FreeBSD.org> In-Reply-To: <52EC0C48.7060507@FreeBSD.org> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="vMbdMPT7S7XBSvALFXOgTC5gmoFXxlamg" 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, 02 Feb 2014 22:37:22 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --vMbdMPT7S7XBSvALFXOgTC5gmoFXxlamg Content-Type: multipart/mixed; boundary="------------060605020303020203050600" This is a multi-part message in MIME format. --------------060605020303020203050600 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2014-01-31 15:49, Benedict Reuschling wrote: > Hi Allan, >=20 > how are you? Judging from BSDnow, you're doing fine. :) >=20 > Can you help me with the ZFS send via SSH part for the ZFS chapter > rewrite below? Benjamin Kaduk remarked that he does not understand > what needs to be done on each side. I think this needs more work and I > don't know exactly what needs to be set for root to be able to do this > (on each system). Plus, if you know some ports or other software that > does that, we could mention that in the paragraph as well. >=20 > I also need to look up the newer ZFS send stuff (hole-less send, the > bookmark-based resume feature, etc.) so that we can reflect this in > the handbook right from the start. If you have some time, I'd be glad > for a patch or some paragraphs that I can put into DocBook. >=20 > While on the subject: a while back you mentioned a port that does > grandfather, father, son snapshots and rotates them automatically. > What was the name of that port? I can't recall, but I want to try it > out at work and it would also be a good addition for the snapshot part.= >=20 > Thanks and keep up the good work with BSDnow and all your other BSD > activities. >=20 > Cheers >=20 > Benedict >=20 >=20 >=20 > -------- Original-Nachricht -------- > Betreff: Re: svn commit: r43697 - > projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs > Datum: Fri, 31 Jan 2014 14:32:11 -0500 (EST) > Von: Benjamin Kaduk > An: Benedict Reuschling > Kopie (CC): doc-committers@freebsd.org, svn-doc-projects@freebsd.org >=20 > On Thu, 30 Jan 2014, Benedict Reuschling wrote: >=20 >> + + + The root user needs >> to be able to + log into the receiving system because only >> that user can + send streams from the pool. SSH should be >> configured so + that root can only >> execute + zfs recv and nothing else to >> prevent + users that might have hijacked this account from >> doing + any harm on the system. >=20 > This paragraph is a little confusing about what happens on the sending > and > receiving systems. (For example, at first I was confused by the first > sentence, thinking that it was saying that the receiving system would b= e > sending streams from the pool.) Do both the send and receive have to > happen as root on the respective machines? I also think that the > restriction to 'zfs recv' should apply only to the particular ssh key > which is doing the automated backups; it would be absurd to prevent roo= t > login from one server to another just because there is a backup > relationship in place. >=20 >> + + + + After these security >> measures have been put into place + and root >> can connect passwordless via SSH >=20 I have made a first pass on this. It still needs some more work. I am not sure if it fits best in this section or the delegation section, but it would be good to document how to do it without root, as it is much safer than having unencrypted root keys laying around, and it is only 2 or 3 extra commands (zfs allow snapshot/send on one side and zfs receive/create etc on the other plus 1 sysctl (usermount)) In a future pass I'll update the screen sections to be more consistent as well --=20 Allan Jude --------------060605020303020203050600 Content-Type: text/plain; charset=windows-1252; name="zfs.send.patch" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="zfs.send.patch" 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 43727) +++ chapter.xml (working copy) @@ -1250,7 +1250,7 @@ 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 @@ -1268,7 +1268,7 @@ The following examples will demonstrate the functionality 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 +1277,38 @@ 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 + the primary pool becomes unavailable. 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 + administrator in case it is needed. First, a snapshot must be created on mypool to have a copy - of the current state of the data to send to the pool - backup. + of the current state of the data to send to the=20 + 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 + the snapshot, which can be stored as a file, or received by another poo= l. The stream must be written to the standard output, otherwise ZFS will - produce an error like in this example: + 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 t= he snapshot, + which means all the data contained in the snapshot, not + only the changes in the 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,98 +1316,100 @@ 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 has to 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 - Another feature of zfs send is that - it can determine the difference between two snapshots to - only send what has changed between the two. This results in - saving disk space and time for the transfer to another pool. + zfs send can also + determine the difference between two snapshots and + only send the changes between the two. This results in + saving disk space and transfer time. For example: =20 - &prompt.root; zfs snapshot mypool@backup2 -&prompt.root; zfs list -t snapshot + &prompt.root; zfs snapshot mypool@replica2 +&prompt.root; zfs list -t snapshot NAME USED AVAIL REFER MOUNTPOINT -mypool@backup1 5.72M - 43.6M - -mypool@backup2 0 - 44.1M - -&prompt.root; zpool list +mypool@replica1 5.72M - 43.6M - +mypool@replica2 0 - 44.1M - +&prompt.root; zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT backup 960M 61.7M 898M 6% 1.00x ONLINE - mypool 960M 50.2M 910M 5% 1.00x ONLINE - =20 A second snapshot called - backup2 was created. This second + replica2 was created. This second snapshot contains only the changes on the ZFS filesystem - between now and the last snapshot, - backup1. Using the - -i flag to zfs send - and providing both snapshots, an incremental snapshot can be - transferred, containing only the data that has + between now and the previous snapshot, + replica1. Using the + -i flag of zfs send + and indicating the pair of snapshots, an incremental replica + stream can be generated, containing only the data that has changed. =20 - &prompt.root; zfs send -i mypool@backup1 mypool@backup2 > /backup/incremental= -&prompt.root; zpool list + &prompt.root; zfs send -v -i mypool@replica1 mypool@replica2 | zfs receive /bac= kup/mypool +send from @replica1 to mypool@replica2 estimated size is 5.02M +total estimated size is 5.02M +TIME SENT SNAPSHOT + +&prompt.root; zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT backup 960M 80.8M 879M 8% 1.00x ONLINE - mypool 960M 50.2M 910M 5% 1.00x ONLINE - -&prompt.root; ls -lh /backup -total 82247 -drwxr-xr-x 1 root wheel 61M Dec 3 11:36 backup1 -drwxr-xr-x 1 root wheel 18M Dec 3 11:36 incremental= =20 +&prompt.root; zfs list +NAME USED AVAIL REFER MOUNTPOINT +backup 55.4M 240G 152K /backup +backup/mypool 55.3M 240G 55.2M /backup/mypool +mypool 55.6M 11.6G 55.0M /mypool + +&prompt.root; zfs list -t snapshot +NAME USED AVAIL REFER MOUNTPO= INT +backup/mypool@replica1 104K - 50.2M - +backup/mypool@replica2 0 - 55.2M - +mypool@replica1 29.9K - 50.0M - +mypool@replica2 0 - 55.0M - + The incremental stream was successfully transferred and - the file on disk is smaller than any of the two snapshots - backup1 or - backup2. This shows that it only + only the data that has changed was replicated, rather than + the entirety of + replica1 and + replica2 with both contain mostly the same= data. This shows that it only contains the differences, which is much faster to transfer and saves disk space by not copying the complete pool each time. This is useful when having to rely on slow networks or when costs per transferred byte have to be considered. - =20 - - Receiving ZFS Data Streams - - Up until now, only the data streams in binary form were - sent to other pools. To get to the actual data contained in - those streams, the reverse operation of zfs - send has to be used to transform the streams - back into files and directories. The command is called - zfs receive and has also a short version: - zfs recv. 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. - - &prompt.root; zfs send mypool@backup1 | zfs receive backup= /backup1 -&prompt.root; ls -lh /backup -total 431 -drwxr-xr-x 4219 root wheel 4.1k Dec 3 11:34 backup1= - - The directory backup1 does - contain all the data, which were part of the snapshot of the - same name. Since this originally was a complete filesystem - snapshot, the listing of all ZFS filesystems for this pool - is also updated and shows the - backup1 entry. - - &prompt.root; zfs list -NAME USED AVAIL REFER MOUNTPOINT -backup 43.7M 884M 32K /backup -backup/backup1 43.5M 884M 43.5M /backup/backup1 -mypool 50.0M 878M 44.1M /mypool - - A new filesystem, backup1 is - available and has the same size as the snapshot it was - created from. It is up to the user to decide whether the - streams should be transformed back into filesystems directly - to have a cold-standby for emergencies or to just keep the - streams and transform them later when required. Sending and + A new filesystem, backup/mypool is + available and has all of the files and data from the pool + mypool. Sending and receiving can be automated so that regular backups are created on a second pool for backup purposes. @@ -1428,14 +1432,17 @@ encrypted, SSH can be used. Since ZFS only requires the stream to be redirected from standard output, it is relatively easy to pipe it through - SSH. + SSH. If you wish the contents of your + ZFS file system to remain encrypted, + consider using PEFS. =20 A few settings and security precautions have to be made before this can be done. Since this chapter is about ZFS and not about configuring SSH, it only lists the things required to perform the encrypted zfs - send operation. The following settings should - be made: + send operation. The following configuration is + required: =20 @@ -1450,7 +1457,10 @@ that root can only execute zfs recv and nothing else to prevent users that might have hijacked this account from doing - any harm on the system. + any harm on the system. Using the delegation system it is + possible to perform replication without requiring + root access. =20 @@ -1460,8 +1470,8 @@ encrypted stream can be sent using the following commands: =20 - &prompt.root; zfs snapshot -r mypool/ho= me@monday -&prompt.root; zfs send -R mypool/home@monday | ssh backuphost zfs recv -dvu backuppool<= /screen> + &prompt.root; zfs snapshot -r mypool/home= @monday +&prompt.root; zfs send -R mypool/home@monday | ssh backuphost zfs recv -dvu backuppool =20 The first command creates a recursive snapshot (option -r) called --------------060605020303020203050600-- --vMbdMPT7S7XBSvALFXOgTC5gmoFXxlamg 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/ iQIcBAEBAgAGBQJS7sigAAoJEJrBFpNRJZKf7SQP/idxZEWJiGbZAyA0UGxgotL/ t398BisJ3Vmk9Ns+qeggTthKf+ZFg3VfGNb5pV3UKkwLABgr/0h1XnuXSFFqIkaU aA30LvuAQJLzCyTgIJqos9G6bMJKpGBEETkVT+yIEVYyDNJ/VlnfPfSv1Atd9e6l kxpzJRLrwz2FSdREaWPpwFi9XWwCfyXSm0fhIews1+xlbLlorhp7/pmmJrbTpwi8 Jf6zmXIo8dCfU76kySiZUb0CAupTErdvS7UKy27CXvXfX5zNH1iNHH0ZP3mtQJNz SMFi6p0r1WdZ8Z/7z/ZqZf776tjZZcHWV4hNj2fP5n5mi+tPqlPCqRcepY2aoEPA 499deB+qr6eY3bGkH1EfmErEeTrklphEZymaaiglIlZUL0WNL7xe/wipSLseb39p WFYjiMwOwPSWu8/2YfA75a0HShc306RhbYpp61KxOFyGM9woB2r5+KjMqHbtBqv6 oA39dmP8hXUT9/Pp7FTK9o0riJXOscePKe4xrca2BMRmDJNFH+l1Jr0/BACL4rhx DyfdKXvASYw/a2Lj1zbHcitX+nqAaLKbGmgX5XrbyFvBTFQUJiHN5AGfpIHAr4Wj sv4orD6RDLdcTyeRVCSr7pFhLTkquWwXukaMtrU0zcYg//0rBFXc5WvrdQvQb9kE VOl6dUM+LiRflTrq71gN =sz/y -----END PGP SIGNATURE----- --vMbdMPT7S7XBSvALFXOgTC5gmoFXxlamg-- From owner-freebsd-doc@FreeBSD.ORG Sun Feb 2 22:51: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 03007AE3 for ; Sun, 2 Feb 2014 22:51:30 +0000 (UTC) Received: from homiemail-a97.g.dreamhost.com (caiajhbdccac.dreamhost.com [208.97.132.202]) by mx1.freebsd.org (Postfix) with ESMTP id DBA9C1813 for ; Sun, 2 Feb 2014 22:51:29 +0000 (UTC) Received: from homiemail-a97.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a97.g.dreamhost.com (Postfix) with ESMTP id B76FF286057 for ; Sun, 2 Feb 2014 14:51:23 -0800 (PST) Received: from dreadnaught (ip68-100-185-59.dc.dc.cox.net [68.100.185.59]) (Authenticated sender: trhodes@fbsdsecure.org) by homiemail-a97.g.dreamhost.com (Postfix) with ESMTPA id C42BA286058 for ; Sun, 2 Feb 2014 14:51:22 -0800 (PST) Date: Sun, 2 Feb 2014 17:51:21 -0500 From: Tom Rhodes To: doc@FreeBSD.org Subject: Patch (WIP): New security front matter; new shell redirection section Message-Id: <20140202175121.16a0c264.trhodes@FreeBSD.org> 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=US-ASCII 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: Sun, 02 Feb 2014 22:51:30 -0000 Hi, After talking to a few people, I've written up two new sections, one is a huge cleanup of the security chapter and the second adds a shell redirection section to the handbook. Right now I'm seeking some comments and suggestions here. Want to commit sometime this week. Cheers, -- Tom Rhodes Index: handbook/basics/chapter.xml =================================================================== --- handbook/basics/chapter.xml (revision 43727) +++ handbook/basics/chapter.xml (working copy) @@ -987,7 +987,7 @@ pw - &man.pw.8; is a command line utility to create, remove, + The &man.pw.8; command line utility can create, remove, modify, and display users and groups. It functions as a front end to the system user and group files. &man.pw.8; has a very powerful set of command line options that make it @@ -3432,6 +3432,79 @@ Then, rerun &man.chsh.1;. + + + + Advanced Shell Techniques + + + + + Tom + Rhodes + + Written by + + + + + The &unix; shell is not just a command interpreter, it + acts as a powerful tool which allows users to execute commands, + redirect their output, redirect their input and chain commands + together to improve the final command output. When this functionality + is mixed with built in commands, the user is provided with + an environment that can maximize efficiency. + + Shell redirection is the action of sending the output + or the input of a command into another command or into a + file. To capture the output of the &man.ls.1; command, for + example, into a file, simply redirect the output: + + &prompt.user; ls > directory_listing.txt + + The directory_listing.txt file will + now contain the directory contents. Some commands allow you + to read input in a similar one, such as &man.sort.1;. To sort + this listing, redirect the input: + + &prompt.user; sort < directory_listing.txt + + The input will be sorted and placed on the screen. To + redirect that input into another file, one could redirect + the output of &man.sort.1; by mixing the direction: + + &prompt.user; sort < directory_listing.txt > sorted.txt + + In all of the previous examples, the commands are performing + redirection using file descriptors. Every unix system has file + descriptors; however, here we will focus on three, so named as + Standard Input, Standard Output, and Standard Error. Each one + has a purpose, where input could be a keyboard or a mouse, + something that provides input. Output could be a screen or + paper in a printer for example. And error would be anything + that is used for diagnostic or error messages. All three + are considered I/O based file descriptors + and sometimes considered streams. + + Through the use of these descriptors, short named + stdin, stdout, and stderr, the shell allows output and + input to be passed around through various commands and + redirected to or from a file. Another method of redirection + is the pipe operator. + + The &unix; pipe operator, | allows the + output of one command to be directly passed, or directed + to another program. Basically a pipe will allow the + standard output of a command to be passed as standard + input to another command, for example: + + &prompt.user; du -h | less + + In that example, the &man.du.1; command will direct the + output to the &man.less.1; command. This allows the user + to scroll through the output at their own pace and prevent + it from scrolling off the screen. + Index: handbook/security/chapter.xml =================================================================== --- handbook/security/chapter.xml (revision 43727) +++ handbook/security/chapter.xml (working copy) @@ -7,8 +7,13 @@ Security - MatthewDillonMuch of this chapter has been taken from the - security(7) manual page by + + + Tom + Rhodes + + Rewritten by + @@ -19,17 +24,17 @@ Synopsis - This chapter provides a basic introduction to system - security concepts, some general good rules of thumb, and some - advanced topics under &os;. Many of the topics covered here - can be applied to system and Internet security in general. - Securing a system is imperative to protect data, intellectual - property, time, and much more from the hands of hackers and the - like. + Security, whether physical or virtual, is a topic + so broad that an entire industry has grown up around it. + Hundreds of standard practices have been authored about + how to secure systems and networks, and as a user of &os;, + understanding how to protect against attacks and intruders + is a must. - &os; provides an array of utilities and mechanisms to - protect the integrity and security of the system and - network. + In this chapter, several fundamentals and techniques will + be discussed. The &os; system comes with multiple layers of + security, and many more third party utilities may be added to + enhance security. After reading this chapter, you will know: @@ -108,758 +113,202 @@ Introduction - Security is a function that begins and ends with the system - administrator. While &os; provides some inherent security, the - job of configuring and maintaining additional security - mechanisms is probably one of the single largest undertakings of - the sysadmin. + Security is everyone's responsibility. A weak entry point + in any system could allow intruders to gain access to critical + information and cause havoc on an entire network. In most + security training, they discuss the security triad + CIA which stands for the confidentiality, + integrity, and availability of information systems. - System security also pertains to dealing with various forms - of attack, including attacks that attempt to crash, or otherwise - make a system unusable, but do not attempt to compromise the - root account. Security concerns can be - split up into several categories: + The CIA triad is a bedrock concept of + computer security, customers and end users expect privacy + of their data; they expect orders they place to not be changed + or their information altered behind the scenes, and they expect + access to information at all times. Together they make up the + confidentiality, integrity, and availability of the + system. - - - Denial of service attacks. - + To protect CIA, security professionals + apply a defense in depth strategy. The idea of defense in + depth is to add several layers of security to prevent one single + layer failing and the entire security system collapsing. A + systems administrator cannot simply turn on a firewall and + consider the network or system secure, they must audit accounts, + check the integrity of binaries, and ensure malicious tools are + not installed. To do this, they must understand what the + threats are. - - User account compromises. - + + Threats - - Root compromise through accessible services. - + What is a threat as pertaining to computer security? For + years it was assumed that threats are remote attackers, people + whom will attempt to access the system without permission, from + a remote location. In today's world, this definition has been + expanded to include employees, malicious software, rogue + network devices, natural disasters, security vulnerabilities, + and even competing corporations. - - Root compromise via user accounts. - + Every day thousands of systems and networks are attacked and + several hundred are accessed without permission. Sometimes + by simple accident, others by remote attackers, and in some + cases, corporate espionage or former employees. As a system + user, it is important to prepare for and admit when a mistake + has lead to a security breach and report possible issues to + the security team. As an administrator, it is important to + know of the threats and be prepared to mitigate them. + - - Backdoor creation. - - + + A Ground Up Approach - - DoS attacks - Denial of Service (DoS) - - - security - DoS attacks - Denial of Service (DoS) - - Denial of Service (DoS) + In security, it is sometimes best to take a ground up + approach, whereas the administrator begins with the basic + accounts, system configuration, and then begins to work with + third party utilities and work up to the network layer. It + is in these latter configuration aspects that system policy + and procedures should take place. - A Denial of Service DoS attack is an - action that deprives the machine of needed resources. - Typically, DoS attacks are brute-force - mechanisms that attempt to crash or otherwise make a machine - unusable by overwhelming its services or network stack. Attacks - on servers can often be fixed by properly specifying options to - limit the load the servers incur on the system under adverse - conditions. Brute-force network attacks are harder to deal - with. This type of attack may not be able to take the machine - down, but it can saturate the Internet connection. + Many places of business already have a security policy that + covers the configuration technology devices in use. They + should contain, at minimal, the security configuration of end + user workstations and desktops, mobile devices such as phones + and laptops, and both production and development servers. In + many cases, when applying computer security, standard operating + procedures (SOPs) already exist. When in + doubt, ask the security team. + - - security - account compromises - + + System and User Accounts - A user account compromise is more common than a - DoS attack. Many sysadmins still run - unencrypted services, meaning that users logging into the - system from a remote location are vulnerable to having their - password sniffed. The attentive sysadmin analyzes the remote - access logs looking for suspicious source addresses and - suspicious logins. + In securing a system, the best starting point is auditing + accounts. Ensure that the root account has a strong password, + disable accounts that do not need shell access, for users who + need to augment their privileges, install the + security/sudo and only allow them access + to applications they need. The root user password should + never be shared. - In a well secured and maintained system, access to a user - account does not necessarily give the attacker access to - root. Without root - access, the attacker cannot generally hide his tracks and may, - at best, be able to do nothing more than mess with the user's - files or crash the machine. User account compromises are common - because users tend not to take the precautions that sysadmins - take. + To deny access to accounts, two methods exist. The first + one is to lock an account, for example, to lock the toor + account: - - security - backdoors - + &prompt.root; pw lock toor - There are potentially many ways to break - root: the attacker may know the - root password, the attacker may exploit a - bug in a service which runs as root, or the - attacker may know of a bug in a SUID-root program. An attacker - may utilize a program known as a backdoor to search for - vulnerable systems, take advantage of unpatched exploits to - access a system, and hide traces of illegal activity. + This command will change the account from this + toor:*:0:0::0:0:Bourne-again Superuser:/root: + to toor:*LOCKED**:0:0::0:0:Bourne-again + Superuser:/root: - Security remedies should always be implemented with a - multi-layered onion peel approach and can be - categorized as follows: + In some cases, this is not possible, perhaps because of + an additional service. In those cases, login access + could be prevented by changing the shell to /sbin/nologin + like in this example: - - - Secure root and staff - accounts. - + &prompt.root; chsh -s /usr/sbin/nologin toor - - Secure root–run servers - and SUID/SGID binaries. - + + Only super users are able to change the shell for + other users. Attempting to perform this as a regular user + will fail. + - - Secure user accounts. - + The account structure will now look like this, with + the nologin shell as the last entry: - - Secure the password file. - + toor:*:0:0::0:0:Bourne-again Superuser:/root:/usr/sbin/nologin - - Secure the kernel core, raw devices, and - filesystems. - + The /usr/sbin/nologin shell will block + the &man.login.1; command from assigning a shell to this + user. + - - Quick detection of inappropriate changes made to the - system. - + + Permitted Account Escalation - - Paranoia. - - + In some cases, system administration access needs to + be shared with other users. &os; has two methods to + handle this. The first one, which is not recommended, + is a shared root password and adding users to the + wheel group. + To achieve this, edit the /etc/group + and add the user to the end of the first group. This + user must be separated by a comma character. - The next section covers these items in greater depth. - + The correct way to permit this privilege escalation is + using the security/sudo port which will + provide additional auditing, more fine grained user + control, and even lock users into running only single, + privileged commands such as &man.service.8; - - Securing &os; + After installation, edit the + /usr/local/etc/sudoers file by using + the visudo interface. In this example, + a new webadmin group will be added, the user + trhodes to that + group, and then give the user + access to restart apache24, the following + procedure may be followed: - - security - securing &os; - + &prompt.root; pw groupadd webadmin -M trhodes -g 6000 - This section describes methods for securing a &os; system - against the attacks that were mentioned in the previous section. + &prompt.root; visudo - - Securing the <systemitem class="username">root</systemitem> Account + %webadmin ALL=(ALL) /usr/sbin/service apache24 * - - &man.su.1; - - - Most - systems have a password assigned to the - root account. Assume that this password - is always at risk of being compromised. - This does not mean that the password should be disabled as the - password is almost always necessary for console access to the - machine. However, it should not be possible to use this - password outside of the console or possibly even with - &man.su.1;. For example, setting the entries in - /etc/ttys to insecure - prevents root logins to the specified - terminals. In &os;, root logins using - &man.ssh.1; are disabled by default as - PermitRootLogin is set to - no in - /etc/ssh/sshd_config. Consider every - access method as services such as FTP often fall through the - cracks. Direct root logins should only - be allowed via the system console. - - - wheel - - - Since a sysadmin needs access to - root, additional password verification - should be configured. One method is to add appropriate user - accounts to wheel in - /etc/group. Members of - wheel are allowed to &man.su.1; to - root. Only those users who actually need - to have root access should be placed in - wheel. When using Kerberos for - authentication, create a .k5login in - the home directory of root to allow - &man.ksu.1; to be used without having to place anyone in - wheel. - - To lock an account completely, use &man.pw.8;: - - &prompt.root; pw lock staff - - This will prevent the specified user from logging in using - any mechanism, including &man.ssh.1;. - - Another method of blocking access to accounts would be to - replace the encrypted password with a single - * character. This character - would never match the encrypted password and thus blocks user - access. For example, the entry for the following - account: - - foobar:R9DT/Fa1/LV9U:1000:1000::0:0:Foo Bar:/home/foobar:/usr/local/bin/tcsh - - could be changed to this using &man.vipw.8;: - - foobar:*:1000:1000::0:0:Foo Bar:/home/foobar:/usr/local/bin/tcsh - - This prevents foobar from logging in - using conventional methods. This method for access - restriction is flawed on sites using - Kerberos or in situations where the - user has set up keys with &man.ssh.1;. - - These security mechanisms assume that users are logging - in from a more restrictive server to a less restrictive - server. For example, if the server is running network - services, the workstation should not be running any. In - order for a workstation to be reasonably secure, run zero or - as few services as possible and run a password-protected - screensaver. Of course, given physical access to any system, - an attacker can break any sort of security. Fortunately, - many break-ins occur remotely, over a network, from people who - do not have physical access to the system. - - Using Kerberos provides the ability to disable or change - the password for a user in one place, and have it immediately - affect all the machines on which the user has an account. If - an account is compromised, the ability to instantly change the - associated password on all machines should not be underrated. - Additional restrictions can be imposed with Kerberos: a - Kerberos ticket can be configured to timeout and the Kerberos - system can require that the user choose a new password after a - configurable period of time. - - - - Securing Root-run Servers and SUID/SGID Binaries - - - sandboxes - - - &man.sshd.8; - - - The prudent sysadmin only enables required services and is - aware that third party servers are often the most bug-prone. - Never run a server that has not been checked out carefully. - Think twice before running any service as - root as many daemons can be run as a - separate service account or can be started in a - sandbox. Do not activate insecure - services such as &man.telnetd.8; or &man.rlogind.8;. - - Another potential security hole is SUID-root and SGID - binaries. Most of these binaries, such as &man.rlogin.1;, - reside in /bin, - /sbin, /usr/bin, or /usr/sbin. While nothing is - 100% safe, the system-default SUID and SGID binaries can be - considered reasonably safe. It is recommended to restrict - SUID binaries to a special group that only staff can access, - and to delete any unused SUID binaries. SGID binaries can be - almost as dangerous. If an intruder can break an SGID-kmem - binary, the intruder might be able to read - /dev/kmem and thus read the encrypted - password file, potentially compromising user accounts. - Alternatively, an intruder who breaks group - kmem can monitor keystrokes sent through - ptys, including ptys used by users who login through secure - methods. An intruder that breaks the - tty group can write to almost any - user's tty. If a user is running a terminal program or - emulator with a keyboard-simulation feature, the intruder can - potentially generate a data stream that causes the user's - terminal to echo a command, which is then run as that - user. - - - - Securing User Accounts - - User accounts are usually the most difficult to secure. - Be vigilant in the monitoring of user accounts. Use of - &man.ssh.1; and Kerberos for user accounts requires extra - administration and technical support, but provides a good - solution compared to an encrypted password file. - - - - Securing the Password File - - The only sure fire way is to star out as many passwords as - possible and use &man.ssh.1; or Kerberos for access to those - accounts. Even though the encrypted password file - (/etc/spwd.db) can only be read by - root, it may be possible for an intruder - to obtain read access to that file even if the attacker cannot - obtain root-write access. - - Security scripts should be used to check for and report - changes to the password file as described in the Checking file integrity + The security/sudo provides an + invaluable resource when it comes to local user management. + It is also possible to not require passwords and just default + to the &man.ssh.1; key method. To disable password login + via &man.sshd.8; and only use local passwords for + sudo, see the section. - - Securing the Kernel Core, Raw Devices, and - Filesystems + + Passwords - Most modern kernels have a packet sniffing device driver - built in. Under &os; it is called - bpf. This device is needed for DHCP, - but can be removed in the custom kernel configuration file of - systems that do not provide or use DHCP. + Passwords are a necessary evil of the past. In the cases + they must be used, not only should the password be extremely + complex, but also use a powerful hash mechanism to protect it. + At the time of this writing, &os; supports + DES, MD5, Blowfish, + SHA256, and SHA512 in + the crypt() library. The default is + SHA512 and should not be changed backwards; + however, some users like to use the Blowfish option. Each + mechanism, aside from DES, has a unique + beginning to designate the hash mechanism assigned. For the + MD5 mechanism, the symbol is a + $ sign. For the SHA256 or + SHA512, the symbol is $6$ + and Blowfish uses $2a$. Any weaker passwords + should be re-hashed by asking the user to run &man.passwd.1; + during their next login. - - &man.sysctl.8; - - - Even if bpf is disabled, - /dev/mem and - /dev/kmem are still problematic. An - intruder can still write to raw disk devices. An enterprising - intruder can use &man.kldload.8; to install his own - bpf, or another sniffing device, on a - running kernel. To avoid these problems, run the kernel at a - higher security level, at least security level 1. - - The security level of the kernel can be set in a variety - of ways. The simplest way of raising the security level of a - running kernel is to set - kern.securelevel: - - &prompt.root; sysctl kern.securelevel=1 - - By default, the &os; kernel boots with a security level of - -1. This is called insecure mode because - immutable file flags may be turned off and all devices may be - read from or written to. The security level will remain at -1 - unless it is altered, either by the administrator or by - &man.init.8;, because of a setting in the startup scripts. - The security level may be raised during system startup by - setting - kern_securelevel_enable to - YES in /etc/rc.conf, - and the value of kern_securelevel to the - desired security level. - - Once the security level is set to 1 or a higher value, the - append-only and immutable files are honored, they cannot be - turned off, and access to raw devices is denied. Higher - levels restrict even more operations. For a full description - of the effect of various security levels, refer to - &man.security.7; and &man.init.8;. - - Bumping the security level to 1 or higher may cause a - few problems to &xorg;, as access - to /dev/io will be blocked, or to the - installation of &os; built from source as - installworld needs to temporarily - reset the append-only and immutable flags of some files. - In the case of &xorg;, it may be - possible to work around this by starting &man.xdm.1; early - in the boot process, when the security level is still low - enough. Workarounds may not be possible for all secure - levels or for all the potential restrictions they enforce. - A bit of forward planning is a good idea. Understanding the - restrictions imposed by each security level is important as - they severely diminish the ease of system use. It will also - make choosing a default setting much simpler and prevent any - surprises. + At the time of this writing, blowfish is not part of + AES nor is it considered compliant + with any FIPS (Federal Information + Processing Standards) standard and it's use may not be + permitted in some environments. - If the kernel's security level is raised to 1 or a higher - value, it may be useful to set the schg - flag on critical startup binaries, directories, script files, - and everything that gets run up to the point where the - security level is set. A less strict compromise is to run - the system at a higher security level but skip setting the - schg flag. Another possibility is to - mount / and /usr read-only. It should be - noted that being too draconian about what is permitted may - prevent detection of an intrusion. + For any system connected to the network, two factor + authentication should be used. This is normally considered + something you have and something you know. With + OpenSSH being part of the &os; + base system and the use of ssh-keys being available for some + time, all network logins should avoid the use of passwords in + exchange for this two factor authentication method. For + more information see the section of + the handbook. Kerberose users may need to make additional + changes to implement OpenSSH in + their network. - - - Checking File Integrity - - One can only protect the core system configuration and - control files so much before the convenience factor rears its - ugly head. For example, using &man.chflags.1; to set the - schg bit on most of the files in / and /usr is probably - counterproductive, because while it may protect the files, it - also closes an intrusion detection window. Security measures - are useless or, worse, present a false sense of security, if - potential intrusions cannot be detected. Half the job of - security is to slow down, not stop, an attacker, in order to - catch him in the act. - - The best way to detect an intrusion is to look for - modified, missing, or unexpected files. The best way to look - for modified files is from another, often centralized, - limited-access system. Writing security scripts on the - extra-security limited-access system makes them mostly - invisible to potential attackers. In order to take maximum - advantage, the limited-access box needs significant access to - the other machines, usually either through a read-only - NFS export or by setting up - &man.ssh.1; key-pairs. Except for its network traffic, - NFS is the least visible method, allowing - the administrator to monitor the filesystems on each client - box virtually undetected. If a limited-access server is - connected to the client boxes through a switch, the - NFS method is often the better choice. If - a limited-access server is connected to the client boxes - through several layers of routing, the NFS - method may be too insecure and &man.ssh.1; may be the better - choice. - - Once a limited-access box has been given at least read - access to the client systems it is supposed to monitor, create - the monitoring scripts. Given an NFS - mount, write scripts out of simple system utilities such as - &man.find.1; and &man.md5.1;. It is best to physically - &man.md5.1; the client system's files at least once a day, and - to test control files such as those found in /etc and /usr/local/etc even more often. - When mismatches are found, relative to the base md5 - information the limited-access machine knows is valid, it - should alert the sysadmin. A good security script will also - check for inappropriate SUID binaries and for new or deleted - files on system partitions such as / and /usr. - - When using &man.ssh.1; rather than NFS, - writing the security script is more difficult. For example, - &man.scp.1; is needed to send the scripts to the client box in - order to run them. The &man.ssh.1; client on the client box - may already be compromised. Using &man.ssh.1; may be - necessary when running over insecure links, but it is harder - to deal with. - - A good security script will also check for changes to - hidden configuration files, such as - .rhosts and - .ssh/authorized_keys, as these files - might fall outside the purview of the - MD5 check. - - For a large amount of user disk space, it may take too - long to run through every file on those partitions. In this - case, consider setting mount flags to disallow SUID binaries - by using nosuid with &man.mount.8;. Scan - these partitions at least once a week, since the objective is - to detect a break-in attempt, whether or not the attempt - succeeds. - - Process accounting (see &man.accton.8;) is a relatively - low-overhead feature of &os; which might help as a - post-break-in evaluation mechanism. It is especially useful - in tracking down how an intruder broke into a system, assuming - the file is still intact after the break-in has - occurred. - - Finally, security scripts should process the log files, - and the logs themselves should be generated in as secure a - manner as possible and sent to a remote syslog server. An - intruder will try to cover his tracks, and log files are - critical to the sysadmin trying to track down the time and - method of the initial break-in. One way to keep a permanent - record of the log files is to run the system console to a - serial port and collect the information to a secure machine - monitoring the consoles. - - - - Paranoia - - A little paranoia never hurts. As a rule, a sysadmin can - add any number of security features which do not affect - convenience and can add security features that - do affect convenience with some added - thought. More importantly, a security administrator should - mix it up a bit. If recommendations, such as those mentioned - in this section, are applied verbatim, those methodologies are - given to the prospective attacker who also has access to this - document. - - - - Denial of Service Attacks - - - Denial of Service (DoS) - - - A DoS attack is typically a packet - attack. While there is not much one can do about spoofed - packet attacks that saturate a network, one can generally - limit the damage by ensuring that the attack cannot take down - servers by: - - - - Limiting server forks. - - - - Limiting springboard attacks such as ICMP response - attacks and ping broadcasts. - - - - Overloading the kernel route cache. - - - - A common DoS attack scenario is to - force a forking server to spawn so many child processes that - the host system eventually runs out of memory and file - descriptors, and then grinds to a halt. There are several - options to &man.inetd.8; to limit this sort of attack. It - should be noted that while it is possible to prevent a machine - from going down, it is not generally possible to prevent a - service from being disrupted by the attack. Read - &man.inetd.8; carefully and pay specific attention to - , , and - . Spoofed IP attacks will circumvent - to &man.inetd.8;, so typically a - combination of options must be used. Some standalone servers - have self-fork-limitation parameters. - - Sendmail provides - , which tends to work - better than trying to use - Sendmail's load limiting options - due to the load lag. Specify a - MaxDaemonChildren when starting - Sendmail which is high enough to - handle the expected load, but not so high that the computer - cannot handle that number of - Sendmail instances. It is prudent - to run Sendmail in queued mode - using and to run the - daemon (sendmail -bd) separate from the - queue-runs (sendmail -q15m). For - real-time delivery, run the queue at a much lower interval, - such as , but be sure to specify a - reasonable MaxDaemonChildren to prevent - cascade failures. - - &man.syslogd.8; can be attacked directly and it is - strongly recommended to use - whenever possible, and - otherwise. - - Be careful with connect-back services such as - reverse-identd, which can be attacked directly. The - reverse-ident feature of - TCP Wrappers is not recommended for - this reason. - - It is recommended to protect internal services from - external access by firewalling them at the border routers. - This is to prevent saturation attacks from outside the LAN, - not so much to protect internal services from network-based - root compromise. Always configure an - exclusive firewall which denies everything by default except - for traffic which is explicitly allowed. The range of port - numbers used for dynamic binding in &os; is controlled by - several net.inet.ip.portrange - &man.sysctl.8; variables. - - Another common DoS attack, called a - springboard attack, causes the server to generate responses - which overloads the server, the local network, or some other - machine. The most common attack of this nature is the - ICMP ping broadcast attack. The attacker - spoofs ping packets sent to the LAN's broadcast address with - the source IP address set to the machine to attack. If the - border routers are not configured to drop ping packets sent to - broadcast addresses, the LAN generates sufficient responses to - the spoofed source address to saturate the victim, especially - when the attack is against several dozen broadcast addresses - over several dozen different networks at once. A second - common springboard attack constructs packets that generate - ICMP error responses which can saturate a server's incoming - network and cause the server to saturate its outgoing network - with ICMP responses. This type of attack can crash the - server by running it out of memory, especially if the server - cannot drain the ICMP responses it generates fast enough. Use - the &man.sysctl.8; variable - net.inet.icmp.icmplim to limit these - attacks. The last major class of springboard attacks is - related to certain internal &man.inetd.8; services such as the - UDP echo service. An attacker spoofs a UDP packet with a - source address of server A's echo port and a destination - address of server B's echo port, where server A and B on the - same LAN. The two servers bounce this one packet back and - forth between each other. The attacker can overload both - servers and the LAN by injecting a few packets in this manner. - Similar problems exist with the - chargen port. These inetd-internal - test services should remain disabled. - - Spoofed packet attacks may be used to overload the kernel - route cache. Refer to the - net.inet.ip.rtexpire, - rtminexpire, and - rtmaxcache &man.sysctl.8; parameters. A - spoofed packet attack that uses a random source IP will cause - the kernel to generate a temporary cached route in the route - table, viewable with netstat -rna | fgrep - W3. These routes typically timeout in 1600 - seconds or so. If the kernel detects that the cached route - table has gotten too big, it will dynamically reduce the - rtexpire but will never decrease it to less - than rtminexpire. This creates two - problems: - - - - - The kernel does not react quickly enough when a - lightly loaded server is suddenly attacked. - - - - The rtminexpire is not low enough - for the kernel to survive a sustained attack. - - - - If the servers are connected to the Internet via a T3 or - better, it may be prudent to manually override both - rtexpire and rtminexpire - via &man.sysctl.8;. Never set either parameter to zero - as this could crash the machine. Setting both parameters to 2 - seconds should be sufficient to protect the route table from - attack. - - - - Access Issues with Kerberos and &man.ssh.1; - - &man.ssh.1; - - There are a few issues with both Kerberos and &man.ssh.1; - that need to be addressed if they are used. Kerberos is an - excellent authentication protocol, but there are bugs in the - kerberized versions of &man.telnet.1; and &man.rlogin.1; that - make them unsuitable for dealing with binary streams. By - default, Kerberos does not encrypt a session unless - is used whereas &man.ssh.1; encrypts - everything. - - While &man.ssh.1; works well, it forwards encryption keys - by default. This introduces a security risk to a user who - uses &man.ssh.1; to access an insecure machine from a secure - workstation. The keys themselves are not exposed, but - &man.ssh.1; installs a forwarding port for the duration of the - login. If an attacker has broken root on - the insecure machine, he can utilize that port to gain access - to any other machine that those keys unlock. - - It is recommended that &man.ssh.1; is used in combination - with Kerberos whenever possible for staff logins and - &man.ssh.1; can be compiled with Kerberos support. This - reduces reliance on potentially exposed SSH - keys while protecting passwords via Kerberos. Keys should - only be used for automated tasks from secure machines as this - is something that Kerberos is unsuited to. It is recommended - to either turn off key-forwarding in the - SSH configuration, or to make use - of from=IP/DOMAIN in - authorized_keys to make the key only - usable to entities logging in from specific machines. - - - DES, Blowfish, MD5, SHA256, SHA512, and Crypt - - BillSwingleParts rewritten and updated by - - - - - - - - security - crypt - - - crypt - Blowfish - DES - MD5 - SHA256 - SHA512 - - Every user on a &unix; system has a password associated with - their account. In order to keep these passwords secret, they - are encrypted with a one-way hash, as they can - be easily encrypted but not decrypted. The operating system - itself does not know the password. It only knows the - encrypted form of the password. The only - way to get the plain-text password is by a brute - force search of the space of possible passwords. - - Originally, the only secure way to encrypt passwords in - &unix; was based on the Data Encryption Standard - (DES). Since the source code for - DES could not be exported outside the US, - &os; had to find a way to both comply with US law and retain - compatibility with other &unix; variants that used - DES. The solution was MD5 which is believed - to be more secure than DES. - - - Recognizing the Crypt Mechanism - - Currently the library supports DES, - MD5, Blowfish, SHA256, and SHA512 hash functions. To identify - which encryption method &os; is set up to use, examine the - encrypted passwords in - /etc/master.passwd. Passwords encrypted - with the MD5 hash are longer than those encrypted with the - DES hash and begin with the characters - $1$. Passwords starting with - $2a$ are encrypted with the - Blowfish hash function. DES password - strings do not have any particular identifying - characteristics, but they are shorter than MD5 passwords, and - are coded in a 64-character alphabet which does not include - the $ character, so a relatively - short string which does not begin with a dollar sign is very - likely a DES password. Both SHA256 and - SHA512 begin with the characters - $6$. - - The password format used for new passwords is controlled - by the passwd_format login capability in - /etc/login.conf, which takes values of - des, md5, - blf, sha256 or - sha512. Refer to &man.login.conf.5; for - more information about login capabilities. - - - One-time Passwords @@ -1970,6 +1419,44 @@ + Access Issues with Kerberos and &man.ssh.1; + + &man.ssh.1; + + There are a few issues with both Kerberos and &man.ssh.1; + that need to be addressed if they are used. Kerberos is an + excellent authentication protocol, but there are bugs in the + kerberized versions of &man.telnet.1; and &man.rlogin.1; that + make them unsuitable for dealing with binary streams. By + default, Kerberos does not encrypt a session unless + is used whereas &man.ssh.1; encrypts + everything. + + While &man.ssh.1; works well, it forwards encryption keys + by default. This introduces a security risk to a user who + uses &man.ssh.1; to access an insecure machine from a secure + workstation. The keys themselves are not exposed, but + &man.ssh.1; installs a forwarding port for the duration of the + login. If an attacker has broken + root on + the insecure machine, he can utilize that port to gain access + to any other machine that those keys unlock. + + It is recommended that &man.ssh.1; is used in combination + with Kerberos whenever possible for staff logins and + &man.ssh.1; can be compiled with Kerberos support. This + reduces reliance on potentially exposed SSH + keys while protecting passwords via Kerberos. Keys should + only be used for automated tasks from secure machines as this + is something that Kerberos is unsuited to. It is recommended + to either turn off key-forwarding in the + SSH configuration, or to make use + of from=IP/DOMAIN in + authorized_keys to make the key only + usable to entities logging in from specific machines. + + + Resources and Further Information From owner-freebsd-doc@FreeBSD.ORG Mon Feb 3 01:28:54 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 18790878; Mon, 3 Feb 2014 01:28:54 +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 0394F19EB; Mon, 3 Feb 2014 01:28:54 +0000 (UTC) Received: from nemysis4now (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with SMTP id s131Sppf074713; Mon, 3 Feb 2014 01:28:52 GMT (envelope-from nemysis@FreeBSD.org) Received: by nemysis4now (sSMTP sendmail emulation); Mon, 03 Feb 2014 02:28:51 +0100 Date: Mon, 3 Feb 2014 02:28:51 +0100 From: Rusmir Dusko To: freebsd-doc@FreeBSD.org Subject: [PATCH] Stripping Binaries and Shared Libraries Message-ID: <20140203012851.GA88519@nemysis4now> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline User-Agent: Mutt/1.5.22 (2013-10-16) Cc: nemysis@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, 03 Feb 2014 01:28:54 -0000 --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline I have personal documentation and wish to share parts that may be beneficial to other users. Here I have changed so that the user can see how to patch for striping executables on more than one file. Porter's Handbook 5.15.2. Stripping Binaries and Shared Libraries -- Best regards, Rusmir Dusko --k+w/mQv8wyuph6w0 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="book.xml.diff" Index: en_US.ISO8859-1/books/porters-handbook/book.xml =================================================================== --- en_US.ISO8859-1/books/porters-handbook/book.xml (revision 43727) +++ en_US.ISO8859-1/books/porters-handbook/book.xml (working copy) @@ -5135,12 +5135,22 @@ INSTALL_LIB macros, ${STRIP_CMD} will strip your program or shared library. This is typically done within the - post-install target. For - example: + post-install target. + If you need to strip one file, + for example this executable: + post-install: - ${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/xdl + ${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/${PORTNAME} + If you need to strip more than one file, + for example these shared libraries: + + post-install: + .for l in geometry media body track world + ${STRIP_CMD} ${STAGEDIR}${PREFIX}/lib/libvamos-${l}.so.0 + .endfor + Use the &man.file.1; command on the installed executable to check whether the binary is stripped or not. If it does not say not stripped, it is stripped. --k+w/mQv8wyuph6w0-- From owner-freebsd-doc@FreeBSD.ORG Mon Feb 3 04:58:28 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 84BA7822 for ; Mon, 3 Feb 2014 04:58:28 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 331001B06 for ; Mon, 3 Feb 2014 04:58:28 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s134wLDm021226 for ; Sun, 2 Feb 2014 21:58:21 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s134wLRn021223 for ; Sun, 2 Feb 2014 21:58:21 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sun, 2 Feb 2014 21:58:21 -0700 (MST) From: Warren Block To: freebsd-doc@FreeBSD.org Subject: Improving callout lists in HTML (CSS) Message-ID: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3512871622-618177893-1391403501=:19166" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 02 Feb 2014 21:58:21 -0700 (MST) 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, 03 Feb 2014 04:58:28 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --3512871622-618177893-1391403501=:19166 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII The attached patch, created with the help of Allan Jude, tightens up the spacing in HTML callout lists, making them easier to read. After applying it, I did not see any problems with the callout lists in the Handbook. Unless problems are reported, I'll commit it in a day or two. --3512871622-618177893-1391403501=:19166 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=docbook.css-callout.diff Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=docbook.css-callout.diff SW5kZXg6IHNoYXJlL21pc2MvZG9jYm9vay5jc3MNCj09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT0NCi0tLSBzaGFyZS9taXNjL2RvY2Jvb2suY3NzCShyZXZpc2lv biA0MzcyNykNCisrKyBzaGFyZS9taXNjL2RvY2Jvb2suY3NzCSh3b3JraW5n IGNvcHkpDQpAQCAtMTM5LDYgKzEzOSwxNyBAQA0KIAltYXJnaW4tYm90dG9t OiAxZXg7DQogfQ0KIA0KK2JvZHkgLmNhbGxvdXRsaXN0IHRkIHsNCisJcGFk ZGluZy1yaWdodDogMC41ZW07DQorCXdpZHRoOiBhdXRvOw0KK30NCisNCiti b2R5IC5jYWxsb3V0bGlzdCB0ZCBwIHsNCisJbGluZS1oZWlnaHQ6IDEuMjsN CisJbWFyZ2luLXRvcDogNHB4Ow0KKwltYXJnaW4tYm90dG9tOiA0cHg7DQor fQ0KKw0KIGJvZHkgZm9ybSB7DQogCW1hcmdpbjogLjZlbSAwOw0KIH0NCg== --3512871622-618177893-1391403501=:19166-- From owner-freebsd-doc@FreeBSD.ORG Mon Feb 3 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 ACCB7E6E for ; Mon, 3 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 8CF5119CD for ; Mon, 3 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 s13B64Ee021755 for ; Mon, 3 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 s13B64Qf021753 for freebsd-doc@FreeBSD.org; Mon, 3 Feb 2014 11:06:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 3 Feb 2014 11:06:04 GMT Message-Id: <201402031106.s13B64Qf021753@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, 03 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 -------------------------------------------------------------------------------- p docs/186191 doc Typo in bhyveload.8 o docs/185764 doc mention of libiconv in FreeBSD 10.0 release note o docs/185602 doc Possible scsi(4) typo 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/185382 doc missing description in rights(4) man page 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/183650 doc [patch] Remove misleading "kldload" in sem(4) man page 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/157049 doc FreeBSD Handbook: Chapter 14 (Security) Inaccuracy 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 3 19:07:04 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 5CD2911A; Mon, 3 Feb 2014 19:07: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 2E5A7195F; Mon, 3 Feb 2014 19:07: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 s13J74m9041990; Mon, 3 Feb 2014 19:07:04 GMT (envelope-from trhodes@freefall.freebsd.org) Received: (from trhodes@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s13J73WI041989; Mon, 3 Feb 2014 19:07:03 GMT (envelope-from trhodes) Date: Mon, 3 Feb 2014 19:07:03 GMT Message-Id: <201402031907.s13J73WI041989@freefall.freebsd.org> To: trhodes@FreeBSD.org, freebsd-doc@FreeBSD.org, trhodes@FreeBSD.org From: trhodes@FreeBSD.org Subject: Re: docs/157049: FreeBSD Handbook: Chapter 14 (Security) Inaccuracy 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, 03 Feb 2014 19:07:04 -0000 Synopsis: FreeBSD Handbook: Chapter 14 (Security) Inaccuracy Responsible-Changed-From-To: freebsd-doc->trhodes Responsible-Changed-By: trhodes Responsible-Changed-When: Mon Feb 3 19:06:44 UTC 2014 Responsible-Changed-Why: Take this PR. http://www.freebsd.org/cgi/query-pr.cgi?pr=157049 From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 01:14:15 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 C397ECE for ; Tue, 4 Feb 2014 01:14:15 +0000 (UTC) Received: from nm2.access.bullet.mail.gq1.yahoo.com (nm2.access.bullet.mail.gq1.yahoo.com [216.39.62.33]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8349F1BF3 for ; Tue, 4 Feb 2014 01:14:15 +0000 (UTC) Received: from [216.39.60.172] by nm2.access.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2014 01:10:55 -0000 Received: from [216.39.60.242] by tm8.access.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2014 01:10:55 -0000 Received: from [127.0.0.1] by omp1013.access.mail.gq1.yahoo.com with NNFMP; 04 Feb 2014 01:10:55 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 470148.53961.bm@omp1013.access.mail.gq1.yahoo.com Received: (qmail 41010 invoked by uid 60001); 4 Feb 2014 01:10:55 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1391476255; bh=CS7S7OBfeLN/JKuJceLGD5bHnVXgn0h1QKs16HEnZko=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=taLIU8Um4eK8Ooc//MWx+iJ2FcURgyjTLx5DD+yxgyTWTZ5lKugfrzjhEJfExjtcxYW6H7PGgdm2Z+ZIs++6bV9Ot1/rAqhUw08/CtOxADLoIld1wdMh/zjGUZ3LqlMTe+8G3hOrsZTkLOMdxuY8HSHAteB7k3PMlh+gAh7pSBI= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=att.net; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=hA4nu3hllXSSOYDXKMQW6x4/1PmldLdIkZcCduQl+pShZ7fVuQQSq5axFJv2StW+MoDaG6NUn6b0I4OzJdadS7CtMqp/iIECcFJ/Cc7uvT7ckgPq4wvBNn6oE2GqTnAIZ32dQkd1CUcO/AoDb3R11T773Z0pvrjasmEKy8FzVcs=; X-YMail-OSG: qDGyOFEVM1nuCRNjXy2eOEni5zJ3ZRBFPZY8vB93V1seVOO j0UFyXSUsAWO8UY3CJEEM7RnMUddq8O2WUp83JHthMafaZW88iw2rgThOAd5 kn_LRm_Jjnb14lKl6H2ZTwDfl_8yXmhJKSiL2Ox_9gh78LAkN18U_.wrRh2I iHp_THmD9zLAwqE7khBWjWXJlESQKUmEWl3oRRU_FFs63.J1YgvxGaTfkgG9 XmgKey4u0P7Qxevwq56D.Is1r6kCY1xboyyoM3bZPbuIMcD5E1fHZPJIvgc. ft0tKp40y4uOLwvoDyA.zxUKV66AqVPDFGm_nSTcxiqvF5dJjKxqE6q4l7yM ZHHTY1iEscKstRYJSSVcLbTmDErTiOelfGsZBIGB3x2ISlafCToVVPYkpY09 mkDvrNc0xrtulEpjBGfbYJUKzp6smfPddf8GQVolBv1PawaH1ynZqOnIrtFt mx5MfwIQIQH4HV6JeGP3rBMeREucLXVNjLUFmh6xmbIWpCNBdUzGLY9nANyD 9RfQOVv.gisxwLpXmag-- Received: from [99.98.83.69] by web184905.mail.gq1.yahoo.com via HTTP; Mon, 03 Feb 2014 17:10:55 PST X-Rocket-MIMEInfo: 002.001, Q3VycmVudGx5LCB0aGVyZSBhcmUgMiBIYW5kYm9vayBzZWN0aW9ucyB0aGF0IGRlYWwgd2l0aCB1cGdyYWRpbmcgcG9ydHM6Cgo1LjYuMy4gVXBncmFkaW5nIFBvcnRzwqAgKHdoaWNoIGRlc2NyaWJlcyB0aGUgdXNlIG9mIHRoZSBwb3J0bWFzdGVyIGFuZCBwb3J0dXBncmFkZSBwb3J0cykKCmFuZAoKMjMuMy4gUG9ydHNuYXA6IGEgUG9ydHMgQ29sbGVjdGlvbiBVcGRhdGUgVG9vbCAod2hpY2ggZGVzY3JpYmVzIHRoZSBidWlsdC1pbiBwb3J0c25hcCkKCkkgd291bGQgbGlrZSB0byBjb21iaW5lIHRoZXNlIGkBMAEBAQE- X-Mailer: YahooMailWebService/0.8.174.629 Message-ID: <1391476255.71576.YahooMailNeo@web184905.mail.gq1.yahoo.com> Date: Mon, 3 Feb 2014 17:10:55 -0800 (PST) From: Dru Lavigne Subject: updating ports To: "freebsd-doc@freebsd.org" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 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 Reply-To: Dru Lavigne List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 01:14:15 -0000 Currently, there are 2 Handbook sections that deal with upgrading ports:=0A= =0A5.6.3. Upgrading Ports=A0 (which describes the use of the portmaster and= portupgrade ports)=0A=0Aand=0A=0A23.3. Portsnap: a Ports Collection Update= Tool (which describes the built-in portsnap)=0A=0AI would like to combine = these into 5.6.3.=0A=0ADo we want to encourage the use of third-party utils= or just encourage the use of the built in one?=0A=0AIf just the built in o= ne, I'll replace 5.6.3 with the contents of 23.3 and reduce portmaster/port= upgrade to a note that these utils are available in the ports collection.= =0A=0AIf we should describe all three, I'll place 23.3 as the first utility= to be described in 5.6.3.=0A=0ACheers,=0A=0ADru From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 01:20:11 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 3A859179; Tue, 4 Feb 2014 01:20:11 +0000 (UTC) Received: from mail0.glenbarber.us (mail0.glenbarber.us [IPv6:2607:fc50:1:2300:1001:1001:1001:face]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 0D1551C26; Tue, 4 Feb 2014 01:20:11 +0000 (UTC) Received: from glenbarber.us (nucleus.glenbarber.us [IPv6:2001:470:8:1205:2:2:ff:100]) (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 4EC0719D4F; Tue, 4 Feb 2014 01:20:09 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.8.3 mail0.glenbarber.us 4EC0719D4F Authentication-Results: mail0.glenbarber.us; dkim=none reason="no signature"; dkim-adsp=none Date: Mon, 3 Feb 2014 20:20:07 -0500 From: Glen Barber To: Dru Lavigne Subject: Re: updating ports Message-ID: <20140204012007.GZ1766@glenbarber.us> References: <1391476255.71576.YahooMailNeo@web184905.mail.gq1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="tArtifyz9D3PkaxN" Content-Disposition: inline In-Reply-To: <1391476255.71576.YahooMailNeo@web184905.mail.gq1.yahoo.com> X-Operating-System: FreeBSD 11.0-CURRENT amd64 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 List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 01:20:11 -0000 --tArtifyz9D3PkaxN Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Feb 03, 2014 at 05:10:55PM -0800, Dru Lavigne wrote: > Currently, there are 2 Handbook sections that deal with upgrading ports: >=20 > 5.6.3. Upgrading Ports=A0 (which describes the use of the portmaster and = portupgrade ports) >=20 > and >=20 > 23.3. Portsnap: a Ports Collection Update Tool (which describes the built= -in portsnap) >=20 > I would like to combine these into 5.6.3. >=20 > Do we want to encourage the use of third-party utils or just encourage th= e use of the built in one? >=20 I think there are two separate topics here (without having looked at the Handbook sections yet). I don't think portmaster and portupgrade actually handle updating the ports tree itself, but handle upgrading/rebuilding ports within the ports tree. Portsnap, on the other hand, does not actually touch the software installed (meaning, it does not update the installed third-party software), but only handles updating the ports tree sources themselves. > If just the built in one, I'll replace 5.6.3 with the contents of 23.3 an= d reduce portmaster/portupgrade to a note that these utils are available in= the ports collection. >=20 > If we should describe all three, I'll place 23.3 as the first utility to = be described in 5.6.3. >=20 Glen --tArtifyz9D3PkaxN Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQIcBAEBCAAGBQJS8EBGAAoJELls3eqvi17QlYEP/0xyJlkLHJiazrozn+95hudo UIEn2ecQXVITFW0c+DNHz2Z6Rd1GzD2m8c3TjsNhaUeioGYqRxApkvpIvpkJh25n Vizf4f1QQAcs1xyuYzQINFCS0PPk4nWOB955dqbn2e4FhWhBKerwyqWjOoE0Pj/O P4/R2tNs9phW+8wqDdHsaX0KoRnqyaXjTcoEKUsH6X4yy8ZHy6YjmOB+ylzG/Vs9 5d56uMlSU4OrSMfx4hdPpPRWJt0YBxoM7AaO32QLwQ6uG+Ntlp24s9xNDkB0YeYr cwT50E+mSPDvZakgYgSUh7vN/k1UWqTa6qmY0902NV5GAUu6cMG+N2dFnS2qK2Ll PS+5RD5huAKEAC1LR2qtfHip7ZqsJHyDoxaDcFnHC4sBOcjcynjCfh3BxOrR449N EhiXNNbs5RvRL5y/Si8wLMwvFXixydlBvHUL45cQe+p7FObA3Gf1EFssEk9Su9aY lbHdgSJr08oImuayt0EFvn6RQj7tvULybuGoelgwJXCFLjZdJHH//NoUEZFP2e8H GL5rasRitRCe/sulkVi1JBChYVDDNEMsYMQz03UFyhni+mWY9H53CnSb2PFxEF8/ LhD/wB6ozv9EStIyMv9U8lF2+EYZ8m0bKaRb5cuiafoWIfpgJpbHUlp3YLT3FwVH qGXE1PVGPodpwERRsncn =CCdH -----END PGP SIGNATURE----- --tArtifyz9D3PkaxN-- From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 01:22:04 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 7DCF21D8 for ; Tue, 4 Feb 2014 01:22:04 +0000 (UTC) Received: from nm23-vm4.access.bullet.mail.gq1.yahoo.com (nm23-vm4.access.bullet.mail.gq1.yahoo.com [216.39.63.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 424F01C8E for ; Tue, 4 Feb 2014 01:22:03 +0000 (UTC) Received: from [216.39.60.169] by nm23.access.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2014 01:19:00 -0000 Received: from [216.39.60.248] by tm5.access.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2014 01:19:00 -0000 Received: from [127.0.0.1] by omp1019.access.mail.gq1.yahoo.com with NNFMP; 04 Feb 2014 01:19:00 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 808418.69994.bm@omp1019.access.mail.gq1.yahoo.com Received: (qmail 64617 invoked by uid 60001); 4 Feb 2014 01:19:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1391476740; bh=Eqqc51BQD31vquKHuwJrEXp9aRbhiP1wD+NkjVv2Cwo=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=0g+6MjG+1tNbALix8n+a+ECP9d+a+LGW14wqlUxavofBAhmN/mFmb4EjJy+SsPOQYNk3bn7IjEBfcu4CBZt4nPBGkDNgC6BGmke2NHEiKxQGePdJnJnWQT8uVdtofhTtPEgHWLNIoT5sYtHujzVsa4cVGHmHXz5+N0pK9uveLS0= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=att.net; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:Message-ID:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=TSk+bMteFDQIfUshVdRKonxObUmZQ1drTVcG1APFILKMe/gtwycmzmpyMEBFOAl9KcbvCMRdIlRPpylJIcv/ZfHqAdJdnYO5GnchIM6rKCVz7FzRlAMvbTAByYAQQiQoySOkEyakqwn/TtsPfsYjsf7FIn+Hpb+Xq9MqLbmCIQE=; X-YMail-OSG: .0nP4OgVM1nwODZHjdzoGiCK_IQB.kTV519f0yt3qpgbXwS CtR0k9b4mYVAx01hl2jt2LKYyY1wNUjdEi7q4gdXhpi.uR3ob_Krw_wYxB8s zsbdNNLCNY5.62bHjwMw.vqDbA1yvcT6JLQHueZCUFez_ZgDB03M1gME_zn. zWDaHjuFyjproMZUbnWVAyvjG4shflMmuuPOF_BK8Z6Vh0.jNHif7_Bt3RZL _ce9R_3Tv6POt7Pu2Wnfxc1vQC2pHEJ1OqOvM3aN5Dor18TLsuqol4twIvnI eqWgca6fAPAprnrwb4Vy.EFnHlKGEfGZgLZ_Oh39LVWTmBTtarJnMLmOudHv C083ZTXo_UXo1jaRY9Ly6CfbtKNFc.8k._DNMGx4JfhlUrmZIf4al__J2P_6 BJkaoOG.BgK9VM1fwDXDajQbiW2bghlLJvYjrpBzk6FqcEkrZ2yZAR_pfiKs RmEayEqkkcFmbcsmEOqnu2.gvceZqLiH8MfP8WAEIFem46EYKCPlDbNRcz8V XXbC1q..1CJGSj6IgPNwZb.Gq7Tr2gBzXC1kfpNfFKBsoHo3YE9R3IwJ1D9x KtkPOWhK2W8gr6QEiyD1mmn.Ij8kZZoyb2D0qlZYGkKDrjVxdCjanjv.IONs TNNPaDWF3_1hmdVcQXvwaUCocIToq7N.AzIO.VXcM9XKQU2N3D.Z9clmTv3j 0VQ-- Received: from [99.98.83.69] by web184904.mail.gq1.yahoo.com via HTTP; Mon, 03 Feb 2014 17:19:00 PST X-Rocket-MIMEInfo: 002.001, VGhpcyBzZWN0aW9uOgoKMjMuNC4gVXBkYXRpbmcgdGhlIERvY3VtZW50YXRpb24gU2V0CgpyZWFsbHkgYmVsb25ncyAoYW5kIGlzIGFscmVhZHkgbW9zdGx5IGR1cGxpY2F0ZWQgaW4pOgoKaHR0cDovL3d3dy5mcmVlYnNkLm9yZy9kb2MvZW5fVVMuSVNPODg1OS0xL2Jvb2tzL2ZkcC1wcmltZXIvb3ZlcnZpZXcuaHRtbCNvdmVydmlldy1kb2MKCkFueSBvYmplY3Rpb25zIHRvIG1lIGRvaW5nIHRoZSBmb2xsb3dpbmc_CgoxLiByZW1vdmUgIjIzLjQuIFVwZGF0aW5nIHRoZSBEb2N1bWVudGF0aW9uIFNldCIgZnIBMAEBAQE- X-Mailer: YahooMailWebService/0.8.174.629 Message-ID: <1391476740.64494.YahooMailNeo@web184904.mail.gq1.yahoo.com> Date: Mon, 3 Feb 2014 17:19:00 -0800 (PST) From: Dru Lavigne Subject: updating documentation set To: "freebsd-doc@freebsd.org" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: Dru Lavigne List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 01:22:04 -0000 This section: 23.4. Updating the Documentation Set really belongs (and is already mostly duplicated in): http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview.html#overview-doc Any objections to me doing the following? 1. remove "23.4. Updating the Documentation Set" from the Handbook, replacing it with a NOTE in the updating section that docs can either be updated during an OS upgrade or, at any other time, by following the instructions in the FDP overview (with link) 2. make sure that any points covered by 23.4 and currently missing from the FDP overview are added to the FDP overview Cheers, Dru From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 01:24:44 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 5B2CC3C5 for ; Tue, 4 Feb 2014 01:24:44 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 337DD1CA2 for ; Tue, 4 Feb 2014 01:24:43 +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 40845576E9 for ; Tue, 4 Feb 2014 01:24:37 +0000 (UTC) Message-ID: <52F04152.5020202@allanjude.com> Date: Mon, 03 Feb 2014 20:24:34 -0500 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-doc@freebsd.org Subject: Re: updating ports References: <1391476255.71576.YahooMailNeo@web184905.mail.gq1.yahoo.com> <20140204012007.GZ1766@glenbarber.us> In-Reply-To: <20140204012007.GZ1766@glenbarber.us> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C03hliDPIDQq4P5ldqiX2guSHOJPiMSV3" 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, 04 Feb 2014 01:24:44 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --C03hliDPIDQq4P5ldqiX2guSHOJPiMSV3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2014-02-03 20:20, Glen Barber wrote: > On Mon, Feb 03, 2014 at 05:10:55PM -0800, Dru Lavigne wrote: >> Currently, there are 2 Handbook sections that deal with upgrading port= s: >> >> 5.6.3. Upgrading Ports (which describes the use of the portmaster and= portupgrade ports) >> >> and >> >> 23.3. Portsnap: a Ports Collection Update Tool (which describes the bu= ilt-in portsnap) >> >> I would like to combine these into 5.6.3. >> >> Do we want to encourage the use of third-party utils or just encourage= the use of the built in one? >> > I think there are two separate topics here (without having looked at th= e > Handbook sections yet). I don't think portmaster and portupgrade > actually handle updating the ports tree itself, but handle > upgrading/rebuilding ports within the ports tree. > > Portsnap, on the other hand, does not actually touch the software > installed (meaning, it does not update the installed third-party > software), but only handles updating the ports tree sources themselves.= > >> If just the built in one, I'll replace 5.6.3 with the contents of 23.3= and reduce portmaster/portupgrade to a note that these utils are availab= le in the ports collection. >> >> If we should describe all three, I'll place 23.3 as the first utility = to be described in 5.6.3. >> > Glen > A section that discusses portmaster should probably talk about the similar functionality that is now 'pkg upgrade', which wasn't possible with the pkg_* tools --=20 Allan Jude --C03hliDPIDQq4P5ldqiX2guSHOJPiMSV3 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/ iQIcBAEBAgAGBQJS8EFWAAoJEJrBFpNRJZKf2LIQALIvkZuw0i53NEl8JkkcgdXH jfOzuZ81QZsYxQefbrGrho6za8NoEUZSZgS4kdtCwP5bhf+SDeFZBnV4pknITrgG CAPn+UiGzanqntH5Da044xI45V0oI2T7FpcldH1BArxo6sdFBJAtrIdH+r7mCNNm Nd3fgsZzd87FOiQf5iMirYM85I1KW6ttZqU1t1JxNhXzRPnjg+e3aRA+2VC/QzHM dA898XbOOCVAo5fo4YSXb0jmy7dR3A1LIfUHEn0fLhVolekF3QxgClvNAbVDcXeC Iap2L8S7AiUto+voCgg20USWdbzrIB2dyxsPnZM/CzzbJdQ8MdJnRIMLyguqgZlO KrEHVDOA/z89BA/I7RjWCV23prWZWFuq/Qg7aAMIZNOPhKdihSZPMxm1ylc3GhJM gCLGnNooNtXZnIC4eOREL0dvdGI4jz9g9cVaRxTWrC01DN55X6UaeBqgG+7XpbIT KznaEX7rr0f4PIDwQKdyVKvp7oz+YTy92Su/bnwlS3zbIGP63OtH6XjldvzRYLG8 VDJ8FtxUadxdbdjKpu9NYClvfK5NQfCtEEBn8rth4UYtx1OwJ+TxkNp4zEAiroFD oK5BSuu7IuCP8FnMDyTOjQox5iEQ55x4VCTp2Mo8C5fFp7K2QniDuHgfx4AEPbWC KWdwe8MGzaST03SYDt4t =ePwc -----END PGP SIGNATURE----- --C03hliDPIDQq4P5ldqiX2guSHOJPiMSV3-- From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 01:25:26 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 11835410 for ; Tue, 4 Feb 2014 01:25:26 +0000 (UTC) Received: from nm23-vm4.access.bullet.mail.gq1.yahoo.com (nm23-vm4.access.bullet.mail.gq1.yahoo.com [216.39.63.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C39E51CA9 for ; Tue, 4 Feb 2014 01:25:25 +0000 (UTC) Received: from [216.39.60.174] by nm23.access.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2014 01:25:25 -0000 Received: from [216.39.60.245] by tm10.access.bullet.mail.gq1.yahoo.com with NNFMP; 04 Feb 2014 01:25:25 -0000 Received: from [127.0.0.1] by omp1016.access.mail.gq1.yahoo.com with NNFMP; 04 Feb 2014 01:25:25 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 215661.7093.bm@omp1016.access.mail.gq1.yahoo.com Received: (qmail 43659 invoked by uid 60001); 4 Feb 2014 01:25:25 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1391477125; bh=qpQV7Nd5PF6KqPczfL4BKrZ3RhLdqMY9K46GlnHa9EY=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=pp4q/VoKgj3NB3ZFaV2mxJKbDyfHUzafpqV1S6IJjcsJhJG/aqVljAoRtpYz5FcfRhBgCNkhaHfSzpEQcGoYk65VqtsXKMR5PF8U7AOPGHXKm76fSDpVKiUWTaEu+YojdYCuIx1tFN3b9dcloqDTN0vZPkpNpbpLS4PHoH2HHSw= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=att.net; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=CbcH6oLMZGOJuUlWFwNHJgBqJxsIKszvzdIA6Piac9Ro80URdYSq8iNpDyQVomOIAu7wKoG/n80xzkCKsvTXuvA/UCAiPZP6KeewbWJtDatxufFlckM0+pc4cIsjkz0tp1TjpElXszjZrpGuPCyY7F3SGQnk/YU6H/0YHO/iGkk=; X-YMail-OSG: 2zHteHQVM1l4gQauJdC2QmUecHp0ji.DXFwIUTqpohpp5bc zpabnZdsZxEvYJ9xnnVmdWiRRDkq5jI1.v0oZ_Gfu1z8k3ZtdgUh87xC6GLs 4KmpAp1Dc8mOFYEWThDU8MQAxNEpzakXmEpibPnZfz..BeTAoZrXjJQQPqZI uWhZct0dF8kBN7qkjTw7rDxuwm7y62n94AFrc2CvdNeN37xi6yXuX7wmuEQj GEJI_NXRHO2RQrD1Q1ENAY6iimFaZM6.BIkJbCeaHke9VjAA3bCOVtxXROjm 8tSzJUkHA9PQ3K8YB5iM7cegGLG_Hv5sKwU0qO0VYN7mpObBkPiq.M8Br2.U dSZAewxnsmQEBwEYVHTpsu7bgvX77zns39544zR09s88oxYoX6_XGG_ZU4xX 3DZONa5wiCw7M9RFHX4ikU4L5k0bJsrZq7Ecjj2XWXFgOEau8gCM7xz93jrl fJ_eQMZgjxXPUoofo6Ul4pK6htDvEcgZpybufjclUxikUUAiq8M8DGX7ImTe lBIheJhG1fdWjCSBB_UuMHiThvpnJuSmH5sRnz0NyeGQ6DpqgSo6PQg46xZZ X Received: from [99.98.83.69] by web184906.mail.gq1.yahoo.com via HTTP; Mon, 03 Feb 2014 17:25:25 PST X-Rocket-MIMEInfo: 002.001, Cgo.PiBDdXJyZW50bHksIHRoZXJlIGFyZSAyIEhhbmRib29rIHNlY3Rpb25zIHRoYXQgZGVhbCB3aXRoIHVwZ3JhZGluZyBwb3J0czoKPj4gCj4.IDUuNi4zLiBVcGdyYWRpbmcgUG9ydHPCoCAod2hpY2ggZGVzY3JpYmVzIHRoZSB1c2Ugb2YgdGhlIHBvcnRtYXN0ZXIgYW5kIHBvcnR1cGdyYWRlIHBvcnRzKQo.PiAKPj4gYW5kCj4.IAo.PiAyMy4zLiBQb3J0c25hcDogYSBQb3J0cyBDb2xsZWN0aW9uIFVwZGF0ZSBUb29sICh3aGljaCBkZXNjcmliZXMgdGhlIGJ1aWx0LWluIHBvcnRzbmFwKQo.PiAKPj4gSSABMAEBAQE- X-Mailer: YahooMailWebService/0.8.174.629 References: <1391476255.71576.YahooMailNeo@web184905.mail.gq1.yahoo.com> <20140204012007.GZ1766@glenbarber.us> Message-ID: <1391477125.13219.YahooMailNeo@web184906.mail.gq1.yahoo.com> Date: Mon, 3 Feb 2014 17:25:25 -0800 (PST) From: Dru Lavigne Subject: Re: updating ports To: Glen Barber In-Reply-To: <20140204012007.GZ1766@glenbarber.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: "freebsd-doc@freebsd.org" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Dru Lavigne List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Feb 2014 01:25:26 -0000 =0A=0A>> Currently, there are 2 Handbook sections that deal with upgrading = ports:=0A>> =0A>> 5.6.3. Upgrading Ports=A0 (which describes the use of the= portmaster and portupgrade ports)=0A>> =0A>> and=0A>> =0A>> 23.3. Portsnap= : a Ports Collection Update Tool (which describes the built-in portsnap)=0A= >> =0A>> I would like to combine these into 5.6.3.=0A>> =0A>> Do we want to= encourage the use of third-party utils or just encourage the use of the bu= ilt in one?=0A>> =0A>=0A>I think there are two separate topics here (withou= t having looked at the=0A>Handbook sections yet).=A0 I don't think portmast= er and portupgrade=0A>actually handle updating the ports tree itself, but h= andle=0A>upgrading/rebuilding ports within the ports tree.=0A>=0A>Portsnap,= on the other hand, does not actually touch the software=0A>installed (mean= ing, it does not update the installed third-party=0A>software), but only ha= ndles updating the ports tree sources themselves.=0A>=0A>> If just the buil= t in one, I'll replace 5.6.3 with the contents of 23.3 and reduce portmaste= r/portupgrade to a note that these utils are available in the ports collect= ion.=0A>> =0A>> If we should describe all three, I'll place 23.3 as the fir= st utility to be described in 5.6.3.=0A=0A=0A=0AGood catch...and I see that= portsnap is already covered in Procedure 5.1 of section 5.6. I'll submit a= patch some time this week.=0A=0ACheers,=0A=0ADru=0A From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 03:01:03 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 B2D19B77; Tue, 4 Feb 2014 03:01:03 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 62207157C; Tue, 4 Feb 2014 03:01:03 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s14311Tl031648; Mon, 3 Feb 2014 20:01:01 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s14311Ar031645; Mon, 3 Feb 2014 20:01:01 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 3 Feb 2014 20:01:01 -0700 (MST) From: Warren Block To: Dru Lavigne Subject: Re: updating documentation set In-Reply-To: <1391476740.64494.YahooMailNeo@web184904.mail.gq1.yahoo.com> Message-ID: References: <1391476740.64494.YahooMailNeo@web184904.mail.gq1.yahoo.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]); Mon, 03 Feb 2014 20:01:01 -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: Tue, 04 Feb 2014 03:01:03 -0000 On Mon, 3 Feb 2014, Dru Lavigne wrote: > This section: > > 23.4. Updating the Documentation Set > > really belongs (and is already mostly duplicated in): > > http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview.html#overview-doc > > Any objections to me doing the following? > > 1. remove "23.4. Updating the Documentation Set" from the Handbook, replacing it with a NOTE in the updating section that docs can either be updated during an OS upgrade or, at any other time, by following the instructions in the FDP overview (with link) > > > 2. make sure that any points covered by 23.4 and currently missing from the FDP overview are added to the FDP overview Don't we have doc ports specifically for users to keep a current version of the documentation on their system? Upgrading a port is simpler for an end user than an svn checkout, there's less overhead, and we would not have to expose them to developer instructions. From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 03:36:23 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 D3425AC8 for ; Tue, 4 Feb 2014 03:36:23 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 899101B60 for ; Tue, 4 Feb 2014 03:36:23 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s143aMGr031917 for ; Mon, 3 Feb 2014 20:36:22 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s143aMIM031914 for ; Mon, 3 Feb 2014 20:36:22 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 3 Feb 2014 20:36:22 -0700 (MST) From: Warren Block To: freebsd-doc@FreeBSD.org Subject: Re: Improving callout lists in HTML (CSS) In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Mon, 03 Feb 2014 20:36:22 -0700 (MST) 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, 04 Feb 2014 03:36:23 -0000 On Sun, 2 Feb 2014, Warren Block wrote: > The attached patch, created with the help of Allan Jude, tightens up the > spacing in HTML callout lists, making them easier to read. > > After applying it, I did not see any problems with the callout lists in the > Handbook. > > Unless problems are reported, I'll commit it in a day or two. It's been pointed out that there were few specifics and no example of what this patch does, so here is one: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/network-wireless.html#co-tls-ssid Look at the callout list after the programlisting. The numbers on the left are far from the descriptions, and there is a lot of vertical space between the entries. Building the Handbook copies doc/share/misc/docbook.css into the Handbook directory. So patch the original, do a 'make clean' for the Handbook, then refresh the browser to view the new version. From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 03:51:22 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 53B87A9 for ; Tue, 4 Feb 2014 03:51:22 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 00B371C39 for ; Tue, 4 Feb 2014 03:51:21 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s143pKGX031986 for ; Mon, 3 Feb 2014 20:51:20 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s143pKR7031983 for ; Mon, 3 Feb 2014 20:51:20 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 3 Feb 2014 20:51:20 -0700 (MST) From: Warren Block To: freebsd-doc@FreeBSD.org Subject: Re: Improving callout lists in HTML (CSS) In-Reply-To: Message-ID: References: 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]); Mon, 03 Feb 2014 20:51:20 -0700 (MST) 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, 04 Feb 2014 03:51:22 -0000 On Mon, 3 Feb 2014, Warren Block wrote: > Building the Handbook copies doc/share/misc/docbook.css into the Handbook > directory. So patch the original, do a 'make clean' for the Handbook, then > refresh the browser to view the new version. Which assumes you are looking at a local copy rather than the real thing shown at the link posted earlier. Presumably your local link would be more like file:///usr/doc/en_US.ISO8859-1/books/handbook/book.html#co-tls-ssid From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 08:16:39 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 0E19948C; Tue, 4 Feb 2014 08:16:39 +0000 (UTC) Received: from chilled.skew.org (chilled.skew.org [70.90.116.205]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CFAC01FC3; Tue, 4 Feb 2014 08:16:38 +0000 (UTC) Received: from chilled.skew.org (localhost [127.0.0.1]) by chilled.skew.org (8.14.7/8.14.7) with ESMTP id s1480glR006991 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 4 Feb 2014 01:00:42 -0700 (MST) (envelope-from mike@chilled.skew.org) Received: (from mike@localhost) by chilled.skew.org (8.14.7/8.14.7/Submit) id s1480fXU006990; Tue, 4 Feb 2014 01:00:41 -0700 (MST) (envelope-from mike) From: Mike Brown Message-Id: <201402040800.s1480fXU006990@chilled.skew.org> Subject: Re: Patch (WIP): New security front matter; new shell redirection section In-Reply-To: <20140202175121.16a0c264.trhodes@FreeBSD.org> To: Tom Rhodes Date: Tue, 4 Feb 2014 01:00:41 -0700 (MST) X-Whoa: whoa. X-Mailer: ELM [version 2.4ME+ PL126 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="UTF-8" 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, 04 Feb 2014 08:16:39 -0000 Tom Rhodes wrote: > + Passwords are a necessary evil of the past. In the cases > + they must be used, not only should the password be extremely > + complex, but also use a powerful hash mechanism to protect it. > + At the time of this writing, &os; supports > + DES, MD5, Blowfish, > + SHA256, and SHA512 in > + the crypt() library. The default is > + SHA512 and should not be changed backwards; > + however, some users like to use the Blowfish option. Each > + mechanism, aside from DES, has a unique > + beginning to designate the hash mechanism assigned. For the > + MD5 mechanism, the symbol is a > + $ sign. For the SHA256 or > + SHA512, the symbol is $6$ > + and Blowfish uses $2a$. Any weaker passwords > + should be re-hashed by asking the user to run &man.passwd.1; > + during their next login. I get confused by this. "Any weaker passwords" immediately follows discussion of hash mechanisms, suggesting you actually mean to say "Any passwords protected by weaker hash mechanisms" ... although maybe you were done talking about hash mechanisms and were actually now back to talking about password complexity? Please clarify. Either way, how do I inspect /etc/spwd.db to find out who has weak/not-complex-enough passwords, and what hash mechanism is in use for each user, so I know who needs to run passwd(1)? If this info is already in the chapter, forgive me; I am just going by what's in the diff. Anyway, overall it looks great. From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 09:10:34 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 E9F63902; Tue, 4 Feb 2014 09:10:34 +0000 (UTC) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) (using TLSv1 with cipher ADH-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9B72814E5; Tue, 4 Feb 2014 09:10:33 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id 6017814D2537; Tue, 4 Feb 2014 10:10:17 +0100 (CET) X-Virus-Scanned: amavisd-new at !change-mydomain-variable!.example.com Received: from server.mypc.hu ([127.0.0.1]) by server.mypc.hu (server.mypc.hu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 2N0qLzPZ67Wq; Tue, 4 Feb 2014 10:10:16 +0100 (CET) Received: from [192.168.0.10] (54034B4D.catv.pool.telekom.hu [84.3.75.77]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id D0E0F14D2536; Tue, 4 Feb 2014 10:10:16 +0100 (CET) Message-ID: <52F0AE74.4090502@kovesdan.org> Date: Tue, 04 Feb 2014 10:10:12 +0100 From: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: Warren Block Subject: Re: updating documentation set References: <1391476740.64494.YahooMailNeo@web184904.mail.gq1.yahoo.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Dru Lavigne , "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, 04 Feb 2014 09:10:35 -0000 On 2014.02.04. 4:01, Warren Block wrote: > On Mon, 3 Feb 2014, Dru Lavigne wrote: > >> This section: >> >> 23.4. Updating the Documentation Set >> >> really belongs (and is already mostly duplicated in): >> >> http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview.html#overview-doc >> >> >> Any objections to me doing the following? >> >> 1. remove "23.4. Updating the Documentation Set" from the Handbook, >> replacing it with a NOTE in the updating section that docs can either >> be updated during an OS upgrade or, at any other time, by following >> the instructions in the FDP overview (with link) >> >> >> 2. make sure that any points covered by 23.4 and currently missing >> from the FDP overview are added to the FDP overview > > Don't we have doc ports specifically for users to keep a current > version of the documentation on their system? Upgrading a port is > simpler for an end user than an svn checkout, there's less overhead, > and we would not have to expose them to developer instructions. I also think that should be still documented in the Handbook. It is a relevant information from an end-user perspective how to obtain the already rendered versions of other kind of documentation. And imo, it should be treated in the introduction or somewhere in the beginning. Gabor From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 09:22:52 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 84BF3E44 for ; Tue, 4 Feb 2014 09:22:52 +0000 (UTC) Received: from smtpq1.tb.mail.iss.as9143.net (smtpq1.tb.mail.iss.as9143.net [212.54.42.164]) by mx1.freebsd.org (Postfix) with ESMTP id 4374315F5 for ; Tue, 4 Feb 2014 09:22:51 +0000 (UTC) Received: from [212.54.42.134] (helo=smtp3.tb.mail.iss.as9143.net) by smtpq1.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1WAbxf-00084c-EZ for freebsd-doc@FreeBSD.org; Tue, 04 Feb 2014 10:06:31 +0100 Received: from d57de66d.static.ziggozakelijk.nl ([213.125.230.109] helo=mail.tervoorde.net) by smtp3.tb.mail.iss.as9143.net with esmtp (Exim 4.71) (envelope-from ) id 1WAbxf-00042D-67 for freebsd-doc@FreeBSD.org; Tue, 04 Feb 2014 10:06:31 +0100 Received: from mail.tervoorde.net (unknown [172.16.1.49]) by mail.tervoorde.net (Postfix) with ESMTPSA id E49DA32DB9D for ; Tue, 4 Feb 2014 10:07:31 +0100 (CET) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Date: Tue, 04 Feb 2014 10:07:31 +0100 From: "Voorde ter, Frank" To: freebsd-doc@FreeBSD.org Subject: Error in Handbook (7.2.4.2. Chromium and =?UTF-8?Q?Adobe=C2=AE=20?= =?UTF-8?Q?Flash=C2=AE=20Plugin=29?= Message-ID: X-Sender: frank@tervoorde.net User-Agent: Roundcube Webmail/RCMAIL_VERSION Content-Transfer-Encoding: quoted-printable X-Ziggo-spambar: -- X-Ziggo-spamscore: -2.9 X-Ziggo-spamreport: ALL_TRUSTED=-1,BAYES_00=-1.9 X-Ziggo-Spam-Status: No X-Spam-Status: No X-Spam-Flag: No 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, 04 Feb 2014 09:22:52 -0000 Good morning, afternoon or night, On https://www.freebsd.org/doc/handbook/desktop-browsers.html, at=20 7.2.4.2. Chromium and Adobe=C2=AE Flash=C2=AE Plugin, the following sente= nce can=20 be read: (...) is similar to the the instructions in Section 7.2.1.1, =E2=80=9CFir= efox=20 and Java=E2=84=A2 Plugin=E2=80=9D. I think this is obviously incorrect, due to a copy-and-paste error. I=20 think it must be: (...) is similar to the the instructions in Section 7.2.1.2, =E2=80=9CFir= efox=20 and Adobe=C2=AE Flash=C2=AE Plugin=E2=80=9D. I hope this helps to make the Handbook closer to perfect. Yours sincerely, Frank ter Voorde From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 10:24:59 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 1A6CB359 for ; Tue, 4 Feb 2014 10:24:59 +0000 (UTC) Received: from boomer.ukrhub.net (boomer.ukrhub.net [94.125.121.14]) by mx1.freebsd.org (Postfix) with ESMTP id 523FF1AE7 for ; Tue, 4 Feb 2014 10:24:57 +0000 (UTC) Received: by boomer.ukrhub.net (Postfix, from userid 58) id A0D2224DC66; Tue, 4 Feb 2014 12:16:06 +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 5F19024DC61 for ; Tue, 4 Feb 2014 12:16:04 +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 s14AG4Al085062 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for ; Tue, 4 Feb 2014 12:16:04 +0200 (EET) (envelope-from ds@ukrhub.net) Received: (from ds@localhost) by gamma.ukrhub.net (8.14.7/8.14.7/Submit) id s14AG4Si085061 for freebsd-doc@freebsd.org; Tue, 4 Feb 2014 12:16:04 +0200 (EET) (envelope-from ds@ukrhub.net) Date: Tue, 4 Feb 2014 12:16:04 +0200 From: Taras Korenko To: freebsd-doc@freebsd.org Subject: en/handbook/kernelconfig: proposed corrections Message-ID: <20140204101604.GC83803@gamma.ukrhub.net> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="NzB8fVQJ5HfG6fxh" Content-Disposition: inline User-Agent: Mutt/1.5.22 (2013-10-16) 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, 04 Feb 2014 10:24:59 -0000 --NzB8fVQJ5HfG6fxh Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Good morning, doc@ folks. The following notes were made while working on russian translation of kernelconfig chapter. I hope some parts of the following diff might be useful. So, could anyone review that diff? -- WBR, Taras Korenko --NzB8fVQJ5HfG6fxh Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="00.en.hb.kc.diff" Index: en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml =================================================================== --- en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml (revision 43745) +++ en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml (working copy) @@ -204,8 +204,8 @@ &man.pciconf.8;, which provides more verbose output. For example: - pciconf -lv - ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00 + &prompt.user; pciconf -lv +ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212 Atheros AR5212 802.11abg wireless' class = network @@ -226,7 +226,7 @@ ath_hal(4) - Atheros Hardware Access Layer (HAL) Once the hardware inventory list is created, refer to it - to ensure that installed hardware is not removed as you edit the custom + to ensure that drivers for installed hardware are not removed as you edit the custom kernel configuration file. @@ -250,11 +250,7 @@ If /usr/src/ does not exist or it is empty, source has not been installed. Source can be installed using - svn, which is described in , or by installing the - src distribution using &man.sysinstall.8;. This - distribution can be selected by navigating to the - Configuration and then to the - Distributions menu within &man.sysinstall.8;. + svn, which is described in . Once source is installed, review the contents of /usr/src/sys. This directory contains a number of subdirectories, including those which represent the following @@ -350,7 +346,7 @@ To build a file which contains all available options, run the following command as root: - &prompt.root; cd /usr/src/sys/i386/conf && make LINT + &prompt.root; cd /usr/src/sys/arch/conf && make LINT @@ -521,10 +517,10 @@ options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI This causes the kernel to pause for 5 seconds before probing - each SCSI device in the system. If the system only has IDE hard - drives, ignore this or lower the number to speed up booting. - However, if &os; has trouble recognizing the SCSI devices, the - number will have to be raised again. + each SCSI device in the system. If &os; has trouble recognizing + the SCSI devices, the number will have to be raised. On the + other hand, if the system has only IDE hard drives, ignore this + or lower the number to speed up booting. options KTRACE # ktrace(1) support @@ -577,7 +573,7 @@ processors. - This device exists only on the i386 architecture and this + This device exists only on the &i386; architecture and this configuration line should not be used on other architectures. @@ -743,8 +739,7 @@ The &man.vga.4; video card driver. - -device splash # Splash screen and screen saver support + device splash # Splash screen and screen saver support Required by the boot splash screen and screen savers. @@ -926,7 +921,7 @@ #device le ISA Ethernet drivers. See - /usr/src/sys/i386/conf/NOTES + /usr/src/sys/arch/conf/NOTES for details of which cards are supported by which driver. # Wireless NIC cards @@ -1065,7 +1060,7 @@ For more information and additional devices supported by &os;, see - /usr/src/sys/i386/conf/NOTES. + /usr/src/sys/arch/conf/NOTES. Large Memory Configurations --NzB8fVQJ5HfG6fxh-- From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 10:46:47 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 178BADF7 for <freebsd-doc@FreeBSD.org>; Tue, 4 Feb 2014 10:46:47 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A51CE1CB4 for <freebsd-doc@FreeBSD.org>; Tue, 4 Feb 2014 10:46:46 +0000 (UTC) Received: from lghh23.zuhause.de (p5B397F20.dip0.t-ipconnect.de [91.57.127.32]) by mrelayeu.kundenserver.de (node=mreue003) with ESMTP (Nemesis) id 0MK5c9-1WC0RC3fhF-001VWF; Tue, 04 Feb 2014 11:46:44 +0100 Message-ID: <52F0C512.8080909@online.de> Date: Tue, 04 Feb 2014 11:46:42 +0100 From: Dieter Lange <dieter_lange@online.de> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:16.0) Gecko/20121014 Thunderbird/16.0.1 MIME-Version: 1.0 To: freebsd-doc@FreeBSD.org Subject: GEOM meaning Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:rG4RTF19PSTqKt2kLD38fo4ajMOMjtk5ihZxmSW033D EWsDTODXAe4Rkl9IzLjH/cOMLPNTkZCJAHsViE+51WJLHlASy0 uOPq+x3BPYI5RZb51KtPKgVrMchIMjiWmWEIx5qVF+HV5sXxDm OUpf2OeIPHwliNZqD47pCgIAuuTSstbj1yiYII8UhfhqfD7B7J vyqoXzC+7lGGsf17q2lFj0n0H7SqPtMzaON5Zn94c6B/dUQPsp eU6zFf8bMK5X/aN30R23fXsKllWHDC0iy7FeI/7V9W1Z6osGa8 bKJZjs+au1fILKRB3UMN7Hy66xw4p+A5eCzIEdT78gigSWUsYS zTdZImJdCVrIjT3Grq6c= X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 10:46:47 -0000 Hi, having looked at quite a few sites now, not just <http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom.html> I still cannot find out what "GEOM" means (wrt disks etc., not geography or so). It probably does not mean "Modular Disk Transformation Framework". I am not talking of its use and/or definitions, just the meaning of the abbreviation or word... Thanks+kind regards from the only person on the WWW who doesn't know... DL From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 11:57:16 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 6214F760 for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 11:57:16 +0000 (UTC) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DB12B139F for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 11:57:14 +0000 (UTC) Received: from [192.168.1.35] (host86-161-164-213.range86-161.btcentralplus.com [86.161.164.213]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id s14Bv6JD027124 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 11:57:07 GMT (envelope-from frank2@fjl.co.uk) Message-ID: <52F0D58F.4040703@fjl.co.uk> Date: Tue, 04 Feb 2014 11:57:03 +0000 From: Frank Leonhardt <frank2@fjl.co.uk> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-doc@freebsd.org Subject: Re: GEOM meaning References: <52F0C512.8080909@online.de> In-Reply-To: <52F0C512.8080909@online.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 11:57:16 -0000 On 04/02/2014 10:46, Dieter Lange wrote: > Hi, > > having looked at quite a few sites now, not just > <http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom.html> > I still cannot find out what "GEOM" means (wrt disks etc., not > geography or so). It probably does not mean "Modular Disk > Transformation Framework". I am not talking of its use and/or > definitions, just the meaning of the abbreviation or word... > > Thanks+kind regards from the only person on the WWW who doesn't know... > DL I've always assumed it was short for (disk) geometry - i.e. converting logical requests to match the disk geometry. Eh? Well, back in my youth we did talk about the "geometr"y of DASD (disk!). For example, how many platters (heads), cylinders (tracks) and sectors/track were present. With ATA and SCSI this has become less relevant as you only get to see the logical structure of a disk (a load of blocks sequentially numbered 0...n). You may well ask why anyone would call these parameters "geometry", but I can't think of any other better name for it, nor any other word in common use for referring to them (other than CHT). But a disk's geometry was highly relevant because you (the programmer) would either be responsible for moving the head (via a stepper motor) to the correct track, or at the very least, you had to be sensitive to where the head was on the disk when optimising your code. I've no proof whatsoever that this is why the geom library is so called - it could all be a complete coincidence. I don't remember hearing about "geom" on System V, nor on BSD until recently (late 1990s). Regards, Frank. From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 12:03:22 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 7E70E96B for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 12:03:22 +0000 (UTC) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id CBFBE14BB for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 12:03:21 +0000 (UTC) Received: from [192.168.1.35] (host86-161-164-213.range86-161.btcentralplus.com [86.161.164.213]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id s14C3J34028339 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 12:03:20 GMT (envelope-from frank2@fjl.co.uk) Message-ID: <52F0D705.1090402@fjl.co.uk> Date: Tue, 04 Feb 2014 12:03:17 +0000 From: Frank Leonhardt <frank2@fjl.co.uk> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-doc@freebsd.org Subject: Re: GEOM meaning References: <52F0C512.8080909@online.de> <52F0D58F.4040703@fjl.co.uk> In-Reply-To: <52F0D58F.4040703@fjl.co.uk> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 12:03:22 -0000 On 04/02/2014 11:57, Frank Leonhardt wrote: > On 04/02/2014 10:46, Dieter Lange wrote: >> Hi, >> >> having looked at quite a few sites now, not just >> <http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom.html> >> I still cannot find out what "GEOM" means (wrt disks etc., not >> geography or so). It probably does not mean "Modular Disk >> Transformation Framework". I am not talking of its use and/or >> definitions, just the meaning of the abbreviation or word... >> >> Thanks+kind regards from the only person on the WWW who doesn't know... >> DL > > I've always assumed it was short for (disk) geometry - i.e. converting > logical requests to match the disk geometry. Eh? Well, back in my > youth we did talk about the "geometr"y of DASD (disk!). For example, > how many platters (heads), cylinders (tracks) and sectors/track were > present. With ATA and SCSI this has become less relevant as you only > get to see the logical structure of a disk (a load of blocks > sequentially numbered 0...n). You may well ask why anyone would call > these parameters "geometry", but I can't think of any other better > name for it, nor any other word in common use for referring to them > (other than CHT). But a disk's geometry was highly relevant because > you (the programmer) would either be responsible for moving the head > (via a stepper motor) to the correct track, or at the very least, you > had to be sensitive to where the head was on the disk when optimising > your code. > > I've no proof whatsoever that this is why the geom library is so > called - it could all be a complete coincidence. I don't remember > hearing about "geom" on System V, nor on BSD until recently (late 1990s). > > Regards, Frank. > P.S. The reason why I'm not 100% happy with the above theory is that the geom library sits between DEVFS and the device driver (pretending to be a device driver to DEVFS). This doesn't seem to me the logical place for geometry translations, but it wouldn't be the first time a name has ended up migrating to another purpose. From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 12:53:45 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 2F291C63 for <doc@FreeBSD.org>; Tue, 4 Feb 2014 12:53:45 +0000 (UTC) Received: from homiemail-a89.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by mx1.freebsd.org (Postfix) with ESMTP id 12A7E192A for <doc@FreeBSD.org>; Tue, 4 Feb 2014 12:53:44 +0000 (UTC) Received: from homiemail-a89.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a89.g.dreamhost.com (Postfix) with ESMTP id 749BC318071; Tue, 4 Feb 2014 04:53:38 -0800 (PST) Received: from dreadnaught (ip68-100-185-59.dc.dc.cox.net [68.100.185.59]) (Authenticated sender: trhodes@fbsdsecure.org) by homiemail-a89.g.dreamhost.com (Postfix) with ESMTPA id 1DCAC318064; Tue, 4 Feb 2014 04:53:38 -0800 (PST) Date: Tue, 4 Feb 2014 07:53:36 -0500 From: Tom Rhodes <trhodes@FreeBSD.org> To: Mike Brown <mike@skew.org> Subject: Re: Patch (WIP): New security front matter; new shell redirection section Message-Id: <20140204075336.3e6291f2.trhodes@FreeBSD.org> In-Reply-To: <201402040800.s1480fXU006990@chilled.skew.org> References: <20140202175121.16a0c264.trhodes@FreeBSD.org> <201402040800.s1480fXU006990@chilled.skew.org> 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=US-ASCII Content-Transfer-Encoding: 7bit Cc: doc@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 12:53:45 -0000 On Tue, 4 Feb 2014 01:00:41 -0700 (MST) Mike Brown <mike@skew.org> wrote: > Tom Rhodes wrote: > > + <para>Passwords are a necessary evil of the past. In the cases > > + they must be used, not only should the password be extremely > > + complex, but also use a powerful hash mechanism to protect it. > > + At the time of this writing, &os; supports > > + <acronym>DES</acronym>, <acronym>MD</acronym>5, Blowfish, > > + <acronym>SHA</acronym>256, and <acronym>SHA</acronym>512 in > > + the <function>crypt()</function> library. The default is > > + <acronym>SHA</acronym>512 and should not be changed backwards; > > + however, some users like to use the Blowfish option. Each > > + mechanism, aside from <acronym>DES</acronym>, has a unique > > + beginning to designate the hash mechanism assigned. For the > > + <acronym>MD</acronym>5 mechanism, the symbol is a > > + <quote>$</quote> sign. For the <acronym>SHA</acronym>256 or > > + <acronym>SHA</acronym>512, the symbol is <quote>$6$</quote> > > + and Blowfish uses <quote>$2a$</quote>. Any weaker passwords > > + should be re-hashed by asking the user to run &man.passwd.1; > > + during their next login.</para> > > I get confused by this. > > "Any weaker passwords" immediately follows discussion of hash > mechanisms, suggesting you actually mean to say "Any passwords > protected by weaker hash mechanisms" ... although maybe you > were done talking about hash mechanisms and were actually now > back to talking about password complexity? Please clarify. > > Either way, how do I inspect /etc/spwd.db to find out who has > weak/not-complex-enough passwords, and what hash mechanism is in use > for each user, so I know who needs to run passwd(1)? > > If this info is already in the chapter, forgive me; I am just > going by what's in the diff. > > Anyway, overall it looks great. Thanks! You actually did remind me that, with the new version I just put in, I added a bunch of sections but completely dropped the ball on checking for weak passwords! Though, the new chapter has sudo, rkhunter, and setting up an mtree(8) based IDS and more tunables. I'll try to work up an additional bit of cracking passwords and the like sometime this week. Cheers, -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 12:54:53 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 DD1C1CC0 for <freebsd-doc@FreeBSD.org>; Tue, 4 Feb 2014 12:54:53 +0000 (UTC) Received: from homiemail-a89.g.dreamhost.com (caiajhbdccah.dreamhost.com [208.97.132.207]) by mx1.freebsd.org (Postfix) with ESMTP id BF8431945 for <freebsd-doc@FreeBSD.org>; Tue, 4 Feb 2014 12:54:53 +0000 (UTC) Received: from homiemail-a89.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a89.g.dreamhost.com (Postfix) with ESMTP id 0B69F318059; Tue, 4 Feb 2014 04:54: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-a89.g.dreamhost.com (Postfix) with ESMTPA id 9409131805C; Tue, 4 Feb 2014 04:54:52 -0800 (PST) Date: Tue, 4 Feb 2014 07:54:51 -0500 From: Tom Rhodes <trhodes@FreeBSD.org> To: Warren Block <wblock@wonkity.com> Subject: Re: Improving callout lists in HTML (CSS) Message-Id: <20140204075451.74ffa6b9.trhodes@FreeBSD.org> In-Reply-To: <alpine.BSF.2.00.1402032049340.31566@wonkity.com> References: <alpine.BSF.2.00.1402022150320.19166@wonkity.com> <alpine.BSF.2.00.1402032028350.31566@wonkity.com> <alpine.BSF.2.00.1402032049340.31566@wonkity.com> 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=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-doc@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 12:54:53 -0000 On Mon, 3 Feb 2014 20:51:20 -0700 (MST) Warren Block <wblock@wonkity.com> wrote: > On Mon, 3 Feb 2014, Warren Block wrote: > > > Building the Handbook copies doc/share/misc/docbook.css into the Handbook > > directory. So patch the original, do a 'make clean' for the Handbook, then > > refresh the browser to view the new version. > > Which assumes you are looking at a local copy rather than the real thing > shown at the link posted earlier. Presumably your local link would be > more like > file:///usr/doc/en_US.ISO8859-1/books/handbook/book.html#co-tls-ssid I'll look at your patch today. :) -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 14:01:45 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 3576BD28; Tue, 4 Feb 2014 14:01:45 +0000 (UTC) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 19B5F10C2; Tue, 4 Feb 2014 14:01:43 +0000 (UTC) Received: from porto.starpoint.kiev.ua (porto-e.starpoint.kiev.ua [212.40.38.100]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id PAA03750; Tue, 04 Feb 2014 15:55:10 +0200 (EET) (envelope-from avg@FreeBSD.org) Received: from localhost ([127.0.0.1]) by porto.starpoint.kiev.ua with esmtp (Exim 4.34 (FreeBSD)) id 1WAgSz-0004jt-Tj; Tue, 04 Feb 2014 15:55:09 +0200 Message-ID: <52F0F0EC.5090902@FreeBSD.org> Date: Tue, 04 Feb 2014 15:53:48 +0200 From: Andriy Gapon <avg@FreeBSD.org> User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-fs <fs@FreeBSD.org>, FreeBSD Current <freebsd-current@FreeBSD.org>, freebsd-doc@FreeBSD.org Subject: zfs boot manual pages References: <201301251633.r0PGX15j040754@svn.freebsd.org> <5102B7A5.7030105@FreeBSD.org> <alpine.BSF.2.00.1307022125160.58832@wonkity.com> <51F0F0FE.6030208@FreeBSD.org> <alpine.BSF.2.00.1307281800200.12706@wonkity.com> <51F60897.1020005@FreeBSD.org> <alpine.BSF.2.00.1307291401500.46556@wonkity.com> <52E22240.5050501@FreeBSD.org> <alpine.BSF.2.00.1401241845360.92265@wonkity.com> <alpine.BSF.2.00.1401241856260.93615@wonkity.com> <alpine.BSF.2.00.1401241901580.93615@wonkity.com> In-Reply-To: <alpine.BSF.2.00.1401241901580.93615@wonkity.com> X-Enigmail-Version: 1.6 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 List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 14:01:45 -0000 I've started working on manual pages for the zfs boot chain. Please [p]review my work in progress here: https://github.com/avg-I/freebsd/compare/review;zfs-boot-man-pages Any additions, corrections, suggestions and other kinds of reviewing are welcome. Patches and pull requests are very welcome! Many thanks to Warren Block for the initial review and many fixes. -- Andriy Gapon From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 15:25:32 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 6427A3E1; Tue, 4 Feb 2014 15:25:32 +0000 (UTC) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 132D11880; Tue, 4 Feb 2014 15:25:32 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id w7so14016894qcr.0 for <multiple recipients>; Tue, 04 Feb 2014 07:25:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=fRhshnpbPLQ/gO1b9tj2CGeNd4hgJR5bbxzsK0CQYOE=; b=WxjaS9ty+DjFQ/ksXL99tYex9xihPPIeMXddLKbPBvi/KtU3CX89UiZFOGDLnbO58T yxGL04VtLxUmCklHVdLDFq75LiI6/AypGvfYDsnAf5mECz7kudjpo/8fLK/qVtgtGf// qtPlivfgjsOweiQ+1XyJe6QaWGz2mJx4Uwxa1BAzT0Wc+wv4L9BLkkvD3HqR8j3jMath 1QpVGZlIFj+k4hiOF31T3qBx8ND3WVU/SLJkci70vzcLTk+jlzFplHgGM6NvS9T1wIC+ LsSKtAXIbCpMZDB8h/9Bc70pDZ0x0CovrQKLNC1dxJWTNR1O0yVV9iuYZuPWKQFHJKem 9HZw== MIME-Version: 1.0 X-Received: by 10.224.124.74 with SMTP id t10mr67184073qar.40.1391527508450; Tue, 04 Feb 2014 07:25:08 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.229.151.73 with HTTP; Tue, 4 Feb 2014 07:25:08 -0800 (PST) Date: Tue, 4 Feb 2014 16:25:08 +0100 X-Google-Sender-Auth: sKaxJkhoI0cRMGncL0yAHNJh2bA Message-ID: <CAFYkXj=0f3cb5kAt+83VecsBer6eN42yesgA7uya2QwU=T4gpw@mail.gmail.com> Subject: poor fusefs documentation From: CeDeROM <cederom@tlen.pl> To: freebsd-doc@freebsd.org, FreeBSD Filesystems <freebsd-fs@freebsd.org> Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 15:25:32 -0000 Hello :-) I am trying to use various fusefs mounters but the documentation for this seems to be inconsistent and incomplete or missing at all in Handbook. There is only mount_fusefs utility that refers to fuse_daemon that does not exist. It is impossible to mount anything at first contact with fusefs in FreeBSD, please update the documentation :-) Best regards :-) Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 15:34:06 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 E25BA830; Tue, 4 Feb 2014 15:34:06 +0000 (UTC) Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [IPv6:2607:f8b0:400d:c00::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8C4571961; Tue, 4 Feb 2014 15:34:06 +0000 (UTC) Received: by mail-qa0-f46.google.com with SMTP id ii20so12157056qab.5 for <multiple recipients>; Tue, 04 Feb 2014 07:34:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=YOryhxHWZnr2iFUgkE3nCUIMsqLOlJ03wBq0EfmI+8o=; b=Ik9ep17JIVxyeHKy8mxBmD75QNtcMh1Hl408FZ9qvOGg3Zz1K3dKH47yC5F/y5jcHY BHbzsTRq4KsMv54HR8XXgiYHPV5YqQzIGQ628aVoetLM9cL2CS0tnHEsUdLvz6O5e//i Wo+6ykCvs7+wFlxncV3Vr3dsKfdbnCU8nQ2rsk5yEkDyUJvkXTXbzi5p7PMYB7fK9aqa mc/n3OoHHjyb3FoW3CPWpSACM/dOiDhd2+vY2YEI/9jc+MsRy4Q+A6q86lrrK2z/dYn+ KrtGeLxSHT2U00/kVUQvlxTo00jDi6JYv5BESCfnXtQz62QUiCasCjuluxyIZ2y9m5P0 MrPw== MIME-Version: 1.0 X-Received: by 10.140.94.74 with SMTP id f68mr63530561qge.64.1391528045608; Tue, 04 Feb 2014 07:34:05 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.229.151.73 with HTTP; Tue, 4 Feb 2014 07:34:05 -0800 (PST) In-Reply-To: <CAFYkXj=0f3cb5kAt+83VecsBer6eN42yesgA7uya2QwU=T4gpw@mail.gmail.com> References: <CAFYkXj=0f3cb5kAt+83VecsBer6eN42yesgA7uya2QwU=T4gpw@mail.gmail.com> Date: Tue, 4 Feb 2014 16:34:05 +0100 X-Google-Sender-Auth: _aaW3DJ_cjb3IbQm847BlmeLCRU Message-ID: <CAFYkXj=rLL=MBj4cnFerJNZMc+RoocFWr6G+MgfuKDvpbzWD5Q@mail.gmail.com> Subject: Re: poor fusefs documentation From: CeDeROM <cederom@tlen.pl> To: freebsd-doc@freebsd.org, FreeBSD Filesystems <freebsd-fs@freebsd.org> Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 15:34:07 -0000 On Tue, Feb 4, 2014 at 4:25 PM, CeDeROM <cederom@tlen.pl> wrote: > I am trying to use various fusefs mounters but the documentation for > this seems to be inconsistent and incomplete or missing at all in > Handbook. There is only mount_fusefs utility that refers to > fuse_daemon that does not exist. It is impossible to mount anything at > first contact with fusefs in FreeBSD, please update the documentation > :-) In example - I need to mount cryptofs or ntfs, I guess mount_fusefs should be used for that with proper "-t" option like in standard mount program or some automatic fs recognition should take place, but instead, I must use dedicated cryptofs application with no manual page, and there is no application for ntfs, apropos can tell nothing about both cryptofs and ntfs. This looks so Linux :-( -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 16:28:51 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 A51E2584 for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 16:28:51 +0000 (UTC) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 93B7F1E08 for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 16:28:50 +0000 (UTC) Received: from [192.168.1.35] (host86-161-164-213.range86-161.btcentralplus.com [86.161.164.213]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id s14GSkir002138 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 16:28:48 GMT (envelope-from frank2@fjl.co.uk) Message-ID: <52F1153B.4070701@fjl.co.uk> Date: Tue, 04 Feb 2014 16:28:43 +0000 From: Frank Leonhardt <frank2@fjl.co.uk> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-doc@freebsd.org Subject: Re: poor fusefs documentation References: <CAFYkXj=0f3cb5kAt+83VecsBer6eN42yesgA7uya2QwU=T4gpw@mail.gmail.com> In-Reply-To: <CAFYkXj=0f3cb5kAt+83VecsBer6eN42yesgA7uya2QwU=T4gpw@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 16:28:51 -0000 On 04/02/2014 15:25, CeDeROM wrote: > Hello :-) > > I am trying to use various fusefs mounters but the documentation for > this seems to be inconsistent and incomplete or missing at all in > Handbook. There is only mount_fusefs utility that refers to > fuse_daemon that does not exist. It is impossible to mount anything at > first contact with fusefs in FreeBSD, please update the documentation > :-) > > Best regards :-) > Tomek > I asked why mount_ntfs had suddenly disappeared on freebsd-questions - started a bit of a thread. mount -t ntfs doesn't work, and neither does its supposed replacement mount -t ntfs-3g. So I'm not sure if this counts as a documentation problem, or an issue that needs fixing in the release with an intermediate note in the manual explaining work-arounds. I'm not very familiar with fuse, but I should still have been able to figure this out and couldn't, and I had a job to do at the time. Regards, Frank. From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 17:32:57 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 A9A8A333 for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 17:32:57 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 8023615C8 for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 17:32:56 +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 44D645861D for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 17:32:55 +0000 (UTC) Message-ID: <52F12446.1040109@allanjude.com> Date: Tue, 04 Feb 2014 12:32:54 -0500 From: Allan Jude <freebsd@allanjude.com> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-doc@freebsd.org Subject: Re: poor fusefs documentation References: <CAFYkXj=0f3cb5kAt+83VecsBer6eN42yesgA7uya2QwU=T4gpw@mail.gmail.com> <52F1153B.4070701@fjl.co.uk> In-Reply-To: <52F1153B.4070701@fjl.co.uk> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="wXOLvOEipfoG5G3v0t47mj0Uit36P7w5n" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 17:32:57 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --wXOLvOEipfoG5G3v0t47mj0Uit36P7w5n Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2014-02-04 11:28, Frank Leonhardt wrote: > On 04/02/2014 15:25, CeDeROM wrote: >> Hello :-) >> >> I am trying to use various fusefs mounters but the documentation for >> this seems to be inconsistent and incomplete or missing at all in >> Handbook. There is only mount_fusefs utility that refers to >> fuse_daemon that does not exist. It is impossible to mount anything at= >> first contact with fusefs in FreeBSD, please update the documentation >> :-) >> >> Best regards :-) >> Tomek >> > I asked why mount_ntfs had suddenly disappeared on freebsd-questions > - started a bit of a thread. > > mount -t ntfs doesn't work, and neither does its supposed replacement > mount -t ntfs-3g. > > So I'm not sure if this counts as a documentation problem, or an issue > that needs fixing in the release with an intermediate note in the > manual explaining work-arounds. I'm not very familiar with fuse, but I > should still have been able to figure this out and couldn't, and I had > a job to do at the time. > > Regards, Frank. > > > _______________________________________________ > 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" ntfs-3g must be installed from ports first The mount_ntfs in older versions of FreeBSD was read-only and very dated. Fuse it self does not mount anything, it just provides a framework to write file system drivers with. A fuse file system will always require the support of an external program, like ntfs-3g or crypto= fs Documentation for those comes with the port, not the base system --=20 Allan Jude --wXOLvOEipfoG5G3v0t47mj0Uit36P7w5n 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/ iQIcBAEBAgAGBQJS8SRJAAoJEJrBFpNRJZKfrSQP/1oRxLcwtzHG62eNpQhAfH5t zaxLEbQmG9/P+Ve6QN71Y8dviOaJamXyba5SEFVhKaYEJwim9+1Un7jIgjyd9ShB Sk3z2SHvwZiWNkqjB2aWfjD+8mqa5vxOecFcBy/mCLpXY3X1o6MBf3wJ4slf4kIh 4FblbaiMfV8tOUD55KqkctXqaFG/Ae5mQMtiiIiDZRAHUZWcJvz3s6CJ1M8P8N1x QuxCq3OrUBpH+y1fHaV4uBCYn93mhKEXOZ0szc72z9l/wSag7ey1qbK0ms3SU/U+ kodI+K5OiTUaDYmA7G+IZQTeX5TEZOkSiioM4Wk/1L6ushY8njP6BdFrsup7ErTn GbUyErHcELNg9iS52FFMLNecQa5az2QOGFRy3JA11lvjKWrQqalBWkkQ44LbqzMm mmP7N4ccoU8RXCjJPwwRbhZxzRtAwjuifUEwQfDFUPQwTn9hkIZBrldhyWgNb7TX ZFvpdKnj074n6jfxbmaxt9gAJzpBg9kTve3xxjNuKkuMoSoWZKzghfHwjRH88rMb xIQx8KBjF43dnElQM8vVS6r8RGK/2u7NiGnOoXmFwFtf0xPQLFeTM21mCABNKZ+2 JJgPK1PTGBjVLujdQWsOw4KmrA8XTVFRVvUrCXCN+ULthmQL2J/xodV+0Qbv6XpS XzVeVh7dFWZ7S+hauvUU =UJSy -----END PGP SIGNATURE----- --wXOLvOEipfoG5G3v0t47mj0Uit36P7w5n-- From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 18:09:50 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 141E8C96 for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 18:09:50 +0000 (UTC) Received: from bs1.fjl.org.uk (bs1.fjl.org.uk [84.45.41.196]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7CB4418A2 for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 18:09:48 +0000 (UTC) Received: from [192.168.1.35] (host86-161-164-213.range86-161.btcentralplus.com [86.161.164.213]) (authenticated bits=0) by bs1.fjl.org.uk (8.14.4/8.14.4) with ESMTP id s14I9kS4023875 (version=TLSv1/SSLv3 cipher=DHE-DSS-CAMELLIA256-SHA bits=256 verify=NO) for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 18:09:46 GMT (envelope-from frank2@fjl.co.uk) Message-ID: <52F12CE7.5070403@fjl.co.uk> Date: Tue, 04 Feb 2014 18:09:43 +0000 From: Frank Leonhardt <frank2@fjl.co.uk> User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-doc@freebsd.org Subject: Re: poor fusefs documentation References: <CAFYkXj=0f3cb5kAt+83VecsBer6eN42yesgA7uya2QwU=T4gpw@mail.gmail.com> <52F1153B.4070701@fjl.co.uk> <52F12446.1040109@allanjude.com> In-Reply-To: <52F12446.1040109@allanjude.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 18:09:50 -0000 On 04/02/2014 17:32, Allan Jude wrote: > On 2014-02-04 11:28, Frank Leonhardt wrote: >> On 04/02/2014 15:25, CeDeROM wrote: >>> Hello :-) >>> >>> I am trying to use various fusefs mounters but the documentation for >>> this seems to be inconsistent and incomplete or missing at all in >>> Handbook. There is only mount_fusefs utility that refers to >>> fuse_daemon that does not exist. It is impossible to mount anything at >>> first contact with fusefs in FreeBSD, please update the documentation >>> :-) >>> >>> Best regards :-) >>> Tomek >>> >> I asked why mount_ntfs had suddenly disappeared on freebsd-questions >> - started a bit of a thread. >> >> mount -t ntfs doesn't work, and neither does its supposed replacement >> mount -t ntfs-3g. >> >> So I'm not sure if this counts as a documentation problem, or an issue >> that needs fixing in the release with an intermediate note in the >> manual explaining work-arounds. I'm not very familiar with fuse, but I >> should still have been able to figure this out and couldn't, and I had >> a job to do at the time. >> >> Regards, Frank. >> >> >> _______________________________________________ >> 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" > ntfs-3g must be installed from ports first > > The mount_ntfs in older versions of FreeBSD was read-only and very > dated. Fuse it self does not mount anything, it just provides a > framework to write file system drivers with. A fuse file system will > always require the support of an external program, like ntfs-3g or cryptofs > > Documentation for those comes with the port, not the base system > The implication of "ntfs-3g must be installed from the ports first" is that once built and installed, mount_ntfs will work. Or as I'd seen in earlier documentation, "mount -t ntfs-3g ..." would now work. If that's the way it's supposed to work, it doesn't! I did publish the runes on freebsd-questions when I'd figured them out. When you say mount_ntfs was in older versions, technically correct but with due respect to your accuracy, still not perticularly helpful. It turned up in 1999 with 3.4, I believe, and disappeared without warning (to users) a couple of weeks ago. The first I knew of it was when I needed to mount an external USB drive in a hurry, and got "Command not found". Okay. mount -t ntfs /dev/da0 /mnt/ntfs mount: /dev/da0: Operation not supported by device Build and install fuse stuff, and try again with ntfs-3g as mount's FS and the same unhelpful message appears. Not the best example of user-friendly design I've ever seen (although IBM's "An error occurred during the physical insertion stage" still beats it on style). The current handbook still says (vaguely) that NTFS is available (20.1). Putting something in 4.7.2 that's useful in this respect (i.e. -t options in mount can be one of.... and if you want to mount NTFS, he's how) would be a good start. I suspect mount_fusefs has something to do with the new solution, but to quote its current man page: DESCRIPTION Basic usage is to start a fuse daemon on the given special file. In practice, the daemon is assigned a special file automatically, which can then be indentified via fstat(1). That special file can then be mounted by mount_fusefs. The second paragraph is even more opaque, and it goes down-hill from there. This is probably a great improvement (the old NTFS driver was ropey, although R/O was fine for me). But the documentation and implementation isn't great for anyone trying to use it. I'd be inclined to tackle this, but I don't know FUSE and I've spent enough time trying to figure it out to realise that it's best left to the gnostics. Regards, Frank. From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 18:25:49 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 CE47930F; Tue, 4 Feb 2014 18:25:49 +0000 (UTC) Received: from mail-qc0-x229.google.com (mail-qc0-x229.google.com [IPv6:2607:f8b0:400d:c01::229]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 7B50E1A3C; Tue, 4 Feb 2014 18:25:49 +0000 (UTC) Received: by mail-qc0-f169.google.com with SMTP id w7so14372232qcr.14 for <multiple recipients>; Tue, 04 Feb 2014 10:25:48 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=8XnxktX6W9tSVeE3IU7Z1fZr50AGGXDcnk+JKZRxp6o=; b=HSQ5cNXr2X7Yd/Gt9Q6QBjCVmDmPhIngBbPpHv5BM+VUqGeffa2hrJ5Og7PqzKThKv kMNG0A+xEQRXoXDw9FlGcDMhUVl72r/M4eZkXvSLXsV/cMY0j/xua8IQ5qD2x9V1kPr7 H4jThUNDMj378FTErWiOoJqebOeNa3hYBG7ssM6946aXU3cTc8EeByUi/DId9rVagjES JZM7gDdQ7pD07h5XzGTI2GLSnUmTRk3qJK56OOiFNF+5+7WFb9LDBDOm80y7GurMdfSD L98Uj08xdvrBStoURNa4iE+NtC/BlyadZE3UT7/dwD8ewDBkRosHEKMbAWbCayMs08IK f+AQ== MIME-Version: 1.0 X-Received: by 10.224.121.137 with SMTP id h9mr58790160qar.55.1391538348588; Tue, 04 Feb 2014 10:25:48 -0800 (PST) Sender: tomek.cedro@gmail.com Received: by 10.229.151.73 with HTTP; Tue, 4 Feb 2014 10:25:48 -0800 (PST) In-Reply-To: <CAFYkXj=rLL=MBj4cnFerJNZMc+RoocFWr6G+MgfuKDvpbzWD5Q@mail.gmail.com> References: <CAFYkXj=0f3cb5kAt+83VecsBer6eN42yesgA7uya2QwU=T4gpw@mail.gmail.com> <CAFYkXj=rLL=MBj4cnFerJNZMc+RoocFWr6G+MgfuKDvpbzWD5Q@mail.gmail.com> Date: Tue, 4 Feb 2014 19:25:48 +0100 X-Google-Sender-Auth: 1rzBG4KDxjiwhU7TkMs01H_b71A Message-ID: <CAFYkXjmKmWW_hmasuvRp_B3od+JN6cpW2-4PJOYjR0wD_t42hQ@mail.gmail.com> Subject: Re: poor fusefs documentation From: CeDeROM <cederom@tlen.pl> To: freebsd-doc@freebsd.org, FreeBSD Filesystems <freebsd-fs@freebsd.org> Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 18:25:49 -0000 On Tue, Feb 4, 2014 at 4:34 PM, CeDeROM <cederom@tlen.pl> wrote: > In example - I need to mount cryptofs or ntfs, I guess mount_fusefs > should be used for that with proper "-t" option like in standard mount > program or some automatic fs recognition should take place, but > instead, I must use dedicated cryptofs application with no manual > page, and there is no application for ntfs, apropos can tell nothing > about both cryptofs and ntfs. This looks so Linux :-( In a perfect situation I would see mount_fusefs to be a frontend for other filesystem loaders/modules, so we only use mount_fusefs no other programs, just like ifconfig works. If any other program/loader has a standalone binary I would consider naming it mount_fusefs_{filesystem} to be coherent with the base and rest of the mount framework. It would be nice if mount_fusefs could detect filesystem if a proper loader is found. I know that fusefs modules/loaders are part of the port tree, but they should also contain man/info, apropos pages and stick to the current FreeBSD naming conventions I guess. This way we could get coherent support for other filesystems provided by fusefs modules. Please keep the FreeBSD ports "the FreeBSD way" not the "Linux way", so many of us switched to FreeBSD because of that integrity issues =) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 19:13:04 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 9C259A55; Tue, 4 Feb 2014 19:13:04 +0000 (UTC) Received: from mail-ig0-x233.google.com (mail-ig0-x233.google.com [IPv6:2607:f8b0:4001:c05::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4872F1FC2; Tue, 4 Feb 2014 19:13:04 +0000 (UTC) Received: by mail-ig0-f179.google.com with SMTP id c10so9205301igq.0 for <multiple recipients>; Tue, 04 Feb 2014 11:13:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jxA2bY1Kpi3xjHQUGA8tb8mHeSTMQmaQA83DVpTHars=; b=XWIEIxQFhANDb5bxw7HhBfyr8hI6/xMpcUo/FFN7A1WJqpD6ZErBiEkN6Ir9cL1vm/ +gWWdn5PwKtWKjpemlcnMcOY9QMXsaKwOmayUSJVxoZI8oq8TBR0rk1p67CRPgoSu2UJ HylrIsNbXxeQpt2Km6Q2COLj0wKtH3qehQiV1JRAq7If4o8yh+cNCxNSsfa2SKDL6XTY 0hBbvzE+uO3IkTSeeRm23yT6yRm2l2UM/jyoTwi4cpZ9H4zqwbD7eI7m88rFgxtVLNOD AnyfHKenfl/4sKKukfe730aeSyQval0mrfAUzC+n1qDfEi8Ak+HtFzvUYIb9H2QFz9M0 KGsQ== MIME-Version: 1.0 X-Received: by 10.42.52.209 with SMTP id k17mr31302452icg.1.1391541183684; Tue, 04 Feb 2014 11:13:03 -0800 (PST) Received: by 10.50.67.84 with HTTP; Tue, 4 Feb 2014 11:13:03 -0800 (PST) In-Reply-To: <52F0F0EC.5090902@FreeBSD.org> References: <201301251633.r0PGX15j040754@svn.freebsd.org> <5102B7A5.7030105@FreeBSD.org> <alpine.BSF.2.00.1307022125160.58832@wonkity.com> <51F0F0FE.6030208@FreeBSD.org> <alpine.BSF.2.00.1307281800200.12706@wonkity.com> <51F60897.1020005@FreeBSD.org> <alpine.BSF.2.00.1307291401500.46556@wonkity.com> <52E22240.5050501@FreeBSD.org> <alpine.BSF.2.00.1401241845360.92265@wonkity.com> <alpine.BSF.2.00.1401241856260.93615@wonkity.com> <alpine.BSF.2.00.1401241901580.93615@wonkity.com> <52F0F0EC.5090902@FreeBSD.org> Date: Tue, 4 Feb 2014 13:13:03 -0600 Message-ID: <CACdU+f-mjkLTJj2TChspvs+TSGgbYo48+7c4n+OYy6ERzj-46g@mail.gmail.com> Subject: Re: zfs boot manual pages From: Scot Hetzel <swhetzel@gmail.com> To: Andriy Gapon <avg@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-doc@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>, freebsd-fs <fs@freebsd.org> X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 19:13:04 -0000 On Tue, Feb 4, 2014 at 7:53 AM, Andriy Gapon <avg@freebsd.org> wrote: > > I've started working on manual pages for the zfs boot chain. > > Please [p]review my work in progress here: > https://github.com/avg-I/freebsd/compare/review;zfs-boot-man-pages > > Any additions, corrections, suggestions and other kinds of reviewing are > welcome. Patches and pull requests are very welcome! > > Many thanks to Warren Block for the initial review and many fixes. One fix for the gptzfsboot man page would be to mention that gptzfsboot is installed into a GPT partition of type freebsd-boot, and that the -i 1 refers to the GPT index for this partition. -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 20:13:56 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 BC7367AD; Tue, 4 Feb 2014 20:13:56 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 66C1A1601; Tue, 4 Feb 2014 20:13:56 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s14KDsoL039959; Tue, 4 Feb 2014 13:13:54 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s14KDseU039956; Tue, 4 Feb 2014 13:13:54 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Tue, 4 Feb 2014 13:13:54 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Scot Hetzel <swhetzel@gmail.com> Subject: Re: zfs boot manual pages In-Reply-To: <CACdU+f-mjkLTJj2TChspvs+TSGgbYo48+7c4n+OYy6ERzj-46g@mail.gmail.com> Message-ID: <alpine.BSF.2.00.1402041301220.38916@wonkity.com> References: <201301251633.r0PGX15j040754@svn.freebsd.org> <5102B7A5.7030105@FreeBSD.org> <alpine.BSF.2.00.1307022125160.58832@wonkity.com> <51F0F0FE.6030208@FreeBSD.org> <alpine.BSF.2.00.1307281800200.12706@wonkity.com> <51F60897.1020005@FreeBSD.org> <alpine.BSF.2.00.1307291401500.46556@wonkity.com> <52E22240.5050501@FreeBSD.org> <alpine.BSF.2.00.1401241845360.92265@wonkity.com> <alpine.BSF.2.00.1401241856260.93615@wonkity.com> <alpine.BSF.2.00.1401241901580.93615@wonkity.com> <52F0F0EC.5090902@FreeBSD.org> <CACdU+f-mjkLTJj2TChspvs+TSGgbYo48+7c4n+OYy6ERzj-46g@mail.gmail.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]); Tue, 04 Feb 2014 13:13:54 -0700 (MST) Cc: freebsd-doc@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>, freebsd-fs <fs@freebsd.org>, Andriy Gapon <avg@freebsd.org> X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 20:13:56 -0000 On Tue, 4 Feb 2014, Scot Hetzel wrote: > On Tue, Feb 4, 2014 at 7:53 AM, Andriy Gapon <avg@freebsd.org> wrote: >> >> I've started working on manual pages for the zfs boot chain. >> >> Please [p]review my work in progress here: >> https://github.com/avg-I/freebsd/compare/review;zfs-boot-man-pages >> >> Any additions, corrections, suggestions and other kinds of reviewing are >> welcome. Patches and pull requests are very welcome! >> >> Many thanks to Warren Block for the initial review and many fixes. > > One fix for the gptzfsboot man page would be to mention that > gptzfsboot is installed into a GPT partition of type freebsd-boot, and > that the -i 1 refers to the GPT index for this partition. We are missing that from the gptboot.8 page also. gptzfsboot is installed in a freebsd-boot partition, usually the first partition on the disk. A ``protective MBR'' (see gpart(8)) is typically used in combination with gptzfsboot. To install gptzfsboot on the ada0 drive: gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 20:37:56 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 CE6E0395 for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 20:37:56 +0000 (UTC) Received: from mail-lb0-x22d.google.com (mail-lb0-x22d.google.com [IPv6:2a00:1450:4010:c04::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5047D181A for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 20:37:56 +0000 (UTC) Received: by mail-lb0-f173.google.com with SMTP id y6so6803721lbh.4 for <freebsd-doc@freebsd.org>; Tue, 04 Feb 2014 12:37:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; bh=3VlajQGPoKnoeNsiDNttsvYjLB1bb5zBf8Tzje1x8do=; b=MojfH5YOqi05LOnKoWUNbuoY+ylOvjQWX7d3wvQA6658Put1484OC75VkL4G13tF51 1z6oM4fPyU3P8rzUbOQn5E+kL1wgSpOb06OK0BsArSq6MFBIhKrx9+EHAiytPzIftq56 1y9akc/nyDbR6Tkfcep7wX1m/xT9Hva/fMB+PNqO9mbYeokB47tNKlEUZ/d8+jadWZJE s0eKNPTElVAbV43oCpv6fKq2bfyTJuIfYz24ibOwl3qNgdrV0fB+fy7Q6eQMToUtq9kV MBWMbnzGkamGfnRNI5Wh8LuO9h42aev1zztX31VFgWurgalxeWEp9qJiW+/2T8TMov86 kReA== X-Received: by 10.112.135.233 with SMTP id pv9mr6592lbb.69.1391546274170; Tue, 04 Feb 2014 12:37:54 -0800 (PST) Received: from omg (pluknet-1-pt.tunnel.tserv11.ams1.ipv6.he.net. [2001:470:1f14:4d0::2]) by mx.google.com with ESMTPSA id mo3sm26436817lbb.17.2014.02.04.12.37.51 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Feb 2014 12:37:53 -0800 (PST) Sender: Sergey Kandaurov <pluknet@gmail.com> Date: Wed, 5 Feb 2014 00:37:48 +0400 From: Sergey Kandaurov <pluknet@freebsd.org> To: Taras Korenko <ds@ukrhub.net> Subject: Re: en/handbook/kernelconfig: proposed corrections Message-ID: <20140204203748.GA16522@omg> References: <20140204101604.GC83803@gamma.ukrhub.net> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="UugvWAfsgieZRqgk" Content-Disposition: inline In-Reply-To: <20140204101604.GC83803@gamma.ukrhub.net> 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 List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 20:37:56 -0000 --UugvWAfsgieZRqgk Content-Type: text/plain; charset=koi8-r Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 04, 2014 at 12:16:04PM +0200, Taras Korenko wrote: > Good morning, doc@ folks. >=20 > The following notes were made while working on russian translation > of kernelconfig chapter. I hope some parts of the following diff > might be useful. >=20 > So, could anyone review that diff? Hi, see my 2c inline. > Index: en_US.ISO8859-1/books/handbook/kernelconfig/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 > --- en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml (revision 437= 45) > +++ en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml (working copy) > @@ -204,8 +204,8 @@ > &man.pciconf.8;, which provides more verbose output. For > example:</para> > =20 > - <programlisting><command>pciconf -lv</command> > - ath0@pci0:3:0:0: class=3D0x020000 card=3D0x058a1014 chip=3D0x= 1014168c rev=3D0x01 hdr=3D0x00 > + <programlisting>&prompt.user; pciconf -lv > +ath0@pci0:3:0:0: class=3D0x020000 card=3D0x058a1014 chip=3D0x1014= 168c rev=3D0x01 hdr=3D0x00 > vendor =3D 'Atheros Communications Inc.' > device =3D 'AR5212 Atheros AR5212 802.11abg wireless' > class =3D network > @@ -226,7 +226,7 @@ > ath_hal(4) - Atheros Hardware Access Layer (HAL)</programl= isting> > =20 > <para>Once the hardware inventory list is created, refer to it > - to ensure that installed hardware is not removed as you edit the c= ustom > + to ensure that drivers for installed hardware are not removed as y= ou edit the custom Or rather "drivers OR installed hardware"? :) Both may be removed I guess. > kernel configuration file.</para> > </sect1> > =20 > @@ -250,11 +250,7 @@ > <para>If <filename>/usr/src/</filename> does > not exist or it is empty, source has not been installed. > Source can be installed using > - <application>svn</application>, which is described in <xref linkend=3D"= svn"/>, or by installing the > - <literal>src</literal> distribution using &man.sysinstall.8;. This > - distribution can be selected by navigating to the=20 > - <literal>Configuration</literal> and then to the > - <literal>Distributions</literal> menu within &man.sysinstall.8;.</para> > + <application>svn</application>, which is described in <xref linkend=3D"= svn"/>.</para> You removed reference to sysinstall, but it is still in use in 9.x and 8.x (well ok, only in 8.x but it also exists in 9.x). If you want to touch this place, I would suggest to specify &os; version this is applicable for and briefly mention bsdinstall with referring to <xref linked=3D"bsdinstall-components"/>. It would be fine with simply removing sysinstall part, but this leaves the reader without options. The rest looks good to me, given that you will split the changes into markup and content changes :). --UugvWAfsgieZRqgk Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (FreeBSD) iQEcBAEBAgAGBQJS8U+cAAoJED9Ol7oQYHQZZNoIAJnwbd0NuY5/cvyMHa6Pmmos BUxx9FashmQRzJWNjvfWZQ5L+XyssvG5VEEmYveGovZuCRb8ZJu9GRD2eYBMDc+p qI05Mq60iHBxzKvDwDlWNIYsGlXZvBTo3kCszbA+ID7j3T3JaEmsIytcMcoZzFSV hGlwThmgI5d4aTbBEVTYmUY8+zkeyeEGBmYhsK5yGb9KDIQdOBXI/QEhgdrV9qel jEdJsOPKiNu7GNOaGagv8RfGuD56dEBZtZMsHBbfdm6jZJnBKnsIQ5WpSMatz2c5 u1ALKXcUpEeCErqWIj9Dmlt7Lj5n8jlssiRkQlbvCE4NJjzAwVe6oBJG9DB3cfQ= =9ivO -----END PGP SIGNATURE----- --UugvWAfsgieZRqgk-- From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 21:40:00 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 E03118EF for <freebsd-doc@smarthost.ysv.freebsd.org>; Tue, 4 Feb 2014 21: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 A06261E1C for <freebsd-doc@smarthost.ysv.freebsd.org>; Tue, 4 Feb 2014 21: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 s14Le0wS045306 for <freebsd-doc@freefall.freebsd.org>; Tue, 4 Feb 2014 21: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 s14Le0LN045305; Tue, 4 Feb 2014 21:40:00 GMT (envelope-from gnats) Resent-Date: Tue, 4 Feb 2014 21:40:00 GMT Resent-Message-Id: <201402042140.s14Le0LN045305@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, Rainer Duffner <rainer@ultra-secure.de> 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 14EF66E1 for <freebsd-gnats-submit@FreeBSD.org>; Tue, 4 Feb 2014 21:30:42 +0000 (UTC) Received: from oldred.freebsd.org (oldred.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 F10921D87 for <freebsd-gnats-submit@FreeBSD.org>; Tue, 4 Feb 2014 21:30:41 +0000 (UTC) Received: from oldred.freebsd.org ([127.0.1.6]) by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id s14LUfgh079773 for <freebsd-gnats-submit@FreeBSD.org>; Tue, 4 Feb 2014 21:30:41 GMT (envelope-from nobody@oldred.freebsd.org) Received: (from nobody@localhost) by oldred.freebsd.org (8.14.5/8.14.5/Submit) id s14LUfY6079737; Tue, 4 Feb 2014 21:30:41 GMT (envelope-from nobody) Message-Id: <201402042130.s14LUfY6079737@oldred.freebsd.org> Date: Tue, 4 Feb 2014 21:30:41 GMT From: Rainer Duffner <rainer@ultra-secure.de> To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: 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 <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 21:40:00 -0000 >Number: 186464 >Category: docs >Synopsis: Online-Documentation for carp(4) is outdated >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: Tue Feb 04 21:40:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Rainer Duffner >Release: 10.0 >Organization: >Environment: >Description: I found out that the documentation here: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/carp.html is no longer correct with 10.0 released. http://www.freebsd.org/cgi/man.cgi?query=carp&apropos=0&sektion=0&manpath=FreeBSD+10.0-RELEASE&arch=default&format=html I don't believe it's a bad thing to have it described "the old way" (lot's of 8.x and 9.x installs out there, after all, including my own) - there just should be some sort of preface that states it is not how it's done with 10.0 >How-To-Repeat: ifconfig carp0 create obviously does not work anymore in 10.0 >Fix: Sorry, no documentation update. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 22:51:50 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 0D508F2; Tue, 4 Feb 2014 22:51:50 +0000 (UTC) Received: from boomer.ukrhub.net (boomer.ukrhub.net [94.125.121.14]) by mx1.freebsd.org (Postfix) with ESMTP id 7A19A171B; Tue, 4 Feb 2014 22:51:49 +0000 (UTC) Received: by boomer.ukrhub.net (Postfix, from userid 58) id D598D24DC28; Wed, 5 Feb 2014 00:51:47 +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 B8AE624DC1E; Wed, 5 Feb 2014 00:51:45 +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 s14MpjR1038305 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 5 Feb 2014 00:51:45 +0200 (EET) (envelope-from ds@ukrhub.net) Received: (from ds@localhost) by gamma.ukrhub.net (8.14.7/8.14.7/Submit) id s14MpjtM038304; Wed, 5 Feb 2014 00:51:45 +0200 (EET) (envelope-from ds@ukrhub.net) Date: Wed, 5 Feb 2014 00:51:45 +0200 From: Taras Korenko <ds@ukrhub.net> To: Sergey Kandaurov <pluknet@freebsd.org> Subject: Re: en/handbook/kernelconfig: proposed corrections Message-ID: <20140204225145.GA38028@gamma.ukrhub.net> References: <20140204101604.GC83803@gamma.ukrhub.net> <20140204203748.GA16522@omg> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-u Content-Disposition: inline In-Reply-To: <20140204203748.GA16522@omg> 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 <ds@ukrhub.net> List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 22:51:50 -0000 On Wed, Feb 05, 2014 at 12:37:48AM +0400, Sergey Kandaurov wrote: > On Tue, Feb 04, 2014 at 12:16:04PM +0200, Taras Korenko wrote: > > ... > > So, could anyone review that diff? > > Hi, see my 2c inline. > > > Index: en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml > > =================================================================== > > --- en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml (revision 43745) > > +++ en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml (working copy) > > ... > > @@ -226,7 +226,7 @@ > > ath_hal(4) - Atheros Hardware Access Layer (HAL)</programlisting> > > > > <para>Once the hardware inventory list is created, refer to it > > - to ensure that installed hardware is not removed as you edit the custom > > + to ensure that drivers for installed hardware are not removed as you edit the custom > Or rather "drivers OR installed hardware"? :) Both may be removed I guess. I guess user's task at this moment is to create a subset from all available drivers, noone is to add/pull_out NICs, videocards, etc... > > > kernel configuration file.</para> > > </sect1> > > > > @@ -250,11 +250,7 @@ > > <para>If <filename>/usr/src/</filename> does > > not exist or it is empty, source has not been installed. > > Source can be installed using > > - <application>svn</application>, which is described in <xref linkend="svn"/>, or by installing the > > - <literal>src</literal> distribution using &man.sysinstall.8;. This > > - distribution can be selected by navigating to the > > - <literal>Configuration</literal> and then to the > > - <literal>Distributions</literal> menu within &man.sysinstall.8;.</para> > > + <application>svn</application>, which is described in <xref linkend="svn"/>.</para> > You removed reference to sysinstall, but it is still in use in 9.x and 8.x > (well ok, only in 8.x but it also exists in 9.x). > If you want to touch this place, I would suggest to specify &os; version > this is applicable for and briefly mention bsdinstall with referring to > <xref linked="bsdinstall-components"/>. It would be fine with simply > removing sysinstall part, but this leaves the reader without options. Well, OS 8.X: sysinstall allows us to install sources. OS 9.X: according to our hb, sysinstall is deprecated. Bsdinstall cannot install sources because it does not have such a post-install procedure. OS 10.X: we've svnlite (but cannot refer to it's man page). So, we've to provide detailed description of all available options, or keep just one. > ... -- WBR, Taras Korenko From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 23:00:00 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 B0948248 for <freebsd-doc@smarthost.ysv.freebsd.org>; Tue, 4 Feb 2014 23:00: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 8BA0C1781 for <freebsd-doc@smarthost.ysv.freebsd.org>; Tue, 4 Feb 2014 23:00: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 s14N00p0064002 for <freebsd-doc@freefall.freebsd.org>; Tue, 4 Feb 2014 23:00:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s14N00m9064001; Tue, 4 Feb 2014 23:00:00 GMT (envelope-from gnats) Resent-Date: Tue, 4 Feb 2014 23:00:00 GMT Resent-Message-Id: <201402042300.s14N00m9064001@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, nemysis <nemysis@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 66DBABC for <freebsd-gnats-submit@FreeBSD.org>; Tue, 4 Feb 2014 22:50:29 +0000 (UTC) Received: from oldred.freebsd.org (oldred.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 5314D1707 for <freebsd-gnats-submit@FreeBSD.org>; Tue, 4 Feb 2014 22:50:29 +0000 (UTC) Received: from oldred.freebsd.org ([127.0.1.6]) by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id s14MoT1d080281 for <freebsd-gnats-submit@FreeBSD.org>; Tue, 4 Feb 2014 22:50:29 GMT (envelope-from nobody@oldred.freebsd.org) Received: (from nobody@localhost) by oldred.freebsd.org (8.14.5/8.14.5/Submit) id s14MoTPI080268; Tue, 4 Feb 2014 22:50:29 GMT (envelope-from nobody) Message-Id: <201402042250.s14MoTPI080268@oldred.freebsd.org> Date: Tue, 4 Feb 2014 22:50:29 GMT From: nemysis <nemysis@FreeBSD.org> To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: docs/186466: [PATCH] book.xml Stripping Binaries and Shared Libraries X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 23:00:00 -0000 >Number: 186466 >Category: docs >Synopsis: [PATCH] book.xml Stripping Binaries and Shared Libraries >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: Tue Feb 04 23:00:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: nemysis >Release: FreeBSD 9.2-RELEASE amd64 >Organization: >Environment: FreeBSD 9.2-RELEASE-p8 #0: Mon Sep 23 16:26:45 UTC 2013 >Description: Here I have changed so that the user can see how to patch for striping executables and libraries on more than one file. Porter's Handbook 5.15.2. Stripping Binaries and Shared Libraries >How-To-Repeat: >Fix: Please commit enclosed porters-handbook_book.xml.diff I have sent one email to freebsd-doc@ but here is newer diff. Please use only this. Patch attached with submission follows: Index: en_US.ISO8859-1/books/porters-handbook/book.xml =================================================================== --- en_US.ISO8859-1/books/porters-handbook/book.xml (revision 43779) +++ en_US.ISO8859-1/books/porters-handbook/book.xml (working copy) @@ -5096,8 +5096,16 @@ example:</para> <programlisting>post-install: - ${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/xdl</programlisting> + ${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/${PORTNAME}</programlisting> + <para>If you need to strip more files, here shared libraries. + For example:</para> + + <programlisting>post-install: + .for l in geometry media body track world + ${STRIP_CMD} ${STAGEDIR}${PREFIX}/lib/lib${PORTNAME}-${l}.so.0 + .endfor</programlisting> + <para>Use the &man.file.1; command on the installed executable to check whether the binary is stripped or not. If it does not say <literal>not stripped</literal>, it is stripped. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Tue Feb 4 23:21:26 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 B98E24C3 for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 23:21:26 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 6B2B0196B for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 23:21:25 +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 0697F58FC1 for <freebsd-doc@freebsd.org>; Tue, 4 Feb 2014 23:21:24 +0000 (UTC) Message-ID: <52F175F4.5000005@allanjude.com> Date: Tue, 04 Feb 2014 18:21:24 -0500 From: Allan Jude <freebsd@allanjude.com> 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/186466: [PATCH] book.xml Stripping Binaries and Shared Libraries References: <201402042250.s14MoTPI080268@oldred.freebsd.org> In-Reply-To: <201402042250.s14MoTPI080268@oldred.freebsd.org> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="gVmqfPP9jWRaJCHwQqUguRIpT2bVkPPUG" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Tue, 04 Feb 2014 23:21:26 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --gVmqfPP9jWRaJCHwQqUguRIpT2bVkPPUG Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2014-02-04 17:50, nemysis wrote: > Number: 186466 > Category: docs > Synopsis: [PATCH] book.xml Stripping Binaries and Shared Librarie= s > Confidential: no > Severity: non-critical > Priority: low > Responsible: freebsd-doc > State: open > Quarter: =20 > Keywords: =20 > Date-Required: > Class: change-request > Submitter-Id: current-users > Arrival-Date: Tue Feb 04 23:00:00 UTC 2014 > Closed-Date: > Last-Modified: > Originator: nemysis > Release: FreeBSD 9.2-RELEASE amd64 > Organization: > Environment: > FreeBSD 9.2-RELEASE-p8 #0: Mon Sep 23 16:26:45 UTC 2013 >> Description: > Here I have changed so that the user can see how to patch for striping = executables and libraries on more than one file. > > Porter's Handbook > > 5.15.2. Stripping Binaries and Shared Libraries >> How-To-Repeat: >> Fix: > Please commit enclosed porters-handbook_book.xml.diff > > I have sent one email to freebsd-doc@ but here is newer diff. Please us= e only this. > > Patch attached with submission follows: > > Index: en_US.ISO8859-1/books/porters-handbook/book.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 > --- en_US.ISO8859-1/books/porters-handbook/book.xml (revision 43779) > +++ en_US.ISO8859-1/books/porters-handbook/book.xml (working copy) > @@ -5096,8 +5096,16 @@ > example:</para> > =20 > <programlisting>post-install: > - ${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/xdl</programlisting> > + ${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/${PORTNAME}</programlisting> > =20 > + <para>If you need to strip more files, here shared libraries. > + For example:</para> > + > + <programlisting>post-install: > + .for l in geometry media body track world > + ${STRIP_CMD} ${STAGEDIR}${PREFIX}/lib/lib${PORTNAME}-${l}.so.0 > + .endfor</programlisting> > + > <para>Use the &man.file.1; command on the installed executable > to check whether the binary is stripped or not. If it does > not say <literal>not stripped</literal>, it is stripped. > > >> Release-Note: >> Audit-Trail: >> Unformatted: > _______________________________________________ > 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" That should probably read as: If you need to strip more files, such as shared libraries for example: --=20 Allan Jude --gVmqfPP9jWRaJCHwQqUguRIpT2bVkPPUG 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/ iQIcBAEBAgAGBQJS8XX3AAoJEJrBFpNRJZKfRZ0QAIR3zj+7wxXPvIucl/z6wShy GA+D2OvdFS9hOB1yuvnFH+5+yIwVBZpFtMRs7CS0yQKDTdlaFl5GljMuuVPd/bZ8 QI8EYl9k1oYnZ+341bWl3HyEmN+ygT0g/tK9jxzZDvA3ck2HbjynTOPFdRD7cJLk cKsqEBnORZYPxO5l0Br2Calz+3H9H1zV7qT7vSaoyDsXglOhaqtweWS1NB0QLaQr 7eDSYvHoPUhQPyQ5VM1xUWOl7eyGAJvslMaF7Zx1XjFDaJXxfAU3lqEJufReWzWP i2GgNchDapsBWfS1+0Oho0GLK4GBEVSIY+u/7MmoQ6dddEG+hcZxnDZhxSSxRHcO QzEukkj4RESrnClecYZIBxRfHzeKc4jaBppyQ2dNVyOQUcDvfYlrQDlBiD9BOTNI ERmvBp2SK5p3UDQBGrbBTktU+DuVMQnvfmilu2c71TgdqwwoTAy2vH+R3YnWGsh/ Q/CL6C3ZVO6n4G6E65yitKWZAC0sD7AcxTREbyZHA54e6glTYdzkP2VGgNRnJRyp D8HSNxyqelcvRxCT3A/H0hlnahw+a6KNMT017hMFLX/zBlH1OBDpQVx1YWdwg7Ce wnDCT+hpAo/OjHXFaG+yJHcRARAocWEDyc31Z1xThR+EZb2DNCRd/t37jKT0Fa2H wMY2J2Vn9bXRpZaL8/I+ =E1lb -----END PGP SIGNATURE----- --gVmqfPP9jWRaJCHwQqUguRIpT2bVkPPUG-- From owner-freebsd-doc@FreeBSD.ORG Wed Feb 5 00:58:17 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 4BEAB67D; Wed, 5 Feb 2014 00:58:17 +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 2008A1156; Wed, 5 Feb 2014 00:58:17 +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 s150wGXE001552; Wed, 5 Feb 2014 00:58:16 GMT (envelope-from jgh@freefall.freebsd.org) Received: (from jgh@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s150wGll001551; Wed, 5 Feb 2014 00:58:16 GMT (envelope-from jgh) Date: Wed, 5 Feb 2014 00:58:16 GMT Message-Id: <201402050058.s150wGll001551@freefall.freebsd.org> To: jgh@FreeBSD.org, freebsd-doc@FreeBSD.org, jgh@FreeBSD.org From: jgh@FreeBSD.org Subject: Re: docs/186466: [PATCH] book.xml Stripping Binaries and Shared Libraries X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 05 Feb 2014 00:58:17 -0000 Synopsis: [PATCH] book.xml Stripping Binaries and Shared Libraries Responsible-Changed-From-To: freebsd-doc->jgh Responsible-Changed-By: jgh Responsible-Changed-When: Wed Feb 5 00:58:16 UTC 2014 Responsible-Changed-Why: I'll take it. http://www.freebsd.org/cgi/query-pr.cgi?pr=186466 From owner-freebsd-doc@FreeBSD.ORG Wed Feb 5 03:01:58 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 1CCE11F1 for <freebsd-doc@freebsd.org>; Wed, 5 Feb 2014 03:01:58 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BB79E1375 for <freebsd-doc@freebsd.org>; Wed, 5 Feb 2014 03:01:57 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s1531sfE042559; Tue, 4 Feb 2014 20:01:54 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s1531rPS042556; Tue, 4 Feb 2014 20:01:54 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Tue, 4 Feb 2014 20:01:53 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Taras Korenko <ds@ukrhub.net> Subject: Re: en/handbook/kernelconfig: proposed corrections In-Reply-To: <20140204101604.GC83803@gamma.ukrhub.net> Message-ID: <alpine.BSF.2.00.1402041948570.42444@wonkity.com> References: <20140204101604.GC83803@gamma.ukrhub.net> 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]); Tue, 04 Feb 2014 20:01:54 -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 <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 05 Feb 2014 03:01:58 -0000 On Tue, 4 Feb 2014, Taras Korenko wrote: > Good morning, doc@ folks. > > The following notes were made while working on russian translation > of kernelconfig chapter. I hope some parts of the following diff > might be useful. > > So, could anyone review that diff? Notes below prefixed with "WB:". Index: en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml =================================================================== --- en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml (revision 43745) +++ en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml (working copy) @@ -204,8 +204,8 @@ &man.pciconf.8;, which provides more verbose output. For example:</para> - <programlisting><command>pciconf -lv</command> - ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00 + <programlisting>&prompt.user; pciconf -lv WB: This should be a <screen> section rather than <programlisting>. +ath0@pci0:3:0:0: class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00 vendor = 'Atheros Communications Inc.' device = 'AR5212 Atheros AR5212 802.11abg wireless' class = network @@ -226,7 +226,7 @@ ath_hal(4) - Atheros Hardware Access Layer (HAL)</programlisting> <para>Once the hardware inventory list is created, refer to it - to ensure that installed hardware is not removed as you edit the custom + to ensure that drivers for installed hardware are not removed as you edit the custom WB: "are not removed as the custom kernel configuration is edited." (to get rid of the informal "you"). kernel configuration file.</para> </sect1> @@ -250,11 +250,7 @@ <para>If <filename>/usr/src/</filename> does not exist or it is empty, source has not been installed. Source can be installed using - <application>svn</application>, which is described in <xref linkend="svn"/>, or by installing the - <literal>src</literal> distribution using &man.sysinstall.8;. This - distribution can be selected by navigating to the - <literal>Configuration</literal> and then to the - <literal>Distributions</literal> menu within &man.sysinstall.8;.</para> + <application>svn</application>, which is described in <xref linkend="svn"/>.</para> WB: s%<application>svn</application>%<application>Subversion</application>% (svn is the command). <para>Once source is installed, review the contents of <filename>/usr/src/sys</filename>. This directory contains a number of subdirectories, including those which represent the following @@ -350,7 +346,7 @@ <note> <para>To build a file which contains all available options, run the following command as <systemitem class="username">root</systemitem>:</para> - <screen>&prompt.root; <userinput>cd /usr/src/sys/i386/conf && make LINT</userinput></screen> + <screen>&prompt.root; <userinput>cd /usr/src/sys/<replaceable>arch</replaceable>/conf && make LINT</userinput></screen> </note> @@ -521,10 +517,10 @@ <programlisting>options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI</programlisting> <para>This causes the kernel to pause for 5 seconds before probing - each SCSI device in the system. If the system only has IDE hard - drives, ignore this or lower the number to speed up booting. - However, if &os; has trouble recognizing the SCSI devices, the - number will have to be raised again.</para> + each SCSI device in the system. If &os; has trouble recognizing + the SCSI devices, the number will have to be raised. On the + other hand, if the system has only IDE hard drives, ignore this + or lower the number to speed up booting.</para> WB: "If <acronym>SCSI</acronym> drives are not recognized, increase the number. If the system does not have any SCSI drives, this value can be ignored or decreased to speed up booting.</para>" WB: How or whether this still affects systems with IDE, or more specifically non-SCSI devices, needs to be verified. <programlisting>options KTRACE # ktrace(1) support</programlisting> @@ -577,7 +573,7 @@ processors.</para> <note> - <para>This device exists only on the i386 architecture and this + <para>This device exists only on the &i386; architecture and this configuration line should not be used on other architectures.</para> </note> @@ -743,8 +739,7 @@ <para>The &man.vga.4; video card driver.</para> - <programlisting> -device splash # Splash screen and screen saver support</programlisting> + <programlisting>device splash # Splash screen and screen saver support</programlisting> <para>Required by the boot splash screen and screen savers.</para> @@ -926,7 +921,7 @@ #device le</programlisting> <para>ISA Ethernet drivers. See - <filename>/usr/src/sys/i386/conf/NOTES</filename> + <filename>/usr/src/sys/<replaceable>arch</replaceable>/conf/NOTES</filename> for details of which cards are supported by which driver.</para> <programlisting># Wireless NIC cards @@ -1065,7 +1060,7 @@ <para>For more information and additional devices supported by &os;, see - <filename>/usr/src/sys/i386/conf/NOTES</filename>.</para> + <filename>/usr/src/sys/<replaceable>arch</replaceable>/conf/NOTES</filename>.</para> <sect2> <title>Large Memory Configurations From owner-freebsd-doc@FreeBSD.ORG Wed Feb 5 03:15:55 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 CC2ADC19; Wed, 5 Feb 2014 03:15:55 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 801F115E9; Wed, 5 Feb 2014 03:15:55 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s153FsYZ042624; Tue, 4 Feb 2014 20:15:54 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s153FsUV042621; Tue, 4 Feb 2014 20:15:54 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Tue, 4 Feb 2014 20:15:54 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: nemysis <nemysis@FreeBSD.org> Subject: Re: docs/186466: [PATCH] book.xml Stripping Binaries and Shared Libraries In-Reply-To: <201402042250.s14MoTPI080268@oldred.freebsd.org> Message-ID: <alpine.BSF.2.00.1402042005420.42444@wonkity.com> References: <201402042250.s14MoTPI080268@oldred.freebsd.org> 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]); Tue, 04 Feb 2014 20:15:54 -0700 (MST) 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 <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 05 Feb 2014 03:15:55 -0000 On Tue, 4 Feb 2014, nemysis wrote: > Index: en_US.ISO8859-1/books/porters-handbook/book.xml > =================================================================== > --- en_US.ISO8859-1/books/porters-handbook/book.xml (revision 43779) > +++ en_US.ISO8859-1/books/porters-handbook/book.xml (working copy) > @@ -5096,8 +5096,16 @@ > example:</para> > > <programlisting>post-install: > - ${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/xdl</programlisting> > + ${STRIP_CMD} ${STAGEDIR}${PREFIX}/bin/${PORTNAME}</programlisting> > > + <para>If you need to strip more files, here shared libraries. > + For example:</para> Please try to avoid the informal "you". (http://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/book.html#writing-style-be-clear) Suggestion: <para>When more than one file needs to be stripped, like several shared libraries, loop through them:</para> > + > + <programlisting>post-install: > + .for l in geometry media body track world > + ${STRIP_CMD} ${STAGEDIR}${PREFIX}/lib/lib${PORTNAME}-${l}.so.0 > + .endfor</programlisting> > + > <para>Use the &man.file.1; command on the installed executable > to check whether the binary is stripped or not. If it does It's a bit redundant. Suggestion: <para>Use &man.file.1; on the installed executable to check whether it has been stripped. > not say <literal>not stripped</literal>, it is stripped. That last sentence has a double negative that makes it confusing. Assuming it is there to tell the port programmer what string to expect: Binaries that have not been stripped will be reported by &man.file.1; as <literal>not stripped</literal>. From owner-freebsd-doc@FreeBSD.ORG Wed Feb 5 03:04:17 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 36D193F6; Wed, 5 Feb 2014 03:04:17 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id DAC11147D; Wed, 5 Feb 2014 03:04:16 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s1534EL2042568; Tue, 4 Feb 2014 20:04:14 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s1534Ec9042564; Tue, 4 Feb 2014 20:04:14 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Tue, 4 Feb 2014 20:04:14 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Sergey Kandaurov <pluknet@freebsd.org> Subject: Re: en/handbook/kernelconfig: proposed corrections In-Reply-To: <20140204203748.GA16522@omg> Message-ID: <alpine.BSF.2.00.1402042002260.42444@wonkity.com> References: <20140204101604.GC83803@gamma.ukrhub.net> <20140204203748.GA16522@omg> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Tue, 04 Feb 2014 20:04:14 -0700 (MST) Cc: freebsd-doc@freebsd.org, Taras Korenko <ds@ukrhub.net> X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 05 Feb 2014 03:04:17 -0000 On Wed, 5 Feb 2014, Sergey Kandaurov wrote: > > The rest looks good to me, given that you will split the changes into > markup and content changes :). If you are talking about that whitespace change inside the programlisting, that can be considered a content change because it will be visible in the rendered output. I didn't notice other whitespace changes, but was not really looking. From owner-freebsd-doc@FreeBSD.ORG Wed Feb 5 06:58:38 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 511B7D93; Wed, 5 Feb 2014 06:58:38 +0000 (UTC) Received: from mail-ig0-x230.google.com (mail-ig0-x230.google.com [IPv6:2607:f8b0:4001:c05::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id EBEAB1623; Wed, 5 Feb 2014 06:58:37 +0000 (UTC) Received: by mail-ig0-f176.google.com with SMTP id j1so11126109iga.3 for <multiple recipients>; Tue, 04 Feb 2014 22:58:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=vyvrRww4nGQGaYg/GLCHLbNBwxc+66kWq9YkVAH/P68=; b=QyrENvtp/TVsPhh2hq8n2AOBdzI0fue9ZBdtdFsDCV6AAlQu1i6sqwQ5pGZ3jBS1p6 rkWqR/OJVWbXt0+/zz1Yi/2FhkM+3JqNLSojD1slYkF2dF82h9/EaD4mpquKLyrMfvoN gdni1fWHBm0Yh1mSEZj4fCMqjSDmXjyb9+A6LdpcfeOSn5yu6M+kVjbe5scXA6JcEgNz ILbG7jgiauQCO8o3PrQX6st7o1kQj7RO8H2QCLCX7YgQO8TS+WjYlf77MxM/kEqS5MmV WqvDNlNDnu91RKbXWzaE5h09Jazm+IaA51jvW4k9Ke6saeTqHZNt6a/J6s9JRQwYtBIB 6jDQ== MIME-Version: 1.0 X-Received: by 10.43.153.138 with SMTP id la10mr34833806icc.10.1391583517372; Tue, 04 Feb 2014 22:58:37 -0800 (PST) Received: by 10.50.67.84 with HTTP; Tue, 4 Feb 2014 22:58:37 -0800 (PST) In-Reply-To: <alpine.BSF.2.00.1402041301220.38916@wonkity.com> References: <201301251633.r0PGX15j040754@svn.freebsd.org> <5102B7A5.7030105@FreeBSD.org> <alpine.BSF.2.00.1307022125160.58832@wonkity.com> <51F0F0FE.6030208@FreeBSD.org> <alpine.BSF.2.00.1307281800200.12706@wonkity.com> <51F60897.1020005@FreeBSD.org> <alpine.BSF.2.00.1307291401500.46556@wonkity.com> <52E22240.5050501@FreeBSD.org> <alpine.BSF.2.00.1401241845360.92265@wonkity.com> <alpine.BSF.2.00.1401241856260.93615@wonkity.com> <alpine.BSF.2.00.1401241901580.93615@wonkity.com> <52F0F0EC.5090902@FreeBSD.org> <CACdU+f-mjkLTJj2TChspvs+TSGgbYo48+7c4n+OYy6ERzj-46g@mail.gmail.com> <alpine.BSF.2.00.1402041301220.38916@wonkity.com> Date: Wed, 5 Feb 2014 00:58:37 -0600 Message-ID: <CACdU+f_PYfOfZssYueKpU=benrdvXCk37HftMR-1Ty2wEHoZ2w@mail.gmail.com> Subject: Re: zfs boot manual pages From: Scot Hetzel <swhetzel@gmail.com> To: Warren Block <wblock@wonkity.com> Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-doc@freebsd.org, FreeBSD Current <freebsd-current@freebsd.org>, freebsd-fs <fs@freebsd.org>, Andriy Gapon <avg@freebsd.org> X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 05 Feb 2014 06:58:38 -0000 On Tue, Feb 4, 2014 at 2:13 PM, Warren Block <wblock@wonkity.com> wrote: > On Tue, 4 Feb 2014, Scot Hetzel wrote: > >> On Tue, Feb 4, 2014 at 7:53 AM, Andriy Gapon <avg@freebsd.org> wrote: >>> >>> >>> I've started working on manual pages for the zfs boot chain. >>> >>> Please [p]review my work in progress here: >>> https://github.com/avg-I/freebsd/compare/review;zfs-boot-man-pages >>> >>> Any additions, corrections, suggestions and other kinds of reviewing are >>> welcome. Patches and pull requests are very welcome! >>> >>> Many thanks to Warren Block for the initial review and many fixes. >> >> >> One fix for the gptzfsboot man page would be to mention that >> gptzfsboot is installed into a GPT partition of type freebsd-boot, and >> that the -i 1 refers to the GPT index for this partition. > > > We are missing that from the gptboot.8 page also. > > gptzfsboot is installed in a freebsd-boot partition, usually the > first partition on the disk. A ``protective MBR'' (see gpart(8)) is > typically used in combination with gptzfsboot. > > To install gptzfsboot on the ada0 drive: > > gpart bootcode -b /boot/pmbr -p /boot/gptzfsboot -i 1 ada0 That sounds perfect for both man pages. -- DISCLAIMER: No electrons were maimed while sending this message. Only slightly bruised. From owner-freebsd-doc@FreeBSD.ORG Wed Feb 5 07:28:04 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 9C58126D for <doc@FreeBSD.org>; Wed, 5 Feb 2014 07:28:04 +0000 (UTC) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 141A71811 for <doc@FreeBSD.org>; Wed, 5 Feb 2014 07:28:03 +0000 (UTC) Received: from alph.d.allbsd.org (p2106-ipbf2009funabasi.chiba.ocn.ne.jp [114.146.169.106]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id s157RhXn053235 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <doc@FreeBSD.org>; Wed, 5 Feb 2014 16:27:54 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.7/8.14.7) with ESMTP id s157RgCX016127 for <doc@FreeBSD.org>; Wed, 5 Feb 2014 16:27:43 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Wed, 05 Feb 2014 16:25:01 +0900 (JST) Message-Id: <20140205.162501.479797051641650212.hrs@allbsd.org> To: doc@FreeBSD.org Subject: new doceng member From: Hiroki Sato <hrs@FreeBSD.org> X-PGPkey-fingerprint: BDB3 443F A5DD B3D0 A530 FFD7 4F2C D3D8 2793 CF2D X-Mailer: Mew version 6.5 on Emacs 24.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Multipart/Signed; protocol="application/pgp-signature"; micalg=pgp-sha1; boundary="--Security_Multipart(Wed_Feb__5_16_25_01_2014_287)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender DNS name whitelisted, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Wed, 05 Feb 2014 16:27:54 +0900 (JST) X-Spam-Status: No, score=-94.3 required=13.0 tests=CONTENT_TYPE_PRESENT, RCVD_IN_PBL,RCVD_IN_RP_RNBL,SPF_SOFTFAIL,USER_IN_WHITELIST autolearn=no version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on gatekeeper.allbsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 05 Feb 2014 07:28:04 -0000 ----Security_Multipart(Wed_Feb__5_16_25_01_2014_287)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, Please welcome Warren Block <wblock@FreeBSD.org> as a new doceng member. As you know already, he has been active in updating our essential documentations such as fdp-primer and handbook as well as reviewing submitted patches for a long time. The doceng team has been working on infrastructural stuff such as XML framework improvement and maintenance of documentation packages, and would like new blood to enhance leadership on stimulating more discussion and contribution about our documentation set. I believe Warren is one of the best persons who can take the role. I hope you can also agree. The current members of doceng include me, Glen Barber <gjb@FreeBSD.org>, Marc Fonvieille <blackend@freebsd.org>, Gabor Kovesdan <gabor@FreeBSD.org>, and Warren Block <wblock@FreeBSD.org>. -- Hiroki (doceng hat on) ----Security_Multipart(Wed_Feb__5_16_25_01_2014_287)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlLx500ACgkQTyzT2CeTzy3zvwCfafk75DpNp3wSZ5Ie0vLIXpnT R60AoM/ZKumt3F9XCNx3v6Rx3MHzpkm+ =fGKO -----END PGP SIGNATURE----- ----Security_Multipart(Wed_Feb__5_16_25_01_2014_287)---- From owner-freebsd-doc@FreeBSD.ORG Wed Feb 5 10:49:47 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 3D12167C for <freebsd-doc@FreeBSD.org>; Wed, 5 Feb 2014 10:49:47 +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 C4CE819FE for <freebsd-doc@FreeBSD.org>; Wed, 5 Feb 2014 10:49:46 +0000 (UTC) Received: from fbipool-clients-45-145.fbi.h-da.de (fbipool-clients-45-145.fbi.h-da.de [141.100.45.145]) (authenticated bits=0) by mx1.bln1.prohost.de (8.14.4/8.14.4) with ESMTP id s15AnZqf016586 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <freebsd-doc@freebsd.org>; Wed, 5 Feb 2014 11:49:35 +0100 Message-ID: <52F21743.6090900@FreeBSD.org> Date: Wed, 05 Feb 2014 11:49:39 +0100 From: Benedict Reuschling <bcr@FreeBSD.org> Organization: The FreeBSD Project User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-doc@FreeBSD.org Subject: Re: new doceng member References: <20140205.162501.479797051641650212.hrs@allbsd.org> In-Reply-To: <20140205.162501.479797051641650212.hrs@allbsd.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Null-Tag: 34ccc7af63860c7e602e32213d9df356 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 05 Feb 2014 10:49:47 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Am 05.02.14 08:25, schrieb Hiroki Sato: > Hi, > > Please welcome Warren Block <wblock@FreeBSD.org> as a new doceng > member. As you know already, he has been active in updating our > essential documentations such as fdp-primer and handbook as well > as reviewing submitted patches for a long time. > > The doceng team has been working on infrastructural stuff such as > XML framework improvement and maintenance of documentation > packages, and would like new blood to enhance leadership on > stimulating more discussion and contribution about our > documentation set. I believe Warren is one of the best persons who > can take the role. I hope you can also agree. > > The current members of doceng include me, Glen Barber > <gjb@FreeBSD.org>, Marc Fonvieille <blackend@freebsd.org>, Gabor > Kovesdan <gabor@FreeBSD.org>, and Warren Block > <wblock@FreeBSD.org>. > > -- Hiroki (doceng hat on) > Congratulations Warren! Keep up the good work and good luck in your new role. Best regards Benedict -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJS8hdDAAoJEAQa31nbPD2LlY8IALfYHgxs3PzGTsO5QAyWLeiO tde5ct1Ui0U4Emg9TUD4InF6DnoLu8EGPuKNGp/y2qaSj1GqblIP/NSVMPhAqfr2 PwzdBibN8DfDy/k9OvAW5h1ih7m2Utjr/0c8NLKH7lukVF7qj+0URsRwLcILaoyK tkOpbBJeFHcGM6HiHEpoEiF2R4re/GwtzkzUHpgVH+J/5I/0RAocRV18gN3UY8SJ sFjhNmEUqSa+GgP1bya/ySTfGOyejtu1nIQCIZcA9iuUVt41sVDTD+r2JDg0Whyd Zpg7QXSzHeY4PwUI6peCFofl0bNKyNTWhDJrifiSUCgEHH7XiD8HLGWKjUZSTxY= =Mx87 -----END PGP SIGNATURE----- From owner-freebsd-doc@FreeBSD.ORG Wed Feb 5 09:22:09 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 88A54801 for <doc@freebsd.org>; Wed, 5 Feb 2014 09:22:09 +0000 (UTC) Received: from mail-ob0-x22d.google.com (mail-ob0-x22d.google.com [IPv6:2607:f8b0:4003:c01::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5230812F6 for <doc@freebsd.org>; Wed, 5 Feb 2014 09:22:09 +0000 (UTC) Received: by mail-ob0-f173.google.com with SMTP id vb8so118261obc.32 for <doc@freebsd.org>; Wed, 05 Feb 2014 01:22:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=ujKgkUhxyMLUS2kf8XxuiLTzcIESBpvefTVfhR3qxDg=; b=BV/wj5FSMFA4d2W8TfDXNbEZ6DQEILhMUAfkHRwLhw56nW/fwrd9EDXE9c5R/cUm8h YC+8OW/LiIF4YZO+3ehfNZg8oZJCsRD380xqIKW3CLy4dx/kGx4H5qPNscdbHUzlHAjx XeSzy3th7FwfWMyyG5CLmBIiQbOdX4yJoSbQYaUU7FOHYXJ1QcARBPh5zmBibLTSfkBm KRbwuvqehzo3XCehM9/RyXtGNMhp3dqziZskEzS7ve7jshxSNB3ED8HLnlobwCDv0tEz JkSubALydFfmHaTeO4AInnJt4IGeqzxcheNVLtKXnyZLUcEW6uYIIaobK41m9Mqe445V gv9g== MIME-Version: 1.0 X-Received: by 10.60.51.230 with SMTP id n6mr286653oeo.35.1391592128628; Wed, 05 Feb 2014 01:22:08 -0800 (PST) Sender: pali.gabor@gmail.com Received: by 10.182.22.44 with HTTP; Wed, 5 Feb 2014 01:22:08 -0800 (PST) In-Reply-To: <20140205.162501.479797051641650212.hrs@allbsd.org> References: <20140205.162501.479797051641650212.hrs@allbsd.org> Date: Wed, 5 Feb 2014 10:22:08 +0100 X-Google-Sender-Auth: WtUQHcBuzJwEOS21P2lP21wfGng Message-ID: <CAHnG2CwfPKrv2BayFhT70Q5qvM9MBjJbCn+BEh9wgZpvjFzFRQ@mail.gmail.com> Subject: Re: new doceng member From: Gabor Pali <pgj@FreeBSD.org> To: Warren Block <wblock@wonkity.com> Content-Type: text/plain; charset=ISO-8859-1 X-Mailman-Approved-At: Wed, 05 Feb 2014 12:56:53 +0000 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 05 Feb 2014 09:22:09 -0000 Hey, On Wed, Feb 5, 2014 at 8:25 AM, Hiroki Sato <hrs@freebsd.org> wrote: > Please welcome Warren Block <wblock@FreeBSD.org> as a new doceng > member. That is excellent news! Congratulations, Warren, I am sure you deserve this. From owner-freebsd-doc@FreeBSD.ORG Wed Feb 5 13:15:55 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 27481A1C; Wed, 5 Feb 2014 13:15:55 +0000 (UTC) Received: from mail.jr-hosting.nl (mail.jr-hosting.nl [IPv6:2a01:4f8:141:5ffd::25]) by mx1.freebsd.org (Postfix) with ESMTP id D835C16AB; Wed, 5 Feb 2014 13:15:54 +0000 (UTC) Received: from scn-lan63.snowcn.snow.nl (gw.snow.nl [213.154.248.74]) by mail.jr-hosting.nl (Postfix) with ESMTPSA id 880F23F478; Wed, 5 Feb 2014 14:15:53 +0100 (CET) Content-Type: multipart/signed; boundary="Apple-Mail=_9EC890E1-30E7-45AA-B7AE-DE882F51C9C5"; protocol="application/pgp-signature"; micalg=pgp-sha1 Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: new doceng member From: Remko Lodder <remko@FreeBSD.org> In-Reply-To: <20140205.162501.479797051641650212.hrs@allbsd.org> Date: Wed, 5 Feb 2014 14:16:01 +0100 Message-Id: <9DB0DEA1-3BD7-4FC5-8780-6B2B9BE54663@FreeBSD.org> References: <20140205.162501.479797051641650212.hrs@allbsd.org> To: Hiroki Sato <hrs@FreeBSD.org> X-Mailer: Apple Mail (2.1827) Cc: doc@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 05 Feb 2014 13:15:55 -0000 --Apple-Mail=_9EC890E1-30E7-45AA-B7AE-DE882F51C9C5 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On 05 Feb 2014, at 08:25, Hiroki Sato <hrs@FreeBSD.org> wrote: > Hi, >=20 > Please welcome Warren Block <wblock@FreeBSD.org> as a new doceng > member. As you know already, he has been active in updating our > essential documentations such as fdp-primer and handbook as well as > reviewing submitted patches for a long time. >=20 > The doceng team has been working on infrastructural stuff such as > XML framework improvement and maintenance of documentation packages, > and would like new blood to enhance leadership on stimulating more > discussion and contribution about our documentation set. I believe > Warren is one of the best persons who can take the role. I hope you > can also agree. >=20 > The current members of doceng include me, Glen Barber > <gjb@FreeBSD.org>, Marc Fonvieille <blackend@freebsd.org>, Gabor > Kovesdan <gabor@FreeBSD.org>, and Warren Block <wblock@FreeBSD.org>. >=20 > -- Hiroki (doceng hat on) Ha! Congratulations to Warren=85 the only appropriate punishment! Remko :-) --=20 /"\ Best regards, | remko@FreeBSD.org \ / Remko Lodder | remko@EFnet X http://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News --Apple-Mail=_9EC890E1-30E7-45AA-B7AE-DE882F51C9C5 Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=signature.asc Content-Type: application/pgp-signature; name=signature.asc Content-Description: Message signed with OpenPGP using GPGMail -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQIcBAEBAgAGBQJS8jmRAAoJEKjD27JZ84ywTw8P/26stweXKKr2B0DLe2cyxDOc joZCAX4IDNj7RKk3cP1G+PmyrucWOrfsbWTjo5n99uncGinXNJhBDY3HsfdaK5yE rfkVsK62WQ0j0L23eaWPRBtKcUzf8JRiKtRABSW87AOcOvuPThmfwe1F4wL+jCTG 2hpa6umi/+pgiq8F+VxGW0eNfhBYLS+8nKzbNwSfvBDznWok6J/sP85cLYHFj8/c 4cbFMo+gV2O4cGrF1OycwcDvjG31l9B+PjqLmkOhjvr0MMu/sfFdwA6MD1+XQ463 9vK0lYBT5ElLB+8dM23QaihlF+SRbTm2S2Ywt1yGE12jE/i7TzxeWL4LBB9gooXP xj/Nf1RHkRK3kCZ8Rec68k8evFn98viWyTCRvZkvg1CX5e/FZ988L3AB8gC5pgqz K+EW694KbLmUaQR1Cvn14uvpdoMdn80SBn0iLsoxllWeyMsmrxiq4pGfAK8dk8XT mMgWi5X4kRSyxWlmPl2eLTGAZzPoPo61LHlaI/5tdJ5BL20A0rh1PWEx21atlHpm at548MsmuPWjxac8+8/UN+ZLr0MfxFpNz3z1K7jkwnXrSjv5uld4X/4lr2OqjvI/ KwBfPEWuSoA2NCaNOJmx4OUfTC0Uj83Ox15XkQdyZgqKmsC1z/alBIKgg3tYJuNg aJ2BKbb7ZWVk4qLjZ/+8 =Obhe -----END PGP SIGNATURE----- --Apple-Mail=_9EC890E1-30E7-45AA-B7AE-DE882F51C9C5-- From owner-freebsd-doc@FreeBSD.ORG Wed Feb 5 23:00:01 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 0630B1D5 for <freebsd-doc@smarthost.ysv.freebsd.org>; Wed, 5 Feb 2014 23: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 B996A14A8 for <freebsd-doc@smarthost.ysv.freebsd.org>; Wed, 5 Feb 2014 23:00: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 s15N00rK033249 for <freebsd-doc@freefall.freebsd.org>; Wed, 5 Feb 2014 23:00:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s15N00EV033248; Wed, 5 Feb 2014 23:00:00 GMT (envelope-from gnats) Resent-Date: Wed, 5 Feb 2014 23:00:00 GMT Resent-Message-Id: <201402052300.s15N00EV033248@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, Ondra Knezour <knezour@weboutsourcing.cz> 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 AA744AA9 for <freebsd-gnats-submit@FreeBSD.org>; Wed, 5 Feb 2014 22:50:28 +0000 (UTC) Received: from oldred.freebsd.org (oldred.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 9418A1389 for <freebsd-gnats-submit@FreeBSD.org>; Wed, 5 Feb 2014 22:50:28 +0000 (UTC) Received: from oldred.freebsd.org ([127.0.1.6]) by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id s15MoRrK087616 for <freebsd-gnats-submit@FreeBSD.org>; Wed, 5 Feb 2014 22:50:27 GMT (envelope-from nobody@oldred.freebsd.org) Received: (from nobody@localhost) by oldred.freebsd.org (8.14.5/8.14.5/Submit) id s15MoRwu087615; Wed, 5 Feb 2014 22:50:27 GMT (envelope-from nobody) Message-Id: <201402052250.s15MoRwu087615@oldred.freebsd.org> Date: Wed, 5 Feb 2014 22:50:27 GMT From: Ondra Knezour <knezour@weboutsourcing.cz> To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: docs/186499: The Porters Handbook - better diff description X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Wed, 05 Feb 2014 23:00:01 -0000 >Number: 186499 >Category: docs >Synopsis: The Porters Handbook - better diff description >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: Wed Feb 05 23:00:00 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Ondra Knezour >Release: >Organization: >Environment: >Description: In the 4.4 Patching section of the Porters Handbook first sentence reads as "In the preparation of the port, files that have been added or changed can be picked up with a diff(1) for later feeding to patch(1)." Inexperienced porter who just started trying may not know which diff options should be used (tested on myself) and default output of diff file new_file can not be used because paths of the files are missing. >How-To-Repeat: >Fix: Someone better in both the english and ports maintaining than me may suggest change describing appropriate diff usage. I, as inexperienced person, would consider useful something like: Before changing file make copy of it. Later you can produce patch with command diff [-some-magic-options-here] file.original file.changed > patch.file which can be placed to PATCHDIR to be later fed to patch. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Thu Feb 6 00:43:26 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 C035FDBC for <doc@freebsd.org>; Thu, 6 Feb 2014 00:43:26 +0000 (UTC) Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 923B01CFE for <doc@freebsd.org>; Thu, 6 Feb 2014 00:43:26 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id ld10so1025757pab.10 for <doc@freebsd.org>; Wed, 05 Feb 2014 16:43:20 -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=0x63wFOgNcZI3//VDMaDbj2smYLQkYk8zScqFFxenJg=; b=kIsMDCEjZa4XTZ1YS98PGIpOstMeHg5MiARN6b1TpX1kl/DMdCohut5agSGNKUzFZh Bm9X8oI2zX63HAe/KAvRVvGj6NPDvEjkY7YIpwI7LbS2rudRAIePgOie5iohCoTtIBLL 6sjEXJZaUWB8LFj05Z/+DNnueFs6kfDWV8b9nCJ6NZH8ycaCz2jUFm88NgXdUxOuSTIl qSIRe2b3t5aV0lvhHvQl+JFg80tPI8yebA8Pxu+jMwC/wvoV/tyOV0SxVShaMjBukhpZ ZctMqjcMWr6l4C9nwL3UV1nZ6b+/Jw9KJqFw9+MvonCCH6rxtsZAnv9UH0urIkrGzMW3 Qk2g== X-Gm-Message-State: ALoCoQmCE/ZLIqovKX55yZvZzgeSxFbz2Z2EXxB6XOpfoiEP/WQMg7+e2leisdGIZ/ck3qUro0hP MIME-Version: 1.0 X-Received: by 10.68.37.42 with SMTP id v10mr6873125pbj.127.1391647400039; Wed, 05 Feb 2014 16:43:20 -0800 (PST) Sender: bsd-src@helfman.org Received: by 10.70.78.130 with HTTP; Wed, 5 Feb 2014 16:43:19 -0800 (PST) In-Reply-To: <9DB0DEA1-3BD7-4FC5-8780-6B2B9BE54663@FreeBSD.org> References: <20140205.162501.479797051641650212.hrs@allbsd.org> <9DB0DEA1-3BD7-4FC5-8780-6B2B9BE54663@FreeBSD.org> Date: Wed, 5 Feb 2014 16:43:19 -0800 X-Google-Sender-Auth: n4Bk4TXOy_HVGqJaYhF1h9Wk-xs Message-ID: <CAMuy=+iMc+QiwRcXWgvWQOr_Tdtx94JirUvmm5kCpkbDkJL-Kw@mail.gmail.com> Subject: Re: new doceng member From: Jason Helfman <jgh@FreeBSD.org> To: Remko Lodder <remko@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 06 Feb 2014 00:43:26 -0000 On Wed, Feb 5, 2014 at 5:16 AM, Remko Lodder <remko@freebsd.org> wrote: > > On 05 Feb 2014, at 08:25, Hiroki Sato <hrs@FreeBSD.org> wrote: > > > Hi, > > > > Please welcome Warren Block <wblock@FreeBSD.org> as a new doceng > > member. As you know already, he has been active in updating our > > essential documentations such as fdp-primer and handbook as well as > > reviewing submitted patches for a long time. > > > > The doceng team has been working on infrastructural stuff such as > > XML framework improvement and maintenance of documentation packages, > > and would like new blood to enhance leadership on stimulating more > > discussion and contribution about our documentation set. I believe > > Warren is one of the best persons who can take the role. I hope you > > can also agree. > > > > The current members of doceng include me, Glen Barber > > <gjb@FreeBSD.org>, Marc Fonvieille <blackend@freebsd.org>, Gabor > > Kovesdan <gabor@FreeBSD.org>, and Warren Block <wblock@FreeBSD.org>. > > > > -- Hiroki (doceng hat on) > Mazel Tov, Warren! You are a welcomed addition :) -jgh -- Jason Helfman | FreeBSD Committer jgh@FreeBSD.org | http://people.freebsd.org/~jgh | The Power to Serve From owner-freebsd-doc@FreeBSD.ORG Thu Feb 6 01:16:38 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 795FF704 for <freebsd-doc@freebsd.org>; Thu, 6 Feb 2014 01:16:38 +0000 (UTC) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 342B71094 for <freebsd-doc@freebsd.org>; Thu, 6 Feb 2014 01:16:37 +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 C74D555F71 for <freebsd-doc@freebsd.org>; Thu, 6 Feb 2014 01:16:28 +0000 (UTC) Message-ID: <52F2E265.3050602@allanjude.com> Date: Wed, 05 Feb 2014 20:16:21 -0500 From: Allan Jude <freebsd@allanjude.com> 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: Patch (WIP): New security front matter; new shell redirection section References: <20140202175121.16a0c264.trhodes@FreeBSD.org> <201402040800.s1480fXU006990@chilled.skew.org> <20140204075336.3e6291f2.trhodes@FreeBSD.org> In-Reply-To: <20140204075336.3e6291f2.trhodes@FreeBSD.org> X-Enigmail-Version: 1.6 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="MggfRIBWbATnLD7UFvWtCoqtjO3OnGiHE" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 06 Feb 2014 01:16:38 -0000 This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --MggfRIBWbATnLD7UFvWtCoqtjO3OnGiHE Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 2014-02-04 07:53, Tom Rhodes wrote: > On Tue, 4 Feb 2014 01:00:41 -0700 (MST) > Mike Brown <mike@skew.org> wrote: >=20 >> Tom Rhodes wrote: >>> + <para>Passwords are a necessary evil of the past. In the case= s >>> + they must be used, not only should the password be extremely >>> + complex, but also use a powerful hash mechanism to protect it. >>> + At the time of this writing, &os; supports >>> + <acronym>DES</acronym>, <acronym>MD</acronym>5, Blowfish, >>> + <acronym>SHA</acronym>256, and <acronym>SHA</acronym>512 in >>> + the <function>crypt()</function> library. The default is >>> + <acronym>SHA</acronym>512 and should not be changed backwards; >>> + however, some users like to use the Blowfish option. Each >>> + mechanism, aside from <acronym>DES</acronym>, has a unique >>> + beginning to designate the hash mechanism assigned. For the >>> + <acronym>MD</acronym>5 mechanism, the symbol is a >>> + <quote>$</quote> sign. For the <acronym>SHA</acronym>256 or >>> + <acronym>SHA</acronym>512, the symbol is <quote>$6$</quote> >>> + and Blowfish uses <quote>$2a$</quote>. Any weaker passwords >>> + should be re-hashed by asking the user to run &man.passwd.1; >>> + during their next login.</para> >> >> I get confused by this. >> >> "Any weaker passwords" immediately follows discussion of hash >> mechanisms, suggesting you actually mean to say "Any passwords >> protected by weaker hash mechanisms" ... although maybe you >> were done talking about hash mechanisms and were actually now >> back to talking about password complexity? Please clarify. >> >> Either way, how do I inspect /etc/spwd.db to find out who has=20 >> weak/not-complex-enough passwords, and what hash mechanism is in use >> for each user, so I know who needs to run passwd(1)? >> >> If this info is already in the chapter, forgive me; I am just >> going by what's in the diff. >> >> Anyway, overall it looks great. >=20 > Thanks! >=20 > You actually did remind me that, with the new version I > just put in, I added a bunch of sections but completely > dropped the ball on checking for weak passwords! >=20 > Though, the new chapter has sudo, rkhunter, and setting > up an mtree(8) based IDS and more tunables. I'll try > to work up an additional bit of cracking passwords and > the like sometime this week. Cheers, >=20 It may be worth noting that bcrypt (the blowfish based hashing algorithm) is not the same thing as blowfish the symmetric encryption system. It might just be best to call it bcrypt instead of blowfish. You might also mention the 'freebsd-update IDS' feature, which compares the SHA256 hashes of the base files against the know good values for a system upgraded with freebsd-update. --=20 Allan Jude --MggfRIBWbATnLD7UFvWtCoqtjO3OnGiHE 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/ iQIcBAEBAgAGBQJS8uJxAAoJEJrBFpNRJZKfHD4P/2xi3jQAK+dyFFhjb6Ciqt2W AuZJryruD3OoPdQcJAkVjlJvFzzJxpyUGfc0cczJQN18pPa9bXRLRFnH01NgJkXn xzfJ28N9BVRK0Fs69zzF4SgCAj3dkjNHzV7N135gNUE9nmiXh0sqk8XMSkcvEcKN x+M/hQkCVRppf+DHcUckCPTEzKQGTeg3XlPJbSiaiK0l6qZpnjo1ZcF3d/6oqH4P eFAyBCAglJi1QS4zwpfmhNVLhMy18IFhtW+ajtw2+/hZXZSbtMoaadMHn49+Antq rI0G/V4ZWKOCasXejeZZQrqTrcAuDSssd0/HmMikLMPFl8MqVyhwlUO5F75/nuXS JcXnK9QZIlHvUW/0b6xdJcr/Fw6rWlPWhAlGT8jJA6xFQaFIu5A64iOSCOyUa0wM gRHjfYPUxz6jgqUtLdE2BgFzFCHXaib2/6ugJLUrAjR2OMR3Erjovaq2vuRu20hZ G6mdRXFHocD+fDHFHxahdOMzy8BUmdIWOP+utaNktKOxt8cm/ekUD8Rac0lagZZV 3htzaS0G4FoUJoZhqMyRK4N3s28UqtWXMAcRRIpdvI2/zLMAiCk4PGjZkjK5Y7Wg 0PjHtXSPhzMteV8FL7D8wyeM3agblG9Wq6hjlIV41FqNlDOyRtj9f3tR3omCV703 0U9CM1muwY9tIy8lOxpf =8nGp -----END PGP SIGNATURE----- --MggfRIBWbATnLD7UFvWtCoqtjO3OnGiHE-- From owner-freebsd-doc@FreeBSD.ORG Thu Feb 6 03:52:57 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 205D12BC; Thu, 6 Feb 2014 03:52:57 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 6D514105D; Thu, 6 Feb 2014 03:52:56 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s163qs1p053349; Wed, 5 Feb 2014 20:52:54 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s163qs5K053346; Wed, 5 Feb 2014 20:52:54 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Wed, 5 Feb 2014 20:52:54 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Jason Helfman <jgh@FreeBSD.org> Subject: Re: new doceng member In-Reply-To: <CAMuy=+iMc+QiwRcXWgvWQOr_Tdtx94JirUvmm5kCpkbDkJL-Kw@mail.gmail.com> Message-ID: <alpine.BSF.2.00.1402052045190.53256@wonkity.com> References: <20140205.162501.479797051641650212.hrs@allbsd.org> <9DB0DEA1-3BD7-4FC5-8780-6B2B9BE54663@FreeBSD.org> <CAMuy=+iMc+QiwRcXWgvWQOr_Tdtx94JirUvmm5kCpkbDkJL-Kw@mail.gmail.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]); Wed, 05 Feb 2014 20:52:54 -0700 (MST) Cc: doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 06 Feb 2014 03:52:57 -0000 Thanks to everyone for their kind thoughts! From owner-freebsd-doc@FreeBSD.ORG Thu Feb 6 10:35:24 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 07964D9B; Thu, 6 Feb 2014 10:35:24 +0000 (UTC) Received: from boomer.ukrhub.net (boomer.ukrhub.net [94.125.121.14]) by mx1.freebsd.org (Postfix) with ESMTP id AC9491110; Thu, 6 Feb 2014 10:35:23 +0000 (UTC) Received: by boomer.ukrhub.net (Postfix, from userid 58) id BAC5C24DC24; Thu, 6 Feb 2014 12:35:15 +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 7167D24DC1F; Thu, 6 Feb 2014 12:35:10 +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 s16AZAGY050953 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 6 Feb 2014 12:35:10 +0200 (EET) (envelope-from ds@ukrhub.net) Received: (from ds@localhost) by gamma.ukrhub.net (8.14.7/8.14.7/Submit) id s16AZAHb050952; Thu, 6 Feb 2014 12:35:10 +0200 (EET) (envelope-from ds@ukrhub.net) Date: Thu, 6 Feb 2014 12:35:10 +0200 From: Taras Korenko <ds@ukrhub.net> To: Warren Block <wblock@FreeBSD.org> Subject: Re: new doceng member Message-ID: <20140206103510.GB48553@gamma.ukrhub.net> References: <20140205.162501.479797051641650212.hrs@allbsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140205.162501.479797051641650212.hrs@allbsd.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 <ds@ukrhub.net> List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 06 Feb 2014 10:35:24 -0000 On Wed, Feb 05, 2014 at 04:25:01PM +0900, Hiroki Sato wrote: > ... > Please welcome Warren Block <wblock@FreeBSD.org> as a new doceng > member. > ... It's a bit late, but, anyway: congratulations, Warren. -- WBR, Taras Korenko From owner-freebsd-doc@FreeBSD.ORG Thu Feb 6 11:39:33 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 0B414289 for <doc@freebsd.org>; Thu, 6 Feb 2014 11:39:33 +0000 (UTC) Received: from m12-11.163.com (m12-11.163.com [220.181.12.11]) by mx1.freebsd.org (Postfix) with ESMTP id 9CC09191D for <doc@freebsd.org>; Thu, 6 Feb 2014 11:39:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=163.com; s=s110527; h=Message-ID:Date:Mime-Version:From:Subject; bh=pISwZ cJCn8YG3jHD8gd5p+blxsGp2HQ4yJ8/LOs40PI=; b=Sp3Q2JKOTyvbceG7nvTvj pvGp0d0i5F2rAEQJS/WZT3Mgy59rVT7Hdw2kMTXyfgdrpG0JEd5n06tZUp67VTrt x8iIXAj2GgfqfcI8nPCWJPL7KB3PRHbk4mMt4g6i3fr0U6pnRqoortW+i+aRk8EY pBhkSKFUw47bZiYwVqXla0= Received: from 2011-20121108SO (unknown [116.10.217.50]) by smtp7 (Coremail) with SMTP id C8CowEDpP05odPNSpmOWAQ--.123S2; Thu, 06 Feb 2014 19:39:21 +0800 (CST) Message-ID: <5ddc434668b2470daf6ac53d481a2fd0@663bf188cc9348a79148eb8127cf7041> Date: Thu, 06 Feb 2014 11:39:23 GMT From: <verbhyp@163.com> To: <doc@freebsd.org> Subject: new laptop keyboards X-CM-TRANSID: C8CowEDpP05odPNSpmOWAQ--.123S2 X-Coremail-Antispam: 1Uf129KBjvJXoWxZw4DJw4DWFW5uw4ruF1xKrg_yoW5uFWrpr n8Jrs0yr4rG3W8JF909a1vyw1jqrZ5A3y2vrZF93sYqay0v34fuFnxWw4ayFnIyFnayFyY qr4UJr1kJry3JFUanT9S1TB71UUUU9DqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDUYxBIdaVFxhVjvjDU0xZFpf9x07j7VyxUUUUU= X-Originating-IP: [116.10.217.50] X-CM-SenderInfo: hyhuuxl1s6il2tof0z/1tbisAAqqVEAGiB+qAABsP MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" 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: zhangtingyouxiang@126.com List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 06 Feb 2014 11:39:33 -0000 Hi coming new keyboard: price 8-10usd/pcs HP DV7-6000 SP HP FOLI013 US HP CQ72 GR US HP CQ42 US HP DV4 US HP DV5 LA UK HP DV6000 US HP DV2000 IT US UK HP CQ50 SP HP CQ62 US HP 6720S SP ASUS K52 G51 FR GR IT US ASUS F80 SP ASUS M50 US ASUS A3000 US IT ASUS EPC7000 UK ASUS A8 TI US ASUS F2 RU ACER AS9400 RU FR ACER AS4710 UK ACER AS5516 SP IT ACER ONE A150 US ACER TM2300 SP GR TOSHIBA A300 RU P205 FR TOSHIBA P750 US C650 US A660 US SAMSUNG NP300 US N148 UK RV511 UK DELL E6420 US LENOVOL S10-2 RU LA S10 US RU X108- US LENOVO S10-2- US SONY CS -SP£¬IT£¬BR ASUS 1005-US£¬ LENOVO U310 RU LENOVO U410 RU HP 8570/6570 US HP 8570/6570 TR LENOVO G470 US ASUS 1015 LA HP DV5 RU LENOVO Z560 TR LENOVO G470 LA TOSHIBA A500 FR LENOVO G470 RU LA LG R410 BR ASUS 1015 TR ASUS 1015 FR TOSHIBA A10 SP LENOVO S10-2 TR LENOVO S10-2 UK LENOVO S10-2 IT LENOVO S10-2 RU LENOVO S10-2 LA ASUS K42 BR ACER V3 SP TOSHIBA A500 GR TOSHIBA A500 UK LENOVO G565 G560 UK LENOVO G565 G560 LA HP DV5 LA TOSHIBA A300 GR TOSHIBA A300 RU FUJITSU AH532 US LENOVO G465 G460 LA TOSHIBA A300 UK ACER AS3810 IT HP MINI10 US DELL E6420 E6320 US ACER 532H FR UK DELL N7110 KR ASUS K42 TR HP CQ72 GR TOSHIBA U500 FR ACER ONE 751 FR ACER ONE 751 TR HP M2000 GR gateway NV55 ASUS N50 TOSHIBA A10 DELL N4010 HP DV6000 ASUS N53 TOSHIBA A300 DELL 630M HP DV6, DV6-1000 black SP LENOVO G470 G475 B470 V470 black LA LENOVO G550 B550 V560 black SP TOSHIBA L800 L830 L845black LA; TOSHIBA C800 C805 C845 black LA; ACER ONE ZG5 black SP ACER ONE ZG5 A110 A150 D250 SP TOSHIBA L600 C640 C645 black LA TOSHIBA L600 C640 C645 black SP LENOVO Z470 black LA ACER ONE 532H D255 D260 black SP hp CQ43 G4 G6 black SP hp CQ42 G42 black LA hp mini 1103 mini 110-3500 MINI 110-3700 black SP HP MINI 210-3000 black SP HP MINI 1000 black LA ACER S3 S5, Aspire one 756 SP ACER ASPIRE 5810T black SP ACER ONE 751H ZA3 black SP DELL MINI 1012 MINI 1018 black SP DELL MINI 10, MINI 1010 black LA DELL Studio 14 1440 black LA SAMSUNG RV411 RC410 black LA SAMSUNG 300E5A 300V5A black LA; SONY VPC-EE black LA SONY VPC-EG LA SONY NW black SP; SONY EA LA SONY EB black SP SONY EB SP HP DM4, DV5-2000 black LA; HP 8440P black SP ACER AS5516 EMACHINE E625 black SP LENOVO G560 black LA LENOVO S10-3 black LA LENOVO G460 black SP HP DV3500 SP ,LA ACER TM8571 TM5740 TM5742 black SP DELL Inspiron 11Z 1110 black SP DELL E5400 black LA; DELL STUDIO 1535 1555 black LA; DELL E4300 black LA; LENOVO G480 black SP SONY VPC-S black SP HP MINI 110 black SP ) HP MINI 210-2000 SP ACER ONE 532H SP ASUS EPC 1000-BR£¬SP£¬FR£¬GR£¬TR ASUS F80- US£¬ ASUS 1015- UK DELL MINI10US DELL 1012 TOSHIBA NB100- US Laptop battery OEM 3/4cell 15usd/pcs original need model to quote OEM 6cell 19usd/pcs original need model to quote OEM 8/9cell 23usd/pcs original need model to quote OEM Laptop adapter 60W 4usd/pcs original 9usd/pcs 90W 6usd/pcs original 11.5usd/pcs laptop fan 4usd/pcs For more model no#,please tell me what you want ,then we will quote to you . Otherwise, we are supply original laptop adapter, laptop battery, motherboard,laptop fan, LED light, CCTV camera and LED/LCD Screen for all size model Should you have any questions, pls do not hesitate to contact me. Best regards Grace zhang +86 13669601454 +86 0775 83647855 [1]http://www.keyboard2013.com Email:zhangtingyouxiang@hotmail.com huaruishop eletronic co.,ltd Q5B136 5F huqiangbei eletronic square futian district shenzhen city guangdong province china References 1. http://www.keyboard2013.com/ From owner-freebsd-doc@FreeBSD.ORG Thu Feb 6 12:56:15 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 87D8125F for <freebsd-doc@freebsd.org>; Thu, 6 Feb 2014 12:56:15 +0000 (UTC) Received: from hapkido.dreamhost.com (hapkido.dreamhost.com [66.33.216.122]) by mx1.freebsd.org (Postfix) with ESMTP id 605BD118F for <freebsd-doc@freebsd.org>; Thu, 6 Feb 2014 12:56:15 +0000 (UTC) Received: from homiemail-a113.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by hapkido.dreamhost.com (Postfix) with ESMTP id 9B3D8DCB58 for <freebsd-doc@freebsd.org>; Thu, 6 Feb 2014 04:56:07 -0800 (PST) Received: from homiemail-a113.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a113.g.dreamhost.com (Postfix) with ESMTP id 454712005D10B; Thu, 6 Feb 2014 04:56:02 -0800 (PST) Received: from dreadnaught (ip68-100-185-59.dc.dc.cox.net [68.100.185.59]) (Authenticated sender: trhodes@fbsdsecure.org) by homiemail-a113.g.dreamhost.com (Postfix) with ESMTPA id E611B2005D10A; Thu, 6 Feb 2014 04:56:01 -0800 (PST) Date: Thu, 6 Feb 2014 07:56:01 -0500 From: Tom Rhodes <trhodes@FreeBSD.org> To: Allan Jude <freebsd@allanjude.com> Subject: Re: Patch (WIP): New security front matter; new shell redirection section Message-Id: <20140206075601.19adb2ab.trhodes@FreeBSD.org> In-Reply-To: <52F2E265.3050602@allanjude.com> References: <20140202175121.16a0c264.trhodes@FreeBSD.org> <201402040800.s1480fXU006990@chilled.skew.org> <20140204075336.3e6291f2.trhodes@FreeBSD.org> <52F2E265.3050602@allanjude.com> 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=US-ASCII Content-Transfer-Encoding: 7bit Cc: freebsd-doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 06 Feb 2014 12:56:15 -0000 On Wed, 05 Feb 2014 20:16:21 -0500 Allan Jude <freebsd@allanjude.com> wrote: > On 2014-02-04 07:53, Tom Rhodes wrote: > > On Tue, 4 Feb 2014 01:00:41 -0700 (MST) > > Mike Brown <mike@skew.org> wrote: > > > >> Tom Rhodes wrote: > >>> + <para>Passwords are a necessary evil of the past. In the cases > >>> + they must be used, not only should the password be extremely > >>> + complex, but also use a powerful hash mechanism to protect it. > >>> + At the time of this writing, &os; supports > >>> + <acronym>DES</acronym>, <acronym>MD</acronym>5, Blowfish, > >>> + <acronym>SHA</acronym>256, and <acronym>SHA</acronym>512 in > >>> + the <function>crypt()</function> library. The default is > >>> + <acronym>SHA</acronym>512 and should not be changed backwards; > >>> + however, some users like to use the Blowfish option. Each > >>> + mechanism, aside from <acronym>DES</acronym>, has a unique > >>> + beginning to designate the hash mechanism assigned. For the > >>> + <acronym>MD</acronym>5 mechanism, the symbol is a > >>> + <quote>$</quote> sign. For the <acronym>SHA</acronym>256 or > >>> + <acronym>SHA</acronym>512, the symbol is <quote>$6$</quote> > >>> + and Blowfish uses <quote>$2a$</quote>. Any weaker passwords > >>> + should be re-hashed by asking the user to run &man.passwd.1; > >>> + during their next login.</para> > >> > >> I get confused by this. > >> > >> "Any weaker passwords" immediately follows discussion of hash > >> mechanisms, suggesting you actually mean to say "Any passwords > >> protected by weaker hash mechanisms" ... although maybe you > >> were done talking about hash mechanisms and were actually now > >> back to talking about password complexity? Please clarify. > >> > >> Either way, how do I inspect /etc/spwd.db to find out who has > >> weak/not-complex-enough passwords, and what hash mechanism is in use > >> for each user, so I know who needs to run passwd(1)? > >> > >> If this info is already in the chapter, forgive me; I am just > >> going by what's in the diff. > >> > >> Anyway, overall it looks great. > > > > Thanks! > > > > You actually did remind me that, with the new version I > > just put in, I added a bunch of sections but completely > > dropped the ball on checking for weak passwords! > > > > Though, the new chapter has sudo, rkhunter, and setting > > up an mtree(8) based IDS and more tunables. I'll try > > to work up an additional bit of cracking passwords and > > the like sometime this week. Cheers, > > > > It may be worth noting that bcrypt (the blowfish based hashing > algorithm) is not the same thing as blowfish the symmetric encryption > system. It might just be best to call it bcrypt instead of blowfish. Now that is very important, I don't want people to get the wrong idea and definitely know the difference. Maybe I should reword and rework parts of this particular section to clear up any possible confusion. > > You might also mention the 'freebsd-update IDS' feature, which compares > the SHA256 hashes of the base files against the know good values for a > system upgraded with freebsd-update. Good point - I actually had that in my mind on the train, but when I began working on the IDS section, only mtree and aide came to mind. I'll have to mention that now. -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Thu Feb 6 15:29:43 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 D7A32AD2; Thu, 6 Feb 2014 15:29:43 +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 AC8DF1291; Thu, 6 Feb 2014 15:29:43 +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 s16FThiw093729; Thu, 6 Feb 2014 15:29:43 GMT (envelope-from wblock@freefall.freebsd.org) Received: (from wblock@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s16FThvY093728; Thu, 6 Feb 2014 15:29:43 GMT (envelope-from wblock) Date: Thu, 6 Feb 2014 15:29:43 GMT Message-Id: <201402061529.s16FThvY093728@freefall.freebsd.org> To: wblock@FreeBSD.org, freebsd-doc@FreeBSD.org, wblock@FreeBSD.org From: wblock@FreeBSD.org Subject: Re: docs/186499: The Porters Handbook - better diff description X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 06 Feb 2014 15:29:43 -0000 Synopsis: The Porters Handbook - better diff description Responsible-Changed-From-To: freebsd-doc->wblock Responsible-Changed-By: wblock Responsible-Changed-When: Thu Feb 6 15:29:28 UTC 2014 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=186499 From owner-freebsd-doc@FreeBSD.ORG Thu Feb 6 16:37:38 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 76A09105 for <freebsd-doc@freebsd.org>; Thu, 6 Feb 2014 16:37:38 +0000 (UTC) Received: from ipmail04.adl6.internode.on.net (ipmail04.adl6.internode.on.net [IPv6:2001:44b8:8060:ff02:300:1:6:4]) by mx1.freebsd.org (Postfix) with ESMTP id ED50019A1 for <freebsd-doc@freebsd.org>; Thu, 6 Feb 2014 16:37:37 +0000 (UTC) Received: from ppp103-111.static.internode.on.net (HELO lillith-iv.ovirt.dyndns.ws) ([150.101.103.111]) by ipmail04.adl6.internode.on.net with ESMTP; 07 Feb 2014 03:07:36 +1030 X-Envelope-From: ws@au.dyndns.ws X-Envelope-To: <freebsd-doc@freebsd.org> Received: from [172.17.17.136] (ws@predator-ii.buffyverse [172.17.17.136]) by lillith-iv.ovirt.dyndns.ws (8.14.5/8.14.5) with ESMTP id s16GbPLU057008 for <freebsd-doc@freebsd.org>; Fri, 7 Feb 2014 03:07:25 +1030 (CST) (envelope-from ws@au.dyndns.ws) Subject: Re: new doceng member From: Wayne Sierke <ws@au.dyndns.ws> To: freebsd-doc@freebsd.org In-Reply-To: <20140205.162501.479797051641650212.hrs@allbsd.org> References: <20140205.162501.479797051641650212.hrs@allbsd.org> Content-Type: text/plain; charset="ASCII" Date: Fri, 07 Feb 2014 03:07:25 +1030 Message-ID: <1391704645.2036.39.camel@predator-ii.buffyverse> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (lillith-iv.ovirt.dyndns.ws [172.17.17.142]); Fri, 07 Feb 2014 03:07:26 +1030 (CST) X-Scanned-By: MIMEDefang 2.73 on 172.17.17.142 X-Scanned-By: SpamAssassin 3.003002(2011-06-06) X-Scanned-By: ClamAV X-Spam-Score: -2.9 () ALL_TRUSTED,BAYES_00 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 06 Feb 2014 16:37:38 -0000 On Wed, 2014-02-05 at 16:25 +0900, Hiroki Sato wrote: > Hi, > > Please welcome Warren Block <wblock@FreeBSD.org> as a new doceng > member. As you know already, he has been active in updating our > essential documentations such as fdp-primer and handbook as well as > reviewing submitted patches for a long time. I have always found the information and advice provided by Warren to be particularly coherent, useful and (perhaps most importantly) easy to understand and follow. I look forward to Warren's contributions under his doceng hat! Wayne From owner-freebsd-doc@FreeBSD.ORG Thu Feb 6 21:39:28 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 D699126A; Thu, 6 Feb 2014 21:39:28 +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 A84D61828; Thu, 6 Feb 2014 21:39:28 +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 s16LdS33081487; Thu, 6 Feb 2014 21:39:28 GMT (envelope-from brueffer@freefall.freebsd.org) Received: (from brueffer@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s16LdP08081486; Thu, 6 Feb 2014 22:39:25 +0100 (CET) (envelope-from brueffer) Date: Thu, 6 Feb 2014 22:39:25 +0100 (CET) Message-Id: <201402062139.s16LdP08081486@freefall.freebsd.org> To: logan@elandsys.com, brueffer@FreeBSD.org, freebsd-doc@FreeBSD.org, brueffer@FreeBSD.org From: brueffer@FreeBSD.org Subject: Re: docs/185382: missing description in rights(4) man page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Thu, 06 Feb 2014 21:39:28 -0000 Synopsis: missing description in rights(4) man page State-Changed-From-To: open->patched State-Changed-By: brueffer State-Changed-When: Thu Feb 6 22:37:25 CET 2014 State-Changed-Why: I committed a little bigger patch that moves all instances of CAP_POLL_EVENT to CAP_EVENT, will merge to 10-STABLE soon. Thanks for the report and prodding! Responsible-Changed-From-To: freebsd-doc->brueffer Responsible-Changed-By: brueffer Responsible-Changed-When: Thu Feb 6 22:37:25 CET 2014 Responsible-Changed-Why: MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=185382 From owner-freebsd-doc@FreeBSD.ORG Fri Feb 7 06:27:33 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 19EC1B57 for <doc@freebsd.org>; Fri, 7 Feb 2014 06:27:33 +0000 (UTC) Received: from nm27-vm2.bullet.mail.ne1.yahoo.com (nm27-vm2.bullet.mail.ne1.yahoo.com [98.138.91.215]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id AD3ED15FF for <doc@freebsd.org>; Fri, 7 Feb 2014 06:27:31 +0000 (UTC) Received: from [98.138.101.128] by nm27.bullet.mail.ne1.yahoo.com with NNFMP; 07 Feb 2014 06:25:31 -0000 Received: from [98.138.84.40] by tm16.bullet.mail.ne1.yahoo.com with NNFMP; 07 Feb 2014 06:25:31 -0000 Received: from [127.0.0.1] by smtp108.mail.ne1.yahoo.com with NNFMP; 07 Feb 2014 06:25:31 -0000 X-Yahoo-Newman-Id: 408931.95598.bm@smtp108.mail.ne1.yahoo.com X-Yahoo-Newman-Property: ymail-3 X-YMail-OSG: mbHPORgVM1kpNDTIe6rINGvyv9m919xe6kYyynkAL0M4p1R ERHmcMgfQ3agSG1Jj_3NIFvd2p_17xijt9Bp.Cgfy1vaLwrZ8XeYEF6W_Y.O HwcIvNVrXAnkEeftNvJ8zdgH.ygDcmazOaSa2qgzMJYR_BO8CTtiSFI4uhDL oosOBcm8FcgBYAX4lNMGwapnKo4Rrb8h4bqgFv.VfnRMXRizHu9RwWpKWYrM xba_OR4jbbrM_u0OvoXumVCbADfWU1m2p1g_5jzeDRyHFfBzDrhIwdzHB1vQ eyEEiYlbc8swq1uviz4KB6VPZcPR5xIhPfSgyoJKiNJTDikEW1YvhJHA8YU1 iaEPkvpbhbHei8FgoeA_.k5lJaSLm9YdcGsetyI5ZUOmT3Gn4Q8IqOyqDBZH fHD3FaPLO_vpT6v84d7r7sdoz5G0uQBo0VvP8W2bySB1z4LFYBcBc2pV_ESc m9BncC7sbrUVWrOLhFvify7CzPyl5XG4H1ZE_KLHauLJAuJ2fJ0k1fs0lh5I XZkGqPdHsm_13pVuomC6kxLACraqUrJ_l9dIg33mbqw4axuL6.xhVf7JC3mT nkg-- X-Yahoo-SMTP: KQ2Dp_aswBBsEMoWsvbyXIio3muArf8weCv4Anc99N8T_iTXV87IShrVA2Dw X-Rocket-Received: from [192.168.0.101] (chiapetto.justin@77.50.245.188 with plain [63.250.193.228]) by smtp108.mail.ne1.yahoo.com with SMTP; 06 Feb 2014 22:25:31 -0800 PST Message-Id: <iebsxquh-ohiq-puhs-qjtr-eqxonkcromrv@nokiamail.com> From: Sarah R <chiapetto.justin@nokiamail.com> To: doc@freebsd.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Beverly Date: Thu, 6 Feb 2014 21:25:40 -0900 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 07 Feb 2014 06:27:33 -0000 OzzyRebdowt, are you not far from Beverly ? From owner-freebsd-doc@FreeBSD.ORG Fri Feb 7 17:00:01 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 DCB9F9EB for <freebsd-doc@smarthost.ysv.freebsd.org>; Fri, 7 Feb 2014 17: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 9DB5E1282 for <freebsd-doc@smarthost.ysv.freebsd.org>; Fri, 7 Feb 2014 17: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 s17H01eA087744 for <freebsd-doc@freefall.freebsd.org>; Fri, 7 Feb 2014 17: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 s17H01OZ087743; Fri, 7 Feb 2014 17:00:01 GMT (envelope-from gnats) Resent-Date: Fri, 7 Feb 2014 17:00:01 GMT Resent-Message-Id: <201402071700.s17H01OZ087743@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, Miklos Magyari <miklos@magyari.hu> 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 6F09C9DF for <freebsd-gnats-submit@FreeBSD.org>; Fri, 7 Feb 2014 16:59:51 +0000 (UTC) Received: from newred.freebsd.org (oldred.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 57E801277 for <freebsd-gnats-submit@FreeBSD.org>; Fri, 7 Feb 2014 16:59:51 +0000 (UTC) Received: from newred.freebsd.org ([127.0.1.6]) by newred.freebsd.org (8.14.7/8.14.7) with ESMTP id s17GxoTf044346 for <freebsd-gnats-submit@FreeBSD.org>; Fri, 7 Feb 2014 16:59:50 GMT (envelope-from nobody@newred.freebsd.org) Received: (from nobody@localhost) by newred.freebsd.org (8.14.7/8.14.7/Submit) id s17GxoOF044345; Fri, 7 Feb 2014 16:59:50 GMT (envelope-from nobody) Message-Id: <201402071659.s17GxoOF044345@newred.freebsd.org> Date: Fri, 7 Feb 2014 16:59:50 GMT From: Miklos Magyari <miklos@magyari.hu> To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: 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 <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 07 Feb 2014 17:00:01 -0000 >Number: 186537 >Category: docs >Synopsis: [patch] removing obsolete vnode (9) man page references >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: Fri Feb 07 17:00:01 UTC 2014 >Closed-Date: >Last-Modified: >Originator: Miklos Magyari >Release: 10.0-RELEASE >Organization: >Environment: FreeBSD mira 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64 >Description: vfree(9) and vbusy(9) are gone from kern/vfs_subr.c, and been replaced by inline code in vdropl and vholdl. So, the reference to these functions should be removed from the vnode manpage. Related commit: http://svnweb.freebsd.org/base/head/sys/kern/vfs_subr.c?revision=234400&view=markup >How-To-Repeat: >Fix: --- vnode.9 2014-02-06 18:55:52.000000000 +0100 +++ vnode.9.new 2014-02-07 17:52:31.000000000 +0100 @@ -69,11 +69,8 @@ .Va v_holdcnt of a vnode reaches zero then the vnode will be put on the freelist and may be reused for another file, possibly in another file system. -The transition to and from the freelist is handled by -.Xr getnewvnode 9 , -.Xr vfree 9 -and -.Xr vbusy 9 . +The transition from the freelist is handled by +.Xr getnewvnode 9 . The third is a count of the number of clients which are writing into the file. It is maintained by the >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Fri Feb 7 17:53:45 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 7DD24E12 for <doc@freebsd.org>; Fri, 7 Feb 2014 17:53:45 +0000 (UTC) Received: from upsilon.lunariffic.com (upsilon.lunariffic.com [216.227.220.84]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 4486317CC for <doc@freebsd.org>; Fri, 7 Feb 2014 17:53:44 +0000 (UTC) Received: from upsilon.lunariffic.com (upsilon.lunariffic.com [127.0.0.1]) by upsilon.lunariffic.com (8.13.8/8.13.8) with ESMTP id s17Gx6bW016952 for <doc@freebsd.org>; Fri, 7 Feb 2014 08:59:06 -0800 Received: (from echos6@localhost) by upsilon.lunariffic.com (8.13.8/8.13.8/Submit) id s17Gx6mr016949; Fri, 7 Feb 2014 08:59:06 -0800 Date: Fri, 7 Feb 2014 08:59:06 -0800 Message-Id: <201402071659.s17Gx6mr016949@upsilon.lunariffic.com> X-Authentication-Warning: upsilon.lunariffic.com: echos6 set sender to melanie_stephens@empreteckenya.com using -f To: doc@freebsd.org Subject: RE: Interesting X-PHP-Originating-Script: 544:pollGiV.php From: "Melanie Stephens" <melanie_stephens@empreteckenya.com> 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: Melanie Stephens <melanie_stephens@empreteckenya.com> List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 07 Feb 2014 17:53:45 -0000 He he Ebony chick doggystyle snatch banged [1]http://ethnicgujarat.com/atk.html References 1. http://ethnicgujarat.com/atk.html From owner-freebsd-doc@FreeBSD.ORG Fri Feb 7 20:47:30 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 D2369A88 for <doc@freebsd.org>; Fri, 7 Feb 2014 20:47:30 +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 AA3FB1723 for <doc@freebsd.org>; Fri, 7 Feb 2014 20:47:30 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id CC936B94C for <doc@freebsd.org>; Fri, 7 Feb 2014 15:47:28 -0500 (EST) From: John Baldwin <jhb@freebsd.org> To: doc@freebsd.org Subject: [PATCH] Publish the project's software license policy Date: Fri, 7 Feb 2014 15:23:58 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201402071523.58314.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 07 Feb 2014 15:47:28 -0500 (EST) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 07 Feb 2014 20:47:30 -0000 A few years ago the core team approved a software license policy for the project and announced it on developers@; however, it was never published on the website. The patch below aims to remedy that. Can someone review the XML to make sure it is correct? It at least builds ok for me locally. http://people.freebsd.org/~jhb/patches/license_policy.patch -- John Baldwin From owner-freebsd-doc@FreeBSD.ORG Fri Feb 7 22:07:08 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 E42F89D0; Fri, 7 Feb 2014 22:07:08 +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 B5A791DEC; Fri, 7 Feb 2014 22:07: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 s17M78HR064576; Fri, 7 Feb 2014 22:07:08 GMT (envelope-from brueffer@freefall.freebsd.org) Received: (from brueffer@localhost) by freefall.freebsd.org (8.14.8/8.14.8/Submit) id s17M78Uq064575; Fri, 7 Feb 2014 23:07:08 +0100 (CET) (envelope-from brueffer) Date: Fri, 7 Feb 2014 23:07:08 +0100 (CET) Message-Id: <201402072207.s17M78Uq064575@freefall.freebsd.org> To: b.heidotting@yahoo.com, brueffer@FreeBSD.org, freebsd-doc@FreeBSD.org, brueffer@FreeBSD.org From: brueffer@FreeBSD.org Subject: Re: docs/183650: [patch] Remove misleading "kldload" in sem(4) man page X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 07 Feb 2014 22:07:09 -0000 Synopsis: [patch] Remove misleading "kldload" in sem(4) man page State-Changed-From-To: open->patched State-Changed-By: brueffer State-Changed-When: Fri Feb 7 23:05:09 CET 2014 State-Changed-Why: Hi Bjorn, instead of removing the kldload bits I added a bit more context instead. I hope that works for you as well. Thanks for the contribution! Responsible-Changed-From-To: freebsd-doc->brueffer Responsible-Changed-By: brueffer Responsible-Changed-When: Fri Feb 7 23:05:09 CET 2014 Responsible-Changed-Why: MFC reminder. http://www.freebsd.org/cgi/query-pr.cgi?pr=183650 From owner-freebsd-doc@FreeBSD.ORG Fri Feb 7 22:24:18 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 CFABBDB9 for <freebsd-doc@freebsd.org>; Fri, 7 Feb 2014 22:24:18 +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 A5C081037 for <freebsd-doc@freebsd.org>; Fri, 7 Feb 2014 22:24:18 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 833CBB96B; Fri, 7 Feb 2014 17:24:16 -0500 (EST) From: John Baldwin <jhb@freebsd.org> To: freebsd-doc@freebsd.org Subject: Re: GEOM meaning Date: Fri, 7 Feb 2014 17:03:11 -0500 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20130906; KDE/4.5.5; amd64; ; ) References: <52F0C512.8080909@online.de> <52F0D58F.4040703@fjl.co.uk> <52F0D705.1090402@fjl.co.uk> In-Reply-To: <52F0D705.1090402@fjl.co.uk> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201402071703.11493.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Fri, 07 Feb 2014 17:24:16 -0500 (EST) Cc: Frank Leonhardt <frank2@fjl.co.uk> X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 07 Feb 2014 22:24:18 -0000 On Tuesday, February 04, 2014 7:03:17 am Frank Leonhardt wrote: > On 04/02/2014 11:57, Frank Leonhardt wrote: > > On 04/02/2014 10:46, Dieter Lange wrote: > >> Hi, > >> > >> having looked at quite a few sites now, not just > >> <http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom.html> > >> I still cannot find out what "GEOM" means (wrt disks etc., not > >> geography or so). It probably does not mean "Modular Disk > >> Transformation Framework". I am not talking of its use and/or > >> definitions, just the meaning of the abbreviation or word... > >> > >> Thanks+kind regards from the only person on the WWW who doesn't know... > >> DL > > > > I've always assumed it was short for (disk) geometry - i.e. converting > > logical requests to match the disk geometry. Eh? Well, back in my > > youth we did talk about the "geometr"y of DASD (disk!). For example, > > how many platters (heads), cylinders (tracks) and sectors/track were > > present. With ATA and SCSI this has become less relevant as you only > > get to see the logical structure of a disk (a load of blocks > > sequentially numbered 0...n). You may well ask why anyone would call > > these parameters "geometry", but I can't think of any other better > > name for it, nor any other word in common use for referring to them > > (other than CHT). But a disk's geometry was highly relevant because > > you (the programmer) would either be responsible for moving the head > > (via a stepper motor) to the correct track, or at the very least, you > > had to be sensitive to where the head was on the disk when optimising > > your code. > > > > I've no proof whatsoever that this is why the geom library is so > > called - it could all be a complete coincidence. I don't remember > > hearing about "geom" on System V, nor on BSD until recently (late 1990s). > > > > Regards, Frank. > > > P.S. The reason why I'm not 100% happy with the above theory is that the > geom library sits between DEVFS and the device driver (pretending to be > a device driver to DEVFS). This doesn't seem to me the logical place for > geometry translations, but it wouldn't be the first time a name has > ended up migrating to another purpose. I have always assumed it was short for geometry. One of the original uses cases for GEOM was handling partition tables, and MBR in particular is (sadly) quite tied to disk geometry since it still specifies boundaries both as LBAs and as C/H/S tuples. -- John Baldwin From owner-freebsd-doc@FreeBSD.ORG Fri Feb 7 23:02:51 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 CA31AA3D for <freebsd-doc@freebsd.org>; Fri, 7 Feb 2014 23:02:51 +0000 (UTC) Received: from mail-pd0-f181.google.com (mail-pd0-f181.google.com [209.85.192.181]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 9F497132D for <freebsd-doc@freebsd.org>; Fri, 7 Feb 2014 23:02:51 +0000 (UTC) Received: by mail-pd0-f181.google.com with SMTP id y10so3701225pdj.26 for <freebsd-doc@freebsd.org>; Fri, 07 Feb 2014 15:02:45 -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:date:message-id:subject:from :to:cc:content-type; bh=/XJ2msiB6vATzYb0IzH15VoQ0muUd6+nxiP7G8JhQUs=; b=Kpduhu+Ab/L4aCPoV2snSfPRrdP071zU8kzayAa5HxBtxpPubln5tkuf3xxUJoXpFc JNfFs+ZU81xGqr3wy+a3trfhDXYUHIxJzqwhbnSBBD5tZQisukkyv07rXM2hsuGfJGEf HhfztnLCf2/FBbVZElavkvi1BOaK2cnatYnGHXhan7MZsFejal0zZaqBb60aEWdDXVhe 76t7hOHT4GnyVvKK+MTosT3EBOPdEa7B0tNJ64CCbsDvT1Pl5HNnwtKDWiZYTCoTSQK3 8zm7cGVPuBEYzOLutfVLr8MUBdbY/ikFPUVRwSOmbhtP9L7LOVBHWNHi0IzV3NgN9ipq PTAg== X-Gm-Message-State: ALoCoQm2b6zGNx03cOkHlF7KAGV+Wc3RQQufQ78SkK4ctI28h/MY2fqfE/zv+NPSfhxH4ye8rrzm MIME-Version: 1.0 X-Received: by 10.66.232.68 with SMTP id tm4mr10696347pac.114.1391814165725; Fri, 07 Feb 2014 15:02:45 -0800 (PST) Sender: bsd-src@helfman.org Received: by 10.70.78.136 with HTTP; Fri, 7 Feb 2014 15:02:45 -0800 (PST) Date: Fri, 7 Feb 2014 15:02:45 -0800 X-Google-Sender-Auth: 7BXRoJ4ZKxxBT1VfFtYMSOjZqWI Message-ID: <CAMuy=+h1b_ibjhgf=yAGuJfSCJXgCFnyykwL7_TnSFQA_-gQoA@mail.gmail.com> Subject: Re: Error in Handbook (7.2.4.2. Chromium and Adobe(R) Flash(R) Plugin) From: Jason Helfman <jgh@FreeBSD.org> To: "Voorde ter, Frank" <frank@tervoorde.net> Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: freesd-doc <freebsd-doc@freebsd.org> X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 07 Feb 2014 23:02:51 -0000 On Tue, Feb 4, 2014 at 1:07 AM, Voorde ter, Frank <frank@tervoorde.net>wrote: > Good morning, afternoon or night, > > On https://www.freebsd.org/doc/handbook/desktop-browsers.html, at > 7.2.4.2. Chromium and Adobe(R) Flash(R) Plugin, the following sentence can be > read: > > (...) is similar to the the instructions in Section 7.2.1.1, "Firefox and > Java(tm) Plugin". > > I think this is obviously incorrect, due to a copy-and-paste error. I > think it must be: > > (...) is similar to the the instructions in Section 7.2.1.2, "Firefox and > Adobe(R) Flash(R) Plugin". > > I hope this helps to make the Handbook closer to perfect. > > Yours sincerely, > > Frank ter Voorde > > _______________________________________________ > 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" I've committed an update for this issue. 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 Fri Feb 7 23:44:11 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 D8EC2199 for <doc@freebsd.org>; Fri, 7 Feb 2014 23:44:11 +0000 (UTC) Received: from hosting.omkc.ru (hosting.omkc.ru [217.25.208.58]) by mx1.freebsd.org (Postfix) with ESMTP id 83439165A for <doc@freebsd.org>; Fri, 7 Feb 2014 23:44:10 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by hosting.omkc.ru (Postfix) with ESMTP id 93E933E638B for <doc@freebsd.org>; Sat, 8 Feb 2014 06:36:19 +0700 (OMST) X-Virus-Scanned: Debian amavisd-new at hosting.omkc.ru Received: from hosting.omkc.ru ([127.0.0.1]) by localhost (hosting.omkc.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GwEfSTb6D1Qf for <doc@freebsd.org>; Sat, 8 Feb 2014 06:36:19 +0700 (OMST) Received: by hosting.omkc.ru (Postfix, from userid 33) id 27A5C3E6398; Sat, 8 Feb 2014 06:36:19 +0700 (OMST) To: doc@freebsd.org Subject: Hi X-PHP-Originating-Script: 33:infox49x.php From: "Celeste Avila" <celeste_avila@ROZAVETROV55.RU> X-Priority: 3 (Normal) Message-Id: <20140207233619.27A5C3E6398@hosting.omkc.ru> Date: Sat, 8 Feb 2014 06:36:19 +0700 (OMST) 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: Celeste Avila <celeste_avila@ROZAVETROV55.RU> List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 07 Feb 2014 23:44:11 -0000 Hello Little anal virgin gets fucked [1]http://farnostvozice.vlaskovi.cz/images/awr.html References 1. http://farnostvozice.vlaskovi.cz/images/awr.html From owner-freebsd-doc@FreeBSD.ORG Sat Feb 8 05:01:47 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 7305AE92 for <freebsd-doc@freebsd.org>; Sat, 8 Feb 2014 05:01:47 +0000 (UTC) Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 3C8D11811 for <freebsd-doc@freebsd.org>; Sat, 8 Feb 2014 05:01:47 +0000 (UTC) Received: by mail-pd0-f179.google.com with SMTP id fp1so3607815pdb.10 for <freebsd-doc@freebsd.org>; Fri, 07 Feb 2014 21:01:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ardiefox.me; s=google; h=from:content-type:subject:date:message-id:to:mime-version; bh=H/JUiEOhCTYAIRaNjofN0Cqh9/Qo8az0HmeW7N45S2g=; b=OaIbkZg/Qu8Biz8zpZ5sm0sQ1ieiiRcJ43gpeU+8nC8X7JSowugzPnXv7d82mb2wxi X7qZ7cPtSM+KOWbgEanmDMfU6D9v6Yb6lqGynPoy6GgYvs1Pun6pac+rhwuJXwAli4NO r1EVjfUa+f9IU5HhB8FqLnzKZS0THSeYCKcts= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:subject:date:message-id:to :mime-version; bh=H/JUiEOhCTYAIRaNjofN0Cqh9/Qo8az0HmeW7N45S2g=; b=NJX4+wqQvZuKwr/l0GEa3z7TeCo0P5vyIc0oMhCElC4jLnT9EKhfIhcwcoq3vVkafI 9HXPuAIPw8b0LkvSXNWf41Q+8w1RdgnMGbTwUhii8q8RWWdaXL26oyoJ5Q9ZNiOAtroj WIE+LaS5QnNAT4jbYkO5IaBTPATy2BlEpsHyZynOVCjIUurJ3X3gkLRVqL1wBpOpXrZR /2bQ4BZXsEMrbuTMU+LFXpbddXc16mJz0ckA/4w29AMQmQearD6IAlUUJ1Ldyk654jkk hNykNFBvVt9MbZJk8y4d1BrwK3XETrlgy+IK+6z43a7KGdszCThUwQOzXIO2tpe1n3qC +Ihw== X-Gm-Message-State: ALoCoQkG3zNx28Htc0DZisaNqjum/tL7MWiwG5CpBLrHjBPqz3fAp75y3Iw1LJbeRmRaKVwqBcax X-Received: by 10.66.138.40 with SMTP id qn8mr12352443pab.154.1391835706409; Fri, 07 Feb 2014 21:01:46 -0800 (PST) Received: from [165.194.17.176] ([165.194.17.176]) by mx.google.com with ESMTPSA id fk4sm49768242pab.23.2014.02.07.21.01.44 for <freebsd-doc@freebsd.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 07 Feb 2014 21:01:45 -0800 (PST) From: Ardie Hyun Hwang <iam@ardiefox.me> Subject: The FreeBSD Korean Documentation Project Date: Sat, 8 Feb 2014 14:01:40 +0900 Message-Id: <7110AC03-A25B-4DF3-A1F1-5EB4DBF19F70@ardiefox.me> To: freebsd-doc@FreeBSD.org Mime-Version: 1.0 (Apple Message framework v1283) X-Mailer: Apple Mail (2.1283) 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 <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 08 Feb 2014 05:01:47 -0000 Hi all. We, newly gathered members of Korean BSD User Group, are about to fully = reconstruct our group from ashes, for reuniting scattered BSD users in = Korea. And as a first step toward that goal, we decided to restart = working on abandoned Korean Documentation Project. The reason of this message is to request help on reviving the project. = We have already tried contacting DocKR mailing list -- = doc@kr.FreeBSD.org -- and got nothing but a delivery failure; looks like = the former localizing team is totally dismissed or so. We wish to have a warm guidance from you doc@ people, as we do not have = much experience in participating this big project. Thank you. -- Ardie Hyun Hwang ---------------- email: iam@ardiefox.me mobile: +82-10-I-AM-ARDIE From owner-freebsd-doc@FreeBSD.ORG Sat Feb 8 13:59:52 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 CF755A5E for <freebsd-doc@FreeBSD.org>; Sat, 8 Feb 2014 13:59:52 +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 56CB11D74 for <freebsd-doc@FreeBSD.org>; Sat, 8 Feb 2014 13:59:51 +0000 (UTC) Received: from Voyager.local (p4FC70C86.dip0.t-ipconnect.de [79.199.12.134]) (authenticated bits=0) by mx1.bln1.prohost.de (8.14.4/8.14.4) with ESMTP id s18Dxm3Y010510 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for <freebsd-doc@freebsd.org>; Sat, 8 Feb 2014 14:59:48 +0100 Message-ID: <52F63858.3010202@FreeBSD.org> Date: Sat, 08 Feb 2014 14:59:52 +0100 From: Benedict Reuschling <bcr@FreeBSD.org> 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: [PATCH] Use a bullet list for general policies References: <201401311421.31347.jhb@freebsd.org> In-Reply-To: <201401311421.31347.jhb@freebsd.org> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Null-Tag: 722a0d985a0b0cb5e8aeca325455b96d X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 08 Feb 2014 13:59:53 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 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 @@ > > <h2><b>General Policies</b></h2> > > -<p>Here you will find various things such as the -<a > href="new-account.html">New Account Creation Procedure</a>, -the > -<a href="expire-bits.html">Commit Bit Expiration Policy</a>, -the > -<a href="bylaws.html">Core Bylaws</a>, -the -<a > href="resources.html">Commit Bit and Project Resources Policy</a>, > -<a href="core-vote.html">Core's Voting Procedures</a>, -the -<a > href="fortunes.html">Fortune File Policy</a>, -the -<a > href="i18n.html">Internationalization Policy</a>, -the -<a > href="data.html">User Data Policy</a>, -the -<a > href="hats.html">Hats Term Limits Policy</a>, -and the -<a > href="../doc/en_US.ISO8859-1/articles/pr-guidelines/">Problem > Report Handling Guidelines</a>.</p> +<ul> + <li><a > href="new-account.html">New Account Creation Procedure</a></li> + > <li><a href="expire-bits.html">Commit Bit Expiration > Policy</a></li> + <li><a href="bylaws.html">Core Bylaws</a></li> + > <li><a href="resources.html">Commit Bit and Project Resources > Policy</a></li> + <li><a href="core-vote.html">Core's Voting > Procedures</a></li> + <li><a href="fortunes.html">Fortune File > Policy</a></li> + <li><a href="i18n.html">Internationalization > Policy</a></li> + <li><a href="data.html">User Data > Policy</a></li> + <li><a href="hats.html">Hats Term Limits > Policy</a></li> + <li><a > href="../doc/en_US.ISO8859-1/articles/pr-guidelines/">Problem > Report Handling Guidelines</a></li> +</ul> > > <h2><b>The FreeBSD Documentation Project</b></h2> > > 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. in general, I like the bullet list better than the original list of links in a long setence. Regards Benedict -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBCgAGBQJS9jhYAAoJEAQa31nbPD2LBFEIAMHEkvOMjr0hr4ImrRt+Gemm MJf9jTzB3kqEWEe4ZfvHbg0B3/CGk8Ni86d50p3t5xDEQCzK/We7JHMDkOjS9iOr xIT2KW4aaFgLKWkGUZdNTazhWKvBxDIA5JaBNGtG8073uF6JPJBfWnljsIiEKOAb x2C5L2tpVb8Yd5W5Oav/sM7OxjwmFUMTBHjjaepwDB0wHiwqviyrA3pjLrGnGNba YyqLXtRD43EomFb7jUD4b5ypCaTv50giCETkf/qwJ7ZlX/wgVbuG/r1VND70J2IH m7j+zzf0pnAN6Fg5G7Vb+NxiMm54fsfm1QQtUh1eo6KHUPLgdXh1S2+EKyg+hVw= =O8Ug -----END PGP SIGNATURE----- From owner-freebsd-doc@FreeBSD.ORG Sat Feb 8 14:48:05 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 83A5FC2D for <doc@freebsd.org>; Sat, 8 Feb 2014 14:48:05 +0000 (UTC) Received: from bewilderbeast.blackhelicopters.org (mwlucas-2-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:b9c::2]) (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 ADCB511FA for <doc@freebsd.org>; Sat, 8 Feb 2014 14:48:04 +0000 (UTC) Received: from bewilderbeast.blackhelicopters.org (localhost [127.0.0.1]) by bewilderbeast.blackhelicopters.org (8.14.7/8.14.7) with ESMTP id s18Em27h003295 for <doc@freebsd.org>; Sat, 8 Feb 2014 09:48:02 -0500 (EST) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: (from mwlucas@localhost) by bewilderbeast.blackhelicopters.org (8.14.7/8.14.7/Submit) id s18Em29C003294 for doc@freebsd.org; Sat, 8 Feb 2014 09:48:02 -0500 (EST) (envelope-from mwlucas) Date: Sat, 8 Feb 2014 09:48:01 -0500 From: "Michael W. Lucas" <mwlucas@michaelwlucas.com> To: doc@freebsd.org Subject: http://www.freebsd.org/features.html Message-ID: <20140208144801.GA3286@bewilderbeast.blackhelicopters.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.22 (2013-10-16) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (bewilderbeast.blackhelicopters.org [127.0.0.1]); Sat, 08 Feb 2014 09:48:02 -0500 (EST) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 08 Feb 2014 14:48:05 -0000 Shouldn't $SUBJECT mention 10.0? Looks like it got missed. (Yeah, yeah, I know, send patches... I acknowledge that I suck.) ==ml -- Michael W. Lucas - mwlucas@michaelwlucas.com, Twitter @mwlauthor http://www.MichaelWLucas.com/, http://blather.MichaelWLucas.com/ Absolute OpenBSD 2/e - http://www.nostarch.com/openbsd2e coupon code "ILUVMICHAEL" gets you 30% off & helps me. From owner-freebsd-doc@FreeBSD.ORG Sat Feb 8 15:57:37 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 51917ED9; Sat, 8 Feb 2014 15:57:37 +0000 (UTC) Received: from hapkido.dreamhost.com (hapkido.dreamhost.com [66.33.216.122]) by mx1.freebsd.org (Postfix) with ESMTP id 09884169D; Sat, 8 Feb 2014 15:57:33 +0000 (UTC) Received: from homiemail-a36.g.dreamhost.com (caiajhbdccac.dreamhost.com [208.97.132.202]) by hapkido.dreamhost.com (Postfix) with ESMTP id BF692DCCB3; Sat, 8 Feb 2014 07:57:32 -0800 (PST) Received: from homiemail-a36.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTP id BA80B778057; Sat, 8 Feb 2014 07:57:27 -0800 (PST) Received: from dreadnaught (ip68-100-185-59.dc.dc.cox.net [68.100.185.59]) (Authenticated sender: trhodes@fbsdsecure.org) by homiemail-a36.g.dreamhost.com (Postfix) with ESMTPA id 374CD77806E; Sat, 8 Feb 2014 07:57:27 -0800 (PST) Date: Sat, 8 Feb 2014 10:57:26 -0500 From: Tom Rhodes <trhodes@FreeBSD.org> To: doc@FreeBSD.org Subject: [WIP]: Splitting up the porters handbook Message-Id: <20140208105726.3e1b52d8.trhodes@FreeBSD.org> 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=US-ASCII Content-Transfer-Encoding: 7bit Cc: doceng@FreeBSD.org, port-mngr@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 08 Feb 2014 15:57:37 -0000 Hi, 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: http://people.freebsd.org/~trhodes/NEW-PH.diff 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, 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, -- Tom Rhodes From owner-freebsd-doc@FreeBSD.ORG Sat Feb 8 16:47:12 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 A21FDF46; Sat, 8 Feb 2014 16:47:12 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 51A731B22; Sat, 8 Feb 2014 16:47:11 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id s18GlAAd036307; Sat, 8 Feb 2014 09:47:10 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id s18GlAX8036304; Sat, 8 Feb 2014 09:47:10 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Sat, 8 Feb 2014 09:47:09 -0700 (MST) From: Warren Block <wblock@wonkity.com> To: Tom Rhodes <trhodes@FreeBSD.org> Subject: Re: [WIP]: Splitting up the porters handbook In-Reply-To: <20140208105726.3e1b52d8.trhodes@FreeBSD.org> Message-ID: <alpine.BSF.2.00.1402080935260.35659@wonkity.com> References: <20140208105726.3e1b52d8.trhodes@FreeBSD.org> 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]); Sat, 08 Feb 2014 09:47:10 -0700 (MST) Cc: port-mngr@FreeBSD.org, doc@FreeBSD.org, doceng@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 08 Feb 2014 16:47:12 -0000 On Sat, 8 Feb 2014, Tom Rhodes wrote: > Hi, > > 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: > > http://people.freebsd.org/~trhodes/NEW-PH.diff > > 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, > > 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, Can't speak for others, but I agree. It's something that has needed to be done for a while now. Based on experience from the Handbook, I suggest fixing the titles in the sections that will become chapters, then using those actual titles for the chapter directory names. With the Handbook, the names don't match and it is difficult to find sections for editing. So: The title of "Making a New Port Yourself" becomes "Making a New Port" (or "Creating a New Port"), and then the chapter directory is making-a-new-port, or creating-a-new-port. The length of these is not as critical as making them consistent with the title. "Testing Your Port" becomes "Testing the Port". "Upgrading an Individual Port" becomes "Upgrading a Port". "Ports Security" becomes just "Security". The chapter entries in SRCS should be in the order they appear in the book. From owner-freebsd-doc@FreeBSD.ORG Sat Feb 8 17:04:42 2014 Return-Path: <owner-freebsd-doc@FreeBSD.ORG> 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 BD8622ED; Sat, 8 Feb 2014 17:04:42 +0000 (UTC) Received: from homiemail-a54.g.dreamhost.com (caiajhbdcagg.dreamhost.com [208.97.132.66]) by mx1.freebsd.org (Postfix) with ESMTP id 981651C84; Sat, 8 Feb 2014 17:04:42 +0000 (UTC) Received: from homiemail-a54.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a54.g.dreamhost.com (Postfix) with ESMTP id 36C854012241C; Sat, 8 Feb 2014 09:04:36 -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 8FA954012241B; Sat, 8 Feb 2014 09:04:35 -0800 (PST) Date: Sat, 8 Feb 2014 12:04:34 -0500 From: Tom Rhodes <trhodes@FreeBSD.org> To: Warren Block <wblock@wonkity.com> Subject: Re: [WIP]: Splitting up the porters handbook Message-Id: <20140208120434.213635b2.trhodes@FreeBSD.org> In-Reply-To: <alpine.BSF.2.00.1402080935260.35659@wonkity.com> References: <20140208105726.3e1b52d8.trhodes@FreeBSD.org> <alpine.BSF.2.00.1402080935260.35659@wonkity.com> 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=US-ASCII Content-Transfer-Encoding: 7bit Cc: port-mngr@FreeBSD.org, doc@FreeBSD.org, doceng@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Documentation project <freebsd-doc.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-doc/> List-Post: <mailto:freebsd-doc@freebsd.org> List-Help: <mailto:freebsd-doc-request@freebsd.org?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-doc>, <mailto:freebsd-doc-request@freebsd.org?subject=subscribe> X-List-Received-Date: Sat, 08 Feb 2014 17:04:42 -0000 On Sat, 8 Feb 2014 09:47:09 -0700 (MST) Warren Block <wblock@wonkity.com> wrote: > On Sat, 8 Feb 2014, Tom Rhodes wrote: > > > Hi, > > > > 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: > > > > http://people.freebsd.org/~trhodes/NEW-PH.diff > > > > 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, > > > > 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, > > Can't speak for others, but I agree. It's something that has needed to > be done for a while now. Based on experience from the Handbook, I > suggest fixing the titles in the sections that will become chapters, > then using those actual titles for the chapter directory names. With > the Handbook, the names don't match and it is difficult to find > sections for editing. > > So: > > The title of "Making a New Port Yourself" becomes "Making a New Port" > (or "Creating a New Port"), and then the chapter directory is > making-a-new-port, or creating-a-new-port. The length of these is not > as critical as making them consistent with the title. > > "Testing Your Port" becomes "Testing the Port". > "Upgrading an Individual Port" becomes "Upgrading a Port". > "Ports Security" becomes just "Security". > > The chapter entries in SRCS should be in the order they appear in the > book. All good points - thanks! I'll put that in the list of things to do before commit. Most of what I did was automated, from creating a Makefile template to using csplit to divide up the chapters. The more manual stuff, things I can't do in a few moments, well, that's waiting for feedback. I'll wait for more and then continue, cheers! -- Tom Rhodes