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

# FreeBSD 2.2.8-RELEASE 勘误

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

<freebsd-stable@FreeBSD.org>

2.2.8 的安全公告请参见：

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

以获取最新信息。

## 安全公告

2.2.8 当前有效的安全公告：无

## 系统更新信息

* **/usr/sbin/sysctl** 是无效链接，**whereis(1)** 无法工作。

  修复：**sysctl(8)** 实际上已移至 **/sbin/sysctl**。只需创建符号链接以兼容：

  ```sh
  ln -sf /sbin/sysctl /usr/sbin
  ```

  或者将你的源码同步至 2.2-stable 并从 **/usr/src/usr.bin/whereis/** 重新构建/安装，然后删除 **/usr/sbin/sysctl**。
* **/usr/share/doc/FAQ** 是西班牙语的。

  修复：这是一个仅影响 FAQ 的构建失败，此后修复完成。如果你已经在通过 `cvsup`/`CTM` 同步 `doc-all` 标签，则可以直接从源码重新制作并安装 FAQ。否则，获取 <ftp://ftp.FreeBSD.org/pub/FreeBSD/doc/FAQ.tar.gz> 并按以下方式解压：

  ```sh
  tar --unlink -xvzf FAQ.tar.gz -C /usr/share/doc
  ```

  以获取英文 FAQ。
* **getpwnam(3)** 语义在某些情况下不正确。

  修复：如果传入的字符串长度超过用户名允许的最大长度，`getpwnam` 会错误地返回用户条目，该用户名与字符串开头到最大允许长度之间的字符匹配。要纠正此行为，需要对 libc 打补丁并重新编译。相应的补丁可从以下地址获取：

  `http://cvsweb.FreeBSD.org/src/lib/libc/gen/getpwent.c.diff?r1="1".35.2.2&r2="1".35.2.3`


---

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