From nobody Tue Jun 24 10:51:54 2025 X-Original-To: dev-commits-doc-all@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4bRMG24nCdz5ydRw for ; Tue, 24 Jun 2025 10: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 "R10" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4bRMG2393Yz46nb; Tue, 24 Jun 2025 10:51:54 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750762314; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=UG2/SM6PnNeUCTomW3UnxjRpOTjFRYIQgndHZ6SJwz0=; b=irpqkAJCcqxhuxX/x9cGCQhgd69AKW0LTPYyuKVA1y5kYPKJKbYzHRehwo1pGURGUB78y6 ESwyj1T4ecfuTf8POkqrgJucT69ZAANh3MdfsoOj6MPpzAz2NxrXUtEeHu5x58EeaC8tHU 3VFn90zpIg0PxcYb6zTb4xXESe0uOxzChHME614tzlrce51VtS2vx0XtXZOlni6pJYkEJ9 Pdw5ANKlVqJ3nqDeugPiY2Mp83Wav5UP1Ns/hV7OdLteDG90kvl3jcZIPtpsUCHMnUakDK T29pyIa6UvQlPwRYUm0QfjnGVG5yS5gLoP6ufvLLZmQyrMjT0Hz1OEROuBU4iA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1750762314; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=UG2/SM6PnNeUCTomW3UnxjRpOTjFRYIQgndHZ6SJwz0=; b=sL+3IcY+EmEgJsTk5CP2F9+mzXQAakrj6JDNFfOF4/Ua4tKvvCCSiB4FNhHlWTT73vAkqt Q9WGE71Ayd8fUHGgcpM6e/CD7SthsnM6uRxO3Isw9dlsmz0e2uzZDAp8RXFjGkATQJ9h/N uipc2zPhUifyWcU7G7N6Ix3EL396VmWbwZO8KeIBqomr7SdOKIwS0b6Xiojk1UMCDQL+QQ gOOt5IyVvW3FziX7sxUFi1GLahwrw3Qljwiwp49H4orCm/TPhfKYsLqd7eEuNuoGzQyFvm SoSAvFA3wckCKNOokQxoQjSSTiu2oBZmiB9T3LT7UsbmMWlUquQiHjXMZdGsaw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1750762314; a=rsa-sha256; cv=none; b=yYWaWX4g8FBMGu0J9rv3yMKkM9ZCs0ZOqzIf+9e5jnSOCSoEO719TMTGwcvn5rKkz/GGKX w29Q3VUJlbeCwxZaMRFpo4qaQvUiJK+/F69XnyLm29JtHmmWduKm6BZo5GhkV8v9u196/3 Wf3lADkqfCCjFuRLJBucqL7e8HwWBZOoSspEMuDyeTcIxcJoA/OK1u7BLUF+OGozytNsBF FkOGIygYM+VspxIOc7LJylkoVXTxx+BcgKf5SERkw8UeAGkj59IR7AWRSpB0rdro127J94 nndTiSdpF563eAtberC/ZVfRL0blw1UhZkLgFUBXukQFfBq3BhUJaGAuAXZj8Q== 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 4bRMG22KPDzlBd; Tue, 24 Jun 2025 10:51:54 +0000 (UTC) (envelope-from git@FreeBSD.org) Received: from gitrepo.freebsd.org ([127.0.1.44]) by gitrepo.freebsd.org (8.18.1/8.18.1) with ESMTP id 55OAps49034617; Tue, 24 Jun 2025 10:51:54 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.18.1/8.18.1/Submit) id 55OAps1W034614; Tue, 24 Jun 2025 10:51:54 GMT (envelope-from git) Date: Tue, 24 Jun 2025 10:51:54 GMT Message-Id: <202506241051.55OAps1W034614@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Maxim Konovalov Subject: git: 80394bc1a9 - main - Status/2025Q2: spell List-Id: Commit messages for all branches of the doc repository List-Archive: https://lists.freebsd.org/archives/dev-commits-doc-all List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: dev-commits-doc-all@freebsd.org Sender: owner-dev-commits-doc-all@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Git-Committer: maxim X-Git-Repository: doc X-Git-Refname: refs/heads/main X-Git-Reftype: branch X-Git-Commit: 80394bc1a9845c318671c3e7ea322ddb0f3bc390 Auto-Submitted: auto-generated The branch main has been updated by maxim: URL: https://cgit.FreeBSD.org/doc/commit/?id=80394bc1a9845c318671c3e7ea322ddb0f3bc390 commit 80394bc1a9845c318671c3e7ea322ddb0f3bc390 Author: Maxim Konovalov AuthorDate: 2025-06-24 10:50:05 +0000 Commit: Maxim Konovalov CommitDate: 2025-06-24 10:50:05 +0000 Status/2025Q2: spell --- website/content/en/status/report-2025-04-2025-06/packrat.adoc | 8 ++++---- .../content/en/status/report-2025-04-2025-06/ports-security.adoc | 2 +- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/website/content/en/status/report-2025-04-2025-06/packrat.adoc b/website/content/en/status/report-2025-04-2025-06/packrat.adoc index 7ceaaebd22..f496bccc9c 100644 --- a/website/content/en/status/report-2025-04-2025-06/packrat.adoc +++ b/website/content/en/status/report-2025-04-2025-06/packrat.adoc @@ -4,9 +4,9 @@ Contact: Rick Macklem NFSv4.1/4.2 provides support for a feature called delegations. When a NFSv4.1/4.2 client holds a delegation, the client has certain rights to a file, including a guarantee that no other client will make changes to the file unless the delegation is recalled. -As such, when a client holds a delegation for a file, it can agressively cache the file's data, knowing that it will not be modified by other clients until it returns the delegation. +As such, when a client holds a delegation for a file, it can aggressively cache the file's data, knowing that it will not be modified by other clients until it returns the delegation. -This project is intended to allow the NFSv4.1/4.2 client to agressively cache file data on client local non-volatile storage, when the client holds a delegation for the file. +This project is intended to allow the NFSv4.1/4.2 client to aggressively cache file data on client local non-volatile storage, when the client holds a delegation for the file. I created a patch long ago to try and do this for NFSv4.0, but it was never at a stage where it was worth using. This project is a complete rewrite of the patch, done in part because NFSv4.1/4.2 plus other recent NFSv4 related changes makes doing this more feasible. @@ -18,6 +18,6 @@ This can result in the umount taking a long time (as in many minutes). To alleviate this, I am planning on implementing a writeback kernel process that will walk the non-volatile storage and write the dirty chunks back. The trick is to make it aggressive enough that most dirty chunks have been written back when a umount is done, but not so aggressive that it impedes the performance of synchronous NFSv4.1/4.2 RPCs. -This will be very much an experimental feature, but it is hoped it will allow NFS mounts to be used more effectively, particularily in WAN situations, such as a mobile laptop. +This will be very much an experimental feature, but it is hoped it will allow NFS mounts to be used more effectively, particularly in WAN situations, such as a mobile laptop. -There is still work to be done, particularily with respect to recovery of delegations after a NFSv4.1/4.2 client restart. +There is still work to be done, particularly with respect to recovery of delegations after a NFSv4.1/4.2 client restart. diff --git a/website/content/en/status/report-2025-04-2025-06/ports-security.adoc b/website/content/en/status/report-2025-04-2025-06/ports-security.adoc index d4b4211b77..8fb04f26d6 100644 --- a/website/content/en/status/report-2025-04-2025-06/ports-security.adoc +++ b/website/content/en/status/report-2025-04-2025-06/ports-security.adoc @@ -21,4 +21,4 @@ Zero call-used registers at function return to increase program security by eith This depends upon support from the compiler for a given architecture. This is disabled for python ports; currently there are issues. -The blog post referenced in the links section explains how to use them, how to exclude certain ports if needed, and provides a more detailed explaination of those 3 new features along the already existing build-time security options of the Ports Collection and the basesystem build. +The blog post referenced in the links section explains how to use them, how to exclude certain ports if needed, and provides a more detailed explanation of those 3 new features along the already existing build-time security options of the Ports Collection and the basesystem build.