Use correct syntax markup for shell

Approved by:	carlavilla
This commit is contained in:
Li-Wen Hsu 2021-03-14 20:08:55 +08:00
parent 55c95407aa
commit a9a9e66105
No known key found for this signature in database
GPG key ID: 8D7BCC7D012FD37E
666 changed files with 17924 additions and 17924 deletions

View file

@ -61,7 +61,7 @@ At a minimum, updates require building on a FreeBSD release greater than or equa
Download the https://svnweb.freebsd.org/base/user/cperciva/freebsd-update-build/[freebsd-update-server] software by installing package:devel/subversion[] and package:security/ca_root_nss[], and execute:
[source,bash]
[source,shell]
....
% svn co https://svn.freebsd.org/base/user/cperciva/freebsd-update-build freebsd-update-server
....
@ -102,7 +102,7 @@ Customizations to the `fetchiso()` code can be installed by copying the default
<.> The name of the build host. This information will be displayed on updated systems when issuing:
+
[source,bash]
[source,shell]
....
% uname -v
....
@ -120,7 +120,7 @@ The default [.filename]#build.conf# shipped with the freebsd-update-server sourc
====
. Create a build environment for amd64:
+
[source,bash]
[source,shell]
....
% mkdir -p /usr/local/freebsd-update-server/scripts/7.2-RELEASE/amd64
....
@ -145,7 +145,7 @@ export EOL=1275289200 <.>
<.> The man:sha256[1] hash key for the desired release, is published within the respective link:https://www.FreeBSD.org/releases/[release announcement].
<.> To generate the "End of Life" number for [.filename]#build.conf#, refer to the "Estimated EOL" posted on the link:https://www.FreeBSD.org/security/security/[FreeBSD Security Website]. The value of `EOL` can be derived from the date listed on the web site, using the man:date[1] utility, for example:
+
[source,bash]
[source,shell]
....
% date -j -f '%Y%m%d-%H%M%S' '20090401-000000' '+%s'
....
@ -156,7 +156,7 @@ export EOL=1275289200 <.>
The first step is to run [.filename]#scripts/make.sh#. This will build some binaries, create directories, and generate an RSA signing key used for approving builds. In this step, a passphrase will have to be supplied for the final creation of the signing key.
[source,bash]
[source,shell]
....
# sh scripts/make.sh
cc -O2 -fno-strict-aliasing -pipe findstamps.c -o findstamps
@ -186,7 +186,7 @@ Keep a note of the generated key fingerprint. This value is required in [.filena
At this point, we are ready to stage a build.
[source,bash]
[source,shell]
....
# cd /usr/local/freebsd-update-server
# sh scripts/init.sh amd64 7.2-RELEASE
@ -194,7 +194,7 @@ At this point, we are ready to stage a build.
What follows is a sample of an _initial_ build run.
[source,bash]
[source,shell]
....
# sh scripts/init.sh amd64 7.2-RELEASE
Mon Aug 24 16:04:36 PDT 2009 Starting fetch for FreeBSD/amd64 7.2-RELEASE
@ -244,7 +244,7 @@ Then the build of the world is performed again, with world patches. A more detai
During this second build cycle, the network time protocol daemon, man:ntpd[8], is turned off. Per `{cperciva}`, Security Officer Emeritus of FreeBSD, "the https://svnweb.freebsd.org/base/user/cperciva/freebsd-update-build/[freebsd-update-server] build code needs to identify timestamps which are stored in files so that they can be ignored when comparing builds to determine which files need to be updated. This timestamp-finding works by doing two builds 400 days apart and comparing the results."
====
[source,bash]
[source,shell]
....
Mon Aug 24 17:54:07 PDT 2009 Extracting world+src for FreeBSD/amd64 7.2-RELEASE
Wed Sep 29 00:54:34 UTC 2010 Building world for FreeBSD/amd64 7.2-RELEASE
@ -283,7 +283,7 @@ world|base|/usr/lib/libalias_ftp.a
Finally, the build completes.
[source,bash]
[source,shell]
....
Values of build stamps, excluding library archive headers:
v1.2 (Aug 25 2009 00:40:36)
@ -321,13 +321,13 @@ to sign the release.
Approve the build if everything is correct. More information on determining this can be found in the distributed source file named [.filename]#USAGE#. Execute [.filename]#scripts/approve.sh#, as directed. This will sign the release, and move components into a staging area suitable for uploading.
[source,bash]
[source,shell]
....
# cd /usr/local/freebsd-update-server
# sh scripts/mountkey.sh
....
[source,bash]
[source,shell]
....
# sh -e scripts/approve.sh amd64 7.2-RELEASE
Wed Aug 26 12:50:06 PDT 2009 Signing build for FreeBSD/amd64 7.2-RELEASE
@ -339,7 +339,7 @@ Wed Aug 26 12:50:07 PDT 2009 Cleaning staging area for FreeBSD/amd64 7.2-RELEASE
After the approval process is complete, the upload procedure may be started.
[source,bash]
[source,shell]
....
# cd /usr/local/freebsd-update-server
# sh scripts/upload.sh amd64 7.2-RELEASE
@ -349,7 +349,7 @@ After the approval process is complete, the upload procedure may be started.
====
In the event update code needs to be re-uploaded, this may be done by changing to the public distributions directory for the target release and updating attributes of the _uploaded_ file.
[source,bash]
[source,shell]
....
# cd /usr/local/freebsd-update-server/pub/7.2-RELEASE/amd64
# touch -t 200801010101.01 uploaded
@ -382,7 +382,7 @@ A couple of assumptions are made for a different release build:
Create the patch directory of the respective release under [.filename]#/usr/local/freebsd-update-server/patches/#.
[source,bash]
[source,shell]
....
% mkdir -p /usr/local/freebsd-update-server/patches/7.1-RELEASE/
% cd /usr/local/freebsd-update-server/patches/7.1-RELEASE
@ -392,7 +392,7 @@ As an example, take the patch for man:named[8]. Read the advisory, and grab the
In the https://security.freebsd.org/advisories/FreeBSD-SA-09:12.bind.asc[security brief], this advisory is called `SA-09:12.bind`. After downloading the file, it is required to rename the file to an appropriate patch level. It is suggested to keep this consistent with official FreeBSD patch levels, but its name may be freely chosen. For this build, let us follow the currently established practice of FreeBSD and call this `p7`. Rename the file:
[source,bash]
[source,shell]
....
% cd /usr/local/freebsd-update-server/patches/7.1-RELEASE/; mv bind.patch 7-SA-09:12.bind
....
@ -412,7 +412,7 @@ It is up to the administrator of the FreeBSD Update Server to take appropriate m
At this point, a _diff_ is ready to be built. The software checks first to see if a [.filename]#scripts/init.sh# has been run on the respective release prior to running the diff build.
[source,bash]
[source,shell]
....
# cd /usr/local/freebsd-update-server
# sh scripts/diff.sh amd64 7.1-RELEASE 7
@ -420,7 +420,7 @@ At this point, a _diff_ is ready to be built. The software checks first to see i
What follows is a sample of a _differential_ build run.
[source,bash]
[source,shell]
....
# sh -e scripts/diff.sh amd64 7.1-RELEASE 7
Wed Aug 26 10:09:59 PDT 2009 Extracting world+src for FreeBSD/amd64 7.1-RELEASE-p7
@ -497,7 +497,7 @@ Wed Aug 26 17:20:39 UTC 2009
Updates are printed, and approval is requested.
[source,bash]
[source,shell]
....
New updates:
kernel|generic|/GENERIC/kernel.symbols|f|0|0|0555|0|7c8dc176763f96ced0a57fc04e7c1b8d793f27e006dd13e0b499e1474ac47e10|
@ -519,7 +519,7 @@ to sign the build.
Follow the same process as noted before for approving a build:
[source,bash]
[source,shell]
....
# sh -e scripts/approve.sh amd64 7.1-RELEASE
Wed Aug 26 12:50:06 PDT 2009 Signing build for FreeBSD/amd64 7.1-RELEASE
@ -537,7 +537,7 @@ the new builds.
After approving the build, upload the software:
[source,bash]
[source,shell]
....
# cd /usr/local/freebsd-update-server
# sh scripts/upload.sh amd64 7.1-RELEASE