> 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.2.-zi-xun.md).

# 10.2 咨询

UNIX 固然是个了不起的系统，但总有一天，你会需要完成一件以前从没人做过的事，而你自己又做不来。也许你只需要一点定制；也许你需要一些信息，好让手头的工作继续下去。这时，咨询就是答案。

咨询顾问来自四面八方。UNIX 厂商常常养着一支可供雇佣的团队，专门解决与自家系统有关的问题。这可不是什么推脱的退路。与其事先猜测客户会需要什么，不如在系统设计完成之后留一批人来处理问题，这样反而更省事。

咨询顾问也来自独立公司，规模从几百人一直到只有一个人不等。大公司往往一遍又一遍地提供相似的解决方案，比如移植某个产品。对某些类型的问题，与他们合作比养自己的员工更省钱。我们认识的许多咨询顾问，都曾在同一个地方一待就是一年以上，与全职员工并肩工作。

把咨询服务外包出去时，务必精确写明你的需求。你把需求界定得越明确，公司就越容易找到符合你要求的人。

一些提供 UNIX 咨询的知名独立公司有：Abmind Corporation、Acorn Systems, Ltd.、Daniel Farkas and Associates、Datix Systems、D.L. Buck & Associates、Lachman Associates Inc.、Parkridge Computer Systems Inc.、Sobell Associates、Specialized Systems Consultants Inc.、Unidot Inc. 以及 Unisolutions Associates。

小型咨询公司还有很多，有的只有一个人。这类公司很难一概而论：他们可能是学生，可能是手头拮据、业余偷偷接活的程序员，也可能恰恰是最顶尖的 UNIX 巫师。有些颇为能干的 UNIX 程序员，背后不需要任何全职班子替他们揽活——他们的本事大到光靠口碑，就足以让自己想干多久，便一直有活干到多久。

想找到合格的独立顾问，最稳妥的办法是向其他使用同类系统的站点打听。


---

# 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.2.-zi-xun.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.