# Page Not Found

The URL `di-5-zhang-freebsd-ji-chu/di-5.5-jie-xu-ni-kong-zhi-tai-he-zhong-duan` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [6.1 虚拟控制台和终端](https://book.bsdcn.org/di-6-zhang-ming-ling-xing-huan-jing/di-6.1-jie-xu-ni-kong-zhi-tai-he-zhong-duan.md)
- [2.1 FreeBSD：理想、现实与中道](https://book.bsdcn.org/di-2-zhang-freebsd-dao-lun/di-2.1-jie-freebsd-li-xiang-xian-shi-yu-zhong-dao.md)
- [4.1 安装前的准备工作](https://book.bsdcn.org/di-4-zhang-freebsd-an-zhuang-ji-chu/di-4.1-jie-an-zhuang-qian-de-zhun-bei-gong-zuo.md)
- [42.6 构建定制内核](https://book.bsdcn.org/di-42-zhang-freebsd-nei-he-jia-gou/di-42.6-jie-gou-jian-ding-zhi-nei-he.md)
- [3.2 Linux 用户迁移指南](https://book.bsdcn.org/di-3-zhang-qian-yi-zhi-nan/di-3.2-jie-linux-yong-hu-qian-yi-zhi-nan.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://book.bsdcn.org/di-6-zhang-ming-ling-xing-huan-jing/di-6.1-jie-xu-ni-kong-zhi-tai-he-zhong-duan.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://book.bsdcn.org/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://book.bsdcn.org/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/di-6-zhang-ming-ling-xing-huan-jing/di-6.1-jie-xu-ni-kong-zhi-tai-he-zhong-duan.md`).

You may also use `Accept: text/markdown` header for content negotiation.