From owner-svn-doc-projects@FreeBSD.ORG Sun Nov 24 01:14:12 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id F14FE9F4; Sun, 24 Nov 2013 01:14:11 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id D981F2588; Sun, 24 Nov 2013 01:14:11 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rAO1EB4W049169; Sun, 24 Nov 2013 01:14:11 GMT (envelope-from gjb@svn.freebsd.org) Received: (from gjb@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id rAO1E956049150; Sun, 24 Nov 2013 01:14:09 GMT (envelope-from gjb@svn.freebsd.org) Message-Id: <201311240114.rAO1E956049150@svn.freebsd.org> From: Glen Barber Date: Sun, 24 Nov 2013 01:14:09 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43228 - in projects/sysctl: . da_DK.ISO8859-1/articles/ipsec-must da_DK.ISO8859-1/articles/pxe da_DK.ISO8859-1/share/xml da_DK.ISO8859-1/share/xsl de_DE.ISO8859-1/articles de_DE.ISO885... X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2013 01:14:12 -0000 Author: gjb Date: Sun Nov 24 01:14:03 2013 New Revision: 43228 URL: http://svnweb.freebsd.org/changeset/doc/43228 Log: MFH up to r43225: Merged /head/Makefile:r42573-43225 Merged /head/README:r42573-43225 Merged /head/da_DK.ISO8859-1:r42573-43225 Merged /projects/db5/da_DK.ISO8859-1:r41723-43125 Merged /head/de_DE.ISO8859-1:r42803-43225 Merged /projects/db5/de_DE.ISO8859-1:r41723-43125 Merged /head/el_GR.ISO8859-7:r42803-43225 Merged /projects/db5/el_GR.ISO8859-7:r41723-43125 Merged /projects/db5/en_US.ISO8859-1:r41723-43125 Merged /head/en_US.ISO8859-1:r42803-43227 Merged /head/es_ES.ISO8859-1:r42573-43225 Merged /projects/db5/es_ES.ISO8859-1:r41723-43125 Merged /head/fr_FR.ISO8859-1:r42803-43225 Merged /projects/db5/fr_FR.ISO8859-1:r41723-43125 Merged /projects/db5/hu_HU.ISO8859-2:r41723-43125 Merged /head/hu_HU.ISO8859-2:r42803-43225 Merged /head/it_IT.ISO8859-15:r42573-43225 Merged /projects/db5/it_IT.ISO8859-15:r41723-43125 Merged /head/ja_JP.eucJP:r42803-43225 Merged /projects/db5/ja_JP.eucJP:r41723-43125 Merged /head/mn_MN.UTF-8:r42803-43225 Merged /projects/db5/mn_MN.UTF-8:r41723-43125 Merged /head/nl_NL.ISO8859-1:r42803-43225 Merged /projects/db5/nl_NL.ISO8859-1:r41723-43125 Merged /projects/db5/no_NO.ISO8859-1:r41723-43125 Merged /head/no_NO.ISO8859-1:r42573-43225 Merged /head/pl_PL.ISO8859-2:r42803-43225 Merged /projects/db5/pl_PL.ISO8859-2:r41723-43125 Merged /head/pt_BR.ISO8859-1:r42573-43225 Merged /projects/db5/pt_BR.ISO8859-1:r41723-43125 Merged /head/release:r42573-43225 Merged /projects/db5/release:r41723-43125 Merged /head/ru_RU.KOI8-R:r42803-43225 Merged /projects/db5/ru_RU.KOI8-R:r41723-43125 Merged /head/share:r42803-43225 Merged /projects/db5/share:r41723-43125 Merged /head/sr_YU.ISO8859-2:r42573-43225 Merged /projects/db5/sr_YU.ISO8859-2:r41723-43125 Merged /head/tr_TR.ISO8859-9:r42573-43225 Merged /projects/db5/tr_TR.ISO8859-9:r41723-43125 Merged /head/zh_TW.Big5:r42573-43225 Merged /projects/db5/zh_TW.Big5:r41723-43125 Approved by: doceng (implicit) Sponsored by: The FreeBSD Foundation Added: projects/sysctl/da_DK.ISO8859-1/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/da_DK.ISO8859-1/share/xml/freebsd-xhtml.xsl projects/sysctl/de_DE.ISO8859-1/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/de_DE.ISO8859-1/share/xml/freebsd-xhtml.xsl projects/sysctl/el_GR.ISO8859-7/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/el_GR.ISO8859-7/share/xml/freebsd-xhtml.xsl projects/sysctl/en_US.ISO8859-1/books/fdp-primer/psgml-mode/ - copied from r43227, head/en_US.ISO8859-1/books/fdp-primer/psgml-mode/ projects/sysctl/en_US.ISO8859-1/books/fdp-primer/sgml-markup/ - copied from r43227, head/en_US.ISO8859-1/books/fdp-primer/sgml-markup/ projects/sysctl/en_US.ISO8859-1/books/fdp-primer/sgml-primer/ - copied from r43227, head/en_US.ISO8859-1/books/fdp-primer/sgml-primer/ projects/sysctl/en_US.ISO8859-1/books/handbook/vinum/ - copied from r43227, head/en_US.ISO8859-1/books/handbook/vinum/ projects/sysctl/en_US.ISO8859-1/htdocs/5xx.xml - copied unchanged from r43227, head/en_US.ISO8859-1/htdocs/5xx.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/howto.xml - copied unchanged from r43227, head/en_US.ISO8859-1/htdocs/news/status/howto.xml projects/sysctl/es_ES.ISO8859-1/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/es_ES.ISO8859-1/share/xml/freebsd-xhtml.xsl projects/sysctl/fr_FR.ISO8859-1/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/fr_FR.ISO8859-1/share/xml/freebsd-xhtml.xsl projects/sysctl/hu_HU.ISO8859-2/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/hu_HU.ISO8859-2/share/xml/freebsd-xhtml.xsl projects/sysctl/it_IT.ISO8859-15/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/it_IT.ISO8859-15/share/xml/freebsd-xhtml.xsl projects/sysctl/ja_JP.eucJP/htdocs/releases/9.2R/installation.html - copied unchanged from r43225, head/ja_JP.eucJP/htdocs/releases/9.2R/installation.html projects/sysctl/ja_JP.eucJP/share/xml/freebsd-dblatex.xsl - copied unchanged from r43225, head/ja_JP.eucJP/share/xml/freebsd-dblatex.xsl projects/sysctl/ja_JP.eucJP/share/xml/freebsd-fo.xsl - copied unchanged from r43225, head/ja_JP.eucJP/share/xml/freebsd-fo.xsl projects/sysctl/ja_JP.eucJP/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/ja_JP.eucJP/share/xml/freebsd-xhtml.xsl projects/sysctl/mn_MN.UTF-8/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/mn_MN.UTF-8/share/xml/freebsd-xhtml.xsl projects/sysctl/nl_NL.ISO8859-1/books/handbook/vinum/ - copied from r43225, head/nl_NL.ISO8859-1/books/handbook/vinum/ projects/sysctl/pt_BR.ISO8859-1/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/pt_BR.ISO8859-1/share/xml/freebsd-xhtml.xsl projects/sysctl/ru_RU.KOI8-R/books/handbook/vinum/ - copied from r43225, head/ru_RU.KOI8-R/books/handbook/vinum/ projects/sysctl/ru_RU.KOI8-R/books/porters-handbook/uses.xml - copied unchanged from r43225, head/ru_RU.KOI8-R/books/porters-handbook/uses.xml projects/sysctl/ru_RU.KOI8-R/books/porters-handbook/versions.xml - copied unchanged from r43225, head/ru_RU.KOI8-R/books/porters-handbook/versions.xml projects/sysctl/ru_RU.KOI8-R/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/ru_RU.KOI8-R/share/xml/freebsd-xhtml.xsl projects/sysctl/share/misc/fop.xconf - copied unchanged from r43225, head/share/misc/fop.xconf projects/sysctl/share/pgpkeys/alexey.key - copied unchanged from r43225, head/share/pgpkeys/alexey.key projects/sysctl/share/pgpkeys/davidch.key - copied unchanged from r43225, head/share/pgpkeys/davidch.key projects/sysctl/share/pgpkeys/dteske.key - copied unchanged from r43225, head/share/pgpkeys/dteske.key projects/sysctl/share/pgpkeys/edavis.key - copied unchanged from r43225, head/share/pgpkeys/edavis.key projects/sysctl/share/pgpkeys/edwin.key - copied unchanged from r43225, head/share/pgpkeys/edwin.key projects/sysctl/share/pgpkeys/gleb.key - copied unchanged from r43225, head/share/pgpkeys/gleb.key projects/sysctl/share/pgpkeys/jmmv.key - copied unchanged from r43225, head/share/pgpkeys/jmmv.key projects/sysctl/share/pgpkeys/mr.key - copied unchanged from r43225, head/share/pgpkeys/mr.key projects/sysctl/share/pgpkeys/se.key - copied unchanged from r43225, head/share/pgpkeys/se.key projects/sysctl/share/pgpkeys/trociny.key - copied unchanged from r43225, head/share/pgpkeys/trociny.key projects/sysctl/share/security/advisories/FreeBSD-EN-13:04.freebsd-update.asc - copied unchanged from r43225, head/share/security/advisories/FreeBSD-EN-13:04.freebsd-update.asc projects/sysctl/share/security/advisories/FreeBSD-SA-13:14.openssh.asc - copied unchanged from r43225, head/share/security/advisories/FreeBSD-SA-13:14.openssh.asc projects/sysctl/share/security/patches/EN-13:04/ - copied from r43225, head/share/security/patches/EN-13:04/ projects/sysctl/share/security/patches/SA-13:14/ - copied from r43225, head/share/security/patches/SA-13:14/ projects/sysctl/share/tools/webupdate.wrapper - copied unchanged from r43225, head/share/tools/webupdate.wrapper projects/sysctl/share/xml/docbook-epub.css.xml - copied unchanged from r43225, head/share/xml/docbook-epub.css.xml projects/sysctl/share/xml/docbook50.dtd - copied unchanged from r43225, head/share/xml/docbook50.dtd projects/sysctl/share/xml/empty.xsl - copied unchanged from r43225, head/share/xml/empty.xsl projects/sysctl/share/xml/events2014.xml - copied unchanged from r43225, head/share/xml/events2014.xml projects/sysctl/share/xml/fo.titlepage.xml - copied unchanged from r43225, head/share/xml/fo.titlepage.xml projects/sysctl/share/xml/freebsd-common.xsl - copied unchanged from r43225, head/share/xml/freebsd-common.xsl projects/sysctl/share/xml/freebsd-dblatex.xsl - copied unchanged from r43225, head/share/xml/freebsd-dblatex.xsl projects/sysctl/share/xml/freebsd-epub.xsl - copied unchanged from r43225, head/share/xml/freebsd-epub.xsl projects/sysctl/share/xml/freebsd-fo-cjk.xsl - copied unchanged from r43225, head/share/xml/freebsd-fo-cjk.xsl projects/sysctl/share/xml/freebsd-fo-titlepage.xsl - copied unchanged from r43225, head/share/xml/freebsd-fo-titlepage.xsl projects/sysctl/share/xml/freebsd-fo.xsl - copied unchanged from r43225, head/share/xml/freebsd-fo.xsl projects/sysctl/share/xml/freebsd-pgpkeyring.xsl - copied unchanged from r43225, head/share/xml/freebsd-pgpkeyring.xsl projects/sysctl/share/xml/freebsd-xhtml-chunk.xsl - copied unchanged from r43225, head/share/xml/freebsd-xhtml-chunk.xsl projects/sysctl/share/xml/freebsd-xhtml-common.xsl - copied unchanged from r43225, head/share/xml/freebsd-xhtml-common.xsl projects/sysctl/share/xml/freebsd-xhtml-titlepage.xsl - copied unchanged from r43225, head/share/xml/freebsd-xhtml-titlepage.xsl projects/sysctl/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/share/xml/freebsd-xhtml.xsl projects/sysctl/share/xml/freebsd50.dtd - copied unchanged from r43225, head/share/xml/freebsd50.dtd projects/sysctl/share/xml/freebsd50.rnc - copied unchanged from r43225, head/share/xml/freebsd50.rnc projects/sysctl/share/xml/l10n-common.ent - copied unchanged from r43225, head/share/xml/l10n-common.ent projects/sysctl/share/xml/xhtml.titlepage.xml - copied unchanged from r43225, head/share/xml/xhtml.titlepage.xml projects/sysctl/sr_YU.ISO8859-2/share/xml/catalog.xml - copied unchanged from r43225, head/sr_YU.ISO8859-2/share/xml/catalog.xml projects/sysctl/zh_TW.Big5/share/xml/freebsd-dblatex.xsl - copied unchanged from r43225, head/zh_TW.Big5/share/xml/freebsd-dblatex.xsl projects/sysctl/zh_TW.Big5/share/xml/freebsd-fo.xsl - copied unchanged from r43225, head/zh_TW.Big5/share/xml/freebsd-fo.xsl projects/sysctl/zh_TW.Big5/share/xml/freebsd-xhtml.xsl - copied unchanged from r43225, head/zh_TW.Big5/share/xml/freebsd-xhtml.xsl Replaced: projects/sysctl/share/xml/catalog-cwd.xml - copied unchanged from r43225, head/share/xml/catalog-cwd.xml Deleted: projects/sysctl/da_DK.ISO8859-1/share/xml/catalog projects/sysctl/da_DK.ISO8859-1/share/xml/freebsd.dsl projects/sysctl/da_DK.ISO8859-1/share/xsl/ projects/sysctl/de_DE.ISO8859-1/share/xml/catalog projects/sysctl/de_DE.ISO8859-1/share/xml/freebsd.dsl projects/sysctl/de_DE.ISO8859-1/share/xsl/ projects/sysctl/el_GR.ISO8859-7/share/mk/ projects/sysctl/el_GR.ISO8859-7/share/xml/catalog projects/sysctl/el_GR.ISO8859-7/share/xml/freebsd.dsl projects/sysctl/el_GR.ISO8859-7/share/xsl/ projects/sysctl/en_US.ISO8859-1/htdocs/community/social.xml projects/sysctl/en_US.ISO8859-1/share/mk/ projects/sysctl/en_US.ISO8859-1/share/xml/catalog projects/sysctl/en_US.ISO8859-1/share/xml/freebsd.dsl projects/sysctl/en_US.ISO8859-1/share/xsl/ projects/sysctl/es_ES.ISO8859-1/share/xml/catalog projects/sysctl/es_ES.ISO8859-1/share/xml/freebsd.dsl projects/sysctl/es_ES.ISO8859-1/share/xsl/ projects/sysctl/fr_FR.ISO8859-1/share/xml/catalog projects/sysctl/fr_FR.ISO8859-1/share/xml/freebsd.dsl projects/sysctl/fr_FR.ISO8859-1/share/xsl/ projects/sysctl/hu_HU.ISO8859-2/share/xml/catalog projects/sysctl/hu_HU.ISO8859-2/share/xml/freebsd.dsl projects/sysctl/hu_HU.ISO8859-2/share/xsl/ projects/sysctl/it_IT.ISO8859-15/share/xml/catalog projects/sysctl/it_IT.ISO8859-15/share/xml/freebsd.dsl projects/sysctl/it_IT.ISO8859-15/share/xsl/ projects/sysctl/ja_JP.eucJP/share/xml/catalog projects/sysctl/ja_JP.eucJP/share/xml/freebsd.dsl projects/sysctl/ja_JP.eucJP/share/xsl/ projects/sysctl/mn_MN.UTF-8/share/mk/ projects/sysctl/mn_MN.UTF-8/share/xml/catalog projects/sysctl/mn_MN.UTF-8/share/xml/freebsd.dsl projects/sysctl/mn_MN.UTF-8/share/xsl/ projects/sysctl/nl_NL.ISO8859-1/share/xml/catalog projects/sysctl/nl_NL.ISO8859-1/share/xml/freebsd.dsl projects/sysctl/nl_NL.ISO8859-1/share/xsl/ projects/sysctl/pl_PL.ISO8859-2/share/mk/ projects/sysctl/pl_PL.ISO8859-2/share/xml/catalog projects/sysctl/pl_PL.ISO8859-2/share/xml/freebsd.dsl projects/sysctl/pl_PL.ISO8859-2/share/xsl/ projects/sysctl/pt_BR.ISO8859-1/share/xml/catalog projects/sysctl/pt_BR.ISO8859-1/share/xml/freebsd.dsl projects/sysctl/pt_BR.ISO8859-1/share/xsl/ projects/sysctl/ru_RU.KOI8-R/share/mk/ projects/sysctl/ru_RU.KOI8-R/share/xml/catalog projects/sysctl/ru_RU.KOI8-R/share/xml/freebsd.dsl projects/sysctl/ru_RU.KOI8-R/share/xsl/ projects/sysctl/share/web2c/ projects/sysctl/share/xml/catalog projects/sysctl/share/xml/default.dsl projects/sysctl/share/xml/freebsd-common.dsl projects/sysctl/share/xml/freebsd-print.dsl projects/sysctl/share/xml/freebsd.dsl projects/sysctl/share/xml/freebsd45.dtd projects/sysctl/share/xml/l10n.ent projects/sysctl/share/xml/spellcheck.dsl projects/sysctl/share/xsl/ projects/sysctl/sr_YU.ISO8859-2/share/mk/ projects/sysctl/sr_YU.ISO8859-2/share/xml/catalog projects/sysctl/sr_YU.ISO8859-2/share/xml/freebsd.dsl projects/sysctl/sr_YU.ISO8859-2/share/xsl/ projects/sysctl/tr_TR.ISO8859-9/share/xsl/ projects/sysctl/zh_TW.Big5/share/mk/ projects/sysctl/zh_TW.Big5/share/xml/catalog projects/sysctl/zh_TW.Big5/share/xml/freebsd.dsl projects/sysctl/zh_TW.Big5/share/xsl/ Modified: projects/sysctl/Makefile (contents, props changed) projects/sysctl/da_DK.ISO8859-1/articles/ipsec-must/article.xml projects/sysctl/da_DK.ISO8859-1/articles/pxe/article.xml projects/sysctl/da_DK.ISO8859-1/share/xml/catalog.xml projects/sysctl/da_DK.ISO8859-1/share/xml/disclaimer.xml projects/sysctl/da_DK.ISO8859-1/share/xml/entities.ent projects/sysctl/da_DK.ISO8859-1/share/xml/mailing-lists.ent projects/sysctl/da_DK.ISO8859-1/share/xml/newsgroups.ent projects/sysctl/da_DK.ISO8859-1/share/xml/teams.ent projects/sysctl/da_DK.ISO8859-1/share/xml/translators.ent projects/sysctl/de_DE.ISO8859-1/articles/Makefile.inc projects/sysctl/de_DE.ISO8859-1/articles/contributing-ports/article.xml projects/sysctl/de_DE.ISO8859-1/articles/contributing/article.xml projects/sysctl/de_DE.ISO8859-1/articles/explaining-bsd/article.xml projects/sysctl/de_DE.ISO8859-1/articles/freebsd-update-server/article.xml projects/sysctl/de_DE.ISO8859-1/articles/laptop/article.xml projects/sysctl/de_DE.ISO8859-1/articles/linux-comparison/article.xml projects/sysctl/de_DE.ISO8859-1/articles/nanobsd/article.xml projects/sysctl/de_DE.ISO8859-1/articles/new-users/article.xml projects/sysctl/de_DE.ISO8859-1/articles/port-mentor-guidelines/article.xml projects/sysctl/de_DE.ISO8859-1/articles/solid-state/article.xml projects/sysctl/de_DE.ISO8859-1/books/Makefile.inc projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/Makefile projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/book.xml projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/chapters.ent projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/introduction/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/ipv6/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/l10n/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/policies/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/secure/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/sockets/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/testing/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/tools/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/developers-handbook/x86/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/faq/book.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/book.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/doc-build/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/examples/appendix.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/overview/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/psgml-mode/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/see-also/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/sgml-markup/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/sgml-primer/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/structure/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/stylesheets/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/the-website/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/tools/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/translations/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/fdp-primer/writing-style/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/Makefile projects/sysctl/de_DE.ISO8859-1/books/handbook/advanced-networking/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/audit/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/basics/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/bibliography/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/book.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/boot/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/bsdinstall/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/chapters.ent projects/sysctl/de_DE.ISO8859-1/books/handbook/colophon.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/config/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/cutting-edge/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/desktop/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/disks/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/dtrace/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/eresources/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/filesystems/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/firewalls/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/geom/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/install/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/introduction/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/jails/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/kernelconfig/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/l10n/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/linuxemu/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/mac/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/mail/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/mirrors/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/multimedia/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/network-servers/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/pgpkeys/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/ports/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/preface/preface.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/printing/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/security/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/serialcomms/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/users/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/vinum/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/virtualization/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/handbook/x11/chapter.xml projects/sysctl/de_DE.ISO8859-1/books/porters-handbook/book.xml projects/sysctl/de_DE.ISO8859-1/htdocs/Makefile projects/sysctl/de_DE.ISO8859-1/htdocs/about.xml projects/sysctl/de_DE.ISO8859-1/htdocs/administration.xml projects/sysctl/de_DE.ISO8859-1/htdocs/applications.xml projects/sysctl/de_DE.ISO8859-1/htdocs/art.xml projects/sysctl/de_DE.ISO8859-1/htdocs/availability.xml projects/sysctl/de_DE.ISO8859-1/htdocs/community.xsl projects/sysctl/de_DE.ISO8859-1/htdocs/community/irc.xml projects/sysctl/de_DE.ISO8859-1/htdocs/community/mailinglists.xml projects/sysctl/de_DE.ISO8859-1/htdocs/community/newsgroups.xml projects/sysctl/de_DE.ISO8859-1/htdocs/community/webresources.xml projects/sysctl/de_DE.ISO8859-1/htdocs/developers/cvs.xml projects/sysctl/de_DE.ISO8859-1/htdocs/docproj/doc-set.xml projects/sysctl/de_DE.ISO8859-1/htdocs/docproj/docproj.xml projects/sysctl/de_DE.ISO8859-1/htdocs/docproj/sgml.xml projects/sysctl/de_DE.ISO8859-1/htdocs/docproj/submitting.xml projects/sysctl/de_DE.ISO8859-1/htdocs/docproj/who.xml projects/sysctl/de_DE.ISO8859-1/htdocs/docs.xml projects/sysctl/de_DE.ISO8859-1/htdocs/docs/books.xml projects/sysctl/de_DE.ISO8859-1/htdocs/docs/webresources.xml projects/sysctl/de_DE.ISO8859-1/htdocs/features.xml projects/sysctl/de_DE.ISO8859-1/htdocs/index.xsl projects/sysctl/de_DE.ISO8859-1/htdocs/internet.xml projects/sysctl/de_DE.ISO8859-1/htdocs/ipv6/index.xml projects/sysctl/de_DE.ISO8859-1/htdocs/java/index.xml projects/sysctl/de_DE.ISO8859-1/htdocs/logo.xml projects/sysctl/de_DE.ISO8859-1/htdocs/mailto.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2002/news.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2003/news.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2004/news.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2004/press.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2005/news.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2005/press.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2006/news.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2006/press.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2007/news.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2007/press.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2008/news.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2008/press.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2009/news.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/2009/press.xml projects/sysctl/de_DE.ISO8859-1/htdocs/news/news.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/alpha.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/amd64.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/arm.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/i386.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/ia64.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/ia64/index.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/ia64/machines.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/ia64/refs.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/ia64/todo.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/index.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/mips.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/pc98.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/ppc.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/sparc.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/sun4v.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/x86-64.xml projects/sysctl/de_DE.ISO8859-1/htdocs/platforms/xbox.xml projects/sysctl/de_DE.ISO8859-1/htdocs/ports/index.xml projects/sysctl/de_DE.ISO8859-1/htdocs/ports/installing.xml projects/sysctl/de_DE.ISO8859-1/htdocs/ports/references.xml projects/sysctl/de_DE.ISO8859-1/htdocs/ports/searching.xml projects/sysctl/de_DE.ISO8859-1/htdocs/ports/updating.xml projects/sysctl/de_DE.ISO8859-1/htdocs/projects/cvsweb.xml projects/sysctl/de_DE.ISO8859-1/htdocs/projects/newbies.xml projects/sysctl/de_DE.ISO8859-1/htdocs/projects/projects.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.11R/announce.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.11R/hardware.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.11R/installation.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.11R/relnotes.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.6.2R/announce.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.6.2R/hardware.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.6.2R/relnotes.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.7R/announce.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.7R/hardware.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.7R/installation.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.7R/relnotes.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.8R/announce.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.8R/hardware.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.8R/installation.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.8R/relnotes.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.9R/announce.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.9R/hardware.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.9R/installation.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/4.9R/relnotes.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.0R/announce.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.0R/hardware.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.0R/installation.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.0R/relnotes.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.1R/announce.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.1R/hardware.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.1R/installation.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.1R/relnotes.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.2R/hardware.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.2R/installation.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.2R/relnotes.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.3R/announce.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.3R/hardware.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.3R/installation.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/5.3R/relnotes.xml projects/sysctl/de_DE.ISO8859-1/htdocs/releases/index.xml projects/sysctl/de_DE.ISO8859-1/htdocs/relnotes.xml projects/sysctl/de_DE.ISO8859-1/htdocs/security/charter.xml projects/sysctl/de_DE.ISO8859-1/htdocs/security/security.xml projects/sysctl/de_DE.ISO8859-1/htdocs/send-pr.xml projects/sysctl/de_DE.ISO8859-1/htdocs/snapshots/index.xml projects/sysctl/de_DE.ISO8859-1/htdocs/support.xml projects/sysctl/de_DE.ISO8859-1/htdocs/support/bugreports.xml projects/sysctl/de_DE.ISO8859-1/htdocs/support/webresources.xml projects/sysctl/de_DE.ISO8859-1/htdocs/where.xml projects/sysctl/de_DE.ISO8859-1/share/xml/bibliography.xml projects/sysctl/de_DE.ISO8859-1/share/xml/catalog.xml projects/sysctl/de_DE.ISO8859-1/share/xml/entities.ent projects/sysctl/de_DE.ISO8859-1/share/xml/glossary.ent projects/sysctl/de_DE.ISO8859-1/share/xml/libcommon.xsl projects/sysctl/de_DE.ISO8859-1/share/xml/mailing-lists.ent projects/sysctl/de_DE.ISO8859-1/share/xml/news.xml projects/sysctl/de_DE.ISO8859-1/share/xml/newsgroups.ent projects/sysctl/de_DE.ISO8859-1/share/xml/press.xml projects/sysctl/de_DE.ISO8859-1/share/xml/teams.ent projects/sysctl/de_DE.ISO8859-1/share/xml/trademarks.ent projects/sysctl/de_DE.ISO8859-1/share/xml/translators.ent projects/sysctl/el_GR.ISO8859-7/articles/bsdl-gpl/article.xml projects/sysctl/el_GR.ISO8859-7/articles/compiz-fusion/article.xml projects/sysctl/el_GR.ISO8859-7/articles/contributing/article.xml projects/sysctl/el_GR.ISO8859-7/articles/cvs-freebsd/article.xml projects/sysctl/el_GR.ISO8859-7/articles/explaining-bsd/article.xml projects/sysctl/el_GR.ISO8859-7/articles/freebsd-questions/article.xml projects/sysctl/el_GR.ISO8859-7/articles/gjournal-desktop/article.xml projects/sysctl/el_GR.ISO8859-7/articles/greek-language-support/article.xml projects/sysctl/el_GR.ISO8859-7/articles/laptop/article.xml projects/sysctl/el_GR.ISO8859-7/articles/linux-users/article.xml projects/sysctl/el_GR.ISO8859-7/articles/mailing-list-faq/article.xml projects/sysctl/el_GR.ISO8859-7/articles/nanobsd/article.xml projects/sysctl/el_GR.ISO8859-7/articles/new-users/article.xml projects/sysctl/el_GR.ISO8859-7/articles/problem-reports/article.xml projects/sysctl/el_GR.ISO8859-7/articles/releng-packages/article.xml projects/sysctl/el_GR.ISO8859-7/articles/releng/article.xml projects/sysctl/el_GR.ISO8859-7/books/faq/book.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/Makefile projects/sysctl/el_GR.ISO8859-7/books/handbook/advanced-networking/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/audit/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/basics/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/bibliography/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/book.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/boot/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/bsdinstall/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/chapters.ent projects/sysctl/el_GR.ISO8859-7/books/handbook/colophon.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/config/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/cutting-edge/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/desktop/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/disks/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/dtrace/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/eresources/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/filesystems/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/firewalls/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/geom/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/install/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/introduction/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/jails/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/kernelconfig/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/l10n/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/linuxemu/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/mac/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/mail/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/mirrors/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/multimedia/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/network-servers/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/pgpkeys/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/ports/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/preface/preface.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/printing/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/security/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/serialcomms/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/users/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/vinum/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/virtualization/chapter.xml projects/sysctl/el_GR.ISO8859-7/books/handbook/x11/chapter.xml projects/sysctl/el_GR.ISO8859-7/share/xml/catalog.xml projects/sysctl/el_GR.ISO8859-7/share/xml/entities.ent projects/sysctl/el_GR.ISO8859-7/share/xml/glossary.ent projects/sysctl/el_GR.ISO8859-7/share/xml/libcommon.xsl projects/sysctl/el_GR.ISO8859-7/share/xml/mailing-lists.ent projects/sysctl/el_GR.ISO8859-7/share/xml/newsgroups.ent projects/sysctl/el_GR.ISO8859-7/share/xml/teams.ent projects/sysctl/el_GR.ISO8859-7/share/xml/trademarks.ent projects/sysctl/el_GR.ISO8859-7/share/xml/translators.ent projects/sysctl/en_US.ISO8859-1/articles/bsdl-gpl/article.xml projects/sysctl/en_US.ISO8859-1/articles/building-products/article.xml projects/sysctl/en_US.ISO8859-1/articles/casestudy-argentina.com/article.xml projects/sysctl/en_US.ISO8859-1/articles/committers-guide/article.xml projects/sysctl/en_US.ISO8859-1/articles/compiz-fusion/article.xml projects/sysctl/en_US.ISO8859-1/articles/console-server/article.xml projects/sysctl/en_US.ISO8859-1/articles/contributing-ports/article.xml projects/sysctl/en_US.ISO8859-1/articles/contributing/article.xml projects/sysctl/en_US.ISO8859-1/articles/contributors/article.xml projects/sysctl/en_US.ISO8859-1/articles/contributors/contrib.386bsd.xml projects/sysctl/en_US.ISO8859-1/articles/contributors/contrib.additional.xml projects/sysctl/en_US.ISO8859-1/articles/contributors/contrib.committers.xml projects/sysctl/en_US.ISO8859-1/articles/contributors/contrib.corealumni.xml projects/sysctl/en_US.ISO8859-1/articles/contributors/contrib.develalumni.xml projects/sysctl/en_US.ISO8859-1/articles/contributors/contrib.develinmemoriam.xml projects/sysctl/en_US.ISO8859-1/articles/contributors/contrib.portmgralumni.xml projects/sysctl/en_US.ISO8859-1/articles/cups/article.xml projects/sysctl/en_US.ISO8859-1/articles/custom-gcc/article.xml projects/sysctl/en_US.ISO8859-1/articles/cvs-freebsd/article.xml projects/sysctl/en_US.ISO8859-1/articles/explaining-bsd/article.xml projects/sysctl/en_US.ISO8859-1/articles/fbsd-from-scratch/article.xml projects/sysctl/en_US.ISO8859-1/articles/filtering-bridges/article.xml projects/sysctl/en_US.ISO8859-1/articles/fonts/article.xml projects/sysctl/en_US.ISO8859-1/articles/freebsd-questions/article.xml projects/sysctl/en_US.ISO8859-1/articles/freebsd-update-server/article.xml projects/sysctl/en_US.ISO8859-1/articles/geom-class/article.xml projects/sysctl/en_US.ISO8859-1/articles/gjournal-desktop/article.xml projects/sysctl/en_US.ISO8859-1/articles/hubs/article.xml projects/sysctl/en_US.ISO8859-1/articles/ipsec-must/article.xml projects/sysctl/en_US.ISO8859-1/articles/laptop/article.xml projects/sysctl/en_US.ISO8859-1/articles/ldap-auth/article.xml projects/sysctl/en_US.ISO8859-1/articles/linux-comparison/article.xml projects/sysctl/en_US.ISO8859-1/articles/linux-emulation/article.xml projects/sysctl/en_US.ISO8859-1/articles/linux-users/article.xml projects/sysctl/en_US.ISO8859-1/articles/mailing-list-faq/article.xml projects/sysctl/en_US.ISO8859-1/articles/mh/article.xml projects/sysctl/en_US.ISO8859-1/articles/nanobsd/article.xml projects/sysctl/en_US.ISO8859-1/articles/new-users/article.xml projects/sysctl/en_US.ISO8859-1/articles/p4-primer/article.xml projects/sysctl/en_US.ISO8859-1/articles/pam/article.xml projects/sysctl/en_US.ISO8859-1/articles/port-mentor-guidelines/article.xml projects/sysctl/en_US.ISO8859-1/articles/portbuild/article.xml projects/sysctl/en_US.ISO8859-1/articles/pr-guidelines/article.xml projects/sysctl/en_US.ISO8859-1/articles/problem-reports/article.xml projects/sysctl/en_US.ISO8859-1/articles/rc-scripting/article.xml projects/sysctl/en_US.ISO8859-1/articles/relaydelay/article.xml projects/sysctl/en_US.ISO8859-1/articles/releng-packages/article.xml projects/sysctl/en_US.ISO8859-1/articles/releng/article.xml projects/sysctl/en_US.ISO8859-1/articles/remote-install/article.xml projects/sysctl/en_US.ISO8859-1/articles/serial-uart/article.xml projects/sysctl/en_US.ISO8859-1/articles/solid-state/article.xml projects/sysctl/en_US.ISO8859-1/articles/vm-design/article.xml projects/sysctl/en_US.ISO8859-1/articles/wp-toolbox/article.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/Makefile projects/sysctl/en_US.ISO8859-1/books/arch-handbook/book.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/chapters.ent projects/sysctl/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/jail/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/kobj/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/locking/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/mac.ent projects/sysctl/en_US.ISO8859-1/books/arch-handbook/mac/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/newbus/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/pci/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/smp/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/sound/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/sysinit/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml projects/sysctl/en_US.ISO8859-1/books/arch-handbook/vm/chapter.xml projects/sysctl/en_US.ISO8859-1/books/bibliography/book.xml projects/sysctl/en_US.ISO8859-1/books/design-44bsd/book.xml projects/sysctl/en_US.ISO8859-1/books/dev-model/book.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/Makefile projects/sysctl/en_US.ISO8859-1/books/developers-handbook/book.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/chapters.ent projects/sysctl/en_US.ISO8859-1/books/developers-handbook/introduction/chapter.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/kernelbuild/chapter.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/l10n/chapter.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/policies/chapter.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/secure/chapter.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/sockets/chapter.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/testing/chapter.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/tools/chapter.xml projects/sysctl/en_US.ISO8859-1/books/developers-handbook/x86/chapter.xml projects/sysctl/en_US.ISO8859-1/books/faq/book.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/book.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/docbook-markup/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/editor-config/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/examples/appendix.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/overview/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/see-also/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/structure/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/stylesheets/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/the-website/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/tools/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/translations/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/working-copy/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/xhtml-markup/chapter.xml projects/sysctl/en_US.ISO8859-1/books/fdp-primer/xml-primer/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/Makefile projects/sysctl/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/audit/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/basics/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/bibliography/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/book.xml projects/sysctl/en_US.ISO8859-1/books/handbook/boot/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/chapters.ent projects/sysctl/en_US.ISO8859-1/books/handbook/colophon.xml projects/sysctl/en_US.ISO8859-1/books/handbook/config/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/desktop/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/disks/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/dtrace/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/eresources/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/filesystems/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/firewalls/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/geom/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/install/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/introduction/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/jails/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/kernelconfig/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/l10n/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/linuxemu/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/mac/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/mail/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/mirrors/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/multimedia/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/network-servers/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/pgpkeys/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/ports/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/preface/preface.xml projects/sysctl/en_US.ISO8859-1/books/handbook/printing/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/security/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/serialcomms/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/users/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/virtualization/chapter.xml projects/sysctl/en_US.ISO8859-1/books/handbook/x11/chapter.xml projects/sysctl/en_US.ISO8859-1/books/pmake/answers/chapter.xml projects/sysctl/en_US.ISO8859-1/books/pmake/basics/chapter.xml projects/sysctl/en_US.ISO8859-1/books/pmake/book.xml projects/sysctl/en_US.ISO8859-1/books/pmake/glossary/glossary.xml projects/sysctl/en_US.ISO8859-1/books/pmake/gods/chapter.xml projects/sysctl/en_US.ISO8859-1/books/pmake/intro/chapter.xml projects/sysctl/en_US.ISO8859-1/books/pmake/legalnotice.xml projects/sysctl/en_US.ISO8859-1/books/pmake/shortcuts/chapter.xml projects/sysctl/en_US.ISO8859-1/books/porters-handbook/book.xml projects/sysctl/en_US.ISO8859-1/books/porters-handbook/uses.xml projects/sysctl/en_US.ISO8859-1/books/porters-handbook/versions.xml projects/sysctl/en_US.ISO8859-1/htdocs/4xx.xml projects/sysctl/en_US.ISO8859-1/htdocs/Makefile projects/sysctl/en_US.ISO8859-1/htdocs/about.xml projects/sysctl/en_US.ISO8859-1/htdocs/administration.xml projects/sysctl/en_US.ISO8859-1/htdocs/advocacy/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/advocacy/myths.xml projects/sysctl/en_US.ISO8859-1/htdocs/advocacy/whyusefreebsd.xml projects/sysctl/en_US.ISO8859-1/htdocs/applications.xml projects/sysctl/en_US.ISO8859-1/htdocs/art.xml projects/sysctl/en_US.ISO8859-1/htdocs/cgi/query-pr-summary.cgi projects/sysctl/en_US.ISO8859-1/htdocs/commercial/commercial.xml projects/sysctl/en_US.ISO8859-1/htdocs/community.xsl projects/sysctl/en_US.ISO8859-1/htdocs/community/Makefile projects/sysctl/en_US.ISO8859-1/htdocs/community/irc.xml projects/sysctl/en_US.ISO8859-1/htdocs/community/mailinglists.xml projects/sysctl/en_US.ISO8859-1/htdocs/community/newsgroups.xml projects/sysctl/en_US.ISO8859-1/htdocs/community/webresources.xml projects/sysctl/en_US.ISO8859-1/htdocs/copyright/copyright.xml projects/sysctl/en_US.ISO8859-1/htdocs/copyright/daemon.xml projects/sysctl/en_US.ISO8859-1/htdocs/copyright/freebsd-doc-license.xml projects/sysctl/en_US.ISO8859-1/htdocs/copyright/freebsd-license.xml projects/sysctl/en_US.ISO8859-1/htdocs/copyright/license.xml projects/sysctl/en_US.ISO8859-1/htdocs/copyright/trademarks.xml projects/sysctl/en_US.ISO8859-1/htdocs/developers/cvs.xml projects/sysctl/en_US.ISO8859-1/htdocs/docproj/current.xml projects/sysctl/en_US.ISO8859-1/htdocs/docproj/doc-set.xml projects/sysctl/en_US.ISO8859-1/htdocs/docproj/docproj.xml projects/sysctl/en_US.ISO8859-1/htdocs/docproj/handbook.xml projects/sysctl/en_US.ISO8859-1/htdocs/docproj/handbook3.xml projects/sysctl/en_US.ISO8859-1/htdocs/docproj/submitting.xml projects/sysctl/en_US.ISO8859-1/htdocs/docproj/translations.xml projects/sysctl/en_US.ISO8859-1/htdocs/docproj/who.xml projects/sysctl/en_US.ISO8859-1/htdocs/docs.xml projects/sysctl/en_US.ISO8859-1/htdocs/docs/books.xml projects/sysctl/en_US.ISO8859-1/htdocs/docs/webresources.xml projects/sysctl/en_US.ISO8859-1/htdocs/donations/donors.xml projects/sysctl/en_US.ISO8859-1/htdocs/donations/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/donations/wantlist.xml projects/sysctl/en_US.ISO8859-1/htdocs/events/2002/bsdcon-devsummit.xml projects/sysctl/en_US.ISO8859-1/htdocs/events/2002/usenix-devsummit.xml projects/sysctl/en_US.ISO8859-1/htdocs/events/2003/bsdcon-devsummit.xml projects/sysctl/en_US.ISO8859-1/htdocs/events/rss.xsl projects/sysctl/en_US.ISO8859-1/htdocs/features.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/contact.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/bugging.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/develfaq.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/example-Makefile.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq2.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq210.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq212.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq214.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq216.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq218.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq220.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq222.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq224.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq226.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq228.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq230.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq232.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/faq28.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/gnome1_porting.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/gnome2_porting.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/gnome_porting.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/halfaq.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/porting.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/docs/volunteer.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/index.xsl projects/sysctl/en_US.ISO8859-1/htdocs/gnome/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/gnome/newsflash.xsl projects/sysctl/en_US.ISO8859-1/htdocs/gnome/rss.xsl projects/sysctl/en_US.ISO8859-1/htdocs/gnome/rss2.xsl projects/sysctl/en_US.ISO8859-1/htdocs/gnome/screenshots.xml projects/sysctl/en_US.ISO8859-1/htdocs/index.xsl projects/sysctl/en_US.ISO8859-1/htdocs/internal/about.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/bylaws.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/clusteradm.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/core-vote.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/data.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/developer.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/doceng.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/expire-bits.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/fortunes.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/hats.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/homepage.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/i18n.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/internal.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/machines.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/mirror.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/new-account.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/policies.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/proposing-committers.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/releng.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/resources.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/ssh-keys.asc (contents, props changed) projects/sysctl/en_US.ISO8859-1/htdocs/internal/statistic.xml projects/sysctl/en_US.ISO8859-1/htdocs/internal/working-with-hats.xml projects/sysctl/en_US.ISO8859-1/htdocs/internet.xml projects/sysctl/en_US.ISO8859-1/htdocs/ipv6/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/ipv6/ipv6only.xml projects/sysctl/en_US.ISO8859-1/htdocs/ipv6/w6d-www-stats.xml projects/sysctl/en_US.ISO8859-1/htdocs/ipv6/w6d.xml projects/sysctl/en_US.ISO8859-1/htdocs/ipv6/w6l.xml projects/sysctl/en_US.ISO8859-1/htdocs/java/dists/16.xml projects/sysctl/en_US.ISO8859-1/htdocs/java/dists/17.xml projects/sysctl/en_US.ISO8859-1/htdocs/java/dists/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/java/howhelp.xml projects/sysctl/en_US.ISO8859-1/htdocs/java/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/java/install.xml projects/sysctl/en_US.ISO8859-1/htdocs/java/java-rss.xsl projects/sysctl/en_US.ISO8859-1/htdocs/java/links.xml projects/sysctl/en_US.ISO8859-1/htdocs/java/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/java/newsflash.xsl projects/sysctl/en_US.ISO8859-1/htdocs/logo.xml projects/sysctl/en_US.ISO8859-1/htdocs/mailto.xml projects/sysctl/en_US.ISO8859-1/htdocs/marketing/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/multimedia/include.xsl projects/sysctl/en_US.ISO8859-1/htdocs/multimedia/multimedia-input.xml projects/sysctl/en_US.ISO8859-1/htdocs/multimedia/multimedia-rss.xsl projects/sysctl/en_US.ISO8859-1/htdocs/multimedia/multimedia.xsl projects/sysctl/en_US.ISO8859-1/htdocs/multimedia/sources.xsl projects/sysctl/en_US.ISO8859-1/htdocs/multimedia/tags.xsl projects/sysctl/en_US.ISO8859-1/htdocs/news/1993/freebsd-coined.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/1993/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/1996/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/1997/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/1998/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/1999/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2000/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2001/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2002/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2003/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2004/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2005/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2006/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2006/press.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2007/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2007/press.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2008/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2008/press.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2009/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2009/press.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/2012-compromise.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/news.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/press-rel-1.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/press-rel-2.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/press-rel-3.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/press-rel-4.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/press-rel-5.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/press-rel-6.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/press-rel-7.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/press-rel-8.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/press-rel-9.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/pressreleases.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/sou1999.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/Makefile projects/sysctl/en_US.ISO8859-1/htdocs/news/status/README projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2001-06.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2001-07.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2001-08.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2001-09.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2001-11.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2001-12-2002-01.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2002-02-2002-04.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2002-05-2002-06.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2002-07-2002-08.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2002-09-2002-10.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2002-11-2002-12.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2003-01-2003-02.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2003-03-2003-09.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2003-10-2003-12.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2004-01-2004-02.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2004-03-2004-04.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2004-05-2004-06.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2004-07-2004-12.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2005-01-2005-03.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2005-03-2005-06.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2005-07-2005-10.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2005-10-2005-12.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2006-01-2006-03.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2006-04-2006-06.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2006-06-2006-10.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2006-10-2006-12.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2007-01-2007-03.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2007-04-2007-06.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2007-07-2007-10.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2007-10-2007-12.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2008-01-2008-03.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2008-04-2008-06.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2008-07-2008-09.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2008-10-2008-12.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2009-01-2009-03.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2009-04-2009-09.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2009-10-2009-12.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2010-01-2010-03.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2010-04-2010-06.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2010-07-2010-09.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2010-10-2010-12.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2011-01-2011-03.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2011-04-2011-06.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2011-07-2011-09.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2011-10-2011-12.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2012-01-2012-03.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2012-04-2012-06.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2012-07-2012-09.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2012-10-2012-12.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2013-01-2013-03.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2013-04-2013-06.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2013-05-devsummit.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-2013-07-2013-09.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report-sample.xml projects/sysctl/en_US.ISO8859-1/htdocs/news/status/report.xsl projects/sysctl/en_US.ISO8859-1/htdocs/news/status/status.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/alpha.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/amd64.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/arm.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/i386.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/ia64.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/ia64/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/ia64/machines.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/ia64/refs.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/ia64/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/mips.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/pc98.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/ppc.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/sparc.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/sun4v.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/x86-64.xml projects/sysctl/en_US.ISO8859-1/htdocs/platforms/xbox.xml projects/sysctl/en_US.ISO8859-1/htdocs/portmgr/charter.xml projects/sysctl/en_US.ISO8859-1/htdocs/portmgr/implementation.xml projects/sysctl/en_US.ISO8859-1/htdocs/portmgr/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/portmgr/policies.xml projects/sysctl/en_US.ISO8859-1/htdocs/portmgr/policies_committing.xml projects/sysctl/en_US.ISO8859-1/htdocs/portmgr/policies_contributors.xml projects/sysctl/en_US.ISO8859-1/htdocs/portmgr/policies_eol.xml projects/sysctl/en_US.ISO8859-1/htdocs/portmgr/qa.xml projects/sysctl/en_US.ISO8859-1/htdocs/ports/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/ports/installing.xml projects/sysctl/en_US.ISO8859-1/htdocs/ports/portindex projects/sysctl/en_US.ISO8859-1/htdocs/ports/references.xml projects/sysctl/en_US.ISO8859-1/htdocs/ports/searching.xml projects/sysctl/en_US.ISO8859-1/htdocs/ports/updating.xml projects/sysctl/en_US.ISO8859-1/htdocs/privacy.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/acpi/completed.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/acpi/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/busdma/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/cvsweb.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/ideas/ideas.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/mac/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/mips/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/netperf/cluster.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/netperf/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/newbies.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/projects.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/summerofcode-2005.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/summerofcode-2006.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/summerofcode-2007.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/summerofcode-2008.xml projects/sysctl/en_US.ISO8859-1/htdocs/projects/summerofcode.xml projects/sysctl/en_US.ISO8859-1/htdocs/prstats/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/publish.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/10.0R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.0.5R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.0.5R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.0/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.0/credits.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.0/install.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.0/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.1.5R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.1.5R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.1.6R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.1.6R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.1.6R/security.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.1.7R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.1.7R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.1R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.1R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.1R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.2R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.2R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.5R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.5R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.5R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.6R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.6R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.6R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.7R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.7R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.7R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.8R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.8R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2.8R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2R/install-media.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/2.2R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.0R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.0R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.0R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.1R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.1R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.1R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.2R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.2R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.2R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.3R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.3R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.3R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.4R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.4R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.4R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.5R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.5R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/3.5R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.0R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.0R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.0R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.1.1R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.1.1R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.1.1R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.10R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.10R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.10R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.10R/qa.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.10R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.10R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.10R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.11R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.11R/errata_policy.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.11R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.11R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.11R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.11R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.11R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.1R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.1R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.1R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.2R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.2R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.2R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.3R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.3R/errata.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.3R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.4R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.4R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.4R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.5R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.5R/contents.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.5R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.5R/notes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.5R/qa.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.5R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.6.2R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.6.2R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.6.2R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.6R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.6R/contents.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.6R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.6R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.6R/qa.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.6R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.6R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.7R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.7R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.7R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.7R/qa.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.7R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.7R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.8R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.8R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.8R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.8R/qa.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.8R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.8R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.9R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.9R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.9R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.9R/qa.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.9R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.9R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/4.9R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/DP1/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/DP1/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/DP1/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/DP1/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/DP2/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/DP2/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/DP2/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/DP2/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.0R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.1R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.1R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.1R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.1R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.1R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.1R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.2.1R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.2.1R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.2.1R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.2.1R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.2R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.2R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.2R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.2R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.2R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.2R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.3R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.3R/errata_policy.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.3R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.3R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.3R/policy.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.3R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.3R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.3R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.4R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.4R/errata_policy.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.4R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.4R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.4R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.4R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.4R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.5R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.5R/approvals.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.5R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.5R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.5R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.5R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/5.5R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.0R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.0R/approvals.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.0R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.0R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.0R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.0R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.0R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.1R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.1R/approvals.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.1R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.1R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.1R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.1R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.1R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.2R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.2R/approvals.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.2R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.2R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.2R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.2R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.2R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.3R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.3R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.3R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.3R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.3R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.4R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.4R/hardware.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.4R/installation.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.4R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/6.4R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.0R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.0R/approvals.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.0R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.0R/todo.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.1R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.1R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.2R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.2R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.2R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.2R/status.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.3R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.3R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.3R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.4R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/7.4R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.0R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.0R/pressrelease.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.0R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.0R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.1R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.1R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.1R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.2R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.2R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.2R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.3R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.3R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.3R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.4R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.4R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/8.4R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/9.0R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/9.0R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/9.0R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/9.1R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/9.1R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/9.1R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/9.2R/announce.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/9.2R/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/9.2R/schedule.xml projects/sysctl/en_US.ISO8859-1/htdocs/releases/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/releng/charter.xml projects/sysctl/en_US.ISO8859-1/htdocs/releng/dst_info.xml projects/sysctl/en_US.ISO8859-1/htdocs/releng/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/relnotes.xml projects/sysctl/en_US.ISO8859-1/htdocs/relnotes/Makefile projects/sysctl/en_US.ISO8859-1/htdocs/robots.txt projects/sysctl/en_US.ISO8859-1/htdocs/search/index-site.xsl projects/sysctl/en_US.ISO8859-1/htdocs/search/opensearch/opensearch.xml projects/sysctl/en_US.ISO8859-1/htdocs/search/search-mid.xml projects/sysctl/en_US.ISO8859-1/htdocs/search/search.xml projects/sysctl/en_US.ISO8859-1/htdocs/search/searchhints.xml projects/sysctl/en_US.ISO8859-1/htdocs/search/sitemap.xml projects/sysctl/en_US.ISO8859-1/htdocs/security/advisories.xml projects/sysctl/en_US.ISO8859-1/htdocs/security/charter.xml projects/sysctl/en_US.ISO8859-1/htdocs/security/errata-rss.xsl projects/sysctl/en_US.ISO8859-1/htdocs/security/errata.rss projects/sysctl/en_US.ISO8859-1/htdocs/security/mkindex.xsl projects/sysctl/en_US.ISO8859-1/htdocs/security/notices.xml projects/sysctl/en_US.ISO8859-1/htdocs/security/reporting.xml projects/sysctl/en_US.ISO8859-1/htdocs/security/security-rdf.xsl projects/sysctl/en_US.ISO8859-1/htdocs/security/security-rss.xsl projects/sysctl/en_US.ISO8859-1/htdocs/security/security.xml projects/sysctl/en_US.ISO8859-1/htdocs/security/so_public_key.asc (contents, props changed) projects/sysctl/en_US.ISO8859-1/htdocs/security/unsupported.xml projects/sysctl/en_US.ISO8859-1/htdocs/send-pr.xml projects/sysctl/en_US.ISO8859-1/htdocs/snapshots/index.xml projects/sysctl/en_US.ISO8859-1/htdocs/support.xml projects/sysctl/en_US.ISO8859-1/htdocs/support/bugreports.xml projects/sysctl/en_US.ISO8859-1/htdocs/support/webresources.xml projects/sysctl/en_US.ISO8859-1/htdocs/where.xml projects/sysctl/en_US.ISO8859-1/share/xml/catalog.xml projects/sysctl/en_US.ISO8859-1/share/xml/entities.ent projects/sysctl/en_US.ISO8859-1/share/xml/glossary.ent projects/sysctl/en_US.ISO8859-1/share/xml/libcommon.xsl projects/sysctl/en_US.ISO8859-1/share/xml/mailing-lists.ent projects/sysctl/en_US.ISO8859-1/share/xml/newsgroups.ent projects/sysctl/en_US.ISO8859-1/share/xml/teams.ent projects/sysctl/es_ES.ISO8859-1/articles/casestudy-argentina.com/article.xml projects/sysctl/es_ES.ISO8859-1/articles/contributing/article.xml projects/sysctl/es_ES.ISO8859-1/articles/cvs-freebsd/article.xml projects/sysctl/es_ES.ISO8859-1/articles/explaining-bsd/article.xml projects/sysctl/es_ES.ISO8859-1/articles/fbsd-from-scratch/article.xml projects/sysctl/es_ES.ISO8859-1/articles/fdp-es/article.xml projects/sysctl/es_ES.ISO8859-1/articles/laptop/article.xml projects/sysctl/es_ES.ISO8859-1/articles/linux-comparison/article.xml projects/sysctl/es_ES.ISO8859-1/articles/linux-users/article.xml projects/sysctl/es_ES.ISO8859-1/articles/mailing-list-faq/article.xml projects/sysctl/es_ES.ISO8859-1/articles/nanobsd/article.xml projects/sysctl/es_ES.ISO8859-1/articles/p4-primer/article.xml projects/sysctl/es_ES.ISO8859-1/articles/problem-reports/article.xml projects/sysctl/es_ES.ISO8859-1/articles/releng/article.xml projects/sysctl/es_ES.ISO8859-1/books/faq/book.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/Makefile projects/sysctl/es_ES.ISO8859-1/books/handbook/advanced-networking/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/audit/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/basics/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/bibliography/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/book.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/boot/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/chapters.ent projects/sysctl/es_ES.ISO8859-1/books/handbook/colophon.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/config/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/cutting-edge/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/desktop/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/disks/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/eresources/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/firewalls/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/geom/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/install/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/introduction/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/jails/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/kernelconfig/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/l10n/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/linuxemu/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/mac/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/mail/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/mirrors/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/multimedia/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/network-servers/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/pgpkeys/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/ports/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/preface/preface.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/printing/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/security/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/serialcomms/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/users/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/vinum/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/virtualization/chapter.xml projects/sysctl/es_ES.ISO8859-1/books/handbook/x11/chapter.xml projects/sysctl/es_ES.ISO8859-1/htdocs/about.xml projects/sysctl/es_ES.ISO8859-1/htdocs/applications.xml projects/sysctl/es_ES.ISO8859-1/htdocs/availability.xml projects/sysctl/es_ES.ISO8859-1/htdocs/community.xml projects/sysctl/es_ES.ISO8859-1/htdocs/copyright/copyright.xml projects/sysctl/es_ES.ISO8859-1/htdocs/copyright/daemon.xml projects/sysctl/es_ES.ISO8859-1/htdocs/copyright/freebsd-license.xml projects/sysctl/es_ES.ISO8859-1/htdocs/docproj/current.xml projects/sysctl/es_ES.ISO8859-1/htdocs/docproj/doc-set.xml projects/sysctl/es_ES.ISO8859-1/htdocs/docproj/docproj.xml projects/sysctl/es_ES.ISO8859-1/htdocs/docproj/sgml.xml projects/sysctl/es_ES.ISO8859-1/htdocs/docproj/submitting.xml projects/sysctl/es_ES.ISO8859-1/htdocs/docproj/translations.xml projects/sysctl/es_ES.ISO8859-1/htdocs/docproj/who.xml projects/sysctl/es_ES.ISO8859-1/htdocs/docs.xml projects/sysctl/es_ES.ISO8859-1/htdocs/features.xml projects/sysctl/es_ES.ISO8859-1/htdocs/index.xsl projects/sysctl/es_ES.ISO8859-1/htdocs/internal/about.xml projects/sysctl/es_ES.ISO8859-1/htdocs/internal/developer.xml projects/sysctl/es_ES.ISO8859-1/htdocs/internal/homepage.xml projects/sysctl/es_ES.ISO8859-1/htdocs/internal/internal.xml projects/sysctl/es_ES.ISO8859-1/htdocs/internal/machines.xml projects/sysctl/es_ES.ISO8859-1/htdocs/internal/mirror.xml projects/sysctl/es_ES.ISO8859-1/htdocs/internal/photos.xml projects/sysctl/es_ES.ISO8859-1/htdocs/internal/statistic.xml projects/sysctl/es_ES.ISO8859-1/htdocs/internet.xml projects/sysctl/es_ES.ISO8859-1/htdocs/mailto.xml projects/sysctl/es_ES.ISO8859-1/htdocs/news/news.xml projects/sysctl/es_ES.ISO8859-1/htdocs/news/newsflash.xml projects/sysctl/es_ES.ISO8859-1/htdocs/news/press-rel-1.xml projects/sysctl/es_ES.ISO8859-1/htdocs/news/press-rel-2.xml projects/sysctl/es_ES.ISO8859-1/htdocs/news/press-rel-3.xml projects/sysctl/es_ES.ISO8859-1/htdocs/news/press.xml projects/sysctl/es_ES.ISO8859-1/htdocs/news/pressreleases.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/alpha.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/amd64.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/arm.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/i386.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/ia64/index.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/ia64/machines.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/ia64/refs.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/ia64/todo.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/index.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/mips.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/pc98.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/sparc.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/sun4v.xml projects/sysctl/es_ES.ISO8859-1/htdocs/platforms/xbox.xml projects/sysctl/es_ES.ISO8859-1/htdocs/projects/newbies.xml projects/sysctl/es_ES.ISO8859-1/htdocs/projects/projects.xml projects/sysctl/es_ES.ISO8859-1/htdocs/publish.xml projects/sysctl/es_ES.ISO8859-1/htdocs/releases/index.xml projects/sysctl/es_ES.ISO8859-1/htdocs/releases/snapshots.xml projects/sysctl/es_ES.ISO8859-1/htdocs/search/index-site.xsl projects/sysctl/es_ES.ISO8859-1/htdocs/search/search-mid.xml projects/sysctl/es_ES.ISO8859-1/htdocs/search/search.xml projects/sysctl/es_ES.ISO8859-1/htdocs/search/searchhints.xml projects/sysctl/es_ES.ISO8859-1/htdocs/search/sitemap.xml projects/sysctl/es_ES.ISO8859-1/htdocs/security/security.xml projects/sysctl/es_ES.ISO8859-1/htdocs/send-pr.xml projects/sysctl/es_ES.ISO8859-1/htdocs/support.xml projects/sysctl/es_ES.ISO8859-1/htdocs/where.xml projects/sysctl/es_ES.ISO8859-1/share/xml/catalog.xml projects/sysctl/es_ES.ISO8859-1/share/xml/entities.ent projects/sysctl/es_ES.ISO8859-1/share/xml/es-mailing-lists.ent projects/sysctl/es_ES.ISO8859-1/share/xml/glossary.ent projects/sysctl/es_ES.ISO8859-1/share/xml/libcommon.xsl projects/sysctl/es_ES.ISO8859-1/share/xml/mailing-lists.ent projects/sysctl/es_ES.ISO8859-1/share/xml/newsgroups.ent projects/sysctl/es_ES.ISO8859-1/share/xml/teams.ent projects/sysctl/es_ES.ISO8859-1/share/xml/trademarks.ent projects/sysctl/es_ES.ISO8859-1/share/xml/translators.ent projects/sysctl/fr_FR.ISO8859-1/articles/building-products/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/committers-guide/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/contributing-ports/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/contributing/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/contributors/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/explaining-bsd/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/filtering-bridges/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/fonts/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/ipsec-must/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/laptop/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/linux-users/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/mh/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/nanobsd/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/new-users/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/pam/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/pr-guidelines/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/problem-reports/article.xml projects/sysctl/fr_FR.ISO8859-1/articles/releng-packages/article.xml projects/sysctl/fr_FR.ISO8859-1/books/developers-handbook/book.xml projects/sysctl/fr_FR.ISO8859-1/books/developers-handbook/driverbasics/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/developers-handbook/locking/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/developers-handbook/pci/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/developers-handbook/scsi/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/developers-handbook/secure/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/developers-handbook/tools/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/developers-handbook/usb/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/faq/book.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/book.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/overview/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/psgml-mode/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/see-also/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/sgml-markup/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/sgml-primer/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/stylesheets/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/the-faq/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/the-handbook/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/the-website/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/tools/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/translations/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/fdp-primer/writing-style/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/Makefile projects/sysctl/fr_FR.ISO8859-1/books/handbook/advanced-networking/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/audit/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/basics/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/bibliography/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/book.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/boot/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/chapters.ent projects/sysctl/fr_FR.ISO8859-1/books/handbook/colophon.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/config/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/cutting-edge/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/desktop/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/disks/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/dtrace/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/eresources/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/firewalls/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/geom/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/install/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/introduction/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/jails/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/kernelconfig/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/l10n/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/linuxemu/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/mac/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/mail/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/mirrors/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/multimedia/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/network-servers/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/pgpkeys/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/ports/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/preface/preface.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/printing/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/security/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/serialcomms/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/users/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/vinum/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/virtualization/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/handbook/x11/chapter.xml projects/sysctl/fr_FR.ISO8859-1/books/porters-handbook/book.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/about.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/advocacy/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/advocacy/myths.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/applications.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/art.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/auditors.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/availability.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/commercial/commercial.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/community.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/community/irc.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/community/mailinglists.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/community/newsgroups.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/community/webresources.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/copyright/copyright.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/copyright/daemon.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/copyright/freebsd-doc-license.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/copyright/freebsd-license.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/copyright/license.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/copyright/trademarks.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/developers/cvs.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docproj/current.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docproj/doc-set.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docproj/docproj.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docproj/handbook.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docproj/handbook3.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docproj/sgml.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docproj/submitting.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docproj/translations.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docproj/who.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docs.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docs/books.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docs/man.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/docs/webresources.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/donations/donors.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/donations/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/donations/wantlist.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/features.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/contact.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/docs/22knownissues.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/docs/bugging.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/docs/faq.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/docs/faq2.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/docs/gnome2_porting.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/docs/gnome_porting.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/docs/porting.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/docs/volunteer.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/index.xsl projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/newsflash.xsl projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/rss.xsl projects/sysctl/fr_FR.ISO8859-1/htdocs/gnome/screenshots.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/index.xsl projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/about.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/bylaws.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/core-vote.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/developer.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/expire-bits.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/homepage.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/internal.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/machines.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/mirror.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/new-account.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/photos.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/releng.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internal/statistic.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/internet.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/advocacy.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/dists/15.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/dists/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/docs/faq.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/docs/howtoports.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/docs/newbies.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/docs/performance.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/docs/tutorials.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/howhelp.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/install.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/links/api.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/links/development.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/links/documentation.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/links/freebsd.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/links/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/links/resources.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/links/servlets.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/links/tools.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/links/tutorials.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/links/vendor.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/newsflash.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/java/press.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/logo.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/mailto.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/1996/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/1997/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/1998/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/1999/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/2000/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/news.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/press-rel-1.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/press-rel-2.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/press-rel-3.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/press-rel-4.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/press-rel-5.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/press-rel-6.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/press-rel-7.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/press-rel-8.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/press-rel-9.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/pressreleases.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/sou1999.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/news/status/report.xsl projects/sysctl/fr_FR.ISO8859-1/htdocs/news/status/status.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/alpha.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/amd64.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/arm.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/i386.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/ia64.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/ia64/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/ia64/machines.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/ia64/refs.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/ia64/todo.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/mips.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/pc98.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/ppc.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/sparc.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/sun4v.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/x86-64.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/platforms/xbox.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/projects/acpi/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/projects/busdma/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/projects/c99/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/projects/cvsweb.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/projects/libh.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/projects/mips/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/projects/newbies.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/projects/projects.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/projects/updater.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/prstats/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/publish.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/2.0/credits.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/2.2.8R/notes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/3.1R/notes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/3.2R/notes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/3.3R/notes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/3.4R/notes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/3.5R/notes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.0R/announce.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.0R/errata.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.0R/notes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.1.1R/errata.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.1R/announce.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.1R/errata.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.1R/notes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.2R/announce.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.2R/errata.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.2R/notes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.3R/announce.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.3R/errata.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.3R/notes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.4R/announce.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.5R/announce.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.5R/notes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.6.2R/relnotes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.6R/relnotes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/4.7R/announce.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/5.0R/DP1/relnotes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/5.1R/installation.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/5.1R/relnotes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releases/snapshots.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releng/charter.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/releng/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/relnotes.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/search/index-site.xsl projects/sysctl/fr_FR.ISO8859-1/htdocs/search/search-mid.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/search/search.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/search/searchhints.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/search/sitemap.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/security/advisories.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/security/mkindex.xsl projects/sysctl/fr_FR.ISO8859-1/htdocs/security/security.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/send-pr.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/snapshots/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/support.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/support/bugreports.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/support/webresources.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/tutorials/index.xml projects/sysctl/fr_FR.ISO8859-1/htdocs/where.xml projects/sysctl/fr_FR.ISO8859-1/share/xml/catalog.xml projects/sysctl/fr_FR.ISO8859-1/share/xml/copyright.xml projects/sysctl/fr_FR.ISO8859-1/share/xml/entities.ent projects/sysctl/fr_FR.ISO8859-1/share/xml/events.xml projects/sysctl/fr_FR.ISO8859-1/share/xml/glossary.ent projects/sysctl/fr_FR.ISO8859-1/share/xml/libcommon.xsl projects/sysctl/fr_FR.ISO8859-1/share/xml/mailing-lists.ent projects/sysctl/fr_FR.ISO8859-1/share/xml/news.xml projects/sysctl/fr_FR.ISO8859-1/share/xml/newsgroups.ent projects/sysctl/fr_FR.ISO8859-1/share/xml/press.xml projects/sysctl/fr_FR.ISO8859-1/share/xml/teams.ent projects/sysctl/fr_FR.ISO8859-1/share/xml/trademarks.ent projects/sysctl/fr_FR.ISO8859-1/share/xml/translators.ent projects/sysctl/hu_HU.ISO8859-2/articles/compiz-fusion/article.xml projects/sysctl/hu_HU.ISO8859-2/articles/cups/article.xml projects/sysctl/hu_HU.ISO8859-2/articles/explaining-bsd/article.xml projects/sysctl/hu_HU.ISO8859-2/articles/gjournal-desktop/article.xml projects/sysctl/hu_HU.ISO8859-2/articles/laptop/article.xml projects/sysctl/hu_HU.ISO8859-2/articles/linux-comparison/article.xml projects/sysctl/hu_HU.ISO8859-2/articles/linux-users/article.xml projects/sysctl/hu_HU.ISO8859-2/books/faq/book.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/book.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/doc-build/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/examples/appendix.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/overview/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/psgml-mode/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/see-also/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/sgml-markup/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/sgml-primer/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/structure/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/stylesheets/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/the-website/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/tools/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/translations/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/fdp-primer/writing-style/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/Makefile projects/sysctl/hu_HU.ISO8859-2/books/handbook/advanced-networking/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/audit/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/basics/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/bibliography/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/book.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/boot/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/chapters.ent projects/sysctl/hu_HU.ISO8859-2/books/handbook/colophon.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/config/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/cutting-edge/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/desktop/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/disks/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/dtrace/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/eresources/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/filesystems/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/firewalls/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/geom/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/install/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/introduction/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/jails/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/kernelconfig/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/l10n/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/linuxemu/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/mac/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/mail/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/mirrors/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/multimedia/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/network-servers/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/pgpkeys/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/ports/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/preface/preface.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/printing/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/security/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/serialcomms/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/users/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/vinum/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/virtualization/chapter.xml projects/sysctl/hu_HU.ISO8859-2/books/handbook/x11/chapter.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/about.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/administration.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/advocacy/index.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/advocacy/myths.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/applications.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/art.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/community.xsl projects/sysctl/hu_HU.ISO8859-2/htdocs/community/irc.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/community/mailinglists.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/community/newsgroups.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/community/webresources.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/copyright/copyright.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/developers/cvs.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/docproj/doc-set.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/docproj/docproj.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/docproj/hungarian.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/docproj/sgml.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/docproj/submitting.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/docproj/who.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/docs.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/docs/books.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/docs/webresources.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/events/rss.xsl projects/sysctl/hu_HU.ISO8859-2/htdocs/features.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/index.xsl projects/sysctl/hu_HU.ISO8859-2/htdocs/internet.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/logo.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/mailto.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/news/2008/press.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/news/2009/news.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/news/news.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/news/pressreleases.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/alpha.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/amd64.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/arm.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/i386.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/ia64/index.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/ia64/machines.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/ia64/refs.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/ia64/todo.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/index.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/mips.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/pc98.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/ppc.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/sparc.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/sun4v.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/platforms/xbox.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/projects/projects.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/search/index-site.xsl projects/sysctl/hu_HU.ISO8859-2/htdocs/search/search-mid.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/search/search.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/search/searchhints.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/search/sitemap.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/security/advisories.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/security/errata-rss.xsl projects/sysctl/hu_HU.ISO8859-2/htdocs/security/errata.rss projects/sysctl/hu_HU.ISO8859-2/htdocs/security/mkindex.xsl projects/sysctl/hu_HU.ISO8859-2/htdocs/security/security-rdf.xsl projects/sysctl/hu_HU.ISO8859-2/htdocs/security/security-rss.xsl projects/sysctl/hu_HU.ISO8859-2/htdocs/security/security.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/send-pr.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/support.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/support/bugreports.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/support/webresources.xml projects/sysctl/hu_HU.ISO8859-2/htdocs/where.xml projects/sysctl/hu_HU.ISO8859-2/share/xml/bibliography.xml projects/sysctl/hu_HU.ISO8859-2/share/xml/catalog.xml projects/sysctl/hu_HU.ISO8859-2/share/xml/entities.ent projects/sysctl/hu_HU.ISO8859-2/share/xml/events.xml projects/sysctl/hu_HU.ISO8859-2/share/xml/freebsd.ent projects/sysctl/hu_HU.ISO8859-2/share/xml/glossary.ent projects/sysctl/hu_HU.ISO8859-2/share/xml/libcommon.xsl projects/sysctl/hu_HU.ISO8859-2/share/xml/mailing-lists.ent projects/sysctl/hu_HU.ISO8859-2/share/xml/news.xml projects/sysctl/hu_HU.ISO8859-2/share/xml/newsgroups.ent projects/sysctl/hu_HU.ISO8859-2/share/xml/press.xml projects/sysctl/hu_HU.ISO8859-2/share/xml/teams.ent projects/sysctl/hu_HU.ISO8859-2/share/xml/templates.events.xsl projects/sysctl/hu_HU.ISO8859-2/share/xml/templates.news-rdf.xsl projects/sysctl/hu_HU.ISO8859-2/share/xml/templates.news-rss.xsl projects/sysctl/hu_HU.ISO8859-2/share/xml/templates.newsflash.xsl projects/sysctl/hu_HU.ISO8859-2/share/xml/templates.oldnewsflash.xsl projects/sysctl/hu_HU.ISO8859-2/share/xml/templates.oldpress.xsl projects/sysctl/hu_HU.ISO8859-2/share/xml/templates.pastevents.xsl projects/sysctl/hu_HU.ISO8859-2/share/xml/templates.press-rss.xsl projects/sysctl/hu_HU.ISO8859-2/share/xml/templates.press.xsl projects/sysctl/hu_HU.ISO8859-2/share/xml/trademarks.ent projects/sysctl/hu_HU.ISO8859-2/share/xml/translators.ent projects/sysctl/it_IT.ISO8859-15/articles/committers-guide/article.xml projects/sysctl/it_IT.ISO8859-15/articles/explaining-bsd/article.xml projects/sysctl/it_IT.ISO8859-15/articles/filtering-bridges/article.xml projects/sysctl/it_IT.ISO8859-15/articles/new-users/article.xml projects/sysctl/it_IT.ISO8859-15/articles/vm-design/article.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/Makefile projects/sysctl/it_IT.ISO8859-15/books/handbook/advanced-networking/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/audit/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/basics/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/bibliography/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/book.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/boot/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/chapters.ent projects/sysctl/it_IT.ISO8859-15/books/handbook/colophon.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/config/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/cutting-edge/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/desktop/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/disks/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/eresources/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/firewalls/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/geom/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/install/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/introduction/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/jails/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/kernelconfig/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/l10n/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/linuxemu/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/mac/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/mail/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/mirrors/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/multimedia/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/network-servers/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/pgpkeys/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/ports/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/preface/preface.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/printing/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/security/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/serialcomms/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/users/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/vinum/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/virtualization/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/handbook/x11/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/bibliography/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/book.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/command-summary/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/commands/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/editors/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/getting-started/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/glossary/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/history/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/preface/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/shell-programming/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/shells/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/special-features/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/structure/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/system-resource/chapter.xml projects/sysctl/it_IT.ISO8859-15/books/unix-introduction/text-processing/chapter.xml projects/sysctl/it_IT.ISO8859-15/htdocs/about.xml projects/sysctl/it_IT.ISO8859-15/htdocs/community.xml projects/sysctl/it_IT.ISO8859-15/htdocs/copyright/copyright.xml projects/sysctl/it_IT.ISO8859-15/htdocs/docs.xml projects/sysctl/it_IT.ISO8859-15/htdocs/docs/books.xml projects/sysctl/it_IT.ISO8859-15/htdocs/index.xsl projects/sysctl/it_IT.ISO8859-15/htdocs/mailto.xml projects/sysctl/it_IT.ISO8859-15/htdocs/platforms/index.xml projects/sysctl/it_IT.ISO8859-15/htdocs/ports/index.xml projects/sysctl/it_IT.ISO8859-15/htdocs/releases/4.10R/announce.xml projects/sysctl/it_IT.ISO8859-15/htdocs/releases/4.11R/announce.xml projects/sysctl/it_IT.ISO8859-15/htdocs/releases/5.2.1R/announce.xml projects/sysctl/it_IT.ISO8859-15/htdocs/releases/5.2R/announce.xml projects/sysctl/it_IT.ISO8859-15/htdocs/releases/5.3R/announce.xml projects/sysctl/it_IT.ISO8859-15/htdocs/releases/5.4R/announce.xml projects/sysctl/it_IT.ISO8859-15/htdocs/releases/6.0R/announce.xml projects/sysctl/it_IT.ISO8859-15/htdocs/releases/index.xml projects/sysctl/it_IT.ISO8859-15/htdocs/support.xml projects/sysctl/it_IT.ISO8859-15/htdocs/where.xml projects/sysctl/it_IT.ISO8859-15/share/xml/catalog.xml projects/sysctl/it_IT.ISO8859-15/share/xml/entities.ent projects/sysctl/it_IT.ISO8859-15/share/xml/glossary.ent projects/sysctl/it_IT.ISO8859-15/share/xml/libcommon.xsl projects/sysctl/it_IT.ISO8859-15/share/xml/mailing-lists.ent projects/sysctl/it_IT.ISO8859-15/share/xml/trademarks.ent projects/sysctl/it_IT.ISO8859-15/share/xml/translators.ent projects/sysctl/ja_JP.eucJP/articles/contributing/article.xml projects/sysctl/ja_JP.eucJP/articles/contributors/article.xml projects/sysctl/ja_JP.eucJP/articles/fbsd-from-scratch/article.xml projects/sysctl/ja_JP.eucJP/articles/fonts/article.xml projects/sysctl/ja_JP.eucJP/articles/ipsec-must/article.xml projects/sysctl/ja_JP.eucJP/articles/problem-reports/article.xml projects/sysctl/ja_JP.eucJP/books/design-44bsd/book.xml projects/sysctl/ja_JP.eucJP/books/faq/book.xml projects/sysctl/ja_JP.eucJP/books/fdp-primer/book.xml projects/sysctl/ja_JP.eucJP/books/fdp-primer/examples/appendix.xml projects/sysctl/ja_JP.eucJP/books/fdp-primer/structure/chapter.xml projects/sysctl/ja_JP.eucJP/books/fdp-primer/writing-style/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/Makefile projects/sysctl/ja_JP.eucJP/books/handbook/advanced-networking/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/basics/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/bibliography/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/book.xml projects/sysctl/ja_JP.eucJP/books/handbook/boot/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/bsdinstall/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/chapters.ent projects/sysctl/ja_JP.eucJP/books/handbook/colophon.xml projects/sysctl/ja_JP.eucJP/books/handbook/config/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/cutting-edge/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/desktop/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/disks/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/eresources/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/install/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/introduction/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/jcontrib/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/kernelconfig/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/l10n/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/linuxemu/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/mail/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/mirrors/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/multimedia/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/pgpkeys/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/ports/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/preface/preface.xml projects/sysctl/ja_JP.eucJP/books/handbook/printing/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/security/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/serialcomms/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/users/chapter.xml projects/sysctl/ja_JP.eucJP/books/handbook/x11/chapter.xml projects/sysctl/ja_JP.eucJP/books/porters-handbook/book.xml projects/sysctl/ja_JP.eucJP/htdocs/about.xml projects/sysctl/ja_JP.eucJP/htdocs/community.xsl projects/sysctl/ja_JP.eucJP/htdocs/events/rss.xsl projects/sysctl/ja_JP.eucJP/htdocs/index.xsl projects/sysctl/ja_JP.eucJP/htdocs/java/java-rss.xsl projects/sysctl/ja_JP.eucJP/htdocs/java/news.xml projects/sysctl/ja_JP.eucJP/htdocs/java/newsflash.xsl projects/sysctl/ja_JP.eucJP/htdocs/news/2001/news.xml projects/sysctl/ja_JP.eucJP/htdocs/news/2001/press.xml projects/sysctl/ja_JP.eucJP/htdocs/platforms/alpha.xml projects/sysctl/ja_JP.eucJP/htdocs/platforms/mips.xml projects/sysctl/ja_JP.eucJP/htdocs/releases/9.2R/Makefile projects/sysctl/ja_JP.eucJP/htdocs/releases/9.2R/announce.xml projects/sysctl/ja_JP.eucJP/htdocs/releases/index.xml projects/sysctl/ja_JP.eucJP/htdocs/search/index-site.xsl projects/sysctl/ja_JP.eucJP/htdocs/search/sitemap.xml projects/sysctl/ja_JP.eucJP/htdocs/security/mkindex.xsl projects/sysctl/ja_JP.eucJP/htdocs/security/security.xml projects/sysctl/ja_JP.eucJP/htdocs/where.xml projects/sysctl/ja_JP.eucJP/share/xml/authors.ent projects/sysctl/ja_JP.eucJP/share/xml/catalog.xml projects/sysctl/ja_JP.eucJP/share/xml/entities.ent projects/sysctl/ja_JP.eucJP/share/xml/l10n.ent projects/sysctl/ja_JP.eucJP/share/xml/libcommon.xsl projects/sysctl/ja_JP.eucJP/share/xml/mailing-lists.ent projects/sysctl/ja_JP.eucJP/share/xml/news.xml projects/sysctl/ja_JP.eucJP/share/xml/newsgroups.ent projects/sysctl/ja_JP.eucJP/share/xml/press.xml projects/sysctl/ja_JP.eucJP/share/xml/teams.ent projects/sysctl/ja_JP.eucJP/share/xml/templates.events.xsl projects/sysctl/ja_JP.eucJP/share/xml/templates.news-rss.xsl projects/sysctl/ja_JP.eucJP/share/xml/templates.oldnewsflash.xsl projects/sysctl/ja_JP.eucJP/share/xml/templates.oldpress.xsl projects/sysctl/ja_JP.eucJP/share/xml/templates.usergroups.xsl projects/sysctl/ja_JP.eucJP/share/xml/trademarks.ent projects/sysctl/mn_MN.UTF-8/books/handbook/Makefile projects/sysctl/mn_MN.UTF-8/books/handbook/advanced-networking/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/audit/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/basics/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/bibliography/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/book.xml projects/sysctl/mn_MN.UTF-8/books/handbook/boot/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/bsdinstall/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/chapters.ent projects/sysctl/mn_MN.UTF-8/books/handbook/colophon.xml projects/sysctl/mn_MN.UTF-8/books/handbook/config/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/cutting-edge/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/desktop/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/disks/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/dtrace/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/eresources/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/filesystems/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/firewalls/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/geom/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/install/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/introduction/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/jails/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/kernelconfig/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/l10n/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/linuxemu/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/mac/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/mail/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/mirrors/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/multimedia/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/network-servers/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/pgpkeys/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/ports/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/preface/preface.xml projects/sysctl/mn_MN.UTF-8/books/handbook/printing/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/security/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/serialcomms/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/users/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/vinum/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/virtualization/chapter.xml projects/sysctl/mn_MN.UTF-8/books/handbook/x11/chapter.xml projects/sysctl/mn_MN.UTF-8/share/xml/catalog.xml projects/sysctl/mn_MN.UTF-8/share/xml/entities.ent projects/sysctl/mn_MN.UTF-8/share/xml/glossary.ent projects/sysctl/mn_MN.UTF-8/share/xml/mailing-lists.ent projects/sysctl/mn_MN.UTF-8/share/xml/newsgroups.ent projects/sysctl/mn_MN.UTF-8/share/xml/teams.ent projects/sysctl/mn_MN.UTF-8/share/xml/trademarks.ent projects/sysctl/mn_MN.UTF-8/share/xml/translators.ent projects/sysctl/nl_NL.ISO8859-1/articles/contributing-ports/article.xml projects/sysctl/nl_NL.ISO8859-1/articles/contributing/article.xml projects/sysctl/nl_NL.ISO8859-1/articles/explaining-bsd/article.xml projects/sysctl/nl_NL.ISO8859-1/articles/problem-reports/article.xml projects/sysctl/nl_NL.ISO8859-1/articles/solid-state/article.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/Makefile projects/sysctl/nl_NL.ISO8859-1/books/handbook/advanced-networking/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/audit/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/basics/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/bibliography/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/book.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/boot/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/bsdinstall/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/chapters.ent projects/sysctl/nl_NL.ISO8859-1/books/handbook/colophon.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/config/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/cutting-edge/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/desktop/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/disks/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/dtrace/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/eresources/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/filesystems/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/firewalls/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/geom/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/install/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/introduction/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/jails/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/kernelconfig/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/l10n/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/linuxemu/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/mac/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/mail/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/mirrors/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/multimedia/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/network-servers/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/pgpkeys/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/ports/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/preface/preface.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/printing/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/security/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/serialcomms/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/users/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/virtualization/chapter.xml projects/sysctl/nl_NL.ISO8859-1/books/handbook/x11/chapter.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/4xx.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/about.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/administration.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/applications.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/art.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/community.xsl projects/sysctl/nl_NL.ISO8859-1/htdocs/docs.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/features.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/index.xsl projects/sysctl/nl_NL.ISO8859-1/htdocs/internet.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/logo.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/mailto.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/privacy.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/publish.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/relnotes.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/send-pr.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/support.xml projects/sysctl/nl_NL.ISO8859-1/htdocs/where.xml projects/sysctl/nl_NL.ISO8859-1/share/xml/bibliography.xml projects/sysctl/nl_NL.ISO8859-1/share/xml/catalog.xml projects/sysctl/nl_NL.ISO8859-1/share/xml/entities.ent projects/sysctl/nl_NL.ISO8859-1/share/xml/glossary.ent projects/sysctl/nl_NL.ISO8859-1/share/xml/libcommon.xsl projects/sysctl/nl_NL.ISO8859-1/share/xml/mailing-lists.ent projects/sysctl/nl_NL.ISO8859-1/share/xml/newsgroups.ent projects/sysctl/nl_NL.ISO8859-1/share/xml/teams.ent projects/sysctl/nl_NL.ISO8859-1/share/xml/trademarks.ent projects/sysctl/nl_NL.ISO8859-1/share/xml/translators.ent projects/sysctl/pl_PL.ISO8859-2/articles/filtering-bridges/article.xml projects/sysctl/pl_PL.ISO8859-2/articles/new-users/article.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/Makefile projects/sysctl/pl_PL.ISO8859-2/books/handbook/advanced-networking/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/audit/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/basics/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/bibliography/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/book.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/boot/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/chapters.ent projects/sysctl/pl_PL.ISO8859-2/books/handbook/colophon.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/config/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/cutting-edge/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/desktop/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/disks/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/eresources/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/firewalls/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/geom/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/install/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/introduction/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/kernelconfig/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/l10n/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/linuxemu/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/mac/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/mail/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/mirrors/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/multimedia/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/network-servers/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/pgpkeys/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/ports/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/preface/preface.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/printing/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/security/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/serialcomms/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/users/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/vinum/chapter.xml projects/sysctl/pl_PL.ISO8859-2/books/handbook/x11/chapter.xml projects/sysctl/pl_PL.ISO8859-2/share/xml/catalog.xml projects/sysctl/pl_PL.ISO8859-2/share/xml/entities.ent projects/sysctl/pl_PL.ISO8859-2/share/xml/mailing-lists.ent projects/sysctl/pl_PL.ISO8859-2/share/xml/teams.ent projects/sysctl/pl_PL.ISO8859-2/share/xml/trademarks.ent projects/sysctl/pt_BR.ISO8859-1/articles/building-products/article.xml projects/sysctl/pt_BR.ISO8859-1/articles/contributing-ports/article.xml projects/sysctl/pt_BR.ISO8859-1/articles/contributing/article.xml projects/sysctl/pt_BR.ISO8859-1/articles/explaining-bsd/article.xml projects/sysctl/pt_BR.ISO8859-1/articles/freebsd-questions/article.xml projects/sysctl/pt_BR.ISO8859-1/articles/freebsd-update-server/article.xml projects/sysctl/pt_BR.ISO8859-1/articles/hubs/article.xml projects/sysctl/pt_BR.ISO8859-1/articles/linux-users/article.xml projects/sysctl/pt_BR.ISO8859-1/articles/new-users/article.xml projects/sysctl/pt_BR.ISO8859-1/articles/portbuild/article.xml projects/sysctl/pt_BR.ISO8859-1/articles/problem-reports/article.xml projects/sysctl/pt_BR.ISO8859-1/books/faq/book.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/book.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/doc-build/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/examples/appendix.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/overview/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/psgml-mode/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/see-also/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/sgml-markup/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/sgml-primer/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/structure/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/stylesheets/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/the-website/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/tools/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/translations/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/fdp-primer/writing-style/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/Makefile projects/sysctl/pt_BR.ISO8859-1/books/handbook/advanced-networking/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/basics/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/bibliography/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/book.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/boot/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/chapters.ent projects/sysctl/pt_BR.ISO8859-1/books/handbook/colophon.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/config/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/cutting-edge/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/disks/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/eresources/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/install/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/introduction/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/kernelconfig/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/l10n/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/linuxemu/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/mail/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/mirrors/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/pgpkeys/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/ports/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/preface/preface.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/printing/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/security/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/serialcomms/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/users/chapter.xml projects/sysctl/pt_BR.ISO8859-1/books/handbook/x11/chapter.xml projects/sysctl/pt_BR.ISO8859-1/share/xml/catalog.xml projects/sysctl/pt_BR.ISO8859-1/share/xml/entities.ent projects/sysctl/pt_BR.ISO8859-1/share/xml/mailing-lists.ent projects/sysctl/pt_BR.ISO8859-1/share/xml/newsgroups.ent projects/sysctl/pt_BR.ISO8859-1/share/xml/teams.ent projects/sysctl/pt_BR.ISO8859-1/share/xml/trademarks.ent projects/sysctl/pt_BR.ISO8859-1/share/xml/translators.ent projects/sysctl/pt_BR.ISO8859-1/share/xml/words.ent projects/sysctl/ru_RU.KOI8-R/articles/committers-guide/article.xml projects/sysctl/ru_RU.KOI8-R/articles/console-server/article.xml projects/sysctl/ru_RU.KOI8-R/articles/contributing/article.xml projects/sysctl/ru_RU.KOI8-R/articles/cups/article.xml projects/sysctl/ru_RU.KOI8-R/articles/custom-gcc/article.xml projects/sysctl/ru_RU.KOI8-R/articles/cvs-freebsd/article.xml projects/sysctl/ru_RU.KOI8-R/articles/explaining-bsd/article.xml projects/sysctl/ru_RU.KOI8-R/articles/fbsd-from-scratch/article.xml projects/sysctl/ru_RU.KOI8-R/articles/fonts/article.xml projects/sysctl/ru_RU.KOI8-R/articles/freebsd-questions/article.xml projects/sysctl/ru_RU.KOI8-R/articles/geom-class/article.xml projects/sysctl/ru_RU.KOI8-R/articles/gjournal-desktop/article.xml projects/sysctl/ru_RU.KOI8-R/articles/hubs/article.xml projects/sysctl/ru_RU.KOI8-R/articles/ipsec-must/article.xml projects/sysctl/ru_RU.KOI8-R/articles/laptop/article.xml projects/sysctl/ru_RU.KOI8-R/articles/linux-comparison/article.xml projects/sysctl/ru_RU.KOI8-R/articles/mailing-list-faq/article.xml projects/sysctl/ru_RU.KOI8-R/articles/mh/article.xml projects/sysctl/ru_RU.KOI8-R/articles/new-users/article.xml projects/sysctl/ru_RU.KOI8-R/articles/pam/article.xml projects/sysctl/ru_RU.KOI8-R/articles/portbuild/article.xml projects/sysctl/ru_RU.KOI8-R/articles/pr-guidelines/article.xml projects/sysctl/ru_RU.KOI8-R/articles/problem-reports/article.xml projects/sysctl/ru_RU.KOI8-R/articles/relaydelay/article.xml projects/sysctl/ru_RU.KOI8-R/articles/releng-packages/article.xml projects/sysctl/ru_RU.KOI8-R/articles/releng/article.xml projects/sysctl/ru_RU.KOI8-R/articles/solid-state/article.xml projects/sysctl/ru_RU.KOI8-R/articles/vm-design/article.xml projects/sysctl/ru_RU.KOI8-R/books/design-44bsd/book.xml projects/sysctl/ru_RU.KOI8-R/books/developers-handbook/Makefile projects/sysctl/ru_RU.KOI8-R/books/developers-handbook/book.xml projects/sysctl/ru_RU.KOI8-R/books/developers-handbook/chapters.ent projects/sysctl/ru_RU.KOI8-R/books/developers-handbook/introduction/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/faq/book.xml projects/sysctl/ru_RU.KOI8-R/books/fdp-primer/book.xml projects/sysctl/ru_RU.KOI8-R/books/fdp-primer/sgml-markup/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/fdp-primer/writing-style/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/Makefile projects/sysctl/ru_RU.KOI8-R/books/handbook/advanced-networking/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/audit/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/basics/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/bibliography/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/book.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/boot/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/bsdinstall/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/chapters.ent projects/sysctl/ru_RU.KOI8-R/books/handbook/colophon.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/config/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/cutting-edge/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/desktop/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/disks/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/eresources/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/filesystems/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/firewalls/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/geom/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/install/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/introduction/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/kernelconfig/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/l10n/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/linuxemu/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/mac/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/mail/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/mirrors/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/multimedia/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/network-servers/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/pgpkeys/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/ports/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/preface/preface.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/printing/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/security/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/serialcomms/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/users/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/handbook/x11/chapter.xml projects/sysctl/ru_RU.KOI8-R/books/porters-handbook/Makefile projects/sysctl/ru_RU.KOI8-R/books/porters-handbook/book.xml (contents, props changed) projects/sysctl/ru_RU.KOI8-R/htdocs/about.xml projects/sysctl/ru_RU.KOI8-R/htdocs/applications.xml projects/sysctl/ru_RU.KOI8-R/htdocs/art.xml projects/sysctl/ru_RU.KOI8-R/htdocs/availability.xml projects/sysctl/ru_RU.KOI8-R/htdocs/commercial/commercial.xml projects/sysctl/ru_RU.KOI8-R/htdocs/community.xsl projects/sysctl/ru_RU.KOI8-R/htdocs/community/irc.xml projects/sysctl/ru_RU.KOI8-R/htdocs/community/mailinglists.xml projects/sysctl/ru_RU.KOI8-R/htdocs/community/newsgroups.xml projects/sysctl/ru_RU.KOI8-R/htdocs/community/social.xsl projects/sysctl/ru_RU.KOI8-R/htdocs/community/webresources.xml projects/sysctl/ru_RU.KOI8-R/htdocs/copyright/copyright.xml projects/sysctl/ru_RU.KOI8-R/htdocs/copyright/daemon.xml projects/sysctl/ru_RU.KOI8-R/htdocs/copyright/freebsd-doc-license.xml projects/sysctl/ru_RU.KOI8-R/htdocs/copyright/freebsd-license.xml projects/sysctl/ru_RU.KOI8-R/htdocs/copyright/license.xml projects/sysctl/ru_RU.KOI8-R/htdocs/copyright/trademarks.xml projects/sysctl/ru_RU.KOI8-R/htdocs/developers/cvs.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docproj/current.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docproj/doc-set.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docproj/docproj.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docproj/handbook.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docproj/handbook3.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docproj/sgml.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docproj/submitting.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docproj/translations.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docproj/who.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docs.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docs/books.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docs/man.xml projects/sysctl/ru_RU.KOI8-R/htdocs/docs/webresources.xml projects/sysctl/ru_RU.KOI8-R/htdocs/donations/donors.xml projects/sysctl/ru_RU.KOI8-R/htdocs/donations/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/donations/wantlist.xml projects/sysctl/ru_RU.KOI8-R/htdocs/events/2003/bsdcon-devsummit.xml projects/sysctl/ru_RU.KOI8-R/htdocs/events/rss.xsl projects/sysctl/ru_RU.KOI8-R/htdocs/features.xml projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/contact.xml projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/docs/bugging.xml projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/docs/develfaq.xml projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/docs/example-Makefile.xml projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/docs/faq2.xml projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/docs/gnome2_porting.xml projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/docs/gnome_porting.xml projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/docs/knownissues.xml projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/docs/porting.xml projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/docs/volunteer.xml projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/index.xsl projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/newsflash.xsl projects/sysctl/ru_RU.KOI8-R/htdocs/gnome/screenshots.xml projects/sysctl/ru_RU.KOI8-R/htdocs/handbook/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/index.xsl projects/sysctl/ru_RU.KOI8-R/htdocs/internal/about.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/bylaws.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/core-vote.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/developer.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/doceng.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/expire-bits.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/fortunes.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/homepage.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/internal.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/machines.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/mirror.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/new-account.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/photos.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/policies.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/releng.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/rtp.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internal/statistic.xml projects/sysctl/ru_RU.KOI8-R/htdocs/internet.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/advocacy.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/dists/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/docs/faq.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/docs/howtoports.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/docs/newbies.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/docs/performance.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/docs/tutorials.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/howhelp.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/install.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/links/api.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/links/development.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/links/documentation.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/links/freebsd.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/links/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/links/resources.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/links/servlets.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/links/tools.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/links/tutorials.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/links/vendor.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/newsflash.xml projects/sysctl/ru_RU.KOI8-R/htdocs/java/press.xml projects/sysctl/ru_RU.KOI8-R/htdocs/logo.xml projects/sysctl/ru_RU.KOI8-R/htdocs/mailto.xml projects/sysctl/ru_RU.KOI8-R/htdocs/marketing/os-comparison.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/1996/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/1997/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/1998/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/1999/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/2000/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/news.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/press-rel-1.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/press-rel-2.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/press-rel-3.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/press-rel-4.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/press-rel-5.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/pressreleases.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/sou1999.xml projects/sysctl/ru_RU.KOI8-R/htdocs/news/status/status.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/alpha.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/amd64.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/amd64/motherboards.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/arm.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/i386.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/ia64.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/ia64/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/ia64/machines.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/ia64/refs.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/ia64/todo.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/mips.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/pc98.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/ppc.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/sparc.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/x86-64.xml projects/sysctl/ru_RU.KOI8-R/htdocs/platforms/xbox.xml projects/sysctl/ru_RU.KOI8-R/htdocs/portmgr/charter.xml projects/sysctl/ru_RU.KOI8-R/htdocs/portmgr/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/portmgr/policies.xml projects/sysctl/ru_RU.KOI8-R/htdocs/portmgr/qa.xml projects/sysctl/ru_RU.KOI8-R/htdocs/ports/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/ports/installing.xml projects/sysctl/ru_RU.KOI8-R/htdocs/ports/portindex projects/sysctl/ru_RU.KOI8-R/htdocs/ports/references.xml projects/sysctl/ru_RU.KOI8-R/htdocs/ports/searching.xml projects/sysctl/ru_RU.KOI8-R/htdocs/ports/updating.xml projects/sysctl/ru_RU.KOI8-R/htdocs/projects/busdma/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/projects/cvsweb.xml projects/sysctl/ru_RU.KOI8-R/htdocs/projects/newbies.xml projects/sysctl/ru_RU.KOI8-R/htdocs/projects/projects.xml projects/sysctl/ru_RU.KOI8-R/htdocs/projects/summerofcode.xml projects/sysctl/ru_RU.KOI8-R/htdocs/prstats/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/publish.xml projects/sysctl/ru_RU.KOI8-R/htdocs/releases/5.3R/announce.xml projects/sysctl/ru_RU.KOI8-R/htdocs/releases/5.3R/hardware.xml projects/sysctl/ru_RU.KOI8-R/htdocs/releases/5.3R/installation.xml projects/sysctl/ru_RU.KOI8-R/htdocs/releases/5.3R/relnotes.xml projects/sysctl/ru_RU.KOI8-R/htdocs/releases/5.4R/announce.xml projects/sysctl/ru_RU.KOI8-R/htdocs/releases/5.4R/hardware.xml projects/sysctl/ru_RU.KOI8-R/htdocs/releases/5.4R/installation.xml projects/sysctl/ru_RU.KOI8-R/htdocs/releases/5.4R/relnotes.xml projects/sysctl/ru_RU.KOI8-R/htdocs/releases/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/releng/charter.xml projects/sysctl/ru_RU.KOI8-R/htdocs/releng/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/relnotes.xml projects/sysctl/ru_RU.KOI8-R/htdocs/search/index-site.xsl projects/sysctl/ru_RU.KOI8-R/htdocs/search/search-mid.xml projects/sysctl/ru_RU.KOI8-R/htdocs/search/search.xml projects/sysctl/ru_RU.KOI8-R/htdocs/search/searchhints.xml projects/sysctl/ru_RU.KOI8-R/htdocs/search/sitemap.xml projects/sysctl/ru_RU.KOI8-R/htdocs/security/advisories.xml projects/sysctl/ru_RU.KOI8-R/htdocs/security/errata-rss.xsl projects/sysctl/ru_RU.KOI8-R/htdocs/security/mkindex.xsl projects/sysctl/ru_RU.KOI8-R/htdocs/security/notices.xml projects/sysctl/ru_RU.KOI8-R/htdocs/security/security-rdf.xsl projects/sysctl/ru_RU.KOI8-R/htdocs/security/security-rss.xsl projects/sysctl/ru_RU.KOI8-R/htdocs/security/security.xml projects/sysctl/ru_RU.KOI8-R/htdocs/send-pr.xml projects/sysctl/ru_RU.KOI8-R/htdocs/snapshots/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/support.xml projects/sysctl/ru_RU.KOI8-R/htdocs/support/bugreports.xml projects/sysctl/ru_RU.KOI8-R/htdocs/support/webresources.xml projects/sysctl/ru_RU.KOI8-R/htdocs/tutorials/index.xml projects/sysctl/ru_RU.KOI8-R/htdocs/where.xml projects/sysctl/ru_RU.KOI8-R/share/xml/catalog.xml projects/sysctl/ru_RU.KOI8-R/share/xml/entities.ent projects/sysctl/ru_RU.KOI8-R/share/xml/events.xml projects/sysctl/ru_RU.KOI8-R/share/xml/events2003.xml projects/sysctl/ru_RU.KOI8-R/share/xml/events2004.xml projects/sysctl/ru_RU.KOI8-R/share/xml/events2005.xml projects/sysctl/ru_RU.KOI8-R/share/xml/events2006.xml projects/sysctl/ru_RU.KOI8-R/share/xml/events2007.xml projects/sysctl/ru_RU.KOI8-R/share/xml/events2008.xml projects/sysctl/ru_RU.KOI8-R/share/xml/events2009.xml projects/sysctl/ru_RU.KOI8-R/share/xml/events2010.xml projects/sysctl/ru_RU.KOI8-R/share/xml/events2011.xml projects/sysctl/ru_RU.KOI8-R/share/xml/events2012.xml projects/sysctl/ru_RU.KOI8-R/share/xml/events2013.xml projects/sysctl/ru_RU.KOI8-R/share/xml/glossary.ent projects/sysctl/ru_RU.KOI8-R/share/xml/libcommon.xsl projects/sysctl/ru_RU.KOI8-R/share/xml/mailing-lists.ent projects/sysctl/ru_RU.KOI8-R/share/xml/news.xml projects/sysctl/ru_RU.KOI8-R/share/xml/newsgroups.ent projects/sysctl/ru_RU.KOI8-R/share/xml/press.xml projects/sysctl/ru_RU.KOI8-R/share/xml/teams.ent projects/sysctl/ru_RU.KOI8-R/share/xml/templates.events.xsl projects/sysctl/ru_RU.KOI8-R/share/xml/templates.usergroups.xsl projects/sysctl/ru_RU.KOI8-R/share/xml/trademarks.ent projects/sysctl/ru_RU.KOI8-R/share/xml/translators.ent projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-adduser1.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-adduser2.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-adduser3.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-boot-loader-menu.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-choose-mode.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-config-components.png projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-config-crashdump.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-config-hostname.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-config-keymap.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-config-services.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-configure-network-interface-ipv4-dhcp.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-configure-network-interface-ipv4-static.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-configure-network-interface-ipv4.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-configure-network-interface-ipv6-static.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-configure-network-interface-ipv6.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-configure-network-interface-slaac.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-configure-network-interface.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-configure-network-ipv4-dns.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-configure-wireless-accesspoints.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-configure-wireless-scan.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-configure-wireless-wpa2setup.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-distfile-extracting.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-distfile-fetching.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-distfile-verifying.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-final-confirmation.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-final-modification-shell.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-finalconfiguration.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-keymap-select-default.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-mainexit.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-netinstall-files.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-netinstall-mirrorselect.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-part-entire-part.png projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-part-guided-disk.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-part-guided-manual.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-part-manual-addpart.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-part-manual-create.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-part-manual-partscheme.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-part-review.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-post-root-passwd.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-set-clock-local-utc.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-timezone-confirm.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-timezone-country.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-timezone-region.png (contents, props changed) projects/sysctl/share/images/books/handbook/bsdinstall/bsdinstall-timezone-zone.png (contents, props changed) projects/sysctl/share/images/callouts/gen.sh projects/sysctl/share/misc/docbook.css projects/sysctl/share/mk/doc.commands.mk projects/sysctl/share/mk/doc.docbook.mk projects/sysctl/share/mk/doc.images.mk projects/sysctl/share/mk/web.site.mk projects/sysctl/share/pgpkeys/aaron.key projects/sysctl/share/pgpkeys/ache.key projects/sysctl/share/pgpkeys/achim.key projects/sysctl/share/pgpkeys/acm.key projects/sysctl/share/pgpkeys/adamw.key projects/sysctl/share/pgpkeys/addkey.sh projects/sysctl/share/pgpkeys/ae.key projects/sysctl/share/pgpkeys/ahze.key projects/sysctl/share/pgpkeys/ak.key projects/sysctl/share/pgpkeys/alc.key projects/sysctl/share/pgpkeys/ale.key projects/sysctl/share/pgpkeys/alepulver.key projects/sysctl/share/pgpkeys/alex.key projects/sysctl/share/pgpkeys/alexbl.key projects/sysctl/share/pgpkeys/amdmi3.key projects/sysctl/share/pgpkeys/anchie.key projects/sysctl/share/pgpkeys/anders.key projects/sysctl/share/pgpkeys/andreas.key projects/sysctl/share/pgpkeys/andrew.key projects/sysctl/share/pgpkeys/anholt.key projects/sysctl/share/pgpkeys/anray.key projects/sysctl/share/pgpkeys/antoine.key projects/sysctl/share/pgpkeys/araujo.key projects/sysctl/share/pgpkeys/ariff.key projects/sysctl/share/pgpkeys/art.key projects/sysctl/share/pgpkeys/arun.key projects/sysctl/share/pgpkeys/arved.key projects/sysctl/share/pgpkeys/asami.key projects/sysctl/share/pgpkeys/ashish.key projects/sysctl/share/pgpkeys/asomers.key projects/sysctl/share/pgpkeys/avatar.key projects/sysctl/share/pgpkeys/avg.key projects/sysctl/share/pgpkeys/avilla.key projects/sysctl/share/pgpkeys/avl.key projects/sysctl/share/pgpkeys/bakul.key projects/sysctl/share/pgpkeys/bapt.key projects/sysctl/share/pgpkeys/bar.key projects/sysctl/share/pgpkeys/barner.key projects/sysctl/share/pgpkeys/bcr.key projects/sysctl/share/pgpkeys/bdrewery.key projects/sysctl/share/pgpkeys/beat.key projects/sysctl/share/pgpkeys/beech.key projects/sysctl/share/pgpkeys/ben.key projects/sysctl/share/pgpkeys/benjsc.key projects/sysctl/share/pgpkeys/benno.key projects/sysctl/share/pgpkeys/bf.key projects/sysctl/share/pgpkeys/bhaga.key projects/sysctl/share/pgpkeys/billf.key projects/sysctl/share/pgpkeys/bjk.key projects/sysctl/share/pgpkeys/bk.key projects/sysctl/share/pgpkeys/blackend.key projects/sysctl/share/pgpkeys/bland.key projects/sysctl/share/pgpkeys/bmah.key projects/sysctl/share/pgpkeys/bms.key projects/sysctl/share/pgpkeys/brd.key projects/sysctl/share/pgpkeys/brian.key projects/sysctl/share/pgpkeys/brix.key projects/sysctl/share/pgpkeys/brooks.key projects/sysctl/share/pgpkeys/brucec.key projects/sysctl/share/pgpkeys/brueffer.key projects/sysctl/share/pgpkeys/bruno.key projects/sysctl/share/pgpkeys/bryanv.key projects/sysctl/share/pgpkeys/bsam.key projects/sysctl/share/pgpkeys/bschmidt.key projects/sysctl/share/pgpkeys/bsd.key projects/sysctl/share/pgpkeys/bushman.key projects/sysctl/share/pgpkeys/bvs.key projects/sysctl/share/pgpkeys/bz.key projects/sysctl/share/pgpkeys/carl.key projects/sysctl/share/pgpkeys/cel.key projects/sysctl/share/pgpkeys/ceri.key projects/sysctl/share/pgpkeys/cherry.key projects/sysctl/share/pgpkeys/chinsan.key projects/sysctl/share/pgpkeys/cjc.key projects/sysctl/share/pgpkeys/cjh.key projects/sysctl/share/pgpkeys/clement.key projects/sysctl/share/pgpkeys/clive.key projects/sysctl/share/pgpkeys/clsung.key projects/sysctl/share/pgpkeys/cokane.key projects/sysctl/share/pgpkeys/core-secretary.key projects/sysctl/share/pgpkeys/cperciva.key projects/sysctl/share/pgpkeys/crees.key projects/sysctl/share/pgpkeys/cs.key projects/sysctl/share/pgpkeys/cshumway.key projects/sysctl/share/pgpkeys/csjp.key projects/sysctl/share/pgpkeys/culot.key projects/sysctl/share/pgpkeys/daichi.key projects/sysctl/share/pgpkeys/damien.key projects/sysctl/share/pgpkeys/danfe.key projects/sysctl/share/pgpkeys/danger.key projects/sysctl/share/pgpkeys/dannyboy.key projects/sysctl/share/pgpkeys/das.key projects/sysctl/share/pgpkeys/davide.key projects/sysctl/share/pgpkeys/davidxu.key projects/sysctl/share/pgpkeys/db.key projects/sysctl/share/pgpkeys/dbn.key projects/sysctl/share/pgpkeys/dchagin.key projects/sysctl/share/pgpkeys/dcs.key projects/sysctl/share/pgpkeys/dd.key projects/sysctl/share/pgpkeys/deb.key projects/sysctl/share/pgpkeys/decke.key projects/sysctl/share/pgpkeys/deischen.key projects/sysctl/share/pgpkeys/delphij.key projects/sysctl/share/pgpkeys/demon.key projects/sysctl/share/pgpkeys/den.key projects/sysctl/share/pgpkeys/des.key projects/sysctl/share/pgpkeys/dfr.key projects/sysctl/share/pgpkeys/dhartmei.key projects/sysctl/share/pgpkeys/dhn.key projects/sysctl/share/pgpkeys/dhw.key projects/sysctl/share/pgpkeys/dim.key projects/sysctl/share/pgpkeys/dinoex.key projects/sysctl/share/pgpkeys/dru.key projects/sysctl/share/pgpkeys/dryice.key projects/sysctl/share/pgpkeys/dutchdaemon.key projects/sysctl/share/pgpkeys/dwmalone.key projects/sysctl/share/pgpkeys/eadler.key projects/sysctl/share/pgpkeys/ebrandi.key projects/sysctl/share/pgpkeys/ed.key projects/sysctl/share/pgpkeys/ehaupt.key projects/sysctl/share/pgpkeys/emaste.key projects/sysctl/share/pgpkeys/emax.key projects/sysctl/share/pgpkeys/erwin.key projects/sysctl/share/pgpkeys/fabient.key projects/sysctl/share/pgpkeys/fanf.key projects/sysctl/share/pgpkeys/farrokhi.key projects/sysctl/share/pgpkeys/feld.key projects/sysctl/share/pgpkeys/fjoe.key projects/sysctl/share/pgpkeys/flo.key projects/sysctl/share/pgpkeys/fluffy.key projects/sysctl/share/pgpkeys/flz.key projects/sysctl/share/pgpkeys/foxfair.key projects/sysctl/share/pgpkeys/gabor.key projects/sysctl/share/pgpkeys/gahr.key projects/sysctl/share/pgpkeys/ganbold.key projects/sysctl/share/pgpkeys/garga.key projects/sysctl/share/pgpkeys/garys.key projects/sysctl/share/pgpkeys/gavin.key projects/sysctl/share/pgpkeys/gblach.key projects/sysctl/share/pgpkeys/gerald.key projects/sysctl/share/pgpkeys/ghelmer.key projects/sysctl/share/pgpkeys/gibbs.key projects/sysctl/share/pgpkeys/girgen.key projects/sysctl/share/pgpkeys/gjb.key projects/sysctl/share/pgpkeys/glarkin.key projects/sysctl/share/pgpkeys/glebius.key projects/sysctl/share/pgpkeys/glewis.key projects/sysctl/share/pgpkeys/gnn.key projects/sysctl/share/pgpkeys/gordon.key projects/sysctl/share/pgpkeys/green.key projects/sysctl/share/pgpkeys/grehan.key projects/sysctl/share/pgpkeys/gshapiro.key projects/sysctl/share/pgpkeys/gsutter.key projects/sysctl/share/pgpkeys/guido.key projects/sysctl/share/pgpkeys/harti.key projects/sysctl/share/pgpkeys/hiren.key projects/sysctl/share/pgpkeys/hmp.key projects/sysctl/share/pgpkeys/hq.key projects/sysctl/share/pgpkeys/hrs.key projects/sysctl/share/pgpkeys/ijliao.key projects/sysctl/share/pgpkeys/imp.key projects/sysctl/share/pgpkeys/issyl0.key projects/sysctl/share/pgpkeys/itetcu.key projects/sysctl/share/pgpkeys/ivoras.key projects/sysctl/share/pgpkeys/jacula.key projects/sysctl/share/pgpkeys/jadawin.key projects/sysctl/share/pgpkeys/jamie.key projects/sysctl/share/pgpkeys/jase.key projects/sysctl/share/pgpkeys/jcamou.key projects/sysctl/share/pgpkeys/jceel.key projects/sysctl/share/pgpkeys/jchandra.key projects/sysctl/share/pgpkeys/jdp.key projects/sysctl/share/pgpkeys/jedgar.key projects/sysctl/share/pgpkeys/jesper.key projects/sysctl/share/pgpkeys/jgh.key projects/sysctl/share/pgpkeys/jh.key projects/sysctl/share/pgpkeys/jhale.key projects/sysctl/share/pgpkeys/jhay.key projects/sysctl/share/pgpkeys/jhb.key projects/sysctl/share/pgpkeys/jhibbits.key projects/sysctl/share/pgpkeys/jilles.key projects/sysctl/share/pgpkeys/jim.key projects/sysctl/share/pgpkeys/jinmei.key projects/sysctl/share/pgpkeys/jkh.key projects/sysctl/share/pgpkeys/jkim.key projects/sysctl/share/pgpkeys/jkois.key projects/sysctl/share/pgpkeys/jkoshy.key projects/sysctl/share/pgpkeys/jlaffaye.key projects/sysctl/share/pgpkeys/jlh.key projects/sysctl/share/pgpkeys/jmb.key projects/sysctl/share/pgpkeys/jmelo.key projects/sysctl/share/pgpkeys/jmg.key projects/sysctl/share/pgpkeys/joe.key projects/sysctl/share/pgpkeys/joerg.key projects/sysctl/share/pgpkeys/johans.key projects/sysctl/share/pgpkeys/jon.key projects/sysctl/share/pgpkeys/jonathan.key projects/sysctl/share/pgpkeys/josef.key projects/sysctl/share/pgpkeys/jpaetzel.key projects/sysctl/share/pgpkeys/jsa.key projects/sysctl/share/pgpkeys/jylefort.key projects/sysctl/share/pgpkeys/kaiw.key projects/sysctl/share/pgpkeys/kato.key projects/sysctl/share/pgpkeys/ken.key projects/sysctl/share/pgpkeys/kensmith.key projects/sysctl/share/pgpkeys/keramida.key projects/sysctl/share/pgpkeys/kib.key projects/sysctl/share/pgpkeys/kmoore.key projects/sysctl/share/pgpkeys/knu.key projects/sysctl/share/pgpkeys/koitsu.key projects/sysctl/share/pgpkeys/krion.key projects/sysctl/share/pgpkeys/kris.key projects/sysctl/share/pgpkeys/kuriyama.key projects/sysctl/share/pgpkeys/kwm.key projects/sysctl/share/pgpkeys/laszlof.key projects/sysctl/share/pgpkeys/lawrance.key projects/sysctl/share/pgpkeys/lbr.key projects/sysctl/share/pgpkeys/le.key projects/sysctl/share/pgpkeys/leeym.key projects/sysctl/share/pgpkeys/lesi.key projects/sysctl/share/pgpkeys/linimon.key projects/sysctl/share/pgpkeys/lioux.key projects/sysctl/share/pgpkeys/lippe.key projects/sysctl/share/pgpkeys/lme.key projects/sysctl/share/pgpkeys/loader.key projects/sysctl/share/pgpkeys/lofi.key projects/sysctl/share/pgpkeys/lth.key projects/sysctl/share/pgpkeys/lulf.key projects/sysctl/share/pgpkeys/luoqi.key projects/sysctl/share/pgpkeys/lwhsu.key projects/sysctl/share/pgpkeys/lx.key projects/sysctl/share/pgpkeys/madpilot.key projects/sysctl/share/pgpkeys/maho.key projects/sysctl/share/pgpkeys/makc.key projects/sysctl/share/pgpkeys/mandree.key projects/sysctl/share/pgpkeys/manolis.key projects/sysctl/share/pgpkeys/marcel.key projects/sysctl/share/pgpkeys/marck.key projects/sysctl/share/pgpkeys/marcus.key projects/sysctl/share/pgpkeys/marius.key projects/sysctl/share/pgpkeys/markj.key projects/sysctl/share/pgpkeys/markm.key projects/sysctl/share/pgpkeys/markp.key projects/sysctl/share/pgpkeys/marks.key projects/sysctl/share/pgpkeys/markus.key projects/sysctl/share/pgpkeys/martymac.key projects/sysctl/share/pgpkeys/mat.key projects/sysctl/share/pgpkeys/matteo.key projects/sysctl/share/pgpkeys/matthew.key projects/sysctl/share/pgpkeys/matusita.key projects/sysctl/share/pgpkeys/mav.key projects/sysctl/share/pgpkeys/max.key projects/sysctl/share/pgpkeys/maxim.key projects/sysctl/share/pgpkeys/mbr.key projects/sysctl/share/pgpkeys/mdf.key projects/sysctl/share/pgpkeys/melifaro.key projects/sysctl/share/pgpkeys/metal.key projects/sysctl/share/pgpkeys/mheinen.key projects/sysctl/share/pgpkeys/mi.key projects/sysctl/share/pgpkeys/mich.key projects/sysctl/share/pgpkeys/mikeh.key projects/sysctl/share/pgpkeys/miwi.key projects/sysctl/share/pgpkeys/mjg.key projects/sysctl/share/pgpkeys/mlaier.key projects/sysctl/share/pgpkeys/mm.key projects/sysctl/share/pgpkeys/mnag.key projects/sysctl/share/pgpkeys/mp.key projects/sysctl/share/pgpkeys/mtm.key projects/sysctl/share/pgpkeys/murray.key projects/sysctl/share/pgpkeys/mux.key projects/sysctl/share/pgpkeys/mva.key projects/sysctl/share/pgpkeys/nate.key projects/sysctl/share/pgpkeys/nectar.key projects/sysctl/share/pgpkeys/nemoliu.key projects/sysctl/share/pgpkeys/netchild.key projects/sysctl/share/pgpkeys/niels.key projects/sysctl/share/pgpkeys/nik.key projects/sysctl/share/pgpkeys/niklas.key projects/sysctl/share/pgpkeys/nivit.key projects/sysctl/share/pgpkeys/njl.key projects/sysctl/share/pgpkeys/nork.key projects/sysctl/share/pgpkeys/novel.key projects/sysctl/share/pgpkeys/nox.key projects/sysctl/share/pgpkeys/np.key projects/sysctl/share/pgpkeys/nsouch.key projects/sysctl/share/pgpkeys/nwhitehorn.key projects/sysctl/share/pgpkeys/nyan.key projects/sysctl/share/pgpkeys/obraun.key projects/sysctl/share/pgpkeys/obrien.key projects/sysctl/share/pgpkeys/ohauer.key projects/sysctl/share/pgpkeys/oleg.key projects/sysctl/share/pgpkeys/olgeni.key (contents, props changed) projects/sysctl/share/pgpkeys/olivierd.key projects/sysctl/share/pgpkeys/patrick.key projects/sysctl/share/pgpkeys/paul.key projects/sysctl/share/pgpkeys/pav.key projects/sysctl/share/pgpkeys/pclin.key projects/sysctl/share/pgpkeys/peadar.key projects/sysctl/share/pgpkeys/perky.key projects/sysctl/share/pgpkeys/petef.key projects/sysctl/share/pgpkeys/peter.key projects/sysctl/share/pgpkeys/peterj.key projects/sysctl/share/pgpkeys/pfg.key projects/sysctl/share/pgpkeys/pgj.key projects/sysctl/share/pgpkeys/pgollucci.key projects/sysctl/share/pgpkeys/pgpkeys-core.xml projects/sysctl/share/pgpkeys/pgpkeys-developers.xml projects/sysctl/share/pgpkeys/pgpkeys-officers.xml projects/sysctl/share/pgpkeys/pgpkeys-other.xml projects/sysctl/share/pgpkeys/pgpkeys.ent projects/sysctl/share/pgpkeys/phantom.key projects/sysctl/share/pgpkeys/philip.key projects/sysctl/share/pgpkeys/phk.key projects/sysctl/share/pgpkeys/pho.key projects/sysctl/share/pgpkeys/pirzyk.key projects/sysctl/share/pgpkeys/pjd.key projects/sysctl/share/pgpkeys/pluknet.key projects/sysctl/share/pgpkeys/portmgr-secretary.key projects/sysctl/share/pgpkeys/qingli.key projects/sysctl/share/pgpkeys/rafan.key projects/sysctl/share/pgpkeys/rakuco.key projects/sysctl/share/pgpkeys/ray.key projects/sysctl/share/pgpkeys/rdivacky.key projects/sysctl/share/pgpkeys/rea.key projects/sysctl/share/pgpkeys/rees.key projects/sysctl/share/pgpkeys/remko.key projects/sysctl/share/pgpkeys/rene.key projects/sysctl/share/pgpkeys/rich.key projects/sysctl/share/pgpkeys/rik.key projects/sysctl/share/pgpkeys/rink.key projects/sysctl/share/pgpkeys/rm.key projects/sysctl/share/pgpkeys/rmacklem.key projects/sysctl/share/pgpkeys/rmh.key projects/sysctl/share/pgpkeys/rnoland.key projects/sysctl/share/pgpkeys/roam.key projects/sysctl/share/pgpkeys/roberto.key projects/sysctl/share/pgpkeys/rodrigc.key projects/sysctl/share/pgpkeys/romain.key projects/sysctl/share/pgpkeys/rpaulo.key projects/sysctl/share/pgpkeys/rrs.key projects/sysctl/share/pgpkeys/rstone.key projects/sysctl/share/pgpkeys/ru.key projects/sysctl/share/pgpkeys/rushani.key projects/sysctl/share/pgpkeys/ryusuke.key projects/sysctl/share/pgpkeys/sahil.key projects/sysctl/share/pgpkeys/sam.key projects/sysctl/share/pgpkeys/sanpei.key projects/sysctl/share/pgpkeys/sat.key projects/sysctl/share/pgpkeys/sbruno.key projects/sysctl/share/pgpkeys/sbz.key projects/sysctl/share/pgpkeys/scheidell.key projects/sysctl/share/pgpkeys/schweikh.key projects/sysctl/share/pgpkeys/scop.key projects/sysctl/share/pgpkeys/scottl.key projects/sysctl/share/pgpkeys/seanc.key projects/sysctl/share/pgpkeys/security-officer.key projects/sysctl/share/pgpkeys/sem.key projects/sysctl/share/pgpkeys/sephe.key projects/sysctl/share/pgpkeys/sepotvin.key projects/sysctl/share/pgpkeys/sergei.key projects/sysctl/share/pgpkeys/shaun.key projects/sysctl/share/pgpkeys/sheldonh.key projects/sysctl/share/pgpkeys/simon.key projects/sysctl/share/pgpkeys/sjg.key projects/sysctl/share/pgpkeys/skreuzer.key projects/sysctl/share/pgpkeys/snb.key projects/sysctl/share/pgpkeys/sobomax.key projects/sysctl/share/pgpkeys/sson.key projects/sysctl/share/pgpkeys/ssouhlal.key projects/sysctl/share/pgpkeys/stas.key projects/sysctl/share/pgpkeys/stefan.key projects/sysctl/share/pgpkeys/stefanf.key projects/sysctl/share/pgpkeys/stephane.key projects/sysctl/share/pgpkeys/stephen.key projects/sysctl/share/pgpkeys/sunpoet.key projects/sysctl/share/pgpkeys/swills.key projects/sysctl/share/pgpkeys/sylvio.key projects/sysctl/share/pgpkeys/syrinx.key projects/sysctl/share/pgpkeys/syuu.key projects/sysctl/share/pgpkeys/tabthorpe.key projects/sysctl/share/pgpkeys/taras.key projects/sysctl/share/pgpkeys/tdb.key projects/sysctl/share/pgpkeys/theraven.key projects/sysctl/share/pgpkeys/thierry.key projects/sysctl/share/pgpkeys/thomas.key projects/sysctl/share/pgpkeys/thompsa.key projects/sysctl/share/pgpkeys/tijl.key projects/sysctl/share/pgpkeys/timur.key projects/sysctl/share/pgpkeys/tj.key projects/sysctl/share/pgpkeys/tmclaugh.key projects/sysctl/share/pgpkeys/tmm.key projects/sysctl/share/pgpkeys/tmseck.key projects/sysctl/share/pgpkeys/tobez.key projects/sysctl/share/pgpkeys/tota.key projects/sysctl/share/pgpkeys/trasz.key projects/sysctl/share/pgpkeys/trevor.key projects/sysctl/share/pgpkeys/trhodes.key projects/sysctl/share/pgpkeys/tuexen.key projects/sysctl/share/pgpkeys/twinterg.key projects/sysctl/share/pgpkeys/ue.key projects/sysctl/share/pgpkeys/ume.key projects/sysctl/share/pgpkeys/ups.key projects/sysctl/share/pgpkeys/uqs.key projects/sysctl/share/pgpkeys/vanilla.key projects/sysctl/share/pgpkeys/vd.key projects/sysctl/share/pgpkeys/versus.key projects/sysctl/share/pgpkeys/viny.key projects/sysctl/share/pgpkeys/vkashyap.key projects/sysctl/share/pgpkeys/vs.key projects/sysctl/share/pgpkeys/vsevolod.key projects/sysctl/share/pgpkeys/wblock.key projects/sysctl/share/pgpkeys/wen.key projects/sysctl/share/pgpkeys/weongyo.key projects/sysctl/share/pgpkeys/wes.key projects/sysctl/share/pgpkeys/wg.key projects/sysctl/share/pgpkeys/wilko.key projects/sysctl/share/pgpkeys/will.key projects/sysctl/share/pgpkeys/wkoszek.key projects/sysctl/share/pgpkeys/wollman.key projects/sysctl/share/pgpkeys/wosch.key projects/sysctl/share/pgpkeys/wxs.key projects/sysctl/share/pgpkeys/xride.key projects/sysctl/share/pgpkeys/yoichi.key projects/sysctl/share/pgpkeys/yzlin.key projects/sysctl/share/pgpkeys/zack.key projects/sysctl/share/pgpkeys/zeising.key projects/sysctl/share/pgpkeys/zi.key projects/sysctl/share/pgpkeys/zml.key projects/sysctl/share/pgpkeys/zont.key projects/sysctl/share/tools/webupdate projects/sysctl/share/xml/advisories.xml projects/sysctl/share/xml/authors.ent projects/sysctl/share/xml/bibliography.xml projects/sysctl/share/xml/catalog.xml projects/sysctl/share/xml/commercial.consult.xml projects/sysctl/share/xml/commercial.hardware.xml projects/sysctl/share/xml/commercial.isp.xml projects/sysctl/share/xml/commercial.misc.xml projects/sysctl/share/xml/commercial.software.xml projects/sysctl/share/xml/events.dtd projects/sysctl/share/xml/events.xml projects/sysctl/share/xml/events2003.xml projects/sysctl/share/xml/events2004.xml projects/sysctl/share/xml/events2005.xml projects/sysctl/share/xml/events2006.xml projects/sysctl/share/xml/events2007.xml projects/sysctl/share/xml/events2008.xml projects/sysctl/share/xml/events2009.xml projects/sysctl/share/xml/events2010.xml projects/sysctl/share/xml/events2011.xml projects/sysctl/share/xml/events2012.xml projects/sysctl/share/xml/events2013.xml projects/sysctl/share/xml/freebsd.ent projects/sysctl/share/xml/freebsd.sch projects/sysctl/share/xml/gallery.dtd projects/sysctl/share/xml/ideas.dtd projects/sysctl/share/xml/libcommon.xsl projects/sysctl/share/xml/man-refs.ent projects/sysctl/share/xml/mirrors-master.xsl projects/sysctl/share/xml/mirrors.dtd projects/sysctl/share/xml/mirrors.xml projects/sysctl/share/xml/multimedia.dtd projects/sysctl/share/xml/navibar.ent projects/sysctl/share/xml/news.dtd projects/sysctl/share/xml/news.xml projects/sysctl/share/xml/notices.xml projects/sysctl/share/xml/press.dtd projects/sysctl/share/xml/press.xml projects/sysctl/share/xml/release.ent projects/sysctl/share/xml/sitemap.dtd projects/sysctl/share/xml/statusreport.dtd projects/sysctl/share/xml/templates.entries.xsl projects/sysctl/share/xml/templates.events.xsl projects/sysctl/share/xml/templates.events2ics.xsl projects/sysctl/share/xml/templates.news-rdf.xsl projects/sysctl/share/xml/templates.news-rss.xsl projects/sysctl/share/xml/templates.newsflash.xsl projects/sysctl/share/xml/templates.oldnewsflash.xsl projects/sysctl/share/xml/templates.oldpress.xsl projects/sysctl/share/xml/templates.pastevents.xsl projects/sysctl/share/xml/templates.press-rss.xsl projects/sysctl/share/xml/templates.press.xsl projects/sysctl/share/xml/templates.usergroups.xsl projects/sysctl/share/xml/trademarks.ent projects/sysctl/share/xml/usergroups.dtd projects/sysctl/share/xml/usergroups.xml projects/sysctl/share/xml/xhtml.xsl projects/sysctl/share/xml/xhtml10-freebsd.dtd projects/sysctl/share/xml/xslt10-freebsd.dtd projects/sysctl/sr_YU.ISO8859-2/share/xml/entities.ent projects/sysctl/tr_TR.ISO8859-9/articles/explaining-bsd/article.xml projects/sysctl/tr_TR.ISO8859-9/htdocs/index.xsl projects/sysctl/tr_TR.ISO8859-9/share/xml/catalog.xml projects/sysctl/tr_TR.ISO8859-9/share/xml/entities.ent projects/sysctl/tr_TR.ISO8859-9/share/xml/libcommon.xsl projects/sysctl/zh_TW.Big5/articles/contributing/article.xml projects/sysctl/zh_TW.Big5/articles/cvs-freebsd/article.xml projects/sysctl/zh_TW.Big5/articles/freebsd-questions/article.xml projects/sysctl/zh_TW.Big5/articles/hubs/article.xml projects/sysctl/zh_TW.Big5/articles/mailing-list-faq/article.xml projects/sysctl/zh_TW.Big5/articles/nanobsd/article.xml projects/sysctl/zh_TW.Big5/articles/pr-guidelines/article.xml projects/sysctl/zh_TW.Big5/articles/problem-reports/article.xml projects/sysctl/zh_TW.Big5/articles/remote-install/article.xml projects/sysctl/zh_TW.Big5/books/developers-handbook/Makefile projects/sysctl/zh_TW.Big5/books/developers-handbook/book.xml projects/sysctl/zh_TW.Big5/books/developers-handbook/chapters.ent projects/sysctl/zh_TW.Big5/books/developers-handbook/introduction/chapter.xml projects/sysctl/zh_TW.Big5/books/developers-handbook/ipv6/chapter.xml projects/sysctl/zh_TW.Big5/books/developers-handbook/kerneldebug/chapter.xml projects/sysctl/zh_TW.Big5/books/developers-handbook/l10n/chapter.xml projects/sysctl/zh_TW.Big5/books/developers-handbook/policies/chapter.xml projects/sysctl/zh_TW.Big5/books/developers-handbook/secure/chapter.xml projects/sysctl/zh_TW.Big5/books/developers-handbook/sockets/chapter.xml projects/sysctl/zh_TW.Big5/books/developers-handbook/testing/chapter.xml projects/sysctl/zh_TW.Big5/books/developers-handbook/tools/chapter.xml projects/sysctl/zh_TW.Big5/books/developers-handbook/x86/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/book.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/doc-build/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/examples/appendix.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/overview/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/psgml-mode/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/see-also/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/sgml-markup/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/sgml-primer/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/structure/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/stylesheets/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/the-website/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/tools/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/translations/chapter.xml projects/sysctl/zh_TW.Big5/books/fdp-primer/writing-style/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/Makefile projects/sysctl/zh_TW.Big5/books/handbook/advanced-networking/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/audit/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/basics/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/bibliography/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/book.xml projects/sysctl/zh_TW.Big5/books/handbook/boot/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/chapters.ent projects/sysctl/zh_TW.Big5/books/handbook/colophon.xml projects/sysctl/zh_TW.Big5/books/handbook/config/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/cutting-edge/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/desktop/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/disks/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/eresources/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/firewalls/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/geom/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/install/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/introduction/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/jails/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/kernelconfig/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/l10n/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/linuxemu/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/mac/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/mail/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/mirrors/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/multimedia/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/network-servers/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/pgpkeys/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/ports/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/ppp-and-slip/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/preface/preface.xml projects/sysctl/zh_TW.Big5/books/handbook/printing/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/security/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/serialcomms/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/users/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/vinum/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/virtualization/chapter.xml projects/sysctl/zh_TW.Big5/books/handbook/x11/chapter.xml projects/sysctl/zh_TW.Big5/books/porters-handbook/book.xml projects/sysctl/zh_TW.Big5/share/xml/authors.ent projects/sysctl/zh_TW.Big5/share/xml/catalog.xml projects/sysctl/zh_TW.Big5/share/xml/entities.ent projects/sysctl/zh_TW.Big5/share/xml/glossary.ent projects/sysctl/zh_TW.Big5/share/xml/mailing-lists.ent projects/sysctl/zh_TW.Big5/share/xml/trademarks.ent Directory Properties: projects/sysctl/README (props changed) projects/sysctl/da_DK.ISO8859-1/ (props changed) projects/sysctl/de_DE.ISO8859-1/ (props changed) projects/sysctl/el_GR.ISO8859-7/ (props changed) projects/sysctl/en_US.ISO8859-1/ (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/blocked.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/branches.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/bsdi-handbook.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/daemon-phk.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/done.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/fbsdcng-english.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/fbsdcng-japanese.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/fm-freebsd45.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/freebsd-basics-cover-front-145.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/freebsdro.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/frowny.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/how_to_contribute.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/in_progress.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/light_button.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/minigraph.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/news.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/not_planned.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/not_started.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/plain.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/project_goal.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/project_plan.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/resources_and_links.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/smiley.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/status_board.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/wr-bsdtool-june2001.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/wr-freebsd43.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/wr-freebsd44.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gifs/wr-handbook-2nd.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gnome/images/gnome.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gnome/images/ss224-1-tn.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gnome/images/ss224-1.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gnome/images/ss224-2-tn.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/gnome/images/ss224-2.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/ipv6/IPv6-badge-blue-128-trans.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/ipv6/IPv6-badge-blue-256-trans.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/ipv6/w6d-www-stats-large.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/ipv6/w6d-www-stats-v6-large.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/ipv6/w6d-www-stats-v6.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/ipv6/w6d-www-stats.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/layout/images/beastie.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/layout/images/blt_gry_arrow.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/layout/images/blt_red_arrow.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/layout/images/hdr_fill.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/layout/images/ico_rss.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/layout/images/logo-red.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/layout/images/logo.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/layout/images/nav_rgt.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/layout/images/nav_tbl_btm.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/layout/images/nav_tbl_top.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/logo/logo-basic-thumb.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/logo/logo-basic.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/logo/logo-bw-thumb.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/logo/logo-bw.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/logo/logo-full-thumb.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/logo/logo-full.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/logo/logo-reverse-thumb.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/logo/logo-reverse.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/logo/logo.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/platforms/ia64/i2inside.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/platforms/ia64/mckinley-die.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/platforms/ia64/merced-die.png (props changed) projects/sysctl/en_US.ISO8859-1/htdocs/platforms/ia64/montecito-die.png (props changed) projects/sysctl/es_ES.ISO8859-1/ (props changed) projects/sysctl/fr_FR.ISO8859-1/ (props changed) projects/sysctl/hu_HU.ISO8859-2/ (props changed) projects/sysctl/it_IT.ISO8859-15/ (props changed) projects/sysctl/ja_JP.eucJP/ (props changed) projects/sysctl/mn_MN.UTF-8/ (props changed) projects/sysctl/nl_NL.ISO8859-1/ (props changed) projects/sysctl/no_NO.ISO8859-1/ (props changed) projects/sysctl/pl_PL.ISO8859-2/ (props changed) projects/sysctl/pt_BR.ISO8859-1/ (props changed) projects/sysctl/release/ (props changed) projects/sysctl/ru_RU.KOI8-R/ (props changed) projects/sysctl/share/ (props changed) projects/sysctl/share/images/articles/console-server/tk0231-9-1.png (props changed) projects/sysctl/share/images/articles/gjournal-desktop/disklabel1.png (props changed) projects/sysctl/share/images/articles/gjournal-desktop/disklabel2.png (props changed) projects/sysctl/share/images/books/dev-model/branches.png (props changed) projects/sysctl/share/images/books/dev-model/freebsd-code-model.png (props changed) projects/sysctl/share/images/books/dev-model/hats-overview.png (props changed) projects/sysctl/share/images/books/dev-model/maintenance.png (props changed) projects/sysctl/share/images/books/dev-model/orghierarchy.png (props changed) projects/sysctl/share/images/books/dev-model/orghierarchy2.png (props changed) projects/sysctl/share/images/books/dev-model/portsstatus.png (props changed) projects/sysctl/share/images/books/dev-model/proc-add-committer.png (props changed) projects/sysctl/share/images/books/dev-model/proc-add-cvsup.png (props changed) projects/sysctl/share/images/books/dev-model/proc-commit.png (props changed) projects/sysctl/share/images/books/dev-model/proc-contrib.png (props changed) projects/sysctl/share/images/books/dev-model/proc-elections.png (props changed) projects/sysctl/share/images/books/dev-model/proc-pr.png (props changed) projects/sysctl/share/images/books/dev-model/proc-releng.png (props changed) projects/sysctl/share/images/books/dev-model/proc-rm-committer.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd1.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd10.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd11.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd12.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd13.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd2.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd3.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd4.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd5.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd6.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd7.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd8.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/parallels-freebsd9.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd1.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd10.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd11.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd12.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd13.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd2.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd3.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd4.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd5.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd6.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd7.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd8.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/virtualpc-freebsd9.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd01.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd02.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd03.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd04.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd05.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd06.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd07.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd08.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd09.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd10.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd11.png (props changed) projects/sysctl/share/images/books/handbook/virtualization/vmware-freebsd12.png (props changed) projects/sysctl/share/images/callouts/1.png (props changed) projects/sysctl/share/images/callouts/10.png (props changed) projects/sysctl/share/images/callouts/11.png (props changed) projects/sysctl/share/images/callouts/12.png (props changed) projects/sysctl/share/images/callouts/13.png (props changed) projects/sysctl/share/images/callouts/14.png (props changed) projects/sysctl/share/images/callouts/15.png (props changed) projects/sysctl/share/images/callouts/16.png (props changed) projects/sysctl/share/images/callouts/17.png (props changed) projects/sysctl/share/images/callouts/18.png (props changed) projects/sysctl/share/images/callouts/19.png (props changed) projects/sysctl/share/images/callouts/2.png (props changed) projects/sysctl/share/images/callouts/20.png (props changed) projects/sysctl/share/images/callouts/21.png (props changed) projects/sysctl/share/images/callouts/22.png (props changed) projects/sysctl/share/images/callouts/23.png (props changed) projects/sysctl/share/images/callouts/24.png (props changed) projects/sysctl/share/images/callouts/25.png (props changed) projects/sysctl/share/images/callouts/26.png (props changed) projects/sysctl/share/images/callouts/27.png (props changed) projects/sysctl/share/images/callouts/28.png (props changed) projects/sysctl/share/images/callouts/29.png (props changed) projects/sysctl/share/images/callouts/3.png (props changed) projects/sysctl/share/images/callouts/30.png (props changed) projects/sysctl/share/images/callouts/4.png (props changed) projects/sysctl/share/images/callouts/5.png (props changed) projects/sysctl/share/images/callouts/6.png (props changed) projects/sysctl/share/images/callouts/7.png (props changed) projects/sysctl/share/images/callouts/8.png (props changed) projects/sysctl/share/images/callouts/9.png (props changed) projects/sysctl/share/images/flyer/logo-full.png (props changed) projects/sysctl/share/openoffice/BSDi/Pictures/10000000000004220000031AEAC840AF.png (props changed) projects/sysctl/sr_YU.ISO8859-2/ (props changed) projects/sysctl/sr_YU.ISO8859-2/share/images/callouts/1.png (props changed) projects/sysctl/sr_YU.ISO8859-2/share/images/callouts/10.png (props changed) projects/sysctl/sr_YU.ISO8859-2/share/images/callouts/2.png (props changed) projects/sysctl/sr_YU.ISO8859-2/share/images/callouts/3.png (props changed) projects/sysctl/sr_YU.ISO8859-2/share/images/callouts/4.png (props changed) projects/sysctl/sr_YU.ISO8859-2/share/images/callouts/5.png (props changed) projects/sysctl/sr_YU.ISO8859-2/share/images/callouts/6.png (props changed) projects/sysctl/sr_YU.ISO8859-2/share/images/callouts/7.png (props changed) projects/sysctl/sr_YU.ISO8859-2/share/images/callouts/8.png (props changed) projects/sysctl/sr_YU.ISO8859-2/share/images/callouts/9.png (props changed) projects/sysctl/tr_TR.ISO8859-9/ (props changed) projects/sysctl/zh_TW.Big5/ (props changed) Modified: projects/sysctl/Makefile ============================================================================== --- projects/sysctl/Makefile Sat Nov 23 23:56:32 2013 (r43227) +++ projects/sysctl/Makefile Sun Nov 24 01:14:03 2013 (r43228) @@ -11,7 +11,7 @@ DOC_LANG= en_US.ISO8859-1 SUBDIR = ${DOC_LANG} .else SUBDIR = en_US.ISO8859-1 -SUBDIR+= bn_BD.ISO10646-1 +SUBDIR+= bn_BD.UTF-8 SUBDIR+= da_DK.ISO8859-1 SUBDIR+= de_DE.ISO8859-1 SUBDIR+= el_GR.ISO8859-7 @@ -27,13 +27,17 @@ SUBDIR+= pt_BR.ISO8859-1 SUBDIR+= ru_RU.KOI8-R SUBDIR+= sr_YU.ISO8859-2 SUBDIR+= tr_TR.ISO8859-9 -SUBDIR+= zh_CN.GB2312 +SUBDIR+= zh_CN.UTF-8 SUBDIR+= zh_TW.Big5 .endif DOC_PREFIX?= ${.CURDIR} +.if exists(/usr/bin/svnlite) +SVN?= /usr/bin/svnlite +.else SVN?= /usr/local/bin/svn +.endif update: .if !exists(${SVN}) Modified: projects/sysctl/da_DK.ISO8859-1/articles/ipsec-must/article.xml ============================================================================== --- projects/sysctl/da_DK.ISO8859-1/articles/ipsec-must/article.xml Sat Nov 23 23:56:32 2013 (r43227) +++ projects/sysctl/da_DK.ISO8859-1/articles/ipsec-must/article.xml Sun Nov 24 01:14:03 2013 (r43228) @@ -1,7 +1,6 @@ - - + - -
- - Uafhængig Verifikation af IPsec Funktionalitet i +<article xmlns="http://docbook.org/ns/docbook" xmlns:xlink="http://www.w3.org/1999/xlink" version="5.0" xml:lang="da"> + <info><title>Uafhængig Verifikation af IPsec Funktionalitet i &os; + - - David - Honig - - + DavidHonig
honig@sprynet.com
- - + 3 Maj 1999 - + &tm-attrib.freebsd; &tm-attrib.opengroup; &tm-attrib.general; @@ -41,9 +34,9 @@ hvordan ved du det? Jeg beskriver en metode til eksperimentalt at verificere at IPsec virker. - + - + Problemet Lad os antage, at du har @@ -55,7 +48,7 @@ uafhængigt? - + Løsningen Først, noget krypto-relevant teoretisk @@ -80,20 +73,19 @@ mode ikke var krypterede, som f.eks. den yderste IP header skal være, hvis pakken skal kunne routes. - + MUST Ueli Maurers Universal Statistical Test for Random - Bit Generators ( - MUST) måler hurtigt entropien + Bit Generators ( + MUST) måler hurtigt entropien af en stikprøve. Den bruger en kompressionsagtig algoritme. Forneden angives kildekoden til en variant der måler successive (~kvart megabyte) store bidder af en fil. - + Tcpdump Vi har også brug for en måde at opsamle de @@ -104,7 +96,7 @@ Kommandoen - tcpdump -c 4000 -s 10000 -w dumpfile.bin + tcpdump -c 4000 -s 10000 -w dumpfile.bin vil opfange 4000 rå pakker til dumpfile.bin. Op til 10.000 bytes @@ -112,7 +104,7 @@ - + Eksperimentet Her er eksperimentet: @@ -144,8 +136,8 @@ og den normale forbindelse har 29% (2.1) af den ventede værdi. - &prompt.user; tcpdump -c 4000 -s 10000 -w ipsecdemo.bin -&prompt.user; uliscan ipsecdemo.bin + &prompt.user; tcpdump -c 4000 -s 10000 -w ipsecdemo.bin +&prompt.user; uliscan ipsecdemo.bin Uliscan 21 Dec 98 L=8 256 258560 @@ -162,7 +154,7 @@ Expected value for L=8 is 7.1836656 - + Undtagelse Dette eksperiment viser at, IPsec kan @@ -176,7 +168,7 @@ Expected value for L=8 is 7.1836656 osv. Studér kildekoden; kend kildekoden. - + IPsec---Definition Internet Protokol sikkerheds udvidelser til IPv4; @@ -188,7 +180,7 @@ Expected value for L=8 is 7.1836656 besked. IPsec krypterer alting mellem to værter. - + Installering af IPsec De fleste af de moderne versioner af &os; har IPsec @@ -199,12 +191,11 @@ Expected value for L=8 is 7.1836656 &man.setkey.8; kommandoen. En udførlig guide om at køre IPsec på - &os; er tilrådighed i FreeBSD - Håndbogen. + &os; er tilrådighed i FreeBSD + Håndbogen. - + src/sys/i386/conf/KERNELNAME Dette skal være til stede i kernel konfig filen for at @@ -216,13 +207,12 @@ Expected value for L=8 is 7.1836656 device bpf - + Maurers universelle statistiske test (for blok størrelse=8 bits) - Du kan finde samme kode på - dette link. + Du kan finde samme kode på + dette link. /* ULISCAN.c ---blocksize of 8 Modified: projects/sysctl/da_DK.ISO8859-1/articles/pxe/article.xml ============================================================================== --- projects/sysctl/da_DK.ISO8859-1/articles/pxe/article.xml Sat Nov 23 23:56:32 2013 (r43227) +++ projects/sysctl/da_DK.ISO8859-1/articles/pxe/article.xml Sun Nov 24 01:14:03 2013 (r43228) @@ -1,7 +1,6 @@ - - + - -
- - FreeBSD kvikstart Guide +
+ FreeBSD kvikstart Guide + - - Alfred - Perlstein - - + AlfredPerlstein
alfred@FreeBSD.org
- - + - + &tm-attrib.freebsd; &tm-attrib.intel; &tm-attrib.general; @@ -42,9 +35,9 @@ &trans.da.jespersen; - + - + Introduktion @@ -91,15 +84,14 @@ interfacet til &intel; PXE (netboot) systemet. - + Server Konfiguration - Installér DHCP: Installér net/isc-dhcp3 du kan bruge denne - config fil - dhcpd.conf, put den ind i + Installér DHCP: Installér net/isc-dhcp3 du kan bruge denne + config fil + dhcpd.conf, put den ind i /usr/local/etc/. @@ -147,16 +139,15 @@ - + Bootstrap opsætning Download bootfiler: Download - - kern.flp og - mfsroot.flp floppy imagesne. + + kern.flp og + mfsroot.flp floppy imagesne. @@ -196,8 +187,7 @@ Lav en speciel loader.rc og installer det i /usr/tftpboot/boot/loader.rc så den - ikke prompter for den anden disk, her er min. + ikke prompter for den anden disk, her er min. @@ -216,8 +206,7 @@ Lav dit sysinstall script - install.cfg, du kan bruge mit som en skabelon, men du er + install.cfg, du kan bruge mit som en skabelon, men du er nød til at editere det. @@ -235,7 +224,7 @@ - + Installations opsætning @@ -274,11 +263,10 @@ RELNOTES.TXT compat1x doc - + Tilpasset Post-Install Pakke - Du kan bruge scriptet pkgmaker.sh til + Du kan bruge scriptet pkgmaker.sh til at lave en tilpasset pakke til post install. Ideen er at have den til at installere og konfigurere de specielle ting du vil have gjort. pkgmaker Køres i mappen @@ -292,8 +280,8 @@ RELNOTES.TXT compat1x doc pakke. Du vil også ønske dig at have nogle filer - kaldet pre og - post i den mappe, + kaldet pre og + post i den mappe, disse er shell scripts som du vil eksekverer før og efter din pakke er installeret. Modified: projects/sysctl/da_DK.ISO8859-1/share/xml/catalog.xml ============================================================================== --- projects/sysctl/da_DK.ISO8859-1/share/xml/catalog.xml Sat Nov 23 23:56:32 2013 (r43227) +++ projects/sysctl/da_DK.ISO8859-1/share/xml/catalog.xml Sun Nov 24 01:14:03 2013 (r43228) @@ -5,11 +5,26 @@ - - + + + + + + - DENNE DOKUMENTATION ER FORSYNET AF FREEBSD DOKUMENTATIONS + DENNE DOKUMENTATION ER FORSYNET AF FREEBSD DOKUMENTATIONS PROJEKTET "SOM DET ER" OG UDEN NOGLE UDTRYKTE ELLER ANTYDEDE GARANTIER, INKLUDERENDE MEN IKKE BEGRÆNSET TIL: ANTYDEDE GARANTIER FOR SALGBARHED OG EGNETHED FOR ET SPECIFIKT FORMÅL. UNDER INGEN Modified: projects/sysctl/da_DK.ISO8859-1/share/xml/entities.ent ============================================================================== --- projects/sysctl/da_DK.ISO8859-1/share/xml/entities.ent Sat Nov 23 23:56:32 2013 (r43227) +++ projects/sysctl/da_DK.ISO8859-1/share/xml/entities.ent Sun Nov 24 01:14:03 2013 (r43228) @@ -7,9 +7,6 @@ %translators; - -%l10n; %mailing-lists; Copied: projects/sysctl/da_DK.ISO8859-1/share/xml/freebsd-xhtml.xsl (from r43225, head/da_DK.ISO8859-1/share/xml/freebsd-xhtml.xsl) ============================================================================== --- /dev/null 00:00:00 1970 (empty, because file is newly added) +++ projects/sysctl/da_DK.ISO8859-1/share/xml/freebsd-xhtml.xsl Sun Nov 24 01:14:03 2013 (r43228, copy of r43225, head/da_DK.ISO8859-1/share/xml/freebsd-xhtml.xsl) @@ -0,0 +1,20 @@ + + + + + + + +

Dette og andre dokumenter kan downloades fra + ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/

+ +

For spørgsmål om FreeBSD, læs + documentationen før du kontakter + <questions@FreeBSD.org>.
+ For spørgsmål angående denne dokumentation, e-mail + <doc@FreeBSD.org>.

+ + Modified: projects/sysctl/da_DK.ISO8859-1/share/xml/mailing-lists.ent ============================================================================== --- projects/sysctl/da_DK.ISO8859-1/share/xml/mailing-lists.ent Sat Nov 23 23:56:32 2013 (r43227) +++ projects/sysctl/da_DK.ISO8859-1/share/xml/mailing-lists.ent Sun Nov 24 01:14:03 2013 (r43228) @@ -6,201 +6,201 @@ --> freebsd-advocacy@FreeBSD.org"> + freebsd-advocacy@FreeBSD.org"> freebsd-afs@FreeBSD.org"> + freebsd-afs@FreeBSD.org"> freebsd-aic7xxx@FreeBSD.org"> + freebsd-aic7xxx@FreeBSD.org"> freebsd-alpha@FreeBSD.org"> + freebsd-alpha@FreeBSD.org"> freebsd-announce@FreeBSD.org"> + freebsd-announce@FreeBSD.org"> freebsd-arch@FreeBSD.org"> + freebsd-arch@FreeBSD.org"> freebsd-arm@FreeBSD.org"> + freebsd-arm@FreeBSD.org"> freebsd-atm@FreeBSD.org"> + freebsd-atm@FreeBSD.org"> freebsd-audit@FreeBSD.org"> + freebsd-audit@FreeBSD.org"> freebsd-binup@FreeBSD.org"> + freebsd-binup@FreeBSD.org"> freebsd-bugbusters@FreeBSD.org"> + freebsd-bugbusters@FreeBSD.org"> freebsd-bugs@FreeBSD.org"> + freebsd-bugs@FreeBSD.org"> freebsd-chat@FreeBSD.org"> + freebsd-chat@FreeBSD.org"> freebsd-cluster@FreeBSD.org"> + freebsd-cluster@FreeBSD.org"> cvs-committers@FreeBSD.org"> + cvs-committers@FreeBSD.org"> freebsd-config@FreeBSD.org"> + freebsd-config@FreeBSD.org"> freebsd-core@FreeBSD.org"> + freebsd-core@FreeBSD.org"> freebsd-current@FreeBSD.org"> + freebsd-current@FreeBSD.org"> cvs-all@FreeBSD.org"> + cvs-all@FreeBSD.org"> freebsd-database@FreeBSD.org"> + freebsd-database@FreeBSD.org"> freebsd-developers@FreeBSD.org"> + freebsd-developers@FreeBSD.org"> freebsd-doc@FreeBSD.org"> + freebsd-doc@FreeBSD.org"> freebsd-emulation@FreeBSD.org"> + freebsd-emulation@FreeBSD.org"> freebsd-firewire@FreeBSD.org"> + freebsd-firewire@FreeBSD.org"> freebsd-fs@FreeBSD.org"> + freebsd-fs@FreeBSD.org"> freebsd-gnome@FreeBSD.org"> + freebsd-gnome@FreeBSD.org"> freebsd-hackers@FreeBSD.org"> + freebsd-hackers@FreeBSD.org"> freebsd-hardware@FreeBSD.org"> + freebsd-hardware@FreeBSD.org"> freebsd-hubs@FreeBSD.org"> + freebsd-hubs@FreeBSD.org"> freebsd-i18n@FreeBSD.org"> + freebsd-i18n@FreeBSD.org"> freebsd-ia64@FreeBSD.org"> + freebsd-ia64@FreeBSD.org"> freebsd-install@FreeBSD.org"> + freebsd-install@FreeBSD.org"> freebsd-ipfw@FreeBSD.org"> + freebsd-ipfw@FreeBSD.org"> freebsd-isdn@FreeBSD.org"> + freebsd-isdn@FreeBSD.org"> freebsd-isp@FreeBSD.org"> + freebsd-isp@FreeBSD.org"> freebsd-java@FreeBSD.org"> + freebsd-java@FreeBSD.org"> freebsd-jobs@FreeBSD.org"> + freebsd-jobs@FreeBSD.org"> freebsd-lfs@FreeBSD.org"> + freebsd-lfs@FreeBSD.org"> freebsd-libh@FreeBSD.org"> + freebsd-libh@FreeBSD.org"> freebsd-mips@FreeBSD.org"> + freebsd-mips@FreeBSD.org"> freebsd-mobile@FreeBSD.org"> + freebsd-mobile@FreeBSD.org"> freebsd-mozilla@FreeBSD.org"> + freebsd-mozilla@FreeBSD.org"> freebsd-multimedia@FreeBSD.org"> + freebsd-multimedia@FreeBSD.org"> freebsd-net@FreeBSD.org"> + freebsd-net@FreeBSD.org"> freebsd-newbies@FreeBSD.org"> + freebsd-newbies@FreeBSD.org"> new-bus-arch@bostonradio.org"> + new-bus-arch@bostonradio.org"> freebsd-platforms@FreeBSD.org"> + freebsd-platforms@FreeBSD.org"> freebsd-policy@FreeBSD.org"> + freebsd-policy@FreeBSD.org"> freebsd-ports@FreeBSD.org"> + freebsd-ports@FreeBSD.org"> freebsd-ppc@FreeBSD.org"> + freebsd-ppc@FreeBSD.org"> freebsd-qa@FreeBSD.org"> + freebsd-qa@FreeBSD.org"> freebsd-questions@FreeBSD.org"> + freebsd-questions@FreeBSD.org"> freebsd-realtime@FreeBSD.org"> + freebsd-realtime@FreeBSD.org"> freebsd-scsi@FreeBSD.org"> + freebsd-scsi@FreeBSD.org"> freebsd-security@FreeBSD.org"> + freebsd-security@FreeBSD.org"> freebsd-security-notifications@FreeBSD.org"> + freebsd-security-notifications@FreeBSD.org"> freebsd-small@FreeBSD.org"> + freebsd-small@FreeBSD.org"> freebsd-smp@FreeBSD.org"> + freebsd-smp@FreeBSD.org"> freebsd-sparc@FreeBSD.org"> + freebsd-sparc@FreeBSD.org"> freebsd-stable@FreeBSD.org"> + freebsd-stable@FreeBSD.org"> freebsd-standards@FreeBSD.org"> + freebsd-standards@FreeBSD.org"> freebsd-test@FreeBSD.org"> + freebsd-test@FreeBSD.org"> freebsd-tokenring@FreeBSD.org"> + freebsd-tokenring@FreeBSD.org"> freebsd-user-groups@FreeBSD.org"> + freebsd-user-groups@FreeBSD.org"> freebsd-vendors@FreeBSD.org"> + freebsd-vendors@FreeBSD.org"> freebsd-www@FreeBSD.org"> + freebsd-www@FreeBSD.org"> -majordomo@FreeBSD.org"> +majordomo@FreeBSD.org"> Modified: projects/sysctl/da_DK.ISO8859-1/share/xml/newsgroups.ent ============================================================================== --- projects/sysctl/da_DK.ISO8859-1/share/xml/newsgroups.ent Sat Nov 23 23:56:32 2013 (r43227) +++ projects/sysctl/da_DK.ISO8859-1/share/xml/newsgroups.ent Sun Nov 24 01:14:03 2013 (r43228) @@ -6,6 +6,6 @@ --> comp.unix.bsd.freebsd.misc + comp.unix.bsd.freebsd.misc nyhedsgruppen"> Modified: projects/sysctl/da_DK.ISO8859-1/share/xml/teams.ent ============================================================================== --- projects/sysctl/da_DK.ISO8859-1/share/xml/teams.ent Sat Nov 23 23:56:32 2013 (r43227) +++ projects/sysctl/da_DK.ISO8859-1/share/xml/teams.ent Sun Nov 24 01:14:03 2013 (r43228) @@ -18,18 +18,18 @@ $FreeBSD$ --> -core-secretary@FreeBSD.org"> +core-secretary@FreeBSD.org"> -cvs@FreeBSD.org"> +cvs@FreeBSD.org"> -faq@FreeBSD.org"> +faq@FreeBSD.org"> -portmgr@FreeBSD.org"> +portmgr@FreeBSD.org"> -re@FreeBSD.org"> +re@FreeBSD.org"> -donations@FreeBSD.org"> +donations@FreeBSD.org"> -security-officer@FreeBSD.org"> +security-officer@FreeBSD.org"> -www@FreeBSD.org"> +www@FreeBSD.org"> Modified: projects/sysctl/da_DK.ISO8859-1/share/xml/translators.ent ============================================================================== --- projects/sysctl/da_DK.ISO8859-1/share/xml/translators.ent Sat Nov 23 23:56:32 2013 (r43227) +++ projects/sysctl/da_DK.ISO8859-1/share/xml/translators.ent Sun Nov 24 01:14:03 2013 (r43228) @@ -9,9 +9,9 @@ --> Laust@doc.freebsd.dk"> + Laust@doc.freebsd.dk"> Dansk version af &a.da.jespersen;."> + "Dansk version af &a.da.jespersen;."> Modified: projects/sysctl/de_DE.ISO8859-1/articles/Makefile.inc ============================================================================== --- projects/sysctl/de_DE.ISO8859-1/articles/Makefile.inc Sat Nov 23 23:56:32 2013 (r43227) +++ projects/sysctl/de_DE.ISO8859-1/articles/Makefile.inc Sun Nov 24 01:14:03 2013 (r43228) @@ -8,4 +8,3 @@ # DESTDIR?= ${DOCDIR}/de_DE.ISO8859-1/articles/${.CURDIR:T} -COLLATEINDEX+=-s Symbole Modified: projects/sysctl/de_DE.ISO8859-1/articles/contributing-ports/article.xml ============================================================================== --- projects/sysctl/de_DE.ISO8859-1/articles/contributing-ports/article.xml Sat Nov 23 23:56:32 2013 (r43227) +++ projects/sysctl/de_DE.ISO8859-1/articles/contributing-ports/article.xml Sun Nov 24 01:14:03 2013 (r43228) @@ -1,7 +1,6 @@ - - + - -
- - Zur FreeBSD Ports-Sammlung beitragen +
+ Zur FreeBSD Ports-Sammlung beitragen + Dieser Artikel beschreibt, wie man zur FreeBSD @@ -22,17 +20,11 @@ - - Sam - Lawrance - - - Mark - Linimon - + SamLawrance + MarkLinimon - + &tm-attrib.freebsd; &tm-attrib.general; @@ -40,7 +32,7 @@ $FreeBSD$ $FreeBSD$ - + Ports, beitragen @@ -68,7 +60,7 @@ Fall in Ihre Entscheidung mit einbeziehen. - + Was Sie tun können, um uns zu helfen Um die Ports-Sammlung aktuell und in einem sauberen Zustand @@ -77,46 +69,41 @@ Finden Sie eine begehrte oder nützliche - Software und erstellen Sie einen + Software und erstellen Sie einen Port. Es gibt eine große Anzahl von Ports, die keinen - Maintainer haben. Werden Sie Maintainer und betreuen Sie einen Port. + Maintainer haben. Werden Sie Maintainer und betreuen Sie einen Port. Wenn Sie einen Port erstellt haben oder betreuen, - vergessen Sie nicht, welche Aufgaben ein Maintainer + vergessen Sie nicht, welche Aufgaben ein Maintainer hat. Wenn Sie nur eine kleine Aufgabe suchen, - könnten Sie beispielsweise einen Bug oder defekten + könnten Sie beispielsweise einen Bug oder defekten Port fixen. - + Erstellen Sie einen neuen Port Es gibt ein eigenes Handbuch, das beim Erstellen - (und Aktualisieren) von Ports hilft. Es heißt Porter-Handbuch. + (und Aktualisieren) von Ports hilft. Es heißt Porter-Handbuch. Das Porter-Handbuch ist die beste Referenz, um mit dem Ports-System zu arbeiten. Es enthält Details darüber, wie das Ports-System funktioniert und wie man mit/an den Ports arbeitet. - + Übernahme eines nicht betreuten Ports @@ -129,12 +116,11 @@ den Einstieg, einen verwaisten Port zu übernehmen, den Sie auch regelmässig selbst verwenden. - Nicht betreute Ports haben als MAINTAINER + Nicht betreute Ports haben als MAINTAINER den Wert ports@FreeBSD.org. Eine Liste der derzeit nicht betreuten Ports sowie Informationen zu deren - aktuellen Fehlern und Problemen können Sie unter - &os; Ports Monitoring System einsehen. + aktuellen Fehlern und Problemen können Sie unter + &os; Ports Monitoring System einsehen. Einige Ports beeinflussen durch Abhängigkeiten und Slave-Port-Beziehungen eine grosse @@ -160,14 +146,13 @@ Bitte vergewissern Sie sich, dass Sie die Aufgaben eines Maintainers verstanden haben. Lesen Sie bitte auch - das Porter-Handbuch. + das Porter-Handbuch. Übernehmen Sie nicht mehr Aufgaben, als Sie bewältigen können. Sie können einen nicht reservierten Port jederzeit übernehmen, die Entscheidung liegt bei Ihnen. Wenn - Sie dazu bereit sind, setzen Sie MAINTAINER + Sie dazu bereit sind, setzen Sie MAINTAINER auf Ihre E-Mail-Adresse und reichen einen Problembericht (PR) mit den von Ihnen vorgenommenen Änderungen ein. Wenn beim Kompilieren des Ports Fehler auftreten oder eine @@ -190,14 +175,14 @@ - + Die Herausforderung als Ports-Maintainer Dieser Abschnitt erklärt, warum Ports betreut werden müssen, und beschreibt die Pflichten eines Ports-Maintainers. - + Warum müssen Ports betreut werden? Einen Port zu erstellen ist eine einmalige Sache. @@ -316,8 +301,7 @@ Dieser Abschnitt bietet einen kurzen Überblick zu diesem Thema. Ausführliche Informationen zur - Aktualisierung von Ports finden Sie im Porter-Handbuch. + Aktualisierung von Ports finden Sie im Porter-Handbuch. @@ -406,7 +390,7 @@ besonders dann wichtig, wenn Ihre Aktualisierung die Shared Library-Version ändert; in diesem Fall werden Sie für die abhängigen Ports - einen PORTREVISION-Bump + einen PORTREVISION-Bump benötigen, damit diese von automatisierten Werkzeugen wie portmaster oder &man.portupgrade.1; auf dem neuesten Stand @@ -422,9 +406,8 @@ welcher die Änderungen erklärt und einen Patch enthält, der die Änderungen zwischen dem Original und Ihrer aktualisierten Version umfasst. - Lesen Sie bitte zuerst den Artikel Writing FreeBSD - Problem Reports, der das korrekte Einreichen + Lesen Sie bitte zuerst den Artikel Writing FreeBSD + Problem Reports, der das korrekte Einreichen von Problemberichten beschreibt. @@ -434,8 +417,7 @@ und Weise können Committer viel einfacher erkennen, welche Änderungen vorgenommen wurden. Das Porter-Handbuch enthält viele nützliche Informationen - zum Upgrading + zum Upgrading eines Ports. @@ -520,10 +502,8 @@ Achten Sie auf Build-Fehler Überprüfen Sie regelmäßig den Ports - Building Cluster pointyhat - und den Distfiles-Scanner, + Building Cluster pointyhat + und den Distfiles-Scanner, um festzustellen, ob einer Ihrer Ports nicht gebaut oder die Distfiles nicht geladen werden können (lesen Sie den Abschnitt Ressourcen @@ -636,9 +616,8 @@ Antworten Sie auf Bug-Reports - Bugs können Ihnen als E-Mail durch die - GNATS Problem Report database zugestellt + Bugs können Ihnen als E-Mail durch die + GNATS Problem Report database zugestellt werden, Sie können Ihnen aber auch direkt von Benutzern gemeldet werden. *** DIFF OUTPUT TRUNCATED AT 1000 LINES *** From owner-svn-doc-projects@FreeBSD.ORG Sun Nov 24 13:41:26 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id C384863B; Sun, 24 Nov 2013 13:41:26 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A44092189; Sun, 24 Nov 2013 13:41:26 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rAODfQFR011075; Sun, 24 Nov 2013 13:41:26 GMT (envelope-from bcr@svn.freebsd.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id rAODfQIt011074; Sun, 24 Nov 2013 13:41:26 GMT (envelope-from bcr@svn.freebsd.org) Message-Id: <201311241341.rAODfQIt011074@svn.freebsd.org> From: Benedict Reuschling Date: Sun, 24 Nov 2013 13:41:26 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43229 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2013 13:41:26 -0000 Author: bcr Date: Sun Nov 24 13:41:26 2013 New Revision: 43229 URL: http://svnweb.freebsd.org/changeset/doc/43229 Log: Add a section about reviewing the zpool history. With section id help from: gjb Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Sun Nov 24 01:14:03 2013 (r43228) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Sun Nov 24 13:41:26 2013 (r43229) @@ -688,6 +688,84 @@ errors: No known data errors + + Displaying recorded Pool history + + ZFS records all the commands that were issued to + administer the pool. These include the creation of datasets, + changing zfs properties or that a disk has been replaced in + the pool. This is useful to review how a pool was created and + which user did a specific action at what point in time. The + history is not kept in a log file, but is a part of the pool + itself. That is the reason why the history cannot be altered + after the fact unless the pool is destroyed. The command to + review this history is aptly named zpool + history: + + &prompt.root; zpool history +History for 'tank': +2013-02-26.23:02:35 zpool create tank mirror /dev/ada0 /dev/ada1 +2013-02-27.18:50:58 zfs set atime=off tank +2013-02-27.18:51:09 zfs set checksum=fletcher4 tank +2013-02-27.18:51:18 zfs create tank/backup + + The command output shows in it's basic form a timestamp + followed by each zpool or + zfs command that was executed on the pool. + Note that only commands that altered the pool in some way are + being recorded. Commands like zfs list are + not part of the history. When there is no pool name provided + for zpool history then the history of all + pools will be displayed. + + The zpool history can show even more + information when the options -i or + -l are provided. The option + -i displays user initiated events as well + as internally logged ZFS events. + + &prompt.root; zpool history -i +History for 'tank': +2013-02-26.23:02:35 [internal pool create txg:5] pool spa 28; zfs spa 28; zpl 5;uts 9.1-RELEASE 901000 amd64 +2013-02-27.18:50:53 [internal property set txg:50] atime=0 dataset = 21 +2013-02-27.18:50:58 zfs set atime=off tank +2013-02-27.18:51:04 [internal property set txg:53] checksum=7 dataset = 21 +2013-02-27.18:51:09 zfs set checksum=fletcher4 tank +2013-02-27.18:51:13 [internal create txg:55] dataset = 39 +2013-02-27.18:51:18 zfs create tank/backup + + The other more detailed history display can be invoked by + using the -l command. This will show the + log records in long format, which includes more information + like the user name who issued the command and the hostname on + which the change was made. + + &prompt.root; zpool history -l +History for 'tank': +2013-02-26.23:02:35 zpool create tank mirror /dev/ada0 /dev/ada1 [user 0 (root) on :global] +2013-02-27.18:50:58 zfs set atime=off tank [user 0 (root) on myzfsbox:global] +2013-02-27.18:51:09 zfs set checksum=fletcher4 tank [user 0 (root) on myzfsbox:global] +2013-02-27.18:51:18 zfs create tank/backup [user 0 (root) on myzfsbox:global] + + This output clearly shows that the root + user created the mirrored pool (consisting of + /dev/ada0 and + /dev/ada1). In addition to that, the + hostname (myzfsbox) is also shown in the + commands following the pool's creation. The hostname display + becomes important when the pool is exported from the current + and imported on another system. The commands that are issued + on the other system can clearly be distinguished by the + hostname that is recorded for each command. + + Both options to the zpool history + command can be combined together to give the most detailed + information possible for any given pool. The pool history can + become a valuable information source when tracking down what + actions were performed or when it is needed to provide more + detailed output for debugging a ZFS pool. + + Performance Monitoring From owner-svn-doc-projects@FreeBSD.ORG Sun Nov 24 19:02:23 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 73277FC1; Sun, 24 Nov 2013 19:02:23 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 622A22FE9; Sun, 24 Nov 2013 19:02:23 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rAOJ2N0k005773; Sun, 24 Nov 2013 19:02:23 GMT (envelope-from bcr@svn.freebsd.org) Received: (from bcr@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id rAOJ2Npp005770; Sun, 24 Nov 2013 19:02:23 GMT (envelope-from bcr@svn.freebsd.org) Message-Id: <201311241902.rAOJ2Npp005770@svn.freebsd.org> From: Benedict Reuschling Date: Sun, 24 Nov 2013 19:02:23 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43235 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2013 19:02:23 -0000 Author: bcr Date: Sun Nov 24 19:02:22 2013 New Revision: 43235 URL: http://svnweb.freebsd.org/changeset/doc/43235 Log: Correct some sentences (typos, wrong words). Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Sun Nov 24 18:59:24 2013 (r43234) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Sun Nov 24 19:02:22 2013 (r43235) @@ -893,7 +893,7 @@ data 288G 1.53T Creating & Destroying Volumes - A volume is special type of ZFS + A volume is a special type of ZFS dataset. Rather than being mounted as a file system, it is exposed as a block device under /dev/zvol/poolname/dataset. @@ -924,7 +924,7 @@ Filesystem Size Used Avail Cap Destroying a volume is much the same as destroying a regular filesystem dataset. The operation is nearly - instantaneous, but it make take several minutes for the free + instantaneous, but it may take several minutes for the free space to be reclaimed in the background. @@ -1054,7 +1054,7 @@ tank custom:costcenter - Dataset quotas can be used to restrict the amount of space - that can be consumed by a peticular dataset. Reference Quotas work in very much the same way, except they only count the space used by the dataset it self, excluding snapshots and child @@ -1329,17 +1329,17 @@ dedup = 1.05, compress = 1.11, copies = Delegated Administration ZFS features a comprehensive delegation system to assign - permissions to performs the various ZFS administration functions - to a regular user. For example, if each users' home directory - is a dataset, then each user could be delegated permission to - create and destroy snapshots of their home directory. A backup - user could be assigned the permissions required to make use of - the ZFS replication features without requiring root access, or - isolate a usage collection script to run as an unprivledged user - with access to only the space utilization data of all users. It - is even possible to delegate the ability to delegate - permissions. It is possible to delegate permissions over each - ZFS subcommand and most ZFS properties. + permissions to perform the various ZFS administration functions + to a regular (non-root) user. For example, if each users' home + directory is a dataset, then each user could be delegated + permission to create and destroy snapshots of their home + directory. A backup user could be assigned the permissions + required to make use of the ZFS replication features without + requiring root access, or isolate a usage collection script to + run as an unprivileged user with access to only the space + utilization data of all users. It is even possible to delegate + the ability to delegate permissions. ZFS allows to delegate + permissions over each subcommand and most ZFS properties. Delegating Dataset Creation @@ -1349,12 +1349,12 @@ dedup = 1.05, compress = 1.11, copies = mydataset command will give the indicated user the required permissions to create child datasets under the selected parent dataset. There is a - caveat, creating a new dataset involves mouting it, which - requires the vfs.usermount sysctl be + caveat: creating a new dataset involves mounting it, which + requires the vfs.usermount sysctl to be enabled in order to allow non-root users to mount a - filesystem. There is the further restriction that non-root - users must own the directory they are mounting the filesystem - to, in order to prevent abuse. + filesystem. There is another restriction that non-root users + must own the directory they are mounting the filesystem to, in + order to prevent abuse. From owner-svn-doc-projects@FreeBSD.ORG Sun Nov 24 23:53:50 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id CEBFA798; Sun, 24 Nov 2013 23:53:50 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BD4FD2D31; Sun, 24 Nov 2013 23:53:50 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rAONroub073314; Sun, 24 Nov 2013 23:53:50 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id rAONrovn073313; Sun, 24 Nov 2013 23:53:50 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201311242353.rAONrovn073313@svn.freebsd.org> From: Warren Block Date: Sun, 24 Nov 2013 23:53:50 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43238 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Nov 2013 23:53:51 -0000 Author: wblock Date: Sun Nov 24 23:53:50 2013 New Revision: 43238 URL: http://svnweb.freebsd.org/changeset/doc/43238 Log: Edit for clarity, spelling, and redundancy. Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Sun Nov 24 23:25:14 2013 (r43237) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Sun Nov 24 23:53:50 2013 (r43238) @@ -689,7 +689,7 @@ errors: No known data errors - Displaying recorded Pool history + Displaying Recorded Pool History ZFS records all the commands that were issued to administer the pool. These include the creation of datasets, @@ -709,13 +709,13 @@ History for 'tank': 2013-02-27.18:51:09 zfs set checksum=fletcher4 tank 2013-02-27.18:51:18 zfs create tank/backup - The command output shows in it's basic form a timestamp - followed by each zpool or - zfs command that was executed on the pool. + The output shows + zpool and + zfs commands that were executed on the pool along with a timestamp. Note that only commands that altered the pool in some way are being recorded. Commands like zfs list are not part of the history. When there is no pool name provided - for zpool history then the history of all + for zpool history, then the history of all pools will be displayed. The zpool history can show even more @@ -758,12 +758,12 @@ History for 'tank': on the other system can clearly be distinguished by the hostname that is recorded for each command. - Both options to the zpool history - command can be combined together to give the most detailed + Both options to zpool history + can be combined to give the most detailed information possible for any given pool. The pool history can - become a valuable information source when tracking down what - actions were performed or when it is needed to provide more - detailed output for debugging a ZFS pool. + be a valuable information source when tracking down what + actions were performed or when more + detailed output is needed for debugging a ZFS pool. @@ -974,9 +974,9 @@ Filesystem Size Used Avail Cap NAME PROPERTY VALUE SOURCE tank custom:costcenter 1234 local - To remove such a custom property again, use the - zfs inherit command with the - option. If the custom property is not + To remove such a custom property again, use + zfs inherit with + . If the custom property is not defined in any of the parent datasets, it will be removed completely (although the changes are still recorded in the pool's history). @@ -1057,7 +1057,7 @@ tank custom:costcenter - that can be consumed by a particular dataset. Reference Quotas work in very much the same way, except they only count the space used - by the dataset it self, excluding snapshots and child + by the dataset itself, excluding snapshots and child datasets. Similarly user and group quotas can be used @@ -1258,7 +1258,7 @@ for> done NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT pool 2.84G 20.9M 2.82G 0% 3.00x ONLINE - - The DEDUP column does now contain the + The DEDUP column now contains the value 3.00x. This indicates that ZFS detected the copies of the ports tree data and was able to deduplicate it at a ratio of 1/3. The space savings that this @@ -1269,8 +1269,7 @@ pool 2.84G 20.9M 2.82G 0% 3.00x ONLINE - there is not much redundant data on a ZFS pool. To see how much space could be saved by deduplication for a given set of data that is already stored in a pool, ZFS can simulate the - effects that deduplication would have. To do that, the - following command can be invoked on the pool. + effects that deduplication would have: &prompt.root; zdb -S pool Simulated DDT histogram: @@ -1293,9 +1292,9 @@ refcnt blocks LSIZE PSIZE DSIZE dedup = 1.05, compress = 1.11, copies = 1.00, dedup * compress / copies = 1.16 - After zdb -S finished analyzing the - pool, it outputs a summary that shows the ratio that would - result in activating deduplication. In this case, + After zdb -S finishes analyzing the + pool, it shows the space reduction ratio that would be achieved by + activating deduplication. In this case, 1.16 is a very poor rate that is mostly influenced by compression. Activating deduplication on this pool would not save any significant amount of space. Keeping @@ -1316,8 +1315,8 @@ dedup = 1.05, compress = 1.11, copies = ZFS dataset to a Jail. zfs jail jailid attaches a dataset - to the specified jail, and the zfs unjail - detaches it. In order for the dataset to be administered from + to the specified jail, and zfs unjail + detaches it. For the dataset to be administered from within a jail, the jailed property must be set. Once a dataset is jailed it can no longer be mounted on the host, because the jail administrator may have set @@ -1328,46 +1327,45 @@ dedup = 1.05, compress = 1.11, copies = Delegated Administration - ZFS features a comprehensive delegation system to assign - permissions to perform the various ZFS administration functions - to a regular (non-root) user. For example, if each users' home - directory is a dataset, then each user could be delegated + A comprehensive permission delegation system allows unprivileged + users to perform ZFS administration functions. + For example, if each user's home + directory is a dataset, users can be given permission to create and destroy snapshots of their home - directory. A backup user could be assigned the permissions - required to make use of the ZFS replication features without - requiring root access, or isolate a usage collection script to - run as an unprivileged user with access to only the space - utilization data of all users. It is even possible to delegate - the ability to delegate permissions. ZFS allows to delegate - permissions over each subcommand and most ZFS properties. + directories. A backup user can be given permission + to use ZFS replication features. + A usage statistics script can be allowed to + run with access only to the space + utilization data for all users. It is even possible to delegate + the ability to delegate permissions. Permission delegation is + possible for each subcommand and most ZFS properties. Delegating Dataset Creation - Using the zfs allow + zfs allow someuser create - mydataset command will - give the indicated user the required permissions to create + mydataset + gives the specified user permission to create child datasets under the selected parent dataset. There is a - caveat: creating a new dataset involves mounting it, which - requires the vfs.usermount sysctl to be - enabled in order to allow non-root users to mount a - filesystem. There is another restriction that non-root users - must own the directory they are mounting the filesystem to, in - order to prevent abuse. + caveat: creating a new dataset involves mounting it. + That requires setting the vfs.usermount &man.sysctl.8; to 1 + to allow non-root users to mount a + filesystem. There is another restriction aimed at preventing abuse: non-root users + must own the mountpoint where the file system is being mounted. Delegating Permission Delegation - Using the zfs allow + zfs allow someuser allow - mydataset command will - give the indicated user the ability to assign any permission + mydataset + gives the specified user the ability to assign any permission they have on the target dataset (or its children) to other users. If a user has the snapshot - permission and the allow permission that - user can then grant the snapshot permission to some other + permission and the allow permission, that + user can then grant the snapshot permission to some other users. @@ -1403,23 +1401,23 @@ dedup = 1.05, compress = 1.11, copies = ZFS on i386 Some of the features provided by ZFS - are RAM-intensive, so some tuning may be required to provide + are RAM-intensive, and may require tuning for maximum efficiency on systems with limited RAM. Memory - At a bare minimum, the total system memory should be at + As a bare minimum, the total system memory should be at least one gigabyte. The amount of recommended RAM depends upon the size of the pool and - the ZFS features which are used. A + which ZFS features are used. A general rule of thumb is 1 GB of RAM for every 1 TB of storage. If the deduplication feature is used, a general rule of thumb is 5 GB of RAM per TB of storage to be deduplicated. While some users successfully use ZFS with less RAM, - it is possible that when the system is under heavy load, it + systems under heavy load may panic due to memory exhaustion. Further tuning may be required for systems with less than the recommended RAM requirements. @@ -1429,19 +1427,19 @@ dedup = 1.05, compress = 1.11, copies = Kernel Configuration Due to the RAM limitations of the - &i386; platform, users using ZFS on the - &i386; architecture should add the following option to a + &i386; platform, ZFS users on the + &i386; architecture should add this option to a custom kernel configuration file, rebuild the kernel, and reboot: options KVA_PAGES=512 - This option expands the kernel address space, allowing + This expands the kernel address space, allowing the vm.kvm_size tunable to be pushed beyond the currently imposed limit of 1 GB, or the limit of 2 GB for PAE. To find the most suitable value for this option, divide the desired - address space in megabytes by four (4). In this example, it + address space in megabytes by four. In this example, it is 512 for 2 GB. @@ -1450,8 +1448,8 @@ dedup = 1.05, compress = 1.11, copies = The kmem address space can be increased on all &os; architectures. On a test system with - one gigabyte of physical memory, success was achieved with - the following options added to + 1 GB of physical memory, success was achieved with + these options added to /boot/loader.conf, and the system restarted: @@ -1638,12 +1636,12 @@ vfs.zfs.vdev.cache.size="5M"RAID-Z1 through RAID-Z3 based on the number of - parity devinces in the array and the number of - disks that the pool can operate without. + parity devices in the array and the number of + disks which can fail while the pool remains operational. In a RAID-Z1 configuration - with 4 disks, each 1 TB, usable storage will - be 3 TB and the pool will still be able to + with 4 disks, each 1 TB, usable storage is + 3 TB and the pool will still be able to operate in degraded mode with one faulted disk. If an additional disk goes offline before the faulted disk is replaced and resilvered, all data @@ -1663,7 +1661,7 @@ vfs.zfs.vdev.cache.size="5M"RAID-60 array. A RAID-Z group's storage capacity - is approximately the size of the smallest disk, + is approximately the size of the smallest disk multiplied by the number of non-parity disks. Four 1 TB disks in RAID-Z1 has an effective size of approximately 3 TB, @@ -1749,17 +1747,17 @@ vfs.zfs.vdev.cache.size="5M"L2ARC - The L2ARC is the second level + L2ARC is the second level of the ZFS caching system. The primary ARC is stored in - RAM, however since the amount of + RAM. Since the amount of available RAM is often limited, - ZFS can also make use of + ZFS can also use cache vdevs. Solid State Disks (SSDs) are often used as these cache devices due to their higher speed and lower latency compared to traditional spinning - disks. An L2ARC is entirely + disks. L2ARC is entirely optional, but having one will significantly increase read speeds for files that are cached on the SSD instead of having to be read from @@ -1789,7 +1787,7 @@ vfs.zfs.vdev.cache.size="5M"ZIL - The ZIL accelerates synchronous + ZIL accelerates synchronous transactions by using storage devices (such as SSDs) that are faster than those used for the main storage pool. When data is being written @@ -1809,11 +1807,11 @@ vfs.zfs.vdev.cache.size="5M"Copy-On-Write Unlike a traditional file system, when data is - overwritten on ZFS the new data is + overwritten on ZFS, the new data is written to a different block rather than overwriting the - old data in place. Only once this write is complete is - the metadata then updated to point to the new location - of the data. This means that in the event of a shorn + old data in place. Only when this write is complete is + the metadata then updated to point to the new location. + In the event of a shorn write (a system crash or power loss in the middle of writing a file), the entire original contents of the file are still available and the incomplete write is @@ -1825,23 +1823,23 @@ vfs.zfs.vdev.cache.size="5M" Dataset - Dataset is the generic term for a + Dataset is the generic term for a ZFS file system, volume, snapshot or - clone. Each dataset will have a unique name in the + clone. Each dataset has a unique name in the format: poolname/path@snapshot. The root of the pool is technically a dataset as well. Child datasets are named hierarchically like - directories; for example, + directories. For example, mypool/home, the home dataset, is a child of mypool and inherits properties from it. This can be expanded further by creating mypool/home/user. This grandchild dataset will inherity properties from the - parent and grandparent. It is also possible to set - properties on a child to override the defaults inherited + parent and grandparent. + Properties on a child can be set to override the defaults inherited from the parents and grandparents. - ZFS also allows administration of - datasets and their children to be delegated. @@ -1852,7 +1850,7 @@ vfs.zfs.vdev.cache.size="5M"ZFS file system is mounted somewhere in the systems directory heirarchy and contains files - and directories of its own with permissions, flags and + and directories of its own with permissions, flags, and other metadata. @@ -1903,7 +1901,7 @@ vfs.zfs.vdev.cache.size="5M"hold, once a snapshot is held, any attempt to destroy it will return - an EBUY error. Each snapshot can have multiple holds, + an EBUSY error. Each snapshot can have multiple holds, each with a unique name. The release command removes the hold so the snapshot can then be deleted. @@ -1924,12 +1922,12 @@ vfs.zfs.vdev.cache.size="5M"promoted, reversing - this dependeancy, making the clone the parent and the + this dependency, making the clone the parent and the previous parent the child. This operation requires no - additional space, however it will change the way the + additional space, but it will change the way the used space is accounted. @@ -1937,9 +1935,9 @@ vfs.zfs.vdev.cache.size="5M"Checksum Every block that is allocated is also checksummed - (the algorithm used is a per dataset property, see: - zfs set). ZFS - transparently validates the checksum of each block as it + (the algorithm used is a per dataset property, see + zfs set). The checksum of each block + is transparently validated as it is read, allowing ZFS to detect silent corruption. If the data that is read does not match the expected checksum, ZFS will @@ -1967,7 +1965,7 @@ vfs.zfs.vdev.cache.size="5M" + can be disabled, but it is inadvisable. @@ -1977,8 +1975,8 @@ vfs.zfs.vdev.cache.size="5M" Deduplication - ZFS has the ability to detect - duplicate blocks of data as they are written (thanks to - the checksumming feature). If deduplication is enabled, + Checksums make it possible to detect + duplicate blocks of data as they are written. + If deduplication is enabled, instead of writing the block a second time, the reference count of the existing block will be increased, saving storage space. To do this, @@ -2011,23 +2009,23 @@ vfs.zfs.vdev.cache.size="5M"ZFS and - the two blocks will be stored separately. Due to the - nature of the DDT, having to store + it is actually identical. If the data is not identical, the hash + collision will be noted and + the two blocks will be stored separately. Because + DDT must store the hash of each unique block, it consumes a very large amount of memory (a general rule of thumb is 5-6 GB of ram per 1 TB of deduplicated data). In situations where it is not practical to have enough RAM to keep the entire DDT in memory, performance will - suffer greatly as the DDT will need - to be read from disk before each new block is written. - Deduplication can make use of the + suffer greatly as the DDT must + be read from disk before each new block is written. + Deduplication can use L2ARC to store the DDT, providing a middle ground between fast system memory and slower disks. Consider - using ZFS compression instead, which + using compression instead, which often provides nearly as much space savings without the additional memory requirement. @@ -2035,17 +2033,17 @@ vfs.zfs.vdev.cache.size="5M" Scrub - In place of a consistency check like &man.fsck.8;, - ZFS has the scrub - command, which reads all data blocks stored on the pool - and verifies their checksums them against the known good + Instead of a consistency check like &man.fsck.8;, + ZFS has the scrub. + scrub reads all data blocks stored on the pool + and verifies their checksums against the known good checksums stored in the metadata. This periodic check of all the data stored on the pool ensures the recovery of any corrupted blocks before they are needed. A scrub is not required after an unclean shutdown, but it is recommended that you run a scrub at least once each - quarter. ZFS compares the checksum - for each block as it is read in the normal course of + quarter. Checksums + of each block are tested as they are read in normal use, but a scrub operation makes sure even infrequently used blocks are checked for silent corruption. @@ -2054,7 +2052,7 @@ vfs.zfs.vdev.cache.size="5M"Dataset Quota ZFS provides very fast and - accurate dataset, user and group space accounting in + accurate dataset, user, and group space accounting in addition to quotas and space reservations. This gives the administrator fine grained control over how space is allocated and allows critical file systems to reserve @@ -2087,8 +2085,8 @@ vfs.zfs.vdev.cache.size="5M" A reference quota limits the amount of space a - dataset can consume by enforcing a hard limit on the - space used. However, this hard limit includes only + dataset can consume by enforcing a hard limit. + However, this hard limit includes only space that the dataset references and does not include space used by descendants, such as file systems or snapshots. @@ -2115,10 +2113,10 @@ vfs.zfs.vdev.cache.size="5M" The reservation property makes - it possible to guaranteed a minimum amount of space for - the use of a specific dataset and its descendants. This + it possible to guarantee a minimum amount of space for + a specific dataset and its descendants. This means that if a 10 GB reservation is set on - storage/home/bob, if another + storage/home/bob, and another dataset tries to use all of the free space, at least 10 GB of space is reserved for this dataset. If a snapshot is taken of @@ -2127,7 +2125,7 @@ vfs.zfs.vdev.cache.size="5M"refreservation property works in a similar way, except it - excludes descendants, such as + excludes descendants like snapshots. Reservations of any sort are useful in many @@ -2143,11 +2141,11 @@ vfs.zfs.vdev.cache.size="5M" The refreservation property - makes it possible to guaranteed a minimum amount of + makes it possible to guarantee a minimum amount of space for the use of a specific dataset excluding its descendants. This means that if a 10 GB reservation is set on - storage/home/bob, if another + storage/home/bob, and another dataset tries to use all of the free space, at least 10 GB of space is reserved for this dataset. In contrast to a regular Resilver When a disk fails and must be replaced, the new - disk must be filled with the data that was lost. This - process of calculating and writing the missing data - (using the parity information distributed across the - remaining drives) to the new drive is called + disk must be filled with the data that was lost. The + process of using the parity information distributed across the remaining drives + to calculate and write the missing data to the new drive + is called resilvering. @@ -2194,7 +2192,7 @@ vfs.zfs.vdev.cache.size="5M"Faulted state. An administrator may choose to offline a disk in - preperation for replacing it, or to make it easier to + preparation for replacing it, or to make it easier to identify. @@ -2204,10 +2202,10 @@ vfs.zfs.vdev.cache.size="5M"A ZFS pool or vdev that is in the Degraded state has one or more disks that have been disconnected or have failed. The pool is - still usable however if additional devices fail the pool + still usable, however if additional devices fail, the pool could become unrecoverable. Reconnecting the missing - device(s) or replacing the failed disks will return the - pool to a Online state after the reconnected or new device has completed the Resilver @@ -2228,7 +2226,7 @@ vfs.zfs.vdev.cache.size="5M"Online state. If there is insufficient redundancy to compensate for the number of failed disks, then the contents of the pool - are lost and will need to be restored from + are lost and must be restored from backups. From owner-svn-doc-projects@FreeBSD.ORG Mon Nov 25 00:20:23 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D754BFD6; Mon, 25 Nov 2013 00:20:23 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C569D2E71; Mon, 25 Nov 2013 00:20:23 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rAP0KNC0084559; Mon, 25 Nov 2013 00:20:23 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id rAP0KNwr084558; Mon, 25 Nov 2013 00:20:23 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201311250020.rAP0KNwr084558@svn.freebsd.org> From: Warren Block Date: Mon, 25 Nov 2013 00:20:23 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43239 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 00:20:23 -0000 Author: wblock Date: Mon Nov 25 00:20:23 2013 New Revision: 43239 URL: http://svnweb.freebsd.org/changeset/doc/43239 Log: Whitespace-only fixes, translators please ignore. Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Sun Nov 24 23:53:50 2013 (r43238) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 00:20:23 2013 (r43239) @@ -4,9 +4,13 @@ $FreeBSD$ --> - + + The Z File System (<acronym>ZFS</acronym>) + @@ -54,15 +58,14 @@ - Data integrity: All data - includes a checksum of the data. When - data is written, the checksum is calculated and written along - with it. When that data is later read back, the - checksum is calculated again. If the checksums do not match, a - data error has been detected. ZFS will attempt to - automatically correct errors when data - redundancy is available. + Data integrity: All data includes a + checksum of the data. + When data is written, the checksum is calculated and written + along with it. When that data is later read back, the + checksum is calculated again. If the checksums do not match, + a data error has been detected. ZFS will + attempt to automatically correct errors when data redundancy + is available. @@ -73,13 +76,12 @@ - Performance: multiple - caching mechanisms provide increased performance. - ARC is an advanced - memory-based read cache. A second level of + Performance: multiple caching mechanisms provide increased + performance. ARC is an + advanced memory-based read cache. A second level of disk-based read cache can be added with - L2ARC, and disk-based synchronous - write cache is available with + L2ARC, and disk-based + synchronous write cache is available with ZIL. @@ -91,34 +93,33 @@ What Makes <acronym>ZFS</acronym> Different ZFS is significantly different from any - previous file system because it is more than just - a file system. Combining the - traditionally separate roles of volume manager and file system - provides ZFS with unique advantages. The file system is now - aware of the underlying structure of the disks. Traditional - file systems could only be created on a single disk at a time. - If there were two disks then two separate file systems would - have to be created. In a traditional hardware - RAID configuration, this problem was worked - around by presenting the operating system with a single logical - disk made up of the space provided by a number of disks, on top - of which the operating system placed its file system. Even in - the case of software RAID solutions like - GEOM, the UFS file system - living on top of the RAID transform believed - that it was dealing with a single device. - ZFS's combination of the volume manager and - the file system solves this and allows the creation of many file - systems all sharing a pool of available storage. One of the - biggest advantages to ZFS's awareness of the - physical layout of the disks is that ZFS can - grow the existing file systems automatically when additional - disks are added to the pool. This new space is then made - available to all of the file systems. ZFS - also has a number of different properties that can be applied to - each file system, creating many advantages to creating a number - of different filesystems and datasets rather than a single - monolithic filesystem. + previous file system because it is more than just a file system. + Combining the traditionally separate roles of volume manager and + file system provides ZFS with unique + advantages. The file system is now aware of the underlying + structure of the disks. Traditional file systems could only be + created on a single disk at a time. If there were two disks + then two separate file systems would have to be created. In a + traditional hardware RAID configuration, this + problem was worked around by presenting the operating system + with a single logical disk made up of the space provided by a + number of disks, on top of which the operating system placed its + file system. Even in the case of software + RAID solutions like GEOM, + the UFS file system living on top of the + RAID transform believed that it was dealing + with a single device. ZFS's combination of + the volume manager and the file system solves this and allows + the creation of many file systems all sharing a pool of + available storage. One of the biggest advantages to + ZFS's awareness of the physical layout of the + disks is that ZFS can grow the existing file + systems automatically when additional disks are added to the + pool. This new space is then made available to all of the file + systems. ZFS also has a number of different + properties that can be applied to each file system, creating + many advantages to creating a number of different filesystems + and datasets rather than a single monolithic filesystem. @@ -473,10 +474,10 @@ errors: No known data errors checksums disabled. There is also no noticeable performance gain from disabling these checksums. - - Checksum verification is known as scrubbing. - Verify the data integrity of the storage - pool, with this command: + + Checksum verification is known as + scrubbing. Verify the data integrity of the + storage pool, with this command: &prompt.root; zpool scrub storage @@ -699,9 +700,9 @@ errors: No known data errors history is not kept in a log file, but is a part of the pool itself. That is the reason why the history cannot be altered after the fact unless the pool is destroyed. The command to - review this history is aptly named zpool - history: - + review this history is aptly named + zpool history: + &prompt.root; zpool history History for 'tank': 2013-02-26.23:02:35 zpool create tank mirror /dev/ada0 /dev/ada1 @@ -709,13 +710,13 @@ History for 'tank': 2013-02-27.18:51:09 zfs set checksum=fletcher4 tank 2013-02-27.18:51:18 zfs create tank/backup - The output shows - zpool and - zfs commands that were executed on the pool along with a timestamp. - Note that only commands that altered the pool in some way are - being recorded. Commands like zfs list are - not part of the history. When there is no pool name provided - for zpool history, then the history of all + The output shows zpool and + zfs commands that were executed on the pool + along with a timestamp. Note that only commands that altered + the pool in some way are being recorded. Commands like + zfs list are not part of the history. When + there is no pool name provided for + zpool history, then the history of all pools will be displayed. The zpool history can show even more @@ -728,7 +729,7 @@ History for 'tank': History for 'tank': 2013-02-26.23:02:35 [internal pool create txg:5] pool spa 28; zfs spa 28; zpl 5;uts 9.1-RELEASE 901000 amd64 2013-02-27.18:50:53 [internal property set txg:50] atime=0 dataset = 21 -2013-02-27.18:50:58 zfs set atime=off tank +2013-02-27.18:50:58 zfs set atime=off tank 2013-02-27.18:51:04 [internal property set txg:53] checksum=7 dataset = 21 2013-02-27.18:51:09 zfs set checksum=fletcher4 tank 2013-02-27.18:51:13 [internal create txg:55] dataset = 39 @@ -795,16 +796,15 @@ data 288G 1.53T 2 11 second number on the command line after the interval to specify the total number of statistics to display. - Even more detailed pool I/O statistics can be - displayed with . In this case - each storage device in the pool will be shown with a - corresponding statistics line. This is helpful to - determine how many read and write operations are being - performed on each device, and can help determine if any - specific device is slowing down I/O on the entire pool. The - following example shows a mirrored pool consisting of two - devices. For each of these, a separate line is shown with - the current I/O activity. + Even more detailed pool I/O statistics can be displayed + with . In this case each storage device in + the pool will be shown with a corresponding statistics line. + This is helpful to determine how many read and write + operations are being performed on each device, and can help + determine if any specific device is slowing down I/O on the + entire pool. The following example shows a mirrored pool + consisting of two devices. For each of these, a separate line + is shown with the current I/O activity. &prompt.root; zpool iostat -v capacity operations bandwidth @@ -1119,8 +1119,8 @@ tank custom:costcenter - User quota properties are not displayed by zfs get all. - Non-root users can only see their own - quotas unless they have been granted the + Non-root users can + only see their own quotas unless they have been granted the userquota privilege. Users with this privilege are able to view and set everyone's quota. @@ -1141,11 +1141,12 @@ tank custom:costcenter - &prompt.root; zfs set groupquota@firstgroup=none As with the user quota property, - non-root users can only see the quotas - associated with the groups that they belong to. However, - root or a user with the - groupquota privilege can view and set all - quotas for all groups. + non-root users can + only see the quotas associated with the groups that they + belong to. However, + root or a user with + the groupquota privilege can view and set + all quotas for all groups. To display the amount of space consumed by each user on the specified filesystem or snapshot, along with any specified @@ -1155,8 +1156,8 @@ tank custom:costcenter - specific options, refer to &man.zfs.1;. Users with sufficient privileges and - root can list the quota for - storage/home/bob using: + root can list the + quota for storage/home/bob using: &prompt.root; zfs get quota storage/home/bob @@ -1259,7 +1260,7 @@ NAME SIZE ALLOC FREE CAP DEDUP HEALTH A pool 2.84G 20.9M 2.82G 0% 3.00x ONLINE - The DEDUP column now contains the - value 3.00x. This indicates that ZFS + value 3.00x. This indicates that ZFS detected the copies of the ports tree data and was able to deduplicate it at a ratio of 1/3. The space savings that this yields can be enormous, but only when there is enough memory @@ -1293,8 +1294,8 @@ refcnt blocks LSIZE PSIZE DSIZE dedup = 1.05, compress = 1.11, copies = 1.00, dedup * compress / copies = 1.16 After zdb -S finishes analyzing the - pool, it shows the space reduction ratio that would be achieved by - activating deduplication. In this case, + pool, it shows the space reduction ratio that would be + achieved by activating deduplication. In this case, 1.16 is a very poor rate that is mostly influenced by compression. Activating deduplication on this pool would not save any significant amount of space. Keeping @@ -1327,18 +1328,16 @@ dedup = 1.05, compress = 1.11, copies = Delegated Administration - A comprehensive permission delegation system allows unprivileged - users to perform ZFS administration functions. - For example, if each user's home - directory is a dataset, users can be given - permission to create and destroy snapshots of their home - directories. A backup user can be given permission - to use ZFS replication features. - A usage statistics script can be allowed to - run with access only to the space - utilization data for all users. It is even possible to delegate - the ability to delegate permissions. Permission delegation is - possible for each subcommand and most ZFS properties. + A comprehensive permission delegation system allows + unprivileged users to perform ZFS administration functions. For + example, if each user's home directory is a dataset, users can + be given permission to create and destroy snapshots of their + home directories. A backup user can be given permission to use + ZFS replication features. A usage statistics script can be + allowed to run with access only to the space utilization data + for all users. It is even possible to delegate the ability to + delegate permissions. Permission delegation is possible for + each subcommand and most ZFS properties. Delegating Dataset Creation @@ -1346,13 +1345,14 @@ dedup = 1.05, compress = 1.11, copies = zfs allow someuser create mydataset - gives the specified user permission to create - child datasets under the selected parent dataset. There is a - caveat: creating a new dataset involves mounting it. - That requires setting the vfs.usermount &man.sysctl.8; to 1 - to allow non-root users to mount a - filesystem. There is another restriction aimed at preventing abuse: non-root users - must own the mountpoint where the file system is being mounted. + gives the specified user permission to create child datasets + under the selected parent dataset. There is a caveat: + creating a new dataset involves mounting it. That requires + setting the vfs.usermount &man.sysctl.8; to + 1 to allow non-root users to mount a + filesystem. There is another restriction aimed at preventing + abuse: non-root users must own the mountpoint where the file + system is being mounted. @@ -1365,8 +1365,8 @@ dedup = 1.05, compress = 1.11, copies = they have on the target dataset (or its children) to other users. If a user has the snapshot permission and the allow permission, that - user can then grant the snapshot permission to some other - users. + user can then grant the snapshot permission + to some other users. @@ -1470,14 +1470,14 @@ vfs.zfs.vdev.cache.size="5M" - FreeBSD Wiki - - ZFS + FreeBSD + Wiki - ZFS FreeBSD Wiki - - ZFS Tuning + xlink:href="https://wiki.freebsd.org/ZFSTuningGuide">FreeBSD + Wiki - ZFS Tuning @@ -1489,8 +1489,7 @@ vfs.zfs.vdev.cache.size="5M" Oracle - Solaris ZFS Administration - Guide + Solaris ZFS Administration Guide @@ -1637,7 +1636,8 @@ vfs.zfs.vdev.cache.size="5M"RAID-Z1 through RAID-Z3 based on the number of parity devices in the array and the number of - disks which can fail while the pool remains operational. + disks which can fail while the pool remains + operational. In a RAID-Z1 configuration with 4 disks, each 1 TB, usable storage is @@ -1823,11 +1823,11 @@ vfs.zfs.vdev.cache.size="5M" Dataset - Dataset is the generic term for a - ZFS file system, volume, snapshot or - clone. Each dataset has a unique name in the - format: poolname/path@snapshot. The - root of the pool is technically a dataset as well. + Dataset is the generic term + for a ZFS file system, volume, + snapshot or clone. Each dataset has a unique name in + the format: poolname/path@snapshot. + The root of the pool is technically a dataset as well. Child datasets are named hierarchically like directories. For example, mypool/home, the home dataset, is a @@ -1835,12 +1835,11 @@ vfs.zfs.vdev.cache.size="5M"mypool/home/user. This grandchild dataset will inherity properties from the - parent and grandparent. - Properties on a child can be set to override the defaults inherited - from the parents and grandparents. - Administration of - datasets and their children can be delegated. + parent and grandparent. Properties on a child can be + set to override the defaults inherited from the parents + and grandparents. Administration of datasets and their + children can be + delegated. @@ -1901,8 +1900,8 @@ vfs.zfs.vdev.cache.size="5M"hold, once a snapshot is held, any attempt to destroy it will return - an EBUSY error. Each snapshot can have multiple holds, - each with a unique name. The + an EBUSY error. Each snapshot can + have multiple holds, each with a unique name. The release command removes the hold so the snapshot can then be deleted. Snapshots can be taken on volumes, however they can only @@ -1988,12 +1987,12 @@ vfs.zfs.vdev.cache.size="5M" - Deduplication + Deduplication - Checksums make it possible to detect - duplicate blocks of data as they are written. - If deduplication is enabled, - instead of writing the block a second time, the + Checksums make it possible to detect duplicate + blocks of data as they are written. If deduplication is + enabled, instead of writing the block a second time, the reference count of the existing block will be increased, saving storage space. To do this, ZFS keeps a deduplication table @@ -2009,25 +2008,23 @@ vfs.zfs.vdev.cache.size="5M"DDT must store - the hash of each unique block, it consumes a very large - amount of memory (a general rule of thumb is 5-6 GB - of ram per 1 TB of deduplicated data). In - situations where it is not practical to have enough + it is actually identical. If the data is not identical, + the hash collision will be noted and the two blocks will + be stored separately. Because DDT + must store the hash of each unique block, it consumes a + very large amount of memory (a general rule of thumb is + 5-6 GB of ram per 1 TB of deduplicated data). + In situations where it is not practical to have enough RAM to keep the entire DDT in memory, performance will - suffer greatly as the DDT must - be read from disk before each new block is written. - Deduplication can use - L2ARC to store the - DDT, providing a middle ground + suffer greatly as the DDT must be + read from disk before each new block is written. + Deduplication can use L2ARC to store + the DDT, providing a middle ground between fast system memory and slower disks. Consider - using compression instead, which - often provides nearly as much space savings without the - additional memory requirement. + using compression instead, which often provides nearly + as much space savings without the additional memory + requirement. @@ -2035,17 +2032,17 @@ vfs.zfs.vdev.cache.size="5M"Instead of a consistency check like &man.fsck.8;, ZFS has the scrub. - scrub reads all data blocks stored on the pool - and verifies their checksums against the known good - checksums stored in the metadata. This periodic check - of all the data stored on the pool ensures the recovery - of any corrupted blocks before they are needed. A scrub - is not required after an unclean shutdown, but it is - recommended that you run a scrub at least once each - quarter. Checksums - of each block are tested as they are read in normal - use, but a scrub operation makes sure even infrequently - used blocks are checked for silent corruption. + scrub reads all data blocks stored on + the pool and verifies their checksums against the known + good checksums stored in the metadata. This periodic + check of all the data stored on the pool ensures the + recovery of any corrupted blocks before they are needed. + A scrub is not required after an unclean shutdown, but + it is recommended that you run a scrub at least once + each quarter. Checksums of each block are tested as + they are read in normal use, but a scrub operation makes + sure even infrequently used blocks are checked for + silent corruption. @@ -2113,9 +2110,9 @@ vfs.zfs.vdev.cache.size="5M" The reservation property makes - it possible to guarantee a minimum amount of space for - a specific dataset and its descendants. This - means that if a 10 GB reservation is set on + it possible to guarantee a minimum amount of space for a + specific dataset and its descendants. This means that + if a 10 GB reservation is set on storage/home/bob, and another dataset tries to use all of the free space, at least 10 GB of space is reserved for this dataset. If a @@ -2167,9 +2164,9 @@ vfs.zfs.vdev.cache.size="5M"When a disk fails and must be replaced, the new disk must be filled with the data that was lost. The - process of using the parity information distributed across the remaining drives - to calculate and write the missing data to the new drive - is called + process of using the parity information distributed + across the remaining drives to calculate and write the + missing data to the new drive is called resilvering. @@ -2202,13 +2199,13 @@ vfs.zfs.vdev.cache.size="5M"A ZFS pool or vdev that is in the Degraded state has one or more disks that have been disconnected or have failed. The pool is - still usable, however if additional devices fail, the pool - could become unrecoverable. Reconnecting the missing - devices or replacing the failed disks will return the - pool to an Online state after - the reconnected or new device has completed the Resilver + still usable, however if additional devices fail, the + pool could become unrecoverable. Reconnecting the + missing devices or replacing the failed disks will + return the pool to an + Online state + after the reconnected or new device has completed the + Resilver process. @@ -2217,17 +2214,16 @@ vfs.zfs.vdev.cache.size="5M"A ZFS pool or vdev that is in the Faulted state is no longer - operational and the data residing on it can no longer - be accessed. A pool or vdev enters the + operational and the data residing on it can no longer be + accessed. A pool or vdev enters the Faulted state when the number of missing or failed devices exceeds the level of redundancy in the vdev. If missing devices can be - reconnected the pool will return to a Online state. If + reconnected the pool will return to a + Online state. If there is insufficient redundancy to compensate for the number of failed disks, then the contents of the pool - are lost and must be restored from - backups. + are lost and must be restored from backups. From owner-svn-doc-projects@FreeBSD.ORG Mon Nov 25 03:53:51 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2978C404; Mon, 25 Nov 2013 03:53:51 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 192C727D2; Mon, 25 Nov 2013 03:53:51 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rAP3ro4N057385; Mon, 25 Nov 2013 03:53:50 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id rAP3roPp057384; Mon, 25 Nov 2013 03:53:50 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201311250353.rAP3roPp057384@svn.freebsd.org> From: Warren Block Date: Mon, 25 Nov 2013 03:53:50 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43240 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 03:53:51 -0000 Author: wblock Date: Mon Nov 25 03:53:50 2013 New Revision: 43240 URL: http://svnweb.freebsd.org/changeset/doc/43240 Log: Change some tags to . Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 00:20:23 2013 (r43239) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 03:53:50 2013 (r43240) @@ -1342,9 +1342,9 @@ dedup = 1.05, compress = 1.11, copies = Delegating Dataset Creation - zfs allow + zfs allow someuser create - mydataset + mydataset gives the specified user permission to create child datasets under the selected parent dataset. There is a caveat: creating a new dataset involves mounting it. That requires @@ -1358,9 +1358,9 @@ dedup = 1.05, compress = 1.11, copies = Delegating Permission Delegation - zfs allow + zfs allow someuser allow - mydataset + mydataset gives the specified user the ability to assign any permission they have on the target dataset (or its children) to other users. If a user has the snapshot From owner-svn-doc-projects@FreeBSD.ORG Mon Nov 25 04:36:46 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 24ABF9F2; Mon, 25 Nov 2013 04:36:46 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 01BF12977; Mon, 25 Nov 2013 04:36:45 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rAP4ajBO071288; Mon, 25 Nov 2013 04:36:45 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id rAP4aji3071287; Mon, 25 Nov 2013 04:36:45 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201311250436.rAP4aji3071287@svn.freebsd.org> From: Warren Block Date: Mon, 25 Nov 2013 04:36:45 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43241 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 04:36:46 -0000 Author: wblock Date: Mon Nov 25 04:36:45 2013 New Revision: 43241 URL: http://svnweb.freebsd.org/changeset/doc/43241 Log: More whitespace fixes, translators please ignore. Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 03:53:50 2013 (r43240) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 04:36:45 2013 (r43241) @@ -303,9 +303,8 @@ example/data 17547008 0 175 &prompt.root; zfs create storage/home - Now compression and keeping extra - copies of directories and files can be enabled with these - commands: + Now compression and keeping extra copies of directories + and files can be enabled with these commands: &prompt.root; zfs set copies=2 storage/home &prompt.root; zfs set compression=gzip storage/home @@ -394,15 +393,15 @@ storage/home 26320512 0 26320512 &prompt.root; zpool status -x - If all pools are Online and everything is - normal, the message indicates that: + If all pools are + Online and everything + is normal, the message indicates that: all pools are healthy - If there is an issue, perhaps a disk is in the Offline state, the pool - state will look similar to: + If there is an issue, perhaps a disk is in the + Offline state, the + pool state will look similar to: pool: storage state: DEGRADED @@ -424,8 +423,7 @@ config: errors: No known data errors This indicates that the device was previously taken - offline by the administrator with this - command: + offline by the administrator with this command: &prompt.root; zpool offline storage da1 @@ -436,8 +434,8 @@ errors: No known data errors &prompt.root; zpool replace storage da1 From here, the status may be checked again, this time - without so that all pools - are shown: + without so that all pools are + shown: &prompt.root; zpool status storage pool: storage @@ -518,25 +516,25 @@ errors: No known data errors The administration of ZFS is divided between two main utilities. The zpool utility which controls the operation of the pool and deals with adding, removing, - replacing and managing disks, and the zfs utility, which - deals with creating, destroying and managing datasets (both - filesystems and volumes). + replacing and managing disks, and the + zfs utility, + which deals with creating, destroying and managing datasets + (both filesystems and + volumes). Creating & Destroying Storage Pools Creating a ZFS Storage Pool (zpool) involves making a number of decisions that are relatively - permanent because the structure of the pool cannot be - changed after the pool has been created. The most important - decision is what types of vdevs to group the physical disks - into. See the list of vdev types for details about - the possible options. After the pool has been created, most - vdev types do not allow additional disks to be added to the - vdev. The exceptions are mirrors, which allow additional + permanent because the structure of the pool cannot be changed + after the pool has been created. The most important decision + is what types of vdevs to group the physical disks into. See + the list of + vdev types for details + about the possible options. After the pool has been created, + most vdev types do not allow additional disks to be added to + the vdev. The exceptions are mirrors, which allow additional disks to be added to the vdev, and stripes, which can be upgraded to mirrors by attaching an additional disk to the vdev. Although additional vdevs can be added to a pool, the @@ -565,21 +563,20 @@ errors: No known data errors linkend="zfs-term-vdev">vdev types allow disks to be added to the vdev after creation. - When adding disks to the existing vdev is not - an option, as in the case of RAID-Z, the other option is - to add a vdev to the pool. It is possible, but - discouraged, to mix vdev types. ZFS stripes data across each - of the vdevs. For example, if there are two mirror vdevs, - then this is effectively a RAID 10, striping the writes across - the two sets of mirrors. Because of the way that space is - allocated in ZFS to attempt to have each vdev reach - 100% full at the same time, there is a performance penalty if - the vdevs have different amounts of free space. + When adding disks to the existing vdev is not an option, + as in the case of RAID-Z, the other option is to add a vdev to + the pool. It is possible, but discouraged, to mix vdev types. + ZFS stripes data across each of the vdevs. For example, if + there are two mirror vdevs, then this is effectively a RAID + 10, striping the writes across the two sets of mirrors. + Because of the way that space is allocated in ZFS to attempt + to have each vdev reach 100% full at the same time, there is a + performance penalty if the vdevs have different amounts of + free space. Currently, vdevs cannot be removed from a zpool, and disks can only be removed from a mirror if there is enough remaining redundancy. - @@ -601,23 +598,23 @@ errors: No known data errors Dealing with Failed Devices When a disk in a ZFS pool fails, the vdev that the disk - belongs to will enter the Degraded state. In this - state, all of the data stored on the vdev is still available, - but performance may be impacted because missing data will need - to be calculated from the available redundancy. To restore - the vdev to a fully functional state the failed physical - device will need to be replace replaced, and ZFS must be - instructed to begin the resilver operation, where - data that was on the failed device will be recalculated + belongs to will enter the + Degraded state. In + this state, all of the data stored on the vdev is still + available, but performance may be impacted because missing + data will need to be calculated from the available redundancy. + To restore the vdev to a fully functional state the failed + physical device will need to be replace replaced, and ZFS must + be instructed to begin the + resilver operation, + where data that was on the failed device will be recalculated from the available redundancy and written to the replacement device. Once this process has completed the vdev will return to Online status. If the vdev does not have any redundancy, or if multiple devices have failed and there is insufficient redundancy to - compensate, the pool will enter the Faulted state. If a + compensate, the pool will enter the + Faulted state. If a sufficient number of devices cannot be reconnected to the pool then the pool will be inoperative, and data will need to be restored from backups. @@ -629,14 +626,14 @@ errors: No known data errors The usable size of a redundant ZFS pool is limited by the size of the smallest device in the vdev. If each device in the vdev is replaced sequentially, after the smallest device - has completed the replace or resilver operation, the - pool can grow based on the size of the new smallest device. - This expansion can be triggered by using zpool - online with the parameter on - each device. After the expansion of each device, the - additional space will become available in the pool. + has completed the + replace or + resilver operation, + the pool can grow based on the size of the new smallest + device. This expansion can be triggered by using + zpool online with the + parameter on each device. After the expansion of each device, + the additional space will become available in the pool. @@ -759,26 +756,26 @@ History for 'tank': on the other system can clearly be distinguished by the hostname that is recorded for each command. - Both options to zpool history - can be combined to give the most detailed - information possible for any given pool. The pool history can - be a valuable information source when tracking down what - actions were performed or when more - detailed output is needed for debugging a ZFS pool. + Both options to zpool history can be + combined to give the most detailed information possible for + any given pool. The pool history can be a valuable + information source when tracking down what actions were + performed or when more detailed output is needed for debugging + a ZFS pool. Performance Monitoring ZFS has a built-in monitoring system that can display - statistics about I/O happening on the pool in real-time. - It shows the amount of free and used space on the pool, how - many read and write operations are being performed per second, - and how much I/O bandwidth is currently being utilized for - read and write operations. By default, all pools in the - system will be monitored and displayed. A pool name can be - provided as part of the command to monitor just that specific - pool. A basic example: + statistics about I/O happening on the pool in real-time. It + shows the amount of free and used space on the pool, how many + read and write operations are being performed per second, and + how much I/O bandwidth is currently being utilized for read + and write operations. By default, all pools in the system + will be monitored and displayed. A pool name can be provided + as part of the command to monitor just that specific pool. A + basic example: &prompt.root; zpool iostat capacity operations bandwidth @@ -790,11 +787,13 @@ data 288G 1.53T 2 11 number can be specified as the last parameter, indicating the frequency in seconds to wait between updates. ZFS will print the next statistic line after each interval. Press - CtrlC - to stop this continuous monitoring. Alternatively, give a - second number on the command line after the interval to - specify the total number of statistics to display. + + Ctrl + C + to stop this continuous monitoring. + Alternatively, give a second number on the command line after + the interval to specify the total number of statistics to + display. Even more detailed pool I/O statistics can be displayed with . In this case each storage device in @@ -850,22 +849,22 @@ data 288G 1.53T partitioned and assigned to a file system, there was no way to add an additional file system without adding a new disk. ZFS also allows you to set a number of - properties on each dataset. These properties - include features like compression, deduplication, caching and - quoteas, as well as other useful properties like readonly, - case sensitivity, network file sharing and mount point. Each - separate dataset can be administered, delegated, replicated, snapshoted, jailed, and destroyed as a unit. - This offers many advantages to creating a separate dataset for - each different type or set of files. The only drawback to - having an extremely large number of datasets, is that some - commands like zfs list will be slower, - and the mounting of an extremely large number of datasets - (100s or 1000s) can make the &os; boot process take + properties on each + dataset. These + properties include features like compression, deduplication, + caching and quoteas, as well as other useful properties like + readonly, case sensitivity, network file sharing and mount + point. Each separate dataset can be administered, + delegated, + replicated, + snapshoted, + jailed, and destroyed as a + unit. This offers many advantages to creating a separate + dataset for each different type or set of files. The only + drawback to having an extremely large number of datasets, is + that some commands like zfs list will be + slower, and the mounting of an extremely large number of + datasets (100s or 1000s) can make the &os; boot process take longer. Destroying a dataset is much quicker than deleting all @@ -878,8 +877,8 @@ data 288G 1.53T property, accessible with zpool get freeing poolname indicates how many datasets are having their blocks freed in the background. - If there are child datasets, such as snapshots or other + If there are child datasets, such as + snapshots or other datasets, then the parent cannot be destroyed. To destroy a dataset and all of its children, use the parameter to recursively destroy the dataset and all of its @@ -926,16 +925,15 @@ Filesystem Size Used Avail Cap regular filesystem dataset. The operation is nearly instantaneous, but it may take several minutes for the free space to be reclaimed in the background. - Renaming a Dataset - The name of a dataset can be changed using zfs - rename. The rename command can also be used to - change the parent of a dataset. Renaming a dataset to be - under a different parent dataset will change the value of + The name of a dataset can be changed using + zfs rename. The rename command can also be + used to change the parent of a dataset. Renaming a dataset to + be under a different parent dataset will change the value of those properties that are inherited by the child dataset. When a dataset is renamed, it is unmounted and then remounted in the new location (inherited from the parent dataset). This @@ -1004,12 +1002,12 @@ tank custom:costcenter - By default, snapshots are mounted in a hidden directory under the parent dataset: .zfs/snapshots/snapshotname. + class="directory">.zfs/snapshots/snapshotname. Individual files can easily be restored to a previous state by copying them from the snapshot back to the parent dataset. It is also possible to revert the entire dataset back to the - point-in-time of the snapshot using zfs - rollback. + point-in-time of the snapshot using + zfs rollback. Snapshots consume space based on how much the parent file system has changed since the time of the snapshot. The @@ -1018,7 +1016,7 @@ tank custom:costcenter - To destroy a snapshot and recover the space consumed by the overwritten or deleted files, run zfs destroy - dataset@snapshot. + dataset@snapshot. The parameter will recursively remove all snapshots with the same name under the parent dataset. Adding the parameters to the destroy command @@ -1035,12 +1033,12 @@ tank custom:costcenter - only, is mounted, and can have its own properties. Once a clone has been created, the snapshot it was created from cannot be destroyed. The child/parent relationship between - the clone and the snapshot can be reversed using zfs - promote. After a clone has been promoted, the - snapshot becomes a child of the clone, rather than of the - original parent dataset. This will change how the space is - accounted, but not actually change the amount of space - consumed. + the clone and the snapshot can be reversed using + zfs promote. After a clone has been + promoted, the snapshot becomes a child of the clone, rather + than of the original parent dataset. This will change how the + space is accounted, but not actually change the amount of + space consumed. @@ -1052,17 +1050,17 @@ tank custom:costcenter - Dataset, User and Group Quotas - Dataset - quotas can be used to restrict the amount of space - that can be consumed by a particular dataset. Reference Quotas work in - very much the same way, except they only count the space used - by the dataset itself, excluding snapshots and child - datasets. Similarly user and group quotas can be used - to prevent users or groups from consuming all of the available - space in the pool or dataset. + Dataset quotas can + be used to restrict the amount of space that can be consumed + by a particular dataset. + Reference Quotas work + in very much the same way, except they only count the space + used by the dataset itself, excluding snapshots and child + datasets. Similarly + user and + group quotas can be + used to prevent users or groups from consuming all of the + available space in the pool or dataset. To enforce a dataset quota of 10 GB for storage/home/bob, use the @@ -1167,11 +1165,10 @@ tank custom:costcenter - Reservations guarantee a minimum amount of space will always be available - to a dataset. The reserved space will not - be available to any other dataset. This feature can be - especially useful to ensure that users cannot comsume all of - the free space, leaving none for an important dataset or log - files. + to a dataset. The reserved space will not be available to any + other dataset. This feature can be especially useful to + ensure that users cannot comsume all of the free space, + leaving none for an important dataset or log files. The general format of the reservation property is @@ -1189,7 +1186,7 @@ tank custom:costcenter - The same principle can be applied to the refreservation property for setting a Reference - Reservation, with the general format + Reservation, with the general format refreservation=size. To check if any reservations or refreservations exist on @@ -1209,13 +1206,13 @@ tank custom:costcenter - Deduplication - When enabled, Deduplication uses - the checksum of each block to detect duplicate blocks. When a - new block is about to be written and it is determined to be a - duplicate of an existing block, rather than writing the same - data again, ZFS just references the - existing data on disk an additional time. This can offer + When enabled, + Deduplication + uses the checksum of each block to detect duplicate blocks. + When a new block is about to be written and it is determined + to be a duplicate of an existing block, rather than writing + the same data again, ZFS just references + the existing data on disk an additional time. This can offer tremendous space savings if your data contains many discreet copies of the file information. Deduplication requires an extremely large amount of memory, and most of the space @@ -1343,12 +1340,12 @@ dedup = 1.05, compress = 1.11, copies = Delegating Dataset Creation zfs allow - someuser create - mydataset - gives the specified user permission to create child datasets - under the selected parent dataset. There is a caveat: - creating a new dataset involves mounting it. That requires - setting the vfs.usermount &man.sysctl.8; to + someuser create + mydataset gives the + specified user permission to create child datasets under the + selected parent dataset. There is a caveat: creating a new + dataset involves mounting it. That requires setting the + vfs.usermount &man.sysctl.8; to 1 to allow non-root users to mount a filesystem. There is another restriction aimed at preventing abuse: non-root users must own the mountpoint where the file @@ -1359,14 +1356,14 @@ dedup = 1.05, compress = 1.11, copies = Delegating Permission Delegation zfs allow - someuser allow - mydataset - gives the specified user the ability to assign any permission - they have on the target dataset (or its children) to other - users. If a user has the snapshot - permission and the allow permission, that - user can then grant the snapshot permission - to some other users. + someuser allow + mydataset gives the + specified user the ability to assign any permission they have + on the target dataset (or its children) to other users. If a + user has the snapshot permission and the + allow permission, that user can then grant + the snapshot permission to some other + users. @@ -1401,8 +1398,8 @@ dedup = 1.05, compress = 1.11, copies = ZFS on i386 Some of the features provided by ZFS - are RAM-intensive, and may require tuning for - maximum efficiency on systems with limited + are RAM-intensive, and may require tuning for maximum + efficiency on systems with limited RAM. @@ -1411,16 +1408,15 @@ dedup = 1.05, compress = 1.11, copies = As a bare minimum, the total system memory should be at least one gigabyte. The amount of recommended RAM depends upon the size of the pool and - which ZFS features are used. A - general rule of thumb is 1 GB of RAM for every - 1 TB of storage. If the deduplication feature is used, - a general rule of thumb is 5 GB of RAM per TB of - storage to be deduplicated. While some users successfully - use ZFS with less RAM, - systems under heavy load - may panic due to memory exhaustion. Further tuning may be - required for systems with less than the recommended RAM - requirements. + which ZFS features are used. A general + rule of thumb is 1 GB of RAM for every 1 TB of + storage. If the deduplication feature is used, a general + rule of thumb is 5 GB of RAM per TB of storage to be + deduplicated. While some users successfully use + ZFS with less RAM, + systems under heavy load may panic due to memory exhaustion. + Further tuning may be required for systems with less than + the recommended RAM requirements. @@ -1686,7 +1682,7 @@ vfs.zfs.vdev.cache.size="5M"Log - ZFS Log Devices, also known as ZFS Intent Log (ZIL) + linkend="zfs-term-zil">ZIL) move the intent log from the regular pool devices to a dedicated device, typically an SSD. Having a dedicated log @@ -1703,7 +1699,7 @@ vfs.zfs.vdev.cache.size="5M"Cache - Adding a cache vdev to a zpool will add the storage of the cache to the L2ARC. + linkend="zfs-term-l2arc">L2ARC. Cache devices cannot be mirrored. Since a cache device only stores additional copies of existing data, there is no risk of data loss. @@ -1870,9 +1866,9 @@ vfs.zfs.vdev.cache.size="5M" Snapshot - The copy-on-write - (COW) design of + The + copy-on-write + (COW) design of ZFS allows for nearly instantaneous consistent snapshots with arbitrary names. After taking a snapshot of a dataset (or a recursive snapshot of a @@ -1974,11 +1970,10 @@ vfs.zfs.vdev.cache.size="5M" LZ4 compression is only @@ -2082,11 +2077,10 @@ vfs.zfs.vdev.cache.size="5M" A reference quota limits the amount of space a - dataset can consume by enforcing a hard limit. - However, this hard limit includes only - space that the dataset references and does not include - space used by descendants, such as file systems or - snapshots. + dataset can consume by enforcing a hard limit. However, + this hard limit includes only space that the dataset + references and does not include space used by + descendants, such as file systems or snapshots. @@ -2145,8 +2139,8 @@ vfs.zfs.vdev.cache.size="5M"storage/home/bob, and another dataset tries to use all of the free space, at least 10 GB of space is reserved for this dataset. In - contrast to a regular reservation, + contrast to a regular + reservation, space used by snapshots and decendant datasets is not counted against the reservation. As an example, if a snapshot was taken of @@ -2186,9 +2180,9 @@ vfs.zfs.vdev.cache.size="5M"Individual devices can be put in an Offline state by the administrator if there is sufficient redundancy to avoid putting the pool - or vdev into a Faulted state. An - administrator may choose to offline a disk in + or vdev into a + Faulted state. + An administrator may choose to offline a disk in preparation for replacing it, or to make it easier to identify. From owner-svn-doc-projects@FreeBSD.ORG Mon Nov 25 05:58:08 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 7788142F; Mon, 25 Nov 2013 05:58:08 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 66C432C78; Mon, 25 Nov 2013 05:58:08 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rAP5w8UZ097855; Mon, 25 Nov 2013 05:58:08 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id rAP5w8LT097854; Mon, 25 Nov 2013 05:58:08 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201311250558.rAP5w8LT097854@svn.freebsd.org> From: Warren Block Date: Mon, 25 Nov 2013 05:58:08 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43242 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 05:58:08 -0000 Author: wblock Date: Mon Nov 25 05:58:08 2013 New Revision: 43242 URL: http://svnweb.freebsd.org/changeset/doc/43242 Log: Edits for clarity and simplicity. Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 04:36:45 2013 (r43241) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 05:58:08 2013 (r43242) @@ -545,16 +545,16 @@ errors: No known data errors A ZFS pool that is no longer needed can be destroyed so that the disks making up the pool can be reused in another pool or for other purposes. Destroying a pool involves - unmouting all of the datasets in that pool. If the datasets + unmounting all of the datasets in that pool. If the datasets are in use, the unmount operation will fail and the pool will not be destroyed. The destruction of the pool can be forced - with the parameter, however this can cause - undefined behavior in the applications which had open files on + with , but this can cause + undefined behavior in applications which had open files on those datasets. - Adding & Removing Devices + Adding and Removing Devices Adding disks to a zpool can be broken down into two separate cases: attaching a disk to an existing vdev with @@ -567,9 +567,9 @@ errors: No known data errors as in the case of RAID-Z, the other option is to add a vdev to the pool. It is possible, but discouraged, to mix vdev types. ZFS stripes data across each of the vdevs. For example, if - there are two mirror vdevs, then this is effectively a RAID + there are two mirror vdevs, then this is effectively a RAID 10, striping the writes across the two sets of mirrors. - Because of the way that space is allocated in ZFS to attempt + Because of the way that space is allocated in ZFS to attempt to have each vdev reach 100% full at the same time, there is a performance penalty if the vdevs have different amounts of free space. @@ -603,20 +603,20 @@ errors: No known data errors this state, all of the data stored on the vdev is still available, but performance may be impacted because missing data will need to be calculated from the available redundancy. - To restore the vdev to a fully functional state the failed - physical device will need to be replace replaced, and ZFS must + To restore the vdev to a fully functional state, the failed + physical device must be replaced, and ZFS must be instructed to begin the resilver operation, where data that was on the failed device will be recalculated - from the available redundancy and written to the replacement - device. Once this process has completed the vdev will return + from available redundancy and written to the replacement + device. After the process has completed, the vdev will return to Online status. If the vdev does not have any redundancy, or if multiple devices - have failed and there is insufficient redundancy to + have failed and there is not enough redundancy to compensate, the pool will enter the Faulted state. If a sufficient number of devices cannot be reconnected to the pool - then the pool will be inoperative, and data will need to be + then the pool will be inoperative, and data must be restored from backups. @@ -631,9 +631,9 @@ errors: No known data errors resilver operation, the pool can grow based on the size of the new smallest device. This expansion can be triggered by using - zpool online with the - parameter on each device. After the expansion of each device, - the additional space will become available in the pool. + zpool online with + on each device. After expansion of all devices, + the additional space will become available to the pool. @@ -689,13 +689,13 @@ errors: No known data errors Displaying Recorded Pool History - ZFS records all the commands that were issued to + ZFS records all the commands that were issued to administer the pool. These include the creation of datasets, - changing zfs properties or that a disk has been replaced in - the pool. This is useful to review how a pool was created and - which user did a specific action at what point in time. The - history is not kept in a log file, but is a part of the pool - itself. That is the reason why the history cannot be altered + changing properties, or when a disk has been replaced in + the pool. This history is useful for reviewing how a pool was created and + which user did a specific action and when. + History is not kept in a log file, but is a part of the pool + itself. Because of that, history cannot be altered after the fact unless the pool is destroyed. The command to review this history is aptly named zpool history: @@ -709,18 +709,18 @@ History for 'tank': The output shows zpool and zfs commands that were executed on the pool - along with a timestamp. Note that only commands that altered - the pool in some way are being recorded. Commands like - zfs list are not part of the history. When - there is no pool name provided for - zpool history, then the history of all - pools will be displayed. + along with a timestamp. Only commands that alter + the pool in some way are recorded. Commands like + zfs list are not included. When + no pool name is given to + zpool history, the history of all + pools is displayed. - The zpool history can show even more + zpool history can show even more information when the options -i or -l are provided. The option -i displays user initiated events as well - as internally logged ZFS events. + as internally logged ZFS events. &prompt.root; zpool history -i History for 'tank': @@ -732,10 +732,10 @@ History for 'tank': 2013-02-27.18:51:13 [internal create txg:55] dataset = 39 2013-02-27.18:51:18 zfs create tank/backup - The other more detailed history display can be invoked by - using the -l command. This will show the - log records in long format, which includes more information - like the user name who issued the command and the hostname on + A more-detailed history is invoked by + adding -l. + Log records are shown in long format, including information + like the name of the user who issued the command and the hostname on which the change was made. &prompt.root; zpool history -l @@ -758,23 +758,22 @@ History for 'tank': Both options to zpool history can be combined to give the most detailed information possible for - any given pool. The pool history can be a valuable - information source when tracking down what actions were - performed or when more detailed output is needed for debugging - a ZFS pool. + any given pool. Pool history provides valuable + information when tracking down what actions were + performed or when more detailed output is needed for debugging. Performance Monitoring - ZFS has a built-in monitoring system that can display - statistics about I/O happening on the pool in real-time. It + A built-in monitoring system can display + statistics about I/O on the pool in real-time. It shows the amount of free and used space on the pool, how many read and write operations are being performed per second, and - how much I/O bandwidth is currently being utilized for read - and write operations. By default, all pools in the system - will be monitored and displayed. A pool name can be provided - as part of the command to monitor just that specific pool. A + how much I/O bandwidth is currently being utilized. + By default, all pools in the system + are monitored and displayed. A pool name can be provided + to limit monitoring to just that pool. A basic example: &prompt.root; zpool iostat @@ -785,8 +784,8 @@ data 288G 1.53T 2 11 To continuously monitor I/O activity on the pool, a number can be specified as the last parameter, indicating - the frequency in seconds to wait between updates. ZFS will - print the next statistic line after each interval. Press + the frequency in seconds to wait between updates. + The next statistic line is printed after each interval. Press Ctrl C @@ -796,14 +795,13 @@ data 288G 1.53T 2 11 display. Even more detailed pool I/O statistics can be displayed - with . In this case each storage device in - the pool will be shown with a corresponding statistics line. - This is helpful to determine how many read and write + with . Each device in + the pool is shown with a statistics line. + This is useful in seeing how many read and write operations are being performed on each device, and can help - determine if any specific device is slowing down I/O on the - entire pool. The following example shows a mirrored pool - consisting of two devices. For each of these, a separate line - is shown with the current I/O activity. + determine if any individual device is slowing down the + pool. This example shows a mirrored pool + consisting of two devices: &prompt.root; zpool iostat -v capacity operations bandwidth @@ -819,13 +817,13 @@ data 288G 1.53T Splitting a Storage Pool - A ZFS pool consisting of one or more mirror vdevs can be + A pool consisting of one or more mirror vdevs can be split into a second pool. The last member of each mirror (unless otherwise specified) is detached and used to create a new pool containing the same data. It is recommended that the operation first be attempted with the - parameter. This will print out the details of the proposed - operation without actually performancing it. This helps + parameter. The details of the proposed + operation are displayed without actually performing it. This helps ensure the operation will happen as expected. @@ -842,55 +840,53 @@ data 288G 1.53T Creating & Destroying Datasets - Unlike with traditional disks and volume managers, space - in ZFS is not preallocated, allowing - additional file systems to be created at any time. With - traditional file systems, once all of the space was - partitioned and assigned to a file system, there was no way to + Unlike traditional disks and volume managers, space + in ZFS is not preallocated. + Wtraditional file systems, once all of the space was + partitioned and assigned, there was no way to add an additional file system without adding a new disk. - ZFS also allows you to set a number of - properties on each - dataset. These - properties include features like compression, deduplication, + With ZFS, new file systems can be created at any time. + Each + dataset has + properties including features like compression, deduplication, caching and quoteas, as well as other useful properties like - readonly, case sensitivity, network file sharing and mount + readonly, case sensitivity, network file sharing, and a mount point. Each separate dataset can be administered, delegated, replicated, snapshoted, jailed, and destroyed as a - unit. This offers many advantages to creating a separate + unit. There are many advantages to creating a separate dataset for each different type or set of files. The only - drawback to having an extremely large number of datasets, is + drawbacks to having an extremely large number of datasets is that some commands like zfs list will be - slower, and the mounting of an extremely large number of - datasets (100s or 1000s) can make the &os; boot process take - longer. + slower, and the mounting of hundreds or even thousands of + datasets can slow the &os; boot process. Destroying a dataset is much quicker than deleting all of the files that reside on the dataset, as it does not invole scanning all of the files and updating all of the corresponding metadata. In modern versions of - ZFS the zfs destroy - operation is asynchronous, the free space may take several + ZFS, zfs destroy + is asynchronous, and the free space may take several minutes to appear in the pool. The freeing property, accessible with zpool get freeing poolname indicates how many datasets are having their blocks freed in the background. - If there are child datasets, such as + If there are child datasets, like snapshots or other datasets, then the parent cannot be destroyed. To destroy a - dataset and all of its children, use the - parameter to recursively destroy the dataset and all of its - children. The parameters can be used - to not actually perform the destruction, but instead list - which datasets and snapshots would be destroyed and in the + dataset and all of its children, use + to recursively destroy the dataset and all of its + children. can be used + to list + datasets and snapshots that would be destroyed and, in the case of snapshots, how much space would be reclaimed by - proceeding with the destruction. + the actual destruction. - Creating & Destroying Volumes + Creating and Destroying Volumes A volume is a special type of ZFS dataset. Rather than being mounted as a file system, it is @@ -898,15 +894,15 @@ data 288G 1.53T /dev/zvol/poolname/dataset. This allows the volume to be used for other file systems, to back the disks of a virtual machine, or to be exported using - protocols like iSCSI or HAST. + protocols like iSCSI or HAST. - A volume can be formatted with any filesystem on top of - it. This will appear to the user as if they are working with - a regular disk using that specific filesystem and not ZFS. - In this way, non-ZFS file systems can be augmented with - ZFS features that they would not normally have. For example, - combining the ZFS compression property together with a - 250 MB volume allows creation of a compressed FAT + A volume can be formatted with any file system. + To the user, it will appear as if they are working with + a regular disk using that specific filesystem and not ZFS. + Putting ordinary file systems on + ZFS volumes provides features those file systems would not normally have. For example, + using the compression property on a + 250 MB volume allows creation of a compressed FAT filesystem. &prompt.root; zfs create -V 250m -o compression=on tank/fat32 @@ -922,7 +918,7 @@ Filesystem Size Used Avail Cap /dev/zvol/tank/fat32 on /mnt (msdosfs, local) Destroying a volume is much the same as destroying a - regular filesystem dataset. The operation is nearly + regular file system dataset. The operation is nearly instantaneous, but it may take several minutes for the free space to be reclaimed in the background. @@ -930,17 +926,17 @@ Filesystem Size Used Avail Cap Renaming a Dataset - The name of a dataset can be changed using - zfs rename. The rename command can also be + The name of a dataset can be changed with + zfs rename. rename can also be used to change the parent of a dataset. Renaming a dataset to be under a different parent dataset will change the value of those properties that are inherited by the child dataset. When a dataset is renamed, it is unmounted and then remounted in the new location (inherited from the parent dataset). This - behavior can be prevented using the - parameter. Due to the nature of snapshots, they cannot be + behavior can be prevented with . + Due to the nature of snapshots, they cannot be renamed outside of the parent dataset. To rename a recursive - snapshot, specify the parameter, and all + snapshot, specify , and all snapshots with the same specified snapshot will be renamed. @@ -949,7 +945,7 @@ Filesystem Size Used Avail Cap Setting Dataset Properties Each ZFS dataset has a number of - properties to control its behavior. Most properties are + properties that control its behavior. Most properties are automatically inherited from the parent dataset, but can be overridden locally. Set a property on a dataset with zfs set @@ -960,11 +956,11 @@ Filesystem Size Used Avail Cap Most properties can be reverted to their inherited values using zfs inherit. - It is possible to set user-defined properties in ZFS. + It is possible to set user-defined properties. They become part of the dataset configuration and can be used to provide additional information about the dataset or its contents. To distinguish these custom properties from the - ones supplied as part of ZFS, a colon (:) + ones supplied as part of ZFS, a colon (:) is used to create a custom namespace for the property. &prompt.root; zfs set custom:costcenter=1234 tank @@ -972,7 +968,7 @@ Filesystem Size Used Avail Cap NAME PROPERTY VALUE SOURCE tank custom:costcenter 1234 local - To remove such a custom property again, use + To remove a custom property, use zfs inherit with . If the custom property is not defined in any of the parent datasets, it will be removed @@ -992,15 +988,15 @@ tank custom:costcenter - Snapshots are one of the most powerful features of ZFS. A - snapshot provides a point-in-time copy of the dataset that the - parent dataset can be rolled back to if required. Create a + snapshot provides a point-in-time copy of the dataset. The + parent dataset can be easily rolled back to that snapshot state. Create a snapshot with zfs snapshot dataset@snapshotname. - Specifying the parameter will recursively - create a snapshot with the same name on all child + Adding creates a snapshot recursively, + with the same name on all child datasets. - By default, snapshots are mounted in a hidden directory + Snapshots are mounted in a hidden directory under the parent dataset: .zfs/snapshots/snapshotname. Individual files can easily be restored to a previous state by @@ -1012,17 +1008,17 @@ tank custom:costcenter - Snapshots consume space based on how much the parent file system has changed since the time of the snapshot. The written property of a snapshot tracks how - much space is being used by a snapshot. + much space is being used by the snapshot. - To destroy a snapshot and recover the space consumed by - the overwritten or deleted files, run zfs destroy + Snapshots are destroyed and the space reclaimed with + zfs destroy dataset@snapshot. - The parameter will recursively remove all + Adding recursively removes all snapshots with the same name under the parent dataset. Adding - the parameters to the destroy command - will display a list of the snapshots that would be deleted and - an estimate of how much space would be reclaimed by proceeding - with the destroy operation. + to the command + displays a list of the snapshots that would be deleted and + an estimate of how much space would be reclaimed without + performing the actual destroy operation. @@ -1050,17 +1046,17 @@ tank custom:costcenter - Dataset, User and Group Quotas - Dataset quotas can - be used to restrict the amount of space that can be consumed + Dataset quotas are + used to restrict the amount of space that can be consumed by a particular dataset. Reference Quotas work - in very much the same way, except they only count the space + in very much the same way, but only count the space used by the dataset itself, excluding snapshots and child - datasets. Similarly + datasets. Similarly, user and group quotas can be - used to prevent users or groups from consuming all of the - available space in the pool or dataset. + used to prevent users or groups from using all of the + space in the pool or dataset. To enforce a dataset quota of 10 GB for storage/home/bob, use the @@ -1103,14 +1099,12 @@ tank custom:costcenter - - For example, to enforce a user quota of 50 GB for a - user named joe, use the - following: + For example, to enforce a user quota of 50 GB for the + user named joe: &prompt.root; zfs set userquota@joe=50G - To remove the quota or make sure that one is not set, - instead use: + To remove any quota: &prompt.root; zfs set userquota@joe=none @@ -1146,8 +1140,8 @@ tank custom:costcenter - the groupquota privilege can view and set all quotas for all groups. - To display the amount of space consumed by each user on - the specified filesystem or snapshot, along with any specified + To display the amount of space used by each user on + a filesystem or snapshot, along with any specified quotas, use zfs userspace. For group information, use zfs groupspace. For more information about supported options or how to display only @@ -1165,10 +1159,10 @@ tank custom:costcenter - Reservations guarantee a minimum amount of space will always be available - to a dataset. The reserved space will not be available to any + on a dataset. The reserved space will not be available to any other dataset. This feature can be especially useful to - ensure that users cannot comsume all of the free space, - leaving none for an important dataset or log files. + ensure that free space is available + for an important dataset or log files. The general format of the reservation property is @@ -1178,8 +1172,7 @@ tank custom:costcenter - &prompt.root; zfs set reservation=10G storage/home/bob - To make sure that no reservation is set, or to remove a - reservation, use: + To clear any reservation: &prompt.root; zfs set reservation=none storage/home/bob @@ -1189,9 +1182,8 @@ tank custom:costcenter - Reservation, with the general format refreservation=size. - To check if any reservations or refreservations exist on - storage/home/bob, execute one of the - following commands: + This command shows any reservations or refreservations that exist on + storage/home/bob: &prompt.root; zfs get reservation storage/home/bob &prompt.root; zfs get refreservation storage/home/bob @@ -1209,65 +1201,59 @@ tank custom:costcenter - When enabled, Deduplication uses the checksum of each block to detect duplicate blocks. - When a new block is about to be written and it is determined - to be a duplicate of an existing block, rather than writing - the same data again, ZFS just references - the existing data on disk an additional time. This can offer - tremendous space savings if your data contains many discreet - copies of the file information. Deduplication requires an + When a new block is a duplicate of an existing block, + ZFS writes an additional reference to + the existing data instead of the whole duplicate block. This can offer + tremendous space savings if the data contains many discreet + copies of the file information. Be warned: deduplication requires an extremely large amount of memory, and most of the space savings can be had without the extra cost by enabling compression instead. - To activate deduplication, you simply need to set the - following property on the target pool. + To activate deduplication, set the + dedup property on the target pool: &prompt.root; zfs set dedup=on pool - it is important to mention that only new data being - written to the pool will be deduplicated. Data that is - already residing on the pool will not be deduplicated by + Only new data being + written to the pool will be deduplicated. Data that has + already been written to the pool will not be deduplicated merely by activating this option. As such, a pool with a freshly activated deduplication property will look something like this - example. + example: &prompt.root; zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT pool 2.84G 2.19M 2.83G 0% 1.00x ONLINE - The DEDUP column shows the actual rate - of deduplication for that pool. A value of - 1.00x that no data has been deduplicated - due to insufficient duplicate data. In the following example, + of deduplication for the pool. A value of + 1.00x shows that data has not been deduplicated + yet. In the next example, the ports tree is copied three times into different - directories on the deduplicated pool above to provide - redundancy. + directories on the deduplicated pool created above. &prompt.root; zpool list for d in dir1 dir2 dir3; do for> mkdir $d && cp -R /usr/ports $d & for> done - Now that redundant data has been created, ZFS detects that - and makes sure that the data is not taking up additional - space. + Redundant data is detected and deduplicated: &prompt.root; zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT pool 2.84G 20.9M 2.82G 0% 3.00x ONLINE - - The DEDUP column now contains the - value 3.00x. This indicates that ZFS - detected the copies of the ports tree data and was able to - deduplicate it at a ratio of 1/3. The space savings that this - yields can be enormous, but only when there is enough memory - available to keep track of the deduplicated blocks. + The DEDUP column now shows a factor of + 3.00x. The multiple copies of the ports + tree data was detected and deduplicated, taking only a third + of the space. The potential for space savings + can be enormous, but comes at the cost of having enough memory + to keep track of the deduplicated blocks. Deduplication is not always beneficial, especially when - there is not much redundant data on a ZFS pool. To see how - much space could be saved by deduplication for a given set of - data that is already stored in a pool, ZFS can simulate the - effects that deduplication would have: + there is not much redundant data on a pool. ZFS + can show potential space savings by simulating deduplication on an existing pool: &prompt.root; zdb -S pool Simulated DDT histogram: @@ -1293,16 +1279,16 @@ dedup = 1.05, compress = 1.11, copies = After zdb -S finishes analyzing the pool, it shows the space reduction ratio that would be achieved by activating deduplication. In this case, - 1.16 is a very poor rate that is mostly + 1.16 is a very poor ratio that is mostly influenced by compression. Activating deduplication on this - pool would not save any significant amount of space. Keeping - the formula dedup * compress / copies = deduplication - ratio in mind, a system administrator can plan the + pool would not save any significant amount of space. Using + the formula dedup * compress / copies = deduplication + ratio, system administrators can plan the storage allocation more towards having multiple copies of data or by having a decent compression rate in order to utilize the space savings that deduplication provides. As a rule of - thumb, compression should be used first before deduplication - due to the lower memory requirements. + thumb, compression should be used before deduplication + due to the much lower memory requirements. @@ -1316,8 +1302,8 @@ dedup = 1.05, compress = 1.11, copies = to the specified jail, and zfs unjail detaches it. For the dataset to be administered from within a jail, the jailed property must be - set. Once a dataset is jailed it can no longer be mounted on - the host, because the jail administrator may have set + set. Once a dataset is jailed, it can no longer be mounted on + the host because the jail administrator may have set unacceptable mount points. @@ -1398,7 +1384,7 @@ dedup = 1.05, compress = 1.11, copies = ZFS on i386 Some of the features provided by ZFS - are RAM-intensive, and may require tuning for maximum + are memory intensive, and may require tuning for maximum efficiency on systems with limited RAM. @@ -1422,7 +1408,7 @@ dedup = 1.05, compress = 1.11, copies = Kernel Configuration - Due to the RAM limitations of the + Due to the address space limitations of the &i386; platform, ZFS users on the &i386; architecture should add this option to a custom kernel configuration file, rebuild the kernel, and @@ -1636,7 +1622,7 @@ vfs.zfs.vdev.cache.size="5M" In a RAID-Z1 configuration - with 4 disks, each 1 TB, usable storage is + with four disks, each 1 TB, usable storage is 3 TB and the pool will still be able to operate in degraded mode with one faulted disk. If an additional disk goes offline before the @@ -1644,15 +1630,15 @@ vfs.zfs.vdev.cache.size="5M" In a RAID-Z3 configuration - with 8 disks of 1 TB, the volume would + with eight disks of 1 TB, the volume will provide 5 TB of usable space and still be able to operate with three faulted disks. &sun; - recommends no more than 9 disks in a single vdev. + recommends no more than nine disks in a single vdev. If the configuration has more disks, it is recommended to divide them into separate vdevs and the pool data will be striped across them. - A configuration of 2 + A configuration of two RAID-Z2 vdevs consisting of 8 disks each would create something similar to a RAID-60 array. A @@ -1960,7 +1946,7 @@ vfs.zfs.vdev.cache.size="5M" + can be disabled, but it is not advised. @@ -1988,7 +1974,7 @@ vfs.zfs.vdev.cache.size="5M"Checksums make it possible to detect duplicate blocks of data as they are written. If deduplication is enabled, instead of writing the block a second time, the - reference count of the existing block will be increased, + reference count of the existing block is increased, saving storage space. To do this, ZFS keeps a deduplication table (DDT) in memory, containing the list @@ -2026,14 +2012,14 @@ vfs.zfs.vdev.cache.size="5M"Scrub Instead of a consistency check like &man.fsck.8;, - ZFS has the scrub. + ZFS has scrub. scrub reads all data blocks stored on the pool and verifies their checksums against the known - good checksums stored in the metadata. This periodic + good checksums stored in the metadata. A periodic check of all the data stored on the pool ensures the recovery of any corrupted blocks before they are needed. A scrub is not required after an unclean shutdown, but - it is recommended that you run a scrub at least once + it is recommended that a scrub is run at least once each quarter. Checksums of each block are tested as they are read in normal use, but a scrub operation makes sure even infrequently used blocks are checked for @@ -2048,7 +2034,7 @@ vfs.zfs.vdev.cache.size="5M"ZFS supports different types of @@ -2167,7 +2153,7 @@ vfs.zfs.vdev.cache.size="5M" Online - A ZFS pool or vdev that is in the + A pool or vdev in the Online state has all of its member devices connected and fully operational. Individual devices in the Online state are @@ -2190,10 +2176,10 @@ vfs.zfs.vdev.cache.size="5M" Degraded - A ZFS pool or vdev that is in the + A pool or vdev in the Degraded state has one or more disks that have been disconnected or have failed. The pool is - still usable, however if additional devices fail, the + still usable, but if additional devices fail, the pool could become unrecoverable. Reconnecting the missing devices or replacing the failed disks will return the pool to an @@ -2206,7 +2192,7 @@ vfs.zfs.vdev.cache.size="5M" Faulted - A ZFS pool or vdev that is in the + A pool or vdev in the Faulted state is no longer operational and the data residing on it can no longer be accessed. A pool or vdev enters the From owner-svn-doc-projects@FreeBSD.ORG Mon Nov 25 06:13:43 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id D3B5969C; Mon, 25 Nov 2013 06:13:43 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C2BDD2D25; Mon, 25 Nov 2013 06:13:43 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rAP6Dh6c004623; Mon, 25 Nov 2013 06:13:43 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id rAP6DhIU004622; Mon, 25 Nov 2013 06:13:43 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201311250613.rAP6DhIU004622@svn.freebsd.org> From: Warren Block Date: Mon, 25 Nov 2013 06:13:43 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43243 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 06:13:43 -0000 Author: wblock Date: Mon Nov 25 06:13:43 2013 New Revision: 43243 URL: http://svnweb.freebsd.org/changeset/doc/43243 Log: Whitespace-only fixes, translators please ignore. Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 05:58:08 2013 (r43242) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 06:13:43 2013 (r43243) @@ -567,12 +567,12 @@ errors: No known data errors as in the case of RAID-Z, the other option is to add a vdev to the pool. It is possible, but discouraged, to mix vdev types. ZFS stripes data across each of the vdevs. For example, if - there are two mirror vdevs, then this is effectively a RAID - 10, striping the writes across the two sets of mirrors. - Because of the way that space is allocated in ZFS to attempt - to have each vdev reach 100% full at the same time, there is a - performance penalty if the vdevs have different amounts of - free space. + there are two mirror vdevs, then this is effectively a + RAID 10, striping the writes across the two + sets of mirrors. Because of the way that space is allocated + in ZFS to attempt to have each vdev reach + 100% full at the same time, there is a performance penalty if + the vdevs have different amounts of free space. Currently, vdevs cannot be removed from a zpool, and disks can only be removed from a mirror if there is enough remaining @@ -604,8 +604,8 @@ errors: No known data errors available, but performance may be impacted because missing data will need to be calculated from the available redundancy. To restore the vdev to a fully functional state, the failed - physical device must be replaced, and ZFS must - be instructed to begin the + physical device must be replaced, and ZFS + must be instructed to begin the resilver operation, where data that was on the failed device will be recalculated from available redundancy and written to the replacement @@ -689,13 +689,13 @@ errors: No known data errors Displaying Recorded Pool History - ZFS records all the commands that were issued to - administer the pool. These include the creation of datasets, - changing properties, or when a disk has been replaced in - the pool. This history is useful for reviewing how a pool was created and - which user did a specific action and when. - History is not kept in a log file, but is a part of the pool - itself. Because of that, history cannot be altered + ZFS records all the commands that were + issued to administer the pool. These include the creation of + datasets, changing properties, or when a disk has been + replaced in the pool. This history is useful for reviewing + how a pool was created and which user did a specific action + and when. History is not kept in a log file, but is a part of + the pool itself. Because of that, history cannot be altered after the fact unless the pool is destroyed. The command to review this history is aptly named zpool history: @@ -732,11 +732,10 @@ History for 'tank': 2013-02-27.18:51:13 [internal create txg:55] dataset = 39 2013-02-27.18:51:18 zfs create tank/backup - A more-detailed history is invoked by - adding -l. - Log records are shown in long format, including information - like the name of the user who issued the command and the hostname on - which the change was made. + A more-detailed history is invoked by adding + -l. Log records are shown in long format, + including information like the name of the user who issued the + command and the hostname on which the change was made. &prompt.root; zpool history -l History for 'tank': @@ -758,9 +757,9 @@ History for 'tank': Both options to zpool history can be combined to give the most detailed information possible for - any given pool. Pool history provides valuable - information when tracking down what actions were - performed or when more detailed output is needed for debugging. + any given pool. Pool history provides valuable information + when tracking down what actions were performed or when more + detailed output is needed for debugging. @@ -820,11 +819,11 @@ data 288G 1.53T A pool consisting of one or more mirror vdevs can be split into a second pool. The last member of each mirror (unless otherwise specified) is detached and used to create a - new pool containing the same data. It is recommended that - the operation first be attempted with the - parameter. The details of the proposed - operation are displayed without actually performing it. This helps - ensure the operation will happen as expected. + new pool containing the same data. It is recommended that the + operation first be attempted with the + parameter. The details of the proposed operation are + displayed without actually performing it. This helps ensure + the operation will happen as expected. @@ -841,18 +840,17 @@ data 288G 1.53T Creating & Destroying Datasets Unlike traditional disks and volume managers, space - in ZFS is not preallocated. - Wtraditional file systems, once all of the space was - partitioned and assigned, there was no way to - add an additional file system without adding a new disk. - With ZFS, new file systems can be created at any time. - Each - dataset has - properties including features like compression, deduplication, - caching and quoteas, as well as other useful properties like - readonly, case sensitivity, network file sharing, and a mount - point. Each separate dataset can be administered, - delegated, + in ZFS is not preallocated. Wtraditional + file systems, once all of the space was partitioned and + assigned, there was no way to add an additional file system + without adding a new disk. With ZFS, new + file systems can be created at any time. Each dataset + has properties including features like compression, + deduplication, caching and quoteas, as well as other useful + properties like readonly, case sensitivity, network file + sharing, and a mount point. Each separate dataset can be + administered, delegated, replicated, snapshoted, jailed, and destroyed as a @@ -871,7 +869,7 @@ data 288G 1.53T is asynchronous, and the free space may take several minutes to appear in the pool. The freeing property, accessible with zpool get freeing - poolname indicates how + poolname indicates how many datasets are having their blocks freed in the background. If there are child datasets, like snapshots or other @@ -894,16 +892,17 @@ data 288G 1.53T /dev/zvol/poolname/dataset. This allows the volume to be used for other file systems, to back the disks of a virtual machine, or to be exported using - protocols like iSCSI or HAST. + protocols like iSCSI or + HAST. - A volume can be formatted with any file system. - To the user, it will appear as if they are working with - a regular disk using that specific filesystem and not ZFS. - Putting ordinary file systems on - ZFS volumes provides features those file systems would not normally have. For example, - using the compression property on a - 250 MB volume allows creation of a compressed FAT - filesystem. + A volume can be formatted with any file system. To the + user, it will appear as if they are working with a regular + disk using that specific filesystem and not + ZFS. Putting ordinary file systems on + ZFS volumes provides features those file + systems would not normally have. For example, using the + compression property on a 250 MB volume allows creation + of a compressed FAT filesystem. &prompt.root; zfs create -V 250m -o compression=on tank/fat32 &prompt.root; zfs list tank @@ -927,16 +926,16 @@ Filesystem Size Used Avail Cap Renaming a Dataset The name of a dataset can be changed with - zfs rename. rename can also be - used to change the parent of a dataset. Renaming a dataset to - be under a different parent dataset will change the value of - those properties that are inherited by the child dataset. - When a dataset is renamed, it is unmounted and then remounted - in the new location (inherited from the parent dataset). This - behavior can be prevented with . - Due to the nature of snapshots, they cannot be - renamed outside of the parent dataset. To rename a recursive - snapshot, specify , and all + zfs rename. rename can + also be used to change the parent of a dataset. Renaming a + dataset to be under a different parent dataset will change the + value of those properties that are inherited by the child + dataset. When a dataset is renamed, it is unmounted and then + remounted in the new location (inherited from the parent + dataset). This behavior can be prevented with + . Due to the nature of snapshots, they + cannot be renamed outside of the parent dataset. To rename a + recursive snapshot, specify , and all snapshots with the same specified snapshot will be renamed. @@ -949,19 +948,21 @@ Filesystem Size Used Avail Cap automatically inherited from the parent dataset, but can be overridden locally. Set a property on a dataset with zfs set - property=value - dataset. Most properties - have a limited set of valid values, zfs get - will display each possible property and its valid values. - Most properties can be reverted to their inherited values - using zfs inherit. - - It is possible to set user-defined properties. - They become part of the dataset configuration and can be used - to provide additional information about the dataset or its + property=value + dataset. Most + properties have a limited set of valid values, + zfs get will display each possible property + and its valid values. Most properties can be reverted to + their inherited values using + zfs inherit. + + It is possible to set user-defined properties. They + become part of the dataset configuration and can be used to + provide additional information about the dataset or its contents. To distinguish these custom properties from the - ones supplied as part of ZFS, a colon (:) - is used to create a custom namespace for the property. + ones supplied as part of ZFS, a colon + (:) is used to create a custom namespace + for the property. &prompt.root; zfs set custom:costcenter=1234 tank &prompt.root; zfs get custom:costcenter tank @@ -969,11 +970,10 @@ NAME PROPERTY VALUE SOURCE tank custom:costcenter 1234 local To remove a custom property, use - zfs inherit with - . If the custom property is not - defined in any of the parent datasets, it will be removed - completely (although the changes are still recorded in the - pool's history). + zfs inherit with . If + the custom property is not defined in any of the parent + datasets, it will be removed completely (although the changes + are still recorded in the pool's history). &prompt.root; zfs inherit -r custom:costcenter tank &prompt.root; zfs get custom:costcenter tank @@ -989,12 +989,11 @@ tank custom:costcenter - Snapshots are one of the most powerful features of ZFS. A snapshot provides a point-in-time copy of the dataset. The - parent dataset can be easily rolled back to that snapshot state. Create a - snapshot with zfs snapshot - dataset@snapshotname. + parent dataset can be easily rolled back to that snapshot + state. Create a snapshot with zfs snapshot + dataset@snapshotname. Adding creates a snapshot recursively, - with the same name on all child - datasets. + with the same name on all child datasets. Snapshots are mounted in a hidden directory under the parent dataset: , with the general format refreservation=size. - This command shows any reservations or refreservations that exist on - storage/home/bob: + This command shows any reservations or refreservations + that exist on storage/home/bob: &prompt.root; zfs get reservation storage/home/bob &prompt.root; zfs get refreservation storage/home/bob @@ -1202,25 +1201,24 @@ tank custom:costcenter - Deduplication uses the checksum of each block to detect duplicate blocks. When a new block is a duplicate of an existing block, - ZFS writes an additional reference to - the existing data instead of the whole duplicate block. This can offer - tremendous space savings if the data contains many discreet - copies of the file information. Be warned: deduplication requires an - extremely large amount of memory, and most of the space - savings can be had without the extra cost by enabling - compression instead. + ZFS writes an additional reference to the + existing data instead of the whole duplicate block. This can + offer tremendous space savings if the data contains many + discreet copies of the file information. Be warned: + deduplication requires an extremely large amount of memory, + and most of the space savings can be had without the extra + cost by enabling compression instead. To activate deduplication, set the dedup property on the target pool: &prompt.root; zfs set dedup=on pool - Only new data being - written to the pool will be deduplicated. Data that has - already been written to the pool will not be deduplicated merely by - activating this option. As such, a pool with a freshly - activated deduplication property will look something like this - example: + Only new data being written to the pool will be + deduplicated. Data that has already been written to the pool + will not be deduplicated merely by activating this option. As + such, a pool with a freshly activated deduplication property + will look something like this example: &prompt.root; zpool list NAME SIZE ALLOC FREE CAP DEDUP HEALTH ALTROOT @@ -1228,10 +1226,10 @@ pool 2.84G 2.19M 2.83G 0% 1.00x ONLINE The DEDUP column shows the actual rate of deduplication for the pool. A value of - 1.00x shows that data has not been deduplicated - yet. In the next example, - the ports tree is copied three times into different - directories on the deduplicated pool created above. + 1.00x shows that data has not been + deduplicated yet. In the next example, the ports tree is + copied three times into different directories on the + deduplicated pool created above. &prompt.root; zpool list for d in dir1 dir2 dir3; do @@ -1247,13 +1245,14 @@ pool 2.84G 20.9M 2.82G 0% 3.00x ONLINE - The DEDUP column now shows a factor of 3.00x. The multiple copies of the ports tree data was detected and deduplicated, taking only a third - of the space. The potential for space savings - can be enormous, but comes at the cost of having enough memory - to keep track of the deduplicated blocks. + of the space. The potential for space savings can be + enormous, but comes at the cost of having enough memory to + keep track of the deduplicated blocks. Deduplication is not always beneficial, especially when - there is not much redundant data on a pool. ZFS - can show potential space savings by simulating deduplication on an existing pool: + there is not much redundant data on a pool. + ZFS can show potential space savings by + simulating deduplication on an existing pool: &prompt.root; zdb -S pool Simulated DDT histogram: @@ -1282,12 +1281,12 @@ dedup = 1.05, compress = 1.11, copies = 1.16 is a very poor ratio that is mostly influenced by compression. Activating deduplication on this pool would not save any significant amount of space. Using - the formula dedup * compress / copies = deduplication - ratio, system administrators can plan the - storage allocation more towards having multiple copies of data - or by having a decent compression rate in order to utilize the - space savings that deduplication provides. As a rule of - thumb, compression should be used before deduplication + the formula dedup * compress / copies = + deduplication ratio, system administrators can plan + the storage allocation more towards having multiple copies of + data or by having a decent compression rate in order to + utilize the space savings that deduplication provides. As a + rule of thumb, compression should be used before deduplication due to the much lower memory requirements. @@ -1296,15 +1295,16 @@ dedup = 1.05, compress = 1.11, copies = zfs jail and the corresponding jailed property are used to delegate a - ZFS dataset to a Jail. zfs jail - jailid attaches a dataset - to the specified jail, and zfs unjail - detaches it. For the dataset to be administered from - within a jail, the jailed property must be - set. Once a dataset is jailed, it can no longer be mounted on - the host because the jail administrator may have set - unacceptable mount points. + ZFS dataset to a + Jail. + zfs jail jailid + attaches a dataset to the specified jail, and + zfs unjail detaches it. For the dataset to + be administered from within a jail, the + jailed property must be set. Once a + dataset is jailed, it can no longer be mounted on the host + because the jail administrator may have set unacceptable mount + points. @@ -1633,8 +1633,8 @@ vfs.zfs.vdev.cache.size="5M" @@ -1793,13 +1793,12 @@ vfs.zfs.vdev.cache.size="5M"ZFS - does not require a &man.fsck.8; after an unexpected - shutdown. + In the event of a shorn write (a system crash or power + loss in the middle of writing a file), the entire + original contents of the file are still available and + the incomplete write is discarded. This also means that + ZFS does not require a &man.fsck.8; + after an unexpected shutdown. @@ -2019,11 +2018,11 @@ vfs.zfs.vdev.cache.size="5M"scrub is run at least once - each quarter. Checksums of each block are tested as - they are read in normal use, but a scrub operation makes - sure even infrequently used blocks are checked for - silent corruption. + it is recommended that a scrub is run + at least once each quarter. Checksums of each block are + tested as they are read in normal use, but a scrub + operation makes sure even infrequently used blocks are + checked for silent corruption. From owner-svn-doc-projects@FreeBSD.ORG Mon Nov 25 06:16:47 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EBA7E6EE; Mon, 25 Nov 2013 06:16:47 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id C27952D32; Mon, 25 Nov 2013 06:16:47 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rAP6Glr1005090; Mon, 25 Nov 2013 06:16:47 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id rAP6GlFE005089; Mon, 25 Nov 2013 06:16:47 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201311250616.rAP6GlFE005089@svn.freebsd.org> From: Warren Block Date: Mon, 25 Nov 2013 06:16:47 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43244 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 06:16:48 -0000 Author: wblock Date: Mon Nov 25 06:16:47 2013 New Revision: 43244 URL: http://svnweb.freebsd.org/changeset/doc/43244 Log: Fix a few small errors. Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 06:13:43 2013 (r43243) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 06:16:47 2013 (r43244) @@ -566,7 +566,7 @@ errors: No known data errors When adding disks to the existing vdev is not an option, as in the case of RAID-Z, the other option is to add a vdev to the pool. It is possible, but discouraged, to mix vdev types. - ZFS stripes data across each of the vdevs. For example, if + ZFS stripes data across each of the vdevs. For example, if there are two mirror vdevs, then this is effectively a RAID 10, striping the writes across the two sets of mirrors. Because of the way that space is allocated @@ -694,7 +694,7 @@ errors: No known data errors datasets, changing properties, or when a disk has been replaced in the pool. This history is useful for reviewing how a pool was created and which user did a specific action - and when. History is not kept in a log file, but is a part of + and when. History is not kept in a log file, but is part of the pool itself. Because of that, history cannot be altered after the fact unless the pool is destroyed. The command to review this history is aptly named @@ -840,7 +840,7 @@ data 288G 1.53T Creating & Destroying Datasets Unlike traditional disks and volume managers, space - in ZFS is not preallocated. Wtraditional + in ZFS is not preallocated. With traditional file systems, once all of the space was partitioned and assigned, there was no way to add an additional file system without adding a new disk. With ZFS, new From owner-svn-doc-projects@FreeBSD.ORG Mon Nov 25 18:11:57 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 94FBDE28; Mon, 25 Nov 2013 18:11:57 +0000 (UTC) Received: from dmz-mailsec-scanner-8.mit.edu (dmz-mailsec-scanner-8.mit.edu [18.7.68.37]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 13BC32D28; Mon, 25 Nov 2013 18:11:56 +0000 (UTC) X-AuditID: 12074425-b7fd96d000000c39-4a-529392e57c27 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-8.mit.edu (Symantec Messaging Gateway) with SMTP id 07.B0.03129.5E293925; Mon, 25 Nov 2013 13:11:49 -0500 (EST) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id rAPIBnt2018918; Mon, 25 Nov 2013 13:11:49 -0500 Received: from multics.mit.edu (system-low-sipb.mit.edu [18.187.2.37]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id rAPIBlBQ019768 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 25 Nov 2013 13:11:48 -0500 Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id rAPIBkX5010705; Mon, 25 Nov 2013 13:11:46 -0500 (EST) Date: Mon, 25 Nov 2013 13:11:46 -0500 (EST) From: Benjamin Kaduk To: Warren Block Subject: Re: svn commit: r43242 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs In-Reply-To: <201311250558.rAP5w8LT097854@svn.freebsd.org> Message-ID: References: <201311250558.rAP5w8LT097854@svn.freebsd.org> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrJIsWRmVeSWpSXmKPExsUixCmqrft00uQggz0PrSx+fDzEZLHwzGpm i8vvJ7I4MHvM+DSfJYAxissmJTUnsyy1SN8ugStj2vPHrAUXxCoW9Uxga2BcLNTFyMkhIWAi 8fZNGwuELSZx4d56ti5GLg4hgdlMEsuvz4FyNjJKzP/YzAThHGKSuHFwNjuE08Aosbmtix2k n0VAW+JCyw5GEJtNQEVi5puNbCC2iICqxPfuVUwgNrOAjcSEBwvA6oUFEiT+Tv8EVMPBwSlg JfGyRxEkzCvgKLHq2W6wViEBS4l9PZ1g5aICOhKr909hgagRlDg58wkLxEhLiX9rf7FOYBSc hSQ1C0lqASPTKkbZlNwq3dzEzJzi1GTd4uTEvLzUIl0LvdzMEr3UlNJNjKBQZXdR3cE44ZDS IUYBDkYlHl6JzslBQqyJZcWVuYcYJTmYlER5uSYChfiS8lMqMxKLM+KLSnNSiw8xSnAwK4nw /iwByvGmJFZWpRblw6SkOViUxHlvcdgHCQmkJ5akZqemFqQWwWRlODiUJHg/9AM1ChalpqdW pGXmlCCkmTg4QYbzAA0/D7KYt7ggMbc4Mx0if4pRl+Pfh0/fGIVY8vLzUqXEeU+DFAmAFGWU 5sHNgaWYV4ziQG8J874BqeIBpie4Sa+AljABLekyAltSkoiQkmpgnBj1Pi7zaJnyvJCzWz74 Me/pY1S/95Zz5rJdPP/YX7MK2x48Zv08JjU6otBqdl28f0HxbunnOXd25JVe/FR4T4RRqafP oD43Y1s8609pxru3z2vcludbKOMkrJl5cuGp9Tdi20U2uhY4bp1ZEiv5Lv/dcluhNzN/yU+r YWbrjPvU/Fa1siZTiaU4I9FQi7moOBEA5s5pewwDAAA= Cc: svn-doc-projects@freebsd.org, doc-committers@freebsd.org X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 25 Nov 2013 18:11:57 -0000 On Mon, 25 Nov 2013, Warren Block wrote: > Author: wblock > Date: Mon Nov 25 05:58:08 2013 > New Revision: 43242 > URL: http://svnweb.freebsd.org/changeset/doc/43242 > > Log: > Edits for clarity and simplicity. > > Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml > ============================================================================== > --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 04:36:45 2013 (r43241) > +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 05:58:08 2013 (r43242) > @@ -732,10 +732,10 @@ History for 'tank': > 2013-02-27.18:51:13 [internal create txg:55] dataset = 39 > 2013-02-27.18:51:18 zfs create tank/backup > > - The other more detailed history display can be invoked by > - using the -l command. This will show the > - log records in long format, which includes more information > - like the user name who issued the command and the hostname on > + A more-detailed history is invoked by I do not think that "invoked" is quite the right word here; we are not calling upon the history, but rather printing it. > + adding -l. > + Log records are shown in long format, including information > + like the name of the user who issued the command and the hostname on > which the change was made. > > &prompt.root; zpool history -l > @@ -842,55 +840,53 @@ data 288G 1.53T > > Creating & Destroying Datasets > > - Unlike with traditional disks and volume managers, space > - in ZFS is not preallocated, allowing > - additional file systems to be created at any time. With > - traditional file systems, once all of the space was > - partitioned and assigned to a file system, there was no way to > + Unlike traditional disks and volume managers, space > + in ZFS is not preallocated. > + Wtraditional file systems, once all of the space was typo? > + partitioned and assigned, there was no way to > add an additional file system without adding a new disk. > @@ -1209,65 +1201,59 @@ tank custom:costcenter - > When enabled, > Deduplication > uses the checksum of each block to detect duplicate blocks. > + When a new block is a duplicate of an existing block, > + ZFS writes an additional reference to > + the existing data instead of the whole duplicate block. This can offer > + tremendous space savings if the data contains many discreet s/discreet/discrete/ -Ben > + copies of the file information. Be warned: deduplication requires an From owner-svn-doc-projects@FreeBSD.ORG Tue Nov 26 03:44:25 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E855E9A; Tue, 26 Nov 2013 03:44:24 +0000 (UTC) Received: from wonkity.com (wonkity.com [67.158.26.137]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 8600F2E5F; Tue, 26 Nov 2013 03:44:24 +0000 (UTC) Received: from wonkity.com (localhost [127.0.0.1]) by wonkity.com (8.14.7/8.14.7) with ESMTP id rAQ3iMvS050555; Mon, 25 Nov 2013 20:44:22 -0700 (MST) (envelope-from wblock@wonkity.com) Received: from localhost (wblock@localhost) by wonkity.com (8.14.7/8.14.7/Submit) with ESMTP id rAQ3iMRq050552; Mon, 25 Nov 2013 20:44:22 -0700 (MST) (envelope-from wblock@wonkity.com) Date: Mon, 25 Nov 2013 20:44:22 -0700 (MST) From: Warren Block To: Benjamin Kaduk Subject: Re: svn commit: r43242 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs In-Reply-To: Message-ID: References: <201311250558.rAP5w8LT097854@svn.freebsd.org> 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, 25 Nov 2013 20:44:22 -0700 (MST) Cc: svn-doc-projects@freebsd.org, doc-committers@freebsd.org, Warren Block X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2013 03:44:25 -0000 On Mon, 25 Nov 2013, Benjamin Kaduk wrote: > On Mon, 25 Nov 2013, Warren Block wrote: > >> Author: wblock >> Date: Mon Nov 25 05:58:08 2013 >> New Revision: 43242 >> URL: http://svnweb.freebsd.org/changeset/doc/43242 >> >> Log: >> Edits for clarity and simplicity. >> >> Modified: >> projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml >> ============================================================================== >> --- >> projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml >> Mon Nov 25 04:36:45 2013 (r43241) >> +++ >> projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml >> Mon Nov 25 05:58:08 2013 (r43242) >> @@ -732,10 +732,10 @@ History for 'tank': >> 2013-02-27.18:51:13 [internal create txg:55] dataset = 39 >> 2013-02-27.18:51:18 zfs create tank/backup >> >> - The other more detailed history display can be invoked by >> - using the -l command. This will show the >> - log records in long format, which includes more information >> - like the user name who issued the command and the hostname on >> + A more-detailed history is invoked by > > I do not think that "invoked" is quite the right word here; we are not > calling upon the history, but rather printing it. Agreed, and that sentence can be simplified also. >> + adding -l. >> + Log records are shown in long format, including information >> + like the name of the user who issued the command and the hostname on >> which the change was made. >> >> &prompt.root; zpool history -l >> @@ -842,55 +840,53 @@ data 288G 1.53T >> >> Creating & Destroying Datasets >> >> - Unlike with traditional disks and volume managers, space >> - in ZFS is not preallocated, allowing >> - additional file systems to be created at any time. With >> - traditional file systems, once all of the space was >> - partitioned and assigned to a file system, there was no way to >> + Unlike traditional disks and volume managers, space >> + in ZFS is not preallocated. >> + Wtraditional file systems, once all of the space was > > typo? Wwhere? :) >> + partitioned and assigned, there was no way to >> add an additional file system without adding a new disk. >> @@ -1209,65 +1201,59 @@ tank custom:costcenter - >> When enabled, >> Deduplication >> uses the checksum of each block to detect duplicate blocks. >> + When a new block is a duplicate of an existing block, >> + ZFS writes an additional reference to >> + the existing data instead of the whole duplicate block. This can >> offer >> + tremendous space savings if the data contains many discreet > > s/discreet/discrete/ Yes, but the usage is questionable anyway. Rewritten. From owner-svn-doc-projects@FreeBSD.ORG Tue Nov 26 03:45:14 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 75CECF1; Tue, 26 Nov 2013 03:45:14 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 65D182E63; Tue, 26 Nov 2013 03:45:14 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.7/8.14.7) with ESMTP id rAQ3jE6j078580; Tue, 26 Nov 2013 03:45:14 GMT (envelope-from wblock@svn.freebsd.org) Received: (from wblock@localhost) by svn.freebsd.org (8.14.7/8.14.5/Submit) id rAQ3jEXw078579; Tue, 26 Nov 2013 03:45:14 GMT (envelope-from wblock@svn.freebsd.org) Message-Id: <201311260345.rAQ3jEXw078579@svn.freebsd.org> From: Warren Block Date: Tue, 26 Nov 2013 03:45:14 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r43246 - projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.16 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Nov 2013 03:45:14 -0000 Author: wblock Date: Tue Nov 26 03:45:13 2013 New Revision: 43246 URL: http://svnweb.freebsd.org/changeset/doc/43246 Log: Miscellaneous fixes pointed out by Benjamin Kaduk. Submitted by: bjk Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Modified: projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml ============================================================================== --- projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Mon Nov 25 22:28:54 2013 (r43245) +++ projects/zfsupdate-201307/en_US.ISO8859-1/books/handbook/zfs/chapter.xml Tue Nov 26 03:45:13 2013 (r43246) @@ -732,8 +732,8 @@ History for 'tank': 2013-02-27.18:51:13 [internal create txg:55] dataset = 39 2013-02-27.18:51:18 zfs create tank/backup - A more-detailed history is invoked by adding - -l. Log records are shown in long format, + More details can be shown by adding + -l. History records are shown in a long format, including information like the name of the user who issued the command and the hostname on which the change was made. @@ -1202,9 +1202,9 @@ tank custom:costcenter - uses the checksum of each block to detect duplicate blocks. When a new block is a duplicate of an existing block, ZFS writes an additional reference to the - existing data instead of the whole duplicate block. This can - offer tremendous space savings if the data contains many - discreet copies of the file information. Be warned: + existing data instead of the whole duplicate block. + Tremendous space savings are possible if the data contains many + duplicated files or repeated information. Be warned: deduplication requires an extremely large amount of memory, and most of the space savings can be had without the extra cost by enabling compression instead.