> 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-release/2.2-install-media.md).

# FreeBSD 2.2-RELEASE 介质变更公告

来自 <jkh@FreeBSD.org>：

2.2-RELEASE 将不再支持 4MB 内存或 1.2MB 软盘驱动器的安装——也就是说，仅支持大于 5MB 内存和 1.44MB 软盘驱动器的系统。实际上，建议的最小内存为 8MB。

因此，如果你的配置存在上述限制且无法升级，建议继续使用 2.1.6-RELEASE。该版本支持这两种安装方式，在你可能希望继续运行此类系统的整个生命周期内，其功能应该绰绰有余。

对于由此给部分用户带来的不便，我们深表歉意。但安装介质的空间压力已持续一段时间，这一变更或多或少是不可避免的。我们讨论取消 4MB 安装和 1.2MB 软盘支持已超过一年，能够将其全部保留在一张软盘上，完全是靠一些极其精巧的技巧（你不会想知道的）。既然我们已跨越到 1.44MB/大于 6MB 级别的机器，至少为未来的增强功能腾出了一些空间，同时仍保持在一张软盘上。

请注意，你仍然可以构建在 4MB 系统中舒适运行的内核，只是无法在仅有 4MB 内存的机器上进行安装。例如，如果你试图构建一台 4MB 内存且配置精简的定制机器，可以简单地在另一台专门为此目的设置的机器上制作其磁盘。


---

# 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-release/2.2-install-media.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.