> 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/zfs/an-zhuang-zhi-yin/arch-linux/index.md).

# 在 Arch Linux 中启用 ZFS 支持

## 支持

你可以通过[邮件列表](/zfs/xiang-mu-yu-she-qu/mailinglists.md)或 Libera Chat 上的 `#zfsonlinux` IRC 频道与社区取得联系。

如果对本指南有错误报告或功能建议，请[提交新 issue 并提及 @ne9z](https://github.com/openzfs/openzfs-docs/issues/new?body=@ne9z,%20I%20have%20the%20following%20issue%20with%20the%20Arch%20Linux%20ZFS%20HOWTO:)。

## 概览

由于许可不兼容，ZFS 并未包含在 Arch Linux 官方仓库中。

ZFS 支持由第三方 [archzfs 仓库](https://github.com/archzfs/archzfs) 提供。

## 安装

参见 [Archlinux Wiki](https://wiki.archlinux.org/title/ZFS)。

## 以 ZFS 为根文件系统

ZFS 可以作为 Arch Linux 的根文件系统使用。安装指南参见[构建以 ZFS 为根文件系统的 Arch Linux](/zfs/an-zhuang-zhi-yin/arch-linux/archlinuxroot.md)。

## 参与贡献

1. Fork 并克隆[本仓库](https://github.com/openzfs/openzfs-docs)。
2. 安装工具：

   ```sh
   sudo pacman -S --needed python-pip make

   pip3 install -r docs/requirements.txt

   # 将 ~/.local/bin 添加到 "${PATH}"，例如在 ~/.bashrc 中加入：
   [ -d "${HOME}"/.local/bin ] && export PATH="${HOME}"/.local/bin:"${PATH}"
   ```
3. 完成你的修改。
4. 测试：

   ```sh
   cd docs
   make html
   sensible-browser _build/html/index.html
   ```
5. 使用 `git commit --signoff` 提交到分支，`git push`，然后创建 PR 并提及 @ne9z。


---

# 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/zfs/an-zhuang-zhi-yin/arch-linux/index.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.