> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/handbook/di-27-zhang-freebsd-geng-xin-yu-sheng-ji/27.2.-jie-shao.md).

# 27.2.介绍

## 27.2.1. 主要版本与次要版本

自 FreeBSD 6.0-RELEASE 起，FreeBSD 发行版严格遵循两级版本编号方案。我们使用“主要版本”一词指代版本号的第一部分，例如“14.3-RELEASE”中的“14”；使用“次要版本”一词指代版本号的第二部分，例如“14.3-RELEASE”中的“3”。

此外，FreeBSD 发行分支还有一个补丁级别，为零时省略，每发布一批安全公告与勘误通知时递增，例如“14.3-RELEASE-p7”表示为 FreeBSD 14.3 发布的第七批补丁。

由于 [FreeBSD 支持模式](https://www.FreeBSD.org/security/#model) 的缘故，FreeBSD 的版本号在同一主要版本内单调递增，但在不同主要版本之间并非如此。例如，FreeBSD 14.2-RELEASE、13.5-RELEASE、14.3-RELEASE、15.0-RELEASE、14.4-RELEASE 和 15.1-RELEASE 就是按此顺序发布的。

## 27.2.2. “更新”与“升级”

我们使用“更新”一词描述应用安全或勘误补丁，这类补丁可能会增加补丁级别，但不会改变版本号；使用“升级”一词描述将整个基本系统替换为版本号不同的另一个基本系统。

## 27.2.3. 升级路径

安装完成后，可以使用[二进制补丁](https://book.bsdcn.org/handbook/di-27-zhang-freebsd-geng-xin-yu-sheng-ji/27.3.-geng-xin-freebsd.md)、[软件包](https://book.bsdcn.org/handbook/di-27-zhang-freebsd-geng-xin-yu-sheng-ji/27.8.-pkgbase.md)或[从源代码](https://book.bsdcn.org/handbook/di-27-zhang-freebsd-geng-xin-yu-sheng-ji/27.7.-cong-yuan-dai-ma-geng-xin-freebsd.md)来更新或升级 FreeBSD。无论采用哪种方式，FreeBSD 仅支持从时间上较早的版本更新或升级到较新的版本。

具体而言，FreeBSD 支持更新到同一版本的较新补丁级别，或从给定版本升级到同一主要版本的较新次要版本（例如从 14.3 升级到 14.4），或升级到下一个主要版本的较新版本（例如从 14.3 升级到 15.0 或 15.1）。不建议也不支持移动到同一主要版本的较旧发行版（例如从 14.4 降回 14.3）、移动到下一个主要版本的较旧发行版（例如从 2026 年 3 月发布的 14.4 移动到三个月前即 2025 年 12 月发布的 15.0），或跳过主要版本（例如从 13.5 升级到 15.1），即使工具允许这样做。


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://book.bsdcn.org/handbook/di-27-zhang-freebsd-geng-xin-yu-sheng-ji/27.2.-jie-shao.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
