When obtaining or updating sources using cvs or CVSup, a revision tag must be specified. A revision tag refers to either a particular line of FreeBSD development, or a specific point in time. The first type are called “branch tags”, and the second type are called “release tags”.
All of these, with the exception of HEAD (which is always a valid tag), only apply to the src/ tree. The ports/, doc/, and www/ trees are not branched.
Symbolic name for the main line, or FreeBSD-CURRENT. Also the default when no revision is specified.
In CVSup, this tag is represented by a . (not punctuation, but a literal . character).
Notatka: In CVS, this is the default when no revision tag is specified. It is usually not a good idea to checkout or update to CURRENT sources on a STABLE machine, unless that is your intent.
The line of development for FreeBSD-6.X, also known as FreeBSD 6-STABLE
The release branch for FreeBSD-6.1, used only for security advisories and other critical fixes.
The release branch for FreeBSD-6.0, used only for security advisories and other critical fixes.
The line of development for FreeBSD-5.X, also known as FreeBSD 5-STABLE.
The release branch for FreeBSD-5.5, used only for security advisories and other critical fixes.
The release branch for FreeBSD-5.4, used only for security advisories and other critical fixes.
The release branch for FreeBSD-5.3, used only for security advisories and other critical fixes.
The release branch for FreeBSD-5.2 and FreeBSD-5.2.1, used only for security advisories and other critical fixes.
The release branch for FreeBSD-5.1, used only for security advisories and other critical fixes.
The release branch for FreeBSD-5.0, used only for security advisories and other critical fixes.
The line of development for FreeBSD-4.X, also known as FreeBSD 4-STABLE.
The release branch for FreeBSD-4.11, used only for security advisories and other critical fixes.
The release branch for FreeBSD-4.10, used only for security advisories and other critical fixes.
The release branch for FreeBSD-4.9, used only for security advisories and other critical fixes.
The release branch for FreeBSD-4.8, used only for security advisories and other critical fixes.
The release branch for FreeBSD-4.7, used only for security advisories and other critical fixes.
The release branch for FreeBSD-4.6 and FreeBSD-4.6.2, used only for security advisories and other critical fixes.
The release branch for FreeBSD-4.5, used only for security advisories and other critical fixes.
The release branch for FreeBSD-4.4, used only for security advisories and other critical fixes.
The release branch for FreeBSD-4.3, used only for security advisories and other critical fixes.
The line of development for FreeBSD-3.X, also known as 3.X-STABLE.
The line of development for FreeBSD-2.2.X, also known as 2.2-STABLE. This branch is mostly obsolete.
These tags refer to a specific point in time when a particular version of FreeBSD was released. The release engineering process is documented in more detail by the Release Engineering Information and Release Process documents. The src tree uses tag names that start with RELENG_ tags. The ports and doc trees use tags whose names begin with RELEASE tags. Finally, the www tree is not tagged with any special name for releases.
FreeBSD 6.1
FreeBSD 6.0
FreeBSD 5.5
FreeBSD 5.4
FreeBSD 4.11
FreeBSD 5.3
FreeBSD 4.10
FreeBSD 5.2.1
FreeBSD 5.2
FreeBSD 4.9
FreeBSD 5.1
FreeBSD 4.8
FreeBSD 5.0
FreeBSD 4.7
FreeBSD 4.6.2
FreeBSD 4.6.1
FreeBSD 4.6
FreeBSD 4.5
FreeBSD 4.4
FreeBSD 4.3
FreeBSD 4.2
FreeBSD 4.1.1
FreeBSD 4.1
FreeBSD 4.0
FreeBSD-3.5
FreeBSD-3.4
FreeBSD-3.3
FreeBSD-3.2
FreeBSD-3.1
FreeBSD-3.0
FreeBSD-2.2.8
FreeBSD-2.2.7
FreeBSD-2.2.6
FreeBSD-2.2.5
FreeBSD-2.2.2
FreeBSD-2.2.1
FreeBSD-2.2.0
Poprzedni | Spis treści | Następny |
Using Portsnap | Początek rozdziału | AFS Sites |
Ten i inne dokumenty można pobrać z ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/.
W przypadku pytań o FreeBSD prosimy przeczytać dostępną dokumentację przed kontaktem z <questions@FreeBSD.org>.
W sprawie zapytań o tę dokumentację prosimy o kontakt z <doc@FreeBSD.org>.