> 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.2-release/3.2-errata.md).

# FreeBSD 3.2-RELEASE 勘误

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

`freebsd-stable@FreeBSD.org`

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

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

以获取最新信息。

\---- 安全公告：

当前针对 3.2 的有效安全公告数量：无

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

* compat20 和 compat21 发行版将自身安装到 **/usr/lib/compat**。compat20/compat21 发行版是 a.out 库，因此它们应位于 **/usr/lib/compat/aout**，以匹配 **/etc/defaults/rc.conf** 中的 `ldconfig_paths_aout` 配置。

修复：

```sh
cd /usr/lib/compat
mkdir -p aout
mv lib*.so.*.* aout
```

* `/usr/bin/gdb` 在调试静态程序的核心转储文件时会崩溃。

修复：此问题在 **solib.c** 的 1.3.2.2 版本中修复。可通过 CVSup 获取修复版本（参见手册中的说明），或通过我们的 CVSweb 服务应用补丁。

* 在引导安装软盘时，用户会看到以下消息，并且似乎没有任何反应，也无法从键盘输入任何内容：

```sh
Keyboard: no
```

修复：由于空间不足，启动块中不再提供对旧式 XT/AT（84 键）键盘的完整支持。某些笔记本电脑也可能配备此类键盘，如果你仍在使用此类硬件，从安装 CD-ROM 或软盘引导时你会看到上述未找到键盘的消息。

一旦看到该消息，请按空格键，你将看到以下提示：

```sh
>> FreeBSD/i386 BOOT
Default: x:xx(x,x)/boot/loader
boot:
```

然后输入 `-Dh`，即可使用你的键盘类型正常继续。此情况仅在初始安装时出现一次，之后不会成为问题。

[返回发行版首页](/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.2-release/3.2-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.