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

# FreeBSD 2.2.7-RELEASE 勘误

文件 **ERRATA.TXT** 包含 2.2.7 的发布后勘误，在报告此版本的问题之前，应始终**首先**查阅此文件。此文件也会随着新问题的报告而定期更新，因此即使你最近已经查阅过，在提交漏洞报告前请再次检查。对此文件的任何更改也会自动发送邮件至：

<freebsd-stable@FreeBSD.org>

2.2.7 的安全公告请参见：

<ftp://ftp.FreeBSD.org/pub/FreeBSD/CERT/>

以获取最新信息。

## 安全公告

2.2.7 当前活动的安全公告：无

## 系统更新信息

* XFree86：如果你在系统安装期间运行 `XF86Setup` 工具，它有时会以 XIO 错误（在第二个 VTY 上可见）失败，而不是正常启动。这不是一个新漏洞，在以前的 FreeBSD 版本中也出现过，但在 2.2.7 中似乎更容易复现（原因尚不清楚）。

  修复：如果遇到此情况，请在系统首次从硬盘引导后手动运行 **/usr/X11R6/bin/XF86Setup**。由于某种原因，当不从引导软盘或 CD 运行时，它能完美工作（这使得该问题更难调试）。
* 发行说明中称 Texas Instruments ThunderLAN PCI 网卡在 2.2.7 中受支持。

  修复：这是一次令人尴尬的误合并，源自 3.0 发行说明，实际上这些网卡仅在 3.0-current 中受支持。请忽略发行说明中此部分以及任何其他声称 ThunderLAN 网卡在 2.2.7 中受支持的文档。
* `rshd` 在 `-Wall` 清理过程中损坏，如 `PR#7500` 中所述。

  修复：此问题已于 1998/07/24 04:32:21 在 2.2-stable 分支的 **/usr/src/libexec/rshd/rshd.c** 修订版 1.9.2.9 中修复。通过 CVSup 获取修复版本（参见 handbook 中的说明，或直接执行 `pkg_add ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CVSup/cvsupit.tgz` 并按照说明操作），或从 FTP 获取：

  <ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-stable/src/libexec/rshd/rshd.c>


---

# 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-2.2.7-release/2.2.7-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.