> 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/life/di-si-bu-fen-unix-zhi-wai/10.-unix-fu-wu/10.8.-yan-zheng.md).

# 10.8 验证

声称一个系统“与 UNIX 兼容”、“符合 System V 接口定义”或“符合 ANSI C”，都是轻而易举的事。但是，除非这些说法经受住了标准机构所规定测试的检验，否则毫无意义。例如，AT\&T 就规定，必须使用 SVVS（System V Verification Suite，System V 验证套件）程序来检验是否符合 SVID。

在 UNIX 标准的背景下，让系统或编译器通过验证或认证，是重要的一步。为 UNIX 和/或 C 提供验证服务的公司有：AT\&T Information Systems、COS（Corporation for Open Systems，开放系统公司）、Human Computing Resources、MindCraft, Inc.、Plum Hall、Software Research, Inc.、Unisoft Corp.，以及诸如美国国家标准局（U.S. National Bureau of Standards）之类的各家国家标准机构。


---

# 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/life/di-si-bu-fen-unix-zhi-wai/10.-unix-fu-wu/10.8.-yan-zheng.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.