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

@ -126,21 +126,21 @@ In all examples below, `$FSVN` refers to the location of the FreeBSD Subversion
The layout of FreeBSD branches in Subversion is described in the link:{committers-guide}#subversion-primer-base-layout[Committer's Guide]. The first step in creating a branch is to identify the revision of the `stable/_X_` sources that you want to branch _from_.
[source,bash]
[source,shell]
....
# svn log -v $FSVN/stable/9
....
The next step is to create the _release branch_
[source,bash]
[source,shell]
....
# svn cp $FSVN/stable/9@REVISION $FSVN/releng/9.2
....
This branch can be checked out:
[source,bash]
[source,shell]
....
# svn co $FSVN/releng/9.2 src
....
@ -211,7 +211,7 @@ Additionally, update the "BSD Family Tree" file:
When the final release is ready, the following command will create the `release/9.2.0` tag.
[source,bash]
[source,shell]
....
# svn cp $FSVN/releng/9.2 $FSVN/release/9.2.0
....
@ -229,7 +229,7 @@ FreeBSD "releases" can be built by anyone with a fast machine and access to a so
man:release[7] documents the exact commands required to build a FreeBSD release. The following sequences of commands can build an 9.2.0 release:
[source,bash]
[source,shell]
....
# cd /usr/src/release
# sh generate-release.sh release/9.2.0 /local3/release
@ -268,7 +268,7 @@ The https://www.FreeBSD.org/ports[FreeBSD Ports collection] is a collection of o
Starting with FreeBSD 4.4, the FreeBSD Project decided to release all four ISO images that were previously sold on the _BSDi/Wind River Systems/FreeBSD Mall_ "official" CDROM distributions. Each of the four discs must contain a [.filename]#README.TXT# file that explains the contents of the disc, a [.filename]#CDROM.INF# file that provides meta-data for the disc so that man:bsdinstall[8] can validate and use the contents, and a [.filename]#filename.txt# file that provides a manifest for the disc. This _manifest_ can be created with a simple command:
[source,bash]
[source,shell]
....
/stage/cdrom# find . -type f | sed -e 's/^\.\///' | sort > filename.txt
....