> 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/4.3-bsd-unix-cao-zuo-xi-tong-she-ji-yu-shi-xian/readme.md).

# README

《4.3BSD UNIX 操作系统的设计与实现》（*The Design and Implementation of the 4.3BSD UNIX Operating System*）简体中文翻译项目，由 FreeBSD 中文社区译制，基于 GitBook 格式发布。

## 关于本书

* 原书：*The Design and Implementation of the 4.3BSD UNIX Operating System*
* 作者：Samuel J. Leffler、Marshall Kirk McKusick、Michael J. Karels、John S. Quarterman
* 出版：Addison-Wesley，1989 年
* 篇幅：5 个部分共 13 章，另有词汇表与索引，中文章号与原书 1:1 对应

本书是关于 Berkeley UNIX（BSD）内核设计与实现的权威著作：从 UNIX 历史与设计目标讲起，依次剖析内核服务、进程管理与内存管理、I/O 系统（描述符、文件系统、设备驱动、终端处理）、进程间通信与网络协议栈，最后以系统启动流程收尾。书中对 4.3BSD 内核数据结构、算法与权衡取舍的论述，是后续《4.4BSD 操作系统的设计与实现》一书的直接前身。

## 关于译本

* 术语以[译者说明与全局术语表](https://github.com/FreeBSD-Ask/4.3BSD/tree/main/yi-zhe-shuo-ming.md)为准，并尽量与《4.4BSD 操作系统的设计与实现》官方中译本保持一致。
* 原书各章末的习题（Exercises）照译；参考文献（References）保留英文原样。
* 原书版权页与商标说明页保留英文原文，不作翻译。
* 翻译与校对进度见 [PROJECT-PROGRESS.md](https://github.com/FreeBSD-Ask/4.3BSD/tree/main/PROJECT-PROGRESS.md)，里程碑见 [CHANGELOG.md](https://github.com/FreeBSD-Ask/4.3BSD/tree/main/CHANGELOG.md)。

## 许可

译文以 BSD 2-Clause 许可发布，见 [LICENSE](https://github.com/FreeBSD-Ask/4.3BSD/tree/main/LICENSE/README.md)。


---

# 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/4.3-bsd-unix-cao-zuo-xi-tong-she-ji-yu-shi-xian/readme.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.