# Page Not Found

The URL `di-23-zhang-wen-jian-xi-tong-yu-ci-pan-guan-li/di-23.6-jie-ext-234-deng-wen-jian-xi-tong` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [26.1 Windows 文件系统](https://book.bsdcn.org/di-26-zhang-qi-ta-wen-jian-xi-tong/di-26.1-jie-windows-wen-jian-xi-tong.md)
- [26.2 Linux 文件系统](https://book.bsdcn.org/di-26-zhang-qi-ta-wen-jian-xi-tong/di-26.2-jie-linux-wen-jian-xi-tong.md)
- [26.3 macOS 文件系统](https://book.bsdcn.org/di-26-zhang-qi-ta-wen-jian-xi-tong/di-26.3-jie-macos-wen-jian-xi-tong.md)
- [23.6 ESP-IDF 开发环境](https://book.bsdcn.org/di-23-zhang-qian-ru-shi-ping-tai-ji-kai-fa-huan-jing/di-23.6-jie-esp-idf-kai-fa-huan-jing.md)
- [28.9 ZFS 启动环境](https://book.bsdcn.org/di-28-zhang-zfs-wen-jian-xi-tong/di-28.9-jie-zfs-qi-dong-huan-jing.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-26-zhang-qi-ta-wen-jian-xi-tong/di-26.1-jie-windows-wen-jian-xi-tong.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-26-zhang-qi-ta-wen-jian-xi-tong/di-26.1-jie-windows-wen-jian-xi-tong.md`).

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