From owner-freebsd-doc@FreeBSD.ORG Sun Jul 14 08:22:50 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id D47E54F2 for ; Sun, 14 Jul 2013 08:22:50 +0000 (UTC) (envelope-from gabor@t-hosting.hu) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id 8EE53938 for ; Sun, 14 Jul 2013 08:22:49 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id 573C514D2403 for ; Sun, 14 Jul 2013 10:22:42 +0200 (CEST) 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 RFCsfs-QivS9 for ; Sun, 14 Jul 2013 10:22:41 +0200 (CEST) Received: from [192.168.1.117] (catv-80-99-23-232.catv.broadband.hu [80.99.23.232]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id 2FC6414D2400 for ; Sun, 14 Jul 2013 10:22:41 +0200 (CEST) Message-ID: <51E25FCE.9020405@t-hosting.hu> Date: Sun, 14 Jul 2013 10:22:38 +0200 From: =?ISO-8859-1?Q?G=E1bor_K=F6vesd=E1n?= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20100101 Thunderbird/23.0a2 MIME-Version: 1.0 To: doc@freebsd.org Subject: Re: RFC: Upgrading to DocBook 5.0 References: <519FA4FE.4030305@FreeBSD.org> In-Reply-To: <519FA4FE.4030305@FreeBSD.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2013 08:22:50 -0000 Some more things: - Admonitions (top, note, warning boxes) look quite strange in lists and such places. I think we should add a policy to avoid them and start changing the markup. - We extensively use markup in titles, which later renders with a different font. E.g. we mark the X of 9.X as replaceable or we mark up root as a username. I think that such rendering should be avoided in titles and the easiest and cleanest way to do so would be not using such markup in titles. - Currently, we use the CALS table model in the documentation, while DocBook also supports the HTML table model. It has a more simple syntax and more rendering features in the DocBook stylesheets. Another advantage is that by using it, we would have only one table semantics in docs + web. Any objection to changing to the HTML table model? - Some lists have their own title, while the preceding text usually introduces well what is enumerated in the list. I find the rendered title quite strange between this text and the list. Besides, I don't remember having seen technical books that use such titles. My suggestion is to simple remove them. Any objection or better idea? Thanks, Gabor From owner-freebsd-doc@FreeBSD.ORG Sun Jul 14 09:20:00 2013 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]) by hub.freebsd.org (Postfix) with ESMTP id BC273C72 for ; Sun, 14 Jul 2013 09:20:00 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 895B1AAA for ; Sun, 14 Jul 2013 09:20:00 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r6E9K0fP098520 for ; Sun, 14 Jul 2013 09:20:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6E9K0Bv098519; Sun, 14 Jul 2013 09:20:00 GMT (envelope-from gnats) Resent-Date: Sun, 14 Jul 2013 09:20:00 GMT Resent-Message-Id: <201307140920.r6E9K0Bv098519@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, "r4721@tormail.org" Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EE25DC59 for ; Sun, 14 Jul 2013 09:17:05 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from oldred.freebsd.org (oldred.freebsd.org [8.8.178.121]) by mx1.freebsd.org (Postfix) with ESMTP id DFACEA9C for ; Sun, 14 Jul 2013 09:17:05 +0000 (UTC) Received: from oldred.freebsd.org ([127.0.1.6]) by oldred.freebsd.org (8.14.5/8.14.7) with ESMTP id r6E9H5MR087918 for ; Sun, 14 Jul 2013 09:17:05 GMT (envelope-from nobody@oldred.freebsd.org) Received: (from nobody@localhost) by oldred.freebsd.org (8.14.5/8.14.5/Submit) id r6E9H587087902; Sun, 14 Jul 2013 09:17:05 GMT (envelope-from nobody) Message-Id: <201307140917.r6E9H587087902@oldred.freebsd.org> Date: Sun, 14 Jul 2013 09:17:05 GMT From: "r4721@tormail.org" To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Subject: docs/180551: [patch] document NULL encryption algorithm in geli(8) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2013 09:20:00 -0000 >Number: 180551 >Category: docs >Synopsis: [patch] document NULL encryption algorithm in geli(8) >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 Jul 14 09:20:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: r4721@tormail.org >Release: >Organization: >Environment: >Description: i had wished for years for a no-op encryption algorithm in geli so i could just use data integrity verification, only to find it existed all along. document this so that others can find it as well. >How-To-Repeat: >Fix: Patch attached with submission follows: Index: sbin/geom/class/eli/geli.8 =================================================================== --- sbin/geom/class/eli/geli.8 (revision 253282) +++ sbin/geom/class/eli/geli.8 (working copy) @@ -277,11 +277,14 @@ .Nm AES-XTS , .Nm AES-CBC , .Nm Blowfish-CBC , -.Nm Camellia-CBC +.Nm Camellia-CBC , +.Nm 3DES-CBC , and -.Nm 3DES-CBC . +.Nm NULL . The default and recommended algorithm is .Nm AES-XTS . +.Nm NULL +is unencrypted. .It Fl i Ar iterations Number of iterations to use with PKCS#5v2. If this option is not specified, >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Sun Jul 14 12:52:34 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id DF49D95D for ; Sun, 14 Jul 2013 12:52:34 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 87EFEFCF for ; Sun, 14 Jul 2013 12:52:34 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6ECqXmV060969; Sun, 14 Jul 2013 06:52:33 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6ECqWgj060966; Sun, 14 Jul 2013 06:52:33 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 14 Jul 2013 06:52:32 -0600 (MDT) From: Warren Block To: =?ISO-8859-15?Q?G=E1bor_K=F6vesd=E1n?= Subject: Re: RFC: Upgrading to DocBook 5.0 In-Reply-To: <51E25FCE.9020405@t-hosting.hu> Message-ID: References: <519FA4FE.4030305@FreeBSD.org> <51E25FCE.9020405@t-hosting.hu> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3512871622-1022815614-1373806353=:60846" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 14 Jul 2013 06:52:33 -0600 (MDT) Cc: doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2013 12:52:34 -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-1022815614-1373806353=:60846 Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT On Sun, 14 Jul 2013, Gábor Kövesdán wrote: > Some more things: > > - Admonitions (top, note, warning boxes) look quite strange in lists and such > places. I think we should add a policy to avoid them and start changing the > markup. Admonitions are overused in some places. They are visually jarring, often moreso than the tip or warning deserves. A link to an example of this particular problem would be helpful to see what you mean, though. > - We extensively use markup in titles, which later renders with a different > font. E.g. we mark the X of 9.X as replaceable or we mark up root as a > username. I think that such rendering should be avoided in titles and the > easiest and cleanest way to do so would be not using such markup in titles. Please expand--what is the problem with differing fonts in titles? I can see this both ways, but the text of a title being consistent with the rendering in the body seems like an advantage. > - Currently, we use the CALS table model in the documentation, while DocBook > also supports the HTML table model. It has a more simple syntax and more > rendering features in the DocBook stylesheets. Another advantage is that by > using it, we would have only one table semantics in docs + web. Any objection > to changing to the HTML table model? An example would be useful here, also. For compatibility with the rest of the world, we should probably stick with the most common usage. > - Some lists have their own title, while the preceding text usually > introduces well what is enumerated in the list. I find the rendered title > quite strange between this text and the list. Besides, I don't remember > having seen technical books that use such titles. My suggestion is to simple > remove them. Any objection or better idea? Please give an example here, also. All of these suggestions seem to be style changes that are not necessarily tied to the change to DocBook 5, or maybe changes that are not possible until after the conversion. Unless they're required, it may be best to wait until after the conversion. --3512871622-1022815614-1373806353=:60846-- From owner-freebsd-doc@FreeBSD.ORG Sun Jul 14 13:25:40 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 679E9C37 for ; Sun, 14 Jul 2013 13:25:40 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id DEF1CFE for ; Sun, 14 Jul 2013 13:25:39 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id 2343614D242C; Sun, 14 Jul 2013 15:25:38 +0200 (CEST) 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 cnX916DOUQXN; Sun, 14 Jul 2013 15:25:36 +0200 (CEST) Received: from [192.168.1.106] (catv-80-99-23-232.catv.broadband.hu [80.99.23.232]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id 30C3B14D2403; Sun, 14 Jul 2013 15:25:36 +0200 (CEST) Message-ID: <51E2A6C9.1070301@FreeBSD.org> Date: Sun, 14 Jul 2013 15:25:29 +0200 From: Gabor Kovesdan User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:23.0) Gecko/20100101 Thunderbird/23.0 MIME-Version: 1.0 To: Warren Block Subject: Re: RFC: Upgrading to DocBook 5.0 References: <519FA4FE.4030305@FreeBSD.org> <51E25FCE.9020405@t-hosting.hu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2013 13:25:40 -0000 Em 14-07-2013 14:52, Warren Block escreveu: > On Sun, 14 Jul 2013, Gábor Kövesdán wrote: > >> Some more things: >> >> - Admonitions (top, note, warning boxes) look quite strange in lists >> and such places. I think we should add a policy to avoid them and >> start changing the markup. > > Admonitions are overused in some places. They are visually jarring, > often moreso than the tip or warning deserves. A link to an example > of this particular problem would be helpful to see what you mean, though. For example here: http://www.freebsd.org/doc/en/books/handbook/history.html It breaks the list. It is even worse in PDF rendering since there are page boundaries and it breaks the page up to two parts. > >> - We extensively use markup in titles, which later renders with a >> different font. E.g. we mark the X of 9.X as replaceable or we mark >> up root as a username. I think that such rendering should be avoided >> in titles and the easiest and cleanest way to do so would be not >> using such markup in titles. > > Please expand--what is the problem with differing fonts in titles? I > can see this both ways, but the text of a title being consistent with > the rendering in the body seems like an advantage. Apart from the ugly visual outlook, it is not conventional in books and as such, it is just bothering and confusing for the reader. It breaks the information flow. Typographyc conventions serve for nice visual outlook and usability. The typesetting should facilitate reading and not difficulting it. If we want to publish a high-quality print edition of Handbook, we must follow the conventions, otherwise it won't be a serious publication. > >> - Currently, we use the CALS table model in the documentation, while >> DocBook also supports the HTML table model. It has a more simple >> syntax and more rendering features in the DocBook stylesheets. >> Another advantage is that by using it, we would have only one table >> semantics in docs + web. Any objection to changing to the HTML table >> model? > > An example would be useful here, also. For compatibility with the > rest of the world, we should probably stick with the most common usage. Most common is very relative. HTML uses exclusively the HTML table model, hence the name. CALS is older and quite common in the SGML/XML world. Both are supported in DocBook and we currently use CALS. Earlier there was no other option in DocBook. Using exclusively HTML tables would reduce the used table models to one. Examples: just google for CALS table and HTML table, both are documented extensively. > >> - Some lists have their own title, while the preceding text usually >> introduces well what is enumerated in the list. I find the rendered >> title quite strange between this text and the list. Besides, I don't >> remember having seen technical books that use such titles. My >> suggestion is to simple remove them. Any objection or better idea? > > Please give an example here, also. http://www.freebsd.org/doc/en/books/handbook/bsdinstall-pre.html Look at 2.3.3. There's a semicolon at the end of the last paragraph and list title is just floating there in the middle. This type of titles breaks the flow of the text and doesn't facilitate reading. > > All of these suggestions seem to be style changes that are not > necessarily tied to the change to DocBook 5, or maybe changes that are > not possible until after the conversion. Unless they're required, it > may be best to wait until after the conversion. Not in theory but theory doesn't always match practice. I'm working on the DocBook 5 change to provide better rendering and support publishing print versions. I'm evaluating and customizing two different rendering methods and I have to see where we can get with each. Practically I can do it by eliminating the confusing and bothering factors. This is sometimes done by customizing the rendering and sometimes by feeding back the results to the concrete documents. Gabor From owner-freebsd-doc@FreeBSD.ORG Sun Jul 14 16:02:39 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B428172C; Sun, 14 Jul 2013 16:02:39 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 6B06C790; Sun, 14 Jul 2013 16:02:39 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6EG2cMd061706; Sun, 14 Jul 2013 10:02:38 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6EG2cr2061703; Sun, 14 Jul 2013 10:02:38 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 14 Jul 2013 10:02:38 -0600 (MDT) From: Warren Block To: Gabor Kovesdan Subject: Re: RFC: Upgrading to DocBook 5.0 In-Reply-To: <51E2A6C9.1070301@FreeBSD.org> Message-ID: References: <519FA4FE.4030305@FreeBSD.org> <51E25FCE.9020405@t-hosting.hu> <51E2A6C9.1070301@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="3512871622-791269410-1373817758=:61543" X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (wonkity.com [127.0.0.1]); Sun, 14 Jul 2013 10:02:38 -0600 (MDT) Cc: doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2013 16:02:39 -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-791269410-1373817758=:61543 Content-Type: TEXT/PLAIN; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT On Sun, 14 Jul 2013, Gabor Kovesdan wrote: > Em 14-07-2013 14:52, Warren Block escreveu: >> On Sun, 14 Jul 2013, Gábor Kövesdán wrote: >> >>> Some more things: >>> >>> - Admonitions (top, note, warning boxes) look quite strange in lists and >>> such places. I think we should add a policy to avoid them and start >>> changing the markup. >> >> Admonitions are overused in some places. They are visually jarring, often >> moreso than the tip or warning deserves. A link to an example of this >> particular problem would be helpful to see what you mean, though. > For example here: http://www.freebsd.org/doc/en/books/handbook/history.html > > It breaks the list. It is even worse in PDF rendering since there are page > boundaries and it breaks the page up to two parts. I see what you mean. But if we say "don't use admonitions in lists because they are visually ugly, that becomes markup for appearance and not for semantics. Some tweaking of the CSS may help, like reducing the size of the admonition title so it is not so much larger than the surrounding text. docbook.css is something I've been meaning to look at, hopefully soon. >>> - We extensively use markup in titles, which later renders with a >>> different font. E.g. we mark the X of 9.X as replaceable or we mark up >>> root as a username. I think that such rendering should be avoided in >>> titles and the easiest and cleanest way to do so would be not using such >>> markup in titles. >> >> Please expand--what is the problem with differing fonts in titles? I can >> see this both ways, but the text of a title being consistent with the >> rendering in the body seems like an advantage. > Apart from the ugly visual outlook, it is not conventional in books and as > such, it is just bothering and confusing for the reader. It breaks the > information flow. Typographyc conventions serve for nice visual outlook and > usability. The typesetting should facilitate reading and not difficulting it. > If we want to publish a high-quality print edition of Handbook, we must > follow the conventions, otherwise it won't be a serious publication. Again, doesn't this break the semantics versus appearance separation? If the standard is to show titles in a single font and size, then that should be done when rendering. Semantically, a filename is a filename whether it is in a title or body text. I find different fonts for filenames and commands to be useful, even in titles. The O'Reilly style guide doesn't mention anything about title styles, and in a quick search I did not find anything else. >>> - Currently, we use the CALS table model in the documentation, while >>> DocBook also supports the HTML table model. It has a more simple syntax >>> and more rendering features in the DocBook stylesheets. Another advantage >>> is that by using it, we would have only one table semantics in docs + web. >>> Any objection to changing to the HTML table model? >> >> An example would be useful here, also. For compatibility with the rest of >> the world, we should probably stick with the most common usage. > Most common is very relative. HTML uses exclusively the HTML table model, > hence the name. CALS is older and quite common in the SGML/XML world. Both > are supported in DocBook and we currently use CALS. Earlier there was no > other option in DocBook. Using exclusively HTML tables would reduce the used > table models to one. > > Examples: just google for CALS table and HTML table, both are documented > extensively. For reference, here are links: http://www.docbook.org/tdg5/en/html/cals.table.html http://www.docbook.org/tdg5/en/html/html.table.html Changing the source documents could be scripted, but would also require modifications to the FDP Primer. I can't tell if HTML tables have all the same capabilities as CALS tables. >>> - Some lists have their own title, while the preceding text usually >>> introduces well what is enumerated in the list. I find the rendered title >>> quite strange between this text and the list. Besides, I don't remember >>> having seen technical books that use such titles. My suggestion is to >>> simple remove them. Any objection or better idea? >> >> Please give an example here, also. > http://www.freebsd.org/doc/en/books/handbook/bsdinstall-pre.html > > Look at 2.3.3. There's a semicolon at the end of the last paragraph and list > title is just floating there in the middle. This type of titles breaks the > flow of the text and doesn't facilitate reading. The previous toolchain rendered that title in bold: http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/books/handbook/bsdinstall-pre.html Agreed, that title does not look very good. Adding a colon to list titles when rendering would help. Removing all list titles be too severe. >> All of these suggestions seem to be style changes that are not necessarily >> tied to the change to DocBook 5, or maybe changes that are not possible >> until after the conversion. Unless they're required, it may be best to >> wait until after the conversion. > Not in theory but theory doesn't always match practice. I'm working on the > DocBook 5 change to provide better rendering and support publishing print > versions. I'm evaluating and customizing two different rendering methods and > I have to see where we can get with each. Practically I can do it by > eliminating the confusing and bothering factors. This is sometimes done by > customizing the rendering and sometimes by feeding back the results to the > concrete documents. Understood. Thank you for working on this! --3512871622-791269410-1373817758=:61543-- From owner-freebsd-doc@FreeBSD.ORG Sun Jul 14 18:14:20 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 694E65BE for ; Sun, 14 Jul 2013 18:14:20 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id 0682FC72 for ; Sun, 14 Jul 2013 18:14:19 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id C292014D2514; Sun, 14 Jul 2013 20:14:17 +0200 (CEST) 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 DsOdJfl8V4wu; Sun, 14 Jul 2013 20:14:15 +0200 (CEST) Received: from [192.168.1.117] (catv-80-99-23-232.catv.broadband.hu [80.99.23.232]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id E35F814D242C; Sun, 14 Jul 2013 20:14:14 +0200 (CEST) Message-ID: <51E2EA74.9070008@FreeBSD.org> Date: Sun, 14 Jul 2013 20:14:12 +0200 From: Gabor Kovesdan User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0a2 MIME-Version: 1.0 To: Warren Block Subject: Re: RFC: Upgrading to DocBook 5.0 References: <519FA4FE.4030305@FreeBSD.org> <51E25FCE.9020405@t-hosting.hu> <51E2A6C9.1070301@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2013 18:14:20 -0000 On 2013.07.14. 18:02, Warren Block wrote: > On Sun, 14 Jul 2013, Gabor Kovesdan wrote: > >> Em 14-07-2013 14:52, Warren Block escreveu: >>> On Sun, 14 Jul 2013, Gábor Kövesdán wrote: >>> >>>> Some more things: >>>> >>>> - Admonitions (top, note, warning boxes) look quite strange in >>>> lists and such places. I think we should add a policy to avoid them >>>> and start changing the markup. >>> >>> Admonitions are overused in some places. They are visually jarring, >>> often moreso than the tip or warning deserves. A link to an example >>> of this particular problem would be helpful to see what you mean, >>> though. >> For example here: >> http://www.freebsd.org/doc/en/books/handbook/history.html >> >> It breaks the list. It is even worse in PDF rendering since there are >> page boundaries and it breaks the page up to two parts. > > I see what you mean. But if we say "don't use admonitions in lists > because they are visually ugly, that becomes markup for appearance and > not for semantics. It is not appearance, it is structure, which is part of semantics. From a semantic point of view, what's an admonition? Imo, it is a piece of additional information that (1) is related to the wider context, (2) is more or less self-contained and (3) does not fit into the main text flow so its position is more or less flexible. It is usually rendereded with a border or a background color that clearly separates it from the main flow of the text. Because of these characteristics, it semantically doesn't fit into the notion of lists. Nor tables should be embedded into lists. > > Some tweaking of the CSS may help, like reducing the size of the > admonition title so it is not so much larger than the surrounding > text. docbook.css is something I've been meaning to look at, hopefully > soon. It may help but that break of information flow still shouldn't be there. > >>>> - We extensively use markup in titles, which later renders with a >>>> different font. E.g. we mark the X of 9.X as replaceable or we mark >>>> up root as a username. I think that such rendering should be >>>> avoided in titles and the easiest and cleanest way to do so would >>>> be not using such markup in titles. >>> >>> Please expand--what is the problem with differing fonts in titles? >>> I can see this both ways, but the text of a title being consistent >>> with the rendering in the body seems like an advantage. >> Apart from the ugly visual outlook, it is not conventional in books >> and as such, it is just bothering and confusing for the reader. It >> breaks the information flow. Typographyc conventions serve for nice >> visual outlook and usability. The typesetting should facilitate >> reading and not difficulting it. If we want to publish a high-quality >> print edition of Handbook, we must follow the conventions, otherwise >> it won't be a serious publication. > > Again, doesn't this break the semantics versus appearance separation? > If the standard is to show titles in a single font and size, then that > should be done when rendering. Semantically, a filename is a filename > whether it is in a title or body text. You are calling appearance what is in fact structure. We could talk about appearance if we wrote or something like that. The semantics of a title could be defined like a plain text title and that would be a valid semantics, too. True, it is also possible to solve it when rendering but if we decide that we don't want such in titles, why not just changing the semantics and sparing some stylesheet code? Both the docs and the stylesheets would be more simple. > > I find different fonts for filenames and commands to be useful, even > in titles. The O'Reilly style guide doesn't mention anything about > title styles, and in a quick search I did not find anything else. Ok, it doesn't specify it explicitly but can you show me a technical book that has such titles? A real, published book, please, not online docs. > >>>> - Currently, we use the CALS table model in the documentation, >>>> while DocBook also supports the HTML table model. It has a more >>>> simple syntax and more rendering features in the DocBook >>>> stylesheets. Another advantage is that by using it, we would have >>>> only one table semantics in docs + web. Any objection to changing >>>> to the HTML table model? >>> >>> An example would be useful here, also. For compatibility with the >>> rest of the world, we should probably stick with the most common usage. >> Most common is very relative. HTML uses exclusively the HTML table >> model, hence the name. CALS is older and quite common in the SGML/XML >> world. Both are supported in DocBook and we currently use CALS. >> Earlier there was no other option in DocBook. Using exclusively HTML >> tables would reduce the used table models to one. >> >> Examples: just google for CALS table and HTML table, both are >> documented extensively. > > For reference, here are links: > > http://www.docbook.org/tdg5/en/html/cals.table.html > http://www.docbook.org/tdg5/en/html/html.table.html > > Changing the source documents could be scripted, but would also > require modifications to the FDP Primer. > > I can't tell if HTML tables have all the same capabilities as CALS > tables. The same information is stored so theoretically it is possible to do the same with them. HTML table markup is more simple and the stock stylesheets implement more features. > >>>> - Some lists have their own title, while the preceding text usually >>>> introduces well what is enumerated in the list. I find the rendered >>>> title quite strange between this text and the list. Besides, I >>>> don't remember having seen technical books that use such titles. My >>>> suggestion is to simple remove them. Any objection or better idea? >>> >>> Please give an example here, also. >> http://www.freebsd.org/doc/en/books/handbook/bsdinstall-pre.html >> >> Look at 2.3.3. There's a semicolon at the end of the last paragraph >> and list title is just floating there in the middle. This type of >> titles breaks the flow of the text and doesn't facilitate reading. > > The previous toolchain rendered that title in bold: > http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/books/handbook/bsdinstall-pre.html > > > Agreed, that title does not look very good. Adding a colon to list > titles when rendering would help. Removing all list titles be too > severe. Having a colon at the end of the paragraph and another one at the end of the list title? It seems even more confusing to me. Why is to severe removing them? Do they add any extra information that helps you understanding the content? I think it makes the comprehension more difficult and is just counter-productive. Can you find a published book with such list titles? Gabor From owner-freebsd-doc@FreeBSD.ORG Sun Jul 14 18:57:48 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id F353B27B; Sun, 14 Jul 2013 18:57:47 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id B5FD0DF5; Sun, 14 Jul 2013 18:57:47 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6EIvk9K062614; Sun, 14 Jul 2013 12:57:46 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6EIvk9m062611; Sun, 14 Jul 2013 12:57:46 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sun, 14 Jul 2013 12:57:46 -0600 (MDT) From: Warren Block To: Gabor Kovesdan Subject: Title formatting (was Re: RFC: Upgrading to DocBook 5.0) In-Reply-To: <51E2EA74.9070008@FreeBSD.org> Message-ID: References: <519FA4FE.4030305@FreeBSD.org> <51E25FCE.9020405@t-hosting.hu> <51E2A6C9.1070301@FreeBSD.org> <51E2EA74.9070008@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]); Sun, 14 Jul 2013 12:57:46 -0600 (MDT) Cc: doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Jul 2013 18:57:48 -0000 On Sun, 14 Jul 2013, Gabor Kovesdan wrote: >> I find different fonts for filenames and commands to be useful, even in >> titles. The O'Reilly style guide doesn't mention anything about title >> styles, and in a quick search I did not find anything else. > Ok, it doesn't specify it explicitly but can you show me a technical book > that has such titles? A real, published book, please, not online docs. Mastering Regular Expressions (1998), by Jeffrey E. F. Friedl, shows acronyms in titles in a smaller all-caps size. There is a Perl chapter with titles including "Modification with \Q and Friends: True Lies", "The /e Modifier", and "Using /g with a Regex That can Match Nothingness". The "\Q", "/e", and "/g" in those titles are in a monospace typewriter font. This is an O'Reilly book, but most of the other O'Reilly books I checked use the same font for all of the title. C Programming, A Modern Approach (2008), by K. N. King, has a Loops chapter with section titles like "The while Loop" and "The do Statement", where "while" and "do" are in a monospace typewriter font. Advanced Programming in the UNIX Environment (2001), by W. Richard Stevens, has section titles like "stat, fstat, and lstat Functions", "Streams and FILE Objects", and "pty_fork Function". The keywords are in a monospace typewriter font. UNIX System Administration Handbook (2001), by Evi Nemeth, shows keywords in the same font, but bold. In "The /etc/ttys and /etc/ttytab files", the filenames are bold. From owner-freebsd-doc@FreeBSD.ORG Mon Jul 15 04:58:53 2013 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C4315429; Mon, 15 Jul 2013 04:58:53 +0000 (UTC) (envelope-from hrs@FreeBSD.org) Received: from mail.allbsd.org (gatekeeper.allbsd.org [IPv6:2001:2f0:104:e001::32]) by mx1.freebsd.org (Postfix) with ESMTP id 54A16878; Mon, 15 Jul 2013 04:58:53 +0000 (UTC) Received: from alph.d.allbsd.org (p2049-ipbf1102funabasi.chiba.ocn.ne.jp [122.26.101.49]) (authenticated bits=128) by mail.allbsd.org (8.14.5/8.14.5) with ESMTP id r6F4waIH020101 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jul 2013 13:58:46 +0900 (JST) (envelope-from hrs@FreeBSD.org) Received: from localhost (localhost [IPv6:::1]) (authenticated bits=0) by alph.d.allbsd.org (8.14.5/8.14.5) with ESMTP id r6F4wYtB029676; Mon, 15 Jul 2013 13:58:35 +0900 (JST) (envelope-from hrs@FreeBSD.org) Date: Mon, 15 Jul 2013 13:58:10 +0900 (JST) Message-Id: <20130715.135810.1689066987888254665.hrs@allbsd.org> To: gabor@FreeBSD.org Subject: Re: RFC: Upgrading to DocBook 5.0 From: Hiroki Sato In-Reply-To: <51E2EA74.9070008@FreeBSD.org> References: <51E2A6C9.1070301@FreeBSD.org> <51E2EA74.9070008@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(Mon_Jul_15_13_58_10_2013_720)--" Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.97.4 at gatekeeper.allbsd.org X-Virus-Status: Clean X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (mail.allbsd.org [133.31.130.32]); Mon, 15 Jul 2013 13:58:46 +0900 (JST) X-Spam-Status: No, score=-89.3 required=13.0 tests=CONTENT_TYPE_PRESENT, DIRECTOCNDYN,DYN_PBL,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 Cc: doc@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 04:58:53 -0000 ----Security_Multipart(Mon_Jul_15_13_58_10_2013_720)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Gabor Kovesdan wrote in <51E2EA74.9070008@FreeBSD.org>: ga> >> It breaks the list. It is even worse in PDF rendering since there are ga> >> page boundaries and it breaks the page up to two parts. ga> > ga> > I see what you mean. But if we say "don't use admonitions in lists ga> > because they are visually ugly, that becomes markup for appearance and ga> > not for semantics. ga> It is not appearance, it is structure, which is part of ga> semantics. From a semantic point of view, what's an admonition? Imo, ga> it is a piece of additional information that (1) is related to the ga> wider context, (2) is more or less self-contained and (3) does not fit ga> into the main text flow so its position is more or less flexible. It ga> is usually rendereded with a border or a background color that clearly ga> separates it from the main flow of the text. Because of these ga> characteristics, it semantically doesn't fit into the notion of ga> lists. Nor tables should be embedded into lists. I agree that admonition in a list/table does not make sense semantically. Probably people abuse it as a replacement of footnote. ga> > Again, doesn't this break the semantics versus appearance separation? ga> > If the standard is to show titles in a single font and size, then that ga> > should be done when rendering. Semantically, a filename is a filename ga> > whether it is in a title or body text. ga> You are calling appearance what is in fact structure. We could talk ga> about appearance if we wrote or something like that. ga> ga> The semantics of a title could be defined like a plain text title and ga> that would be a valid semantics, too. True, it is also possible to ga> solve it when rendering but if we decide that we don't want such in ga> titles, why not just changing the semantics and sparing some ga> stylesheet code? Both the docs and the stylesheets would be more ga> simple. I like to solve this upon rendering and I think it will be simpler because a policy of plain text title (in markup) practically does not work without DTD change, and elements such as can be included in title elements via entity references or so in any way. Forcing a consistent style for title elements looks easy to me. ga> >> Examples: just google for CALS table and HTML table, both are ga> >> documented extensively. ga> > ga> > For reference, here are links: ga> > ga> > http://www.docbook.org/tdg5/en/html/cals.table.html ga> > http://www.docbook.org/tdg5/en/html/html.table.html ga> > ga> > Changing the source documents could be scripted, but would also ga> > require modifications to the FDP Primer. ga> > ga> > I can't tell if HTML tables have all the same capabilities as CALS ga> > tables. ga> The same information is stored so theoretically it is possible to do ga> the same with them. HTML table markup is more simple and the stock ga> stylesheets implement more features. I am neutral about this. The difference in their capability is quite small. XHTML table model may be better for people who are familiar with XHTML. ga> > The previous toolchain rendered that title in bold: ga> > http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/books/handbook/bsdinstall-pre.html ga> > Agreed, that title does not look very good. Adding a colon to list ga> > titles when rendering would help. Removing all list titles be too ga> > severe. ga> Having a colon at the end of the paragraph and another one at the end ga> of the list title? It seems even more confusing to me. ga> Why is to severe removing them? Do they add any extra information that ga> helps you understanding the content? I think it makes the ga> comprehension more difficult and is just counter-productive. ga> ga> Can you find a published book with such list titles? I think removing title is fine. Although there are some exmaples for such an informal title like this: Pros: - A - B Cons: - C - D they are items, not "title" actually. If we really need it, it should be a caption. -- Hiroki ----Security_Multipart(Mon_Jul_15_13_58_10_2013_720)-- Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (FreeBSD) iEYEABECAAYFAlHjgWIACgkQTyzT2CeTzy35sQCdF3/fZ74UsN8fzCl9TSBgd0CV BucAn15Lqi6SelJYAx3DMo6iPpYg/YGB =aqXZ -----END PGP SIGNATURE----- ----Security_Multipart(Mon_Jul_15_13_58_10_2013_720)---- From owner-freebsd-doc@FreeBSD.ORG Mon Jul 15 08:43:23 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3606C6F1 for ; Mon, 15 Jul 2013 08:43:23 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id E54B9908 for ; Mon, 15 Jul 2013 08:43:22 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id D7DDD14D243A; Mon, 15 Jul 2013 10:43:21 +0200 (CEST) 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 a8sWovtalMiV; Mon, 15 Jul 2013 10:43:21 +0200 (CEST) Received: from [192.168.1.117] (catv-80-99-23-232.catv.broadband.hu [80.99.23.232]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id 18EF514D2403; Mon, 15 Jul 2013 10:43:21 +0200 (CEST) Message-ID: <51E3B626.1030904@FreeBSD.org> Date: Mon, 15 Jul 2013 10:43:18 +0200 From: Gabor Kovesdan User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0a2 MIME-Version: 1.0 To: Warren Block Subject: Re: Title formatting (was Re: RFC: Upgrading to DocBook 5.0) References: <519FA4FE.4030305@FreeBSD.org> <51E25FCE.9020405@t-hosting.hu> <51E2A6C9.1070301@FreeBSD.org> <51E2EA74.9070008@FreeBSD.org> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 08:43:23 -0000 On 2013.07.14. 20:57, Warren Block wrote: > On Sun, 14 Jul 2013, Gabor Kovesdan wrote: > >>> I find different fonts for filenames and commands to be useful, even >>> in titles. The O'Reilly style guide doesn't mention anything about >>> title styles, and in a quick search I did not find anything else. >> Ok, it doesn't specify it explicitly but can you show me a technical >> book that has such titles? A real, published book, please, not online >> docs. > > Mastering Regular Expressions (1998), by Jeffrey E. F. Friedl, shows > acronyms in titles in a smaller all-caps size. There is a Perl > chapter with titles including "Modification with \Q and Friends: True > Lies", "The /e Modifier", and "Using /g with a Regex That can Match > Nothingness". The "\Q", "/e", and "/g" in those titles are in a > monospace typewriter font. This is an O'Reilly book, but most of the > other O'Reilly books I checked use the same font for all of the title. > > C Programming, A Modern Approach (2008), by K. N. King, has a Loops > chapter with section titles like "The while Loop" and "The do > Statement", where "while" and "do" are in a monospace typewriter font. > > Advanced Programming in the UNIX Environment (2001), by W. Richard > Stevens, has section titles like "stat, fstat, and lstat Functions", > "Streams and FILE Objects", and "pty_fork Function". The keywords are > in a monospace typewriter font. > > UNIX System Administration Handbook (2001), by Evi Nemeth, shows > keywords in the same font, but bold. In "The /etc/ttys and > /etc/ttytab files", the filenames are bold. Ok, thank you for investigating this. If it is accepted then I don't object that much. But please let's keep these at a reasonable extent, e.g. monspace or italic but no colors. Gabor From owner-freebsd-doc@FreeBSD.ORG Mon Jul 15 08:46:49 2013 Return-Path: Delivered-To: doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 834E97A3; Mon, 15 Jul 2013 08:46:49 +0000 (UTC) (envelope-from gabor@FreeBSD.org) Received: from server.mypc.hu (server.mypc.hu [87.229.73.95]) by mx1.freebsd.org (Postfix) with ESMTP id 3FFD1920; Mon, 15 Jul 2013 08:46:48 +0000 (UTC) Received: from server.mypc.hu (localhost [127.0.0.1]) by server.mypc.hu (Postfix) with ESMTP id 1B8CB14D243A; Mon, 15 Jul 2013 10:46:48 +0200 (CEST) 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 D8Dk7Um-CmdB; Mon, 15 Jul 2013 10:46:43 +0200 (CEST) Received: from [192.168.1.117] (catv-80-99-23-232.catv.broadband.hu [80.99.23.232]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by server.mypc.hu (Postfix) with ESMTPSA id B536214D2403; Mon, 15 Jul 2013 10:46:43 +0200 (CEST) Message-ID: <51E3B6F0.9010908@FreeBSD.org> Date: Mon, 15 Jul 2013 10:46:40 +0200 From: Gabor Kovesdan User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.0a2 MIME-Version: 1.0 To: Hiroki Sato Subject: Re: RFC: Upgrading to DocBook 5.0 References: <51E2A6C9.1070301@FreeBSD.org> <51E2EA74.9070008@FreeBSD.org> <20130715.135810.1689066987888254665.hrs@allbsd.org> In-Reply-To: <20130715.135810.1689066987888254665.hrs@allbsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: doc@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 08:46:49 -0000 On 2013.07.15. 6:58, Hiroki Sato wrote: > ga> The semantics of a title could be defined like a plain text title and > ga> that would be a valid semantics, too. True, it is also possible to > ga> solve it when rendering but if we decide that we don't want such in > ga> titles, why not just changing the semantics and sparing some > ga> stylesheet code? Both the docs and the stylesheets would be more > ga> simple. > > I like to solve this upon rendering and I think it will be simpler > because a policy of plain text title (in markup) practically does not > work without DTD change, and elements such as can be > included in title elements via entity references or so in any way. > Forcing a consistent style for title elements looks easy to me. I thought of adding some Schematron constraints for the problematic cases but I'll go for the rendering customization if this is better accepted. I agree that this may work better for entity references. > ga> > The previous toolchain rendered that title in bold: > ga> >http://docs.freebsd.org/doc/9.0-RELEASE/usr/share/doc/freebsd/en_US.ISO8859-1/books/handbook/bsdinstall-pre.html > ga> > Agreed, that title does not look very good. Adding a colon to list > ga> > titles when rendering would help. Removing all list titles be too > ga> > severe. > ga> Having a colon at the end of the paragraph and another one at the end > ga> of the list title? It seems even more confusing to me. > ga> Why is to severe removing them? Do they add any extra information that > ga> helps you understanding the content? I think it makes the > ga> comprehension more difficult and is just counter-productive. > ga> > ga> Can you find a published book with such list titles? > > I think removing title is fine. Although there are some exmaples for > such an informal title like this: > > Pros: > - A > - B > > Cons: > - C > - D > > they are items, not "title" actually. If we really need it, it > should be a caption. I believe these are already rendered as normal paragraphs between two itemizedlists but I'll verify this. Gabor From owner-freebsd-doc@FreeBSD.ORG Mon Jul 15 11:06:04 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 409E7D77 for ; Mon, 15 Jul 2013 11:06:04 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 25217F4D for ; Mon, 15 Jul 2013 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 r6FB642m083496 for ; Mon, 15 Jul 2013 11:06:04 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6FB63h2083494 for freebsd-doc@FreeBSD.org; Mon, 15 Jul 2013 11:06:03 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 15 Jul 2013 11:06:03 GMT Message-Id: <201307151106.r6FB63h2083494@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.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 11:06:04 -0000 (Note: an HTML version of this report is available at http://www.freebsd.org/cgi/query-pr-summary.cgi?category=doc .) The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o docs/180551 doc [patch] document NULL encryption algorithm in geli(8) o docs/180493 doc 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/180289 doc [patch] suggest bsdinstall and portsnap for installati 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/179832 doc manual page of mac_from_text suggests incorrect freein o docs/179697 doc Handbook incomplete WRT Opera flash usage (linproc) o docs/179560 doc [handbook] brazilian portuguese translation to "DTrace o docs/179552 doc [handbook] brazilian portuguese translation to "Instal o docs/179541 doc [handbook] brazilian portuguese translation to "Obtain 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/178677 doc *** [article.html] Error code 1 Stop in /usr/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/178077 doc [patch] Correct description of -webnfs in exports.5 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/177056 doc typo in link in handbook section 31.4.16 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/176583 doc getifaddrs(3) - struct ifa_data not exist 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/170223 doc IPv6 configuration section for 9.x is incorrect 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/164620 doc Raid 1 issues 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/160446 doc [handbook] Handbook sound setup seems outdated 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/150877 doc ambiguity in newsyslog(8) man page about zfs with comp 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/144515 doc [handbook] Expand handbook Table of contents 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/138845 doc Exceeding kern.ipc.maxpipekva refers to tuning(7) whic 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/135516 doc [patch] pax(1) manual not mentioning chflags unawarene o docs/132839 doc [patch] Fix example script in ldap-auth article o docs/132718 doc [handbook] Information about adding a new mirror is ou o docs/132260 doc dhcpd(8) pid not stored in documented location 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/116080 doc PREFIX is documented, but not the more important LOCAL 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/110062 doc [patch] mount_nfs(8) fails to mention a failure condit o docs/109981 doc No manual entry for post-grohtml o docs/109977 doc No manual entry for ksu o docs/109972 doc No manual entry for zless/bzless 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 o docs/100196 doc man login.conf does explain not "unlimited" o docs/98974 doc Missing tunables in loader(8) manpage o docs/98115 doc Missing parts after rendering handbook to RTF format 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/45303 doc Bug in PDF DocBook rendering 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 s docs/33589 doc [patch] to doc.docbook.mk to post process .tex files. 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 246 problems total. From owner-freebsd-doc@FreeBSD.ORG Mon Jul 15 18:00:00 2013 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]) by hub.freebsd.org (Postfix) with ESMTP id A40FBFD2 for ; Mon, 15 Jul 2013 18:00:00 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 75721DC8 for ; Mon, 15 Jul 2013 18: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 r6FI00oZ074782 for ; Mon, 15 Jul 2013 18:00:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6FI00Jh074781; Mon, 15 Jul 2013 18:00:00 GMT (envelope-from gnats) Resent-Date: Mon, 15 Jul 2013 18:00:00 GMT Resent-Message-Id: <201307151800.r6FI00Jh074781@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, Matthias Andree Received: from apollo.emma.line.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by hub.freebsd.org (Postfix) with ESMTP id 143CBF46 for ; Mon, 15 Jul 2013 17:51:30 +0000 (UTC) (envelope-from mandree@FreeBSD.org) Received: from mandree by apollo.emma.line.org with local (Exim 4.80.1 (FreeBSD)) (envelope-from ) id 1UymvS-000ADt-VA for FreeBSD-gnats-submit@freebsd.org; Mon, 15 Jul 2013 19:51:06 +0200 Message-Id: Date: Mon, 15 Jul 2013 19:51:06 +0200 From: Matthias Andree To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.113 Subject: docs/180579: committer's guide incomplete on ports removal X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Matthias Andree List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 18:00:00 -0000 >Number: 180579 >Category: docs >Synopsis: committer's guide incomplete on ports removal >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-doc >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Jul 15 18:00:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Matthias Andree >Release: FreeBSD 9.1-RELEASE-p4 amd64 >Organization: >Environment: System: FreeBSD apollo.emma.line.org 9.1-RELEASE-p4 FreeBSD 9.1-RELEASE-p4 #0: Mon Jun 17 11:42:37 UTC 2013 root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 >Description: The Committer's Guide is incomplete with respect to removing ports. I am looking at revision 42226 as obtained from We used to use CVS, and hence section 13.2.1 "How do I remove an existing port?" mentions, in a box: * Then, remove the port: 1. Remove the port's files via svn remove. 2. Remove the SUBDIR listing of the port in the parent directory Makefile. 3. Add an entry to ports/MOVED. 4. Remove the port from ports/LEGAL if it is there. This is incomplete in that step 1 mentions "remove the port's files". This used to suffice because CVS only tracked files, and the client was responsible for removing directories when the last contained file had been removed. With SVN, directories are tracked in addition to files. I propose to change 1. to read: Remove the port's files and its directory via svn remove. >How-To-Repeat: >Fix: Change bullet 1 text from Remove the port's files via svn remove. to Remove the port's files and its directory via svn remove. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Mon Jul 15 18:14:42 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3E37F450 for ; Mon, 15 Jul 2013 18:14:42 +0000 (UTC) (envelope-from armida.marchesi@gmail.com) Received: from mail-ea0-x231.google.com (mail-ea0-x231.google.com [IPv6:2a00:1450:4013:c01::231]) by mx1.freebsd.org (Postfix) with ESMTP id CDACCE76 for ; Mon, 15 Jul 2013 18:14:41 +0000 (UTC) Received: by mail-ea0-f177.google.com with SMTP id j14so7909939eak.22 for ; Mon, 15 Jul 2013 11:14:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:message-id:subject:mime-version:content-type; bh=tJIpRr1Z6l6Mf/jkae9CWYLAHywnBufc6pbXtbcQ3t8=; b=1Jl9VsUKR0UNfl7F6MRtFf8dfu5+7SysMQQRzLt1qrtucglHkVp18pu5tUfXeF1lUV hbmFCOH2InQ/X+xZ+9rnCmrcIpPzXm1ncSQ2V4Zn8asWs9I0GZ3K5Wah+69LlYO7VbYg F7DBaJwMYkTTs91jp51Zy/I8tq6XgWf4TBPVMn8DGPZbWnNQ7CD3eJY+15OmVFRyS/pO xJwqpF9R2fVLf1vAOszHPoiN5qiK+2epF6BVQKOshIFb9gR29/bHJg1rvwbSYgVZkd3x R7jY+9jfFLlAYxWpnOFqzjrS1kOAGf1uQSv7Ilu8dPzYpLYRFddXeX59IZL6r+E3XnKs rUvA== X-Received: by 10.14.223.199 with SMTP id v47mr60229734eep.32.1373912081037; Mon, 15 Jul 2013 11:14:41 -0700 (PDT) Received: from InFusio (176-114-240-18.rychlydrat.cz. [176.114.240.18]) by mx.google.com with ESMTPSA id n45sm104569159eew.1.2013.07.15.11.14.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 15 Jul 2013 11:14:40 -0700 (PDT) Date: Mon, 15 Jul 2013 20:14:39 +0200 (CEST) From: Armida Marchesi To: freebsd-doc@freebsd.org Message-ID: <22257131.99.1373912079906.JavaMail.Kari@InFusio> Subject: Backlinks MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_25_23770836.1373911845917" X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 18:14:42 -0000 ------=_Part_25_23770836.1373911845917 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Hi, we would be interested in buying a place on your portal for our gambling related contextual ads, links or articles. 6 months via Paypal, Moneybookers or Wire Transfer. Let me know whether it is possible. Thanks, Armida Marchesi -------------------------------------------------------------------------------------------------------------------------- Salve, saremmo interessati ad acquistare spazi sul vostro portale per i nostri annunci pubblicitari, articoli e link riguardanti il gioco d'azzardo. Pagamenti a 6 mesi via Paypal, Moneybooker o Wire Transfer. Fateci sapere se possibile. Cordiali saluti Armida Marchesi ------=_Part_25_23770836.1373911845917-- From owner-freebsd-doc@FreeBSD.ORG Mon Jul 15 18:22:36 2013 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id E8E868AB; Mon, 15 Jul 2013 18:22:36 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id C20A7EC0; Mon, 15 Jul 2013 18:22:36 +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 r6FIMaJY081047; Mon, 15 Jul 2013 18:22:36 GMT (envelope-from wblock@freefall.freebsd.org) Received: (from wblock@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6FIMalt081046; Mon, 15 Jul 2013 18:22:36 GMT (envelope-from wblock) Date: Mon, 15 Jul 2013 18:22:36 GMT Message-Id: <201307151822.r6FIMalt081046@freefall.freebsd.org> To: wblock@FreeBSD.org, freebsd-doc@FreeBSD.org, wblock@FreeBSD.org From: wblock@FreeBSD.org Subject: Re: docs/180579: committer's guide incomplete on ports removal X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 18:22:37 -0000 Synopsis: committer's guide incomplete on ports removal Responsible-Changed-From-To: freebsd-doc->wblock Responsible-Changed-By: wblock Responsible-Changed-When: Mon Jul 15 18:22:20 UTC 2013 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=180579 From owner-freebsd-doc@FreeBSD.ORG Mon Jul 15 18:39:43 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 26101D48 for ; Mon, 15 Jul 2013 18:39:43 +0000 (UTC) (envelope-from groundup2360917182914017@gmail.com) Received: from mail-we0-x22b.google.com (mail-we0-x22b.google.com [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id A17A3F89 for ; Mon, 15 Jul 2013 18:39:42 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id m46so10548378wev.30 for ; Mon, 15 Jul 2013 11:39:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=2uIHdUzbx4/JzoYVb/FNf1N2eejUe6/MjRbanTY7PEA=; b=nb185gN3G62pGnW2b7cHfKYwx3LJ05o1xv556xXvL2f5sAL347Hx+FFHbAt8ZsSK++ d4Rpt2HVWELWsRgy9ZbYujm0JTQXEpKkC3mEFPw3ZmUQi8SyWuuAuZBQF4k5d0uJdbh9 nOeNky4mKZnUqH5iXcdqKb4Vp9+DD7IpdBzr3uYz4DUEnaczxPDaYxlCpWdIKLB8/Cv0 x9NWKEXv1yUbfAl/xVv7Syww0DO9HepMeDUvl9WXSvDi2f4x+1bZZVwYxjEe3kyTSno0 qcDsbqQfYKl3dt8Gk0ZmOq8xraYFD5nbmssqFvCyAyXxRQlqh8uQA+DZ7j+U2exeYXM7 LGcQ== MIME-Version: 1.0 X-Received: by 10.180.188.97 with SMTP id fz1mr9779384wic.34.1373913581827; Mon, 15 Jul 2013 11:39:41 -0700 (PDT) Received: by 10.216.212.138 with HTTP; Mon, 15 Jul 2013 11:39:41 -0700 (PDT) Date: Mon, 15 Jul 2013 14:39:41 -0400 Message-ID: Subject: 64 bit assembly language using c standard library From: Anthony Brown To: freebsd-doc@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 18:39:43 -0000 Tell me if this is useful: The general purpose registers in 64 bit assembly are rax, rbx, rcx, rdx, rsp, rbp, rsi, rdi, r8, r9, r10, r11, r12, r13, r14, r15. Registers r8-r15 can have a b, w, or d following after them to represent byte, word, or double word. Examples r8b, r8w, r8d. The calling convention when using the c standard library is rdi, rsi, rdx, rcx, r8, r9, and then the stack starting with the right most argument to the left most argument. We will use yasm to assemble the assembly instructions and gcc or clang to link the object file yasm produce. The commands to make the executable for the first program, hello.asm, except openbsd is yasm -f elf64 hello.asm; gcc -o hello hello.o or yasm -f elf64 hello.asm; clang -o hello hello.o. For openbsd yasm -f elf64 hello.asm; gcc -o hello hello.o -static The start of the lines in the source code to hello.asm and the later program examples aren't part of the source code. Don't type them in. [hello.asm] 1 ; The purpose of this program is to print Hello, world! 2 3 segment .data 4 hello db "Hello, world!", 0xa, 0 5 6 segment .text 7 extern printf 8 extern exit 9 10 global main 11 main: 12 mov rax, 0 13 mov rdi, hello 14 call printf 15 16 mov rax, 0 17 mov rdi, 0 18 call exit Explanation of hello.asm 1 The ; is a comment. It is a message to the reader of the source code. The assembler doesn't do anything with it, but ignore it. 3 Declares the data segment 4 hello is a identifier for the string Hello, world!. 0xa is to create a newline and 0 is to terminate the Hello, world!\n with a null. db is specify that the string is in bytes. 6 Declares the text segment. 7 Allows the linker to resolve the calls to printf later in the program. 8 Allows the linker to resolve the calls to exit later in the program. 10 This is need to use gcc or clang to do the linking. 11 This is need to use gcc or clang to do the linking. 12 Move 0 in rax. For the c standard library this tells it that their aren't any floating point arguments to pass to the function called. If their were floating point arguments passed to the function. Then you would place the amount of floating point arguments. Here we have none, so we pass 0. 13 Move hello in rdi. rdi is the first argument to the printf function. The second argument to the printf function would be rsi if there were another argument. This hello is the format string passed to printf. 14 Call the c standard library function printf. 16 Move 0 in rax. See explanation 12 for the rest of the explanation. 17 Move 0 in rdi. This is the first and only argument to the exit function. 18 Call the c standard library function exit. [age.asm] 1 segment .data 2 yourage db "How old are you: ", 0 3 willbe db "You will be %d years old in ten years.", 0xa, 0 4 input db "%d", 0 5 age dq 0 6 7 segment .text 8 extern printf 9 extern scanf 10 extern exit 11 12 global main 13 main: 14 mov rax, 0 15 mov rdi, yourage 16 call printf 17 18 mov rax, 0 19 mov rdi, input 20 mov rsi, age 21 call scanf 22 23 mov r15, [age] 24 add r15, 10 25 mov [age], r15 26 mov rax, 0 27 mov rdi, willbe 28 mov rsi, [age] 29 call printf 30 31 mov rax, 0 32 mov rdi, 0 33 call exit Explanation of age.asm 1 Declare data segment. 2 Declare some data with a identifier. 3 Declare some data with a identifier. 4 Declare the format string passed to scanf. 5 Declare 64 bit data for identifier age. This data is original set to all 0, but we will set it to something else with the scanf function. 7 Declare the text segment. 8 Allows the linker to resolve the calls to printf later in the source code. 9 Allows the linker to resolve the calls to scanf later in the source code. 10 Allows the linker to resolve the calls to exit later in the source code. 12 Allows to link using gcc or clang. 13 Allows to link using gcc or clang. 14 Move 0 in rax. This is the amount of floating point arguments pass to the c standard library function. 15 Move yourage in rdi. This is the first argument passed to printf. yourage happens to be the format string passed to printf. 16 Call the c standard library function printf. 18 Move 0 in rax. This is the amount of floating point arguments pass to the c standard library function. 19 Move input in rdi. Puts the specifier of the variable passed to scanf as the first argument to scanf. 20 Move age in rsi. Puts the variable for the c standard library function scanf in the second argument. The second argument is placed in rsi. 21 Call the c standard library function scanf. 23 Move the contents of the the age identifier in register r15. This is necessary, because we can't use the next add instruction with a identifier and immediate value. The identifier is really a address. 24 Add 10 to r15 and place to addition in r15. 25 Move r15 in the contents of age. This places the contents of r15 it the address of age. 26 Move 0 in rax. This is the amount of floating point arguments pass to the c standard library function. 27 Move willbe in rdi. Puts the format string in the first argument to printf function. 28 Move the contents of age in rsi. Puts the contents of age in the second argument to printf funciton. 29 Call the c standard library printf function. 31 Move 0 in rax. This is the amount of floating point arguments pass to the c standard library function. 32 Move 0 in rdi. This the first and only argument to exit function. 33 Call the c standard library exit function. From owner-freebsd-doc@FreeBSD.ORG Mon Jul 15 23:23:11 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 92789CD1 for ; Mon, 15 Jul 2013 23:23:11 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 3E5A1F9 for ; Mon, 15 Jul 2013 23:23:11 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6FNNAxZ074295 for ; Mon, 15 Jul 2013 17:23:10 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6FNNAF1074292 for ; Mon, 15 Jul 2013 17:23:10 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 15 Jul 2013 17:23:10 -0600 (MDT) From: Warren Block To: freebsd-doc@FreeBSD.org Subject: Project GRUDS: Handbook disk reorg 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]); Mon, 15 Jul 2013 17:23:10 -0600 (MDT) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Jul 2013 23:23:11 -0000 Project GRUDS (Grand Unified Disk Storage) Goal: Edit and rewrite the scattered, repetitive, and conflicting Handbook sections on disk storage into a unified group. This would be a separate in the Handbook, starting where chapter 19, Storage, currently begins. The problem: Right now there are at least three different places in the Handbook show disk partitioning methods and guidelines. All are different, and none really complete. An in-depth chapter on partitioning would allow sections to link to it and dispense with long explanations that distract from the current topic. Besides reducing redundancy, this would make many sections shorter and let users familiar with the concepts skip ahead easily. It's a big project, but even as a plan would help future Handbook contributions go in the right place. Tentative outline: Part 4:Disk Storage Introduction Quick start links to current methods for mirror (gmirror and ZFS) BIOS RAID (graid) RAID-5/RAID-Z (ZFS) Disk Hardware Chapter Introduction Blocks 512-byte Advanced Format Hardware RAID versus software RAID Comparison, advantages and disadvantages HAST? Device names SATA, IDE, SCSI, USB, most common hardware RAID device names Conclusion Disk Partitions Chapter Introduction Partitioning Schemes Metadata (types, locations, conflicts) MBR GPT Others Conclusion Labels Chapter (expanded from existing GEOM "Labeling Disk Devices") Introduction easy device relocatability provided by geom_label (others?) GPT labels Generic labels (glabel(8)) Filesystem labels "Unique ID" labels GPT UUID ufsid others? Conclusion GEOM Chapter ("Disk Device Transformations with GEOM"?) Introduction what is GEOM? from existing GEOM chapter additional section on graid(8) sorted in order of most common usage (gmirror, graid, ...) Conclusion Filesystems Chapter Introduction what are filesystems? UFS traditional split-filesystem layout newer, unified everything in root layout Other filesystems ext2, NTFS, etc mention NFS, with pointer to NFS section in "Network Servers" mention ZFS, and how it is more than a filesystem, and will be covered in the next chapter Conclusion ZFS Chapter neither fish nor fowl, it's a dessert topping *and* a floor wax both device and filesystem Introduction what is it? brief mention of best capabilities in-depth Conclusion Backup Chapter Introduction UFS Backup (main part from existing Storage chapter) ZFS Backup Conclusion From owner-freebsd-doc@FreeBSD.ORG Tue Jul 16 00:27:49 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 8F7C47C9 for ; Tue, 16 Jul 2013 00:27:49 +0000 (UTC) (envelope-from freebsd@allanjude.com) Received: from mx1.scaleengine.net (beauharnois2.bhs1.scaleengine.net [142.4.218.15]) by mx1.freebsd.org (Postfix) with ESMTP id 6F78F312 for ; Tue, 16 Jul 2013 00:27:48 +0000 (UTC) Received: from [10.1.1.1] (S01060001abad1dea.hm.shawcable.net [50.70.108.129]) (Authenticated sender: allan.jude@scaleengine.com) by mx1.scaleengine.net (Postfix) with ESMTPSA id 8406F34A97 for ; Tue, 16 Jul 2013 00:18:39 +0000 (UTC) Message-ID: <51E4915F.9010303@allanjude.com> Date: Mon, 15 Jul 2013 20:18:39 -0400 From: Allan Jude User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:20.0) Gecko/20100101 Thunderbird/20.0 MIME-Version: 1.0 To: freebsd-doc@freebsd.org Subject: Re: Project GRUDS: Handbook disk reorg References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2013 00:27:49 -0000 On 2013-07-15 19:23, Warren Block wrote: > Project GRUDS (Grand Unified Disk Storage) > > Goal: Edit and rewrite the scattered, repetitive, and conflicting > Handbook > sections on disk storage into a unified group. This would be a separate > in the Handbook, starting where chapter 19, Storage, currently > begins. > > The problem: Right now there are at least three different places in the > Handbook show disk partitioning methods and guidelines. All are > different, and none really complete. An in-depth chapter on > partitioning would allow sections to link to it and dispense with long > explanations that distract from the current topic. Besides reducing > redundancy, this would make many sections shorter and let users familiar > with the concepts skip ahead easily. > > It's a big project, but even as a plan would help future Handbook > contributions go in the right place. > > Tentative outline: > > > Part 4:Disk Storage > Introduction > Quick start > links to current methods for > mirror (gmirror and ZFS) > BIOS RAID (graid) > RAID-5/RAID-Z (ZFS) > > Disk Hardware Chapter > Introduction > Blocks > 512-byte > Advanced Format > Hardware RAID versus software RAID > Comparison, advantages and disadvantages > HAST? > Device names > SATA, IDE, SCSI, USB, most common hardware RAID device names > Conclusion > > > Disk Partitions Chapter > Introduction > Partitioning Schemes > Metadata (types, locations, conflicts) > MBR > GPT > Others > Conclusion > > > Labels Chapter (expanded from existing GEOM "Labeling Disk Devices") > Introduction > easy device relocatability > provided by geom_label (others?) > GPT labels > Generic labels (glabel(8)) > Filesystem labels > "Unique ID" labels > GPT UUID > ufsid > others? > Conclusion > > > GEOM Chapter ("Disk Device Transformations with GEOM"?) > Introduction > what is GEOM? > from existing GEOM chapter > additional section on graid(8) > sorted in order of most common usage (gmirror, graid, ...) > Conclusion > > > Filesystems Chapter > Introduction > what are filesystems? > UFS > traditional split-filesystem layout > newer, unified everything in root layout > Other filesystems > ext2, NTFS, etc > mention NFS, with pointer to NFS section in "Network Servers" > mention ZFS, and how it is more than a filesystem, and will be > covered in the next chapter > Conclusion > > > ZFS Chapter > neither fish nor fowl, it's a dessert topping *and* a floor wax > both device and filesystem > Introduction > what is it? > brief mention of best capabilities > in-depth > Conclusion > > > Backup Chapter > Introduction > UFS Backup (main part from existing Storage chapter) > ZFS Backup > Conclusion > _______________________________________________ > 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 definitely think this is a good idea, as I work on the ZFS chapter, I am often left wondering about where things that are not specific to ZFS should be covered. I imagine chapters 19 through 21 should be reorganized into a single coherent chapter, probably with a bit of stuff from the installation chapters moved here as well. Notes: Quick-start section should probably cover installation with 'root on zfs' Hardware chapter might mention SAS and things like SAS expanders and other enterprise hardware considerations The metadata storage location conflicts chapter is a really good idea. whole-disk GEOM + GPT is basically not possible, so you get in to per-partition GEOMs The labels bit should probably talk a bit about ZFS gUIDs and how ZFS does labels (this is both metadata and a label...) too The GEOM chapter should have at least a small stub for each GEOM type, like cache, journal, multipath, etc Moving ZFS to its own chapter is probably a good idea too. ZFS straddles the definition of raid transform, volume manager and file system (and maybe also block device for zvols), so doesn't fit neatly into the existing structure. For the ZFS chapter, this is the structure that bcr@ and myself proposed at the last docsprint (this is probably a lot more detail than you need, but if anyone has suggestions or ideas for additional things to do, please let me know): ZFS - ZFS introduction (what is ZFS) - ZFS Features and Terminology (giant table of definitions) - ZFS differences to other file systems (not sure about this one yet, or whether it should be part of the ZFS introduction section, could also just highlight differences to UFS, stuff we do not support out of the box like shareiscsi, zones) - quick start (get people started) - Admin Guide - zpool creation and destriction - Adding/Removing devices - Adding ZIL, L2ARC, hot spares - Dealing with failed devices - Upgrading a pool - Importing and exporting a pool - Checking the status of a pool - Performance monitoring (Built-in tools like iostat) - zpool split - ZFS administration - creating and destroying filesystems (explained in the terminology section) - creating and destroying volumes - renaming datasets - dataset properties (setting and querying as a general concept) - snapshots - clones - replication (you replicate a dataset, not an entire pool) - quota/reservation - compression - deduplication (copies property could go well in here, describe tradeoffs) - ZFS volumes - delegated administration - ZFS advanced topics and troubleshooting - root-on-ZFS installation? (or does this go in the bsdinstall chapter) - trouble booting off ZFS - BEADM? - zdb (?) - Fixing common problems one might encounter (devices offline, could be part of the zpool section) - Tuning recommendations? - ZFS on i386 - Links to ZFS evil tuning guide and other docs covering ZFS in even greater detail From owner-freebsd-doc@FreeBSD.ORG Tue Jul 16 02:25:43 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B849B5BE for ; Tue, 16 Jul 2013 02:25:43 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 7AB548A4 for ; Tue, 16 Jul 2013 02:25:43 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6G2PbCD075028 for ; Mon, 15 Jul 2013 20:25:37 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6G2Pbso075025 for ; Mon, 15 Jul 2013 20:25:37 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 15 Jul 2013 20:25:37 -0600 (MDT) From: Warren Block To: doc@freebsd.org Subject: Entities: DocBook versus XHTML 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]); Mon, 15 Jul 2013 20:25:37 -0600 (MDT) X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2013 02:25:43 -0000 The FDP Primer, which I have been bludgeoning lately, has no section that really tells the basic FreeBSD-specific entities available, either in XHTML or DocBook or both. The XHTML section does not show the correct way to refer to a Handbook chapter or an article. &os; is only used a couple of times in the entire FDP Primer, and those are new, and I added them! So please, let's collect a list of the most basic entities, and add it. I'm also curious to know why some but not all of the DocBook entities can be used in XHTML. FreeBSD DocBook Entities Entity Name Expands To ------------------------------------ &os; FreeBSD &os.current; FreeBSD-CURRENT &os.stable; FreeBSD-STABLE &url.books.handbook; ../../../.. Effectively, that last one works out to http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook FreeBSD XHTML Entities Entity Name Expands To ------------------------------------ &base; http://www.freebsd.org From owner-freebsd-doc@FreeBSD.ORG Tue Jul 16 02:52:21 2013 Return-Path: Delivered-To: freebsd-doc@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id BB82CC88; Tue, 16 Jul 2013 02:52:21 +0000 (UTC) (envelope-from wblock@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 946F7980; Tue, 16 Jul 2013 02:52:21 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r6G2qL3c096282; Tue, 16 Jul 2013 02:52:21 GMT (envelope-from wblock@freefall.freebsd.org) Received: (from wblock@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6G2qLuf096281; Tue, 16 Jul 2013 02:52:21 GMT (envelope-from wblock) Date: Tue, 16 Jul 2013 02:52:21 GMT Message-Id: <201307160252.r6G2qLuf096281@freefall.freebsd.org> To: jgh@FreeBSD.org, wblock@FreeBSD.org, freebsd-doc@FreeBSD.org, wblock@FreeBSD.org From: wblock@FreeBSD.org Subject: Re: docs/180289: [patch] suggest bsdinstall and portsnap for installation methods of ports collection X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2013 02:52:21 -0000 Synopsis: [patch] suggest bsdinstall and portsnap for installation methods of ports collection State-Changed-From-To: open->closed State-Changed-By: wblock State-Changed-When: Tue Jul 16 02:51:25 UTC 2013 State-Changed-Why: Rewrite committed. Responsible-Changed-From-To: freebsd-doc->wblock Responsible-Changed-By: wblock Responsible-Changed-When: Tue Jul 16 02:51:25 UTC 2013 Responsible-Changed-Why: Take. http://www.freebsd.org/cgi/query-pr.cgi?pr=180289 From owner-freebsd-doc@FreeBSD.ORG Tue Jul 16 03:08:06 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A60C5F2F for ; Tue, 16 Jul 2013 03:08:06 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 4DECEAF0 for ; Tue, 16 Jul 2013 03:08:06 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6G384Mm075322; Mon, 15 Jul 2013 21:08:04 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6G38337075319; Mon, 15 Jul 2013 21:08:04 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Mon, 15 Jul 2013 21:08:03 -0600 (MDT) From: Warren Block To: Allan Jude Subject: Re: Project GRUDS: Handbook disk reorg In-Reply-To: <51E4915F.9010303@allanjude.com> Message-ID: References: <51E4915F.9010303@allanjude.com> 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, 15 Jul 2013 21:08:04 -0600 (MDT) Cc: freebsd-doc@freebsd.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2013 03:08:06 -0000 On Mon, 15 Jul 2013, Allan Jude wrote: > Notes: > Quick-start section should probably cover installation with 'root on zfs' Excellent point! We really need to make the quick start sections almost mandatory. Added to outline. > Hardware chapter might mention SAS and things like SAS expanders and > other enterprise hardware considerations Yes. Added to outline. > The metadata storage location conflicts chapter is a really good idea. > whole-disk GEOM + GPT is basically not possible, so you get in to > per-partition GEOMs There is a little section about this in the new RAID1 (gmirror) section. > The labels bit should probably talk a bit about ZFS gUIDs and how ZFS > does labels (this is both metadata and a label...) too Added to outline. > The GEOM chapter should have at least a small stub for each GEOM type, > like cache, journal, multipath, etc Agreed. The hard part is getting people to write the missing ones. > For the ZFS chapter, this is the structure that bcr@ and myself proposed > at the last docsprint (this is probably a lot more detail than you need, > but if anyone has suggestions or ideas for additional things to do, > please let me know): > > ZFS > - ZFS introduction (what is ZFS) > - ZFS Features and Terminology (giant table of definitions) I have not really looked at the new section yet, but I did see the giant table. Personally, I'd rather have a gentle introduction that builds up, and then definitions later. It reminds me of instructions on recording menus for phone systems. They said not to put the number first ("Press one for..."), because it gives people anxiety about remembering that number. Instead, put the description first, then the thing to remember last: "For help, press one." In computer terms, a lot of definitions I have to remember won't help me as much as an introductory section that says "ZFS storage devices, called *zpools*, can be a single disk or group of disks." And then build on that. Later sections would have full detail and definitions. Thanks! From owner-freebsd-doc@FreeBSD.ORG Tue Jul 16 20:08:36 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 19CC7620 for ; Tue, 16 Jul 2013 20:08:36 +0000 (UTC) (envelope-from baker.victoria33@gmail.com) Received: from 12-185.sl.smtp.com (12-185.sl.smtp.com [192.40.185.12]) by mx1.freebsd.org (Postfix) with ESMTP id DFFB7E99 for ; Tue, 16 Jul 2013 20:08:35 +0000 (UTC) X-MSFBL: ZnJlZWJzZC1kb2NAZnJlZWJzZC5vcmdAMTkyXzQwXzE4NV8xMkBzbXRwY29tXzRA DKIM-Signature: v=1; a=rsa-sha256; d=smtp.com; s=smtpcomcustomers; c=relaxed/simple; q=dns/txt; i=@smtp.com; t=1374004109; h=From:Subject:To:Date:Mime-Version:Content-Type; bh=2C0SxZflzyEyzR81fgj9RaQHMNOkhDKVWnNWmOAn7fA=; b=TYdn5+rxHu2Z7UuZZjEnSOzg8+QSLfQpmfTsAk7Gs2bovw5n1N9H1Nc+mRLxDvkF NbuJUnTFbNA3Xy1YiC9E6EX+Oh5yxw2tiFE8JS9/R12/DgwTtEcakvxJBpV3Jh0S vHA9DTxLlKbtxOqYgvcO7cXlmhhuzUauUKi7Bi7lyZM=; Received: from [54.224.25.235] ([54.224.25.235:59249] helo=offandawaymail.com) by sl-mta03 (envelope-from ) (ecelerity 3.3.2.44647 r(44647)) with ESMTPA id 47/37-29968-D83A5E15; Tue, 16 Jul 2013 19:48:29 +0000 Received: from offandawaymail.com (localhost [127.0.0.1]) by offandawaymail.com (Postfix) with ESMTP id CC6F63A44 for ; Tue, 16 Jul 2013 19:44:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha1; c=simple; d=offandawaymail.com; h= message-id:mime-version:from:to:subject:date:content-type :content-transfer-encoding; s=postfix; bh=6CwzHzUVHpsjG5Wxa6XMcF 1xqZ0=; b=EAXQxGlz1s/aCVIfW53wQ9TqjHybC2/Ex5hQox3P9e3+PeXyFvciBp +wtxvPhX2SD7QMCoVRwalhTDH4QF4NrUY+MwcTTtkFEtPxkVecRZZKjnKsKpfQ0m SzgzN8sze+G98o7DPR0PL19PdH3dr8EDLmKIvGQQfQfVOuDwgk69g= Message-Id: Mime-Version: 1.0 From: Victoria Baker To: there Subject: Checking in on Health Sector Undergraduate and Graduate Program Directory Date: Tue, 16 Jul 2013 12:48:26 -0700 Content-Type: text/plain; charset=iso-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-SMTPCOM-Tracking-Number: c9179c2e-2c5c-47cc-a1a3-af4676aa256d X-SMTPCOM-Sender-ID: 106785 X-SMTPCOM-Spam-Policy: SMTP.com is a paid relay service. We do not tolerate UCE of any kind. Please report it ASAP to abuse@smtp.com X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Jul 2013 20:08:36 -0000 Hi there, I hope you are well=2E I wanted see if you are the person responsible for m= aintaining this page: http://www=2Efreebsd=2Eorg/projects/newbies=2Ehtml= =2E I have a few questions that I am hoping you can help me with=2E If you are = not the right contact, please forward me or let me know who I should contac= t=2E Hope to hear back from you soon=2E Thank you, Victoria Baker From owner-freebsd-doc@FreeBSD.ORG Wed Jul 17 01:07:11 2013 Return-Path: Delivered-To: doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B3BC176A for ; Wed, 17 Jul 2013 01:07:11 +0000 (UTC) (envelope-from rwoolley@croftagencies.com) Received: from hapkido.dreamhost.com (hapkido.dreamhost.com [66.33.216.122]) by mx1.freebsd.org (Postfix) with ESMTP id 9E924AEB for ; Wed, 17 Jul 2013 01:07:10 +0000 (UTC) Received: from homiemail-a60.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by hapkido.dreamhost.com (Postfix) with ESMTP id 2E4AD4F0 for ; Tue, 16 Jul 2013 18:07:10 -0700 (PDT) Received: from homiemail-a60.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a60.g.dreamhost.com (Postfix) with ESMTP id 4C5E13BC06A; Tue, 16 Jul 2013 18:07:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=croftagencies.com; h=to :date:subject:from:mime-version:content-type:message-id; s= croftagencies.com; bh=eoGGVehmprBD+BtZXnNP+LlS0ro=; b=jJ8uSncWhK 6Az5ffbMro71FynDZetrlP4lnt3M9PN+8aqGFdAh+vtHb39z2Xz9b7ov/IcJ0hYu at5nwEfDNtFV0wo5UitA/abhIIX48SyVwvwcRw5ABbnM5GawfLIs+MHxEfssyEdf nYMW1MNulDObQA++fSzzrNWqO4bWUEtao= Received: from jtlzajjiyw (unknown [84.23.206.168]) (Authenticated sender: rwoolley@croftagencies.com) by homiemail-a60.g.dreamhost.com (Postfix) with ESMTPA id AED7B3BC063; Tue, 16 Jul 2013 18:07:02 -0700 (PDT) To: , , Date: Wed, 17 Jul 2013 01:59:50 -0700 Subject: From: rwoolley@croftagencies.com Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Message-Id: <20130717010702.AED7B3BC063@homiemail-a60.g.dreamhost.com> X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 01:07:11 -0000 kawumup r vak rehe hawutet wyh rax sy http://import-beer.ru/movie.htm?wirat t jopo From owner-freebsd-doc@FreeBSD.ORG Wed Jul 17 17:06:30 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CC82B41E for ; Wed, 17 Jul 2013 17:06:30 +0000 (UTC) (envelope-from bsd-lists@1command.com) Received: from udns.ultimateDNS.NET (ultimatedns.net [209.180.214.225]) by mx1.freebsd.org (Postfix) with ESMTP id 9E95DE17 for ; Wed, 17 Jul 2013 17:06:30 +0000 (UTC) Received: from udns.ultimateDNS.NET (localhost [127.0.0.1]) by udns.ultimateDNS.NET (8.14.5/8.14.5) with ESMTP id r6HH6eGl011183 for ; Wed, 17 Jul 2013 10:06:46 -0700 (PDT) (envelope-from bsd-lists@1command.com) Received: (from www@localhost) by udns.ultimateDNS.NET (8.14.5/8.14.5/Submit) id r6HH6Zf7011182; Wed, 17 Jul 2013 10:06:35 -0700 (PDT) (envelope-from bsd-lists@1command.com) Received: from udns.ultimatedns.net ([209.180.214.225]) (UDNSMS authenticated user chrish) by ultimatedns.net with HTTP; Wed, 17 Jul 2013 10:06:35 -0700 (PDT) Message-ID: <277961ac69def97aea03aa52dae647cb.authenticated@ultimatedns.net> Date: Wed, 17 Jul 2013 10:06:35 -0700 (PDT) Subject: mysql_upgrade man, and upgrade/install info missing manditory information From: "Chris H" To: "freebsd-doc" User-Agent: UDNSMS/2.0.3 MIME-Version: 1.0 Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Jul 2013 17:06:30 -0000 Greetings, I recently performed an upgrade/update, which required upgrading mysql-server from mysql-server-5.5.30 --> mysql-server-5.5.32. At the end of the process, the message indicated it was necessary to perform mysql_ugrade(1). Doing so, led to the following: mysql_upgrade -u root --verbose Looking for 'mysql' as: mysql Looking for 'mysqlcheck' as: mysqlcheck FATAL ERROR: Upgrade failed _extremely_ informative -- no? So what to do? A quick check of the server, and the databases indicate all appear to normal. Conclusion; dismiss the mysql_upgrade(1) as being broken, and forget about it. The man(1) pages reveal nothing pertinent, in fact they are essentially the same page as: http://dev.mysql.com/doc/refman/5.5/en/mysql-upgrade.html with one _major_ exception; the user comments at the end. In particular; the one at the end: mysql_upgrade -u root -p The -p makes all the difference. But unlike: mysql -u root add ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) The omission of the -p does _not_ provide an informative error, as mysql, and all of it's other utilities _do_. Please make references to this in both the mysql_upgrade(1) man(1) page && the install/upgrade message emitted at the end of the install/upgrade. Additional reference: http://forums.freebsd.org/showthread.php?t=40884 Thank you for all your time, and consideration. --chris From owner-freebsd-doc@FreeBSD.ORG Thu Jul 18 02:43:57 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 3C08E4FB for ; Thu, 18 Jul 2013 02:43:57 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) by mx1.freebsd.org (Postfix) with ESMTP id DA5A3D06 for ; Thu, 18 Jul 2013 02:43:56 +0000 (UTC) X-AuditID: 12074422-b7ef78e000000935-57-51e75666e538 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 89.8E.02357.66657E15; Wed, 17 Jul 2013 22:43:50 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id r6I2hnFJ003233; Wed, 17 Jul 2013 22:43:50 -0400 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id r6I2hl7J027142 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 17 Jul 2013 22:43:49 -0400 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id r6I2hlWI026230; Wed, 17 Jul 2013 22:43:47 -0400 (EDT) Date: Wed, 17 Jul 2013 22:43:46 -0400 (EDT) From: Benjamin Kaduk To: Chris H Subject: Re: mysql_upgrade man, and upgrade/install info missing manditory information In-Reply-To: <277961ac69def97aea03aa52dae647cb.authenticated@ultimatedns.net> Message-ID: References: <277961ac69def97aea03aa52dae647cb.authenticated@ultimatedns.net> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLIsWRmVeSWpSXmKPExsUixCmqrJsW9jzQ4MN9JYvO+a9YLE6d6WJ1 YPL4cuU5k8eMT/NZApiiuGxSUnMyy1KL9O0SuDLOd89nLtjLWbHscBdTA+Mz9i5GTg4JAROJ 37/nM0HYYhIX7q1n62Lk4hAS2McocejIRWYIZyOjxNSJZ5ggnENMEiePH4Mqa2CU+PFnBgtI P4uAtsT3g0sZQWw2ARWJmW82soHYIkD2zQvLWEFsZgFNicObn4HtExaIkLi9/AFQDQcHp4Cv xMlZbiBhXgFHiY6Jl8BKhAR8JN5PaAUbIyqgI7F6/xQWiBpBiZMzn7BAjLSUOPfnOtsERsFZ SFKzkKQWMDKtYpRNya3SzU3MzClOTdYtTk7My0st0jXVy80s0UtNKd3ECApVdhelHYw/Dyod YhTgYFTi4TXkfx4oxJpYVlyZe4hRkoNJSZS3MAQoxJeUn1KZkVicEV9UmpNafIhRgoNZSYS3 3Awox5uSWFmVWpQPk5LmYFES53329GygkEB6YklqdmpqQWoRTFaGg0NJgvcwyFDBotT01Iq0 zJwShDQTByfIcB6g4d2hIMOLCxJzizPTIfKnGBWlxHlVQBICIImM0jy4XlgqecUoDvSKMG8z SBUPMA3Bdb8CGswENLh59mOQwSWJCCmpBsZUdyMPhr7/uxcE1MQHa+fcuLTgw7YzWc0LtZqm 1VWybnRNuNt6qLky/er7g+lS8ukp6XPY9Q9eWx1nkmSw3LKVYeGEP2ps06I1xaLM//vWb16Q uiPaMcJisxlTl0jReTmVzUq9iWUsvcs+qvrObwt/lPxpxUVBr1zr7RNU+oofcD2w1UqJVmIp zkg01GIuKk4EADQ5qrcAAwAA Cc: freebsd-doc X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Jul 2013 02:43:57 -0000 On Wed, 17 Jul 2013, Chris H wrote: > The -p makes all the difference. But unlike: > mysql -u root add > ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO) > The omission of the -p does _not_ provide an informative error, as mysql, and all > of it's other utilities _do_. > Please make references to this in both the mysql_upgrade(1) man(1) page && the mysql is not part of the FreeBSD base system; it is an external piece of software that is made available through the FreeBSD Ports Collection. > install/upgrade message emitted at the end of the install/upgrade. > Additional reference: http://forums.freebsd.org/showthread.php?t=40884 The mysql_upgrade manual page is part of the upstream mysql distribution, and any changes to it must go through upstream. The message displayed at the end of the install/upgrade is http://svnweb.freebsd.org/ports/head/databases/mysql55-server/pkg-message?revision=311815&view=markup ; you could contact the maintainer (ale@freebsd.org) via PR or directly to ask about changing that text. I'm sorry that the forums sent you to a not-quite-correct location for getting your concerns addressed. -Ben Kaduk From owner-freebsd-doc@FreeBSD.ORG Fri Jul 19 06:21:40 2013 Return-Path: Delivered-To: www@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id EEC1E250 for ; Fri, 19 Jul 2013 06:21:39 +0000 (UTC) (envelope-from linkseo12@gmail.com) Received: from mail-pb0-x241.google.com (mail-pb0-x241.google.com [IPv6:2607:f8b0:400e:c01::241]) by mx1.freebsd.org (Postfix) with ESMTP id CBEE7243 for ; Fri, 19 Jul 2013 06:21:39 +0000 (UTC) Received: by mail-pb0-f65.google.com with SMTP id un1so1773590pbc.4 for ; Thu, 18 Jul 2013 23:21:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=reply-to:from:to:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language:disposition-notification-to; bh=8NVNjWLhwdK4VtFFhGr6uNM/dDe3cPjkoiJSAxkowfo=; b=qTOGfk4Nuqy00UYZM1fut/6jC+u6CuRqPYus7kaRPSWiTO3SFxU6fW7BLwham4arEO QV70ZvINAEWFPRr3bGxIWvRgO4C8LkyuF33V5xzmZCB8wlSWPTRNPeU/ll85C1aHkj/A OxmyQx6l3fVmutnOxhKbHKnDi+N7y7NtHHyB+mmAhad3JYAcJPXL6Y5WhQG4fnmaTYKR XgsjlxANtH5hEf469b0PiMebM2WBqHt9slUl8K8qT2YoSds6VQm+sEKDGhKErzuZmEhI ZN27RpFKxQ5Ab2R+X0lQ4oS36YDHt7ZXG3G1iQsh5hG1wgf+OOc2NjmL/f5lZbG+rj/r AJpQ== X-Received: by 10.68.242.105 with SMTP id wp9mr15502693pbc.153.1374214899607; Thu, 18 Jul 2013 23:21:39 -0700 (PDT) Received: from SWPC ([122.177.214.179]) by mx.google.com with ESMTPSA id sq5sm20720880pab.11.2013.07.18.23.21.37 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Thu, 18 Jul 2013 23:21:38 -0700 (PDT) From: "Swati Patel" To: Subject: Site-look-designing Date: Fri, 19 Jul 2013 11:51:32 +0530 Message-ID: MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac6ESDKky4QzgxCtQqmCMLSQkdRTwQ== Content-Language: en-us Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: linkseo12@gmail.com List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 06:21:40 -0000 Greetings of the day! We are one of the leading on line Marketing Company with the core Skills in Website Design and Development. We have vast experience in dealing with the clients across the globe; most of our clients are from US, Europe, Australia, Canada, Germany and Netherlands. We have a strong, highly experienced and dedicated team with relative experience in developing the websites. You can use us for your website www.freebsd.org or for creation of any new ones. Our creative team is competent enough to convert your ideas into the real working websites. We have earned 5000+ hours working experience in developing the professional design with attractive approach in the latest technologies like Joomla, Magento, Zencart, Wordpress, Code Igniter (CI), Core PHP, OS Commerce etc. All the developed projects cater into the various markets ranging from small to large Business Enterprises. We would like to collect your thoughts so that we could show you our creativity. Look forward to your positive reply with our services. Regards, Swati Patel Website Development Manager From owner-freebsd-doc@FreeBSD.ORG Fri Jul 19 10:43:35 2013 Return-Path: Delivered-To: www@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 833F2379 for ; Fri, 19 Jul 2013 10:43:35 +0000 (UTC) (envelope-from increaseyoursitlink@gmail.com) Received: from mail-pd0-x241.google.com (mail-pd0-x241.google.com [IPv6:2607:f8b0:400e:c02::241]) by mx1.freebsd.org (Postfix) with ESMTP id 615B1FDA for ; Fri, 19 Jul 2013 10:43:35 +0000 (UTC) Received: by mail-pd0-f193.google.com with SMTP id v10so1524149pde.4 for ; Fri, 19 Jul 2013 03:43:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=reply-to:from:to:subject:date:message-id:mime-version:content-type :x-mailer:thread-index:content-language; bh=rFvNV3YZdOrpd8G+u6UOxXf6IM4IEdGp32utf3QdiBw=; b=DpnxGNuwq5u3mVcLZk96N8c2m8Fjd2GWIGrnN6H6mYXkx7s5TRNWE5A9girJdZEsh7 AFG38NDFUtZqFDKyFLeLxPdKel1xVNE89WNJPSREdIvQyYmImzhAYcyBkd7vVGP8a9Gn XkRmpl0e7gxdalgIKVYn7EDZb4NoIdRW1BYpckDQ6t0EyZFyD4c0/317Gzu8CtasT8LU oOCZBiMNkwb0rJdWoIIm0gIZjo0fGKQsYnv2UbdGpFpfxMXVr3rxLwWRbS6hLCER4X8t 7zCWnhNl1LTZF3BWrfqK48ybhQU6dn2WpLYSeGSvc0i5UPtgin92dewKdifPONAWLTht nwIg== X-Received: by 10.68.213.135 with SMTP id ns7mr16784983pbc.5.1374230615231; Fri, 19 Jul 2013 03:43:35 -0700 (PDT) Received: from xp ([182.68.21.58]) by mx.google.com with ESMTPSA id s5sm18877958pbo.38.2013.07.19.03.43.32 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 19 Jul 2013 03:43:34 -0700 (PDT) From: "Avanish Mathur \(SEO\)" To: Subject: 1st Page On Google!!! Date: Fri, 19 Jul 2013 16:13:02 +0530 Message-ID: <023001ce846c$d33c93a0$79b5bae0$@com> MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook 12.0 Thread-Index: Ac6EbL226YQ7OhA6RvymJa++1XEVDw== Content-Language: en-us Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: increaseyoursitlink@gmail.com List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 10:43:35 -0000 Hi, *Rank your website top on the major search engines.* Do you want to know why your competitors are showing up over your Website on Google, Yahoo or Bing and how you can rank on top to first Place for your keywords? How important is your Internet marketing or SEO company? Consider these stats: . 97% of customers research online before buying . 92% of customers contact a business immediately after searching . 80% of search engine traffic goes to the top 3 organic results . 7-to-1 returns on investment for the average SEO campaign Ranking top on the major search engines will increase your sales *Our SEO Services Will:* Get your website ranked top on the search major search engines for your targeted keywords . Dominate your market over competitors . Boost your websites sales . Increase targeted traffic I look forward to your positive reply. Best Regards, Avanish Online Marketing consultant (Best team Business) From owner-freebsd-doc@FreeBSD.ORG Fri Jul 19 16:30:01 2013 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]) by hub.freebsd.org (Postfix) with ESMTP id C2C08235 for ; Fri, 19 Jul 2013 16:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id E3B4B304 for ; Fri, 19 Jul 2013 16:30: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 r6JGU03V065319 for ; Fri, 19 Jul 2013 16:30:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r6JGU0ri065318; Fri, 19 Jul 2013 16:30:00 GMT (envelope-from gnats) Resent-Date: Fri, 19 Jul 2013 16:30:00 GMT Resent-Message-Id: <201307191630.r6JGU0ri065318@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, Michael W Lucas Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6C977F1 for ; Fri, 19 Jul 2013 16:28:17 +0000 (UTC) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: from bewilderbeast.blackhelicopters.org (mwlucas-2-pt.tunnel.tserv9.chi1.ipv6.he.net [IPv6:2001:470:1f10:b9c::2]) by mx1.freebsd.org (Postfix) with ESMTP id 1AE682D2 for ; Fri, 19 Jul 2013 16:28:16 +0000 (UTC) Received: from bewilderbeast.blackhelicopters.org (localhost [127.0.0.1]) by bewilderbeast.blackhelicopters.org (8.14.5/8.14.5) with ESMTP id r6JGSFMI006808 for ; Fri, 19 Jul 2013 12:28:16 -0400 (EDT) (envelope-from mwlucas@bewilderbeast.blackhelicopters.org) Received: (from mwlucas@localhost) by bewilderbeast.blackhelicopters.org (8.14.5/8.14.5/Submit) id r6JGSFLh006807; Fri, 19 Jul 2013 12:28:15 -0400 (EDT) (envelope-from mwlucas) Message-Id: <201307191628.r6JGSFLh006807@bewilderbeast.blackhelicopters.org> Date: Fri, 19 Jul 2013 12:28:15 -0400 (EDT) From: Michael W Lucas To: FreeBSD-gnats-submit@freebsd.org X-Send-Pr-Version: 3.114 Subject: docs/180658: add detail to pkgng part of the handbook X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Michael W Lucas List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 16:30:01 -0000 >Number: 180658 >Category: docs >Synopsis: add detail to pkgng part of the handbook >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: Fri Jul 19 16:30:00 UTC 2013 >Closed-Date: >Last-Modified: >Originator: Michael W Lucas >Release: FreeBSD 10.0-CURRENT amd64 >Organization: FreeBSD Committer Alumni >Environment: System: FreeBSD bewilderbeast.blackhelicopters.org 10.0-CURRENT FreeBSD 10.0-CURRENT #15: Thu Nov 8 14:02:45 EST 2012 mwlucas@bewilderbeast.blackhelicopters.org:/usr/obj/usr/src/sys/GENERIC amd64 Based on: http://www.freebsd.org/doc/handbook/pkgng-intro.html >Description: The pkgng setup for 9.1 tells users to use the pkg command to convert to pkgng. The pkg command is not suitable for scripting or automated installs, as it requires human intervention. You can still use pkg_add -r pkg to perform the conversion, however. >How-To-Repeat: Try to write an Ansible playbook to convert from pkg_add to pkgng while using pkg. >Fix: I don't have a current docs hacking environment set up, but I figured if I wrote some text and sent it in an active committer would happily take it. At least, that's what we did back in FreeBSD's Bronze Age. ;-) I would recommend some text like this. FreeBSD 9.1 and later includes a utility for interactive "bootstrapping" of pkgng. This bootstrap utility downloads and installs pkgng. To bootstrap the system, run: # /usr/sbin/pkg For non-interactive pkgng installs use the pkgng package, as used in older FreeBSD versions. >Release-Note: >Audit-Trail: >Unformatted: From owner-freebsd-doc@FreeBSD.ORG Fri Jul 19 19:42:57 2013 Return-Path: Delivered-To: freebsd-doc@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1C8F6BCB; Fri, 19 Jul 2013 19:42:57 +0000 (UTC) (envelope-from marc@blackend.org) Received: from smtp6-g21.free.fr (smtp6-g21.free.fr [IPv6:2a01:e0c:1:1599::15]) by mx1.freebsd.org (Postfix) with ESMTP id 8435EDD7; Fri, 19 Jul 2013 19:42:53 +0000 (UTC) Received: from emphyrio.blackend.org (unknown [88.179.1.53]) by smtp6-g21.free.fr (Postfix) with ESMTP id 6F388822EC; Fri, 19 Jul 2013 21:42:48 +0200 (CEST) Received: from emphyrio.blackend.org (localhost [127.0.0.1]) by emphyrio.blackend.org (8.14.5/8.14.4) with ESMTP id r6JJgliM006113; Fri, 19 Jul 2013 21:42:47 +0200 (CEST) (envelope-from marc@emphyrio.blackend.org) Received: (from marc@localhost) by emphyrio.blackend.org (8.14.5/8.14.4/Submit) id r6JJgklI006112; Fri, 19 Jul 2013 21:42:46 +0200 (CEST) (envelope-from marc) Date: Fri, 19 Jul 2013 21:42:46 +0200 From: Marc Fonvieille To: freebsd-doc@FreeBSD.org Subject: HEADS UP: doc/ slush for 9.2R begins on 25 July, 2013 Message-ID: <20130719194246.GA1657@emphyrio.blackend.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S" Content-Disposition: inline X-Useless-Header: blackend.org X-Operating-System: FreeBSD 8.3-STABLE User-Agent: Mutt/1.5.21 (2010-09-15) Cc: doceng@FreeBSD.org, re@FreeBSD.org X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Jul 2013 19:42:57 -0000 --AhhlLboLdkugWU4S Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all, The doc slush will begin on 25 July, 2013. The purpose of the doc slush is to slow down the rate of changes in that tree in order to allow the translation teams time to finalize their work and to avoid last-minute breakage for the 9.2-RELEASE. Please note that the slush will not apply to /htdocs documents. As usual, this is not a real freeze and requires no formal commit approval procedure for your commit, but you are kindly requested not to commit large, structural changes during that period. Tagging of the doc tree is scheduled to take place on 2 August, 2013. Thank you for your cooperation and keep up the good work! --=20 Marc on behalf of doceng@ --AhhlLboLdkugWU4S Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iD8DBQFR6Za2zQ9RwE+OdOgRAsEFAJ9DII6RAYSa0gIxWHymflTmdnKsoACfS/gt igrBdhPKfTYfOUjCsEx1/Lc= =v1B/ -----END PGP SIGNATURE----- --AhhlLboLdkugWU4S-- From owner-freebsd-doc@FreeBSD.ORG Sat Jul 20 07:15:17 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BD658F8B; Sat, 20 Jul 2013 07:15:17 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 4B3257C5; Sat, 20 Jul 2013 07:15:17 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-143-198.lns20.adl6.internode.on.net [118.210.143.198]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id r6K7EvQO027742 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 20 Jul 2013 16:45:03 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Trouble building release with docs From: "Daniel O'Connor" Date: Sat, 20 Jul 2013 16:44:56 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: To: freebsd-doc@freebsd.org X-Mailer: Apple Mail (2.1508) X-Spam-Score: 0.163 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-stable stable X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 07:15:17 -0000 Hi, I am trying to do a full (customised) release of 9.1 but I am having = trouble building the docs. If I use NODOC it builds fine, but without = that I get.. [andenes 7:04] /usr/src/release #/usr/bin/time make release = BUILDNAME=3D$BUILDNAME =20 make -C /usr/src/release BUILDNAME=3D9.1-GENESIS obj make -C /usr/src/release BUILDNAME=3D9.1-GENESIS ftp cdrom memstick cd /usr/src/release/doc && make all install clean 'FORMATS=3Dhtml txt' = INSTALL_COMPRESSED=3D'' URLS_ABSOLUTE=3DYES = DOCDIR=3D/usr/obj/usr/src/release/rdoc =3D=3D=3D> en_US.ISO8859-1 (all) =3D=3D=3D> en_US.ISO8859-1/relnotes (all) /usr/bin/grep '^' article.xml > = article.parsed.xml.tmp grep: article.xml: No such file or directory *** [article.parsed.xml] Error code 2 Stop in /usr/src/release/doc/en_US.ISO8859-1/relnotes. *** [all] Error code 1 Stop in /usr/src/release/doc/en_US.ISO8859-1. *** [all] Error code 1 Stop in /usr/src/release/doc. *** [reldoc] Error code 1 Stop in /usr/src/release. *** [release] Error code 1 Stop in /usr/src/release. 0.48 real 0.37 user 0.10 sys There is article.sgml though.. I have installed textproc/docproj and I = can build /usr/docs fine. I have /usr/src r253451 and /usr/doc r42325. I can copy a doc distfile from a 'real' release since I'm not = customising that, but it would be nice to know what I'm doing wrong :) Thanks. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C From owner-freebsd-doc@FreeBSD.ORG Sat Jul 20 13:17:34 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 7AB8A8ED; Sat, 20 Jul 2013 13:17:34 +0000 (UTC) (envelope-from wblock@wonkity.com) Received: from wonkity.com (wonkity.com [67.158.26.137]) by mx1.freebsd.org (Postfix) with ESMTP id 3FFF9171; Sat, 20 Jul 2013 13:17:34 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id r6KDHXu7029874; Sat, 20 Jul 2013 07:17:33 -0600 (MDT) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id r6KDHWHg029871; Sat, 20 Jul 2013 07:17:33 -0600 (MDT) (envelope-from wblock@wonkity.com) Date: Sat, 20 Jul 2013 07:17:32 -0600 (MDT) From: Warren Block To: "Daniel O'Connor" Subject: Re: Trouble building release with docs 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]); Sat, 20 Jul 2013 07:17:33 -0600 (MDT) Cc: freebsd-doc@freebsd.org, freebsd-stable stable X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 13:17:34 -0000 On Sat, 20 Jul 2013, Daniel O'Connor wrote: > Hi, > I am trying to do a full (customised) release of 9.1 but I am having trouble building the docs. If I use NODOC it builds fine, but without that I get.. > [andenes 7:04] /usr/src/release #/usr/bin/time make release BUILDNAME=$BUILDNAME > make -C /usr/src/release BUILDNAME=9.1-GENESIS obj > make -C /usr/src/release BUILDNAME=9.1-GENESIS ftp cdrom memstick > cd /usr/src/release/doc && make all install clean 'FORMATS=html txt' INSTALL_COMPRESSED='' URLS_ABSOLUTE=YES DOCDIR=/usr/obj/usr/src/release/rdoc > ===> en_US.ISO8859-1 (all) > ===> en_US.ISO8859-1/relnotes (all) > /usr/bin/grep '^' article.xml > article.parsed.xml.tmp > grep: article.xml: No such file or directory > *** [article.parsed.xml] Error code 2 > > Stop in /usr/src/release/doc/en_US.ISO8859-1/relnotes. > *** [all] Error code 1 > > Stop in /usr/src/release/doc/en_US.ISO8859-1. > *** [all] Error code 1 > > Stop in /usr/src/release/doc. > *** [reldoc] Error code 1 > > Stop in /usr/src/release. > *** [release] Error code 1 > > Stop in /usr/src/release. > 0.48 real 0.37 user 0.10 sys > > There is article.sgml though.. I have installed textproc/docproj and I can build /usr/docs fine. What does svn say about that file? % cd /usr/src/release/doc/en_US.ISO8859-1/relnotes/ % svn stat The article.sgml suggests a leftover file from an earlier /usr/src that was not removed before svn checkout. That does not explain why article.xml is missing, though. It is present on my 9-stable and 8-stable checkouts. Maybe a mixed or partial checkout? From owner-freebsd-doc@FreeBSD.ORG Sat Jul 20 22:37:12 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id A97A9B34; Sat, 20 Jul 2013 22:37:12 +0000 (UTC) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (cain.gsoft.com.au [203.31.81.10]) by mx1.freebsd.org (Postfix) with ESMTP id 34D6585D; Sat, 20 Jul 2013 22:37:11 +0000 (UTC) Received: from ur.dons.net.au (ppp118-210-143-198.lns20.adl6.internode.on.net [118.210.143.198]) (authenticated bits=0) by cain.gsoft.com.au (8.14.4/8.14.3) with ESMTP id r6KMaua7075578 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sun, 21 Jul 2013 08:07:03 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Subject: Re: Trouble building release with docs Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Content-Type: text/plain; charset=us-ascii From: "Daniel O'Connor" In-Reply-To: Date: Sun, 21 Jul 2013 08:06:56 +0930 Content-Transfer-Encoding: quoted-printable Message-Id: <1636FC68-C225-492C-9599-26CA25A800AC@gsoft.com.au> References: To: Warren Block X-Mailer: Apple Mail (2.1508) X-Spam-Score: 0.163 () BAYES_00,RDNS_DYNAMIC X-Scanned-By: MIMEDefang 2.67 on 203.31.81.10 Cc: freebsd-doc@freebsd.org, freebsd-stable stable X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2013 22:37:12 -0000 On 20/07/2013, at 22:47, Warren Block wrote: >> There is article.sgml though.. I have installed textproc/docproj and = I can build /usr/docs fine. >=20 > What does svn say about that file? >=20 > % cd /usr/src/release/doc/en_US.ISO8859-1/relnotes/ > % svn stat ? article.parsed.xml.tmp > The article.sgml suggests a leftover file from an earlier /usr/src = that was not removed before svn checkout. That does not explain why = article.xml is missing, though. It is present on my 9-stable and = 8-stable checkouts. Maybe a mixed or partial checkout? I got a response on IRC, apparently my docproj port is too new to build = the sgml release docs. I think I'll just skip it for now, none of the documentation there is of = interest to me anyway. -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C