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

# FreeBSD 3.0-RELEASE 勘误

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

`freebsd-stable@FreeBSD.org`

有关 3.0 的安全公告，请参见：

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

以获取最新信息。

\---- 安全公告：

当前针对 3.0 的有效安全公告：1

* SA-98:08: IP 分片拒绝服务

修复：升级至 3.0-current 或应用 98:08 公告中提供的补丁，地址为：

**ftp\://ftp.FreeBSD.org/pub/FreeBSD/CERT/advisories/FreeBSD-SA-98:08.fragment.asc**

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

* `GPL_MATH_EMULATE` 内核选项在系统启动期间会导致致命陷阱。

修复：将选项 `GPL_MATH_EMULATE` 替换为默认的数学仿真选项 `MATH_EMULATE`。这仅影响修改过内核配置文件的用户。该问题在文件 **/usr/src/sys/gnu/i386/fpemul/fpu\_entry.c** 的 1.16 版本中修复完成。

* DOS 分区安装无法找到安装文件。

修复：将 **C:\FREEBSD** 重命名为 **C:\3.0-RELEASE** 并重新尝试安装。此命名语法是为了使 DOS 安装与其他类型的安装介质更加相似而更改的，但有关 DOS 安装的文档未能正确更新以反映此更改。当前的 sysinstall 现在接受这两个位置，本应如此。

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