> 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/release/freebsd-3.1-release/3.1-errata.md).

# FreeBSD 3.1-RELEASE 勘误

文件 `ERRATA.TXT` 包含 3.1 发行后的勘误信息，在报告本发行版的问题之前，应始终将其视为首先查阅的权威来源。此文件也会随着新问题的报告而定期更新，因此即使你最近查看过此文件，在提交错误报告之前也请再次查阅。对此文件的任何更改也会自动发送电子邮件至：

`freebsd-stable@FreeBSD.org`

有关所有 FreeBSD 安全公告，请参见：

**ftp\://ftp.FreeBSD.org/pub/FreeBSD/CERT/**

以获取最新信息。

\---- 安全公告：

当前针对 3.1 的有效安全公告：无

\---- 系统更新信息：

* 某些软件包（如 netscape）如果在初始系统安装时选择安装，将无法安装成功，在某些情况下会声称需要安装“compat22”发行版，即便它实际上安装完成。

修复：此问题在于，虽然兼容 a.out 库可能已从 compat22 安装并作为 XFree86 发行版的一部分，但 a.out 库（ldconfig）缓存尚未构建，因为只有在系统至少完全启动一次后才会构建。这会导致需要旧 a.out 库的软件包（如 netscape）在缓存构建完成之前安装时出现混乱。要解决此问题，只需正常完成安装并完全启动系统，然后重新运行 **/stand/sysinstall**（或直接使用 **pkg\_add(1)** 命令）重新安装失败的软件包。

* 内核更改信息未保存到新内核中，尽管文档声称此功能可正常工作。

修复：更改信息实际上已写出，但写到了错误的位置。将 **/kernel.config** 移动到 **/boot/kernel.conf**（如果存在；否则说明没有需要保存的更改），并在 **/boot/loader.rc** 中添加以下行：

```sh
load /kernel
load -t userconfig_script /boot/kernel.conf
autoboot 5
```

这将使内核更改信息正确读取和使用（你也在此过程中了解了新的 3 阶段加载器的一些知识，所以这次操作并非全无所获）。

* 当你按照说明在 **C:\FREEBSD\BIN...** 等位置安装内容时，DOS 安装会失败。

修复：说明是正确的，但 3.1-RELEASE 中的代码有误，sysinstall 直接在 *C:\* 下（如 **C:\BIN...**）或\*\*C:\RELEASES\** 下（**C:\RELEASES\BIN...** 等）查找。此问题在 3.1-STABLE 中修复完成。

[返回发行版首页](/release/readme.md)


---

# 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/release/freebsd-3.1-release/3.1-errata.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.