> 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/release/freebsd-2.0-release/2.0-credits.md).

# FreeBSD 2.0-RELEASE 贡献者名单

**FreeBSD 2.0** **贡献者名单**

## 派生软件贡献者

本软件最初派生自 William F. Jolitz 的 386BSD 0.1 版本，但几乎所有的 386BSD 特定代码均不复存在。本软件基本上是在加州大学伯克利分校计算机系统研究组（CSRG）的 4.4 BSD Lite 基础上重新实现的，同时也包含了相关学术贡献者的工作。

其中也融入了 NetBSD 的部分代码，因此我们要感谢所有为 NetBSD 做出贡献的开发者。尽管两个团队之间的关系偶尔有些波折，但双方的目标本质上是一致的：让更多基于 BSD 的操作系统运行在用户的计算机上！我们祝愿 NetBSD 团队在各项事业中取得圆满成功。

## 硬件贡献者

特别感谢 Walnut Creek CDROM 提供了用于开发工作的 486/DX2-66 EISA/VL 系统，更不用说网络接入和其他硬件资源的捐赠。没有他们的支持，完成这一版本是不可能的。

还要感谢 Dermot McDonnell 捐赠了 Toshiba XM3401B CDROM 驱动器，它一直非常有用！

## FreeBSD 核心团队（按字母顺序排列）

* Andreas Schulz <ats@g386bsd.first.bmd.de>
* Andrew A. Chernov <ache@astral.msk.su>
* Bruce Evans <bde@FreeBSD.org>
* David Greenman <davidg@Root.COM>
* Garrett A. Wollman <wollman@freefall.cdrom.com>
* Gary Palmer <gpalmer@FreeBSD.org>
* Geoff Rehmet <csgr@cs.ru.ac.za>
* Jack Vogel <jackv@FreeBSD.org>
* John Dyson <dyson@implode.rain.com>
* Jordan K. Hubbard <jkh@FreeBSD.org>
* Paul Richards <paul@isl.cf.ac.uk>
* Poul-Henning Kamp <phk@FreeBSD.org>
* Rich Murphey <rich@lamprey.utmb.edu>
* Rodney W. Grimes <rgrimes@cdrom.com>
* Soren Schmidt <sos@FreeBSD.org>

## 其他 FreeBSD 贡献者（排名不分先后）

* Adam Glass <glass@postgres.berkeley.edu>
* Andrew Herbert <andrew@werple.apana.org.au>
* Andrew Moore <alm@FreeBSD.org>
* Atsushi Murai <amurai@spec.co.jp>
* Bob Wilcox <bob@obiwan.uucp>
* Bruce Evans <bde@kralizec.zeta.org.au>
* Charles Hannum <mycroft@ai.mit.edu>
* Chris G. Demetriou <cgd@postgres.berkeley.edu>
* Chris Torek <torek@ee.lbl.gov>
* Christoph Robitschko <chmr@edvz.tu-graz.ac.at>
* Curt Mayer <curt@toad.com>
* Dave Burgess <burgess@hrd769.brooks.af.mil>
* Dave Rivers <rivers@ponds.uucp>
* David Dawes <dawes@physics.su.OZ.AU>
* Frank Maclachlan <fpm@crash.cts.com>
* Gary A. Browning <gab10@griffcd.amdahl.com>
* Gary Clark II <gclarkii@radon.gbdata.com>
* Guido van Rooij <guido@gvr.win.tue.nl>
* Havard Eidnes <Havard.Eidnes@runit.sintef.no>
* Holger Veit <Holger.Veit@gmd.de>
* Ishii Masahiro, R. Kym Horsell
* J.T. Conklin <jtc@winsey.com>
* James Clark <jjc@jclark.com>
* James da Silva <jds@cs.umd.edu> et al
* Jim Wilson <wilson@moria.cygnus.com>
* Joerg Wunsch <joerg_wunsch@uriah.sax.de>
* Julian Elischer <julian@dialix.oz.au>
* Julian Stacey <stacey@guug.de> \<fallback: <julian@meepmeep.pcs.com>>
* Keith Bostic <bostic@toe.CS.Berkeley.EDU>
* Keith Moore \<?>
* Marc Frajola <marc@escargot.rain.com>
* Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu>
* Martin Birgmeier
* Paul Kranenburg <pk@cs.few.eur.nl>
* Paul Mackerras <paulus@cs.anu.edu.au>
* Poul-Henning Kamp <phk@login.dkuug.dk>
* Rob Shady <rls@id.net>
* Sascha Wildner <swildner@channelz.GUN.de>
* Scott Mace <smace@FreeBSD.org>
* Sean Eric Fagan <sef@kithrup.com>
* Serge V. Vakulenko <vak@zebub.msk.su>
* Steven Wallace <swallace@ece.uci.edu>
* Søren Schmidt <sos@login.dkuug.dk>
* Terry Lee <terry@uivlsi.csl.uiuc.edu>
* Theo Deraadt <deraadt@fsa.ca>
* Ugen J.S.Antsilevich <ugen@NetVision.net.il>
* Yuval Yarom <yval@cs.huji.ac.il>

## 386BSD 补丁包贡献者（排名不分先后）

* Adam Glass <glass@postgres.berkeley.edu>
* Adrian Hall <adrian@ibmpcug.co.uk>
* Andrew A. Chernov <ache@astral.msk.su>
* Andrew Herbert <andrew@werple.apana.org.au>
* Andrew Moore <alm@netcom.com>
* Andy Valencia <ajv@csd.mot.com> <jtk@netcom.com>
* Arne Henrik Juul <arnej@Lise.Unit.NO>
* Bakul Shah <bvs@bitblocks.com>
* Barry Lustig <barry@ictv.com>
* Bob Wilcox <bob@obiwan.uucp>
* Branko Lankester
* Brett Lymn <blymn@mulga.awadi.com.AU>
* Bruce Evans <bde@kralizec.zeta.org.au>
* Charles Hannum <mycroft@ai.mit.edu>
* Chris G. Demetriou <cgd@postgres.berkeley.edu>
* Chris Torek <torek@ee.lbl.gov>
* Christoph Robitschko <chmr@edvz.tu-graz.ac.at>
* Daniel Poirot <poirot@aio.jsc.nasa.gov>
* Dave Burgess <burgess@hrd769.brooks.af.mil>
* Dave Rivers <rivers@ponds.uucp>
* David Dawes <dawes@physics.su.OZ.AU>
* David Greenman <davidg@Root.COM>
* Eric J. Haug <ejh@slustl.slu.edu>
* Felix Gaehtgens <felix@escape.vsse.in-berlin.de>
* Frank Maclachlan <fpm@crash.cts.com>
* Gary A. Browning <gab10@griffcd.amdahl.com>
* Geoff Rehmet <csgr@alpha.ru.ac.za>
* Goran Hammarback <goran@astro.uu.se>
* Guido van Rooij <guido@gvr.win.tue.nl>
* Guy Harris <guy@auspex.com>
* Havard Eidnes <Havard.Eidnes@runit.sintef.no>
* Herb Peyerl <<hpeyerl@novatel.cuc.ab.ca>
* Holger Veit <Holger.Veit@gmd.de>
* Ishii Masahiro, R. Kym Horsell
* J.T. Conklin <jtc@winsey.com>
* Jagane D Sundar < <jagane@netcom.com> >
* James Clark <jjc@jclark.com>
* James Jegers <jimj@miller.cs.uwm.edu>
* James W. Dolter
* James da Silva <jds@cs.umd.edu> et al
* Jay Fenlason <hack@datacube.com>
* Jim Wilson <wilson@moria.cygnus.com>
* Joerg Lohse <lohse@tech7.informatik.uni-hamburg.de>
* Joerg Wunsch <joerg_wunsch@uriah.sax.de>
* John Dyson - \<formerly <dyson@ref.tfs.com>>
* John Woods <jfw@eddie.mit.edu>
* Jordan K. Hubbard <jkh@whisker.hubbard.ie>
* Julian Elischer <julian@dialix.oz.au>
* Julian Stacey <stacey@guug.de> \<fallback: <julian@meepmeep.pcs.com>>
* Karl Lehenbauer <karl@NeoSoft.com> <karl@one.neosoft.com>
* Keith Bostic <bostic@toe.CS.Berkeley.EDU>
* Ken Hughes
* Kent Talarico <kent@shipwreck.tsoft.net>
* Kevin Lahey <kml%rokkaku.UUCP@mathcs.emory.edu> <kml@mosquito.cis.ufl.edu>
* Marc Frajola <marc@escargot.rain.com>
* Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu>
* Martin Renters <martin@innovus.com>
* Michael Galassi <nerd@percival.rain.com>
* Mike Durkin <mdurkin@tsoft.sf-bay.org>
* Nate Williams <nate@bsd.coe.montana.edu>
* Nick Handel <nhandel@NeoSoft.com> <nick@madhouse.neosoft.com>
* Pace Willisson <pace@blitz.com>
* Paul Kranenburg <pk@cs.few.eur.nl>
* Paul Mackerras <paulus@cs.anu.edu.au>
* Paul Popelka <paulp@uts.amdahl.com>
* Peter da Silva <peter@NeoSoft.com>
* Phil Sutherland <philsuth@mycroft.dialix.oz.au>
* Poul-Henning Kamp <phk@login.dkuug.dk>
* Ralf Friedl <friedl@informatik.uni-kl.de>
* Rich Murphey <rich@lamprey.utmb.edu>
* Rick Macklem <root@snowhite.cis.uoguelph.ca>
* Robert D. Thrush <rd@phoenix.aii.com>
* Rodney W. Grimes <rgrimes@cdrom.com>
* Rog Egge \<?>
* Sascha Wildner <swildner@channelz.GUN.de>
* Scott Burris <scott@pita.cns.ucla.edu>
* Scott Reynolds <scott@clmqt.marquette.mi.us>
* Sean Eric Fagan <sef@kithrup.com>
* Simon J Gerraty <sjg@melb.bull.oz.au> <sjg@zen.void.oz.au>
* Stephen McKay <robert@psych.psy.uq.oz.au>
* Terry Lambert <terry@icarus.weber.edu>
* Terry Lee <terry@uivlsi.csl.uiuc.edu>
* Warren Toomey <wkt@csadfa.cs.adfa.oz.au>
* Wiljo Heinen <wiljo@freeside.ki.open.de>
* William Jolitz
* Wolfgang Solfrank <ws@tools.de>
* Wolfgang Stanglmeier <wolf@dentaro.GUN.de>
* Yuval Yarom <yval@cs.huji.ac.il>

```ini
Id: CONTRIB.FreeBSD,v 1.1 1994/11/18 12:03:25 jkh Exp
```


---

# 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/release/freebsd-2.0-release/2.0-credits.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.
