From nobody Tue Jun 7 07:42:00 2022 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 0F7461BE036F for ; Tue, 7 Jun 2022 07:42: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 4LHMkc50gyz4Rsf; Tue, 7 Jun 2022 07:42:00 +0000 (UTC) (envelope-from git@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1654587720; 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=5+DGlWTKC2ZDBNTbt2nMakZXBW9UUduDfNFYXgpjo2M=; b=wfI/JfqvRA0PoxxdZXk6/z2LMVYNEAti2RqNZkzuEP/E8ACawubWxr+1Pdydr3N3M9exQL caXCecdHB3mp3pfKWS+fvVKCaY8c1Cleiys01mo6eVNbl3fq8wQJt1gG504WHZQ0eqg5Uw VsI1hwDVooea0H0tuG6/otfteRsf8MB56cwLsRwd6l+EwV8CkE1prS+UOqvE2cWAJN1/7m ma2UiNcXr4Y40zndUC5TQ/vQL3LriUBII3jpEg9UQEdNwp0JrVOtBUG1OF4OHS5UEv2Sga VPixCxWzsaUM6pbYgoR8SsT9Ggz8wRpgTDs/84gXKBH8QJz8mvtLHlyacZyreA== 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 7DA6917110; Tue, 7 Jun 2022 07:42:00 +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 2577g0gG076329; Tue, 7 Jun 2022 07:42:00 GMT (envelope-from git@gitrepo.freebsd.org) Received: (from git@localhost) by gitrepo.freebsd.org (8.16.1/8.16.1/Submit) id 2577g0qc076328; Tue, 7 Jun 2022 07:42:00 GMT (envelope-from git) Date: Tue, 7 Jun 2022 07:42:00 GMT Message-Id: <202206070742.2577g0qc076328@gitrepo.freebsd.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org From: Sergio Carlavilla Delgado Subject: git: 9f81e7c44f - main - Fix version numbers in FAQs 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: Sender: owner-dev-commits-doc-all@freebsd.org X-BeenThere: dev-commits-doc-all@freebsd.org 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: 9f81e7c44fcf1a5018f6402ddc8c09001daade12 Auto-Submitted: auto-generated ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1654587720; 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=5+DGlWTKC2ZDBNTbt2nMakZXBW9UUduDfNFYXgpjo2M=; b=M0vOu4m70flvQlZWPo8AyQzbRoqyZ/RRGF+f7AVnd+XE4yAThbo5q+ZKzZcaJv/aMFthez 9bW0cUWSqitLXnE5g0CEDqz71MtNCFwAubaCqYgxd+YRApX+W4G9zrJLnxN//7OAZrGTzy GwrzO91kEFhkK4tn55yK2OSHlyYuu9ROrhddGn/SaJi79u1I7jK/LPkuKW1zvo9Lj3nWmF h3iiIJB5RwAwpR7HWCq6lQ0tWDeb47GgGiVSnxj3cC0Y2KSN8Hk7xq+2nqoWtwffXmwE0J jzvrcTZNSTgn+FpqFq4cIuaVa3PzU0rD1iBWA9Z2KsR+pwRsGvbuwevCJvvqUQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1654587720; a=rsa-sha256; cv=none; b=Lv29bAKbrEPzbVtg1N85ZmZ8doK1fUHBUA0++eXqEFgmO4B0dmYtudyD8DX84Noe6LtWoJ GXwNCaLOIdrw8Wtka09mFRT47FOkrUah+F3a6fIi2A02ZkrFm6r4zvw4YslHAsUgaNrha7 I2jNmRkxdDBrcjbPGn8a96zN9ljIW5C36tZeAJftOCG7H8kuOwRt7O+ywhSCYXTn5LG7dZ WLQabZ5MjuwdF9CNANZeJQOZ7VFlp/hhKAv1Z3xIHVoEji7wwQAfImN2XDMTobQN7+ktky N5i+MnL5No3fU7dcETbHbqFuOh7UIsoqLBDkQz3yPUBhyO0DKYStnyf/42yNBQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N The branch main has been updated by carlavilla: URL: https://cgit.FreeBSD.org/doc/commit/?id=9f81e7c44fcf1a5018f6402ddc8c09001daade12 commit 9f81e7c44fcf1a5018f6402ddc8c09001daade12 Author: Sergio Carlavilla Delgado AuthorDate: 2022-06-07 07:39:41 +0000 Commit: Sergio Carlavilla Delgado CommitDate: 2022-06-07 07:39:41 +0000 Fix version numbers in FAQs * Use architecture-agnostic URLs. * Make FAQ 10.18 less dramatic and less condescending. PR: 261816 Patch by: pauamma@ Reviewd by: grahamperrin@ Differential Revision: https://reviews.freebsd.org/D35345 --- documentation/content/en/books/faq/_index.adoc | 24 +++++++++++------------- 1 file changed, 11 insertions(+), 13 deletions(-) diff --git a/documentation/content/en/books/faq/_index.adoc b/documentation/content/en/books/faq/_index.adoc index b56a880137..de3500ff6e 100644 --- a/documentation/content/en/books/faq/_index.adoc +++ b/documentation/content/en/books/faq/_index.adoc @@ -2,7 +2,7 @@ title: Frequently Asked Questions for FreeBSD 12.X and 13.X authors: - author: The FreeBSD Documentation Project -copyright: 1995-2021 The FreeBSD Documentation Project +copyright: 1995-2022 The FreeBSD Documentation Project description: Frequently Asked Questions, and answers, covering all aspects of FreeBSD trademarks: ["freebsd", "ibm", "ieee", "adobe", "intel", "linux", "microsoft", "opengroup", "sun", "netbsd", "general"] bookOrder: 5 @@ -191,8 +191,8 @@ _FreeBSD-CURRENT_, on the other hand, has been one unbroken line since 2.0 was r For more detailed information on branches see "extref:{releng}[FreeBSD Release Engineering: Creating the Release Branch, rel-branch]", the status of the branches and the upcoming release schedule can be found on the https://www.FreeBSD.org/releng[Release Engineering Information] page. -Version https://download.FreeBSD.org/releases/amd64/amd64/{rel121-current}-RELEASE/[{rel121-current}] is the latest release from the {rel-stable} branch; it was released in {rel121-current-date}. -Version https://download.FreeBSD.org/releases/amd64/amd64/{rel113-current}-RELEASE/[{rel113-current}] is the latest release from the {rel2-stable} branch; it was released in {rel113-current-date}. +Version {u-rel123-announce}[{rel123-current}] is the latest release from the {rel2-stable} branch; it was released on {rel123-current-date}. +Version {u-rel131-announce}[{rel131-current}] is the latest release from the {rel-stable} branch; it was released on {rel131-current-date}. [[release-freq]] === When are FreeBSD releases made? @@ -237,11 +237,11 @@ and there are no restrictions on who may take part in the discussion. [[where-get]] === Where can I get FreeBSD? -Every significant release of FreeBSD is available via anonymous FTP from the https://download.FreeBSD.org/releases/[FreeBSD FTP site]: +Every supported release of FreeBSD is available from the https://www.freebsd.org/where/[FreeBSD release locator page]: -* The latest {rel-stable} release, {rel121-current}-RELEASE can be found in the https://download.FreeBSD.org/releases/amd64/amd64/{rel121-current}-RELEASE/[{rel121-current}-RELEASE directory]. -* link:https://www.FreeBSD.org/snapshots/[Snapshot] releases are made monthly for the <> and <> branch, these being of service purely to bleeding-edge testers and developers. -* The latest {rel2-stable} release, {rel113-current}-RELEASE can be found in the https://download.FreeBSD.org/releases/amd64/amd64/{rel113-current}-RELEASE/[{rel113-current}-RELEASE directory]. +* For the latest {rel-stable} release, {rel131-current}-RELEASE, follow the link for link:https://www.freebsd.org/where/#download-rel131[the appropriate architecture and installation mode for {rel131-current}-RELEASE]. +* For the latest {rel2-stable} release, {rel123-current}-RELEASE, follow the link for link:https://www.freebsd.org/where/#download-rel123[the appropriate architecture and installation mode for {rel123-current}-RELEASE]. +* link:https://www.FreeBSD.org/snapshots/[Snapshot] releases are made monthly for the <> and <> branches, these being of service purely to bleeding-edge testers and developers. Information about obtaining FreeBSD on CD, DVD, and other media can be found in extref:{handbook}[the Handbook, mirrors]. @@ -574,7 +574,7 @@ bsdconfig provides a nice interface to configure FreeBSD post-installation. ==== I want to get a piece of hardware for my FreeBSD system. Which model/brand/type is best? This is discussed continually on the FreeBSD mailing lists but is to be expected since hardware changes so quickly. -Read through the Hardware Notes for FreeBSD link:{u-rel121-hardware}[{rel121-current}] or link:{u-rel113-hardware}[{rel113-current}] and search the mailing list https://www.FreeBSD.org/search/#mailinglists[archives] before asking about the latest and greatest hardware. +Read through the Hardware Notes for FreeBSD link:{u-rel123-hardware}[{rel123-current}] or link:{u-rel131-hardware}[{rel131-current}] and search the https://www.FreeBSD.org/search/#mailinglists[mailing list archives] before asking about the latest and greatest hardware. Chances are a discussion about that type of hardware took place just last week. Before purchasing a laptop, check the archives for {freebsd-questions}, @@ -663,7 +663,7 @@ to [.filename]#/etc/rc.conf# [[supported-peripherals]] ==== What kind of peripherals does FreeBSD support? -See the complete list in the Hardware Notes for FreeBSD link:{u-rel121-hardware}[{rel121-current}] or link:{u-rel113-hardware}[{rel113-current}]. +See a list of hardware known to work and any applicable restrictions in the Hardware Notes for FreeBSD link:{u-rel123-hardware}[{rel123-current}] or link:{u-rel131-hardware}[{rel131-current}]. [[compatibility-kbd-mice]] === Keyboards and Mice @@ -1905,13 +1905,11 @@ See the man:init[8] manual page for details on `securelevel`, and see [.filename === Why is rpc.statd using 256 MB of memory? No, there is no memory leak, and it is not using 256 MB of memory. -For convenience, `rpc.statd` maps an obscene amount of memory into its address space. +For convenience, `rpc.statd` maps a large amount of memory into its address space. There is nothing terribly wrong with this from a technical standpoint; it just throws off things like man:top[1] and man:ps[1]. -man:rpc.statd[8] maps its status file (resident on [.filename]#/var#) into its address space; +man:rpc.statd[8] maps its status file ([.filename]#/var/db/statd.status#) into its address space; to save worrying about remapping the status file later when it needs to grow, it maps the status file with a generous size. -This is very evident from the source code, where one can see that the length argument to man:mmap[2] is `0x10000000`, -or one sixteenth of the address space on an IA32, or exactly 256 MB. [[unsetting-schg]] === Why can I not unset the schg file flag?