git: 42f4d16e77 - main - Replace more http links with https
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Wed, 28 Oct 2026 18:24:28 UTC
The branch main has been updated by bcr:
URL: https://cgit.FreeBSD.org/doc/commit/?id=42f4d16e77b19ed3772c80cbc84c80a23b19f0b8
commit 42f4d16e77b19ed3772c80cbc84c80a23b19f0b8
Author: Sarder Kamal <s.kamal@mdx.ac.uk>
AuthorDate: 2026-10-28 18:18:38 +0000
Commit: Benedict Reuschling <bcr@FreeBSD.org>
CommitDate: 2026-10-28 18:24:02 +0000
Replace more http links with https
Replaced links that still exist with their https derivatives. For those
links that are dead, a suitable replacement was tried to put into its
place. If nothing came up during the search, removed the link entirely.
Event: Oslo Hackathon 2026
---
documentation/content/en/articles/cups/_index.adoc | 2 +-
.../content/en/articles/explaining-bsd/_index.adoc | 18 +++++++++---------
.../content/en/articles/geom-class/_index.adoc | 6 +++---
.../content/en/articles/mailing-list-faq/_index.adoc | 2 +-
documentation/content/en/articles/pam/_index.adoc | 2 +-
.../content/en/articles/rc-scripting/_index.adoc | 2 +-
documentation/content/en/articles/releng/_index.adoc | 4 ++--
.../content/en/articles/x86-assembly/_index.adoc | 6 +++---
8 files changed, 21 insertions(+), 21 deletions(-)
diff --git a/documentation/content/en/articles/cups/_index.adoc b/documentation/content/en/articles/cups/_index.adoc
index 58478fa0de..bb99da6aba 100644
--- a/documentation/content/en/articles/cups/_index.adoc
+++ b/documentation/content/en/articles/cups/_index.adoc
@@ -58,7 +58,7 @@ The Line Printer Daemon (LPD), Server Message Block (SMB), and AppSocket (aka Je
CUPS adds network printer browsing and PostScript Printer Description (PPD) based printing options to support real-world printing under UNIX(R).
As a result, CUPS is ideally-suited for sharing and accessing printers in mixed environments of FreeBSD, Linux(R), Mac OS(R) X, or Windows(R).
-The main site for CUPS is http://www.cups.org/[http://www.cups.org/].
+The main site for CUPS is https://www.cups.org/[https://www.cups.org/].
[[printing-cups-install]]
== Installing the CUPS Print Server
diff --git a/documentation/content/en/articles/explaining-bsd/_index.adoc b/documentation/content/en/articles/explaining-bsd/_index.adoc
index 86365b5b26..d78a8d0ab9 100644
--- a/documentation/content/en/articles/explaining-bsd/_index.adoc
+++ b/documentation/content/en/articles/explaining-bsd/_index.adoc
@@ -69,7 +69,7 @@ __The BSD C library is based on code from Berkeley, not the GNU project.__
__Some of the utilities are derived from the GNU project, others are not.__
* The X Window system, which handles graphical display.
+
-The X Window system used in most versions of BSD is maintained by the http://www.X.org/[X.Org project].
+The X Window system used in most versions of BSD is maintained by the https://www.X.org/[X.Org project].
FreeBSD allows the user to choose from a variety of desktop environments, such as Gnome, KDE, or Xfce; and lightweight window managers like Openbox, Fluxbox, or Awesome.
* Many other programs and utilities.
@@ -99,14 +99,14 @@ Some members of the group decided to release the BSD code, which was Open Source
This finally happened with the __Networking Tape 2__, usually known as __Net/2__.
Net/2 was not a complete operating system: about 20% of the kernel code was missing.
One of the CSRG members, William F. Jolitz, wrote the remaining code and released it in early 1992 as __386BSD__.
-At the same time, another group of ex-CSRG members formed a commercial company called http://www.bsdi.com/[Berkeley Software Design Inc.] and released a beta version of an operating system called http://www.bsdi.com/[BSD/386], which was based on the same sources.
+At the same time, another group of ex-CSRG members formed a commercial company called Berkeley Software Design Inc. and released a beta version of an operating system called BSD/386, which was based on the same sources.
The name of the operating system was later changed to BSD/OS.
386BSD never became a stable operating system.
-Instead, two other projects split off from it in 1993: http://www.NetBSD.org/[NetBSD] and link:https://www.FreeBSD.org/[FreeBSD].
+Instead, two other projects split off from it in 1993: https://www.NetBSD.org/[NetBSD] and link:https://www.FreeBSD.org/[FreeBSD].
The two projects originally diverged due to differences in patience waiting for improvements to 386BSD: the NetBSD people started early in the year, and the first version of FreeBSD was not ready until the end of the year.
In the meantime, the code base had diverged sufficiently to make it difficult to merge.
-In addition, the projects had different aims, as we will see below. In 1996, http://www.OpenBSD.org/[OpenBSD] split off from NetBSD, and in 2003, http://www.dragonflybsd.org/[DragonFlyBSD] split off from FreeBSD.
+In addition, the projects had different aims, as we will see below. In 1996, https://www.OpenBSD.org/[OpenBSD] split off from NetBSD, and in 2003, https://www.dragonflybsd.org/[DragonFlyBSD] split off from FreeBSD.
[[why-is-bsd-not-better-known]]
== Why is BSD not better known?
@@ -115,7 +115,7 @@ For a number of reasons, BSD is relatively unknown:
. The BSD developers are often more interested in polishing their code than marketing it.
. Much of Linux's popularity is due to factors external to the Linux projects, such as the press, and to companies formed to provide Linux services. Until recently, the open source BSDs had no such proponents.
-. In 1992, AT&T sued http://www.bsdi.com/[BSDI], the vendor of BSD/386, alleging that the product contained AT&T-copyrighted code. The case was settled out of court in 1994, but the spectre of the litigation continues to haunt people. In March 2000 an article published on the web claimed that the court case had been "recently settled".
+. In 1992, AT&T sued BSDI, the vendor of BSD/386, alleging that the product contained AT&T-copyrighted code. The case was settled out of court in 1994, but the spectre of the litigation continues to haunt people. In March 2000 an article published on the web claimed that the court case had been "recently settled".
+
One detail that the lawsuit did clarify is the naming: in the 1980s, BSD was known as "BSD UNIX(R)".
With the elimination of the last vestige of AT&T code from BSD, it also lost the right to the name UNIX(R).
@@ -193,13 +193,13 @@ It is difficult to categorize the goals of each project: the differences are ver
There are also two additional BSD UNIX(R) operating systems which are not open source, BSD/OS and Apple's Mac OS(R) X:
* BSD/OS was the oldest of the 4.4BSD derivatives. It was not open source, though source code licenses were available at relatively low cost. It resembled FreeBSD in many ways. Two years after the acquisition of BSDi by Wind River Systems, BSD/OS failed to survive as an independent product. Support and source code may still be available from Wind River, but all new development is focused on the VxWorks embedded operating system.
-* http://www.apple.com/macosx/server/[Mac OS(R) X] is the latest version of the operating system for Apple(R)'s Mac(R) line. The BSD core of this operating system, http://developer.apple.com/darwin/[Darwin], is available as a fully functional open source operating system for x86 and PPC computers. The Aqua/Quartz graphics system and many other proprietary aspects of Mac OS(R) X remain closed-source, however. Several Darwin developers are also FreeBSD committers, and vice-versa.
+* https://www.apple.com/os/macos/[Mac OS(R) X] is the latest version of the operating system for Apple(R)'s Mac(R) line. The BSD core of this operating system, https://www.operating-system.org/betriebssystem/_english/bs-darwin.htm[Darwin], is available as a fully functional open source operating system for x86 and PPC computers. The Aqua/Quartz graphics system and many other proprietary aspects of Mac OS(R) X remain closed-source, however. Several Darwin developers are also FreeBSD committers, and vice-versa.
=== How does the BSD license differ from the GNU Public license?
-Linux is available under the http://www.fsf.org/copyleft/gpl.html[GNU General Public License] (GPL), which is designed to eliminate closed source software.
+Linux is available under the https://www.gnu.org/licenses/old-licenses/gpl-2.0.html[GNU General Public License] (GPL), which is designed to eliminate closed source software.
In particular, any derivative work of a product released under the GPL must also be supplied with source code if requested.
-By contrast, the http://www.opensource.org/licenses/bsd-license.html[BSD license] is less restrictive: binary-only distributions are allowed.
+By contrast, the https://opensource.org/license/BSD-2-Clause[BSD license] is less restrictive: binary-only distributions are allowed.
This is particularly attractive for embedded applications.
=== What else should I know?
@@ -227,4 +227,4 @@ Here are some guidelines:
=== Who provides support, service, and training for BSD?
-Each of the projects has a list of consultants for hire: link:https://www.FreeBSD.org/commercial/consult_bycat/[FreeBSD], http://www.netbsd.org/gallery/consultants.html[NetBSD], and http://www.openbsd.org/support.html[OpenBSD].
+Each of the projects has a list of consultants for hire: link:https://www.FreeBSD.org/commercial/consult_bycat/[FreeBSD], https://www.netbsd.org/gallery/consultants.html[NetBSD], and https://www.openbsd.org/support.html[OpenBSD].
diff --git a/documentation/content/en/articles/geom-class/_index.adoc b/documentation/content/en/articles/geom-class/_index.adoc
index 233a2f6478..0cd3e26895 100644
--- a/documentation/content/en/articles/geom-class/_index.adoc
+++ b/documentation/content/en/articles/geom-class/_index.adoc
@@ -59,9 +59,9 @@ However, there are some bits and pieces (some of them seriously outdated) floati
* The extref:{developers-handbook}[FreeBSD Developer's Handbook] - part of the documentation project, it does not contain anything specific to kernel programming, but rather some general useful information.
* The extref:{arch-handbook}[FreeBSD Architecture Handbook] - also from the documentation project, contains descriptions of several low-level facilities and procedures. The most important chapter is 13, extref:{arch-handbook}[Writing FreeBSD device drivers, driverbasics].
-* The Blueprints section of http://www.freebsddiary.org[FreeBSD Diary] web site - contains several interesting articles on kernel facilities.
+* The Blueprints section of https://www.freebsddiary.org[FreeBSD Diary] web site - contains several interesting articles on kernel facilities.
* The man pages in section 9 - for important documentation on kernel functions.
-* The man:geom[4] man page and http://phk.freebsd.dk/pubs/[PHK's GEOM slides] - for general introduction of the GEOM subsystem.
+* The man:geom[4] man page and https://phk.freebsd.dk/pubs/[PHK's GEOM slides] - for general introduction of the GEOM subsystem.
* Man pages man:g_bio[9], man:g_event[9], man:g_data[9], man:g_geom[9], man:g_provider[9], man:g_consumer[9], man:g_access[9] & others linked from those, for documentation on specific functionalities.
* The man:style[9] man page - for documentation on the coding-style conventions which must be followed for any code which is to be committed to the FreeBSD tree.
@@ -75,7 +75,7 @@ The second system does not even require a proper display.
Instead, it could be connected with a serial cable or KVM to the first one.
But, since not everybody has two or more computers handy, there are a few things that can be done to prepare an otherwise "live" system for developing kernel code.
-This setup is also applicable for developing in a http://www.vmware.com/[VMWare] or http://www.qemu.org/[QEmu] virtual machine (the next best thing after a dedicated development machine).
+This setup is also applicable for developing in a https://www.vmware.com/[VMWare] or https://www.qemu.org/[QEmu] virtual machine (the next best thing after a dedicated development machine).
[[prelim-system]]
=== Modifying a System for Development
diff --git a/documentation/content/en/articles/mailing-list-faq/_index.adoc b/documentation/content/en/articles/mailing-list-faq/_index.adoc
index 7d7fa98278..b79f4e4b79 100644
--- a/documentation/content/en/articles/mailing-list-faq/_index.adoc
+++ b/documentation/content/en/articles/mailing-list-faq/_index.adoc
@@ -178,7 +178,7 @@ In particular, there are certain topics that seem to regularly occur to newcomer
It is the responsibility of each poster to ensure that their postings do not fall into one of these categories.
By doing so, you will help the mailing lists to stay on-topic, and probably save yourself being flamed in the process.
-The best method to avoid this is to familiarize yourself with the http://docs.FreeBSD.org/mail/[mailing list archives], to help yourself understand the background of what has gone before.
+The best method to avoid this is to familiarize yourself with the https://mail-archive.freebsd.org/mail/[mailing list archives], to help yourself understand the background of what has gone before.
In this, the https://www.FreeBSD.org/search/#mailinglists[mailing list search interface] is invaluable.
(If that method does not yield useful results, please supplement it with a search with your favorite major search engine).
diff --git a/documentation/content/en/articles/pam/_index.adoc b/documentation/content/en/articles/pam/_index.adoc
index d76cb36c19..af00790b69 100644
--- a/documentation/content/en/articles/pam/_index.adoc
+++ b/documentation/content/en/articles/pam/_index.adoc
@@ -680,6 +680,6 @@ _link:https://docs.oracle.com/cd/E26505_01/html/E27224/pam-1.html[PAM Administra
_link:https://www.openpam.org/[OpenPAM homepage]_ Dag-Erling Smørgrav. ThinkSec AS.
-_link:http://www.kernel.org/pub/linux/libs/pam/[Linux-PAM homepage]_ Andrew Morgan.
+_link:https://www.kernel.org/pub/linux/libs/pam/[Linux-PAM homepage]_ Andrew Morgan.
_Solaris PAM homepage_. Sun Microsystems.
diff --git a/documentation/content/en/articles/rc-scripting/_index.adoc b/documentation/content/en/articles/rc-scripting/_index.adoc
index f9fe049c17..663e89b7bc 100644
--- a/documentation/content/en/articles/rc-scripting/_index.adoc
+++ b/documentation/content/en/articles/rc-scripting/_index.adoc
@@ -1012,7 +1012,7 @@ This prevents the automatic pick-up of changes to the start script when an updat
[[rcng-furthur]]
== Further reading
-[[lukem]]http://www.mewburn.net/luke/papers/rc.d.pdf[The original article by Luke Mewburn] offers a general overview of [.filename]#rc.d# and detailed rationale for its design decisions.
+[[lukem]]https://www.mewburn.net/luke/papers/rc.d.pdf[The original article by Luke Mewburn] offers a general overview of [.filename]#rc.d# and detailed rationale for its design decisions.
It provides insight on the whole [.filename]#rc.d# framework and its place in a modern BSD operating system.
[[manpages]]The manual pages man:rc[8], man:rc.subr[8], and man:rcorder[8] document the [.filename]#rc.d# components in great detail.
diff --git a/documentation/content/en/articles/releng/_index.adoc b/documentation/content/en/articles/releng/_index.adoc
index cdb1f717f7..22b37af20b 100644
--- a/documentation/content/en/articles/releng/_index.adoc
+++ b/documentation/content/en/articles/releng/_index.adoc
@@ -61,7 +61,7 @@ toc::[]
The development of FreeBSD is a very open process.
FreeBSD is comprised of contributions from thousands of people around the world.
-The FreeBSD Project provides Subversion footnote:[Subversion, http://subversion.apache.org] access to the general public so that others can have access to log messages, diffs (patches) between development branches, and other productivity enhancements that formal source code management provides.
+The FreeBSD Project provides Subversion footnote:[Subversion, https://subversion.apache.org] access to the general public so that others can have access to log messages, diffs (patches) between development branches, and other productivity enhancements that formal source code management provides.
This has been a huge help in attracting more talented developers to FreeBSD.
However, I think everyone would agree that chaos would soon manifest if write access to the main repository was opened up to everyone on the Internet.
Therefore only a "select" group of nearly 300 people are given write access to the Subversion repository.
@@ -443,4 +443,4 @@ Along these lines we are working very hard to document the procedures involved i
I would like to thank Jordan Hubbard for giving me the opportunity to take on some of the release engineering responsibilities for FreeBSD 4.4 and also for all of his work throughout the years making FreeBSD what it is today.
Of course the release would not have been possible without all of the release-related work done by `{asami}`, `{steve}`, `{bmah}`, `{nik}`, `{obrien}`, `{kris}`, `{jhb}` and the rest of the FreeBSD development community.
I would also like to thank `{rgrimes}`, `{phk}`, and others who worked on the release engineering tools in the very early days of FreeBSD.
-This article was influenced by release engineering documents from the CSRG footnote:[Marshall Kirk McKusick, Michael J. Karels, and Keith Bostic: link:http://docs.FreeBSD.org/44doc/papers/releng.html[The Release Engineering of 4.3BSD]] , the NetBSD Project, footnote:[NetBSD Developer Documentation: Release Engineering http://www.NetBSD.org/developers/releng/index.html] , and John Baldwin's proposed release engineering process notes. footnote:[John Baldwin's FreeBSD Release Engineering Proposal https://people.FreeBSD.org/~jhb/docs/releng.txt]
+This article was influenced by release engineering documents from the CSRG footnote:[Marshall Kirk McKusick, Michael J. Karels, and Keith Bostic: link:https://docs.FreeBSD.org/44doc/papers/releng.html[The Release Engineering of 4.3BSD]] , the NetBSD Project, footnote:[NetBSD Developer Documentation: Release Engineering httpis://www.NetBSD.org/developers/releng/index.html] , and John Baldwin's proposed release engineering process notes. footnote:[John Baldwin's FreeBSD Release Engineering Proposal https://people.FreeBSD.org/~jhb/docs/releng.txt]
diff --git a/documentation/content/en/articles/x86-assembly/_index.adoc b/documentation/content/en/articles/x86-assembly/_index.adoc
index 612b8bface..34c437aba5 100644
--- a/documentation/content/en/articles/x86-assembly/_index.adoc
+++ b/documentation/content/en/articles/x86-assembly/_index.adoc
@@ -63,7 +63,7 @@ Even if we believe that all of UNIX software should be written in C, or some oth
In this article I will attempt to show you how you can use assembly language writing UNIX programs, specifically under FreeBSD.
This article does not explain the basics of assembly language.
-There are enough resources about that (for a complete online course in assembly language, see Randall Hyde's http://webster.cs.ucr.edu/[Art of Assembly Language];
+There are enough resources about that (for a complete online course in assembly language, see Randall Hyde's https://www.randallhyde.com/books/#Bookshelf[Art of Assembly Language];
or if you prefer a printed book, take a look at Jeff Duntemann's Assembly Language Step-by-Step (ISBN: 0471375233).
However, once the article is finished, any assembly language programmer will be able to write programs for FreeBSD quickly and efficiently.
@@ -1463,7 +1463,7 @@ http db 'Content-type: text/html', 0Ah, 0Ah
db '<?xml version="1.0" encoding="utf-8"?>', 0Ah
db '<!DOCTYPE html PUBLIC "-//W3C/DTD XHTML Strict//EN" '
db '"DTD/xhtml1-strict.dtd">', 0Ah
- db '<html xmlns="http://www.w3.org/1999/xhtml" '
+ db '<html xmlns="https://www.w3.org/1999/xhtml" '
db 'xml.lang="en" lang="en">', 0Ah
db '<head>', 0Ah
db '<title>Web Environment</title>', 0Ah
@@ -2709,7 +2709,7 @@ Remember that, or you will be pulling your hair out in desperation!
[NOTE]
====
-The book to read-if you can find it-is Richard Startz' http://www.amazon.com/exec/obidos/ASIN/013246604X/whizkidtechnomag[8087/80287/80387 for the IBM PC & Compatibles].
+The book to read-if you can find it-is Richard Startz' https://www.amazon.com/exec/obidos/ASIN/013246604X/whizkidtechnomag[8087/80287/80387 for the IBM PC & Compatibles].
Though it does seem to take the fact about the little-endian storage of the _packed decimal_ for granted.
I kid you not about the desperation of trying to figure out what was wrong with the filter I show below _before_ it occurred to me I should try the little-endian order even for this type of data.
====