> 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.1-release/2.1-announce.md).

# FreeBSD 2.1-RELEASE 发行公告

**日期**：1995 年 11 月 19 日（星期日）14:48:46 -0800 **发件人**：“Jordan K. Hubbard” <<jkh@freebsd.org>> **收件人**：<announce@freefall.cdrom.com> **主题**：2.1.0-RELEASE 现已发布！

这可能吗？期待已久的 FreeBSD 2.1 真的到来了吗？

我很高兴地用一句“是的！”来回答这些问题。

FreeBSD 2.1.0-RELEASE 现已在 [ftp.freebsd.org](ftp://ftp.freebsd.org/pub/FreeBSD/2.1.0-RELEASE/) 及全球各 FTP [镜像站点](https://www.freebsd.org/handbook/mirrors.html) 上提供。也可从 [Walnut Creek CDROM](http://www.cdrom.com/) 订购 CD 版本，即将开始发货。

FreeBSD 2.1 代表了自上一个版本（FreeBSD 2.0.5）以来，在 FreeBSD 的 2.1-STABLE 分支上 6 个月工作的成果。

STABLE 分支的设立源于这样一种需求：允许 FreeBSD 发展并支持 devfs、NFSv3、IPX、PCCARD 等长期开发项目，同时又不影响现有用户群的稳定性。实验性或高影响的变更会被纳入 [FreeBSD-current](https://www.freebsd.org/handbook/current.html)——它相当于一种共享的群体开发树，而只有经过充分测试或显而易见的修复才会被纳入 STABLE。在少数情况下，某些功能此前完全缺失，我们在 STABLE 中提供了 ALPHA 测试质量的版本，前提是有总比没有好（IDE CDROM 驱动就是一个典型的例子）。

有关 2.1 版本本身的更多信息，请参阅随 [安装过程](https://www.freebsd.org/handbook/install.html) 附带的文档。

Jordan


---

# 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.1-release/2.1-announce.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.