+
+
+
+
+
+
2020
From owner-dev-commits-doc-all@freebsd.org Tue Jan 5 15: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 0FAB24E79CA
for ;
Tue, 5 Jan 2021 15: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 "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4D9GYp7430z4bmg;
Tue, 5 Jan 2021 15:26: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 E5A926994;
Tue, 5 Jan 2021 15:26: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 105FQcM0026130;
Tue, 5 Jan 2021 15:26:38 GMT (envelope-from git@gitrepo.freebsd.org)
Received: (from git@localhost)
by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 105FQceI026129;
Tue, 5 Jan 2021 15:26:38 GMT (envelope-from git)
Date: Tue, 5 Jan 2021 15:26:38 GMT
Message-Id: <202101051526.105FQceI026129@gitrepo.freebsd.org>
To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org
From: Neel Chauhan
Subject: git: 0c529cc483 - main - Set year for my commit bit as 2021
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Git-Committer: nc
X-Git-Repository: doc
X-Git-Refname: refs/heads/main
X-Git-Reftype: branch
X-Git-Commit: 0c529cc483b9c15cf4e7eeb2bd6a80effe426254
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, 05 Jan 2021 15:26:39 -0000
The branch main has been updated by nc (ports committer):
URL: https://cgit.FreeBSD.org/doc/commit/?id=0c529cc483b9c15cf4e7eeb2bd6a80effe426254
commit 0c529cc483b9c15cf4e7eeb2bd6a80effe426254
Author: Neel Chauhan
AuthorDate: 2021-01-05 15:26:44 +0000
Commit: Neel Chauhan
CommitDate: 2021-01-05 15:26:44 +0000
Set year for my commit bit as 2021
---
share/xml/news.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/share/xml/news.xml b/share/xml/news.xml
index e3f6ebd734..766e3d1dc6 100644
--- a/share/xml/news.xml
+++ b/share/xml/news.xml
@@ -28,7 +28,7 @@
$FreeBSD$
- 2020
+ 20211
From owner-dev-commits-doc-all@freebsd.org Wed Jan 6 17:50: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 88B0C4D88E7
for ;
Wed, 6 Jan 2021 17:50: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 "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4D9xhs3Q98z4dHt;
Wed, 6 Jan 2021 17:50: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 6829F221FE;
Wed, 6 Jan 2021 17:50: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 106Ho5QF068891;
Wed, 6 Jan 2021 17:50:05 GMT (envelope-from git@gitrepo.freebsd.org)
Received: (from git@localhost)
by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 106Ho5v6068884;
Wed, 6 Jan 2021 17:50:05 GMT (envelope-from git)
Date: Wed, 6 Jan 2021 17:50:05 GMT
Message-Id: <202101061750.106Ho5v6068884@gitrepo.freebsd.org>
To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org
From: Fernando ApesteguÃa
Subject: git: 345f2fd6a6 - main - Remove FuryBSD mentions from documentation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Git-Committer: fernape
X-Git-Repository: doc
X-Git-Refname: refs/heads/main
X-Git-Reftype: branch
X-Git-Commit: 345f2fd6a68802f1ffaa2dedbe719b02f70dea8c
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, 06 Jan 2021 17:50:05 -0000
The branch main has been updated by fernape (ports committer):
URL: https://cgit.FreeBSD.org/doc/commit/?id=345f2fd6a68802f1ffaa2dedbe719b02f70dea8c
commit 345f2fd6a68802f1ffaa2dedbe719b02f70dea8c
Author: Fernando ApesteguÃa
AuthorDate: 2020-12-31 18:29:15 +0000
Commit: Fernando ApesteguÃa
CommitDate: 2021-01-06 17:42:12 +0000
Remove FuryBSD mentions from documentation
Summary:
FuryBSD has been discontinued. Replace it with references to NomadBSD where
appropriate.
PR: 252058
Reported by: 0mp@FreeBSD.org
Approved by: 0mp@FreeBSD.org
Differential Revision: https://reviews.freebsd.org/D27869
---
en_US.ISO8859-1/books/faq/book.xml | 6 ++---
.../books/handbook/bsdinstall/chapter.xml | 6 ++---
en_US.ISO8859-1/books/handbook/desktop/chapter.xml | 7 +++---
.../books/handbook/introduction/chapter.xml | 26 +++++++++++-----------
en_US.ISO8859-1/books/handbook/x11/chapter.xml | 8 ++++---
en_US.ISO8859-1/htdocs/advocacy/myths.xml | 13 ++++++-----
en_US.ISO8859-1/htdocs/advocacy/whyusefreebsd.xml | 2 +-
en_US.ISO8859-1/htdocs/projects/newbies.xml | 15 +++++++------
en_US.ISO8859-1/htdocs/where.xml | 16 +++++++------
9 files changed, 53 insertions(+), 46 deletions(-)
diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml
index 546decb6c6..11ebe38646 100644
--- a/en_US.ISO8859-1/books/faq/book.xml
+++ b/en_US.ISO8859-1/books/faq/book.xml
@@ -228,11 +228,11 @@
environment will find &os; to be similar.
&windows; and &macos; users may be interested in instead
using FuryBSD,
+ xlink:href="https://ghostbsd.org/">GhostBSD,
GhostBSD
- or MidnightBSD
+ or NomadBSD
three &os;-based desktop distributions. Non-&unix; users
should expect to invest some additional time learning the
&unix; way of doing things. This FAQ
diff --git a/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml b/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
index 3a40f23413..c20e796c67 100644
--- a/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/bsdinstall/chapter.xml
@@ -136,10 +136,10 @@
Users who prefer to install &os; using a graphical
installer may be interested in
- FuryBSD,
- GhostBSD or
+ GhostBSD,
MidnightBSD.
+ xlink:href="https://www.midnightbsd.org">MidnightBSD or
+ NomadBSD.
After reading this chapter, you will know:
diff --git a/en_US.ISO8859-1/books/handbook/desktop/chapter.xml b/en_US.ISO8859-1/books/handbook/desktop/chapter.xml
index 9daff7a2f3..9fbd69a5dc 100644
--- a/en_US.ISO8859-1/books/handbook/desktop/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/desktop/chapter.xml
@@ -36,10 +36,11 @@
Users who prefer to install a pre-built desktop version
of FreeBSD rather than configuring one from scratch should
refer to FuryBSD,
- GhostBSD or
+ xlink:href="https://ghostbsd.org">GhostBSD,
MidnightBSD.
+ xlink:href="https://www.midnightbsd.org">MidnightBSD
+ or NomadBSD.
Readers of this chapter should know how to:
diff --git a/en_US.ISO8859-1/books/handbook/introduction/chapter.xml b/en_US.ISO8859-1/books/handbook/introduction/chapter.xml
index 34fec5a301..0df8e1f8ec 100644
--- a/en_US.ISO8859-1/books/handbook/introduction/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/introduction/chapter.xml
@@ -676,19 +676,6 @@
available.
-
- FuryBSD
-
- FuryBSD
- - is a brand new, open source &os; desktop.
- FuryBSD pays homage to desktop BSD projects of the past
- like PC-BSD and TrueOS with its graphical interface and
- adds additional tools like a live, hybrid USB/DVD image.
- FuryBSD is completely free to use and distributed under
- the BSD license.
-
-
MidnightBSD
@@ -701,6 +688,19 @@
more.
+
+ NomadBSD
+
+ NomadBSD
+ - is a persistent live system for USB flash
+ drives, based on &os;. Together with automatic hardware
+ detection and setup, it is configured to be used as a
+ desktop system that works out of the box, but can also be
+ used for data recovery, for educational purposes, or to
+ test &os;'s hardware compatibility.
+
+
pfSense
diff --git a/en_US.ISO8859-1/books/handbook/x11/chapter.xml b/en_US.ISO8859-1/books/handbook/x11/chapter.xml
index 0ebd1bb20f..41c753186e 100644
--- a/en_US.ISO8859-1/books/handbook/x11/chapter.xml
+++ b/en_US.ISO8859-1/books/handbook/x11/chapter.xml
@@ -39,10 +39,12 @@
Users who prefer an installation method that automatically
configures the &xorg; should refer
- to FuryBSD,
- GhostBSD or
+ to GhostBSD,
MidnightBSD.
+ xlink:href="https://www.midnightbsd.org">MidnightBSD
+ or
+ NomadBSD.For more information on the video hardware that
diff --git a/en_US.ISO8859-1/htdocs/advocacy/myths.xml b/en_US.ISO8859-1/htdocs/advocacy/myths.xml
index 753e6ca507..731f633fe8 100644
--- a/en_US.ISO8859-1/htdocs/advocacy/myths.xml
+++ b/en_US.ISO8859-1/htdocs/advocacy/myths.xml
@@ -163,12 +163,13 @@
storage. It is also a part of the FreeBSD source tree, see
/usr/src/tools/tools/nanobsd.
-
FuryBSD is a
- brand new, open source &os; desktop. FuryBSD pays homage to
- desktop BSD projects of the past PC-BSD and TrueOS with its
- graphical interface and adds additional tools like a live,
- hybrid USB/DVD image. FuryBSD is completely free to use and
- distributed under the BSD license.
+
NomadBSD is a
+ persistent live system for USB flash drives, based on &os;.
+ Together with automatic hardware detection and setup, it is
+ configured to be used as a desktop system that works out of
+ the box, but can also be used for data recovery, for
+ educational purposes, or to test &os;'s hardware
+ compatibility.
GhostBSD is derived
from &os;, uses the GTK environment to provide a beautiful
diff --git a/en_US.ISO8859-1/htdocs/advocacy/whyusefreebsd.xml b/en_US.ISO8859-1/htdocs/advocacy/whyusefreebsd.xml
index 62e007c332..16942c4a9d 100644
--- a/en_US.ISO8859-1/htdocs/advocacy/whyusefreebsd.xml
+++ b/en_US.ISO8859-1/htdocs/advocacy/whyusefreebsd.xml
@@ -74,7 +74,7 @@
thrive together.
This same collaboration works downstream, with projects like
- FuryBSD, GhostBSD, MidnightBSD and pfSense building on top of
+ GhostBSD, MidnightBSD, NomadBSD and pfSense building on top of
the &os; base to provide desktop and firewall oriented
distributions, respectively. These projects are not forks,
they base their work on the latest version of &os; and
diff --git a/en_US.ISO8859-1/htdocs/projects/newbies.xml b/en_US.ISO8859-1/htdocs/projects/newbies.xml
index db704b409a..5a889a8392 100644
--- a/en_US.ISO8859-1/htdocs/projects/newbies.xml
+++ b/en_US.ISO8859-1/htdocs/projects/newbies.xml
@@ -79,13 +79,6 @@
platform to share data over a network. It uses ZFS to protect,
store, backup, all of your data.
-
FuryBSD is a brand
- new, open source &os; desktop. FuryBSD pays homage to desktop
- BSD projects of the past PC-BSD and TrueOS with its graphical
- interface and adds additional tools like a live, hybrid
- USB/DVD image. FuryBSD is completely free to use and
- distributed under the BSD license.
-
GhostBSD is derived
from &os;, GhostBSD uses the GTK environment to provide a
beautiful looks and comfortable experience on the modern BSD
@@ -98,6 +91,14 @@
daily tasks: mail, web browsing, word processing, gaming,
and much more.
+
NomadBSD is a
+ persistent live system for USB flash drives, based on &os;.
+ Together with automatic hardware detection and setup, it is
+ configured to be used as a desktop system that works out
+ of the box, but can also be used for data recovery, for
+ educational purposes, or to test &os;'s hardware
+ compatibility.
+
pfSense is a &os;
based network security solution. pfSense
software, with the help of the package system, is able to
diff --git a/en_US.ISO8859-1/htdocs/where.xml b/en_US.ISO8859-1/htdocs/where.xml
index 1b91724cda..66bdc6ef5f 100644
--- a/en_US.ISO8859-1/htdocs/where.xml
+++ b/en_US.ISO8859-1/htdocs/where.xml
@@ -500,13 +500,6 @@
source storage platform based on &os; and supports sharing
across Windows, Apple, and UNIX-like systems.
-
FuryBSD is a brand
- new, open source &os; desktop. FuryBSD pays homage to desktop
- BSD projects of the past PC-BSD and TrueOS with its graphical
- interface and adds additional tools like a live, hybrid
- USB/DVD image. FuryBSD is completely free to use and
- distributed under the BSD license.
-
GhostBSD is derived
from &os;, GhostBSD uses the GTK environment to provide a
beautiful looks and comfortable experience on the modern BSD
@@ -519,6 +512,15 @@
daily tasks: mail, web browsing, word processing, gaming,
and much more.
+
NomadBSD is
+ a persistent live system for USB flash drives, based on &os;.
+ Together with automatic hardware detection and setup,
+ it is configured to be used as a desktop system that works out
+ of the box, but can also be used for data recovery, for
+ educational purposes, or to test &os;'s hardware
+ compatibility.
+
+
pfSense is a
&os; based customized distribution tailored for
use as a firewall and router.
From owner-dev-commits-doc-all@freebsd.org Thu Jan 7 09: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 053E04C94D4
for ;
Thu, 7 Jan 2021 09: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 "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4DBLCm67wKz4lh7;
Thu, 7 Jan 2021 09:14:44 +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 C59FF66B6;
Thu, 7 Jan 2021 09:14:44 +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 1079Eine069189;
Thu, 7 Jan 2021 09:14:44 GMT (envelope-from git@gitrepo.freebsd.org)
Received: (from git@localhost)
by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 1079EiFL069188;
Thu, 7 Jan 2021 09:14:44 GMT (envelope-from git)
Date: Thu, 7 Jan 2021 09:14:44 GMT
Message-Id: <202101070914.1079EiFL069188@gitrepo.freebsd.org>
To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org
From: Li-Wen Hsu
Subject: git: f3bf61d561 - main - Add link to git pepository
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: f3bf61d5614d54621681c2613edfa77c3eb659db
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, 07 Jan 2021 09:14:45 -0000
The branch main has been updated by lwhsu (ports, src committer):
URL: https://cgit.FreeBSD.org/doc/commit/?id=f3bf61d5614d54621681c2613edfa77c3eb659db
commit f3bf61d5614d54621681c2613edfa77c3eb659db
Author: Li-Wen Hsu
AuthorDate: 2021-01-07 09:13:44 +0000
Commit: Li-Wen Hsu
CommitDate: 2021-01-07 09:13:44 +0000
Add link to git pepository
Approved by: ygy
Differential Revision: https://reviews.freebsd.org/D28015
---
share/xml/header.ent | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/share/xml/header.ent b/share/xml/header.ent
index 93cf647b67..739508729d 100644
--- a/share/xml/header.ent
+++ b/share/xml/header.ent
@@ -137,8 +137,9 @@
From owner-dev-commits-doc-all@freebsd.org Fri Jan 8 13:23:35 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 5555D4CA0AB
for ;
Fri, 8 Jan 2021 13:23:35 +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 "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4DC3hR1wh8z3tFt;
Fri, 8 Jan 2021 13:23: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 34BE423E4B;
Fri, 8 Jan 2021 13:23: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 108DNZrU056059;
Fri, 8 Jan 2021 13:23:35 GMT (envelope-from git@gitrepo.freebsd.org)
Received: (from git@localhost)
by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 108DNZTn056058;
Fri, 8 Jan 2021 13:23:35 GMT (envelope-from git)
Date: Fri, 8 Jan 2021 13:23:35 GMT
Message-Id: <202101081323.108DNZTn056058@gitrepo.freebsd.org>
To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org
From: Daniel Ebdrup Jensen
Subject: git: e194334c79 - main - Arch handbook and articles: Reword sentences
beginning with 'Because...'
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Git-Committer: debdrup
X-Git-Repository: doc
X-Git-Refname: refs/heads/main
X-Git-Reftype: branch
X-Git-Commit: e194334c7994de1d5aa91259075cc4e05d0b4a73
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, 08 Jan 2021 13:23:35 -0000
The branch main has been updated by debdrup:
URL: https://cgit.FreeBSD.org/doc/commit/?id=e194334c7994de1d5aa91259075cc4e05d0b4a73
commit e194334c7994de1d5aa91259075cc4e05d0b4a73
Author: Daniel Ebdrup Jensen
AuthorDate: 2021-01-08 13:04:42 +0000
Commit: Daniel Ebdrup Jensen
CommitDate: 2021-01-08 13:04:42 +0000
Arch handbook and articles: Reword sentences beginning with 'Because...'
These sentences can either be or be mistaken for being sentence
fragments. While it is perfectly reasonable to use subordinate
conjunctions conversationally, as long as both clauses are explicitly
used in the same sentence, the handbook or articles are not written
in this style.
PR: 252493
Submitted by: Ceri Davies (ceri AT submonkey.net)
Reviewed by: 0mp, pauamma (pauamma AT gundo.com)
---
en_US.ISO8859-1/articles/committers-guide/article.xml | 2 +-
.../articles/contributors/contrib.develinmemoriam.xml | 2 +-
en_US.ISO8859-1/articles/ldap-auth/article.xml | 2 +-
en_US.ISO8859-1/articles/linux-emulation/article.xml | 8 ++++----
en_US.ISO8859-1/articles/serial-uart/article.xml | 16 ++++++++--------
en_US.ISO8859-1/articles/solid-state/article.xml | 10 +++++-----
en_US.ISO8859-1/articles/vm-design/article.xml | 2 +-
en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml | 8 ++++----
.../books/arch-handbook/driverbasics/chapter.xml | 4 ++--
en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml | 10 +++++-----
en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml | 2 +-
en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml | 8 ++++----
en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml | 2 +-
13 files changed, 38 insertions(+), 38 deletions(-)
diff --git a/en_US.ISO8859-1/articles/committers-guide/article.xml b/en_US.ISO8859-1/articles/committers-guide/article.xml
index e05587a219..db04ddd5f0 100644
--- a/en_US.ISO8859-1/articles/committers-guide/article.xml
+++ b/en_US.ISO8859-1/articles/committers-guide/article.xml
@@ -1280,7 +1280,7 @@ You need a Passphrase to protect your secret key.
Preparing the Merge Target
- Because of the mergeinfo propagation issues described
+ Due to the mergeinfo propagation issues described
earlier, it is very important to never merge changes
into a sparse working copy. Always use a full
checkout of the branch being merged into. For instance,
diff --git a/en_US.ISO8859-1/articles/contributors/contrib.develinmemoriam.xml b/en_US.ISO8859-1/articles/contributors/contrib.develinmemoriam.xml
index cb5064aa5c..eda3c20709 100644
--- a/en_US.ISO8859-1/articles/contributors/contrib.develinmemoriam.xml
+++ b/en_US.ISO8859-1/articles/contributors/contrib.develinmemoriam.xml
@@ -33,7 +33,7 @@
thinking, the missing historical context, the ambiguous
standards - and the style(9) transgressions.
- Because Bruce gave more code reviews than anybody else in
+ As Bruce gave more code reviews than anybody else in
the history of the FreeBSD project, the commit logs hide the
true scale of his impact until you pay attention to
"Submitted by", "Reviewed by" and "Pointed out by".
diff --git a/en_US.ISO8859-1/articles/ldap-auth/article.xml b/en_US.ISO8859-1/articles/ldap-auth/article.xml
index d1957adb4f..26ecdf7f29 100644
--- a/en_US.ISO8859-1/articles/ldap-auth/article.xml
+++ b/en_US.ISO8859-1/articles/ldap-auth/article.xml
@@ -617,7 +617,7 @@ passwd: files ldap
Unfortunately, as of the time this was written &os; did
not support changing user passwords with &man.passwd.1;.
- Because of this, most administrators are left to implement a
+ As a result of this, most administrators are left to implement a
solution themselves. I provide some examples here. Note that
if you write your own password change script, there are some
security issues you should be made aware of; see kse_* family of syscalls while the 1:1
library uses the thr_* family of
- syscalls. Because of this, there is no general concept of
+ syscalls. Due to this, there is no general concept of
thread ID shared between kernel and userspace. Of course,
both threading libraries implement the pthread thread ID
API. Every kernel thread (as described by struct
@@ -1683,7 +1683,7 @@ translate_traps(int signal, int trap_code)
PID mangling
- Because of the described different view knowing what a
+ As there is a difference in view as what to the idea of a
process ID and thread ID is between &os; and &linux; we have
to translate the view somehow. We do it by PID mangling.
This means that we fake what a PID (=TGID) and TID (=PID) is
@@ -1783,7 +1783,7 @@ void * child_tidptr);
linux_emuldata_shared. The
emul_lock is a nonsleepable blocking
mutex while emul_shared_lock is a
- sleepable blocking sx_lock. Because of
+ sleepable blocking sx_lock. Due to
the per-subsystem locking we can coalesce some locks and
that is why the em find offers the non-locking
access.
@@ -1981,7 +1981,7 @@ void * child_tidptr);
Threaded programs should be written with as little
contention on locks as possible. Otherwise, instead of
- doing useful work the thread just waits on a lock. Because
+ doing useful work the thread just waits on a lock. As a result
of this, the most well written threaded programs show little
locks contention.
diff --git a/en_US.ISO8859-1/articles/serial-uart/article.xml b/en_US.ISO8859-1/articles/serial-uart/article.xml
index e57b052b9e..2ddbfbe2aa 100644
--- a/en_US.ISO8859-1/articles/serial-uart/article.xml
+++ b/en_US.ISO8859-1/articles/serial-uart/article.xml
@@ -160,7 +160,7 @@
for the new word can be sent as soon as the Stop Bit for the
previous word has been sent.
- Because asynchronous data is self
+ As asynchronous data is self
synchronizing, if there is no data to transmit, the
transmission line can be idle.
@@ -605,7 +605,7 @@
Bits, Baud and SymbolsBaud is a measurement of transmission speed in
- asynchronous communication. Because of advances in modem
+ asynchronous communication. Due to advances in modem
communication technology, this term is frequently misused
when describing the data rates in newer devices.
@@ -676,7 +676,7 @@
DCE speed because of the use of compression by the
modems.
- Because the number of bits needed to describe a byte
+ As the number of bits needed to describe a byte
varied during the trip between the two machines plus the
differing bits-per-seconds speeds that are used present on
the DTE-DCE and DCE-DCE links, the usage of the term Baud to
@@ -769,7 +769,7 @@
technology with various functional flaws
corrected. The INS8250A was used initially in PC
clone computers by vendors who used
- clean BIOS designs. Because of the
+ clean BIOS designs. Due to the
corrections in the chip, this part could not be used
with a BIOS compatible with the INS8250 or
INS8250B.
@@ -949,7 +949,7 @@
In internal modems, the modem designer will frequently
emulate the 8250A/16450 with the modem microprocessor, and
the emulated UART will frequently have a hidden buffer
- consisting of several hundred bytes. Because of the size of
+ consisting of several hundred bytes. Due to the size of
the buffer, these emulations can be as reliable as a 16550A
in their ability to handle high speed data. However, most
operating systems will still report that the UART is only a
@@ -971,7 +971,7 @@
When the NS16550 was developed, the National
Semiconductor obtained several patents on the design and
they also limited licensing, making it harder for other
- vendors to provide a chip with similar features. Because of
+ vendors to provide a chip with similar features. As a result of
the patents, reverse-engineered designs and emulations had
to avoid infringing the claims covered by the patents.
Subsequently, these copies almost never perform exactly the
@@ -1008,7 +1008,7 @@
TI, StarTech, and CMD as well as megacells and emulations
embedded in internal modems were tested with COMTEST. A
difference count for some of these components is listed
- below. Because these tests were performed in 1994, they may
+ below. Since these tests were performed in 1994, they may
not reflect the current performance of the given product
from a vendor.
@@ -1954,7 +1954,7 @@
produce intelligent serial communication boards. This type of
design usually provides a microprocessor that interfaces with
several UARTs, processes and buffers the data, and then alerts the
- main PC processor when necessary. Because the UARTs are not
+ main PC processor when necessary. As the UARTs are not
directly accessed by the PC processor in this type of
communication system, it is not necessary for the vendor to use
UARTs that are compatible with the 8250, 16450, or the 16550 UART.
diff --git a/en_US.ISO8859-1/articles/solid-state/article.xml b/en_US.ISO8859-1/articles/solid-state/article.xml
index 232a5d59f4..8de18f207c 100644
--- a/en_US.ISO8859-1/articles/solid-state/article.xml
+++ b/en_US.ISO8859-1/articles/solid-state/article.xml
@@ -136,7 +136,7 @@
All embedded &os; systems that use flash memory as system
disk will be interested in memory disks and memory filesystems.
- Because of the limited number of writes that can be done to
+ As a result of the limited number of writes that can be done to
flash memory, the disk and the filesystems on the disk will most
likely be mounted read-only. In this environment, filesystems
such as /tmp and /var
@@ -223,16 +223,16 @@ pseudo-device md # memory disk
Building a File System from Scratch
- Because ATA compatible compact-flash cards are seen by &os;
+ Since ATA compatible compact-flash cards are seen by &os;
as normal IDE hard drives, you could theoretically install &os;
from the network using the kern and mfsroot floppies or from a
CD.However, even a small installation of &os; using normal
installation procedures can produce a system in size of greater
- than 200 megabytes. Because most people will be using smaller
+ than 200 megabytes. Most people will be using smaller
flash memory devices (128 megabytes is considered fairly large -
- 32 or even 16 megabytes is common) an installation using normal
+ 32 or even 16 megabytes is common), so an installation using normal
mechanisms is not possible—there is simply not enough disk
space for even the smallest of conventional
installations.
@@ -423,7 +423,7 @@ pseudo-device md # memory disk
successfully run makeinstall, we must create a packages
directory on a non-memory filesystem that will keep track of
- our packages across reboots. Because it is necessary to mount
+ our packages across reboots. As it is necessary to mount
your filesystems as read-write for the installation of a
package anyway, it is sensible to assume that an area on the
flash media can also be used for package information to be
diff --git a/en_US.ISO8859-1/articles/vm-design/article.xml b/en_US.ISO8859-1/articles/vm-design/article.xml
index 2cf7e001eb..79b56d296c 100644
--- a/en_US.ISO8859-1/articles/vm-design/article.xml
+++ b/en_US.ISO8859-1/articles/vm-design/article.xml
@@ -648,7 +648,7 @@
cannot be combined with the next A-B sequence.Why do we interleave our swap space instead of just tack swap
- areas onto the end and do something fancier? Because it is a whole
+ areas onto the end and do something fancier? It is a whole
lot easier to allocate linear swaths of an address space and have
the result automatically be interleaved across multiple disks than
it is to try to put that sophistication elsewhere.
diff --git a/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml
index 65f8c6cfd0..798b7bc6d9 100644
--- a/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/boot/chapter.xml
@@ -404,7 +404,7 @@ FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
- Because boot0 is loaded by the
+ As boot0 is loaded by the
BIOS to address 0x7C00, it
copies itself to address 0x600 and then
transfers control there (recall that it was linked to execute at
@@ -1021,7 +1021,7 @@ main.3:
bytes of boot and, because
boot is written to the first sector of the
&os; slice, boot1 fits exactly in this
- first sector. Because nread reads the first
+ first sector. When nread reads the first
16 sectors of the &os; slice, it effectively reads the entire
boot file
@@ -1440,7 +1440,7 @@ init: cli # Disable interrupts
flags in the EFLAGS register. Note that the
popfl instruction pops out a doubleword (4
bytes) from the stack and places it in the EFLAGS register.
- Because the value actually popped is 2, the
+ As the value actually popped is 2, the
EFLAGS register is effectively cleared (IA-32 requires that bit
2 of the EFLAGS register always be 1).
@@ -1583,7 +1583,7 @@ init.3: lea 0x8(%di),%di # Next entry
abstraction. The IA-32 architecture demands the creation and
use of at least one TSS
if multitasking facilities are used or different privilege
- levels are defined. Because the boot2
+ levels are defined. Since the boot2
client is executed in privilege level 3, but the
BTX server does in privilege level 0, a
TSS must be defined:
diff --git a/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
index 6e5551873b..9826e3a1d9 100644
--- a/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/driverbasics/chapter.xml
@@ -397,10 +397,10 @@ Closing device "echo".
For this reason, no serious applications rely on block
devices, and in fact, almost all applications which access
disks directly take great pains to specify that character
- (or raw) devices should always be used. Because
+ (or raw) devices should always be used. As
the implementation of the aliasing of each disk (partition) to
two devices with different semantics significantly complicated
- the relevant kernel code &os; dropped support for cached disk
+ the relevant kernel code, &os; dropped support for cached disk
devices as part of the modernization of the disk I/O
infrastructure.
diff --git a/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml
index 97bd2822c5..04de498a3f 100644
--- a/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/isa/chapter.xml
@@ -375,7 +375,7 @@
with PnP. This feature is not implemented in any existing
driver and is not considered further in this document.
- Because the PnP devices are disabled when probing the
+ As the PnP devices are disabled when probing the
legacy devices they will not be attached twice (once as legacy
and once as PnP). But in case of device-dependent identify
routines it is the responsibility of the driver to make sure
@@ -1019,7 +1019,7 @@
Free the memory allocated by
bus_dmamem_alloc(). At present,
freeing of the memory allocated with ISA restrictions is
- not implemented. Because of this the recommended model
+ not implemented. Due to this the recommended model
of use is to keep and re-use the allocated areas for as
long as possible. Do not lightly free some area and then
shortly allocate it again. That does not mean that
@@ -1322,11 +1322,11 @@
Before calling the callback function from
bus_dmamap_load() the segment array is
stored in the stack. And it gets pre-allocated for the
- maximal number of segments allowed by the tag. Because of
+ maximal number of segments allowed by the tag. As a result of
this the practical limit for the number of segments on i386
architecture is about 250-300 (the kernel stack is 4KB minus
the size of the user structure, size of a segment array
- entry is 8 bytes, and some space must be left). Because the
+ entry is 8 bytes, and some space must be left). Since the
array is allocated based on the maximal number this value
must not be set higher than really needed. Fortunately, for
most of hardware the maximal supported number of segments is
@@ -2192,7 +2192,7 @@
int error = 0;
Then allocate and activate all the necessary
- resources. Because normally the port range will be released
+ resources. As normally the port range will be released
before returning from probe, it has to be allocated
again. We expect that the probe routine had properly set all
the resource ranges, as well as saved them in the structure
diff --git a/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml
index a9a2753d9a..59261a9568 100644
--- a/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/pccard/chapter.xml
@@ -52,7 +52,7 @@
LinksysD-Link
- Because of this practice, FreeBSD drivers usually rely on
+ Due to this practice, FreeBSD drivers usually rely on
numeric IDs for device identification. Using numeric IDs and
a centralized database complicates adding IDs and support for
cards to the system. One must carefully check to see who
diff --git a/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml
index c325840bed..7de627b5b9 100644
--- a/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/scsi/chapter.xml
@@ -103,7 +103,7 @@
then also converting the SCSI commands to the native commands of
the hardware).
- Because we are interested in writing a SCSI adapter driver
+ As we are interested in writing a SCSI adapter driver
here, from this point on we will consider everything from the
SIM standpoint.
@@ -1076,7 +1076,7 @@
the timeout to make sure that the target is not sleeping
forever. If the command would not get aborted in some
reasonable time like 10 seconds the timeout routine would go
- ahead and reset the whole SCSI bus. Because the command
+ ahead and reset the whole SCSI bus. Since the command
will be aborted in some reasonable time we can just return
the abort request now as successfully completed, and mark
the aborted CCB as aborted (but not mark it as done
@@ -1116,7 +1116,7 @@
return;
That is all for the ABORT request, although there is one
- more issue. Because the ABORT message cleans all the
+ more issue. As the ABORT message cleans all the
ongoing transactions on a LUN we have to mark all the other
active transactions on this LUN as aborted. That should be
done in the interrupt routine, after the transaction gets
@@ -1634,7 +1634,7 @@
routine (or the other way around, the poll routine may be doing
the real action and the interrupt routine would just call the
poll routine). Why bother about a separate function then?
- Because of different calling conventions. The
+ Due to different calling conventions. The
xxx_poll routine gets the struct cam_sim
pointer as its argument when the PCI interrupt routine by common
convention gets pointer to the struct
diff --git a/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml b/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml
index 6fa02b2d59..1d34c3192b 100644
--- a/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml
+++ b/en_US.ISO8859-1/books/arch-handbook/usb/chapter.xml
@@ -668,7 +668,7 @@ This part is unclear, is it an unformatted code example?
Example: Firmware download Many devices that have been
developed are based on a general purpose processor with an
- additional USB core added to it. Because the development of
+ additional USB core added to it. Since the development of
drivers and firmware for USB devices is still very new, many
devices require the downloading of the firmware after they have
been connected.
From owner-dev-commits-doc-all@freebsd.org Fri Jan 8 15:18:56 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 DD01E4CCD2B
for ;
Fri, 8 Jan 2021 15:18:56 +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 "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4DC6FX5ztZz4Vy7;
Fri, 8 Jan 2021 15:18:56 +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 C071C2534F;
Fri, 8 Jan 2021 15:18: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 108FIubm099055;
Fri, 8 Jan 2021 15:18:56 GMT (envelope-from git@gitrepo.freebsd.org)
Received: (from git@localhost)
by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 108FIu8t099054;
Fri, 8 Jan 2021 15:18:56 GMT (envelope-from git)
Date: Fri, 8 Jan 2021 15:18:56 GMT
Message-Id: <202101081518.108FIu8t099054@gitrepo.freebsd.org>
To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org
From: Glen Barber
Subject: git: 07484d9080 - main - 13.0-RELEASE schedule: code slush in effect
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Git-Committer: gjb
X-Git-Repository: doc
X-Git-Refname: refs/heads/main
X-Git-Reftype: branch
X-Git-Commit: 07484d90809cfd10b34e718df3fe59cd3bea3495
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, 08 Jan 2021 15:18:56 -0000
The branch main has been updated by gjb:
URL: https://cgit.FreeBSD.org/doc/commit/?id=07484d90809cfd10b34e718df3fe59cd3bea3495
commit 07484d90809cfd10b34e718df3fe59cd3bea3495
Author: Glen Barber
AuthorDate: 2021-01-08 15:17:51 +0000
Commit: Glen Barber
CommitDate: 2021-01-08 15:17:51 +0000
13.0-RELEASE schedule: code slush in effect
Update the 13.0-RELEASE schedule to reflect the code slush for the
upcoming 13.0-RELEASE is now in effect.
Approved by: re (implicit)
Sponsored by: Rubicon Communications, LLC (netgate.com)
---
en_US.ISO8859-1/htdocs/releases/13.0R/schedule.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/en_US.ISO8859-1/htdocs/releases/13.0R/schedule.xml b/en_US.ISO8859-1/htdocs/releases/13.0R/schedule.xml
index d84ce4cd30..8717e92064 100644
--- a/en_US.ISO8859-1/htdocs/releases/13.0R/schedule.xml
+++ b/en_US.ISO8859-1/htdocs/releases/13.0R/schedule.xml
@@ -88,7 +88,7 @@
Code slush begins
8 January 2021
-
-
+
8 January 2021
Release Engineers announce that all further commits to the
&local.branch.head; branch will not require explicit
approval, however new features should be avoided.
From owner-dev-commits-doc-all@freebsd.org Sun Jan 10 11:51:54 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 C60FC4C9317
for ;
Sun, 10 Jan 2021 11:51:54 +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 "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4DDFYk5FxNz4WqX;
Sun, 10 Jan 2021 11:51:54 +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 A732527C2E;
Sun, 10 Jan 2021 11:51:54 +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 10ABpsqC071007;
Sun, 10 Jan 2021 11:51:54 GMT (envelope-from git@gitrepo.freebsd.org)
Received: (from git@localhost)
by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 10ABpsMD071006;
Sun, 10 Jan 2021 11:51:54 GMT (envelope-from git)
Date: Sun, 10 Jan 2021 11:51:54 GMT
Message-Id: <202101101151.10ABpsMD071006@gitrepo.freebsd.org>
To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org
From: Li-Wen Hsu
Subject: git: 09c1f2d199 - main - Community: mention the official FreeBSD
channel on YouTube
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: 09c1f2d199931d00b6f22842cf4db7e51509f458
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, 10 Jan 2021 11:51:54 -0000
The branch main has been updated by lwhsu (ports, src committer):
URL: https://cgit.FreeBSD.org/doc/commit/?id=09c1f2d199931d00b6f22842cf4db7e51509f458
commit 09c1f2d199931d00b6f22842cf4db7e51509f458
Author: Li-Wen Hsu
AuthorDate: 2021-01-10 11:51:07 +0000
Commit: Li-Wen Hsu
CommitDate: 2021-01-10 11:51:07 +0000
Community: mention the official FreeBSD channel on YouTube
Also tweak channel descriptions.
Approved by: ygy
Differential Revision: https://reviews.freebsd.org/D28076
---
en_US.ISO8859-1/htdocs/community.xsl | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/en_US.ISO8859-1/htdocs/community.xsl b/en_US.ISO8859-1/htdocs/community.xsl
index 2c9e6515cd..96dd9135ed 100644
--- a/en_US.ISO8859-1/htdocs/community.xsl
+++ b/en_US.ISO8859-1/htdocs/community.xsl
@@ -135,7 +135,11 @@
There are hundreds of videos from conferences,
screencasts, and demonstrations relating to &os;
- on YouTube. In particular, there is a new BSD Conferences channel with full length 1 hour taped presentations from FreeBSD technical conferences.
+ on YouTube. In particular, there is an
+ official FreeBSD channel
+ with developer summits, office hours and other event recordings, and a
+ BSD Conferences channel
+ with full taped presentations from FreeBSD technical conferences.
The GNU
Hurd project is another effort to develop a free
&unix; like operating system.
From owner-dev-commits-doc-all@freebsd.org Sun Jan 10 16:08: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 A660E4D1076
for ;
Sun, 10 Jan 2021 16:08: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 "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4DDMFM4HWQz4qKt;
Sun, 10 Jan 2021 16:08: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 863612E52;
Sun, 10 Jan 2021 16:08: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 10AG87Er095986;
Sun, 10 Jan 2021 16:08:07 GMT (envelope-from git@gitrepo.freebsd.org)
Received: (from git@localhost)
by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 10AG87lJ095985;
Sun, 10 Jan 2021 16:08:07 GMT (envelope-from git)
Date: Sun, 10 Jan 2021 16:08:07 GMT
Message-Id: <202101101608.10AG87lJ095985@gitrepo.freebsd.org>
To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org
From: Marc Fonvieille
Subject: git: 0d6f42cb77 - main - Redirect gs stdout to stderr. This will
prevent warnings to be part of the generated file causing broken files. This
does not redirect drivers output which still write to stdout.
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: 0d6f42cb77983bc8c908294b8fcbaa029040810a
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, 10 Jan 2021 16:08:07 -0000
The branch main has been updated by blackend:
URL: https://cgit.FreeBSD.org/doc/commit/?id=0d6f42cb77983bc8c908294b8fcbaa029040810a
commit 0d6f42cb77983bc8c908294b8fcbaa029040810a
Author: Marc Fonvieille
AuthorDate: 2021-01-10 16:01:58 +0000
Commit: Marc Fonvieille
CommitDate: 2021-01-10 16:01:58 +0000
Redirect gs stdout to stderr. This will prevent warnings to be part of
the generated file causing broken files. This does not redirect drivers
output which still write to stdout.
I'm currently seeing "**** Warning: glyf overlaps cmap, truncating."
during esptopng conversion leading to broken .pnm.
This change prevents the broken .pnm file.
---
share/mk/doc.commands.mk | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/share/mk/doc.commands.mk b/share/mk/doc.commands.mk
index 6f2c1f2282..fa759eb09c 100644
--- a/share/mk/doc.commands.mk
+++ b/share/mk/doc.commands.mk
@@ -117,7 +117,7 @@ SCR2PNGOPTS?= ${SCR2PNGFLAGS}
SCR2TXT?= ${PREFIX}/bin/scr2txt
SCR2TXTOPTS?= -l ${SCR2TXTFLAGS}
EPS2PNM?= ${PREFIX}/bin/gs
-EPS2PNMOPTS?= -q -dBATCH -dGraphicsAlphaBits=4 -dTextAlphaBits=4 \
+EPS2PNMOPTS?= -sstdout=%stderr -q -dBATCH -dGraphicsAlphaBits=4 -dTextAlphaBits=4 \
-dEPSCrop -r${EPS2PNM_RES}x${EPS2PNM_RES} \
-dNOPAUSE -dSAFER -sDEVICE=pnm -sOutputFile=-
#
From owner-dev-commits-doc-all@freebsd.org Sun Jan 10 16:11:43 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 469CA4D1650
for ;
Sun, 10 Jan 2021 16:11:43 +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 "Let's Encrypt Authority X3" (verified OK))
by mx1.freebsd.org (Postfix) with ESMTPS id 4DDMKW1bTGz4qb0;
Sun, 10 Jan 2021 16:11:43 +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 29A4D2E70;
Sun, 10 Jan 2021 16:11:43 +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 10AGBhsv005604;
Sun, 10 Jan 2021 16:11:43 GMT (envelope-from git@gitrepo.freebsd.org)
Received: (from git@localhost)
by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 10AGBhmZ005603;
Sun, 10 Jan 2021 16:11:43 GMT (envelope-from git)
Date: Sun, 10 Jan 2021 16:11:43 GMT
Message-Id: <202101101611.10AGBhmZ005603@gitrepo.freebsd.org>
To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org
From: Marc Fonvieille
Subject: git: 7e233f6e6a - main - Update Xorg fonts section.
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: 7e233f6e6aacdd008b49fc41887d1c3a393c120a
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, 10 Jan 2021 16:11:43 -0000
The branch main has been updated by blackend:
URL: https://cgit.FreeBSD.org/doc/commit/?id=7e233f6e6aacdd008b49fc41887d1c3a393c120a
commit 7e233f6e6aacdd008b49fc41887d1c3a393c120a
Author: Marc Fonvieille
AuthorDate: 2021-01-10 16:10:05 +0000
Commit: Marc Fonvieille
CommitDate: 2021-01-10 16:10:05 +0000
Update Xorg fonts section.
---
fr_FR.ISO8859-1/books/handbook/x11/chapter.xml | 119 ++++++++-----------------
1 file changed, 36 insertions(+), 83 deletions(-)
diff --git a/fr_FR.ISO8859-1/books/handbook/x11/chapter.xml b/fr_FR.ISO8859-1/books/handbook/x11/chapter.xml
index 8dd89ed4df..f0d0d23bde 100644
--- a/fr_FR.ISO8859-1/books/handbook/x11/chapter.xml
+++ b/fr_FR.ISO8859-1/books/handbook/x11/chapter.xml
@@ -1166,11 +1166,18 @@ EndSection
- Polices de caractères anticrénelage
-
- Joe MarcusClarkeMis à jour par
-
-
+
+ Polices de caractères anticrénelagepolices de caractères
@@ -1178,25 +1185,14 @@ EndSection
polices de caractèresanticrénelage
- L'anticrénelage est disponible sous
- X11 depuis &xfree86; 4.0.2.
- Cependant, la configuration des polices de caractères
- était relativement lourde avant l'arrivée
- d'&xfree86; 4.3.0. Depuis
- &xfree86; 4.3.0, toutes les polices
- sous X11 se trouvant dans les répertoires /usr/local/lib/X11/fonts/ et
+ Toutes les polices de caractères sous &xorg;
+ se trouvant dans les répertoires /usr/local/share/fonts/ et
~/.fonts/ sont
automatiquement disponibles pour l'anticrénelage avec
- les applications compatibles Xft. Toutes les applications ne
- sont pas compatibles Xft, mais de nombreuses ont
- été dotées du support Xft. Par exemple,
- les applications utilisant Qt 2.3 et versions suivantes (la
- boîte à outils pour l'environnement de travail
- KDE), GTK+ 2.0 et suivantes (la
- boîte à outils de l'environnement de travail
- GNOME), et
- Mozilla 1.2 et versions
- suivantes.
+ les applications compatibles Xft. La plupart des application
+ sont compatibles Xft, comme KDE,
+ GNOME, et
+ Firefox.Afin de contrôler quelles polices de
caractères sont anticrénelées, ou pour
@@ -1228,7 +1224,7 @@ EndSection
Comme précisé précédemment,
l'ensemble des polices de caractères du
- répertoire /usr/local/lib/X11/fonts/ comme du
+ répertoire /usr/local/share/fonts/ comme du
répertoire ~/.fonts/ sont disponibles pour
les applications compatibles Xft. Si vous désirez
ajouter un autre répertoire en dehors des ces deux
@@ -1238,7 +1234,7 @@ EndSection
<dir>/chemin/vers/mes/fontes</dir>
- Après l'ajout de nouvelles fontes, et tout
+ Après l'ajout de nouvelles polices, et tout
particulièrement de nouveaux répertoires de polices, vous
devrez exécuter la commande suivante pour reconstituer le
cache des polices de caractères:
@@ -1248,8 +1244,8 @@ EndSection
L'anticrénelage rend les bords
légèrement flous, ce qui rend le texte très
petit plus lisible et enlève l'effet
- “d'escalier” des grands textes, mais peut provoquer
- une fatigue visuelle si c'est appliqué au texte normal.
+ d'escalier des grands textes, mais peut provoquer
+ une fatigue visuelle si c'est appliqué au texte de taille normale.
Pour exclure les tailles de polices inférieures à 14 points de
l'anticrénelage, ajoutez ces lignes:
@@ -1316,8 +1312,7 @@ EndSection
l'anticrénelage. Généralement cela se
manifeste par l'impression que la fonte semble coupée
en deux verticalement. Au pire cela peut provoquer des crashs
- avec certaines applications comme
- Mozilla. Pour éviter cela,
+ avec certaines applications. Pour éviter cela,
pensez à ajouter ce qui suit au fichier
local.conf:
@@ -1336,34 +1331,15 @@ EndSection
</fontconfig>. Si ce n'est pas le
cas, tous vos changements seront ignorés.
- L'ensemble de polices de caractères fourni par
- défaut avec X11 n'est
- pas très adapté pour l'anticrénelage. Un
- bien meilleur ensemble de fontes peut être trouvé
- dans le catalogue des logiciels portés: x11-fonts/bitstream-vera. Ce
- logiciel installera un fichier
- /usr/local/etc/fonts/local.conf si ce
- dernier n'existe pas déjà. Si le fichier
- existe, le logiciel porté créera un fichier
- nommé
- /usr/local/etc/fonts/local.conf-vera. Il
- fusionnera le contenu de ce fichier dans
- /usr/local/etc/fonts/local.conf, et les
- polices de caractères Bitstream remplaceront
- automatiquement les polices avec empattement (serif), sans
- empattement (sans-serif) et à chasse fixe
- d'X11.
-
- Et enfin, les utilisateurs peuvent ajouter leurs propres
- paramètres par l'intermédiaire de leur fichier
- .fonts.conf. Pour cela, chaque
- utilisateur devrait créer un fichier
- ~/.fonts.conf. Ce fichier doit
- également être écrit en XML.
-
- LCD screen
- Fonts
- LCD screen
+ Les utilisateurs peuvent ajouter leurs propres
+ paramètres par l'intermédiaire de leur propre fichier
+ ~/.config/fontconfig/fonts.conf.
+ Ce fichier doit utiliser le même format XML
+ décrit précédemment.
+
+ Écran LCD
+ polices de caractères
+ Écran LCDUn dernier point: avec un écran LCD, un
échantillonnage “sub-pixel” peut être
@@ -1388,34 +1364,11 @@ EndSection
En fonction de type d'écran, le terme
- “rgb” pourra devoir être changé pour
- “bgr”, “vrgb” ou
- “vbgr”: expérimentez
- pour définir lequel fonctionne le mieux.
+ rgb pourra devoir être changé pour
+ bgr, vrgb ou
+ vbgr: expérimentez
+ pour déterminer lequel fonctionne le mieux.
-
-
- Mozilla
- désactiver l'anticrénelage des
- polices de caractères
-
-
- L'anticrénelage devrait être activé au
- prochain lancement du serveur X. Cependant, notez que les
- applications doivent savoir comment l'utiliser. A l'heure
- actuelle, le “toolkit” Qt le supporte, donc
- l'intégralité de l'environnement
- KDE peut utiliser des polices
- anticrénelées.
- GTK+ et GNOME peuvent également
- faire usage de l'anticrénelage via le système
- Font.
- Par défaut, Mozilla 1.2 et
- versions suivantes utiliseront automatiquement
- l'anticrénelage. Pour désactiver cette
- caractéristique, recompilez
- Mozilla avec le paramètre
- -DWITHOUT_XFT.