Date: Sat, 30 May 2026 18:24:58 +0000 From: Vladlen Popolitov <vladlen@FreeBSD.org> To: doc-committers@FreeBSD.org, dev-commits-doc-all@FreeBSD.org Subject: git: 6ac4980f06 - main - articles/releng: fix man links Message-ID: <6a1b2b7a.1d74d.38d0950f@gitrepo.freebsd.org>
index | next in thread | raw e-mail
The branch main has been updated by vladlen: URL: https://cgit.FreeBSD.org/doc/commit/?id=6ac4980f06c9bdca95a8c514ab492c5415e66dad commit 6ac4980f06c9bdca95a8c514ab492c5415e66dad Author: Vladlen Popolitov <vladlen@FreeBSD.org> AuthorDate: 2026-05-30 18:24:51 +0000 Commit: Vladlen Popolitov <vladlen@FreeBSD.org> CommitDate: 2026-05-30 18:24:51 +0000 articles/releng: fix man links Approved by: doceng (implicit) Differential Revision: https://reviews.freebsd.org/D57367 --- .../content/en/articles/freebsd-releng/_index.adoc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/documentation/content/en/articles/freebsd-releng/_index.adoc b/documentation/content/en/articles/freebsd-releng/_index.adoc index 60460d3c92..d3a3bac672 100644 --- a/documentation/content/en/articles/freebsd-releng/_index.adoc +++ b/documentation/content/en/articles/freebsd-releng/_index.adoc @@ -341,7 +341,7 @@ The relevant release-related documents exist in the [.filename]#doc# repository === Ports Changes During `BETA`, `RC`, and the Final `RELEASE` For each build during the release cycle, the `MANIFEST` files containing the `SHA256` of the various distribution sets, such as `base.txz`, `kernel.txz`, and so on, are added to the package:misc/freebsd-release-manifests[] port. -This allows utilities other than , such as package:ports-mgmt/poudriere[], to safely use these distribution sets by providing a mechanism through which the checksums can be verified. +This allows utilities other than man:bsdinstall[8], such as package:ports-mgmt/poudriere[], to safely use these distribution sets by providing a mechanism through which the checksums can be verified. [[releng-head]] == Release from {branchHead} @@ -591,7 +591,7 @@ This section describes the general procedures producing FreeBSD development snap [[releng-build-scripts]] === Release Build Scripts -Prior to FreeBSD 9.0-RELEASE, [.filename]#src/release/Makefile# was updated to support , and the [.filename]#src/release/generate-release.sh# script was introduced as a wrapper to automate invoking the targets. +Prior to FreeBSD 9.0-RELEASE, [.filename]#src/release/Makefile# was updated to support man:bsdinstall[8], and the [.filename]#src/release/generate-release.sh# script was introduced as a wrapper to automate invoking the man:release[7] targets. Prior to FreeBSD 9.2-RELEASE, [.filename]#src/release/release.sh# was introduced, which heavily based on [.filename]#src/release/generate-release.sh# included support to specify configuration files to override various options and environment variables. Support for configuration files provided support for cross building each architecture for a release by specifying a separate configuration file for each invocation. @@ -621,7 +621,7 @@ Then invoke [.filename]#src/release/release.sh# as: # /bin/sh /usr/src/release/release.sh -c $HOME/release.conf .... -See and [.filename]#src/release/release.conf.sample# for more details and example usage. +See man:release[7] and [.filename]#src/release/release.conf.sample# for more details and example usage. [[releng-build-release]] === Building FreeBSD Releases @@ -673,8 +673,8 @@ Staging FreeBSD snapshots and releases is a two part process: * Creating the directory structure to match the hierarchy on `ftp-master` + -If `EVERYTHINGISFINE` is defined in the build configuration files, [.filename]#main.conf# in the case of the build scripts referenced above, this happens automatically in the after the build is complete, creating the directory structure in [.filename]#${DESTDIR}/R/ftp-stage# with a path structure matching what is expected on `ftp-master`. -This is equivalent to running the following in the directly: +If `EVERYTHINGISFINE` is defined in the build configuration files, [.filename]#main.conf# in the case of the build scripts referenced above, this happens automatically in the man:chroot[8] after the build is complete, creating the directory structure in [.filename]#${DESTDIR}/R/ftp-stage# with a path structure matching what is expected on `ftp-master`. +This is equivalent to running the following in the man:chroot[8] directly: + [source,shell,subs="attributes"] .... @@ -695,14 +695,14 @@ On `ftp-master` in the FreeBSD Project infrastructure, this step requires `root` === Publishing FreeBSD Installation Media Once the images are staged in [.filename]#/archive/tmp/#, they are ready to be made public by putting them in [.filename]#/archive/pub/FreeBSD#. -To reduce propagation time, is used to create hard links from [.filename]#/archive/tmp# to [.filename]#/archive/pub/FreeBSD#. +To reduce propagation time, man:pax[1] is used to create hard links from [.filename]#/archive/tmp# to [.filename]#/archive/pub/FreeBSD#. [NOTE] ==== For this to be effective, both [.filename]#/archive/tmp# and [.filename]#/archive/pub# must reside on the same logical filesystem. ==== -There is a caveat, however, where rsync must be used after to correct the symbolic links in [.filename]#pub/FreeBSD/snapshots/ISO-IMAGES# which will replace with a hard link, increasing the propagation time. +There is a caveat, however, where rsync must be used after man:pax[1] to correct the symbolic links in [.filename]#pub/FreeBSD/snapshots/ISO-IMAGES# which man:pax[1] will replace with a hard link, increasing the propagation time. [NOTE] ====home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6a1b2b7a.1d74d.38d0950f>