From owner-dev-commits-doc-all@freebsd.org Mon May 31 16:08:18 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E0E0264A55D for ; Mon, 31 May 2021 16:08:18 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fv0ZV65HTz3sPl; Mon, 31 May 2021 16:08:18 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B8B8113073; Mon, 31 May 2021 16:08:18 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VG8IDB078697; Mon, 31 May 2021 16:08:18 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VG8IAn078696; Mon, 31 May 2021 16:08:18 GMT (envelope-from git) Date: Mon, 31 May 2021 16:08:18 GMT Message-Id: <202105311608.14VG8IAn078696@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: a5566333ea - main - ru/books: fix several includes to remove errors during PDF builds. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: a5566333ea83f48bb44f8a49717237cae1f0e6cb Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 16:08:18 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=a5566333ea83f48bb44f8a49717237cae1f0e6cb commit a5566333ea83f48bb44f8a49717237cae1f0e6cb Author: Marc Fonvieille AuthorDate: 2021-05-31 16:01:29 +0000 Commit: Marc Fonvieille CommitDate: 2021-05-31 16:01:29 +0000 ru/books: fix several includes to remove errors during PDF builds. --- documentation/content/ru/books/design-44bsd/_index.adoc | 6 +++--- documentation/content/ru/books/handbook/security/_index.adoc | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/documentation/content/ru/books/design-44bsd/_index.adoc b/documentation/content/ru/books/design-44bsd/_index.adoc index 40d9ee8b05..f7d41c42de 100644 --- a/documentation/content/ru/books/design-44bsd/_index.adoc +++ b/documentation/content/ru/books/design-44bsd/_index.adoc @@ -37,7 +37,7 @@ include::shared/releases.adoc[] include::shared/ru/mailing-lists.adoc[] include::shared/ru/teams.adoc[] include::shared/ru/urls.adoc[] -:imagesdir: ../../../images/books/design-44bsd/ +:imagesdir: ../../../../images/books/design-44bsd/ :chapters-path: content/ru/books/design-44bsd/ endif::[] @@ -48,7 +48,7 @@ include::../../../../shared/releases.adoc[] include::../../../../shared/ru/mailing-lists.adoc[] include::../../../../shared/ru/teams.adoc[] include::../../../../shared/ru/urls.adoc[] -:imagesdir: ../../../static/images/books/design-44bsd/ +:imagesdir: ../../../../static/images/books/design-44bsd/ :chapters-path: endif::[] @@ -59,7 +59,7 @@ include::../../../../shared/releases.adoc[] include::../../../../shared/ru/mailing-lists.adoc[] include::../../../../shared/ru/teams.adoc[] include::../../../../shared/ru/urls.adoc[] -:imagesdir: ../../../static/images/books/design-44bsd/ +:imagesdir: ../../../../static/images/books/design-44bsd/ :chapters-path: endif::[] diff --git a/documentation/content/ru/books/handbook/security/_index.adoc b/documentation/content/ru/books/handbook/security/_index.adoc index fdb9bfb954..7dd23310d5 100644 --- a/documentation/content/ru/books/handbook/security/_index.adoc +++ b/documentation/content/ru/books/handbook/security/_index.adoc @@ -1635,11 +1635,11 @@ setkey -D То есть исходящий пакет, который выглядит примерно так: -image::security/ipsec-out-pkt.png[] +image::ipsec-out-pkt.png[] будет инкапсулирован в другой пакет, выглядящий примерно так: -image::security/ipsec-encap-pkt.png[] +image::ipsec-encap-pkt.png[] Этой инкапсуляцией занимается устройство [.filename]#gif#. Как вы можете видеть, теперь у пакета есть реальный IP адрес, исходный пакет был включен в этот пакет в виде данных, которые передаются через интернет. @@ -1709,7 +1709,7 @@ ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D Исходящие пакеты теперь будут выглядеть примерно так: -image::security/ipsec-crypt-pkt.png[] +image::ipsec-crypt-pkt.png[] Когда эти пакеты будут получены на удаленном конце VPN соединения, они будут расшифрованы (используя параметры безопасности, о которых договорился racoon). Затем они будут переданы интерфейсу [.filename]#gif#, который "развернет" второй слой, оставив пакет с внутренними адресами, который сможет попасть во внутреннюю сеть. From owner-dev-commits-doc-all@freebsd.org Mon May 31 16:08:20 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 0340564A56B for ; Mon, 31 May 2021 16:08:20 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fv0ZW6ghdz3sFK; Mon, 31 May 2021 16:08:19 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id CAF681327C; Mon, 31 May 2021 16:08:19 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VG8JZp078718; Mon, 31 May 2021 16:08:19 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VG8JbX078717; Mon, 31 May 2021 16:08:19 GMT (envelope-from git) Date: Mon, 31 May 2021 16:08:19 GMT Message-Id: <202105311608.14VG8JbX078717@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: 58375f6399 - main - ru/books/arch-handbook/: add a missing book.adoc, this allows PDF build. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 58375f63995ea28c5e3dfa4d4c45cb4959c153bc Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 16:08:20 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=58375f63995ea28c5e3dfa4d4c45cb4959c153bc commit 58375f63995ea28c5e3dfa4d4c45cb4959c153bc Author: Marc Fonvieille AuthorDate: 2021-05-31 16:03:10 +0000 Commit: Marc Fonvieille CommitDate: 2021-05-31 16:03:10 +0000 ru/books/arch-handbook/: add a missing book.adoc, this allows PDF build. --- .../content/ru/books/arch-handbook/book.adoc | 72 ++++++++++++++++++++++ 1 file changed, 72 insertions(+) diff --git a/documentation/content/ru/books/arch-handbook/book.adoc b/documentation/content/ru/books/arch-handbook/book.adoc new file mode 100644 index 0000000000..863d9aa451 --- /dev/null +++ b/documentation/content/ru/books/arch-handbook/book.adoc @@ -0,0 +1,72 @@ +--- +title: FreeBSD Architecture Handbook +authors: + - author: The FreeBSD Documentation Project +copyright: Copyright © 2000-2006, 2012-2013 The FreeBSD Documentation Project +description: FreeBSD Architecture Handbook +trademarks: ["freebsd", "apple", "microsoft", "unix", "general"] +tags: ["Arch Handbook", "FreeBSD"] +--- + += FreeBSD Architecture Handbook +:doctype: book +:toc: macro +:toclevels: 2 +:icons: font +:xrefstyle: basic +:relfileprefix: ../ +:outfilesuffix: +:sectnums: +:sectnumlevels: 6 +:partnums: +:chapter-signifier: Chapter +:part-signifier: Part +:source-highlighter: rouge +:experimental: +:skip-front-matter: +:book: true +:pdf: false + +ifeval::["{backend}" == "html5"] +include::shared/mirrors.adoc[] +include::shared/authors.adoc[] +include::shared/releases.adoc[] +include::shared/ru/mailing-lists.adoc[] +include::shared/ru/teams.adoc[] +include::shared/ru/urls.adoc[] +:chapters-path: content/ru/books/arch-handbook/ +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/mirrors.adoc[] +include::../../../../shared/authors.adoc[] +include::../../../../shared/releases.adoc[] +include::../../../../shared/ru/mailing-lists.adoc[] +include::../../../../shared/ru/teams.adoc[] +include::../../../../shared/ru/urls.adoc[] +:chapters-path: +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/mirrors.adoc[] +include::../../../../shared/authors.adoc[] +include::../../../../shared/releases.adoc[] +include::../../../../shared/ru/mailing-lists.adoc[] +include::../../../../shared/ru/teams.adoc[] +include::../../../../shared/ru/urls.adoc[] +:chapters-path: +endif::[] + +''' + +toc::[] + +// Section one + +include::{chapters-path}locking/chapter.adoc[] + +// Section two + +include::{chapters-path}driverbasics/chapter.adoc[] +include::{chapters-path}sound/chapter.adoc[] + From owner-dev-commits-doc-all@freebsd.org Mon May 31 16:15:05 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 714A564AA4F for ; Mon, 31 May 2021 16:15:05 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fv0kK2VXvz3tKn; Mon, 31 May 2021 16:15:05 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 3E9301343A; Mon, 31 May 2021 16:15:05 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VGF5NB091382; Mon, 31 May 2021 16:15:05 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VGF5et091381; Mon, 31 May 2021 16:15:05 GMT (envelope-from git) Date: Mon, 31 May 2021 16:15:05 GMT Message-Id: <202105311615.14VGF5et091381@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: 29e47423be - main - articles/pgpkeys: Add a workaround to fix the 1h build time for PDF. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 29e47423be969b7fcc7125977c1b22ddd33fc671 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 16:15:05 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=29e47423be969b7fcc7125977c1b22ddd33fc671 commit 29e47423be969b7fcc7125977c1b22ddd33fc671 Author: Marc Fonvieille AuthorDate: 2021-05-31 16:09:55 +0000 Commit: Marc Fonvieille CommitDate: 2021-05-31 16:09:55 +0000 articles/pgpkeys: Add a workaround to fix the 1h build time for PDF. asciidoctor-pdf has issues with important number of lines leading to very long build time (more than 1 hour). The PGP keys are source of huge number of lines. As a quick workaround, a wrong path is used for the keys. --- documentation/content/en/articles/pgpkeys/_index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/content/en/articles/pgpkeys/_index.adoc b/documentation/content/en/articles/pgpkeys/_index.adoc index 4efcf5152b..7b753b8301 100644 --- a/documentation/content/en/articles/pgpkeys/_index.adoc +++ b/documentation/content/en/articles/pgpkeys/_index.adoc @@ -23,7 +23,7 @@ endif::[] ifeval::["{backend}" == "pdf"] include::../../../../shared/authors.adoc[] include::../../../../shared/en/teams.adoc[lines=16..-1] -:include-path: ../../../../static/pgpkeys/ +:include-path: ../../../static/pgpkeys/ endif::[] ifeval::["{backend}" == "epub3"] From owner-dev-commits-doc-all@freebsd.org Mon May 31 16:26:20 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D095D64ABFE for ; Mon, 31 May 2021 16:26:20 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fv0zJ5ByCz3wSX; Mon, 31 May 2021 16:26:20 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9AAF2138D6; Mon, 31 May 2021 16:26:20 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VGQKei005090; Mon, 31 May 2021 16:26:20 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VGQKfc005089; Mon, 31 May 2021 16:26:20 GMT (envelope-from git) Date: Mon, 31 May 2021 16:26:20 GMT Message-Id: <202105311626.14VGQKfc005089@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: 5f4322e404 - main - documentation/Makefile: Add PDF targets. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 5f4322e404e4ea93f640658f3aef25b7e45a4e95 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 16:26:20 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=5f4322e404e4ea93f640658f3aef25b7e45a4e95 commit 5f4322e404e4ea93f640658f3aef25b7e45a4e95 Author: Marc Fonvieille AuthorDate: 2021-05-31 16:16:55 +0000 Commit: Marc Fonvieille CommitDate: 2021-05-31 16:16:55 +0000 documentation/Makefile: Add PDF targets. Addition of various PDF targets allowing the build of books, articles with the choice of the language. For example, to build both en_US and fr_FR books, use: make DOC_LANG="en,fr" pdf-books Documents are installed in documentation/public/lang/. Targets to clean the builds are also available. Reviewed by: ceri, gjb, dbaio Differential Revision: --- documentation/Makefile | 132 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 132 insertions(+) diff --git a/documentation/Makefile b/documentation/Makefile index 72616084fa..2257cc0061 100644 --- a/documentation/Makefile +++ b/documentation/Makefile @@ -20,13 +20,20 @@ LOCALBASE?= /usr/local PYTHON_CMD = ${LOCALBASE}/bin/python3 RUBY_CMD = ${LOCALBASE}/bin/ruby HUGO_CMD = ${LOCALBASE}/bin/hugo +ASCIIDOCTORPDF_CMD= /usr/local/bin/asciidoctor-pdf +.if defined(DOC_LANG) && !empty(DOC_LANG) +LANGUAGES = ${DOC_LANG} +.else LANGUAGES = en,es,pt-br,de,ja,zh-cn,zh-tw,ru,el,hu,it,mn,nl,pl,fr +.endif + RUBYLIB = ../shared/lib .export RUBYLIB RUN_DEPENDS= ${PYTHON_CMD} \ ${HUGO_CMD} \ ${LOCALBASE}/bin/asciidoctor \ + ${LOCALBASE}/bin/asciidoctor-pdf \ ${LOCALBASE}/bin/rougify .ifndef HOSTNAME @@ -72,3 +79,128 @@ run-local: .PHONY build: .PHONY ${HUGO_CMD} --minify + +# +# PDF targets +# Use DOC_LANG to choose the language, e.g., make DOC_LANG="en,fr" pdf-books +# +pdf: pdf-articles pdf-books + +pdf-books-target: +.for _lang in ${LANGUAGES:S|,| |g} +.if exists(${.CURDIR}/content/${_lang}/books/) +TMP += ${.CURDIR}/content/${_lang}/books/*/ +.endif +.endfor +BOOKSDIR != echo ${TMP} + +pdf-articles-target: +.for _lang in ${LANGUAGES:S|,| |g} +.if exists(${.CURDIR}/content/${_lang}/articles/) +TTMP += ${.CURDIR}/content/${_lang}/articles/*/ +.endif +.endfor +ARTICLESDIR != echo ${TTMP} + +pdf-books: pdf-books-target generate-books-toc + +# Books build +# +# Notes: +# pdf-theme=default-with-fallback-font is +# used instead of pdf-theme=./themes/default-pdf-theme.yml because +# it allows ja, ru, tr, zh-* fonts to be embedded and rendering is +# better for other languages. +# +# asciidoctor-pdf-cjk and/or specific themes should be used for cjk +# fonts +.for _curpdf in ${BOOKSDIR} + @mkdir -p ${.CURDIR}/public${_curpdf:S|^${.CURDIR}/content||} +.if exists(${_curpdf}book.adoc) + ${ASCIIDOCTORPDF_CMD} \ + -r ./shared/lib/man-macro.rb \ + -r ./shared/lib/man-macro.rb \ + -r ./shared/lib/git-macro.rb \ + -r ./shared/lib/packages-macro.rb \ + -r ./shared/lib/inter-document-references-macro.rb \ + -r ./shared/lib/sectnumoffset-treeprocessor.rb \ + --doctype=book \ + -a skip-front-matter \ + -a pdf-theme=default-with-fallback-font \ + -o ${.CURDIR}/public${_curpdf:S|^${.CURDIR}/content||}book.pdf \ + ${_curpdf}book.adoc +.else +# some books use _index.adoc as main document + ${ASCIIDOCTORPDF_CMD} \ + -r ./shared/lib/man-macro.rb \ + -r ./shared/lib/man-macro.rb \ + -r ./shared/lib/git-macro.rb \ + -r ./shared/lib/packages-macro.rb \ + -r ./shared/lib/inter-document-references-macro.rb \ + -r ./shared/lib/sectnumoffset-treeprocessor.rb \ + --doctype=book \ + -a skip-front-matter \ + -a pdf-theme=default-with-fallback-font \ + -o ${.CURDIR}/public${_curpdf:S|^${.CURDIR}/content||}book.pdf \ + ${_curpdf}_index.adoc +.endif +.endfor + +pdf-articles: pdf-articles-target + +# Articles build +.for _curpdf in ${ARTICLESDIR} + @mkdir -p ${.CURDIR}/public${_curpdf:S|^${.CURDIR}/content||} + ${ASCIIDOCTORPDF_CMD} \ + -r ./shared/lib/man-macro.rb \ + -r ./shared/lib/man-macro.rb \ + -r ./shared/lib/git-macro.rb \ + -r ./shared/lib/packages-macro.rb \ + -r ./shared/lib/inter-document-references-macro.rb \ + -r ./shared/lib/sectnumoffset-treeprocessor.rb \ + --doctype=article \ + -a skip-front-matter \ + -a pdf-theme=default-with-fallback-font \ + -o ${.CURDIR}/public${_curpdf:S|^${.CURDIR}/content||}article.pdf \ + ${_curpdf}_index.adoc +.if exists(${.CURDIR}/static/source/articles/${_curpdf:H:T}) + cp -R ${.CURDIR}/static/source/articles/${_curpdf:H:T}/ \ + ${.CURDIR}/public${_curpdf:S|^${.CURDIR}/content||} +.endif +.endfor + +pdf-clean: pdf-articles-clean pdf-books-clean + +pdf-books-clean: pdf-books-target +.for _curpdf in ${BOOKSDIR} + rm -f ${.CURDIR}/public${_curpdf:S|^${.CURDIR}/content||}book.pdf ${_curpdf}toc*.adoc + rm -fr ${.CURDIR}/public${_curpdf:S|^${.CURDIR}/content||} +.endfor +.for _lang in ${LANGUAGES:S|,| |g} + rm -fr ${.CURDIR}/public/${_lang}/books +.if !exists(${.CURDIR}/public/${_lang}/articles) + rm -fr ${.CURDIR}/public/${_lang} +.endif +.endfor + @if [ -d ${.CURDIR}/public/ ]; then \ + if [ -z "`ls -A ${.CURDIR}/public/`" ]; then \ + rm -fr ${.CURDIR}/public; \ + fi; \ + fi + +pdf-articles-clean: pdf-articles-target +.for _curpdf in ${ARTICLESDIR} + rm -f ${.CURDIR}/public${_curpdf:S|^${.CURDIR}/content||}article.pdf + rm -fr ${.CURDIR}/public${_curpdf:S|^${.CURDIR}/content||} +.endfor +.for _lang in ${LANGUAGES:S|,| |g} + rm -fr ${.CURDIR}/public/${_lang}/articles +.if !exists(${.CURDIR}/public/${_lang}/books) + rm -fr ${.CURDIR}/public/${_lang} +.endif +.endfor + @if [ -d ${.CURDIR}/public/ ]; then \ + if [ -z "`ls -A ${.CURDIR}/public/`" ]; then \ + rm -fr ${.CURDIR}/public; \ + fi; \ + fi From owner-dev-commits-doc-all@freebsd.org Mon May 31 16:39:04 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 42A0764B139 for ; Mon, 31 May 2021 16:39:04 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fv1G011r4z4VV8; Mon, 31 May 2021 16:39:04 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 0B80B13960; Mon, 31 May 2021 16:39:04 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VGd3sq018559; Mon, 31 May 2021 16:39:03 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VGd3nl018558; Mon, 31 May 2021 16:39:03 GMT (envelope-from git) Date: Mon, 31 May 2021 16:39:03 GMT Message-Id: <202105311639.14VGd3nl018558@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: 58489548fc - main - ja/: Fix include links for PDF. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 58489548fc1a8592f550b35b9297c3cad4edda0d Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 16:39:04 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=58489548fc1a8592f550b35b9297c3cad4edda0d commit 58489548fc1a8592f550b35b9297c3cad4edda0d Author: Marc Fonvieille AuthorDate: 2021-05-31 16:37:52 +0000 Commit: Marc Fonvieille CommitDate: 2021-05-31 16:37:52 +0000 ja/: Fix include links for PDF. --- .../content/ja/articles/contributing/_index.adoc | 4 ++-- documentation/content/ja/articles/fonts/_index.adoc | 2 +- documentation/content/ja/articles/ipsec-must/_index.adoc | 2 +- .../content/ja/articles/leap-seconds/_index.adoc | 2 +- .../content/ja/articles/problem-reports/_index.adoc | 4 ++-- documentation/content/ja/books/design-44bsd/_index.adoc | 16 ++++++++-------- documentation/content/ja/books/faq/_index.adoc | 12 ++++++------ 7 files changed, 21 insertions(+), 21 deletions(-) diff --git a/documentation/content/ja/articles/contributing/_index.adoc b/documentation/content/ja/articles/contributing/_index.adoc index f3c043ab08..b2f1e38603 100644 --- a/documentation/content/ja/articles/contributing/_index.adoc +++ b/documentation/content/ja/articles/contributing/_index.adoc @@ -23,8 +23,8 @@ trademarks: ["freebsd", "ieee", "general"] :figure-caption: 図 :example-caption: 例 -include::shared/ja/mailing-lists.adoc[] -include::shared/ja/urls.adoc[] +include::../../../../shared/ja/mailing-lists.adoc[] +include::../../../../shared/ja/urls.adoc[] [.abstract-title] 概要 diff --git a/documentation/content/ja/articles/fonts/_index.adoc b/documentation/content/ja/articles/fonts/_index.adoc index 965e160396..7f68aa8cef 100644 --- a/documentation/content/ja/articles/fonts/_index.adoc +++ b/documentation/content/ja/articles/fonts/_index.adoc @@ -25,7 +25,7 @@ trademarks: ["freebsd", "adobe", "apple", "linux", "microsoft", "opengroup", "ge :figure-caption: 図 :example-caption: 例 -include::shared/ja/urls.adoc[] +include::../../../../shared/ja/urls.adoc[] [.abstract-title] 概要 diff --git a/documentation/content/ja/articles/ipsec-must/_index.adoc b/documentation/content/ja/articles/ipsec-must/_index.adoc index afbdfe9df2..24d452c0cc 100644 --- a/documentation/content/ja/articles/ipsec-must/_index.adoc +++ b/documentation/content/ja/articles/ipsec-must/_index.adoc @@ -24,7 +24,7 @@ trademarks: ["freebsd", "opengroup", "general"] :figure-caption: 図 :example-caption: 例 -include::shared/ja/urls.adoc[] +include::../../../../shared/ja/urls.adoc[] [.abstract-title] 概要 diff --git a/documentation/content/ja/articles/leap-seconds/_index.adoc b/documentation/content/ja/articles/leap-seconds/_index.adoc index d13e63e5c9..83f4fa0a69 100644 --- a/documentation/content/ja/articles/leap-seconds/_index.adoc +++ b/documentation/content/ja/articles/leap-seconds/_index.adoc @@ -20,7 +20,7 @@ releaseinfo: "$FreeBSD$" :figure-caption: 図 :example-caption: 例 -include::shared/ja/urls.adoc[] +include::../../../../shared/ja/urls.adoc[] ''' diff --git a/documentation/content/ja/articles/problem-reports/_index.adoc b/documentation/content/ja/articles/problem-reports/_index.adoc index 57922a1245..c3920a3d6b 100644 --- a/documentation/content/ja/articles/problem-reports/_index.adoc +++ b/documentation/content/ja/articles/problem-reports/_index.adoc @@ -24,8 +24,8 @@ trademarks: ["freebsd", "ibm", "intel", "sun", "general"] :figure-caption: 図 :example-caption: 例 -include::shared/ja/mailing-lists.adoc[] -include::shared/ja/urls.adoc[] +include::../../../../shared/ja/mailing-lists.adoc[] +include::../../../../shared/ja/urls.adoc[] [.abstract-title] 概要 diff --git a/documentation/content/ja/books/design-44bsd/_index.adoc b/documentation/content/ja/books/design-44bsd/_index.adoc index c112bb5444..327d89ab27 100644 --- a/documentation/content/ja/books/design-44bsd/_index.adoc +++ b/documentation/content/ja/books/design-44bsd/_index.adoc @@ -47,10 +47,10 @@ ifeval::["{backend}" == "pdf"] include::../../../../shared/mirrors.adoc[] include::../../../../shared/authors.adoc[] include::../../../../shared/releases.adoc[] -include::../../../../shared/jp/mailing-lists.adoc[] -include::../../../../shared/jp/teams.adoc[] -include::../../../../shared/jp/urls.adoc[] -:imagesdir: ../../../static/images/books/design-44bsd/ +include::../../../../shared/ja/mailing-lists.adoc[] +include::../../../../shared/ja/teams.adoc[] +include::../../../../shared/ja/urls.adoc[] +:imagesdir: ../../../../static/images/books/design-44bsd/ :chapters-path: endif::[] @@ -58,10 +58,10 @@ ifeval::["{backend}" == "epub3"] include::../../../../shared/mirrors.adoc[] include::../../../../shared/authors.adoc[] include::../../../../shared/releases.adoc[] -include::../../../../shared/jp/mailing-lists.adoc[] -include::../../../../shared/jp/teams.adoc[] -include::../../../../shared/jp/urls.adoc[] -:imagesdir: ../../../static/images/books/design-44bsd/ +include::../../../../shared/ja/mailing-lists.adoc[] +include::../../../../shared/ja/teams.adoc[] +include::../../../../shared/ja/urls.adoc[] +:imagesdir: ../../../../static/images/books/design-44bsd/ :chapters-path: endif::[] diff --git a/documentation/content/ja/books/faq/_index.adoc b/documentation/content/ja/books/faq/_index.adoc index 7e2b7cf7c5..3cdfc161e0 100644 --- a/documentation/content/ja/books/faq/_index.adoc +++ b/documentation/content/ja/books/faq/_index.adoc @@ -53,18 +53,18 @@ ifeval::["{backend}" == "pdf"] include::../../../../shared/mirrors.adoc[] include::../../../../shared/authors.adoc[] include::../../../../shared/releases.adoc[] -include::../../../../shared/jp/mailing-lists.adoc[] -include::../../../../shared/jp/teams.adoc[] -include::../../../../shared/jp/urls.adoc[] +include::../../../../shared/ja/mailing-lists.adoc[] +include::../../../../shared/ja/teams.adoc[] +include::../../../../shared/ja/urls.adoc[] endif::[] ifeval::["{backend}" == "epub3"] include::../../../../shared/mirrors.adoc[] include::../../../../shared/authors.adoc[] include::../../../../shared/releases.adoc[] -include::../../../../shared/jp/mailing-lists.adoc[] -include::../../../../shared/jp/teams.adoc[] -include::../../../../shared/jp/urls.adoc[] +include::../../../../shared/ja/mailing-lists.adoc[] +include::../../../../shared/ja/teams.adoc[] +include::../../../../shared/ja/urls.adoc[] endif::[] [.abstract-title] From owner-dev-commits-doc-all@freebsd.org Mon May 31 16:52:52 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5305364B075 for ; Mon, 31 May 2021 16:52:52 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fv1Yw1f2Pz4WLj; Mon, 31 May 2021 16:52:52 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 20AAF1414F; Mon, 31 May 2021 16:52:52 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VGqq48044127; Mon, 31 May 2021 16:52:52 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VGqqgm044126; Mon, 31 May 2021 16:52:52 GMT (envelope-from git) Date: Mon, 31 May 2021 16:52:52 GMT Message-Id: <202105311652.14VGqqgm044126@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: 238d5218d1 - main - ja/: Complete previous commit. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 238d5218d16e35897f0204402cea597248565c47 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 16:52:52 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=238d5218d16e35897f0204402cea597248565c47 commit 238d5218d16e35897f0204402cea597248565c47 Author: Marc Fonvieille AuthorDate: 2021-05-31 16:46:21 +0000 Commit: Marc Fonvieille CommitDate: 2021-05-31 16:46:21 +0000 ja/: Complete previous commit. --- documentation/content/ja/articles/contributing/_index.adoc | 12 ++++++++++++ documentation/content/ja/articles/fonts/_index.adoc | 10 ++++++++++ documentation/content/ja/articles/ipsec-must/_index.adoc | 10 ++++++++++ documentation/content/ja/articles/leap-seconds/_index.adoc | 10 ++++++++++ .../content/ja/articles/problem-reports/_index.adoc | 12 ++++++++++++ 5 files changed, 54 insertions(+) diff --git a/documentation/content/ja/articles/contributing/_index.adoc b/documentation/content/ja/articles/contributing/_index.adoc index b2f1e38603..11982225c7 100644 --- a/documentation/content/ja/articles/contributing/_index.adoc +++ b/documentation/content/ja/articles/contributing/_index.adoc @@ -23,8 +23,20 @@ trademarks: ["freebsd", "ieee", "general"] :figure-caption: 図 :example-caption: 例 +ifeval::["{backend}" == "html5"] +include::shared/ja/mailing-lists.adoc[] +include::shared/ja/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/ja/mailing-lists.adoc[] +include::../../../../shared/ja/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] include::../../../../shared/ja/mailing-lists.adoc[] include::../../../../shared/ja/urls.adoc[] +endif::[] [.abstract-title] 概要 diff --git a/documentation/content/ja/articles/fonts/_index.adoc b/documentation/content/ja/articles/fonts/_index.adoc index 7f68aa8cef..772c83ef7d 100644 --- a/documentation/content/ja/articles/fonts/_index.adoc +++ b/documentation/content/ja/articles/fonts/_index.adoc @@ -25,7 +25,17 @@ trademarks: ["freebsd", "adobe", "apple", "linux", "microsoft", "opengroup", "ge :figure-caption: 図 :example-caption: 例 +ifeval::["{backend}" == "html5"] +include::shared/ja/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/ja/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] include::../../../../shared/ja/urls.adoc[] +endif::[] [.abstract-title] 概要 diff --git a/documentation/content/ja/articles/ipsec-must/_index.adoc b/documentation/content/ja/articles/ipsec-must/_index.adoc index 24d452c0cc..ce26a0f53a 100644 --- a/documentation/content/ja/articles/ipsec-must/_index.adoc +++ b/documentation/content/ja/articles/ipsec-must/_index.adoc @@ -24,7 +24,17 @@ trademarks: ["freebsd", "opengroup", "general"] :figure-caption: 図 :example-caption: 例 +ifeval::["{backend}" == "html5"] +include::shared/ja/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/ja/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] include::../../../../shared/ja/urls.adoc[] +endif::[] [.abstract-title] 概要 diff --git a/documentation/content/ja/articles/leap-seconds/_index.adoc b/documentation/content/ja/articles/leap-seconds/_index.adoc index 83f4fa0a69..955fb81754 100644 --- a/documentation/content/ja/articles/leap-seconds/_index.adoc +++ b/documentation/content/ja/articles/leap-seconds/_index.adoc @@ -20,7 +20,17 @@ releaseinfo: "$FreeBSD$" :figure-caption: 図 :example-caption: 例 +ifeval::["{backend}" == "html5"] +include::shared/ja/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/ja/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] include::../../../../shared/ja/urls.adoc[] +endif::[] ''' diff --git a/documentation/content/ja/articles/problem-reports/_index.adoc b/documentation/content/ja/articles/problem-reports/_index.adoc index c3920a3d6b..caa1c9e39f 100644 --- a/documentation/content/ja/articles/problem-reports/_index.adoc +++ b/documentation/content/ja/articles/problem-reports/_index.adoc @@ -24,8 +24,20 @@ trademarks: ["freebsd", "ibm", "intel", "sun", "general"] :figure-caption: 図 :example-caption: 例 +ifeval::["{backend}" == "html5"] +include::shared/ja/mailing-lists.adoc[] +include::shared/ja/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/ja/mailing-lists.adoc[] +include::../../../../shared/ja/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] include::../../../../shared/ja/mailing-lists.adoc[] include::../../../../shared/ja/urls.adoc[] +endif::[] [.abstract-title] 概要 From owner-dev-commits-doc-all@freebsd.org Mon May 31 16:52:53 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6B5F464B2E2 for ; Mon, 31 May 2021 16:52:53 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fv1Yx2flgz4WRd; Mon, 31 May 2021 16:52:53 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 41D6113CEC; Mon, 31 May 2021 16:52:53 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VGqrgn044148; Mon, 31 May 2021 16:52:53 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VGqr1X044147; Mon, 31 May 2021 16:52:53 GMT (envelope-from git) Date: Mon, 31 May 2021 16:52:53 GMT Message-Id: <202105311652.14VGqr1X044147@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: 1c92b60fba - main - documentation/Makefile: Use of ${LOCALBASE} where needed. Reported by: ceri MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 1c92b60fba29071871424cf8178adfd63d4f64a2 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 16:52:53 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=1c92b60fba29071871424cf8178adfd63d4f64a2 commit 1c92b60fba29071871424cf8178adfd63d4f64a2 Author: Marc Fonvieille AuthorDate: 2021-05-31 16:51:47 +0000 Commit: Marc Fonvieille CommitDate: 2021-05-31 16:51:47 +0000 documentation/Makefile: Use of ${LOCALBASE} where needed. Reported by: ceri --- documentation/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/Makefile b/documentation/Makefile index 2257cc0061..24b6090cd3 100644 --- a/documentation/Makefile +++ b/documentation/Makefile @@ -20,7 +20,7 @@ LOCALBASE?= /usr/local PYTHON_CMD = ${LOCALBASE}/bin/python3 RUBY_CMD = ${LOCALBASE}/bin/ruby HUGO_CMD = ${LOCALBASE}/bin/hugo -ASCIIDOCTORPDF_CMD= /usr/local/bin/asciidoctor-pdf +ASCIIDOCTORPDF_CMD= ${LOCALBASE}/bin/asciidoctor-pdf .if defined(DOC_LANG) && !empty(DOC_LANG) LANGUAGES = ${DOC_LANG} .else From owner-dev-commits-doc-all@freebsd.org Mon May 31 17:04:53 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 956C864B722 for ; Mon, 31 May 2021 17:04:53 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fv1qn3Y5vz4WYs; Mon, 31 May 2021 17:04:53 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 6202513E53; Mon, 31 May 2021 17:04:53 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VH4r0K058780; Mon, 31 May 2021 17:04:53 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VH4rAW058779; Mon, 31 May 2021 17:04:53 GMT (envelope-from git) Date: Mon, 31 May 2021 17:04:53 GMT Message-Id: <202105311704.14VH4rAW058779@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: 97f6abcfc9 - main - articles/pgpkeys: Add a comment in the file about the workaround for PDF. Reported by: ceri MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 97f6abcfc9dbb23ae6f5e19328a5dbceb644ed7d Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 17:04:53 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=97f6abcfc9dbb23ae6f5e19328a5dbceb644ed7d commit 97f6abcfc9dbb23ae6f5e19328a5dbceb644ed7d Author: Marc Fonvieille AuthorDate: 2021-05-31 17:03:13 +0000 Commit: Marc Fonvieille CommitDate: 2021-05-31 17:03:13 +0000 articles/pgpkeys: Add a comment in the file about the workaround for PDF. Reported by: ceri --- documentation/content/en/articles/pgpkeys/_index.adoc | 3 +++ 1 file changed, 3 insertions(+) diff --git a/documentation/content/en/articles/pgpkeys/_index.adoc b/documentation/content/en/articles/pgpkeys/_index.adoc index 7b753b8301..2950eda071 100644 --- a/documentation/content/en/articles/pgpkeys/_index.adoc +++ b/documentation/content/en/articles/pgpkeys/_index.adoc @@ -20,6 +20,9 @@ include::shared/en/teams.adoc[lines=16..-1] :include-path: static/pgpkeys/ endif::[] +// PGP keys are not included during the build +// See 29e47423be969b7fcc7125977c1b22ddd33fc671 revision +// (a wrong path is used as a workaround) ifeval::["{backend}" == "pdf"] include::../../../../shared/authors.adoc[] include::../../../../shared/en/teams.adoc[lines=16..-1] From owner-dev-commits-doc-all@freebsd.org Mon May 31 17:13:45 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9183E64B84C for ; Mon, 31 May 2021 17:13:45 +0000 (UTC) (envelope-from marc@blackend.org) Received: from smtp1-g21.free.fr (smtp1-g21.free.fr [212.27.42.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fv2202jCcz4XVw; Mon, 31 May 2021 17:13:44 +0000 (UTC) (envelope-from marc@blackend.org) Received: from emphyrio.blackend.org (unknown [82.64.86.146]) by smtp1-g21.free.fr (Postfix) with ESMTPS id A1419B004E8; Mon, 31 May 2021 19:13:35 +0200 (CEST) Received: from emphyrio.blackend.org (localhost [127.0.0.1]) by emphyrio.blackend.org (8.16.1/8.16.1) with ESMTPS id 14VHDZHO014444 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 31 May 2021 19:13:35 +0200 (CEST) (envelope-from marc@emphyrio.blackend.org) Received: (from marc@localhost) by emphyrio.blackend.org (8.16.1/8.16.1/Submit) id 14VHDZ3N014443; Mon, 31 May 2021 19:13:35 +0200 (CEST) (envelope-from marc) Date: Mon, 31 May 2021 19:13:35 +0200 From: Marc Fonvieille To: doc-committers@freebsd.org, dev-commits-doc-all@freebsd.org Subject: Re: git: 5f4322e404 - main - documentation/Makefile: Add PDF targets. Message-ID: References: <202105311626.14VGQKfc005089@gitrepo.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <202105311626.14VGQKfc005089@gitrepo.freebsd.org> X-Rspamd-Queue-Id: 4Fv2202jCcz4XVw X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=none; spf=none (mx1.freebsd.org: domain of marc@blackend.org has no SPF policy when checking 212.27.42.1) smtp.mailfrom=marc@blackend.org X-Spamd-Result: default: False [-1.80 / 15.00]; RWL_MAILSPIKE_GOOD(0.00)[212.27.42.1:from]; TO_DN_NONE(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; NEURAL_HAM_SHORT(-1.00)[-1.000]; RCPT_COUNT_TWO(0.00)[2]; FORGED_SENDER(0.30)[blackend@freebsd.org,marc@blackend.org]; RECEIVED_SPAMHAUS_PBL(0.00)[82.64.86.146:received]; MIME_TRACE(0.00)[0:+]; RBL_DBL_DONT_QUERY_IPS(0.00)[212.27.42.1:from]; ASN(0.00)[asn:12322, ipnet:212.27.32.0/19, country:FR]; R_DKIM_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[blackend@freebsd.org,marc@blackend.org]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; FREEFALL_USER(0.00)[marc]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[freebsd.org]; AUTH_NA(1.00)[]; SPAMHAUS_ZRD(0.00)[212.27.42.1:from:127.0.2.255]; RCVD_IN_DNSWL_NONE(0.00)[212.27.42.1:from]; R_SPF_NA(0.00)[no SPF record]; RCVD_TLS_ALL(0.00)[]; MAILMAN_DEST(0.00)[dev-commits-doc-all] X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 17:13:45 -0000 Le 31.05.2021 16:26, Marc Fonvieille a crit : > The branch main has been updated by blackend: > > URL: https://cgit.FreeBSD.org/doc/commit/?id=5f4322e404e4ea93f640658f3aef25b7e45a4e95 > > commit 5f4322e404e4ea93f640658f3aef25b7e45a4e95 > Author: Marc Fonvieille > AuthorDate: 2021-05-31 16:16:55 +0000 > Commit: Marc Fonvieille > CommitDate: 2021-05-31 16:16:55 +0000 > > documentation/Makefile: Add PDF targets. > > Addition of various PDF targets allowing the build of books, articles > with the choice of the language. For example, to build both en_US and > fr_FR books, use: > make DOC_LANG="en,fr" pdf-books > Documents are installed in documentation/public/lang/. Targets to clean > the builds are also available. > I forgot to mention it, you need to upgrade your docproj package/port which now comes, by default, with asciidoctor-pdf (or manually install it). -- Marc From owner-dev-commits-doc-all@freebsd.org Mon May 31 17:14:45 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 8040164BA87 for ; Mon, 31 May 2021 17:14:45 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fv23934l4z4X9D; Mon, 31 May 2021 17:14:45 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4DFB9144AA; Mon, 31 May 2021 17:14:45 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VHEj6J072113; Mon, 31 May 2021 17:14:45 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VHEjPV072112; Mon, 31 May 2021 17:14:45 GMT (envelope-from git) Date: Mon, 31 May 2021 17:14:45 GMT Message-Id: <202105311714.14VHEjPV072112@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: ca74b73c7c - main - zh-cn/articles: Fix include links for PDF. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: ca74b73c7c8b8f0c99a0e284c1be7b841641895d Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 17:14:45 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=ca74b73c7c8b8f0c99a0e284c1be7b841641895d commit ca74b73c7c8b8f0c99a0e284c1be7b841641895d Author: Marc Fonvieille AuthorDate: 2021-05-31 17:13:53 +0000 Commit: Marc Fonvieille CommitDate: 2021-05-31 17:13:53 +0000 zh-cn/articles: Fix include links for PDF. --- .../content/zh-cn/articles/contributing/_index.adoc | 12 ++++++++++++ .../content/zh-cn/articles/leap-seconds/_index.adoc | 10 ++++++++++ documentation/content/zh-cn/articles/linux-users/_index.adoc | 10 ++++++++++ documentation/content/zh-cn/articles/nanobsd/_index.adoc | 10 ++++++++++ .../content/zh-cn/articles/rc-scripting/_index.adoc | 10 ++++++++++ .../content/zh-cn/articles/remote-install/_index.adoc | 12 ++++++++++++ 6 files changed, 64 insertions(+) diff --git a/documentation/content/zh-cn/articles/contributing/_index.adoc b/documentation/content/zh-cn/articles/contributing/_index.adoc index f87cdeb7e2..a7ece340a7 100644 --- a/documentation/content/zh-cn/articles/contributing/_index.adoc +++ b/documentation/content/zh-cn/articles/contributing/_index.adoc @@ -22,8 +22,20 @@ trademarks: ["freebsd", "ieee", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/zh-cn/mailing-lists.adoc[] include::shared/zh-cn/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/zh-cn/mailing-lists.adoc[] +include::../../../../shared/zh-cn/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/zh-cn/mailing-lists.adoc[] +include::../../../../shared/zh-cn/urls.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-cn/articles/leap-seconds/_index.adoc b/documentation/content/zh-cn/articles/leap-seconds/_index.adoc index 2903bc3496..822030ab7d 100644 --- a/documentation/content/zh-cn/articles/leap-seconds/_index.adoc +++ b/documentation/content/zh-cn/articles/leap-seconds/_index.adoc @@ -19,7 +19,17 @@ releaseinfo: "$FreeBSD$" :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/zh-cn/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/zh-cn/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/zh-cn/urls.adoc[] +endif::[] ''' diff --git a/documentation/content/zh-cn/articles/linux-users/_index.adoc b/documentation/content/zh-cn/articles/linux-users/_index.adoc index faa013d6e3..f96c358fef 100644 --- a/documentation/content/zh-cn/articles/linux-users/_index.adoc +++ b/documentation/content/zh-cn/articles/linux-users/_index.adoc @@ -23,7 +23,17 @@ trademarks: ["freebsd", "intel", "redhat", "linux", "unix", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/zh-cn/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/zh-cn/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/zh-cn/urls.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-cn/articles/nanobsd/_index.adoc b/documentation/content/zh-cn/articles/nanobsd/_index.adoc index e58690019b..93b5b8b031 100644 --- a/documentation/content/zh-cn/articles/nanobsd/_index.adoc +++ b/documentation/content/zh-cn/articles/nanobsd/_index.adoc @@ -23,7 +23,17 @@ trademarks: ["freebsd", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-cn/articles/rc-scripting/_index.adoc b/documentation/content/zh-cn/articles/rc-scripting/_index.adoc index 0ad14c6126..0cd4c5394c 100644 --- a/documentation/content/zh-cn/articles/rc-scripting/_index.adoc +++ b/documentation/content/zh-cn/articles/rc-scripting/_index.adoc @@ -24,7 +24,17 @@ trademarks: ["freebsd", "netbsd", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/zh-cn/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/zh-cn/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/zh-cn/urls.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-cn/articles/remote-install/_index.adoc b/documentation/content/zh-cn/articles/remote-install/_index.adoc index b14208aefa..dfbd64cd6b 100644 --- a/documentation/content/zh-cn/articles/remote-install/_index.adoc +++ b/documentation/content/zh-cn/articles/remote-install/_index.adoc @@ -24,8 +24,20 @@ trademarks: ["freebsd", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] include::shared/zh-cn/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/zh-cn/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/zh-cn/urls.adoc[] +endif::[] [.abstract-title] 摘要 From owner-dev-commits-doc-all@freebsd.org Mon May 31 17:54:37 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 6902164BE39 for ; Mon, 31 May 2021 17:54:37 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fv2x92HG7z4ZrK; Mon, 31 May 2021 17:54:37 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 31CA7149D0; Mon, 31 May 2021 17:54:37 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VHsb1t025373; Mon, 31 May 2021 17:54:37 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VHsbv8025372; Mon, 31 May 2021 17:54:37 GMT (envelope-from git) Date: Mon, 31 May 2021 17:54:37 GMT Message-Id: <202105311754.14VHsbv8025372@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: 275d19d9bf - main - zh-tw/: Fix include links for PDF. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 275d19d9bf9fc903c1171dc43ec44b64ad44d886 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 17:54:37 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=275d19d9bf9fc903c1171dc43ec44b64ad44d886 commit 275d19d9bf9fc903c1171dc43ec44b64ad44d886 Author: Marc Fonvieille AuthorDate: 2021-05-31 17:49:35 +0000 Commit: Marc Fonvieille CommitDate: 2021-05-31 17:49:35 +0000 zh-tw/: Fix include links for PDF. --- .../content/zh-tw/articles/contributing/_index.adoc | 12 ++++++++++++ .../content/zh-tw/articles/freebsd-questions/_index.adoc | 12 ++++++++++++ documentation/content/zh-tw/articles/hubs/_index.adoc | 10 ++++++++++ .../content/zh-tw/articles/leap-seconds/_index.adoc | 10 ++++++++++ .../content/zh-tw/articles/mailing-list-faq/_index.adoc | 14 ++++++++++++++ documentation/content/zh-tw/articles/nanobsd/_index.adoc | 10 ++++++++++ .../content/zh-tw/articles/pr-guidelines/_index.adoc | 12 ++++++++++++ .../content/zh-tw/articles/problem-reports/_index.adoc | 14 ++++++++++++++ .../content/zh-tw/articles/remote-install/_index.adoc | 12 ++++++++++++ .../content/zh-tw/books/developers-handbook/_index.adoc | 4 ++-- 10 files changed, 108 insertions(+), 2 deletions(-) diff --git a/documentation/content/zh-tw/articles/contributing/_index.adoc b/documentation/content/zh-tw/articles/contributing/_index.adoc index 7c58c41366..36ddcf9aa7 100644 --- a/documentation/content/zh-tw/articles/contributing/_index.adoc +++ b/documentation/content/zh-tw/articles/contributing/_index.adoc @@ -23,8 +23,20 @@ trademarks: ["freebsd", "ieee", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/zh-tw/mailing-lists.adoc[] include::shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/zh-tw/mailing-lists.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/zh-tw/mailing-lists.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-tw/articles/freebsd-questions/_index.adoc b/documentation/content/zh-tw/articles/freebsd-questions/_index.adoc index 91bb198fa1..c614749423 100644 --- a/documentation/content/zh-tw/articles/freebsd-questions/_index.adoc +++ b/documentation/content/zh-tw/articles/freebsd-questions/_index.adoc @@ -24,8 +24,20 @@ trademarks: ["freebsd", "microsoft", "opengroup", "qualcomm", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/zh-tw/mailing-lists.adoc[] include::shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/zh-tw/mailing-lists.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/zh-tw/mailing-lists.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-tw/articles/hubs/_index.adoc b/documentation/content/zh-tw/articles/hubs/_index.adoc index c461be0051..fb74f127f5 100644 --- a/documentation/content/zh-tw/articles/hubs/_index.adoc +++ b/documentation/content/zh-tw/articles/hubs/_index.adoc @@ -30,7 +30,17 @@ trademarks: ["freebsd", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-tw/articles/leap-seconds/_index.adoc b/documentation/content/zh-tw/articles/leap-seconds/_index.adoc index 7c06fbe94e..3ec5291688 100644 --- a/documentation/content/zh-tw/articles/leap-seconds/_index.adoc +++ b/documentation/content/zh-tw/articles/leap-seconds/_index.adoc @@ -20,7 +20,17 @@ releaseinfo: "$FreeBSD$" :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] ''' diff --git a/documentation/content/zh-tw/articles/mailing-list-faq/_index.adoc b/documentation/content/zh-tw/articles/mailing-list-faq/_index.adoc index dfe33f0c65..469ee37646 100644 --- a/documentation/content/zh-tw/articles/mailing-list-faq/_index.adoc +++ b/documentation/content/zh-tw/articles/mailing-list-faq/_index.adoc @@ -23,9 +23,23 @@ releaseinfo: "$FreeBSD$" :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] include::shared/zh-tw/mailing-lists.adoc[] include::shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/zh-tw/mailing-lists.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/zh-tw/mailing-lists.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-tw/articles/nanobsd/_index.adoc b/documentation/content/zh-tw/articles/nanobsd/_index.adoc index c8cabd72de..3315fa790b 100644 --- a/documentation/content/zh-tw/articles/nanobsd/_index.adoc +++ b/documentation/content/zh-tw/articles/nanobsd/_index.adoc @@ -24,7 +24,17 @@ trademarks: ["freebsd", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-tw/articles/pr-guidelines/_index.adoc b/documentation/content/zh-tw/articles/pr-guidelines/_index.adoc index a29acf5349..203fa06a0e 100644 --- a/documentation/content/zh-tw/articles/pr-guidelines/_index.adoc +++ b/documentation/content/zh-tw/articles/pr-guidelines/_index.adoc @@ -24,8 +24,20 @@ trademarks: ["freebsd", "opengroup", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/zh-tw/mailing-lists.adoc[] include::shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/zh-tw/mailing-lists.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/zh-tw/mailing-lists.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-tw/articles/problem-reports/_index.adoc b/documentation/content/zh-tw/articles/problem-reports/_index.adoc index e559de5456..e3f264be10 100644 --- a/documentation/content/zh-tw/articles/problem-reports/_index.adoc +++ b/documentation/content/zh-tw/articles/problem-reports/_index.adoc @@ -24,9 +24,23 @@ trademarks: ["freebsd", "cvsup", "ibm", "intel", "sparc", "sun", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/en/teams.adoc[] include::shared/zh-tw/mailing-lists.adoc[] include::shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/en/teams.adoc[] +include::../../../../shared/zh-tw/mailing-lists.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/en/teams.adoc[] +include::../../../../shared/zh-tw/mailing-lists.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-tw/articles/remote-install/_index.adoc b/documentation/content/zh-tw/articles/remote-install/_index.adoc index 69622b2544..e8b75cca4e 100644 --- a/documentation/content/zh-tw/articles/remote-install/_index.adoc +++ b/documentation/content/zh-tw/articles/remote-install/_index.adoc @@ -25,8 +25,20 @@ trademarks: ["freebsd", "general"] :figure-caption: 图 :example-caption: 例 +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] include::shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/zh-tw/urls.adoc[] +endif::[] [.abstract-title] 摘要 diff --git a/documentation/content/zh-tw/books/developers-handbook/_index.adoc b/documentation/content/zh-tw/books/developers-handbook/_index.adoc index d74adf6ea3..4f2d623cd0 100644 --- a/documentation/content/zh-tw/books/developers-handbook/_index.adoc +++ b/documentation/content/zh-tw/books/developers-handbook/_index.adoc @@ -45,7 +45,7 @@ include::../../../../shared/authors.adoc[] include::../../../../shared/releases.adoc[] include::../../../../shared/zh-tw/mailing-lists.adoc[] include::../../../../shared/zh-tw/urls.adoc[] -:imagesdir: ../../../static/images/books/developers-handbook/ +:imagesdir: ../../../../static/images/books/developers-handbook/ :chapters-path: endif::[] @@ -55,7 +55,7 @@ include::../../../../shared/authors.adoc[] include::../../../../shared/releases.adoc[] include::../../../../shared/zh-tw/mailing-lists.adoc[] include::../../../../shared/zh-tw/urls.adoc[] -:imagesdir: ../../../static/images/books/developers-handbook/ +:imagesdir: ../../../../static/images/books/developers-handbook/ :chapters-path: endif::[] From owner-dev-commits-doc-all@freebsd.org Mon May 31 23:23:55 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DDD206330AE for ; Mon, 31 May 2021 23:23:55 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FvBF75s8rz3QCG; Mon, 31 May 2021 23:23:55 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B216A1920F; Mon, 31 May 2021 23:23:55 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VNNt74066394; Mon, 31 May 2021 23:23:55 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VNNtCK066393; Mon, 31 May 2021 23:23:55 GMT (envelope-from git) Date: Mon, 31 May 2021 23:23:55 GMT Message-Id: <202105312323.14VNNtCK066393@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Warner Losh Subject: git: 5fdd3fefdd - main - arch-handbook: Document kobj HEADER keyword MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: imp X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 5fdd3fefdd8c5ded4821f9969c650fc0ed9ba642 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 23:23:55 -0000 The branch main has been updated by imp: URL: https://cgit.FreeBSD.org/doc/commit/?id=5fdd3fefdd8c5ded4821f9969c650fc0ed9ba642 commit 5fdd3fefdd8c5ded4821f9969c650fc0ed9ba642 Author: Warner Losh AuthorDate: 2021-04-27 21:00:46 +0000 Commit: Warner Losh CommitDate: 2021-05-31 23:23:34 +0000 arch-handbook: Document kobj HEADER keyword The HEADER keyword is like the CODE keyword, except the lines go into the .h file. Sponsored by: Netflix --- .../content/en/books/arch-handbook/kobj/_index.adoc | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/documentation/content/en/books/arch-handbook/kobj/_index.adoc b/documentation/content/en/books/arch-handbook/kobj/_index.adoc index 8a91c0132c..32b64e3bbd 100644 --- a/documentation/content/en/books/arch-handbook/kobj/_index.adoc +++ b/documentation/content/en/books/arch-handbook/kobj/_index.adoc @@ -118,7 +118,7 @@ KOBJMETHOD(NAME, FUNC) The first step in using Kobj is to create an Interface. Creating the interface involves creating a template that the script [.filename]#src/sys/kern/makeobjops.pl# can use to generate the header and code for the method declarations and method lookup functions. -Within this template the following keywords are used: `#include`, `INTERFACE`, `CODE`, `METHOD`, `STATICMETHOD`, and `DEFAULT`. +Within this template the following keywords are used: `#include`, `INTERFACE`, `CODE`, `HEADER`, `METHOD`, `STATICMETHOD`, and `DEFAULT`. The `#include` statement and what follows it is copied verbatim to the head of the generated code file. @@ -155,6 +155,20 @@ CODE { }; .... +The `HEADER` keyword copies its arguments verbatim into the header file. +Its syntax is `HEADER { [whatever] };` + +For example: + +[.programlisting] +.... +HEADER { + struct mumble; + struct grumble; +} +}; +.... + The `METHOD` keyword describes a method. Its syntax is `METHOD [return type] [method name] { [object [, arguments]] };` From owner-dev-commits-doc-all@freebsd.org Mon May 31 23:23:57 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 243C8632E6A for ; Mon, 31 May 2021 23:23:57 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FvBF90GGlz3QR6; Mon, 31 May 2021 23:23:57 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D35F219210; Mon, 31 May 2021 23:23:56 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 14VNNu03066415; Mon, 31 May 2021 23:23:56 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 14VNNue9066414; Mon, 31 May 2021 23:23:56 GMT (envelope-from git) Date: Mon, 31 May 2021 23:23:56 GMT Message-Id: <202105312323.14VNNue9066414@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Warner Losh Subject: git: 293f155765 - main - arch-handbook: Document PROLOG and EPILOG MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: imp X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 293f155765ee12c857f818b9e9d9e94cc61323a4 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 May 2021 23:23:57 -0000 The branch main has been updated by imp: URL: https://cgit.FreeBSD.org/doc/commit/?id=293f155765ee12c857f818b9e9d9e94cc61323a4 commit 293f155765ee12c857f818b9e9d9e94cc61323a4 Author: Warner Losh AuthorDate: 2021-04-27 21:07:35 +0000 Commit: Warner Losh CommitDate: 2021-05-31 23:23:35 +0000 arch-handbook: Document PROLOG and EPILOG PROLOG and EPILOG modifiers are used to set code to insert before or after the method is called. It's use cases are limited. It is intended to only be used only for tracing or other profling. Sponsored by: Netflix --- documentation/content/en/books/arch-handbook/kobj/_index.adoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/documentation/content/en/books/arch-handbook/kobj/_index.adoc b/documentation/content/en/books/arch-handbook/kobj/_index.adoc index 32b64e3bbd..0b81112792 100644 --- a/documentation/content/en/books/arch-handbook/kobj/_index.adoc +++ b/documentation/content/en/books/arch-handbook/kobj/_index.adoc @@ -118,7 +118,7 @@ KOBJMETHOD(NAME, FUNC) The first step in using Kobj is to create an Interface. Creating the interface involves creating a template that the script [.filename]#src/sys/kern/makeobjops.pl# can use to generate the header and code for the method declarations and method lookup functions. -Within this template the following keywords are used: `#include`, `INTERFACE`, `CODE`, `HEADER`, `METHOD`, `STATICMETHOD`, and `DEFAULT`. +Within this template the following keywords are used: `#include`, `INTERFACE`, `CODE`, `EPILOG`, `HEADER`, `METHOD`, `PROLOG`, `STATICMETHOD`, and `DEFAULT`. The `#include` statement and what follows it is copied verbatim to the head of the generated code file. @@ -202,6 +202,9 @@ The `STATICMETHOD` keyword is used like the `METHOD` keyword except the kobj dat Instead `STATICMETHOD` relies on the Kobj data being referenced as 'ops'. This is also useful for calling methods directly out of a class's method table. +The `PROLOG` and `EPILOG` keywords sets inserts code immediately before or directly after the `METHOD` they are attached to. +This feature is used primarily for profiling situations where it's difficult to obtain the information in another way. + Other complete examples: [.programlisting] From owner-dev-commits-doc-all@freebsd.org Tue Jun 1 06:35:49 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 511D864A2B9 for ; Tue, 1 Jun 2021 06:35:49 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FvMqT08ztz3QsY; Tue, 1 Jun 2021 06:35:49 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id D661D1EBEC; Tue, 1 Jun 2021 06:35:48 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 1516ZmFW037103; Tue, 1 Jun 2021 06:35:48 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 1516Zmnj037102; Tue, 1 Jun 2021 06:35:48 GMT (envelope-from git) Date: Tue, 1 Jun 2021 06:35:48 GMT Message-Id: <202106010635.1516Zmnj037102@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Guangyuan Yang Subject: git: 231b9562c8 - main - porters-handbook: Fix typos and phrasing MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: ygy X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 231b9562c8714ccf53530acf5db94853e842a02f Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2021 06:35:49 -0000 The branch main has been updated by ygy: URL: https://cgit.FreeBSD.org/doc/commit/?id=231b9562c8714ccf53530acf5db94853e842a02f commit 231b9562c8714ccf53530acf5db94853e842a02f Author: Philipp Ost AuthorDate: 2021-06-01 06:35:17 +0000 Commit: Guangyuan Yang CommitDate: 2021-06-01 06:35:32 +0000 porters-handbook: Fix typos and phrasing --- documentation/content/en/books/porters-handbook/makefiles/_index.adoc | 4 ++-- documentation/content/en/books/porters-handbook/plist/_index.adoc | 2 +- documentation/content/en/books/porters-handbook/special/_index.adoc | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/content/en/books/porters-handbook/makefiles/_index.adoc b/documentation/content/en/books/porters-handbook/makefiles/_index.adoc index f80c96a952..ddf8d9e63a 100644 --- a/documentation/content/en/books/porters-handbook/makefiles/_index.adoc +++ b/documentation/content/en/books/porters-handbook/makefiles/_index.adoc @@ -4328,7 +4328,7 @@ For any of these dependency types: * `LIB_DEPENDS` * `RUN_DEPENDS` -When option _OPT_ is selected, the value of `PT_DEPTYPE`, if defined, is appended to `DEPTYPE`. `OPT_DEPTYPE_OFF` works the same, but when `OPT` is _not_ selected. For example: +When option _OPT_ is selected, the value of `OPT_DEPTYPE`, if defined, is appended to `DEPTYPE`. `OPT_DEPTYPE_OFF` works the same, but when `OPT` is _not_ selected. For example: [.programlisting] .... @@ -4760,7 +4760,7 @@ These macros do not add the installed files to [.filename]#pkg-plist#. They must [[install-documentation]] === Install Additional Documentation -If the software has some documentation other than the standard man and info pages that is useful for the user, install it under `DOCSDIR` This can be done, like the previous item, in the `post-install` target. +If the software has some documentation other than the standard man and info pages that is useful for the user, install it under `DOCSDIR`. This can be done, like the previous item, in the `post-install` target. Create a new directory for the port. The directory name is `DOCSDIR`. This usually equals `PORTNAME`. However, if the user might want different versions of the port to be installed at the same time, the whole `PKGNAME` can be used. diff --git a/documentation/content/en/books/porters-handbook/plist/_index.adoc b/documentation/content/en/books/porters-handbook/plist/_index.adoc index 4d6689b428..e89f1b6770 100644 --- a/documentation/content/en/books/porters-handbook/plist/_index.adoc +++ b/documentation/content/en/books/porters-handbook/plist/_index.adoc @@ -38,7 +38,7 @@ Some ports, particularly the `p5-` ports, need to change their [.filename]#pkg-p To make other substitutions, set `PLIST_SUB` with a list of `_VAR=VALUE_` pairs and instances of `%%_VAR_%%` will be substituted with _VALUE_ in [.filename]#pkg-plist#. -For instance, if a port installs many files in a version-specific subdirectory, use a placeholder for the version so that [.filename]#pkg-plist# does not have to be regenerated every time the port is updated. For example: +For instance, if a port installs many files in a version-specific subdirectory, use a placeholder for the version so that [.filename]#pkg-plist# does not have to be regenerated every time the port is updated. For example, set: [.programlisting] .... diff --git a/documentation/content/en/books/porters-handbook/special/_index.adoc b/documentation/content/en/books/porters-handbook/special/_index.adoc index 0e3951e091..64748f5290 100644 --- a/documentation/content/en/books/porters-handbook/special/_index.adoc +++ b/documentation/content/en/books/porters-handbook/special/_index.adoc @@ -161,7 +161,7 @@ USE_LDCONFIG= ${PREFIX}/lib/foo ${PREFIX}/lib/bar Please double-check, often this is not necessary at all or can be avoided through `-rpath` or setting `LD_RUN_PATH` during linking (see package:lang/mosml[] for an example), or through a shell-wrapper which sets `LD_LIBRARY_PATH` before invoking the binary, like package:www/seamonkey[] does. -When installing 32-bit libraries on 64-bit system, use `USE_LDCONFIG32` instead. +When installing 32-bit libraries on a 64-bit system, use `USE_LDCONFIG32` instead. If the software uses <>, and specifically `libtool`, add crossref:uses[uses-libtool,`USES=libtool`]. From owner-dev-commits-doc-all@freebsd.org Tue Jun 1 12:35:01 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C0BE1653A01 for ; Tue, 1 Jun 2021 12:35:01 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FvWnx4rcgz4vhm; Tue, 1 Jun 2021 12:35:01 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 8B1F123C0F; Tue, 1 Jun 2021 12:35:01 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 151CZ1kO017439; Tue, 1 Jun 2021 12:35:01 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 151CZ14O017438; Tue, 1 Jun 2021 12:35:01 GMT (envelope-from git) Date: Tue, 1 Jun 2021 12:35:01 GMT Message-Id: <202106011235.151CZ14O017438@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Ceri Davies Subject: git: a10df4fef6 - main - documentation/Makefile: update lead-in note on common targets MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: ceri X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: a10df4fef638b2c3007202ef48a059dcffbfb76f Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2021 12:35:01 -0000 The branch main has been updated by ceri: URL: https://cgit.FreeBSD.org/doc/commit/?id=a10df4fef638b2c3007202ef48a059dcffbfb76f commit a10df4fef638b2c3007202ef48a059dcffbfb76f Author: Ceri Davies AuthorDate: 2021-06-01 12:32:09 +0000 Commit: Ceri Davies CommitDate: 2021-06-01 12:32:09 +0000 documentation/Makefile: update lead-in note on common targets Approved by: blackend (mentor) --- documentation/Makefile | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/documentation/Makefile b/documentation/Makefile index 24b6090cd3..d8765511e1 100644 --- a/documentation/Makefile +++ b/documentation/Makefile @@ -6,7 +6,8 @@ # Targets intended for use on the command line # # all (default) - generate the books TOC and compile all the documentation -# run - serves the built documentation site for local browsing +# run - serves the built documentation site for local browsing +# pdf - build PDF versions of the articles and books. # # The run target uses hugo's built-in webserver to make the documentation site # available for local browsing. The documentation should have been built prior From owner-dev-commits-doc-all@freebsd.org Tue Jun 1 12:35:02 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E61CB6536B9 for ; Tue, 1 Jun 2021 12:35:02 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FvWny5dMzz4vVF; Tue, 1 Jun 2021 12:35:02 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id A943D23AAC; Tue, 1 Jun 2021 12:35:02 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 151CZ21R017460; Tue, 1 Jun 2021 12:35:02 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 151CZ2jY017459; Tue, 1 Jun 2021 12:35:02 GMT (envelope-from git) Date: Tue, 1 Jun 2021 12:35:02 GMT Message-Id: <202106011235.151CZ2jY017459@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Ceri Davies Subject: git: 6dbbe7fae5 - main - documentation/Makefile: un-.PHONY generate-pgpkeys-txt target MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: ceri X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 6dbbe7fae560ad67d290624b28687d6c758ba4a8 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2021 12:35:03 -0000 The branch main has been updated by ceri: URL: https://cgit.FreeBSD.org/doc/commit/?id=6dbbe7fae560ad67d290624b28687d6c758ba4a8 commit 6dbbe7fae560ad67d290624b28687d6c758ba4a8 Author: Ceri Davies AuthorDate: 2021-06-01 12:33:14 +0000 Commit: Ceri Davies CommitDate: 2021-06-01 12:33:14 +0000 documentation/Makefile: un-.PHONY generate-pgpkeys-txt target Approved by: blackend (mentor) --- documentation/Makefile | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/documentation/Makefile b/documentation/Makefile index d8765511e1..a10461f4ae 100644 --- a/documentation/Makefile +++ b/documentation/Makefile @@ -72,7 +72,9 @@ generate-books-toc: .PHONY ${PYTHON_CMD} ./tools/books-toc-tables-creator.py -l ${LANGUAGES} ${PYTHON_CMD} ./tools/books-toc-examples-creator.py -l ${LANGUAGES} -generate-pgpkeys-txt: .PHONY +generate-pgpkeys-txt: static/pgpkeys/pgpkeys.txt + +static/pgpkeys/pgpkeys.txt: static/pgpkeys/*key ${RUBY_CMD} ./tools/global-pgpkeys-creator.rb run-local: .PHONY From owner-dev-commits-doc-all@freebsd.org Tue Jun 1 16:37:07 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E7D73657C93 for ; Tue, 1 Jun 2021 16:37:07 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fvd9H60Mjz3mfV; Tue, 1 Jun 2021 16:37:07 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B613826F8E; Tue, 1 Jun 2021 16:37:07 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 151Gb7VS039102; Tue, 1 Jun 2021 16:37:07 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 151Gb7fC039101; Tue, 1 Jun 2021 16:37:07 GMT (envelope-from git) Date: Tue, 1 Jun 2021 16:37:07 GMT Message-Id: <202106011637.151Gb7fC039101@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Li-Wen Hsu Subject: git: 2f00015371 - main - Add freebsd-friday-2021-06-04 event MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: lwhsu X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 2f00015371f335855fa1ded835d40b7be36ab04a Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2021 16:37:08 -0000 The branch main has been updated by lwhsu (ports, src committer): URL: https://cgit.FreeBSD.org/doc/commit/?id=2f00015371f335855fa1ded835d40b7be36ab04a commit 2f00015371f335855fa1ded835d40b7be36ab04a Author: Li-Wen Hsu AuthorDate: 2021-06-01 15:22:01 +0000 Commit: Li-Wen Hsu CommitDate: 2021-06-01 16:36:26 +0000 Add freebsd-friday-2021-06-04 event Reviewed by: ceri Differential Revision: https://reviews.freebsd.org/D30596 --- website/data/en/events/events2021.toml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/website/data/en/events/events2021.toml b/website/data/en/events/events2021.toml index bf812f07da..faf4e30e88 100644 --- a/website/data/en/events/events2021.toml +++ b/website/data/en/events/events2021.toml @@ -56,6 +56,15 @@ endDate = "2021-05-26" site = "live.FreeBSD.org" description = "On May 26th at 02:00 UTC we will hold a \"FreeBSD Office Hours\", an interactive online event where users, contributors, and developers can ask questions or to offer comments. The topic will be \"Best Practices virtual panel discussion\", hosted by Warner Losh. For more information, please see the Office Hours page on the FreeBSD wiki." +[[events]] +id = "freebsd-friday-2021-06-04" +name = "FreeBSD Friday: An Introduction to BastilleBSD" +url = "https://live.freebsd.org/FreeBSD/freebsdfriday/" +startDate = "2021-06-04" +endDate = "2021-06-04" +site = "live.FreeBSD.org" +description = "On June 4th 2021 from 17:00 UTC there will be an 1 hour live streaming session of the FreeBSD Fridays. The topic of this week is: \"An Introduction to BastilleBSD\" by Christer Edwards." + [[events]] id = "devsummit-202106" name = "June 2021 FreeBSD Developer Summit" From owner-dev-commits-doc-all@freebsd.org Tue Jun 1 16:56:10 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DAB1565823F for ; Tue, 1 Jun 2021 16:56:10 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FvdbG40sqz3qCc; Tue, 1 Jun 2021 16:56:10 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7195926E7F; Tue, 1 Jun 2021 16:56:10 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 151GuAPr065023; Tue, 1 Jun 2021 16:56:10 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 151GuAOq065022; Tue, 1 Jun 2021 16:56:10 GMT (envelope-from git) Date: Tue, 1 Jun 2021 16:56:10 GMT Message-Id: <202106011656.151GuAOq065022@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: a8f517b59c - main - de/: Fix include links for PDF. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: a8f517b59c4383329127523e48d1f5d7393f811e Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2021 16:56:10 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=a8f517b59c4383329127523e48d1f5d7393f811e commit a8f517b59c4383329127523e48d1f5d7393f811e Author: Marc Fonvieille AuthorDate: 2021-06-01 16:41:46 +0000 Commit: Marc Fonvieille CommitDate: 2021-06-01 16:55:38 +0000 de/: Fix include links for PDF. --- documentation/content/de/articles/contributing/_index.adoc | 12 ++++++++++++ .../content/de/articles/freebsd-update-server/_index.adoc | 10 ++++++++++ documentation/content/de/articles/leap-seconds/_index.adoc | 10 ++++++++++ documentation/content/de/articles/linux-users/_index.adoc | 10 ++++++++++ documentation/content/de/articles/nanobsd/_index.adoc | 10 ++++++++++ documentation/content/de/articles/new-users/_index.adoc | 14 +++++++++++++- .../content/de/articles/port-mentor-guidelines/_index.adoc | 10 ++++++++++ documentation/content/de/books/handbook/basics/_index.adoc | 12 ++++++------ 8 files changed, 81 insertions(+), 7 deletions(-) diff --git a/documentation/content/de/articles/contributing/_index.adoc b/documentation/content/de/articles/contributing/_index.adoc index 2fa43e3832..7fc45f3cd8 100644 --- a/documentation/content/de/articles/contributing/_index.adoc +++ b/documentation/content/de/articles/contributing/_index.adoc @@ -20,8 +20,20 @@ trademarks: ["freebsd", "ieee", "general"] :figure-caption: Abbildung :example-caption: Beispiel +ifeval::["{backend}" == "html5"] include::shared/de/mailing-lists.adoc[] include::shared/de/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/de/urls.adoc[] +include::../../../../shared/de/mailing-lists.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/de/urls.adoc[] +include::../../../../shared/de/mailing-lists.adoc[] +endif::[] [.abstract-title] Zusammenfassung diff --git a/documentation/content/de/articles/freebsd-update-server/_index.adoc b/documentation/content/de/articles/freebsd-update-server/_index.adoc index b70d36587a..5b0b201a58 100644 --- a/documentation/content/de/articles/freebsd-update-server/_index.adoc +++ b/documentation/content/de/articles/freebsd-update-server/_index.adoc @@ -22,7 +22,17 @@ trademarks: ["freebsd", "amd", "intel", "general"] :figure-caption: Abbildung :example-caption: Beispiel +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +endif::[] [.abstract-title] Zusammenfassung diff --git a/documentation/content/de/articles/leap-seconds/_index.adoc b/documentation/content/de/articles/leap-seconds/_index.adoc index d080b2b00d..990497a624 100644 --- a/documentation/content/de/articles/leap-seconds/_index.adoc +++ b/documentation/content/de/articles/leap-seconds/_index.adoc @@ -17,7 +17,17 @@ releaseinfo: "$FreeBSD$" :figure-caption: Abbildung :example-caption: Beispiel +ifeval::["{backend}" == "html5"] include::shared/de/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/de/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/de/urls.adoc[] +endif::[] ''' diff --git a/documentation/content/de/articles/linux-users/_index.adoc b/documentation/content/de/articles/linux-users/_index.adoc index 983de0c0f3..6960975bb5 100644 --- a/documentation/content/de/articles/linux-users/_index.adoc +++ b/documentation/content/de/articles/linux-users/_index.adoc @@ -21,7 +21,17 @@ trademarks: ["freebsd", "intel", "redhat", "linux", "unix", "general"] :figure-caption: Abbildung :example-caption: Beispiel +ifeval::["{backend}" == "html5"] include::shared/de/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/de/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/de/urls.adoc[] +endif::[] [.abstract-title] Zusammenfassung diff --git a/documentation/content/de/articles/nanobsd/_index.adoc b/documentation/content/de/articles/nanobsd/_index.adoc index 825e00ed3e..5f3bb2bdb9 100644 --- a/documentation/content/de/articles/nanobsd/_index.adoc +++ b/documentation/content/de/articles/nanobsd/_index.adoc @@ -20,7 +20,17 @@ trademarks: ["freebsd", "general"] :figure-caption: Abbildung :example-caption: Beispiel +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +endif::[] [.abstract-title] Zusammenfassung diff --git a/documentation/content/de/articles/new-users/_index.adoc b/documentation/content/de/articles/new-users/_index.adoc index cdcaf55611..46f5c10add 100644 --- a/documentation/content/de/articles/new-users/_index.adoc +++ b/documentation/content/de/articles/new-users/_index.adoc @@ -21,8 +21,20 @@ trademarks: ["freebsd", "ibm", "microsoft", "opengroup", "general"] :figure-caption: Abbildung :example-caption: Beispiel -include::shared/de/urls.adoc[] +ifeval::["{backend}" == "html5"] include::shared/de/mailing-lists.adoc[] +include::shared/de/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/de/urls.adoc[] +include::../../../../shared/de/mailing-lists.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/de/urls.adoc[] +include::../../../../shared/de/mailing-lists.adoc[] +endif::[] [.abstract-title] Zusammenfassung diff --git a/documentation/content/de/articles/port-mentor-guidelines/_index.adoc b/documentation/content/de/articles/port-mentor-guidelines/_index.adoc index 9a4a149bf5..4ee098de90 100644 --- a/documentation/content/de/articles/port-mentor-guidelines/_index.adoc +++ b/documentation/content/de/articles/port-mentor-guidelines/_index.adoc @@ -20,7 +20,17 @@ releaseinfo: "$FreeBSD$" :figure-caption: Abbildung :example-caption: Beispiel +ifeval::["{backend}" == "html5"] include::shared/de/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/de/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/de/urls.adoc[] +endif::[] ''' diff --git a/documentation/content/de/books/handbook/basics/_index.adoc b/documentation/content/de/books/handbook/basics/_index.adoc index dd72d5e028..195d22a1ef 100644 --- a/documentation/content/de/books/handbook/basics/_index.adoc +++ b/documentation/content/de/books/handbook/basics/_index.adoc @@ -987,27 +987,27 @@ Betrachten wir die drei Dateisysteme `A`, `B` und `C`. Jedes Dateisystem besitzt Das Wurzeldateisystem soll `A` sein. man:ls[1] zeigt darin die beiden Verzeichnisse [.filename]#A1# und [.filename]#A2# an. Der Verzeichnisbaum sieht wie folgt aus: -image::../../../images/handbook/basics/example-dir1.png[] +image::example-dir1.png[] Ein Dateisystem wird in einem Verzeichnis eines anderen Dateisystems eingehangen. Wir hängen nun das Dateisystem `B` in das Verzeichnis [.filename]#A1# ein. Das Wurzelverzeichnis von `B` ersetzt nun das Verzeichnis [.filename]#A1# und die Verzeichnisse des Dateisystems `B` werden sichtbar: -image::../../../images/handbook/basics/example-dir2.png[] +image::example-dir2.png[] Jede Datei in den Verzeichnissen [.filename]#B1# oder [.filename]#B2# kann über den Pfad [.filename]#/A1/B1# oder [.filename]#/A1/B2# erreicht werden. Dateien aus dem Verzeichnis [.filename]#/A1# sind jetzt verborgen. Wenn das Dateisystem `B` wieder _abgehangen_ wird (umount), erscheinen die verborgenen Dateien wieder. Wenn das Dateisystem `B` unter dem Verzeichnis [.filename]#A2# eingehangen würde, sähe der Verzeichnisbaum so aus: -image::../../../images/handbook/basics/example-dir3.png[] +image::example-dir3.png[] Die Dateien des Dateisystems `B` wären unter den Pfaden [.filename]#/A2/B1# und [.filename]#/A2/B2# erreichbar. Dateisysteme können übereinander eingehangen werden. Der folgende Baum entsteht, wenn im letzten Beispiel das Dateisystem `C` in das Verzeichnis [.filename]#B1# des Dateisystems `B` eingehangen wird: -image::../../../images/handbook/basics/example-dir4.png[] +image::example-dir4.png[] `C` könnte auch im Verzeichnis [.filename]#A1# eingehangen werden: -image::../../../images/handbook/basics/example-dir5.png[] +image::example-dir5.png[] Sie können sogar mit nur einem großen Dateisystem auskommen. Dies hat mehrere Nachteile und einen Vorteil. @@ -1126,7 +1126,7 @@ Das folgende Diagramm zeigt die Sicht von FreeBSD auf die erste SATA-Festplatte Jede der vier Partitionen enthält ein Dateisystem. Das Wurzeldateisystem ist die `a`-Partition. In der `d`-Partition befindet sich [.filename]#/var# und in der `f`-Partition befindet sich [.filename]#/usr#. Die `c`-Partition bezieht sich auf die gesamte Slice und wird nicht für gewöhnliche Partitionen verwendet. -image::../../../images/handbook/basics/disk-layout.png[] +image::disk-layout.png[] ==== From owner-dev-commits-doc-all@freebsd.org Tue Jun 1 19:33:58 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id C487465BCF5 for ; Tue, 1 Jun 2021 19:33:58 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fvj5L59DPz4ZpC; Tue, 1 Jun 2021 19:33:58 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 998CE15AD; Tue, 1 Jun 2021 19:33:58 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 151JXwHc077941; Tue, 1 Jun 2021 19:33:58 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 151JXwJ4077940; Tue, 1 Jun 2021 19:33:58 GMT (envelope-from git) Date: Tue, 1 Jun 2021 19:33:58 GMT Message-Id: <202106011933.151JXwJ4077940@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Wolfram Schneider Subject: git: 63a97bf0b0 - main - Restore the OpenSearch URL for ports. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: wosch X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 63a97bf0b02fcad83a05d8d5a7ccd4540f089fb9 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2021 19:33:58 -0000 The branch main has been updated by wosch: URL: https://cgit.FreeBSD.org/doc/commit/?id=63a97bf0b02fcad83a05d8d5a7ccd4540f089fb9 commit 63a97bf0b02fcad83a05d8d5a7ccd4540f089fb9 Author: Wolfram Schneider AuthorDate: 2021-06-01 19:33:11 +0000 Commit: Wolfram Schneider CommitDate: 2021-06-01 19:33:11 +0000 Restore the OpenSearch URL for ports. This fix 75e9a0b144ec4ec451e1bc07d0e4756a8a577e47 PR: 256350 --- website/themes/beastie/static/opensearch/ports.xml | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/website/themes/beastie/static/opensearch/ports.xml b/website/themes/beastie/static/opensearch/ports.xml new file mode 100644 index 0000000000..aac92aa76e --- /dev/null +++ b/website/themes/beastie/static/opensearch/ports.xml @@ -0,0 +1,17 @@ + + + + + + FreeBSD Ports + FreeBSD Ports and Packages Collection + FreeBSD Ports and Packages Collection + + The FreeBSD Project + https://www.freebsd.org/ + https://www.freebsd.org/favicon.ico + en + ISO-8859-1 + + From owner-dev-commits-doc-all@freebsd.org Tue Jun 1 19:43:14 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id ECE5365BF92 for ; Tue, 1 Jun 2021 19:43:14 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FvjJ26Q2Fz4bXj; Tue, 1 Jun 2021 19:43:14 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C42A41717; Tue, 1 Jun 2021 19:43:14 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 151JhEMm090935; Tue, 1 Jun 2021 19:43:14 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 151JhEoK090934; Tue, 1 Jun 2021 19:43:14 GMT (envelope-from git) Date: Tue, 1 Jun 2021 19:43:14 GMT Message-Id: <202106011943.151JhEoK090934@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Wolfram Schneider Subject: git: c2fb54e693 - main - Restore the OpenSearch URL for ports MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: wosch X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: c2fb54e693935407cca3e34f0a2a197927d45a2f Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2021 19:43:15 -0000 The branch main has been updated by wosch: URL: https://cgit.FreeBSD.org/doc/commit/?id=c2fb54e693935407cca3e34f0a2a197927d45a2f commit c2fb54e693935407cca3e34f0a2a197927d45a2f Author: Wolfram Schneider AuthorDate: 2021-06-01 19:42:52 +0000 Commit: Wolfram Schneider CommitDate: 2021-06-01 19:42:52 +0000 Restore the OpenSearch URL for ports PR: 256350 --- website/themes/beastie/layouts/partials/site-head.html | 1 + 1 file changed, 1 insertion(+) diff --git a/website/themes/beastie/layouts/partials/site-head.html b/website/themes/beastie/layouts/partials/site-head.html index c91c8bee11..11f858b53d 100644 --- a/website/themes/beastie/layouts/partials/site-head.html +++ b/website/themes/beastie/layouts/partials/site-head.html @@ -13,6 +13,7 @@ + From owner-dev-commits-doc-all@freebsd.org Tue Jun 1 20:51:34 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id F134265DAAC for ; Tue, 1 Jun 2021 20:51:34 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fvkpt6ZMFz4k1J; Tue, 1 Jun 2021 20:51:34 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C9E5B24C7; Tue, 1 Jun 2021 20:51:34 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 151KpY01080285; Tue, 1 Jun 2021 20:51:34 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 151KpY8V080284; Tue, 1 Jun 2021 20:51:34 GMT (envelope-from git) Date: Tue, 1 Jun 2021 20:51:34 GMT Message-Id: <202106012051.151KpY8V080284@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Gordon Tetlow Subject: git: caf6116627 - main - Add EN-21:17. Approved by: so MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: gordon X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: caf6116627fb89e2d4020f04255c0133d6faaa58 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Jun 2021 20:51:35 -0000 The branch main has been updated by gordon (src committer): URL: https://cgit.FreeBSD.org/doc/commit/?id=caf6116627fb89e2d4020f04255c0133d6faaa58 commit caf6116627fb89e2d4020f04255c0133d6faaa58 Author: Gordon Tetlow AuthorDate: 2021-06-01 20:51:11 +0000 Commit: Gordon Tetlow CommitDate: 2021-06-01 20:51:11 +0000 Add EN-21:17. Approved by: so --- website/data/security/errata.toml | 4 + .../advisories/FreeBSD-EN-21:17.libradius.asc | 147 +++++++++++++++++++++ .../security/patches/EN-21:17/libradius.patch | 16 +++ .../security/patches/EN-21:17/libradius.patch.asc | 16 +++ 4 files changed, 183 insertions(+) diff --git a/website/data/security/errata.toml b/website/data/security/errata.toml index de0a6f640f..4c1b2b1704 100644 --- a/website/data/security/errata.toml +++ b/website/data/security/errata.toml @@ -1,6 +1,10 @@ # Sort errata notices by year, month and day # $FreeBSD$ +[[notices]] +name = "FreeBSD-EN-21:17.libradius" +date = "2021-06-01" + [[notices]] name = "FreeBSD-EN-21:16.bc" date = "2021-05-26" diff --git a/website/static/security/advisories/FreeBSD-EN-21:17.libradius.asc b/website/static/security/advisories/FreeBSD-EN-21:17.libradius.asc new file mode 100644 index 0000000000..889553b23f --- /dev/null +++ b/website/static/security/advisories/FreeBSD-EN-21:17.libradius.asc @@ -0,0 +1,147 @@ +-----BEGIN PGP SIGNED MESSAGE----- +Hash: SHA512 + +============================================================================= +FreeBSD-EN-21:17.libradius Errata Notice + The FreeBSD Project + +Topic: Incorrect validation in rad_get_attr(3) + +Category: core +Module: libradius +Announced: 2021-06-01 +Affects: All supported versions of FreeBSD. +Corrected: 2021-05-28 17:00:19 UTC (stable/13, 13.0-STABLE) + 2021-06-01 20:26:32 UTC (releng/13.0, 13.0-RELEASE-p2) + 2021-05-28 17:03:20 UTC (stable/12, 12.2-STABLE) + 2021-06-01 20:38:39 UTC (releng/12.2, 12.2-RELEASE-p8) + 2021-05-28 17:02:43 UTC (stable/11, 11.4-STABLE) + 2021-05-28 20:37:54 UTC (releng/11.4, 11.4-RELEASE-p11) + +For general information regarding FreeBSD Errata Notices and Security +Advisories, including descriptions of the fields above, security +branches, and the following sections, please visit +. + +I. Background + +libradius(3) is a client and server library implementing the Remote +Authentication Dial In User Service (RADIUS) protocol. It is used by +pam_radius(8) and mpd5 (available in the ports tree as net/mpd5). + +II. Problem Description + +The patch for FreeBSD-SA-21:12.libradius modified rad_get_attr(3) to +verify that an attribute length smaller than the minimum required for +the attribute type and length fields is disallowed. This check may fail +incorrectly for the final attribute in a RADIUS message. + +III. Impact + +The bug may cause request validation to fail when it should succeed. +This can result in errors in applications making using of libradius(3). + +IV. Workaround + +No workaround is available. Systems not using libradius(3) are unaffected. + +V. Solution + +Upgrade your system to a supported FreeBSD stable or release / security +branch (releng) dated after the correction date. + +Perform one of the following: + +1) To update your system via a binary patch: + +Systems running a RELEASE version of FreeBSD on the amd64, i386, or +(on FreeBSD 13 and later) arm64 platforms can be updated via the +freebsd-update(8) utility: + +# freebsd-update fetch +# freebsd-update install + +2) To update your system via a source code patch: + +The following patches have been verified to apply to the applicable +FreeBSD release branches. + +a) Download the relevant patch from the location below, and verify the +detached PGP signature using your PGP utility. + +# fetch https://security.FreeBSD.org/patches/EN-21:17/libradius.patch +# fetch https://security.FreeBSD.org/patches/EN-21:17/libradius.patch.asc +# gpg --verify libradius.patch.asc + +b) Apply the patch. Execute the following commands as root: + +# cd /usr/src +# patch < /path/to/patch + +c) Recompile the operating system using buildworld and installworld as +described in . + +Restart all daemons that use the library, or reboot the system. + +VI. Correction details + +This issue is corrected by the corresponding Git commit hash or Subversion +revision number in the following stable and release branches: + +Branch/path Hash Revision +- ------------------------------------------------------------------------- +stable/13/ f9972532343b stable/13-n245792 +releng/13.0/ 8acc450613c3 releng/13.0-n244745 +stable/12/ r369897 +releng/12.2/ r369921 +stable/11/ r369896 +releng/11.4/ r369919 +- ------------------------------------------------------------------------- + +For FreeBSD 13 and later: + +Run the following command to see which files were modified by a +particular commit: + +# git show --stat + +Or visit the following URL, replacing NNNNNN with the hash: + + + +To determine the commit count in a working tree (for comparison against +nNNNNNN in the table above), run: + +# git rev-list --count --first-parent HEAD + +For FreeBSD 12 and earlier: + +Run the following command to see which files were modified by a particular +revision, replacing NNNNNN with the revision number: + +# svn diff -cNNNNNN --summarize svn://svn.freebsd.org/base + +Or visit the following URL, replacing NNNNNN with the revision number: + + + +VII. References + +The latest revision of this advisory is available at + +-----BEGIN PGP SIGNATURE----- + +iQIzBAEBCgAdFiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAmC2nUcACgkQ05eS9J6n +5cIyuxAAgNcgrQ/+3NRWPk8N0iqjIs5fN0HHdKF91o8FtCel9JW0UXXH9LZEsJiX +5twBTXHy8QL5yleJy83KDgHtIAKFTgILr2NaKBsc9T10sKJ7QWqpTUYKy9YXbqfO +3eX2+60j5LVfazoRMrPZotLxvvexa3imHQh4IrUEr/eDdUs1kB/fIc1bwi6sBksK +5Mqg6rlm1FusruUFfRynEUCQY7MhuFMTPUDvOOu8bvfmYK+sFB2lyfH1mxv7eaNA +LtiTrP/EcMDxpxbPL+fwEJgHnz50K4UIwaqpt9x46z3tNEDB/NJI5XWJ8KHG7liW +mJvPJIhu0QV2+Q04r5zqF9Io8PSulowS7NYxgGwcFXL7ZquLFxR2w/IdPkkqoLmZ +kTHW3Zz2kyDDJ7c3kg2dafolMS2G5MmUy91cIpR8T6o4ARYHIHuojXE4E8M2JUPQ +GV/HP0keMNKHRAy674Ie1Pa+Lmzwa1o1MNj/znF/8kR7pFqY60TqQ+h2jsHKO+ov +TZEjVf886LOmw6z/q7s2WBl2sq2JMiffWoFBx6URGKPtjCYYOWbC4AocsbAeu4a1 +5aNOa5otm25JjSZi6h0nepbw/QQHhR6LgqAIJue1bD4uA0Sbhf4Vwcbte1aMasGs +Te0nK0Q2QAdzfSI7TJdzAazXPHeqDfWnKAw2h57jJnMQH5IbMss= +=lZku +-----END PGP SIGNATURE----- diff --git a/website/static/security/patches/EN-21:17/libradius.patch b/website/static/security/patches/EN-21:17/libradius.patch new file mode 100644 index 0000000000..4f8e05c631 --- /dev/null +++ b/website/static/security/patches/EN-21:17/libradius.patch @@ -0,0 +1,16 @@ +--- lib/libradius/radlib.c.orig ++++ lib/libradius/radlib.c +@@ -964,7 +964,12 @@ + } + type = h->in[h->in_pos++]; + len = h->in[h->in_pos++]; +- if (len < 2 || h->in_pos + len > h->in_len) { ++ if (len < 2) { ++ generr(h, "Malformed attribute in response"); ++ return -1; ++ } ++ len -= 2; ++ if (h->in_pos + len > h->in_len) { + generr(h, "Malformed attribute in response"); + return -1; + } diff --git a/website/static/security/patches/EN-21:17/libradius.patch.asc b/website/static/security/patches/EN-21:17/libradius.patch.asc new file mode 100644 index 0000000000..fdc7c1af1e --- /dev/null +++ b/website/static/security/patches/EN-21:17/libradius.patch.asc @@ -0,0 +1,16 @@ +-----BEGIN PGP SIGNATURE----- + +iQIzBAABCgAdFiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAmC2nUgACgkQ05eS9J6n +5cLZcxAApmo7ozxwyMyLpvozf94MtA4spYgM3/MQb8WiO4gd1FkQOKjqyLVTnSF3 +Hbb8VTrhDp13K5o5v4wCtF102P5LWnRC1Ny0ivOGVBmtOnZsDsMHCH1FSSGE8V9z +8kFtFWSxaW5GKyA8KWHNxfWnxbwlrK0PXNBYgcGbXv8t1LBO/OJ6AKv7ghuNHaSR +wPcLekQXRc4AyjkqNETiXLwc+zUTXT9uEgbtQw9TgFjhP15R1EIwFBfL9IdyLaW3 +8cShW2JbByCIPocVzCjZGbgLYWXGoysrIVTM7bKMvJmmOUbP++b+WDpFhdhDQh7v +RYpkBcU4uSsSKmMp/y9b9oJf0s2ARkrK5TJphQ3hecdpINFnQeq2jC1YP95DuW+U +9JARIvL1R8bQgdg3BihpZUgpdV0nOLc+V5rTTu7zbB5mhc1PdppIUKHOS26bmzbP +lIaqQb3npiCMslcjsybYNCpYfLIGbPP+aoSzvu/uAOkXhWp4CPlwvCEberM8jtVo +h7/3XmfzMkKqpf86OVm7/xXxPQgP/F5HZm66hFeaUZOIutAKcmJGkOaH3gzO1U9N +oyUQPbDkbTEUKuGRnxHBXf3ne6KUfxx8k6zq0Xr9St5MXSRjLH8gdfSyTS4EgXtb +s9XrgdHfvsJlOff/p3m17sEm4hrX3fXJeX1e+adG54N4rldPgHM= +=CECh +-----END PGP SIGNATURE----- From owner-dev-commits-doc-all@freebsd.org Wed Jun 2 13:16:59 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D6F9164366D for ; Wed, 2 Jun 2021 13:16:59 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fw8gv5Qm7z3Lng; Wed, 2 Jun 2021 13:16:59 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9CB62175F8; Wed, 2 Jun 2021 13:16:59 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 152DGxjC085315; Wed, 2 Jun 2021 13:16:59 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 152DGxcN085314; Wed, 2 Jun 2021 13:16:59 GMT (envelope-from git) Date: Wed, 2 Jun 2021 13:16:59 GMT Message-Id: <202106021316.152DGxcN085314@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Mateusz Piotrowski <0mp@FreeBSD.org> Subject: git: bf0e170bf3 - main - handbook: Update HPLIP links MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: 0mp X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: bf0e170bf35112360aa97c47e60129e91d24b8bf Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2021 13:16:59 -0000 The branch main has been updated by 0mp: URL: https://cgit.FreeBSD.org/doc/commit/?id=bf0e170bf35112360aa97c47e60129e91d24b8bf commit bf0e170bf35112360aa97c47e60129e91d24b8bf Author: Mateusz Piotrowski <0mp@FreeBSD.org> AuthorDate: 2021-06-02 13:15:36 +0000 Commit: Mateusz Piotrowski <0mp@FreeBSD.org> CommitDate: 2021-06-02 13:17:15 +0000 handbook: Update HPLIP links While here, start new sentences on newlines. --- documentation/content/en/books/handbook/printing/_index.adoc | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/documentation/content/en/books/handbook/printing/_index.adoc b/documentation/content/en/books/handbook/printing/_index.adoc index 4731496b77..87f618fb40 100644 --- a/documentation/content/en/books/handbook/printing/_index.adoc +++ b/documentation/content/en/books/handbook/printing/_index.adoc @@ -762,7 +762,11 @@ CUPS is a popular printing system available on many operating systems. Using CUP [[printing-other-hplip]] === HPLIP -Hewlett Packard provides a printing system that supports many of their inkjet and laser printers. The port is package:print/hplip[]. The main web page is at http://hplipopensource.com/hplip-web/index.html[]. The port handles all the installation details on FreeBSD. Configuration information is shown at http://hplipopensource.com/hplip-web/install/manual/hp_setup.html[]. +Hewlett Packard provides a printing system that supports many of their inkjet and laser printers. +The port is package:print/hplip[]. +The main web page is at https://developers.hp.com/hp-linux-imaging-and-printing[]. +The port handles all the installation details on FreeBSD. +Configuration information is shown at https://developers.hp.com/hp-linux-imaging-and-printing/install[]. [[printing-other-lprng]] === LPRng From owner-dev-commits-doc-all@freebsd.org Wed Jun 2 16:59:58 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D95F4646FF6 for ; Wed, 2 Jun 2021 16:59:58 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FwFdB5t9sz3vZM; Wed, 2 Jun 2021 16:59:58 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id A80C21A827; Wed, 2 Jun 2021 16:59:58 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 152Gxwpm080405; Wed, 2 Jun 2021 16:59:58 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 152Gxw35080404; Wed, 2 Jun 2021 16:59:58 GMT (envelope-from git) Date: Wed, 2 Jun 2021 16:59:58 GMT Message-Id: <202106021659.152Gxw35080404@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: 75cf5289e3 - main - nl/articles: Fix include links for PDF. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 75cf5289e3211fe307f55d84e72e773d1778da74 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2021 16:59:58 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=75cf5289e3211fe307f55d84e72e773d1778da74 commit 75cf5289e3211fe307f55d84e72e773d1778da74 Author: Marc Fonvieille AuthorDate: 2021-06-02 16:46:17 +0000 Commit: Marc Fonvieille CommitDate: 2021-06-02 16:46:17 +0000 nl/articles: Fix include links for PDF. --- documentation/content/nl/articles/contributing/_index.adoc | 12 ++++++++++++ documentation/content/nl/articles/leap-seconds/_index.adoc | 10 ++++++++++ .../content/nl/articles/problem-reports/_index.adoc | 12 ++++++++++++ 3 files changed, 34 insertions(+) diff --git a/documentation/content/nl/articles/contributing/_index.adoc b/documentation/content/nl/articles/contributing/_index.adoc index e246ec0427..25197f1e74 100644 --- a/documentation/content/nl/articles/contributing/_index.adoc +++ b/documentation/content/nl/articles/contributing/_index.adoc @@ -23,8 +23,20 @@ trademarks: ["freebsd", "ieee", "general"] :figure-caption: Afbeelding :example-caption: Voorbeeld +ifeval::["{backend}" == "html5"] include::shared/nl/mailing-lists.adoc[] include::shared/nl/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/nl/mailing-lists.adoc[] +include::../../../../shared/nl/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/nl/mailing-lists.adoc[] +include::../../../../shared/nl/urls.adoc[] +endif::[] [.abstract-title] Samenvatting diff --git a/documentation/content/nl/articles/leap-seconds/_index.adoc b/documentation/content/nl/articles/leap-seconds/_index.adoc index 189e516b08..9f63db3c58 100644 --- a/documentation/content/nl/articles/leap-seconds/_index.adoc +++ b/documentation/content/nl/articles/leap-seconds/_index.adoc @@ -20,7 +20,17 @@ releaseinfo: "$FreeBSD$" :figure-caption: Afbeelding :example-caption: Voorbeeld +ifeval::["{backend}" == "html5"] include::shared/nl/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/nl/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/nl/urls.adoc[] +endif::[] ''' diff --git a/documentation/content/nl/articles/problem-reports/_index.adoc b/documentation/content/nl/articles/problem-reports/_index.adoc index b5977755a8..c7863603b4 100644 --- a/documentation/content/nl/articles/problem-reports/_index.adoc +++ b/documentation/content/nl/articles/problem-reports/_index.adoc @@ -24,8 +24,20 @@ trademarks: ["freebsd", "ibm", "intel", "sparc", "sun", "general"] :figure-caption: Afbeelding :example-caption: Voorbeeld +ifeval::["{backend}" == "html5"] include::shared/nl/mailing-lists.adoc[] include::shared/nl/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/nl/mailing-lists.adoc[] +include::../../../../shared/nl/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/nl/mailing-lists.adoc[] +include::../../../../shared/nl/urls.adoc[] +endif::[] [.abstract-title] Samenvatting From owner-dev-commits-doc-all@freebsd.org Wed Jun 2 17:00:00 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1AC19647260 for ; Wed, 2 Jun 2021 17:00:00 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FwFdC6dbGz3vZR; Wed, 2 Jun 2021 16:59:59 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id CB7DA1A98C; Wed, 2 Jun 2021 16:59:59 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 152Gxx5k080426; Wed, 2 Jun 2021 16:59:59 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 152Gxxci080425; Wed, 2 Jun 2021 16:59:59 GMT (envelope-from git) Date: Wed, 2 Jun 2021 16:59:59 GMT Message-Id: <202106021659.152Gxxci080425@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: e513af7ee1 - main - hu/articles: Fix include links for PDF. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: e513af7ee1f5d305c0a2293d0d7ff047a3eb685a Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2021 17:00:00 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=e513af7ee1f5d305c0a2293d0d7ff047a3eb685a commit e513af7ee1f5d305c0a2293d0d7ff047a3eb685a Author: Marc Fonvieille AuthorDate: 2021-06-02 16:57:08 +0000 Commit: Marc Fonvieille CommitDate: 2021-06-02 16:59:09 +0000 hu/articles: Fix include links for PDF. --- documentation/content/hu/articles/explaining-bsd/_index.adoc | 10 ++++++++++ .../content/hu/articles/gjournal-desktop/_index.adoc | 12 +++++++++--- documentation/content/hu/articles/linux-users/_index.adoc | 10 ++++++++++ 3 files changed, 29 insertions(+), 3 deletions(-) diff --git a/documentation/content/hu/articles/explaining-bsd/_index.adoc b/documentation/content/hu/articles/explaining-bsd/_index.adoc index f78b377133..b2cb04bc6e 100644 --- a/documentation/content/hu/articles/explaining-bsd/_index.adoc +++ b/documentation/content/hu/articles/explaining-bsd/_index.adoc @@ -21,7 +21,17 @@ trademarks: ["freebsd", "amd", "apple", "intel", "xfree86", "linux", "opengroup" :figure-caption: Ábra :example-caption: Példa +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +endif::[] [.abstract-title] Kivonat diff --git a/documentation/content/hu/articles/gjournal-desktop/_index.adoc b/documentation/content/hu/articles/gjournal-desktop/_index.adoc index 2f116389a0..aade9b35ca 100644 --- a/documentation/content/hu/articles/gjournal-desktop/_index.adoc +++ b/documentation/content/hu/articles/gjournal-desktop/_index.adoc @@ -23,20 +23,26 @@ trademarks: ["freebsd", "general"] :example-caption: Példa ifeval::["{backend}" == "html5"] +include::shared/authors.adoc[] +include::shared/hu/mailing-lists.adoc[] +include::shared/hu/urls.adoc[] :imagesdir: ../../../images/articles/gjournal-desktop/ endif::[] ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/hu/mailing-lists.adoc[] +include::../../../../shared/hu/urls.adoc[] :imagesdir: ../../../../static/images/articles/gjournal-desktop/ endif::[] ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/hu/mailing-lists.adoc[] +include::../../../../shared/hu/urls.adoc[] :imagesdir: ../../../../static/images/articles/gjournal-desktop/ endif::[] -include::shared/authors.adoc[] -include::shared/hu/mailing-lists.adoc[] -include::shared/hu/urls.adoc[] [.abstract-title] Kivonat diff --git a/documentation/content/hu/articles/linux-users/_index.adoc b/documentation/content/hu/articles/linux-users/_index.adoc index 6833f37223..12b023c7de 100644 --- a/documentation/content/hu/articles/linux-users/_index.adoc +++ b/documentation/content/hu/articles/linux-users/_index.adoc @@ -21,7 +21,17 @@ trademarks: ["freebsd", "intel", "redhat", "linux", "unix", "general"] :figure-caption: Ábra :example-caption: Példa +ifeval::["{backend}" == "html5"] include::shared/hu/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/hu/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/hu/urls.adoc[] +endif::[] [.abstract-title] Kivonat From owner-dev-commits-doc-all@freebsd.org Wed Jun 2 17:03:21 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 017F1647A00 for ; Wed, 2 Jun 2021 17:03:20 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FwFj46HSYz3vtM; Wed, 2 Jun 2021 17:03:20 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C07391A9B7; Wed, 2 Jun 2021 17:03:20 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 152H3KVO094520; Wed, 2 Jun 2021 17:03:20 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 152H3KDf094519; Wed, 2 Jun 2021 17:03:20 GMT (envelope-from git) Date: Wed, 2 Jun 2021 17:03:20 GMT Message-Id: <202106021703.152H3KDf094519@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: ea5b0f1a8b - main - hu/books/handbook: Fix a wrong image filename. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: ea5b0f1a8b4c0e9a008627af8df14baa0481b6a7 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jun 2021 17:03:21 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=ea5b0f1a8b4c0e9a008627af8df14baa0481b6a7 commit ea5b0f1a8b4c0e9a008627af8df14baa0481b6a7 Author: Marc Fonvieille AuthorDate: 2021-06-02 17:02:27 +0000 Commit: Marc Fonvieille CommitDate: 2021-06-02 17:02:27 +0000 hu/books/handbook: Fix a wrong image filename. --- documentation/content/hu/books/handbook/advanced-networking/_index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/content/hu/books/handbook/advanced-networking/_index.adoc b/documentation/content/hu/books/handbook/advanced-networking/_index.adoc index 139179a161..e25dc4d69e 100644 --- a/documentation/content/hu/books/handbook/advanced-networking/_index.adoc +++ b/documentation/content/hu/books/handbook/advanced-networking/_index.adoc @@ -2527,7 +2527,7 @@ Például, ha egy otthon vagy a vállalat egy fiókjánál levõ gépet akarjuk ==== A hálózat busz topológiájú és 10 Base 2 Ethernetet használ ("thinnet"). Ha szükséges, akkor az útválasztót egy AUI/10BT adó-vevõvel csatlakoztassuk a hálózati kábelre. -image::isdn-buse.png[10 Base 2 Ethernet] +image::isdn-bus.png[10 Base 2 Ethernet] Ha az otthoni vagy fiókbeli számítógép az egyedüli, akkor egy keresztkötésû sodrott érpár kábellel akár közvetlenül is csatlakozhatunk az útválasztóhoz. ==== From owner-dev-commits-doc-all@freebsd.org Thu Jun 3 12:55:05 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D5958639056 for ; Thu, 3 Jun 2021 12:55:05 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fwm895SqSz3Drs; Thu, 3 Jun 2021 12:55:05 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id A0FE021EE; Thu, 3 Jun 2021 12:55:05 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 153Ct5Ko076260; Thu, 3 Jun 2021 12:55:05 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 153Ct5qZ076259; Thu, 3 Jun 2021 12:55:05 GMT (envelope-from git) Date: Thu, 3 Jun 2021 12:55:05 GMT Message-Id: <202106031255.153Ct5qZ076259@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Warner Losh Subject: git: f98364e5cc - main - Remove stray } MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: imp X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: f98364e5cc1d18eda448df5daa3bb80dc05fd5ca Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2021 12:55:05 -0000 The branch main has been updated by imp: URL: https://cgit.FreeBSD.org/doc/commit/?id=f98364e5cc1d18eda448df5daa3bb80dc05fd5ca commit f98364e5cc1d18eda448df5daa3bb80dc05fd5ca Author: Warner Losh AuthorDate: 2021-06-03 12:53:48 +0000 Commit: Warner Losh CommitDate: 2021-06-03 12:55:03 +0000 Remove stray } Noticed by: ceri@ Sponsored by: Netflix --- documentation/content/en/books/arch-handbook/kobj/_index.adoc | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/documentation/content/en/books/arch-handbook/kobj/_index.adoc b/documentation/content/en/books/arch-handbook/kobj/_index.adoc index 0b81112792..77954ac18b 100644 --- a/documentation/content/en/books/arch-handbook/kobj/_index.adoc +++ b/documentation/content/en/books/arch-handbook/kobj/_index.adoc @@ -151,7 +151,7 @@ CODE { struct foo * foo_alloc_null(struct bar *) { return NULL; -} + } }; .... @@ -165,7 +165,6 @@ For example: HEADER { struct mumble; struct grumble; -} }; .... From owner-dev-commits-doc-all@freebsd.org Thu Jun 3 13:03:04 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id CFC5063906D for ; Thu, 3 Jun 2021 13:03:04 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FwmKN594jz3FbP; Thu, 3 Jun 2021 13:03:04 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 98A8F24BB; Thu, 3 Jun 2021 13:03:04 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 153D34Rx089989; Thu, 3 Jun 2021 13:03:04 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 153D34xb089988; Thu, 3 Jun 2021 13:03:04 GMT (envelope-from git) Date: Thu, 3 Jun 2021 13:03:04 GMT Message-Id: <202106031303.153D34xb089988@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Warner Losh Subject: git: cd2b40e5b8 - main - git: document how to merge a pull request from github. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: imp X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: cd2b40e5b8d5f4ca05ab1ce43a736d406f051119 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2021 13:03:04 -0000 The branch main has been updated by imp: URL: https://cgit.FreeBSD.org/doc/commit/?id=cd2b40e5b8d5f4ca05ab1ce43a736d406f051119 commit cd2b40e5b8d5f4ca05ab1ce43a736d406f051119 Author: Warner Losh AuthorDate: 2021-06-03 13:02:25 +0000 Commit: Warner Losh CommitDate: 2021-06-03 13:02:25 +0000 git: document how to merge a pull request from github. Reviewed by: ceri@, ygy@ Sponsored by: Netflix Differential Revision: https://reviews.freebsd.org/D30589 --- .../en/articles/committers-guide/_index.adoc | 54 ++++++++++++++++++++++ 1 file changed, 54 insertions(+) diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc index 82800ccfd7..f3c63a4943 100644 --- a/documentation/content/en/articles/committers-guide/_index.adoc +++ b/documentation/content/en/articles/committers-guide/_index.adoc @@ -2208,6 +2208,60 @@ To github.com:gvnn3/freebsd-src.git At this point your work is now in your branch on +GitHub+ and you can share the link with other collaborators. +=== Landing a github pull request +This section documents how to land a GitHub pull request that's submitted against the FreeBSD Git mirrors at GitHub. +While this is not an official way to submit patches at this time, sometimes good fixes come in this way and it is easiest just to bring them into a committer's tree and have them pushed into the FreeBSD's tree from there. +Similar steps can be used to pull branches from other repositories and land those. +When committing pull requests from others, one should take extra care to examine all the changes to ensure they are exactly as represented. + +Before beginning, make sure that the local Git repo is up to date and has the correct origins set <> +In addition, make sure to have the following origins: +[source,shell] +.... +% git remote -v +freebsd https://git.freebsd.org/src.git (fetch) +freebsd ssh://git@gitrepo.freebsd.org/src.git (push) +github https://github.com/freebsd/freebsd-src (fetch) +github https://github.com/freebsd/freebsd-src (fetch) +.... +Often pull requests are simple: requests that contain only a single commit. +In this case, a streamlined approach may be used, though the approach in the prior section will also work. +Here, a branch is created, the change is cherry picked, the commit message adjusted, and sanity-checked before being pushed. +The branch `staging` is used in this example but it can be any name. +This technique works for any number of commits in the pull request, especailly when the changes apply cleanly to the FreeBSD tree. +However, when there's multiple commits, especially when minor adjustments are needed, `git rebase -i` works better than `git cherry-pick`. +Briefly, these commands create a branch; cherry-picks the changes from the pull request; tests it; adjusts the commit messages; and fast forward merges it back to `main`. +The PR number is `$PR` below. +When adjusting the message, add `Pull Request: https://github.com/freebsd-src/pull/$PR`. +[source,shell] +.... +% git fetch github pull/$PR/head:staging +% git rebase -i main staging # to move the staging branch forward, adjust commit message here + +% git checkout main +% git pull --ff-only # to get the latest if time has passed +% git checkout main +% git merge --ff-only staging + +% git push freebsd +.... + +[.procedure] +==== +For complicated pull requests that have multiple commits with conflicts, follow the following outline. + +. checkout the pull request `git checkout github/pull/XXX` +. create a branch to rebase `git checkout -b staging` +. rebase the `staging` branch to the latest `main` with `git rebase -i main staging` +. resolve conflicts and do whatever testing is needed +. fast forward the `staging` branch into `main` as above +. final sanity check of changes to make sure all is well +. push to FreeBSD's Git repository. + +This will also work when bringing branches developed elsewhere into the local tree for committing. +==== +Once finished with the pull request, close it using GitHub's web interface. +If the changes are fetched with https, this last step is the only one requiring a GitHub account. [[vcs-history]] == Version Control History From owner-dev-commits-doc-all@freebsd.org Thu Jun 3 13:57:16 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 23A2D63A0DC for ; Thu, 3 Jun 2021 13:57:16 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FwnWw0Wvpz3LmW; Thu, 3 Jun 2021 13:57:16 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id EA3BD31CB; Thu, 3 Jun 2021 13:57:15 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 153DvFxR056831; Thu, 3 Jun 2021 13:57:15 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 153DvFO4056830; Thu, 3 Jun 2021 13:57:15 GMT (envelope-from git) Date: Thu, 3 Jun 2021 13:57:15 GMT Message-Id: <202106031357.153DvFO4056830@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Warner Losh Subject: git: e22642d10e - main - committers-guide: pull request landing tweaks. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: imp X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: e22642d10ef896da9a08ac07a264f290b28b934c Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2021 13:57:16 -0000 The branch main has been updated by imp: URL: https://cgit.FreeBSD.org/doc/commit/?id=e22642d10ef896da9a08ac07a264f290b28b934c commit e22642d10ef896da9a08ac07a264f290b28b934c Author: Warner Losh AuthorDate: 2021-06-03 13:55:34 +0000 Commit: Warner Losh CommitDate: 2021-06-03 13:55:34 +0000 committers-guide: pull request landing tweaks. Clarify that only closing the pull request resuires a GitHub account. All the other steps can proceed without one. Also, include --push-option=confirm-author in the push because pull requests will have a different author than the committer and this instructs the src pre-commit hooks to allow the commit through. Sponsored by: Netflix --- documentation/content/en/articles/committers-guide/_index.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc index f3c63a4943..1767095908 100644 --- a/documentation/content/en/articles/committers-guide/_index.adoc +++ b/documentation/content/en/articles/committers-guide/_index.adoc @@ -2243,7 +2243,7 @@ When adjusting the message, add `Pull Request: https://github.com/freebsd-src/pu % git checkout main % git merge --ff-only staging -% git push freebsd +% git push freebsd --push-option=confirm-author .... [.procedure] @@ -2261,7 +2261,7 @@ For complicated pull requests that have multiple commits with conflicts, follow This will also work when bringing branches developed elsewhere into the local tree for committing. ==== Once finished with the pull request, close it using GitHub's web interface. -If the changes are fetched with https, this last step is the only one requiring a GitHub account. +It is worth noting that if your `github` origin uses `https://`, the only step you'll need a GitHub account for is closing the pull request. [[vcs-history]] == Version Control History From owner-dev-commits-doc-all@freebsd.org Thu Jun 3 19:44:36 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 1479B63FCCD for ; Thu, 3 Jun 2021 19:44:36 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FwxDg75Vpz4jNT; Thu, 3 Jun 2021 19:44:35 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id DA8547CB7; Thu, 3 Jun 2021 19:44:35 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 153JiZpE021212; Thu, 3 Jun 2021 19:44:35 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 153JiZr5021211; Thu, 3 Jun 2021 19:44:35 GMT (envelope-from git) Date: Thu, 3 Jun 2021 19:44:35 GMT Message-Id: <202106031944.153JiZr5021211@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: "Danilo G. Baio" Subject: git: cf0f8d609a - main - articles/pgpkeys: Move eduardo's key to Developers section MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: dbaio X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: cf0f8d609ab7bd3bd2cf42c7012c77a732b69c20 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2021 19:44:36 -0000 The branch main has been updated by dbaio: URL: https://cgit.FreeBSD.org/doc/commit/?id=cf0f8d609ab7bd3bd2cf42c7012c77a732b69c20 commit cf0f8d609ab7bd3bd2cf42c7012c77a732b69c20 Author: Danilo G. Baio AuthorDate: 2021-06-03 19:04:19 +0000 Commit: Danilo G. Baio CommitDate: 2021-06-03 19:04:50 +0000 articles/pgpkeys: Move eduardo's key to Developers section --- documentation/content/en/articles/pgpkeys/_index.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/content/en/articles/pgpkeys/_index.adoc b/documentation/content/en/articles/pgpkeys/_index.adoc index 2950eda071..e46baa2962 100644 --- a/documentation/content/en/articles/pgpkeys/_index.adoc +++ b/documentation/content/en/articles/pgpkeys/_index.adoc @@ -1572,6 +1572,9 @@ include::{include-path}tota.key[] === `{romain}` include::{include-path}romain.key[] +=== `{eduardo}` +include::{include-path}eduardo.key[] + === `{sylvio}` include::{include-path}sylvio.key[] @@ -1808,6 +1811,3 @@ include::{include-path}mwlucas.key[] === `{dhw}` include::{include-path}dhw.key[] - -=== `{eduardo}` -include::{include-path}eduardo.key[] From owner-dev-commits-doc-all@freebsd.org Thu Jun 3 19:44:37 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5BB2963FAD5 for ; Thu, 3 Jun 2021 19:44:37 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FwxDj1Sb8z4jHm; Thu, 3 Jun 2021 19:44:37 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 0CF817866; Thu, 3 Jun 2021 19:44:37 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 153Jiaxm021233; Thu, 3 Jun 2021 19:44:36 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 153Jian8021232; Thu, 3 Jun 2021 19:44:36 GMT (envelope-from git) Date: Thu, 3 Jun 2021 19:44:36 GMT Message-Id: <202106031944.153Jian8021232@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: "Danilo G. Baio" Subject: git: f2d5f930d8 - main - tools/*translate.sh: Add description field on the YAML Front Matter parser MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: dbaio X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: f2d5f930d82a9f0ccb290dd020173302eceeea02 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2021 19:44:37 -0000 The branch main has been updated by dbaio: URL: https://cgit.FreeBSD.org/doc/commit/?id=f2d5f930d82a9f0ccb290dd020173302eceeea02 commit f2d5f930d82a9f0ccb290dd020173302eceeea02 Author: Danilo G. Baio AuthorDate: 2021-06-03 19:30:31 +0000 Commit: Danilo G. Baio CommitDate: 2021-06-03 19:30:31 +0000 tools/*translate.sh: Add description field on the YAML Front Matter parser This field was introduced on 0d9894b11e0e94cde952b0112782e68e27c893da to improve SEO. --- tools/translate.sh | 2 +- tools/update_translate_template.sh | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/tools/translate.sh b/tools/translate.sh index cb4005611d..af3335ec91 100755 --- a/tools/translate.sh +++ b/tools/translate.sh @@ -66,7 +66,7 @@ for pofile in $(find "$COMPONENT/content/$LANGUAGE/" -name "*.po" ); do po4a-translate \ --format asciidoc \ --option compat=asciidoctor \ - --option yfm_keys=title,part \ + --option yfm_keys=title,part,description \ --master "$adoc_orig" \ --master-charset "UTF-8" \ --po "$pofile" \ diff --git a/tools/update_translate_template.sh b/tools/update_translate_template.sh index 4bb5699d2e..5e577b7f71 100755 --- a/tools/update_translate_template.sh +++ b/tools/update_translate_template.sh @@ -69,7 +69,7 @@ for component in $COMPONENTS; do po4a-updatepo \ --format asciidoc \ --option compat=asciidoctor \ - --option yfm_keys=title,part \ + --option yfm_keys=title,part,description \ --master "$document" \ --master-charset "UTF-8" \ --copyright-holder "The FreeBSD Project" \ @@ -82,7 +82,7 @@ for component in $COMPONENTS; do po4a-gettextize \ --format asciidoc \ --option compat=asciidoctor \ - --option yfm_keys=title,part \ + --option yfm_keys=title,part,description \ --master "$document" \ --master-charset "UTF-8" \ --copyright-holder "The FreeBSD Project" \ From owner-dev-commits-doc-all@freebsd.org Thu Jun 3 19:44:38 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 56A5063F8FB for ; Thu, 3 Jun 2021 19:44:38 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FwxDk1vTwz4jHs; Thu, 3 Jun 2021 19:44:38 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 232767BF6; Thu, 3 Jun 2021 19:44:38 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 153Jic5j021261; Thu, 3 Jun 2021 19:44:38 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 153Jicaw021260; Thu, 3 Jun 2021 19:44:38 GMT (envelope-from git) Date: Thu, 3 Jun 2021 19:44:38 GMT Message-Id: <202106031944.153Jicaw021260@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: "Danilo G. Baio" Subject: git: 06ca1e8842 - main - books/fdp-primer/po-translations: Update po4a commands MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: dbaio X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 06ca1e884279e9f7440ed18078625ddb01893b1b Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 03 Jun 2021 19:44:38 -0000 The branch main has been updated by dbaio: URL: https://cgit.FreeBSD.org/doc/commit/?id=06ca1e884279e9f7440ed18078625ddb01893b1b commit 06ca1e884279e9f7440ed18078625ddb01893b1b Author: Danilo G. Baio AuthorDate: 2021-06-03 19:38:46 +0000 Commit: Danilo G. Baio CommitDate: 2021-06-03 19:38:46 +0000 books/fdp-primer/po-translations: Update po4a commands This adds description field on the YAML Front Matter parser following f2d5f930d82a9f0ccb290dd020173302eceeea02 update. --- .../content/en/books/fdp-primer/po-translations/_index.adoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/content/en/books/fdp-primer/po-translations/_index.adoc b/documentation/content/en/books/fdp-primer/po-translations/_index.adoc index 7b07f0bc89..8dc6a58602 100644 --- a/documentation/content/en/books/fdp-primer/po-translations/_index.adoc +++ b/documentation/content/en/books/fdp-primer/po-translations/_index.adoc @@ -97,7 +97,7 @@ These steps are repeated until the translator feels that enough of the document % po4a-gettextize \ --format asciidoc \ --option compat=asciidoctor \ - --option yfm_keys=title,part \ + --option yfm_keys=title,part,description \ --master "documentation/content/en/articles/leap-seconds/_index.adoc" \ --master-charset "UTF-8" \ --copyright-holder "The FreeBSD Project" \ @@ -125,7 +125,7 @@ These steps are repeated until the translator feels that enough of the document % po4a-translate \ --format asciidoc \ --option compat=asciidoctor \ - --option yfm_keys=title,part \ + --option yfm_keys=title,part,description \ --master "documentation/content/en/articles/leap-seconds/_index.adoc" \ --master-charset "UTF-8" \ --po "documentation/content/es/articles/leap-seconds/_index.po" \ @@ -313,7 +313,7 @@ It contains all of the work that translators have done. % po4a-gettextize \ --format asciidoc \ --option compat=asciidoctor \ - --option yfm_keys=title,part \ + --option yfm_keys=title,part,description \ --master "documentation/content/en/books/porters-handbook/_index.adoc" \ --master-charset "UTF-8" \ --copyright-holder "The FreeBSD Project" \ From owner-dev-commits-doc-all@freebsd.org Fri Jun 4 07:55:36 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id BD57B649C3B for ; Fri, 4 Jun 2021 07:55:36 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FxFS84jycz4X7C; Fri, 4 Jun 2021 07:55:36 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 74A5B19376; Fri, 4 Jun 2021 07:55:36 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 1547taoD093379; Fri, 4 Jun 2021 07:55:36 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 1547tahC093378; Fri, 4 Jun 2021 07:55:36 GMT (envelope-from git) Date: Fri, 4 Jun 2021 07:55:36 GMT Message-Id: <202106040755.1547tahC093378@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: 5891781195 - internal/admin - Release Ceri Davies (ceri) from mentorship. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/internal/admin X-Git-Reftype: branch X-Git-Commit: 5891781195be2494e6d726d0c9316e3e31ecd54b Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2021 07:55:36 -0000 The branch internal/admin has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=5891781195be2494e6d726d0c9316e3e31ecd54b commit 5891781195be2494e6d726d0c9316e3e31ecd54b Author: Marc Fonvieille AuthorDate: 2021-06-04 07:51:23 +0000 Commit: Marc Fonvieille CommitDate: 2021-06-04 07:51:23 +0000 Release Ceri Davies (ceri) from mentorship. Ceri is, now, more than ready to fly on his own! Approved by: doceng (implicit) --- mentors | 1 - 1 file changed, 1 deletion(-) diff --git a/mentors b/mentors index a17302730c..ccaa57643f 100644 --- a/mentors +++ b/mentors @@ -10,6 +10,5 @@ # Sort by mentee login name. # Mentee Mentor Optional comment -ceri blackend fernape 0mp co-mentors: gbe murray bcr From owner-dev-commits-doc-all@freebsd.org Fri Jun 4 14:14:29 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 2B9C864F60E for ; Fri, 4 Jun 2021 14:14:29 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FxPsK0XVrz3k4f; Fri, 4 Jun 2021 14:14:29 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id EEB1D1E4D2; Fri, 4 Jun 2021 14:14:28 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 154EES3D099732; Fri, 4 Jun 2021 14:14:28 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 154EESkY099731; Fri, 4 Jun 2021 14:14:28 GMT (envelope-from git) Date: Fri, 4 Jun 2021 14:14:28 GMT Message-Id: <202106041414.154EESkY099731@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Ceri Davies Subject: git: 46e26eda73 - main - */README: update links to the FDP. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: ceri X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 46e26eda73f07ec445d01ff739749725ea1dd790 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2021 14:14:29 -0000 The branch main has been updated by ceri: URL: https://cgit.FreeBSD.org/doc/commit/?id=46e26eda73f07ec445d01ff739749725ea1dd790 commit 46e26eda73f07ec445d01ff739749725ea1dd790 Author: Ceri Davies AuthorDate: 2021-06-04 14:13:14 +0000 Commit: Ceri Davies CommitDate: 2021-06-04 14:14:10 +0000 */README: update links to the FDP. --- documentation/README | 2 +- website/README | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/README b/documentation/README index c8e1f8f4ba..2d0898c04b 100644 --- a/documentation/README +++ b/documentation/README @@ -3,7 +3,7 @@ $FreeBSD$ If you plan on building a local copy of the FreeBSD documentation, or using our toolchain in your own projects, please read the Documentation Primer at: - https://www.FreeBSD.org/doc/en/books/fdp-primer/ + https://docs.FreeBSD.org/en/books/fdp-primer/ for information about the tools and formatting languages we use. Chapter 1 has a Quick Start section, and Chapter 2 covers the software diff --git a/website/README b/website/README index c8e1f8f4ba..2d0898c04b 100644 --- a/website/README +++ b/website/README @@ -3,7 +3,7 @@ $FreeBSD$ If you plan on building a local copy of the FreeBSD documentation, or using our toolchain in your own projects, please read the Documentation Primer at: - https://www.FreeBSD.org/doc/en/books/fdp-primer/ + https://docs.FreeBSD.org/en/books/fdp-primer/ for information about the tools and formatting languages we use. Chapter 1 has a Quick Start section, and Chapter 2 covers the software From owner-dev-commits-doc-all@freebsd.org Fri Jun 4 16:34:18 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D7EF16512C8 for ; Fri, 4 Jun 2021 16:34:18 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FxSyf5pjFz3tpS; Fri, 4 Jun 2021 16:34:18 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B0F0820A81; Fri, 4 Jun 2021 16:34:18 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 154GYI9F085594; Fri, 4 Jun 2021 16:34:18 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 154GYI8j085593; Fri, 4 Jun 2021 16:34:18 GMT (envelope-from git) Date: Fri, 4 Jun 2021 16:34:18 GMT Message-Id: <202106041634.154GYI8j085593@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: 4e035380d4 - main - el/articles: Fix include links for PDF. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 4e035380d4f9967c59ae0f959308320ecff7b0e6 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2021 16:34:18 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=4e035380d4f9967c59ae0f959308320ecff7b0e6 commit 4e035380d4f9967c59ae0f959308320ecff7b0e6 Author: Marc Fonvieille AuthorDate: 2021-06-04 16:33:17 +0000 Commit: Marc Fonvieille CommitDate: 2021-06-04 16:33:17 +0000 el/articles: Fix include links for PDF. --- .../content/el/articles/contributing/_index.adoc | 12 ++++++++++++ .../el/articles/freebsd-questions/_index.adoc | 12 ++++++++++++ .../content/el/articles/gjournal-desktop/_index.adoc | 12 +++++++++--- .../el/articles/greek-language-support/_index.adoc | 12 ++++++++++++ .../content/el/articles/linux-users/_index.adoc | 10 ++++++++++ .../content/el/articles/mailing-list-faq/_index.adoc | 14 ++++++++++++++ .../content/el/articles/nanobsd/_index.adoc | 10 ++++++++++ .../content/el/articles/new-users/_index.adoc | 10 ++++++++++ .../content/el/articles/problem-reports/_index.adoc | 12 ++++++++++++ documentation/content/el/articles/releng/_index.adoc | 20 +++++++++++++++++++- 10 files changed, 120 insertions(+), 4 deletions(-) diff --git a/documentation/content/el/articles/contributing/_index.adoc b/documentation/content/el/articles/contributing/_index.adoc index ddab398441..38be4554dd 100644 --- a/documentation/content/el/articles/contributing/_index.adoc +++ b/documentation/content/el/articles/contributing/_index.adoc @@ -21,8 +21,20 @@ trademarks: ["freebsd", "ieee", "general"] :figure-caption: Σχήμα :example-caption: Παράδειγμα +ifeval::["{backend}" == "html5"] include::shared/el/urls.adoc[] include::shared/el/mailing-lists.adoc[lines=10..-1] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/el/urls.adoc[] +include::../../../../shared/el/mailing-lists.adoc[lines=10..-1] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/el/urls.adoc[] +include::../../../../shared/el/mailing-lists.adoc[lines=10..-1] +endif::[] [.abstract-title] Περίληψη diff --git a/documentation/content/el/articles/freebsd-questions/_index.adoc b/documentation/content/el/articles/freebsd-questions/_index.adoc index bd722f9e8c..c11b9f1860 100644 --- a/documentation/content/el/articles/freebsd-questions/_index.adoc +++ b/documentation/content/el/articles/freebsd-questions/_index.adoc @@ -21,8 +21,20 @@ trademarks: ["freebsd", "microsoft", "opengroup", "qualcomm", "general"] :figure-caption: Σχήμα :example-caption: Παράδειγμα +ifeval::["{backend}" == "html5"] include::shared/el/urls.adoc[] include::shared/el/mailing-lists.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/el/urls.adoc[] +include::../../../../shared/el/mailing-lists.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/el/urls.adoc[] +include::../../../../shared/el/mailing-lists.adoc[] +endif::[] [.abstract-title] Περίληψη diff --git a/documentation/content/el/articles/gjournal-desktop/_index.adoc b/documentation/content/el/articles/gjournal-desktop/_index.adoc index d88c314d64..1a997e4ce7 100644 --- a/documentation/content/el/articles/gjournal-desktop/_index.adoc +++ b/documentation/content/el/articles/gjournal-desktop/_index.adoc @@ -22,20 +22,26 @@ trademarks: ["freebsd", "general"] :example-caption: Παράδειγμα ifeval::["{backend}" == "html5"] +include::shared/authors.adoc[] +include::shared/el/mailing-lists.adoc[lines=10..-1] +include::shared/el/urls.adoc[] :imagesdir: ../../../images/articles/gjournal-desktop/ endif::[] ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/el/urls.adoc[] +include::../../../../shared/el/mailing-lists.adoc[lines=10..-1] :imagesdir: ../../../../static/images/articles/gjournal-desktop/ endif::[] ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/el/urls.adoc[] +include::../../../../shared/el/mailing-lists.adoc[lines=10..-1] :imagesdir: ../../../../static/images/articles/gjournal-desktop/ endif::[] -include::shared/authors.adoc[] -include::shared/el/mailing-lists.adoc[lines=10..-1] -include::shared/el/urls.adoc[] [.abstract-title] Περίληψη diff --git a/documentation/content/el/articles/greek-language-support/_index.adoc b/documentation/content/el/articles/greek-language-support/_index.adoc index cb0b7ddbfb..dc861f81a7 100644 --- a/documentation/content/el/articles/greek-language-support/_index.adoc +++ b/documentation/content/el/articles/greek-language-support/_index.adoc @@ -21,8 +21,20 @@ trademarks: ["freebsd", "general"] :figure-caption: Σχήμα :example-caption: Παράδειγμα +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] include::shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/el/urls.adoc[] +endif::[] [.abstract-title] Περίληψη diff --git a/documentation/content/el/articles/linux-users/_index.adoc b/documentation/content/el/articles/linux-users/_index.adoc index 05e618adb8..506102e033 100644 --- a/documentation/content/el/articles/linux-users/_index.adoc +++ b/documentation/content/el/articles/linux-users/_index.adoc @@ -21,7 +21,17 @@ trademarks: ["freebsd", "intel", "redhat", "linux", "unix", "general"] :figure-caption: Σχήμα :example-caption: Παράδειγμα +ifeval::["{backend}" == "html5"] include::shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/el/urls.adoc[] +endif::[] [.abstract-title] Περίληψη diff --git a/documentation/content/el/articles/mailing-list-faq/_index.adoc b/documentation/content/el/articles/mailing-list-faq/_index.adoc index bc79bbabdb..c111e6c474 100644 --- a/documentation/content/el/articles/mailing-list-faq/_index.adoc +++ b/documentation/content/el/articles/mailing-list-faq/_index.adoc @@ -19,9 +19,23 @@ releaseinfo: "$FreeBSD$" :figure-caption: Σχήμα :example-caption: Παράδειγμα +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] include::shared/el/mailing-lists.adoc[lines=10..-1] include::shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/el/mailing-lists.adoc[lines=10..-1] +include::../../../../shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/el/mailing-lists.adoc[lines=10..-1] +include::../../../../shared/el/urls.adoc[] +endif::[] [.abstract-title] Περίληψη diff --git a/documentation/content/el/articles/nanobsd/_index.adoc b/documentation/content/el/articles/nanobsd/_index.adoc index 5f43be2b7b..9a9ce0a9c5 100644 --- a/documentation/content/el/articles/nanobsd/_index.adoc +++ b/documentation/content/el/articles/nanobsd/_index.adoc @@ -22,7 +22,17 @@ trademarks: ["freebsd", "general"] :figure-caption: Σχήμα :example-caption: Παράδειγμα +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +endif::[] [.abstract-title] Περίληψη diff --git a/documentation/content/el/articles/new-users/_index.adoc b/documentation/content/el/articles/new-users/_index.adoc index fb2b243d37..049ea57bf2 100644 --- a/documentation/content/el/articles/new-users/_index.adoc +++ b/documentation/content/el/articles/new-users/_index.adoc @@ -21,7 +21,17 @@ trademarks: ["freebsd", "ibm", "microsoft", "opengroup", "general"] :figure-caption: Σχήμα :example-caption: Παράδειγμα +ifeval::["{backend}" == "html5"] include::shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/el/urls.adoc[] +endif::[] [.abstract-title] Περίληψη diff --git a/documentation/content/el/articles/problem-reports/_index.adoc b/documentation/content/el/articles/problem-reports/_index.adoc index c20cd2fbeb..81f8b6e62a 100644 --- a/documentation/content/el/articles/problem-reports/_index.adoc +++ b/documentation/content/el/articles/problem-reports/_index.adoc @@ -20,8 +20,20 @@ trademarks: ["freebsd", "cvsup", "ibm", "intel", "sparc", "sun", "general"] :figure-caption: Σχήμα :example-caption: Παράδειγμα +ifeval::["{backend}" == "html5"] include::shared/el/mailing-lists.adoc[lines=10..-1] include::shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/el/mailing-lists.adoc[lines=10..-1] +include::../../../../shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/el/mailing-lists.adoc[lines=10..-1] +include::../../../../shared/el/urls.adoc[] +endif::[] [.abstract-title] Περίληψη diff --git a/documentation/content/el/articles/releng/_index.adoc b/documentation/content/el/articles/releng/_index.adoc index 4264c954f1..75b2330cb9 100644 --- a/documentation/content/el/articles/releng/_index.adoc +++ b/documentation/content/el/articles/releng/_index.adoc @@ -23,11 +23,29 @@ trademarks: ["freebsd", "intel", "general"] :figure-caption: Σχήμα :example-caption: Παράδειγμα +ifeval::["{backend}" == "html5"] include::shared/authors.adoc[] include::shared/releases.adoc[] -include::shared/el/teams.adoc[lines=21..-1] include::shared/el/mailing-lists.adoc[lines=10..-1] +include::shared/el/teams.adoc[lines=21..-1] include::shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/releases.adoc[] +include::../../../../shared/el/mailing-lists.adoc[lines=10..-1] +include::../../../../shared/el/teams.adoc[lines=21..-1] +include::../../../../shared/el/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/authors.adoc[] +include::../../../../shared/releases.adoc[] +include::../../../../shared/el/mailing-lists.adoc[lines=10..-1] +include::../../../../shared/el/teams.adoc[lines=21..-1] +include::../../../../shared/el/urls.adoc[] +endif::[] [.abstract-title] Περίληψη From owner-dev-commits-doc-all@freebsd.org Fri Jun 4 23:35:34 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id E5CF76571E6 for ; Fri, 4 Jun 2021 23:35:34 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FxfJk57Nrz3Hry; Fri, 4 Jun 2021 23:35:34 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 93C2E26399; Fri, 4 Jun 2021 23:35:34 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 154NZYvO058697; Fri, 4 Jun 2021 23:35:34 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 154NZYNK058696; Fri, 4 Jun 2021 23:35:34 GMT (envelope-from git) Date: Fri, 4 Jun 2021 23:35:34 GMT Message-Id: <202106042335.154NZYNK058696@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: "Danilo G. Baio" Subject: git: 7af42a7fa7 - main - pt-br/articles/bsdl-gpl: Sync with en 5b0bf6b3 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: dbaio X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 7af42a7fa72af29b99c91335dc11213c711b1ba8 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2021 23:35:35 -0000 The branch main has been updated by dbaio: URL: https://cgit.FreeBSD.org/doc/commit/?id=7af42a7fa72af29b99c91335dc11213c711b1ba8 commit 7af42a7fa72af29b99c91335dc11213c711b1ba8 Author: Danilo G. Baio AuthorDate: 2021-06-04 23:31:05 +0000 Commit: Danilo G. Baio CommitDate: 2021-06-04 23:31:05 +0000 pt-br/articles/bsdl-gpl: Sync with en 5b0bf6b3 Obtained from: https://translate-dev.freebsd.org --- .../content/pt-br/articles/bsdl-gpl/_index.adoc | 41 +- .../content/pt-br/articles/bsdl-gpl/_index.po | 1149 ++++++++++++++++++++ 2 files changed, 1164 insertions(+), 26 deletions(-) diff --git a/documentation/content/pt-br/articles/bsdl-gpl/_index.adoc b/documentation/content/pt-br/articles/bsdl-gpl/_index.adoc index f4c13e2812..cbc736feaa 100644 --- a/documentation/content/pt-br/articles/bsdl-gpl/_index.adoc +++ b/documentation/content/pt-br/articles/bsdl-gpl/_index.adoc @@ -1,10 +1,12 @@ --- -title: Por que você deve usar uma licença de estilo BSD em seu Projeto Open Source authors: - - author: Bruce Montague + - + author: 'Bruce Montague' email: brucem@alumni.cse.ucsc.edu -releaseinfo: "$FreeBSD$" -trademarks: ["freebsd", "intel", "general"] +description: 'Por que você deve usar uma licença de estilo BSD em seu Projeto Open Source' +tags: '["bsdl", "gpl", "FreeBSD License"]' +title: 'Por que você deve usar uma licença de estilo BSD em seu Projeto Open Source' +trademarks: '["freebsd", "intel", "general"]' --- = Por que você deve usar uma licença de estilo BSD em seu Projeto Open Source @@ -16,13 +18,6 @@ trademarks: ["freebsd", "intel", "general"] :sectnumlevels: 6 :source-highlighter: rouge :experimental: -:toc-title: Índice -:part-signifier: Parte -:chapter-signifier: Capítulo -:appendix-caption: Apêndice -:table-caption: Tabela -:figure-caption: Figura -:example-caption: Exemplo ''' @@ -77,7 +72,7 @@ Richard Stallman, o desenvolvedor do Emacs, era membro da equipe do MIT quando s A GPL foi projetada para ser o oposto da licença proprietária padrão. Para este fim, quaisquer modificações que eram feitas a um programa GPL tinham que ser devolvidas à comunidade GPL (exigindo que o código fonte do programa fosse disponibilizado para o usuário) e que qualquer programa que utilizar ou linkar com código GPL, teria que estar sob a GPL. A GPL pretendia impedir que o software se tornasse proprietário. Como o último parágrafo da GPL afirma: -"This General Public License does not permit incorporating your program into proprietary programs."[1] +"This General Public License does not permit incorporating your program into proprietary programs."<> A http://www.opensource.org/licenses/gpl-license.php[GPL] é uma licença complexa, então aqui estão algumas regras básicas ao usar a GPL: @@ -113,9 +108,9 @@ Uma licença BSD concede a uma pequena empresa o equivalente a um software-in-es Nenhuma licença pode garantir disponibilidade futura do software. Embora um detentor de direitos autorais possa tradicionalmente mudar os termos de um direito autoral a qualquer momento, a presunção na comunidade BSD é de que tal tentativa simplesmente faz com que o código fonte seja derivado (fork). -A GPL proíbe explicitamente a revogação da licença. Ocorreu no entanto, que uma empresa (Mattel) comprou um copyright GPL (cphack), e revogou todo o direito autoral, foi a tribunal e conseguiu prevalecer [2]. Ou seja, eles revogaram legalmente toda a distribuição e todos os trabalhos derivados com base nos direitos autorais. Se isso pode acontecer com uma distribuição maior e mais dispersa, fica uma questão em aberto; Há também alguma confusão sobre se o software estava realmente sob a GPL. +A GPL proíbe explicitamente a revogação da licença. Ocorreu no entanto, que uma empresa (Mattel) comprou um copyright GPL (cphack), e revogou todo o direito autoral, foi a tribunal e conseguiu prevalecer <>. Ou seja, eles revogaram legalmente toda a distribuição e todos os trabalhos derivados com base nos direitos autorais. Se isso pode acontecer com uma distribuição maior e mais dispersa, fica uma questão em aberto; Há também alguma confusão sobre se o software estava realmente sob a GPL. -Em outro exemplo, a Red Hat comprou a Cygnus, uma empresa de engenharia que havia assumido o desenvolvimento das ferramentas de compilação da FSF. A Cygnus foi capaz de fazer isso porque eles desenvolveram um modelo de negócios no qual eles vendiam suporte para o software GNU. Isso permitiu que eles empregassem cerca de 50 engenheiros e os orientassem na direção dos programas, contribuindo com a preponderância de modificações. Como afirma Donald Rosenberg, "projetos usando licenças como a GPL ... vivem sob constante ameaça de que alguém assuma o projeto produzindo uma versão melhor do código e fazendo isso mais rápido que os proprietários originais". [3] +Em outro exemplo, a Red Hat comprou a Cygnus, uma empresa de engenharia que havia assumido o desenvolvimento das ferramentas de compilação da FSF. A Cygnus foi capaz de fazer isso porque eles desenvolveram um modelo de negócios no qual eles vendiam suporte para o software GNU. Isso permitiu que eles empregassem cerca de 50 engenheiros e os orientassem na direção dos programas, contribuindo com a preponderância de modificações. Como afirma Donald Rosenberg, "projetos usando licenças como a GPL ... vivem sob constante ameaça de que alguém assuma o projeto produzindo uma versão melhor do código e fazendo isso mais rápido que os proprietários originais". <> [[gpl-advantages]] == Vantagens e Desvantagens da GPL @@ -175,21 +170,15 @@ Em contraste com a GPL, que é projetada para impedir a comercialização propri Além disso, como a licença BSD não vem com a complexidade legal das licenças GPL ou LGPL, ela permite que desenvolvedores e empresas gastem seu tempo criando e promovendo um bom código, em vez de se preocupar se esse código viola algum licenciamento. [[addenda]] +[bibliography] == Referências Bibliográficas -[.programlisting] -.... +* [[[one,1]]] http://www.gnu.org/licenses/gpl.html -[1] http://www.gnu.org/licenses/gpl.html +* [[[two,2]]] http://archives.cnn.com/2000/TECH/computing/03/28/cyberpatrol.mirrors/ -[2] http://archives.cnn.com/2000/TECH/computing/03/28/cyberpatrol.mirrors/ +* [[[three,3]]] Open Source: the Unauthorized White Papers, Donald K. Rosenberg, IDG Books, 2000. Quotes are from page 114, "Effects of the GNU GPL". -[3] Open Source: the Unauthorized White Papers, Donald K. Rosenberg, IDG Books, - 2000. Quotes are from page 114, ``Effects of the GNU GPL''. +* [[[four,4]]] In the "What License to Use?" section of http://www.oreilly.com/catalog/opensources/book/brian.html -[4] In the "What License to Use?" section of - http://www.oreilly.com/catalog/opensources/book/brian.html - -This whitepaper is a condensation of an original work available at -http://alumni.cse.ucsc.edu/~brucem/open_source_license.htm -.... +This whitepaper is a condensation of an original work available at http://alumni.cse.ucsc.edu/~brucem/open_source_license.htm diff --git a/documentation/content/pt-br/articles/bsdl-gpl/_index.po b/documentation/content/pt-br/articles/bsdl-gpl/_index.po new file mode 100644 index 0000000000..2ab551d19c --- /dev/null +++ b/documentation/content/pt-br/articles/bsdl-gpl/_index.po @@ -0,0 +1,1149 @@ +# SOME DESCRIPTIVE TITLE +# Copyright (C) YEAR The FreeBSD Project +# This file is distributed under the same license as the FreeBSD Documentation package. +# Danilo G. Baio , 2021. +msgid "" +msgstr "" +"Project-Id-Version: FreeBSD Documentation VERSION\n" +"POT-Creation-Date: 2021-03-20 17:26-0300\n" +"PO-Revision-Date: 2021-05-30 20:51+0000\n" +"Last-Translator: Danilo G. Baio \n" +"Language-Team: Portuguese (Brazil) \n" +"Language: pt_BR\n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"Plural-Forms: nplurals=2; plural=n > 1;\n" +"X-Generator: Weblate 4.6.2\n" + +#. type: Title = +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:1 +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:10 +#, no-wrap +msgid "Why you should use a BSD style license for your Open Source Project" +msgstr "Por que você deve usar uma licença de estilo BSD em seu Projeto Open Source" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:21 +msgid "'''" +msgstr "'''" + +#. type: Title == +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:25 +#, no-wrap +msgid "Introduction" +msgstr "Introdução" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:30 +msgid "" +"This document makes a case for using a BSD style license for software and " +"data; specifically it recommends using a BSD style license in place of the " +"GPL. It can also be read as a BSD versus GPL Open Source License " +"introduction and summary." +msgstr "" +"Este documento apresenta argumentos para a utilização de uma licença de " +"estilo BSD para software e dados; especificamente recomenda utilizar uma " +"licença de estilo BSD no lugar de uma GPL. Também pode ser lido como uma " +"introdução e resumo das licenças de Projeto Open Source, BSD versus GPL." + +#. type: Title == +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:32 +#, no-wrap +msgid "Very Brief Open Source History" +msgstr "Uma Breve História do Open Source" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:38 +msgid "" +"Long before the term \"Open Source\" was used, software was developed by " +"loose associations of programmers and freely exchanged. Starting in the " +"early 1950's, organizations such as http://www.share.org[SHARE] and http://" +"www.decus.org[DECUS] developed much of the software that computer hardware " +"companies bundled with their hardware offerings. At that time computer " +"companies were in the hardware business; anything that reduced software cost " +"and made more programs available made the hardware companies more " +"competitive." +msgstr "" +"Muito antes do termo \"Open Source\" ser utilizado, o software era " +"desenvolvido por associações livres de programadores e os softwares eram " +"livremente trocados ou negociados. A partir do início dos anos 50, " +"organizações como a http://www.share.org[SHARE] e a http://www.decus." +"org[DECUS] desenvolviam grande parte do software que as empresas de hardware " +"empacotavam em suas ofertas. Naquela época, as empresas de computadores " +"estavam no negócio de hardware; qualquer coisa que reduzisse o custo do " +"software e disponibilizasse mais programas tornava as empresas de hardware " +"mais competitivas." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:45 +msgid "" +"This model changed in the 1960's. In 1965 ADR developed the first licensed " +"software product independent of a hardware company. ADR was competing " +"against a free IBM package originally developed by IBM customers. ADR " +"patented their software in 1968. To stop sharing of their program, they " +"provided it under an equipment lease in which payment was spread over the " +"lifetime of the product. ADR thus retained ownership and could control " +"resale and reuse." +msgstr "" +"Este modelo mudou nos anos 60. Em 1965, a ADR desenvolveu o primeiro produto " +"de software licenciado e independente de uma empresa de hardware. A ADR " +"estava competindo contra um pacote gratuito da IBM que foi originalmente " +"desenvolvido por seus próprios clientes. A ADR patenteou seu software em " +"1968. Para interromper o compartilhamento de seu programa, eles forneceram " +"seu software sob leasing de equipamento, na qual o pagamento foi distribuído " +"durante a vida útil do produto. A ADR reteve a propriedade e pôde controlar " +"a revenda e a reutilização." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:48 +msgid "" +"In 1969 the US Department of Justice charged IBM with destroying businesses " +"by bundling free software with IBM hardware. As a result of this suit, IBM " +"unbundled its software; that is, software became independent products " +"separate from hardware." +msgstr "" +"Em 1969, o Departamento de Justiça dos EUA acusou a IBM de destruir negócios " +"e empresas com seu agrupamento de software livre e hardware IBM. Como " +"resultado deste processo, a IBM separou seu software; isto é, os softwares " +"tornaram-se produtos independentes e separados do hardware." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:53 +msgid "" +"In 1968 Informatics introduced the first commercial killer-app and rapidly " +"established the concept of the software product, the software company, and " +"very high rates of return. Informatics developed the perpetual license " +"which is now standard throughout the computer industry, wherein ownership is " +"never transferred to the customer." +msgstr "" +"Em 1968, a Informatics apresentou o primeiro software comercial " +"revolucionário e rapidamente foi estabelecido o conceito do produto de " +"software, da empresa de software e de taxas de retorno bem altas. A " +"Informatics desenvolveu a licença perpétua que agora é comum em toda a " +"indústria de computadores, onde a propriedade do software nunca é " +"transferida para o cliente." + +#. type: Title == +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:55 +#, no-wrap +msgid "Unix from a BSD Licensing Perspective" +msgstr "Unix de uma Perspectiva de Licenciamento BSD" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:61 +msgid "" +"AT&T, who owned the original Unix implementation, was a publicly regulated " +"monopoly tied up in anti-trust court; it was legally unable to sell a " +"product into the software market. It was, however, able to provide it to " +"academic institutions for the price of media." +msgstr "" +"A AT&T, que detinha a implementação original do Unix, era um monopólio " +"regulado publicamente e amarrado a um tribunal anti-trust; ela foi " +"legalmente impossibilitada de vender um produto no mercado de software. " +"Entretanto, ela podia fornece-lo a instituições acadêmicas pelo preço da " +"mídia." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:67 +msgid "" +"Universities rapidly adopted Unix after an OS conference publicized its " +"availability. It was extremely helpful that Unix ran on the PDP-11, a very " +"affordable 16-bit computer, and was coded in a high-level language that was " +"demonstrably good for systems programming. The DEC PDP-11 had, in effect, " +"an open hardware interface designed to make it easy for customers to write " +"their own OS, which was common. As DEC founder Ken Olsen famously " +"proclaimed, \"software comes from heaven when you have good hardware\"." +msgstr "" +"As universidades adotaram rapidamente o Unix depois da divulgação de sua " +"disponibilidade em uma conferência de Sistema Operacional. Foi extremamente " +"útil o Unix rodar no PDP-11, um computador de 16 bits muito acessível na " +"época, e que foi codificado em uma linguagem de alto nível, que era " +"comprovadamente boa para a programação de sistemas. O DEC PDP-11 tinha, na " +"verdade, uma interface de hardware aberta, projetada para tornar mais fácil " +"para os clientes escreverem seus próprios sistemas operacionais, o que era " +"comum. O famoso fundador da DEC, Ken Olsen, proclamou que \"o software vem " +"do céu quando você tem um bom hardware\"." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:73 +msgid "" +"Unix author Ken Thompson returned to his alma mater, University of " +"California Berkeley (UCB), in 1975 and taught the kernel line-by-line. This " +"ultimately resulted in an evolving system known as BSD (Berkeley Standard " +"Distribution). UCB converted Unix to 32-bits, added virtual memory, and " +"implemented the version of the TCP/IP stack upon which the Internet was " +"essentially built. UCB made BSD available for the cost of media, under what " +"became known as \"the BSD license\". A customer purchased Unix from AT&T " +"and then ordered a BSD tape from UCB." +msgstr "" +"O autor do Unix, Ken Thompson, retornou à Universidade da Califórnia de " +"Berkeley (UCB) em 1975, e lecionou sobre o kernel linha por linha. Isso " +"acabou resultando em um sistema evoluído conhecido como BSD (Berkeley " +"Standard Distribution). A UCB converteu o Unix em 32 bits, adicionou memória " +"virtual e implementou a stack TCP/IP, a qual foi essencialmente necessária " +"para a construção da Internet. A UCB disponibilizou o BSD pelo custo da " +"mídia, e isso ficou conhecido como \"a licença BSD\". Um cliente comprava o " +"Unix da AT&T e depois comprava uma fita BSD da UCB." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:77 +msgid "" +"In the mid-1980s a government anti-trust case against AT&T ended with the " +"break-up of AT&T. AT&T still owned Unix and was now able to sell it. AT&T " +"embarked on an aggressive licensing effort and most commercial Unixes of the " +"day became AT&T-derived." +msgstr "" +"Em meados da década de 80, um processo anti-trust governamental contra a " +"AT&T resultou no seu desmembramento. A AT&T ainda possuía o Unix e a partir " +"daquele momento podia vendê-lo. Então a AT&T embarcou em um esforço " +"agressivo de licenciamento e a maioria dos Unixes comerciais da época " +"tornaram-se derivações do Unix AT&T." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:83 +msgid "" +"In the early 1990's AT&T sued UCB over license violations related to BSD. " +"UCB discovered that AT&T had incorporated, without acknowledgment or " +"payment, many improvements due to BSD into AT&T's products, and a lengthy " +"court case, primarily between AT&T and UCB, ensued. During this period some " +"UCB programmers embarked on a project to rewrite any AT&T code associated " +"with BSD. This project resulted in a system called BSD 4.4-lite (lite " +"because it was not a complete system; it lacked 6 key AT&T files)." +msgstr "" +"No início dos anos 90, a AT&T processou a UCB por violações de licenças " +"relacionadas ao BSD. A UCB descobriu que a AT&T havia incorporado, sem " +"reconhecimento ou pagamento, muitas melhorias nos produtos da AT&T " +"originadas no BSD, e isso resultou em um longo processo judicial entre a " +"AT&T e a UCB. Durante esse período, alguns programadores da UCB embarcaram " +"em um projeto para reescrever todos os códigos AT&T que estavam associados " +"ao BSD. Este projeto resultou em um sistema chamado BSD 4.4-lite (lite " +"porque não era um sistema completo; faltavam 6 arquivos-chave AT&T)." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:87 +msgid "" +"A lengthy series of articles published slightly later in Dr. Dobbs magazine " +"described a BSD-derived 386 PC version of Unix, with BSD-licensed " +"replacement files for the 6 missing 4.4 lite files. This system, named " +"386BSD, was due to ex-UCB programmer William Jolitz. It became the original " +"basis of all the PC BSDs in use today." +msgstr "" +"Uma longa série de artigos foram publicados um pouco depois disso na revista " +"Dr. Dobbs, que descreviam uma versão do Unix derivada do BSD para PC 386, na " +"qual os 6 arquivos que estavam faltando no 4.4 lite foram substituídos por " +"arquivos de licença BSD. Este sistema, chamado 386BSD, foi devido ao ex " +"programador da UCB, William Jolitz. Ele se tornou a base original de todos " +"os BSD para PCs que estão atualmente em uso." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:90 +msgid "" +"In the mid 1990s, Novell purchased AT&T's Unix rights and a (then secret) " +"agreement was reached to terminate the lawsuit. UCB soon terminated its " +"support for BSD." +msgstr "" +"Em meados da década de 90, a Novell comprou os direitos do Unix da AT&T e um " +"acordo (então secreto) foi fechado para encerrar o processo. A UCB logo " +"encerrou seu suporte para o BSD." + +#. type: Title == +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:92 +#, no-wrap +msgid "The Current State of FreeBSD and BSD Licenses" +msgstr "O Estado Atual das Licenças FreeBSD e BSD" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:98 +msgid "" +"The so-called http://www.opensource.org/licenses/bsd-license.php[new BSD " +"license] applied to FreeBSD within the last few years is effectively a " +"statement that you can do anything with the program or its source, but you " +"do not have any warranty and none of the authors has any liability " +"(basically, you cannot sue anybody). This new BSD license is intended to " +"encourage product commercialization. Any BSD code can be sold or included " +"in proprietary products without any restrictions on the availability of your " +"code or your future behavior." +msgstr "" +"A chamada http://www.opensource.org/licenses/bsd-license.php[nova licença " +"BSD] aplicada ao FreeBSD nos últimos anos é efetivamente uma afirmação de " +"que você pode fazer qualquer coisa com o programa ou seu código fonte, mas " +"você não tem nenhuma garantia e nenhum dos autores tem qualquer " +"responsabilidade (basicamente, você não pode processar ninguém). Esta nova " +"licença BSD destina-se a incentivar a comercialização de produtos. Qualquer " +"código BSD pode ser vendido ou incluído em produtos proprietários, sem " +"quaisquer restrições quanto à disponibilidade do seu código ou seu " +"comportamento futuro." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:101 +msgid "" +"Do not confuse the new BSD license with \"public domain\". While an item in " +"the public domain is also free for all to use, it has no owner." +msgstr "" +"Não confunda a nova licença BSD com \"domínio público\". Enquanto um item no " +"domínio público também é gratuito para todos, ele não possui um proprietário." + +#. type: Title == +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:103 +#, no-wrap +msgid "The origins of the GPL" +msgstr "As origens da GPL" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:107 +msgid "" +"While the future of Unix had been so muddled in the late 1980s and early " +"1990s, the GPL, another development with important licensing considerations, " +"reached fruition." +msgstr "" +"Enquanto o futuro do Unix era tão confuso no final dos anos 80 e início dos " +"anos 90, a GPL, um outro desenvolvimento com importantes considerações sobre " +"licenciamento, surgiu." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:116 +msgid "" +"Richard Stallman, the developer of Emacs, was a member of the staff at MIT " +"when his lab switched from home-grown to proprietary systems. Stallman " +"became upset when he found that he could not legally add minor improvements " +"to the system. (Many of Stallman's co-workers had left to form two " +"companies based on software developed at MIT and licensed by MIT; there " +"appears to have been disagreement over access to the source code for this " +"software). Stallman devised an alternative to the commercial software " +"license and called it the GPL, or \"GNU Public License\". He also started a " +"non-profit foundation, the http://www.fsf.org[Free Software Foundation] " +"(FSF), which intended to develop an entire operating system, including all " +"associated software, that would not be subject to proprietary licensing. " +"This system was called GNU, for \"GNU is Not Unix\"." +msgstr "" +"Richard Stallman, o desenvolvedor do Emacs, era membro da equipe do MIT " +"quando seu laboratório mudou de sistemas domésticos para sistemas " +"proprietários. Stallman ficou chateado quando descobriu que não podia " +"adicionar legalmente pequenas melhorias ao sistema. (Muitos dos colegas de " +"trabalho de Stallman tinham saído para formar duas empresas com base em " +"software desenvolvido no MIT e licenciado pelo MIT; parece ter havido " +"desacordo sobre o acesso ao código-fonte desse software). Stallman criou uma " +"alternativa para a licença de software comercial e a chamou de GPL, ou \"GNU " +"Public License\". Ele também fundou uma fundação sem fins lucrativos, a " +"http://www.fsf.org[Free Software Foundation] (FSF), que pretendia " +"desenvolver um sistema operacional completo, incluindo todos os softwares " +"associados, e que não estaria sujeito a uma licença proprietária. Este " +"sistema foi chamado de GNU, que significa \"GNU is Not Unix\"." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:121 +msgid "" +"The GPL was designed to be the antithesis of the standard proprietary " +"license. To this end, any modifications that were made to a GPL program " +"were required to be given back to the GPL community (by requiring that the " +"source of the program be available to the user) and any program that used or " +"linked to GPL code was required to be under the GPL. The GPL was intended " +"to keep software from becoming proprietary. As the last paragraph of the " +"GPL states:" +msgstr "" +"A GPL foi projetada para ser o oposto da licença proprietária padrão. Para " +"este fim, quaisquer modificações que eram feitas a um programa GPL tinham " +"que ser devolvidas à comunidade GPL (exigindo que o código fonte do programa " +"fosse disponibilizado para o usuário) e que qualquer programa que utilizar " +"ou linkar com código GPL, teria que estar sob a GPL. A GPL pretendia impedir " +"que o software se tornasse proprietário. Como o último parágrafo da GPL " +"afirma:" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:123 +msgid "" +"\"This General Public License does not permit incorporating your program " +"into proprietary programs.\"<>" +msgstr "" +"\"This General Public License does not permit incorporating your program " +"into proprietary programs.\"<>" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:125 +msgid "" +"The http://www.opensource.org/licenses/gpl-license.php[GPL] is a complex " +"license so here are some rules of thumb when using the GPL:" +msgstr "" +"A http://www.opensource.org/licenses/gpl-license.php[GPL] é uma licença " +"complexa, então aqui estão algumas regras básicas ao usar a GPL:" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:127 +msgid "" +"you can charge as much as you want for distributing, supporting, or " +"documenting the software, but you cannot sell the software itself." +msgstr "" +"você pode cobrar o quanto quiser para distribuir, dar suporte ou documentar " +"o software, mas não pode vender o software em si." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:128 +msgid "" +"the rule-of-thumb states that if GPL source is required for a program to " +"compile, the program must be under the GPL. Linking statically to a GPL " +"library requires a program to be under the GPL." +msgstr "" +"a regra básica indica que, se um código fonte GPL for necessário para um " +"programa compilar, então o programa deve estar sob a GPL. Linkar " +"estaticamente a uma biblioteca GPL requer que um programa esteja sob a GPL." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:129 +msgid "" +"the GPL requires that any patents associated with GPLed software must be " +"licensed for everyone's free use." +msgstr "" +"a GPL exige que quaisquer patentes associadas ao software GPL sejam " +"licenciadas para uso livre de todos." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:130 +msgid "" +"simply aggregating software together, as when multiple programs are put on " +"one disk, does not count as including GPLed programs in non-GPLed programs." +msgstr "" +"simplesmente agregar softwares juntos, como quando vários programas são " +"colocados em um disco, não conta como inclusão de programas GPL em programas " +"não-GPL." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:131 +msgid "" +"output of a program does not count as a derivative work. This enables the " +"gcc compiler to be used in commercial environments without legal problems." +msgstr "" +"o que se resulta de um programa não conta como um trabalho derivado. Isso " +"permite que o compilador gcc seja utilizado em ambientes comerciais sem " +"problemas legais." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:132 +msgid "" +"since the Linux kernel is under the GPL, any code statically linked with the " +"Linux kernel must be GPLed. This requirement can be circumvented by " +"dynamically linking loadable kernel modules. This permits companies to " +"distribute binary drivers, but often has the disadvantage that they will " +"only work for particular versions of the Linux kernel." +msgstr "" +"como o kernel do Linux está sob a GPL, qualquer código estaticamente linkado " +"ao kernel do Linux deve ser GPL. Este requisito pode ser contornado ao " +"linkar dinamicamente módulos carregáveis do kernel. Isso permite que as " +"empresas distribuam drivers binários, mas geralmente tem a desvantagem de " +"que eles só funcionarão para versões específicas do kernel do Linux." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:135 +msgid "" +"Due in part to its complexity, in many parts of the world today the " +"legalities of the GPL are being ignored in regard to Linux and related " +"software. The long-term ramifications of this are unclear." +msgstr "" +"Devido em parte à sua complexidade, em muitas partes do mundo hoje as " +"legalidades da GPL estão sendo ignoradas em relação ao Linux e softwares " +"relacionados. As ramificações de longo prazo por causa disso não são claras." + +#. type: Title == +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:137 +#, no-wrap +msgid "The origins of Linux and the LGPL" +msgstr "As origens do Linux e da LGPL" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:142 +msgid "" +"While the commercial Unix wars raged, the Linux kernel was developed as a PC " +"Unix clone. Linus Torvalds credits the existence of the GNU C compiler and " +"the associated GNU tools for the existence of Linux. He put the Linux " +"kernel under the GPL." +msgstr "" +"Enquanto as guerras comerciais do Unix se intensificavam, o kernel do Linux " +"foi desenvolvido como um clone do PC Unix. Linus Torvalds credita a " +"existência do compilador GNU C e das ferramentas GNU associadas pela " +"existência do Linux. Ele colocou o kernel do Linux sob a GPL." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:151 +msgid "" +"Remember that the GPL requires anything that statically links to any code " +"under the GPL also be placed under the GPL. The source for this code must " +"thus be made available to the user of the program. Dynamic linking, " +"however, is not considered a violation of the GPL. Pressure to put " +"proprietary applications on Linux became overwhelming. Such applications " +"often must link with system libraries. This resulted in a modified version " +"of the GPL called the http://www.opensource.org/licenses/lgpl-license." +"php[LGPL] (\"Library\", since renamed to \"Lesser\", GPL). The LGPL allows " +"proprietary code to be linked to the GNU C library, glibc. You do not have " +"to release the source code which has been dynamically linked to an LGPLed " +"library." +msgstr "" +"Lembre-se de que a GPL requer que qualquer software que seja estaticamente " +"linkado a um código GPL, também seja colocado sob a GPL. O código fonte " +"desse software deve ser disponibilizado ao usuário do programa. O link " +"dinâmico, no entanto, não é considerado uma violação da GPL. A pressão para " +"colocar aplicativos proprietários no Linux tornou-se esmagadora. Tais " +"aplicativos geralmente precisavam se linkar a bibliotecas do sistema. Isso " +"resultou em uma versão modificada da GPL chamada http://www.opensource.org/" +"licenses/lgpl-license.php[LGPL] (\"Library\", e depois renomeado para " +"\"Lesser\", GPL). A LGPL permite que o código proprietário faça link com à " +"biblioteca GNU C, glibc. Você não precisa liberar o código fonte que foi " +"linkado dinamicamente a uma biblioteca LGPL." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:155 +msgid "" +"If you statically link an application with glibc, such as is often required " +"in embedded systems, you cannot keep your application proprietary, that is, " +"the source must be released. Both the GPL and LGPL require any " +"modifications to the code directly under the license to be released." +msgstr "" +"Se você linkar estaticamente uma aplicação com a glibc, o que geralmente é " +"necessário em sistemas embarcados, não será possível manter seu aplicativo " +"proprietário, isto é, o código fonte deve ser liberado. Tanto a GPL quanto a " +"LGPL requerem que qualquer software sob suas licenças liberem quaisquer " +"modificações no código fonte." + +#. type: Title == +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:157 +#, no-wrap +msgid "Open Source licenses and the Orphaning Problem" +msgstr "Licenças Open Source e o Problema dos Softwares Orfãos" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:162 +msgid "" +"One of the serious problems associated with proprietary software is known as " +"\"orphaning\". This occurs when a single business failure or change in a " +"product strategy causes a huge pyramid of dependent systems and companies to " +"fail for reasons beyond their control. Decades of experience have shown " +"that the momentary size or success of a software supplier is no guarantee " +"that their software will remain available, as current market conditions and " +"strategies can change rapidly." +msgstr "" +"Um problema sério associado ao software proprietário é conhecido como " +"\"orphaning\". Isso ocorre quando um simples negócio falha ou quando uma " +"mudança na estratégia de um produto faz com que uma cadeia de sistemas e " +"empresas que dependiam deste produto, também falhem por motivos que estão " +"fora de seus controles. Décadas de experiência mostraram que o tamanho ou o " +"sucesso momentâneo de um fornecedor de software não é uma garantia de que " +"seu software permanecerá disponível, pois as condições e estratégias atuais " +"do mercado podem mudar rapidamente." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:164 +msgid "" +"The GPL attempts to prevent orphaning by severing the link to proprietary " +"intellectual property." +msgstr "" +"A GPL tenta impedir o software órfão cortando o link para a propriedade " +"intelectual proprietária." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:169 +msgid "" +"A BSD license gives a small company the equivalent of software-in-escrow " +"without any legal complications or costs. If a BSD-licensed program becomes " +"orphaned, a company can simply take over, in a proprietary manner, the " +"program on which they are dependent. An even better situation occurs when a " +"BSD code-base is maintained by a small informal consortium, since the " +"development process is not dependent on the survival of a single company or " +"product line. The survivability of the development team when they are " +"mentally in the zone is much more important than simple physical " +"availability of the source code." +msgstr "" +"Uma licença BSD concede a uma pequena empresa o equivalente a um software-in-" +"escrow sem quaisquer complicações ou custos legais. Se um programa " +"licenciado pela BSD se torna órfão, uma empresa pode simplesmente assumir, " +"de maneira proprietária, o programa do qual eles são dependentes. Uma " +"situação ainda melhor ocorre quando uma base de código BSD é mantida por um " +"pequeno consórcio informal, uma vez que o processo de desenvolvimento não " +"depende da sobrevivência de uma única empresa ou de uma linha de produtos. A " +"capacidade de sobrevivência da equipe de desenvolvimento quando eles estão " +"mentalmente seguros é muito mais importante do que a simples disponibilidade " +"física do código-fonte." + +#. type: Title == +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:171 +#, no-wrap +msgid "What a license cannot do" +msgstr "O que uma licença não pode fazer" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:175 +msgid "" +"No license can guarantee future software availability. Although a copyright " +"holder can traditionally change the terms of a copyright at anytime, the " +"presumption in the BSD community is that such an attempt simply causes the " +"source to fork." +msgstr "" +"Nenhuma licença pode garantir disponibilidade futura do software. Embora um " +"detentor de direitos autorais possa tradicionalmente mudar os termos de um " +"direito autoral a qualquer momento, a presunção na comunidade BSD é de que " +"tal tentativa simplesmente faz com que o código fonte seja derivado (fork)." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:181 +msgid "" +"The GPL explicitly disallows revoking the license. It has occurred, " +"however, that a company (Mattel) purchased a GPL copyright (cphack), revoked " +"the entire copyright, went to court, and prevailed <>. That is, they " +"legally revoked the entire distribution and all derivative works based on " +"the copyright. Whether this could happen with a larger and more dispersed " +"distribution is an open question; there is also some confusion regarding " +"whether the software was really under the GPL." +msgstr "" +"A GPL proíbe explicitamente a revogação da licença. Ocorreu no entanto, que " +"uma empresa (Mattel) comprou um copyright GPL (cphack), e revogou todo o " +"direito autoral, foi a tribunal e conseguiu prevalecer <>. Ou seja, " +"eles revogaram legalmente toda a distribuição e todos os trabalhos derivados " +"com base nos direitos autorais. Se isso pode acontecer com uma distribuição " +"maior e mais dispersa, fica uma questão em aberto; Há também alguma confusão " +"sobre se o software estava realmente sob a GPL." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:186 +msgid "" +"In another example, Red Hat purchased Cygnus, an engineering company that " +"had taken over development of the FSF compiler tools. Cygnus was able to do " +"so because they had developed a business model in which they sold support " +"for GNU software. This enabled them to employ some 50 engineers and drive " +"the direction of the programs by contributing the preponderance of " +"modifications. As Donald Rosenberg states \"projects using licenses like " +"the GPL...live under constant threat of having someone take over the project " +"by producing a better version of the code and doing it faster than the " +"original owners.\" <>" +msgstr "" +"Em outro exemplo, a Red Hat comprou a Cygnus, uma empresa de engenharia que " +"havia assumido o desenvolvimento das ferramentas de compilação da FSF. A " +"Cygnus foi capaz de fazer isso porque eles desenvolveram um modelo de " +"negócios no qual eles vendiam suporte para o software GNU. Isso permitiu que " +"eles empregassem cerca de 50 engenheiros e os orientassem na direção dos " +"programas, contribuindo com a preponderância de modificações. Como afirma " +"Donald Rosenberg, \"projetos usando licenças como a GPL ... vivem sob " +"constante ameaça de que alguém assuma o projeto produzindo uma versão melhor " +"do código e fazendo isso mais rápido que os proprietários originais\". " +"<>" + +#. type: Title == +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:188 +#, no-wrap +msgid "GPL Advantages and Disadvantages" +msgstr "Vantagens e Desvantagens da GPL" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:192 +msgid "" +"A common reason to use the GPL is when modifying or extending the gcc " +"compiler. This is particularly apt when working with one-off specialty CPUs " +"in environments where all software costs are likely to be considered " +"overhead, with minimal expectations that others will use the resulting " +"compiler." +msgstr "" +"Um motivo comum para usar a GPL é ao modificar ou criar extensões ao " +"compilador gcc. Isso é particularmente apropriado quando se trabalha com " +"CPUs especiais únicas em ambientes em que todos os custos de software " +"provavelmente são considerados como despesas gerais, com expectativas " +"mínimas de que outros usarão o compilador resultante." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:195 +msgid "" +"The GPL is also attractive to small companies selling CDs in an environment " +"where \"buy-low, sell-high\" may still give the end-user a very inexpensive " +"product. It is also attractive to companies that expect to survive by " +"providing various forms of technical support, including documentation, for " +"the GPLed intellectual property world." +msgstr "" +"A GPL também é atraente para pequenas empresas que vendem CDs em um ambiente " +"em que o \"buy-low, sell-high\" ainda pode dar ao usuário final um produto " +"muito barato. Também é atraente para empresas que esperam sobreviver " +"fornecendo várias formas de suporte técnico, incluindo documentação, para o " +"mundo da propriedade intelectual GPL." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:198 +msgid "" +"A less publicized and unintended use of the GPL is that it is very favorable " +"to large companies that want to undercut software companies. In other " +"words, the GPL is well suited for use as a marketing weapon, potentially " +"reducing overall economic benefit and contributing to monopolistic behavior." +msgstr "" +"Um uso menos divulgado e não intencional da GPL é que ela é muito favorável " +"a grandes empresas que querem minar empresas de software. Em outras " +"palavras, a GPL é bem adequada para uso como arma de marketing, reduzindo " +"potencialmente o benefício econômico geral e contribuindo para o " +"comportamento monopolista." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:201 +msgid "" +"The GPL can present a real problem for those wishing to commercialize and " +"profit from software. For example, the GPL adds to the difficulty a " +"graduate student will have in directly forming a company to commercialize " +"his research results, or the difficulty a student will have in joining a " +"company on the assumption that a promising research project will be " +"commercialized." +msgstr "" +"A GPL pode representar um problema real para aqueles que desejam " +"comercializar e lucrar com software. Por exemplo, a GPL aumenta a " +"dificuldade que um estudante de pós-graduação terá em formar diretamente uma " +"empresa para comercializar seus resultados de pesquisa, ou a dificuldade que " +"um aluno terá em ingressar em uma empresa com a suposição de que um " +"promissor projeto de pesquisa será comercializado." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:206 +msgid "" +"For those who must work with statically-linked implementations of multiple " +"software standards, the GPL is often a poor license, because it precludes " +"using proprietary implementations of the standards. The GPL thus minimizes " +"the number of programs that can be built using a GPLed standard. The GPL " +"was intended to not provide a mechanism to develop a standard on which one " +"engineers proprietary products. (This does not apply to Linux applications " +"because they do not statically link, rather they use a trap-based API.)" +msgstr "" +"Para aqueles que precisam trabalhar com implementações linkadas " +"estaticamente em vários modelos de software, a GPL é geralmente uma licença " +"ruim, porque impede o uso de implementações proprietárias dos modelos. A GPL " +"minimiza, assim, o número de programas que podem ser compilados usando o " +"modelo GPL. A GPL tinha como objetivo não fornecer um mecanismo para " +"desenvolver um padrão na engenharia de produtos proprietários. (Isso não se " +"aplica a aplicativos Linux porque eles não usam links estáticos, em vez " +"disso, usam uma trap-based API.)" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:210 +msgid "" +"The GPL attempts to make programmers contribute to an evolving suite of " +"programs, then to compete in the distribution and support of this suite. " +"This situation is unrealistic for many required core system standards, which " +"may be applied in widely varying environments which require commercial " +"customization or integration with legacy standards under existing (non-GPL) " +"licenses. Real-time systems are often statically linked, so the GPL and " +"LGPL are definitely considered potential problems by many embedded systems " +"companies." +msgstr "" +"A GPL tenta fazer com que os programadores contribuam para um conjunto de " +"programas em desenvolvimento, para então competir na distribuição e suporte " +"deste conjunto. Essa situação não é realista para muitos dos padrões de " +"sistema exigidos, que podem ser aplicados em ambientes amplamente " +"diferentes, e que exigem personalização comercial ou integração com padrões " +"legados sob licenças existentes (não-GPL). Os sistemas real-time usam " +"frequentemente links estáticos, de modo que a GPL e a LGPL são " +"definitivamente consideradas problemas potenciais por muitas empresas de " +"sistemas embarcados." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:213 +msgid "" +"The GPL is an attempt to keep efforts, regardless of demand, at the research " +"and development stages. This maximizes the benefits to researchers and " +"developers, at an unknown cost to those who would benefit from wider " +"distribution." +msgstr "" +"A GPL é uma tentativa de manter os trabalhos disponíveis, independentemente " +"da demanda nos estágios de pesquisa e desenvolvimento. Isso maximiza os " +"benefícios para pesquisadores e desenvolvedores, a um custo desconhecido " +"para aqueles que se beneficiariam de uma distribuição mais ampla." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:217 +msgid "" +"The GPL was designed to keep research results from transitioning to " +"proprietary products. This step is often assumed to be the last step in the " +"traditional technology transfer pipeline and it is usually difficult enough " +"under the best of circumstances; the GPL was intended to make it impossible." +msgstr "" +"A GPL foi projetada para impedir que os resultados de uma pesquisa sejam " +"transferidos para produtos proprietários. Este passo é frequentemente " +"considerado o último passo no pipeline tradicional de transferência de " +"tecnologia e é geralmente o mais difícil mesmo sob as melhores " +"circunstâncias; a GPL pretendia tornar isso impossível." + +#. type: Title == +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:219 +#, no-wrap +msgid "BSD Advantages" +msgstr "Vantagens da licença BSD" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:222 +msgid "" +"A BSD style license is a good choice for long duration research or other " +"projects that need a development environment that:" +msgstr "" +"Uma licença de estilo BSD é uma boa opção para pesquisas de longa duração ou " +"outros projetos que precisam de um ambiente de desenvolvimento que:" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:224 +msgid "has near zero cost" +msgstr "tem custo próximo a zero" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:225 +msgid "will evolve over a long period of time" +msgstr "irá evoluir durante um longo período de tempo" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:226 +msgid "" +"permits anyone to retain the option of commercializing final results with " +"minimal legal issues." +msgstr "" +"permite que qualquer pessoa mantenha a opção de comercializar os resultados " +"finais com problemas legais mínimos." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:228 +msgid "" +"This final consideration may often be the dominant one, as it was when the " +"Apache project decided upon its license:" +msgstr "" +"Esta consideração final pode muitas vezes ser a dominante, como foi quando o " +"projeto Apache decidiu sua licença:" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:232 +msgid "" +"\"This type of license is ideal for promoting the use of a reference body of " +"code that implements a protocol for common service. This is another reason " +"why we choose it for the Apache group - many of us wanted to see HTTP " +"survive and become a true multiparty standard, and would not have minded in " +"the slightest if Microsoft or Netscape choose to incorporate our HTTP engine " +"or any other component of our code into their products, if it helped further " +"the goal of keeping HTTP common... All this means that, strategically " +"speaking, the project needs to maintain sufficient momentum, and that " +"participants realize greater value by contributing their code to the " +"project, even code that would have had value if kept proprietary.\"" +msgstr "" +"\"Este tipo de licença é ideal para promover o uso de um corpo de referência " +"de código que implementa um protocolo para um serviço comum. Esta é outra " +"razão pela qual a escolhemos para o grupo Apache - muitos de nós queriam que " +"o HTTP sobrevivesse e se tornasse um verdadeiro padrão multipartidário, e " +"não nos importaríamos nem um pouco se a Microsoft ou a Netscape escolhessem " +"incorporar nosso mecanismo HTTP ou qualquer outro componente de nosso código " +"em seus produtos, se isso ajudasse a manter o objetivo comum de manter o " +"HTTP universal... Tudo isso significa que, estrategicamente falando, o " +"projeto precisa manter ímpeto suficiente e que os participantes percebam um " +"maior valor contribuindo com seu código para o projeto, mesmo código que " +"teria valor se fosse mantido proprietário.\"" + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:236 +msgid "" +"Developers tend to find the BSD license attractive as it keeps legal issues " +"out of the way and lets them do whatever they want with the code. In " +"contrast, those who expect primarily to use a system rather than program it, " +"or expect others to evolve the code, or who do not expect to make a living " +"from their work associated with the system (such as government employees), " +"find the GPL attractive, because it forces code developed by others to be " +"given to them and keeps their employer from retaining copyright and thus " +"potentially \"burying\" or orphaning the software. If you want to force " +"your competitors to help you, the GPL is attractive." +msgstr "" +"Os desenvolvedores tendem a achar a licença BSD atrativa, pois ela mantém os " +"problemas legais fora do caminho e permite que eles façam o que quiserem com " +"o código. Em contraste, aqueles que esperam principalmente usar um sistema " +"em vez de programá-lo, ou que esperam que outros evoluam o código, ou " +"aqueles que não esperam ganhar a vida com seu trabalho associado ao sistema (" +"como funcionários do governo), achem a GPL atraente, porque força o código " +"desenvolvido por outros a ser dado a eles de volta e impede que os seus " +"empregadores retenham os direitos autorais e, portanto, potencialmente " +"\"enterra\" o problema de software órfão. Se você quiser forçar seus " +"concorrentes a ajudá-lo, a GPL é atraente." + +#. type: Plain text +#: documentation/content/en/articles/bsdl-gpl/_index.adoc:243 +msgid "" +"A BSD license is not simply a gift. The question \"why should we help our " +"competitors or let them steal our work?\" comes up often in relation to a " +"BSD license. Under a BSD license, if one company came to dominate a product " +"niche that others considered strategic, the other companies can, with " +"minimal effort, form a mini-consortium aimed at reestablishing parity by " +"contributing to a competitive BSD variant that increases market competition " +"and fairness. This permits each company to believe that it will be able to " +"profit from some advantage it can provide, while also contributing to " +"economic flexibility and efficiency. The more rapidly and easily the " +"cooperating members can do this, the more successful they will be. A BSD " +"license is essentially a minimally complicated license that enables such " +"behavior." +msgstr "" +"Uma licença BSD não é simplesmente um presente. A pergunta \"por que devemos " +"ajudar nossos concorrentes ou deixá-los roubar nosso trabalho?\" surge " +"frequentemente em relação a uma licença BSD. Sob uma licença BSD, se uma " +"empresa vier a dominar um nicho de produto que outros consideram " +"estratégico, as outras empresas podem, com esforço mínimo, formar um mini " +"consórcio visando restabelecer a paridade, contribuindo para uma variante " +"BSD competitiva que aumente a competição e a justiça no mercado. Isso " *** 270 LINES SKIPPED *** From owner-dev-commits-doc-all@freebsd.org Sat Jun 5 01:26:39 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id DF3B3638AB5 for ; Sat, 5 Jun 2021 01:26:39 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fxhmv5T9gz3jb9; Sat, 5 Jun 2021 01:26:39 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 9831F27940; Sat, 5 Jun 2021 01:26:39 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 1551QdF5004194; Sat, 5 Jun 2021 01:26:39 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 1551QdhI004193; Sat, 5 Jun 2021 01:26:39 GMT (envelope-from git) Date: Sat, 5 Jun 2021 01:26:39 GMT Message-Id: <202106050126.1551QdhI004193@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: "Danilo G. Baio" Subject: git: 3cb477eaad - main - website: Move google-site-verification to the static dir MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: dbaio X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 3cb477eaad92143493e65da8a33c01794d8577b4 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2021 01:26:39 -0000 The branch main has been updated by dbaio: URL: https://cgit.FreeBSD.org/doc/commit/?id=3cb477eaad92143493e65da8a33c01794d8577b4 commit 3cb477eaad92143493e65da8a33c01794d8577b4 Author: Danilo G. Baio AuthorDate: 2021-06-05 01:20:15 +0000 Commit: Danilo G. Baio CommitDate: 2021-06-05 01:20:15 +0000 website: Move google-site-verification to the static dir There are many build failures with timeout on our ci, with the following message: Error: Error building site: "/workspace/doc/website/content/en/google96eb5b100ed66487.html:1:1": timed out initializing value. You may have a circular loop in a shortcode, or your site may have resources that take longer to build than the `timeout` limit in your Hugo config file. *** [build] Error code 255 This is an attempt to fix that without increasing timeout, this way Hugo won't handle these files anymore. Structure before: $ find website/public/ | grep google website/public/google96eb5b100ed66487 website/public/google96eb5b100ed66487/index.html website/public/google6bb24ed0b804d5e9 website/public/google6bb24ed0b804d5e9/index.html After: $ find website/public/ | grep google website/public/google6bb24ed0b804d5e9.html website/public/google96eb5b100ed66487.html PR: 256367 Reported by: wosch --- website/{content/en => static}/google6bb24ed0b804d5e9.html | 0 website/{content/en => static}/google96eb5b100ed66487.html | 0 2 files changed, 0 insertions(+), 0 deletions(-) diff --git a/website/content/en/google6bb24ed0b804d5e9.html b/website/static/google6bb24ed0b804d5e9.html similarity index 100% rename from website/content/en/google6bb24ed0b804d5e9.html rename to website/static/google6bb24ed0b804d5e9.html diff --git a/website/content/en/google96eb5b100ed66487.html b/website/static/google96eb5b100ed66487.html similarity index 100% rename from website/content/en/google96eb5b100ed66487.html rename to website/static/google96eb5b100ed66487.html From owner-dev-commits-doc-all@freebsd.org Sat Jun 5 09:33:36 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7C1CD63FB62 for ; Sat, 5 Jun 2021 09:33:36 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FxvZm2hJLz4jLY; Sat, 5 Jun 2021 09:33:36 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 4440C622A; Sat, 5 Jun 2021 09:33:36 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 1559Xata051416; Sat, 5 Jun 2021 09:33:36 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 1559Xa7D051415; Sat, 5 Jun 2021 09:33:36 GMT (envelope-from git) Date: Sat, 5 Jun 2021 09:33:36 GMT Message-Id: <202106050933.1559Xa7D051415@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Marc Fonvieille Subject: git: e89d34ab6a - main - pl/: Fix include links for PDF. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: blackend X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: e89d34ab6a13676efad6c0ecc78fe582543e9133 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2021 09:33:36 -0000 The branch main has been updated by blackend: URL: https://cgit.FreeBSD.org/doc/commit/?id=e89d34ab6a13676efad6c0ecc78fe582543e9133 commit e89d34ab6a13676efad6c0ecc78fe582543e9133 Author: Marc Fonvieille AuthorDate: 2021-06-05 09:31:56 +0000 Commit: Marc Fonvieille CommitDate: 2021-06-05 09:31:56 +0000 pl/: Fix include links for PDF. --- .../content/pl/articles/filtering-bridges/_index.adoc | 10 ++++++++++ documentation/content/pl/books/handbook/book.adoc | 4 ++-- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/documentation/content/pl/articles/filtering-bridges/_index.adoc b/documentation/content/pl/articles/filtering-bridges/_index.adoc index 4525307679..018e7cb6ae 100644 --- a/documentation/content/pl/articles/filtering-bridges/_index.adoc +++ b/documentation/content/pl/articles/filtering-bridges/_index.adoc @@ -24,7 +24,17 @@ trademarks: ["freebsd", "3com", "intel", "general"] :figure-caption: Rysunek :example-caption: Przykład +ifeval::["{backend}" == "html5"] include::shared/pl/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "pdf"] +include::../../../../shared/pl/urls.adoc[] +endif::[] + +ifeval::["{backend}" == "epub3"] +include::../../../../shared/pl/urls.adoc[] +endif::[] [.abstract-title] Abstrakt diff --git a/documentation/content/pl/books/handbook/book.adoc b/documentation/content/pl/books/handbook/book.adoc index 8979e3f0b2..0f77022886 100644 --- a/documentation/content/pl/books/handbook/book.adoc +++ b/documentation/content/pl/books/handbook/book.adoc @@ -48,7 +48,7 @@ include::../../../../shared/authors.adoc[] include::../../../../shared/releases.adoc[] include::../../../../shared/pl/mailing-lists.adoc[] include::../../../../shared/pl/urls.adoc[] -include::shared/pl/teams.adoc[] +include::../../../../shared/pl/teams.adoc[] :chapters-path: endif::[] @@ -58,7 +58,7 @@ include::../../../../shared/authors.adoc[] include::../../../../shared/releases.adoc[] include::../../../../shared/pl/mailing-lists.adoc[] include::../../../../shared/pl/urls.adoc[] -include::shared/pl/teams.adoc[] +include::../../../../shared/pl/teams.adoc[] :chapters-path: endif::[] From owner-dev-commits-doc-all@freebsd.org Sat Jun 5 17:31:16 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 7E978647342 for ; Sat, 5 Jun 2021 17:31:16 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fy69w3CmQz3kQL; Sat, 5 Jun 2021 17:31:16 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 56BB114C09; Sat, 5 Jun 2021 17:31:16 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 155HVGXG085451; Sat, 5 Jun 2021 17:31:16 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 155HVGbi085450; Sat, 5 Jun 2021 17:31:16 GMT (envelope-from git) Date: Sat, 5 Jun 2021 17:31:16 GMT Message-Id: <202106051731.155HVGbi085450@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: "Danilo G. Baio" Subject: git: 163f29fb33 - main - Add support to Hugo arguments/flags MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: dbaio X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 163f29fb33bf5cd8101635f5c7cddfcc04a0d28d Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2021 17:31:16 -0000 The branch main has been updated by dbaio: URL: https://cgit.FreeBSD.org/doc/commit/?id=163f29fb33bf5cd8101635f5c7cddfcc04a0d28d commit 163f29fb33bf5cd8101635f5c7cddfcc04a0d28d Author: Danilo G. Baio AuthorDate: 2021-06-05 17:25:34 +0000 Commit: Danilo G. Baio CommitDate: 2021-06-05 17:25:34 +0000 Add support to Hugo arguments/flags This also enables verbose output by default, same behavior we had in the doc tree before Hugo/Asciidoctor and add --minify to HUGO_ARGS variable to make it optional. Reviewed by: ceri, allanjude, imp Differential Revision: https://reviews.freebsd.org/D30652 --- documentation/Makefile | 5 +++-- website/Makefile | 5 +++-- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/documentation/Makefile b/documentation/Makefile index a10461f4ae..606d79c30f 100644 --- a/documentation/Makefile +++ b/documentation/Makefile @@ -21,6 +21,7 @@ LOCALBASE?= /usr/local PYTHON_CMD = ${LOCALBASE}/bin/python3 RUBY_CMD = ${LOCALBASE}/bin/ruby HUGO_CMD = ${LOCALBASE}/bin/hugo +HUGO_ARGS?= --verbose --minify ASCIIDOCTORPDF_CMD= ${LOCALBASE}/bin/asciidoctor-pdf .if defined(DOC_LANG) && !empty(DOC_LANG) LANGUAGES = ${DOC_LANG} @@ -78,10 +79,10 @@ static/pgpkeys/pgpkeys.txt: static/pgpkeys/*key ${RUBY_CMD} ./tools/global-pgpkeys-creator.rb run-local: .PHONY - ${HUGO_CMD} server -D $(BIND:D--bind=$(BIND)) --baseURL="http://$(.HOST):1313" + ${HUGO_CMD} server ${HUGO_ARGS} -D $(BIND:D--bind=$(BIND)) --baseURL="http://$(.HOST):1313" build: .PHONY - ${HUGO_CMD} --minify + ${HUGO_CMD} ${HUGO_ARGS} # # PDF targets diff --git a/website/Makefile b/website/Makefile index 560c7b8d45..fbee771541 100644 --- a/website/Makefile +++ b/website/Makefile @@ -17,6 +17,7 @@ MAINTAINER=carlavilla@FreeBSD.org PYTHON_CMD = /usr/local/bin/python3 HUGO_CMD = /usr/local/bin/hugo +HUGO_ARGS?= --verbose RUBYLIB = ../shared/lib .export RUBYLIB @@ -51,10 +52,10 @@ generate-releases: .PHONY ${PYTHON_CMD} ./tools/releases-toml.py -p ./shared/releases.adoc run-local: .PHONY - ${HUGO_CMD} server -D $(BIND:D--bind=$(BIND)) --baseURL="http://$(.HOST):1313" + ${HUGO_CMD} server ${HUGO_ARGS} -D $(BIND:D--bind=$(BIND)) --baseURL="http://$(.HOST):1313" build: .PHONY - ${HUGO_CMD} + ${HUGO_CMD} ${HUGO_ARGS} post-build: cgi-permissions From owner-dev-commits-doc-all@freebsd.org Sat Jun 5 18:31:29 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A68B7647F1E for ; Sat, 5 Jun 2021 18:31:29 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fy7WP4MtZz3mKJ; Sat, 5 Jun 2021 18:31:29 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 7E62015539; Sat, 5 Jun 2021 18:31:29 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 155IVTDd067342; Sat, 5 Jun 2021 18:31:29 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 155IVTtd067341; Sat, 5 Jun 2021 18:31:29 GMT (envelope-from git) Date: Sat, 5 Jun 2021 18:31:29 GMT Message-Id: <202106051831.155IVTtd067341@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: "Danilo G. Baio" Subject: git: 11f77bb410 - main - Cirrus CI: Fix build, and Add build verbosity MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: dbaio X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 11f77bb4105d884f15e2f94125e34773f822ff72 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2021 18:31:29 -0000 The branch main has been updated by dbaio: URL: https://cgit.FreeBSD.org/doc/commit/?id=11f77bb4105d884f15e2f94125e34773f822ff72 commit 11f77bb4105d884f15e2f94125e34773f822ff72 Author: Danilo G. Baio AuthorDate: 2021-06-05 18:28:56 +0000 Commit: Danilo G. Baio CommitDate: 2021-06-05 18:28:56 +0000 Cirrus CI: Fix build, and Add build verbosity While here: - Relax resources, default is 2 CPUs and 4 GBs of memory - Use newer FreeBSD image --- .cirrus.yml | 9 +++------ 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/.cirrus.yml b/.cirrus.yml index 4edb6ca00b..e96f8a8e50 100644 --- a/.cirrus.yml +++ b/.cirrus.yml @@ -1,16 +1,13 @@ freebsd_instance: - image_family: freebsd-12-2-snap - cpu: 8 - memory: 16G + image_family: freebsd-13-0-snap env: CIRRUS_CLONE_DEPTH: 1 task: - only_if: $CIRRUS_BRANCH != 'svn_head' timeout_in: 10m install_script: - - pkg install -y gohugo python37 rubygem-asciidoctor rubygem-rouge + - pkg install -y docproj python3 test_script: - - make + - make HUGO_ARGS="--verbose --debug --path-warnings" From owner-dev-commits-doc-all@freebsd.org Sat Jun 5 18:50:09 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 5B7F3647ED2 for ; Sat, 5 Jun 2021 18:50:09 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fy7wx1zgMz3n7M; Sat, 5 Jun 2021 18:50:09 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 29A5C15565; Sat, 5 Jun 2021 18:50:09 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 155Io9EX084804; Sat, 5 Jun 2021 18:50:09 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 155Io9tE084800; Sat, 5 Jun 2021 18:50:09 GMT (envelope-from git) Date: Sat, 5 Jun 2021 18:50:09 GMT Message-Id: <202106051850.155Io9tE084800@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: "Danilo G. Baio" Subject: git: 9a8282e7d2 - main - Cirrus CI: Increase timeout to 20 minutes MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: dbaio X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 9a8282e7d2151ea37ecd313de5210f77ea5393a4 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Jun 2021 18:50:09 -0000 The branch main has been updated by dbaio: URL: https://cgit.FreeBSD.org/doc/commit/?id=9a8282e7d2151ea37ecd313de5210f77ea5393a4 commit 9a8282e7d2151ea37ecd313de5210f77ea5393a4 Author: Danilo G. Baio AuthorDate: 2021-06-05 18:49:07 +0000 Commit: Danilo G. Baio CommitDate: 2021-06-05 18:49:07 +0000 Cirrus CI: Increase timeout to 20 minutes --- .cirrus.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.cirrus.yml b/.cirrus.yml index e96f8a8e50..a61946529e 100644 --- a/.cirrus.yml +++ b/.cirrus.yml @@ -5,7 +5,7 @@ env: CIRRUS_CLONE_DEPTH: 1 task: - timeout_in: 10m + timeout_in: 20m install_script: - pkg install -y docproj python3 test_script: From owner-dev-commits-doc-all@freebsd.org Sun Jun 6 09:16:08 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 9258E65A67D for ; Sun, 6 Jun 2021 09:16:08 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FyW883fjjz4TLb; Sun, 6 Jun 2021 09:16:08 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 65396210C7; Sun, 6 Jun 2021 09:16:08 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 1569G8IH034088; Sun, 6 Jun 2021 09:16:08 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 1569G7Bf034082; Sun, 6 Jun 2021 09:16:07 GMT (envelope-from git) Date: Sun, 6 Jun 2021 09:16:07 GMT Message-Id: <202106060916.1569G7Bf034082@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Sergio Carlavilla Delgado Subject: git: a8c5c8965c - main - Use One Sentence Per Line in the Handbook MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: carlavilla X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: a8c5c8965cd534ff9634d95e6d84edb321c273d5 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jun 2021 09:16:08 -0000 The branch main has been updated by carlavilla: URL: https://cgit.FreeBSD.org/doc/commit/?id=a8c5c8965cd534ff9634d95e6d84edb321c273d5 commit a8c5c8965cd534ff9634d95e6d84edb321c273d5 Author: Sergio Carlavilla Delgado AuthorDate: 2021-06-06 09:15:27 +0000 Commit: Sergio Carlavilla Delgado CommitDate: 2021-06-06 09:15:55 +0000 Use One Sentence Per Line in the Handbook --- .../content/en/books/handbook/_index.adoc | 13 +- .../books/handbook/advanced-networking/_index.adoc | 916 ++++++++++++++------ .../content/en/books/handbook/audit/_index.adoc | 103 ++- .../content/en/books/handbook/basics/_index.adoc | 685 +++++++++++---- .../en/books/handbook/bibliography/_index.adoc | 3 +- documentation/content/en/books/handbook/book.adoc | 13 +- .../content/en/books/handbook/boot/_index.adoc | 151 +++- .../en/books/handbook/bsdinstall/_index.adoc | 459 +++++++--- .../content/en/books/handbook/config/_index.adoc | 851 +++++++++++++----- .../en/books/handbook/cutting-edge/_index.adoc | 15 +- .../content/en/books/handbook/desktop/_index.adoc | 127 ++- .../content/en/books/handbook/disks/_index.adoc | 739 +++++++++++----- .../content/en/books/handbook/dtrace/_index.adoc | 81 +- .../en/books/handbook/eresources/_index.adoc | 260 ++++-- .../en/books/handbook/filesystems/_index.adoc | 30 +- .../en/books/handbook/firewalls/_index.adoc | 950 +++++++++++++++------ .../content/en/books/handbook/geom/_index.adoc | 376 +++++--- .../en/books/handbook/introduction/_index.adoc | 101 ++- .../content/en/books/handbook/jails/_index.adoc | 289 +++++-- .../en/books/handbook/kernelconfig/_index.adoc | 114 ++- .../content/en/books/handbook/l10n/_index.adoc | 124 ++- .../content/en/books/handbook/linuxemu/_index.adoc | 80 +- .../content/en/books/handbook/mac/_index.adoc | 324 +++++-- .../content/en/books/handbook/mail/_index.adoc | 385 ++++++--- .../content/en/books/handbook/mirrors/_index.adoc | 51 +- .../en/books/handbook/multimedia/_index.adoc | 321 +++++-- .../en/books/handbook/network-servers/_index.adoc | 939 ++++++++++++++------ documentation/content/en/books/handbook/parti.adoc | 3 +- .../content/en/books/handbook/partii.adoc | 3 +- .../content/en/books/handbook/partiii.adoc | 7 +- .../content/en/books/handbook/partiv.adoc | 6 +- .../content/en/books/handbook/pgpkeys/_index.adoc | 5 +- .../content/en/books/handbook/ports/_index.adoc | 347 +++++--- .../en/books/handbook/ppp-and-slip/_index.adoc | 246 ++++-- .../content/en/books/handbook/preface/_index.adoc | 48 +- .../content/en/books/handbook/printing/_index.adoc | 252 ++++-- .../content/en/books/handbook/security/_index.adoc | 883 ++++++++++++++----- .../en/books/handbook/serialcomms/_index.adoc | 433 +++++++--- .../en/books/handbook/usb-device-mode/_index.adoc | 91 +- .../en/books/handbook/virtualization/_index.adoc | 342 ++++++-- .../content/en/books/handbook/wine/_index.adoc | 259 ++++-- .../content/en/books/handbook/x11/_index.adoc | 419 ++++++--- .../content/en/books/handbook/zfs/_index.adoc | 762 +++++++++++++---- 43 files changed, 9320 insertions(+), 3286 deletions(-) diff --git a/documentation/content/en/books/handbook/_index.adoc b/documentation/content/en/books/handbook/_index.adoc index 6551efc869..af69a1236e 100644 --- a/documentation/content/en/books/handbook/_index.adoc +++ b/documentation/content/en/books/handbook/_index.adoc @@ -26,9 +26,16 @@ include::shared/en/mailing-lists.adoc[] [.abstract-title] Abstract -Welcome to FreeBSD! This handbook covers the installation and day to day use of _FreeBSD {rel130-current}-RELEASE_, _FreeBSD {rel122-current}-RELEASE_ and _FreeBSD {rel114-current}-RELEASE_. This book is the result of ongoing work by many individuals. Some sections might be outdated. Those interested in helping to update and expand this document should send email to the {freebsd-doc}. - -The latest version of this book is available from the https://www.FreeBSD.org/[FreeBSD web site]. Previous versions can be obtained from https://docs.FreeBSD.org/doc/[https://docs.FreeBSD.org/doc/]. The book can be downloaded in a variety of formats and compression options from the https://download.freebsd.org/ftp/doc/[FreeBSD FTP server] or one of the numerous link:./mirrors#mirrors-ftp[mirror sites]. Printed copies can be purchased at the https://www.freebsdmall.com/[FreeBSD Mall]. Searches can be performed on the handbook and other documents on the link:https://www.FreeBSD.org/search/[search page]. +Welcome to FreeBSD! This handbook covers the installation and day to day use of _FreeBSD {rel130-current}-RELEASE_, _FreeBSD {rel122-current}-RELEASE_ and _FreeBSD {rel114-current}-RELEASE_. +This book is the result of ongoing work by many individuals. +Some sections might be outdated. +Those interested in helping to update and expand this document should send email to the {freebsd-doc}. + +The latest version of this book is available from the https://www.FreeBSD.org/[FreeBSD web site]. +Previous versions can be obtained from https://docs.FreeBSD.org/doc/[https://docs.FreeBSD.org/doc/]. +The book can be downloaded in a variety of formats and compression options from the https://download.freebsd.org/ftp/doc/[FreeBSD FTP server] or one of the numerous link:./mirrors#mirrors-ftp[mirror sites]. +Printed copies can be purchased at the https://www.freebsdmall.com/[FreeBSD Mall]. +Searches can be performed on the handbook and other documents on the link:https://www.FreeBSD.org/search/[search page]. ''' diff --git a/documentation/content/en/books/handbook/advanced-networking/_index.adoc b/documentation/content/en/books/handbook/advanced-networking/_index.adoc index 73e766a724..a64a5e8fa5 100644 --- a/documentation/content/en/books/handbook/advanced-networking/_index.adoc +++ b/documentation/content/en/books/handbook/advanced-networking/_index.adoc @@ -70,9 +70,16 @@ Before reading this chapter, you should: [[network-routing]] == Gateways and Routes -_Routing_ is the mechanism that allows a system to find the network path to another system. A _route_ is a defined pair of addresses which represent the "destination" and a "gateway". The route indicates that when trying to get to the specified destination, send the packets through the specified gateway. There are three types of destinations: individual hosts, subnets, and "default". The "default route" is used if no other routes apply. There are also three types of gateways: individual hosts, interfaces, also called links, and Ethernet hardware (MAC) addresses. Known routes are stored in a routing table. +_Routing_ is the mechanism that allows a system to find the network path to another system. +A _route_ is a defined pair of addresses which represent the "destination" and a "gateway". +The route indicates that when trying to get to the specified destination, send the packets through the specified gateway. +There are three types of destinations: individual hosts, subnets, and "default". +The "default route" is used if no other routes apply. +There are also three types of gateways: individual hosts, interfaces, also called links, and Ethernet hardware (MAC) addresses. +Known routes are stored in a routing table. -This section provides an overview of routing basics. It then demonstrates how to configure a FreeBSD system as a router and offers some troubleshooting tips. +This section provides an overview of routing basics. +It then demonstrates how to configure a FreeBSD system as a router and offers some troubleshooting tips. [[network-routing-default]] === Routing Basics @@ -100,32 +107,49 @@ host2.example.com link#1 UC 0 0 The entries in this example are as follows: default:: -The first route in this table specifies the `default` route. When the local system needs to make a connection to a remote host, it checks the routing table to determine if a known path exists. If the remote host matches an entry in the table, the system checks to see if it can connect using the interface specified in that entry. +The first route in this table specifies the `default` route. +When the local system needs to make a connection to a remote host, it checks the routing table to determine if a known path exists. +If the remote host matches an entry in the table, the system checks to see if it can connect using the interface specified in that entry. + -If the destination does not match an entry, or if all known paths fail, the system uses the entry for the default route. For hosts on a local area network, the `Gateway` field in the default route is set to the system which has a direct connection to the Internet. When reading this entry, verify that the `Flags` column indicates that the gateway is usable (`UG`). +If the destination does not match an entry, or if all known paths fail, the system uses the entry for the default route. +For hosts on a local area network, the `Gateway` field in the default route is set to the system which has a direct connection to the Internet. +When reading this entry, verify that the `Flags` column indicates that the gateway is usable (`UG`). + The default route for a machine which itself is functioning as the gateway to the outside world will be the gateway machine at the Internet Service Provider (ISP). localhost:: -The second route is the `localhost` route. The interface specified in the `Netif` column for `localhost` is [.filename]#lo0#, also known as the loopback device. This indicates that all traffic for this destination should be internal, rather than sending it out over the network. +The second route is the `localhost` route. +The interface specified in the `Netif` column for `localhost` is [.filename]#lo0#, also known as the loopback device. +This indicates that all traffic for this destination should be internal, rather than sending it out over the network. MAC address:: -The addresses beginning with `0:e0:` are MAC addresses. FreeBSD will automatically identify any hosts, `test0` in the example, on the local Ethernet and add a route for that host over the Ethernet interface, [.filename]#re0#. This type of route has a timeout, seen in the `Expire` column, which is used if the host does not respond in a specific amount of time. When this happens, the route to this host will be automatically deleted. These hosts are identified using the Routing Information Protocol (RIP), which calculates routes to local hosts based upon a shortest path determination. +The addresses beginning with `0:e0:` are MAC addresses. +FreeBSD will automatically identify any hosts, `test0` in the example, on the local Ethernet and add a route for that host over the Ethernet interface, [.filename]#re0#. +This type of route has a timeout, seen in the `Expire` column, which is used if the host does not respond in a specific amount of time. +When this happens, the route to this host will be automatically deleted. +These hosts are identified using the Routing Information Protocol (RIP), which calculates routes to local hosts based upon a shortest path determination. subnet:: -FreeBSD will automatically add subnet routes for the local subnet. In this example, `10.20.30.255` is the broadcast address for the subnet `10.20.30` and `example.com` is the domain name associated with that subnet. The designation `link#1` refers to the first Ethernet card in the machine. +FreeBSD will automatically add subnet routes for the local subnet. +In this example, `10.20.30.255` is the broadcast address for the subnet `10.20.30` and `example.com` is the domain name associated with that subnet. +The designation `link#1` refers to the first Ethernet card in the machine. + -Local network hosts and local subnets have their routes automatically configured by a daemon called man:routed[8]. If it is not running, only routes which are statically defined by the administrator will exist. +Local network hosts and local subnets have their routes automatically configured by a daemon called man:routed[8]. +If it is not running, only routes which are statically defined by the administrator will exist. host:: -The `host1` line refers to the host by its Ethernet address. Since it is the sending host, FreeBSD knows to use the loopback interface ([.filename]#lo0#) rather than the Ethernet interface. +The `host1` line refers to the host by its Ethernet address. +Since it is the sending host, FreeBSD knows to use the loopback interface ([.filename]#lo0#) rather than the Ethernet interface. + -The two `host2` lines represent aliases which were created using man:ifconfig[8]. The `=>` symbol after the [.filename]#lo0# interface says that an alias has been set in addition to the loopback address. Such routes only show up on the host that supports the alias and all other hosts on the local network will have a `link#1` line for such routes. +The two `host2` lines represent aliases which were created using man:ifconfig[8]. +The `=>` symbol after the [.filename]#lo0# interface says that an alias has been set in addition to the loopback address. +Such routes only show up on the host that supports the alias and all other hosts on the local network will have a `link#1` line for such routes. 224:: The final line (destination subnet `224`) deals with multicasting. -Various attributes of each route can be seen in the `Flags` column. <> summarizes some of these flags and their meanings: +Various attributes of each route can be seen in the `Flags` column. +<> summarizes some of these flags and their meanings: [[routeflags]] .Commonly Seen Routing Table Flags @@ -170,34 +194,45 @@ It is also possible to manually add the route using `route`: # route add default 10.20.30.1 .... -Note that manually added routes will not survive a reboot. For more information on manual manipulation of network routing tables, refer to man:route[8]. +Note that manually added routes will not survive a reboot. +For more information on manual manipulation of network routing tables, refer to man:route[8]. [[network-static-routes]] === Configuring a Router with Static Routes -A FreeBSD system can be configured as the default gateway, or router, for a network if it is a dual-homed system. A dual-homed system is a host which resides on at least two different networks. Typically, each network is connected to a separate network interface, though IP aliasing can be used to bind multiple addresses, each on a different subnet, to one physical interface. +A FreeBSD system can be configured as the default gateway, or router, for a network if it is a dual-homed system. +A dual-homed system is a host which resides on at least two different networks. +Typically, each network is connected to a separate network interface, though IP aliasing can be used to bind multiple addresses, each on a different subnet, to one physical interface. -In order for the system to forward packets between interfaces, FreeBSD must be configured as a router. Internet standards and good engineering practice prevent the FreeBSD Project from enabling this feature by default, but it can be configured to start at boot by adding this line to [.filename]#/etc/rc.conf#: +In order for the system to forward packets between interfaces, FreeBSD must be configured as a router. +Internet standards and good engineering practice prevent the FreeBSD Project from enabling this feature by default, but it can be configured to start at boot by adding this line to [.filename]#/etc/rc.conf#: [.programlisting] .... gateway_enable="YES" # Set to YES if this host will be a gateway .... -To enable routing now, set the man:sysctl[8] variable `net.inet.ip.forwarding` to `1`. To stop routing, reset this variable to `0`. +To enable routing now, set the man:sysctl[8] variable `net.inet.ip.forwarding` to `1`. +To stop routing, reset this variable to `0`. -The routing table of a router needs additional routes so it knows how to reach other networks. Routes can be either added manually using static routes or routes can be automatically learned using a routing protocol. Static routes are appropriate for small networks and this section describes how to add a static routing entry for a small network. +The routing table of a router needs additional routes so it knows how to reach other networks. +Routes can be either added manually using static routes or routes can be automatically learned using a routing protocol. +Static routes are appropriate for small networks and this section describes how to add a static routing entry for a small network. [NOTE] ==== -For large networks, static routes quickly become unscalable. FreeBSD comes with the standard BSD routing daemon man:routed[8], which provides the routing protocols RIP, versions 1 and 2, and IRDP. Support for the BGP and OSPF routing protocols can be installed using the package:net/zebra[] package or port. +For large networks, static routes quickly become unscalable. +FreeBSD comes with the standard BSD routing daemon man:routed[8], which provides the routing protocols RIP, versions 1 and 2, and IRDP. +Support for the BGP and OSPF routing protocols can be installed using the package:net/zebra[] package or port. ==== Consider the following network: image::static-routes.png[] -In this scenario, `RouterA` is a FreeBSD machine that is acting as a router to the rest of the Internet. It has a default route set to `10.0.0.1` which allows it to connect with the outside world. `RouterB` is already configured to use `192.168.1.1` as its default gateway. +In this scenario, `RouterA` is a FreeBSD machine that is acting as a router to the rest of the Internet. +It has a default route set to `10.0.0.1` which allows it to connect with the outside world. +`RouterB` is already configured to use `192.168.1.1` as its default gateway. Before adding any static routes, the routing table on `RouterA` looks like this: @@ -214,14 +249,17 @@ default 10.0.0.1 UGS 0 49378 xl0 192.168.1.0/24 link#2 UC 0 0 xl1 .... -With the current routing table, `RouterA` does not have a route to the `192.168.2.0/24` network. The following command adds the `Internal Net 2` network to ``RouterA``'s routing table using `192.168.1.2` as the next hop: +With the current routing table, `RouterA` does not have a route to the `192.168.2.0/24` network. +The following command adds the `Internal Net 2` network to ``RouterA``'s routing table using `192.168.1.2` as the next hop: [source,shell] .... # route add -net 192.168.2.0/24 192.168.1.2 .... -Now, `RouterA` can reach any host on the `192.168.2.0/24` network. However, the routing information will not persist if the FreeBSD system reboots. If a static route needs to be persistent, add it to [.filename]#/etc/rc.conf#: +Now, `RouterA` can reach any host on the `192.168.2.0/24` network. +However, the routing information will not persist if the FreeBSD system reboots. +If a static route needs to be persistent, add it to [.filename]#/etc/rc.conf#: [.programlisting] .... @@ -230,9 +268,11 @@ static_routes="internalnet2" route_internalnet2="-net 192.168.2.0/24 192.168.1.2" .... -The `static_routes` configuration variable is a list of strings separated by a space, where each string references a route name. The variable `route_internalnet2` contains the static route for that route name. +The `static_routes` configuration variable is a list of strings separated by a space, where each string references a route name. +The variable `route_internalnet2` contains the static route for that route name. -Using more than one string in `static_routes` creates multiple static routes. The following shows an example of adding static routes for the `192.168.0.0/24` and `192.168.1.0/24` networks: +Using more than one string in `static_routes` creates multiple static routes. +The following shows an example of adding static routes for the `192.168.0.0/24` and `192.168.1.0/24` networks: [.programlisting] .... @@ -244,31 +284,44 @@ route_net2="-net 192.168.1.0/24 192.168.1.1" [[network-routing-troubleshooting]] === Troubleshooting -When an address space is assigned to a network, the service provider configures their routing tables so that all traffic for the network will be sent to the link for the site. But how do external sites know to send their packets to the network's ISP? +When an address space is assigned to a network, the service provider configures their routing tables so that all traffic for the network will be sent to the link for the site. +But how do external sites know to send their packets to the network's ISP? -There is a system that keeps track of all assigned address spaces and defines their point of connection to the Internet backbone, or the main trunk lines that carry Internet traffic across the country and around the world. Each backbone machine has a copy of a master set of tables, which direct traffic for a particular network to a specific backbone carrier, and from there down the chain of service providers until it reaches a particular network. +There is a system that keeps track of all assigned address spaces and defines their point of connection to the Internet backbone, or the main trunk lines that carry Internet traffic across the country and around the world. +Each backbone machine has a copy of a master set of tables, which direct traffic for a particular network to a specific backbone carrier, and from there down the chain of service providers until it reaches a particular network. -It is the task of the service provider to advertise to the backbone sites that they are the point of connection, and thus the path inward, for a site. This is known as route propagation. +It is the task of the service provider to advertise to the backbone sites that they are the point of connection, and thus the path inward, for a site. +This is known as route propagation. -Sometimes, there is a problem with route propagation and some sites are unable to connect. Perhaps the most useful command for trying to figure out where routing is breaking down is `traceroute`. It is useful when `ping` fails. +Sometimes, there is a problem with route propagation and some sites are unable to connect. +Perhaps the most useful command for trying to figure out where routing is breaking down is `traceroute`. +It is useful when `ping` fails. -When using `traceroute`, include the address of the remote host to connect to. The output will show the gateway hosts along the path of the attempt, eventually either reaching the target host, or terminating because of a lack of connection. For more information, refer to man:traceroute[8]. +When using `traceroute`, include the address of the remote host to connect to. +The output will show the gateway hosts along the path of the attempt, eventually either reaching the target host, or terminating because of a lack of connection. +For more information, refer to man:traceroute[8]. [[network-routing-multicast]] === Multicast Considerations -FreeBSD natively supports both multicast applications and multicast routing. Multicast applications do not require any special configuration in order to run on FreeBSD. Support for multicast routing requires that the following option be compiled into a custom kernel: +FreeBSD natively supports both multicast applications and multicast routing. +Multicast applications do not require any special configuration in order to run on FreeBSD. +Support for multicast routing requires that the following option be compiled into a custom kernel: [.programlisting] .... options MROUTING .... -The multicast routing daemon, mrouted can be installed using the package:net/mrouted[] package or port. This daemon implements the DVMRP multicast routing protocol and is configured by editing [.filename]#/usr/local/etc/mrouted.conf# in order to set up the tunnels and DVMRP. The installation of mrouted also installs map-mbone and mrinfo, as well as their associated man pages. Refer to these for configuration examples. +The multicast routing daemon, mrouted can be installed using the package:net/mrouted[] package or port. +This daemon implements the DVMRP multicast routing protocol and is configured by editing [.filename]#/usr/local/etc/mrouted.conf# in order to set up the tunnels and DVMRP. +The installation of mrouted also installs map-mbone and mrinfo, as well as their associated man pages. +Refer to these for configuration examples. [NOTE] ==== -DVMRP has largely been replaced by the PIM protocol in many multicast installations. Refer to man:pim[4] for more information. +DVMRP has largely been replaced by the PIM protocol in many multicast installations. +Refer to man:pim[4] for more information. ==== [[network-wireless]] @@ -276,22 +329,46 @@ DVMRP has largely been replaced by the PIM protocol in many multicast installati === Wireless Networking Basics -Most wireless networks are based on the IEEE(R) 802.11 standards. A basic wireless network consists of multiple stations communicating with radios that broadcast in either the 2.4GHz or 5GHz band, though this varies according to the locale and is also changing to enable communication in the 2.3GHz and 4.9GHz ranges. - -802.11 networks are organized in two ways. In _infrastructure mode_, one station acts as a master with all the other stations associating to it, the network is known as a BSS, and the master station is termed an access point (AP). In a BSS, all communication passes through the AP; even when one station wants to communicate with another wireless station, messages must go through the AP. In the second form of network, there is no master and stations communicate directly. This form of network is termed an IBSS and is commonly known as an _ad-hoc network_. - -802.11 networks were first deployed in the 2.4GHz band using protocols defined by the IEEE(R) 802.11 and 802.11b standard. These specifications include the operating frequencies and the MAC layer characteristics, including framing and transmission rates, as communication can occur at various rates. Later, the 802.11a standard defined operation in the 5GHz band, including different signaling mechanisms and higher transmission rates. Still later, the 802.11g standard defined the use of 802.11a signaling and transmission mechanisms in the 2.4GHz band in such a way as to be backwards compatible with 802.11b networks. - -Separate from the underlying transmission techniques, 802.11 networks have a variety of security mechanisms. The original 802.11 specifications defined a simple security protocol called WEP. This protocol uses a fixed pre-shared key and the RC4 cryptographic cipher to encode data transmitted on a network. Stations must all agree on the fixed key in order to communicate. This scheme was shown to be easily broken and is now rarely used except to discourage transient users from joining networks. Current security practice is given by the IEEE(R) 802.11i specification that defines new cryptographic ciphers and an additional protocol to authenticate stations to an access point and exchange keys for data communication. Cryptographic keys are periodically refreshed and there are mechanisms for detecting and countering intrusion attempts. Another security protocol specification commonly used in wireless networks is termed WPA, which was a precursor to 802.11i. WPA specifies a subset of the r equirements found in 802.11i and is designed for implementation on legacy hardware. Specifically, WPA requires only the TKIP cipher that is derived from the original WEP cipher. 802.11i permits use of TKIP but also requires support for a stronger cipher, AES-CCM, for encrypting data. The AES cipher was not required in WPA because it was deemed too computationally costly to be implemented on legacy hardware. - -The other standard to be aware of is 802.11e. It defines protocols for deploying multimedia applications, such as streaming video and voice over IP (VoIP), in an 802.11 network. Like 802.11i, 802.11e also has a precursor specification termed WME (later renamed WMM) that has been defined by an industry group as a subset of 802.11e that can be deployed now to enable multimedia applications while waiting for the final ratification of 802.11e. The most important thing to know about 802.11e and WME/WMM is that it enables prioritized traffic over a wireless network through Quality of Service (QoS) protocols and enhanced media access protocols. Proper implementation of these protocols enables high speed bursting of data and prioritized traffic flow. - -FreeBSD supports networks that operate using 802.11a, 802.11b, and 802.11g. The WPA and 802.11i security protocols are likewise supported (in conjunction with any of 11a, 11b, and 11g) and QoS and traffic prioritization required by the WME/WMM protocols are supported for a limited set of wireless devices. +Most wireless networks are based on the IEEE(R) 802.11 standards. +A basic wireless network consists of multiple stations communicating with radios that broadcast in either the 2.4GHz or 5GHz band, though this varies according to the locale and is also changing to enable communication in the 2.3GHz and 4.9GHz ranges. + +802.11 networks are organized in two ways. +In _infrastructure mode_, one station acts as a master with all the other stations associating to it, the network is known as a BSS, and the master station is termed an access point (AP). +In a BSS, all communication passes through the AP; even when one station wants to communicate with another wireless station, messages must go through the AP. +In the second form of network, there is no master and stations communicate directly. +This form of network is termed an IBSS and is commonly known as an _ad-hoc network_. + +802.11 networks were first deployed in the 2.4GHz band using protocols defined by the IEEE(R) 802.11 and 802.11b standard. +These specifications include the operating frequencies and the MAC layer characteristics, including framing and transmission rates, as communication can occur at various rates. +Later, the 802.11a standard defined operation in the 5GHz band, including different signaling mechanisms and higher transmission rates. +Still later, the 802.11g standard defined the use of 802.11a signaling and transmission mechanisms in the 2.4GHz band in such a way as to be backwards compatible with 802.11b networks. + +Separate from the underlying transmission techniques, 802.11 networks have a variety of security mechanisms. +The original 802.11 specifications defined a simple security protocol called WEP. +This protocol uses a fixed pre-shared key and the RC4 cryptographic cipher to encode data transmitted on a network. +Stations must all agree on the fixed key in order to communicate. +This scheme was shown to be easily broken and is now rarely used except to discourage transient users from joining networks. +Current security practice is given by the IEEE(R) 802.11i specification that defines new cryptographic ciphers and an additional protocol to authenticate stations to an access point and exchange keys for data communication. +Cryptographic keys are periodically refreshed and there are mechanisms for detecting and countering intrusion attempts. +Another security protocol specification commonly used in wireless networks is termed WPA, which was a precursor to 802.11i. +WPA specifies a subset of the requirements found in 802.11i and is designed for implementation on legacy hardware. +Specifically, WPA requires only the TKIP cipher that is derived from the original WEP cipher. +802.11i permits use of TKIP but also requires support for a stronger cipher, AES-CCM, for encrypting data. +The AES cipher was not required in WPA because it was deemed too computationally costly to be implemented on legacy hardware. + +The other standard to be aware of is 802.11e. It defines protocols for deploying multimedia applications, such as streaming video and voice over IP (VoIP), in an 802.11 network. +Like 802.11i, 802.11e also has a precursor specification termed WME (later renamed WMM) that has been defined by an industry group as a subset of 802.11e that can be deployed now to enable multimedia applications while waiting for the final ratification of 802.11e. +The most important thing to know about 802.11e and WME/WMM is that it enables prioritized traffic over a wireless network through Quality of Service (QoS) protocols and enhanced media access protocols. +Proper implementation of these protocols enables high speed bursting of data and prioritized traffic flow. + +FreeBSD supports networks that operate using 802.11a, 802.11b, and 802.11g. +The WPA and 802.11i security protocols are likewise supported (in conjunction with any of 11a, 11b, and 11g) and QoS and traffic prioritization required by the WME/WMM protocols are supported for a limited set of wireless devices. [[network-wireless-quick-start]] === Quick Start -Connecting a computer to an existing wireless network is a very common situation. This procedure shows the steps required. +Connecting a computer to an existing wireless network is a very common situation. +This procedure shows the steps required. [.procedure] . Obtain the SSID (Service Set Identifier) and PSK (Pre-Shared Key) for the wireless network from the network administrator. @@ -342,16 +419,21 @@ ifconfig_wlan0="WPA SYNCDHCP" ==== Kernel Configuration -To use wireless networking, a wireless networking card is needed and the kernel needs to be configured with the appropriate wireless networking support. The kernel is separated into multiple modules so that only the required support needs to be configured. +To use wireless networking, a wireless networking card is needed and the kernel needs to be configured with the appropriate wireless networking support. +The kernel is separated into multiple modules so that only the required support needs to be configured. -The most commonly used wireless devices are those that use parts made by Atheros. These devices are supported by man:ath[4] and require the following line to be added to [.filename]#/boot/loader.conf#: +The most commonly used wireless devices are those that use parts made by Atheros. +These devices are supported by man:ath[4] and require the following line to be added to [.filename]#/boot/loader.conf#: [.programlisting] .... if_ath_load="YES" .... -The Atheros driver is split up into three separate pieces: the driver (man:ath[4]), the hardware support layer that handles chip-specific functions (man:ath_hal[4]), and an algorithm for selecting the rate for transmitting frames. When this support is loaded as kernel modules, any dependencies are automatically handled. To load support for a different type of wireless device, specify the module for that device. This example is for devices based on the Intersil Prism parts (man:wi[4]) driver: +The Atheros driver is split up into three separate pieces: the driver (man:ath[4]), the hardware support layer that handles chip-specific functions (man:ath_hal[4]), and an algorithm for selecting the rate for transmitting frames. +When this support is loaded as kernel modules, any dependencies are automatically handled. +To load support for a different type of wireless device, specify the module for that device. +This example is for devices based on the Intersil Prism parts (man:wi[4]) driver: [.programlisting] .... @@ -360,10 +442,17 @@ if_wi_load="YES" [NOTE] ==== -The examples in this section use an man:ath[4] device and the device name in the examples must be changed according to the configuration. A list of available wireless drivers and supported adapters can be found in the FreeBSD Hardware Notes, available on the https://www.FreeBSD.org/releases/[Release Information] page of the FreeBSD website. If a native FreeBSD driver for the wireless device does not exist, it may be possible to use the Windows(R) driver with the help of the crossref:config[config-network-ndis,NDIS] driver wrapper. +The examples in this section use an man:ath[4] device and the device name in the examples must be changed according to the configuration. +A list of available wireless drivers and supported adapters can be found in the FreeBSD Hardware Notes, available on the https://www.FreeBSD.org/releases/[Release Information] page of the FreeBSD website. +If a native FreeBSD driver for the wireless device does not exist, it may be possible to use the Windows(R) driver with the help of the crossref:config[config-network-ndis,NDIS] driver wrapper. ==== -In addition, the modules that implement cryptographic support for the security protocols to use must be loaded. These are intended to be dynamically loaded on demand by the man:wlan[4] module, but for now they must be manually configured. The following modules are available: man:wlan_wep[4], man:wlan_ccmp[4], and man:wlan_tkip[4]. The man:wlan_ccmp[4] and man:wlan_tkip[4] drivers are only needed when using the WPA or 802.11i security protocols. If the network does not use encryption, man:wlan_wep[4] support is not needed. To load these modules at boot time, add the following lines to [.filename]#/boot/loader.conf#: +In addition, the modules that implement cryptographic support for the security protocols to use must be loaded. +These are intended to be dynamically loaded on demand by the man:wlan[4] module, but for now they must be manually configured. +The following modules are available: man:wlan_wep[4], man:wlan_ccmp[4], and man:wlan_tkip[4]. +The man:wlan_ccmp[4] and man:wlan_tkip[4] drivers are only needed when using the WPA or 802.11i security protocols. +If the network does not use encryption, man:wlan_wep[4] support is not needed. +To load these modules at boot time, add the following lines to [.filename]#/boot/loader.conf#: [.programlisting] .... @@ -372,7 +461,8 @@ wlan_ccmp_load="YES" wlan_tkip_load="YES" .... -Once this information has been added to [.filename]#/boot/loader.conf#, reboot the FreeBSD box. Alternately, load the modules by hand using man:kldload[8]. +Once this information has been added to [.filename]#/boot/loader.conf#, reboot the FreeBSD box. +Alternately, load the modules by hand using man:kldload[8]. [NOTE] ==== @@ -407,7 +497,8 @@ ath0: AR2413 mac 7.9 RF2413 phy 4.5 Since the regulatory situation is different in various parts of the world, it is necessary to correctly set the domains that apply to your location to have the correct information about what channels can be used. -The available region definitions can be found in [.filename]#/etc/regdomain.xml#. To set the data at runtime, use `ifconfig`: +The available region definitions can be found in [.filename]#/etc/regdomain.xml#. +To set the data at runtime, use `ifconfig`: [source,shell] .... @@ -423,13 +514,18 @@ To persist the settings, add it to [.filename]#/etc/rc.conf#: === Infrastructure Mode -Infrastructure (BSS) mode is the mode that is typically used. In this mode, a number of wireless access points are connected to a wired network. Each wireless network has its own name, called the SSID. Wireless clients connect to the wireless access points. +Infrastructure (BSS) mode is the mode that is typically used. +In this mode, a number of wireless access points are connected to a wired network. +Each wireless network has its own name, called the SSID. +Wireless clients connect to the wireless access points. ==== FreeBSD Clients ===== How to Find Access Points -To scan for available networks, use man:ifconfig[8]. This request may take a few moments to complete as it requires the system to switch to each available wireless frequency and probe for available access points. Only the superuser can initiate a scan: +To scan for available networks, use man:ifconfig[8]. +This request may take a few moments to complete as it requires the system to switch to each available wireless frequency and probe for available access points. +Only the superuser can initiate a scan: [source,shell] .... @@ -442,10 +538,13 @@ freebsdap 00:11:95:c3:0d:ac 1 54M -83:96 100 EPS WPA [NOTE] ==== -The interface must be `up` before it can scan. Subsequent scan requests do not require the interface to be marked as up again. +The interface must be `up` before it can scan. +Subsequent scan requests do not require the interface to be marked as up again. ==== -The output of a scan request lists each BSS/IBSS network found. Besides listing the name of the network, the `SSID`, the output also shows the `BSSID`, which is the MAC address of the access point. The `CAPS` field identifies the type of each network and the capabilities of the stations operating there: +The output of a scan request lists each BSS/IBSS network found. +Besides listing the name of the network, the `SSID`, the output also shows the `BSSID`, which is the MAC address of the access point. +The `CAPS` field identifies the type of each network and the capabilities of the stations operating there: .Station Capability Codes [cols="1,1", frame="none", options="header"] @@ -476,17 +575,21 @@ One can also display the current list of known networks with: # ifconfig wlan0 list scan .... -This information may be updated automatically by the adapter or manually with a `scan` request. Old data is automatically removed from the cache, so over time this list may shrink unless more scans are done. +This information may be updated automatically by the adapter or manually with a `scan` request. +Old data is automatically removed from the cache, so over time this list may shrink unless more scans are done. ===== Basic Settings -This section provides a simple example of how to make the wireless network adapter work in FreeBSD without encryption. Once familiar with these concepts, it is strongly recommend to use <> to set up the wireless network. +This section provides a simple example of how to make the wireless network adapter work in FreeBSD without encryption. +Once familiar with these concepts, it is strongly recommend to use <> to set up the wireless network. -There are three basic steps to configure a wireless network: select an access point, authenticate the station, and configure an IP address. The following sections discuss each step. +There are three basic steps to configure a wireless network: select an access point, authenticate the station, and configure an IP address. +The following sections discuss each step. ====== Selecting an Access Point -Most of the time, it is sufficient to let the system choose an access point using the builtin heuristics. This is the default behavior when an interface is marked as up or it is listed in [.filename]#/etc/rc.conf#: +Most of the time, it is sufficient to let the system choose an access point using the builtin heuristics. +This is the default behavior when an interface is marked as up or it is listed in [.filename]#/etc/rc.conf#: [.programlisting] .... @@ -502,7 +605,8 @@ wlans_ath0="wlan0" ifconfig_wlan0="ssid your_ssid_here DHCP" .... -In an environment where there are multiple access points with the same SSID, which is often done to simplify roaming, it may be necessary to associate to one specific device. In this case, the BSSID of the access point can be specified, with or without the SSID: +In an environment where there are multiple access points with the same SSID, which is often done to simplify roaming, it may be necessary to associate to one specific device. +In this case, the BSSID of the access point can be specified, with or without the SSID: [.programlisting] .... @@ -510,7 +614,9 @@ wlans_ath0="wlan0" ifconfig_wlan0="ssid your_ssid_here bssid xx:xx:xx:xx:xx:xx DHCP" .... -There are other ways to constrain the choice of an access point, such as limiting the set of frequencies the system will scan on. This may be useful for a multi-band wireless card as scanning all the possible channels can be time-consuming. To limit operation to a specific band, use the `mode` parameter: +There are other ways to constrain the choice of an access point, such as limiting the set of frequencies the system will scan on. +This may be useful for a multi-band wireless card as scanning all the possible channels can be time-consuming. +To limit operation to a specific band, use the `mode` parameter: [.programlisting] .... @@ -518,15 +624,25 @@ wlans_ath0="wlan0" ifconfig_wlan0="mode 11g ssid your_ssid_here DHCP" .... -This example will force the card to operate in 802.11g, which is defined only for 2.4GHz frequencies so any 5GHz channels will not be considered. This can also be achieved with the `channel` parameter, which locks operation to one specific frequency, and the `chanlist` parameter, to specify a list of channels for scanning. More information about these parameters can be found in man:ifconfig[8]. +This example will force the card to operate in 802.11g, which is defined only for 2.4GHz frequencies so any 5GHz channels will not be considered. +This can also be achieved with the `channel` parameter, which locks operation to one specific frequency, and the `chanlist` parameter, to specify a list of channels for scanning. +More information about these parameters can be found in man:ifconfig[8]. ====== Authentication -Once an access point is selected, the station needs to authenticate before it can pass data. Authentication can happen in several ways. The most common scheme, open authentication, allows any station to join the network and communicate. This is the authentication to use for test purposes the first time a wireless network is setup. Other schemes require cryptographic handshakes to be completed before data traffic can flow, either using pre-shared keys or secrets, or more complex schemes that involve backend services such as RADIUS. Open authentication is the default setting. The next most common setup is WPA-PSK, also known as WPA Personal, which is described in <>. +Once an access point is selected, the station needs to authenticate before it can pass data. +Authentication can happen in several ways. +The most common scheme, open authentication, allows any station to join the network and communicate. +This is the authentication to use for test purposes the first time a wireless network is setup. +Other schemes require cryptographic handshakes to be completed before data traffic can flow, either using pre-shared keys or secrets, or more complex schemes that involve backend services such as RADIUS. +Open authentication is the default setting. +The next most common setup is WPA-PSK, also known as WPA Personal, which is described in <>. [NOTE] ==== -If using an Apple(R) AirPort(R) Extreme base station for an access point, shared-key authentication together with a WEP key needs to be configured. This can be configured in [.filename]#/etc/rc.conf# or by using man:wpa_supplicant[8]. For a single AirPort(R) base station, access can be configured with: +If using an Apple(R) AirPort(R) Extreme base station for an access point, shared-key authentication together with a WEP key needs to be configured. +This can be configured in [.filename]#/etc/rc.conf# or by using man:wpa_supplicant[8]. +For a single AirPort(R) base station, access can be configured with: [.programlisting] .... @@ -534,12 +650,16 @@ wlans_ath0="wlan0" ifconfig_wlan0="authmode shared wepmode on weptxkey 1 wepkey 01234567 DHCP" .... -In general, shared key authentication should be avoided because it uses the WEP key material in a highly-constrained manner, making it even easier to crack the key. If WEP must be used for compatibility with legacy devices, it is better to use WEP with `open` authentication. More information regarding WEP can be found in <>. +In general, shared key authentication should be avoided because it uses the WEP key material in a highly-constrained manner, making it even easier to crack the key. +If WEP must be used for compatibility with legacy devices, it is better to use WEP with `open` authentication. +More information regarding WEP can be found in <>. ==== ====== Getting an IP Address with DHCP -Once an access point is selected and the authentication parameters are set, an IP address must be obtained in order to communicate. Most of the time, the IP address is obtained via DHCP. To achieve that, edit [.filename]#/etc/rc.conf# and add `DHCP` to the configuration for the device: +Once an access point is selected and the authentication parameters are set, an IP address must be obtained in order to communicate. +Most of the time, the IP address is obtained via DHCP. +To achieve that, edit [.filename]#/etc/rc.conf# and add `DHCP` to the configuration for the device: [.programlisting] .... @@ -570,11 +690,14 @@ wlan0: flags=8843 mtu 1500 roam:rate 5 protmode CTS wme burst .... -The `status: associated` line means that it is connected to the wireless network. The `bssid 00:13:46:49:41:76` is the MAC address of the access point and `authmode OPEN` indicates that the communication is not encrypted. +The `status: associated` line means that it is connected to the wireless network. +The `bssid 00:13:46:49:41:76` is the MAC address of the access point and `authmode OPEN` indicates that the communication is not encrypted. ====== Static IP Address -If an IP address cannot be obtained from a DHCP server, set a fixed IP address. Replace the `DHCP` keyword shown above with the address information. Be sure to retain any other parameters for selecting the access point: +If an IP address cannot be obtained from a DHCP server, set a fixed IP address. +Replace the `DHCP` keyword shown above with the address information. +Be sure to retain any other parameters for selecting the access point: [.programlisting] .... @@ -585,20 +708,33 @@ ifconfig_wlan0="inet 192.168.1.100 netmask 255.255.255.0 ssid your_ssid_here" [[network-wireless-wpa]] ===== WPA -Wi-Fi Protected Access (WPA) is a security protocol used together with 802.11 networks to address the lack of proper authentication and the weakness of WEP. WPA leverages the 802.1X authentication protocol and uses one of several ciphers instead of WEP for data integrity. The only cipher required by WPA is the Temporary Key Integrity Protocol (TKIP). TKIP is a cipher that extends the basic RC4 cipher used by WEP by adding integrity checking, tamper detection, and measures for responding to detected intrusions. TKIP is designed to work on legacy hardware with only software modification. It represents a compromise that improves security but is still not entirely immune to attack. WPA also specifies the AES-CCMP cipher as an alternative to TKIP, and that is preferred when possible. For this specification, the term WPA2 or RSN is commonly used. +Wi-Fi Protected Access (WPA) is a security protocol used together with 802.11 networks to address the lack of proper authentication and the weakness of WEP. +WPA leverages the 802.1X authentication protocol and uses one of several ciphers instead of WEP for data integrity. +The only cipher required by WPA is the Temporary Key Integrity Protocol (TKIP). +TKIP is a cipher that extends the basic RC4 cipher used by WEP by adding integrity checking, tamper detection, and measures for responding to detected intrusions. +TKIP is designed to work on legacy hardware with only software modification. +It represents a compromise that improves security but is still not entirely immune to attack. +WPA also specifies the AES-CCMP cipher as an alternative to TKIP, and that is preferred when possible. +For this specification, the term WPA2 or RSN is commonly used. -WPA defines authentication and encryption protocols. Authentication is most commonly done using one of two techniques: by 802.1X and a backend authentication service such as RADIUS, or by a minimal handshake between the station and the access point using a pre-shared secret. The former is commonly termed WPA Enterprise and the latter is known as WPA Personal. Since most people will not set up a RADIUS backend server for their wireless network, WPA-PSK is by far the most commonly encountered configuration for WPA. +WPA defines authentication and encryption protocols. +Authentication is most commonly done using one of two techniques: by 802.1X and a backend authentication service such as RADIUS, or by a minimal handshake between the station and the access point using a pre-shared secret. +The former is commonly termed WPA Enterprise and the latter is known as WPA Personal. +Since most people will not set up a RADIUS backend server for their wireless network, WPA-PSK is by far the most commonly encountered configuration for WPA. -The control of the wireless connection and the key negotiation or authentication with a server is done using man:wpa_supplicant[8]. This program requires a configuration file, [.filename]#/etc/wpa_supplicant.conf#, to run. More information regarding this file can be found in man:wpa_supplicant.conf[5]. +The control of the wireless connection and the key negotiation or authentication with a server is done using man:wpa_supplicant[8]. +This program requires a configuration file, [.filename]#/etc/wpa_supplicant.conf#, to run. +More information regarding this file can be found in man:wpa_supplicant.conf[5]. [[network-wireless-wpa-wpa-psk]] ====== WPA-PSK -WPA-PSK, also known as WPA Personal, is based on a pre-shared key (PSK) which is generated from a given password and used as the master key in the wireless network. This means every wireless user will share the same key. WPA-PSK is intended for small networks where the use of an authentication server is not possible or desired. +WPA-PSK, also known as WPA Personal, is based on a pre-shared key (PSK) which is generated from a given password and used as the master key in the wireless network. +This means every wireless user will share the same key. +WPA-PSK is intended for small networks where the use of an authentication server is not possible or desired. [WARNING] ==== - Always use strong passwords that are sufficiently long and made from a rich alphabet so that they will not be easily guessed or attacked. ==== @@ -710,11 +846,17 @@ When DHCP is not used, the default gateway and the nameserver also have to be ma [[network-wireless-wpa-eap-tls]] ====== WPA with EAP-TLS -The second way to use WPA is with an 802.1X backend authentication server. In this case, WPA is called WPA Enterprise to differentiate it from the less secure WPA Personal. Authentication in WPA Enterprise is based on the Extensible Authentication Protocol (EAP). +The second way to use WPA is with an 802.1X backend authentication server. +In this case, WPA is called WPA Enterprise to differentiate it from the less secure WPA Personal. +Authentication in WPA Enterprise is based on the Extensible Authentication Protocol (EAP). -EAP does not come with an encryption method. Instead, EAP is embedded inside an encrypted tunnel. There are many EAP authentication methods, but EAP-TLS, EAP-TTLS, and EAP-PEAP are the most common. +EAP does not come with an encryption method. +Instead, EAP is embedded inside an encrypted tunnel. +There are many EAP authentication methods, but EAP-TLS, EAP-TTLS, and EAP-PEAP are the most common. -EAP with Transport Layer Security (EAP-TLS) is a well-supported wireless authentication protocol since it was the first EAP method to be certified by the http://www.wi-fi.org/[Wi-Fi Alliance]. EAP-TLS requires three certificates to run: the certificate of the Certificate Authority (CA) installed on all machines, the server certificate for the authentication server, and one client certificate for each wireless client. In this EAP method, both the authentication server and wireless client authenticate each other by presenting their respective certificates, and then verify that these certificates were signed by the organization's CA. +EAP with Transport Layer Security (EAP-TLS) is a well-supported wireless authentication protocol since it was the first EAP method to be certified by the http://www.wi-fi.org/[Wi-Fi Alliance]. +EAP-TLS requires three certificates to run: the certificate of the Certificate Authority (CA) installed on all machines, the server certificate for the authentication server, and one client certificate for each wireless client. +In this EAP method, both the authentication server and wireless client authenticate each other by presenting their respective certificates, and then verify that these certificates were signed by the organization's CA. As previously, the configuration is done via [.filename]#/etc/wpa_supplicant.conf#: @@ -778,7 +920,10 @@ It is also possible to bring up the interface manually using man:wpa_supplicant[ [[network-wireless-wpa-eap-ttls]] ====== WPA with EAP-TTLS -With EAP-TLS, both the authentication server and the client need a certificate. With EAP-TTLS, a client certificate is optional. This method is similar to a web server which creates a secure SSL tunnel even if visitors do not have client-side certificates. EAP-TTLS uses an encrypted TLS tunnel for safe transport of the authentication data. +With EAP-TLS, both the authentication server and the client need a certificate. +With EAP-TTLS, a client certificate is optional. +This method is similar to a web server which creates a secure SSL tunnel even if visitors do not have client-side certificates. +EAP-TTLS uses an encrypted TLS tunnel for safe transport of the authentication data. The required configuration can be added to [.filename]#/etc/wpa_supplicant.conf#: @@ -838,12 +983,16 @@ wlan0: flags=8843 mtu 1500 [NOTE] ==== -PEAPv0/EAP-MSCHAPv2 is the most common PEAP method. In this chapter, the term PEAP is used to refer to that method. +PEAPv0/EAP-MSCHAPv2 is the most common PEAP method. +In this chapter, the term PEAP is used to refer to that method. ==== -Protected EAP (PEAP) is designed as an alternative to EAP-TTLS and is the most used EAP standard after EAP-TLS. In a network with mixed operating systems, PEAP should be the most supported standard after EAP-TLS. +Protected EAP (PEAP) is designed as an alternative to EAP-TTLS and is the most used EAP standard after EAP-TLS. +In a network with mixed operating systems, PEAP should be the most supported standard after EAP-TLS. -PEAP is similar to EAP-TTLS as it uses a server-side certificate to authenticate clients by creating an encrypted TLS tunnel between the client and the authentication server, which protects the ensuing exchange of authentication information. PEAP authentication differs from EAP-TTLS as it broadcasts the username in the clear and only the password is sent in the encrypted TLS tunnel. EAP-TTLS will use the TLS tunnel for both the username and password. +PEAP is similar to EAP-TTLS as it uses a server-side certificate to authenticate clients by creating an encrypted TLS tunnel between the client and the authentication server, which protects the ensuing exchange of authentication information. +PEAP authentication differs from EAP-TTLS as it broadcasts the username in the clear and only the password is sent in the encrypted TLS tunnel. +EAP-TTLS will use the TLS tunnel for both the username and password. Add the following lines to [.filename]#/etc/wpa_supplicant.conf# to configure the EAP-PEAP related settings: @@ -903,7 +1052,8 @@ wlan0: flags=8843 mtu 1500 [[network-wireless-wep]] ===== WEP -Wired Equivalent Privacy (WEP) is part of the original 802.11 standard. There is no authentication mechanism, only a weak form of access control which is easily cracked. +Wired Equivalent Privacy (WEP) is part of the original 802.11 standard. +There is no authentication mechanism, only a weak form of access control which is easily cracked. WEP can be set up using man:ifconfig[8]: @@ -924,7 +1074,8 @@ Replace the `0x3456789012` with the key configured for use on the access point. Refer to man:ifconfig[8] for further information. -The man:wpa_supplicant[8] facility can be used to configure a wireless interface with WEP. The example above can be set up by adding the following lines to [.filename]#/etc/wpa_supplicant.conf#: +The man:wpa_supplicant[8] facility can be used to configure a wireless interface with WEP. +The example above can be set up by adding the following lines to [.filename]#/etc/wpa_supplicant.conf#: [.programlisting] .... @@ -947,7 +1098,8 @@ Associated with 00:13:46:49:41:76 === Ad-hoc Mode -IBSS mode, also called ad-hoc mode, is designed for point to point connections. For example, to establish an ad-hoc network between the machines `A` and `B`, choose two IP addresses and a SSID. +IBSS mode, also called ad-hoc mode, is designed for point to point connections. +For example, to establish an ad-hoc network between the machines `A` and `B`, choose two IP addresses and a SSID. On `A`: @@ -978,7 +1130,8 @@ The `adhoc` parameter indicates that the interface is running in IBSS mode. freebsdap 02:11:95:c3:0d:ac 2 54M -64:-96 100 IS WME .... -The `I` in the output confirms that `A` is in ad-hoc mode. Now, configure `B` with a different IP address: +The `I` in the output confirms that `A` is in ad-hoc mode. +Now, configure `B` with a different IP address: [source,shell] .... @@ -999,16 +1152,19 @@ Both `A` and `B` are now ready to exchange information. [[network-wireless-ap]] === FreeBSD Host Access Points -FreeBSD can act as an Access Point (AP) which eliminates the need to buy a hardware AP or run an ad-hoc network. This can be particularly useful when a FreeBSD machine is acting as a gateway to another network such as the Internet. +FreeBSD can act as an Access Point (AP) which eliminates the need to buy a hardware AP or run an ad-hoc network. +This can be particularly useful when a FreeBSD machine is acting as a gateway to another network such as the Internet. [[network-wireless-ap-basic]] ==== Basic Settings -Before configuring a FreeBSD machine as an AP, the kernel must be configured with the appropriate networking support for the wireless card as well as the security protocols being used. For more details, see <>. +Before configuring a FreeBSD machine as an AP, the kernel must be configured with the appropriate networking support for the wireless card as well as the security protocols being used. +For more details, see <>. [NOTE] ==== -The NDIS driver wrapper for Windows(R) drivers does not currently support AP operation. Only native FreeBSD wireless drivers support AP mode. +The NDIS driver wrapper for Windows(R) drivers does not currently support AP operation. +Only native FreeBSD wireless drivers support AP mode. ==== Once wireless networking support is loaded, check if the wireless device supports the host-based access point mode, also known as hostap mode: @@ -1021,7 +1177,10 @@ drivercaps=6f85edc1 .... -This output displays the card's capabilities. The `HOSTAP` word confirms that this wireless card can act as an AP. Various supported ciphers are also listed: WEP, TKIP, and AES. This information indicates which security protocols can be used on the AP. +This output displays the card's capabilities. +The `HOSTAP` word confirms that this wireless card can act as an AP. +Various supported ciphers are also listed: WEP, TKIP, and AES. +This information indicates which security protocols can be used on the AP. The wireless device can only be put into hostap mode during the creation of the network pseudo-device, so a previously created device must be destroyed first: @@ -1066,7 +1225,8 @@ ifconfig_wlan0="inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap mode 11g c ==== Host-based Access Point Without Authentication or Encryption -Although it is not recommended to run an AP without any authentication or encryption, this is a simple way to check if the AP is working. This configuration is also important for debugging client issues. +Although it is not recommended to run an AP without any authentication or encryption, this is a simple way to check if the AP is working. +This configuration is also important for debugging client issues. Once the AP is configured, initiate a scan from another wireless machine to find the AP: @@ -1098,11 +1258,13 @@ The client machine found the AP and can be associated with it: [[network-wireless-ap-wpa]] ==== WPA2 Host-based Access Point -This section focuses on setting up a FreeBSD access point using the WPA2 security protocol. More details regarding WPA and the configuration of WPA-based wireless clients can be found in <>. +This section focuses on setting up a FreeBSD access point using the WPA2 security protocol. +More details regarding WPA and the configuration of WPA-based wireless clients can be found in <>. The man:hostapd[8] daemon is used to deal with client authentication and key management on the WPA2-enabled AP. -The following configuration operations are performed on the FreeBSD machine acting as the AP. Once the AP is correctly working, man:hostapd[8] can be automatically started at boot with this line in [.filename]#/etc/rc.conf#: +The following configuration operations are performed on the FreeBSD machine acting as the AP. +Once the AP is correctly working, man:hostapd[8] can be automatically started at boot with this line in [.filename]#/etc/rc.conf#: [.programlisting] .... @@ -1164,11 +1326,14 @@ wlan0: flags=8943 metric 0 mtu 1 groups: wlan .... -Once the AP is running, the clients can associate with it. See <> for more details. It is possible to see the stations associated with the AP using `ifconfig _wlan0_ list sta`. +Once the AP is running, the clients can associate with it. +See <> for more details. +It is possible to see the stations associated with the AP using `ifconfig _wlan0_ list sta`. ==== WEP Host-based Access Point -It is not recommended to use WEP for setting up an AP since there is no authentication mechanism and the encryption is easily cracked. Some legacy wireless cards only support WEP and these cards will only support an AP without authentication or encryption. +It is not recommended to use WEP for setting up an AP since there is no authentication mechanism and the encryption is easily cracked. +Some legacy wireless cards only support WEP and these cards will only support an AP without authentication or encryption. The wireless device can now be put into hostap mode and configured with the correct SSID and IP address: @@ -1207,13 +1372,16 @@ SSID BSSID CHAN RATE S:N INT CAPS freebsdap 00:11:95:c3:0d:ac 1 54M 22:1 100 EPS .... -In this example, the client machine found the AP and can associate with it using the correct parameters. See <> for more details. +In this example, the client machine found the AP and can associate with it using the correct parameters. +See <> for more details. === Using Both Wired and Wireless Connections -A wired connection provides better performance and reliability, while a wireless connection provides flexibility and mobility. Laptop users typically want to roam seamlessly between the two types of connections. +A wired connection provides better performance and reliability, while a wireless connection provides flexibility and mobility. +Laptop users typically want to roam seamlessly between the two types of connections. -On FreeBSD, it is possible to combine two or even more network interfaces together in a "failover" fashion. This type of configuration uses the most preferred and available connection from a group of network interfaces, and the operating system switches automatically when the link state changes. +On FreeBSD, it is possible to combine two or even more network interfaces together in a "failover" fashion. +This type of configuration uses the most preferred and available connection from a group of network interfaces, and the operating system switches automatically when the link state changes. Link aggregation and failover is covered in <> and an example for using both wired and wireless connections is provided at <>. @@ -1234,14 +1402,18 @@ Debugging support is provided by man:wpa_supplicant[8]. Try running this utility net.wlan.0.debug: 0 => 0xc80000 .... + -Many useful statistics are maintained by the 802.11 layer and `wlanstats`, found in [.filename]#/usr/src/tools/tools/net80211#, will dump this information. These statistics should display all errors identified by the 802.11 layer. However, some errors are identified in the device drivers that lie below the 802.11 layer so they may not show up. To diagnose device-specific problems, refer to the drivers' documentation. +Many useful statistics are maintained by the 802.11 layer and `wlanstats`, found in [.filename]#/usr/src/tools/tools/net80211#, will dump this information. +These statistics should display all errors identified by the 802.11 layer. +However, some errors are identified in the device drivers that lie below the 802.11 layer so they may not show up. +To diagnose device-specific problems, refer to the drivers' documentation. If the above information does not help to clarify the problem, submit a problem report and include output from the above tools. [[network-usb-tethering]] == USB Tethering -Many cellphones provide the option to share their data connection over USB (often called "tethering"). This feature uses one of RNDIS, CDC, or a custom Apple(R) iPhone(R)/iPad(R) protocol. +Many cellphones provide the option to share their data connection over USB (often called "tethering"). +This feature uses one of RNDIS, CDC, or a custom Apple(R) iPhone(R)/iPad(R) protocol. * Android(TM) devices generally use the man:urndis[4] driver. * Apple(R) devices use the man:ipheth[4] driver. @@ -1256,7 +1428,8 @@ Before attaching a device, load the appropriate driver into the kernel: # kldload if_ipheth .... -Once the device is attached ``ue``_0_ will be available for use like a normal network device. Be sure that the "USB tethering" option is enabled on the device. +Once the device is attached ``ue``_0_ will be available for use like a normal network device. +Be sure that the "USB tethering" option is enabled on the device. To make this change permanent and load the driver as a module at boot time, place the appropriate line of the following in [.filename]#/boot/loader.conf#: @@ -1270,15 +1443,23 @@ if_ipheth_load="YES" [[network-bluetooth]] == Bluetooth -Bluetooth is a wireless technology for creating personal networks operating in the 2.4 GHz unlicensed band, with a range of 10 meters. Networks are usually formed ad-hoc from portable devices such as cellular phones, handhelds, and laptops. Unlike Wi-Fi wireless technology, Bluetooth offers higher level service profiles, such as FTP-like file servers, file pushing, voice transport, serial line emulation, and more. +Bluetooth is a wireless technology for creating personal networks operating in the 2.4 GHz unlicensed band, with a range of 10 meters. +Networks are usually formed ad-hoc from portable devices such as cellular phones, handhelds, and laptops. +Unlike Wi-Fi wireless technology, Bluetooth offers higher level service profiles, such as FTP-like file servers, file pushing, voice transport, serial line emulation, and more. -This section describes the use of a USB Bluetooth dongle on a FreeBSD system. It then describes the various Bluetooth protocols and utilities. +This section describes the use of a USB Bluetooth dongle on a FreeBSD system. +It then describes the various Bluetooth protocols and utilities. === Loading Bluetooth Support -The Bluetooth stack in FreeBSD is implemented using the man:netgraph[4] framework. A broad variety of Bluetooth USB dongles is supported by man:ng_ubt[4]. Broadcom BCM2033 based Bluetooth devices are supported by the man:ubtbcmfw[4] and man:ng_ubt[4] drivers. The 3Com Bluetooth PC Card 3CRWB60-A is supported by the man:ng_bt3c[4] driver. Serial and UART based Bluetooth devices are supported by man:sio[4], man:ng_h4[4], and man:hcseriald[8]. +The Bluetooth stack in FreeBSD is implemented using the man:netgraph[4] framework. +A broad variety of Bluetooth USB dongles is supported by man:ng_ubt[4]. +Broadcom BCM2033 based Bluetooth devices are supported by the man:ubtbcmfw[4] and man:ng_ubt[4] drivers. +The 3Com Bluetooth PC Card 3CRWB60-A is supported by the man:ng_bt3c[4] driver. +Serial and UART based Bluetooth devices are supported by man:sio[4], man:ng_h4[4], and man:hcseriald[8]. -Before attaching a device, determine which of the above drivers it uses, then load the driver. For example, if the device uses the man:ng_ubt[4] driver: +Before attaching a device, determine which of the above drivers it uses, then load the driver. +For example, if the device uses the man:ng_ubt[4] driver: [source,shell] .... @@ -1292,7 +1473,8 @@ If the Bluetooth device will be attached to the system during system startup, th ng_ubt_load="YES" .... -Once the driver is loaded, plug in the USB dongle. If the driver load was successful, output similar to the following should appear on the console and in [.filename]#/var/log/messages#: +Once the driver is loaded, plug in the USB dongle. +If the driver load was successful, output similar to the following should appear on the console and in [.filename]#/var/log/messages#: [source,shell] .... @@ -1302,7 +1484,9 @@ ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3, wMaxPacketSize=49, nframes=6, buffer size=294 .... -To start and stop the Bluetooth stack, use its startup script. It is a good idea to stop the stack before unplugging the device. Starting the bluetooth stack might require man:hcsecd[8] to be started. When starting the stack, the output should be similar to the following: +To start and stop the Bluetooth stack, use its startup script. It is a good idea to stop the stack before unplugging the device. +Starting the bluetooth stack might require man:hcsecd[8] to be started. +When starting the stack, the output should be similar to the following: [source,shell] .... @@ -1322,9 +1506,16 @@ Number of SCO packets: 8 === Finding Other Bluetooth Devices -The Host Controller Interface (HCI) provides a uniform method for accessing Bluetooth baseband capabilities. In FreeBSD, a netgraph HCI node is created for each Bluetooth device. For more details, refer to man:ng_hci[4]. +The Host Controller Interface (HCI) provides a uniform method for accessing Bluetooth baseband capabilities. +In FreeBSD, a netgraph HCI node is created for each Bluetooth device. +For more details, refer to man:ng_hci[4]. -One of the most common tasks is discovery of Bluetooth devices within RF proximity. This operation is called _inquiry_. Inquiry and other HCI related operations are done using man:hccontrol[8]. The example below shows how to find out which Bluetooth devices are in range. The list of devices should be displayed in a few seconds. Note that a remote device will only answer the inquiry if it is set to _discoverable_ mode. +One of the most common tasks is discovery of Bluetooth devices within RF proximity. +This operation is called _inquiry_. +Inquiry and other HCI related operations are done using man:hccontrol[8]. +The example below shows how to find out which Bluetooth devices are in range. +The list of devices should be displayed in a few seconds. +Note that a remote device will only answer the inquiry if it is set to _discoverable_ mode. [source,shell] .... @@ -1340,7 +1531,10 @@ Inquiry result #0 Inquiry complete. Status: No error [00] .... -The `BD_ADDR` is the unique address of a Bluetooth device, similar to the MAC address of a network card. This address is needed for further communication with a device and it is possible to assign a human readable name to a `BD_ADDR`. Information regarding the known Bluetooth hosts is contained in [.filename]#/etc/bluetooth/hosts#. The following example shows how to obtain the human readable name that was assigned to the remote device: +The `BD_ADDR` is the unique address of a Bluetooth device, similar to the MAC address of a network card. +This address is needed for further communication with a device and it is possible to assign a human readable name to a `BD_ADDR`. +Information regarding the known Bluetooth hosts is contained in [.filename]#/etc/bluetooth/hosts#. +The following example shows how to obtain the human readable name that was assigned to the remote device: [source,shell] .... @@ -1349,11 +1543,14 @@ BD_ADDR: 00:80:37:29:19:a4 Name: Pav's T39 .... -If an inquiry is performed on a remote Bluetooth device, it will find the computer as "your.host.name (ubt0)". The name assigned to the local device can be changed at any time. +If an inquiry is performed on a remote Bluetooth device, it will find the computer as "your.host.name (ubt0)". +The name assigned to the local device can be changed at any time. -Remote devices can be assigned aliases in [.filename]#/etc/bluetooth/hosts#. More information about [.filename]#/etc/bluetooth/hosts# file might be found in man:bluetooth.hosts[5]. +Remote devices can be assigned aliases in [.filename]#/etc/bluetooth/hosts#. +More information about [.filename]#/etc/bluetooth/hosts# file might be found in man:bluetooth.hosts[5]. -The Bluetooth system provides a point-to-point connection between two Bluetooth units, or a point-to-multipoint connection which is shared among several Bluetooth devices. The following example shows how to create a connection to a remote device: +The Bluetooth system provides a point-to-point connection between two Bluetooth units, or a point-to-multipoint connection which is shared among several Bluetooth devices. +The following example shows how to create a connection to a remote device: [source,shell] .... @@ -1371,7 +1568,8 @@ Remote BD_ADDR Handle Type Mode Role Encrypt Pending Queue State 00:80:37:29:19:a4 41 ACL 0 MAST NONE 0 0 OPEN .... -A _connection handle_ is useful when termination of the baseband connection is required, though it is normally not required to do this by hand. The stack will automatically terminate inactive baseband connections. +A _connection handle_ is useful when termination of the baseband connection is required, though it is normally not required to do this by hand. +The stack will automatically terminate inactive baseband connections. [source,shell] .... @@ -1380,13 +1578,24 @@ Connection handle: 41 Reason: Connection terminated by local host [0x16] .... -Type `hccontrol help` for a complete listing of available HCI commands. Most of the HCI commands do not require superuser privileges. +Type `hccontrol help` for a complete listing of available HCI commands. +Most of the HCI commands do not require superuser privileges. === Device Pairing -By default, Bluetooth communication is not authenticated, and any device can talk to any other device. A Bluetooth device, such as a cellular phone, may choose to require authentication to provide a particular service. Bluetooth authentication is normally done with a _PIN code_, an ASCII string up to 16 characters in length. The user is required to enter the same PIN code on both devices. Once the user has entered the PIN code, both devices will generate a _link key_. After that, the link key can be stored either in the devices or in a persistent storage. Next time, both devices will use the previously generated link key. This procedure is called _pairing_. Note that if the link key is lost by either device, the pairing must be repeated. +By default, Bluetooth communication is not authenticated, and any device can talk to any other device. +A Bluetooth device, such as a cellular phone, may choose to require authentication to provide a particular service. +Bluetooth authentication is normally done with a _PIN code_, an ASCII string up to 16 characters in length. +The user is required to enter the same PIN code on both devices. +Once the user has entered the PIN code, both devices will generate a _link key_. +After that, the link key can be stored either in the devices or in a persistent storage. +Next time, both devices will use the previously generated link key. +This procedure is called _pairing_. +Note that if the link key is lost by either device, the pairing must be repeated. -The man:hcsecd[8] daemon is responsible for handling Bluetooth authentication requests. The default configuration file is [.filename]#/etc/bluetooth/hcsecd.conf#. An example section for a cellular phone with the PIN code set to `1234` is shown below: +The man:hcsecd[8] daemon is responsible for handling Bluetooth authentication requests. +The default configuration file is [.filename]#/etc/bluetooth/hcsecd.conf#. +An example section for a cellular phone with the PIN code set to `1234` is shown below: [.programlisting] .... @@ -1398,7 +1607,14 @@ device { } .... -The only limitation on PIN codes is length. Some devices, such as Bluetooth headsets, may have a fixed PIN code built in. The `-d` switch forces man:hcsecd[8] to stay in the foreground, so it is easy to see what is happening. Set the remote device to receive pairing and initiate the Bluetooth connection to the remote device. The remote device should indicate that pairing was accepted and request the PIN code. Enter the same PIN code listed in [.filename]#hcsecd.conf#. Now the computer and the remote device are paired. Alternatively, pairing can be initiated on the remote device. +The only limitation on PIN codes is length. +Some devices, such as Bluetooth headsets, may have a fixed PIN code built in. +The `-d` switch forces man:hcsecd[8] to stay in the foreground, so it is easy to see what is happening. +Set the remote device to receive pairing and initiate the Bluetooth connection to the remote device. +The remote device should indicate that pairing was accepted and request the PIN code. +Enter the same PIN code listed in [.filename]#hcsecd.conf#. +Now the computer and the remote device are paired. +Alternatively, pairing can be initiated on the remote device. *** 26075 LINES SKIPPED *** From owner-dev-commits-doc-all@freebsd.org Sun Jun 6 12:26:30 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id A4D2B65D9CA for ; Sun, 6 Jun 2021 12:26:30 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FybMp43KQz4jNf; Sun, 6 Jun 2021 12:26:30 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 73B2B23572; Sun, 6 Jun 2021 12:26:30 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 156CQUX7086865; Sun, 6 Jun 2021 12:26:30 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 156CQUjs086864; Sun, 6 Jun 2021 12:26:30 GMT (envelope-from git) Date: Sun, 6 Jun 2021 12:26:30 GMT Message-Id: <202106061226.156CQUjs086864@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Sergio Carlavilla Delgado Subject: git: d00a527f1c - main - Use One Sentence Per Line in the Developers Handbook MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: carlavilla X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: d00a527f1ce922091d779911eaedde4efd122ea1 Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jun 2021 12:26:30 -0000 The branch main has been updated by carlavilla: URL: https://cgit.FreeBSD.org/doc/commit/?id=d00a527f1ce922091d779911eaedde4efd122ea1 commit d00a527f1ce922091d779911eaedde4efd122ea1 Author: Sergio Carlavilla Delgado AuthorDate: 2021-06-06 12:19:15 +0000 Commit: Sergio Carlavilla Delgado CommitDate: 2021-06-06 12:19:15 +0000 Use One Sentence Per Line in the Developers Handbook --- .../en/books/developers-handbook/_index.adoc | 9 +- .../content/en/books/developers-handbook/book.adoc | 9 +- .../developers-handbook/introduction/_index.adoc | 13 +- .../en/books/developers-handbook/ipv6/_index.adoc | 318 ++++-- .../developers-handbook/kernelbuild/_index.adoc | 10 +- .../developers-handbook/kerneldebug/_index.adoc | 182 +++- .../en/books/developers-handbook/l10n/_index.adoc | 82 +- .../en/books/developers-handbook/parti.adoc | 2 +- .../books/developers-handbook/policies/_index.adoc | 97 +- .../books/developers-handbook/secure/_index.adoc | 115 ++- .../books/developers-handbook/sockets/_index.adoc | 413 ++++++-- .../books/developers-handbook/testing/_index.adoc | 34 +- .../en/books/developers-handbook/tools/_index.adoc | 468 ++++++--- .../en/books/developers-handbook/x86/_index.adoc | 1060 ++++++++++++++------ 14 files changed, 2051 insertions(+), 761 deletions(-) diff --git a/documentation/content/en/books/developers-handbook/_index.adoc b/documentation/content/en/books/developers-handbook/_index.adoc index c30bf0645d..43db14ab19 100644 --- a/documentation/content/en/books/developers-handbook/_index.adoc +++ b/documentation/content/en/books/developers-handbook/_index.adoc @@ -48,12 +48,15 @@ include::../../../../shared/en/urls.adoc[] endif::[] [.abstract-title] -[abstract] Abstract -Welcome to the Developers' Handbook. This manual is a _work in progress_ and is the work of many individuals. Many sections do not yet exist and some of those that do exist need to be updated. If you are interested in helping with this project, send email to the {freebsd-doc}. +Welcome to the Developers' Handbook. +This manual is a _work in progress_ and is the work of many individuals. +Many sections do not yet exist and some of those that do exist need to be updated. +If you are interested in helping with this project, send email to the {freebsd-doc}. -The latest version of this document is always available from the link:https://www.FreeBSD.org[FreeBSD World Wide Web server]. It may also be downloaded in a variety of formats and compression options from the link:https://download.freebsd.org/ftp/doc/[FreeBSD FTP server] or one of the numerous link:{handbook}#mirrors-ftp/[mirror sites]. +The latest version of this document is always available from the link:https://www.FreeBSD.org[FreeBSD World Wide Web server]. +It may also be downloaded in a variety of formats and compression options from the link:https://download.freebsd.org/ftp/doc/[FreeBSD FTP server] or one of the numerous link:{handbook}#mirrors-ftp/[mirror sites]. ''' diff --git a/documentation/content/en/books/developers-handbook/book.adoc b/documentation/content/en/books/developers-handbook/book.adoc index 1e85eb8196..f874755ccd 100644 --- a/documentation/content/en/books/developers-handbook/book.adoc +++ b/documentation/content/en/books/developers-handbook/book.adoc @@ -61,12 +61,15 @@ include::../../../../shared/en/urls.adoc[] endif::[] [.abstract-title] -[abstract] Abstract -Welcome to the Developers' Handbook. This manual is a _work in progress_ and is the work of many individuals. Many sections do not yet exist and some of those that do exist need to be updated. If you are interested in helping with this project, send email to the {freebsd-doc}. +Welcome to the Developers' Handbook. +This manual is a _work in progress_ and is the work of many individuals. +Many sections do not yet exist and some of those that do exist need to be updated. +If you are interested in helping with this project, send email to the {freebsd-doc}. -The latest version of this document is always available from the link:https://www.FreeBSD.org[FreeBSD World Wide Web server]. It may also be downloaded in a variety of formats and compression options from the link:https://download.freebsd.org/ftp/doc/[FreeBSD FTP server] or one of the numerous link:{handbook}#mirrors-ftp/[mirror sites]. +The latest version of this document is always available from the link:https://www.FreeBSD.org[FreeBSD World Wide Web server]. +It may also be downloaded in a variety of formats and compression options from the link:https://download.freebsd.org/ftp/doc/[FreeBSD FTP server] or one of the numerous link:{handbook}#mirrors-ftp/[mirror sites]. ''' diff --git a/documentation/content/en/books/developers-handbook/introduction/_index.adoc b/documentation/content/en/books/developers-handbook/introduction/_index.adoc index c7c9ad74d0..35e8e65fca 100644 --- a/documentation/content/en/books/developers-handbook/introduction/_index.adoc +++ b/documentation/content/en/books/developers-handbook/introduction/_index.adoc @@ -37,9 +37,15 @@ toc::[] [[introduction-devel]] == Developing on FreeBSD -So here we are. System all installed and you are ready to start programming. But where to start? What does FreeBSD provide? What can it do for me, as a programmer? +So here we are. +System all installed and you are ready to start programming. +But where to start? What does FreeBSD provide? What can it do for me, as a programmer? -These are some questions which this chapter tries to answer. Of course, programming has different levels of proficiency like any other trade. For some it is a hobby, for others it is their profession. The information in this chapter might be aimed toward the beginning programmer; indeed, it could serve useful for the programmer unfamiliar with the FreeBSD platform. +These are some questions which this chapter tries to answer. +Of course, programming has different levels of proficiency like any other trade. +For some it is a hobby, for others it is their profession. +The information in this chapter might be aimed toward the beginning programmer; +indeed, it could serve useful for the programmer unfamiliar with the FreeBSD platform. [[introduction-bsdvision]] == The BSD Vision @@ -64,7 +70,8 @@ From Scheifler & Gettys: "X Window System" [[introduction-layout]] == The Layout of /usr/src -The complete source code to FreeBSD is available from our public repository. The source code is normally installed in [.filename]#/usr/src# which contains the following subdirectories: +The complete source code to FreeBSD is available from our public repository. +The source code is normally installed in [.filename]#/usr/src# which contains the following subdirectories: [.informaltable] [cols="1,1", frame="none", options="header"] diff --git a/documentation/content/en/books/developers-handbook/ipv6/_index.adoc b/documentation/content/en/books/developers-handbook/ipv6/_index.adoc index 6546bec79c..9596e12e78 100644 --- a/documentation/content/en/books/developers-handbook/ipv6/_index.adoc +++ b/documentation/content/en/books/developers-handbook/ipv6/_index.adoc @@ -36,18 +36,22 @@ toc::[] [[ipv6-implementation]] == IPv6/IPsec Implementation -This section should explain IPv6 and IPsec related implementation internals. These functionalities are derived from http://www.kame.net/[KAME project] +This section should explain IPv6 and IPsec related implementation internals. +These functionalities are derived from http://www.kame.net/[KAME project] [[ipv6details]] === IPv6 ==== Conformance -The IPv6 related functions conforms, or tries to conform to the latest set of IPv6 specifications. For future reference we list some of the relevant documents below (_NOTE_: this is not a complete list - this is too hard to maintain...). +The IPv6 related functions conforms, or tries to conform to the latest set of IPv6 specifications. +For future reference we list some of the relevant documents below (_NOTE_: this is not a complete list - this is too hard to maintain...). For details please refer to specific chapter in the document, RFCs, manual pages, or comments in the source code. -Conformance tests have been performed on the KAME STABLE kit at TAHI project. Results can be viewed at http://www.tahi.org/report/KAME/[http://www.tahi.org/report/KAME/]. We also attended University of New Hampshire IOL tests (http://www.iol.unh.edu/[http://www.iol.unh.edu/]) in the past, with our past snapshots. +Conformance tests have been performed on the KAME STABLE kit at TAHI project. +Results can be viewed at http://www.tahi.org/report/KAME/[http://www.tahi.org/report/KAME/]. +We also attended University of New Hampshire IOL tests (http://www.iol.unh.edu/[http://www.iol.unh.edu/]) in the past, with our past snapshots. * RFC1639: FTP Operation Over Big Address Records (FOOBAR) @@ -140,55 +144,91 @@ Conformance tests have been performed on the KAME STABLE kit at TAHI project. Re [[neighbor-discovery]] ==== Neighbor Discovery -Neighbor Discovery is fairly stable. Currently Address Resolution, Duplicated Address Detection, and Neighbor Unreachability Detection are supported. In the near future we will be adding Proxy Neighbor Advertisement support in the kernel and Unsolicited Neighbor Advertisement transmission command as admin tool. +Neighbor Discovery is fairly stable. +Currently Address Resolution, Duplicated Address Detection, and Neighbor Unreachability Detection are supported. +In the near future we will be adding Proxy Neighbor Advertisement support in the kernel and Unsolicited Neighbor Advertisement transmission command as admin tool. -If DAD fails, the address will be marked "duplicated" and message will be generated to syslog (and usually to console). The "duplicated" mark can be checked with man:ifconfig[8]. It is administrators' responsibility to check for and recover from DAD failures. The behavior should be improved in the near future. +If DAD fails, the address will be marked "duplicated" and message will be generated to syslog (and usually to console). +The "duplicated" mark can be checked with man:ifconfig[8]. +It is administrators' responsibility to check for and recover from DAD failures. +The behavior should be improved in the near future. -Some of the network driver loops multicast packets back to itself, even if instructed not to do so (especially in promiscuous mode). In such cases DAD may fail, because DAD engine sees inbound NS packet (actually from the node itself) and considers it as a sign of duplicate. You may want to look at #if condition marked "heuristics" in sys/netinet6/nd6_nbr.c:nd6_dad_timer() as workaround (note that the code fragment in "heuristics" section is not spec conformant). +Some of the network driver loops multicast packets back to itself, even if instructed not to do so (especially in promiscuous mode). +In such cases DAD may fail, because DAD engine sees inbound NS packet (actually from the node itself) and considers it as a sign of duplicate. +You may want to look at #if condition marked "heuristics" in sys/netinet6/nd6_nbr.c:nd6_dad_timer() as workaround (note that the code fragment in "heuristics" section is not spec conformant). Neighbor Discovery specification (RFC2461) does not talk about neighbor cache handling in the following cases: . when there was no neighbor cache entry, node received unsolicited RS/NS/NA/redirect packet without link-layer address . neighbor cache handling on medium without link-layer address (we need a neighbor cache entry for IsRouter bit) -For first case, we implemented workaround based on discussions on IETF ipngwg mailing list. For more details, see the comments in the source code and email thread started from (IPng 7155), dated Feb 6 1999. +For first case, we implemented workaround based on discussions on IETF ipngwg mailing list. +For more details, see the comments in the source code and email thread started from (IPng 7155), dated Feb 6 1999. -IPv6 on-link determination rule (RFC2461) is quite different from assumptions in BSD network code. At this moment, no on-link determination rule is supported where default router list is empty (RFC2461, section 5.2, last sentence in 2nd paragraph - note that the spec misuse the word "host" and "node" in several places in the section). +IPv6 on-link determination rule (RFC2461) is quite different from assumptions in BSD network code. +At this moment, no on-link determination rule is supported where default router list is empty (RFC2461, section 5.2, last sentence in 2nd paragraph - note that the spec misuse the word "host" and "node" in several places in the section). -To avoid possible DoS attacks and infinite loops, only 10 options on ND packet is accepted now. Therefore, if you have 20 prefix options attached to RA, only the first 10 prefixes will be recognized. If this troubles you, please ask it on FREEBSD-CURRENT mailing list and/or modify nd6_maxndopt in [.filename]#sys/netinet6/nd6.c#. If there are high demands we may provide sysctl knob for the variable. +To avoid possible DoS attacks and infinite loops, only 10 options on ND packet is accepted now. +Therefore, if you have 20 prefix options attached to RA, only the first 10 prefixes will be recognized. +If this troubles you, please ask it on FREEBSD-CURRENT mailing list and/or modify nd6_maxndopt in [.filename]#sys/netinet6/nd6.c#. +If there are high demands we may provide sysctl knob for the variable. [[ipv6-scope-index]] ==== Scope Index -IPv6 uses scoped addresses. Therefore, it is very important to specify scope index (interface index for link-local address, or site index for site-local address) with an IPv6 address. Without scope index, scoped IPv6 address is ambiguous to the kernel, and kernel will not be able to determine the outbound interface for a packet. +IPv6 uses scoped addresses. +Therefore, it is very important to specify scope index (interface index for link-local address, or site index for site-local address) with an IPv6 address. +Without scope index, scoped IPv6 address is ambiguous to the kernel, and kernel will not be able to determine the outbound interface for a packet. -Ordinary userland applications should use advanced API (RFC2292) to specify scope index, or interface index. For similar purpose, sin6_scope_id member in sockaddr_in6 structure is defined in RFC2553. However, the semantics for sin6_scope_id is rather vague. If you care about portability of your application, we suggest you to use advanced API rather than sin6_scope_id. +Ordinary userland applications should use advanced API (RFC2292) to specify scope index, or interface index. +For similar purpose, sin6_scope_id member in sockaddr_in6 structure is defined in RFC2553. +However, the semantics for sin6_scope_id is rather vague. +If you care about portability of your application, we suggest you to use advanced API rather than sin6_scope_id. -In the kernel, an interface index for link-local scoped address is embedded into 2nd 16bit-word (3rd and 4th byte) in IPv6 address. For example, you may see something like: +In the kernel, an interface index for link-local scoped address is embedded into 2nd 16bit-word (3rd and 4th byte) in IPv6 address. +For example, you may see something like: [source,bash] .... fe80:1::200:f8ff:fe01:6317 .... -in the routing table and interface address structure (struct in6_ifaddr). The address above is a link-local unicast address which belongs to a network interface whose interface identifier is 1. The embedded index enables us to identify IPv6 link local addresses over multiple interfaces effectively and with only a little code change. +in the routing table and interface address structure (struct in6_ifaddr). +The address above is a link-local unicast address which belongs to a network interface whose interface identifier is 1. +The embedded index enables us to identify IPv6 link local addresses over multiple interfaces effectively and with only a little code change. -Routing daemons and configuration programs, like man:route6d[8] and man:ifconfig[8], will need to manipulate the "embedded" scope index. These programs use routing sockets and ioctls (like SIOCGIFADDR_IN6) and the kernel API will return IPv6 addresses with 2nd 16bit-word filled in. The APIs are for manipulating kernel internal structure. Programs that use these APIs have to be prepared about differences in kernels anyway. +Routing daemons and configuration programs, like man:route6d[8] and man:ifconfig[8], will need to manipulate the "embedded" scope index. +These programs use routing sockets and ioctls (like SIOCGIFADDR_IN6) and the kernel API will return IPv6 addresses with 2nd 16bit-word filled in. +The APIs are for manipulating kernel internal structure. +Programs that use these APIs have to be prepared about differences in kernels anyway. -When you specify scoped address to the command line, NEVER write the embedded form (such as ff02:1::1 or fe80:2::fedc). This is not supposed to work. Always use standard form, like ff02::1 or fe80::fedc, with command line option for specifying interface (like `ping6 -I ne0 ff02::1`). In general, if a command does not have command line option to specify outgoing interface, that command is not ready to accept scoped address. This may seem to be opposite from IPv6's premise to support "dentist office" situation. We believe that specifications need some improvements for this. +When you specify scoped address to the command line, NEVER write the embedded form (such as ff02:1::1 or fe80:2::fedc). +This is not supposed to work. +Always use standard form, like ff02::1 or fe80::fedc, with command line option for specifying interface (like `ping6 -I ne0 ff02::1`). +In general, if a command does not have command line option to specify outgoing interface, that command is not ready to accept scoped address. +This may seem to be opposite from IPv6's premise to support "dentist office" situation. +We believe that specifications need some improvements for this. -Some of the userland tools support extended numeric IPv6 syntax, as documented in [.filename]#draft-ietf-ipngwg-scopedaddr-format-00.txt#. You can specify outgoing link, by using name of the outgoing interface like "fe80::1%ne0". This way you will be able to specify link-local scoped address without much trouble. +Some of the userland tools support extended numeric IPv6 syntax, as documented in [.filename]#draft-ietf-ipngwg-scopedaddr-format-00.txt#. +You can specify outgoing link, by using name of the outgoing interface like "fe80::1%ne0". +This way you will be able to specify link-local scoped address without much trouble. -To use this extension in your program, you will need to use man:getaddrinfo[3], and man:getnameinfo[3] with NI_WITHSCOPEID. The implementation currently assumes 1-to-1 relationship between a link and an interface, which is stronger than what specs say. +To use this extension in your program, you will need to use man:getaddrinfo[3], and man:getnameinfo[3] with NI_WITHSCOPEID. +The implementation currently assumes 1-to-1 relationship between a link and an interface, which is stronger than what specs say. [[ipv6-pnp]] ==== Plug and Play -Most of the IPv6 stateless address autoconfiguration is implemented in the kernel. Neighbor Discovery functions are implemented in the kernel as a whole. Router Advertisement (RA) input for hosts is implemented in the kernel. Router Solicitation (RS) output for endhosts, RS input for routers, and RA output for routers are implemented in the userland. +Most of the IPv6 stateless address autoconfiguration is implemented in the kernel. +Neighbor Discovery functions are implemented in the kernel as a whole. +Router Advertisement (RA) input for hosts is implemented in the kernel. +Router Solicitation (RS) output for endhosts, RS input for routers, and RA output for routers are implemented in the userland. ===== Assignment of link-local, and special addresses -IPv6 link-local address is generated from IEEE802 address (Ethernet MAC address). Each of interface is assigned an IPv6 link-local address automatically, when the interface becomes up (IFF_UP). Also, direct route for the link-local address is added to routing table. +IPv6 link-local address is generated from IEEE802 address (Ethernet MAC address). +Each of interface is assigned an IPv6 link-local address automatically, when the interface becomes up (IFF_UP). +Also, direct route for the link-local address is added to routing table. Here is an output of netstat command: @@ -200,17 +240,30 @@ fe80:1::%ed0/64 link#1 UC ed0 fe80:2::%ep0/64 link#2 UC ep0 .... -Interfaces that has no IEEE802 address (pseudo interfaces like tunnel interfaces, or ppp interfaces) will borrow IEEE802 address from other interfaces, such as Ethernet interfaces, whenever possible. If there is no IEEE802 hardware attached, a last resort pseudo-random value, MD5(hostname), will be used as source of link-local address. If it is not suitable for your usage, you will need to configure the link-local address manually. +Interfaces that has no IEEE802 address (pseudo interfaces like tunnel interfaces, or ppp interfaces) will borrow IEEE802 address from other interfaces, such as Ethernet interfaces, whenever possible. +If there is no IEEE802 hardware attached, a last resort pseudo-random value, MD5(hostname), will be used as source of link-local address. +If it is not suitable for your usage, you will need to configure the link-local address manually. -If an interface is not capable of handling IPv6 (such as lack of multicast support), link-local address will not be assigned to that interface. See section 2 for details. +If an interface is not capable of handling IPv6 (such as lack of multicast support), link-local address will not be assigned to that interface. +See section 2 for details. -Each interface joins the solicited multicast address and the link-local all-nodes multicast addresses (e.g., fe80::1:ff01:6317 and ff02::1, respectively, on the link the interface is attached). In addition to a link-local address, the loopback address (::1) will be assigned to the loopback interface. Also, ::1/128 and ff01::/32 are automatically added to routing table, and loopback interface joins node-local multicast group ff01::1. +Each interface joins the solicited multicast address and the link-local all-nodes multicast addresses (e.g., fe80::1:ff01:6317 and ff02::1, respectively, on the link the interface is attached). +In addition to a link-local address, the loopback address (::1) will be assigned to the loopback interface. +Also, ::1/128 and ff01::/32 are automatically added to routing table, and loopback interface joins node-local multicast group ff01::1. ===== Stateless address autoconfiguration on Hosts -In IPv6 specification, nodes are separated into two categories: _routers_ and _hosts_. Routers forward packets addressed to others, hosts does not forward the packets. net.inet6.ip6.forwarding defines whether this node is router or host (router if it is 1, host if it is 0). +In IPv6 specification, nodes are separated into two categories: _routers_ and _hosts_. +Routers forward packets addressed to others, hosts does not forward the packets. net.inet6.ip6.forwarding defines whether this node is router or host (router if it is 1, host if it is 0). -When a host hears Router Advertisement from the router, a host may autoconfigure itself by stateless address autoconfiguration. This behavior can be controlled by net.inet6.ip6.accept_rtadv (host autoconfigures itself if it is set to 1). By autoconfiguration, network address prefix for the receiving interface (usually global address prefix) is added. Default route is also configured. Routers periodically generate Router Advertisement packets. To request an adjacent router to generate RA packet, a host can transmit Router Solicitation. To generate a RS packet at any time, use the _rtsol_ command. man:rtsold[8] daemon is also available. man:rtsold[8] generates Router Solicitation whenever necessary, and it works great for nomadic usage (notebooks/laptops). If one wishes to ignore Router Advertisements, use sysctl to set net.inet6.ip6.accept_rtadv to 0. +When a host hears Router Advertisement from the router, a host may autoconfigure itself by stateless address autoconfiguration. +This behavior can be controlled by net.inet6.ip6.accept_rtadv (host autoconfigures itself if it is set to 1). +By autoconfiguration, network address prefix for the receiving interface (usually global address prefix) is added. +Default route is also configured. Routers periodically generate Router Advertisement packets. +To request an adjacent router to generate RA packet, a host can transmit Router Solicitation. +To generate a RS packet at any time, use the _rtsol_ command. man:rtsold[8] daemon is also available. +man:rtsold[8] generates Router Solicitation whenever necessary, and it works great for nomadic usage (notebooks/laptops). +If one wishes to ignore Router Advertisements, use sysctl to set net.inet6.ip6.accept_rtadv to 0. To generate Router Advertisement from a router, use the man:rtadvd[8] daemon. @@ -219,7 +272,8 @@ Note that, IPv6 specification assumes the following items, and nonconforming cas * Only hosts will listen to router advertisements * Hosts have single network interface (except loopback) -Therefore, this is unwise to enable net.inet6.ip6.accept_rtadv on routers, or multi-interface host. A misconfigured node can behave strange (nonconforming configuration allowed for those who would like to do some experiments). +Therefore, this is unwise to enable net.inet6.ip6.accept_rtadv on routers, or multi-interface host. +A misconfigured node can behave strange (nonconforming configuration allowed for those who would like to do some experiments). To summarize the sysctl knob: @@ -238,30 +292,39 @@ To summarize the sysctl knob: (out-of-scope of spec) .... -RFC2462 has validation rule against incoming RA prefix information option, in 5.5.3 (e). This is to protect hosts from malicious (or misconfigured) routers that advertise very short prefix lifetime. There was an update from Jim Bound to ipngwg mailing list (look for "(ipng 6712)" in the archive) and it is implemented Jim's update. +RFC2462 has validation rule against incoming RA prefix information option, in 5.5.3 (e). +This is to protect hosts from malicious (or misconfigured) routers that advertise very short prefix lifetime. +There was an update from Jim Bound to ipngwg mailing list (look for "(ipng 6712)" in the archive) and it is implemented Jim's update. See <> in the document for relationship between DAD and autoconfiguration. [[gif]] ==== Generic Tunnel Interface -GIF (Generic InterFace) is a pseudo interface for configured tunnel. Details are described in man:gif[4]. Currently +GIF (Generic InterFace) is a pseudo interface for configured tunnel. +Details are described in man:gif[4]. Currently * v6 in v6 * v6 in v4 * v4 in v6 * v4 in v4 -are available. Use man:gifconfig[8] to assign physical (outer) source and destination address to gif interfaces. Configuration that uses same address family for inner and outer IP header (v4 in v4, or v6 in v6) is dangerous. It is very easy to configure interfaces and routing tables to perform infinite level of tunneling. _Please be warned_. +are available. Use man:gifconfig[8] to assign physical (outer) source and destination address to gif interfaces. +Configuration that uses same address family for inner and outer IP header (v4 in v4, or v6 in v6) is dangerous. +It is very easy to configure interfaces and routing tables to perform infinite level of tunneling. +_Please be warned_. -gif can be configured to be ECN-friendly. See <> for ECN-friendliness of tunnels, and man:gif[4] for how to configure. +gif can be configured to be ECN-friendly. +See <> for ECN-friendliness of tunnels, and man:gif[4] for how to configure. -If you would like to configure an IPv4-in-IPv6 tunnel with gif interface, read man:gif[4] carefully. You will need to remove IPv6 link-local address automatically assigned to the gif interface. +If you would like to configure an IPv4-in-IPv6 tunnel with gif interface, read man:gif[4] carefully. +You will need to remove IPv6 link-local address automatically assigned to the gif interface. [[ipv6-sas]] ==== Source Address Selection -Current source selection rule is scope oriented (there are some exceptions - see below). For a given destination, a source IPv6 address is selected by the following rule: +Current source selection rule is scope oriented (there are some exceptions - see below). +For a given destination, a source IPv6 address is selected by the following rule: . If the source address is explicitly specified by the user (e.g., via the advanced API), the specified address is used. . If there is an address assigned to the outgoing interface (which is usually determined by looking up the routing table) that has the same scope as the destination address, the address is used. @@ -271,16 +334,29 @@ This is the most typical case. . If there is no address that satisfies the above condition, and destination address is site local scope, choose a site local address assigned to one of the interfaces on the sending node. . If there is no address that satisfies the above condition, choose the address associated with the routing table entry for the destination. This is the last resort, which may cause scope violation. -For instance, ::1 is selected for ff01::1, fe80:1::200:f8ff:fe01:6317 for fe80:1::2a0:24ff:feab:839b (note that embedded interface index - described in <> - helps us choose the right source address. Those embedded indices will not be on the wire). If the outgoing interface has multiple address for the scope, a source is selected longest match basis (rule 3). Suppose 2001:0DB8:808:1:200:f8ff:fe01:6317 and 2001:0DB8:9:124:200:f8ff:fe01:6317 are given to the outgoing interface. 2001:0DB8:808:1:200:f8ff:fe01:6317 is chosen as the source for the destination 2001:0DB8:800::1. +For instance, ::1 is selected for ff01::1, fe80:1::200:f8ff:fe01:6317 for fe80:1::2a0:24ff:feab:839b (note that embedded interface index - described in <> - helps us choose the right source address. +Those embedded indices will not be on the wire). +If the outgoing interface has multiple address for the scope, a source is selected longest match basis (rule 3). +Suppose 2001:0DB8:808:1:200:f8ff:fe01:6317 and 2001:0DB8:9:124:200:f8ff:fe01:6317 are given to the outgoing interface. 2001:0DB8:808:1:200:f8ff:fe01:6317 is chosen as the source for the destination 2001:0DB8:800::1. -Note that the above rule is not documented in the IPv6 spec. It is considered "up to implementation" item. There are some cases where we do not use the above rule. One example is connected TCP session, and we use the address kept in tcb as the source. Another example is source address for Neighbor Advertisement. Under the spec (RFC2461 7.2.2) NA's source should be the target address of the corresponding NS's target. In this case we follow the spec rather than the above longest-match rule. +Note that the above rule is not documented in the IPv6 spec. It is considered "up to implementation" item. +There are some cases where we do not use the above rule. +One example is connected TCP session, and we use the address kept in tcb as the source. +Another example is source address for Neighbor Advertisement. +Under the spec (RFC2461 7.2.2) NA's source should be the target address of the corresponding NS's target. +In this case we follow the spec rather than the above longest-match rule. -For new connections (when rule 1 does not apply), deprecated addresses (addresses with preferred lifetime = 0) will not be chosen as source address if other choices are available. If no other choices are available, deprecated address will be used as a last resort. If there are multiple choice of deprecated addresses, the above scope rule will be used to choose from those deprecated addresses. If you would like to prohibit the use of deprecated address for some reason, configure net.inet6.ip6.use_deprecated to 0. The issue related to deprecated address is described in RFC2462 5.5.4 (NOTE: there is some debate underway in IETF ipngwg on how to use "deprecated" address). +For new connections (when rule 1 does not apply), deprecated addresses (addresses with preferred lifetime = 0) will not be chosen as source address if other choices are available. +If no other choices are available, deprecated address will be used as a last resort. +If there are multiple choice of deprecated addresses, the above scope rule will be used to choose from those deprecated addresses. +If you would like to prohibit the use of deprecated address for some reason, configure net.inet6.ip6.use_deprecated to 0. +The issue related to deprecated address is described in RFC2462 5.5.4 (NOTE: there is some debate underway in IETF ipngwg on how to use "deprecated" address). [[ipv6-jumbo]] ==== Jumbo Payload -The Jumbo Payload hop-by-hop option is implemented and can be used to send IPv6 packets with payloads longer than 65,535 octets. But currently no physical interface whose MTU is more than 65,535 is supported, so such payloads can be seen only on the loopback interface (i.e., lo0). +The Jumbo Payload hop-by-hop option is implemented and can be used to send IPv6 packets with payloads longer than 65,535 octets. +But currently no physical interface whose MTU is more than 65,535 is supported, so such payloads can be seen only on the loopback interface (i.e., lo0). If you want to try jumbo payloads, you first have to reconfigure the kernel so that the MTU of the loopback interface is more than 65,535 bytes; add the following to the kernel configuration file: @@ -288,16 +364,22 @@ If you want to try jumbo payloads, you first have to reconfigure the kernel so t and recompile the new kernel. -Then you can test jumbo payloads by the man:ping6[8] command with -b and -s options. The -b option must be specified to enlarge the size of the socket buffer and the -s option specifies the length of the packet, which should be more than 65,535. For example, type as follows: +Then you can test jumbo payloads by the man:ping6[8] command with -b and -s options. +The -b option must be specified to enlarge the size of the socket buffer and the -s option specifies the length of the packet, which should be more than 65,535. +For example, type as follows: [source,bash] .... % ping6 -b 70000 -s 68000 ::1 .... -The IPv6 specification requires that the Jumbo Payload option must not be used in a packet that carries a fragment header. If this condition is broken, an ICMPv6 Parameter Problem message must be sent to the sender. specification is followed, but you cannot usually see an ICMPv6 error caused by this requirement. +The IPv6 specification requires that the Jumbo Payload option must not be used in a packet that carries a fragment header. +If this condition is broken, an ICMPv6 Parameter Problem message must be sent to the sender. +specification is followed, but you cannot usually see an ICMPv6 error caused by this requirement. -When an IPv6 packet is received, the frame length is checked and compared to the length specified in the payload length field of the IPv6 header or in the value of the Jumbo Payload option, if any. If the former is shorter than the latter, the packet is discarded and statistics are incremented. You can see the statistics as output of man:netstat[8] command with `-s -p ip6' option: +When an IPv6 packet is received, the frame length is checked and compared to the length specified in the payload length field of the IPv6 header or in the value of the Jumbo Payload option, if any. +If the former is shorter than the latter, the packet is discarded and statistics are incremented. +You can see the statistics as output of man:netstat[8] command with `-s -p ip6' option: [source,bash] .... @@ -307,45 +389,72 @@ When an IPv6 packet is received, the frame length is checked and compared to the 1 with data size < data length .... -So, kernel does not send an ICMPv6 error unless the erroneous packet is an actual Jumbo Payload, that is, its packet size is more than 65,535 bytes. As described above, currently no physical interface with such a huge MTU is supported, so it rarely returns an ICMPv6 error. +So, kernel does not send an ICMPv6 error unless the erroneous packet is an actual Jumbo Payload, that is, its packet size is more than 65,535 bytes. +As described above, currently no physical interface with such a huge MTU is supported, so it rarely returns an ICMPv6 error. -TCP/UDP over jumbogram is not supported at this moment. This is because we have no medium (other than loopback) to test this. Contact us if you need this. +TCP/UDP over jumbogram is not supported at this moment. +This is because we have no medium (other than loopback) to test this. Contact us if you need this. -IPsec does not work on jumbograms. This is due to some specification twists in supporting AH with jumbograms (AH header size influences payload length, and this makes it real hard to authenticate inbound packet with jumbo payload option as well as AH). +IPsec does not work on jumbograms. +This is due to some specification twists in supporting AH with jumbograms (AH header size influences payload length, and this makes it real hard to authenticate inbound packet with jumbo payload option as well as AH). -There are fundamental issues in *BSD support for jumbograms. We would like to address those, but we need more time to finalize these. To name a few: +There are fundamental issues in *BSD support for jumbograms. +We would like to address those, but we need more time to finalize these. +To name a few: + +* mbuf pkthdr.len field is typed as "int" in 4.4BSD, so it will not hold jumbogram with len > 2G on 32bit architecture CPUs. +If we would like to support jumbogram properly, the field must be expanded to hold 4G + IPv6 header + link-layer header. +Therefore, it must be expanded to at least int64_t (u_int32_t is NOT enough). -* mbuf pkthdr.len field is typed as "int" in 4.4BSD, so it will not hold jumbogram with len > 2G on 32bit architecture CPUs. If we would like to support jumbogram properly, the field must be expanded to hold 4G + IPv6 header + link-layer header. Therefore, it must be expanded to at least int64_t (u_int32_t is NOT enough). * We mistakingly use "int" to hold packet length in many places. We need to convert them into larger integral type. It needs a great care, as we may experience overflow during packet length computation. * We mistakingly check for ip6_plen field of IPv6 header for packet payload length in various places. We should be checking mbuf pkthdr.len instead. ip6_input() will perform sanity check on jumbo payload option on input, and we can safely use mbuf pkthdr.len afterwards. * TCP code needs a careful update in bunch of places, of course. ==== Loop Prevention in Header Processing -IPv6 specification allows arbitrary number of extension headers to be placed onto packets. If we implement IPv6 packet processing code in the way BSD IPv4 code is implemented, kernel stack may overflow due to long function call chain. sys/netinet6 code is carefully designed to avoid kernel stack overflow, so sys/netinet6 code defines its own protocol switch structure, as "struct ip6protosw" (see [.filename]#netinet6/ip6protosw.h#). There is no such update to IPv4 part (sys/netinet) for compatibility, but small change is added to its pr_input() prototype. So "struct ipprotosw" is also defined. As a result, if you receive IPsec-over-IPv4 packet with massive number of IPsec headers, kernel stack may blow up. IPsec-over-IPv6 is okay. (Of-course, for those all IPsec headers to be processed, each such IPsec header must pass each IPsec check. So an anonymous attacker will not be able to do such an attack.) +IPv6 specification allows arbitrary number of extension headers to be placed onto packets. +If we implement IPv6 packet processing code in the way BSD IPv4 code is implemented, kernel stack may overflow due to long function call chain. +sys/netinet6 code is carefully designed to avoid kernel stack overflow, so sys/netinet6 code defines its own protocol switch structure, as "struct ip6protosw" (see [.filename]#netinet6/ip6protosw.h#). +There is no such update to IPv4 part (sys/netinet) for compatibility, but small change is added to its pr_input() prototype. +So "struct ipprotosw" is also defined. +As a result, if you receive IPsec-over-IPv4 packet with massive number of IPsec headers, kernel stack may blow up. +IPsec-over-IPv6 is okay. +(Of-course, for those all IPsec headers to be processed, each such IPsec header must pass each IPsec check. +So an anonymous attacker will not be able to do such an attack.) [[icmpv6]] ==== ICMPv6 -After RFC2463 was published, IETF ipngwg has decided to disallow ICMPv6 error packet against ICMPv6 redirect, to prevent ICMPv6 storm on a network medium. This is already implemented into the kernel. +After RFC2463 was published, IETF ipngwg has decided to disallow ICMPv6 error packet against ICMPv6 redirect, to prevent ICMPv6 storm on a network medium. +This is already implemented into the kernel. ==== Applications For userland programming, we support IPv6 socket API as specified in RFC2553, RFC2292 and upcoming Internet drafts. -TCP/UDP over IPv6 is available and quite stable. You can enjoy man:telnet[1], man:ftp[1], man:rlogin[1], man:rsh[1], man:ssh[1], etc. These applications are protocol independent. That is, they automatically chooses IPv4 or IPv6 according to DNS. +TCP/UDP over IPv6 is available and quite stable. +You can enjoy man:telnet[1], man:ftp[1], man:rlogin[1], man:rsh[1], man:ssh[1], etc. +These applications are protocol independent. +That is, they automatically chooses IPv4 or IPv6 according to DNS. ==== Kernel Internals While ip_forward() calls ip_output(), ip6_forward() directly calls if_output() since routers must not divide IPv6 packets into fragments. -ICMPv6 should contain the original packet as long as possible up to 1280. UDP6/IP6 port unreach, for instance, should contain all extension headers and the *unchanged* UDP6 and IP6 headers. So, all IP6 functions except TCP never convert network byte order into host byte order, to save the original packet. +ICMPv6 should contain the original packet as long as possible up to 1280. +UDP6/IP6 port unreach, for instance, should contain all extension headers and the *unchanged* UDP6 and IP6 headers. +So, all IP6 functions except TCP never convert network byte order into host byte order, to save the original packet. -tcp_input(), udp6_input() and icmp6_input() can not assume that IP6 header is preceding the transport headers due to extension headers. So, in6_cksum() was implemented to handle packets whose IP6 header and transport header is not continuous. TCP/IP6 nor UDP6/IP6 header structures do not exist for checksum calculation. +tcp_input(), udp6_input() and icmp6_input() can not assume that IP6 header is preceding the transport headers due to extension headers. +So, in6_cksum() was implemented to handle packets whose IP6 header and transport header is not continuous. +TCP/IP6 nor UDP6/IP6 header structures do not exist for checksum calculation. -To process IP6 header, extension headers and transport headers easily, network drivers are now required to store packets in one internal mbuf or one or more external mbufs. A typical old driver prepares two internal mbufs for 96 - 204 bytes data, however, now such packet data is stored in one external mbuf. +To process IP6 header, extension headers and transport headers easily, network drivers are now required to store packets in one internal mbuf or one or more external mbufs. +A typical old driver prepares two internal mbufs for 96 - 204 bytes data, however, now such packet data is stored in one external mbuf. -`netstat -s -p ip6` tells you whether or not your driver conforms such requirement. In the following example, "cce0" violates the requirement. (For more information, refer to Section 2.) +`netstat -s -p ip6` tells you whether or not your driver conforms such requirement. +In the following example, "cce0" violates the requirement. +(For more information, refer to Section 2.) [source,bash] .... @@ -358,19 +467,23 @@ Mbuf statistics: 0 two or more ext mbuf .... -Each input function calls IP6_EXTHDR_CHECK in the beginning to check if the region between IP6 and its header is continuous. IP6_EXTHDR_CHECK calls m_pullup() only if the mbuf has M_LOOP flag, that is, the packet comes from the loopback interface. m_pullup() is never called for packets coming from physical network interfaces. +Each input function calls IP6_EXTHDR_CHECK in the beginning to check if the region between IP6 and its header is continuous. +IP6_EXTHDR_CHECK calls m_pullup() only if the mbuf has M_LOOP flag, that is, the packet comes from the loopback interface. +m_pullup() is never called for packets coming from physical network interfaces. Both IP and IP6 reassemble functions never call m_pullup(). [[ipv6-wildcard-socket]] ==== IPv4 Mapped Address and IPv6 Wildcard Socket -RFC2553 describes IPv4 mapped address (3.7) and special behavior of IPv6 wildcard bind socket (3.8). The spec allows you to: +RFC2553 describes IPv4 mapped address (3.7) and special behavior of IPv6 wildcard bind socket (3.8). +The spec allows you to: * Accept IPv4 connections by AF_INET6 wildcard bind socket. * Transmit IPv4 packet over AF_INET6 socket by using special form of the address like ::ffff:10.1.1.1. -but the spec itself is very complicated and does not specify how the socket layer should behave. Here we call the former one "listening side" and the latter one "initiating side", for reference purposes. +but the spec itself is very complicated and does not specify how the socket layer should behave. +Here we call the former one "listening side" and the latter one "initiating side", for reference purposes. You can perform wildcard bind on both of the address families, on the same port. @@ -390,15 +503,29 @@ The following sections will give you more details, and how you can configure the Comments on listening side: -It looks that RFC2553 talks too little on wildcard bind issue, especially on the port space issue, failure mode and relationship between AF_INET/INET6 wildcard bind. There can be several separate interpretation for this RFC which conform to it but behaves differently. So, to implement portable application you should assume nothing about the behavior in the kernel. Using man:getaddrinfo[3] is the safest way. Port number space and wildcard bind issues were discussed in detail on ipv6imp mailing list, in mid March 1999 and it looks that there is no concrete consensus (means, up to implementers). You may want to check the mailing list archives. +It looks that RFC2553 talks too little on wildcard bind issue, especially on the port space issue, failure mode and relationship between AF_INET/INET6 wildcard bind. +There can be several separate interpretation for this RFC which conform to it but behaves differently. +So, to implement portable application you should assume nothing about the behavior in the kernel. +Using man:getaddrinfo[3] is the safest way. +Port number space and wildcard bind issues were discussed in detail on ipv6imp mailing list, in mid March 1999 and it looks that there is no concrete consensus (means, up to implementers). +You may want to check the mailing list archives. If a server application would like to accept IPv4 and IPv6 connections, there will be two alternatives. -One is using AF_INET and AF_INET6 socket (you will need two sockets). Use man:getaddrinfo[3] with AI_PASSIVE into ai_flags, and man:socket[2] and man:bind[2] to all the addresses returned. By opening multiple sockets, you can accept connections onto the socket with proper address family. IPv4 connections will be accepted by AF_INET socket, and IPv6 connections will be accepted by AF_INET6 socket. +One is using AF_INET and AF_INET6 socket (you will need two sockets). +Use man:getaddrinfo[3] with AI_PASSIVE into ai_flags, and man:socket[2] and man:bind[2] to all the addresses returned. +By opening multiple sockets, you can accept connections onto the socket with proper address family. +IPv4 connections will be accepted by AF_INET socket, and IPv6 connections will be accepted by AF_INET6 socket. -Another way is using one AF_INET6 wildcard bind socket. Use man:getaddrinfo[3] with AI_PASSIVE into ai_flags and with AF_INET6 into ai_family, and set the 1st argument hostname to NULL. And man:socket[2] and man:bind[2] to the address returned. (should be IPv6 unspecified addr). You can accept either of IPv4 and IPv6 packet via this one socket. +Another way is using one AF_INET6 wildcard bind socket. +Use man:getaddrinfo[3] with AI_PASSIVE into ai_flags and with AF_INET6 into ai_family, and set the 1st argument hostname to NULL. +And man:socket[2] and man:bind[2] to the address returned. +(should be IPv6 unspecified addr). +You can accept either of IPv4 and IPv6 packet via this one socket. -To support only IPv6 traffic on AF_INET6 wildcard binded socket portably, always check the peer address when a connection is made toward AF_INET6 listening socket. If the address is IPv4 mapped address, you may want to reject the connection. You can check the condition by using IN6_IS_ADDR_V4MAPPED() macro. +To support only IPv6 traffic on AF_INET6 wildcard binded socket portably, always check the peer address when a connection is made toward AF_INET6 listening socket. +If the address is IPv4 mapped address, you may want to reject the connection. +You can check the condition by using IN6_IS_ADDR_V4MAPPED() macro. To resolve this issue more easily, there is system dependent man:setsockopt[2] option, IPV6_BINDV6ONLY, used like below. @@ -421,15 +548,23 @@ Advise to application implementers: to implement a portable IPv6 application (wh * If you would like to connect to destination, use man:getaddrinfo[3] and try all the destination returned, like man:telnet[1] does. * Some of the IPv6 stack is shipped with buggy man:getaddrinfo[3]. Ship a minimal working version with your application and use that as last resort. -If you would like to use AF_INET6 socket for both IPv4 and IPv6 outgoing connection, you will need to use man:getipnodebyname[3]. When you would like to update your existing application to be IPv6 aware with minimal effort, this approach might be chosen. But please note that it is a temporal solution, because man:getipnodebyname[3] itself is not recommended as it does not handle scoped IPv6 addresses at all. For IPv6 name resolution, man:getaddrinfo[3] is the preferred API. So you should rewrite your application to use man:getaddrinfo[3], when you get the time to do it. +If you would like to use AF_INET6 socket for both IPv4 and IPv6 outgoing connection, you will need to use man:getipnodebyname[3]. +When you would like to update your existing application to be IPv6 aware with minimal effort, this approach might be chosen. +But please note that it is a temporal solution, because man:getipnodebyname[3] itself is not recommended as it does not handle scoped IPv6 addresses at all. +For IPv6 name resolution, man:getaddrinfo[3] is the preferred API. +So you should rewrite your application to use man:getaddrinfo[3], when you get the time to do it. -When writing applications that make outgoing connections, story goes much simpler if you treat AF_INET and AF_INET6 as totally separate address family. {set,get}sockopt issue goes simpler, DNS issue will be made simpler. We do not recommend you to rely upon IPv4 mapped address. +When writing applications that make outgoing connections, story goes much simpler if you treat AF_INET and AF_INET6 as totally separate address family. +{set,get}sockopt issue goes simpler, DNS issue will be made simpler. +We do not recommend you to rely upon IPv4 mapped address. ===== unified tcp and inpcb code -FreeBSD 4.x uses shared tcp code between IPv4 and IPv6 (from sys/netinet/tcp*) and separate udp4/6 code. It uses unified inpcb structure. +FreeBSD 4.x uses shared tcp code between IPv4 and IPv6 (from sys/netinet/tcp*) and separate udp4/6 code. +It uses unified inpcb structure. -The platform can be configured to support IPv4 mapped address. Kernel configuration is summarized as follows: +The platform can be configured to support IPv4 mapped address. +Kernel configuration is summarized as follows: * By default, AF_INET6 socket will grab IPv4 connections in certain condition, and can initiate connection to IPv4 destination embedded in IPv4 mapped IPv6 address. * You can disable it on entire system with sysctl like below. @@ -438,7 +573,8 @@ The platform can be configured to support IPv4 mapped address. Kernel configurat ====== Listening Side -Each socket can be configured to support special AF_INET6 wildcard bind (enabled by default). You can disable it on each socket basis with man:setsockopt[2] like below. +Each socket can be configured to support special AF_INET6 wildcard bind (enabled by default). +You can disable it on each socket basis with man:setsockopt[2] like below. [.programlisting] .... @@ -461,7 +597,10 @@ FreeBSD 4.x supports outgoing connection to IPv4 mapped address (::ffff:10.1.1.1 ==== sockaddr_storage -When RFC2553 was about to be finalized, there was discussion on how struct sockaddr_storage members are named. One proposal is to prepend "__" to the members (like "__ss_len") as they should not be touched. The other proposal was not to prepend it (like "ss_len") as we need to touch those members directly. There was no clear consensus on it. +When RFC2553 was about to be finalized, there was discussion on how struct sockaddr_storage members are named. +One proposal is to prepend "__" to the members (like "__ss_len") as they should not be touched. +The other proposal was not to prepend it (like "ss_len") as we need to touch those members directly. +There was no clear consensus on it. As a result, RFC2553 defines struct sockaddr_storage as follows: @@ -489,7 +628,8 @@ In December 1999, it was agreed that RFC2553bis should pick the latter (XNET) de Current implementation conforms to XNET definition, based on RFC2553bis discussion. -If you look at multiple IPv6 implementations, you will be able to see both definitions. As an userland programmer, the most portable way of dealing with it is to: +If you look at multiple IPv6 implementations, you will be able to see both definitions. +As an userland programmer, the most portable way of dealing with it is to: . ensure ss_family and/or ss_len are available on the platform, by using GNU autoconf, . have -Dss_family=__ss_family to unify all occurrences (including header file) into __ss_family, or @@ -508,9 +648,11 @@ Now following two items are required to be supported by standard drivers: . mbuf clustering requirement. In this stable release, we changed MINCLSIZE into MHLEN+1 for all the operating systems in order to make all the drivers behave as we expect. . multicast. If man:ifmcstat[8] yields no multicast group for a interface, that interface has to be patched. -If any of the drivers do not support the requirements, then the drivers cannot be used for IPv6 and/or IPsec communication. If you find any problem with your card using IPv6/IPsec, then, please report it to the {freebsd-bugs}. +If any of the drivers do not support the requirements, then the drivers cannot be used for IPv6 and/or IPsec communication. +If you find any problem with your card using IPv6/IPsec, then, please report it to the {freebsd-bugs}. -(NOTE: In the past we required all PCMCIA drivers to have a call to in6_ifattach(). We have no such requirement any more) +(NOTE: In the past we required all PCMCIA drivers to have a call to in6_ifattach(). +We have no such requirement any more) === Translator @@ -532,23 +674,38 @@ IPsec is mainly organized by three components. ==== Policy Management -The kernel implements experimental policy management code. There are two way to manage security policy. One is to configure per-socket policy using man:setsockopt[2]. In this cases, policy configuration is described in man:ipsec_set_policy[3]. The other is to configure kernel packet filter-based policy using PF_KEY interface, via man:setkey[8]. +The kernel implements experimental policy management code. +There are two way to manage security policy. +One is to configure per-socket policy using man:setsockopt[2]. +In this cases, policy configuration is described in man:ipsec_set_policy[3]. +The other is to configure kernel packet filter-based policy using PF_KEY interface, via man:setkey[8]. The policy entry is not re-ordered with its indexes, so the order of entry when you add is very significant. ==== Key Management -The key management code implemented in this kit (sys/netkey) is a home-brew PFKEY v2 implementation. This conforms to RFC2367. +The key management code implemented in this kit (sys/netkey) is a home-brew PFKEY v2 implementation. +This conforms to RFC2367. -The home-brew IKE daemon, "racoon" is included in the kit (kame/kame/racoon). Basically you will need to run racoon as daemon, then set up a policy to require keys (like `ping -P 'out ipsec esp/transport//use'`). The kernel will contact racoon daemon as necessary to exchange keys. +The home-brew IKE daemon, "racoon" is included in the kit (kame/kame/racoon). +Basically you will need to run racoon as daemon, then set up a policy to require keys (like `ping -P 'out ipsec esp/transport//use'`). +The kernel will contact racoon daemon as necessary to exchange keys. ==== AH and ESP Handling -IPsec module is implemented as "hooks" to the standard IPv4/IPv6 processing. When sending a packet, ip{,6}_output() checks if ESP/AH processing is required by checking if a matching SPD (Security Policy Database) is found. If ESP/AH is needed, {esp,ah}{4,6}_output() will be called and mbuf will be updated accordingly. When a packet is received, {esp,ah}4_input() will be called based on protocol number, i.e., (*inetsw[proto])(). {esp,ah}4_input() will decrypt/check authenticity of the packet, and strips off daisy-chained header and padding for ESP/AH. It is safe to strip off the ESP/AH header on packet reception, since we will never use the received packet in "as is" form. +IPsec module is implemented as "hooks" to the standard IPv4/IPv6 processing. +When sending a packet, ip{,6}_output() checks if ESP/AH processing is required by checking if a matching SPD (Security Policy Database) is found. +If ESP/AH is needed, {esp,ah}{4,6}_output() will be called and mbuf will be updated accordingly. +When a packet is received, {esp,ah}4_input() will be called based on protocol number, i.e., (*inetsw[proto])(). +{esp,ah}4_input() will decrypt/check authenticity of the packet, and strips off daisy-chained header and padding for ESP/AH. +It is safe to strip off the ESP/AH header on packet reception, since we will never use the received packet in "as is" form. -By using ESP/AH, TCP4/6 effective data segment size will be affected by extra daisy-chained headers inserted by ESP/AH. Our code takes care of the case. +By using ESP/AH, TCP4/6 effective data segment size will be affected by extra daisy-chained headers inserted by ESP/AH. +Our code takes care of the case. -Basic crypto functions can be found in directory "sys/crypto". ESP/AH transform are listed in {esp,ah}_core.c with wrapper functions. If you wish to add some algorithm, add wrapper function in {esp,ah}_core.c, and add your crypto algorithm code into sys/crypto. +Basic crypto functions can be found in directory "sys/crypto". +ESP/AH transform are listed in {esp,ah}_core.c with wrapper functions. +If you wish to add some algorithm, add wrapper function in {esp,ah}_core.c, and add your crypto algorithm code into sys/crypto. Tunnel mode is partially supported in this release, with the following restrictions: @@ -562,7 +719,8 @@ The IPsec code in the kernel conforms (or, tries to conform) to the following st "old IPsec" specification documented in [.filename]#rfc182[5-9].txt# -"new IPsec" specification documented in [.filename]#rfc240[1-6].txt#, [.filename]#rfc241[01].txt#, [.filename]#rfc2451.txt# and [.filename]#draft-mcdonald-simple-ipsec-api-01.txt# (draft expired, but you can take from link:ftp://ftp.kame.net/pub/internet-drafts/[ ftp://ftp.kame.net/pub/internet-drafts/]). (NOTE: IKE specifications, [.filename]#rfc241[7-9].txt# are implemented in userland, as "racoon" IKE daemon) +"new IPsec" specification documented in [.filename]#rfc240[1-6].txt#, [.filename]#rfc241[01].txt#, [.filename]#rfc2451.txt# and [.filename]#draft-mcdonald-simple-ipsec-api-01.txt# (draft expired, but you can take from link:ftp://ftp.kame.net/pub/internet-drafts/[ ftp://ftp.kame.net/pub/internet-drafts/]). +(NOTE: IKE specifications, [.filename]#rfc241[7-9].txt# are implemented in userland, as "racoon" IKE daemon) Currently supported algorithms are: @@ -608,16 +766,21 @@ The following algorithms are NOT supported: ** HMAC MD5 with 128bit crypto checksum + 64bit replay prevention ([.filename]#rfc2085.txt#) ** keyed SHA1 with 160bit crypto checksum + 32bit padding ([.filename]#rfc1852.txt#) -IPsec (in kernel) and IKE (in userland as "racoon") has been tested at several interoperability test events, and it is known to interoperate with many other implementations well. Also, current IPsec implementation as quite wide coverage for IPsec crypto algorithms documented in RFC (we cover algorithms without intellectual property issues only). +IPsec (in kernel) and IKE (in userland as "racoon") has been tested at several interoperability test events, and it is known to interoperate with many other implementations well. +Also, current IPsec implementation as quite wide coverage for IPsec crypto algorithms documented in RFC (we cover algorithms without intellectual property issues only). [[ipsec-ecn]] ==== ECN Consideration on IPsec Tunnels ECN-friendly IPsec tunnel is supported as described in [.filename]#draft-ipsec-ecn-00.txt#. -Normal IPsec tunnel is described in RFC2401. On encapsulation, IPv4 TOS field (or, IPv6 traffic class field) will be copied from inner IP header to outer IP header. On decapsulation outer IP header will be simply dropped. The decapsulation rule is not compatible with ECN, since ECN bit on the outer IP TOS/traffic class field will be lost. +Normal IPsec tunnel is described in RFC2401. +On encapsulation, IPv4 TOS field (or, IPv6 traffic class field) will be copied from inner IP header to outer IP header. +On decapsulation outer IP header will be simply dropped. +The decapsulation rule is not compatible with ECN, since ECN bit on the outer IP TOS/traffic class field will be lost. -To make IPsec tunnel ECN-friendly, we should modify encapsulation and decapsulation procedure. This is described in http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt[ http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt], chapter 3. +To make IPsec tunnel ECN-friendly, we should modify encapsulation and decapsulation procedure. +This is described in http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt[ http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt], chapter 3. IPsec tunnel implementation can give you three behaviors, by setting net.inet.ipsec.ecn (or net.inet6.ipsec6.ecn) to some value: @@ -662,6 +825,7 @@ http://www.aciri.org/floyd/papers/draft-ipsec-ecn-00.txt[ http://www.aciri.org/f ==== Interoperability -Here are (some of) platforms that KAME code have tested IPsec/IKE interoperability in the past. Note that both ends may have modified their implementation, so use the following list just for reference purposes. +Here are (some of) platforms that KAME code have tested IPsec/IKE interoperability in the past. +Note that both ends may have modified their implementation, so use the following list just for reference purposes. Altiga, Ashley-laurent (vpcom.com), Data Fellows (F-Secure), Ericsson ACC, FreeS/WAN, HITACHI, IBM AIX(R), IIJ, Intel, Microsoft(R) Windows NT(R), NIST (linux IPsec + plutoplus), Netscreen, OpenBSD, RedCreek, Routerware, SSH, Secure Computing, Soliton, Toshiba, VPNet, Yamaha RT100i diff --git a/documentation/content/en/books/developers-handbook/kernelbuild/_index.adoc b/documentation/content/en/books/developers-handbook/kernelbuild/_index.adoc index e7fb85fa07..bf127de265 100644 --- a/documentation/content/en/books/developers-handbook/kernelbuild/_index.adoc +++ b/documentation/content/en/books/developers-handbook/kernelbuild/_index.adoc @@ -32,19 +32,23 @@ include::shared/en/urls.adoc[] toc::[] -Being a kernel developer requires understanding of the kernel build process. To debug the FreeBSD kernel it is required to be able to build one. There are two known ways to do so: +Being a kernel developer requires understanding of the kernel build process. +To debug the FreeBSD kernel it is required to be able to build one. +There are two known ways to do so: The supported procedure to build and install a kernel is documented in the link:{handbook}#kernelconfig-building[Building and Installing a Custom Kernel] chapter of the FreeBSD Handbook. [NOTE] ==== -It is supposed that the reader of this chapter is familiar with the information described in the link:{handbook}#kernelconfig-building[Building and Installing a Custom Kernel] chapter of the FreeBSD Handbook. If this is not the case, please read through the above mentioned chapter to understand how the build process works. +It is supposed that the reader of this chapter is familiar with the information described in the link:{handbook}#kernelconfig-building[Building and Installing a Custom Kernel] chapter of the FreeBSD Handbook. +If this is not the case, please read through the above mentioned chapter to understand how the build process works. ==== [[kernelbuild-traditional]] == Building the Faster but Brittle Way -Building the kernel this way may be useful when working on the kernel code and it may actually be faster than the documented procedure when only a single option or two were tweaked in the kernel configuration file. On the other hand, it might lead to unexpected kernel build breakage. +Building the kernel this way may be useful when working on the kernel code and it may actually be faster than the documented procedure when only a single option or two were tweaked in the kernel configuration file. +On the other hand, it might lead to unexpected kernel build breakage. [.procedure] . Run man:config[8] to generate the kernel source code: diff --git a/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc b/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc index daea455841..817ef1f7de 100644 --- a/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc +++ b/documentation/content/en/books/developers-handbook/kerneldebug/_index.adoc @@ -38,13 +38,20 @@ toc::[] [[kerneldebug-obtain]] == Obtaining a Kernel Crash Dump -When running a development kernel (e.g., FreeBSD-CURRENT), such as a kernel under extreme conditions (e.g., very high load averages, tens of thousands of connections, exceedingly high number of concurrent users, hundreds of man:jail[8]s, etc.), or using a new feature or device driver on FreeBSD-STABLE (e.g., PAE), sometimes a kernel will panic. In the event that it does, this chapter will demonstrate how to extract useful information out of a crash. +When running a development kernel (e.g., FreeBSD-CURRENT), such as a kernel under extreme conditions (e.g., very high load averages, tens of thousands of connections, exceedingly high number of concurrent users, hundreds of man:jail[8]s, etc.), +or using a new feature or device driver on FreeBSD-STABLE (e.g., PAE), sometimes a kernel will panic. +In the event that it does, this chapter will demonstrate how to extract useful information out of a crash. -A system reboot is inevitable once a kernel panics. Once a system is rebooted, the contents of a system's physical memory (RAM) is lost, as well as any bits that are on the swap device before the panic. To preserve the bits in physical memory, the kernel makes use of the swap device as a temporary place to store the bits that are in RAM across a reboot after a crash. In doing this, when FreeBSD boots after a crash, a kernel image can now be extracted and debugging can take place. +A system reboot is inevitable once a kernel panics. +Once a system is rebooted, the contents of a system's physical memory (RAM) is lost, as well as any bits that are on the swap device before the panic. +To preserve the bits in physical memory, the kernel makes use of the swap device as a temporary place to store the bits that are in RAM across a reboot after a crash. +In doing this, when FreeBSD boots after a crash, a kernel image can now be extracted and debugging can take place. [NOTE] ==== -A swap device that has been configured as a dump device still acts as a swap device. Dumps to non-swap devices (such as tapes or CDRWs, for example) are not supported at this time. A "swap device" is synonymous with a "swap partition." +A swap device that has been configured as a dump device still acts as a swap device. +Dumps to non-swap devices (such as tapes or CDRWs, for example) are not supported at this time. +A "swap device" is synonymous with a "swap partition." ==== Several types of kernel crash dumps are available: @@ -63,11 +70,15 @@ Minidumps are the default dump type as of FreeBSD 7.0, and in most cases will ca [[config-dumpdev]] === Configuring the Dump Device -Before the kernel will dump the contents of its physical memory to a dump device, a dump device must be configured. A dump device is specified by using the man:dumpon[8] command to tell the kernel where to save kernel crash dumps. The man:dumpon[8] program must be called after the swap partition has been configured with man:swapon[8]. This is normally handled by setting the `dumpdev` variable in man:rc.conf[5] to the path of the swap device (the recommended way to extract a kernel dump) or `AUTO` to use the first configured swap device. The default for `dumpdev` is `AUTO` in HEAD, and changed to `NO` on RELENG_* branches (except for RELENG_7, which was left set to `AUTO`). On FreeBSD 9.0-RELEASE and later versions, bsdinstall will ask whether crash dumps should be enabled on the target system during the install process. +Before the kernel will dump the contents of its physical memory to a dump device, a dump device must be configured. +A dump device is specified by using the man:dumpon[8] command to tell the kernel where to save kernel crash dumps. +The man:dumpon[8] program must be called after the swap partition has been configured with man:swapon[8]. +This is normally handled by setting the `dumpdev` variable in man:rc.conf[5] to the path of the swap device (the recommended way to extract a kernel dump) or `AUTO` to use the first configured swap device. +The default for `dumpdev` is `AUTO` in HEAD, and changed to `NO` on RELENG_* branches (except for RELENG_7, which was left set to `AUTO`). +On FreeBSD 9.0-RELEASE and later versions, bsdinstall will ask whether crash dumps should be enabled on the target system during the install process. [TIP] ==== - Check [.filename]#/etc/fstab# or man:swapinfo[8] for a list of swap devices. ==== @@ -87,16 +98,23 @@ Also, remember that the contents of [.filename]#/var/crash# is sensitive and ver [[extract-dump]] === Extracting a Kernel Dump -Once a dump has been written to a dump device, the dump must be extracted before the swap device is mounted. To extract a dump from a dump device, use the man:savecore[8] program. If `dumpdev` has been set in man:rc.conf[5], man:savecore[8] will be called automatically on the first multi-user boot after the crash and before the swap device is mounted. The location of the extracted core is placed in the man:rc.conf[5] value `dumpdir`, by default [.filename]#/var/crash# and will be named [.filename]#vmcore.0#. +Once a dump has been written to a dump device, the dump must be extracted before the swap device is mounted. +To extract a dump from a dump device, use the man:savecore[8] program. +If `dumpdev` has been set in man:rc.conf[5], man:savecore[8] will be called automatically on the first multi-user boot after the crash and before the swap device is mounted. +The location of the extracted core is placed in the man:rc.conf[5] value `dumpdir`, by default [.filename]#/var/crash# and will be named [.filename]#vmcore.0#. -In the event that there is already a file called [.filename]#vmcore.0# in [.filename]#/var/crash# (or whatever `dumpdir` is set to), the kernel will increment the trailing number for every crash to avoid overwriting an existing [.filename]#vmcore# (e.g., [.filename]#vmcore.1#). man:savecore[8] will always create a symbolic link to named [.filename]#vmcore.last# in [.filename]#/var/crash# after a dump is saved. This symbolic link can be used to locate the name of the most recent dump. +In the event that there is already a file called [.filename]#vmcore.0# in [.filename]#/var/crash# (or whatever `dumpdir` is set to), the kernel will increment the trailing number for every crash to avoid overwriting an existing [.filename]#vmcore# (e.g., [.filename]#vmcore.1#). +man:savecore[8] will always create a symbolic link to named [.filename]#vmcore.last# in [.filename]#/var/crash# after a dump is saved. +This symbolic link can be used to locate the name of the most recent dump. -The man:crashinfo[8] utility generates a text file containing a summary of information from a full memory dump or minidump. If `dumpdev` has been set in man:rc.conf[5], man:crashinfo[8] will be invoked automatically after man:savecore[8]. The output is saved to a file in `dumpdir` named [.filename]#core.txt.N#. +The man:crashinfo[8] utility generates a text file containing a summary of information from a full memory dump or minidump. +If `dumpdev` has been set in man:rc.conf[5], man:crashinfo[8] will be invoked automatically after man:savecore[8]. +The output is saved to a file in `dumpdir` named [.filename]#core.txt.N#. [TIP] ==== - -If you are testing a new kernel but need to boot a different one in order to get your system up and running again, boot it only into single user mode using the `-s` flag at the boot prompt, and then perform the following steps: +If you are testing a new kernel but need to boot a different one in order to get your system up and running again, +boot it only into single user mode using the `-s` flag at the boot prompt, and then perform the following steps: [source,bash] .... @@ -106,12 +124,16 @@ If you are testing a new kernel but need to boot a different one in order to get # exit # exit to multi-user .... -This instructs man:savecore[8] to extract a kernel dump from [.filename]#/dev/ad0s1b# and place the contents in [.filename]#/var/crash#. Do not forget to make sure the destination directory [.filename]#/var/crash# has enough space for the dump. Also, do not forget to specify the correct path to your swap device as it is likely different than [.filename]#/dev/ad0s1b#! +This instructs man:savecore[8] to extract a kernel dump from [.filename]#/dev/ad0s1b# and place the contents in [.filename]#/var/crash#. +Do not forget to make sure the destination directory [.filename]#/var/crash# has enough space for the dump. +Also, do not forget to specify the correct path to your swap device as it is likely different than [.filename]#/dev/ad0s1b#! ==== === Testing Kernel Dump Configuration -The kernel includes a man:sysctl[8] node that requests a kernel panic. This can be used to verify that your system is properly configured to save kernel crash dumps. You may wish to remount existing file systems as read-only in single user mode before triggering the crash to avoid data loss. +The kernel includes a man:sysctl[8] node that requests a kernel panic. +This can be used to verify that your system is properly configured to save kernel crash dumps. +You may wish to remount existing file systems as read-only in single user mode before triggering the crash to avoid data loss. [source,bash] .... @@ -131,7 +153,9 @@ After rebooting, your system should save a dump in [.filename]#/var/crash# along [NOTE] ==== -This section covers man:kgdb[1]. The latest version is included in the package:devel/gdb[]. An older version is also present in FreeBSD 11 and earlier. +This section covers man:kgdb[1]. +The latest version is included in the package:devel/gdb[]. +An older version is also present in FreeBSD 11 and earlier. ==== To enter into the debugger and begin getting information from the dump, start kgdb: @@ -141,14 +165,16 @@ To enter into the debugger and begin getting information from the dump, start kg # kgdb -n N .... -Where _N_ is the suffix of the [.filename]#vmcore.N# to examine. To open the most recent dump use: +Where _N_ is the suffix of the [.filename]#vmcore.N# to examine. +To open the most recent dump use: [source,bash] .... # kgdb -n last .... -Normally, man:kgdb[1] should be able to locate the kernel running at the time the dump was generated. If it is not able to locate the correct kernel, pass the pathname of the kernel and dump as two arguments to kgdb: +Normally, man:kgdb[1] should be able to locate the kernel running at the time the dump was generated. +If it is not able to locate the correct kernel, pass the pathname of the kernel and dump as two arguments to kgdb: [source,bash] .... @@ -157,7 +183,12 @@ Normally, man:kgdb[1] should be able to locate the kernel running at the time th You can debug the crash dump using the kernel sources just like you can for any other program. -This dump is from a 5.2-BETA kernel and the crash comes from deep within the kernel. The output below has been modified to include line numbers on the left. This first trace inspects the instruction pointer and obtains a back trace. The address that is used on line 41 for the `list` command is the instruction pointer and can be found on line 17. Most developers will request having at least this information sent to them if you are unable to debug the problem yourself. If, however, you do solve the problem, make sure that your patch winds its way into the source tree via a problem report, mailing lists, or by being able to commit it! +This dump is from a 5.2-BETA kernel and the crash comes from deep within the kernel. +The output below has been modified to include line numbers on the left. +This first trace inspects the instruction pointer and obtains a back trace. +The address that is used on line 41 for the `list` command is the instruction pointer and can be found on line 17. +Most developers will request having at least this information sent to them if you are unable to debug the problem yourself. +If, however, you do solve the problem, make sure that your patch winds its way into the source tree via a problem report, mailing lists, or by being able to commit it! [source,bash] .... @@ -255,16 +286,19 @@ This dump is from a 5.2-BETA kernel and the crash comes from deep within the ker [TIP] ==== - -If your system is crashing regularly and you are running out of disk space, deleting old [.filename]#vmcore# files in [.filename]#/var/crash# could save a considerable amount of disk space! +If your system is crashing regularly and you are running out of disk space, +deleting old [.filename]#vmcore# files in [.filename]#/var/crash# could save a considerable amount of disk space! ==== [[kerneldebug-online-ddb]] == On-Line Kernel Debugging Using DDB -While `kgdb` as an off-line debugger provides a very high level of user interface, there are some things it cannot do. The most important ones being breakpointing and single-stepping kernel code. +While `kgdb` as an off-line debugger provides a very high level of user interface, there are some things it cannot do. +The most important ones being breakpointing and single-stepping kernel code. -If you need to do low-level debugging on your kernel, there is an on-line debugger available called DDB. It allows setting of breakpoints, single-stepping kernel functions, examining and changing kernel variables, etc. However, it cannot access kernel source files, and only has access to the global and static symbols, not to the full debug information like `kgdb` does. +If you need to do low-level debugging on your kernel, there is an on-line debugger available called DDB. +It allows setting of breakpoints, single-stepping kernel functions, examining and changing kernel variables, etc. +However, it cannot access kernel source files, and only has access to the global and static symbols, not to the full debug information like `kgdb` does. To configure your kernel to include DDB, add the options [.programlisting] @@ -277,20 +311,32 @@ options KDB options DDB .... -to your config file, and rebuild. (See link:{handbook}/[The FreeBSD Handbook] for details on configuring the FreeBSD kernel). +to your config file, and rebuild. +(See link:{handbook}/[The FreeBSD Handbook] for details on configuring the FreeBSD kernel). -Once your DDB kernel is running, there are several ways to enter DDB. The first, and earliest way is to use the boot flag `-d`. The kernel will start up in debug mode and enter DDB prior to any device probing. Hence you can even debug the device probe/attach functions. To use this, exit the loader's boot menu and enter `boot -d` at the loader prompt. +Once your DDB kernel is running, there are several ways to enter DDB. +The first, and earliest way is to use the boot flag `-d`. +The kernel will start up in debug mode and enter DDB prior to any device probing. +Hence you can even debug the device probe/attach functions. +To use this, exit the loader's boot menu and enter `boot -d` at the loader prompt. -The second scenario is to drop to the debugger once the system has booted. There are two simple ways to accomplish this. If you would like to break to the debugger from the command prompt, simply type the command: +The second scenario is to drop to the debugger once the system has booted. +There are two simple ways to accomplish this. +If you would like to break to the debugger from the command prompt, simply type the command: [source,bash] .... # sysctl debug.kdb.enter=1 .... -Alternatively, if you are at the system console, you may use a hot-key on the keyboard. The default break-to-debugger sequence is kbd:[Ctrl+Alt+ESC]. For syscons, this sequence can be remapped and some of the distributed maps out there do this, so check to make sure you know the right sequence to use. There is an option available for serial consoles that allows the use of a serial line BREAK on the console line to enter DDB (`options BREAK_TO_DEBUGGER` in the kernel config file). It is not the default since there are a lot of serial adapters around that gratuitously generate a BREAK condition, for example when pulling the cable. +Alternatively, if you are at the system console, you may use a hot-key on the keyboard. +The default break-to-debugger sequence is kbd:[Ctrl+Alt+ESC]. +For syscons, this sequence can be remapped and some of the distributed maps out there do this, so check to make sure you know the right sequence to use. +There is an option available for serial consoles that allows the use of a serial line BREAK on the console line to enter DDB (`options BREAK_TO_DEBUGGER` in the kernel config file). +It is not the default since there are a lot of serial adapters around that gratuitously generate a BREAK condition, for example when pulling the cable. -The third way is that any panic condition will branch to DDB if the kernel is configured to use it. For this reason, it is not wise to configure a kernel with DDB for a machine running unattended. +The third way is that any panic condition will branch to DDB if the kernel is configured to use it. +For this reason, it is not wise to configure a kernel with DDB for a machine running unattended. To obtain the unattended functionality, add: @@ -301,14 +347,17 @@ options KDB_UNATTENDED to the kernel configuration file and rebuild/reinstall. -The DDB commands roughly resemble some `gdb` commands. The first thing you probably need to do is to set a breakpoint: +The DDB commands roughly resemble some `gdb` commands. +The first thing you probably need to do is to set a breakpoint: [source,bash] .... break function-name address .... -Numbers are taken hexadecimal by default, but to make them distinct from symbol names; hexadecimal numbers starting with the letters `a-f` need to be preceded with `0x` (this is optional for other numbers). Simple expressions are allowed, for example: `function-name + 0x103`. +Numbers are taken hexadecimal by default, but to make them distinct from symbol names; +hexadecimal numbers starting with the letters `a-f` need to be preceded with `0x` (this is optional for other numbers). +Simple expressions are allowed, for example: `function-name + 0x103`. To exit the debugger and continue execution, type: @@ -334,7 +383,8 @@ If you want to remove a breakpoint, use del address-expression .... -The first form will be accepted immediately after a breakpoint hit, and deletes the current breakpoint. The second form can remove any breakpoint, but you need to specify the exact address; this can be obtained from: +The first form will be accepted immediately after a breakpoint hit, and deletes the current breakpoint. +The second form can remove any breakpoint, but you need to specify the exact address; this can be obtained from: [source,bash] .... @@ -364,7 +414,8 @@ This will step into functions, but you can make DDB trace them until the matchin [NOTE] ==== -This is different from ``gdb``'s `next` statement; it is like ``gdb``'s `finish`. Pressing kbd:[n] more than once will cause a continue. +This is different from ``gdb``'s `next` statement; it is like ``gdb``'s `finish`. +Pressing kbd:[n] more than once will cause a continue. ==== To examine data from memory, use (for example): @@ -377,7 +428,9 @@ To examine data from memory, use (for example): x/s stringbuf .... -for word/halfword/byte access, and hexadecimal/decimal/character/ string display. The number after the comma is the object count. To display the next 0x10 items, simply use: +for word/halfword/byte access, and hexadecimal/decimal/character/ string display. +The number after the comma is the object count. +To display the next 0x10 items, simply use: [source,bash] .... *** 4742 LINES SKIPPED *** From owner-dev-commits-doc-all@freebsd.org Sun Jun 6 14:30:57 2021 Return-Path: Delivered-To: dev-commits-doc-all@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D98A965FC8B for ; Sun, 6 Jun 2021 14:30:57 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Fyf7P5tfTz4rx7; Sun, 6 Jun 2021 14:30:57 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org (gitrepo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:5]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B272424FD5; Sun, 6 Jun 2021 14:30:57 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.16.1/8.16.1) with ESMTP id 156EUvnM055992; Sun, 6 Jun 2021 14:30:57 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 156EUvJT055991; Sun, 6 Jun 2021 14:30:57 GMT (envelope-from git) Date: Sun, 6 Jun 2021 14:30:57 GMT Message-Id: <202106061430.156EUvJT055991@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: "Danilo G. Baio" Subject: git: 03221c34cf - main - website/de: Remove duplicate pages MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: dbaio X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 03221c34cf6bf2724e7fdb55e903cf82c462a83e Auto-Submitted: auto-generated X-BeenThere: dev-commits-doc-all@freebsd.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: Commit messages for all branches of the doc repository List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 06 Jun 2021 14:30:57 -0000 The branch main has been updated by dbaio: URL: https://cgit.FreeBSD.org/doc/commit/?id=03221c34cf6bf2724e7fdb55e903cf82c462a83e commit 03221c34cf6bf2724e7fdb55e903cf82c462a83e Author: Danilo G. Baio AuthorDate: 2021-06-06 14:25:16 +0000 Commit: Danilo G. Baio CommitDate: 2021-06-06 14:26:55 +0000 website/de: Remove duplicate pages WARN 2021/06/06 12:35:26 Duplicate target paths: /workspace/doc/website/public/de/community/index.html (2), /workspace/doc/website/public/de/platforms/ia64/index.html (2) These indexes are stored in: website/content/de/community/_index.adoc website/content/de/platforms/ia64/_index.adoc --- website/content/de/community.adoc | 14 -------------- website/content/de/platforms/ia64.adoc | 8 -------- 2 files changed, 22 deletions(-) diff --git a/website/content/de/community.adoc b/website/content/de/community.adoc deleted file mode 100644 index b22d4e18c9..0000000000 --- a/website/content/de/community.adoc +++ /dev/null @@ -1,14 +0,0 @@ -]> &nav.community; - -Es gibt mehr als 100 link:&base;/community/mailinglists.html[Mailinglisten], dutzende https://forums.FreeBSD.org/[Foren] sowie diverse https://www.FreeBSD.org/doc/de_DE.ISO8859-1/books/handbook/eresources-news.html[Newsgroups]. Dazu kommen mehr als 91 https://www.FreeBSD.org/usergroups.html[User Groups] in 40 Ländern. Zusätzlich existiert eine aktive link:&base;/community/irc.html[IRC]-Gemeinde. Außerdem betreiben die FreeBSD-Entwickler gemeinsam mit einigen der wichtigsten Unterstützer ein https://wiki.FreeBSD.org/[Wiki], das Informationen zur FreeBSD-Entwicklung und zu diversen Projekten enthält. - -Letztes Jahr gab es insgesamt 9 FreeBSD-Veranstaltungen in 9 verschiedenen Ländern. Ein https://www.FreeBSD.org/events/events.ics[Kalender] sowie ein https://www.FreeBSD.org/events/rss.xml[RSS Feed] zu bevorstehenden FreeBSD-spezifischen Veranstaltungen sind auf der Seite https://www.FreeBSD.org/events/events.html[Veranstaltungen] verfügbar. Und nicht zuletzt gibt es dutzende Videos im Youtube-Channel https://www.youtube.com/bsdconferences[BSD Conferences]. - -== Soziale Netzwerke - -FreeBSD ist auf diversen sozialen Netzwerken vertreten. - -* Es gibt tausende Photos von Usergroup-Treffen, Konferenzen und Hackatons, die auf http://www.flickr.com[flickr] mit dem Tag 'https://flickr.com/search/?z=t&ss=2&w=all&q=freebsd&m=text[freebsd]' versehen wurden. -* Auf https://www.youtube.com[YouTube] gibt es hunderte Videos von Konferenzen, Präsentatitionen und Vorträgen, die sich auf https://www.youtube.com/results?search_query=freebsd[FreeBSD] beziehen. Weiters gibt es den Channel https://www.youtube.com/bsdconferences[BSD Conferences], über den Sie komplette Präsentationen von FreeBSD-Konferenzen verfolgen/ansehen können. -* Auf https://www.facebook.com[Facebook] gibt es die https://www.facebook.com/home.php#/group.php?gid=2204657214[FreeBSD Users Group], auf https://www.linkedin.com[LinkedIn] die https://www.linkedin.com/groups?gid=47628[FreeBSD Group]. -* Auf https://twitter.com[Twitter] können Sie beispielsweise https://twitter.com/freebsd[@freebsd], https://twitter.com/freebsdhelp[@freebsdhelp], https://twitter.com/freebsdblogs[@freebsdblogs] oder https://twitter.com/freebsdcore[@freebsdcore] folgen. diff --git a/website/content/de/platforms/ia64.adoc b/website/content/de/platforms/ia64.adoc deleted file mode 100644 index 96a9cec807..0000000000 --- a/website/content/de/platforms/ia64.adoc +++ /dev/null @@ -1,8 +0,0 @@ ---- -title: "FreeBSD/ia64 Project" -sidenav: developers ---- - -= FreeBSD/ia64 Project - -Die Seiten über die FreeBSD/ia64 Plattform wurden link:ia64[hierhin] hinverschoben. Bitte bringen Sie ihre Bookmarks auf den neuesten Stand.