aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDoc Manager <doceng@FreeBSD.org>2000-11-21 10:28:00 +0000
committerDoc Manager <doceng@FreeBSD.org>2000-11-21 10:28:00 +0000
commit49bcfc06a6ff4c91ddca135602a37eb1c2bdc059 (patch)
tree27ff750a22725cc0b66e947fdb457ed1b127b2d5
parenta1548d0e3a573552e48642427219bb11815e0618 (diff)
downloaddoc-49bcfc06a6ff4c91ddca135602a37eb1c2bdc059.tar.gz
doc-49bcfc06a6ff4c91ddca135602a37eb1c2bdc059.zip
Create tag '4.2.0'.release/4.2.0
Notes
Notes: svn path=/head/; revision=8401 svn path=/release/4.2.0/; revision=8402; tag=release/4.2.0
-rw-r--r--de_DE.ISO8859-1/Makefile8
-rw-r--r--de_DE.ISO8859-1/books/Makefile13
-rw-r--r--de_DE.ISO8859-1/books/Makefile.inc8
-rw-r--r--de_DE.ISO8859-1/books/handbook/Makefile37
-rw-r--r--de_DE.ISO8859-1/books/handbook/appendix.decl1
-rw-r--r--de_DE.ISO8859-1/books/handbook/backups/chapter.sgml848
-rw-r--r--de_DE.ISO8859-1/books/handbook/basics/chapter.sgml581
-rw-r--r--de_DE.ISO8859-1/books/handbook/bibliography/chapter.sgml485
-rw-r--r--de_DE.ISO8859-1/books/handbook/book.sgml114
-rw-r--r--de_DE.ISO8859-1/books/handbook/chapter.decl1
-rw-r--r--de_DE.ISO8859-1/books/handbook/chapters.ent21
-rw-r--r--de_DE.ISO8859-1/books/handbook/mailing-lists.ent114
-rw-r--r--de_DE.ISO8859-1/books/handbook/newsgroups.ent10
-rw-r--r--de_DE.ISO8859-1/books/handbook/ports/chapter.sgml1050
-rw-r--r--de_DE.ISO8859-1/share/sgml/bookinfo.ent12
-rw-r--r--de_DE.ISO8859-1/share/sgml/catalog9
-rw-r--r--de_DE.ISO8859-1/share/sgml/freebsd.dsl30
-rw-r--r--de_DE.ISO8859-1/share/sgml/legalnotice.sgml44
-rw-r--r--en/handbook/contrib/chapter.sgml5796
-rw-r--r--en_US.ISO8859-1/Makefile9
-rw-r--r--en_US.ISO8859-1/articles/Makefile18
-rw-r--r--en_US.ISO8859-1/articles/Makefile.inc5
-rw-r--r--en_US.ISO8859-1/articles/committers-guide/Makefile25
-rw-r--r--en_US.ISO8859-1/articles/committers-guide/article.sgml2017
-rw-r--r--en_US.ISO8859-1/articles/contributing/article.sgml6224
-rw-r--r--en_US.ISO8859-1/articles/dialup-firewall/Makefile14
-rw-r--r--en_US.ISO8859-1/articles/dialup-firewall/article.sgml299
-rw-r--r--en_US.ISO8859-1/articles/diskless-x/Makefile14
-rw-r--r--en_US.ISO8859-1/articles/diskless-x/article.sgml349
-rw-r--r--en_US.ISO8859-1/articles/fonts/Makefile14
-rw-r--r--en_US.ISO8859-1/articles/fonts/article.sgml980
-rw-r--r--en_US.ISO8859-1/articles/formatting-media/Makefile14
-rw-r--r--en_US.ISO8859-1/articles/formatting-media/article.sgml603
-rw-r--r--en_US.ISO8859-1/articles/ipsec-must/Makefile16
-rw-r--r--en_US.ISO8859-1/articles/ipsec-must/article.sgml297
-rw-r--r--en_US.ISO8859-1/articles/mh/Makefile14
-rw-r--r--en_US.ISO8859-1/articles/mh/article.sgml782
-rw-r--r--en_US.ISO8859-1/articles/multi-os/Makefile14
-rw-r--r--en_US.ISO8859-1/articles/multi-os/article.sgml743
-rw-r--r--en_US.ISO8859-1/articles/new-users/Makefile14
-rw-r--r--en_US.ISO8859-1/articles/new-users/article.sgml1053
-rw-r--r--en_US.ISO8859-1/articles/programming-tools/Makefile14
-rw-r--r--en_US.ISO8859-1/articles/programming-tools/article.sgml2264
-rw-r--r--en_US.ISO8859-1/articles/vm-design/Makefile16
-rw-r--r--en_US.ISO8859-1/articles/vm-design/article.sgml838
-rw-r--r--en_US.ISO8859-1/articles/vm-design/fig1.eps104
-rw-r--r--en_US.ISO8859-1/articles/vm-design/fig2.eps115
-rw-r--r--en_US.ISO8859-1/articles/vm-design/fig3.eps133
-rw-r--r--en_US.ISO8859-1/articles/vm-design/fig4.eps133
-rw-r--r--en_US.ISO8859-1/articles/zip-drive/Makefile14
-rw-r--r--en_US.ISO8859-1/articles/zip-drive/article.sgml267
-rw-r--r--en_US.ISO8859-1/books/Makefile12
-rw-r--r--en_US.ISO8859-1/books/Makefile.inc5
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/Makefile27
-rw-r--r--en_US.ISO8859-1/books/arch-handbook/book.sgml3751
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/Makefile27
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/book.sgml3751
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/kerneldebug/chapter.sgml647
-rw-r--r--en_US.ISO8859-1/books/developers-handbook/policies/chapter.sgml398
-rw-r--r--en_US.ISO8859-1/books/faq/Makefile26
-rw-r--r--en_US.ISO8859-1/books/faq/book.sgml11371
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/Makefile50
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/book.sgml295
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/chapter.decl1
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/chapters.ent25
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/doc-build/chapter.sgml501
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/examples/appendix.sgml355
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/overview/chapter.sgml179
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/psgml-mode/chapter.sgml150
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/see-also/chapter.sgml121
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml2555
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml1583
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/structure/chapter.sgml287
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/stylesheets/chapter.sgml81
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/the-website/chapter.sgml217
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/tools/chapter.sgml284
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/translations/chapter.sgml474
-rw-r--r--en_US.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml316
-rw-r--r--en_US.ISO8859-1/books/handbook/Makefile62
-rw-r--r--en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml2746
-rw-r--r--en_US.ISO8859-1/books/handbook/appendix.decl1
-rw-r--r--en_US.ISO8859-1/books/handbook/authors.ent550
-rw-r--r--en_US.ISO8859-1/books/handbook/backups/chapter.sgml732
-rw-r--r--en_US.ISO8859-1/books/handbook/basics/chapter.sgml543
-rw-r--r--en_US.ISO8859-1/books/handbook/bibliography/chapter.sgml484
-rw-r--r--en_US.ISO8859-1/books/handbook/book.sgml142
-rw-r--r--en_US.ISO8859-1/books/handbook/boot/chapter.sgml549
-rw-r--r--en_US.ISO8859-1/books/handbook/chapter.decl1
-rw-r--r--en_US.ISO8859-1/books/handbook/chapters.ent50
-rw-r--r--en_US.ISO8859-1/books/handbook/contrib/chapter.sgml6224
-rw-r--r--en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml1566
-rw-r--r--en_US.ISO8859-1/books/handbook/disks/chapter.sgml883
-rw-r--r--en_US.ISO8859-1/books/handbook/eresources/chapter.sgml1584
-rw-r--r--en_US.ISO8859-1/books/handbook/hw/chapter.sgml5872
-rw-r--r--en_US.ISO8859-1/books/handbook/install/chapter.sgml1831
-rw-r--r--en_US.ISO8859-1/books/handbook/introduction/chapter.sgml709
-rw-r--r--en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml1177
-rw-r--r--en_US.ISO8859-1/books/handbook/kerneldebug/chapter.sgml647
-rw-r--r--en_US.ISO8859-1/books/handbook/kernelopts/chapter.sgml165
-rw-r--r--en_US.ISO8859-1/books/handbook/l10n/chapter.sgml928
-rw-r--r--en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml786
-rw-r--r--en_US.ISO8859-1/books/handbook/mail/chapter.sgml495
-rw-r--r--en_US.ISO8859-1/books/handbook/mailing-lists.ent107
-rw-r--r--en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml3728
-rw-r--r--en_US.ISO8859-1/books/handbook/newsgroups.ent10
-rw-r--r--en_US.ISO8859-1/books/handbook/pgpkeys/chapter.sgml1644
-rw-r--r--en_US.ISO8859-1/books/handbook/policies/chapter.sgml398
-rw-r--r--en_US.ISO8859-1/books/handbook/ports/chapter.sgml1007
-rw-r--r--en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml2632
-rw-r--r--en_US.ISO8859-1/books/handbook/printing/chapter.sgml4610
-rw-r--r--en_US.ISO8859-1/books/handbook/security/chapter.sgml2690
-rw-r--r--en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml2742
-rw-r--r--en_US.ISO8859-1/books/handbook/staff/chapter.sgml1251
-rw-r--r--en_US.ISO8859-1/books/handbook/users/chapter.sgml425
-rw-r--r--en_US.ISO8859-1/books/handbook/x11/chapter.sgml1400
-rw-r--r--en_US.ISO8859-1/books/porters-handbook/Makefile29
-rw-r--r--en_US.ISO8859-1/books/porters-handbook/book.sgml4399
-rw-r--r--en_US.ISO8859-1/books/porters-handbook/freebsd.dsl41
-rw-r--r--en_US.ISO8859-1/books/ppp-primer/Makefile26
-rw-r--r--en_US.ISO8859-1/books/ppp-primer/book.sgml2359
-rw-r--r--en_US.ISO8859-1/share/images/callouts/1.pngbin294 -> 0 bytes
-rw-r--r--en_US.ISO8859-1/share/images/callouts/10.pngbin326 -> 0 bytes
-rw-r--r--en_US.ISO8859-1/share/images/callouts/2.pngbin318 -> 0 bytes
-rw-r--r--en_US.ISO8859-1/share/images/callouts/3.pngbin315 -> 0 bytes
-rw-r--r--en_US.ISO8859-1/share/images/callouts/4.pngbin310 -> 0 bytes
-rw-r--r--en_US.ISO8859-1/share/images/callouts/5.pngbin313 -> 0 bytes
-rw-r--r--en_US.ISO8859-1/share/images/callouts/6.pngbin320 -> 0 bytes
-rw-r--r--en_US.ISO8859-1/share/images/callouts/7.pngbin309 -> 0 bytes
-rw-r--r--en_US.ISO8859-1/share/images/callouts/8.pngbin322 -> 0 bytes
-rw-r--r--en_US.ISO8859-1/share/images/callouts/9.pngbin322 -> 0 bytes
-rw-r--r--en_US.ISO8859-1/share/sgml/authors.ent550
-rw-r--r--en_US.ISO8859-1/share/sgml/bookinfo.ent12
-rw-r--r--en_US.ISO8859-1/share/sgml/catalog9
-rw-r--r--en_US.ISO8859-1/share/sgml/freebsd.dsl39
-rw-r--r--en_US.ISO8859-1/share/sgml/legalnotice.sgml44
-rw-r--r--en_US.ISO_8859-1/books/handbook/book.sgml4
-rw-r--r--es_ES.ISO8859-1/FAQ/FAQ.sgml64
-rw-r--r--es_ES.ISO8859-1/FAQ/Makefile16
-rw-r--r--es_ES.ISO8859-1/FAQ/acknowledgments.sgml61
-rw-r--r--es_ES.ISO8859-1/FAQ/admin.sgml1163
-rw-r--r--es_ES.ISO8859-1/FAQ/applications.sgml170
-rw-r--r--es_ES.ISO8859-1/FAQ/commercial.sgml186
-rw-r--r--es_ES.ISO8859-1/FAQ/hackers.sgml556
-rw-r--r--es_ES.ISO8859-1/FAQ/hardware.sgml560
-rw-r--r--es_ES.ISO8859-1/FAQ/includes.sgml7
-rw-r--r--es_ES.ISO8859-1/FAQ/install.sgml698
-rw-r--r--es_ES.ISO8859-1/FAQ/kernelconfig.sgml156
-rw-r--r--es_ES.ISO8859-1/FAQ/misc.sgml200
-rw-r--r--es_ES.ISO8859-1/FAQ/network.sgml1167
-rw-r--r--es_ES.ISO8859-1/FAQ/preface.sgml635
-rw-r--r--es_ES.ISO8859-1/FAQ/serial.sgml538
-rw-r--r--es_ES.ISO8859-1/FAQ/troubleshoot.sgml418
-rw-r--r--es_ES.ISO8859-1/FAQ/x.sgml442
-rw-r--r--es_ES.ISO8859-1/Makefile8
-rw-r--r--es_ES.ISO8859-1/books/Makefile8
-rw-r--r--es_ES.ISO8859-1/books/Makefile.inc5
-rw-r--r--es_ES.ISO8859-1/books/faq/Makefile25
-rw-r--r--es_ES.ISO8859-1/books/faq/book.sgml9343
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/Makefile59
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/advanced-networking/chapter.sgml24
-rw-r--r--es_ES.ISO8859-1/books/handbook/appendix.decl1
-rw-r--r--es_ES.ISO8859-1/books/handbook/authors.ent477
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/backups/chapter.sgml675
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/basics/chapter.sgml156
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/bibliography/chapter.sgml488
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/book.sgml144
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/chapter.decl5
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/chapters.ent52
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/contrib/chapter.sgml29
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/cutting-edge/chapter.sgml39
-rw-r--r--es_ES.ISO8859-1/books/handbook/disks/chapter.sgml186
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/eresources/chapter.sgml34
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/hw/chapter.sgml24
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/install/chapter.sgml1297
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/internals/chapter.sgml24
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/introduction/chapter.sgml639
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/kernelconfig/chapter.sgml30
-rw-r--r--es_ES.ISO8859-1/books/handbook/kerneldebug/chapter.sgml618
-rw-r--r--es_ES.ISO8859-1/books/handbook/kernelopts/chapter.sgml165
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/l10n/chapter.sgml24
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/linuxemu/chapter.sgml24
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/mail/chapter.sgml24
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/mailing-lists.ent48
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/mirrors/chapter.sgml29
-rw-r--r--es_ES.ISO8859-1/books/handbook/newsgroups.ent10
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/pgpkeys/chapter.sgml517
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/policies/chapter.sgml392
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/ports/chapter.sgml2091
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml29
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/printing/chapter.sgml24
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/quotas/chapter.sgml243
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/security/chapter.sgml24
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/serialcomms/chapter.sgml24
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/staff/chapter.sgml802
-rwxr-xr-xes_ES.ISO8859-1/books/handbook/x11/chapter.sgml24
-rw-r--r--es_ES.ISO8859-1/share/sgml/catalog9
-rw-r--r--es_ES.ISO8859-1/share/sgml/freebsd.dsl30
-rw-r--r--fr_FR.ISO8859-1/Makefile9
-rw-r--r--fr_FR.ISO8859-1/articles/Makefile26
-rw-r--r--fr_FR.ISO8859-1/articles/Makefile.inc9
-rw-r--r--fr_FR.ISO8859-1/articles/committers-guide/Makefile20
-rw-r--r--fr_FR.ISO8859-1/articles/committers-guide/article.sgml1233
-rw-r--r--fr_FR.ISO8859-1/articles/ddwg/Makefile20
-rw-r--r--fr_FR.ISO8859-1/articles/ddwg/article.sgml1861
-rw-r--r--fr_FR.ISO8859-1/articles/diskless-x/Makefile20
-rw-r--r--fr_FR.ISO8859-1/articles/diskless-x/article.sgml298
-rw-r--r--fr_FR.ISO8859-1/articles/fonts/Makefile20
-rwxr-xr-xfr_FR.ISO8859-1/articles/fonts/article.sgml775
-rw-r--r--fr_FR.ISO8859-1/articles/formatting-media/Makefile20
-rwxr-xr-xfr_FR.ISO8859-1/articles/formatting-media/article.sgml557
-rw-r--r--fr_FR.ISO8859-1/articles/ip-aliasing/Makefile20
-rwxr-xr-xfr_FR.ISO8859-1/articles/ip-aliasing/article.sgml277
-rw-r--r--fr_FR.ISO8859-1/articles/make-world/Makefile20
-rwxr-xr-xfr_FR.ISO8859-1/articles/make-world/article.sgml1376
-rw-r--r--fr_FR.ISO8859-1/articles/mh/Makefile20
-rw-r--r--fr_FR.ISO8859-1/articles/mh/article.sgml744
-rw-r--r--fr_FR.ISO8859-1/articles/multi-os/Makefile20
-rwxr-xr-xfr_FR.ISO8859-1/articles/multi-os/article.sgml700
-rw-r--r--fr_FR.ISO8859-1/articles/new-users/Makefile20
-rwxr-xr-xfr_FR.ISO8859-1/articles/new-users/article.sgml827
-rw-r--r--fr_FR.ISO8859-1/articles/ntfs/Makefile20
-rw-r--r--fr_FR.ISO8859-1/articles/ntfs/article.sgml490
-rw-r--r--fr_FR.ISO8859-1/articles/ppp/Makefile20
-rwxr-xr-xfr_FR.ISO8859-1/articles/ppp/article.sgml1894
-rw-r--r--fr_FR.ISO8859-1/articles/programming-tools/Makefile20
-rwxr-xr-xfr_FR.ISO8859-1/articles/programming-tools/article.sgml2001
-rw-r--r--fr_FR.ISO8859-1/articles/zip-drive/Makefile14
-rw-r--r--fr_FR.ISO8859-1/articles/zip-drive/article.sgml304
-rw-r--r--fr_FR.ISO8859-1/books/Makefile16
-rw-r--r--fr_FR.ISO8859-1/books/Makefile.inc9
-rw-r--r--fr_FR.ISO8859-1/books/faq/Makefile45
-rw-r--r--fr_FR.ISO8859-1/books/faq/acknowledgments.sgml92
-rw-r--r--fr_FR.ISO8859-1/books/faq/admin.sgml893
-rw-r--r--fr_FR.ISO8859-1/books/faq/applications.sgml149
-rw-r--r--fr_FR.ISO8859-1/books/faq/book.sgml97
-rw-r--r--fr_FR.ISO8859-1/books/faq/commercial.sgml254
-rw-r--r--fr_FR.ISO8859-1/books/faq/hackers.sgml299
-rw-r--r--fr_FR.ISO8859-1/books/faq/hardware.sgml478
-rw-r--r--fr_FR.ISO8859-1/books/faq/includes.sgml10
-rw-r--r--fr_FR.ISO8859-1/books/faq/install.sgml860
-rw-r--r--fr_FR.ISO8859-1/books/faq/kernelconfig.sgml147
-rw-r--r--fr_FR.ISO8859-1/books/faq/misc.sgml353
-rw-r--r--fr_FR.ISO8859-1/books/faq/network.sgml1588
-rw-r--r--fr_FR.ISO8859-1/books/faq/preface.sgml785
-rw-r--r--fr_FR.ISO8859-1/books/faq/serial.sgml626
-rw-r--r--fr_FR.ISO8859-1/books/faq/troubleshoot.sgml640
-rw-r--r--fr_FR.ISO8859-1/books/faq/x.sgml475
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/Makefile47
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/book.sgml303
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/chapters.ent23
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/overview/chapter.sgml187
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/psgml-mode/chapter.sgml154
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/see-also/chapter.sgml124
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml2356
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml1645
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/stylesheets/chapter.sgml72
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/the-faq/chapter.sgml49
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/the-handbook/chapter.sgml282
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/the-website/chapter.sgml49
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/tools/chapter.sgml301
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/translations/chapter.sgml497
-rw-r--r--fr_FR.ISO8859-1/books/fdp-primer/writing-style/chapter.sgml149
-rw-r--r--fr_FR.ISO8859-1/books/handbook/Makefile67
-rw-r--r--fr_FR.ISO8859-1/books/handbook/advanced-networking/chapter.sgml1124
-rw-r--r--fr_FR.ISO8859-1/books/handbook/backups/chapter.sgml774
-rw-r--r--fr_FR.ISO8859-1/books/handbook/basics/chapter.sgml163
-rw-r--r--fr_FR.ISO8859-1/books/handbook/bibliography/chapter.sgml498
-rw-r--r--fr_FR.ISO8859-1/books/handbook/book.sgml142
-rw-r--r--fr_FR.ISO8859-1/books/handbook/chapter.decl1
-rw-r--r--fr_FR.ISO8859-1/books/handbook/chapters.ent53
-rw-r--r--fr_FR.ISO8859-1/books/handbook/contrib/chapter.sgml5888
-rw-r--r--fr_FR.ISO8859-1/books/handbook/cutting-edge/chapter.sgml2628
-rwxr-xr-xfr_FR.ISO8859-1/books/handbook/disks/chapter.sgml191
-rw-r--r--fr_FR.ISO8859-1/books/handbook/eresources/chapter.sgml1357
-rw-r--r--fr_FR.ISO8859-1/books/handbook/hw/chapter.sgml5780
-rw-r--r--fr_FR.ISO8859-1/books/handbook/in-progress.sgml9
-rw-r--r--fr_FR.ISO8859-1/books/handbook/install/chapter.sgml1298
-rw-r--r--fr_FR.ISO8859-1/books/handbook/internals/chapter.sgml2141
-rw-r--r--fr_FR.ISO8859-1/books/handbook/introduction/chapter.sgml727
-rwxr-xr-xfr_FR.ISO8859-1/books/handbook/kernelconfig/chapter.sgml1876
-rw-r--r--fr_FR.ISO8859-1/books/handbook/kerneldebug/chapter.sgml682
-rw-r--r--fr_FR.ISO8859-1/books/handbook/kernelopts/chapter.sgml200
-rw-r--r--fr_FR.ISO8859-1/books/handbook/l10n/chapter.sgml376
-rw-r--r--fr_FR.ISO8859-1/books/handbook/linuxemu/chapter.sgml973
-rw-r--r--fr_FR.ISO8859-1/books/handbook/mail/chapter.sgml653
-rw-r--r--fr_FR.ISO8859-1/books/handbook/mailing-lists.ent113
-rw-r--r--fr_FR.ISO8859-1/books/handbook/mirrors/chapter.sgml1420
-rw-r--r--fr_FR.ISO8859-1/books/handbook/pgpkeys/chapter.sgml627
-rw-r--r--fr_FR.ISO8859-1/books/handbook/policies/chapter.sgml404
-rw-r--r--fr_FR.ISO8859-1/books/handbook/ports/chapter.sgml5197
-rw-r--r--fr_FR.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml2783
-rwxr-xr-xfr_FR.ISO8859-1/books/handbook/printing/chapter.sgml5375
-rwxr-xr-xfr_FR.ISO8859-1/books/handbook/quotas/chapter.sgml284
-rwxr-xr-xfr_FR.ISO8859-1/books/handbook/security/chapter.sgml1894
-rw-r--r--fr_FR.ISO8859-1/books/handbook/serialcomms/chapter.sgml2351
-rw-r--r--fr_FR.ISO8859-1/books/handbook/staff/chapter.sgml859
-rw-r--r--fr_FR.ISO8859-1/books/handbook/todo.sgml9
-rw-r--r--fr_FR.ISO8859-1/books/handbook/x11/chapter.sgml29
-rw-r--r--fr_FR.ISO8859-1/share/sgml/abstract.ent15
-rw-r--r--fr_FR.ISO8859-1/share/sgml/artheader.ent14
-rw-r--r--fr_FR.ISO8859-1/share/sgml/bookinfo.ent16
-rw-r--r--fr_FR.ISO8859-1/share/sgml/catalog9
-rw-r--r--fr_FR.ISO8859-1/share/sgml/copyright.sgml13
-rw-r--r--fr_FR.ISO8859-1/share/sgml/disclaimer.sgml19
-rw-r--r--fr_FR.ISO8859-1/share/sgml/freebsd.dsl37
-rw-r--r--fr_FR.ISO8859-1/share/sgml/legalnotice.sgml14
-rw-r--r--fr_FR.ISO8859-1/share/sgml/license.sgml27
-rw-r--r--fr_FR.ISO8859-1/share/sgml/translators.ent63
-rw-r--r--fr_FR.ISO8859-1/share/sgml/urls.ent22
-rw-r--r--ja_JP.eucJP/articles/contributing/article.sgml6372
-rw-r--r--ja_JP.eucJP/man/man1/gtar.1498
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/aic.451
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/apm.4160
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/ar.4108
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/cs.4105
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/cx.4289
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/el.458
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/ep.4121
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/ex.484
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/fe.4284
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/ie.496
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/io.472
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/lnc.4124
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/mcd.4151
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/npx.479
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/pcf.465
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/perfmon.4225
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/pnp.4221
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/scd.465
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/spkr.4234
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/sr.4119
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/vx.4102
-rw-r--r--ja_JP.eucJP/man/man4/man4.i386/wd.4106
-rw-r--r--ja_JP.eucJP/man/man8/man8.i386/apm.8157
-rw-r--r--ja_JP.eucJP/man/man8/man8.i386/apmd.8295
-rw-r--r--ja_JP.eucJP/share/sgml/authors.ent555
-rw-r--r--ja_JP.eucJP/share/sgml/jauthors.ent91
-rw-r--r--nl_NL.ISO8859-1/Makefile6
-rw-r--r--nl_NL.ISO8859-1/share/sgml/bookinfo.ent13
-rw-r--r--nl_NL.ISO8859-1/share/sgml/catalog9
-rw-r--r--zh/FAQ/FAQ.sgml70
341 files changed, 2 insertions, 226817 deletions
diff --git a/de_DE.ISO8859-1/Makefile b/de_DE.ISO8859-1/Makefile
deleted file mode 100644
index 63a1e66199..0000000000
--- a/de_DE.ISO8859-1/Makefile
+++ /dev/null
@@ -1,8 +0,0 @@
-# $FreeBSD$
-
-COMPAT_SYMLINK = de
-
-SUBDIR= books
-
-DOC_PREFIX?= ${.CURDIR}/..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/de_DE.ISO8859-1/books/Makefile b/de_DE.ISO8859-1/books/Makefile
deleted file mode 100644
index d24196de13..0000000000
--- a/de_DE.ISO8859-1/books/Makefile
+++ /dev/null
@@ -1,13 +0,0 @@
-#
-# The FreeBSD Documentation Project
-# The FreeBSD German Documentation Project
-#
-# $FreeBSD$
-#
-
-SUBDIR= handbook
-
-ROOT_SYMLINKS= handbook
-
-DOC_PREFIX?= ${.CURDIR}/../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/de_DE.ISO8859-1/books/Makefile.inc b/de_DE.ISO8859-1/books/Makefile.inc
deleted file mode 100644
index b30d4be8da..0000000000
--- a/de_DE.ISO8859-1/books/Makefile.inc
+++ /dev/null
@@ -1,8 +0,0 @@
-#
-# The FreeBSD Documentation Project
-# The FreeBSD German Documentation Project
-#
-# $FreeBSD$
-#
-
-DESTDIR?= ${DOCDIR}/de_DE.ISO_8859-1/books/${.CURDIR:T}
diff --git a/de_DE.ISO8859-1/books/handbook/Makefile b/de_DE.ISO8859-1/books/handbook/Makefile
deleted file mode 100644
index dac832cfe8..0000000000
--- a/de_DE.ISO8859-1/books/handbook/Makefile
+++ /dev/null
@@ -1,37 +0,0 @@
-#
-# $FreeBSD: doc/de_DE.ISO_8859-1/books/handbook/Makefile,v 1.4 2000/07/30 10:05:59 alex Exp $
-#
-# Build the FreeBSD Handbook in its German translation.
-#
-
-MAINTAINER=alex@FreeBSD.org
-
-DOC?= book
-
-FORMATS?= html-split
-
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-#
-# SRCS lists the individual SGML files that make up the document. Changes
-# to any of these files will force a rebuild
-#
-
-# SGML content
-SRCS= book.sgml
-SRCS+= backups/chapter.sgml
-SRCS+= basics/chapter.sgml
-SRCS+= bibliography/chapter.sgml
-SRCS+= ports/chapter.sgml
-
-# Entities
-SRCS+= ../../../en_US.ISO_8859-1/books/handbook/authors.ent
-SRCS+= chapters.ent
-SRCS+= newsgroups.ent
-
-# German
-SRCS+= de-authors.ent
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/de_DE.ISO8859-1/books/handbook/appendix.decl b/de_DE.ISO8859-1/books/handbook/appendix.decl
deleted file mode 100644
index 5b0425623d..0000000000
--- a/de_DE.ISO8859-1/books/handbook/appendix.decl
+++ /dev/null
@@ -1 +0,0 @@
-<!DOCTYPE appendix PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
diff --git a/de_DE.ISO8859-1/books/handbook/backups/chapter.sgml b/de_DE.ISO8859-1/books/handbook/backups/chapter.sgml
deleted file mode 100644
index 0a8b63a48e..0000000000
--- a/de_DE.ISO8859-1/books/handbook/backups/chapter.sgml
+++ /dev/null
@@ -1,848 +0,0 @@
-<!--
- The FreeBSD Documentation Project
- The FreeBSD German Documentation Project
-
- Original version 1.25
- $FreeBSD: doc/de_DE.ISO_8859-1/books/handbook/backups/chapter.sgml,v 1.1 2000/06/13 09:42:15 alex Exp $
--->
-
-<chapter id="backups">
- <title>Datensicherung</title>
-
- <para><emphasis>&Uuml;bersetzt von &a.de.bwarken,
- Januar 1999</emphasis></para>
-
- <para>Das folgende Kapitel besch&auml;ftigt sich mit der Datensicherung und
- den dazu verwendeten Programmen. Wenn Sie etwas zu diesem Kapitel
- beisteuern m&ouml;chten, senden Sie es bitte an die (englischsprachige)
- &a.doc;</para>
-
- <sect1 id="backups-tapebackups">
- <title>Bandmedien</title>
-
- <para>Die wichtigsten Bandmedien sind 4mm, 8mm, QIC,
- Mini-Cartridge und DLT.</para>
-
- <sect2 id="backups-tapebackups-4mm">
- <title>4mm (DDS: Digital Data Storage)</title>
-
- <para>Die 4mm-B&auml;nder ersetzen mehr und mehr das QIC-Format als
- Backupmedium der Wahl f&uuml;r Workstations. Dieser Trend nahm stark
- zu, als Conner die Firma Archive, einen f&uuml;hrenden Hersteller von
- QIC-Laufwerken, aufkaufte und die Produktion von QIC-Laufwerken
- stoppte. 4mm-Laufwerke sind klein und ruhig, haben aber nicht den
- gleichen Ruf der Zuverl&auml;ssigkeit, den die 8mm-Laufwerke
- genie&szlig;en. Die 4mm-Kassetten sind preiswerter und mit den
- Ma&szlig;en 76,2 x 50,8 x 12,7 mm (3 x 2 x 0,5 Inch) kleiner als die
- 8mm-Kassetten. Sowohl die 4mm- als auch die 8mm-Magnetk&ouml;pfe
- haben eine relativ kurze Lebensdauer, weil beide die gleiche
- Helical-Scan-Technologie benutzen.</para>
-
- <para>Der Datendurchsatz dieser Laufwerke beginnt bei etwa 150
- kByte/s, Spitzenwerte liegen bei etwa 500 kByte/s. Die
- Datenkapazit&auml;t liegt zwischen 1,3 GB und 2 GB. Die meisten
- Ger&auml;te haben eine Hardwarekompression eingebaut, die die
- Kapazit&auml;t ungef&auml;hr verdoppelt. Es gibt
- Multi-Drive-Einheiten f&uuml;r Bandbibliotheken mit bis zu 6
- Laufwerken in einem Geh&auml;use und automatischem Bandwechsel. Die
- Kapazit&auml;t einer solchen Bibliothek liegt bei 240 GB.</para>
-
- <para>Der Standard DDS-3 unterst&uuml;tzt nun Bandkapazit&auml;ten bis
- zu 12 GB (oder komprimiert 24 GB).</para>
-
- <para>4mm-Laufwerke, ebenso wie 8mm-Laufwerke, verwenden Helical-Scan.
- Alle Vor- und Nachteile von Helical-Scan gelten sowohl f&uuml;r 4mm-
- als auch f&uuml;r 8mm-Laufwerke.</para>
-
- <para>B&auml;nder sollten nach 2.000 Banddurchl&auml;ufen oder 100
- vollen Backups ersetzt werden.</para>
- </sect2>
-
- <sect2 id="backups-tapebackups-8mm">
- <title>8mm (Exabyte)</title>
-
- <para>8mm-B&auml;nder sind die verbreitetsten SCSI-Bandlaufwerke; sie
- sind das geeignetste Bandformat zum Austausch von B&auml;ndern. Fast
- an jedem Standort gibt es ein 8mm-Bandlaufwerk mit 2 GB.
- 8mm-B&auml;nder sind zuverl&auml;ssig, gut zu handhaben und arbeiten
- leise. Bandkassetten sind preiswert und klein mit 122 x 84 x 15 mm
- (4,8 x 3,3 x 0,6 Inch). ein Nachteil der 8mm-Technologie ist die
- relativ kurze Lebensdauer des Schreib-/Lesekopfs und der B&auml;nder
- auf Grund der hohen Relativgeschwindigkeit des Bandes &uuml;ber die
- K&ouml;pfe hinweg.</para>
-
- <para>Der Datendurchsatz liegt ungef&auml;hr zwischen 250 kByte/s und
- 500 kByte/s. Die Datenkapazit&auml;t beginnt bei 300 MB und erreicht
- bis zu 7 GB bei den Spitzenger&auml;ten. Die meisten Ger&auml;te
- haben eine Hardwarekompression eingebaut, die die Kapazit&auml;t
- ungef&auml;hr verdoppelt. Diese Laufwerke sind erh&auml;ltlich in
- Form von Einzelger&auml;ten oder als Multi-Drive-Bandbibliotheken mit
- 6 Laufwerken und 120 B&auml;ndern in einem Geh&auml;use. Die
- B&auml;nder werden von der Ger&auml;teeinheit automatisch gewechselt.
- Die Kapazit&auml;t einer solchen Bibliothek liegt bei 840 GB und
- mehr.</para>
-
- <para>Das Exabyte-Modell <quote>Mammoth</quote> unterst&uuml;tzt 12 GB
- auf einem Band (24 MB mit Kompression) und kostet etwa doppelt so viel
- wie ein konventionelles Bandlaufwerk.</para>
-
- <para>Die Daten werden mittels Helical-Scan auf das Band
- aufgezeichnet, die K&ouml;pfe sind leicht schr&auml;g zum Medium
- angebracht (mit einem Winkel von etwa 6 Grad). Das Band wickelt sich
- 270 Grad um die Spule, die die K&ouml;pfe tr&auml;gt. Die Spule dreht
- sich, w&auml;hrend das Band dar&uuml;berl&auml;uft. Das Resultat ist
- eine hohe Datendichte und eng gepackte Spuren, die von einem Rand des
- Bands zum gegen&uuml;berliegenden quer &uuml;ber das Band abgewinkelt
- verlaufen.</para>
- </sect2>
-
- <sect2 id="backups-tapebackups-qic">
- <title>QIC</title>
-
- <para>QIC-150-B&auml;nder und -Laufwerke sind wohl der am weitesten
- verbreitete Bandtyp &uuml;berhaupt. QIC-Bandlaufwerke sind die
- preiswertesten "seri&ouml;sen" Backupger&auml;te, die angeboten
- werden. Der Nachteil dabei ist der hohe Preis der B&auml;nder.
- QIC-B&auml;nder sind im Vergleich zu 8mm- oder 4mm-B&auml;ndern bis zu
- 5 Mal teurer, wenn man den Preis auf 1 GB Datenkapazit&auml;t
- umrechnet. Aber wenn Ihr Bedarf mit einem halben Dutzend B&auml;nder
- abgedeckt werden kann, mag QIC die richtige Wahl sein.</para>
-
- <para>QIC ist der <emphasis>g&auml;ngigste</emphasis>
- Bandlaufwerkstyp. Jeder Standort hat ein QIC-Laufwerk der einen oder
- anderen Dichte. Aber gerade das ist der Haken an der Sache, QIC
- bietet eine gro&szlig;e Anzahl verschiedener Datendichten auf
- physikalisch &auml;hnlichen (manchmal identischen) B&auml;ndern.
- QIC-Laufwerke sind nicht leise. Diese Laufwerke suchen lautstark die
- richtige Bandstelle, bevor sie mit der Datenaufzeichnung beginnen.
- Sie sind w&auml;hrend des Lesens, Schreibens und Suchens deutlich
- h&ouml;rbar.</para>
-
- <para>Die Abmessungen der QIC-Kassetten betragen 152.4 x 101.6 x 17.78
- mm (6 x 4 x 0,7 Inch), die QIC-Bandbreite betr&auml;gt 6,35 mm (1/4
- Inch). <link
- linkend="backups-tapebackups-mini">Mini-Cartridges</link>, die die
- gleiche Bandbreite verwenden, werden gesondert vorgestellt.
- Bandbibliotheken und Bandwechselger&auml;te gibt es im QIC-Format
- keine.</para>
-
- <para>Der Datendurchsatz liegt ungef&auml;hr zwischen 150 kByte/s und
- 500 kByte/s. Die Datenkapzit&auml;t reicht von 40 MB bis zu 15 GB.
- Hardwarekompression ist in vielen der neueren QIC-Laufwerke eingebaut.
- QIC-Laufwerke werden heute seltener eingesetzt; sie werden von den
- DAT-Laufwerken abgel&ouml;st.</para>
-
- <para>Die Daten werden auf dem Band in Spuren aufgezeichnet. Die
- Spuren verlaufen entlang der L&auml;ngsachse des Bandmediums von einem
- Ende zum anderen. Die Anzahl der Spuren, und damit auch die Breite
- einer Spur, variiert mit der Kapazit&auml;t des Laufwerks. Die
- meisten, wenn nicht alle neueren Laufwerke sind
- r&uuml;ckw&auml;rtskompatibel, zumindest zum Lesen (aber oft auch zum
- Schreiben). QIC hat einen guten Ruf bez&uuml;glich der
- Datensicherheit (die Mechanik ist einfacher und robuster als diejenige
- der Helical-Scan-Laufwerken).</para>
-
- <para>B&auml;nder sollten nach 5,000 Backups ersetzt werden.</para>
- </sect2>
-
-<![ %not.published; [
-
- <sect2 id="backups-tapebackups-mini">
- <title>* Mini-Cartridge</title>
-
- <para></para>
- </sect2>
-
-]]>
-
- <sect2 id="backups-tapebackups-dlt">
- <title>DLT</title>
-
- <para>DLT hat die schnellste Datentransferrate von allen hier
- aufgelisteten Ger&auml;tetypen. Das 1/2-Inch-Band (12,7 mm) befindet
- sich in einer Spulkassette mit den Abmessungen 101,6 x 101,6 x 25,4 mm
- (4 x 4 x 1 Inch). Die eine Seite der Kassette hat eine bewegliche
- Abdeckung. Der Laufwerksmechanismus &ouml;ffnet diese Abdeckung und
- zieht die Bandf&uuml;hrung heraus. Die Bandf&uuml;hrung tr&auml;gt
- ein ovales Loch, die das Laufwerk zum "Einh&auml;ngen" des Bandes
- benutzt. Die Aufwickelspule befindet sich im Innern des
- Bandlaufwerks. Bei allen anderen hier besprochenen Bandkassetten
- (9-Spur-B&auml;nder sind die einzige Ausnahme) befinden sich sowohl
- die Auf- als auch die Abwickelspule im Inneren der
- Bandkassette.</para>
-
- <para>Der Datendurchsatz liegt bei etwa 1,5 MBytes/s, der dreifache
- Durchsatz der 4mm-, 8mm- oder QIC-Bandlaufwerke. Die
- Datenkapazit&auml;t reicht von 10 GB bis 20 GB f&uuml;r
- Einfachlaufwerke. Auch Mehrfachbandger&auml;te sind erh&auml;ltlich,
- sowohl als Bandwechsler wie auch als Multi-Drive-Bandbibliotheken, die
- Platz f&uuml;r 5 bis 900 B&auml;nder verteilt auf 1 bis 20 Laufwerke
- enthalten, mit einer Speicherkapazit&auml;t von 50 GB bis 9 TB.</para>
-
- <para>Mit Kompression unterst&uuml;tzt das Format DLT Type IV bis zu
- 70 GB Kapazit&auml;t.</para>
-
- <para>Die Daten werden auf dem Band in Spuren aufgezeichnet, die
- parallel zur Bewegungsrichtung verlaufen (gerade so wie bei den
- QIC-B&auml;ndern). Zwei Spuren werden dabei gleichzeitig beschrieben.
- Die Lebenszeit der Lese- und Schreibk&ouml;pfe sind relativ lang; denn
- sobald das Band anh&auml;lt, gibt es keine Relativbewegung mehr
- zwischen den K&ouml;pfen und dem Band.</para>
- </sect2>
-
- <sect2>
- <title id="backups-tapebackups-ait">AIT</title>
-
- <para>AIT ist ein neues Format von Sony, das (mit Kompression) bis zu
- 50 GB pro Band speichern kann. Die B&auml;nder haben einen
- Speicherchip, der einen Index mit dem Inhalt des Bandes anlegt.
- Dieser Index kann vom Bandlaufwerk zur schnellen Bestimmung der Lage
- von Dateien auf dem Band benutzt werden, w&auml;hrend andere
- B&auml;nder einige Minuten zur Lokalisierung ben&ouml;tigen.</para>
-
- <para>Entsprechende Software wie etwa SAMS:Alexandria
- k&ouml;nnen 40 oder mehr AIT-Bandbibliotheken verarbeiten, indem sie
- direkt mit dem Speicherchip des Bandes kommunizieren, wenn der
- Bandinhalt am Bildschirm dargestellt werden soll oder bestimmt werden
- soll, welche Dateien auf welchem Band gespeichert sind, oder um das
- richtige Band zu lockalisieren, zu laden und Daten vom Band
- zur&uuml;ckzuspielen. Bibliotheken dieser Art liegen in der
- Preiskategorie von $20,000, womit sie etwas aus dem Hobbymarkt
- herausfallen.</para>
- </sect2>
-
- <sect2>
- <title>Die erste Benutzung eines neuen Bands</title>
-
- <para>Der Versuch ein neues, vollkommen leeres Band ohne weiteres zu
- lesen oder zu beschreiben wird schiefgehen. Auf der Konsole werden
- dann Meldungen &auml;hnlich wie folgt ausgegeben:</para>
-
- <screen>sa0(ncr1:4:0): NOT READY asc:4,1
-0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
-
- <para>Das Band enth&auml;lt n&auml;mlich keinen Identifier-Block
- (Blocknummer 0). Alle QIC-Bandlaufwerke seit der Einf&uuml;hrung des
- QIC-525-Standards schreiben einen Identifier-Block auf das Band. Es
- gibt zwei L&ouml;sungen:</para>
-
- <para><command>mt fsf 1</command> veranlasst das Bandlaufwerk einen
- Identifier-Block auf das Band zu schreiben.</para>
-
- <para>Das Band durch Dr&uuml;cken des Bandauswurfknopfs an der
- Vorderseite des Bandger&auml;ts auswerfen.</para>
-
- <para>Danach das Band wieder einlegen und Daten auf das Band
- &uuml;bertragen wie in &man.dump.8; beschrieben.</para>
-
- <para>Das Kommando &man.dump.8; gibt die Meldung <literal>DUMP: End of
- tape detected</literal> zur&uuml;ck und die Konsole zeigt:
- <literal>HARDWARE FAILURE info:280 asc:80,96</literal></para>
-
- <para>Das Band zur&uuml;ckspulen mit dem Kommando: <command>mt
- rewind</command></para>
-
- <para>Nachfolgende Bandoperationen werden dann erfolgreich
- ausgef&uuml;hrt.</para>
- </sect2>
- </sect1>
-
- <sect1 id="backup-programs">
- <title>Backup-Programme</title>
-
- <para>Die drei wichtigsten Programme sind
- &man.dump.8;,
- &man.tar.1;,
- and
- &man.cpio.1;.</para>
-
- <sect2>
- <title>Aufspielen und Wiederherstellen</title>
-
- <para>&man.dump.8; und &man.restore.8; sind die traditionellen
- Backupprogramme in UNIX. Sie betrachten das Laufwerk als eine
- Ansammlung von Bl&ouml;cken, operieren also unterhalb dem
- Abstraktionslevel von Dateien, Links und Verzeichnissen, die die
- Grundlage des Dateisystemkonzepts bilden.</para>
-
- <para>&man.dump.8; f&uuml;hrt Datensicherungen von Ger&auml;ten aus,
- bearbeitet also nur komplette Dateisysteme, nicht jedoch Teile eines
- Dateisystems und auch keine Verzeichnisb&auml;ume, die mehr als ein
- Dateisystem &uuml;berspannen, was durch Verwendung von symbolischen
- Links mittels &man.ln.1; oder durch das Einh&auml;ngen von
- Dateisystemen vorkommen kann. &man.dump.8; schreibt also keine
- Dateien und Verzeichnisse auf das Band, sondern direkt die
- Datenbl&ouml;cke, die die Dateien und Verzeichnisse enthalten.</para>
-
- <para>&man.dump.8; hat einige Eigenarten, die noch aus den fr&uuml;hen
- Tagen der Version 6 von ATT UNIX (ca. 1975) stammen. Die Parameter
- sind f&uuml;r 9-Spur-B&auml;nder (6250 bpi) voreingestellt, nicht auf
- die heute &uuml;blichen Medien hoher Dichte (bis zu 62.182 ftpi). Bei
- der Verwendung der Kapazit&auml;ten moderner Bandlaufwerke muss diese
- Voreinstellung auf der Kommandozeile &uuml;berschrieben werden.</para>
-
- <para>&man.rdump.8; und &man.rrestore.8; k&ouml;nnen Daten &uuml;ber
- Netzwerk auf ein Band, das sich in einem Laufwerk eines anderen
- Computers befindet, &uuml;berspielen. Beide Programme benutzen die
- Befehle &man.rcmd.3; und &man.ruserok.3; zum Zugriff auf das entfernte
- Bandlaufwerk. Daher muss der Anwender, der das Backup
- durchf&uuml;hrt, auf dem entfernten Computer eine Zugangsberechtigung
- f&uuml;r <literal>rhosts</literal> haben.</para>
-
- <para>Die Argumente zu &man.rdump.8; und &man.rrestore.8; m&uuml;ssen
- zur Verwendung auf dem entfernten Computer geeignet sein.
- (Z.B. lautet das Kommando zum Aufrufen von <command>rdump</command>
- von einem FreeBSD-Computer aus auf ein Exabyte-Bandlaufwerk auf einer
- Sun namens <hostid>komodo</hostid>: <command>/sbin/rdump 0dsbfu 54000
- 13000 126 komodo:/dev/nrsa8 /dev/rda0a 2&gt;&amp;1</command>). Man
- beachte, dass bei der Ausf&uuml;hrung die Sicherheitsvorkehrungen wie
- beim Aufruf des Kommandos <literal>rhosts</literal> gelten.
- Erkundigen Sie sich nach Ihrer Zugangsberechtigung.</para>
- </sect2>
-
- <sect2>
- <title>Tar</title>
-
- <para>&man.tar.1; stammt ebenfalls aus Version 6 von ATT Unix
- (ca. 1975). &man.tar.1; arbeitet mit dem Dateisystem, denn es
- schreibt Dateien und Verzeichnisse auf das Band. &man.tar.1;
- unterst&uuml;tzt zwar nicht den vollen Umfang von Optionen, die bei
- &man.cpio.1; zur Verf&uuml;gung stehen, aber daf&uuml;r erfordert
- &man.tar.1; nicht die ungew&ouml;hnliche Kommando-Pipeline,1 die
- &man.cpio.1; verwendet.</para>
-
- <para>Die meisten Versionen von &man.tar.1; unterst&uuml;tzen keine
- Backups &uuml;ber das Netzwerk. Die GNU-Version von &man.tar.1;, die
- in FreeBSD verwendet wird, unterst&uuml;zt jedoch entfernte
- Ger&auml;te mit der gleichen Syntax wie &man.rdump.8;. Um &man.tar.1;
- f&uuml;r ein Exabyte-Bandlaufwerk auf einer Sun
- namens<hostid>komodo</hostid> auszuf&uuml;hren, muss folgendes
- Kommando aufgerufen werden: <command>/usr/bin/tar cf komodo:/dev/nrsa8
- . 2&gt;&amp;1</command>. Bei den Versionen ohne Unterst&uuml;tzung
- f&uuml;r entfernte Ger&auml;te kann man die Daten &uuml;ber eine
- Pipeline und &man.rsh.1; an ein entferntes Laufwerk senden.</para>
-
- <screen>&prompt.root; <userinput>tar cf - . | rsh <replaceable>hostname</replaceable> dd of=<replaceable>tape-device</replaceable> obs=20b</userinput></screen>
-
- <para>Wenn Sie Bedenken bez&uuml;glich der Sicherheit beim Backup
- &uuml;ber's Netz haben, sollten Sie &man.ssh.1; anstatt
- &man.rsh.1; benutzen.</para>
- </sect2>
-
- <sect2>
- <title>Cpio</title>
-
- <para>&man.cpio.1; ist das urspr&uuml;ngliche Unix-Programm zum
- Dateitransfer mit magnetischen Medien. &man.cpio.1; hat (neben vielen
- anderen Leistungsmerkmalen) Optionen zum Byte-Swapping, zum Schreiben
- einer Anzahl verschiedener Archivformate und zum Weiterleiten von
- Daten an andere Programme &uuml;ber Pipeline. Dieses letztes
- Leistungsmerkmal macht &man.cpio.1; zu einer ausgezeichneten Wahl
- f&uuml;r Installationsmedien. Leider kann &man.cpio.1; keine
- Dateib&auml;ume durchlaufen, so dass eine Liste der zu bearbeitenden
- Dateien &uuml;ber <filename>stdin</filename> angegeben werden
- muss.</para>
-
- <para>&man.cpio.1; unterst&uuml;tzt keine Backups &uuml;ber das
- Netzwerk. Man kann aber eine Pipeline und &man.rsh.1 verwenden, um
- Daten an ein entferntes Bandlaufwerk zu senden. (XXX ein
- Beispiel-Kommando beif&uuml;gen)</para>
- </sect2>
-
- <sect2>
- <title>Pax</title>
-
- <para>&man.pax.1; ist die Antort von IEEE/POSIX auf &man.tar.1; und
- &man.cpio.1;. &Uuml;ber die Jahre hinweg sind die verschiedenen
- Versionen von &man.tar.1; und &man.cpio.1; leicht inkompatibel
- geworden. Daher hat POSIX, statt eine Standardisierung zwischen
- diesen auszufechten, ein neues Archivprogramm geschaffen. &man.pax.1;
- versucht viele der unterschiedlichen cpio- und tar-Formate zu lesen
- und zu schreiben, au&szlig;erdem einige neue, eigene Formate. Die
- Kommandostruktur &auml;hnelt eher &man.cpio.1; als &man.tar.1;.</para>
- </sect2>
-
- <sect2 id="backups-programs-amanda">
- <title>Amanda</title>
-
- <para><ulink url="../ports/misc.html#amanda-2.4.0">Amanda</ulink>
- (Advanced Maryland Network Disk Archiver) ist ein
- Client/Server-Backupsystem, nicht nur ein einzelnes Programm. Ein
- Amanda-Server kann auf einem einzigen Bandlaufwerk Datensicherungen
- von jeder beliebigen Anzahl von Computern speichern, sofern auf diesen
- jeweils ein Amanda-Client l&auml;uft und sie &uuml;ber Netzwerk mit
- dem Amanda-Server verbunden sind.</para>
-
- <para>Ein h&auml;ufiges Problem bei Standorten mit einer Anzahl
- gro&szlig;er Festplatten ist, dass das Kopieren der Daten auf Band
- langsamer vor sich geht als solche Daten anfallen. Amanda l&ouml;st
- dieses Problem durch Verwendung einer "Holding Disk", einer Festplatte
- zum gleichzeitigen Zwischenspeichern mehrerer Dateisysteme.</para>
-
- <para>F&uuml;r Datensicherungen &uuml;ber einen l&auml;ngeren Zeitraum
- erzeugt Amanda "Archivsets" von allen Dateisystemen, die in Amanda's
- Konfigurationsdatei genannt werden. Ein Archivset ist eine Gruppe von
- B&auml;ndern mit vollen Backups und Reihen von inkrementellen (oder
- differentiellen) Backups, die jeweils nur die Unterschiede zum vorigen
- Backup enthalten. Zur Wiederherstellung von besch&auml;digten
- Dateissystemen ben&ouml;tigt man das letzte volle Backup und alle
- darauf folgenden inkrementellen Backups.</para>
-
- <para>Ein g&auml;ngiger Datensicherungsplan ist, an den Wochenenden
- ein volles Backup und w&auml;hrend der Woche jede Nacht ein
- inkrementelles Backup zu erstellen.</para>
-
- <para>Die Konfigurationsdatei erm&ouml;glicht die Feineinstellung der
- Backups und des Netzwerkverkehrs von Amanda. Amanda kann zum
- Schreiben der Daten auf das Band jedes der oben beschriebenen
- Backuprogramme verwenden. Amanda ist erh&auml;ltlich als Portierung
- oder als Softwarepaket, es ist nicht von vorne herein auf dem System
- installiert.</para>
- </sect2>
-
- <sect2>
- <title>Tue nichts</title>
-
- <para><quote>Tue nichts</quote> ist kein Computerprogramm, sondern die
- am h&auml;ufigsten angewendete Backupstrategie. Diese kostet nichts,
- man muss keinen Backupplan befolgen, einfach nur nein sagen. Wenn
- etwas passiert, einfach grinsen und ertragen!</para>
-
- <para>Wenn Ihre Zeit und Ihre Daten nicht so wichtig sind, dann ist
- die Strategie <quote>Tue nichts</quote> das geeignetste Backupprogramm
- f&uuml;r Ihren Computer. Aber UNIX ein n&uuml;tzliches Werkzeug. Sie
- m&uuml;ssen damit rechnen, dass Sie innerhalb von sechs Monaten eine
- Sammlung von Dateien haben, die f&uuml;r Sie wertvoll geworden
- sind.</para>
-
- <para><quote>Tue nichts</quote> ist die richtige Backupmethode f&uuml;r
- <filename>/usr/obj</filename> und andere Verzeichnisb&auml;ume, die
- vom Computer exakt wiedererzeugt werden k&ouml;nnen. Ein Beispiel
- sind die Dateien, die diese Handbuchseiten darstellen &mdash; sie
- wurden aus Quelldateien im Format <acronym>SGML</acronym> erzeugt. Es
- ist nicht n&ouml;tig, Sicherheitskopien der Dateien in den
- sekund&auml;ren Formaten wie etwa <acronym>HTML</acronym> zu
- erstellen. Die Quelldateien in <acronym>SGML</acronym> sollten jedoch
- in die regelm&auml;&szlig;igen Backups mit einbezogen werden.</para>
- </sect2>
-
- <sect2>
- <title>Welches Backup-Programm ist am Besten?</title>
-
- <para>&man.dump.8;, <emphasis>Punkt und Schluss.</emphasis> Elizabeth
- D. Zwicky hat alle hier genannten Backup-Programme bis zur
- Ersch&ouml;pfung ausgetestet. Ihre eindeutige Wahl zur Sicherung
- aller Daten mit Ber&uuml;cksichtigung aller Besonderheiten von
- UNIX-Dateisystemen ist &man.dump.8;.</para>
-
- <para>Elizabeth erzeugte Dateisysteme mit einer gro&szlig;en Vielfalt
- ungew&ouml;hnlicher Bedingungen (und einiger gar nicht so
- ungew&ouml;hnlicher) und testete jedes Programm durch ein Backup und
- eine Wiederherstellung dieser Dateisysteme. Unter den Besonderheiten
- waren Dateien mit L&ouml;chern, Dateien mit L&ouml;chern und einem
- Block mit Null-Zeichen, Dateien mit ausgefallenen Buchstaben im
- Dateinamen, unlesbare und nichtschreibbare Dateien,
- Ger&auml;tedateien, Dateien, deren L&auml;nge sich w&auml;hrend des
- Backups &auml;ndert, Dateien, die w&auml;hrend des Backups erzeugt und
- gel&ouml;scht werden, u.v.m. Sie berichtete &uuml;ber ihre Ergebnisse
- in LISA V im Oktober 1991, s. <ulink
- url="http://reality.sgi.com/zwicky_neu/testdump.doc.html">Torture-testing
- Backup and Archive Programs</ulink>.</para>
- </sect2>
-
- <sect2>
- <title>Die Wiederherstellung in einem Notfall</title>
-
- <sect3>
- <title>Vor dem Ungl&uuml;ck</title>
-
- <para>Es sind nur vier Vorkehrungen zu treffen, um auf jedes
- erdenkliche Ungl&uuml;ck vorbereitet zu sein.</para>
-
- <para>Als erstes drucken Sie das Disklabel jeder Ihrer Festplatten
- (z.B. mittels <command>disklabel da0 | lpr</command>), die
- Partitions- und Dateisystemtabelle jeder Festplatte (mit
- <filename>/etc/fstab</filename>) sowie alle Bootmeldungen, jeweils
- in zweifacher Ausfertigung.</para>
-
- <para>Zweitens, &uuml;berzeugen Sie sich, dass sowohl die
- Bootdiskette als auch die Reparaturdiskette
- (<filename>boot.flp</filename> bzw. <filename>fixit.flp</filename>)
- all Ihre Ger&auml;te ansprechen k&ouml;nnen. Die einfachste Methode
- dies nach zu pr&uuml;fen ist, Ihren Rechner mit der Boot-Diskette im
- Floppylaufwerk neu zu starten und die Bootmeldungen zu durchzusehen.
- Wenn all Ihre Ger&auml;te aufgelistet sind und funktionieren,
- k&ouml;nnen Sie weiter zu Schritt drei gehen.</para>
-
- <para>Ist das nicht der Fall, m&uuml;ssen Sie sich eine eigene
- Version der beiden zum Booten ben&ouml;tigten Disketten erstellen.
- Diese m&uuml;ssen einen Kernel enthalten, der all Ihre Platten
- mounten kann und Zugriff auf Ihr Bandlaufwerk gestattet. Diese
- Disketten m&uuml;ssen ferner folgende Programme enthalten:
- &man.fdisk.8;, &man.disklabel.8;, &man.newfs.8;, &man.mount.8; sowie
- jedes Backup-Programm, das Sie verwenden. Diese Programme
- m&uuml;ssen statisch gelinkt sein. Falls Sie &man.dump.8;
- verwenden, muss die Diskette auch &man.restore.8; enthalten.</para>
-
- <para>Drittens, machen Sie oft Backups auf Band. Jede &Auml;nderung
- seit Ihrem letzten Backup kann unwiederbringlich verloren gehen.
- Versehen Sie die Backup-B&auml;nder mit Schreibschutz.</para>
-
- <para>Viertens, testen Sie aus, wie die Disketten (entweder
- <filename>boot.flp</filename> und <filename>fixit.flp</filename>
- oder Ihre beiden eigenen Disketten aus Schritt zwei) und die
- B&auml;nder mit den Backups zu behandeln sind. Machen Sie sich
- Notizen zu diesem Test. Bewahren Sie diese Notizen zusammen mit den
- Bootdisketten, den Ausdrucken und den B&auml;ndern mit den Backups
- auf. Wenn der Ernstfall eintritt, werden Sie vielleicht so genervt
- sein, dass Sie ohne Ihre Notizen evt. das Backup auf Ihren
- B&auml;ndern zerst&ouml;ren. (Wie das geht? Man braucht nur
- ungl&uuml;cklicherweise den Befehl <command>tar cvf
- /dev/rsa0</command> einzugeben um ein Band zu
- &uuml;berschreiben).</para>
-
- <para>Als zus&auml;tzliche Sicherheitsvorkehrung, kann man jeweils
- die Disketten und B&auml;nder zweifach erstellen. Eine der Kopien
- sollte an einem entfernten Standort aufbewahrt werden. Ein
- entfernter Standort ist NICHT der Keller im gleichen
- B&uuml;rogeb&auml;ude. Eine Anzahl von Firmen im World Trade Center
- musste diese Lektion auf die harte Tour lernen. Ein entfernter
- Standort sollte von Ihrem Computer und Ihren Festplatten
- physikalisch durch eine erhebliche Entfernung getrennt sein.</para>
-
- <para>Ein Beispielskript zum Erstellen eigener Bootdisketten:</para>
-
- <programlisting>
-<![ CDATA [#!/bin/sh
-#
-# Erstellen einer Diskette zur Wiederherstellung eines Backups
-#
-# Diskette formatieren
-#
-PATH=/bin:/sbin:/usr/sbin:/usr/bin
-
-fdformat -q fd0
-if [ $? -ne 0 ]
-then
-echo "Bad floppy, please use a new one"
-exit 1
-fi
-
-# Die Bootbloecke auf die Diskette schreiben
-#
-disklabel -w -B /dev/rfd0c fd1440
-
-#
-# Dateisystem fuer die (einzige) Partition auf der Diskette
-#
-newfs -t 2 -u 18 -l 1 -c 40 -i 5120 -m 5 -o space /dev/rfd0a
-
-#
-# Diskette mounten
-#
-mount /dev/fd0a /mnt
-
-#
-# Benoetigte Verzeichnisse erstellen
-#
-mkdir /mnt/dev
-mkdir /mnt/bin
-mkdir /mnt/sbin
-mkdir /mnt/etc
-mkdir /mnt/root
-mkdir /mnt/mnt # fuer die Root-Partition
-mkdir /mnt/tmp
-mkdir /mnt/var
-
-#
-# die Verzeichnisse bevoelkern
-#
-if [ ! -x /sys/compile/MINI/kernel ]
-then
-cat << EOM
-Der MINI_Kernel existiert nicht, bitte einen erzeugen.
-Hier ein Beispiel einer Konfigurationsdatei:
-#
-# MINI -- Ein FreeBSD-Kernel, der auf die Diskette passt.
-#
-machine "i386"
-cpu "I486_CPU"
-ident MINI
-maxusers 5
-
-options INET # notwendig fuer _tcp _icmpstat _ipstat
-# _udpstat _tcpstat _udb
-options FFS #Berkeley Fast File System
-options FAT_CURSOR #Blockcursor in syscons oder pccons
-options SCSI_DELAY=15 #traue nicht Joe's SCSI-Geraet
-options NCONS=2 #2 virtuelle Konsolen
-options USERCONFIG #Konfiguration mit -c XXX zulassen
-
-
-config kernel root on da0 swap on da0 and da1 dumps on da0
-
-controller isa0
-controller pci0
-
-controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
-disk fd0 at fdc0 drive 0
-
-controller ncr0
-
-controller scbus0
-
-device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr
-device npx0 at isa? port "IO_NPX" irq 13 vector npxintr
-
-device da0
-device da1
-device da2
-
-device sa0
-
-pseudo-device loop # von INET benoetigt
-pseudo-device gzip # komprimierte a.out-Dateien ausfuehren
-EOM
-exit 1
-fi
-
-cp -f /sys/compile/MINI/kernel /mnt
-
-gzip -c -best /sbin/init > /mnt/sbin/init
-gzip -c -best /sbin/fsck > /mnt/sbin/fsck
-gzip -c -best /sbin/mount > /mnt/sbin/mount
-gzip -c -best /sbin/halt > /mnt/sbin/halt
-gzip -c -best /sbin/restore > /mnt/sbin/restore
-
-gzip -c -best /bin/sh > /mnt/bin/sh
-gzip -c -best /bin/sync > /mnt/bin/sync
-
-cp /root/.profile /mnt/root
-
-cp -f /dev/MAKEDEV /mnt/dev
-chmod 755 /mnt/dev/MAKEDEV
-
-chmod 500 /mnt/sbin/init
-chmod 555 /mnt/sbin/fsck /mnt/sbin/mount /mnt/sbin/halt
-chmod 555 /mnt/bin/sh /mnt/bin/sync
-chmod 6555 /mnt/sbin/restore
-
-#
-# Geraetedateien erstellen
-#
-cd /mnt/dev
-./MAKEDEV std
-./MAKEDEV da0
-./MAKEDEV da1
-./MAKEDEV da2
-./MAKEDEV sa0
-./MAKEDEV pty0
-cd /
-
-#
-# Minimale Dateisystemtabelle erstellen
-#
-cat > /mnt/etc/fstab <<EOM
-/dev/fd0a / ufs rw 1 1
-EOM
-
-#
-# Minimale Passwortdatei erstellen
-#
-cat > /mnt/etc/passwd <<EOM
-root:*:0:0:Charlie &:/root:/bin/sh
-EOM
-
-cat > /mnt/etc/master.passwd <<EOM
-root::0:0::0:0:Charlie &:/root:/bin/sh
-EOM
-
-chmod 600 /mnt/etc/master.passwd
-chmod 644 /mnt/etc/passwd
-/usr/sbin/pwd_mkdb -d/mnt/etc /mnt/etc/master.passwd
-
-#
-# Die Diskette aushaengen und den Benutzer informieren
-#
-/sbin/umount /mnt
-echo "Die Diskette wurde ausgehaengt und ist jetzt bereit."]]></programlisting>
- </sect3>
-
- <sect3>
- <title>Nach dem Ungl&uuml;ck</title>
-
- <para>Die Schl&uuml;sselfrage ist, ob Ihre Hardware &uuml;berlebt
- hat. Denn da Sie ja regelm&auml;&szlig;ig Backups angefertigt
- haben, brauchen Sie sich um die Software keine Sorgen zu
- machen.</para>
-
- <para>Falls die Hardware besch&auml;digt wurde, ersetzen Sie zuerst
- die defekten Teile.</para>
-
- <para>Falls die Hardware funktioniert, &uuml;berpr&uuml;fen Sie die
- Disketten. Wenn Sie eigene Bootdisketten verwenden, booten Sie im
- Single-User-Modus (geben dazu Sie <literal>-s</literal> am
- Boot-Prompt <prompt>boot:</prompt> ein). &Uuml;berspringen Sie den
- folgenden Paragrafen.</para>
-
- <para>Wenn Sie die Standarddisketten <filename>boot.flp</filename>
- und <filename>fixit.flp</filename> verwenden, lesen Sie hier weiter.
- Legen Sie die Bootdiskette <filename>boot.flp</filename> in das
- erste Floppylaufwerk ein und starten Sie den Computer. Wie
- &uuml;blich wird dann das originale Installationsmen&uuml; von
- FreeBSD gestartet. W&auml;hlen Sie die Option
- <literal>Fixit--Repair mode with CDROM or floppy.</literal>. Legen
- Sie die Diskette <filename>fixit.flp</filename> ein, wenn danach
- gefragt wird. <command>restore</command> und die anderen Programme,
- die Sie ben&ouml;tigen, befinden sich dann in
- <filename>/mnt2/stand</filename>.</para>
-
- <para>Stellen Sie die Dateisysteme nacheinander, getrennt von
- einander, wieder her.</para>
-
- <para>Versuchen Sie die Root-Partition Ihrer ersten Festplatte
- &man.mount.8; einzuh&auml;ngen (z.B. mit <command>mount /dev/sd0a
- /mnt</command>). Wenn das Disklabel besch&auml;digt wurde, benutzen
- Sie &man.disklabel.8; um die Platte neu zu partitionieren und zu
- benennen und zwar so, dass die Festplatte mit dem Label
- &uuml;bereinstimmt, das Sie ausgedruckt und aufbewahrt haben.</para>
-
- <para>Verwenden Sie &man.newfs.8; um neue Dateisysteme auf den
- Partitionen anzulegen. H&auml;ngen Sie nun die Root-Partition der
- Festplatte mit Schreibzugriff ein (mit <command>mount -u -o rw
- /mnt</command>). Benutzen Sie Ihr Backup-Programm um die Daten
- f&uuml;r das jeweilige Dateisystem aus den Backup-B&auml;ndern
- wieder her zu stellen (z.B. durch <command>restore vrf
- /dev/sta</command>). H&auml;ngen Sie das Dateisystem wieder aus
- (z.B. durch <command>umount /mnt</command>). Wiederholen Sie diesen
- Ablauf f&uuml;r jedes betroffene Dateisystem.</para>
-
- <para>Sobald Ihr System wieder l&auml;uft, machen Sie gleich wieder
- ein vollst&auml;ndiges Backup auf neue B&auml;nder. Denn die
- Ursache f&uuml;r den Absturz oder den Datenverlust kann wieder
- zuschlagen. Eine weitere Stunde, die Sie jetzt noch
- dranh&auml;ngen, kann Ihnen sp&auml;ter ein weiteres Missgeschick
- ersparen.</para>
- </sect3>
-
-<![ %not.published; [
-
- <sect3>
- <title>* Ich habe mich nicht auf Missgeschicke vorbereitet - was
- nun?</title>
-
- <para></para>
- </sect3>
-
-]]>
-
- </sect2>
- </sect1>
-
- <sect1 id="backups-floppybackups">
- <title>Was ist mit Backups auf Disketten?</title>
-
- <sect2 id="floppies-using">
- <title>Kann ich Disketten zum Backup meiner Daten verwenden?</title>
-
- <para>Disketten sind kein wirklich geeignetes Medium f&uuml;r Backups
- aus folgenden Gr&uuml;nden:</para>
-
- <itemizedlist>
- <listitem>
- <para>Disketten sind unzuverl&auml;ssig, besonders
- langfristig.</para>
- </listitem>
-
- <listitem>
- <para>Speichern und Wiederherstellen ist sehr langsam.</para>
- </listitem>
-
- <listitem>
- <para>Sie haben eine sehr eingeschr&auml;nkte Kapazit&auml;t (Die
- Zeiten sind l&auml;ngst vorbei, wo eine ganze Festplatte auf ein
- Dutzend Floppies oder so gespeichert werden konnte).</para>
- </listitem>
- </itemizedlist>
-
- <para>Wenn jedoch keine andere M&ouml;glichkeit zum Datenbackup
- vorhanden ist, dann sind Disketten immer noch besser als gar kein
- Backup.</para>
-
- <para>Wenn man gezwungen ist Disketten zu verwenden, dann sollte man
- auf eine gute Qualit&auml;t achten. Floppies, die schon einige Jahre
- im B&uuml;ro herumgelegen haben, sind eine schlechte Wahl. Ideal sind
- neue Disketten von einem renommierten Hersteller.</para>
- </sect2>
-
- <sect2 id="floppies-creating">
- <title>Wie mache ich ein Backup auf Disketten?</title>
-
- <para>Die beste Art eines Diskettenbackups ist der Befehl &man.tar.1;
- mit der Mehrfachband-Option <option>-M</option>, die es
- erm&ouml;glicht ein Backup &uuml;ber mehrere Floppies zu
- verteilen.</para>
-
- <para>Ein Backup aller Dateien im aktuellen Verzeichnis
- einschlie&szlig;lich aller Unterverzeichnisse wird durch den folgenden
- Befehl veranlasst (als root):</para>
-
- <screen>&prompt.root; <userinput>tar Mcvf /dev/rfd0 *</userinput></screen>
-
- <para>Wenn die erste Floppy voll ist, meldet sich &man.tar.1; und
- verlangt einen Diskettenwechsel (weil &man.tar.1; unabh&auml;ngig vom
- Medium arbeitet, wird der n&auml;chste Band (Volume) verlangt, was in
- diesem Zusammenhang eine Diskette bedeutet), in etwa wie folgt:</para>
-
- <screen>Prepare volume #2 for /dev/rfd0 and hit return:</screen>
-
- <para>Dies wird mit steigender Volumezahl wiederholt, bis alle
- angebenen Dateien archiviert sind.</para>
- </sect2>
-
- <sect2 id="floppies-compress">
- <title>K&ouml;nnen Diskettenbackups komprimiert werden?</title>
-
- <para>Leider erlaubt es &man.tar.1; nicht, die Option
- <option>-z</option> f&uuml;r Multi-Volume-Archive zu verwenden. Man
- kann nat&uuml;rlich alle Dateien mit &man.gzip.1; komprimieren, sie
- mit &man.tar.1; auf die Floppies aufspielen, und dann die Dateien
- wieder &man.gunzip.1; entkomprimieren!</para>
- </sect2>
-
- <sect2 id="floppies-restoring">
- <title>Wie werden Diskettenbackups wieder her gestellt?</title>
-
- <para>Zur Wiederherstellung des gesamten Archivs verwendet man:</para>
-
- <screen>&prompt.root; <userinput>tar Mxvf /dev/rfd0</userinput></screen>
-
- <para>Eine Methode um nur bestimmte Dateien wieder her zu stellen ist
- mit der ersten Diskette den folgenden Befehl auszuf&uuml;hren:</para>
-
- <screen>&prompt.root; <userinput>tar Mxvf /dev/rfd0 <replaceable>filename</replaceable></userinput></screen>
-
- <para>&man.tar.1; wird dann dir folgenden Disketten anfordern, bis die
- ben&ouml;tigte Datei gefunden ist.</para>
-
- <para>Wenn man die Diskette kennt auf der sich die Datei befindet,
- kann man alternativ diese Diskette auch direkt einlegen und den
- gleichen Befehl wie oben verwenden. Man beachte, dass, falls die
- erste Datei eine Fortsetzung eine Fortsetzung einer Datei von einer
- der vorigen Disketten ist, &man.tar.1; die Warnung ausgibt, dass diese
- Datei nicht wiederhergestellt werden kann, selbst dann, wenn dies gar
- nicht verlangt wurde!</para>
- </sect2>
- </sect1>
-</chapter>
-
-<!--
- Local Variables:
- mode: sgml
- sgml-declaration: "../chapter.decl"
- sgml-indent-data: t
- sgml-omittag: nil
- sgml-always-quote-attributes: t
- sgml-parent-document: ("../book.sgml" "part" "chapter")
- End:
--->
diff --git a/de_DE.ISO8859-1/books/handbook/basics/chapter.sgml b/de_DE.ISO8859-1/books/handbook/basics/chapter.sgml
deleted file mode 100644
index 2958665e8b..0000000000
--- a/de_DE.ISO8859-1/books/handbook/basics/chapter.sgml
+++ /dev/null
@@ -1,581 +0,0 @@
-<!--
- The FreeBSD Documentation Project
- The FreeBSD German Documentation Project
-
- Original version 1.20
- $FreeBSD$
--->
-
-<chapter id="basics">
- <title>Unix Grundlagen</title>
-
- <sect1>
- <title>&Uuml;bersicht</title>
-
- <para><emphasis>Neugeschrieben von Chris Shumway
- <email>cshumway@cdrom.com</email>, 10 Mar 2000.</emphasis></para>
- <para><emphasis>&Uuml;bersetzt von &a.de.pierau,
- Juni 2000</emphasis></para>
-
- <para>Das folgende Kapitel umfa&szlig;t die grundlegenden Kommandos
- und Funktionsweisen des Betriebssystems FreeBSD. Wenn FreeBSD neu
- f&uuml;r Sie ist, dann sollten Sie dieses Kapitel auf jeden Fall
- lesen, bevor Sie um Hilfe fragen.</para>
- </sect1>
-
- <sect1 id="permissions">
- <title>Zugriffsrechte</title>
-
- <para>Die Grundlagen von FreeBSD, dessen Geschichte in BSD UNIX
- begr&uuml;ndet ist, st&uuml;tzen sich auf verschiedene UNIX
- Grundkonzepte. Das erste und ausgepr&auml;gteste: FreeBSD ist
- ein Multi-User Betriebssystem. Das System erm&ouml;glicht,
- da&szlig; mehrere User gleichzeitig an v&ouml;llig verschiedenen
- und unabh&auml;ngigen Aufgaben arbeiten k&ouml;nnen. Es ist
- verantwortlich f&uuml;r eine gerechte Auf- und Zuteilung von
- Nachfragen nach Hardware- und Peripherieger&auml;ten, Speicher
- und CPU Zeit unter den Usern.</para>
-
- <para>Da das System mehere Benutzer unterst&uuml;tzt, hat alles,
- was das System verwaltet, einen Satz von Rechten, die bestimmen,
- wer die jeweilige Ressource lesen, schreiben oder ausf&uuml;hren
- darf. Diese Zugriffsrechte stehen in einer Achtergruppe, die in
- drei Teile unterteilt ist: einen f&uuml;r den Besitzer der
- Datei, einen f&uuml;r die Gruppe¸ zu der die Datei geh&ouml;rt
- und einen f&uuml;r alle anderen. Die numerische Darstellung
- sieht wie folgt aus:</para>
-
- <informaltable frame="none">
- <tgroup cols="3">
- <thead>
- <row>
- <entry>Wert</entry>
- <entry>Zugriffsrechte</entry>
- <entry>Auflistung im Verzeichnis</entry>
- </row>
- </thead>
-
- <tbody>
- <row>
- <entry>0</entry>
- <entry>Kein Lesen, Kein Schreiben, Kein Ausf&uuml;hren</entry>
- <entry><literal>---</literal></entry>
- </row>
-
- <row>
- <entry>1</entry>
- <entry>Kein Lesen, Kein Schreiben, Ausf&uuml;hren</entry>
- <entry><literal>--x</literal></entry>
- </row>
-
- <row>
- <entry>2</entry>
- <entry>Kein Lesen, Schreiben, Kein Ausf&uuml;hren</entry>
- <entry><literal>-w-</literal></entry>
- </row>
-
- <row>
- <entry>3</entry>
- <entry>Kein Lesen, Schreiben, Ausf&uuml;hren</entry>
- <entry><literal>-wx</literal></entry>
- </row>
-
- <row>
- <entry>4</entry>
- <entry>Lesen, Kein Schreiben, Kein Ausf&uuml;hren</entry>
- <entry><literal>r--</literal></entry>
- </row>
-
- <row>
- <entry>5</entry>
- <entry>Lesen, Kein Schreiben, Ausf&uuml;hren</entry>
- <entry><literal>r-x</literal></entry>
- </row>
-
- <row>
- <entry>6</entry>
- <entry>Lesen, Schreiben, Kein Ausf&uuml;hren</entry>
- <entry><literal>rw-</literal></entry>
- </row>
-
- <row>
- <entry>7</entry>
- <entry>Lesen, Schreiben, Ausf&uuml;hren</entry>
- <entry><literal>rwx</literal></entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>Bei einer ausf&uuml;hrlichen Verzeichnisauflistung mittels
- <command>ls -l</command> zeigt eine Spalte die Zugriffsrechte
- f&uuml;r den Besitzer, die Gruppe und alle anderen an. Hier
- sieht man, wie das aussehen k&ouml;nnte:</para>
-
- <screen>-rw-r--r--</screen>
-
- <para>Das erste Zeichen von links ist ein Sysmbol, welches angibt,
- ob es sich um eine normale Datei, ein Verzeichnis, ein special-
- oder block-device, ein Socket oder irgend eine andere
- Pseudo-Datei handelt. Die n&auml;chsten drei Zeichen,
- dargestellt als <literal>rw-</literal>, ergeben die Rechte
- f&uuml;r den Datei-Besitzer. Die drei Zeichen danach
- <literal>r--</literal> die Rechte der Gruppe, zu der die Datei
- geh&ouml;rt. Die letzten drei Zeichen, <literal>r--</literal>,
- geben die Rechte f&uuml;r den Rest der Welt an. Ein Minus
- bedeutet, da&szlig; das Recht nicht gegeben ist. In diesem Fall
- sind die Zugriffsrechte also: der Eigent&uuml;mer kann die Datei
- lesen und schreiben, die Gruppe kann lesen und alle anderen
- k&ouml;nnen auch nur lesen. Entsprechend obiger Tabelle
- w&auml;ren die Zugriffsrechte f&uuml;r diese Datei
- <literal>644</literal>, worin jede Ziffer die drei Teile der
- Zugriffrechte dieser Datei verk&ouml;rpert.</para>
-
- <para>Das ist alles sch&ouml;n und gut, aber wie kontrolliert das
- System die Rechte von Hardware Ger&auml;ten? FreeBSD behandelt
- die meisten Hardware Ger&auml;te als Dateien, welche Programme
- &ouml;ffnen, lesen und mit Daten beschreiben k&ouml;nnen wie
- alle anderen Dateien auch. Diese Spezial-Dateien sind im
- Verzeichnis <filename>/dev</filename> gespeichert.</para>
-
- <para>Verzeichnisse werden ebenfalls wie Dateien behandelt. Sie
- haben Lese-, Schreib- und Ausf&uuml;hr-Rechte. Das
- Ausf&uuml;hrungs-Bit hat eine etwas andere Bedeutung f&uuml;r
- ein Verzeichnis als f&uuml;r eine Datei. Die Ausf&uuml;hrbarkeit
- eines Verzeichnisses bedeutet, da&szlig; man darin Suchen kann.
- Zum Beispiel kann man sich in diesem Verzeichnis eine Auflistung
- erstellen.</para>
-
- <para>Es gibt noch mehr Rechte, aber die werden vor allem in
- speziellen Umst&auml;nden benutzt, wie zum Beispiel bei
- setuid binaries und sticky directories. Wollen Sie mehr
- &uuml;ber Zugriffsrechte von Dateien erfahren, lesen Sie in die
- &man.chmod.1; Man-Page.</para>
- </sect1>
-
- <sect1 id="dirstructure">
- <title>Verzeichnis-Strukturen</title>
-
- <para>Da FreeBSD seine Dateisysteme nutzt, um viele grundlegende
- Systemt&auml;tigkeiten festzulegen, ist die Hierarchie des
- Dateisystems &auml;u&szlig;erst wichtig. Durch den Umstand,
- da&szlig; die Man-Page &man.hier.7; eine komplette Beschreibung
- der Verzeichnisstruktur bietet, wird sie hier nicht dupliziert.
- Bitte lesen Sie &man.hier.7; f&uuml;r ausf&uuml;hrlichere
- Informationen.</para>
-
- <para>Von bedeutender Wichtigkeit ist die Wurzel aller
- Verzeichnisse, das / Verzeichnis. Dieses wird beim booten als
- erstes gemountet und es enth&auml;lt das Basissystem,
- welches zum boot-Zeitpunkt notwendig ist. Das / Verzeichnis
- enth&auml;lt au&szlig;erdem mount Punkte (Montierungspunkte)
- f&uuml;r jedes weitere Dateisystem, das Sie mounten
- wollen.</para>
-
- <para>Ein mount Punkt ist ein Verzeichnis, in das zus&auml;tzliche
- Dateisysteme ins / Verzeichnis eingepflanzt werden k&ouml;nnen.
- Standard mount Punkte beinhalten <filename>/usr</filename>,
- <filename>/var</filename>, <filename>/mnt</filename> und
- <filename>/cdrom</filename>. Auf diese Verzeichnisse verweisen
- &uuml;blicherweise Eintr&auml;ge in der Datei
- <filename>/etc/fstab</filename>. <filename>/etc/fstab</filename> ist
- eine Tabelle mit verschiedenen Dateisystemen und mount Punkten
- als Referenz des Systems. Die meisten der Dateisysteme in
- <filename>/etc/fstab</filename> werden zur boot Zeit automatisch
- durch das Skript &man.rc.8; gemountet, wenn die zugeh&ouml;rigen
- Eintr&auml;ge nicht mit der Option <option>noauto</option>
- versehen sind. Konsultieren Sie die &man.fstab.5; Man-Page
- f&uuml;r mehr Informationen &uuml;ber das Format der Datei
- <filename>/etc/fstab</filename> und den Optionen darin.</para>
- </sect1>
-
- <sect1 id="shells">
- <title>Shells</title>
-
- <para>Von der tagt&auml;glichen Arbeit mit FreeBSD wird eine Menge
- mit der Kommandozeilen Schnittstelle der Shell erledigt. Die
- Hauptaufgabe einer Shell besteht darin, Kommandos der Eingabe
- anzunehmen und diese auszuf&uuml;hren. Viele Shells haben
- au&szlig;erdem eingebaute Funktionen, um die t&auml;gliche
- Arbeit zu erleichtern, wie Dateiverwaltung, Editieren von
- Kommandozeilen, Makros und Umgebungsvariablen. FreeBSD
- enth&auml;lt die Shells sh (die Bourne Shell) und csh
- (die C-Shell) im Basissystem. Viele andere sind in der Ports
- Sammlung zu finden, von denen einige auch leistungsf&auml;higer
- sind, zum Beispiel tcsh und bash.</para>
-
- <para>Welche Shell soll ich benutzen? Das ist wirklich eine
- Geschmacksfrage. Sind Sie ein C Programmierer, finden Sie
- vielleicht eine C-artige Shell wie die tcsh angenehmer. Kommen
- Sie von Linux oder Ihnen ist eine UNIX Kommandozeile neu, so
- k&ouml;nnten Sie die bash probieren. Der Punkt ist, da&szlig;
- jede Shell ihre speziellen Eigenschaften hat, die mit Ihrer
- bevorzugten Arbeitsumgebung harmonieren k&ouml;nnen oder nicht.
- Sie m&uuml;ssen sich eine Shell aussuchen.</para>
-
- <para>Ein verbreitetes Merkmal in Shells ist die
- Dateinamen-Vervollst&auml;ndigung. Sie m&uuml;ssen nur einige
- Buchstaben eines Kommandos oder eines Dateinames eingeben und
- die Shell vervollst&auml;ndigt den Rest automatisch durch
- dr&uuml;cken der TAB-Taste. Hier ist ein Beispiel. Ich habe
- zwei Dateien <filename>foobar</filename> und
- <filename>foo.bar</filename>. Die Datei
- <filename>foo.bar</filename> m&ouml;chte ich l&ouml;schen. Nun
- w&uuml;rde ich an der Tastatur eingeben:
- <command>rm fo[TAB].[TAB]</command>.</para>
-
- <para>Die Shell g&auml;be dann ausgeben <command>rm
- foo[BEEP].bar</command>.</para>
-
- <para>[BEEP] meint den Rechner-Piepser. Diesen gibt die Shell
- aus, um anzuzeigen, da&szlig; es den Dateinamen nicht
- vervollst&auml;ndigen konnte, da es mehrere M&ouml;glichkeiten
- gibt. Beide Dateien <filename>foobar</filename> und
- <filename>foo.bar</filename> beginnen mit <literal>fo</literal>,
- so konnte nur bis <literal>foo</literal> erg&auml;nzt werden.
- Nachdem ich <literal>.</literal> eingab und dann die TAB-Taste
- dr&uuml;ckte, konnte die Shell den Rest f&uuml;r mich
- ausf&uuml;llen.</para>
-
- <para>Eine andere Funktion der Shell sind die Umgebungsvariablen.
- Das sind ver&auml;nderbare Schl&uuml;sselpaare im Umgebungsraum
- der Shell. Diesen Umgebungsraum kann jedes von der Shell
- aufgerufene Programm lesen. So kommt es, da&szlig; viel
- Programmkonfiguration darin enthalten ist. Hier eine Liste
- verbreiteter Umgebungsvariablen und was sie bedeuten:</para>
-
- <informaltable frame="none">
- <tgroup cols="2">
- <thead>
- <row>
- <entry>Variable</entry>
- <entry>Beschreibung</entry>
- </row>
- </thead>
-
- <tbody>
- <row>
- <entry><envar>USER</envar></entry>
- <entry>Name des zur Zeit angemeldeten Benutzers.</entry>
- </row>
-
- <row>
- <entry><envar>PATH</envar></entry>
- <entry>Liste mit Verzeichnissen (getrennt durch Doppelpunkt)
- zum Suchen nach Programmen.</entry>
- </row>
-
- <row>
- <entry><envar>DISPLAY</envar></entry>
- <entry>Wenn gesetzt der Netzwerkname des X11 Bildschirms
- f&uuml;r die Anzeige.</entry>
- </row>
-
- <row>
- <entry><envar>SHELL</envar></entry>
- <entry>Die aktuelle Shell.</entry>
- </row>
-
- <row>
- <entry><envar>TERM</envar></entry>
- <entry>Name des Terminals des Benutzers. Benutzt, um die
- F&auml;higkeiten des Terminals bestimmen.</entry>
- </row>
-
- <row>
- <entry><envar>TERMCAP</envar></entry>
- <entry>Datenbankeintrag der Terminal Escape Kodes,
- ben&ouml;tigt um verschieden Terminalfunktionen
- auszuf&uuml;hren.</entry>
- </row>
-
- <row>
- <entry><envar>OSTYPE</envar></entry>
- <entry>Typ des Betriebsystems. Z.B., FreeBSD.</entry>
- </row>
-
- <row>
- <entry><envar>MACHTYPE</envar></entry>
- <entry>Die CPU Architektur auf dem das System
- l&auml;uft.</entry>
- </row>
-
- <row>
- <entry><envar>EDITOR</envar></entry>
- <entry>Vom Benutzer bervorzugter Text-Editor.</entry>
- </row>
-
- <row>
- <entry><envar>PAGER</envar></entry>
- <entry>Vom Benutzer bevorzugter Text-Betrachter.</entry>
- </row>
-
- <row>
- <entry><envar>MANPATH</envar></entry>
- <entry>Liste mit Verzeichnissen (getrennt durch Doppelpunkt)
- zum Suchen nach Man-Pages.</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>Das Anzeigen oder Setzen von Umgebungsvariablen funktioniert
- von Shell zu Shell unterschiedlich. Zum Beispiel benutzt man
- in C-artigen Shells wie der tcsh dazu <command>setenv</command>.
- Unter Bourne-Shells wie sh oder bash w&uuml;rde man
- <command>set</command> und <command>export</command> benutzen
- zum ansehen oder setzen von aktuellen Umgebungsvariablen. Um
- beispielsweise die Variable <envar>EDITOR</envar> zu setzen oder
- zu modifizieren, w&uuml;rde folgendes Kommando die Variable
- <envar>EDITOR</envar> auf
- <filename>/usr/local/bin/emacs</filename> setzen:</para>
-
- <para><command>setenv EDITOR /usr/local/bin/emacs</command></para>
-
- <para>Unter Bourne-Shells:</para>
-
- <para><command>export EDITOR="/usr/local/bin/emacs"</command></para>
-
- <para>Sie k&ouml;nnen die meisten Shells Umgebungsvariablen
- expandieren lassen, in dem Sie in der Kommandozeile ein
- <literal>$</literal> davor eingeben. Zum Beispiel gibt
- <command>echo $TERM</command> aus, worauf <envar>$TERM</envar>
- gesetzt ist, weil die Shell <envar>$TERM</envar> expandiert
- und das Ergebnis an echo gibt.</para>
-
- <para>Shells behandeln eine Menge an Spezialzeichen, sogenannte
- meta-characters, als besondere Darstellungen f&uuml;r Daten.
- Das allgemeinste ist das Zeichen <literal>*</literal>, das eine
- beliebige Anzahl Zeichen in einem Dateinamen repr&auml;sentiert.
- Das Kommando <command>echo *</command> liefert nahezu das gleiche
- wie die Eingabe von <command>ls</command>, da die Shell alle
- Dateinamen die mit <command>*</command> &uuml;bereinstimmen an
- echo weitergibt.</para>
-
- <para>Um zu verhindern, da&szlig; die Shell diese Sonderzeichen
- interpretiert, kann man sie sch&uuml;tzen, indem man ihnen einen
- backslash (<literal>\</literal>) voranstellt. <command>echo
- $TERM</command> gibt aus, auf was auch immer Ihr Terminal
- gesetzt ist. <command>echo \$TERM</command> gibt
- <envar>$TERM</envar> genauso aus, wie es hier steht.</para>
-
- <sect2 id="changing-shells">
- <title>&Auml;ndern der Shell</title>
-
- <para>Der einfachste Weg Ihre Shell zu &auml;ndern, ist das
- Kommando <command>chsh</command> zu benutzen.
- <command>chsh</command> platziert Sie im Editor, welcher durch
- Ihre Umgebungsvariable <envar>EDITOR</envar> gesetzt ist,
- im <command>vi</command> wenn die Variable nicht gesetzt ist.
- &Auml;ndern Sie die Zeile mit <quote>Shell:</quote>
- entsprechend Ihren W&uuml;nschen.</para>
-
- <para>Sie k&ouml;nnen auch <command>chsh</command> mit der Option
- <option>-s</option> aufrufen, dann wird Ihre Shell gesetzt,
- ohne das&szlig; Sie in einen Editor gelangen. Um Ihre Shell
- zum Beispiel auf die bash zu &auml;ndern, geben Sie das
- folgende Kommando ein:</para>
-
- <screen>&prompt.user; <userinput>chsh -s /usr/local/bin/bash</userinput></screen>
-
- <para>Einfach <command>chsh</command> ohne Optionen und mit
- Editieren der entsprechenden Zeile w&uuml;rde auch
- funktionieren.</para>
-
- <note>
- <para>Die von Ihnen gew&uuml;nschte Shell
- <emphasis>mu&szlig;</emphasis> in <filename>/etc/shells</filename>
- aufgef&uuml;hrt sein. Haben Sie eine Shell aus der
- <!--<link linkend="ports">-->Ports Sammlung<!--</link>--> installiert,
- sollte das schon automatisch erledigt werden. Installierten
- Sie die Shell von Hand, so m&uuml;ssen Sie sie dort
- eintragen.</para>
-
- <para>Haben Sie beispielsweise die <command>bash</command> nach
- <filename>/usr/local/bin</filename> installiert, wollen Sie
- dies tun:</para>
-
- <screen>&prompt.root; <userinput>echo &quot;/usr/local/bin/bash&quot; &gt;&gt; /etc/shells</userinput></screen>
-
- <para>Danach <command>chsh</command> aufrufen.</para>
- </note>
- </sect2>
- </sect1>
-
- <sect1 id="editors">
- <title>Text Editoren</title>
-
- <para>Eine Menge der Konfiguration bei FreeBSD wird durch
- das Editieren von Textdateien erledigt. Deshalb ist es eine
- gute Idee, mit einem Texteditor vertraut zu werden. FreeBSD hat
- ein paar davon im Basissystem und sehr viel mehr in der Ports
- Sammlung.</para>
-
- <para>Der am leichtesten und einfachsten zu erlernende Editor nennt
- sich <application>ee</application>, was f&uuml;r easy editor steht.
- Um <application>ee</application> zu starten, gibt man in der
- Kommandozeile <command>ee filename</command> ein, worin
- <literal>filename</literal> der Name der zu editierenden Datei
- ist. Um zum Beispiel <filename>/etc/rc.conf</filename> zu
- editieren, tippen Sie <command>ee /etc/rc.conf</command>.
- Einmal im Editor, finden Sie alle Editor-Funktionen oben im
- Display aufgelistet. Das Einschaltungszeichen
- <literal>^</literal> meint die Control (oft Steuerung) Taste,
- also ^e hei&szlig;t, da&szlig; die Controltaste und dann der
- Buchstabe <literal>e</literal> gedr&uuml;ckt werden. Um
- <application>ee</application> zu verlassen, einfach die
- Escapetaste dr&uuml;cken und leave editor w&auml;hlen. Der
- Editor fragt Sie nach, ob Sie speichern m&ouml;chten, wenn die
- Datei ver&auml;ndert wurde.</para>
-
- <para>FreeBSD verf&uuml;gt &uuml;ber leistungf&auml;higere
- Editoren wie <application>vi</application> als Teil des
- Basissystems und <application>emacs</application> oder
- <application>vim</application> als Teil der Ports Sammlung.
- Diese Editoren bieten h&ouml;here Funktionalit&auml;t und
- Leistungsf&auml;higkeit jedoch auf Kosten einer etwas
- schwierigeren Erlernbarkeit. Dennoch, wenn Sie viel
- Textdateien editieren werden, sparen Sie auf lange Sicht mehr
- Zeit ein durch das Erlernen solcher Editoren wie
- <application>vim</application> oder
- <application>emacs</application>.</para>
- </sect1>
-
- <sect1>
- <title>Weitere Informationen...</title>
-
- <sect2 id="basics-man">
- <title>Man pages</title>
-
- <para>Die umfassendste Dokumentation rund um FreeBSD gibt es in
- Form von Man-Pages. Ann&auml;hrernd jedes Programm im System
- bringt eine kurze Referenzdokumentation mit, die die
- grunds&auml;tzliche Funktion und verschiedene Parameter
- erkl&auml;rt. Diese Dokumentationen kann man mit dem
- <command>man</command> Kommando benutzen. Die Benutzung des
- <command>man</command> Kommandos ist einfach:</para>
-
- <para><command>&prompt.user; man Kommando</command></para>
-
- <para><literal>Kommando</literal> ist der Name des Kommandos,
- &uuml;ber das Sie etwas erfahren wollen. Um beispielsweise
- mehr &uuml;ber das Kommando <command>ls</command> zu lernen,
- geben Sie ein:</para>
-
- <para><command>&prompt.user; man ls</command></para>
-
- <para>Die Online-Dokumentation ist in numerierte Sektionen
- unterteilt:</para>
-
- <orderedlist>
- <listitem>
- <para>Benutzerkommandos.</para>
- </listitem>
-
- <listitem>
- <para>Systemaufrufe und Fehlernummern.</para>
- </listitem>
-
- <listitem>
- <para>Funktionen der C Bibliothkene.</para>
- </listitem>
-
- <listitem>
- <para>Ger&auml;tetreiber.</para>
- </listitem>
-
- <listitem>
- <para>Dateiformate.</para>
- </listitem>
-
- <listitem>
- <para>Spiele und andere Unterhaltung.</para>
- </listitem>
-
- <listitem>
- <para>Verschiedene Informationen.</para>
- </listitem>
-
- <listitem>
- <para>Systemverwaltung und -Kommandos.</para>
- </listitem>
-
- <listitem>
- <para>Kernel Entwickler.</para>
- </listitem>
- </orderedlist>
-
- <para>In einigen F&auml;llen kann dasselbe Thema in mehreren
- Sektionen auftauchen. Es gibt zum Beispiel ein chmod
- Benutzerkommando und ein <literal>chmod()</literal>
- Systemaufruf. In diesem Fall k&ouml;nnen Sie dem man Kommando
- sagen, aus welcher Sektion Sie die Information erhalten
- m&ouml;chten, indem Sie die Sektion mit angeben:</para>
-
- <para><command>&prompt.user; man 1 chmod</command></para>
-
- <para>Dies wird Ihnen die Man-Page f&uuml;r das Benutzerkommando
- <command>chmod</command> zeigen. Verweise auf eine Sektion
- der Man-Pages werden traditionsgem&auml;&szlig; in Klammern
- gesetzt. So nezieht sich &man.chmod.1; auf das
- Benutzerkommando <command>chmod</command> und mit
- &man.chmod.2; ist der Systemaufruf gemeint.</para>
-
- <para>Das ist nett, wenn Sie den Namen eines Kommandos wissen,
- und lediglich wissen wollen, wie es zu benutzen ist. Aber was
- tun Sie, wenn Sie Sich nicht an den Namen des Kommandos
- erinnern k&ouml;nnen? Sie k&ouml;nnen man benutzen, um nach
- Schl&uuml;sselbegriffen in den Kommandobeschreibungen zu
- suchen, indem Sie den Parameter <option>-k</option>
- benutzen:</para>
-
- <para><command>&prompt.user; man -k mail</command></para>
-
- <para> Mit diesem Kommando bekommen Sie eine Liste der
- Kommandos, deren Beschreibung das Schl&uuml;sselwort
- <quote>mail</quote> enth&auml;lt. Diese Funktionalit&auml;t
- erhalten Sie auch, wenn Sie das Kommando apropos
- benutzen.</para>
-
- <para>Nun, Sie schauen Sich alle die geheimnisvollen Kommandos
- in <filename>/usr/bin</filename> an, haben aber nicht den
- blassesten Schimmer, wozu die meisten davon gut sind? Dann
- geben Sie doch einfach <command>&prompt.user; cd /usr/bin;
- man -f *</command> oder <command>&prompt.user; cd /usr/bin;
- whatis *</command> ein, beides tut dasselbe.</para>
- </sect2>
-
- <sect2 id="basics-info">
- <title>GNU Info Dateien</title>
-
- <para>FreeBSD enth&auml;lt viele Applikationen und Utilities
- der Free Software Foundation (FSF). Zus&auml;tzlich zu den
- Man-Pages bringen diese Programme ausf&uuml;hrlichere
- Hypertext-Dokumente (<literal>info</literal> genannt) mit,
- welche man sich mit dem Kommando <command>info</command>
- ansehen kann. Wenn Sie <application>emacs</application>
- installiert haben, k&ouml;nnen Sie auch dessen info-Modus
- benutzen.</para>
-
- <para>Um das Kommando &man.info.1; zu benutzen, geben Sie
- einfach ein:</para>
-
- <para><command>&prompt.user; info</command></para>
-
- <para>Eine kurze Einf&uuml;rung gibt es mit
- <literal>h</literal>; eine Befehlsreferenz erhalten Sie durch
- Eingabe von: <literal>?</literal>.</para>
- </sect2>
- </sect1>
-</chapter>
-<!--
- Local Variables:
- mode: sgml
- sgml-declaration: "../chapter.decl"
- sgml-indent-data: t
- sgml-omittag: nil
- sgml-always-quote-attributes: t
- sgml-parent-document: ("../book.sgml" "part" "chapter")
- End:
--->
-
diff --git a/de_DE.ISO8859-1/books/handbook/bibliography/chapter.sgml b/de_DE.ISO8859-1/books/handbook/bibliography/chapter.sgml
deleted file mode 100644
index b0d0288f8c..0000000000
--- a/de_DE.ISO8859-1/books/handbook/bibliography/chapter.sgml
+++ /dev/null
@@ -1,485 +0,0 @@
-<!--
- The FreeBSD Documentation Project
- The FreeBSD German Documentation Project
-
- Original version 1.26
- $FreeBSD: doc/de_DE.ISO_8859-1/books/handbook/bibliography/chapter.sgml,v 1.1 2000/06/29 10:08:28 alex Exp $
--->
-
-<appendix id="bibliography">
- <title>Bibliografie</title>
-
- <para><emphasis>&Uuml;bersetzt von &a.de.gruender</emphasis></para>
-
- <para>W&auml;hrend die Manual-Seiten die endg&uuml;ltige Auskunft
- &uuml;ber bestimmte Teile des FreeBSD Betriebssystems geben, so
- k&ouml;nnen sie jedoch nicht darstellen, wie man die einzelnen Teile
- zusammenf&uuml;gt, um ein vollst&auml;ndig laufendes Betriebssystem
- herzustellen. Daher gibt es keinen Ersatz f&uuml;r ein gutes Buch
- f&uuml;r UNIX System-Administration und ein gutes
- Benutzerhandbuch.</para>
-
- <sect1 id="bibliography-freebsd">
- <title>B&uuml;cher &amp; Magazine speziell f&uuml;r FreeBSD</title>
-
- <para><emphasis>Internationale B&uuml;cher &amp;
- Magazine:</emphasis></para>
-
- <itemizedlist>
- <listitem>
- <para><ulink
- url="http://jdli.tw.freebsd.org/publication/book/freebsd2/index.htm">Using FreeBSD</ulink> (auf chinesisch).</para>
- </listitem>
-
- <listitem>
- <para>FreeBSD for PC 98'ers (auf japanisch), herausgegeben von
- SHUWA System Co, LTD. ISBN 4-87966-468-5 C3055 P2900E.</para>
- </listitem>
-
- <listitem>
- <para>FreeBSD (auf japanisch), herausgegeben von CUTT. ISBN
- 4-906391-22-2 C3055 P2400E.</para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="http://www.shoeisha.co.jp/pc/index/shinkan/97_05_06.htm">Complete Introduction to FreeBSD</ulink> (auf japanisch), herausgegeben von <ulink url="http://www.shoeisha.co.jp/">Shoeisha Co., Ltd</ulink>. ISBN 4-88135-473-6 P3600E.</para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="http://www.ascii.co.jp/pb/book1/shinkan/detail/1322785.html">Personal UNIX Starter Kit FreeBSD</ulink> (auf japanisch), herausgegeben von <ulink url="http://www.ascii.co.jp/">ASCII</ulink>. ISBN 4-7561-1733-3 P3000E.</para>
- </listitem>
-
- <listitem>
- <para>FreeBSD Handbook (japanische &Uuml;bersetzung), herausgegeben
- von <ulink url="http://www.ascii.co.jp/">ASCII</ulink>. ISBN
- 4-7561-1580-2 P3800E.</para>
- </listitem>
-
- <listitem>
- <para>FreeBSD mit Methode (auf deutsch), herausgegeben von Computer und
- Literatur Verlag/Vertrieb Hanser, 1998. ISBN 3-932311-31-0.</para>
- </listitem>
-
- <listitem>
- <para><ulink
- url="http://www.pc.mycom.co.jp/FreeBSD/install-manual.html">FreeBSD Install and Utilization Manual</ulink> (auf japanisch), herausgegeben von <ulink url="http://www.pc.mycom.co.jp/">Mainichi Communications Inc.</ulink>.</para>
- </listitem>
- </itemizedlist>
-
- <para><emphasis>Englischsprachige B&uuml;cher &amp;
- Magazine:</emphasis></para>
-
- <itemizedlist>
- <listitem>
- <para><ulink
- url="http://www.cdrom.com/titles/freebsd/bsdcomp_bkx.phtml">
- The Complete FreeBSD</ulink>, herausgegeben von <ulink
- url="http://www.cdrom.com/">Walnut Creek CDROM</ulink>.</para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1 id="bibliography-userguides">
- <title>Handb&uuml;cher</title>
-
- <itemizedlist>
- <listitem>
- <para>Computer Systems Research Group, UC Berkeley. <emphasis>4.4BSD
- User's Reference Manual</emphasis>. O'Reilly &amp; Associates,
- Inc., 1994. ISBN 1-56592-075-9</para>
- </listitem>
-
- <listitem>
- <para>Computer Systems Research Group, UC Berkeley. <emphasis>4.4BSD
- User's Supplementary Documents</emphasis>. O'Reilly &amp;
- Associates, Inc., 1994. ISBN 1-56592-076-7</para>
- </listitem>
-
- <listitem>
- <para><emphasis>UNIX in a Nutshell</emphasis>. O'Reilly &amp;
- Associates, Inc., 1990. ISBN 093717520X</para>
- </listitem>
-
- <listitem>
- <para>Mui, Linda. <emphasis>What You Need To Know When You Can't Find
- Your UNIX System Administrator</emphasis>. O'Reilly &amp;
- Associates, Inc., 1995. ISBN 1-56592-104-6</para>
- </listitem>
-
- <listitem>
- <para>Die <ulink url="http://www-wks.acs.ohio-state.edu/">Ohio State
- University</ulink> hat ein <ulink
- url="http://www-wks.acs.ohio-state.edu/unix_course/unix.html">UNIX
- Introductory Course</ulink> geschrieben, welcher auch online im
- HTML- und Postscriptformat verf&uuml;gbar ist.</para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.jp.FreeBSD.org/">Jpman Project, Japan
- FreeBSD Users Group</ulink>. <ulink
- url="http://www.pc.mycom.co.jp/FreeBSD/urm.html">FreeBSD User's
- Reference Manual</ulink> (japanische &Uuml;bersetzung). <ulink
- url="http://www.pc.mycom.co.jp/">Mainichi Communications
- Inc.</ulink>, 1998. ISBN4-8399-0088-4 P3800E.</para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1 id="bibliography-adminguides">
- <title>Administrations-Anleitungen</title>
-
- <itemizedlist>
- <listitem>
- <para>Albitz, Paul and Liu, Cricket. <emphasis>DNS and
- BIND</emphasis>, 3nd Ed. O'Reilly &amp; Associates, Inc., 1998.
- ISBN 1-56592-512-2</para>
- </listitem>
-
- <listitem>
- <para>Computer Systems Research Group, UC Berkeley. <emphasis>4.4BSD
- System Manager's Manual</emphasis>. O'Reilly &amp; Associates,
- Inc., 1994. ISBN 1-56592-080-5</para>
- </listitem>
-
- <listitem>
- <para>Costales, Brian, et al. <emphasis>Sendmail</emphasis>, 2nd Ed.
- O'Reilly &amp; Associates, Inc., 1997. ISBN 1-56592-222-0</para>
- </listitem>
-
- <listitem>
- <para>Frisch, &AElig;leen. <emphasis>Essential System
- Administration</emphasis>, 2nd Ed. O'Reilly &amp; Associates,
- Inc., 1995. ISBN 1-56592-127-5</para>
- </listitem>
-
- <listitem>
- <para>Hunt, Craig. <emphasis>TCP/IP Network
- Administration</emphasis>, 2nd Ed. O'Reilly &amp; Associates, Inc., 1997.
- ISBN 1-56592-322-7</para>
- </listitem>
-
- <listitem>
- <para>Nemeth, Evi. <emphasis>UNIX System Administration
- Handbook</emphasis>. 3nd Ed. Prentice Hall, 2000. ISBN
- 0-13-020601-6</para>
- </listitem>
-
- <listitem>
- <para>Stern, Hal <emphasis>Managing NFS and NIS</emphasis> O'Reilly
- &amp; Associates, Inc., 1991. ISBN 0-937175-75-7</para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.jp.FreeBSD.org/">Jpman Project, Japan
- FreeBSD Users Group</ulink>. <ulink
- url="http://www.pc.mycom.co.jp/FreeBSD/sam.html">FreeBSD System
- Administrator's Manual</ulink> (japanische &Uuml;bersetzung). <ulink
- url="http://www.pc.mycom.co.jp/">Mainichi Communications
- Inc.</ulink>, 1998. ISBN4-8399-0109-0 P3300E.</para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1 id="bibliography-programmers">
- <title>Programmierhandb&uuml;cher</title>
-
- <itemizedlist>
- <listitem>
- <para>Asente, Paul. <emphasis>X Window System Toolkit</emphasis>.
- Digital Press. ISBN 1-55558-051-3</para>
- </listitem>
-
- <listitem>
- <para>Computer Systems Research Group, UC Berkeley. <emphasis>4.4BSD
- Programmer's Reference Manual</emphasis>. O'Reilly &amp;
- Associates, Inc., 1994. ISBN 1-56592-078-3</para>
- </listitem>
-
- <listitem>
- <para>Computer Systems Research Group, UC Berkeley. <emphasis>4.4BSD
- Programmer's Supplementary Documents</emphasis>. O'Reilly &amp;
- Associates, Inc., 1994. ISBN 1-56592-079-1</para>
- </listitem>
-
- <listitem>
- <para>Harbison, Samuel P. and Steele, Guy L. Jr. <emphasis>C: A
- Reference Manual</emphasis>. 4rd ed. Prentice Hall, 1995.
- ISBN 0-13-326224-3</para>
- </listitem>
-
- <listitem>
- <para>Kernighan, Brian and Dennis M. Ritchie. <emphasis>The C
- Programming Language.</emphasis>. PTR Prentice Hall, 1988.
- ISBN 0-13-110362-9</para>
- </listitem>
-
- <listitem>
- <para>Lehey, Greg. <emphasis>Porting UNIX Software</emphasis>.
- O'Reilly &amp; Associates, Inc., 1995. ISBN 1-56592-126-7</para>
- </listitem>
-
- <listitem>
- <para>Plauger, P. J. <emphasis>The Standard C Library</emphasis>.
- Prentice Hall, 1992. ISBN 0-13-131509-9</para>
- </listitem>
-
- <listitem>
- <para>Stevens, W. Richard. <emphasis>Advanced Programming in the UNIX
- Environment</emphasis>. Reading, Mass. : Addison-Wesley, 1992
- ISBN 0-201-56317-7</para>
- </listitem>
-
- <listitem>
- <para>Stevens, W. Richard. <emphasis>UNIX Network
- Programming</emphasis>. 2nd Ed, PTR Prentice Hall, 1998. ISBN
- 0-13-490012-X</para>
- </listitem>
-
- <listitem>
- <para>Wells, Bill. <quote>Writing Serial Drivers for UNIX</quote>.
- <emphasis>Dr. Dobb's Journal</emphasis>. 19(15), December 1994.
- pp68-71, 97-99.</para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1 id="bibliography-osinternals">
- <title>Betriebssystem-Interna</title>
-
- <itemizedlist>
- <listitem>
- <para>Andleigh, Prabhat K. <emphasis>UNIX System
- Architecture</emphasis>. Prentice-Hall, Inc., 1990. ISBN
- 0-13-949843-5</para>
- </listitem>
-
- <listitem>
- <para>Jolitz, William. <quote>Porting UNIX to the 386</quote>.
- <emphasis>Dr. Dobb's Journal</emphasis>. January 1991-July
- 1992.</para>
- </listitem>
-
- <listitem>
- <para>Leffler, Samuel J., Marshall Kirk McKusick, Michael J Karels and
- John Quarterman <emphasis>The Design and Implementation of the
- 4.3BSD UNIX Operating System</emphasis>. Reading, Mass. :
- Addison-Wesley, 1989. ISBN 0-201-06196-1</para>
- </listitem>
-
- <listitem>
- <para>Leffler, Samuel J., Marshall Kirk McKusick, <emphasis>The Design
- and Implementation of the 4.3BSD UNIX Operating System: Answer
- Book</emphasis>. Reading, Mass. : Addison-Wesley, 1991. ISBN
- 0-201-54629-9</para>
- </listitem>
-
- <listitem>
- <para>McKusick, Marshall Kirk, Keith Bostic, Michael J Karels, and
- John Quarterman. <emphasis>The Design and Implementation of the
- 4.4BSD Operating System</emphasis>. Reading, Mass. :
- Addison-Wesley, 1996. ISBN 0-201-54979-4</para>
- </listitem>
-
- <listitem>
- <para>Stevens, W. Richard. <emphasis>TCP/IP Illustrated, Volume 1:
- The Protocols</emphasis>. Reading, Mass. : Addison-Wesley,
- 1996. ISBN 0-201-63346-9</para>
- </listitem>
-
- <listitem>
- <para>Schimmel, Curt. <emphasis>Unix Systems for Modern
- Architectures</emphasis>. Reading, Mass. : Addison-Wesley, 1994.
- ISBN 0-201-63338-8</para>
- </listitem>
-
- <listitem>
- <para>Stevens, W. Richard. <emphasis>TCP/IP Illustrated, Volume 3:
- TCP for Transactions, HTTP, NNTP and the UNIX Domain
- Protocols</emphasis>. Reading, Mass. : Addison-Wesley, 1996.
- ISBN 0-201-63495-3</para>
- </listitem>
-
- <listitem>
- <para>Vahalia, Uresh. <emphasis>UNIX Internals -- The New
- Frontiers</emphasis>. Prentice Hall, 1996. ISBN
- 0-13-101908-2</para>
- </listitem>
-
- <listitem>
- <para>Wright, Gary R. and W. Richard Stevens. <emphasis>TCP/IP
- Illustrated, Volume 2: The Implementation</emphasis>. Reading,
- Mass. : Addison-Wesley, 1995. ISBN 0-201-63354-X</para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1 id="bibliography-security">
- <title>Sicherheits-Anleitung</title>
-
- <itemizedlist>
- <listitem>
- <para>Cheswick, William R. and Steven M. Bellovin. <emphasis>Firewalls
- and Internet Security: Repelling the Wily Hacker</emphasis>.
- Reading, Mass. : Addison-Wesley, 1995. ISBN
- 0-201-63357-4</para>
- </listitem>
-
- <listitem>
- <para>Garfinkel, Simson and Gene Spafford. <emphasis>Practical UNIX
- Security</emphasis>. 2nd Ed. O'Reilly &amp; Associates, Inc.,
- 1996. ISBN 1-56592-148-8</para>
- </listitem>
-
- <listitem>
- <para>Garfinkel, Simson. <emphasis>PGP Pretty Good
- Privacy</emphasis> O'Reilly &amp; Associates, Inc., 1995. ISBN
- 1-56592-098-8</para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1 id="bibliography-hardware">
- <title>Hardware-Anleitung</title>
-
- <itemizedlist>
- <listitem>
- <para>Anderson, Don and Tom Shanley. <emphasis>Pentium Processor
- System Architecture</emphasis>. 2nd Ed. Reading, Mass. :
- Addison-Wesley, 1995. ISBN 0-201-40992-5</para>
- </listitem>
-
- <listitem>
- <para>Ferraro, Richard F. <emphasis>Programmer's Guide to the EGA,
- VGA, and Super VGA Cards</emphasis>. 3rd ed. Reading, Mass. :
- Addison-Wesley, 1995. ISBN 0-201-62490-7</para>
- </listitem>
-
- <listitem>
- <para>Die Intel Corporation ver&ouml;ffentlicht Dokumentationen
- Ihrer CPUs, Chipsets und Standards auf ihrer <ulink
- url="http://developer.intel.com/">developer web site</ulink>,
- normalerweise als PDF-Dateien.</para>
- </listitem>
-
- <listitem>
- <para>Shanley, Tom. <emphasis>80486 System Architecture</emphasis>.
- 3rd ed. Reading, Mass. : Addison-Wesley, 1995. ISBN
- 0-201-40994-1</para>
- </listitem>
-
- <listitem>
- <para>Shanley, Tom. <emphasis>ISA System Architecture</emphasis>.
- 3rd ed. Reading, Mass. : Addison-Wesley, 1995. ISBN
- 0-201-40996-8</para>
- </listitem>
-
- <listitem>
- <para>Shanley, Tom. <emphasis>PCI System Architecture</emphasis>.
- 3rd ed. Reading, Mass. : Addison-Wesley, 1995. ISBN
- 0-201-40993-3</para>
- </listitem>
-
- <listitem>
- <para>Van Gilluwe, Frank. <emphasis>The Undocumented PC</emphasis>.
- Reading, Mass: Addison-Wesley Pub. Co., 1994. ISBN
- 0-201-62277-7</para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1 id="bibliography-history">
- <title>UNIX Geschichte</title>
-
- <itemizedlist>
- <listitem>
- <para>Lion, John <emphasis>Lion's Commentary on UNIX, 6th Ed. With
- Source Code</emphasis>. ITP Media Group, 1996. ISBN
- 1573980137</para>
- </listitem>
-
- <listitem>
- <para>Raymond, Eric S. <emphasis>The New Hacker's Dictionary, 3rd
- edition</emphasis>. MIT Press, 1996. ISBN
- 0-262-68092-0. Auch bekannt als das <ulink
- url="http://www.ccil.org/jargon/jargon.html">Jargon
- File</ulink></para>
- </listitem>
-
- <listitem>
- <para>Salus, Peter H. <emphasis>A quarter century of UNIX</emphasis>.
- Addison-Wesley Publishing Company, Inc., 1994. ISBN
- 0-201-54777-5</para>
- </listitem>
-
- <listitem>
- <para>Simon Garfinkel, Daniel Weise, Steven Strassmann. <emphasis>The
- UNIX-HATERS Handbook</emphasis>. IDG Books Worldwide, Inc.,
- 1994. ISBN 1-56884-203-1</para>
- </listitem>
-
- <listitem>
- <para>Don Libes, Sandy Ressler <emphasis>Life with UNIX</emphasis>
- &mdash; special edition. Prentice-Hall, Inc., 1989. ISBN
- 0-13-536657-7</para>
- </listitem>
-
- <listitem>
- <para><emphasis>The BSD family tree</emphasis>. 1997. <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/misc/bsd-family-tree">ftp://ftp.FreeBSD.org/pub/FreeBSD/FreeBSD-current/src/share/misc/bsd-family-tree</ulink> oder <ulink url="file:/usr/share/misc/bsd-family-tree">local</ulink> auf einem FreeBSD-current Rechner.</para>
- </listitem>
-
- <listitem>
- <para><emphasis>The BSD Release Announcements collection</emphasis>.
- 1997. <ulink
- url="http://www.de.FreeBSD.org/de/ftp/releases/">http://www.de.FreeBSD.org/de/ftp/releases/</ulink></para>
- </listitem>
-
- <listitem>
- <para><emphasis>Networked Computer Science Technical Reports
- Library</emphasis>. <ulink
- url="http://www.ncstrl.org/">http://www.ncstrl.org/</ulink></para>
- </listitem>
-
- <listitem>
- <para><emphasis>Old BSD releases from the Computer Systems Research
- group (CSRG)</emphasis>. <ulink
- url="http://www.mckusick.com/csrg/">http://www.mckusick.com/csrg/</ulink>:
- Das Paket mit 4 CDROM enth&auml;lt alle BSD-Versionen von 1BSD
- bis 4.4BSD und 4.4BSD-Lite2 (ungl&uuml;cklicherweise nicht
- 2.11BSD). Die letzte CD beinhaltet auch die finalen Sourcen
- inclusive den SCCS Dateien.</para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1 id="bibliography-journals">
- <title>Magazine und Journale</title>
-
- <itemizedlist>
- <listitem>
- <para><emphasis>The C/C++ Users Journal</emphasis>. R&amp;D
- Publications Inc. ISSN 1075-2838</para>
- </listitem>
-
- <listitem>
- <para><emphasis>Sys Admin &mdash; The Journal for UNIX System
- Administrators</emphasis> Miller Freeman, Inc., ISSN
- 1061-2688</para>
- </listitem>
- </itemizedlist>
- </sect1>
-</appendix>
-
-<!--
- Local Variables:
- mode: sgml
- sgml-declaration: "../appendix.decl"
- sgml-indent-data: t
- sgml-omittag: nil
- sgml-always-quote-attributes: t
- sgml-parent-document: ("../book.sgml" "part" "appendix")
- End:
--->
-
diff --git a/de_DE.ISO8859-1/books/handbook/book.sgml b/de_DE.ISO8859-1/books/handbook/book.sgml
deleted file mode 100644
index 93ff83dd5c..0000000000
--- a/de_DE.ISO8859-1/books/handbook/book.sgml
+++ /dev/null
@@ -1,114 +0,0 @@
-<!--
- The FreeBSD Documentation Project
- The FreeBSD German Documentation Project
-
- $FreeBSD: doc/de_DE.ISO_8859-1/books/handbook/book.sgml,v 1.5 2000/08/06 11:40:23 alex Exp $
--->
-
-<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
-<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
-%man;
-
-<!ENTITY % bookinfo PUBLIC "-//FreeBSD//ENTITIES DocBook BookInfo Entities//EN">
-%bookinfo;
-
-<!ENTITY % chapters SYSTEM "chapters.ent"> %chapters;
-<!ENTITY % authors SYSTEM "../../../en_US.ISO_8859-1/books/handbook/authors.ent"> %authors;
-<!ENTITY % de-authors SYSTEM "de-authors.ent"> %de-authors;
-<!ENTITY % mailing-lists SYSTEM "mailing-lists.ent"> %mailing-lists;
-<!ENTITY % newsgroups SYSTEM "newsgroups.ent"> %newsgroups;
-<!ENTITY % not.published "INCLUDE">
-
-<!-- Die aktuelle FreeBSD-RELEASE version. Wird für verschiedene Dinge benutzt,
- z.B. Links auf Webseiten usw. Solange NICHT ändern wie es nicht wirklich
- Release-Zeit ist. -->
-<!ENTITY rel.current CDATA "4.1">
-]>
-
-<book>
- <bookinfo>
- <title>FreeBSD Handbuch</title>
-
- <authorgroup>
- <author>
- <surname>The FreeBSD German Documentation Project</surname>
- <affiliation>
- <address>
- <email>de-bsd-translators@de.FreeBSD.org</email>
- </address>
- </affiliation>
- </author>
- </authorgroup>
-
- <pubdate>February 1999</pubdate>
-
- <copyright>
- <year>1995</year>
- <year>1996</year>
- <year>1997</year>
- <year>1998</year>
- <year>1999</year>
- <year>2000</year>
- <holder>The FreeBSD German Documentation Project</holder>
- </copyright>
-
- &bookinfo.legalnotice;
-
- <abstract>
- <para>Willkommen bei FreeBSD! Dieses Handbuch beschreibt die
- Installation und den t&auml;glichen Umgang mit <emphasis>FreeBSD
- Release &rel.current;</emphasis>.
- Das Handbuch ist <emphasis>jederzeit unter Bearbeitung</emphasis>
- und die Arbeit vieler Einzelpersonen. Manche Kapitel existieren noch
- nicht und andere Kapitel m&uuml;ssen auf den neusten Stand
- gebracht werden.
- Wenn Sie an diesem Projekt mithelfen m&ouml;chten, senden Sie bitte
- eine E-Mail an die &a.de.translators;. Die letzte Version des
- Handbuchs ist immer auf dem
- <ulink URL="http://www.FreeBSD.ORG/de/handbook/">FreeBSD Web
- Server</ulink> verf&uuml;gbar.
- Es kann au&szlig;erdem in verschiedenen Formaten und in komprimierter
- Form vom <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/doc">FreeBSD
- FTP Server</ulink> oder einer der vielen
-
-<!--
-<link linkend="mirrors-ftp">Mirror Seiten</link>
--->
-
- <ulink URL="http://www.FreeBSD.org/handbook/mirrors-ftp.html">Mirror
- Seiten</ulink> herunter geladen werden.
- Vielleicht m&ouml;chten Sie das Handbuch auch
- <ulink URL="http://www.FreeBSD.org/search.html">durchsuchen</ulink>.</para>
- </abstract>
- </bookinfo>
-
- <part>
- <title>Erste Schritte</title>
-
- &chap.basics;
- &chap.ports;
- </part>
-
- <part>
- <title>System Administration</title>
-
- &chap.backups;
- </part>
-
- <part>
- <title>Anhang</title>
-
- &chap.bibliography;
- </part>
-
-</book>
-
-<!--
- Local Variables:
- mode: sgml
- sgml-indent-data: t
- sgml-omittag: nil
- sgml-always-quote-attributes: t
- End:
--->
-
diff --git a/de_DE.ISO8859-1/books/handbook/chapter.decl b/de_DE.ISO8859-1/books/handbook/chapter.decl
deleted file mode 100644
index ce0a7ed16a..0000000000
--- a/de_DE.ISO8859-1/books/handbook/chapter.decl
+++ /dev/null
@@ -1 +0,0 @@
-<!DOCTYPE chapter PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN">
diff --git a/de_DE.ISO8859-1/books/handbook/chapters.ent b/de_DE.ISO8859-1/books/handbook/chapters.ent
deleted file mode 100644
index e711d7f9ba..0000000000
--- a/de_DE.ISO8859-1/books/handbook/chapters.ent
+++ /dev/null
@@ -1,21 +0,0 @@
-<!--
- Die Entities für jedes Kapitel im FreeBSD Handbuch.
- Jede Entity heißt chap.foo, wobei foo der Name des ID-Attributes
- dieses Kapitels ist und dem Verzeichnis, in dem die entsprechende
- .sgml Datei liegt, entspricht.
-
- Kapitel sollten in der Reihenfolge aufgelistet sein, in der auf sie
- referenziert wird.
-
- $FreeBSD: doc/de_DE.ISO_8859-1/books/handbook/chapters.ent,v 1.4 2000/06/29 10:08:28 alex Exp $
--->
-
-<!-- Teil Eins -->
-<!ENTITY chap.basics SYSTEM "basics/chapter.sgml">
-<!ENTITY chap.ports SYSTEM "ports/chapter.sgml">
-
-<!-- Teil Zwei -->
-<!ENTITY chap.backups SYSTEM "backups/chapter.sgml">
-
-<!-- Teil Fünf (Anhang) -->
-<!ENTITY chap.bibliography SYSTEM "bibliography/chapter.sgml">
diff --git a/de_DE.ISO8859-1/books/handbook/mailing-lists.ent b/de_DE.ISO8859-1/books/handbook/mailing-lists.ent
deleted file mode 100644
index 6f62fb4418..0000000000
--- a/de_DE.ISO8859-1/books/handbook/mailing-lists.ent
+++ /dev/null
@@ -1,114 +0,0 @@
-<!--
- Namen der FreeBSD Mailinglisten und verwandter Software
-
- $FreeBSD: doc/de_DE.ISO_8859-1/books/handbook/mailing-lists.ent,v 1.1 2000/06/11 18:50:56 alex Exp $
--->
-
-<!ENTITY a.advocacy "FreeBSD Bef&uuml;rworter Mailingliste
- <email>freebsd-advocacy@FreeBSD.org</email>">
-
-<!ENTITY a.announce "FreeBSD Ank&uuml;ndigungen Mailingliste
- <email>freebsd-announce@FreeBSD.org</email>">
-
-<!ENTITY a.bugs "FreeBSD Problem Report (PR) Mailingliste
- <email>freebsd-bugs@FreeBSD.org</email>">
-
-<!ENTITY a.chat "FreeBSD Chat Mailingliste
- <email>freebsd-chat@FreeBSD.org</email>">
-
-<!ENTITY a.core "FreeBSD Core Team
- <email>freebsd-core@FreeBSD.org</email>">
-
-<!ENTITY a.current "FreeBSD-current Mailingliste
- <email>freebsd-current@FreeBSD.org</email>">
-
-<!ENTITY a.cvsall "FreeBSD CVS Commit Nachrichten Mailingliste
- <email>cvs-all@FreeBSD.org</email>">
-
-<!ENTITY a.database "FreeBSD basierte Datenbanken Mailingliste
- <email>freebsd-database@FreeBSD.org</email>">
-
-<!ENTITY a.doc "FreeBSD Documentation Project Mailingliste
- <email>freebsd-doc@FreeBSD.org</email>">
-
-<!ENTITY a.emulation "FreeBSD-emulation Mailingliste
- <email>freebsd-emulation@FreeBSD.org</email>">
-
-<!ENTITY a.fs "FreeBSD Filesystem Project (Dateisysteme) Mailingliste
- <email>freebsd-fs@FreeBSD.org</email>">
-
-<!ENTITY a.hackers "FreeBSD technische Diskussionen Mailingliste
- <email>freebsd-hackers@FreeBSD.org</email>">
-
-<!ENTITY a.hardware "FreeBSD Hardware und Zubeh&ouml;r Mailingliste
- <email>freebsd-hardware@FreeBSD.org</email>">
-
-<!ENTITY a.isdn "FreeBSD ISDN Mailingliste
- <email>freebsd-isdn@FreeBSD.org</email>">
-
-<!ENTITY a.isp "FreeBSD Internet Service Providers Mailingliste
- <email>freebsd-isp@FreeBSD.org</email>">
-
-<!ENTITY a.java "FreeBSD Java Mailingliste
- <email>freebsd-java@FreeBSD.org</email>">
-
-<!ENTITY a.jobs "FreeBSD betreffende Stellenangebote/-gesuche Mailingliste
- <email>freebsd-jobs@FreeBSD.org</email>">
-
-<!ENTITY a.mobile "FreeBSD Laptop Computer Mailingliste
- <email>freebsd-mobile@FreeBSD.org</email>">
-
-<!ENTITY a.mozilla "FreeBSD Portierung des Mozilla Browsers Mailingliste
- <email>freebsd-mozilla@FreeBSD.org</email>">
-
-<!ENTITY a.multimedia "FreeBSD Multimedia Mailingliste
- <email>freebsd-multimedia@FreeBSD.org</email>">
-
-<!ENTITY a.net "FreeBSD Netzwerk und Netzwerktechnik Mailingliste
- <email>freebsd-net@FreeBSD.org</email>">
-
-<!ENTITY a.newbies "FreeBSD Anf&auml;nger Mailingliste
- <email>freebsd-newbies@FreeBSD.org</email>">
-
-<!ENTITY a.newbus "New Bus Architektur Mailingliste
- <email>new-bus-arch@bostonradio.org</email>">
-
-<!ENTITY a.ports "FreeBSD Ports Mailingliste
- <email>freebsd-ports@FreeBSD.org</email>">
-
-<!ENTITY a.questions "FreeBSD generelle Fragen Mailingliste
- <email>freebsd-questions@FreeBSD.org</email>">
-
-<!ENTITY a.scsi "FreeBSD SCSI Subsystem Mailingliste
- <email>freebsd-scsi@FreeBSD.org</email>">
-
-<!ENTITY a.security "FreeBSD Security Mailingliste
- <email>freebsd-security@FreeBSD.org</email>">
-
-<!ENTITY a.security-notifications "FreeBSD Sicherheits Benachrichtungen Mailingliste
- <email>freebsd-security-notifications@FreeBSD.org</email>">
-
-<!ENTITY a.small "FreeBSD-small Mailingliste
- <email>freebsd-small@FreeBSD.org</email>">
-
-<!ENTITY a.smp "FreeBSD Symmetric Multiprocessing Mailingliste
- <email>freebsd-smp@FreeBSD.org</email>">
-
-<!ENTITY a.stable "FreeBSD-stable Mailingliste
- <email>freebsd-stable@FreeBSD.org</email>">
-
-<!ENTITY a.tokenring "FreeBSD Tokenring Mailingliste
- <email>freebsd-tokenring@FreeBSD.org</email>">
-
-<!ENTITY a.www "FreeBSD Webmaster Mailingliste
- <email>freebsd-www@FreeBSD.org</email>">
-
-<!ENTITY a.majordomo "<email>majordomo@FreeBSD.org</email>">
-
-<!-- Deutsche Mailinglisten -->
-
-<!ENTITY a.de.translators "FreeBSD German Documentation Project Mailingliste
- <email>de-bsd-translators@de.FreeBSD.org</email>">
-
-<!ENTITY a.de.questions "deutsche FreeBSD Fragen Mailingliste
- <email>de-bsd-questions@de.FreeBSD.org</email>">
diff --git a/de_DE.ISO8859-1/books/handbook/newsgroups.ent b/de_DE.ISO8859-1/books/handbook/newsgroups.ent
deleted file mode 100644
index e580f9e3b7..0000000000
--- a/de_DE.ISO8859-1/books/handbook/newsgroups.ent
+++ /dev/null
@@ -1,10 +0,0 @@
-<!--
- Namen der FreeBSD Newsgroups
-
- $FreeBSD$
--->
-
-<!ENTITY ng.misc "die
- <ulink url='news:comp.unix.bsd.freebsd.misc'>comp.unix.bsd.freebsd.misc</ulink>
- Newsgroup">
-
diff --git a/de_DE.ISO8859-1/books/handbook/ports/chapter.sgml b/de_DE.ISO8859-1/books/handbook/ports/chapter.sgml
deleted file mode 100644
index 399652b334..0000000000
--- a/de_DE.ISO8859-1/books/handbook/ports/chapter.sgml
+++ /dev/null
@@ -1,1050 +0,0 @@
-<!--
- The FreeBSD Documentation Project
- The FreeBSD German Documentation Project
-
- Original version 1.111
- $FreeBSD: doc/de_DE.ISO_8859-1/books/handbook/ports/chapter.sgml,v 1.1 2000/08/18 12:47:40 alex Exp $
--->
-
-<chapter id="ports">
- <title>Installieren von Anwendungen: Die Ports-Sammlung</title>
-
- <para><emphasis>Neu geschrieben von &a.jim;, 22 November 1999.
- Urspr&uuml;ngliche Version von verschiedenen Leuten.</emphasis></para>
- <para><emphasis>&Uuml;bersetzt von &a.de.pierau, Juli 2000</emphasis></para>
-
- <sect1>
- <title>&Uuml;bersicht</title>
-
- <para>Die FreeBSD Ports-Sammlung erlaubt Ihnen das &Uuml;bersetzen
- und Installieren einer Vielzahl von Anwendungen mit minimalem
- Aufwand.</para>
-
- <para>Ein Port ist gew&ouml;hnlich eine Gruppe von <link
- linkend="ports-skeleton">Ger&uuml;sten</link>, die die minimalen
- Anpassungen enthalten, welche n&ouml;tig sind, damit sich
- eine Anwendung unter FreeBSD &uuml;bersetzen und installieren
- l&auml;&szlig;t.</para>
-
- <para>Trotz des ganzen Geredes von offenen Standards kann es eine
- verzwickte Angelegenheit werden, eine Anwednung unter verschiedenen
- UNIX Versionen zu &uuml;bersetzen. Sie k&ouml;nnen zufrieden sein,
- wenn sich die Anwendung sauber &uuml;bersetzen l&auml;&szlig;t, in die
- richtigen Verzeichnisse installiert und <quote>out-of-the-box</quote>
- fehlerfrei l&auml;uft. Dies wird aber sehr selten vorkommen.
- Die meiste Zeit werden Sie Modifizierungen vornehmen m&uuml;ssen, damit
- die Anwendung funktioniert. An diesem Punkt kommt die Ports-Sammlung
- zum Zuge.</para>
-
- <para>Die Grundidee hinter der Ports-Sammlung ist, all die
- verwirrenden Schritte zu eliminieren, welche n&ouml;tig sind,
- damit alles richtig funktioniert, so da&szlig; die Installation
- einfach und schmerzlos ist. Mit der Ports-Sammlung ist die
- ganze harte Arbeit bereits f&uuml;r Sie getan und Sie brauchen
- zum Installieren eines Ports aus der Ports-Sammlung lediglich
- <command>make install</command> eingeben.</para>
- </sect1>
-
- <sect1 id="ports-using">
- <title>Benutzen der Ports-Sammlung</title>
-
- <para>Die folgenden Abschnitte stellen die grundlegenden Anweisungen
- vor, um Anwendungen aus der Ports-Sammlung auf
- Ihren Rechner zu installieren oder zu l&ouml;schen.</para>
-
- <sect2 id="ports-skeleton">
- <title>Ports installieren</title>
-
- <para>Was ist mit einem <quote>Ger&uuml;st</quote> im Zusammenhang
- mit der Ports-Sammlung gemeint? In aller K&uuml;rze: ein
- Ger&uuml;st eines Ports ist ein minimaler Satz von Dateien, die
- f&uuml;r eine Anwendung ben&ouml;tigt werden, damit es sich
- unter FreeBSD sauber &uuml;bersetzen und installieren
- l&auml;&szlig;t. Ein jeder Port beinhaltet:</para>
-
- <itemizedlist>
- <listitem>
- <para>Eine Datei <filename>Makefile</filename>. Das
- <filename>Makefile</filename> enth&auml;lt verschiedene
- Anweisungen, die spezifizieren, wie die Anwendung kompiliert
- werden und wo sie auf Ihrem System installiert werden
- sollte.</para>
- </listitem>
-
- <listitem>
- <para>Ein Verzeichnis <filename>files</filename>. Dieses
- Verzeichnis enth&auml;lt eine Datei namens
- <filename>md5</filename>. Der Name kommt vom MD5
- Algorithmus, welcher zur Ermittlung der Pr&uuml;fsumme des
- Portes benutzt wird. Eine Pr&uuml;fsumme ist eine Zahl,
- die durch Addition aller Daten einer Datei entsteht.
- &Auml;ndert sich ein Zeichen in der Datei, so weicht die
- Pr&uuml;fsumme vom Original ab und eine Fehlermeldung
- erscheint. Damit sind Sie in der Lage, die Unterschiede zu
- bemerken und zu untersuchen.</para>
-
- <para>Dieses <filename>files</filename> Verzeichnis kann
- noch andere Dateien enthalten, die vom Port ben&ouml;tigt
- werden, aber nicht woanders in die Verzeichnis-Struktur
- geh&ouml;ren.</para>
- </listitem>
-
- <listitem>
- <para>Ein <filename>patches</filename> Verzeichnis. Hierin
- liegen Patches, welche das &Uuml;bersetzen und Installieren
- der Anwendung erm&ouml;glichen. Patches sind im Wesentlichen
- kleine Dateien, die &Auml;nderungen an speziellen Dateien
- s&uuml;zifizieren. Sie liegen als reiner Text vor und sagen
- ungef&auml;hr:
- <quote>L&ouml;sche Zeile 10</quote> oder
- <quote>&Auml;ndere Zeile 26 zu ...</quote>. Patches sind
- auch bekannt unter dem Namen <quote>diffs</quote>, weil
- Sie mit dem Programm <application>diff</application>
- erstellt werden.</para>
- </listitem>
-
- <listitem>
- <para>Ein Verzeichnis <filename>pkg</filename>. Dieses
- enth&auml;lt normalerweise drei Dateien. Gelegentlich sind
- es auch mehr, das h&auml;ngt vom Port ab. Die meisten
- Ports erfordern nur drei, und zwar diese:</para>
-
- <itemizedlist>
- <listitem>
- <para><filename>COMMENT</filename>. Eine einzeilige
- Beschreibung der Anwendung.</para>
- </listitem>
-
- <listitem>
- <para><filename>DESCR</filename>. Eine
- ausf&uuml;hrlichere oft mehrzeilige Beschreibung der
- Anwendung.</para>
- </listitem>
-
- <listitem>
- <para><filename>PLIST</filename>. Das ist eine Liste
- aller Dateien, die durch diesen Port installiert
- werden. Au&szlig;erdem sind hier Informationen enthalten,
- die bei der Deinstallation des Ports ben&ouml;tigt werden.
- </para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
-
- <para>Nun haben Sie genug Hintergrund Informationen &uuml;ber
- die Ports-Sammlung und Sie k&ouml;nnen Ihren ersten Port
- installieren. Es gibt dazu zwei M&ouml;glichkeiten, beide
- werden im Folgenden erl&auml;utert.</para>
-
- <para>Bevor Sie damit beginnen, m&uuml;ssen Sie sich nat&uuml;rlich
- einen Port zum Installieren aussuchen. Sie k&ouml;nnen
- dazu mehrere Wege gehen, als einfachste Methode gibt es die
- <ulink url="http://www.freebsd.org/ports/">Liste der Port auf
- dem FreeBSD Web-Server</ulink>. Sie k&ouml;nnen dort Suchen
- oder in der Liste schm&ouml;kern. Jeder Port enth&auml;lt
- au&szlig;erdem eine Beschreibung, so da&szlig; Sie sich vor der
- Entscheidung, welchen Port Sie installieren wollen, &uuml;ber den Port
- informieren k&ouml;nnen.</para>
-
- <para>Eine andere Methode bietet das Kommando <command>whereis</command>.
- Um <command>whereis</command> zu benutzen, geben Sie einfach
- <quote><command>whereis &lt;Programm, da&szlig; Sie
- installieren m&ouml;chten&gt;</command></quote> ein. Wenn es auf
- Ihrem System gefunden wird, wird das wie im folgenden Beispiel anzeigt:
- </para>
-
- <screen>&prompt.root; <userinput>whereis xchat</userinput>
-xchat: /usr/ports/irc/xchat
-&prompt.root;</screen>
-
- <para>Dies sagt uns, da&szlig; xchat (ein IRC-Client) im
- Verzeichnis <filename>/usr/ports/irc/xchat</filename>
- gefunden werden kann.</para>
-
- <para>Ein noch anderer Weg, einen bestimmten Port zu finden ist,
- die eingebaute Suchfunktion der Ports-Sammlung zu benutzen.
- Dazu m&uuml;ssen Sie im Verzeichnis <filename>/usr/ports</filename>
- sein. Darin geben Sie ein
- <command>make search key=Anwendungsname</command> worin
- <quote>Anwendungsname</quote> der Name der von Ihnen gesuchten
- Anwendung ist. Wenn Sie zum Beispiel nach xchat suchten:</para>
-
- <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
-&prompt.root; <userinput>make search key=xchat</userinput>
-Port: xchat-1.3.8
-Path: /usr/ports/irc/xchat
-Info: An X11 IRC client using the GTK+ toolkit, and optionally, GNOME
-Maint: jim@FreeBSD.org
-Index: irc
-B-deps: XFree86-3.3.5 bzip2-0.9.5d gettext-0.10.35 giflib-4.1.0 glib-1.2.6 gmake-3.77 gtk-1.2.6
- imlib-1.9.8 jpeg-6b png-1.0.3 tiff-3.5.1
-R-deps: XFree86-3.3.5 gettext-0.10.35 giflib-4.1.0 glib-1.2.6 gtk-1.2.6 imlib-1.9.8 jpeg-6b
- png-1.0.3 tiff-3.5.1</screen>
-
- <para>Der Teil der Ausgabe der Sie interessiert ist die Zeile, die
- mit <quote>Path:</quote> beginnt, weil sie Ihnen sagt, wo der Port
- zu finden ist. Die anderen Informationen werden zum Installieren
- des Ports nicht direkt ben&ouml;tigt, Sie brauchen sich darum
- jetzt nicht weiter zu k&uuml;mmern.</para>
-
- <note>
- <para>Zum Installieren von Ports m&uuml;ssen Sie als Benutzer
- <username>root</username> angemeldet sein.</para>
- </note>
-
- <para>Jetzt, wo Sie den gew&uuml;nschten Port gefunden haben, kann es
- mit der eigentlichen Installation losgehen.</para>
-
- <sect3 id="ports-cd">
- <title>Installation von einer CDROM</title>
-
- <para>Wie Sie schon vermuten, geht dieser Abschnitt davon aus,
- da&szlig; Sie eine FreeBSD-CDROM Zusammenstellung haben.
- Wenn nicht, k&ouml;nnen Sie eine bei <ulink
- url="http://www.freebsdmall.com/">FreeBSD Mall</ulink>
- bestellen.</para>
-
- <para>Angenommen Ihre FreeBSD-CDROM ist im Laufwerk und nach
- <filename>/cdrom</filename> eingebunden (und der Mount Punkt
- <emphasis>mu&szlig;</emphasis> das Verzeichnis
- <filename>/cdrom</filename> sein), kann es mit dem Installieren
- von Port losgehen. Zu Beginn gehen Sie in das Verzeichnis des
- Portes, welchen Sie installieren m&ouml;chten:</para>
-
- <screen>&prompt.root; <userinput>cd /usr/ports/irc/xchat</userinput></screen>
-
- <para>Im Verzeichnis xchat kann man das Ger&uuml;st erkennen. Der
- n&auml;chste Schritt ist das &Uuml;bersetzen (auch Bauen genannt)
- des Portes. Dies wird durch Eingabe von <command>make</command>
- getan. Haben Sie das eingegeben, so werden Sie etwas lesen
- wie:</para>
-
-
- <screen>&prompt.root; <userinput>make</userinput>
-&gt;&gt; xchat-1.3.8.tar.bz2 doesn't seem to exist on this system.
-&gt;&gt; Attempting to fetch from file:/cdrom/ports/distfiles/.
-===&gt; Extracting for xchat-1.3.8
-&gt;&gt; Checksum OK for xchat-1.3.8.tar.bz2.
-===&gt; xchat-1.3.8 depends on executable: bzip2 - found
-===&gt; xchat-1.3.8 depends on executable: gmake - found
-===&gt; xchat-1.3.8 depends on shared library: gtk12.2 - found
-===&gt; xchat-1.3.8 depends on shared library: Imlib.5 - found
-===&gt; xchat-1.3.8 depends on shared library: X11.6 - found
-===&gt; Patching for xchat-1.3.8
-===&gt; Applying FreeBSD patches for xchat-1.3.8
-===&gt; Configuring for xchat-1.3.8
-...
-[configure-Ausgabe weggelassen]
-...
-===&gt; Building for xchat-1.3.8
-...
-[Ausgabe der &Uuml;bersetzung weggelassen]
-...
-&prompt.root;</screen>
-
- <para>Ist die &Uuml;bersetzungsprozedur beendet, sind Sie wieder
- in der Kommandozeile und der n&auml;chste Schritt ist das
- Installieren. Dazu h&auml;ngen Sie einfach ein Wort an das
- <command>make</command>-Kommando, und dieses Wort ist
- <command>install</command>:</para>
-
- <screen>&prompt.root; <userinput>make install</userinput>
-===&gt; Installing for xchat-1.3.8
-===&gt; xchat-1.3.8 depends on shared library: gtk12.2 - found
-===&gt; xchat-1.3.8 depends on shared library: Imlib.5 - found
-===&gt; xchat-1.3.8 depends on shared library: X11.6 - found
-...
-[Ausgabe der Installation weggelassen]
-...
-===&gt; Generating temporary packing list
-===&gt; Installing xchat docs in /usr/X11R6/share/doc/xchat
-===&gt; Registering installation for xchat-1.3.8
-&prompt.root;</screen>
-
- <para>Wenn Sie wieder den Prompt haben, sollte Sie in der Lage
- sein, die gerade in stallierte Anwendung laufen zu lassen.</para>
-
- <note>
- <para>Sie k&ouml;nnen einen Schritt sparen, wenn Sie gleich
- <command>make install</command> anstatt von
- <command>make</command> und dem anschlie&szlig;enden
- <command>make install</command> eingeben.</para>
- </note>
-
- <note>
- <para>Beachten Sie bitte, da&szlig; die Lizenzen einiger Ports
- die Einbeziehung auf der CDROM verbieten. Das k&ouml;nnte
- aufgrund verschiedenster Gr&uuml;nde der Fall sein, beispielsweise
- weil man sich vor dem Herunterladen registrieren lassen
- mu&szlig; oder eine Weiterverteilung verboten ist u.s.w.
- W&uuml;nschen Sie einen Port zu installieren, der nicht auf
- der CDROM enthalten ist, so m&uuml;ssen Sie online gehen und
- mit Hilfe <link linkend="ports-inet"> des n&auml;chsten
- Abschnitts </link> den Port installieren.</para>
- </note>
- </sect3>
-
- <sect3 id="ports-inet">
- <title>Port vom Internet installieren</title>
-
- <para>Dieser Abschnitt setzt voraus, da&szlig; Sie eine Verbindung
- mit dem Internet haben. Haben Sie dies nicht, m&uuml;ssen Sie
- eine <link linkend="ports-cd">CDROM Installation</link>
- durchf&uuml;hren.</para>
-
- <para>Das Installieren eines Ports vom Internet wird genau so
- durchgef&uuml;hrt wie das Installieren von CDROM. Der einzige
- Unterschied zwischen beiden ist, da&szlig; der Quellcode der
- Anwendung vom Internet heruntergeladen und nicht von der CDROM
- genommen wird.</para>
-
- <para>Die durchgef&uuml;hrten Schritte sind identisch:</para>
-
- <screen>&prompt.root; <userinput>make install</userinput>
-&gt;&gt; xchat-1.3.8.tar.bz2 doesn't seem to exist on this system.
-&gt;&gt; Attempting to fetch from http://xchat.org/files/v1.3/.
-Receiving xchat-1.3.8.tar.bz2 (305543 bytes): 100%
-305543 bytes transferred in 2.9 seconds (102.81 Kbytes/s)
-===&gt; Extracting for xchat-1.3.8
-&gt;&gt; Checksum OK for xchat-1.3.8.tar.bz2.
-===&gt; xchat-1.3.8 depends on executable: bzip2 - found
-===&gt; xchat-1.3.8 depends on executable: gmake - found
-===&gt; xchat-1.3.8 depends on shared library: gtk12.2 - found
-===&gt; xchat-1.3.8 depends on shared library: Imlib.5 - found
-===&gt; xchat-1.3.8 depends on shared library: X11.6 - found
-===&gt; Patching for xchat-1.3.8
-===&gt; Applying FreeBSD patches for xchat-1.3.8
-===&gt; Configuring for xchat-1.3.8
-...
-[configure-Ausgabe weggelassen]
-...
-===&gt; Building for xchat-1.3.8
-...
-[Ausgabe der &Uuml;bersetzung weggelassen]
-...
-===&gt; Installing for xchat-1.3.8
-===&gt; xchat-1.3.8 depends on shared library: gtk12.2 - found
-===&gt; xchat-1.3.8 depends on shared library: Imlib.5 - found
-===&gt; xchat-1.3.8 depends on shared library: X11.6 - found
-...
-[Ausgabe der Installation weggelassen]
-...
-===&gt; Generating temporary packing list
-===&gt; Installing xchat docs in /usr/X11R6/share/doc/xchat
-===&gt; Registering installation for xchat-1.3.8
-&prompt.root;</screen>
-
- <para>Wie Sie sehen k&ouml;nnen, besteht der einzige Unterschied in
- der Zeile, die Ihnen sagt, woher das System den Quellcode
- herholt.</para>
-
- <para>Obiges erkl&auml;rte Ihnen, wie Sie Ports auf Ihrem Computer
- installieren k&ouml;nnen. Hiernach lernen Sie, wie Sie einen
- Port wieder von Ihrem System l&ouml;schen.</para>
- </sect3>
- </sect2>
-
- <sect2 id="ports-removing">
- <title>Entfernen installierter Ports</title>
-
- <para>Da Sie nun wissen, wie man einen Port installiert, wollen Sie
- sicher auch wissen, wie man einen Port deinstalliert, f&uuml;r den
- Fall, da&szlig; Sie versehentlich einen Falschen installiert haben.
- Die n&auml;chsten Abschitte decken genau dieses Thema ab.</para>
-
- <para>Nun wollen wir mal unser vorheriges Beispiel wieder
- l&ouml;schen (f&uuml;r alle die nicht aufgepa&szlig;t haben, da&szlig;
- war xchat). Wie beim Installieren geht man zuerst in das
- Verzeichnis des Portes, wie Sie sich erinnern werden war das
- <filename>/usr/ports/irc/xchat</filename>. Danach ist man
- in der Lage den Port zu deinstallieren. Dies wird mit dem
- Kommando <command>make deinstall</command> getan (erscheint
- sinnvoll, oder?):</para>
-
- <screen>&prompt.root; <userinput>cd /usr/ports/irc/xchat</userinput>
-&prompt.root; <userinput>make deinstall</userinput>
-===&gt; Deinstalling for xchat-1.3.8
-&prompt.root;</screen>
-
- <para>Das war leicht. Sie haben jetzt die F&auml;higkeit, xchat
- von Ihrem System zu entfernen. M&ouml;chten Sie den Port doch
- wieder neu installieren, geben Sie
- <command>make reinstall</command> im Verzeichnis
- <filename>/usr/ports/irc/xchat</filename> ein.</para>
- </sect2>
- </sect1>
-
- <sect1 id="ports-trouble">
- <title>Fehlersuche und -behebung</title>
-
- <para>Die folgenden Zeilen beschreiben einige einfache
- Fehlerbehebungsm&ouml;glichkeiten beim Benutzen der Ports-Sammlung
- und ein paar Fehlerbehandlungen, falls ein <link
- linkend="ports-broken">Port kaputt</link> ist.</para>
-
- <sect2 id="ports-questions">
- <title>Einige Fragen und Antworten</title>
-
- <qandaset>
- <qandaentry>
- <question>
- <para>Ich dachte hierbei ging es um Modems??!</para>
- </question>
-
- <answer>
- <para>Ah, Sie m&uuml;ssen an die serielle Schnittstelle auf der
- R&uuml;ckseite Ihres Computers gedacht haben (engl. port). Wir
- benutzen hier <quote>Port</quote> als Ergebnis des
- <quote>Portierens</quote> einer Anwendung von einer UNIX-Variante
- zu einer anderen.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Ich dachte man soll Packete (packages) benutzen, um
- zus&auml;tzliche Anwendungen zu installieren?</para>
- </question>
-
- <answer>
- <para>Ja, das ist gew&ouml;hnlich der schnellste und einfachste
- Weg.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Warum dann mit den Ports herumplagen?</para>
- </question>
-
- <answer>
- <para>Aus verschiedenen Gr&uuml;nden:</para>
-
- <orderedlist>
- <listitem>
- <para>Die Lizenz-Bestimmungen einiger Software verbietet
- Verteilung in bin&auml;rer Form. Diese mu&szlig; als
- Quellcode verteilt werden.</para>
- </listitem>
-
- <listitem>
- <para>Einige Leute vertrauen bereits kompilierter Software
- nicht. Mit dem Quellcode haben sie zumindest (in der
- Theorie) die M&ouml;glichkeit, sich den Code anzusehen und
- nach potentiellen Problemen f&uuml;r sich zu suchen.</para>
- </listitem>
-
- <listitem>
- <para>Haben Sie eigene Anpassungen, so ben&ouml;tigen Sie den
- Quellcode, um diese vornehmen zu k&ouml;nnen.</para>
- </listitem>
-
- <listitem>
- <para>Sie k&ouml;nnten andere Ansichten dar&uuml;ber haben,
- wie eine Anwendung &uuml;bersetzt werden soll, als die Person
- welche das Package erstellt hat&mdash; einige Leute haben
- strenge Ansichten dr&uuml;ber, welche Optimierung benutzt,
- ob eine Debug-Version erstellt oder ob anschlie&szlig;end
- <command>strip</command> benutzt werden soll und so
- weiter.</para>
- </listitem>
-
- <listitem>
- <para>Packages werden normalerweise mit recht konservativen
- Einstellungen erstellt. Wenn ein Port spezielle Optionen
- f&uuml;r einen speziellen Prozessor oder eine besondere
- Karte in Ihrem Rechner hat, k&ouml;nnen Sie diese immer
- benutzen und die Ersteller der Packages m&uuml;ssen nicht
- sehr viele verschiedene davon bereitstellen.</para>
-
- <para>Die verbreiteste Ausnahme von dieser Regel ist das
- Papierformat. Unterst&uuml;tzt ein Port von Haus aus
- verschieden Formate, stellen wir auch verschiedene
- packages bereit, eins pro Papierformat.</para>
- </listitem>
-
- <listitem>
- <para>Manche Menschen haben gerne Quellcode rumliegen, um
- darin zu lesen, wenn ihnen langweilig ist, drin rumzuhacken,
- sich etwas auszuleihen (nat&uuml;rlich, wenn es die Lizenz
- erlaubt) und so weiter.</para>
- </listitem>
-
- <listitem>
- <para>Hast Du keinen Quellcode, ist es keine Software!
- <!-- smiley -->;-)</para>
- </listitem>
- </orderedlist>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para id="ports-patch">Was ist ein Patch?</para>
- </question>
-
- <answer>
- <para>Ein Patch ist eine kleine Datei, die beschreibt, wie man
- von einer Version einer Datei zu einer anderen kommt. Sie
- enth&auml;lt reinen Text und sagt im Prinzip Dinge wie
- <quote>l&ouml;sche Zeile 23</quote>,
- <quote>f&uuml;ge diese zwei Zeilen hinter Zeile 468an </quote>,
- oder <quote>&auml;ndere Zeile 197 hierzu</quote>. Sie sind
- auch bekannt als diffs, weil sie mit der Anwendung
- <application>diff</application> erstellt werden.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para id="ports-tarball">Worum gehts eigentlich bei diesen
- tarballs?</para>
- </question>
-
- <answer>
- <para>Das ist eine Datei mit der Endung <filename>.tar</filename>
- oder als Varianten mit <filename>.tar.gz</filename>,
- <filename>.tar.Z</filename>, <filename>.tar.bz2</filename>,
- oder auch <filename>.tgz</filename>.</para>
-
- <para>Vereinfacht ist das ein Verzeichnisbaum, welcher in eine
- einzelne Datei (<filename>.tar</filename>) archiviert und
- optional gepackt (<filename>.gz</filename>) wurde. Diese
- Technik wurde urspr&uuml;nglich f&uuml;r
- <emphasis>T</emphasis>ape <emphasis>AR</emphasis>chives
- benutzt (daher der Name <command>tar</command>), aber stellt
- heute einen weit verbreiteten Weg da, im Internet Quellcode
- zu verbreiten und zu verteilen.</para>
-
- <para>Sie k&ouml;nnen selber hineinsehen, was f&uuml;r Dateien
- darin sind oder diese auspacken, indem Sie das UNIX-Programm
- <application>tar</application> benutzen. Dies ist auch bei
- FreeBSD dabei. Das s&auml;he in etwa so aus:</para>
-
- <screen>&prompt.user; <userinput>tar tvzf foobar.tar.gz</userinput>
-&prompt.user; <userinput>tar xzvf foobar.tar.gz</userinput>
-&prompt.user; <userinput>tar tvf foobar.tar</userinput>
-&prompt.user; <userinput>tar xvf foobar.tar</userinput></screen>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para id="ports-checksum">Eine Pr&uuml;fsumme?</para>
- </question>
-
- <answer>
- <para>Das ist eine Zahl, die dadurch generiert wird, indem man
- die ganzen Daten einer Datei aufaddiert. &Auml;ndert sich ein
- Zeichen in dieser Datei, ist die Pr&uuml;fsumme nicht mehr die
- gleiche und ein einfacher Vergleich erm&ouml;glicht das
- Erkennen des Unterschiedes.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Ich tat, was ihr zum &Uuml;bersetzen von Ports von der
- CDROM geschrieben habt und es funktionierte auch prima, bis ich
- zum Port kermit kam.</para>
-
- <screen>&prompt.root; <userinput>make install</userinput>
-&gt;&gt; cku190.tar.gz doesn't seem to exist on this system.
-&gt;&gt; Attempting to fetch from ftp://kermit.columbia.edu/kermit/archives/.</screen>
-
- <para>Warum kann die Datei nicht gefunden werden? Habe ich eine kaputte
- CDROM?</para>
- </question>
-
- <answer>
- <para>Wie im Abschnitt <link linkend="ports-cd">Installation von
- CDROM</link> erl&auml;utert, d&uuml;rfen einige Ports wegen
- Lizenz-Beschr&auml;nkungen nicht auf CDROM ver&ouml;ffentlicht
- werden. Kermit ist ein solches Beispiel. Die Lizenz-Bestimmungen
- verbieten uns das Brennen des tarballs auf CDROM, leider
- m&uuml;ssen Sie es sich von Hand aus dem Netz
- Herunterladen&mdash;sorry!</para>
-
- <para>Der Grund f&uuml;r die ganzen Fehlermeldungen liegt darin,
- da&szlig; Sie zu diesem Zeitpunkt nicht mit dem Internet verbunden
- waren. Haben Sie den tarball von einer der MASTER_SITES
- (aufgef&uuml;hrt im Makefile) gezogen, k&ouml;nnen Sie die
- Installation erneut starten.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Das habe ich getan, aber als ich ihn ins Verzeichnis
- <filename>/usr/ports/distfiles</filename> legen wollte, erhielt
- ich eine Fehlermeldung bez&uuml;glich der Zugriffsrechte.</para>
- </question>
-
- <answer>
- <para>Der Ports Mechanimus sucht den tarball in
- <filename>/usr/ports/distfiles</filename>, aber Sie konnten ihn
- dort nicht hinkopieren, da dieses Verzeichnis auf die CDROM
- zeigt, die man nur gelesen kann. Sie k&ouml;nnen eine andere
- Stelle angeben, indem Sie eingeben:</para>
-
- <screen>&prompt.root; <userinput>make DISTDIR=<replaceable>/wohin/Sie/es/legten</replaceable> install</userinput></screen>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Funktioniert das Konzept der Ports nur, wenn alles in
- <filename>/usr/ports</filename> abl&auml;uft? Mein
- Systemadministrator sagt, da&szlig; ich alles unter
- <filename>/u/people/guests/wurzburger</filename> haben
- mu&szlig;, aber das scheint nicht klappen.</para>
- </question>
-
- <answer>
- <para>Sie k&ouml;nnen die Variablen <makevar>PORTSDIR</makevar>
- und <makevar>PREFIX</makevar> benutzen, um dem Ports-System zu
- sagen, da&szlig; es andere Verzeichnisse nutzen soll. Zum
- Beispiel w&uuml;rde,</para>
-
- <screen>&prompt.root; <userinput>make PORTSDIR=/u/people/guests/wurzburger/ports install</userinput></screen>
-
- <para>den Port in
- <filename>/u/people/guests/wurzburger/ports</filename>
- kompilieren und alles unter <filename>/usr/local</filename>
- installieren.</para>
-
- <screen>&prompt.root; <userinput>make PREFIX=/u/people/guests/wurzburger/local install</userinput></screen>
-
- <para>kompiliert in <filename>/usr/ports</filename> und
- installiert ihn in
- <filename>/u/people/guests/wurzburger/local</filename>.</para>
-
- <para>Und nat&uuml;rlich</para>
-
- <screen>&prompt.root; <userinput>make PORTSDIR=../ports PREFIX=../local install</userinput></screen>
-
- <para>kombiniert die beiden Sachen. (Es ist aber ein wenig lang,
- um es hier komplett aufzuschreiben. Sie sollten aber die
- zugrunde liegende Idee erkennen.)</para>
-
- <para>Wenn Sie keine Lust haben, dies jedesmal einzutippen,
- sollten Sie diese Variablen als Umgebungsvariablen setzen.
- Lesen Sie die Man-Page Ihre Shell, um zu erfahren, wie das
- anstellt.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Ich habe keine FreeBSD CDROM, w&uuml;rde aber gerne die
- tarballs auf meinem Rechner liegen haben, damit ich nicht
- jedesmal auf den Downlaod warten mu&szlig;, wenn ich mal einen
- Port installieren will. Gibt es einen Weg, alle auf einmal
- zu holen?</para>
- </question>
-
- <answer>
- <para>Um jeden einzelnen tarball f&uuml;r die Ports-Sammlung zu
- holen geben Sie ein:</para>
-
- <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
-&prompt.root; <userinput>make fetch</userinput></screen>
-
- <para>F&uuml;r alle tarballs eines Ports-Verzeichnis:</para>
-
- <screen>&prompt.root; <userinput>cd /usr/ports/<replaceable>Verzeichnis</replaceable></userinput>
-&prompt.root; <userinput>make fetch</userinput></screen>
-
- <para>und f&uuml;r nur einen Port&mdash;gut, das haben Sie sicher
- schon erraten.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Ich wei&szlig;, das es wohl schneller geht, wenn ich die
- tarballs von einem FreeBSD Mirror in der N&auml;he hole. Kann
- ich sagen, da&szlig; andere als in MASTER_SITES angegebene
- Server genommen werden soll?</para>
- </question>
-
- <answer>
- <para>Ja. Zum Beispiel, wenn <hostid
- role="fqdn">ftp.FreeBSD.org</hostid> bei Ihnen n&auml;her dran
- ist, als der in <makevar>MASTER_SITES</makevar> angegebene,
- machen Sie das wie folgt:</para>
-
- <screen>&prompt.root; <userinput>cd /usr/ports/<replaceable>directory</replaceable></userinput>
-&prompt.root; <userinput>make MASTER_SITE_OVERRIDE= \
-ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch</userinput></screen>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Ich w&uuml;rde gern vorher wissen, welche Dateien
- <command>make</command> holen wird, bevor es das versucht.</para>
- </question>
-
- <answer>
- <para><command>make fetch-list</command> gibt aus, welche Dateien
- f&uuml;r den Port ben&ouml;tigt werden.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Gibt es einen Weg einen Port am Kompilieren zu hindern? Ich
- m&ouml;chter gern vor der Installation etwas im Quellcode hacken.
- Es ist aber etwas nervig, immer aufzupassen und im richtigen
- Moment mit Control-C abzubrechen.</para>
- </question>
-
- <answer>
- <para>Die Eingabe von <command>make extract</command> erreicht,
- da&szlig; der Port Quellcode nur geholt und entpackt wird.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Ich versuche einen eigenen Port zu erstellen und will,
- da&szlig; der Port vor dem &Uuml;bersetzen anh&auml;lt, damit
- ich eine Chance habe zu sehen, ob meine Patches sauber
- funktionieren. Gibt es etwas wie <command>make
- extract</command> f&uuml;r Patches?</para>
- </question>
-
- <answer>
- <para>Klar, <command>make patch</command> ist alles was Sie
- w&uuml;nschen. Sie werden wahrscheinlich die Variable
- <makevar>PATCH_DEBUG</makevar> auch recht n&uuml;tzlich finden.
- Ach ja, und vielen Dank f&uuml;r Ihre Bem&uuml;hungen!</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Stimmt es, da&szlig; einige Compiler Fehler machen? Wie
- kann ich sicher gehen, da&szlig; ich mit den richtigen
- Einstellungen &uuml;bersetze?</para>
- </question>
-
- <answer>
- <para>Ja, in der Version 2.6.3 des <command>gcc</command> (diese
- Version ist bei FreeBSD 2.1.0 und 2.1.5 dabei) kann die Option
- <option>-O2</option> fehlerhafte Ergebnisse liefern, sofern man
- nicht auch die Option <option>-fno-strength-reduce</option>
- benutzt. (Die meisten Ports benutzen <option>-O2</option>
- nicht). Sie <emphasis>sollten</emphasis> die Compiler Optionen
- etwa wie folgt spezifieren k&ouml;nnen:</para>
-
- <screen>&prompt.root; <userinput>make CFLAGS='-O2 -fno-strength-reduce' install</userinput></screen>
-
- <para>oder durch editieren von <filename>/etc/make.conf</filename>,
- alleding beachten das nicht alle Ports. Der sicherste Weg ist,
- nach einem <command>make configure</command> ins Verzeichnis
- mit dem Quellcode zu gehen und dort die Makefiles von Hand zu
- untersuchen. Das kann aber sehr m&uuml;hselig werden, da es
- oft sehr viele Unterverzeichnisse mit eigenen Makefiles geben
- kann.</para>
-
- <para>Die bei FreeBSD voreingestellten Compiler Optionen sind
- recht konservativ, so sollten Sie eigentlich keine Probleme
- bekommen, wenn Sie diese nicht ver&auml;ndert haben.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Das sind aber ganz sch&ouml;n viele Ports und es ist nicht
- leicht den einen zu finden, den ich gerade m&ouml;chte. Gibt es
- eine Liste der erh&auml;ltlichen Ports?</para>
- </question>
-
- <answer>
- <para>Schauen Sie in die Datei <filename>INDEX</filename> im
- Verzeichnis <filename>/usr/ports</filename>. Sie k&ouml;nnen
- auch die Ports-Sammlung nach einem Stichwort durchsuchen.
- Wollen Sie zum Beispiel alle Ports finden, die mit der
- Programmiersprache LISP zu tun haben, geben Sie ein:</para>
-
- <screen>&prompt.user; <userinput>cd /usr/ports</userinput>
-&prompt.user; <userinput>make search key=lisp</userinput></screen>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Als ich den Port <literal>bla</literal> installieren
- wollte, h&ouml;rt das System auf einmal mit dem Kompilieren auf
- und fing an, den Port <literal>s&uuml;lz</literal> zu
- erstellen. Was ist hier los?</para>
- </question>
-
- <answer>
- <para>Der Port <literal>bla</literal> braucht etwas, was mit dem
- Port <literal>s&uuml;lz</literal> mitkommt &mdash; beispielsweise,
- wenn <literal>bla</literal> Grafik benutzt wird und der Port
- <literal>s&uuml;lz</literal> k&ouml;nnte dann eine Bibliothek mit
- n&uuml;tzlichen grafischen Routinen enthalten. Oder
- <literal>s&uuml;lz</literal> k&ouml;nnte ein Werkzeug sein, das zum
- &Uuml;bersetzen des Ports <literal>bla</literal> notwendig
- ist.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para id="ports-remove"> Ich habe aus der Ports-Sammlung die
- Anwendung <literal>grizzle</literal> installiert und nun
- festgestellt, da&szlig; es reine Verschwendung von Plattenplatz
- ist. Ich will ihn wieder l&ouml;schen, wei&szlig; aber nicht
- wohin der Port seine Dateien installiert hat. Tips?</para>
- </question>
-
- <answer>
- <para>Alles kein Problem, machen Sie nur:</para>
-
- <screen>&prompt.root; <userinput>pkg_delete grizzle-6.5</userinput></screen>
-
- <para>Sie k&ouml;nnen alternativ auch eingeben:</para>
-
- <screen>&prompt.root; <userinput>cd <replaceable>/usr/ports/somewhere/grizzle</replaceable></userinput>
-&prompt.root; <userinput>make deinstall</userinput></screen>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Moment, man mu&szlig; die Versionsnummer wissen, um das
- Kommando benutzen zu k&ouml;nnen. Es wird nicht wirklich
- erwartet, da&szlig; ich mich daran noch erinner, oder??</para>
- </question>
-
- <answer>
- <para>Nein, Sie finden diese Nummer durch folgende Eingabe heraus:</para>
-
- <screen>&prompt.root; <userinput>pkg_info -a | grep grizzle</userinput>
-Information for grizzle-6.5:
-grizzle-6.5 - the combined piano tutorial, LOGO interpreter and shoot 'em up
-arcade game.</screen>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Apropos Plattenplatz, die Ports-Sammlung scheint recht viel
- Platz einzunehmen. Ist es gef&auml;hrlich dahin zu gehen und
- Sachen zu l&ouml;schen?</para>
- </question>
-
- <answer>
- <para>Nun, wenn Sie Anwendungen installiert haben und sicher sind,
- da&szlig; Sie den Quellcode nicht ben&ouml;tigen, gibt es
- keinen Grund diesen herumliegen zu haben. Der beste Weg zum
- Aufr&auml;umen ist:</para>
-
- <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
-&prompt.root; <userinput>make clean</userinput></screen>
-
- <para>Das geht durch alle Ports-Verzeichnisse und l&ouml;scht
- f&uuml;r jeden Port alles bis auf das Ger&uuml;st.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Das habe ich probiert, aber da liegen immer noch diese
- tarballs (oder wie die genannt werden) im Verzeichnis
- <filename>distfiles</filename> herum. Darf ich die auch
- l&ouml;schen?</para>
- </question>
-
- <answer>
- <para>Ja, wenn Sie mit denen fertig sind, konnen die auch
- verschwinden. Man kann sie von Hand l&ouml;schen das
- Kommando <command>make distclean</command> benutzen.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Ich finde es toll, tierisch viele Anwendungen zu haben und
- damit rumzuspielen. Gibt es einen Weg alle Ports auf einmal
- zu installieren?</para>
- </question>
-
- <answer>
- <para>Machen Sie einfach:</para>
-
- <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
-&prompt.root; <userinput>make install</userinput></screen>
-
- <para>Vorsicht: Einige Ports k&ouml;nnten Dateien mit dem
- gleichen Namen installieren. Wenn man zwei grafische Ports
- installiert und beide eine Datei
- <filename>/usr/local/bin/plot</filename> anlegen, haben Sie
- ein Problem.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Okay, das habe ich gemacht und ich dachte, da&szlig; das
- sicherlich ziemlich lange dauert, ging zu Bett. Als ich heute
- morgen zum Computer kam, waren erst dreieinhalb Ports
- installiert. Hat da etwas nicht geklappt?</para>
- </question>
-
- <answer>
- <para>Nein, das Problem ist, da&szlig; es Ports gibt, die Ihnen
- Fragen stellen, auf die wir die Antworten nicht f&uuml;r Sie
- geben konnten (z.B. <quote>Drucken Sie auf Papier im A4 oder US
- letter Format?</quote>). In solchen F&auml;llen mu&szlig;
- jemand da sein und die Fragen beantworten.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Ich m&ouml;chte aber nicht wirklich einen ganzen Tag damit
- verbringen, auf den Monitor zu starren. Irgendeine bessere
- Idee?</para>
- </question>
-
- <answer>
- <para>Klar, bevor Sie ins Bett/zur Arbeit/in den Park gehen,
- geben Sie ein:</para>
-
- <screen>&prompt.root <userinput>cd /usr/ports</userinput>
-&prompt.root; <userinput>make -DBATCH install</userinput></screen>
-
- <para>Das installiert Ihnen alle Ports, die
- <emphasis>keine</emphasis> Eingaben des Benutzers erfordern.
- Wenn Sie dann zur&uuml;ck sind, geben Sie ein:</para>
-
- <screen>&prompt.root; <userinput>cd /usr/ports</userinput>
-&prompt.root; <userinput>make -DIS_INTERACTIVE install</userinput></screen>
-
- <para>um die Aufgabe zu beenden.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Auf der Arbeit benutzen wir die Anwendung
- <literal>frobble</literal>, das in der Ports-Sammlung ist. Wir
- haben das aber etwas auf unsere Bed&uuml;rfnisse angepa&szlig;t.
- K&ouml;nnen wir irgendwie eigene packages erstellen, so
- da&szlig; wir die Anwendung auf unseren Rechnern leichter
- verteilen k&ouml;nnen?</para>
- </question>
-
- <answer>
- <para>Kein Problem. Angenommen Sie wissen, wie Sie f&uuml;r Ihre
- Anpassungen Patches erzeugen:</para>
-
- <screen>&prompt.root; <userinput>cd <replaceable>/usr/ports/somewhere/frobble</replaceable></userinput>
-&prompt.root; <userinput>make extract</userinput>
-&prompt.root; <userinput>cd work/frobble-2.8</userinput>
-[Ihre patche einspielen]
-&prompt.root; <userinput>cd ../..</userinput>
-&prompt.root; <userinput>make package</userinput></screen>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Diese Geschichte mit den Ports ist wirklich clever. Ich
- habe keine Ahnung, wie ihr das hinbekommen habt. Was ist das
- Geheimnis dahinter?</para>
- </question>
-
- <answer>
- <para>Keine Geheimnisse. Sehen Sie einfach in die Dateien
- <filename>bsd.port.mk</filename> und
- <filename>bsd.port.subdir.mk</filename> in dem
- <ulink url="file://localhost/usr/ports/Mk/">makefiles
- Verzeichnis</ulink> auf Ihrem Rechner an.</para>
-
- <para>(Lesern mit einer Aversion gegen komplizierte Shell-scripts
- wird geraten, diesen Link nicht zu verfolgen...)</para>
- </answer>
- </qandaentry>
- </qandaset>
- </sect2>
-
- <sect2 id="ports-broken">
- <title>Hilfe! Dieser Port ist kaputt!</title>
-
- <para>Stolpern Sie mal &uuml;ber einen Port, der bei Ihnen nicht
- funktioniert, k&ouml;nnten Sie zum Beispiel folgendes tun:</para>
-
- <orderedlist>
- <listitem>
- <para>Reparieren Sie ihn! Der Abschnitt
- <link linkend="porting"><quote>Wie erstelle ich einen
- Port</quote></link> sollte Ihnen dabei helfen.</para>
- </listitem>
-
- <listitem>
- <para>Rummeckern&mdash;<emphasis>nur mittels E-Mail!</emphasis>
- Senden Sie zuerst eine E-Mail an den Betreuer des Ports. Geben
- Sie dazu <command>make maintainer</command> ein oder lesen das
- <filename>Makefile</filename> im Verzeichnis des Ports, um an
- die E-Mail-Adresse zu kommen. Vergessen Sie nicht den Namen und
- die Version des Ports (schicken Sie die Zeile mit
- <literal>$FreeBSD:</literal> aus dem <filename>Makefile</filename>)
- und die Ausgabe bis zur Fehlermeldung mitzuschicken. Erhalten
- Sie vom Betreuer keine Resonanz, k&ouml;nnen Sie auch das
- <command>send-pr</command> Kommando benutzen, um einen
- Fehler-Report einzusenden.</para>
- </listitem>
-
- <listitem>
- <para>Vergessen Sie es. Das ist der einfachste Weg&mdash; nur
- sehr wenige Ports kann man als <quote>unverzichtbar</quote>
- klassifizieren. Au&szlig;erdem gibt eine gro&szlig;e
- Wahrscheinlichkeit, da&szlig; der Fehler in der n&auml;chsten
- Version behoben ist, wenn der Port aktualisiert wurde.</para>
- </listitem>
-
- <listitem>
- <para>Holen Sie sich das Package von einem FTP-Server in Ihrer
- N&auml;he. Die <quote>Basis</quote> Sammlung aller packages
- liegt auf <hostid role="fqdn">ftp.de.FreeBSD.org</hostid> im
- Verzeichnis <ulink
- URL="ftp://ftp.de.FreeBSD.org/pub/FreeBSD/ports/packages/">packages</ulink>.
- Aber versuchen Sie <emphasis>zuerst</emphasis> einen Mirror in
- Ihrer N&auml;he! Die Methode mit den Packages geht um einiges
- schneller. Benutzen Sie das Programm &man.pkg.add.1;, um
- Packages auf Ihrem Rechner zu installieren.</para>
- </listitem>
- </orderedlist>
- </sect2>
- </sect1>
-
- <sect1 id="porting">
- <title>Weitergehende Themen</title>
-
- <para>Dieser Abschnitt wurde ausgelagert und zu einem eigenst&auml;ndigen
- Handbuch, dem
- <ulink url="../porters-handbook/index.html">Porters-Handbuch</ulink>,
- Wenn Sie selber einen Port erstellen und einreichen
- wollen, lesen Sie bitte dieses Handbuch.</para>
- </sect1>
-</chapter>
-
-<!--
- Local Variables:
- mode: sgml
- sgml-declaration: "../chapter.decl"
- sgml-indent-data: t
- sgml-omittag: nil
- sgml-always-quote-attributes: t
- sgml-parent-document: ("../book.sgml" "part" "chapter")
- End:
--->
-
diff --git a/de_DE.ISO8859-1/share/sgml/bookinfo.ent b/de_DE.ISO8859-1/share/sgml/bookinfo.ent
deleted file mode 100644
index d6e567519c..0000000000
--- a/de_DE.ISO8859-1/share/sgml/bookinfo.ent
+++ /dev/null
@@ -1,12 +0,0 @@
-<!--
- Querverweise auf andere Dateien können in einem DocBook BookInfo
- Element eingefügt werden.
-
- Entity Namen haben die Form "bookinfo.<element>", wobei <element> der
- Name des äußersten Elements in der Entity ist. Beispiele sind
- "bookinfo.legalnotice" und "bookinfo.preface".
-
- $FreeBSD$
--->
-
-<!ENTITY bookinfo.legalnotice SYSTEM "legalnotice.sgml">
diff --git a/de_DE.ISO8859-1/share/sgml/catalog b/de_DE.ISO8859-1/share/sgml/catalog
deleted file mode 100644
index 5ebe8768fc..0000000000
--- a/de_DE.ISO8859-1/share/sgml/catalog
+++ /dev/null
@@ -1,9 +0,0 @@
- -- ...................................................................... --
- -- FreeBSD SGML Public Identifiers ...................................... --
-
- -- $FreeBSD: doc/share/sgml/catalog,v 1.9 2000/07/08 16:31:28 phantom Exp $
- --
-
-PUBLIC "-//FreeBSD//DOCUMENT DocBook Stylesheet//EN"
- "freebsd.dsl"
-
diff --git a/de_DE.ISO8859-1/share/sgml/freebsd.dsl b/de_DE.ISO8859-1/share/sgml/freebsd.dsl
deleted file mode 100644
index 2536dfd538..0000000000
--- a/de_DE.ISO8859-1/share/sgml/freebsd.dsl
+++ /dev/null
@@ -1,30 +0,0 @@
-<!-- $FreeBSD: doc/de_DE.ISO_8859-1/share/sgml/freebsd.dsl,v 1.1 2000/06/09 12:26:38 alex Exp $ -->
-
-<!DOCTYPE style-sheet PUBLIC "-//James Clark//DTD DSSSL Style Sheet//EN" [
-<!ENTITY freebsd.dsl PUBLIC "-//FreeBSD//DOCUMENT DocBook Language Neutral Stylesheet//EN" CDATA DSSSL>
-]>
-
-<style-sheet>
- <style-specification use="docbook">
- <style-specification-body>
-
- <![ %output.html; [
- (define ($email-footer$)
- (make sequence
- (literal "For questions about FreeBSD, e-mail <")
- (make element gi: "a"
- attributes: (list (list "href" "mailto:questions@FreeBSD.org"))
- (literal "questions@FreeBSD.org"))
- (literal ">.")
- (make empty-element gi: "br")
- (literal "For questions about this documentation, e-mail <")
- (make element gi: "a"
- attributes: (list (list "href" "mailto:doc@FreeBSD.org"))
- (literal "doc@FreeBSD.org"))
- (literal ">.")))
- ]]>
- </style-specification-body>
- </style-specification>
-
- <external-specification id="docbook" document="freebsd.dsl">
-</style-sheet>
diff --git a/de_DE.ISO8859-1/share/sgml/legalnotice.sgml b/de_DE.ISO8859-1/share/sgml/legalnotice.sgml
deleted file mode 100644
index ecb8ba6cee..0000000000
--- a/de_DE.ISO8859-1/share/sgml/legalnotice.sgml
+++ /dev/null
@@ -1,44 +0,0 @@
-<!--
- Standard FreeBSD Documentation Project Legal Notice.
-
- $FreeBSD$
--->
-
-<legalnotice>
- <para>Redistribution and use in source (SGML DocBook) and 'compiled'
- forms (SGML, HTML, PDF, PostScript, RTF and so forth) with or without
- modification, are permitted provided that the following conditions are
- met:</para>
-
- <orderedlist>
- <listitem>
- <para>Redistributions of source code (SGML DocBook) must retain the
- above copyright notice, this list of conditions and the following
- disclaimer as the first lines of this file unmodified.</para>
- </listitem>
-
- <listitem>
- <para>Redistributions in compiled form (transformed to other DTDs,
- converted to PDF, PostScript, RTF and other formats) must
- reproduce the above copyright notice, this list of conditions and
- the following disclaimer in the documentation and/or other
- materials provided with the distribution.</para>
- </listitem>
- </orderedlist>
-
- <important>
- <para>THIS DOCUMENTATION IS PROVIDED BY THE FREEBSD DOCUMENTATION
- PROJECT "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
- BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
- FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL
- THE FREEBSD DOCUMENTATION PROJECT BE LIABLE FOR ANY DIRECT, INDIRECT,
- INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING,
- BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS
- OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
- ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
- TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
- USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH
- DAMAGE.</para>
- </important>
-</legalnotice>
-
diff --git a/en/handbook/contrib/chapter.sgml b/en/handbook/contrib/chapter.sgml
deleted file mode 100644
index 9a41073467..0000000000
--- a/en/handbook/contrib/chapter.sgml
+++ /dev/null
@@ -1,5796 +0,0 @@
-<!--
- The FreeBSD Documentation Project
-
- $Id: chapter.sgml,v 1.92 2000-03-19 06:20:31 vanilla Exp $
--->
-
-<chapter id="contrib">
- <title>Contributing to FreeBSD</title>
-
- <para><emphasis>Contributed by &a.jkh;.</emphasis></para>
-
- <para>So you want to contribute something to FreeBSD? That is great! We can
- always use the help, and FreeBSD is one of those systems that
- <emphasis>relies</emphasis> on the contributions of its user base in order
- to survive. Your contributions are not only appreciated, they are vital
- to FreeBSD's continued growth!</para>
-
- <para>Contrary to what some people might also have you believe, you do not
- need to be a hot-shot programmer or a close personal friend of the FreeBSD
- core team in order to have your contributions accepted. The FreeBSD
- Project's development is done by a large and growing number of
- international contributors whose ages and areas of technical expertise
- vary greatly, and there is always more work to be done than there are
- people available to do it.</para>
-
- <para>Since the FreeBSD project is responsible for an entire operating
- system environment (and its installation) rather than just a kernel or a
- few scattered utilities, our <filename>TODO</filename> list also spans a
- very wide range of tasks, from documentation, beta testing and
- presentation to highly specialized types of kernel development. No matter
- what your skill level, there is almost certainly something you can do to
- help the project!</para>
-
- <para>Commercial entities engaged in FreeBSD-related enterprises are also
- encouraged to contact us. Need a special extension to make your product
- work? You will find us receptive to your requests, given that they are not
- too outlandish. Working on a value-added product? Please let us know! We
- may be able to work cooperatively on some aspect of it. The free software
- world is challenging a lot of existing assumptions about how software is
- developed, sold, and maintained throughout its life cycle, and we urge you
- to at least give it a second look.</para>
-
- <sect1>
- <title>What Is Needed</title>
-
- <para>The following list of tasks and sub-projects represents something of
- an amalgam of the various core team <filename>TODO</filename> lists and
- user requests we have collected over the last couple of months. Where
- possible, tasks have been ranked by degree of urgency. If you are
- interested in working on one of the tasks you see here, send mail to the
- coordinator listed by clicking on their names. If no coordinator has
- been appointed, maybe you would like to volunteer?</para>
-
- <sect2>
- <title>High priority tasks</title>
-
- <para>The following tasks are considered to be urgent, usually because
- they represent something that is badly broken or sorely needed:</para>
-
- <orderedlist>
- <listitem>
- <para>3-stage boot issues. Overall coordination: &a.hackers;</para>
-
- <itemizedlist>
- <listitem>
- <para>Do WinNT compatible drive tagging so that the 3rd stage
- can provide an accurate mapping of BIOS geometries for
- disks.</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>Filesystem problems. Overall coordination: &a.fs;</para>
-
- <itemizedlist>
- <listitem>
- <para>Fix the MSDOS file system.</para>
- </listitem>
-
- <listitem>
- <para>Clean up and document the nullfs filesystem code.
- Coordinator: &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Fix the union file system. Coordinator: &a.dg;</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>Implement Int13 vm86 disk driver. Coordinator:
- &a.hackers;</para>
- </listitem>
-
- <listitem>
- <para>New bus architecture. Coordinator: &a.newbus;</para>
-
- <itemizedlist>
- <listitem>
- <para>Port existing ISA drivers to new architecture.</para>
- </listitem>
-
- <listitem>
- <para>Move all interrupt-management code to appropriate parts of
- the bus drivers.</para>
- </listitem>
-
- <listitem>
- <para>Port PCI subsystem to new architecture. Coordinator:
- &a.dfr;</para>
- </listitem>
-
- <listitem>
- <para>Figure out the right way to handle removable devices and
- then use that as a substrate on which PC-Card and CardBus
- support can be implemented.</para>
- </listitem>
-
- <listitem>
- <para>Resolve the probe/attach priority issue once and for
- all.</para>
- </listitem>
-
- <listitem>
- <para>Move any remaining buses over to the new
- architecture.</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>Kernel issues. Overall coordination: &a.hackers;</para>
- </listitem>
-
- <listitem>
- <para>Add more pro-active security infrastructure. Overall
- coordination: &a.security;</para>
-
- <itemizedlist>
- <listitem>
- <para>Build something like Tripwire(TM) into the kernel, with a
- remote and local part. There are a number of cryptographic
- issues to getting this right; contact the coordinator for
- details. Coordinator: &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Make the entire kernel use <literal>suser()</literal>
- instead of comparing to 0. It is presently using about half
- of each. Coordinator: &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Split securelevels into different parts, to allow an
- administrator to throw away those privileges he can throw
- away. Setting the overall securelevel needs to have the same
- effect as now, obviously. Coordinator: &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Make it possible to upload a list of &ldquo;allowed
- program&rdquo; to BPF, and then block BPF from accepting other
- programs. This would allow BPF to be used e.g. for DHCP,
- without allowing an attacker to start snooping the local
- network.</para>
- </listitem>
-
- <listitem>
- <para>Update the security checker script. We should at least
- grab all the checks from the other BSD derivatives, and add
- checks that a system with securelevel increased also have
- reasonable flags on the relevant parts. Coordinator:
- &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Add authorization infrastructure to the kernel, to allow
- different authorization policies. Part of this could be done
- by modifying <literal>suser()</literal>. Coordinator:
- &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Add code to the NFS layer so that you cannot
- <literal>chdir("..")</literal> out of an NFS partition. E.g.,
- <filename>/usr</filename> is a UFS partition with
- <filename>/usr/src</filename> NFS exported. Now it is
- possible to use the NFS filehandle for
- <filename>/usr/src</filename> to get access to
- <filename>/usr</filename>.</para>
- </listitem>
- </itemizedlist>
- </listitem>
- </orderedlist>
- </sect2>
-
- <sect2>
- <title>Medium priority tasks</title>
-
- <para>The following tasks need to be done, but not with any particular
- urgency:</para>
-
- <orderedlist>
- <listitem>
- <para>Full KLD based driver support/Configuration Manager.</para>
-
- <itemizedlist>
- <listitem>
- <para>Write a configuration manager (in the 3rd stage boot?)
- that probes your hardware in a sane manner, keeps only the
- KLDs required for your hardware, etc.</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>PCMCIA/PCCARD. Coordinators: &a.msmith; and &a.phk;</para>
-
- <itemizedlist>
- <listitem>
- <para>Documentation!</para>
- </listitem>
-
- <listitem>
- <para>Reliable operation of the pcic driver (needs
- testing).</para>
- </listitem>
-
- <listitem>
- <para>Recognizer and handler for <filename>sio.c</filename>
- (mostly done).</para>
- </listitem>
-
- <listitem>
- <para>Recognizer and handler for <filename>ed.c</filename>
- (mostly done).</para>
- </listitem>
-
- <listitem>
- <para>Recognizer and handler for <filename>ep.c</filename>
- (mostly done).</para>
- </listitem>
-
- <listitem>
- <para>User-mode recognizer and handler (partially done).</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>Advanced Power Management. Coordinators: &a.msmith; and
- &a.phk;</para>
-
- <itemizedlist>
- <listitem>
- <para>APM sub-driver (mostly done).</para>
- </listitem>
-
- <listitem>
- <para>IDE/ATA disk sub-driver (partially done).</para>
- </listitem>
-
- <listitem>
- <para>syscons/pcvt sub-driver.</para>
- </listitem>
-
- <listitem>
- <para>Integration with the PCMCIA/PCCARD drivers
- (suspend/resume).</para>
- </listitem>
- </itemizedlist>
- </listitem>
- </orderedlist>
- </sect2>
-
- <sect2>
- <title>Low priority tasks</title>
-
- <para>The following tasks are purely cosmetic or represent such an
- investment of work that it is not likely that anyone will get them
- done anytime soon:</para>
-
- <para>The first N items are from Terry Lambert
- <email>terry@lambert.org</email></para>
-
- <orderedlist>
- <listitem>
- <para>NetWare Server (protected mode ODI driver) loader and
- subservices to allow the use of ODI card drivers supplied with
- network cards. The same thing for NDIS drivers and NetWare SCSI
- drivers.</para>
- </listitem>
-
- <listitem>
- <para>An "upgrade system" option that works on Linux boxes instead
- of just previous rev FreeBSD boxes.</para>
- </listitem>
-
- <listitem>
- <para>Symmetric Multiprocessing with kernel preemption (requires
- kernel preemption).</para>
- </listitem>
-
- <listitem>
- <para>A concerted effort at support for portable computers. This is
- somewhat handled by changing PCMCIA bridging rules and power
- management event handling. But there are things like detecting
- internal vs. external display and picking a different screen
- resolution based on that fact, not spinning down the disk if the
- machine is in dock, and allowing dock-based cards to disappear
- without affecting the machines ability to boot (same issue for
- PCMCIA).</para>
- </listitem>
- </orderedlist>
- </sect2>
-
- <sect2>
- <title>Smaller tasks</title>
-
- <para>Most of the tasks listed in the previous sections require either a
- considerable investment of time or an in-depth knowledge of the
- FreeBSD kernel (or both). However, there are also many useful tasks
- which are suitable for &quot;weekend hackers&quot;, or people without
- programming skills.</para>
-
- <orderedlist>
- <listitem>
- <para>If you run FreeBSD-current and have a good Internet
- connection, there is a machine <hostid
- role="fqdn">current.FreeBSD.org</hostid> which builds a full
- release once a day &mdash; every now and again, try and install
- the latest release from it and report any failures in the
- process.</para>
- </listitem>
-
- <listitem>
- <para>Read the freebsd-bugs mailing list. There might be a
- problem you can comment constructively on or with patches you
- can test. Or you could even try to fix one of the problems
- yourself.</para>
- </listitem>
-
- <listitem>
- <para>Read through the FAQ and Handbook periodically. If anything
- is badly explained, out of date or even just completely wrong, let
- us know. Even better, send us a fix (SGML is not difficult to
- learn, but there is no objection to ASCII submissions).</para>
- </listitem>
-
- <listitem>
- <para>Help translate FreeBSD documentation into your native language
- (if not already available) &mdash; just send an email to &a.doc;
- asking if anyone is working on it. Note that you are not
- committing yourself to translating every single FreeBSD document
- by doing this &mdash; in fact, the documentation most in need of
- translation is the installation instructions.</para>
- </listitem>
-
- <listitem>
- <para>Read the freebsd-questions mailing list and &ng.misc
- occasionally (or even regularly). It can be very satisfying to
- share your expertise and help people solve their problems;
- sometimes you may even learn something new yourself! These forums
- can also be a source of ideas for things to work on.</para>
- </listitem>
-
- <listitem>
- <para>If you know of any bugfixes which have been successfully
- applied to -current but have not been merged into -stable after a
- decent interval (normally a couple of weeks), send the committer a
- polite reminder.</para>
- </listitem>
-
- <listitem>
- <para>Move contributed software to <filename>src/contrib</filename>
- in the source tree.</para>
- </listitem>
-
- <listitem>
- <para>Make sure code in <filename>src/contrib</filename> is up to
- date.</para>
- </listitem>
-
- <listitem>
- <para>Look for year 2000 bugs (and fix any you find!)</para>
- </listitem>
-
- <listitem>
- <para>Build the source tree (or just part of it) with extra warnings
- enabled and clean up the warnings.</para>
- </listitem>
-
- <listitem>
- <para>Fix warnings for ports which do deprecated things like using
- gets() or including malloc.h.</para>
- </listitem>
-
- <listitem>
- <para>If you have contributed any ports, send your patches back to
- the original author (this will make your life easier when they
- bring out the next version)</para>
- </listitem>
-
- <listitem>
- <para>Suggest further tasks for this list!</para>
- </listitem>
- </orderedlist>
- </sect2>
-
- <sect2>
- <title>Work through the PR database</title>
-
- <para>The <ulink
- url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">FreeBSD PR
- list</ulink> shows all the current active problem reports and
- requests for enhancement that have been submitted by FreeBSD users.
- Look through the open PRs, and see if anything there takes your
- interest. Some of these might be very simple tasks, that just need an
- extra pair of eyes to look over them and confirm that the fix in the
- PR is a good one. Others might be much more complex.</para>
-
- <para>Start with the PRs that have not been assigned to anyone else, but
- if one them is assigned to someone else, but it looks like something
- you can handle, e-mail the person it is assigned to and ask if you can
- work on it&mdash;they might already have a patch ready to be tested,
- or further ideas that you can discuss with them.</para>
- </sect2>
- </sect1>
-
- <sect1>
- <title>How to Contribute</title>
-
- <para>Contributions to the system generally fall into one or more of the
- following 6 categories:</para>
-
- <sect2 id="contrib-general">
- <title>Bug reports and general commentary</title>
-
- <para>An idea or suggestion of <emphasis>general</emphasis> technical
- interest should be mailed to the &a.hackers;. Likewise, people with
- an interest in such things (and a tolerance for a
- <emphasis>high</emphasis> volume of mail!) may subscribe to the
- hackers mailing list by sending mail to &a.majordomo;. See <link
- linkend="eresources-mail">mailing lists</link> for more information
- about this and other mailing lists.</para>
-
- <para>If you find a bug or are submitting a specific change, please
- report it using the &man.send-pr.1; program or its <ulink
- URL="http://www.FreeBSD.org/send-pr.html">WEB-based
- equivalent</ulink>. Try to fill-in each field of the bug report.
- Unless they exceed 65KB, include any patches directly in the report.
- When including patches, <emphasis>do not</emphasis> use cut-and-paste
- because cut-and-paste turns tabs into spaces and makes them unusable.
- Consider compressing patches and using &man.uuencode.1; if they exceed
- 20KB. Upload very large submissions to <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/">ftp.FreeBSD.org:/pub/FreeBSD/incoming/</ulink>.</para>
-
- <para>After filing a report, you should receive confirmation along with
- a tracking number. Keep this tracking number so that you can update
- us with details about the problem by sending mail to
- <email>bug-followup@FreeBSD.org</email>. Use the number as the
- message subject, e.g. <literal>"Re: kern/3377"</literal>. Additional
- information for any bug report should be submitted this way.</para>
-
- <para>If you do not receive confirmation in a timely fashion (3 days to
- a week, depending on your email connection) or are, for some reason,
- unable to use the &man.send-pr.1; command, then you may ask
- someone to file it for you by sending mail to the &a.bugs;.</para>
- </sect2>
-
- <sect2>
- <title>Changes to the documentation</title>
-
- <para>Changes to the documentation are overseen by the &a.doc;. Send
- submissions and changes (even small ones are welcome!) using
- <command>send-pr</command> as described in <link
- linkend="contrib-general">Bug Reports and General
- Commentary</link>.</para>
- </sect2>
-
- <sect2>
- <title>Changes to existing source code</title>
-
- <para>An addition or change to the existing source code is a somewhat
- trickier affair and depends a lot on how far out of date you are with
- the current state of the core FreeBSD development. There is a special
- on-going release of FreeBSD known as &ldquo;FreeBSD-current&rdquo;
- which is made available in a variety of ways for the convenience of
- developers working actively on the system. See <link
- linkend="current">Staying current with FreeBSD</link> for more
- information about getting and using FreeBSD-current.</para>
-
- <para>Working from older sources unfortunately means that your changes
- may sometimes be too obsolete or too divergent for easy re-integration
- into FreeBSD. Chances of this can be minimized somewhat by
- subscribing to the &a.announce; and the &a.current; lists, where
- discussions on the current state of the system take place.</para>
-
- <para>Assuming that you can manage to secure fairly up-to-date sources
- to base your changes on, the next step is to produce a set of diffs to
- send to the FreeBSD maintainers. This is done with the &man.diff.1;
- command, with the &ldquo;context diff&rdquo; form
- being preferred. For example:</para>
-
- <para>
- <screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
-
- or
-
- <screen>&prompt.user; <userinput>diff -c -r olddir newdir</userinput></screen>
-
- would generate such a set of context diffs for the given source file
- or directory hierarchy. See the man page for &man.diff.1; for more
- details.</para>
-
- <para>Once you have a set of diffs (which you may test with the
- &man.patch.1; command), you should submit them for inclusion with
- FreeBSD. Use the &man.send-pr.1; program as described in <link
- linkend="contrib-general">Bug Reports and General Commentary</link>.
- <emphasis>Do not</emphasis> just send the diffs to the &a.hackers; or
- they will get lost! We greatly appreciate your submission (this is a
- volunteer project!); because we are busy, we may not be able to
- address it immediately, but it will remain in the pr database until we
- do.</para>
-
- <para>If you feel it appropriate (e.g. you have added, deleted, or
- renamed files), bundle your changes into a <command>tar</command> file
- and run the &man.uuencode.1; program on it. Shar archives are also
- welcome.</para>
-
- <para>If your change is of a potentially sensitive nature, e.g. you are
- unsure of copyright issues governing its further distribution or you
- are simply not ready to release it without a tighter review first,
- then you should send it to &a.core; directly rather than submitting it
- with &man.send-pr.1;. The core mailing list reaches a much smaller
- group of people who do much of the day-to-day work on FreeBSD. Note
- that this group is also <emphasis>very busy</emphasis> and so you
- should only send mail to them where it is truly necessary.</para>
-
- <para>Please refer to <command>man 9 intro</command> and <command>man 9
- style</command> for some information on coding style. We would
- appreciate it if you were at least aware of this information before
- submitting code.</para>
- </sect2>
-
- <sect2>
- <title>New code or major value-added packages</title>
-
- <para>In the rare case of a significant contribution of a large body
- work, or the addition of an important new feature to FreeBSD, it
- becomes almost always necessary to either send changes as uuencode'd
- tar files or upload them to our ftp site <ulink
- URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming">ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming</ulink>.</para>
-
- <para>When working with large amounts of code, the touchy subject of
- copyrights also invariably comes up. Acceptable copyrights for code
- included in FreeBSD are:</para>
-
- <orderedlist>
- <listitem>
- <para>The BSD copyright. This copyright is most preferred due to
- its &ldquo;no strings attached&rdquo; nature and general
- attractiveness to commercial enterprises. Far from discouraging
- such commercial use, the FreeBSD Project actively encourages such
- participation by commercial interests who might eventually be
- inclined to invest something of their own into FreeBSD.</para>
- </listitem>
-
- <listitem>
- <para>The GNU Public License, or &ldquo;GPL&rdquo;. This license is
- not quite as popular with us due to the amount of extra effort
- demanded of anyone using the code for commercial purposes, but
- given the sheer quantity of GPL'd code we currently require
- (compiler, assembler, text formatter, etc) it would be silly to
- refuse additional contributions under this license. Code under
- the GPL also goes into a different part of the tree, that being
- <filename>/sys/gnu</filename> or
- <filename>/usr/src/gnu</filename>, and is therefore easily
- identifiable to anyone for whom the GPL presents a problem.</para>
- </listitem>
- </orderedlist>
-
- <para>Contributions coming under any other type of copyright must be
- carefully reviewed before their inclusion into FreeBSD will be
- considered. Contributions for which particularly restrictive
- commercial copyrights apply are generally rejected, though the authors
- are always encouraged to make such changes available through their own
- channels.</para>
-
- <para>To place a &ldquo;BSD-style&rdquo; copyright on your work, include
- the following text at the very beginning of every source code file you
- wish to protect, replacing the text between the <literal>%%</literal>
- with the appropriate information.</para>
-
- <programlisting>
-Copyright (c) %%proper_years_here%%
- %%your_name_here%%, %%your_state%% %%your_zip%%.
- All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer as
- the first lines of this file unmodified.
-2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-
-THIS SOFTWARE IS PROVIDED BY %%your_name_here%% ``AS IS'' AND ANY EXPRESS OR
-IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
-IN NO EVENT SHALL %%your_name_here%% BE LIABLE FOR ANY DIRECT, INDIRECT,
-INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
-NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
-THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
- &#36;Id&#36;</programlisting>
-
- <para>For your convenience, a copy of this text can be found in
- <filename>/usr/share/examples/etc/bsd-style-copyright</filename>.</para>
- </sect2>
-
- <sect2>
- <title>Money, Hardware or Internet access</title>
-
- <para>We are always very happy to accept donations to further the cause
- of the FreeBSD Project and, in a volunteer effort like ours, a little
- can go a long way! Donations of hardware are also very important to
- expanding our list of supported peripherals since we generally lack
- the funds to buy such items ourselves.</para>
-
- <sect3>
- <title><anchor id="donations">Donating funds</title>
-
- <para>While the FreeBSD Project is not a 501(c)(3) (charitable)
- corporation and hence cannot offer special tax incentives for any
- donations made, any such donations will be gratefully accepted on
- behalf of the project by FreeBSD, Inc.</para>
-
- <para>FreeBSD, Inc. was founded in early 1995 by &a.jkh; and &a.dg;
- with the goal of furthering the aims of the FreeBSD Project and
- giving it a minimal corporate presence. Any and all funds donated
- (as well as any profits that may eventually be realized by FreeBSD,
- Inc.) will be used exclusively to further the project's
- goals.</para>
-
- <para>Please make any checks payable to FreeBSD, Inc., sent in care of
- the following address:</para>
-
- <address>
- <otheraddr>FreeBSD, Inc.</otheraddr>
- <otheraddr>c/o Jordan Hubbard</otheraddr>
- <street>4041 Pike Lane, Suite F</street>
- <city>Concord</city>
- <state>CA</state>, <postcode>94520</postcode>
- </address>
-
- <para>(currently using the Walnut Creek CDROM address until a PO box
- can be opened)</para>
-
- <para>Wire transfers may also be sent directly to:</para>
-
- <address>
- <otheraddr>Bank Of America</otheraddr>
- <otheraddr>Concord Main Office</otheraddr>
- <pob>P.O. Box 37176</pob>
- <city>San Francisco</city>
- <state>CA</state>, <postcode>94137-5176</postcode>
-
- <otheraddr>Routing #: 121-000-358</otheraddr>
- <otheraddr>Account #: 01411-07441 (FreeBSD, Inc.)</otheraddr>
- </address>
-
- <para>Any correspondence related to donations should be sent to &a.jkh,
- either via email or to the FreeBSD, Inc. postal address given above.
- </para>
-
- <para>If you do not wish to be listed in our <link
- linkend="donors">donors</link> section, please specify this when
- making your donation. Thanks!</para>
- </sect3>
-
- <sect3>
- <title>Donating hardware</title>
-
- <para>Donations of hardware in any of the 3 following categories are
- also gladly accepted by the FreeBSD Project:</para>
-
- <itemizedlist>
- <listitem>
- <para>General purpose hardware such as disk drives, memory or
- complete systems should be sent to the FreeBSD, Inc. address
- listed in the <emphasis>donating funds</emphasis>
- section.</para>
- </listitem>
-
- <listitem>
- <para>Hardware for which ongoing compliance testing is desired.
- We are currently trying to put together a testing lab of all
- components that FreeBSD supports so that proper regression
- testing can be done with each new release. We are still lacking
- many important pieces (network cards, motherboards, etc) and if
- you would like to make such a donation, please contact &a.dg;
- for information on which items are still required.</para>
- </listitem>
-
- <listitem>
- <para>Hardware currently unsupported by FreeBSD for which you
- would like to see such support added. Please contact the
- &a.core; before sending such items as we will need to find a
- developer willing to take on the task before we can accept
- delivery of new hardware.</para>
- </listitem>
- </itemizedlist>
- </sect3>
-
- <sect3>
- <title>Donating Internet access</title>
-
- <para>We can always use new mirror sites for FTP, WWW or
- <command>cvsup</command>. If you would like to be such a mirror,
- please contact the FreeBSD project administrators
- <email>admin@FreeBSD.org</email> for more information.</para>
- </sect3>
- </sect2>
- </sect1>
-
- <sect1 id="donors">
- <title>Donors Gallery</title>
-
- <para>The FreeBSD Project is indebted to the following donors and would
- like to publically thank them here!</para>
-
- <itemizedlist>
- <listitem>
- <para><emphasis>Contributors to the central server
- project:</emphasis></para>
-
- <para>The following individuals and businesses made it possible for
- the FreeBSD Project to build a new central server machine to
- eventually replace <hostid role="fqdn">freefall.FreeBSD.org</hostid>
- by donating the following items:</para>
-
- <itemizedlist>
- <listitem>
- <para>&a.mbarkah and his employer, <ulink URL="http://www.hemi.com">
- Hemisphere Online</ulink>, donated a <emphasis>Pentium Pro
- (P6) 200Mhz CPU</emphasis></para>
- </listitem>
-
- <listitem>
- <para><ulink URL="http://www.asacomputers.com">ASA
- Computers</ulink> donated a <emphasis>Tyan 1662
- motherboard</emphasis>.</para>
- </listitem>
-
- <listitem>
- <para>Joe McGuckin <email>joe@via.net</email> of <ulink
- URL="http://www.via.net">ViaNet Communications</ulink> donated
- a <emphasis>Kingston ethernet controller.</emphasis></para>
- </listitem>
-
- <listitem>
- <para>Jack O'Neill <email>jack@diamond.xtalwind.net</email>
- donated an <emphasis>NCR 53C875 SCSI controller
- card</emphasis>.</para>
- </listitem>
-
- <listitem>
- <para>Ulf Zimmermann <email>ulf@Alameda.net</email> of <ulink
- URL="http://www.Alameda.net">Alameda Networks</ulink> donated
- <emphasis>128MB of memory</emphasis>, a <emphasis>4 Gb disk
- drive and the case.</emphasis></para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para><emphasis>Direct funding:</emphasis></para>
-
- <para>The following individuals and businesses have generously
- contributed direct funding to the project:</para>
-
- <itemizedlist>
- <listitem>
- <para>Annelise Anderson
- <email>ANDRSN@HOOVER.STANFORD.EDU</email></para>
- </listitem>
-
- <listitem>
- <para>&a.dillon</para>
- </listitem>
-
- <listitem>
- <para><ulink URL="http://www.epilogue.com/">Epilogue Technology
- Corporation</ulink></para>
- </listitem>
-
- <listitem>
- <para>&a.sef</para>
- </listitem>
-
- <listitem>
- <para>Don Scott Wilde</para>
- </listitem>
-
- <listitem>
- <para>Gianmarco Giovannelli
- <email>gmarco@masternet.it</email></para>
- </listitem>
-
- <listitem>
- <para>Josef C. Grosch <email>joeg@truenorth.org</email></para>
- </listitem>
-
- <listitem>
- <para>Robert T. Morris</para>
- </listitem>
-
- <listitem>
- <para>&a.chuckr</para>
- </listitem>
-
- <listitem>
- <para>Kenneth P. Stox <email>ken@stox.sa.enteract.com</email> of
- <ulink URL="http://www.imagescape.com">Imaginary Landscape,
- LLC.</ulink></para>
- </listitem>
-
- <listitem>
- <para>Dmitry S. Kohmanyuk <email>dk@dog.farm.org</email></para>
- </listitem>
-
- <listitem>
- <para><ulink URL="http://www.cdrom.co.jp/">Laser5</ulink> of Japan
- (a portion of the profits from sales of their various FreeBSD
- CD-ROMs.</para>
- </listitem>
-
- <listitem>
- <para><ulink URL="http://www.mmjp.or.jp/fuki/">Fuki Shuppan
- Publishing Co.</ulink> donated a portion of their profits from
- <emphasis>Hajimete no FreeBSD</emphasis> (FreeBSD, Getting
- started) to the FreeBSD and XFree86 projects.</para>
- </listitem>
-
- <listitem>
- <para><ulink URL="http://www.ascii.co.jp/">ASCII Corp.</ulink>
- donated a portion of their profits from several FreeBSD-related
- books to the FreeBSD project.</para>
- </listitem>
-
- <listitem>
- <para><ulink URL="http://www.yokogawa.co.jp/">Yokogawa Electric
- Corp</ulink> has generously donated significant funding to the
- FreeBSD project.</para>
- </listitem>
-
- <listitem>
- <para><ulink URL="http://www.buffnet.net/">BuffNET</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.pacificsolutions.com/">Pacific
- Solutions</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.siemens.de/">Siemens AG</ulink>
- via <ulink url="mailto:andre.albsmeier@mchp.siemens.de">Andre
- Albsmeier</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink url="mailto:ras@interaccess.com">Chris Silva</ulink>
- </para>
- </listitem>
-
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para><emphasis>Hardware contributors:</emphasis></para>
-
- <para>The following individuals and businesses have generously
- contributed hardware for testing and device driver
- development/support:</para>
-
- <itemizedlist>
- <listitem>
- <para>Walnut Creek CDROM for providing the Pentium P5-90 and
- 486/DX2-66 EISA/VL systems that are being used for our
- development work, to say nothing of the network access and other
- donations of hardware resources.</para>
- </listitem>
-
- <listitem>
- <para>TRW Financial Systems, Inc. provided 130 PCs, three 68 GB
- fileservers, twelve Ethernets, two routers and an ATM switch for
- debugging the diskless code.</para>
- </listitem>
-
- <listitem>
- <para>Dermot McDonnell donated the Toshiba XM3401B CDROM drive
- currently used in freefall.</para>
- </listitem>
-
- <listitem>
- <para>&a.chuck; contributed his floppy tape streamer for
- experimental work.</para>
- </listitem>
-
- <listitem>
- <para>Larry Altneu <email>larry@ALR.COM</email>, and &a.wilko;,
- provided Wangtek and Archive QIC-02 tape drives in order to
- improve the <devicename>wt</devicename> driver.</para>
- </listitem>
-
- <listitem>
- <para>Ernst Winter <email>ewinter@lobo.muc.de</email> contributed
- a 2.88 MB floppy drive to the project. This will hopefully
- increase the pressure for rewriting the floppy disk driver.
- <!-- smiley -->;-)</para>
- </listitem>
-
- <listitem>
- <para><ulink URL="http://www.tekram.com">Tekram
- Technologies</ulink> sent one each of their DC-390, DC-390U
- and DC-390F FAST and ULTRA SCSI host adapter cards for
- regression testing of the NCR and AMD drivers with their cards.
- They are also to be applauded for making driver sources for free
- operating systems available from their FTP server <ulink
- URL="ftp://ftp.tekram.com/scsi/FreeBSD">ftp://ftp.tekram.com/scsi/FreeBSD</ulink>.</para>
- </listitem>
-
- <listitem>
- <para><email>Larry M. Augustin</email> contributed not only a
- Symbios Sym8751S SCSI card, but also a set of data books,
- including one about the forthcoming Sym53c895 chip with Ultra-2
- and LVD support, and the latest programming manual with
- information on how to safely use the advanced features of the
- latest Symbios SCSI chips. Thanks a lot!</para>
- </listitem>
-
- <listitem>
- <para>Christoph Kukulies <email>kuku@FreeBSD.org</email> donated
- an FX120 12 speed Mitsumi CDROM drive for IDE CDROM driver
- development.</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para><emphasis>Special contributors:</emphasis></para>
-
- <itemizedlist>
- <listitem>
- <para><ulink URL="http://www.cdrom.com">Walnut Creek CDROM</ulink>
- has donated almost more than we can say (see the <link
- linkend="history">history</link> document for more details).
- In particular, we would like to thank them for the original
- hardware used for <hostid
- role="fqdn">freefall.FreeBSD.org</hostid>, our primary
- development machine, and for <hostid
- role="fqdn">thud.FreeBSD.org</hostid>, a testing and build
- box. We are also indebted to them for funding various
- contributors over the years and providing us with unrestricted
- use of their T1 connection to the Internet.</para>
- </listitem>
-
- <listitem>
- <para>The <ulink URL="http://www.interface-business.de">interface
- business GmbH, Dresden</ulink> has been patiently supporting
- &a.joerg; who has often preferred FreeBSD work over paywork, and
- used to fall back to their (quite expensive) EUnet Internet
- connection whenever his private connection became too slow or
- flakey to work with it...</para>
- </listitem>
-
- <listitem>
- <para><ulink URL="http://www.bsdi.com">Berkeley Software Design,
- Inc.</ulink> has contributed their DOS emulator code to the
- remaining BSD world, which is used in the
- <emphasis>doscmd</emphasis> command.</para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1>
- <title>Core Team Alumni</title>
-
- <para>The following people were members of the FreeBSD core team during
- the periods indicated. We thank them for their past efforts in the
- service of the FreeBSD project.</para>
-
- <para><emphasis>In rough chronological order:</emphasis></para>
-
- <itemizedlist>
- <listitem>
- <para>&a.guido (1995 - 1999)</para>
- </listitem>
-
- <listitem>
- <para>&a.dyson (1993 - 1998)</para>
- </listitem>
-
- <listitem>
- <para>&a.nate (1992 - 1996)</para>
- </listitem>
-
- <listitem>
- <para>&a.rgrimes (1992 - 1995)</para>
- </listitem>
-
- <listitem>
- <para>Andreas Schulz (1992 - 1995)</para>
- </listitem>
-
- <listitem>
- <para>&a.csgr (1993 - 1995)</para>
- </listitem>
-
- <listitem>
- <para>&a.paul (1992 - 1995)</para>
- </listitem>
-
- <listitem>
- <para>&a.smace (1993 - 1994)</para>
- </listitem>
-
- <listitem>
- <para>Andrew Moore (1993 - 1994)</para>
- </listitem>
-
- <listitem>
- <para>Christoph Robitschko (1993 - 1994)</para>
- </listitem>
-
- <listitem>
- <para>J. T. Conklin (1992 - 1993)</para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1>
- <title>Derived Software Contributors</title>
-
- <para>This software was originally derived from William F. Jolitz's 386BSD
- release 0.1, though almost none of the original 386BSD specific code
- remains. This software has been essentially re-implemented from the
- 4.4BSD-Lite release provided by the Computer Science Research Group
- (CSRG) at the University of California, Berkeley and associated academic
- contributors.</para>
-
- <para>There are also portions of NetBSD and OpenBSD that have been
- integrated into FreeBSD as well, and we would therefore like to thank
- all the contributors to NetBSD and OpenBSD for their work.</para>
- </sect1>
-
- <sect1 id="contrib-additional">
- <title>Additional FreeBSD Contributors</title>
-
- <para>(in alphabetical order by first name):</para>
-
- <itemizedlist>
- <listitem>
- <para>ABURAYA Ryushirou <email>rewsirow@ff.iij4u.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>AMAGAI Yoshiji <email>amagai@nue.org</email></para>
- </listitem>
-
- <listitem>
- <para>Aaron Bornstein <email>aaronb@j51.com</email></para>
- </listitem>
-
- <listitem>
- <para>Aaron Smith <email>aaron@mutex.org</email></para>
- </listitem>
-
- <listitem>
- <para>Achim Patzner <email>ap@noses.com</email></para>
- </listitem>
-
- <listitem>
- <para>Ada T Lim <email>ada@bsd.org</email></para>
- </listitem>
-
- <listitem>
- <para>Adam Baran <email>badam@mw.mil.pl</email></para>
- </listitem>
-
- <listitem>
- <para>Adam Glass <email>glass@postgres.berkeley.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Adam McDougall <email>mcdouga9@egr.msu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Adrian Colley <email>aecolley@ois.ie</email></para>
- </listitem>
-
- <listitem>
- <para>Adrian Hall <email>adrian@ibmpcug.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Adrian Mariano <email>adrian@cam.cornell.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Adrian Steinmann <email>ast@marabu.ch</email></para>
- </listitem>
-
- <listitem>
- <para>Adam Strohl <email>troll@digitalspark.net</email></para>
- </listitem>
-
- <listitem>
- <para>Adrian T. Filipi-Martin
- <email>atf3r@agate.cs.virginia.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Ajit Thyagarajan <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Akio Morita
- <email>amorita@meadow.scphys.kyoto-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Akira SAWADA <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Akira Watanabe
- <email>akira@myaw.ei.meisei-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Akito Fujita <email>fujita@zoo.ncl.omron.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Alain Kalker
- <email>A.C.P.M.Kalker@student.utwente.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Alan Bawden <email>alan@curry.epilogue.com</email></para>
- </listitem>
-
- <listitem>
- <para>Alec Wolman <email>wolman@cs.washington.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Aled Morris <email>aledm@routers.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Alex <email>garbanzo@hooked.net</email></para>
- </listitem>
-
- <listitem>
- <para>Alex D. Chen
- <email>dhchen@Canvas.dorm7.nccu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Alex G. Bulushev <email>bag@demos.su</email></para>
- </listitem>
-
- <listitem>
- <para>Alex Le Heux <email>alexlh@funk.org</email></para>
- </listitem>
-
- <listitem>
- <para>Alex Perel <email>veers@disturbed.net</email></para>
- </listitem>
-
- <listitem>
- <para>Alexander B. Povolotsky <email>tarkhil@mgt.msk.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Alexander Leidinger
- <email>netchild@wurzelausix.CS.Uni-SB.DE</email></para>
- </listitem>
-
- <listitem>
- <para>Alexander Langer <email>alex@cichlids.com</email></para>
- </listitem>
-
- <listitem>
- <para>Alexandre Snarskii <email>snar@paranoia.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Alistair G. Crooks <email>agc@uts.amdahl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Allan Saddi <email>asaddi@philosophysw.com</email></para>
- </listitem>
-
- <listitem>
- <para>Allen Campbell <email>allenc@verinet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Amakawa Shuhei <email>amakawa@hoh.t.u-tokyo.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Amancio Hasty <email>hasty@star-gate.com</email></para>
- </listitem>
-
- <listitem>
- <para>Amir Farah <email>amir@comtrol.com</email></para>
- </listitem>
-
- <listitem>
- <para>Amy Baron <email>amee@beer.org</email></para>
- </listitem>
-
- <listitem>
- <para>Anatoly A. Orehovsky <email>tolik@mpeks.tomsk.su</email></para>
- </listitem>
-
- <listitem>
- <para>Anatoly Vorobey <email>mellon@pobox.com</email></para>
- </listitem>
-
- <listitem>
- <para>Anders Nordby <email>nickerne@nome.no</email></para>
- </listitem>
-
- <listitem>
- <para>Anders Thulin <email>Anders.X.Thulin@telia.se</email></para>
- </listitem>
-
- <listitem>
- <para>Andras Olah <email>olah@cs.utwente.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Andre Albsmeier
- <email>Andre.Albsmeier@mchp.siemens.de</email></para>
- </listitem>
-
- <listitem>
- <para>Andre Oppermann <email>andre@pipeline.ch</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Haakh <email>ah@alman.robin.de</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Kohout <email>shanee@rabbit.augusta.de</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Lohr <email>andreas@marvin.RoBIN.de</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Schulz <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Wetzel <email>mickey@deadline.snafu.de</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Wrede <email>andreas@planix.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andres Vega Garcia <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Atrens <email>atreand@statcan.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Boothman <email>andrew@cream.org</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Gillham <email>gillham@andrews.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Gordon <email>andrew.gordon@net-tel.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Herbert <email>andrew@werple.apana.org.au</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew J. Korty <email>ajk@purdue.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew L. Moore <email>alm@mclink.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew McRae <email>amcrae@cisco.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Stevenson <email>andrew@ugh.net.au</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Timonin <email>tim@pool1.convey.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew V. Stesin <email>stesin@elvisti.kiev.ua</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Webster <email>awebster@dataradio.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andrey Zakhvatov <email>andy@icc.surw.chel.su</email></para>
- </listitem>
-
- <listitem>
- <para>Andy Farkas <email>andyf@speednet.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Andy Valencia <email>ajv@csd.mot.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andy Whitcroft <email>andy@sarc.city.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Angelo Turetta <email>ATuretta@stylo.it</email></para>
- </listitem>
-
- <listitem>
- <para>Anthony C. Chavez <email>magus@xmission.com</email></para>
- </listitem>
-
- <listitem>
- <para>Anthony Yee-Hang Chan <email>yeehang@netcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Anton Berezin <email>tobez@plab.ku.dk</email></para>
- </listitem>
-
- <listitem>
- <para>Antti Kaipila <email>anttik@iki.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Are Bryne <email>are.bryne@communique.no</email></para>
- </listitem>
-
- <listitem>
- <para>Ari Suutari <email>ari@suutari.iki.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Arjan de Vet <email>devet@IAEhv.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Arne Henrik Juul <email>arnej@Lise.Unit.NO</email></para>
- </listitem>
-
- <listitem>
- <para>Assar Westerlund <email>assar@sics.se</email></para>
- </listitem>
-
- <listitem>
- <para>Atsushi Furuta <email>furuta@sra.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Atsushi Murai <email>amurai@spec.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Bakul Shah <email>bvs@bitblocks.com</email></para>
- </listitem>
-
- <listitem>
- <para>Barry Bierbauch <email>pivrnec@vszbr.cz</email></para>
- </listitem>
-
- <listitem>
- <para>Barry Lustig <email>barry@ictv.com</email></para>
- </listitem>
-
- <listitem>
- <para>Ben Hutchinson <email>benhutch@xfiles.org.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Ben Jackson <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Ben Smithurst <email>ben@scientia.demon.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Ben Walter <email>bwalter@itachi.swcp.com</email></para>
- </listitem>
-
- <listitem>
- <para>Benjamin Lewis <email>bhlewis@gte.net</email></para>
- </listitem>
-
- <listitem>
- <para>Bernd Rosauer <email>br@schiele-ct.de</email></para>
- </listitem>
-
- <listitem>
- <para>Bill Kish <email>kish@osf.org</email></para>
- </listitem>
-
- <listitem>
- <para>Bill Trost <email>trost@cloud.rain.com</email></para>
- </listitem>
-
- <listitem>
- <para>Blaz Zupan <email>blaz@amis.net</email></para>
- </listitem>
-
- <listitem>
- <para>Bob Van Valzah <email>Bob@whitebarn.com</email></para>
- </listitem>
-
- <listitem>
- <para>Bob Willcox <email>bob@luke.pmr.com</email></para>
- </listitem>
-
- <listitem>
- <para>Boris Staeblow <email>balu@dva.in-berlin.de</email></para>
- </listitem>
-
- <listitem>
- <para>Boyd R. Faulkner <email>faulkner@asgard.bga.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brad Karp <email>karp@eecs.harvard.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Bradley Dunn <email>bradley@dunn.org</email></para>
- </listitem>
-
- <listitem>
- <para>Brandon Fosdick <email>bfoz@glue.umd.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Brandon Gillespie <email>brandon@roguetrader.com</email></para>
- </listitem>
-
- <listitem>
- <para>&a.wlloyd</para>
- </listitem>
-
- <listitem>
- <para>Bob Wilcox <email>bob@obiwan.uucp</email></para>
- </listitem>
-
- <listitem>
- <para>Boyd Faulkner <email>faulkner@mpd.tandem.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brent J. Nordquist <email>bjn@visi.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brett Lymn <email>blymn@mulga.awadi.com.AU</email></para>
- </listitem>
-
- <listitem>
- <para>Brett Taylor
- <email>brett@peloton.physics.montana.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Campbell <email>brianc@pobox.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Clapper <email>bmc@willscreek.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Cully <email>shmit@kublai.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Handy
- <email>handy@lambic.space.lockheed.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Litzinger <email>brian@MediaCity.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian McGovern <email>bmcgover@cisco.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Moore <email>ziff@houdini.eecs.umich.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Brian R. Haug <email>haug@conterra.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Tao <email>taob@risc.org</email></para>
- </listitem>
-
- <listitem>
- <para>Brion Moss <email>brion@queeg.com</email></para>
- </listitem>
-
- <listitem>
- <para>Bruce A. Mah <email>bmah@ca.sandia.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Bruce Albrecht <email>bruce@zuhause.mn.org</email></para>
- </listitem>
-
- <listitem>
- <para>Bruce Gingery <email>bgingery@gtcs.com</email></para>
- </listitem>
-
- <listitem>
- <para>Bruce J. Keeler <email>loodvrij@gridpoint.com</email></para>
- </listitem>
-
- <listitem>
- <para>Bruce Murphy <email>packrat@iinet.net.au</email></para>
- </listitem>
-
- <listitem>
- <para>Bruce Walter <email>walter@fortean.com</email></para>
- </listitem>
-
- <listitem>
- <para>Carey Jones <email>mcj@acquiesce.org</email></para>
- </listitem>
-
- <listitem>
- <para>Carl Fongheiser <email>cmf@netins.net</email></para>
- </listitem>
-
- <listitem>
- <para>Carl Mascott <email>cmascott@world.std.com</email></para>
- </listitem>
-
- <listitem>
- <para>Casper <email>casper@acc.am</email></para>
- </listitem>
-
- <listitem>
- <para>Castor Fu <email>castor@geocast.com</email></para>
- </listitem>
-
- <listitem>
- <para>Cejka Rudolf <email>cejkar@dcse.fee.vutbr.cz</email></para>
- </listitem>
-
- <listitem>
- <para>Chain Lee <email>chain@110.net</email></para>
- </listitem>
-
- <listitem>
- <para>Charles Hannum <email>mycroft@ai.mit.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Charles Henrich <email>henrich@msu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Charles Mott <email>cmott@srv.net</email></para>
- </listitem>
-
- <listitem>
- <para>Charles Owens <email>owensc@enc.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Chet Ramey <email>chet@odin.INS.CWRU.Edu</email></para>
- </listitem>
-
- <listitem>
- <para>Chia-liang Kao <email>clkao@CirX.ORG</email></para>
- </listitem>
-
- <listitem>
- <para>Chiharu Shibata <email>chi@bd.mbn.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Chip Norkus <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Choi Jun Ho <email>junker@jazz.snu.ac.kr</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Csanady <email>cc@tarsier.ca.sandia.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Dabrowski <email>chris@vader.org</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Dillon <email>cdillon@wolves.k12.mo.us</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Shenton
- <email>cshenton@angst.it.hq.nasa.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Stenton <email>jacs@gnome.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Timmons <email>skynyrd@opus.cts.cwu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Torek <email>torek@ee.lbl.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Christian Gusenbauer
- <email>cg@fimp01.fim.uni-linz.ac.at</email></para>
- </listitem>
-
- <listitem>
- <para>Christian Haury <email>Christian.Haury@sagem.fr</email></para>
- </listitem>
-
- <listitem>
- <para>Christian Weisgerber
- <email>naddy@bigeye.rhein-neckar.de</email></para>
- </listitem>
-
- <listitem>
- <para>Christoph P. Kukulies <email>kuku@FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Christoph Robitschko
- <email>chmr@edvz.tu-graz.ac.at</email></para>
- </listitem>
-
- <listitem>
- <para>Christoph Weber-Fahr
- <email>wefa@callcenter.systemhaus.net</email></para>
- </listitem>
-
- <listitem>
- <para>Christopher G. Demetriou
- <email>cgd@postgres.berkeley.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Christopher T. Johnson
- <email>cjohnson@neunacht.netgsi.com</email></para>
- </listitem>
-
- <listitem>
- <para>Chrisy Luke <email>chrisy@flix.net</email></para>
- </listitem>
-
- <listitem>
- <para>Chuck Hein <email>chein@cisco.com</email></para>
- </listitem>
-
- <listitem>
- <para>Clive Lin <email>clive@CiRX.ORG</email></para>
- </listitem>
-
- <listitem>
- <para>Colman Reilly <email>careilly@tcd.ie</email></para>
- </listitem>
-
- <listitem>
- <para>Conrad Sabatier <email>conrads@neosoft.com</email></para>
- </listitem>
-
- <listitem>
- <para>Coranth Gryphon <email>gryphon@healer.com</email></para>
- </listitem>
-
- <listitem>
- <para>Cornelis van der Laan
- <email>nils@guru.ims.uni-stuttgart.de</email></para>
- </listitem>
-
- <listitem>
- <para>Cove Schneider <email>cove@brazil.nbn.com</email></para>
- </listitem>
-
- <listitem>
- <para>Craig Leres <email>leres@ee.lbl.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Craig Loomis <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Craig Metz <email>cmetz@inner.net</email></para>
- </listitem>
-
- <listitem>
- <para>Craig Spannring <email>cts@internetcds.com</email></para>
- </listitem>
-
- <listitem>
- <para>Craig Struble <email>cstruble@vt.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Cristian Ferretti <email>cfs@riemann.mat.puc.cl</email></para>
- </listitem>
-
- <listitem>
- <para>Curt Mayer <email>curt@toad.com</email></para>
- </listitem>
-
- <listitem>
- <para>Cy Schubert <email>cschuber@uumail.gov.bc.ca</email></para>
- </listitem>
-
- <listitem>
- <para>DI. Christian Gusenbauer
- <email>cg@scotty.edvz.uni-linz.ac.at</email></para>
- </listitem>
-
- <listitem>
- <para>Dai Ishijima <email>ishijima@tri.pref.osaka.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Damian Hamill <email>damian@cablenet.net</email></para>
- </listitem>
-
- <listitem>
- <para>Dan Cross <email>tenser@spitfire.ecsel.psu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Dan Lukes <email>dan@obluda.cz</email></para>
- </listitem>
-
- <listitem>
- <para>Dan Nelson <email>dnelson@emsphone.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dan Walters <email>hannibal@cyberstation.net</email></para>
- </listitem>
-
- <listitem>
- <para>Daniel M. Eischen
- <email>deischen@iworks.InterWorks.org</email></para>
- </listitem>
-
- <listitem>
- <para>Daniel O'Connor <email>doconnor@gsoft.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Daniel Poirot <email>poirot@aio.jsc.nasa.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Daniel Rock <email>rock@cs.uni-sb.de</email></para>
- </listitem>
-
- <listitem>
- <para>Danny Egen <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Danny J. Zerkel <email>dzerkel@phofarm.com</email></para>
- </listitem>
-
- <listitem>
- <para>Darren Reed <email>avalon@coombs.anu.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Adkins <email>adkin003@tc.umn.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Andersen <email>angio@aros.net</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Blizzard <email>dblizzar@sprynet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Bodenstab <email>imdave@synet.net</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Burgess <email>burgess@hrd769.brooks.af.mil</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Chapeskie <email>dchapes@ddm.on.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Cornejo <email>dave@dogwood.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Edmondson <email>davided@sco.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Glowacki <email>dglo@ssec.wisc.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Marquardt <email>marquard@austin.ibm.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Tweten <email>tweten@FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>David A. Adkins <email>adkin003@tc.umn.edu</email></para>
- </listitem>
-
- <listitem>
- <para>David A. Bader <email>dbader@umiacs.umd.edu</email></para>
- </listitem>
-
- <listitem>
- <para>David Borman <email>dab@bsdi.com</email></para>
- </listitem>
-
- <listitem>
- <para>David Dawes <email>dawes@XFree86.org</email></para>
- </listitem>
-
- <listitem>
- <para>David Filo <email>filo@yahoo.com</email></para>
- </listitem>
-
- <listitem>
- <para>David Holland <email>dholland@eecs.harvard.edu</email></para>
- </listitem>
-
- <listitem>
- <para>David Holloway <email>daveh@gwythaint.tamis.com</email></para>
- </listitem>
-
- <listitem>
- <para>David Horwitt <email>dhorwitt@ucsd.edu</email></para>
- </listitem>
-
- <listitem>
- <para>David Hovemeyer <email>daveho@infocom.com</email></para>
- </listitem>
-
- <listitem>
- <para>David Jones <email>dej@qpoint.torfree.net</email></para>
- </listitem>
-
- <listitem>
- <para>David Kelly <email>dkelly@tomcat1.tbe.com</email></para>
- </listitem>
-
- <listitem>
- <para>David Kulp <email>dkulp@neomorphic.com</email></para>
- </listitem>
-
- <listitem>
- <para>David L. Nugent <email>davidn@blaze.net.au</email></para>
- </listitem>
-
- <listitem>
- <para>David Leonard <email>d@scry.dstc.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>David Malone <email>dwmalone@maths.tcd.ie</email></para>
- </listitem>
-
- <listitem>
- <para>David Muir Sharnoff <email>muir@idiom.com</email></para>
- </listitem>
-
- <listitem>
- <para>David S. Miller <email>davem@jenolan.rutgers.edu</email></para>
- </listitem>
-
- <listitem>
- <para>David Wolfskill <email>dhw@whistle.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dean Gaudet <email>dgaudet@arctic.org</email></para>
- </listitem>
-
- <listitem>
- <para>Dean Huxley <email>dean@fsa.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Denis Fortin <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Dennis Glatting
- <email>dennis.glatting@software-munitions.com</email></para>
- </listitem>
-
- <listitem>
- <para>Denton Gentry <email>denny1@home.com</email></para>
- </listitem>
-
- <listitem>
- <para>Derek Inksetter <email>derek@saidev.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dima Sivachenko <email>dima@Chg.RU</email></para>
- </listitem>
-
- <listitem>
- <para>Dirk Keunecke <email>dk@panda.rhein-main.de</email></para>
- </listitem>
-
- <listitem>
- <para>Dirk Nehrling <email>nerle@pdv.de</email></para>
- </listitem>
-
- <listitem>
- <para>Dmitry Khrustalev <email>dima@xyzzy.machaon.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Dmitry Kohmanyuk <email>dk@farm.org</email></para>
- </listitem>
-
- <listitem>
- <para>Dom Mitchell <email>dom@myrddin.demon.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Dominik Brettnacher <email>domi@saargate.de</email></para>
- </listitem>
-
- <listitem>
- <para>Don Croyle <email>croyle@gelemna.ft-wayne.in.us</email></para>
- </listitem>
-
- <listitem>
- <para>&a.whiteside;</para>
- </listitem>
-
- <listitem>
- <para>Don Morrison <email>dmorrisn@u.washington.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Don Yuniskis <email>dgy@rtd.com</email></para>
- </listitem>
-
- <listitem>
- <para>Donald Maddox <email>dmaddox@conterra.com</email></para>
- </listitem>
-
- <listitem>
- <para>Doug Barton <email>studded@dal.net</email></para>
- </listitem>
-
- <listitem>
- <para>Douglas Ambrisko <email>ambrisko@whistle.com</email></para>
- </listitem>
-
- <listitem>
- <para>Douglas Carmichael <email>dcarmich@mcs.com</email></para>
- </listitem>
-
- <listitem>
- <para>Douglas Crosher <email>dtc@scrooge.ee.swin.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Drew Derbyshire <email>ahd@kew.com</email></para>
- </listitem>
-
- <listitem>
- <para>Duncan Barclay <email>dmlb@ragnet.demon.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Dustin Sallings <email>dustin@spy.net</email></para>
- </listitem>
-
- <listitem>
- <para>Eckart "Isegrim" Hofmann
- <email>Isegrim@Wunder-Nett.org</email></para>
- </listitem>
-
- <listitem>
- <para>Ed Gold
- <email>vegold01@starbase.spd.louisville.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Ed Hudson <email>elh@p5.spnet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Edward Wang <email>edward@edcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Edwin Groothus <email>edwin@nwm.wan.philips.com</email></para>
- </listitem>
-
- <listitem>
- <para>Eiji-usagi-MATSUmoto <email>usagi@clave.gr.jp</email></para>
- </listitem>
-
- <listitem>
- <para>ELISA Font Project</para>
- </listitem>
-
- <listitem>
- <para>Elmar Bartel
- <email>bartel@informatik.tu-muenchen.de</email></para>
- </listitem>
-
- <listitem>
- <para>Eric A. Griff <email>eagriff@global2000.net</email></para>
- </listitem>
-
- <listitem>
- <para>Eric Blood <email>eblood@cs.unr.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Eric J. Haug <email>ejh@slustl.slu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Eric J. Schwertfeger <email>eric@cybernut.com</email></para>
- </listitem>
-
- <listitem>
- <para>Eric L. Hernes <email>erich@lodgenet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Eric P. Scott <email>eps@sirius.com</email></para>
- </listitem>
-
- <listitem>
- <para>Eric Sprinkle <email>eric@ennovatenetworks.com</email></para>
- </listitem>
-
- <listitem>
- <para>Erich Stefan Boleyn <email>erich@uruk.org</email></para>
- </listitem>
-
- <listitem>
- <para>Erik E. Rantapaa <email>rantapaa@math.umn.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Erik H. Moe <email>ehm@cris.com</email></para>
- </listitem>
-
- <listitem>
- <para>Ernst Winter <email>ewinter@lobo.muc.de</email></para>
- </listitem>
-
- <listitem>
- <para>Espen Skoglund <email>espensk@stud.cs.uit.no></email></para>
- </listitem>
-
- <listitem>
- <para>Eugene M. Kim <email>astralblue@usa.net</email></para>
- </listitem>
-
- <listitem>
- <para>Eugene Radchenko <email>genie@qsar.chem.msu.su</email></para>
- </listitem>
-
- <listitem>
- <para>Evan Champion <email>evanc@synapse.net</email></para>
- </listitem>
-
- <listitem>
- <para>Faried Nawaz <email>fn@Hungry.COM</email></para>
- </listitem>
-
- <listitem>
- <para>Flemming Jacobsen <email>fj@tfs.com</email></para>
- </listitem>
-
- <listitem>
- <para>Fong-Ching Liaw <email>fong@juniper.net</email></para>
- </listitem>
-
- <listitem>
- <para>Francis M J Hsieh <email>mjshieh@life.nthu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Bartels <email>knarf@camelot.de</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Chen Hsiung Chan
- <email>frankch@waru.life.nthu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Durda IV <email>uhclem@nemesis.lonestar.org</email></para>
- </listitem>
-
- <listitem>
- <para>Frank MacLachlan <email>fpm@n2.net</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Mayhar <email>frank@exit.com</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Nobis <email>fn@Radio-do.de</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Volf <email>volf@oasis.IAEhv.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Frank ten Wolde <email>franky@pinewood.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Frank van der Linden <email>frank@fwi.uva.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Fred Cawthorne <email>fcawth@jjarray.umn.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Fred Gilham <email>gilham@csl.sri.com</email></para>
- </listitem>
-
- <listitem>
- <para>Fred Templin <email>templin@erg.sri.com</email></para>
- </listitem>
-
- <listitem>
- <para>Frederick Earl Gray <email>fgray@rice.edu</email></para>
- </listitem>
-
- <listitem>
- <para>FUJIMOTO Kensaku
- <email>fujimoto@oscar.elec.waseda.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>FUJISHIMA Satsuki <email>k5@respo.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>FURUSAWA Kazuhisa
- <email>furusawa@com.cs.osakafu-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Gabor Kincses <email>gabor@acm.org</email></para>
- </listitem>
-
- <listitem>
- <para>Gabor Zahemszky <email>zgabor@CoDe.hu</email></para>
- </listitem>
-
- <listitem>
- <para>G. Adam Stanislav<email>adam@whizkidtech.net</email></para>
- </listitem>
-
- <listitem>
- <para>Garance A Drosehn <email>gad@eclipse.its.rpi.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Gareth McCaughan <email>gjm11@dpmms.cam.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Gary A. Browning <email>gab10@griffcd.amdahl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Gary Howland <email>gary@hotlava.com</email></para>
- </listitem>
-
- <listitem>
- <para>Gary J. <email>garyj@rks32.pcs.dec.com</email></para>
- </listitem>
-
- <listitem>
- <para>Gary Kline <email>kline@thought.org</email></para>
- </listitem>
-
- <listitem>
- <para>Gaspar Chilingarov <email>nightmar@lemming.acc.am</email></para>
- </listitem>
-
- <listitem>
- <para>Gea-Suan Lin <email>gsl@tpts4.seed.net.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Geoff Rehmet <email>csgr@alpha.ru.ac.za</email></para>
- </listitem>
-
- <listitem>
- <para>Georg Wagner <email>georg.wagner@ubs.com</email></para>
- </listitem>
-
- <listitem>
- <para>Gerard Roudier <email>groudier@club-internet.fr</email></para>
- </listitem>
-
- <listitem>
- <para>Gianmarco Giovannelli
- <email>gmarco@giovannelli.it</email></para>
- </listitem>
-
- <listitem>
- <para>Gil Kloepfer Jr. <email>gil@limbic.ssdl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Gilad Rom <email>rom_glsa@ein-hashofet.co.il</email></para>
- </listitem>
-
- <listitem>
- <para>Ginga Kawaguti
- <email>ginga@amalthea.phys.s.u-tokyo.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Giles Lean <email>giles@nemeton.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Glen Foster <email>gfoster@gfoster.com</email></para>
- </listitem>
-
- <listitem>
- <para>Glenn Johnson <email>gljohns@bellsouth.net</email></para>
- </listitem>
-
- <listitem>
- <para>Godmar Back <email>gback@facility.cs.utah.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Goran Hammarback <email>goran@astro.uu.se</email></para>
- </listitem>
-
- <listitem>
- <para>Gord Matzigkeit <email>gord@enci.ucalgary.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Gordon Greeff <email>gvg@uunet.co.za</email></para>
- </listitem>
-
- <listitem>
- <para>Graham Wheeler <email>gram@cdsec.com</email></para>
- </listitem>
-
- <listitem>
- <para>Greg A. Woods <email>woods@zeus.leitch.com</email></para>
- </listitem>
-
- <listitem>
- <para>Greg Ansley <email>gja@ansley.com</email></para>
- </listitem>
-
- <listitem>
- <para>Greg Troxel <email>gdt@ir.bbn.com</email></para>
- </listitem>
-
- <listitem>
- <para>Greg Ungerer <email>gerg@stallion.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Gregory Bond <email>gnb@itga.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Gregory D. Moncreaff
- <email>moncrg@bt340707.res.ray.com</email></para>
- </listitem>
-
- <listitem>
- <para>Guy Harris <email>guy@netapp.com</email></para>
- </listitem>
-
- <listitem>
- <para>Guy Helmer <email>ghelmer@cs.iastate.edu</email></para>
- </listitem>
-
- <listitem>
- <para>HAMADA Naoki <email>hamada@astec.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>HONDA Yasuhiro
- <email>honda@kashio.info.mie-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>HOSOBUCHI Noriyuki <email>hoso@buchi.tama.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Hannu Savolainen <email>hannu@voxware.pp.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Hans Huebner <email>hans@artcom.de</email></para>
- </listitem>
-
- <listitem>
- <para>Hans Petter Bieker <email>zerium@webindex.no</email></para>
- </listitem>
-
- <listitem>
- <para>Hans Zuidam <email>hans@brandinnovators.com</email></para>
- </listitem>
-
- <listitem>
- <para>Harlan Stenn <email>Harlan.Stenn@pfcs.com</email></para>
- </listitem>
-
- <listitem>
- <para>Harold Barker <email>hbarker@dsms.com</email></para>
- </listitem>
-
- <listitem>
- <para>Havard Eidnes
- <email>Havard.Eidnes@runit.sintef.no</email></para>
- </listitem>
-
- <listitem>
- <para>Heikki Suonsivu <email>hsu@cs.hut.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Heiko W. Rupp <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Helmut F. Wirth <email>hfwirth@ping.at</email></para>
- </listitem>
-
- <listitem>
- <para>Henrik Vestergaard Draboel
- <email>hvd@terry.ping.dk</email></para>
- </listitem>
-
- <listitem>
- <para>Herb Peyerl <email>hpeyerl@NetBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Hideaki Ohmon <email>ohmon@tom.sfc.keio.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Hidekazu Kuroki <email>hidekazu@cs.titech.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Hideki Yamamoto <email>hyama@acm.org</email></para>
- </listitem>
-
- <listitem>
- <para>Hideyuki Suzuki
- <email>hideyuki@sat.t.u-tokyo.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Hirayama Issei <email>iss@mail.wbs.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Hiroaki Sakai <email>sakai@miya.ee.kagu.sut.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Hiroharu Tamaru <email>tamaru@ap.t.u-tokyo.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Hironori Ikura <email>hikura@kaisei.org</email></para>
- </listitem>
-
- <listitem>
- <para>Hiroshi Nishikawa <email>nis@pluto.dti.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Hiroya Tsubakimoto <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Holger Veit <email>Holger.Veit@gmd.de</email></para>
- </listitem>
-
- <listitem>
- <para>Holm Tiffe <email>holm@geophysik.tu-freiberg.de</email></para>
- </listitem>
-
- <listitem>
- <para>Horance Chou
- <email>horance@freedom.ie.cycu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Horihiro Kumagai <email>kuma@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>HOTARU-YA <email>hotaru@tail.net</email></para>
- </listitem>
-
- <listitem>
- <para>Hr.Ladavac <email>lada@ws2301.gud.siemens.co.at</email></para>
- </listitem>
-
- <listitem>
- <para>Hubert Feyrer <email>hubertf@NetBSD.ORG</email></para>
- </listitem>
-
- <listitem>
- <para>Hugh F. Mahon <email>hugh@nsmdserv.cnd.hp.com</email></para>
- </listitem>
-
- <listitem>
- <para>Hugh Mahon <email>h_mahon@fc.hp.com</email></para>
- </listitem>
-
- <listitem>
- <para>Hung-Chi Chu <email>hcchu@r350.ee.ntu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>IMAI Takeshi <email>take-i@ceres.dti.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>IMAMURA Tomoaki
- <email>tomoak-i@is.aist-nara.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Ian Dowse <email>iedowse@maths.tcd.ie</email></para>
- </listitem>
-
- <listitem>
- <para>Ian Holland <email>ianh@tortuga.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Ian Struble <email>ian@broken.net</email></para>
- </listitem>
-
- <listitem>
- <para>Ian Vaudrey <email>i.vaudrey@bigfoot.com</email></para>
- </listitem>
-
- <listitem>
- <para>Igor Khasilev <email>igor@jabber.paco.odessa.ua</email></para>
- </listitem>
-
- <listitem>
- <para>Igor Roshchin <email>str@giganda.komkon.org</email></para>
- </listitem>
-
- <listitem>
- <para>Igor Sviridov <email>siac@ua.net</email></para>
- </listitem>
-
- <listitem>
- <para>Igor Vinokurov <email>igor@zynaps.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Ikuo Nakagawa <email>ikuo@isl.intec.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Ilya V. Komarov <email>mur@lynx.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Issei Suzuki <email>issei@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Itsuro Saito <email>saito@miv.t.u-tokyo.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>J. Bryant <email>jbryant@argus.flash.net</email></para>
- </listitem>
-
- <listitem>
- <para>J. David Lowe <email>lowe@saturn5.com</email></para>
- </listitem>
-
- <listitem>
- <para>J. Han <email>hjh@best.com</email></para>
- </listitem>
-
- <listitem>
- <para>J. Hawk <email>jhawk@MIT.EDU</email></para>
- </listitem>
-
- <listitem>
- <para>J.T. Conklin <email>jtc@cygnus.com</email></para>
- </listitem>
-
- <listitem>
- <para>J.T. Jang <email>keith@email.gcn.net.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Jack <email>jack@zeus.xtalwind.net</email></para>
- </listitem>
-
- <listitem>
- <para>Jacob Bohn Lorensen <email>jacob@jblhome.ping.mk</email></para>
- </listitem>
-
- <listitem>
- <para>Jagane D Sundar <email>jagane@netcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Jake Burkholder <email>jake@checker.org</email></para>
- </listitem>
-
- <listitem>
- <para>Jake Hamby <email>jehamby@lightside.com</email></para>
- </listitem>
-
- <listitem>
- <para>James Clark <email>jjc@jclark.com</email></para>
- </listitem>
-
- <listitem>
- <para>James D. Stewart <email>jds@c4systm.com</email></para>
- </listitem>
-
- <listitem>
- <para>James Jegers <email>jimj@miller.cs.uwm.edu</email></para>
- </listitem>
-
- <listitem>
- <para>James Raynard
- <email>fhackers@jraynard.demon.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>James T. Liu <email>jtliu@phlebas.rockefeller.edu</email></para>
- </listitem>
-
- <listitem>
- <para>James da Silva <email>jds@cs.umd.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Jan Conard
- <email>charly@fachschaften.tu-muenchen.de</email></para>
- </listitem>
-
- <listitem>
- <para>Jan Koum <email>jkb@FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Janick Taillandier
- <email>Janick.Taillandier@ratp.fr</email></para>
- </listitem>
-
- <listitem>
- <para>Janusz Kokot <email>janek@gaja.ipan.lublin.pl</email></para>
- </listitem>
-
- <listitem>
- <para>Jarle Greipsland <email>jarle@idt.unit.no</email></para>
- </listitem>
-
- <listitem>
- <para>Jason Garman <email>init@risen.org</email></para>
- </listitem>
-
- <listitem>
- <para>Jason Thorpe <email>thorpej@NetBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Jason Wright <email>jason@OpenBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Jason Young
- <email>doogie@forbidden-donut.anet-stl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Javier Martin Rueda <email>jmrueda@diatel.upm.es</email></para>
- </listitem>
-
- <listitem>
- <para>Jay Fenlason <email>hack@datacube.com</email></para>
- </listitem>
-
- <listitem>
- <para>Jaye Mathisen <email>mrcpu@cdsnet.net</email></para>
- </listitem>
-
- <listitem>
- <para>Jeff Bartig <email>jeffb@doit.wisc.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Jeff Forys <email>jeff@forys.cranbury.nj.us</email></para>
- </listitem>
-
- <listitem>
- <para>Jeff Kletsky <email>Jeff@Wagsky.com</email></para>
- </listitem>
-
- <listitem>
- <para>Jeffrey Evans <email>evans@scnc.k12.mi.us</email></para>
- </listitem>
-
- <listitem>
- <para>Jeffrey Wheat <email>jeff@cetlink.net</email></para>
- </listitem>
-
- <listitem>
- <para>Jens Schweikhardt <email>schweikh@noc.dfn.d</email></para>
- </listitem>
-
- <listitem>
- <para>Jeremy Allison <email>jallison@whistle.com</email></para>
- </listitem>
-
- <listitem>
- <para>Jeremy Chatfield <email>jdc@xinside.com</email></para>
- </listitem>
-
- <listitem>
- <para>Jeremy Lea <email>reg@shale.csir.co.za</email></para>
- </listitem>
-
- <listitem>
- <para>Jeremy Prior <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Jeroen Ruigrok/Asmodai <email>asmodai@wxs.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Jesse Rosenstock <email>jmr@ugcs.caltech.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Jian-Da Li <email>jdli@csie.nctu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Jim Babb <email>babb@FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Jim Binkley <email>jrb@cs.pdx.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Jim Carroll <email>jim@carroll.com</email></para>
- </listitem>
-
- <listitem>
- <para>Jim Flowers <email>jflowers@ezo.net</email></para>
- </listitem>
-
- <listitem>
- <para>Jim Leppek <email>jleppek@harris.com</email></para>
- </listitem>
-
- <listitem>
- <para>Jim Lowe <email>james@cs.uwm.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Jim Mattson <email>jmattson@sonic.net</email></para>
- </listitem>
-
- <listitem>
- <para>Jim Mercer <email>jim@komodo.reptiles.org</email></para>
- </listitem>
-
- <listitem>
- <para>Jim Wilson <email>wilson@moria.cygnus.com</email></para>
- </listitem>
-
- <listitem>
- <para>Jimbo Bahooli
- <email>griffin@blackhole.iceworld.org</email></para>
- </listitem>
-
- <listitem>
- <para>Jin Guojun <email>jin@george.lbl.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Joachim Kuebart <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Joao Carlos Mendes Luis <email>jonny@jonny.eng.br</email></para>
- </listitem>
-
- <listitem>
- <para>Jochen Pohl <email>jpo.drs@sni.de</email></para>
- </listitem>
-
- <listitem>
- <para>Joe "Marcus" Clarke <email>marcus@miami.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Joe Abley <email>jabley@clear.co.nz</email></para>
- </listitem>
-
- <listitem>
- <para>Joe Jih-Shian Lu <email>jslu@dns.ntu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Joe Orthoefer <email>j_orthoefer@tia.net</email></para>
- </listitem>
-
- <listitem>
- <para>Joe Traister <email>traister@mojozone.org</email></para>
- </listitem>
-
- <listitem>
- <para>Joel Faedi <email>Joel.Faedi@esial.u-nancy.fr</email></para>
- </listitem>
-
- <listitem>
- <para>Joel Ray Holveck <email>joelh@gnu.org</email></para>
- </listitem>
-
- <listitem>
- <para>Joel Sutton <email>sutton@aardvark.apana.org.au</email></para>
- </listitem>
-
- <listitem>
- <para>Johan Granlund <email>johan@granlund.nu</email></para>
- </listitem>
-
- <listitem>
- <para>Johan Karlsson <email>k@numeri.campus.luth.se</email></para>
- </listitem>
-
- <listitem>
- <para>Johan Larsson <email>johan@moon.campus.luth.se</email></para>
- </listitem>
-
- <listitem>
- <para>Johann Tonsing <email>jtonsing@mikom.csir.co.za</email></para>
- </listitem>
-
- <listitem>
- <para>Johannes Helander <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Johannes Stille <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>John Baldwin <email>jobaldwi@vt.edu</email></para>
- </listitem>
-
- <listitem>
- <para>John Beckett <email>jbeckett@southern.edu</email></para>
- </listitem>
-
- <listitem>
- <para>John Beukema <email>jbeukema@hk.super.net</email></para>
- </listitem>
-
- <listitem>
- <para>John Brezak <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>John Capo <email>jc@irbs.com</email></para>
- </listitem>
-
- <listitem>
- <para>John F. Woods <email>jfw@jfwhome.funhouse.com</email></para>
- </listitem>
-
- <listitem>
- <para>John Goerzen
- <email>jgoerzen@alexanderwohl.complete.org</email></para>
- </listitem>
-
- <listitem>
- <para>John Hay <email>jhay@mikom.csir.co.za</email></para>
- </listitem>
-
- <listitem>
- <para>John Heidemann <email>johnh@isi.edu</email></para>
- </listitem>
-
- <listitem>
- <para>John Hood <email>cgull@owl.org</email></para>
- </listitem>
-
- <listitem>
- <para>John Kohl <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>John Lind <email>john@starfire.mn.org</email></para>
- </listitem>
-
- <listitem>
- <para>John Mackin <email>john@physiol.su.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>John P <email>johnp@lodgenet.com</email></para>
- </listitem>
-
- <listitem>
- <para>John Perry <email>perry@vishnu.alias.net</email></para>
- </listitem>
-
- <listitem>
- <para>John Preisler <email>john@vapornet.com</email></para>
- </listitem>
-
- <listitem>
- <para>John Rochester <email>jr@cs.mun.ca</email></para>
- </listitem>
-
- <listitem>
- <para>John Sadler <email>john_sadler@alum.mit.edu</email></para>
- </listitem>
-
- <listitem>
- <para>John Saunders <email>john@pacer.nlc.net.au</email></para>
- </listitem>
-
- <listitem>
- <para>John W. DeBoskey <email>jwd@unx.sas.com</email></para>
- </listitem>
-
- <listitem>
- <para>John Wehle <email>john@feith.com</email></para>
- </listitem>
-
- <listitem>
- <para>John Woods <email>jfw@eddie.mit.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Jon Morgan <email>morgan@terminus.trailblazer.com</email></para>
- </listitem>
-
- <listitem>
- <para>Jonathan H N Chin <email>jc254@newton.cam.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Jonathan Hanna
- <email>jh@pc-21490.bc.rogers.wave.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Jorge Goncalves <email>j@bug.fe.up.pt</email></para>
- </listitem>
-
- <listitem>
- <para>Jorge M. Goncalves <email>ee96199@tom.fe.up.pt</email></para>
- </listitem>
-
- <listitem>
- <para>Jos Backus <email>jbackus@plex.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Jose M. Alcaide <email>jose@we.lc.ehu.es</email></para>
- </listitem>
-
- <listitem>
- <para>Jose Marques <email>jose@nobody.org</email></para>
- </listitem>
-
- <listitem>
- <para>Josef Grosch
- <email>jgrosch@superior.mooseriver.com</email></para>
- </listitem>
-
- <listitem>
- <para>Josef Karthauser <email>joe@uk.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Joseph Stein <email>joes@wstein.com</email></para>
- </listitem>
-
- <listitem>
- <para>Josh Gilliam <email>josh@quick.net</email></para>
- </listitem>
-
- <listitem>
- <para>Josh Tiefenbach <email>josh@ican.net</email></para>
- </listitem>
-
- <listitem>
- <para>Juergen Lock <email>nox@jelal.hb.north.de</email></para>
- </listitem>
-
- <listitem>
- <para>Juha Inkari <email>inkari@cc.hut.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Jukka A. Ukkonen <email>jua@iki.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Julian Assange <email>proff@suburbia.net</email></para>
- </listitem>
-
- <listitem>
- <para>Julian Coleman <email>j.d.coleman@ncl.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>&a.jhs</para>
- </listitem>
-
- <listitem>
- <para>Julian Jenkins <email>kaveman@magna.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Junichi Satoh <email>junichi@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Junji SAKAI <email>sakai@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Junya WATANABE <email>junya-w@remus.dti.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>K.Higashino <email>a00303@cc.hc.keio.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>KUNISHIMA Takeo <email>kunishi@c.oka-pu.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Kai Vorma <email>vode@snakemail.hut.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Kaleb S. Keithley <email>kaleb@ics.com</email></para>
- </listitem>
-
- <listitem>
- <para>Kaneda Hiloshi <email>vanitas@ma3.seikyou.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Kapil Chowksey <email>kchowksey@hss.hns.com</email></para>
- </listitem>
-
- <listitem>
- <para>Karl Denninger <email>karl@mcs.com</email></para>
- </listitem>
-
- <listitem>
- <para>Karl Dietz <email>Karl.Dietz@triplan.com</email></para>
- </listitem>
-
- <listitem>
- <para>Karl Lehenbauer <email>karl@NeoSoft.com</email></para>
- </listitem>
-
- <listitem>
- <para>Kato Takenori
- <email>kato@eclogite.eps.nagoya-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Kawanobe Koh <email>kawanobe@st.rim.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Kazuhiko Kiriyama <email>kiri@kiri.toba-cmt.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Kazuo Horikawa <email>horikawa@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Kees Jan Koster <email>kjk1@ukc.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Keith Bostic <email>bostic@bostic.com</email></para>
- </listitem>
-
- <listitem>
- <para>Keith E. Walker <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Keith Moore <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Keith Sklower <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Kelly Yancey <email>kbyanc@posi.net</email></para>
- </listitem>
-
- <listitem>
- <para>Ken Hornstein <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Ken Key <email>key@cs.utk.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Ken Mayer <email>kmayer@freegate.com</email></para>
- </listitem>
-
- <listitem>
- <para>Kenji Saito <email>marukun@mx2.nisiq.net</email></para>
- </listitem>
-
- <listitem>
- <para>Kenji Tomita <email>tommyk@da2.so-net.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Kenneth Furge <email>kenneth.furge@us.endress.com</email></para>
- </listitem>
-
- <listitem>
- <para>Kenneth Monville <email>desmo@bandwidth.org</email></para>
- </listitem>
-
- <listitem>
- <para>Kenneth R. Westerback <email>krw@tcn.net</email></para>
- </listitem>
-
- <listitem>
- <para>Kenneth Stailey <email>kstailey@gnu.ai.mit.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Kent Talarico <email>kent@shipwreck.tsoft.net</email></para>
- </listitem>
-
- <listitem>
- <para>Kent Vander Velden <email>graphix@iastate.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Kentaro Inagaki <email>JBD01226@niftyserve.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Kevin Bracey <email>kbracey@art.acorn.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Kevin Day <email>toasty@dragondata.com</email></para>
- </listitem>
-
- <listitem>
- <para>Kevin Lahey <email>kml@nas.nasa.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Kevin Lo<email>kevlo@hello.com.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Kevin Street <email>street@iname.com</email></para>
- </listitem>
-
- <listitem>
- <para>Kevin Van Maren <email>vanmaren@fast.cs.utah.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Kiroh HARADA <email>kiroh@kh.rim.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Klaus Klein <email>kleink@layla.inka.de</email></para>
- </listitem>
-
- <listitem>
- <para>Klaus-J. Wolf <email>Yanestra@t-online.de</email></para>
- </listitem>
-
- <listitem>
- <para>Koichi Sato <email>copan@ppp.fastnet.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Kostya Lukin <email>lukin@okbmei.msk.su</email></para>
- </listitem>
-
- <listitem>
- <para>Kouichi Hirabayashi <email>kh@mogami-wire.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Kurt D. Zeilenga <email>Kurt@Boolean.NET</email></para>
- </listitem>
-
- <listitem>
- <para>Kurt Olsen <email>kurto@tiny.mcs.usu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>L. Jonas Olsson
- <email>ljo@ljo-slip.DIALIN.CWRU.Edu</email></para>
- </listitem>
-
- <listitem>
- <para>Lars K&ouml;ller
- <email>Lars.Koeller@Uni-Bielefeld.DE</email></para>
- </listitem>
-
- <listitem>
- <para>Larry Altneu <email>larry@ALR.COM</email></para>
- </listitem>
-
- <listitem>
- <para>Laurence Lopez <email>lopez@mv.mv.com</email></para>
- </listitem>
-
- <listitem>
- <para>Lee Cremeans <email>lcremean@tidalwave.net</email></para>
- </listitem>
-
- <listitem>
- <para>Liang Tai-hwa
- <email>avatar@www.mmlab.cse.yzu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Lon Willett <email>lon%softt.uucp@math.utah.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Louis A. Mamakos <email>louie@TransSys.COM</email></para>
- </listitem>
-
- <listitem>
- <para>Louis Mamakos <email>loiue@TransSys.com</email></para>
- </listitem>
-
- <listitem>
- <para>Lucas James <email>Lucas.James@ldjpc.apana.org.au</email></para>
- </listitem>
-
- <listitem>
- <para>Lyndon Nerenberg <email>lyndon@orthanc.com</email></para>
- </listitem>
-
- <listitem>
- <para>M.C. Wong <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>MANTANI Nobutaka <email>nobutaka@nobutaka.com</email></para>
- </listitem>
-
- <listitem>
- <para>MIHIRA Sanpei Yoshiro <email>sanpei@sanpei.org</email></para>
- </listitem>
-
- <listitem>
- <para>MITA Yoshio <email>mita@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>MITSUNAGA Noriaki
- <email>mitchy@er.ams.eng.osaka-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>MOROHOSHI Akihiko <email>moro@race.u-tokyo.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Magnus Enbom <email>dot@tinto.campus.luth.se</email></para>
- </listitem>
-
- <listitem>
- <para>Mahesh Neelakanta <email>mahesh@gcomm.com</email></para>
- </listitem>
-
- <listitem>
- <para>Makoto MATSUSHITA <email>matusita@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Makoto WATANABE
- <email>watanabe@zlab.phys.nagoya-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Malte Lance <email>malte.lance@gmx.net</email></para>
- </listitem>
-
- <listitem>
- <para>Manu Iyengar
- <email>iyengar@grunthos.pscwa.psca.com</email></para>
- </listitem>
-
- <listitem>
- <para>Marc Frajola <email>marc@dev.com</email></para>
- </listitem>
-
- <listitem>
- <para>Marc Ramirez <email>mrami@mramirez.sy.yale.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Marc Slemko <email>marcs@znep.com</email></para>
- </listitem>
-
- <listitem>
- <para>Marc van Kempen <email>wmbfmk@urc.tue.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Marc van Woerkom <email>van.woerkom@netcologne.de</email></para>
- </listitem>
-
- <listitem>
- <para>Marcel Moolenaar <email>marcel@scc.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Mario Sergio Fujikawa Ferreira
- <email>lioux@gns.com.br</email></para>
- </listitem>
-
- <listitem>
- <para>Mark Andrews <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Mark Cammidge <email>mark@gmtunx.ee.uct.ac.za</email></para>
- </listitem>
-
- <listitem>
- <para>Mark Diekhans <email>markd@grizzly.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mark Huizer <email>xaa@stack.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Mark J. Taylor <email>mtaylor@cybernet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mark Krentel <email>krentel@rice.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Mark Mayo <email>markm@vmunix.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mark Thompson <email>thompson@tgsoft.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mark Tinguely <email>tinguely@plains.nodak.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Mark Treacy <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Mark Valentine <email>mark@linus.demon.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Martin Birgmeier</para>
- </listitem>
-
- <listitem>
- <para>Martin Ibert <email>mib@ppe.bb-data.de</email></para>
- </listitem>
-
- <listitem>
- <para>Martin Kammerhofer <email>dada@sbox.tu-graz.ac.at</email></para>
- </listitem>
-
- <listitem>
- <para>Martin Renters <email>martin@tdc.on.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Martti Kuparinen
- <email>martti.kuparinen@ericsson.com</email></para>
- </listitem>
-
- <listitem>
- <para>Masachika ISHIZUKA
- <email>ishizuka@isis.min.ntt.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Mas.TAKEMURA <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Masafumi NAKANE <email>max@wide.ad.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Masahiro Sekiguchi
- <email>seki@sysrap.cs.fujitsu.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Masanobu Saitoh <email>msaitoh@spa.is.uec.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Masanori Kanaoka <email>kana@saijo.mke.mei.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Masanori Kiriake <email>seiken@ARGV.AC</email></para>
- </listitem>
-
- <listitem>
- <para>Masatoshi TAMURA
- <email>tamrin@shinzan.kuee.kyoto-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Mats Lofkvist <email>mal@algonet.se</email></para>
- </listitem>
-
- <listitem>
- <para>Matt Bartley <email>mbartley@lear35.cytex.com</email></para>
- </listitem>
-
- <listitem>
- <para>Matt Thomas <email>matt@3am-software.com</email></para>
- </listitem>
-
- <listitem>
- <para>Matt White <email>mwhite+@CMU.EDU</email></para>
- </listitem>
-
- <listitem>
- <para>Matthew C. Mead <email>mmead@Glock.COM</email></para>
- </listitem>
-
- <listitem>
- <para>Matthew Cashdollar <email>mattc@rfcnet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Matthew Flatt <email>mflatt@cs.rice.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Matthew Fuller <email>fullermd@futuresouth.com</email></para>
- </listitem>
-
- <listitem>
- <para>Matthew Stein <email>matt@bdd.net</email></para>
- </listitem>
-
- <listitem>
- <para>Matthias Pfaller <email>leo@dachau.marco.de</email></para>
- </listitem>
-
- <listitem>
- <para>Matthias Scheler <email>tron@netbsd.org</email></para>
- </listitem>
-
- <listitem>
- <para>Mattias Gronlund
- <email>Mattias.Gronlund@sa.erisoft.se</email></para>
- </listitem>
-
- <listitem>
- <para>Mattias Pantzare <email>pantzer@ludd.luth.se</email></para>
- </listitem>
-
- <listitem>
- <para>Maurice Castro
- <email>maurice@planet.serc.rmit.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>Max Euston <email>meuston@jmrodgers.com</email></para>
- </listitem>
-
- <listitem>
- <para>Max Khon <email>fjoe@husky.iclub.nsu.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Maxim Bolotin <email>max@rsu.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Maxim V. Sobolev <email>sobomax@altavista.net</email></para>
- </listitem>
-
- <listitem>
- <para>Micha Class
- <email>michael_class@hpbbse.bbn.hp.com</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Butler <email>imb@scgt.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Butschky <email>butsch@computi.erols.com</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Clay <email>mclay@weareb.org</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Elbel <email>me@FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Galassi <email>nerd@percival.rain.com</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Hancock <email>michaelh@cet.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Hohmuth <email>hohmuth@inf.tu-dresden.de</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Perlman <email>canuck@caam.rice.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Petry <email>petry@netwolf.NetMasters.com</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Reifenberger <email>root@totum.plaut.de</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Sardo <email>jaeger16@yahoo.com</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Searle <email>searle@longacre.demon.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Michal Listos <email>mcl@Amnesiac.123.org</email></para>
- </listitem>
-
- <listitem>
- <para>Michio Karl Jinbo
- <email>karl@marcer.nagaokaut.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Miguel Angel Sagreras
- <email>msagre@cactus.fi.uba.ar</email></para>
- </listitem>
-
- <listitem>
- <para>Mihoko Tanaka <email>m_tonaka@pa.yokogawa.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Mika Nystrom <email>mika@cs.caltech.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Mikael Hybsch <email>micke@dynas.se</email></para>
- </listitem>
-
- <listitem>
- <para>Mikael Karpberg
- <email>karpen@ocean.campus.luth.se</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Del <email>repenting@hotmail.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Durian <email>durian@plutotech.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Durkin <email>mdurkin@tsoft.sf-bay.org</email></para>
- </listitem>
-
- <listitem>
- <para>Mike E. Matsnev <email>mike@azog.cs.msu.su</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Evans <email>mevans@candle.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Grupenhoff <email>kashmir@umiacs.umd.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Hibler <email>mike@marker.cs.utah.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Karels <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Mike McGaughey <email>mmcg@cs.monash.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Meyer <email>mwm@shiva.the-park.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Mitchell <email>mitchell@ref.tfs.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Murphy <email>mrm@alpharel.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Peck <email>mike@binghamton.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Spengler <email>mks@msc.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Mikhail A. Sokolov <email>mishania@demos.su</email></para>
- </listitem>
-
- <listitem>
- <para>Mikhail Teterin <email>mi@aldan.ziplink.net</email></para>
- </listitem>
-
- <listitem>
- <para>Ming-I Hseh <email>PA@FreeBSD.ee.Ntu.edu.TW</email></para>
- </listitem>
-
- <listitem>
- <para>Mitsuru IWASAKI <email>iwasaki@pc.jaring.my</email></para>
- </listitem>
-
- <listitem>
- <para>Mitsuru Yoshida <email>mitsuru@riken.go.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Monte Mitzelfelt <email>monte@gonefishing.org</email></para>
- </listitem>
-
- <listitem>
- <para>Morgan Davis <email>root@io.cts.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mostyn Lewis <email>mostyn@mrl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Motomichi Matsuzaki <email>mzaki@e-mail.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Motoyuki Kasahara <email>m-kasahr@sra.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Motoyuki Konno <email>motoyuki@snipe.rim.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Murray Stokely <email>murray@cdrom.com</email></para>
- </listitem>
-
- <listitem>
- <para>N.G.Smith <email>ngs@sesame.hensa.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>NAGAO Tadaaki <email>nagao@cs.titech.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>NAKAJI Hiroyuki
- <email>nakaji@tutrp.tut.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>NAKAMURA Kazushi <email>nkazushi@highway.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>NAKAMURA Motonori
- <email>motonori@econ.kyoto-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>NIIMI Satoshi <email>sa2c@and.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>NOKUBI Hirotaka <email>h-nokubi@yyy.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Nadav Eiron <email>nadav@barcode.co.il</email></para>
- </listitem>
-
- <listitem>
- <para>Nanbor Wang <email>nw1@cs.wustl.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Naofumi Honda
- <email>honda@Kururu.math.sci.hokudai.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Naoki Hamada <email>nao@tom-yam.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Narvi <email>narvi@haldjas.folklore.ee</email></para>
- </listitem>
-
- <listitem>
- <para>Nathan Ahlstrom <email>nrahlstr@winternet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Nathan Dorfman <email>nathan@rtfm.net</email></para>
- </listitem>
-
- <listitem>
- <para>Neal Fachan <email>kneel@ishiboo.com</email></para>
- </listitem>
-
- <listitem>
- <para>Neil Blakey-Milner <email>nbm@rucus.ru.ac.za</email></para>
- </listitem>
-
- <listitem>
- <para>Niall Smart <email>rotel@indigo.ie</email></para>
- </listitem>
-
- <listitem>
- <para>Nick Barnes <email>Nick.Barnes@pobox.com</email></para>
- </listitem>
-
- <listitem>
- <para>Nick Handel <email>nhandel@NeoSoft.com</email></para>
- </listitem>
-
- <listitem>
- <para>Nick Hilliard <email>nick@foobar.org</email></para>
- </listitem>
-
- <listitem>
- <para>&a.nsayer;</para>
- </listitem>
-
- <listitem>
- <para>Nick Williams <email>njw@cs.city.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Nickolay N. Dudorov <email>nnd@itfs.nsk.su</email></para>
- </listitem>
-
- <listitem>
- <para>Niklas Hallqvist <email>niklas@filippa.appli.se</email></para>
- </listitem>
-
- <listitem>
- <para>Nisha Talagala <email>nisha@cs.berkeley.edu</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>ZW6T-KND@j.asahi-net.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>adrian@virginia.edu</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>alex@elvisti.kiev.ua</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>anto@netscape.net</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>bobson@egg.ics.nitch.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>bovynf@awe.be</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>burg@is.ge.com</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>chris@gnome.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>colsen@usa.net</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>coredump@nervosa.com</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>dannyman@arh0300.urh.uiuc.edu</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>davids@SECNET.COM</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>derek@free.org</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>devet@adv.IAEhv.nl</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>djv@bedford.net</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>dvv@sprint.net</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>enami@ba2.so-net.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>flash@eru.tubank.msk.su</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>flash@hway.ru</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>fn@pain.csrv.uidaho.edu</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>gclarkii@netport.neosoft.com</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>gordon@sheaky.lonestar.org</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>graaf@iae.nl</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>greg@greg.rim.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>grossman@cygnus.com</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>gusw@fub46.zedat.fu-berlin.de</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>hfir@math.rochester.edu</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>hnokubi@yyy.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>iaint@css.tuu.utas.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>invis@visi.com</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>ishisone@sra.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>iverson@lionheart.com</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>jpt@magic.net</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>junker@jazz.snu.ac.kr</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>k-sugyou@ccs.mt.nec.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>kenji@reseau.toyonaka.osaka.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>kfurge@worldnet.att.net</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>lh@aus.org</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>lhecking@nmrc.ucc.ie</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>mrgreen@mame.mu.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>nakagawa@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>ohki@gssm.otsuka.tsukuba.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>owaki@st.rim.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>pechter@shell.monmouth.com</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>pete@pelican.pelican.com</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>pritc003@maroon.tc.umn.edu</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>risner@stdio.com</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>roman@rpd.univ.kiev.ua</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>root@ns2.redline.ru</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>root@uglabgw.ug.cs.sunysb.edu</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>stephen.ma@jtec.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>sumii@is.s.u-tokyo.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>takas-su@is.aist-nara.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>tamone@eig.unige.ch</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>tjevans@raleigh.ibm.com</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>tony-o@iij.ad.jp amurai@spec.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>torii@tcd.hitachi.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>uenami@imasy.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>uhlar@netlab.sk</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>vode@hut.fi</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>wlloyd@mpd.ca</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>wlr@furball.wellsfargo.com</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>wmbfmk@urc.tue.nl</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>yamagata@nwgpc.kek.jp</email></para>
- </listitem>
-
- <listitem>
- <para>No Name <email>ziggy@ryan.org</email></para>
- </listitem>
-
- <listitem>
- <para>Nobuhiro Yasutomi <email>nobu@psrc.isac.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Nobuyuki Koganemaru
- <email>kogane@koganemaru.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Norio Suzuki <email>nosuzuki@e-mail.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Noritaka Ishizumi <email>graphite@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Noriyuki Soda <email>soda@sra.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Oh Junseon <email>hollywar@mail.holywar.net</email></para>
- </listitem>
-
- <listitem>
- <para>Olaf Wagner <email>wagner@luthien.in-berlin.de</email></para>
- </listitem>
-
- <listitem>
- <para>Oleg Sharoiko <email>os@rsu.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Oleg V. Volkov <email>rover@lglobus.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Oliver Breuninger <email>ob@seicom.NET</email></para>
- </listitem>
-
- <listitem>
- <para>Oliver Friedrichs <email>oliver@secnet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Oliver Fromme
- <email>oliver.fromme@heim3.tu-clausthal.de</email></para>
- </listitem>
-
- <listitem>
- <para>Oliver Laumann
- <email>net@informatik.uni-bremen.de</email></para>
- </listitem>
-
- <listitem>
- <para>Oliver Oberdorf <email>oly@world.std.com</email></para>
- </listitem>
-
- <listitem>
- <para>Olof Johansson <email>offe@ludd.luth.se</email></para>
- </listitem>
-
- <listitem>
- <para>Osokin Sergey aka oZZ <email>ozz@FreeBSD.org.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Pace Willisson <email>pace@blitz.com</email></para>
- </listitem>
-
- <listitem>
- <para>Paco Rosich <email>rosich@modico.eleinf.uv.es</email></para>
- </listitem>
-
- <listitem>
- <para>Palle Girgensohn <email>girgen@partitur.se</email></para>
- </listitem>
-
- <listitem>
- <para>Parag Patel <email>parag@cgt.com</email></para>
- </listitem>
-
- <listitem>
- <para>Pascal Pederiva <email>pascal@zuo.dec.com</email></para>
- </listitem>
-
- <listitem>
- <para>Pasvorn Boonmark <email>boonmark@juniper.net</email></para>
- </listitem>
-
- <listitem>
- <para>Patrick Gardella <email>patrick@cre8tivegroup.com</email></para>
- </listitem>
-
- <listitem>
- <para>Patrick Hausen <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Antonov <email>apg@demos.su</email></para>
- </listitem>
-
- <listitem>
- <para>Paul F. Werkowski <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Fox <email>pgf@foxharp.boston.ma.us</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Koch <email>koch@thehub.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Kranenburg <email>pk@NetBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Mackerras <email>paulus@cs.anu.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Popelka <email>paulp@uts.amdahl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Paul S. LaFollette, Jr. <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Saab <email>paul@mu.org</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Sandys <email>myj@nyct.net</email></para>
- </listitem>
-
- <listitem>
- <para>Paul T. Root <email>proot@horton.iaces.com</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Vixie <email>paul@vix.com</email></para>
- </listitem>
-
- <listitem>
- <para>Paulo Menezes <email>paulo@isr.uc.pt</email></para>
- </listitem>
-
- <listitem>
- <para>Paulo Menezes <email>pm@dee.uc.pt</email></para>
- </listitem>
-
- <listitem>
- <para>Pedro A M Vazquez <email>vazquez@IQM.Unicamp.BR</email></para>
- </listitem>
-
- <listitem>
- <para>Pedro Giffuni <email>giffunip@asme.org</email></para>
- </listitem>
-
- <listitem>
- <para>Pete Bentley <email>pete@demon.net</email></para>
- </listitem>
-
- <listitem>
- <para>Peter Childs <email>pjchilds@imforei.apana.org.au</email></para>
- </listitem>
-
- <listitem>
- <para>Peter Cornelius <email>pc@inr.fzk.de</email></para>
- </listitem>
-
- <listitem>
- <para>Peter Haight <email>peterh@prognet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Peter Jeremy <email>perer.jeremy@alcatel.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Peter M. Chen <email>pmchen@eecs.umich.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Peter Much <email>peter@citylink.dinoex.sub.org</email></para>
- </listitem>
-
- <listitem>
- <para>Peter Olsson <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Peter Philipp <email>pjp@bsd-daemon.net</email></para>
- </listitem>
-
- <listitem>
- <para>Peter Stubbs <email>PETERS@staidan.qld.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>Phil Maker <email>pjm@cs.ntu.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>Phil Sutherland
- <email>philsuth@mycroft.dialix.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Phil Taylor <email>phil@zipmail.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Philip Musumeci <email>philip@rmit.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>Pierre Y. Dampure <email>pierre.dampure@k2c.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Pius Fischer <email>pius@ienet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Pomegranate <email>daver@flag.blackened.net</email></para>
- </listitem>
-
- <listitem>
- <para>Powerdog Industries
- <email>kevin.ruddy@powerdog.com</email></para>
- </listitem>
-
- <listitem>
- <para>R. Kym Horsell</para>
- </listitem>
-
- <listitem>
- <para>Rajesh Vaidheeswarran <email>rv@fore.com</email></para>
- </listitem>
-
- <listitem>
- <para>Ralf Friedl <email>friedl@informatik.uni-kl.de</email></para>
- </listitem>
-
- <listitem>
- <para>Randal S. Masutani <email>randal@comtest.com</email></para>
- </listitem>
-
- <listitem>
- <para>Randall Hopper <email>rhh@ct.picker.com</email></para>
- </listitem>
-
- <listitem>
- <para>Randall W. Dean <email>rwd@osf.org</email></para>
- </listitem>
-
- <listitem>
- <para>Randy Bush <email>rbush@bainbridge.verio.net</email></para>
- </listitem>
-
- <listitem>
- <para>Reinier Bezuidenhout
- <email>rbezuide@mikom.csir.co.za</email></para>
- </listitem>
-
- <listitem>
- <para>Remy Card <email>Remy.Card@masi.ibp.fr</email></para>
- </listitem>
-
- <listitem>
- <para>Ricardas Cepas <email>rch@richard.eu.org</email></para>
- </listitem>
-
- <listitem>
- <para>Riccardo Veraldi <email>veraldi@cs.unibo.it</email></para>
- </listitem>
-
- <listitem>
- <para>Richard Henderson <email>richard@atheist.tamu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Richard Hwang <email>rhwang@bigpanda.com</email></para>
- </listitem>
-
- <listitem>
- <para>Richard Kiss <email>richard@homemail.com</email></para>
- </listitem>
-
- <listitem>
- <para>Richard J Kuhns <email>rjk@watson.grauel.com</email></para>
- </listitem>
-
- <listitem>
- <para>Richard M. Neswold
- <email>rneswold@drmemory.fnal.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Richard Seaman, Jr. <email>dick@tar.com</email></para>
- </listitem>
-
- <listitem>
- <para>Richard Stallman <email>rms@gnu.ai.mit.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Richard Straka <email>straka@user1.inficad.com</email></para>
- </listitem>
-
- <listitem>
- <para>Richard Tobin <email>richard@cogsci.ed.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Richard Wackerbarth <email>rkw@Dataplex.NET</email></para>
- </listitem>
-
- <listitem>
- <para>Richard Winkel <email>rich@math.missouri.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Richard Wiwatowski <email>rjwiwat@adelaide.on.net</email></para>
- </listitem>
-
- <listitem>
- <para>Rick Macklem <email>rick@snowhite.cis.uoguelph.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Rick Macklin <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Rob Austein <email>sra@epilogue.com</email></para>
- </listitem>
-
- <listitem>
- <para>Rob Mallory <email>rmallory@qualcomm.com</email></para>
- </listitem>
-
- <listitem>
- <para>Rob Snow <email>rsnow@txdirect.net</email></para>
- </listitem>
-
- <listitem>
- <para>Robert Crowe <email>bob@speakez.com</email></para>
- </listitem>
-
- <listitem>
- <para>Robert D. Thrush <email>rd@phoenix.aii.com</email></para>
- </listitem>
-
- <listitem>
- <para>Robert Eckardt
- <email>roberte@MEP.Ruhr-Uni-Bochum.de</email></para>
- </listitem>
-
- <listitem>
- <para>Robert Sanders <email>rsanders@mindspring.com</email></para>
- </listitem>
-
- <listitem>
- <para>Robert Sexton <email>robert@kudra.com</email></para>
- </listitem>
-
- <listitem>
- <para>Robert Shady <email>rls@id.net</email></para>
- </listitem>
-
- <listitem>
- <para>Robert Swindells <email>swindellsr@genrad.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Robert Watson <email>robert@cyrus.watson.org</email></para>
- </listitem>
-
- <listitem>
- <para>Robert Withrow <email>witr@rwwa.com</email></para>
- </listitem>
-
- <listitem>
- <para>Robert Yoder <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Robin Carey
- <email>robin@mailgate.dtc.rankxerox.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Roger Hardiman <email>roger@cs.strath.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Roland Jesse <email>jesse@cs.uni-magdeburg.de</email></para>
- </listitem>
-
- <listitem>
- <para>Ron Bickers <email>rbickers@intercenter.net</email></para>
- </listitem>
-
- <listitem>
- <para>Ron Lenk <email>rlenk@widget.xmission.com</email></para>
- </listitem>
-
- <listitem>
- <para>Ronald Kuehn <email>kuehn@rz.tu-clausthal.de</email></para>
- </listitem>
-
- <listitem>
- <para>Rudolf Cejka <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Ruslan Belkin <email>rus@home2.UA.net</email></para>
- </listitem>
-
- <listitem>
- <para>Ruslan Ermilov <email>ru@ucb.crimea.ua</email></para>
- </listitem>
-
- <listitem>
- <para>Ruslan Shevchenko <email>rssh@cam.grad.kiev.ua</email></para>
- </listitem>
-
- <listitem>
- <para>Russell L. Carter <email>rcarter@pinyon.org</email></para>
- </listitem>
-
- <listitem>
- <para>Russell Vincent <email>rv@groa.uct.ac.za</email></para>
- </listitem>
-
- <listitem>
- <para>Ryan Younce <email>ryany@pobox.com</email></para>
- </listitem>
-
- <listitem>
- <para>Ryuichiro IMURA <email>imura@cs.titech.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>SANETO Takanori <email>sanewo@strg.sony.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>SAWADA Mizuki <email>miz@qb3.so-net.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>SUGIMURA Takashi <email>sugimura@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>SURANYI Peter
- <email>suranyip@jks.is.tsukuba.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Sakai Hiroaki <email>sakai@miya.ee.kagu.sut.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Sakari Jalovaara <email>sja@tekla.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Sam Hartman <email>hartmans@mit.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Samuel Lam <email>skl@ScalableNetwork.com</email></para>
- </listitem>
-
- <listitem>
- <para>Samuele Zannoli <email>zannoli@cs.unibo.it</email></para>
- </listitem>
-
- <listitem>
- <para>Sander Vesik <email>sander@haldjas.folklore.ee</email></para>
- </listitem>
-
- <listitem>
- <para>Sandro Sigala <email>ssigala@globalnet.it</email></para>
- </listitem>
-
- <listitem>
- <para>Sascha Blank <email>blank@fox.uni-trier.de</email></para>
- </listitem>
-
- <listitem>
- <para>Sascha Wildner <email>swildner@channelz.GUN.de</email></para>
- </listitem>
-
- <listitem>
- <para>Satoh Junichi <email>junichi@astec.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Scot Elliott <email>scot@poptart.org</email></para>
- </listitem>
-
- <listitem>
- <para>Scot W. Hetzel <email>hetzels@westbend.net</email></para>
- </listitem>
-
- <listitem>
- <para>Scott A. Kenney <email>saken@rmta.ml.org</email></para>
- </listitem>
-
- <listitem>
- <para>Scott Blachowicz
- <email>scott.blachowicz@seaslug.org</email></para>
- </listitem>
-
- <listitem>
- <para>Scott Burris <email>scott@pita.cns.ucla.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Scott Hazen Mueller <email>scott@zorch.sf-bay.org</email></para>
- </listitem>
-
- <listitem>
- <para>Scott Michel <email>scottm@cs.ucla.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Scott Mitchel <email>scott@uk.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Scott Reynolds <email>scott@clmqt.marquette.mi.us</email></para>
- </listitem>
-
- <listitem>
- <para>Sebastian Strollo <email>seb@erix.ericsson.se</email></para>
- </listitem>
-
- <listitem>
- <para>Serge A. Babkin <email>babkin@hq.icb.chel.su</email></para>
- </listitem>
-
- <listitem>
- <para>Serge V. Vakulenko <email>vak@zebub.msk.su</email></para>
- </listitem>
-
- <listitem>
- <para>Sergei Chechetkin
- <email>csl@whale.sunbay.crimea.ua</email></para>
- </listitem>
-
- <listitem>
- <para>Sergei S. Laskavy <email>laskavy@pc759.cs.msu.su</email></para>
- </listitem>
-
- <listitem>
- <para>Sergey Gershtein <email>sg@mplik.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Sergey Kosyakov <email>ks@itp.ac.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Sergey Potapov <email>sp@alkor.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Sergey Shkonda <email>serg@bcs.zp.ua</email></para>
- </listitem>
-
- <listitem>
- <para>Sergey V.Dorokhov <email>svd@kbtelecom.nalnet.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Sergio Lenzi <email>lenzi@bsi.com.br</email></para>
- </listitem>
-
- <listitem>
- <para>Shaun Courtney <email>shaun@emma.eng.uct.ac.za</email></para>
- </listitem>
-
- <listitem>
- <para>Shawn M. Carey <email>smcarey@mailbox.syr.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Shigio Yamaguchi <email>shigio@tamacom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Shinya Esu <email>esu@yk.rim.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Shuichi Tanaka <email>stanaka@bb.mbn.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Shunsuke Akiyama <email>akiyama@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Simon <email>simon@masi.ibp.fr</email></para>
- </listitem>
-
- <listitem>
- <para>Simon Burge <email>simonb@telstra.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Simon J Gerraty <email>sjg@melb.bull.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Simon Marlow <email>simonm@dcs.gla.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Simon Shapiro <email>shimon@simon-shapiro.org</email></para>
- </listitem>
-
- <listitem>
- <para>Sin'ichiro MIYATANI <email>siu@phaseone.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Slaven Rezic <email>eserte@cs.tu-berlin.de</email></para>
- </listitem>
-
- <listitem>
- <para>Soochon Radee <email>slr@mitre.org</email></para>
- </listitem>
-
- <listitem>
- <para>Soren Dayton <email>csdayton@midway.uchicago.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Soren Dossing <email>sauber@netcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Soren S. Jorvang <email>soren@dt.dk</email></para>
- </listitem>
-
- <listitem>
- <para>Stefan Bethke <email>stb@hanse.de</email></para>
- </listitem>
-
- <listitem>
- <para>Stefan Eggers <email>seggers@semyam.dinoco.de</email></para>
- </listitem>
-
- <listitem>
- <para>Stefan Moeding <email>s.moeding@ndh.net</email></para>
- </listitem>
-
- <listitem>
- <para>Stefan Petri <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Stefan `Sec` Zehl <email>sec@42.org</email></para>
- </listitem>
-
- <listitem>
- <para>Steinar Haug <email>sthaug@nethelp.no</email></para>
- </listitem>
-
- <listitem>
- <para>Stephane E. Potvin <email>sepotvin@videotron.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Stephane Legrand <email>stephane@lituus.fr</email></para>
- </listitem>
-
- <listitem>
- <para>Stephen Clawson
- <email>sclawson@marker.cs.utah.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Stephen F. Combs <email>combssf@salem.ge.com</email></para>
- </listitem>
-
- <listitem>
- <para>Stephen Farrell <email>stephen@farrell.org</email></para>
- </listitem>
-
- <listitem>
- <para>Stephen Hocking <email>sysseh@devetir.qld.gov.au</email></para>
- </listitem>
-
- <listitem>
- <para>Stephen J. Roznowski <email>sjr@home.net</email></para>
- </listitem>
-
- <listitem>
- <para>Stephen McKay <email>syssgm@devetir.qld.gov.au</email></para>
- </listitem>
-
- <listitem>
- <para>Stephen Melvin <email>melvin@zytek.com</email></para>
- </listitem>
-
- <listitem>
- <para>Steve Bauer <email>sbauer@rock.sdsmt.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Steve Coltrin <email>spcoltri@io.com</email></para>
- </listitem>
-
- <listitem>
- <para>Steve Deering <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Steve Gerakines <email>steve2@genesis.tiac.net</email></para>
- </listitem>
-
- <listitem>
- <para>Steve Gericke <email>steveg@comtrol.com</email></para>
- </listitem>
-
- <listitem>
- <para>Steve Piette <email>steve@simon.chi.il.US</email></para>
- </listitem>
-
- <listitem>
- <para>Steve Schwarz <email>schwarz@alpharel.com</email></para>
- </listitem>
-
- <listitem>
- <para>Steven G. Kargl
- <email>kargl@troutmask.apl.washington.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Steven H. Samorodin <email>samorodi@NUXI.com</email></para>
- </listitem>
-
- <listitem>
- <para>Steven McCanne <email>mccanne@cs.berkeley.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Steven Plite <email>splite@purdue.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Steven Wallace <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Stuart Henderson
- <email>stuart@internationalschool.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Sue Blake <email>sue@welearn.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Sugimoto Sadahiro <email>ixtl@komaba.utmc.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Sugiura Shiro <email>ssugiura@duo.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Sujal Patel <email>smpatel@wam.umd.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Sune Stjerneby <email>stjerneby@usa.net</email></para>
- </listitem>
-
- <listitem>
- <para>Suzuki Yoshiaki
- <email>zensyo@ann.tama.kawasaki.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Tadashi Kumano <email>kumano@strl.nhk.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Taguchi Takeshi <email>taguchi@tohoku.iij.ad.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Takahiro Yugawa <email>yugawa@orleans.rim.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Takanori Watanabe
- <email>takawata@shidahara1.planet.sci.kobe-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Takashi Mega <email>mega@minz.org</email></para>
- </listitem>
-
- <listitem>
- <para>Takashi Uozu <email>j1594016@ed.kagu.sut.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Takayuki Ariga <email>a00821@cc.hc.keio.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Takeru NAIKI <email>naiki@bfd.es.hokudai.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Takeshi Amaike <email>amaike@iri.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Takeshi MUTOH <email>mutoh@info.nara-k.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Takeshi Ohashi
- <email>ohashi@mickey.ai.kyutech.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Takeshi WATANABE
- <email>watanabe@crayon.earth.s.kobe-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Takuya SHIOZAKI
- <email>tshiozak@makino.ise.chuo-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Tatoku Ogaito <email>tacha@tera.fukui-med.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Tatsumi HOSOKAWA <email>hosokawa@jp.FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Ted Buswell <email>tbuswell@mediaone.net</email></para>
- </listitem>
-
- <listitem>
- <para>Ted Faber <email>faber@isi.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Ted Lemon <email>mellon@isc.org</email></para>
- </listitem>
-
- <listitem>
- <para>Terry Lambert <email>terry@lambert.org</email></para>
- </listitem>
-
- <listitem>
- <para>Terry Lee <email>terry@uivlsi.csl.uiuc.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Tetsuya Furukawa <email>tetsuya@secom-sis.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Theo de Raadt <email>deraadt@OpenBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas <email>thomas@mathematik.uni-Bremen.de</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas D. Dean <email>tomdean@ix.netcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas David Rivers <email>rivers@dignus.com</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas G. McWilliams <email>tgm@netcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas Gellekum
- <email>thomas@ghpc8.ihf.rwth-aachen.de</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas Graichen
- <email>graichen@omega.physik.fu-berlin.de</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas K&ouml;nig
- <email>Thomas.Koenig@ciw.uni-karlsruhe.de</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas Ptacek <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas A. Stephens <email>tas@stephens.org</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas Stromberg <email>tstrombe@rtci.com</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas Valentino Crimi
- <email>tcrimi+@andrew.cmu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Thomas Wintergerst <email>thomas@lemur.nord.de</email></para>
- </listitem>
-
- <listitem>
- <para>&THORN;&oacute;r&eth;ur &Iacute;varsson
- <email>totii@est.is</email></para>
- </listitem>
-
- <listitem>
- <para>Tim Kientzle <email>kientzle@netcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Tim Singletary
- <email>tsingle@sunland.gsfc.nasa.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Tim Wilkinson <email>tim@sarc.city.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Timo J. Rinne <email>tri@iki.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Todd Miller <email>millert@openbsd.org</email></para>
- </listitem>
-
- <listitem>
- <para>Tom <email>root@majestix.cmr.no</email></para>
- </listitem>
-
- <listitem>
- <para>Tom <email>tom@sdf.com</email></para>
- </listitem>
-
- <listitem>
- <para>Tom Gray - DCA <email>dcasba@rain.org</email></para>
- </listitem>
-
- <listitem>
- <para>Tom Jobbins <email>tom@tom.tj</email></para>
- </listitem>
-
- <listitem>
- <para>Tom Pusateri <email>pusateri@juniper.net</email></para>
- </listitem>
-
- <listitem>
- <para>Tom Rush <email>tarush@mindspring.com</email></para>
- </listitem>
-
- <listitem>
- <para>Tom Samplonius <email>tom@misery.sdf.com</email></para>
- </listitem>
-
- <listitem>
- <para>Tomohiko Kurahashi
- <email>kura@melchior.q.t.u-tokyo.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Tony Kimball <email>alk@Think.COM</email></para>
- </listitem>
-
- <listitem>
- <para>Tony Li <email>tli@jnx.com</email></para>
- </listitem>
-
- <listitem>
- <para>Tony Lynn <email>wing@cc.nsysu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Tony Maher <email>tonym@angis.org.au</email></para>
- </listitem>
-
- <listitem>
- <para>Torbjorn Granlund <email>tege@matematik.su.se</email></para>
- </listitem>
-
- <listitem>
- <para>Toshihiko ARAI <email>toshi@tenchi.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Toshihiko SHIMOKAWA <email>toshi@tea.forus.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Toshihiro Kanda <email>candy@kgc.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Toshiomi Moriki
- <email>Toshiomi.Moriki@ma1.seikyou.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Trefor S. <email>trefor@flevel.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Trevor Blackwell <email>tlb@viaweb.com</email></para>
- </listitem>
-
- <listitem>
- <para>URATA Shuichiro <email>s-urata@nmit.tmg.nec.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Udo Schweigert <email>ust@cert.siemens.de</email></para>
- </listitem>
-
- <listitem>
- <para>Ugo Paternostro <email>paterno@dsi.unifi.it</email></para>
- </listitem>
-
- <listitem>
- <para>Ulf Kieber <email>kieber@sax.de</email></para>
- </listitem>
-
- <listitem>
- <para>Ulli Linzen <email>ulli@perceval.camelot.de</email></para>
- </listitem>
-
- <listitem>
- <para>Ustimenko Semen <email>semen@iclub.nsu.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Uwe Arndt <email>arndt@mailhost.uni-koblenz.de</email></para>
- </listitem>
-
- <listitem>
- <para>Vadim Chekan <email>vadim@gc.lviv.ua</email></para>
- </listitem>
-
- <listitem>
- <para>Vadim Kolontsov <email>vadim@tversu.ac.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Vadim Mikhailov <email>mvp@braz.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Van Jacobson <email>van@ee.lbl.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Vasily V. Grechishnikov
- <email>bazilio@ns1.ied-vorstu.ac.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Vasim Valejev <email>vasim@uddias.diaspro.com</email></para>
- </listitem>
-
- <listitem>
- <para>Vernon J. Schryver <email>vjs@mica.denver.sgi.com</email></para>
- </listitem>
-
- <listitem>
- <para>Vic Abell <email>abe@cc.purdue.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Ville Eerola <email>ve@sci.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Vincent Poy <email>vince@venus.gaianet.net</email></para>
- </listitem>
-
- <listitem>
- <para>Vincenzo Capuano
- <email>VCAPUANO@vmprofs.esoc.esa.de</email></para>
- </listitem>
-
- <listitem>
- <para>Virgil Champlin <email>champlin@pa.dec.com</email></para>
- </listitem>
-
- <listitem>
- <para>Vladimir A. Jakovenko
- <email>vovik@ntu-kpi.kiev.ua</email></para>
- </listitem>
-
- <listitem>
- <para>Vladimir Kushnir <email>kushn@mail.kar.net</email></para>
- </listitem>
-
- <listitem>
- <para>Vsevolod Lobko <email>seva@alex-ua.com</email></para>
- </listitem>
-
- <listitem>
- <para>W. Gerald Hicks <email>wghicks@bellsouth.net</email></para>
- </listitem>
-
- <listitem>
- <para>W. Richard Stevens <email>rstevens@noao.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Walt Howard <email>howard@ee.utah.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Warren Toomey <email>wkt@csadfa.cs.adfa.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Wayne Scott <email>wscott@ichips.intel.com</email></para>
- </listitem>
-
- <listitem>
- <para>Werner Griessl
- <email>werner@btp1da.phy.uni-bayreuth.de</email></para>
- </listitem>
-
- <listitem>
- <para>Wes Santee <email>wsantee@wsantee.oz.net</email></para>
- </listitem>
-
- <listitem>
- <para>Wietse Venema <email>wietse@wzv.win.tue.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Wilfredo Sanchez <email>wsanchez@apple.com</email></para>
- </listitem>
-
- <listitem>
- <para>Wiljo Heinen <email>wiljo@freeside.ki.open.de</email></para>
- </listitem>
-
- <listitem>
- <para>Wilko Bulte <email>wilko@yedi.iaf.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Will Andrews <email>andrews@technologist.com</email></para>
- </listitem>
-
- <listitem>
- <para>Willem Jan Withagen <email>wjw@surf.IAE.nl</email></para>
- </listitem>
-
- <listitem>
- <para>William Jolitz <email>withheld</email></para>
- </listitem>
-
- <listitem>
- <para>William Liao <email>william@tale.net</email></para>
- </listitem>
-
- <listitem>
- <para>Wojtek Pilorz
- <email>wpilorz@celebris.bdk.lublin.pl</email></para>
- </listitem>
-
- <listitem>
- <para>Wolfgang Helbig <email>helbig@ba-stuttgart.de</email></para>
- </listitem>
-
- <listitem>
- <para>Wolfgang Solfrank <email>ws@tools.de</email></para>
- </listitem>
-
- <listitem>
- <para>Wolfgang Stanglmeier <email>wolf@FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Wu Ching-hong <email>woju@FreeBSD.ee.Ntu.edu.TW</email></para>
- </listitem>
-
- <listitem>
- <para>Yarema <email>yds@ingress.com</email></para>
- </listitem>
-
- <listitem>
- <para>Yaroslav Terletsky <email>ts@polynet.lviv.ua</email></para>
- </listitem>
-
- <listitem>
- <para>Yasuhito FUTATSUKI <email>futatuki@fureai.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Yasuhiro Fukama <email>yasuf@big.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Yen-Shuo Su <email>yssu@CCCA.NCTU.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Ying-Chieh Liao <email>ijliao@csie.NCTU.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Yixin Jin <email>yjin@rain.cs.ucla.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Yoshiaki Uchikawa <email>yoshiaki@kt.rim.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Yoshihiko OHTA <email>yohta@bres.tsukuba.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Yoshihisa NAKAGAWA
- <email>y-nakaga@ccs.mt.nec.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Yoshikazu Goto <email>gotoh@ae.anritsu.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Yoshimasa Ohnishi
- <email>ohnishi@isc.kyutech.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Yoshishige Arai <email>ryo2@on.rim.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Yuichi MATSUTAKA <email>matutaka@osa.att.ne.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Yujiro MIYATA
- <email>miyata@bioele.nuee.nagoya-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Yukihiro Nakai <email>nacai@iname.com</email></para>
- </listitem>
-
- <listitem>
- <para>Yusuke Nawano <email>azuki@azkey.org</email></para>
- </listitem>
-
- <listitem>
- <para>Yuu Yashiki <email>s974123@cc.matsuyama-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Yuval Yarom <email>yval@cs.huji.ac.il</email></para>
- </listitem>
-
- <listitem>
- <para>Yves Fonk <email>yves@cpcoup5.tn.tudelft.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Yves Fonk <email>yves@dutncp8.tn.tudelft.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Zach Heilig <email>zach@gaffaneys.com</email></para>
- </listitem>
-
- <listitem>
- <para>Zahemszhky Gabor <email>zgabor@code.hu</email></para>
- </listitem>
-
- <listitem>
- <para>Zhong Ming-Xun <email>zmx@mail.CDPA.nsysu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>arci <email>vega@sophia.inria.fr</email></para>
- </listitem>
-
- <listitem>
- <para>der Mouse <email>mouse@Collatz.McRCIM.McGill.EDU</email></para>
- </listitem>
-
- <listitem>
- <para>frf <email>frf@xocolatl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Ege Rekk <email>aagero@aage.priv.no</email></para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1>
- <title>386BSD Patch Kit Patch Contributors</title>
-
- <para>(in alphabetical order by first name):</para>
-
- <itemizedlist>
- <listitem>
- <para>Adam Glass <email>glass@postgres.berkeley.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Adrian Hall <email>adrian@ibmpcug.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Andrey A. Chernov <email>ache@astral.msk.su</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Herbert <email>andrew@werple.apana.org.au</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Moore <email>alm@netcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andy Valencia <email>ajv@csd.mot.com</email>
- <email>jtk@netcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Arne Henrik Juul <email>arnej@Lise.Unit.NO</email></para>
- </listitem>
-
- <listitem>
- <para>Bakul Shah <email>bvs@bitblocks.com</email></para>
- </listitem>
-
- <listitem>
- <para>Barry Lustig <email>barry@ictv.com</email></para>
- </listitem>
-
- <listitem>
- <para>Bob Wilcox <email>bob@obiwan.uucp</email></para>
- </listitem>
-
- <listitem>
- <para>Branko Lankester</para>
- </listitem>
-
- <listitem>
- <para>Brett Lymn <email>blymn@mulga.awadi.com.AU</email></para>
- </listitem>
-
- <listitem>
- <para>Charles Hannum <email>mycroft@ai.mit.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Chris G. Demetriou
- <email>cgd@postgres.berkeley.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Torek <email>torek@ee.lbl.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Christoph Robitschko
- <email>chmr@edvz.tu-graz.ac.at</email></para>
- </listitem>
-
- <listitem>
- <para>Daniel Poirot <email>poirot@aio.jsc.nasa.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Burgess <email>burgess@hrd769.brooks.af.mil</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Rivers <email>rivers@ponds.uucp</email></para>
- </listitem>
-
- <listitem>
- <para>David Dawes <email>dawes@physics.su.OZ.AU</email></para>
- </listitem>
-
- <listitem>
- <para>David Greenman <email>dg@Root.COM</email></para>
- </listitem>
-
- <listitem>
- <para>Eric J. Haug <email>ejh@slustl.slu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Felix Gaehtgens
- <email>felix@escape.vsse.in-berlin.de</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Maclachlan <email>fpm@crash.cts.com</email></para>
- </listitem>
-
- <listitem>
- <para>Gary A. Browning <email>gab10@griffcd.amdahl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Gary Howland <email>gary@hotlava.com</email></para>
- </listitem>
-
- <listitem>
- <para>Geoff Rehmet <email>csgr@alpha.ru.ac.za</email></para>
- </listitem>
-
- <listitem>
- <para>Goran Hammarback <email>goran@astro.uu.se</email></para>
- </listitem>
-
- <listitem>
- <para>Guido van Rooij <email>guido@gvr.org</email></para>
- </listitem>
-
- <listitem>
- <para>Guy Harris <email>guy@auspex.com</email></para>
- </listitem>
-
- <listitem>
- <para>Havard Eidnes
- <email>Havard.Eidnes@runit.sintef.no</email></para>
- </listitem>
-
- <listitem>
- <para>Herb Peyerl <email>hpeyerl@novatel.cuc.ab.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Holger Veit <email>Holger.Veit@gmd.de</email></para>
- </listitem>
-
- <listitem>
- <para>Ishii Masahiro, R. Kym Horsell</para>
- </listitem>
-
- <listitem>
- <para>J.T. Conklin <email>jtc@cygnus.com</email></para>
- </listitem>
-
- <listitem>
- <para>Jagane D Sundar <email>jagane@netcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>James Clark <email>jjc@jclark.com</email></para>
- </listitem>
-
- <listitem>
- <para>James Jegers <email>jimj@miller.cs.uwm.edu</email></para>
- </listitem>
-
- <listitem>
- <para>James W. Dolter</para>
- </listitem>
-
- <listitem>
- <para>James da Silva <email>jds@cs.umd.edu</email> et al</para>
- </listitem>
-
- <listitem>
- <para>Jay Fenlason <email>hack@datacube.com</email></para>
- </listitem>
-
- <listitem>
- <para>Jim Wilson <email>wilson@moria.cygnus.com</email></para>
- </listitem>
-
- <listitem>
- <para>J&ouml;rg Lohse
- <email>lohse@tech7.informatik.uni-hamburg.de</email></para>
- </listitem>
-
- <listitem>
- <para>J&ouml;rg Wunsch
- <email>joerg_wunsch@uriah.heep.sax.de</email></para>
- </listitem>
-
- <listitem>
- <para>John Dyson</para>
- </listitem>
-
- <listitem>
- <para>John Woods <email>jfw@eddie.mit.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Jordan K. Hubbard <email>jkh@whisker.hubbard.ie</email></para>
- </listitem>
-
- <listitem>
- <para>Julian Elischer <email>julian@dialix.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Julian Stacey <email>jhs@FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Karl Dietz <email>Karl.Dietz@triplan.com</email></para>
- </listitem>
-
- <listitem>
- <para>Karl Lehenbauer <email>karl@NeoSoft.com</email>
- <email>karl@one.neosoft.com</email></para>
- </listitem>
-
- <listitem>
- <para>Keith Bostic <email>bostic@toe.CS.Berkeley.EDU</email></para>
- </listitem>
-
- <listitem>
- <para>Ken Hughes</para>
- </listitem>
-
- <listitem>
- <para>Kent Talarico <email>kent@shipwreck.tsoft.net</email></para>
- </listitem>
-
- <listitem>
- <para>Kevin Lahey <email>kml%rokkaku.UUCP@mathcs.emory.edu</email>
- <email>kml@mosquito.cis.ufl.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Marc Frajola <email>marc@dev.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mark Tinguely <email>tinguely@plains.nodak.edu</email>
- <email>tinguely@hookie.cs.ndsu.NoDak.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Martin Renters <email>martin@tdc.on.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Clay <email>mclay@weareb.org</email></para>
- </listitem>
-
- <listitem>
- <para>Michael Galassi <email>nerd@percival.rain.com</email></para>
- </listitem>
-
- <listitem>
- <para>Mike Durkin <email>mdurkin@tsoft.sf-bay.org</email></para>
- </listitem>
-
- <listitem>
- <para>Naoki Hamada <email>nao@tom-yam.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Nate Williams <email>nate@bsd.coe.montana.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Nick Handel <email>nhandel@NeoSoft.com</email>
- <email>nick@madhouse.neosoft.com</email></para>
- </listitem>
-
- <listitem>
- <para>Pace Willisson <email>pace@blitz.com</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Kranenburg <email>pk@cs.few.eur.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Mackerras <email>paulus@cs.anu.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>Paul Popelka <email>paulp@uts.amdahl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Peter da Silva <email>peter@NeoSoft.com</email></para>
- </listitem>
-
- <listitem>
- <para>Phil Sutherland
- <email>philsuth@mycroft.dialix.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Poul-Henning Kamp<email>phk@FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Ralf Friedl <email>friedl@informatik.uni-kl.de</email></para>
- </listitem>
-
- <listitem>
- <para>Rick Macklem <email>root@snowhite.cis.uoguelph.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Robert D. Thrush <email>rd@phoenix.aii.com</email></para>
- </listitem>
-
- <listitem>
- <para>Rodney W. Grimes <email>rgrimes@cdrom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Sascha Wildner <email>swildner@channelz.GUN.de</email></para>
- </listitem>
-
- <listitem>
- <para>Scott Burris <email>scott@pita.cns.ucla.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Scott Reynolds <email>scott@clmqt.marquette.mi.us</email></para>
- </listitem>
-
- <listitem>
- <para>Sean Eric Fagan <email>sef@kithrup.com</email></para>
- </listitem>
-
- <listitem>
- <para>Simon J Gerraty <email>sjg@melb.bull.oz.au</email>
- <email>sjg@zen.void.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Stephen McKay <email>syssgm@devetir.qld.gov.au</email></para>
- </listitem>
-
- <listitem>
- <para>Terry Lambert <email>terry@icarus.weber.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Terry Lee <email>terry@uivlsi.csl.uiuc.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Tor Egge <email>Tor.Egge@idi.ntnu.no</email></para>
- </listitem>
-
- <listitem>
- <para>Warren Toomey <email>wkt@csadfa.cs.adfa.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Wiljo Heinen <email>wiljo@freeside.ki.open.de</email></para>
- </listitem>
-
- <listitem>
- <para>William Jolitz <email>withheld</email></para>
- </listitem>
-
- <listitem>
- <para>Wolfgang Solfrank <email>ws@tools.de</email></para>
- </listitem>
-
- <listitem>
- <para>Wolfgang Stanglmeier <email>wolf@dentaro.GUN.de</email></para>
- </listitem>
-
- <listitem>
- <para>Yuval Yarom <email>yval@cs.huji.ac.il</email></para>
- </listitem>
- </itemizedlist>
- </sect1>
-</chapter>
-
-<!--
- Local Variables:
- mode: sgml
- sgml-declaration: "../chapter.decl"
- sgml-indent-data: t
- sgml-omittag: nil
- sgml-always-quote-attributes: t
- sgml-parent-document: ("../handbook.sgml" "part" "chapter")
- End:
--->
-
diff --git a/en_US.ISO8859-1/Makefile b/en_US.ISO8859-1/Makefile
deleted file mode 100644
index 0b2210c098..0000000000
--- a/en_US.ISO8859-1/Makefile
+++ /dev/null
@@ -1,9 +0,0 @@
-# $FreeBSD$
-
-SUBDIR = articles
-SUBDIR+= books
-
-COMPAT_SYMLINK = en
-
-DOC_PREFIX?= ${.CURDIR}/..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/Makefile b/en_US.ISO8859-1/articles/Makefile
deleted file mode 100644
index e1c5b47597..0000000000
--- a/en_US.ISO8859-1/articles/Makefile
+++ /dev/null
@@ -1,18 +0,0 @@
-# $FreeBSD: doc/en_US.ISO_8859-1/articles/Makefile,v 1.7 2000/06/07 23:24:18 nik Exp $
-
-SUBDIR = committers-guide
-SUBDIR+= dialup-firewall
-SUBDIR+= diskless-x
-SUBDIR+= fonts
-SUBDIR+= formatting-media
-SUBDIR+= ipsec-must
-SUBDIR+= mh
-SUBDIR+= multi-os
-SUBDIR+= new-users
-SUBDIR+= programming-tools
-SUBDIR+= zip-drive
-
-# ROOT_SYMLINKS+= new-users
-
-DOC_PREFIX?= ${.CURDIR}/../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/Makefile.inc b/en_US.ISO8859-1/articles/Makefile.inc
deleted file mode 100644
index 68161e6d79..0000000000
--- a/en_US.ISO8859-1/articles/Makefile.inc
+++ /dev/null
@@ -1,5 +0,0 @@
-#
-# $FreeBSD$
-#
-
-DESTDIR?= ${DOCDIR}/en_US.ISO_8859-1/articles/${.CURDIR:T}
diff --git a/en_US.ISO8859-1/articles/committers-guide/Makefile b/en_US.ISO8859-1/articles/committers-guide/Makefile
deleted file mode 100644
index a623572f3e..0000000000
--- a/en_US.ISO8859-1/articles/committers-guide/Makefile
+++ /dev/null
@@ -1,25 +0,0 @@
-#
-# $FreeBSD$
-#
-# Build the FreeBSD New Committers Guide
-#
-
-MAINTAINER=jhb@FreeBSD.org
-
-DOC?= article
-
-FORMATS?= html
-
-INSTALL_COMPRESSED?= gz
-INSTALL_ONLY_COMPRESSED?=
-
-#
-# SRCS lists the individual SGML files that make up the document. Changes
-# to any of these files will force a rebuild
-#
-
-# SGML content
-SRCS= article.sgml
-
-DOC_PREFIX?= ${.CURDIR}/../../..
-.include "${DOC_PREFIX}/share/mk/doc.project.mk"
diff --git a/en_US.ISO8859-1/articles/committers-guide/article.sgml b/en_US.ISO8859-1/articles/committers-guide/article.sgml
deleted file mode 100644
index deaec4435a..0000000000
--- a/en_US.ISO8859-1/articles/committers-guide/article.sgml
+++ /dev/null
@@ -1,2017 +0,0 @@
-<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V3.1-Based Extension//EN" [
-<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
-%man;
-
-<!ENTITY % authors PUBLIC "-//FreeBSD//ENTITIES DocBook Author Entities//EN">
-%authors;
-]>
-
-<article>
- <artheader>
- <title>Committer Guide</title>
-
- <authorgroup>
- <author>
- <surname>The FreeBSD Documentation Project</surname>
- </author>
- </authorgroup>
-
- <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/articles/committers-guide/article.sgml,v 1.43 2000/11/03 19:01:27 sobomax Exp $</pubdate>
-
- <copyright>
- <year>1999</year>
- <year>2000</year>
- <holder>The FreeBSD Documentation Project</holder>
- </copyright>
-
- <abstract>
- <para>This document provides information for the FreeBSD committer
- community. All new committers should read this document before they
- start, and existing committers are strongly encouraged to review it
- from time to time.</para>
- </abstract>
- </artheader>
-
- <sect1 id="admin">
- <title>Administrative Details</title>
-
- <informaltable frame="none" orient="port">
- <tgroup cols="2">
- <tbody>
- <row>
- <entry><emphasis>Main Repository Host</emphasis></entry>
- <entry><hostid>freefall.FreeBSD.org</hostid></entry>
- </row>
-
- <row>
- <entry><emphasis>Login Methods</emphasis></entry>
- <entry>&man.ssh.1;</entry>
- </row>
-
- <row>
- <entry><emphasis>Main CVSROOT</emphasis></entry>
- <entry>/home/ncvs</entry>
- </row>
-
- <row>
- <entry><emphasis>Main CVS Repository Meisters</emphasis></entry>
- <entry>&a.jdp; and &a.peter; as well as &a.asami; for
- <filename>ports/</filename></entry>
- </row>
-
- <row>
- <entry><emphasis>Mailing List</emphasis></entry>
- <entry><email>developers@FreeBSD.org</email></entry>
- <entry><email>cvs-committers@FreeBSD.org</email></entry>
- </row>
-
- <row>
- <entry><emphasis>Noteworthy CVS Tags</emphasis></entry>
- <entry>RELENG_3 (3.x-STABLE), RELENG_4 (4.x-STABLE), HEAD (-CURRENT)</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>It is required that you use &man.ssh.1; or &man.telnet.1;
- with Kerberos 5 to connect to the repository hosts. These are
- generally more secure than plain &man.telnet.1; or
- &man.rlogin.1; since credential negotiation will always be
- encrypted. All traffic is encrypted by default with &man.ssh.1;.
- With utilities like &man.ssh-agent.1; and &man.scp.1; also
- available, &man.ssh.1; is also far more convenient. If you do
- not know anything about &man.ssh.1;, please see
- <xref linkend="ssh.guide">.</para>
- </sect1>
-
- <sect1 id="cvs.operations">
- <title>CVS Operations</title>
-
- <para>It is assumed that you are already familiar with the basic operation
- of CVS.</para>
-
- <para>The CVS Repository Meisters (Peter Wemm and John Polstra)
- are the <quote>owners</quote> of the CVS repository and are
- responsible for any and <emphasis>all</emphasis> direct
- modification of it for the purposes of cleanup or fixing some
- grievous abuse of CVS by a committer. No one else should
- attempt to touch the repository directly. Should you cause some
- repository accident, say a bad cvs import or tag operation, do
- <emphasis role="bold">not</emphasis> attempt to fix it yourself!
- Mail or call John or Peter immediately and report the problem to
- one of them instead. The only ones allowed to directly fiddle
- the repository bits are the repomeisters. Satoshi Asami is also a
- repomeister for the <filename>ports/</filename> portion of the
- tree.</para>
-
- <para>CVS operations are usually done by logging into
- <hostid>freefall</hostid>, making sure the
- <envar>CVSROOT</envar> environment variable is set to
- <filename>/home/ncvs</filename>, and then doing the appropriate
- check-out/check-in operations. If you wish to add
- something which is wholly new (like contrib-ified
- sources, etc), a script called <quote>easy-import</quote> is
- also provided for making the process easier. It automatically
- adds the new module entry, does the appropriate thing with
- <command>cvs import</command>, etc. &ndash; just run it without
- arguments and it will prompt you for everything it needs to
- know.</para>
-
- <para>Note that when you use CVS on <hostid>freefall</hostid>, you
- should set your <literal>umask</literal> to <literal>2</literal>,
- as well as setting the <literal>CVSUMASK</literal> environmenet
- variable to <literal>2</literal>. This ensures that any new
- files created by <command>cvs add</command> will have the correct
- permissions. If you add a file or directory and discover that the
- file in the repository has incorrect permissions (specifically,
- all files in the repository should be group writable by group
- <literal>ncvs</literal>), contact one of the repository meisters
- as described below.</para>
-
- <para>If you are familiar with remote CVS and consider yourself
- pretty studly with CVS in general, you can also do CVS
- operations directly from your own machine and local working
- sources. Just remember to set <envar>CVS_RSH</envar> to
- <wordasword>ssh</wordasword> so that you are using a relatively
- secure and reliable transport. If you have no idea what any of
- the above even means, on the other hand, then please stick with
- logging into <hostid>freefall</hostid> and applying your diffs
- with &man.patch.1;.</para>
-
- <para>If you need to use CVS <command>add</command> and
- <command>delete</command> operations in a manner that is
- effectively a <quote>mv</quote> operation, then a repository
- copy is in order rather than your CVS <command>add</command> and
- <command>delete</command>. In a repository copy, a <link
- linkend="conventions">CVS Meister</link> will copy the file(s)
- to their new name and/or location and let you know when it is
- done. The purpose of a repository copy is to preserve file
- change history, or logs. We in the FreeBSD Project greatly
- value the change history CVS gives to the project.</para>
-
- <para>CVS reference information, tutorials, and FAQs can also be found at:
- <ulink
- url="http://www.cyclic.com/CVS/support">http://www.cyclic.com/CVS/support</ulink></para>
-
- <para>&a.des; also supplied the following <quote>mini primer</quote> for
- CVS.</para>
-
- <orderedlist>
- <listitem>
- <para>Check out a module with the <literal>co</literal> or
- <literal>checkout</literal> command.</para>
-
- <screen>&prompt.user; <userinput>cvs checkout shazam</userinput></screen>
-
- <para>This checks out a copy of the <filename>shazam</filename> module. If
- there is no <filename>shazam</filename> module in the modules file, looks for a
- top-level directory named <filename>shazam</filename> instead.</para>
-
- <para>Useful options:</para>
-
- <informaltable>
- <tgroup cols=2>
- <tbody>
- <row>
- <entry><option>-P</option></entry>
- <entry>Don't create empty directories</entry>
- </row>
-
- <row>
- <entry><option>-l</option></entry>
- <entry>Check out a single level, no subdirectories</entry>
- </row>
-
- <row>
- <entry><option>-r<replaceable>rev</replaceable></option></entry>
- <entry>Check out revision, branch or tag
- <replaceable>rev</replaceable></entry>
- </row>
-
- <row>
- <entry><option>-D<replaceable>date</replaceable></option></entry>
- <entry>Check out the sources as they were on date
- <replaceable>data</replaceable></entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>Practical FreeBSD examples:</para>
-
- <itemizedlist>
- <listitem>
- <para>Check out the <filename>miscfs</filename> module,
- which corresponds to <filename>src/sys/miscfs</filename>:</para>
-
- <screen>&prompt.user; <userinput>cvs co miscfs</userinput></screen>
-
- <para>You now have a directory named <filename>miscfs</filename>
- with subdirectories <filename>CVS</filename>,
- <filename>deadfs</filename>, <filename>devfs</filename>, and so
- on. One of these (<filename>linprocfs</filename>) is
- empty.</para>
- </listitem>
-
- <listitem>
- <para>Check out the same files, but with full path:</para>
-
- <screen>&prompt.user; <userinput>cvs co src/sys/miscfs</userinput></screen>
-
- <para>You now have a directory named <filename>src</filename>,
- with subdirectories <filename>CVS</filename> and
- <filename>sys</filename>. <filename>src/sys</filename> has
- subdirectories <filename>CVS</filename> and
- <filename>miscfs</filename>, etc.</para>
- </listitem>
-
- <listitem>
- <para>Check out the same files, but prunes empty
- directories:</para>
-
- <screen>&prompt.user; <userinput>cvs co -P miscfs</userinput></screen>
-
- <para>You now have a directory named
- <filename>miscfs</filename> with subdirectories
- <filename>CVS</filename>, <filename>deadfs</filename>,
- <filename>devfs</filename>... but note that there is no
- <filename>linprocfs</filename> subdirectory, because there
- are no files in it.</para>
- </listitem>
-
- <listitem>
- <para>Check out the directory <filename>miscfs</filename>, but
- none of the subdirectories:</para>
-
- <screen>&prompt.root; <userinput>cvs co -l miscfs</userinput></screen>
-
- <para>You now have a directory named <filename>miscfs</filename>
- with just one subdirectory named
- <filename>CVS</filename>.</para>
- </listitem>
-
- <listitem>
- <para>Check out the <filename>miscfs</filename> module as
- it is in the 4.x branch:</para>
-
- <screen>&prompt.user; <userinput>cvs co -rRELENG_4 miscfs</userinput></screen>
-
- <para>You can modify the sources and commit along this
- branch.</para>
- </listitem>
-
- <listitem>
- <para>Check out the <filename>miscfs</filename> module as
- it was in 3.4-RELEASE.</para>
-
- <screen>&prompt.user; <userinput>cvs co -rRELENG_3_4_0_RELEASE miscfs</userinput></screen>
-
- <para>You will not be able to commit modifications, since
- RELENG_3_4_0_RELEASE is a point in time, not a branch.</para>
- </listitem>
-
- <listitem>
- <para>Check out the <filename>miscfs</filename> module as it was
- on Jan 15 2000.</para>
-
- <screen>&prompt.user; <userinput>cvs co -D'01/15/2000' miscfs</userinput></screen>
-
- <para>You will not be able to commit modifications.</para>
- </listitem>
-
- <listitem>
- <para>Check out the <filename>miscfs</filename> module as it was
- one week agao.</para>
-
- <screen>&prompt.user; <userinput>cvs co -D'last week' miscfs</userinput></screen>
-
- <para>You will not be able to commit modifications.</para>
- </listitem>
- </itemizedlist>
-
- <para>Note that cvs stores metadata in subdirectories named
- <filename>CVS</filename>.</para>
-
- <para>Arguments to <option>-D</option> and <option>-r</option>
- are sticky, which means cvs will remember them later, e.g.
- when you do a <command>cvs update</command>.</para>
- </listitem>
-
- <listitem>
- <para>Check the status of checked-out files with the
- <literal>status</literal> command.</para>
-
- <screen>&prompt.user; <userinput>cvs status shazam</userinput></screen>
-
- <para>This displays the status of the
- <filename>shazam</filename> file or of every file in the
- <filename>shazam</filename> directory. For every file, the
- status is given as one of:</para>
-
- <informaltable>
- <tgroup cols=2>
- <tbody>
- <row>
- <entry>Up-to-date</entry>
- <entry>File is up-to-date and unmodified.</entry>
- </row>
-
- <row>
- <entry>Needs Patch</entry>
- <entry>File is unmodified, but there's a newer revision in
- the repository.</entry>
- </row>
-
- <row>
- <entry>Locally Modified</entry>
- <entry>File is up-to-date, but modified.</entry>
- </row>
-
- <row>
- <entry>Needs Merge</entry>
- <entry>File is modified, and there's a newer revision in the
- repository.</entry>
- </row>
-
- <row>
- <entry>File had conflicts on merge</entry>
- <entry>There were conflicts the last time this file was
- updated, and they haven't been resolved yet.</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>You'll also see the local revision and date,
- the revision number of the newest applicable version
- (<quote>newest applicable</quote> because if you have a
- sticky date, tag or branch, it may not be the actual newest
- revision), and any sticky tags, dates or options.</para>
- </listitem>
-
- <listitem>
- <para>Once you've checked something out, update it with the
- <literal>update</literal> command.</para>
-
- <screen>&prompt.user; <userinput>cvs update shazam</userinput></screen>
-
- <para>This updates the <filename>shazam</filename> file or the
- contents of the <filename>shazam</filename> directory to the
- latest version along the branch you checked out. If you
- checked out a <quote>point in time</quote>, does nothing
- unless the tags have moved in the repo or some other weird
- stuff is going on.</para>
-
- <para>Useful options, in addition to those listed above for
- <literal>checkout</literal>:</para>
-
- <informaltable>
- <tgroup cols=2>
- <tbody>
- <row>
- <entry><option>-d</option></entry>
- <entry>Check out any additional missing directories.</entry>
- </row>
-
- <row>
- <entry><option>-A</option></entry>
- <entry>Update to head of main branch.</entry>
- </row>
-
- <row>
- <entry><option>-j<replaceable>rev</replaceable></option></entry>
- <entry>More magic (see below).</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>If you checked out a module with <option>-r</option> or
- <option>-D</option>, running <command>cvs update</command>
- with a different <option>-r</option> or <option>-D</option>
- argument or with <option>-A</option> will select a new branch,
- revision or date. The <option>-A</option> option clears all
- sticky tags, dates or revisions whereas <option>-r</option>
- and <option>-D</option> set new ones.</para>
-
- <para>Theoretically, specifying <literal>HEAD</literal> as
- argument to <option>-r</option> will give you the same result
- as <option>-A</option>, but that's just theory.</para>
-
- <para>The <option>-d</option> option is useful if:</para>
-
- <itemizedlist>
- <listitem>
- <para>somebody has added subdirectories to the module
- you've checked out after you checked it out.</para>
- </listitem>
-
- <listitem>
- <para>you checked out with <option>-l</option>, and later
- change your mind and want to check out the subdirectories
- as well.</para>
- </listitem>
-
- <listitem>
- <para>you deleted some subdirectories and want to check
- them all back out.</para>
- </listitem>
- </itemizedlist>
-
- <para><emphasis>Watch the output of the <command>cvs
- update</command> with care.</emphasis> The letter in front of
- each file name indicates what was done with it:</para>
-
- <informaltable>
- <tgroup cols=2>
- <tbody>
- <row>
- <entry><literal>U</literal></entry>
- <entry>The file was updated with no trouble.</entry>
- </row>
-
- <row>
- <entry><literal>P</literal></entry>
- <entry>The file was updated with no trouble (you'll only see
- this when working against a remote repo).</entry>
- </row>
-
- <row>
- <entry><literal>M</literal></entry>
- <entry>The file had been modified, and was merged with no
- conflicts.</entry>
- </row>
-
- <row>
- <entry><literal>C</literal></entry>
- <entry>The file had been modified, and was merged with
- conflicts.</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>Merging is what happens if you check out a copy of
- some source code, modify it, then someone else commits a
- change, and you run <command>cvs update</command>. CVS notices
- that you've made local changes, and tries to merge your
- changes with the changes between the version you originally
- checked out and the one you updated to. If the changed are to
- separate portions of the file, it'll almost always work fine
- (though the result might not be syntactically or semantically
- correct).</para>
-
- <para>CVS will print an 'M' in front of every locally modified
- file even if there is no newer version in the repository, so
- <command>cvs update</command> is handy for getting a summary
- of what you've changed locally.</para>
-
- <para>If you get a <literal>C</literal>, then your changes
- conflicted with the changes in the repository (the changes
- were to the same lines, or neighboring lines, or you changed
- the local file so much that <command>cvs</command> can't
- figure out how to apply the repository's changes). You'll have
- to go through the file manually and resolve the conflicts;
- they'll be marked with rows of <literal>&lt;</literal>,
- <literal>=</literal> and <literal>&gt;</literal> signs. For
- every conflict, there'll be a marker line with seven
- <literal>&lt;</literal> signs and the name of the file,
- followed by a chunk of what your local file contained,
- followed by a separator line with seven <literal>=</literal>
- signs, followed by the corresponding chunk in the
- repository version, followed by a marker line with seven
- <literal>&gt;</literal> signs and the revision number you
- updated to.</para>
-
- <para>The <option>-j</option> option is slightly voodoo. It
- updates the local file to the specified revision as if you
- used <option>-r</option>, but it does not change the recorded
- revision number or branch of the local file. It's not really
- useful except when used twice, in which case it will merge the
- changes between the two specified versions into the working
- copy.</para>
-
- <para>For instance, say you commit a change to
- <filename>shazam/shazam.c</filename> in -CURRENT and later
- want to MFC it. The change you want to MFC was revision
- 1.15:</para>
-
- <itemizedlist>
- <listitem>
- <para>Check out the -STABLE version of the
- <filename>shazam</filename> module:</para>
-
- <screen>&prompt.user; <userinput>cvs co -rRELENG_4 shazam</userinput></screen>
- </listitem>
-
- <listitem>
- <para>Apply the changes between rev 1.14 and 1.15:</para>
-
- <screen>&prompt.user; <userinput>cvs update -j1.14 -j1.15 shazam/shazam.c</userinput></screen>
- </listitem>
- </itemizedlist>
-
- <para>You'll almost certainly get a conflict because
- of the <literal>$Id: article.sgml,v 1.44 2000-11-14 11:11:56 demon Exp $</literal> (or in FreeBSD's case,
- <literal>$FreeBSD<!-- stop expansion -->$</literal>) lines, so you'll have to edit
- the file to resolve the conflict (remove the marker lines and
- the second <literal>$Id: article.sgml,v 1.44 2000-11-14 11:11:56 demon Exp $</literal> line, leaving the original
- <literal>$Id: article.sgml,v 1.44 2000-11-14 11:11:56 demon Exp $</literal> line intact).</para>
- </listitem>
-
- <listitem>
- <para>View differences between the local version and the
- repository version with the <literal>diff</literal>
- command.</para>
-
- <screen>&prompt.user; <userinput>cvs diff shazam</userinput></screen>
-
- <para>shows you every modification you've made to the
- <filename>shazam</filename> file or module.</para>
-
- <para>Useful options:</para>
-
- <informaltable>
- <tgroup cols=2>
- <tbody>
- <row>
- <entry><option>-u</option></entry>
- <entry>Uses the unified diff format.</entry>
- </row>
-
- <row>
- <entry><option>-N</option></entry>
- <entry>Shows missing or added files.</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>You always want to use <option>-u</option>, since
- unified diffs are much easier to read than almost any other
- diff format (in some circumstances, context diffs may be
- better, but they're much bulkier). A unified diff consists of
- a series of hunks. Each hunk begins with a line that starts
- with two <literal>@</literal> signs and specifies where in the
- file the differences are and how many lines they span. This
- is followed by a number of lines; some (preceded by a blank)
- are context; some (preceded by a <literal>-</literal> sign)
- are outtakes and some (preceded by a <literal>+</literal>) are
- additions.</para>
-
- <para>You can also diff against a different version
- than the one you checked out by specifying a version
- with <option>-r</option> or <option>-D</option> as in
- <literal>checkout</literal> or <literal>update</literal>,
- or even view the diffs between two arbitrary versions
- (with no regard for what you have locally) by specifying
- <emphasis>two</emphasis> versions with <option>-r</option> or
- <option>-D</option>.</para>
- </listitem>
-
- <listitem>
- <para>View log entries with the <literal>log</literal>
- command.</para>
-
- <!-- XXX needs more details -->
- <screen>&prompt.user; <userinput>cvs log shazam</userinput></screen>
- </listitem>
-
- <listitem>
- <para>See who did what with the <literal>annotate</literal> command.
- This command shows you each line of the specified file or
- files, along with which user most recently changed that
- line.</para>
-
- <screen>&prompt.user; <userinput>cvs annotate shazam</userinput></screen>
- </listitem>
-
- <listitem>
- <para>Add new files with the <literal>add</literal> command.</para>
-
- <para>Create the file, <command>cvs add</command> it, then
- <command>cvs commit</command> it.</para>
-
- <para>Similarly, you can add new directories by creating them
- and then <command>cvs add</command>ing them. Note that you
- don't need to commit directories.</para>
- </listitem>
-
- <listitem>
- <para>Remove obsolete files with the <literal>remove</literal> command.</para>
-
- <para>Remove the file, then <command>cvs rm</command> it, then
- <command>cvs commit</command> it.</para>
- </listitem>
-
- <listitem>
- <para>Commit with the <literal>commit</literal> or
- <literal>checkin</literal> command.</para>
-
- <para>Useful options:</para>
-
- <informaltable>
- <tgroup cols=2>
- <tbody>
- <row>
- <entry><option>-f</option></entry>
- <entry>Force a commit of an unmodified file.</entry>
- </row>
-
- <row>
- <entry><option>-m<replaceable>msg</replaceable></option></entry>
- <entry>Specify a commit message on the command line rather
- than invoking an editor.</entry>
- </row>
- </tbody>
- </tgroup>
- </informaltable>
-
- <para>Use the <option>-f</option> option if you realize that
- you left out important information from the commit message.</para>
-
- <para>Good commit messages are important. They tell others
- why you did the changes you did, not just right here and now,
- but months or years from now when someone wonders why some
- seemingly illogical or inefficient piece of code snuck into
- your source file. It's also an invaluable aid to deciding
- which changes to MFC and which not to MFC.</para>
-
- <para>Don't waste space in the commit messages explaining
- <emphasis>what</emphasis> you did. That's what
- <command>cvs diff</command> is for. Instead, tell us
- <emphasis>why</emphasis> you did it.</para>
-
- <para>Avoid committing several unrelated changes in one go. It
- makes merging difficult, and also makes it harder to determine
- which change is the culprit if a bug crops up.</para>
-
- <para>Avoid committing style or whitespace fixes and
- functionality fixes in one go. It makes merging difficult,
- and also makes it harder to understand just what functional
- changes were made.</para>
-
- <para>Avoid committing changes to multiple files in one go
- with a generic, vague message. Instead, commit each file (or
- small groups of files) with tailored commit messages.</para>
-
- <para>Before committing, <emphasis>always</emphasis>:</para>
-
- <itemizedlist>
- <listitem>
- <para>verify which branch you're committing to, using
- <command>cvs status</command>.</para>
- </listitem>
-
- <listitem>
- <para>review your diffs, using
- <command>cvs diff</command></para>
- </listitem>
- </itemizedlist>
-
- <para>Also, ALWAYS specify which files to commit explicitly on
- the command line, so you don't accidentally commit other files
- than the ones you intended - <command>cvs commit</command>
- with no arguments will commit every modification in your
- current working directory and every subdirectory.</para>
- </listitem>
- </orderedlist>
-
- <para>Additional tips and tricks:</para>
-
- <orderedlist>
- <listitem>
-
- <para>You can place commonly used options in your
- <filename>~/.cvsrc</filename>, like this:</para>
-
- <programlisting>cvs -z3
-diff -Nu
-update -Pd
-checkout -P</programlisting>
-
- <para>This example says:</para>
-
- <itemizedlist>
- <listitem>
- <para>always use compression level 3 when talking to a
- remote server. This is a life-saver when working over a
- slow connection.</para>
- </listitem>
-
- <listitem>
- <para>always use the <option>-N</option> (show added or
- removed files) and <option>-u</option> (unified diff
- format) options to &man.diff.1;.</para>
- </listitem>
-
- <listitem>
- <para>always use the <option>-P</option> (prune empty
- directories) and <option>-d</option> (check out new
- directories) options when updating.</para>
- </listitem>
-
- <listitem>
- <para>always use the <option>-P</option> (prune empty
- directories) option when checking out.</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>Use Eivind Eklund's <command>cdiff</command> script to
- view unidiffs. It's a wrapper for &man.less.1; that adds ANSI
- color codes to make hunk headers, outtakes and additions stand
- out; context and garbage are unmodified. It also expands tabs
- properly (tabs often look wrong in diffs because of the extra
- character in front of each line).</para>
-
-<para><ulink url="http://people.freebsd.org/~eivind/cdiff">http://people.freebsd.org/~eivind/cdiff</ulink></para>
-
- <para>Simply use instead of &man.more.1; or &man.less.1;:</para>
-
- <screen>&prompt.user; <userinput>cvs diff -Nu shazam | cdiff</userinput></screen>
-
- <para>Alternatively some editors like &man.vim.1;
- (ports/editors/vim5) have color support and when used as
- a pager with color syntax highlighting switched on will
- highlight many types of file, including diffs, patches,
- and cvs/rcs logs. </para>
-
- <screen>&prompt.user; <userinput> echo "syn on" >> ~/.vimrc </userinput>
-&prompt.user; <userinput> cvs diff -Nu shazam | vim -</userinput>
-&prompt.user; <userinput> cvs log shazam | vim -</userinput> </screen>
- </listitem>
-
- <listitem>
- <para>CVS is old, arcane, crufty and buggy, and sometimes
- exhibits non-deterministic behavior which some claim as proof
- that it's actually merely the newtonian manifestation of a
- sentient transdimensional entity. It's not humanly possible
- to know its every quirk inside out, so don't be afraid to ask
- the resident AI (<email>cvs@FreeBSD.org</email>) for help when
- you screw up.</para>
- </listitem>
-
- <listitem>
- <para>Don't leave the <command>cvs commit</command> command in commit
- message editing mode for too long (more than 2-3 minutes). It
- locks the directory you are working with and will prevent other
- developers from committing into the same directory. If you have
- to type a long commit message, type it before executing
- <command>cvs commit</command>, and insert it into the commit
- message.</para>
- </listitem>
- </orderedlist>
-
- </sect1>
-
- <sect1 id="conventions">
- <title>Conventions and Traditions</title>
-
- <para>As a new committer there are a number of things you should do
- first.</para>
-
- <itemizedlist>
- <listitem>
- <para>Add yourself to the <quote>Developers</quote> section of the
- Handbook and remove yourself from the <quote>Additional
- Contributors</quote> section.</para>
-
- <para>This is a relatively easy task, but remains a good first test of
- your CVS skills.</para>
- </listitem>
-
- <listitem>
- <para>Add an entry for yourself to
- <filename>www/en/news/newsflash.sgml</filename>. Look for the other
- entries that look like <quote>A new committer</quote> and follow the
- format.</para>
- </listitem>
-
- <listitem>
- <para>Some people also add an entry for themselves to
- <filename>ports/astro/xearth/files/freebsd.committers.markers</filename>.</para>
- </listitem>
-
- <listitem>
- <para>Introduce yourself to the other committers, otherwise no one
- will have any idea who you are or what you are working on. You do
- not have to write a comprehensive biography, just write a paragraph
- or two about who you are and what you plan to be working on as a
- committer in FreeBSD. Email this to
- <email>developers@FreeBSD.org</email> and you will be on your
- way!</para>
- </listitem>
-
- <listitem>
- <para>Log into <hostid>hub.FreeBSD.org</hostid> and create a
- <filename>/var/forward/<replaceable>user</replaceable></filename>
- (where <replaceable>user</replaceable> is your username) file
- containing the e-mail address where you want mail addressed to
- <replaceable>yourusername</replaceable>@FreeBSD.org to be forwarded.
- This includes all of the commit messages as well as any other mail
- addressed to <email>cvs-committers@FreeBSD.org</email> and
- <email>developers@FreeBSD.org</email>. Really
- large mailboxes which have taken up permanent residence on
- <hostid>hub</hostid> often get <quote>accidently</quote> truncated
- without warning, so forward it or read it and you will not lose
- it.</para>
- </listitem>
- </itemizedlist>
-
- <para>All new committers also have a mentor assigned to them for
- the first few months. Your mentor is more or less responsible for
- explaining anything which is confusing to you and is also
- responsible for your actions during this initial period. If you
- make a bogus commit, it is only going to embarrass your mentor
- and you should probably make it a policy to pass at least your
- first few commits by your mentor before committing it to the
- repository.</para>
-
- <para>All commits should go to <literal>-CURRENT</literal> first
- before being merged to <literal>-STABLE</literal>. No major new
- features or high-risk modifications should be made to the
- <literal>-STABLE</literal> branch.</para>
- </sect1>
-
- <sect1 id="developer.relations">
- <title>Developer Relations</title>
-
- <para>If you are working directly on your own code or on code
- which is already well established as your responsibility, then
- there is probably little need to check with other committers
- before jumping in with a commit. If you see a bug in an area of
- the system which is clearly orphaned (and there are a few such
- areas, to our shame), the same applies. If, however, you are
- about to modify something which is clearly being actively
- maintained by someone else (and it is only by watching the
- <literal>cvs-committers</literal> mailing list that you can
- really get a feel for just what is and is not) then consider
- sending the change to them instead, just as you would have
- before becoming a committer. For ports, you should contact the
- listed <makevar>MAINTAINER</makevar> in the
- <filename>Makefile</filename>. For other parts of the
- repository, if you are unsure who the active maintainer might
- be, it may help to scan the output of <command>cvs log</command>
- to see who has committed changes in the past. &a.fenner; has
- written a nice shell script that can help determine who the
- active maintainer might be. It lists each person who has
- committed to a given file along with the number of commits each
- person has made. It can be found on <hostid>freefall</hostid>
- at <filename>~fenner/bin/whodid</filename>. If your queries go
- unanswered or the committer otherwise indicates a lack of
- proprietary interest in the area affected, go ahead and commit
- it.</para>
-
- <para>If you are unsure about a commit for any reason at
- all, have it reviewed by <literal>-hackers</literal>
- before committing. Better to have it flamed then and there
- rather than when it is part of the CVS repository. If you do
- happen to commit something which results in controversy
- erupting, you may also wish to consider backing the change out
- again until the matter is settled. Remember &ndash; with CVS we
- can always change it back.</para>
- </sect1>
-
- <sect1 id="gnats">
- <title>GNATS</title>
-
- <para>The FreeBSD Project utilizes
- <application>GNATS</application> for tracking bugs and change
- requests. Be sure that if you commit a fix or suggestion found
- in a <application>GNATS</application> PR, you use
- <command>edit-pr <replaceable>pr-number</replaceable></command>
- on <hostid>freefall</hostid> to close it. It is also considered
- nice if you take time to close any PRs associated with your
- commits, if appropriate. Your can also make use of
- &man.send-pr.1; yourself for proposing any change which you feel
- should probably be made, pending a more extensive peer-review
- first.</para>
-
- <para>You can find out more about <application>GNATS</application>
- at:</para>
-
- <itemizedlist>
- <listitem>
- <para><ulink url="http://www.cs.utah.edu/csinfo/texinfo/gnats/gnats.html">http://www.cs.utah.edu/csinfo/texinfo/gnats/gnats.html</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.FreeBSD.org/support.html">http://www.FreeBSD.org/support.html</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.FreeBSD.org/send-pr.html">http://www.FreeBSD.org/send-pr.html</ulink></para>
- </listitem>
-
- <listitem>
- <para>&man.send-pr.1;</para>
- </listitem>
- </itemizedlist>
-
- <para>You can run a local copy of GNATS, and then integrate the FreeBSD
- GNATS tree in to it using CVSup. Then you can run GNATS commands
- locally, or use other interfaces, such as <command>tkgnats</command>.
- This lets you query the PR database without needing to be connected to
- the Internet.</para>
-
- <procedure>
- <title>Using a local GNATS tree</title>
-
- <step>
- <para>If you are not already downloading the GNATS tree, add this line
- to your <filename>supfile</filename>, and re-sup. Note that since
- GNATS is not under CVS control it has no tag, so if you are adding
- it to your existing <filename>supfile</filename> it should appear
- before any <quote>tag=</quote> entry as these remain active once set.
- </para>
-
- <programlisting>gnats release=current prefix=/usr</programlisting>
-
- <para>This will place the FreeBSD GNATS tree in
- <filename>/usr/gnats</filename>. You can use a
- <emphasis>refuse</emphasis> file to control which categories to
- receive. For example, to only receive <literal>docs</literal> PRs,
- put this line in
- <filename>/usr/local/etc/cvsup/sup/refuse</filename><footnote>
- <para>The precise path depends on the <literal>*default
- base</literal> setting in your
- <filename>supfile</filename>.</para>
- </footnote>.</para>
-
- <programlisting>gnats/[a-ce-z]*</programlisting>
-
- <para>The rest of these examples assume you have only supped the
- <literal>docs</literal> category. Adjust them as necessary,
- depending on the categories you are synching.</para>
- </step>
-
- <step>
- <para>Install the GNATS port from
- <filename>ports/databases/gnats</filename>. This will place the
- various GNATS directories under
- <filename>$PREFIX/share/gnats</filename>.</para>
- </step>
-
- <step>
- <para>Symlink the GNATS directories you are supping under the version
- of GNATS you have installed.</para>
-
- <screen>&prompt.root; <userinput>cd /usr/local/share/gnats/gnats-db</userinput>
-&prompt.root; <userinput>ln -s /usr/gnats/docs</userinput></screen>
-
- <para>Repeat as necessary, depending on how many GNATS categories you
- are synching.</para>
- </step>
-
- <step>
- <para>Update the GNATS <filename>categories</filename> file with these
- cageories. The file is
- <filename>$PREFIX/share/gnats/gnats-db/gnats-adm/categories</filename>.</para>
-
- <programlisting># This category is mandatory
-pending:Category for faulty PRs:gnats-admin:
-#
-# FreeBSD categories
-#
-docs:Documentation Bug:nik:</programlisting>
- </step>
-
- <step>
- <para>Run <filename>$PREFIX/libexec/gnats/gen-index</filename> to
- recreate the GNATS index. The output has to be redirected to
- <filename>$PREFIX/share/gnats/gnats-db/gnats-adm/index</filename>.
- You can do this periodically from &man.cron.8;, or run &man.cvsup.1;
- from a shell script that does this as well.</para>
-
- <screen>&prompt.root; <userinput>/usr/local/libexec/gnats/gen-index \
- > /usr/local/share/gnats/gnats-db/gnats-adm/index</userinput></screen>
- </step>
-
- <step>
- <para>Test the configuration by querying the PR database. This
- command shows open <literal>docs</literal> PRs.</para>
-
- <screen>&prompt.root; <userinput>query-pr -c docs -s open</userinput></screen>
-
- <para>Other interfaces, like
- <filename>ports/databases/tkgnats</filename> should also work
- nicely.</para>
- </step>
-
- <step>
- <para>Pick a PR and close it.</para>
- </step>
- </procedure>
-
- <note>
- <para>This procedure only works to allow you to view and query the PRs
- locally. To edit or close them you will still have to log in to
- <hostid>freefall</hostid> and do it from there.</para>
- </note>
- </sect1>
-
- <sect1 id="people">
- <title>Who's Who</title>
-
- <para>Besides Peter Wemm and John Polstra, the repository
- meisters, there are other FreeBSD project members whom you will
- probably get to know in your role as a committer. Briefly,
- and by no means all-inclusively, these are:</para>
-
- <variablelist>
- <varlistentry>
- <term>&a.asami;</term>
-
- <listitem>
- <para>Satoshi is the Ports Wraith, meaning that he has
- ultimate authority over any modifications to the ports
- collection or the ports skeleton makefiles. He is also
- the one responsible for administering ports freezes before
- the releases.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.bde;</term>
-
- <listitem>
- <para>Bruce is the Obersturmbahnfuhrer of the Style Police.
- When you do a commit that could have been done better,
- Bruce will be there to tell you. Be thankful that someone
- is.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.dg;</term>
-
- <listitem>
- <para>David is the overseer of the
- VM system. If you have a VM system change in mind,
- coordinate it with David.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.jkh;</term>
-
- <listitem>
- <para>Jordan is the release engineer. He is responsible for
- setting release deadlines and controlling the release
- process. During code freezes, he also has final authority
- on all changes to the system for whichever branch is
- pending release status. If there is something you want
- merged from <literal>-CURRENT</literal> to
- <literal>-STABLE</literal> (whatever values those may have
- at any given time), he is also the one to talk to about
- it.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.steve;</term>
-
- <listitem>
- <para>Steve is the unofficial maintainer of
- <filename>src/bin</filename>. If you have something
- significant you'd like to do there, you should probably
- coordinate it with Steve first. He is also a Problem
- Report-meister, along with &a.phk;.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.brian;</term>
-
- <listitem>
- <para>Official maintainer of
- <filename>/usr/bin/ppp</filename> and LPD.</para>
- </listitem>
- </varlistentry>
-
- <varlistentry>
- <term>&a.wollman;</term>
-
- <listitem>
- <para>If you need advice on obscure network internals or
- aren't sure of some potential change to the networking
- subsystem you have in mind, Garrett is someone to talk
- to.</para>
- </listitem>
- </varlistentry>
- </variablelist>
- </sect1>
-
- <sect1 id="ssh.guide">
- <title>SSH Quick-Start Guide</title>
-
- <procedure>
- <step>
- <para>If you are using FreeBSD 4.0 or later,
- OpenSSH is included in the base system.
- If you are using an earlier release,
- update and install one of the SSH ports. In general,
- you will probably want to get OpenSSH from the port in
- <filename>/usr/ports/security/openssh</filename>. You
- may also wish to check out the original ssh1 in
- <filename>/usr/ports/security/ssh</filename>, but make
- certain you pay attention to its license. Note that both
- of these ports cannot be installed at the same time.</para>
- </step>
-
- <step>
- <para>If you do not wish to type your password in every
- time you use &man.ssh.1;, and you use RSA keys to
- authenticate, &man.ssh-agent.1; is there for your
- convenience. If you want to use &man.ssh-agent.1;, make
- sure that you run it before running other applications. X
- users, for example, usually do this from their
- <filename>.xsession</filename> or
- <filename>.xinitrc</filename> file. See &man.ssh-agent.1;
- for details.</para>
- </step>
-
- <step>
- <para>Generate a key pair using &man.ssh-keygen.1;. The key
- pair will wind up in the
- <filename><envar>$HOME</envar>/.ssh</filename>
- directory.</para>
- </step>
-
- <step>
- <para>Send your public key
- (<filename><envar>$HOME</envar>/.ssh/identity.pub</filename>)
- to the person setting you up as a committer so it can be put
- into your <filename>authorized_keys</filename> file in your
- home directory on <hostid>freefall</hostid>
- (i.e.
- <filename><envar>$HOME</envar>/.ssh/authorized_keys</filename>).
- </para>
- </step>
- </procedure>
-
- <para>Now you should be able to use &man.ssh-add.1; for
- authentication once per session. This will prompt you for
- your private key's pass phrase, and then store it in your
- authentication agent (&man.ssh-agent.1;). If you no longer
- wish to have your key stored in the agent, issuing
- <command>ssh-add -d</command> will remove it.</para>
-
- <para>Test by doing something such as <command>ssh
- freefall.FreeBSD.org ls /usr</command>.</para>
-
- <para>For more information, see
- <filename>/usr/ports/security/openssh</filename>, &man.ssh.1;,
- &man.ssh-add.1;, &man.ssh-agent.1;, &man.ssh-keygen.1;, and
- &man.scp.1;.</para>
- </sect1>
-
- <sect1>
- <title>The FreeBSD Committers' Big List of Rules</title>
-
- <orderedlist>
- <listitem>
- <para>Respect other committers.</para>
- </listitem>
-
- <listitem>
- <para>Discuss any significant change
- <emphasis>before</emphasis> committing.</para>
- </listitem>
-
- <listitem>
- <para>Respect existing maintainers if listed in the
- (<makevar>MAINTAINER</makevar> field in
- <filename>Makefile</filename> or in the
- <filename>MAINTAINER</filename> file in the top-level
- directory).</para>
- </listitem>
-
- <listitem>
- <para>Never touch the repository directly. Ask a
- Repomeister.</para>
- </listitem>
-
- <listitem>
- <para>Any disputed change must be backed out pending
- resolution of the dispute if requested by a maintainer.
- Security related changes may
- override a maintainer's wishes at the Security Officer's
- discretion.</para>
- </listitem>
-
- <listitem>
- <para>Changes go to <literal>-CURRENT</literal> before
- <literal>-STABLE</literal> unless specifically permitted by
- the release engineer or unless they're not applicable to
- <literal>-CURRENT</literal>. Any non-trivial or non-urgent
- change which is applicable should also be allowed to sit in
- <literal>-CURRENT</literal> for at least 3 days before
- merging so that it can be given sufficient testing. The
- release engineer has the same authority over the
- <literal>-STABLE</literal> branch as outlined for the
- maintainer in rule #5.</para>
- </listitem>
-
- <listitem>
- <para>Don't fight in public with other committers; it looks
- bad. If you must <quote>strongly disagree</quote> about
- something, do so only in private.</para>
- </listitem>
-
- <listitem>
- <para>Respect all code freezes and read the
- <literal>committers</literal> mailing list on a timely basis
- so you know when a code freeze is in effect.</para>
- </listitem>
-
- <listitem>
- <para>When in doubt on any procedure, ask first!</para>
- </listitem>
-
- <listitem>
- <para>Test your changes before committing them.</para>
- </listitem>
- </orderedlist>
-
- <para>As noted, breaking some of these rules can be grounds for
- suspension or, upon repeated offense, permanent removal of
- commit privileges. Three or more members of core
- acting in unison,
- have the power to temporarily suspend commit privileges until
- <literal>-core</literal> as a whole has the chance to review the
- issue. In case of an <quote>emergency</quote> (a committer
- doing damage to the repository), a temporary suspension may also
- be done by the repository meisters or any other member of core
- who may happen to be awake at the time. Only core as a whole
- has the authority to suspend commit privileges for any
- significant length of time or to remove them permanently, the
- latter generally only being done after consultation with
- committers. This rule does not exist to set core up as a bunch
- of cruel dictators who can dispose of committers as casually as
- empty soda cans, but to give the project a kind of safety fuse.
- If someone is seriously out of control, it's important to be
- able to deal with this immediately rather than be paralyzed by
- debate. In all cases, a committer whose privileges are
- suspended or revoked is entitled to a <quote>hearing</quote>,
- the total duration of the suspension being determined at that
- time. A committer whose privileges are suspended may also
- request a review of the decision after 30 days and every 30 days
- thereafter (unless the total suspension period is less than 30
- days). A committer whose privileges have been revoked entirely
- may request a review after a period of 6 months have elapsed.
- This review policy is <emphasis>strictly informal</emphasis>
- and, in all cases, core reserves the right to either act on or
- disregard requests for review if they feel their original
- decision to be the right one.</para>
-
- <para>In all other aspects of project operation, core is a subset
- of committers and is bound by the <emphasis>same
- rules</emphasis>. Just because someone is in core doesn't mean
- that they have special dispensation to step outside of any of
- the lines painted here; core's <quote>special powers</quote>
- only kick in when it acts as a group, not on an individual
- basis. As individuals, we are all committers first and core
- second.</para>
-
- <sect2>
- <title>Details</title>
-
- <orderedlist>
- <listitem>
- <para>Respect other committers.</para>
-
- <para>This means that you need to treat other committers as
- the peer-group developers that they are. Despite our
- occasional attempts to prove the contrary, one doesn't get
- into committers by being stupid and nothing rankles more
- than being treated that way by one of your peers. Whether
- we always feel respect for one another or not (and
- everyone has off days), we still have to
- <emphasis>treat</emphasis> other committers with respect
- at all times or the whole team structure rapidly breaks
- down.</para>
-
- <para>Being able to work together long term is this project's
- greatest asset, one far more important than any set of
- changes to the code, and turning arguments about code into
- issues that affect our long-term ability to work
- harmoniously together is just not worth the trade-off by
- any conceivable stretch of the imagination.</para>
-
- <para>To comply with this rule, don't send email when you're
- angry or otherwise behave in a manner which is likely to
- strike others as needlessly confrontational. First calm
- down, then think about how to communicate in the most
- effective fashion for convincing the other person(s) that
- your side of the argument is correct, don't just blow off
- some steam so you can feel better in the short term at the
- cost of a long-term flame war. Not only is this very bad
- <quote>energy economics</quote>, but repeated displays of
- public aggression which impair our ability to work well
- together will be dealt with severely by the project
- leadership and may result in suspension or termination of
- your commit privileges. That's never an option which the
- project's leadership enjoys in the slightest, but unity
- comes first. No amount of code or good advice is worth
- trading that away.</para>
- </listitem>
-
- <listitem>
- <para>Discuss any significant change
- <emphasis>before</emphasis> committing.</para>
-
- <para>The CVS repository is not where changes should be
- initially submitted for correctness or argued over, that
- should happen first in the mailing lists and then
- committed only once something resembling consensus has
- been reached. This doesn't mean that you have to ask
- permission before correcting every obvious syntax error or
- man page misspelling, simply that you should try to
- develop a feel for when a proposed change isn't quite such
- a no-brainer and requires some feedback first. People
- really don't mind sweeping changes if the result is
- something clearly better than what they had before, they
- just don't like being <emphasis>surprised</emphasis> by
- those changes. The very best way of making sure that
- you're on the right track is to have your code reviewed by
- one or more other committers.</para>
-
- <para>When in doubt, ask for review!</para>
- </listitem>
-
- <listitem>
- <para>Respect existing maintainers if listed.</para>
-
- <para>Many parts of FreeBSD aren't <quote>owned</quote> in
- the sense that any specific individual will jump up and
- yell if you commit a change to <quote>their</quote> area,
- but it still pays to check first. One convention we use
- is to put a maintainer line in the
- <filename>Makefile</filename> for any package or subtree
- which is being actively maintained by one or more people;
- see <ulink
- url="http://www.FreeBSD.org/handbook/policies.html">http://www.FreeBSD.org/handbook/policies.html</ulink>
- for documentation on this. Where sections of code have
- several maintainers, commits to affected areas by one
- maintainer need to be reviewed by at least one other
- maintainer. In cases where the
- <quote>maintainer-ship</quote> of something isn't clear,
- you can also look at the CVS logs for the file(s) in
- question and see if someone has been working recently or
- predominantly in that area.</para>
-
- <para>Other areas of FreeBSD fall under the control of
- someone who manages an overall category of FreeBSD
- evolution, such as internationalization or networking.
- See <ulink url="http://www.FreeBSD.org/handbook/staff-who.html">http://www.FreeBSD.org/handbook/staff-who.html</ulink>
- for more information on this.</para>
- </listitem>
-
- <listitem>
- <para>Never touch the repository directly. Ask a
- Repomeister.</para>
-
- <para>This is pretty clear - you're not allowed to make
- direct modifications to the CVS repository, period. In
- case of difficulty, ask one of the repository meisters by
- sending mail to <email>cvs@FreeBSD.org</email> and simply
- wait for them to fix the problem and get back to you. Do
- not attempt to fix the problem yourself!</para>
-
- <para>If you're thinking about putting down a tag or doing a
- new import of code on a vendor branch, you might also find
- it useful to ask for advice first. A lot of people get
- this wrong the first few times and the consequences are
- expensive in terms of files touched and angry CVSup/CTM
- folks who are suddenly getting a lot of changes sent over
- unnecessarily.</para>
- </listitem>
-
- <listitem>
- <para>Any disputed change must be backed out pending
- resolution of the dispute if requested by a maintainer
- Security related changes may
- override a maintainer's wishes at the Security Officer's
- discretion.</para>
-
- <para>This may be hard to swallow in times of conflict (when
- each side is convinced that they're in the right, of
- course) but CVS makes it unnecessary to have an ongoing
- dispute raging when it's far easier to simply reverse the
- disputed change, get everyone calmed down again and then
- try and figure out how best to proceed. If the change
- turns out to be the best thing after all, it can be easily
- brought back. If it turns out not to be, then the users
- didn't have to live with the bogus change in the tree
- while everyone was busily debating its merits. People
- very very rarely call for back-outs in the repository
- since discussion generally exposes bad or controversial
- changes before the commit even happens, but on such rare
- occasions the back-out should be done without argument so
- that we can get immediately on to the topic of figuring
- out whether it was bogus or not.</para>
- </listitem>
-
- <listitem>
- <para>Changes go to <literal>-CURRENT</literal> before
- <literal>-STABLE</literal> unless specifically permitted
- by the release engineer or unless they're not applicable
- to <literal>-CURRENT</literal>. Any non-trivial or
- non-urgent change which is applicable should also be
- allowed to sit in <literal>-CURRENT</literal> for at least
- 3 days before merging so that it can be given sufficient
- testing. The release engineer has the same authority over
- the <literal>-STABLE</literal> branch as outlined in rule
- #5.</para>
-
- <para>This is another <quote>don't argue about it</quote>
- issue since it's the release engineer who is ultimately
- responsible (and gets beaten up) if a change turns out to
- be bad. Please respect this and give the release engineer
- your full cooperation when it comes to the
- <literal>-STABLE</literal> branch. The management of
- <literal>-STABLE</literal> may frequently seem to be
- overly conservative to the casual observer, but also bear
- in mind the fact that conservatism is supposed to be the
- hallmark of <literal>-STABLE</literal> and different rules
- apply there than in <literal>-CURRENT</literal>. There's
- also really no point in having <literal>-CURRENT</literal>
- be a testing ground if changes are merged over to
- <literal>-STABLE</literal> immediately. Changes need a
- chance to be tested by the <literal>-CURRENT</literal>
- developers, so allow some time to elapse before merging
- unless the <literal>-STABLE</literal> fix is critical,
- time sensitive or so obvious as to make further testing
- unnecessary (spelling fixes to manpages, obvious bug/typo
- fixes, etc.) In other words, apply common sense.</para>
- </listitem>
-
- <listitem>
- <para>Don't fight in public with other committers; it looks
- bad. If you must <quote>strongly disagree</quote> about
- something, do so only in private.</para>
-
- <para>This project has a public image to uphold and that
- image is very important to all of us, especially if we are
- to continue to attract new members. There will be
- occasions when, despite everyone's very best attempts at
- self-control, tempers are lost and angry words are
- exchanged, and the best we can do is try and minimize the
- effects of this until everyone has cooled back down. That
- means that you should not air your angry words in public
- and you should not forward private correspondence to
- public mailing lists or aliases. What people say
- one-to-one is often much less sugar-coated than what they
- would say in public, and such communications therefore
- have no place there - they only serve to inflame an
- already bad situation. If the person sending you a
- flame-o-gram at least had the grace to send it privately,
- then have the grace to keep it private yourself. If you
- feel you are being unfairly treated by another developer,
- and it is causing you anguish, bring the matter up with
- core rather than taking it public. We will do our best to
- play peace makers and get things back to sanity. In cases
- where the dispute involves a change to the codebase and
- the participants do not appear to be reaching an amicable
- agreement, core may appoint a mutually-agreeable 3rd party
- to resolve the dispute. All parties involved must then
- agree to be bound by the decision reached by this 3rd
- party.</para>
- </listitem>
-
- <listitem>
- <para>Respect all code freezes and read the
- <literal>committers</literal> mailing list on a timely
- basis so you know when they are.</para>
-
- <para>Committing changes during a code freeze is a really
- big mistake and committers are expected to keep up-to-date
- on what's going on before jumping in after a long absence
- and committing 10 megabytes worth of accumulated stuff.
- People who abuse this on a regular basis will have their
- commit privileges suspended until they get back from the
- FreeBSD Happy Reeducation Camp we run in Greenland.</para>
- </listitem>
-
- <listitem>
- <para>When in doubt on any procedure, ask first!</para>
-
- <para>Many mistakes are made because someone is in a hurry
- and just assumes they know the right way of doing
- something. If you have not done it before, chances are
- good that you do not actually know the way we do things
- and really need to ask first or you are going to
- completely embarrass yourself in public. There's no shame
- in asking <quote>how in the heck do I do this?</quote> We
- already know you are an intelligent person; otherwise, you
- would not be a committer.</para>
- </listitem>
-
- <listitem>
- <para>Test your changes before committing them.</para>
-
- <para>This may sound obvious, but if it really were so
- obvious then we probably wouldn't see so many cases of
- people clearly not doing this. If your changes are to the
- kernel, make sure you can still compile both GENERIC and
- LINT. If your changes are anywhere else, make sure you
- can still make world. If your changes are to a branch,
- make sure your testing occurs with a machine which is
- running that code. If you have a change which also may
- break another architecture, be sure and test on all
- supported architectures. Currently, this is only the x86
- and the Alpha so it's pretty easy to do. If you need to
- test on the AXP, your account on <hostid
- role="fqdn">beast.FreeBSD.org</hostid> will let you
- compile and test Alpha binaries/kernels/etc. As other
- architectures are added to the FreeBSD supported platforms
- list, the appropriate shared testing resources will be
- made available.</para>
- </listitem>
- </orderedlist>
- </sect2>
-
- <sect2>
- <title>Other Suggestions</title>
-
- <para>When committing documentation changes, use a spell checker
- before committing. :) For all SGML docs, you should also
- verify that your formatting directives are correct by running
- <command>make lint</command>.</para>
-
- <para>For all on-line manual pages, run <command>manck</command>
- (from ports) over the man page to verify the all of the cross
- references and file references are correct and that the man
- page has all of the appropriate <makevar>MLINK</makevar>s
- installed.</para>
-
- <para>Do not mix style fixes with new functionality. A style
- fix is any change which does not modify the functionality of
- the code. Mixing the changes obfuscates the functionality
- change when using <command>cvs diff</command>, which can hide
- any new bugs. Do not include whitespace changes with content
- changes in commits to <filename>doc/</filename> or
- <filename>www/</filename>. The extra clutter in the diffs
- makes the translators' job much more difficult. Instead, make
- any style or whitespace changes in seperate commits that are
- clearly labeled as such in the commit message.</para>
- </sect2>
- </sect1>
-
- <sect1>
- <title>Ports Specific FAQ</title>
-
- <qandaset>
- <qandadiv>
- <title>Importing a New Port</title>
-
- <qandaentry>
- <question>
- <para>How do I import a new port?</para>
- </question>
-
- <answer>
- <para>First, please read the section about repository
- copy.</para>
-
- <para>The easiest way to import a new port is to use the
- <command>addport</command> script on
- <hostid>freefall</hostid>. It will import a port from the
- directory you specify, determining the category automatically
- from the port <filename>Makefile</filename>.
- It will also add an entry to the
- <filename>CVSROOT/modules</filename> file and the port's
- category <filename>Makefile</filename>. It was
- written by &a.mharo; and &a.will;, but Will is the current
- maintainer so please send questions/patches about
- <command>addport</command> to him.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Any other things I need to know when I import a new
- port?</para>
- </question>
-
- <answer>
- <para>Check the port, preferably to make sure it compiles
- and packages correctly. This is the recommended
- sequence:</para>
-
- <screen>&prompt.root; <userinput>make install</userinput>
-&prompt.root; <userinput>make package</userinput>
-&prompt.root; <userinput>make deinstall</userinput>
-&prompt.root; <userinput>pkg_add <replaceable>package you built above</replaceable></userinput>
-&prompt.root; <userinput>make deinstall</userinput>
-&prompt.root; <userinput>make reinstall</userinput>
-&prompt.root; <userinput>make package</userinput>
- </screen>
-
- <para>The
- <ulink url="http://www.freebsd.org/porters-handbook/index.html">Porters
- Handbook</ulink> contains more detailed
- instructions.</para>
-
- <para>Use &man.portlint.1; to check the syntax of the port.
- You don't necessarily have to eliminate all warnings but
- make sure you have fixed the simple ones.</para>
-
- <para>If the port came from a submitter who has not
- contributed to the project before, add that person's
- name to the Handbook's <citetitle
- pubwork="section">Additional Contributors</citetitle>
- section.</para>
-
- <para>Close the PR if the port came in as a PR. To close
- a PR, just do
- <userinput>edit-pr <replaceable>PR#</replaceable></userinput>
- on <hostid>freefall</hostid> and change the
- <varname>state</varname> from <constant>open</constant>
- to <constant>closed</constant>. You will be asked to
- enter a log message and then you are done.</para>
- </answer>
- </qandaentry>
- </qandadiv>
-
- <qandadiv>
- <title>Repository Copies</title>
-
- <qandaentry>
- <question>
- <para>When do we need a repository copy?</para>
- </question>
-
- <answer>
- <para>When you want to import a port that is related to
- any port that is already in the tree in a separate
- directory, please send mail to the ports manager asking
- about it. Here <wordasword>related</wordasword> means
- it is a different version or a slightly modified
- version. Examples are
- <filename>print/ghostscript*</filename> (different
- versions) and <filename>x11-wm/windowmaker*</filename>
- (English-only and internationalized version).</para>
-
- <para>Another example is when a port is moved from one
- subdirectory to another, or when you want to change the
- name of a directory because the author(s) renamed their
- software even though it is a
- descendant of a port already in a tree.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>When do we <emphasis>not</emphasis> need a
- repository copy?</para>
- </question>
-
- <answer>
- <para>When there is no history to preserve. If a port is
- imported into a wrong category and is moved immediately,
- it suffices to simply <command>cvs remove</command> the
- old one and <command>cvs import</command> the new
- one.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>What do I need to do?</para>
- </question>
-
- <answer>
- <para>Send mail to the ports manager, who will do a copy
- from the old location/name to the new location/name.
- You will then get a notice, at which point you are
- expected to perform the following:</para>
-
- <procedure>
- <step>
- <para><command>cvs remove</command> the old port (if
- necessary)</para>
- </step>
-
- <step>
- <para>Adjust the parent (category)
- <filename>Makefile</filename></para>
- </step>
-
- <step>
- <para>Update <filename>CVSROOT/modules</filename></para>
- </step>
-
- <step>
- <para>If other ports depend on the updated port,
- change their <filename>Makefile</filename>s'
- dependency lines</para>
- </step>
-
- <step>
- <para>If the port changed categories, modify the
- <makevar>CATEGORIES</makevar> line of the port's
- <filename>Makefile</filename> accordingly</para>
- </step>
- </procedure>
- </answer>
- </qandaentry>
- </qandadiv>
-
- <qandadiv>
- <title>Ports Freeze</title>
-
- <qandaentry>
- <question>
- <para>What is a <quote>ports freeze</quote>?</para>
- </question>
-
- <answer>
- <para>Before a release, it is necessary to restrict
- commits to the ports tree for a short period of time
- while the packages and the release itself are being
- built. This is to ensure consistency among the various
- parts of the release, and is called the <quote>ports
- freeze</quote>.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>How long is a ports freeze?</para>
- </question>
-
- <answer>
- <para>Usually an hour or two.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>What does it mean to me?</para>
- </question>
-
- <answer>
- <para>During the ports freeze, you are not allowed to
- commit anything to the tree without explicit approval
- from the ports manager. <quote>Explicit
- approval</quote> here means either of the
- following:</para>
-
- <itemizedlist>
- <listitem>
- <para>You asked the ports manager and got a reply
- saying, <quote>Go ahead and commit
- it.</quote></para>
- </listitem>
-
- <listitem>
- <para>The ports manager sent a mail to you or the
- mailing lists during the ports freeze pointing out
- that the port is broken and has to be fixed.</para>
- </listitem>
- </itemizedlist>
-
- <para>Note that you do not have implicit permission to fix
- a port during the freeze just because it is
- broken.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>How do I know when the ports freeze starts?</para>
- </question>
-
- <answer>
- <para>The ports manager will send out warning messages to
- the <email>freebsd-ports@FreeBSD.org</email> and
- <email>cvs-committers@FreeBSD.org</email> mailing lists
- announcing the start of the impending release, usually
- two or three weeks in advance. The exact starting time
- will not be determined until a few days before the
- actual release. This is because the ports freeze has to
- be synchronized with the release, and it is usually not
- known until then when exactly the release will be
- rolled.</para>
-
- <para>When the freeze starts, there will be another
- announcement to the
- <email>cvs-committers@FreeBSD.org</email> list, of
- course.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>How do I know when the ports freeze ends?</para>
- </question>
-
- <answer>
- <para>A few hours after the release, the ports manager
- will send out a mail to the
- <email>freebsd-ports@FreeBSD.org</email> and
- <email>cvs-committers@FreeBSD.org</email> mailing lists
- announcing the end of the ports freeze. Note that the
- release being cut does not automatically end the freeze.
- We have to make sure there will not be any last minute
- snafus that result in an immediate re-rolling of the
- release.</para>
- </answer>
- </qandaentry>
- </qandadiv>
-
- <qandadiv>
- <title>Miscellaneous Questions</title>
-
- <qandaentry>
- <question>
- <para>How do I know if my port is building correctly or
- not?</para>
- </question>
-
- <answer>
- <para>First, go check
- <ulink url="http://bento.FreeBSD.org/~asami/errorlogs/">http://bento.FreeBSD.org/~asami/errorlogs/</ulink>.
-
- There you will find error logs from the latest package
- building runs on 3-stable, 4-stable and 5-current.</para>
-
- <para>However, just because the port doesn't show up there
- doesn't mean it's building correctly. (One of the
- dependencies may have failed, for instance.) Here are
- the relevant directories on bento, so feel free to dig
- around.</para>
-
- <programlisting> /a/asami/portbuild/3/errors error logs from latest 3-stable run
- /logs all logs from latest 3-stable run
- /packages packages from latest 3-stable run
- /bak/errors error logs from last complete 3-stable run
- /bak/logs all logs from last complete 3-stable run
- /bak/packages packages from last complete 3-stable run
- /4/errors error logs from latest 4-stable run
- /logs all logs from latest 4-stable run
- /packages packages from latest 4-stable run
- /bak/errors error logs from last complete 4-stable run
- /bak/logs all logs from last complete 4-stable run
- /bak/packages packages from last complete 4-stable run
- /5/errors error logs from latest 5-current run
- /logs all logs from latest 5-current run
- /packages packages from latest 5-current run
- /bak/errors error logs from last complete 5-current run
- /bak/logs all logs from last complete 5-current run
- /bak/packages packages from last complete 5-current run
- </programlisting>
-
- <para>Basically, if the port shows up in
- <filename>packages</filename>, or it is in
- <filename>logs</filename> but not in
- <filename>errors</filename>, it built fine. (The
- <filename>errors</filename> directories are what you get
- from the web page.)</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>I added a new port. Do I need to add it to the
- <filename>INDEX</filename>?</para>
- </question>
-
- <answer>
- <para>No. The ports manager will regenerate the
- <filename>INDEX</filename> and commit it every few
- days.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>Are there any other files I'm not allowed to
- touch?</para>
- </question>
-
- <answer>
- <para>Any file directly under <filename>ports/</filename>, or
- any file under a subdirectory that starts with an
- uppercase letter (<filename>Mk/</filename>,
- <filename>Tools/</filename>, etc.). In particular, the
- ports manager is very protective of
- <filename>ports/Mk/bsd.port*.mk</filename> so don't
- commit changes to those files unless you want to face his
- wra(i)th.</para>
- </answer>
- </qandaentry>
- </qandadiv>
- </qandaset>
- </sect1>
-
- <sect1>
- <title>Miscellaneous Questions</title>
-
- <qandaset>
- <qandaentry>
- <question>
- <para>Why are trivial or cosmetic changes to files on a vendor
- branch a bad idea?</para>
- </question>
-
- <answer>
- <para>The RCS file format is quite braindead and certain
- operations to achieve things for CVS are hideously
- expensive for the repository. Making changes to files on
- a vendor branch, thereby pulling the file off that branch,
- is one example of this.</para>
-
- <para>Suppose you have a file which was first imported on a
- vendor branch, and was then re-imported three times (still
- on the vendor branch) as the vendor makes updates to the
- file.</para>
-
- <segmentedlist>
- <seglistitem>
- <seg>1.1.1.1</seg>
- <seg>vendor import</seg>
- </seglistitem>
-
- <seglistitem>
- <seg>1.1.1.2</seg>
- <seg>vendor import, +1000, -500 lines</seg>
- </seglistitem>
-
- <seglistitem>
- <seg>1.1.1.3</seg>
- <seg>vendor import, +2000, -500 lines</seg>
- </seglistitem>
-
- <seglistitem>
- <seg>1.1.1.4</seg>
- <seg>vendor import, +1000, -1000 lines</seg>
- </seglistitem>
- </segmentedlist>
-
- <para>Now suppose that one of the FreeBSD committers makes a
- one line change to this file, causing it to go to version
- 1.2. This causes it to leave the branch, resulting in
- 4,001 lines being added to the file's history, and 2,001
- lines being deleted.</para>
-
- <para>This is because the 1.2 delta is stored relative to
- 1.1.1.1, <emphasis>not</emphasis> 1.1.1.4, and so the
- entire vendor history is duplicated in the 1.2 delta.
- Now, repeat this for 2000 files in a large directory, it
- adds up a lot.</para>
-
- <para><emphasis>This</emphasis> is why we have such
- <quote>hands off</quote> policies for
- <filename>src/contrib</filename> and other things that
- track the vendor releases. This is why <quote>typo
- fixes</quote> in man pages and spelling
- <quote>corrections</quote> are so strongly discouraged for
- vendor code.</para>
- </answer>
- </qandaentry>
-
- <qandaentry>
- <question>
- <para>How do I add a new file to a CVS branch?</para>
- </question>
-
- <answer>
- <para>To add a file onto a branch, simply checkout or update
- to the branch you want to add to and then add the file using
- <command>cvs add</command> as you normally would. For
- example, if you wanted to MFC the file
- <filename>src/sys/alpha/include/smp.h</filename> from HEAD
- to RELENG_4 and it does not exist in RELENG_4 yet, you would
- use the following steps:</para>
-
- <example>
- <title>MFC'ing a New File</title>
-
- <screen>&prompt.user; <userinput>cd sys/alpha/include</userinput>
-&prompt.user; <userinput>cvs update -rRELENG_4</userinput>
-cvs update: Updating .
-U clockvar.h
-U console.h
-...
-&prompt.user; <userinput>cvs update -kk -Ap smp.h &gt; smp.h</userinput>
-===================================================================
-Checking out smp.h
-RCS: /usr/cvs/src/sys/alpha/include/smp.h,v
-VERS: 1.1
-***************
-&prompt.user; <userinput>cvs add smp.h</userinput>
-cvs add: scheduling file `smp.h' for addition on branch `RELENG_4'
-cvs add: use 'cvs commit' to add this file permanently
-&prompt.user; <userinput>cvs commit</userinput>
- </screen>
- </example>
- </answer>
- </qandaentry>
- </qandaset>
- </sect1>
-</article>
diff --git a/en_US.ISO8859-1/articles/contributing/article.sgml b/en_US.ISO8859-1/articles/contributing/article.sgml
deleted file mode 100644
index 7144714cd4..0000000000
--- a/en_US.ISO8859-1/articles/contributing/article.sgml
+++ /dev/null
@@ -1,6224 +0,0 @@
-<!--
- The FreeBSD Documentation Project
-
- $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/contrib/chapter.sgml,v 1.337 2000/11/13 19:22:53 okazaki Exp $
--->
-
-<chapter id="contrib">
- <title>Contributing to FreeBSD</title>
-
- <para><emphasis>Contributed by &a.jkh;.</emphasis></para>
-
- <para>So you want to contribute something to FreeBSD? That is great! We can
- always use the help, and FreeBSD is one of those systems that
- <emphasis>relies</emphasis> on the contributions of its user base in order
- to survive. Your contributions are not only appreciated, they are vital
- to FreeBSD's continued growth!</para>
-
- <para>Contrary to what some people might also have you believe, you do not
- need to be a hot-shot programmer or a close personal friend of the FreeBSD
- core team in order to have your contributions accepted. The FreeBSD
- Project's development is done by a large and growing number of
- international contributors whose ages and areas of technical expertise
- vary greatly, and there is always more work to be done than there are
- people available to do it.</para>
-
- <para>Since the FreeBSD project is responsible for an entire operating
- system environment (and its installation) rather than just a kernel or a
- few scattered utilities, our <filename>TODO</filename> list also spans a
- very wide range of tasks, from documentation, beta testing and
- presentation to highly specialized types of kernel development. No matter
- what your skill level, there is almost certainly something you can do to
- help the project!</para>
-
- <para>Commercial entities engaged in FreeBSD-related enterprises are also
- encouraged to contact us. Need a special extension to make your product
- work? You will find us receptive to your requests, given that they are not
- too outlandish. Working on a value-added product? Please let us know! We
- may be able to work cooperatively on some aspect of it. The free software
- world is challenging a lot of existing assumptions about how software is
- developed, sold, and maintained throughout its life cycle, and we urge you
- to at least give it a second look.</para>
-
- <sect1 id="contrib-what">
- <title>What is Needed</title>
-
- <para>The following list of tasks and sub-projects represents something of
- an amalgam of the various core team <filename>TODO</filename> lists and
- user requests we have collected over the last couple of months. Where
- possible, tasks have been ranked by degree of urgency. If you are
- interested in working on one of the tasks you see here, send mail to the
- coordinator listed by clicking on their names. If no coordinator has
- been appointed, maybe you would like to volunteer?</para>
-
- <sect2>
- <title>High priority tasks</title>
-
- <para>The following tasks are considered to be urgent, usually because
- they represent something that is badly broken or sorely needed:</para>
-
- <orderedlist>
- <listitem>
- <para>3-stage boot issues. Overall coordination: &a.hackers;</para>
-
- <itemizedlist>
- <listitem>
- <para>Do WinNT compatible drive tagging so that the 3rd stage
- can provide an accurate mapping of BIOS geometries for
- disks.</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>Filesystem problems. Overall coordination: &a.fs;</para>
-
- <itemizedlist>
- <listitem>
- <para>Clean up and document the nullfs filesystem code.
- Coordinator: &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Fix the union file system. Coordinator: &a.dg;</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>Implement Int13 vm86 disk driver. Coordinator:
- &a.hackers;</para>
- </listitem>
-
- <listitem>
- <para>New bus architecture. Coordinator: &a.newbus;</para>
-
- <itemizedlist>
- <listitem>
- <para>Port existing ISA drivers to new architecture.</para>
- </listitem>
-
- <listitem>
- <para>Move all interrupt-management code to appropriate parts of
- the bus drivers.</para>
- </listitem>
-
- <listitem>
- <para>Port PCI subsystem to new architecture. Coordinator:
- &a.dfr;</para>
- </listitem>
-
- <listitem>
- <para>Figure out the right way to handle removable devices and
- then use that as a substrate on which PC-Card and CardBus
- support can be implemented.</para>
- </listitem>
-
- <listitem>
- <para>Resolve the probe/attach priority issue once and for
- all.</para>
- </listitem>
-
- <listitem>
- <para>Move any remaining buses over to the new
- architecture.</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>Kernel issues. Overall coordination: &a.hackers;</para>
- </listitem>
-
- <listitem>
- <para>Add more pro-active security infrastructure. Overall
- coordination: &a.security;</para>
-
- <itemizedlist>
- <listitem>
- <para>Build something like Tripwire(TM) into the kernel, with a
- remote and local part. There are a number of cryptographic
- issues to getting this right; contact the coordinator for
- details. Coordinator: &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Make the entire kernel use <literal>suser()</literal>
- instead of comparing to 0. It is presently using about half
- of each. Coordinator: &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Split securelevels into different parts, to allow an
- administrator to throw away those privileges he can throw
- away. Setting the overall securelevel needs to have the same
- effect as now, obviously. Coordinator: &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Make it possible to upload a list of <quote>allowed
- program</quote> to BPF, and then block BPF from accepting other
- programs. This would allow BPF to be used e.g. for DHCP,
- without allowing an attacker to start snooping the local
- network.</para>
- </listitem>
-
- <listitem>
- <para>Update the security checker script. We should at least
- grab all the checks from the other BSD derivatives, and add
- checks that a system with securelevel increased also have
- reasonable flags on the relevant parts. Coordinator:
- &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Add authorization infrastructure to the kernel, to allow
- different authorization policies. Part of this could be done
- by modifying <literal>suser()</literal>. Coordinator:
- &a.eivind;</para>
- </listitem>
-
- <listitem>
- <para>Add code to the NFS layer so that you cannot
- <literal>chdir("..")</literal> out of an NFS partition. E.g.,
- <filename>/usr</filename> is a UFS partition with
- <filename>/usr/src</filename> NFS exported. Now it is
- possible to use the NFS filehandle for
- <filename>/usr/src</filename> to get access to
- <filename>/usr</filename>.</para>
- </listitem>
- </itemizedlist>
- </listitem>
- </orderedlist>
- </sect2>
-
- <sect2>
- <title>Medium priority tasks</title>
-
- <para>The following tasks need to be done, but not with any particular
- urgency:</para>
-
- <orderedlist>
- <listitem>
- <para>Full KLD based driver support/Configuration Manager.</para>
-
- <itemizedlist>
- <listitem>
- <para>Write a configuration manager (in the 3rd stage boot?)
- that probes your hardware in a sane manner, keeps only the
- KLDs required for your hardware, etc.</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>PCMCIA/PCCARD. Coordinators: &a.msmith; and &a.imp;</para>
-
- <itemizedlist>
- <listitem>
- <para>Documentation!</para>
- </listitem>
-
- <listitem>
- <para>Reliable operation of the pcic driver (needs
- testing).</para>
- </listitem>
-
- <listitem>
- <para>Recognizer and handler for <filename>sio.c</filename>
- (mostly done).</para>
- </listitem>
-
- <listitem>
- <para>Recognizer and handler for <filename>ed.c</filename>
- (mostly done).</para>
- </listitem>
-
- <listitem>
- <para>Recognizer and handler for <filename>ep.c</filename>
- (mostly done).</para>
- </listitem>
-
- <listitem>
- <para>User-mode recognizer and handler (partially done).</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para>Advanced Power Management. Coordinators: &a.msmith; and
- &a.phk;</para>
-
- <itemizedlist>
- <listitem>
- <para>APM sub-driver (mostly done).</para>
- </listitem>
-
- <listitem>
- <para>IDE/ATA disk sub-driver (partially done).</para>
- </listitem>
-
- <listitem>
- <para>syscons/pcvt sub-driver.</para>
- </listitem>
-
- <listitem>
- <para>Integration with the PCMCIA/PCCARD drivers
- (suspend/resume).</para>
- </listitem>
- </itemizedlist>
- </listitem>
- </orderedlist>
- </sect2>
-
- <sect2>
- <title>Low priority tasks</title>
-
- <para>The following tasks are purely cosmetic or represent such an
- investment of work that it is not likely that anyone will get them
- done anytime soon:</para>
-
- <para>The first N items are from Terry Lambert
- <email>terry@lambert.org</email></para>
-
- <orderedlist>
- <listitem>
- <para>NetWare Server (protected mode ODI driver) loader and
- sub-services to allow the use of ODI card drivers supplied with
- network cards. The same thing for NDIS drivers and NetWare SCSI
- drivers.</para>
- </listitem>
-
- <listitem>
- <para>An "upgrade system" option that works on Linux boxes instead
- of just previous rev FreeBSD boxes.</para>
- </listitem>
-
- <listitem>
- <para>Symmetric Multiprocessing with kernel preemption (requires
- kernel preemption).</para>
- </listitem>
-
- <listitem>
- <para>A concerted effort at support for portable computers. This is
- somewhat handled by changing PCMCIA bridging rules and power
- management event handling. But there are things like detecting
- internal v.s.. external display and picking a different screen
- resolution based on that fact, not spinning down the disk if the
- machine is in dock, and allowing dock-based cards to disappear
- without affecting the machines ability to boot (same issue for
- PCMCIA).</para>
- </listitem>
- </orderedlist>
- </sect2>
-
- <sect2>
- <title>Smaller tasks</title>
-
- <para>Most of the tasks listed in the previous sections require either a
- considerable investment of time or an in-depth knowledge of the
- FreeBSD kernel (or both). However, there are also many useful tasks
- which are suitable for &quot;weekend hackers&quot;, or people without
- programming skills.</para>
-
- <orderedlist>
- <listitem>
- <para>If you run FreeBSD-current and have a good Internet
- connection, there is a machine <hostid
- role="fqdn">current.FreeBSD.org</hostid> which builds a full
- release once a day &mdash; every now and again, try and install
- the latest release from it and report any failures in the
- process.</para>
- </listitem>
-
- <listitem>
- <para>Read the freebsd-bugs mailing list. There might be a
- problem you can comment constructively on or with patches you
- can test. Or you could even try to fix one of the problems
- yourself.</para>
- </listitem>
-
- <listitem>
- <para>Read through the FAQ and Handbook periodically. If anything
- is badly explained, out of date or even just completely wrong, let
- us know. Even better, send us a fix (SGML is not difficult to
- learn, but there is no objection to ASCII submissions).</para>
- </listitem>
-
- <listitem>
- <para>Help translate FreeBSD documentation into your native language
- (if not already available) &mdash; just send an email to &a.doc;
- asking if anyone is working on it. Note that you are not
- committing yourself to translating every single FreeBSD document
- by doing this &mdash; in fact, the documentation most in need of
- translation is the installation instructions.</para>
- </listitem>
-
- <listitem>
- <para>Read the freebsd-questions mailing list and &ng.misc
- occasionally (or even regularly). It can be very satisfying to
- share your expertise and help people solve their problems;
- sometimes you may even learn something new yourself! These forums
- can also be a source of ideas for things to work on.</para>
- </listitem>
-
- <listitem>
- <para>If you know of any bug fixes which have been successfully
- applied to -current but have not been merged into -stable after a
- decent interval (normally a couple of weeks), send the committer a
- polite reminder.</para>
- </listitem>
-
- <listitem>
- <para>Move contributed software to <filename>src/contrib</filename>
- in the source tree.</para>
- </listitem>
-
- <listitem>
- <para>Make sure code in <filename>src/contrib</filename> is up to
- date.</para>
- </listitem>
-
- <listitem>
- <para>Look for year 2000 bugs (and fix any you find!)</para>
- </listitem>
-
- <listitem>
- <para>Build the source tree (or just part of it) with extra warnings
- enabled and clean up the warnings.</para>
- </listitem>
-
- <listitem>
- <para>Fix warnings for ports which do deprecated things like using
- gets() or including malloc.h.</para>
- </listitem>
-
- <listitem>
- <para>If you have contributed any ports, send your patches back to
- the original author (this will make your life easier when they
- bring out the next version)</para>
- </listitem>
-
- <listitem>
- <para>Suggest further tasks for this list!</para>
- </listitem>
- </orderedlist>
- </sect2>
-
- <sect2>
- <title>Work through the PR database</title>
-
- <para>The <ulink
- url="http://www.FreeBSD.org/cgi/query-pr-summary.cgi">FreeBSD PR
- list</ulink> shows all the current active problem reports and
- requests for enhancement that have been submitted by FreeBSD users.
- Look through the open PRs, and see if anything there takes your
- interest. Some of these might be very simple tasks, that just need an
- extra pair of eyes to look over them and confirm that the fix in the
- PR is a good one. Others might be much more complex.</para>
-
- <para>Start with the PRs that have not been assigned to anyone else, but
- if one them is assigned to someone else, but it looks like something
- you can handle, e-mail the person it is assigned to and ask if you can
- work on it&mdash;they might already have a patch ready to be tested,
- or further ideas that you can discuss with them.</para>
- </sect2>
- </sect1>
-
- <sect1 id="contrib-how">
- <title>How to Contribute</title>
-
- <para>Contributions to the system generally fall into one or more of the
- following 6 categories:</para>
-
- <sect2 id="contrib-general">
- <title>Bug reports and general commentary</title>
-
- <para>An idea or suggestion of <emphasis>general</emphasis> technical
- interest should be mailed to the &a.hackers;. Likewise, people with
- an interest in such things (and a tolerance for a
- <emphasis>high</emphasis> volume of mail!) may subscribe to the
- hackers mailing list by sending mail to &a.majordomo;. See <link
- linkend="eresources-mail">mailing lists</link> for more information
- about this and other mailing lists.</para>
-
- <para>If you find a bug or are submitting a specific change, please
- report it using the &man.send-pr.1; program or its <ulink
- url="http://www.FreeBSD.org/send-pr.html">WEB-based
- equivalent</ulink>. Try to fill-in each field of the bug report.
- Unless they exceed 65KB, include any patches directly in the report.
- When including patches, <emphasis>do not</emphasis> use cut-and-paste
- because cut-and-paste turns tabs into spaces and makes them unusable.
- Consider compressing patches and using &man.uuencode.1; if they exceed
- 20KB. Upload very large submissions to <ulink
- url="ftp://ftp.FreeBSD.org/pub/FreeBSD/incoming/">ftp.FreeBSD.org:/pub/FreeBSD/incoming/</ulink>.</para>
-
- <para>After filing a report, you should receive confirmation along with
- a tracking number. Keep this tracking number so that you can update
- us with details about the problem by sending mail to
- <email>bug-followup@FreeBSD.org</email>. Use the number as the
- message subject, e.g. <literal>"Re: kern/3377"</literal>. Additional
- information for any bug report should be submitted this way.</para>
-
- <para>If you do not receive confirmation in a timely fashion (3 days to
- a week, depending on your email connection) or are, for some reason,
- unable to use the &man.send-pr.1; command, then you may ask
- someone to file it for you by sending mail to the &a.bugs;.</para>
- </sect2>
-
- <sect2>
- <title>Changes to the documentation</title>
-
- <para>Changes to the documentation are overseen by the &a.doc;. Send
- submissions and changes (even small ones are welcome!) using
- <command>send-pr</command> as described in <link
- linkend="contrib-general">Bug Reports and General
- Commentary</link>.</para>
- </sect2>
-
- <sect2>
- <title>Changes to existing source code</title>
-
- <para>An addition or change to the existing source code is a somewhat
- trickier affair and depends a lot on how far out of date you are with
- the current state of the core FreeBSD development. There is a special
- on-going release of FreeBSD known as <quote>FreeBSD-current</quote>
- which is made available in a variety of ways for the convenience of
- developers working actively on the system. See <link
- linkend="current">Staying current with FreeBSD</link> for more
- information about getting and using FreeBSD-current.</para>
-
- <para>Working from older sources unfortunately means that your changes
- may sometimes be too obsolete or too divergent for easy re-integration
- into FreeBSD. Chances of this can be minimized somewhat by
- subscribing to the &a.announce; and the &a.current; lists, where
- discussions on the current state of the system take place.</para>
-
- <para>Assuming that you can manage to secure fairly up-to-date sources
- to base your changes on, the next step is to produce a set of diffs to
- send to the FreeBSD maintainers. This is done with the &man.diff.1;
- command, with the <quote>context diff</quote> form
- being preferred. For example:</para>
-
- <para>
- <screen>&prompt.user; <userinput>diff -c oldfile newfile</userinput></screen>
-
- or
-
- <screen>&prompt.user; <userinput>diff -c -r olddir newdir</userinput></screen>
-
- would generate such a set of context diffs for the given source file
- or directory hierarchy. See the man page for &man.diff.1; for more
- details.</para>
-
- <para>Once you have a set of diffs (which you may test with the
- &man.patch.1; command), you should submit them for inclusion with
- FreeBSD. Use the &man.send-pr.1; program as described in <link
- linkend="contrib-general">Bug Reports and General Commentary</link>.
- <emphasis>Do not</emphasis> just send the diffs to the &a.hackers; or
- they will get lost! We greatly appreciate your submission (this is a
- volunteer project!); because we are busy, we may not be able to
- address it immediately, but it will remain in the pr database until we
- do.</para>
-
- <para>If you feel it appropriate (e.g. you have added, deleted, or
- renamed files), bundle your changes into a <command>tar</command> file
- and run the &man.uuencode.1; program on it. Shar archives are also
- welcome.</para>
-
- <para>If your change is of a potentially sensitive nature, e.g. you are
- unsure of copyright issues governing its further distribution or you
- are simply not ready to release it without a tighter review first,
- then you should send it to &a.core; directly rather than submitting it
- with &man.send-pr.1;. The core mailing list reaches a much smaller
- group of people who do much of the day-to-day work on FreeBSD. Note
- that this group is also <emphasis>very busy</emphasis> and so you
- should only send mail to them where it is truly necessary.</para>
-
- <para>Please refer to <command>man 9 intro</command> and <command>man 9
- style</command> for some information on coding style. We would
- appreciate it if you were at least aware of this information before
- submitting code.</para>
- </sect2>
-
- <sect2>
- <title>New code or major value-added packages</title>
-
- <para>In the case of a significant contribution of a large body
- work, or the addition of an important new feature to FreeBSD, it
- becomes almost always necessary to either send changes as uuencoded
- tar files or upload them to a web or FTP site for other people to
- access. If you do not have access to a web or FTP site, ask on an
- appropriate FreeBSD mailing list for someone to host the changes for
- you.</para>
-
- <para>When working with large amounts of code, the touchy subject of
- copyrights also invariably comes up. Acceptable copyrights for code
- included in FreeBSD are:</para>
-
- <orderedlist>
- <listitem>
- <para>The BSD copyright. This copyright is most preferred due to
- its <quote>no strings attached</quote> nature and general
- attractiveness to commercial enterprises. Far from discouraging
- such commercial use, the FreeBSD Project actively encourages such
- participation by commercial interests who might eventually be
- inclined to invest something of their own into FreeBSD.</para>
- </listitem>
-
- <listitem>
- <para>The GNU Public License, or <quote>GPL</quote>. This license is
- not quite as popular with us due to the amount of extra effort
- demanded of anyone using the code for commercial purposes, but
- given the sheer quantity of GPL'd code we currently require
- (compiler, assembler, text formatter, etc) it would be silly to
- refuse additional contributions under this license. Code under
- the GPL also goes into a different part of the tree, that being
- <filename>/sys/gnu</filename> or
- <filename>/usr/src/gnu</filename>, and is therefore easily
- identifiable to anyone for whom the GPL presents a problem.</para>
- </listitem>
- </orderedlist>
-
- <para>Contributions coming under any other type of copyright must be
- carefully reviewed before their inclusion into FreeBSD will be
- considered. Contributions for which particularly restrictive
- commercial copyrights apply are generally rejected, though the authors
- are always encouraged to make such changes available through their own
- channels.</para>
-
- <para>To place a <quote>BSD-style</quote> copyright on your work, include
- the following text at the very beginning of every source code file you
- wish to protect, replacing the text between the <literal>%%</literal>
- with the appropriate information.</para>
-
- <programlisting>
-Copyright (c) %%proper_years_here%%
- %%your_name_here%%, %%your_state%% %%your_zip%%.
- All rights reserved.
-
-Redistribution and use in source and binary forms, with or without
-modification, are permitted provided that the following conditions
-are met:
-1. Redistributions of source code must retain the above copyright
- notice, this list of conditions and the following disclaimer as
- the first lines of this file unmodified.
-2. Redistributions in binary form must reproduce the above copyright
- notice, this list of conditions and the following disclaimer in the
- documentation and/or other materials provided with the distribution.
-
-THIS SOFTWARE IS PROVIDED BY %%your_name_here%% ``AS IS'' AND ANY EXPRESS OR
-IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
-OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
-IN NO EVENT SHALL %%your_name_here%% BE LIABLE FOR ANY DIRECT, INDIRECT,
-INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
-NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
-THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
- &#36;Id&#36;</programlisting>
-
- <para>For your convenience, a copy of this text can be found in
- <filename>/usr/share/examples/etc/bsd-style-copyright</filename>.</para>
- </sect2>
-
- <sect2>
- <title>Money, Hardware or Internet access</title>
-
- <para>We are always very happy to accept donations to further the cause
- of the FreeBSD Project and, in a volunteer effort like ours, a little
- can go a long way! Donations of hardware are also very important to
- expanding our list of supported peripherals since we generally lack
- the funds to buy such items ourselves.</para>
-
- <sect3>
- <title><anchor id="donations">Donating funds</title>
-
- <para>While the FreeBSD Project is not a 501(c)(3) (charitable)
- corporation and hence cannot offer special tax incentives for any
- donations made, any such donations will be gratefully accepted on
- behalf of the project by FreeBSD, Inc.</para>
-
- <para>FreeBSD, Inc. was founded in early 1995 by &a.jkh; and &a.dg;
- with the goal of furthering the aims of the FreeBSD Project and
- giving it a minimal corporate presence. Any and all funds donated
- (as well as any profits that may eventually be realized by FreeBSD,
- Inc.) will be used exclusively to further the project's
- goals.</para>
-
- <para>Please make any checks payable to FreeBSD, Inc., sent in care of
- the following address:</para>
-
- <address>
- <otheraddr>FreeBSD, Inc.</otheraddr>
- <otheraddr>c/o Jordan Hubbard</otheraddr>
- <street>4041 Pike Lane, Suite F</street>
- <city>Concord</city>
- <state>CA</state>, <postcode>94520</postcode>
- </address>
-
- <para>(currently using the BSDi address until a PO box
- can be opened)</para>
-
- <para>Wire transfers may also be sent directly to:</para>
-
- <address>
- <otheraddr>Bank Of America</otheraddr>
- <otheraddr>Concord Main Office</otheraddr>
- <pob>P.O. Box 37176</pob>
- <city>San Francisco</city>
- <state>CA</state>, <postcode>94137-5176</postcode>
-
- <otheraddr>Routing #: 121-000-358</otheraddr>
- <otheraddr>Account #: 01411-07441 (FreeBSD, Inc.)</otheraddr>
- </address>
-
- <para>Any correspondence related to donations should be sent to &a.jkh,
- either via email or to the FreeBSD, Inc. postal address given above.
- </para>
-
- <para>If you do not wish to be listed in our <link
- linkend="donors">donors</link> section, please specify this when
- making your donation. Thanks!</para>
- </sect3>
-
- <sect3>
- <title>Donating hardware</title>
-
- <para>Donations of hardware in any of the 3 following categories are
- also gladly accepted by the FreeBSD Project:</para>
-
- <itemizedlist>
- <listitem>
- <para>General purpose hardware such as disk drives, memory or
- complete systems should be sent to the FreeBSD, Inc. address
- listed in the <emphasis>donating funds</emphasis>
- section.</para>
- </listitem>
-
- <listitem>
- <para>Hardware for which ongoing compliance testing is desired.
- We are currently trying to put together a testing lab of all
- components that FreeBSD supports so that proper regression
- testing can be done with each new release. We are still lacking
- many important pieces (network cards, motherboards, etc) and if
- you would like to make such a donation, please contact &a.dg;
- for information on which items are still required.</para>
- </listitem>
-
- <listitem>
- <para>Hardware currently unsupported by FreeBSD for which you
- would like to see such support added. Please contact the
- &a.core; before sending such items as we will need to find a
- developer willing to take on the task before we can accept
- delivery of new hardware.</para>
- </listitem>
- </itemizedlist>
- </sect3>
-
- <sect3>
- <title>Donating Internet access</title>
-
- <para>We can always use new mirror sites for FTP, WWW or
- <command>cvsup</command>. If you would like to be such a mirror,
- please contact the FreeBSD project administrators
- <email>hubs@FreeBSD.org</email> for more information.</para>
- </sect3>
- </sect2>
- </sect1>
-
- <sect1 id="donors">
- <title>Donors Gallery</title>
-
- <para>The FreeBSD Project is indebted to the following donors and would
- like to publicly thank them here!</para>
-
- <itemizedlist>
- <listitem>
- <para><emphasis>Contributors to the central server
- project:</emphasis></para>
-
- <para>The following individuals and businesses made it possible for
- the FreeBSD Project to build a new central server machine to
- eventually replace <hostid role="fqdn">freefall.FreeBSD.org</hostid>
- by donating the following items:</para>
-
- <itemizedlist>
- <listitem>
- <para>&a.mbarkah and his employer, <ulink url="http://www.hemi.com/">
- Hemisphere Online</ulink>, donated a <emphasis>Pentium Pro
- (P6) 200Mhz CPU</emphasis></para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.asacomputers.com/">ASA
- Computers</ulink> donated a <emphasis>Tyan 1662
- motherboard</emphasis>.</para>
- </listitem>
-
- <listitem>
- <para>Joe McGuckin <email>joe@via.net</email> of <ulink
- url="http://www.via.net/">ViaNet Communications</ulink> donated
- a <emphasis>Kingston ethernet controller.</emphasis></para>
- </listitem>
-
- <listitem>
- <para>Jack O'Neill <email>jack@diamond.xtalwind.net</email>
- donated an <emphasis>NCR 53C875 SCSI controller
- card</emphasis>.</para>
- </listitem>
-
- <listitem>
- <para>Ulf Zimmermann <email>ulf@Alameda.net</email> of <ulink
- url="http://www.Alameda.net/">Alameda Networks</ulink> donated
- <emphasis>128MB of memory</emphasis>, a <emphasis>4 Gb disk
- drive and the case.</emphasis></para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para><emphasis>Direct funding:</emphasis></para>
-
- <para>The following individuals and businesses have generously
- contributed direct funding to the project:</para>
-
- <itemizedlist>
- <listitem>
- <para>Annelise Anderson
- <email>ANDRSN@HOOVER.STANFORD.EDU</email></para>
- </listitem>
-
- <listitem>
- <para>&a.dillon</para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.bluemountain.com/">Blue Mountain
- Arts</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.epilogue.com/">Epilogue Technology
- Corporation</ulink></para>
- </listitem>
-
- <listitem>
- <para>&a.sef</para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.gta.com/">Global Technology
- Associates, Inc</ulink></para>
- </listitem>
-
- <listitem>
- <para>Don Scott Wilde</para>
- </listitem>
-
- <listitem>
- <para>Gianmarco Giovannelli
- <email>gmarco@masternet.it</email></para>
- </listitem>
-
- <listitem>
- <para>Josef C. Grosch <email>joeg@truenorth.org</email></para>
- </listitem>
-
- <listitem>
- <para>Robert T. Morris</para>
- </listitem>
-
- <listitem>
- <para>&a.chuckr</para>
- </listitem>
-
- <listitem>
- <para>Kenneth P. Stox <email>ken@stox.sa.enteract.com</email> of
- <ulink url="http://www.imagescape.com/">Imaginary Landscape,
- LLC.</ulink></para>
- </listitem>
-
- <listitem>
- <para>Dmitry S. Kohmanyuk <email>dk@dog.farm.org</email></para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.cdrom.co.jp/">Laser5</ulink> of Japan
- (a portion of the profits from sales of their various FreeBSD
- CDROMs).</para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.mmjp.or.jp/fuki/">Fuki Shuppan
- Publishing Co.</ulink> donated a portion of their profits from
- <emphasis>Hajimete no FreeBSD</emphasis> (FreeBSD, Getting
- started) to the FreeBSD and XFree86 projects.</para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.ascii.co.jp/">ASCII Corp.</ulink>
- donated a portion of their profits from several FreeBSD-related
- books to the FreeBSD project.</para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.yokogawa.co.jp/">Yokogawa Electric
- Corp</ulink> has generously donated significant funding to the
- FreeBSD project.</para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.buffnet.net/">BuffNET</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.pacificsolutions.com/">Pacific
- Solutions</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.siemens.de/">Siemens AG</ulink>
- via <ulink url="mailto:andre.albsmeier@mchp.siemens.de">Andre
- Albsmeier</ulink></para>
- </listitem>
-
- <listitem>
- <para><ulink url="mailto:ras@interaccess.com">Chris Silva</ulink>
- </para>
- </listitem>
-
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para><emphasis>Hardware contributors:</emphasis></para>
-
- <para>The following individuals and businesses have generously
- contributed hardware for testing and device driver
- development/support:</para>
-
- <itemizedlist>
- <listitem>
- <para>BSDi for providing the Pentium P5-90 and
- 486/DX2-66 EISA/VL systems that are being used for our
- development work, to say nothing of the network access and other
- donations of hardware resources.</para>
- </listitem>
-
- <listitem>
- <para>TRW Financial Systems, Inc. provided 130 PCs, three 68 GB
- fileservers, twelve Ethernets, two routers and an ATM switch for
- debugging the diskless code.</para>
- </listitem>
-
- <listitem>
- <para>Dermot McDonnell donated the Toshiba XM3401B CDROM drive
- currently used in freefall.</para>
- </listitem>
-
- <listitem>
- <para>&a.chuck; contributed his floppy tape streamer for
- experimental work.</para>
- </listitem>
-
- <listitem>
- <para>Larry Altneu <email>larry@ALR.COM</email>, and &a.wilko;,
- provided Wangtek and Archive QIC-02 tape drives in order to
- improve the <devicename>wt</devicename> driver.</para>
- </listitem>
-
- <listitem>
- <para>Ernst Winter <email>ewinter@lobo.muc.de</email> contributed
- a 2.88 MB floppy drive to the project. This will hopefully
- increase the pressure for rewriting the floppy disk driver.
- <!-- smiley -->;-)</para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.tekram.com/">Tekram
- Technologies</ulink> sent one each of their DC-390, DC-390U
- and DC-390F FAST and ULTRA SCSI host adapter cards for
- regression testing of the NCR and AMD drivers with their cards.
- They are also to be applauded for making driver sources for free
- operating systems available from their FTP server <ulink
- url="ftp://ftp.tekram.com/scsi/FreeBSD/">ftp://ftp.tekram.com/scsi/FreeBSD/</ulink>.</para>
- </listitem>
-
- <listitem>
- <para>Larry M. Augustin contributed not only a
- Symbios Sym8751S SCSI card, but also a set of data books,
- including one about the forthcoming Sym53c895 chip with Ultra-2
- and LVD support, and the latest programming manual with
- information on how to safely use the advanced features of the
- latest Symbios SCSI chips. Thanks a lot!</para>
- </listitem>
-
- <listitem>
- <para>Christoph Kukulies <email>kuku@FreeBSD.org</email> donated
- an FX120 12 speed Mitsumi CDROM drive for IDE CDROM driver
- development.</para>
- </listitem>
- </itemizedlist>
- </listitem>
-
- <listitem>
- <para><emphasis>Special contributors:</emphasis></para>
-
- <itemizedlist>
- <listitem>
- <para><ulink url="http://www.osd.bsdi.com/">BSDi</ulink> (formerly Walnut Creek CDROM)
- has donated almost more than we can say (see the <link
- linkend="history">history</link> document for more details).
- In particular, we would like to thank them for the original
- hardware used for <hostid
- role="fqdn">freefall.FreeBSD.org</hostid>, our primary
- development machine, and for <hostid
- role="fqdn">thud.FreeBSD.org</hostid>, a testing and build
- box. We are also indebted to them for funding various
- contributors over the years and providing us with unrestricted
- use of their T1 connection to the Internet.</para>
- </listitem>
-
- <listitem>
- <para>The <ulink url="http://www.interface-business.de/">interface
- business GmbH, Dresden</ulink> has been patiently supporting
- &a.joerg; who has often preferred FreeBSD work over paid work, and
- used to fall back to their (quite expensive) EUnet Internet
- connection whenever his private connection became too slow or
- flaky to work with it...</para>
- </listitem>
-
- <listitem>
- <para><ulink url="http://www.bsdi.com/">Berkeley Software Design,
- Inc.</ulink> has contributed their DOS emulator code to the
- remaining BSD world, which is used in the
- <emphasis>doscmd</emphasis> command.</para>
- </listitem>
- </itemizedlist>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1 id="contrib-corealumni">
- <title>Core Team Alumni</title>
-
- <para>The following people were members of the FreeBSD core team during
- the periods indicated. We thank them for their past efforts in the
- service of the FreeBSD project.</para>
-
- <para><emphasis>In rough chronological order:</emphasis></para>
-
- <itemizedlist>
- <listitem>
- <para>&a.ache (1993 - 2000)</para>
- </listitem>
-
- <listitem>
- <para>&a.jmb (1993 - 2000)</para>
- </listitem>
-
- <listitem>
- <para>&a.bde (1992 - 2000)</para>
- </listitem>
-
- <listitem>
- <para>&a.gibbs (1993 - 2000)</para>
- </listitem>
-
- <listitem>
- <para>&a.rich (1994 - 2000)</para>
- </listitem>
-
- <listitem>
- <para>&a.phk (1992 - 2000)</para>
- </listitem>
-
- <listitem>
- <para>&a.gpalmer (1993 - 2000)</para>
- </listitem>
-
- <listitem>
- <para>&a.sos (1993 - 2000)</para>
- </listitem>
-
- <listitem>
- <para>&a.wollman (1993 - 2000)</para>
- </listitem>
-
- <listitem>
- <para>&a.joerg (1993 - 2000)</para>
- </listitem>
-
- <listitem>
- <para>&a.jdp (1997 - 2000)</para>
- </listitem>
-
- <listitem>
- <para>&a.guido (1995 - 1999)</para>
- </listitem>
-
- <listitem>
- <para>&a.dyson (1993 - 1998)</para>
- </listitem>
-
- <listitem>
- <para>&a.nate (1992 - 1996)</para>
- </listitem>
-
- <listitem>
- <para>&a.rgrimes (1992 - 1995)</para>
- </listitem>
-
- <listitem>
- <para>Andreas Schulz (1992 - 1995)</para>
- </listitem>
-
- <listitem>
- <para>&a.csgr (1993 - 1995)</para>
- </listitem>
-
- <listitem>
- <para>&a.paul (1992 - 1995)</para>
- </listitem>
-
- <listitem>
- <para>&a.smace (1993 - 1994)</para>
- </listitem>
-
- <listitem>
- <para>Andrew Moore (1993 - 1994)</para>
- </listitem>
-
- <listitem>
- <para>Christoph Robitschko (1993 - 1994)</para>
- </listitem>
-
- <listitem>
- <para>J. T. Conklin (1992 - 1993)</para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1 id="contrib-develalumni">
- <title>Development Team Alumni</title>
-
- <para>The following people were members of the FreeBSD development team
- during the periods indicated. We thank them for their past efforts
- in the service of the FreeBSD project.</para>
-
- <para><emphasis>In rough chronological order:</emphasis></para>
-
- <itemizedlist>
- <listitem>
- <para>&a.tedm (???? - 2000)</para>
- </listitem>
- <listitem>
- <para>&a.karl (???? - 2000)</para>
- </listitem>
- <listitem>
- <para>&a.gclarkii (???? - 2000)</para>
- </listitem>
- <listitem>
- <para>&a.jraynard (???? - 2000)</para>
- </listitem>
- <listitem>
- <para>&a.jgreco (???? - 1999)</para>
- </listitem>
- <listitem>
- <para>&a.ats (???? - 1999)</para>
- </listitem>
- <listitem>
- <para>Jamil Weatherby (1997 - 1999)</para>
- </listitem>
- <listitem>
- <para>meganm (???? - 1998)</para>
- </listitem>
- <listitem>
- <para>&a.dyson (???? - 1998)</para>
- </listitem>
- <listitem>
- <para>Amancio Hasty (1997 - 1998)</para>
- </listitem>
- <listitem>
- <para>Drew Derbyshire (1997 - 1998)</para>
- </listitem>
- </itemizedlist>
- </sect1>
-
- <sect1 id="contrib-derived">
- <title>Derived Software Contributors</title>
-
- <para>This software was originally derived from William F. Jolitz's 386BSD
- release 0.1, though almost none of the original 386BSD specific code
- remains. This software has been essentially re-implemented from the
- 4.4BSD-Lite release provided by the Computer Science Research Group
- (CSRG) at the University of California, Berkeley and associated academic
- contributors.</para>
-
- <para>There are also portions of NetBSD and OpenBSD that have been
- integrated into FreeBSD as well, and we would therefore like to thank
- all the contributors to NetBSD and OpenBSD for their work.</para>
- </sect1>
-
- <sect1 id="contrib-additional">
- <title>Additional FreeBSD Contributors</title>
-
- <para>(in alphabetical order by first name):</para>
-
- <itemizedlist>
- <listitem>
- <para>ABURAYA Ryushirou <email>rewsirow@ff.iij4u.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>AMAGAI Yoshiji <email>amagai@nue.org</email></para>
- </listitem>
-
- <listitem>
- <para>Aaron Bornstein <email>aaronb@j51.com</email></para>
- </listitem>
-
- <listitem>
- <para>Aaron Smith <email>aaron@mutex.org</email></para>
- </listitem>
-
- <listitem>
- <para>Achim Patzner <email>ap@noses.com</email></para>
- </listitem>
-
- <listitem>
- <para>Ada T Lim <email>ada@bsd.org</email></para>
- </listitem>
-
- <listitem>
- <para>Adam Baran <email>badam@mw.mil.pl</email></para>
- </listitem>
-
- <listitem>
- <para>Adam Glass <email>glass@postgres.berkeley.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Adam McDougall <email>mcdouga9@egr.msu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Adam Strohl <email>troll@digitalspark.net</email></para>
- </listitem>
-
- <listitem>
- <para>Adoal Xu <email>adoal@iname.com</email></para>
- </listitem>
-
- <listitem>
- <para>Adrian Colley <email>aecolley@ois.ie</email></para>
- </listitem>
-
- <listitem>
- <para>Adrian Hall <email>ahall@mirapoint.com</email></para>
- </listitem>
-
- <listitem>
- <para>Adrian Mariano <email>adrian@cam.cornell.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Adrian Steinmann <email>ast@marabu.ch</email></para>
- </listitem>
-
- <listitem>
- <para>Adrian T. Filipi-Martin
- <email>atf3r@agate.cs.virginia.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Ajit Thyagarajan <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Akio Morita
- <email>amorita@meadow.scphys.kyoto-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Akira SAWADA <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Akira Watanabe
- <email>akira@myaw.ei.meisei-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Akito Fujita <email>fujita@zoo.ncl.omron.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Alain Kalker
- <email>A.C.P.M.Kalker@student.utwente.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Alan Bawden <email>alan@curry.epilogue.com</email></para>
- </listitem>
-
- <listitem>
- <para>Alec Wolman <email>wolman@cs.washington.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Aled Morris <email>aledm@routers.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Aleksandr A Babaylov <email>.@babolo.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Alex G. Bulushev <email>bag@demos.su</email></para>
- </listitem>
-
- <listitem>
- <para>Alex D. Chen
- <email>dhchen@Canvas.dorm7.nccu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Alex Le Heux <email>alexlh@funk.org</email></para>
- </listitem>
-
- <listitem>
- <para>Alex Kapranoff <email>kappa@zombie.antar.bryansk.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Alex Perel <email>veers@disturbed.net</email></para>
- </listitem>
-
- <listitem>
- <para>Alex Varju <email>varju@webct.com</email></para>
- </listitem>
-
- <listitem>
- <para>Alex Zepeda <email>garbanzo@hooked.net</email></para>
- </listitem>
-
- <listitem>
- <para>Alexander B. Povolotsky <email>tarkhil@mgt.msk.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Alexander Gelfenbain <email>mail@gelf.com</email></para>
- </listitem>
-
- <listitem>
- <para>Alexander Leidinger
- <email>netchild@wurzelausix.CS.Uni-SB.DE</email></para>
- </listitem>
-
- <listitem>
- <para>Alexandre Snarskii <email>snar@paranoia.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Alistair G. Crooks <email>agc@uts.amdahl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Allan Bowhill <email>bowhill@bowhill.vservers.com</email></para>
- </listitem>
-
- <listitem>
- <para>Allan Saddi <email>asaddi@philosophysw.com</email></para>
- </listitem>
-
- <listitem>
- <para>Allen Campbell <email>allenc@verinet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Amakawa Shuhei <email>amakawa@hoh.t.u-tokyo.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Amancio Hasty <email>hasty@star-gate.com</email></para>
- </listitem>
-
- <listitem>
- <para>Amir Farah <email>amir@comtrol.com</email></para>
- </listitem>
-
- <listitem>
- <para>Amy Baron <email>amee@beer.org</email></para>
- </listitem>
-
- <listitem>
- <para>Anatoly A. Orehovsky <email>tolik@mpeks.tomsk.su</email></para>
- </listitem>
-
- <listitem>
- <para>Anatoly Vorobey <email>mellon@pobox.com</email></para>
- </listitem>
-
- <listitem>
- <para>Anders Nordby <email>anders@fix.no</email></para>
- </listitem>
-
- <listitem>
- <para>Anders Thulin <email>Anders.X.Thulin@telia.se</email></para>
- </listitem>
-
- <listitem>
- <para>Andras Olah <email>olah@cs.utwente.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Andre Albsmeier
- <email>Andre.Albsmeier@mchp.siemens.de</email></para>
- </listitem>
-
- <listitem>
- <para>Andre Oppermann <email>andre@pipeline.ch</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Haakh <email>ah@alman.robin.de</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Kohout <email>shanee@rabbit.augusta.de</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Lohr <email>andreas@marvin.RoBIN.de</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Schulz <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Wetzel <email>mickey@deadline.snafu.de</email></para>
- </listitem>
-
- <listitem>
- <para>Andreas Wrede <email>andreas@planix.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andres Vega Garcia <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Atrens <email>atreand@statcan.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Boothman <email>andrew@cream.org</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Gillham <email>gillham@andrews.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Gordon <email>andrew.gordon@net-tel.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Herbert <email>andrew@werple.apana.org.au</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew J. Korty <email>ajk@purdue.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew L. Moore <email>alm@mclink.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew L. Neporada <email>andrew@chg.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew McRae <email>amcrae@cisco.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Stevenson <email>andrew@ugh.net.au</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Timonin <email>tim@pool1.convey.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew V. Stesin <email>stesin@elvisti.kiev.ua</email></para>
- </listitem>
-
- <listitem>
- <para>Andrew Webster <email>awebster@dataradio.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andrey Novikov <email>andrey@novikov.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andrey Tchoritch <email>andy@venus.sympad.net</email></para>
- </listitem>
-
- <listitem>
- <para>Andy Farkas <email>andyf@speednet.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Andy Valencia <email>ajv@csd.mot.com</email></para>
- </listitem>
-
- <listitem>
- <para>Andy Whitcroft <email>andy@sarc.city.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Angelo Turetta <email>ATuretta@stylo.it</email></para>
- </listitem>
-
- <listitem>
- <para>Anthony C. Chavez <email>magus@xmission.com</email></para>
- </listitem>
-
- <listitem>
- <para>Anthony Yee-Hang Chan <email>yeehang@netcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Anton Berezin <email>tobez@plab.ku.dk</email></para>
- </listitem>
-
- <listitem>
- <para>Anton N. Bruesov <email>antonz@library.ntu-kpi.kiev.ua</email></para>
- </listitem>
-
- <listitem>
- <para>Antti Kaipila <email>anttik@iki.fi</email></para>
- </listitem>
-
- <listitem>
- <para>arci <email>vega@sophia.inria.fr</email></para>
- </listitem>
-
- <listitem>
- <para>Are Bryne <email>are.bryne@communique.no</email></para>
- </listitem>
-
- <listitem>
- <para>Ari Suutari <email>ari@suutari.iki.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Arindum Mukerji <email>rmukerji@execpc.com</email></para>
- </listitem>
-
- <listitem>
- <para>Arjan de Vet <email>devet@IAEhv.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Arne Henrik Juul <email>arnej@Lise.Unit.NO</email></para>
- </listitem>
-
- <listitem>
- <para>Arun Sharma <email>adsharma@sharmas.dhs.org</email></para>
- </listitem>
-
- <listitem>
- <para>Ask Bjoern Hansen <email>ask@valueclick.com</email></para>
- </listitem>
-
- <listitem>
- <para>Atsushi Furuta <email>furuta@sra.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Atsushi Murai <email>amurai@spec.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Bakul Shah <email>bvs@bitblocks.com</email></para>
- </listitem>
-
- <listitem>
- <para>Barry Bierbauch <email>pivrnec@vszbr.cz</email></para>
- </listitem>
-
- <listitem>
- <para>Barry Lustig <email>barry@ictv.com</email></para>
- </listitem>
-
- <listitem>
- <para>Ben Hutchinson <email>benhutch@xfiles.org.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Ben Jackson <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Ben Walter <email>bwalter@itachi.swcp.com</email></para>
- </listitem>
-
- <listitem>
- <para>Benjamin Lewis <email>bhlewis@gte.net</email></para>
- </listitem>
-
- <listitem>
- <para>Berend de Boer <email>berend@pobox.com</email></para>
- </listitem>
-
- <listitem>
- <para>Bernd Rosauer <email>br@schiele-ct.de</email></para>
- </listitem>
-
- <listitem>
- <para>Bill Kish <email>kish@osf.org</email></para>
- </listitem>
-
- <listitem>
- <para>Bill Trost <email>trost@cloud.rain.com</email></para>
- </listitem>
-
- <listitem>
- <para>Blaz Zupan <email>blaz@amis.net</email></para>
- </listitem>
-
- <listitem>
- <para>Bob Van Valzah <email>Bob@whitebarn.com</email></para>
- </listitem>
-
- <listitem>
- <para>Bob Wilcox <email>bob@obiwan.uucp</email></para>
- </listitem>
-
- <listitem>
- <para>Bob Willcox <email>bob@luke.pmr.com</email></para>
- </listitem>
-
- <listitem>
- <para>Boris Staeblow <email>balu@dva.in-berlin.de</email></para>
- </listitem>
-
- <listitem>
- <para>Boyd Faulkner <email>faulkner@mpd.tandem.com</email></para>
- </listitem>
-
- <listitem>
- <para>Boyd R. Faulkner <email>faulkner@asgard.bga.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brad Chapman <email>chapmanb@arches.uga.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Brad Hendrickse <email>bradh@uunet.co.za</email></para>
- </listitem>
-
- <listitem>
- <para>Brad Karp <email>karp@eecs.harvard.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Bradley Dunn <email>bradley@dunn.org</email></para>
- </listitem>
-
- <listitem>
- <para>Brandon Fosdick <email>bfoz@glue.umd.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Brandon Gillespie <email>brandon@roguetrader.com</email></para>
- </listitem>
-
- <listitem>
- <para>&a.wlloyd</para>
- </listitem>
-
- <listitem>
- <para>Brent J. Nordquist <email>bjn@visi.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brett Lymn <email>blymn@mulga.awadi.com.AU</email></para>
- </listitem>
-
- <listitem>
- <para>Brett Taylor
- <email>brett@peloton.runet.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Campbell <email>brianc@pobox.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Clapper <email>bmc@willscreek.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Cully <email>shmit@kublai.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Handy
- <email>handy@lambic.space.lockheed.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Litzinger <email>brian@MediaCity.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian McGovern <email>bmcgover@cisco.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Moore <email>ziff@houdini.eecs.umich.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Brian R. Haug <email>haug@conterra.com</email></para>
- </listitem>
-
- <listitem>
- <para>Brian Tao <email>taob@risc.org</email></para>
- </listitem>
-
- <listitem>
- <para>Brion Moss <email>brion@queeg.com</email></para>
- </listitem>
-
- <listitem>
- <para>Bruce Albrecht <email>bruce@zuhause.mn.org</email></para>
- </listitem>
-
- <listitem>
- <para>Bruce Gingery <email>bgingery@gtcs.com</email></para>
- </listitem>
-
- <listitem>
- <para>Bruce J. Keeler <email>loodvrij@gridpoint.com</email></para>
- </listitem>
-
- <listitem>
- <para>Bruce Murphy <email>packrat@iinet.net.au</email></para>
- </listitem>
-
- <listitem>
- <para>Bruce Walter <email>walter@fortean.com</email></para>
- </listitem>
-
- <listitem>
- <para>Carey Jones <email>mcj@acquiesce.org</email></para>
- </listitem>
-
- <listitem>
- <para>Carl Fongheiser <email>cmf@netins.net</email></para>
- </listitem>
-
- <listitem>
- <para>Carl Mascott <email>cmascott@world.std.com</email></para>
- </listitem>
-
- <listitem>
- <para>Casper <email>casper@acc.am</email></para>
- </listitem>
-
- <listitem>
- <para>Castor Fu <email>castor@geocast.com</email></para>
- </listitem>
-
- <listitem>
- <para>Chain Lee <email>chain@110.net</email></para>
- </listitem>
-
- <listitem>
- <para>Charles Hannum <email>mycroft@ai.mit.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Charles Henrich <email>henrich@msu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Charles Mott <email>cmott@scientech.com</email></para>
- </listitem>
-
- <listitem>
- <para>Charles Owens <email>owensc@enc.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Chet Ramey <email>chet@odin.INS.CWRU.Edu</email></para>
- </listitem>
-
- <listitem>
- <para>Chia-liang Kao <email>clkao@CirX.ORG</email></para>
- </listitem>
-
- <listitem>
- <para>Chiharu Shibata <email>chi@bd.mbn.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Chip Norkus <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Csanady <email>cc@tarsier.ca.sandia.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Dabrowski <email>chris@vader.org</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Dillon <email>cdillon@wolves.k12.mo.us</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Shenton
- <email>cshenton@angst.it.hq.nasa.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Stenton <email>jacs@gnome.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Timmons <email>skynyrd@opus.cts.cwu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Chris Torek <email>torek@ee.lbl.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Christian Gusenbauer
- <email>cg@fimp01.fim.uni-linz.ac.at</email></para>
- </listitem>
-
- <listitem>
- <para>Christian Haury <email>Christian.Haury@sagem.fr</email></para>
- </listitem>
-
- <listitem>
- <para>Christian Weisgerber
- <email>naddy@mips.inka.de</email></para>
- </listitem>
-
- <listitem>
- <para>Christoph P. Kukulies <email>kuku@FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>Christoph Robitschko
- <email>chmr@edvz.tu-graz.ac.at</email></para>
- </listitem>
-
- <listitem>
- <para>Christoph Weber-Fahr
- <email>wefa@callcenter.systemhaus.net</email></para>
- </listitem>
-
- <listitem>
- <para>Christopher G. Demetriou
- <email>cgd@postgres.berkeley.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Christopher N. Harrell <email>cnh@ivmg.net</email></para>
- </listitem>
-
- <listitem>
- <para>Christopher T. Johnson
- <email>cjohnson@neunacht.netgsi.com</email></para>
- </listitem>
-
- <listitem>
- <para>Chrisy Luke <email>chrisy@flix.net</email></para>
- </listitem>
-
- <listitem>
- <para>Chuck Hein <email>chein@cisco.com</email></para>
- </listitem>
-
- <listitem>
- <para>Cliff Rowley <email>dozprompt@onsea.com</email></para>
- </listitem>
-
- <listitem>
- <para>Clive Lin <email>clive@CiRX.ORG</email></para>
- </listitem>
-
- <listitem>
- <para>Colman Reilly <email>careilly@tcd.ie</email></para>
- </listitem>
-
- <listitem>
- <para>Conrad Sabatier <email>conrads@neosoft.com</email></para>
- </listitem>
-
- <listitem>
- <para>Coranth Gryphon <email>gryphon@healer.com</email></para>
- </listitem>
-
- <listitem>
- <para>Cornelis van der Laan
- <email>nils@guru.ims.uni-stuttgart.de</email></para>
- </listitem>
-
- <listitem>
- <para>Cove Schneider <email>cove@brazil.nbn.com</email></para>
- </listitem>
-
- <listitem>
- <para>Craig Leres <email>leres@ee.lbl.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Craig Loomis <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Craig Metz <email>cmetz@inner.net</email></para>
- </listitem>
-
- <listitem>
- <para>Craig Spannring <email>cts@internetcds.com</email></para>
- </listitem>
-
- <listitem>
- <para>Craig Struble <email>cstruble@vt.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Cristian Ferretti <email>cfs@riemann.mat.puc.cl</email></para>
- </listitem>
-
- <listitem>
- <para>Curt Mayer <email>curt@toad.com</email></para>
- </listitem>
-
- <listitem>
- <para>Cy Schubert <email>cschuber@uumail.gov.bc.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Cyrille Lefevre <email>clefevre@citeweb.net</email></para>
- </listitem>
-
- <listitem>
- <para>Cyrus Rahman <email>cr@jcmax.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dai Ishijima <email>ishijima@tri.pref.osaka.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Daisuke Watanabe <email>NU7D-WTNB@asahi-net.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Damian Hamill <email>damian@cablenet.net</email></para>
- </listitem>
-
- <listitem>
- <para>Dan Cross <email>tenser@spitfire.ecsel.psu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Dan Lukes <email>dan@obluda.cz</email></para>
- </listitem>
-
- <listitem>
- <para>Dan Nelson <email>dnelson@emsphone.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dan Papasian <email>bugg@bugg.strangled.net</email></para>
- </listitem>
-
- <listitem>
- <para>Dan Piponi <email>wmtop@tanelorn.demon.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Dan Walters <email>hannibal@cyberstation.net</email></para>
- </listitem>
-
- <listitem>
- <para>Daniel Hagan
- <email>dhagan@cs.vt.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Daniel M. Eischen
- <email>deischen@iworks.InterWorks.org</email></para>
- </listitem>
-
- <listitem>
- <para>Daniel O'Connor <email>doconnor@gsoft.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Daniel Poirot <email>poirot@aio.jsc.nasa.gov</email></para>
- </listitem>
-
- <listitem>
- <para>Daniel Rock <email>rock@cs.uni-sb.de</email></para>
- </listitem>
-
- <listitem>
- <para>Danny Egen <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Danny J. Zerkel <email>dzerkel@phofarm.com</email></para>
- </listitem>
-
- <listitem>
- <para>Darren Reed <email>avalon@coombs.anu.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Adkins <email>adkin003@tc.umn.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Andersen <email>angio@aros.net</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Blizzard <email>dblizzar@sprynet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Bodenstab <email>imdave@synet.net</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Burgess <email>burgess@hrd769.brooks.af.mil</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Chapeskie <email>dchapes@ddm.on.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Cornejo <email>dave@dogwood.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Edmondson <email>davided@sco.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Glowacki <email>dglo@ssec.wisc.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Marquardt <email>marquard@austin.ibm.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dave Tweten <email>tweten@FreeBSD.org</email></para>
- </listitem>
-
- <listitem>
- <para>David A. Adkins <email>adkin003@tc.umn.edu</email></para>
- </listitem>
-
- <listitem>
- <para>David A. Bader <email>dbader@eece.unm.edu</email></para>
- </listitem>
-
- <listitem>
- <para>David Borman <email>dab@bsdi.com</email></para>
- </listitem>
-
- <listitem>
- <para>David W. Chapman Jr. <email>dwcjr@inethouston.net</email></para>
- </listitem>
-
- <listitem>
- <para>David Dawes <email>dawes@XFree86.org</email></para>
- </listitem>
-
- <listitem>
- <para>David Filo <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>David Holland <email>dholland@eecs.harvard.edu</email></para>
- </listitem>
-
- <listitem>
- <para>David Holloway <email>daveh@gwythaint.tamis.com</email></para>
- </listitem>
-
- <listitem>
- <para>David Horwitt <email>dhorwitt@ucsd.edu</email></para>
- </listitem>
-
- <listitem>
- <para>David Hovemeyer <email>daveho@infocom.com</email></para>
- </listitem>
-
- <listitem>
- <para>David Jones <email>dej@qpoint.torfree.net</email></para>
- </listitem>
-
- <listitem>
- <para>David Kelly <email>dkelly@tomcat1.tbe.com</email></para>
- </listitem>
-
- <listitem>
- <para>David Kulp <email>dkulp@neomorphic.com</email></para>
- </listitem>
-
- <listitem>
- <para>David L. Nugent <email>davidn@blaze.net.au</email></para>
- </listitem>
-
- <listitem>
- <para>David Leonard <email>d@scry.dstc.edu.au</email></para>
- </listitem>
-
- <listitem>
- <para>David Muir Sharnoff <email>muir@idiom.com</email></para>
- </listitem>
-
- <listitem>
- <para>David S. Miller <email>davem@jenolan.rutgers.edu</email></para>
- </listitem>
-
- <listitem>
- <para>David Sugar <email>dyfet@gnu.org</email></para>
- </listitem>
-
- <listitem>
- <para>David Wolfskill <email>dhw@whistle.com</email></para>
- </listitem>
-
- <listitem>
- <para>Dean Gaudet <email>dgaudet@arctic.org</email></para>
- </listitem>
-
- <listitem>
- <para>Dean Huxley <email>dean@fsa.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Denis Fortin <email>unknown</email></para>
- </listitem>
-
- <listitem>
- <para>Denis Shaposhnikov <email>dsh@vlink.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Dennis Glatting
- <email>dennis.glatting@software-munitions.com</email></para>
- </listitem>
-
- <listitem>
- <para>Denton Gentry <email>denny1@home.com</email></para>
- </listitem>
-
- <listitem>
- <para>der Mouse <email>mouse@Collatz.McRCIM.McGill.EDU</email></para>
- </listitem>
-
- <listitem>
- <para>Derek Inksetter <email>derek@saidev.com</email></para>
- </listitem>
-
- <listitem>
- <para>DI. Christian Gusenbauer
- <email>cg@scotty.edvz.uni-linz.ac.at</email></para>
- </listitem>
-
- <listitem>
- <para>Dirk Keunecke <email>dk@panda.rhein-main.de</email></para>
- </listitem>
-
- <listitem>
- <para>Dirk Meyer <email>dirk.meyer@dinoex.sub.org</email></para>
- </listitem>
-
- <listitem>
- <para>Dirk Nehrling <email>nerle@pdv.de</email></para>
- </listitem>
-
- <listitem>
- <para>Dishanker Rajakulendren <email>draj@oceanfree.net</email></para>
- </listitem>
-
- <listitem>
- <para>Dmitry Khrustalev <email>dima@xyzzy.machaon.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Dmitry Kohmanyuk <email>dk@farm.org</email></para>
- </listitem>
-
- <listitem>
- <para>Dom Mitchell <email>dom@myrddin.demon.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Domas Mituzas <email>midom@dammit.lt</email></para>
- </listitem>
-
- <listitem>
- <para>Dominik Brettnacher <email>domi@saargate.de</email></para>
- </listitem>
-
- <listitem>
- <para>Dominik Rothert <email>dr@domix.de</email></para>
- </listitem>
-
- <listitem>
- <para>Don Croyle <email>croyle@gelemna.ft-wayne.in.us</email></para>
- </listitem>
-
- <listitem>
- <para>Donn Miller <email>dmmiller@cvzoom.net</email></para>
- </listitem>
-
- <listitem>
- <para>Dan Pelleg <email>dpelleg+unison@cs.cmu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>&a.whiteside;</para>
- </listitem>
-
- <listitem>
- <para>Don Morrison <email>dmorrisn@u.washington.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Don Yuniskis <email>dgy@rtd.com</email></para>
- </listitem>
-
- <listitem>
- <para>Donald Maddox <email>dmaddox@conterra.com</email></para>
- </listitem>
-
- <listitem>
- <para>Douglas Ambrisko <email>ambrisko@whistle.com</email></para>
- </listitem>
-
- <listitem>
- <para>Douglas Carmichael <email>dcarmich@mcs.com</email></para>
- </listitem>
-
- <listitem>
- <para>Douglas Crosher <email>dtc@scrooge.ee.swin.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Drew Derbyshire <email>ahd@kew.com</email></para>
- </listitem>
-
- <listitem>
- <para>Duncan Barclay <email>dmlb@ragnet.demon.co.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Dustin Sallings <email>dustin@spy.net</email></para>
- </listitem>
-
- <listitem>
- <para>Eckart "Isegrim" Hofmann
- <email>Isegrim@Wunder-Nett.org</email></para>
- </listitem>
-
- <listitem>
- <para>Ed Gold
- <email>vegold01@starbase.spd.louisville.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Ed Hudson <email>elh@p5.spnet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Edward Chuang <email>edwardc@firebird.org.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Edward Wang <email>edward@edcom.com</email></para>
- </listitem>
-
- <listitem>
- <para>Edwin Groothus <email>edwin@nwm.wan.philips.com</email></para>
- </listitem>
-
- <listitem>
- <para>Edwin Mons <email>e@ik.nu</email></para>
- </listitem>
-
- <listitem>
- <para>Ege Rekk <email>aagero@aage.priv.no</email></para>
- </listitem>
-
- <listitem>
- <para>Eiji-usagi-MATSUmoto <email>usagi@clave.gr.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Eike Bernhardt <email>eike.bernhardt@gmx.de</email></para>
- </listitem>
-
- <listitem>
- <para>ELISA Font Project</para>
- </listitem>
-
- <listitem>
- <para>Elmar Bartel
- <email>bartel@informatik.tu-muenchen.de</email></para>
- </listitem>
-
- <listitem>
- <para>Eoin Lawless <email>eoin@maths.tcd.ie</email></para>
- </listitem>
-
- <listitem>
- <para>Eric A. Griff <email>eagriff@global2000.net</email></para>
- </listitem>
-
- <listitem>
- <para>Eric Melville <email>eric@osd.bsdi.com</email></para>
- </listitem>
-
- <listitem>
- <para>Eric Blood <email>eblood@cs.unr.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Eric D. Futch <email>efutch@nyct.net</email></para>
- </listitem>
-
- <listitem>
- <para>Eric J. Haug <email>ejh@slustl.slu.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Eric J. Schwertfeger <email>eric@cybernut.com</email></para>
- </listitem>
-
- <listitem>
- <para>Eric L. Hernes <email>erich@lodgenet.com</email></para>
- </listitem>
-
- <listitem>
- <para>Eric P. Scott <email>eps@sirius.com</email></para>
- </listitem>
-
- <listitem>
- <para>Eric Sprinkle <email>eric@ennovatenetworks.com</email></para>
- </listitem>
-
- <listitem>
- <para>Erich Stefan Boleyn <email>erich@uruk.org</email></para>
- </listitem>
-
- <listitem>
- <para>Erich Zigler <email>erich@tacni.net</email></para>
- </listitem>
-
- <listitem>
- <para>Erik H. Bakke <email>erikhb@bgnett.no</email></para>
- </listitem>
-
- <listitem>
- <para>Erik E. Rantapaa <email>rantapaa@math.umn.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Erik H. Moe <email>ehm@cris.com</email></para>
- </listitem>
-
- <listitem>
- <para>Ernst Winter <email>ewinter@lobo.muc.de</email></para>
- </listitem>
-
- <listitem>
- <para>Espen Skoglund <email>esk@ira.uka.de</email></para>
- </listitem>
-
- <listitem>
- <para>Eugene M. Kim <email>astralblue@usa.net</email></para>
- </listitem>
-
- <listitem>
- <para>Eugene Radchenko <email>genie@qsar.chem.msu.su</email></para>
- </listitem>
-
- <listitem>
- <para>Eugeny Kuzakov <email>CoreDumped@coredumped.null.ru</email></para>
- </listitem>
-
- <listitem>
- <para>Evan Champion <email>evanc@synapse.net</email></para>
- </listitem>
-
- <listitem>
- <para>Faried Nawaz <email>fn@Hungry.COM</email></para>
- </listitem>
-
- <listitem>
- <para>Flemming Jacobsen <email>fj@tfs.com</email></para>
- </listitem>
-
- <listitem>
- <para>Fong-Ching Liaw <email>fong@juniper.net</email></para>
- </listitem>
-
- <listitem>
- <para>Francis M J Hsieh <email>mjshieh@life.nthu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Bartels <email>knarf@camelot.de</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Chen Hsiung Chan
- <email>frankch@waru.life.nthu.edu.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Durda IV <email>uhclem@nemesis.lonestar.org</email></para>
- </listitem>
-
- <listitem>
- <para>Frank MacLachlan <email>fpm@n2.net</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Nobis <email>fn@Radio-do.de</email></para>
- </listitem>
-
- <listitem>
- <para>Frank ten Wolde <email>franky@pinewood.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Frank van der Linden <email>frank@fwi.uva.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Frank Volf <email>volf@oasis.IAEhv.nl</email></para>
- </listitem>
-
- <listitem>
- <para>Fred Cawthorne <email>fcawth@jjarray.umn.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Fred Gilham <email>gilham@csl.sri.com</email></para>
- </listitem>
-
- <listitem>
- <para>Fred Templin <email>templin@erg.sri.com</email></para>
- </listitem>
-
- <listitem>
- <para>Frederick Earl Gray <email>fgray@rice.edu</email></para>
- </listitem>
-
- <listitem>
- <para>FUJIMOTO Kensaku
- <email>fujimoto@oscar.elec.waseda.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>FUJISHIMA Satsuki <email>k5@respo.or.jp</email></para>
- </listitem>
-
- <listitem>
- <para>FURUSAWA Kazuhisa
- <email>furusawa@com.cs.osakafu-u.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>G. Adam Stanislav<email>adam@whizkidtech.net</email></para>
- </listitem>
-
- <listitem>
- <para>Gabor Kincses <email>gabor@acm.org</email></para>
- </listitem>
-
- <listitem>
- <para>Gabor Zahemszky <email>zgabor@CoDe.hu</email></para>
- </listitem>
-
- <listitem>
- <para>Gareth McCaughan <email>gjm11@dpmms.cam.ac.uk</email></para>
- </listitem>
-
- <listitem>
- <para>Gary A. Browning <email>gab10@griffcd.amdahl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Gary Howland <email>gary@hotlava.com</email></para>
- </listitem>
-
- <listitem>
- <para>Gary J. <email>garyj@rks32.pcs.dec.com</email></para>
- </listitem>
-
- <listitem>
- <para>Gary Kline <email>kline@thought.org</email></para>
- </listitem>
-
- <listitem>
- <para>Gaspar Chilingarov <email>nightmar@lemming.acc.am</email></para>
- </listitem>
-
- <listitem>
- <para>Gea-Suan Lin <email>gsl@tpts4.seed.net.tw</email></para>
- </listitem>
-
- <listitem>
- <para>Gene Raytsin <email>pal@paladin7.net</email></para>
- </listitem>
-
- <listitem>
- <para>Geoff Rehmet <email>csgr@alpha.ru.ac.za</email></para>
- </listitem>
-
- <listitem>
- <para>Georg Wagner <email>georg.wagner@ubs.com</email></para>
- </listitem>
-
- <listitem>
- <para>George Reid <email>services@nevernet.net</email></para>
- </listitem>
-
- <listitem>
- <para>Gianlorenzo Masini <email>masini@uniroma3.it</email></para>
- </listitem>
-
- <listitem>
- <para>Gianmarco Giovannelli
- <email>gmarco@giovannelli.it</email></para>
- </listitem>
-
- <listitem>
- <para>Gil Kloepfer Jr. <email>gil@limbic.ssdl.com</email></para>
- </listitem>
-
- <listitem>
- <para>Gilad Rom <email>rom_glsa@ein-hashofet.co.il</email></para>
- </listitem>
-
- <listitem>
- <para>Giles Lean <email>giles@nemeton.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Ginga Kawaguti
- <email>ginga@amalthea.phys.s.u-tokyo.ac.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Giorgos Keramidas <email>keramida@ceid.upatras.gr</email></para>
- </listitem>
-
- <listitem>
- <para>Glen Foster <email>gfoster@gfoster.com</email></para>
- </listitem>
-
- <listitem>
- <para>Glenn Johnson <email>gljohns@bellsouth.net</email></para>
- </listitem>
-
- <listitem>
- <para>Godmar Back <email>gback@facility.cs.utah.edu</email></para>
- </listitem>
-
- <listitem>
- <para>Goran Hammarback <email>goran@astro.uu.se</email></para>
- </listitem>
-
- <listitem>
- <para>Gord Matzigkeit <email>gord@enci.ucalgary.ca</email></para>
- </listitem>
-
- <listitem>
- <para>Gordon Greeff <email>gvg@uunet.co.za</email></para>
- </listitem>
-
- <listitem>
- <para>Graham Wheeler <email>gram@cdsec.com</email></para>
- </listitem>
-
- <listitem>
- <para>Greg A. Woods <email>woods@zeus.leitch.com</email></para>
- </listitem>
-
- <listitem>
- <para>Greg Ansley <email>gja@ansley.com</email></para>
- </listitem>
-
- <listitem>
- <para>Greg Robinson <email>greg@rosevale.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Greg Troxel <email>gdt@ir.bbn.com</email></para>
- </listitem>
-
- <listitem>
- <para>Greg Ungerer <email>gerg@stallion.oz.au</email></para>
- </listitem>
-
- <listitem>
- <para>Gregory Bond <email>gnb@itga.com.au</email></para>
- </listitem>
-
- <listitem>
- <para>Gregory D. Moncreaff
- <email>moncrg@bt340707.res.ray.com</email></para>
- </listitem>
-
- <listitem>
- <para>Guy Harris <email>guy@netapp.com</email></para>
- </listitem>
-
- <listitem>
- <para>Guy Helmer <email>ghelmer@cs.iastate.edu</email></para>
- </listitem>
-
- <listitem>
- <para>HAMADA Naoki <email>hamada@astec.co.jp</email></para>
- </listitem>
-
- <listitem>
- <para>Hannu Savolainen <email>hannu@voxware.pp.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Hans Huebner <email>hans@artcom.de</email></para>
- </listitem>
-
- <listitem>
- <para>Hans Petter Bieker <email>zerium@webindex.no</email></para>
- </listitem>
-
- <listitem>
- <para>Hans Zuidam <email>hans@brandinnovators.com</email></para>
- </listitem>
-
- <listitem>
- <para>Harlan Stenn <email>Harlan.Stenn@pfcs.com</email></para>
- </listitem>
-
- <listitem>
- <para>Harold Barker <email>hbarker@dsms.com</email></para>
- </listitem>
-
- <listitem>
- <para>Havard Eidnes
- <email>Havard.Eidnes@runit.sintef.no</email></para>
- </listitem>
-
- <listitem>
- <para>Heikki Suonsivu <email>hsu@cs.hut.fi</email></para>
- </listitem>
-
- <listitem>
- <para>Heiko W. Rupp <email>unknown</email></par