> 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-4.0-release/4.0-errata.md).
# FreeBSD 4.0-RELEASE 勘误
如果在安装此版本 FreeBSD 之前你没有阅读任何其他文档，那么至少务必**阅读本发行版的勘误**，以免在已经发现并修复的问题上绊倒。此 ERRATA.TXT 文件按定义显然已经过时，但网络上的其他副本会保持更新，应作为你的发行版的“当前勘误”查阅。这些其他勘误副本位于：
1.
2. **ftp\://ftp.FreeBSD.org/pub/FreeBSD/releases//ERRATA.TXT**（以及任何保持此位置最新镜像的站点）。
对此文件的任何更改也会自动发送电子邮件至：
`freebsd-current@FreeBSD.org`
有关所有 FreeBSD 安全公告，请参见：
以获取最新的安全事件信息。
\---- 安全公告：
当前有效的安全公告：无
\---- 系统更新信息：
bin 发行版中的 `tcpdump` 二进制文件错误地链接到了 `libcrypto.so` 库，而该库仅存在于单独的 crypto 发行版中。
因此，如果你只安装了 bin 发行版而未安装 crypto 发行版，`tcpdump` 将无法正常工作。
修复：从以下位置下载新的 `tcpdump` 二进制文件：
（i386） （alpha）
此文件的 MD5 校验和为：
i386 版本：MD5 (tcpdump) = 0b3d32b367e7312d546ccae8f1824391 alpha 版本：MD5 (tcpdump) = 2d113fa4c38c8a0299d558acb5c6ad57
要验证你下载的副本的校验和，请执行以下命令：
```sh
/sbin/md5 /path/to/downloaded/tcpdump
```
并与上述值进行比较。
* `install.sh` 未安装工具源代码（`sysinstall` 之外）
如果你试图从 CDROM 中提取完整源代码（在 `sysinstall` 程序之外），最终会缺少工具源代码。
修复：如果你从 **/cdrom/src** 运行 `install.sh`，还需要运行：
```sh
cat stool.?? | tar --unlink -xpzf - -C /usr/src
```
以安装工具源代码（**/usr/src/tools** 层级目录）。这些源代码是成功构建 world 所必需的。
[返回发行版首页](/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-4.0-release/4.0-errata.md?ask=&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.