> For the complete documentation index, see [llms.txt](https://freebsd-journal-cn.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://freebsd-journal-cn.bsdcn.org/20170708-zi-yuan-kong-zhi/letter-from-the-foundation.md).

# 基金会致信

来自编辑委员会的信

欢迎来到 FreeBSD 期刊的夏末刊——至少从我所在的英国剑桥来看是夏末。下周就是 BSDCam，这是每年 8 月学生离校、教授们撒欢时举办的 FreeBSD 开发者峰会——撒欢的程度仅限教授们能撒到的范围。Summit 结束后我们会有更多内容分享，但现在先来看看本期为你准备了什么——你在海滩或任何阅读期刊的地方放松时可以读一读。

过去一两年，读到关于虚拟化和操作系统的内容，几乎不可能不遇到 Docker。任何新技术都会引来下一个理所当然的问题：“FreeBSD 呢？”Kurt Lidl 用一篇关于 Docker 与 FreeBSD 的概述来回答这个问题，不仅涵盖现状，也展望了 FreeBSD 与 Docker 的未来。

接下来，FreeBSD 期刊与 FreeBSD 基金会董事会成员 Benedict Reuschling 采访了 TrueOS 项目的 Joe Maloney，谈谈 TrueOS 最新发行版中部署的新 OpenRC 系统。

Pawel Jakub Dawidek 与 Milosz Kaniewski 讲述他们如何用 FreeBSD 进行网络流量分析，深入 TLS 加密流。许多人对 bhyve——FreeBSD 原生 hypervisor——和 ZFS——这一泽字节文件系统——并不陌生。Trent Thompson 撰文介绍 iohyve，它把这两项技术结合在一起，让你的系统部署工作更轻松。

本期还以三个专栏收尾：New Faces——Dru Lavigne 与两位新 Ports 提交者对谈；SVN 动态——Steven Kreuzer 带我们看看 FreeBSD 中所有崭新且闪亮的内容；以及 Roller Angel 撰写的 BSDCan 会议报告。想知道接下来 FreeBSD 还有哪些活动？Dru Lavigne 的活动日历会告诉你 FreeBSD 人在全球何处相聚。

***

**George Neville-Neil**

FreeBSD 基金会董事会主席


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://freebsd-journal-cn.bsdcn.org/20170708-zi-yuan-kong-zhi/letter-from-the-foundation.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.