                         FreeBSD "IYENICURaYENU

  FreeBSD CURaaYENopue

   -a(c)AAv (c) 1995, 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003,
   2004, 2005, 2006, 2007, 2008 FreeBSD CURaaYENopue

   AAw-ai"IYENIFreeBSD!I YEN>>"IYENICURaYENU^2[>>\
   1/2d^3oYEN]NOTACURF FreeBSD 8.4-RELEASE (c)M FreeBSD 9.1-RELEASE
   -a-o|w,E(c)MCURe+-`"IYENI!C
   ^3oYEN-:"IYENICURaYENUNOTO<<U:|hCURH-a-oP:DEGAAe^3D-S:@!A|OYENBCUR'uM!y<<uA:oCUR-L-A_!z-a-oP:i|aeCURCUR!C
   ^3\|h^3^1,`CUR'YEN
   1/4S:^1|"!ACURwS:^1|"-a-o^3!YEN-:CUR]|^3"C,>>YnS:o.s!C
   |p-aG+-z|^3?^3 1/2`i"oS:UYEN>>pue-a-o,U:!A 1/2D-+-H e-mail "`i
   FreeBSD documentation project P:l>> 1/4 1/2 * 3/4A!C |b FreeBSD
   -oo-,
   YENiYENHS:a:"`i^3oYEN-:CURaaYENo-a-o^3I.s-a(c)YEN>>(AA-a(c)CURaaYENoYENi+-q
   http://docs.FreeBSD.org/doc/ "u+-o)!ACUR]YENiYENH+-q FreeBSD FTP
   |o/-aA 3/4^1 (c)INOTO^2^3|h mirror -,>>O
   CURU,u:CUR-L-|P(R)ae|!-a-o,e(R)AE!C |p-aGCURn,uDEG
   3/4|n^1eAAe(R)N+-,e(R)AE!A"-oYENiYENH|b FreeBSD Mall AEP:R!C
   |^1YEN~!ACUR]YENiYENH|b "IYENICURaYENU CURCUR.j'M,e(R)AE!C

   Redistribution and use in source (XML DocBook) and 'compiled'
   forms (XML, HTML, PDF, PostScript, RTF and so forth) with or
   without modification, are permitted provided that the following
   conditions are met:

    1. Redistributions of source code (XML DocBook) 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 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.

     <<n: 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.

   FreeBSD NOTO FreeBSDDEGo-a-:.|-a-ouuYENUDEGO 1/4D-

   3Com (c)M HomeConnect NOTO 3Com Corporation -a-ouuYENUDEGO 1/4D-!C

   3ware (c)M Escalade NOTO 3ware Inc -a-ouuYENUDEGO 1/4D-!C

   ARM NOTO ARM Limited. -a-ouuYENUDEGO 1/4D-!C

   Adaptec NOTO Adaptec, Inc. -a-ouuYENUDEGO 1/4D-!C

   Adobe, Acrobat, Acrobat Reader, YENHCURI PostScript NOTO Adobe
   Systems Incorporated |bNOTu:DEGe(c)M/(c)I"a:YENLDEGe(R)a-a-oDEGO
   1/4D-(c)IuuYENUDEGO 1/4D-!C

   Apple, AirPort, FireWire, Mac, Macintosh, Mac OS, Quicktime,
   YENHCURI TrueType NOTO Apple Computer, Inc.
   |bNOTu:DEGeYENHCURI"a:YENLDEGe(R)a-a-ouuYENUDEGO 1/4D-!C

   Corel (c)M WordPerfect NOTO Corel Corporation (c)M/(c)I"a:CURlCUR
   1/2YENq|bYEN[(R)^3CURj!BNOTu:DEGe(c)M/(c)I"a:YENLDEGe(R)a-a-ouuYENUDEGO
   1/4D-!C

   Sound Blaster NOTO Creative Technology Ltd.
   |bNOTu:DEGe(c)M/(c)I"a:YENLDEGe(R)a-a-ouuYENUDEGO 1/4D-!C

   CVSup NOTO John D. Polstra -a-ouuYENUDEGO 1/4D-!C

   Heidelberg, Helvetica, Palatino, (c)M Times Roman NOTO
   Heidelberger Druckmaschinen AG
   |bNOTu:DEGeYENHCURI"a:YENLDEGe(R)a-a-oDEGO 1/4D-(c)IuuYENUDEGO
   1/4D-!C

   IBM, AIX, EtherJet, Netfinity, OS/2, PowerPC, PS/2, S/390, (c)M
   ThinkPad NOTO DEGe>>UDEGOYENI 3/4-: 3/4^1CUR
   1/2YENq|bNOTu:DEGe(c)M"a:YENLDEGe(R)a-a-ouuYENUDEGO 1/4D-(c)IDEGO
   1/4D-!C

   IEEE, POSIX, (c)M 802 NOTO Institute of Electrical and Electronics
   Engineers, Inc. |bNOTu:DEGe-a-ouuYENUDEGO 1/4D-!C

   Intel, Celeron, EtherExpress, i386, i486, Itanium, Pentium, (c)M
   Xeon NOTO Intel Corporation CURI"a:CURACURa:
   3/4-:-oc|bNOTu:DEGe(c)M"a:YENLDEGe(R)a-a-oDEGO 1/4D-(c)IuuYENUDEGO
   1/4D-!C

   Intuit (c)M Quicken NOTO Intuit Inc., (c)I"a:CURlCUR
   1/2YENq|bNOTu:DEGe(c)M"a:YENLDEGe(R)a-a-oDEGO 1/4D-(c)IuuYENUDEGO
   1/4D-!C

   Linux NOTO Linus Torvalds -a-ouuYENUDEGO 1/4D-!C

   LSI Logic, AcceleRAID, eXtremeRAID, MegaRAID (c)M Mylex NOTO LSI
   Logic Corp -a-oDEGO 1/4D-(c)IuuYENUDEGO 1/4D-!C

   M-Systems (c)M DiskOnChip NOTO M-Systems Flash Disk Pioneers, Ltd.
   -a-oDEGO 1/4D-(c)IuuYENUDEGO 1/4D-!C

   Macromedia, Flash, YENHCURI Shockwave Macromedia, Inc.
   |bNOTu:DEGe(c)M/(c)I"a:YENLDEGe(R)a-a-oDEGO 1/4D-(c)IuuYENUDEGO
   1/4D-!C

   Microsoft, IntelliMouse, MS-DOS, Outlook, Windows, Windows Media,
   (c)M Windows NT NOTO Microsoft Corporation
   |bNOTu:DEGe(c)M/(c)I"a:YENLDEGe(R)a-a-oDEGO 1/4D-(c)IuuYENUDEGO
   1/4D-!C

   Netscape YENHCURI Netscape Navigator NOTO Netscape Communications
   Corporation |bNOTu:DEGe(c)M"a:YENLDEGe(R)a-a-ouuYENUDEGO 1/4D-!C

   GateD (c)M NextHop NOTO NextHop
   |bNOTu:DEGe(c)M"a:YENLDEGe(R)a-a-oDEGO 1/4D-(c)IuuYENUDEGO 1/4D-!C

   Motif, OSF/1, (c)M UNIX NOTO The Open Group
   |bNOTu:DEGe(c)M"a:YENLDEGe(R)a-a-ouuYENUDEGO 1/4D-!F IT DialTone
   (c)M The Open Group NOTO"a:DEGO 1/4D-!C

   Oracle NOTO Oracle Corporation -a-ouuYENUDEGO 1/4D-!C

   PowerQuest (c)M PartitionMagic NOTO PowerQuest Corporation
   |bNOTu:DEGe(c)M/(c)I"a:YENLDEGe(R)a-a-ouuYENUDEGO 1/4D-!C

   RealNetworks, RealPlayer, (c)M RealAudio NOTO RealNetworks, Inc.
   -a-ouuYENUDEGO 1/4D-!C

   Red Hat, RPM, NOTO Red Hat, Inc.
   |bNOTu:DEGe(c)M"a:YENLDEGe(R)a-a-ouuYENUDEGO 1/4D-!C

   SAP, R/3, (c)M mySAP NOTO SAP AG |b
   1/4wDEGeYENHCURI^3\|h"a:YENLDEGe(R)a-a-oDEGO 1/4D-(c)IuuYENUDEGO
   1/4D-!C

   Sun, Sun Microsystems, Java, Java Virtual Machine, JavaServer
   Pages, JDK, JSP, JVM, Netra, Solaris, StarOffice, Sun Blade, Sun
   Enterprise, Sun Fire, SunOS, (c)M Ultra NOTO Sun Microsystems,
   Inc. |bNOTu:DEGe(c)M"a:YENLDEGe(R)a-a-oDEGO 1/4D-(c)IuuYENUDEGO
   1/4D-!C

   Symantec (c)M Ghost NOTO Symantec Corporation
   |bNOTu:DEGe(c)M"a:YENLDEGe(R)a-a-ouuYENUDEGO 1/4D-!C

   MATLAB NOTO The MathWorks, Inc. -a-ouuYENUDEGO 1/4D-!C

   SpeedTouch NOTO Thomson -a-oDEGO 1/4D-!C

   U.S. Robotics (c)M Sportster NOTO U.S. Robotics Corporation
   -a-ouuYENUDEGO 1/4D-!C

   VMware NOTO VMware, Inc. -a-oDEGO 1/4D-

   Waterloo Maple (c)M Maple NOTO Waterloo Maple Inc -a-oDEGO
   1/4D-(c)IuuYENUDEGO 1/4D-

   Mathematica NOTO Wolfram Research, Inc -a-ouuYENUDEGO 1/4D-!C

   XFree86 NOTO The XFree86 Project, Inc -a-oDEGO 1/4D-!C.

   Ogg Vorbis (c)M Xiph.Org NOTO Xiph.Org -a-oDEGO 1/4D-!C

   ^3\|h>>s^3yDEGO(c)M,g 3/4PDEGO"IYENICUR@"C,-oUNOTDEGDEGO
   1/4D--a-o^1I(R) *(c)ICURaa|r^3]p"O^1u:AAa|UCURv-a-o^2-L-<<~!C
   YEN>>CURaaCURCURYENX^2{-a-o^2^3|hDEGO 1/4D-!AYENHCURI FreeBSD
   Project YEN>>" 1/4s(c)OCURH-a 3/4-a-oDEGO 1/4D-!A<<a+-+-NYENH
   '(TM)' (c)I '(R)' ^2AA,^1"O 1/4D-uu!C

     --------------------------------------------------------------

   CUR-o(R)eYENO/?y

   S:C,

   I. P:}(c)l"IYENI FreeBSD

                1. A^2CURP:

                             1.1. .S:z

                             1.2. Welcome to FreeBSD!

                             1.3. Ao:(c)o FreeBSD p^1-o

                2. |w,E FreeBSD

                             2.1. .S:z

                             2.2. uwAAe>>Y"D

                             2.3. |w,E<<e-a-o.C,^3AECURuS:@

                             2.4. P:}(c)l|w,E

                             2.5. CURP:^2D- Sysinstall

                             2.6. uw-oD--aAAP:!-a-oCURADEGt

                             2.7. ?i 3/4U:.Qn|w,E-a-o

                             2.8. ?i 3/4U:|w,E"O. 1/2

                             2.9. P:}(c)lP:i|ae|w,E

                             2.10. <<aA:o|w,E

                             2.11. |w,E-a-o-oAAo/Ao/-g,N"M

                             2.12. P:iP:YEN|w,E<<u:<<n

                             2.13. >>sS:@|w,ECURu

                3. UNIX DEGoA|.S:(c)A

                             3.1. .S:z

                             3.2. Virtual Consoles (c)M^2 *-oY 3/4-:

                             3.3. AAv

                             3.4. YENO/?yu^2-oc

                             3.5. -oI-oD-^2OA'

                             3.6. +- 3/4,u:>>P"o/,u:AE(R) *"t^2I

                             3.7. u{S:C,

                             3.8. Daemon!B<<H,^1CURI^2 *CURiu{S:C,

                             3.9. Shells

                             3.10. CURaa|r 1/2s?e 3/4^1

                             3.11. ^3]^3AECURI^3]^3AE,`AI

                             3.12. Binary -a-o(R)ae|!

                             3.13. S:o|h,eDEGT

                4. ^3nAAe(R)MYENo-oTH^2z 1/2g!GPackages CURI Ports 
                3/4-:"i

                             4.1. .S:z

                             4.2. |w,E^3nAAe-a-o|U-oO/CURe|!CURP:^2D-

                             4.3. 'MS:a:.Q,E-a-o^3nAAe

                             4.4. "IYENI Packages -oTH^2z 3/4-:"i

                             4.5. "IYENI Ports -oTH^2z 3/4-:"i

                             4.6.
                             |w,ECURS:<<a!A|^3CURDEG>>o<<aA:o-a`.N"AEP:uP:U:!H

                             4.7. |p|o^3B^2zA:e+- 1/4(Broken)-a-o
                             Ports!H

                5. X Window uo/u!"t^2I

                             5.1. .S:z

                             5.2. AA,N X -a-oYEN@NOTE

                             5.3. |w,E X11

                             5.4. ^3](c)w X11

                             5.5. |b X11 CURCUR"IYENI|r<<NOT

                             5.6. The X Display Manager

                             5.7. (R)`a+-Ao^1O

   II. CUR@-e(c)ECURuS:@

                6. (R)`a+-Ao^1OA^3YENIu{|!

                             6.1. .S:z

                             6.2. AsA:y 3/4^1

                             6.3. ?`iCUR 1/2<<C,^3nAAe

                             6.4. CURaaYENo 3/4\A:y 3/4^1

                             6.5. DEG]DEGE

                             6.6. -oKn

                7. |h'CAAe 1/4vu(R)T 1/4O:(Multimedia)

                             7.1. .S:z

                             7.2. ^3](c)wu(R)A:YENd

                             7.3. MP3 u 1/4O:

                             7.4.  1/4 1/2(c)n 1/4vCURu

                             7.5. ^3](c)w^1quo/YENd(TV Cards)

                             7.6. +- 1/2'y 3/4^1

                8. ^3](c)w FreeBSD Kernel

                             8.1. .S:z

                             8.2. NOTDEG|o>>Yn<<.s 1/2ODEGt!B
                             1/2sA:P: kernel!H

                             8.3. +-''u"t^2IuwAAe

                             8.4. <<.s 1/2ODEGt!B 1/2sA:P: kernel

                             8.5. kernel ^3](c)wAE,N>>!

                             8.6. If Something Goes Wrong

                9. |C|L

                             9.1. .S:z

                             9.2. CURP:^2D-

                             9.3. DEGoA|^3](c)w

                             9.4. Advanced Printer Setup

                             9.5. Using Printers

                             9.6. Alternatives to the Standard
                             Spooler

                             9.7. Troubleshooting

                10. >>P Linux Binary -a-oNOTU(R)eCURe+-

                             10.1. .S:z

                             10.2. |w,E

                             10.3. Installing Mathematica(R)

                             10.4. Installing Maple(TM)

                             10.5. Installing MATLAB(R)

                             10.6. Installing Oracle(R)

                             10.7. Installing SAP(R) R/3(R)

                             10.8. Advanced Topics

   III. "t^2I-oTH^2z

                11. ^3](c)w>>P(R)A:-`a 1/2O(R)O(Tuning)

                             11.1. .S:z

                             11.2. CUR@P:}(c)l-a-o^3W^1-o

                             11.3. ^3IYENDn-a-o^3](c)wAE

                             11.4. |U|!A^3YENIu{|!-a-o^3](c)wAE

                             11.5. |U-oO/ Services -a-o+-ODEGECURe|!

                             11.6. ^3](c)w cron

                             11.7. |b FreeBSD "IYENI rc

                             11.8. ^3](c)w-oo,oYENd

                             11.9. ueAAYEND 3/4-:(Virtual Hosts)

                             11.10. AU|^3th"C,YENDn^3](c)wAE(c)O!H

                             11.11. Tuning with sysctl

                             11.12. Tuning Disks

                             11.13. Tuning Kernel Limits

                             11.14. Adding Swap Space

                             11.15. Power and Resource Management

                             11.16. Using and Debugging FreeBSD ACPI

                12. FreeBSD P:} 3/4-:NOTyu{ 1/2g

                             12.1. .S:z

                             12.2. Booting DEGYAD

                             12.3. The Boot Manager and Boot Stages

                             12.4. Kernel Interaction During Boot

                             12.5. Device Hints

                             12.6. Init: Process Control
                             Initialization

                             12.7. Shutdown Sequence

                13. "IYENI-aI>>PDEGoYEN>>+-b,^1-oTH^2z

                             13.1. .S:z

                             13.2. CURP:^2D-

                             13.3. "t^2I-oTH^2z-aI+-b,^1

                             13.4. "t^2I+-b,^1

                             13.5. "IYENI-aI+-b,^1

                             13.6. S:oS:i+-b,^1

                             13.7. "IYENI-aI,e. 1/2"i

                             13.8. ,s^2O

                14. "t^2I|wYENth

                             14.1. .S:z

                             14.2. CURP:^2D-

                             14.3. FreeBSD -a-o"t^2I|wYENth

                             14.4. DES, MD5, and Crypt

                             14.5. One-time Passwords

                             14.6. TCP Wrappers

                             14.7. KerberosIV

                             14.8. Kerberos5

                             14.9. OpenSSL

                             14.10. VPN over IPsec

                             14.11. OpenSSH

                             14.12. File System Access Control Lists

                             14.13. Monitoring Third Party Security
                             Issues

                             14.14. FreeBSD Security Advisories

                             14.15. Process Accounting

                15. Jails

                             15.1. .S:z

                             15.2. Jail NOTUAo:^3N>>y

                             15.3. I'-oNOTG"AE

                             15.4. <<O/YENss(c)M+-+-"i Jail

                             15.5. .L 1/2O>>P-oTH^2z

                             15.6. Jail -a-oA^3YENI

                16. Mandatory Access Control

                             16.1. Synopsis

                             16.2. Key Terms in this Chapter

                             16.3. Explanation of MAC

                             16.4. Understanding MAC Labels

                             16.5. Module Configuration

                             16.6. The MAC bsdextended Module

                             16.7. The MAC ifoff Module

                             16.8. The MAC portacl Module

                             16.9. MAC Policies with Labeling
                             Features

                             16.10. The MAC partition Module

                             16.11. The MAC Multi-Level Security
                             Module

                             16.12. The MAC Biba Module

                             16.13. The MAC LOMAC Module

                             16.14. Implementing a Secure Environment
                             with MAC

                             16.15. Another Example: Using MAC to
                             Constrain a Web Server

                             16.16. Troubleshooting the MAC Framework

                17. Security Event Auditing

                             17.1. Synopsis

                             17.2. Key Terms - Words to Know

                             17.3. Installing Audit Support

                             17.4. Audit Configuration

                             17.5. Event Audit Administration

                18. Ax|s^3]^3AE 1/2g

                             18.1. .S:z

                             18.2. ,E,m|W-oU

                             18.3. .s 1/4W-oI-oD-

                             18.4. RAID

                             18.5. USB Ax|s,E,m

                             18.6. Creating and Using Optical Media
                             (CDs)

                             18.7. Creating and Using Optical Media
                             (DVDs)

                             18.8. Creating and Using Floppy Disks

                             18.9. Creating and Using Data Tapes

                             18.10. Backups to Floppies

                             18.11. Backup Strategies

                             18.12. Backup Basics

                             18.13. Network, Memory, and File-Backed
                             File Systems

                             18.14. File System Snapshots

                             18.15. -oI-oD--aAAP:!DEGtAB(Quota)

                             18.16. Encrypting Disk Partitions

                             18.17. Encrypting Swap Space

                19. GEOM: Modular Disk Transformation Framework

                             19.1. .S:z

                             19.2. GEOM  3/4E 1/2 *

                             19.3. RAID0 - CURA'^2^3su^2(striping)

                             19.4. RAID1 - Ae(R)g(Mirroring)

                20. The Vinum Volume Manager

                             20.1. Synopsis

                             20.2. Disks Are Too Small

                             20.3. Access Bottlenecks

                             20.4. Data Integrity

                             20.5. Vinum Objects

                             20.6. Some Examples

                             20.7. Object Naming

                             20.8. Configuring Vinum

                             20.9. Using Vinum for the Root
                             Filesystem

                21. Virtualization(ueAA 3/4-: 3/4^1)

                             21.1. Synopsis

                             21.2. |w,E FreeBSD NOTDEG Guest OS

                             21.3. YENH FreeBSD NOTDEG Host OS

                22. >>y"t^3](c)w - I18N/L10N YENI-ak>>P^3](c)w

                             22.1. .S:z

                             22.2. L10N DEGoA|.S:(c)A

                             22.3. "IYENI>>y"t^3](c)w(Localization)

                             22.4. Compiling I18N Programs

                             22.5. Localizing FreeBSD to Specific
                             Languages

                23. S:o.s!BCURE-AA FreeBSD

                             23.1. .S:z

                             23.2. FreeBSD-CURRENT vs. FreeBSD-STABLE

                             23.3. S:o.sS:A-a-o Source

                             23.4. <<.s 1/2sA:P: !S:world!"

                             23.5. Tracking for Multiple Machines

   IV. -oo,o^3qDEGT

                24. Serial Communications

                             24.1. Synopsis

                             24.2. Introduction

                             24.3. Terminals

                             24.4. Dial-in Service

                             24.5. Dial-out Service

                             24.6. Setting Up the Serial Console

                25. PPP and SLIP

                             25.1. Synopsis

                             25.2. Using User PPP

                             25.3. Using Kernel PPP

                             25.4. Troubleshooting PPP Connections

                             25.5. Using PPP over Ethernet (PPPoE)

                             25.6. Using PPP over ATM (PPPoA)

                             25.7. Using SLIP

                26. ^1qCURlP:lYENo

                             26.1. .S:z

                             26.2. "IYENI^1qCURlP:lYENo

                             26.3. sendmail Configuration

                             26.4. Changing Your Mail Transfer Agent

                             26.5. Troubleshooting

                             26.6. Advanced Topics

                             26.7. SMTP with UUCP

                             26.8. Setting Up to Send Only

                             26.9. Using Mail with a Dialup
                             Connection

                             26.10. SMTP Authentication

                             26.11. Mail User Agents

                             26.12. Using fetchmail

                             26.13. Using procmail

                27. Network Servers

                             27.1. .S:z

                             27.2. The inetd !S:Super-Server!"

                             27.3. Network File System (NFS)

                             27.4. Network Information System
                             (NIS/YP)

                             27.5. Automatic Network Configuration
                             (DHCP)

                             27.6. Domain Name System (DNS)

                             27.7. BIND9 and FreeBSD

                             27.8. Apache HTTP Server

                             27.9. File Transfer Protocol (FTP)

                             27.10. File and Print Services for
                             Microsoft Windows clients (Samba)

                             27.11. Clock Synchronization with NTP

                28. " 3/4CURoAd-

                             28.1. .S:z

                             28.2. ^2L 1/2I" 3/4CURoAd-.S:(c)A

                             28.3. " 3/4CURoAd-NOTUAo:^3nAAe

                             28.4. OpenBSD <<EYEN]^1LAo 3/4^1 (Packet
                             Filter, PF)CURI ALTQ

                             28.5. IPFILTER (IPF) " 3/4CURoAd-

                             28.6. IPFW

                29. -oo,oP:iP:YEN 1/2mYEN\(c)D-

                             29.1. .S:z

                             29.2. Gateways and Routes

                             29.3. Wireless Networking

                             29.4. Bluetooth

                             29.5. Bridging

                             29.6. Link Aggregation and Failover

                             29.7. Diskless Operation

                             29.8. ISDN

                             29.9. Network Address Translation

                             29.10. Parallel Line IP (PLIP)

                             29.11. IPv6

                             29.12. Asynchronous Transfer Mode (ATM)

                             29.13. Common Access Redundancy Protocol
                             (CARP)

   V. -ath?y

                A. "u+-o FreeBSD -a-oCURe|!

                             A.1. CDROM CURI DVD uo|aeDEGO

                             A.2. FTP -,

                             A.3. Anonymous CVS

                             A.4. Using CTM

                             A.5. Using CVSup

                             A.6. Using Portsnap

                             A.7. CVS Tags

                             A.8. AFS Sites

                             A.9. rsync Sites

                B. DEGN|OCURaaA:m

                             B.1. FreeBSD NOTUAo:-a-o(R)NA:y!BAo/>>x

                             B.2. "IYENI>>!(c)uCURaYENU

                             B.3. "t^2I-oTH^2z<<u:<<n

                             B.4. u{|!^3]p(R)v<<u:<<n

                             B.5. ^2`CURJS:@.~"t^2I

                             B.6. ,e|w>>aDEG`i-a-oDEGN|OCURaaA:m

                             B.7. uwAAeCURe+--a-oDEGN|OCURaaA:m

                             B.8. UNIX  3/4uYENv^2W. 1/2

                             B.9. Ao/>>x!B'AYENZ

                C. -oo>>U-oo,oCURW-a-o,e. 1/2

                             C.1. P:l>> 1/4 1/2 * 3/4A(Mailing Lists)

                             C.2. Usenet Newsgroups

                             C.3. World Wide Web Servers

                             C.4. Email Addresses

                             C.5. Shell Accounts

                D. PGP Keys

                             D.1. Officers

                             D.2. Core Team Members

                             D.3. Developers

   FreeBSD Glossary

   -a(c)YEN>>DEGO?y

   -ath-aiYENO/?y

   2-1. uwAAe^2M^3ae(A|"O)

   2-2. ^2A:CUR@Auuw-oD--a-oCURA^3IDEGI(Partition)DEGt,m

   2-3. "a:YENLuw-oD--a-oCURA^3IDEGI(Partition)DEGt,m

   2-4. FreeBSD 5.X and 6.X ISO Image Names and Meanings

   3-1. -oI-oD- 3/4-:YENN,^1

   18-1. (c)R|W^3W<<h

   20-1. Vinum Plex Organizations

   24-1. DB-25 to DB-25 Null-Modem Cable

   24-2. DB-9 to DB-9 Null-Modem Cable

   24-3. DB-9 to DB-25 Null-Modem Cable

   24-4. Signal Names

   29-1. Wiring a Parallel Cable for Networking

   29-2. Reserved IPv6 addresses

   -ath^1IYENO/?y

   2-1. FreeBSD Boot Loader ?i^3ae

   2-2. DEG>>'uuwAAe-a-o"OCURl

   2-3. ?i 3/4U:DEGeS:O

   2-4. A-:P:} Sysinstall u{|!

   2-5. ?i 3/4U: Sysinstall YENDue+--a-o!yUsage(S:O:^3t>>!(c)u)!z

   2-6. ?i 3/4U:!yDocumentation(>>!(c)uCURaaYENo)!z?i^3ae

   2-7. Sysinstall -a-o>>!(c)uCURaaYENo(Documentation)?i^3ae

   2-8. Sysinstall YEND?i^3ae

   2-9. Sysinstall Aa: 1/2L^1iA^3?i^3ae

   2-10. Sysinstall YEND?i^3ae

   2-11. Sysinstall ?iP:u^3](c)w

   2-12. P:}(c)lP:i|ae 1/4D-.C,|w,E

   2-13. ?i 3/4U: FDisk nCURA^3I-a-ouw-oD-

   2-14. (A|"O)YEN 1/4 1/2s?e<<e-a-o Fdisk CURA^3IDEGI(Partition)

   2-15. Fdisk +-A:YENI 3/4aAuuw-oD-S:@CURA^3IDEGI(Partition)

   2-16. Sysinstall -a-o Boot Manager ?i^3ae

   2-17. A-:P:}!y?i 3/4U:uw-oD-!zue+-

   2-18. Sysinstall -a-o Disklabel  1/2s?e 3/4^1

   2-19. Sysinstall -a-o Disklabel  1/2s?e 3/4^1 !X
   "IYENI|UDEGECURADEGt

   2-20. (R)UYENO/?y-a-o-aAAP:!CURADEGt

   2-21.  *S:i(R)UYENO/?y-a-o-aAAP:!CURADEGt

   2-22. ?i 3/4U:CURA^3IDEGI-a-oAth<<NOT

   2-23. ?i 3/4U:(R)UYENO/?y-a-o+- 3/4,u:AI

   2-24. Sysinstall Disklabel  1/2s?e 3/4^1

   2-25. ?i 3/4U:n,E-a-o(R)MYENoP:DEG(Distributions)

   2-26.  1/2T>>{n|w,E-a-o(R)MYENoP:DEG

   2-27. ?i 3/4U:|w,E"O. 1/2

   2-28. ?i 3/4U:-oo,oYENd

   2-29. ^3](c)w ed0 ^3o+-i-oo,oYENd-a-o-oo,o^3](c)w

   2-30. Editing inetd.conf

   2-31. Default Anonymous FTP Configuration

   2-32. Edit the FTP Welcome Message

   2-33. Editing exports

   2-34. System Console Configuration Options

   2-35. Screen Saver Options

   2-36. Screen Saver Timeout

   2-37. System Console Configuration Exit

   2-38. Select Your Region

   2-39. Select Your Country

   2-40. Select Your Time Zone

   2-41. Select Mouse Protocol Type

   2-42. Set Mouse Protocol

   2-43. Configure Mouse Port

   2-44. Setting the Mouse Port

   2-45. Enable the Mouse Daemon

   2-46. Test the Mouse Daemon

   2-47. Select Package Category

   2-48. Select Packages

   2-49. Install Packages

   2-50. Confirm Package Installation

   2-51. Select User

   2-52. Add User Information

   2-53. Exit User and Group Management

   2-54. Exit Install

   2-55. Network Configuration Upper-level

   2-56. Select a default MTA

   2-57. Ntpdate Configuration

   2-58. Network Configuration Lower-level

   20-1. Concatenated Organization

   20-2. Striped Organization

   20-3. RAID-5 Organization

   20-4. A Simple Vinum Volume

   20-5. A Mirrored Vinum Volume

   20-6. A Striped Vinum Volume

   20-7. A Mirrored, Striped Vinum Volume

   1/2d"OYENO/?y

   2-1. "IYENI^2{|^3-a-oCURA^3IDEGI

   2-2. AY'i^2{|^3-a-oCURA^3IDEGI

   3-1. -oI-oD-!Bslice CURICURA^3IDEGI(c)R|W 1/2d"O

   3-2. -oI-oD--a-o.S:(c)A 1/4O<<NOT

   4-1. CURaDEGECURU,u:!B|w,E Package

   11-1. Creating a Swapfile on FreeBSD

   12-1. boot0 Screenshot

   12-2. boot2 Screenshot

   12-3. An Insecure Console in /etc/ttys

   13-1. |b FreeBSD CUR-o.s 1/4W"IYENI-aI

   13-2. rmuser +-b,^1^2 3/4DEG-L-

   13-3. "t^2I-oTH^2z-aI+-b,^1 chpass

   13-4. CUR@-e"IYENI-aI chpass

   13-5. S:oS:i+-z-a-o+-K 1/2X

   13-6. YENH"t^2I-oTH^2z-aI+-b,^1YENhS:oS:i"a:YENL"IYENI-aI-a-o+-K
   1/2X

   13-7. Adding a Group Using pw(8)

   13-8. Adding Somebody to a Group Using pw(8)

   13-9. Using id(1) to Determine Group Membership

   14-1. Using SSH to Create a Secure Tunnel for SMTP

   18-1. Using dump over ssh

   18-2. Using dump over ssh with RSH set

   18-3. A Script for Creating a Bootable Floppy

   18-4. Using mdconfig to Mount an Existing File System Image

   18-5. Creating a New File-Backed Disk with mdconfig

   18-6. Configure and Mount a File-Backed Disk with mdmfs

   18-7. Creating a New Memory-Based Disk with mdconfig

   18-8. Creating a New Memory-Based Disk with mdmfs

   24-1. Adding Terminal Entries to /etc/ttys

   26-1. Configuring the sendmail Access Database

   26-2. Mail Aliases

   26-3. Example Virtual Domain Mail Map

   27-1. Sending inetd a HangUP Signal

   27-2. Mounting an Export with amd

   29-1. LACP aggregation with a Cisco switch

   29-2. Failover mode

   29-3. Branch Office or Home Network

   29-4. Head Office or Other LAN

   A-1. Checking Out Something from -CURRENT (ls(1)):

   A-2. Using SSH to check out the src/ tree:

   A-3. Checking Out the Version of ls(1) in the 6-STABLE Branch:

   A-4. Creating a List of Changes (as Unified Diffs) to ls(1)

   A-5. Finding Out What Other Module Names Can Be Used:

     --------------------------------------------------------------

                                  S:C,

u^1AA-a-aI-a-o,U:

   Y+-zNOTO^2A:CUR@|,+-uA:^2 FreeBSD
   -a-o.sCURa!AYENiYENH|bYEN>>(R)N^2A:CUR@^3!CURAS:a:"`i FreeBSD
   -a-o|w,ECURe-ak!A|P(R)E.|^3v"BCURP:^2D- UNIX(R)
   -a-oDEGoA|.S:(c)A>>PCUR@"C,+-`YENI!B|@^3q-a-o-aF|e!C|O
   3/4\AA-a^3o^3!CURA"ACUR-L-Ao/!AYENu>>Yn+-z|^3+-'-A-a-o-oe-<<(c)M+-u"u:.s.S:(c)A!C

   AA-aS:^1^3o"C,CURS:<<a!ACURaYENUCURCUR-a-o^2A:CURG^3!CURA-aa<<U:-ao/
   1/2g'TCURP:^2D--a-o|U-oO/
   1/4s-axYENDAD!ANOTU.iE+-o"t^2I-oTH^2z-aIYENh-a`.N!C |b
   3/4\AA-a^3o"C,^3^1,`-a-oCUR-o(R)e(R)E(c)O>>Yn-a-oI'-o-a
   3/4AN!A^3-L-uuA:A|b,O^3^1-a-oCURj-oo,I+-!AYCUR-L-
   1/4o-a-o,U:!AYENi|b 3/4\AA-a<<eYENy^1w^2ssCUR@uf!C

   (c)u|u 3/4\AA-aCURe+-!AYENiDEGN 3/4\ -ath?y B!C

^2A:CURT-a(c)-a-oYENDn *q

   +-zYENO/<<eNOTY"`i-a-o^3oYEN>>CURaYENU^2A:CURT-a(c)NOTO FreeBSD
   CURaaYENop^1-o-a-o|"u 3/4u(R)E"a|~S:^1|"-a-oCURss|aaCURS:S:@!C
   .s-a(c)-a-oYENDn *q^3!CURA!A|pCURU!G

     * uU 11 ^3^1, ^3](c)w>>P(R)A:-`a
       1/2O(R)O(Tuning)!A,O^3^1,`DEGw^1i.sCUR-o(R)eS:@S:o.s!ACURn|p!G
       ACPI ^1q. 1/2-oTH^2z!Bcron!BYENHCURI"a:YENLS:o|h-a-o kernel
       tuning ?iP:u>>!(c)uCUR-o(R)e!C

     * uU 14 ^3^1, "t^2I|wYENth 1/2g!A,O^3^1,`
       1/4WYEN[CURFueAA"pCURH-oo,o(VPN)!BAE(R)
       *"t^2I-a-o|s"u+-+-"i(ACL)!AYENHCURI|wYENthCUR 1/2S:i(Security
       Advisories)-a-oCUR-o(R)e!C

     * uU 16 ^3^1, P:DEGAAv|!|s"u+-+-"i(MAC)NOTOYEN>>-a(c)(c)O
       1/4WYEN[-a-o^3^1,`!CYEN>>^3^1CURP:^2D-!GCURDEG>>oNOTO MAC 
       3/4-:"i!HYENHCURI|p|o^1BYENIYEN|"O"I+-z-a-o FreeBSD
       "t^2IS:o|wYENth!C

     * uU 18 ^3^1, Ax|s^3]^3AE 1/2g!A.s 1/4WCURF^1^3NOTO!GUSB
       AH"-oD-!BAE(R) *"t^2IS:O:.O(snapshot)!BAE(R)
       *"t^2IDEGtAB(quota) !BAE(R) *CURI-oo,o-a-o^3AE'(c)AE(R)
       *"t^2I!BYENHCURI|p|o^1iuw-oD-CURA^3IDEGIS:@YEN[+-KuYEN,O,N!C

     * uU 20 ^3^1VinumNOTOYEN>>-a(c)(c)O.s
       1/4W-a-o^3^1,`!CYEN>>^3^1CURP:^2D-!G|p|o^1BYENI Vinum
       ^3o-oO/AATH?e-oI-oD-(device-independent) !AYENHCURI^3nAAe
       RAID-0, RAID-1 (c)M RAID-5 !C

     * uU 25 ^3^1PPP CURI SLIP CUR@^3^1CURCUR
       1/4WYEN[CURFNOTG>>U+-AEDEG-L--a-o>>!(c)u!C

     * uU 26 ^3^1^1qCURlP:lYENoCUR@^3^1CURCUR.s
       1/4W|^3Ao:|p|o"IYENI"a:YEN|-a-o MTA u{|!!BSMTP
       >>{uy!BUUCP!Bfecthmail!Bprocmail
       -a-o^1BYENIYENHCURI"a:YEN|P:iP:YEN+-MAD!C

     * uU 27 ^3^1, -oo,o|o/-aA 3/4^1
       1/2g!ANOTO.s-a(c)CURCURYENth.s-a-oCUR@^3^1!C^3oCUR@^3^1CURP:^2D-CURF|p|oNOT[^3]
       Apache HTTP |o/-aA 3/4^1!BFTPd!AYENHCURIYENI(c)oCURa:'(c)
       Microsoft Windows client -a-o Samba |o/-aA
       3/4^1!C"a:CURCUR|^3"C,NOTq,""O|U`iYENy-a-ouU 29
       ^3^1P:iP:YEN-oo,oA^3YENICUR@^3^1!C

     * uU 29 ^3^1P:iP:YEN-oo,oA^3YENICUR@^3^1.s 1/4W|^3Ao:|b FreeBSD
       CURCUR"IYENIAAA-aTH^3]^3AE!B|w,EuL 1/2u-oo,oYENHCURI"IYENI
       ATM(Asynchronous Transfer Mode) -oo,o-a-oCURP:^2D-!C

     * 1/4WYEN[CURFCUR@YEN-:uu:.J-ai(Glossary)!AYENIYENH>>!(c)uYENth(R)NCURCURYENX^2{-a-o^3N>>y!C

     * <<.sNOTu: 1/2s(R)NCURCUR(c)O|C-a-o^1I-ai!C

^2A:CURG-a(c)-a-oYENDn *q

   YEN>>CURaYENU-a-o^2A:CURG-a(c)NOTO FreeBSD CURaaYENop^1-o-a-o|"u
   3/4u(R)E"a|~S:^1|"-a-oCURss|aaCURS:S:@!C^2A:CURG-a(c)YEN]S:tCURF|pCURU-a-oYENDnAAU:DEGE!J

     * 1/4WYEN[S:^1 3/4a-a-oYENO/?y-ACURTH!C

     * (c)O|^3-a-o ASCII ^1I-aiS:!S:i|"^1IAE(R)ae|!-a-o^1I-ai!C

     * "CO^3^1,`S:!YEN[CURJ.S:z!AYENH<<KS:O:^3t-a-oAsA:y,O^3^1,`CUR-o(R)e-oKn!BAA-a-aI(c)O+-yCURF,N-a-o^3!CURA!C

     * CUR-o(R)eNOT[-oc<<.s^2OA'|"CURTCURj^3!CURA: !S:P:}(c)l"IYENI
       FreeBSD!", !S:"t^2I-oTH^2z!", and !S:-ath?y!"!C

     * uU 2 ^3^1 (!S:|w,E FreeBSD!") CURw,g<<.sS:i
       1/4g!A"AYEN[CURJ^3\|h>>!(c)u^1ICURu!A AAy^2A:CUR@|,+-uA:^2
       FreeBSD -a-oCURH!A-a
       1/2+-uNOTY^1I'N<<U:^2M.!(c)uAA<<AI(CUR@^1I(c)eCURd|r-a-o(R)A:-aG)!C

     * uU 3 ^3^1(!S:UNIX DEGoA|.S:(c)A 1/2g!").s 1/4WCURF processes,
       daemons (c)M signals -a-oCURP:^2D-!C

     * uU 4 ^3^1 (!S:^3nAAe(R)MYENo-oTH^2z 1/2g!").s
       1/4WCURFCURP:^2D-|p|o-oTH^2z binary package
       (R)MYENo-a-o,eDEGT!C

     * uU 5 ^3^1 (!S:X Window uo/u!"t^2I 1/2g!") ,g^1LYENth+-S:i
       1/4g!AuU<<(c)o|b XFree86(TM) 4.X CURW-a-oNOTy|ae
       x11-wm!A^1^3NOTO!G KDE (c)M GNOME !C

     * uU 12 ^3^1 (!S:FreeBSD P:} 3/4-:NOTyu{
       1/2g!")S:o.sNOTUAo:CUR-o(R)e!C

     * uU 18 ^3^1 (!S:Ax|s^3]^3AE 1/2g(Storage)!")
       CURAS:OYENH"aO^3^1,` !S:Disks!" >>P !S:Backups!" "O 1/4P:
       1/4g!CS:UI>>{NOTDEG^3o
       1/4ECURl.|CURn^3aeCUR@^3^1,`"O+-o(R)e(c)o:AA,N!CAU|^3Ao:(c)o
       RAID(YEN]S:tuwAAe!B^3nAAeRAID) -a-oNOTq,"CUR].s
       1/4WCURWYENhCURF!C

     * uU 24 ^3^1(!S:Serial ^3qDEGT 1/2g!")NOT[-oc<<.sS:i
       1/4g!A"AS:o.s|U: FreeBSD 4.X/5.X -a-oCUR-o(R)e!C

     * uU 25 ^3^1 (!S:PPP CURI SLIP!")|^3NOTU.iu{<< *-a-oS:o.s!C

     * uU 29 ^3^1(!S:P:iP:YEN-oo,oA^3YENI
       1/2g!")YEN[CURJ^3\|h.sCUR-o(R)e!C

     * uU 26 ^3^1 (!S:^1qCURlP:lYENo 1/2g!")CURjP:q.s 1/4WCURF^3](c)w
       sendmail -a-oCURP:^2D-!C

     * uU 10 ^3^1 (!S:Linux(R) NOTU(R)e 1/2g!") 
       1/4WYEN[^3\|h|^3Ao:|w,E Oracle(R) CURI SAP(R) R/3(R)
       -a-oCURP:^2D-!C

     * |^1YEN~!A^2A:CURG-a(c)AU.sYEN[^3^1,`!AYENHCURP:^2D-CURU|C+-MAD!G

          * uU 11 ^3^1, ^3](c)w>>P(R)A:-`a 1/2O(R)O(Tuning)!C

          * uU 7 ^3^1, |h'CAAe 1/4vu(R)T 1/4O:(Multimedia)!C

YEN>>(R)NNOT[-oc

   YEN>>(R)NYENDnCURANOTDEGCURCURj^3!CURA!A^2A:CUR@^3!YEN-:!yP:}(c)l"IYENI!z!GCURP:^2D-
   FreeBSD -a-o|w,E!BDEGoYEN>> 3/4THS:@!C AA-a-aIYENi(R)U
   3/4U|UCURv-a-ou{<< *!A'`S:C,(c)I-aI,o^1LCUR@"C,
   1/4o+-x-a-oYENDAD"O 3/4\AA-a!F ^2A:CURG^3!CURA!y+-`YENI
   3/4THS:@!z!GCURP:^2D- FreeBSD
   +-`YENIYEN\-`a!A^3o^3!CURAYENiYENHCUR-L-<<o:P:P:S:C,"OAA-a!C
   "C^3^1<<e+-^3-L-.||^3.S:z!A.S:z.|'yzYEN>>^3^1,`^2[>>\-a-oCUR-o(R)e(c)MAA-a-aIA^3,OCURw-a
   3/4-a-o!A ^3oYENDnNOTOAAyAA-a-aIYENiYENHNOTD^3ssAAw-a-o^3^1,`
   3/4\AA-a!F ^2A:CURT^3!CURA!y"t^2I-oTH^2z!z!GCURP:^2D- FreeBSD
   |NCURa(c)O.P?^3 1/2`i-a-o|U-oO/+-MAD^3!CURA!F
   ^2A:YEN|^3!CURA!y-oo,o^3qDEGT!z!G<<hYEN]NOTA-oo,o(c)M|U|! Server
   +-MAD!F|O^2A:CUR^3!CURA!y-ath?y!z!GNOTO|U-oO/|^3Ao: FreeBSD
   -a-o,e. 1/2!C

   uU 1 ^3^1, A^2CURP: 1/2g

           |V.sCURaCURP:^2D- FreeBSD!C,O 1/2g>>!(c)uCURF FreeBSD
           p^1-o-a-o 3/4uYENv!BYENO/ 1/4D-(c)MP:}uo 1/4O|!!C

   uU 2 ^3^1, |w,E 1/2g

           CURP:^2D-|w,Eu{S:C,!C"a:CURCURAU|^3CURP:^2D-CUR@"C,P:iP:YEN-a-o|w,EYENDAD!AYEN]NOTA^1^3NOTO|p|o^3z^1L
           serial console "O|w,E!C

   uU 3 ^3^1, UNIX DEGoA|.S:(c)A 1/2g

           Covers the basic commands and functionality of the FreeBSD
           operating system. If you are familiar with Linux or
           another flavor of UNIX then you can probably skip this
           chapter.

   uU 4 ^3^1, ^3nAAe(R)MYENo-oTH^2z 1/2g

           Covers the installation of third-party software with both
           FreeBSD's innovative !S:Ports Collection!" and standard
           binary packages.

   uU 5 ^3^1, X Window uo/u!"t^2I 1/2g

           Describes the X Window System in general and using X11 on
           FreeBSD in particular. Also describes common desktop
           environments such as KDE and GNOME.

   uU 6 ^3^1, Desktop Applications

           Lists some common desktop applications, such as web
           browsers and productivity suites, and describes how to
           install them on FreeBSD.

   uU 7 ^3^1, Multimedia

           Shows how to set up sound and video playback support for
           your system. Also describes some sample audio and video
           applications.

   uU 8 ^3^1, Configuring the FreeBSD Kernel

           Explains why you might need to configure a new kernel and
           provides detailed instructions for configuring, building,
           and installing a custom kernel.

   uU 9 ^3^1, |C|L 1/2g

           Describes managing printers on FreeBSD, including
           information about banner pages, printer accounting, and
           initial setup.

   uU 10 ^3^1, Linux Binary Compatibility

           Describes the Linux compatibility features of FreeBSD.
           Also provides detailed installation instructions for many
           popular Linux applications such as Oracle, SAP R/3, and
           Mathematica(R).

   uU 11 ^3^1, Configuration and Tuning

           Describes the parameters available for system
           administrators to tune a FreeBSD system for optimum
           performance. Also describes the various configuration
           files used in FreeBSD and where to find them.

   uU 12 ^3^1, Booting Process

           Describes the FreeBSD boot process and explains how to
           control this process with configuration options.

   uU 13 ^3^1, Users and Basic Account Management

           Describes the creation and manipulation of user accounts.
           Also discusses resource limitations that can be set on
           users and other account management tasks.

   uU 14 ^3^1, Security

           Describes many different tools available to help keep your
           FreeBSD system secure, including Kerberos, IPsec and
           OpenSSH.

   uU 16 ^3^1, Mandatory Access Control

           Explains what Mandatory Access Control (MAC) is and how
           this mechanism can be used to secure a FreeBSD system.

   uU 18 ^3^1, Storage

           Describes how to manage storage media and filesystems with
           FreeBSD. This includes physical disks, RAID arrays,
           optical and tape media, memory-backed disks, and network
           filesystems.

   uU 19 ^3^1, GEOM

           Describes what the GEOM framework in FreeBSD is and how to
           configure various supported RAID levels.

   uU 20 ^3^1, Vinum

           Describes how to use Vinum, a logical volume manager which
           provides device-independent logical disks, and software
           RAID-0, RAID-1 and RAID-5.

   uU 22 ^3^1, Localization

           Describes how to use FreeBSD in languages other than
           English. Covers both system and application level
           localization.

   uU 23 ^3^1, The Cutting Edge

           Explains the differences between FreeBSD-STABLE,
           FreeBSD-CURRENT, and FreeBSD releases. Describes which
           users would benefit from tracking a development system and
           outlines that process.

   uU 24 ^3^1, Serial Communications

           Explains how to connect terminals and modems to your
           FreeBSD system for both dial in and dial out connections.

   uU 25 ^3^1, PPP and SLIP

           Describes how to use PPP, SLIP, or PPP over Ethernet to
           connect to remote systems with FreeBSD.

   uU 26 ^3^1, Electronic Mail

           Explains the different components of an email server and
           dives into simple configuration topics for the most
           popular mail server software: sendmail.

   uU 27 ^3^1, Network Servers

           Provides detailed instructions and example configuration
           files to set up your FreeBSD machine as a network
           filesystem server, domain name server, network information
           system server, or time synchronization server.

   uU 28 ^3^1, Firewalls

           Explains the philosophy behind software-based firewalls
           and provides detailed information about the configuration
           of the different firewalls available for FreeBSD.

   uU 29 ^3^1, Advanced Networking

           Describes many networking topics, including sharing an
           Internet connection with other computers on your LAN,
           advanced routing topics, wireless networking, bluetooth,
           ATM, IPv6, and much more.

   -ath?y A, Obtaining FreeBSD

           Lists different sources for obtaining FreeBSD media on
           CDROM or DVD as well as different sites on the Internet
           that allow you to download and install FreeBSD.

   -ath?y B, Bibliography

           This book touches on many different subjects that may
           leave you hungry for a more detailed explanation. The
           bibliography lists many excellent books that are
           referenced in the text.

   -ath?y C, Resources on the Internet

           Describes the many forums available for FreeBSD users to
           post questions and engage in technical conversations about
           FreeBSD.

   -ath?y D, PGP Keys

           Lists the PGP fingerprints of several FreeBSD Developers.

YEN>>(R)N-a-o 1/2s+-AEAAeuo

   NOTDEGCURe<<K
   3/4\AA-aYEN>>(R)N!AYENHCURUNOTOCUR@"C,YEN>>(R)N(c)O?i'`-a-o
   1/2s+-AEAAeuo!G

  CURaa|r 1/2s+-AEAAeuo

   +- *AAe|r(Italic)

           +- *AAe|r<<NOT(Italic)
           YENI(c)o!GAE|W!BYENO/?y!B-ooS:}(URL)!B +-j
           1/2O>>y(R)d-!BYENHCURI^2A:CUR@|,'-L-CURI-a-oS:TH^3Nuu:.J!C

   (c)w 1/4e|r(Monospace)

           (c)w 1/4e|r(Monospace) YENI(c)o!G
           ?u>>~DEGT(R)S:!B<<u:YENO!BAo^1OAAU: 1/4AE!Bport
           |W-oU!BYEND
           3/4-:|W-oU(hostname)!B+-b,^1!B,s^2O!B^3]^3AE(device)|W-oU!BAAU:
           1/4AE!B u{|! 1/2XuYEN!C

   ^2EAAe|r<<NOT(Bold)

           YENH^2EAAe|r-aiYENU:!GA^3YENIu{|!!B(c)RYENO!B<<o:Aa:!C

  "IYENI-aI?eCURJ

   Aa: 1/2L?eCURJYENH ^2EAAe|r(Bold)
   -aiYENU:!AYENH<<K>>PCUR@-eCURaa|rDEGuDEGI^1j!C
   ^2O|XAa:NOTO<<u:|P(R)E<<o:CURUCUR@"C,<<o:Aa:!AS:UIYENH `+'
   "O-aiYENU:^3s+-u!A^1^3NOTO!G

   Ctrl+Alt+Del

   CUR]'NNOTO>>!!ACUR@DEG_<<o: Ctrl Aa:!B Alt Aa:!AYENHCURI Del Aa:!C

   Yn^3vCUR@<<o:Aa:!A"-o>>o.|YENH^3r,^1(,)"O-aiYENU:!A^1^3NOTO!G

   Ctrl+X, Ctrl+S

   CUR]'NNOTO>>!!GYENy|P(R)E<<o:CURU Ctrl >>P X Aa:!A
   uM<<a(c)nP:}<<a|A|P(R)E<<o: Ctrl >>P S Aa:!C

  A|O^1e"O

   CURU+-"OCURlYENH E:\> NOTDEGP:}AY-a-oYENN-ai MS-DOS(R)
   <<u:YENO^3!CURA!C
   Y"S|^3-S(R)i+-!-ap-a-o,U:!A^3o"C,<<u:YENOA^3,ONOTO|b
   Microsoft(R) Windows(R) Ao^1O-a-o
   !S:(c)RYENO'-L-YENU:|rCUR,(Command Prompt)!" CUR-oDEGo|ae!C

 E:\> tools\fdimage floppies\kern.flp A:

   "OCURlYNOTOYENyYENH #
   NOTDEGP:}AY|A+-u<<u:YENO-a-o,U:!A'NNOTO<<u:|b FreeBSD CURCURYENH
   root AAv"OCURU(c)RYENO!C S:AYENiYENHYENyYENH
   rootunCURJ"t^2I"ACURU<<u:YENO!A(c)INOTOYENHS:A|UCURv-a-o+-b,^1unCURJ!A"A"IYENI
   su(1) "O"u+-o root AAv!C

 # dd if=kern.flp of=/dev/fd0

   "OCURlYNOTOYENyYENH %
   NOTDEGP:}AY|A+-u<<u:YENO-a-o,U:!A'NNOTO<<u:|b FreeBSD
   CURCURYENHCUR@-e+-b,^1"OCURU(c)RYENOS:YYENi!C
   DEG-L-<<D|^3'-L-"`i"a:YENLYENI-ak!AS:_<<h^3-L-NOTO^1w^3]NOTDEG
   C-shell(csh/tcsh) >>y-ak!AYENI"O^3](c)wAo^1OAAU:
   1/4AEYENHCURICURU"a:YENL<<u:YENO-a-o.N<<a:!C

 % top

PAA

   +-z(c)ONOTY"`i-a-o^3oYEN>>(R)NNOTO,g^1L
   1/4AE|EOCURA'^2|bYEN@NOTE|U|a-a-oCURH(c)OS:VCURO|O"O-a-ou^2-aG!C
   uL 1/2 *YENLIYENuNOTO-aEYEN?CUR@"C,?u>>~(c)I'-L-YENaeS:^1
   3/4a-a-o^3^1,`!A(c)O|^3-a-oAI-owDEG^A:m^3-L-NOTO<<D+-`A:_P:Q|^3YENI-a-o!C

   CUR]|^3CUR@"C,CUR 1/2YENq^3z^1L'-L-"N,e-a-:AAyS:@-aI+-M-a`(c)o
   1/4P: 1/2Z!B'-L-"NYENX-a(c),e-a-:uYEN
   1/4O|!"OCURa:<<uCURaaYENo-a-o 1/4gS:@!C "a:CURCUR!ABSDi
   (CURS:<<a"O:CURJ Wind River Systems) ,eS:U FreeBSD
   CURaaYENop^1-o|"u"O+-MA 3/4S:iu 1/2^3oYEN>>(R)N-a 1/2"`i 2000 |~ 3
   CURe^2A:CUR@-a(c)-a-oYENX-a(c)!C(ISBN 1-57176-241-8) Wind River
   Systems
   |P(R)E,eS:U"a:YENLS:@-aI"O^1i?eYENXNOT[-ocDEGu<<U:|hS:iP:i!AYENHCURIu^1CURaa^3^1
   1/4WYEN[CUR@"C,-athYEN[^3^1,`!C^3oP:uCURuS:@u^2S:o(c)o 2001 |~ 11
   CURe^2A:CURG-a(c)!C(ISBN 1-57176-303-1) |b 2003-2004
   "a|~CURCUR!AFreeBSD Mall
   S:a^3o/^1SCURa:YENIu^1S:iP:i^3oYEN>>CURaYENUYENH"I^2A:CURT-a(c)|L"e-a(c)YEN>>-`aDEG-:YENX-a(c)-a-oS:OCURu!C

                        I. P:}(c)l"IYENI FreeBSD

   ^3o^3!YEN-:NOTO'-L-"Nu^1-a`i|,"IYENI FreeBSD
   -a-o"IYENI-aI(c)M"t^2I-oTH^2z-aI!C ^3o"C,^3^1,`YEN]NOTA!G

     * CURP:^2D- FreeBSD u^1+-z!C

     * |b|w,E^1Lu{u^1+-z<<u:CURTH!C

     * +-D-+-z UNIX -a-oDEGoA|CURI`i^2z!C

     * (R)iYENU:u^1+-zNOTY|p|o|w,EA *'I-a-o FreeBSD -a-oA^3YENI^3nAAe

     * |V+-zCURP:^2D- X!A UNIX
       -a-ouo/u!"t^2IYENHCURI,O^2O-a-o(R)`a+-Ao^1O^3](c)w!AAAy+-zS:o|^3YENI^2-L-CURO!C

   S:UI,OuU 3/4"YENi-`a-a-oAAy^3oNOTqCURaa|r-a-oDEGN|O^3su^2
   1/4AEYENO/DEG"`i^3IS:C!AAAy+-z|bAA-a"IYENICURaYENU-a-o^3o^3!YEN-:(R)EYENiYENHCUR-L-CURO>>Yn+-`+-`<<e<<aA
   1/2P:!C

   CUR-o(R)eYENO/?y

   1. A^2CURP:

   2. |w,E FreeBSD

   3. UNIX DEGoA|.S:(c)A

   4. ^3nAAe(R)MYENo-oTH^2z 1/2g!GPackages CURI Ports  3/4-:"i

   5. X Window uo/u!"t^2I

     --------------------------------------------------------------

                            ^3^1 1. A^2CURP:

   Restructured, reorganized, and parts rewritten by Jim Mock.

1.1. .S:z

   <<D+-`.PAA+-z^1i FreeBSD .P?^3 1/2`i!IYENHCURU^3^1,`^2[>>\ FreeBSD
   p^1-o-a-o|UCURe+-!GCURn|pYEN|-a-o 3/4uYENv!BYENO/ 1/4D-!BP:}uo
   1/4O|!uYENuYEN!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!J

     * FreeBSD >>P"a:YENL OS CURS:P:!-a-oAo:<<Y!F

     * FreeBSD p^1-o-a-o 3/4uYENv. 1/2NOTy!F

     * FreeBSD p^1-o-a-oYENO/ 1/4D-!F

     * FreeBSD open-source P:}uo 1/4O|!-a-oDEGoA|.S:(c)A!F

     * .iuMAAo!AAU|^3 !S:FreeBSD!" ^3o|W|r-a-oYENN"O!C

     --------------------------------------------------------------

1.2. Welcome to FreeBSD!

   FreeBSD NOTOCUR@O+-q 4.4BSD-Lite lYENIYENX|O-`a|bYENH Intel (x86
   and Itanium(R)), AMD64, Alpha(TM), Sun UltraSPARC(R)
   NOTDEGDEGoA|-a-o^1q,-L-CURWDEGo|ae-a-oS:@.~"t^2I!C|P(R)E!A^2
   3/4'O"`i"a:YENLYENYENx-a-oCURuS:@CUR]|bP:i|aeCURCUR!C
   ^1i(c)oYEN>>p^1-o 3/4uYENv-a-oCURP:^2D-!A 1/2D-NOTY FreeBSD 
   3/4uYENv. 1/2NOTy!A ^1i(c)o FreeBSD -a-o^3I.s-a(c)YEN>>CURP:^2D-!A
   1/2D-NOTY current release !CYYEN'-oa^1i(c)o FreeBSD
   p^1-o|^3(c)ODEG^A:m-a-o,U:(^1^3NOTOu{|!
   1/2XuwAAe^3]^3AE!BDEGo-a-:)!A  1/2D-NOTY |p|o^1i FreeBSD
   |^3DEG^A:m!C

     --------------------------------------------------------------

  1.2.1. FreeBSD -`aDEGuCURDEG>>o!H

   FreeBSD '-L-"Nu^1S:A^3\|hYENyP:iYEN\-`a!C^3o"C,YEN\-`aYEN]NOTA!G

     * DEGE-oAAuYENyAAv 1/2O 3/4a-a-o!yYENy|u|!|hCURu!z-`aDEG-:
       1/2T<<O!AS:Y"I|b"t^2It 3/4a<<U:<<-a-o+-!-apCURU!A
       u{|!DEGo|aeYENP:P:"AYENBA^3YENIu{|!>>P"IYENI-aICUR
       1/2YEN|a|@"E,e. 1/2!C

     * !y|hCURH|@YENI(multi-user)!zYENN-aiuU^3\|hCURHYENiYENH|P(R)E"IYENICUR@O
       FreeBSD "t^2I"O^3B^2z|U|U-a-o"AEDEGE!C
       "t^2I-a-ouwAAe(c)PAa:(|p|L-ai 3/4-:CURI-oI+-a
       3/4-:)CUR]YENiYENHAAy(c)O|^3-a-o"IYENI-aI 3/4A.i|aCURA"E!C
       CUR]YENiYENHDEGw^1i|US:O"IYENI-aI(c)ICUR@,s"IYENI-aI-a-o"t^2I,e.
       1/2!ACUR(c)YENH^3]!A YENH<<OAA@"t^2ICUR-L-P^3Q^1L<< *"IYENI!C

     * |nYENI-a-o!yTCP/IP -oo,oYEN\-`a!zYENiCURa:'(c)^3\|h.~NOTE
       1/4D-.C,!ACURn|p!G
       SCTP!BDHCP!BNFS!BNIS!BPPP!BSLIP!BIPSec!BIPv6
       -a-oCURa:'(c)!ACUR]'NNOTO>>! FreeBSD
       YENiYENH(R)e(c)o:|a,o"a:YENLS:@.~"t^2I^3z^1L-oo,o|@|P^1BS:@!A(c)INOTO.iS:@YENo/.~-a-o|o/-aA
       3/4^1YENI^3~ !A"O|p'-L-"N>>.-oYAE(R)
       *|@"E(NFS)CURI^1qCURlP:lYENo(email)uYEN-aADEGE!A
       (c)INOTOAAy+-z-a-oYENo/.~^3sCURW-oo>>U-oo,o(Internet)"A'-L-"N
       WWW!BFTP!B ,oYENN(routing)!BCURI"
       3/4CURoAd-(firewall!Bsecurity) uYENYEN^2^3AE-aADEGE!C

     * !yDEGO 3/4D-AAe<<OAA@(Memory protection)!z-`a
       1/2T<<Ou{|!((c)INOTO"IYENI-aI)CUR-L-.|CURNOTNOTUCURzAZ!A
       S:Y"IYENo|ou{|!|^3CUR-L-YEN?+-`-a-o^1BS:@!A^3-L-CUR-L-.|
       1/4vAAT"a:YENLu{|!-a-oDEGo|ae!C

     * FreeBSD NOTO!y32|`iCUR,(32-bit)!z-a-oS:@.~"t^2I (|b
       Alpha!BItanium!B AMD64 CURI UltraSPARC
       CURW<<hNOTO!y64|`iCUR,(64-bit)!z) !X
       YEN'+-qCUR@P:}(c)l<<KNOTO^3o 1/4E^3]p-a-o!C

     * .~NOTE 1/4D-.C,-a-o!yX Window
       "t^2I!z(X11R7)YENiYENH|b+-`"-L--a-o<<K(c)y VGA
       AAaYENU:YENd/?A^1o!A
       '-L-"NCURF^1IS:ICURAE-a-o"IYENI-aICURP:+-(GUI)!A"AYENBYEN]NOTACURFS:^1
       3/4a-a-o`i(c)lu{|! 1/2X!C

     * -`a!y-a 1/2+-uDEGo|ae!z^3\|h"a:YENLS:@.~"t^2I(CURn|p!G
       Linux!BSCO!BSVR4!BBSDI (c)M NetBSD) -a-oYENiDEGo|aeAE!C

     * 1/4AEYENH,Up-a-oYENssS:YYENiYENHDEGo|ae-a-oA^3YENIu{|!!A^3o"C,^3-L-YENi^3z^1L
       FreeBSD -a-o!yports!zCURI!ypackages!z^3nAAe-oTH^2z
       3/4-:"i"O"u+-o!C
       CUR-L-|A>>YnP:OCURss"`i-oo,oCURW"`i^3B.j'M(c)O>>Yn-a-o^3nAAe!C

     * |^1YEN~!A-oo,oCURW(c)||^3YENi<<D+-`(R)e(c)o:^2 3/4'O-a-o
       1/4AEYENH,UpA^3YENIu{|!!C FreeBSD -a-o`i(c)lu{|!
       1/2X>>P^3\|h+-`"-L--a-oDEGO.~-a(c) UNIX "t^2I^3-L-NOTU(R)e!A
       (c)OYENHCURj^3!CURA-a-ou{|!^3-L-YENu>>Yn<<U:CURO:-a-o
       *S:i((c)I(R)UYEN>>CUR-L-YENI *S:i) !A'NYENiYENH
       1/2sA:P:DEGo|ae!C

     * >>Yn(R)ECUR~,m'<<(demand paged) virtual memory CURI !S:merged
       VM/buffer cache!" -a-o^3]p!A
       ^3oAI|b"t^2ICURCUR|^3YENIYENhCURjP:qDEGO
       3/4D-AAe-a-ou{|!DEGo|ae(R)E!ACUR'uM|^3CUR-L-?u-a-o(R)A:^2v-ai^2{!C

     * CURa:'(c) CPU -a-o^1i-oU|hCURu^3B^2z(SMP)!GYENiYENHCURa:'(c)|h
       CPU -a-o^1q,-L-"t^2I!C

     * S:^1YENthNOTU(R)e-a-o C!BC++ YENHCURI Fortran
       -a-oAo^1O(c)M"a:YENLP:}uoCURu"a!C
       YENHCURI"a:YENL^3\|hYENi"NP:iP:YENNOTauo-a-ou{|!>>y"YENCUR]|NOTP:DEG|b
       ports (c)M packages!C

     * 3/4aO"t^2I^3-L-|^3!y`i(c)lu{|! 1/2X!z!A ^3oAAyS:A^1iS:@.~Ao^1O
       3/4O:|^3^3IS:^1YENth-a-o'x'CUR<< *!C NOTJuM-`a
       3/4O:|^3S:^1YENthP:}(c)n-a-o"t^2I!A|oW^3Q-S(c)w<<E^3NOT^3nAAe(c)ONOTuS:o!AYENo
       1/4tDEGOA\S:G(c)O!H

     * 1/4s-axYENBA *'I-a-o!y 1/2uCURWCURaaYENo!z!C

     * .iuMAAo!AAUCUR-L-CURi|p|^1!I

   FreeBSD "t^2ICURDNOTODEGo(c)oNOTu:DEGeYEN[|{CURj
   3/4C,NOTfS:JuU:CURA(R)O-a-o^1q,-L-"t^2INOTa"s,s (Computer Systems
   Research Group CUR]'NNOTO CSRG) (c)Ouo|ae-a-o
   4.4BSD-Lite!AYENHCURIDEGo(c)o BSD "t^2IP:}uo-a-oAu"}P:C,^2I!C
   DEG-L-CURFYENN CSRG (c)O'-L-"N-a-oDEG-a<<~ 1/2e-a-o|"-aG!A
   NOTDEGCURF'-L-"NYENi^3B^2z-uYEN?"at^2u:-a-oCURuS:@!A FreeBSD
   p^1-oCUR]S:eCURJCURF 1/4AECURdCURp(R)EYENHCURW-a-o^2O^3! 1/2O
   3/4a!A
   YENH-`aAo+-o^3I|n-a-oDEGo|ae(R)A:^2vYENHCURI"t^2I-a-oA(c)w<< *!C
   YEN?.i^3\|hDEGO.~CURW-a-oYEN"CURHYEN?S:VCURO|aS:AE+-ae-`a'-L-"N(R)A:-`aCURIA(c)w(R)E!A
   FreeBSD CURw,g"a^3AE^3o 1/4E-a-o-S 1/2e -- 'NNOTO^2{|b!I

   FreeBSD -a-o^1BYENI
   1/2d^3ouL!A"a:^1eS:^1YENth"i|bS:A-a-o.Q^1^3CUROCURW!C
   +-q^3nAAe-a-oP:}uo"`iCURu 1/4t|UDEGECURAE!A(c)INOTOCURH^3y
   1/2ANOTPCURW+--a-oCURN 1/2u-a-oCURe|`i"CUR<< *-a-o>>.-oY+-+-"i!F
   ^3o"C,YEN\-`aYYENiYENHYENIDEGOYENI-a-o Unix ^2-L-<<~"O^1F|"!A
   "-o>>o.YEN|^3YENi-`a"IYENI FreeBSD CUR]-`a?`i"`i!I FreeBSD
   CUR]"u:-q(c)o"O|U(c)oYENth^2y|UNOTa"sCURCURCURssCURICURj
   3/4C,(c)OP:}uo-a-o 1/4AECURdODEG-a<<~ 1/2e-a-o^3nAAe
   !A^3o"C,^3q+-`YENu>>Yn-aaP:O<<U:CURO:-a-oP:OYENI(c)I(R)UYEN>>'NNOTOS:KP:O-a-o!C
   .iuMCUR]|^3DEGO.~^3nAAe!A|OYENBYENX^2{-a-o 1/4AEYENO/NOTO>>PCUReN
   1/4W!C

   YENN(c)o"COCURH^3-L-YENiYENH"u+-o FreeBSD -a-o`i(c)lu{|! 1/2X!A
   ^3oO"t^2IYENiYENH^3Q 1/2O
   3/4a|O-`aDEGo|aeYENo|o`iYEN>>S:^1YENthuL-ak.Q^1^3-a-oYEN\-`a(c)Ip^1-o!A
   |O^1i(c)o+-q|U 1/4tDEGO"u+-o-a-oS:@.~"t^2I^3q+-`"S|^3?`i-ak^3o
   1/4E|a^3Q *S:i!C YENHCURU'-L-"NCUR@"C,CURHI"IYENI FreeBSD
   -a-o"OCURl!G

     * -oo,o-aADEGE!G FreeBSD
       CUR-o<<O/+-j<<l-a-o-oo,oYEN\-`a"IYEN||"NOTDEG-oo,o-aADEGE(|pCURU"O)-a-o^2z.QYENYENx!G

          * AE(R) *|o/-aA 3/4^1(FTP servers)

          * YENth^2y,eDEGT-oo|o/-aA 3/4^1(WWW servers) (
            1/4D-.C,-a-o(c)IS:o|wYENth-a-o [SSL] ^3s 1/2u)

          * IPv4 CURI IPv6 routing

          * " 3/4CURoAd-YENHCURI NAT (!S:IP masquerading!")
            gateways!C

          * ^1qCURlP:lYENo|o/-aA 3/4^1(Electronic Mail servers)

          * -oo,o.s>>D|o/-aA 3/4^1(USENET News)
            (c)INOTO^1qCURlS:GS:iA:ae"t^2I(BBS)

          * AU|^3S:o|h...

       |^3CURF FreeBSD!A+-zYENiYENH(R)e(c)o:|aYENyYENI<<K(c)y-a-o 386
       PC!A |A^3v"BCURE-AA+-z-a-o 3/4-: 3/4^1"`iYEN|O CPU -a-o Xeon
       "A"IYENI-oI-oD-DEG}|C(RAID)"O-o!"NOT+-zYENo/.~^1BYENICURW-a-o>>Y"D!C

     * +-D-"|!G Y+-zNOTO,eCURuNOTUAo:>>aDEG`i-a-o
       3/4C,YENI!A|ACUR]"S|^3CURn"IYENI FreeBSD -`a
       3/4C,"`iS:o|hS:@.~"t^2I!Bp-oa
       3/4-:u^2-oc!BCURI-oo,o-a-oCURe-akCURF!C
       YENtYEN~|p-aGS:A.QS:QYENI^1q,-L-"O^3B^2zCUR@"C,"a:YENL-a-o
       CURuS:@!AAU|^3CUR@"C,|p CAD!B  1/4AE
       3/4C,^1B-oaYENHCURI^1IS:I^3B^2z^3nAAeuYENYENiYENHS:KP:O|a"u+-o"IYENI!C

     * NOTa"s!G|^3CURFS:^1 3/4a-a-o`i(c)lu{|! 1/2X!AFreeBSD
       NOTONOTa"sS:@.~"t^2ICURI^1q,-L-NOT`i 3/4C,-a-o.YEN"IAo^1O!C
       "a|^3S:KP:OYENB|UYENN"u+-o-S(c)E-a-o FreeBSD
       CUR]"I+-oCUR@OCURA,m"a|a-a-o|XS:@p^1-o!ACUR-L-YEN^2
       3/4aCURss-a(c)AAvCURI"t^2IP:}(c)n(c)E-a-oDEGYAD!A
       |O-`a|U|b-a-oYENaeNOTy!C

     * -oo,o!G S:A|p-aG>>Yn router!BName Server (DNS)
       (c)I|wYENth-a-o" 3/4CURoAd-(Firewall)!A FreeBSD
       YENiYENH>>'(c)o:-a-o+-NS:A"S|^3YENI"`i-a-o 386 (c)I 486 PC
       AAU:"|"NOTDEGu'"I-a-o|o/-aA
       3/4^1!ANOTAE|U:"a|^3^1LAo<<EYEN](packet-filter) -a-oYEN\-`a!C

     * X uo/u!CURuS:@-,!G FreeBSD NOTO X ^2 *-oY
       3/4-:-a-o"}u|!AS:AYENiYENH"IYENIS:KP:O-a-o X11 Server!C
       FreeBSD CUR-L-|yYENiYENHYENR.i>>.-oY X u{|!^2 *-oY 3/4-:!A
       CUR]YENiYENHDEGo|aeYEN>>|a-a-o X
       u{|!|O'i>>'CURj<<NOTCURuS:@-,-a-ot^2u:!C
       |p-aG|^3CUR@YENxCURCURYEN!|o/-aA 3/4^1-a-o,U:!AFreeBSD
       NOTAE|U:YENiYENH,gYENN-oo,oP:} 3/4-:
       (CUR-L->>Yuw-oD-!ACUR]'NNOTO!S:diskless!")
       !A|OAAU:|"S:o<<K(c)yYENB(c)o:(c)o-oTH^2z-a-oCURuS:@-,!C

     * ^3nAAeP:}uo!G DEGoYEN>>|w,E-a-o FreeBSD 'NYEN]S:tCURFS:^1
       3/4a-a-ou{|!P:}uoCURu"a!A|p GNU C/C++  1/2sA:P:
       3/4^1CURIDEG-L-?u 3/4^1!C

   S:AYENiYENH,gYENN?N?y CD-ROM!BDVD (c)INOTO+-q FTP -,CURWS:`i|^
   FreeBSD --
   YEN]NOTAYENssS:YYENiDEGo|ae-a-o"t^2IYENHCURI"t^2I-a-oS:^1 3/4au{|!
   1/2X!C ,O+-! 1/2D-DEGN 3/4\ -ath?y A "u+-o FreeBSD!C

     --------------------------------------------------------------

  1.2.2.  1/2O:|bYENI FreeBSD!H

   ^3\|h Internet CURW-a-oCURj<<NOT-oo-,^3-L-NOTOYENH FreeBSD
   S:@NOTDEGYEN|-a-oS:@.~"t^2I!A"O|p!G

     * Yahoo!

     * Apache

     * Blue Mountain Arts

     * Pair Networks

     * Sony Japan

     * Netcraft

     * Weathernews

     * Supervalu

     * TELEHOUSE America

     * Sophos Anti-Virus

     * JMA Wired

   YENHCURI^3\|h"a:YENL-a-o-oo-,!C

     --------------------------------------------------------------

1.3. Ao:(c)o FreeBSD p^1-o

   +-uCURU"OA?-a-oNOTO FreeBSD p^1-o-a-oI'-o!AYEN]S:t 3/4uYENv.
   1/2NOTy-a-oA^2CURP:!Bp^1-o-a-oYENO/ 1/4D-!AYENHCURIP:}uo-a-o
   1/4O|!!C

     --------------------------------------------------------------

  1.3.1. FreeBSD  3/4uYENv. 1/2NOTy-a-oA^2CURP:

   Contributed by Jordan Hubbard.

   FreeBSD pue-a-o.Q-akNOTO|b 1993 |~-a`i(c)OS:I|"-a-o!A "-oNOTO.
   1/2|U(c)o-ouAA@CUR@^2O !y<<D(c)xCURe 386BSD -a-o patchkit(
   *YEN?CURu"a)!zp^1-o-a-oCURTO"o 1/2O-ouAA@CURH Nate Williams!ARod
   Grimes (c)MS:U(Jordan Hubbard)!C

   S:UI^3I-a`i-a-oYENO/ 1/4D-NOTODEGuYENXCUR@YEN-: 386BSD -oi|X
   *YEN?-a-o snapshot -a(c)!AYENH<<K *YEN?.i(R)ECUR@DEGi patchkit
   ^3-L-CUR-L-(R)e(c)o:,N"M-a-oDEGYAD!C|^3"C,CURHYENi-`aAUDEGO+-o|'A-a-op^1-o|W-oUYENsDEGu
   !S:386BSD 0.5!" (c)I !S:386BSD Interim!" 'NNOTO^3oO`i|]!C

   386BSD NOTO Bill Jolitz
   -a-oS:@.~"t^2I!A|b.i(R)E'NCURw|^3NOTuCUR@|~-a-oCURAuoDEGQ 1/2 *!C
   .i,O *YEN?CURu"a (patchkit)
   CURe-oYENAeAo/+-oYENOCURHCUR-L-uI-aA!AS:UIuL^2S:A:^3|a|P.NnS:@CUR@"C,"AECURF!A
   "A"M(c)w'-L-"NCUR@YEN-:A{(R)E(c)E-a-o !S:^2bCURAE-a(c)(cleanup)!"
   "OADEGS:U Bill!C uM|O!AYENN(c)o Bill Jolitz
   (c)?uM"M(c)w"u(R)o/"a:^1i,Op^1-o-a-o>>{YENi!AYENB"S|^3(c)u
   1/2T<<u:YENXYEN 1/4"O-a-oYEN'-oa!A
   (c)OYENH,Op^1-o<<KNOTd-uM+-A{A_-aCUR|M 3/4-:!C

   CUR-L-CUR[S:UI<<K"M(c)w|bS:Y"I"S|^3 Bill
   -a-oCURa:<<uCURU!AAAy,Op^1-oCUR'uMA:~A:oCURUYENh!A
   ^3I<<aS:UI+-A:YENI David Greenman
   YENa>>E-aO"M(c)w-a-o|W|r!ACUR]'NNOTO!yFreeBSD!z!C
   |b,ssDEGYCURF.i(R)E-a-oCUR@"C,"IYENI-aI.N"-L-CURS:<<a!A'NP:}(c)l"M(c)wCURF^3I-a`i-a-oYENO/
   1/4D-!A
   .i,Op^1-oP:}(c)l^1eNOTICUR@CURA'Nn|"-u(R)E!ACUR@CURA'NAAU:+-oS:o^2M.!CURF!C
   S:U,o Walnut Creek CD-ROM DEGQ 1/2 *uo|ae CD-ROM ^3o
   1/4ECURlCUR-L-<<KCURW-oo-a-oCURH'NYENiYENHYENICURn,uA^2^3ae-a-oCURe|!"u+-o
   FreeBSD!C Walnut Creek CD-ROM CUR-L-YENuAU|"YENH CD-ROM "Ouo|ae
   FreeBSD -a-o.Q-ak!A|P(R)E'-L-"NCURFCUR@YENx 3/4-:
   3/4^1YENHCURIS:O:^3t-a-o-oo>>U-oo,o-a-oAW 1/4e!C |p-aGCUR-L-NOTO
   Walnut Creek CD-ROM
   'XYENGNOTO-aAA<<e-a-o<<HYENo^3oOeP:}(c)lAUNOTOS:^1YENthAqAquL>>D-a-op^1-o!A
   "-o>>o<<U:YENi-`a FreeBSD
   CUR-L-.||p|^1S:O:^3t-a-o|"-ao/"`iCURuCURe^3o 1/4E-a-o^3W 1/4O!C

   ^2A:CUR@+-iYENH CD-ROM (CURI-oo,o)uo|ae-a-o FreeBSD 1.0 NOTO|b
   1993 |~CURQCURGCURe!C ,O-a(c)YEN>>NOTODEGo(c)oYENN U.C. Berkeley
   YENH-oI+-aCURe|!uo|ae-a-o 4.3BSD-Lite
   (!S:Net/2!")YENHCURI^3\|h"O|U(c)o 386BSD
   (c)M|UYENN^3nAAeDEGo-a-:.|-a-o^3nAAe!C^1i(c)o^2A:CUR@|,uo|ae|O"YENAU-oa|"YEN\!A
   S:UICURS+-uuU(c)o 1994 |~ 5 CUReuo|aeCURFNOTU.i|"YEN\-a-o FreeBSD
   1.1!C

   uM|O|^1<<aCUR-L-CUR[!AYENtCUR@O.NYEN~-a-o. 1/4E|b Novell (c)M U.C.
   Berkeley Ao:(c)o Berkeley Net/2 -oI+-aCURS:-ak<<ss|a|`i-a-oP:D^3^
   1/2T(c)wCURS:<<aS:I|"!C U.C. Berkeley +-u"u:CURj^3!YEN-:-a-o Net/2
   -a-ou{|! 1/2X^3-L-NOTO!y<<I|u"O-a-o!zYENBNOTOA:Y(c)o Novell
   -a-oDEG]^2-L- -- "AE^1eCURWNOTO.i(R)ECUR-L-CUR[<<e+-q AT&T
   "u+-o-a-o!C Berkeley +-o"`i-a-oNOTO Novell ^1i(c)o 4.4BSD-Lite
   -a-o!y-NOT-oO:!z!A^3I<<a.i 4.4BSD-Lite ^2
   *(c)ouo|aeCURS:<<a!A<<KCUR-L-|ANOTO<<I|u|aeNOTDEG!C
   |O(c)O|^3^2{|^3 Net/2
   "IYENI-aI^3-L-^3Q+-j-P<<O/A:^3S:o'<<.s-a(c)YEN>>!A^3oYEN]NOTACURF
   FreeBSD!C (c)oNOTO!AS:UI^3Qn"D(c)o 1994 |~ 6
   CURe(c)^3<<eDEG+-CURi'^2S:GDEGo(c)o Net/2
   -a-o^2-L-<<~!C|b|^1<<e'-L-CURS:CURU!AYEN>>p^1-o^3QCUR^1^3\|b'AYENH<<eS:@^3I<<aCUR@|,uo|ae!ACUR]'NNOTO
   FreeBSD 1.1.5.1!C

   FreeBSD <<KP:}(c)lCURF^3o(c){|p!y<<.suo(c)u
   1/2u:CURl!z-a-oA}^1dCURuS:@ -- +-qYENth.s-a-oYENBCUR-L-S:^1
   3/4a-a-o 4.4BSD-Lite <<.s 3/4a|X!C ^3oO !S:Lite!"
   -a(c)YEN>>NOTOCUR-L-S:^1 3/4a-a-o!A|]NOTDEG Berkeley -a-o CSRG
   CURw,gS:RDEG-L-CURFCURjP:q|b<<O/YENssCUR@OYENiYENHP:}
   3/4-:DEGo|ae-a-o"t^2I(c)O>>Yn-a-ou{|! 1/2X
   (DEGo(c)oYCURz-ak<<ssCURW-a-on"D)!AYENB,O-a(c)YEN>>|b Intel
   YENYENx-a-o^2 3/4'ONOTO<<D+-`CUR-L-S:^1 3/4a-a-o!C -a 1/2"`i 1994
   |~ 11 CUReYEN>>p^1-oCUR~S:^1|"CURF^3oOA`a^2 3/4!A |P(R)E|b,O|~ 12
   CURe(c)^3YENH CD-ROM YENHCURI-oo,o-a-oS:I|!uo|aeCURF FreeBSD 2.0!C
   Ao:uM,OYEN-:-a(c)YEN>>|b.i(R)E|^3AIYEN^<<P^2EAW!A|yCUR'NOTO'I|^3.N,q-a-o|"YEN\!C
   AHCURS:(c)o 1995 |~ 6 CUReCURSuo|aeCURFS:o(R)e(c)o:|w,E!AS:o|n-a-o
   FreeBSD 2.0.5!C

   S:UI|b 1996 |~ 8 CUReuo|aeCURF FreeBSD 2.1.5!A|b ISP
   (c)MDEGO.~^1IAAeCURCUR<<D+-`NOTy|ae!C AH<<a!A 2.1-STABLE
   CURACURa:-a-oYENtCUR@O-a(c)YEN>>A^3^1B|OYENI!AYEN|'NNOTO|b 1997 |~
   2 CUReuo|ae FreeBSD 2.1.7.1 !A|P(R)ECUR]NOTO 2.1-STABLE
   CURACURa:-a-o^3I<<a-a(c)!CCURS:<<a|^1CURACURa:<<KP:iCURJ-ouAA@-aNOT-oA!A
   P:EP:E'-L-"N|wYENth(c)E-a-oYEN[+-j(c)M"a:YENLA:Y<<?u>>~
   *,E-a-o-ouAA@(RELENG_2_1_0)!C

   1996 |~ 11 CURe FreeBSD 2.2 +-qP:}uoYENDP:bCURACURa:
   (!S:-CURRENT!") YENX"O|"NOTDEG RELENG_2_2
   CURACURa:!CYEN|-a-o^2A:CUR@OS:^1 3/4a-a(c)(2.2.1)(c)o 1997 |~ 4
   CUReuo|ae!C 2.2 CURACURa:-a-o(c)uA:o-a(c)YEN>>|b 97
   |~(R)LNOTiCURS:P:!uo|ae-a-o!A"a:^3I<<a-a(c)NOTO|b 1998 |~ 11
   CUReuo|ae-a-o 2.2.8 -a(c)!C ^2A:CUR@OYEN?|!-a-o 3.0 -a(c)YEN>>|b
   1998 |~ 10 CUReuo|ae!AYENc,S:Y<<AAS:i 2.2 CURACURa:-a-o,"^1o!C

   1999/01/20 CURe|A<< *CURACURa:!A^3o^2-L-YENICURF 4.0-CURRENT
   YENHCURI 3.X-STABLE "aOCURACURa:!C 3.X-STABLE CURe+-!A3.1
   uo|ae(c)o 1999/02/15!A3.2 uo|ae(c)o1999/05/15!A3.3 uo|ae(c)o
   1999/09/16!A 3.4 uo|ae(c)o 1999/12/20!A3.5 uo|ae(c)o 2000/06/24
   !A+-uCURU"O'XCURN<<auoS:GCURFCUR@"C,-a-o *,EAE(^1i Kerberos
   |wYENth(c)ECURe+--a-o *YEN?)!A'NCURE-AA|U: 3.5.1 !A^3oNOTO 3.X
   CURACURa:^3I<<aCUR@Ouo|ae-a(c)YEN>>!C

   |b 2000/03/13 CURS|^3CURFCUR@O.s-a-oCURACURa:!A CUR]'NNOTO
   4.X-STABLE
   !C^3oOCURACURa:CURS:<<auoS:GCURF^3\|h-a-ouo|ae-a(c)YEN>>!J
   4.0-RELEASE |b 2000 |~ 3 CUReuo|ae!A |O^3I<<a-a-o 4.11-RELEASE
   <<h|b 2005 |~ 1 CUReuo|ae!C4-STABLE
   CURACURa:-a-oCURa:'(c).|<<uA:o"`i 2007/01/31
   !A|yYENDnuJAI|b(c)o|wYENthCURe+--a-o-o|NOT}!B-a:AICURI"a:YENLA:Y<<DEGYAD-a-o
   *,E!C

   'A<<YCURwCUR[-a-o 5.0-RELEASE |b 2003/01/19
   YEN?|!uo|ae!C^3oNOTO+-N-anP:}uoCURT|~-a-oAAq(R)pCURS:S:@!A|P(R)E
   CUR]P:}(c)lYEN[+-j|hAuCPU(SMPng)-a-oCURa:'(c)!Bkernel thread(KSE)
   -a-oCURa:'(c)!BAE(R) *"t^2I+-A:YENI UFS2 YENHCURICURa:'(c)
   snapshot uYEN!A "ACURa:'(c) UltraSPARC (c)M ia64
   YENYENx!BCURa:'(c)AAA-aTH!B32 bit -a-o PCMCIA uYEN!CCURS:<<a(c)o
   2003 |~ 6 CUReuo|aeCURF 5.1!C |O -CURRENT
   ^3oOuo(R)iYENDP:bCURACURa:-a-o^3I<<a 5.X -a(c)YEN>>NOTO|b 2004 |~
   2 CUReYEN?|!uo|ae-a-o 5.2.1-RELEASE!A|b 5.X "t|CP:iCURJ -STABLE
   (RELENG_5CURACURa:)CURS:<<a!A-CURRENT 'NA`a^2 3/4NOTDEG 6.X "t|C!C

   RELENG_5 CURACURa:(c)o 2004 |~ 8 CUReYEN?|!P:}P:]!ACURS:<<aNOTO
   5.3-RELEASE !AYEN|NOTO 5-STABLE
   CURACURa:-a-o^2A:CUR@Ouo|ae-a(c)YEN>>!C ^3I<<a-a-o 5.5-RELEASE
   NOTO|b 2006 |~ 5 CUReuo|ae-a-o!A|b|^1CURS:<<a RELENG_5
   CURACURa:CUR-L-|AA:~A:o!C

   RELENG_6 CURACURa:(c)o 2005 |~ 7 CUReP:}P:]!A|O 6.X
   CURACURa:-a-o^2A:CUR@O release(6.0-RELEASE) NOTO|b 2005 |~ 11
   CUReYENX-a-o!C ^3I.s-a-o 8.4-RELEASE NOTO|b 2006 |~ 5 CURe uo|ae!C
   .iuMAAo!ARELENG_6 CURACURa:AU+-N|^3<<aA:o-a-ouo|ae-a(c)!C

   RELENG_7 CURACURa:(c)o 2007 |~ 10 CUReP:}P:]!A^3I.s-a-o
   9.1-RELEASE NOTO|b 2006 |~ 5 CURe uo|ae!C RELENG_7
   CURACURa:AU+-N|^3<<aA:o-a-ouo|ae-a(c)!C

   YENO/<<e!A-ao/'A-a-oP:}uopueA:~A:o|b 8.X-CURRENT (trunk)
   CURACURa:CURCURP:i|ae!A|O 8.X -a-o CD-ROM
   (.iuM!ACUR]YENiYENHYENI-oo,oS:`i) snapshot -a(c)YEN>>YENiYENH|b
   FreeBSD snapshot server "u+-o!C

     --------------------------------------------------------------

  1.3.2. FreeBSD p^1-o-a-oYENO/ 1/4D-

   Contributed by Jordan Hubbard.

   FreeBSD p^1-o-a-oYENO/
   1/4D-|b(c)o'-L-"NYENiS:@YENo.NYENI^3~-a-o^3nAAe|OCUR-L--ath+-aYENo|o"i+-o/CURaa!C
   S:UICURS:CURCUR^3\|hCURH^1iu{|! 1/2X (YENHCURIpueYEN>>")
   ^3-L-|^3<<D+-`CURj-a-oS:eCURJ!A
   |]|^1!A.iuMCUR-L-CURP:.NDEG,-o,|^3CUR@"C,,e-a-:CURW-a-o,EAv!A|yS:UI"A"SYEN'-oaDEGi"M|an"D+-o"`i^3oAth,eS:U!C
   S:UI>>{NOTDEGS:UI-a-o-on!y"I(c)R(mission)!zNOTONOTDEGYENo|oCURH'-L-"Nu{|!
   1/2X!A CUR-L--oTHYENLIYEN'-oaYENI^3o"C,u{|! 1/2XDEGuCURDEG>>o!A
   |]NOTDEG^3o 1/4Eu{|! 1/2X+-N-`aDEG-:^3QS:o
   1/4s-ax|a"IYENI!A+-q|Ouo'S:"a:>>uE!C
   S:U>>{NOTDEG^3oNOTO|UYENN^3nAAe^3IDEGoYEN>>-a-o!A|P(R)ECUR]NOTOS:UI(c)OO
   3/4E-a-oCUR@OYENO/ 1/4D-!C

   S:UIu{|! 1/2X 3/4d-CURCUR!A|^3YCURzNOTOYENH GNU GPL (c)I-aI LGPL
   uoS:G-a-o"-o"C,u{|!
   1/2X+-a|^3CURO:^3\-a-o-athYEN["i!AAU|nYENuNOTO+-j"i(c)E-a-on"DP:}(c)nu{|!
   1/2X|OCUR-L-NOTOS:O-a-o!C YENN(c)o"IYENI GPL
   -a-o^3nAAe|bDEGO.~YENI^3~CURW.| 1/4WYEN[YCURz
   1/2AEAo/(c)E!A|]|^1!A|p-aGYENiYENH?i 3/4U:-a-o,U:!A
   S:UI.|CURn,u^3ssAAw"IYENI"iNOTU^1iS:o 1/4eAP-a-o BSD
   -a(c)AAv"OuoS:G^3nAAe!C

     --------------------------------------------------------------

  1.3.3. FreeBSD -a-oP:}uo 1/4O|!

   Contributed by Satoshi Asami.

   FreeBSD -a-oP:}uoNOTOCUR@O<<D+-`P:}(c)nYENB"a
   1/4u(c)E-a-o^1Lu{!A'N^1^3+-q DEG^A:m-aI|W^3ae
   (c)ONOTY"`i-a-o!ANOTOYENNYENthYEN@NOTE|"CURdCURW,U-a-oDEG^A:m-aIuo(R)iDEG_"O-a-o!C
   FreeBSD -a-oP:}uoDEGoA|NOT[-ocCUR^1^3\
   1/4AEYENH|Ep-a-oP:}uo-aI^3z^1L-oo>>U-oo,o"o|PCURuS:@!C
   S:UICUR],g+-`Ao:-a`uU"-o"C,^1iS:UI-a-opue.P?^3
   1/2`i-a-o.sP:}uo-aI(c)M.s-a-o^3D-.N!A "-o"C,|^3?^3
   1/2`iS:oP:iCUR@"BDEGN>>Pp^1-o-a-oCURHYENu>>Yn|b FreeBSD technical
   discussions P:l>> 1/4 1/2 * 3/4A ^3sA'S:UI!C FreeBSD announcements
   P:l>> 1/4 1/2 * 3/4A ^1i"-o"C,S:AE+-aeCURF,NS:UIP:i<<
   *-a-oCURHCUR]NOTONOTU.i|^3YENI-a-o!C

   uL 1/2
   *NOTO^3ae?WP:}uo-aI(c)I-aI<<E^3NOT|!-a-o^1IP:CUR|XS:@!A|hAA,N
   FreeBSD p^1-o(c)MYEN|-a-oP:}uo^1Lu{.|NOTOCUR-L-?u-a-o!J

   The SVN and CVS repository

           ^1LYENh 1/4AE|~"O FreeBSD -a-oCURCURYEN! source tree
           CUR@-a 1/2NOTOYENH CVS (Concurrent Versions System)
           "O-ouAA@-a-o!A
           YEN|NOTOO|UYENN^3nAAe!AYENiYENI"ODEGuNOTDEG-a(c)YEN>>+-+-"i!ACUR@,ES:^1
           FreeBSD CUR-o'N|^3-athCURF!C uM|O|b 2008 |~ 6 CUReDEG_!A
           FreeBSD -a(c)YEN>>+-+-"i"t^2IS:iYENI SVN(Subversion)!C
           ^3oCURA'<<DEGES:@S:UI>>{NOTDEGNOTO|^3YEN^2n!A|]NOTDEG CVS
           YENyCURN-a-oS:TH^3N"i!A 3/4EP source tree YENHCURI
           3/4uYENv-a(c)YEN>> 1/4AEP:qCUR-L-A_S:O:^3tAX+-i!C
           |]|^1!AYENDn-a-o repository YENO/<<eNOTO+-A:YENI SVN !A|O
           client -oY-a-oCURu"a^1^3NOTO CVSup!B csup
           ^3-L-NOTOYENHAA|!-a-o CVS
           NOT[-ocNOTDEGDEGoA|!ACUR'YENiYENHA:~A:oYEN?+-`^1BS:@ !X!X
           |^1CURD|] SVN repository |^3 backport |^ CVS
           CUR~YENiYENHA:~A:oAAy client -oYNOTU(R)e!C
           YENO/<<e!A'NYENu|^3CURCURYEN! source tree NOTO+-A: SVN
           -a(c)YEN>>+-+-"iCURe|!!C |OCURaaYENo!B-ooP:!B Ports ^3o"C,
           repository CUR'<<uA:o"IYENI CVS -a(c)YEN>>+-+-"iCURe|!!C
           |OYENDn-a-o CVS repository NOTO|`i(c)oNOTu:DEGeYEN[|{
           Santa Clara -a-oNOTYYENx 3/4-: 3/4^1CURW!A uM<<a|A mirror
           "`iYEN@NOTECURW"a:YENL-a-o^3\|h 3/4-: 3/4^1CURW!C SVN tree
           CUR-o|^3"aOYENDCURACURa:!G -CURRENT YENHCURI -STABLE
           !A^3o"C,^3-L-YENi>>'AP 1/2AE>>s"`i|UCURv 3/4-: 3/4^1CURW!C
           ,O+-! 1/2D-DEGN 3/4\ S:o.sS:A-a-o source tree CUR@,`!C

   The committers list

           (c)O? *-a-o committers <<u:-a-oNOTO^1i CVS tree |^3 write
           AAv!A "A"ICUR-L-|P+-AAAv^3!CURA!A|O|^3CUR-L-|PAAvYENi *S:i
           FreeBSD source!C (!S:committer!" ^3ouu:. 1/2|U cvs(1)
           CURCUR-a-o commit <<u:YENO!A,O<<u:YENONOTOYENI"OS:a.s-a-o
           *S:i'-L-YENaeu^1 CVS repository!C) |O'-L-YENae *S:iu^1
           committer IAENOTd-a-o^3I|nCURe|!!A'NNOTOYENI send-pr(1)
           <<u:YENO!C Y'-L-YENae PR -a-oNOTyu{"t^2ICURW|^3
           3/4AP:e^2{P:H-a-o,U:!A
           CUR]YENiYENHS:iYENI+-H<<HCURe|!!A+-H<<H"`i FreeBSD
           committer's P:l>> 1/4 1/2 * 3/4A S:YYENi!C

   The FreeBSD core team

           |p-aGS:a FreeBSD NOTY|"NOTOCUR@(R)aCUR 1/2YENq-a-o,U:!A
           FreeBSD core team 'NNOTU.i(c)o!y,^3"AE.|(board of
           directors)!z!C core team -a-oYENDnA 3/4^3d|b(c)o
           1/2T<<O|^1p^1-o|^3"}|n-a-oNOT[-oc!AYENH'AuUYEN?
           1/2T-a-oCURe|Vuo(R)i!C |^1YEN~!AAU: 1/2D-
           1/4o:|aaYENBt^3d-a-o^3nAAeP:}uo-aIYEN[CURJ committers
           |ae|C!A YENH|bYCURz|"uA-:YENh(R)E+-oYENH,EYENR.s|aa!C
           YENO/<<e-a-o core team NOTO|b 2008 |~ 7 CURe committers
           O?iCURHCURCUR?iYENX"O-a-o!A"C"a|~.|A|?`iCUR@|,?iA|!C

           |^3"C, core team |"uAUt^3dNOTY"C,-S(c)w 1/2d^3o!A
           CUR]'NNOTO>>!YENLIYEN^2P:.-oEP:q
           1/2T<<OCUR@"C,CURl"t^2I-a-oA(c)w!B(R)A:-`a!C Ao:(c)o
           FreeBSD P:}uo-aIIYENHCURI|U|U^3dYENo 1/2d^3o!A 1/2D-DEGN
           3/4\ DEG^A:m-aI|W^3ae !C

             -a`: core team CURj^3!CURA|"uYEN[CURJ FreeBSD
             P:}uo^3-L-NOTOS:OCURu(c)E 1/2e|OCURw!A "AYEN
             1/4+-qYEN>>p^1-oCURCURAo+-oYENo|oA~^1S!A(c)OYENHCUR-L-,OS:a
             !S:commitment!" >>~,NNOTDEG !S:guaranteed support!"
             CUR~^1i!C
             e<<e+-(c)OA?-a-o!y,^3"AE.|!zYENi-`aNOTOCUR-L-<<e.i-a-oAth+-A!A(c)I^3\S:UIA^3,O>>!!G
             YENLINOTOCUR@,s|UA:@(c)n+-o`iYEN>>-a-oAu'`iYENINOT!!BOCURH"a:YENL>>aDEG`i|"'N!A
             |O?i 3/4U:S:eCURJ FreeBSD P:}uo-a-o
             1/4o:|aa|^3NOTDEG-aICUR~^1i!I

   "a:YENL-a-oDEG^A:m-aI

           ^3I<<aCUR@AI!A|y^3oAIu'<<D^3ICUR-L-<<n-a-o!A
           ^3ICURj-a-oP:}uo-aI^1IP:CUR'NNOTO<<uA:oNOTDEGS:UI'-L-"N|^oXYENHCURI?u>>~
           *YEN?-a-o"IYENI-aI|UCURv!C >>P FreeBSD
           <<D(R)O:CURssP:}uo-aICURNOTDEGE-a-oYENDnCURe|!!A<<KNOTO^3z^1Lq
           3/4\ FreeBSD technical discussions P:l>> 1/4 1/2 * 3/4A
           "OP:i|ae. 3/4^3q!A^3oCURe+-YENiDEGN|O!A 1/2D-DEGN 3/4\
           -ath?y C YENHAA,N|U|!CUR-L-|P-a-o FreeBSD P:l>> 1/4 1/2 *
           3/4A(mailing lists)!C

           FreeBSD DEG^A:m-aI|W^3ae
           NOTU.i-ao/YENBCUR-L-A_|"-ao/CURCUR!A
           YENun|^3DEG^A:m'N.|^3Q|CCURJ"a:CURCUR!A nCUR-L-nYENssS:Y|O
           1/4{DEG^A:m FreeBSD CUR@"C,|^oX(c)O!H

           uM|O!A'-L-"N`i(c)l
           1/2X"A<<DNOTDEG^3oOp^1-oDEGuDEG^A:m-a-oDEGssCUR@CURe|!!F
           AU>>YnCURj(R)aS:eCURJ-a-oS:^1 3/4aCURuS:@|C-ai!B>>!(c)u!A
           1/2D-DEGN 3/4\ FreeBSD (c)x-oo!C

   A^2^3ae-a-o>>!!AS:UI-a-oP:}uo
   1/4O|!'N^1^3NOTOCUR@^2O"S|^3(c)eS:o-a-o|PCURssP:e!C
   ^3o-oO/P:DEGCURCURP:}uo 1/4O|!NOTOYENH u^1"IYENI-aICURe<<K
   NOTDEGYEND!A
   |P(R)EAAyYENLI-`a<<U:(R)e(c)o:|a|@|P-ouAA@^3nAAe!A|OCUR-L-.|S:a
   1/4c,|b-a-oDEG^A:m-aI+-AEDEG-L-|bYEN~!I S:UI-a-oYENO/
   1/4D-NOTO'-L-"NS:t|^3CURjP:qCUR@P(c)E-a-o
   A^3YENI^3nAAe(ports/packages)
   !AYENH<<KAAy"IYENI-aI>>'AP|w,E!B"IYENI-a-oS:@.~"t^2I !X!X
   |O^3oP:}uo 1/4O|!NOTU.i^2AA|X|^1CUR@YENO/ 1/4D-!C

   S:UI^1i(c)o"-o"C,.QnYEN[CURJ FreeBSD P:}uo-aI-a-o'A<<YNOTO!G 
   1/2D-<<O<<u|p|P<<eCURHCUR@ 1/4E-a-oS:eCURJ!AYENH
   1/2T<<OA:~A:o|"YEN\!I

     --------------------------------------------------------------

  1.3.4. ^3I.s-a-o FreeBSD uo|ae-a(c)YEN>>

   FreeBSD NOTOS:KP:O"IYENIYENB+-a|^3S:^1 3/4a`i(c)lu{|! 1/2X-a-oYENH
   4.4BSD-Lite NOTDEGDEGoA|-a-o"t^2I!AYENiYENH|b Intel i386(TM),
   i486(TM), Pentium(R), Pentium Pro, Celeron(R), Pentium II,
   Pentium III, Pentium 4 ((c)I-aINOTU(R)e<<NOT,^1), Xeon(TM), DEC
   Alpha (c)M Sun UltraSPARC
   NOTDEGDEGoA|-a-o^1q,-L-CURWDEGo|ae-a-oS:@.~"t^2I!C
   YEN|YENDnYENHYEN[|{CURj 3/4C,CURU-o,S:JS:QCURA(R)O -a-o CSRG
   NOTa"sCURp^2O-a-o^3nAAeNOTDEGDEGoA|!A"AYEN[CURJCURF
   NetBSD!BOpenBSD!B386BSD
   YENHCURI|UYENN^3nAAeDEGo-a-:.|-a-oCUR@"C,-aF|e!C

   |U+-q 1994 |~YEN 1/2!AS:UIuoS:GCURF FreeBSD 2.0
   CURS:<<a!A"t^2I-a-oDEGo|ae(R)A:^2v!B
   YEN\-`a!BA(c)w(c)E^3-L-|^3CURFYENOCURH-a`YENO/-a-o'-L-CURE!C
   ^3ICURj-a-oS:iAAU:'NNOTOS:UI+-NDEGO 3/4D-AAe>>PAE(R) *"t^2I-a-o
   cache  3/4-:"iu^2|X|bCUR@DEG_!C
   ^3oCUR-L-YENu"I+-o"t^2I-a-o-ai^2{AAU:+-oS:o|n, "AYENB"I+-o FreeBSD
   "t^2I^3ICURO:-a-oDEGO 3/4D-AAe>>Y"D'iCURO:"`i 5 MB!C
   "a:YEN|-a-oS:iP:iYEN]NOTAS:^1 3/4a-a-o NIS cilent and server
   YEN\-`aCURa:'(c)!A CURa:'(c) transaction TCP!BPPP  1/4.+-u^3s
   1/2u!B 3/4a|X-a-o DHCP CURa:'(c)!B SCSI CURl"t^2I-a-oS:iP:i!BISDN
   -a-oCURa:'(c)!AATM!BFDDI YENHCURICURACURO-oo,o (Ethernet!BYEN]NOTA
   100 Mbit (c)M Gigabit) -a-oCURa:'(c)!A'-L-CURECURF^3I.s-a-o
   Adaptec +-+-"iYENdAAXDEGEu{|!-a-oS:iu 1/2!AYENHCURI
   1/4AEYENHCURdp-a-o bug  *YEN?!C

   DEG-L-CURF^3IDEGoYEN>>-a-o"t^2I^3nAAe!AFreeBSD AU'-L-"NCURF
   1/4s"u:AAw-ai-a-o(R)MYENo^3nAAe-oTH^2z 3/4-:"i!G Ports
   Collection!C "`iYEN>>(R)NYENI|L(R)E!ACURw|^3P:W^1L 24,000 O
   ports!A^3o 1/2dAYEN^2[>>\+-q http(WWW) |o/-aA
   3/4^1"`i^1CA,!Bu{|!>>y"YEN!B 1/2s?e
   3/4^1YENHCURI+-z-`a.Q"`i-a-o'XYENG(c)O|^3-a-o-aF|e!C S:^1 3/4a-a-o
   Ports Collection >>YnNOTu 500 MB -a-ouw-oD--aAAP:!!ADEG-L-CURF
   port DEGoYEN>>NOT[-ocAE(R) *YEN~!A^3-L-YENuAx|s>>P,O port
   ^3nAAe-a-o`i(c)l 1/2X|^3!yP:.nAAU:S:o!z-a-o^3!YEN-:!C
   |p|^1CUR@"O!AS:UIYENiYENHS:o(R)e(c)o:S:o.s^3o"C,
   ports!ACUR]CURjP:q-a-o'iCURO:|pAA-a-o 1.0 -a(c) Ports Collection
   ^1i(c)ouw-oD--aAAP:!-a-o>>Y"D!C n|w,ECUR@O port
   -a-o,U:!AYENu>>YnP:iCURJ,O port -a-oYENO/?y!A?eCURJ make
   install!A^3o 1/4ECURl"t^2I'N.|ADEGS:A,E|nCURF!C +-zn
   1/2sA:P:-a-o"COu{|!-a-oS:^1 3/4a`i(c)lu{|!!A ^3-L-YENi+-q FTP (c)I
   CD-ROM
   CURCURAo+-o!A(c)OYENH+-zYENu>>Y.C,^3AE"NOTDEG-:-a-ouw-oD--aAAP:!"O
   1/2sA:P:S:An-a-o port ^3nAAe!C 'XYENG"CCUR@O port
   ^3-L-|^3CURw"AEYENy 1/2sA:P:|n-a-o !S:package!"YENHCURe<<K|w,E!A
   |p-aGCUR-L-.Q+-q 1/2sA:P: port -a-oCURH!AYENunYENIOA^2^3ae<<u:YENO
   (pkg_add)'NYENiYENH|w,E!C |^3Ao: packages (c)M ports
   -a-o^2O,`!AYENiYENHDEGN 3/4\ uU 4 ^3^1!C

   FreeBSD YEND 3/4-:-a-o /usr/share/doc
   YENO/?yCURUS:a:"`i^3\|h|^3YENI-a-oCURaaYENo!A
   "OADEGS:U+-z|w,E!B"IYENI FreeBSD!C
   CUR]YENiYENH"IYENICURU+--a-o-ooS:}!AYENHAsA:y 3/4^1"OA 1/2
   3/4\YEN>> 3/4-:CURW|w,E-a-oCURaYENU!J

   FreeBSD "IYENICURaYENU

           /usr/share/doc/handbook/index.html

   FreeBSD +-`"-L-DEGYu-aP:DEG

           /usr/share/doc/faq/index.html

   |^1YEN~!AYENi|bCURU|C-ooS:}S:a:"`i^3I.s-a(c)
   (CUR]NOTOS:o.s^3IAWAc-a-o-a(c)YEN>>)!Ghttp://www.FreeBSD.org/!C

     --------------------------------------------------------------

                          ^3^1 2. |w,E FreeBSD

   Restructured, reorganized, and parts rewritten by Jim Mock. The
   sysinstall walkthrough, screenshots, and general copy by Randy
   Pratt.

2.1. .S:z

   FreeBSD
   '-L-"NCUR@OA^2^3ae|nYENI-a-oCURaa|rCURP:+-|w,Eu{|!!AYENsDEGu
   sysinstall!C ^3oNOTO FreeBSD ^1w^3]"IYENI-a-o|w,Eu{|! !C"oCURO
   1/4tDEGOY|^3.NA:@-a-o,U:!ACUR]YENiYENHS:iYENI|UCURv-a-o|w,Eu{|!!C
   YEN>>^3^1+-N>>!(c)u|p|o"IYENI sysinstall "O|w,E FreeBSD!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!J

     * |p|o>>sS:@ FreeBSD |w,ECURu

     * FreeBSD ^1iuw-oD--a-o"IYENICURIDEGt,m!C

     * |p|o+-ODEGE sysinstall u{|!!C

     * |bDEGo|ae sysinstall
       (R)E.|DEGY-a-oNOTUAo:DEGYAD|^3th"C,!B^3o"C,DEGYAD-a-o.N<<a:NOTDEG|o!BYENHCURI,O|p|o|^u-a!C

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!J

     * 3/4\AA-an|w,E-a-o FreeBSD
       -a(c)YEN>>(c)O-athCURS:uwAAeCURa:'(c)-ai!A YENH
       1/2T(c)w+-z-a-ouwAAe|^3"S|^3^3QCURa:'(c)!C

     -a`: CUR@-e"O>>!!A|^1|w,E>>!(c)uNOTODEGw^1i i386 (NOTU(R)e-a-o
     PC  3/4-:-oO/) NOT[-oc-a-o^1q,-L-!C
     |p-aG|^3"a:YENLNOT[-oc(CURn|p
     Alpha)-a-o|w,E>>!(c)u!AS:UI.|CUR@"O:|CYENX!C
     Ao:uMYEN>>CURaaYENo.|+-`+-`S:o.s!A|y|^3YENi-`a>>P+-z|w,E-a(c)YEN>>CURW(c)O-ath-a-o>>!(c)uCURaaYENo|^3"C,^3\YENXCURJ!C
     |b|^1!AS:UI<<O/A:^3+-zS:aYEN>>>>!(c)uCURaa^3^1.iS:@CUR@-e-a-o|w,EDEGN|O`i<<h'N|n!C

     --------------------------------------------------------------

2.2. uwAAe>>Y"D

  2.2.1. ^3IS:C>>Y"D

   |w,E FreeBSD -a-ouwAAeCURe+-^3IS:C>>Y"D!A"I|U FreeBSD
   -a(c)YEN>>>>PuwAAeNOT[-oc(R)tS:O|O|^3(c)OCUR-L-|P!C

   Ao:(c)o|w,E(c)O>>Y-a-o^3IS:C>>Y"D!AYENi|b FreeBSD -oo-,-a-o
   Release Information S:a:NOTUAo:-a-o Installation Notes >>!(c)u!C
   +-uCURU"O-a-o^3^1,`.||^3NOTUAo:>>!(c)u 3/4a^2z!C (R)U 3/4U|w,E
   FreeBSD -a-oCURe|!CUR-L-|P!AYENi-`a.|>>Yn^3n-oD- 3/4-:(c)IYENu-oD-
   3/4-:!A (c)INOTY"C,+-!-ap<<hNOTOn-oo,oYENd!C ^3o"C,^3!YEN-:.||b uU
   2.3.7 ,` |^3CURP:^2D-!C

     --------------------------------------------------------------

    2.2.1.1. FreeBSD/i386 CURI FreeBSD/pc98 NOT[-oc

   FreeBSD/i386 CURI FreeBSD/pc98 "a-oO/-a(c)YEN>>S:!P:. 486
   (c)IS:o|n-a-o^3B^2z 3/4^1!A YENHCURI|U:CURO: 24 MB -a-o
   RAM!B|U:CURO: 150 MB -a-ouw-oD--aAAP:!!A
   CUR~-`aP:i|ae^3ICURp|w,E!C

     -a`: ^1i|NAAuwAAe|O"YEN!A|bCURj^3!YEN-:+-!-ap,ES:o|h-a-o RAM
     >>PS:oCURj-a-ouw-oD--aAAP:!!A.|CURn"IYENIS:oS:O:-a-o CPU
     S:o|^3YENI!C

     --------------------------------------------------------------

    2.2.1.2. FreeBSD/alpha NOT[-oc

   Yn,E FreeBSD/alpha!A<<h>>Y 1/2T>>{,O 3/4-:<<NOTNOTOS:_|^3CURa:'(c)
   ( 1/2D-DEGN 3/4\ uU 2.2.2 ,`) YENBYEN^2P:. 3/4aAuuw-oD-NOTOu^1
   FreeBSD "IYENI!C YENO/<<euL-ak|P(R)E>>P"a:YENLS:@.~"t^2I|@|s!C
   ^3ouw-oD-P:.+-u"`i SRM P:'AAe|^3CURa:'(c)-a-o SCSI controller
   CURW!A(c)I-aI IDE uw-oD- (,O 3/4-:<<NOT-a-o SRM
   |^3CURa:'(c)YENi+-q IDE uw-oD-P:} 3/4-:)!C

   |^1YEN~!AAU>>Y,O 3/4-:<<NOT-a-o SRM console firmware!C |^3"C,
   3/4-:<<NOTYENiYENH?i 3/4U: AlphaBIOS (or ARC) firmware (c)I SRM
   "OYENI!C Y"S|^3-a-o,U:!A<<h>>Y+-quwAAe
   1/4tDEGO-a-o-oo-,YENhCURU,u:.s-a-oP:'AAe!C

     -a`: +-q FreeBSD 7.0 'NCUR-L-|ACURa:'(c) Alpha!C FreeBSD 6.X
     "t|C<<hNOTO|^1NOT[-oc-a-o^3I<<aCURa:'(c) !C

     --------------------------------------------------------------

    2.2.1.3. FreeBSD/amd64 NOT[-oc

   |^3"a-oO/ CPU -`aP:] FreeBSD/amd64!C ^2A:CUR@-oO/NOTOYEN]NOTA
   AMD Athlon(TM)64 !BAMD Athlon64-FX!BAMD Opteron(TM) (c)IS:o|n-a-o
   CPU!C

   ^2A:CURG-oO/<<hNOTO Intel(R) EM64T NOT[-oc-a-o
   CPU!A^3o"C,CUR]YENiYENHYENI FreeBSD/amd64!C ^3o"C, CPU
   YEN]NOTACURF Intel Core(TM) 2 Duo !BQuad!BExtreme "t|CYENHCURI
   Intel Xeon 3000!B5000!B7000 NOTUAo:"t|C-a-o CPU!C

   YYEND 3/4-:-aO'^1CURu^2ONOTDEG nVidia nForce3 Pro-150!A<<h
   YEN^2P:.  1/2O 3/4a BIOS ^3](c)w!A+-N IO APIC DEG+-YENICUR~|ae!C
   YS:a:CUR-L-"`i^3o?iP:u!A"-oYENi-`a'NNOTOS:a: ACPI DEG+-YENI!C
   |]NOTDEG Pro-150 '^1CURu^2O|^3O
   bug!AYENO/<<eS:UI(c)|uLS:a:"`i^3o,NCURS:^1D!C

     --------------------------------------------------------------

    2.2.1.4. FreeBSD/sparc64 NOT[-oc

   Yn,E FreeBSD/sparc64!A<<h>>Y 1/2T>>{,O
   3/4-:<<NOTNOTOS:_|^3CURa:'(c) ( 1/2D-DEGN 3/4\ uU 2.2.2 ,`)!C

   FreeBSD/sparc64 YEN^2P:."IYENI 3/4aAuuw-oD-!A
   |]NOTDEGuL-ak|P(R)E>>P"a:YENLS:@.~"t^2I|@|s!C

     --------------------------------------------------------------

  2.2.2. |^3CURa:'(c)-a-ouwAAe

   FreeBSD "C|, release (R)E^3-L-.||^3-athCURW FreeBSD Hardware Notes
   "O>>!(c)u|^3CURa:'(c)-a-ouwAAe|C-ai!C
   ^3q+-`^3oYEN-:CURaaYENoYENi|bYENu-oD-(c)I FTP -a-o^3ICURW
   1/4hYENO/?yS:a:"`i!ACUR]'NNOTO|WNOTDEG HARDWARE.TXT -a-oAE(R) *!C
   |^1YEN~!A|b sysinstall -a-o documentation
   ?iP:uCUR-oCUR]YENiYENHNOTY"`i!C "C|, FreeBSD release
   (R)E,O|C-ai.|"I|UCUR-L-|PNOT[-oc!A |O|CYENXNOTUAo:CURw-a
   3/4|^3CURa:'(c)-a-ouwAAe!C |b FreeBSD -oo-,-a-o Release
   Information P:YENiYENHS:a:"`i|UCUR-L-|P release
   -a(c)YEN>>>>P|UNOT[-ocCURW-a-ouwAAeCURa:'(c)|C-ai!C

     --------------------------------------------------------------

2.3. |w,E<<e-a-o.C,^3AECURuS:@

  2.3.1. |CYENX+-z^1q,-L--a-ouwAAe^2M^3ae

   |b|w,E FreeBSD
   CURS:<<e!A+-zA^3,O,OuU+-N+-z^1q,-L-CURCUR-a-ouwAAe^2M^3ae|CYENX"O!C
   FreeBSD |w,Eu{|!.|+-N^3o"C,uwAAe(uw-oD-!B-oo,oYENd!BYENu-oD-
   3/4-:uYENuYEN) YENH<<NOT,^1CURI>>s^3y 1/4tDEGO|CYENX"O!C FreeBSD
   CUR].|^1A,ONOTDEG^3o"C,uwAAeS:a:YENX^3I 3/4A.i-a-o IRQ CURI IO
   port -a-o^3](c)w!C |yNOTO|]NOTDEG PC -a-ouwAAe-oO/Ath^1e|bCURO^1L
   1/2AEAo/!A^3oO"BAEJCUR-L-CUR@(c)w<<OAOu'^1i|"YEN\!C
   ^3o(R)E!A+-z'NYENi-`a>>YnCURaDEGES:oS:i|^3DEGYAD-a-o^3](c)wEu!C

   |p-aG+-zCURw,ECURF"a:YEN|-a-oS:@.~"t^2I!A|p!G Windows (c)I
   Linux!A"-o>>oYENiYENyYENN^3o"C,"t^2I(c)O'-L-"N-a-oCURu"a!A
   "ONOTdNOTY^3o"C,uwAAe^3](c)wENOTO<<c,>>o^3](c)w-a-o!C
   Y-u-a-o"S?`i-ak 1/2T(c)wNOTY"C,YENdYENICURDEG>>o^3](c)wE!A
   "-o>>oYENiYENHAENOTdNOTYNOTYYENdCURW+-(c)O
   1/4D-YENU:-a-o-aF|e!A>>!CUR-L-(c)wYEN|-a-o^3](c)wCURw|^3
   1/4D-YENU:|bYENdCURW!C +-`YENI-a-o IRQ ,^1 1/2XNOTDEG 3!B5
   YENHCURI 7!F|O IO DEGd--a-oE^3q+-`YENH 16 P:i|`i-aiYENU:!A "O|p
   0x330!C

   <<O/A:^3+-z|b|w,E FreeBSD
   CURS:<<e!AS:a^3o"C,,e(R)AE|C|L(c)IS:U?yCURU"ODEGu|"-ai(R)ae!A
   CUR]^3\.|,u|^3YENI^3a!A"O|p!G

   -ai(R)ae 2-1. uwAAe^2M^3ae(A|"O)

      uwAAe|W-oU    IRQ   IO                   ^3AEuu                 
                        port(s) 
   ^2A:CUR@Au IDE               40 GB!ASeagate                        
   uw-oD-           N/A N/A     >>s^3y!A+-u|b^2A:CUR@+-o/ IDE +-AE    
                                1/2u-a-o master                       
   CDROM            N/A N/A     +-u|b^2A:CUR@+-o/ IDE +-AE 1/2u-a-o   
                                slave                                 
   ^2A:CURGAuuw-oD- N/A N/A     20 GB!AIBM >>s^3y!A+-u|b^2A:CURG+-o/  
                                IDE +-AE 1/2u-a-o master              
   ^2A:CUR@O IDE    14  0x1f0                                         
   controller       
   -oo,oYENd        N/A N/A     Intel 10/100                          
   1/4AE 3/4U 3/4-: N/A N/A     3Com(R) 56K faxmodem!A+-u|b COM1      
   !K                                                                 

   uwAAe^2M^3aeS:^1|"CURS:<<a!A'N>>YDEGw^1iS:A(c)On,E-a-o FreeBSD
   -a(c)YEN>>CURS:uwAAe>>Y"D!A "OAENOTdNOTOS:_|^3CURa:'(c)!C

     --------------------------------------------------------------

  2.3.2. ^3AEYEN-:+-z-a-o,e(R)AE

   |p-aGn,E-a-o^1q,-L-CURW+-|s|^3<<n,e(R)AE!A"-o>>o|b|w,E FreeBSD
   <<e!A  1/2D-
   1/2T(c)w+-zCURw,g+-N^3o"C,,e(R)AE^3AEYEN-:CURF!A"AYENBYENy'u,O^1L^3o"C,^3AEYEN-:AENOTOS:_"S|^3DEGYAD!C
   FreeBSD |w,Eu{|!|bn
   1/4gCURJYENo|o,e(R)AE"`i+-z-a-ouw-oD-<<e!A^3-L-.|YENy'-L-?o+-z
   1/2T>>{!A CUR@YEN^1+-z 1/2T(c)wn
   1/4gCURJ!A"-o>>oCURS:<<a'N|ACUR]"S|^3CURI(R)NOT-a-o 3/4-:.|AAo!C

     --------------------------------------------------------------

  2.3.3. "M(c)wn+-N FreeBSD |w,E"`ith,I

   |p-aG+-z.QAAy FreeBSD -a 1/2+-u"IYENI 3/4aAuuw-oD-!A"-o>>o 1/2D--a
   1/2+-u,o"`iCURUCUR@,`!C

   uM|O!A|p-aG+-z.Qn FreeBSD ,oNOTJ|^3-a-o"t^2I"A|s!A"-o>>o!A
   +-zYEN^2P:.^1iuw-oD--a-o,e(R)AECURAS:GCURe|!|^3^2`CURJ-a-oCURF,N!AYENHCURI"a:(c)O^3y|"-a-o
   1/4vAAT!C

     --------------------------------------------------------------

    2.3.3.1. FreeBSD/i386 NOT[-oc-a-ouw-oD-DEGt,m 1/4O|!

   PC
   CURW-a-ouw-oD-YENiYENH^3Q^2OCURANOTDEG^3\|hCURA'^2DEGI(chunk)!C^3o"C,DEGIDEG`iYENsDEGu
   CURA^3IDEGI(Partitions)!C YENN(c)o FreeBSD CUR-o^3!CUR]|^3
   partition!A|W-oUYENi-`a<<U:(R)e(c)o:^3y|"^2V^2c!A |]|^1^3q+-`|b
   FreeBSD ^3oAa:.|-oU(c)I^3o"C,-oI-oD-CURA'^2DEGINOTDEG disk slices
   (c)IA^2-oU slices!C A|"O"O>>!!AFreeBSD -a-o fdisk
   -a-o^1iP:HNOTODEGw^1i PC uw-oD--a-o slice |O<<D partition!C
   |]NOTDEG PC YEN>>"YENyCURN^3]p!A"COuw-oD-^3I|hYENiYENH|^3 4
   OCURA^3IDEGI!A|O^3o"C,CURA^3IYENsDEGu YENDnCURA^3IDEGI(Primary
   Partitions)!C
   NOTDEGCURFNOTd--}^3oO"i!AYENH<<K-`a"IYENIS:o|h-a-oCURA^3IDEGI!A'N|^3CURF.s-a-oCURA^3IDEGIAth<<NOT!AYENsS:@!G
   (c)u|uCURA^3IDEGI(Extended Partition)!C
   "COuw-oD-'NYENu-`a|^3CUR@O(c)u|uCURA^3IDEGI!C
   uM|O!A|b(c)u|uCURA^3IDEGI,I+-YENiYENH<<O/YENss^3\|hO-S(R)iCURA^3IDEGI!AYENsS:@
   AATH?eCURA^3IDEGI(Logical Partitions)!C

   "C-oO/CURA^3IDEGI^3-L-|^3"a: CURA^3IDEGIYENN,^1(Partition ID)
   YENIYENHDEGIS:O"C-oO/CURA^3IDEGI-a-o,e(R)AEAth<<NOT!C |O FreeBSD
   CURA^3IDEGIYENN,^1NOTO 165!C

   CUR@-e"OA?!A"C-oO/S:@.~"t^2I^3-L-.||^3|UCURv?W-S-a-oCURe|!"ODEGIS:OCURA^3IDEGI!C
   A|"O!G DOS CURI"a:CURS:<<a-a-oS:@.~"t^2I!ACURn|p Windows
   .|CURADEGtu^1"COYENDnCURA^3IDEGICURIAATH?eCURA^3IDEGI 1 O
   -oI-oD-YENN,^1(drive letter)!A+-q C: P:}(c)l!C

   FreeBSD YEN^2P:.|w,E|bYENDnCURA^3IDEGI!C FreeBSD
   YENiYENH|b^3oOCURA^3IDEGICURW+-|s(c)n,e(R)AE(c)INOTO+-z<<O/YENss-a-oYENo|oAE(R)
   *!C
   uM|O!A|p-aG+-z|^3<<U:|hAuuw-oD-!ACUR]YENiYENH|b^3o"C,((c)I^3!YEN-:)uw-oD-<<O/YENss
   FreeBSD CURA^3IDEGI!C |w,E FreeBSD -a-o(R)EO!AYEN^2P:.|U:CURO:n|^3
   1 OCURA^3IDEGIu^1 FreeBSD "IYENI!A
   ^3oOCURA^3IDEGIYENiYENHNOTO(c)|YEN
   1/4"IYENI-a-oCURA^3IDEGI!A(c)INOTO^2{|s-a-oCURA^3IDEGI
   (|yCURW+--a-o,e(R)AECUR-L-YEN'-oaA:~A:o"IYENI)!C

   |p-aGCURw,gYENIS:^1CURF-oI-oD-CURW(c)O|^3-a-oCURA^3IDEGI!A
   "-o>>o+-zYEN^2P:."IYENI"a:YENLS:@.~"t^2I(c)O'-L-"N-a-oCURu"a
   (^1^3NOTO DOS or Windows CURW-a-o fdisk)
   "OA:EYENXCUR@OCURA^3IDEGIu^1 FreeBSD YENI!C

   |p-aG|^3|h 3/4l-a-oCURA^3IDEGI!ACUR]YENiYENH"IYENIYEN|!C
   |y"IYENI<<e!A+-zYENi-`a>>YnYENy 3/4a^2zCUR@CURU^3o"C,CURA^3IDEGI!C

   FreeBSD^3ICURp|w,E>>YnNOTu 100 MB
   -a-o-aAAP:!!A|yNOTO^3oYENuNOTO!y^3ICURp|w,E!z!A
   'XYENG"S^3NCURU|hCURO:-aAAP:!"O|s(c)n+-z|UCURv-a-oAE(R) *!C
   ,u^2z.Q-a-o(CUR-L-S:t^1IS:ICURP:+-)^3ICURp|w,ENOTONOTu
   250 MB!A(c)I-aINOTO 350 MB YEN-aYENk(YEN]S:t^1IS:ICURP:+-)!C
   AU>>Yn|w,E"a:YENL-a-o(R)MYENo^3nAAe!A"-o>>o+-N>>YnS:o|h-a-ouw-oD--aAAP:!!C

   +-zYENiYENH"IYENIDEGO.~^3nAAe^1^3NOTO PartitionMagic(R)
   (c)IS:KP:O|UYENNCURu"a^1^3NOTO GParted "O<<.s 1/2O
   3/4aCURA^3IDEGI-aAAP:!!A "Ou^1 FreeBSD YENI-a-o-aAAP:!!CFreeBSD
   YENu-oD-!BFTP CURW+--a-o tools YENO/?yYEN]S:t"aOS:KP:O-a-oCURu"a!A
   CUR]YENiYENH^1F|"^3oOCURuS:@!AYENsS:@!GFIPS CURI PResizer!C
   ^3o"C,CURu"a-a-o>>!(c)uCURaaYENoYENiYENH|b|POYENO/?yCUR-oS:a:"`i!C
   FIPS!B PResizer (c)M PartitionMagic YENiYENH<<.s 1/2O 3/4a|b
   MS-DOS "`i Windows ME (c)O"IYENI-a-o FAT16 CURI FAT32
   CURA^3IDEGICURjCURp!C YENO/<<eCURw-a 3/4YENiS:oS:i NTFS
   CURA^3IDEGI-a-o|^3 PartitionMagic CURI GParted
   ^3o"a-oO/CURu"au{|!!C GParted|b^3\|h Linux distributions -a-o Live
   CD ^3-L-|^3'-L-"N!A^1^3NOTO SystemRescueCD!C

   YENO/<<eCURw-a 3/4 Microsoft Vista CURA^3IDEGI-a-o<<.s 1/2O
   3/4aCURjCURp.||^3DEGYAD!C |bDEGuCURWzAth|u:DEGES:@(R)E!A
   1/2D-DEGO+-oCURaAa:n|^3 Vista |w,EYENu-oD-YENHS:K,UCUR@!C
   |^1YEN~!A+-j-P<<O/A:^3YENyDEGu-oI-oD--ouAA@!AYENHCURI^2{|^3,e(R)AE^3AEYEN-:!C

     A:uS:iCUR-L-.i-a-o"IYENI^3o"C,CURu"a!AYENi-`a.|S:RDEG-L-(c)O|^3uw-oD-CURW-a-o,e(R)AE!C
     |b"IYENI^3o"C,CURu"a<<e!A 1/2D-
     1/2T(c)w+-zCURw|^3YENy^3AEYEN-:|n,e(R)AE!C

   1/2d"O 2-1. "IYENI^2{|^3-a-oCURA^3IDEGI

   DEG^2^3]+-zYENu|^3CUR@O 4 GB -a-ouw-oD-!A|OYENBCURw,g,ECURF
   Windows !AuM<<a+-N^3oAuuw-oD-CURA|""aO-oI-oD-YENN,^1!GC: CURI
   D:!A"COCURjCURpNOTDEG 2 GB !C C:  1/4NCURW(c)nCURF 1 GB
   -a-o,e(R)AE!A |O D:  1/4NCURW(c)nCURF 0.5 GB -a-o,e(R)AE!C

   ^3o-aiYENU:uw-oD-CURW|^3"aOCURA^3IDEGI!A"CO-oI-oD-YENN,^1
   1/4N^3-L-NOTOCURA^3IDEGI!C +-zYENiYENHS:a(c)O|^3(c)n|b D:
   -a-o,e(R)AE!A^3-L-^2 3/4DEGE"`i C:!A^3o
   1/4E'N-aAAYENXCURF^2A:CURGOCURA^3IDEGIYENiYENHu^1 FreeBSD "IYENI!C

   1/2d"O 2-2. AY'i^2{|^3-a-oCURA^3IDEGI

   DEG^2^3]+-zYENu|^3CUR@O 4 GB uw-oD-!A|OYENBCURw,g,ECURF Windows!C
   |b|w,E Windows (R)ES:a 4 GB ^3-L-u^1 C: 
   1/4N!A"AYENB^2{|bCURw,gYENICURF 1.5 GB
   -aAAP:!!A|OS:A.Q+-N^3NCURU-aAAP:!-a-o 2 GB u^1 FreeBSD "IYENI!C

   |p|^1CUR@"O!ANOTDEGCURF,E
   FreeBSD!AS:AYEN^2P:.|bYENHCURU"a-oO/CURe|!CURG?iCUR@!G

    1. ^3AEYEN-: Windows ,e(R)AE!AuM<<a<<,E Windows!A "A|b|w,E
       Windows (R)Eu^1 2 GB -a-oCURA^3I-aAAP:!!C

    2. "IYENICURWz-a-oCURu"a!A^1^3NOTO PartitionMagic!A"O<<.s 1/2O
       3/4a Windows (c)OYENI-a-oCURA^3IDEGICURjCURp!C

     --------------------------------------------------------------

    2.3.3.2. Alpha NOT[-oc-a-o-oI-oD-DEGt,m 1/4O|!

   |b Alpha CURW!A+-zYEN^2P:."IYENICUR@ 3/4aAuuw-oD-u^1 FreeBSD!A
   "S|^3?`i-ak|b|PAuuw-oD-CURW,o"a:YENLS:@.~"t^2I|@|s!C
   "ICUR-L-|P<<NOT,^1-a-o Alpha  3/4-:
   3/4^1!A+-z-a-ouw-oD-YENiYENHNOTO SCSI (c)I IDE uw-oD-!A
   YENun+-z-a-o 3/4-: 3/4^1YENiYENH+-q^3o"C,uw-oD-P:}
   3/4-:'NYENiYENH!C

   <<o:.O Digital / Compaq "IYENICURaYENU-a-o 1/2s+-AE.(R)ae!A
   (c)O|^3 SRM ?eCURJ-a-o^3!CURA^3-L-YENICURj 1/4g-aiYENU:!C
   -a`.N!GSRM CURjCURp 1/4g|^3S:O!C

   n+-o-a 3/4+-z-oI-oD--a-o|W-oUYENHCURI<<NOT,^1!AYENiYENH|b SRM
   console '-L-YENU:CURU"IYENI SHOW DEVICE (c)RYENO!G

 >>>SHOW DEVICE
 dka0.0.0.4.0               DKA0           TOSHIBA CD-ROM XM-57  3476
 dkc0.0.0.1009.0            DKC0                       RZ1BB-BS  0658
 dkc100.1.0.1009.0          DKC100             SEAGATE ST34501W  0015
 dva0.0.0.0.1               DVA0
 ewa0.0.0.3.0               EWA0              00-00-F8-75-6D-01
 pkc0.7.0.1009.0            PKC0                  SCSI Bus ID 7  5.27
 pqa0.0.0.4.0               PQA0                       PCI EIDE
 pqb0.0.1.4.0               PQB0                       PCI EIDE

   "OCURlCURCUR 3/4-: 3/4^1NOTDEG Digital Personal Workstation
   433au!A "AYENBAAaYENU:YENX|^1 3/4-: 3/4^1|^3^3s+-uCURTO-oI-oD-
   3/4-:!C ^2A:CUR@ONOTO CDROM!AYENsDEGu DKA0
   !FYENtYEN~"aONOTO-oI-oD- 3/4-:!A CURAS:OYENsDEGu!G DKC0 CURI
   DKC100!C

   -oI-oD- 3/4-:-a-o|W-oUCURCUR|^3 DKx |r 1/4E-a-oNOTO SCSI
   uw-oD-!C"O|p!G DKA100 -aiYENU:NOTO SCSI uw-oD-!A"a: SCSI ID NOTDEG
   1!A |`i|b^2A:CUR@O SCSI P: *NOTy+-AE(A)!F |O DKC300 -aiYENU:NOTO
   SCSI uw-oD-!A "a: SCSI ID NOTDEG 3!A|`i(c)o^2A:CURTO SCSI P:
   *NOTy+-AE(C)!C ,E,m|W-oU PKx <<hNOTDEG SCSI +-+-"iYENd!C YENNCURWz
   SHOW DEVICE -a-ou^2-aGNOTY"O!A SCSI YENu-oD-
   3/4-:CUR]^3Quo/NOTDEGNOTO SCSI uw-oD--a-oCUR@-oO/!C

   YNOTDEG IDE uw-oD--a-o,U:!A|W-oU.||^3 DQx |r 1/4E!A |O PQx
   <<h-aiYENU:NOTU^1iA^3-a-o IDE -oI-oD-+-+-"i 3/4^1!C

     --------------------------------------------------------------

  2.3.4.  3/4a^2zS:A-a-o-oo,o^3](c)w,e(R)AE

   |p-aG.Q^3z^1L-oo,o( FTP -,(c)I NFS)|w,E FreeBSD!A
   "-o>>o'NYEN^2P:.-a 3/4^1D+-z-a-o-oo,o^3](c)w!C |b|w,E FreeBSD
   -a-o^1Lu{CURCUR+-N.|'-L-YENU:+-z?eCURJ^3o"C,,eDEGT!AYENHP:P:S:QS:^1|"|w,E^1Lu{!C

     --------------------------------------------------------------

    2.3.4.1. "IYENICURACURO-oo,o(Ethernet)(c)I Cable/DSL  1/4AE 3/4U
    3/4-:CURW-oo

   Y"IYENICURACURO-oo,o!A(c)INOTOn^3z^1L Cable/DSL  1/4AE 3/4U
   3/4-:CURW-oo!A "-o>>o+-zYEN^2P:..C,^3AECURU+--a-o,eDEGT!G

    1. IP |`iS:}

    2. ^1w^3] Gateway(^1h^1D) -a-o IP |`iS:}

    3. Hostname( 3/4-: 3/4^1|W-oU)

    4. DNS |o/-aA 3/4^1-a-o IP |`iS:}

    5. Subnet Mask

   YCUR-L--a
   3/4^1D^3o"C,,eDEGT!A+-zYENiYENH,ssDEGY"t^2I-oTH^2z-aI(c)INOTO+-z-a-o
   ISP .~-aI!C YENLIYENi-`a.|>>!^3o"C,,eDEGT.|YENN DHCP
   |UDEGE<<u:NOT-L-!F |p-aGNOTO^3o 1/4E-a-o,U:!A
   1/2D-DEGO|i^3oCUR@AI'NYENiYENHCURF!C

     --------------------------------------------------------------

    2.3.4.2. "IYENI 1/4AE 3/4U 3/4-:CURW-oo

   YYENNCUR@-e-a-o 1/4AE 3/4U 3/4-:
   1/4.+-uCURW-oo!A+-zCUR'uMYENiYENH|w,E FreeBSD!A
   YENuNOTO.|>>Yn<<U:-ao/-a-o(R)EP:!!C

   +-zYEN^2P:.-a 3/4^1D!G

    1. 1/4.+-u"`i ISP -a-o^1q,U:,^1 1/2X!C

    2. +-z-a-o 1/4AE 3/4U 3/4-:NOTO^3s"`ithO COM DEGd-!C

    3. +-z 1/4.+-u"`i ISP (c)OYENI-a-o+-b,^1,o+-K 1/2X!C

     --------------------------------------------------------------

  2.3.5. NOTd 3/4\ FreeBSD DEGE>>~-ai(Errata)

   Ao:uMS:UI-oECURO"I+-o"CO FreeBSD uo|ae-a(c)YEN>>^3-L-<<U:A(c)w!A
   |yNOTO^1Lu{CURCURCUR'uMCUR-L-S:K|^3(R)E.|uoYENI?u>>~!C
   |bNOTY"C,<<U:"u"-L--a-o+-!S:ICURU!A^3o"C,?u>>~.|
   1/4vAAT"`i|w,E-a-o^1Lu{!C .iuo^2{^3o"C,?u>>~YENB
   *YEN?<<a!A.|+-NYEN|I|C|b   FreeBSD DEGE>>~-ai(Errata) CURCUR!C
   |b+-z|w,E FreeBSD
   <<e!AA^3,OYENyNOTYNOTYDEGE>>~-aiCURCUR|^3"S|^3CURDEG>>oDEGYAD.|
   1/4vAAT"`i+-z-a-o|w,E!C

   Ao:(c)o(c)O|^3uo|ae-a(c)YEN>>-a-o,eDEGT(YEN]NOTADEGE>>~-ai)!AYENiYENH|b
   FreeBSD -oo-, -a-o uo|ae+-!^3o/(release information) S:a:"`i!C

     --------------------------------------------------------------

  2.3.6. .C,^3AE|n FreeBSD |w,EAE(R) *

   FreeBSD YENiYENH^3z^1LCURU+-YENo|oCUR@-oO/|w,E"O. 1/2P:i|ae|w,E!J

   Local Media

     * CDROM (c)I DVD

     * ^2{|^3-a-o DOS CURA^3IDEGI

     * SCSI (c)I QIC -oI+-a!C

     * ^3n-oD--oICURu

   Network

     * FTP -,!BCURa:'(c) Passvie  1/4O|!-a-o FTP -,(Y+-z 3/4-:
       3/4^1|b NAT CUR-o) !BNOTAE|U: HTTP proxy ^3-L-YENiYENH!C

     * NFS |o/-aA 3/4^1

     * +-MYENI(dedicated)-a-o parallel (c)I serial ^3s 1/2u

   YCURw,g|^3 FreeBSD -a-o CD (c)I DVD!A|y 3/4-:
   3/4^1CUR-L-CURa:'(c)+-qYENu-oD-P:} 3/4-:-a-o,U:!A "-o>>o 1/2D--a
   1/2+-uP:iCURUCUR@,` (uU 2.3.7 ,`)!C

   Y"S|^3 FreeBSD |w,ECURu-a-o,U:!A"-o>>o 1/2D-YENyNOTY uU 2.13 ,`
   ^3o,I.|CURP:^2D-|p|o.C,^3AE(c)O>>Yn-a-o|w,ECURu!A
   .O,O,`"BAEJS:E|n<<a!A'NYENiYENHA:~A:oCURUCUR@"B uU 2.4 ,`!C

     --------------------------------------------------------------

  2.3.7. .C,^3AE|nP:} 3/4-:-oICURu

   FreeBSD |w,ENOTyu{NOTOn+-q^1q,-L-P:} 3/4-:<<a!AP:iCURJ FreeBSD
   |w,Eue+- !X!X |OCUR-L-NOTO|b"a:YENLS:@.~"t^2ICURWDEGo|aeu{|!!C
   CUR@-e"OA?!A^1q,-L-^3-L-NOTOYENI,E|buw-oD-CURW-a-oS:@.~"t^2I"OP:}
   3/4-:!A CUR]YENiYENHYENIP:} 3/4-:-oICURu"OP:} 3/4-:!F
   |^1YEN~!A^2{|bCURj|h 1/4AE^1q,-L-^3-L-YENiYENH+-qYENu-oD-P:}
   3/4-:!C

     '-L-YENU:: |p-aG+-z|^3 FreeBSD -a-o CDROM (c)I DVD(uL 1/2
     *NOTOYENIP:R^2{|"-a-o(c)INOTO|UCURv?N?y-a-o)!A
     YENB+-z-a-o^1q,-L-YENiCURa:'(c)YENNYENu-oD-P:} 3/4-:!A(^3q+-`|b
     BIOS CURCUR.||^3 !S:Boot Order!"
     (c)IAth|u:?iP:u)!A"-o>>o+-z'NYENiYENH,o^1L|^1CURp,`!C |]NOTDEG
     FreeBSD CDROM (c)I DVD ^3-L-YENiYENHYENI"OP:} 3/4-:!C

   1/2D-<<o:.OCURU+-"BAEJ!AYENH>>sS:@P:} 3/4-:CURu!G

    1. "u+-oP:} 3/4-:CURu-a-oNOTM^1^3AE(images)

       P:}
       3/4-:-oICURuYENI-a-oNOTM^1^3AE(images)^3q+-`.|(c)n|bYENu-oD-CURuCURW-a-o
       floppies/ YENO/?yCUR-o!A YENtYEN~CUR]YENiYENH+-q^1^3NOTOCURU+-
       FTP -,-a-o floppies YENO/?yCURU,u:!G
       ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/<arch>/<version>-RELEASE/floppies/
       !C
       1/2D-+-N!yarch!z!B!yversion!z'A'<<NOTDEGYEN'-oa|w,E-a-o^1q,-L-NOT[-oc!BOS
       -a(c)YEN>>!C "O|p!G.Q,E-a-oNOTO FreeBSD/i386 9.1-RELEASE
       !A"-o>>oYENiYENH"`i   CURU,u:!C

       NOTM^1^3AE(images)-a-o-athAE|W^3-L-NOTO .flp!C|O floppies/
       YENO/?yCUR-oYEN]S:tCUR@"C,CUR-L-|PYENI^3~-a-oNOTM^1^3AE
       (images)!A^3o"u"M(c)o+-zn,E-a-o FreeBSD
       -a(c)YEN>>!B>>Y"D!BuwAAeDEGt^3AENOTDEG|o!C ^3q+-`n 4
       ONOTM^1^3AE!ACUR]'NNOTO!G boot.flp!B kern1.flp!Bkern2.flp!B
       kern3.flp!C Y|^3-oADEGY-a-o,U:!A 1/2D-A 1/2
       3/4\|PCUR@YENO/?yCURU-a-o README.TXT
       CURaaYENoAE!AYENHAA,NNOTUAo:^3I.s-a`.N"AEP:u!C

         <<n: |b"IYENI FTP CURU,u:(R)E!AYEN^2P:."IYENI binary  1/4O|!
         P:i|aeP:C,?e!C |^3"C,AsA:y 3/4^1^1w^3]NOTOYENH text ((c)I
         ASCII)  1/4O|!"OP:C,?e,e(R)AE!A (c)OYENH^3o"C,?u>>~P:C,?e
         1/4O|!CURU,u:-a-oNOTM^1^3AE(c)ODEGu|"-a-o-oICURu!A.|uL-ak"IYENI!C

    2. .C,^3AEP:} 3/4-:-oICURu

       "CONOTM^1^3AE^3-L->>YnCUR@+-i-oICURu!A"AYENB 1/2D-A
       *S:K"IYENI"`iAa-a-o-oICURu!C
       ^3IA^2^3ae-a-oAE'uCURe|!'NNOTO|UCURvYENyS:a^3o"C,-oICURu|A<<.s(R)ae|!CURAE(format)
       |OCUR-L-nNOTU<<H(c)O?
       *-a-oCURw(R)ae|!CURAE-a-o-oICURu!AWindows CUR-o-a-o format
       |b(R)ae|!CURAE(R)E!A"ACUR-L-.|S:iP:DS:ANOTOS:_|^3Aay!A
       |OYENu.|-a 1/2+-u+-NYEN|I
       1/4D-YENU:Aay|OCUR-L-"IYENIAay^3!CURA|OCURw!C
       |^1YEN~!A<<O/A:^3+-A:YENIYENth.s-a-o-oICURu"O>>sS:@|w,ECURuCURn,u<<OAI!C

         <<n: Y|b|w,E FreeBSD -a-o^1Lu{CURCURuoYENI.i 3/4-:!B
         ue+-au^2(c)INOTO"a:YENL(c)C,^2S:-a-o^2{P:H!A-oYENynAh-oA-a-o'NNOTOP:}
         3/4-:-oICURuNOTOS:_Aa+- 1/4!C 
         1/2D-YENI"a:YENL-a-o-oICURu>>sS:@NOTM^1^3AE|A,O,ONOTY!C

    3. +-NNOTM^1^3AE(images) 1/4gCURJ"`i-oICURuCUR-o

       .flp AE"A<<DCUR@-eAE(R) *!A CUR-L--`a-a 1/2+-uS:aYEN|
       1/2AE>>s"`i-oICURuCURW!C "AE^1eCURWYEN|NOTOYEN]S:t
       3/4a+-i-oICURu(c)O|^3CUR-o(R)e-a-oNOTM^1^3AE(image)!C
       CUR]'NNOTO>>!!ACUR-L--`a-A-oe 1/2AE>>sAE(R) *"`i-oICURuCURW!A
       |OYEN^2P:."IYENI-SS:O-a-oCURu"au{|!!A"O+-NNOTM^1^3AE-a 1/2+-u
       1/4g"`i-oICURuCURW!C

       YnYENI MS-DOS/Windows "OS:@|w,ECURu-a-o,U:!A"-o>>oYENiYENHYENI
       fdimage CURu"au{|!"O+-NNOTM^1^3AE!A 1/4g"`i-oICURuCURW!C

       Y+-zYENI-a-oNOTO FreeBSD YENu-oD--a-o,U:(DEG^2^3]YENu-oD-
       3/4-:YENN,^1NOTDEG E: !A"-o>>o
       1/2D-DEGo|aeAth|u:CURU+--a-o<<u:YENO!G

 E:\> tools\fdimage floppies\boot.flp A:

       1/2D-DEGw^1i"CO>>YnYENI"`i-a-o .flp NOTM^1^3AE!A <<
       1/2AECURWz-a-o<<u:YENO(DEGO+-oS:oS:iNOTUAo:AE|W)!A"C|,-a-oNOTM^1^3AES:^1|"<<a!A
       ^3-L->>Yn'<<YENtYEN~CUR@CURu"O,E.s-a-oNOTM^1^3AE!F 
       1/2D-DEGO+-o!G
       |bS:@|n-a-o-oICURuCURWuu(c)uNOTO"IYENIthONOTM^1^3AES:@-a-o!C Y
       .flp NOTM^1^3AE(c)n|bCUR-L-|P|aCURe!A  1/2D-|U|ae
       *S:iCURWz<<u:YENO!CY"S|^3 FreeBSD YENu-oD--a-o,U:!A
       YENiYENH"`i FTP CURW+--a-o tools YENO/?y CURU,u: fdimage
       "IYENI!C

       |p-aGnYENI UNIX "t^2I(CURn|p"a:YENLYENx FreeBSD  3/4-: 3/4^1)
       "O>>sS:@P:} 3/4-:CURu-a-o,U:!AYENiYENHYENI dd(1)
       <<u:YENO"OS:aNOTM^1^3AE-a 1/2+-u 1/4gCURJ"`i-oICURuCURW!C |b
       FreeBSDCURW-a-o,U:!AYENiYENHYEN'Ath|u:CURU+--a-o<<u:YENO!G

 # dd if=boot.flp of=/dev/fd0

       |b FreeBSD CURCUR!A/dev/fd0 'NNOTO<<u:^2A:CUR@YENx^3n-oD-
       3/4-:(S:YCUR@-e MS-DOS/Windows CURW-a-o A: -oI-oD- 3/4-:)!F |O
       /dev/fd1 <<u: B: -oI-oD- 3/4-:!A"a: 3/4l-a-o"I|^1Ath+-A!C
       CUR-L-^1L"a:YENL-a-o UNIX
       "t^2IYENi-`a.|YENICUR-L-|P-a-o|W-oU!A^3o(R)E'NnNOTd
       3/4\,O"t^2I-a-o>>!(c)uCURaaYENoCURF!C

   ^2{|bDEG_!AS:UIYENiYENHP:}(c)l|w,E FreeBSD AAo!I

     --------------------------------------------------------------

2.4. P:}(c)l|w,E

     <<n: ^1w^3]-a-o+-!-apCURU!A|w,E^1Lu{"ACUR-L-.|S:iAAU:+-z-oI-oD-
     3/4-:CURCUR-a-oYENo|o,e(R)AE!A
     DEG-L-<<D+-zNOTY"`iCURU+--a-oDEGT(R)S:!G

 Last Chance: Are you SURE you want continue the installation?

 If you're running this on a disk with data you wish to save then WE
 STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding!

 We can take no responsibility for lost disk contents!

     |bNOTY"`i^3o^3I<<a-a-oA:uS:iDEGT(R)S:<<e!A
     +-z^3-L-YENiYENHAH(R)EA-:P:}|w,Eu{|!|OCUR-L-.|AAU:S:o+-z-a-ouw-oD-!C
     |p-aG+-zuo^2{|^3YENo|o^3](c)w?u>>~!A ^3o(R)E+-zYENiYENH-a
     1/2+-u+-N^1q. 1/2Ao:+- 1/4|OCUR-L-.|^3y|"YENo|oP:E(R)`!C

     --------------------------------------------------------------

  2.4.1. P:} 3/4-:+-ODEGENOTyu{ 1/2g

    2.4.1.1. i386(TM) YENYENx-a-oP:} 3/4-:NOTyu{

    1. |bCUR@P:}(c)l!A^1q,-L-^1q. 1/2P:}Ao:NOTOAo:^3NOT-a-o!C

    2. YEN'P:}^1q,-L-^1q. 1/2P:}Ao:!CeP:}(c)l-a-o(R)EO!A
       YEN|A^3,O.|AAaYENU:P:iCURJ"t^2I^3](c)w?i^3ae(c)I BIOS
       n<<o:thOAa:!A +-`"-L--a-o|^3!G F2, F10, Del (c)I
       Alt+S!C(<<o:Aa: 1/2D-"I 3/4U^1e>>U+-!-ap"M(c)w) CUR-L- 1/2
       *NOTOn<<o:thOAa:!A  1/2D-<<o:YEN|P:iCURJ BIOS ^3](c)wue+-!C
       |^3(R)E+-z-a-o^1q,-L-YENi-`a.|AAaYENU:CUR@O^1IS:Iue+-!A
       ^3q+-`DEGu-akNOTO<<o: Esc Aa:+-NA-:P:}^3oO^1IS:Iue+-!A
       YENH"I+-z-`aDEG-:NOTY"`iYEN^2n-a-o^3](c)wDEGT(R)S:!C

    3. S:a:YENXYENiYENH^3](c)w!yP:} 3/4-:P:P:S:C,(Boot
       Order)!z-a-o?iP:u!A
       ^3q+-`,O?iP:u.||CYENXCUR@"C,^3]^3AEAAy+-z?i 3/4U:!A"O|p!J
       Floppy, CDROM, First Hard Disk uYENuYEN!C

       |p-aGnYENI^3n-oD-|w,E!A 1/2D- 1/2T(c)w floppy disk
       n|CNOTDEGP:} 3/4-:P:P:S:C,-a-o^2A:CUR@O!F
       YnYENIYENu-oD-|w,E!ADEGO+-o CDROM n|CNOTDEGP:}
       3/4-:P:P:S:C,-a-o^2A:CUR@O!C NOTDEGCURFA
       *S:KCUR-L-YEN^2n-a-o-oA'b!A 1/2D-DEGN|O 3/4-: 3/4^1!BYEND
       3/4-:-aO>>!(c)uCURaYENU!C

       Ax|s^3](c)w"AA-:P:}!A"t^2IA^3,O.|<<.s+-ODEGE!C

    4. YnYENI-oICURu|w,E!A 1/2D-S:a|b uU 2.3.7
       ,`CUR@,`CURCUR>>sS:@|n-a-o boot.flp
       "-o+-i|w,E-oICURu(c)n"`i^2A:CUR@YENx^3n-oD- 3/4-:CURCUR!C

       |p-aGNOTO+-qYENu-oD-|w,E!A"-o>>oP:} 3/4-:<<a 1/2D-+-N FreeBSD
       YENu-oD-(c)nCURJYENu-oD- 3/4-:CURCUR!C

       |p-aG!AP:} 3/4-:<<a|p(c)^1+-`CUR@
       1/4E|O"S|^3+-q^3n-oD-(c)IYENu-oD-P:} 3/4-:!A 1/2D-AENOTd!J

         1. NOTOCUR-L-NOTO-oICURu(c)IYENu-oD-CURO+-ss(c)nCURJ|O?uYEN-c-P:}
            3/4-:(R)EP:!!C |p-aGNOTO!A
            1/2D-+-NYEN|I(c)nCURJ!AuM<<a<<.sP:} 3/4-:!C

         2. BIOS ^3](c)wCUR-L-^1i(c)IS:NCURFAx|s^3](c)w!A
            1/2D-<<.sAENOTd BIOS -a-o^3](c)w!C

         3. +-z-a-o^1q,-L- BIOS CUR-L-CURa:'(c)+-qYENu-oD-P:} 3/4-:!C

    5. |^1(R)E!AFreeBSD 'NP:}(c)l+-ODEGECURF!C
       |p-aGNOTO+-qYENu-oD-P:}
       3/4-:!A.|"-L-"`iAth|u:CURU+--a-oue+-(-a(c)YEN>>^3!CURANOTU^2CUR)!G

 Booting from CD-Rom...
 CD Loader 1.2

 Building the boot loader arguments
 Looking up /BOOT/LOADER... Found
 Relocating the loader and the BTX
 Starting the BTX loader

 BTX loader 1.00 BTX version is 1.01
 Console: internal video/keyboard
 BIOS CD is cd0
 BIOS drive C: is disk0
 BIOS drive D: is disk1
 BIOS 639kB/261120kB available memory

 FreeBSD/i386 bootstrap loader, Revision 1.1

 Loading /boot/defaults/loader.conf
 /boot/kernel/kernel text=0x64daa0 data=0xa4e80+0xa9e40 syms=[0x4+0x6cac0+0x4+0x88e9d]
 \

       |p-aG+-z+-q^3n-oD-P:}
       3/4-:!A.|NOTY"`iAth|u:CURU+--a-oue+-(-a(c)YEN>>^3!CURANOTU^2CUR)!G

 Booting from Floppy...
 Uncompressing ... done

 BTX loader 1.00  BTX version is 1.01
 Console: internal video/keyboard
 BIOS drive A: is disk0
 BIOS drive C: is disk1
 BIOS 639kB/261120kB available memory

 FreeBSD/i386 bootstrap loader, Revision 1.1

 Loading /boot/defaults/loader.conf
 /kernel text=0x277391 data=0x3268c+0x332a8 |

 Insert disk labelled "Kernel floppy 1" and press any key...

       1/2D-(R)U 3/4U'-L-YENU:+-N boot.flp -oICURu"uYENX!A "A(c)nCURJ
       kern1.flp ^3o+-i-oICURu!A uM<<a<<o: Enter Aa:!C
       A`CURS:!A+-zYENu>>Y+-q^2A:CUR@+-i-oICURu+-ODEGE!AuM<<a(R)U
       3/4U'-L-YENU:!A|A(c)nCURJNOTUAo:-oICURuS:YYENi!C

    6. uL 1/2 *+-q^3n-oD-(c)IYENu-oD-P:} 3/4-:!A+-uCURU"O.|P:iCURJ
       FreeBSD boot loader ?i^3aeue+-!G

       ^1IS:I 2-1. FreeBSD Boot Loader ?i^3ae

       +-zYENiYENHuYEN<<Y 10 NOTi!A(c)INOTO<<o: Enter Aa:!C

     --------------------------------------------------------------

    2.4.1.2. Alpha YENYENx-a-oP:} 3/4-:NOTyu{

    1. |bCUR@P:}(c)l!A^1q,-L-^1q. 1/2P:}Ao:NOTOAo:^3NOT-a-o!C

    2. YEN'P:}^1q,-L-^1q. 1/2P:}Ao:!AuM<<auYENP:} 3/4-:ue+-YENX^2{!C

    3. YnYENI-oICURu|w,E!A 1/2D-S:a|b uU 2.3.7
       ,`CUR@,`CURCUR>>sS:@|n-a-o boot.flp
       "-o+-i|w,E-oICURu(c)n"`i^2A:CUR@YENx^3n-oD- 3/4-:CURCUR!C
       uM<<a!AYEN'CURU|C<<u:YENO"O+-q-oICURuP:} 3/4-: (
       1/2D-S:aCURU|C^3n-oD-
       3/4-:YENN,^1S:iNOTDEGS:A^1q,-L--a-o^3n-oD- 3/4-:YENN,^1)!G

 >>>BOOT DVA0 -FLAGS '' -FILE ''

       YnYENIYENu-oD-|w,E!A
       1/2D-S:aDEGu|n-a-o|w,ECURu(c)nCURJYENu-oD- 3/4-:!A
       uM<<aYEN'CURU|C<<u:YENO"O+-qYENu-oD-P:} 3/4-: (
       1/2D-S:aCURU|CYENu-oD-
       3/4-:YENN,^1S:iNOTDEGS:A^1q,-L--a-oYENu-oD- 3/4-:YENN,^1)!G

 >>>BOOT DKA0 -FLAGS '' -FILE ''

    4. +-uuU FreeBSD P:}
       3/4-:CURu'N.|P:}(c)lCURF!CYNOTOYENN^3n-oD-P:} 3/4-:-a-o,U:!A
       ^3o(R)E.|NOTY"`iYENHCURUDEGT(R)S:!G

 Insert disk labelled "Kernel floppy 1" and press any key...

       1/2D-.O<<u:YENU:!A(R)^3"<< boot.flp CURu!AS:i(c)n kern1.flp
       CURu!A uM<<a<<o: Enter!C

    5. uL 1/2 *+-q^3n-oD-(c)IYENu-oD-P:}
       3/4-:!A+-z^3-L-.|NOTY"`iCURU+-^3oNOTqDEGT(R)S:!G

 Hit [Enter] to boot immediately, or any other key for command prompt.
 Booting [kernel] in 9 seconds... _

       +-zYENiYENHuYEN<<Y 10 NOTi!A(c)INOTO<<o: Enter Aa:!C
       +-uCURU"O'N.|P:iCURJkernel configuration ?i^3ae!C

     --------------------------------------------------------------

    2.4.1.3. Sparc64(R) YENYENx-a-oP:} 3/4-:NOTyu{

   CURj|h 1/4AE-a-o Sparc64(R)  3/4-: 3/4^1^1w^3].||UDEGE+-quw-oD-P:}
   3/4-:!C |]|^1n,E FreeBSD -a-o,U:!A<<h>>YnP:iCURJ
   PROM(OpenFirmware) ^3](c)wYENN-oo,o(c)IYENu-oD-P:} 3/4-:CUR~YENi!C

   1/2D-YENy<<P:} 3/4-:!AuM<<auYEN<<Y-a 1/2"`iP:}
   3/4-:DEGT(R)S:YENX^2{!C ^3o^3!CURAYENi-`a.|AH 3/4-:
   3/4^1<<NOT,^1CUR-L-|P
   !A|O|^3(c)O(R)t^2S:!A|yCURj.S:.|YENX^2{^1^3CURU|C^3o 1/4E!G

 Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
 Copyright 1998-2001 Sun Microsystems, Inc.  All rights reserved.
 OpenBoot 4.2, 128 MB memory installed, Serial #51090132.
 Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.

   Y+-z 3/4-: 3/4^1|^1(R)E.|YENyYENNuw-oD-P:} 3/4-:!A"-o>>o>>Yn<<o:
   L1+A (c)I Stop+A (c)I-aINOTO^3z^1L serial console (YENI-ak
   1/2D-DEGN 3/4\ tip(1) (c)I cu(1) CUR-o|^3Ao: ~# -a-o>>!(c)u)
   DEGeYENX BREAK <<u:YENO"OP:iCURJ PROM prompt!C
   CURj.S:.|^1^3CURU+-!G

 ok         (1)
 ok {0}    (2)

   (1)
           ^3oNOTO 3/4AYENI(c)oYENu|^3^3aeCUR@ CPU -a-o 3/4-: 3/4^1!C
   (2)
           ^3oNOTO 3/4AYENI(c)o SMP  3/4-: 3/4^1!A
           1/4AE|r^3!CURANOTO<<u:YENO/<<e|b"IYENICURCUR-a-o CPU 
           1/2s,^1!C

   |^1(R)E 1/2D-S:a|w,EYENu-oD-(c)nCURJYENu-oD- 3/4-:CUR-o!AuM<<a|b
   PROM prompt YEN' boot cdrom S:YYENi!C

     --------------------------------------------------------------

  2.4.2. "-on<<c,>>oYENhA 1/2 3/4\DEG>>'uuwAAe-a-ou^2-aG(c)O!H

   YENy<<e|b?A^1oCURW(c)OAAaYENU:-a-o^3I<<a'X|E|ae|r!A.||s|b
   1/4E|sDEGI(buffer) YENH<<K+-zA 1/2 3/4\!C

   YnA 1/2 3/4\ 1/4E|sDEGI!A 1/2D-<<o: Scroll Lock Aa:!A
   ^3o.|P:}+-O+-^2DEGEue+-YEN\-`a!C
   uM<<a'NYENiYENH"IYENICURe|VAa:!A(c)INOTO PageUp!B PageDown
   Aa:"OCURWCURUA 1/2 3/4\!C |A<<o:CUR@|, Scroll Lock
   Aa:!A'N.|DEG+-CURiue+-+-^2DEGE!C

   ^2{|b'N 1/2D-,O,ONOTY!AA 1/2 3/4\CUR@CURUDEG>>'uuwAAe-a-oue+-S:a!A
   S:AA^3,O.|NOTY"`iAth|u: ^1IS:I 2-2 -a-oue+-!A
   -uYEN?ue+-.|"IS:A-a-o^1q,-L-^3]^3AE|O|^3(c)OCUR-L-|P!C

   ^1IS:I 2-2. DEG>>'uuwAAe-a-o"OCURl

 avail memory = 253050880 (247120K bytes)
 Preloaded elf kernel "kernel" at 0xc0817000.
 Preloaded mfs_root "/mfsroot" at 0xc0817084.
 md0: Preloaded image </mfsroot> 4423680 bytes at 0xc03ddcd4

 md1: Malloc disk
 Using $PIR table, 4 entries at 0xc00fde60
 npx0: <math processor> on motherboard
 npx0: INT 16 interface
 pcib0: <Host to PCI bridge> on motherboard
 pci0: <PCI bus> on pcib0
 pcib1:<VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0
 pci1: <PCI bus> on pcib1
 pci1: <Matrox MGA G200 AGP graphics accelerator> at 0.0 irq 11
 isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0
 isa0: <iSA bus> on isab0
 atapci0: <VIA 82C586 ATA33 controller> port 0xe000-0xe00f at device 7.1 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0 <VIA 83C572 USB controller> port 0xe400-0xe41f irq 10 at device 7.2 on pci
 0
 usb0: <VIA 83572 USB controller> on uhci0
 usb0: USB revision 1.0
 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr1
 uhub0: 2 ports with 2 removable, self powered
 pci0: <unknown card> (vendor=0x1106, dev=0x3040) at 7.3
 dc0: <ADMtek AN985 10/100BaseTX> port 0xe800-0xe8ff mem 0xdb000000-0xeb0003ff ir
 q 11 at device 8.0 on pci0
 dc0: Ethernet address: 00:04:5a:74:6b:b5
 miibus0: <MII bus> on dc0
 ukphy0: <Generic IEEE 802.3u media interface> on miibus0
 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xec00-0xec1f irq 9 at device 10.
 0 on pci0
 ed0 address 52:54:05:de:73:1b, type NE2000 (16 bit)
 isa0: too many dependant configs (8)
 isa0: unexpected small tag 14
 orm0: <Option ROM> at iomem 0xc0000-0xc7fff on isa0
 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: <1440-KB 3.5" drive> on fdc0 drive 0
 atkbdc0: <Keyboard controller (i8042)> at port 0x60,0x64 on isa0
 atkbd0: <AT Keyboard> flags 0x1 irq1 on atkbdc0
 kbd0 at atkbd0
 psm0: <PS/2 Mouse> irq 12 on atkbdc0
 psm0: model Generic PS/@ mouse, device ID 0
 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 sc0: <System console> at flags 0x100 on isa0
 sc0: VGA <16 virtual consoles, flags=0x300>
 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
 sio0: type 16550A
 sio1 at port 0x2f8-0x2ff irq 3 on isa0
 sio1: type 16550A
 ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
 pppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/15 bytes threshold
 plip0: <PLIP network interface> on ppbus0
 ad0: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata0-master UDMA33
 acd0: CD-RW <LITE-ON LTR-1210B> at ata1-slave PIO4
 Mounting root from ufs:/dev/md0c
 /stand/sysinstall running as init on vty0

   1/2D-YENJ^2OAENOTd"CP:uAE'uu^2-aG!AYENH 1/2T(c)w FreeBSD |^3YEN?
   1/2TDEG>>'u"`i"CP:uuwAAe!C
   Y"SDEG>>'u"`iuwAAe-a-o,U:!A"-oue+-'NCUR-L-.||CYENX"OCURF!C |Uq
   kernel YENiYENHAAy+-zYEN[CURW`iYEN>>^1w^3]-a-o GENERIC kernel
   (c)OCUR-L-CURa:'(c)-a-ouwAAe!A^1^3NOTOu(R)A:YENdCURS:Ath!C

   |O FreeBSD 6.2 DEG_-a-o-a(c)YEN>>!A|bDEG>>'uuwAAe<<a.|NOTY"`i
   ^1IS:I 2-3!A 1/2D-YENICURe|VAa:?i
   3/4U:S:A-a-oDEGeS:O!B|aDEGI(c)I,s^2O!C uM<<a<<o: Enter
   Aa:'N.|ADEGS:A^3](c)wNOTUAo:DEGeS:O!BAa: 1/2L^1iA^3!C
   |^1YEN~!AnA-:P:}!B<<+-O sysinstall u{|!!ACUR]<<U:A^2^3ae!C

   ^1IS:I 2-3. ?i 3/4U:DEGeS:O

   ^1IS:I 2-4. A-:P:} Sysinstall u{|!

   |bYENDue+-?i 3/4U: Exit Install!A
   +-uCURU"OA^3,O.|YENX^2{YENHCURUDEGT(R)S:!G

                       User Confirmation Requested
          Are you sure you wish to exit? The system will reboot
            (be sure to remove any floppies/CDs/DVDs from the drives).

                             [ Yes ]    No

   Y<<o:CURU [ Yes ]
   CURS:<<a!A<<oS:NCURFS:aYENu-oD-DEGhYENX"O-a-o,U:!A
   "-o>>ouYENCURU<<P:} 3/4-:<<aCURS.||A|,+-ODEGE|w,Eu{|!CURF!C

   YS:ANOTOYENI-oICURuP:} 3/4-:-a-o,U:!A"-o>>o<<P:} 3/4-:CURS:<<e!A
   1/2D-DEGO+-oYENyDEGhYENX boot.flp CURuS:a!C

     --------------------------------------------------------------

2.5. CURP:^2D- Sysinstall

   sysinstall NOTO FreeBSD p^1-o(c)O'-L-"N-a-o|w,Eu{|!!C
   YEN|NOTOYENHCURaa|r 1/4O|! 3/4THS:@CURe|!NOTDEGYEND!ACURANOTDEG'X
   1/4h?i^3ae!Bue+-!AYENHAAy+-zP:i|ae|w,E!C

   sysinstall ?i^3aeYENDnYENNCURe|VAa:!B Enter!BTab!BSpace
   YENHCURI"a:YENL<<o:Aa:"OP:i|ae 3/4THS:@!A |b sysinstall
   YENDue+--a-o Usage CUR-o|^3^3o"C,Aa: 1/2L
   3/4THS:@CURW-a-o>>!(c)u!C

   nNOTd 3/4\^3o"C,>>!(c)u!A 1/2D-+-N'aa 1/4D-^2 3/4"`i
   Usage!AuM<<a?i [Select] !A^3o(R)ES:Aue+-A^3,O.|-ao/^1^3 ^1IS:I
   2-5!A+-uuU 1/2D-<<o: Enter Aa:!C

   +-uCURU"O!A.|YENX^2{|w,E-a-o"IYENI>>!(c)u!A 3/4\AA-aS:^1^2|
   1/2D-<<o: Enter YENH,o|^YENDue+-!C

   ^1IS:I 2-5. ?i 3/4U: Sysinstall
   YENDue+--a-o!yUsage(S:O:^3t>>!(c)u)!z

     --------------------------------------------------------------

  2.5.1. ?i 3/4U:!y Documentation(>>!(c)uCURaaYENo)!z?i^3ae

   |bYENDue+-YENICURe|VAa:?i 3/4U: Doc!AuM<<a<<o: Enter Aa:!C

   ^1IS:I 2-6. ?i 3/4U:!yDocumentation(>>!(c)uCURaaYENo)!z?i^3ae

   ^3o(R)E.|YENX^2{>>!(c)uCURaaYENo-a-o?i^3ae!C

   ^1IS:I 2-7. Sysinstall -a-o>>!(c)uCURaaYENo(Documentation)?i^3ae

   3/4\AA-a^3o"C,>>!(c)uCURaaYENo<<U:<<n!C

   n 3/4\AA-aCURaaYENo-a-o,U:!A 1/2D-YENICURe|VAa:?i"un
   3/4\AA-a-a-oCURaaYENouM<<a<<o: Enter
   Aa:!CAA-aS:^1<<a!A|A<<o:CUR@|, Enter
   Aa:'N.||^"`i>>!(c)uCURaaYENoue+-CURF!C

   Yn|^"`iYENDue+-!AYENICURe|VAa:?i 3/4U: Exit uM<<a<<o:CURU Enter
   Aa:S:YYENi!C

     --------------------------------------------------------------

  2.5.2. ?i 3/4U:!yAa: 1/2L^1iA^3!z?i^3ae

   |p-aGnS:iAAU:Aa: 1/2L<<o:Aa:-a-o^1iA^3 1/4O|!!A
   1/2D-|bYEND?i^3ae?i"u Keymap uM<<a<<o: Enter Aa:S:YYENi!C
   CUR@-e+-!-apCURUNOTOCUR-L-YENIYENhS:i!A DEG-L-<<DS:AYENI-a-oAa:
   1/2LCUR-L-NOTOCUR@-e 1/4D-.C,(c)I<<DNOTu:|!Aa: 1/2L!C

   ^1IS:I 2-8. Sysinstall YEND?i^3ae

   +-zYENiYENH"IYENICURWCURUAa:^2 3/4DEGE"`i+-z.Q"IYENI-a-oAa:
   1/2L^1iA^3CURe|!!AuM<<a<<o:CURU Space
   Aa:YENH?i"uYEN|!F|A<<o:CUR@CURU Space
   Aa:YENiYENH"u(R)o/?i"u!C.i+-zS:^1|"<<a!A 1/2D-?i 3/4U: [ OK ]
   uM<<a<<o: Enter Aa:S:YYENi!C

   |b^3oOue+-AAaYENU:-a-oYENuNOTO"a:CURCURCUR@CURp^3!CURA!F
   YYENunYENI^1w^3]Aa: 1/2L^1iA^3CURe|!'N|n-a-o,U:!AYENiYENHYENI Tab
   "O?i [ Cancel ] ^3o 1/4E'N.|-ad-|^YENDue+-!C

   ^1IS:I 2-9. Sysinstall Aa: 1/2L^1iA^3?i^3ae

     --------------------------------------------------------------

  2.5.3. |w,E?iP:u-a-o^3](c)wue+-

   1/2D-?i Options uM<<a<<o: Enter Aa:!C

   ^1IS:I 2-10. Sysinstall YEND?i^3ae

   ^1IS:I 2-11. Sysinstall ?iP:u^3](c)w

   ^3q+-`!A"IYENI-aICURj|hYENI^1w^3]E'NYENiYENHCURF!A|OCUR-L-YENI
   *S:iYEN|I!C |O Release Name
   -a-o|aCURe<<h"IS:A(c)O|w,E-a-o-a(c)YEN>>|O|^3(c)OCUR-L-|P!C

   |OYENO/<<e(c)O?i-a-o-a-oP:uYENO/!A.||bue+-CURUCUReYENHAAA(c)^3YENO|rAAaYENU:>>!(c)u!C
   -a`.N!G"a:CURCURYENkAa:^3I<<a-a-o?iP:uNOTO Use
   Defaults("IYENI^1w^3]E)
   !A+-zYENiYENHAC,YENN|^1?iP:u+-N(c)O|^3-a-o^3](c)wAU`iNOTDEG^1w^3]E!C

   YENtYEN~!AYENiYENH<<o: F1 Aa:"O 3/4\AA-a|U?iP:u-a-o>>!(c)u!C

   |O<<o: Q Aa:<<hNOTOYENiYENH|^"`iYENDue+-!C

     --------------------------------------------------------------

  2.5.4. P:}(c)lP:i|ae 1/4D-.C,|w,E

   Standard( 1/4D-.C,)|w,E 3/4AYENI(c)o"-o"C,-a`i+-' UNIX (c)I
   FreeBSD -a-o"IYENI-aI!CYENICURe|VAa:?i 3/4U: Standard uM<<a<<o:
   Enter Aa:S:YYENiP:}(c)lP:iCURJ 1/4D-.C,|w,E!C

   ^1IS:I 2-12. P:}(c)lP:i|ae 1/4D-.C,|w,E

     --------------------------------------------------------------

2.6. uw-oD--aAAP:!-a-oCURADEGt

   +-z-a-o^2A:CUR@OYENoDEGE'NNOTOn"M(c)wCURADEGtu^1 FreeBSD
   YENI-a-o-oI-oD--aAAP:!!Blabel!A YENH<<K sysinstall
   ADEGS:ADEGuNOTUAo:.C,^3AEDEGES:@!C |]|^1!AS:AYEN^2P:.YENy^1i
   FreeBSD NOTO|p|o 1/2T>>{-oI-oD--a-oNOTyu{|^3O.S:(c)A!C

     --------------------------------------------------------------

  2.6.1. BIOS -oI-oD- 3/4-: 1/2s,^1

   |b|w,E!B^3](c)w FreeBSD
   CURS:<<e!A|^3<<U:<<n-a-oCUR@AIYEN^2P:.-a`.N!A CUR
   *"a:.i+-z|^3^3\|hAuuw-oD--a-o(R)EO!C

   |b PC NOT[-oc!A.i+-zP:]^1^3 MS-DOS (c)I Microsoft Windows
   ^3o-oO/,o BIOS ^3](c)wNOTUAo:-a-oS:@.~"t^2I!A BIOS "-oAa:YENiYENH
   1/2O 3/4aYEN?+-`-a-o-oI-oD-
   3/4-:P:P:S:C,!AuM<<a^3o"C,S:@.~"t^2I.|,ouU BIOS DEGuS:iAAU:!C
   ^3oAAy"IYENI-aICUR-L-CUR@(c)w<<D+-onYENN(c)O? *-a-o !S:primary
   master!" uw-oD-P:} 3/4-:!C
   |^3CURHuo^2{^3IA^2^3ae!B<<K(c)y-a-o^3AEYEN-:"t^2ICURe|!!A'NNOTO|AYENhP:RCUR@AuCUR@
   1/4OCUR@ 1/4E-a-ouw-oD-!A uM<<a(c)w'A"IYENI   Ghost(R) (c)I XCOPY
   YENH+-N,e(R)AE+-q^2A:CUR@Auuw-oD-
   1/2AE>>s"`i^2A:CURGAuuw-oD-CURW+-YENh!C
   (c)OYENH!A.i^2A:CUR@Auuw-oD-+-
   3/4CURF(YENi-`aNOTO-fNOTr(c)IAay^3y|"-a-o)!A 'NYENiYENH>>'AP^3z^1L
   1/2O 3/4a BIOS CURCUR-a-oP:} 3/4-:P:P:S:C,!A |O-a
   1/2+-uYENI^2A:CURGAuuw-oD-P:} 3/4-:!C ^3o,o+-N
   3/4-:'ss(c)iP:}!AS:a^2A:CURGAuuw-oD-,o^2A:CUR@Au^1i 1/2O(n 1/2O
   jumper)|^3|P 1/4E-a-o(R)A:-aG!A (R)tS:O'NNOTO!GCUR-L-YENI(c)i
   3/4-:'ss!C

   |^1YEN~!AY,E|^3CURn,uP:Q-a-o SCSI YENd"t^2I!A^3q+-`YEN>>"CUR]|^3
   BIOS -a-oYEN\-`a"OAAy SCSI ^3]^3AE(^3I|hYENi"`i 7
   O)^1F"`iAth|u:S:iAAU:P:P:S:C,-a-oYEN\-`a!C

   ^2ss-oDCURWzCURe|!-a-o"IYENI-aI<<U:YENi-`a.|.P"`iAAaa^3Y!A|]NOTDEG|b
   FreeBSD CURCUR"A<<D|p|^1!A FreeBSD CUR-L-.|DEGN|O BIOS
   ^3](c)wE!A|OYENBCUR]CUR-L--`aDEG>>'u !S:logical BIOS drive
   mapping!" ^3](c)w!C
   ^3o.|AAyCURH.PA:+-<<U:-oA'b!A(c)u(c)u'NNOTOCUR@ 1/4E-a-ouw-oD-!A
   |OYENB,e(R)AECUR]S:^1YENth+-qYENtCUR@Au
   1/2AE>>s^1L"O!Au^2-aG<<o"S?`i-ak^1^3YENH<<e"-o 1/4EYENI!C

   "IYENI FreeBSD -a-o(R)EO!A 1/2D-+-N BIOS CURCUR-a-ouw-oD-P:}
   3/4-:P:P:S:C, 1/2O|^`iYEN>>YEN?+-`-a-oP:P:S:C,!A
   "AYENBYENH<<aCUR-L-n|AS:i^3o^3](c)w!C|p-aG+-z>>YnCURA'<<uw-oD-P:P:S:C,-a-o,U:!A"-o
   1/2D-YENIuwAAeCURe|!!A -a 1/2+-uYEN'P:} 3/4-:'ss!A 1/2O jumper
   CURI+-AE 1/2uS:YYENi!C

+--------------------------------------------------------------------------+
|CUR@NOTqCURpNOTG"AE!GBill CURI Fred -a-o|w,E 3/4uAI                       |
|                                                                          |
|CURn-o,(Bill)YEN'-oaADEG|o|C 1/4w(Fred)S:aAA-a-o Wintel  3/4-: 3/4^1A:e   |
|FreeBSD!C YENL|bCUR@Au SCSI uw-oD-(ID NOTO 0),ECURW FreeBSD!C             |
|                                                                          |
|(c)oNOTO|o|C 1/4wP:}(c)lYENIYENL.s-a-o FreeBSD                            |
|"t^2I!F|yNOTO^1LCURF'XCURN!AYENLuo^2{^3oAu SCSI                           |
||Nuw-oD-uoYENI^3\|hCURpDEGYAD!C                                           |
|CURS:<<a!AYENL'N,oCURn-o,>>!DEG_^3oYENo"AE!C                              |
|                                                                          |
||^1"AE,g^1L'XCURN<<a!ACURn-o,"M(c)wNOTO,O,N"MDEGYAD-a-o(R)EOCURF!A        |
|(c)OYENHYENL+-q<<a+-(c)D-P:!-a-ouw-oD- !S:|NOTAADEGI!"                    |
|CUR-o(R)^3YENXCUR@OCUR@ 1/4OCUR@ 1/4E-a-ouw-oD-!A"AYENB,g^1L-a`i"B surface|
|+- 1/2-oE'u,O<<a!A                                                        |
|AAaYENU:^3oAuuw-oD-AUYENi^3oYENI!A|]|^1!ACURn-o,+-NYEN|-a-o ID  1/2O|" 4!A|
|uM<<a|w,E"`i|o|C 1/4w-a-o 3/4-: 3/4^1!A "AYENB+-N,e(R)AE+-q-oI-oD- 0      |
|1/2AE>>s"`i-oI-oD- 4!C                                                    |
|^2{|b.suw-oD-,E|nCURF!A|OYENBNOTYDEG_"O|n^1^3CUR@CURAYEN?+-`!F            |
|(c)OYENH!ACURn-o,>>{NOTDEG^2{|bA^3,OYENiYENHP:}(c)lYENIYEN|CURF!C         |
|(c)oNOTO"`i SCSI BIOS CURCUR^3](c)w SCSI ID 4 NOTDEGP:} 3/4-:-oD-!A       |
|YENI-oI-oD- 4 <<.sP:} 3/4-:<<a!AFreeBSD CUR@CURAP:]+-o<<U:P:P:S:Q!C       |
|                                                                          |
||o|C 1/4wA:~A:oYENICURF'XCURN<<a!ACURn-o,,o|o|C                           |
|1/4w"M(c)wn"O-a+-AI.s-a-o!G ,OuUCURE-AA FreeBSD NOTYNOTY!C CURn-o,+-N ID 0|
|-a-ouw-oD-^2 3/4DEG-L-(|]NOTDEG|^3DEGYAD)"AYENBCURS+-q !S:|NOTAADEGI!"    |
|CURCUR(R)^3CURFCUR@AuCUR@ 1/4E-a-ouw-oD-"O!C uM<<aYENLYENI|o|C 1/4w-a-oP:}|
|3/4-:-oICURu^3z^1L FTP CURe|!+-N|b^3oAuuw-oD-CURW,ECURF.s-a(c)-a-o        |
|FreeBSD!A|w,E^1Lu{^3-L-<<U:P:P:S:Q!C                                      |
|                                                                          |
||o|C 1/4wYENICURF^3o.s-a(c)YEN>>'XCURN<<a!AA:+-+-oYEN|<<U:                |
|3/4A|XYENI|bCURuu{^3!-au...                                               |
|NOTO(R)EO+-NYENH<<e(c)n|bAA"t^2I-a-oCURuS:@,e(R)AE 1/2AE>>s^1L"OCURF!C    |
||]|^1!A|o|C 1/4w+-N ID 4 -a-o SCSI uw-oD- (,I+-|^3(c)n+-qAA"t^2ICURCUR    |
|1/2AE>>s^1L"O-a-o^3I.s,e(R)AE)YENy mount DEG_"O!A u^2-aG^3-ouMuo^2{|b ID 4|
|-a-ouw-oD-CURW!AYENLYENH<<e-a-o(c)O|^3,e(R)AE^3-L-CUR-L-"-L-CURF!I        |
|                                                                          |
|(c)_(c)C,!A,e(R)AE"`i(c)^3NOTOP:]"`ith,IYENhCURF(c)O!H                    |
|                                                                          |
|`i"O!A.i-a`iCURn-o,+-N ID 0 uw-oD--a-o,e(R)AE 1/2AE>>s"`i ID 4            |
|uw-oD--a-o(R)EO!A ID 4 'NAAU:|" !S:.s-a-o 1/2AE>>s<<~(new clone)!"!C      |
||O.iYENL 1/2O SCSI BIOS ^3](c)w ID 4 NOTDEGP:} 3/4-:-oD-!A.QAAy"t^2I+-q ID|
|4 P:} 3/4-:!A ^3o"BAEJ"a:^1eYENuNOTOYENL|UCURv.d^2VCURF!A                 |
||]NOTDEGCURj^3!CURA-a-oS:@.~"t^2IYENiYENHAC,YENN 1/2O BIOS                |
|^3](c)wYENHS:iAAU:P:} 3/4-:P:P:S:C,!A |yNOTO FreeBSD <<o.|S:aP:}          |
|3/4-:P:P:S:C,AU`i|"YEN?+-`-a-o 1/4O|!!A |]|^1!A|o|C 1/4w-a-o FreeBSD      |
|AUNOTO+-q^3I-a`i-a-o"-oAu ID 0 uw-oD-P:} 3/4-:-a-o!C                      |
|"AE^1eCURW!A(c)O|^3-a-o,e(R)AE^3-L-AU|bNOTG"AE^3I-a`i-a-o"-oAuuw-oD-CURW!A|
||OCUR-L-NOTO|bYENL.Q^1^3CURCUR-a-o ID 4 uw-oD-!C                          |
|                                                                          |
|S:UI<<U:DEG-a?^3|buo^2{^3oYENo"AE(R)E!A"-o"C,,e(R)AE^3-L-AU|b!A           |
|S:UIS:a,e(R)AE+-q^3I-a`i-a-o"-oAu ID 0 uw-oD-"uYENX"O"AYENaeAUu^1|o|C 1/4w|
|(|OYENBCURn-o,CUR]+-q|^1AA,NCURF 0 -a-o<<n....)!C                         |
|                                                                          |
|Ao:uMS:UI^3oAa:-a-o"OCURlNOTOYENI SCSI uw-oD-!A                           |
||yNOTONOTU|P-a-oAE[(c)ACUR]YENiYENH(R)MYENI|b IDE uw-oD-CURW!C            |
+--------------------------------------------------------------------------+

     --------------------------------------------------------------

  2.6.2. YENH FDisk "O<<O/YENssCURA^3I-oIDEGI(Slices)

     -a`: |b^3o(R)EO+-z(c)ODEGu-a-oAAU:S:o^3-L-AUCUR-L-.|-uYEN?
     1/4gCURJuw-oD-CURCUR!C
     |p-aGS:Auo^2{S:E?uCURF!A.Qn<<"OCUR@^1M-a-o,U:!A
     YENiYENHYENI?i^3ae"OA-:P:} sysinstall!A (c)INOTO<<o: U Aa:"O
     Undo(|^'_) (c)O|^3^3](c)w!C |p-aGS:AS:EP:ACURF|OYENBCUR-L--a
     3/4^1D<<c,>>oA-:P:}!AS:AYENiYENH-a 1/2+-u+-N^1q,-L-^1q. 1/2Ao:+-
     1/4|A<<"O!C

   |b sysinstall YENDue+-?i 3/4U:"IYENI 1/4D-.C,|w,E<<a!A
   A^3,O.|NOTY"`iCURU+--a-oDEGT(R)S:!G

                                  Message
  In the next menu, you will need to set up a DOS-style ("fdisk")
  partitioning scheme for your hard disk. If you simply wish to devote
  all disk space to FreeBSD (overwriting anything else that might be on
  the disk(s) selected) then use the (A)ll command to select the default
  partitioning scheme followed by a (Q)uit. If you wish to allocate only
  free space to FreeBSD, move to a partition marked "unused" and use the
  (C)reate command.
                                 [  OK  ]

                       [ Press enter or space ]

   ^3o(R)E 1/2D-"Iue+->>!(c)u!A<<o: Enter Aa:!C
   uM<<a.|NOTY"`iCUR@O|C-ai!ACURW+-.||CYENX(c)O|^3|bDEG>>'uuwAAe(R)E(c)OS:a:"`i-a-ouw-oD-!C
   ^1IS:I 2-13  1/2d"OAAaYENU:-a-oNOTO|^3S:a:"`i"aO IDE -oI-oD-
   3/4-:-a-o+-!S:I!A^3o"aO-oI-oD- 3/4-:CURAS:ONOTDEG!G ad0 >>P ad2!C

   ^1IS:I 2-13. ?i 3/4U: FDisk nCURA^3I-a-ouw-oD-

   S:AYENi-`a.||n(c)_!ANOTDEG|o ad1 "S|C|b^3o,I!C
   NOTDEGCURDEG>>o.|CUR-L-"-L-CURF(c)O!H

   ,O.Q!A|p-aG+-z|^3"aAu IDE uw-oD-!ACUR@ONOTO primary
   master!ACUR@ONOTO secondary master!A^3o
   1/4E.|uoYENICURDEG>>o"AE(c)O!H |p-aG FreeBSD
   "I.OS:a:"`i-a-oP:P:S:C,"ONOTDEGYENLI(c)R|W!A CURn|p-oYENyNOTO ad0
   |A"ONOTO ad1 "-o>>o'NCUR-L-.|YENX^2{S:xAZ!C

   |yNOTO!A^2{|bDEGYAD"OCURF!C|p-aG+-z^2{|b.Q|b primary slave
   YEN[,E^2A:CURTAuuw-oD-!A "-o>>o^3oAuuw-oD--a-o|W-oU'N.|NOTO
   ad1!ACURS:<<e`iYEN>>-a-o ad1 'N.|AAU:|" ad2!C ^3o
   1/4E.|^3y|"CURDEG>>oDEGYAD(c)O!H
   |]NOTDEGuwAAe^3]^3AE-a-o|W-oU(^1^3NOTO
   ad1s1a)NOTOYENI"O'MS:a:AE(R) *"t^2I-a-o!A
   |]|^1+-zYENi-`a.|NOTd-uMuo^2{!A|^3"C,AE(R)
   *"t^2I+-q|^1uL-akYEN?+-`AAaYENU:!A YEN^2P:. *S:i FreeBSD
   ^3](c)w(/etc/fstab)CUR~YENiYENHYEN? 1/2TAAaYENU:!C

   NOTDEGCURF,N"M^3oODEGYAD!A|b^3](c)w kernel (R)EYENiYENH+-A:YENI
   IDE uw-oD-(c)O|b-a-o|`i,m"O(c)R|W!A|O<<D(R)U
   3/4US:a:"`i-a-oP:P:S:C,!C "IYENI^3o-oO/CURe|!-a-o,U:!A |b
   secondary master -a-o IDE uw-oD-'NYENA>>..|NOTO ad2!A
   S:Y"I"t^2ICURCUR"A"S|^3 ad0 (c)I ad1 CUR]CUR-L-"u: 1/4vAAT!C

   YENN(c)o|^1NOTDEG FreeBSD kernel
   ^1w^3]^3](c)w!ACUR]'NNOTONOTDEG|oCURWzue+-YENuAAaYENU: ad0 CURI
   ad2 CURS:NOTG!C ue+-CURW^3oYENx 3/4-:
   3/4^1-a-o"aAuuw-oD-NOTOCURAS:O,E|b primary YENHCURI secondary +-AE
   1/2uCURW-a-o master!A^3o"aAu^3-L-"S|^3,E|b slave CURW!C

   1/2D-?i|n.Q|w,E FreeBSD -a-ouw-oD-!AuM<<a<<o:CURU [ OK ]!C
   +-uuU'N.|P:}(c)l FDisk!AuM<<a.|NOTY"`iAth|u: ^1IS:I 2-14
   -a-oue+-!C

   FDisk -a-oAAaYENU:ue+-CURANOTDEGCURTO^3!CURA!C

   ^2A:CUR@^3!YEN-:NOTOue+-^3ICURWCURe-a-o<<e"a|ae!A^3o,I.|AAaYENU:YENO/<<e(c)O?i-a-ouw-oD-,eDEGT!A
   YEN]NOTAYEN||b FreeBSD -a-o|W-oU!Buw-oD-
   geometry!Buw-oD-A`(R)eP:q!C

   ^2A:CURG^3!CURA.|AAaYENU:YENO/<<e(c)O?i-a-ouw-oD-CURW|^3th"C,
   slice YENHCURI|U slice -a-oDEG_YEN 1/2|`i,m!B
   (c)O|u(R)eP:q!BFreeBSD |W-oU!B'yz>>!(c)u!BCURlAthS:O(sub-type)!C
   "OCURlCURCURAAaYENU:YENX|^3 2 OCURp-a-o"AYENB(c)|YEN 1/4"IYENI-a-o
   slice!A^3oNOTO"u:"`i PC -a-ouw-oD-YEN>>"NOT[-oc 1/4vAATCURS:NOTG!C
   |^1YEN~!A AU|^3CUR@OCURj-a-o FAT slice(^3q+-`NOTO MS-DOS / Windows
   CURCUR-a-o C:)!AYENHCURICUR@O(c)u|u-oI-oD-CURA^3IDEGI (|b MS-DOS /
   Windows CUR-o-a-o"a:YENL-oI-oD-YENN,^1)!C

   ^2A:CURT^3!CURA<<hAAaYENU: FDisk YENiYENI-a-o<<u:YENO!C

   ^1IS:I 2-14. (A|"O)YEN 1/4 1/2s?e<<e-a-o Fdisk
   CURA^3IDEGI(Partition)

   +-uCURU"OnDEGu-a-o"AE!A,o+-zn<<c,>>oCURA^3Iuw-oD-|^3Ao:!C

   YnAAy FreeBSD "IYENI 3/4aAuuw-oD-(uy<<a-a-o|w,E.||An+-z
   1/2T>>{YENH sysinstall "OA:~A:o|w,E!A
   'N.|^2MDEG-L-,Ouw-oD-CUR-oCURW-a-o,e(R)AE)!A"-o>>o'NYENiYENH<<o: A
   Aa:( Use Entire Disk)!AYENHS:RDEG-L-(c)O|^3NOTJ|s-a-o slice!A
   "u|OYENNCURS:-a-oNOTOCUR@OCURp-a-o"A 1/4D-YENU:NOTDEG unused(|P
   1/4E-a-o!A^3oCUR]NOTO PC uw-oD-NOT[-oc(c)O^3y|")-a-o
   slice!AYENHCURICUR@OCURj-a-o FreeBSD slice!C CURS:<<a!A 
   1/2D-YENICURe|VAa:S:aYENu'I^2 3/4|U:,O FreeBSD slice!AuM<<a<<o: S
   Aa:YENH<<K+-N|^1 slice  1/4D-NOTDEGP:} 3/4-: slice!C
   |^1(R)E-a-oue+-A^3,OAth|u: ^1IS:I 2-15!C  1/2D--a`.N!G |b Flags
   A:ae|`i-a-o A E-aiYENU:,O slice A:Y(c)o active!ACUR].|YENN|^1
   slice "OP:} 3/4-:!C

   YnS:RDEG-L-^2{|^3 slice YENH(R)?YENX-aAAP:!u^1 FreeBSD
   "IYENI!AYENiYENHS:aYENu'I^2 3/4"`inS:RDEG-L--a-o slice <<a<<o: D
   Aa:!AuM<<a|A<<o: C Aa:!A |^1(R)E.|YENX^2{^1i,U:(R)O/!A
   1/2D-?eCURJn.s 1/4W-a-o slice CURjCURpNOTDEG|o!A?eCURJ|X
   3/4ACURjCURpCURS:<<a<<o: Enter Aa:S:YYENi!C
   ,O^1w^3]ENOTDEGYENiCURADEGt-aAAP:!-a-o^3ICURjE!A
   YENiYENHNOTO^3ICURj-a-o(c)I(c)|YEN 1/4CURADEGt-a-o
   3/4aAuuw-oD-CURjCURp!C

   YCURw<<O/YENssS:^1^2|u^1 FreeBSD -a-o-aAAP:!(^3z^1LAth|u:
   PartitionMagic CURS:Ath-a-oCURu"a)!A"-o>>oYENiYENH<<o: C Aa:YENH.s
   1/4W slice!C|P 1/4ECUR].||^3^1i,U:(R)O/YENX^2{!A"ODEGY.Qn.s
   1/4W-a-o slice CURjCURpNOTDEG|o!C

   ^1IS:I 2-15. Fdisk +-A:YENI 3/4aAuuw-oD-S:@CURA^3IDEGI(Partition)

   S:^1^2|<<a 1/2D-<<o: Q Aa:!C ^3o"C,S:oS:i.| 1/4E|su^1 sysinstall
   "IYENI!A|yAUCUR-L-.|-uYEN? 1/4gCURJ"`iuw-oD- !C

     --------------------------------------------------------------

  2.6.3. |w,E Boot Manager

   ^2{|bYENiYENH?i 3/4U:NOTOS:_n,E boot manager!C CUR@-e|O"YEN!A
   ^1J"`iCURU|C+-!-apCUR~.|>>Yn,E boot manager!G

     * |^3CUR@OYENHCURW-a-ouw-oD-!A|O FreeBSD
       "A<<D,E|b^2A:CUR@Ouw-oD-CURW!C

     * |PCUR@Auuw-oD-CURWDEG-L-CURF|^3,E FreeBSD
       CURS:YEN~!AAU|^3,E"a:YENLS:@.~"t^2I!A (c)OYENH>>Yn|bP:}
       3/4-:(R)E?i 3/4U:nP:iCURJthOS:@.~"t^2I!C

   YYENu,E FreeBSD!A"AYENBNOTO,E|b^2A:CUR@Auuw-oD-!A"-o>>o?i Standard
   S:YYENi!C YCURw,g|^3"IYENI"a:YENL-a-o boot manager YENiP:}
   3/4-:P:iCURJ FreeBSD "-o>>o 1/2D-?i None S:YYENi!C

   1/2D-"I|U">>Y"D>>P+-!-apDEGuS:`a 3/4U:!AuM<<a<<o: Enter Aa:!C

   ^1IS:I 2-16. Sysinstall -a-o Boot Manager ?i^3ae

   <<o: F1 .||^3CUR-L-|PS:@.~"t^2I|@|s(R)E!A
   |^3YENi-`a^1J"`i-a-oNOTUAo:DEGYAD>>!(c)u!C

     --------------------------------------------------------------

  2.6.4. |b"a:YENLuw-oD-CURW<<O/YENssCURA^3I-oIDEGI(Slices)

   Y|^3CUR@OYENHCURW-a-ouw-oD-!A"-o>>o|b?iS:^1 boot manager
   CURS:<<a.||A|^"`i?i 3/4U:uw-oD--a-oue+-!C YnS:a FreeBSD
   ,E|b|hOuw-oD-CURW!A "-o>>oYENiYENH|b|^1?i 3/4U:"a:YENLuw-oD-!A"A<<
   1/2AE"IYENI FDisk "O<<O/YENss slice !C

     <<n: Y^2A:CUR@Auuw-oD-CUR-L-NOTO,E FreeBSD
     -a-o,U:!A"-o>>o"CCUR@Au'Nn^3-L-,E FreeBSD boot manager
     CUR~YENiYENH!C

   ^1IS:I 2-17. A-:P:}!y?i 3/4U:uw-oD-!zue+-

   Tab Aa:YENiYENH|b^3I<<a?i 3/4U:-a-ouw-oD-YENHCURI [ OK ]!B
   [ Cancel ] CURS:P:!P:i|aeCURA'<<!C

   YENy<<o:CUR@|, Tab .|YENy^2 3/4"`i [ OK ]!AuM<<a|A<<o: Enter
   Aa:YENHA:~A:o|w,E!C

     --------------------------------------------------------------

  2.6.5. YENH Disklabel "O<<O/YENssCURA^3IDEGI(Partitions)

   ^2{|bYEN^2P:.|be<<O/YENss|n-a-o slice ^3W^1-oCUR@"C,CURA^3IDEGI!C 
   1/2D--a`.N!G "COCURA^3IDEGI-a-oYENN,^1NOTO+-q a "`i h!A |^1YEN~
   b!Bc!Bd ^3q+-`NOTO-S(R)iYENI^3~!ACUR-L-,OAH.NAAU:DEGE!C

   |^3"C,u{|!YENiYENH^3z^1L-S(R)i-a-oCURA^3ICURe|!|O^1F"`iS:o|n-a-o(R)A:-aG!A
   CUR *"a:NOTOCURA^3IDEGINOTOCURA'^2|bCUR-L-|Puw-oD-CURW-a-o(R)EO!C
   |yNOTO!A^2{|bNOTO+-z^2A:CUR@|,,E FreeBSD!A (c)OYENH
   1/2D-CUR-L-nYENh.D-'o,O|p|oCURA^3Iuw-oD-CUR~|n!C
   ^3I<<n-a-oNOTO!A,E|n FreeBSD uM<<a 3/4C,^2ss|p|ou 1/2YENICURS:!C
   .i^1i FreeBSD |^3CUR@(c)wu{<< *-a-o
   1/4o+-xCURS:<<a!AYENiYENHAH(R)E<<,E
   FreeBSD!A"AS:iAAU:CURA^3I-a-oCURe|!!C

   CURU+-"OCURl|^3YEN|OCURA^3IDEGI !X!X "a:CURCURCUR@ONOTO swap
   -aAAP:!!Ai "a:YENLCURTONOTOAE(R) *"t^2I!C

   -ai(R)ae 2-2. ^2A:CUR@Auuw-oD--a-oCURA^3IDEGI(Partition)DEGt,m

CURA^3IDEGI AE(R)        CURjCURp                                  CURP:^2D-                            
            *"t^2I 
                                         |^1NOTDEG(R)UYENO/?yAE(R) *"t^2I(root filesystem)!C            
                                         "a:YENL-a-oAE(R) *"t^2I^3-L-.|+-                               
                                         3/4,u:|b(R)UYENO/?yCURS:CURU!C 128 MB ^1i(c)o|^1AE(R)          
                                         *"t^2I"O>>!NOTONOTU.i|X^2z-a-oCURjCURp!A                       
a           /      128 MB                |]NOTDEG^3q+-`^3o,I"ACUR-L-.|(c)nCURO|h,e(R)AE!A|O|b FreeBSD   
                                         ,ES:^1<<a.|YENI"`iNOTu 40 MB -a-o(R)UYENO/?y-aAAP:!!C          
                                         ^3NCURU-a-o-aAAP:!NOTO(c)nA{(R)E,e(R)AEYENI-a-o!A              
                                         |^1YEN~CUR]A^3,On^1w-dCUR@"C,-aAAP:!!A|]NOTDEGCURe<<a-a-o      
                                         FreeBSD -a(c)YEN>>YENi-`a.|>>YnS:o|h-a-o /((R)UYENO/?y)        
                                         -aAAP:! !C                                                     
                                         "t^2I-a-o swap -aAAP:!NOTO(c)n|b b CURA^3IDEGI!C |p|o?i 3/4U:  
                                         3/4A|X-a-o swap -aAAP:!CURjCURpYENiNOTOCUR@-au 3/4C,DEGY!C     
                                         CUR@-e"O>>!!A swap -aAAP:!A^3,ONOTODEGO                        
                                         3/4D-AAe(RAM)CURjCURp-a-o 2 (c)I 3 ?!C |^1YEN~!Aswap           
                                         |U:CURO:>>Yn 64 MB!A|]|^1Y RAM CURp(c)o 32 MB -a-o,U:!A        
                                         1/2D-S:a swap CURjCURp^3]NOTDEG 64 MB!C                        
                                                                                                        
b           N/A    RAM -a-o 2~3 ?        Y|^3CUR@OYENHCURW-a-ouw-oD-!A<<hYENiYENH|b"COuw-oD-^3-L-DEGt,m 
                                         swap -aAAP:!!C FreeBSD .|u 1/2YENI"COuw-oD-CURW-a-o swap       
                                         -aAAP:!!A|p|^1CUR@"O<<K-`a|^3(R)A:'-L-DEG-a swap -a-o(c)E-`a!C 
                                         Y+-zA:Y^3oAth+-!-ap!A 1/2D-YENy-oaYENXA`|@>>Yn-a-o swap        
                                         A`CURjCURp (CURn|p!G128 MB)!AuM<<aDEG-L-YENHYENth^3!-a-ouw-oD- 
                                         1/4AEP:q(CURn|p!G"aAuuw-oD-)!A ^3o                             
                                         1/4E-oaYENX"O-a-ou^2-aG'NNOTO"COuw-oD-CURW(c)O>>YDEGt,m-a-o    
                                         swap CURjCURp!A |b^3oO"OCURlCURCUR!A<<h"COuw-oD-(c)O>>YCURS:   
                                         swap -aAAP:!NOTDEG 64 MB !C                                    
                                         /var YENO/?y.|(c)n-a-oAE(R) *|^3<<U:|h-oO/!A^1^3NOTO log AE(R) 
                                         *YENHCURI"a:YENL-a-o"t^2I-oTH^2zAE(R) *!C ^3o"C,AE(R)          
e           /var   256 MB                *CURj^3!CURA^3-L-NOTO FreeBSD "CCURe^1BS:@(c)O.|AA-a!B 1/4g!C  
                                         S:a^3o"C,AE(R) *YENtYEN~(c)n"`i+-M-au-a-oAE(R) *"t^2I(S:Y      
                                         /var) <<hYENiYENH^3I"ICURAE^3o"C,AE(R) *-a-o|s"u!A             
                                         |OCUR-L-P(c)o 1/4vAAT"a:YENLYENO/?y-a-o|s"u!C                  
f           /usr   ^3N                   (c)O|^3"a:YENLAE(R) *^3q+-`.||s|b /usr                         
                   3/4l-a-ouw-oD--aAAP:! CURI"a:CURlYENO/?yCUR-o!C                                      

   YnS:a FreeBSD
   ,E|b|hOuw-oD-CURW!A"-o>>oYEN^2P:.|b+-z(c)ODEGt,m-a-o"a:YENL slice
   CURW.s 1/4WCURA^3IDEGI!C
   ^3IA^2^3ae-a-oCURe|!!A'NNOTO|b"COuw-oD-CURW<<O/YENssCURA^3IDEGI!ACUR@Ou^1
   swap -aAAP:!!AYENtCUR@O<<hNOTOAE(R) *"t^2I!C

   -ai(R)ae 2-3. "a:YENLuw-oD--a-oCURA^3IDEGI(Partition)DEGt,m

CURA^3IDEGI AE(R)        CURjCURp                                                  CURP:^2D-                                            
            *"t^2I 
b           N/A    1/2D-DEGN 3/4\YENkDEG <<e+-|^3'-L-^1L!Aswap -aAAP:!NOTOYENiYENH,o|Uuw-oD-!C S:Y"I"S|^3"IYENI a                       
                   1/4-a-oCURP:^2D-      CURA^3IDEGI!A|y^2ss-oDCURWAUNOTO.|S:a swap -aAAP:!^3]NOTDEG b CURA^3IDEGI!C                    
                                         ^3NCURU-a-o-aAAP:!NOTOCUR@OCURj-a-oCURA^3IDEGI!A^3IA^2^3ae-a-oDEGu-akNOTO+-NCURS:^3W^1-oNOTDEG 
                                         a CURA^3IDEGI!A|OCUR-L-NOTO e CURA^3IDEGI!C uM|O!A^2ss-oDCURW a CURA^3IDEGINOTO<<O-du^1        
                                         (R)UYENO/?y(/)(c)O"IYENI-a-o!C .iuM!A +-zCUR-L-CUR@(c)wn?i'`|^1^2ss-oD!A|y sysinstall          
e           /diskn ^3N                   YEN>>".|!A(c)OYENH.OYEN|NOTJ|^3-a-oCURe|!.|AAyS:A|w,ES:oYEN[^2M^2n!B 1/4a:^2b!C                
                   3/4l-a-ouw-oD--aAAP:! S:AYENiYENHS:a^3o"C,AE(R) *"t^2I+- 3/4,u:|bYENo|o|aCURe!AYEN>> 1/2d"ONOTO<<O/A:^3S:aYEN|I+-    
                                         3/4,u:(c)o /diskn YENO/?y!A "a:CURCUR-a-o n -a-o 1/4AE|r!A                                     
                                         <<h"I|Uuw-oD--a-oP:P:S:C,|O|^3(c)OAAU:CURAE!C |yY+-zDEG-a?^3!A CUR]YENiYENHS:aYEN|I+-          
                                         3/4,u:(c)o"a:YENL|aCURe!C                                                                      

   S:^1|"CURA^3IDEGIDEGt,mCURS:<<a!A'NYENiYENHYENI sysinstall
   "O<<O/YENssCURS:!C +-z.|NOTY"`i|pCURUDEGT(R)S:!G

                                  Message
  Now, you need to create BSD partitions inside of the fdisk
  partition(s) just created. If you have a reasonable amount of disk
  space (200MB or more) and don't have any special requirements, simply
  use the (A)uto command to allocate space automatically. If you have
  more specific needs or just don't care for the layout chosen by
  (A)uto, press F1 for more information on manual layout.

                                 [  OK  ]
                           [ Press enter or space ]

   1/2D-<<o: Enter Aa:YENHP:iCURJ FreeBSD CURA^3IDEGI 1/2s?e
   3/4^1!AYENsDEGu Disklabel!C

   ^1IS:I 2-18 AAaYENU:^2A:CUR@|,DEGo|ae Disklabel -a-oue+-!A
   ^3oue+-YENiDEGICURANOTDEGCURTODEGIP:o!C

   <<e'X|aeAAaYENU:-a-oNOTOYEN?|b
   1/2s?e-a-ouw-oD-!AYENHCURIYENO/<<eYEN?|b<<O/YENss-a-o slice
   |`i(c)othO CURA^3IDEGICURW!C(|b|^1^3B!ADisklabel NOTO"IYENI
   Partition name(CURA^3IDEGI|W-oU)!A|O<<D slice |W-oU)!C
   |^1ue+-CUR].|AAaYENU:YENO/<<e slice
   AU|^3|hCURO:-aAAP:!YENi"N"IYENI!A '<<YENy,U:>>!'NNOTO(c)|YEN
   1/4<<u:(c)wCURA^3IDEGI-a-o|h 3/4l-aAAP:!!C

   |bue+-CURCURP:!!A<<hAAaYENU:CURw<<O/YENss-a-oCURA^3IDEGI!B"COCURA^3IDEGI-a-oAE(R)
   *"t^2I|W-oU!B (c)O|uCURjCURp!AYENHCURICUR@"C,DEGN 1/4AE!C

   |bue+-CURUCURe!A<<hAAaYENU: Disklabel YENiYENI-a-o<<o:Aa:!C

   ^1IS:I 2-18. Sysinstall -a-o Disklabel  1/2s?e 3/4^1

   Disklabel YENi|UDEGECURADEGtCURA^3IDEGI!A "A
   1/2aCUR(c)^1w^3]ECURjCURp!A<<o: A S:YYENi|UDEGES:^1|"!C
   +-z.|NOTY"`iAth|u: ^1IS:I 2-19 -a-oue+-!C CUR-L-^1L!A
   YENN(c)o(c)OYENI-a-ouw-oD-CURjCURpCUR-L-CUR@!A(c)OYENH|UDEGECURADEGt(c)O^3](c)w-a-oCURjCURpCUR-L-CUR@(c)w|XYENI!ACUR-L-n-oo!A
   +-zCUR-L-CUR@(c)w+-o"IYENI^1w^3]CURjCURpCUR~YENiYENH!C

     -a`: ^1w^3].|u^1 /tmp YENO/?yS:@NOTDEG?WYENssCURA^3IDEGI!A
     |O<<D-athA:Y(c)o / CURS:CURU!C |p|^1CUR@"O!A YENiA *S:K /
     .|^3QCUR@DEGiA{(R)EAE(R) *P:eAz!C

   ^1IS:I 2-19. Sysinstall -a-o Disklabel  1/2s?e 3/4^1 !X
   "IYENI|UDEGECURADEGt

   |p-aG+-zCUR-L-.QYENI|UDEGECURADEGtCURA^3IDEGI|OS:AE+-ae|U|ae^3](c)w!A
   1/2D-YENICURe|VAa:?i 3/4U:^2A:CUR@OCURA^3IDEGI!A"A<<o:CURU D
   S:RDEG-L-CURS:!C << 1/2AE|^1DEGES:@-a
   1/2"`iS:RDEG-L-(c)O|^3CURA^3IDEGI!C

   <<O/YENss^2A:CUR@OCURA^3IDEGI(a!A+- 3/4,u:NOTDEG / !X!X
   (R)UYENO/?y)!A  1/2D-|bue+-^3ICURWCURe?i 3/4U:YEN?
   1/2T-a-o-oI-oD-CURA^3I-oIDEGI(slice)"A<<o:CURU C!C
   +-uCURU"O+-NYENX^2{^1i,U:(R)O/!A
   .|n"D?eCURJ.s-a-oCURA^3IDEGICURjCURp(|p ^1IS:I 2-20 (c)OYENU:) !C
   ^3oAa:YENiYENH-a 1/2+-u?eCURJYENH block NOTDEG^3ae|`i!A
   (c)I-aINOTOYENH M(MB)NOTDEG^3ae|`i!B (c)IYENH G(GB)NOTDEG^3ae|`i!A
   (c)I-aIYENH C(-oINOTW!Acylinders) NOTDEG^3ae|`i!C

     -a`: |U FreeBSD 5.X DEG_!A<<hYENi"IYENI Custom Newfs ?iP:u"OYENI
     UFS2 (+-q FreeBSD 5.1 DEG_!A|^1S:YNOTDEG^1w^3]E)!C YNOTO"IYENI
     Auto Defaults |UDEGE^1w^3]-a-o+-!-apCURU!A<<hYENiYENH|AYENI
     Custom Newfs ?iP:u!A(c)I-aI|b<<O/YENssAE(R) *"t^2I(R)E<<u:(c)w
     -O 2 DEGN 1/4AEYENc,YENi!C YYENI Custom Newfs
     ?iP:u-a-o,U:!A<<hS:OS:NCURFnYEN[CURW -U "O+-OYENI SoftUpdates
     YEN\-`a!I

   ^1IS:I 2-20. (R)UYENO/?y-a-o-aAAP:!CURADEGt

   |^1^3B^1w^3]AAaYENU:-a-oCURjCURp!A.|NOTO 3/4aO slice
   -a-o(c)O|^3-aAAP:!!C
   Yn+-A:YENIYENy<<e"OCURl(c)OCURP:^2D--a-o^1-oCURACURjCURp!A<<h<<o:
   Backspace Aa:"O(R)o/DEG-L-^3o"C, 1/4AE|r!A"A?eCURJ"OCURlCURCUR-a-o
   128M!A|p ^1IS:I 2-21 (c)OYENU:!C +-uuU<<o:CURU [ OK ]!C

   ^1IS:I 2-21.  *S:i(R)UYENO/?y-a-o-aAAP:!CURADEGt

   |b?eCURJCURS:<<a.|DEGY(c)On<<O/YENss-a-oNOTOAE(R) *"t^2I(file
   system)(c)I-aINOTO swap -aAAP:!!A |p ^1IS:I 2-22 (c)OYENU:!C
   ^2A:CUR@O?iP:uNOTDEGAE(R) *"t^2I!A(c)OYENH?i 3/4U: FS
   <<a<<o:CURUEnter!C

   ^1IS:I 2-22. ?i 3/4U:CURA^3IDEGI-a-oAth<<NOT

   ^3I<<a!A|]NOTDEGn.s 1/4W-a-oNOTOAE(R)
   *"t^2I!A(c)OYENHYEN^2P:.S:iP:D Disklabel n+-N"a:+-
   3/4,u:|U:|o^3B!C |p ^1IS:I 2-23 (c)OYENU:!C (R)UYENO/?yAE(R)
   *"t^2I -a-o+- 3/4,u:AINOTDEG /!A(c)OYENH 1/2D-?eCURJ /
   !AuM<<a<<o:CURU Enter!C

   ^1IS:I 2-23. ?i 3/4U:(R)UYENO/?y-a-o+- 3/4,u:AI

   e(c)O<<O/YENss-a-oCURA^3IDEGI.|AAaYENU:|bue+-CURW!AYENiYENHYENICURWzAth|u:DEGES:@"O<<O/YENss"a:YENLCURA^3IDEGI!C
   uM|O|b<<O/YENss swap CURA^3IDEGI(R)E!A"t^2I"ACUR-L-.|DEGYn+-
   3/4,u:(c)othAa:!A|]NOTDEG swap -aAAP:!NOTOCUR-L-YEN^2ABYEN~+-
   3/4,u:-a-o!C |^1YEN~|b<<O/YENss^3I<<aCURA^3IDEGI /usr
   (R)E!AYENiYENH-a 1/2+-u+-A:YENI^1w^3]CURjCURp!ACUR]'NNOTO,O slice
   ^3N 3/4l-a-o(c)O|^3-aAAP:!!C

   ^3I<<a FreeBSD CURW-a-o DiskLabel  1/2s?e 3/4^1ue+-.|Ath|u: ^1IS:I
   2-24!A^1e>>U 1/4AE|r<<h"I|w,E?i 3/4U:|O|^3(c)OCUR-L-|P!C 
   1/2D-<<o:CURU Q S:YYENiS:^1|"CURA^3IDEGI^3W^1-o!C

   ^1IS:I 2-24. Sysinstall Disklabel  1/2s?e 3/4^1

     --------------------------------------------------------------

2.7. ?i 3/4U:.Qn|w,E-a-o

  2.7.1. ?i 3/4U:n|w,E-a-o(R)MYENoP:DEG(Distribution Set)

   n,Eth"C,(R)MYENo!AYENDn"u"M(c)o,O"t^2I-a-oYENI^3~NOTDEG|oCURI-oI-oD--aAAP:!|O(c)w!C
   ^1w,m-a-o(R)MYENo!A+-q^3ICURp|w,E"`iS:^1 3/4a|w,E^3-L-|^3!C YNOTO
   UNIX (c)I FreeBSD .sCURa!A^3q+-`-a
   1/2+-u?i"a:CURCURCURS:CUR@S:YYENi!C |O|Uq(R)MYENoCURn,u
   3/4A|X|^3,gAAc,-a-oCURH"OYENI!C

   YnAA,N|U(R)MYENo-a-o?iP:u^2O,`,eDEGT!A 1/2D-<<o: F1 Aa:!C
   NOTYS:^1CURS:<<a<<o: Enter S:Y.||^"`ieCUR~-a-o(R)MYENo?i
   3/4U:ue+-!C

   Y>>Yn GUI CURP:+-!A"-oYEN^2>>YYEN[?i X P:}AY-a-oNOTUAo:(R)MYENo!C
   |U:(c)o X server
   -a-o^3](c)wCURInYENIthCUR@Ath-a-o(R)`a+--oTH^2z!AYEN^2P:.|b
   FreeBSD ,E|nCURS:<<aCUR~-`aP:i|ae!C X server ^3](c)w^2O,`^3!CURA
   1/2D-DEGN 3/4\ uU 5 ^3^1!C

   ^1w^3]|w,E-a-o X11 -a(c)YEN>>NOTDEG Xorg!C

   Y>>Yn|Uq kernel!A"-o>>o>>YYEN[?i|^3S:t source code -a-o?iP:u!C
   |U:(c)oNOTDEG|o>>Y|Uq kernel CURINOTUAo:^2O,`!A 1/2D-DEGN 3/4\ uU
   8 ^3^1!C

   <<U:(c)uAAa|a!AYENth^3!^3-L-,E'NCUR-L-YENIS:xAZ>>Yn,ECURDEG>>oCURF!C
   Yuw-oD-DEG-:CURj!A 1/2D-YENHCURe|VAa:?i ^1IS:I 2-25 ^1ICURU-a-o
   All ?iP:u!A"A<<o:CURU Enter S:YYENi!C Yuw-oD--aAAP:!CUR-L-DEG-:!A
   1/2D-"I|U">>Y"D?i 3/4U:|w,E!C .iuM|b|w,ES:^1^2|<<a!A
   AUNOTOYENiYENH"I>>Y"D|AYEN[,E"a:YENL(R)MYENo!C

   ^1IS:I 2-25. ?i 3/4U:n,E-a-o(R)MYENoP:DEG(Distributions)

     --------------------------------------------------------------

  2.7.2. |w,E Ports Collection

   |b,ES:^1(R)MYENoP:DEGCURS:<<a!A+-uuU.|DEGYNOTOS:_n,E FreeBSD Ports
   (R)MYENo!C Ports
   (R)MYENoYENiYENHAAy+-z>>'AP|w,E|U-oO/+-`"-L--a-o^3nAAe!AYEN|YEN>>""ACUR-L-S:t"-o"C,^3nAAe-a-o`i(c)l
   1/2X!A |ONOTOCUR@OYEN]S:t|p|o|UDEGECURU,u:!B 1/2sA:P:!B|w,E
   third-party ^3nAAe-a-oAE(R) *P:DEG|X!C uU 4 ^3^1
   .|CURP:^2D-|p|o"IYENI ports!C

   |w,Eu{|!"ACUR-L-.|AENOTdNOTOS:_|^3"NOTDEG-:-aAAP:!"O(c)n ports
   tree!A (c)OYENH 1/2D-YENy 1/2T>>{|^3"NOTDEG-:-aAAP:!!C YENO/<<e
   FreeBSD 9.1 -a-o FreeBSD Ports Collection CURjNOTu>>Yn 500 MB
   -a-o-aAAP:!!C |]|^1!A YENiYENH+-A|oS:o.s-a(c)-a-o FreeBSD
   .|>>YnS:o|h-a-o-aAAP:!"O,E!C

                          User Confirmation Requested
  Would you like to install the FreeBSD ports collection?

  This will give you ready access to over 24,000 ported software packages,
  at a cost of around 500 MB of disk space when "clean" and possibly much
  more than that if a lot of the distribution tarballs are loaded
  (unless you have the extra CDs from a FreeBSD CD/DVD distribution
  available and can mount it on /cdrom, in which case this is far less
  of a problem).

  The Ports Collection is a very valuable resource and well worth having
  on your /usr partition, so it is advisable to say Yes to this option.

  For more information on the Ports Collection & the latest ports,
  visit:
      http://www.FreeBSD.org/ports

                               [ Yes ]     No

   YENICURe|VAa:?i [ Yes ] 'N.|,E Ports Collection!AS:_<<h'N?i [ No ]
   YENH^2CUR^1L!C ?i|n<<a<<o: Enter A:~A:o!A uM<<a.||A|,|^"`i?i
   3/4U:(R)MYENoP:DEG-a-oue+-!C

   ^1IS:I 2-26.  1/2T>>{n|w,E-a-o(R)MYENoP:DEG

   YnCURA:?i-a-oP:uYENO/^3-L-
   1/2T>>{"SDEGYAD-a-o,U:!A'NYENHCURe|VAa:?i Exit DEGhYENX"A 1/2T>>{
   [ OK ] |^3?i"`i!AuM<<a<<o:I Enter A:~A:o!C

     --------------------------------------------------------------

2.8. ?i 3/4U:|w,E"O. 1/2

   Yn+-q CDROM (c)I DVD |w,E!AYENICURe|VAa:+-N'aa 1/4D-^2 3/4"`i
   Install from a FreeBSD CD/DVD!A"A 1/2T(c)w ?i [ OK ] <<a<<o:CURU
   Enter 'N.|P:}(c)l,ECURF!C

   YNOTOnYENI"a:YENL-a-oCURe|!|w,E-a-o,U:!A 1/2D-?i 3/4U:
   3/4A.i-a-o|w,E"O. 1/2!A uM<<a?i.O?A^1o<<u:YENU:P:i|ae|w,ES:YYENi!C

   <<o: F1 YENiYENHAAaYENU:DEGw^1i|^1^3!CURA(|w,E"O. 1/2)-a-o
   1/2uCURW>>!(c)u!C <<o:CUR@CURU Enter 'N.||^"`i!y?i 3/4U:|w,E"O.
   1/2!z-a-oue+-CURF!C

   ^1IS:I 2-27. ?i 3/4U:|w,E"O. 1/2

     FTP |w,E 1/4O|!: "IYENI FTP |w,E-a-o,U:!A|^3CURACURT-oO/
     1/4O|!!JYENDDEGE|!(active)FTP!B ^3QDEGE|!(passive)FTP
     (c)INOTO^3z^1L HTTP proxy server!C

     YENDDEGE|! FTP!G+-q FTP server |w,E

             ,O?iP:u.|^3z^1L !S:Active!"  1/4O|!S:@ FTP
             P:C,?eDEGES:@!C ^3o.|uL-akNOTi^1L"
             3/4CURoAd-!A|yYENiYENI|b"-o"C,,uYENj|!BCUR-L-CURa:'(c)^3QDEGE
             1/4O|!-a-o FTP -,!C Y FTP ^3s
             1/2u.|YENd|i(^1w^3]NOTDEG^3QDEGE 1/4O|!)!A "-o
             1/2D-S:i'<<YENDDEGE 1/4O|!NOTYNOTY!I

     ^3QDEGE|! FTP!G^3z^1L" 3/4CURoAd-!A+-q FTP server |w,E

             ,O?iP:u.|AAy sysinstall YENthu{"IYENI
             !S:Passive(^3QDEGE|!)!" "OP:i|ae FTP ^3s 1/2u!A
             'NYENiYENHNOTi^1LYENuCUR^1^3\"IYENI(c)T(c)w TCP port
             ^3sCURJ-a-o" 3/4CURoAd-!C

     ^3z^1L HTTP proxy -a-o FTP!G^3z^1L http proxy "O+-q FTP -,|w,E

             ,O?iP:u.|AAy sysinstall -a-o FTP ^3s 1/2u!A YENy^3z^1L
             HTTP "o(c)w('N^1^3-ooP:AsA:y 3/4^1CUR@ 1/4E)^3s"`i proxy
             server!A|O proxy server .|,NA:P:DEGe^1L"O-a-o-a-o
             1/2D-"D!AuM<<aA`aDEGeu^1 FTP server!C
             ^3oYENiYENHNOTi^3zYENuCUR^1^3\ HTTP ^3s
             1/2u|yCUR-L-CUR^1^3\ FTP ^3s 1/2u-a-o" 3/4CURoAd-!C
             |yDEGO+-onYENICURS:(R)E!AYEN^2P:.<<u:(c)w proxy server
             -a-o|`iS:}!C

     ^1i proxy FTP server
     |O"YEN!A^3q+-`n|bunCURJYENI-a-o+-b,^1|W-oU<<a+-!A YEN[CURW
     !S:@!" ^2AA,^1|AYEN[CURWnunCURJ-a-o server |W-oU!C uM<<a!A proxy
     server 'N.| !S:fakes(DEGDEG,E)!" NOTDEG-u-a-o server  1/4ECURl!C
     A|O"OCURl!AYn"`i ftp.FreeBSD.org "O,E!A |yCURCURP:!^3z^1L proxy
     FTP server CUR]'NNOTO foo.example.com "AYENB"IYENI port 1234!C

     |b|^1+-!-apCURU!AYENiYENH"`i options ?i^3ae!A+-N FTP username
     ^3]NOTDEG ftp@ftp.FreeBSD.org!A+-K 1/2X<<h^3]NOTDEG|UCURv-a-o
     email <<H 1/2c!C |w,E"O. 1/2^3!CURA!A<<h"IYENI FTP ((c)I proxy
     |^3CURa:'(c)-a-o,U:!A'NYENI passive FTP)!A |O URL <<hYENI
     ftp://foo.example.com:1234/pub/FreeBSD!C

     |]NOTDEG ftp.FreeBSD.org -a-o /pub/FreeBSD .|^3Q porxy "`i
     foo.example.com!A(c)OYENH'NYENiYENH+-q foo.example.com ^3oYENx 
     3/4-: 3/4^1(^3oYENx.|+-q ftp.FreeBSD.org S:`iAE|^"Ou^1+-z)
     |w,E!C

     --------------------------------------------------------------

2.9. P:}(c)lP:i|ae|w,E

   "`i|^1NOTDEGCURi!AYENiYENHP:}(c)lP:i|ae|w,ECURF!A ^3oCUR]NOTO+-zA
   *S:KS:oDEGE"`iuw-oD--a-o^3I<<a 3/4-:.|!C

                        User Confirmation Requested
  Last Chance! Are you SURE you want to continue the installation?

  If you're running this on a disk with data you wish to save then WE
  STRONGLY ENCOURAGE YOU TO MAKE PROPER BACKUPS before proceeding!

  We can take no responsibility for lost disk contents!

                              [ Yes ]    No

   ?i 3/4U: [ Yes ] "A<<o:CURU EnterYENH 1/2T>>{-u-a-onP:}(c)l|w,E

   |w,E(c)O>>Y(R)EP:!.|"I 3/4U(c)O?i
   3/4U:|w,E-a-o(R)MYENoP:DEG(distribution) !B|w,E"O.
   1/2YENHCURI^1q,-L-^3t<< *|O|^3(c)OCUR-L-|P!C
   |b|w,E-a-o^1Lu{CURCUR!A.||^3CUR@"C,DEGT(R)S:AAaYENU:YENO/<<e-a-o|w,EP:i<<
   *!C

   .i+-zNOTY"`iCURU+--a-oDEGT(R)S:-aiYENU:CURw,g|w,ES:^1|"CURF!J

                                Message

 Congratulations! You now have FreeBSD installed on your system.

 We will now move on to the final configuration questions.
 For any option you do not wish to configure, simply select No.

 If you wish to re-enter this utility after the system is up, you may
 do so by typing: /usr/sbin/sysinstall.

                                  [ OK ]

                       [  Press enter or space  ]

   1/2D-<<o: Enter Aa:"OP:i|aeNOTUAo:-a-o<<aA:o^3](c)w!C

   |p-aGe?i-a-oNOTO [ No ] "A<<o:CURU Enter
   Aa:!A"-o>>o.|CURCURA_|w,E('NCUR-L-.|DEGE"`iS:A-a-o`i|^3"t^2I)!C
   +-uuU!A.|YENX^2{YENHCURUDEGT(R)S:!G

                                 Message
 Installation complete with some errors.  You may wish to scroll
 through the debugging messages on VTY1 with the scroll-lock feature.
 You can also choose "No" at the next prompt and go back into the
 installation menus to retry whichever operations have failed.

                                  [ OK ]

   ^3oNOTqDEGT(R)S:CURDNOTO|]NOTDEG^3-L-"S,EYENo|o-aF|eCURS:NOTG!A
   1/2D-<<o: Enter YENH,o|^YENDue+-!C

     --------------------------------------------------------------

2.10. <<aA:o|w,E

   |w,E"t^2I|"YEN\CURS:<<a!AYENiYENH|b.s,E|n-a-o FreeBSD <<P:}
   3/4-:CURS:<<e!A(c)I-aINOTO"AE<<a|A^3z^1L sysinstall (FreeBSD 5.2
   CURS:<<e-a(c)YEN>><<hNOTO /stand/sysinstall) uM<<a?i 3/4U:
   Configure ?iP:uYENHP:i|ae<<aA:o^3](c)w!C

     --------------------------------------------------------------

  2.10.1. ^3](c)w-oo,o

   |p-aG+-zCURS:<<e|^3^3](c)wYENI PPP ^3s 1/2u^3z^1L FTP
   |w,E!A"-o>>o^3oOue+-+-NCUR-L-.|YENX^2{!F
   YEN?|pCURW+-e(c)O>>!-a-o!A+-zYENiYENHuy<<a|ADEGuS:oS:i!C

   |^3Ao: LAN (c)IS:a FreeBSD ^3](c)wNOTDEG gateway (c)I router 
   1/2D-DEGN 3/4\"IYENICURaYENUCURCUR|^3Ao: -oo,oP:iP:YEN^1BYENI
   -a-o^3^1,`!C

                       User Confirmation Requested
    Would you like to configure any Ethernet or SLIP/PPP network devices?

                              [ Yes ]   No

   |p-aGn^3](c)w-oo,oYENd!A 1/2D-?i 3/4U: [ Yes ] uM<<a<<o: Enter!C
   S:_<<h 1/2D-?i [ No ] YENHA:~A:o!C

   ^1IS:I 2-28. ?i 3/4U:-oo,oYENd

   YENICURe|VAa:?i 3/4U:+-zn^3](c)w-a-o-oo,oYENd!AuM<<a<<o: Enter!C

                       User Confirmation Requested
        Do you want to try IPv6 configuration of the interface?

                               Yes   [ No ]

   |b"pCURHDEGIDEG`i-oo,o-a-o+-!-ap!AYENN(c)oYENO/<<e-a-o Internet
   "o(c)w (IPv4)AU-oaDEG-:YENI!A (c)OYENH 1/2D-?i [ No ]
   CUR-L-^3](c)w IPv6!AuM<<a<<o: Enter!C

   YNOTO^3z^1L RA server ^3s"`iNOTJ|^3-a-o IPv6 Ao^1O!A"-o>>o'N?i
   [ Yes ] "A<<o: Enter!ACURS:<<a"t^2I.|-aa'XNOTiA:AYENh.j'M RA
   server!C

                              User Confirmation Requested
         Do you want to try DHCP configuration of the interface?

                               Yes   [ No ]

   +-uCURU"O!AYCUR-L->>Yn DHCP (Dynamic Host Configuration Protocol)
   1/2D-?i [ No ] "A<<o:Enter!C

   ?i 3/4U: [ Yes ] -a-o,U:!A<<h.|DEGo|ae dhclient!AY|"YEN\n"`i IP!A
   <<h"a:.||UDEGEP:nCURWNOTUAo:-a-oAo^1O^3](c)w!A^2O,` 1/2D-DEGN 3/4\
   uU 27.5 ,`!C

   CURU+--a-o-oo,o^3](c)w^1IAAaYENU:|p|o|bDEGIDEG`i-oo,o(LAN)CURCUR!A
   +-N,O 3/4-: 3/4^1^3](c)wNOTDEG gateway -a-oCURe|!!G

   ^1IS:I 2-29. ^3](c)w ed0 ^3o+-i-oo,oYENd-a-o-oo,o^3](c)w

   YENiYENI Tab Aa:|b|UA:ae|`iP:!S:@CURA'<<!A "AP:nCURW
   3/4A|X-a-o,e(R)AE!G

   Host( 3/4-: 3/4^1|W-oU)

           S:^1 3/4a-a-o 3/4-: 3/4^1|W-oU!A"O|pYEN>>"OCURCUR-a-o
           k6-2.example.com!C

   Domain(-ooDEG`i)

           3/4-: 3/4^1(c)OA:Y-a-o-ooDEG`i|W-oU!A"O|pYEN>>"OCURCUR-a-o
           example.com!C

   IPv4 Gateway

           ^3o,I 1/2D-?eCURJ Gateway -a-o IP
           |`iS:}!A"a:YENit^3d+-N<<EYEN]A`a>> 1/4"`i>>.-oY-oo,o!C
           YENu|^3|b,O gateway
           A:Y(c)o,O-oo,o"a:CURCUR,`AICURS:CUR@(R)E!ACUR~n?eCURJ!C
           Y^3o 3/4-: 3/4^1YEN>>"nDEGuNOTDEG,ODEGIDEG`i-oo,o-a-o
           gateway -a-o,U:!A  1/2D-<<O<<uYEN>>A:aeNOTDEG-aAAYENO!C
           |^1YEN~!A ^3q+-` IPv4 Gateway CUR].|^3Q>>{NOTDEGNOTO
           default gateway (c)I default route!C

   Name server(Name server (c)I DNS server)

           ,O-oo,o(c)OYENI-a-o DNS server CURS: IP!C
           YEN>>"ODEG^2^3],O 3/4-: 3/4^1(c)O|b-a-o-oo,o"S|^3
           DNS!ANOTGP:nCURW-a-oNOTO,O ISP (c)O'-L-"N-a-o DNS server
           (208.163.10.2)!C

   IPv4 address

           The IP address to be used for this interface was
           192.168.0.1

   Netmask

           The address block being used for this local area network
           is a Class C block (192.168.0.0 - 192.168.0.255). The
           default netmask is for a Class C network (255.255.255.0).

   Extra options to ifconfig

           Any interface-specific options to ifconfig you would like
           to add. There were none in this case.

   Use Tab to select [ OK ] when finished and press Enter.

                       User Confirmation Requested
         Would you like to Bring Up the ed0 interface right now?

                              [ Yes ]   No

   Choosing [ Yes ] and pressing Enter will bring the machine up on
   the network and be ready for use. However, this does not
   accomplish much during installation, since the machine still needs
   to be rebooted.

     --------------------------------------------------------------

  2.10.2. Configure Gateway

                        User Confirmation Requested
        Do you want this machine to function as a network gateway?

                               [ Yes ]    No

   If the machine will be acting as the gateway for a local area
   network and forwarding packets between other machines then select
   [ Yes ] and press Enter. If the machine is a node on a network
   then select [ No ] and press Enter to continue.

     --------------------------------------------------------------

  2.10.3. Configure Internet Services

                       User Confirmation Requested
 Do you want to configure inetd and the network services that it provides?

                                Yes   [ No ]

   If [ No ] is selected, various services such telnetd will not be
   enabled. This means that remote users will not be able to telnet
   into this machine. Local users will still be able to access remote
   machines with telnet.

   These services can be enabled after installation by editing
   /etc/inetd.conf with your favorite text editor. See uU 27.2.1 ,`
   for more information.

   Select [ Yes ] if you wish to configure these services during
   install. An additional confirmation will display:

                       User Confirmation Requested
 The Internet Super Server (inetd) allows a number of simple Internet
 services to be enabled, including finger, ftp and telnetd.  Enabling
 these services may increase risk of security problems by increasing
 the exposure of your system.

 With this in mind, do you wish to enable inetd?

                              [ Yes ]   No

   Select [ Yes ] to continue.

                       User Confirmation Requested
 inetd(8) relies on its configuration file, /etc/inetd.conf, to determine
 which of its Internet services will be available.  The default FreeBSD
 inetd.conf(5) leaves all services disabled by default, so they must be
 specifically enabled in the configuration file before they will
 function, even once inetd(8) is enabled.  Note that services for
 IPv6 must be separately enabled from IPv4 services.

 Select [Yes] now to invoke an editor on /etc/inetd.conf, or [No] to
 use the current settings.

                              [ Yes ]   No

   Selecting [ Yes ] will allow adding services by deleting the # at
   the beginning of a line.

   ^1IS:I 2-30. Editing inetd.conf

   After adding the desired services, pressing Esc will display a
   menu which will allow exiting and saving the changes.

     --------------------------------------------------------------

  2.10.4. +-OYENI SSH unCURJ

                       User Confirmation Requested
                   Would you like to enable SSH login?
                            Yes        [  No  ]

   ?i 3/4U: [ Yes ] 'N.|+-OYENI sshd(8)!ACUR]'NNOTO OpenSSH -a-o
   daemon u{|!!C ^3o.|CUR^1^3\,O 3/4-:
   3/4^1YENi+-q>>.-oY|wYENthunCURJ!C Ao:(c)o OpenSSH  1/2D-DEGN 3/4\
   uU 14.11 ,` ^3!CURA-a-o>>!(c)u!C

     --------------------------------------------------------------

  2.10.5. Anonymous FTP

                       User Confirmation Requested
  Do you want to have anonymous FTP access to this machine?

                               Yes    [ No ]

     --------------------------------------------------------------

    2.10.5.1. Deny Anonymous FTP

   Selecting the default [ No ] and pressing Enter will still allow
   users who have accounts with passwords to use FTP to access the
   machine.

     --------------------------------------------------------------

    2.10.5.2. Allow Anonymous FTP

   Anyone can access your machine if you elect to allow anonymous FTP
   connections. The security implications should be considered before
   enabling this option. For more information about security see uU
   14 ^3^1.

   To allow anonymous FTP, use the arrow keys to select [ Yes ] and
   press Enter. The following screen (or similar) will display:

   ^1IS:I 2-31. Default Anonymous FTP Configuration

   Pressing F1 will display the help:

 This screen allows you to configure the anonymous FTP user.

 The following configuration values are editable:

 UID:     The user ID you wish to assign to the anonymous FTP user.
          All files uploaded will be owned by this ID.

 Group:   Which group you wish the anonymous FTP user to be in.

 Comment: String describing this user in /etc/passwd


 FTP Root Directory:

         Where files available for anonymous FTP will be kept.

 Upload subdirectory:

         Where files uploaded by anonymous FTP users will go.

   The ftp root directory will be put in /var by default. If you do
   not have enough room there for the anticipated FTP needs, the /usr
   directory could be used by setting the FTP Root Directory to
   /usr/ftp.

   When you are satisfied with the values, press Enter to continue.

                           User Confirmation Requested
          Create a welcome message file for anonymous FTP users?

                               [ Yes ]    No

   If you select [ Yes ] and press Enter, an editor will
   automatically start allowing you to edit the message.

   ^1IS:I 2-32. Edit the FTP Welcome Message

   This is a text editor called ee. Use the instructions to change
   the message or change the message later using a text editor of
   your choice. Note the file name/location at the bottom of the
   editor screen.

   Press Esc and a pop-up menu will default to a) leave editor. Press
   Enter to exit and continue. Press Enter again to save changes if
   you made any.

     --------------------------------------------------------------

  2.10.6. Configure Network File System

   Network File System (NFS) allows sharing of files across a
   network. A machine can be configured as a server, a client, or
   both. Refer to uU 27.3 ,` for a more information.

     --------------------------------------------------------------

    2.10.6.1. NFS Server

                        User Confirmation Requested
  Do you want to configure this machine as an NFS server?

                               Yes    [ No ]

   If there is no need for a Network File System server, select
   [ No ] and press Enter.

   If [ Yes ] is chosen, a message will pop-up indicating that the
   exports file must be created.

                                Message
 Operating as an NFS server means that you must first configure an
 /etc/exports file to indicate which hosts are allowed certain kinds of
 access to your local filesystems.
 Press [Enter] now to invoke an editor on /etc/exports
                                [ OK ]

   Press Enter to continue. A text editor will start allowing the
   exports file to be created and edited.

   ^1IS:I 2-33. Editing exports

   Use the instructions to add the actual exported filesystems now or
   later using a text editor of your choice. Note the file
   name/location at the bottom of the editor screen.

   Press Esc and a pop-up menu will default to a) leave editor. Press
   Enter to exit and continue.

     --------------------------------------------------------------

    2.10.6.2. NFS Client

   The NFS client allows your machine to access NFS servers.

                        User Confirmation Requested
  Do you want to configure this machine as an NFS client?

                               Yes   [ No ]

   With the arrow keys, select [ Yes ] or [ No ] as appropriate and
   press Enter.

     --------------------------------------------------------------

  2.10.7. System Console Settings

   There are several options available to customize the system
   console.

                       User Confirmation Requested
        Would you like to customize your system console settings?

                               [ Yes ]  No

   To view and configure the options, select [ Yes ] and press Enter.

   ^1IS:I 2-34. System Console Configuration Options

   A commonly used option is the screen saver. Use the arrow keys to
   select Saver and then press Enter.

   ^1IS:I 2-35. Screen Saver Options

   Select the desired screen saver using the arrow keys and then
   press Enter. The System Console Configuration menu will redisplay.

   The default time interval is 300 seconds. To change the time
   interval, select Saver again. At the Screen Saver Options menu,
   select Timeout using the arrow keys and press Enter. A pop-up menu
   will appear:

   ^1IS:I 2-36. Screen Saver Timeout

   The value can be changed, then select [ OK ] and press Enter to
   return to the System Console Configuration menu.

   ^1IS:I 2-37. System Console Configuration Exit

   Selecting Exit and pressing Enter will continue with the
   post-installation configurations.

     --------------------------------------------------------------

  2.10.8. Setting the Time Zone

   Setting the time zone for your machine will allow it to
   automatically correct for any regional time changes and perform
   other time zone related functions properly.

   The example shown is for a machine located in the Eastern time
   zone of the United States. Your selections will vary according to
   your geographical location.

                       User Confirmation Requested
           Would you like to set this machine's time zone now?

                             [ Yes ]   No

   Select [ Yes ] and press Enter to set the time zone.

                        User Confirmation Requested
  Is this machine's CMOS clock set to UTC? If it is set to local time
  or you don't know, please choose NO here!

                               Yes   [ No ]

   Select [ Yes ] or [ No ] according to how the machine's clock is
   configured and press Enter.

   ^1IS:I 2-38. Select Your Region

   The appropriate region is selected using the arrow keys and then
   pressing Enter.

   ^1IS:I 2-39. Select Your Country

   Select the appropriate country using the arrow keys and press
   Enter.

   ^1IS:I 2-40. Select Your Time Zone

   The appropriate time zone is selected using the arrow keys and
   pressing Enter.

                             Confirmation
             Does the abbreviation 'EDT' look reasonable?

                             [ Yes ]   No

   Confirm the abbreviation for the time zone is correct. If it looks
   okay, press Enter to continue with the post-installation
   configuration.

     --------------------------------------------------------------

  2.10.9. Linux Compatibility

                       User Confirmation Requested
           Would you like to enable Linux binary compatibility?

                             [ Yes ]   No

   Selecting [ Yes ] and pressing Enter will allow running Linux
   software on FreeBSD. The install will add the appropriate packages
   for Linux compatibility.

   If installing by FTP, the machine will need to be connected to the
   Internet. Sometimes a remote ftp site will not have all the
   distributions like the Linux binary compatibility. This can be
   installed later if necessary.

     --------------------------------------------------------------

  2.10.10. Mouse Settings

   This option will allow you to cut and paste text in the console
   and user programs with a 3-button mouse. If using a 2-button
   mouse, refer to manual page, moused(8), after installation for
   details on emulating the 3-button style. This example depicts a
   non-USB mouse configuration (such as a PS/2 or COM port mouse):

                       User Confirmation Requested
          Does this system have a PS/2, serial, or bus mouse?

                             [ Yes ]    No

   Select [ Yes ] for a PS/2, serial, or bus mouse, or [ No ] for a
   USB mouse and press Enter.

   ^1IS:I 2-41. Select Mouse Protocol Type

   Use the arrow keys to select Type and press Enter.

   ^1IS:I 2-42. Set Mouse Protocol

   The mouse used in this example is a PS/2 type, so the default Auto
   was appropriate. To change protocol, use the arrow keys to select
   another option. Ensure that [ OK ] is highlighted and press Enter
   to exit this menu.

   ^1IS:I 2-43. Configure Mouse Port

   Use the arrow keys to select Port and press Enter.

   ^1IS:I 2-44. Setting the Mouse Port

   This system had a PS/2 mouse, so the default PS/2 was appropriate.
   To change the port, use the arrow keys and then press Enter.

   ^1IS:I 2-45. Enable the Mouse Daemon

   Last, use the arrow keys to select Enable, and press Enter to
   enable and test the mouse daemon.

   ^1IS:I 2-46. Test the Mouse Daemon

   Move the mouse around the screen and verify the cursor shown
   responds properly. If it does, select [ Yes ] and press Enter. If
   not, the mouse has not been configured correctly !X!X select
   [ No ] and try using different configuration options.

   Select Exit with the arrow keys and press Enter to return to
   continue with the post-installation configuration.

     --------------------------------------------------------------

  2.10.11. Install Packages

   Packages are pre-compiled binaries and are a convenient way to
   install software.

   Installation of one package is shown for purposes of illustration.
   Additional packages can also be added at this time if desired.
   After installation sysinstall can be used to add additional
   packages.

                      User Confirmation Requested
  The FreeBSD package collection is a collection of hundreds of
  ready-to-run applications, from text editors to games to WEB servers
  and more. Would you like to browse the collection now?

                             [ Yes ]   No

   Selecting [ Yes ] and pressing Enter will be followed by the
   Package Selection screens:

   ^1IS:I 2-47. Select Package Category

   Only packages on the current installation media are available for
   installation at any given time.

   All packages available will be displayed if All is selected or you
   can select a particular category. Highlight your selection with
   the arrow keys and press Enter.

   A menu will display showing all the packages available for the
   selection made:

   ^1IS:I 2-48. Select Packages

   The bash shell is shown selected. Select as many as desired by
   highlighting the package and pressing the Space key. A short
   description of each package will appear in the lower left corner
   of the screen.

   Pressing the Tab key will toggle between the last selected
   package, [ OK ], and [ Cancel ].

   When you have finished marking the packages for installation,
   press Tab once to toggle to the [ OK ] and press Enter to return
   to the Package Selection menu.

   The left and right arrow keys will also toggle between [ OK ] and
   [ Cancel ]. This method can also be used to select [ OK ] and
   press Enter to return to the Package Selection menu.

   ^1IS:I 2-49. Install Packages

   Use the Tab and arrow keys to select [ Install ] and press Enter.
   You will then need to confirm that you want to install the
   packages:

   ^1IS:I 2-50. Confirm Package Installation

   Selecting [ OK ] and pressing Enter will start the package
   installation. Installing messages will appear until completed.
   Make note if there are any error messages.

   The final configuration continues after packages are installed. If
   you end up not selecting any packages, and wish to return to the
   final configuration, select Install anyways.

     --------------------------------------------------------------

  2.10.12. Add Users/Groups

   You should add at least one user during the installation so that
   you can use the system without being logged in as root. The root
   partition is generally small and running applications as root can
   quickly fill it. A bigger danger is noted below:

                      User Confirmation Requested
  Would you like to add any initial user accounts to the system? Adding
  at least one account for yourself at this stage is suggested since
  working as the "root" user is dangerous (it is easy to do things which
  adversely affect the entire system).

                             [ Yes ]   No

   Select [ Yes ] and press Enter to continue with adding a user.

   ^1IS:I 2-51. Select User

   Select User with the arrow keys and press Enter.

   ^1IS:I 2-52. Add User Information

   The following descriptions will appear in the lower part of the
   screen as the items are selected with Tab to assist with entering
   the required information:

   Login ID

           The login name of the new user (mandatory).

   UID

           The numerical ID for this user (leave blank for automatic
           choice).

   Group

           The login group name for this user (leave blank for
           automatic choice).

   Password

           The password for this user (enter this field with care!).

   Full name

           The user's full name (comment).

   Member groups

           The groups this user belongs to (i.e. gets access rights
           for).

   Home directory

           The user's home directory (leave blank for default).

   Login shell

           The user's login shell (leave blank for default, e.g.
           /bin/sh).

   The login shell was changed from /bin/sh to /usr/local/bin/bash to
   use the bash shell that was previously installed as a package. Do
   not try to use a shell that does not exist or you will not be able
   to login. The most common shell used in the BSD-world is the C
   shell, which can be indicated as /bin/tcsh.

   The user was also added to the wheel group to be able to become a
   superuser with root privileges.

   When you are satisfied, press [ OK ] and the User and Group
   Management menu will redisplay:

   ^1IS:I 2-53. Exit User and Group Management

   Groups can also be added at this time if specific needs are known.
   Otherwise, this may be accessed through using sysinstall
   (/stand/sysinstall in FreeBSD versions older than 5.2) after
   installation is completed.

   When you are finished adding users, select Exit with the arrow
   keys and press Enter to continue the installation.

     --------------------------------------------------------------

  2.10.13. Set the root Password

                         Message
  Now you must set the system manager's password.
  This is the password you'll use to log in as "root".

                          [ OK ]

                [ Press enter or space ]

   Press Enter to set the root password.

   The password will need to be typed in twice correctly. Needless to
   say, make sure you have a way of finding the password if you
   forget. Notice that the password you type in is not echoed, nor
   are asterisks displayed.

 New password :
 Retype new password :

   The installation will continue after the password is successfully
   entered.

     --------------------------------------------------------------

  2.10.14. Exiting Install

   If you need to configure additional network devices or any other
   configuration, you can do it at this point or after installation
   with sysinstall (/stand/sysinstall in FreeBSD versions older than
   5.2).

                      User Confirmation Requested
  Visit the general configuration menu for a chance to set any last
  options?

                               Yes   [ No ]

   Select [ No ] with the arrow keys and press Enter to return to the
   Main Installation Menu.

   ^1IS:I 2-54. Exit Install

   Select [X Exit Install] with the arrow keys and press Enter. You
   will be asked to confirm exiting the installation:

                      User Confirmation Requested
  Are you sure you wish to exit? The system will reboot (be sure to
  remove any floppies/CDs/DVDs from the drives).

                             [ Yes ]   No

   Select [ Yes ] and remove the floppy if booting from the floppy.
   The CDROM drive is locked until the machine starts to reboot. The
   CDROM drive is then unlocked and the disk can be removed from
   drive (quickly).

   The system will reboot so watch for any error messages that may
   appear, see uU 2.10.16 ,` details.

     --------------------------------------------------------------

  2.10.15. Configure Additional Network Services

   Contributed by Tom Rhodes.

   Configuring network services can be a daunting task for new users
   if they lack previous knowledge in this area. Networking,
   including the Internet, is critical to all modern operating
   systems including FreeBSD; as a result, it is very useful to have
   some understanding FreeBSD's extensive networking capabilities.
   Doing this during the installation will ensure users have some
   understanding of the various services available to them.

   Network services are programs that accept input from anywhere on
   the network. Every effort is made to make sure these programs will
   not do anything !S:harmful!". Unfortunately, programmers are not
   perfect and through time there have been cases where bugs in
   network services have been exploited by attackers to do bad
   things. It is important that you only enable the network services
   you know that you need. If in doubt it is best if you do not
   enable a network service until you find out that you do need it.
   You can always enable it later by re-running sysinstall or by
   using the features provided by the /etc/rc.conf file.

   Selecting the Networking option will display a menu similar to the
   one below:

   ^1IS:I 2-55. Network Configuration Upper-level

   The first option, Interfaces, was previously covered during the uU
   2.10.1 ,`, thus this option can safely be ignored.

   Selecting the AMD option adds support for the BSD automatic mount
   utility. This is usually used in conjunction with the NFS protocol
   (see below) for automatically mounting remote file systems. No
   special configuration is required here.

   Next in line is the AMD Flags option. When selected, a menu will
   pop up for you to enter specific AMD flags. The menu already
   contains a set of default options:

 -a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map

   The -a option sets the default mount location which is specified
   here as /.amd_mnt. The -l option specifies the default log file;
   however, when syslogd is used all log activity will be sent to the
   system log daemon. The /host directory is used to mount an
   exported file system from a remote host, while /net directory is
   used to mount an exported file system from an IP address. The
   /etc/amd.map file defines the default options for AMD exports.

   The Anon FTP option permits anonymous FTP connections. Select this
   option to make this machine an anonymous FTP server. Be aware of
   the security risks involved with this option. Another menu will be
   displayed to explain the security risks and configuration in
   depth.

   The Gateway configuration menu will set the machine up to be a
   gateway as explained previously. This can be used to unset the
   Gateway option if you accidentally selected it during the
   installation process.

   The Inetd option can be used to configure or completely disable
   the inetd(8) daemon as discussed above.

   The Mail option is used to configure the system's default MTA or
   Mail Transfer Agent. Selecting this option will bring up the
   following menu:

   ^1IS:I 2-56. Select a default MTA

   Here you are offered a choice as to which MTA to install and set
   as the default. An MTA is nothing more than a mail server which
   delivers email to users on the system or the Internet.

   Selecting Sendmail will install the popular sendmail server which
   is the FreeBSD default. The Sendmail local option will set
   sendmail to be the default MTA, but disable its ability to receive
   incoming email from the Internet. The other options here, Postfix
   and Exim act similar to Sendmail. They both deliver email;
   however, some users prefer these alternatives to the sendmail MTA.

   After selecting an MTA, or choosing not to select an MTA, the
   network configuration menu will appear with the next option being
   NFS client.

   The NFS client option will configure the system to communicate
   with a server via NFS. An NFS server makes file systems available
   to other machines on the network via the NFS protocol. If this is
   a stand-alone machine, this option can remain unselected. The
   system may require more configuration later; see uU 27.3 ,` for
   more information about client and server configuration.

   Below that option is the NFS server option, permitting you to set
   the system up as an NFS server. This adds the required information
   to start up the RPC remote procedure call services. RPC is used to
   coordinate connections between hosts and programs.

   Next in line is the Ntpdate option, which deals with time
   synchronization. When selected, a menu like the one below shows
   up:

   ^1IS:I 2-57. Ntpdate Configuration

   From this menu, select the server which is the closest to your
   location. Selecting a close one will make the time synchronization
   more accurate as a server further from your location may have more
   connection latency.

   The next option is the PCNFSD selection. This option will install
   the net/pcnfsd package from the Ports Collection. This is a useful
   utility which provides NFS authentication services for systems
   which are unable to provide their own, such as Microsoft's MS-DOS
   operating system.

   Now you must scroll down a bit to see the other options:

   ^1IS:I 2-58. Network Configuration Lower-level

   The rpcbind(8), rpc.statd(8), and rpc.lockd(8) utilities are all
   used for Remote Procedure Calls (RPC). The rpcbind utility manages
   communication between NFS servers and clients, and is required for
   NFS servers to operate correctly. The rpc.statd daemon interacts
   with the rpc.statd daemon on other hosts to provide status
   monitoring. The reported status is usually held in the
   /var/db/statd.status file. The next option listed here is the
   rpc.lockd option, which, when selected, will provide file locking
   services. This is usually used with rpc.statd to monitor what
   hosts are requesting locks and how frequently they request them.
   While these last two options are marvelous for debugging, they are
   not required for NFS servers and clients to operate correctly.

   As you progress down the list the next item here is Routed, which
   is the routing daemon. The routed(8) utility manages network
   routing tables, discovers multicast routers, and supplies a copy
   of the routing tables to any physically connected host on the
   network upon request. This is mainly used for machines which act
   as a gateway for the local network. When selected, a menu will be
   presented requesting the default location of the utility. The
   default location is already defined for you and can be selected
   with the Enter key. You will then be presented with yet another
   menu, this time asking for the flags you wish to pass on to
   routed. The default is -q and it should already appear on the
   screen.

   Next in line is the Rwhod option which, when selected, will start
   the rwhod(8) daemon during system initialization. The rwhod
   utility broadcasts system messages across the network
   periodically, or collects them when in !S:consumer!" mode. More
   information can be found in the ruptime(1) and rwho(1) manual
   pages.

   The next to the last option in the list is for the sshd(8) daemon.
   This is the secure shell server for OpenSSH and it is highly
   recommended over the standard telnet and FTP servers. The sshd
   server is used to create a secure connection from one host to
   another by using encrypted connections.

   Finally there is the TCP Extensions option. This enables the TCP
   Extensions defined in RFC 1323 and RFC 1644. While on many hosts
   this can speed up connections, it can also cause some connections
   to be dropped. It is not recommended for servers, but may be
   beneficial for stand alone machines.

   Now that you have configured the network services, you can scroll
   up to the very top item which is X Exit and continue on to the
   next configuration item or simply exit sysinstall in selecting X
   Exit twice then [X Exit Install].

     --------------------------------------------------------------

  2.10.16. FreeBSD P:} 3/4-:NOTyu{

    2.10.16.1. FreeBSD/i386 -a-oP:} 3/4-:NOTyu{

   If everything went well, you will see messages scroll off the
   screen and you will arrive at a login prompt. You can view the
   content of the messages by pressing Scroll-Lock and using PgUp and
   PgDn. Pressing Scroll-Lock again will return to the prompt.

   The entire message may not display (buffer limitation) but it can
   be viewed from the command line after logging in by typing dmesg
   at the prompt.

   Login using the username/password you set during installation
   (rpratt, in this example). Avoid logging in as root except when
   necessary.

   Typical boot messages (version information omitted):

 Copyright (c) 1992-2002 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
         The Regents of the University of California. All rights reserved.

 Timecounter "i8254"  frequency 1193182 Hz
 CPU: AMD-K6(tm) 3D processor (300.68-MHz 586-class CPU)
   Origin = "AuthenticAMD"  Id = 0x580  Stepping = 0
   Features=0x8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8,MMX>
   AMD Features=0x80000800<SYSCALL,3DNow!>
 real memory  = 268435456 (262144K bytes)
 config> di sn0
 config> di lnc0
 config> di le0
 config> di ie0
 config> di fe0
 config> di cs0
 config> di bt0
 config> di aic0
 config> di aha0
 config> di adv0
 config> q
 avail memory = 256311296 (250304K bytes)
 Preloaded elf kernel "kernel" at 0xc0491000.
 Preloaded userconfig_script "/boot/kernel.conf" at 0xc049109c.
 md0: Malloc disk
 Using $PIR table, 4 entries at 0xc00fde60
 npx0: <math processor> on motherboard
 npx0: INT 16 interface
 pcib0: <Host to PCI bridge> on motherboard
 pci0: <PCI bus> on pcib0
 pcib1: <VIA 82C598MVP (Apollo MVP3) PCI-PCI (AGP) bridge> at device 1.0 on pci0
 pci1: <PCI bus> on pcib1
 pci1: <Matrox MGA G200 AGP graphics accelerator> at 0.0 irq 11
 isab0: <VIA 82C586 PCI-ISA bridge> at device 7.0 on pci0
 isa0: <ISA bus> on isab0
 atapci0: <VIA 82C586 ATA33 controller> port 0xe000-0xe00f at device 7.1 on pci0
 ata0: at 0x1f0 irq 14 on atapci0
 ata1: at 0x170 irq 15 on atapci0
 uhci0: <VIA 83C572 USB controller> port 0xe400-0xe41f irq 10 at device 7.2 on pci0
 usb0: <VIA 83C572 USB controller> on uhci0
 usb0: USB revision 1.0
 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
 uhub0: 2 ports with 2 removable, self powered
 chip1: <VIA 82C586B ACPI interface> at device 7.3 on pci0
 ed0: <NE2000 PCI Ethernet (RealTek 8029)> port 0xe800-0xe81f irq 9 at
 device 10.0 on pci0
 ed0: address 52:54:05:de:73:1b, type NE2000 (16 bit)
 isa0: too many dependant configs (8)
 isa0: unexpected small tag 14
 fdc0: <NEC 72065B or clone> at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0
 fdc0: FIFO enabled, 8 bytes threshold
 fd0: <1440-KB 3.5" drive> on fdc0 drive 0
 atkbdc0: <keyboard controller (i8042)> at port 0x60-0x64 on isa0
 atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
 kbd0 at atkbd0
 psm0: <PS/2 Mouse> irq 12 on atkbdc0
 psm0: model Generic PS/2 mouse, device ID 0
 vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
 sc0: <System console> at flags 0x1 on isa0
 sc0: VGA <16 virtual consoles, flags=0x300>
 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
 sio0: type 16550A
 sio1 at port 0x2f8-0x2ff irq 3 on isa0
 sio1: type 16550A
 ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/15 bytes threshold
 ppbus0: IEEE1284 device found /NIBBLE
 Probing for PnP devices on ppbus0:
 plip0: <PLIP network interface> on ppbus0
 lpt0: <Printer> on ppbus0
 lpt0: Interrupt-driven port
 ppi0: <Parallel I/O> on ppbus0
 ad0: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata0-master using UDMA33
 ad2: 8063MB <IBM-DHEA-38451> [16383/16/63] at ata1-master using UDMA33
 acd0: CDROM <DELTA OTC-H101/ST3 F/W by OIPD> at ata0-slave using PIO4
 Mounting root from ufs:/dev/ad0s1a
 swapon: adding /dev/ad0s1b as swap device
 Automatic boot in progress...
 /dev/ad0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1a: clean, 48752 free (552 frags, 6025 blocks, 0.9% fragmentation)
 /dev/ad0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1f: clean, 128997 free (21 frags, 16122 blocks, 0.0% fragmentation)
 /dev/ad0s1g: FILESYSTEM CLEAN; SKIPPING CHECKS
 /dev/ad0s1g: clean, 3036299 free (43175 frags, 374073 blocks, 1.3% fragmentation)
 /dev/ad0s1e: filesystem CLEAN; SKIPPING CHECKS
 /dev/ad0s1e: clean, 128193 free (17 frags, 16022 blocks, 0.0% fragmentation)
 Doing initial network setup: hostname.
 ed0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
         inet6 fe80::5054::5ff::fede:731b%ed0 prefixlen 64 tentative scopeid 0x1
         ether 52:54:05:de:73:1b
 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
         inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8
         inet6 ::1 prefixlen 128
         inet 127.0.0.1 netmask 0xff000000
 Additional routing options: IP gateway=YES TCP keepalive=YES
 routing daemons:.
 additional daemons: syslogd.
 Doing additional network setup:.
 Starting final network daemons: creating ssh RSA host key
 Generating public/private rsa1 key pair.
 Your identification has been saved in /etc/ssh/ssh_host_key.
 Your public key has been saved in /etc/ssh/ssh_host_key.pub.
 The key fingerprint is:
 cd:76:89:16:69:0e:d0:6e:f8:66:d0:07:26:3c:7e:2d root@k6-2.example.com
  creating ssh DSA host key
 Generating public/private dsa key pair.
 Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
 Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
 The key fingerprint is:
 f9:a1:a9:47:c4:ad:f9:8d:52:b8:b8:ff:8c:ad:2d:e6 root@k6-2.example.com.
 setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib
 /usr/local/lib
 a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout
 starting standard daemons: inetd cron sshd usbd sendmail.
 Initial rc.i386 initialization:.
 rc.i386 configuring syscons: blank_time screensaver moused.
 Additional ABI support: linux.
 Local package initialization:.
 Additional TCP options:.

 FreeBSD/i386 (k6-2.example.com) (ttyv0)

 login: rpratt
 Password:

   Generating the RSA and DSA keys may take some time on slower
   machines. This happens only on the initial boot-up of a new
   installation. Subsequent boots will be faster.

   If the X server has been configured and a Default Desktop chosen,
   it can be started by typing startx at the command line.

     --------------------------------------------------------------

    2.10.16.2. FreeBSD/alpha P:} 3/4-:NOTyu{

   Once the install procedure has finished, you will be able to start
   FreeBSD by typing something like this to the SRM prompt:

 >>>BOOT DKC0

   This instructs the firmware to boot the specified disk. To make
   FreeBSD boot automatically in the future, use these commands:

 >>> SET BOOT_OSFLAGS A
 >>> SET BOOT_FILE ''
 >>> SET BOOTDEF_DEV DKC0
 >>> SET AUTO_ACTION BOOT

   The boot messages will be similar (but not identical) to those
   produced by FreeBSD booting on the i386.

     --------------------------------------------------------------

  2.10.17. FreeBSD Shutdown

   It is important to properly shutdown the operating system. Do not
   just turn off power. First, become a superuser by typing su at the
   command line and entering the root password. This will work only
   if the user is a member of the wheel group. Otherwise, login as
   root and use shutdown -h now.

 The operating system has halted.
 Please press any key to reboot.

   It is safe to turn off the power after the shutdown command has
   been issued and the message !S:Please press any key to reboot!"
   appears. If any key is pressed instead of turning off the power
   switch, the system will reboot.

   You could also use the Ctrl+Alt+Del key combination to reboot the
   system, however this is not recommended during normal operation.

     --------------------------------------------------------------

2.11. |w,E-a-o-oAAo/Ao/-g,N"M

   The following section covers basic installation troubleshooting,
   such as common problems people have reported. There are also a few
   questions and answers for people wishing to dual-boot FreeBSD with
   MS-DOS or Windows.

     --------------------------------------------------------------

  2.11.1. What to Do If Something Goes Wrong

   Due to various limitations of the PC architecture, it is
   impossible for probing to be 100% reliable, however, there are a
   few things you can do if it fails.

   Check the Hardware Notes document for your version of FreeBSD to
   make sure your hardware is supported.

   YuwAAe|^3|bCURa:'(c)^2M^3aeCUR-o!A|y"IYENI GENERIC kernel
   CUR'|^3DEGYAD!A"-o>>o'NYENi-`a>>Yn |Uq
   kernel!AYENHYEN[CURJ|^3CURa:'(c)-a-ouwAAe!C The kernel on the boot
   disks is configured assuming that most hardware devices are in
   their factory default configuration in terms of IRQs, IO
   addresses, and DMA channels. If your hardware has been
   reconfigured, you will most likely need to edit the kernel
   configuration and recompile to tell FreeBSD where to find things.

   It is also possible that a probe for a device not present will
   cause a later probe for another device that is present to fail. In
   that case, the probes for the conflicting driver(s) should be
   disabled.

     -a`: Some installation problems can be avoided or alleviated by
     updating the firmware on various hardware components, most
     notably the motherboard. The motherboard firmware may also be
     referred to as BIOS and most of the motherboard or computer
     manufactures have a website where the upgrades and upgrade
     information may be located.

     Most manufacturers strongly advise against upgrading the
     motherboard BIOS unless there is a good reason for doing so,
     which could possibly be a critical update of sorts. The upgrade
     process can go wrong, causing permanent damage to the BIOS chip.

     --------------------------------------------------------------

  2.11.2. Using MS-DOS(R) and Windows(R) File Systems

   At this time, FreeBSD does not support file systems compressed
   with the Double Space(TM) application. Therefore the file system
   will need to be uncompressed before FreeBSD can access the data.
   This can be done by running the Compression Agent located in the
   Start> Programs > System Tools menu.

   FreeBSD can support MS-DOS based file systems(FAT16 and FAT32).
   This requires you use the mount_msdosfs(8) command with the
   required parameters. The utility most common usage is:

 # mount -t msdosfs /dev/ad0s1 /mnt

   In this example, the MS-DOS file system is located on the first
   partition of the primary hard disk. Your situation may be
   different, check the output from the dmesg, and mount commands.
   They should produce enough information to give an idea of the
   partition layout.

     -a`: Extended MS-DOS file systems are usually mapped after the
     FreeBSD partitions. In other words, the slice number may be
     higher than the ones FreeBSD is using. For instance, the first
     MS-DOS partition may be /dev/ad0s1, the FreeBSD partition may be
     /dev/ad0s2, with the extended MS-DOS partition being located on
     /dev/ad0s3. To some, this can be confusing at first.

   NTFS partitions can also be mounted in a similar manner using the
   mount_ntfs(8) command.

     --------------------------------------------------------------

  2.11.3. Troubleshooting Questions and Answers

   2.11.3.1. My system hangs while probing hardware during boot, or
   it behaves strangely during install, or the floppy drive isn't
   probed.

   2.11.3.2. I go to boot from the hard disk for the first time after
   installing FreeBSD, the kernel loads and probes my hardware, but
   stops with messages like:

   2.11.3.3. I go to boot from the hard disk for the first time after
   installing FreeBSD, but the Boot Manager prompt just prints F? at
   the boot menu each time but the boot won't go any further.

   2.11.3.4. The system finds my ed(4) network card, but I keep
   getting device timeout errors.

   2.11.3.1. My system hangs while probing hardware during boot, or
   it behaves strangely during install, or the floppy drive isn't
   probed.

   FreeBSD 5.0 and above makes extensive use of the system ACPI
   service on the i386, amd64 and ia64 platforms to aid in system
   configuration if it's detected during boot. Unfortunately, some
   bugs still exist in both the ACPI driver and within system
   motherboards and BIOS. The use of ACPI can be disabled by setting
   the hint.acpi.0.disabled hint in the third stage boot loader:

 set hint.acpi.0.disabled="1"

   This is reset each time the system is booted, so it is necessary
   to add hint.acpi.0.disabled="1" to the file /boot/loader.conf.
   More information about the boot loader can be found in uU 12.1 ,`.

   2.11.3.2. I go to boot from the hard disk for the first time after
   installing FreeBSD, the kernel loads and probes my hardware, but
   stops with messages like:

 changing root device to ad1s1a panic: cannot mount root

   What is wrong? What can I do?

   What is this bios_drive:interface(unit,partition)kernel_name thing
   that is displayed with the boot help?

   There is a longstanding problem in the case where the boot disk is
   not the first disk in the system. The BIOS uses a different
   numbering scheme to FreeBSD, and working out which numbers
   correspond to which is difficult to get right.

   In the case where the boot disk is not the first disk in the
   system, FreeBSD can need some help finding it. There are two
   common situations here, and in both of these cases, you need to
   tell FreeBSD where the root filesystem is. You do this by
   specifying the BIOS disk number, the disk type and the FreeBSD
   disk number for that type.

   The first situation is where you have two IDE disks, each
   configured as the master on their respective IDE busses, and wish
   to boot FreeBSD from the second disk. The BIOS sees these as disk
   0 and disk 1, while FreeBSD sees them as ad0 and ad2.

   FreeBSD is on BIOS disk 1, of type ad and the FreeBSD disk number
   is 2, so you would say:

 1:ad(2,a)kernel

   Note that if you have a slave on the primary bus, the above is not
   necessary (and is effectively wrong).

   The second situation involves booting from a SCSI disk when you
   have one or more IDE disks in the system. In this case, the
   FreeBSD disk number is lower than the BIOS disk number. If you
   have two IDE disks as well as the SCSI disk, the SCSI disk is BIOS
   disk 2, type da and FreeBSD disk number 0, so you would say:

 2:da(0,a)kernel

   To tell FreeBSD that you want to boot from BIOS disk 2, which is
   the first SCSI disk in the system. If you only had one IDE disk,
   you would use '1:' instead.

   Once you have determined the correct values to use, you can put
   the command exactly as you would have typed it in the /boot.config
   file using a standard text editor. Unless instructed otherwise,
   FreeBSD will use the contents of this file as the default response
   to the boot: prompt.

   2.11.3.3. I go to boot from the hard disk for the first time after
   installing FreeBSD, but the Boot Manager prompt just prints F? at
   the boot menu each time but the boot won't go any further.

   The hard disk geometry was set incorrectly in the Partition editor
   when you installed FreeBSD. Go back into the partition editor and
   specify the actual geometry of your hard disk. You must reinstall
   FreeBSD again from the beginning with the correct geometry.

   If you are failing entirely in figuring out the correct geometry
   for your machine, here's a tip: Install a small DOS partition at
   the beginning of the disk and install FreeBSD after that. The
   install program will see the DOS partition and try to infer the
   correct geometry from it, which usually works.

   The following tip is no longer recommended, but is left here for
   reference:

     If you are setting up a truly dedicated FreeBSD server or
     workstation where you don't care for (future) compatibility with
     DOS, Linux or another operating system, you've also got the
     option to use the entire disk (`A' in the partition editor),
     selecting the non-standard option where FreeBSD occupies the
     entire disk from the very first to the very last sector. This
     will leave all geometry considerations aside, but is somewhat
     limiting unless you're never going to run anything other than
     FreeBSD on a disk.

   2.11.3.4. The system finds my ed(4) network card, but I keep
   getting device timeout errors.

   Your card is probably on a different IRQ from what is specified in
   the /boot/device.hints file. The ed driver does not use the `soft'
   configuration by default (values entered using EZSETUP in DOS),
   but it will use the software configuration if you specify -1 in
   the hints for the interface.

   Either move the jumper on the card to a hard configuration setting
   (altering the kernel settings if necessary), or specify the IRQ as
   -1 by setting the hint !S:hint.ed.0.irq="-1"!" This will tell the
   kernel to use the soft configuration.

   Another possibility is that your card is at IRQ 9, which is shared
   by IRQ 2 and frequently a cause of problems (especially when you
   have a VGA card using IRQ 2!). You should not use IRQ 2 or 9 if at
   all possible.

     --------------------------------------------------------------

2.12. P:iP:YEN|w,E<<u:<<n

   Contributed by Valentino Vaschetto.

   This section describes how to install FreeBSD in exceptional
   cases.

     --------------------------------------------------------------

  2.12.1. Installing FreeBSD on a System without a Monitor or Keyboard

   This type of installation is called a !S:headless install!",
   because the machine that you are trying to install FreeBSD on
   either does not have a monitor attached to it, or does not even
   have a VGA output. How is this possible you ask? Using a serial
   console. A serial console is basically using another machine to
   act as the main display and keyboard for a system. To do this,
   just follow the steps to create installation floppies, explained
   in uU 2.3.7 ,`.

   To modify these floppies to boot into a serial console, follow
   these steps:

    1. Enabling the Boot Floppies to Boot into a Serial Console

       If you were to boot into the floppies that you just made,
       FreeBSD would boot into its normal install mode. We want
       FreeBSD to boot into a serial console for our install. To do
       this, you have to mount the boot.flp floppy onto your FreeBSD
       system using the mount(8) command.

 # mount /dev/fd0 /mnt

       Now that you have the floppy mounted, you must change into the
       /mnt directory:

 # cd /mnt

       Here is where you must set the floppy to boot into a serial
       console. You have to make a file called boot.config containing
       /boot/loader -h. All this does is pass a flag to the
       bootloader to boot into a serial console.

 # echo "/boot/loader -h" > boot.config

       Now that you have your floppy configured correctly, you must
       unmount the floppy using the umount(8) command:

 # cd /
 # umount /mnt

       Now you can remove the floppy from the floppy drive.

    2. Connecting Your Null-modem Cable

       You now need to connect a null-modem cable between the two
       machines. Just connect the cable to the serial ports of the 2
       machines. A normal serial cable will not work here, you need a
       null-modem cable because it has some of the wires inside
       crossed over.

    3. Booting Up for the Install

       It is now time to go ahead and start the install. Put the
       boot.flp floppy in the floppy drive of the machine you are
       doing the headless install on, and power on the machine.

    4. Connecting to Your Headless Machine

       Now you have to connect to that machine with cu(1):

 # cu -l /dev/cuad0

       |b FreeBSD 5.X!A 1/2D-S:iYENI /dev/cuaa0 |O<<D /dev/cuad0!C

   That's it! You should now be able to control the headless machine
   through your cu session. It will ask you to put in the kern1.flp,
   and then it will come up with a selection of what kind of terminal
   to use. Select the FreeBSD color console and proceed with your
   install!

     --------------------------------------------------------------

2.13. >>sS:@|w,ECURu

     -a`: NOTDEGA
     *S:K<<AD->>!(c)u!A|bCURaaCURCUR(c)O'-L-"`i-a-o!uFreeBSD
     YENu-oD-!v!A |b^3o,I<<u:-a-oNOTO+-z(c)OAEP:R(c)I|U|ae?N?y-a-o
     FreeBSD CDROM (c)I DVD!C

   There may be some situations in which you need to create your own
   FreeBSD installation media and/or source. This might be physical
   media, such as a tape, or a source that sysinstall can use to
   retrieve the files, such as a local FTP site, or an MS-DOS
   partition.

   For example:

     * You have many machines connected to your local network, and
       one FreeBSD disc. You want to create a local FTP site using
       the contents of the FreeBSD disc, and then have your machines
       use this local FTP site instead of needing to connect to the
       Internet.

     * You have a FreeBSD disc, and FreeBSD does not recognize your
       CD/DVD drive, but MS-DOS/Windows does. You want to copy the
       FreeBSD installation files to a DOS partition on the same
       computer, and then install FreeBSD using those files.

     * The computer you want to install on does not have a CD/DVD
       drive or a network card, but you can connect a
       !S:Laplink-style!" serial or parallel cable to a computer that
       does.

     * You want to create a tape that can be used to install FreeBSD.

     --------------------------------------------------------------

  2.13.1. Creating an Installation CDROM

   As part of each release, the FreeBSD project makes available at
   least two CDROM images (!S:ISO images!") per supported
   architecture. These images can be written (!S:burned!") to CDs if
   you have a CD writer, and then used to install FreeBSD. If you
   have a CD writer, and bandwidth is cheap, then this is the easiest
   way to install FreeBSD.

    1. Download the Correct ISO Images

       The ISO images for each release can be downloaded from
       ftp://ftp.FreeBSD.org/pub/FreeBSD/ISO-IMAGES-arch/version or
       the closest mirror. Substitute arch and version as
       appropriate.

       That directory will normally contain the following images:

       -ai(R)ae 2-4. FreeBSD 5.X and 6.X ISO Image Names and Meanings

                     AE|W                            CUR-o(R)e           
                                            Everything you need to boot  
                                            into a FreeBSD kernel and    
                                            start the installation       
    -a(c)YEN>>-RELEASE-NOT[-oc-bootonly.iso interface. The installable   
                                            files have to be pulled over 
                                            FTP or some other supported  
                                            source.                      
                                            Everything you need to       
                                            install FreeBSD and a        
    -a(c)YEN>>-RELEASE-NOT[-oc-disc1.iso    !S:live filesystem!", which  
                                            is used in conjunction with  
                                            the !S:Repair!" facility in  
                                            sysinstall.                  
                                            FreeBSD CURaaYENo(FreeBSD    
    -a(c)YEN>>-RELEASE-NOT[-oc-disc2.iso    6.2                          
                                            CURS:<<e-a-o)!AYENHCURI^3\|h 
                                            third-party packages!C       
    -a(c)YEN>>-RELEASE-NOT[-oc-docs.iso     FreeBSD CURaaYENo(FreeBSD    
                                            6.2 CURICURS:<<a)!C          

       You must download one of either the bootonly ISO image (if
       available), or the image of disc one. Do not download both of
       them, since the disc one image contains everything that the
       bootonly ISO image contains.

       Use the bootonly ISO if Internet access is cheap for you. It
       will let you install FreeBSD, and you can then install
       third-party packages by downloading them using the
       ports/packages system (see uU 4 ^3^1) as necessary.

       Use the image of disc one if you want to install a FreeBSD
       release and want a reasonable selection of third-party
       packages on the disc as well.

       The additional disc images are useful, but not essential,
       especially if you have high-speed access to the Internet.

    2. Write the CDs

       You must then write the CD images to disc. If you will be
       doing this on another FreeBSD system then see uU 18.6 ,` for
       more information (in particular, uU 18.6.3 ,` and uU 18.6.4
       ,`).

       If you will be doing this on another platform then you will
       need to use whatever utilities exist to control your CD writer
       on that platform. The images provided are in the standard ISO
       format, which many CD writing applications support.

     -a`: If you are interested in building a customized release of
     FreeBSD, please see the Release Engineering Article.

     --------------------------------------------------------------

  2.13.2. Creating a Local FTP Site with a FreeBSD Disc

   FreeBSD discs are laid out in the same way as the FTP site. This
   makes it very easy for you to create a local FTP site that can be
   used by other machines on your network when installing FreeBSD.

    1. On the FreeBSD computer that will host the FTP site, ensure
       that the CDROM is in the drive, and mounted on /cdrom.

 # mount /cdrom

    2. Create an account for anonymous FTP in /etc/passwd. Do this by
       editing /etc/passwd using vipw(8) and adding this line:

 ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent

    3. Ensure that the FTP service is enabled in /etc/inetd.conf.

   Anyone with network connectivity to your machine can now chose a
   media type of FTP and type in ftp://your machine after picking
   !S:Other!" in the FTP sites menu during the install.

     -a`: If the boot media (floppy disks, usually) for your FTP
     clients is not precisely the same version as that provided by
     the local FTP site, then sysinstall will not let you complete
     the installation. If the versions are not similar and you want
     to override this, you must go into the Options menu and change
     distribution name to any.

     A:uS:iThis approach is OK for a machine that is on your local
     network, and that is protected by your firewall. Offering up FTP
     services to other machines over the Internet (and not your local
     network) exposes your computer to the attention of crackers and
     other undesirables. We strongly recommend that you follow good
     security practices if you do this.

     --------------------------------------------------------------

  2.13.3. <<O/YENss|w,EYENI-a-o-oICURu

   Y+-zYEN^2P:.+-q-oICURu|w,E(Ao:uMS:UICUR-L-<<O/A:^3^3o 1/4EDEGu)!A
   CUR-L- 1/2
   *NOTO|]NOTDEGuwAAeCUR-L-CURa:'(c)(c)INOTO+-zDEGi<<unYENI^3o>>o"eW-a-oCURe|!!A
   +-z^3-L-YEN^2P:.YENy.C,^3AECUR@"C,-oICURuYENH"N|w,E!C

   -oICURu|U:CURO:+-oNOTO 1.44 MB At a minimum, you will need as many
   1.44 MB floppies as it takes to hold all the files in the base
   (base distribution) directory. If you are preparing the floppies
   from DOS, then they must be formatted using the MS-DOS FORMAT
   command. If you are using Windows, use Explorer to format the
   disks (right-click on the A: drive, and select !S:Format!").

   Do not trust factory pre-formatted floppies. Format them again
   yourself, just to be sure. Many problems reported by our users in
   the past have resulted from the use of improperly formatted media,
   which is why we are making a point of it now.

   If you are creating the floppies on another FreeBSD machine, a
   format is still not a bad idea, though you do not need to put a
   DOS filesystem on each floppy. You can use the disklabel and newfs
   commands to put a UFS filesystem on them instead, as the following
   sequence of commands (for a 3.5" 1.44 MB floppy) illustrates:

 # fdformat -f 1440 fd0.1440
 # bsdlabel -w fd0.1440 floppy3
 # newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0

   Then you can mount and write to them like any other filesystem.

   After you have formatted the floppies, you will need to copy the
   files to them. The distribution files are split into chunks
   conveniently sized so that five of them will fit on a conventional
   1.44 MB floppy. Go through all your floppies, packing as many
   files as will fit on each one, until you have all of the
   distributions you want packed up in this fashion. Each
   distribution should go into a subdirectory on the floppy, e.g.:
   a:\base\base.aa, a:\base\base.ab, and so on.

     <<n: The base.inf file also needs to go on the first floppy of
     the base set since it is read by the installation program in
     order to figure out how many additional pieces to look for when
     fetching and concatenating the distribution.

   Once you come to the Media screen during the install process,
   select Floppy and you will be prompted for the rest.

     --------------------------------------------------------------

  2.13.4. +-q MS-DOS CURA^3IDEGI|w,E

   Y.C,^3AEn+-q MS-DOS CURA^3IDEGIP:i|ae|w,E!A 
   1/2D-S:a(c)O|^3|w,EAE^3-L-
   1/2AE>>s"`i,OCURA^3IDEGI(R)UYENO/?yCUR-o-a-o freebsd YENO/?y!C
   CURn|p!Gc:\freebsd!C |^1YENO/?yu^2-ocYEN^2P:.>>PYENu-oD-(c)I FTP
   CUR-o-a-oYENO/?yu^2-ocCUR@P!A |]|^1YNOTOn+-qYENu-oD- 1/2AE>>sAE(R)
   *!A<<O/A:^3"IYENI DOS -a-o xcopy <<u:YENO!C "O|p!An 1/2AE>>s
   FreeBSD ^3ICURp|w,E(c)O>>Y-a-oAE(R) *!G

 C:\> md c:\freebsd
 C:\> xcopy e:\bin c:\freebsd\bin\ /s
 C:\> xcopy e:\manpages c:\freebsd\manpages\ /s

   DEG^2^3] C:  1/4N|^3|h 3/4l-aAAP:!!AYENiYENH(c)n FreeBSD
   |w,EAE!FE:<<hNOTOYENu-oD- 3/4-:YENN,^1!C

   Y"S|^3YENu-oD- 3/4-:!AYENiYENH"`i ftp.FreeBSD.org
   YENhCURU,u:|w,EAE!C
   "CO|w,E(R)MYENo^3-L-|^3"a:NOTU^1iA^3-a-oYENO/?y!FCURn|p base
   NOTO(c)n|b 9.1/base/ YENO/?yCUR-o!C

   1/2D-+-N+-zn|w,E-a-o(R)MYENo(.iuM-aAAP:!nDEG-:)(c)n"`i MS-DOS
   CURA^3IDEGI-a-o c:\freebsd ,I !X!X |]NOTDEG^3oO BIN
   |w,E(R)MYENoP:E"N^3I-oeA^2|w,E|OCURw!C

     --------------------------------------------------------------

  2.13.5. >>sS:@|w,EYENI-a-o-oI+-a

   +-q-oI+-aCURW|w,ECUR]^3\NOTO^3IA^2^3ae-a-oCURe|!!ACURnYENI FTP
   (c)IYENu-oD-|w,EAUS:O:!C |w,Eu{|!DEG^2^3](c)O|^3AE(R)
   *^3-L-.|A-L-AY(c)n|b-oI+-aCURW!C
   |b"u+-o(c)O|^3n,E-a-o|w,EAECURS:<<a
   !AYENiYENHYENICURU|C<<u:YENOS:aYEN|IA-L-AY(c)n|b-oI+-aCURW!G

 # cd /freebsd/distdir
 # tar cvf /dev/rwt0 dist1 ... dist2

   .in|w,E(R)E!AYEN^2P:.YENy 1/2T>>{-oI+-aAU|^3"NOTDEG-:-aAAP:!!A
   YENH<<KAAy|w,E^1Lu{ 1/4E|s-aAAP:!(YENiYENH|U|ae?i
   3/4U:n(c)n|bthOYENO/?y)!A
   YENiYENH(R)e-C,-oI+-a|w,E(R)E-a-oYENth^3!AE(R) *!C
   YENN(c)o-oI+-aYEN>>""ACUR-L--`aAH
   3/4-:|s"u!A|]|^1YENI-oI+-a|w,E.|>>Yn<<U:CURj-a-o 1/4E|s-aAAP:!!C

     -a`: |b"IYENI|w,E-oICURuP:} 3/4-: CURS:<<e!A
     -oI+-aCUR@(c)wnYENy(c)nCURJ-oI+-a
     3/4-:CUR-o!AS:_<<h|bDEG>>'uuwAAe(R)EYENi-`a.|uL-akDEG>>'u"`i-oI+-a
     3/4-:!C

     --------------------------------------------------------------

  2.13.6. Before Installing over a Network

   |^3CURT-oO/-oo,o|w,ECURe|!!G Ethernet ( 1/4D-.C, Ethernet
   '^1CURu)!BSerial port(SLIP (c)I PPP)!B Parallel port (PLIP
   (laplink cable))!C

   ^3z^1L-oo,o|w,E-a-o^3IS:O:CURe|!!A'NNOTO"IYENI Ethernet
   -oo,oYENd!I FreeBSD CURa:'(c)CURj|h 1/4AE+-`"-L--a-o Ethernet
   -oo,oYENd!F
   (c)O|^3CURa:'(c)-a-o-oo,oYENd(CURI"a:(c)O>>Y-a-o^3](c)w)^3-L-|^3|b|U-a(c)YEN>>-a-o
   FreeBSD CUR-o-a-o Hardware Note >>!(c)uCURaaYENoCUR-o|CYENX!C
   Y+-z(c)OYENI-a-oNOTO|^3CURa:'(c)-a-o PCMCIA -oo,oYENd!A 
   1/2D-DEGEYEN^2|bP:} 3/4-:CURS:<<e!AYENyS:a,O-oo,oYENd'!CURW!C
   |]NOTDEG FreeBSD -a-o|w,E^1Lu{!AYENO/<<e"ACUR-L-CURa:'(c) PCMCIA
   YENd-a-o 1/4o:'!(c)TH!C

   |^1YEN~!AAU>>Yn-a 3/4^1D,OYENI-a-o IP |`iS:}YENHCURINOTU^1iA^3-a-o
   netmask NOTDEG|o!A YENHCURI 3/4-: 3/4^1|W-oU!C Y(c)OYENI-a-oNOTO
   PPP ^3s 1/2u!A|OYENB"S|^3(c)T(c)w IP!AS:O 3/4aCURss!A
   |]NOTDEG+-z-a-o ISP .||UDEGECURADEGt IP u^1+-z!C
   Ao:(c)o^3o"C,-oo,o-a-o^2O^3!^3](c)w!A
   YENiYENHNOT-c-,ss+-z-oo,oAo^1O-a-o"t^2I-oTH^2z-aI!C Yn-`aYENH
   3/4-: 3/4^1|W-oU'N-`a^3s"`iNOTU^1iA^3-a-o 3/4-: 3/4^1!A|O<<D-a
   1/2+-u"IYENI IP|`iS:}YENh^3s!A "-o>>o+-zAU>>Yn DNS YENHCURI
   gateway -a-o|`iS:}(YYENI-a-oNOTO PPP ^3s 1/2u!A gateway
   |`iS:}'NNOTO ISP (c)OCURADEGtu^1S:A-a-o IP |`iS:})!C Y.Q^3z^1L
   HTTP proxy "O"IYENI FTP |w,E!A"-o>>oYEN^2P:.-a 3/4^1D proxy
   -a-o-ooS:}NOTDEG|o!C
   Y+-z^1iCURWz(c)O>>Y,eDEGTCUR-L-NOTAECURF,N!A"-o>>o
   1/2D-|b|w,ECURS:<<e!A YENy,ssDEGY"t^2I-oTH^2z-aI(c)I ISP!C

   SLIP
   -a-oCURa:'(c)NOTU.i`i(c)l!A"AYENBYENDn"u:(c)o^1q,-L-CURS:P:!-a-o^1eAAe
   1/2u,o(hard-wired)
   !ACURn|puS:DEGO<<NOT^1q,-L->>P"a:YENL^1q,-L-CURS:P:!-a-o serial 
   1/2u!C CURS:(c)OYENH+-oYENH^1q,-L-P:!YENH-a 1/2+-u
   1/2u,o^3su^2!ACURDNOTOYENN(c)o SLIP |w,EYENO/<<e"ACUR-L-CURa:'(c)
   1/4.+-uYEN\-`a!C PPP CUR~|^3'-L-"N 1/4.+-uYEN\-`a!A (c)OYENH 1/2D-
   3/4"YENi-`aAuYENy+-A:YENI PPP |O<<D SLIP!C

   Yn^3z^1L 1/4AE 3/4U 3/4-:(modem)"O|w,E!A"-o PPP
   'XYENGNOTO+-zDEGssCUR@?i 3/4U:!C  1/2D-YENy.C,^3AE|n ISP
   (c)O'-L-"N-a-oNOTUAo:,e(R)AE!A|]NOTDEG|b|w,ECURS:-a`i'N.|YENI"`i!C

   Y"IYENI PAP (c)I CHAP "O^3s"`i ISP('<<YENy,U:>>!!AY|b Windows
   YENiYENHCUR-L-^3z^1L script 'NYENiYENH^3s 1/2u"`i
   ISP)!A"-o>>o+-zP:E>>Y|b ppp '-L-YENU:^2AA,^1CURU?eCURJ dial
   <<u:YENOS:YYENi 1/4.,^1!C S:_<<h!A+-zYEN^2P:.-a 3/4^1D|p|oYENH,O
   1/4AE 3/4U 3/4-:(c)O+-A:YENI-a-o !S:AT <<u:YENOP:DEG!""O^3s"`i
   ISP!A|]NOTDEG PPP  1/4.,^1u{|!P:E'-L-"N<<D+-`P:S:NOTK-a-o ^2 *-oY
   1/4OAA 3/4^1(terminal emulator)|ODEG_!C  1/2D-DEGN 3/4\ Handbook
   CURCUR user-ppp ^3^1,`YENHCURI FAQ CURCUR-a-oNOTUAo:P:uYENO/!C
   Y|^3 3/4THS:@CURW-a-o-oADEGY!AYENiYENHYEN' set log local ...
   <<u:YENO!AYENH<<K|b?A^1oCURWAAaYENU:NOTUAo:DEGO?y!C

   YYENi-a 1/2+-uYENH hard-wired CURe|!^3s"`iYENtYEN~-a-o
   FreeBSD(2.0-R CURICURS:<<a)  3/4-: 3/4^1!A "-o>>oYENiYENH|O
   1/4{^3z^1L !S:laplink!" YEN|ae^1qAEl"O|w,E!C
   YEN|aeDEGd--a-oP:C,?e^3t^2vCURnS:C,|CDEGd-DEG-a<<U:|h(^3IDEG-aYENi^1F"CNOTi
   50 kbytes/sec)!A (c)OYENH|w,E^3t<< *.|S:oS:O:CUR@"C,!C

     --------------------------------------------------------------

    2.13.6.1. Before Installing via NFS

   NFS |w,ECURe|!NOTU.iA^2<<K!AYENu>>Y+-N FreeBSD |w,EAE(R)
   *^3-L-(c)n"`iNOTYYENx NFS server
   CURW!AuM<<a|A<<u:(c)w"IYENI^3oYENx NFS S:@NOTDEG|w,E"O.
   1/2S:YYENi!C

   Y,O server YENuCUR^1^3\ !S:privileged port!"(^3q+-`^3oNOTO Sun
   CURuS:@-,-a-o^1w^3]E)!A"-o>>o|b|w,ECURS:<<e!AYEN^2P:.YENy"`i
   Options ?i^3aeYENh<<u:(c)w NFS Secure ^3](c)wE!C

   Y-oo,oYENd-a-o^3s 1/2u<<~ 1/2eCUR-L-"I!A"-oYENi-`a>>Yn 1/2O
   3/4aCUR@CURU NFS Slow ^3](c)w!C

   NOTDEGCURFAAy NFS |w,E-`aP:P:S:QS:^1|"!ANFS YEND
   3/4-:YEN^2P:.nYENiYENHCURa:'(c)CURlYENO/?y-a-o+- 3/4,u:
   (mount)!A"O|p!GFreeBSD 9.1 |w,EYENO/?yNOTO|b!G
   ziggy:/usr/archive/stuff/FreeBSD!A"-o>>o ziggy YEN^2P:.CUR^1^3\-a
   1/2+-u+- 3/4,u:|b /usr/archive/stuff/FreeBSD!A|O<<DP:E /usr
   (c)INOTO /usr/archive/stuff!C

   |b FreeBSD -a-o /etc/exports AE!ACURWzYEN\-`aNOTOYENN -alldirs
   ?iP:u(c)O^3](c)w!C "a:YENL-a-o NFS server
   YENi-`a.||^3CUR-L-|P-a-o^3](c)wCURe|!!C YNOTY"`i !S:permission
   denied!" ?u>>~DEGT(R)S:!A
   <<h-aiYENU:YENi-`aYENN(c)o"S|^3+-OYENI^3o?iP:u(c)O^3y|"-a-o!C

     --------------------------------------------------------------

                       ^3^1 3. UNIX DEGoA|.S:(c)A

   Rewritten by Chris Shumway.

3.1. .S:z

   +-uCURU"O-a-o^3oCUR@^3^1+-N^2[>>\ FreeBSD
   S:@.~"t^2I-a-oDEGoYEN>><<u:YENOCURIYEN\-`a!C
   CURj^3!YEN-:-a-oCUR-o(R)e|b UNIX-like
   S:@.~"t^2ICURCUR^3-L-NOTONOTU^3q-a-o!C |p-aG+-z^1i^3o"C,CUR-o(R)e
   1/4o+-x-a-o,U:!AYENiYENH(c)nCURss-a-o,o^1L!C |p-aG+-ze+-uA:^2
   FreeBSD!A"-o+-zCUR@(c)wnYENJ^2O-a-oAA-aS:^1^3o^3^1!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!G

     * |p|o"IYENI FreeBSD -a-o!S:virtual consoles!"!C

     * UNIX AE(R) *AAv^1BS:@-a-oCURe|!YENHCURI FreeBSD CURCURAE(R)
       *-a-o flags!C

     * ^1w^3]-a-o FreeBSD AE(R) *"t^2IDEGt,m!C

     * FreeBSD -a-o-oI-oD-u^2-oc!C

     * |p|o+- 3/4,u:(mount)!B"o/,u:(umount)AE(R) *"t^2I

     * CURDEG>>oNOTOprocesses!Bdaemons YENHCURI signals !C

     * CURDEG>>oNOTO shell
       !AYENHCURI|p|oAAU:S:o+-z^1w^3]-a-ounCURJAo^1O!C

     * |p|o"IYENIDEGoYEN>>-a-oCURaa|r 1/2s?e 3/4^1!C

     * CURDEG>>oNOTO devices (c)M device nodes !C

     * FreeBSD CURU"IYENI-a-o binary (R)ae|!!C

     * |p|o 3/4\AA-a manual pages YENHAo+-oS:o|h-a-o,eDEGT!C

     --------------------------------------------------------------

3.2. Virtual Consoles (c)M^2 *-oY 3/4-:

   |^3<<U:|hCURe-akYENiYENH 3/4THS:@ FreeBSD
   !A"a:CURCURCUR@-oO/'NNOTO|bCURaa|r^2 *-oY 3/4-:CURWYEN'|r!C
   |p|^1"IYENI FreeBSD S:YYENi>>'(c)o:-a-oAAe.|"`i UNIX
   S:@.~"t^2I-a-o<<ACURO(c)M 1/4u(c)E!C
   ^3oCUR@,`'yzCURDEG>>oNOTO!S:^2 *-oY 3/4-:!"(c)M !S:console!"
   !AYENHCURIYENiYENH|p|o|b FreeBSD CURCUR^1BYENIYEN|I!C

     --------------------------------------------------------------

  3.2.1. The Console

   |p-aG+-z"S|^3+-N FreeBSD ^3](c)w|"P:}
   3/4-:(R)E|UDEGEP:iCURJ^1IS:ICURAE 1/4O|!!A"t^2I.||b+-ODEGE-a-o
   script P:]S:^1CURS:<<aAAaYENU:unCURJ-a-o'-L-YENU:^2AA,^1!C
   +-z+-N.|NOTY"`i^1^3NOTO^3o 1/4E-a-o-aF|e!G

 Additional ABI support:.
 Local package initialization:.
 Additional TCP options:.

 Fri Sep 20 13:01:06 EEST 2002

 FreeBSD/i386 (pc3.example.org) (ttyv0)

 login:

   ^3oODEGT(R)S:|b+-z-a-o"t^2ICURW.||^3"C,^3\-a-oCUR-L-|P!A|yNOTOA^3,O.|NOTY"`iAth|u:-a-o-aF|e!C
   S:UI.P?^3 1/2`i-a-oNOTO^3I<<a"a|ae!A^3I<<a"a|aeNOTO!G

 FreeBSD/i386 (pc3.example.org) (ttyv0)

   ^3o|aeYEN]S:tCURFeP:} 3/4-:S:^1"t^2I-a-o,eDEGT!C
   +-zNOTY"`i-a-oNOTO|b Intel (c)INOTU(R)e^3B^2z 3/4^1-a-o x86
   NOT[-ocCURWDEGo|ae-a-o !S:FreeBSD!"-a-o console[1]!C ^3oYENx 3/4-:
   3/4^1-a-o|W|r("CYENx UNIX  3/4-: 3/4^1^3-L-|^3CUR@O|W|r)NOTO
   pc3.example.org!A|O+-z^2{|bNOTY"`i-a-oNOTOYEN|-a-o"t^2I
   console!X!X ttyv0^2 *-oY 3/4-:!C

   ^3I<<a-a-oCUR@|aeA^3,O^3-L-.|NOTO!G

 login:

   ^3oNOTO+-zA^3,On?eCURJ+-z-a-o!S:+-b,^1|W-oU!"-a-o|aCURe!C
   CURUCUR@CURp,`+-NS:iP:D+-z|p|ounCURJ FreeBSD!C

     --------------------------------------------------------------

  3.2.2. unCURJ FreeBSD

   FreeBSD NOTOCUR@O multiuser!Bmultiprocessing -a-o"t^2I!C
   ^3oNOTOCUR@OYEN?|!-a-o|W-oU!A<<u:-a-oNOTO|b^3aeCUR@ 3/4-:
   3/4^1CURWYENiYENH|P(R)E^3QCUR-L-|PCURH"IYENI!A
   |y|P(R)EYENiYENHDEGo|ae<<U:|hu{|!-a-o"t^2I!C

   "CCUR@-oO/|h"IYENI-aI"t^2I^3-L->>YnYENiYENHCURA?eCUR-L-|P!S:"IYENI-aI!"-a-oCURe-ak!C
   |b FreeBSD (YENHCURI(c)O|^3-a-o UNIX-like S:@.~"t^2I)
   CURCUR!A(c)O|^3-a-o"IYENI-aI|bDEGo|aeu{|!CURS:<<eYEN^2P:.YENy!S:unCURJ!""t^2I!C
   "CO"IYENI-aI^3-L-|^3CUR@^2O?W-S-a-o+-b,^1|W-oU
   (!S:username!")CURI+-K 1/2X(!S:password!")!C FreeBSD
   |bCUR^1^3\"IYENI-aIDEGo|aeu{|!<<e+-N.|YENyDEGY^3o"aODEGYAD!C

   |b FreeBSD P:} 3/4-:"AP:]S:^1+-ODEGE-a-o script
   CURS:<<a[2]!AYEN|+-N.||LYENX'-L-YENU:|rCUR,n"D+-z?eCURJYEN?
   1/2T-a-o+-b,^1|W-oU!G

 login:

   |b^3oO 1/2d"O,I!AS:UIDEG^2^3]+-z-a-o+-b,^1NOTOjohn!C
   |b'-L-YENU:|rCUR,^3B?eCURJ john "A<<o:CURU Enter !C
   +-uuU+-zA^3,O.|NOTY"`iYENtCUR@O'-L-YENU:|rCUR,n+-z?eCURJ!S:+-K
   1/2X!"!G

 login: john
 Password:

   ?eCURJ john -a-o+-K 1/2X!A|A<<o:CURU Enter!C ?eCURJ-a-o+-K 1/2X
   CUR-L-.|AAaYENU:|b?A^1oCURW!C +-zCUR-L->>YnNOTDEG|^1
   3/4aCURss!A^3o 1/4EDEGuNOTONOTDEGCURF|wYENthCURW-a-oDEGYAD!C

   |p-aG+-z?eCURJCURFYEN? 1/2T-a-o+-K 1/2X!A+-zA^3,OCURw,gunCURJ
   FreeBSD!C ^2{|b'NYENiYENH^1A,O(c)O|^3YENiYENI-a-o<<u:YENOCURF!C

   +-zA^3,O.|NOTY"`iMOTD (S:YCURuCUReDEGT(R)S:!BMessages Of The
   Day)!A<<a+-+-uuU(c)RYENO'-L-YENU:|rCUR, (CUR@O #,$, (c)INOTO %
   |rCUR,)!C ^3o'N-aiYENU:+-zCURw,g|"YEN\unCURJ FreeBSD CURF!C

     --------------------------------------------------------------

  3.2.3. |h<< Console

   |bCUR@O Console CURUDEGo|ae UNIX .iuMNOTO"S|^3DEGYAD!AuM|O FreeBSD
   NOTOYENiYENH|P(R)EDEGo|ae<<U:|hu{|!-a-o!C ^1^3 FreeBSD ^3o
   1/4EYENiYENH|P(R)EDEGo|aeCUR@CURjDEGiu{|!-a-oS:@.~"t^2I!AYENu|^3CUR@O
   console YENiYENH?eCURJ<<u:YENO^1e|bNOTO|^3AI(R)o:P:O!C |]|^1
   !S:virtual consoles!" 'NAAa+-oNOTU.i|nYENI!C

   YENiYENH^3](c)wAAy FreeBSD |P(R)E|^3<<U:|h virtual console!A
   YENI'XO<<o:Aa:-a-o^2O|X'NYENiYENH+-qCUR@O virtual console
   ,o"`iS:O-a-o virtual console !C "CCUR@O console
   ^3-L-|^3|UCURwCUR-L-|P-a-o?eYENXAW^1D!A.i+-qNOTYCUR@O virtual
   console CURA'<<"`iCURUCUR@O-a-o(R)EO!AFreeBSD .||UDEGE^3B^2zAa:
   1/2L?eCURJCURI?A^1o?eYENX!C

   FreeBSD <<O-dCURF-SS:O-a-o<<o:Aa:^2O|X"OCURA'<< console [3]!C
   +-zYENiYENHYENI Alt-F1!B Alt-F2!B"`i Alt-F8 "OCURA'<< FreeBSD
   -a-oCUR-L-|P console!C

   .i+-z+-qCUR@O console CURA'<<"`iCURUCUR@O-a-o(R)EO!AFreeBSD
   .|^3B^2z?A^1o?eYENX-a-oAx|sCURI|^'_!C
   ^3o'N!S:|n^1^3!"|^3<<U:|h!S:ueAA!"-a-o?A^1o(c)MAa: 1/2L!A
   YENiYENHAAy+-z?eCURJ<<u:YENO"`i FreeBSD DEGo|ae!C |bNOTYCUR@O
   console CURWDEGo|ae-a-ou{|!"ACUR-L-.||]NOTDEGCURA"`iS:O-a-o
   console |ODEG+-CURiDEGo|ae!ACURA'<<"`iYENtCUR@O console
   (R)E!AYEN|ICUR'.|A:~A:oDEGo|ae!C

     --------------------------------------------------------------

  3.2.4. /etc/ttys AE

   FreeBSD ^1w^3]-a-oueAA console A`|@|^3 8 O!A
   |y^3o"A<<Duw(c)E^3W(c)w!A+-zYENi>>'AP^3](c)w^3o"C,ueAA console
   -a-o 1/4AEP:q 1/4W'i!C |^3Ao:ueAA console -a-o
   1/2s,^1,o^3](c)w^3-L-|b /etc/ttys ^3oAE(R) *CUR-o^3](c)w!C

   YENiYENHYENI /etc/ttys AE(R) *"O^3](c)w FreeBSD -a-oueAA console!C
   AE(R) *CUR-o"C|ae<<Duu,NCURaa|r(,O|aeP:}AY"S|^3 #
   ^3o|r)^3-L-NOTO^3](c)w^2 *-oY 3/4-:(c)IueAA console!C FreeBSD
   ^1w^3]|^3 9 OueAA console |yYENu+-ODEGE 8
   O!ACUR]'NNOTOYENHCURUYENH ttyv P:}AY-a-o"-o'X|ae^3](c)w!C

 # name  getty                           type    status          comments
 #
 ttyv0   "/usr/libexec/getty Pc"         cons25  on  secure
 # Virtual terminals
 ttyv1   "/usr/libexec/getty Pc"         cons25  on  secure
 ttyv2   "/usr/libexec/getty Pc"         cons25  on  secure
 ttyv3   "/usr/libexec/getty Pc"         cons25  on  secure
 ttyv4   "/usr/libexec/getty Pc"         cons25  on  secure
 ttyv5   "/usr/libexec/getty Pc"         cons25  on  secure
 ttyv6   "/usr/libexec/getty Pc"         cons25  on  secure
 ttyv7   "/usr/libexec/getty Pc"         cons25  on  secure
 ttyv8   "/usr/X11R6/bin/xdm -nodaemon"  xterm   off secure

   |^3Ao:|UA:ae|`i-a-o^3](c)wYENHCURI"a:YENL?iP:u!A 1/2D-DEGN 3/4\
   ttys(5) >>!(c)u!C

     --------------------------------------------------------------

  3.2.5. Single User  1/4O|!-a-o Console

   |^3Ao: !S:single user  1/4O|!!" -a-oCURP:^2D-|b uU 12.6.2 ,`
   ^3oAa:|^3,O-oECURP:^2D-!C |b single user 
   1/4O|!(R)E!A-`aDEG-:"IYENI-a-o console YENu|^3CUR@O!A"AuLueAA
   console YENiYENI!C |O single user  1/4O|!NOTUAo:^3](c)wEYENiYENH|b
   /etc/ttys AEDEGu 1/2O 3/4a!C CURU+-YENH console
   P:}AY-a-o"-o|ae!A'NNOTOCURF!G

 # name  getty                           type    status          comments
 #
 # If console is marked "insecure", then init will ask for the root password
 # when going to single-user mode.
 console none                            unknown off secure

     -a`: |b console
     "-o|ae<<e+--a-ouu,N|^3'-L-"`i!AYENiYENHS:a"-o|ae-a-o secure
     S:iNOTDEG insecure!A |p|^1CUR@"O!AS:Y"I FreeBSD P:iCURJ single
     user  1/4O|!!A CUR'.|n"D+-z?eCURJ root -a-o+-K 1/2X!C

     1/2D- 1/4f.V|O 1/4{NOTOS:_nS:iNOTDEG insecure!C
     |]NOTDEG,UCUR@S:NDEGO root +-K 1/2X-a-o,U:!AYnunCURJ single user
     1/4O|!'N|^3"C,^3A.D-CURF!C
     3/4"-oTHAU|^3"a:YENLCURe|!YENiYENHunCURJ!A|y^1iCUR-L- 1/4o
     FreeBSD P:} 3/4-:u{S:C,-a-oCURH|O"YEN!A'N.|NOTU.i'AECURa!C

     --------------------------------------------------------------

  3.2.6. S:oS:i console -a-oAAaYENU:ue+-

   FreeBSD console ^1w^3]AAaYENU:CURjCURpYENiYENH 1/2O 3/4aNOTDEG
   1024x768!B1280x1024
   (c)I"a:YENLAAaYENU:YENd>>P?A^1o|^3CURa:'(c)-a-o,N-aR<< *CURjCURp!C
   nCURA'<<AAaYENU:CURjCURp!AYEN^2P:.n<<.s 1/2sA:P: kernel
   "AYEN[CURJCURU+-^3o"aP:u^3](c)w!G

 options VESA
 options SC_PIXEL_MODE

   CUR@YEN^1 kernel |^3YEN[CURJ^3o"aP:u"A<<.s
   1/2sA:P:S:^1^2|!A'NYENiYENHYENI vidcontrol(1)
   "ODEG>>'uYENO/<<e(c)OCURa:'(c)-a-o 1/4O|!|^3th"C,!C
   YnNOTdNOTYCURa:'(c)-a-o 1/4O|!!AYENiYENHYEN'!G

 # vidcontrol -i mode

   ,O<<u:YENO.|AAaYENU:,O 3/4-: 3/4^1(c)OCURa:'(c)-a-oAAaYENU:
   1/4O|!^2M^3ae!C uM<<aYENiYENH|b root console CUR-o^3z^1L
   vidcontrol(1) <<u:YENO!A "OS:oS:iAAaYENU: 1/4O|!!G

 # vidcontrol MODE_279

   Y^1i.s-a-oAAaYENU: 1/4O|!A:+-+-oAUCUR-L-?u!AYENiYENH|b
   /etc/rc.conf ^3](c)wCURS:!AYENHAAy"C|,<<P:}
   3/4-:<<a.||UDEGEYENI(R)A:!C YENHCURW+-^3o+-!-apNOTDEG"O!A'NNOTO!G

 allscreens_flags="MODE_279"

     --------------------------------------------------------------

3.3. AAv

   FreeBSD . 1/2|U(c)o BSD UNIX!AA:~(c)OCURF'XO<<n-a-o UNIX .S:(c)A!C
   -oYENyCUR]^3I(c)uAAa!AYEN|NOTOCUR@'U multi-user S:@.~"t^2I!C
   YEN|YENiYENH|P(R)E^3B^2z|hCURH|hCURu!A
   t^3d^1y(c)^3-a-oCURA"E>>P-oTH^2z"O|U"C|`i"IYENI-aI^1iuw-oD-,E,m!BP:gAa:^3]^3AE!BDEGO
   3/4D-AAeCURI CPU (R)EP:!-a-on"D!C

   CUR]|]NOTDEG"t^2I-`aDEG-:CURa:'(c)|h"IYENI-aI!A
   (c)OYENH"t^2I-oTH^2z-a-oCUR@CURA^3-L-|^3AAv"O"M(c)w
   1/2O:YENiYENHAA-a"u!B 1/4gCURJ(c)IDEGo|ae,e. 1/2!C
   ^3o"C,AAvCURAS:O"IYENICURT^2OCURKP:i|`i-a-o
   1/4AE|rAx|s!ACUR@^2OYENN-aiAE(R) *-a-o(c)O|^3-aI!A
   CUR@^2OYENN-aiAE(R)
   *(c)OA:Y-a-o,s^2O!A|O^3I<<aCUR@^2O<<hYENN-ai"a:YENL(c)O|^3CURH!C
   -aiYENU:^3o"C, 1/4AE|r-a-oCURe|!|pCURU:

   E                       AAv                        YENO/?yAAaYENU: 
   0 CUR-L-YENiAA-a"u, CUR-L-YENi 1/4gCURJ,           ---             
     CUR-L-YENiDEGo|ae                                
   1 CUR-L-YENiAA-a"u, CUR-L-YENi 1/4gCURJ,           --x             
     YENiDEGo|ae                                      
   2 CUR-L-YENiAA-a"u, YENi 1/4gCURJ,                 -w-             
     CUR-L-YENiDEGo|ae                                
   3 CUR-L-YENiAA-a"u, YENi 1/4gCURJ, YENiDEGo|ae     -wx             
   4 YENiAA-a"u, CUR-L-YENi 1/4gCURJ,                 r--             
     CUR-L-YENiDEGo|ae                                
   5 YENiAA-a"u, CUR-L-YENi 1/4gCURJ, YENiDEGo|ae     r-x             
   6 YENiAA-a"u, YENi 1/4gCURJ, CUR-L-YENiDEGo|ae     rw-             
   7 YENiAA-a"u, YENi 1/4gCURJ, YENiDEGo|ae           rwx             

   "IYENI ls(1) <<u:YENO(R)E!AYENiYENHYEN[CURW -l DEGN 1/4AE!A
   "OAEuo/,O^2O-a-oYENO/?y^2M^3ae!C
   ^2M^3aeCURCURA:ae|`i-a-o,eDEGTYEN]S:tAE(R)
   *^1i(c)O|^3-aI!B,s^2OCURI"a:YENLCURH-a-oAAv!C
   |bYENoCUR@OYENO/?y(c)^3CURUDEGo|ae ls
   -l!A.|AAaYENU:|pCURU-a-ou^2-aG:

 % ls -l
 total 530
 -rw-r--r--  1 root  wheel     512 Sep  5 12:31 myfile
 -rw-r--r--  1 root  wheel     512 Sep  5 12:31 otherfile
 -rw-r--r--  1 root  wheel    7680 Sep  5 12:31 email.txt
 ...

   |b^3o,IS:i(c)O+-z,O|p|oDEGICURA ls -l
   ^2A:CUR@A:ae.iCURCUR-a-o,eDEGT:

 -rw-r--r--

   ^2A:CUR@O (^3IYEN-aAa:) -a-o|rCUR,YENI"O-aiYENU:^3oOAE(R)
   *-a-oAth<<NOTNOTDEG|o!A DEG-L- 1/4D-.C,AE(R)
   *YENHYEN~!A(c)||^3YENO/?y!B-S(R)i|rCUR,,E,m (Special character
   device)!B Socket CURI"a:YENL-S(R)iueAAAE(R) *,E,m (Special
   pseudo-file device)!A |b|^1"O.iCURCUR!A- -aiYENU:,OAE(R)
   *NOTDEGCUR@O 1/4D-.C,-a-oAE(R) *!C 
   1/2d"OCURCUR+-uCURU"O-a-oCURTO|rCUR,CURCUR!Arw-
   YENN-ai(c)O|^3-aI^1iAE(R) * 3/4O:|^3-a-oAAv!C
   |A+-uCURU"O-a-oCURTO|rCUR,!A r-- <<hYENN-ai,s^2O^1iAE(R) *
   3/4O:|^3-a-oAAv!A ^3I<<aCURTO|rCUR,!Ar--
   <<hYENN-ai"a:YENLCURH^1iAE(R) * 3/4O:|^3-a-oAAv!C -}S:e,^1 (-)
   -aiYENU:"S|^3AAv!A 1/2d"OCURCUR-a-o^3oOAE(R) *-a-oAAv!A
   YENuCUR^1^3\(c)O|^3-aIAA-a"u!B 1/4gCURJAE(R)
   *!A,s^2OYENHCURI"a:YENLCURHP:E-`aAA-a"uAE(R) *!C (R)U
   3/4UYENHCURW-a-o-ai(R)ae!A|^1-oO/AAv-a-oAE(R) *YENiYENH"IYENI 644
   "O-aiYENU:!A "C^2O 1/4AE|rCURAS:OYENN-aiAE(R) *-a-oCURT-oO/AAv!C

   YENHCURWNOTOCUR-L-?u-a-oCURe|!!A|y"t^2I,O|p|o+-+-"i,E,m-a-oAAv!H
   ^1e>>UCURW FreeBSD ^1iCURj|h-a-ouw-oD-,E,m'N|p|PAE(R)
   *!Au{|!YENiYENHP:}+-O!BAA-a"uYENHCURI 1/4gCURJ,e(R)AE|pCUR@-eAE(R)
   *!C ^3o"C,-S(R)i,E,mAE(R) * (Special device file) ^3-L-Ax|s(c)o
   /dev YENO/?yCURCUR!C

   YENO/?yCUR]|P|pAE(R) *!A 3/4O:|^3AA-a"u!B
   1/4gCURJCURIDEGo|ae-a-oAAv!A |y|bDEGo|aeAAvCURW>>PAE(R)
   *|^3(c)uAAa-a-o(R)t^2S:!C .iYENO/?y^3Q
   1/4D-YENU:NOTDEGYENiDEGo|ae(R)E!AYENN-aiYENiYENH"IYENI !S:cd!"
   (S:oS:iYENO/?y) P:iCURJ,OYENO/?y!C
   CUR]YENN-ai-`aDEG-:|s"u|b|^1YENO/?yCURS:CURCUR-a-oCURw-a
   3/4AE|W-a-oAE(R) * (.iuM!AAE(R) *CUR' 3/4O:|^3|UCURv-a-oAAv)

   CUR *"a:!An-`aDEG-:|CYENXYENO/?yCUR-o(R)e!AYEN^2P:.
   3/4O:|^3YENO/?y-a-oAA-a"uAAv!C |O.inS:RDEG-L-CURw-a
   3/4AE|W-a-oAE(R) *(R)E!ACUR]YEN^2P:. 3/4O:|^3AE(R)
   *(c)O|bYENO/?y-a-o 1/4gCURJ YENHCURI DEGo|ae-a-oAAv!C

   AU|^3CUR@"C,AAv!A|y^3o"C,AAvYENDn|b-S(R)i+-!-ap"IYENI!A|p setuid
   binaries CURI sticky directories!C |p-aG+-zAU.Q-a 3/4^1DS:o|hAE(R)
   *AAv-a-o,eDEGTCURI"IYENICURe-ak!A 1/2D-DEGEYEN^2DEGN 3/4\ chmod(1)
   >>!(c)uCURaaYENo!C

     --------------------------------------------------------------

  3.3.1. AAv^2AA,^1

   Contributed by Tom Rhodes.

   AAv^2AA,^1YENi-oUDEGu^2AA,^1-aiYENU:!A
   "IYENI|rCUR,-a-oCURe|!"O"uYENN"IYENI 1/4AEE"O^3](c)wAE(R)
   *(c)IYENO/?y-a-oAAv!C ^2AA,^1-aiYENU:-a-o(R)ae|!"IS:C,NOTDEG
   (NOTYCURH)(DEGES:@)(AAv)!AYENi"IYENI-a-o^2AA,^1|pCURU:

         P:uYENO/           |rYENA                  .N,q              
   (NOTYCURH)           u               "IYENI-aI                     
   (NOTYCURH)           g               ,s^2O(c)O|^3-aI               
   (NOTYCURH)           o               "a:YENL                       
   (NOTYCURH)           a               YENth^3!(!S:world!")          
   (DEGES:@)            +               1/4WYEN[AAv                   
   (DEGES:@)            -               ^2 3/4DEG-L-AAv               
   (DEGES:@)            =               <<u:(c)wAAv                   
   (AAv)                r               AA-a"u                        
   (AAv)                w               1/4gCURJ                      
   (AAv)                x               DEGo|ae                       
   (AAv)                t               Sticky bit                    
   (AAv)                s               Set UID (c)I GID              

   |pYENy<<e|P 1/4E"IYENI chmod(1)
   <<u:YENO"O^3](c)w!A|y"IYENI-a-oDEGN 1/4AENOTDEG^3o"C,|rCUR,!C
   "O|p!A+-zYENiYENH"IYENICURU|C<<u:YENO,TCURi"a:YENL"IYENI-aI|s"uAE(R)
   * FILE:

 % chmod go= FILE

   Y|^3"aOYENHCURW-a-o^2AA,^1-aiYENU:YENiYENH"IYENI^3r,^1 (,)
   DEGI^1j!C "O|p!ACURU|C<<u:YENO+-N.|^2
   3/4DEG-L-,s^2OCURI"a:YENLCURH^1iAE(R) * FILE -a-o 1/4gCURJAAv!A
   "A"IYENth^3!CURH(!S:world!")^1i,OAE|^3DEGo|aeAAv!C

 % chmod go-w,a+x FILE

     --------------------------------------------------------------

  3.3.2. FreeBSD AE(R) *-oX 1/4D-(Flag)

   Contributed by Tom Rhodes.

   DEG-L-CURF<<e+-'-L-"`i-a-oAE(R) *AAvYEN~!AFreeBSD CURa:'(c)"IYENI
   !S:AE(R) *-oX 1/4D-!"!C ^3o"C,-oX 1/4D- 1/4WYEN[CURFAE(R)
   *-a-o|wYENth(c)ECURI-oTH^2z(c)E!A|yCUR-L-YEN]S:tYENO/?y!C

   AE(R) *-oX 1/4D- 1/4WYEN[CURF-oTH^2z(c)E!A 1/2T<<O|bNOTY"C,(R)EO
   root CUR-L-.|.NYEN~+-NAE(R) * *S:i(c)I^2 3/4DEG-L-!C

   *S:i-a-oAE(R) * flag P:E>>Yn"IYENI 3/4O:|^3A^2(c)o:-a-oCURP:+--a-o
   chflags(1) CURu"a!C "O|p!A 1/4D-YENU:"t^2I,TCURiS:RDEG-L--a-o-oX
   1/4D-(c)oAE(R) * file1!A"IYENICURU|C<<u:YENO!G

 # chflags sunlink file1

   Yn^2 3/4DEG-L-"t^2I,TCURiS:RDEG-L--a-o-oX 1/4D-!AYENu>>YnA^2^3ae|b
   sunlink <<eYEN[CURW !S:no!"!A"O|p!G

 # chflags nosunlink file1

   "IYENI ls(1) CURIDEGN 1/4AE -lo YENiAEuo/AE(R) *YENO/<<e-a-o-oX
   1/4D-!G

 # ls -lo file1
        

   ?eYENX-a-ou^2-aG|pCURU:

 -rw-r--r--  1 trhodes  trhodes  sunlnk 0 Mar  1 05:54 file1

   |h 1/4AE-a-o-oX 1/4D-P:E-`aYENN root "IYENI-aI"O 1/4D-YENU:(c)I^2
   3/4DEG-L-!A|O^3!YEN-:-oX 1/4D-YENiYENNAE(R) *(c)O|^3-aI^3](c)w!C
   S:UI<<O/A:^3"t^2I-oTH^2z-aIYENi 3/4\AA-a chflags(1) CURI
   chflags(2) >>!(c)uYENHAA,NNOTUAo:^2O,`!C

     --------------------------------------------------------------

3.4. YENO/?yu^2-oc

   >>{AN FreeBSD
   -a-oYENO/?yNOT[-oc!A'NYENi^1i"t^2I|^3.S:^2CUR-a-oDEGoA|^2z,N!C
   ^3I<<n-a-o^2o:^1L(c)o 3/4aOYENO/?y-a-o(R)UYENO/?y!A'NNOTO !S:/!"
   YENO/?y!A ,OYENO/?y.||bP:} 3/4-:(R)E^3IYENy+- 3/4,u:
   (mount)!A,I+-.||^3P:} 3/4-:(c)O.|YENI"`iYEN^2^3AEAE(R) *!C
   |^1YEN~!A(R)UYENO/?yAU|^3NOTo:?y"a:YENLAE(R) *"t^2I-a-o+-
   3/4,u:AINOTUAo:^3](c)w!C

   !u+- 3/4,u:AI!v'NNOTOAAy.s 1/4W-a-oAE(R) *"t^2I!A-`a+-u"`iCURW
   1/4h-a-oAE(R) *"t^2I (^3q+-`'NNOTO!u(R)UYENO/?y!vAE(R) *"t^2I)
   -a-oYENO/?y!C |b uU 3.5 ,` ^3oAa:^1i|^1|^3S:o,O^2OCURP:^2D-!C 
   1/4D-.C,-a-o+- 3/4,u:AIYEN]NOTACURF /usr!B/var!B /tmp!B/mnt
   YENHCURI /cdrom!C ^3o"C,YENO/?y^3q+-`.|DEGO?y|b /etc/fstab
   ^3](c)wAECUR-o!C /etc/fstab NOTODEGO?y|UAE(R) *"t^2ICURINOTUAo:+-
   3/4,u:AI-a-o-ai(R)ae!C CURj^3!CURA|b /etc/fstab |^3DEGO?y-a-oAE(R)
   *"t^2I!A.||bP:} 3/4-:(R)EYENN rc(8) script "O|UDEGE+-
   3/4,u:!ADEG-L-<<DYEN|I|^3^3](c)w noauto ?iP:u!C
   "a:CURCUR^2O,`>>!(c)uYENiDEGN 3/4\ uU 3.6.1 ,`!C

   |^3Ao:AE(R) *"t^2INOT[-oc-a-oS:^1 3/4a>>!(c)uYENiDEGN 3/4\
   hier(7)!C
   ^2{|b(c)O!AAAyS:UICURjPYENyCUR@?s+-`"-L--a-oYENO/?y|^3th"C,S:a!C



    YENO/?y                                 >>!(c)u                              
/               AE(R) *"t^2I-a-o(R)UYENO/?y!C                                    
/bin/           single-user!Bmulti-user "a-oO/                                   
                1/4O|!NOTOYENi"IYENI-a-oDEGoYEN>>CURu"a !C                       
/boot/          S:@.~"t^2IP:} 3/4-:^1Lu{.|YENI"`i-a-ou{|!!B^3](c)wAE!C           
/boot/defaults/ ^1w^3]-a-oP:} 3/4-:+-ODEGE^3](c)wAE!A,O+-! 1/2D-DEGN 3/4\        
                loader.conf(5) !C                                                
/dev/           Device nodes!A,O+-! 1/2D-DEGN 3/4\ intro(4)!C                    
/etc/           "t^2I^3](c)wAECURICUR@"C, script AE!C                            
/etc/defaults/  ^1w^3]-a-o"t^2I^3](c)wAE!A,O+-! 1/2D-DEGN 3/4\ rc(8)!C           
/etc/mail/      MTA(Mail Transport Agent)-a-oNOTUAo:^3](c)wAE!A^1^3NOTO          
                sendmail(8)!C                                                    
/etc/namedb/    named ^3](c)wAE!A,O+-! 1/2D-DEGN 3/4\ named(8)!C                 
/etc/periodic/  "CCURe!B"CP:g!B"CCURe^3z^1L cron(8); DEGo|ae-a-o(c)w'A+-AEu{     
                script!A ,O+-! 1/2D-DEGN 3/4\ periodic(8)!C                      
/etc/ppp/       ppp ^3](c)wAE!A,O+-! 1/2D-DEGN 3/4\ ppp(8)!C                     
/mnt/           "t^2I-oTH^2z-aI-oDYENIYENR.iA{(R)E+- 3/4,u:AI-a-o-aAAYENO/?y!C   
/proc/          Process AE(R) *"t^2I!A,O+-! 1/2D-DEGN 3/4\ procfs(5) CURI        
                mount_procfs(8)!C                                                
/rescue/        -oo<<ae+-I'(c)YENI^3~-a-oCUR@"C, statically linked u{|!!A,O+-!   
                1/2D-DEGN 3/4\ rescue(8)!C                                       
/root/          root +-b,^1-a-o(R)aYENO/?y!C                                     
/sbin/          "N single-user CURI multi-user                                   
                Ao^1O"IYENI-a-o"t^2Iu{|!CURI-oTH^2zCURu"a !C                     
                A{(R)EAE(R) *!C CUR@-e|O"YEN!A<<P:} 3/4-:CURS:<<a /tmp           
                CUR-o-a-o-aF|e.|^3Q^2MDEG-L-+- 1/4!C |O^3q+-`.|+-N memory-based  
/tmp/           AE(R) *"t^2I+- 3/4,u:|b /tmp CURW!C ^3o"C,-o 3/4"AEYENi^3z^1L    
                tmpmfs NOTUAo:-a-o rc.conf(5) Ao^1OAAU: 1/4AE"O|UDEGES:^1|"      
                !C((c)INOTO|b /etc/fstab CUR-oDEGu^3](c)w!A ,O+-! 1/2D-DEGN 3/4\ 
                mdmfs(8)!C)                                                      
/usr/           YENDnNOTO"IYENI-aI(c)O|w,E-a-oCURu"au{|!!BA^3YENIu{|!|s(c)n^3B!C 
/usr/bin/       +-`YENICURu"a!BP:}uoCURu"a!BA^3YENI^3nAAe!C                      
/usr/include/   1/4D-.C, C include -a-oNOTUAo: header AE(R) *(R)w!C              
/usr/lib/       "c,|!(R)w|s(c)n^3B!C                                             
/usr/libdata/   "a:YENL|U|!CURu"a-a-o,e(R)AEAE!C                                 
/usr/libexec/   "t^2I daemons CURI"t^2ICURu"au{|!(^3z^1L"a:YENLu{|!"ODEGo|ae)!C  
                |s(c)nCUR@"C,|U|ae|w,E-a-oDEGo|aeAE!B"c,|!(R)wuYENuYEN!C         
                |P(R)E!ACUR]NOTO FreeBSD ports NOT[-oc-a-o^1w^3]|w,EYENO/?y!C    
                /usr/local CUR-o-a-oYENO/?yNOT[-ocCURjP>>P /usr NOTU|P!A,O+-!    
/usr/local/     1/2D-DEGN 3/4\ hier(7) >>!(c)u!C |y man                          
                YENO/?y"OYEN~!AYEN|INOTO-a 1/2+-u(c)n|b /usr/local               
                (c)^3CURU!A|O<<D /usr/local/share!A|O ports                      
                (c)O|w,E-a-o>>!(c)uCURaaYENo<<h|b share/doc/port!C               
/usr/obj/       |b 1/2sA:P: /usr/src YENO/?y(R)E(c)O^2-L-YENI-a-oNOTUAo:NOT[-oc  
                object AE(R) *!C                                                 
/usr/ports      FreeBSD Ports Collection (optional)!C                            
/usr/sbin/      "t^2I daemon CURI"t^2ICURu"a(-a 1/2+-uYENN"IYENI-aIDEGo|ae)!C    
/usr/share/     |UNOT[-ocNOTO|@^3q-a-oAE(R) *!C                                  
/usr/src/       BSD YEN>>"-a-o`i(c)l 1/2X((c)I|U|ae.s 1/4W-a-o)!C                
/usr/X11R6/     X11R6 NOTUAo:(R)MYENo-a-oDEGo|aeAE!B"c,|!(R)wuYEN(optional)!C    
                |s(c)n|U-oO/YENI^3~-a-o log AE!BA{(R)E(c)I                       
                1/4E(R)E|s(c)n!B|C|L(c)IP:lYENo-a-o spool AE(R)                  
/var/           *!C|^3(R)EO!Amemory-based AE(R) *"t^2ICUR].|+- 3/4,u:|b /var!C   
                ^3o"C,-o 3/4"AEYENi^3z^1L varmfs NOTUAo:-a-o rc.conf(5)          
                Ao^1OAAU: 1/4AE"O|UDEGES:^1|"!C((c)INOTO|b /etc/fstab            
                CUR-oDEGu^3](c)w!ANOTUAo:^2O,` 1/2D-DEGN 3/4\ mdmfs(8)!C)        
/var/log/       |UP:u"t^2IDEGO?y-a-o log AE(R) *!C                               
/var/mail/      |U"IYENI-aI-a-o mailbox AE(R) *!C                                
/var/spool/     |U-oO/|L-ai 3/4-:!BP:lYENo"t^2I-a-o spool YENO/?y!C              
                A{(R)EAE(R) *!C ^3o"C,AE(R) *|b<<P:}                             
/var/tmp/       3/4-:<<a^3q+-`CUR'.|<<O-d!ADEG-L-<<D /var NOTOA:Y(c)o            
                memory-based AE(R) *"t^2I!C                                      
/var/yp         DEGO?y NIS maps!C                                                

     --------------------------------------------------------------

3.5. -oI-oD-^2OA'

   FreeBSD YENI"O'MS:a:AE(R) *-a-o^3ICURp^3ae|`i'NNOTOAE(R)
   *-a-o|W-oUCURF!C AE(R) *-a-o|W-oU|^3CURjCURp
   1/4gCURS:CURA!A(c)OYENH>>! readme.txt (c)M README.TXT
   NOTO"aOCUR-L-|P-a-oAE(R) *!C FreeBSD "ACUR-L-"IYENIDEGAEAE|W
   (.txt)
   "OS:PS:O^3oNOTOCUR@Ou{|!AE!BCURaaYENoAE(c)INOTO"a:YENLAth<<NOT-a-oAE(R)
   *!C

   AE(R) *|s|bYENO/?y,I+-!C CUR@OYENO/?yCURCURYENi-`a"S|^3YENo|oAE(R)
   *!ACUR]YENi-`a|^3|n'X|EOAE(R) *!C
   YENO/?yCURS:CURCURCUR]YENiYENHYEN]S:t"a:YENL-a-oYENO/?y!F
   +-zYENiYENH<<O/YENssP:YEN
   1/4h|!-a-oYENO/?yYENH<<K,e(R)AE-a-o-oTH^2z!C

   AE(R) *(c)IYENO/?y-a-o^1iA^3NOTOAC,YENNu^1(c)w-a-oAE(R)
   *(c)IYENO/?y|W-oU!AuM<<aYEN[CURWYEN?+- * 1/2u^2AA,^1
   (/)!FCURS:<<a|Auo/>>YnYEN[CURW"a:YENL-a-oYENO/?y|W-oU!C
   |p-aG+-z|^3CUR@OYENO/?y foo !A,I+-|^3CUR@OYENO/?yYENsS:@
   bar!A^3oOYENO/?yCURCURCURSYEN]S:tCURFCUR@OYENs readme.txt
   -a-oAE(R) *!A"-o>>o^3oOAE(R) *-a-oYENth|W!A(c)I-aI>>!AE(R)
   *-a-o,o(R)|'NNOTO foo/bar/readme.txt!C

   YENO/?yCURIAE(R) *Ax|s|bAE(R) *"t^2ICURS:CURCUR!C "COAE(R)
   *"t^2I^3-L-|^3DEGssCUR@CUR@O^3ICURW
   1/4h-a-oYENO/?y!AYENsDEGu(R)UYENO/?y (root directory)!C
   uM<<a|b^3oO(R)UYENO/?yCURU+-CUR~-`a|^3"a:YENL-a-oYENO/?y!C

   "`iYENO/<<eNOTDEGCURiCURj.S:(c)M"a:YENL+-zYENI^1L-a-o-a-oS:@.~"t^2I^3-L-(R)tCUR-L-|h!C
   AUNOTO|^3"C,CUR-L-CUR@ 1/4E-a-o|aCURe'NNOTOCURF!A"O|p MS-DOS YENI
   \ .iAE(R) *(c)MYENO/?y|W-oU-a-oCURA^1j^2AA,^1!A|O Mac OS(R)
   <<hNOTOYENI : ^2AA,^1!C

   FreeBSD -a-o,o(R)|CURCUR"A"S|^3"IYENI-oI-oD-
   3/4-:YENN,^1(c)I"a:YENL-a-o-oI-oD-|W-oU!C
   |]|^1!A+-zCUR-L-YENiYENH"IYENI^1^3 c:/foo/bar/readme.txt ^3o
   1/4ECURl-a-oAE(R) *|W-oU!C

   NOTU^1i-a-o!A|b FreeBSD "t^2ICURCUR|^3CUR@OAE(R)
   *"t^2I^3Q<<u:(c)wNOTDEG(R)UAE(R) *"t^2I!C (R)UAE(R)
   *"t^2I-a-o(R)UYENO/?yYENN / -aiYENU:!C uM<<a"a:YENL-a-oAE(R)
   *"t^2I|A+- 3/4,u: (mount) |b(R)UAE(R) *"t^2ICURS:CURU!C|]|^1uL 1/2
   *+-z-a-o FreeBSD
   "t^2ICURW|^3|hCURO:Auuw-oD-!A"CCUR@OYENO/?yNOTYDEG_"O'N^1^3|b|PCUR@O-oI-oD-CURW!C

   DEG^2^3]+-z|^3CURTOAE(R) *"t^2I!ACURAS:OYENsS:@ A!B B CURI C!C
   "COAE(R) *"t^2I^3-L-YEN]S:t"aOYENO/?y!AYENsDEGu A1!BA2
   ("I|^1Ath+-A+-o B1!BB2 CURI C1!BC2)!C

   -oU A NOTDEGYENDn-a-oAE(R) *"t^2I!F|p-aG+-zYENI ls
   <<u:YENONOTdNOTY|^1YENO/?y-a-oCUR-o(R)e!A+-z.|NOTY"`i"aOCURlYENO/?y!G
   A1 CURI A2!A|pCURU(c)OYENU:!G

  /
  |
  +--- A1
  |
  `--- A2

   CUR@OAE(R) *"t^2IYEN^2P:.YENHYENO/?yS:I|!+-
   3/4,u:(c)oYENtCUR@OAE(R) *"t^2ICURW!C |]|^1!ADEG^2^3]+-z+-N B +-
   3/4,u:(c)o A1 CURS:CURW!A<<h B -a-o(R)UYENO/?y'NAAU:|"CURF
   A1!A|O|b B CURS:CURU-a-oYENo|oYENO/?y-a-o,o(R)|CUR]AHCURS:S:iAAU::

  /
  |
  +--- A1
  |     |
  |     +--- B1
  |     |
  |     `--- B2
  |
  `--- A2

   |b B1 (c)I B2 YENO/?yCURCUR-a-oYENo|oAE(R) *YEN^2P:.,gYENN,o(R)|
   /A1/B1 (c)I /A1/B2 CUR~-`a^1F"`i!C (c)O|^3`i"O|b /A1
   CURCUR-a-oAE(R) *.| 1/4E(R)E^3QAoAADEG_"O!A-a 1/2"`i B ^3Q!u^2
   3/4DEG-L- (unmounted)!v<<aCUR~.||AAAa^2{YENX"O!C

   |p-aG B +- 3/4,u:|b A2 CURS:CURW!A<<h.|AAU:|"!G

  /
  |
  +--- A1
  |
  `--- A2
        |
        +--- B1
        |
        `--- B2

   CURW+--a-o,o(R)|CURAS:ONOTDEG /A2/B1 CURI /A2/B2!C

   AE(R) *"t^2IYENiYENH+- 3/4|b"a:YENLAE(R)
   *"t^2I-a-oYENO/?yCURS:CURW!C (c)uA:oCURS:<<e-a-o"OCURl!AC AE(R)
   *"t^2IYENiYENH+- 3/4|bAE(R) *"t^2I B -a-o B1
   YENO/?yCURS:CURW!A|p^1I(c)OYENU:!G

  /
  |
  +--- A1
  |
  `--- A2
        |
        +--- B1
        |     |
        |     +--- C1
        |     |
        |     `--- C2
        |
        `--- B2

   (c)I-aI C -a 1/2+-u+- 3/4,u:(c)o A -a-o A1 YENO/?yCURS:CURW!G

  /
  |
  +--- A1
  |     |
  |     +--- C1
  |     |
  |     `--- C2
  |
  `--- A2
        |
        +--- B1
        |
        `--- B2

   |p-aG+-z 1/4o+-x MS-DOS -a-o,U:!A^3o(c)M join <<u:YENO<<U:Ath|u:
   (Ao:uMCUR-L- 3/4"NOTU|P)!C

   CUR@-e+-!-apCURU+-zCUR-L->>Yn 3/4aCURss^3o"C,-aF|e!C
   DEG-L-<<D+-zn|w,E.s-a-o-oI-oD-!ACUR-L-uM^3q+-`|b+-z|w,E FreeBSD
   (R)E<<O/YENss|nAE(R) *"t^2I"A"M(c)w|nn+-
   3/4,u:|b|o^3BCURS:<<a'NCUR-L-.||ADEGuYENo|oS:oDEGECURF!C

   +-zS:^1YENthYENiYENH"IYENI^3aeCUR@-a-oCUR@OCURj-a-o(R)UAE(R)
   *"t^2I (root file system) |OCUR-L-<<O/YENss"a:YENL-a-oAE(R)
   *"t^2I!C ^3o 1/4E|^3|n^3BCUR]|^3|^3Aa^3B!C

   "IYENI|hOAE(R) *"t^2I-a-o|n^3B

     * CUR-L-|P-a-oAE(R) *"t^2I|b+-
       3/4CURW-a-o(R)EOYENiYENH|^3CUR-L-|P-a-o +- 3/4,u:DEGN 1/4AE!C
       A|"O"O>>!!ANOTDEG"DAO.V+-zYENiYENH+-N(R)UAE(R)
       *"t^2I^3]|"DEGssAA-a!A YENHA *S:KCUR-L-CURpCURssS:RDEG-L-(c)I
       *S:i+- 1/4<<n-a-oAE(R) *!C +-N"IYENI-aIYENi 1/4gCURJ-a-oAE(R)
       *"t^2I ("O|p /home) ?WYENssYENX"OCUR]YENiYENHAAyYENLIYENI
       nosuid -a-oDEGN 1/4AE+- 3/4,u:!A|^1?iP:uYENiYENHAAy|b^3oOAE(R)
       *"t^2ICURCURDEGo|aeAE-a-o suid/guid bits
       YEN-c-(R)A:!ACUR]^3\YENiYENHAAy"t^2IS:o|wYENth!C

     * FreeBSD .||UDEGE(R)U 3/4U+-zAE(R)
       *"t^2I-a-o"IYENICURe|!"ODEGu^3I"I-a-oAE(R) *DEGt,mCURe|!!C
       |]|^1!ACUR@O|^3<<U:|hCURpAE(R) *!B +-`+-` 1/4gCURJ-a-oAE(R)
       *"t^2I,oYENu|^3'XO,uCURj-a-oAE(R) *-a-oAE(R)
       *"t^2IDEGt,mNOTOCUR-L-CUR@ 1/4E-a-o!C
       |p-aG+-zYENu|^3^3aeCUR@CUR@OCURj-a-oAE(R)
       *"t^2I!A^3o^3!CURA'N"SYENICURF!C

     * FreeBSD -a-oAE(R) *"t^2I|bDEG+-^1q-a-o(R)EO<<U:A(c)T!C
       uM|O!A|bNOTY"C,<<n-a-o(R)EODEG+-^1qCUR'uM.|^1iAE(R)
       *"t^2Iu^2-oc^3y|".l(R)`!C CURA^3I|"^3\|hOAE(R)
       *"t^2I-a-o,U:|b"t^2I|bDEG+-^1q<<aCURn,u-`aDEG-:YEN?+-`+-ODEGE!A
       YENH<<K+-z|b>>Yn-a-o(R)EO+-N^3AEYEN-:,e(R)AE|^|s|^"O!C

   "IYENI^3aeCUR@AE(R) *"t^2I-a-o|n^3B

     * AE(R) *"t^2I-a-oCURjCURpNOTO(c)T(c)w-a-o!C +-z.i-a`i|w,E
       FreeBSD
       -a-o(R)EOA^3,O.|u^1(c)wCUR@OCURjCURp!AYENiNOTO<<a"O+-zYENi-`a.|.QS:a-aAAP:!YEN[CURj!C
       |p-aG"S|^3^3AEYEN-:-a-o,U:NOTO<<U:Ao/^1F|"-a-o!F
       +-zYEN^2P:.+-NAE(R)
       *"t^2I<<.s<<O/YENssNOTDEG+-z>>Yn-a-oCURjCURp!AuM<<a+-N^3AEYEN-:|^|s|^"O!C

         <<n: FreeBSD -a-o growfs(8) <<u:YENOYENiYENHNOTd--}|^1"i-a
         1/2+-uAAU:S:oAE(R) *"t^2I-a-oCURjCURp!C

   AE(R) *"t^2IYEN]S:t|bCURA^3IDEGI,I+-!C |]NOTDEG FreeBSD (c)OAAS:
   UNIX
   NOT[-oc!A^3oAa:A?-a-oCURA^3IDEGI(c)MCUR@-e'-L-"`i-a-oCURA^3IDEGI
   ("O|p MS-DOS CURA^3IDEGI) CUR-L-|P!C
   "CCUR@OCURA^3IDEGIYENNCUR@OYENN,^1(|rYENA)-aiYENU:!A+-q a "`i h!C
   "COCURA^3IDEGIYENu-`aYEN]S:tCUR@OAE(R) *"t^2I!C
   |]|^1DEG-L-CURF>>!+-`"-L-"`iYENIAE(R) *"t^2I|P-a-o+-
   3/4,u:AI"O-aiYENU:AE(R) *"t^2IYEN~!A
   CUR]YENiYENHYENIYEN]S:tYENL-a-oCURA^3IDEGIYENN,^1"O-aiYENU:!C

   FreeBSD CUR].|(R)^3-oI-oD--aAAP:!"O.i swap space!C Swap space u^1
   FreeBSD .iS:@ueAADEGO 3/4D-AAeYENI!C ^3oAAy+-z-a-o^1q,-L-|n^1^3
   3/4O:|^3CURn^1e>>US:o|h-a-oDEGO 3/4D-AAe!C .i FreeBSD -a-oDEGO
   3/4D-AAeYENIS:^1-a-o(R)EO!AYEN|.|S:aCUR@"C,YENO/<<e"SYENI"`i-a-o,e(R)AE^2
   3/4"`i swap space!AuM<<a|bYENI"`i-a-o(R)EO^2 3/4|^YENh (|P(R)E^2
   3/4YENX^3!YEN-:"SYENI"`i-a-o)!C

   NOTY"C,CURA^3IDEGI|^3-oD"O-a-o"IYENICURe|!|pCURU!G

   CURA^3IDEGI                         -oD"O                          
   a           ^3q+-`YEN]S:t(R)UAE(R) *"t^2I (root file system)       
   b           ^3q+-`NOTO swap space                                  
               ^3q+-`(c)M 3/4aO slice -a-oCURjCURpCUR@                
               1/4E!Au^1CUR@"C,.|YENI"`i 3/4aO slice -a-oCURu"au{|!   
   c           ("O|puw-oD-AayAENOTdCURu"a) "O"IYENI!C                 
               CUR@-e"O>>!+-zA^3,OCUR-L-.|S:aAE(R)                    
               *"t^2I<<O/YENss|b^3oOCURA^3IDEGI!C                     
               CURA^3IDEGI d                                          
   d           '?,g|^3YENN-ai-S(R)i.N,q!A|yNOTOCURw,gCUR-L-|A"IYENI!C 
               (c)OYENH^2{|b d                                        
               'N(c)M"a:YENLCUR@-e-a-oCURA^3IDEGINOTU|PCURF!C         

   "COYEN]S:t|^3AE(R) *"t^2I-a-oCURA^3IDEGINOTO|s|b(c)O? *-a-o slice
   ,I+-!C FreeBSD -a-o slice 'NNOTO<<u:YEN+-`S:UI-oUNOTDEGCURA^3IDEGI
   (partition) -a-o-aF|e!C |P 1/4E|a!A.|^3o
   1/4ECURl-oU(c)ICUR]NOTO|]NOTDEG FreeBSD -a-o UNIX |a+-m!C |O slice
   NOTO|^3 1/2s,^1-a-o!A+-q 1 ,^1 1/2s"`i 4 ,^1!C

   slice ,^1 1/2X,o|b,E,m|W-oU<<a+-!AYENy+-uCUR@O|rYENA s!AuM<<a+-q 1
   ,^1P:}(c)l 1/2sCURUYENh!C |]|^1 !S:da0s1!" 'NNOTO<<u:^2A:CUR@O
   SCSI uw-oD--a-o^2A:CUR@O slice!C
   CUR@O-oI-oD-CURWYENu-`a|^3YEN|O^1eAAe-a-o
   slice!A|yNOTO|b^1eAAe-a-o slice CURCUR+-zYENiYENHP:eP:i
   3/4A.iAth<<NOT-a-oAATH?e slice!C ^3o"C,(c)u|u-a-o slice 
   1/2s,^1+-q 5 P:}(c)l!A(c)OYENH !S:ad0s5!" NOTO^2A:CUR@O IDE
   uw-oD-CURW-a-o^2A:CUR@O(c)u|u slice!C AE(R) *"t^2I|b,E,m (device)
   ,I'NNOTO|bCUR@O slice CURS:CURCUR!C

   Slices!B!S:dangerously dedicated!"  1/4O|!-a-o^1eAAe-oI-oD-
   3/4-:!AYENHCURI"a:YENLYEN]S:tCURA^3IDEGI(partition)
   -a-o-oI-oD-^3-L-NOTOYENH|rYENA a "`i h -a-o 1/2s,^1"O-aiYENU:!C 
   1/2s,^1NOTO+-u|b,E,m|W-oU-a-o<<a+--a-o!A|]|^1 !S:da0a!"
   NOTO-oI-oD- 3/4-: da CURW-a-o^2A:CUR@O !S:dangerously dedicated!"
   1/4O|!CURS:CURA^3IDEGI!C |O !S:ad1s3e!" <<hNOTO^2A:CURGAu IDE
   uw-oD-CURW^2A:CURTO slice -a-o^2A:CUROCURA^3IDEGI!C

   ^3I<<a!AS:UI'NYENiYENHS:a"t^2ICURW-a-o"CO-oI-oD-^3-L-DEGICURAYENX"OCURF!C
   CUR@O-oI-oD--a-o|W-oU.||^3CUR@OYENN
   1/2X"O-aiYENU:^3oO-oI-oD--a-oAth<<NOT!A+-uuUNOTOCUR@O 1/4AE|r!A
   -aiYENU:^3oNOTOthCUR@O-oI-oD-!C ^3oAa:,o slice "CO-oI-oD-
   1/2s,^1+-q 0 P:}(c)lCUR-L-CUR@ 1/4E!C +-`"-L--a-oYENN
   1/2XYENiYENHDEGN|O -ai(R)ae 3-1!C

   .inDEGN.OCUR@OCURA^3IDEGI-a-o(R)EO!AFreeBSD
   .|n+-zCUR@"O:?eCURJYEN]S:t^3oOCURA^3IDEGI-a-o slice CURI-oI-oD-
   3/4-:|W-oU!F.inDEGN.OCUR@O slice
   -a-o(R)EO!ACUR]YEN^2P:.?eCURJYEN]S:t^3oO slice -a-o-oI-oD-|W-oU!C
   <<c,>>oDEGu(c)O!H-oYENyYENy|CYENX-oI-oD-|W-oU!AuM<<a s YEN[CURW
   slice  1/2s,^1!A^3I<<a|A?eCURJCURA^3IDEGI|rYENAYENN,^1!C 
   1/2d"OYENiYENHDEGN|O  1/2d"O 3-1.

   1/2d"O 3-2 YENU: 1/2dCURFCUR@ODEGoYEN>>-a-o-oI-oD-CURAYENNOT
   1/4O|!!ANOTU<<H^1i+-z|^3"C,ADEGS:U!C

   n|w,E FreeBSD!A+-zYEN^2P:.YENy<<O/,m-oI-oD--a-o slice!A+-uuU(c)o
   slice CURCUR<<O/YENssnu^1 FreeBSD YENI-a-oCURA^3IDEGI!C
   ^3I<<a|b^3o"C,CURA^3IDEGICURCUR<<O/YENssAE(R) *"t^2I ((c)I swap
   space) "A"M(c)wn+-N^3o"C,AE(R) *"t^2I+- 3/4,u:(c)oth,I!C

   -ai(R)ae 3-1. -oI-oD- 3/4-:YENN,^1

     YENN,^1                            .N,q                          
   ad          ATAPI(IDE) -oI-oD- 3/4-:                               
   da          SCSI -a 1/2+-u|s"u-oI-oD- 3/4-:                        
   acd         ATAPI(IDE) YENu-oD- 3/4-:                              
   cd          SCSI YENu-oD- 3/4-:                                    
   fd          ^3n-oD- 3/4-:                                          

   1/2d"O 3-1. -oI-oD-!Bslice CURICURA^3IDEGI(c)R|W 1/2d"O

   |W-oU                             .N,q                             
   ad0s1a ^2A:CUR@O IDE uw-oD- (ad0) CURW^2A:CUR@O slice              
          (s1)-a-o^2A:CUR@OCURA^3IDEGI(a) !C                          
   da1s2e ^2A:CURGO SCSI uw-oD- (da1) CURW^2A:CURGO slice (s2)        
          -a-o^2A:CUROCURA^3IDEGI (e) !C                              

   1/2d"O 3-2. -oI-oD--a-o.S:(c)A 1/4O<<NOT

   |^1^1IAAaYENU: FreeBSD CURCUR+-u"`i"t^2I-a-o^2A:CUR@O IDE -oI-oD-
   3/4-:CUR-o^3!DEGt,m^1I!C DEG^2^3]^3oO-oI-oD--a-o(R)eP:qNOTO
   4 GB!A"AYENBYEN]S:tCURF"aO 2 GB -a-o slice (MS-DOS
   -a-oCURA^3IDEGI)!C ^2A:CUR@O slice NOTO DOS -a-o C: -oI-oD-
   3/4-:!A^2A:CURGO<<h|w,ECURF FreeBSD!C YEN>> 1/2d"O-a-o FreeBSD
   |^3CURTOCURA^3IDEGIYENHCURICUR@O swap CURA^3IDEGI!C

   ^3oCURTOCURA^3IDEGI"CO^3-L-NOTOCUR@OAE(R) *"t^2I!C a
   CURA^3INOTO(R)U (root) AE(R) *"t^2I!FCURA^3I e NOTO /var!F|O f
   CURA^3INOTO /usr YENO/?yu^2-oc!C

 .-----------------.  --.
 |                 |    |
 |  DOS / Windows  |    |
 :                 :     >  First slice, ad0s1
 :                 :    |
 |                 |    |
 :=================:  ==:                               --.
 |                 |    |  Partition a, mounted as /      |
 |                 |     > referred to as ad0s2a          |
 |                 |    |                                 |
 :-----------------:  ==:                                 |
 |                 |    |  Partition b, used as swap      |
 |                 |     > referred to as ad0s2b          |
 |                 |    |                                 |
 :-----------------:  ==:                                 |  Partition c, no
 |                 |    |  Partition e, used as /var       > file system, all
 |                 |     > referred to as ad0s2e          |  of FreeBSD slice,
 |                 |    |                                 |  ad0s2c
 :-----------------:  ==:                                 |
 |                 |    |                                 |
 :                 :    |  Partition f, used as /usr      |
 :                 :     > referred to as ad0s2f          |
 :                 :    |                                 |
 |                 |    |                                 |
 |                 |  --'                                 |
 `-----------------'                                    --'

     --------------------------------------------------------------

3.6. +- 3/4,u:>>P"o/,u:AE(R) *"t^2I

   AE(R) *"t^2I'N^1^3CUR@Au 3/4d-!C/ 'N^1^3NOTO 3/4d-(R)U!A|O
   /dev!A/usr YENHCURI"a:YENL|b(R)UYENO/?yCURU-a-oYENO/?y'N^1^3NOTO
   3/4d--aK!A|O^3o"C, 3/4d--aKCURW+-CURSAU|^3CURACURa:!A^1^3NOTO
   /usr/local uYEN!C

   |]NOTDEGNOTY"C,`i|]!AS:UI.|+-NCUR@"C,YENO/?yCURAS:O(c)n|bCUR-L-|P-a-oAE(R)
   *"t^2ICURW!C |p /var YEN]S:tCURFYENi-`a.|-o!YENX"O-a-o
   log/!Aspool/ uYENYENO/?yYENHCURI|U|!|U 1/4E-a-o 1/4E|sAE!C
   S:a(R)UAE(R)
   *"t^2IP:e"`i-o!YENX"OAAauMCUR-L-NOTOO|nYEND.N!A(c)OYENHS:UI(c)^1(c)^1.|CURn,uP:E|VS:a
   /var +-q / CURCUR(c)OYENX"O!C

   YENtCUR@O+-`"-L-"`iS:aNOTY"C,YENO/?y(c)n|bCUR-L-|PAE(R)
   *"t^2ICURW-a-o^2zYENNNOTO!G ^3o"C,AE(R)
   *|bCUR-L-|P-a-o^1eAAe(c)IueAA-oI-oD- 3/4-:CURW!C
   ^1^3NOTO-oo,oAE(R) *"t^2I (Network File System) (c)INOTOYENu-oD-
   3/4-:!C

     --------------------------------------------------------------

  3.6.1. fstab AE

   |b /etc/fstab ,I+-|^3^3](c)w-a-oAE(R) *"t^2I.||bP:} 3/4-:
   -a-o^1Lu{CURCUR|UDEGE|a^3Q+- 3/4,u: (DEG-L-<<D,OAE(R)
   *"t^2I|^3^3QYEN[CURW noauto DEGN 1/4AE)!C

   /etc/fstab AE(R) *CUR-o(R)e-a-o(R)ae|!|pCURU!G

 device       /mount-point fstype     options      dumpfreq     passno

   device

           ,E,m|W-oU (,O,E,mYEN^2P:.-u-a-o|s|b)!C ,O+-! 1/2D-DEGN
           3/4\ uU 18.2 ,`.

   mount-point

           AE(R) *"t^2In+- 3/4,u:"`i-a-oYENO/?y
           (,OYENO/?yYEN^2P:.-u-a-o|s|b)!C

   fstype

           AE(R) *"t^2IAth<<NOT!A^3oNOTOnP:C,u^1 mount(8) -a-oDEGN
           1/4AE!C FreeBSD ^1w^3]-a-oAE(R) *"t^2INOTO ufs!C

   options

           YENiAA-aYENi 1/4g-a-oAE(R) *"t^2IYENI
           rw!A|ODEGssAA-a-a-oAE(R) *"t^2I<<hNOTOYENI
           ro!A<<a+-uo/>>YnAUYENiYENHYEN["a:YENL?iP:u!C
           +-`"-L--a-o?iP:u|p noauto NOTOYENI|bCUR-L-n(c)oP:}
           3/4-:^1Lu{CURCUR|UDEGE-a-o+- 3/4,u:-a-oAE(R) *"t^2I!C
           "a:YENL?iP:uYENiDEGN 3/4\ mount(8) >>!(c)u!C

   dumpfreq

           dump(8) YENN|^1P:uYENO/"M(c)w"-o"C,AE(R) *"t^2I>>YnP:E|L!C
           |p-aG^3o(R)ae-aAAYENO<<hYENH^1sNOTDEG^1w^3]E!C

   passno

           ^3oOP:uYENO/"M(c)wAE(R) *"t^2IAENOTd-a-oP:P:S:C,!C
           ^1i(c)on,o^1LAENOTd-a-oAE(R) *"t^2I!AYEN|I-a-o passno
           En^3]NOTDEG^1s!C (R)UAE(R) *"t^2I-a-o passno
           EA^3^3]NOTDEGCUR@
           (|]NOTDEG>>YnCURn(c)O|^3"a:YENL-a-oAUnYENyAENOTd)!A|O"a:YENL-a-oAE(R)
           *"t^2I-a-o passno EA^3,On^3]+-oCURnCUR@CURj!C Y|^3|hOAE(R)
           *"t^2I"a|^3NOTU|P-a-o passno E!A<<h fsck(8)
           .|,OuUYEN|ae|a(|p-aGYENi-`a-a-o,U:)AENOTd^3o"C,AE(R)
           *"t^2I!C

   S:o|hAo:(c)o /etc/fstab AE(R) *(R)ae|!CURI?iP:u-a-o,eDEGT
   1/2D-DEGN 3/4\ fstab(5) >>!(c)uCURaaYENo!C

     --------------------------------------------------------------

  3.6.2. mount <<u:YENO

   mount(8) <<u:YENONOTO(R)^3"O+- 3/4,u:AE(R) *"t^2IYENI-a-o!C

   DEGoYEN>>-a-o 3/4THS:@<<u:YENO(R)ae|!|pCURU:

 # mount device mountpoint

   |b mount(8)
   ,I+-|^3'-L-"`iCUR@CURjDEGi-a-o?iP:u!ACUR-L-^1L^3I+-`YENI-a-o'NNOTO^3o"C,!G

   +- 3/4,u:?iP:u

   -a

           S:a /etc/fstab ,I+-(c)O|^3AU"S|^3^3Q+- 3/4,u:!B"S|^3^3Q
           1/4D-DEGO|" !S:noauto!" |OYENB"S|^3YENI -t
           +-AEDEG-L--a-oAE(R) *"t^2I+- 3/4,u:DEG_"O!C

   -d

           DEGo|ae(c)O|^3-a-oDEGES:@!A|yNOTOCUR-L--u-a-oYENh(c)IYENs+-
           3/4,u:-a-o system call!C ^3oO?iP:u(c)M -v
           .fDEGt(R)^3"O+-A'u mount(8)
           +-NnDEGuCURDEG>>oDEGES:@(R)E<<U:|nYENI!C

   -f

           +-j-c-+- 3/4,u:CUR-L-DEG(R)^2b-a-oAE(R) *"t^2I
           (|MAI)!A(c)INOTOYENI"O+-j"i"u(R)o/ 1/4gCURJAAv (S:aAE(R)
           *"t^2I-a-o+- 3/4,u:-aNOT-oA+-qYENi|s"uAAU:|"DEGssAA-a)!C

   -r

           YENIDEGssAA-a-a-oCURe|!+- 3/4,u:AE(R) *"t^2I!C
           ^3oO?iP:u(c)M|b -o ?iP:uCURCUR<<u:(c)w ro (|b FreeBSD
           5.2CURS:<<e-a-o-a(c)YEN>>NOTOYENI rdonly) DEGN
           1/4AENOTOCUR@ 1/4E-a-o!C

   -t fstype

           YENI<<u:(c)w-a-oAE(R) *"t^2I<<NOT-oA (fstype) "O+-
           3/4,u:<<u:(c)w-a-oAE(R) *"t^2I!A(c)INOTO|b|^3 -a
           ?iP:u(R)EYENu+- 3/4,u:<<u:(c)w<<NOT-oA-a-oAE(R) *"t^2I!C

           ^1w^3]-a-oAE(R) *"t^2INOTO !S:ufs!"!C

   -u

           S:o.sAE(R) *"t^2I-a-o+- 3/4,u:?iP:u!C

   -v

           AAaYENU:,u,O^2O,eDEGT!C

   -w

           YENHYENi|s"u-a-o 1/4O|!+- 3/4,u:AE(R) *"t^2I!C

   -o ?iP:u<<a+-.|+-uuUYENH^3r,^1CURA^1j-a-oDEGN 1/4AE!A"O|p!G

   noexec

           CUR-L-CUR^1^3\|b^3oOAE(R) *"t^2ICURWDEGo|aeCURGP:i|`iu{|!
           1/2X!A ^3oCUR]NOTOCUR@OAEZ|^3YENI-a-o|wYENth?iP:u!C

   nosuid

           CUR-L-,N-aRAE(R) *"t^2ICURW-a-o setuid (c)I setgid -oX
           1/4D-!A ^3oCUR]NOTOCUR@OAEZ|^3YENI-a-o|wYENth?iP:u!C

     --------------------------------------------------------------

  3.6.3. umount <<u:YENO

   umount(8) <<u:YENO-a-oDEGN 1/4AEYENiYENHNOTO+- 3/4,u:AI
   (mountpoint)!A,E,m|W-oU!AYENHCURI -a (c)INOTO -A uYEN?iP:u!C

   YEN[CURW -f YENiYENH+-j"i"o/,u:!AYEN[CURW -v
   <<hNOTO.|AAaYENU:,O^2O,eDEGT!C n-a`.N-a-oNOTOCUR@-e"O>>!YENI -f
   "ACUR-L-NOTOO|nYEND.N!A+-j"i"o/,u:AE(R)
   *"t^2I|^3YENi-`a.|^3y|"^1q,-L-.i 3/4-:!A (c)I-aI.lAaAE(R)
   *"t^2ICUR-o-a-o,e(R)AE!C

   -a (c)M -A NOTOYENI"O"o/,u:(c)O|^3CURw+- 3/4,u:-a-oAE(R)
   *"t^2I!AYENtYEN~AUYENiYENHYENI -t
   "O<<u:(c)wn"o/,u:-a-oNOTOth"C,-oO/Ath-a-oAE(R) *"t^2I!C
   n-a`.N-a-oNOTO -A "ACUR-L-.|,O^1I"o/,u:(R)UAE(R) *"t^2I!C

     --------------------------------------------------------------

3.7. u{S:C,

   FreeBSD
   NOTOCUR@O|hCURu-a-oS:@.~"t^2I!ACUR]'NNOTO>>!|b|PCUR@(R)EP:!CUR-oYENiYENHP:]P:W^1LCUR@Ou{|!!C
   "CCUR@OYEN?|b-aa(R)EP:!P:]-a-ou{|!'NYENsDEGu u{S:C, (process)!C
   +-zCURU-a-o"CO<<u:YENO^3-L-|U:CURO:.|P:}+-OCUR@O.s-a-ou{S:C,!A
   |O|^3"C,"t^2Iu{S:C,NOTOCUR@-a
   1/2|bP:]YENH-ou<<u"t^2IYEN?+-`^1BS:@-a-o!C

   "CCUR@Ou{S:C,^3-L-|^3CUR@OCUR-L-<<AD--a-o 1/4AE|rYENsDEGu process
   ID !A(c)I-oUNOTDEG PID !A|OYENB'N^1^3AE(R) *CUR@
   1/4E!A"CCUR@Ou{S:C,CUR]|^3 3/4O:|^3-aICURI,s^2O!C 
   3/4O:|^3-aICURI,s^2O-a-o,eDEGTNOTOYENI"O"M(c)wCURDEG>>oAE(R)
   *(c)I,E,mNOTO^3oOu{S:C,YENiYENHP:}+-O-a-o (<<e+-|^3'-L-"`i^1LAE(R)
   *AAv)!C CURj^3!YEN-:-a-ou{S:C,^3-L-|^3CUR-:u{S:C,!C
   CUR-:u{S:C,NOTOP:}+-O^3oOu{S:C,-a-ou{S:C,!A"O|p!G+-z^1i shell
   ?eCURJ<<u:YENO!Ashell
   YEN>>"'NNOTOCUR@Ou{S:C,!A|O+-zDEGo|ae-a-o<<u:YENOCUR]NOTOu{S:C,!C
   "CCUR@O+-zYENI^3o-oO/CURe|!P:]-a-ou{S:C,-a-oCUR-:u{S:C,^3-L-NOTO
   shell!C |^3CUR@O-SS:O-a-ou{S:C,YENsDEGu init(8) NOTOO"OYEN~!Cinit
   YENA>>.NOTO^2A:CUR@Ou{S:C,!A(c)OYENHYENL-a-o PID CUR@-a
   1/2^3-L-.|NOTO 1!C |b FreeBSD P:} 3/4-:-a-o(R)EO init
   .||UDEGE|a^3Q kernel P:}+-O!C

   nNOTY"t^2IDEGo|aeCURCUR-a-ou{S:C,!A|^3"aONOTU.i|^3YENI-a-o<<u:YENOYENiYENI!G
   ps(1) YENHCURI top(1)!Cps
   <<u:YENONOTOYENI"O|CYENXYEN?|bDEGo|aeCURS:u{S:C,!A|OYENBYENiYENH"qYEN|I-a-o
   PID!BYENICURF|hCURO:DEGO
   3/4D-AAe!BDEGo|ae-a-o<<u:YENO|W-oUCURI"a:<<aCURS:DEGN
   1/4AENOTOCURDEG>>ouYENuYEN!C top
   <<u:YENO<<hNOTOAAaYENU:(c)O|^3YEN?|bDEGo|ae-a-ou{S:C,!A "AYENB
   1/4AENOTiA:AS:o.sCUR@|,!C|]|^1+-zYENiYENHCURNOTDEGE|!-a-oAE[NOTY+-z-a-o^1q,-L-YEN?|bDEGuCURDEG>>o!C

   |b^1w^3]-a-o+-!-apCURU!Aps <<u:YENOYENu.|AAaYENU:+-z(c)O
   3/4O:|^3-a-o-a-ou{S:C,!C "O|p!G

 % ps
   PID  TT  STAT      TIME COMMAND
   298  p0  Ss     0:01.10 tcsh
  7078  p0  S      2:40.88 xemacs mdoc.xsl (xemacs-21.1.14)
 37393  p0  I      0:03.11 xemacs freebsd.dsl (xemacs-21.1.14)
 48630  p0  S      2:50.89 /usr/local/lib/netscape-linux/navigator-linux-4.77.bi
 48730  p0  IW     0:00.00 (dns helper) (navigator-linux-)
 72210  p0  R+     0:00.00 ps
   390  p1  Is     0:01.14 tcsh
  7059  p2  Is+    1:36.18 /usr/local/bin/mutt -y
  6688  p3  IWs    0:00.00 tcsh
 10735  p4  IWs    0:00.00 tcsh
 20256  p5  IWs    0:00.00 tcsh
   262  v0  IWs    0:00.00 -tcsh (tcsh)
   270  v0  IW+    0:00.00 /bin/sh /usr/X11R6/bin/startx -- -bpp 16
   280  v0  IW+    0:00.00 xinit /home/nik/.xinitrc -- -bpp 16
   284  v0  IW     0:00.00 /bin/sh /home/nik/.xinitrc
   285  v0  S      0:38.45 /usr/X11R6/bin/sawfish

   |b^3oO 1/2d"O,IYENiYENHNOTY"`i ps(1)
   -a-o?eYENXCURA|"|n'XOA:ae|`i!C PID 'NNOTO<<e+-|^3'-L-"`i-a-o
   process ID!C PID -a-oCURADEGtNOTO+-q 1 P:}(c)lCUR@-a 1/2"`i
   99999!A|p-aGYENIS:^1-a-o,U:CURS.|AP:|^"O<<AYP:}(c)lCURADEGt (Y,O
   PID CURw,g|bYENICURF!A<<h PID CUR-L-.|<<.sCURADEGt)!C TT
   A:ae|`iNOTO<<u:^3oOu{|!|bthO tty
   CURWDEGo|ae!A|b^3o,IYENiYENHYENy(c)?^2CURCUR-L--oTH!CSTAT
   NOTOu{|!-a-o-aNOT-oA!ACUR]YENiYENHYENyCUR-L-n-oTH!CTIME
   NOTO^3oOu{|!|b CPU
   CURWDEGo|ae-a-o(R)EP:!!X!X^3o^3q+-`CUR-L-NOTOu{|!A`|@-aa-a-o(R)EP:!!A
   |]NOTDEG.i+-zP:}(c)lDEGo|aeu{|!<<a!ACURj^3!YEN-:-a-ou{|!|b CPU
   CURWDEGo|ae<<e.|YENy-aaCURWCUR-L-CURO:(R)EP:!uYEN<<Y !C
   ^3I<<a!ACOMMAND NOTODEGo|ae^3oOu{|!-a-o(c)RYENO|C!C

   ps(1)
   |^3'XOCUR-L-|P-a-o?iP:u^2O|XYENiYENHYENI"OAAU:S:oAAaYENU:YENX"O-a-o,eDEGT!A"a:CURCURCUR@O^3I|^3YENI-a-o^2O|XNOTO
   auxww!C a
   YENiYENHAAaYENU:(c)O|^3YEN?|bP:]-a-ou{S:C,-a-o<<u:YENO!ACUR-L-YENuNOTO+-z|UCURw-a-o!C
   u <<hNOTOAAaYENU:u{S:C,-a-o 3/4O:|^3-aI|W-oUYENHCURIDEGO
   3/4D-AAe"IYENI+-!-ap!C x YENiYENHS:a daemon u{S:C,AAaYENU:YENX"O!A
   |O ww YENiAAy ps(1) AAaYENU:YENX"COu{S:C,S:^1 3/4a-a-oCUR-o(R)e!A
   |OCUR-L-P|]^1L-ao/|O^3Q?A^1o-oI+- 1/4CURF!C

   top(1) CUR]|^3Ath|u:-a-o?eYENX!C CUR@-e-a-o+-!-apNOTY^1^3NOTO^3o
   1/4E!G

 % top
 last pid: 72257;  load averages:  0.13,  0.09,  0.03    up 0+13:38:33  22:39:10
 47 processes:  1 running, 46 sleeping
 CPU states: 12.6% user,  0.0% nice,  7.8% system,  0.0% interrupt, 79.7% idle
 Mem: 36M Active, 5256K Inact, 13M Wired, 6312K Cache, 15M Buf, 408K Free
 Swap: 256M Total, 38M Used, 217M Free, 15% Inuse

   PID USERNAME PRI NICE  SIZE    RES STATE    TIME   WCPU    CPU COMMAND
 72257 nik       28   0  1960K  1044K RUN      0:00 14.86%  1.42% top
  7078 nik        2   0 15280K 10960K select   2:54  0.88%  0.88% xemacs-21.1.14
   281 nik        2   0 18636K  7112K select   5:36  0.73%  0.73% XF86_SVGA
   296 nik        2   0  3240K  1644K select   0:12  0.05%  0.05% xterm
 48630 nik        2   0 29816K  9148K select   3:18  0.00%  0.00% navigator-linu
   175 root       2   0   924K   252K select   1:41  0.00%  0.00% syslogd
  7059 nik        2   0  7260K  4644K poll     1:38  0.00%  0.00% mutt
 ...

   ?eYENX-a-o,eDEGTCURA|""aO^3!YEN-:!CP:}AY (<<eCUR|ae)
   "qYENX^3I-anCUR@Ou{S:C,-a-o PID!B"t^2IYENS:!t,u:
   ("t^2I|^3|h|-L-?y-a-o'u,O)!B"t^2I-a-oP:} 3/4-:(R)EP:!
   (+-qCURW|,<<P:}-oaDEG_) YENHCURI^2{|b-a-o(R)EP:!uYEN!C
   |bP:}AY,I+--a-o"a:YENL
   1/4AE|rCURAS:ONOTO|bA?|^3|hCURO:u{S:C,YEN?|bDEGo|ae
   (|bYEN>>"OCURCURNOTDEG47)!B|^3|hCURO:DEGO 3/4D-AAeCURI swap space
   ^3QYENeYENICURF!AAU|^3'NNOTO"t^2ICURAS:O-aaCURF|hCURO:(R)EP:!|bCUR-L-|P-a-o
   CPU -aNOT-oACURW!C

   +-uCURU"O-a-o^3!YEN-:NOTOYENN|n'XOA:ae|`i(c)O-oc|"!A(c)M ps(1)
   ?eYENX-a-o,eDEGTAth|u:!C 'N|p|P<<e"O!A+-zYENiYENHNOTY"`i
   PID!B"IYENI-aI|W-oU!BCPU
   -aaP:O-a-o(R)EP:!YENHCURIYEN?|bDEGo|ae-a-o<<u:YENO!C top(1)
   |b^1w^3]-a-o+-!-apCURUAU.|S:iP:D+-zu{S:C,YENI+-
   1/4CURF|hCURO:-a-oDEGO 3/4D-AAe-aAAP:!!C
   |b^3oAa:.|CURA|""aA:ae!ACUR@ONOTOA`YENIP:q (total
   size)!AYENtCUR@ONOTO^1e>>UYENIP:q (resident
   size)!X!XA`YENIP:qNOTO<<u:^3oOA^3YENIu{|!>>Yn-a-oDEGO
   3/4D-AAe-aAAP:!!A
   |O^1e>>UYENIP:q<<hNOTO<<u:^1e>>UCURW,Ou{|!-a-oDEGO
   3/4D-AAe"IYENIP:q!C |b^3oO"OCURl,I+-+-zYENiYENHNOTY"`i Netscape(R)
   nCURF'XYENG"`i 30 MB -a-o RAM!A|yNOTOYENu|^3YENI"`i 9 MB!C

   top(1) "C^1j 2 NOTiA:A.||UDEGES:o.sAAaYENU:CUR-o(R)e!AYENiYENI s
   ?iP:u"OS:iAAU:P:!^1j-a-o(R)EP:!!C

     --------------------------------------------------------------

3.8. Daemon!B<<H,^1CURI^2 *CURiu{S:C,

   .i|bDEGo|aeCURaa(R)N 1/2s?e
   3/4^1(R)E!A+-zYENiYENH<<U:(R)e(c)o:|a"IYENIYEN|!AYENsYEN|AA-a"uAE(R)
   *(c)INOTOCURDEG>>o-a-o!C YENiYENH^3o 1/4EDEGuNOTO|]NOTDEG 1/2s?e
   3/4^1|^3'-L-"N^3o"C,YEN\-`a!A AU|^3'NNOTO 1/2s?e
   3/4^1"I-ath|bCUR@O^2 *-oY 3/4-: (Terminal) CURS:CURW!C
   |^3"C,u{|!"ACUR-L-NOTO^3]p|"CUR@-a
   1/2|b+-u|NOT"IYENI-aI-a-o?eCURJ-a-o!A
   (c)OYENHYEN|I|bCUR@P:}(c)lDEGo|ae-a-o(R)EO'N+-q^2 *-oY
   3/4-:A_P:}CURF!C "O|p>>!!A -ooP:|o/-aA 3/4^1
   3/4aCURN^3-L-|b|^A^3-ooP:CURe+--a-on"D!AYEN|^3q+-`CUR-L->>Yn+-z?eCURJYENo|o-aF|e!C
   YENtYEN~!A^1^3NOTOS:a<<H+-qCUR@O-,P:C,DEGe"`iYENtCUR@O-,-a-ou{|!!ACUR]NOTO^3o-oO/Ath<<NOT-a-oA^3YENIu{|!!C

   S:UIS:a^3o-oO/u{|!-oUS:@ daemon!C Daemon ('cAA]!B|uAA@-<<)
   NOTOS:AEA 3/4-<<,U:CURCUR-a-o"CUR|a!GI-c-ICUR-L-A:Y(c)ou
   1/2"}DEG}Ac,(c)I",'cDEG}Ac,!ANOTO|uAA@-a-oCURp-oeAEF!C
   CURjPCURW"O>>!I-c-I'NNOTO|b'ACURHAthDEGuCUR@"C,|^3YENI-a-o"AE+-!!A
   ,oCURuCURN-a-o-ooP:|o/-aA 3/4^1(c)INOTOP:lYENo|o/-aA
   3/4^1<<U:^1^3!C ^3oCUR]'NNOTONOTDEG|o BSD
   -a-o|N^2>>-a<<!A-ao/'AYENH"O^3-L-NOTOCUR@DEG|NOTiuU||YENNOT
   3/4c(R)^3uUCURTCURe-O-a-oS:O: 1/4O:CURp'cAA]-a-o`i|]!C

   ^3q+-`"O>>! deamon u{|!-a-o|W|r<<a+-^3-L-.|YEN[CUR@O|rYENA
   !S:d!"!C BIND NOTO Berkeley Internet Name Domain -a-oAY 1/4g
   (|y^1e>>UCURWDEGo|ae-a-ou{|!|W-oUNOTO named)!BApache -ooP:|o/-aA
   3/4^1-a-ou{|!|W-oUNOTO httpd!B|L-ai 3/4-:-aADEGEu{|!NOTO
   lpd!A"I|^1Ath+-A!C
   ^3oNOTO^2ss-oDYENI-ak!A"A"S|^3uw(c)E^3W(c)w!A"O|p Sendmail
   YENDn-a-o+-H<<H daemon NOTOYENsDEGu sendmail |OCUR-L-NOTO
   maild!A,o+-z.Q^1^3-a-oCUR-L-CUR@ 1/4E!C

   |^3"C,(R)EO.|>>Yn,oNOTYO daemon u{S:C,. 3/4^3q!A ^3o"C,.
   3/4^3qNOTO^3z^1L(c)O? *-a-o<<H,^1(signal)"OP:C,>> 1/4u^1,O daemon
   u{S:C,((c)INOTO"a:YENLDEGo|aeCURCUR-a-ou{S:C,)!C
   AC,YENNDEGeYENX<<H,^1!A+-zYENiYENH(c)MCUR@O daemon
   ((c)INOTOYENo|oCUR@OYEN?|bP:]-a-ou{S:C,) . 3/4^3q!C
   <<H,^1|^3<<U:|h-oO/!X!X|^3"C,|^3-S(c)w-a-o.N,q!A|^3"C,<<hNOTO.|YENNA^3YENIu{|!"O,NAA-a!C
   A^3YENIu{|!-a-o>>!(c)uCURaaYENo.|S:iP:D+-z,Ou{|!NOTO|p|o,NAA-a<<H,^1-a-o!C
   +-zYENu-`aDEGe<<H,^1u^1+-z 3/4O:|^3-a-ou{S:C,!ADEGe kill(1) (c)I
   kill(2) -a-o<<H,^1u^1S:OCURH-a-ou{S:C,NOTOCUR-L-^3QCUR^1^3\-a-o!C
   CUR-L-^1L root
   CUR-L-"u:|^1"i!AYENLYENiYENHDEGe<<H,^1u^1YENo|oCURH-a-ou{S:C,!C

   FreeBSD YEN>>"|bNOTY"C,+-!-apCUR].|DEGe<<H,^1u^1A^3YENIu{|!!C
   DEG^2^3]|^3OA^3YENIu{|!
   1/4g+-o<<U:A:e!AuM<<aYENo/^1In|s"uYEN|CUR-L-,O,I-a-oDEGO
   3/4D-AAe-a-o(R)EO!AFreeBSD .|DEGeCUR@O Segmentation Violation
   <<H,^1 (SIGSEGV) u^1^3oOu{S:C,!C
   CURS|p-aG|^3CUR@OA^3YENIu{|!YENICURF alarm(3) -a-o system call
   n"D"t^2I|b^1LCUR@NOTq(R)EP:!CURS:<<aYENsYENLCUR@CURU!A(R)EP:!"`iCURF-a-o(R)EO
   3/4xA:A-a-o<<H,^1 (SIGALRM)
   'N.|^3QDEGeYENXCURF!A"a:YENL-a-o"I|^1Ath+-A!C

   SIGTERM and SIGKILL ^3o"aO<<H,^1YENiYENH(R)^3"O^2 *CURiu{S:C,!C
   YENI SIGTERM
   u^2S:ou{S:C,NOTOCURn,u|^3AS:>>-a-a-oCURe|!!A,Ou{S:C,.|(R).(R)>>
   (catch) ^3oO<<H,^1|OCURF,N"`i+-z.QnS:aYENLAo:+- 1/4!C
   +-uuUCURU"OYEN|.|S:aYEN||UCURwP:}-a-oDEGO?yAE^3q^3qAo:+- 1/4!A
   uM<<a|bAo:+- 1/4u{S:C,CURS:<<eu^2S:o+- 1/4CURaAa:-a-oCURuS:@!C
   |bNOTY"C,+-!-apCURUu{S:C,|^3YENi-`a.|,ES:@"SNOTY"-L-
   SIGTERM!ADEG^2|pYEN|YEN?|bDEGuCUR@"C,CUR-L--`aCURCURA_-a-oCURuS:@-a-o,U:!C

   SIGKILL 'N"S|^3?`i-ak^3Qu{S:C,(c)?^2CURCURF!C
   ^3oNOTOCUR@O!S:S:U-oTHS:AYEN?|b.F^1A!A^2{|b'Nu^1S:UDEG+-CURU"O!"-a-o<<H,^1!C
   |p-aG+-zDEGeCURF SIGKILL <<H,^1u^1NOTYOu{S:C,!AFreeBSD
   +-N.|S:aYEN|DEG+-+- 1/4[4]!C

   ^3o"C,NOTO"a:YENL+-z|^3YENi-`a.|nYENI"`i-a-o<<H,^1!G
   SIGHUP!ASIGUSR1!AYENHCURI SIGUSR2!C
   ^3o"C,NOTO^3qYENI-a-o<<H,^1!A.iDEGeYENX(R)ECUR-L-|P-a-oA^3YENIu{|!.||^3CUR-L-|P-a-oCURIA^3!C

   DEG^2^3]+-zS:oDEGECURF+-z-a-o-ooP:|o/-aA 3/4^1-a-o^3](c)wAE!X!X
   +-z.QnYENs-ooP:|o/-aA 3/4^1YENh<<.sAA-a"u^3](c)wE!C
   +-zYENiYENHAo:^3NOT<<a|A<<.s+-ODEGE
   httpd!A|yNOTO^3o>>oDEGu.|^3y|"-ooP:|o/-aA 3/4^1
   1/4EDEG+--aADEGECUR@NOTq(R)EP:!!A ^3o
   1/4ECURlYENi-`aCUR-L-CURO|n!C CURj^3!YEN-:-a-o daemon ^3-L-
   1/4g|".|YENh|^A^3 SIGHUP!C
   .i|NOT"`i^3oO<<H,^1CURS:<<a!AYEN|I.|YENh<<.sAA-a"u|UCURw-a-o^3](c)wAE!C
   |]|^1+-zYENiYENHYENIDEGe SIGHUP <<H,^1"O"uYENNAo:+- 1/4<<P:}!C
   CURS|]NOTDEG"S|^3 1/4D-.C,|b^3W
   1/2d|p|o|^A^3^3o"C,<<H,^1!ACUR-L-|P-a-o daemon
   YENi-`a.||^3CUR-L-|P-a-o|aeNOTDEG!A(c)OYENH|^3-oADEGY-a-o,U:
   1/2D-YENy 1/2T>>{"AA 1/2 3/4\ deamon -a-o>>!(c)uCURaaYENo!C

   <<H,^1NOTOYENN kill(1) <<u:YENODEGeYENX-a-o!A|p 1/2d"O(c)OYENU:!G

   DEGe<<H,^1u^1u{S:C,

   ^3oO 1/2d"O+-N.|YENU: 1/2d|p|oDEGeCUR@O<<H,^1u^1 inetd(8)!C inetd
   -a-o^3](c)wAENOTO /etc/inetd.conf!A|O inetd .||b|NOT"`i SIGHUP
   -a-o(R)EO<<.sAA-a"u^3oO^3](c)wAE!C

    1. S:a:YENX+-z.QnDEGe<<H,^1-a-o"-oOu{S:C,-a-o ID!C +-z.|YENI"`i
       ps(1) YENHCURI grep(1) ^3o"aO<<u:YENO!C grep(1)
       NOTOYENI"O|b?eYENXCURCUR.j'M!A S:a:YENX+-z<<u:(c)w-a-o|r|e!C
       ^3oO<<u:YENONOTOYENNCUR@-e"IYENI-aIDEGo|ae!A|O inetd(8)
       NOTOYENN root DEGo|ae!A(c)OYENH|b"IYENI ps(1) (R)E>>YnYEN[CURW
       ax ?iP:u!C

 % ps -ax | grep inetd
   198  ??  IWs    0:00.00 inetd -wW

       |]|^1YENi-a 3/4 inetd(8) -a-o PID NOTDEG 198!C
       |bNOTY"C,+-!-apCURU grep inetd
       ^3oO<<u:YENOYEN>>"CUR].|YENX^2{|b?eYENX,I!C ^3oNOTO|]NOTDEG
       ps(1)
       CURDNOTOS:a:(c)O|^3DEGo|aeCURCUR-a-ou{S:C,-a-oCURe|!^3y|"-a-o!C

    2. YENI kill(1) "ODEGe<<H,^1!C CURS|]NOTDEG inetd(8) NOTOYENN
       root DEGo|ae-a-o!A+-zYEN^2P:.YENI su(1) CURA'<<|" rootYENy!C

 % su
 Password:
 # /bin/kill -s HUP 198

       CUR@-e+-!-ap^1iCURj|h 1/4AE UNIX <<u:YENO"OA?!A.i kill(1)
       DEGo|ae|"YEN\(R)E"ACUR-L-.|?eYENXYENo|oDEGT(R)S:!C
       DEG^2^3]+-zDEGeCUR@O<<H,^1u^1NOTYOCUR-L-NOTO+-z(c)O
       3/4O:|^3-a-ou{S:C,!A "-o>>o+-z'N.||Y"`i^3oO?u>>~DEGT(R)S:!G
       !S:kill: PID: Operation not permitted!"!C |O|p-aG+-zYEN'?u PID
       -a-o,U:!A"-o'N.|S:a<<H,^1DEGeu^1?u>>~-a-ou{S:C,!C ^3o
       1/4EYENi-`a.|<<U:AV!A
       CUR-L-^1L|p-aG+-zDEG-:(c)-^1B-a-o,U:!AYENi-`ae|n'NYENuNOTOS:a<<H,^1DEGeu^1CUR@O<<D"IYENICURCUR-a-o
       PID!A"-o+-z'NYENu.|NOTY"`i !S:kill: PID: No such process!"
       |OCURw!C

         NOTDEGCURDEG>>oYENI /bin/kill!H: <<U:|h shell
         |^3'-L-"NCUR-o<<O/-a-o kill <<u:YENO!C CUR]'NNOTO>>!^3o-oO/
         shell .|-a 1/2+-uDEGe<<H,^1!A|OCUR-L-NOTODEGo|ae /bin/kill!C
         ^3o 1/4ENOTOAEZCURe<<K-a-o"S?uDEGO!A|yNOTOCUR-L-|P-a-o shell
         .||^3CUR-L-|P-a-o>>y-ak"O<<u:(c)w<<H,^1-a-o|W-oUuYEN!C
         >>P"a:^1A,OYENhS:aYEN|I^3q^3q
         3/4C,.|!ACUR-L-|p'N^3ae-A-a-o-a 1/2+-uYENI /bin/kill ...
         S:a!C

   nDEGe"a:YENL-a-o<<H,^1-a-o,U:CUR]NOTO<<D+-`Ath|u:!A'Nuo/>>YnS:a<<u:YENOCURCUR-a-o
   TERM (c)I KILL 'A'<<+- 1/4S:YYENi!C

     <<n: AH<<KS:`iCUR@O"t^2ICURCUR-a-ou{S:C,uM<<aS:aYENLNOTaa+-
     1/4"ACUR-L-NOTOO|nYEND.N!C -SS:ONOTO init(8)!A process ID
     1!ACUR@O<<D+-`-SS:O-a-ou{S:C,!C DEGo|ae /bin/kill -s KILL 1
     -a-ou^2-aG'NNOTO"t^2IYENss"eAo: 3/4-:!C |]|^1|b+-z<<o:CURU
     Return nDEGo|ae kill(1)CURS:<<e!A  1/2D-CUR@(c)wnDEGO+-o|A|,
     1/2T>>{+-zCURU-a-oDEGN 1/4AE!C

     --------------------------------------------------------------

3.9. Shells

   |b FreeBSD CURCUR!A<<U:|hCURe+-`-a-oCURuS:@NOTO|bCUR@OYENsDEGu
   shell -a-oCURaa|rCURP:+-CURCURS:^1|"-a-o!C Shell
   -a-oYENDnCURuS:@'NNOTO+-q?eCURJCURCUR|NOT"`i(c)RYENO"ADEGo|aeYEN|I!C
   ^3\|h shell
   CUR]|^3CUR-o<<O/CUR@"C,|^3S:U(c)oCURe+-`CURuS:@-a-o<<u:YENO!A
   ^1^3NOTOAE(R) *-oTH^2z!BAE(R) *CURn^1i!B(c)RYENO|C
   1/2s?e!B<<u:YENOYEN"P:DEGYENHCURIAo^1OAAU: 1/4AEuYEN!C FreeBSD
   |^3CUR-o-athCURF'XO shell!A^1^3NOTO sh!A Bourne Shell!AYENHCURI
   tcsh!AS:i"}-a(c)-a-o C-shell!C AU|^3^3\|h"a:YENL-a-o shell
   YENiYENH+-q FreeBSD Ports Collection CURCUR"u+-o!A^1^3NOTO zsh
   YENHCURI bash uYEN!C

   +-zYENIthO shell (c)O!H "a:^1e"COCURH-a-o^3ss|n^3-L-CUR-L-CUR@
   1/4E!C |p-aG+-zNOTOCUR@O C u{|!^3]p(R)v!A"-o^1i(c)o"IYENI^1^3NOTO
   tcsh ^3o-oO/ C-like -a-o shell YENi-`a.|.P"`iNOTU.i'rS:O:!C
   |p-aGS:ANOTO+-q Linux ,o^1L"O-a-o!A(c)I-aI+-zNOTOCUR@O UNIX
   .sCURa!A"-o+-zCUR]^3\.|.QnYENI bash "O.iS:@CURaa|rCURP:+-!C
   "CCUR@O shell
   ^3-L-|^3|UCURw?W-SCURS:^3B!A|U:(c)o^3o"C,-SAI-`aCUR-L--`aDEGt|X+-z-a-oCURuS:@Ao^1O!H
   "-o'NNOTO+-z?i 3/4U: shell -a-o<<AICURF!C

   AE|W|UDEGE,E>>o'NNOTO+-`"-L--a-o shell YEN\-`a!C
   -oYENy?eCURJ<<u:YENO(c)IAE(R)
   *-a-o<<e'XO|rYENA!A^3o(R)E^3q+-`+-zYENu>>Yn<<o:CURU Tab
   Aa:!A+-uCURU"O shell 'N.||UDEGES:a<<u:YENO(c)INOTOAE(R) *|W-oU^3N
   3/4l-a-o^3!YEN-:,E>>o!C DEG^2^3]+-z|^3"aOAE(R) *CURAS:OYENsS:@
   foobar CURI foo.bar!C ^2{|bnS:R+- 1/4
   foo.bar!A"-o>>oYENiYENH?eCURJ!G rm fo[Tab].[Tab]

   Shell .||LYENX^3oO!G rm foo[^1I].bar!C

   [^1I] NOTO console -a-oAAT^1a!A^3o^1I-a-oCUR@AnNOTO shell
   |bS:iP:DS:U>>!YEN|"S|^3?`i-akS:^1YENth|UDEGE,E>>oAE|W!A|]NOTDEG|^3CUR-L-YENuCUR@OAE|W^2AA|X+-o/YENo!C
   foobar (c)M foo.bar ^3-L-NOTO fo
   P:}AY-a-oAE|W!ACUR-L-^1LYEN||U:CURO:YENiYENH,E>>o"`i foo!C
   |p-aG+-z+-uuU?eCURJ . uM<<a|A<<o: Tab CUR@|,!A"-o shell
   'N-`aDEG-:'A+-zS:a^3NCURU-a-oAE|WP:n-o!CURF!C

   Shell -a-oYENtCUR@P:u-SAINOTO"IYENICURFAo^1OAAU: 1/4AE!C Ao^1OAAU:
   1/4AENOTOYENHAAU:
   1/4AE>>PAa:E!]variable/key!^-a-o^1iA^3Ao:<<YAx|s(c)o shell
   -a-oAo^1O-aAAP:!CURCUR!AYENo|oYENN shell
   (c)O^2-L-YENI-a-ou{S:C,^3-L-YENiYENHAA-a"u|^1-aAAP:!!A
   |]|^1^3oO-aAAP:!Ax|sCURF^3\|hu{S:C,-a-o^3](c)w^2O-oA!C
   |b|^1-athCURW CUR@YEN-:+-`"-L-Ao^1OAAU:
   1/4AE>>P"a:^2[,q-a-o|C-ai!G

  AAU:                                 ,O^2O>>!(c)u                               
 1/4AE   
USER     YENO/<<eunCURJ-a-o"IYENI-aI|W-oU!C                                       
PATH     YENH<<_,^1!]:!^^1jP:}-a-oYENO/?y|C-ai!AYENIYENH.j'MDEGo|aeAE-a-o,o(R)|!C 
DISPLAY  Y|s|b^3oOAo^1OAAU: 1/4AE!A<<hYENN-ai X11 ^3su^2AAaYENU:                  
         3/4^1-a-o-oo,o|W-oU!C                                                    
SHELL    YENO/<<e"IYENI-a-o shell!C                                               
TERM     "IYENI-aI^2 *-oY 3/4-:-a-o|W-oU!A-`aAC,YENN|^1AAU: 1/4AES:PA_^2 *-oY     
         3/4-:-a-o-`aCURO!C                                                       
TERMCAP  Database entry of the terminal escape codes to perform various terminal  
         functions.                                                               
OSTYPE   S:@.~"t^2I-a-o-oO/Ath!A|p!GFreeBSD!C                                     
MACHTYPE YENO/<<e"t^2I(c)OYENI-a-o CPU NOT[-oc!C                                  
EDITOR   "IYENI-aIDEG 3/4|n-a-oCURaa|r 1/2s?e 3/4^1!C                             
PAGER    "IYENI-aIDEG 3/4|n-a-oCURaa|rCURAP: 3/4^1!]text pager!^!C                
MANPATH  YENH<<_,^1!]:!^^1jP:}-a-oYENO/?y|C-ai!AYENIYENH.j'M manual pages         
         -a-o,o(R)|!C                                                             

   |bCUR-L-|P-a-o shell (c)^3CURU^3](c)wAo^1OAAU:
   1/4AE-a-oCURe|!CUR]|^3(c)OCUR-L-|P!C A|"O"O>>!!A|b C-Style -a-o
   shell (c)^3CURU!A^1^3NOTO tcsh (c)M csh!AS:AYEN^2P:."IYENI setenv
   "O^3](c)wAo^1OAAU: 1/4AE!C |y|b Bourne shells (c)^3CURU!A^1^3NOTO
   sh (c)M bash!AS:A<<hYEN^2P:."IYENI export
   "O^3](c)wS:A(c)O"IYENI-a-oAo^1OAAU: 1/4AE!C
   |AA|O"OCURl"O>>!!AYn^3](c)w(c)INOTO *S:i EDITOR ^3oOAo^1OAAU:
   1/4AE!A|b csh (c)I tcsh CURU^3](c)w EDITOR ^3oOAo^1OAAU:
   1/4AENOTDEG /usr/local/bin/emacs -a-o<<u:YENONOTO!G

 % setenv EDITOR /usr/local/bin/emacs

   |b Bourne shells CURU<<hNOTO!G

 % export EDITOR="/usr/local/bin/emacs"

   CURj|h 1/4AE-a-o shell
   ^3-L-CURa:'(c)"IYENI-aI|b(c)RYENO|CCURCUR+-N $ |rCUR,(c)n|bAAU:
   1/4AECURS:<<e!AYENH"u+-oAo^1OAAU: 1/4AE-a-oE!C A|"O"O>>!!Aecho
   $TERM .| AAaYENU:YENX $TERM -a-o^3](c)wE!A^3oNOTO|]NOTDEG shell
   "u+-oCURF $TERM -a-o^3](c)wE!A "A+-N"a:P:C,u^1 echo
   AAaYENU:YENX"O!C

   Shell
   CURCUR|^3NOTY"C,-SS:O-a-o|rCUR,NOTO"O-aiYENU:-S(R)i-a-o,e(R)AE!AS:UI+-N"a:-oUS:@
   meta-characters!C "a:CURCUR^3I+-`"-L--a-oNOTO *
   |rCUR,!AYENLYENN-aiCURFAE|WCURCUR-a-oYENo.N|rCUR,!C
   ^3o"C,-S(R)i|rCUR,YENiYENHYENI|bAE|W(R)iP:}!]filename
   globbing!^CURW!AA|"O"O>>!!A?eCURJ echo * .|(c)M?eCURJ ls
   +-o"`i'XYENGNOTU|P-a-ou^2-aG!A^3oNOTO|]NOTDEG shell
   .|+-N(c)O|^3^2AA|X * |rCUR,-a-oAE(R)
   *P:C,"`i(c)RYENO|CCURW!A|AYENN echo AAaYENU:YENX"O!C

   NOTDEGCURFA *S:K shell
   A`aA:P:^3o"C,-S(R)i|rCUR,!AS:UIYENiYENH|b^3o"C,-S(R)i|rCUR,<<e(c)nCUR@OCURI+-
   * 1/2u (\) |rCUR,"IYENLI,o^2ae(escape) shell
   -a-oA`aA:P:!CA|"O"O>>!!A echo $TERM
   .||LYENXS:AYENO/<<e^3](c)w-a-o^2 *-oY 3/4-:(R)ae|!!A echo \$TERM
   <<h.|-a 1/2+-u|LYENX $TERM ^3o'XO|r!C

     --------------------------------------------------------------

  3.9.1. AAU:S:oS:A-a-o Shell

   AAU:S:o shell ^3IA^2^3ae-a-oCURe-ak'NNOTO^3z^1L chsh (c)RYENO!C
   DEGo|ae chsh +-N.|(c)IYENsAo^1OAAU: 1/4AECURCUR EDITOR
   <<u:(c)w-a-oCURaa|r 1/2s?e 3/4^1!C
   |p-aG"S|^3^3](c)w!A<<h^1w^3]NOTO vi!C  1/2D-"I.O>>Y"DYENh *S:i
   !S:Shell:!" -a-oE!C

   S:ACUR]YENiYENH^3z^1L chsh -a-oDEGN 1/4AE -s!A ^3oYENiYENH-a
   1/2+-u^3](c)wS:A-a-o shell |OCUR-L->>Yn^3z^1LYENo|oCURaa|r 1/2s?e
   3/4^1!C "O|p!A DEG^2^3].QS:a(c)OYENI-a-o shell S:iNOTDEG bash!A
   YENiYENH^3z^1LCURU|C-a-oCURe|!!G

 % chsh -s /usr/local/bin/bash

     -a`: S:A(c)O"IYENI-a-o shell YEN^2P:. |C(c)o /etc/shells ,IAY!C
     |p-aGNOTOYENN Ports Collection "O,E shell!A
     "-o^3oO"BAEJCURw,gS:^1|"CURF!C |yYNOTOCURaDEGE|w,ECURFCUR@O
     shell!A "-o>>o'NYEN^2P:.NOTDEG.s|w,E-a-o shell P:i|ae^3](c)w!C

     A|"O"O>>!!AYCURaDEGE|w,ECURF bash "A+-NYEN|,m(c)o /usr/local/bin
     (c)^3CURU!AS:AAU+-o!G

 # echo "/usr/local/bin/bash" >> /etc/shells

     uM<<a|A<<.sDEGo|ae chsh!C

     --------------------------------------------------------------

3.10. CURaa|r 1/2s?e 3/4^1

   |b FreeBSD CURCUR|^3^3\|h^3](c)wYEN^2P:.^3z^1L
   1/2s?eCURaa|rAES:^1|"!C |]|^1!AY-`a 1/4o+-xCURaa|r 1/2s?e
   3/4^1NOTO|A|nCUR-L-^1L-a-o!C FreeBSD YEN>>"!]<<u: base
   system!^'N-ath|^3'X-oO/CURaa|r 1/2s?e 3/4^1!A
   |^1YEN~!AS:ACUR]YENiYENH^3z^1L Ports Collection
   "O|w,E"a:YENL-a-oCURaa|r 1/2s?e 3/4^1!C

   ^3IA^2^3ae(c)o: 3/4C,-a-oCURaa|r 1/2s?e 3/4^1YENsDEGu ee!A
   YENN-aiCURF"a:YENth|W easy editor!C nP:}(c)l"IYENI ee!A
   YEN^2P:.|b(c)RYENO|CCURW?eCURJ ee filename!A ^3oAa:-a-o filename
   YENN-aiS:A.Qn 1/2s?e-a-oAE(R) *|W-oU!C A|"O"O>>!!An 1/2s?e
   /etc/rc.conf!A'Nn?eCURJ ee /etc/rc.conf!C |O|b ee -a-o
   3/4THS:@CURP:+-CURU!A (c)O|^3 1/2s?e 3/4^1-a-oYEN\-`a>>P
   3/4THS:@^3-L-.|AAaYENU:|b?A^1o-a-oYEN?CURWCURe!C
   "a:CURCUR-a-o'!CURJ^2AA,^1(^)YENN-aiAa: 1/2LCURW-a-o Ctrl
   Aa:!A(c)OYENH ^e 'NuYEN|P(c)o Ctrl+e !C Ynu^2S:o ee!A
   1/2D-<<o:CURU Esc Aa:!A+-uuU?i 3/4U: leave editor S:YYENi!C
   |^1(R)E|p-aG,OAE(R) *|^3 *S:i^1L!A 1/2s?e
   3/4^1.|'-L-?oS:ANOTOS:_n|sAE!C

   |^1YEN~!AFreeBSD CUR]CUR-o-athCURF'XO|nYENI-a-oCURaa|r 1/2s?e
   3/4^1!A^1^3NOTO base system -a-o vi CURI FreeBSD Ports Collection
   CUR-o-a-o"a:YENL 1/2s?e 3/4^1!A CURn|p Emacs CURI vim
   (editors/emacs CURI editors/vim)!C ^3o"C,CURaa|r 1/2s?e
   3/4^1'-L-"NS:o+-j-a-oYEN\-`a!A|yNOTOCUR]CURn,uAo/ 3/4C,^2ss!C
   uM|OYn+-q"AECURjP:qCURaa|r 1/2s?eCURuS:@!A "-o>>o-aaAI(R)EP:!"O
   3/4C,^2ss^3o"C,|nYENI-a-o 1/2s?e 3/4^1!A
   .||bCURe<<aNOTDEG+-zNOTUCURUS:o|h-a-o(R)EP:!!C

     --------------------------------------------------------------

3.11. ^3]^3AECURI^3]^3AE,`AI

   ^3]^3AE(device)YENDnNOTO<<u:,ouwAAeCURn,u|^3Ao:-a-o^3N>>y!A
   YEN]NOTA-oI-oD-!B|L-ai 3/4-:!BAAaYENU:YENd(c)MAa: 1/2L!C FreeBSD
   P:} 3/4-:^1Lu{.iCURCUR!A CURj|h
   1/4AEuwAAe^3q+-`^3-L--`aDEG>>'u"`i"AAAaYENU:YENX"O!ACUR]YENiYENHNOTd
   3/4\ /var/run/dmesg.boot CUR-o|^3P:} 3/4-:-a-oNOTUAo:DEGT(R)S:!C

   A|"O"O>>!!Aacd0S:YNOTDEG^2A:CUR@YENx IDE YENu-oD-
   3/4-:-a-oYENN,^1!A |O kbd0 <<hYENN-aiAa: 1/2L!C

   |b UNIX S:@.~"t^2I!A CURj^3!CURA-a-o^3]^3AE^3-L-NOTO^3z^1LYENsDEGu
   device nodes(^3]^3AE,`AI)-a-o-S(R)iAE(R) *"OS:@|s"u!A
   |O^3o"C,AE(R) *^3-L-|`i(c)o /dev YENO/?y!C

     --------------------------------------------------------------

  3.11.1. <<O/YENss^3]^3AE,`AI

   Yn|b"t^2ICURW<<O/YENss.s,`AI!A(c)I-aINOTOn
   1/2sA:P:NOTY"C,.suwAAe-a-oCURa:'(c)^3nAAe!A "-o>>o'NnYENy.s
   1/4W^3]^3AE,`AI!C

     --------------------------------------------------------------

    3.11.1.1. DEVFS (DEVice File System)

   ^3]^3AEAE(R) *"t^2I((c)I-oUNOTDEG DEVFS) NOTO<<u:|b 3/4aAAeAE(R)
   *"t^2I namespace '-L-"N kernel -a-o^3]^3AE namespace!C DEVFS
   CURDNOTO-ouAA@^3o"C,AE(R) *"t^2I!A|OCUR-L--`a.s 1/4W(c)I
   *S:i^3o"C,^3]^3AE,`AI!C

   ^2O,` 1/2D-DEGN 3/4\ devfs(5) >>!(c)u!C

     --------------------------------------------------------------

3.12. Binary -a-o(R)ae|!

   Yn-a 3/4^1DNOTDEG|o FreeBSD NOTO+-A:YENI elf(5)
   (R)ae|!!AYEN^2YENyAA,N.i<<e UNIX "t^2ICURCURCURT-oO/!S:
   1/4vAAT^3INOTDEG<<CURj!"-a-oYENiDEGo|aeAENOTUAo:I'-o!G

     * a.out(5)

       ^3IYENj|N!B!S:,g"aa!" -a-o UNIX object AE(R)ae|!!C It uses a
       short and compact header with a magic number at the beginning
       that is often used to characterize the format (see a.out(5)
       for more details). It contains three loaded segments: .text,
       .data, and .bss plus a symbol table and a string table.

     * COFF

       The SVR3 object format. The header now comprises a section
       table, so you can have more than just .text, .data, and .bss
       sections.

     * elf(5)

       The successor to COFF, featuring multiple sections and 32-bit
       or 64-bit possible values. One major drawback: ELF was also
       designed with the assumption that there would be only one ABI
       per system architecture. That assumption is actually quite
       incorrect, and not even in the commercial SYSV world (which
       has at least three ABIs: SVR4, Solaris, SCO) does it hold
       true.

       FreeBSD tries to work around this problem somewhat by
       providing a utility for branding a known ELF executable with
       information about the ABI it is compliant with. See the manual
       page for brandelf(1) for more information.

   FreeBSD comes from the !S:classic!" camp and used the a.out(5)
   format, a technology tried and proven through many generations of
   BSD releases, until the beginning of the 3.X branch. Though it was
   possible to build and run native ELF binaries (and kernels) on a
   FreeBSD system for some time before that, FreeBSD initially
   resisted the !S:push!" to switch to ELF as the default format.
   Why? Well, when the Linux camp made their painful transition to
   ELF, it was not so much to flee the a.out executable format as it
   was their inflexible jump-table based shared library mechanism,
   which made the construction of shared libraries very difficult for
   vendors and developers alike. Since the ELF tools available
   offered a solution to the shared library problem and were
   generally seen as !S:the way forward!" anyway, the migration cost
   was accepted as necessary and the transition made. FreeBSD's
   shared library mechanism is based more closely on Sun's SunOS(TM)
   style shared library mechanism and, as such, is very easy to use.

   So, why are there so many different formats?

   Back in the dim, dark past, there was simple hardware. This simple
   hardware supported a simple, small system. a.out was completely
   adequate for the job of representing binaries on this simple
   system (a PDP-11). As people ported UNIX from this simple system,
   they retained the a.out format because it was sufficient for the
   early ports of UNIX to architectures like the Motorola 68k, VAXen,
   etc.

   Then some bright hardware engineer decided that if he could force
   software to do some sleazy tricks, then he would be able to shave
   a few gates off the design and allow his CPU core to run faster.
   While it was made to work with this new kind of hardware (known
   these days as RISC), a.out was ill-suited for this hardware, so
   many formats were developed to get to a better performance from
   this hardware than the limited, simple a.out format could offer.
   Things like COFF, ECOFF, and a few obscure others were invented
   and their limitations explored before things seemed to settle on
   ELF.

   In addition, program sizes were getting huge and disks (and
   physical memory) were still relatively small so the concept of a
   shared library was born. The VM system also became more
   sophisticated. While each one of these advancements was done using
   the a.out format, its usefulness was stretched more and more with
   each new feature. In addition, people wanted to dynamically load
   things at run time, or to junk parts of their program after the
   init code had run to save in core memory and swap space. Languages
   became more sophisticated and people wanted code called before
   main automatically. Lots of hacks were done to the a.out format to
   allow all of these things to happen, and they basically worked for
   a time. In time, a.out was not up to handling all these problems
   without an ever increasing overhead in code and complexity. While
   ELF solved many of these problems, it would be painful to switch
   from the system that basically worked. So ELF had to wait until it
   was more painful to remain with a.out than it was to migrate to
   ELF.

   However, as time passed, the build tools that FreeBSD derived
   their build tools from (the assembler and loader especially)
   evolved in two parallel trees. The FreeBSD tree added shared
   libraries and fixed some bugs. The GNU folks that originally wrote
   these programs rewrote them and added simpler support for building
   cross compilers, plugging in different formats at will, and so on.
   Since many people wanted to build cross compilers targeting
   FreeBSD, they were out of luck since the older sources that
   FreeBSD had for as and ld were not up to the task. The new GNU
   tools chain (binutils) does support cross compiling, ELF, shared
   libraries, C++ extensions, etc. In addition, many vendors are
   releasing ELF binaries, and it is a good thing for FreeBSD to run
   them.

   ELF is more expressive than a.out and allows more extensibility in
   the base system. The ELF tools are better maintained, and offer
   cross compilation support, which is important to many people. ELF
   may be a little slower than a.out, but trying to measure it can be
   difficult. There are also numerous details that are different
   between the two in how they map pages, handle init code, etc. None
   of these are very important, but they are differences. In time
   support for a.out will be moved out of the GENERIC kernel, and
   eventually removed from the kernel once the need to run legacy
   a.out programs is past.

     --------------------------------------------------------------

3.13. S:o|h,eDEGT

  3.13.1. Manual  1/2uCURW>>!(c)u

   |b"IYENI FreeBSD (R)E!A^3I,O^2O-a-o"IYENI>>!(c)u^2o:^1L(c)o man 
   1/2uCURW>>!(c)u!C
   'XYENG|Uu{|!^3-L-.||^3-athCURWA^2uu>>!(c)u!AYENHCURP:^2D-,Ou{|!-a-oDEGoYEN>>YEN\-`a,oNOTUAo:DEGN
   1/4AEYENI-ak!C YENiYENH^3z^1L man <<u:YENO"O
   3/4\AA-a^3o"C,>>!(c)u!A|O man
   <<u:YENO-a-o"IYENINOTU.iA^2^3ae(c)o:A'!G

 % man command

   command ^3B'NNOTO.Qn-a 3/4^1D-a-o<<u:YENO!C A|O"OCURl!A Yn-a
   3/4^1D ls -a-o,O^2OYENI-ak!A'NYENiYENHYEN'!G

 % man ls

   |O|U 1/2uCURW>>!(c)u|]NOTDEG(c)E
   1/2eCUR-L-|P!A|ODEGICURANOTDEGCURU|C-a-o 1/4AE|r^3^1,`!G

    1. "IYENI-aI<<u:YENO!C

    2. "t^2I(c)IYENs(System call) CURI?u>>~YENN,^1!C

    3. C >>y"YEN"c,|!(R)w!C

    4. |U^3]^3AE-a-oAAXDEGEu{|!!C

    5. AE(R) *(R)ae|!!C

    6. CURp^1CA,u{|!CURI"a:YENL(R)T 1/4O:u{|!!C

    7. Ao/P:uCURu"a!B"a:YENL,eDEGT!C

    8. "t^2I-ouAA@!B 3/4THS:@-a-o<<u:YENO!C

    9. Kernel P:}uoYENI^3~!C

   |^3"C,+-!-ap.||^3|P 1/4EYENDAD|yCUR-L-|P^3^1,`!C
   A|O"OCURl!A"t^2ICUR-o.||^3 chmod <<u:YENO!A|yCUR]|^3 chmod()
   "t^2I(c)IYENs!C |b^3o-oO/+-!-ap!Aman
   A^3,On<<u:(c)w(c)OnNOTd,ss-a-o^3^1,`!G

 % man 1 chmod

   |p|^1CUR@"O'N.|NOTd chmod <<u:YENO^3!CURA!C ^3q+-`|b
   1/4gCURaaYENo(R)E.|S:a|^3DEGN|O"`iNOTY-S(c)w^3^1,`-a-o man ,^1
   1/2XCUR]CUR@"O: 1/4g|bNOTA,^1CUR-o!C (c)OYENH chmod(1) 'NNOTO<<u:
   chmod <<u:YENO!A|O chmod(2) <<hNOTO<<u:"t^2I(c)IYENs-a-o^3!CURA!C

   |p-aG+-zCURw,g-a 3/4^1D(c)RYENO-a-o|W-oU!AYENuNOTOCUR-L--a
   3/4^1Dn<<c, 1/4E"IYENI-a-o,U:!A"-o'NCURn,u|n?`i!C |yYCUR-L--a
   3/4^1DnYENIthO<<u:YENO(R)E!A,O<<c,>>o?`i(c)O!H
   ^3oO(R)EO!A'NYENiYENHS:QYENI man -a-o.j'MAo:Aa:|rYEN\-`a!A
   YENH|b|U>>!(c)u-a-oCURP:^2D-^3!CURA.j'MNOTUAo:|r^2'!C!AYEN|-a-o?iP:uNOTO
   -k!G

 % man -k mail

   |p|^1CUR@"O.|NOTY"`iCUR@DEGi|^3 !S:mail!" Ao:Aa:|r-a-o>>!(c)u!A
   "AE^1eCURW,OYEN\-`a>>P apropos <<u:YENONOTOCUR@ 1/4E-a-o!C

   |O|^3(R)ES:A.|NOTY"`i^1^3NOTO /usr/bin
   |^3^3\|hNOTYDEG_"O>>aNOT--a-o<<u:YENO!A|yCUR-L--a 3/4"a:YENI^3~!H
   YENunA^2^3ae?eCURJ!G

 % cd /usr/bin
 % man -f *

   (c)I-aINOTO

 % cd /usr/bin
 % whatis *

   ^3o"a-aI-a-o<<u:YENO(R)A:-aGNOTOCUR@ 1/4E-a-o!C

     --------------------------------------------------------------

  3.13.2. GNU Info AE(R) *

   FreeBSD |^3^3\|hu{|!,oCURu"a"O|U(c)o|UYENN^3nAAeDEGo-a-:.|(FSF)!C
   DEG-L-CURF man 
   1/2uCURW>>!(c)uCURS:YEN~!A^3o"C,u{|!'-L-"NCURFYENtYEN~CUR@-oO/S:o"a|^3
   1/4u(c)E-a-o hypertext (R)ae|!CURaaYENo!A YENsDEGu info!C
   YENiYENHYENI info <<u:YENO"O 3/4\AA-a!A(c)I-aIY|^3,E emacs
   YENc,YENi^3z^1L emacs -a-o info  1/4O|! 3/4\AA-a!C

   nYENI info(1) <<u:YENO!AYENu>>YYEN'!G

 % info

   <<o: h .||^3A^2^3ae>>!(c)u!A|OYnS:O:^3tNOTd 3/4\NOTUAo:
   3/4THS:@CURe|!!A <<h 1/2D-<<o: ?!C

     --------------------------------------------------------------

    ^3^1 4. ^3nAAe(R)MYENo-oTH^2z 1/2g!GPackages CURI Ports  3/4-:"i

4.1. .S:z

   3/4"-oTH FreeBSD |b base system CURwYEN[CURF<<U:|h"t^2ICURu"a!C
   uM|O!A|b^1eDEGE^1BYENICURW!A+-zYENi-`aCUR'>>Yn|w,EABYEN~-a-o^3nAAe!C
   FreeBSD '-L-"NCURF 2
   -oO/|w,EA^3YENIu{|!-a-o(R)MYENo-oTH^2z"t^2I!JPorts Collection
   (YENH soucre "O 1/2sA:P:!B|w,E) (c)M package(^1wYENy
   1/2sA:P:|n-a-o binary AE)!C CURWz-a-oCURe|!!AuL 1/2
   *nYENIthCUR@-oO/!A^3-L-YENiYENHYENN^1^3NOTO CDROM
   uYEN(c)I-oo,oCURW"O|w,E.Q,E-a-o^3I.s-a(c)^3nAAe!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!G

     * |p|oYENH packages "O|w,E^3nAAe!C

     * |p|oYENH ports "O|w,E^3nAAe!C

     * CURw|w,E-a-o packages (c)I ports n|p|o^2 3/4DEG-L-!C

     * |p|oS:oS:i(override) ports collection (c)O"IYENI-a-o^1w^3]E!C

     * |p|o|b(R)MYENo-oTH^2z"t^2ICURCUR!AS:a:YENX.Q,E-a-o^3nAAe!C

     * |p|oCURE-AACURw|w,E-a-o^3nAAe!C

     --------------------------------------------------------------

4.2. |w,E^3nAAe-a-o|U-oO/CURe|!CURP:^2D-

   ^3q+-`n|b UNIX "t^2ICURW|w,E^3nAAe(R)E!A|^3'XO"BAEJnS:@!G

    1. YENyCURU,u:,O^3nAAeA-L-AYAE(tarball)!A|^3YENi-`aNOTO`i(c)l
       1/2X(c)INOTO binary DEGo|aeAE!C

    2. ,NP:},OA-L-AYAE!C(^3q+-`NOTOYENH compress(1) , gzip(1) (c)I
       bzip2(1) A-L-AY-a-o)

    3. 3/4\AA-aNOTUAo:CURaaYENoAE!AYENHCURF,N|p|o|w,E!C(^3q+-`AE|WNOTO
       INSTALL (c)I README !A(c)I|b doc/
       YENO/?yCURU-a-oCUR@"C,CURaaYENo)

    4. |p-aG(c)OCURU,u:-a-oNOTO`i(c)l 1/2X!AYENi-`anYENy *S:i
       Makefile (c)INOTODEGo|ae ./configure CURS:Ath-a-o script
       !A+-uuU|A 1/2sA:P:,O^3nAAe!C

    5. ^3I<<a'u,O|A'u,O>>P|w,E!C

   |p-aGCUR@CURAP:P:S:Q-a-o,U:!A'N^3o>>oA^2^3ae!C
   |p-aG|b|w,E<<D+-M-au^3]p(^2 3/4'O)u^1 FreeBSD
   -a-o^3nAAe(R)EYENXDEGYAD!A "-oYENi-`a>>Yn *S:iCUR@CURUYEN|-a-ou{|!
   1/2X!ACUR~-`aYEN?+-`"IYENI!C

   .iuM!AS:UIYENiYENH|b FreeBSD
   CURW"IYENICURWz-a-oP:C,^2ICURe|!"O|w,E^3nAAe!A
   |yNOTO!AS:UIAU|^3S:oA^2^3ae-a-o?i 3/4U:!C FreeBSD
   '-L-"NCURF"a-oO/NOTU"AE-a-o^3nAAe-oTH^2z 3/4-:"i!G packages (c)M
   ports!C 'N|b 1/4g^3o 1/2gCURaa^3^1-a-o(R)EO!A CURw,g|^3P:W^1L
   24,000 O port ^3nAAeYENiYENH"IYENI!C

   (c)O? *-a-o FreeBSD package 'NNOTOS:OCURHS:a,OA^3YENIu{|!
   1/2sA:P:!BYEN'YEN]S:^1^2|!C ,O package
   .|YEN]NOTA,OA^3YENIu{|!-a-o(c)O|^3DEGo|aeAE!B^3](c)wAE!BCURaaYENouYEN!C
   |OCURU,u:"`iuw-oD-CURW-a-o package ^3-L-YENi^3z^1L FreeBSD
   (R)MYENo-oTH^2z<<u:YENO"OP:i|ae-oTH^2z!ACURn|p!G
   pkg_add(1)!Bpkg_delete(1)!Bpkg_info(1) uYEN<<u:YENO!C
   (c)OYENH!AYENu>>YA^2^3aeYEN'O<<u:YENO'NYENi>>'AP|w,E.s-a-oA^3YENIu{|!CURF!C

   |O FreeBSD port <<hNOTOYENICUR@"C,AE(R)
   *!A"O|UDEGE^3B^2zA^3YENIu{|!-a-o|w,ENOTyu{!C

   1/2D-DEGO|i!G|p-aGYEN'-oa|UCURv"O
   1/2sA:P:-a-o,U:!A>>YnDEGo|ae<<U:|h 3/4THS:@"BAEJ
   (CURU,u:!B,NA-L-!Bpatch!B 1/2sA:P:!B|w,E)!C |O port
   (c)O!A<<hNOTO^2[>>\(c)O|^3>>YnS:^1|"^3o"C,CURuS:@-a-oYEN^2^3AE"BAEJ!A
   (c)OYENHYENu>>YYEN'CUR@"C,A^2^3ae-a-o<<u:YENO!A"-o"C,`i(c)lu{|!
   1/2X'N.||UDEGECURU,u:!B,NA-L-!B patch!B 1/2sA:P:!A-a
   1/2|U:|w,ES:^1^2|!C

   "AE^1eCURW!Aports  3/4-:"iAUYENiYENHYENI"O^2-L-YENI
   packages!AYENH<<KYENLCURHYENiYENHYENI pkg_add "O|w,E!A
   (c)INOTOuy<<a.|CURP:^2D-"`i-a-o"a:YENL(R)MYENo-oTH^2z<<u:YENO!C

   |O packages YENHCURI ports YEN|I^3-L-NOTOCUR@ 1/4E.|>>{
   dependencies(^3nAAeNOTU"IAo:<<Y)!C
   DEG^2^3]!G+-z.Q|w,ENOTYu{|!!A|yYEN||^3NOTU"IYENtCUR@OCURw,E-a-o"c,|!(R)w(library)!A
   |O|b FreeBSD -a-o port YENHCURI package
   ^3-L-|^3^3ou{|!YENHCURI,O"c,|!(R)wCURF!C (c)OYENHuL 1/2 *NOTOYENI
   pkg_add <<u:YENO(c)I-aI port CURe|!"O,E,Ou{|!!A
   ^3o"a-aI(package!Bport)^3-L-.|YENyAENOTd|^3"S|^3,E,O"c,|!(R)w!A
   Y"S|^3'N.||UDEGEYENy,E,O"c,|!(R)wCURF!C

   ^3o"a-oO/S:TH^3N^3-L-<<U:NOTU|u:!A+-zYENi-`a.||n(c)_NOTDEGCURDEG>>o
   FreeBSD .|S:EYENX^3o"a-oO/S:TH^3N"O(c)O!C "a:^1e!Apackages (c)M
   ports ^3-L-|^3YEN|I|U|U-a-o-ao/^3B!A
   "IYENIthCUR@-oO/S:^1YENth"u"M(c)o+-z|UCURv-a-o^3ss|n!C

   Package |n^3B|b(c)o!G

     * |P 1/4ENOTOA-L-AY^1L-a-o package >>P`i(c)l 1/2X tarball
       NOTUCURn!A <<e-aI^3q+-`.|CURn<<a-aICURp|hCURF!C

     * package "ACUR-L->>Y|AP:i|ae 1/2sA:P:!C
       ^1iCURj<<NOTA^3YENIu{|!|p Mozilla!B KDE!B GNOME
       |O"YEN!A^3oAIAAa+-oNOTU.i<<n!A CUR *"a:NOTO"IYENI^3t<< *
       1/2w-oC-a-o 3/4-: 3/4^1!C

     * CUR-L->>YnAA,N|p|o|b FreeBSD CURW
       1/2sA:P:^3nAAe-a-oNOTUAo:^2O,`^1Lu{!A S:YYENi"IYENI package!C

   Ports |n^3B|b(c)o!G

     * NOTDEGCURFAAy package -`a|bCURj|h
       1/4AE"t^2ICURWP:P:S:QDEGo|ae!A ^3q+-`|b
       1/2sA:P:(R)E.|"IYENICURn,u<<O|u-a-o?iP:u!C uM|O!A ^3z^1L port
       |w,E-a-o,U:!A<<hYENiDEGw^1i-S(c)wAo^1O(CURn|p!G Pentium 4 (c)I
       Athlon CPU) "O 1/2O 3/4a?iP:u!AYENH^2AA|X>>Y"D!C

     * |^3"C,u{|!|b 1/2sA:P:(R)E!A.||^3CUR@"C,?iP:uYENiYENH?i 3/4U:!C
       A|"O"O>>!!AApache YENiYENH^3](c)wCUR@CURjDEGi-a-o
       1/2sA:P:?iP:u!C Y^3z^1L port "O|w,E-a-o,U:!A .|CURn,u
       1/4u(c)E|hCURF!AYENiYENH|UCURv?i|OCUR-L-YEN^2"IYENI^1w^3]-a-o
       1/2sA:P:?iP:u!C

       |bNOTY"C,+-!-ap!A|P 1/4E-a-ou{|!|yCUR-L-|P
       1/2sA:P:?iP:u!A<<h.|CURA|"CUR-L-|P-a-o package!C CURn|p!G
       Ghostscript .||]NOTDEGNOTOS:_n,E X11 server!A |O^1-oCURANOTDEG
       ghostscript YENHCURI ghostscript-nox11 ^3o"a-oO/ package!C
       |p|^1-a-o 1/2O 3/4a^1i package -oaNOTOYENi|"YENss-a-o!A
       |yY,Ou{|!|^3CUR@OYENHCURW(c)I"a-oO/CUR-L-|P-a-o
       1/2sA:P:?iP:u(R)E!A ^3o^1i package 'N"S?`i-akCURF!C

     * NOTY"C,^3nAAe-a-o,TCURiYENH binary CURe|!'^2S:G!A
       (c)I-aI>>!YEN^2P:.YENH`i(c)l 1/2XCURe|!'^2S:GCUR~YENi!C

     * |^3"C,CURH"ACUR-L-<<HYENo binary (R)MYENo
       3/4-:"i!A|]NOTDEGYENLIA:+-+-o|U:CURO:|^3`i(c)l 1/2X!A (^2z 1/2
       *CURW)'NYENiYENH|UCURvAE 3/4\!A"A'MS:a:NOTOS:_|^3
       1/4c,|b-a-oDEGYAD!C

     * Yn^1i^3nAAeYEN[CURW|UCURvS:i^1L-a-o patch!A
       "-o>>o'NYEN^2P:.nYENy|^3`i(c)l 1/2XCUR~-`aYENhCURWNOTUAo:
       patch  *YEN?!C

     * |^3"C,CURH^3ssAAw|^3`i(c)l 1/2X|bCURaAa:!A
       (c)OYENHYENLIuL^2a(R)E'NYENiYENH|UCURv
       3/4\AA-a!BAEpNOTa!BEYENI (.iuMn^2AA|X`i(c)l
       1/2XYEN>>"-a-o+-AAAv^3W(c)w)`i(c)l 1/2XuYENuYEN!C

   Y.Q-a`.N port S:o.sDEGE-oA-a-o,U:!AYENiYENHq 3/4\ FreeBSD ports
   P:l>> 1/4 1/2 * 3/4A YENHCURI FreeBSD ports bugs P:l>> 1/4 1/2 *
   3/4A!C

     A:uS:i|b|w,E^3nAAe<<e!A^3I|nYENyNOTY http://vuxml.freebsd.org/
     CUR-oNOTOS:_|^3,O^3nAAe-a-o|wYENth-o|NOT}^3q^3o/!C

     |^1YEN~!ACUR]YENiYENH,E
     ports-mgmt/portaudit!AYEN|.||UDEGEAENOTd(c)O|^3CURw,E-a-o
     -a-o^3nAAeNOTOS:_|^3CURw-a
     3/4-a-o|wYENth-o|NOT}!AYENtYEN~!AYEN|AU.||b,E^3nAAe-a-o
     1/2sA:P:^1Lu{<<eYENy|aeAENOTd!C
     CUR]YENiYENH|b,ECURFNOTY"C,^3nAAeCURS:<<a!AYENI portaudit -F -a
     "OS:@YENth+-+-j"i|wAE!C

   YEN>>^3^1+-uCURU"O+-NCURP:^2D-|p|o|b FreeBSD "IYENI package CURI
   port "O|w,E!B-oTH^2z third-party ^3nAAe!C

     --------------------------------------------------------------

4.3. 'MS:a:.Q,E-a-o^3nAAe

   |b|w,EYENo|o^3nAAeCURS:<<e!AS:AYEN^2P:.YENyCURF,NS:A.QnCURDEG>>o-a-o^3nAAe!A
   YENHCURI,O^3nAAeYENsDEGuCURDEG>>o|W-oU!C

   FreeBSD CURWYENi,E-a-o^3nAAe^2M^3aeCUR-L-A_|b 1/4WYEN[CURCUR!A
   CUR-L-^1L!AS:UI<<U:
   1/4y(c)-|^3'X-oO/CURe|!YENiYENH"OS:a:S:A.Q,E-a-o^3nAAe!G

     * FreeBSD -oo-,CURW|^3S:o.sAWAc-a-o^3nAAe^2M^3ae!A|b
       http://www.FreeBSD.org/ports/ !C |U ports NOTO"I"a:(c)E
       1/2e|OCURA-auS:OAth!ANOTJYENiYENH^3z^1L^3nAAe|W-oU"O.j'M
       (|p-aG-a 3/4^1D|W|r-a-o,U:)!A
       CUR]YENiYENH|bCURAAthCURCUR|CYENX(c)O|^3YENiYENI-a-o^3nAAe!C

     * YENN Dan Langille (c)O-ouAA@ FreshPorts -oo-,!A-ooS:}|b
       http://www.FreshPorts.org/!C FreshPorts .|CUR-L-A_DEGlAU: port
       tree CURCUR-a-o|U-oO/AAU:CURAE!A CUR]YENiYENHDEGw^1iNOTY"C,
       port YENH|CCURJ !S:DEGlAU:|W^3ae(watch)!" CUR-o!A
       .i|^3YENo|o^3nAAeCURE-AA(R)E!A'N.|uo email '-L-?o!C

     * |p-aGCUR-L--a
       3/4^1D.Q,E-a-o^3nAAe|W-oU!A"-o>>oYENi^3z^1L^1^3NOTO FreshMeat
       (http://www.freshmeat.net/) ^3oAth-a-o-oo-,"OS:a:!A
       |p-aGS:a:"`iCURF!AYENiYENH|^ FreeBSD
       -oo-,YENhNOTYCUR@CURU^3oOA^3YENIu{|!NOTOS:_CURw,g^3Q port
       P:iYENhCURF!C

     * Y-a 3/4^1D,O port -a-oYEN? 1/2T|W-oU!A|yCUR-L--a
       3/4^1D(c)n|bthOCURAAthYENO/?y!AYENiYENHYENI whereis(1)
       <<u:YENO"OS:a:YENX"O!C YENunYEN' whereis file S:YYENi!A|O file
       -a-o|aCURe 1/2D-S:iNOTDEG.Q,E-a-o^3nAAe|W-oU!C
       YS:a:"`i,O^3nAAe!A'N.|S:iP:DS:A!A'N^1^3CURU+-^3o 1/4E!G

 # whereis lsof
 lsof: /usr/ports/sysutils/lsof

       |p|^1CUR@"O!A'N.|-a 3/4^1D lsof ("t^2ICURu"au{|!) NOTO(c)n|b
       /usr/ports/sysutils/lsof YENO/?y!C

     * |^1YEN~!ACUR]YENiYENHYENI echo(1) >>'APS:a:YENX,O port
       NOTO|`i(c)o porte tree -a-o|o^3B!C A|"O"O>>!!G

 # echo /usr/ports/*/*lsof*
 /usr/ports/sysutils/lsof

       1/2D--a`.N!A^3oCUR].|AAaYENU: /usr/ports/distfiles
       YENO/?yCUR-o|^3^2AA|XAE|W-a-oAE(R) *!C

     * AU|^3YENtCUR@(c)U!A'NNOTOYENI Ports Collection
       YEN>>"CUR-o<<O/-a-o.j'M 3/4-:"i!C nYENI-a-o(R)EO!A
       1/2D-YENyCURA'<<"`i /usr/ports YENO/?y!C uM<<a!AYEN' make
       search name=u{|!|W-oU !A"a:CURCUR u{|!|W-oU 
       1/2D-S:iNOTDEG.QS:a:-a-o^3nAAe|W-oU!C
       A|"O"O>>!!AYnS:a:-a-oNOTO lsof -a-o,U:!A"-o>>o'NNOTO!G

 # cd /usr/ports
 # make search name=lsof
 Port:   lsof-4.56.4
 Path:   /usr/ports/sysutils/lsof
 Info:   Lists information about open files (similar to fstat(1))
 Maint:  obrien@FreeBSD.org
 Index:  sysutils
 B-deps:
 R-deps:

       ^3o"C,.j'Mu^2-aGCURCUR!An-a`.N-a-oNOTO !S:Path:!" ^3o|ae!A
       |]NOTDEG^3o|ae.|S:iP:DS:AYENiYENH|bthAa:S:a:"`i,O port!C
       |O.j'Mu^2-aG-a-o"a:YENL^3!CURA!A|]NOTDEG>>P port
       |w,E,uuLAo:<<Y!A(c)OYENH^3o,I'NCUR-L-A?CURF!C

       YnS:o^1y(c)^3-a-o.j'M!A"-o>>oYENiYENHS:iYENI make search
       key=string!A"a:CURCUR string 
       1/2D-S:iNOTDEG.Q.j'M-a-oAo:Aa:|r!C |p|^1CUR@"O.|S:a: port
       |W-oU!B^3nAAeA^2CURP:(comments)!B^3nAAe+-OzAE(descriptions)
       YENHCURI^3nAAeNOTU"IAo:<<Y(dependencies),I+-NOTOS:_|^3^2AA|XAo:Aa:|r!A
       |^1YEN~!ACUR-L-^2M.!^3nAAe|W-oU-a-o,U:!ACUR]YENiYENH(R)^3"OS:a:|^3^2AA|XAo:Aa:|rYENDAD-a-o
       port!C

       eA?-a-o^3o"a-oO/CURe|!!A.j'M|r^2'^3-L-NOTO
       case-insensitive(CUR-L-YEN^2DEGICURACURjCURp 1/4g)!C
       CURn|p!A.j'M !S:LSOF!" >>P !S:lsof!"
       "a-aIu^2-aG^3-L-.|NOTOCUR@ 1/4E-a-o!C

     --------------------------------------------------------------

4.4. "IYENI Packages -oTH^2z 3/4-:"i

   Contributed by Chern Lee.

  4.4.1. Package -a-o|w,ECURe|!

   YENiYENHYENI pkg_add(1) +-qYEN>>
   3/4-:CURW(c)I-aI^3z^1L-oo,o"O|w,EYENoCUR@ FreeBSD package!C

   1/2d"O 4-1. CURaDEGECURU,u:!B|w,E Package

 # ftp -a ftp2.FreeBSD.org
 Connected to ftp2.FreeBSD.org.
 220 ftp2.FreeBSD.org FTP server (Version 6.00LS) ready.
 331 Guest login ok, send your email address as password.
 230-
 230-     This machine is in Vienna, VA, USA, hosted by Verio.
 230-         Questions? E-mail freebsd@vienna.verio.net.
 230-
 230-
 230 Guest login ok, access restrictions apply.
 Remote system type is UNIX.
 Using binary mode to transfer files.
 ftp> cd /pub/FreeBSD/ports/packages/sysutils/
 250 CWD command successful.
 ftp> get lsof-4.56.4.tgz
 local: lsof-4.56.4.tgz remote: lsof-4.56.4.tgz
 200 PORT command successful.
 150 Opening BINARY mode data connection for 'lsof-4.56.4.tgz' (92375 bytes).
 100% |**************************************************| 92375       00:00 ETA
 226 Transfer complete.
 92375 bytes received in 5.60 seconds (16.11 KB/s)
 ftp> exit
 # pkg_add lsof-4.56.4.tgz

   YCURaAa:"S|^3 package "O. 1/2(^1^3NOTO FreeBSD YENu-oD-)-a-o,U:!A
   "-o>>o<<O/A:^3"IYENI pkg_add(1) (R)E!AYEN[CURW -r
   ?iP:u"OS:o>>'AP|w,E package!C|p|^1CUR@"O!A'N.||UDEGES:PA_YEN?
   1/2T-a-o package (R)ae|!!B YENHCURI(c)O.fDEGt-a-oS:@.~"t^2I
   release -a(c)YEN>>!A uM<<a.||UCURv+-q FTP
   -,S:`i|^!B|w,ENOTU^1iA^3-a-o package!C

 # pkg_add -r lsof

   CURW+-^3o"OCURl.||UDEGECURU,u:YEN? 1/2T-a-o package "A|w,E!C
   Y.QS:i'<<YENI"a:YENL FreeBSD Packages Mirror -,!A"-o>>o'Nn^3](c)w
   PACKAGESITE Ao^1OAAU: 1/4AE!A
   |p|^1CUR@"OCUR~.|"uYENN^1w^3]^3](c)w!C pkg_add(1) .|YENI fetch(3)
   <<u:YENO"OCURU,u:AE(R) *!A|O fetch(3)
   YEN>>"<<h.|"IYENINOTUAo:Ao^1OAAU: 1/4AE-a-o^3](c)w!A ^1^3NOTO!G
   FTP_PASSIVE_MODE!BFTP_PROXY YENHCURI FTP_PASSWORD!C
   |p-aGS:A-oo,oAo^1O^3B(c)o firewall <<a+-!A(c)I-aI>>YnYENI FTP/HTTP
   proxy -a-o,U:!A"-o>>o'N>>Yn^3](c)w!C ^3](c)w^2O,` 1/2D-DEGN 3/4\
   fetch(3)!C  1/2D--a`.N!GCURW+-(c)O>>!-a-o"OCURlNOTO 1/4g lsof
   |O<<D lsof-4.56.4!C .i"IYENI>>.-oYS:`i"uYEN\-`a(R)E!A,O package
   -a(c),^1'NCUR-L-YEN^2YEN[CURWYENhCURF!C pkg_add(1)
   .||UDEGECURU,u:,O^3nAAe-a-o^3I.s-a(c)|^"O|w,E!C

     -a`: YYENI-a-oNOTO FreeBSD-CURRENT (c)I FreeBSD-STABLE
     -a-o,U:!Apkg_add(1) .||UDEGECURU,u:,O^3nAAe^3I.s-a(c)|^"O!C
     YYENI-a-oNOTOA:Y(c)o -RELEASE
     -a(c)YEN>>!A"-o>>oYENL.|S:`i|^A:Y(c)o,O release CURW(c)O
     1/2sA:P:-a-o package!C CUR]YENiYENHS:oS:i PACKAGESITE Ao^1OAAU:
     1/4AE!AYENHS:iAAU:CURU,u:CURe|!!C A|"O"O>>!!A|p-aGNOTO
     FreeBSD 5.4-RELEASE -a-o,U:!A"-o>>o pkg_add(1) ^1w^3].|+-q
     ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.4-release/Latest/
     "OS:`i package!CYn+-j"i pkg_add(1) CURU,u: FreeBSD 5-STABLE
     (c)OYENI-a-o package!A"-o>>o'NS:a PACKAGESITE S:i^3]NOTDEG
     ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5-stable/Latest/
     S:YYENi!C

   Package AE|^3 .tgz YENHCURI .tbz "a-oO/(R)ae|!!C
   ^3o"C,^3-L-YENi^3z^1L
   ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/ !A(c)I-aI
   FreeBSD YENu-oD-CUR-o"u+-o!C "C+-i 4 CURu,E-a-o FreeBSD
   YENu-oD-(YENHCURI PowerPak YEN]uYENuYEN)CUR-o^3-L-.||b /packages
   YENO/?yCUR-o(c)n package!C ,I+--a-oYENO/?yNOT[-ocAth|u: /usr/ports
   -a-oYENO/?yNOT[-oc!C
   "COCURAAth^3-L-|U|U|^3+-MA:YYENO/?y!AYENB"CYEN-: package
   ^3-L-.|(c)n|b All YENO/?yCUR-o!C

   package YENO/?yNOT[-oc>>P port -a-o^3-L-CUR@P!FYEN|I|@|P-oc|"
   3/4aO package/port "t^2I 3/4-:"i!C

     --------------------------------------------------------------

  4.4.2. -oTH^2z Packages

   pkg_info(1)
   YENiYENI"O|CYENX(c)O|^3CURw|w,E-a-o^3nAAe!B^3nAAeA^2CURP:!C

 # pkg_info
 cvsup-16.1          A general network file distribution system optimized for CV
 docbook-1.2         Meta-port for the different versions of the DocBook DTD
 ...

   pkg_version(1) <<hNOTO|CYENX(c)O|^3CURw|w,E-a-o^3nAAe-a(c)YEN>>!C
   YEN|.|AAaYENU:CURw,E-a(c)YEN>>YENHCURIYENO/<<e 3/4-: 3/4^1CURW
   port tree -a-o-a(c)YEN>>(R)t^2S:!C

 # pkg_version
 cvsup                       =
 docbook                     =
 ...

   ^2A:CURGA:ae-a-o^2AA,^1-aiYENU:!GCURw|w,E-a-o^3nAAe-a(c)YEN>>>>PYENO/<<e
   3/4-: 3/4^1CURW port tree -a-o-a(c)YEN>>(R)t^2S:!C

   ^2AA,^1                        YENN-ai.N,q                         
   =       CURw,E-a-o-a(c)YEN>>>>PYENO/<<e 3/4-: 3/4^1CURW port tree  
           -a-o-a(c)YEN>>NOTO|PCUR@-a(c)-a-o!C                        
   <       >>PYENO/<<e 3/4-: 3/4^1CURW port tree                      
           -a(c)YEN>>NOTUCURnDEG_"O!ACURw,E-a-o-a(c)YEN>>,uAA!C       
           >>PYENO/<<e 3/4-: 3/4^1CURW port tree                      
   >       -a(c)YEN>>NOTUCURnDEG_"O!A                                 
           CURw,E-a-o-a(c)YEN>>,u.s!C(YENi-`aNOTOYENO/<<e 3/4-:       
           3/4^1CURW port tree (c)|YEN 1/4S:o.s!C)                    
           CURw,E-a-o^3nAAe|b ports                                   
   ?       -ACURTHCUR-oS:a:uLNOTUAo:,e(R)AE!C                         
           (^3q+-`YENi-`aNOTO!AA|"O"O>>!!GCURw|w,E-a-o,O port CURw+-q 
           Ports Collection CURCUR^2 3/4DEG-L-(c)IS:i|WCURF!C)        
   *       ,O^3nAAe|P(R)E|^3^3\|h-a(c)YEN>>!C                         

     --------------------------------------------------------------

  4.4.3. ^2 3/4DEG-L-CURw|w,E-a-o Package

   Yn^2 3/4DEG-L-CURw,E-a-o^3nAAe!A"-o>>o 1/2D-|hS:QYENI
   pkg_delete(1) CURu"a!ACURn|p!G

 # pkg_delete xchat-1.7.1

   1/2D--a`.N pkg_delete(1) P:.n(c)nCURWS:^1
   3/4a-a-o^3nAAe|W-oUYENHCURI-a(c)YEN>>!A YYENu?eCURJ xchat
   'NCUR-L-|ae!AYEN^2P:.'<<|" xchat-1.7.1 CUR~YENi!C
   uM|O!AS:UIYENiYENHYENI pkg_version(1)
   >>'APS:a:YENXCURw,E-a-o(c)O|^3^3nAAe-a(c)YEN>>!A(c)I-aIYENH
   wildcard (,UYENI|rCUR,) -a-oCURe|!!G

 # pkg_delete xchat\*

   YENHCURW+-"OCURl|O"YEN!A+-N.|^2 3/4DEG-L-(c)O|^3YENH xchat
   P:}AY-a-o^3nAAe!C

     --------------------------------------------------------------

  4.4.4. "a:YENL^2O,`^3!YEN-:

   (c)O|^3CURw,E-a-o package ,eDEGT^3-L-.||s"`i /var/db/pkg
   YENO/?yCUR-o!A|b,OYENO/?yCURUYENiYENHS:a:"`iDEGO,u:CURw,E-a-o^3nAAeAE(R)
   *^2M^3aeCURI,O^3nAAeA^2CURP:-a-oAE(R) *!C

     --------------------------------------------------------------

4.5. "IYENI Ports -oTH^2z 3/4-:"i

   CURU+-S:UI.|CURP:^2D-|p|o"IYENI Ports Collection "O|w,E!B^2
   3/4DEG-L-^3nAAe-a-oDEGoYEN>>YENI-ak!C |U:(c)o"a:YENLYENiYENI-a-o
   make ,O^2OYENI-ak>>PAo^1O^3](c)w!AYENiDEGN 3/4\ ports(7)!C

     --------------------------------------------------------------

  4.5.1. DEGO+-o|w,E Ports Collection

   |b|w,EYENoCUR@ ports CURS:<<e!AYEN^2P:.YENy,ECURW Ports Collection
   !X!X YEN|YENDnNOTOYENN /usr/ports CUR-oCUR@DEGi Makefiles, patches
   YENHCURICUR@"C,^3nAAeA^2CURP:AE(c)O^2O|"-a-o!C

   |b,E FreeBSD (R)E!AYS:NCURF|b sysinstall CUR-oCURA:?in,E Ports
   Collection -a-o,U:!A "SAo:<<Y!AYENiYENH.OCURU|CCURe|!"O|w,E ports
   collection!G

   CVSup CURe|!

   "IYENI CVSup NOTO|w,E!BS:o.s Ports Collection
   -a-oS:O:^3tCURe-akCURS:CUR@!C Y.QS:oAA,N CVSup YENI-ak-a-o,U:!A
   1/2D-DEGN 3/4\ "IYENI CVSup!C

     -a`: csup NOTOYENH C >>y"YEN^1i CVSup ^3nAAe-a-o<< 1/4g!A|b
     FreeBSD 6.2 CURICURS:<<a-a(c)YEN>>S:Y|^3-ath|b"t^2ICUR-o!C
     YENiYENH-a 1/2+-uYENI"t^2I(c)O-ath-a-o csup
     S:YYENi,o^1L"BAEJCUR@-a-oDEGES:@!A "A+-NYEN>>CURaaNOTUAo:'-L-"`i
     cvsup CURS:^3B!A ^3-L-S:iNOTDEG csup S:YYENi!C |^1YEN~!A FreeBSD
     6.2 CURS:<<e-a-o-a(c)YEN>>!A<<hYENi,E net/csup (c)I-aI package
     "O"IYENI csup!C

   ^2A:CUR@|,P:] CVSup CURS:<<e!A 1/2D-YENy 1/2T>>{ /usr/ports
   NOTODEG(R)^2b-a-o!I YS:ACURw,g,ECURF Ports Collection
   !A|yCURS|U|aeYEN[CURW"a:YENL patch AE!A"-o>>o CVSup
   "ACUR-L-.|S:RDEG-L-S:A|U|aeYEN[CURW-a-o patch AE!A^3o
   1/4EYENi-`a.| 3/4EPn|w,ENOTY"C,^3nAAe(R)E!A uoYENI patch
   YEN-c-+-N(c)I 1/2sA:P:YEN-c-+-N!C

    1. |w,E net/cvsup-without-gui package!G

 # pkg_add -r cvsup-without-gui

       ^2O,`YENI-ak 1/2D-DEGN 3/4\ |w,E CVSup(uU A.5.2 ,`)!C

    2. DEGo|ae cvsup!G

 # cvsup -L 2 -h cvsup.tw.FreeBSD.org /usr/share/examples/cvsup/ports-supfile

       1/2D-S:a cvsup.tw.FreeBSD.org  1/2D-S:i|"A-:S:ACURn,u-an
       (S:O:)-a-o CVSup YEND 3/4-:!C ^3o^3!CURAYENiYENHDEGN 3/4\S:^1
       3/4a-a-o CVSup mirror -,|C-ai(uU A.5.7 ,`)!C

         -a`: Y.QS:iYENI|UCURv^3]-a-o ports-supfile!ACURn|p>>!!A
         CUR-L-.Q"C|,^3-L-+-oYEN'<<u:YENO"O<<u:(c)w(c)O"IYENI-a-o
         CVSup YEND 3/4-:!C

           1. ^3o-oO/+-!-apCURU!A 1/2D-YENH root AAvS:a
              /usr/share/examples/cvsup/ports-supfile 
              1/2AE>>s"`i"a:YENL|`i,m!ACURn|p /root
              (c)I-aI|UCURv+-b,^1-a-o(R)aYENO/?y!C

           2. *S:i.s-a-o ports-supfile AE!C

           3. S:a CHANGE_THIS.FreeBSD.org
              S:iNOTDEGA-:S:ACURn,u-an(S:O:)-a-o CVSup YEND 3/4-:!C
              ^3o^3!CURAYENiYENHDEGN 3/4\S:^1 3/4a-a-o CVSup Mirrors
              (uU A.5.7 ,`) -,|C-ai

           4. uM<<a'NP:}(c)lYENHAth|u:CURU|C<<u:YENOP:] cvsup!G

 # cvsup -L 2 /root/ports-supfile

    3. DEGo|ae cvsup(1) CURS:<<a!A'N.|P:}(c)lS:o.s Ports Collection!C
       CUR-L-^1L^3oDEGES:@YENuNOTO!yS:o.s!z"ACUR-L-NOTO!yCURE-AA!z!ACUR-L-.|S:aCURw,E-a-o^3nAAe<<.s
       1/2sA:P:!BCURE-AA!C

   Portsnap CURe|!

   portsnap(8) CUR]NOTOS:o.s Ports Collection -a-oCURe|!CURS:CUR@!C
   FreeBSD 6.0 DEG_P:}(c)lCUR-o<<O/ Portsnap 
   3/4-:"i!A|O,uAA-a-o"t^2I!A<<hYENi^3z^1L ports-mgmt/portsnap port
   "O|w,E!G

 # pkg_add -r portsnap

   Portsnap ^2O,`YEN\-`a!A 1/2D-DEGN 3/4\ Portsnap "IYENI 1/2g!C

    1. Y /usr/ports YENO/?yCUR-L-|s|b-a-o,U:!A
       'N<<O/YENssCUR@CURUS:a!G

 # mkdir /usr/ports

    2. +-uCURU"O!ACURU,u:A-L-AY-a-o Ports Collection (c)w'AS:o.sAE"`i
       /var/db/portsnap YENO/?y!C S:^1|"CURU,u:<<a!AnA_
       1/2u>>PS:_^3-L-YENiYENH!C

 # portsnap fetch

    3. YNOTO^2A:CUR@|,P:] Portsnap -a-o,U:!A <<h>>YnYENy,NA-L-"`i
       /usr/ports!G

 # portsnap extract

       YCURw|^3 /usr/ports |OYENBYENuNOTO.QS:o.s|OCURw!A
       "-o>>o'N.OCURU+-S:@!G

 # portsnap update

   Sysinstall CURe|!

   ^3oCURe|!nYENI sysinstall ^3z^1L|w,E"O. 1/2"O,E Ports Collection!C
   1/2D--a`.N!G(c)O|w,E-a-o Ports Collection -a(c)YEN>>YENuNOTO,O
   release uoS:G(R)E-a-o-a(c)YEN>>|OCURw!A|O<<D^3I.s!C
   Y-`aCURW-oo(Internet)-a-o,U:!A
   1/2D-"IYENICURWzCURe|!CURS:CUR@.|CURn,u|n!C

    1. YENH root AAvDEGo|ae sysinstall (|b FreeBSD 5.2
       CURS:<<e-a(c)YEN>><<hNOTO /stand/sysinstall) !ACURe|!|pCURU!G

 # sysinstall

    2. 1/2D-YENHCURe|VAa:^2 3/4DEGE?i 3/4U:P:uYENO/!A?i 3/4U:
       Configure!AuM<<a<<o: Enter Aa:!C

    3. ?i 3/4U: Distributions!AuM<<a<<o: Enter Aa:!C

    4. ?i 3/4U: ports!AuM<<a<<o: Space Aa:!C

    5. ?i Exit!AuM<<a<<o: Enter Aa:!C

    6. ?i 3/4U:nYENI-a-o|w,E"O. 1/2!ACURn|p!GCDROM(YENu-oD-)!BFTP
       uYENCURe|!!C

    7. ?i Exit!AuM<<a<<o: Enter Aa:!C

    8. <<o:CURU X Aa:'NYENiA-:P:} sysinstall u{|!!C

     --------------------------------------------------------------

  4.5.2. Ports -a-o|w,ECURe|!

   '-L-"`i Ports Collection!A-oYENynYENy>>!(c)u-a-oNOTO!G|o? *
   !S:skeleton!"!C A^2^3ae"OA?!Aport skeleton 'NNOTOAAy^3nAAe|p|o|b
   FreeBSD P:P:S:Q 1/2sA:P:!B|w,E-a-o^3IDEGoYEN>>AE(R) *^2O|X!C
   "CYEN-: port skeleton DEGoYEN>>CURW.||^3!G

     * Makefile AE!C ^3oO Makefile CUR-o(R)e|^3CURA^3\|h^3!CURA!A
       NOTOYENI"O<<u:(c)wn|p|o
       1/2sA:P:!AYENHCURI,O,E|b"t^2I-a-o|o^3B!C

     * distinfo AE!C  1/2sA:P:,O^3nAAe(c)O>>YCURU,u:-a-oAE(R)
       *!Bchecksum("IYENI md5(1) CURI sha256(1) "OAEAAc,AE(R)
       *)^3-L-.|DEGO?y|b^3oAE!A YENH 1/2T<<O(c)OCURU,u:-a-oAE(R)
       *NOTOYEN? 1/2TuL>>~-a-o!C

     * files YENO/?y!C ^3oYENO/?y(c)n-a-oNOTOAAy^3nAAeYEN?+-`
       1/2sA:P:!B |w,E-a-o patch AE!C Patches
       AEDEGoYEN>>CURWNOTOCUR@"C,CURpAE(R) *!A"ADEGw^1i-S(c)wAE(R)
       *"ODEGu *S:i!A |OYENBNOTO-ACURaa|rAE(R)ae|!!A
       DEGoYEN>>CURWCUR-o(R)e^3q+-`.|^1^3NOTO !S:Remove line
       10(S:RDEG-L-^2A: 10 |ae)!" (c)I !S:Change line 26 to this
       ...(S:a^2A: 26 |aeS:iNOTDEG...)!" CURS:Ath-a-o!C ^3o"C,
       Patches ^3q+-`CUR]-oUNOTDEG !S:diffs!" !A|]NOTDEG^3-L-NOTOYENN
       diff(1) u{|!(c)O^2-L-YENI-a-o!C

       |^1YEN~!AYEN>>YENO/?yCUR]YENi-`a.|(c)nCUR@"C,"oS:U 1/2sA:P:,O
       port -a-oAE(R) *!C

     * pkg-descr AE!ACUR-o(R)eNOTOCURn,u,O^2O-a-o^3nAAeCURP:^2D-!A
       ^3q+-`.| 1/4g+-oCURn,u|h|ae!C

     * pkg-plist AE!A,O port .||w,E-a-o(c)O|^3AE(R) *^2M^3ae!C
       CUR]NOTOS:iP:D"t^2I|b^2 3/4DEG-L-,O port
       (R)E!A>>YnS:RDEG-L-th"C,AE(R) *!C

   |^3"C, port AU.||^3"a:YENLAE(R) *!A^1^3NOTO pkg-message AE!C port
   "t^2I|bCUR@"C,+-!-ap(R)E!A.|YENI^3o"C,AE(R) *!C |p-aG.Q-a
   3/4^1D^3o"C,AE(R) *-a-oS:o|h^2O,`YENI^3~!AYENHCURI port
   CUR@-eYENI-ak!A 1/2D-DEGN 3/4\ FreeBSD Porter's Handbook!C

   port CUR-o 1/4g-a-oNOTOS:iP:D"t^2I|p|o 1/2sA:P: source code
   -a-oNOTUAo:<<u:YENO!A |y"ACUR-L-NOTO-uYEN?-a-o source code!C |O
   source code YENiYENH+-qYENu-oD-(c)I-oo,o(Internet)"O"u+-o!A
   ,O^3nAAeP:}uo-aIYENi-`a.|S:a source code
   YENH|U-oO/(R)ae|!"OuoS:G!C ^3q+-`NOTOYENH tar YENHCURI gzip
   ^3o"a-aICURu"aCUR@DEG_A-L-AY-a-oAE(R) *!A
   CUR]|^3YENi-`aNOTOYENH"a:YENLCURu"aA-L-AY!A(c)I(R)UYEN>>"SA-L-AY!C
   |O^3nAAe-a-o source code uL 1/2
   *NOTOYENHthCUR@-oO/A-L-AYAE<<NOT-oA!AS:UI^3-L--oUCURS:NOTDEG
   !S:distfile!"!C CURU+-+-NCURP:^2D-"a-oO/|w,E FreeBSD port
   -a-oCURe|!!C

     -a`: n|w,E port -a-o,U:!A 1/2D-DEGEYEN^2CURANOTDEG root "YEN-:!C

     A:uS:i|b|w,EYENo|o port CURS:<<e!A 1/2D-DEGEYEN^2
     1/2T>>{|^3S:o.s Ports Collection "`i^3I.s-a(c)!A |^1YEN~ 1/2D-AE
     3/4\ http://vuxml.freebsd.org/ "OAENOTd(c)On,E-a-o port
     NOTOS:_|^3NOTUAo:|wYENth-o|NOT}A:^3AD>>Yn-a`.N-a-o!C

     portaudit .||b|w,EYENo|o port CURS:<<e!A
     YENy|UDEGEAENOTdNOTOS:_|^3NOTUAo:CURw-a
     3/4-a-o|wYENth-o|NOT}!C^3oOCURu"a|b Ports Collection CUR-o|^3
     (ports-mgmt/portaudit)!C |b|w,E port CURS:<<e!AYENiYENHYENyP:]
     portaudit -F <<u:YENO!A
     |p|^1CUR@"O'N.|S:`i^3I.s-a-o,e|w-o|NOT},e(R)AE(R)w|^"O(R)O:^1i!C
     "CCURN-a-o"t^2I(c)w'A|wAE.||UDEGES:o.s,e(R)AE(R)w!A"AS:@|wYENth
     1/2](R)O:!C ,O+-! 1/2D-DEGN 3/4\ portaudit(1) YENHCURI
     periodic(8) -a-o 1/2uCURW>>!(c)u!C

   Ports Collection .|DEG^2^3]S:A-a-o-oo,oNOTOYENiYEN?+-`^3s
   1/2u-a-o!C |p-aG"S|^3-a-o,U:!A"-o>>o>>YCURaDEGES:a(c)O>>Y-a-o
   distfile AE 1/2AE>>s"`i /usr/ports/distfiles CUR~|ae!C

   P:}(c)l 3/4THS:@CURS:<<e!AnYENyP:iCURJYEN'-oa|w,E-a-o port
   YENO/?yCUR-o!G

 # cd /usr/ports/sysutils/lsof

   CUR@YEN^1P:iCURJ lsof YENO/?y<<a!A'NYENiYENHNOTY"`i^3oO port -a-o
   skeleton u^2-oc!C +-uCURU"O!A'NNOTO 1/2sA:P:!ACUR]'NNOTO
   !S:build!" ^3oO port!C YENu>>YA^2^3ae?eCURJ make
   <<u:YENO!A'NYENi>>'APS:^1|" 1/2sA:P:!C
   S:^1|"<<a!AA^3,OYENiYENHNOTY"`iAth|u:CURU+-DEGT(R)S:!G

 # make
 >> lsof_4.57D.freebsd.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
 >> Attempting to fetch from ftp://lsof.itap.purdue.edu/pub/tools/unix/lsof/.
 ===>  Extracting for lsof-4.57
 ...
 [extraction output snipped]
 ...
 >> Checksum OK for lsof_4.57D.freebsd.tar.gz.
 ===>  Patching for lsof-4.57
 ===>  Applying FreeBSD patches for lsof-4.57
 ===>  Configuring for lsof-4.57
 ...
 [configure output snipped]
 ...
 ===>  Building for lsof-4.57
 ...
 [compilation output snipped]
 ...
 #

   1/2D--a`.N!G
   1/2sA:P:S:^1|"<<a!A'N.||^"`i'-L-YENU:|C(prompt)!C+-uCURU"O'NNOTO|w,E,O
   port CURF!An,E-a-o,U:!AYENu>>Y|b`iYEN>>-a-o make
   <<u:YENO<<a+-|AYEN[CURWCUR@O|rS:YYENi!A "-oO|r'NNOTO install!G

 # make install
 ===>  Installing for lsof-4.57
 ...
 [installation output snipped]
 ...
 ===>   Generating temporary packing list
 ===>   Compressing manual pages for lsof-4.57
 ===>   Registering installation for lsof-4.57
 ===>  SECURITY NOTE:
       This port has installed the following binaries which execute with
       increased privileges.
 #

   CUR@YEN^1|^"`i'-L-YENU:|C(prompt)!A'NYENiYENHDEGo|aee,E-a-ou{|!CURF!C
   YENtYEN~!A|]NOTDEG lsof ^3ou{|!DEGo|ae(R)E.||^3ABYEN~AAv!A
   (c)OYENH.|YENX^2{|wYENthA:uS:i!C|b 1/2sA:P:!B|w,E port -a-o(R)EO!A
   1/2D--d.NYENo|oYENX^2{-a-oA:uS:i!C

   |^1YEN~!A<<O/A:^3S:RDEG-L-
   1/2sA:P:YENI-a-oCURuS:@YENO/?y(^1w^3]NOTO work)!A
   ^3oYENO/?yCUR-oNOTDEG|b
   1/2sA:P:^1Lu{CURCUR(c)OYENI"`i-a-oCUR@"C,A{(R)EAE(R) *!A
   ^3o"C,AE(R) *CUR-L-YENu|uuw-oD--aAAP:!!A|OYENBCUR]YENi-`a.||b,O
   port CURE-AA.s-a(c)(R)E!A ^3y|"CUR-L-YEN^2n-a-oS:xAZ!C

 # make clean
 ===>  Cleaning for lsof-4.57
 #

     -a`: YENI make install clean
     'NYENiYENHCUR@CURf(R)d-S:^1|"e(c)O>>! make!Bmake install!B make
     clean ^3oCURTO"BAEJCURF!C

     -a`: |^3"C, shell .|"I 3/4U PATH Ao^1OAAU: 1/4AE-a-o,o(R)|!A
     S:a"-o"C,,o(R)|-a-oDEGo|aeAE cache
     DEG_"O!A"OYEN[^3t.j'MDEGo|aeAE!C |p-aGS:AYENI-a-oNOTO^3oAth-a-o
     shell!A"-o>>o|b,ES:^1 port <<a>>YnYEN' rehash
     <<u:YENO!ACUR~-`aDEGo|ae.s,E-a-oDEGo|aeAE!A|O rehash
     <<u:YENOYENiYENH|b tcsh CURS:Ath-a-o shell CURW"IYENI!AYNOTO sh
     -a-o,U:!A<<hNOTO hash -r!C ,O+-! 1/2D-DEGN 3/4\S:A(c)O"IYENI-a-o
     shell NOTUAo:CURaaYENo!C

   |^3"C,YENN(c)O? * third-party (c)Ouo|ae-a-o DVD-ROM
   ^2-L-<<~!A^1^3NOTO FreeBSD Mall (c)Ouo|ae-a-o FreeBSD Toolkit
   .|YEN]NOTA distfiles AE(R) *!A ^3o"C,AE(R) *YENiYENI"O.fDEGt Ports
   Collection!C S:a DVD-ROM +- 3/4,u:|b /cdrom!C Y"IYENI"a:YENL+-
   3/4,u:AI-a-o,U:!AnDEGO+-o^3](c)w CD_MOUNTPTS Ao^1OAAU:
   1/4AENOTDEGNOTU^1iA^3-a-o+- 3/4,u:AI!C
   |p|^1CUR@"O!AYENu-oD-CURWY|^3(c)O>>Y-a-o distfiles
   'N.||UDEGE"IYENIYENu-oD--a-oAE(R) *!C

     -a`:  1/2D--a`.N!A|^3CURO: 1/4AE port
     "ACUR-L-CUR^1^3\^3z^1LYENu-oD-"OuoS:GAE(R) *!C
     YENi-`a-a-o`i|]|^3!G>>YYENyP:nuuYENU^3aeCUR~-`aCURU,u:(c)I'^2S:GAE(R)
     *!A(c)I"a:YENL`i|]!C |p-aG.Q|w,E|bYENu-oD-CURW"S-athCURW-a-o
     port!A'N>>Y^3sCURW-oo,oCUR~-`aA:~A:oP:i|ae|w,E!C

   ports "t^2I+-A:YENI fetch(1) "OCURU,u:AE(R) *!A YEN||^3^3\|hYENi
   1/2O 3/4a-a-oAo^1OAAU: 1/4AE!AYEN]NOTA!G
   FTP_PASSIVE_MODE!BFTP_PROXY!B FTP_PASSWORD!C |p-aGNOTO^3B(c)o|^3"
   3/4CURoAd--a-oAo^1O!A (c)I-aI>>Yn"IYENI FTP/HTTP
   proxy!A"-o>>o'N>>Yn^3](c)w^3o"C,AAU: 1/4AE!C "IYENI^2O,` 1/2D-DEGN
   3/4\ fetch(3) >>!(c)u!C

   YuL-akAH(R)ECUR@-a 1/2CURW-oo-a-o,U:!A"-o>>oYENiYENHS:QYENI make
   fetch!C YENun|b port -a-o^3ICURW 1/4h,o(R)|(/usr/ports)
   YEN'^3o<<u:YENO!A"-o>>o(c)O|^3>>YnYENI"`i-a-oAE(R)
   *^3-L-.|CURU,u:!C ^3o<<u:YENOCUR]YENiYENH|bCURU
   1/4hYENO/?y"IYENI!A"O|p!G /usr/ports/net!C  1/2D--a`.N!AY,O port
   |^3NOTU"I-a-o library (c)I-aI"a:YENL port -a-o,U:!A
   "-o>>oYEN|"ACUR-L-.|,ouUCUR@DEG_CURU,u:"a:YENL(c)ONOTU"I-a-oAE(R)
   *!C Y.QCUR@|,CURU,u:(c)O|^3NOTU"I-a-o port (c)O|^3AE(R)
   *!A"-o>>o<<u:YENODEGN 1/4AE 1/2D-S:iYENI fetch-recursive |O<<D
   fetch!C

     -a`: YENiYENH|bNOTYAthS:O(c)I^3ICURW 1/4h,o(R)|YEN' make
     <<u:YENO"O 1/2sA:P:(c)O|^3-a-o port!A(c)I-aIYENHCURWz-a-o make
     fetch <<u:YENO"OCURU,u:(c)O|^3AE(R) *!C uM|O!A^3o
     1/4ENOTONOTU.i|MAI!A|]NOTDEG|^3"C, port CUR-L--`a"A|s!C
     CUR]|^3YENtCUR@-oO/+-!-ap!A|^3"C, port YENi-`a.|YENHNOTU|PAE|W!A
     |yNOTO^1e>>UCURW<<oNOTOCUR-L-|PCUR-o(R)e-a-oAE(R) *!C

   |bNOTY"C,"u"-L-+-!-ap!AYENi-`a>>YYEN[CURW MASTER_SITES (AE(R)
   *-a-o`i(c)lCURU,u:^3B)CURS:YEN~-a-oCURU,u:AI!AYENHCURU,u:(c)O>>Y-a-oAE(R)
   *!C YENiYENHYENICURU|C<<u:YENO!A"OS:oS:i^1w^3]-a-o MASTER_SITES
   CURU,u:AI!G

 # cd /usr/ports/directory
 # make MASTER_SITE_OVERRIDE= \
 ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ fetch

   CURW+-^3o"OCURl!ANOTOS:a MASTER_SITES S:i^3]
   ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/ NOTDEGCURU,u:AI!C

     -a`: |^3"C, port CUR^1^3\((c)In"D)+-z+-o<<u:(c)w 1/2sA:P:?iP:u!A
     YENH+-OYENI!BDEG+-YENI,O^3nAAeCURCUR<<DYEN^2P:.-a-oYEN\-`a!B|wYENth?iP:uYENHCURI"a:YENLYENi|Uq-a-o?iP:u!C
     "a|^3YENN-ai(c)E-a-oYEN]NOTACURF
     www/mozilla!Bsecurity/gpgme!Bmail/sylpheed-claws!C
     Y|^3^3oAth?iP:u(R)E!A^3q+-`|b
     1/2sA:P:(R)E.|YENX^2{NOTUAo:'-L-YENU:DEGT(R)S:!C

     --------------------------------------------------------------

    4.5.2.1. S:oS:i(Override)^1w^3]-a-o Ports YENO/?y

   |^3(R)EO!A.|uo^2{"`i"IYENI"a:YENLYENO/?yS:@NOTDEG port!Bdistfiles
   YENO/?yYENi-`aNOTU.i|^3YENI(NOTAE|U:NOTOYEN^2P:.)!AYENiYENH^3](c)w
   PORTSDIR CURI PREFIX Ao^1OAAU: 1/4AEYENH *S:i^1w^3]-a-o port
   YENO/?y!CA|"O!G

 # make PORTSDIR=/usr/home/example/ports install

   YENHCURW.||b /usr/home/example/ports CUR-oP:i|ae 1/2sA:P:!A
   "AS:a(c)O|^3AE(R) *|w,E"`i /usr/local CUR-o!C

 # make PREFIX=/usr/home/example/local install

   <<h.||b /usr/ports YENO/?yCUR-o 1/2sA:P:!A "AS:a(c)O|^3AE(R)
   *|w,E"`i /usr/home/example/local CUR-o!C

   .iuMAAo!A

 # make PORTSDIR=../ports PREFIX=../local install

   <<h.||P(R)EYEN]S:t"a-oO/^3](c)w(AU|^3<<U:|hAAU:CURAEYENHPuL-ak|bYEN>>P:YENth^3!^3-L-|^3
   1/4g"`i!A |y+-zA^3,OCURw,g|^3S:`i"`iCURj.S:.S:(c)ACURFS:a)!C

   |^1YEN~!A^3o"C,AAU: 1/4AECUR]YENHS:@NOTDEGAo^1OAAU:
   1/4AE"O^3](c)w!C  1/2D-"I+-z(c)O"IYENI-a-o shell YENhDEGN
   3/4\NOTUAo:>>!(c)u!AYENHAA,N|p|o^3](c)w!C

     --------------------------------------------------------------

    4.5.2.2. ^3B^2z imake

   |^3"C, port .|"IYENI imake(X Window "t^2I-a-oCUR@^3!YEN-:)
   uL-akYEN?+-`^1BYENI PREFIX AAU: 1/4AE!A YEN|I.|DEGi<<uS:aAE(R)
   *^3-L-|w,E"`i /usr/X11R6 YENO/?y!C |P 1/4E|a!ACUR]|^3CUR@"C, Perl
   port .|(c)?^2CUR PREFIX "AS:aAE(R) *|w,E"`i Perl
   YENO/?yNOT[-ocCUR-o!C AAy^3o"C, ports respect PREFIX
   NOTONOTU.iS:xAo/!ANOTAE|U:NOTOCUR-L-YENi-`a-a-o"AE!C

     --------------------------------------------------------------

    4.5.2.3. <<.s^3](c)w Ports ?iP:u

   |b 1/2sA:P:NOTY"C, port (R)E.|YENX^2{?i^3aeue+-(ncurses-based)!A
   YENiYENHYENI"O?i 3/4U:|w,E?iP:u!C ^3q+-`,E|n,O port
   CURS:<<a!A<<KCUR-L-CURO.|>>Yn<<YEN[!B ^2
   3/4DEG-L-!BS:oS:iCUR@"C,.i-a`i|w,E-a-o?iP:u!C
   |yCURe<<aY|^3>>Yn-a-o,U:!A CUR]|^3^3\|hCURe|!YENiYENH 1/2O
   3/4a^3o"C,?iP:u!C "a:CURCURCUR@-oO/CURe|!<<KNOTOCURA"`i,O port
   YENO/?y!A "AYEN' make config S:YYENi|A|,|^"`i?iP:uue+-YENhS:@ 1/2O
   3/4a!C YENtYEN~AUYENiYENI make showconfig YENHAAaYENU:,O port
   |w,E(R)E(c)OYENI-a-o?iP:u!C CUR]YENiYENHYENI make rmconfig
   "OS:a(c)O|^3?iP:u|^"`i-a`i(c)l^3](c)w!C
   ^3o"C,?iP:u,o"a:YENLDEGES:@^3-L-YENiDEGN 3/4\ ports(7)
   CUR-o-a-o,O^2O>>!(c)u!C

     --------------------------------------------------------------

  4.5.3. ^2 3/4DEG-L-CURw|w,E-a-o Ports

   ^2{|b+-zCURw,g-a 3/4^1D|p|o|w,E port!A|OP:}(c)l.QAA,N|p|o^2
   3/4DEG-L-!C CURn|p,ECURFCUR@O port <<aCUR~.NAN"`i,E?u port CURF!C
   |b|^1!AS:UI+-N^2 3/4DEG-L-<<e+-"OCURl(c)O,E-a-o"-oO port
   ("SYENJ^2O-a`.N-a-o,U:!AS:UI|A'-L-?oCUR@CURU'NNOTO lsof)!C ,o^2
   3/4DEG-L- package (R)ENOTU.iAth|u:(|b Packages section
   |^3CURP:^2D-)!A^3-L-NOTO"IYENI pkg_delete(1) <<u:YENO!G

 # pkg_delete lsof-4.57

     --------------------------------------------------------------

  4.5.4. CURE-AACURw|w,E-a-o Ports

   -oYENy!AYENI pkg_version(1) <<u:YENO"O|CYENXYENO/<<e Ports
   Collection CURCUR'-L-"NCURF"-o"C,YENiCURE-AA-a-o port -a(c)YEN>>!G

 # pkg_version -v

     --------------------------------------------------------------

    4.5.4.1. /usr/ports/UPDATING

   "C|,S:o.sS:^1 Ports Collection CURS:<<a!A
   1/2D-DEGEYEN^2DEGO+-o|bCURE-AA port <<e!A YENyNOTYNOTY
   /usr/ports/UPDATING!A ^3o,I.|
   1/4gCURE-AACURe+--a-o|U|!DEGYAD!ACURn|p!GAE(R)
   *(R)ae|!S:iAAU:!BAAU:S:o^3](c)wAE|`i,m!B
   >>PAA-a(c)CUR-L-NOTU(R)e-a-oDEGYADuYEN!AYENHCURI<<c,>>o,N"M-a-oS:^1
   3/4a"BAEJ!C

   Y UPDATING
   CUR-o(R)e>>PS:ANOTY"`i-a-o"a:YENLCURaaYENo|^3"C,CUR-L-|P !BNOTU
   1/2A:-a-o,U:!A "-o>>o 1/2D-YENH UPDATING NOTDEG.C,!C

     --------------------------------------------------------------

    4.5.4.2. YENH Portupgrade "OCURE-AACURw|w,E-a-o Ports

   portupgrade YENiYENH>>'APCURE-AACURw,E-a-o^3nAAe!C ,OCURu"aYENi+-q
   ports-mgmt/portupgrade port |w,E!A |w,ECURe|!'N|p|P"a:YENL port
   CUR@ 1/4E!AYENI make install clean <<u:YENO'NYENiYENHCURF!G

 # cd /usr/ports/ports-mgmt/portupgrade
 # make install clean

   -oYENy^3I|nYENyYENH pkgdb -F "O+- 1/2-oECURw,E-a-o ports
   ,e(R)AE(R)wNOTOS:_|^3>>~!A"A *YEN?|^3DEGYAD-a-o|aCURe!C
   |b"C|,DEGuCURE-AACURS:<<e!A^3I|n(c)w'ADEGuCUR@CURU pkgdb -F
   DEGES:@.|,uNOTDEGS:'.i!C

   P:] portupgrade -a -a-o,U:!A portupgrade
   .|CURE-AA"t^2ICURW(c)O|^3CURw,E-a-o^1LAA ports!C YYENI -i
   <<h|bCURE-AA"CO port ^1Lu{.iCURCUR!A .|n"D
   1/2T>>{NOTUAo:DEGES:@NOTOS:_^2AA|X(c)O>>Y!C

 # portupgrade -ai

   YYENu.QCURE-AANOTY-S(c)wu{|!|O<<DYENth^3!!A"-o>>oYENiYENHYENI
   portupgrade pkgname "ODEGu<<u:(c)w!C Y.Qn portupgrade
   AuYENyCURE-AANOTY port (c)ONOTU"I-a-oNOTUAo:(R)MYENo!A<<h
   1/2D-YENI -R DEGN 1/4AES:YYENi!C

 # portupgrade -R firefox

   YnYENI package |O<<D port "O|w,E!A<<h>>Y<<u:(c)w -P CUR~YENiYENH!C
   Y|^3<<u:(c)w^3o?iP:u!A<<h portupgrade .|.j'M PKG_PATH AAU:
   1/4AE(c)O<<u:(c)w-a-oYEN>> 3/4-:YENO/?y!A
   YS:a:CUR-L-"`i<<h^3z^1L-oo,o"OCURU,u:|w,E!C YYEN>>
   3/4-:,o-oo,o^3-L-"S|^3YENiYENI-a-o package -a-o,U:!A<<h
   portupgrade .|"IYENI port CURe|!|w,E!C
   YCUR-L-.Q|p|^1CURSAAU:|""IYENI port CURe|!|w,E!A<<hYENI -PP
   S:YYENi+-j"iA *S:K"IYENI port CURe|!|w,E!C

 # portupgrade -PP gnome2

   YYENu.QCURU,u: distfiles((c)I-aIY<<u:(c)w -P -a-o,U:!A<<hNOTO
   package)|OCUR-L-.Q 1/2sA:P:(c)I|w,EAE(R) *!AYENiYENH"IYENI -F!C
   ,O+-! 1/2D-DEGN 3/4\ portupgrade(1) -a-o>>!(c)u!C

     --------------------------------------------------------------

    4.5.4.3. YENH Portmanager "OCURE-AACURw|w,E-a-o Ports

   Portmanager CUR]YENiYENHYENI"O>>'APCURE-AACURw,E-a-o^3nAAe!C
   ,OCURu"aYENi+-q ports-mgmt/portmanager port |w,E!G

 # cd /usr/ports/ports-mgmt/portmanager
 # make install clean

   (c)O|^3CURw,E-a-o^3nAAe!A^3-L-YENiYENH>>'APYENIAth|u:CURU|C<<u:YENO"OCURE-AA!G

 # portmanager -u

   |^1YEN~!A"IYENIDEGN 1/4AEYENiYENHS:iNOTDEG -ui!A|p|^1CUR@"O
   Portmanager |bCURE-AACUR@"C,|^3-S(R)i?iP:u-a-o^3nAAe(R)E
   !A'N.|,ssDEGY,O|p|oCURE-AA!C Portmanager CUR]YENiYENHYENI"O,E.s
   port!C>>PYENH(c)^1+-`YENI-a-o make install clean
   <<u:YENOCUR-L-|PCURS:^3B|b(c)o!G YEN|.|YENyCURE-AAS:An,E-a-o port
   (c)ONOTU"I-a-o(c)O|^3 ports!AuM<<aCUR~P:}(c)l 1/2sA:P:!B
   |w,En,E-a-o port!C

 # portmanager x11/gnome2

   Yn,E-a-o port
   CURS:^3nAAeNOTU"IAo:<<Y|^3DEGYAD(R)E!ACUR]YENiYENHYENI Portmanager
   "IYEN|I<<AkYEN?y!C |O Portmanager
   ,N"MNOTU"IDEGYADS:^1^2|CURS:<<a!A,O port CUR].|<<.s
   1/2sA:P:!AYENH|]A^3YEN? 1/2T-a-oNOTU"IAo:<<Y!C

 # portmanager graphics/gimp -f

   "a: 3/4l^1BYENI-ak-au!A 1/2D-DEGN 3/4\ portmanager(1) >>!(c)u!C

     --------------------------------------------------------------

  4.5.5. Ports >>Puw-oD--aAAP:!

   |]NOTDEG"IYENI Ports Collection
   ?d-|YENi-`a.|YENIYENuuw-oD--aAAP:!!A
   (c)OYENH|b,ES:^1^3nAAe<<a!ADEGO+-onYENH make clean
   <<u:YENO"O^2MDEG-L-A{(R)E-a-o work YENO/?y!C
   |^1YEN~!AYENiYENHYENICURU|C<<u:YENO"O^2MDEG-L- 3/4aO Ports
   Collection CUR-o-a-oA{(R)EYENO/?y!G

 # portsclean -C

   ports YENICUR[CURF!A+-zYENi-`a.||b distfiles
   YENO/?yCUR-o.|^2O:?nuU^3\|h-a-o`i(c)l 1/2XAE(R) *!C
   YENiYENHCURaDEGES:RDEG-L-^3o"C,AE(R) *!A
   (c)I-aIYENICURU|C<<u:YENO"O^2MDEG-L-(c)O|^3 port
   ^3-L-CUR-L-"IYENI-a-oAAAE!G

 # portsclean -D

   (c)I-aIn^2MDEG-L-(c)O|^3CURw,E-a-o port
   ^3-L-CUR-L-|A"IYENI-a-oAAAE!G

 # portsclean -DD

     -a`: portsclean ^3oCURu"aCURDNOTO portupgrade
     (R)MYENo-a-oCUR@^3!CURA!C

   CUR-L-nS:NCURF^2
   3/4DEG-L-"-o"C,CURw,g|w,E!A|yCUR-L-|A>>YnYENI"`i-a-o ports!C |^3O
   ports-mgmt/pkg_cutleaves
   port!AYEN?NOTOYENi|UDEGES:^1|"^3oYEN\-`a-a-o|nCURu"a!C

     --------------------------------------------------------------

4.6. |w,ECURS:<<a!A|^3CURDEG>>o<<aA:o-a`.N"AEP:uP:U:!H

   ^3q+-`!A|w,ES:^1^3nAAe<<a!AS:UIYENiYENH
   3/4\AA-a(c)O-ath-a-oCUR@"C,CURaaYENo!A(c)I>>Yn 1/2s?e^3](c)wAE!A
   "O 1/2T<<O^3oO^3nAAe-`aP:P:S:Q^1BS:@!A(c)I|b 3/4-: 3/4^1P:}
   3/4-:-a-o(R)EO+-ODEGE(|p-aGNOTO daemon -a-o,U:) uYENuYEN!C

   CUR-L-|P-a-o^3nAAe.||^3CUR-L-|P-a-o^3](c)w"BAEJ!CCUR-L--oTH<<c,
   1/4E!A|p-aG,E|nCURF^3nAAe!A |yNOTOCUR-L--a
   3/4^1DCURUCUR@"B<<c,>>o?`i-a-o(R)EO!A
   YENiYENH,O,ONOTY^3o"C,CURpS:THYEN(c)!G

     * u 1/2YENI pkg_info(1)
       !A^3o<<u:YENOYENiYENHAAaYENU:!G^3z^1L(R)MYENo-oTH^2z"t^2I
       (Packages/Ports),ECURFth"C,^3nAAe!BAE(R)
       *,E|bthAa:!CA|"O"O>>!!AYe,ECURF FooPackage (-a(c)YEN>>
       1.0.0)!A"-o>>oCURU+-^3o<<u:YENO!G

 # pkg_info -L foopackage-1.0.0 | less

       'N.|AAaYENU:^3o^3nAAe(c)O|w,E-a-oAE(R) *^2M^3ae!C 
       1/2D--SS:O-a`.N|b man/ YENO/?yCUR-oNOTO>>!(c)uAE!B etc/
       YENO/?yCUR-oNOTO^3](c)wAE!B doc/ YENO/?yCUR-oNOTOS:^1
       3/4aCURaaYENo!C

       YCUR-L-
       1/2T(c)wCURw,E-a-o(R)MYENo-a(c)YEN>>NOTDEG|o!AYENiYENHYENIAth|u:CURU|C<<u:YENO"ONOTd!G

 # pkg_info | grep -i foopackage

       YENHCURW+-N.|.j'M(c)O|^3CURw,E-a-o(R)MYENo!A|CYENX|^3^2AA|X
       foopackage -a-o(R)MYENo|W-oU!C  1/2D-|U|ae"I>>Y"D!A *S:i
       foopackage NOTDEG.QS:a:-a-o(R)MYENo|W-oU!C

     * CUR@YEN^1 1/2T>>{,Ou{|!-a-o
       1/2uCURW>>!(c)u|^3|w,E!A'NYENiYENHYENI man(1) "OA 1/2 3/4\!C
       |P
       1/4E|a!AY,Ou{|!|^3'-L-"N-a-o,U:!ACUR]YENiYENHDEGN|O^3](c)wAE
       1/4EYEN>>!AYENHCURI"a:YENLCURaaYENo!C

     * Y,Ou{|!|^3(c)x-oo-a-o,U:!AAUYENiYENH^3z^1L-oo-,"OS:a:CURaaYENo!B+-`"-L-DEGYu-aP:DEG(FAQ)uYEN!C
       YCUR-L--a 3/4^1D-ooS:}!A 1/2D-YENICURU|C<<u:YENO!G

 # pkg_info foopackage-1.0.0

       Y,Ou{|!|^3(c)x-oo-a-o,U:!A<<h.||^3CUR@|ae WWW:
       P:}AY-a-oYENX^2{!A^3o|ae.||CYENX,Ou{|!-a-o(c)x-oo-ooS:}(URL)!C

     * Port YP:.|bP:} 3/4-:(R)E'N.|+-ODEGE('N^1^3 Internet YEND
       3/4-:)!A^3q+-`^3-L-.||w,E script "`i /usr/local/etc/rc.d
       YENO/?y!C +-zYENiYENHAE 3/4\^3o script -a-oYEN?
       1/2T>>PS:_!A(c)IY|^3>>Yn!ACUR]YENiYENH *S:i!BS:i|W!C ,O+-!
       1/2D-DEGN 3/4\ +-ODEGE Services!C

     --------------------------------------------------------------

4.7. |p|o^3B^2zA:e+- 1/4(Broken)-a-o Ports!H

   |p-aGuo^2{NOTYO port uL-akP:P:S:Q|w,E!B^1BS:@!A
   |^3'X-oO/CURe-akYENiYENH,O,ONOTY!G

    1. +-q Problem Report ,e(R)AE(R)w
       CURCUR<<oA:_NOTYNOTY!A>>!CUR-L-(c)wCURw,g|^3CURHDEGeYENiYENI-a-o
       patch CURWYENhAAo!A
       "-o>>o(c)I^3\'NYENiYENHP:P:S:Q,N"MDEGYADu!C

    2. |V,O port -a-o maintainer 'M"D"oS:U!G 1/2D-YEN' make
       maintainer (c)IA 1/2 3/4\ Makefile YENHNOTd,ss maintainer -a-o
       email address!CDEGO+-o+-H<<Hu^1 maintainer (R)E!An-athuu,O
       port -a-o|W-oU!B-a(c)YEN>>((c)INOTOS:a Makefile CUR-o-a-o
       $FreeBSD: "-oCUR@ 3/4a|ae-athCURW)
       YENHCURINOTUAo:?u>>~DEGT(R)S:!C

         -a`: |^3"C, port CUR-L-NOTOYENN+-M-au-a-o^3aeCUR@ maintainer
         t^3d!A|ONOTO^3z^1L mailing list -a-o+-MADDEGQ 1/2
         *!C^3\|h(|y<<DYENth^3!)-a-oApu, email (R)ae|!^3q+-`NOTO
         <freebsd-list|W-oU@FreeBSD.org> !CuoDEGY(R)E!A
         1/2D-DEGO+-oS:a!yfreebsd-list|W-oU!zS:iNOTDEGNOTUAo:DEGQ 1/2
         *-a-o mailing list |W-oU!C

         CUR *"a:.i port -a-o maintainer A:ae|`iNOTO
         <freebsd-ports@FreeBSD.org> (R)E!A"AE^1eCURWCURw,g"SCURH.i,O
         port maintainer CURF!C |]|^1Y,O port CUR'|^3
         *YEN?(c)I"a:YENLS:TH^3NCURa:'(c)-a-o,U:!ANOTUAo:DEGQ 1/2
         *^3-L-.||b freebsd-ports P:l>> 1/4 1/2 * 3/4ACURWYENX^2{!C
         ^3a!A^1iCURF!A|p-aG|^3 1/4o+-x,O^3nAAe-aI!AS:OA:@.i,O port
         maintainer
         -a-o,U:!AS:UICUR]^3-L-<<U:AAw-ai+-z-a-oYEN[CURJ^3a!C

       Y port maintainer "S|^3|^AD-+-z-a-o<<HYENo!A <<hYENiYENHYENI
       send-pr(1) "O'-L-YENaeDEGYAD^3o/S:i PR!C( 1/2D-DEGN 3/4\
       Writing FreeBSD Problem Reports)!C

    3. ,O,ONOTY *YEN?YEN|S:a! Porter's Handbook YEN]NOTACURF
       !S:Ports!"
       NOT[-oc-a-o^2O,`^3!YEN-:!A^3o"C,(R)NCURCURCUR-o(R)e|^3S:U+-z
       *|n|^3DEGYAD-a-o port NOTAE|U:'-L-YENae|UCURv-a-o port!T

    4. +-q,u-an-a-o FTP -,AICURU,u: 1/2sA:P:|n-a-o package!C package
       collection -a-o^3ICURW'aa-,NOTO|b ftp.FreeBSD.org CURW-a-o
       packages YENO/?yCUR-o!A|y 1/2D-DEGO+-oYENyAENOTdNOTOS:_CURw|^3
       local mirror -,!I ^3q+-`+-!-apCURU^3o"C, package
       ^3-L-YENiYENH-a 1/2+-u"IYENI!A |OYENBA^3,OCURn|U|ae
       1/2sA:P:S:O:CUR@"C,!C YENI pkg_add(1) S:YYENiP:P:S:Q|w,E
       package !C

     --------------------------------------------------------------

                      ^3^1 5. X Window uo/u!"t^2I

   Updated for X.Org's X11 server by Ken Tom YENB Marc Fonvieille.

5.1. .S:z

   FreeBSD "IYENI X11 "O'-L-"N"IYENI-aINOTU.i|nYENI-a-o GUI CURP:+-!C
   X11 NOTO X Window "t^2I!AYEN]NOTA Xorg YENHCURI XFree86
   ^1eS:@-a-o|UYENN^3nAAe-a(c)YEN>> (YENHCURI"a:YENLYEN
   1/4|bYEN>>^3^1|^3CURP:^2D--a-o^3nAAe)!C FreeBSD CUR@-a 1/2"`i
   FreeBSD 5.2.1-RELEASE ^3-L-CUR'YENi|b^1w^3]-a-o|w,Eu{|!CUR-oYENh,E
   XFree86 (YENN The XFree86 Project, Inc uo|ae-a-o X11 server)!C |O
   FreeBSD 5.3-RELEASE DEG_!A^1w^3]-a-o X11 S:iNOTDEG Xorg(YENN X.Org
   DEGo-a-:.|(c)OP:}uo-a-o X11 server!A"A+-A:YENI>>P FreeBSD
   NOTU.iAth|u:-a-o license)!C |^1YEN~!A.iuMCUR]|^3DEGO.~ X servers
   -a-o FreeBSD -a(c)!C

   YEN>>^3^1YENDnNOTOCURP:^2D- X11 (YENDnuU<<(c)o Xorg 7.5.2
   -a(c)^3!CURA)-a-o|w,E>>P^3](c)w!C Y+-yAA,N XFree86
   -a-o,O^2O,e(R)AE(|'A-a-o FreeBSD CUR-o!A XFree86
   CURDNOTO^1w^3]-a-o X11 (R)MYENo)!A 1/2D-DEGN 3/4\AA-a(c)-a-o
   FreeBSD Handbook!A-ooS:}NOTDEG http://docs.FreeBSD.org/doc/ !C

   +-y-a 3/4 X11 ^1i(c)oAAaYENU:CURe+-uwAAe-a-oCURa:'(c)+-!-ap!A
   1/2D-DEGN 3/4\ Xorg -oo-,!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!G

     * X Window
       "t^2I-a-o|U^2O|"^3!YEN-:!AYENHCURIYEN|INOTO|p|oNOTUCURNOT^1BS:@!C

     * |p|o|w,E!B^3](c)w X11!C

     * |p|o|w,E"A"IYENICUR-L-|P-a-o window managers!C

     * |p|o|b X11 CURW"IYENI TrueType(R) |r<<NOT!C

     * |p|o^3](c)w"t^2IYENH"IYENI^1IS:IunCURJCURP:+-!C (XDM)

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!J

     * -a 3/4^1D|p|o^1BYENI ports!Bpackages "O|w,E^3nAAe!C (uU 4
       ^3^1)

     --------------------------------------------------------------

5.2. AA,N X -a-oYEN@NOTE

   ^2A:CUR@|,+-uA:^2 X -a-oCURH!ACURj.S:^3-L-.||^3"C, 3/4_ 3/4U!ACUR
   *"a:NOTO 1/4o+-x"a:YENL GUI CURP:+-(^1^3NOTO Microsoft Windows
   (c)I Mac OS)-a-o"IYENI-aI!C

   Ao:uM X
   |UCUR,YENo-a-o(c)O|^3^2O,`CURI^1BS:@CURe|!!A"ACUR-L-NOTOYEN^2P:.n-a
   3/4^1D-a-o!C
   |y^1iYEN|I|^3"C,DEGoYEN>>.S:(c)A.|S:o(R)e(c)o:CURWCURa!C

     --------------------------------------------------------------

  5.2.1. NOTDEG|oYENsDEGu X!H

   X "A<<D UNIX CURW^2A:CUR@(R)Muo/u!"t^2I!A|yYEN|<<oNOTO^3I
   1/4sNOTDEGNOTyP:C,^1BYENI!C `iYEN>>-a-o X NOTauo^1IP:CUR|bNOTauo X
   CURS:<<e|^3P:}uoYENtCUR@(R)Muo/u!"t^2I!C "-o(R)M"t^2IYENsDEGu
   !S:W!"("u !S:Window!" -a-o^2A:CUR@O|r)!C |O X <<hNOTO W
   CURS:<<a-a-oCURUCUR@OA^1DEG"|rYENA!C

   X YENc,^3Q-oUCURS:NOTDEG !S:X!"!B!S:X Window System!"!B
   !S:X11!"!AYENHCURI"a:YENLCUR@"C,uu:.J!C "IYENI !S:X Windows!"
   ^3o|r^2'"O-oU(c)I
   X11!AYENi-`a.|AAy|^3"C,CURHCUR-L-^2n!F^3o^3!CURA^2O,`YENiDEGN 3/4\
   X(7) >>!(c)u!C

     --------------------------------------------------------------

  5.2.2. X -a-o Client/Server NOT[-oc

   X CUR@P:}(c)lNOTO^3]pNOTDEG-oo,oNOT[-ocAo^1O!A"A+-A:YENI
   !S:client-server!" NOT[-oc!C

   |b X NOT[-ocCURU!A !S:X server!" NOTO|b|^3Aa:
   1/2L!B?A^1o!B.AE^1<<-a-o^1q,-L-CURW^1BS:@!C |O server
   ^3!YEN-:<<hNOTOt^3d^1^3NOTOAAaYENU:^3!YEN-:-a-o-oTH^2z!B
   ^3B^2z"O|UAa:
   1/2L!B.AE^1<<CURI"a:YENL^3]^3AE(CURnCURe^1^3NOTOYENHA,^1I-aO"O?eCURJ!B
   (c)I-aINOTOAAaYENU:"`iS:e 1/4v 3/4-:)-a-o?eCURJuYENuYEN!A "CO X
   u{|!(^1^3NOTO XTerm!A(c)I Netscape)^3-L-NOTO !S:client!"!C client
   .|P:C,DEGT(R)S:"`i server CURW!ACURn|p!G!S:Please draw a window at
   these coordinates!"!A+-uuU server .|P:C,|^DEGT(R)S:!ACURn|p!G
   !S:The user just clicked on the OK button!"!C

   |b(R)a(R)x(c)ICURp?`iCUR 1/2<<C,Ao^1O!A^3q+-` X server ,o X client
   ^3-L-NOTO|b|PCUR@YENx^1q,-L-CURWDEGo|ae-a-o!C
   uM|O!ACUR]YENiYENH|bCURn,uA:e-a-o(R)`a 3/4-:CURWDEGo|ae X server!A
   "A|bCURn,u+-j!BCURn,uP:Q-a-o^1q,-L-CURWP:] X
   u{|!(client)"ODEGu"AE+-!!C |b^3o-oO/^3o'-o!AX client >>P server
   CURS:P:!-a-o. 3/4^3q'N>>Y^3z^1L-oo,o"OP:i|ae!C

   ^3oAIYENi-`a.|AAy|^3"C,CURH^2-L-YENIS:x'b!A|]NOTDEG X
   ^3N>>y>>PYENLI`iYEN>>-a-o>>{-a 3/4e|nNOTUCURI!C
   YENLI`iYEN>>YENHNOTDEG !S:X server!" NOTOn|b^3I+-j(R)<<-a-o 3/4-:
   3/4^1CURWP:]CUR~|ae!A|O !S:X client!" <<hNOTO|bYENLI(R)`a
   3/4-:CURW+-P:]!C ^1e>>UCURW<<oCUR-L-NOTO^3o 1/4E!C

   |^3AINOTU.i<<n!A 1/2D-DEGO|i X server NOTO|b|^3+-u?A^1o!BAa:
   1/2L-a-o 3/4-: 3/4^1CURW^1BS:@!A |O X client
   <<hNOTOAAaYENU:^3o"C,uo/u!-a-ou{|!!C

   "o(c)w(protocol)CUR-o"AuL+-j"i^3W(c)w client YENHCURI server "aAa:
   3/4-: 3/4^1^3-L-+-oNOTO|PCUR@S:@.~"t^2I!A(c)I-aI+-oNOTO|P<<NOT
   3/4-: 3/4^1CUR~YENiYENH!C '<<YENy,U:>>!!ACUR]YENiYENH|b
   Microsoft Windows (c)IA:<<-aG^1q,-L-(Apple)-a-o Mac OS CURWP:] X
   server!A|OYENBYENiYENH^3z^1L^3\|hS:KP:O(c)IDEGO.~^3nAAeS:^1|"^3o"C,|w,E!B^3](c)w!C

     --------------------------------------------------------------

  5.2.3. The Window Manager

   X ^3]po 3/4C,>>P UNIX ^3]po 3/4C,NOTU.iAth|u:!A^3-L-NOTO !S:tools,
   not policy!"!C CUR]'NNOTO>>!!AX
   CUR-L-.|,O^1I+-j"i^3W(c)wNOTYYENoDEGEA^3,On|p|oS:^1|"!A|ONOTOYENu'-L-"N"IYENI-aICUR@"C,CURu"a!A
   |U:(c)o|p|o^1BYENI^3o"C,CURu"a!A<<hNOTO"IYENI-aIYEN>>"-a-o"AECURF!C

   X (c)uA:o^3oo
   3/4C,!AYEN|"ACUR-L-^3W(c)w!G?A^1oCURW-a-ouo/u!,O-ao/CURDEG>>o
   1/4E!Bn|p|o^2 3/4DEGE.AE^1<<<<u: 1/4D-!B
   ,OYENICURDEG>>o^2O|XAa:"OCURA'<<|Uuo/u!(CURn|p!G|b
   Microsoft Windows -a-o Alt+TabAa:)!B|Uuo/u!-a-o
   1/4D-AD|C-ao/NOTU!AYENHCURINOTOS:_,O|^3Ao:^3NOTP:suYENuYEN!C

   "AE^1eCURW!AX S:a^3o^3!CURAYENaeu^1(c)O? *-a-o !S:Window Manager!"
   "O-oTH^2z!C |^3CUR@DEGi window manager u{|!!A^1^3NOTO: AfterStep
   !BBlackbox!Bctwm !BEnlightenment!B fvwm!BSawfish!B twm!B Window
   Maker uYENuYEN!C"CCUR@-oO/ window manager
   ^3-L-'-L-"NCUR-L-|P-a-o"IYENI,gAAc,!F |^3"C,AUYENi"IYENI
   !S:virtual desktops(ueAA(R)`a+-)
   !"!F|^3"C,<<hYENi|Uq^2O|XAa:"O-oTH^2z(R)`a+-!F|^3"C,.||^3
   !S:Start(P:}(c)l) !"P:s(c)I"a:YENLAth|u:^3]p!F|^3"C,<<hNOTO
   !S:YENiS:o'<<S:G'-oYENDAD!"!A
   YENi|U|ae|w,E.s-a-oS:G'-oYENDADYENHS:o'<<YEN~AE[!C
   ^3o"C,,o"a:YENL-a-o window manager |b Ports Collection CUR-o-a-o
   x11-wm YENO/?yCUR-o^3-L-|^3!C

   |^1YEN~!AKDE CURI GNOME (R)`a+-Ao^1O<<h|^3"a:|UA:Y"A 3/4a|XS:^1
   3/4a-a-o window manager!C

   "CO window manager CUR]|U|^3"a:CUR-L-|P-a-o^3](c)w
   3/4-:"i!F|^3"C,>>YCURaDEGE 1/4g^3](c)wAE!A |O|^3-a-o<<hYENi^3z^1L
   GUI CURu"a"OS:^1|"CURj^3!CURA-a-o^3](c)w!CA|O"OCURl!G Sawfish
   'N|^3YENH Lisp >>y"YEN 1/4g-a-o^3](c)wAE!C

     Focus Policy: window manager
     -a-oYENtCUR@-S|a'NNOTOt^3d.AE^1<<<<u: 1/4D--a-o !S:focus
     policy!"!C "CCUR@-oO/uo/u!"t^2I^3-L->>Yn?i
     3/4U:S:@YENIuo/u!-a-oCURe|! !AYENH+-u"u:Aa:
     1/2L?eCURJ!AYENHCURI"M(c)wYENO/<<ethOuo/u!NOTO^3B(c)o"IYENICURCUR-a-o-aNOT-oA!C

     ^3q+-`,uNOTDEGCURH 1/4o+-x-a-o focus policy YENsDEGu
     !S:click-to-focus!"!A ^3oNOTO Microsoft Windows (c)O+-A:YENI-a-o
     1/4O|!!ACUR]'NNOTO<<u: 1/4D-|b,Ouo/u!<<o:CUR@CURU-a-o,U:!A
     ,Ouo/u!'N.|^3B(c)o"IYENICURCUR-a-o-aNOT-oA!C

     X "ACUR-L-CURa:'(c)CUR@"C,-S(R)i-a-o focus policy!C
     '<<YENy,U:>>!!Awindow manager
     .|+-+-"ithOuo/u!|b|o(R)ENOTOS:@YENICURCUR!C CUR-L-|P-a-o window
     manager |^3CUR-L-|P-a-oCURa:'(c)CURe|!!C |yYEN|I^3-L-CURa:'(c)
     click-to-focus!A |OYENBCURj|h
     1/4AE^3-L-|^3CURa:'(c)|h-oO/CURe|!!C

     YENHCURUNOTOYENO/<<e^3INOTy|ae-a-o focus policy!G

     focus-follows-mouse

             .AE^1<<^2 3/4"`ithOuo/u!'NNOTO"IYENI,Ouo/u!!C
             ,Ouo/u!CUR-L-CUR@(c)w|`i(c)o"a:YENLuo/u!CURW+-!A
             |yYENunS:a.AE^1<<^2
             3/4"`i,Ouo/u!'NYENiYENHS:iAAU:S:@YENICURCUR-a-ouo/u!!A
             |OCUR-L->>Y|bYEN|CURW+-AIA>>!C

     sloppy-focus

             ,O policy NOTODEGw^1i focus-follows-mouse
             -a-oCURpCURp(c)u|u!C ^1i(c)o focus-follows-mouse
             |O"YEN!AYS:a'aa 1/4D-^2
             3/4"`i^3I-a`i-a-ouo/u!((c)I(R)`a+-)!A
             "-o(c)O|^3"a:YENLuo/u!^3-L-.|^3B(c)o<<DS:@YENICURCUR!A|OYENB(c)O|^3Aa:
             1/2L?eCURJCUR].|YEN-c-(R)A:!C YNOTO?iYENI
             sloppy-focus!A<<hYENu|^3|b'aa 1/4D-^2
             3/4"`i.suo/u!(R)E!A
             S:@YENICURCUR-a-ouo/u!CUR~.|AAU:|".s-a-o!A
             |OYENuA-:P:}YENO/<<eS:@YENICURCUR-a-ouo/u!CUR'CUR-L-.|S:iAAU:S:@YENI-aNOT-oA!C

     click-to-focus

             YENN'aa 1/4D-AIA>>CUR~.|"M(c)wS:@YENICURCUR-a-ouo/u!!C
             "AYENB,Ouo/u!.|^3Q !S:raised(YENYAAa)!"
             "`i(c)O|^3"a:YENLuo/u!CURS:<<e!A S:Y"I'aa 1/4D-^2
             3/4"`i"a:YENLuo/u!!A(c)O|^3-a-oAa:
             1/2L?eCURJCUR'.|YENN,Ouo/u!(c)O+-u|NOT!C

     ^3\|h window manager CUR]CURa:'(c)"a:YENL
     policy!A>>P^3o"C,NOTUCURnDEG_"OCURS|^3"C,CUR-L-|P!A ^2O,`^3!CURA
     1/2D-DEGN 3/4\,O window manager -a-oCURaaYENo>>!(c)u!C

     --------------------------------------------------------------

  5.2.4. Widgets

   The X approach of providing tools and not policy extends to the
   widgets seen on screen in each application.

   !S:Widget!" is a term for all the items in the user interface that
   can be clicked or manipulated in some way; buttons, check boxes,
   radio buttons, icons, lists, and so on. Microsoft Windows calls
   these !S:controls!".

   Microsoft Windows and Apple's Mac OS both have a very rigid widget
   policy. Application developers are supposed to ensure that their
   applications share a common look and feel. With X, it was not
   considered sensible to mandate a particular graphical style, or
   set of widgets to adhere to.

   As a result, do not expect X applications to have a common look
   and feel. There are several popular widget sets and variations,
   including the original Athena widget set from MIT, Motif(R) (on
   which the widget set in Microsoft Windows was modeled, all
   bevelled edges and three shades of grey), OpenLook, and others.

   Most newer X applications today will use a modern-looking widget
   set, either Qt, used by KDE, or GTK+, used by the GNOME project.
   In this respect, there is some convergence in look-and-feel of the
   UNIX desktop, which certainly makes things easier for the novice
   user.

     --------------------------------------------------------------

5.3. |w,E X11

   Xorg NOTO FreeBSD ^1w^3]-a-o X11 ^1eS:@!C Xorg NOTOYENN X.Org
   DEGo-a-:.|(c)Ouo|aeCURS:P:}(c)n. 1/2 1/2X^3nAAe X Window
   "t^2I^1eS:@-a-o X server!C Xorg CURDNOTOYENH XFree86 4.4RC2
   YENHCURI X11R6.6 NOTDEGDEGoA|(c)O^2-L-YENI-a-o!C YENO/<<e FreeBSD
   Ports Collection CUR-o-a-o Xorg -a(c)YEN>>NOTDEG 7.5.2!C

   +-q Ports Collection "O|w,E Xorg -a-o|w,ECURe|!!G

 # cd /usr/ports/x11/xorg
 # make install clean

     -a`: Yn 1/2sA:P:S:^1 3/4a-a-o Xorg!A  1/2D-YENy
     1/2T>>{|U:CURO:|^3 4 GB -a-o-oI-oD--aAAP:!!C

   |^1YEN~ X11 CUR]YENi-a 1/2+-u^3z^1L package
   CURe|!"O|w,E!AYENi"IYENI pkg_add(1) "O|w,E 1/2sA:P:|n-a-o X11
   (R)MYENo!ADEGO+-o|b^3z^1L-oo,o|w,E(R)ECUR-L-n<<u:(c)w-a(c)YEN>>S:YYENi!A
   pkg_add(1) .||UDEGES:`i,O(R)MYENo^3I.s-a(c)-a-o(R)MYENo|^"O!C

   Yn|UDEGE^3z^1L package CURe|!"O,E Xorg !A-a
   1/2+-uYEN'CURU+-^3o|aeS:YYENi!G

 # pkg_add -r xorg

     -a`: CURW+--a-o"OCURl.|,ES:^1 3/4a-a-o X11 (R)MYENo!AYEN]NOTA
     server!Bclient!B|r<<NOTuYEN!C |^1YEN~!AAU|^3"a:YENL-a-o X11
     CURl(R)MYENoYENi^3z^1L package (c)I port CURe|!"O^3ae?W|w,E!C

   YEN>>^3^1"a: 3/4l^3!CURA+-NCURP:^2D-|p|o^3](c)w X11!A
   YENHCURI|p|oYEN'^3yDEG-aYENI^2-L-CURO-a-o(R)`a+-Ao^1O!C

     --------------------------------------------------------------

5.4. ^3](c)w X11

   Contributed by Christopher Shumway.

     --------------------------------------------------------------

  5.4.1. |bP:}(c)lCURS:<<e

   |bP:}(c)l^3](c)w X11 CURS:<<e!AnYENyAA,N(c)On,E-a-o 3/4-:
   3/4^1,e(R)AENOTDEG|o!G

     * ?A^1o^3W(R)ae

     * AAaYENU:YENd-a-o'^1CURu^3W(R)ae

     * AAaYENU:YENd-a-oDEGO 3/4D-AAe(R)eP:q

   X11 .|"I?A^1o^3W(R)ae"O"M(c)w,N-aR<< *YENHCURIS:o.sAW^2v!C
   ^3o"C,^3W(R)ae^3q+-`YENi+-q?A^1o(c)O-ath-a-oCURaaYENo(c)I
   1/4tDEGO-oo-,CURW"u+-o!C ^3I<<n-a-oNOTOn-a 3/4^1DCURoYEN!B<<<<-a
   1/2S:o.sAW^2vNOTDEG|o!C

   |OAAaYENU:YENd'^1CURu<<h"M(c)w X11 nYENIthCUR@-oO/AAXDEGEu{|!
   1/4O^2O!C CURj|h
   1/4AE-a-o'^1CURu^3-L-YENiYENH|UDEGEDEG>>'u!A|y^3I|nAUNOTOn-a
   3/4^1DNOTO|o-oO/'^1CURu!A YENHS:K,UCUR@|UDEGEDEG>>'uYEN-c-+-N!C

   Video memory on the graphic adapter determines the resolution and
   color depth which the system can run at. This is important to know
   so the user knows the limitations of the system.

     --------------------------------------------------------------

  5.4.2. ^3](c)w X11

   Xorg |U 7.3
   -a(c)DEG_CUR-L-|A>>YYENo|o^3](c)wAE!AYENunYEN'CURU|CS:YYENi!G

 % startx

   Y^3o<<u:YENOCUR-L-|ae(c)I^1w^3]^3](c)wuL-ak"IYENI!A"-o>>o'N>>YnCURaDEGE^3](c)w
   X11!C ^3](c)w X11
   >>Yn'XO"BAEJ!A-oYENyNOTOYENH"t^2I-oTH^2z-aI+-b,^1"O<<O/YENss-a`i(c)l^3](c)wAE!G

 # Xorg -configure

   ^3o.||b /root YENO/?yCUR-o^2-L-YENI xorg.conf.new ^3](c)wAE(uL 1/2
   *NOTOYENI su(1) (c)I-a 1/2+-uunCURJNOTDEG root!A^3-L-.|S:iAAU:
   root ^1w^3]-a-o $HOME Ao^1OAAU: 1/4AE)!C X11
   u{|!+-uuU.|DEG>>'u"t^2I-a-oAAaYENU:YENdNOTUAo:uwAAe!A"A+-NDEG>>'u"`iuwAAeDEGT(R)S:
   1/4gCURJ^3](c)wAE!A YENH<<K,u:CURJYEN? 1/2T-a-oAAXDEGEu{|!!C

   CURUCUR@"BNOTO'u,O^2{|^3-a-o^3](c)wAE!AYENH<<K 1/2T>>{ Xorg
   YENiYENH>>PAAaYENU:YENd!B?A^1oNOTUAo:uwAAeYEN? 1/2T^1BS:@!G

 # Xorg -config xorg.conf.new

   YNOTY+-o"`iCUR@DEGiP:A|C,S:"Ao/-a-o-oo(R)aeue+-!AYENHCURI X
   S:I-a-o.AE^1<<'aa 1/4D-!A "-o>>o^3](c)wAE'NNOTO|"YEN\-a-o!C
   nDEGhYENX'u,O!AYENun|P(R)E<<o:CURU Ctrl+Alt+Backspace S:YYENi!C

     -a`: Y.AE^1<<CUR-L-YEN?
     1/2T^1BS:@!A"-o>>o>>YnYENy^1i"a:S:@^3](c)w!C  1/2D-DEGN 3/4\
     FreeBSD |w,ECUR@^3^1CURCUR-a-o uU 2.10.10 ,` >>!(c)u!C

   Next, tune the xorg.conf.new configuration file to taste. Open the
   file in a text editor such as emacs(1) or ee(1). First, add the
   frequencies for the target system's monitor. These are usually
   expressed as a horizontal and vertical synchronization rate. These
   values are added to the xorg.conf.new file under the "Monitor"
   section:

 Section "Monitor"
         Identifier   "Monitor0"
         VendorName   "Monitor Vendor"
         ModelName    "Monitor Model"
         HorizSync    30-107
         VertRefresh  48-120
 EndSection

   The HorizSync and VertRefresh keywords may be missing in the
   configuration file. If they are, they need to be added, with the
   correct horizontal synchronization rate placed after the HorizSync
   keyword and the vertical synchronization rate after the
   VertRefresh keyword. In the example above the target monitor's
   rates were entered.

   X allows DPMS (Energy Star) features to be used with capable
   monitors. The xset(1) program controls the time-outs and can force
   standby, suspend, or off modes. If you wish to enable DPMS
   features for your monitor, you must add the following line to the
   monitor section:

         Option       "DPMS"

   While the xorg.conf.new configuration file is still open in an
   editor, select the default resolution and color depth desired.
   This is defined in the "Screen" section:

 Section "Screen"
         Identifier "Screen0"
         Device     "Card0"
         Monitor    "Monitor0"
         DefaultDepth 24
         SubSection "Display"
                 Viewport  0 0
                 Depth     24
                 Modes     "1024x768"
         EndSubSection
 EndSection

   The DefaultDepth keyword describes the color depth to run at by
   default. This can be overridden with the -depth command line
   switch to Xorg(1). The Modes keyword describes the resolution to
   run at for the given color depth. Note that only VESA standard
   modes are supported as defined by the target system's graphics
   hardware. In the example above, the default color depth is
   twenty-four bits per pixel. At this color depth, the accepted
   resolution is 1024 by 768 pixels.

   Finally, write the configuration file and test it using the test
   mode given above.

     -a`: One of the tools available to assist you during
     troubleshooting process are the X11 log files, which contain
     information on each device that the X11 server attaches to. Xorg
     log file names are in the format of /var/log/Xorg.0.log. The
     exact name of the log can vary from Xorg.0.log to Xorg.8.log and
     so forth.

   If all is well, the configuration file needs to be installed in a
   common location where Xorg(1) can find it. This is typically
   /etc/X11/xorg.conf or /usr/local/etc/X11/xorg.conf.

 # cp xorg.conf.new /etc/X11/xorg.conf

   The X11 configuration process is now complete. Xorg
   YENO/<<eYENi^3z^1L startx(1) "O+-ODEGECURS:!C The X11 server may
   also be started with the use of xdm(1).

     -a`: There is also a graphical configuration tool, xorgcfg(1),
     which comes with the X11 distribution. It allows you to
     interactively define your configuration by choosing the
     appropriate drivers and settings. This program can be invoked
     from the console, by typing the command xorgcfg -textmode. For
     more details, refer to the xorgcfg(1) manual pages.

     Alternatively, there is also a tool called xorgconfig(1). This
     program is a console utility that is less user friendly, but it
     may work in situations where the other tools do not.

     --------------------------------------------------------------

  5.4.3. P:iP:YEN^3](c)w+-MA:ae

    5.4.3.1. ^3](c)w Intel(R) i810 A,^1I'^1CURu^2O

   Configuration with Intel i810 integrated chipsets requires the
   agpgart AGP programming interface for X11 to drive the card. ,O+-!
   1/2D-DEGN 3/4\ agp(4) >>!(c)u!C

   This will allow configuration of the hardware as any other
   graphics board. Note on systems without the agp(4) driver compiled
   in the kernel, trying to load the module with kldload(8) will not
   work. This driver has to be in the kernel at boot time through
   being compiled in or using /boot/loader.conf.

     --------------------------------------------------------------

    5.4.3.2. NOTDEG 1/4e?A^1oYEN'^3yS:ouI 3/4AAo^1O

   YEN>>,`DEG^2^3]|U|`iCURw,g|^3"C,.LP:iP:YEN^3](c)w-a-oYEN\CURO!C
   |p-aG,OuU"IYENICURWz^3](c)wCURu"a.||^3DEGYAD-a-o,U:!A
   1/2D-|hS:QYENINOTUAo: log AE
   (.|DEGO?yNOTUAo:DEGT(R)S:)YENH<<KS:a:YENX,N-ak!C
   S:a:'M,N-ak^1Lu{CURCUR!AYENi-`a.|>>YnYENI"`iCURaa|r 1/2s?e
   3/4^1S:@NOTDEG>>^2S:U!C

   YENO/<<e-a-o 1/4e?A^1o (WSXGA, WSXGA+, WUXGA, WXGA, WXGA+ uYEN)
   ^3-L-|^3CURa:'(c) 16:10 CURI 10:9
   CURn"O!AYENHCURICUR@"C,YENi-`a|^3DEGYAD-a-oCURn"O!C
   YENHCURUNOTOCUR@"C,+-`"-L--a-o 16:10 ?A^1o,N-aR<< *!G

     * 2560x1600

     * 1920x1200

     * 1680x1050

     * 1440x900

     * 1280x800

   NOTYCURe+-|O"YEN!An 1/4WYEN[^3o"C,,N-aR<<
   *^3](c)wCUR]NOTONOTU.i(R)e(c)o:-a-o!A YENun|b Section "Screen"
   CUR-o-a-o Mode YEN[CURWYENh'N|n!ACURn|p!G

 Section "Screen"
 Identifier "Screen0"
 Device     "Card0"
 Monitor    "Monitor0"
 DefaultDepth 24
 SubSection "Display"
         Viewport  0 0
         Depth     24
         Modes     "1680x1050"
 EndSubSection
 EndSection

   Xorg YENiYENH^3z^1L I2C/DDC "O+-o-a 3/4,O
   1/4e?A^1o(c)OCURa:'(c)-a-o,N-aR<< *uYENNOTUAo:,eDEGT!A
   |]|^1'N-`aYEN?
   1/2TDEG>>'uYENX,O?A^1o(c)O-`aCURa:'(c)-a-oAW^2v!B,N-aR<< *!C

   YAAXDEGEu{|!"AYEN 1/4YEN]NOTA ModeLine DEGT(R)S:-a-o,U:!A
   "-o>>o'NnNOTDEG Xorg DEGu"C,^3](c)wCUR~|ae!C S:UIYENiYENH^3z^1L
   /var/log/Xorg.0.log AE"O"u+-o ModeLine
   NOTUAo:^3](c)w,e(R)AE!AS:YYENiAAy?A^1oYEN?+-`AAaYENU:!C
   A^3,OYENiYENHNOTY"`iAth|u:CURU+--a-oDEGT(R)S:!G

 (II) MGA(0): Supported additional Video Mode:
 (II) MGA(0): clock: 146.2 MHz   Image Size:  433 x 271 mm
 (II) MGA(0): h_active: 1680  h_sync: 1784  h_sync_end 1960 h_blank_end 2240 h_border: 0
 (II) MGA(0): v_active: 1050  v_sync: 1053  v_sync_end 1059 v_blanking: 1089 v_border: 0
 (II) MGA(0): Ranges: V min: 48  V max: 85 Hz, H min: 30  H max: 94 kHz, PixClock max 170 MHz

   ^3o"C,DEGT(R)S:^3Q-oUNOTDEG EDID DEGT(R)S:!C
   YENiYENHAC,YENN^3o"C,,e(R)AE!A .fDEGtCURU|C-a-oYEN?
   1/2TP:P:S:C,"O^2-L-YENI ModeLine ^3](c)w!G

  ModeLine <name> <clock> <4 horiz. timings> <4 vert. timings>

   (c)OYENH^3oO(R) *"O Section "Monitor" -a-o ModeLine
   'N.|NOTO^1^3CURU+-^3o 1/4E!G

 Section "Monitor"
 Identifier      "Monitor1"
 VendorName      "Bigname"
 ModelName       "BestModel"
 ModeLine        "1680x1050" 146.2 1680 1784 1960 2240 1050 1053 1059 1089
 Option          "DPMS"
 EndSection

   ^3o 1/4ECURl'NA^2^3aeS:^1|"CURF!AX
   uo/u!'NYENiYENHYEN'^3yNOTDEG.s-a-o 1/4e?A^1oAo^1OAAo!C

     --------------------------------------------------------------

5.5. |b X11 CURCUR"IYENI|r<<NOT

   Contributed by Murray Stokely.

  5.5.1. Type1 ^3W(R)ae-a-o|r<<NOT

   The default fonts that ship with X11 are less than ideal for
   typical desktop publishing applications. Large presentation fonts
   show up jagged and unprofessional looking, and small fonts in
   Netscape are almost completely unintelligible. However, there are
   several free, high quality Type1 (PostScript(R)) fonts available
   which can be readily used with X11. For instance, the URW font
   collection (x11-fonts/urwfonts) includes high quality versions of
   standard type1 fonts (Times Roman(R), Helvetica(R), Palatino(R)
   and others). The Freefonts collection (x11-fonts/freefonts)
   includes many more fonts, but most of them are intended for use in
   graphics software such as the Gimp, and are not complete enough to
   serve as screen fonts. In addition, X11 can be configured to use
   TrueType fonts with a minimum of effort. For more details on this,
   see the X(7) manual page or the section on TrueType fonts.

   To install the above Type1 font collections from the ports
   collection, run the following commands:

 # cd /usr/ports/x11-fonts/urwfonts
 # make install clean

   And likewise with the freefont or other collections. To have the X
   server detect these fonts, add an appropriate line to the X server
   configuration file (/etc/X11/xorg.conf), which reads:

 FontPath "/usr/local/lib/X11/fonts/URW/"

   Alternatively, at the command line in the X session run:

 % xset fp+ /usr/local/lib/X11/fonts/URW
 % xset fp rehash

   This will work but will be lost when the X session is closed,
   unless it is added to the startup file (~/.xinitrc for a normal
   startx session, or ~/.xsession when logging in through a graphical
   login manager like XDM). A third way is to use the new
   /usr/local/etc/fonts/local.conf file: see the section on
   anti-aliasing.

     --------------------------------------------------------------

  5.5.2. TrueType(R) ^3W(R)ae-a-o|r<<NOT

   Xorg has built in support for rendering TrueType fonts. There are
   two different modules that can enable this functionality. The
   freetype module is used in this example because it is more
   consistent with the other font rendering back-ends. To enable the
   freetype module just add the following line to the "Module"
   section of the /etc/X11/xorg.conf file.

 Load  "freetype"

   Now make a directory for the TrueType fonts (for example,
   /usr/local/lib/X11/fonts/TrueType) and copy all of the TrueType
   fonts into this directory. Keep in mind that TrueType fonts cannot
   be directly taken from a Macintosh(R); they must be in
   UNIX/MS-DOS/Windows format for use by X11. Once the files have
   been copied into this directory, use ttmkfdir to create a
   fonts.dir file, so that the X font renderer knows that these new
   files have been installed. ttmkfdir is available from the FreeBSD
   Ports Collection as x11-fonts/ttmkfdir.

 # cd /usr/local/lib/X11/fonts/TrueType
 # ttmkfdir -o fonts.dir

   Now add the TrueType directory to the font path. This is just the
   same as described above for Type1 fonts, that is, use

 % xset fp+ /usr/local/lib/X11/fonts/TrueType
 % xset fp rehash

   or add a FontPath line to the xorg.conf file.

   That's it. Now Netscape, Gimp, StarOffice(TM), and all of the
   other X applications should now recognize the installed TrueType
   fonts. Extremely small fonts (as with text in a high resolution
   display on a web page) and extremely large fonts (within
   StarOffice) will look much better now.

     --------------------------------------------------------------

  5.5.3. Anti-Aliased ^3W(R)ae-a-o|r<<NOT

   Updated by Joe Marcus Clarke.

   Anti-aliasing has been available in X11 since XFree86 4.0.2.
   However, font configuration was cumbersome before the introduction
   of XFree86 4.3.0. Beginning with XFree86 4.3.0, all fonts in X11
   that are found in /usr/local/lib/X11/fonts/ and ~/.fonts/ are
   automatically made available for anti-aliasing to Xft-aware
   applications. Not all applications are Xft-aware, but many have
   received Xft support. Examples of Xft-aware applications include
   Qt 2.3 and higher (the toolkit for the KDE desktop), GTK+ 2.0 and
   higher (the toolkit for the GNOME desktop), and Mozilla 1.2 and
   higher.

   In order to control which fonts are anti-aliased, or to configure
   anti-aliasing properties, create (or edit, if it already exists)
   the file /usr/local/etc/fonts/local.conf. Several advanced
   features of the Xft font system can be tuned using this file; this
   section describes only some simple possibilities. For more
   details, please see fonts-conf(5).

   This file must be in XML format. Pay careful attention to case,
   and make sure all tags are properly closed. The file begins with
   the usual XML header followed by a DOCTYPE definition, and then
   the <fontconfig> tag:

       <?xml version="1.0"?>
       <!DOCTYPE fontconfig SYSTEM "fonts.dtd">
       <fontconfig>
    

   As previously stated, all fonts in /usr/local/lib/X11/fonts/ as
   well as ~/.fonts/ are already made available to Xft-aware
   applications. If you wish to add another directory outside of
   these two directory trees, add a line similar to the following to
   /usr/local/etc/fonts/local.conf:

 <dir>/path/to/my/fonts</dir>

   After adding new fonts, and especially new font directories, you
   should run the following command to rebuild the font caches:

 # fc-cache -f

   Anti-aliasing makes borders slightly fuzzy, which makes very small
   text more readable and removes !S:staircases!" from large text,
   but can cause eyestrain if applied to normal text. To exclude font
   sizes smaller than 14 point from anti-aliasing, include these
   lines:

         <match target="font">
             <test name="size" compare="less">
                 <double>14</double>
             </test>
             <edit name="antialias" mode="assign">
                 <bool>false</bool>
             </edit>
         </match>
         <match target="font">
             <test name="pixelsize" compare="less" qual="any">
                 <double>14</double>
             </test>
             <edit mode="assign" name="antialias">
                 <bool>false</bool>
             </edit>
         </match>

   Spacing for some monospaced fonts may also be inappropriate with
   anti-aliasing. This seems to be an issue with KDE, in particular.
   One possible fix for this is to force the spacing for such fonts
   to be 100. Add the following lines:

        <match target="pattern" name="family">
            <test qual="any" name="family">
                <string>fixed</string>
            </test>
            <edit name="family" mode="assign">
                <string>mono</string>
            </edit>
         </match>
         <match target="pattern" name="family">
             <test qual="any" name="family">
                 <string>console</string>
             </test>
             <edit name="family" mode="assign">
                 <string>mono</string>
             </edit>
         </match>

   (this aliases the other common names for fixed fonts as "mono"),
   and then add:

          <match target="pattern" name="family">
              <test qual="any" name="family">
                  <string>mono</string>
              </test>
              <edit name="spacing" mode="assign">
                  <int>100</int>
              </edit>
          </match>     

   Certain fonts, such as Helvetica, may have a problem when
   anti-aliased. Usually this manifests itself as a font that seems
   cut in half vertically. At worst, it may cause applications such
   as Mozilla to crash. To avoid this, consider adding the following
   to local.conf:

          <match target="pattern" name="family">
              <test qual="any" name="family">
                  <string>Helvetica</string>
              </test>
              <edit name="family" mode="assign">
                  <string>sans-serif</string>
              </edit>
          </match>       

   Once you have finished editing local.conf make sure you end the
   file with the </fontconfig> tag. Not doing this will cause your
   changes to be ignored.

   The default font set that comes with X11 is not very desirable
   when it comes to anti-aliasing. A much better set of default fonts
   can be found in the x11-fonts/bitstream-vera port. This port will
   install a /usr/local/etc/fonts/local.conf file if one does not
   exist already. If the file does exist, the port will create a
   /usr/local/etc/fonts/local.conf-vera file. Merge the contents of
   this file into /usr/local/etc/fonts/local.conf, and the Bitstream
   fonts will automatically replace the default X11 Serif, Sans
   Serif, and Monospaced fonts.

   Finally, users can add their own settings via their personal
   .fonts.conf files. To do this, each user should simply create a
   ~/.fonts.conf. This file must also be in XML format.

   One last point: with an LCD screen, sub-pixel sampling may be
   desired. This basically treats the (horizontally separated) red,
   green and blue components separately to improve the horizontal
   resolution; the results can be dramatic. To enable this, add the
   line somewhere in the local.conf file:

          <match target="font">
              <test qual="all" name="rgba">
                  <const>unknown</const>
              </test>
              <edit name="rgba" mode="assign">
                  <const>rgb</const>
              </edit>
          </match>
       

     -a`: Depending on the sort of display, rgb may need to be
     changed to bgr, vrgb or vbgr: experiment and see which works
     best.

   Anti-aliasing should be enabled the next time the X server is
   started. However, programs must know how to take advantage of it.
   At present, the Qt toolkit does, so the entire KDE environment can
   use anti-aliased fonts. GTK+ and GNOME can also be made to use
   anti-aliasing via the !S:Font!" capplet (see uU 5.7.1.3 ,` for
   details). By default, Mozilla 1.2 and greater will automatically
   use anti-aliasing. To disable this, rebuild Mozilla with the
   -DWITHOUT_XFT flag.

     --------------------------------------------------------------

5.6. The X Display Manager

   Contributed by Seth Kingsley.

  5.6.1. Overview

   The X Display Manager (XDM) is an optional part of the X Window
   System that is used for login session management. This is useful
   for several types of situations, including minimal !S:X
   Terminals!", desktops, and large network display servers. Since
   the X Window System is network and protocol independent, there are
   a wide variety of possible configurations for running X clients
   and servers on different machines connected by a network. XDM
   provides a graphical interface for choosing which display server
   to connect to, and entering authorization information such as a
   login and password combination.

   Think of XDM as providing the same functionality to the user as
   the getty(8) utility (see uU 24.3.2 ,` for details). That is, it
   performs system logins to the display being connected to and then
   runs a session manager on behalf of the user (usually an X window
   manager). XDM then waits for this program to exit, signaling that
   the user is done and should be logged out of the display. At this
   point, XDM can display the login and display chooser screens for
   the next user to login.

     --------------------------------------------------------------

  5.6.2. Using XDM

   The XDM daemon program is located in /usr/local/bin/xdm. This
   program can be run at any time as root and it will start managing
   the X display on the local machine. If XDM is to be run every time
   the machine boots up, a convenient way to do this is by adding an
   entry to /etc/ttys. For more information about the format and
   usage of this file, see uU 24.3.2.1 ,`. There is a line in the
   default /etc/ttys file for running the XDM daemon on a virtual
   terminal:

 ttyv8   "/usr/local/bin/xdm -nodaemon"  xterm   off secure

   By default this entry is disabled; in order to enable it change
   field 5 from off to on and restart init(8) using the directions in
   uU 24.3.2.2 ,`. The first field, the name of the terminal this
   program will manage, is ttyv8. This means that XDM will start
   running on the 9th virtual terminal.

     --------------------------------------------------------------

  5.6.3. Configuring XDM

   The XDM configuration directory is located in
   /usr/local/lib/X11/xdm. In this directory there are several files
   used to change the behavior and appearance of XDM. Typically these
   files will be found:

      File                          Description                       
   Xaccess    Client authorization ruleset.                           
   Xresources Default X resource values.                              
   Xservers   List of remote and local displays to manage.            
   Xsession   Default session script for logins.                      
   Xsetup_*   Script to launch applications before the login          
              interface.                                              
   xdm-config Global configuration for all displays running on this   
              machine.                                                
   xdm-errors Errors generated by the server program.                 
   xdm-pid    The process ID of the currently running XDM.            

   Also in this directory are a few scripts and programs used to set
   up the desktop when XDM is running. The purpose of each of these
   files will be briefly described. The exact syntax and usage of all
   of these files is described in xdm(1).

   The default configuration is a simple rectangular login window
   with the hostname of the machine displayed at the top in a large
   font and !S:Login:!" and !S:Password:!" prompts below. This is a
   good starting point for changing the look and feel of XDM screens.

     --------------------------------------------------------------

    5.6.3.1. Xaccess

   The protocol for connecting to XDM-controlled displays is called
   the X Display Manager Connection Protocol (XDMCP). This file is a
   ruleset for controlling XDMCP connections from remote machines. It
   is ignored unless the xdm-config is changed to listen for remote
   connections. By default, it does not allow any clients to connect.

     --------------------------------------------------------------

    5.6.3.2. Xresources

   This is an application-defaults file for the display chooser and
   login screens. In it, the appearance of the login program can be
   modified. The format is identical to the app-defaults file
   described in the X11 documentation.

     --------------------------------------------------------------

    5.6.3.3. Xservers

   This is a list of the remote displays the chooser should provide
   as choices.

     --------------------------------------------------------------

    5.6.3.4. Xsession

   This is the default session script for XDM to run after a user has
   logged in. Normally each user will have a customized session
   script in ~/.xsession that overrides this script.

     --------------------------------------------------------------

    5.6.3.5. Xsetup_*

   These will be run automatically before displaying the chooser or
   login interfaces. There is a script for each display being used,
   named Xsetup_ followed by the local display number (for instance
   Xsetup_0). Typically these scripts will run one or two programs in
   the background such as xconsole.

     --------------------------------------------------------------

    5.6.3.6. xdm-config

   This contains settings in the form of app-defaults that are
   applicable to every display that this installation manages.

     --------------------------------------------------------------

    5.6.3.7. xdm-errors

   This contains the output of the X servers that XDM is trying to
   run. If a display that XDM is trying to start hangs for some
   reason, this is a good place to look for error messages. These
   messages are also written to the user's ~/.xsession-errors file on
   a per-session basis.

     --------------------------------------------------------------

  5.6.4. Running a Network Display Server

   In order for other clients to connect to the display server, you
   must edit the access control rules, and enable the connection
   listener. By default these are set to conservative values. To make
   XDM listen for connections, first comment out a line in the
   xdm-config file:

 ! SECURITY: do not listen for XDMCP or Chooser requests
 ! Comment out this line if you want to manage X terminals with xdm
 DisplayManager.requestPort:     0

   and then restart XDM. Remember that comments in app-defaults files
   begin with a !S:!!" character, not the usual !S:#!". More strict
   access controls may be desired !X!X look at the example entries in
   Xaccess, and refer to the xdm(1) manual page for further
   infomation.

     --------------------------------------------------------------

  5.6.5. Replacements for XDM

   Several replacements for the default XDM program exist. One of
   them, kdm (bundled with KDE) is described later in this chapter.
   The kdm display manager offers many visual improvements and
   cosmetic frills, as well as the functionality to allow users to
   choose their window manager of choice at login time.

     --------------------------------------------------------------

5.7. (R)`a+-Ao^1O

   Contributed by Valentino Vaschetto.

   YEN>>^3^1.|CURP:^2D-|b FreeBSD CURCUR-a-o X
   ,IAY!A|^3th"C,CUR-L-|P-a-o(R)`a+-Ao^1O!C !S:(R)`a+-Ao^1O!"
   1/2d^3o<<U: 1/4s!A+-qA^2^3ae-a-o window manager "`i S:^1
   3/4a-a-o(R)`a+-A^3YENIu{|!!A"O|p KDE (c)I GNOME!C

     --------------------------------------------------------------

  5.7.1. GNOME

    5.7.1.1. Ao:(c)o GNOME

   GNOME is a user-friendly desktop environment that enables users to
   easily use and configure their computers. GNOME includes a panel
   (for starting applications and displaying status), a desktop
   (where data and applications can be placed), a set of standard
   desktop tools and applications, and a set of conventions that make
   it easy for applications to cooperate and be consistent with each
   other. Users of other operating systems or environments should
   feel right at home using the powerful graphics-driven environment
   that GNOME provides. More information regarding GNOME on FreeBSD
   can be found on the FreeBSD GNOME Project's web site. The web site
   also contains fairly comprehensive FAQs about installing,
   configuring, and managing GNOME.

     --------------------------------------------------------------

    5.7.1.2. Installing GNOME

   YENi^3z^1L package (c)I Ports Collection -a-oCURe|!"O>>'AP|w,E!G

   ^3z^1L-oo,oS:QYENI package |w,E GNOME!G

 # pkg_add -r gnome2

   +-q ports tree ^3z^1L`i(c)l 1/2X 1/2sA:P:|w,E GNOME!G

 # cd /usr/ports/x11/gnome2
 # make install clean

   .i GNOME |w,ES:^1|"<<a!A YEN^2P:.S:iP:D X server +-ODEGE GNOME
   |O<<D`iYEN>>-a-o window manager!C

   +-ODEGE GNOME ^3IA^2^3ae-a-oCURe-akNOTOS:Q YENI GDM(GNOME Display
   Manager)!C GDM, which is installed as a part of the GNOME desktop
   (but is disabled by default), can be enabled by adding
   gdm_enable="YES" to /etc/rc.conf. Once you have rebooted, GNOME
   will start automatically once you log in !X!X no further
   configuration is necessary.

   GNOME may also be started from the command-line by properly
   configuring a file named .xinitrc. If a custom .xinitrc is already
   in place, simply replace the line that starts the current window
   manager with one that starts /usr/local/bin/gnome-session instead.
   If nothing special has been done to the configuration file, then
   it is enough simply to type:

 % echo "/usr/local/bin/gnome-session" > ~/.xinitrc

   Next, type startx, and the GNOME desktop environment will be
   started.

     -a`: If an older display manager, like XDM, is being used, this
     will not work. Instead, create an executable .xsession file with
     the same command in it. To do this, edit the file and replace
     the existing window manager command with
     /usr/local/bin/gnome-session:

 % echo "#!/bin/sh" > ~/.xsession
 % echo "/usr/local/bin/gnome-session" >> ~/.xsession
 % chmod +x ~/.xsession

   Yet another option is to configure the display manager to allow
   choosing the window manager at login time; the section on KDE
   details explains how to do this for kdm, the display manager of
   KDE.

     --------------------------------------------------------------

    5.7.1.3. Anti-aliased Fonts with GNOME

   X11 supports anti-aliasing via its !S:RENDER!" extension. GTK+ 2.0
   and greater (the toolkit used by GNOME) can make use of this
   functionality. Configuring anti-aliasing is described in uU 5.5.3
   ,`. So, with up-to-date software, anti-aliasing is possible within
   the GNOME desktop. Just go to Applications->Desktop
   Preferences->Font, and select either Best shapes, Best contrast,
   or Subpixel smoothing (LCDs). For a GTK+ application that is not
   part of the GNOME desktop, set the environment variable
   GDK_USE_XFT to 1 before launching the program.

     --------------------------------------------------------------

  5.7.2. KDE

     --------------------------------------------------------------

    5.7.2.1. About KDE

   KDE is an easy to use contemporary desktop environment. Some of
   the things that KDE brings to the user are:

     * A beautiful contemporary desktop

     * A desktop exhibiting complete network transparency

     * An integrated help system allowing for convenient, consistent
       access to help on the use of the KDE desktop and its
       applications

     * Consistent look and feel of all KDE applications

     * Standardized menu and toolbars, keybindings, color-schemes,
       etc.

     * Internationalization: KDE is available in more than 40
       languages

     * Centralized, consistent, dialog-driven desktop configuration

     * A great number of useful KDE applications

   KDE comes with a web browser called Konqueror, which is a solid
   competitor to other existing web browsers on UNIX systems. More
   information on KDE can be found on the KDE website. For FreeBSD
   specific information and resources on KDE, consult the KDE on
   FreeBSD team's website.

     --------------------------------------------------------------

    5.7.2.2. |w,E KDE

   |p|P GNOME (c)I"a:YENL(R)`a+--oTH^2z^3nAAeCUR@ 1/4E!A
   CUR]YENiYENH>>'AP^3z^1L package (c)I Ports Collection "O|w,E!G

   To install the KDE package from the network, simply type:

 # pkg_add -r kde

   pkg_add(1) will automatically fetch the latest version of the
   application.

   To build KDE from source, use the ports tree:

 # cd /usr/ports/x11/kde3
 # make install clean

   After KDE has been installed, the X server must be told to launch
   this application instead of the default window manager. This is
   accomplished by editing the .xinitrc file:

 % echo "exec startkde" > ~/.xinitrc

   Now, whenever the X Window System is invoked with startx, KDE will
   be the desktop.

   If a display manager such as XDM is being used, the configuration
   is slightly different. Edit the .xsession file instead.
   Instructions for kdm are described later in this chapter.

     --------------------------------------------------------------

  5.7.3. More Details on KDE

   Now that KDE is installed on the system, most things can be
   discovered through the help pages, or just by pointing and
   clicking at various menus. Windows or Mac(R) users will feel quite
   at home.

   The best reference for KDE is the on-line documentation. KDE comes
   with its own web browser, Konqueror, dozens of useful
   applications, and extensive documentation. The remainder of this
   section discusses the technical items that are difficult to learn
   by random exploration.

     --------------------------------------------------------------

    5.7.3.1. The KDE Display Manager

   An administrator of a multi-user system may wish to have a
   graphical login screen to welcome users. XDM can be used, as
   described earlier. However, KDE includes an alternative, kdm,
   which is designed to look more attractive and include more
   login-time options. In particular, users can easily choose (via a
   menu) which desktop environment (KDE, GNOME, or something else) to
   run after logging on.

   To enable kdm, the ttyv8 entry in /etc/ttys has to be adapted. The
   line should look as follows:

 ttyv8 "/usr/local/bin/kdm -nodaemon" xterm on secure

     --------------------------------------------------------------

  5.7.4. XFce

    5.7.4.1. About XFce

   XFce is a desktop environment based on the GTK+ toolkit used by
   GNOME, but is much more lightweight and meant for those who want a
   simple, efficient desktop which is nevertheless easy to use and
   configure. Visually, it looks very much like CDE, found on
   commercial UNIX systems. Some of XFce's features are:

     * A simple, easy-to-handle desktop

     * Fully configurable via mouse, with drag and drop, etc.

     * Main panel similar to CDE, with menus, applets and
       applications launchers

     * Integrated window manager, file manager, sound manager, GNOME
       compliance module, and more

     * Themeable (since it uses GTK+)

     * Fast, light and efficient: ideal for older/slower machines or
       machines with memory limitations

   More information on XFce can be found on the XFce website.

     --------------------------------------------------------------

    5.7.4.2. Installing XFce

   A binary package for XFce exists (at the time of writing). To
   install, simply type:

 # pkg_add -r xfce4

   Alternatively, to build from source, use the ports collection:

 # cd /usr/ports/x11-wm/xfce4
 # make install clean

   Now, tell the X server to launch XFce the next time X is started.
   Simply type this:

 % echo "/usr/local/bin/startxfce4" > ~/.xinitrc

   The next time X is started, XFce will be the desktop. As before,
   if a display manager like XDM is being used, create an .xsession,
   as described in the section on GNOME, but with the
   /usr/local/bin/startxfce4 command; or, configure the display
   manager to allow choosing a desktop at login time, as explained in
   the section on kdm.

                         II. CUR@-e(c)ECURuS:@

   NOTJuMDEGoA|-a-o^3!CURACURw,g'-L-^1LCURF!A+-uCURU"O-a-o^3oO^3!CURA+-N.|DEGQ
   1/2 *CUR@"C,+-`.|YENI"`i-a-o FreeBSD
   -a-o-S|a!A^3o"C,^3^1,`YEN]NOTA!G

     * CURP:^2D-u^1+-z+-`"-L-YENB^1eYENI-a-o(R)`a+-A^3YENI^3nAAe!G-ooP:AsA:y
       3/4^1!BYENI^2-L-CUROCURu"a!BCURaaYENoAEuo/u{|!uYEN!C

     * CURP:^2D-u^1+-z^2^3|h FreeBSD CURWYENiYENI-a-o|h'CAAeCURu"a!C

     * ,NA:A|p|o 1/2sA:P:|Uq FreeBSD (R)O:CURssYENH
       1/4WYEN[ABYEN~"t^2IYEN\-`a-a-oNOTyu{!C

     * ,O^2O'yz|C|L"t^2I!AYEN]S:t(R)`aCURW<<NOT|L-ai
       3/4-:CURI-oo,o|L-ai 3/4-:-a-o^3](c)w!C

     * (R)iYENU:u^1+-zNOTY|p|o|b+-z-a-o FreeBSD "t^2ICURCURDEGo|ae
       Linux A^3YENI^3nAAe!C

   ^3o"C,^3^1,`CURCUR|^3"C,>>Yn+-z^1wYENy
   3/4\AA-a"C,NOTUAo:CURaaYENo!A|b|U^3^1,`P:}AY-a-o.S:nCUR-o.|'-L-CURI!C

   CUR-o(R)eYENO/?y

   6. (R)`a+-Ao^1OA^3YENIu{|!

   7. |h'CAAe 1/4vu(R)T 1/4O:(Multimedia)

   8. ^3](c)w FreeBSD Kernel

   9. |C|L

   10. >>P Linux Binary -a-oNOTU(R)eCURe+-

     --------------------------------------------------------------

                    ^3^1 6. (R)`a+-Ao^1OA^3YENIu{|!

   Contributed by Christophe Juniet.

6.1. .S:z

   |b FreeBSD
   CURW+-YENiYENHDEGo|ae<<D+-`|h-oO/Ath-a-o(R)`a+-A^3YENIu{|!!A
   ^1^3NOTO-ooP:AsA:y 3/4^1(c)MCURaa|r^3B^2z^3nAAeuYEN!C
   ^3o"C,u{|!CURj^3-L-YENiYENH^3z^1L(R)MYENo"O|w,E(c)INOTO+-q Ports
   Collection CURCUR|UDEGE 1/2sA:P:|w,E!C
   ^3\|h.s-a-o"IYENI-aI.|S:AE+-ae-`a|b|bYENLI-a-o(R)`a+-"t^2ICURCURS:a:"`i^3o"C,u{|!!C
   ^3o^3^1+-N.|S:iP:DS:A|p|oCUR-L-YENIP:OCURO|hYEN\CUROYENh|w,ECUR@"C,
   1/4o:-au-a-o(R)`a+-A^3YENIu{|!!A
   CUR-L--oTHNOTO+-q(R)MYENo(c)INOTO+-q Ports Collection CURCUR|w,E!C

   >>Yn-a`.N"`i-a-oNOTO!G.i+-q ports CURCUR|w,Eu{|!-a-o(R)EO!A
   YEN|INOTO+-q`i(c)l 1/2XP:}(c)l 1/2sA:P:-a-o!C"I.OS:A 1/2sA:P:-a-o
   ports (c)M^1q,-L-^3t<< *(uwAAeuYEN-AA)!A
   |^3YENi-`a.|-aa<<U:-ao/CUR@NOTq(R)EP:!CUR~-`aS:^1|"!C
   |p-aG+-q`i(c)l 1/2X 1/2sA:P:^1iS:A"O>>!.|-aaCURO|h(R)EP:!-a-o,U:!A
   CURj^3!CURA-a-o ports S:A^3-L--`aS:a:"`i"AEYENy
   1/2sA:P:|n-a-o(R)MYENo"O|w,E!C

   |]NOTDEG FreeBSD "a|^3NOTU(R)e Linux CURGP:i"i-a-o-S(c)E!A
   ^3\|h`iYENy|b Linux CURWP:}uo-a-oA^3YENIu{|!^3-L--`a|bS:A-a-o
   FreeBSD (R)`a+-Ao^1ODEGo|ae!C |b|w,EYENo|o Linux
   A^3YENIu{|!CURS:<<e!A+-j-P<<O/A:^3S:AYENy 3/4\AA-a uU 10 ^3^1
   Linux DEGo|aeNOTU(R)e 1/4O|!^3oO^3^1,`!C |O^3\|hYENI Linux
   CURGP:i"iNOTU(R)e 1/4O|!-a-o^3nAAe|b ports ,IAY^3q+-`^3-L-.|YENI
   !S:linux-!" P:}AY!C
   .iS:A|b.j'MNOTYO-S(c)w^3nAAe(R)E!ADEGO|i^3oAI!A"AYENBYENiYENH"IYENI
   whereis(1) "OS:a:!C |bCURU|C-a-o>>!(c)uCURCUR!A
   ^3-L-DEG^2^3]S:A|b|w,EYENo|o Linux A^3YENI^3nAAeCURS:<<e!A
   CURw,g"AEYENy+-OYENICURF Linux CURGP:i"iNOTU(R)e 1/4O|!!C

   CURU|CYENO/?yNOTO^3o^3^1CURCUR(c)O^2[>>\-a-oA^3YENIu{|!!G

     * AsA:y 3/4^1 (^1^3NOTO Mozilla, Opera, Firefox, Konqueror)

     * ?`iCUR 1/2^3nAAe (^1^3NOTO KOffice, AbiWord, The GIMP,
       OpenOffice.org)

     * CURaaYENoAsA:y^3nAAe (^1^3NOTO Acrobat Reader(R), gv, Xpdf,
       GQview)

     * DEG]DEGE^3B^2z^3nAAe (^1^3NOTO GnuCash, Gnumeric, Abacus)

   |b 3/4\AA-a^3o^3^1CURS:<<e!AS:AYEN^2P:.

     * -a 3/4^1D|p|o|w,E"a:YENL-a-o^3nAAe(third-party software) (uU 4
       ^3^1).

     * -a 3/4^1D|p|o|w,E Linux ^3nAAe (uU 10 ^3^1).

   n-a 3/4^1DS:o|hAo:(c)o|h'CAAeAo^1O-a-o,eDEGT!A 1/2D-YENy 3/4\AA-a
   uU 7 ^3^1 |h'CAAe^3^1,`!C
   |p-aGS:A.Qn^3](c)w(c)M"IYENI^1qCURlP:lYENo!ACUR] 1/2D-S:AYENyNOTY
   uU 26 ^3^1P:lYENo^3^1,`!C

     --------------------------------------------------------------

6.2. AsA:y 3/4^1

   |b FreeBSD CURCUR"A"S|^3^1wYENy|w,E|n-a-o-S(c)wAsA:y 3/4^1!C |y|b
   Ports Collection CURS:CURCUR<<o|^3^3\|hAsA:y
   3/4^1YENi"NS:A|w,E"IYENI!C |p-aGS:A"S|^3"NOTDEG-:(R)EP:!YENh
   1/2sA:P:(c)O|^3-a-o-aF|e
   (|bNOTY"C,+-!-apCURU^3oYENi-`a.|-aaCURW<<U:-ao/-a-oCUR@NOTq(R)EP:!)!A
   ^3o"C,^3-L-|^3^2{|"-a-o(R)MYENoYENi"N-a 1/2+-u|w,E!C

   KDE (c)M GNOME (R)`a+-Ao^1O^3-L-CURw'-L-"N HTML AsA:y 3/4^1!C 
   1/2D-DEGN|O uU 5.7 ,` "OCURF,NS:o|h|^3Ao:|p|o^3](c)w^3o"C,S:^1
   3/4a-a-o(R)`a+-Ao^1O"t^2I,eDEGT!C

   |p-aGS:A|b'MS:a:>>'P:qCURAE-a-oAsA:y 3/4^1!AS:AYENiYENH+-q Ports
   Collection CURCURS:a:"`iCURU+--a-o'X-oO/!G www/dillo, www/links,
   (c)I www/w3m!C

   ^3o,`CURP:^2D-^3o"C,AsA:y 3/4^1!G

     AsA:y    (c)O>>Y-a-o"t^2I,e.  +-q ports   YENDnNOTU"I-a-o^3nAAe   
   3/4^1|W-oU         1/2         |w,E(R)EP:! 
   Mozilla    |h                  -ao/        Gtk+                     
                                              FreeBSD (c)M Linux       
                                              -a-o-a(c)YEN>>^3-L-|^3!C 
   Opera      CURO:               uu          Linux -a-o-a(c)YEN>>>>Yn 
                                              Linux CURGP:i"iNOTU(R)e  
                                              1/4O^2OYENHCURI          
                                              linux-openmotif.         
   Firefox    CURCUR<< *          -ao/        Gtk+                     
   Konqueror  CURCUR<< *          -ao/        KDE "c,|!(R)w            

     --------------------------------------------------------------

  6.2.1. Mozilla

   Mozilla NOTONOTU.i^2{YENNCURAE!BA(c)wYENBS:^1YENth^2 3/4'O|U:
   FreeBSD "t^2ICURW!C YEN|CUR]"a^3AE|^3CURQCURA^2AA|X HTML 
   1/4D-.C,-a-oAAaYENU:CURTHA-o!A
   YEN|S:o'-L-"NCURFP:lYENoCURI.s>>D,s^2O-a-o 3/4\AA-aYEN\-`a!C
   |^1YEN~|p-aGS:AYEN'-oan|UCURv
   1/4gCUR@"C,-ooP:-a-o,U:!AYEN|AU'-L-"NCURF HTML -a-o 1/2s?e 3/4^1!C
   |p-aGNOTO Netscape -a-o"IYENI-aI!A S:AYENi-`a.|>>{YENX^3o,o
   Communicator <<U:^1^3!A YEN|I"a:^1e|P
   1/4ENOTO"IYENINOTU|PDEGoA|-a-oAsA:y 3/4^1!C

   |b^3t<< *,u-oC!A^1^3NOTO CPU ^3t<< *CURO:(c)o 233MHz
   (c)INOTOCURp(c)o 64MB DEGO 3/4D-AAe-a-o 3/4-: 3/4^1CURW+-!A
   S:^1YENth"IYENI Mozilla .|NOTOYENo.YEN<< *-OP:O,e. 1/2-a-o"AE!C
   (c)OYENH|b^3o 1/4E-a-o 3/4-: 3/4^1CURW+-!AS:AYENi-`a.|.Qn"IYENI
   Opera ^3o 1/4E>>'P:q-AA-a-oAsA:y
   3/4^1!A|O+-uCURU"O<<a+-.|'-L-"`i!C

   |p-aGS:A|^3CURDEG>>o`i|]CUR-L--`a(c)INOTOCUR-L-.Q 1/2sA:P: Mozilla
   -a-o,U:!AFreeBSD GNOME
   ^1IP:CURCURw,gNOTDEGS:ADEGu|nCURF^3oYENo"AE!C
   YENunYENICURU+--a-o<<u:YENO^3z^1L-oo,o|w,E(R)MYENo'N|aeCURF!G

 # pkg_add -r mozilla

   |p-aG"S|^3S:a:"`i(R)MYENoYENiYENH"IYENI!A|OS:ACUR]|^3"NOTDEG-:-a-o(R)EP:!(c)M-oI-oD--aAAP:!"O
   1/2sA:P: Mozilla "A|w,E"`iS:A-a-o"t^2ICURCUR!A
   S:AYENiYENH^3z^1LCURU|C"BAEJ"O|w,E!G

 # cd /usr/ports/www/mozilla
 # make install clean

   Mozilla >>Yn"IYENI root -a-oAAv"ODEGo|ae chrome uuYENU"O
   1/2T<<OYEN? 1/2T-a-o-a`i(c)lCURAE!C
   YENtYEN~!A|p-aGS:A>>YnS:`iCUR@"C,ABYEN~-a-oYEN~+- 3/4u{|!^1^3NOTO
   mouse gestures!A S:A'NYEN^2P:.n"IYENI root -a-oAAv"O|w,E!A YENH
   3/4A.i-a-o|w,E^3o"C,YEN~+- 3/4u{|!!C

   CUR@YEN^1S:AS:^1|"CURF Mozilla -a-o|w,E!AS:A'N|ACUR]CUR-L->>Yn
   root -a-oAAvCURF!C !@S:AYENiYENH-a
   1/2+-uYEN'CURU+--a-o<<u:YENO"O+-ODEGE Mozilla!G

 % mozilla

   CUR]YENiYENH-a 1/2+-uYEN'CURU|C<<u:YENO!A-a
   1/2+-u+-ODEGEP:lYENo(c)M.s>>D 3/4\AA-a 3/4^1!G

 % mozilla -mail

     --------------------------------------------------------------

  6.2.2. Firefox

   Firefox NOTOYENH Mozilla `i(c)l
   1/2XNOTDEGDEGoA|-a-o.sYEN@YENNAsA:y 3/4^1!C Mozilla
   NOTOCUR@DEGiA^3YENI^3nAAe-a-o 3/4a|X(R)M,E!A ^1^3NOTOAsA:y
   3/4^1!BP:lYENou{|!!B^2aCURN<<C,^3nAAeuYEN(c)O^2O|"!C Firefox
   <<h-A-oeNOTOAsA:y 3/4^1!A
   ^3oCUR]NOTONOTDEG|oYEN|-`auuCURp-oe(R)<<CURS:NOTG!C

   YENiYENHYEN'CURU|C<<u:YENO"O|w,E!G

 #pkg_add -r firefox

   CUR]YENiYENH^3z^1L Ports Collection!AYENH 1/2sA:P:`i(c)l
   1/2X-a-oCURe|!"O|w,E!G

 #cd /usr/ports/www/firefox
 # make install clean

     --------------------------------------------------------------

  6.2.3. Firefox, Mozilla -a-o Java(TM) plugin u{|!

     -a`: YEN>>,`YENHCURICURUCUR@,`!AS:!DEG^2^3]+-zCURw,E|n Firefox
     (c)I Mozilla!C

   FreeBSD DEGo-a-:.|>>P Sun Microsystems |^3^1F|"+-AAAv"oA:^3!A
   YENiYENH'^2 1/4 1/2 Java Runtime Environment(JRE(TM)) CURI Java
   Developement Kit(JDK(TM)) -a-o FreeBSD -a(c) binary(DEGo|aeAE)!C
   FreeBSD -a(c)-a-o binary YENiYENH|b FreeBSD DEGo-a-:.|
   -oo-,CURU,u:!C

   nAAy Firefox (c)I Mozilla CURa:'(c) Java(TM)
   -a-o,U:!A-oYENynYENy,E java/javavmwrapper ^3oO port!C uM<<a|AYENh
   http://www.freebsdfoundation.org/downloads/java.shtml CURU,u:
   Diablo JRE!A"AYENH pkg_add(1) <<u:YENO"O|w,ECURS:!C

   +-uuU+-ODEGEAsA:y 3/4^1!A|b-ooS:}|C?eCURJ about:plugins uM<<a<<o:
   Enter Aa:!A'N.|AAaYENU:YENO/<<eCURw,E-a-o plugins ^2M^3ae!A
   ^3o(R)EA^3,O'NYENiYENHNOTY"`i Java CUR]|^3|CYENX"O!C YCUR'YEN
   1/4NOTY"`i-a-o,U:!A"-o'NCURA'<<NOTDEG root +-b,^1!A
   YEN'CURU|C<<u:YENO!G

 # ln -s /usr/local/diablo-jre1.5.0/plugin/i386/ns7/libjavaplugin_oji.so \
   /usr/local/lib/browser_plugins/

   ^3I<<a!A<<+-OAsA:y 3/4^1S:YYENi!C

     --------------------------------------------------------------

  6.2.4. Firefox, Mozilla -a-o Macromedia(R) Flash(TM) plugin u{|!

   Macromedia(R) Flash(TM) plugin u{|!"A"S|^3 FreeBSD -a(c)!A
   uM|OYENiYENH^3z^1L^3nAAe 1/4h(wrapper)"ODEGo|ae Linux -a(c)-a-o
   plugin u{|!!C ^3oO wrapper |P(R)ECUR]CURa:'(c) Adobe(R) Acrobat(R)
   YENHCURI RealPlayer(R) plugin uYEN!C

   +-uCURU"OYENh,E www/linuxpluginwrapper!C linuxpluginwrapper
   >>YnYENy,ECUR@O<<U:CURj-a-o emulators/linux_baseport!C uM<<a(R)U
   3/4U port (c)O<<u:YENU:-a-oS:@-ak!A YENhYEN? 1/2T|a^3](c)wS:A-a-o
   /etc/libmap.conf!I ^3](c)w-a-o 1/2d"OAE(R) *|`i(c)o
   /usr/local/share/examples/linuxpluginwrapper/
   -a-oYENO/?y(c)^3CURU!C

   CURUCUR@"B!A<<hNOTO,E www/linux-flashplugin7!C
   ,E|n<<a!A|A+-ODEGEAsA:y 3/4^1!A|b-ooS:}|C?eCURJ about:plugins!A
   uM<<a<<o: Enter Aa:'N.|AAaYENU:YENO/<<eCURw,E-a-o plugin ^2M^3ae!C

   Y Flash plugin
   "SYENX^2{-a-o,U:!ACURj|hYENi-`aNOTO|]NOTDEG-o|CURFDEGu symlink
   ^3su^2CURS:NOTG!C  1/2D-CURANOTDEG root
   +-b,^1!AYEN'CURU|C<<u:YENO!G

 # ln -s /usr/local/lib/npapi/linux-flashplugin/libflashplayer.so \
   /usr/local/lib/browser_plugins/
 # ln -s /usr/local/lib/npapi/linux-flashplugin/flashplayer.xpt \
   /usr/local/lib/browser_plugins/

   ^3I<<a!A<<+-OAsA:y 3/4^1A^3,O'NYENiNOTY"`iCURF!C

     -a`: linuxpluginwrapper YENu-`a|b i386
     -a-o"t^2INOT[-ocCURU^1B|ae!C

     --------------------------------------------------------------

  6.2.5. Opera

   Opera NOTOO"a^3AES:^1 3/4aYEN\-`a!B^2AA|X 1/4D-.C,-a-oAsA:y
   3/4^1!C YEN||P(R)ECUR]"a^3AECURFCUR-o<<O/-a-oP:lYENo!B.s>>D
   3/4\AA-a 3/4^1!BIRC!BRSS/Atom feeds  3/4\AA-a 3/4^1uYEN!C |^1YEN~
   Opera S:oNOTOO>>'P:q-AA!B DEGo|ae^3t<< *CURSS:O:-a-oAsA:y 3/4^1!C
   YEN||b ports CURCUR|^3"a-oO/-a(c)YEN>>!G!u`iYENI!v-a-o FreeBSD
   -a(c)YEN>>AU|^3|b Linux  1/4OAA 1/4O|!CURU-a-o-a(c)YEN>>!C

   nYENI Opera -a-o FreeBSD -a(c)YEN>>"OAsA:y-ooP:-a-o,U:!A
   YENICURU+--a-o<<u:YENO|w,E!G

 # pkg_add -r opera

   |^3"C, FTP -,YENx"A"S|^3YENth^3!-a-o(R)MYENo!A
   |yNOTOYEN'CURU+--a-o<<u:YENO'N-`a+-q Ports Collection CURCUR|w,E!G

 # cd /usr/ports/www/opera
 # make install clean

   n|w,E Opera -a-o Linux -a(c)YEN>>-a-o,U:!A 
   1/2D-+-NCURW+-"OCURlCURCUR-a-o opera 'A'<<|" linux-opera!C
   |^3"C,(R)EO!A Linux -a-o-a(c)YEN>>NOTOCURQCURA|^3YENI-a-o!A
   ^1^3NOTOYENu|^3 Linux -a(c)YEN>>YEN~+- 3/4u{|!-a-o(R)EO!C
   |y|b"a:YENLCURe+-"O>>!!A FreeBSD (c)M Linux
   -a-o-a(c)YEN>>YEN\-`aCURWNOTOCUR@ 1/4E-a-o!C

     --------------------------------------------------------------

  6.2.6. Konqueror

   Konqueror NOTO KDE
   (R)`a+-"t^2I-a-oCUR@^3!CURA!A|yNOTOYEN|CUR]YENiYENHAC,YENN|w,E
   x11/kdebase3 |b KDE Ao^1OYENHYEN~"IYENI!C Konqueror
   CUR-L-YENuNOTOO-ooP:AsA:y 3/4^1!A YENL|P(R)ECUR]NOTOAE(R) *-oTH^2z
   3/4^1(c)M|h'CAAeAsA:y 3/4^1!C

   Konqueror CUR]|^3^3\|h-a-oYEN~+- 3/4u{|!!A ^3o"C,YEN~+-
   3/4u{|!YENiYENH+-q misc/konq-plugins CURCUR|w,E!C

   Konqueror CUR]CURa:'(c) Flash -a-oYEN~+- 3/4u{|!!C
   |p|o|w,E-a-o>>!(c)u 1/2D-DEGN
   3/4\!Ghttp://freebsd.kde.org/howto.php!C

     --------------------------------------------------------------

6.3. ?`iCUR 1/2<<C,^3nAAe

   .iP:}(c)lP:i|ae?`iCUR 1/2!A
   .s-a-o"IYENI-aI^3q+-`.|YENhS:a:|nYENI-a-o?`iCUR
   1/2<<C,^3nAAe(c)INOTO|nCURWCURa-a-oCURaa|r^3B^2z 3/4^1!C YENO/<<e
   |^3"C,(R)`a+-Ao^1O ^1^3NOTO KDECURw,g'-L-"NCURF?`iCUR
   1/2^3nAAe^2O|X-a-o(R)MYENo!C FreeBSD
   '-L-"NCURF(c)O>>Y-a-o(c)O|^3?`iCUR
   1/2^3nAAe!A(R)`a+-Ao^1OCUR]CUR-L-"OYEN~!C

   ^3o,`^2[>>\CURFCURU|C-a-o^3o"C,^3nAAe!G

    ^3nAAe|W-oU   (c)O>>Y"t^2I,e.    +-q Ports    YENDnNOTU"I(R)MYENo 
                        1/2       |w,E-a-o(R)EP:! 
   KOffice        CURO:           -ao/            KDE                 
   AbiWord        CURO:           uu              Gtk+ (c)INOTO GNOME 
   The Gimp       CURO:           -ao/            Gtk+                
   OpenOffice.org |h              <<U:CUR[        JDK 1.4, Mozilla    

     --------------------------------------------------------------

  6.3.1. KOffice

   KDE -aA,s|bYEN|-a-o(R)`a+-Ao^1O,IAY'-L-"NCURFCUR@OYENiYENH|b KDE
   YEN~"IYENI-a-o?`iCUR 1/2^3nAAe^2O|X!C YEN|YEN]S:tCURFYEN|-oO/
   1/4O^2O!G KWord NOTOCURaa|r^3B^2z 3/4^1!A KSpread
   NOTO,O-oa-aiu{|!!A KPresenter NOTOA^2^3o/ 1/4 1/2(c)nu{|!!A
   YENtYEN~ Karbon14
   AAyS:AYENiYENH^2-L-YENI^1IS:ICURAE-a-oCURaaYENo!C [5]

   |b|w,E^3I.s-a(c)-a-o KOffice CURS:<<e!A  1/2D-YENy
   1/2T(c)wS:A|^3^3I.s-a(c)YEN>>-a-o KDE!C

   YnYENI(R)MYENo"O|w,E KOffice!A  1/2D-"I.OCURU+--a-o<<u:YENO!G

 # pkg_add -r koffice

   |p-aG(R)MYENoCUR-L-|s|b-a-o,U:!AS:AYENiYENH"IYENI ports
   collection. "O|pn|w,E KDE3 CURCUR-a-o KOffice!A
   1/2D-"IYENICURU|C<<u:YENO|w,E!G

 # cd /usr/ports/editors/koffice-kde3
 # make install clean

     --------------------------------------------------------------

  6.3.2. AbiWord

   AbiWord
   NOTOCUR@OS:KP:O-a-oCURaa|r^3B^2z^3nAAe!AYEN~AE[(c)M.PA:+-^3-L--an|u:(c)o
   Microsoft Word!C YEN|
   3/4A|X^3B^2zCURaaYENo!B<<HYENo!B^3o/S:i!B^3AES:N?yuYENuYEN!C
   YEN|CUR]<<D+-`S:O:^3t!AYEN]S:tCURF^3\|hYEN\-`a|OYENB<<D+-`(R)e(c)o:CURWCURa!C

   AbiWord YENiYENH?eCURJ(c)I?eYENX^3\|hAE(R) *(R)ae|!!A
   YEN]NOTACUR@"C,|^3+-MS:Q-a-o(R)ae|!!A"O|p.L^3n(Microsoft)CUR
   1/2YENq-a-o .doc (R)ae|!!C

   AbiWord CUR]-`aYENI(R)MYENo|w,E!A
   S:AYENiYENHYENICURU|C<<u:YENO"O|w,E!G

 # pkg_add -r abiword

   |p-aGS:a:CUR-L-"`i(R)MYENo-a-o,U:!AYEN|CUR]YENiYENH+-q Ports
   Collection CURCUR 1/2sA:P:|w,E!C |O Ports Collection
   A^3,On<<O<<u|b^3I.s-a-o-aNOT-oA!C AbiWord
   YENiYENH^3z^1LCURU|CCURe|! 1/2sA:P:|w,E!G

 # cd /usr/ports/editors/abiword
 # make install clean

     --------------------------------------------------------------

  6.3.3. The GIMP

   ^1i(c)o 1/4v^1^3-a-o 1/2s?eCURI *S:i"O>>!!AGIMP NOTO<<D+-`-oe
   1/2o-a-o 1/4v^1^3^3B^2z^3nAAe!C
   YEN|YENiYENH.iS:@A^2^3ae-a-oA,^1I^3nAAe(c)INOTODEG-a<<~
   1/2e-a-oNOTUCURu^3B^2z^3nAAe!C YEN|CURa:'(c)NOTDEG
   1/4AE^2^3|h-a-oYEN~+- 3/4u{|!CURI<<u:YENO 1/2Z (script-fu)
   CURP:+-!C GIMP YENiYENHAA-a 1/4g^3\|hAE(R) *(R)ae|!!C
   YEN|CUR]CURa:'(c)+- 1/2'y 3/4^1 [6] (c)MCURa 1/4g-aO!C

   A:P:uu!GGIMP |bYENO/<<eNOTO 2.x -a(c)!A|p-aGS:A.Qn|w,E 1.x
   -a(c)-a-o,U:!A 1/2D-YENI Ports Collection CURCUR-a-o
   graphics/gimp1!C YENtYEN~|p-aGS:ACURw,g"IYENI^2ss-oD Adobe
   Photoshop!A|OYENBCUR-L-^2ss-oD GIMP
   CURP:+--a-o,U:!AS:ACUR]YENiYENH^1A,O|w,E graphics/gimpshop!A
   YEN|-a-o"IYENICURP:+-CURQCURAAth|u: Adobe Photoshop!C

   S:AYENiYENH"IYENICURU+-<<u:YENO|w,E(R)MYENo!G

 # pkg_add -r gimp

   |p-aG-a-oS:A-a-o FTP -,YENx"S|^3^3oO(R)MYENo!AS:AYENiYENH"IYENI
   Ports Collection!C |b Ports Collection -a-o graphics
   YENO/?yCURUCUR]YEN]S:tCURF The Gimp Manual(GIMP "IYENICURaYENU)!C
   CURU+-YENU: 1/2d|p|o|w,E^3o"C,u{|!!G

 # cd /usr/ports/graphics/gimp
 # make install clean
 # cd /usr/ports/graphics/gimp-manual-pdf
 # make install clean

   A:P:uu!GYENtYEN~|b Ports Collection CURCURCUR]|^3CUR@"C,YEN~+-
   3/4u{|!YENiYENH"IYENI!A "O|p>>!YENiYENH^3B^2z 1/4AE|`iNOTU 3/4-:
   raw AE(R) *(R)ae|!-a-o gimp-ufraw!C

     -a`: GIMP "IYENICURaYENUCUR]|^3 HTML (R)ae|!-a-o!AS:AYENiYENH|b
     graphics/gimp-manual-html CURCUR|w,E!C

     --------------------------------------------------------------

  6.3.4. OpenOffice.org

   OpenOffice.org YEN]S:tCURF(c)O|^3S:^1 3/4a-a-o?`iCUR
   1/2^3nAAe^2O|X!G CURaa|r^3B^2z
   3/4^1!B,O-oa-ai!BA^2^3o/^3nAAeAU|^3A,^1I^3nAAe!C
   DEG-L-CURFYEN|-a-o"IYENI-aICURP:+-<<D+-`Ath|u:"a:YENL-a-o?`iCUR
   1/2^3nAAe!A YENLAU-`aDEG-:?eCURJ(c)M?eYENX^3\|h 1/4o:-au-a-oAE(R)
   *(R)ae|!!C
   YEN|CUR]YEN]S:tCURFCUR-L-|P>>y"YEN-a-o"IYENI-aICURP:+-!B<<-:|rAENOTd(c)M|r"aa!C

   OpenOffice.org -a-oCURaa|r^3B^2z 3/4^1"IYENI XML AE(R) *(R)ae|!"O
   1/4WYEN[^2 3/4'O(c)ECURI 1/4u(c)E!C
   ,O-oa-aiu{|!CURa:'(c)YEN"P:DEG(macro)YEN\-`a|OYENB-`aDEG-:"IYENIYEN~"O-a-o,e(R)AE(R)wCURP:+-!C
   OpenOffice.org CURw,gCURQCURAA(c)w!A "AYENB-`aDEG-:|b Windows,
   Solaris(TM), Linux, FreeBSD CURI Mac OS X
   uYENS:@.~"t^2ICURW+-DEGo|ae!C .Q-a 3/4^1DS:o|hAo:(c)o
   OpenOffice.org -a-o,eDEGTYENiYENH|b OpenOffice.org -ooP:
   CURWNOTd,ss!CS:ACUR]YENiYENH|b FreeBSD OpenOffice.org ^2
   3/4'O^1IP:CUR -a-o-ooP:CURWNOTd,ssAo:(c)o FreeBSD CURW OpenOffice
   -S(c)w-a-o,eDEGT(c)I-a 1/2+-uCURU,u:CURw 1/2sA:P:|n-a-o(R)MYENo

   n|w,E OpenOffice.org!A  1/2D-YENIYENHCURUCURe|!"ODEGo|ae!G

 # pkg_add -r openoffice.org

     -a`: .iS:A|b"IYENI FreeBSD -RELEASE
     -a(c)YEN>>-a-o(R)EO!ACURW+--a-oS:@-akA^3,O|ae+-o^3q!C
     nNOTO"a:YENL-a-o-a(c)YEN>>!AS:AA^3,ONOTYCUR@CURU FreeBSD
     OpenOffice.org ^2 3/4'O^1IP:CUR-a-o-oo-,!A"AYENBYENI pkg_add(1)
     |w,E|X 3/4A-a-o(R)MYENo!C
     |b^3oO-,YENx^3-L-YENiYENHCURU,u:"`iA(c)w-a-oA:AYENX-a(c)(release)(c)IP:}uoCURCUR-a-o-a(c)YEN>>!C

   .iCURw,g|w,ES:^1CURS:<<a!AS:AYENunAa:CURJCURU+--a-o<<u:YENO'N-`aDEGo|ae
   OpenOffice.org!G

 % openoffice.org

   A:P:uu!G-oYNOTYS:A-a-o-a(c)YEN>>!A|^3(R)EO>>Yn?eCURJ|p
   openoffice.org-2.0.1
   CURS:Ath-a-o<<u:YENO!ACUR-L-^1LS:ACUR]YENiYENHYENI shell
   CURCUR-a-o alias (c)INOTOYENI symbolic link "O^3B^2z!C

     -a`: |b^2A:CUR@|,+-ODEGE-a-o(R)EO!AOpenOffice
     .|DEGY"`iCUR@"C,DEGYAD!C
     |OYENB|bS:A-a-o(R)aYENO/?y(c)^3CURU.||UDEGE<<O/YENss
     .openoffice.org2 -a-o,e(R)AES:"!C

   |p-aGuL-ak"u+-o OpenOffice.org -a-o(R)MYENo!AS:ACUR'uMYENiYENH?i
   3/4U:+-q port  1/2sA:P:!C CUR-L-^1LS:AYEN^2P:.AODEGO|bCURss!G
   1/2sA:P:-a-o^1Lu{.|>>YnCURjP:q-a-o-oI-oD--aAAP:!YENBNOTU.i-O(R)E!C

 # cd /usr/ports/editors/openoffice.org-2
 # make install clean

     -a`:
     |p-aGS:A.Qn|w,EYEN>>|aCURAE-a-o-a(c)YEN>>!AS:a<<e+--a-o<<u:YENOYENN'<<|"CURU+--a-o!G

 # make LOCALIZED_LANG=S:A-a-o>>y"YEN install clean

     S:AYEN^2P:.S:aS:A-a-o>>y"YEN '<<|"YEN? 1/2T-a-o>>y"YEN ISO-code
     [7] (c)OCURa:'(c)-a-o>>y"YENYENN 1/2X^2M^3aeYENiYENH|b port
     YENO/?y,I-a-o files/Makefile.localized AE(R) *CURCURS:a:"`i!C

   CUR@YEN^1S:^1|"CURFCURWz"BAEJ!A OpenOffice.org
   YENiYENIYENHCURU<<u:YENO+-ODEGE!G

 % openoffice.org

     --------------------------------------------------------------

6.4. CURaaYENo 3/4\A:y 3/4^1

   -an|~"O|^3"C,CURaaYENo(R)ae|!AAU:+-o.U"O.UNOTy|ae!A
   DEGoYEN>>-a-o"t^2ICURCURCUR]^3\CUR-L-.||^3^3o"C,(R)ae|!(c)O>>Y-a-o
   1/4D-.C, 3/4\A:y 3/4^1!C
   |b^3oCUR@,`!AS:UI"ONOTYNOTY<<c,>>o|w,E^3o"C,^3nAAe!C

   ^3o+-i^2[>>\CURFCURU|C-a-o^3nAAe

    ^3nAAe|W-oU   (c)O>>Y"t^2I,e.  +-q Ports    YENDnNOTU"I(R)MYENo   
                        1/2       |w,E(R)EP:! 
   Acrobat Reader CURO:           uu          Linux CURGP:i"iNOTU(R)e 
                                              1/4O^2O                 
   gv             CURO:           uu          Xaw3d                   
   Xpdf           CURO:           uu          FreeType                
   GQview         CURO:           uu          Gtk+ (c)INOTO GNOME     

     --------------------------------------------------------------

  6.4.1. Acrobat Reader(R)

   ^3\|hCURaaYENo|b'^2S:G-a-o(R)EO^3-L-NOTOYENI PDF -a-oAE(R)
   *(R)ae|!!A ^3oO(R)ae|!NOTODEGo(c)o
   !S:YENiA:a|!CURaaYENo(R)ae|!(Portable Document Format)!"!C
   "a:CURCURCUR@O+-AAE-a-o 3/4\A:y^3nAAe'NNOTOAcrobat Reader!A
   YEN|NOTOYENN Adobe CUR 1/2YENquo|aeu^1 Linux
   "IYENI-a-o-a(c)YEN>>!C |]NOTDEG FreeBSD CUR]YENiYENHDEGo|ae Linux
   CURGP:i|`iAE(R) *!A (c)OYENHYEN|CUR]-`a|b FreeBSD CURW+-DEGo|ae!C

   n+-q Ports Collection CURCUR|w,E Acrobat Reader 7 YENun!G

 # cd /usr/ports/print/acroread7
 # make install clean

   |]NOTDEG+-AAAv-a-o"i!A(c)OYENHCUR-L-'-L-"N
   1/2sA:P:|n-a-o(R)MYENo!C

     --------------------------------------------------------------

  6.4.2. gv

   gvNOTO PostScript (c)M PDF -a-o 3/4\A:y 3/4^1!C YEN|<<O/-oc(c)o
   ghostview-a-oDEGoA|CURW!A CUR-L-^1L|]NOTDEG"IYENI Xaw3d
   "c,|!(R)w!A (c)OYENHYEN~AE[NOTYDEG_"OCURn,u-o}<<G!C gv ^3t<<
   *S:O:!ACURP:+-A^2 1/4a:"AYENB|^3^3\|hYEN\-`a!A
   CURn|p>>!CURe|V(c)E!B-E+-iCURjCURp!BAY(c)nCURn"O!B(c)MCURI?-:
   3/4|(antialias)uYEN!C
   |OYENB'XYENG(c)O|^3-a-o"IYENI^3-L-YENiYENH+-qAa:
   1/2L(c)I.AE^1<<"OS:^1|"!C

   YENI(R)MYENo"O|w,E gv!A"IYENICURU|C<<u:YENO!G

 # pkg_add -r gv

   |p-aGS:ACUR-L--`a"u+-o(R)MYENo!AS:AYENiYENH"IYENI Ports
   Collection!G

 # cd /usr/ports/print/gv
 # make install clean

     --------------------------------------------------------------

  6.4.3. Xpdf

   |p-aGS:A.QnCUR@OCURp<<NOT-a-o FreeBSD PDF  3/4\A:y^3nAAe!A
   XpdfNOTOO>>'P:q-AA|OYENB|^3(R)A:^2v-a-o 3/4\A:y 3/4^1!C
   YEN|YENu>>Yn<<D+-`CURO:-a-o,e. 1/2|OYENBCURQCURAA(c)w!C
   YEN|YENu"IYENI 1/4D-.C,-a-o X |r<<NOT|OCUR-L->>Yn Motif
   (c)INOTO"a:YENL-a-o X CURu"a^2O(toolkit)!C

   YENI(R)MYENo"O|w,E Xpdf!A"IYENICURU|C<<u:YENO!G

 # pkg_add -r xpdf

   |p-aG(R)MYENoCUR-L-|s|b(c)INOTOS:ADEG 3/4|n"IYENI Ports
   Collection!A "IYENIYENHCURU<<u:YENO!G

 # cd /usr/ports/graphics/xpdf
 # make install clean

   CUR@YEN^1S:^1|"CURF|w,E!AS:AYENiYENH+-ODEGE Xpdf
   "AYENB"IYENI.AE^1<<YENkAa:YENh"IYENI?i^3ae!C

     --------------------------------------------------------------

  6.4.4. GQview

   GQview NOTO 1/4v^1^3-oTH^2z^3nAAe!C S:AYENiYENHYENI^3aeAa:"O
   3/4\A:yAE(R) *!B+-ODEGEABYEN~-a-o 1/2s?e
   3/4^1!BAY^1I^1wA:yuYENYEN\-`a!C YEN|CUR]|^3CURU?OCURu 1/4
   1/2(c)n(slideshow)CURICUR@"C,DEGoYEN>>-a-oAE(R) *
   3/4THS:@YEN\-`a!C S:AYENiYENI GQview -oTH^2z
   1/4v^1^3P:DEG"A-`a>>'AP|aS:a:YENX<< 1/2AE-a-oAE(R) *!C GQview
   -`aDEG-:"IYENIYENth?A^1oAE[NOTY"ACURa:'(c)DEGe>>UCURAE!C

   |p-aGS:A.Qn|w,E GQview-a-o(R)MYENo!A  1/2D-"IYENICURU|C<<u:YENO!G

 # pkg_add -r gqview

   |p-aG(R)MYENouL-ak"u+-o!A(c)INOTOS:ACURn,u^3ssAAw"IYENI Ports
   Collection!AYENun!G

 # cd /usr/ports/graphics/gqview
 # make install clean

     --------------------------------------------------------------

6.5. DEG]DEGE

   |p-aG|^3YENo|o^2zYENNS:A.Qn|bS:A-a-o FreeBSD
   (R)`a+-Ao^1OCURW-oTH^2zS:A-a-oOCURHDEG]DEGE!A
   ^3o,I|^3CUR@"C,YEN\-`a+-jCURj!B"IYENIA^2^3ae-a-oA^3YENIu{|!YENi"N|w,E!C
   ^3o"C,DEG]DEGE-oTH^2z^3nAAeCURS:CURCUR|^3"C,NOTONOTU(R)e(c)oNOTy|ae-a-o
   Quicken(R) (c)I Excel CURaaYENo!C

   ^3o,`^2[>>\CURFCURU+-^3o"C,^3nAAe!G

   ^3nAAe|W-oU (c)O>>Y"t^2I,e.    +-q Ports    YENDn-a-oNOTU"I(R)MYENo 
                     1/2       |w,E-a-o(R)EP:! 
   GnuCash     CURO:           -ao/            GNOME                   
   Gnumeric    CURO:           -ao/            GNOME                   
   Abacus      CURO:           uu              Tcl/Tk                  

     --------------------------------------------------------------

  6.5.1. GnuCash

   GnuCash NOTO GNOME ^1IP:CURS:VCURO|"-aGCURCUR-a-oCUR@^3!CURA!A |O
   GNOME YENDnNOTO'-L-"N^2 *-oY"IYENI-aI(end-users)
   ?ECURA|O+-jCURj-a-o(R)`a+-A^3YENIu{|!!C "IYENI GnuCash!A
   S:AYENiYENH<<uA:oNOTo:?yS:A-a-o|NOTCURJCURI-aaP:O!BS:A-a-o>>E|ae+-bCURa!B(c)INOTOS:A-a-o-aN^2
   1/4AO"euYEN!C YEN|-a-o-S(c)ENOTOCURP:+--a
   1/2A:+-|yYEN\-`aCUR'<<D+-`+-M.~!C

   GnuCash '-L-"NCURFCUR@O' 1/4 1/4z-a-ouuYENU 3/4^1!B +-bCURa
   1/4h-AA"t^2I!B^3\|hS:O:^3tAa:CURI|UDEGES:^1|"(auto-completion)
   1/4O|!!C YEN|CUR]-`aCURAP:}^3aeCUR@-a-o^3o/-ai|U:
   1/4AEO,O^2O-a-o^3!YEN-:!C GnuCash CUR]-`aDEG-:?eCURJCURI|X"O:
   Quicken QIF AE(R) *!C
   YEN|CUR]-`a^3B^2zCURj^3!CURADEGe>>U-a-oCURe'ACURI^3qYENI^3f^1oCURS:(R)ae|!!C

   n|w,E GnuCash "`iS:A-a-o"t^2ICURCUR!A YENunDEGuCURU|C"BAEJ!G

 # pkg_add -r gnucash

   |p-aGCUR-L--`a"u+-o(R)MYENo!AS:AYENiYENH"IYENI Ports Collection:

 # cd /usr/ports/finance/gnucash
 # make install clean

     --------------------------------------------------------------

  6.5.2. Gnumeric

   Gnumeric NOTO GNOME (R)`a+-Ao^1OCURCUR-a-o,O-oa-ai!C
   YEN|-a-o-SAINOTO-`aDEG-:(R)U 3/4UAx|s(R)ae(R)ae|!(cell
   format)CURI|UDEGE,E>>o-a-o"t^2I!A
   "OCURe<<K|UDEGE|a!u^2qYENX!v"IYENI-aI-a-o?eCURJ!C
   YEN|CUR]-`aDEG-:?eCURJ^3\|h 1/4o:-au-a-oAE(R) *(R)ae|!!A^1^3NOTO
   Excel, Lotus 1-2-3, (c)INOTO Quattro Pro!C Gnumeric
   CURa:'(c)"IYENI math/guppi A,^1I^3nAAe"OA,^1I!C
   YEN||^3^3\|hCUR-o<<O/-a-o"c,
   1/4AE|OYENBCUR^1^3\CUR@-e-a-oAx|s(R)ae(R)ae|!!A^1^3NOTO: 
   1/4AE|r!B^3f^1o!BCURe'A!B(R)EP:!CURI"a:YENL(R)ae|!uYEN!C

   nYENI(R)MYENo|w,E Gnumeric!AYENunYEN'YENHCURU<<u:YENO!G

 # pkg_add -r gnumeric

   |p-aG(R)MYENoCUR-L-|s|b!AS:AYENiYENHDEGuCURU+--a-o"BAEJ"O"IYENI
   Ports Collection  1/2sA:P:|w,E!G

 # cd /usr/ports/math/gnumeric
 # make install clean

     --------------------------------------------------------------

  6.5.3. Abacus

   Abacus NOTOOCURpYEN(c)CURS"IYENIA^2^3ae-a-o,O-oa-ai!C
   YEN|YEN]S:tCURF^3\|hCUR-o<<O/-a-o"c,
   1/4AE!A|bNOTUAo:-a-o>>aDEG`i|p^2Ip 3/4C,!BDEG]DEGE!B 1/4AE
   3/4C,CURCUR<<U:^1eYENI!C YEN|CUR]YENiYENH?eYENX?eCURJ Excel
   -a-oAE(R) *(R)ae|!!C YENtYEN~ AbacusCUR]-`aDEG-:?eYENX PostScript
   (R)ae|!!C

   +-q(R)MYENo|w,E Abacus YENunDEGu!G

 # pkg_add -r abacus

   |p-aG(R)MYENoCUR-L--`a"u+-o-a-o,U:!AS:AYENiYENH"IYENI Ports
   Collection!A "AYENIYENHCURU<<u:YENO!G

 # cd /usr/ports/deskutils/abacus
 # make install clean

     --------------------------------------------------------------

6.6. -oKn

   Ao:uM FreeBSD NOTO|]NOTDEG(R)A:-`aCURIA(c)w(c)E|O|b ISP
   CURS:P:!<<U:NOTy|ae!A
   CUR-L-^1LYEN|CUR]YENiYENHS:^1YENth.iS:@(R)`a+-Ao^1O(desktop)"O"IYENI!A
   "ACUR-L-<<](c)o"IYENI|b|o/-aA 3/4^1CURW+-!CYENO/<<e|^3
   1/4AECURd-oO/A^3YENIu{|!-a-o (R)MYENo(packages) (c)I ports,
   YENi"N"IYENI!AS:AYENiYENH(R)U
   3/4US:A-a-o>>Y"DYEN'^3yYENXCUR@OS:^1NOTu:-a-o(R)`a+-Ao^1O!C

   CURU+-NOTO^3o^3^1^2[>>\-a-o(c)O|^3(R)`a+-A^3YENI^3nAAeCURS:S:O:^3t|^AAU-ai!G

       ^3nAAe|W-oU       (R)MYENo|W-oU            Ports |W-oU         
   Mozilla             mozilla            www/mozilla                 
   Opera               opera              www/opera                   
   Firefox             firefox            www/firefox                 
   KOffice             koffice-kde3       editors/koffice-kde3        
   AbiWord             abiword            editors/abiword             
   The GIMP            gimp               graphics/gimp               
   OpenOffice.org      openoffice         editors/openoffice-1.1      
   Acrobat Reader      acroread           print/acroread7             
   gv                  gv                 print/gv                    
   Xpdf                xpdf               graphics/xpdf               
   GQview              gqview             graphics/gqview             
   GnuCash             gnucash            finance/gnucash             
   Gnumeric            gnumeric           math/gnumeric               
   Abacus              abacus             deskutils/abacus            

     --------------------------------------------------------------

              ^3^1 7. |h'CAAe 1/4vu(R)T 1/4O:(Multimedia)

   Edited by Ross Lippert.

7.1. .S:z

   FreeBSD  1/4s-ax|aCURa:'(c)|U-oO/u(R)A:YENd!A
   AAy+-zYENiYENH"E"u:"O|U^1q,-L-CURW-a-oDEG-aP:C,-uu 1/2e(Hi-Fi)!A
   |^1YEN~AUYEN]NOTACURF?y>>s(c)M 1/4 1/2(c)n MPEG Audio Layer 3
   (MP3)!B WAV!B YENHCURI Ogg Vorbis
   uYEN^3\|h-oO/(R)ae|!Anu-a-o-`aCURO!C|P(R)E FreeBSD Ports
   Collection CUR]YEN]NOTACURF^3\|h-a-oA^3YENIu{|!!A
   AAy+-zYENiYENH?yu!B 1/2s *u(R)A:YENHCURI+-+-"i MIDI DEGt^3AE!C

   nNOTO^3ssAAwDEGECURa^1A,OCUR-L-|P-a-oAAeAAc,!A FreeBSD CUR]-`a 1/4
   1/2(c)nCUR@-e-a-ouo/DEGTAE(c)M DVD!C  1/2s 1/2X!BA`a'<<(c)M 1/4
   1/2(c)nuo/DEGT-a-ou{|!CURnDEG_^3B^2zAnu-a-ou{|!^2CURCURO:CUR@"C,!C"O|p!A
   |b 1/4P: 1/4g^3o^3^1(R)E!A FreeBSD Ports Collection
   CURCURAU"S|^3Ath|u: audio/sox "-o 1/4E|nYENI-a-o 1/2s
   1/2XCURu"a!A-`aDEG-:YENI"OA`a'<<CUR-L-|P-a-o(R)ae|!!C
   CUR-L-^1L!A^3oO>>aDEG`i-a-o^3nAAeNOTauoP:i(R)iNOTONOTU.i"^3^3t-a-o!C

   YEN>>^3^1+-NCURP:^2D-^3](c)wu(R)A:YENd-a-oYEN^2n"BAEJ!CYENy<<eCURP:^2D-"`i-a-o
   X11 (uU 5 ^3^1)
   |w,E(c)M^3](c)w,I!ACURw,gA?"`iCURFAAaYENU:YENd-a-o^3!YEN-:!A
   |yn.Q|^3S:o|n-a-o 1/4 1/2(c)n(R)A:-aG!A CUR'>>YnCUR@"C,^2O^3! 1/2O
   3/4a!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!G

     * |p|o^3](c)w"t^2I!AYENHYEN? 1/2TANS:Ou(R)A:YENd!C

     * |p|o^1BYENI
       1/4EYEN>>u{|!!AYENH'u,Ou(R)A:YENdNOTOS:_YEN?+-`^1BS:@!C

     * |p|o,N"Mu(R)A:YENd-a-o^3](c)wDEGYAD!C

     * |p|o 1/4 1/2(c)n!B?y>>s MP3 CURI"a:YENLAnuAE(R) *(R)ae|!!C

     * X server NOTO|p|oCURa:'(c)AAaYENU:YENd!C

     * Ports Collections CUR-o|^3th"C,|nYENI-a-o 1/4v^1^3 1/4
       1/2(c)n!B?y>>s^3nAAe!C

     * |p|o 1/4 1/2(c)n DVD -a-o .mpg CURI .avi AE

     * |p|o+-q CD (c)M DVD CURCURA^"u(rip)AE(R) *!C

     * |p|o^3](c)w^1quo/YENd

     * |p|o^3](c)w+- 1/2'y 3/4^1

   |b 3/4\AA-a^3o^3^1CURS:<<e!A+-zA^3.iCURF,N!G

     * -a 3/4^1D|p|o^3](c)w!B|w,E.s-a-o kernel (uU 8 ^3^1)!C

     A:uS:i|p-aGnYENI mount(8) <<u:YENO"O mount u
     1/4O:YENu-oD--a-o,U:!A^3q+-`.|uoYENI?u>>~!A NOTAE|U: 3/4EP
     kernel panic!C ^3oNOTO|]NOTDEGu 1/4O:YENu-oD-NOTO-S(R)i 1/2s
     1/2X!A|O<<DCUR@-e-a-o ISO AE(R) *"t^2ICURS:NOTG!C

     --------------------------------------------------------------

7.2. ^3](c)wu(R)A:YENd

   Contributed by Moses Moore. YEN[+-j FreeBSD 5.X
   -a-oCUR-o(R)e!GMarc Fonvieille.

  7.2.1. ^3](c)w"t^2I

   P:}(c)l^3](c)wCURS:<<e!AYEN^2P:.YENy-a
   3/4^1DS:A-a-ou(R)A:YENd<<NOT,^1!B'^1CURuNOTDEG|o!AYENHCURINOTO PCI
   (c)I ISA ^3W(R)ae!C FreeBSD |^3CURa:'(c)^3\|h-oO/-a-o PCI!BISA
   u(R)A:YENd!A 1/2D-AENOTdCURa:'(c)-a-ou(R)A:uwAAe-ai Hardware
   Notes!AYENH 1/2T>>{S:A-a-ou(R)A:YENdNOTOS:_CURa:'(c)!C
   YEN>>CURaaCUR].|'-L-"`iNOTU^1iA^3,OYENd-a-oAAXDEGEu{|!!C

   n"IYENIu(R)A:YENd!AYEN^2P:.n,u:CURJYEN?
   1/2T-a-oAAXDEGEu{|!CUR~|ae!C|^3"a-oO/CURe|!^3-L-YENiYENHS:^1|"^3oDEGES:@!A
   ^3IA^2^3aeCURe|!'NNOTOYENH kldload(8) "O>>'AP,u:CURJ kernel
   DEGE-oA 1/4O^2O(module)!A ^1^3NOTOCURU|C<<u:YENO!G

 # kldload snd_emu10k1

   (c)I-aIS:aNOTUAo:AAXDEGEu{|!YEN["`i /boot/loader.conf
   AE!A^1^3NOTO!G

 snd_emu10k1_load="YES"

   CURW+-"OCURlNOTOu^1 Creative SoundBlaster(R) Live!
   u(R)A:YENd"IYENI-a-o!C "a:YENLYENiYENI-a-ou(R)A:YENdAAXDEGEu{|!
   1/4O^2O!AYENiDEGN|O /boot/defaults/loader.conf  1/2d"O!C YCUR-L-
   1/2T(c)w"`i(c)^3,OYENIthCUR@-oO/AAXDEGEu{|!!A"-o>>oYENiYENH,O,O,u:CURJ
   snd_driver  1/4O^2ONOTYNOTY!G

 # kldload snd_driver

   This is a metadriver loading the most common device drivers at
   once. This speeds up the search for the correct driver. It is also
   possible to load all sound drivers via the /boot/loader.conf
   facility.

   If you wish to find out the driver selected for your soundcard
   after loading the snd_driver metadriver, you may check the
   /dev/sndstat file with the cat /dev/sndstat command.

     -a`: Under FreeBSD 4.X, to load all sound drivers, you have to
     load the snd module instead of snd_driver.

   A second method is to statically compile in support for your sound
   card in your kernel. The section below provides the information
   you need to add support for your hardware in this manner. For more
   information about recompiling your kernel, please see uU 8 ^3^1.

     --------------------------------------------------------------

    7.2.1.1. Configuring a Custom Kernel with Sound Support

   The first thing to do is adding the generic audio driver sound(4)
   to the kernel, for that you will need to add the following line to
   the kernel configuration file:

 device sound

   Under FreeBSD 4.X, you would use the following line:

 device pcm

   Then we have to add the support for our sound card. Therefore, we
   need to know which driver supports the card. Check the supported
   audio devices list of the Hardware Notes, to determine the correct
   driver for your sound card. For example, a Creative SoundBlaster
   Live! sound card is supported by the snd_emu10k1(4) driver. To add
   the support for this card, use the following:

 device snd_emu10k1

   Be sure to read the manual page of the driver for the syntax to
   use. Information regarding the syntax of sound drivers in the
   kernel configuration can also be found in the
   /usr/src/sys/conf/NOTES file (/usr/src/sys/i386/conf/LINT for
   FreeBSD 4.X).

   Non-PnP ISA cards may require you to provide the kernel with
   information on the sound card settings (IRQ, I/O port, etc). This
   is done via the /boot/device.hints file. At system boot, the
   loader(8) will read this file and pass the settings to the kernel.
   For example, an old Creative SoundBlaster 16 ISA non-PnP card will
   use the snd_sbc(4) driver in conjunction with snd_sb16(4). For
   this card the following lines have to be added to the kernel
   configuration file:

 device snd_sbc
 device snd_sb16

   as well as the following in /boot/device.hints:

 hint.sbc.0.at="isa"
 hint.sbc.0.port="0x220"
 hint.sbc.0.irq="5"
 hint.sbc.0.drq="1"
 hint.sbc.0.flags="0x15"

   In this case, the card uses the 0x220 I/O port and the IRQ 5.

   The syntax used in the /boot/device.hints file is covered in the
   sound driver manual page. On FreeBSD 4.X, these settings are
   directly written in the kernel configuration file. In the case of
   our ISA card, we would only use this line:

 device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15

   The settings shown above are the defaults. In some cases, you may
   need to change the IRQ or the other settings to match your card.
   See the snd_sbc(4) manual page for more information.

     -a`: Under FreeBSD 4.X, some systems with built-in motherboard
     sound devices may require the following option in the kernel
     configuration:

 options PNPBIOS

     --------------------------------------------------------------

  7.2.2. Testing the Sound Card

   After rebooting with the modified kernel, or after loading the
   required module, the sound card should appear in your system
   message buffer (dmesg(8)) as something like:

 pcm0: <Intel ICH3 (82801CA)> port 0xdc80-0xdcbf,0xd800-0xd8ff irq 5 at device 31.5 on pci0
 pcm0: [GIANT-LOCKED]
 pcm0: <Cirrus Logic CS4205 AC97 Codec>

   The status of the sound card may be checked via the /dev/sndstat
   file:

 # cat /dev/sndstat
 FreeBSD Audio Driver (newpcm)
 Installed devices:
 pcm0: <Intel ICH3 (82801CA)> at io 0xd800, 0xdc80 irq 5 bufsz 16384
 kld snd_ich (1p/2r/0v channels duplex default)

   The output from your system may vary. If no pcm devices show up,
   go back and review what was done earlier. Go through your kernel
   configuration file again and make sure the correct device is
   chosen. Common problems are listed in uU 7.2.2.1 ,`.

   If all goes well, you should now have a functioning sound card. If
   your CD-ROM or DVD-ROM drive is properly coupled to your sound
   card, you can put a CD in the drive and play it with cdcontrol(1):

 % cdcontrol -f /dev/acd0 play 1

   Various applications, such as audio/workman can provide a
   friendlier interface. You may want to install an application such
   as audio/mpg123 to listen to MP3 audio files. A quick way to test
   the card is sending data to the /dev/dsp, like this:

 % cat filename > /dev/dsp

   where filename can be any file. This command line should produce
   some noise, confirming the sound card is actually working.

     -a`: FreeBSD 4.X users need to create the sound card device
     nodes before being able to use it. If the card showed up in
     message buffer as pcm0, you will have to run the following as
     root:

 # cd /dev
 # sh MAKEDEV snd0

     If the card detection returned pcm1, follow the same steps as
     shown above, replacing snd0 with snd1.

     MAKEDEV will create a group of device nodes that will be used by
     the different sound related applications.

   Sound card mixer levels can be changed via the mixer(8) command.
   More details can be found in the mixer(8) manual page.

     --------------------------------------------------------------

    7.2.2.1. Common Problems

              Error                           Solution                
   !S:unsupported subdevice    One or more of the device nodes was    
   XX!"                        not created correctly. Repeat the      
                               steps above.                           
   !S:sb_dspwr(XX) timed out!" The I/O port is not set correctly.     
                               The IRQ is set incorrectly. Make sure  
   !S:bad irq XX!"             that the set IRQ and the sound IRQ are 
                               the same.                              
   !S:xxx: gus pcm not         There is not enough available memory   
   attached, out of memory!"   to use the device.                     
                               Check with fstat | grep dsp if another 
   !S:xxx: can't open          application is holding the device      
   /dev/dsp!!"                 open. Noteworthy troublemakers are     
                               esound and KDE's sound support.        

     --------------------------------------------------------------

  7.2.3. Utilizing Multiple Sound Sources

   Contributed by Munish Chopra.

   It is often desirable to have multiple sources of sound that are
   able to play simultaneously, such as when esound or artsd do not
   support sharing of the sound device with a certain application.

   FreeBSD lets you do this through Virtual Sound Channels, which can
   be set with the sysctl(8) facility. Virtual channels allow you to
   multiplex your sound card's playback channels by mixing sound in
   the kernel.

   To set the number of virtual channels, there are two sysctl knobs
   which, if you are the root user, can be set like this:

 # sysctl hw.snd.pcm0.vchans=4
 # sysctl hw.snd.maxautovchans=4

   The above example allocates four virtual channels, which is a
   practical number for everyday use. hw.snd.pcm0.vchans is the
   number of virtual channels pcm0 has, and is configurable once a
   device has been attached. hw.snd.maxautovchans is the number of
   virtual channels a new audio device is given when it is attached
   using kldload(8). Since the pcm module can be loaded independently
   of the hardware drivers, hw.snd.maxautovchans can store how many
   virtual channels any devices which are attached later will be
   given.

     -a`: You cannot change the number of virtual channels for a
     device while it is in use. First close any programs using the
     device, such as music players or sound daemons.

   If you are not using devfs(5), you will have to point your
   applications at /dev/dsp0.x, where x is 0 to 3 if
   hw.snd.pcm.0.vchans is set to 4 as in the above example. On a
   system using devfs(5), the above will automatically be allocated
   transparently to the user.

     --------------------------------------------------------------

  7.2.4. ^3](c)w^1w^3](Mixer Channel)-a-ouP:qCURjCURp

   Contributed by Josef El-Rayes.

     -a`: YEN>>YEN\-`aYENu|^3|b FreeBSD 5.3-RELEASE
     CURICURS:<<a-a(c)YEN>>CUR~|^3CURa:'(c)!C

   The default values for the different mixer channels are hardcoded
   in the sourcecode of the pcm(4) driver. There are a lot of
   different applications and daemons that allow you to set values
   for the mixer they remember and set each time they are started,
   but this is not a clean solution, we want to have default values
   at the driver level. This is accomplished by defining the
   appropriate values in /boot/device.hints. E.g.:

 hint.pcm.0.vol="100"

   This will set the volume channel to a default value of 100, when
   the pcm(4) module is loaded.

     --------------------------------------------------------------

7.3. MP3 u 1/4O:

   Contributed by Chern Lee.

   MP3 (MPEG Layer 3 Audio) accomplishes near CD-quality sound,
   leaving no reason to let your FreeBSD workstation fall short of
   its offerings.

     --------------------------------------------------------------

  7.3.1. MP3 Players

   By far, the most popular X11 MP3 player is XMMS (X Multimedia
   System). Winamp skins can be used with XMMS since the GUI is
   almost identical to that of Nullsoft's Winamp. XMMS also has
   native plug-in support.

   XMMS can be installed from the multimedia/xmms port or package.

   XMMS' interface is intuitive, with a playlist, graphic equalizer,
   and more. Those familiar with Winamp will find XMMS simple to use.

   The audio/mpg123 port is an alternative, command-line MP3 player.

   mpg123 can be run by specifying the sound device and the MP3 file
   on the command line, as shown below:

 # mpg123 -a /dev/dsp1.0 Foobar-GreatestHits.mp3
 High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2 and 3.
 Version 0.59r (1999/Jun/15). Written and copyrights by Michael Hipp.
 Uses code from various people. See 'README' for more!
 THIS SOFTWARE COMES WITH ABSOLUTELY NO WARRANTY! USE AT YOUR OWN RISK!





 Playing MPEG stream from Foobar-GreatestHits.mp3 ...
 MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo

   /dev/dsp1.0 should be replaced with the dsp device entry on your
   system.

     --------------------------------------------------------------

  7.3.2. Ripping CD Audio Tracks

   Before encoding a CD or CD track to MP3, the audio data on the CD
   must be ripped onto the hard drive. This is done by copying the
   raw CDDA (CD Digital Audio) data to WAV files.

   The cdda2wav tool, which is a part of the sysutils/cdrtools suite,
   is used for ripping audio information from CDs and the information
   associated with them.

   With the audio CD in the drive, the following command can be
   issued (as root) to rip an entire CD into individual (per track)
   WAV files:

 # cdda2wav -D 0,1,0 -B

   cdda2wav will support ATAPI (IDE) CDROM drives. To rip from an IDE
   drive, specify the device name in place of the SCSI unit numbers.
   For example, to rip track 7 from an IDE drive:

 # cdda2wav -D /dev/acd0a -t 7

   The -D 0,1,0 indicates the SCSI device 0,1,0, which corresponds to
   the output of cdrecord -scanbus.

   To rip individual tracks, make use of the -t option as shown:

 # cdda2wav -D 0,1,0 -t 7

   This example rips track seven of the audio CDROM. To rip a range
   of tracks, for example, track one to seven, specify a range:

 # cdda2wav -D 0,1,0 -t 1+7

   The utility dd(1) can also be used to extract audio tracks on
   ATAPI drives, read uU 18.6.5 ,` for more information on that
   possibility.

     --------------------------------------------------------------

  7.3.3. Encoding MP3s

   Nowadays, the mp3 encoder of choice is lame. Lame can be found at
   audio/lame in the ports tree.

   Using the ripped WAV files, the following command will convert
   audio01.wav to audio01.mp3:

 # lame -h -b 128 \
 --tt "Foo Song Title" \
 --ta "FooBar Artist" \
 --tl "FooBar Album" \
 --ty "2001" \
 --tc "Ripped and encoded by Foo" \
 --tg "Genre" \
 audio01.wav audio01.mp3

   128 kbits seems to be the standard MP3 bitrate in use. Many enjoy
   the higher quality 160, or 192. The higher the bitrate, the more
   disk space the resulting MP3 will consume--but the quality will be
   higher. The -h option turns on the !S:higher quality but a little
   slower!" mode. The options beginning with --t indicate ID3 tags,
   which usually contain song information, to be embedded within the
   MP3 file. Additional encoding options can be found by consulting
   the lame man page.

     --------------------------------------------------------------

  7.3.4. Decoding MP3s

   In order to burn an audio CD from MP3s, they must be converted to
   a non-compressed WAV format. Both XMMS and mpg123 support the
   output of MP3 to an uncompressed file format.

   Writing to Disk in XMMS:

    1. Launch XMMS.

    2. Right-click on the window to bring up the XMMS menu.

    3. Select Preference under Options.

    4. Change the Output Plugin to !S:Disk Writer Plugin!".

    5. Press Configure.

    6. Enter (or choose browse) a directory to write the uncompressed
       files to.

    7. Load the MP3 file into XMMS as usual, with volume at 100% and
       EQ settings turned off.

    8. Press Play !X!X XMMS will appear as if it is playing the MP3,
       but no music will be heard. It is actually playing the MP3 to
       a file.

    9. Be sure to set the default Output Plugin back to what it was
       before in order to listen to MP3s again.

   Writing to stdout in mpg123:

    1. Run mpg123 -s audio01.mp3 > audio01.pcm

   XMMS writes a file in the WAV format, while mpg123 converts the
   MP3 into raw PCM audio data. Both of these formats can be used
   with cdrecord to create audio CDs. You have to use raw PCM with
   burncd(8). If you use WAV files, you will notice a small tick
   sound at the beginning of each track, this sound is the header of
   the WAV file. You can simply remove the header of a WAV file with
   the utility SoX (it can be installed from the audio/sox port or
   package):

 % sox -t wav -r 44100 -s -w -c 2 track.wav track.raw

   Read uU 18.6 ,` for more information on using a CD burner in
   FreeBSD.

     --------------------------------------------------------------

7.4.  1/4 1/2(c)n 1/4vCURu

   Contributed by Ross Lippert.

   Video playback is a very new and rapidly developing application
   area. Be patient. Not everything is going to work as smoothly as
   it did with sound.

   Before you begin, you should know the model of the video card you
   have and the chip it uses. While Xorg and XFree86 support a wide
   variety of video cards, fewer give good playback performance. To
   obtain a list of extensions supported by the X server using your
   card use the command xdpyinfo(1) while X11 is running.

   It is a good idea to have a short MPEG file which can be treated
   as a test file for evaluating various players and options. Since
   some DVD players will look for DVD media in /dev/dvd by default,
   or have this device name hardcoded in them, you might find it
   useful to make symbolic links to the proper devices:

 # ln -sf /dev/acd0c /dev/dvd
 # ln -sf /dev/racd0c /dev/rdvd

   On FreeBSD 5.X, which uses devfs(5) there is a slightly different
   set of recommended links:

 # ln -sf /dev/acd0 /dev/dvd
 # ln -sf /dev/acd0 /dev/rdvd

   Note that due to the nature of devfs(5), manually created links
   like these will not persist if you reboot your system. In order to
   create the symbolic links automatically whenever you boot your
   system, add the following lines to /etc/devfs.conf:

 link acd0 dvd
 link acd0 rdvd

   Additionally, DVD decryption, which requires invoking special
   DVD-ROM functions, requires write permission on the DVD devices.

   Some of the ports discussed rely on the following kernel options
   to build correctly. Before attempting to build, add this option to
   the kernel configuration file, build a new kernel, and reboot:

 options CPU_ENABLE_SSE

     -a`: On FreeBSD 4.X options USER_LDT should be added to the
     kernel configuration file. This option is not available on
     FreeBSD 5.X and later version.

   To enhance the shared memory X11 interface, it is recommended that
   the values of some sysctl(8) variables should be increased:

 kern.ipc.shmmax=67108864
 kern.ipc.shmall=32768

     --------------------------------------------------------------

  7.4.1. Determining Video Capabilities

   There are several possible ways to display video under X11. What
   will really work is largely hardware dependent. Each method
   described below will have varying quality across different
   hardware. Secondly, the rendering of video in X11 is a topic
   receiving a lot of attention lately, and with each version of
   Xorg, or of XFree86, there may be significant improvement.

   A list of common video interfaces:

    1. X11: normal X11 output using shared memory.

    2. XVideo: an extension to the X11 interface which supports video
       in any X11 drawable.

    3. SDL: the Simple Directmedia Layer.

    4. DGA: the Direct Graphics Access.

    5. SVGAlib: low level console graphics layer.

     --------------------------------------------------------------

    7.4.1.1. XVideo

   Xorg and XFree86 4.X have an extension called XVideo (aka Xvideo,
   aka Xv, aka xv) which allows video to be directly displayed in
   drawable objects through a special acceleration. This extension
   provides very good quality playback even on low-end machines.

   To check whether the extension is running, use xvinfo:

 % xvinfo

   XVideo is supported for your card if the result looks like:

 X-Video Extension version 2.2
 screen #0
   Adaptor #0: "Savage Streams Engine"
     number of ports: 1
     port base: 43
     operations supported: PutImage
     supported visuals:
       depth 16, visualID 0x22
       depth 16, visualID 0x23
     number of attributes: 5
       "XV_COLORKEY" (range 0 to 16777215)
               client settable attribute
               client gettable attribute (current value is 2110)
       "XV_BRIGHTNESS" (range -128 to 127)
               client settable attribute
               client gettable attribute (current value is 0)
       "XV_CONTRAST" (range 0 to 255)
               client settable attribute
               client gettable attribute (current value is 128)
       "XV_SATURATION" (range 0 to 255)
               client settable attribute
               client gettable attribute (current value is 128)
       "XV_HUE" (range -180 to 180)
               client settable attribute
               client gettable attribute (current value is 0)
     maximum XvImage size: 1024 x 1024
     Number of image formats: 7
       id: 0x32595559 (YUY2)
         guid: 59555932-0000-0010-8000-00aa00389b71
         bits per pixel: 16
         number of planes: 1
         type: YUV (packed)
       id: 0x32315659 (YV12)
         guid: 59563132-0000-0010-8000-00aa00389b71
         bits per pixel: 12
         number of planes: 3
         type: YUV (planar)
       id: 0x30323449 (I420)
         guid: 49343230-0000-0010-8000-00aa00389b71
         bits per pixel: 12
         number of planes: 3
         type: YUV (planar)
       id: 0x36315652 (RV16)
         guid: 52563135-0000-0000-0000-000000000000
         bits per pixel: 16
         number of planes: 1
         type: RGB (packed)
         depth: 0
         red, green, blue masks: 0x1f, 0x3e0, 0x7c00
       id: 0x35315652 (RV15)
         guid: 52563136-0000-0000-0000-000000000000
         bits per pixel: 16
         number of planes: 1
         type: RGB (packed)
         depth: 0
         red, green, blue masks: 0x1f, 0x7e0, 0xf800
       id: 0x31313259 (Y211)
         guid: 59323131-0000-0010-8000-00aa00389b71
         bits per pixel: 6
         number of planes: 3
         type: YUV (packed)
       id: 0x0
         guid: 00000000-0000-0000-0000-000000000000
         bits per pixel: 0
         number of planes: 0
         type: RGB (packed)
         depth: 1
         red, green, blue masks: 0x0, 0x0, 0x0

   Also note that the formats listed (YUV2, YUV12, etc) are not
   present with every implementation of XVideo and their absence may
   hinder some players.

   If the result looks like:

 X-Video Extension version 2.2
 screen #0
 no adaptors present

   Then XVideo is probably not supported for your card.

   If XVideo is not supported for your card, this only means that it
   will be more difficult for your display to meet the computational
   demands of rendering video. Depending on your video card and
   processor, though, you might still be able to have a satisfying
   experience. You should probably read about ways of improving
   performance in the advanced reading uU 7.4.3 ,`.

     --------------------------------------------------------------

    7.4.1.2. Simple Directmedia Layer

   The Simple Directmedia Layer, SDL, was intended to be a porting
   layer between Microsoft Windows, BeOS, and UNIX, allowing
   cross-platform applications to be developed which made efficient
   use of sound and graphics. The SDL layer provides a low-level
   abstraction to the hardware which can sometimes be more efficient
   than the X11 interface.

   The SDL can be found at devel/sdl12.

     --------------------------------------------------------------

    7.4.1.3. Direct Graphics Access

   Direct Graphics Access is an X11 extension which allows a program
   to bypass the X server and directly alter the framebuffer. Because
   it relies on a low level memory mapping to effect this sharing,
   programs using it must be run as root.

   The DGA extension can be tested and benchmarked by dga(1). When
   dga is running, it changes the colors of the display whenever a
   key is pressed. To quit, use q.

     --------------------------------------------------------------

  7.4.2. Ports and Packages Dealing with Video

   This section discusses the software available from the FreeBSD
   Ports Collection which can be used for video playback. Video
   playback is a very active area of software development, and the
   capabilities of various applications are bound to diverge somewhat
   from the descriptions given here.

   Firstly, it is important to know that many of the video
   applications which run on FreeBSD were developed as Linux
   applications. Many of these applications are still beta-quality.
   Some of the problems that you may encounter with video packages on
   FreeBSD include:

    1. An application cannot playback a file which another
       application produced.

    2. An application cannot playback a file which the application
       itself produced.

    3. The same application on two different machines, rebuilt on
       each machine for that machine, plays back the same file
       differently.

    4. A seemingly trivial filter like rescaling of the image size
       results in very bad artifacts from a buggy rescaling routine.

    5. An application frequently dumps core.

    6. Documentation is not installed with the port and can be found
       either on the web or under the port's work directory.

   Many of these applications may also exhibit !S:Linux-isms!". That
   is, there may be issues resulting from the way some standard
   libraries are implemented in the Linux distributions, or some
   features of the Linux kernel which have been assumed by the
   authors of the applications. These issues are not always noticed
   and worked around by the port maintainers, which can lead to
   problems like these:

    1. The use of /proc/cpuinfo to detect processor characteristics.

    2. A misuse of threads which causes a program to hang upon
       completion instead of truly terminating.

    3. Software not yet in the FreeBSD Ports Collection which is
       commonly used in conjunction with the application.

   So far, these application developers have been cooperative with
   port maintainers to minimize the work-arounds needed for port-ing.

     --------------------------------------------------------------

    7.4.2.1. MPlayer

   MPlayer is a recently developed and rapidly developing video
   player. The goals of the MPlayer team are speed and flexibility on
   Linux and other Unices. The project was started when the team
   founder got fed up with bad playback performance on then available
   players. Some would say that the graphical interface has been
   sacrificed for a streamlined design. However, once you get used to
   the command line options and the key-stroke controls, it works
   very well.

     --------------------------------------------------------------

      7.4.2.1.1. Building MPlayer

   MPlayer resides in multimedia/mplayer. MPlayer performs a variety
   of hardware checks during the build process, resulting in a binary
   which will not be portable from one system to another. Therefore,
   it is important to build it from ports and not to use a binary
   package. Additionally, a number of options can be specified in the
   make command line, as described in the Makefile and at the start
   of the build:

 # cd /usr/ports/multimedia/mplayer
 # make
 N - O - T - E

 Take a careful look into the Makefile in order
 to learn how to tune mplayer towards you personal preferences!
 For example,
 make WITH_GTK1
 builds MPlayer with GTK1-GUI support.
 If you want to use the GUI, you can either install
 /usr/ports/multimedia/mplayer-skins
 or download official skin collections from
 http://www.mplayerhq.hu/homepage/dload.html

   The default port options should be sufficient for most users.
   However, if you need the XviD codec, you have to specify the
   WITH_XVID option in the command line. The default DVD device can
   also be defined with the WITH_DVD_DEVICE option, by default
   /dev/acd0 will be used.

   As of this writing, the MPlayer port will build its HTML
   documentation and two executables, mplayer, and mencoder, which is
   a tool for re-encoding video.

   The HTML documentation for MPlayer is very informative. If the
   reader finds the information on video hardware and interfaces in
   this chapter lacking, the MPlayer documentation is a very thorough
   supplement. You should definitely take the time to read the
   MPlayer documentation if you are looking for information about
   video support in UNIX.

     --------------------------------------------------------------

      7.4.2.1.2. Using MPlayer

   Any user of MPlayer must set up a .mplayer subdirectory of her
   home directory. To create this necessary subdirectory, you can
   type the following:

 % cd /usr/ports/multimedia/mplayer
 % make install-user

   The command options for mplayer are listed in the manual page. For
   even more detail there is HTML documentation. In this section, we
   will describe only a few common uses.

   To play a file, such as testfile.avi, through one of the various
   video interfaces set the -vo option:

 % mplayer -vo xv testfile.avi

 % mplayer -vo sdl testfile.avi

 % mplayer -vo x11 testfile.avi

 # mplayer -vo dga testfile.avi

 # mplayer -vo 'sdl:dga' testfile.avi

   It is worth trying all of these options, as their relative
   performance depends on many factors and will vary significantly
   with hardware.

   To play from a DVD, replace the testfile.avi with dvd://N
   -dvd-device DEVICE where N is the title number to play and DEVICE
   is the device node for the DVD-ROM. For example, to play title 3
   from /dev/dvd:

 # mplayer -vo xv dvd://3 -dvd-device /dev/dvd

     -a`: The default DVD device can be defined during the build of
     the MPlayer port via the WITH_DVD_DEVICE option. By default,
     this device is /dev/acd0. More details can be found in the port
     Makefile.

   To stop, pause, advance and so on, consult the keybindings, which
   are output by running mplayer -h or read the manual page.

   Additional important options for playback are: -fs -zoom which
   engages the fullscreen mode and -framedrop which helps
   performance.

   In order for the mplayer command line to not become too large, the
   user can create a file .mplayer/config and set default options
   there:

 vo=xv
 fs=yes
 zoom=yes

   Finally, mplayer can be used to rip a DVD title into a .vob file.
   To dump out the second title from a DVD, type this:

 # mplayer -dumpstream -dumpfile out.vob dvd://2 -dvd-device /dev/dvd

   The output file, out.vob, will be MPEG and can be manipulated by
   the other packages described in this section.

     --------------------------------------------------------------

      7.4.2.1.3. mencoder

   Before using mencoder it is a good idea to familiarize yourself
   with the options from the HTML documentation. There is a manual
   page, but it is not very useful without the HTML documentation.
   There are innumerable ways to improve quality, lower bitrate, and
   change formats, and some of these tricks may make the difference
   between good or bad performance. Here are a couple of examples to
   get you going. First a simple copy:

 % mencoder input.avi -oac copy -ovc copy -o output.avi

   Improper combinations of command line options can yield output
   files that are unplayable even by mplayer. Thus, if you just want
   to rip to a file, stick to the -dumpfile in mplayer.

   To convert input.avi to the MPEG4 codec with MPEG3 audio encoding
   (audio/lame is required):

 % mencoder input.avi -oac mp3lame -lameopts br=192 \
          -ovc lavc -lavcopts vcodec=mpeg4:vhq -o output.avi

   This has produced output playable by mplayer and xine.

   input.avi can be replaced with dvd://1 -dvd-device /dev/dvd and
   run as root to re-encode a DVD title directly. Since you are
   likely to be dissatisfied with your results the first time around,
   it is recommended you dump the title to a file and work on the
   file.

     --------------------------------------------------------------

    7.4.2.2. The xine Video Player

   The xine video player is a project of wide scope aiming not only
   at being an all in one video solution, but also in producing a
   reusable base library and a modular executable which can be
   extended with plugins. It comes both as a package and as a port,
   multimedia/xine.

   The xine player is still very rough around the edges, but it is
   clearly off to a good start. In practice, xine requires either a
   fast CPU with a fast video card, or support for the XVideo
   extension. The GUI is usable, but a bit clumsy.

   As of this writing, there is no input module shipped with xine
   which will play CSS encoded DVD's. There are third party builds
   which do have modules for this built in them, but none of these
   are in the FreeBSD Ports Collection.

   Compared to MPlayer, xine does more for the user, but at the same
   time, takes some of the more fine-grained control away from the
   user. The xine video player performs best on XVideo interfaces.

   By default, xine player will start up in a graphical user
   interface. The menus can then be used to open a specific file:

 % xine

   Alternatively, it may be invoked to play a file immediately
   without the GUI with the command:

 % xine -g -p mymovie.avi

     --------------------------------------------------------------

    7.4.2.3. The transcode Utilities

   The software transcode is not a player, but a suite of tools for
   re-encoding video and audio files. With transcode, one has the
   ability to merge video files, repair broken files, using command
   line tools with stdin/stdout stream interfaces.

   A great number of options can be specified during the build from
   the multimedia/transcode port, we recommend the following command
   line to build transcode:

 # make WITH_OPTIMIZED_CFLAGS=yes WITH_LIBA52=yes WITH_LAME=yes WITH_OGG=yes \
 WITH_MJPEG=yes -DWITH_XVID=yes

   The proposed settings should be sufficient for most users.

   To illustrate transcode capacities, one example to show how to
   convert a DivX file into a PAL MPEG-1 file (PAL VCD):

 % transcode -i input.avi -V --export_prof vcd-pal -o output_vcd
 % mplex -f 1 -o output_vcd.mpg output_vcd.m1v output_vcd.mpa

   The resulting MPEG file, output_vcd.mpg, is ready to be played
   with MPlayer. You could even burn the file on a CD-R media to
   create a Video CD, in this case you will need to install and use
   both multimedia/vcdimager and sysutils/cdrdao programs.

   There is a manual page for transcode, but you should also consult
   the transcode wiki for further information and examples.

     --------------------------------------------------------------

  7.4.3. Further Reading

   The various video software packages for FreeBSD are developing
   rapidly. It is quite possible that in the near future many of the
   problems discussed here will have been resolved. In the mean time,
   those who want to get the very most out of FreeBSD's A/V
   capabilities will have to cobble together knowledge from several
   FAQs and tutorials and use a few different applications. This
   section exists to give the reader pointers to such additional
   information.

   The MPlayer documentation is very technically informative. These
   documents should probably be consulted by anyone wishing to obtain
   a high level of expertise with UNIX video. The MPlayer mailing
   list is hostile to anyone who has not bothered to read the
   documentation, so if you plan on making bug reports to them, RTFM.

   The xine HOWTO contains a chapter on performance improvement which
   is general to all players.

   Finally, there are some other promising applications which the
   reader may try:

     * Avifile which is also a port multimedia/avifile.

     * Ogle which is also a port multimedia/ogle.

     * Xtheater

     * multimedia/dvdauthor, an open source package for authoring DVD
       content.

     --------------------------------------------------------------

7.5. ^3](c)w^1quo/YENd(TV Cards)

   Original contribution by Josef El-Rayes. Enhanced and adapted by
   Marc Fonvieille.

     --------------------------------------------------------------

  7.5.1. CURP:^2D-

   ^1quo/YENd(TV card)YENiYENHAAy+-zYENI^1q,-L-"ONOTYuL 1/2u!B|^3
   1/2u^1quo/,`YENO/!C^3\|hYENd^3-L-NOTO^3z^1L RCA (c)I S-video
   ?eCURJ-oYCURl"O+-u|NOTuo/DEGT!A|OYENB|^3"C,YENdAUYENi+-u|NOT FM 
   1/4s 1/4 1/2-a-oYEN\-`a!C

   FreeBSD YENi^3z^1L bktr(4) AAXDEGEu{|!!A"OCURa:'(c) PCI
   CURP:+--a-o^1quo/YENd!AYENun^3o"C,YENd"IYENI-a-oNOTO Brooktree
   Bt848/849/878/879 (c)I Conexant CN-878/Fusion 878a
   uo/DEGTA^"u'^1CURu!C|^1YEN~!An|A
   1/2T>>{th"C,YENdCURW(c)O-ath-a-o?iYENxYEN\-`aNOTOS:_|^3CURa:'(c)!AYENiYENHDEGN|O
   bktr(4) >>!(c)u!AYENHNOTdNOTY(c)OCURa:'(c)-a-ouwAAe^2M^3ae!C

     --------------------------------------------------------------

  7.5.2. ^3](c)wNOTUAo:AAXDEGEu{|!

   nYENI^1quo/YENd-a-o,U:!A'Nn,u:CURJ bktr(4)
   AAXDEGEu{|!!A^3oOYENiYENH^3z^1L|b /boot/loader.conf
   AEYEN[CURWCURU+-^3oCUR@|ae'NYENiYENHCURF!G

 bktr_load="YES"

   |^1YEN~!ACUR]YENiYENHS:a,O kernel module -a 1/2+-u>>P kernel 
   1/2sA:P:|bCUR@DEG_!AS:@-ak'NNOTO|bS:A-a-o kernel
   ^3](c)wAECUR-o!AYEN[CURWCURU+-^3o'X|ae!G

 device   bktr
 device  iicbus
 device  iicbb
 device  smbus

   CURS:(c)OYENHnYEN[CURW^3o"C,ABYEN~-a-oAAXDEGEu{|!!ANOTO|]NOTDEGYENd-a-o|U^2O|"^3!CURA^3-L-NOTO^3z^1L
   I2C P: *NOTy+-AE|ONOTUCURNOT^3s+-u-a-o!C+-uCURU"O!A 1/2D-<<.s
   1/2sA:P:!B|w,E.s-a-o kernel !C

   |w,E|n.s-a-o kernel CURS:<<a!An<<P:} 3/4-:CUR~.|YENI(R)A:!CP:}
   3/4-:(R)E!AA^3,O.|NOTY"`iAth|u:CURU+--a-oYEN? 1/2TDEG>>'u"`i TV
   card DEGT(R)S:!G

 bktr0: <BrookTree 848A> mem 0xd7000000-0xd7000fff irq 10 at device 10.0 on pci0
 iicbb0: <I2C bit-banging driver> on bti2c0
 iicbus0: <Philips I2C bus> on iicbb0 master-only
 iicbus1: <Philips I2C bus> on iicbb0 master-only
 smbus0: <System Management Bus> on bti2c0
 bktr0: Pinnacle/Miro TV, Philips SECAM tuner.

   .iuM!A^3o"C,DEGT(R)S:YENi-`a|]+-z-a-ouwAAeCUR-L-|P|O|^3(c)OCUR-L-|P!CHowever
   you should check if the tuner is correctly detected; it is still
   possible to override some of the detected parameters with
   sysctl(8) MIBs and kernel configuration file options. For example,
   if you want to force the tuner to a Philips SECAM tuner, you
   should add the following line to your kernel configuration file:

 options OVERRIDE_TUNER=6

   or you can directly use sysctl(8):

 # sysctl hw.bt848.tuner=6

   See the bktr(4) manual page and the /usr/src/sys/conf/NOTES file
   for more details on the available options. (If you are under
   FreeBSD 4.X, /usr/src/sys/conf/NOTES is replaced with
   /usr/src/sys/i386/conf/LINT.)

     --------------------------------------------------------------

  7.5.3. |nYENI-a-ou{|!

   nYENI^1quo/YENd!AYENiYENHuo/>>Yn|w,ECURU|CA^3YENIu{|!CURS:CUR@!J

     * multimedia/fxtv provides TV-in-a-window and image/audio/video
       capture capabilities.

     * multimedia/xawtv is also a TV application, with the same
       features as fxtv.

     * misc/alevt decodes and displays Videotext/Teletext.

     * audio/xmradio, an application to use the FM radio tuner coming
       with some TV cards.

     * audio/wmtune, a handy desktop application for radio tuners.

   More applications are available in the FreeBSD Ports Collection.

     --------------------------------------------------------------

  7.5.4. Troubleshooting

   If you encounter any problem with your TV card, you should check
   at first if the video capture chip and the tuner are really
   supported by the bktr(4) driver and if you used the right
   configuration options. For more support and various questions
   about your TV card you may want to contact and use the archives of
   the freebsd-multimedia mailing list.

     --------------------------------------------------------------

7.6. +- 1/2'y 3/4^1

   Written by Marc Fonvieille.

     --------------------------------------------------------------

  7.6.1. CURP:^2D-

   FreeBSD 'N^1^3YENo|o^2{YENNS:@.~"t^2ICUR@
   1/4E!A^3-L-YENiYENH"IYENI+- 1/2'y 3/4^1!C |b FreeBSD NOTO^3z^1L
   Ports Collection CUR-o-a-o SANE(Scanner Access Now Easy)
   (c)O'-L-"N-a-o API "O 3/4THS:@+- 1/2'y 3/4^1!C SANE
   CUR].|"IYENICUR@"C, FreeBSD -a-oAAXDEGEu{|!"O+-+-"i+- 1/2'y
   3/4^1uwAAe!C

   FreeBSD |P(R)ECURa:'(c) SCSI (c)M USB "a-oO/CURP:+--a-o+- 1/2'y
   3/4^1!C|bDEGuYENo|o^3](c)wCURS:<<e!A 1/2D- 1/2T<<O SANE
   |^3CURa:'(c)+-z-a-o+- 1/2'y 3/4^1!C SANE |^3+-i CURa:'(c)uwAAe
   -a-o^2M^3ae!A^3o,I|^3CURP:^2D-+- 1/2'y
   3/4^1-a-oCURa:'(c)+-!-ap(c)M-aNOT-oADEGT(R)S:!C |b uscanner(4)
   CUR-oCUR]|^3'-L-"NCUR@YEN-: USB +- 1/2'y 3/4^1-a-oCURa:'(c)|C-ai!C

     --------------------------------------------------------------

  7.6.2. Kernel -a-o^3](c)w

   |p|PCURWz(c)O'-L--a-o SCSI (c)M USB
   NOTE+-^3-L-|^3CURa:'(c)!C^3on"u"M(c)o+-z-a-o+- 1/2'y
   3/4^1NOTE+-!A|O>>YnCUR-L-|P-a-o^3]^3AEAAXDEGEu{|!!C

     --------------------------------------------------------------

    7.6.2.1. USB CURP:+-

   The GENERIC kernel by default includes the device drivers needed
   to support USB scanners. Should you decide to use a custom kernel,
   be sure that the following lines are present in your kernel
   configuration file:

 device usb
 device uhci
 device ohci
 device uscanner

   Depending upon the USB chipset on your motherboard, you will only
   need either device uhci or device ohci, however having both in the
   kernel configuration file is harmless.

   If you do not want to rebuild your kernel and your kernel is not
   the GENERIC one, you can directly load the uscanner(4) device
   driver module with the kldload(8) command:

 # kldload uscanner

   To load this module at each system startup, add the following line
   to /boot/loader.conf:

 uscanner_load="YES"

   After rebooting with the correct kernel, or after loading the
   required module, plug in your USB scanner. The scanner should
   appear in your system message buffer (dmesg(8)) as something like:

 uscanner0: EPSON EPSON Scanner, rev 1.10/3.02, addr 2

   This shows that our scanner is using the /dev/uscanner0 device
   node.

     -a`: On FreeBSD 4.X, the USB daemon (usbd(8)) must be running to
     be able to see some USB devices. To enable this, add
     usbd_enable="YES" to your /etc/rc.conf file and reboot the
     machine.

     --------------------------------------------------------------

    7.6.2.2. SCSI CURP:+-

   If your scanner comes with a SCSI interface, it is important to
   know which SCSI controller board you will use. According to the
   SCSI chipset used, you will have to tune your kernel configuration
   file. The GENERIC kernel supports the most common SCSI
   controllers. Be sure to read the NOTES file (LINT under
   FreeBSD 4.X) and add the correct line to your kernel configuration
   file. In addition to the SCSI adapter driver, you need to have the
   following lines in your kernel configuration file:

 device scbus
 device pass

   Once your kernel has been properly compiled, you should be able to
   see the devices in your system message buffer, when booting:

 pass2 at aic0 bus 0 target 2 lun 0
 pass2: <AGFA SNAPSCAN 600 1.10> Fixed Scanner SCSI-2 device
 pass2: 3.300MB/s transfers

   If your scanner was not powered-on at system boot, it is still
   possible to manually force the detection by performing a SCSI bus
   scan with the camcontrol(8) command:

 # camcontrol rescan all
 Re-scan of bus 0 was successful
 Re-scan of bus 1 was successful
 Re-scan of bus 2 was successful
 Re-scan of bus 3 was successful

   Then the scanner will appear in the SCSI devices list:

 # camcontrol devlist
 <IBM DDRS-34560 S97B>              at scbus0 target 5 lun 0 (pass0,da0)
 <IBM DDRS-34560 S97B>              at scbus0 target 6 lun 0 (pass1,da1)
 <AGFA SNAPSCAN 600 1.10>           at scbus1 target 2 lun 0 (pass3)
 <PHILIPS CDD3610 CD-R/RW 1.00>     at scbus2 target 0 lun 0 (pass2,cd0)

   More details about SCSI devices, are available in the scsi(4) and
   camcontrol(8) manual pages.

     --------------------------------------------------------------

  7.6.3. ^3](c)w SANE

   The SANE system has been splitted in two parts: the backends
   (graphics/sane-backends) and the frontends
   (graphics/sane-frontends). The backends part provides access to
   the scanner itself. The SANE's supported devices list specifies
   which backend will support your image scanner. It is mandatory to
   determine the correct backend for your scanner if you want to be
   able to use your device. The frontends part provides the graphical
   scanning interface (xscanimage).

   The first thing to do is install the graphics/sane-backends port
   or package. Then, use the sane-find-scanner command to check the
   scanner detection by the SANE system:

 # sane-find-scanner -q
 found SCSI scanner "AGFA SNAPSCAN 600 1.10" at /dev/pass3

   The output will show the interface type of the scanner and the
   device node used to attach the scanner to the system. The vendor
   and the product model may not appear, it is not important.

     -a`: Some USB scanners require you to load a firmware, this is
     explained in the backend manual page. You should also read
     sane-find-scanner(1) and sane(7) manual pages.

   Now we have to check if the scanner will be identified by a
   scanning frontend. By default, the SANE backends comes with a
   command line tool called scanimage(1). This command allows you to
   list the devices and to perform an image acquisition from the
   command line. The -L option is used to list the scanner device:

 # scanimage -L
 device `snapscan:/dev/pass3' is a AGFA SNAPSCAN 600 flatbed scanner

   No output or a message saying that no scanners were identified
   indicates that scanimage(1) is unable to identify the scanner. If
   this happens, you will need to edit the backend configuration file
   and define the scanner device used. The /usr/local/etc/sane.d/
   directory contains all backends configuration files. This
   identification problem does appear with certain USB scanners.

   For example, with the USB scanner used in the uU 7.6.2.1 ,`,
   sane-find-scanner gives us the following information:

 # sane-find-scanner -q
 found USB scanner (UNKNOWN vendor and product) at device /dev/uscanner0

   The scanner is correctly detected, it uses the USB interface and
   is attached to the /dev/uscanner0 device node. We can now check if
   the scanner is correctly identified:

 # scanimage -L

 No scanners were identified. If you were expecting something different,
 check that the scanner is plugged in, turned on and detected by the
 sane-find-scanner tool (if appropriate). Please read the documentation
 which came with this software (README, FAQ, manpages).

   Since the scanner is not identified, we will need to edit the
   /usr/local/etc/sane.d/epson.conf file. The scanner model used was
   the EPSON Perfection(R) 1650, so we know the scanner will use the
   epson backend. Be sure to read the help comments in the backends
   configuration files. Line changes are quite simple: comment out
   all lines that have the wrong interface for your scanner (in our
   case, we will comment out all lines starting with the word scsi as
   our scanner uses the USB interface), then add at the end of the
   file a line specifying the interface and the device node used. In
   this case, we add the following line:

 usb /dev/uscanner0

   Please be sure to read the comments provided in the backend
   configuration file as well as the backend manual page for more
   details and correct syntax to use. We can now verify if the
   scanner is identified:

 # scanimage -L
 device `epson:/dev/uscanner0' is a Epson GT-8200 flatbed scanner

   Our USB scanner has been identified. It is not important if the
   brand and the model do not match. The key item to be concerned
   with is the `epson:/dev/uscanner0' field, which give us the right
   backend name and the right device node.

   Once the scanimage -L command is able to see the scanner, the
   configuration is complete. The device is now ready to scan.

   While scanimage(1) does allow us to perform an image acquisition
   from the command line, it is preferable to use a graphical user
   interface to perform image scanning. SANE offers a simple but
   efficient graphical interface: xscanimage
   (graphics/sane-frontends).

   Xsane (graphics/xsane) is another popular graphical scanning
   frontend. This frontend offers advanced features such as various
   scanning mode (photocopy, fax, etc.), color correction, batch
   scans, etc. Both of these applications are useable as a GIMP
   plugin.

     --------------------------------------------------------------

  7.6.4. Allowing Scanner Access to Other Users

   All previous operations have been done with root privileges. You
   may however, need other users to have access to the scanner. The
   user will need read and write permissions to the device node used
   by the scanner. As an example, our USB scanner uses the device
   node /dev/uscanner0 which is owned by the operator group. Adding
   the user joe to the operator group will allow him to use the
   scanner:

 # pw groupmod operator -m joe

   For more details read the pw(8) manual page. You also have to set
   the correct write permissions (0660 or 0664) on the /dev/uscanner0
   device node, by default the operator group can only read the
   device node. This is done by adding the following lines to the
   /etc/devfs.rules file:

 [system=5]
 add path uscanner0 mode 660

   Then add the following to /etc/rc.conf and reboot the machine:

 devfs_system_ruleset="system"

   More information regarding these lines can be found in the
   devfs(8) manual page. Under FreeBSD 4.X, the operator group has,
   by default, read and write permissions to /dev/uscanner0.

     -a`: Of course, for security reasons, you should think twice
     before adding a user to any group, especially the operator
     group.

     --------------------------------------------------------------

                     ^3^1 8. ^3](c)w FreeBSD Kernel

   S:o.s!B<<+-AE!GJim Mock. `iS:@NOTDEG!GJake Hamby.

8.1. .S:z

   kernel NOTO 3/4aO FreeBSD S:@.~"t^2I-a-o(R)O:CURss!C
   YEN|+-+-"iCURF"t^2I-a-o 3/4aAAe^1BS:@!AYEN]S:t(c)MDEGO
   3/4D-AAe-oTH^2z!B|wYENth+-+--oTH!B-oo,o!Buw-oD-|s"uuYENuYEN!C 
   3/4"-oTHYENO/<<e FreeBSD CURj|hYENiYENHYENIDEGE-oA module
   "O,u:CURJ!B"o/,u:(c)O>>YYEN\-`a!A |y|^3(R)EOCUR'|^3YEN^2n
   3/4C,.|<<.s 1/2ODEGt kernel!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!J

     * NOTDEG|o>>Yn<<.s 1/2ODEGt!B 1/2sA:P: kernel!H

     * n<<c,>>o *S:i kernel ^3](c)wAE!H

     * |p|oYENH kernel ^3](c)wAE"O<<O/YENss!B 1/2sA:P:.s-a-o kernel
       (c)O!H

     * |p|o|w,E.s-a-o kernel!C

     * |p|o^3B^2z kernel ?u>>~uL-akP:} 3/4-:-a-o+-!S:I!C

   YEN>>^3^1(c)OA|"O-a-oNOTUAo:<<u:YENO^3-L-NOTOYENH root
   AAv"OP:i|ae!C

     --------------------------------------------------------------

8.2. NOTDEG|o>>Yn<<.s 1/2ODEGt!B 1/2sA:P: kernel!H

   |'A-a-o FreeBSD -a-o kernel ^3QA,-oUNOTDEG !S:monolithic!"
   kernel!C ^3o.N<<a:NOTO>>!.i(R)E-a-o kernel
   NOTOOCURjP:oAYu{|!!AYENBYENuCURa:'(c)(c)T(c)w-a-ouwAAe|OCURw!C
   |p-aG+-z.QS:iAAU: kernel -a-o^3](c)w!A"-o>>oYEN^2P:.
   1/2sA:P:CUR@O.s-a-o"A<<.sP:} 3/4-:!ACUR~-`a+-OYENI!C

   ^2{|b-a-o FreeBSD CURwS:O:^3t|"-ao/"`i.s<<NOT-oA-a-o-oTH^2z
   1/4O|!!A"a:<<n-S|aNOTO!G kernel YEN\-`aYENiYENHAH(R)E"I
   3/4U>>Y"D!A |OYENHDEGE-oA,u:CURJ(c)I"o/,u:NOTUAo:-a-o kernel
   module!C ^3o"I+-o kernel -`aDEG-:S:O:^3t|]A^3.s-a-oAo^1O|OS:@ 1/2O
   3/4a (|^3AI^1^3NOTO!GuS:DEGO<<NOT^1q,-L-CURW-a-o PCMCIA YENdCUR@
   1/4ES:Y'!S:YYENI) !A(c)INOTO 1/4WYEN["a:YENL`iYEN>>-a-o^1w^3]
   kernel(GENERIC)(c)O"S|^3-a-oYEN\-`a!C ^3o-oO/ 1/4O|!!A'NYENsDEGu
   modular kernel((R)O:CURss 1/4O^2O)!C

   3/4"-oTH|p|^1!AAUNOTO|^3CUR@"C,YEN\-`aCUR'P:. 1/2sA:P:|b kernel
   CUR-oCUR~|ae!C|]NOTDEG|^3(R)EONOTO|]NOTDEG^3o"C,YEN\-`a>>P kernel
   u^2|X-a-oNOTU.i
   1/2AEAo/-oo+-K!A|OuL-ak+-NYEN|IS:E|"YENiDEGE-oA,u:CURJ-a-o module
   !F|O|^3(R)EO!A<<hNOTO|]NOTDEG"S|^3CURH|^3-aAA"OS:E"-o"C, kernel
   module -a-o^1eS:@!C

   <<.s 1/2ODEGt!B 1/2sA:P: kernel 'XYENGNOTO"C|`i BSD
   "IYENI-aI(c)OYEN^2P:.,g 3/4u-a-o^1Lu{!C 
   3/4"-oTH^3oP:uCURuS:@YENi-`aCURn,u-O(R)E!A|y|b FreeBSD
   -a-o"IYENICURW.||^3^3\|h|n^3B!C ,oYEN^2P:.CURa:'(c)CURj|h
   1/4AE|U|!uwAAe-a-o GENERIC kernel NOTUCURn-a-o,U:!A |U|ae 1/2ODEGt
   kernel
   CUR-L-|P^3B|b(c)o!GYENiYENHS:o!yAAeP:K!z!AYENuCURa:'(c)!y|UCURvuwAAe!z-a-o^3!CURA'N|n!C
   |n^3B|b(c)o!AA:'|p!J

     * P:} 3/4-:^3t<< *S:oS:O:!G|]NOTDEG|U|ae 1/2ODEGt-a-o kernel
       YENu>>YnDEG>>'u+-z"t^2ICURW-a-ouwAAe!A
       (c)OYENHAAy+-ODEGE(c)O-aa-a-o^1Lu{S:oNOTy-oZS:O:^3t!C

     * |uYENI-a-oDEGO 3/4D-AAeS:oCURO:!G|U|ae 1/2ODEGt-a-o kernel
       ^3q+-`.|CURn GENERIC (R)O:CURss"IYENIS:oCURO:-a-oDEGO
       3/4D-AAe!AYENN(c)o kernel YEN^2P:.CUR@-a 1/2|s(c)n|bDEGO
       3/4D-AAeCUR-o!A|]|^1^3o'NAAa+-oS:oYEN[<<n!C|]|^1!A ^1i(c)oDEGO
       3/4D-AAe,uCURp-a-o"t^2I"O>>!!A |U|ae 1/2ODEGt-a-o kernel
       'NYENiuo'S:S:o|h-a-oS:@YENI!B'S:AAx-aAAP:!!C

     * YENiCURa:'(c)S:o|huwAAe!G+-zYENi|b|U|ae 1/2ODEGt-a-o kernel 
       1/4WYEN[CUR@"C,`iYEN>> GENERIC
       (R)O:CURss"S|^3'-L-"N-a-ouwAAeCURa:'(c)!A^1^3NOTOu(R)A:YENdCURS:Ath-a-o!C

     --------------------------------------------------------------

8.3. +-''u"t^2IuwAAe

   Written by Tom Rhodes.

   |bP:i|ae kernel ^3](c)w-a-o+-'-ACURS:(R)E<<e!A YENyS:a,O 3/4-:
   3/4^1|UP:uuwAAe,eDEGTS:@AI 1/2ONOTd.|NOTO(c)u' 1/4CURS:A|!C Y
   FreeBSD
   "A<<DYENDn-a-oS:@.~"t^2I!A"-o>>oCUR]YENiYENH>>'AP^3z^1LYENO/<<e(c)O"IYENI-a-oS:@.~"t^2I!A
   "ONOTdNOTYNOTUAo:uwAAe,eDEGT-ai!C A|"O"O>>!!AMicrosoft -a-o
   ,E,m-oTH^2zu(Device Manager)
   CUR-o^3q+-`.||^3YENO/<<e|^3,E-a-ouwAAe,eDEGT!C |O ,E,m-oTH^2zu
   NOTO|b+-+-"iYENx!C

     -a`: Microsoft Windows NOTY"C,-a(c)YEN>><<hNOTOYENy^3z^1L
     "t^2I(System) |AP:iCURJ ,E,m-oTH^2zu!C

   Y,O 3/4-: 3/4^1(c)|YEN
   1/4|w,EYENo|oS:@.~"t^2I!A"-o>>o'Nn?E|US:a:YENXNOTUAo:uwAAe,eDEGT!C
   "a:CURCURCUR@-oO/CURe|!NOTO^3z^1L dmesg(8) YENHCURI man(1)!C
   FreeBSD CURWCURj|huwAAe^3-L-.||^3NOTUAo:-a-o man
   >>!(c)u|^3CURa:'(c)-a-o^3W(R)ae<<NOT,^1!A "AYENBP:}
   3/4-:-a-oDEG>>'u^1Lu{CURCUR!ACUR].||CYENX|^3S:a:"`i-a-ouwAAe!C
   A|O"OCURl!A
   CURU+-^3o'X|aeNOTO>>!|^3DEG>>'u"`i.AE^1<<!A"AYENBNOTOYENH psm
   AAXDEGEu{|!!G

 psm0: <PS/2 Mouse> irq 12 on atkbdc0
 psm0: [GIANT-LOCKED]
 psm0: [ITHREAD]
 psm0: model Generic PS/2 mouse, device ID 0

   AAXDEGEu{|!YEN^2P:.n|b|Uq-a-o kernel
   ^3](c)wAECUR-oYEN[CURJ!A(c)I-aINOTOYENI loader.conf(5)!C

   dmesg |^3(R)EYENuAAaYENU:"t^2IDEGT(R)S:|O"S|^3P:}
   3/4-:DEG>>'u-a-o^3!YEN-:!A ^1J"`i^3o-oO/+-!-ap 1/2D-NOTd 3/4\
   /var/run/dmesg.boot AE!C

   YENtYEN~CUR]YENiYENH^3z^1L pciconf(8)
   "O|CYENXS:o,O^2O-a-oNOTUAo:,eDEGT!C A|"O>>!(c)u!G

 ath0@pci0:3:0:0:        class=0x020000 card=0x058a1014 chip=0x1014168c rev=0x01 hdr=0x00
     vendor     = 'Atheros Communications Inc.'
     device     = 'AR5212 Atheros AR5212 802.11abg wireless'
     class      = network
     subclass   = ethernet

   CURW+-AAaYENU:NOTO^3z^1L pciconf -lv (c)ONOTY"`i-a-o ath uL
   1/2u-ooYENdAAXDEGEu{|!!C YENiYENHYENI man ath "ONOTdNOTY ath(4)
   -a-oNOTUAo:>>!(c)u!C

   |b"IYENI man(1) (R)E!AYEN[CURW -k DEGN
   1/4AECUR]YENiYENH'-L-"NCURn,u-oe.C,-a-o,eDEGT!C
   YENHCURWz"OCURl|O"YEN!AYENiYENHS:iNOTDEGYEN'!G

 # man -k Atheros

   'N.||CYENX|^3S:tCURWzAo:Aa:|r-a-oNOTUAo: man >>!(c)u!G

 ath(4)                   - Atheros IEEE 802.11 wireless network driver
 ath_hal(4)               - Atheros Hardware Access Layer (HAL)

   -a 3/4CURv-a 3/4(c)
   1/4!AYENyAA,NNOTUAo:uwAAeAo^1O!ACUR~-`aAAy+-uCURU"O-a-o|Uq kernel
   YEN'^3y^1Lu{S:oNOTDEGP:P:S:Q!C

     --------------------------------------------------------------

8.4. <<.s 1/2ODEGt!B 1/2sA:P: kernel

   -oYENy^1i kernel NOTUAo:YENO/?yS:@S:O:^3tCURP:^2D-!C
   ^3o,I(c)O'-L-"`i-a-o(c)O|^3YENO/?y^3-L-|b /usr/src/sys CUR-o!A
   CUR]YENiYENHYENI /sys ^3oO symbolic link "O^3s"`i^3o!C
   ^3o,I-a-o^3\|hCURlYENO/?yCURAS:OA\(c)n kernel
   -a-o|U^2O|"^3!CURA!A|y^1iYEN'^3y kernel 
   1/4vAAT^3I<<n-a-oYENO/?yNOTO arch/conf!A
   ^3o,INOTOYENiYENHDEGw^1i>>Y"D"O *S:i|Uq kernel NOTUAo:^3](c)w!C
   |^1YEN~!AAU|^3|b 1/2sA:P: kernel ^1Lu{CURCUR.| 1/4E(R)EA\(c)n-a-o
   compile YENO/?y!C eA?"`i-a-o arch
   YENiYENHNOTOYENk|CNOT[-ocCURS:CUR@!G i386!Balpha!B amd64!Bia64!B
   powerpc!Bsparc64!B pc98(|bCUReYEN>>,uNOTy|ae-a-oYENtCUR@-oO/ PC
   uwAAeNOT[-oc)!C
   |b|U-S(c)wuwAAeNOT[-ocYENO/?y-a-o-aF|e!AYENu.fDEGtNOTU^1iA^3-a-ouwAAeNOT[-oc|OCURw!C
   |O"a: 3/4l-a-o`i(c)l
   1/2X<<hNOTO>>PuwAAeNOT[-ocuLAo:!AYENiYENH|b(c)O|^3 FreeBSD
   YENi,E-a-oYENYENxCURW|@YENI!C 
   3/4aAAeYENO/?yNOT[-oc^3-L-NOTO|^3AATH?eYENi'`!A^1^3NOTO|UP:u|^3CURa:'(c)-a-ouwAAe^3]^3AE!BAE(R)
   *"t^2I!A
   YENHCURINOTUAo:?iP:u^3q+-`^3-L-.|A\|bYEN|I|UCURv-a-oCURlYENO/?yCUR-o!C

   YEN>>^3^1(c)OYENI"`i-a-o"OCURl!A^3-L-NOTOS:A"IYENI i386
   NOT[-oc-a-o 3/4-: 3/4^1!C 
   1/2D-"I^1e>>U+-!-ap!A^1iNOTUAo:YENO/?yS:@ 1/2O 3/4aS:YYENi!C

     -a`: Y+-z"t^2ICURW "S,E /usr/src/sys YENO/?y!A CUR]'NNOTO>>!"S,E
     kernel source code -a-o,U:!A"-o>>o^3IA^2^3ae|w,ECURe|!'NNOTOYENH
     root AAv"ODEGo|ae sysinstall!A +-uuU 1/2D-?i Configure!AuM<<a?i
     Distributions +-uuUNOTDEG src |A?i base ^3I<<a?i sys!C
     YCUR-L-^3ssAAwYENI sysinstall |OYENBCURaAa:|^3 !S:YEN?|!-a-o!"
     FreeBSD YENu-oD-YENiYENHYENI-a-o,U:!A
     "-o>>oCUR]YENiYENHYENIYENHCURU<<u:YENO"O|w,E!G

 # mount /cdrom
 # mkdir -p /usr/src/sys
 # ln -s /usr/src/sys /sys
 # cat /cdrom/src/ssys.[a-d]* | tar -xzvf -
 # cat /cdrom/src/sbase.[a-d]* | tar -xzvf -

   +-uCURU"O!ACURA'<<"`i arch/conf YENO/?y!A  1/2AE>>s GENERIC
   ^3](c)wAENOTDEGS:A.Q-oU(c)I-a-o.s kernel |W-oU!C "O|p!G

 # cd /usr/src/sys/i386/conf
 # cp GENERIC MYKERNEL

   ^3q+-`!A(c)R|WCURe|!^3-L-NOTOCURj
   1/4g!C|p-aGS:At^3d-ouAA@^3\|hCUR-L-|PuwAAeNOT[-oc-a-o FreeBSD 
   3/4-: 3/4^1-a-o,U:!A"-o>>o.O,O 3/4-:
   3/4^1|W-oU(hostname)"O(c)R|W.|NOTOCURn,u(c)u' 1/4!C
   CURW+-"OCURlCURCURCURS:(c)OYENH(c)R|WNOTDEG MYKERNEL
   'NNOTO|]NOTDEG^3o 1/2tNOTG!C

     '-L-YENU:: <<O/A:^3CUR-L-nS:aS:i^1L-a-o kernel ^3](c)wAE-a
     1/2+-u(c)n|b /usr/src!C |]NOTDEGY
     1/2sA:P:^1J"`i"a:YENLDEGYAD(R)E!A -a 1/2+-uNOTaa+- 1/4 /usr/src
     |A<< 1/2m!A YENi-`a.|NOTOCURn,uDEG(R)-U:-a-o?i 3/4U:CURS:CUR@!C
     CUR@YEN^1-u-a-oNOTaaCURFCURS:<<a!AS:AYENi-`a'XNOTiCURS:<<aCUR~.|?o(R)(c)"`i!G
     S:A|P(R)ECUR]NOTaa+- 1/4|UCURvS:i-a-o kernel ^3](c)wAE!C
     |^1YEN~!ACUR]CUR-L-n-a 1/2+-u *S:i GENERIC!A|]NOTDEGCURU|,S:A
     S:o.s source tree(R)E!A YEN|.|^3Q.s-a(c)AD->>\!A|ONOTUAo:
     *S:iCUR]+-NAHCURS:|O^3u!C

     S:ACUR]YENi|O 1/4{S:a kernel
     ^3](c)wAES:i(c)n"`i"a:YENL|aCURe!AuM<<a|A"`i i386
     YENO/?yCUR-o<<O/O<<u:|VYEN|-a-o symbolic link!C

     A|"O!G

 # cd /usr/src/sys/i386/conf
 # mkdir /root/kernels
 # cp GENERIC /root/kernels/MYKERNEL
 # ln -s /root/kernels/MYKERNEL

   ^2{|b!A'NP:}(c)lYENI|UCURv^3ssAAw-a-o 1/2s?e 3/4^1"O *S:i
   MYKERNEL!C YCUR~e,E|n FreeBSD |OCURw!ADEGssCUR@YENiYENI-a-o 1/2s?e
   3/4^1<<U:YENi-`aNOTO vi
   CURF!AYENN(c)oYEN|-a-oYENI-ak<<U:|h-oO/!AA-a(c)o
   1/2g'T+-NCUR-L-,O^2OCURP:^2D-!A S:AYENi|b DEGN|O(R)NYENO/
   CUR-oS:a:"`iNOTUAo:(R)NA:y!C CUR-L-^1L!AFreeBSD
   CUR]'-L-"NYENtCUR@OS:o|nYENI-a-o 1/2s?e 3/4^1!AYEN|YENsDEGu
   ee!A^1i.sCURa|O"YEN!A^3oYENi-`aNOTOAEZ|n-a-o?i 3/4U:!C
   S:AYENiYENHYENo.N *S:iAE(R)
   *CUR-o-a-oNOTUAo:uu,NYENH>>!(c)uNOTUAo:^3](c)wNOTDEG|o!A
   (c)I-aI"a:YENL.QS:i-a-o GENERIC ^3](c)wCUR-o(R)e!C

   YS:A|^3|b SunOS (c)I-aI"a:YENL-oO/ BSD S:@.~"t^2ICURUP:i|ae
   1/2sA:P: kernel -a-o,gAAc,!A "-o>>oA^3,OCURw,g<<U: 1/4o+-xYEN>>
   1/2g(c)OCURP:^2D--a-oCURj^3!CURA"BAEJ!C
   '<<YENy,U:>>!!AY+-zCURS:<<eYENI-a-oNOTO DOS
   ^3oAthS:@.~"t^2I!A"-o>>o GENERIC
   ^3](c)wAE-a-oCUR-o(R)e'NYENi-`aCURn,uAo/A'"C,!A"SAo:<<Y!A
   S:UI+-N|bCURU+--a-o kernel ^3](c)w .|'`S:C,-oYENP:i|aCURP:^2D-!C

     -a`: Y|^3+-q FreeBSD p^1-oYENh S:o.sS:A-a-o source tree
     -a-o,U:!A
     <<hCURADEGO|bP:i|aeYENo|oCURE-AACURS:<<e!ADEGEYEN^2n^1iNOTY
     /usr/src/UPDATING!C
     ^3oAE.|CURP:^2D-|bS:o.s^1Lu{CURCUR-a-o<<CURjA:^3AD(c)In-a`.N-a-o"AEP:u!C
     YENN(c)o /usr/src/UPDATING NOTO^1iA^3(c)oS:A 3/4-:
     3/4^1CURWYENO/<<e-a-o FreeBSD source code
     -a(c)YEN>>!A|]|^1.|'-L-"NCURnYEN>>CURaYENUS:o.s-a-oCUR-o(R)e!C

   ^2{|bP:}(c)l"O 1/2sA:P: kernel S:a!C

   1/2sA:P: Kernel

    1. 1/2D-CURA'<<|U: /usr/src YENO/?y!G

 # cd /usr/src

    2. 1/2sA:P: kernel!G

 # make buildkernel KERNCONF=MYKERNEL

    3. |w,E.s kernel!G

 # make installkernel KERNCONF=MYKERNEL

     -a`: n|^3S:^1 3/4a-a-o FreeBSD source tree CUR~-`a 1/2sA:P:
     kernel!C

     '-L-YENU:: ^1w^3]+-!-apCURU!A|b 1/2sA:P:|Uq kernel
     (R)E!AYENth^3!-a-o kernel modules CUR].|CUR@DEG_<< 1/2s!C
     YnS:O:^3tCURE-AA kernel!A (c)INOTOYENu.Q<< 1/2s(c)O>>Y-a-o
     kernel module!A"-o>>o|b 1/2sA:P: kernel <<enYENyS:iCUR@CURU
     /etc/make.conf!ACURn|p!G

 MODULES_OVERRIDE = linux acpi sound/sound sound/driver/ds1 ntfs

     CURW+-,O^3](c)wENOTDEG(c)OS:AE+-ae<< 1/2s-a-o kernel module
     |C-ai!C

 WITHOUT_MODULES = linux acpi sound/sound sound/driver/ds1 ntfs

     |OCURW+-^3o^3](c)wE<<hNOTDEGCUR-L-n 1/2sCURJ-a-o kernel module
     |C-ai!C Y.QS:oAA,N"a:YENL kernel  1/2sA:P:-a-oNOTUAo:AAU:
     1/4AE!A 1/2D-DEGN 3/4\ make.conf(5) >>!(c)u!C

   .s-a-o kernel .| 1/2AE>>s"`i /boot/kernel YENO/?yCUR-o-a-o
   /boot/kernel/kernel!A|OAA-a-o<<h^2 3/4|U:
   /boot/kernel.old/kernel!C ^2{|b(c)O!AYENyAo:
   3/4-:!AuM<<a'N.|YENH.s kernel <<P:} 3/4-:
   Y|^3DEGYAD-a-o,U:!AYEN>>^3^1<<a+-.|CURP:^2D-CUR@"C,-oAAo/Ao/-g"O"oS:US:A!C
   Y.s kernel uL-akP:} 3/4-:-a-o,U:!A 1/2D-DEGN 3/4\ ^3o,I
   YENH<<`i'_"t^2I^1BS:@!C

     -a`: |U:(c)oP:} 3/4-:^1Lu{-a-o"a:YENLNOTUAo:AE(R)
     *!B^3](c)w!ACURn|p loader(8) CURI"a:^3](c)w!A<<h(c)n|b /boot!C
     Third party (c)I|Uq-a-o kernel modules <<h.|(c)n|b
     /boot/kernel!ACUR-L-^1L!A A^3-a`.Nn<<O<<u kernel module >>P
     kernel NOTOS:_|^3|P"B!A ^3oAI<<U:<<n!AS:_<<h.|
     3/4EPCUR-L-A(c)IYENXDEGYAD!C

     --------------------------------------------------------------

8.5. kernel ^3](c)wAE,N>>!

   Updated for FreeBSD 6.X by Joel Dahl.

   kernel ^3](c)wAE-a-oCUR-o(R)e(R)ae|!NOTU.iA^2^3ae!C
   "CCUR@|ae^3-L-YEN]NOTACUR@OAo:Aa:|r!AYENHCURICUR@O(c)I|hODEGN
   1/4AE!C"AE^1eCURW!A <<U:|h|aeCURj|hYENu|^3CUR@ODEGN
   1/4AE!CYENo|oYENH #
   P:}AY-a-o+-Oz^3-L-+-N^3Quo/NOTDEGuu,N|O^3Q(c)?^2CUR!C
   +-uCURU"O+-NYENH|b GENERIC
   (c)OYENX^2{-a-oP:P:S:C,CUR@CUR@CURP:^2D-CURS:!C
   YnNOTY>>P,OYENYENxNOT[-oc|^3Ao:-a-o|U?iP:u!B^3]^3AE|C-ai!A 
   1/2D-DEGN 3/4\>>P GENERIC AE|PYENO/?y-a-o NOTES AE!C
   |O>>PYENYENxNOT[-oc(R)t^2S:,uuLAo:-a-o^3qYENI^3!YEN-:!A<<hYENiDEGN
   3/4\ /usr/src/sys/conf/NOTES!C

     -a`:
     YNOTDEGCURF'u,O!A|O>>YnCUR@YEN-:S:t|^3(c)O|^3YENiYENI^3](c)w-a-o^3](c)wAE!A"-o>>o
     1/2D-YENH root "YEN-:CURU!G

 # cd /usr/src/sys/i386/conf && make LINT

   CURU+-NOTDEG GENERIC ^3](c)wAE-a-o 1/2d"O!A
   "a:CURCURYEN]NOTA>>!(c)uYENI-a-ouuA:A!C ^3o"OCURlA^3,O>>P+-z 3/4-:
   3/4^1CURW-a-o /usr/src/sys/i386/conf/GENERIC NOTU.i+-u-an!C

 machine         i386

   |^1^3BNOTO<<u: 3/4-: 3/4^1NOT[-oc!AYEN^2P:.NOTDEG alpha!Bamd64!B
   i386!Bia64!B pc98!Bpowerpc!B sparc64 "a:CURCURCURS:CUR@!C

 cpu          I486_CPU
 cpu          I586_CPU
 cpu          I686_CPU

   CURW+-^3](c)wNOTO<<u:(c)wnYENIthCUR@-oO/ CPU <<NOT,^1!C
   CUR]YENiYENH|P(R)EYEN[CURW|h^2O CPU <<NOT,^1
   (CURn|p>>!,UCUR@CUR-L- 1/2T(c)wNOTOS:_nYENI I586_CPU (c)I
   I686_CPU)!C uM|O|Uq kernel -a-o,U:!A<<O/A:^3YENy 1/2T>>{|UCURv-a-o
   CPU <<NOT,^1!AuM<<aYENuYENI^3I 3/4A|X-a-o"-o^2O'N|nCURF!C YCUR-L-
   1/2T(c)w CPU "`i(c)^3NOTOYENIthCUR@-oO/!A YENiYENHNOTd 3/4\
   /var/run/dmesg.boot -a-oP:} 3/4-:DEGT(R)S:YENH 1/2T(c)w!C

 ident          GENERIC

   ^3oNOTO^3](c)w,O kernel
   |W-oUNOTDEG|o!AYENiYENHAH.N(c)R|WCURS:!A^1^3NOTO"u|WNOTDEG
   MYKERNEL!AYNOTO|^3.OYENy<<e>>!(c)u"OS:@CURj.S:.|"u^3o 1/4E|W|r!C
   ident <<a+--a-o|r|e.||bP:} 3/4-:(R)EAAaYENU:!A|]|^1Yn?e>>{.s
   kernel >>P+-`YENI kernel
   -a-o,U:!A'N^3](c)wCUR-L-|P^2O|W-oUS:YYENi(CURn|p|b|Uq^1eAAc,YENI-a-o
   kernel)!C

 #To statically compile in device wiring instead of /boot/device.hints
 #hints          "GENERIC.hints"         # Default places to look for devices.

   device.hints(5) YENiYENI"O^3](c)w|UP:uAAXDEGEu{|!-a-o?iP:u!C P:}
   3/4-:(R)E loader(8) .|AENOTd^1w^3]-a-o /boot/device.hints
   ^3](c)wAE!C "IYENI hints ?iP:u!A'NYENiYENHS:a^3o"C, hints AR-oA
   1/2sCURJ kernel CUR-o!C |p|^1CUR@"O'NCUR-L-YEN^2|b /boot
   CUR-o<<O/YENss device.hints AE!C

 makeoptions     DEBUG=-g          # Build kernel with gdb(1) debug symbols

   YEN[CURW -g ?iP:u-a-o,U:!AFreeBSD .||b 1/2sA:P:^1Lu{YEN[CURW debug
   YENI-a-o,eDEGT!A^3z^1L^3o?iP:u.|AAy gcc(1) +-OYENI debug
   (c)O.|YENI"`i-a-oNOTUAo:,eDEGT!C

 options          SCHED_4BSD         # 4BSD scheduler

   FreeBSD. P:C,^2I(c)OYENI("AYENBNOTO^1w^3])-a-o"t^2I CPU
   scheduler!C Y+-zCUR-L-^2M.!n|p|o^3](c)w !A 1/2D-<<O-d^3o^3](c)w!C

 options          PREEMPTION         # Enable kernel thread preemption

   Allows threads that are in the kernel to be preempted by higher
   priority threads. It helps with interactivity and allows interrupt
   threads to run sooner rather than waiting.

 options          INET              # InterNETworking

   Networking support. Leave this in, even if you do not plan to be
   connected to a network. Most programs require at least loopback
   networking (i.e., making network connections within your PC), so
   this is essentially mandatory.

 options          INET6             # IPv6 communications protocols

   This enables the IPv6 communication protocols.

 options          FFS               # Berkeley Fast Filesystem

   This is the basic hard drive file system. Leave it in if you boot
   from the hard disk.

 options          SOFTUPDATES       # Enable FFS Soft Updates support

   This option enables Soft Updates in the kernel, this will help
   speed up write access on the disks. Even when this functionality
   is provided by the kernel, it must be turned on for specific
   disks. Review the output from mount(8) to see if Soft Updates is
   enabled for your system disks. If you do not see the soft-updates
   option then you will need to activate it using the tunefs(8) (for
   existing file systems) or newfs(8) (for new file systems)
   commands.

 options          UFS_ACL           # Support for access control lists

   This option enables kernel support for access control lists. This
   relies on the use of extended attributes and UFS2, and the feature
   is described in detail in uU 14.12 ,`. ACLs are enabled by default
   and should not be disabled in the kernel if they have been used
   previously on a file system, as this will remove the access
   control lists, changing the way files are protected in
   unpredictable ways.

 options          UFS_DIRHASH       # Improve performance on big directories

   This option includes functionality to speed up disk operations on
   large directories, at the expense of using additional memory. You
   would normally keep this for a large server, or interactive
   workstation, and remove it if you are using FreeBSD on a smaller
   system where memory is at a premium and disk access speed is less
   important, such as a firewall.

 options          MD_ROOT           # MD is a potential root device

   This option enables support for a memory backed virtual disk used
   as a root device.

 options          NFSCLIENT         # Network Filesystem Client
 options          NFSSERVER         # Network Filesystem Server
 options          NFS_ROOT          # NFS usable as /, requires NFSCLIENT

   The network file system. Unless you plan to mount partitions from
   a UNIX file server over TCP/IP, you can comment these out.

 options          MSDOSFS           # MSDOS Filesystem

   The MS-DOS file system. Unless you plan to mount a DOS formatted
   hard drive partition at boot time, you can safely comment this
   out. It will be automatically loaded the first time you mount a
   DOS partition, as described above. Also, the excellent
   emulators/mtools software allows you to access DOS floppies
   without having to mount and unmount them (and does not require
   MSDOSFS at all).

 options          CD9660            # ISO 9660 Filesystem

   The ISO 9660 file system for CDROMs. Comment it out if you do not
   have a CDROM drive or only mount data CDs occasionally (since it
   will be dynamically loaded the first time you mount a data CD).
   Audio CDs do not need this file system.

 options          PROCFS            # Process filesystem(requires PSEUDOFS)

   The process file system. This is a !S:pretend!" file system
   mounted on /proc which allows programs like ps(1) to give you more
   information on what processes are running. Use of PROCFS is not
   required under most circumstances, as most debugging and
   monitoring tools have been adapted to run without PROCFS: installs
   will not mount this file system by default.

 options          PSEUDOFS          # Pseudo-filesystem framework

   6.X kernels making use of PROCFS must also include support for
   PSEUDOFS.

 options          GEOM_GPT          # GUID Partition Tables.

   This option brings the ability to have a large number of
   partitions on a single disk.

 options          COMPAT_43         # Compatible with BSD 4.3 [KEEP THIS!]

   Compatibility with 4.3BSD. Leave this in; some programs will act
   strangely if you comment this out.

 options          COMPAT_FREEBSD4   # Compatible with FreeBSD4

   This option is required on FreeBSD 5.X i386 and Alpha systems to
   support applications compiled on older versions of FreeBSD that
   use older system call interfaces. It is recommended that this
   option be used on all i386 and Alpha systems that may run older
   applications; platforms that gained support only in 5.X, such as
   ia64 and Sparc64, do not require this option.

 options          COMPAT_FREEBSD5   # >>P FreeBSD5 NOTU(R)e

   |^1|aeNOTO FreeBSD 6.X CURIS:o.s-a-o-a(c)YEN>>Y>>YCURa:'(c)
   FreeBSD 5.X "t^2I(c)IYENsCUR~>>Yn^3](c)w!C

 options          SCSI_DELAY=5000  # Delay (in ms) before probing SCSI

   This causes the kernel to pause for 5 seconds before probing each
   SCSI device in your system. If you only have IDE hard drives, you
   can ignore this, otherwise you can try to lower this number, to
   speed up booting. Of course, if you do this and FreeBSD has
   trouble recognizing your SCSI devices, you will have to raise it
   again.

 options          KTRACE            # ktrace(1) support

   This enables kernel process tracing, which is useful in debugging.

 options          SYSVSHM           # SYSV-style shared memory

   This option provides for System V shared memory. The most common
   use of this is the XSHM extension in X, which many
   graphics-intensive programs will automatically take advantage of
   for extra speed. If you use X, you will definitely want to include
   this.

 options          SYSVMSG           # SYSV-style message queues

   Support for System V messages. This option only adds a few hundred
   bytes to the kernel.

 options          SYSVSEM           # SYSV-style semaphores

   Support for System V semaphores. Less commonly used but only adds
   a few hundred bytes to the kernel.

     -a`: The -p option of the ipcs(1) command will list any
     processes using each of these System V facilities.

 options              _KPOSIX_PRIORITY_SCHEDULING # POSIX P1003_1B real-time extensions

   Real-time extensions added in the 1993 POSIX(R). Certain
   applications in the Ports Collection use these (such as
   StarOffice).

 options          KBD_INSTALL_CDEV  # install a CDEV entry in /dev

   This option is required to allow the creation of keyboard device
   nodes in /dev.

 options          ADAPTIVE_GIANT    # Giant mutex is adaptive.

   Giant is the name of a mutual exclusion mechanism (a sleep mutex)
   that protects a large set of kernel resources. Today, this is an
   unacceptable performance bottleneck which is actively being
   replaced with locks that protect individual resources. The
   ADAPTIVE_GIANT option causes Giant to be included in the set of
   mutexes adaptively spun on. That is, when a thread wants to lock
   the Giant mutex, but it is already locked by a thread on another
   CPU, the first thread will keep running and wait for the lock to
   be released. Normally, the thread would instead go back to sleep
   and wait for its next chance to run. If you are not sure, leave
   this in.

     -a`: Note that on FreeBSD 8.0-CURRENT and later versions, all
     mutexes are adaptive by default, unless explicitly set to
     non-adaptive by compiling with the NO_ADAPTIVE_MUTEXES option.
     As a result, Giant is adaptive by default now, and the
     ADAPTIVE_GIANT option has been removed from the kernel
     configuration.

 device          apic               # I/O APIC

   The apic device enables the use of the I/O APIC for interrupt
   delivery. The apic device can be used in both UP and SMP kernels,
   but is required for SMP kernels. Add options SMP to include
   support for multiple processors.

     -a`: apic YENu i386
     NOT[-ocCUR~|^3!A"a:YENLNOT[-oc<<hCUR-L-YEN^2YEN[CURW^3o|ae!C

 device          eisa

   Include this if you have an EISA motherboard. This enables
   auto-detection and configuration support for all devices on the
   EISA bus.

 device          pci

   Include this if you have a PCI motherboard. This enables
   auto-detection of PCI cards and gatewaying from the PCI to ISA
   bus.

 # Floppy drives
 device          fdc

   This is the floppy drive controller.

 # ATA and ATAPI devices
 device          ata

   This driver supports all ATA and ATAPI devices. You only need one
   device ata line for the kernel to detect all PCI ATA/ATAPI devices
   on modern machines.

 device          atadisk                 # ATA disk drives

   This is needed along with device ata for ATA disk drives.

 device          ataraid                 # ATA RAID drives

   This is needed along with device ata for ATA RAID drives.

 device          atapicd                 # ATAPI CDROM drives

   This is needed along with device ata for ATAPI CDROM drives.

 device          atapifd                 # ATAPI floppy drives

   This is needed along with device ata for ATAPI floppy drives.

 device          atapist                 # ATAPI tape drives

   This is needed along with device ata for ATAPI tape drives.

 options         ATA_STATIC_ID           # Static device numbering

   This makes the controller number static; without this, the device
   numbers are dynamically allocated.

 # SCSI Controllers
 device          ahb        # EISA AHA1742 family
 device          ahc        # AHA2940 and onboard AIC7xxx devices
 options         AHC_REG_PRETTY_PRINT    # Print register bitfields in debug
                                         # output.  Adds ~128k to driver.
 device          ahd        # AHA39320/29320 and onboard AIC79xx devices
 options         AHD_REG_PRETTY_PRINT    # Print register bitfields in debug
                                         # output.  Adds ~215k to driver.
 device          amd        # AMD 53C974 (Teckram DC-390(T))
 device          isp        # Qlogic family
 device          ispfw      # Firmware for QLogic HBAs- normally a module
 device          mpt        # LSI-Logic MPT-Fusion
 #device         ncr        # NCR/Symbios Logic
 device          sym        # NCR/Symbios Logic (newer chipsets + those of `ncr')
 device          trm        # Tekram DC395U/UW/F DC315U adapters

 device          adv        # Advansys SCSI adapters
 device          adw        # Advansys wide SCSI adapters
 device          aha        # Adaptec 154x SCSI adapters
 device          aic        # Adaptec 15[012]x SCSI adapters, AIC-6[23]60.
 device          bt         # Buslogic/Mylex MultiMaster SCSI adapters

 device          ncv        # NCR 53C500
 device          nsp        # Workbit Ninja SCSI-3
 device          stg        # TMC 18C30/18C50

   SCSI controllers. Comment out any you do not have in your system.
   If you have an IDE only system, you can remove these altogether.
   The *_REG_PRETTY_PRINT lines are debugging options for their
   respective drivers.

 # SCSI peripherals
 device          scbus      # SCSI bus (required for SCSI)
 device          ch         # SCSI media changers
 device          da         # Direct Access (disks)
 device          sa         # Sequential Access (tape etc)
 device          cd         # CD
 device          pass       # Passthrough device (direct SCSI access)
 device          ses        # SCSI Environmental Services (and SAF-TE)

   SCSI peripherals. Again, comment out any you do not have, or if
   you have only IDE hardware, you can remove them completely.

     -a`: The USB umass(4) driver and a few other drivers use the
     SCSI subsystem even though they are not real SCSI devices.
     Therefore make sure not to remove SCSI support, if any such
     drivers are included in the kernel configuration.

 # RAID controllers interfaced to the SCSI subsystem
 device          amr        # AMI MegaRAID
 device          arcmsr     # Areca SATA II RAID
 device          asr        # DPT SmartRAID V, VI and Adaptec SCSI RAID
 device          ciss       # Compaq Smart RAID 5*
 device          dpt        # DPT Smartcache III, IV - See NOTES for options
 device          hptmv      # Highpoint RocketRAID 182x
 device          rr232x     # Highpoint RocketRAID 232x
 device          iir        # Intel Integrated RAID
 device          ips        # IBM (Adaptec) ServeRAID
 device          mly        # Mylex AcceleRAID/eXtremeRAID
 device          twa        # 3ware 9000 series PATA/SATA RAID

 # RAID controllers
 device          aac        # Adaptec FSA RAID
 device          aacp       # SCSI passthrough for aac (requires CAM)
 device          ida        # Compaq Smart RAID
 device          mfi        # LSI MegaRAID SAS
 device          mlx        # Mylex DAC960 family
 device          pst        # Promise Supertrak SX6000
 device          twe        # 3ware ATA RAID

   Supported RAID controllers. If you do not have any of these, you
   can comment them out or remove them.

 # atkbdc0 controls both the keyboard and the PS/2 mouse
 device          atkbdc     # AT keyboard controller

   The keyboard controller (atkbdc) provides I/O services for the AT
   keyboard and PS/2 style pointing devices. This controller is
   required by the keyboard driver (atkbd) and the PS/2 pointing
   device driver (psm).

 device          atkbd      # AT keyboard

   The atkbd driver, together with atkbdc controller, provides access
   to the AT 84 keyboard or the AT enhanced keyboard which is
   connected to the AT keyboard controller.

 device          psm        # PS/2 mouse

   Use this device if your mouse plugs into the PS/2 mouse port.

 device          kbdmux        # keyboard multiplexer

   |h<<Aa: 1/2L-a-oCURa:'(c)!C YCUR-L-YEN'-oa|P(R)E+-u|h^2OAa:
   1/2L-a-o,U:!A "-o>>oYn^2 3/4DEG-L-,O|aeCUR]"SAo:<<Y!C

 device          vga        # VGA video card driver

   The video card driver.

 device          splash     # Splash screen and screen saver support

   Splash screen at start up! Screen savers require this too.

 # syscons is the default console driver, resembling an SCO console
 device          sc

   sc is the default console driver and resembles a SCO console.
   Since most full-screen programs access the console through a
   terminal database library like termcap, it should not matter
   whether you use this or vt, the VT220 compatible console driver.
   When you log in, set your TERM variable to scoansi if full-screen
   programs have trouble running under this console.

 # Enable this for the pcvt (VT220 compatible) console driver
 #device          vt
 #options         XSERVER          # support for X server on a vt console
 #options         FAT_CURSOR       # start with block cursor

   This is a VT220-compatible console driver, backward compatible to
   VT100/102. It works well on some laptops which have hardware
   incompatibilities with sc. Also set your TERM variable to vt100 or
   vt220 when you log in. This driver might also prove useful when
   connecting to a large number of different machines over the
   network, where termcap or terminfo entries for the sc device are
   often not available !X!X vt100 should be available on virtually
   any platform.

 device          agp

   Include this if you have an AGP card in the system. This will
   enable support for AGP, and AGP GART for boards which have these
   features.

 # Power management support (see NOTES for more options)
 #device          apm

   Advanced Power Management support. Useful for laptops, although in
   FreeBSD 5.X and above this is disabled in GENERIC by default.

 # Add suspend/resume support for the i8254.
 device           pmtimer

   Timer device driver for power management events, such as APM and
   ACPI.

 # PCCARD (PCMCIA) support
 # PCMCIA and cardbus bridge support
 device          cbb               # cardbus (yenta) bridge
 device          pccard            # PC Card (16-bit) bus
 device          cardbus           # CardBus (32-bit) bus

   PCMCIA support. You want this if you are using a laptop.

 # Serial (COM) ports
 device          sio               # 8250, 16[45]50 based serial ports

   These are the serial ports referred to as COM ports in the
   MS-DOS/Windows world.

     -a`: If you have an internal modem on COM4 and a serial port at
     COM2, you will have to change the IRQ of the modem to 2 (for
     obscure technical reasons, IRQ2 = IRQ 9) in order to access it
     from FreeBSD. If you have a multiport serial card, check the
     manual page for sio(4) for more information on the proper values
     to add to your /boot/device.hints. Some video cards (notably
     those based on S3 chips) use IO addresses in the form of 0x*2e8,
     and since many cheap serial cards do not fully decode the 16-bit
     IO address space, they clash with these cards making the COM4
     port practically unavailable.

     Each serial port is required to have a unique IRQ (unless you
     are using one of the multiport cards where shared interrupts are
     supported), so the default IRQs for COM3 and COM4 cannot be
     used.

 # Parallel port
 device          ppc

   This is the ISA-bus parallel port interface.

 device          ppbus      # Parallel port bus (required)

   Provides support for the parallel port bus.

 device          lpt        # Printer

   Support for parallel port printers.

     -a`: All three of the above are required to enable parallel
     printer support.

 device          plip       # TCP/IP over parallel

   This is the driver for the parallel network interface.

 device          ppi        # Parallel port interface device

   The general-purpose I/O (!S:geek port!") + IEEE1284 I/O.

 #device         vpo        # Requires scbus and da

   This is for an Iomega Zip drive. It requires scbus and da support.
   Best performance is achieved with ports in EPP 1.9 mode.

 #device         puc

   Uncomment this device if you have a !S:dumb!" serial or parallel
   PCI card that is supported by the puc(4) glue driver.

 # PCI Ethernet NICs.
 device          de         # DEC/Intel DC21x4x (!S:Tulip!")
 device          em         # Intel PRO/1000 adapter Gigabit Ethernet Card
 device          ixgb       # Intel PRO/10GbE Ethernet Card
 device          txp        # 3Com 3cR990 (!S:Typhoon!")
 device          vx         # 3Com 3c590, 3c595 (!S:Vortex!")

   Various PCI network card drivers. Comment out or remove any of
   these not present in your system.

 # PCI Ethernet NICs that use the common MII bus controller code.
 # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs!
 device          miibus     # MII bus support

   MII bus support is required for some PCI 10/100 Ethernet NICs,
   namely those which use MII-compliant transceivers or implement
   transceiver control interfaces that operate like an MII. Adding
   device miibus to the kernel config pulls in support for the
   generic miibus API and all of the PHY drivers, including a generic
   one for PHYs that are not specifically handled by an individual
   driver.

 device          bce        # Broadcom BCM5706/BCM5708 Gigabit Ethernet
 device          bfe        # Broadcom BCM440x 10/100 Ethernet
 device          bge        # Broadcom BCM570xx Gigabit Ethernet
 device          dc         # DEC/Intel 21143 and various workalikes
 device          fxp        # Intel EtherExpress PRO/100B (82557, 82558)
 device          lge        # Level 1 LXT1001 gigabit ethernet
 device          msk        # Marvell/SysKonnect Yukon II Gigabit Ethernet
 device          nge        # NatSemi DP83820 gigabit ethernet
 device          nve        # nVidia nForce MCP on-board Ethernet Networking
 device          pcn        # AMD Am79C97x PCI 10/100 (precedence over 'lnc')
 device          re         # RealTek 8139C+/8169/8169S/8110S
 device          rl         # RealTek 8129/8139
 device          sf         # Adaptec AIC-6915 (!S:Starfire!")
 device          sis        # Silicon Integrated Systems SiS 900/SiS 7016
 device          sk         # SysKonnect SK-984x & SK-982x gigabit Ethernet
 device          ste        # Sundance ST201 (D-Link DFE-550TX)
 device          stge       # Sundance/Tamarack TC9021 gigabit Ethernet
 device          ti         # Alteon Networks Tigon I/II gigabit Ethernet
 device          tl         # Texas Instruments ThunderLAN
 device          tx         # SMC EtherPower II (83c170 !S:EPIC!")
 device          vge        # VIA VT612x gigabit ethernet
 device          vr         # VIA Rhine, Rhine II
 device          wb         # Winbond W89C840F
 device          xl         # 3Com 3c90x (!S:Boomerang!", !S:Cyclone!")

   Drivers that use the MII bus controller code.

 # ISA Ethernet NICs.  pccard NICs included.
 device          cs         # Crystal Semiconductor CS89x0 NIC
 # 'device ed' requires 'device miibus'
 device          ed         # NE[12]000, SMC Ultra, 3c503, DS8390 cards
 device          ex         # Intel EtherExpress Pro/10 and Pro/10+
 device          ep         # Etherlink III based cards
 device          fe         # Fujitsu MB8696x based cards
 device          ie         # EtherExpress 8/16, 3C507, StarLAN 10 etc.
 device          lnc        # NE2100, NE32-VL Lance Ethernet cards
 device          sn         # SMC's 9000 series of Ethernet chips
 device          xe         # Xircom pccard Ethernet

 # ISA devices that use the old ISA shims
 #device         le

   ISA Ethernet drivers. See /usr/src/sys/i386/conf/NOTES for details
   of which cards are supported by which driver.

 # Wireless NIC cards
 device          wlan       # 802.11 support

   ^1i 802.11  1/4D-.C,-a-oCURa:'(c)!C YnuL
   1/2uCURW-oo!A<<h>>YYEN[CURW^3o|ae!C

 device          wlan_wep        # 802.11 WEP support
 device          wlan_ccmp       # 802.11 CCMP support
 device          wlan_tkip       # 802.11 TKIP support

   ^1i 802.11 YEN[+-K^3]^3AE-a-oCURa:'(c)!C Yn|wYENthYEN[+-KYENHCURI
   802.11i |wYENth"o(c)w!A <<h>>YYEN[CURW^3o|ae!C

 device          an         # Aironet 4500/4800 802.11 wireless NICs.
 device          ath             # Atheros pci/cardbus NIC's
 device          ath_hal         # Atheros HAL (Hardware Access Layer)
 device          ath_rate_sample # SampleRate tx rate control for ath
 device          an         # Aironet 4500/4800 802.11 wireless NICs.
 device          awi        # BayStack 660 and others
 device          ral        # Ralink Technology RT2500 wireless NICs.
 device          wi         # WaveLAN/Intersil/Symbol 802.11 wireless NICs.
 #device         wl         # Older non 802.11 Wavelan wireless NIC.

   Support for various wireless cards.

 # Pseudo devices
 device   loop          # Network loopback

   This is the generic loopback device for TCP/IP. If you telnet or
   FTP to localhost (a.k.a. 127.0.0.1) it will come back at you
   through this device. This is mandatory.

 device   random        # Entropy device

   Cryptographically secure random number generator.

 device   ether         # Ethernet support

   ether is only needed if you have an Ethernet card. It includes
   generic Ethernet protocol code.

 device   sl            # Kernel SLIP

   sl is for SLIP support. This has been almost entirely supplanted
   by PPP, which is easier to set up, better suited for
   modem-to-modem connection, and more powerful.

 device   ppp           # Kernel PPP

   This is for kernel PPP support for dial-up connections. There is
   also a version of PPP implemented as a userland application that
   uses tun and offers more flexibility and features such as demand
   dialing.

 device   tun           # Packet tunnel.

   This is used by the userland PPP software. See the PPP section of
   this book for more information.

 device   pty           # Pseudo-ttys (telnet etc)

   This is a !S:pseudo-terminal!" or simulated login port. It is used
   by incoming telnet and rlogin sessions, xterm, and some other
   applications such as Emacs.

 device   md            # Memory !S:disks!"

   Memory disk pseudo-devices.

 device   gif           # IPv6 and IPv4 tunneling

   This implements IPv6 over IPv4 tunneling, IPv4 over IPv6
   tunneling, IPv4 over IPv4 tunneling, and IPv6 over IPv6 tunneling.
   The gif device is !S:auto-cloning!", and will create device nodes
   as needed.

 device   faith         # IPv6-to-IPv4 relaying (translation)

   This pseudo-device captures packets that are sent to it and
   diverts them to the IPv4/IPv6 translation daemon.

 # The `bpf' device enables the Berkeley Packet Filter.
 # Be aware of the administrative consequences of enabling this!
 # Note that 'bpf' is required for DHCP.
 device   bpf           # Berkeley packet filter

   This is the Berkeley Packet Filter. This pseudo-device allows
   network interfaces to be placed in promiscuous mode, capturing
   every packet on a broadcast network (e.g., an Ethernet). These
   packets can be captured to disk and or examined with the
   tcpdump(1) program.

     -a`: The bpf(4) device is also used by dhclient(8) to obtain the
     IP address of the default router (gateway) and so on. If you use
     DHCP, leave this uncommented.

 # USB support
 device          uhci          # UHCI PCI->USB interface
 device          ohci          # OHCI PCI->USB interface
 device          ehci          # EHCI PCI->USB interface (USB 2.0)
 device          usb           # USB Bus (required)
 #device         udbp          # USB Double Bulk Pipe devices
 device          ugen          # Generic
 device          uhid          # !S:Human Interface Devices!"
 device          ukbd          # Keyboard
 device          ulpt          # Printer
 device          umass         # Disks/Mass storage - Requires scbus and da
 device          ums           # Mouse
 device          ural          # Ralink Technology RT2500USB wireless NICs
 device          urio          # Diamond Rio 500 MP3 player
 device          uscanner      # Scanners
 # USB Ethernet, requires mii
 device          aue           # ADMtek USB Ethernet
 device          axe           # ASIX Electronics USB Ethernet
 device          cdce          # Generic USB over Ethernet
 device          cue           # CATC USB Ethernet
 device          kue           # Kawasaki LSI USB Ethernet
 device          rue           # RealTek RTL8150 USB Ethernet

   Support for various USB devices.

 # FireWire support
 device          firewire      # FireWire bus code
 device          sbp           # SCSI over FireWire (Requires scbus and da)
 device          fwe           # Ethernet over FireWire (non-standard!)

   Support for various Firewire devices.

   For more information and additional devices supported by FreeBSD,
   see /usr/src/sys/i386/conf/NOTES.

     --------------------------------------------------------------

  8.5.1. Large Memory Configurations (PAE)

   Large memory configuration machines require access to more than
   the 4 gigabyte limit on User+Kernel Virtual Address (KVA) space.
   Due to this limitation, Intel added support for 36-bit physical
   address space access in the Pentium Pro and later line of CPUs.

   The Physical Address Extension (PAE) capability of the Intel
   Pentium Pro and later CPUs allows memory configurations of up to
   64 gigabytes. FreeBSD provides support for this capability via the
   PAE kernel configuration option, available in all current release
   versions of FreeBSD. Due to the limitations of the Intel memory
   architecture, no distinction is made for memory above or below 4
   gigabytes. Memory allocated above 4 gigabytes is simply added to
   the pool of available memory.

   To enable PAE support in the kernel, simply add the following line
   to your kernel configuration file:

 options             PAE

     -a`: The PAE support in FreeBSD is only available for Intel
     IA-32 processors. It should also be noted, that the PAE support
     in FreeBSD has not received wide testing, and should be
     considered beta quality compared to other stable features of
     FreeBSD.

   PAE support in FreeBSD has a few limitations:

     * A process is not able to access more than 4 gigabytes of VM
       space.

     * KLD modules cannot be loaded into a PAE enabled kernel, due to
       the differences in the build framework of a module and the
       kernel.

     * Device drivers that do not use the bus_dma(9) interface will
       cause data corruption in a PAE enabled kernel and are not
       recommended for use. For this reason, a PAE kernel
       configuration file is provided in FreeBSD which excludes all
       drivers not known to work in a PAE enabled kernel.

     * Some system tunables determine memory resource usage by the
       amount of available physical memory. Such tunables can
       unnecessarily over-allocate due to the large memory nature of
       a PAE system. One such example is the kern.maxvnodes sysctl,
       which controls the maximum number of vnodes allowed in the
       kernel. It is advised to adjust this and other such tunables
       to a reasonable value.

     * It might be necessary to increase the kernel virtual address
       (KVA) space or to reduce the amount of specific kernel
       resource that is heavily used (see above) in order to avoid
       KVA exhaustion. The KVA_PAGES kernel option can be used for
       increasing the KVA space.

   For performance and stability concerns, it is advised to consult
   the tuning(7) manual page. The pae(4) manual page contains
   up-to-date information on FreeBSD's PAE support.

     --------------------------------------------------------------

8.6. If Something Goes Wrong

   There are five categories of trouble that can occur when building
   a custom kernel. They are:

   config fails:

           If the config(8) command fails when you give it your
           kernel description, you have probably made a simple error
           somewhere. Fortunately, config(8) will print the line
           number that it had trouble with, so that you can quickly
           locate the line containing the error. For example, if you
           see:

 config: line 17: syntax error

           Make sure the keyword is typed correctly by comparing it
           to the GENERIC kernel or another reference.

   make fails:

           If the make command fails, it usually signals an error in
           your kernel description which is not severe enough for
           config(8) to catch. Again, look over your configuration,
           and if you still cannot resolve the problem, send mail to
           the FreeBSD general questions P:l>> 1/4 1/2 * 3/4A with
           your kernel configuration, and it should be diagnosed
           quickly.

   The kernel does not boot:

           If your new kernel does not boot, or fails to recognize
           your devices, do not panic! Fortunately, FreeBSD has an
           excellent mechanism for recovering from incompatible
           kernels. Simply choose the kernel you want to boot from at
           the FreeBSD boot loader. You can access this when the
           system boot menu appears. Select the !S:Escape to a loader
           prompt!" option, number six. At the prompt, type unload
           kernel and then type boot /boot/kernel.old/kernel, or the
           filename of any other kernel that will boot properly. When
           reconfiguring a kernel, it is always a good idea to keep a
           kernel that is known to work on hand.

           After booting with a good kernel you can check over your
           configuration file and try to build it again. One helpful
           resource is the /var/log/messages file which records,
           among other things, all of the kernel messages from every
           successful boot. Also, the dmesg(8) command will print the
           kernel messages from the current boot.

             -a`: If you are having trouble building a kernel, make
             sure to keep a GENERIC, or some other kernel that is
             known to work on hand as a different name that will not
             get erased on the next build. You cannot rely on
             kernel.old because when installing a new kernel,
             kernel.old is overwritten with the last installed kernel
             which may be non-functional. Also, as soon as possible,
             move the working kernel to the proper /boot/kernel
             location or commands such as ps(1) may not work
             properly. To do this, simply rename the directory
             containing the good kernel:

 # mv /boot/kernel /boot/kernel.bad
 # mv /boot/kernel.good /boot/kernel

   The kernel works, but ps(1) does not work any more:

           If you have installed a different version of the kernel
           from the one that the system utilities have been built
           with, for example, a -CURRENT kernel on a -RELEASE, many
           system-status commands like ps(1) and vmstat(8) will not
           work any more. You should recompile and install a world
           built with the same version of the source tree as your
           kernel. This is one reason it is not normally a good idea
           to use a different version of the kernel from the rest of
           the operating system.

     --------------------------------------------------------------

                              ^3^1 9. |C|L

   Contributed by Sean Kelly. Restructured and updated by Jim Mock.

9.1. .S:z

   FreeBSD YENiYENH(c)M|U|!|U 1/4E-a-o|L-ai 3/4-:.fDEGt|C|L!A
   +-q^3I|N-a-o 1/4^2DEGw|!|L-ai 3/4-:"`i^3I.s-a-o^1p(R)g|L-ai
   3/4-:^3-L-"SDEGYAD!A
   AAy+-z-a-oA^3YENIu{|!YENiYENH^2-L-YENIYENXDEG-a<<~
   1/2e-a-oCURaaYENo|C|L?eYENX!C

   CUR]YENiYENHS:a FreeBSD ^3](c)w|"CUR@YENx-oo,o|C|L|o/-aA
   3/4^1!F^3o(R)EO-a-o FreeBSD
   -`a+-u|NOT"a:YENL^1q,-L-DEGe"O-a-o|C|LCURuS:@!AYEN]NOTA"a:YENL
   FreeBSD -a-o^1q,-L-!BWindows -a-o^1q,-L-YENHCURI Mac OS
   -a-o^1q,-L-!C FreeBSD .|
   1/2T<<O|P(R)EYENu|^3CUR@YENoCURaaYENoYEN?|b|C|L!A|OYENBYENiYENH^2IpthO"IYENI-aICURI
   3/4-: 3/4^1|L+-o^3I|h!A AU|^3'NNOTO|LYENX+-uCURU"ONOTO
   1/2O:-a-oCURaaYENo^3oAth-a-o!S: 1/4D-AD!"P:uYEN!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!G

     * |p|o^3](c)w FreeBSD -a-o|C|L|hCURu 1/2w 1/2A:^3B^2z 3/4^1!C

     * |p|o|w,E|C|L^1LAo
       3/4^1YENHCURAS:O^3B^2z-S(R)i-a-o|C|LCURuS:@!A
       YEN]NOTAS:a|NOT"`i-a-oCURaaYENoA`a'<<|"+-z-a-o|L-ai
       3/4-:NOTY+-oA'-a-o|C|L(R)ae|!uYEN!C

     * CURF,N|p|o|b+-z|C|L(R)EP:P:<<K|LYENXP:-o(c)I 1/4D-AD!C

     * |p|oS:QYENIS:OYENx^1q,-L-CURW-a-o|L-ai 3/4-:|C|L!C

     * |p|oS:QYENI-a 1/2+-u+-u|b-oo,oCURW-a-o|L-ai 3/4-:|C|L!C

     * |p|o+-+-"i|L-ai 3/4-:-a-oAAv!AYEN]NOTA"i|C|LCURuS:@-a-oAE(R)
       *CURjCURp!A YENHCURICUR-L-CUR^1^3\-S(c)w"IYENI-aI|C|LuYEN!C

     * |p|oDEGOCURU|L-ai
       3/4-:-a-o^2Ip,e(R)AE!AYENHCURI|U+-b,^1-a-o|L-ai
       3/4-:"IYENIP:q!C

     * |p|o,N"M|C|L(R)E^1J"`i-a-oDEGYAD!C

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!J

     * n|^3^3](c)w!B 1/2sA:P: kernel -a-oDEGoA|.S:(c)A (uU 8 ^3^1)!C

     --------------------------------------------------------------

9.2. CURP:^2D-

   n|b FreeBSD CURW"IYENI|L-ai 3/4-:!A+-z>>Yn^3](c)w|n Berkeley
   |ae|C|!|L-ai 3/4-:|C|L 1/2w 1/2A:"t^2I!ACURS-oUNOTDEG LPD |C|L
   1/2w 1/2A:"t^2I!A(c)I-aI'NYENsYENL LPD S:a!C ^3oNOTO FreeBSD 
   1/4D-.C,-a-o|L-ai
   3/4-:+-+-"i"t^2I!AYEN>>^3^1.|CURP:^2D-"A+-D-+-z|p|o^3](c)w LPD!C

   |p-aG+-zCURw,g^1i LPD (c)INOTO"a:YENL|C|L 1/2w 1/2A:"t^2I<<U:
   1/4o+-xCURF!A +-zYENiYENH-a 1/2+-u,o"`iDEGoYEN>>^3](c)w!C

   LPD +-+-"iuUYEND 3/4-:CURW|L-ai 3/4-:-a-oCUR@CURA!C
   YEN|t^3d^3o"C,CURuS:@!G

     * +-+-"iYEN>> 3/4-:CURI-oo,o|L-ai 3/4-:-a-o"IYENI!C

     * AAy"IYENI-aIYENiYENH|C|LCURaaYENo!ADEGeYENX-a-oCURaaYENo-oUNOTDEGCURuS:@!C

     * NOTDEG"CYENx|L-ai 3/4-:.C,^3AECUR@O|i|C!A A
       *S:K|hO"IYENI-aI|P(R)E"IYENI|PCUR@YENx|L-ai 3/4-:!C

     * |C|L header pages (CURS-oUNOTDEG banner or burst
       pages)!ACURe<<K"IYENI-aI|bYENX-E^1hCURCURS:a:"`i|UCURw|C|L-a-oCURaaYENo!C

     * S:a+-u|b|e|CDEGd-CURW-a-o|L-ai 3/4-:-a-o^3qDEGTDEGN
       1/4AE^3](c)w|n!C

     * S:QYENI-oo,oP:C,DEGe|C|LCURuS:@u^1S:OYENxYEND 3/4-:CURW-a-o
       LPD!C

     * DEGo|ae-SS:O-a-o^1LAou{|!+-N|C|LCURuS:@(R)ae|!CURAEYENHDEGt|XCUR-L-|P-a-o|C|L>>y"YEN(c)I|L-ai
       3/4-:!C

     * ^2Ip|L-ai 3/4-:-a-o"IYENI+-!-ap!C

   AC,YENN^3](c)wAE (/etc/printcap) YENHCURI^1LAou{|!-a-oADEGS:U!A
   +-zYENiYENHAAyCURj|h 1/4AE-a-o|L-ai 3/4-:DEGt|X LPD
   ^1F|"CURWzYENth^3!(c)I^3!YEN-:-a-oYEN\-`a!C

     --------------------------------------------------------------

  9.2.1. NOTDEGCURDEG>>o>>Yn"IYENI|hCURu 1/2w 1/2A:^3B^2z 3/4^1

   |p-aG+-z-a-o"t^2INOTOOCURH"IYENI!A CUR-L->>Yn+-+-"i|s"uAAv!B|C|L
   1/4D-ADP:(c)I-aI^2Ip"IYENI+-!-apuYENYEN\-`a(R)E!A
   +-zYENi-`a.|A:+-+-o<<U:(c)_(c)C,NOTDEGCURDEG>>oAU>>YnYENh-oTH^3oO|hCURu
   1/2w 1/2A:^3B^2z 3/4^1!C .iuMn-a 1/2+-u+-+-"i|L-ai
   3/4-:YENi|ae-a-o!A CUR-L-^1LuL 1/2 *|p|o+-zAUNOTO>>Yn|hCURu 1/2w
   1/2A:^3B^2z 3/4^1!A|]NOTDEG!G

     * LPD YENiYENH|bI'-o (background)
       |C|L!A+-zCUR-L->>Yn|b"-oAa:uYENCURaaYENoDEGe"`i|L-ai 3/4-:!C

     * LPD YENiYENH<<U:>>'AP|aYENI^1LAo 3/4^1 1/4WYEN[CURe'A /
       (R)EP:!(c)oP:-o(c)INOTOS:a-SS:O-a-oAE(R) *(R)ae|! (^1^3NOTO
       TeX DVI AE) A`a'<<|"|L-ai
       3/4-:NOTY+-oA'-a-o-a-o(R)ae|!!A+-zCUR-L->>YnCURaDEGEYENhDEGu^3o"C,"BAEJ!C

     * ^3\|hS:KP:O(c)IDEGO.~^3nAAe'-L-"N-a-o|C|LYEN\-`a^3q+-`^3-L-NOTO(c)M|hCURu
       1/2w 1/2A:^3B^2z 3/4^1. 3/4^3q!C ^3z^1L^3](c)w 1/2w
       1/2A:"t^2I!ACURa:'(c)+-z^2{|^3(c)INOTOS:Y+-Nn|w,E-a-o"a:YENL^3nAAe+-NAAU:+-oS:o(R)e(c)o:!C

     --------------------------------------------------------------

9.3. DEGoA|^3](c)w

   nYENI|L-ai 3/4-:.fDEGt LPD |hCURu 1/2w 1/2A:"t^2I!A+-z>>Yn|^3|L-ai
   3/4-:^3oOuwAAeYENHCURI LPD ^3o(R)M^3nAAe!C
   YEN>>CURaYENU'-L-"NCURF"aP:YENNOTq-a-o^3](c)w>>!(c)u!G

     * 3/4\AA-a A^2(c)o:|L-ai 3/4-:^3](c)w "O
       3/4C,^2ss|p|o^3s+-u|L-ai 3/4-:!BAAy|L-ai 3/4-:(c)M LPD .
       3/4^3qYENHCURI|C|L-ACURaa|rCURaaYENo!C

     * 3/4\AA-a P:iP:YEN|L-ai 3/4-:^3](c)w "O
       3/4C,^2ss|p|o|C|L|U-oO/-S(R)i(R)ae|!CURaaYENo!B|C|L-oP:!B-oo,o|C|L!B
       +-+-"i|L-ai 3/4-:AAvYENHCURI^2Ip"IYENI-aNOT-apuYEN!C

     --------------------------------------------------------------

  9.3.1. A^2(c)o:|L-ai 3/4-:^3](c)w

   YEN>>^3^1,`.|S:iP:D+-z|p|o^3](c)w|L-ai 3/4-:^3]^3AE(c)M LPD
   ^3nAAeYENH"IYENI|L-ai 3/4-:!A DEGoYEN>>+-D- 3/4C,CUR-o(R)e!G

     * uwAAe^3](c)w .|'-L-YENU:|p|o+-N|L-ai
       3/4-:+-uCURW^1q,-L--a-o^3s+-uDEGd-!C

     * ^3nAAe^3](c)w .|YENU: 1/2d|p|o 1/4g LPD  1/2w 1/2A:
       3/4^1^3](c)wAE (/etc/printcap)!C

   |p-aG+-znS:a|L-ai
   3/4-:^3](c)w+-u|NOT-oo,o|C|L,e(R)AE|OCUR-L-NOTOYEN>>
   3/4-:-oY-a-o,U:!A 1/2D-DEGN|O   |L-ai
   3/4-:CURI-oo,o,e(R)AEP:C,?eCURP:+-!C

   ^3oO^3^1,`Ao:uMYENsDEGu!S:A^2(c)o:|L-ai 3/4-:^3](c)w!"!A
   ^1e>>UCURWAUNOTO|^3AI 1/2AEAo/-a-o!C
   ^3IS:xAo/-a-o^3!YEN-:NOTOAAyS:A-a-o|L-ai 3/4-:(c)M^1q,-L-CURW-a-o
   LPD  1/2w 1/2A: 3/4^1-`aDEG-:YEN?+-`^1BS:@!C CUR@YEN^1|L-ai
   3/4-:YENiYENHYEN?+-`CURuS:@CURS:<<a!A
   ^1^3NOTO|L-oP:(c)INOTODEGu|C|L^2Ip^3o"C,P:iP:YEN-a-oYEN\-`a'NCUR-L-Ao/DEGu"`iCURF!C

     --------------------------------------------------------------

    9.3.1.1. uwAAe^3](c)w

   YEN>>^3^1,`DEGQ 1/2 *|U-oO/^3s+-u|L-ai 3/4-:"`i PC -a-oCURe|!!C
   ^3o,I.|'-L-"`iCUR-L-|P-oO/Ath-a-o^3s+-uDEGd-(c)M^3s+-u 1/2u!A
   YENHCURINOTDEGCURFAAy FreeBSD -`a(c)M|L-ai 3/4-:.
   3/4^3q+-zYENi-`a.|>>YnP:}+-O-a-o(R)O:CURssDEGN 1/4AEuYEN!C

   |p-aG+-zCURw,gS:a|L-ai 3/4-:+-uCURW^1q,-L-!A
   |OYENB|b"a:YENLS:@.~"t^2ICURW|^3|"YEN\|C|L^1L-a-o,U:!AYENiYENH-a
   1/2+-u,o|U: ^3nAAe^3](c)w!C

     --------------------------------------------------------------

      9.3.1.1.1. ^3s+-uDEGd-(c)M+-AE 1/2u

   YEN<<DEGaOCURH^1q,-L-|L-ai
   3/4-:CUR@-e"O>>!CUR-L-YENX^3oCURT-oO/NOTE+-!G

     * S:C,|C (Serial) NOTE+-!ACURS-oUNOTDEG RS-232 (c)I COM DEGd-!A
       YENI+-z^1q,-L-CURW-a-oS:C,|CDEGd-P:C,DEGe,e(R)AE"`i|L-ai
       3/4-:!C S:C,|CNOTE+-
       1/4s-ax-a-oNOTDEG^1q,-L-.~NOTE(c)O+-A:YENI!A (c)OYENH+-AE
       1/2u(R)e(c)o:"u+-o!An^3](c)w^3s 1/2u"ACUR-L-S:xAo/!C
       uM|OS:C,|CCURP:+-|^3(R)EO.|>>Yn"IYENI,u-SS:O-a-o+-AE 1/2u!A
       ^3o(R)EO'N|^3YENi-`a>>Yn^3](c)wCUR@"C,,uNOTDEG
       1/2AEAo/-a-o^3qDEGTDEGN 1/4AECURF!C CURj^3!YEN-: PC
       S:C,|CDEGd--a-oP:C,?e^3t<< *^3IDEG-aYENu"`i 115200 bps!A
       |]|^1.QnYENIS:C,|CDEGd-"O|C|LCURj^1INOTOCUR-L-CURA^1e>>U-a-o!C

     * "A|C (Parallel)
       NOTE+-S:QYENI^1q,-L--a-o"A|CDEGd-+-N,e(R)AEDEGe"`i|L-ai
       3/4-:!C "A|CDEGd-CURn RS-232
       S:C,|CDEGd-AUS:O:!ACUR]NOTOCUR@-oO/^1q,-L-.~NOTE+-`YENI-a-oNOTE+-!C
       ^3o-oO/NOTE+--a-o+-AE
       1/2u<<D+-`(R)e(c)o:"u+-o!A|yNOTO,uAo/YENICURaCURuYEN'^3y!C
       ^3q+-`"O>>!"A|CNOTE+-"A"S|^3CURDEG>>o^3qDEGTDEGN
       1/4AE>>Yn<<u:(c)w!A (c)OYENH^3](c)wDEG_"OP:W-AA(R)e(c)o:!C

       "A|CDEGd-NOTE+-|^3(R)EOCUR].|^3Q-oUNOTDEG !S:Centronics!"
       NOTE+-!A^3oNOTO|L-ai 3/4-:-a-o+-uAY-a-o|W-oU!C

     * USB NOTE+-!ACUR]'NNOTO^3qYENIS:C,|CP:
       *NOTy+-AE!AP:C,?e^3t^2vCURn"A|CNOTE+-(c)INOTO RS-232
       S:C,|CNOTE+-^3-L-"O+-oS:O:!A|OYENB USB +-AE
       1/2u^3ae-ACURS<<K(c)y!C ^1i|C|LCURuS:@|O"YEN!AUSB CURn RS-232
       S:C,|CDEGd-(c)INOTO"A|CDEGd-^3-L-"O+-o|n!A|yNOTO|b UNIX
       "t^2ICURW-a-oCURa:'(c)<< *,u(R)t!C AEP:R|P(R)E"a|^3 USB
       CURI"A|CDEGd-"a-oO/NOTE+--a-o|L-ai 3/4-:YENiYENHA *S:K+-
       1/4^3o-oO/DEGYAD!C

   CUR@-e|O"YEN!A"A|CNOTE+-YENu-`a'-L-"N^3ae|VP:C,?e (^1q,-L-|U:|L-ai
   3/4-:)!A|OnYENI USB CUR~-`a'-L-"NAu|V!C uM|O|b FreeBSD
   CURU!A"IYENI,u.s-a-o"A|CDEGd- (EPP (c)M ECP) YENHCURI|L-ai
   3/4-:!A|ADEGt|X"IYENI IEEE-1284 NOTU(R)e+-AE
   1/2uCUR]YENiYENHDEGu"`iAu|V. 3/4^3q!C

   ^1q,-L-(c)M|L-ai 3/4-:CURS:P:!AC,YENN"A|CDEGd-|aeP:iAu|V.
   3/4^3q-a-oCURe|!|^3"a-oO/!C
   ^2A:CUR@-oO/NOTO"IYENI-S>>s-a-o!B-`a(c)M-S(c)w|L-ai 3/4-:.
   3/4^3q-a-o FreeBSD |L-ai 3/4-:AAXDEGEu{|!!C ^3o-oO/CURe|!|b 1/4Q
   3/4YEN|L-ai 3/4-:CURW<<U:+-`"-L-!AYENI"O|^^3o/
   3/4YENCURo|sP:qYENHCURI"a:YENL-aNOT-oA,eDEGTuYEN!C
   ^2A:CURG-oO/CURe-akNOTOYENI PostScript!A|p-aG|L-ai
   3/4-:|^3CURa:'(c)-a-o,U:!C

   PostScript jobs are actually programs sent to the printer; they
   need not produce paper at all and may return results directly to
   the computer. PostScript also uses two-way communication to tell
   the computer about problems, such as errors in the PostScript
   program or paper jams. Your users may be appreciative of such
   information. Furthermore, the best way to do effective accounting
   with a PostScript printer requires two-way communication: you ask
   the printer for its page count (how many pages it has printed in
   its lifetime), then send the user's job, then ask again for its
   page count. Subtract the two values and you know how much paper to
   charge to the user.

     --------------------------------------------------------------

      9.3.1.1.2. Parallel Ports

   To hook up a printer using a parallel interface, connect the
   Centronics cable between the printer and the computer. The
   instructions that came with the printer, the computer, or both
   should give you complete guidance.

   Remember which parallel port you used on the computer. The first
   parallel port is ppc0 to FreeBSD; the second is ppc1, and so on.
   The printer device name uses the same scheme: /dev/lpt0 for the
   printer on the first parallel ports etc.

     --------------------------------------------------------------

      9.3.1.1.3. Serial Ports

   To hook up a printer using a serial interface, connect the proper
   serial cable between the printer and the computer. The
   instructions that came with the printer, the computer, or both
   should give you complete guidance.

   If you are unsure what the !S:proper serial cable!" is, you may
   wish to try one of the following alternatives:

     * A modem cable connects each pin of the connector on one end of
       the cable straight through to its corresponding pin of the
       connector on the other end. This type of cable is also known
       as a !S:DTE-to-DCE!" cable.

     * A null-modem cable connects some pins straight through, swaps
       others (send data to receive data, for example), and shorts
       some internally in each connector hood. This type of cable is
       also known as a !S:DTE-to-DTE!" cable.

     * A serial printer cable, required for some unusual printers, is
       like the null-modem cable, but sends some signals to their
       counterparts instead of being internally shorted.

   You should also set up the communications parameters for the
   printer, usually through front-panel controls or DIP switches on
   the printer. Choose the highest bps (bits per second, sometimes
   baud rate) that both your computer and the printer can support.
   Choose 7 or 8 data bits; none, even, or odd parity; and 1 or 2
   stop bits. Also choose a flow control protocol: either none, or
   XON/XOFF (also known as !S:in-band!" or !S:software!") flow
   control. Remember these settings for the software configuration
   that follows.

     --------------------------------------------------------------

    9.3.1.2. Software Setup

   This section describes the software setup necessary to print with
   the LPD spooling system in FreeBSD.

   Here is an outline of the steps involved:

    1. Configure your kernel, if necessary, for the port you are
       using for the printer; section Kernel Configuration tells you
       what you need to do.

    2. Set the communications mode for the parallel port, if you are
       using a parallel port; section Setting the Communication Mode
       for the Parallel Port gives details.

    3. Test if the operating system can send data to the printer.
       Section Checking Printer Communications gives some suggestions
       on how to do this.

    4. Set up LPD for the printer by modifying the file
       /etc/printcap. You will find out how to do this later in this
       chapter.

     --------------------------------------------------------------

      9.3.1.2.1. Kernel Configuration

   The operating system kernel is compiled to work with a specific
   set of devices. The serial or parallel interface for your printer
   is a part of that set. Therefore, it might be necessary to add
   support for an additional serial or parallel port if your kernel
   is not already configured for one.

   To find out if the kernel you are currently using supports a
   serial interface, type:

 # grep sioN /var/run/dmesg.boot

   Where N is the number of the serial port, starting from zero. If
   you see output similar to the following:

 sio2 at port 0x3e8-0x3ef irq 5 on isa
 sio2: type 16550A

   then the kernel supports the port.

   To find out if the kernel supports a parallel interface, type:

 # grep ppcN /var/run/dmesg.boot

   Where N is the number of the parallel port, starting from zero. If
   you see output similar to the following:

 ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
 ppc0: FIFO with 16/16/8 bytes threshold

   then the kernel supports the port.

   You might have to reconfigure your kernel in order for the
   operating system to recognize and use the parallel or serial port
   you are using for the printer.

   To add support for a serial port, see the section on kernel
   configuration. To add support for a parallel port, see that
   section and the section that follows.

     --------------------------------------------------------------

    9.3.1.3. Setting the Communication Mode for the Parallel Port

   When you are using the parallel interface, you can choose whether
   FreeBSD should use interrupt-driven or polled communication with
   the printer. The generic printer device driver (lpt(4)) on FreeBSD
   uses the ppbus(4) system, which controls the port chipset with the
   ppc(4) driver.

     * The interrupt-driven method is the default with the GENERIC
       kernel. With this method, the operating system uses an IRQ
       line to determine when the printer is ready for data.

     * The polled method directs the operating system to repeatedly
       ask the printer if it is ready for more data. When it responds
       ready, the kernel sends more data.

   The interrupt-driven method is usually somewhat faster but uses up
   a precious IRQ line. Some newer HP printers are claimed not to
   work correctly in interrupt mode, apparently due to some (not yet
   exactly understood) timing problem. These printers need polled
   mode. You should use whichever one works. Some printers will work
   in both modes, but are painfully slow in interrupt mode.

   You can set the communications mode in two ways: by configuring
   the kernel or by using the lptcontrol(8) program.

   To set the communications mode by configuring the kernel:

    1. Edit your kernel configuration file. Look for an ppc0 entry.
       If you are setting up the second parallel port, use ppc1
       instead. Use ppc2 for the third port, and so on.

          * If you want interrupt-driven mode, edit the following
            line:

 hint.ppc.0.irq="N"

            in the /boot/device.hints file and replace N with the
            right IRQ number. The kernel configuration file must also
            contain the ppc(4) driver:

 device ppc

          * If you want polled mode, remove in your
            /boot/device.hints file, the following line:

 hint.ppc.0.irq="N"

            In some cases, this is not enough to put the port in
            polled mode under FreeBSD. Most of time it comes from
            acpi(4) driver, this latter is able to probe and attach
            devices, and therefore, control the access mode to the
            printer port. You should check your acpi(4) configuration
            to correct this problem.

    2. Save the file. Then configure, build, and install the kernel,
       then reboot. See kernel configuration for more details.

   To set the communications mode with lptcontrol(8):

    1. Type:

 # lptcontrol -i -d /dev/lptN

       to set interrupt-driven mode for lptN.

    2. Type:

 # lptcontrol -p -d /dev/lptN

       to set polled-mode for lptN.

   You could put these commands in your /etc/rc.local file to set the
   mode each time your system boots. See lptcontrol(8) for more
   information.

     --------------------------------------------------------------

    9.3.1.4. Checking Printer Communications

   Before proceeding to configure the spooling system, you should
   make sure the operating system can successfully send data to your
   printer. It is a lot easier to debug printer communication and the
   spooling system separately.

   To test the printer, we will send some text to it. For printers
   that can immediately print characters sent to them, the program
   lptest(1) is perfect: it generates all 96 printable ASCII
   characters in 96 lines.

   For a PostScript (or other language-based) printer, we will need a
   more sophisticated test. A small PostScript program, such as the
   following, will suffice:

 %!PS
 100 100 moveto 300 300 lineto stroke
 310 310 moveto /Helvetica findfont 12 scalefont setfont
 (Is this thing working?) show
 showpage

   The above PostScript code can be placed into a file and used as
   shown in the examples appearing in the following sections.

     -a`: When this document refers to a printer language, it is
     assuming a language like PostScript, and not Hewlett Packard's
     PCL. Although PCL has great functionality, you can intermingle
     plain text with its escape sequences. PostScript cannot directly
     print plain text, and that is the kind of printer language for
     which we must make special accommodations.

     --------------------------------------------------------------

      9.3.1.4.1. Checking a Parallel Printer

   This section tells you how to check if FreeBSD can communicate
   with a printer connected to a parallel port.

   To test a printer on a parallel port:

    1. Become root with su(1).

    2. Send data to the printer.

          * If the printer can print plain text, then use lptest(1).
            Type:

 # lptest > /dev/lptN

            Where N is the number of the parallel port, starting from
            zero.

          * If the printer understands PostScript or other printer
            language, then send a small program to the printer. Type:

 # cat > /dev/lptN

            Then, line by line, type the program carefully as you
            cannot edit a line once you have pressed RETURN or ENTER.
            When you have finished entering the program, press
            CONTROL+D, or whatever your end of file key is.

            Alternatively, you can put the program in a file and
            type:

 # cat file > /dev/lptN

            Where file is the name of the file containing the program
            you want to send to the printer.

   You should see something print. Do not worry if the text does not
   look right; we will fix such things later.

     --------------------------------------------------------------

      9.3.1.4.2. Checking a Serial Printer

   This section tells you how to check if FreeBSD can communicate
   with a printer on a serial port.

   To test a printer on a serial port:

    1. Become root with su(1).

    2. Edit the file /etc/remote. Add the following entry:

 printer:dv=/dev/port:br#bps-rate:pa=parity

       Where port is the device entry for the serial port (ttyd0,
       ttyd1, etc.), bps-rate is the bits-per-second rate at which
       the printer communicates, and parity is the parity required by
       the printer (either even, odd, none, or zero).

       Here is a sample entry for a printer connected via a serial
       line to the third serial port at 19200 bps with no parity:

 printer:dv=/dev/ttyd2:br#19200:pa=none

    3. Connect to the printer with tip(1). Type:

 # tip printer

       If this step does not work, edit the file /etc/remote again
       and try using /dev/cuaaN instead of /dev/ttydN.

    4. Send data to the printer.

          * If the printer can print plain text, then use lptest(1).
            Type:

 % $lptest

          * If the printer understands PostScript or other printer
            language, then send a small program to the printer. Type
            the program, line by line, very carefully as backspacing
            or other editing keys may be significant to the printer.
            You may also need to type a special end-of-file key for
            the printer so it knows it received the whole program.
            For PostScript printers, press CONTROL+D.

            Alternatively, you can put the program in a file and
            type:

 % >file

            Where file is the name of the file containing the
            program. After tip(1) sends the file, press any required
            end-of-file key.

   You should see something print. Do not worry if the text does not
   look right; we will fix that later.

     --------------------------------------------------------------

    9.3.1.5. Enabling the Spooler: the /etc/printcap File

   At this point, your printer should be hooked up, your kernel
   configured to communicate with it (if necessary), and you have
   been able to send some simple data to the printer. Now, we are
   ready to configure LPD to control access to your printer.

   You configure LPD by editing the file /etc/printcap. The LPD
   spooling system reads this file each time the spooler is used, so
   updates to the file take immediate effect.

   The format of the printcap(5) file is straightforward. Use your
   favorite text editor to make changes to /etc/printcap. The format
   is identical to other capability files like
   /usr/share/misc/termcap and /etc/remote. For complete information
   about the format, see the cgetent(3).

   The simple spooler configuration consists of the following steps:

    1. Pick a name (and a few convenient aliases) for the printer,
       and put them in the /etc/printcap file; see the Naming the
       Printer section for more information on naming.

    2. Turn off header pages (which are on by default) by inserting
       the sh capability; see the Suppressing Header Pages section
       for more information.

    3. Make a spooling directory, and specify its location with the
       sd capability; see the Making the Spooling Directory section
       for more information.

    4. Set the /dev entry to use for the printer, and note it in
       /etc/printcap with the lp capability; see the Identifying the
       Printer Device for more information. Also, if the printer is
       on a serial port, set up the communication parameters with the
       ms# capability which is discussed in the Configuring Spooler
       Communications Parameters section.

    5. Install a plain text input filter; see the Installing the Text
       Filter section for details.

    6. Test the setup by printing something with the lpr(1) command.
       More details are available in the Trying It Out and
       Troubleshooting sections.

     -a`: Language-based printers, such as PostScript printers,
     cannot directly print plain text. The simple setup outlined
     above and described in the following sections assumes that if
     you are installing such a printer you will print only files that
     the printer can understand.

   Users often expect that they can print plain text to any of the
   printers installed on your system. Programs that interface to LPD
   to do their printing usually make the same assumption. If you are
   installing such a printer and want to be able to print jobs in the
   printer language and print plain text jobs, you are strongly urged
   to add an additional step to the simple setup outlined above:
   install an automatic plain-text-to-PostScript (or other printer
   language) conversion program. The section entitled Accommodating
   Plain Text Jobs on PostScript Printers tells how to do this.

     --------------------------------------------------------------

      9.3.1.5.1. Naming the Printer

   The first (easy) step is to pick a name for your printer. It
   really does not matter whether you choose functional or whimsical
   names since you can also provide a number of aliases for the
   printer.

   At least one of the printers specified in the /etc/printcap should
   have the alias lp. This is the default printer's name. If users do
   not have the PRINTER environment variable nor specify a printer
   name on the command line of any of the LPD commands, then lp will
   be the default printer they get to use.

   Also, it is common practice to make the last alias for a printer
   be a full description of the printer, including make and model.

   Once you have picked a name and some common aliases, put them in
   the /etc/printcap file. The name of the printer should start in
   the leftmost column. Separate each alias with a vertical bar and
   put a colon after the last alias.

   In the following example, we start with a skeletal /etc/printcap
   that defines two printers (a Diablo 630 line printer and a
   Panasonic KX-P4455 PostScript laser printer):

 #
 #  /etc/printcap for host rose
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:

 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:

   In this example, the first printer is named rattan and has as
   aliases line, diablo, lp, and Diablo 630 Line Printer. Since it
   has the alias lp, it is also the default printer. The second is
   named bamboo, and has as aliases ps, PS, S, panasonic, and
   Panasonic KX-P4455 PostScript v51.4.

     --------------------------------------------------------------

      9.3.1.5.2. Suppressing Header Pages

   The LPD spooling system will by default print a header page for
   each job. The header page contains the user name who requested the
   job, the host from which the job came, and the name of the job, in
   nice large letters. Unfortunately, all this extra text gets in the
   way of debugging the simple printer setup, so we will suppress
   header pages.

   To suppress header pages, add the sh capability to the entry for
   the printer in /etc/printcap. Here is an example /etc/printcap
   with sh added:

 #
 #  /etc/printcap for host rose - no header pages anywhere
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:

 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:

   Note how we used the correct format: the first line starts in the
   leftmost column, and subsequent lines are indented. Every line in
   an entry except the last ends in a backslash character.

     --------------------------------------------------------------

      9.3.1.5.3. Making the Spooling Directory

   The next step in the simple spooler setup is to make a spooling
   directory, a directory where print jobs reside until they are
   printed, and where a number of other spooler support files live.

   Because of the variable nature of spooling directories, it is
   customary to put these directories under /var/spool. It is not
   necessary to backup the contents of spooling directories, either.
   Recreating them is as simple as running mkdir(1).

   It is also customary to make the directory with a name that is
   identical to the name of the printer, as shown below:

 # mkdir /var/spool/printer-name

   However, if you have a lot of printers on your network, you might
   want to put the spooling directories under a single directory that
   you reserve just for printing with LPD. We will do this for our
   two example printers rattan and bamboo:

 # mkdir /var/spool/lpd
 # mkdir /var/spool/lpd/rattan
 # mkdir /var/spool/lpd/bamboo

     -a`: If you are concerned about the privacy of jobs that users
     print, you might want to protect the spooling directory so it is
     not publicly accessible. Spooling directories should be owned
     and be readable, writable, and searchable by user daemon and
     group daemon, and no one else. We will do this for our example
     printers:

 # chown daemon:daemon /var/spool/lpd/rattan
 # chown daemon:daemon /var/spool/lpd/bamboo
 # chmod 770 /var/spool/lpd/rattan
 # chmod 770 /var/spool/lpd/bamboo

   Finally, you need to tell LPD about these directories using the
   /etc/printcap file. You specify the pathname of the spooling
   directory with the sd capability:

 #
 #  /etc/printcap for host rose - added spooling directories
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:

 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:

   Note that the name of the printer starts in the first column but
   all other entries describing the printer should be indented and
   each line end escaped with a backslash.

   If you do not specify a spooling directory with sd, the spooling
   system will use /var/spool/lpd as a default.

     --------------------------------------------------------------

      9.3.1.5.4. Identifying the Printer Device

   In the Entries for the Ports section, we identified which entry in
   the /dev directory FreeBSD will use to communicate with the
   printer. Now, we tell LPD that information. When the spooling
   system has a job to print, it will open the specified device on
   behalf of the filter program (which is responsible for passing
   data to the printer).

   List the /dev entry pathname in the /etc/printcap file using the
   lp capability.

   In our running example, let us assume that rattan is on the first
   parallel port, and bamboo is on a sixth serial port; here are the
   additions to /etc/printcap:

 #
 #  /etc/printcap for host rose - identified what devices to use
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:

 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:\
         :lp=/dev/ttyd5:

   If you do not specify the lp capability for a printer in your
   /etc/printcap file, LPD uses /dev/lp as a default. /dev/lp
   currently does not exist in FreeBSD.

   If the printer you are installing is connected to a parallel port,
   skip to the section entitled, Installing the Text Filter.
   Otherwise, be sure to follow the instructions in the next section.

     --------------------------------------------------------------

      9.3.1.5.5. Configuring Spooler Communication Parameters

   For printers on serial ports, LPD can set up the bps rate, parity,
   and other serial communication parameters on behalf of the filter
   program that sends data to the printer. This is advantageous
   since:

     * It lets you try different communication parameters by simply
       editing the /etc/printcap file; you do not have to recompile
       the filter program.

     * It enables the spooling system to use the same filter program
       for multiple printers which may have different serial
       communication settings.

   The following /etc/printcap capabilities control serial
   communication parameters of the device listed in the lp
   capability:

   br#bps-rate

           Sets the communications speed of the device to bps-rate,
           where bps-rate can be 50, 75, 110, 134, 150, 200, 300,
           600, 1200, 1800, 2400, 4800, 9600, 19200, 38400, 57600, or
           115200 bits-per-second.

   ms#stty-mode

           Sets the options for the terminal device after opening the
           device. stty(1) explains the available options.

   When LPD opens the device specified by the lp capability, it sets
   the characteristics of the device to those specified with the ms#
   capability. Of particular interest will be the parenb, parodd,
   cs5, cs6, cs7, cs8, cstopb, crtscts, and ixon modes, which are
   explained in the stty(1) manual page.

   Let us add to our example printer on the sixth serial port. We
   will set the bps rate to 38400. For the mode, we will set no
   parity with -parenb, 8-bit characters with cs8, no modem control
   with clocal and hardware flow control with crtscts:

 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:

     --------------------------------------------------------------

      9.3.1.5.6. Installing the Text Filter

   We are now ready to tell LPD what text filter to use to send jobs
   to the printer. A text filter, also known as an input filter, is a
   program that LPD runs when it has a job to print. When LPD runs
   the text filter for a printer, it sets the filter's standard input
   to the job to print, and its standard output to the printer device
   specified with the lp capability. The filter is expected to read
   the job from standard input, perform any necessary translation for
   the printer, and write the results to standard output, which will
   get printed. For more information on the text filter, see the
   Filters section.

   For our simple printer setup, the text filter can be a small shell
   script that just executes /bin/cat to send the job to the printer.
   FreeBSD comes with another filter called lpf that handles
   backspacing and underlining for printers that might not deal with
   such character streams well. And, of course, you can use any other
   filter program you want. The filter lpf is described in detail in
   section entitled lpf: a Text Filter.

   First, let us make the shell script /usr/local/libexec/if-simple
   be a simple text filter. Put the following text into that file
   with your favorite text editor:

 #!/bin/sh
 #
 # if-simple - Simple text input filter for lpd
 # Installed in /usr/local/libexec/if-simple
 #
 # Simply copies stdin to stdout.  Ignores all filter arguments.

 /bin/cat && exit 0
 exit 2

   Make the file executable:

 # chmod 555 /usr/local/libexec/if-simple

   And then tell LPD to use it by specifying it with the if
   capability in /etc/printcap. We will add it to the two printers we
   have so far in the example /etc/printcap:

 #
 #  /etc/printcap for host rose - added text filter
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\ :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:

 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:\
         :if=/usr/local/libexec/if-simple:

     -a`: A copy of the if-simple script can be found in the
     /usr/share/examples/printing directory.

     --------------------------------------------------------------

      9.3.1.5.7. Turn on LPD

   lpd(8) is run from /etc/rc, controlled by the lpd_enable variable.
   This variable defaults to NO. If you have not done so already, add
   the line:

 lpd_enable="YES"

   to /etc/rc.conf, and then either restart your machine, or just run
   lpd(8).

 # lpd

     --------------------------------------------------------------

      9.3.1.5.8. Trying It Out

   You have reached the end of the simple LPD setup. Unfortunately,
   congratulations are not quite yet in order, since we still have to
   test the setup and correct any problems. To test the setup, try
   printing something. To print with the LPD system, you use the
   command lpr(1), which submits a job for printing.

   You can combine lpr(1) with the lptest(1) program, introduced in
   section Checking Printer Communications to generate some test
   text.

   To test the simple LPD setup:

   Type:

 # lptest 20 5 | lpr -Pprinter-name

   Where printer-name is a the name of a printer (or an alias)
   specified in /etc/printcap. To test the default printer, type
   lpr(1) without any -P argument. Again, if you are testing a
   printer that expects PostScript, send a PostScript program in that
   language instead of using lptest(1). You can do so by putting the
   program in a file and typing lpr file.

   For a PostScript printer, you should get the results of the
   program. If you are using lptest(1), then your results should look
   like the following:

 !"#$%&'()*+,-./01234
 "#$%&'()*+,-./012345
 #$%&'()*+,-./0123456
 $%&'()*+,-./01234567
 %&'()*+,-./012345678

   To further test the printer, try downloading larger programs (for
   language-based printers) or running lptest(1) with different
   arguments. For example, lptest 80 60 will produce 60 lines of 80
   characters each.

   If the printer did not work, see the Troubleshooting section.

     --------------------------------------------------------------

9.4. Advanced Printer Setup

   This section describes filters for printing specially formatted
   files, header pages, printing across networks, and restricting and
   accounting for printer usage.

     --------------------------------------------------------------

  9.4.1. Filters

   Although LPD handles network protocols, queuing, access control,
   and other aspects of printing, most of the real work happens in
   the filters. Filters are programs that communicate with the
   printer and handle its device dependencies and special
   requirements. In the simple printer setup, we installed a plain
   text filter!X!Xan extremely simple one that should work with most
   printers (section Installing the Text Filter).

   However, in order to take advantage of format conversion, printer
   accounting, specific printer quirks, and so on, you should
   understand how filters work. It will ultimately be the filter's
   responsibility to handle these aspects. And the bad news is that
   most of the time you have to provide filters yourself. The good
   news is that many are generally available; when they are not, they
   are usually easy to write.

   Also, FreeBSD comes with one, /usr/libexec/lpr/lpf, that works
   with many printers that can print plain text. (It handles
   backspacing and tabs in the file, and does accounting, but that is
   about all it does.) There are also several filters and filter
   components in the FreeBSD Ports Collection.

   Here is what you will find in this section:

     * Section How Filters Work, tries to give an overview of a
       filter's role in the printing process. You should read this
       section to get an understanding of what is happening !S:under
       the hood!" when LPD uses filters. This knowledge could help
       you anticipate and debug problems you might encounter as you
       install more and more filters on each of your printers.

     * LPD expects every printer to be able to print plain text by
       default. This presents a problem for PostScript (or other
       language-based printers) which cannot directly print plain
       text. Section Accommodating Plain Text Jobs on PostScript
       Printers tells you what you should do to overcome this
       problem. You should read this section if you have a PostScript
       printer.

     * PostScript is a popular output format for many programs. Some
       people even write PostScript code directly. Unfortunately,
       PostScript printers are expensive. Section Simulating
       PostScript on Non PostScript Printers tells how you can
       further modify a printer's text filter to accept and print
       PostScript data on a non PostScript printer. You should read
       this section if you do not have a PostScript printer.

     * Section Conversion Filters tells about a way you can automate
       the conversion of specific file formats, such as graphic or
       typesetting data, into formats your printer can understand.
       After reading this section, you should be able to set up your
       printers such that users can type lpr -t to print troff data,
       or lpr -d to print TeX DVI data, or lpr -v to print raster
       image data, and so forth. I recommend reading this section.

     * Section Output Filters tells all about a not often used
       feature of LPD: output filters. Unless you are printing header
       pages (see Header Pages), you can probably skip that section
       altogether.

     * Section lpf: a Text Filter describes lpf, a fairly complete if
       simple text filter for line printers (and laser printers that
       act like line printers) that comes with FreeBSD. If you need a
       quick way to get printer accounting working for plain text, or
       if you have a printer which emits smoke when it sees backspace
       characters, you should definitely consider lpf.

     -a`: A copy of the various scripts described below can be found
     in the /usr/share/examples/printing directory.

     --------------------------------------------------------------

    9.4.1.1. How Filters Work

   As mentioned before, a filter is an executable program started by
   LPD to handle the device-dependent part of communicating with the
   printer.

   When LPD wants to print a file in a job, it starts a filter
   program. It sets the filter's standard input to the file to print,
   its standard output to the printer, and its standard error to the
   error logging file (specified in the lf capability in
   /etc/printcap, or /dev/console by default).

   Which filter LPD starts and the filter's arguments depend on what
   is listed in the /etc/printcap file and what arguments the user
   specified for the job on the lpr(1) command line. For example, if
   the user typed lpr -t, LPD would start the troff filter, listed in
   the tf capability for the destination printer. If the user wanted
   to print plain text, it would start the if filter (this is mostly
   true: see Output Filters for details).

   There are three kinds of filters you can specify in /etc/printcap:

     * The text filter, confusingly called the input filter in LPD
       documentation, handles regular text printing. Think of it as
       the default filter. LPD expects every printer to be able to
       print plain text by default, and it is the text filter's job
       to make sure backspaces, tabs, or other special characters do
       not confuse the printer. If you are in an environment where
       you have to account for printer usage, the text filter must
       also account for pages printed, usually by counting the number
       of lines printed and comparing that to the number of lines per
       page the printer supports. The text filter is started with the
       following argument list:

       filter-name [-c] -wwidth -llength -iindent -n login -h host
       acct-file

       where

            -c

                    appears if the job is submitted with lpr -l

            width

                    is the value from the pw (page width) capability
                    specified in /etc/printcap, default 132

            length

                    is the value from the pl (page length)
                    capability, default 66

            indent

                    is the amount of the indentation from lpr -i,
                    default 0

            login

                    is the account name of the user printing the file

            host

                    is the host name from which the job was submitted

            acct-file

                    is the name of the accounting file from the af
                    capability.

     * A conversion filter converts a specific file format into one
       the printer can render onto paper. For example, ditroff
       typesetting data cannot be directly printed, but you can
       install a conversion filter for ditroff files to convert the
       ditroff data into a form the printer can digest and print.
       Section Conversion Filters tells all about them. Conversion
       filters also need to do accounting, if you need printer
       accounting. Conversion filters are started with the following
       arguments:

       filter-name -xpixel-width -ypixel-height -n login -h host
       acct-file

       where pixel-width is the value from the px capability (default
       0) and pixel-height is the value from the py capability
       (default 0).
     * The output filter is used only if there is no text filter, or
       if header pages are enabled. In my experience, output filters
       are rarely used. Section Output Filters describe them. There
       are only two arguments to an output filter:

       filter-name -wwidth -llength

       which are identical to the text filters -w and -l arguments.

   Filters should also exit with the following exit status:

   exit 0

           If the filter printed the file successfully.

   exit 1

           If the filter failed to print the file but wants LPD to
           try to print the file again. LPD will restart a filter if
           it exits with this status.

   exit 2

           If the filter failed to print the file and does not want
           LPD to try again. LPD will throw out the file.

   The text filter that comes with the FreeBSD release,
   /usr/libexec/lpr/lpf, takes advantage of the page width and length
   arguments to determine when to send a form feed and how to account
   for printer usage. It uses the login, host, and accounting file
   arguments to make the accounting entries.

   If you are shopping for filters, see if they are LPD-compatible.
   If they are, they must support the argument lists described above.
   If you plan on writing filters for general use, then have them
   support the same argument lists and exit codes.

     --------------------------------------------------------------

    9.4.1.2. Accommodating Plain Text Jobs on PostScript(R) Printers

   If you are the only user of your computer and PostScript (or other
   language-based) printer, and you promise to never send plain text
   to your printer and to never use features of various programs that
   will want to send plain text to your printer, then you do not need
   to worry about this section at all.

   But, if you would like to send both PostScript and plain text jobs
   to the printer, then you are urged to augment your printer setup.
   To do so, we have the text filter detect if the arriving job is
   plain text or PostScript. All PostScript jobs must start with %!
   (for other printer languages, see your printer documentation). If
   those are the first two characters in the job, we have PostScript,
   and can pass the rest of the job directly. If those are not the
   first two characters in the file, then the filter will convert the
   text into PostScript and print the result.

   How do we do this?

   If you have got a serial printer, a great way to do it is to
   install lprps. lprps is a PostScript printer filter which performs
   two-way communication with the printer. It updates the printer's
   status file with verbose information from the printer, so users
   and administrators can see exactly what the state of the printer
   is (such as !S:toner low!" or !S:paper jam!"). But more
   importantly, it includes a program called psif which detects
   whether the incoming job is plain text and calls textps (another
   program that comes with lprps) to convert it to PostScript. It
   then uses lprps to send the job to the printer.

   lprps is part of the FreeBSD Ports Collection (see The Ports
   Collection). You can fetch, build and install it yourself, of
   course. After installing lprps, just specify the pathname to the
   psif program that is part of lprps. If you installed lprps from
   the Ports Collection, use the following in the serial PostScript
   printer's entry in /etc/printcap:

 :if=/usr/local/libexec/psif:

   You should also specify the rw capability; that tells LPD to open
   the printer in read-write mode.

   If you have a parallel PostScript printer (and therefore cannot
   use two-way communication with the printer, which lprps needs),
   you can use the following shell script as the text filter:

 #!/bin/sh
 #
 #  psif - Print PostScript or plain text on a PostScript printer
 #  Script version; NOT the version that comes with lprps
 #  Installed in /usr/local/libexec/psif
 #

 IFS="" read -r first_line
 first_two_chars=`expr "$first_line" : '\(..\)'`

 if [ "$first_two_chars" = "%!" ]; then
     #
     #  PostScript job, print it.
     #
     echo "$first_line" && cat && printf "\004" && exit 0
     exit 2
 else
     #
     #  Plain text, convert it, then print it.
     #
     ( echo "$first_line"; cat ) | /usr/local/bin/textps && printf "\004" && exit 0
     exit 2
 fi

   In the above script, textps is a program we installed separately
   to convert plain text to PostScript. You can use any
   text-to-PostScript program you wish. The FreeBSD Ports Collection
   (see The Ports Collection) includes a full featured
   text-to-PostScript program called a2ps that you might want to
   investigate.

     --------------------------------------------------------------

    9.4.1.3. Simulating PostScript on Non PostScript Printers

   PostScript is the de facto standard for high quality typesetting
   and printing. PostScript is, however, an expensive standard.
   Thankfully, Aladdin Enterprises has a free PostScript work-alike
   called Ghostscript that runs with FreeBSD. Ghostscript can read
   most PostScript files and can render their pages onto a variety of
   devices, including many brands of non-PostScript printers. By
   installing Ghostscript and using a special text filter for your
   printer, you can make your non PostScript printer act like a real
   PostScript printer.

   Ghostscript is in the FreeBSD Ports Collection, if you would like
   to install it from there. You can fetch, build, and install it
   quite easily yourself, as well.

   To simulate PostScript, we have the text filter detect if it is
   printing a PostScript file. If it is not, then the filter will
   pass the file directly to the printer; otherwise, it will use
   Ghostscript to first convert the file into a format the printer
   will understand.

   Here is an example: the following script is a text filter for
   Hewlett Packard DeskJet 500 printers. For other printers,
   substitute the -sDEVICE argument to the gs (Ghostscript) command.
   (Type gs -h to get a list of devices the current installation of
   Ghostscript supports.)

 #!/bin/sh
 #
 #  ifhp - Print Ghostscript-simulated PostScript on a DeskJet 500
 #  Installed in /usr/local/libexec/ifhp

 #
 #  Treat LF as CR+LF (to avoid the "staircase effect" on HP/PCL
 #  printers):
 #
 printf "\033&k2G" || exit 2

 #
 #  Read first two characters of the file
 #
 IFS="" read -r first_line
 first_two_chars=`expr "$first_line" : '\(..\)'`

 if [ "$first_two_chars" = "%!" ]; then
     #
     #  It is PostScript; use Ghostscript to scan-convert and print it.
     #
     /usr/local/bin/gs -dSAFER -dNOPAUSE -q -sDEVICE=djet500 \
       -sOutputFile=- - && exit 0
 else
     #
     #  Plain text or HP/PCL, so just print it directly; print a form feed
     #  at the end to eject the last page.
     #
     echo "$first_line" && cat && printf "\033&l0H" &&
 exit 0
 fi

 exit 2

   Finally, you need to notify LPD of the filter via the if
   capability:

 :if=/usr/local/libexec/ifhp:

   That is it. You can type lpr plain.text and lpr whatever.ps and
   both should print successfully.

     --------------------------------------------------------------

    9.4.1.4. Conversion Filters

   After completing the simple setup described in Simple Printer
   Setup, the first thing you will probably want to do is install
   conversion filters for your favorite file formats (besides plain
   ASCII text).

     --------------------------------------------------------------

      9.4.1.4.1. Why Install Conversion Filters?

   Conversion filters make printing various kinds of files easy. As
   an example, suppose we do a lot of work with the TeX typesetting
   system, and we have a PostScript printer. Every time we generate a
   DVI file from TeX, we cannot print it directly until we convert
   the DVI file into PostScript. The command sequence goes like this:

 % dvips seaweed-analysis.dvi
 % lpr seaweed-analysis.ps

   By installing a conversion filter for DVI files, we can skip the
   hand conversion step each time by having LPD do it for us. Now,
   each time we get a DVI file, we are just one step away from
   printing it:

 % lpr -d seaweed-analysis.dvi

   We got LPD to do the DVI file conversion for us by specifying the
   -d option. Section Formatting and Conversion Options lists the
   conversion options.

   For each of the conversion options you want a printer to support,
   install a conversion filter and specify its pathname in
   /etc/printcap. A conversion filter is like the text filter for the
   simple printer setup (see section Installing the Text Filter)
   except that instead of printing plain text, the filter converts
   the file into a format the printer can understand.

     --------------------------------------------------------------

      9.4.1.4.2. Which Conversion Filters Should I Install?

   You should install the conversion filters you expect to use. If
   you print a lot of DVI data, then a DVI conversion filter is in
   order. If you have got plenty of troff to print out, then you
   probably want a troff filter.

   The following table summarizes the filters that LPD works with,
   their capability entries for the /etc/printcap file, and how to
   invoke them with the lpr command:

       File type       /etc/printcap capability       lpr option      
   cifplot           cf                           -c                  
   DVI               df                           -d                  
   plot              gf                           -g                  
   ditroff           nf                           -n                  
   FORTRAN text      rf                           -f                  
   troff             tf                           -f                  
   raster            vf                           -v                  
   plain text        if                           none, -p, or -l     

   In our example, using lpr -d means the printer needs a df
   capability in its entry in /etc/printcap.

   Despite what others might contend, formats like FORTRAN text and
   plot are probably obsolete. At your site, you can give new
   meanings to these or any of the formatting options just by
   installing custom filters. For example, suppose you would like to
   directly print Printerleaf files (files from the Interleaf desktop
   publishing program), but will never print plot files. You could
   install a Printerleaf conversion filter under the gf capability
   and then educate your users that lpr -g mean !S:print Printerleaf
   files.!"

     --------------------------------------------------------------

      9.4.1.4.3. Installing Conversion Filters

   Since conversion filters are programs you install outside of the
   base FreeBSD installation, they should probably go under
   /usr/local. The directory /usr/local/libexec is a popular
   location, since they are specialized programs that only LPD will
   run; regular users should not ever need to run them.

   To enable a conversion filter, specify its pathname under the
   appropriate capability for the destination printer in
   /etc/printcap.

   In our example, we will add the DVI conversion filter to the entry
   for the printer named bamboo. Here is the example /etc/printcap
   file again, with the new df capability for the printer bamboo.

 #
 #  /etc/printcap for host rose - added df filter for bamboo
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:

 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:\
         :if=/usr/local/libexec/psif:\
         :df=/usr/local/libexec/psdf:

   The DVI filter is a shell script named /usr/local/libexec/psdf.
   Here is that script:

 #!/bin/sh
 #
 #  psdf - DVI to PostScript printer filter
 #  Installed in /usr/local/libexec/psdf
 #
 # Invoked by lpd when user runs lpr -d
 #
 exec /usr/local/bin/dvips -f | /usr/local/libexec/lprps "$@"

   This script runs dvips in filter mode (the -f argument) on
   standard input, which is the job to print. It then starts the
   PostScript printer filter lprps (see section Accommodating Plain
   Text Jobs on PostScript Printers) with the arguments LPD passed to
   this script. lprps will use those arguments to account for the
   pages printed.

     --------------------------------------------------------------

      9.4.1.4.4. More Conversion Filter Examples

   Since there is no fixed set of steps to install conversion
   filters, let me instead provide more examples. Use these as
   guidance to making your own filters. Use them directly, if
   appropriate.

   This example script is a raster (well, GIF file, actually)
   conversion filter for a Hewlett Packard LaserJet III-Si printer:

 #!/bin/sh
 #
 #  hpvf - Convert GIF files into HP/PCL, then print
 #  Installed in /usr/local/libexec/hpvf

 PATH=/usr/X11R6/bin:$PATH; export PATH
 giftopnm | ppmtopgm | pgmtopbm | pbmtolj -resolution 300 \
     && exit 0 \
     || exit 2

   It works by converting the GIF file into a portable anymap,
   converting that into a portable graymap, converting that into a
   portable bitmap, and converting that into LaserJet/PCL-compatible
   data.

   Here is the /etc/printcap file with an entry for a printer using
   the above filter:

 #
 #  /etc/printcap for host orchid
 #
 teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
         :lp=/dev/lpt0:sh:sd=/var/spool/lpd/teak:mx#0:\
         :if=/usr/local/libexec/hpif:\
         :vf=/usr/local/libexec/hpvf:

   The following script is a conversion filter for troff data from
   the groff typesetting system for the PostScript printer named
   bamboo:

 #!/bin/sh
 #
 #  pstf - Convert groff's troff data into PS, then print.
 #  Installed in /usr/local/libexec/pstf
 #
 exec grops | /usr/local/libexec/lprps "$@"

   The above script makes use of lprps again to handle the
   communication with the printer. If the printer were on a parallel
   port, we would use this script instead:

 #!/bin/sh
 #
 #  pstf - Convert groff's troff data into PS, then print.
 #  Installed in /usr/local/libexec/pstf
 #
 exec grops

   That is it. Here is the entry we need to add to /etc/printcap to
   enable the filter:

 :tf=/usr/local/libexec/pstf:

   Here is an example that might make old hands at FORTRAN blush. It
   is a FORTRAN-text filter for any printer that can directly print
   plain text. We will install it for the printer teak:

 #!/bin/sh
 #
 # hprf - FORTRAN text filter for LaserJet 3si:
 # Installed in /usr/local/libexec/hprf
 #

 printf "\033&k2G" && fpr && printf "\033&l0H" &&
  exit 0
 exit 2

   And we will add this line to the /etc/printcap for the printer
   teak to enable this filter:

 :rf=/usr/local/libexec/hprf:

   Here is one final, somewhat complex example. We will add a DVI
   filter to the LaserJet printer teak introduced earlier. First, the
   easy part: updating /etc/printcap with the location of the DVI
   filter:

 :df=/usr/local/libexec/hpdf:

   Now, for the hard part: making the filter. For that, we need a
   DVI-to-LaserJet/PCL conversion program. The FreeBSD Ports
   Collection (see The Ports Collection) has one: dvi2xx is the name
   of the package. Installing this package gives us the program we
   need, dvilj2p, which converts DVI into LaserJet IIp, LaserJet III,
   and LaserJet 2000 compatible codes.

   dvilj2p makes the filter hpdf quite complex since dvilj2p cannot
   read from standard input. It wants to work with a filename. What
   is worse, the filename has to end in .dvi so using /dev/fd/0 for
   standard input is problematic. We can get around that problem by
   linking (symbolically) a temporary file name (one that ends in
   .dvi) to /dev/fd/0, thereby forcing dvilj2p to read from standard
   input.

   The only other fly in the ointment is the fact that we cannot use
   /tmp for the temporary link. Symbolic links are owned by user and
   group bin. The filter runs as user daemon. And the /tmp directory
   has the sticky bit set. The filter can create the link, but it
   will not be able clean up when done and remove it since the link
   will belong to a different user.

   Instead, the filter will make the symbolic link in the current
   working directory, which is the spooling directory (specified by
   the sd capability in /etc/printcap). This is a perfect place for
   filters to do their work, especially since there is (sometimes)
   more free disk space in the spooling directory than under /tmp.

   Here, finally, is the filter:

 #!/bin/sh
 #
 #  hpdf - Print DVI data on HP/PCL printer
 #  Installed in /usr/local/libexec/hpdf

 PATH=/usr/local/bin:$PATH; export PATH

 #
 #  Define a function to clean up our temporary files.  These exist
 #  in the current directory, which will be the spooling directory
 #  for the printer.
 #
 cleanup() {
    rm -f hpdf$$.dvi
 }

 #
 #  Define a function to handle fatal errors: print the given message
 #  and exit 2.  Exiting with 2 tells LPD to do not try to reprint the
 #  job.
 #
 fatal() {
     echo "$@" 1>&2
     cleanup
     exit 2
 }

 #
 #  If user removes the job, LPD will send SIGINT, so trap SIGINT
 #  (and a few other signals) to clean up after ourselves.
 #
 trap cleanup 1 2 15

 #
 #  Make sure we are not colliding with any existing files.
 #
 cleanup

 #
 #  Link the DVI input file to standard input (the file to print).
 #
 ln -s /dev/fd/0 hpdf$$.dvi || fatal "Cannot symlink /dev/fd/0"

 #
 #  Make LF = CR+LF
 #
 printf "\033&k2G" || fatal "Cannot initialize printer"

 #
 #  Convert and print.  Return value from dvilj2p does not seem to be
 #  reliable, so we ignore it.
 #
 dvilj2p -M1 -q -e- dfhp$$.dvi

 #
 #  Clean up and exit
 #
 cleanup
 exit 0

     --------------------------------------------------------------

      9.4.1.4.5. Automated Conversion: an Alternative to Conversion
      Filters

   All these conversion filters accomplish a lot for your printing
   environment, but at the cost forcing the user to specify (on the
   lpr(1) command line) which one to use. If your users are not
   particularly computer literate, having to specify a filter option
   will become annoying. What is worse, though, is that an
   incorrectly specified filter option may run a filter on the wrong
   type of file and cause your printer to spew out hundreds of sheets
   of paper.

   Rather than install conversion filters at all, you might want to
   try having the text filter (since it is the default filter) detect
   the type of file it has been asked to print and then automatically
   run the right conversion filter. Tools such as file can be of help
   here. Of course, it will be hard to determine the differences
   between some file types!X!Xand, of course, you can still provide
   conversion filters just for them.

   The FreeBSD Ports Collection has a text filter that performs
   automatic conversion called apsfilter. It can detect plain text,
   PostScript, and DVI files, run the proper conversions, and print.

     --------------------------------------------------------------

    9.4.1.5. Output Filters

   The LPD spooling system supports one other type of filter that we
   have not yet explored: an output filter. An output filter is
   intended for printing plain text only, like the text filter, but
   with many simplifications. If you are using an output filter but
   no text filter, then:

     * LPD starts an output filter once for the entire job instead of
       once for each file in the job.

     * LPD does not make any provision to identify the start or the
       end of files within the job for the output filter.

     * LPD does not pass the user's login or host to the filter, so
       it is not intended to do accounting. In fact, it gets only two
       arguments:

       filter-name -wwidth -llength

       Where width is from the pw capability and length is from the
       pl capability for the printer in question.

   Do not be seduced by an output filter's simplicity. If you would
   like each file in a job to start on a different page an output
   filter will not work. Use a text filter (also known as an input
   filter); see section Installing the Text Filter. Furthermore, an
   output filter is actually more complex in that it has to examine
   the byte stream being sent to it for special flag characters and
   must send signals to itself on behalf of LPD.

   However, an output filter is necessary if you want header pages
   and need to send escape sequences or other initialization strings
   to be able to print the header page. (But it is also futile if you
   want to charge header pages to the requesting user's account,
   since LPD does not give any user or host information to the output
   filter.)

   On a single printer, LPD allows both an output filter and text or
   other filters. In such cases, LPD will start the output filter to
   print the header page (see section Header Pages) only. LPD then
   expects the output filter to stop itself by sending two bytes to
   the filter: ASCII 031 followed by ASCII 001. When an output filter
   sees these two bytes (031, 001), it should stop by sending SIGSTOP
   to itself. When LPD's done running other filters, it will restart
   the output filter by sending SIGCONT to it.

   If there is an output filter but no text filter and LPD is working
   on a plain text job, LPD uses the output filter to do the job. As
   stated before, the output filter will print each file of the job
   in sequence with no intervening form feeds or other paper
   advancement, and this is probably not what you want. In almost all
   cases, you need a text filter.

   The program lpf, which we introduced earlier as a text filter, can
   also run as an output filter. If you need a quick-and-dirty output
   filter but do not want to write the byte detection and signal
   sending code, try lpf. You can also wrap lpf in a shell script to
   handle any initialization codes the printer might require.

     --------------------------------------------------------------

    9.4.1.6. lpf: a Text Filter

   The program /usr/libexec/lpr/lpf that comes with FreeBSD binary
   distribution is a text filter (input filter) that can indent
   output (job submitted with lpr -i), allow literal characters to
   pass (job submitted with lpr -l), adjust the printing position for
   backspaces and tabs in the job, and account for pages printed. It
   can also act like an output filter.

   lpf is suitable for many printing environments. And although it
   has no capability to send initialization sequences to a printer,
   it is easy to write a shell script to do the needed initialization
   and then execute lpf.

   In order for lpf to do page accounting correctly, it needs correct
   values filled in for the pw and pl capabilities in the
   /etc/printcap file. It uses these values to determine how much
   text can fit on a page and how many pages were in a user's job.
   For more information on printer accounting, see Accounting for
   Printer Usage.

     --------------------------------------------------------------

  9.4.2. Header Pages

   If you have lots of users, all of them using various printers,
   then you probably want to consider header pages as a necessary
   evil.

   Header pages, also known as banner or burst pages identify to whom
   jobs belong after they are printed. They are usually printed in
   large, bold letters, perhaps with decorative borders, so that in a
   stack of printouts they stand out from the real documents that
   comprise users' jobs. They enable users to locate their jobs
   quickly. The obvious drawback to a header page is that it is yet
   one more sheet that has to be printed for every job, their
   ephemeral usefulness lasting not more than a few minutes,
   ultimately finding themselves in a recycling bin or rubbish heap.
   (Note that header pages go with each job, not each file in a job,
   so the paper waste might not be that bad.)

   The LPD system can provide header pages automatically for your
   printouts if your printer can directly print plain text. If you
   have a PostScript printer, you will need an external program to
   generate the header page; see Header Pages on PostScript Printers.

     --------------------------------------------------------------

    9.4.2.1. Enabling Header Pages

   In the Simple Printer Setup section, we turned off header pages by
   specifying sh (meaning !S:suppress header!") in the /etc/printcap
   file. To enable header pages for a printer, just remove the sh
   capability.

   Sounds too easy, right?

   You are right. You might have to provide an output filter to send
   initialization strings to the printer. Here is an example output
   filter for Hewlett Packard PCL-compatible printers:

 #!/bin/sh
 #
 #  hpof - Output filter for Hewlett Packard PCL-compatible printers
 #  Installed in /usr/local/libexec/hpof

 printf "\033&k2G" || exit 2
 exec /usr/libexec/lpr/lpf

   Specify the path to the output filter in the of capability. See
   the Output Filters section for more information.

   Here is an example /etc/printcap file for the printer teak that we
   introduced earlier; we enabled header pages and added the above
   output filter:

 #
 #  /etc/printcap for host orchid
 #
 teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
         :lp=/dev/lpt0:sd=/var/spool/lpd/teak:mx#0:\
         :if=/usr/local/libexec/hpif:\
         :vf=/usr/local/libexec/hpvf:\
         :of=/usr/local/libexec/hpof:

   Now, when users print jobs to teak, they get a header page with
   each job. If users want to spend time searching for their
   printouts, they can suppress header pages by submitting the job
   with lpr -h; see the Header Page Options section for more lpr(1)
   options.

     -a`: LPD prints a form feed character after the header page. If
     your printer uses a different character or sequence of
     characters to eject a page, specify them with the ff capability
     in /etc/printcap.

     --------------------------------------------------------------

    9.4.2.2. Controlling Header Pages

   By enabling header pages, LPD will produce a long header, a full
   page of large letters identifying the user, host, and job. Here is
   an example (kelly printed the job named outline from host rose):

       k                   ll       ll
       k                    l        l
       k                    l        l
       k   k     eeee       l        l     y    y
       k  k     e    e      l        l     y    y
       k k      eeeeee      l        l     y    y
       kk k     e           l        l     y    y
       k   k    e    e      l        l     y   yy
       k    k    eeee      lll      lll     yyy y
                                                y
                                           y    y
                                            yyyy


                                    ll
                           t         l        i
                           t         l
        oooo    u    u   ttttt       l       ii     n nnn     eeee
       o    o   u    u     t         l        i     nn   n   e    e
       o    o   u    u     t         l        i     n    n   eeeeee
       o    o   u    u     t         l        i     n    n   e
       o    o   u   uu     t  t      l        i     n    n   e    e
        oooo     uuu u      tt      lll      iii    n    n    eeee









       r rrr     oooo     ssss     eeee
       rr   r   o    o   s    s   e    e
       r        o    o    ss      eeeeee
       r        o    o      ss    e
       r        o    o   s    s   e    e
       r         oooo     ssss     eeee







                                               Job:  outline
                                               Date: Sun Sep 17 11:04:58 1995

   LPD appends a form feed after this text so the job starts on a new
   page (unless you have sf (suppress form feeds) in the destination
   printer's entry in /etc/printcap).

   If you prefer, LPD can make a short header; specify sb (short
   banner) in the /etc/printcap file. The header page will look like
   this:

 rose:kelly  Job: outline  Date: Sun Sep 17 11:07:51 1995

   Also by default, LPD prints the header page first, then the job.
   To reverse that, specify hl (header last) in /etc/printcap.

     --------------------------------------------------------------

    9.4.2.3. Accounting for Header Pages

   Using LPD's built-in header pages enforces a particular paradigm
   when it comes to printer accounting: header pages must be free of
   charge.

   Why?

   Because the output filter is the only external program that will
   have control when the header page is printed that could do
   accounting, and it is not provided with any user or host
   information or an accounting file, so it has no idea whom to
   charge for printer use. It is also not enough to just !S:add one
   page!" to the text filter or any of the conversion filters (which
   do have user and host information) since users can suppress header
   pages with lpr -h. They could still be charged for header pages
   they did not print. Basically, lpr -h will be the preferred option
   of environmentally-minded users, but you cannot offer any
   incentive to use it.

   It is still not enough to have each of the filters generate their
   own header pages (thereby being able to charge for them). If users
   wanted the option of suppressing the header pages with lpr -h,
   they will still get them and be charged for them since LPD does
   not pass any knowledge of the -h option to any of the filters.

   So, what are your options?

   You can:

     * Accept LPD's paradigm and make header pages free.

     * Install an alternative to LPD, such as LPRng. Section
       Alternatives to the Standard Spooler tells more about other
       spooling software you can substitute for LPD.

     * Write a smart output filter. Normally, an output filter is not
       meant to do anything more than initialize a printer or do some
       simple character conversion. It is suited for header pages and
       plain text jobs (when there is no text (input) filter). But,
       if there is a text filter for the plain text jobs, then LPD
       will start the output filter only for the header pages. And
       the output filter can parse the header page text that LPD
       generates to determine what user and host to charge for the
       header page. The only other problem with this method is that
       the output filter still does not know what accounting file to
       use (it is not passed the name of the file from the af
       capability), but if you have a well-known accounting file, you
       can hard-code that into the output filter. To facilitate the
       parsing step, use the sh (short header) capability in
       /etc/printcap. Then again, all that might be too much trouble,
       and users will certainly appreciate the more generous system
       administrator who makes header pages free.

     --------------------------------------------------------------

    9.4.2.4. Header Pages on PostScript Printers

   As described above, LPD can generate a plain text header page
   suitable for many printers. Of course, PostScript cannot directly
   print plain text, so the header page feature of LPD is
   useless!X!Xor mostly so.

   One obvious way to get header pages is to have every conversion
   filter and the text filter generate the header page. The filters
   should use the user and host arguments to generate a suitable
   header page. The drawback of this method is that users will always
   get a header page, even if they submit jobs with lpr -h.

   Let us explore this method. The following script takes three
   arguments (user login name, host name, and job name) and makes a
   simple PostScript header page:

 #!/bin/sh
 #
 #  make-ps-header - make a PostScript header page on stdout
 #  Installed in /usr/local/libexec/make-ps-header
 #

 #
 #  These are PostScript units (72 to the inch).  Modify for A4 or
 #  whatever size paper you are using:
 #
 page_width=612
 page_height=792
 border=72

 #
 #  Check arguments
 #
 if [ $# -ne 3 ]; then
     echo "Usage: `basename $0` <user> <host> <job>" 1>&2
     exit 1
 fi

 #
 #  Save these, mostly for readability in the PostScript, below.
 #
 user=$1
 host=$2
 job=$3
 date=`date`

 #
 #  Send the PostScript code to stdout.
 #
 exec cat <<EOF
 %!PS

 %
 %  Make sure we do not interfere with user's job that will follow
 %
 save

 %
 %  Make a thick, unpleasant border around the edge of the paper.
 %
 $border $border moveto
 $page_width $border 2 mul sub 0 rlineto
 0 $page_height $border 2 mul sub rlineto
 currentscreen 3 -1 roll pop 100 3 1 roll setscreen
 $border 2 mul $page_width sub 0 rlineto closepath
 0.8 setgray 10 setlinewidth stroke 0 setgray

 %
 %  Display user's login name, nice and large and prominent
 %
 /Helvetica-Bold findfont 64 scalefont setfont
 $page_width ($user) stringwidth pop sub 2 div $page_height 200 sub moveto
 ($user) show

 %
 %  Now show the boring particulars
 %
 /Helvetica findfont 14 scalefont setfont
 /y 200 def
 [ (Job:) (Host:) (Date:) ] {
 200 y moveto show /y y 18 sub def }
 forall

 /Helvetica-Bold findfont 14 scalefont setfont
 /y 200 def
 [ ($job) ($host) ($date) ] {
         270 y moveto show /y y 18 sub def
 } forall

 %
 % That is it
 %
 restore
 showpage
 EOF

   Now, each of the conversion filters and the text filter can call
   this script to first generate the header page, and then print the
   user's job. Here is the DVI conversion filter from earlier in this
   document, modified to make a header page:

 #!/bin/sh
 #
 #  psdf - DVI to PostScript printer filter
 #  Installed in /usr/local/libexec/psdf
 #
 #  Invoked by lpd when user runs lpr -d
 #

 orig_args="$@"

 fail() {
     echo "$@" 1>&2
     exit 2
 }

 while getopts "x:y:n:h:" option; do
     case $option in
         x|y)  ;; # Ignore
         n)    login=$OPTARG ;;
         h)    host=$OPTARG ;;
         *)    echo "LPD started `basename $0` wrong." 1>&2
               exit 2
               ;;
     esac
 done

 [ "$login" ] || fail "No login name"
 [ "$host" ] || fail "No host name"

 ( /usr/local/libexec/make-ps-header $login $host "DVI File"
   /usr/local/bin/dvips -f ) | eval /usr/local/libexec/lprps $orig_args

   Notice how the filter has to parse the argument list in order to
   determine the user and host name. The parsing for the other
   conversion filters is identical. The text filter takes a slightly
   different set of arguments, though (see section How Filters Work).

   As we have mentioned before, the above scheme, though fairly
   simple, disables the !S:suppress header page!" option (the -h
   option) to lpr. If users wanted to save a tree (or a few pennies,
   if you charge for header pages), they would not be able to do so,
   since every filter's going to print a header page with every job.

   To allow users to shut off header pages on a per-job basis, you
   will need to use the trick introduced in section Accounting for
   Header Pages: write an output filter that parses the LPD-generated
   header page and produces a PostScript version. If the user submits
   the job with lpr -h, then LPD will not generate a header page, and
   neither will your output filter. Otherwise, your output filter
   will read the text from LPD and send the appropriate header page
   PostScript code to the printer.

   If you have a PostScript printer on a serial line, you can make
   use of lprps, which comes with an output filter, psof, which does
   the above. Note that psof does not charge for header pages.

     --------------------------------------------------------------

  9.4.3. Networked Printing

   FreeBSD supports networked printing: sending jobs to remote
   printers. Networked printing generally refers to two different
   things:

     * Accessing a printer attached to a remote host. You install a
       printer that has a conventional serial or parallel interface
       on one host. Then, you set up LPD to enable access to the
       printer from other hosts on the network. Section Printers
       Installed on Remote Hosts tells how to do this.

     * Accessing a printer attached directly to a network. The
       printer has a network interface in addition (or in place of) a
       more conventional serial or parallel interface. Such a printer
       might work as follows:

          * It might understand the LPD protocol and can even queue
            jobs from remote hosts. In this case, it acts just like a
            regular host running LPD. Follow the same procedure in
            section Printers Installed on Remote Hosts to set up such
            a printer.

          * It might support a data stream network connection. In
            this case, you !S:attach!" the printer to one host on the
            network by making that host responsible for spooling jobs
            and sending them to the printer. Section Printers with
            Networked Data Stream Interfaces gives some suggestions
            on installing such printers.

     --------------------------------------------------------------

    9.4.3.1. Printers Installed on Remote Hosts

   The LPD spooling system has built-in support for sending jobs to
   other hosts also running LPD (or are compatible with LPD). This
   feature enables you to install a printer on one host and make it
   accessible from other hosts. It also works with printers that have
   network interfaces that understand the LPD protocol.

   To enable this kind of remote printing, first install a printer on
   one host, the printer host, using the simple printer setup
   described in the Simple Printer Setup section. Do any advanced
   setup in Advanced Printer Setup that you need. Make sure to test
   the printer and see if it works with the features of LPD you have
   enabled. Also ensure that the local host has authorization to use
   the LPD service in the remote host (see Restricting Jobs from
   Remote Printers).

   If you are using a printer with a network interface that is
   compatible with LPD, then the printer host in the discussion below
   is the printer itself, and the printer name is the name you
   configured for the printer. See the documentation that accompanied
   your printer and/or printer-network interface.

     '-L-YENU:: If you are using a Hewlett Packard Laserjet then the
     printer name text will automatically perform the LF to CRLF
     conversion for you, so you will not require the hpif script.

   Then, on the other hosts you want to have access to the printer,
   make an entry in their /etc/printcap files with the following:

    1. Name the entry anything you want. For simplicity, though, you
       probably want to use the same name and aliases as on the
       printer host.

    2. Leave the lp capability blank, explicitly (:lp=:).

    3. Make a spooling directory and specify its location in the sd
       capability. LPD will store jobs here before they get sent to
       the printer host.

    4. Place the name of the printer host in the rm capability.

    5. Place the printer name on the printer host in the rp
       capability.

   That is it. You do not need to list conversion filters, page
   dimensions, or anything else in the /etc/printcap file.

   Here is an example. The host rose has two printers, bamboo and
   rattan. We will enable users on the host orchid to print to those
   printers. Here is the /etc/printcap file for orchid (back from
   section Enabling Header Pages). It already had the entry for the
   printer teak; we have added entries for the two printers on the
   host rose:

 #
 #  /etc/printcap for host orchid - added (remote) printers on rose
 #

 #
 #  teak is local; it is connected directly to orchid:
 #
 teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
         :lp=/dev/lpt0:sd=/var/spool/lpd/teak:mx#0:\
         :if=/usr/local/libexec/ifhp:\
         :vf=/usr/local/libexec/vfhp:\
         :of=/usr/local/libexec/ofhp:

 #
 #  rattan is connected to rose; send jobs for rattan to rose:
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :lp=:rm=rose:rp=rattan:sd=/var/spool/lpd/rattan:

 #
 #  bamboo is connected to rose as well:
 #
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :lp=:rm=rose:rp=bamboo:sd=/var/spool/lpd/bamboo:

   Then, we just need to make spooling directories on orchid:

 # mkdir -p /var/spool/lpd/rattan /var/spool/lpd/bamboo
 # chmod 770 /var/spool/lpd/rattan /var/spool/lpd/bamboo
 # chown daemon:daemon /var/spool/lpd/rattan /var/spool/lpd/bamboo

   Now, users on orchid can print to rattan and bamboo. If, for
   example, a user on orchid typed

 % lpr -P bamboo -d sushi-review.dvi

   the LPD system on orchid would copy the job to the spooling
   directory /var/spool/lpd/bamboo and note that it was a DVI job. As
   soon as the host rose has room in its bamboo spooling directory,
   the two LPDs would transfer the file to rose. The file would wait
   in rose's queue until it was finally printed. It would be
   converted from DVI to PostScript (since bamboo is a PostScript
   printer) on rose.

     --------------------------------------------------------------

    9.4.3.2. Printers with Networked Data Stream Interfaces

   Often, when you buy a network interface card for a printer, you
   can get two versions: one which emulates a spooler (the more
   expensive version), or one which just lets you send data to it as
   if you were using a serial or parallel port (the cheaper version).
   This section tells how to use the cheaper version. For the more
   expensive one, see the previous section Printers Installed on
   Remote Hosts.

   The format of the /etc/printcap file lets you specify what serial
   or parallel interface to use, and (if you are using a serial
   interface), what baud rate, whether to use flow control, delays
   for tabs, conversion of newlines, and more. But there is no way to
   specify a connection to a printer that is listening on a TCP/IP or
   other network port.

   To send data to a networked printer, you need to develop a
   communications program that can be called by the text and
   conversion filters. Here is one such example: the script netprint
   takes all data on standard input and sends it to a
   network-attached printer. We specify the hostname of the printer
   as the first argument and the port number to which to connect as
   the second argument to netprint. Note that this supports one-way
   communication only (FreeBSD to printer); many network printers
   support two-way communication, and you might want to take
   advantage of that (to get printer status, perform accounting,
   etc.).

 #!/usr/bin/perl
 #
 #  netprint - Text filter for printer attached to network
 #  Installed in /usr/local/libexec/netprint
 #
 $#ARGV eq 1 || die "Usage: $0 <printer-hostname> <port-number>";

 $printer_host = $ARGV[0];
 $printer_port = $ARGV[1];

 require 'sys/socket.ph';

 ($ignore, $ignore, $protocol) = getprotobyname('tcp');
 ($ignore, $ignore, $ignore, $ignore, $address)
     = gethostbyname($printer_host);

 $sockaddr = pack('S n a4 x8', &AF_INET, $printer_port, $address);

 socket(PRINTER, &PF_INET, &SOCK_STREAM, $protocol)
     || die "Can't create TCP/IP stream socket: $!";
 connect(PRINTER, $sockaddr) || die "Can't contact $printer_host: $!";
 while (<STDIN>) { print PRINTER; }
 exit 0;

   We can then use this script in various filters. Suppose we had a
   Diablo 750-N line printer connected to the network. The printer
   accepts data to print on port number 5100. The host name of the
   printer is scrivener. Here is the text filter for the printer:

 #!/bin/sh
 #
 #  diablo-if-net - Text filter for Diablo printer `scrivener' listening
 #  on port 5100.   Installed in /usr/local/libexec/diablo-if-net
 #
 exec /usr/libexec/lpr/lpf "$@" | /usr/local/libexec/netprint scrivener 5100

     --------------------------------------------------------------

  9.4.4. Restricting Printer Usage

   This section gives information on restricting printer usage. The
   LPD system lets you control who can access a printer, both locally
   or remotely, whether they can print multiple copies, how large
   their jobs can be, and how large the printer queues can get.

     --------------------------------------------------------------

    9.4.4.1. Restricting Multiple Copies

   The LPD system makes it easy for users to print multiple copies of
   a file. Users can print jobs with lpr -#5 (for example) and get
   five copies of each file in the job. Whether this is a good thing
   is up to you.

   If you feel multiple copies cause unnecessary wear and tear on
   your printers, you can disable the -# option to lpr(1) by adding
   the sc capability to the /etc/printcap file. When users submit
   jobs with the -# option, they will see:

 lpr: multiple copies are not allowed

   Note that if you have set up access to a printer remotely (see
   section Printers Installed on Remote Hosts), you need the sc
   capability on the remote /etc/printcap files as well, or else
   users will still be able to submit multiple-copy jobs by using
   another host.

   Here is an example. This is the /etc/printcap file for the host
   rose. The printer rattan is quite hearty, so we will allow
   multiple copies, but the laser printer bamboo is a bit more
   delicate, so we will disable multiple copies by adding the sc
   capability:

 #
 #  /etc/printcap for host rose - restrict multiple copies on bamboo
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:

 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:sc:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:\
         :if=/usr/local/libexec/psif:\
         :df=/usr/local/libexec/psdf:

   Now, we also need to add the sc capability on the host orchid's
   /etc/printcap (and while we are at it, let us disable multiple
   copies for the printer teak):

 #
 #  /etc/printcap for host orchid - no multiple copies for local
 #  printer teak or remote printer bamboo
 teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
         :lp=/dev/lpt0:sd=/var/spool/lpd/teak:mx#0:sc:\
         :if=/usr/local/libexec/ifhp:\
         :vf=/usr/local/libexec/vfhp:\
         :of=/usr/local/libexec/ofhp:

 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :lp=:rm=rose:rp=rattan:sd=/var/spool/lpd/rattan:

 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :lp=:rm=rose:rp=bamboo:sd=/var/spool/lpd/bamboo:sc:

   By using the sc capability, we prevent the use of lpr -#, but that
   still does not prevent users from running lpr(1) multiple times,
   or from submitting the same file multiple times in one job like
   this:

 % lpr forsale.sign forsale.sign forsale.sign forsale.sign forsale.sign

   There are many ways to prevent this abuse (including ignoring it)
   which you are free to explore.

     --------------------------------------------------------------

    9.4.4.2. Restricting Access to Printers

   You can control who can print to what printers by using the UNIX
   group mechanism and the rg capability in /etc/printcap. Just place
   the users you want to have access to a printer in a certain group,
   and then name that group in the rg capability.

   Users outside the group (including root) will be greeted with
   !S:lpr: Not a member of the restricted group!" if they try to
   print to the controlled printer.

   As with the sc (suppress multiple copies) capability, you need to
   specify rg on remote hosts that also have access to your printers,
   if you feel it is appropriate (see section Printers Installed on
   Remote Hosts).

   For example, we will let anyone access the printer rattan, but
   only those in group artists can use bamboo. Here is the familiar
   /etc/printcap for host rose:

 #
 #  /etc/printcap for host rose - restricted group for bamboo
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:

 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:sc:rg=artists:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:\
         :if=/usr/local/libexec/psif:\
         :df=/usr/local/libexec/psdf:

   Let us leave the other example /etc/printcap file (for the host
   orchid) alone. Of course, anyone on orchid can print to bamboo. It
   might be the case that we only allow certain logins on orchid
   anyway, and want them to have access to the printer. Or not.

     -a`: There can be only one restricted group per printer.

     --------------------------------------------------------------

    9.4.4.3. Controlling Sizes of Jobs Submitted

   If you have many users accessing the printers, you probably need
   to put an upper limit on the sizes of the files users can submit
   to print. After all, there is only so much free space on the
   filesystem that houses the spooling directories, and you also need
   to make sure there is room for the jobs of other users.

   LPD enables you to limit the maximum byte size a file in a job can
   be with the mx capability. The units are in BUFSIZ blocks, which
   are 1024 bytes. If you put a zero for this capability, there will
   be no limit on file size; however, if no mx capability is
   specified, then a default limit of 1000 blocks will be used.

     -a`: The limit applies to files in a job, and not the total job
     size.

   LPD will not refuse a file that is larger than the limit you place
   on a printer. Instead, it will queue as much of the file up to the
   limit, which will then get printed. The rest will be discarded.
   Whether this is correct behavior is up for debate.

   Let us add limits to our example printers rattan and bamboo. Since
   those artists' PostScript files tend to be large, we will limit
   them to five megabytes. We will put no limit on the plain text
   line printer:

 #
 #  /etc/printcap for host rose
 #

 #
 #  No limit on job size:
 #
 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:mx#0:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:

 #
 #  Limit of five megabytes:
 #
 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:sc:rg=artists:mx#5000:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:\
         :if=/usr/local/libexec/psif:\
         :df=/usr/local/libexec/psdf:

   Again, the limits apply to the local users only. If you have set
   up access to your printers remotely, remote users will not get
   those limits. You will need to specify the mx capability in the
   remote /etc/printcap files as well. See section Printers Installed
   on Remote Hosts for more information on remote printing.

   There is another specialized way to limit job sizes from remote
   printers; see section Restricting Jobs from Remote Printers.

     --------------------------------------------------------------

    9.4.4.4. Restricting Jobs from Remote Printers

   The LPD spooling system provides several ways to restrict print
   jobs submitted from remote hosts:

   Host restrictions

           You can control from which remote hosts a local LPD
           accepts requests with the files /etc/hosts.equiv and
           /etc/hosts.lpd. LPD checks to see if an incoming request
           is from a host listed in either one of these files. If
           not, LPD refuses the request.

           The format of these files is simple: one host name per
           line. Note that the file /etc/hosts.equiv is also used by
           the ruserok(3) protocol, and affects programs like rsh(1)
           and rcp(1), so be careful.

           For example, here is the /etc/hosts.lpd file on the host
           rose:

 orchid
 violet
 madrigal.fishbaum.de

           This means rose will accept requests from the hosts
           orchid, violet, and madrigal.fishbaum.de. If any other
           host tries to access rose's LPD, the job will be refused.

   Size restrictions

           You can control how much free space there needs to remain
           on the filesystem where a spooling directory resides. Make
           a file called minfree in the spooling directory for the
           local printer. Insert in that file a number representing
           how many disk blocks (512 bytes) of free space there has
           to be for a remote job to be accepted.

           This lets you insure that remote users will not fill your
           filesystem. You can also use it to give a certain priority
           to local users: they will be able to queue jobs long after
           the free disk space has fallen below the amount specified
           in the minfree file.

           For example, let us add a minfree file for the printer
           bamboo. We examine /etc/printcap to find the spooling
           directory for this printer; here is bamboo's entry:

 bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
         :sh:sd=/var/spool/lpd/bamboo:sc:rg=artists:mx#5000:\
         :lp=/dev/ttyd5:ms#-parenb cs8 clocal crtscts:rw:mx#5000:\
         :if=/usr/local/libexec/psif:\
         :df=/usr/local/libexec/psdf:

           The spooling directory is given in the sd capability. We
           will make three megabytes (which is 6144 disk blocks) the
           amount of free disk space that must exist on the
           filesystem for LPD to accept remote jobs:

 # echo 6144 > /var/spool/lpd/bamboo/minfree
              

   User restrictions

           You can control which remote users can print to local
           printers by specifying the rs capability in /etc/printcap.
           When rs appears in the entry for a locally-attached
           printer, LPD will accept jobs from remote hosts if the
           user submitting the job also has an account of the same
           login name on the local host. Otherwise, LPD refuses the
           job.

           This capability is particularly useful in an environment
           where there are (for example) different departments
           sharing a network, and some users transcend departmental
           boundaries. By giving them accounts on your systems, they
           can use your printers from their own departmental systems.
           If you would rather allow them to use only your printers
           and not your computer resources, you can give them
           !S:token!" accounts, with no home directory and a useless
           shell like /usr/bin/false.

     --------------------------------------------------------------

  9.4.5. Accounting for Printer Usage

   So, you need to charge for printouts. And why not? Paper and ink
   cost money. And then there are maintenance costs!X!Xprinters are
   loaded with moving parts and tend to break down. You have examined
   your printers, usage patterns, and maintenance fees and have come
   up with a per-page (or per-foot, per-meter, or per-whatever) cost.
   Now, how do you actually start accounting for printouts?

   Well, the bad news is the LPD spooling system does not provide
   much help in this department. Accounting is highly dependent on
   the kind of printer in use, the formats being printed, and your
   requirements in charging for printer usage.

   To implement accounting, you have to modify a printer's text
   filter (to charge for plain text jobs) and the conversion filters
   (to charge for other file formats), to count pages or query the
   printer for pages printed. You cannot get away with using the
   simple output filter, since it cannot do accounting. See section
   Filters.

   Generally, there are two ways to do accounting:

     * Periodic accounting is the more common way, possibly because
       it is easier. Whenever someone prints a job, the filter logs
       the user, host, and number of pages to an accounting file.
       Every month, semester, year, or whatever time period you
       prefer, you collect the accounting files for the various
       printers, tally up the pages printed by users, and charge for
       usage. Then you truncate all the logging files, starting with
       a clean slate for the next period.

     * Timely accounting is less common, probably because it is more
       difficult. This method has the filters charge users for
       printouts as soon as they use the printers. Like disk quotas,
       the accounting is immediate. You can prevent users from
       printing when their account goes in the red, and might provide
       a way for users to check and adjust their !S:print quotas.!"
       But this method requires some database code to track users and
       their quotas.

   The LPD spooling system supports both methods easily: since you
   have to provide the filters (well, most of the time), you also
   have to provide the accounting code. But there is a bright side:
   you have enormous flexibility in your accounting methods. For
   example, you choose whether to use periodic or timely accounting.
   You choose what information to log: user names, host names, job
   types, pages printed, square footage of paper used, how long the
   job took to print, and so forth. And you do so by modifying the
   filters to save this information.

     --------------------------------------------------------------

    9.4.5.1. Quick and Dirty Printer Accounting

   FreeBSD comes with two programs that can get you set up with
   simple periodic accounting right away. They are the text filter
   lpf, described in section lpf: a Text Filter, and pac(8), a
   program to gather and total entries from printer accounting files.

   As mentioned in the section on filters (Filters), LPD starts the
   text and the conversion filters with the name of the accounting
   file to use on the filter command line. The filters can use this
   argument to know where to write an accounting file entry. The name
   of this file comes from the af capability in /etc/printcap, and if
   not specified as an absolute path, is relative to the spooling
   directory.

   LPD starts lpf with page width and length arguments (from the pw
   and pl capabilities). lpf uses these arguments to determine how
   much paper will be used. After sending the file to the printer, it
   then writes an accounting entry in the accounting file. The
   entries look like this:

 2.00 rose:andy
 3.00 rose:kelly
 3.00 orchid:mary
 5.00 orchid:mary
 2.00 orchid:zhang

   You should use a separate accounting file for each printer, as lpf
   has no file locking logic built into it, and two lpfs might
   corrupt each other's entries if they were to write to the same
   file at the same time. An easy way to insure a separate accounting
   file for each printer is to use af=acct in /etc/printcap. Then,
   each accounting file will be in the spooling directory for a
   printer, in a file named acct.

   When you are ready to charge users for printouts, run the pac(8)
   program. Just change to the spooling directory for the printer you
   want to collect on and type pac. You will get a dollar-centric
   summary like the following:

   Login               pages/feet   runs    price
 orchid:kelly                5.00    1   $  0.10
 orchid:mary                31.00    3   $  0.62
 orchid:zhang                9.00    1   $  0.18
 rose:andy                   2.00    1   $  0.04
 rose:kelly                177.00  104   $  3.54
 rose:mary                  87.00   32   $  1.74
 rose:root                  26.00   12   $  0.52

 total                     337.00  154   $  6.74

   These are the arguments pac(8) expects:

   -Pprinter

           Which printer to summarize. This option works only if
           there is an absolute path in the af capability in
           /etc/printcap.

   -c

           Sort the output by cost instead of alphabetically by user
           name.

   -m

           Ignore host name in the accounting files. With this
           option, user smith on host alpha is the same user smith on
           host gamma. Without, they are different users.

   -pprice

           Compute charges with price dollars per page or per foot
           instead of the price from the pc capability in
           /etc/printcap, or two cents (the default). You can specify
           price as a floating point number.

   -r

           Reverse the sort order.

   -s

           Make an accounting summary file and truncate the
           accounting file.

   name !K

           Print accounting information for the given user names
           only.

   In the default summary that pac(8) produces, you see the number of
   pages printed by each user from various hosts. If, at your site,
   host does not matter (because users can use any host), run pac -m,
   to produce the following summary:

   Login               pages/feet   runs    price
 andy                        2.00    1   $  0.04
 kelly                     182.00  105   $  3.64
 mary                      118.00   35   $  2.36
 root                       26.00   12   $  0.52
 zhang                       9.00    1   $  0.18

 total                     337.00  154   $  6.74

   To compute the dollar amount due, pac(8) uses the pc capability in
   the /etc/printcap file (default of 200, or 2 cents per page).
   Specify, in hundredths of cents, the price per page or per foot
   you want to charge for printouts in this capability. You can
   override this value when you run pac(8) with the -p option. The
   units for the -p option are in dollars, though, not hundredths of
   cents. For example,

 # pac -p1.50

   makes each page cost one dollar and fifty cents. You can really
   rake in the profits by using this option.

   Finally, running pac -s will save the summary information in a
   summary accounting file, which is named the same as the printer's
   accounting file, but with _sum appended to the name. It then
   truncates the accounting file. When you run pac(8) again, it
   rereads the summary file to get starting totals, then adds
   information from the regular accounting file.

     --------------------------------------------------------------

    9.4.5.2. How Can You Count Pages Printed?

   In order to perform even remotely accurate accounting, you need to
   be able to determine how much paper a job uses. This is the
   essential problem of printer accounting.

   For plain text jobs, the problem is not that hard to solve: you
   count how many lines are in a job and compare it to how many lines
   per page your printer supports. Do not forget to take into account
   backspaces in the file which overprint lines, or long logical
   lines that wrap onto one or more additional physical lines.

   The text filter lpf (introduced in lpf: a Text Filter) takes into
   account these things when it does accounting. If you are writing a
   text filter which needs to do accounting, you might want to
   examine lpf's source code.

   How do you handle other file formats, though?

   Well, for DVI-to-LaserJet or DVI-to-PostScript conversion, you can
   have your filter parse the diagnostic output of dvilj or dvips and
   look to see how many pages were converted. You might be able to do
   similar things with other file formats and conversion programs.

   But these methods suffer from the fact that the printer may not
   actually print all those pages. For example, it could jam, run out
   of toner, or explode!X!Xand the user would still get charged.

   So, what can you do?

   There is only one sure way to do accurate accounting. Get a
   printer that can tell you how much paper it uses, and attach it
   via a serial line or a network connection. Nearly all PostScript
   printers support this notion. Other makes and models do as well
   (networked Imagen laser printers, for example). Modify the filters
   for these printers to get the page usage after they print each job
   and have them log accounting information based on that value only.
   There is no line counting nor error-prone file examination
   required.

   Of course, you can always be generous and make all printouts free.

     --------------------------------------------------------------

9.5. Using Printers

   This section tells you how to use printers you have set up with
   FreeBSD. Here is an overview of the user-level commands:

   lpr(1)

           Print jobs

   lpq(1)

           Check printer queues

   lprm(1)

           Remove jobs from a printer's queue

   There is also an administrative command, lpc(8), described in the
   section Administering Printers, used to control printers and their
   queues.

   All three of the commands lpr(1), lprm(1), and lpq(1) accept an
   option -P printer-name to specify on which printer/queue to
   operate, as listed in the /etc/printcap file. This enables you to
   submit, remove, and check on jobs for various printers. If you do
   not use the -P option, then these commands use the printer
   specified in the PRINTER environment variable. Finally, if you do
   not have a PRINTER environment variable, these commands default to
   the printer named lp.

   Hereafter, the terminology default printer means the printer named
   in the PRINTER environment variable, or the printer named lp when
   there is no PRINTER environment variable.

     --------------------------------------------------------------

  9.5.1. Printing Jobs

   To print files, type:

 % lpr filename ...

   This prints each of the listed files to the default printer. If
   you list no files, lpr(1) reads data to print from standard input.
   For example, this command prints some important system files:

 % lpr /etc/host.conf /etc/hosts.equiv

   To select a specific printer, type:

 % lpr -P printer-name filename ...

   This example prints a long listing of the current directory to the
   printer named rattan:

 % ls -l | lpr -P rattan

   Because no files were listed for the lpr(1) command, lpr read the
   data to print from standard input, which was the output of the ls
   -l command.

   The lpr(1) command can also accept a wide variety of options to
   control formatting, apply file conversions, generate multiple
   copies, and so forth. For more information, see the section
   Printing Options.

     --------------------------------------------------------------

  9.5.2. Checking Jobs

   When you print with lpr(1), the data you wish to print is put
   together in a package called a !S:print job!", which is sent to
   the LPD spooling system. Each printer has a queue of jobs, and
   your job waits in that queue along with other jobs from yourself
   and from other users. The printer prints those jobs in a
   first-come, first-served order.

   To display the queue for the default printer, type lpq(1). For a
   specific printer, use the -P option. For example, the command

 % lpq -P bamboo

   shows the queue for the printer named bamboo. Here is an example
   of the output of the lpq command:

 bamboo is ready and printing
 Rank   Owner    Job  Files                              Total Size
 active kelly    9    /etc/host.conf, /etc/hosts.equiv   88 bytes
 2nd    kelly    10   (standard input)                   1635 bytes
 3rd    mary     11   ...                                78519 bytes

   This shows three jobs in the queue for bamboo. The first job,
   submitted by user kelly, got assigned !S:job number!" 9. Every job
   for a printer gets a unique job number. Most of the time you can
   ignore the job number, but you will need it if you want to cancel
   the job; see section Removing Jobs for details.

   Job number nine consists of two files; multiple files given on the
   lpr(1) command line are treated as part of a single job. It is the
   currently active job (note the word active under the !S:Rank!"
   column), which means the printer should be currently printing that
   job. The second job consists of data passed as the standard input
   to the lpr(1) command. The third job came from user mary; it is a
   much larger job. The pathname of the file she is trying to print
   is too long to fit, so the lpq(1) command just shows three dots.

   The very first line of the output from lpq(1) is also useful: it
   tells what the printer is currently doing (or at least what LPD
   thinks the printer is doing).

   The lpq(1) command also support a -l option to generate a detailed
   long listing. Here is an example of lpq -l:

 waiting for bamboo to become ready (offline ?)
 kelly: 1st                               [job 009rose]
        /etc/host.conf                    73 bytes
        /etc/hosts.equiv                  15 bytes

 kelly: 2nd                               [job 010rose]
        (standard input)                  1635 bytes

 mary: 3rd                                [job 011rose]
       /home/orchid/mary/research/venus/alpha-regio/mapping 78519 bytes

     --------------------------------------------------------------

  9.5.3. Removing Jobs

   If you change your mind about printing a job, you can remove the
   job from the queue with the lprm(1) command. Often, you can even
   use lprm(1) to remove an active job, but some or all of the job
   might still get printed.

   To remove a job from the default printer, first use lpq(1) to find
   the job number. Then type:

 % lprm job-number

   To remove the job from a specific printer, add the -P option. The
   following command removes job number 10 from the queue for the
   printer bamboo:

 % lprm -P bamboo 10

   The lprm(1) command has a few shortcuts:

   lprm -

           Removes all jobs (for the default printer) belonging to
           you.

   lprm user

           Removes all jobs (for the default printer) belonging to
           user. The superuser can remove other users' jobs; you can
           remove only your own jobs.

   lprm

           With no job number, user name, or - appearing on the
           command line, lprm(1) removes the currently active job on
           the default printer, if it belongs to you. The superuser
           can remove any active job.

   Just use the -P option with the above shortcuts to operate on a
   specific printer instead of the default. For example, the
   following command removes all jobs for the current user in the
   queue for the printer named rattan:

 % lprm -P rattan -

     -a`: If you are working in a networked environment, lprm(1) will
     let you remove jobs only from the host from which the jobs were
     submitted, even if the same printer is available from other
     hosts. The following command sequence demonstrates this:

 % lpr -P rattan myfile
 % rlogin orchid
 % lpq -P rattan
 Rank   Owner      Job  Files                          Total Size
 active seeyan     12    ...                           49123 bytes
 2nd    kelly      13   myfile                         12 bytes
 % lprm -P rattan 13
 rose: Permission denied
 % logout
 % lprm -P rattan 13
 dfA013rose dequeued
 cfA013rose dequeued
        

     --------------------------------------------------------------

  9.5.4. Beyond Plain Text: Printing Options

   The lpr(1) command supports a number of options that control
   formatting text, converting graphic and other file formats,
   producing multiple copies, handling of the job, and more. This
   section describes the options.

     --------------------------------------------------------------

    9.5.4.1. Formatting and Conversion Options

   The following lpr(1) options control formatting of the files in
   the job. Use these options if the job does not contain plain text
   or if you want plain text formatted through the pr(1) utility.

   For example, the following command prints a DVI file (from the TeX
   typesetting system) named fish-report.dvi to the printer named
   bamboo:

 % lpr -P bamboo -d fish-report.dvi

   These options apply to every file in the job, so you cannot mix
   (say) DVI and ditroff files together in a job. Instead, submit the
   files as separate jobs, using a different conversion option for
   each job.

     -a`: All of these options except -p and -T require conversion
     filters installed for the destination printer. For example, the
     -d option requires the DVI conversion filter. Section Conversion
     Filters gives details.

   -c

           Print cifplot files.

   -d

           Print DVI files.

   -f

           Print FORTRAN text files.

   -g

           Print plot data.

   -i number

           Indent the output by number columns; if you omit number,
           indent by 8 columns. This option works only with certain
           conversion filters.

             -a`: Do not put any space between the -i and the number.

   -l

           Print literal text data, including control characters.

   -n

           Print ditroff (device independent troff) data.

   -p

           Format plain text with pr(1) before printing. See pr(1)
           for more information.

   -T title

           Use title on the pr(1) header instead of the file name.
           This option has effect only when used with the -p option.

   -t

           Print troff data.

   -v

           Print raster data.

   Here is an example: this command prints a nicely formatted version
   of the ls(1) manual page on the default printer:

 % zcat /usr/share/man/man1/ls.1.gz | troff -t -man | lpr -t

   The zcat(1) command uncompresses the source of the ls(1) manual
   page and passes it to the troff(1) command, which formats that
   source and makes GNU troff output and passes it to lpr(1), which
   submits the job to the LPD spooler. Because we used the -t option
   to lpr(1), the spooler will convert the GNU troff output into a
   format the default printer can understand when it prints the job.

     --------------------------------------------------------------

    9.5.4.2. Job Handling Options

   The following options to lpr(1) tell LPD to handle the job
   specially:

   -# copies

           Produce a number of copies of each file in the job instead
           of just one copy. An administrator may disable this option
           to reduce printer wear-and-tear and encourage photocopier
           usage. See section Restricting Multiple Copies.

           This example prints three copies of parser.c followed by
           three copies of parser.h to the default printer:

 % lpr -#3 parser.c parser.h

   -m

           Send mail after completing the print job. With this
           option, the LPD system will send mail to your account when
           it finishes handling your job. In its message, it will
           tell you if the job completed successfully or if there was
           an error, and (often) what the error was.

   -s

           Do not copy the files to the spooling directory, but make
           symbolic links to them instead.

           If you are printing a large job, you probably want to use
           this option. It saves space in the spooling directory
           (your job might overflow the free space on the filesystem
           where the spooling directory resides). It saves time as
           well since LPD will not have to copy each and every byte
           of your job to the spooling directory.

           There is a drawback, though: since LPD will refer to the
           original files directly, you cannot modify or remove them
           until they have been printed.

             -a`: If you are printing to a remote printer, LPD will
             eventually have to copy files from the local host to the
             remote host, so the -s option will save space only on
             the local spooling directory, not the remote. It is
             still useful, though.

   -r

           Remove the files in the job after copying them to the
           spooling directory, or after printing them with the -s
           option. Be careful with this option!

     --------------------------------------------------------------

    9.5.4.3. Header Page Options

   These options to lpr(1) adjust the text that normally appears on a
   job's header page. If header pages are suppressed for the
   destination printer, these options have no effect. See section
   Header Pages for information about setting up header pages.

   -C text

           Replace the hostname on the header page with text. The
           hostname is normally the name of the host from which the
           job was submitted.

   -J text

           Replace the job name on the header page with text. The job
           name is normally the name of the first file of the job, or
           stdin if you are printing standard input.

   -h

           Do not print any header page.

             -a`: At some sites, this option may have no effect due
             to the way header pages are generated. See Header Pages
             for details.

     --------------------------------------------------------------

  9.5.5. Administering Printers

   As an administrator for your printers, you have had to install,
   set up, and test them. Using the lpc(8) command, you can interact
   with your printers in yet more ways. With lpc(8), you can

     * Start and stop the printers

     * Enable and disable their queues

     * Rearrange the order of the jobs in each queue.

   First, a note about terminology: if a printer is stopped, it will
   not print anything in its queue. Users can still submit jobs,
   which will wait in the queue until the printer is started or the
   queue is cleared.

   If a queue is disabled, no user (except root) can submit jobs for
   the printer. An enabled queue allows jobs to be submitted. A
   printer can be started for a disabled queue, in which case it will
   continue to print jobs in the queue until the queue is empty.

   In general, you have to have root privileges to use the lpc(8)
   command. Ordinary users can use the lpc(8) command to get printer
   status and to restart a hung printer only.

   Here is a summary of the lpc(8) commands. Most of the commands
   take a printer-name argument to tell on which printer to operate.
   You can use all for the printer-name to mean all printers listed
   in /etc/printcap.

   abort printer-name

           Cancel the current job and stop the printer. Users can
           still submit jobs if the queue is enabled.

   clean printer-name

           Remove old files from the printer's spooling directory.
           Occasionally, the files that make up a job are not
           properly removed by LPD, particularly if there have been
           errors during printing or a lot of administrative
           activity. This command finds files that do not belong in
           the spooling directory and removes them.

   disable printer-name

           Disable queuing of new jobs. If the printer is running, it
           will continue to print any jobs remaining in the queue.
           The superuser (root) can always submit jobs, even to a
           disabled queue.

           This command is useful while you are testing a new printer
           or filter installation: disable the queue and submit jobs
           as root. Other users will not be able to submit jobs until
           you complete your testing and re-enable the queue with the
           enable command.

   down printer-name message

           Take a printer down. Equivalent to disable followed by
           stop. The message appears as the printer's status whenever
           a user checks the printer's queue with lpq(1) or status
           with lpc status.

   enable printer-name

           Enable the queue for a printer. Users can submit jobs but
           the printer will not print anything until it is started.

   help command-name

           Print help on the command command-name. With no
           command-name, print a summary of the commands available.

   restart printer-name

           Start the printer. Ordinary users can use this command if
           some extraordinary circumstance hangs LPD, but they cannot
           start a printer stopped with either the stop or down
           commands. The restart command is equivalent to abort
           followed by start.

   start printer-name

           Start the printer. The printer will print jobs in its
           queue.

   stop printer-name

           Stop the printer. The printer will finish the current job
           and will not print anything else in its queue. Even though
           the printer is stopped, users can still submit jobs to an
           enabled queue.

   topq printer-name job-or-username

           Rearrange the queue for printer-name by placing the jobs
           with the listed job numbers or the jobs belonging to
           username at the top of the queue. For this command, you
           cannot use all as the printer-name.

   up printer-name

           Bring a printer up; the opposite of the down command.
           Equivalent to start followed by enable.

   lpc(8) accepts the above commands on the command line. If you do
   not enter any commands, lpc(8) enters an interactive mode, where
   you can enter commands until you type exit, quit, or end-of-file.

     --------------------------------------------------------------

9.6. Alternatives to the Standard Spooler

   If you have been reading straight through this manual, by now you
   have learned just about everything there is to know about the LPD
   spooling system that comes with FreeBSD. You can probably
   appreciate many of its shortcomings, which naturally leads to the
   question: !S:What other spooling systems are out there (and work
   with FreeBSD)?!"

   LPRng

           LPRng, which purportedly means !S:LPR: the Next
           Generation!" is a complete rewrite of PLP. Patrick Powell
           and Justin Mason (the principal maintainer of PLP)
           collaborated to make LPRng. The main site for LPRng is
           http://www.lprng.org/.

   CUPS

           CUPS, the Common UNIX Printing System, provides a portable
           printing layer for UNIX-based operating systems. It has
           been developed by Easy Software Products to promote a
           standard printing solution for all UNIX vendors and users.

           CUPS uses the Internet Printing Protocol (IPP) as the
           basis for managing print jobs and queues. The Line Printer
           Daemon (LPD), Server Message Block (SMB), and AppSocket
           (a.k.a. JetDirect) protocols are also supported with
           reduced functionality. CUPS adds network printer browsing
           and PostScript Printer Description (PPD) based printing
           options to support real-world printing under UNIX.

           The main site for CUPS is http://www.cups.org/.

     --------------------------------------------------------------

9.7. Troubleshooting

   After performing the simple test with lptest(1), you might have
   gotten one of the following results instead of the correct
   printout:

   It worked, after awhile; or, it did not eject a full sheet.

           The printer printed the above, but it sat for awhile and
           did nothing. In fact, you might have needed to press a
           PRINT REMAINING or FORM FEED button on the printer to get
           any results to appear.

           If this is the case, the printer was probably waiting to
           see if there was any more data for your job before it
           printed anything. To fix this problem, you can have the
           text filter send a FORM FEED character (or whatever is
           necessary) to the printer. This is usually sufficient to
           have the printer immediately print any text remaining in
           its internal buffer. It is also useful to make sure each
           print job ends on a full sheet, so the next job does not
           start somewhere on the middle of the last page of the
           previous job.

           The following replacement for the shell script
           /usr/local/libexec/if-simple prints a form feed after it
           sends the job to the printer:

 #!/bin/sh
 #
 # if-simple - Simple text input filter for lpd
 # Installed in /usr/local/libexec/if-simple
 #
 # Simply copies stdin to stdout.  Ignores all filter arguments.
 # Writes a form feed character (\f) after printing job.

 /bin/cat && printf "\f" && exit 0
 exit 2

   It produced the !S:staircase effect.!"

           You got the following on paper:

 !"#$%&'()*+,-./01234
                 "#$%&'()*+,-./012345
                                  #$%&'()*+,-./0123456

           You have become another victim of the staircase effect,
           caused by conflicting interpretations of what characters
           should indicate a new line. UNIX style operating systems
           use a single character: ASCII code 10, the line feed (LF).
           MS-DOS, OS/2(R), and others uses a pair of characters,
           ASCII code 10 and ASCII code 13 (the carriage return or
           CR). Many printers use the MS-DOS convention for
           representing new-lines.

           When you print with FreeBSD, your text used just the line
           feed character. The printer, upon seeing a line feed
           character, advanced the paper one line, but maintained the
           same horizontal position on the page for the next
           character to print. That is what the carriage return is
           for: to move the location of the next character to print
           to the left edge of the paper.

           Here is what FreeBSD wants your printer to do:

           Printer received CR         Printer prints CR              
           Printer received LF         Printer prints CR + LF         

           Here are some ways to achieve this:

              * Use the printer's configuration switches or control
                panel to alter its interpretation of these
                characters. Check your printer's manual to find out
                how to do this.

                  -a`: If you boot your system into other operating
                  systems besides FreeBSD, you may have to
                  reconfigure the printer to use a an interpretation
                  for CR and LF characters that those other operating
                  systems use. You might prefer one of the other
                  solutions, below.

              * Have FreeBSD's serial line driver automatically
                convert LF to CR+LF. Of course, this works with
                printers on serial ports only. To enable this
                feature, use the ms# capability and set the onlcr
                mode in the /etc/printcap file for the printer.

              * Send an escape code to the printer to have it
                temporarily treat LF characters differently. Consult
                your printer's manual for escape codes that your
                printer might support. When you find the proper
                escape code, modify the text filter to send the code
                first, then send the print job.

                Here is an example text filter for printers that
                understand the Hewlett-Packard PCL escape codes. This
                filter makes the printer treat LF characters as a LF
                and CR; then it sends the job; then it sends a form
                feed to eject the last page of the job. It should
                work with nearly all Hewlett Packard printers.

 #!/bin/sh
 #
 # hpif - Simple text input filter for lpd for HP-PCL based printers
 # Installed in /usr/local/libexec/hpif
 #
 # Simply copies stdin to stdout.  Ignores all filter arguments.
 # Tells printer to treat LF as CR+LF.  Ejects the page when done.

 printf "\033&k2G" && cat && printf "\033&l0H" && exit 0
 exit 2

                Here is an example /etc/printcap from a host called
                orchid. It has a single printer attached to its first
                parallel port, a Hewlett Packard LaserJet 3Si named
                teak. It is using the above script as its text
                filter:

 #
 #  /etc/printcap for host orchid
 #
 teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
         :lp=/dev/lpt0:sh:sd=/var/spool/lpd/teak:mx#0:\
         :if=/usr/local/libexec/hpif:

   It overprinted each line.

           The printer never advanced a line. All of the lines of
           text were printed on top of each other on one line.

           This problem is the !S:opposite!" of the staircase effect,
           described above, and is much rarer. Somewhere, the LF
           characters that FreeBSD uses to end a line are being
           treated as CR characters to return the print location to
           the left edge of the paper, but not also down a line.

           Use the printer's configuration switches or control panel
           to enforce the following interpretation of LF and CR
           characters:

                  Printer receives              Printer prints        
           CR                             CR                          
           LF                             CR + LF                     

   The printer lost characters.

           While printing, the printer did not print a few characters
           in each line. The problem might have gotten worse as the
           printer ran, losing more and more characters.

           The problem is that the printer cannot keep up with the
           speed at which the computer sends data over a serial line
           (this problem should not occur with printers on parallel
           ports). There are two ways to overcome the problem:

              * If the printer supports XON/XOFF flow control, have
                FreeBSD use it by specifying the ixon mode in the ms#
                capability.

              * If the printer supports carrier flow control, specify
                the crtscts mode in the ms# capability. Make sure the
                cable connecting the printer to the computer is
                correctly wired for carrier flow control.

   It printed garbage.

           The printer printed what appeared to be random garbage,
           but not the desired text.

           This is usually another symptom of incorrect
           communications parameters with a serial printer.
           Double-check the bps rate in the br capability, and the
           parity setting in the ms# capability; make sure the
           printer is using the same settings as specified in the
           /etc/printcap file.

   Nothing happened.

           If nothing happened, the problem is probably within
           FreeBSD and not the hardware. Add the log file (lf)
           capability to the entry for the printer you are debugging
           in the /etc/printcap file. For example, here is the entry
           for rattan, with the lf capability:

 rattan|line|diablo|lp|Diablo 630 Line Printer:\
         :sh:sd=/var/spool/lpd/rattan:\
         :lp=/dev/lpt0:\
         :if=/usr/local/libexec/if-simple:\
         :lf=/var/log/rattan.log

           Then, try printing again. Check the log file (in our
           example, /var/log/rattan.log) to see any error messages
           that might appear. Based on the messages you see, try to
           correct the problem.

           If you do not specify a lf capability, LPD uses
           /dev/console as a default.

     --------------------------------------------------------------

              ^3^1 10. >>P Linux Binary -a-oNOTU(R)eCURe+-

   Restructured and parts updated by Jim Mock. Originally contributed
   by Brian N. Handy YENB Rich Murphey.

10.1. .S:z

   FreeBSD |^3'-L-"N"a:YENL'X-oO/ UNIX like S:@.~"t^2I-a-o binary
   NOTU(R)e(c)E!A"a:CURCURYEN]NOTACURF Linux!C
   S:AYENi-`a.|-C,'e!GNOTDEGCURDEG>>o FreeBSD >>Yn-`aDEG-:DEGo|ae
   Linux +-MYENIDEGo|aeAE(binary)(c)O!Hu-a(R) *<<U:A^2^3ae!A ^3\|hCUR
   1/2YENq!BP:}uo-aIYENu.| Linux
   P:}uou{|!!A|]NOTDEG^3oNOTOYENO/<<e,eDEGTNOTE !S:^3I 1/4o:-au!"
   -a-o-a+-.N!C ^3o^1G+-o^3\|h FreeBSD
   "IYENI-aICUR-L-+-oCUR-L-YENhA:U>>!^3o"C,CURHNOTOS:_'-L-"NYENi-a
   1/2+-u|b FreeBSD CURWDEGo|ae-a-o-a(c)YEN>>!C |yDEGYADNOTO!ACURj|h
   1/4AECUR 1/2YENq"ACUR-L-AA,N.||^3|hCURO:CURH.|YENI FreeBSD
   -a(c)!A|]|^1YENLICUR'YENuP:}uo Linux -a(c)!C "-o>>o FreeBSD
   "IYENI-aI,O<<c,>>o?`i(c)O!Hu-a(R) *'NNOTOYENI FreeBSD
   (c)O'-L-"N-a-o Linux binary NOTU(R)e!C

   A^2^3ae"OA?!A^3o-oO/NOTU(R)e(c)EYENiAAy FreeBSD "IYENI-aI-a
   1/2+-uDEGo|aeNOTu 90% -a-o Linux u{|!!A|OCUR-L-YEN^2DEGuYENo|o
   *S:i!C ^3o"C,YEN]NOTACURF!G StarOffice!B Netscape -a-o Linux
   -a(c)!B Adobe Acrobat!B RealPlayer!B VMware(TM)!B Oracle!B
   WordPerfect(R)!BDoom!B Quake
   uYENuYEN!C|^1YEN~!ACUR]|^3CURH|^^3o/>>!|bNOTY"C,+-!-apCURU!A
   ^3o"C,|b FreeBSD CURWDEGo|ae-a-o Linux u{|!!ANOTAE|U:CURn`iYEN>>|b
   Linux DEGo|ae+-oS:o|n!C

   uM|O(c)O!AAUNOTO|^3"C,YENu Linux -S(c)w-a-oS:@.~"t^2IYEN\-`a!A|b
   FreeBSD CURW"AYEN 1/4CURa:'(c)!C |p-aG Linux
   u{|!^1L(c)oAYYENIYENu|^3 i386
   NOT[-ocCURWCUR~-`aYENI-a-oYEN\-`a!ACURn|p!GueAA 8086  1/4O|!!A
   <<hYENi-`auL-ak|b FreeBSD ^1BS:@YEN?+-`!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!G

     * |p|o+-OYENI Linux NOTU(R)e 1/4O|!!C

     * |p|o|w,EABYEN~-a-o Linux share libraries!C

     * |p|o|b FreeBSD CURW|w,E Linux u{|!!C

     * FreeBSD CURW-a-o Linux NOTU(R)e 1/4O|!-a-o^1eS:@^2O,`!C

   |b 3/4\AA-a^3o^3^1CURS:<<e!A+-zA^3.iCURF,N!G

     * -a 3/4^1D|p|o^3z^1L port  3/4-:"i"O|w,E^3nAAe(uU 4 ^3^1)!C

     --------------------------------------------------------------

10.2. |w,E

   ^1w^3]"ACUR-L-.|YEN'P:} Linux NOTU(R)e
   1/4O|!!A^3IA^2^3ae-a-o+-OYENICURe|!!A'NNOTO,u:CURJ linux KLD
   object (!S:Kernel LoaDable object!")!C ,u:CURJCURe|!!A
   1/2D-CURANOTDEG root AAv!AuM<<aYEN'CURU|C<<u:YENO!G

 # kldload linux

   Yn"C|,P:} 3/4-:^3-L-+-OYENI-a-o,U:!A
   1/2D-S:aCURU|CCUR-o(R)eYEN["`i /etc/rc.conf AE!G

 linux_enable="YES"

   YENtYEN~YENiYENHYENI kldstat(8) <<u:YENO!A"O 1/2T>>{|^3th"C, KLD
   |^3,u:CURJ!G

 % kldstat
 Id Refs Address    Size     Name
  1    2 0xc0100000 16bdb8   kernel
  7    1 0xc24db000 d000     linux.ko

   If for some reason you do not want to or cannot load the KLD, then
   you may statically link Linux binary compatibility into the kernel
   by adding options COMPAT_LINUX to your kernel configuration file.
   Then install your new kernel as described in uU 8 ^3^1.

     --------------------------------------------------------------

  10.2.1. Installing Linux Runtime Libraries

   This can be done one of two ways, either by using the linux_base
   port, or by installing them manually.

     --------------------------------------------------------------

    10.2.1.1. Installing Using the linux_base Port

   This is by far the easiest method to use when installing the
   runtime libraries. It is just like installing any other port from
   the Ports Collection. Simply do the following:

 # cd /usr/ports/emulators/linux_base-fc4
 # make install distclean

   You should now have working Linux binary compatibility. Some
   programs may complain about incorrect minor versions of the system
   libraries. In general, however, this does not seem to be a
   problem.

     -a`: There may be multiple versions of the emulators/linux_base
     port available, corresponding to different versions of various
     Linux distributions. You should install the port most closely
     resembling the requirements of the Linux applications you would
     like to install.

     --------------------------------------------------------------

    10.2.1.2. Installing Libraries Manually

   If you do not have the !S:ports!" collection installed, you can
   install the libraries by hand instead. You will need the Linux
   shared libraries that the program depends on and the runtime
   linker. Also, you will need to create a !S:shadow root!"
   directory, /compat/linux, for Linux libraries on your FreeBSD
   system. Any shared libraries opened by Linux programs run under
   FreeBSD will look in this tree first. So, if a Linux program
   loads, for example, /lib/libc.so, FreeBSD will first try to open
   /compat/linux/lib/libc.so, and if that does not exist, it will
   then try /lib/libc.so. Shared libraries should be installed in the
   shadow tree /compat/linux/lib rather than the paths that the Linux
   ld.so reports.

   Generally, you will need to look for the shared libraries that
   Linux binaries depend on only the first few times that you install
   a Linux program on your FreeBSD system. After a while, you will
   have a sufficient set of Linux shared libraries on your system to
   be able to run newly imported Linux binaries without any extra
   work.

     --------------------------------------------------------------

    10.2.1.3. How to Install Additional Shared Libraries

   What if you install the linux_base port and your application still
   complains about missing shared libraries? How do you know which
   shared libraries Linux binaries need, and where to get them?
   Basically, there are 2 possibilities (when following these
   instructions you will need to be root on your FreeBSD system).

   If you have access to a Linux system, see what shared libraries
   the application needs, and copy them to your FreeBSD system. Look
   at the following example:

   Let us assume you used FTP to get the Linux binary of Doom, and
   put it on a Linux system you have access to. You then can check
   which shared libraries it needs by running ldd linuxdoom, like so:

 % ldd linuxdoom
 libXt.so.3 (DLL Jump 3.1) => /usr/X11/lib/libXt.so.3.1.0
 libX11.so.3 (DLL Jump 3.1) => /usr/X11/lib/libX11.so.3.1.0
 libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29

   You would need to get all the files from the last column, and put
   them under /compat/linux, with the names in the first column as
   symbolic links pointing to them. This means you eventually have
   these files on your FreeBSD system:

 /compat/linux/usr/X11/lib/libXt.so.3.1.0
 /compat/linux/usr/X11/lib/libXt.so.3 -> libXt.so.3.1.0
 /compat/linux/usr/X11/lib/libX11.so.3.1.0
 /compat/linux/usr/X11/lib/libX11.so.3 -> libX11.so.3.1.0
 /compat/linux/lib/libc.so.4.6.29
 /compat/linux/lib/libc.so.4 -> libc.so.4.6.29

       -a`: Note that if you already have a Linux shared library with
       a matching major revision number to the first column of the
       ldd output, you will not need to copy the file named in the
       last column to your system, the one you already have should
       work. It is advisable to copy the shared library anyway if it
       is a newer version, though. You can remove the old one, as
       long as you make the symbolic link point to the new one. So,
       if you have these libraries on your system:

 /compat/linux/lib/libc.so.4.6.27
 /compat/linux/lib/libc.so.4 -> libc.so.4.6.27

       and you find a new binary that claims to require a later
       version according to the output of ldd:

 libc.so.4 (DLL Jump 4.5pl26) -> libc.so.4.6.29

       If it is only one or two versions out of date in the in the
       trailing digit then do not worry about copying
       /lib/libc.so.4.6.29 too, because the program should work fine
       with the slightly older version. However, if you like, you can
       decide to replace the libc.so anyway, and that should leave
       you with:

 /compat/linux/lib/libc.so.4.6.29
 /compat/linux/lib/libc.so.4 -> libc.so.4.6.29

       -a`: The symbolic link mechanism is only needed for Linux
       binaries. The FreeBSD runtime linker takes care of looking for
       matching major revision numbers itself and you do not need to
       worry about it.

     --------------------------------------------------------------

  10.2.2. Installing Linux ELF Binaries

   ELF binaries sometimes require an extra step of !S:branding!". If
   you attempt to run an unbranded ELF binary, you will get an error
   message like the following:

 % ./my-linux-elf-binary
 ELF binary type not known
 Abort

   To help the FreeBSD kernel distinguish between a FreeBSD ELF
   binary from a Linux binary, use the brandelf(1) utility.

 % brandelf -t Linux my-linux-elf-binary

   The GNU toolchain now places the appropriate branding information
   into ELF binaries automatically, so this step should become
   increasingly unnecessary in the future.

     --------------------------------------------------------------

  10.2.3. Configuring the Hostname Resolver

   If DNS does not work or you get this message:

 resolv+: "bind" is an invalid keyword resolv+:
 "hosts" is an invalid keyword

   You will need to configure a /compat/linux/etc/host.conf file
   containing:

 order hosts, bind
 multi on

   The order here specifies that /etc/hosts is searched first and DNS
   is searched second. When /compat/linux/etc/host.conf is not
   installed, Linux applications find FreeBSD's /etc/host.conf and
   complain about the incompatible FreeBSD syntax. You should remove
   bind if you have not configured a name server using the
   /etc/resolv.conf file.

     --------------------------------------------------------------

10.3. Installing Mathematica(R)

   Updated for Mathematica 5.X by Boris Hollas.

   This document describes the process of installing the Linux
   version of Mathematica 5.X onto a FreeBSD system.

   The Linux version of Mathematica or Mathematica for Students can
   be ordered directly from Wolfram at http://www.wolfram.com/.

     --------------------------------------------------------------

  10.3.1. Running the Mathematica Installer

   First, you have to tell FreeBSD that Mathematica's Linux binaries
   use the Linux ABI. The easiest way to do so is to set the default
   ELF brand to Linux for all unbranded binaries with the command:

 # sysctl kern.fallback_elf_brand=3

   This will make FreeBSD assume that unbranded ELF binaries use the
   Linux ABI and so you should be able to run the installer straight
   from the CDROM.

   Now, copy the file MathInstaller to your hard drive:

 # mount /cdrom
 # cp /cdrom/Unix/Installers/Linux/MathInstaller /localdir/

   and in this file, replace /bin/sh in the first line by
   /compat/linux/bin/sh. This makes sure that the installer is
   executed by the Linux version of sh(1). Next, replace all
   occurrences of Linux) by FreeBSD) with a text editor or the script
   below in the next section. This tells the Mathematica installer,
   who calls uname -s to determine the operating system, to treat
   FreeBSD as a Linux-like operating system. Invoking MathInstaller
   will now install Mathematica.

     --------------------------------------------------------------

  10.3.2. Modifying the Mathematica Executables

   The shell scripts that Mathematica created during installation
   have to be modified before you can use them. If you chose
   /usr/local/bin as the directory to place the Mathematica
   executables in, you will find symlinks in this directory to files
   called math, mathematica, Mathematica, and MathKernel. In each of
   these, replace Linux) by FreeBSD) with a text editor or the
   following shell script:

 #!/bin/sh
 cd /usr/local/bin
 for i in math mathematica Mathematica MathKernel
   do sed 's/Linux)/FreeBSD)/g' $i > $i.tmp
   sed 's/\/bin\/sh/\/compat\/linux\/bin\/sh/g' $i.tmp > $i
   rm $i.tmp
   chmod a+x $i
 done

     --------------------------------------------------------------

  10.3.3. Obtaining Your Mathematica Password

   When you start Mathematica for the first time, you will be asked
   for a password. If you have not yet obtained a password from
   Wolfram, run the program mathinfo in the installation directory to
   obtain your !S:machine ID!". This machine ID is based solely on
   the MAC address of your first Ethernet card, so you cannot run
   your copy of Mathematica on different machines.

   When you register with Wolfram, either by email, phone or fax, you
   will give them the !S:machine ID!" and they will respond with a
   corresponding password consisting of groups of numbers.

     --------------------------------------------------------------

  10.3.4. Running the Mathematica Frontend over a Network

   Mathematica uses some special fonts to display characters not
   present in any of the standard font sets (integrals, sums, Greek
   letters, etc.). The X protocol requires these fonts to be install
   locally. This means you will have to copy these fonts from the
   CDROM or from a host with Mathematica installed to your local
   machine. These fonts are normally stored in
   /cdrom/Unix/Files/SystemFiles/Fonts on the CDROM, or
   /usr/local/mathematica/SystemFiles/Fonts on your hard drive. The
   actual fonts are in the subdirectories Type1 and X. There are
   several ways to use them, as described below.

   The first way is to copy them into one of the existing font
   directories in /usr/X11R6/lib/X11/fonts. This will require editing
   the fonts.dir file, adding the font names to it, and changing the
   number of fonts on the first line. Alternatively, you should also
   just be able to run mkfontdir(1) in the directory you have copied
   them to.

   The second way to do this is to copy the directories to
   /usr/X11R6/lib/X11/fonts:

 # cd /usr/X11R6/lib/X11/fonts
 # mkdir X
 # mkdir MathType1
 # cd /cdrom/Unix/Files/SystemFiles/Fonts
 # cp X/* /usr/X11R6/lib/X11/fonts/X
 # cp Type1/* /usr/X11R6/lib/X11/fonts/MathType1
 # cd /usr/X11R6/lib/X11/fonts/X
 # mkfontdir
 # cd ../MathType1
 # mkfontdir

   Now add the new font directories to your font path:

 # xset fp+ /usr/X11R6/lib/X11/fonts/X
 # xset fp+ /usr/X11R6/lib/X11/fonts/MathType1
 # xset fp rehash

   If you are using the Xorg server, you can have these font
   directories loaded automatically by adding them to your xorg.conf
   file.

     -a`: For XFree86 servers, the configuration file is XF86Config.

   If you do not already have a directory called
   /usr/X11R6/lib/X11/fonts/Type1, you can change the name of the
   MathType1 directory in the example above to Type1.

     --------------------------------------------------------------

10.4. Installing Maple(TM)

   Contributed by Aaron Kaplan. Thanks to Robert Getschmann.

   Maple(TM) is a commercial mathematics program similar to
   Mathematica. You must purchase this software from
   http://www.maplesoft.com/ and then register there for a license
   file. To install this software on FreeBSD, please follow these
   simple steps.

    1. Execute the INSTALL shell script from the product
       distribution. Choose the !S:RedHat!" option when prompted by
       the installation program. A typical installation directory
       might be /usr/local/maple.

    2. If you have not done so, order a license for Maple from Maple
       Waterloo Software (http://register.maplesoft.com/) and copy it
       to /usr/local/maple/license/license.dat.

    3. Install the FLEXlm license manager by running the INSTALL_LIC
       install shell script that comes with Maple. Specify the
       primary hostname for your machine for the license server.

    4. Patch the /usr/local/maple/bin/maple.system.type file with the
       following:

    ----- snip ------------------
 *** maple.system.type.orig      Sun Jul  8 16:35:33 2001
 --- maple.system.type   Sun Jul  8 16:35:51 2001
 ***************
 *** 72,77 ****
 --- 72,78 ----
           # the IBM RS/6000 AIX case
           MAPLE_BIN="bin.IBM_RISC_UNIX"
           ;;
 +     "FreeBSD"|\
       "Linux")
           # the Linux/x86 case
         # We have two Linux implementations, one for Red Hat and
    ----- snip end of patch -----

       Please note that after the "FreeBSD"|\ no other whitespace
       should be present.

       This patch instructs Maple to recognize !S:FreeBSD!" as a type
       of Linux system. The bin/maple shell script calls the
       bin/maple.system.type shell script which in turn calls uname
       -a to find out the operating system name. Depending on the OS
       name it will find out which binaries to use.

    5. Start the license server.

       The following script, installed as
       /usr/local/etc/rc.d/lmgrd.sh is a convenient way to start up
       lmgrd:

    ----- snip ------------

 #! /bin/sh
 PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin
 PATH=${PATH}:/usr/local/maple/bin:/usr/local/maple/FLEXlm/UNIX/LINUX
 export PATH

 LICENSE_FILE=/usr/local/maple/license/license.dat
 LOG=/var/log/lmgrd.log

 case "$1" in
 start)
         lmgrd -c ${LICENSE_FILE} 2>> ${LOG} 1>&2
         echo -n " lmgrd"
         ;;
 stop)
         lmgrd -c ${LICENSE_FILE} -x lmdown 2>> ${LOG} 1>&2
         ;;
 *)
         echo "Usage: `basename $0` {start|stop}" 1>&2
         exit 64
         ;;
 esac

 exit 0
    ----- snip ------------

    6. Test-start Maple:

 % cd /usr/local/maple/bin
 % ./xmaple

       You should be up and running. Make sure to write Maplesoft to
       let them know you would like a native FreeBSD version!

     --------------------------------------------------------------

  10.4.1. Common Pitfalls

     * The FLEXlm license manager can be a difficult tool to work
       with. Additional documentation on the subject can be found at
       http://www.globetrotter.com/.

     * lmgrd is known to be very picky about the license file and to
       core dump if there are any problems. A correct license file
       should look like this:

 # =======================================================
 # License File for UNIX Installations ("Pointer File")
 # =======================================================
 SERVER chillig ANY
 #USE_SERVER
 VENDOR maplelmg

 FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \
          PLATFORMS=i86_r ISSUER="Waterloo Maple Inc." \
          ISSUED=11-may-2000 NOTICE=" Technische Universitat Wien" \
          SN=XXXXXXXXX

         -a`: Serial number and key 'X''ed out. chillig is a
         hostname.

       Editing the license file works as long as you do not touch the
       !S:FEATURE!" line (which is protected by the license key).

     --------------------------------------------------------------

10.5. Installing MATLAB(R)

   Contributed by Dan Pelleg.

   This document describes the process of installing the Linux
   version of MATLAB(R) version 6.5 onto a FreeBSD system. It works
   quite well, with the exception of the Java Virtual Machine(TM)
   (see uU 10.5.3 ,`).

   The Linux version of MATLAB can be ordered directly from The
   MathWorks at http://www.mathworks.com. Make sure you also get the
   license file or instructions how to create it. While you are
   there, let them know you would like a native FreeBSD version of
   their software.

     --------------------------------------------------------------

  10.5.1. Installing MATLAB

   To install MATLAB, do the following:

    1. Insert the installation CD and mount it. Become root, as
       recommended by the installation script. To start the
       installation script type:

 # /compat/linux/bin/sh /cdrom/install

         '-L-YENU:: The installer is graphical. If you get errors
         about not being able to open a display, type setenv HOME
         ~USER, where USER is the user you did a su(1) as.

    2. When asked for the MATLAB root directory, type:
       /compat/linux/usr/local/matlab.

         '-L-YENU:: For easier typing on the rest of the installation
         process, type this at your shell prompt: set
         MATLAB=/compat/linux/usr/local/matlab

    3. Edit the license file as instructed when obtaining the MATLAB
       license.

         '-L-YENU:: You can prepare this file in advance using your
         favorite editor, and copy it to $MATLAB/license.dat before
         the installer asks you to edit it.

    4. Complete the installation process.

   At this point your MATLAB installation is complete. The following
   steps apply !S:glue!" to connect it to your FreeBSD system.

     --------------------------------------------------------------

  10.5.2. License Manager Startup

    1. Create symlinks for the license manager scripts:

 # ln -s $MATLAB/etc/lmboot /usr/local/etc/lmboot_TMW
 # ln -s $MATLAB/etc/lmdown /usr/local/etc/lmdown_TMW

    2. Create a startup file at /usr/local/etc/rc.d/flexlm.sh. The
       example below is a modified version of the distributed
       $MATLAB/etc/rc.lm.glnx86. The changes are file locations, and
       startup of the license manager under Linux emulation.

 #!/bin/sh
 case "$1" in
   start)
         if [ -f /usr/local/etc/lmboot_TMW ]; then
               /compat/linux/bin/sh /usr/local/etc/lmboot_TMW -u username && echo 'MATLAB_lmgrd'
         fi
         ;;
   stop)
         if [ -f /usr/local/etc/lmdown_TMW ]; then
             /compat/linux/bin/sh /usr/local/etc/lmdown_TMW  > /dev/null 2>&1
         fi
         ;;
   *)
         echo "Usage: $0 {start|stop}"
         exit 1
         ;;
 esac

 exit 0

         <<n: The file must be made executable:

 # chmod +x /usr/local/etc/rc.d/flexlm.sh

         You must also replace username above with the name of a
         valid user on your system (and not root).

    3. Start the license manager with the command:

 # /usr/local/etc/rc.d/flexlm.sh start

     --------------------------------------------------------------

  10.5.3. Linking the Java Runtime Environment

   Change the Java Runtime Environment (JRE) link to one working
   under FreeBSD:

 # cd $MATLAB/sys/java/jre/glnx86/
 # unlink jre; ln -s ./jre1.1.8 ./jre

     --------------------------------------------------------------

  10.5.4. Creating a MATLAB Startup Script

    1. Place the following startup script in /usr/local/bin/matlab:

 #!/bin/sh
 /compat/linux/bin/sh /compat/linux/usr/local/matlab/bin/matlab "$@"

    2. Then type the command chmod +x /usr/local/bin/matlab.

     '-L-YENU:: Depending on your version of emulators/linux_base,
     you may run into errors when running this script. To avoid that,
     edit the file /compat/linux/usr/local/matlab/bin/matlab, and
     change the line that says:

 if [ `expr "$lscmd" : '.*->.*'` -ne 0 ]; then

     (in version 13.0.1 it is on line 410) to this line:

 if test -L $newbase; then

     --------------------------------------------------------------

  10.5.5. Creating a MATLAB Shutdown Script

   The following is needed to solve a problem with MATLAB not exiting
   correctly.

    1. Create a file $MATLAB/toolbox/local/finish.m, and in it put
       the single line:

 ! $MATLAB/bin/finish.sh

         -a`: The $MATLAB is literal.

         '-L-YENU:: In the same directory, you will find the files
         finishsav.m and finishdlg.m, which let you save your
         workspace before quitting. If you use either of them, insert
         the line above immediately after the save command.

    2. Create a file $MATLAB/bin/finish.sh, which will contain the
       following:

 #!/usr/compat/linux/bin/sh
 (sleep 5; killall -1 matlab_helper) &
 exit 0

    3. Make the file executable:

 # chmod +x $MATLAB/bin/finish.sh

     --------------------------------------------------------------

  10.5.6. Using MATLAB

   At this point you are ready to type matlab and start using it.

     --------------------------------------------------------------

10.6. Installing Oracle(R)

   Contributed by Marcel Moolenaar.

     --------------------------------------------------------------

  10.6.1. Preface

   This document describes the process of installing Oracle 8.0.5 and
   Oracle 8.0.5.1 Enterprise Edition for Linux onto a FreeBSD
   machine.

     --------------------------------------------------------------

  10.6.2. Installing the Linux Environment

   Make sure you have both emulators/linux_base and
   devel/linux_devtools from the Ports Collection installed. If you
   run into difficulties with these ports, you may have to use the
   packages or older versions available in the Ports Collection.

   If you want to run the intelligent agent, you will also need to
   install the Red Hat Tcl package: tcl-8.0.3-20.i386.rpm. The
   general command for installing packages with the official RPM port
   (archivers/rpm) is:

 # rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm package

   Installation of the package should not generate any errors.

     --------------------------------------------------------------

  10.6.3. Creating the Oracle Environment

   Before you can install Oracle, you need to set up a proper
   environment. This document only describes what to do specially to
   run Oracle for Linux on FreeBSD, not what has been described in
   the Oracle installation guide.

     --------------------------------------------------------------

    10.6.3.1. Kernel Tuning

   As described in the Oracle installation guide, you need to set the
   maximum size of shared memory. Do not use SHMMAX under FreeBSD.
   SHMMAX is merely calculated out of SHMMAXPGS and PGSIZE. Therefore
   define SHMMAXPGS. All other options can be used as described in
   the guide. For example:

 options SHMMAXPGS=10000
 options SHMMNI=100
 options SHMSEG=10
 options SEMMNS=200
 options SEMMNI=70
 options SEMMSL=61

   Set these options to suit your intended use of Oracle.

   Also, make sure you have the following options in your kernel
   configuration file:

 options SYSVSHM #SysV shared memory
 options SYSVSEM #SysV semaphores
 options SYSVMSG #SysV interprocess communication

     --------------------------------------------------------------

    10.6.3.2. Oracle Account

   Create an oracle account just as you would create any other
   account. The oracle account is special only that you need to give
   it a Linux shell. Add /compat/linux/bin/bash to /etc/shells and
   set the shell for the oracle account to /compat/linux/bin/bash.

     --------------------------------------------------------------

    10.6.3.3. Environment

   Besides the normal Oracle variables, such as ORACLE_HOME and
   ORACLE_SID you must set the following environment variables:

      Variable                           Value                        
   LD_LIBRARY_PATH $ORACLE_HOME/lib                                   
   CLASSPATH       $ORACLE_HOME/jdbc/lib/classes111.zip               
                   /compat/linux/bin /compat/linux/sbin               
   PATH            /compat/linux/usr/bin /compat/linux/usr/sbin /bin  
                   /sbin /usr/bin /usr/sbin /usr/local/bin            
                   $ORACLE_HOME/bin                                   

   It is advised to set all the environment variables in .profile. A
   complete example is:

 ORACLE_BASE=/oracle; export ORACLE_BASE
 ORACLE_HOME=/oracle; export ORACLE_HOME
 LD_LIBRARY_PATH=$ORACLE_HOME/lib
 export LD_LIBRARY_PATH
 ORACLE_SID=ORCL; export ORACLE_SID
 ORACLE_TERM=386x; export ORACLE_TERM
 CLASSPATH=$ORACLE_HOME/jdbc/lib/classes111.zip
 export CLASSPATH
 PATH=/compat/linux/bin:/compat/linux/sbin:/compat/linux/usr/bin
 PATH=$PATH:/compat/linux/usr/sbin:/bin:/sbin:/usr/bin:/usr/sbin
 PATH=$PATH:/usr/local/bin:$ORACLE_HOME/bin
 export PATH

     --------------------------------------------------------------

  10.6.4. Installing Oracle

   Due to a slight inconsistency in the Linux emulator, you need to
   create a directory named .oracle in /var/tmp before you start the
   installer. Let it be owned by the oracle user. You should be able
   to install Oracle without any problems. If you have problems,
   check your Oracle distribution and/or configuration first! After
   you have installed Oracle, apply the patches described in the next
   two subsections.

   A frequent problem is that the TCP protocol adapter is not
   installed right. As a consequence, you cannot start any TCP
   listeners. The following actions help solve this problem:

 # cd $ORACLE_HOME/network/lib
 # make -f ins_network.mk ntcontab.o
 # cd $ORACLE_HOME/lib
 # ar r libnetwork.a ntcontab.o
 # cd $ORACLE_HOME/network/lib
 # make -f ins_network.mk install

   Do not forget to run root.sh again!

     --------------------------------------------------------------

    10.6.4.1. Patching root.sh

   When installing Oracle, some actions, which need to be performed
   as root, are recorded in a shell script called root.sh. This
   script is written in the orainst directory. Apply the following
   patch to root.sh, to have it use to proper location of chown or
   alternatively run the script under a Linux native shell.

 *** orainst/root.sh.orig Tue Oct 6 21:57:33 1998
 --- orainst/root.sh Mon Dec 28 15:58:53 1998
 ***************
 *** 31,37 ****
 # This is the default value for CHOWN
 # It will redefined later in this script for those ports
 # which have it conditionally defined in ss_install.h
 ! CHOWN=/bin/chown
 #
 # Define variables to be used in this script
 --- 31,37 ----
 # This is the default value for CHOWN
 # It will redefined later in this script for those ports
 # which have it conditionally defined in ss_install.h
 ! CHOWN=/usr/sbin/chown
 #
 # Define variables to be used in this script

   When you do not install Oracle from CD, you can patch the source
   for root.sh. It is called rthd.sh and is located in the orainst
   directory in the source tree.

     --------------------------------------------------------------

    10.6.4.2. Patching genclntsh

   The script genclntsh is used to create a single shared client
   library. It is used when building the demos. Apply the following
   patch to comment out the definition of PATH:

 *** bin/genclntsh.orig Wed Sep 30 07:37:19 1998
 --- bin/genclntsh Tue Dec 22 15:36:49 1998
 ***************
 *** 32,38 ****
 #
 # Explicit path to ensure that we're using the correct commands
 #PATH=/usr/bin:/usr/ccs/bin export PATH
 ! PATH=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin export PATH
 #
 # each product MUST provide a $PRODUCT/admin/shrept.lst
 --- 32,38 ----
 #
 # Explicit path to ensure that we're using the correct commands
 #PATH=/usr/bin:/usr/ccs/bin export PATH
 ! #PATH=/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin export PATH
 #
 # each product MUST provide a $PRODUCT/admin/shrept.lst

     --------------------------------------------------------------

  10.6.5. Running Oracle

   When you have followed the instructions, you should be able to run
   Oracle as if it was run on Linux itself.

     --------------------------------------------------------------

10.7. Installing SAP(R) R/3(R)

   Contributed by Holger Kipp. Original version converted to SGML by
   Valentino Vaschetto.

   Installations of SAP Systems using FreeBSD will not be supported
   by the SAP support team !X!X they only offer support for certified
   platforms.

     --------------------------------------------------------------

  10.7.1. Preface

   This document describes a possible way of installing a SAP R/3
   System with Oracle Database for Linux onto a FreeBSD machine,
   including the installation of FreeBSD and Oracle. Two different
   configurations will be described:

     * SAP R/3 4.6B (IDES) with Oracle 8.0.5 on FreeBSD 4.3-STABLE

     * SAP R/3 4.6C with Oracle 8.1.7 on FreeBSD 4.5-STABLE

   Even though this document tries to describe all important steps in
   a greater detail, it is not intended as a replacement for the
   Oracle and SAP R/3 installation guides.

   Please see the documentation that comes with the SAP R/3 Linux
   edition for SAP and Oracle specific questions, as well as
   resources from Oracle and SAP OSS.

     --------------------------------------------------------------

  10.7.2. Software

   The following CD-ROMs have been used for SAP installations:

     --------------------------------------------------------------

    10.7.2.1. SAP R/3 4.6B, Oracle 8.0.5

    Name    Number                     Description                    
   KERNEL  51009113 SAP Kernel Oracle / Installation / AIX, Linux,    
                    Solaris                                           
   RDBMS   51007558 Oracle / RDBMS 8.0.5.X / Linux                    
   EXPORT1 51010208 IDES / DB-Export / Disc 1 of 6                    
   EXPORT2 51010209 IDES / DB-Export / Disc 2 of 6                    
   EXPORT3 51010210 IDES / DB-Export / Disc 3 of 6                    
   EXPORT4 51010211 IDES / DB-Export / Disc 4 of 6                    
   EXPORT5 51010212 IDES / DB-Export / Disc 5 of 6                    
   EXPORT6 51010213 IDES / DB-Export / Disc 6 of 6                    

   Additionally, we used the Oracle 8 Server (Pre-production version
   8.0.5 for Linux, Kernel Version 2.0.33) CD which is not really
   necessary, and FreeBSD 4.3-STABLE (it was only a few days past 4.3
   RELEASE).

     --------------------------------------------------------------

    10.7.2.2. SAP R/3 4.6C SR2, Oracle 8.1.7

    Name    Number                     Description                    
   KERNEL  51014004 SAP Kernel Oracle / SAP Kernel Version 4.6D /     
                    DEC, Linux                                        
   RDBMS   51012930 Oracle 8.1.7/ RDBMS / Linux                       
   EXPORT1 51013953 Release 4.6C SR2 / Export / Disc 1 of 4           
   EXPORT1 51013953 Release 4.6C SR2 / Export / Disc 2 of 4           
   EXPORT1 51013953 Release 4.6C SR2 / Export / Disc 3 of 4           
   EXPORT1 51013953 Release 4.6C SR2 / Export / Disc 4 of 4           
   LANG1   51013954 Release 4.6C SR2 / Language / DE, EN, FR / Disc 1 
                    of 3                                              

   Depending on the languages you would like to install, additional
   language CDs might be necessary. Here we are just using DE and EN,
   so the first language CD is the only one needed. As a little note,
   the numbers for all four EXPORT CDs are identical. All three
   language CDs also have the same number (this is different from the
   4.6B IDES release CD numbering). At the time of writing this
   installation is running on FreeBSD 4.5-STABLE (20.03.2002).

     --------------------------------------------------------------

  10.7.3. SAP Notes

   The following notes should be read before installing SAP R/3 and
   proved to be useful during installation:

     --------------------------------------------------------------

    10.7.3.1. SAP R/3 4.6B, Oracle 8.0.5

     Number                            Title                          
   0171356    SAP Software on Linux: Essential Comments               
   0201147    INST: 4.6C R/3 Inst. on UNIX - Oracle                   
   0373203    Update / Migration Oracle 8.0.5 --> 8.0.6/8.1.6 LINUX   
   0072984    Release of Digital UNIX 4.0B for Oracle                 
   0130581    R3SETUP step DIPGNTAB terminates                        
   0144978    Your system has not been installed correctly            
   0162266    Questions and tips for R3SETUP on Windows NT / W2K      

     --------------------------------------------------------------

    10.7.3.2. SAP R/3 4.6C, Oracle 8.1.7

      Number                            Title                         
   0015023       Initializing table TCPDB (RSXP0004) (EBCDIC)         
   0045619       R/3 with several languages or typefaces              
   0171356       SAP Software on Linux: Essential Comments            
   0195603       RedHat 6.1 Enterprise version: Known problems        
   0212876       The new archiving tool SAPCAR                        
   0300900       Linux: Released DELL Hardware                        
   0377187       RedHat 6.2: important remarks                        
   0387074       INST: R/3 4.6C SR2 Installation on UNIX              
   0387077       INST: R/3 4.6C SR2 Inst. on UNIX - Oracle            
   0387078       SAP Software on UNIX: OS Dependencies 4.6C SR2       

     --------------------------------------------------------------

  10.7.4. Hardware Requirements

   The following equipment is sufficient for the installation of a
   SAP R/3 System. For production use, a more exact sizing is of
   course needed:

       Component               4.6B                    4.6C           
   Processor         2 x 800MHz Pentium III   2 x 800MHz Pentium III  
   Memory            1GB ECC                  2GB ECC                 
   Hard Disk Space   50-60GB (IDES)           50-60GB (IDES)          

   For use in production, Xeon Processors with large cache,
   high-speed disk access (SCSI, RAID hardware controller), USV and
   ECC-RAM is recommended. The large amount of hard disk space is due
   to the preconfigured IDES System, which creates 27 GB of database
   files during installation. This space is also sufficient for
   initial production systems and application data.

     --------------------------------------------------------------

    10.7.4.1. SAP R/3 4.6B, Oracle 8.0.5

   The following off-the-shelf hardware was used: a dual processor
   board with 2 800 MHz Pentium III processors, Adaptec(R) 29160
   Ultra160 SCSI adapter (for accessing a 40/80 GB DLT tape drive and
   CDROM), Mylex(R) AcceleRAID(TM) (2 channels, firmware 6.00-1-00
   with 32 MB RAM). To the Mylex RAID controller are attached two
   17 GB hard disks (mirrored) and four 36 GB hard disks (RAID level
   5).

     --------------------------------------------------------------

    10.7.4.2. SAP R/3 4.6C, Oracle 8.1.7

   For this installation a Dell(TM) PowerEdge(TM) 2500 was used: a
   dual processor board with two 1000 MHz Pentium III processors
   (256 kB Cache), 2 GB PC133 ECC SDRAM, PERC/3 DC PCI RAID
   Controller with 128 MB, and an EIDE DVD-ROM drive. To the RAID
   controller are attached two 18 GB hard disks (mirrored) and four
   36 GB hard disks (RAID level 5).

     --------------------------------------------------------------

  10.7.5. Installation of FreeBSD

   First you have to install FreeBSD. There are several ways to do
   this, for more information read the uU 2.13 ,`.

     --------------------------------------------------------------

    10.7.5.1. Disk Layout

   To keep it simple, the same disk layout both for the SAP R/3 46B
   and SAP R/3 46C SR2 installation was used. Only the device names
   changed, as the installations were on different hardware (/dev/da
   and /dev/amr respectively, so if using an AMI MegaRAID(R), one
   will see /dev/amr0s1a instead of /dev/da0s1a):

    File system   Size (1k-blocks)  Size (GB)        Mounted on       
   /dev/da0s1a   1.016.303          1          /                      
   /dev/da0s1b                      6          swap                   
   /dev/da0s1e   2.032.623          2          /var                   
   /dev/da0s1f   8.205.339          8          /usr                   
   /dev/da1s1e   45.734.361         45         /compat/linux/oracle   
   /dev/da1s1f   2.032.623          2          /compat/linux/sapmnt   
   /dev/da1s1g   2.032.623          2          /compat/linux/usr/sap  

   Configure and initialize the two logical drives with the Mylex or
   PERC/3 RAID software beforehand. The software can be started
   during the BIOS boot phase.

   Please note that this disk layout differs slightly from the SAP
   recommendations, as SAP suggests mounting the Oracle
   subdirectories (and some others) separately !X!X we decided to
   just create them as real subdirectories for simplicity.

     --------------------------------------------------------------

    10.7.5.2. make world and a New Kernel

   Download the latest -STABLE sources. Rebuild world and your custom
   kernel after configuring your kernel configuration file. Here you
   should also include the kernel parameters which are required for
   both SAP R/3 and Oracle.

     --------------------------------------------------------------

  10.7.6. Installing the Linux Environment

    10.7.6.1. Installing the Linux Base System

   First the linux_base port needs to be installed (as root):

 # cd /usr/ports/emulators/linux_base
 # make install distclean

     --------------------------------------------------------------

    10.7.6.2. Installing Linux Development Environment

   The Linux development environment is needed, if you want to
   install Oracle on FreeBSD according to the uU 10.6 ,`:

 # cd /usr/ports/devel/linux_devtools
 # make install distclean

   The Linux development environment has only been installed for the
   SAP R/3 46B IDES installation. It is not needed, if the Oracle DB
   is not relinked on the FreeBSD system. This is the case if you are
   using the Oracle tarball from a Linux system.

     --------------------------------------------------------------

    10.7.6.3. Installing the Necessary RPMs

   To start the R3SETUP program, PAM support is needed. During the
   first SAP Installation on FreeBSD 4.3-STABLE we tried to install
   PAM with all the required packages and finally forced the
   installation of the PAM package, which worked. For SAP R/3 4.6C
   SR2 we directly forced the installation of the PAM RPM, which also
   works, so it seems the dependent packages are not needed:

 # rpm -i --ignoreos --nodeps --root /compat/linux --dbpath /var/lib/rpm \
 pam-0.68-7.i386.rpm

   For Oracle 8.0.5 to run the intelligent agent, we also had to
   install the RedHat Tcl package tcl-8.0.5-30.i386.rpm (otherwise
   the relinking during Oracle installation will not work). There are
   some other issues regarding relinking of Oracle, but that is a
   Oracle Linux issue, not FreeBSD specific.

     --------------------------------------------------------------

    10.7.6.4. Some Additional Hints

   It might also be a good idea to add linprocfs to /etc/fstab, for
   more information, see the linprocfs(5) manual page. Another
   parameter to set is kern.fallback_elf_brand=3 which is done in the
   file /etc/sysctl.conf.

     --------------------------------------------------------------

  10.7.7. Creating the SAP R/3 Environment

    10.7.7.1. Creating the Necessary File Systems and Mountpoints

   For a simple installation, it is sufficient to create the
   following file systems:

                mount point                       size in GB          
   /compat/linux/oracle                   45 GB                       
   /compat/linux/sapmnt                   2 GB                        
   /compat/linux/usr/sap                  2 GB                        

   It is also necessary to created some links. Otherwise the SAP
   Installer will complain, as it is checking the created links:

 # ln -s /compat/linux/oracle /oracle
 # ln -s /compat/linux/sapmnt /sapmnt
 # ln -s /compat/linux/usr/sap /usr/sap

   Possible error message during installation (here with System PRD
   and the SAP R/3 4.6C SR2 installation):

 INFO 2002-03-19 16:45:36 R3LINKS_IND_IND SyLinkCreate:200
     Checking existence of symbolic link /usr/sap/PRD/SYS/exe/dbg to
     /sapmnt/PRD/exe. Creating if it does not exist...

 WARNING 2002-03-19 16:45:36 R3LINKS_IND_IND SyLinkCreate:400
     Link /usr/sap/PRD/SYS/exe/dbg exists but it points to file
     /compat/linux/sapmnt/PRD/exe instead of /sapmnt/PRD/exe. The
     program cannot go on as long as this link exists at this
     location. Move the link to another location.

 ERROR 2002-03-19 16:45:36 R3LINKS_IND_IND Ins_SetupLinks:0
     can not setup link '/usr/sap/PRD/SYS/exe/dbg' with content
     '/sapmnt/PRD/exe'

     --------------------------------------------------------------

    10.7.7.2. Creating Users and Directories

   SAP R/3 needs two users and three groups. The user names depend on
   the SAP system ID (SID) which consists of three letters. Some of
   these SIDs are reserved by SAP (for example SAP and NIX. For a
   complete list please see the SAP documentation). For the IDES
   installation we used IDS, for the 4.6C SR2 installation PRD, as
   that system is intended for production use. We have therefore the
   following groups (group IDs might differ, these are just the
   values we used with our installation):

       group ID         group name              description           
   100              dba                Data Base Administrator        
   101              sapsys             SAP System                     
   102              oper               Data Base Operator             

   For a default Oracle installation, only group dba is used. As oper
   group, one also uses group dba (see Oracle and SAP documentation
   for further information).

   We also need the following users:

    user    user name    generic  group   additional    description   
     ID                   name              groups    
   1000   idsadm/prdadm sidadm    sapsys oper         SAP             
                                                      Administrator   
   1002   oraids/oraprd orasid    dba    oper         Oracle          
                                                      Administrator   

   Adding the users with adduser(8) requires the following (please
   note shell and home directory) entries for !S:SAP Administrator!":

 Name: sidadm
 Password: ******
 Fullname: SAP Administrator SID
 Uid: 1000
 Gid: 101 (sapsys)
 Class:
 Groups: sapsys dba
 HOME: /home/sidadm
 Shell: bash  (/compat/linux/bin/bash)

   and for !S:Oracle Administrator!":

 Name: orasid
 Password: ******
 Fullname: Oracle Administrator SID
 Uid: 1002
 Gid: 100 (dba)
 Class:
 Groups: dba
 HOME: /oracle/sid
 Shell: bash  (/compat/linux/bin/bash)

   This should also include group oper in case you are using both
   groups dba and oper.

     --------------------------------------------------------------

    10.7.7.3. Creating Directories

   These directories are usually created as separate file systems.
   This depends entirely on your requirements. We choose to create
   them as simple directories, as they are all located on the same
   RAID 5 anyway:

   First we will set owners and rights of some directories (as user
   root):

 # chmod 775 /oracle
 # chmod 777 /sapmnt
 # chown root:dba /oracle
 # chown sidadm:sapsys /compat/linux/usr/sap
 # chmod 775 /compat/linux/usr/sap

   Second we will create directories as user orasid. These will all
   be subdirectories of /oracle/SID:

 # su - orasid
 # cd /oracle/SID
 # mkdir mirrlogA mirrlogB origlogA origlogB
 # mkdir sapdata1 sapdata2 sapdata3 sapdata4 sapdata5 sapdata6
 # mkdir saparch sapreorg
 # exit

   For the Oracle 8.1.7 installation some additional directories are
   needed:

 # su - orasid
 # cd /oracle
 # mkdir 805_32
 # mkdir client stage
 # mkdir client/80x_32
 # mkdir stage/817_32
 # cd /oracle/SID
 # mkdir 817_32

     -a`: The directory client/80x_32 is used with exactly this name.
     Do not replace the x with some number or anything.

   In the third step we create directories as user sidadm:

 # su - sidadm
 # cd /usr/sap
 # mkdir SID
 # mkdir trans
 # exit

     --------------------------------------------------------------

    10.7.7.4. Entries in /etc/services

   SAP R/3 requires some entries in file /etc/services, which will
   not be set correctly during installation under FreeBSD. Please add
   the following entries (you need at least those entries
   corresponding to the instance number !X!X in this case, 00. It
   will do no harm adding all entries from 00 to 99 for dp, gw, sp
   and ms). If you are going to use a SAProuter or need to access SAP
   OSS, you also need 99, as port 3299 is usually used for the
   SAProuter process on the target system:

 sapdp00    3200/tcp # SAP Dispatcher.      3200 + Instance-Number
 sapgw00  3300/tcp # SAP Gateway.         3300 + Instance-Number
 sapsp00  3400/tcp #                      3400 + Instance-Number
 sapms00  3500/tcp #                      3500 + Instance-Number
 sapmsSID 3600/tcp # SAP Message Server.  3600 + Instance-Number
 sapgw00s   4800/tcp # SAP Secure Gateway   4800 + Instance-Number

     --------------------------------------------------------------

    10.7.7.5. Necessary Locales

   SAP requires at least two locales that are not part of the default
   RedHat installation. SAP offers the required RPMs as download from
   their FTP server (which is only accessible if you are a customer
   with OSS access). See note 0171356 for a list of RPMs you need.

   It is also possible to just create appropriate links (for example
   from de_DE and en_US ), but we would not recommend this for a
   production system (so far it worked with the IDES system without
   any problems, though). The following locales are needed:

 de_DE.ISO-8859-1
 en_US.ISO-8859-1

   Create the links like this:

 # cd /compat/linux/usr/share/locale
 # ln -s de_DE de_DE.ISO-8859-1
 # ln -s en_US en_US.ISO-8859-1

   If they are not present, there will be some problems during the
   installation. If these are then subsequently ignored (by setting
   the STATUS of the offending steps to OK in file CENTRDB.R3S), it
   will be impossible to log onto the SAP system without some
   additional effort.

     --------------------------------------------------------------

    10.7.7.6. Kernel Tuning

   SAP R/3 systems need a lot of resources. We therefore added the
   following parameters to the kernel configuration file:

 # Set these for memory pigs (SAP and Oracle):
 options MAXDSIZ="(1024*1024*1024)"
 options DFLDSIZ="(1024*1024*1024)"
 # System V options needed.
 options SYSVSHM #SYSV-style shared memory
 options SHMMAXPGS=262144 #max amount of shared mem. pages
 #options SHMMAXPGS=393216 #use this for the 46C inst.parameters
 options SHMMNI=256 #max number of shared memory ident if.
 options SHMSEG=100 #max shared mem.segs per process
 options SYSVMSG #SYSV-style message queues
 options MSGSEG=32767 #max num. of mes.segments in system
 options MSGSSZ=32 #size of msg-seg. MUST be power of 2
 options MSGMNB=65535 #max char. per message queue
 options MSGTQL=2046 #max amount of msgs in system
 options SYSVSEM #SYSV-style semaphores
 options SEMMNU=256 #number of semaphore UNDO structures
 options SEMMNS=1024 #number of semaphores in system
 options SEMMNI=520 #number of semaphore identifiers
 options SEMUME=100       #number of UNDO keys

   The minimum values are specified in the documentation that comes
   from SAP. As there is no description for Linux, see the HP-UX
   section (32-bit) for further information. As the system for the
   4.6C SR2 installation has more main memory, the shared segments
   can be larger both for SAP and Oracle, therefore choose a larger
   number of shared memory pages.

     -a`: With the default installation of FreeBSD on i386, leave
     MAXDSIZ and DFLDSIZ at 1 GB maximum. Otherwise, strange errors
     like !S:ORA-27102: out of memory!" and !S:Linux Error: 12:
     Cannot allocate memory!" might happen.

     --------------------------------------------------------------

  10.7.8. Installing SAP R/3

    10.7.8.1. Preparing SAP CDROMs

   There are many CDROMs to mount and unmount during the
   installation. Assuming you have enough CDROM drives, you can just
   mount them all. We decided to copy the CDROMs contents to
   corresponding directories:

 /oracle/SID/sapreorg/cd-name

   where cd-name was one of KERNEL, RDBMS, EXPORT1, EXPORT2, EXPORT3,
   EXPORT4, EXPORT5 and EXPORT6 for the 4.6B/IDES installation, and
   KERNEL, RDBMS, DISK1, DISK2, DISK3, DISK4 and LANG for the 4.6C
   SR2 installation. All the filenames on the mounted CDs should be
   in capital letters, otherwise use the -g option for mounting. So
   use the following commands:

 # mount_cd9660 -g /dev/cd0a /mnt
 # cp -R /mnt/* /oracle/SID/sapreorg/cd-name
 # umount /mnt

     --------------------------------------------------------------

    10.7.8.2. Running the Installation Script

   First you have to prepare an install directory:

 # cd /oracle/SID/sapreorg
 # mkdir install
 # cd install

   Then the installation script is started, which will copy nearly
   all the relevant files into the install directory:

 # /oracle/SID/sapreorg/KERNEL/UNIX/INSTTOOL.SH

   The IDES installation (4.6B) comes with a fully customized SAP R/3
   demonstration system, so there are six instead of just three
   EXPORT CDs. At this point the installation template CENTRDB.R3S is
   for installing a standard central instance (R/3 and database), not
   the IDES central instance, so one needs to copy the corresponding
   CENTRDB.R3S from the EXPORT1 directory, otherwise R3SETUP will
   only ask for three EXPORT CDs.

   The newer SAP 4.6C SR2 release comes with four EXPORT CDs. The
   parameter file that controls the installation steps is
   CENTRAL.R3S. Contrary to earlier releases there are no separate
   installation templates for a central instance with or without
   database. SAP is using a separate template for database
   installation. To restart the installation later it is however
   sufficient to restart with the original file.

   During and after installation, SAP requires hostname to return the
   computer name only, not the fully qualified domain name. So either
   set the hostname accordingly, or set an alias with alias
   hostname='hostname -s' for both orasid and sidadm (and for root at
   least during installation steps performed as root). It is also
   possible to adjust the installed .profile and .login files of both
   users that are installed during SAP installation.

     --------------------------------------------------------------

    10.7.8.3. Start R3SETUP 4.6B

   Make sure LD_LIBRARY_PATH is set correctly:

 # export LD_LIBRARY_PATH=/oracle/IDS/lib:/sapmnt/IDS/exe:/oracle/805_32/lib

   Start R3SETUP as root from installation directory:

 # cd /oracle/IDS/sapreorg/install
 # ./R3SETUP -f CENTRDB.R3S

   The script then asks some questions (defaults in brackets,
   followed by actual input):

   Question             Default                        Input             
   Enter SAP [C11]                          IDSEnter                     
   System ID 
   Enter SAP                                                             
   Instance  [00]                           Enter
   Number    
   Enter                                                                 
   SAPMOUNT  [/sapmnt]                      Enter
   Directory 
   Enter                                                                 
   name of   
   SAP       [troubadix.domain.de]          Enter
   central   
   host      
   Enter                                                                 
   name of   [troubadix]                    Enter
   SAP db    
   host      
   Select                                                                
   character [1] (WE8DEC)                   Enter
   set       
   Enter                                                                 
   Oracle    
   server    
   version   
   (1)       
   Oracle    
   8.0.5,    
   (2)                                      1Enter
   Oracle    
   8.0.6,    
   (3)       
   Oracle    
   8.1.5,    
   (4)       
   Oracle    
   8.1.6     
   Extract                                                               
   Oracle    [1] (Yes, extract)             Enter
   Client    
   archive   
   Enter                                                                 
   path to   [/sapcd]                       /oracle/IDS/sapreorg/KERNEL
   KERNEL CD 
   Enter                                                                 
   path to   [/sapcd]                       /oracle/IDS/sapreorg/RDBMS
   RDBMS CD  
   Enter                                                                 
   path to   [/sapcd]                       /oracle/IDS/sapreorg/EXPORT1
   EXPORT1   
   CD        
   Directory                                                             
   to copy   [/oracle/IDS/sapreorg/CD4_DIR] Enter
   EXPORT1   
   CD        
   Enter                                                                 
   path to   [/sapcd]                       /oracle/IDS/sapreorg/EXPORT2
   EXPORT2   
   CD        
   Directory                                                             
   to copy   [/oracle/IDS/sapreorg/CD5_DIR] Enter
   EXPORT2   
   CD        
   Enter                                                                 
   path to   [/sapcd]                       /oracle/IDS/sapreorg/EXPORT3
   EXPORT3   
   CD        
   Directory                                                             
   to copy   [/oracle/IDS/sapreorg/CD6_DIR] Enter
   EXPORT3   
   CD        
   Enter                                                                 
   path to   [/sapcd]                       /oracle/IDS/sapreorg/EXPORT4
   EXPORT4   
   CD        
   Directory                                                             
   to copy   [/oracle/IDS/sapreorg/CD7_DIR] Enter
   EXPORT4   
   CD        
   Enter                                                                 
   path to   [/sapcd]                       /oracle/IDS/sapreorg/EXPORT5
   EXPORT5   
   CD        
   Directory                                                             
   to copy   [/oracle/IDS/sapreorg/CD8_DIR] Enter
   EXPORT5   
   CD        
   Enter                                                                 
   path to   [/sapcd]                       /oracle/IDS/sapreorg/EXPORT6
   EXPORT6   
   CD        
   Directory                                                             
   to copy   [/oracle/IDS/sapreorg/CD9_DIR] Enter
   EXPORT6   
   CD        
   Enter                                                                 
   amount of                                850Enter (in Megabytes)
   RAM for   
   SAP + DB  
   Service                                                               
   Entry     [3600]                         Enter
   Message   
   Server    
   Enter                                                                 
   Group-ID  [101]                          Enter
   of sapsys 
   Enter                                                                 
   Group-ID  [102]                          Enter
   of oper   
   Enter                                                                 
   Group-ID  [100]                          Enter
   of dba    
   Enter                                                                 
   User-ID   [1000]                         Enter
   of sidadm 
   Enter                                                                 
   User-ID   [1002]                         Enter
   of orasid 
   Number of                                                             
   parallel  [2]                            Enter
   procs     

   If you had not copied the CDs to the different locations, then the
   SAP installer cannot find the CD needed (identified by the
   LABEL.ASC file on the CD) and would then ask you to insert and
   mount the CD and confirm or enter the mount path.

   The CENTRDB.R3S might not be error free. In our case, it requested
   EXPORT4 CD again but indicated the correct key (6_LOCATION, then
   7_LOCATION etc.), so one can just continue with entering the
   correct values.

   Apart from some problems mentioned below, everything should go
   straight through up to the point where the Oracle database
   software needs to be installed.

     --------------------------------------------------------------

    10.7.8.4. Start R3SETUP 4.6C SR2

   Make sure LD_LIBRARY_PATH is set correctly. This is a different
   value from the 4.6B installation with Oracle 8.0.5:

 # export LD_LIBRARY_PATH=/sapmnt/PRD/exe:/oracle/PRD/817_32/lib

   Start R3SETUP as user root from installation directory:

 # cd /oracle/PRD/sapreorg/install
 # ./R3SETUP -f CENTRAL.R3S

   The script then asks some questions (defaults in brackets,
   followed by actual input):

          Question            Default                Input            
   Enter SAP System ID     [C11]          PRDEnter                    
   Enter SAP Instance      [00]           Enter                       
   Number                  
   Enter SAPMOUNT          [/sapmnt]      Enter                       
   Directory               
   Enter name of SAP       [majestix]     Enter                       
   central host            
   Enter Database System   [PRD]          PRDEnter                    
   ID                      
   Enter name of SAP db    [majestix]     Enter                       
   host                    
   Select character set    [1] (WE8DEC)   Enter                       
   Enter Oracle server                                                
   version (2) Oracle                     2Enter
   8.1.7                   
   Extract Oracle Client   [1] (Yes,      Enter                       
   archive                 extract)       
   Enter path to KERNEL CD [/sapcd]       /oracle/PRD/sapreorg/KERNEL 
   Enter amount of RAM for 2044           1800Enter (in Megabytes)    
   SAP + DB                
   Service Entry Message   [3600]         Enter                       
   Server                  
   Enter Group-ID of       [100]          Enter                       
   sapsys                  
   Enter Group-ID of oper  [101]          Enter                       
   Enter Group-ID of dba   [102]          Enter                       
   Enter User-ID of oraprd [1002]         Enter                       
   Enter User-ID of prdadm [1000]         Enter                       
   LDAP support                           3Enter (no support)         
   Installation step       [1] (continue) Enter                       
   completed               
   Choose installation     [1] (DB        Enter                       
   service                 inst,file)     

   So far, creation of users gives an error during installation in
   phases OSUSERDBSID_IND_ORA (for creating user orasid) and
   OSUSERSIDADM_IND_ORA (creating user sidadm).

   Apart from some problems mentioned below, everything should go
   straight through up to the point where the Oracle database
   software needs to be installed.

     --------------------------------------------------------------

  10.7.9. Installing Oracle 8.0.5

   Please see the corresponding SAP Notes and Oracle Readmes
   regarding Linux and Oracle DB for possible problems. Most if not
   all problems stem from incompatible libraries.

   For more information on installing Oracle, refer to the Installing
   Oracle chapter.

     --------------------------------------------------------------

    10.7.9.1. Installing the Oracle 8.0.5 with orainst

   If Oracle 8.0.5 is to be used, some additional libraries are
   needed for successfully relinking, as Oracle 8.0.5 was linked with
   an old glibc (RedHat 6.0), but RedHat 6.1 already uses a new
   glibc. So you have to install the following additional packages to
   ensure that linking will work:

   compat-libs-5.2-2.i386.rpm

   compat-glibc-5.2-2.0.7.2.i386.rpm

   compat-egcs-5.2-1.0.3a.1.i386.rpm

   compat-egcs-c++-5.2-1.0.3a.1.i386.rpm

   compat-binutils-5.2-2.9.1.0.23.1.i386.rpm

   See the corresponding SAP Notes or Oracle Readmes for further
   information. If this is no option (at the time of installation we
   did not have enough time to check this), one could use the
   original binaries, or use the relinked binaries from an original
   RedHat system.

   For compiling the intelligent agent, the RedHat Tcl package must
   be installed. If you cannot get tcl-8.0.3-20.i386.rpm, a newer one
   like tcl-8.0.5-30.i386.rpm for RedHat 6.1 should also do.

   Apart from relinking, the installation is straightforward:

 # su - oraids
 # export TERM=xterm
 # export ORACLE_TERM=xterm
 # export ORACLE_HOME=/oracle/IDS
 # cd $ORACLE_HOME/orainst_sap
 # ./orainst

   Confirm all screens with Enter until the software is installed,
   except that one has to deselect the Oracle On-Line Text Viewer, as
   this is not currently available for Linux. Oracle then wants to
   relink with i386-glibc20-linux-gcc instead of the available gcc,
   egcs or i386-redhat-linux-gcc .

   Due to time constrains we decided to use the binaries from an
   Oracle 8.0.5 PreProduction release, after the first attempt at
   getting the version from the RDBMS CD working, failed, and finding
   and accessing the correct RPMs was a nightmare at that time.

     --------------------------------------------------------------

    10.7.9.2. Installing the Oracle 8.0.5 Pre-production Release for
    Linux (Kernel 2.0.33)

   This installation is quite easy. Mount the CD, start the
   installer. It will then ask for the location of the Oracle home
   directory, and copy all binaries there. We did not delete the
   remains of our previous RDBMS installation tries, though.

   Afterwards, Oracle Database could be started with no problems.

     --------------------------------------------------------------

  10.7.10. Installing the Oracle 8.1.7 Linux Tarball

   Take the tarball oracle81732.tgz you produced from the
   installation directory on a Linux system and untar it to
   /oracle/SID/817_32/.

     --------------------------------------------------------------

  10.7.11. Continue with SAP R/3 Installation

   First check the environment settings of users idsamd (sidadm) and
   oraids (orasid). They should now both have the files .profile,
   .login and .cshrc which are all using hostname. In case the
   system's hostname is the fully qualified name, you need to change
   hostname to hostname -s within all three files.

     --------------------------------------------------------------

    10.7.11.1. Database Load

   Afterwards, R3SETUP can either be restarted or continued
   (depending on whether exit was chosen or not). R3SETUP then
   creates the tablespaces and loads the data (for 46B IDES, from
   EXPORT1 to EXPORT6, for 46C from DISK1 to DISK4) with R3load into
   the database.

   When the database load is finished (might take a few hours), some
   passwords are requested. For test installations, one can use the
   well known default passwords (use different ones if security is an
   issue!):

                Question                           Input              
   Enter Password for sapr3            sapEnter                       
   Confirum Password for sapr3         sapEnter                       
   Enter Password for sys              change_on_installEnter         
   Confirm Password for sys            change_on_installEnter         
   Enter Password for system           managerEnter                   
   Confirm Password for system         managerEnter                   

   At this point We had a few problems with dipgntab during the 4.6B
   installation.

     --------------------------------------------------------------

    10.7.11.2. Listener

   Start the Oracle Listener as user orasid as follows:

 % umask 0; lsnrctl start

   Otherwise you might get the error ORA-12546 as the sockets will
   not have the correct permissions. See SAP Note 072984.

     --------------------------------------------------------------

    10.7.11.3. Updating MNLS Tables

   If you plan to import non-Latin-1 languages into the SAP system,
   you have to update the Multi National Language Support tables.
   This is described in the SAP OSS Notes 15023 and 45619. Otherwise,
   you can skip this question during SAP installation.

     -a`: If you do not need MNLS, it is still necessary to check the
     table TCPDB and initializing it if this has not been done. See
     SAP note 0015023 and 0045619 for further information.

     --------------------------------------------------------------

  10.7.12. Post-installation Steps

    10.7.12.1. Request SAP R/3 License Key

   You have to request your SAP R/3 License Key. This is needed, as
   the temporary license that was installed during installation is
   only valid for four weeks. First get the hardware key. Log on as
   user idsadm and call saplicense:

 # /sapmnt/IDS/exe/saplicense -get

   Calling saplicense without parameters gives a list of options.
   Upon receiving the license key, it can be installed using:

 # /sapmnt/IDS/exe/saplicense -install

   You are then required to enter the following values:

 SAP SYSTEM ID   = SID, 3 chars
 CUSTOMER KEY    = hardware key, 11 chars
 INSTALLATION NO = installation, 10 digits
 EXPIRATION DATE = yyyymmdd, usually "99991231"
 LICENSE KEY     = license key, 24 chars

     --------------------------------------------------------------

    10.7.12.2. Creating Users

   Create a user within client 000 (for some tasks required to be
   done within client 000, but with a user different from users sap*
   and ddic). As a user name, We usually choose wartung (or service
   in English). Profiles required are sap_new and sap_all. For
   additional safety the passwords of default users within all
   clients should be changed (this includes users sap* and ddic).

     --------------------------------------------------------------

    10.7.12.3. Configure Transport System, Profile, Operation Modes,
    Etc.

   Within client 000, user different from ddic and sap*, do at least
   the following:

                            Task                          Transaction 
   Configure Transport System, e.g. as Stand-Alone        STMS        
   Transport Domain Entity                                
   Create / Edit Profile for System                       RZ10        
   Maintain Operation Modes and Instances                 RZ04        

   These and all the other post-installation steps are thoroughly
   described in SAP installation guides.

     --------------------------------------------------------------

    10.7.12.4. Edit initsid.sap (initIDS.sap)

   The file /oracle/IDS/dbs/initIDS.sap contains the SAP backup
   profile. Here the size of the tape to be used, type of compression
   and so on need to be defined. To get this running with sapdba /
   brbackup, we changed the following values:

 compress = hardware
 archive_function = copy_delete_save
 cpio_flags = "-ov --format=newc --block-size=128 --quiet"
 cpio_in_flags = "-iuv --block-size=128 --quiet"
 tape_size = 38000M
 tape_address = /dev/nsa0
 tape_address_rew = /dev/sa0

   Explanations:

   compress: The tape we use is a HP DLT1 which does hardware
   compression.

   archive_function: This defines the default behavior for saving
   Oracle archive logs: new logfiles are saved to tape, already saved
   logfiles are saved again and are then deleted. This prevents lots
   of trouble if you need to recover the database, and one of the
   archive-tapes has gone bad.

   cpio_flags: Default is to use -B which sets block size to
   5120 Bytes. For DLT Tapes, HP recommends at least 32 K block size,
   so we used --block-size=128 for 64 K. --format=newc is needed
   because we have inode numbers greater than 65535. The last option
   --quiet is needed as otherwise brbackup complains as soon as cpio
   outputs the numbers of blocks saved.

   cpio_in_flags: Flags needed for loading data back from tape.
   Format is recognized automatically.

   tape_size: This usually gives the raw storage capability of the
   tape. For security reason (we use hardware compression), the value
   is slightly lower than the actual value.

   tape_address: The non-rewindable device to be used with cpio.

   tape_address_rew: The rewindable device to be used with cpio.

     --------------------------------------------------------------

    10.7.12.5. Configuration Issues after Installation

   The following SAP parameters should be tuned after installation
   (examples for IDES 46B, 1 GB memory):

                    Name                             Value            
   ztta/roll_extension                     250000000                  
   abap/heap_area_dia                      300000000                  
   abap/heap_area_nondia                   400000000                  
   em/initial_size_MB                      256                        
   em/blocksize_kB                         1024                       
   ipc/shm_psize_40                        70000000                   

   SAP Note 0013026:

                   Name                             Value             
   ztta/dynpro_area                      2500000                      

   SAP Note 0157246:

                    Name                             Value            
   rdisp/ROLL_MAXFS                       16000                       
   rdisp/PG_MAXFS                         30000                       

     -a`: With the above parameters, on a system with 1 gigabyte of
     memory, one may find memory consumption similar to:

 Mem: 547M Active, 305M Inact, 109M Wired, 40M Cache, 112M Buf, 3492K Free

     --------------------------------------------------------------

  10.7.13. Problems during Installation

    10.7.13.1. Restart R3SETUP after Fixing a Problem

   R3SETUP stops if it encounters an error. If you have looked at the
   corresponding logfiles and fixed the error, you have to start
   R3SETUP again, usually selecting REPEAT as option for the last
   step R3SETUP complained about.

   To restart R3SETUP, just start it with the corresponding R3S file:

 # ./R3SETUP -f CENTRDB.R3S

   for 4.6B, or with

 # ./R3SETUP -f CENTRAL.R3S

   for 4.6C, no matter whether the error occurred with CENTRAL.R3S or
   DATABASE.R3S.

     -a`: At some stages, R3SETUP assumes that both database and SAP
     processes are up and running (as those were steps it already
     completed). Should errors occur and for example the database
     could not be started, you have to start both database and SAP by
     hand after you fixed the errors and before starting R3SETUP
     again.

     Do not forget to also start the Oracle listener again (as orasid
     with umask 0; lsnrctl start) if it was also stopped (for example
     due to a necessary reboot of the system).

     --------------------------------------------------------------

    10.7.13.2. OSUSERSIDADM_IND_ORA during R3SETUP

   If R3SETUP complains at this stage, edit the template file R3SETUP
   used at that time (CENTRDB.R3S (4.6B) or either CENTRAL.R3S or
   DATABASE.R3S (4.6C)). Locate [OSUSERSIDADM_IND_ORA] or search for
   the only STATUS=ERROR entry and edit the following values:

 HOME=/home/sidadm (was empty)
 STATUS=OK (had status ERROR)
        

   Then you can restart R3SETUP again.

     --------------------------------------------------------------

    10.7.13.3. OSUSERDBSID_IND_ORA during R3SETUP

   Possibly R3SETUP also complains at this stage. The error here is
   similar to the one in phase OSUSERSIDADM_IND_ORA. Just edit the
   template file R3SETUP used at that time (CENTRDB.R3S (4.6B) or
   either CENTRAL.R3S or DATABASE.R3S (4.6C)). Locate
   [OSUSERDBSID_IND_ORA] or search for the only STATUS=ERROR entry
   and edit the following value in that section:

 STATUS=OK

   Then restart R3SETUP.

     --------------------------------------------------------------

    10.7.13.4. !S:oraview.vrf FILE NOT FOUND!" during Oracle
    Installation

   You have not deselected Oracle On-Line Text Viewer before starting
   the installation. This is marked for installation even though this
   option is currently not available for Linux. Deselect this product
   inside the Oracle installation menu and restart installation.

     --------------------------------------------------------------

    10.7.13.5. !S:TEXTENV_INVALID!" during R3SETUP, RFC or SAPgui Start

   If this error is encountered, the correct locale is missing. SAP
   Note 0171356 lists the necessary RPMs that need be installed (e.g.
   saplocales-1.0-3, saposcheck-1.0-1 for RedHat 6.1). In case you
   ignored all the related errors and set the corresponding STATUS
   from ERROR to OK (in CENTRDB.R3S) every time R3SETUP complained
   and just restarted R3SETUP, the SAP system will not be properly
   configured and you will then not be able to connect to the system
   with a SAPgui, even though the system can be started. Trying to
   connect with the old Linux SAPgui gave the following messages:

 Sat May 5 14:23:14 2001
 *** ERROR => no valid userarea given [trgmsgo. 0401]
 Sat May 5 14:23:22 2001
 *** ERROR => ERROR NR 24 occured [trgmsgi. 0410]
 *** ERROR => Error when generating text environment. [trgmsgi. 0435]
 *** ERROR => function failed [trgmsgi. 0447]
 *** ERROR => no socket operation allowed [trxio.c 3363]
 Speicherzugriffsfehler

   This behavior is due to SAP R/3 being unable to correctly assign a
   locale and also not being properly configured itself (missing
   entries in some database tables). To be able to connect to SAP,
   add the following entries to file DEFAULT.PFL (see Note 0043288):

 abap/set_etct_env_at_new_mode = 0
 install/collate/active = 0
 rscp/TCP0B = TCP0B

   Restart the SAP system. Now you can connect to the system, even
   though country-specific language settings might not work as
   expected. After correcting country settings (and providing the
   correct locales), these entries can be removed from DEFAULT.PFL
   and the SAP system can be restarted.

     --------------------------------------------------------------

    10.7.13.6. ORA-00001

   This error only happened with Oracle 8.1.7 on FreeBSD. The reason
   was that the Oracle database could not initialize itself properly
   and crashed, leaving semaphores and shared memory on the system.
   The next try to start the database then returned ORA-00001.

   Find them with ipcs -a and remove them with ipcrm.

     --------------------------------------------------------------

    10.7.13.7. ORA-00445 (Background Process PMON Did Not Start)

   This error happened with Oracle 8.1.7. This error is reported if
   the database is started with the usual startsap script (for
   example startsap_majestix_00) as user prdadm.

   A possible workaround is to start the database as user oraprd
   instead with svrmgrl:

 % svrmgrl
 SVRMGR> connect internal;
 SVRMGR> startup;
 SVRMGR> exit

     --------------------------------------------------------------

    10.7.13.8. ORA-12546 (Start Listener with Correct Permissions)

   Start the Oracle listener as user oraids with the following
   commands:

 # umask 0; lsnrctl start

   Otherwise you might get ORA-12546 as the sockets will not have the
   correct permissions. See SAP Note 0072984.

     --------------------------------------------------------------

    10.7.13.9. ORA-27102 (Out of Memory)

   This error happened whilst trying to use values for MAXDSIZ and
   DFLDSIZ greater than 1 GB (1024x1024x1024). Additionally, we got
   !S:Linux Error 12: Cannot allocate memory!".

     --------------------------------------------------------------

    10.7.13.10. [DIPGNTAB_IND_IND] during R3SETUP

   In general, see SAP Note 0130581 (R3SETUP step DIPGNTAB
   terminates). During the IDES-specific installation, for some
   reason the installation process was not using the proper SAP
   system name !S:IDS!", but the empty string "" instead. This leads
   to some minor problems with accessing directories, as the paths
   are generated dynamically using SID (in this case IDS). So instead
   of accessing:

 /usr/sap/IDS/SYS/...
 /usr/sap/IDS/DVMGS00

   the following paths were used:

 /usr/sap//SYS/...
 /usr/sap/D00

   To continue with the installation, we created a link and an
   additional directory:

 # pwd
 /compat/linux/usr/sap
 # ls -l
 total 4
 drwxr-xr-x 3  idsadm sapsys 512 May 5 11:20 D00
 drwxr-x--x 5  idsadm sapsys 512 May 5 11:35 IDS
 lrwxr-xr-x 1  root   sapsys 7 May 5 11:35 SYS -> IDS/SYS
 drwxrwxr-x 2  idsadm sapsys 512 May 5 13:00 tmp
 drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans

   We also found SAP Notes (0029227 and 0008401) describing this
   behavior. We did not encounter any of these problems with the SAP
   4.6C installation.

     --------------------------------------------------------------

    10.7.13.11. [RFCRSWBOINI_IND_IND] during R3SETUP

   During installation of SAP 4.6C, this error was just the result of
   another error happening earlier during installation. In this case,
   you have to look through the corresponding logfiles and correct
   the real problem.

   If after looking through the logfiles this error is indeed the
   correct one (check the SAP Notes), you can set STATUS of the
   offending step from ERROR to OK (file CENTRDB.R3S) and restart
   R3SETUP. After installation, you have to execute the report
   RSWBOINS from transaction SE38. See SAP Note 0162266 for
   additional information about phase RFCRSWBOINI and RFCRADDBDIF.

     --------------------------------------------------------------

    10.7.13.12. [RFCRADDBDIF_IND_IND] during R3SETUP

   Here the same restrictions apply: make sure by looking through the
   logfiles, that this error is not caused by some previous problems.

   If you can confirm that SAP Note 0162266 applies, just set STATUS
   of the offending step from ERROR to OK (file CENTRDB.R3S) and
   restart R3SETUP. After installation, you have to execute the
   report RADDBDIF from transaction SE38.

     --------------------------------------------------------------

    10.7.13.13. sigaction sig31: File size limit exceeded

   This error occurred during start of SAP processes disp+work. If
   starting SAP with the startsap script, subprocesses are then
   started which detach and do the dirty work of starting all other
   SAP processes. As a result, the script itself will not notice if
   something goes wrong.

   To check whether the SAP processes did start properly, have a look
   at the process status with ps ax | grep SID, which will give you a
   list of all Oracle and SAP processes. If it looks like some
   processes are missing or if you cannot connect to the SAP system,
   look at the corresponding logfiles which can be found at
   /usr/sap/SID/DVEBMGSnr/work/. The files to look at are dev_ms and
   dev_disp.

   Signal 31 happens here if the amount of shared memory used by
   Oracle and SAP exceed the one defined within the kernel
   configuration file and could be resolved by using a larger value:

 # larger value for 46C production systems:
 options SHMMAXPGS=393216
 # smaller value sufficient for 46B:
 #options SHMMAXPGS=262144

     --------------------------------------------------------------

    10.7.13.14. Start of saposcol Failed

   There are some problems with the program saposcol (version 4.6D).
   The SAP system is using saposcol to collect data about the system
   performance. This program is not needed to use the SAP system, so
   this problem can be considered a minor one. The older versions
   (4.6B) does work, but does not collect all the data (many calls
   will just return 0, for example for CPU usage).

     --------------------------------------------------------------

10.8. Advanced Topics

   If you are curious as to how the Linux binary compatibility works,
   this is the section you want to read. Most of what follows is
   based heavily on an email written to FreeBSD chat P:l>> 1/4 1/2 *
   3/4A by Terry Lambert <tlambert@primenet.com> (Message ID:
   <199906020108.SAA07001@usr09.primenet.com>).

     --------------------------------------------------------------

  10.8.1. How Does It Work?

   FreeBSD has an abstraction called an !S:execution class loader!".
   This is a wedge into the execve(2) system call.

   What happens is that FreeBSD has a list of loaders, instead of a
   single loader with a fallback to the #! loader for running any
   shell interpreters or shell scripts.

   Historically, the only loader on the UNIX platform examined the
   magic number (generally the first 4 or 8 bytes of the file) to see
   if it was a binary known to the system, and if so, invoked the
   binary loader.

   If it was not the binary type for the system, the execve(2) call
   returned a failure, and the shell attempted to start executing it
   as shell commands.

   The assumption was a default of !S:whatever the current shell
   is!".

   Later, a hack was made for sh(1) to examine the first two
   characters, and if they were :\n, then it invoked the csh(1) shell
   instead (we believe SCO first made this hack).

   What FreeBSD does now is go through a list of loaders, with a
   generic #! loader that knows about interpreters as the characters
   which follow to the next whitespace next to last, followed by a
   fallback to /bin/sh.

   For the Linux ABI support, FreeBSD sees the magic number as an ELF
   binary (it makes no distinction between FreeBSD, Solaris, Linux,
   or any other OS which has an ELF image type, at this point).

   The ELF loader looks for a specialized brand, which is a comment
   section in the ELF image, and which is not present on SVR4/Solaris
   ELF binaries.

   For Linux binaries to function, they must be branded as type Linux
   from brandelf(1):

 # brandelf -t Linux file

   When this is done, the ELF loader will see the Linux brand on the
   file.

   When the ELF loader sees the Linux brand, the loader replaces a
   pointer in the proc structure. All system calls are indexed
   through this pointer (in a traditional UNIX system, this would be
   the sysent[] structure array, containing the system calls). In
   addition, the process is flagged for special handling of the trap
   vector for the signal trampoline code, and several other (minor)
   fix-ups that are handled by the Linux kernel module.

   The Linux system call vector contains, among other things, a list
   of sysent[] entries whose addresses reside in the kernel module.

   When a system call is called by the Linux binary, the trap code
   dereferences the system call function pointer off the proc
   structure, and gets the Linux, not the FreeBSD, system call entry
   points.

   In addition, the Linux mode dynamically reroots lookups; this is,
   in effect, what the union option to file system mounts (not the
   unionfs file system type!) does. First, an attempt is made to
   lookup the file in the /compat/linux/original-path directory, then
   only if that fails, the lookup is done in the /original-path
   directory. This makes sure that binaries that require other
   binaries can run (e.g., the Linux toolchain can all run under
   Linux ABI support). It also means that the Linux binaries can load
   and execute FreeBSD binaries, if there are no corresponding Linux
   binaries present, and that you could place a uname(1) command in
   the /compat/linux directory tree to ensure that the Linux binaries
   could not tell they were not running on Linux.

   In effect, there is a Linux kernel in the FreeBSD kernel; the
   various underlying functions that implement all of the services
   provided by the kernel are identical to both the FreeBSD system
   call table entries, and the Linux system call table entries: file
   system operations, virtual memory operations, signal delivery,
   System V IPC, etc!K The only difference is that FreeBSD binaries
   get the FreeBSD glue functions, and Linux binaries get the Linux
   glue functions (most older OS's only had their own glue functions:
   addresses of functions in a static global sysent[] structure
   array, instead of addresses of functions dereferenced off a
   dynamically initialized pointer in the proc structure of the
   process making the call).

   Which one is the native FreeBSD ABI? It does not matter. Basically
   the only difference is that (currently; this could easily be
   changed in a future release, and probably will be after this) the
   FreeBSD glue functions are statically linked into the kernel, and
   the Linux glue functions can be statically linked, or they can be
   accessed via a kernel module.

   Yeah, but is this really emulation? No. It is an ABI
   implementation, not an emulation. There is no emulator (or
   simulator, to cut off the next question) involved.

   So why is it sometimes called !S:Linux emulation!"? To make it
   hard to sell FreeBSD! Really, it is because the historical
   implementation was done at a time when there was really no word
   other than that to describe what was going on; saying that FreeBSD
   ran Linux binaries was not true, if you did not compile the code
   in or load a module, and there needed to be a word to describe
   what was being loaded!X!Xhence !S:the Linux emulator!".

                           III. "t^2I-oTH^2z

   FreeBSD
   "IYENICURaYENU^3NCURU-a-o^3o"C,^3^1,`^2[>>\CURFYENthCURe|`i-a-o
   FreeBSD "t^2I-oTH^2z!C
   "CO^3^1,`-a-oP:}AY.|YENy'yz|b,O+-zAA-aS:^1,O^3^1,`<<a+-z.|
   3/4C,"`iCURDEG>>o!ACUR].|,Oz|b+-z|bNOTY^3o"C,,e(R)AE(R)EA^3,On|^3-a-oCUR@"C,I'-o-a
   3/4AN!C

   ^3o"C,^3^1,`NOTOAAy+-z|b>>YnNOTd,e(R)AE-a-o(R)EOA 1/2
   3/4\YENI-a-o!C
   +-zCUR-L->>Yn"I.O-S(c)w-a-oP:P:S:C,"OAA-a!ACUR]CUR-L->>Yn+-N^3o"C,^3^1,`YENth^3!^1LAA-aCURS:<<aCUR~P:}(c)lYENI
   FreeBSD!C

   CUR-o(R)eYENO/?y

   11. ^3](c)w>>P(R)A:-`a 1/2O(R)O(Tuning)

   12. FreeBSD P:} 3/4-:NOTyu{ 1/2g

   13. "IYENI-aI>>PDEGoYEN>>+-b,^1-oTH^2z

   14. "t^2I|wYENth

   15. Jails

   16. Mandatory Access Control

   17. Security Event Auditing

   18. Ax|s^3]^3AE 1/2g

   19. GEOM: Modular Disk Transformation Framework

   20. The Vinum Volume Manager

   21. Virtualization(ueAA 3/4-: 3/4^1)

   22. >>y"t^3](c)w - I18N/L10N YENI-ak>>P^3](c)w

   23. S:o.s!BCURE-AA FreeBSD

     --------------------------------------------------------------

              ^3^1 11. ^3](c)w>>P(R)A:-`a 1/2O(R)O(Tuning)

   Written by Chern Lee. Based on a tutorial written by Mike Smith.
   Also based on tuning(7) written by Matt Dillon.

11.1. .S:z

   |b FreeBSD
   "IYENI^1Lu{CURCUR!ANOTU.i<<n-a-oAo,`CURS:CUR@'NNOTO"t^2I^3](c)w^3!CURA!C
   YEN?
   1/2T-a-o"t^2I^3](c)w!AYENiYENHAAyS:A'i>>'CURe<<aCURE-AA-a-oAYuhA-L-CURO!C
   YEN>>^3^1uU<<(c)oCURP:^2D- FreeBSD
   -a-oNOTUAo:<<n^3](c)wCURW!AYEN]NOTACUR@"C,YENiYENH 1/2O 3/4a
   FreeBSD (R)A:-`a-a-oDEGN 1/4AE^3](c)w!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!G

     * |p|o|^3(R)A:^1BYENIAE(R) *"t^2IYENHCURI swap CURA^3IDEGI!C

     * rc.conf -a-o^3](c)w>>P /usr/local/etc/rc.d
       -a-o+-ODEGENOT[-oc!C

     * |p|o^3](c)w!B'u,O-oo,oYENd!C

     * |p|o^3](c)w virtual hosts!C

     * |p|o^3](c)w /etc CUR-o-a-o|U-oO/^3](c)wAE!C

     * |p|oYENH sysctl "O 1/2O 3/4a FreeBSD -a-o"t^2I(R)A:-`a!C

     * |p|o 1/2O 3/4auw-oD-(R)A:-`a!AYENHCURIS:oS:i kernel "i!C

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!J

     * AA,N UNIX CURI FreeBSD NOTUAo:DEGoYEN>>.S:(c)A(uU 3 ^3^1)!C

     * n|^3^3](c)w!B 1/2sA:P: kernel -a-oDEGoA|.S:(c)A(uU 8 ^3^1)!C

     --------------------------------------------------------------

11.2. CUR@P:}(c)l-a-o^3W^1-o

  11.2.1. ^3W^1-oCURA^3IDEGI(Partition)

     --------------------------------------------------------------

    11.2.1.1. Base Partitions

   YENI bsdlabel(8) (c)I sysinstall(8) "O^3W^1-oAE(R) *"t^2I(R)E!A
   1/2D-DEGO|i!G
   uw-oD-|bP:C,?e,e(R)AECURe+-!A(YENN(c)ou^2-ocNOTDEG-oD-CURu|]-A)YEN~DEGe.|CURnCUR-oDEGe"O+-oS:O:"C,!C
   |]|^1!A<<O/A:^3S:a,uCURp!B+-`.||s"u-a-oCURA^3IDEGI
   3/4"P:q(c)nYEN~DEGe!A|O,uCURj-a-oCURA^3IDEGI^1^3NOTO /usr
   <<hA^3(c)n|b,uCUR-oDEGe!C
   <<O/A:^3<<O/YENssCURA^3IDEGI-a-oP:P:S:C,!AYENH^1^3NOTO!Groot,
   swap, /var, /usr ^3o 1/4EP:P:S:C,"O<<O/YENss.|,uS:'!C

   /var -a-oCURjCURpnuo/ 3/4-: 3/4^1-a-oYENI^3~|O(c)w!C /var
   NOTOYENI"O(c)n <<H 1/2c!Blog NOTo:?yAEYENHCURI|L-ai
   3/4-:|i|C(spools)!C <<H 1/2cYENHCURIDEGO?yAE-a-o|"-ao/'T<<
   *YENi-`auL-ak^1w|o!A |]NOTDEG^3o"C,|"-ao/'T<<
   *CURDNOTO"u"M(c)o|hCURO:YENICURa!Bn(c)n|hCUR[uYEN-oTH^2z`i<<h|O(c)w!C
   ^3q+-`^3o"C,"IYENI-aI"A"S|^3YENI"`i 1 GB YENHCURW!A|y
   1/2D-CURADEGO!G|U:CURO:n<<O-dCUR@(c)w-aAAP:!u^1 /var/tmp
   YENH<<K|s(c)n packages!C

   |O /usr
   CURA^3IDEGIYENDnNOTOYENI"O(c)n"t^2I^1BS:@(R)E(c)O>>Y-a-oAE(R)
   *!BCURu"au{|!uYEN!A"O|p!G ports(7) collection(<<O/A:^3|w,E),o
   source tree(optional)!C |b|w,E FreeBSD
   (R)E!A^3o"a-aI^3-L-NOTOYENi?i 3/4U:,E>>PCUR-L-,E-a-o!C
   CUR-L-^1L!A^3oOCURA^3IDEGI<<O/A:^3|U:CURO:n|^3 2 GB
   -aAAP:!YENHCURWCUR~DEG-:YENI!C

   ^3W^1-oCURA^3IDEGICURjCURp(R)E!ADEGO+-o|h<<O-d"C,|"-ao/-aAAP:!!C
   S:_<<hYNOTYOCURA^3IDEGI-o!CURF!A|yYENtCUR@OCURA^3IDEGI<<oAU^3N<<U:|h-aAAP:!!A'N.|NOTU.iS:xu~!C

     -a`: |^3"C,CURHYENi-`a.|uo^2{ sysinstall(8) -a-o
     Auto-defaults(|UDEGE^1w^3]E) (c)ODEGu-a-oCURA^3IDEGICURjCURp!A
     |^3(R)EO.|S:a /var YENHCURI / CURA^3IDEGI^3]CUROCURpCURF!C
     S:UI<<O/A:^3NOTO!G 1/2D-"I"IYENI+-!-apYENHCURI>>Y"D!A"OCURaDEGE
     1/2O 3/4aNOTUAo:CURA^3IDEGICURjCURp!C

     --------------------------------------------------------------

    11.2.1.2. Swap CURA^3IDEGI

   (R)U 3/4U,gAAc,-ak<<h!A^3q+-` swap
   CURA^3IDEGIA^3,O^3]NOTDEG"t^2IDEGO
   3/4D-AAe(RAM)CURjCURp-a-o"a?S:YYENi!C A|"O"O>>!!GY 3/4-: 3/4^1|^3
   128 MB RAM -a-o,U:!A"-o>>o swap <<hA^3,O^3]NOTDEG 256 MB!C DEGO
   3/4D-AAe,uCURO:-a-o 3/4-: 3/4^1!AYENiYENH^3z^1L 1/4WYEN[S:o|h swap
   -aAAP:!"O'-L--a@(R)A:-`a!C S:UI<<O/A:^3 swap
   -aAAP:!CUR-L-n^3]S:C(c)o 256 MB!A|OYENB,O|O 1/4{ 1/4WYEN[DEGO
   3/4D-AAeCUR~NOTO"}u|!C .i swap ^3ICURO:NOTDEGDEGO
   3/4D-AAe-a-o"a?CURj(R)E!Akernel -a-o VM paging
   -ot-oa-ak.|S:a(R)A:-`a 1/2O 3/4a"`i^3I"I-aNOT-oA!C |yYNOTO 3/4-:
   3/4^1DEGO 3/4D-AAe<<U:CURj!A|y swap
   <<o^1-oCURACUROCURO:-a-o,U:!A.| 3/4EP VM page +-
   1/2-oE-a-o(R)A:^2v^1LS:C!A |^1YEN~CURe<<aY 1/4WYEN[S:o|hDEGO
   3/4D-AAe(R)E!ACUR].| 3/4EPCUR@"C,^2S:+-`-aNOT-apuoYENI!C

   |b,uCURj<<NOT-a-o 3/4-: 3/4^1CUR-o!A^3q+-`.||^3|hAu SCSI
   -oI-oD-((c)I|hAu IDE -oI-oD-+-u|bCUR-L-|P IDE P: *NOTy+-AECURW)!A
   <<O/A:^3|b"CAu-oI-oD-CURW^3-L-<<O/YENss swap(^3I|h"`iYEN|Au)!C
   |O^3o"C, swap A^3,O^3-L-CURjNOTuCUR@ 1/4ECURjCURp!A Kernel
   YENi+-u"u:YENo.NCURjCURp-a-o
   swap!A|yCUR-o^3!,e(R)AEu^2-oc<<hNOTO^3ICURjP:o swap -a-o 4 ?!C
   Y|^3<<O<<u swap NOTDEG|P 1/4ECURjCURp-a-o,U:!A<<hYENiAAy kernel
   ^3I"ICURAE^1BYENI|U-oI-oD-CURS:CURCUR-a-o swap -aAAP:!!C
   S:Y"ICUR-L-CURO+-`.|YENI"`i!ACURADEGtCURj-a-o swap
   CUR]^3-L-AUYENi+-u"u:!A |]NOTDEGYEN|YENi|b+-j"i<<P:}
   3/4-:CURS:<<eAAyS:AS:o(R)e(c)o:+-q.i+-
   1/4-a-ou{|!CURCUR<<`i'_YEN?+-`!C

     --------------------------------------------------------------

    11.2.1.3. NOTDEG|on^3W^1-o Partition!H

   |^3"C,CURHA:+-+-oS:auw-oD-'N-a
   1/2+-u^1-oCURACUR@OCURjCURA^3IDEGI'N|nCURF!A
   |yNOTO"AE^1eCURW|^3"C,`i|].|AO(c)uNOTDEG|o^3oNOTOOA:eAICURl!A
   -oYENy!A"COCURA^3IDEGI^3-L-|^3CUR-L-|P-a-o^1BS:@-S(c)E!AS:aYEN|ICURAP:}-a-o,U:YENiYENHAAyAE(R)
   *"t^2I"O 1/2O 3/4a!C CURn|p!G / YENHCURI /usr
   CURA^3IDEGICURj|hYENuNOTOAA-a"u|OCURw!A CURn,uCURO:|b 1/4gCURJ!C
   |OAA-a 1/4g^3-L-<<U:AWAc-a-o<<hNOTO /var CURI /var/tmp!C

   By properly partitioning a system, fragmentation introduced in the
   smaller write heavy partitions will not bleed over into the
   mostly-read partitions. Keeping the write-loaded partitions closer
   to the disk's edge, will increase I/O performance in the
   partitions where it occurs the most. Now while I/O performance in
   the larger partitions may be needed, shifting them more toward the
   edge of the disk will not lead to a significant performance
   improvement over moving /var to the edge. Finally, there are
   safety concerns. A smaller, neater root partition which is mostly
   read-only has a greater chance of surviving a bad crash.

     --------------------------------------------------------------

11.3. ^3IYENDn-a-o^3](c)wAE

   The principal location for system configuration information is
   within /etc/rc.conf. This file contains a wide range of
   configuration information, principally used at system startup to
   configure the system. Its name directly implies this; it is
   configuration information for the rc* files.

   An administrator should make entries in the rc.conf file to
   override the default settings from /etc/defaults/rc.conf. The
   defaults file should not be copied verbatim to /etc - it contains
   default values, not examples. All system-specific changes should
   be made in the rc.conf file itself.

   A number of strategies may be applied in clustered applications to
   separate site-wide configuration from system-specific
   configuration in order to keep administration overhead down. The
   recommended approach is to place site-wide configuration into
   another file, such as /etc/rc.conf.site, and then include this
   file into /etc/rc.conf, which will contain only system-specific
   information.

   As rc.conf is read by sh(1) it is trivial to achieve this. For
   example:

     * rc.conf:

         . /etc/rc.conf.site
         hostname="node15.example.com"
         network_interfaces="fxp0 lo0"
         ifconfig_fxp0="inet 10.1.1.1"

     * rc.conf.site:

         defaultrouter="10.1.1.254"
         saver="daemon"
         blanktime="100"

   The rc.conf.site file can then be distributed to every system
   using rsync or a similar program, while the rc.conf file remains
   unique.

   Upgrading the system using sysinstall(8) or make world will not
   overwrite the rc.conf file, so system configuration information
   will not be lost.

     --------------------------------------------------------------

11.4. |U|!A^3YENIu{|!-a-o^3](c)wAE

   `i<<hCURW!A|w,E-a-o^3nAAe^3-L-.||^3"a:|U|^3-a-o^3](c)wAE!ACUR].||^3|UCURv-a-o(R)ae|!CURI>>y-ak!C
   |]|^1!A+-N"a:>>P"t^2ICURAP:}?WYENssNOTOYENo<<D+-`<<n-a-o"AE+-!!C|p|^1CUR@"O!A(R)MYENo-oTH^2zCURu"a+-NYENiYENH
   <<U:>>'(c)o:-a-oS:a:YENX^3o"C,^3](c)wAE"A-oTH^2z^3o"C,^3](c)wAE!C

   `i<<hCURW!A^3](c)wAE.|^3Q(c)n,m|b /usr/local/etc!C
   YNOTY^3nAAe-a-o^3](c)wAENOTDEG
   1/4AE^2^3|h!A"-o+-N.|"a:CURU<<O/YENssCUR@OYENO/?yYENH"N(c)n,m

   ^3q+-`!A.iCUR@O port (c)I package
   ^3Q|w,E-a-o|P(R)E!ACUR@"C,DEGoYEN>>-a-o^3](c)w 1/2d"O
   CUR].|CUR@"O:^3Q|w,E|U:|^1!C^3o"C, 1/2d"O^3q+-`.|^3QYENI .default
   DEGuNOTDEGDEGAEAE|W!C Y|w,E(R)E"S|^3|U|ae 1/4P:
   1/4g-a-o^3nAAe^3](c)wAE!A"-o>>o+-N.| 1/2AE>>sCUR@YEN-: .default
   ^3](c)w DEGuNOTDEG^1w^3]^3](c)wAE

   A|O"OCURl!AS:UI"ONOTYNOTY /usr/local/etc/apache!G

 -rw-r--r--  1 root  wheel   2184 May 20  1998 access.conf
 -rw-r--r--  1 root  wheel   2184 May 20  1998 access.conf.default
 -rw-r--r--  1 root  wheel   9555 May 20  1998 httpd.conf
 -rw-r--r--  1 root  wheel   9555 May 20  1998 httpd.conf.default
 -rw-r--r--  1 root  wheel  12205 May 20  1998 magic
 -rw-r--r--  1 root  wheel  12205 May 20  1998 magic.default
 -rw-r--r--  1 root  wheel   2700 May 20  1998 mime.types
 -rw-r--r--  1 root  wheel   2700 May 20  1998 mime.types.default
 -rw-r--r--  1 root  wheel   7980 May 20  1998 srm.conf
 -rw-r--r--  1 root  wheel   7933 May 20  1998 srm.conf.default

   srm.conf -a-oAE(R) *^3Q *S:i^1LCURF!A-o,<<a Apache -a-oS:o.s
   +-NCUR-L-.|^1i^3oOCURw *S:i^1L-a-o^3](c)wAEDEGuYENo|oAAU:DEGE!C

     --------------------------------------------------------------

11.5. |U-oO/ Services -a-o+-ODEGECURe|!

   Contributed by Tom Rhodes.

   Many users choose to install third party software on FreeBSD from
   the Ports Collection. In many of these situations it may be
   necessary to configure the software in a manner which will allow
   it to be started upon system initialization. Services, such as
   mail/postfix or www/apache13 are just two of the many software
   packages which may be started during system initialization. This
   section explains the procedures available for starting third party
   software.

   In FreeBSD, most included services, such as cron(8), are started
   through the system start up scripts. These scripts may differ
   depending on FreeBSD or vendor version; however, the most
   important aspect to consider is that their start up configuration
   can be handled through simple startup scripts.

   Before the advent of rc.d, applications would drop a simple start
   up script into the /usr/local/etc/rc.d directory which would be
   read by the system initialization scripts. These scripts would
   then be executed during the latter stages of system start up.

   While many individuals have spent hours trying to merge the old
   configuration style into the new system, the fact remains that
   some third party utilities still require a script simply dropped
   into the aforementioned directory. The subtle differences in the
   scripts depend whether or not rc.d is being used. Prior to
   FreeBSD 5.1 the old configuration style is used and in almost all
   cases a new style script would do just fine.

   While every script must meet some minimal requirements, most of
   the time these requirements are FreeBSD version agnostic. Each
   script must have a .sh extension appended to the end and every
   script must be executable by the system. The latter may be
   achieved by using the chmod command and setting the unique
   permissions of 755. There should also be, at minimal, an option to
   start the application and an option to stop the application.

   The simplest start up script would probably look a little bit like
   this one:

 #!/bin/sh
 echo -n ' utility'

 case "$1" in
 start)
         /usr/local/bin/utility
         ;;
 stop)
         kill -9 `cat /var/run/utility.pid`
         ;;
 *)
         echo "Usage: `basename $0` {start|stop}" >&2
         exit 64
         ;;
 esac

 exit 0

   This script provides for a stop and start option for the
   application hereto referred simply as utility.

   Could be started manually with:

 # /usr/local/etc/rc.d/utility.sh start

   While not all third party software requires the line in rc.conf,
   almost every day a new port will be modified to accept this
   configuration. Check the final output of the installation for more
   information on a specific application. Some third party software
   will provide start up scripts which permit the application to be
   used with rc.d; although, this will be discussed in the next
   section.

     --------------------------------------------------------------

  11.5.1. Extended Application Configuration

   Now that FreeBSD includes rc.d, configuration of application
   startup has become easier, and more featureful. Using the key
   words discussed in the rc.d section, applications may now be set
   to start after certain other services for example DNS; may permit
   extra flags to be passed through rc.conf in place of hard coded
   flags in the start up script, etc. A basic script may look similar
   to the following:

 #!/bin/sh
 #
 # PROVIDE: utility
 # REQUIRE: DAEMON
 # KEYWORD: shutdown

 . /etc/rc.subr

 name=utility
 rcvar=utility_pidfile

 command="/usr/local/sbin/utility"

 load_rc_config $name

 #
 # DO NOT CHANGE THESE DEFAULT VALUES HERE
 # SET THEM IN THE /etc/rc.conf FILE
 #
 utility_enable=${utility_enable-"NO"}
 pidfile=${utility_pidfile-"/var/run/utility.pid"}

 run_rc_command "$1"

   This script will ensure that the provided utility will be started
   after the daemon service. It also provides a method for setting
   and tracking the PID, or process ID file.

   This application could then have the following line placed in
   /etc/rc.conf:

 utility_enable="YES"

   This new method also allows for easier manipulation of the command
   line arguments, inclusion of the default functions provided in
   /etc/rc.subr, compatibility with the rcorder(8) utility and
   provides for easier configuration via the rc.conf file.

     --------------------------------------------------------------

  11.5.2. YENH Services "O+-ODEGE|U|! Services

   Other services, such as POP3 server daemons, IMAP, etc. could be
   started using the inetd(8). This involves installing the service
   utility from the Ports Collection with a configuration line
   appended to the /etc/inetd.conf file, or uncommenting one of the
   current configuration lines. Working with inetd and its
   configuration is described in depth in the inetd section.

   In some cases, it may be more plausible to use the cron(8) daemon
   to start system services. This approach has a number of advantages
   because cron runs these processes as the crontab's file owner.
   This allows regular users to start and maintain some applications.

   The cron utility provides a unique feature, @reboot, which may be
   used in place of the time specification. This will cause the job
   to be run when cron(8) is started, normally during system
   initialization.

     --------------------------------------------------------------

11.6. ^3](c)w cron

   Contributed by Tom Rhodes.

   FreeBSD ^3I|nYENI-a-oCURu"aCURS:CUR@'NNOTO cron(8)!C cron
   .||bI'-oCURU^1BS:@!A"ACUR-L-A_AENOTd /etc/crontab AEYENHCURI
   /var/cron/tabs YENO/?y!A"O.j'MNOTOS:_|^3.s crontab AE(R) *!C
   ^3o"C, crontab AE.||s(c)nCUR@"C,+-AEu{CURuS:@-a-o^3](c)w!A"Ou^1
   cron DEGo|ae!C

   cron
   u{|!!AYENi|P(R)E+-A:YENI"a-oO/CUR-L-|PAth<<NOT-a-o^3](c)wAE!G"t^2IYEN>>"-a-o
   crontab CURI"IYENI-aIYEN>>"-a-o
   crontab!C|O"a-oO/(R)ae|!DEGssCUR@(R)tS:O|b(c)o^2A:CUR>>A:ae-a-oCUR-L-|P!FIn
   the system crontab, the sixth field is the name of a user for the
   command to run as. This gives the system crontab the ability to
   run commands as any user. In a user crontab, the sixth field is
   the command to run, and all commands run as the user who created
   the crontab; this is an important security feature.

     -a`: User crontabs allow individual users to schedule tasks
     without the need for root privileges. Commands in a user's
     crontab run with the permissions of the user who owns the
     crontab.

     The root user can have a user crontab just like any other user.
     This one is different from /etc/crontab (the system crontab).
     Because of the system crontab, there is usually no need to
     create a user crontab for root.

   Let us take a look at the /etc/crontab file (the system crontab):

 # /etc/crontab - root's crontab for FreeBSD
 #
 # $FreeBSD: src/etc/crontab,v 1.32 2002/11/22 16:13:39 tom Exp $
 # (1)
 #
 SHELL=/bin/sh
 PATH=/etc:/bin:/sbin:/usr/bin:/usr/sbin (2)
 HOME=/var/log
 #
 #
 #minute hour    mday    month   wday    who     command (3)
 #
 #
 */5     *       *       *       *       root    /usr/libexec/atrun (4)

   (1)
           Like most FreeBSD configuration files, the # character
           represents a comment. A comment can be placed in the file
           as a reminder of what and why a desired action is
           performed. Comments cannot be on the same line as a
           command or else they will be interpreted as part of the
           command; they must be on a new line. Blank lines are
           ignored.
   (2)
           First, the environment must be defined. The equals (=)
           character is used to define any environment settings, as
           with this example where it is used for the SHELL, PATH,
           and HOME options. If the shell line is omitted, cron will
           use the default, which is sh. If the PATH variable is
           omitted, no default will be used and file locations will
           need to be absolute. If HOME is omitted, cron will use the
           invoking users home directory.
   (3)
           This line defines a total of seven fields. Listed here are
           the values minute, hour, mday, month, wday, who, and
           command. These are almost all self explanatory. minute is
           the time in minutes the command will be run. hour is
           similar to the minute option, just in hours. mday stands
           for day of the month. month is similar to hour and minute,
           as it designates the month. The wday option stands for day
           of the week. All these fields must be numeric values, and
           follow the twenty-four hour clock. The who field is
           special, and only exists in the /etc/crontab file. This
           field specifies which user the command should be run as.
           When a user installs his or her crontab file, they will
           not have this option. Finally, the command option is
           listed. This is the last field, so naturally it should
           designate the command to be executed.
   (4)
           This last line will define the values discussed above.
           Notice here we have a */5 listing, followed by several
           more * characters. These * characters mean
           !S:first-last!", and can be interpreted as every time. So,
           judging by this line, it is apparent that the atrun
           command is to be invoked by root every five minutes
           regardless of what day or month it is. For more
           information on the atrun command, see the atrun(8) manual
           page.

           Commands can have any number of flags passed to them;
           however, commands which extend to multiple lines need to
           be broken with the backslash !S:\!" continuation
           character.

   This is the basic set up for every crontab file, although there is
   one thing different about this one. Field number six, where we
   specified the username, only exists in the system /etc/crontab
   file. This field should be omitted for individual user crontab
   files.

     --------------------------------------------------------------

  11.6.1. CURuS:@+-AEu{(Crontab)-a-o+-AE(c)w>>P-oTH^2z

     <<n: You must not use the procedure described here to
     edit/install the system crontab. Simply use your favorite
     editor: the cron utility will notice that the file has changed
     and immediately begin using the updated version. See   this FAQ
     entry for more information.

   To install a freshly written user crontab, first use your favorite
   editor to create a file in the proper format, and then use the
   crontab utility. The most common usage is:

 % crontab crontab-file

   In this example, crontab-file is the filename of a crontab that
   was previously created.

   There is also an option to list installed crontab files: just pass
   the -l option to crontab and look over the output.

   For users who wish to begin their own crontab file from scratch,
   without the use of a template, the crontab -e option is available.
   This will invoke the selected editor with an empty file. When the
   file is saved, it will be automatically installed by the crontab
   command.

   If you later want to remove your user crontab completely, use
   crontab with the -r option.

     --------------------------------------------------------------

11.7. |b FreeBSD "IYENI rc

   Contributed by Tom Rhodes.

   +-q 2002 |~DEG_!AFreeBSD  3/4a|XCURF NetBSD -a-o rc.d 
   3/4-:"i"OS:@NOTDEG"t^2I-aADEGE+-ODEGE 3/4-:"i!C YENiYENH"`i
   /etc/rc.d YENO/?yCURUYENhNOTY!A<<U:|hAE(R)
   *^3-L-NOTODEGoYEN>>-aADEGE!AYENiYENHYENI start, stop CURI restart
   S:@NOTDEG"IYENI(R)E-a-o?iP:u!C
   A|O"OCURl!AYENiYENHYENICURU|C<<u:YENO"O<<.s+-ODEGE sshd(8)!G

 # /etc/rc.d/sshd restart

   "a:YENL-aADEGECUR]NOTOAth|u:S:@-ak!C.iuM!A -aADEGE^3q+-`YENun|b
   rc.conf(5) CUR-o|^3<<u:(c)w-a-o,U:!A^3-L-.||bP:}
   3/4-:(R)E'N|UDEGE+-ODEGE!CA|"O"O>>!!AYnP:} 3/4-:(R)E+-ODEGE
   NAT(Network Address Translation) daemon -a-o,U:!AYENun|b
   /etc/rc.conf CUR-oYEN[CURWCURU|C^3o|aeS:YYENi!G

 natd_enable="YES"

   Y`iYEN>> 1/4g-a-oNOTO natd_enable="NO" "-o>>oYENunS:a NO S:iNOTDEG
   YES 'N|nCURF!Crc scripts .||bCURU|,<<P:}
   3/4-:(R)E!A|UDEGE,u:CURJNOTUAo:(|^3NOTU"I)-a-o-aADEGE!AYENHCURUS:UI.|A?"`i^3o^3!CURA!C

   Since the rc.d system is primarily intended to start/stop services
   at system startup/shutdown time, the standard start, stop and
   restart options will only perform their action if the appropriate
   /etc/rc.conf variables are set. For instance the above sshd
   restart command will only work if sshd_enable is set to YES in
   /etc/rc.conf. To start, stop or restart a service regardless of
   the settings in /etc/rc.conf, the commands should be prefixed with
   !S:force!". For instance to restart sshd regardless of the current
   /etc/rc.conf setting, execute the following command:

 # /etc/rc.d/sshd forcerestart

   It is easy to check if a service is enabled in /etc/rc.conf by
   running the appropriate rc.d script with the option rcvar. Thus,
   an administrator can check that sshd is in fact enabled in
   /etc/rc.conf by running:

 # /etc/rc.d/sshd rcvar
 # sshd
 $sshd_enable=YES

     -a`: The second line (# sshd) is the output from the sshd
     command, not a root console.

   YnAENOTd-aADEGENOTOS:_|^3|b^1BS:@!AYENiYENHYENI status
   ?iP:u"ONOTd,ss!CCURn|p!GYn 1/2T>>{ sshd
   NOTOS:_-u-a-o|^3+-ODEGE-a-o,U:!A"-o>>oYEN'!G

 # /etc/rc.d/sshd status
 sshd is running as pid 433.

   In some cases it is also possible to reload a service. This will
   attempt to send a signal to an individual service, forcing the
   service to reload its configuration files. In most cases this
   means sending the service a SIGHUP signal. Support for this
   feature is not included for every service.

   The rc.d system is not only used for network services, it also
   contributes to most of the system initialization. For instance,
   consider the bgfsck file. When this script is executed, it will
   print out the following message:

 Starting background file system checks in 60 seconds.

   Therefore this file is used for background file system checks,
   which are done only during system initialization.

   Many system services depend on other services to function
   properly. For example, NIS and other RPC-based services may fail
   to start until after the rpcbind (portmapper) service has started.
   To resolve this issue, information about dependencies and other
   meta-data is included in the comments at the top of each startup
   script. The rcorder(8) program is then used to parse these
   comments during system initialization to determine the order in
   which system services should be invoked to satisfy the
   dependencies. The following words may be included at the top of
   each startup file:

     * PROVIDE: Specifies the services this file provides.

     * REQUIRE: Lists services which are required for this service.
       This file will run after the specified services.

     * BEFORE: Lists services which depend on this service. This file
       will run before the specified services.

   By using this method, an administrator can easily control system
   services without the hassle of !S:runlevels!" like some other UNIX
   operating systems.

   Additional information about the rc.d system can be found in the
   rc(8) and rc.subr(8) manual pages.

     --------------------------------------------------------------

11.8. ^3](c)w-oo,oYENd

   Contributed by Marc Fonvieille.

   Nowadays we can not think about a computer without thinking about
   a network connection. Adding and configuring a network card is a
   common task for any FreeBSD administrator.

     --------------------------------------------------------------

  11.8.1. ?i 3/4U:YEN? 1/2T!BYENiYENI-a-oAAXDEGEu{|!(Driver)

   Before you begin, you should know the model of the card you have,
   the chip it uses, and whether it is a PCI or ISA card. FreeBSD
   supports a wide variety of both PCI and ISA cards. Check the
   Hardware Compatibility List for your release to see if your card
   is supported.

   Once you are sure your card is supported, you need to determine
   the proper driver for the card. /usr/src/sys/conf/NOTES and
   /usr/src/sys/arch/conf/NOTES will give you the list of network
   interface drivers with some information about the supported
   chipsets/cards. If you have doubts about which driver is the
   correct one, read the manual page of the driver. The manual page
   will give you more information about the supported hardware and
   even the possible problems that could occur.

   If you own a common card, most of the time you will not have to
   look very hard for a driver. Drivers for common network cards are
   present in the GENERIC kernel, so your card should show up during
   boot, like so:

 dc0: <82c169 PNIC 10/100BaseTX> port 0xa000-0xa0ff mem 0xd3800000-0xd38
 000ff irq 15 at device 11.0 on pci0
 dc0: Ethernet address: 00:a0:cc:da:da:da
 miibus0: <MII bus> on dc0
 ukphy0: <Generic IEEE 802.3u media interface> on miibus0
 ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
 dc1: <82c169 PNIC 10/100BaseTX> port 0x9800-0x98ff mem 0xd3000000-0xd30
 000ff irq 11 at device 12.0 on pci0
 dc1: Ethernet address: 00:a0:cc:da:da:db
 miibus1: <MII bus> on dc1
 ukphy1: <Generic IEEE 802.3u media interface> on miibus1
 ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

   In this example, we see that two cards using the dc(4) driver are
   present on the system.

   If the driver for your NIC is not present in GENERIC, you will
   need to load the proper driver to use your NIC. This may be
   accomplished in one of two ways:

     * The easiest way is to simply load a kernel module for your
       network card with kldload(8), or automatically at boot time by
       adding the appropriate line to the file /boot/loader.conf. Not
       all NIC drivers are available as modules; notable examples of
       devices for which modules do not exist are ISA cards.

     * Alternatively, you may statically compile the support for your
       card into your kernel. Check /usr/src/sys/conf/NOTES,
       /usr/src/sys/arch/conf/NOTES and the manual page of the driver
       to know what to add in your kernel configuration file. For
       more information about recompiling your kernel, please see uU
       8 ^3^1. If your card was detected at boot by your kernel
       (GENERIC) you do not have to build a new kernel.

     --------------------------------------------------------------

    11.8.1.1. Using Windows NDIS Drivers

   Unfortunately, there are still many vendors that do not provide
   schematics for their drivers to the open source community because
   they regard such information as trade secrets. Consequently, the
   developers of FreeBSD and other operating systems are left two
   choices: develop the drivers by a long and pain-staking process of
   reverse engineering or using the existing driver binaries
   available for the Microsoft Windows platforms. Most developers,
   including those involved with FreeBSD, have taken the latter
   approach.

   Thanks to the contributions of Bill Paul (wpaul), as of
   FreeBSD 5.3-RELEASE there is !S:native!" support for the Network
   Driver Interface Specification (NDIS). The FreeBSD NDISulator
   (otherwise known as Project Evil) takes a Windows driver binary
   and basically tricks it into thinking it is running on Windows.
   Because the ndis(4) driver is using a Windows binary, it is only
   usable on i386 and amd64 systems.

     -a`: The ndis(4) driver is designed to support mainly PCI,
     CardBus and PCMCIA devices, USB devices are not yet supported.

   In order to use the NDISulator, you need three things:

    1. Kernel sources

    2. Windows XP driver binary (.SYS extension)

    3. Windows XP driver configuration file (.INF extension)

   Locate the files for your specific card. Generally, they can be
   found on the included CDs or at the vendors' websites. In the
   following examples, we will use W32DRIVER.SYS and W32DRIVER.INF.

     -a`: You can not use a Windows/i386 driver with FreeBSD/amd64,
     you must get a Windows/amd64 driver to make it work properly.

   The next step is to compile the driver binary into a loadable
   kernel module. To accomplish this, as root, use ndisgen(8):

 # ndisgen /path/to/W32DRIVER.INF /path/to/W32DRIVER.SYS

   The ndisgen(8) utility is interactive and will prompt for any
   extra information it requires; it will produce a kernel module in
   the current directory which can be loaded as follows:

 # kldload ./W32DRIVER.ko

   In addition to the generated kernel module, you must load the
   ndis.ko and if_ndis.ko modules. This should be automatically done
   when you load any module that depends on ndis(4). If you want to
   load them manually, use the following commands:

 # kldload ndis
 # kldload if_ndis

   The first command loads the NDIS miniport driver wrapper, the
   second loads the actual network interface.

   Now, check dmesg(8) to see if there were any errors loading. If
   all went well, you should get output resembling the following:

 ndis0: <Wireless-G PCI Adapter> mem 0xf4100000-0xf4101fff irq 3 at device 8.0 on pci1
 ndis0: NDIS API version: 5.0
 ndis0: Ethernet address: 0a:b1:2c:d3:4e:f5
 ndis0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
 ndis0: 11g rates: 6Mbps 9Mbps 12Mbps 18Mbps 36Mbps 48Mbps 54Mbps

   From here you can treat the ndis0 device like any other network
   interface (e.g., dc0).

   You can configure the system to load the NDIS modules at boot time
   in the same way as with any other module. First, copy the
   generated module, W32DRIVER.ko, to the /boot/modules directory.
   Then, add the following line to /boot/loader.conf:

 W32DRIVER_load="YES"

     --------------------------------------------------------------

  11.8.2. ^3](c)w-oo,oYENd

   Once the right driver is loaded for the network card, the card
   needs to be configured. As with many other things, the network
   card may have been configured at installation time by sysinstall.

   To display the configuration for the network interfaces on your
   system, enter the following command:

 % ifconfig
 dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255
         ether 00:a0:cc:da:da:da
         media: Ethernet autoselect (100baseTX <full-duplex>)
         status: active
 dc1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         inet 10.0.0.1 netmask 0xffffff00 broadcast 10.0.0.255
         ether 00:a0:cc:da:da:db
         media: Ethernet 10baseT/UTP
         status: no carrier
 lp0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500
 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
         inet 127.0.0.1 netmask 0xff000000
 tun0: flags=8010<POINTOPOINT,MULTICAST> mtu 1500

     -a`: Old versions of FreeBSD may require the -a option following
     ifconfig(8), for more details about the correct syntax of
     ifconfig(8), please refer to the manual page. Note also that
     entries concerning IPv6 (inet6 etc.) were omitted in this
     example.

   In this example, the following devices were displayed:

     * dc0: The first Ethernet interface

     * dc1: The second Ethernet interface

     * lp0: The parallel port interface

     * lo0: The loopback device

     * tun0: The tunnel device used by ppp

   FreeBSD uses the driver name followed by the order in which one
   the card is detected at the kernel boot to name the network card.
   For example sis2 would be the third network card on the system
   using the sis(4) driver.

   In this example, the dc0 device is up and running. The key
   indicators are:

    1. UP means that the card is configured and ready.

    2. The card has an Internet (inet) address (in this case
       192.168.1.3).

    3. It has a valid subnet mask (netmask; 0xffffff00 is the same as
       255.255.255.0).

    4. It has a valid broadcast address (in this case,
       192.168.1.255).

    5. The MAC address of the card (ether) is 00:a0:cc:da:da:da

    6. The physical media selection is on autoselection mode (media:
       Ethernet autoselect (100baseTX <full-duplex>)). We see that
       dc1 was configured to run with 10baseT/UTP media. For more
       information on available media types for a driver, please
       refer to its manual page.

    7. The status of the link (status) is active, i.e. the carrier is
       detected. For dc1, we see status: no carrier. This is normal
       when an Ethernet cable is not plugged into the card.

   If the ifconfig(8) output had shown something similar to:

 dc0: flags=8843<BROADCAST,SIMPLEX,MULTICAST> mtu 1500
                 ether 00:a0:cc:da:da:da

   it would indicate the card has not been configured.

   To configure your card, you need root privileges. The network card
   configuration can be done from the command line with ifconfig(8)
   but you would have to do it after each reboot of the system. The
   file /etc/rc.conf is where to add the network card's
   configuration.

   Open /etc/rc.conf in your favorite editor. You need to add a line
   for each network card present on the system, for example in our
   case, we added these lines:

 ifconfig_dc0="inet 192.168.1.3 netmask 255.255.255.0"
 ifconfig_dc1="inet 10.0.0.1 netmask 255.255.255.0 media 10baseT/UTP"

   You have to replace dc0, dc1, and so on, with the correct device
   for your cards, and the addresses with the proper ones. You should
   read the card driver and ifconfig(8) manual pages for more details
   about the allowed options and also rc.conf(5) manual page for more
   information on the syntax of /etc/rc.conf.

   If you configured the network during installation, some lines
   about the network card(s) may be already present. Double check
   /etc/rc.conf before adding any lines.

   You will also have to edit the file /etc/hosts to add the names
   and the IP addresses of various machines of the LAN, if they are
   not already there. For more information please refer to hosts(5)
   and to /usr/share/examples/etc/hosts.

     --------------------------------------------------------------

  11.8.3. 'u,O>>P-oAAo/+-AEDEG-L-

   Once you have made the necessary changes in /etc/rc.conf, you
   should reboot your system. This will allow the change(s) to the
   interface(s) to be applied, and verify that the system restarts
   without any configuration errors.

   Once the system has been rebooted, you should test the network
   interfaces.

     --------------------------------------------------------------

    11.8.3.1. 'u,OCURACURO-oo,oYENd(Ethernet Card)

   To verify that an Ethernet card is configured correctly, you have
   to try two things. First, ping the interface itself, and then ping
   another machine on the LAN.

   First test the local interface:

 % ping -c5 192.168.1.3
 PING 192.168.1.3 (192.168.1.3): 56 data bytes
 64 bytes from 192.168.1.3: icmp_seq=0 ttl=64 time=0.082 ms
 64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=0.074 ms
 64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=0.076 ms
 64 bytes from 192.168.1.3: icmp_seq=3 ttl=64 time=0.108 ms
 64 bytes from 192.168.1.3: icmp_seq=4 ttl=64 time=0.076 ms

 --- 192.168.1.3 ping statistics ---
 5 packets transmitted, 5 packets received, 0% packet loss
 round-trip min/avg/max/stddev = 0.074/0.083/0.108/0.013 ms

   Now we have to ping another machine on the LAN:

 % ping -c5 192.168.1.2
 PING 192.168.1.2 (192.168.1.2): 56 data bytes
 64 bytes from 192.168.1.2: icmp_seq=0 ttl=64 time=0.726 ms
 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.766 ms
 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.700 ms
 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.747 ms
 64 bytes from 192.168.1.2: icmp_seq=4 ttl=64 time=0.704 ms

 --- 192.168.1.2 ping statistics ---
 5 packets transmitted, 5 packets received, 0% packet loss
 round-trip min/avg/max/stddev = 0.700/0.729/0.766/0.025 ms

   You could also use the machine name instead of 192.168.1.2 if you
   have set up the /etc/hosts file.

     --------------------------------------------------------------

    11.8.3.2. -oAAo/+-AEDEG-L-

   Troubleshooting hardware and software configurations is always a
   pain, and a pain which can be alleviated by checking the simple
   things first. Is your network cable plugged in? Have you properly
   configured the network services? Did you configure the firewall
   correctly? Is the card you are using supported by FreeBSD? Always
   check the hardware notes before sending off a bug report. Update
   your version of FreeBSD to the latest STABLE version. Check the
   mailing list archives, or perhaps search the Internet.

   If the card works, yet performance is poor, it would be worthwhile
   to read over the tuning(7) manual page. You can also check the
   network configuration as incorrect network settings can cause slow
   connections.

   Some users experience one or two !S:device timeout!" messages,
   which is normal for some cards. If they continue, or are
   bothersome, you may wish to be sure the device is not conflicting
   with another device. Double check the cable connections. Perhaps
   you may just need to get another card.

   At times, users see a few !S:watchdog timeout!" errors. The first
   thing to do here is to check your network cable. Many cards
   require a PCI slot which supports Bus Mastering. On some old
   motherboards, only one PCI slot allows it (usually slot 0). Check
   the network card and the motherboard documentation to determine if
   that may be the problem.

   !S:No route to host!" messages occur if the system is unable to
   route a packet to the destination host. This can happen if no
   default route is specified, or if a cable is unplugged. Check the
   output of netstat -rn and make sure there is a valid route to the
   host you are trying to reach. If there is not, read on to uU 29
   ^3^1.

   !S:ping: sendto: Permission denied!" error messages are often
   caused by a misconfigured firewall. If ipfw is enabled in the
   kernel but no rules have been defined, then the default policy is
   to deny all traffic, even ping requests! Read on to uU 28 ^3^1 for
   more information.

   Sometimes performance of the card is poor, or below average. In
   these cases it is best to set the media selection mode from
   autoselect to the correct media selection. While this usually
   works for most hardware, it may not resolve this issue for
   everyone. Again, check all the network settings, and read over the
   tuning(7) manual page.

     --------------------------------------------------------------

11.9. ueAAYEND 3/4-:(Virtual Hosts)

   A very common use of FreeBSD is virtual site hosting, where one
   server appears to the network as many servers. This is achieved by
   assigning multiple network addresses to a single interface.

   A given network interface has one !S:real!" address, and may have
   any number of !S:alias!" addresses. These aliases are normally
   added by placing alias entries in /etc/rc.conf.

   An alias entry for the interface fxp0 looks like:

 ifconfig_fxp0_alias0="inet xxx.xxx.xxx.xxx netmask xxx.xxx.xxx.xxx"

   Note that alias entries must start with alias0 and proceed upwards
   in order, (for example, _alias1, _alias2, and so on). The
   configuration process will stop at the first missing number.

   The calculation of alias netmasks is important, but fortunately
   quite simple. For a given interface, there must be one address
   which correctly represents the network's netmask. Any other
   addresses which fall within this network must have a netmask of
   all 1s (expressed as either 255.255.255.255 or 0xffffffff).

   For example, consider the case where the fxp0 interface is
   connected to two networks, the 10.1.1.0 network with a netmask of
   255.255.255.0 and the 202.0.75.16 network with a netmask of
   255.255.255.240. We want the system to appear at 10.1.1.1 through
   10.1.1.5 and at 202.0.75.17 through 202.0.75.20. As noted above,
   only the first address in a given network range (in this case,
   10.0.1.1 and 202.0.75.17) should have a real netmask; all the rest
   (10.1.1.2 through 10.1.1.5 and 202.0.75.18 through 202.0.75.20)
   must be configured with a netmask of 255.255.255.255.

   The following /etc/rc.conf entries configure the adapter correctly
   for this arrangement:

 ifconfig_fxp0="inet 10.1.1.1 netmask 255.255.255.0"
 ifconfig_fxp0_alias0="inet 10.1.1.2 netmask 255.255.255.255"
 ifconfig_fxp0_alias1="inet 10.1.1.3 netmask 255.255.255.255"
 ifconfig_fxp0_alias2="inet 10.1.1.4 netmask 255.255.255.255"
 ifconfig_fxp0_alias3="inet 10.1.1.5 netmask 255.255.255.255"
 ifconfig_fxp0_alias4="inet 202.0.75.17 netmask 255.255.255.240"
 ifconfig_fxp0_alias5="inet 202.0.75.18 netmask 255.255.255.255"
 ifconfig_fxp0_alias6="inet 202.0.75.19 netmask 255.255.255.255"
 ifconfig_fxp0_alias7="inet 202.0.75.20 netmask 255.255.255.255"

     --------------------------------------------------------------

11.10. AU|^3th"C,YENDn^3](c)wAE(c)O!H

  11.10.1. /etc Layout

   There are a number of directories in which configuration
   information is kept. These include:

   /etc                Generic system configuration information; data 
                       here is system-specific.                       
   /etc/defaults       Default versions of system configuration       
                       files.                                         
   /etc/mail           Extra sendmail(8) configuration, other MTA     
                       configuration files.                           
   /etc/ppp            Configuration for both user- and kernel-ppp    
                       programs.                                      
   /etc/namedb         Default location for named(8) data. Normally   
                       named.conf and zone files are stored here.     
                       Configuration files for installed              
   /usr/local/etc      applications. May contain per-application      
                       subdirectories.                                
   /usr/local/etc/rc.d Start/stop scripts for installed applications. 
                       Automatically generated system-specific        
   /var/db             database files, such as the package database,  
                       the locate database, and so on                 

     --------------------------------------------------------------

  11.10.2. Hostnames

     --------------------------------------------------------------

    11.10.2.1. /etc/resolv.conf

   /etc/resolv.conf dictates how FreeBSD's resolver accesses the
   Internet Domain Name System (DNS).

   The most common entries to resolv.conf are:

              The IP address of a name server the resolver should     
   nameserver query. The servers are queried in the order listed with 
              a maximum of three.                                     
   search     Search list for hostname lookup. This is normally       
              determined by the domain of the local hostname.         
   domain     The local domain name.                                  

   A typical resolv.conf:

 search example.com
 nameserver 147.11.1.11
 nameserver 147.11.100.30

     -a`: Only one of the search and domain options should be used.

   If you are using DHCP, dhclient(8) usually rewrites resolv.conf
   with information received from the DHCP server.

     --------------------------------------------------------------

    11.10.2.2. /etc/hosts

   /etc/hosts is a simple text database reminiscent of the old
   Internet. It works in conjunction with DNS and NIS providing name
   to IP address mappings. Local computers connected via a LAN can be
   placed in here for simplistic naming purposes instead of setting
   up a named(8) server. Additionally, /etc/hosts can be used to
   provide a local record of Internet names, reducing the need to
   query externally for commonly accessed names.

 # $FreeBSD$
 #
 # Host Database
 # This file should contain the addresses and aliases
 # for local hosts that share this file.
 # In the presence of the domain name service or NIS, this file may
 # not be consulted at all; see /etc/nsswitch.conf for the resolution order.
 #
 #
 ::1                     localhost localhost.my.domain myname.my.domain
 127.0.0.1               localhost localhost.my.domain myname.my.domain

 #
 # Imaginary network.
 #10.0.0.2               myname.my.domain myname
 #10.0.0.3               myfriend.my.domain myfriend
 #
 # According to RFC 1918, you can use the following IP networks for
 # private nets which will never be connected to the Internet:
 #
 #       10.0.0.0        -   10.255.255.255
 #       172.16.0.0      -   172.31.255.255
 #       192.168.0.0     -   192.168.255.255
 #
 # In case you want to be able to connect to the Internet, you need
 # real official assigned numbers.  PLEASE PLEASE PLEASE do not try
 # to invent your own network numbers but instead get one from your
 # network provider (if any) or from the Internet Registry (ftp to
 # rs.internic.net, directory `/templates').
 #

   /etc/hosts takes on the simple format of:

 [Internet address] [official hostname] [alias1] [alias2] ...

   For example:

 10.0.0.1 myRealHostname.example.com myRealHostname foobar1 foobar2

   Consult hosts(5) for more information.

     --------------------------------------------------------------

  11.10.3. Log File Configuration

     --------------------------------------------------------------

    11.10.3.1. syslog.conf

   syslog.conf is the configuration file for the syslogd(8) program.
   It indicates which types of syslog messages are logged to
   particular log files.

 # $FreeBSD$
 #
 #       Spaces ARE valid field separators in this file. However,
 #       other *nix-like systems still insist on using tabs as field
 #       separators. If you are sharing this file between systems, you
 #       may want to use only tabs as field separators here.
 #       Consult the syslog.conf(5) manual page.
 *.err;kern.debug;auth.notice;mail.crit          /dev/console
 *.notice;kern.debug;lpr.info;mail.crit;news.err /var/log/messages
 security.*                                      /var/log/security
 mail.info                                       /var/log/maillog
 lpr.info                                        /var/log/lpd-errs
 cron.*                                          /var/log/cron
 *.err                                           root
 *.notice;news.err                               root
 *.alert                                         root
 *.emerg                                         *
 # uncomment this to log all writes to /dev/console to /var/log/console.log
 #console.info                                   /var/log/console.log
 # uncomment this to enable logging of all log messages to /var/log/all.log
 #*.*                                            /var/log/all.log
 # uncomment this to enable logging to a remote log host named loghost
 #*.*                                            @loghost
 # uncomment these if you're running inn
 # news.crit                                     /var/log/news/news.crit
 # news.err                                      /var/log/news/news.err
 # news.notice                                   /var/log/news/news.notice
 !startslip
 *.*                                             /var/log/slip.log
 !ppp
 *.*                                             /var/log/ppp.log

   Consult the syslog.conf(5) manual page for more information.

     --------------------------------------------------------------

    11.10.3.2. newsyslog.conf

   newsyslog.conf is the configuration file for newsyslog(8), a
   program that is normally scheduled to run by cron(8). newsyslog(8)
   determines when log files require archiving or rearranging.
   logfile is moved to logfile.0, logfile.0 is moved to logfile.1,
   and so on. Alternatively, the log files may be archived in gzip(1)
   format causing them to be named: logfile.0.gz, logfile.1.gz, and
   so on.

   newsyslog.conf indicates which log files are to be managed, how
   many are to be kept, and when they are to be touched. Log files
   can be rearranged and/or archived when they have either reached a
   certain size, or at a certain periodic time/date.

 # configuration file for newsyslog
 # $FreeBSD$
 #
 # filename          [owner:group]    mode count size when [ZB] [/pid_file] [sig_num]
 /var/log/cron                           600  3     100  *     Z
 /var/log/amd.log                        644  7     100  *     Z
 /var/log/kerberos.log                   644  7     100  *     Z
 /var/log/lpd-errs                       644  7     100  *     Z
 /var/log/maillog                        644  7     *    @T00  Z
 /var/log/sendmail.st                    644  10    *    168   B
 /var/log/messages                       644  5     100  *     Z
 /var/log/all.log                        600  7     *    @T00  Z
 /var/log/slip.log                       600  3     100  *     Z
 /var/log/ppp.log                        600  3     100  *     Z
 /var/log/security                       600  10    100  *     Z
 /var/log/wtmp                           644  3     *    @01T05 B
 /var/log/daily.log                      640  7     *    @T00  Z
 /var/log/weekly.log                     640  5     1    $W6D0 Z
 /var/log/monthly.log                    640  12    *    $M1D0 Z
 /var/log/console.log                    640  5     100  *     Z

   Consult the newsyslog(8) manual page for more information.

     --------------------------------------------------------------

  11.10.4. sysctl.conf

   sysctl.conf looks much like rc.conf. Values are set in a
   variable=value form. The specified values are set after the system
   goes into multi-user mode. Not all variables are settable in this
   mode.

   A sample sysctl.conf turning off logging of fatal signal exits and
   letting Linux programs know they are really running under FreeBSD:

 kern.logsigexit=0       # Do not log fatal signal exits (e.g. sig 11)
 compat.linux.osname=FreeBSD
 compat.linux.osrelease=4.3-STABLE

     --------------------------------------------------------------

11.11. Tuning with sysctl

   sysctl(8) is an interface that allows you to make changes to a
   running FreeBSD system. This includes many advanced options of the
   TCP/IP stack and virtual memory system that can dramatically
   improve performance for an experienced system administrator. Over
   five hundred system variables can be read and set using sysctl(8).

   At its core, sysctl(8) serves two functions: to read and to modify
   system settings.

   To view all readable variables:

 % sysctl -a

   To read a particular variable, for example, kern.maxproc:

 % sysctl kern.maxproc
 kern.maxproc: 1044

   To set a particular variable, use the intuitive variable=value
   syntax:

 # sysctl kern.maxfiles=5000
 kern.maxfiles: 2088 -> 5000

   Settings of sysctl variables are usually either strings, numbers,
   or booleans (a boolean being 1 for yes or a 0 for no).

   If you want to set automatically some variables each time the
   machine boots, add them to the /etc/sysctl.conf file. For more
   information see the sysctl.conf(5) manual page and the uU 11.10.4
   ,`.

     --------------------------------------------------------------

  11.11.1. sysctl(8) Read-only

   Contributed by Tom Rhodes.

   In some cases it may be desirable to modify read-only sysctl(8)
   values. While this is sometimes unavoidable, it can only be done
   on (re)boot.

   For instance on some laptop models the cardbus(4) device will not
   probe memory ranges, and fail with errors which look similar to:

 cbb0: Could not map register memory
 device_probe_and_attach: cbb0 attach returned 12

   Cases like the one above usually require the modification of some
   default sysctl(8) settings which are set read only. To overcome
   these situations a user can put sysctl(8) !S:OIDs!" in their local
   /boot/loader.conf. Default settings are located in the
   /boot/defaults/loader.conf file.

   Fixing the problem mentioned above would require a user to set
   hw.pci.allow_unsupported_io_range=1 in the aforementioned file.
   Now cardbus(4) will work properly.

     --------------------------------------------------------------

11.12. Tuning Disks

  11.12.1. Sysctl Variables

    11.12.1.1. vfs.vmiodirenable

   The vfs.vmiodirenable sysctl variable may be set to either 0 (off)
   or 1 (on); it is 1 by default. This variable controls how
   directories are cached by the system. Most directories are small,
   using just a single fragment (typically 1 K) in the file system
   and less (typically 512 bytes) in the buffer cache. With this
   variable turned off (to 0), the buffer cache will only cache a
   fixed number of directories even if you have a huge amount of
   memory. When turned on (to 1), this sysctl allows the buffer cache
   to use the VM Page Cache to cache the directories, making all the
   memory available for caching directories. However, the minimum
   in-core memory used to cache a directory is the physical page size
   (typically 4 K) rather than 512  bytes. We recommend keeping this
   option on if you are running any services which manipulate large
   numbers of files. Such services can include web caches, large mail
   systems, and news systems. Keeping this option on will generally
   not reduce performance even with the wasted memory but you should
   experiment to find out.

     --------------------------------------------------------------

    11.12.1.2. vfs.write_behind

   The vfs.write_behind sysctl variable defaults to 1 (on). This
   tells the file system to issue media writes as full clusters are
   collected, which typically occurs when writing large sequential
   files. The idea is to avoid saturating the buffer cache with dirty
   buffers when it would not benefit I/O performance. However, this
   may stall processes and under certain circumstances you may wish
   to turn it off.

     --------------------------------------------------------------

    11.12.1.3. vfs.hirunningspace

   The vfs.hirunningspace sysctl variable determines how much
   outstanding write I/O may be queued to disk controllers
   system-wide at any given instance. The default is usually
   sufficient but on machines with lots of disks you may want to bump
   it up to four or five megabytes. Note that setting too high a
   value (exceeding the buffer cache's write threshold) can lead to
   extremely bad clustering performance. Do not set this value
   arbitrarily high! Higher write values may add latency to reads
   occurring at the same time.

   There are various other buffer-cache and VM page cache related
   sysctls. We do not recommend modifying these values, the VM system
   does an extremely good job of automatically tuning itself.

     --------------------------------------------------------------

    11.12.1.4. vm.swap_idle_enabled

   The vm.swap_idle_enabled sysctl variable is useful in large
   multi-user systems where you have lots of users entering and
   leaving the system and lots of idle processes. Such systems tend
   to generate a great deal of continuous pressure on free memory
   reserves. Turning this feature on and tweaking the swapout
   hysteresis (in idle seconds) via vm.swap_idle_threshold1 and
   vm.swap_idle_threshold2 allows you to depress the priority of
   memory pages associated with idle processes more quickly then the
   normal pageout algorithm. This gives a helping hand to the pageout
   daemon. Do not turn this option on unless you need it, because the
   tradeoff you are making is essentially pre-page memory sooner
   rather than later; thus eating more swap and disk bandwidth. In a
   small system this option will have a determinable effect but in a
   large system that is already doing moderate paging this option
   allows the VM system to stage whole processes into and out of
   memory easily.

     --------------------------------------------------------------

    11.12.1.5. hw.ata.wc

   FreeBSD 4.3 flirted with turning off IDE write caching. This
   reduced write bandwidth to IDE disks but was considered necessary
   due to serious data consistency issues introduced by hard drive
   vendors. The problem is that IDE drives lie about when a write
   completes. With IDE write caching turned on, IDE hard drives not
   only write data to disk out of order, but will sometimes delay
   writing some blocks indefinitely when under heavy disk loads. A
   crash or power failure may cause serious file system corruption.
   FreeBSD's default was changed to be safe. Unfortunately, the
   result was such a huge performance loss that we changed write
   caching back to on by default after the release. You should check
   the default on your system by observing the hw.ata.wc sysctl
   variable. If IDE write caching is turned off, you can turn it back
   on by setting the kernel variable back to 1. This must be done
   from the boot loader at boot time. Attempting to do it after the
   kernel boots will have no effect.

   For more information, please see ata(4).

     --------------------------------------------------------------

    11.12.1.6. SCSI_DELAY (kern.cam.scsi_delay)

   The SCSI_DELAY kernel config may be used to reduce system boot
   times. The defaults are fairly high and can be responsible for 15
   seconds of delay in the boot process. Reducing it to 5 seconds
   usually works (especially with modern drives). Newer versions of
   FreeBSD (5.0 and higher) should use the kern.cam.scsi_delay boot
   time tunable. The tunable, and kernel config option accept values
   in terms of milliseconds and not seconds.

     --------------------------------------------------------------

  11.12.2. Soft Updates

   The tunefs(8) program can be used to fine-tune a file system. This
   program has many different options, but for now we are only
   concerned with toggling Soft Updates on and off, which is done by:

 # tunefs -n enable /filesystem
 # tunefs -n disable /filesystem

   A filesystem cannot be modified with tunefs(8) while it is
   mounted. A good time to enable Soft Updates is before any
   partitions have been mounted, in single-user mode.

   Soft Updates drastically improves meta-data performance, mainly
   file creation and deletion, through the use of a memory cache. We
   recommend to use Soft Updates on all of your file systems. There
   are two downsides to Soft Updates that you should be aware of:
   First, Soft Updates guarantees filesystem consistency in the case
   of a crash but could very easily be several seconds (even a
   minute!) behind updating the physical disk. If your system crashes
   you may lose more work than otherwise. Secondly, Soft Updates
   delays the freeing of filesystem blocks. If you have a filesystem
   (such as the root filesystem) which is almost full, performing a
   major update, such as make installworld, can cause the filesystem
   to run out of space and the update to fail.

     --------------------------------------------------------------

    11.12.2.1. More Details about Soft Updates

   There are two traditional approaches to writing a file systems
   meta-data back to disk. (Meta-data updates are updates to
   non-content data like inodes or directories.)

   Historically, the default behavior was to write out meta-data
   updates synchronously. If a directory had been changed, the system
   waited until the change was actually written to disk. The file
   data buffers (file contents) were passed through the buffer cache
   and backed up to disk later on asynchronously. The advantage of
   this implementation is that it operates safely. If there is a
   failure during an update, the meta-data are always in a consistent
   state. A file is either created completely or not at all. If the
   data blocks of a file did not find their way out of the buffer
   cache onto the disk by the time of the crash, fsck(8) is able to
   recognize this and repair the filesystem by setting the file
   length to 0. Additionally, the implementation is clear and simple.
   The disadvantage is that meta-data changes are slow. An rm -r, for
   instance, touches all the files in a directory sequentially, but
   each directory change (deletion of a file) will be written
   synchronously to the disk. This includes updates to the directory
   itself, to the inode table, and possibly to indirect blocks
   allocated by the file. Similar considerations apply for unrolling
   large hierarchies (tar -x).

   The second case is asynchronous meta-data updates. This is the
   default for Linux/ext2fs and mount -o async for *BSD ufs. All
   meta-data updates are simply being passed through the buffer cache
   too, that is, they will be intermixed with the updates of the file
   content data. The advantage of this implementation is there is no
   need to wait until each meta-data update has been written to disk,
   so all operations which cause huge amounts of meta-data updates
   work much faster than in the synchronous case. Also, the
   implementation is still clear and simple, so there is a low risk
   for bugs creeping into the code. The disadvantage is that there is
   no guarantee at all for a consistent state of the filesystem. If
   there is a failure during an operation that updated large amounts
   of meta-data (like a power failure, or someone pressing the reset
   button), the filesystem will be left in an unpredictable state.
   There is no opportunity to examine the state of the filesystem
   when the system comes up again; the data blocks of a file could
   already have been written to the disk while the updates of the
   inode table or the associated directory were not. It is actually
   impossible to implement a fsck which is able to clean up the
   resulting chaos (because the necessary information is not
   available on the disk). If the filesystem has been damaged beyond
   repair, the only choice is to use newfs(8) on it and restore it
   from backup.

   The usual solution for this problem was to implement dirty region
   logging, which is also referred to as journaling, although that
   term is not used consistently and is occasionally applied to other
   forms of transaction logging as well. Meta-data updates are still
   written synchronously, but only into a small region of the disk.
   Later on they will be moved to their proper location. Because the
   logging area is a small, contiguous region on the disk, there are
   no long distances for the disk heads to move, even during heavy
   operations, so these operations are quicker than synchronous
   updates. Additionally the complexity of the implementation is
   fairly limited, so the risk of bugs being present is low. A
   disadvantage is that all meta-data are written twice (once into
   the logging region and once to the proper location) so for normal
   work, a performance !S:pessimization!" might result. On the other
   hand, in case of a crash, all pending meta-data operations can be
   quickly either rolled-back or completed from the logging area
   after the system comes up again, resulting in a fast filesystem
   startup.

   Kirk McKusick, the developer of Berkeley FFS, solved this problem
   with Soft Updates: all pending meta-data updates are kept in
   memory and written out to disk in a sorted sequence (!S:ordered
   meta-data updates!"). This has the effect that, in case of heavy
   meta-data operations, later updates to an item !S:catch!" the
   earlier ones if the earlier ones are still in memory and have not
   already been written to disk. So all operations on, say, a
   directory are generally performed in memory before the update is
   written to disk (the data blocks are sorted according to their
   position so that they will not be on the disk ahead of their
   meta-data). If the system crashes, this causes an implicit !S:log
   rewind!": all operations which did not find their way to the disk
   appear as if they had never happened. A consistent filesystem
   state is maintained that appears to be the one of 30 to 60 seconds
   earlier. The algorithm used guarantees that all resources in use
   are marked as such in their appropriate bitmaps: blocks and
   inodes. After a crash, the only resource allocation error that
   occurs is that resources are marked as !S:used!" which are
   actually !S:free!". fsck(8) recognizes this situation, and frees
   the resources that are no longer used. It is safe to ignore the
   dirty state of the filesystem after a crash by forcibly mounting
   it with mount -f. In order to free resources that may be unused,
   fsck(8) needs to be run at a later time. This is the idea behind
   the background fsck: at system startup time, only a snapshot of
   the filesystem is recorded. The fsck can be run later on. All file
   systems can then be mounted !S:dirty!", so the system startup
   proceeds in multiuser mode. Then, background fscks will be
   scheduled for all file systems where this is required, to free
   resources that may be unused. (File systems that do not use Soft
   Updates still need the usual foreground fsck though.)

   The advantage is that meta-data operations are nearly as fast as
   asynchronous updates (i.e. faster than with logging, which has to
   write the meta-data twice). The disadvantages are the complexity
   of the code (implying a higher risk for bugs in an area that is
   highly sensitive regarding loss of user data), and a higher memory
   consumption. Additionally there are some idiosyncrasies one has to
   get used to. After a crash, the state of the filesystem appears to
   be somewhat !S:older!". In situations where the standard
   synchronous approach would have caused some zero-length files to
   remain after the fsck, these files do not exist at all with a Soft
   Updates filesystem because neither the meta-data nor the file
   contents have ever been written to disk. Disk space is not
   released until the updates have been written to disk, which may
   take place some time after running rm. This may cause problems
   when installing large amounts of data on a filesystem that does
   not have enough free space to hold all the files twice.

     --------------------------------------------------------------

11.13. Tuning Kernel Limits

     --------------------------------------------------------------

  11.13.1. File/Process Limits

    11.13.1.1. kern.maxfiles

   kern.maxfiles can be raised or lowered based upon your system
   requirements. This variable indicates the maximum number of file
   descriptors on your system. When the file descriptor table is
   full, !S:file: table is full!" will show up repeatedly in the
   system message buffer, which can be viewed with the dmesg command.

   Each open file, socket, or fifo uses one file descriptor. A
   large-scale production server may easily require many thousands of
   file descriptors, depending on the kind and number of services
   running concurrently.

   In older FreeBSD releases, kern.maxfile's default value is derived
   from the maxusers option in your dictated by the maxusers option
   in your kernel configuration file. kern.maxfiles grows
   proportionally to the value of maxusers. When compiling a custom
   kernel, it is a good idea to set this kernel configuration option
   according to the uses of your system. From this number, the kernel
   is given most of its pre-defined limits. Even though a production
   machine may not actually have 256 users connected at once, the
   resources needed may be similar to a high-scale web server.

   As of FreeBSD 4.5, kern.maxusers is automatically sized at boot
   based on the amount of memory available in the system, and may be
   determined at run-time by inspecting the value of the read-only
   kern.maxusers sysctl. Some sites will require larger or smaller
   values of kern.maxusers and may set it as a loader tunable; values
   of 64, 128, and 256 are not uncommon. We do not recommend going
   above 256 unless you need a huge number of file descriptors; many
   of the tunable values set to their defaults by kern.maxusers may
   be individually overridden at boot-time or run-time in
   /boot/loader.conf (see the loader.conf(5) man page or the
   /boot/defaults/loader.conf file for some hints) or as described
   elsewhere in this document. Systems older than FreeBSD 4.4 must
   set this value via the kernel config(8) option maxusers instead.

   The system will auto-tune maxusers for you if you explicitly set
   it to 0[8]. When setting this option, you will want to set
   maxusers to at least 4, especially if you are using the X Window
   System or compiling software. The reason is that the most
   important table set by maxusers is the maximum number of
   processes, which is set to 20 + 16 * maxusers, so if you set
   maxusers to 1, then you can only have 36 simultaneous processes,
   including the 18 or so that the system starts up at boot time and
   the 15 or so you will probably create when you start the X Window
   System. Even a simple task like reading a manual page will start
   up nine processes to filter, decompress, and view it. Setting
   maxusers to 64 will allow you to have up to 1044 simultaneous
   processes, which should be enough for nearly all uses. If,
   however, you see the dreaded proc table full error when trying to
   start another program, or are running a server with a large number
   of simultaneous users (like ftp.FreeBSD.org), you can always
   increase the number and rebuild.

     -a`: maxusers does not limit the number of users which can log
     into your machine. It simply sets various table sizes to
     reasonable values considering the maximum number of users you
     will likely have on your system and how many processes each of
     them will be running. One keyword which does limit the number of
     simultaneous remote logins and X terminal windows is
     pseudo-device pty 16. With FreeBSD 5.X, you do not have to worry
     about this number since the pty(4) driver is !S:auto-cloning!";
     you simply use the line device pty in your configuration file.

     --------------------------------------------------------------

    11.13.1.2. kern.ipc.somaxconn

   The kern.ipc.somaxconn sysctl variable limits the size of the
   listen queue for accepting new TCP connections. The default value
   of 128 is typically too low for robust handling of new connections
   in a heavily loaded web server environment. For such environments,
   it is recommended to increase this value to 1024 or higher. The
   service daemon may itself limit the listen queue size (e.g.
   sendmail(8), or Apache) but will often have a directive in its
   configuration file to adjust the queue size. Large listen queues
   also do a better job of avoiding Denial of Service (DoS) attacks.

     --------------------------------------------------------------

  11.13.2. Network Limits

   The NMBCLUSTERS kernel configuration option dictates the amount of
   network Mbufs available to the system. A heavily-trafficked server
   with a low number of Mbufs will hinder FreeBSD's ability. Each
   cluster represents approximately 2 K of memory, so a value of 1024
   represents 2 megabytes of kernel memory reserved for network
   buffers. A simple calculation can be done to figure out how many
   are needed. If you have a web server which maxes out at 1000
   simultaneous connections, and each connection eats a 16 K receive
   and 16 K send buffer, you need approximately 32 MB worth of
   network buffers to cover the web server. A good rule of thumb is
   to multiply by 2, so 2x32 MB / 2 KB = 64 MB / 2 kB = 32768. We
   recommend values between 4096 and 32768 for machines with greater
   amounts of memory. Under no circumstances should you specify an
   arbitrarily high value for this parameter as it could lead to a
   boot time crash. The -m option to netstat(1) may be used to
   observe network cluster use.

   kern.ipc.nmbclusters loader tunable should be used to tune this at
   boot time. Only older versions of FreeBSD will require you to use
   the NMBCLUSTERS kernel config(8) option.

   For busy servers that make extensive use of the sendfile(2) system
   call, it may be necessary to increase the number of sendfile(2)
   buffers via the NSFBUFS kernel configuration option or by setting
   its value in /boot/loader.conf (see loader(8) for details). A
   common indicator that this parameter needs to be adjusted is when
   processes are seen in the sfbufa state. The sysctl variable
   kern.ipc.nsfbufs is a read-only glimpse at the kernel configured
   variable. This parameter nominally scales with kern.maxusers,
   however it may be necessary to tune accordingly.

     <<n: Even though a socket has been marked as non-blocking,
     calling sendfile(2) on the non-blocking socket may result in the
     sendfile(2) call blocking until enough struct sf_buf's are made
     available.

     --------------------------------------------------------------

    11.13.2.1. net.inet.ip.portrange.*

   The net.inet.ip.portrange.* sysctl variables control the port
   number ranges automatically bound to TCP and UDP sockets. There
   are three ranges: a low range, a default range, and a high range.
   Most network programs use the default range which is controlled by
   the net.inet.ip.portrange.first and net.inet.ip.portrange.last,
   which default to 1024 and 5000, respectively. Bound port ranges
   are used for outgoing connections, and it is possible to run the
   system out of ports under certain circumstances. This most
   commonly occurs when you are running a heavily loaded web proxy.
   The port range is not an issue when running servers which handle
   mainly incoming connections, such as a normal web server, or has a
   limited number of outgoing connections, such as a mail relay. For
   situations where you may run yourself out of ports, it is
   recommended to increase net.inet.ip.portrange.last modestly. A
   value of 10000, 20000 or 30000 may be reasonable. You should also
   consider firewall effects when changing the port range. Some
   firewalls may block large ranges of ports (usually low-numbered
   ports) and expect systems to use higher ranges of ports for
   outgoing connections !X!X for this reason it is not recommended
   that net.inet.ip.portrange.first be lowered.

     --------------------------------------------------------------

    11.13.2.2. TCP Bandwidth Delay Product

   The TCP Bandwidth Delay Product Limiting is similar to TCP/Vegas
   in NetBSD. It can be enabled by setting
   net.inet.tcp.inflight.enable sysctl variable to 1. The system will
   attempt to calculate the bandwidth delay product for each
   connection and limit the amount of data queued to the network to
   just the amount required to maintain optimum throughput.

   This feature is useful if you are serving data over modems,
   Gigabit Ethernet, or even high speed WAN links (or any other link
   with a high bandwidth delay product), especially if you are also
   using window scaling or have configured a large send window. If
   you enable this option, you should also be sure to set
   net.inet.tcp.inflight.debug to 0 (disable debugging), and for
   production use setting net.inet.tcp.inflight.min to at least 6144
   may be beneficial. However, note that setting high minimums may
   effectively disable bandwidth limiting depending on the link. The
   limiting feature reduces the amount of data built up in
   intermediate route and switch packet queues as well as reduces the
   amount of data built up in the local host's interface queue. With
   fewer packets queued up, interactive connections, especially over
   slow modems, will also be able to operate with lower Round Trip
   Times. However, note that this feature only effects data
   transmission (uploading / server side). It has no effect on data
   reception (downloading).

   Adjusting net.inet.tcp.inflight.stab is not recommended. This
   parameter defaults to 20, representing 2 maximal packets added to
   the bandwidth delay product window calculation. The additional
   window is required to stabilize the algorithm and improve
   responsiveness to changing conditions, but it can also result in
   higher ping times over slow links (though still much lower than
   you would get without the inflight algorithm). In such cases, you
   may wish to try reducing this parameter to 15, 10, or 5; and may
   also have to reduce net.inet.tcp.inflight.min (for example, to
   3500) to get the desired effect. Reducing these parameters should
   be done as a last resort only.

     --------------------------------------------------------------

  11.13.3. Virtual Memory

    11.13.3.1. kern.maxvnodes

   A vnode is the internal representation of a file or directory. So
   increasing the number of vnodes available to the operating system
   cuts down on disk I/O. Normally this is handled by the operating
   system and does not need to be changed. In some cases where disk
   I/O is a bottleneck and the system is running out of vnodes, this
   setting will need to be increased. The amount of inactive and free
   RAM will need to be taken into account.

   To see the current number of vnodes in use:

 # sysctl vfs.numvnodes
 vfs.numvnodes: 91349

   To see the maximum vnodes:

 # sysctl kern.maxvnodes
 kern.maxvnodes: 100000

   If the current vnode usage is near the maximum, increasing
   kern.maxvnodes by a value of 1,000 is probably a good idea. Keep
   an eye on the number of vfs.numvnodes. If it climbs up to the
   maximum again, kern.maxvnodes will need to be increased further. A
   shift in your memory usage as reported by top(1) should be
   visible. More memory should be active.

     --------------------------------------------------------------

11.14. Adding Swap Space

   No matter how well you plan, sometimes a system does not run as
   you expect. If you find you need more swap space, it is simple
   enough to add. You have three ways to increase swap space: adding
   a new hard drive, enabling swap over NFS, and creating a swap file
   on an existing partition.

   For information on how to encrypt swap space, what options for
   this task exist and why it should be done, please refer to uU
   18.17 ,` of the Handbook.

     --------------------------------------------------------------

  11.14.1. Swap on a New Hard Drive

   The best way to add swap, of course, is to use this as an excuse
   to add another hard drive. You can always use another hard drive,
   after all. If you can do this, go reread the discussion of swap
   space in uU 11.2 ,` of the Handbook for some suggestions on how to
   best arrange your swap.

     --------------------------------------------------------------

  11.14.2. Swapping over NFS

   Swapping over NFS is only recommended if you do not have a local
   hard disk to swap to; NFS swapping will be limited by the
   available network bandwidth and puts an additional burden on the
   NFS server.

     --------------------------------------------------------------

  11.14.3. Swapfiles

   You can create a file of a specified size to use as a swap file.
   In our example here we will use a 64MB file called /usr/swap0. You
   can use any name you want, of course.

   1/2d"O 11-1. Creating a Swapfile on FreeBSD

    1. Be certain that your kernel configuration includes the memory
       disk driver (md(4)). It is default in GENERIC kernel.

 device   md   # Memory "disks"

    2. Create a swapfile (/usr/swap0):

 # dd if=/dev/zero of=/usr/swap0 bs=1024k count=64

    3. Set proper permissions on (/usr/swap0):

 # chmod 0600 /usr/swap0

    4. Enable the swap file in /etc/rc.conf:

 swapfile="/usr/swap0"   # Set to name of swapfile if aux swapfile desired.

    5. Reboot the machine or to enable the swap file immediately,
       type:

 # mdconfig -a -t vnode -f /usr/swap0 -u 0 && swapon /dev/md0

     --------------------------------------------------------------

11.15. Power and Resource Management

   Written by Hiten Pandya YENB Tom Rhodes.

   It is very important to utilize hardware resources in an efficient
   manner. Before ACPI was introduced, it was very difficult and
   inflexible for operating systems to manage the power usage and
   thermal properties of a system. The hardware was controlled by
   some sort of BIOS embedded interface, such as Plug and Play BIOS
   (PNPBIOS), or Advanced Power Management (APM) and so on. Power and
   Resource Management is one of the key components of a modern
   operating system. For example, you may want an operating system to
   monitor system limits (and possibly alert you) in case your system
   temperature increased unexpectedly.

   In this section of the FreeBSD Handbook, we will provide
   comprehensive information about ACPI. References will be provided
   for further reading at the end.

     --------------------------------------------------------------

  11.15.1. What Is ACPI?

   Advanced Configuration and Power Interface (ACPI) is a standard
   written by an alliance of vendors to provide a standard interface
   for hardware resources and power management (hence the name). It
   is a key element in Operating System-directed configuration and
   Power Management, i.e.: it provides more control and flexibility
   to the operating system (OS). Modern systems !S:stretched!" the
   limits of the current Plug and Play interfaces prior to the
   introduction of ACPI. ACPI is the direct successor to APM
   (Advanced Power Management).

     --------------------------------------------------------------

  11.15.2. Shortcomings of Advanced Power Management (APM)

   The Advanced Power Management (APM) facility controls the power
   usage of a system based on its activity. The APM BIOS is supplied
   by the (system) vendor and it is specific to the hardware
   platform. An APM driver in the OS mediates access to the APM
   Software Interface, which allows management of power levels.

   There are four major problems in APM. Firstly, power management is
   done by the (vendor-specific) BIOS, and the OS does not have any
   knowledge of it. One example of this, is when the user sets
   idle-time values for a hard drive in the APM BIOS, that when
   exceeded, it (BIOS) would spin down the hard drive, without the
   consent of the OS. Secondly, the APM logic is embedded in the
   BIOS, and it operates outside the scope of the OS. This means
   users can only fix problems in their APM BIOS by flashing a new
   one into the ROM; which is a very dangerous procedure with the
   potential to leave the system in an unrecoverable state if it
   fails. Thirdly, APM is a vendor-specific technology, which means
   that there is a lot of parity (duplication of efforts) and bugs
   found in one vendor's BIOS, may not be solved in others. Last but
   not the least, the APM BIOS did not have enough room to implement
   a sophisticated power policy, or one that can adapt very well to
   the purpose of the machine.

   Plug and Play BIOS (PNPBIOS) was unreliable in many situations.
   PNPBIOS is 16-bit technology, so the OS has to use 16-bit
   emulation in order to !S:interface!" with PNPBIOS methods.

   The FreeBSD APM driver is documented in the apm(4) manual page.

     --------------------------------------------------------------

  11.15.3. Configuring ACPI

   The acpi.ko driver is loaded by default at start up by the
   loader(8) and should not be compiled into the kernel. The
   reasoning behind this is that modules are easier to work with, say
   if switching to another acpi.ko without doing a kernel rebuild.
   This has the advantage of making testing easier. Another reason is
   that starting ACPI after a system has been brought up is not too
   useful, and in some cases can be fatal. In doubt, just disable
   ACPI all together. This driver should not and can not be unloaded
   because the system bus uses it for various hardware interactions.
   ACPI can be disabled with the acpiconf(8) utility. In fact most of
   the interaction with ACPI can be done via acpiconf(8). Basically
   this means, if anything about ACPI is in the dmesg(8) output, then
   most likely it is already running.

     -a`: ACPI and APM cannot coexist and should be used separately.
     The last one to load will terminate if the driver notices the
     other running.

   In the simplest form, ACPI can be used to put the system into a
   sleep mode with acpiconf(8), the -s flag, and a 1-5 option. Most
   users will only need 1. Option 5 will do a soft-off which is the
   same action as:

 # halt -p

   The other options are available. Check out the acpiconf(8) manual
   page for more information.

     --------------------------------------------------------------

11.16. Using and Debugging FreeBSD ACPI

   Written by Nate Lawson. With contributions from Peter Schultz YENB
   Tom Rhodes.

   ACPI is a fundamentally new way of discovering devices, managing
   power usage, and providing standardized access to various hardware
   previously managed by the BIOS. Progress is being made toward ACPI
   working on all systems, but bugs in some motherboards' ACPI
   Machine Language (AML) bytecode, incompleteness in FreeBSD's
   kernel subsystems, and bugs in the Intel ACPI-CA interpreter
   continue to appear.

   This document is intended to help you assist the FreeBSD ACPI
   maintainers in identifying the root cause of problems you observe
   and debugging and developing a solution. Thanks for reading this
   and we hope we can solve your system's problems.

     --------------------------------------------------------------

  11.16.1. Submitting Debugging Information

     -a`: Before submitting a problem, be sure you are running the
     latest BIOS version and, if available, embedded controller
     firmware version.

   For those of you that want to submit a problem right away, please
   send the following information to   freebsd-acpi@FreeBSD.org:

     * Description of the buggy behavior, including system type and
       model and anything that causes the bug to appear. Also, please
       note as accurately as possible when the bug began occurring if
       it is new for you.

     * The dmesg(8) output after boot -v, including any error
       messages generated by you exercising the bug.

     * The dmesg(8) output from boot -v with ACPI disabled, if
       disabling it helps fix the problem.

     * Output from sysctl hw.acpi. This is also a good way of
       figuring out what features your system offers.

     * URL where your ACPI Source Language (ASL) can be found. Do not
       send the ASL directly to the list as it can be very large.
       Generate a copy of your ASL by running this command:

 # acpidump -t -d > name-system.asl

       (Substitute your login name for name and manufacturer/model
       for system. Example: njl-FooCo6000.asl)

   Most of the developers watch the FreeBSD-CURRENT P:l>> 1/4 1/2 *
   3/4A but please submit problems to freebsd-acpi to be sure it is
   seen. Please be patient, all of us have full-time jobs elsewhere.
   If your bug is not immediately apparent, we will probably ask you
   to submit a PR via send-pr(1). When entering a PR, please include
   the same information as requested above. This will help us track
   the problem and resolve it. Do not send a PR without emailing
   freebsd-acpi first as we use PRs as reminders of existing
   problems, not a reporting mechanism. It is likely that your
   problem has been reported by someone before.

     --------------------------------------------------------------

  11.16.2. Background

   ACPI is present in all modern computers that conform to the ia32
   (x86), ia64 (Itanium), and amd64 (AMD) architectures. The full
   standard has many features including CPU performance management,
   power planes control, thermal zones, various battery systems,
   embedded controllers, and bus enumeration. Most systems implement
   less than the full standard. For instance, a desktop system
   usually only implements the bus enumeration parts while a laptop
   might have cooling and battery management support as well. Laptops
   also have suspend and resume, with their own associated
   complexity.

   An ACPI-compliant system has various components. The BIOS and
   chipset vendors provide various fixed tables (e.g., FADT) in
   memory that specify things like the APIC map (used for SMP),
   config registers, and simple configuration values. Additionally, a
   table of bytecode (the Differentiated System Description Table
   DSDT) is provided that specifies a tree-like name space of devices
   and methods.

   The ACPI driver must parse the fixed tables, implement an
   interpreter for the bytecode, and modify device drivers and the
   kernel to accept information from the ACPI subsystem. For FreeBSD,
   Intel has provided an interpreter (ACPI-CA) that is shared with
   Linux and NetBSD. The path to the ACPI-CA source code is
   src/sys/contrib/dev/acpica. The glue code that allows ACPI-CA to
   work on FreeBSD is in src/sys/dev/acpica/Osd. Finally, drivers
   that implement various ACPI devices are found in
   src/sys/dev/acpica.

     --------------------------------------------------------------

  11.16.3. Common Problems

   For ACPI to work correctly, all the parts have to work correctly.
   Here are some common problems, in order of frequency of
   appearance, and some possible workarounds or fixes.

     --------------------------------------------------------------

    11.16.3.1. Mouse Issues

   In some cases, resuming from a suspend operation will cause the
   mouse to fail. A known work around is to add
   hint.psm.0.flags="0x3000" to the /boot/loader.conf file. If this
   does not work then please consider sending a bug report as
   described above.

     --------------------------------------------------------------

    11.16.3.2. Suspend/Resume

   ACPI has three suspend to RAM (STR) states, S1-S3, and one suspend
   to disk state (STD), called S4. S5 is !S:soft off!" and is the
   normal state your system is in when plugged in but not powered up.
   S4 can actually be implemented two separate ways. S4BIOS is a
   BIOS-assisted suspend to disk. S4OS is implemented entirely by the
   operating system.

   Start by checking sysctl hw.acpi for the suspend-related items.
   Here are the results for a Thinkpad:

 hw.acpi.supported_sleep_state: S3 S4 S5
 hw.acpi.s4bios: 0

   This means that we can use acpiconf -s to test S3, S4OS, and S5.
   If s4bios was one (1), we would have S4BIOS support instead of S4
   OS.

   When testing suspend/resume, start with S1, if supported. This
   state is most likely to work since it does not require much driver
   support. No one has implemented S2 but if you have it, it is
   similar to S1. The next thing to try is S3. This is the deepest
   STR state and requires a lot of driver support to properly
   reinitialize your hardware. If you have problems resuming, feel
   free to email the freebsd-acpi list but do not expect the problem
   to be resolved since there are a lot of drivers/hardware that need
   more testing and work.

   To help isolate the problem, remove as many drivers from your
   kernel as possible. If it works, you can narrow down which driver
   is the problem by loading drivers until it fails again. Typically
   binary drivers like nvidia.ko, X11 display drivers, and USB will
   have the most problems while Ethernet interfaces usually work
   fine. If you can properly load/unload the drivers, you can
   automate this by putting the appropriate commands in
   /etc/rc.suspend and /etc/rc.resume. There is a commented-out
   example for unloading and loading a driver. Try setting
   hw.acpi.reset_video to zero (0) if your display is messed up after
   resume. Try setting longer or shorter values for
   hw.acpi.sleep_delay to see if that helps.

   Another thing to try is load a recent Linux distribution with ACPI
   support and test their suspend/resume support on the same
   hardware. If it works on Linux, it is likely a FreeBSD driver
   problem and narrowing down which driver causes the problems will
   help us fix the problem. Note that the ACPI maintainers do not
   usually maintain other drivers (e.g sound, ATA, etc.) so any work
   done on tracking down a driver problem should probably eventually
   be posted to the freebsd-current list and mailed to the driver
   maintainer. If you are feeling adventurous, go ahead and start
   putting some debugging printf(3)s in a problematic driver to track
   down where in its resume function it hangs.

   Finally, try disabling ACPI and enabling APM instead. If
   suspend/resume works with APM, you may be better off sticking with
   APM, especially on older hardware (pre-2000). It took vendors a
   while to get ACPI support correct and older hardware is more
   likely to have BIOS problems with ACPI.

     --------------------------------------------------------------

    11.16.3.3. System Hangs (temporary or permanent)

   Most system hangs are a result of lost interrupts or an interrupt
   storm. Chipsets have a lot of problems based on how the BIOS
   configures interrupts before boot, correctness of the APIC (MADT)
   table, and routing of the System Control Interrupt (SCI).

   Interrupt storms can be distinguished from lost interrupts by
   checking the output of vmstat -i and looking at the line that has
   acpi0. If the counter is increasing at more than a couple per
   second, you have an interrupt storm. If the system appears hung,
   try breaking to DDB (CTRL+ALT+ESC on console) and type show
   interrupts.

   Your best hope when dealing with interrupt problems is to try
   disabling APIC support with hint.apic.0.disabled="1" in
   loader.conf.

     --------------------------------------------------------------

    11.16.3.4. Panics

   Panics are relatively rare for ACPI and are the top priority to be
   fixed. The first step is to isolate the steps to reproduce the
   panic (if possible) and get a backtrace. Follow the advice for
   enabling options DDB and setting up a serial console (see uU
   24.6.5.3 ,`) or setting up a dump(8) partition. You can get a
   backtrace in DDB with tr. If you have to handwrite the backtrace,
   be sure to at least get the lowest five (5) and top five (5) lines
   in the trace.

   Then, try to isolate the problem by booting with ACPI disabled. If
   that works, you can isolate the ACPI subsystem by using various
   values of debug.acpi.disable. See the acpi(4) manual page for some
   examples.

     --------------------------------------------------------------

    11.16.3.5. System Powers Up After Suspend or Shutdown

   First, try setting hw.acpi.disable_on_poweroff="0" in
   loader.conf(5). This keeps ACPI from disabling various events
   during the shutdown process. Some systems need this value set to 1
   (the default) for the same reason. This usually fixes the problem
   of a system powering up spontaneously after a suspend or poweroff.

     --------------------------------------------------------------

    11.16.3.6. Other Problems

   If you have other problems with ACPI (working with a docking
   station, devices not detected, etc.), please email a description
   to the mailing list as well; however, some of these issues may be
   related to unfinished parts of the ACPI subsystem so they might
   take a while to be implemented. Please be patient and prepared to
   test patches we may send you.

     --------------------------------------------------------------

  11.16.4. ASL, acpidump, and IASL

   The most common problem is the BIOS vendors providing incorrect
   (or outright buggy!) bytecode. This is usually manifested by
   kernel console messages like this:

 ACPI-1287: *** Error: Method execution failed [\\_SB_.PCI0.LPC0.FIGD._STA] \\
 (Node 0xc3f6d160), AE_NOT_FOUND

   Often, you can resolve these problems by updating your BIOS to the
   latest revision. Most console messages are harmless but if you
   have other problems like battery status not working, they are a
   good place to start looking for problems in the AML. The bytecode,
   known as AML, is compiled from a source language called ASL. The
   AML is found in the table known as the DSDT. To get a copy of your
   ASL, use acpidump(8). You should use both the -t (show contents of
   the fixed tables) and -d (disassemble AML to ASL) options. See the
   Submitting Debugging Information section for an example syntax.

   The simplest first check you can do is to recompile your ASL to
   check for errors. Warnings can usually be ignored but errors are
   bugs that will usually prevent ACPI from working correctly. To
   recompile your ASL, issue the following command:

 # iasl your.asl

     --------------------------------------------------------------

  11.16.5. Fixing Your ASL

   In the long run, our goal is for almost everyone to have ACPI work
   without any user intervention. At this point, however, we are
   still developing workarounds for common mistakes made by the BIOS
   vendors. The Microsoft interpreter (acpi.sys and acpiec.sys) does
   not strictly check for adherence to the standard, and thus many
   BIOS vendors who only test ACPI under Windows never fix their ASL.
   We hope to continue to identify and document exactly what
   non-standard behavior is allowed by Microsoft's interpreter and
   replicate it so FreeBSD can work without forcing users to fix the
   ASL. As a workaround and to help us identify behavior, you can fix
   the ASL manually. If this works for you, please send a diff(1) of
   the old and new ASL so we can possibly work around the buggy
   behavior in ACPI-CA and thus make your fix unnecessary.

   Here is a list of common error messages, their cause, and how to
   fix them:

     --------------------------------------------------------------

    11.16.5.1. _OS dependencies

   Some AML assumes the world consists of various Windows versions.
   You can tell FreeBSD to claim it is any OS to see if this fixes
   problems you may have. An easy way to override this is to set
   hw.acpi.osname="Windows 2001" in /boot/loader.conf or other
   similar strings you find in the ASL.

     --------------------------------------------------------------

    11.16.5.2. Missing Return statements

   Some methods do not explicitly return a value as the standard
   requires. While ACPI-CA does not handle this, FreeBSD has a
   workaround that allows it to return the value implicitly. You can
   also add explicit Return statements where required if you know
   what value should be returned. To force iasl to compile the ASL,
   use the -f flag.

     --------------------------------------------------------------

    11.16.5.3. Overriding the Default AML

   After you customize your.asl, you will want to compile it, run:

 # iasl your.asl

   You can add the -f flag to force creation of the AML, even if
   there are errors during compilation. Remember that some errors
   (e.g., missing Return statements) are automatically worked around
   by the interpreter.

   DSDT.aml is the default output filename for iasl. You can load
   this instead of your BIOS's buggy copy (which is still present in
   flash memory) by editing /boot/loader.conf as follows:

 acpi_dsdt_load="YES"
 acpi_dsdt_name="/boot/DSDT.aml"

   Be sure to copy your DSDT.aml to the /boot directory.

     --------------------------------------------------------------

  11.16.6. Getting Debugging Output From ACPI

   The ACPI driver has a very flexible debugging facility. It allows
   you to specify a set of subsystems as well as the level of
   verbosity. The subsystems you wish to debug are specified as
   !S:layers!" and are broken down into ACPI-CA components
   (ACPI_ALL_COMPONENTS) and ACPI hardware support
   (ACPI_ALL_DRIVERS). The verbosity of debugging output is specified
   as the !S:level!" and ranges from ACPI_LV_ERROR (just report
   errors) to ACPI_LV_VERBOSE (everything). The !S:level!" is a
   bitmask so multiple options can be set at once, separated by
   spaces. In practice, you will want to use a serial console to log
   the output if it is so long it flushes the console message buffer.
   A full list of the individual layers and levels is found in the
   acpi(4) manual page.

   Debugging output is not enabled by default. To enable it, add
   options ACPI_DEBUG to your kernel configuration file if ACPI is
   compiled into the kernel. You can add ACPI_DEBUG=1 to your
   /etc/make.conf to enable it globally. If it is a module, you can
   recompile just your acpi.ko module as follows:

 # cd /sys/modules/acpi/acpi
 && make clean &&
 make ACPI_DEBUG=1

   Install acpi.ko in /boot/kernel and add your desired level and
   layer to loader.conf. This example enables debug messages for all
   ACPI-CA components and all ACPI hardware drivers (CPU, LID, etc.)
   It will only output error messages, the least verbose level.

 debug.acpi.layer="ACPI_ALL_COMPONENTS ACPI_ALL_DRIVERS"
 debug.acpi.level="ACPI_LV_ERROR"

   If the information you want is triggered by a specific event (say,
   a suspend and then resume), you can leave out changes to
   loader.conf and instead use sysctl to specify the layer and level
   after booting and preparing your system for the specific event.
   The sysctls are named the same as the tunables in loader.conf.

     --------------------------------------------------------------

  11.16.7. References

   More information about ACPI may be found in the following
   locations:

     * The FreeBSD ACPI P:l>> 1/4 1/2 * 3/4A

     * The ACPI Mailing List Archives
       http://lists.freebsd.org/pipermail/freebsd-acpi/

     * The old ACPI Mailing List Archives
       http://home.jp.FreeBSD.org/mail-list/acpi-jp/

     * The ACPI 2.0 Specification http://acpi.info/spec.htm

     * FreeBSD Manual pages: acpi(4), acpi_thermal(4), acpidump(8),
       iasl(8), acpidb(8)

     * DSDT debugging resource. (Uses Compaq as an example but
       generally useful.)

     --------------------------------------------------------------

                 ^3^1 12. FreeBSD P:} 3/4-:NOTyu{ 1/2g

12.1. .S:z

   The process of starting a computer and loading the operating
   system is referred to as !S:the bootstrap process!", or simply
   !S:booting!". FreeBSD's boot process provides a great deal of
   flexibility in customizing what happens when you start the system,
   allowing you to select from different operating systems installed
   on the same computer, or even different versions of the same
   operating system or installed kernel.

   This chapter details the configuration options you can set and how
   to customize the FreeBSD boot process. This includes everything
   that happens until the FreeBSD kernel has started, probed for
   devices, and started init(8). If you are not quite sure when this
   happens, it occurs when the text color changes from bright white
   to grey.

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!G

     * What the components of the FreeBSD bootstrap system are, and
       how they interact.

     * The options you can give to the components in the FreeBSD
       bootstrap to control the boot process.

     * device.hints(5) -a-oDEGoYEN>>.S:(c)A!C

     x86 Only: This chapter only describes the boot process for
     FreeBSD running on Intel x86 systems.

     --------------------------------------------------------------

12.2. Booting DEGYAD

   Turning on a computer and starting the operating system poses an
   interesting dilemma. By definition, the computer does not know how
   to do anything until the operating system is started. This
   includes running programs from the disk. So if the computer can
   not run a program from the disk without the operating system, and
   the operating system programs are on the disk, how is the
   operating system started?

   This problem parallels one in the book The Adventures of Baron
   Munchausen. A character had fallen part way down a manhole, and
   pulled himself out by grabbing his bootstraps, and lifting. In the
   early days of computing the term bootstrap was applied to the
   mechanism used to load the operating system, which has become
   shortened to !S:booting!".

   On x86 hardware the Basic Input/Output System (BIOS) is
   responsible for loading the operating system. To do this, the BIOS
   looks on the hard disk for the Master Boot Record (MBR), which
   must be located on a specific place on the disk. The BIOS has
   enough knowledge to load and run the MBR, and assumes that the MBR
   can then carry out the rest of the tasks involved in loading the
   operating system, possibly with the help of the BIOS.

   The code within the MBR is usually referred to as a boot manager,
   especially when it interacts with the user. In this case the boot
   manager usually has more code in the first track of the disk or
   within some OS's file system. (A boot manager is sometimes also
   called a boot loader, but FreeBSD uses that term for a later stage
   of booting.) Popular boot managers include boot0 (a.k.a. Boot
   Easy, the standard FreeBSD boot manager), Grub, GAG, and LILO.
   (Only boot0 fits within the MBR.)

   If you have only one operating system installed on your disks then
   a standard PC MBR will suffice. This MBR searches for the first
   bootable (a.k.a. active) slice on the disk, and then runs the code
   on that slice to load the remainder of the operating system. The
   MBR installed by fdisk(8), by default, is such an MBR. It is based
   on /boot/mbr.

   If you have installed multiple operating systems on your disks
   then you can install a different boot manager, one that can
   display a list of different operating systems, and allows you to
   choose the one to boot from. Two of these are discussed in the
   next subsection.

   The remainder of the FreeBSD bootstrap system is divided into
   three stages. The first stage is run by the MBR, which knows just
   enough to get the computer into a specific state and run the
   second stage. The second stage can do a little bit more, before
   running the third stage. The third stage finishes the task of
   loading the operating system. The work is split into these three
   stages because the PC standards put limits on the size of the
   programs that can be run at stages one and two. Chaining the tasks
   together allows FreeBSD to provide a more flexible loader.

   The kernel is then started and it begins to probe for devices and
   initialize them for use. Once the kernel boot process is finished,
   the kernel passes control to the user process init(8), which then
   makes sure the disks are in a usable state. init(8) then starts
   the user-level resource configuration which mounts file systems,
   sets up network cards to communicate on the network, and generally
   starts all the processes that usually are run on a FreeBSD system
   at startup.

     --------------------------------------------------------------

12.3. The Boot Manager and Boot Stages

     --------------------------------------------------------------

  12.3.1. The Boot Manager

   The code in the MBR or boot manager is sometimes referred to as
   stage zero of the boot process. This subsection discusses two of
   the boot managers previously mentioned: boot0 and LILO.

   The boot0 Boot Manager: The MBR installed by FreeBSD's installer
   or boot0cfg(8), by default, is based on /boot/boot0. (The boot0
   program is very simple, since the program in the MBR can only be
   446 bytes long because of the slice table and 0x55AA identifier at
   the end of the MBR.) If you have installed boot0 and multiple
   operating systems on your hard disks, then you will see a display
   similar to this one at boot time:

   1/2d"O 12-1. boot0 Screenshot

 F1 DOS
 F2 FreeBSD
 F3 Linux
 F4 ??
 F5 Drive 1

 Default: F2

   Other operating systems, in particular Windows, have been known to
   overwrite an existing MBR with their own. If this happens to you,
   or you want to replace your existing MBR with the FreeBSD MBR then
   use the following command:

 # fdisk -B -b /boot/boot0 device

   where device is the device that you boot from, such as ad0 for the
   first IDE disk, ad2 for the first IDE disk on a second IDE
   controller, da0 for the first SCSI disk, and so on. Or, if you
   want a custom configuration of the MBR, use boot0cfg(8).

   The LILO Boot Manager: To install this boot manager so it will
   also boot FreeBSD, first start Linux and add the following to your
   existing /etc/lilo.conf configuration file:

 other=/dev/hdXY
 table=/dev/hdX
 loader=/boot/chain.b
 label=FreeBSD

   In the above, specify FreeBSD's primary partition and drive using
   Linux specifiers, replacing X with the Linux drive letter and Y
   with the Linux primary partition number. If you are using a SCSI
   drive, you will need to change /dev/hd to read something similar
   to /dev/sd. The loader=/boot/chain.b line can be omitted if you
   have both operating systems on the same drive. Now run
   /sbin/lilo -v to commit your new changes to the system; this
   should be verified by checking its screen messages.

     --------------------------------------------------------------

  12.3.2. Stage One, /boot/boot1, and Stage Two, /boot/boot2

   Conceptually the first and second stages are part of the same
   program, on the same area of the disk. Because of space
   constraints they have been split into two, but you would always
   install them together. They are copied from the combined file
   /boot/boot by the installer or disklabel (see below).

   They are located outside file systems, in the first track of the
   boot slice, starting with the first sector. This is where boot0,
   or any other boot manager, expects to find a program to run which
   will continue the boot process. The number of sectors used is
   easily determined from the size of /boot/boot.

   boot1 is very simple, since it can only be 512 bytes in size, and
   knows just enough about the FreeBSD disklabel, which stores
   information about the slice, to find and execute boot2.

   boot2 is slightly more sophisticated, and understands the FreeBSD
   file system enough to find files on it, and can provide a simple
   interface to choose the kernel or loader to run.

   Since the loader is much more sophisticated, and provides a nice
   easy-to-use boot configuration, boot2 usually runs it, but
   previously it was tasked to run the kernel directly.

   1/2d"O 12-2. boot2 Screenshot

 >> FreeBSD/i386 BOOT
 Default: 0:ad(0,a)/kernel
 boot:

   If you ever need to replace the installed boot1 and boot2 use
   disklabel(8):

 # disklabel -B diskslice

   where diskslice is the disk and slice you boot from, such as ad0s1
   for the first slice on the first IDE disk.

     Dangerously Dedicated ModeIf you use just the disk name, such as
     ad0, in the disklabel(8) command you will create a dangerously
     dedicated disk, without slices. This is almost certainly not
     what you want to do, so make sure you double check the
     disklabel(8) command before you press Return.

     --------------------------------------------------------------

  12.3.3. Stage Three, /boot/loader

   The loader is the final stage of the three-stage bootstrap, and is
   located on the file system, usually as /boot/loader.

   The loader is intended as a user-friendly method for
   configuration, using an easy-to-use built-in command set, backed
   up by a more powerful interpreter, with a more complex command
   set.

     --------------------------------------------------------------

    12.3.3.1. Loader Program Flow

   During initialization, the loader will probe for a console and for
   disks, and figure out what disk it is booting from. It will set
   variables accordingly, and an interpreter is started where user
   commands can be passed from a script or interactively.

   The loader will then read /boot/loader.rc, which by default reads
   in /boot/defaults/loader.conf which sets reasonable defaults for
   variables and reads /boot/loader.conf for local changes to those
   variables. loader.rc then acts on these variables, loading
   whichever modules and kernel are selected.

   Finally, by default, the loader issues a 10 second wait for key
   presses, and boots the kernel if it is not interrupted. If
   interrupted, the user is presented with a prompt which understands
   the easy-to-use command set, where the user may adjust variables,
   unload all modules, load modules, and then finally boot or reboot.

     --------------------------------------------------------------

    12.3.3.2. Loader Built-In Commands

   These are the most commonly used loader commands. For a complete
   discussion of all available commands, please see loader(8).

   autoboot seconds

           Proceeds to boot the kernel if not interrupted within the
           time span given, in seconds. It displays a countdown, and
           the default time span is 10 seconds.

   boot [-options] [kernelname]

           Immediately proceeds to boot the kernel, with the given
           options, if any, and with the kernel name given, if it is.

   boot-conf

           Goes through the same automatic configuration of modules
           based on variables as what happens at boot. This only
           makes sense if you use unload first, and change some
           variables, most commonly kernel.

   help [topic]

           Shows help messages read from /boot/loader.help. If the
           topic given is index, then the list of available topics is
           given.

   include filename !K

           Processes the file with the given filename. The file is
           read in, and interpreted line by line. An error
           immediately stops the include command.

   load [-t type] filename

           Loads the kernel, kernel module, or file of the type
           given, with the filename given. Any arguments after
           filename are passed to the file.

   ls [-l] [path]

           Displays a listing of files in the given path, or the root
           directory, if the path is not specified. If -l is
           specified, file sizes will be shown too.

   lsdev [-v]

           Lists all of the devices from which it may be possible to
           load modules. If -v is specified, more details are
           printed.

   lsmod [-v]

           Displays loaded modules. If -v is specified, more details
           are shown.

   more filename

           Displays the files specified, with a pause at each LINES
           displayed.

   reboot

           Immediately reboots the system.

   set variable, set variable=value

           Sets the loader's environment variables.

   unload

           Removes all loaded modules.

     --------------------------------------------------------------

    12.3.3.3. Loader Examples

   Here are some practical examples of loader usage:

     * To simply boot your usual kernel, but in single-user mode:

 boot -s

     * To unload your usual kernel and modules, and then load just
       your old (or another) kernel:

 unload
 load kernel.old

       You can use kernel.GENERIC to refer to the generic kernel that
       comes on the install disk, or kernel.old to refer to your
       previously installed kernel (when you have upgraded or
       configured your own kernel, for example).

         -a`: Use the following to load your usual modules with
         another kernel:

 unload
 set kernel="kernel.old"
 boot-conf

     * To load a kernel configuration script (an automated script
       which does the things you would normally do in the kernel
       boot-time configurator):

 load -t userconfig_script /boot/kernel.conf

     --------------------------------------------------------------

12.4. Kernel Interaction During Boot

   Once the kernel is loaded by either loader (as usual) or boot2
   (bypassing the loader), it examines its boot flags, if any, and
   adjusts its behavior as necessary.

     --------------------------------------------------------------

  12.4.1. Kernel Boot Flags

   Here are the more common boot flags:

   -a

           during kernel initialization, ask for the device to mount
           as the root file system.

   -C

           boot from CDROM.

   -c

           run UserConfig, the boot-time kernel configurator

   -s

           boot into single-user mode

   -v

           be more verbose during kernel startup

     -a`: There are other boot flags, read boot(8) for more
     information on them.

     --------------------------------------------------------------

12.5. Device Hints

   Contributed by Tom Rhodes.

     -a`: This is a FreeBSD 5.0 and later feature which does not
     exist in earlier versions.

   During initial system startup, the boot loader(8) will read the
   device.hints(5) file. This file stores kernel boot information
   known as variables, sometimes referred to as !S:device hints!".
   These !S:device hints!" are used by device drivers for device
   configuration.

   Device hints may also be specified at the   Stage 3 boot loader
   prompt. Variables can be added using set, removed with unset, and
   viewed with the show commands. Variables set in the
   /boot/device.hints file can be overridden here also. Device hints
   entered at the boot loader are not permanent and will be forgotten
   on the next reboot.

   Once the system is booted, the kenv(1) command can be used to dump
   all of the variables.

   The syntax for the /boot/device.hints file is one variable per
   line, using the standard hash !S:#!" as comment markers. Lines are
   constructed as follows:

 hint.driver.unit.keyword="value"

   The syntax for the Stage 3 boot loader is:

 set hint.driver.unit.keyword=value

   driver is the device driver name, unit is the device driver unit
   number, and keyword is the hint keyword. The keyword may consist
   of the following options:

     * at: specifies the bus which the device is attached to.

     * port: specifies the start address of the I/O to be used.

     * irq: specifies the interrupt request number to be used.

     * drq: specifies the DMA channel number.

     * maddr: specifies the physical memory address occupied by the
       device.

     * flags: sets various flag bits for the device.

     * disabled: if set to 1 the device is disabled.

   Device drivers may accept (or require) more hints not listed here,
   viewing their manual page is recommended. For more information,
   consult the device.hints(5), kenv(1), loader.conf(5), and
   loader(8) manual pages.

     --------------------------------------------------------------

12.6. Init: Process Control Initialization

   Once the kernel has finished booting, it passes control to the
   user process init(8), which is located at /sbin/init, or the
   program path specified in the init_path variable in loader.

     --------------------------------------------------------------

  12.6.1. Automatic Reboot Sequence

   The automatic reboot sequence makes sure that the file systems
   available on the system are consistent. If they are not, and
   fsck(8) cannot fix the inconsistencies, init(8) drops the system
   into single-user mode for the system administrator to take care of
   the problems directly.

     --------------------------------------------------------------

  12.6.2. Single-User Mode

   This mode can be reached through the automatic reboot sequence, or
   by the user booting with the -s option or setting the boot_single
   variable in loader.

   It can also be reached by calling shutdown(8) without the reboot
   (-r) or halt (-h) options, from multi-user mode.

   If the system console is set to insecure in /etc/ttys, then the
   system prompts for the root password before initiating single-user
   mode.

   1/2d"O 12-3. An Insecure Console in /etc/ttys

 # name  getty                           type    status          comments
 #
 # If console is marked "insecure", then init will ask for the root password
 # when going to single-user mode.
 console none                            unknown off insecure

     -a`: An insecure console means that you consider your physical
     security to the console to be insecure, and want to make sure
     only someone who knows the root password may use single-user
     mode, and it does not mean that you want to run your console
     insecurely. Thus, if you want security, choose insecure, not
     secure.

     --------------------------------------------------------------

  12.6.3. Multi-User Mode

   If init(8) finds your file systems to be in order, or once the
   user has finished in single-user mode, the system enters
   multi-user mode, in which it starts the resource configuration of
   the system.

     --------------------------------------------------------------

    12.6.3.1. Resource Configuration (rc)

   The resource configuration system reads in configuration defaults
   from /etc/defaults/rc.conf, and system-specific details from
   /etc/rc.conf, and then proceeds to mount the system file systems
   mentioned in /etc/fstab, start up networking services, start up
   miscellaneous system daemons, and finally runs the startup scripts
   of locally installed packages.

   The rc(8) manual page is a good reference to the resource
   configuration system, as is examining the scripts themselves.

     --------------------------------------------------------------

12.7. Shutdown Sequence

   Upon controlled shutdown, via shutdown(8), init(8) will attempt to
   run the script /etc/rc.shutdown, and then proceed to send all
   processes the TERM signal, and subsequently the KILL signal to any
   that do not terminate timely.

   To power down a FreeBSD machine on architectures and systems that
   support power management, simply use the command shutdown -p now
   to turn the power off immediately. To just reboot a FreeBSD
   system, just use shutdown -r now. You need to be root or a member
   of operator group to run shutdown(8). The halt(8) and reboot(8)
   commands can also be used, please refer to their manual pages and
   to shutdown(8)'s one for more information.

     -a`: Power management requires acpi(4) support in the kernel or
     loaded as module for FreeBSD 5.X and apm(4) support for
     FreeBSD 4.X.

     --------------------------------------------------------------

              ^3^1 13. "IYENI-aI>>PDEGoYEN>>+-b,^1-oTH^2z

   Contributed by Neil Blakey-Milner.

13.1. .S:z

   FreeBSD CUR^1^3\|hO"IYENI-aI|P(R)E"IYENI^1q,-L-!C .iuM!A
   ^3o"ACUR-L-NOTO<<U:|hCURH|P(R)ES:CUR|b|PCUR@YENx^1q,-L-<<e
   [9]!A|ONOTO"a:YENL"IYENI-aIYENiYENH^3z^1L-oo,o"O"IYENI|PCUR@YENx^1q,-L-YENHS:^1|"YENLI-a-oCURuS:@!C
   n"IYENI"t^2I-a-o,U:!A"-o>>o"COCURH^3-L-+-o|^3CUR@O+-b,^1!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!G

     * |b FreeBSD "t^2ICURWCUR-L-|P+-b,^1CURS:P:!-a-oDEGIS:O!C

     * |p|o 1/4WYEN[+-b,^1!C

     * |p|oS:RDEG-L-+-b,^1!C

     * |p|oS:oS:i+-b,^1-a-oDEGoYEN>>,e(R)AE!A^1^3NOTO+-b,^1YENth|W!A(c)INOTO"IYENI-a-o
       shell -oO/Ath!C

     * |p|oDEGw^1i+-b,^1!B,s^2O"O^3]!ACURn|p!GCUR^1^3\|s"uDEGO
       3/4D-AAe(c)I CPU ,e. 1/2|h^1euYEN!C

     * |p|o^1BYENI,s^2O!A"OS:o(R)e(c)o:|a-oTH^2z+-b,^1!C

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!G

     * AA,N UNIX CURI FreeBSD (uU 3 ^3^1)-a-oDEGoA|.S:(c)A!C

     --------------------------------------------------------------

13.2. CURP:^2D-

   "t^2I-a-o(c)O|^3|s"uNOTO,gYENN+-b,^1"OP:i|ae!A|O(c)O|^3-a-ou{|!
   process
   NOTOYENN"IYENI-aI"OP:i|ae!A(c)OYENH"IYENI-aICURI+-b,^1-a-o-oTH^2z!ACURDNOTO
   FreeBSD "t^2ICURWCUR-L-YENi(c)I-E-a-o<<AI!C

   (c)O|^3(c)o FreeBSD
   "t^2ICURCUR-a-o+-b,^1NOTOYEN]S:tCURU|CNOTUAo:,eDEGTYENI"O?eAN"YEN-:!C

   "IYENI-aI|W-oU

           "IYENI-aI|W-oUn?eCURJ|b login: '-L-YENU:YENX^2{<<a!C
           "IYENI-aI|W-oUYEN^2P:.NOTO?WCUR@uLCURG!A CUR-L--`a|^3<<
           1/2AE-a-o"IYENI-aI|W-oU!C
           |U:(c)o|p|o<<O/YENss|^3(R)A:"IYENI-aI|W-oU-a-o^3W<<h!A
           1/2D-DEGN 3/4\ passwd(5) >>!(c)u!A
           ^3q+-`"IYENI-aI|W-oUNOTOYENHCURKOYENHCUR-o-a-oCURp
           1/4g|rYENA(c)O^2O|"!C

   +-K 1/2X

           "CO+-b,^1^3-L-YENi 3/4O:|^3CUR@^2O+-K 1/2X!C +-K
           1/2XCUR]YENiYENHCUR-L-^3]!A |p|^1'NCUR-L->>Y+-K
           1/2XS:YYENiunCURJ"t^2I!A|y^3q+-`^3o"A<<DS:(R)u|!A
           "CO+-b,^1^3-L-A^3^3](c)wCUR@^2O+-K 1/2X!C

   "IYENI-aIYENN,^1 (User ID, UID)

           UID NOTO"t^2IYENI"O?eAN"IYENI-aI-a-o 1/4AE|r!A^3q+-`
           1/2d^3oNOTO+-q 0 "`i 65535 [10]!C FreeBSD
           CUR-o^3!NOTO"IYENI UID "O?eAN"IYENI-aI !X!X FreeBSD
           |bDEGo|aeYENo|o<<u:(c)w"IYENI-aI-a-o<<u:YENOCURS:<<e!A^3-L-.|YENyS:a"IYENI-aI|W-oUA`a'<<NOTDEG
           UID!C CUR]'NNOTO>>!!ACURn|pYENiYENH|^3
           1/4AEOCUR-L-|P-a-o"IYENI-aI|W-oU!A
           |yNOTO^3-L-"IYENI|PCUR@O UID!A^1i FreeBSD
           "O>>!!A^3o"C,+-b,^1^3-L-YENuYENN-ai|PCUR@"IYENI-aI!C
           CUR-L-^1L!A^1e>>UCURW>>Yn^3o
           1/4EDEGu-a-oYENi-`a(c)ECUR-L-CURj!C

   ,s^2OYENN,^1 (Group ID, GID)

           GID NOTO"t^2IYENI"O?eAN"IYENI-aI(c)OA:Y,s^2O-a-o
           1/4AE|r!A^3q+-` 1/2d^3oNOTO+-q 0 "`i 65535[10] !C
           YENI,s^2O"O+-+-"i,e.
           1/2|s"u!AYENi|^3(R)A:'iCURO:CUR@"C,^3](c)wAE-a-oCURjCURp!C
           |^1YEN~!A"IYENI-aIAUYENiYENH|P(R)EA:Y(c)o|hOCUR-L-|P-a-o,s^2O!C

   unCURJCURAAth(Login classes)

           unCURJCURAAthNOTO,s^2O-a-o(c)u|u 3/4-:"i!A
           '-L-"NCURFCUR-L-|P-a-o"IYENI-aIS:o 1/4u(c)E-a-o!C

   +-K 1/2XAAU:S:o'A

           FreeBSD ^1w^3]"ACUR-L-n"D"IYENI-aIP:g'A(c)E-a-oS:oS:i+-K
           1/2X!C+-zYENiYENH+-j"iNOTY"C,(c)I
           YENth^3!-a-o"IYENI-aI|b<<u:(c)w-a-o'AP:!^1L<<aYEN^2P:.S:oS:i+-K
           1/2X!C

   +-b,^1'A

           FreeBSD -a-o+-b,^1"S|^3^1w^3]-a-o'A!A|p-aG+-zCURw-a
           3/4^1D+-b,^1-a-o"IYENI'A!A "O|p!A 3/4C,(R)OCURCUR'-L-"N
           3/4C,YENI"IYENI-a-o+-b,^1!AYENi|b<<O/YENss+-b,^1(R)E<<u:(c)w+-b,^1-a-o'A!C
           .i+-b,^1^1L'A<<a.|uL-akunCURJ"t^2I!A|y,O+-b,^1-a-oYENO/?yCURIAE(R)
           *<<h.|<<O-d!C

   "IYENI-aIYENth|W

           FreeBSD
           -a-o+-b,^1"IYENI"IYENI-aI|W-oUYENI"O?eAN!A|y"IYENI-aI|W-oU"ACUR-L-CUR@(c)wYENN-ai
           -u^1e"IYENI-aI-a-o(c)m|W!CNOTDEG+-b,^1(c)O>>Y-a-oNOTUAo:,eDEGT!C

   (R)aYENO/?y

           (R)aYENO/?yNOTDEG"IYENI-aIunCURJ"t^2I(R)E-a-o(c)O|bYENO/?y-a-oS:^1
           3/4a,o(R)|!C
           ^3q+-`.|+-N(c)O|^3"IYENI-aI-a-o(R)aYENO/?y(c)n,m(c)o
           /home/"IYENI-aI|W-oU (c)I /usr/home/"IYENI-aI|W-oU!C
           "IYENI-aIYENiYENH+-N"a:OCURH-a-o,e(R)AE(c)n,m(c)o"a:(R)aYENO/?yCURS:CURCUR!A"AYENiYENH|b|^1YENO/?y(c)^3CURU
           <<O/YENss.s-a-oYENO/?y

   "IYENI-aI Shell

           Shell
           '-L-"N^1w^3]-a-oAo^1OAAy"IYENI-aI>>P"t^2ICURNOTDEGE!C
           Shell  3/4O:|^3 1/4AE-oO/CUR-L-|P-a-o-oO/Ath,
           YENi"NP:iP:YEN"IYENI-aI"I"IYENI^2ss-oD?i 3/4U:!C

   +-b,^1YENDnCURANOTDEGCURU|CCURTAth: "t^2I-oTH^2z-aI+-b,^1,
   "t^2I+-b,^1!ACURI "IYENI-aI+-b,^1!C
   "t^2I-oTH^2z-aI+-b,^1-a-o+-b,^1 ^3q+-`NOTDEG root!A
   3/4O:|^3^3ICURj-a-oAAv"O-oTH^2z"t^2I!C
   "t^2I+-b,^1YENI"ODEGo|ae|o/-aA
   3/4^1-aADEGE!C^3I<<a!A"IYENI-aI+-b,^1"N-uYEN?-a-o"IYENI-aI"IYENI!A
   YENiunCURJ!BAA-a<<HuYENuYEN!C

     --------------------------------------------------------------

13.3. "t^2I-oTH^2z-aI+-b,^1

   The superuser account, usually called root, comes preconfigured to
   facilitate system administration, and should not be used for
   day-to-day tasks like sending and receiving mail, general
   exploration of the system, or programming.

   This is because the superuser, unlike normal user accounts, can
   operate without limits, and misuse of the superuser account may
   result in spectacular disasters. User accounts are unable to
   destroy the system by mistake, so it is generally best to use
   normal user accounts whenever possible, unless you especially need
   the extra privilege.

   You should always double and triple-check commands you issue as
   the superuser, since an extra space or missing character can mean
   irreparable data loss.

   So, the first thing you should do after reading this chapter is to
   create an unprivileged user account for yourself for general usage
   if you have not already. This applies equally whether you are
   running a multi-user or single-user machine. Later in this
   chapter, we discuss how to create additional accounts, and how to
   change between the normal user and superuser.

     --------------------------------------------------------------

13.4. "t^2I+-b,^1

   System users are those used to run services such as DNS, mail, web
   servers, and so forth. The reason for this is security; if all
   services ran as the superuser, they could act without restriction.

   Examples of system users are daemon, operator, bind (for the
   Domain Name Service), news, and www.

   nobody is the generic unprivileged system user. However, it is
   important to keep in mind that the more services that use nobody,
   the more files and processes that user will become associated
   with, and hence the more privileged that user becomes.

     --------------------------------------------------------------

13.5. "IYENI-aI+-b,^1

   User accounts are the primary means of access for real people to
   the system, and these accounts insulate the user and the
   environment, preventing the users from damaging the system or
   other users, and allowing users to customize their environment
   without affecting others.

   Every person accessing your system should have a unique user
   account. This allows you to find out who is doing what, prevent
   people from clobbering each others' settings or reading each
   others' mail, and so forth.

   Each user can set up their own environment to accommodate their
   use of the system, by using alternate shells, editors, key
   bindings, and language.

     --------------------------------------------------------------

13.6. S:oS:i+-b,^1

   |b UNIX
   -a-oAo^1OCURS:CURCUR'-L-"NCURF|U|!CUR-L-|P-a-o<<u:YENO-oTH^2z"IYENI-aI+-b,^1!A
   YENHCURUNOTDEG,u+-`"IYENI-a-o<<u:YENO-oKnCURIS:o,O^2O-a-o"IYENI
   1/2d"O!C

         <<u:YENO                            -oKn                     
   adduser(8)            .s 1/4W"IYENI-aI!C                           
   rmuser(8)             ^2 3/4DEG-L-"IYENI-aI!C                      
   chpass(1)             S:oS:i"IYENI-aI,e(R)AE!C                     
   passwd(1)             S:oS:i"IYENI-aI+-K 1/2X!C                    
   pw(8)                 *S:i"IYENI-aI-a-o|U-oO/,e(R)AE!C             

     --------------------------------------------------------------

  13.6.1. adduser

   adduser(8) NOTOCUR@CURa:.s 1/4W"IYENI-aI-a-oA^2^3aeu{|!!C
   YEN|.|<<O/YENss,e(R)AE(c)o"t^2I-a-o passwd >>P group AE(R)
   *CURS:CURCUR!C |P(R)ECUR].|<<O/YENss"IYENI-aI-a-o(R)aYENO/?y!A+-q 
   /usr/share/skel  1/2AE>>s^1w^3]-a-o^2O-oAAE(!S:dotfiles!")!A
   "AYENiYENH?i 3/4U:(c)E-a-oP:lYENo^3q-a
   3/4.s"IYENI-aIAAw-aiDEGT(R)S:!C

   1/2d"O 13-1. |b FreeBSD CUR-o.s 1/4W"IYENI-aI

 # adduser
 Username: jru
 Full name: J. Random User
 Uid (Leave empty for default):
 Login group [jru]:
 Login group is jru. Invite jru into other groups? []: wheel
 Login class [default]:
 Shell (sh csh tcsh zsh nologin) [sh]: zsh
 Home directory [/home/jru]:
 Use password-based authentication? [yes]:
 Use an empty password? (yes/no) [no]:
 Use a random password? (yes/no) [no]:
 Enter password:
 Enter password again:
 Lock out the account after creation? [no]:
 Username   : jru
 Password   : ****
 Full Name  : J. Random User
 Uid        : 1001
 Class      :
 Groups     : jru wheel
 Home       : /home/jru
 Shell      : /usr/local/bin/zsh
 Locked     : no
 OK? (yes/no): yes
 adduser: INFO: Successfully added (jru) to the user database.
 Add another user? (yes/no): no
 Goodbye!
 #

     -a`: +-z?eCURJ-a-o+-K
     1/2X"ACUR-L-.||^A^3"`i?A^1o!A(c)OYENHCUR-L-.|YENHNOTP,^1AAaYENU:
     !C  1/2D- 1/2T(c)w+-z(c)O?eCURJ-a-o+-K 1/2XuL>>~!C

     --------------------------------------------------------------

  13.6.2. rmuser

   +-zYENiYENH"IYENI rmuser(8)
   "O+-N"IYENI-aI+-q"t^2ICURS:CURCURS:^1YENth^2 3/4DEG-L- rmuser(8)
   .|DEGo|aeYENHCURUDEGES:@:

    1. ^2 3/4DEG-L-,O"IYENI-aI-a-o crontab(1) ,e(R)AE (|p-aG|s|b)!C

    2. ^2 3/4DEG-L-(c)O|^3A:Y(c)o,O"IYENI-aI-a-o at(1) CURuS:@!C

    3. CURCURCURi(c)O|^3,O"IYENI-aI 3/4O:|^3-a-ou{S:C,!C

    4. ^2 3/4DEG-L-"t^2IYEN>> 3/4-:+-K
       1/2XAECURCUR,O"IYENI-aI-a-o,e(R)AE!C

    5. ^2 3/4DEG-L-,O"IYENI-aI-a-o(R)aYENO/?y
       (|p-aGNOTDEG,O"IYENI-aI(c)O|^3)!C

    6. ^2 3/4DEG-L- /var/mail CURCURA:Y(c)o,O"IYENI-aI-a-oP:lYENo!C

    7. ^2 3/4DEG-L- 1/4E|s-aAAP:! (|p: /tmp)
       CURCUR(c)O|^3A:Y(c)o,O"IYENI-aI-a-oAE(R) *!C

    8. ^3I<<a!A|b /etc/group AECUR-o^2 3/4DEG-L-,O"IYENI-aI+-b,^1!C

         -a`:
         Y,O,s^2OCURwuL|"u!A(c)I-aINOTO,s^2O|W-oU>>P,O"IYENI-aI|W-oUNOTU|P(R)E!A
         <<h,s^2O+-N.|^3Q^2 3/4DEG-L-!F |^1 3/4THS:@.|>>P adduser(8)
         (c)O<<O/YENss-a-o+-b,^1,s^2ONOTU^1iA^3!C

   rmuser(8) uL-ak^2 3/4DEG-L-"t^2I-oTH^2z-aI+-b,^1+-b,^1!A
   |]NOTDEG^3oS:YYENN-aiA:Y<<-a-o-}Aa|aeNOTDEG!C

   NOTDEGCURF 1/2T>>{+-z-a-o 3/4THS:@!A^1w^3]+-A:CURNOTDEGE 1/4O|!!C

   1/2d"O 13-2. rmuser +-b,^1^2 3/4DEG-L-

 # rmuser jru
 Matching password entry:
 jru:*:1001:1001::0:0:J. Random User:/home/jru:/usr/local/bin/zsh
 Is this the entry you wish to remove? y
 Remove user's home directory (/home/jru)? y
 Updating password file, updating databases, done.
 Updating group file: trusted (removing group jru -- personal group is empty) done.
 Removing user's incoming mail file /var/mail/jru: done.
 Removing files belonging to jru from /tmp: done.
 Removing files belonging to jru from /var/tmp: done.
 Removing files belonging to jru from /var/tmp/vi.recover: done.
 #

     --------------------------------------------------------------

  13.6.3. chpass

   chpass(1) YENiS:oS:i"IYENI-aI,e(R)AE|p: +-K
   1/2X!BShellCURIOCURH,eDEGT!C

   P:E"t^2I-oTH^2z-aIS:Y"t^2I-oTH^2z-aI+-b,^1YENiS:QYENI chpass(1)
   S:oS:i"a:YENL"IYENI-aI-a-o,eDEGTCURI+-K 1/2X

   DEG-L-CURF<<u:(c)w"IYENI-aI|W-oU!A.iCUR-L-YEN[DEGN
   1/4AE(R)E!Achpass(1) .|+-N"IYENI-aI,eDEGTAAaYENU:(c)o 1/2s?e
   3/4^1.iCURCUR!C "A(c)o"IYENI-aIA-:P:} 1/2s?e
   3/4^1(R)ES:o.s"IYENI-aI,eDEGT!C

     -a`: Y+-z"A<<D"t^2I-oTH^2z-aI+-b,^1!A|bA-:P:} 1/2s?e
     3/4^1<<e.|,ssDEGY+-z-a-o+-K 1/2X!C

   1/2d"O 13-3. "t^2I-oTH^2z-aI+-b,^1 chpass

 #Changing user database information for jru.
 Login: jru
 Password: *
 Uid [#]: 1001
 Gid [# or name]: 1001
 Change [month day year]:
 Expire [month day year]:
 Class:
 Home directory: /home/jru
 Shell: /usr/local/bin/zsh
 Full Name: J. Random User
 Office Location:
 Office Phone:
 Home Phone:
 Other information:

   CUR@-e"IYENI-aIP:EYENiS:oS:i|UCURv-a-oCURO:^3!YEN-:,eDEGT!C

   1/2d"O 13-4. CUR@-e"IYENI-aI chpass

 #Changing user database information for jru.
 Shell: /usr/local/bin/zsh
 Full Name: J. Random User
 Office Location:
 Office Phone:
 Home Phone:
 Other information:

     -a`: chfn(1) >>P chsh(1) S:YNOTDEG chpass(1)!ACUR]|P
     ypchpass(1)!Bypchfn(1) >>P ypchsh(1)!C NIS
     CURa:'(c)NOTO|UDEGE-a-o!A(c)OYENHuL>>Y|b<<u:YENO<<eYEN[CURW yp!C
     Y^3o.|S:xAZ+-z!A 1/2D-CUR-L-YEN^2 3/4aCURss!AuU 27 ^3^1
     +-N"c,>>\ NIS -a-o^3!YEN-:-a-o>>!(c)u!C

     --------------------------------------------------------------

  13.6.4. passwd

   passwd(1) NOTOS:oS:i+-K
   1/2X+-`YENI-a-oCURe|!!ADEG-L-CURFP:W-AA-oTH^2z-aIYENiS:oS:i"a:YENL"IYENI-aI-a-o+-K
   1/2XYEN~ "IYENI-aIP:E-`aS:oS:i|UCURv-a-o+-K 1/2X!C

     -a`: NOTDEGCURFA *S:K.NYEN~(c)IYEN 1/4,g|P.N-a-o
     *S:i!A|bS:o.s+-K 1/2X<<e>>Y?eCURJ`i+-K 1/2X!C

   1/2d"O 13-5. S:oS:i+-z-a-o+-K 1/2X

 % passwd
 Changing local password for jru.
 Old password:
 New password:
 Retype new password:
 passwd: updating the database...
 passwd: done

   1/2d"O 13-6.
   YENH"t^2I-oTH^2z-aI+-b,^1YENhS:oS:i"a:YENL"IYENI-aI-a-o+-K 1/2X

 # passwd jru
 Changing local password for jru.
 New password:
 Retype new password:
 passwd: updating the database...
 passwd: done

     -a`: chpass(1)!B yppasswd(1) S:YNOTDEG passwd(1)!ANOTOCURa:'(c)
     NIS!C

     --------------------------------------------------------------

  13.6.5. pw

   pw(8) YENI"O<<O/YENss!B^2 3/4DEG-L-!B
   *S:iCURINOTd,ss"IYENI-aICURI,s^2O!C
   "a:YEN\-`aS:YNOTDEG"t^2I"IYENI-aICURI,s^2OAE(R) *-a-o<<e-oY!Cpw(8)
    3/4O:|^3CURjP:q-a-o<<u:YENODEGN 1/4AE ,u 3/4A|X"IYENI(c)o shell
   script CURCUR!A^1i.sCURa"O>>!.||^1<<u:YENO,u"a:YENL<<u:YENO
   1/2AEAo/^3\|h!C

     --------------------------------------------------------------

13.7. "IYENI-aI,e. 1/2"i

   Y+-z 3/4O:|^3^3\|h"IYENI-aI!A+-uCURU.|.Q"`i,O|p|o"i"IYENI-a-o,e.
   1/2!C FreeBSD '-L-"N-oTH^2z-aI^3\|hCURe-ak"O"i"t^2I-a-o,e.
   1/2u^1"COCURH"IYENI!C ^3o"C,"iCURANOTDEG"aO^3!YEN-::
   -oI-oD-AB!AYENHCURI"a:YENL,e. 1/2"i!C

   -oI-oD-ABYENiYENH"i"IYENI-aI-a-o-oI-oD-YENIP:q!A
   YEN|'-L-"NCURFCUR@-oO/CURe-akYENiYENHS:O:^3t-a-oAENOTd"Ap-oaYENIP:q
   |OCUR-L->>Y"C|,<<.sp-oa!A Ao:(c)o-oI-oD-AB+-N(c)o uU 18.15 ,`
   .|DEGQ 1/2 *!C

   "a:YENL,e. 1/2"iYEN]S:tCURF CPU!BDEGO
   3/4D-AAe!BYENHCURI"a:YENL"CO"IYENI-aIYENi"IYENI -a-o,e.
   1/2DEGu"i!A^3o"C,"iYENi"IYENI Login class
   "O(c)w,q"A(c)o|bYEN>>^3^1DEGQ 1/2 *!C

   Login class (c)w,q(c)o /etc/login.conf!C (c)u
   1/2T>>y.NCUR-L-.||bYEN>>,`>>!(c)u |y,O^2O-a-o'yz.||b login.conf(5)
   CURaaYENoCURCUR!C "C"IYENI-aI^1w^3]^3Q CURADEGt"`iCUR@O Login
   class CURCUR (^1w^3]NOTDEG default)!A |O"CO Login class
   ^3-L-|^3"a:,e. 1/2-a-o"i(Login capabilitiy)!C Login capabilitiy
   YENH |W-oU=E |"^1i!A |W-oU YENN-ai,e. 1/2-a-o-oO/Ath!A|O E
   NOTDEGYENo.N-a-o|r|e!ANOTDEG^1iA^3|W-oU-a-oDEGN 1/4AE!C ^3](c)w
   Login class CURI Login capability NOTU.iA^2^3ae!A"A|P 1/4E|b
   login.conf(5) CURCUR,O^2O>>!(c)u!C

     -a`: "t^2ICUR-L-.|-a 1/2+-uAA-a"u /etc/login.conf -a-o^2O-oA
     |ONOTOAA-a"u'-L-"NNOTd,ss,uS:O:-a-o /etc/login.conf.db
     ,e(R)AE(R)wAE!C n+-q /etc/login.conf ^2-L-YENI
     /etc/login.conf.db >>YnDEGo|aeYENHCURU<<u:YENO:

 # cap_mkdb /etc/login.conf

   ,e. 1/2"i(c)oCUR@-e-a-o Login capability |^3"aAICUR-L-|P!C
   ^2A:CUR@!A"C-oO/"iCURANOTDEG^3n(c)E"iCURIuw(c)E"i!C
   ^3n(c)E"iYENiYENN"IYENI-aI(c)IA^3YENIu{|! 1/2O
   3/4a!A|yCUR-L--`aDEG-a(c)ouw(c)E"i!C
   <<a-aI"iYENi^3Q"IYENI-aIDEGS:C!A|yuL-ak|A'-L-DEG-a!C ^2A:CURG!A|h
   1/4AE,e.
   1/2"iNOTODEGw^1i"CO"IYENI-aI-a-oOS:O|aeu{"i!A|OCUR-L-NOTO"IYENI-aI-a-o(c)O|^3|aeu{!C
   -a`.N!A^3o"C,(R)t^2S:NOTOYENN<<u:(c)w-a-o"iu{|!|<<-oTH!A"A<<D^1eS:@(c)o
   Login capability -a-oNOT[-oc ("O|p!A^3o"C,CUR-L-NOTO -uYEN?
   unCURJ(R)eP:q-a-o-S"O)!C

   YENtYEN~!ANOTDEGCURFA *S:K^3A.D-!AYENHCURUNOTDEG'XO+-`YENI-a-o,e.
   1/2"i (^3NCURUCURI"a:YENL-a-o Login capability YENi|b
   login.conf(5) CURCURS:a:"`i>>!(c)u)!C

   coredumpsize

           The limit on the size of a core file generated by a
           program is, for obvious reasons, subordinate to other
           limits on disk usage (e.g., filesize, or disk quotas).
           Nevertheless, it is often used as a less-severe method of
           controlling disk space consumption: since users do not
           generate core files themselves, and often do not delete
           them, setting this may save them from running out of disk
           space should a large program (e.g., emacs) crash.

   cputime

           This is the maximum amount of CPU time a user's process
           may consume. Offending processes will be killed by the
           kernel.

             -a`: This is a limit on CPU time consumed, not
             percentage of the CPU as displayed in some fields by
             top(1) and ps(1). A limit on the latter is, at the time
             of this writing, not possible, and would be rather
             useless: a compiler!X!Xprobably a legitimate task!X!Xcan
             easily use almost 100% of a CPU for some time.

   filesize

           This is the maximum size of a file the user may possess.
           Unlike disk quotas, this limit is enforced on individual
           files, not the set of all files a user owns.

   maxproc

           This is the maximum number of processes a user may be
           running. This includes foreground and background processes
           alike. For obvious reasons, this may not be larger than
           the system limit specified by the kern.maxproc sysctl(8).
           Also note that setting this too small may hinder a user's
           productivity: it is often useful to be logged in multiple
           times or execute pipelines. Some tasks, such as compiling
           a large program, also spawn multiple processes (e.g.,
           make(1), cc(1), and other intermediate preprocessors).

   memorylocked

           This is the maximum amount a memory a process may have
           requested to be locked into main memory (e.g., see
           mlock(2)). Some system-critical programs, such as amd(8),
           lock into main memory such that in the event of being
           swapped out, they do not contribute to a system's trashing
           in time of trouble.

   memoryuse

           This is the maximum amount of memory a process may consume
           at any given time. It includes both core memory and swap
           usage. This is not a catch-all limit for restricting
           memory consumption, but it is a good start.

   openfiles

           This is the maximum amount of files a process may have
           open. In FreeBSD, files are also used to represent sockets
           and IPC channels; thus, be careful not to set this too
           low. The system-wide limit for this is defined by the
           kern.maxfiles sysctl(8).

   sbsize

           This is the limit on the amount of network memory, and
           thus mbufs, a user may consume. This originated as a
           response to an old DoS attack by creating a lot of
           sockets, but can be generally used to limit network
           communications.

   stacksize

           This is the maximum size a process' stack may grow to.
           This alone is not sufficient to limit the amount of memory
           a program may use; consequently, it should be used in
           conjunction with other limits.

   There are a few other things to remember when setting resource
   limits. Following are some general tips, suggestions, and
   miscellaneous comments.

     * Processes started at system startup by /etc/rc are assigned to
       the daemon login class.

     * Although the /etc/login.conf that comes with the system is a
       good source of reasonable values for most limits, only you,
       the administrator, can know what is appropriate for your
       system. Setting a limit too high may open your system up to
       abuse, while setting it too low may put a strain on
       productivity.

     * Users of the X Window System (X11) should probably be granted
       more resources than other users. X11 by itself takes a lot of
       resources, but it also encourages users to run more programs
       simultaneously.

     * Remember that many limits apply to individual processes, not
       the user as a whole. For example, setting openfiles to 50
       means that each process the user runs may open up to 50 files.
       Thus, the gross amount of files a user may open is the value
       of openfiles multiplied by the value of maxproc. This also
       applies to memory consumption.

   For further information on resource limits and login classes and
   capabilities in general, please consult the relevant manual pages:
   cap_mkdb(1), getrlimit(2), login.conf(5).

     --------------------------------------------------------------

13.8. ,s^2O

   A group is simply a list of users. Groups are identified by their
   group name and GID (Group ID). In FreeBSD (and most other UNIX
   like systems), the two factors the kernel uses to decide whether a
   process is allowed to do something is its user ID and list of
   groups it belongs to. Unlike a user ID, a process has a list of
   groups associated with it. You may hear some things refer to the
   !S:group ID!" of a user or process; most of the time, this just
   means the first group in the list.

   The group name to group ID map is in /etc/group. This is a plain
   text file with four colon-delimited fields. The first field is the
   group name, the second is the encrypted password, the third the
   group ID, and the fourth the comma-delimited list of members. It
   can safely be edited by hand (assuming, of course, that you do not
   make any syntax errors!). For a more complete description of the
   syntax, see the group(5) manual page.

   If you do not want to edit /etc/group manually, you can use the
   pw(8) command to add and edit groups. For example, to add a group
   called teamtwo and then confirm that it exists you can use:

   1/2d"O 13-7. Adding a Group Using pw(8)

 # pw groupadd teamtwo
 # pw groupshow teamtwo
 teamtwo:*:1100:

   The number 1100 above is the group ID of the group teamtwo. Right
   now, teamtwo has no members, and is thus rather useless. Let's
   change that by inviting jru to the teamtwo group.

   1/2d"O 13-8. Adding Somebody to a Group Using pw(8)

 # pw groupmod teamtwo -M jru
 # pw groupshow teamtwo
 teamtwo:*:1100:jru

   The argument to the -M option is a comma-delimited list of users
   who are members of the group. From the preceding sections, we know
   that the password file also contains a group for each user. The
   latter (the user) is automatically added to the group list by the
   system; the user will not show up as a member when using the
   groupshow command to pw(8), but will show up when the information
   is queried via id(1) or similar tool. In other words, pw(8) only
   manipulates the /etc/group file; it will never attempt to read
   additionally data from /etc/passwd.

   1/2d"O 13-9. Using id(1) to Determine Group Membership

 % id jru
 uid=1001(jru) gid=1001(jru) groups=1001(jru), 1100(teamtwo)

   As you can see, jru is a member of the groups jru and teamtwo.

   For more information about pw(8), see its manual page, and for
   more information on the format of /etc/group, consult the group(5)
   manual page.

     --------------------------------------------------------------

                         ^3^1 14. "t^2I|wYENth

   Much of this chapter has been taken from the security(7) manual
   page by Matthew Dillon.

     --------------------------------------------------------------

14.1. .S:z

   ^3oCUR@^3^1+-N^1i"t^2I|wYENth-a-oDEGoYEN>>.S:(c)AP:i|aeCURP:^2D-!ADEG-L-|^1CURS:YEN~!AAU+-NCURP:^2D-CUR@"C,|n-a-o^2ss-oD!AYENHCURI
   FreeBSD
   CURU-a-oCUR@"C,S:o^2`CURJ-a-o,U:AD!C^3o^3^1-a-o^3\|hCUR-o(R)e^1i(c)oCUR@-e-a-o"t^2I(c)M
   Internet |wYENthCUR] 3/4AYENI!C|pCURu!AInternet
   CURw,gCUR-L-|A^1^3YENH<<e"-o
   1/4ENOTOOCURHCURH^3-L-A:@.N>>P+-zS:@|n 3/4F(c)~-a-o!yCURIu
   1/2^3o(c)O!z!C
   YEN^2P:.AAy"t^2IS:o|wYENth!ACUR~-`aYENh<<OAA@+-z-a-o,e(R)AE!B' 1/4
   1/4zDEG]^2-L-!BA:_P:Q(R)EP:!YENHCURI"a:YENL<<U:|h-aF|e!A
   |OCUR-L-|U:(c)o^3QCURJ<<I-aI(c)ICURss|s'c.N-a-oCURH(c)OAAN"u!C

   FreeBSD '-L-"NCURFCUR@"t|CCURu"a(c)MNOTUAo: 3/4-:"i!A"O
   1/2T<<O"t^2I(c)M-oo,o-a-oS:^1 3/4a!B|wYENth!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!J

     * FreeBSD "t^2I-a-oDEGoYEN>>|wYENth.S:(c)A!C

     * FreeBSD CURCUR^3\|hYENiYENI-a-oYEN[+-K 3/4-:"i!A"O|p DES CURI
       MD5!C

     * |p|o<<O/YENssCUR@|,(c)E(one-time)+-K 1/2XAAc,AO 3/4-:"i!C

     * |p|o^3](c)w TCP Wrappers YENH<<K>>P inetd DEGt|X"IYENI!C

     * |p|o|b FreeBSD 5.0. CURS:<<e-a-o-a(c)YEN>>CURW^3](c)w
       KerberosIV!C

     * |p|o|b FreeBSD 5.0 (S:tCURS:<<a-a(c)YEN>>)CURW^3](c)w
       Kerberos5!C

     * |p|o^3](c)w IPsec YENHCURI|b FreeBSD/Windows CURW<<O/YENss VPN
       -oo,o!C

     * |p|o^3](c)w!B^1BYENI OpenSSH!AYENHCURI FreeBSD -a-o SSH
       ^1eS:@CURe|!(implementation)

     * CURF,NAE(R) *"t^2I-a-o ACLs 
       3/4-:"iNOTDEG|o!AYENHCURI|p|o^1BYENI!C

     * |p|o"IYENI Portaudit CURu"a"OAEAAc,(audit) +-q Ports
       Collection |w,E-a-o^3nAAe|wYENth(c)E!C

     * |p|ou 1/2YENI FreeBSD |wYENthCUR 1/2S:i(Security
       Advisories)!A"A+-A:"uNOTUA^3+-^1NOTI!C

     * AA,N Process Accounting  3/4-:"iCURI|p|o|b FreeBSD
       CURW+-ODEGE!C

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!J

     * AA,N FreeBSD CURI Internet -a-oDEGoYEN>>.S:(c)A!C

   YEN>>(R)NCURCUR"a:YENL^3^1,`!ACUR]|^3CURP:^2D-|wYENthCURe+--a-o"a:YENL,U:AD!C"O|p!G
   |b uU 16 ^3^1 |^3 1/2I"`i Mandatory Access Control!A Internet
   Firewalls <<h|b uU 28 ^3^1!C

     --------------------------------------------------------------

14.2. CURP:^2D-

   |wYENth!A^1i"t^2I-oTH^2z-aI|O"YEN!ANOTO|U:(c)l|U:^2
   *^3IDEGoYEN>>-a-on"D!CYENN(c)o(c)O|^3-a-o BSD UNIX multi-user
   "t^2I^3-L-'-L-"NCURF>>PYENIN"O-a-oDEGoYEN>>|wYENth!A(c)OYENH<<O/YENss!B-ouAA@ABYEN~-a-o|wYENth
   3/4-:"i!AYENH 1/2T<<O"IYENI-aI-a-o!yYENi 3/4a!z!A
   YENi-`aCUR]'NNOTO"t^2I-oTH^2zu^3I>>Yn.V<<a:-a-oA}YEN"YENoDEGECURF!C
   3/4-:
   3/4^1-a-o|wYENth(c)E"u"M(c)o+-z(c)O<<O/YENss-a-o|wYENth+-^1NOTI!A
   |O^3\|h|wYENthCURe+--a-o|OP:q!A<<h.|>>PCURHI"IYENI^1q,-L-(R)E-a-o<<KS:QNOTUYENUNOTTH!CCUR@-e"O>>!!A
   UNIX "t^2IYENi|P(R)EDEGo|ae^3\|h 1/4AEYENO/-a-ou{|! process
   !A"AYENB"a:CURCUR^3\|h process CUR]|P(R)EYENH Server -oY"O^1BS:@!C
   -c-w-c-w ^3o.N"yuU!AYEN~^3!^1eAAe 3/4-:
   3/4^1-`aDEG-:>>PYEN|ICURNOTNOTU^3s+-u!A"A^2-L-YENICURNOTDEGE!C^2{|b-a-oCUR@-e(R)`a
   3/4-:!A CURw,g-`aDEG-:^1F"`iYENH<<eCURp<<NOTYEND
   3/4-:NOTAE|U:CURj<<NOTYEND
   3/4-:-a-o(c)E-`a!A|OAHuU^3o"C,^1q,-L--a-o-oo,o^3s+-u(c)M|bS:oCURj
   1/2d^3oCUR-oCURNOTNOTU^3s+-u
   !A|wYENthCUR]|"NOTDEGCURFCUR@OCURe-qA:Y(R)m-a-o 1/2OAD!C

   |wYENth^3I|n-a-oCURe|!!ANOTO-`aDEG-:^3z^1L^1^3!yNOTv 1/2u!z"-o
   1/4E-a-o 1/4h 1/4h" 3/4AA@ 1/4O|!!C A^2^3aeA?!AA^3,O
   3/4"YENi-`a-a-o<<O/YENss|h 1/4h|,|wYENth"
   3/4AA@!A"ACURpCURss|a-oEuo/|UAthDEGw^1i"t^2I-a-oCURJ<<I-oAAI!C You
   do not want to overbuild your security or you will interfere with
   the detection side, and detection is one of the single most
   important aspects of any security mechanism. For example, it makes
   little sense to set the schg flag (see chflags(1)) on every system
   binary because while this may temporarily protect the binaries, it
   prevents an attacker who has broken in from making an easily
   detectable change that may result in your security mechanisms not
   detecting the attacker at all.

   System security also pertains to dealing with various forms of
   attack, including attacks that attempt to crash, or otherwise make
   a system unusable, but do not attempt to compromise the root
   account (!S:break root!"). Security concerns can be split up into
   several categories:

    1. -aADEGE-ayA_S:d-A>>(DoS)

    2. AAN"u"a:YENL"IYENI-aI-a-o+-b,^1!C

    3. ^3z^1L|U|! Server CURW(c)O'-L-"N-a-o Service "OAAN"u root
       +-b,^1!C

    4. ^3z^1L"IYENI-aI+-b,^1AAN"u root +-b,^1!C

    5. P:}<<a-au!C

   A denial of service attack is an action that deprives the machine
   of needed resources. Typically, DoS attacks are brute-force
   mechanisms that attempt to crash or otherwise make a machine
   unusable by overwhelming its servers or network stack. Some DoS
   attacks try to take advantage of bugs in the networking stack to
   crash a machine with a single packet. The latter can only be fixed
   by applying a bug fix to the kernel. Attacks on servers can often
   be fixed by properly specifying options to limit the load the
   servers incur on the system under adverse conditions. Brute-force
   network attacks are harder to deal with. A spoofed-packet attack,
   for example, is nearly impossible to stop, short of cutting your
   system off from the Internet. It may not be able to take your
   machine down, but it can saturate your Internet connection.

   A user account compromise is even more common than a DoS attack.
   Many sysadmins still run standard telnetd, rlogind, rshd, and ftpd
   servers on their machines. These servers, by default, do not
   operate over encrypted connections. The result is that if you have
   any moderate-sized user base, one or more of your users logging
   into your system from a remote location (which is the most common
   and convenient way to login to a system) will have his or her
   password sniffed. The attentive system admin will analyze his
   remote access logs looking for suspicious source addresses even
   for successful logins.

   One must always assume that once an attacker has access to a user
   account, the attacker can break root. However, the reality is that
   in a well secured and maintained system, access to a user account
   does not necessarily give the attacker access to root. The
   distinction is important because without access to root the
   attacker cannot generally hide his tracks and may, at best, be
   able to do nothing more than mess with the user's files, or crash
   the machine. User account compromises are very common because
   users tend not to take the precautions that sysadmins take.

   System administrators must keep in mind that there are potentially
   many ways to break root on a machine. The attacker may know the
   root password, the attacker may find a bug in a root-run server
   and be able to break root over a network connection to that
   server, or the attacker may know of a bug in a suid-root program
   that allows the attacker to break root once he has broken into a
   user's account. If an attacker has found a way to break root on a
   machine, the attacker may not have a need to install a backdoor.
   Many of the root holes found and closed to date involve a
   considerable amount of work by the attacker to cleanup after
   himself, so most attackers install backdoors. A backdoor provides
   the attacker with a way to easily regain root access to the
   system, but it also gives the smart system administrator a
   convenient way to detect the intrusion. Making it impossible for
   an attacker to install a backdoor may actually be detrimental to
   your security, because it will not close off the hole the attacker
   found to break in the first place.

   Security remedies should always be implemented with a
   multi-layered !S:onion peel!" approach and can be categorized as
   follows:

    1. Securing root and staff accounts.

    2. Securing root!Vrun servers and suid/sgid binaries.

    3. Securing user accounts.

    4. Securing the password file.

    5. Securing the kernel core, raw devices, and file systems.

    6. Quick detection of inappropriate changes made to the system.

    7. Paranoia.

   The next section of this chapter will cover the above bullet items
   in greater depth.

     --------------------------------------------------------------

14.3. FreeBSD -a-o"t^2I|wYENth

     Command vs. Protocol: Throughout this document, we will use bold
     text to refer to an application, and a monospaced font to refer
     to specific commands. Protocols will use a normal font. This
     typographical distinction is useful for instances such as ssh,
     since it is a protocol as well as command.

   The sections that follow will cover the methods of securing your
   FreeBSD system that were mentioned in the last section of this
   chapter.

     --------------------------------------------------------------

  14.3.1. Securing the root Account and Staff Accounts

   First off, do not bother securing staff accounts if you have not
   secured the root account. Most systems have a password assigned to
   the root account. The first thing you do is assume that the
   password is always compromised. This does not mean that you should
   remove the password. The password is almost always necessary for
   console access to the machine. What it does mean is that you
   should not make it possible to use the password outside of the
   console or possibly even with the su(1) command. For example, make
   sure that your ptys are specified as being insecure in the
   /etc/ttys file so that direct root logins via telnet or rlogin are
   disallowed. If using other login services such as sshd, make sure
   that direct root logins are disabled there as well. You can do
   this by editing your /etc/ssh/sshd_config file, and making sure
   that PermitRootLogin is set to NO. Consider every access method
   !X!X services such as FTP often fall through the cracks. Direct
   root logins should only be allowed via the system console.

   Of course, as a sysadmin you have to be able to get to root, so we
   open up a few holes. But we make sure these holes require
   additional password verification to operate. One way to make root
   accessible is to add appropriate staff accounts to the wheel group
   (in /etc/group). The staff members placed in the wheel group are
   allowed to su to root. You should never give staff members native
   wheel access by putting them in the wheel group in their password
   entry. Staff accounts should be placed in a staff group, and then
   added to the wheel group via the /etc/group file. Only those staff
   members who actually need to have root access should be placed in
   the wheel group. It is also possible, when using an authentication
   method such as Kerberos, to use Kerberos' .k5login file in the
   root account to allow a ksu(1) to root without having to place
   anyone at all in the wheel group. This may be the better solution
   since the wheel mechanism still allows an intruder to break root
   if the intruder has gotten hold of your password file and can
   break into a staff account. While having the wheel mechanism is
   better than having nothing at all, it is not necessarily the
   safest option.

   An indirect way to secure staff accounts, and ultimately root
   access is to use an alternative login access method and do what is
   known as !S:starring!" out the encrypted password for the staff
   accounts. Using the vipw(8) command, one can replace each instance
   of an encrypted password with a single !S:*!" character. This
   command will update the /etc/master.passwd file and user/password
   database to disable password-authenticated logins.

   A staff account entry such as:

 foobar:R9DT/Fa1/LV9U:1000:1000::0:0:Foo Bar:/home/foobar:/usr/local/bin/tcsh

   Should be changed to this:

 foobar:*:1000:1000::0:0:Foo Bar:/home/foobar:/usr/local/bin/tcsh

   This change will prevent normal logins from occurring, since the
   encrypted password will never match !S:*!". With this done, staff
   members must use another mechanism to authenticate themselves such
   as kerberos(1) or ssh(1) using a public/private key pair. When
   using something like Kerberos, one generally must secure the
   machines which run the Kerberos servers and your desktop
   workstation. When using a public/private key pair with ssh, one
   must generally secure the machine used to login from (typically
   one's workstation). An additional layer of protection can be added
   to the key pair by password protecting the key pair when creating
   it with ssh-keygen(1). Being able to !S:star!" out the passwords
   for staff accounts also guarantees that staff members can only
   login through secure access methods that you have set up. This
   forces all staff members to use secure, encrypted connections for
   all of their sessions, which closes an important hole used by many
   intruders: sniffing the network from an unrelated, less secure
   machine.

   The more indirect security mechanisms also assume that you are
   logging in from a more restrictive server to a less restrictive
   server. For example, if your main box is running all sorts of
   servers, your workstation should not be running any. In order for
   your workstation to be reasonably secure you should run as few
   servers as possible, up to and including no servers at all, and
   you should run a password-protected screen blanker. Of course,
   given physical access to a workstation an attacker can break any
   sort of security you put on it. This is definitely a problem that
   you should consider, but you should also consider the fact that
   the vast majority of break-ins occur remotely, over a network,
   from people who do not have physical access to your workstation or
   servers.

   Using something like Kerberos also gives you the ability to
   disable or change the password for a staff account in one place,
   and have it immediately affect all the machines on which the staff
   member may have an account. If a staff member's account gets
   compromised, the ability to instantly change his password on all
   machines should not be underrated. With discrete passwords,
   changing a password on N machines can be a mess. You can also
   impose re-passwording restrictions with Kerberos: not only can a
   Kerberos ticket be made to timeout after a while, but the Kerberos
   system can require that the user choose a new password after a
   certain period of time (say, once a month).

     --------------------------------------------------------------

  14.3.2. Securing Root-run Servers and SUID/SGID Binaries

   The prudent sysadmin only runs the servers he needs to, no more,
   no less. Be aware that third party servers are often the most
   bug-prone. For example, running an old version of imapd or popper
   is like giving a universal root ticket out to the entire world.
   Never run a server that you have not checked out carefully. Many
   servers do not need to be run as root. For example, the ntalk,
   comsat, and finger daemons can be run in special user sandboxes. A
   sandbox is not perfect, unless you go through a large amount of
   trouble, but the onion approach to security still stands: If
   someone is able to break in through a server running in a sandbox,
   they still have to break out of the sandbox. The more layers the
   attacker must break through, the lower the likelihood of his
   success. Root holes have historically been found in virtually
   every server ever run as root, including basic system servers. If
   you are running a machine through which people only login via sshd
   and never login via telnetd or rshd or rlogind, then turn off
   those services!

   FreeBSD now defaults to running ntalkd, comsat, and finger in a
   sandbox. Another program which may be a candidate for running in a
   sandbox is named(8). /etc/defaults/rc.conf includes the arguments
   necessary to run named in a sandbox in a commented-out form.
   Depending on whether you are installing a new system or upgrading
   an existing system, the special user accounts used by these
   sandboxes may not be installed. The prudent sysadmin would
   research and implement sandboxes for servers whenever possible.

   There are a number of other servers that typically do not run in
   sandboxes: sendmail, popper, imapd, ftpd, and others. There are
   alternatives to some of these, but installing them may require
   more work than you are willing to perform (the convenience factor
   strikes again). You may have to run these servers as root and rely
   on other mechanisms to detect break-ins that might occur through
   them.

   The other big potential root holes in a system are the suid-root
   and sgid binaries installed on the system. Most of these binaries,
   such as rlogin, reside in /bin, /sbin, /usr/bin, or /usr/sbin.
   While nothing is 100% safe, the system-default suid and sgid
   binaries can be considered reasonably safe. Still, root holes are
   occasionally found in these binaries. A root hole was found in
   Xlib in 1998 that made xterm (which is typically suid) vulnerable.
   It is better to be safe than sorry and the prudent sysadmin will
   restrict suid binaries, that only staff should run, to a special
   group that only staff can access, and get rid of (chmod 000) any
   suid binaries that nobody uses. A server with no display generally
   does not need an xterm binary. Sgid binaries can be almost as
   dangerous. If an intruder can break an sgid-kmem binary, the
   intruder might be able to read /dev/kmem and thus read the
   encrypted password file, potentially compromising any passworded
   account. Alternatively an intruder who breaks group kmem can
   monitor keystrokes sent through ptys, including ptys used by users
   who login through secure methods. An intruder that breaks the tty
   group can write to almost any user's tty. If a user is running a
   terminal program or emulator with a keyboard-simulation feature,
   the intruder can potentially generate a data stream that causes
   the user's terminal to echo a command, which is then run as that
   user.

     --------------------------------------------------------------

  14.3.3. Securing User Accounts

   User accounts are usually the most difficult to secure. While you
   can impose Draconian access restrictions on your staff and
   !S:star!" out their passwords, you may not be able to do so with
   any general user accounts you might have. If you do have
   sufficient control, then you may win out and be able to secure the
   user accounts properly. If not, you simply have to be more
   vigilant in your monitoring of those accounts. Use of ssh and
   Kerberos for user accounts is more problematic, due to the extra
   administration and technical support required, but still a very
   good solution compared to a crypted password file.

     --------------------------------------------------------------

  14.3.4. Securing the Password File

   The only sure fire way is to * out as many passwords as you can
   and use ssh or Kerberos for access to those accounts. Even though
   the encrypted password file (/etc/spwd.db) can only be read by
   root, it may be possible for an intruder to obtain read access to
   that file even if the attacker cannot obtain root-write access.

   Your security scripts should always check for and report changes
   to the password file (see the Checking file integrity section
   below).

     --------------------------------------------------------------

  14.3.5. Securing the Kernel Core, Raw Devices, and File systems

   If an attacker breaks root he can do just about anything, but
   there are certain conveniences. For example, most modern kernels
   have a packet sniffing device driver built in. Under FreeBSD it is
   called the bpf device. An intruder will commonly attempt to run a
   packet sniffer on a compromised machine. You do not need to give
   the intruder the capability and most systems do not have the need
   for the bpf device compiled in.

   But even if you turn off the bpf device, you still have /dev/mem
   and /dev/kmem to worry about. For that matter, the intruder can
   still write to raw disk devices. Also, there is another kernel
   feature called the module loader, kldload(8). An enterprising
   intruder can use a KLD module to install his own bpf device, or
   other sniffing device, on a running kernel. To avoid these
   problems you have to run the kernel at a higher secure level, at
   least securelevel 1. The securelevel can be set with a sysctl on
   the kern.securelevel variable. Once you have set the securelevel
   to 1, write access to raw devices will be denied and special
   chflags flags, such as schg, will be enforced. You must also
   ensure that the schg flag is set on critical startup binaries,
   directories, and script files !X!X everything that gets run up to
   the point where the securelevel is set. This might be overdoing
   it, and upgrading the system is much more difficult when you
   operate at a higher secure level. You may compromise and run the
   system at a higher secure level but not set the schg flag for
   every system file and directory under the sun. Another possibility
   is to simply mount / and /usr read-only. It should be noted that
   being too Draconian in what you attempt to protect may prevent the
   all-important detection of an intrusion.

     --------------------------------------------------------------

  14.3.6. Checking File Integrity: Binaries, Configuration Files, Etc.

   When it comes right down to it, you can only protect your core
   system configuration and control files so much before the
   convenience factor rears its ugly head. For example, using chflags
   to set the schg bit on most of the files in / and /usr is probably
   counterproductive, because while it may protect the files, it also
   closes a detection window. The last layer of your security onion
   is perhaps the most important !X!X detection. The rest of your
   security is pretty much useless (or, worse, presents you with a
   false sense of safety) if you cannot detect potential incursions.
   Half the job of the onion is to slow down the attacker, rather
   than stop him, in order to give the detection side of the equation
   a chance to catch him in the act.

   The best way to detect an incursion is to look for modified,
   missing, or unexpected files. The best way to look for modified
   files is from another (often centralized) limited-access system.
   Writing your security scripts on the extra-secure limited-access
   system makes them mostly invisible to potential attackers, and
   this is important. In order to take maximum advantage you
   generally have to give the limited-access box significant access
   to the other machines in the business, usually either by doing a
   read-only NFS export of the other machines to the limited-access
   box, or by setting up ssh key-pairs to allow the limited-access
   box to ssh to the other machines. Except for its network traffic,
   NFS is the least visible method !X!X allowing you to monitor the
   file systems on each client box virtually undetected. If your
   limited-access server is connected to the client boxes through a
   switch, the NFS method is often the better choice. If your
   limited-access server is connected to the client boxes through a
   hub, or through several layers of routing, the NFS method may be
   too insecure (network-wise) and using ssh may be the better choice
   even with the audit-trail tracks that ssh lays.

   Once you give a limited-access box, at least read access to the
   client systems it is supposed to monitor, you must write scripts
   to do the actual monitoring. Given an NFS mount, you can write
   scripts out of simple system utilities such as find(1) and md5(1).
   It is best to physically md5 the client-box files at least once a
   day, and to test control files such as those found in /etc and
   /usr/local/etc even more often. When mismatches are found,
   relative to the base md5 information the limited-access machine
   knows is valid, it should scream at a sysadmin to go check it out.
   A good security script will also check for inappropriate suid
   binaries and for new or deleted files on system partitions such as
   / and /usr.

   When using ssh rather than NFS, writing the security script is
   much more difficult. You essentially have to scp the scripts to
   the client box in order to run them, making them visible, and for
   safety you also need to scp the binaries (such as find) that those
   scripts use. The ssh client on the client box may already be
   compromised. All in all, using ssh may be necessary when running
   over insecure links, but it is also a lot harder to deal with.

   A good security script will also check for changes to user and
   staff members access configuration files: .rhosts, .shosts,
   .ssh/authorized_keys and so forth!K files that might fall outside
   the purview of the MD5 check.

   If you have a huge amount of user disk space, it may take too long
   to run through every file on those partitions. In this case,
   setting mount flags to disallow suid binaries and devices on those
   partitions is a good idea. The nodev and nosuid options (see
   mount(8)) are what you want to look into. You should probably scan
   them anyway, at least once a week, since the object of this layer
   is to detect a break-in whether or not the break-in is effective.

   Process accounting (see accton(8)) is a relatively low-overhead
   feature of the operating system which might help as a
   post-break-in evaluation mechanism. It is especially useful in
   tracking down how an intruder has actually broken into a system,
   assuming the file is still intact after the break-in occurs.

   Finally, security scripts should process the log files, and the
   logs themselves should be generated in as secure a manner as
   possible !X!X remote syslog can be very useful. An intruder tries
   to cover his tracks, and log files are critical to the sysadmin
   trying to track down the time and method of the initial break-in.
   One way to keep a permanent record of the log files is to run the
   system console to a serial port and collect the information on a
   continuing basis through a secure machine monitoring the consoles.

     --------------------------------------------------------------

  14.3.7. Paranoia

   A little paranoia never hurts. As a rule, a sysadmin can add any
   number of security features, as long as they do not affect
   convenience, and can add security features that do affect
   convenience with some added thought. Even more importantly, a
   security administrator should mix it up a bit !X!X if you use
   recommendations such as those given by this document verbatim, you
   give away your methodologies to the prospective attacker who also
   has access to this document.

     --------------------------------------------------------------

  14.3.8. DoS(Denial of Service)-aADEGE-ayA_S:d-A>>

   ^3oCUR@,`+-NCURP:^2D--aADEGE-ayA_S:d-A>>!C DoS
   S:d-A>>^3q+-`NOTOYENH<<EYEN]-a-oCURe|!P:i|aeS:d-A>>!A 
   3/4"-oTH'XYENG"S|^3YENo|o?`i-ak"O-ayCURiCURjP:q-a-oDEGDEG^3y<<EYEN]-O-oE-oo,o,e.
   1/2!A
   |y^3q+-`YENiYENH^3z^1LCUR@"C,CURe|!"ODEGS:C^3oAthS:d-A>>-a-o.l(R)`!A"IYEN|IuL-akA>><<+-|o/-aA
   3/4^1!C

    1. Limiting server forks.

    2. Limiting springboard attacks (ICMP response S:d-A>>!Aping
       broadcastuYENuYEN)

    3. Kernel Route Cache.

   A common DoS attack is against a forking server that attempts to
   cause the server to eat processes, file descriptors, and memory,
   until the machine dies. inetd (see inetd(8)) has several options
   to limit this sort of attack. It should be noted that while it is
   possible to prevent a machine from going down, it is not generally
   possible to prevent a service from being disrupted by the attack.
   Read the inetd manual page carefully and pay specific attention to
   the -c, -C, and -R options. Note that spoofed-IP attacks will
   circumvent the -C option to inetd, so typically a combination of
   options must be used. Some standalone servers have
   self-fork-limitation parameters.

   Sendmail has its -OMaxDaemonChildren option, which tends to work
   much better than trying to use sendmail's load limiting options
   due to the load lag. You should specify a MaxDaemonChildren
   parameter, when you start sendmail, high enough to handle your
   expected load, but not so high that the computer cannot handle
   that number of sendmails without falling on its face. It is also
   prudent to run sendmail in queued mode (-ODeliveryMode=queued) and
   to run the daemon (sendmail -bd) separate from the queue-runs
   (sendmail -q15m). If you still want real-time delivery you can run
   the queue at a much lower interval, such as -q1m, but be sure to
   specify a reasonable MaxDaemonChildren option for that sendmail to
   prevent cascade failures.

   Syslogd can be attacked directly and it is strongly recommended
   that you use the -s option whenever possible, and the -a option
   otherwise.

   You should also be fairly careful with connect-back services such
   as TCP Wrapper's reverse-identd, which can be attacked directly.
   You generally do not want to use the reverse-ident feature of TCP
   Wrapper for this reason.

   It is a very good idea to protect internal services from external
   access by firewalling them off at your border routers. The idea
   here is to prevent saturation attacks from outside your LAN, not
   so much to protect internal services from network-based root
   compromise. Always configure an exclusive firewall, i.e.,
   !S:firewall everything except ports A, B, C, D, and M-Z!". This
   way you can firewall off all of your low ports except for certain
   specific services such as named (if you are primary for a zone),
   ntalkd, sendmail, and other Internet-accessible services. If you
   try to configure the firewall the other way !X!X as an inclusive
   or permissive firewall, there is a good chance that you will
   forget to !S:close!" a couple of services, or that you will add a
   new internal service and forget to update the firewall. You can
   still open up the high-numbered port range on the firewall, to
   allow permissive-like operation, without compromising your low
   ports. Also take note that FreeBSD allows you to control the range
   of port numbers used for dynamic binding, via the various
   net.inet.ip.portrange sysctl's (sysctl -a | fgrep portrange),
   which can also ease the complexity of your firewall's
   configuration. For example, you might use a normal first/last
   range of 4000 to 5000, and a hiport range of 49152 to 65535, then
   block off everything under 4000 in your firewall (except for
   certain specific Internet-accessible ports, of course).

   Another common DoS attack is called a springboard attack !X!X to
   attack a server in a manner that causes the server to generate
   responses which overloads the server, the local network, or some
   other machine. The most common attack of this nature is the ICMP
   ping broadcast attack. The attacker spoofs ping packets sent to
   your LAN's broadcast address with the source IP address set to the
   actual machine they wish to attack. If your border routers are not
   configured to stomp on ping's to broadcast addresses, your LAN
   winds up generating sufficient responses to the spoofed source
   address to saturate the victim, especially when the attacker uses
   the same trick on several dozen broadcast addresses over several
   dozen different networks at once. Broadcast attacks of over a
   hundred and twenty megabits have been measured. A second common
   springboard attack is against the ICMP error reporting system. By
   constructing packets that generate ICMP error responses, an
   attacker can saturate a server's incoming network and cause the
   server to saturate its outgoing network with ICMP responses. This
   type of attack can also crash the server by running it out of
   mbuf's, especially if the server cannot drain the ICMP responses
   it generates fast enough. FreeBSD 4.X kernels have a kernel
   compile option called ICMP_BANDLIM which limits the effectiveness
   of these sorts of attacks. Later kernels use the sysctl variable
   net.inet.icmp.icmplim. The last major class of springboard attacks
   is related to certain internal inetd services such as the udp echo
   service. An attacker simply spoofs a UDP packet with the source
   address being server A's echo port, and the destination address
   being server B's echo port, where server A and B are both on your
   LAN. The two servers then bounce this one packet back and forth
   between each other. The attacker can overload both servers and
   their LANs simply by injecting a few packets in this manner.
   Similar problems exist with the internal chargen port. A competent
   sysadmin will turn off all of these inetd-internal test services.

   Spoofed packet attacks may also be used to overload the kernel
   route cache. Refer to the net.inet.ip.rtexpire, rtminexpire, and
   rtmaxcache sysctl parameters. A spoofed packet attack that uses a
   random source IP will cause the kernel to generate a temporary
   cached route in the route table, viewable with netstat -rna |
   fgrep W3. These routes typically timeout in 1600 seconds or so. If
   the kernel detects that the cached route table has gotten too big
   it will dynamically reduce the rtexpire but will never decrease it
   to less than rtminexpire. There are two problems:

    1. The kernel does not react quickly enough when a lightly loaded
       server is suddenly attacked.

    2. The rtminexpire is not low enough for the kernel to survive a
       sustained attack.

   If your servers are connected to the Internet via a T3 or better,
   it may be prudent to manually override both rtexpire and
   rtminexpire via sysctl(8). Never set either parameter to zero
   (unless you want to crash the machine). Setting both parameters to
   2 seconds should be sufficient to protect the route table from
   attack.

     --------------------------------------------------------------

  14.3.9. Access Issues with Kerberos and SSH

   There are a few issues with both Kerberos and ssh that need to be
   addressed if you intend to use them. Kerberos V is an excellent
   authentication protocol, but there are bugs in the kerberized
   telnet and rlogin applications that make them unsuitable for
   dealing with binary streams. Also, by default Kerberos does not
   encrypt a session unless you use the -x option. ssh encrypts
   everything by default.

   ssh works quite well in every respect except that it forwards
   encryption keys by default. What this means is that if you have a
   secure workstation holding keys that give you access to the rest
   of the system, and you ssh to an insecure machine, your keys are
   usable. The actual keys themselves are not exposed, but ssh
   installs a forwarding port for the duration of your login, and if
   an attacker has broken root on the insecure machine he can utilize
   that port to use your keys to gain access to any other machine
   that your keys unlock.

   We recommend that you use ssh in combination with Kerberos
   whenever possible for staff logins. ssh can be compiled with
   Kerberos support. This reduces your reliance on potentially
   exposed ssh keys while at the same time protecting passwords via
   Kerberos. ssh keys should only be used for automated tasks from
   secure machines (something that Kerberos is unsuited to do). We
   also recommend that you either turn off key-forwarding in the ssh
   configuration, or that you make use of the from=IP/DOMAIN option
   that ssh allows in its authorized_keys file to make the key only
   usable to entities logging in from specific machines.

     --------------------------------------------------------------

14.4. DES, MD5, and Crypt

   Parts rewritten and updated by Bill Swingle.

   Every user on a UNIX system has a password associated with their
   account. It seems obvious that these passwords need to be known
   only to the user and the actual operating system. In order to keep
   these passwords secret, they are encrypted with what is known as a
   !S:one-way hash!", that is, they can only be easily encrypted but
   not decrypted. In other words, what we told you a moment ago was
   obvious is not even true: the operating system itself does not
   really know the password. It only knows the encrypted form of the
   password. The only way to get the !S:plain-text!" password is by a
   brute force search of the space of possible passwords.

   Unfortunately the only secure way to encrypt passwords when UNIX
   came into being was based on DES, the Data Encryption Standard.
   This was not such a problem for users resident in the US, but
   since the source code for DES could not be exported outside the
   US, FreeBSD had to find a way to both comply with US law and
   retain compatibility with all the other UNIX variants that still
   used DES.

   The solution was to divide up the encryption libraries so that US
   users could install the DES libraries and use DES but
   international users still had an encryption method that could be
   exported abroad. This is how FreeBSD came to use MD5 as its
   default encryption method. MD5 is believed to be more secure than
   DES, so installing DES is offered primarily for compatibility
   reasons.

     --------------------------------------------------------------

  14.4.1. Recognizing Your Crypt Mechanism

   Before FreeBSD 4.4 libcrypt.a was a symbolic link pointing to the
   library which was used for encryption. FreeBSD 4.4 changed
   libcrypt.a to provide a configurable password authentication hash
   library. Currently the library supports DES, MD5 and Blowfish hash
   functions. By default FreeBSD uses MD5 to encrypt passwords.

   It is pretty easy to identify which encryption method FreeBSD is
   set up to use. Examining the encrypted passwords in the
   /etc/master.passwd file is one way. Passwords encrypted with the
   MD5 hash are longer than those encrypted with the DES hash and
   also begin with the characters $1$. Passwords starting with $2a$
   are encrypted with the Blowfish hash function. DES password
   strings do not have any particular identifying characteristics,
   but they are shorter than MD5 passwords, and are coded in a
   64-character alphabet which does not include the $ character, so a
   relatively short string which does not begin with a dollar sign is
   very likely a DES password.

   The password format used for new passwords is controlled by the
   passwd_format login capability in /etc/login.conf, which takes
   values of des, md5 or blf. See the login.conf(5) manual page for
   more information about login capabilities.

     --------------------------------------------------------------

14.5. One-time Passwords

   S/Key is a one-time password scheme based on a one-way hash
   function. FreeBSD uses the MD4 hash for compatibility but other
   systems have used MD5 and DES-MAC. S/Key has been part of the
   FreeBSD base system since version 1.1.5 and is also used on a
   growing number of other operating systems. S/Key is a registered
   trademark of Bell Communications Research, Inc.

   From version 5.0 of FreeBSD, S/Key has been replaced with the
   functionally equivalent OPIE (One-time Passwords In Everything).
   OPIE uses the MD5 hash by default.

   There are three different sorts of passwords which we will discuss
   below. The first is your usual UNIX style or Kerberos password; we
   will call this a !S:UNIX password!". The second sort is the
   one-time password which is generated by the S/Key key program or
   the OPIE opiekey(1) program and accepted by the keyinit or
   opiepasswd(1) programs and the login prompt; we will call this a
   !S:one-time password!". The final sort of password is the secret
   password which you give to the key/opiekey programs (and sometimes
   the keyinit/opiepasswd programs) which it uses to generate
   one-time passwords; we will call it a !S:secret password!" or just
   unqualified !S:password!".

   The secret password does not have anything to do with your UNIX
   password; they can be the same but this is not recommended. S/Key
   and OPIE secret passwords are not limited to 8 characters like old
   UNIX passwords[11], they can be as long as you like. Passwords of
   six or seven word long phrases are fairly common. For the most
   part, the S/Key or OPIE system operates completely independently
   of the UNIX password system.

   Besides the password, there are two other pieces of data that are
   important to S/Key and OPIE. One is what is known as the !S:seed!"
   or !S:key!", consisting of two letters and five digits. The other
   is what is called the !S:iteration count!", a number between 1 and
   100. S/Key creates the one-time password by concatenating the seed
   and the secret password, then applying the MD4/MD5 hash as many
   times as specified by the iteration count and turning the result
   into six short English words. These six English words are your
   one-time password. The authentication system (primarily PAM) keeps
   track of the last one-time password used, and the user is
   authenticated if the hash of the user-provided password is equal
   to the previous password. Because a one-way hash is used it is
   impossible to generate future one-time passwords if a successfully
   used password is captured; the iteration count is decremented
   after each successful login to keep the user and the login program
   in sync. When the iteration count gets down to 1, S/Key and OPIE
   must be reinitialized.

   There are three programs involved in each system which we will
   discuss below. The key and opiekey programs accept an iteration
   count, a seed, and a secret password, and generate a one-time
   password or a consecutive list of one-time passwords. The keyinit
   and opiepasswd programs are used to initialize S/Key and OPIE
   respectively, and to change passwords, iteration counts, or seeds;
   they take either a secret passphrase, or an iteration count, seed,
   and one-time password. The keyinfo and opieinfo programs examine
   the relevant credentials files (/etc/skeykeys or /etc/opiekeys)
   and print out the invoking user's current iteration count and
   seed.

   There are four different sorts of operations we will cover. The
   first is using keyinit or opiepasswd over a secure connection to
   set up one-time-passwords for the first time, or to change your
   password or seed. The second operation is using keyinit or
   opiepasswd over an insecure connection, in conjunction with key or
   opiekey over a secure connection, to do the same. The third is
   using key/opiekey to log in over an insecure connection. The
   fourth is using key or opiekey to generate a number of keys which
   can be written down or printed out to carry with you when going to
   some location without secure connections to anywhere.

     --------------------------------------------------------------

  14.5.1. Secure Connection Initialization

   To initialize S/Key for the first time, change your password, or
   change your seed while logged in over a secure connection (e.g. on
   the console of a machine or via ssh), use the keyinit command
   without any parameters while logged in as yourself:

 % keyinit
 Adding unfurl:
 Reminder - Only use this method if you are directly connected.
 If you are using telnet or rlogin exit with no password and use keyinit -s.
 Enter secret password:
 Again secret password:

 ID unfurl s/key is 99 to17757
 DEFY CLUB PRO NASH LACE SOFT

   For OPIE, opiepasswd is used instead:

 % opiepasswd -c
 [grimreaper] ~ $ opiepasswd -f -c
 Adding unfurl:
 Only use this method from the console; NEVER from remote. If you are using
 telnet, xterm, or a dial-in, type ^C now or exit with no password.
 Then run opiepasswd without the -c parameter.
 Using MD5 to compute responses.
 Enter new secret pass phrase:
 Again new secret pass phrase:
 ID unfurl OTP key is 499 to4268
 MOS MALL GOAT ARM AVID COED

   At the Enter new secret pass phrase: or Enter secret password:
   prompts, you should enter a password or phrase. Remember, this is
   not the password that you will use to login with, this is used to
   generate your one-time login keys. The !S:ID!" line gives the
   parameters of your particular instance: your login name, the
   iteration count, and seed. When logging in the system will
   remember these parameters and present them back to you so you do
   not have to remember them. The last line gives the particular
   one-time password which corresponds to those parameters and your
   secret password; if you were to re-login immediately, this
   one-time password is the one you would use.

     --------------------------------------------------------------

  14.5.2. Insecure Connection Initialization

   To initialize or change your secret password over an insecure
   connection, you will need to already have a secure connection to
   some place where you can run key or opiekey; this might be in the
   form of a desk accessory on a Macintosh, or a shell prompt on a
   machine you trust. You will also need to make up an iteration
   count (100 is probably a good value), and you may make up your own
   seed or use a randomly-generated one. Over on the insecure
   connection (to the machine you are initializing), use the keyinit
   -s command:

 % keyinit -s
 Updating unfurl:
 Old key: to17758
 Reminder you need the 6 English words from the key command.
 Enter sequence count from 1 to 9999: 100
 Enter new key [default to17759]:
 s/key 100 to 17759
 s/key access password:
 s/key access password:CURE MIKE BANE HIM RACY GORE

   For OPIE, you need to use opiepasswd:

 % opiepasswd

 Updating unfurl:
 You need the response from an OTP generator.
 Old secret pass phrase:
         otp-md5 498 to4268 ext
         Response: GAME GAG WELT OUT DOWN CHAT
 New secret pass phrase:
         otp-md5 499 to4269
         Response: LINE PAP MILK NELL BUOY TROY

 ID mark OTP key is 499 gr4269
 LINE PAP MILK NELL BUOY TROY

   To accept the default seed (which the keyinit program confusingly
   calls a key), press Return. Then before entering an access
   password, move over to your secure connection or S/Key desk
   accessory, and give it the same parameters:

 % key 100 to17759
 Reminder - Do not use this program while logged in via telnet or rlogin.
 Enter secret password: <secret password>
 CURE MIKE BANE HIM RACY GORE

   Or for OPIE:

 % opiekey 498 to4268
 Using the MD5 algorithm to compute response.
 Reminder: Don't use opiekey from telnet or dial-in sessions.
 Enter secret pass phrase:
 GAME GAG WELT OUT DOWN CHAT

   Now switch back over to the insecure connection, and copy the
   one-time password generated over to the relevant program.

     --------------------------------------------------------------

  14.5.3. Generating a Single One-time Password

   Once you have initialized S/Key or OPIE, when you login you will
   be presented with a prompt like this:

 % telnet example.com
 Trying 10.0.0.1...
 Connected to example.com
 Escape character is '^]'.

 FreeBSD/i386 (example.com) (ttypa)

 login: <username>
 s/key 97 fw13894
 Password:

   Or for OPIE:

 % telnet example.com
 Trying 10.0.0.1...
 Connected to example.com
 Escape character is '^]'.

 FreeBSD/i386 (example.com) (ttypa)

 login: <username>
 otp-md5 498 gr4269 ext
 Password:

   As a side note, the S/Key and OPIE prompts have a useful feature
   (not shown here): if you press Return at the password prompt, the
   prompter will turn echo on, so you can see what you are typing.
   This can be extremely useful if you are attempting to type in a
   password by hand, such as from a printout.

   At this point you need to generate your one-time password to
   answer this login prompt. This must be done on a trusted system
   that you can run key or opiekey on. (There are versions of these
   for DOS, Windows and Mac OS as well.) They need both the iteration
   count and the seed as command line options. You can cut-and-paste
   these right from the login prompt on the machine that you are
   logging in to.

   On the trusted system:

 % key 97 fw13894
 Reminder - Do not use this program while logged in via telnet or rlogin.
 Enter secret password:
 WELD LIP ACTS ENDS ME HAAG

   For OPIE:

 % opiekey 498 to4268
 Using the MD5 algorithm to compute response.
 Reminder: Don't use opiekey from telnet or dial-in sessions.
 Enter secret pass phrase:
 GAME GAG WELT OUT DOWN CHAT

   Now that you have your one-time password you can continue logging
   in:

 login: <username>
 s/key 97 fw13894
 Password: <return to enable echo>
 s/key 97 fw13894
 Password [echo on]: WELD LIP ACTS ENDS ME HAAG
 Last login: Tue Mar 21 11:56:41 from 10.0.0.2 ...

     --------------------------------------------------------------

  14.5.4. Generating Multiple One-time Passwords

   Sometimes you have to go places where you do not have access to a
   trusted machine or secure connection. In this case, it is possible
   to use the key and opiekey commands to generate a number of
   one-time passwords beforehand to be printed out and taken with
   you. For example:

 % key -n 5 30 zz99999
 Reminder - Do not use this program while logged in via telnet or rlogin.
 Enter secret password: <secret password>
 26: SODA RUDE LEA LIND BUDD SILT
 27: JILT SPY DUTY GLOW COWL ROT
 28: THEM OW COLA RUNT BONG SCOT
 29: COT MASH BARR BRIM NAN FLAG
 30: CAN KNEE CAST NAME FOLK BILK

   Or for OPIE:

 % opiekey -n 5 30 zz99999
 Using the MD5 algorithm to compute response.
 Reminder: Don't use opiekey from telnet or dial-in sessions.
 Enter secret pass phrase: <secret password>
 26: JOAN BORE FOSS DES NAY QUIT
 27: LATE BIAS SLAY FOLK MUCH TRIG
 28: SALT TIN ANTI LOON NEAL USE
 29: RIO ODIN GO BYE FURY TIC
 30: GREW JIVE SAN GIRD BOIL PHI

   The -n 5 requests five keys in sequence, the 30 specifies what the
   last iteration number should be. Note that these are printed out
   in reverse order of eventual use. If you are really paranoid, you
   might want to write the results down by hand; otherwise you can
   cut-and-paste into lpr. Note that each line shows both the
   iteration count and the one-time password; you may still find it
   handy to scratch off passwords as you use them.

     --------------------------------------------------------------

  14.5.5. Restricting Use of UNIX(R) Passwords

   S/Key can place restrictions on the use of UNIX passwords based on
   the host name, user name, terminal port, or IP address of a login
   session. These restrictions can be found in the configuration file
   /etc/skey.access. The skey.access(5) manual page has more
   information on the complete format of the file and also details
   some security cautions to be aware of before depending on this
   file for security.

   If there is no /etc/skey.access file (this is the default on
   FreeBSD 4.X systems), then all users will be allowed to use UNIX
   passwords. If the file exists, however, then all users will be
   required to use S/Key unless explicitly permitted to do otherwise
   by configuration statements in the skey.access file. In all cases,
   UNIX passwords are permitted on the console.

   Here is a sample skey.access configuration file which illustrates
   the three most common sorts of configuration statements:

 permit internet 192.168.0.0 255.255.0.0
 permit user fnord
 permit port ttyd0

   The first line (permit internet) allows users whose IP source
   address (which is vulnerable to spoofing) matches the specified
   value and mask, to use UNIX passwords. This should not be
   considered a security mechanism, but rather, a means to remind
   authorized users that they are using an insecure network and need
   to use S/Key for authentication.

   The second line (permit user) allows the specified username, in
   this case fnord, to use UNIX passwords at any time. Generally
   speaking, this should only be used for people who are either
   unable to use the key program, like those with dumb terminals, or
   those who are ineducable.

   The third line (permit port) allows all users logging in on the
   specified terminal line to use UNIX passwords; this would be used
   for dial-ups.

   OPIE can restrict the use of UNIX passwords based on the IP
   address of a login session just like S/Key does. The relevant file
   is /etc/opieaccess, which is present by default on FreeBSD 5.0 and
   newer systems. Please check opieaccess(5) for more information on
   this file and which security considerations you should be aware of
   when using it.

   Here is a sample opieaccess file:

 permit 192.168.0.0 255.255.0.0

   This line allows users whose IP source address (which is
   vulnerable to spoofing) matches the specified value and mask, to
   use UNIX passwords at any time.

   If no rules in opieaccess are matched, the default is to deny
   non-OPIE logins.

     --------------------------------------------------------------

14.6. TCP Wrappers

   Written by: Tom Rhodes.

   "CO 1/4o inetd(8) -a-oCURH'XYENG^3-L-.|AAYEN^1L TCP Wrappers
   ^3oO-aF|e!A|y<<U:CURO:CURH-`aS:^1YENthAA,NYEN||b-oo,oAo^1OCURW-a-o|nYENI|bth!C
   CURj|h 1/4AE-a-oCURH^3-L-.|,E" 3/4CURoAd-"O<<OAA@-oo,o!AAo:uM!A"
   3/4CURoAd-YENI^3~<<D+-` 1/4s-ax!A|y"A<<D,U-`a!C
   "O|p!GYYEN'-oa|^P:C,CUR@NOTqCURaa|ru^1^3s 1/2u"O.
   1/2-aIuYENCURS:Ath-a-o!C|O TCP
   ^3nAAe<<oYENiYENHDEGu"`i^3oAI!AAU|^3"a:YENLS:o|h"AE+-!!C|bYENHCURUNOTq,"CUR-o!AS:UI+-NA:~A:oCURP:^2D-
   TCP Wrappers
   '-L-"N-a-oYEN\-`a!AYENHCURICUR@"C,^1e>>U^1BYENI-a-o"OCURl!C

   TCP Wrappers YENiYENHAAy inetd (c)O-oTH^2z-a-o"CO server daemon
   !A^3-L-.||b TCP Wrappers -a-o'x'CURCURS:CURU!C^3z^1L TCP Wrappers
   ^3o-oO/CURe|!YENiYENHCURa:'(c)^3s 1/2uNOTo:?y(logging)
   !B|^P:C,CUR@NOTqCURaa|ru^1^3s 1/2u"O. 1/2-aI!BYENiYENHAAy daemon
   YENu+-u"u:CUR-o^3!^3s 1/2uuYENuYEN!C
   Ao:uM"a:CURCUR^3!YEN-:YEN\-`aYENI"
   3/4CURoAd-CUR]YENiYENHDEGu"`i!A|y TCP Wrappers CUR-L-YENuNOTO
   1/4WYEN[CURFCUR@ 1/4h<<OAA@!AAU'-L-"NCURF"
   3/4CURoAd-(c)O?`iCUR-L-"`i-a-o"AE+-!!C

   uM|O!A YENN TCP Wrappers
   (c)O'-L-"N-a-o^3o"C,ABYEN~|wYENthYEN\-`a!A
   CUR-L-A^3,Ouo/NOTDEGAu"q" 3/4CURoAd--a-o'AYENNCURe(R)
   *!CA^3,Ou^2|X TCP Wrappers CURI"
   3/4CURoAd-!B"a:YENLYEN[+-j|wYENth+-^1NOTI"OCUR@"O:^1BYENICUR~^1i!A^3o
   1/4ECUR~YENiYENHNOTDEG"t^2I'-L-"N|h 1/4h|wYENth" 3/4AA@!C

   YENN(c)o^3o"C,^3](c)wNOTOYENDnDEGw^1i inetd
   (c)O'-L-"N-a-o!A(c)OYENHS:UI<<O/A:^3+-zYENyDEGN 3/4\ inetd ^3](c)w
   CUR@,`!C

     -a`: Ao:uM inetd(8)
     (c)O+-ODEGE-a-ou{|!"A<<DYENth^3!^3-L-NOTO-uYEN?-a-o
     !ydaemons!z!A|yCUR@-e"OA?!AS:UI^3-L-AUNOTO.|-oU(c)INOTDEG!ydaemons!z!A
     CURU+-S:UICUR'+-N"IYENI^3o|r^2'"O-ai^1F!C

     --------------------------------------------------------------

  14.6.1. Initial Configuration

   Yn|b FreeBSD CURCUR"IYENI TCP Wrappers -a-o,U:!AYENun 1/2T(c)w
   inetd |b+-ODEGE(R)E!A|^3|b /etc/rc.conf YEN[CURW -Ww -a-oDEGN
   1/4AES:YYENi!A^3oO^3](c)w|b"t^2I^1w^3]'N|^3CURF!C .iuMAU>>Yn
   3/4A.i *S:i /etc/hosts.allow ^3](c)wAE!A|y syslogd(8)
   CUR'.||b"t^2I log AECUR-o!ANOTo:?yNOTUAo:,e(R)AECURU"O!C

     -a`: FreeBSD -a-o TCP Wrappers
     ^1eS:@CURe|!>>P"a:YENLS:@.~"t^2ICURW-a-o TCP Wrappers
     CUR-L-CUROCUR@ 1/4E!AYENO/<<e FreeBSD CURw,g 1/4o+-oCUR-L-YENI
     /etc/hosts.deny !A|OCUR@<<ssS:iYENI /etc/hosts.allow!C

   ^3IA^2^3ae-a-o^3](c)wCURe|!NOTO!A"CO^1i daemon -a-o^3s
   1/2u^3-L-YENN /etc/hosts.allow "O"M(c)wNOTOS:_CUR^1^3\(c)I(c)Uu'!C
   The default configuration in FreeBSD is to allow a connection to
   every daemon started with inetd. Changing this will be discussed
   only after the basic configuration is covered.

   Basic configuration usually takes the form of daemon : address :
   action. Where daemon is the daemon name which inetd started. The
   address can be a valid hostname, an IP address or an IPv6 address
   enclosed in brackets ([ ]). The action field can be either allow
   or deny to grant or deny access appropriately. Keep in mind that
   configuration works off a first rule match semantic, meaning that
   the configuration file is scanned in ascending order for a
   matching rule. When a match is found the rule is applied and the
   search process will halt.

   Several other options exist but they will be explained in a later
   section. A simple configuration line may easily be constructed
   from that information alone. For example, to allow POP3
   connections via the mail/qpopper daemon, the following lines
   should be appended to hosts.allow:

 # This line is required for POP3 connections:
 qpopper : ALL : allow

   YEN[CURWCURW+-^3o|aeCURS:<<a!AYEN^2P:.<<.s+-ODEGE
   inetd!C<<.s+-ODEGE-a-oCURe|!YENiYENHYENI kill(1)
   <<u:YENO!A(c)IYEN'!y /etc/rc.d/inetd restart !z "OS:^1|"!C

     --------------------------------------------------------------

  14.6.2. Advanced Configuration

   TCP Wrappers has advanced options too; they will allow for more
   control over the way connections are handled. In some cases it may
   be a good idea to return a comment to certain hosts or daemon
   connections. In other cases, perhaps a log file should be recorded
   or an email sent to the administrator. Other situations may
   require the use of a service for local connections only. This is
   all possible through the use of configuration options known as
   wildcards, expansion characters and external command execution.
   The next two sections are written to cover these situations.

     --------------------------------------------------------------

    14.6.2.1. External Commands

   Suppose that a situation occurs where a connection should be
   denied yet a reason should be sent to the individual who attempted
   to establish that connection. How could it be done? That action
   can be made possible by using the twist option. When a connection
   attempt is made, twist will be called to execute a shell command
   or script. An example already exists in the hosts.allow file:

 # The rest of the daemons are protected.
 ALL : ALL \
         : severity auth.info \
         : twist /bin/echo "You are not welcome to use %d from %h."

   This example shows that the message, !S:You are not allowed to use
   daemon from hostname.!" will be returned for any daemon not
   previously configured in the access file. This is extremely useful
   for sending a reply back to the connection initiator right after
   the established connection is dropped. Note that any message
   returned must be wrapped in quote " characters; there are no
   exceptions to this rule.

     A:uS:iIt may be possible to launch a denial of service attack on
     the server if an attacker, or group of attackers could flood
     these daemons with connection requests.

   Another possibility is to use the spawn option in these cases.
   Like twist, the spawn implicitly denies the connection and may be
   used to run external shell commands or scripts. Unlike twist,
   spawn will not send a reply back to the individual who established
   the connection. For an example, consider the following
   configuration line:

 # We do not allow connections from example.com:
 ALL : .example.com \
         : spawn (/bin/echo %a from %h attempted to access %d >> \
           /var/log/connections.log) \
         : deny

   This will deny all connection attempts from the *.example.com
   domain; simultaneously logging the hostname, IP address and the
   daemon which they attempted to access in the
   /var/log/connections.log file.

   Aside from the already explained substitution characters above,
   e.g. %a, a few others exist. See the hosts_access(5) manual page
   for the complete list.

     --------------------------------------------------------------

    14.6.2.2. Wildcard Options

   Thus far the ALL example has been used continuously throughout the
   examples. Other options exist which could extend the functionality
   a bit further. For instance, ALL may be used to match every
   instance of either a daemon, domain or an IP address. Another
   wildcard available is PARANOID which may be used to match any host
   which provides an IP address that may be forged. In other words,
   paranoid may be used to define an action to be taken whenever a
   connection is made from an IP address that differs from its
   hostname. The following example may shed some more light on this
   discussion:

 # Block possibly spoofed requests to sendmail:
 sendmail : PARANOID : deny

   In that example all connection requests to sendmail which have an
   IP address that varies from its hostname will be denied.

     -a`.NUsing the PARANOID may severely cripple servers if the
     client or server has a broken DNS setup. Administrator
     discretion is advised.

   To learn more about wildcards and their associated functionality,
   see the hosts_access(5) manual page.

   Before any of the specific configuration lines above will work,
   the first configuration line should be commented out in
   hosts.allow. This was noted at the beginning of this section.

     --------------------------------------------------------------

14.7. KerberosIV

   Contributed by Mark Murray. Based on a contribution by Mark Dapoz.

   Kerberos is a network add-on system/protocol that allows users to
   authenticate themselves through the services of a secure server.
   Services such as remote login, remote copy, secure inter-system
   file copying and other high-risk tasks are made considerably safer
   and more controllable.

   The following instructions can be used as a guide on how to set up
   Kerberos as distributed for FreeBSD. However, you should refer to
   the relevant manual pages for a complete description.

     --------------------------------------------------------------

  14.7.1. Installing KerberosIV

   Kerberos is an optional component of FreeBSD. The easiest way to
   install this software is by selecting the krb4 or krb5
   distribution in sysinstall during the initial installation of
   FreeBSD. This will install the !S:eBones!" (KerberosIV) or
   !S:Heimdal!" (Kerberos5) implementation of Kerberos. These
   implementations are included because they are developed outside
   the USA/Canada and were thus available to system owners outside
   those countries during the era of restrictive export controls on
   cryptographic code from the USA.

   Alternatively, the MIT implementation of Kerberos is available
   from the Ports Collection as security/krb5.

     --------------------------------------------------------------

  14.7.2. Creating the Initial Database

   This is done on the Kerberos server only. First make sure that you
   do not have any old Kerberos databases around. You should change
   to the directory /etc/kerberosIV and check that only the following
   files are present:

 # cd /etc/kerberosIV
 # ls
 README          krb.conf        krb.realms

   If any additional files (such as principal.* or master_key) exist,
   then use the kdb_destroy command to destroy the old Kerberos
   database, or if Kerberos is not running, simply delete the extra
   files.

   You should now edit the krb.conf and krb.realms files to define
   your Kerberos realm. In this case the realm will be EXAMPLE.COM
   and the server is grunt.example.com. We edit or create the
   krb.conf file:

 # cat krb.conf
 EXAMPLE.COM
 EXAMPLE.COM grunt.example.com admin server
 CS.BERKELEY.EDU okeeffe.berkeley.edu
 ATHENA.MIT.EDU kerberos.mit.edu
 ATHENA.MIT.EDU kerberos-1.mit.edu
 ATHENA.MIT.EDU kerberos-2.mit.edu
 ATHENA.MIT.EDU kerberos-3.mit.edu
 LCS.MIT.EDU kerberos.lcs.mit.edu
 TELECOM.MIT.EDU bitsy.mit.edu
 ARC.NASA.GOV trident.arc.nasa.gov

   In this case, the other realms do not need to be there. They are
   here as an example of how a machine may be made aware of multiple
   realms. You may wish to not include them for simplicity.

   The first line names the realm in which this system works. The
   other lines contain realm/host entries. The first item on a line
   is a realm, and the second is a host in that realm that is acting
   as a !S:key distribution center!". The words admin server
   following a host's name means that host also provides an
   administrative database server. For further explanation of these
   terms, please consult the Kerberos manual pages.

   Now we have to add grunt.example.com to the EXAMPLE.COM realm and
   also add an entry to put all hosts in the .example.com domain in
   the EXAMPLE.COM realm. The krb.realms file would be updated as
   follows:

 # cat krb.realms
 grunt.example.com EXAMPLE.COM
 .example.com EXAMPLE.COM
 .berkeley.edu CS.BERKELEY.EDU
 .MIT.EDU ATHENA.MIT.EDU
 .mit.edu ATHENA.MIT.EDU

   Again, the other realms do not need to be there. They are here as
   an example of how a machine may be made aware of multiple realms.
   You may wish to remove them to simplify things.

   The first line puts the specific system into the named realm. The
   rest of the lines show how to default systems of a particular
   subdomain to a named realm.

   Now we are ready to create the database. This only needs to run on
   the Kerberos server (or Key Distribution Center). Issue the
   kdb_init command to do this:

 # kdb_init
 Realm name [default  ATHENA.MIT.EDU ]: EXAMPLE.COM
 You will be prompted for the database Master Password.
 It is important that you NOT FORGET this password.

 Enter Kerberos master key:

   Now we have to save the key so that servers on the local machine
   can pick it up. Use the kstash command to do this:

 # kstash

 Enter Kerberos master key:

 Current Kerberos master key version is 1.

 Master key entered. BEWARE!

   This saves the encrypted master password in
   /etc/kerberosIV/master_key.

     --------------------------------------------------------------

  14.7.3. Making It All Run

   Two principals need to be added to the database for each system
   that will be secured with Kerberos. Their names are kpasswd and
   rcmd. These two principals are made for each system, with the
   instance being the name of the individual system.

   These daemons, kpasswd and rcmd allow other systems to change
   Kerberos passwords and run commands like rcp(1), rlogin(1) and
   rsh(1).

   Now let us add these entries:

 # kdb_edit
 Opening database...

 Enter Kerberos master key:

 Current Kerberos master key version is 1.

 Master key entered.  BEWARE!
 Previous or default values are in [brackets] ,
 enter return to leave the same, or new value.

 Principal name: passwd
 Instance: grunt

 <Not found>, Create [y] ? y

 Principal: passwd, Instance: grunt, kdc_key_ver: 1
 New Password:                    <---- enter RANDOM here
 Verifying password

 New Password: <---- enter RANDOM here

 Random password [y] ? y

 Principal's new key version = 1
 Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?
 Max ticket lifetime (*5 minutes) [ 255 ] ?
 Attributes [ 0 ] ?
 Edit O.K.
 Principal name: rcmd
 Instance: grunt

 <Not found>, Create [y] ?

 Principal: rcmd, Instance: grunt, kdc_key_ver: 1
 New Password:           <---- enter RANDOM here
 Verifying password

 New Password:           <---- enter RANDOM here

 Random password [y] ?

 Principal's new key version = 1
 Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?
 Max ticket lifetime (*5 minutes) [ 255 ] ?
 Attributes [ 0 ] ?
 Edit O.K.
 Principal name:         <---- null entry here will cause an exit

     --------------------------------------------------------------

  14.7.4. Creating the Server File

   We now have to extract all the instances which define the services
   on each machine. For this we use the ext_srvtab command. This will
   create a file which must be copied or moved by secure means to
   each Kerberos client's /etc/kerberosIV directory. This file must
   be present on each server and client, and is crucial to the
   operation of Kerberos.

 # ext_srvtab grunt
 Enter Kerberos master key:

 Current Kerberos master key version is 1.

 Master key entered. BEWARE!
 Generating 'grunt-new-srvtab'....

   Now, this command only generates a temporary file which must be
   renamed to srvtab so that all the servers can pick it up. Use the
   mv(1) command to move it into place on the original system:

 # mv grunt-new-srvtab srvtab

   If the file is for a client system, and the network is not deemed
   safe, then copy the client-new-srvtab to removable media and
   transport it by secure physical means. Be sure to rename it to
   srvtab in the client's /etc/kerberosIV directory, and make sure it
   is mode 600:

 # mv grumble-new-srvtab srvtab
 # chmod 600 srvtab

     --------------------------------------------------------------

  14.7.5. Populating the Database

   We now have to add some user entries into the database. First let
   us create an entry for the user jane. Use the kdb_edit command to
   do this:

 # kdb_edit
 Opening database...

 Enter Kerberos master key:

 Current Kerberos master key version is 1.

 Master key entered.  BEWARE!
 Previous or default values are in [brackets] ,
 enter return to leave the same, or new value.

 Principal name: jane
 Instance:

 <Not found>, Create [y] ? y

 Principal: jane, Instance: , kdc_key_ver: 1
 New Password:                <---- enter a secure password here
 Verifying password

 New Password:                <---- re-enter the password here
 Principal's new key version = 1
 Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?
 Max ticket lifetime (*5 minutes) [ 255 ] ?
 Attributes [ 0 ] ?
 Edit O.K.
 Principal name:            <---- null entry here will cause an exit

     --------------------------------------------------------------

  14.7.6. Testing It All Out

   First we have to start the Kerberos daemons. Note that if you have
   correctly edited your /etc/rc.conf then this will happen
   automatically when you reboot. This is only necessary on the
   Kerberos server. Kerberos clients will automatically get what they
   need from the /etc/kerberosIV directory.

 # kerberos &
 Kerberos server starting
 Sleep forever on error
 Log file is /var/log/kerberos.log
 Current Kerberos master key version is 1.

 Master key entered. BEWARE!

 Current Kerberos master key version is 1
 Local realm: EXAMPLE.COM
 # kadmind -n &
 KADM Server KADM0.0A initializing
 Please do not use 'kill -9' to kill this job, use a
 regular kill instead

 Current Kerberos master key version is 1.

 Master key entered.  BEWARE!

   Now we can try using the kinit command to get a ticket for the ID
   jane that we created above:

 % kinit jane
 MIT Project Athena (grunt.example.com)
 Kerberos Initialization for "jane"
 Password:

   Try listing the tokens using klist to see if we really have them:

 % klist
 Ticket file:    /tmp/tkt245
 Principal:      jane@EXAMPLE.COM

   Issued           Expires          Principal
 Apr 30 11:23:22  Apr 30 19:23:22  krbtgt.EXAMPLE.COM@EXAMPLE.COM

   Now try changing the password using passwd(1) to check if the
   kpasswd daemon can get authorization to the Kerberos database:

 % passwd
 realm EXAMPLE.COM
 Old password for jane:
 New Password for jane:
 Verifying password
 New Password for jane:
 Password changed.

     --------------------------------------------------------------

  14.7.7. Adding su Privileges

   Kerberos allows us to give each user who needs root privileges
   their own separate su(1) password. We could now add an ID which is
   authorized to su(1) to root. This is controlled by having an
   instance of root associated with a principal. Using kdb_edit we
   can create the entry jane.root in the Kerberos database:

 # kdb_edit
 Opening database...

 Enter Kerberos master key:

 Current Kerberos master key version is 1.

 Master key entered.  BEWARE!
 Previous or default values are in [brackets] ,
 enter return to leave the same, or new value.

 Principal name: jane
 Instance: root

 <Not found>, Create [y] ? y

 Principal: jane, Instance: root, kdc_key_ver: 1
 New Password:                    <---- enter a SECURE password here
 Verifying password

 New Password:                    <---- re-enter the password here

 Principal's new key version = 1
 Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?
 Max ticket lifetime (*5 minutes) [ 255 ] ? 12 <--- Keep this short!
 Attributes [ 0 ] ?
 Edit O.K.
 Principal name:                  <---- null entry here will cause an exit

   Now try getting tokens for it to make sure it works:

 # kinit jane.root
 MIT Project Athena (grunt.example.com)
 Kerberos Initialization for "jane.root"
 Password:

   Now we need to add the user to root's .klogin file:

 # cat /root/.klogin
 jane.root@EXAMPLE.COM

   Now try doing the su(1):

 % su
 Password:

   and take a look at what tokens we have:

 # klist
 Ticket file:    /tmp/tkt_root_245
 Principal:      jane.root@EXAMPLE.COM

   Issued           Expires          Principal
 May  2 20:43:12  May  3 04:43:12  krbtgt.EXAMPLE.COM@EXAMPLE.COM

     --------------------------------------------------------------

  14.7.8. Using Other Commands

   In an earlier example, we created a principal called jane with an
   instance root. This was based on a user with the same name as the
   principal, and this is a Kerberos default; that a
   <principal>.<instance> of the form <username>.root will allow that
   <username> to su(1) to root if the necessary entries are in the
   .klogin file in root's home directory:

 # cat /root/.klogin
 jane.root@EXAMPLE.COM

   Likewise, if a user has in their own home directory lines of the
   form:

 % cat ~/.klogin
 jane@EXAMPLE.COM
 jack@EXAMPLE.COM

   This allows anyone in the EXAMPLE.COM realm who has authenticated
   themselves as jane or jack (via kinit, see above) to access to
   jane's account or files on this system (grunt) via rlogin(1),
   rsh(1) or rcp(1).

   For example, jane now logs into another system using Kerberos:

 % kinit
 MIT Project Athena (grunt.example.com)
 Password:
 % rlogin grunt
 Last login: Mon May  1 21:14:47 from grumble
 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
         The Regents of the University of California.   All rights reserved.

 FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995

   Or jack logs into jane's account on the same machine (jane having
   set up the .klogin file as above, and the person in charge of
   Kerberos having set up principal jack with a null instance):

 % kinit
 % rlogin grunt -l jane
 MIT Project Athena (grunt.example.com)
 Password:
 Last login: Mon May  1 21:16:55 from grumble
 Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
         The Regents of the University of California.   All rights reserved.
 FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995

     --------------------------------------------------------------

14.8. Kerberos5

   Contributed by Tillman Hodgson. Based on a contribution by Mark
   Murray.

   Every FreeBSD release beyond FreeBSD-5.1 includes support only for
   Kerberos5. Hence Kerberos5 is the only version included, and its
   configuration is similar in many aspects to that of KerberosIV.
   The following information only applies to Kerberos5 in post
   FreeBSD-5.0 releases. Users who wish to use the KerberosIV package
   may install the security/krb4 port.

   Kerberos is a network add-on system/protocol that allows users to
   authenticate themselves through the services of a secure server.
   Services such as remote login, remote copy, secure inter-system
   file copying and other high-risk tasks are made considerably safer
   and more controllable.

   Kerberos can be described as an identity-verifying proxy system.
   It can also be described as a trusted third-party authentication
   system. Kerberos provides only one function !X!X the secure
   authentication of users on the network. It does not provide
   authorization functions (what users are allowed to do) or auditing
   functions (what those users did). After a client and server have
   used Kerberos to prove their identity, they can also encrypt all
   of their communications to assure privacy and data integrity as
   they go about their business.

   Therefore it is highly recommended that Kerberos be used with
   other security methods which provide authorization and audit
   services.

   The following instructions can be used as a guide on how to set up
   Kerberos as distributed for FreeBSD. However, you should refer to
   the relevant manual pages for a complete description.

   For purposes of demonstrating a Kerberos installation, the various
   name spaces will be handled as follows:

     * The DNS domain (!S:zone!") will be example.org.

     * The Kerberos realm will be EXAMPLE.ORG.

     -a`: Please use real domain names when setting up Kerberos even
     if you intend to run it internally. This avoids DNS problems and
     assures inter-operation with other Kerberos realms.

     --------------------------------------------------------------

  14.8.1. History

   Kerberos was created by MIT as a solution to network security
   problems. The Kerberos protocol uses strong cryptography so that a
   client can prove its identity to a server (and vice versa) across
   an insecure network connection.

   Kerberos is both the name of a network authentication protocol and
   an adjective to describe programs that implement the program
   (Kerberos telnet, for example). The current version of the
   protocol is version 5, described in RFC 1510.

   Several free implementations of this protocol are available,
   covering a wide range of operating systems. The Massachusetts
   Institute of Technology (MIT), where Kerberos was originally
   developed, continues to develop their Kerberos package. It is
   commonly used in the US as a cryptography product, as such it has
   historically been affected by US export regulations. The MIT
   Kerberos is available as a port (security/krb5). Heimdal Kerberos
   is another version 5 implementation, and was explicitly developed
   outside of the US to avoid export regulations (and is thus often
   included in non-commercial UNIX variants). The Heimdal Kerberos
   distribution is available as a port (security/heimdal), and a
   minimal installation of it is included in the base FreeBSD
   install.

   In order to reach the widest audience, these instructions assume
   the use of the Heimdal distribution included in FreeBSD.

     --------------------------------------------------------------

  14.8.2. Setting up a Heimdal KDC

   The Key Distribution Center (KDC) is the centralized
   authentication service that Kerberos provides !X!X it is the
   computer that issues Kerberos tickets. The KDC is considered
   !S:trusted!" by all other computers in the Kerberos realm, and
   thus has heightened security concerns.

   Note that while running the Kerberos server requires very few
   computing resources, a dedicated machine acting only as a KDC is
   recommended for security reasons.

   To begin setting up a KDC, ensure that your /etc/rc.conf file
   contains the correct settings to act as a KDC (you may need to
   adjust paths to reflect your own system):

 kerberos5_server_enable="YES"
 kadmind5_server_enable="YES"
 kerberos_stash="YES"

     -a`: The kerberos_stash is only available in FreeBSD 4.X.

   Next we will set up your Kerberos config file, /etc/krb5.conf:

 [libdefaults]
     default_realm = EXAMPLE.ORG
 [realms]
     EXAMPLE.ORG = {
         kdc = kerberos.example.org
         admin_server = kerberos.example.org
     }
 [domain_realm]
     .example.org = EXAMPLE.ORG

   Note that this /etc/krb5.conf file implies that your KDC will have
   the fully-qualified hostname of kerberos.example.org. You will
   need to add a CNAME (alias) entry to your zone file to accomplish
   this if your KDC has a different hostname.

     -a`: For large networks with a properly configured BIND DNS
     server, the above example could be trimmed to:

 [libdefaults]
       default_realm = EXAMPLE.ORG

     With the following lines being appended to the example.org
     zonefile:

 _kerberos._udp      IN  SRV     01 00 88 kerberos.example.org.
 _kerberos._tcp      IN  SRV     01 00 88 kerberos.example.org.
 _kpasswd._udp       IN  SRV     01 00 464 kerberos.example.org.
 _kerberos-adm._tcp  IN  SRV     01 00 749 kerberos.example.org.
 _kerberos           IN  TXT     EXAMPLE.ORG

     -a`: For clients to be able to find the Kerberos services, you
     must have either a fully configured /etc/krb5.conf or a
     miminally configured /etc/krb5.conf and a properly configured
     DNS server.

   Next we will create the Kerberos database. This database contains
   the keys of all principals encrypted with a master password. You
   are not required to remember this password, it will be stored in a
   file (/var/heimdal/m-key). To create the master key, run kstash
   and enter a password.

   Once the master key has been created, you can initialize the
   database using the kadmin program with the -l option (standing for
   !S:local!"). This option instructs kadmin to modify the database
   files directly rather than going through the kadmind network
   service. This handles the chicken-and-egg problem of trying to
   connect to the database before it is created. Once you have the
   kadmin prompt, use the init command to create your realms initial
   database.

   Lastly, while still in kadmin, create your first principal using
   the add command. Stick to the defaults options for the principal
   for now, you can always change them later with the modify command.
   Note that you can use the ? command at any prompt to see the
   available options.

   A sample database creation session is shown below:

 # kstash
 Master key: xxxxxxxx
 Verifying password - Master key: xxxxxxxx

 # kadmin -l
 kadmin> init EXAMPLE.ORG
 Realm max ticket life [unlimited]:
 kadmin> add tillman
 Max ticket life [unlimited]:
 Max renewable life [unlimited]:
 Attributes []:
 Password: xxxxxxxx
 Verifying password - Password: xxxxxxxx

   Now it is time to start up the KDC services. Run
   /etc/rc.d/kerberos start and /etc/rc.d/kadmind start to bring up
   the services. Note that you will not have any kerberized daemons
   running at this point but you should be able to confirm the that
   the KDC is functioning by obtaining and listing a ticket for the
   principal (user) that you just created from the command-line of
   the KDC itself:

 % k5init tillman
 tillman@EXAMPLE.ORG's Password:

 % k5list
 Credentials cache: FILE:/tmp/krb5cc_500
         Principal: tillman@EXAMPLE.ORG

   Issued           Expires          Principal
 Aug 27 15:37:58  Aug 28 01:37:58  krbtgt/EXAMPLE.ORG@EXAMPLE.ORG

     --------------------------------------------------------------

  14.8.3. Kerberos enabling a server with Heimdal services

   First, we need a copy of the Kerberos configuration file,
   /etc/krb5.conf. To do so, simply copy it over to the client
   computer from the KDC in a secure fashion (using network
   utilities, such as scp(1), or physically via a floppy disk).

   Next you need a /etc/krb5.keytab file. This is the major
   difference between a server providing Kerberos enabled daemons and
   a workstation !X!X the server must have a keytab file. This file
   contains the servers host key, which allows it and the KDC to
   verify each others identity. It must be transmitted to the server
   in a secure fashion, as the security of the server can be broken
   if the key is made public. This explicitly means that transferring
   it via a clear text channel, such as FTP, is a very bad idea.

   Typically, you transfer to the keytab to the server using the
   kadmin program. This is handy because you also need to create the
   host principal (the KDC end of the krb5.keytab) using kadmin.

   Note that you must have already obtained a ticket and that this
   ticket must be allowed to use the kadmin interface in the
   kadmind.acl. See the section titled !S:Remote administration!" in
   the Heimdal info pages (info heimdal) for details on designing
   access control lists. If you do not want to enable remote kadmin
   access, you can simply securely connect to the KDC (via local
   console, ssh(1) or Kerberos telnet(1)) and perform administration
   locally using kadmin -l.

   After installing the /etc/krb5.conf file, you can use kadmin from
   the Kerberos server. The add --random-key command will let you add
   the servers host principal, and the ext command will allow you to
   extract the servers host principal to its own keytab. For example:

 # kadmin
 kadmin> add --random-key host/myserver.example.org
 Max ticket life [unlimited]:
 Max renewable life [unlimited]:
 Attributes []:
 kadmin> ext host/myserver.example.org
 kadmin> exit

   Note that the ext command (short for !S:extract!") stores the
   extracted key in /etc/krb5.keytab by default.

   If you do not have kadmind running on the KDC (possibly for
   security reasons) and thus do not have access to kadmin remotely,
   you can add the host principal (host/myserver.EXAMPLE.ORG)
   directly on the KDC and then extract it to a temporary file (to
   avoid over-writing the /etc/krb5.keytab on the KDC) using
   something like this:

 # kadmin
 kadmin> ext --keytab=/tmp/example.keytab host/myserver.example.org
 kadmin> exit

   You can then securely copy the keytab to the server computer
   (using scp or a floppy, for example). Be sure to specify a
   non-default keytab name to avoid over-writing the keytab on the
   KDC.

   At this point your server can communicate with the KDC (due to its
   krb5.conf file) and it can prove its own identity (due to the
   krb5.keytab file). It is now ready for you to enable some Kerberos
   services. For this example we will enable the telnet service by
   putting a line like this into your /etc/inetd.conf and then
   restarting the inetd(8) service with /etc/rc.d/inetd restart:

 telnet    stream  tcp     nowait  root    /usr/libexec/telnetd  telnetd -a user

   The critical bit is that the -a (for authentication) type is set
   to user. Consult the telnetd(8) manual page for more details.

     --------------------------------------------------------------

  14.8.4. Kerberos enabling a client with Heimdal

   Setting up a client computer is almost trivially easy. As far as
   Kerberos configuration goes, you only need the Kerberos
   configuration file, located at /etc/krb5.conf. Simply securely
   copy it over to the client computer from the KDC.

   Test your client computer by attempting to use kinit, klist, and
   kdestroy from the client to obtain, show, and then delete a ticket
   for the principal you created above. You should also be able to
   use Kerberos applications to connect to Kerberos enabled servers,
   though if that does not work and obtaining a ticket does the
   problem is likely with the server and not with the client or the
   KDC.

   When testing an application like telnet, try using a packet
   sniffer (such as tcpdump(1)) to confirm that your password is not
   sent in the clear. Try using telnet with the -x option, which
   encrypts the entire data stream (similar to ssh).

   The core Kerberos client applications (traditionally named kinit,
   klist, kdestroy, and kpasswd) are installed in the base FreeBSD
   install. Note that FreeBSD versions prior to 5.0 renamed them to
   k5init, k5list, k5destroy, k5passwd, and k5stash (though it is
   typically only used once).

   Various non-core Kerberos client applications are also installed
   by default. This is where the !S:minimal!" nature of the base
   Heimdal installation is felt: telnet is the only Kerberos enabled
   service.

   The Heimdal port adds some of the missing client applications:
   Kerberos enabled versions of ftp, rsh, rcp, rlogin, and a few
   other less common programs. The MIT port also contains a full
   suite of Kerberos client applications.

     --------------------------------------------------------------

  14.8.5. User configuration files: .k5login and .k5users

   Users within a realm typically have their Kerberos principal (such
   as tillman@EXAMPLE.ORG) mapped to a local user account (such as a
   local account named tillman). Client applications such as telnet
   usually do not require a user name or a principal.

   Occasionally, however, you want to grant access to a local user
   account to someone who does not have a matching Kerberos
   principal. For example, tillman@EXAMPLE.ORG may need access to the
   local user account webdevelopers. Other principals may also need
   access to that local account.

   The .k5login and .k5users files, placed in a users home directory,
   can be used similar to a powerful combination of .hosts and
   .rhosts, solving this problem. For example, if a .k5login with the
   following contents:

 tillman@example.org
 jdoe@example.org

   Were to be placed into the home directory of the local user
   webdevelopers then both principals listed would have access to
   that account without requiring a shared password.

   Reading the manual pages for these commands is recommended. Note
   that the ksu manual page covers .k5users.

     --------------------------------------------------------------

  14.8.6. Kerberos Tips, Tricks, and Troubleshooting

     * When using either the Heimdal or MIT Kerberos ports ensure
       that your PATH environment variable lists the Kerberos
       versions of the client applications before the system
       versions.

     * Do all the computers in your realm have synchronized time
       settings? If not, authentication may fail. uU 27.11 ,`
       describes how to synchronize clocks using NTP.

     * MIT and Heimdal inter-operate nicely. Except for kadmin, the
       protocol for which is not standardized.

     * If you change your hostname, you also need to change your
       host/ principal and update your keytab. This also applies to
       special keytab entries like the www/ principal used for
       Apache's www/mod_auth_kerb.

     * All hosts in your realm must be resolvable (both forwards and
       reverse) in DNS (or /etc/hosts as a minimum). CNAMEs will
       work, but the A and PTR records must be correct and in place.
       The error message is not very intuitive: !S:Kerberos5 refuses
       authentication because Read req failed: Key table entry not
       found!".

     * Some operating systems that may being acting as clients to
       your KDC do not set the permissions for ksu to be setuid root.
       This means that ksu does not work, which is a good security
       idea but annoying. This is not a KDC error.

     * With MIT Kerberos, if you want to allow a principal to have a
       ticket life longer than the default ten hours, you must use
       modify_principal in kadmin to change the maxlife of both the
       principal in question and the krbtgt principal. Then the
       principal can use the -l option with kinit to request a ticket
       with a longer lifetime.

     *   -a`: If you run a packet sniffer on your KDC to add in
         troubleshooting and then run kinit from a workstation, you
         will notice that your TGT is sent immediately upon running
         kinit !X!X even before you type your password! The
         explanation is that the Kerberos server freely transmits a
         TGT (Ticket Granting Ticket) to any unauthorized request;
         however, every TGT is encrypted in a key derived from the
         user's password. Therefore, when a user types their password
         it is not being sent to the KDC, it is being used to decrypt
         the TGT that kinit already obtained. If the decryption
         process results in a valid ticket with a valid time stamp,
         the user has valid Kerberos credentials. These credentials
         include a session key for establishing secure communications
         with the Kerberos server in the future, as well as the
         actual ticket-granting ticket, which is actually encrypted
         with the Kerberos server's own key. This second layer of
         encryption is unknown to the user, but it is what allows the
         Kerberos server to verify the authenticity of each TGT.

     * If you want to use long ticket lifetimes (a week, for example)
       and you are using OpenSSH to connect to the machine where your
       ticket is stored, make sure that Kerberos TicketCleanup is set
       to no in your sshd_config or else your tickets will be deleted
       when you log out.

     * Remember that host principals can have a longer ticket
       lifetime as well. If your user principal has a lifetime of a
       week but the host you are connecting to has a lifetime of nine
       hours, you will have an expired host principal in your cache
       and the ticket cache will not work as expected.

     * When setting up a krb5.dict file to prevent specific bad
       passwords from being used (the manual page for kadmind covers
       this briefly), remember that it only applies to principals
       that have a password policy assigned to them. The krb5.dict
       files format is simple: one string per line. Creating a
       symbolic link to /usr/share/dict/words might be useful.

     --------------------------------------------------------------

  14.8.7. Differences with the MIT port

   The major difference between the MIT and Heimdal installs relates
   to the kadmin program which has a different (but equivalent) set
   of commands and uses a different protocol. This has a large
   implications if your KDC is MIT as you will not be able to use the
   Heimdal kadmin program to administer your KDC remotely (or vice
   versa, for that matter).

   The client applications may also take slightly different command
   line options to accomplish the same tasks. Following the
   instructions on the MIT Kerberos web site
   (http://web.mit.edu/Kerberos/www/) is recommended. Be careful of
   path issues: the MIT port installs into /usr/local/ by default,
   and the !S:normal!" system applications may be run instead of MIT
   if your PATH environment variable lists the system directories
   first.

     -a`: With the MIT security/krb5 port that is provided by
     FreeBSD, be sure to read the
     /usr/local/share/doc/krb5/README.FreeBSD file installed by the
     port if you want to understand why logins via telnetd and
     klogind behave somewhat oddly. Most importantly, correcting the
     !S:incorrect permissions on cache file!" behavior requires that
     the login.krb5 binary be used for authentication so that it can
     properly change ownership for the forwarded credentials.

     --------------------------------------------------------------

  14.8.8. Mitigating limitations found in Kerberos

     --------------------------------------------------------------

    14.8.8.1. Kerberos is an all-or-nothing approach

   Every service enabled on the network must be modified to work with
   Kerberos (or be otherwise secured against network attacks) or else
   the users credentials could be stolen and re-used. An example of
   this would be Kerberos enabling all remote shells (via rsh and
   telnet, for example) but not converting the POP3 mail server which
   sends passwords in plain text.

     --------------------------------------------------------------

    14.8.8.2. Kerberos is intended for single-user workstations

   In a multi-user environment, Kerberos is less secure. This is
   because it stores the tickets in the /tmp directory, which is
   readable by all users. If a user is sharing a computer with
   several other people simultaneously (i.e. multi-user), it is
   possible that the user's tickets can be stolen (copied) by another
   user.

   This can be overcome with the -c filename command-line option or
   (preferably) the KRB5CCNAME environment variable, but this is
   rarely done. In principal, storing the ticket in the users home
   directory and using simple file permissions can mitigate this
   problem.

     --------------------------------------------------------------

    14.8.8.3. The KDC is a single point of failure

   By design, the KDC must be as secure as the master password
   database is contained on it. The KDC should have absolutely no
   other services running on it and should be physically secured. The
   danger is high because Kerberos stores all passwords encrypted
   with the same key (the !S:master!" key), which in turn is stored
   as a file on the KDC.

   As a side note, a compromised master key is not quite as bad as
   one might normally fear. The master key is only used to encrypt
   the Kerberos database and as a seed for the random number
   generator. As long as access to your KDC is secure, an attacker
   cannot do much with the master key.

   Additionally, if the KDC is unavailable (perhaps due to a denial
   of service attack or network problems) the network services are
   unusable as authentication can not be performed, a recipe for a
   denial-of-service attack. This can alleviated with multiple KDCs
   (a single master and one or more slaves) and with careful
   implementation of secondary or fall-back authentication (PAM is
   excellent for this).

     --------------------------------------------------------------

    14.8.8.4. Kerberos Shortcomings

   Kerberos allows users, hosts and services to authenticate between
   themselves. It does not have a mechanism to authenticate the KDC
   to the users, hosts or services. This means that a trojanned kinit
   (for example) could record all user names and passwords. Something
   like security/tripwire or other file system integrity checking
   tools can alleviate this.

     --------------------------------------------------------------

  14.8.9. Resources and further information

     * The Kerberos FAQ

     * Designing an Authentication System: a Dialog in Four Scenes

     * RFC 1510, The Kerberos Network Authentication Service (V5)

     * MIT Kerberos home page

     * Heimdal Kerberos home page

     --------------------------------------------------------------

14.9. OpenSSL

   Written by: Tom Rhodes.

   One feature that many users overlook is the OpenSSL toolkit
   included in FreeBSD. OpenSSL provides an encryption transport
   layer on top of the normal communications layer; thus allowing it
   to be intertwined with many network applications and services.

   Some uses of OpenSSL may include encrypted authentication of mail
   clients, web based transactions such as credit card payments and
   more. Many ports such as www/apache13-ssl, and mail/sylpheed-claws
   will offer compilation support for building with OpenSSL.

     -a`: In most cases the Ports Collection will attempt to build
     the security/openssl port unless the WITH_OPENSSL_BASE make
     variable is explicitly set to !S:yes!".

   The version of OpenSSL included in FreeBSD supports Secure Sockets
   Layer v2/v3 (SSLv2/SSLv3), Transport Layer Security v1 (TLSv1)
   network security protocols and can be used as a general
   cryptographic library.

     -a`: While OpenSSL supports the IDEA algorithm, it is disabled
     by default due to United States patents. To use it, the license
     should be reviewed and, if the restrictions are acceptable, the
     MAKE_IDEA variable must be set in make.conf.

   One of the most common uses of OpenSSL is to provide certificates
   for use with software applications. These certificates ensure that
   the credentials of the company or individual are valid and not
   fraudulent. If the certificate in question has not been verified
   by one of the several !S:Certificate Authorities!", or CAs, a
   warning is usually produced. A Certificate Authority is a company,
   such as VeriSign, which will sign certificates in order to
   validate credentials of individuals or companies. This process has
   a cost associated with it and is definitely not a requirement for
   using certificates; however, it can put some of the more paranoid
   users at ease.

     --------------------------------------------------------------

  14.9.1. Generating Certificates

   To generate a certificate, the following command is available:

 # openssl req -new -nodes -out req.pem -keyout cert.pem
 Generating a 1024 bit RSA private key
 ................++++++
 .......................................++++++
 writing new private key to 'cert.pem'
 -----
 You are about to be asked to enter information that will be incorporated
 into your certificate request.
 What you are about to enter is what is called a Distinguished Name or a DN.
 There are quite a few fields but you can leave some blank
 For some fields there will be a default value,
 If you enter '.', the field will be left blank.
 -----
 Country Name (2 letter code) [AU]:US
 State or Province Name (full name) [Some-State]:PA
 Locality Name (eg, city) []:Pittsburgh
 Organization Name (eg, company) [Internet Widgits Pty Ltd]:My Company
 Organizational Unit Name (eg, section) []:Systems Administrator
 Common Name (eg, YOUR name) []:localhost.example.org
 Email Address []:trhodes@FreeBSD.org

 Please enter the following 'extra' attributes
 to be sent with your certificate request
 A challenge password []:SOME PASSWORD
 An optional company name []:Another Name

   Notice the response directly after the !S:Common Name!" prompt
   shows a domain name. This prompt requires a server name to be
   entered for verification purposes; placing anything but a domain
   name would yield a useless certificate. Other options, for
   instance expire time, alternate encryption algorithms, etc. are
   available. A complete list may be obtained by viewing the
   openssl(1) manual page.

   Two files should now exist in the directory in which the
   aforementioned command was issued. The certificate request,
   req.pem, may be sent to a certificate authority who will validate
   the credentials that you entered, sign the request and return the
   certificate to you. The second file created will be named cert.pem
   and is the private key for the certificate and should be protected
   at all costs; if this falls in the hands of others it can be used
   to impersonate you (or your server).

   In cases where a signature from a CA is not required, a self
   signed certificate can be created. First, generate the RSA key:

 # openssl dsaparam -rand -genkey -out myRSA.key 1024

   Next, generate the CA key:

 # openssl gendsa -des3 -out myca.key myRSA.key

   Use this key to create the certificate:

 # openssl req -new -x509 -days 365 -key myca.key -out new.crt

   Two new files should appear in the directory: a certificate
   authority signature file, myca.key and the certificate itself,
   new.crt. These should be placed in a directory, preferably under
   /etc, which is readable only by root. Permissions of 0700 should
   be fine for this and they can be set with the chmod utility.

     --------------------------------------------------------------

  14.9.2. Using Certificates, an Example

   So what can these files do? A good use would be to encrypt
   connections to the Sendmail MTA. This would dissolve the use of
   clear text authentication for users who send mail via the local
   MTA.

     -a`: This is not the best use in the world as some MUAs will
     present the user with an error if they have not installed the
     certificate locally. Refer to the documentation included with
     the software for more information on certificate installation.

   The following lines should be placed inside the local .mc file:

 dnl SSL Options
 define(`confCACERT_PATH',`/etc/certs')dnl
 define(`confCACERT',`/etc/certs/new.crt')dnl
 define(`confSERVER_CERT',`/etc/certs/new.crt')dnl
 define(`confSERVER_KEY',`/etc/certs/myca.key')dnl
 define(`confTLS_SRV_OPTIONS', `V')dnl

   Where /etc/certs/ is the directory to be used for storing the
   certificate and key files locally. The last few requirements are a
   rebuild of the local .cf file. This is easily achieved by typing
   make install within the /etc/mail directory. Follow that up with
   make restart which should start the Sendmail daemon.

   If all went well there will be no error messages in the
   /var/log/maillog file and Sendmail will show up in the process
   list.

   For a simple test, simply connect to the mail server using the
   telnet(1) utility:

 # telnet example.com 25
 Trying 192.0.34.166...
 Connected to example.com.
 Escape character is '^]'.
 220 example.com ESMTP Sendmail 8.12.10/8.12.10; Tue, 31 Aug 2004 03:41:22 -0400 (EDT)
 ehlo example.com
 250-example.com Hello example.com [192.0.34.166], pleased to meet you
 250-ENHANCEDSTATUSCODES
 250-PIPELINING
 250-8BITMIME
 250-SIZE
 250-DSN
 250-ETRN
 250-AUTH LOGIN PLAIN
 250-STARTTLS
 250-DELIVERBY
 250 HELP
 quit
 221 2.0.0 example.com closing connection
 Connection closed by foreign host.

   If the !S:STARTTLS!" line appears in the output then everything is
   working correctly.

     --------------------------------------------------------------

14.10. VPN over IPsec

   Written by Nik Clayton.

   Creating a VPN between two networks, separated by the Internet,
   using FreeBSD gateways.

     --------------------------------------------------------------

  14.10.1. Understanding IPsec

   Written by Hiten M. Pandya.

   This section will guide you through the process of setting up
   IPsec, and to use it in an environment which consists of FreeBSD
   and Microsoft Windows 2000/XP machines, to make them communicate
   securely. In order to set up IPsec, it is necessary that you are
   familiar with the concepts of building a custom kernel (see uU 8
   ^3^1).

   IPsec is a protocol which sits on top of the Internet Protocol
   (IP) layer. It allows two or more hosts to communicate in a secure
   manner (hence the name). The FreeBSD IPsec !S:network stack!" is
   based on the KAME implementation, which has support for both
   protocol families, IPv4 and IPv6.

     -a`: FreeBSD 5.X contains a !S:hardware accelerated!" IPsec
     stack, known as !S:Fast IPsec!", that was obtained from OpenBSD.
     It employs cryptographic hardware (whenever possible) via the
     crypto(4) subsystem to optimize the performance of IPsec. This
     subsystem is new, and does not support all the features that are
     available in the KAME version of IPsec. However, in order to
     enable hardware-accelerated IPsec, the following kernel option
     has to be added to your kernel configuration file:

 options   FAST_IPSEC  # new IPsec (cannot define w/ IPSEC)
        

     Note, that it is not currently possible to use the !S:Fast
     IPsec!" subsystem in lue with the KAME implementation of IPsec.
     Consult the fast_ipsec(4) manual page for more information.

   IPsec consists of two sub-protocols:

     * Encapsulated Security Payload (ESP), protects the IP packet
       data from third party interference, by encrypting the contents
       using symmetric cryptography algorithms (like Blowfish, 3DES).

     * Authentication Header (AH), protects the IP packet header from
       third party interference and spoofing, by computing a
       cryptographic checksum and hashing the IP packet header fields
       with a secure hashing function. This is then followed by an
       additional header that contains the hash, to allow the
       information in the packet to be authenticated.

   ESP and AH can either be used together or separately, depending on
   the environment.

   IPsec can either be used to directly encrypt the traffic between
   two hosts (known as Transport Mode); or to build !S:virtual
   tunnels!" between two subnets, which could be used for secure
   communication between two corporate networks (known as Tunnel
   Mode). The latter is more commonly known as a Virtual Private
   Network (VPN). The ipsec(4) manual page should be consulted for
   detailed information on the IPsec subsystem in FreeBSD.

   To add IPsec support to your kernel, add the following options to
   your kernel configuration file:

 options   IPSEC        #IP security
 options   IPSEC_ESP    #IP security (crypto; define w/ IPSEC)
      

   If IPsec debugging support is desired, the following kernel option
   should also be added:

 options   IPSEC_DEBUG  #debug for IP security
      

     --------------------------------------------------------------

  14.10.2. The Problem

   There is no standard for what constitutes a VPN. VPNs can be
   implemented using a number of different technologies, each of
   which have their own strengths and weaknesses. This section
   presents a scenario, and the strategies used for implementing a
   VPN for this scenario.

     --------------------------------------------------------------

  14.10.3. The Scenario: Two networks, connected to the Internet, to
  behave as one

   The premise is as follows:

     * You have at least two sites

     * Both sites are using IP internally

     * Both sites are connected to the Internet, through a gateway
       that is running FreeBSD.

     * The gateway on each network has at least one public IP
       address.

     * The internal addresses of the two networks can be public or
       private IP addresses, it does not matter. You can be running
       NAT on the gateway machine if necessary.

     * The internal IP addresses of the two networks do not collide.
       While I expect it is theoretically possible to use a
       combination of VPN technology and NAT to get this to work, I
       expect it to be a configuration nightmare.

   If you find that you are trying to connect two networks, both of
   which, internally, use the same private IP address range (e.g.
   both of them use 192.168.1.x), then one of the networks will have
   to be renumbered.

   The network topology might look something like this:

 Network #1            [ Internal Hosts ]    Private Net, 192.168.1.2-254
                       [   Win9x/NT/2K  ]
                       [      UNIX      ]
                                |
                                |
                         .---[fxp1]---.      Private IP, 192.168.1.1
                         |   FreeBSD  |
                         `---[fxp0]---'      Public IP, A.B.C.D
                                |
                                |
                       -=-=- Internet -=-=-
                                |
                                |
                         .---[fxp0]---.      Public IP, W.X.Y.Z
                         |   FreeBSD  |
                         `---[fxp1]---'      Private IP, 192.168.2.1
                                |
                                |
 Network #2            [ Internal Hosts ]
                       [   Win9x/NT/2K  ]    Private Net, 192.168.2.2-254
                       [      UNIX      ]

   Notice the two public IP addresses. I will use the letters to
   refer to them in the rest of this article. Anywhere you see those
   letters in this article, replace them with your own public IP
   addresses. Note also that internally, the two gateway machines
   have .1 IP addresses, and that the two networks have different
   private IP addresses (192.168.1.x and 192.168.2.x respectively).
   All the machines on the private networks have been configured to
   use the .1 machine as their default gateway.

   The intention is that, from a network point of view, each network
   should view the machines on the other network as though they were
   directly attached the same router -- albeit a slightly slow router
   with an occasional tendency to drop packets.

   This means that (for example), machine 192.168.1.20 should be able
   to run

 ping 192.168.2.34

   and have it work, transparently. Windows machines should be able
   to see the machines on the other network, browse file shares, and
   so on, in exactly the same way that they can browse machines on
   the local network.

   And the whole thing has to be secure. This means that traffic
   between the two networks has to be encrypted.

   Creating a VPN between these two networks is a multi-step process.
   The stages are as follows:

    1. Create a !S:virtual!" network link between the two networks,
       across the Internet. Test it, using tools like ping(8), to
       make sure it works.

    2. Apply security policies to ensure that traffic between the two
       networks is transparently encrypted and decrypted as
       necessary. Test this, using tools like tcpdump(1), to ensure
       that traffic is encrypted.

    3. Configure additional software on the FreeBSD gateways, to
       allow Windows machines to see one another across the VPN.

     --------------------------------------------------------------

    14.10.3.1. Step 1: Creating and testing a !S:virtual!" network link

   Suppose that you were logged in to the gateway machine on network
   #1 (with public IP address A.B.C.D, private IP address
   192.168.1.1), and you ran ping 192.168.2.1, which is the private
   address of the machine with IP address W.X.Y.Z. What needs to
   happen in order for this to work?

    1. The gateway machine needs to know how to reach 192.168.2.1. In
       other words, it needs to have a route to 192.168.2.1.

    2. Private IP addresses, such as those in the 192.168.x range are
       not supposed to appear on the Internet at large. Instead, each
       packet you send to 192.168.2.1 will need to be wrapped up
       inside another packet. This packet will need to appear to be
       from A.B.C.D, and it will have to be sent to W.X.Y.Z. This
       process is called encapsulation.

    3. Once this packet arrives at W.X.Y.Z it will need to
       !S:unencapsulated!", and delivered to 192.168.2.1.

   You can think of this as requiring a !S:tunnel!" between the two
   networks. The two !S:tunnel mouths!" are the IP addresses A.B.C.D
   and W.X.Y.Z, and the tunnel must be told the addresses of the
   private IP addresses that will be allowed to pass through it. The
   tunnel is used to transfer traffic with private IP addresses
   across the public Internet.

   This tunnel is created by using the generic interface, or gif
   devices on FreeBSD. As you can imagine, the gif interface on each
   gateway host must be configured with four IP addresses; two for
   the public IP addresses, and two for the private IP addresses.

   Support for the gif device must be compiled in to the FreeBSD
   kernel on both machines. You can do this by adding the line:

 device gif

   to the kernel configuration files on both machines, and then
   compile, install, and reboot as normal.

   Configuring the tunnel is a two step process. First the tunnel
   must be told what the outside (or public) IP addresses are, using
   gifconfig(8). Then the private IP addresses must be configured
   using ifconfig(8).

     -a`: In FreeBSD 5.X, the functionality provided by the
     gifconfig(8) utility has been merged into ifconfig(8).

   On the gateway machine on network #1 you would run the following
   two commands to configure the tunnel.

 gifconfig gif0 A.B.C.D W.X.Y.Z
 ifconfig gif0 inet 192.168.1.1 192.168.2.1 netmask 0xffffffff
      

   On the other gateway machine you run the same commands, but with
   the order of the IP addresses reversed.

 gifconfig gif0 W.X.Y.Z A.B.C.D
 ifconfig gif0 inet 192.168.2.1 192.168.1.1 netmask 0xffffffff
      

   You can then run:

 gifconfig gif0

   to see the configuration. For example, on the network #1 gateway,
   you would see this:

 # gifconfig gif0
 gif0: flags=8011<UP,POINTTOPOINT,MULTICAST> mtu 1280
 inet 192.168.1.1 --> 192.168.2.1 netmask 0xffffffff
 physical address inet A.B.C.D --> W.X.Y.Z
      

   As you can see, a tunnel has been created between the physical
   addresses A.B.C.D and W.X.Y.Z, and the traffic allowed through the
   tunnel is that between 192.168.1.1 and 192.168.2.1.

   This will also have added an entry to the routing table on both
   machines, which you can examine with the command netstat -rn. This
   output is from the gateway host on network #1.

 # netstat -rn
 Routing tables

 Internet:
 Destination      Gateway       Flags    Refs    Use    Netif  Expire
 ...
 192.168.2.1      192.168.1.1   UH        0        0    gif0
 ...
      

   As the !S:Flags!" value indicates, this is a host route, which
   means that each gateway knows how to reach the other gateway, but
   they do not know how to reach the rest of their respective
   networks. That problem will be fixed shortly.

   It is likely that you are running a firewall on both machines.
   This will need to be circumvented for your VPN traffic. You might
   want to allow all traffic between both networks, or you might want
   to include firewall rules that protect both ends of the VPN from
   one another.

   It greatly simplifies testing if you configure the firewall to
   allow all traffic through the VPN. You can always tighten things
   up later. If you are using ipfw(8) on the gateway machines then a
   command like

 ipfw add 1 allow ip from any to any via gif0

   will allow all traffic between the two end points of the VPN,
   without affecting your other firewall rules. Obviously you will
   need to run this command on both gateway hosts.

   This is sufficient to allow each gateway machine to ping the
   other. On 192.168.1.1, you should be able to run

 ping 192.168.2.1

   and get a response, and you should be able to do the same thing on
   the other gateway machine.

   However, you will not be able to reach internal machines on either
   network yet. This is because of the routing -- although the
   gateway machines know how to reach one another, they do not know
   how to reach the network behind each one.

   To solve this problem you must add a static route on each gateway
   machine. The command to do this on the first gateway would be:

 route add 192.168.2.0 192.168.2.1 netmask 0xffffff00
      

   This says !S:In order to reach the hosts on the network
   192.168.2.0, send the packets to the host 192.168.2.1!". You will
   need to run a similar command on the other gateway, but with the
   192.168.1.x addresses instead.

   IP traffic from hosts on one network will now be able to reach
   hosts on the other network.

   That has now created two thirds of a VPN between the two networks,
   in as much as it is !S:virtual!" and it is a !S:network!". It is
   not private yet. You can test this using ping(8) and tcpdump(1).
   Log in to the gateway host and run

 tcpdump dst host 192.168.2.1

   In another log in session on the same host run

 ping 192.168.2.1

   You will see output that looks something like this:

 16:10:24.018080 192.168.1.1 > 192.168.2.1: icmp: echo request
 16:10:24.018109 192.168.1.1 > 192.168.2.1: icmp: echo reply
 16:10:25.018814 192.168.1.1 > 192.168.2.1: icmp: echo request
 16:10:25.018847 192.168.1.1 > 192.168.2.1: icmp: echo reply
 16:10:26.028896 192.168.1.1 > 192.168.2.1: icmp: echo request
 16:10:26.029112 192.168.1.1 > 192.168.2.1: icmp: echo reply
      

   As you can see, the ICMP messages are going back and forth
   unencrypted. If you had used the -s parameter to tcpdump(1) to
   grab more bytes of data from the packets you would see more
   information.

   Obviously this is unacceptable. The next section will discuss
   securing the link between the two networks so that it all traffic
   is automatically encrypted.

   Summary:

     * Configure both kernels with !S:pseudo-device gif!".

     * Edit /etc/rc.conf on gateway host #1 and add the following
       lines (replacing IP addresses as necessary).

 gifconfig_gif0="A.B.C.D W.X.Y.Z"
 ifconfig_gif0="inet 192.168.1.1 192.168.2.1 netmask 0xffffffff"
 static_routes="vpn"
 route_vpn="192.168.2.0 192.168.2.1 netmask 0xffffff00"
          

     * Edit your firewall script (/etc/rc.firewall, or similar) on
       both hosts, and add

 ipfw add 1 allow ip from any to any via gif0

     * Make similar changes to /etc/rc.conf on gateway host #2,
       reversing the order of IP addresses.

     --------------------------------------------------------------

    14.10.3.2. Step 2: Securing the link

   To secure the link we will be using IPsec. IPsec provides a
   mechanism for two hosts to agree on an encryption key, and to then
   use this key in order to encrypt data between the two hosts.

   The are two areas of configuration to be considered here.

    1. There must be a mechanism for two hosts to agree on the
       encryption mechanism to use. Once two hosts have agreed on
       this mechanism there is said to be a !S:security association!"
       between them.

    2. There must be a mechanism for specifying which traffic should
       be encrypted. Obviously, you do not want to encrypt all your
       outgoing traffic -- you only want to encrypt the traffic that
       is part of the VPN. The rules that you put in place to
       determine what traffic will be encrypted are called
       !S:security policies!".

   Security associations and security policies are both maintained by
   the kernel, and can be modified by userland programs. However,
   before you can do this you must configure the kernel to support
   IPsec and the Encapsulated Security Payload (ESP) protocol. This
   is done by configuring a kernel with:

 options IPSEC
 options IPSEC_ESP
       

   and recompiling, reinstalling, and rebooting. As before you will
   need to do this to the kernels on both of the gateway hosts.

   You have two choices when it comes to setting up security
   associations. You can configure them by hand between two hosts,
   which entails choosing the encryption algorithm, encryption keys,
   and so forth, or you can use daemons that implement the Internet
   Key Exchange protocol (IKE) to do this for you.

   I recommend the latter. Apart from anything else, it is easier to
   set up.

   Editing and displaying security policies is carried out using
   setkey(8). By analogy, setkey is to the kernel's security policy
   tables as route(8) is to the kernel's routing tables. setkey can
   also display the current security associations, and to continue
   the analogy further, is akin to netstat -r in that respect.

   There are a number of choices for daemons to manage security
   associations with FreeBSD. This article will describe how to use
   one of these, racoon !X!X which is available from
   security/ipsec-tools in the FreeBSD Ports collection.

   The racoon software must be run on both gateway hosts. On each
   host it is configured with the IP address of the other end of the
   VPN, and a secret key (which you choose, and must be the same on
   both gateways).

   The two daemons then contact one another, confirm that they are
   who they say they are (by using the secret key that you
   configured). The daemons then generate a new secret key, and use
   this to encrypt the traffic over the VPN. They periodically change
   this secret, so that even if an attacker were to crack one of the
   keys (which is as theoretically close to unfeasible as it gets) it
   will not do them much good -- by the time they have cracked the
   key the two daemons have chosen another one.

   The configuration file for racoon is stored in
   ${PREFIX}/etc/racoon. You should find a configuration file there,
   which should not need to be changed too much. The other component
   of racoon's configuration, which you will need to change, is the
   !S:pre-shared key!".

   The default racoon configuration expects to find this in the file
   ${PREFIX}/etc/racoon/psk.txt. It is important to note that the
   pre-shared key is not the key that will be used to encrypt your
   traffic across the VPN link, it is simply a token that allows the
   key management daemons to trust one another.

   psk.txt contains a line for each remote site you are dealing with.
   In this example, where there are two sites, each psk.txt file will
   contain one line (because each end of the VPN is only dealing with
   one other end).

   On gateway host #1 this line should look like this:

 W.X.Y.Z            secret

   That is, the public IP address of the remote end, whitespace, and
   a text string that provides the secret. Obviously, you should not
   use !S:secret!" as your key -- the normal rules for choosing a
   password apply.

   On gateway host #2 the line would look like this

 A.B.C.D            secret

   That is, the public IP address of the remote end, and the same
   secret key. psk.txt must be mode 0600 (i.e., only read/write to
   root) before racoon will run.

   You must run racoon on both gateway machines. You will also need
   to add some firewall rules to allow the IKE traffic, which is
   carried over UDP to the ISAKMP (Internet Security Association Key
   Management Protocol) port. Again, this should be fairly early in
   your firewall ruleset.

 ipfw add 1 allow udp from A.B.C.D to W.X.Y.Z isakmp
 ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp
       

   Once racoon is running you can try pinging one gateway host from
   the other. The connection is still not encrypted, but racoon will
   then set up the security associations between the two hosts --
   this might take a moment, and you may see this as a short delay
   before the ping commands start responding.

   Once the security association has been set up you can view it
   using setkey(8). Run

 setkey -D

   on either host to view the security association information.

   That's one half of the problem. They other half is setting your
   security policies.

   To create a sensible security policy, let's review what's been set
   up so far. This discussions hold for both ends of the link.

   Each IP packet that you send out has a header that contains data
   about the packet. The header includes the IP addresses of both the
   source and destination. As we already know, private IP addresses,
   such as the 192.168.x.y range are not supposed to appear on the
   public Internet. Instead, they must first be encapsulated inside
   another packet. This packet must have the public source and
   destination IP addresses substituted for the private addresses.

   So if your outgoing packet started looking like this:

   .----------------------.
   | Src: 192.168.1.1     |
   | Dst: 192.168.2.1     |
   | <other header info>  |
   +----------------------+
   | <packet data>        |
   `----------------------'

   Then it will be encapsulated inside another packet, looking
   something like this:

   .--------------------------.
   | Src: A.B.C.D             |
   | Dst: W.X.Y.Z             |
   | <other header info>      |
   +--------------------------+
   | .----------------------. |
   | | Src: 192.168.1.1     | |
   | | Dst: 192.168.2.1     | |
   | | <other header info>  | |
   | +----------------------+ |
   | | <packet data>        | |
   | `----------------------' |
   `--------------------------'

   This encapsulation is carried out by the gif device. As you can
   see, the packet now has real IP addresses on the outside, and our
   original packet has been wrapped up as data inside the packet that
   will be put out on the Internet.

   Obviously, we want all traffic between the VPNs to be encrypted.
   You might try putting this in to words, as:

   !S:If a packet leaves from A.B.C.D, and it is destined for
   W.X.Y.Z, then encrypt it, using the necessary security
   associations.!"

   !S:If a packet arrives from W.X.Y.Z, and it is destined for
   A.B.C.D, then decrypt it, using the necessary security
   associations.!"

   That's close, but not quite right. If you did this, all traffic to
   and from W.X.Y.Z, even traffic that was not part of the VPN, would
   be encrypted. That's not quite what you want. The correct policy
   is as follows

   !S:If a packet leaves from A.B.C.D, and that packet is
   encapsulating another packet, and it is destined for W.X.Y.Z, then
   encrypt it, using the necessary security associations.!"

   !S:If a packet arrives from W.X.Y.Z, and that packet is
   encapsulating another packet, and it is destined for A.B.C.D, then
   decrypt it, using the necessary security associations.!"

   A subtle change, but a necessary one.

   Security policies are also set using setkey(8). setkey(8) features
   a configuration language for defining the policy. You can either
   enter configuration instructions via stdin, or you can use the -f
   option to specify a filename that contains configuration
   instructions.

   The configuration on gateway host #1 (which has the public IP
   address A.B.C.D) to force all outbound traffic to W.X.Y.Z to be
   encrypted is:

 spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/require;
       

   Put these commands in a file (e.g. /etc/ipsec.conf) and then run

 # setkey -f /etc/ipsec.conf

   spdadd tells setkey(8) that we want to add a rule to the secure
   policy database. The rest of this line specifies which packets
   will match this policy. A.B.C.D/32 and W.X.Y.Z/32 are the IP
   addresses and netmasks that identify the network or hosts that
   this policy will apply to. In this case, we want it to apply to
   traffic between these two hosts. ipencap tells the kernel that
   this policy should only apply to packets that encapsulate other
   packets. -P out says that this policy applies to outgoing packets,
   and ipsec says that the packet will be secured.

   The second line specifies how this packet will be encrypted. esp
   is the protocol that will be used, while tunnel indicates that the
   packet will be further encapsulated in an IPsec packet. The
   repeated use of A.B.C.D and W.X.Y.Z is used to select the security
   association to use, and the final require mandates that packets
   must be encrypted if they match this rule.

   This rule only matches outgoing packets. You will need a similar
   rule to match incoming packets.

 spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P in ipsec esp/tunnel/W.X.Y.Z-A.B.C.D/require;

   Note the in instead of out in this case, and the necessary
   reversal of the IP addresses.

   The other gateway host (which has the public IP address W.X.Y.Z)
   will need similar rules.

 spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P out ipsec esp/tunnel/W.X.Y.Z-A.B.C.D/require;
 spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P in ipsec esp/tunnel/A.B.C.D-W.X.Y.Z/require;

   Finally, you need to add firewall rules to allow ESP and IPENCAP
   packets back and forth. These rules will need to be added to both
   hosts.

 ipfw add 1 allow esp from A.B.C.D to W.X.Y.Z
 ipfw add 1 allow esp from W.X.Y.Z to A.B.C.D
 ipfw add 1 allow ipencap from A.B.C.D to W.X.Y.Z
 ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
       

   Because the rules are symmetric you can use the same rules on each
   gateway host.

   Outgoing packets will now look something like this:

   .------------------------------.  --------------------------.
   | Src: A.B.C.D                 |                            |
   | Dst: W.X.Y.Z                 |                            |
   | <other header info>          |                            |  Encrypted
   +------------------------------+                            |  packet.
   | .--------------------------. |  -------------.            |  contents
   | | Src: A.B.C.D             | |               |            |  are
   | | Dst: W.X.Y.Z             | |               |            |  completely
   | | <other header info>      | |               |            |- secure
   | +--------------------------+ |               |  Encap'd   |  from third
   | | .----------------------. | |  -.           |  packet    |  party
   | | | Src: 192.168.1.1     | | |   |  Original |- with real |  snooping
   | | | Dst: 192.168.2.1     | | |   |  packet,  |  IP addr   |
   | | | <other header info>  | | |   |- private  |            |
   | | +----------------------+ | |   |  IP addr  |            |
   | | | <packet data>        | | |   |           |            |
   | | `----------------------' | |  -'           |            |
   | `--------------------------' |  -------------'            |
   `------------------------------'  --------------------------'
            

   When they are received by the far end of the VPN they will first
   be decrypted (using the security associations that have been
   negotiated by racoon). Then they will enter the gif interface,
   which will unwrap the second layer, until you are left with the
   innermost packet, which can then travel in to the inner network.

   You can check the security using the same ping(8) test from
   earlier. First, log in to the A.B.C.D gateway machine, and run:

 tcpdump dst host 192.168.2.1

   In another log in session on the same host run

 ping 192.168.2.1

   This time you should see output like the following:

 XXX tcpdump output

   Now, as you can see, tcpdump(1) shows the ESP packets. If you try
   to examine them with the -s option you will see (apparently)
   gibberish, because of the encryption.

   Congratulations. You have just set up a VPN between two remote
   sites.

   Summary

     * Configure both kernels with:

 options IPSEC
 options IPSEC_ESP
          

     * Install security/ipsec-tools. Edit
       ${PREFIX}/etc/racoon/psk.txt on both gateway hosts, adding an
       entry for the remote host's IP address and a secret key that
       they both know. Make sure this file is mode 0600.

     * Add the following lines to /etc/rc.conf on each host:

 ipsec_enable="YES"
 ipsec_file="/etc/ipsec.conf"
          

     * Create an /etc/ipsec.conf on each host that contains the
       necessary spdadd lines. On gateway host #1 this would be:

 spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P out ipsec
   esp/tunnel/A.B.C.D-W.X.Y.Z/require;
 spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P in ipsec
   esp/tunnel/W.X.Y.Z-A.B.C.D/require;

       On gateway host #2 this would be:

 spdadd W.X.Y.Z/32 A.B.C.D/32 ipencap -P out ipsec
   esp/tunnel/W.X.Y.Z-A.B.C.D/require;
 spdadd A.B.C.D/32 W.X.Y.Z/32 ipencap -P in ipsec
   esp/tunnel/A.B.C.D-W.X.Y.Z/require;

     * Add firewall rules to allow IKE, ESP, and IPENCAP traffic to
       both hosts:

 ipfw add 1 allow udp from A.B.C.D to W.X.Y.Z isakmp
 ipfw add 1 allow udp from W.X.Y.Z to A.B.C.D isakmp
 ipfw add 1 allow esp from A.B.C.D to W.X.Y.Z
 ipfw add 1 allow esp from W.X.Y.Z to A.B.C.D
 ipfw add 1 allow ipencap from A.B.C.D to W.X.Y.Z
 ipfw add 1 allow ipencap from W.X.Y.Z to A.B.C.D
          

   The previous two steps should suffice to get the VPN up and
   running. Machines on each network will be able to refer to one
   another using IP addresses, and all traffic across the link will
   be automatically and securely encrypted.

     --------------------------------------------------------------

14.11. OpenSSH

   Contributed by Chern Lee.

   OpenSSH is a set of network connectivity tools used to access
   remote machines securely. It can be used as a direct replacement
   for rlogin, rsh, rcp, and telnet. Additionally, TCP/IP connections
   can be tunneled/forwarded securely through SSH. OpenSSH encrypts
   all traffic to effectively eliminate eavesdropping, connection
   hijacking, and other network-level attacks.

   OpenSSH is maintained by the OpenBSD project, and is based upon
   SSH v1.2.12 with all the recent bug fixes and updates. It is
   compatible with both SSH protocols 1 and 2. OpenSSH has been in
   the base system since FreeBSD 4.0.

     --------------------------------------------------------------

  14.11.1. Advantages of Using OpenSSH

   Normally, when using telnet(1) or rlogin(1), data is sent over the
   network in an clear, un-encrypted form. Network sniffers anywhere
   in between the client and server can steal your user/password
   information or data transferred in your session. OpenSSH offers a
   variety of authentication and encryption methods to prevent this
   from happening.

     --------------------------------------------------------------

  14.11.2. Enabling sshd

   The sshd daemon is enabled by default on FreeBSD 4.X. In FreeBSD
   5.X and later enabling sshd is an option presented during a
   Standard install of FreeBSD. To see if sshd is enabled, check the
   rc.conf file for:

 sshd_enable="YES"

   This will load sshd(8), the daemon program for OpenSSH, the next
   time your system initializes. Alternatively, you can simply run
   directly the sshd daemon by typing sshd on the command line.

     --------------------------------------------------------------

  14.11.3. SSH Client

   The ssh(1) utility works similarly to rlogin(1).

 # ssh user@example.com
 Host key not found from the list of known hosts.
 Are you sure you want to continue connecting (yes/no)? yes
 Host 'example.com' added to the list of known hosts.
 user@example.com's password: *******

   The login will continue just as it would have if a session was
   created using rlogin or telnet. SSH utilizes a key fingerprint
   system for verifying the authenticity of the server when the
   client connects. The user is prompted to enter yes only when
   connecting for the first time. Future attempts to login are all
   verified against the saved fingerprint key. The SSH client will
   alert you if the saved fingerprint differs from the received
   fingerprint on future login attempts. The fingerprints are saved
   in ~/.ssh/known_hosts, or ~/.ssh/known_hosts2 for SSH v2
   fingerprints.

   By default, recent versions of the OpenSSH servers only accept SSH
   v2 connections. The client will use version 2 if possible and will
   fall back to version 1. The client can also be forced to use one
   or the other by passing it the -1 or -2 for version 1 or version
   2, respectively. The version 1 compatability is maintained in the
   client for backwards compatability with older versions.

     --------------------------------------------------------------

  14.11.4. Secure Copy

   The scp(1) command works similarly to rcp(1); it copies a file to
   or from a remote machine, except in a secure fashion.

 #  scp user@example.com:/COPYRIGHT COPYRIGHT
 user@example.com's password: *******
 COPYRIGHT            100% |*****************************|  4735
 00:00
 #

   Since the fingerprint was already saved for this host in the
   previous example, it is verified when using scp(1) here.

   The arguments passed to scp(1) are similar to cp(1), with the file
   or files in the first argument, and the destination in the second.
   Since the file is fetched over the network, through SSH, one or
   more of the file arguments takes on the form
   user@host:<path_to_remote_file>.

     --------------------------------------------------------------

  14.11.5. Configuration

   The system-wide configuration files for both the OpenSSH daemon
   and client reside within the /etc/ssh directory.

   ssh_config configures the client settings, while sshd_config
   configures the daemon.

   Additionally, the sshd_program (/usr/sbin/sshd by default), and
   sshd_flags rc.conf options can provide more levels of
   configuration.

     --------------------------------------------------------------

  14.11.6. ssh-keygen

   Instead of using passwords, ssh-keygen(1) can be used to generate
   DSA or RSA keys to authenticate a user:

 % ssh-keygen -t dsa
 Generating public/private dsa key pair.
 Enter file in which to save the key (/home/user/.ssh/id_dsa):
 Created directory '/home/user/.ssh'.
 Enter passphrase (empty for no passphrase):
 Enter same passphrase again:
 Your identification has been saved in /home/user/.ssh/id_dsa.
 Your public key has been saved in /home/user/.ssh/id_dsa.pub.
 The key fingerprint is:
 bb:48:db:f2:93:57:80:b6:aa:bc:f5:d5:ba:8f:79:17 user@host.example.com

   ssh-keygen(1) will create a public and private key pair for use in
   authentication. The private key is stored in ~/.ssh/id_dsa or
   ~/.ssh/id_rsa, whereas the public key is stored in
   ~/.ssh/id_dsa.pub or ~/.ssh/id_rsa.pub, respectively for DSA and
   RSA key types. The public key must be placed in
   ~/.ssh/authorized_keys of the remote machine in order for the
   setup to work. Similarly, RSA version 1 public keys should be
   placed in ~/.ssh/authorized_keys.

   This will allow connection to the remote machine based upon SSH
   keys instead of passwords.

   If a passphrase is used in ssh-keygen(1), the user will be
   prompted for a password each time in order to use the private key.
   ssh-agent(1) can alleviate the strain of repeatedly entering long
   passphrases, and is explored in the uU 14.11.7 ,` section below.

     A:uS:iThe various options and files can be different according
     to the OpenSSH version you have on your system; to avoid
     problems you should consult the ssh-keygen(1) manual page.

     --------------------------------------------------------------

  14.11.7. ssh-agent and ssh-add

   The ssh-agent(1) and ssh-add(1) utilities provide methods for SSH
   keys to be loaded into memory for use, without needing to type the
   passphrase each time.

   The ssh-agent(1) utility will handle the authentication using the
   private key(s) that are loaded into it. ssh-agent(1) should be
   used to launch another application. At the most basic level, it
   could spawn a shell or at a more advanced level, a window manager.

   To use ssh-agent(1) in a shell, first it will need to be spawned
   with a shell as an argument. Secondly, the identity needs to be
   added by running ssh-add(1) and providing it the passphrase for
   the private key. Once these steps have been completed the user
   will be able to ssh(1) to any host that has the corresponding
   public key installed. For example:

 % ssh-agent csh
 % ssh-add
 Enter passphrase for /home/user/.ssh/id_dsa:
 Identity added: /home/user/.ssh/id_dsa (/home/user/.ssh/id_dsa)
 %

   To use ssh-agent(1) in X11, a call to ssh-agent(1) will need to be
   placed in ~/.xinitrc. This will provide the ssh-agent(1) services
   to all programs launched in X11. An example ~/.xinitrc file might
   look like this:

 exec ssh-agent startxfce4

   This would launch ssh-agent(1), which would in turn launch XFCE,
   every time X11 starts. Then once that is done and X11 has been
   restarted so that the changes can take effect, simply run
   ssh-add(1) to load all of your SSH keys.

     --------------------------------------------------------------

  14.11.8. SSH Tunneling

   OpenSSH has the ability to create a tunnel to encapsulate another
   protocol in an encrypted session.

   The following command tells ssh(1) to create a tunnel for telnet:

 % ssh -2 -N -f -L 5023:localhost:23 user@foo.example.com
 %

   The ssh command is used with the following options:

   -2

           Forces ssh to use version 2 of the protocol. (Do not use
           if you are working with older SSH servers)

   -N

           Indicates no command, or tunnel only. If omitted, ssh
           would initiate a normal session.

   -f

           Forces ssh to run in the background.

   -L

           Indicates a local tunnel in
           localport:remotehost:remoteport fashion.

   user@foo.example.com

           The remote SSH server.

   An SSH tunnel works by creating a listen socket on localhost on
   the specified port. It then forwards any connection received on
   the local host/port via the SSH connection to the specified remote
   host and port.

   In the example, port 5023 on localhost is being forwarded to port
   23 on localhost of the remote machine. Since 23 is telnet, this
   would create a secure telnet session through an SSH tunnel.

   This can be used to wrap any number of insecure TCP protocols such
   as SMTP, POP3, FTP, etc.

   1/2d"O 14-1. Using SSH to Create a Secure Tunnel for SMTP

 % ssh -2 -N -f -L 5025:localhost:25 user@mailserver.example.com
 user@mailserver.example.com's password: *****
 % telnet localhost 5025
 Trying 127.0.0.1...
 Connected to localhost.
 Escape character is '^]'.
 220 mailserver.example.com ESMTP

   This can be used in conjunction with an ssh-keygen(1) and
   additional user accounts to create a more seamless/hassle-free SSH
   tunneling environment. Keys can be used in place of typing a
   password, and the tunnels can be run as a separate user.

     --------------------------------------------------------------

    14.11.8.1. Practical SSH Tunneling Examples

      14.11.8.1.1. Secure Access of a POP3 Server

   At work, there is an SSH server that accepts connections from the
   outside. On the same office network resides a mail server running
   a POP3 server. The network, or network path between your home and
   office may or may not be completely trustable. Because of this,
   you need to check your e-mail in a secure manner. The solution is
   to create an SSH connection to your office's SSH server, and
   tunnel through to the mail server.

 % ssh -2 -N -f -L 2110:mail.example.com:110 user@ssh-server.example.com
 user@ssh-server.example.com's password: ******

   When the tunnel is up and running, you can point your mail client
   to send POP3 requests to localhost port 2110. A connection here
   will be forwarded securely across the tunnel to mail.example.com.

     --------------------------------------------------------------

      14.11.8.1.2. Bypassing a Draconian Firewall

   Some network administrators impose extremely draconian firewall
   rules, filtering not only incoming connections, but outgoing
   connections. You may be only given access to contact remote
   machines on ports 22 and 80 for SSH and web surfing.

   You may wish to access another (perhaps non-work related) service,
   such as an Ogg Vorbis server to stream music. If this Ogg Vorbis
   server is streaming on some other port than 22 or 80, you will not
   be able to access it.

   The solution is to create an SSH connection to a machine outside
   of your network's firewall, and use it to tunnel to the Ogg Vorbis
   server.

 % ssh -2 -N -f -L 8888:music.example.com:8000 user@unfirewalled-system.example.org
 user@unfirewalled-system.example.org's password: *******

   Your streaming client can now be pointed to localhost port 8888,
   which will be forwarded over to music.example.com port 8000,
   successfully evading the firewall.

     --------------------------------------------------------------

  14.11.9. The AllowUsers Users Option

   It is often a good idea to limit which users can log in and from
   where. The AllowUsers option is a good way to accomplish this. For
   example, to only allow the root user to log in from 192.168.1.32,
   something like this would be appropriate in the
   /etc/ssh/sshd_config file:

 AllowUsers root@192.168.1.32

   To allow the user admin to log in from anywhere, just list the
   username by itself:

 AllowUsers admin

   Multiple users should be listed on the same line, like so:

 AllowUsers root@192.168.1.32 admin

     -a`: It is important that you list each user that needs to log
     in to this machine; otherwise they will be locked out.

   After making changes to /etc/ssh/sshd_config you must tell sshd(8)
   to reload its config files, by running:

 # /etc/rc.d/sshd reload

     --------------------------------------------------------------

  14.11.10. Further Reading

   OpenSSH

   ssh(1) scp(1) ssh-keygen(1) ssh-agent(1) ssh-add(1) ssh_config(5)

   sshd(8) sftp-server(8) sshd_config(5)

     --------------------------------------------------------------

14.12. File System Access Control Lists

   Contributed by Tom Rhodes.

   In conjunction with file system enhancements like snapshots,
   FreeBSD 5.0 and later offers the security of File System Access
   Control Lists (ACLs).

   Access Control Lists extend the standard UNIX permission model in
   a highly compatible (POSIX.1e) way. This feature permits an
   administrator to make use of and take advantage of a more
   sophisticated security model.

   To enable ACL support for UFS file systems, the following:

 options UFS_ACL

   must be compiled into the kernel. If this option has not been
   compiled in, a warning message will be displayed when attempting
   to mount a file system supporting ACLs. This option is included in
   the GENERIC kernel. ACLs rely on extended attributes being enabled
   on the file system. Extended attributes are natively supported in
   the next generation UNIX file system, UFS2.

     -a`: A higher level of administrative overhead is required to
     configure extended attributes on UFS1 than on UFS2. The
     performance of extended attributes on UFS2 is also substantially
     higher. As a result, UFS2 is generally recommended in preference
     to UFS1 for use with access control lists.

   ACLs are enabled by the mount-time administrative flag, acls,
   which may be added to /etc/fstab. The mount-time flag can also be
   automatically set in a persistent manner using tunefs(8) to modify
   a superblock ACLs flag in the file system header. In general, it
   is preferred to use the superblock flag for several reasons:

     * The mount-time ACLs flag cannot be changed by a remount
       (mount(8) -u), only by means of a complete umount(8) and fresh
       mount(8). This means that ACLs cannot be enabled on the root
       file system after boot. It also means that you cannot change
       the disposition of a file system once it is in use.

     * Setting the superblock flag will cause the file system to
       always be mounted with ACLs enabled even if there is not an
       fstab entry or if the devices re-order. This prevents
       accidental mounting of the file system without ACLs enabled,
       which can result in ACLs being improperly enforced, and hence
       security problems.

     -a`: We may change the ACLs behavior to allow the flag to be
     enabled without a complete fresh mount(8), but we consider it
     desirable to discourage accidental mounting without ACLs
     enabled, because you can shoot your feet quite nastily if you
     enable ACLs, then disable them, then re-enable them without
     flushing the extended attributes. In general, once you have
     enabled ACLs on a file system, they should not be disabled, as
     the resulting file protections may not be compatible with those
     intended by the users of the system, and re-enabling ACLs may
     re-attach the previous ACLs to files that have since had their
     permissions changed, resulting in other unpredictable behavior.

   File systems with ACLs enabled will show a + (plus) sign in their
   permission settings when viewed. For example:

 drwx------  2 robert  robert  512 Dec 27 11:54 private
 drwxrwx---+ 2 robert  robert  512 Dec 23 10:57 directory1
 drwxrwx---+ 2 robert  robert  512 Dec 22 10:20 directory2
 drwxrwx---+ 2 robert  robert  512 Dec 27 11:57 directory3
 drwxr-xr-x  2 robert  robert  512 Nov 10 11:54 public_html

   Here we see that the directory1, directory2, and directory3
   directories are all taking advantage of ACLs. The public_html
   directory is not.

     --------------------------------------------------------------

  14.12.1. Making Use of ACLs

   The file system ACLs can be viewed by the getfacl(1) utility. For
   instance, to view the ACL settings on the test file, one would use
   the command:

 % getfacl test
         #file:test
         #owner:1001
         #group:1001
         user::rw-
         group::r--
         other::r--

   To change the ACL settings on this file, invoke the setfacl(1)
   utility. Observe:

 % setfacl -k test

   The -k flag will remove all of the currently defined ACLs from a
   file or file system. The more preferable method would be to use -b
   as it leaves the basic fields required for ACLs to work.

 % setfacl -m u:trhodes:rwx,group:web:r--,o::--- test

   In the aforementioned command, the -m option was used to modify
   the default ACL entries. Since there were no pre-defined entries,
   as they were removed by the previous command, this will restore
   the default options and assign the options listed. Take care to
   notice that if you add a user or group which does not exist on the
   system, an !S:Invalid argument!" error will be printed to stdout.

     --------------------------------------------------------------

14.13. Monitoring Third Party Security Issues

   Contributed by Tom Rhodes.

   In recent years, the security world has made many improvements to
   how vulnerability assessment is handled. The threat of system
   intrusion increases as third party utilities are installed and
   configured for virtually any operating system available today.

   Vulnerability assessment is a key factor in security, and while
   FreeBSD releases advisories for the base system, doing so for
   every third party utility is beyond the FreeBSD Project's
   capability. There is a way to mitigate third party vulnerabilities
   and warn administrators of known security issues. A FreeBSD add on
   utility known as Portaudit exists solely for this purpose.

   The security/portaudit port polls a database, updated and
   maintained by the FreeBSD Security Team and ports developers, for
   known security issues.

   To begin using Portaudit, one must install it from the Ports
   Collection:

 # cd /usr/ports/security/portaudit && make install clean

   During the install process, the configuration files for
   periodic(8) will be updated, permitting Portaudit output in the
   daily security runs. Ensure the daily security run emails, which
   are sent to root's email account, are being read. No more
   configuration will be required here.

   After installation, an administrator can update the database and
   view known vulnerabilities in installed packages by invoking the
   following command:

 # portaudit -Fda

     -a`: The database will automatically be updated during the
     periodic(8) run; thus, the previous command is completely
     optional. It is only required for the following examples.

   To audit the third party utilities installed as part of the Ports
   Collection at anytime, an administrator need only run the
   following command:

 # portaudit -a

   Portaudit will produce something like this for vulnerable
   packages:

 Affected package: cups-base-1.1.22.0_1
 Type of problem: cups-base -- HPGL buffer overflow vulnerability.
 Reference: <http://www.FreeBSD.org/ports/portaudit/40a3bca2-6809-11d9-a9e7-0001020eed82.html>

 1 problem(s) in your installed packages found.

 You are advised to update or deinstall the affected package(s) immediately.

   By pointing a web browser to the URL shown, an administrator may
   obtain more information about the vulnerability in question. This
   will include versions affected, by FreeBSD Port version, along
   with other web sites which may contain security advisories.

   In short, Portaudit is a powerful utility and extremely useful
   when coupled with the Portupgrade port.

     --------------------------------------------------------------

14.14. FreeBSD Security Advisories

   Contributed by Tom Rhodes.

   Like many production quality operating systems, FreeBSD publishes
   !S:Security Advisories!". These advisories are usually mailed to
   the security lists and noted in the Errata only after the
   appropriate releases have been patched. This section will work to
   explain what an advisory is, how to understand it, and what
   measures to take in order to patch a system.

     --------------------------------------------------------------

  14.14.1. What does an advisory look like?

   The FreeBSD security advisories look similar to the one below,
   taken from the freebsd-security-notifications mailing list.

 =============================================================================
 FreeBSD-SA-XX:XX.UTIL                                     Security Advisory
                                                           The FreeBSD Project

 Topic:          denial of service due to some problem(1)

 Category:       core(2)
 Module:         sys(3)
 Announced:      2003-09-23(4)
 Credits:        Person@EMAIL-ADDRESS(5)
 Affects:        All releases of FreeBSD(6)
                 FreeBSD 4-STABLE prior to the correction date
 Corrected:      2003-09-23 16:42:59 UTC (RELENG_4, 4.9-PRERELEASE)
                 2003-09-23 20:08:42 UTC (RELENG_5_1, 5.1-RELEASE-p6)
                 2003-09-23 20:07:06 UTC (RELENG_5_0, 5.0-RELEASE-p15)
                 2003-09-23 16:44:58 UTC (RELENG_4_8, 4.8-RELEASE-p8)
                 2003-09-23 16:47:34 UTC (RELENG_4_7, 4.7-RELEASE-p18)
                 2003-09-23 16:49:46 UTC (RELENG_4_6, 4.6-RELEASE-p21)
                 2003-09-23 16:51:24 UTC (RELENG_4_5, 4.5-RELEASE-p33)
                 2003-09-23 16:52:45 UTC (RELENG_4_4, 4.4-RELEASE-p43)
                 2003-09-23 16:54:39 UTC (RELENG_4_3, 4.3-RELEASE-p39)(7)
 FreeBSD only:   NO(8)

 For general information regarding FreeBSD Security Advisories,
 including descriptions of the fields above, security branches, and the
 following sections, please visit
 http://www.FreeBSD.org/security/.

 I.   Background(9)


 II.  Problem Description(10)


 III. Impact(11)


 IV.  Workaround(12)


 V.   Solution(13)


 VI.  Correction details(14)


 VII. References(15)

   (1)
           The Topic field indicates exactly what the problem is. It
           is basically an introduction to the current security
           advisory and notes the utility with the vulnerability.
   (2)
           The Category refers to the affected part of the system
           which may be one of core, contrib, or ports. The core
           category means that the vulnerability affects a core
           component of the FreeBSD operating system. The contrib
           category means that the vulnerability affects software
           contributed to the FreeBSD Project, such as sendmail.
           Finally the ports category indicates that the
           vulnerability affects add on software available as part of
           the Ports Collection.
   (3)
           The Module field refers to the component location, for
           instance sys. In this example, we see that the module,
           sys, is affected; therefore, this vulnerability affects a
           component used within the kernel.
   (4)
           The Announced field reflects the date said security
           advisory was published, or announced to the world. This
           means that the security team has verified that the problem
           does exist and that a patch has been committed to the
           FreeBSD source code repository.
   (5)
           The Credits field gives credit to the individual or
           organization who noticed the vulnerability and reported
           it.
   (6)
           The Affects field explains which releases of FreeBSD are
           affected by this vulnerability. For the kernel, a quick
           look over the output from ident on the affected files will
           help in determining the revision. For ports, the version
           number is listed after the port name in /var/db/pkg. If
           the system does not sync with the FreeBSD CVS repository
           and rebuild daily, chances are that it is affected.
   (7)
           The Corrected field indicates the date, time, time offset,
           and release that was corrected.
   (8)
           The FreeBSD only field indicates whether this
           vulnerability affects just FreeBSD, or if it affects other
           operating systems as well.
   (9)
           The Background field gives information on exactly what the
           affected utility is. Most of the time this is why the
           utility exists in FreeBSD, what it is used for, and a bit
           of information on how the utility came to be.
   (10)
           The Problem Description field explains the security hole
           in depth. This can include information on flawed code, or
           even how the utility could be maliciously used to open a
           security hole.
   (11)
           The Impact field describes what type of impact the problem
           could have on a system. For example, this could be
           anything from a denial of service attack, to extra
           privileges available to users, or even giving the attacker
           superuser access.
   (12)
           The Workaround field offers a feasible workaround to
           system administrators who may be incapable of upgrading
           the system. This may be due to time constraints, network
           availability, or a slew of other reasons. Regardless,
           security should not be taken lightly, and an affected
           system should either be patched or the security hole
           workaround should be implemented.
   (13)
           The Solution field offers instructions on patching the
           affected system. This is a step by step tested and
           verified method for getting a system patched and working
           securely.
   (14)
           The Correction Details field displays the CVS branch or
           release name with the periods changed to underscore
           characters. It also shows the revision number of the
           affected files within each branch.
   (15)
           The References field usually offers sources of other
           information. This can included web URLs, books, mailing
           lists, and newsgroups.

     --------------------------------------------------------------

14.15. Process Accounting

   Contributed by Tom Rhodes.

   Process accounting is a security method in which an administrator
   may keep track of system resources used, their allocation among
   users, provide for system monitoring, and minimally track a user's
   commands.

   This indeed has its own positive and negative points. One of the
   positives is that an intrusion may be narrowed down to the point
   of entry. A negative is the amount of logs generated by process
   accounting, and the disk space they may require. This section will
   walk an administrator through the basics of process accounting.

     --------------------------------------------------------------

  14.15.1. Enable and Utilizing Process Accounting

   Before making use of process accounting, it must be enabled. To do
   this, execute the following commands:

 # touch /var/account/acct

 # accton /var/account/acct

 # echo 'accounting_enable="YES"' >> /etc/rc.conf

   Once enabled, accounting will begin to track CPU stats, commands,
   etc. All accounting logs are in a non-human readable format and
   may be viewed using the sa(8) utility. If issued without any
   options, sa will print information relating to the number of per
   user calls, the total elapsed time in minutes, total CPU and user
   time in minutes, average number of I/O operations, etc.

   To view information about commands being issued, one would use the
   lastcomm(1) utility. The lastcomm may be used to print out
   commands issued by users on specific ttys(5), for example:

 # lastcomm ls
         trhodes ttyp1

   Would print out all known usage of the ls by trhodes on the ttyp1
   terminal.

   Many other useful options exist and are explained in the
   lastcomm(1), acct(5) and sa(8) manual pages.

     --------------------------------------------------------------

                             ^3^1 15. Jails

   Contributed by Matteo Riondato.

     --------------------------------------------------------------

15.1. .S:z

   YEN>>^3^1+-NCURP:^2D- FreeBSD jail
   NOTDEG|o!AYENHCURI|p|o^1BYENICURS:-ak!C Jails
   |^3(R)ECUR]+-`^3Q>>{NOTDEGNOTO chroot Ao^1O
   -a-oYEN[+-j<<NOT'AYENN<<~CURS:CUR@!AYEN|^1i"t^2I-oTH^2z-aI|O"YENNOTO<<D+-`|nYENI-a-oCURu"a!A
   |^1YEN~!AYEN|-a-oCUR@"C,DEGoYEN>>YENI-ak^1iP:iP:YEN"IYENI-aI|O"YEN!ACUR]NOTONOTU.i|^3YENI!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!J

     * jail NOTOCURDEG>>o!AYENHCURIYEN||b FreeBSD
       CURWYENiYENHuo'S:-a-oS:@YENI!C

     * |p|o 1/2sA:P:!B+-ODEGE!BDEG+-CURi jail!C

     * jail -oTH^2z-a-oDEGoYEN>>.S:(c)A!GYEN]NOTA+-q jail
       CUR-o^3!(c)IYEND 3/4-:YEN>>"!C

   "a:YENL|^3YENI-a-o jail NOTUAo:,e. 1/2AU|^3!G

     * jail(8)  1/2uCURW>>!(c)u!C ^3oNOTO|^3Ao: jail -a-oS:^1
       3/4a>>!(c)u !X!X FreeBSD CUR-o-a-o+-ODEGE!BDEG+-CURi!B+-+-"i
       FreeBSD jail NOTUAo:-oTH^2zCURu"a!C

     * P:l>> 1/4 1/2 * 3/4A(mailing lists)CURIAA<<HAE(R)
       *A](archives)!C FreeBSD list server (c)O'-L-"N-a-o FreeBSD
       general questions P:l>> 1/4 1/2 * 3/4A CURI"a:YENLP:l>> 1/4
       1/2 * 3/4A-a-oAA<<H !ACURw|^3YEN]NOTACUR@DEGi jail
       -a-o|^3YENI,e(R)AE!C ^3q+-`!A.j'MAA<<H(c)I-aI|b
       freebsd-questions CURWuoDEGY!ACUR]NOTU.i|^3(R)A:!C

     --------------------------------------------------------------

15.2. Jail NOTUAo:^3N>>y

   NOTDEG"oS:US:o(R)e(c)o:^2z,N FreeBSD "t^2I-a-o jail
   NOTUAo:^3!CURA!A YENHCURIYEN|I>>P FreeBSD
   "a:YENL^3!CURA-a-oNOTUCURNOTS:@YENIAo:<<Y!A
   YENHCURU|CYENXYEN>>^3^1+-N"IYENI-a-o^3N>>y!G

   chroot(2) (<<u:YENO)

           FreeBSD -a-o system call
           CURS:CUR@!A"a:S:@YENINOTDEGS:iAAU: process CURI"a:lYENI
           process (c)O-`a^1BYENI-a-o(R)UYENO/?y (/ dir)!C

   chroot(2) (Ao^1O)

           <<u:|b !S:chroot!" CURCUR^1B|ae-a-o process Ao^1O!C
           ^3oYEN]NOTACURFAth|u:AE(R)
           *"t^2I-a-oYENi"-L-^3!CURA!BYENiYENI-a-o
           UID!BGID!B-oo,oYENdCURI"a:YENL IPC  3/4-:"iuYEN,e. 1/2!C

   jail(8) (command)

           CUR^1^3\u{|!|b jail
           Ao^1OCURUDEGo|ae-a-o"t^2I-oTH^2zCURu"a!C

   host ("t^2I!Bprocess!B+-b,^1uYENuYEN)

           jail Ao^1O-a-o+-+-"i"t^2I!C host
           "t^2IYENiYENH"IYENIYENth^3!YENiYENI-a-ouwAAe,e. 1/2!A
           "A-`a+-+-"i jail Ao^1OCUR-oYEN~-a-o process!C host
           "t^2I>>P jail ^3ICURj-a-o(R)tS:O|b(c)o !G|b host
           "t^2ICURCUR-a-o superuser processes "ACUR-L-^1^3|b jail
           Ao^1O"-o 1/4E^3B^3B"u:"`iCUR@DEGi"i!C

   hosted ("t^2I!Bprocess!B+-b,^1uYENuYEN)

           YENiYENI,e. 1/2"u:"`i FreeBSD jail "i-a-o
           process!B+-b,^1!B(c)I"a:YENL^3]^3AE,e. 1/2 !C

     --------------------------------------------------------------

15.3. I'-oNOTG"AE

   YENN(c)o"t^2I-oTH^2zNOTOS:xAo/CURSAc-o
   3/4-a-oCURuS:@!A|]|^1CURHIP:}uo^3\|h|nYENICURu"a!A
   YENHAAy-oTH^2zCURuS:@S:oYEN[A^2^3ae>>'AP!C ^3o"C,S:iu
   1/2^3q+-`NOTOAAy"t^2I-`aDEG-:YENHS:oA^2^3ae-a-oCURe|!|w,E!B
   ^3](c)w!B-ouAA@!A|O|^3"C,S:iu 1/2YENO/
   1/4D-<<hNOTO"t^2I|wYENth-a-oYEN?
   1/2T^3](c)w!A"I"a:-`a-uYEN?uo'S:`iYEN>>YENI^3~!A
   |O<<D^3'CURJ|wYENth.AICURS:CURCUR!C

   FreeBSD
   "t^2I(c)O'-L-"N-a-oCUR@-oO/YENI(c)o+-jCURAE|wYENth-a-oCURu"a'NNOTO
   jail !C Jail NOTOYENN Poul-Henning Kamp <phk@FreeBSD.org> (c)o
   FreeBSD 4.X P:}(c)l 3/4ECURJ!A|O|b FreeBSD 5.X
   "u:"`i^3\|h<<CURjS:i"}|OP:DEGCURj|"!A|"NOTDEG+-jCURj|OAEFNOT!-a-oCURl"t^2I!AYENO/<<eCUR'|b<<uA:oP:}uo!B
   YENH'-L-DEG-a"a:YENiYENI(c)E!B(R)A:-`a>>P|wYENth!C

     --------------------------------------------------------------

  15.3.1. |oNOTDEG Jail

   BSD-like S:@.~"t^2I|U 4.2BSD DEG_S:Y'-L-"N chroot(2)!C chroot(8)
   YENiYENI"OAAU:S:oCUR@^2O process -a-o(R)UYENO/?y|`i,m!A
   AC,|^1<<O/YENss>>P^1eAAe"t^2ICURCURNOTU^1jA-:-a-o|wYENthAo^1O!C
   ^3B(c)o chrooted Ao^1O-a-o process
   .|uL-akCUR-L--`a|s"uYEN@YEN~-a-oAE(R) *(c)I,e. 1/2!C
   YENN(c)o|^1|]-A!A NOTGS:Y"IS:d-A>>-aIS:d--}NOTYO^3B(c)o chroot
   Ao^1O-a-o service!ACUR]CUR-L--`aS:d--} 3/4aO"t^2I!C chroot(8)
   ^1i(c)o"-o"C,CUR-L-CURO>>Yn 1/4u(c)E(c)I
   1/2AEAo/CURSDEG-a-AA-a-oA^2^3aeA^3YENI|O"YENNOTU.i|nYENI!C
   YENtYEN~!A|bCURTHCURJ chroot
   .S:(c)A-a-o^1Lu{CURCUR!A'?,guo^2{^3\|hYENi^2aeDEGk chroot
   Ao^1O-a-oCURe|!!A  3/4"-oTH^3o"C,DEGYAD|b,u.s-a(c)YEN>>-a-o
   FreeBSD kernel S:!CURw *YEN?!A|y<<U:(c)uAAa|a chroot(2)
   u'<<DYENI(c)o+-jCURAE|wYENth-a-o^2z.Q,N"MCURe(R) *!C |]|^1!A
   P:OYEN^2+-o^1eS:@.s-a-oCURl"t^2I"O,N"M^3o"C,DEGYAD!C

   ^3o'NNOTONOTDEG|onP:}uo jail -a-o^3IYENDn`i|]!C

   Jail |b|U-oO/CURe|!CURAP:i|XA>>!AS:iP:iP:C,^2I chroot(2)
   Ao^1O-a-o.S:(c)A!C |bP:C,^2I-a-o chroot(2) Ao^1OCURCUR!AYENu"i
   process ^1i(c)oAE(R) *"t^2I-a-o|s"u^3!CURA!A |O"t^2I,e.
   1/2-a-o"a:YENL^3!CURA("O|p"t^2I+-b,^1!BDEGo|aeCURCUR-a-o
   process!B-oo,oCURl"t^2I)<<hNOTOYENN chroot process >>P host
   "t^2I-a-o"a:YENL process CUR@DEG_|@"E!C Jail
   YENH!yueAACURAE!z"OAX(R)i^3o 1/4O<<NOT!ACUR-L-^3aeYENu|^3AE(R)
   *"t^2I-a-o|s"u!AAU(c)u|u"`i "t^2I+-b,^1!BFreeBSD kernel
   -a-o-oo,oCURl"t^2ICURI"a:YENL"t^2I,e. 1/2-a-oueAACURAE!C
   Ao:(c)o^3o"C, jail Ao^1O|s"u-a-o^2O.L 1/2O+-+-!A 1/2D-DEGN 3/4\ uU
   15.5 ,`!C

   jail "a|^3CURU|CYEN|P:u-S|a!G

     * YENO/?yCURl 3/4d-(directory subtree) !X!X CUR]'NNOTOP:iCURJ
       jail -a-oDEG_AI!C CUR@YEN^1P:iCURJ jail CURS:<<a!Aprocess
       'NCUR-L-|A^3QCUR^1^3\,o"`i subtree YENHYEN~!C &P:C,^2I.|
       1/4vAAT"`i chroot(2)
       ^3I-a`i^3]p-a-o|wYENthDEGYAD!A'NCUR-L-.||A 1/4vAAT FreeBSD
       jail!C

     * YEND 3/4-:|W-oU(hostname) !X!X YENI(c)o jail -a-o hostname!C
       YENN(c)o jail YENDnYENI(c)o-oo,o-aADEGE!A|]|^1Y|U jail
       NOTO|^3|W-oU!A
       ^1i(c)o"t^2I-oTH^2zCURuS:@-a-oA^2CURAE.|NOTU.i|^3(R)A:!C

     * IP address !X!X NOTOYENI"Ou^1 jail "IYENI!A "AYENB|b jail
       YENI(c)RP:g'ACUR-o^3-L-uL-akAAU:S:o!C ^3q+-` jail -a-o IP
       address NOTO^2{|^3-ooYENd-a-o alias
       address!A|y^3o"ACUR-L-NOTOYEN^2P:.-a-o!C

     * <<u:YENO(Command) !X!X .C,^3AE|b jail CUR-oDEGo|ae-a-oS:^1
       3/4a,o(R)|!C ^3o<<u:YENONOTONOTU^1i(c)o jail
       Ao^1O-a-o(R)UYENO/?y!Auo/ jail
       Ao^1O-a-oAth<<NOTCUR-L-|P!A|O|^3(c)O(R)t^2S:!C

   DEG-L-CURFCURWzCURS:YEN~!Ajail CUR]YENi
   3/4O:|^3|UCURv-a-o+-b,^1CURI root +-b,^1!C .iuM!A^3o,I-a-oroot
   AAvCURO.|"u:"i(c)o jail Ao^1OCUR-o!C "AYENB+-q host
   "t^2I-a-o"CUR<< *"ONOTY!Ajail -a-o root
   "A<<DuL(c)OCUR-L--`a-a-o+-b,^1!C |^1YEN~ jail -a-o root
   "ACUR-L--`aDEGo|ae"a:^1i(c)o jail(8)
   Ao^1OYENHYEN~-a-oCUR@"C,Ao:Aa:(c)E 3/4THS:@!C Ao:(c)o root
   -a-o-`aCURO>>P"i!A+-N(c)ouy<<a-a-o uU 15.5 ,` CURP:^2D-CURS:!C

     --------------------------------------------------------------

15.4. <<O/YENss(c)M+-+-"i Jail

   |^3"C,"t^2I-oTH^2z-aIS:a jail
   CURANOTDEGCURU|C"a-oO/!G!S:complete(S:^1YENth)!" jail !X!X
   ^3q+-`YEN]NOTAS:^1 3/4a-a-o FreeBSD "t^2I!FYENtCUR@-oO/<<hNOTDEG
   !S:service(-aADEGE)!" jail !X!X
   +-M-auYENuP:]NOTY^3aeCUR@YENi-`anYENI-S(R)iAAv-a-ou{|!(c)I
   service!C ^3oYENuNOTOCUR@-oO/.S:(c)ACURW-a-oDEGICURA !A"ACUR-L-
   1/4vAAT|p|o<<O/YENss jail -a-o^1Lu{!C |U:(c)o|p|o<<O/YENss jail |b
   jail(8) CUR-o|^3S:o,O^2O-a-o>>!(c)u!G

 # setenv D /here/is/the/jail
 # mkdir -p $D (1)
 # cd /usr/src
 # make world DESTDIR=$D (2)
 # cd etc/ [12]
 # make distribution DESTDIR=$D (3)
 # mount -t devfs $D/dev (4)

   (1)
           -oYENy'NNOTOYENyNOTDEG jail S:a:O(R)a!C ,O,o(R)|NOTO|b
           host "t^2ICURCUR-a-o jail ^1eAAe|`i,m!C ^2ss-oDNOTO(c)n|b
           /usr/jail/jailname!A jailname  1/2D-'A'<<NOTDEG,O jail
           -a-o hostname YENH<<K?eS:O!C ^3q+-` /usr
           .||^3"NOTDEG-:-aAAP:!"O|s(c)n jail AE(R) *"t^2I!A^1i(c)o
           !S:complete!" jail |O"YEN!AYEN|^3q+-`YEN]NOTACURF FreeBSD
           ^1w^3]|w,E base system (c)O|^3AE(R) *-a-o<<th"(c)AE!C
   (2)
           ,O<<u:YENO+-N.||b jail YENO/?yCURCUR|w,E(c)O>>Y-a-o
           binary!Blibrary!Bmanual >>!(c)uuYEN !C
           ^3o"C,NOTOYENHP:C,^2I-a-o FreeBSD CURe|!S:^1|" !X!X
           S:Y-oYENyYENy 1/2sA:P:(c)O|^3AE(R) *!A
           +-uuU|A,E"`iYENO/-a-o|a!C
   (3)
           "IYENI distribution ^3oO make target
           "O,E(c)O|^3.|YENI"`i-a-o^3](c)wAE!C
           A^2^3ae"O>>!,ODEGES:@'NNOTOS:a /usr/src/etc/  1/2AE>>s"`i
           jail Ao^1OCUR-o-a-o /etc!ACUR]'NNOTO $D/etc/!C
   (4)
           ^1i(c)o jail Ao^1O|O"YEN!Adevfs(8) AE(R) *"t^2I-a-o+-
           3/4,u:"A<<DYEN^2P:.!A
           |yYENtCUR@CURe+-!A'XYENG(c)O|^3A^3YENIu{|!^3-L-.|>>Yn|s"u|U:CURO:CUR@O^3]^3AE(device)!A
           ^3oYENDn"u"M(c)o,Ou{|!YENO/-a-o|O(c)w!C +-+-"i jail
           (c)O-`a|s"u-a-o^3]^3AE<<D+-`<<n!A |]NOTDEGCUR-L-YEN?
           1/2T-a-o^3](c)w!A.|AAyS:d-A>>-aI^1i jail |^3
           3/4-:YENiP:X!C |U:(c)o|p|o^3z^1L devfs(8)
           "O+-+-"i-a-o^3W<<h!AYENiYENHDEGN 3/4\ devfs(8) CURI
           devfs.conf(5) >>!(c)u!C

   ,E|n jail CURS:<<a!A'NYENiYENHYENI jail(8) CURu"a!C jail(8)
   >>YnYEN|P:uYEN^2P:nDEGN 1/4AE!A^3o"C,DEGN 1/4AE|b uU 15.3.1 ,`
   |^3CURP:^2D-^1L!C DEG-L-CURF^3oYEN|ODEGN
   1/4AECURS:YEN~!AAUYENiYENH<<u:(c)w"a:YENLDEGN
   1/4AE!A^1^3NOTOYENH-S(c)w+-b,^1|b jail CURCURDEGo|ae process!C
   command DEGN 1/4AE"u"M(c)o jail Ath<<NOT|O(c)w!F^1i(c)o virtual
   system(ueAA"t^2I) !A"-o>>o'N?i 3/4U: /etc/rc!A
   |]NOTDEGYEN|.|S:^1|"-uYEN? FreeBSD "t^2I+-ODEGE(c)O>>Y-a-o
   3/4THS:@!C ^1i(c)o service(-aADEGE) jail
   |O"YEN!ADEGo|ae-a-o<<u:YENO"u"M(c)o+-N|b jail CUR-oDEGo|ae-a-o
   service (c)IA^3YENIu{|!|O(c)w!C

   Jail ^3q+-`n|b"t^2IP:} 3/4-:(R)E+-ODEGE!A|]|^1 FreeBSD -a-o rc 
   3/4-:"i'-L-"NCUR@"C,<<KS:Q-a-oCURe|!"OA^2CURAE^3o"C,CURuS:@!G

    1. P:} 3/4-:(R)En+-ODEGE-a-o jail ^2M^3aenYEN["`i rc.conf(5)
       ^3](c)wAE!G

 jail_enable="YES"   # Y^3]NOTDEG NO <<h-aiYENU:CUR-L-|UDEGE+-ODEGE jail
 jail_list="www"     # Y|^3^3\|h jail <<h 1/2D-YENH-aAAYENO^1jP:}"O 1/4g

    2. ^1i(c)o"CCUR@uS:|b jail_list (c)O|CYENX-a-o jail!A CUR]n|b
       rc.conf(5) DEGuYENXNOTU^1iA^3-a-o^3](c)w!G

 jail_www_rootdir="/usr/jail/www"     # jail -a-o(R)UYENO/?y
 jail_www_hostname="www.example.org"  # jail -a-o hostname
 jail_www_ip="192.168.0.10"           # jail -a-o IP address
 jail_www_devfs_enable="YES"          # |b jail CUR-o mount devfs
 jail_www_devfs_ruleset="www_ruleset" # jail CUR-o(c)OYENI-a-o devfs ^3W<<h-ai

       |b rc.conf(5) (c)O^1w^3]-a-o jail +-ODEGE^3](c)w.|P:] /etc/rc
       CUR-o-a-o jail script!ACUR]'NNOTO>>!.|DEG^2^3] jail NOTOS:^1
       3/4a-a-oueAA"t^2I!C YnYENI service jail
       Ath<<NOT!A<<hnYENtYEN~<<u:(c)w+-ODEGE<<u:YENO!A
       CURe-akNOTO^3](c)w^1iA^3-a-o jail_jailname_exec_start
       ^3](c)w!C

         -a`: Y+-y-a 3/4^1D(c)O|^3YENiYENI-a-o?iP:u^2M^3ae!A
         1/2D-DEGN 3/4\ rc.conf(5) >>!(c)u!C

   CUR]YENiYENH^3z^1LCURaDEGEDEGo|ae /etc/rc.d/jail script
   "O+-ODEGE(c)IDEG+-CURi rc.conf (c)O^3](c)w-a-o jail!G

 # /etc/rc.d/jail start www
 # /etc/rc.d/jail stop www

   YENO/<<e(c)|uLYENo|oCURe-ak"O<<U:DEG(R)^2b|aAo:^3NOT jail(8)!C
   |^1CURD|]NOTDEGYEN?+-`YENI"OAo:^3NOT"t^2I-a-o<<u:YENO!AYENO/<<e(c)|CUR-L--`a|b
   jail CURCUR"IYENI!C YENO/<<eAo:^3NOT jail ^3I"I-a-oCURe|!!ANOTO|b
   jail CUR-oDEGo|aeCURU|C<<u:YENO!A(c)I-aI jail YEN~+-^3z^1L
   jexec(8) DEGo|aeCURU|C<<u:YENO!G

 # sh /etc/rc.shutdown

   ,O+-! 1/2D-DEGN 3/4\ jail(8) >>!(c)u!C

     --------------------------------------------------------------

15.5. .L 1/2O>>P-oTH^2z

   YENiYENHNOTDEG jail ^3](c)w^3\|hCUR-L-|P?iP:u!A"AAAy FreeBSD -a-o
   host "t^2I>>P jail
   YENH|U-oO/CUR-L-|PCURe|!^2O|X.fDEGt!AYENH^2AA|XS:o|h-a-oA^3YENIYENI^3~!C
   YEN>>,`nCURP:^2D--a-oNOTO!G

     * YENIYENH.L 1/2O jail |aeNOTDEG>>P|wYENth"i-a-o?iP:u!C

     * YENi^3z^1L FreeBSD Ports Collection |w,E-a-oDEG-aP:YEN jail
       -oTH^2zu{|!!A .fDEGt^3o"C,u{|!YENiYENH^1F"`iCUR@"C, jail-based
       ,N"MCURe(R) *!C

     --------------------------------------------------------------

  15.5.1. FreeBSD (c)O'-L-"N-a-o jail tuning CURu"a

   ^1i(c)o jail ^3](c)w-a-o.L
   1/2O!ADEGoYEN>>CURW^3-L-NOTO^3z^1L^3](c)w sysctl(8) AAU:
   1/4AE"OS:^1|"!C "t^2I'-L-"NCUR@^2O sysctl -a-o-S(R)iCURl
   3/4d-!AYENth^3!NOTUAo:-a-o?iP:u^3-L-|b,OCURl
   3/4d-CUR-o!ACUR]'NNOTO FreeBSD kernel CURCUR-a-o security.jail.*
   CURl 3/4d-!C CURU+-<<hNOTO>>P jail NOTUAo:-a-oYENDn sysctl
   ^3](c)wCURI^1w^3]E!A^3o"C,|W-oU^3-L-NOTU.i(R)e(c)o:^2z,N!A
   |p+-yS:oP:iCUR@"B-a-o,eDEGT!A 1/2D-DEGN 3/4\ jail(8) >>P sysctl(8)
   >>!(c)u!G

     * security.jail.set_hostname_allowed: 1

     * security.jail.socket_unixiproute_only: 1

     * security.jail.sysvipc_allowed: 0

     * security.jail.enforce_statfs: 2

     * security.jail.allow_raw_sockets: 0

     * security.jail.chflags_allowed: 0

     * security.jail.jailed: 0

   "t^2I-oTH^2z-aIYENi|b host system ^3z^1L *S:i^3o"C,^3](c)wE"O
   1/4WYEN[!B"u(R)o/ Jail CUR-o root +-b,^1-a-o^1w^3]"i!C 
   1/2D--a`.N!G|^3"C,"iNOTOCUR-L--`a"u(R)o/!A|b jail(8) Ao^1O-a-o
   root CUR-L--`a+- 3/4,u:(c)I"o/,u:AE(R) *"t^2I!C
   |^1YEN~YENc,CUR-L--`a,u:CURJ!B "o/,u: devfs(8) ^3W<<h!B^3](c)w"
   3/4CURoAd-^3W<<h!A(c)IDEGo|ae"a:YENL>>Y *S:i kernel
   ,e(R)AE-a-o-oTH^2zS:@.~!A"O|p^3](c)w kernel -a-o securelevel E!C

   FreeBSD base system
   CUR-o-athCUR@"C,DEGoYEN>>CURu"a!AYENiYENI"ONOTd
   3/4\YENO/<<e"IYENICURCUR-a-o jail!B "A+-uCURW(attach) jail
   YENHDEGo|ae-oTH^2z<<u:YENO!C jls(8) CURI jexec(8) S:!A:Y(c)o
   FreeBSD base system
   CURS:CUR@!AYENiYENI"ODEGo|aeCUR@"C,A^2^3aeCURuS:@!G

     * |CYENX|^3|b"IYENI-a-o jail CURI"a:NOTU^1iA^3-a-o jail
       identifier (JID)!BIP address!B hostname!B,o(R)|!C

     * +-uCURW(Attach)YEN?|b^1BS:@CURCUR-a-o
       jail!A"A|b"a:CURCURDEGo|ae<<u:YENOYENHP:i|ae-oTH^2zCURuS:@!C
       ^3oAI|b.i root .QDEG(R)^2bAo:^3NOT jail (R)ENOTU.i|^3YENI!A
       jexec(8) CUR]YENiYENI|b jail CURCUR+-ODEGE shell
       YENH<<K^1i"a:P:i|ae-oTH^2z!A CURn|p!G

 # jexec 1 tcsh

     --------------------------------------------------------------

  15.5.2. FreeBSD Ports Collection (c)O'-L-"N-a-oDEG-aP:YEN-oTH^2zCURu"a

   |b 1/2N|h third-party (c)O'-L-"N-a-o jail
   -oTH^2zCURu"a.iCURCUR!Asysutils/jailutils NOTO^3IS:^1
   3/4aCUR]^3I|nYENI-a-o!C ,O(R)MYENoNOTOYENNCUR@"t|C jail(8)
   -oTH^2zCURpCURu"a(c)O^2O|"-a-o!C ,O+-! 1/2D-DEGN
   3/4\"a:-oo-,CURP:^2D- !C

     --------------------------------------------------------------

15.6. Jail -a-oA^3YENI

  15.6.1. Service Jails

   Contributed by Daniel Gerzo.

   YEN>>,`YENDnYENH Simon L. Nielsen <simon@FreeBSD.org>  1/4g-a-o
   http://simon.nitro.dk/service-jails.html NOTDEGYEND!AYEN[CURW Ken
   Tom <locals@gmail.com> (c)OS:o.s-a-oCURaa^3^1!C
   YEN>>,`CURP:^2D-|p|o^3](c)w FreeBSD YENH jail(8) YEN\-`a"O
   1/4WYEN[ABYEN~-a-o|wYENth 1/4h+-!C
   ^3o^3!CURADEG^2^3]+-z"t^2IP:]-a-oNOTO RELENG_6_0
   (c)IS:o.s-a-o-a(c)YEN>>!A
   "AYENB^1iYEN>>^3^1YENy<<e^3!CURAS:!-`a^2z,N!C

     --------------------------------------------------------------

    15.6.1.1. Design

   Jail
   -a-oYENDnDEGYADCURS:CUR@|b(c)o|p|o^1i"a:P:i|aeS:o.s!BCURE-AA(c)M-oTH^2z!C
   YENN(c)o"CO jail ^3-L-NOTO+-qAY<<.s 1/2sA:P:!A^1i(c)o^3aeCUR@ jail
   |O"YEN!A
   CURE-AACUR]^3\AUCUR-L-NOTO<<U:A:Y<<-a-oDEGYAD!A|]NOTDEGS:o.s!BCURE-AA"ACUR-L-.|CURO^3A.D-!C
   |y^1i(c)oCUR@DEGi jail
   |O"YEN!ACURE-AACUR-L-P:E.|-OP:OCURO|h(R)EP:!!A"ANOTU.iNOT\AeYENF"y!C

     A:uS:i^3o"C,^3](c)w-a-o<<e'-L-NOTO+-z^1i FreeBSD
     "IYENI!BYEN\-`a^1BYENICURW|^3NOTU.i-a-o,gAAc,!A
     YCURU+--a-o^3](c)w^1i+-z"O>>!CURO^1L 1/2AEAo/!A<<O/A:^3+-z,O|O
     1/4{YENI,uA^2(c)o:-a-o"t^2I!A^1^3NOTO
     sysutils/ezjail!A"a:'-L-"NS:oA^2^3ae-a-o FreeBSD jail
     -oTH^2zCURe|!!C

   DEGoYEN>>-a-o.Q-akNOTO|bCUR-L-|P-a-o jail CURCUR
   3/4"P:qYENH|wYENth-a-oCURe|!"O|@YENI,e. 1/2 !X!X
   +-A:YENIDEGssAA-a-a-o mount_nullfs(8) +-
   3/4,u:!A"OAAyCURE-AAS:oA^2^3ae!A "AS:a|UO service
   (c)n"`iCUR-L-|P-a-o jail -a-oS:@-ak.|S:oYEN[YENi|ae!C |^1YEN~!A
   "a:CUR]'-L-"N^1i(c)o|p|o 1/4WYEN[!BS:RDEG-L-!BCURE-AA jail
   -a-oA^2<<KCURe|!!C

     -a`: service +-`"-L--a-o"OCURlYEN]NOTA!G HTTP server!BDNS
     server!BSMTP server uYENuYEN!C

   YEN>>,`CURP:^2D--a-o^3](c)wYENO/-a-o|b(c)o!G

     * <<O/YENssA^2(c)o:YENB(R)e(c)o:^2z,N-a-o jail NOT[-oc!C
       CUR]'NNOTO>>! CUR-L-YEN^2NOTDEG"CO jail ^3-L-DEGo|aeS:^1
       3/4a-a-o installworld !C

     * AAy jail -a-o.s 1/4W!B^2 3/4DEG-L-S:oA^2^3ae!C

     * AAy jail -a-oS:o.s!BCURE-AAS:o>>'AP!C

     * YENiYENHP:]|U|aeYEN'^3y-a-o FreeBSD CURACURa:!C

     * ^1i|wYENth|^3S:oDEG 3/4DEGo"g-a-oDEGl"D!A
       3/4"YENi-`aDEGS:C^3QS:d-^3'-a-oYENi-`a!C

     * 3/4"P:q,`NOTU-aAAP:!>>P inode!C

   |p|PYENy<<e(c)O'-L-"`i-a-o!A^3o^3]pYENDnNOTO
   3/4aS:aDEGssAA-a-a-oYENDn 1/4O-a(c) (CUR]'NNOTOCURj(R)a(c)O 1/4o-a
   3/4-a-o nullfs)+- 3/4,u:"`i"CO jail!A"AYENBAAy"CO jail
   |^3OYENiAA-a!B
   1/4g-a-o^3]^3AE!A^3o^3]^3AEYENiYENHNOTO?WYENss^1eAAeuw-oD-!B
   !BCURA^3IDEGI!B(c)IYENH vnode NOTDEG<<a-oY-a-o md(4) ^3]^3AE!C
   |bYEN>>"O.iCURCUR!A S:UI+-A:YENIYENiAA-a 1/4g-a-o nullfs +-
   3/4,u:!C

   CURU+--a-o-ai<<hCURP:^2D-AE(R) *"t^2I-a-oDEGt,m!G

     * "CO jail ^3-L-.|+- 3/4,u:"`i /home/j
       (c)^3CURU-a-o"a:CURCURCUR@OYENO/?y!C

     * /home/j/mroot <<hNOTO"CO jail |@YENI-a-o
       1/4O-a(c)!A"A^1i(c)o(c)O|^3 jail |O"YEN^3-L-NOTODEGssAA-a!C

     * "CO jail |b /home/j
       (c)^3CURU^3-L-|^3CUR@ONOTU^1iA^3-a-o-aAAYENO/?y!C

     * "CO jail ^3-L-.||^3 /s YENO/?y!A
       ,OYENO/?y.|^3s"`i"t^2I-a-oYENiAA-a 1/4g^3!CURA!C

     * "CO jail ^3-L-.||b /home/j/skel
       YENO/?y<<O/YENss|UA:Y-a-oYENiAA-a 1/4g-aAAP:! !C

     * "CO jailspace (|U jail YENiAA-a 1/4g-a-o^3!CURA) ^3-L-<<O/|b
       /home/js>!C

     -a`: ^3oAa:DEG^2^3](c)O|^3 jail ^3-L-(c)n|b /home CURA^3IDEGI!C
     .iuM!A
     CUR]YENiYENH"I|U">>Y"DS:oS:i!A|y+-uCURU"O-a-o"OCURlCURCUR!A
     CUR]nDEGO+-o *S:iNOTU^1iA^3-a-o|aCURe!C

     --------------------------------------------------------------

    15.6.1.2. <<O/YENss 1/4O-a(c)

   YEN>>,`+-N^3v"BCURP:^2D-|p|o<<O/YENss jail nYENI-a-oDEGssAA-aYEND
   1/4O-a(c)!C

   <<O/A:^3YENyS:a FreeBSD "t^2ICURE-AA"`i^3I.s-a-o -RELEASE
   CURACURa:!A|U:(c)o|p|oDEGu 1/2D-DEGN 3/4\ Handbook -a-o
   NOTUAo:^3^1,`!C .iS:o.sS:^1|"CURS:<<a!A'NnP:i|ae buildworld
   u{S:C,!A|^1YEN~AUn,E sysutils/cpdup (R)MYENo!C S:UI+-NYENI
   portsnap(8) "OCURU,u: FreeBSD Ports Collection!A |b Handbook
   CURCUR^1i Portsnap ^3^1,` CURCUR|^3NOTUAo:CURP:^2D-!A-a`i
   3/4C,-aIYENiYENHNOTYNOTY!C

    1. -oYENy!AYENy<<O/YENssDEGssAA-a-a-oYENO/?yu^2-ocu^1 jail (c)n
       FreeBSD binary!A +-uuU"`i FreeBSD source tree YENO/?y!A"A|w,E
       jail  1/4O-a(c)!G

 # mkdir -p /home/j/mroot
 # cd /usr/src
 # make installworld DESTDIR=/home/j/mroot

    2. +-uuU,o FreeBSD source tree CUR@ 1/4E!ACUR]S:a FreeBSD Ports
       Collection (c)nCUR@YEN-:"N jail "IYENI!AYENH^3AE mergemaster
       !G

 # cd /home/j/mroot
 # mkdir usr/ports
 # portsnap -p /home/j/mroot/usr/ports fetch extract
 # cpdup /usr/src /home/j/mroot/usr/src

    3. <<O/YENssYENiAA-a 1/4g^3!CURA-a-oDEG(c)NOT[!G

 # mkdir /home/j/skel /home/j/skel/home /home/j/skel/usr-X11R6 /home/j/skel/distfiles
 # mv etc /home/j/skel
 # mv usr/local /home/j/skel/usr-local
 # mv tmp /home/j/skel
 # mv var /home/j/skel
 # mv root /home/j/skel

    4. YENI mergemaster "O,E-o|+- 1/4-a-o^3](c)wAE!C
       +-uCURU"OS:RDEG-L- mergemaster (c)O<<O/YENss-a-o|h
       3/4lYENO/?y!G

 # mergemaster -t /home/j/skel/var/tmp/temproot -D /home/j/skel -i
 # cd /home/j/skel
 # rm -R bin boot lib libexec mnt proc rescue sbin sys usr dev

    5. ^2{|bS:aYENiAA-a 1/4g-a-oAE(R) *"t^2IYENH symlink
       CURe|!^3s"`iDEGssAA-a-a-oAE(R) *"t^2I!C  1/2D- 1/2T>>{
       symbolic link NOTOS:_|^3YEN? 1/2T^3s"`i s/
       YENO/?y!AYYENO/?y<<O/YENssCURe|!CUR-L-^1i!A
       (c)I<<u:|V|`i,mCUR-L-^1i!AYENi-`a.| 3/4EP|w,EYEN-c-+-N!C

 # cd /home/j/mroot
 # mkdir s
 # ln -s s/etc etc
 # ln -s s/home home
 # ln -s s/root root
 # ln -s ../s/usr-local usr/local
 # ln -s ../s/usr-X11R6 usr/X11R6
 # ln -s ../../s/distfiles usr/ports/distfiles
 # ln -s s/tmp tmp
 # ln -s s/var var

    6. ^3I<<a<<hNOTO.s 1/4W /home/j/skel/etc/make.conf
       !A"AP:nCURJYENHCURUCUR-o(R)e!G

 WRKDIRPREFIX?=  /s/portbuild

       n^3](c)w WRKDIRPREFIX CUR~YENiYENHAAy|U jail +-oYENHP:P:S:Q
       1/2sA:P: FreeBSD ports!C 1/2D-DEGO|i ports
       YENO/?yNOTOA:YDEGssAA-aAE(R) *"t^2I!C |O.fDEGt|Uq-a-o
       WRKDIRPREFIX CUR~YENiYENHAAy|U jail |bYENiAA-a
       1/4g-aAAP:!P:i|ae 1/2sA:P:!C

     --------------------------------------------------------------

    15.6.1.3. <<O/YENss Jail

   ^2{|bCURw,g|^3S:^1 3/4a-a-o FreeBSD jail  1/4O-a(c)!AYENiYENH|b
   /etc/rc.conf CUR-oDEGuNOTUAo:^3](c)w!C CURU+-^3o"OCURl<<hYENU:
   1/2d|p|o<<O/YENss 3 O jail!G!S:NS!"!B !S:MAIL!"!B!S:WWW!"!C

    1. |b /etc/fstab YEN[CURWCURU|C^3](c)w!A YENH<<KAAy"t^2I|UDEGE+-
       3/4,u:|U jail (c)O>>Y-a-oDEGssAA-a 1/4O-a(c)>>PAA-a
       1/4g-aAAP:!!G

 /home/j/mroot   /home/j/ns     nullfs  ro  0   0
 /home/j/mroot   /home/j/mail   nullfs  ro  0   0
 /home/j/mroot   /home/j/www    nullfs  ro  0   0
 /home/js/ns     /home/j/ns/s   nullfs  rw  0   0
 /home/js/mail   /home/j/mail/s nullfs  rw  0   0
 /home/js/www    /home/j/www/s  nullfs  rw  0   0

         -a`: CURA^3IDEGI-a-o pass number  1/4D-YENU:NOTDEG 0
         'NCUR-L-.||bP:} 3/4-:(R)EDEGu fsck(8)
         AENOTd!F|OCURA^3IDEGI-a-o dump number  1/4D-YENU:NOTDEG 0
         <<hCUR-L-.|^3Q dump(8) (c)O^3AEYEN-:!C S:UI"ACUR-L-S:AE+-ae
         fsck AENOTd nullfs -a-o+- 3/4,u:!A(c)I-aIAAy dump ^3AEYEN-:
         jail CUR-oDEGssAA-a-a-o nullfs +- 3/4,u:!C
         ^3oCUR]'NNOTONOTDEG|oCURWz fstab
         "C|ae^3](c)w<<a+-^3-L-|^3"aA:aeNOTDEG !S:0 0!"!C

    2. |b /etc/rc.conf CUR-o^3](c)w jail!G

 jail_enable="YES"
 jail_set_hostname_allow="NO"
 jail_list="ns mail www"
 jail_ns_hostname="ns.example.org"
 jail_ns_ip="192.168.3.17"
 jail_ns_rootdir="/usr/home/j/ns"
 jail_ns_devfs_enable="YES"
 jail_mail_hostname="mail.example.org"
 jail_mail_ip="192.168.3.18"
 jail_mail_rootdir="/usr/home/j/mail"
 jail_mail_devfs_enable="YES"
 jail_www_hostname="www.example.org"
 jail_www_ip="62.123.43.14"
 jail_www_rootdir="/usr/home/j/www"
 jail_www_devfs_enable="YES"

         A:uS:iCURS:(c)OYENHnS:a jail_name_rootdir +-q /home
         S:iNOTDEG /usr/home -a-o`i|]|b(c)o FreeBSD ^1w^3]|w,E-a-o
         /home YENO/?y"a:^1eYENuNOTO<<u:|V /usr/home -a-o symbolic
         link!C |O jail_name_rootdir AAU: 1/4AEP:.NOTDEG
         ^1eAAeYENO/?y |O<<D symbolic link!A S:_<<h jail
         .|(c)Uu'+-ODEGE!C YENiYENHYENI realpath(1) "O"M(c)w,OAAU:
         1/4AE!C ,O+-! 1/2D-DEGN 3/4\ FreeBSD-SA-07:01.jail
         |wYENth^3qS:i!C

    3. 'A"CO jail <<O/YENssYEN^2P:.-a-oDEGssAA-aAE(R) *"t^2I+-
       3/4,u:AI!G

 # mkdir /home/j/ns /home/j/mail /home/j/www

    4. NOTDEG"CO jail |w,EYENiAA-a 1/4g-a-o 1/4O-a(c)!C 
       1/2D--a`.N^3o(R)EnYENI sysutils/cpdup !AYEN|-`a
       1/2T<<O"COYENO/?y^3-L-|^3YEN? 1/2T 1/2AE>>s!C

 # mkdir /home/js
 # cpdup /home/j/skel /home/js/ns
 # cpdup /home/j/skel /home/js/mail
 # cpdup /home/j/skel /home/js/www

    5. |p|^1CUR@"O'NCURwS:^1|" jail
       Ao^1O<<O/YENss!AYENiYENH.C,^3AE|nnYENICURF!C 
       1/2D-YENyNOTDEG|U jail +- 3/4,u:(c)OP:.-a-oAE(R)
       *"t^2I!A|AYENI /etc/rc.d/jail script "O+-ODEGE!G

 # mount -a
 # /etc/rc.d/jail start

   ^2{|b jail A^3,O'N.|+-ODEGECURF!C
   YnAENOTdNOTOS:_|^3YEN?+-`+-ODEGE!AYENiYENHYENI jls(8)
   <<u:YENO"ONOTY!A,O<<u:YENO-a-oDEGo|aeu^2-aGA^3,OAth|u:CURU+-!G

 # jls
    JID  IP Address      Hostname                      Path
      3  192.168.3.17    ns.example.org                /home/j/ns
      2  192.168.3.18    mail.example.org              /home/j/mail
      1  62.123.43.14    www.example.org               /home/j/www

   |^1(R)E'NYENiYENHunCURJ|U jail "A.s 1/4W+-b,^1>>P^3](c)wNOTUAo:
   service nYENI-a-o daemon !C CURW+--a-o JID
   A:aeYENN-aiYEN?|b^1BS:@CURCUR-a-o jail  1/2s,^1!C
   YENiYENICURU|C<<u:YENOYENH|b JID  1/2s,^1 3 -a-o jail
   DEGo|ae-oTH^2zCURuS:@!G

 # jexec 3 tcsh

     --------------------------------------------------------------

    15.6.1.4. CURE-AA

   |^3(R)EYENN(c)o|wYENthDEGYAD(c)I-aI jail
   CUR-onYENI.sYEN\-`a!A|O>>YnS:a FreeBSD "t^2ICURE-AA"`iS:o.s!C
   ^3o-oO/|w,E^3]pCURe|!AAyNOTJ|^3-a-o jail
   CURE-AAAAU:+-oS:oYEN[(R)e(c)o:!C jail CUR]YENiYENHS:a service
   DEG+- 3/4-:(R)EP:!(downtime)DEG"`i^3IS:C!A|]NOTDEG jail
   YENu>>Y|b^3I<<aAo:Aa:CUR~>>Yn<<P:}!C
   |^1YEN~!A,UCUR@.s-a(c)|^3DEGYAD-a-o,U:!A
   YEN|CUR]'-L-"N>>'AP|^.^1"`iAA-a(c)-a-oYEN\-`a!C

    1. -oYENyNOTO.OCUR@-eCURe|!"OCURE-AA host system!A|A.s
       1/4WA{(R)E-a-oDEGssAA-a 1/4O-a(c) /home/j/mroot2!G

 # mkdir /home/j/mroot2
 # cd /usr/src
 # make installworld DESTDIR=/home/j/mroot2
 # cd /home/j/mroot2
 # cpdup /usr/src usr/src
 # mkdir s

       |P 1/4E|a!A|bDEGo|ae installworld
       (R)E.|<<O/YENssCUR@"C,YENICUR-L-uU-a-oYENO/?y!A
       1/2D-S:a^3o"C,NOTaa+- 1/4!G

 # chflags -R 0 var
 # rm -R etc var root usr/local tmp

    2. <<.s<<O/YENss"`iYEND"t^2I-a-oYENiAA-a 1/4g-aAAP:! symlink!G

 # ln -s s/etc etc
 # ln -s s/root root
 # ln -s s/home home
 # ln -s ../s/usr-local usr/local
 # ln -s ../s/usr-X11R6 usr/X11R6
 # ln -s s/tmp tmp
 # ln -s s/var var

    3. ^2{|bYENiYENHAo:^3NOT jail!G

 # /etc/rc.d/jail stop

    4. "o/,u:`iYENy-a-oAE(R) *"t^2I!G

 # umount /home/j/ns/s
 # umount /home/j/ns
 # umount /home/j/mail/s
 # umount /home/j/mail
 # umount /home/j/www/s
 # umount /home/j/www

         -a`: YENiAA-a 1/4g-aAAP:!(/s) NOTO+- 3/4,u:|bDEGssAA-aAE(R)
         *"t^2I(c)^3CURU!ANOTGnYENy"o/,u:!C

    5. S:aAA-a-oDEGssAA-a"t^2I.h"<<!A'<<|".s-a-o!C |p|^1CUR@"O!A
       YENi|P(R)E<<O-dYENy<<e"t^2I-a-o^3AEYEN-:!AYENH^3AE,UCUR@CURE-AA<<a|^3DEGYADYENi|^'_!C
       ^3oAa:-a-o(c)R|WCURe|!+-A:.sDEGssAA-aAE(R)
       *"t^2I-a-o<<O/YENss(R)EP:!!A|^1YEN~`iYENy FreeBSD Ports
       Collection -a 1/2+-u.h"`i.s-a-oAE(R)
       *"t^2I!AYENH,`NOTUuw-oD--aAAP:!>>P inode !G

 # cd /home/j
 # mv mroot mroot.20060601
 # mv mroot2 mroot
 # mv mroot.20060601/usr/ports mroot/usr

    6. ^2{|b.s-a-oDEGssAA-a 1/4O-a(c).C,^3AE|nCURF!AYENu^3NCURU<<.s+-
       3/4,u:YENHCURI+-ODEGE jail!G

 # mount -a
 # /etc/rc.d/jail start

   ^3I<<aYENH jls(8) "OAENOTd jail NOTOS:_S:!YEN?+-`+-ODEGE!C
   S:OS:NCURFn|b|U jail CUR-oDEGo|ae
   mergemaster!AAU|^3NOTUAo:^3](c)wAEYENHCURI rc.d scripts
   S:!nS:o.s!C

     --------------------------------------------------------------

                   ^3^1 16. Mandatory Access Control

   Written by Tom Rhodes.

16.1. Synopsis

   FreeBSD 5.X introduced new security extensions from the TrustedBSD
   project based on the POSIX.1e draft. Two of the most significant
   new security mechanisms are file system Access Control Lists
   (ACLs) and Mandatory Access Control (MAC) facilities. Mandatory
   Access Control allows new access control modules to be loaded,
   implementing new security policies. Some provide protections of a
   narrow subset of the system, hardening a particular service, while
   others provide comprehensive labeled security across all subjects
   and objects. The mandatory part of the definition comes from the
   fact that the enforcement of the controls is done by
   administrators and the system, and is not left up to the
   discretion of users as is done with discretionary access control
   (DAC, the standard file and System V IPC permissions on FreeBSD).

   This chapter will focus on the Mandatory Access Control Framework
   (MAC Framework), and a set of pluggable security policy modules
   enabling various security mechanisms.

   After reading this chapter, you will know:

     * What MAC security policy modules are currently included in
       FreeBSD and their associated mechanisms.

     * What MAC security policy modules implement as well as the
       difference between a labeled and non-labeled policy.

     * How to efficiently configure a system to use the MAC
       framework.

     * How to configure the different security policy modules
       included with the MAC framework.

     * How to implement a more secure environment using the MAC
       framework and the examples shown.

     * How to test the MAC configuration to ensure the framework has
       been properly implemented.

   Before reading this chapter, you should:

     * Understand UNIX and FreeBSD basics (uU 3 ^3^1).

     * Be familiar with the basics of kernel
       configuration/compilation (uU 8 ^3^1).

     * Have some familiarity with security and how it pertains to
       FreeBSD (uU 14 ^3^1).

     A:uS:iThe improper use of the information in this chapter may
     cause loss of system access, aggravation of users, or inability
     to access the features provided by X11. More importantly, MAC
     should not be relied upon to completely secure a system. The MAC
     framework only augments existing security policy; without sound
     security practices and regular security checks, the system will
     never be completely secure.

     It should also be noted that the examples contained within this
     chapter are just that, examples. It is not recommended that
     these particular settings be rolled out on a production system.
     Implementing the various security policy modules takes a good
     deal of thought. One who does not fully understand exactly how
     everything works may find him or herself going back through the
     entire system and reconfiguring many files or directories.

     --------------------------------------------------------------

  16.1.1. What Will Not Be Covered

   This chapter covers a broad range of security issues relating to
   the MAC framework; however, the development of new MAC security
   policy modules will not be covered. A number of security policy
   modules included with the MAC framework have specific
   characteristics which are provided for both testing and new module
   development. These include the mac_test(4), mac_stub(4) and
   mac_none(4). For more information on these security policy modules
   and the various mechanisms they provide, please review the manual
   pages.

     --------------------------------------------------------------

16.2. Key Terms in this Chapter

   Before reading this chapter, a few key terms must be explained.
   This will hopefully clear up any confusion that may occur and
   avoid the abrupt introduction of new terms and information.

     * compartment: A compartment is a set of programs and data to be
       partitioned or separated, where users are given explicit
       access to specific components of a system. Also, a compartment
       represents a grouping, such as a work group, department,
       project, or topic. Using compartments, it is possible to
       implement a need-to-know security policy.

     * integrity: Integrity, as a key concept, is the level of trust
       which can be placed on data. As the integrity of the data is
       elevated, so does the ability to trust that data.

     * label: A label is a security attribute which can be applied to
       files, directories, or other items in the system. It could be
       considered a confidentiality stamp; when a label is placed on
       a file it describes the security properties for that specific
       file and will only permit access by files, users, resources,
       etc. with a similar security setting. The meaning and
       interpretation of label values depends on the policy
       configuration: while some policies might treat a label as
       representing the integrity or secrecy of an object, other
       policies might use labels to hold rules for access.

     * level: The increased or decreased setting of a security
       attribute. As the level increases, its security is considered
       to elevate as well.

     * multilabel: The multilabel property is a file system option
       which can be set in single user mode using the tunefs(8)
       utility, during the boot operation using the fstab(5) file, or
       during the creation of a new file system. This option will
       permit an administrator to apply different MAC labels on
       different objects. This option only applies to security policy
       modules which support labeling.

     * object: An object or system object is an entity through which
       information flows under the direction of a subject. This
       includes directories, files, fields, screens, keyboards,
       memory, magnetic storage, printers or any other data
       storage/moving device. Basically, an object is a data
       container or a system resource; access to an object
       effectively means access to the data.

     * policy: A collection of rules which defines how objectives are
       to be achieved. A policy usually documents how certain items
       are to be handled. This chapter will consider the term policy
       in this context as a security policy; i.e. a collection of
       rules which will control the flow of data and information and
       define whom will have access to that data and information.

     * sensitivity: Usually used when discussing MLS. A sensitivity
       level is a term used to describe how important or secret the
       data should be. As the sensitivity level increases, so does
       the importance of the secrecy, or confidentiality of the data.

     * single label: A single label is when the entire file system
       uses one label to enforce access control over the flow of
       data. When a file system has this set, which is any time when
       the multilabel option is not set, all files will conform to
       the same label setting.

     * subject: a subject is any active entity that causes
       information to flow between objects; e.g. a user, user
       processor, system process, etc. On FreeBSD, this is almost
       always a thread acting in a process on behalf of a user.

     --------------------------------------------------------------

16.3. Explanation of MAC

   With all of these new terms in mind, consider how the MAC
   framework augments the security of the system as a whole. The
   various security policy modules provided by the MAC framework
   could be used to protect the network and file systems, block users
   from accessing certain ports and sockets, and more. Perhaps the
   best use of the policy modules is to blend them together, by
   loading several security policy modules at a time for a
   multi-layered security environment. In a multi-layered security
   environment, multiple policy modules are in effect to keep
   security in check. This is different to a hardening policy, which
   typically hardens elements of a system that is used only for
   specific purposes. The only downside is administrative overhead in
   cases of multiple file system labels, setting network access
   control user by user, etc.

   These downsides are minimal when compared to the lasting effect of
   the framework; for instance, the ability to pick and choose which
   policies are required for a specific configuration keeps
   performance overhead down. The reduction of support for unneeded
   policies can increase the overall performance of the system as
   well as offer flexibility of choice. A good implementation would
   consider the overall security requirements and effectively
   implement the various security policy modules offered by the
   framework.

   Thus a system utilizing MAC features should at least guarantee
   that a user will not be permitted to change security attributes at
   will; all user utilities, programs and scripts must work within
   the constraints of the access rules provided by the selected
   security policy modules; and that total control of the MAC access
   rules are in the hands of the system administrator.

   It is the sole duty of the system administrator to carefully
   select the correct security policy modules. Some environments may
   need to limit access control over the network; in these cases, the
   mac_portacl(4), mac_ifoff(4) and even mac_biba(4) policy modules
   might make good starting points. In other cases, strict
   confidentiality of file system objects might be required. Policy
   modules such as mac_bsdextended(4) and mac_mls(4) exist for this
   purpose.

   Policy decisions could be made based on network configuration.
   Perhaps only certain users should be permitted access to
   facilities provided by ssh(1) to access the network or the
   Internet. The mac_portacl(4) would be the policy module of choice
   for these situations. But what should be done in the case of file
   systems? Should all access to certain directories be severed from
   other groups or specific users? Or should we limit user or utility
   access to specific files by setting certain objects as classified?

   In the file system case, access to objects might be considered
   confidential to some users, but not to others. For an example, a
   large development team might be broken off into smaller groups of
   individuals. Developers in project A might not be permitted to
   access objects written by developers in project B. Yet they might
   need to access objects created by developers in project C; that is
   quite a situation indeed. Using the different security policy
   modules provided by the MAC framework; users could be divided into
   these groups and then given access to the appropriate areas
   without fear of information leakage.

   Thus, each security policy module has a unique way of dealing with
   the overall security of a system. Module selection should be based
   on a well thought out security policy. In many cases, the overall
   policy may need to be revised and reimplemented on the system.
   Understanding the different security policy modules offered by the
   MAC framework will help administrators choose the best policies
   for their situations.

   The default FreeBSD kernel does not include the option for the MAC
   framework; thus the following kernel option must be added before
   trying any of the examples or information in this chapter:

 options MAC

   And the kernel will require a rebuild and a reinstall.

     -a`.NWhile the various manual pages for MAC policy modules state
     that they may be built into the kernel, it is possible to lock
     the system out of the network and more. Implementing MAC is much
     like implementing a firewall, care must be taken to prevent
     being completely locked out of the system. The ability to revert
     back to a previous configuration should be considered while the
     implementation of MAC remotely should be done with extreme
     caution.

     --------------------------------------------------------------

16.4. Understanding MAC Labels

   A MAC label is a security attribute which may be applied to
   subjects and objects throughout the system.

   When setting a label, the user must be able to comprehend what it
   is, exactly, that is being done. The attributes available on an
   object depend on the policy module loaded, and that policy modules
   interpret their attributes in different ways. If improperly
   configured due to lack of comprehension, or the inability to
   understand the implications, the result will be the unexpected and
   perhaps, undesired, behavior of the system.

   The security label on an object is used as a part of a security
   access control decision by a policy. With some policies, the label
   by itself contains all information necessary to make a decision;
   in other models, the labels may be processed as part of a larger
   rule set, etc.

   For instance, setting the label of biba/low on a file will
   represent a label maintained by the Biba security policy module,
   with a value of !S:low!".

   A few policy modules which support the labeling feature in FreeBSD
   offer three specific predefined labels. These are the low, high,
   and equal labels. Although they enforce access control in a
   different manner with each policy module, you can be sure that the
   low label will be the lowest setting, the equal label will set the
   subject or object to be disabled or unaffected, and the high label
   will enforce the highest setting available in the Biba and MLS
   policy modules.

   Within single label file system environments, only one label may
   be used on objects. This will enforce one set of access
   permissions across the entire system and in many environments may
   be all that is required. There are a few cases where multiple
   labels may be set on objects or subjects in the file system. For
   those cases, the multilabel option may be passed to tunefs(8).

   In the case of Biba and MLS, a numeric label may be set to
   indicate the precise level of hierarchical control. This numeric
   level is used to partition or sort information into different
   groups of say, classification only permitting access to that group
   or a higher group level.

   In most cases the administrator will only be setting up a single
   label to use throughout the file system.

   Hey wait, this is similar to DAC! I thought MAC gave control
   strictly to the administrator. That statement still holds true, to
   some extent as root is the one in control and who configures the
   policies so that users are placed in the appropriate
   categories/access levels. Alas, many policy modules can restrict
   the root user as well. Basic control over objects will then be
   released to the group, but root may revoke or modify the settings
   at any time. This is the hierarchal/clearance model covered by
   policies such as Biba and MLS.

     --------------------------------------------------------------

  16.4.1. Label Configuration

   Virtually all aspects of label policy module configuration will be
   performed using the base system utilities. These commands provide
   a simple interface for object or subject configuration or the
   manipulation and verification of the configuration.

   All configuration may be done by use of the setfmac(8) and
   setpmac(8) utilities. The setfmac command is used to set MAC
   labels on system objects while the setpmac command is used to set
   the labels on system subjects. Observe:

 # setfmac biba/high test

   If no errors occurred with the command above, a prompt will be
   returned. The only time these commands are not quiescent is when
   an error occurred; similarly to the chmod(1) and chown(8)
   commands. In some cases this error may be a !S:Permission denied!"
   and is usually obtained when the label is being set or modified on
   an object which is restricted.[13] The system administrator may
   use the following commands to overcome this:

 # setfmac biba/high test
 !S:Permission denied!"
 # setpmac biba/low setfmac biba/high test
 # getfmac test
 test: biba/high

   As we see above, setpmac can be used to override the policy
   module's settings by assigning a different label to the invoked
   process. The getpmac utility is usually used with currently
   running processes, such as sendmail: although it takes a process
   ID in place of a command the logic is extremely similar. If users
   attempt to manipulate a file not in their access, subject to the
   rules of the loaded policy modules, the !S:Operation not
   permitted!" error will be displayed by the mac_set_link function.

     --------------------------------------------------------------

    16.4.1.1. Common Label Types

   For the mac_biba(4), mac_mls(4) and mac_lomac(4) policy modules,
   the ability to assign simple labels is provided. These take the
   form of high, equal and low, what follows is a brief description
   of what these labels provide:

     * The low label is considered the lowest label setting an object
       or subject may have. Setting this on objects or subjects will
       block their access to objects or subjects marked high.

     * The equal label should only be placed on objects considered to
       be exempt from the policy.

     * The high label grants an object or subject the highest
       possible setting.

   With respect to each policy module, each of those settings will
   instate a different information flow directive. Reading the proper
   manual pages will further explain the traits of these generic
   label configurations.

     --------------------------------------------------------------

      16.4.1.1.1. Advanced Label Configuration

   Numeric grade numbers used for comparison:compartment+compartment;
   thus the following:

 biba/10:2+3+6(5:2+3-20:2+3+4+5+6)

   May be interpreted as:

   !S:Biba Policy Label!"/!S:Grade 10!" :!S:Compartments 2, 3 and
   6!": (!S:grade 5 ...!")

   In this example, the first grade would be considered the
   !S:effective grade!" with !S:effective compartments!", the second
   grade is the low grade and the last one is the high grade. In most
   configurations these settings will not be used; indeed, they
   offered for more advanced configurations.

   When applied to system objects, they will only have a current
   grade/compartments as opposed to system subjects as they reflect
   the range of available rights in the system, and network
   interfaces, where they are used for access control.

   The grade and compartments in a subject and object pair are used
   to construct a relationship referred to as !S:dominance!", in
   which a subject dominates an object, the object dominates the
   subject, neither dominates the other, or both dominate each other.
   The !S:both dominate!" case occurs when the two labels are equal.
   Due to the information flow nature of Biba, you have rights to a
   set of compartments, !S:need to know!", that might correspond to
   projects, but objects also have a set of compartments. Users may
   have to subset their rights using su or setpmac in order to access
   objects in a compartment from which they are not restricted.

     --------------------------------------------------------------

    16.4.1.2. Users and Label Settings

   Users themselves are required to have labels so that their files
   and processes may properly interact with the security policy
   defined on the system. This is configured through the login.conf
   file by use of login classes. Every policy module that uses labels
   will implement the user class setting.

   An example entry containing every policy module setting is
   displayed below:

 default:\
         :copyright=/etc/COPYRIGHT:\
         :welcome=/etc/motd:\
         :setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\
         :path=~/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:\
         :manpath=/usr/share/man /usr/local/man:\
         :nologin=/usr/sbin/nologin:\
         :cputime=1h30m:\
         :datasize=8M:\
         :vmemoryuse=100M:\
         :stacksize=2M:\
         :memorylocked=4M:\
         :memoryuse=8M:\
         :filesize=8M:\
         :coredumpsize=8M:\
         :openfiles=24:\
         :maxproc=32:\
         :priority=0:\
         :requirehome:\
         :passwordtime=91d:\
         :umask=022:\
         :ignoretime@:\
         :label=partition/13,mls/5,biba/10(5-15),lomac10[2]:

   The label option is used to set the user class default label which
   will be enforced by MAC. Users will never be permitted to modify
   this value, thus it can be considered not optional in the user
   case. In a real configuration, however, the administrator will
   never wish to enable every policy module. It is recommended that
   the rest of this chapter be reviewed before any of this
   configuration is implemented.

     -a`: Users may change their label after the initial login;
     however, this change is subject constraints of the policy. The
     example above tells the Biba policy that a process's minimum
     integrity is 5, its maximum is 15, but the default effective
     label is 10. The process will run at 10 until it chooses to
     change label, perhaps due to the user using the setpmac command,
     which will be constrained by Biba to the range set at login.

   In all cases, after a change to login.conf, the login class
   capability database must be rebuilt using cap_mkdb and this will
   be reflected throughout every forthcoming example or discussion.

   It is useful to note that many sites may have a particularly large
   number of users requiring several different user classes. In depth
   planning is required as this may get extremely difficult to
   manage.

   Future versions of FreeBSD will include a new way to deal with
   mapping users to labels; however, this will not be available until
   some time after FreeBSD 5.3.

     --------------------------------------------------------------

    16.4.1.3. Network Interfaces and Label Settings

   Labels may also be set on network interfaces to help control the
   flow of data across the network. In all cases they function in the
   same way the policies function with respect to objects. Users at
   high settings in biba, for example, will not be permitted to
   access network interfaces with a label of low.

   The maclabel may be passed to ifconfig when setting the MAC label
   on network interfaces. For example:

 # ifconfig bge0 maclabel biba/equal

   will set the MAC label of biba/equal on the bge(4) interface. When
   using a setting similar to biba/high(low-high) the entire label
   should be quoted; otherwise an error will be returned.

   Each policy module which supports labeling has a tunable which may
   be used to disable the MAC label on network interfaces. Setting
   the label to equal will have a similar effect. Review the output
   from sysctl, the policy manual pages, or even the information
   found later in this chapter for those tunables.

     --------------------------------------------------------------

  16.4.2. Singlelabel or Multilabel?

   By default the system will use the singlelabel option. But what
   does this mean to the administrator? There are several differences
   which, in their own right, offer pros and cons to the flexibility
   in the systems security model.

   The singlelabel only permits for one label, for instance biba/high
   to be used for each subject or object. It provides for lower
   administration overhead but decreases the flexibility of policies
   which support labeling. Many administrators may want to use the
   multilabel option in their security policy.

   The multilabel option will permit each subject or object to have
   its own independent MAC label in place of the standard singlelabel
   option which will allow only one label throughout the partition.
   The multilabel and single label options are only required for the
   policies which implement the labeling feature, including the Biba,
   Lomac, MLS and SEBSD policies.

   In many cases, the multilabel may not need to be set at all.
   Consider the following situation and security model:

     * FreeBSD web-server using the MAC framework and a mix of the
       various policies.

     * This machine only requires one label, biba/high, for
       everything in the system. Here the file system would not
       require the multilabel option as a single label will always be
       in effect.

     * But, this machine will be a web server and should have the web
       server run at biba/low to prevent write up capabilities. The
       Biba policy and how it works will be discussed later, so if
       the previous comment was difficult to interpret just continue
       reading and return. The server could use a separate partition
       set at biba/low for most if not all of its runtime state. Much
       is lacking from this example, for instance the restrictions on
       data, configuration and user settings; however, this is just a
       quick example to prove the aforementioned point.

   If any of the non-labeling policies are to be used, then the
   multilabel option would never be required. These include the
   seeotheruids, portacl and partition policies.

   It should also be noted that using multilabel with a partition and
   establishing a security model based on multilabel functionality
   could open the doors for higher administrative overhead as
   everything in the file system would have a label. This includes
   directories, files, and even device nodes.

   The following command will set multilabel on the file systems to
   have multiple labels. This may only be done in single user mode:

 # tunefs -l enable /

   This is not a requirement for the swap file system.

     -a`: Some users have experienced problems with setting the
     multilabel flag on the root partition. If this is the case,
     please review the uU 16.16 ,` of this chapter.

     --------------------------------------------------------------

  16.4.3. Controlling MAC with Tunables

   Without any modules loaded, there are still some parts of MAC
   which may be configured using the sysctl interface. These tunables
   are described below and in all cases the number one (1) means
   enabled while the number zero (0) means disabled:

     * security.mac.enforce_fs defaults to one (1) and enforces MAC
       file system policies on the file systems.

     * security.mac.enforce_kld defaults to one (1) and enforces MAC
       kernel linking policies on the dynamic kernel linker (see
       kld(4)).

     * security.mac.enforce_network defaults to one (1) and enforces
       MAC network policies.

     * security.mac.enforce_pipe defaults to one (1) and enforces MAC
       policies on pipes.

     * security.mac.enforce_process defaults to one (1) and enforces
       MAC policies on processes which utilize inter-process
       communication.

     * security.mac.enforce_socket defaults to one (1) and enforces
       MAC policies on sockets (see the socket(2) manual page).

     * security.mac.enforce_system defaults to one (1) and enforces
       MAC policies on system activities such as accounting and
       rebooting.

     * security.mac.enforce_vm defaults to one (1) and enforces MAC
       policies on the virtual memory system.

     -a`: Every policy or MAC option supports tunables. These usually
     hang off of the security.mac.<policyname> tree. To view all of
     the tunables from MAC use the following command:

 # sysctl -da | grep mac

   This should be interpreted as all of the basic MAC policies are
   enforced by default. If the modules were built into the kernel the
   system would be extremely locked down and most likely unable to
   communicate with the local network or connect to the Internet,
   etc. This is why building the modules into the kernel is not
   completely recommended. Not because it limits the ability to
   disable features on the fly with sysctl, but it permits the
   administrator to instantly switch the policies of a system without
   the requirement of rebuilding and reinstalling a new system.

     --------------------------------------------------------------

16.5. Module Configuration

   Every module included with the MAC framework may be either
   compiled into the kernel as noted above or loaded as a run-time
   kernel module. The recommended method is to add the module name to
   the /boot/loader.conf file so that it will load during the initial
   boot operation.

   The following sections will discuss the various MAC modules and
   cover their features. Implementing them into a specific
   environment will also be a consideration of this chapter. Some
   modules support the use of labeling, which is controlling access
   by enforcing a label such as !S:this is allowed and this is not!".
   A label configuration file may control how files may be accessed,
   network communication can be exchanged, and more. The previous
   section showed how the multilabel flag could be set on file
   systems to enable per-file or per-partition access control.

   A single label configuration would enforce only one label across
   the system, that is why the tunefs option is called multilabel.

     --------------------------------------------------------------

  16.5.1. The MAC seeotheruids Module

   Module name: mac_seeotheruids.ko

   Kernel configuration line: options MAC_SEEOTHERUIDS

   Boot option: mac_seeotheruids_load="YES"

   The mac_seeotheruids(4) module mimics and extends the
   security.bsd.see_other_uids and security.bsd.see_other_gids sysctl
   tunables. This option does not require any labels to be set before
   configuration and can operate transparently with the other
   modules.

   After loading the module, the following sysctl tunables may be
   used to control the features:

     * security.mac.seeotheruids.enabled will enable the module's
       features and use the default settings. These default settings
       will deny users the ability to view processes and sockets
       owned by other users.

     * security.mac.seeotheruids.specificgid_enabled will allow a
       certain group to be exempt from this policy. To exempt
       specific groups from this policy, use the
       security.mac.seeotheruids.specificgid=XXX sysctl tunable. In
       the above example, the XXX should be replaced with the numeric
       group ID to be exempted.

     * security.mac.seeotheruids.primarygroup_enabled is used to
       exempt specific primary groups from this policy. When using
       this tunable, the
       security.mac.seeotheruids.specificgid_enabled may not be set.

     --------------------------------------------------------------

16.6. The MAC bsdextended Module

   Module name: mac_bsdextended.ko

   Kernel configuration line: options MAC_BSDEXTENDED

   Boot option: mac_bsdextended_load="YES"

   The mac_bsdextended(4) module enforces the file system firewall.
   This module's policy provides an extension to the standard file
   system permissions model, permitting an administrator to create a
   firewall-like ruleset to protect files, utilities, and directories
   in the file system hierarchy.

   The policy may be created using a utility, ugidfw(8), that has a
   syntax similar to that of ipfw(8). More tools can be written by
   using the functions in the libugidfw(3) library.

   Extreme caution should be taken when working with this module;
   incorrect use could block access to certain parts of the file
   system.

     --------------------------------------------------------------

  16.6.1. Examples

   After the mac_bsdextended(4) module has been loaded, the following
   command may be used to list the current rule configuration:

 # ugidfw list
 0 slots, 0 rules

   As expected, there are no rules defined. This means that
   everything is still completely accessible. To create a rule which
   will block all access by users but leave root unaffected, simply
   run the following command:

 # ugidfw add subject not uid root new object not uid root mode n

     -a`: In releases prior to FreeBSD 5.3, the add parameter did not
     exist. In those cases the set should be used instead. See below
     for a command example.

   This is a very bad idea as it will block all users from issuing
   even the most simple commands, such as ls. A more patriotic list
   of rules might be:

 # ugidfw set 2 subject uid user1 object uid user2 mode n
 # ugidfw set 3 subject uid user1 object gid user2 mode n

   This will block any and all access, including directory listings,
   to user2's home directory from the username user1.

   In place of user1, the not uid user2 could be passed. This will
   enforce the same access restrictions above for all users in place
   of just one user.

     -a`: The root user will be unaffected by these changes.

   This should give a general idea of how the mac_bsdextended(4)
   module may be used to help fortify a file system. For more
   information, see the mac_bsdextended(4) and the ugidfw(8) manual
   pages.

     --------------------------------------------------------------

16.7. The MAC ifoff Module

   Module name: mac_ifoff.ko

   Kernel configuration line: options MAC_IFOFF

   Boot option: mac_ifoff_load="YES"

   The mac_ifoff(4) module exists solely to disable network
   interfaces on the fly and keep network interfaces from being
   brought up during the initial system boot. It does not require any
   labels to be set up on the system, nor does it have a dependency
   on other MAC modules.

   Most of the control is done through the sysctl tunables listed
   below.

     * security.mac.ifoff.lo_enabled will enable/disable all traffic
       on the loopback (lo(4)) interface.

     * security.mac.ifoff.bpfrecv_enabled will enable/disable all
       traffic on the Berkeley Packet Filter interface (bpf(4))

     * security.mac.ifoff.other_enabled will enable/disable traffic
       on all other interfaces.

   One of the most common uses of mac_ifoff(4) is network monitoring
   in an environment where network traffic should not be permitted
   during the boot sequence. Another suggested use would be to write
   a script which uses security/aide to automatically block network
   traffic if it finds new or altered files in protected directories.

     --------------------------------------------------------------

16.8. The MAC portacl Module

   Module name: mac_portacl.ko

   Kernel configuration line: MAC_PORTACL

   Boot option: mac_portacl_load="YES"

   The mac_portacl(4) module is used to limit binding to local TCP
   and UDP ports using a variety of sysctl variables. In essence
   mac_portacl(4) makes it possible to allow non-root users to bind
   to specified privileged ports, i.e. ports fewer than 1024.

   Once loaded, this module will enable the MAC policy on all
   sockets. The following tunables are available:

     * security.mac.portacl.enabled will enable/disable the policy
       completely.[14]

     * security.mac.portacl.port_high will set the highest port
       number that mac_portacl(4) will enable protection for.

     * security.mac.portacl.suser_exempt will, when set to a non-zero
       value, exempt the root user from this policy.

     * security.mac.portacl.rules will specify the actual mac_portacl
       policy; see below.

   The actual mac_portacl policy, as specified in the
   security.mac.portacl.rules sysctl, is a text string of the form:
   rule[,rule,...] with as many rules as needed. Each rule is of the
   form: idtype:id:protocol:port. The idtype parameter can be uid or
   gid and used to interpret the id parameter as either a user id or
   group id, respectively. The protocol parameter is used to
   determine if the rule should apply to TCP or UDP by setting the
   parameter to tcp or udp. The final port parameter is the port
   number to allow the specified user or group to bind to.

     -a`: Since the ruleset is interpreted directly by the kernel
     only numeric values can be used for the user ID, group ID, and
     port parameters. I.e. user, group, and port service names cannot
     be used.

   By default, on UNIX-like systems, ports fewer than 1024 can only
   be used by/bound to privileged processes, i.e. those run as root.
   For mac_portacl(4) to allow non-privileged processes to bind to
   ports below 1024 this standard UNIX restriction has to be
   disabled. This can be accomplished by setting the sysctl(8)
   variables net.inet.ip.portrange.reservedlow and
   net.inet.ip.portrange.reservedhigh to zero.

   See the examples below or review the mac_portacl(4) manual page
   for further information.

     --------------------------------------------------------------

  16.8.1. Examples

   The following examples should illuminate the above discussion a
   little better:

 # sysctl security.mac.portacl.port_high=1023
 # sysctl net.inet.ip.portrange.reservedlow=0 net.inet.ip.portrange.reservedhigh=0

   First we set mac_portacl(4) to cover the standard privileged ports
   and disable the normal UNIX bind restrictions.

 # sysctl security.mac.portacl.suser_exempt=1

   The root user should not be crippled by this policy, thus set the
   security.mac.portacl.suser_exempt to a non-zero value. The
   mac_portacl(4) module has now been set up to behave the same way
   UNIX-like systems behave by default.

 # sysctl security.mac.portacl.rules=uid:80:tcp:80

   Allow the user with UID 80 (normally the www user) to bind to port
   80. This can be used to allow the www user to run a web server
   without ever having root privilege.

 # sysctl security.mac.portacl.rules=uid:1001:tcp:110,uid:1001:tcp:995

   Permit the user with the UID of 1001 to bind to the TCP ports 110
   (!S:pop3!") and 995 (!S:pop3s!"). This will permit this user to
   start a server that accepts connections on ports 110 and 995.

     --------------------------------------------------------------

16.9. MAC Policies with Labeling Features

   The next few sections will discuss MAC policies which use labels.

   From here on this chapter will focus on the features of
   mac_biba(4), mac_lomac(4), mac_partition(4), and mac_mls(4).

     -a`: This is an example configuration only and should not be
     considered for a production implementation. The goal is to
     document and show the syntax as well as examples for
     implementation and testing.

   For these policies to work correctly several preparations must be
   made.

     --------------------------------------------------------------

  16.9.1. Preparation for Labeling Policies

   The following changes are required in the login.conf file:

     * An insecure class, or another class of similar type, must be
       added. The login class of insecure is not required and just
       used as an example here; different configurations may use
       another class name.

     * The insecure class should have the following settings and
       definitions. Several of these can be altered but the line
       which defines the default label is a requirement and must
       remain.

 insecure:\
         :copyright=/etc/COPYRIGHT:\
         :welcome=/etc/motd:\
         :setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\
         :path=~/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:\
         :manpath=/usr/share/man /usr/local/man:\
         :nologin=/usr/sbin/nologin:\
         :cputime=1h30m:\
         :datasize=8M:\
         :vmemoryuse=100M:\
         :stacksize=2M:\
         :memorylocked=4M:\
         :memoryuse=8M:\
         :filesize=8M:\
         :coredumpsize=8M:\
         :openfiles=24:\
         :maxproc=32:\
         :priority=0:\
         :requirehome:\
         :passwordtime=91d:\
         :umask=022:\
         :ignoretime@:\
         :label=partition/13,mls/5,biba/low:

       The cap_mkdb(1) command needs to be ran on login.conf(5)
       before any of the users can be switched over to the new class.

       The root username should also be placed into a login class;
       otherwise, almost every command executed by root will require
       the use of setpmac.

         A:uS:iRebuilding the login.conf database may cause some
         errors later with the daemon class. Simply uncommenting the
         daemon account and rebuilding the database should alleviate
         these issues.

     * Ensure that all partitions on which MAC labeling will be
       implemented support the multilabel. We must do this because
       many of the examples here contain different labels for testing
       purposes. Review the output from the mount command as a
       precautionary measure.

     * Switch any users who will have the higher security mechanisms
       enforced over to the new user class. A quick run of pw(8) or
       vipw(8) should do the trick.

     --------------------------------------------------------------

16.10. The MAC partition Module

   Module name: mac_partition.ko

   Kernel configuration line: options MAC_PARTITION

   Boot option: mac_partition_load="YES"

   The mac_partition(4) policy will drop processes into specific
   !S:partitions!" based on their MAC label. Think of it as a special
   type of jail(8), though that is hardly a worthy comparison.

   This is one module that should be added to the loader.conf(5) file
   so that it loads and enables the policy during the boot process.

   Most configuration for this policy is done using the setpmac(8)
   utility which will be explained below. The following sysctl
   tunable is available for this policy:

     * security.mac.partition.enabled will enable the enforcement of
       MAC process partitions.

   When this policy is enabled, users will only be permitted to see
   their processes but will not be permitted to work with certain
   utilities. For instance, a user in the insecure class above will
   not be permitted to access the top command as well as many other
   commands that must spawn a process.

   To set or drop utilities into a partition label, use the setpmac
   utility:

 # setpmac partition/13 top

   This will add the top command to the label set on users in the
   insecure class. Note that all processes spawned by users in the
   insecure class will stay in the partition/13 label.

     --------------------------------------------------------------

  16.10.1. Examples

   The following command will show you the partition label and the
   process list:

 # ps Zax

   This next command will allow the viewing of another user's process
   partition label and that user's currently running processes:

 # ps -ZU trhodes

     -a`: Users can see processes in root's label unless the
     mac_seeotheruids(4) policy is loaded.

   A really crafty implementation could have all of the services
   disabled in /etc/rc.conf and started by a script that starts them
   with the proper labeling set.

     -a`: The following policies support integer settings in place of
     the three default labels offered. These options, including their
     limitations, are further explained in the module manual pages.

     --------------------------------------------------------------

16.11. The MAC Multi-Level Security Module

   Module name: mac_mls.ko

   Kernel configuration line: options MAC_MLS

   Boot option: mac_mls_load="YES"

   The mac_mls(4) policy controls access between subjects and objects
   in the system by enforcing a strict information flow policy.

   In MLS environments, a !S:clearance!" level is set in each subject
   or objects label, along with compartments. Since these clearance
   or sensibility levels can reach numbers greater than six thousand;
   it would be a daunting task for any system administrator to
   thoroughly configure each subject or object. Thankfully, three
   !S:instant!" labels are already included in this policy.

   These labels are mls/low, mls/equal and mls/high. Since these
   labels are described in depth in the manual page, they will only
   get a brief description here:

     * The mls/low label contains a low configuration which permits
       it to be dominated by all other objects. Anything labeled with
       mls/low will have a low clearance level and not be permitted
       to access information of a higher level. In addition, this
       label will prevent objects of a higher clearance level from
       writing or passing information on to them.

     * The mls/equal label should be placed on objects considered to
       be exempt from the policy.

     * The mls/high label is the highest level of clearance possible.
       Objects assigned this label will hold dominance over all other
       objects in the system; however, they will not permit the
       leaking of information to objects of a lower class.

   MLS provides for:

     * A hierarchical security level with a set of non hierarchical
       categories;

     * Fixed rules: no read up, no write down (a subject can have
       read access to objects on its own level or below, but not
       above. Similarly, a subject can have write access to objects
       on its own level or above but not beneath.);

     * Secrecy (preventing inappropriate disclosure of data);

     * Basis for the design of systems that concurrently handle data
       at multiple sensitivity levels (without leaking information
       between secret and confidential).

   The following sysctl tunables are available for the configuration
   of special services and interfaces:

     * security.mac.mls.enabled is used to enable/disable the MLS
       policy.

     * security.mac.mls.ptys_equal will label all pty(4) devices as
       mls/equal during creation.

     * security.mac.mls.revocation_enabled is used to revoke access
       to objects after their label changes to a label of a lower
       grade.

     * security.mac.mls.max_compartments is used to set the maximum
       number of compartment levels with objects; basically the
       maximum compartment number allowed on a system.

   To manipulate the MLS labels, the setfmac(8) command has been
   provided. To assign a label to an object, issue the following
   command:

 # setfmac mls/5 test

   To get the MLS label for the file test issue the following
   command:

 # getfmac test

   This is a summary of the MLS policy's features. Another approach
   is to create a master policy file in /etc which specifies the MLS
   policy information and to feed that file into the setfmac command.
   This method will be explained after all policies are covered.

   Observations: an object with lower clearance is unable to observe
   higher clearance processes. A basic policy would be to enforce
   mls/high on everything not to be read, even if it needs to be
   written. Enforce mls/low on everything not to be written, even if
   it needs to be read. And finally enforce mls/equal on the rest.
   All users marked insecure should be set at mls/low.

     --------------------------------------------------------------

16.12. The MAC Biba Module

   Module name: mac_biba.ko

   Kernel configuration line: options MAC_BIBA

   Boot option: mac_biba_load="YES"

   The mac_biba(4) module loads the MAC Biba policy. This policy
   works much like that of the MLS policy with the exception that the
   rules for information flow are slightly reversed. This is said to
   prevent the downward flow of sensitive information whereas the MLS
   policy prevents the upward flow of sensitive information; thus,
   much of this section can apply to both policies.

   In Biba environments, an !S:integrity!" label is set on each
   subject or object. These labels are made up of hierarchal grades,
   and non-hierarchal components. As an object's or subject's grade
   ascends, so does its integrity.

   Supported labels are biba/low, biba/equal, and biba/high; as
   explained below:

     * The biba/low label is considered the lowest integrity an
       object or subject may have. Setting this on objects or
       subjects will block their write access to objects or subjects
       marked high. They still have read access though.

     * The biba/equal label should only be placed on objects
       considered to be exempt from the policy.

     * The biba/high label will permit writing to objects set at a
       lower label, but not permit reading that object. It is
       recommended that this label be placed on objects that affect
       the integrity of the entire system.

   Biba provides for:

     * Hierarchical integrity level with a set of non hierarchical
       integrity categories;

     * Fixed rules: no write up, no read down (opposite of MLS). A
       subject can have write access to objects on its own level or
       below, but not above. Similarly, a subject can have read
       access to objects on its own level or above, but not below;

     * Integrity (preventing inappropriate modification of data);

     * Integrity levels (instead of MLS sensitivity levels).

   The following sysctl tunables can be used to manipulate the Biba
   policy.

     * security.mac.biba.enabled may be used to enable/disable
       enforcement of the Biba policy on the target machine.

     * security.mac.biba.ptys_equal may be used to disable the Biba
       policy on pty(4) devices.

     * security.mac.biba.revocation_enabled will force the revocation
       of access to objects if the label is changed to dominate the
       subject.

   To access the Biba policy setting on system objects, use the
   setfmac and getfmac commands:

 # setfmac biba/low test
 # getfmac test
 test: biba/low

   Observations: a lower integrity subject is unable to write to a
   higher integrity subject; a higher integrity subject cannot
   observe or read a lower integrity object.

     --------------------------------------------------------------

16.13. The MAC LOMAC Module

   Module name: mac_lomac.ko

   Kernel configuration line: options MAC_LOMAC

   Boot option: mac_lomac_load="YES"

   Unlike the MAC Biba policy, the mac_lomac(4) policy permits access
   to lower integrity objects only after decreasing the integrity
   level to not disrupt any integrity rules.

   The MAC version of the Low-watermark integrity policy, not to be
   confused with the older lomac(4) implementation, works almost
   identically to Biba, but with the exception of using floating
   labels to support subject demotion via an auxiliary grade
   compartment. This secondary compartment takes the form of
   [auxgrade]. When assigning a lomac policy with an auxiliary grade,
   it should look a little bit like: lomac/10[2] where the number two
   (2) is the auxiliary grade.

   The MAC LOMAC policy relies on the ubiquitous labeling of all
   system objects with integrity labels, permitting subjects to read
   from low integrity objects and then downgrading the label on the
   subject to prevent future writes to high integrity objects. This
   is the [auxgrade] option discussed above, thus the policy may
   provide for greater compatibility and require less initial
   configuration than Biba.

     --------------------------------------------------------------

  16.13.1. Examples

   Like the Biba and MLS policies; the setfmac and setpmac utilities
   may be used to place labels on system objects:

 # setfmac /usr/home/trhodes lomac/high[low]
 # getfmac /usr/home/trhodes lomac/high[low]

   Notice the auxiliary grade here is low, this is a feature provided
   only by the MAC LOMAC policy.

     --------------------------------------------------------------

16.14. Implementing a Secure Environment with MAC

   The following demonstration will implement a secure environment
   using various MAC modules with properly configured policies. This
   is only a test and should not be considered the complete answer to
   everyone's security woes. Just implementing a policy and ignoring
   it never works and could be disastrous in a production
   environment.

   Before beginning this process, the multilabel option must be set
   on each file system as stated at the beginning of this chapter.
   Not doing so will result in errors.

     --------------------------------------------------------------

  16.14.1. Create an insecure User Class

   Begin the procedure by adding the following user class to the
   /etc/login.conf file:

 insecure:\
 :copyright=/etc/COPYRIGHT:\
 :welcome=/etc/motd:\
 :setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\
 :path=~/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin
 :manpath=/usr/share/man /usr/local/man:\
 :nologin=/usr/sbin/nologin:\
 :cputime=1h30m:\
 :datasize=8M:\
 :vmemoryuse=100M:\
 :stacksize=2M:\
 :memorylocked=4M:\
 :memoryuse=8M:\
 :filesize=8M:\
 :coredumpsize=8M:\
 :openfiles=24:\
 :maxproc=32:\
 :priority=0:\
 :requirehome:\
 :passwordtime=91d:\
 :umask=022:\
 :ignoretime@:\
 :label=partition/13,mls/5:

   And adding the following line to the default user class:

 :label=mls/equal,biba/equal,partition/15:

   Once this is completed, the following command must be issued to
   rebuild the database:

 # cap_mkdb /etc/login.conf

     --------------------------------------------------------------

  16.14.2. Boot with the Correct Modules

   Add the following lines to /boot/loader.conf so the required
   modules will load during system initialization:

 mac_biba_load="YES"
 mac_mls_load="YES"
 mac_seeotheruids_load="YES"
 mac_partition_load="YES"

     --------------------------------------------------------------

  16.14.3. Set All Users to Insecure

   All user accounts that are not root or system users will now
   require a login class. The login class is required otherwise users
   will be refused access to common commands such as vi(1). The
   following sh script should do the trick:

 # for x in `awk -F: '($3 >= 1001) && ($3 != 65534) { print $1 }' \
         /etc/passwd`; do pw usermod $x -L insecure; done;

   The cap_mkdb command will need to be run on /etc/master.passwd
   after this change.

     --------------------------------------------------------------

  16.14.4. Complete the Configuration

   A contexts file should now be created; the following example was
   taken from Robert Watson's example policy and should be placed in
   /etc/policy.contexts.

 # This is the default BIBA/MLS policy for this system.

 .*                              biba/high,mls/high
 /sbin/dhclient                  biba/high(low),mls/high(low)
 /dev(/.*)?                      biba/equal,mls/equal
 # This is not an exhaustive list of all "privileged" devices.
 /dev/mdctl                      biba/high,mls/high
 /dev/pci                        biba/high,mls/high
 /dev/k?mem                      biba/high,mls/high
 /dev/io                         biba/high,mls/high
 /dev/agp.*                      biba/high,mls/high
 (/var)?/tmp(/.*)?               biba/equal,mls/equal
 /tmp/\.X11-unix                 biba/high(equal),mls/high(equal)
 /tmp/\.X11-unix/.*              biba/equal,mls/equal
 /proc(/.*)?                     biba/equal,mls/equal
 /mnt.*                          biba/low,mls/low
 (/usr)?/home                    biba/high(low),mls/high(low)
 (/usr)?/home/.*                 biba/low,mls/low
 /var/mail(/.*)?                 biba/low,mls/low
 /var/spool/mqueue(/.*)?         biba/low,mls/low
 (/mnt)?/cdrom(/.*)?             biba/high,mls/high
 (/usr)?/home/(ftp|samba)(/.*)?  biba/high,mls/high
 /var/log/sendmail\.st           biba/low,mls/low
 /var/run/utmp                   biba/equal,mls/equal
 /var/log/(lastlog|wtmp)         biba/equal,mls/equal

   This policy will enforce security by setting restrictions on both
   the downward and upward flow of information with regards to the
   directories and utilities listed on the left.

   This can now be read into our system by issuing the following
   command:

 # setfsmac -ef /etc/policy.contexts /
 # setfsmac -ef /etc/policy.contexts /usr

     -a`: The above file system layout may be different depending on
     environment.

   The /etc/mac.conf file requires the following modifications in the
   main section:

 default_labels file ?biba,?mls
 default_labels ifnet ?biba,?mls
 default_labels process ?biba,?mls,?partition
 default_labels socket ?biba,?mls

     --------------------------------------------------------------

  16.14.5. Testing the Configuration

   Add a user with the adduser command and place that user in the
   insecure class for these tests.

   The examples below will show a mix of root and regular user tests;
   use the prompt to distinguish between the two.

     --------------------------------------------------------------

    16.14.5.1. Basic Labeling Tests

 % getpmac
 biba/15(15-15),mls/15(15-15),partition/15
 # setpmac partition/15,mls/equal top

     -a`: The top process will be killed before we start another top
     process.

     --------------------------------------------------------------

    16.14.5.2. MAC Seeotheruids Tests

 % ps Zax
 biba/15(15-15),mls/15(15-15),partition/15  1096 #C:  S      0:00.03 -su (bash)
 biba/15(15-15),mls/15(15-15),partition/15  1101 #C:  R+     0:00.01 ps Zax

   We should not be permitted to see any processes owned by other
   users.

     --------------------------------------------------------------

    16.14.5.3. MAC Partition Test

   Disable the MAC seeotheruids policy for the rest of these tests:

 # sysctl security.mac.seeotheruids.enabled=0
 % ps Zax
 LABEL                                                   PID  TT  STAT      TIME COMMAND
   biba/equal(low-high),mls/equal(low-high),partition/15  1122 #C:  S+     0:00.02 top
   biba/15(15-15),mls/15(15-15),partition/15              1096 #C:  S      0:00.05 -su (bash)
   biba/15(15-15),mls/15(15-15),partition/15              1123 #C:  R+     0:00.01 ps Zax

   All users should be permitted to see every process in their
   partition.

     --------------------------------------------------------------

    16.14.5.4. Testing Biba and MLS Labels

 # setpmac partition/15,mls/equal,biba/high\(high-high\) top
 % ps Zax
 LABEL                                                   PID  TT  STAT    TIME   COMMAND
   biba/high(high-high),mls/equal(low-high),partition/15   1251 #C:  S+     0:00.02 top
   biba/15(15-15),mls/15(15-15),partition/15               1096 #C:  S      0:00.06 -su (bash)
   biba/15(15-15),mls/15(15-15),partition/15               1157 #C:  R+     0:00.00 ps Zax

   The Biba policy allows us to read higher-labeled objects.

 # setpmac partition/15,mls/equal,biba/low top
 % ps Zax
 LABEL                                       PID  TT  STAT      TIME COMMAND
   biba/15(15-15),mls/15(15-15),partition/15  1096 #C:  S      0:00.07 -su (bash)
   biba/15(15-15),mls/15(15-15),partition/15  1226 #C:  R+     0:00.01 ps Zax

   The Biba policy does not allow lower-labeled objects to be read;
   however, MLS does.

 % ifconfig bge0 | grep maclabel
 maclabel biba/low(low-low),mls/low(low-low)
 % ping -c 1 192.0.34.166
 PING 192.0.34.166 (192.0.34.166): 56 data bytes
 ping: sendto: Permission denied

   Users are unable to ping example.com, or any domain for that
   matter.

   To prevent this error from occurring, run the following command:

 # sysctl security.mac.biba.trust_all_interfaces=1

   This sets the default interface label to insecure mode, so the
   default Biba policy label will not be enforced.

 # ifconfig bge0 maclabel biba/equal\(low-high\),mls/equal\(low-high\)
 % ping -c 1 192.0.34.166
 PING 192.0.34.166 (192.0.34.166): 56 data bytes
 64 bytes from 192.0.34.166: icmp_seq=0 ttl=50 time=204.455 ms
 --- 192.0.34.166 ping statistics ---
 1 packets transmitted, 1 packets received, 0% packet loss
 round-trip min/avg/max/stddev = 204.455/204.455/204.455/0.000 ms

   By setting a more correct label, we can issue ping requests.

   Now to create a few files for some read and write testing
   procedures:

 # touch test1 test2 test3 test4 test5
 # getfmac test1
 test1: biba/equal,mls/equal
 # setfmac biba/low test1 test2; setfmac biba/high test4 test5; \
   setfmac mls/low test1 test3; setfmac mls/high test2 test4
 # setfmac mls/equal,biba/equal test3 && getfmac test?
 test1: biba/low,mls/low
 test2: biba/low,mls/high
 test3: biba/equal,mls/equal
 test4: biba/high,mls/high
 test5: biba/high,mls/equal
 # chown testuser:testuser test?

   All of these files should now be owned by our testuser user. And
   now for some read tests:

 % ls
 test1   test2   test3   test4   test5
 % ls test?
 ls: test1: Permission denied
 ls: test2: Permission denied
 ls: test4: Permission denied
 test3   test5

   We should not be permitted to observe pairs; e.g.:
   (biba/low,mls/low), (biba/low,mls/high) and (biba/high,mls/high).
   And of course, read access should be denied. Now for some write
   tests:

 % for i in `echo test*`; do echo 1 > $i; done
 -su: test1: Permission denied
 -su: test4: Permission denied
 -su: test5: Permission denied

   Like with the read tests, write access should not be permitted to
   write pairs; e.g.: (biba/low,mls/high) and (biba/equal,mls/equal).

 % cat test?
 cat: test1: Permission denied
 cat: test2: Permission denied
 1
 cat: test4: Permission denied

   And now as root:

 # cat test2
 1

     --------------------------------------------------------------

16.15. Another Example: Using MAC to Constrain a Web Server

   A separate location for the web data which users must be capable
   of accessing will be appointed. This will permit biba/high
   processes access rights to the web data.

   Begin by creating a directory to store the web data in:

 # mkdir /usr/home/cvs

   Now initialize it with cvs:

 # cvs -d /usr/home/cvs init

   The first goal is to enable the biba policy, thus the
   mac_biba_enable="YES" should be placed in /boot/loader.conf. This
   assumes that support for MAC has been enabled in the kernel.

   From this point on everything in the system should be set at
   biba/high by default.

   The following modification must be made to the login.conf file,
   under the default user class:

 :ignoretime@:\
         :umask=022:\
         :label=biba/high:

   Every user should now be placed in the default class; a command
   such as:

 # for x in `awk -F: '($3 >= 1001) && ($3 != 65534) { print $1 }' \
         /etc/passwd`; do pw usermod $x -L default; done;

   will accomplish this task in a few moments.

   Now create another class, web, a copy of default, with the label
   setting of biba/low.

   Create a user who will be used to work with the main web data
   stored in a cvs repository. This user must be placed in our new
   login class, web.

   Since the default is biba/high everywhere, the repository will be
   the same. The web data must also be the same for users to have
   read/write access to it; however, since our web server will be
   serving data that biba/high users must access, we will need to
   downgrade the data as a whole.

   The perfect tools for this are sh(1) and cron(8) and are already
   provided in FreeBSD. The following script should do everything we
   want:

 PATH=/bin:/usr/bin:/usr/local/bin; export PATH;
 CVSROOT=/home/repo; export CVSROOT;
 cd /home/web;
 cvs -qR checkout -P htdocs;
 exit;

     -a`: In many cases the cvs Id tags must be placed into the web
     site data files.

   This script may now be placed into web's home directory and the
   following crontab(1) entry added:

 # Check out the web data as biba/low every twelve hours:
 0       */12       *       *       *       web    /home/web/checkout.sh

   This will check out the HTML sources every twelve hours on the
   machine.

   The default startup method for the web server must also be
   modified to start the process as biba/low. This can be done by
   making the following modification to the
   /usr/local/etc/rc.d/apache.sh script:

 command="setpmac biba/low /usr/local/sbin/httpd"

   The Apache configuration must be altered to work with the biba/low
   policy. In this case the software must be configured to append to
   the log files in a directory set at biba/low or else !S:access
   denied!" errors will be returned.

     -a`: Following this example requires that the docroot directive
     be set to /home/web/htdocs; otherwise, Apache will fail when
     trying to locate the directory to serve documents from.

   Other configuration variables must be altered as well, including
   the PID file, Scoreboardfile, DocumentRoot, log file locations, or
   any other variable which requires write access. When using biba,
   all write access will be denied to the server in areas not set at
   biba/low.

     --------------------------------------------------------------

16.16. Troubleshooting the MAC Framework

   During the development stage, a few users reported problems with
   normal configuration. Some of these problems are listed below:

     --------------------------------------------------------------

  16.16.1. The multilabel option cannot be enabled on /

   The multilabel flag does not stay enabled on my root (/)
   partition!

   It seems that one out of every fifty users has this problem,
   indeed, we had this problem during our initial configuration.
   Further observation of this so called !S:bug!" has lead me to
   believe that it is a result of either incorrect documentation or
   misinterpretation of the documentation. Regardless of why it
   happened, the following steps may be taken to resolve it:

    1. Edit /etc/fstab and set the root partition at ro for
       read-only.

    2. Reboot into single user mode.

    3. Run tunefs -l enable on /.

    4. Reboot the system into normal mode.

    5. Run mount -urw / and change the ro back to rw in /etc/fstab
       and reboot the system again.

    6. Double-check the output from the mount to ensure that
       multilabel has been properly set on the root file system.

     --------------------------------------------------------------

  16.16.2. Cannot start a X11 server after MAC

   After establishing a secure environment with MAC, I am no longer
   able to start X!

   This could be caused by the MAC partition policy or by a
   mislabeling in one of the MAC labeling policies. To debug, try the
   following:

    1. Check the error message; if the user is in the insecure class,
       the partition policy may be the culprit. Try setting the
       user's class back to the default class and rebuild the
       database with the cap_mkdb command. If this does not alleviate
       the problem, go to step two.

    2. Double-check the label policies. Ensure that the policies are
       set correctly for the user in question, the X11 application,
       and the /dev entries.

    3. If neither of these resolve the problem, send the error
       message and a description of your environment to the
       TrustedBSD discussion lists located at the TrustedBSD website
       or to the FreeBSD general questions P:l>> 1/4 1/2 * 3/4A
       mailing list.

     --------------------------------------------------------------

  16.16.3. Error: _secure_path(3) cannot stat .login_conf

   When I attempt to switch from the root to another user in the
   system, the error message !S:_secure_path: unable to state
   .login_conf!".

   This message is usually shown when the user has a higher label
   setting then that of the user whom they are attempting to become.
   For instance a user on the system, joe, has a default label of
   biba/low. The root user, who has a label of biba/high, cannot view
   joe's home directory. This will happen regardless if root has used
   the su command to become joe, or not. In this scenario, the Biba
   integrity model will not permit root to view objects set at a
   lower integrity level.

     --------------------------------------------------------------

  16.16.4. The root username is broken!

   In normal or even single user mode, the root is not recognized.
   The whoami command returns 0 (zero) and su returns !S:who are
   you?!". What could be going on?

   This can happen if a labeling policy has been disabled, either by
   a sysctl(8) or the policy module was unloaded. If the policy is
   being disabled or has been temporarily disabled, then the login
   capabilities database needs to be reconfigured with the label
   option being removed. Double check the login.conf file to ensure
   that all label options have been removed and rebuild the database
   with the cap_mkdb command.

     --------------------------------------------------------------

                    ^3^1 17. Security Event Auditing

   Written by Tom Rhodes.

17.1. Synopsis

   The FreeBSD 7-CURRENT development branch includes support for
   Event Auditing based on the POSIX.1e draft and Sun's published BSM
   API and file format. Event auditing permits the selective logging
   of security-relevant system events for the purposes of post-mortem
   analysis, system monitoring, and intrusion detection. After some
   settling time in FreeBSD 7-CURRENT, this support will be merged to
   FreeBSD 6-STABLE and appear in subsequent releases.

     A:uS:iThe audit facility in FreeBSD is considered experimental,
     and production deployment should occur only after careful
     consideration of the risks of deploying experimental software.

   This chapter will focus mainly on the installation and
   configuration of Event Auditing. Explanation of audit policies,
   and an example configuration will be provided for the convenience
   of the reader.

   After reading this chapter, you will know:

     * What Event Auditing is and how it works.

     * How to configure Event Auditing on FreeBSD for users and
       processes.

   Before reading this chapter, you should:

     * Understand UNIX and FreeBSD basics (uU 3 ^3^1).

     * Be familiar with the basics of kernel
       configuration/compilation (uU 8 ^3^1).

     * Have some familiarity with security and how it pertains to
       FreeBSD (uU 14 ^3^1).

     A:uS:iEvent auditing can generate a great deal of log file data,
     exceeding gigabytes a week in some configurations. An
     administrator should read this chapter in its entirety to avoid
     possible self-inflicted DoS attacks due to improper
     configuration.

   The implementation of Event Auditing in FreeBSD is similar to that
   of the Sun(TM) Basic Security Module, or BSM library. Thus, the
   configuration is almost completely interchangeable with Solaris
   and Mac OS X/Darwin operating systems.

     --------------------------------------------------------------

17.2. Key Terms - Words to Know

   Before reading this chapter, a few key terms must be explained.
   This is intended to clear up any confusion that may occur and to
   avoid the abrupt introduction of new terms and information.

     * event: An auditable event is an event that can be logged using
       the audit subsystem. The administrator can configure which
       events will be audited. Examples of security-relevant events
       include the creation of a file, the building of a network
       connection, or the logging in of a user. Events are either
       !S:attributable!", meaning that they can be traced back to a
       user authentication, or !S:non-attributable!". Examples of
       non-attributable events are any events that occur before
       authentication has succeeded in the login process, such as
       failed authentication attempts.

     * class: Events may be assigned to one or more classes, usually
       based on the general category of the events, such as !S:file
       creation!", !S:file access!", or !S:network!". Login and
       logout events are assigned to the lo class. The use of classes
       allows the administrator to specify high level auditing rules
       without having to specify whether each individual auditable
       operation will be logged.

     * record: A record is a log entry describing a security event.
       Records typically have a record event type, information on the
       subject (user) associated with the event, time information,
       information on any objects, such as files, and information on
       whether the event corresponded to a successful operation.

     * trail: An audit trail, or log file, consists of a series of
       audit records describing security events. Typically, trails
       are in roughly chronological order with respect to the time
       events completed. Only authorized processes are allowed to
       commit records to the audit trail.

     * prefix: A prefix is considered to be the configuration element
       used to toggle auditing for success and failed events.

     --------------------------------------------------------------

17.3. Installing Audit Support

   Support for Event Auditing is installed with the normal
   installworld process. An administrator may confirm this by viewing
   the contents of /etc/security. Files beginning with the word audit
   should be present. For example, audit_event.

   In-kernel support for the framework must also exist. This may be
   done by adding the following lines to the local kernel
   configuration file:

 options AUDIT

   Rebuild and reinstall the kernel via the normal process explained
   in uU 8 ^3^1.

   Once completed, enable the audit daemon by adding the following
   line to rc.conf(5):

 auditd_enable="YES"

   Functionality not provided by the default may be added here with
   the auditd_flags option.

     --------------------------------------------------------------

17.4. Audit Configuration

   All configuration files for security audit are found in
   /etc/security. The following files must be present before the
   audit daemon is started:

     * audit_class - Contains the definitions of the audit classes.

     * audit_control - Controls aspects of the audit subsystem, such
       as default audit classes, minimum disk space to leave on the
       audit log volume, etc.

     * audit_event - Defines the kernel audit events. These map,
       mostly, to system calls.

     * audit_user - The events to audit for individual users. Users
       not appearing here will be subject to the default
       configuration in the control configuration file.

     * audit_warn - A shell script used by auditd to generate warning
       messages in exceptional situations, such as when space for
       audit records is running low.

     --------------------------------------------------------------

  17.4.1. Audit File Syntax

   The configuration file syntax is rather arcane, albeit easy to
   work with. One thing an administrator must be leery about is
   overriding system defaults. This could create potential openings
   for audit data to not be collected properly.

   The audit subsystem will accept both the short name and long name
   with regards to configuration syntax. A syntax map has been
   included below.

   The following list contains all supported audit classes:

     * all - all - All audit flags set.

     * ad - administrative - Administrative actions performed on the
       system as a whole.

     * ap - application - Application defined action.

     * cl - file_close - Audit calls to the close system call.

     * ex - exec - Audit program or utility execution.

     * fa - file_attr_acc - Audit the access of object attributes
       such as stat(1), pathconf(2) and similar events.

     * fc - file_creation - Audit events where a file is created as a
       result.

     * fd - file_deletion - Audit events where file deletion occurs.

     * fm - file_attr_mod - Audit events where file attribute
       modification occurs, such as chown(8), chflags(1), flock(2),
       etc.

     * fr - file_read - Audit events in which data is read, files are
       opened for reading, etc.

     * fw - file_write - Audit events in which data is written, files
       are written or modified, etc.

     * io - ioctl - Audit use of the ioctl(2) system call.

     * ip - ipc - Audit various forms of Inter-Process Communication,
       including POSIX pipes and System V IPC operations.

     * lo - login_logout - Audit login(1) and logout(1) events
       occurring on the system.

     * na - non_attrib - Audit non-attributable events.

     * no - no_class - Null class used to disable event auditing.

     * nt - network - Audit events related to network actions, such
       as connect(2) and accept(2).

     * ot - other - Audit miscellaneous events.

     * pc - process - Audit process operations, such as exec(3) and
       exit(3).

   Following is a list of all supported audit prefixes:

     * none - Audit both the success or failure of an event. For
       example, just listing a class will result in the auditing of
       both success and failure.

     * + - Audit successful events only.

     * - - Audit failed events only.

     A:uS:iUsing the all class with either the positive or negative
     prefix can generate a large amount of data at an extremely rapid
     rate.

   Extra prefixes used to modify the default configuration values:

     * ^- - Disable auditing of failed events.

     * ^+ - Enable auditing of successful events.

     * ^ - Disable auditing of both successful and failed events.

     --------------------------------------------------------------

  17.4.2. Configuration Files

   In most cases, administrators will need to modify only two files
   when configuring the audit system: audit_control and audit_user.
   The first controls system-wide audit paramaters and defaults for
   both attributable and non-attributable events. The second may be
   used to tune the level and nature of auditing for individual
   users.

     --------------------------------------------------------------

    17.4.2.1. The audit_control File

   The audit_control file contains some basic defaults that the
   administrator may wish to modify. Perhaps even set some new ones.
   Viewing the contents of this file, we see the following:

 dir:/var/audit
 flags:lo
 minfree:20
 naflags:lo

   The dir option is used to set the default directory where audit
   logs are stored. Audit is frequently configured so that audit logs
   are stored on a dedicated file system, so as to prevent
   interference between the audit subsystem and other subsystems when
   file systems become full.

   The flags option is used to set the system-wide defaults. The
   current setting, lo configures the auditing of all login(1) and
   logout(1) actions. A more complex example,
   lo,ad,-all,^-fa,^-fc,^-cl audits all system login(1) and logout(1)
   actions, all administrator actions, all failed events in the
   system, and finally disables auditing of failed attempts for fa,
   fc, and cl. Even though the -all turned on the auditing of all
   failed attempts, the ^- prefix will override that for the latter
   options.

   Notice that the previous paragraph shows the file is read from
   left to right. As such, values further on the right side may
   override a previous value specified to its left.

   The minfree option defines the minimum percentage of free space
   for audit file systems. This relates to the file system where
   audit logs are stored. For example, if the dir specifies
   /var/audit and minfree is set to twenty (20), warning messages
   will be generated when the /var file system grows to eighty (80)
   percent full.

   The naflags option specifies audit classes to be audited for
   non-attributed events !X!X that is, events for which there is no
   authenticated user.

     --------------------------------------------------------------

    17.4.2.2. The audit_user File

   The audit_user file permits the administrator to determine which
   classes of audit events should be logged for which system users.

   The following is the defaults currently placed in the audit_user
   file:

 root:lo:no
 audit:fc:no

   Notice how the default is to audit all cases of login/logout and
   disable auditing of all other actions for root. This configuration
   also audits all file creation and disables all other auditing for
   the audit user. While event auditing does not require a special
   user exist, some configurations, specifically environments making
   use of MAC, may require it.

     --------------------------------------------------------------

17.5. Event Audit Administration

   Events written by the kernel audit subsystem cannot be altered or
   read in plain text. Data is stored and accessed in a method
   similar to that of ktrace(1) and kdump(1), that is, they may only
   be viewed by dumping them using the praudit command; audit trails
   may be reduced using the auditreduce command, which selects
   records from an audit trail based on properties of interest, such
   as the user, time of the event, and type of operation.

   For example, the praudit utility will dump the entire contents of
   a specified audit log in plain text. To dump an audit log in its
   entirety, use:

 # praudit /var/audit/AUDITFILE

   Where AUDITFILE is the audit log of viewing choice. Since audit
   logs may contain enormous amounts of data, an administrator may
   prefer to select records for specific users. This is made possible
   with the following command, where trhodes is the user of choice:

 # auditreduce -e trhodes /var/audit/AUDITFILE | praudit

   This will select all audit records produced by the user trhodes
   stored in the AUDITFILE file.

   There are several other options available for reading audit
   records, see the aforementioned command's manual pages for a more
   in depth explanation.

     --------------------------------------------------------------

  17.5.1. Rotating Audit Log Files

   Due to log reliability requirements, audit trails are written to
   only by the kernel, and managed only by auditd. Administrators
   should not attempt to use newsyslog.conf(5) or other tools to
   directly rotate audit logs. Instead, the audit management tool
   should be used to shut down auditing, reconfigure the audit
   system, and perform log rotation. The following command causes the
   audit daemon to create a new audit log and signal the kernel to
   switch to using the new log. The old log will be terminated and
   renamed, at which point it may then be manipulated by the
   administrator.

 # audit -n

     A:uS:iIf the auditd daemon is not currently running, the
     previous command will fail and an error message will be
     produced.

   Adding the following line to /etc/crontab will force the rotation
   every twelve hours from cron(8):

 *     */12       *       *       *       root    /usr/sbin/audit -n

   The change will take effect once you have saved the new
   /etc/crontab.

     --------------------------------------------------------------

  17.5.2. Delegating Audit Review Rights

   By default, only the root user has the right to read system audit
   logs. However, that right may be delegated to members of the audit
   group, as the audit directory and audit trail files are assigned
   to that group, and made group-readable. As the ability to track
   audit log contents provides significant insight into the behavior
   of users and processes, it is recommended that the delegation of
   audit review rights be performed with caution.

     --------------------------------------------------------------

                       ^3^1 18. Ax|s^3]^3AE 1/2g

18.1. .S:z

   YEN>>^3^1^2[>>\|p|o|b FreeBSD CURU"IYENI-oD-CURu,E,m [15] YEN]S:t
   memory-backed disk (YENIDEGO
   3/4D-AAeS:@NOTDEG-oI-oD-"IYENI)!B,o-oo,o"IYENI-a-o-oI-oD-!B 
   1/4D-.C, SCSI/IDE -oI-oD-!BUSB CURP:+--a-o^3]^3AEuYEN!C

   3/4\AA-aYEN>>^3^1<<a!A+-z,E 3/4C,.|!G

     * FreeBSD |p|o'yz,e(R)AE|b-oI-oD-CURW-a-o^1-oCURA+-!S:I
       (partition (c)M slices)!C

     * |p|o|b"t^2ICURWYEN[CURJ-oI-oD-

     * |p|o^3](c)w FreeBSD "O"IYENI USB ,E,m!C

     * |p|o^3](c)wueAAAE(R) *"t^2I (virtual file systems), "O|p
       memory disks (YENIDEGO 3/4D-AAeS:@NOTDEG-oI-oD-"IYENI)!C

     * |p|oYENI quota "O"i-oI-oD--aAAP:!-a-o"IYENI!C

     * |p|o^1i-oI-oD-YEN[+-KYENHA^3YENIS:d-A>>!C

     * |p|o|b FreeBSD CURU<<O/YENss!B?N?y CD (c)M DVD!C

     * |U-oO/CUR-L-|P-a-o^3AEYEN-:^3]^3AE!C

     * |p|o"IYENI FreeBSD '-L-"N-a-o^3AEYEN-:CURu"a!C

     * |p|o^3AEYEN-:"`i^3n-oD-!C

     * CURDEG>>oNOTO snapshots !AYENB|p|o|^3(R)A:^2v|a"IYENICURS:!C

   |b 3/4\AA-aCURS:<<e!A+-zA^3,O!G

     * -a 3/4^1D|p|o^3](c)w!B|w,E.s-a-o FreeBSD kernel!C (uU 8 ^3^1).

     --------------------------------------------------------------

18.2. ,E,m|W-oU

   CURU+-NOTO FreeBSD
   CURa:'(c)-a-oAx|s'CAAe|C-ai!ACURIYEN|I^1iA^3-a-o,E,m|W-oU!C

   -ai(R)ae 18-1. (c)R|W^3W<<h

            ,E,mAth<<NOT                       ,E,m|W-oU              
   IDE -oI-oD- 3/4-:               ad                                 
   IDE YENu-oD- 3/4-:              acd                                
   SCSI -oI-oD- 3/4-:(c)M USB -oD- da                                 
   SCSI YENu-oD- 3/4-:             cd                                 
   <<D 1/4D-.C,^3W(R)aeYENu-oD-    Mitsumi YENu-oD- 3/4-:YENI mcd!A   
   3/4-:                           Sony YENu-oD- 3/4-:YENI scd!C      
   ^3n-oD- 3/4-:                   fd                                 
   SCSI -oD-+-a 3/4-:              sa                                 
   IDE -oD-+-a 3/4-:               ast                                
   Flash -oI-oD- 3/4-:             DiskOnChip(R) Flash -oI-oD-        
                                   3/4-:YENI fla                      
                                   Adaptec AdvancedRAID YENIaacd!A    
                                   Mylex YENI mlxd (c)M mlyd!A AMI    
   RAID -oI-oD- 3/4-:              MegaRAID YENI amrd!A Compaq Smart  
                                   RAID YENI idad!A 3ware(R) RAID     
                                   YENI twed!C                        

     --------------------------------------------------------------

18.3. .s 1/4W-oI-oD-

   Originally contributed by David O'Brien.

   DEG^2^3]S:UI.Q.s 1/4W SCSI
   -oI-oD-"`iCUR@>>O`iYENyYENu|^3CUR@Au-oI-oD--a-o 3/4-: 3/4^1CURW!A
   -oYENy+-N^1q,-L-Ao:
   3/4-:!A"I>>s^3yDEGO-a-o<<u:YENU:+-N-oI-oD-,ECURWYENh!A ,O^2O-a-o
   3/4THS:@CURe|! 1/2D-DEGN|O>>s^3yDEGO-a-o>>!(c)uCURaaYENo!C

   |w,E|n-oI-oD-<<a!AYENI root unCURJ"t^2I!A NOTYCUR@CURU
   /var/run/dmesg.boot YENH 1/2T>>{"t^2INOTOS:_S:`i"`i.s-oI-oD-!C
   A:~A:oeCUR~-a-o 1/2d"O!A.s 1/4W-a-o-oI-oD-.|NOTO da1!A
   DEG^2^3]S:UI.Q+-NYEN|+- 3/4,u:"`i /1 ^3oO|`i,m (|p-aG+-z.s
   1/4W-a-oNOTO IDE -oI-oD--a-o,U:!A 1/2D-YENI ad1)!C

   FreeBSD NOTDEGCURF|b IBM-PC NOTU(R)e^1q,-L-CURWDEGo|ae!A
   YEN^2P:.DEGt|X PC BIOS partition!A|]|^1(c)MP:C,^2I-a-o BSD
   partition |^3<<U:CURj-a-oCUR-L-|P!C |b PC
   ,I-oI-oD-^3I|hYENiYENH|^3YEN|uS: BIOS partition
   ,eDEGT(YENc,S:Y^3I|hYENiCURA^3I|"YEN|O
   partition)!C|p-aG^3oO-oI-oD-YEN'-oaYENth^3!AAy FreeBSD
   "IYENI!AYENi?i 3/4U: dedicated  1/4O|!!A CUR-L-uM-a-o,U: FreeBSD
   YEN^2P:.,m"(c)o"a:CURCURCUR@O PC BIOS partition CURCUR!C |b
   FreeBSD ,I!APC BIOS partition -oUNOTDEG slice!A
   ^3oNOTONOTDEGCURFCUR-L-n(c)MP:C,^2I-a-o BSD partition .d^2VCURF!C
   [16] CUR-L- 1/2 *NOTOS:^1YENthYENN FreeBSD
   "IYENI-a-o-oI-oD-!AAUNOTO|w,ECURF"a:YEN|S:@.~"t^2I-a-o-oI-oD-!A
   +-z^3-L-YENiYENH"IYENI slice!C^3o 1/4E-a-o|n^3BNOTO!A"a:YEN|<<D
   FreeBSD S:@.~"t^2I-a-o fdisk CURu"aYENiYENHP:P:S:Q 3/4THS:@!C

   |p-aG"IYENI slice!A^3oO.s 1/4W-a-o-oI-oD-.|NOTO
   /dev/da1s1e!CYENiYENH^3o 1/4E"O,NAA-aYEN|!GSCSI -oI-oD-!B unit
   number 1(^2A:CURGO SCSI -oI-oD-)!Bslice 1(^2A:CUR@O PC BIOS
   partition)!B CURI e BSD partition!C|b dedicated  1/4O|!-a-o,U:!A
   .s-oI-oD-<<hNOTO /dev/da1e!C

   |]NOTDEG bsdlabel(8) NOTOYENI 32-bit  3/4a 1/4AE"OAx|s
   sector(-oIDEGI)  1/4AE!A |]|^1"iCUR@O-oI-oD-^3ICURjYENu-`a|^3
   2^32-1 O sector!AYENc,S:Y 2TB -a-o-aAAP:!!C |O fdisk(8)
   -a-o(R)ae|!(R)e^3\DEG_(c)l sector  1/2s,^1CUR-L-P:W^1L 2^32-1!A
   -ao/<< *CUR]CUR-L-P:W^1L 2^32-1!A|]|^1 partition
   ^3ICURj-aAAP:!NOTO 2TB!A|O-oI-oD-^3ICURjNOTO 4TB!C sunlabel(8)
   <<h"i partition ^3ICURjNOTO 2TB!A-oI-oD-^3I|hYENi|^3 8 O
   partition!A|]|^1^3ICURjNOTO 16TB!C
   |p-aGn"IYENIS:oCURj-a-o-oI-oD-!A 1/2D-"IYENI gpt(8)!C

     --------------------------------------------------------------

  18.3.1. "IYENI sysinstall(8)

    1. 3/4THS:@ Sysinstall

       ^3z^1L sysinstall -a-o?i^3aeCURP:+-!A
       YENiYENH>>'(c)o:NOTDEG-oI-oD-CURA^3I BIOS partition(slice)
       (c)M BSD patition!C YEN^2P:.YENH root "YEN-:"IYENI
       sysinstall!A n^1AYENI root unCURJ!An^1AYENI su CURA'<<"`i
       root!C DEGo|ae sysinstall <<a!A?i Configure!A|b FreeBSD
       Configuration Menu ,I^2 3/4"`i Fdisk ?iP:u!C

    2. fdisk Partition  1/2s?e 3/4^1

       |b fdisk ,I!A<<o:CURU A -aiYENU: 3/4aO-oI-oD-^3-L-u^1 FreeBSD
       "IYENI!C
       +-uuU.|'-L-YENU:+-z!yNOTOS:_nNOTU(R)e"a:YEN|-a-oS:@.~"t^2I!z!A|^u-a
       YES!C <<o: W .|+-N^3o"C,S:iAAU:YENssS:Y
       1/4gCURJ-oI-oD-!A|A<<o: q YENiYENHA-:P:} FDISK  1/2s?e 3/4^1!C
       +-uCURU"O.|DEGY+-zn+-N !S:Master Boot Record!"
       |w,E(c)o|o^3B!AYENN(c)o^2{|bNOTO.s
       1/4W-oI-oD-!A-aiYENU:S:@.~"t^2ICURw,g,E|bS:O-a-o-oI-oD-CURWCURF!A
       (c)OYENHYENiYENH?i None 'N|aeCURF!C

    3. Disk Label Editor(-oI-oD- Label  1/2s?e 3/4^1)

       +-uuU 1/2D-Ao:^3NOT sysinstall!A|A<<P:}CUR@|,!C
       .OuUCURWCUR@,`-a-o<<u:YENU:!ACUR-L-^1L^3o|,S:i?i Label P:iCURJ
       Disk Label Editor!A|b|^1+-zYENiYENH 1/2s?eP:C,^2I-a-o BSD
       partition!C CUR@O-oI-oD-((c)IuUCUR@O slice)
       ^3I|hYENiCURACURA|" 8 O BSD partition!A"IS:C,YENI a-h
       "O-aiYENU:!C |^3"C,|rYENA|^3-SS:O-a-o.N,q!Aa partition
       -aiYENU:^3oNOTO root partition((R)UCURA^3IDEGI!A/)!A
       |]|^1YENu|^3|w,E"t^2I-a-o-oI-oD-("O|pYENI"OP:}
       3/4-:-a-o-oI-oD-) |^3 a partition!C b partition
       -aiYENU:^3oNOTO swap
       partitions(YENae'<<CURA^3IDEGI)!A"CO-oI-oD-CURW^3-L-YENiYENH|^3
       swap!C c partition YENI"O-aiYENU: 3/4aO-oI-oD-(|p-aG"IYENI
       dedicated mode -a-o,U:)(c)I 3/4aO slice!C
       "a:YEN|-a-o|rYENA<<hYENI"O-aiYENU:'P:^3q-a-o BSD partition !C

       sysinstall -a-o Label editor(-oI-oD- Label  1/2s?e 3/4^1) DEG
       3/4|nYENI e "O-aiYENU:<<D root!BCUR]<<D swap -a-oCURA^3IDEGI
       [17] |b Label editor ,I!A<<o: C YENiYENH.s 1/4WCUR@OAE(R)
       *"t^2I(BSD label)!AYEN|.|DEGY+-z^3oNOTOCUR@O FS(file system
       !AAE(R) *"t^2I) (c)INOTO swap(YENae'<<CURA^3IDEGI)!A?i 3/4U:
       FS +-uuU?eCURJn+- 3/4,u:-a-o|`i,m("O|p /mnt)!C
       |p-aG"t^2I|w,ES:^1<<aCUR~.s 1/4W-oI-oD-!Asysinstall
       CUR-L-.|ADEG+-zS:a^3ouS:+- 3/4,u:,e(R)AEYEN[CURJ /etc/fstab!A
       (c)OYENH+- 3/4,u:-a-o|`i,mCUR-L-CURO<<n!C

       .i+-z.C,^3AE|n+-N.s-a-o label  1/4gCURJ-oI-oD-!B<<O/YENssAE(R)
       *"t^2I!A<<o: W S:YYENi!C|p-aGYENX^2{|bCURDEG>>o?u>>~!A
       sysinstall YENi-`auL-akADEG+-z+- 3/4,u:^3oO.sCURA^3IDEGI!C
       u^2S:o Label Editor!Bu^2S:o sysinstall 'N|aeCURF!C

    4. S:^1|"

       ^3I<<anDEGu-a-oNOTO 1/2s?e /etc/fstab!A YEN[CURJ+-z.s
       1/4W-a-oCURA^3IDEGI,eDEGT!C

     --------------------------------------------------------------

  18.3.2. "IYENI(c)RYENO|CCURu"a

    18.3.2.1. "IYENI Slices(BIOS partitions)

   ^3o-oO/
   1/4O|!-`aAAy+-z-a-o-oI-oD-CURA^3IDEGI>>P"a:YEN|S:@.~"t^2I-a-o
   fdisk CURu"a(c)MYEN|@^3B!A|]|^1S:UI<<O/A:^3+-z"IYENI slice 
   1/4O|!!C |p-aG+-zCUR@(c)wn"IYENI dedicated  1/4O|!!A
   +-z+-o|^3O|n^2zYENN!I [18]

 # dd if=/dev/zero of=/dev/da1 bs=1k count=1
 # fdisk -BI da1 # -a`i(c)l+-z-a-o-oI-oD-!C
 # bsdlabel -B -w -r da1s1 auto # <<O/YENss bsdlabel!C
 # bsdlabel -e da1s1 #  1/2s?e bsdlabel YENH.s 1/4W label!C
 # mkdir -p /1
 # newfs /dev/da1s1e # |p-aG+-z.s 1/4WCURF|hO label!A^1i"CO label <<AD-^3oO"BAEJ!C
 # mount /dev/da1s1e /1 # +- 3/4,u:^3o"C,.s label!C
 # vi /etc/fstab # |b /etc/fstab YEN[CURJ 3/4A.i-a-o,eDEGT!C

   |p-aG+-z.s 1/4W-a-oNOTO IDE -oI-oD-!A+-N da S:i|" ad S:YYENi
   [19]!C

     --------------------------------------------------------------

    18.3.2.2. Dedicated

   |p-aG+-zCUR-L-YEN'-oa+-N.s-oI-oD-YENI(c)o"a:YEN|-a-oS:@.~"t^2I!A
   +-zYENiYENH"IYENI dedicated  1/4O|!!C-a`.N!G Microsoft
   -a-oS:@.~"t^2I>>{CUR-L-+-o^3oO
   1/4O|!!ACUR-L-^1LCUR]CUR-L-.|YENh-}AaYEN|!F uM|O IBM -a-o OS/2
   'N"S"-o>>o|nCURssCURF!AYEN|.|YENh 1/2O
   3/4a(c)O|^3YEN|CUR-L->>{+-o-a-oCURA^3IDEGI [20]!C

 # dd if=/dev/zero of=/dev/da1 bs=1k count=1
 # bsdlabel -Brw da1 auto
 # bsdlabel -e da1                               # <<O/YENss `e' partition!C
 # newfs -d0 /dev/da1e
 # mkdir -p /1
 # vi /etc/fstab                         # .s 1/4WCUR@uS: /dev/da1e -a-o,eDEGT!C
 # mount /1

   YENtCUR@-oO/CURe-ak!G

 # dd if=/dev/zero of=/dev/da1 count=2
 # bsdlabel /dev/da1 | bsdlabel -BrR da1 /dev/stdin
 # newfs /dev/da1e
 # mkdir -p /1
 # vi /etc/fstab                                 # .s 1/4WCUR@uS: /dev/da1e -a-o,eDEGT!C
 # mount /1

     --------------------------------------------------------------

18.4. RAID

  18.4.1. ^3nAAe RAID

    18.4.1.1. ^3s+-u|!-oI-oD-,E,mAAXDEGEu{|!(CCD, Concatenated Disk
    Driver) ^3](c)w

   Original work by Christopher Shumway. Revised by Jim Brown.

   ^1iCURj(R)eP:qAx|s^3]^3AE|O"YEN!A^3IAo:Aa:-a-on-ACURDNOTO^3t<<
   *!BYENi 3/4a(c)ECURI>>u(R)ae!C
   uM|O^3oCURT-aI(c)^1(c)^1Ao/YENHYAAU!GS:O:^3tYENi
   3/4a-a-o^3]^3AE^3q+-`<<U:P:Q!F
   |ODEGS:C|"YEN>>^3q+-`CUR]A:eNOT^1CURF^3t<< *(c)IYENi 3/4a(c)E!C

   +-uCURU"OnCURP:^2D--a-o"t^2I!A>>u(R)aeNOTO^3I<<n-a-o|OP:q!A+-uCURU"ONOTO^3t<<
   *!A ^3I<<aCUR~NOTOYENi 3/4a(c)E!C
   P:P:S:C,|p|^1NOTO|]NOTDEG,e(R)AEP:C,?e-a-o^3t<< *^3I^2
   *"u"M(c)o-oo,o!A |O 3/4"-oTHYENi
   3/4a(c)ECURQCURA<<n!A<<o|^3A^2^3ae-a-o"uYENNCURe(R) *!G
   +-N,e(R)AES:^1 3/4a^3AEYEN-:(c)o CD-R CURCUR!C

   ?i 3/4U:CURj(R)eP:qAx|s^3]^3AECURe(R)
   *(R)E!A-oYENyn(c)w,q+-z-a-o>>Y"D!C |p-aG+-z<<uo/^3t<< *(c)IYENi
   3/4a(c)ENOTAE(c)o>>u(R)ae!A+-uCURU"O-a-oCURP:^2D-(R)-L-<<D+-z(c)O>>Y!C

     --------------------------------------------------------------

      18.4.1.1.1. |w,EuwAAe

   DEG-L-CURF"t^2I-oI-oD-YEN~!ACURU+-CURP:^2D--a-o CCD
   -oI-oD-DEG}|C+-N"IYENI"`iCURTAu 30GB!B 5400 RPM -a-o Western
   Digital IDE -oI-oD-!AYENH'-L-"NNOTu 90GB -a-oAx|s-aAAP:!!C
   ^3I^2z.Q-a-o+-!-apNOTO"CO-oI-oD-YENN?WYENss"IYENI-a-o+-AE
   1/2u^3s+-u?WYENss"IYENI-a-o IDE +-+-"i 3/4^1!A
   CUR-L-^1LNOTDEGCURFDEGS:C|"YEN>>!AS:QYENI jumper
   ^3](c)w-oI-oD-!A"I"CO IDE +-+-"i 3/4^1YENi^3s+-u
   CUR@OYEND-oI-oD-YEN[CUR@ODEGAE-oI-oD-!A|p|^1YENiCUR-L-YEN^2YEN[,EABYEN~-a-o
   IDE +-+-"i 3/4^1!C

   P:} 3/4-:<<a!ABIOS
   A^3,O^3](c)w|"|U<<DEG>>'u-oI-oD-!CS:o<<n-a-oNOTO FreeBSD A^3,O
   nDEG>>'u"`iYEN|I!G

 ad0: 19574MB <WDC WD205BA> [39770/16/63] at ata0-master UDMA33
 ad1: 29333MB <WDC WD307AA> [59598/16/63] at ata0-slave UDMA33
 ad2: 29333MB <WDC WD307AA> [59598/16/63] at ata1-master UDMA33
 ad3: 29333MB <WDC WD307AA> [59598/16/63] at ata1-slave UDMA33

     -a`: |p-aG FreeBSD "S|^3DEG>>'u"`i(c)O|^3-oI-oD-!A 1/2D- 1/2T>>{
     jumper ^3-L-^3](c)wYEN? 1/2T!C ^3\|h IDE
     -oI-oD-YENiYENH^3](c)w|" !S:Cable Select!" ((R)U 3/4U+-AE
     1/2u|`i,m"M(c)w)!A^3o"A<<D master(YEND-oI-oD-) (c)I
     slave(DEGAE-oI-oD-)!C  1/2D-DEGN
     3/4\-oI-oD--a-o>>!(c)uCURaaYENoYENHYEN? 1/2T^3](c)w jumper !C

   +-uCURU"O!A|O 1/4{|p|o+-NYEN|IAAU:|"AE(R)
   *"t^2I-a-oCUR@^3!YEN-:!C+-zYENiYENHDEGN|O vinum(8)(uU 20 ^3^1)
   CURI ccd(4)!C |b|^1S:UI?i 3/4U: ccd(4)!C

     --------------------------------------------------------------

      18.4.1.1.2. ^3](c)w CCD

   ccd(4)
   YENiYENH+-N|hO-oI-oD-+-uDEG_"O|"NOTDEGCUR@OCURj-oI-oD-!Cn"IYENI
   ccd(4)!A+-z-a-o kernel >>YnCURa:'(c) ccd(4)!C+-N^3o|aeYEN[CURJ"`i
   kernel ^3](c)wAE!A"A<< 1/2s!B<<|w,E kernel!G

 device   ccd

   CUR]YENiYENH,u:CURJ kernel DEGE-oA 1/4O^2O"OCURa:'(c) ccd(4)!C

   "IYENI ccd(4)  1/2D-YENyYENI bsdlabel(8) "O-a`i(c)l-oI-oD-!G

 bsdlabel -r -w ad1 auto
 bsdlabel -r -w ad2 auto
 bsdlabel -r -w ad3 auto

   CURWz<<u:YENO.|<<O/YENss ad1c!A ad2c (c)M ad3c!A ^3o"C, bsdlabel
   ^3-L-"IYENICURF 3/4aO-oI-oD-!C

   CURUCUR@"BNOTO *S:i label type!A|P 1/4EYENI bsdlabel(8) "O^3B^2z!G

 bsdlabel -e ad1
 bsdlabel -e ad2
 bsdlabel -e ad3

   ^3oO<<u:YENO.|YEN'P:}CUR@O 1/2s?e 3/4^1(^1w^3]NOTO
   vi(1)!AYENiYENHYENI EDITOR Ao^1OAAU: 1/4AE"O<<u:(c)w"a:YEN| 1/2s?e
   3/4^1)!A"A+-NYENO/<<e-oI-oD--a-o label ,eDEGTAAaYENU:|b,O 1/2s?e
   3/4^1,I!C

   CUR@OAUYEN 1/4AAU:DEGE^1L-a-o-oI-oD- label
   ,eDEGTNOTYDEG_"O.|^1^3^3o 1/4E!G

 8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)

   |b|^1S:UIn.s 1/4WCUR@O e partition u^1 ccd(4) "IYENI!C ^3q+-`
   1/2AE>>s c partition "-oCUR@|ae!A |AS:a fstype "-oCUR@|aeS:i|"
   4.2BSD 'NYENiYENHCURF!C S:iS:^1CURS:<<aNOTYDEG_"OA^3,O.|^1^3^3o
   1/4E!G

 8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   c: 60074784        0    unused        0     0     0   # (Cyl.    0 - 59597)
   e: 60074784        0    4.2BSD        0     0     0   # (Cyl.    0 - 59597)

     --------------------------------------------------------------

      18.4.1.1.3. <<O/YENssAE(R) *"t^2I

   ^2{|b(c)O|^3-a-o-oI-oD-^3-L-CURw,g<<O/|n bsdlabel
   CURF!AYENiYENHP:}(c)l<<O/YENss ccd(4)!C YENI ccdconfig(8)
   "O<<O/YENss ccd(4)!ADEGN|OCURU+--a-o<<u:YENO!G

 ccdconfig ccd0(1) 32(2) 0(3) /dev/ad1e(4) /dev/ad2e /dev/ad3e

   "CODEGN 1/4AE-a-oS:@YENI|pCURU!G

   (1)
           ^2A:CUR@ODEGN
           1/4AENOTOn^3](c)w-a-o,E,m|W-oU!A|b^3oO"OCURl,INOTO
           /dev/ccd0c!C"a:CURCUR /dev/ YENi|^3YENiuL!C
   (2)
           !uinterleave!v-a-oCURjCURp!C(c)O? * interleave
           NOTO<<u:CUR@+-AE-oI-oD-DEGIP:o (disk
           block)-a-oCURjCURp!A^3q+-`YENH 512 bytes
           NOTDEG^3ae|`i!A(c)OYENH interleave ^3]NOTDEG 32 S:YNOTDEG
           16,384 bytes!C
   (3)
           ccdconfig(8) ^3](c)w 1/4O|!-a-oDEGN
           1/4AE!C|p-aG+-zYEN'-oa+-OYENI-oI-oD-Ae^3] (drive
           mirroring)!A+-zYENiYENH|b|^1<<u:(c)wDEGN
           1/4AE!C^3oO"OCURl"S|^3"IYENIAe^3]!A (c)OYENH^3]|" 0!C
   (4)
           ccdconfig(8) ^3I<<a-a-oDEGN
           1/4AENOTOnYEN[CURJ"`iDEG}|C-a-o(c)O|^3-oI-oD-!C 
           1/2D-"IYENIS:^1 3/4a-a-o,o(R)|!C

   DEGo|ae ccdconfig(8) CURS:<<a!Accd(4)
   CURw^3](c)wS:^1|"YENi"N<<O/YENssAE(R) *"t^2I!C  1/2D-DEGN|O
   newfs(8) (c)I?eCURJ!G

 newfs /dev/ccd0c

     --------------------------------------------------------------

      18.4.1.1.4. AAyCUR@CURA|UDEGES:^1|"

   ^3q+-`+-z.|S:AE+-ae"C|,P:} 3/4-:(R)E^3-L--`a|UDEGE+-
   3/4CURW(mount) ccd(4)!C
   YENICURU+--a-o<<u:YENO+-N+-zYENO/<<e-a-o^3](c)w 1/4gCURJ
   /etc/ccd.conf !G

 ccdconfig -g > /etc/ccd.conf

   |p-aG /etc/ccd.conf |s|b!A"C|,P:} 3/4-:(R)E /etc/rc ^3-L-.|DEGo|ae
   ccdconfig -C !C |p|^1<<KYENi|UDEGE^3](c)w ccd(4) YENH<<KCURS:<<a+-
   3/4CURW(mount)AE(R) *"t^2I!C

     -a`: |p-aG+-zP:} 3/4-:(R)E?i 3/4U:P:iCURJ^3aeCURH 1/4O|!(single
     mode)!A|b+- 3/4CURW (mount(8)) ccd(4) -a-oAE(R)
     *"t^2ICURS:<<e+-z+-oYENyDEGo|ae^3](c)w-a-o<<u:YENO!G

 ccdconfig -C

   n|b"C|,P:} 3/4-:(R)E|UDEGE+- 3/4CURW(mount) ccd(4)!A 1/2D-|b
   /etc/fstab YEN[CURJ ccd(4)!G

 /dev/ccd0c              /media       ufs     rw      2       2

     --------------------------------------------------------------

    18.4.1.2. Vinum (R)eP:q-oTH^2z"t^2I

   Vinum (R)eP:q-oTH^2z"t^2I(YENHCURUA^2-oU Vinum)
   YENiuo/NOTDEGCUR@-oO/ueAA-oI-oD-!C YEN|+-NDEGIP:o,E,m(block
   device)
   -a-oCURP:+->>P^1iA^3,e(R)AE-a-oCURe|!CURA^3IP:}"O!ACURnDEG_`iYEN>>
   slice ^1-oCURA-a-o-oI-oD-!AVinum YENi 1/4WYEN[CURF
   1/4u(c)E!B(R)A:-`a(c)MA(c)w<< * [21] vinum(8) ^1eS:@CURF
   RAID-0!BRAID-1 (c)M RAID-5 uYEN 1/4O^2O!A
   YEN|I^3-L-YENiYENH^3ae?W"IYENI!ACUR]YENiYENHCURNOTNOTU.fDEGt"IYENI!C

   1/2D-"-L- uU 20 ^3^1 YENHDEGN|OS:o|hAo:(c)o vinum(8) -a-o,eDEGT!C

     --------------------------------------------------------------

  18.4.2. uwAAe RAID

   FreeBSD CUR]CURa:'(c)^3\|huwAAe RAID +-+-"i 3/4^1!C ^3o"C,+-+-"i
   3/4^1|U|ae'x+-+-CUR@OCURp<<NOT-a-o RAID "t^2I!A
   |]|^1CUR-L->>Yn-S(c)w^3nAAe"O-oTH^2z!C

   ^3z^1L+-+-"i 3/4^1CURW-a-o BIOS 'XYENG-`a+-+-"i(c)O|^3-a-o
   3/4THS:@!C +-uCURU"O+-NA^2^3aeCURP:^2D-|p|o^3](c)w Promise IDE
   RAID +-+-"iYENd!C-oYENy 1/2T>>{+-+-"iYENdCURw|w,E!A+-uuUP:}
   3/4-:!C
   YEN|A^3,O.|'-L-YENU:CUR@"C,,eDEGT[22]!C"I<<u:YENU:P:iCURJ+-+-"iYENd-a-o^3](c)wue+-!A
   +-q^3o,I+-zYENiYENH+-NYENth^3!-a-ouwAAeu^2|X|"CUR@OCURj-oI-oD-!CS:^1|"CURS:<<a!AFreeBSD
   +-NYENu.|NOTY"`i^3oOCURj-oI-oD-!C.iuM+-zCUR]YENiYENH"IYENI"a:YEN|-a-o
   RAID  1/4O|!!C

     --------------------------------------------------------------

  18.4.3. <<<<O/(rebuild) ATA RAID1 DEG}|C

   FreeBSD CUR^1^3\+-z 1/4o:'!(c)TH-oI-oD-DEG}|C,IAa+-
   1/4-a-o-oI-oD-!A .iuM|b<<P:} 3/4-:<<e'N+-oYENyuo^2{!C

   CUR]^3\+-z.||b /var/log/messages((c)I dmesg(8) -a-o?eYENX)
   NOTY"`iAth|u:CURU+--a-oDEGT(R)S:!G

 ad6 on monster1 suffered a hard error.
 ad6: READ command timeout tag=0 serv=0 - resetting
 ad6: trying fallback to PIO mode
 ata3: resetting devices .. done
 ad6: hard error reading fsbn 1116119 of 0-7 (ad6 bn 1116119; cn 1107 tn 4 sn 11)\\
 status=59 error=40
 ar0: WARNING - mirror lost

   1/2D-YENI atacontrol(8) "O+-o"`iS:o|h,eDEGT!G

 # atacontrol list
 ATA channel 0:
         Master:      no device present
         Slave:   acd0 <HL-DT-ST CD-ROM GCR-8520B/1.00> ATA/ATAPI rev 0

 ATA channel 1:
         Master:      no device present
         Slave:       no device present

 ATA channel 2:
         Master:  ad4 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI rev 5
         Slave:       no device present

 ATA channel 3:
         Master:  ad6 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI rev 5
         Slave:       no device present

 # atacontrol status ar0
 ar0: ATA RAID1 subdisks: ad4 ad6 status: DEGRADED

    1. -oYENy+-z+-o+-N.lAa-oI-oD-(c)O|b-a-o ata channel
       "o/,u:(detach)!A |p|^1CUR~-`a|wYENth|a^2 3/4DEG-L-!G

 # atacontrol detach ata3

    2. YENI|n-a-o-oI-oD-'<<CURU.lAa-a-o!C

    3. <<.s,u:CURJ(re-attach) ata channel!G

 # atacontrol attach ata3
 Master:  ad6 <MAXTOR 6L080J4/A93.0500> ATA/ATAPI rev 5
 Slave:   no device present

    4. +-N.s-a-o-oI-oD-YEN[CURJ`iYEN>>-a-o-oI-oD-DEG}|C|"NOTDEG^3AE'(c)(spare)
       -oI-oD-!G

 # atacontrol addspare ar0 ad6

    5. <<<<O/-oI-oD-DEG}|C!G

 # atacontrol rebuild ar0

    6. YENiYENHYENICURU+-<<u:(c)w"O 1/2T>>{<<<<O/-a-oP:i<< *!G

 # dmesg | tail -10
 [output removed]
 ad6: removed from configuration
 ad6: deleted from ar0 disk1
 ad6: inserted into ar0 disk1 as spare

 # atacontrol status ar0
 ar0: ATA RAID1 subdisks: ad4 ad6 status: REBUILDING 0% completed

    7. uYEN<<<<O/S:^1'NS:^1|"CURF!C

     --------------------------------------------------------------

18.5. USB Ax|s,E,m

   Contributed by Marc Fonvieille.

   |b^2{|b!A|^3^3\|hYEN~^3!Ax|s,E,m+-A:YENI USB(Universal Serial Bus)
   CURP:+-!A "O|puw-oD-!BUSB (c)ae<<u:-oD-!BCD-R ?N?y 3/4-:uYEN!C
   FreeBSD '-L-"N^1i^3o"C,,E,m-a-oCURa:'(c)!C

     --------------------------------------------------------------

  18.5.1. ^3](c)w

   USB mass Ax|s,E,mAAXDEGEu{|!(umass(4))'-L-"N USB
   Ax|s,E,m-a-oCURa:'(c)!C |y|p-aGNOTOYENI GENERIC
   kernel!A'NCUR-L->>YnDEGuYENo|o^3](c)wAAU:DEGE !C YNOTO|Uq kernel!A
   1/2D- 1/2T>>{ kernel ^3](c)wAES:t|^3CURU+-^3o'X|ae!G

 device scbus
 device da
 device pass
 device uhci
 device ohci
 device usb
 device umass

   umass(4) AAXDEGEu{|!^3z^1L SCSI CURl"t^2I|s"u USB Ax|s,E,m!A
   +-z-a-o USB ,E,m.|^3Q"t^2I?eAN|" SCSI ,E,m!C "I.O+-zYEND
   3/4-:-aOCURW USB '^1CURu<<NOT,^1!A +-zYENu>>Yn device uhci (c)I
   device ohci "a:CURCURCUR@O!C uM|O!A+-N"a-aI^3-L- 1/2sP:i kernel
   CUR]uLS:<<!C YENunS:OS:NCURF|b *S:i kernel ^3](c)w<<a<<.s
   1/2sA:P:CURI|w,E.s-a-o kernel 'N|aeCURF!C

     -a`: |p-aG+-z-a-o USB ,E,mNOTO CD-R (c)I DVD ?N?y 3/4-:!A<<h
     SCSI YENu-oD- 3/4-:AAXDEGEu{|! cd(4) YEN^2P:. 1/4gCURJ kernel
     ^3](c)wAE!A^1^3^3o 1/4E!G

 device cd

     |]NOTDEG?N?y 3/4-:.|^3Q.i|" SCSI ,E,m!A(c)OYENH atapicam(4)
     AAXDEGEu{|!CUR-L->>Yn 1/2sCURJ kernel!C

   USB 2.0 +-+-"i 3/4^1-a-oCURa:'(c)YENN FreeBSD;
   '-L-"N!AuM|OYEN^2P:.|b kernel ^3](c)wAE
   1/4WYEN[CURU+-^3o|aeYENH'-L-"N USB 2.0 CURa:'(c)!G

 device ehci

   -a`.N!A|p-aG+-z>>Yn USB 1.x CURa:'(c)!A+-zCUR'uM>>Yn+-N uhci(4)
   CURI ohci(4) AAXDEGEu{|! 1/2sCURJ kernel!C

     --------------------------------------------------------------

  18.5.2. 'u,O^3](c)w

   The configuration is ready to be tested: plug in your USB device,
   and in the system message buffer (dmesg(8)), the drive should
   appear as something like:

 umass0: USB Solid state disk, rev 1.10/1.00, addr 2
 GEOM: create disk da0 dp=0xc2d74850
 da0 at umass-sim0 bus 0 target 0 lun 0
 da0: <Generic Traveling Disk 1.11> Removable Direct Access SCSI-2 device
 da0: 1.000MB/s transfers
 da0: 126MB (258048 512 byte sectors: 64H 32S/T 126C)

   Of course, the brand, the device node (da0) and other details can
   differ according to your configuration.

   Since the USB device is seen as a SCSI one, the camcontrol command
   can be used to list the USB storage devices attached to the
   system:

 # camcontrol devlist
 <Generic Traveling Disk 1.11>      at scbus0 target 0 lun 0 (da0,pass0)

   If the drive comes with a file system, you should be able to mount
   it. The uU 18.3 ,` will help you to format and create partitions
   on the USB drive if needed.

   If you unplug the device (the disk must be unmounted before), you
   should see, in the system message buffer, something like the
   following:

 umass0: at uhub0 port 1 (addr 2) disconnected
 (da0:umass-sim0:0:0:0): lost device
 (da0:umass-sim0:0:0:0): removing device entry
 GEOM: destroy disk da0 dp=0xc2d74850
 umass0: detached

     --------------------------------------------------------------

  18.5.3. Further Reading

   Beside the Adding Disks and Mounting and Unmounting File Systems
   sections, reading various manual pages may be also useful:
   umass(4), camcontrol(8), and usbdevs(8).

     --------------------------------------------------------------

18.6. Creating and Using Optical Media (CDs)

   Contributed by Mike Meyer.

     --------------------------------------------------------------

  18.6.1. Introduction

   CDs have a number of features that differentiate them from
   conventional disks. Initially, they were not writable by the user.
   They are designed so that they can be read continuously without
   delays to move the head between tracks. They are also much easier
   to transport between systems than similarly sized media were at
   the time.

   CDs do have tracks, but this refers to a section of data to be
   read continuously and not a physical property of the disk. To
   produce a CD on FreeBSD, you prepare the data files that are going
   to make up the tracks on the CD, then write the tracks to the CD.

   The ISO 9660 file system was designed to deal with these
   differences. It unfortunately codifies file system limits that
   were common then. Fortunately, it provides an extension mechanism
   that allows properly written CDs to exceed those limits while
   still working with systems that do not support those extensions.

   The sysutils/cdrtools port includes mkisofs(8), a program that you
   can use to produce a data file containing an ISO 9660 file system.
   It has options that support various extensions, and is described
   below.

   Which tool to use to burn the CD depends on whether your CD burner
   is ATAPI or something else. ATAPI CD burners use the burncd
   program that is part of the base system. SCSI and USB CD burners
   should use cdrecord from the sysutils/cdrtools port.

   burncd has a limited number of supported drives. To find out if a
   drive is supported, see the CD-R/RW supported drives list.

     -a`: If you run FreeBSD 5.X, FreeBSD 4.8-RELEASE version or
     higher, it will be possible to use cdrecord and other tools for
     SCSI drives on an ATAPI hardware with the ATAPI/CAM module.

   If you want a CD burning software with a graphical user interface,
   you should have a look to X-CD-Roast or K3b. These tools are
   available as packages or from the sysutils/xcdroast and
   sysutils/k3b ports. X-CD-Roast and K3b require the ATAPI/CAM
   module with ATAPI hardware.

     --------------------------------------------------------------

  18.6.2. mkisofs

   The mkisofs(8) program, which is part of the sysutils/cdrtools
   port, produces an ISO 9660 file system that is an image of a
   directory tree in the UNIX file system name space. The simplest
   usage is:

 # mkisofs -o imagefile.iso /path/to/tree

   This command will create an imagefile.iso containing an ISO 9660
   file system that is a copy of the tree at /path/to/tree. In the
   process, it will map the file names to names that fit the
   limitations of the standard ISO 9660 file system, and will exclude
   files that have names uncharacteristic of ISO file systems.

   A number of options are available to overcome those restrictions.
   In particular, -R enables the Rock Ridge extensions common to UNIX
   systems, -J enables Joliet extensions used by Microsoft systems,
   and -hfs can be used to create HFS file systems used by Mac OS.

   For CDs that are going to be used only on FreeBSD systems, -U can
   be used to disable all filename restrictions. When used with -R,
   it produces a file system image that is identical to the FreeBSD
   tree you started from, though it may violate the ISO 9660 standard
   in a number of ways.

   The last option of general use is -b. This is used to specify the
   location of the boot image for use in producing an !S:El Torito!"
   bootable CD. This option takes an argument which is the path to a
   boot image from the top of the tree being written to the CD. By
   default, mkisofs(8) creates an ISO image in the so-called
   !S:floppy disk emulation!" mode, and thus expects the boot image
   to be exactly 1200, 1440 or 2880 KB in size. Some boot loaders,
   like the one used by the FreeBSD distribution disks, do not use
   emulation mode; in this case, the -no-emul-boot option should be
   used. So, if /tmp/myboot holds a bootable FreeBSD system with the
   boot image in /tmp/myboot/boot/cdboot, you could produce the image
   of an ISO 9660 file system in /tmp/bootable.iso like so:

 # mkisofs -R -no-emul-boot -b boot/cdboot -o /tmp/bootable.iso /tmp/myboot

   Having done that, if you have md configured in your kernel, you
   can mount the file system with:

 # mdconfig -a -t vnode -f /tmp/bootable.iso -u 0
 # mount -t cd9660 /dev/md0 /mnt

   At which point you can verify that /mnt and /tmp/myboot are
   identical.

   There are many other options you can use with mkisofs(8) to
   fine-tune its behavior. In particular: modifications to an ISO
   9660 layout and the creation of Joliet and HFS discs. See the
   mkisofs(8) manual page for details.

     --------------------------------------------------------------

  18.6.3. burncd

   If you have an ATAPI CD burner, you can use the burncd command to
   burn an ISO image onto a CD. burncd is part of the base system,
   installed as /usr/sbin/burncd. Usage is very simple, as it has few
   options:

 # burncd -f cddevice data imagefile.iso fixate

   Will burn a copy of imagefile.iso on cddevice. The default device
   is /dev/acd0. See burncd(8) for options to set the write speed,
   eject the CD after burning, and write audio data.

     --------------------------------------------------------------

  18.6.4. cdrecord

   If you do not have an ATAPI CD burner, you will have to use
   cdrecord to burn your CDs. cdrecord is not part of the base
   system; you must install it from either the port at
   sysutils/cdrtools or the appropriate package. Changes to the base
   system can cause binary versions of this program to fail, possibly
   resulting in a !S:coaster!". You should therefore either upgrade
   the port when you upgrade your system, or if you are tracking
   -STABLE, upgrade the port when a new version becomes available.

   While cdrecord has many options, basic usage is even simpler than
   burncd. Burning an ISO 9660 image is done with:

 # cdrecord dev=device imagefile.iso

   The tricky part of using cdrecord is finding the dev to use. To
   find the proper setting, use the -scanbus flag of cdrecord, which
   might produce results like this:

 # cdrecord -scanbus
 Cdrecord-Clone 2.01 (i386-unknown-freebsd7.0) Copyright (C) 1995-2004 Jo:rg Schilling
 Using libscg version 'schily-0.1'
 scsibus0:
         0,0,0     0) 'SEAGATE ' 'ST39236LW       ' '0004' Disk
         0,1,0     1) 'SEAGATE ' 'ST39173W        ' '5958' Disk
         0,2,0     2) *
         0,3,0     3) 'iomega  ' 'jaz 1GB         ' 'J.86' Removable Disk
         0,4,0     4) 'NEC     ' 'CD-ROM DRIVE:466' '1.26' Removable CD-ROM
         0,5,0     5) *
         0,6,0     6) *
         0,7,0     7) *
 scsibus1:
         1,0,0   100) *
         1,1,0   101) *
         1,2,0   102) *
         1,3,0   103) *
         1,4,0   104) *
         1,5,0   105) 'YAMAHA  ' 'CRW4260         ' '1.0q' Removable CD-ROM
         1,6,0   106) 'ARTEC   ' 'AM12S           ' '1.06' Scanner
         1,7,0   107) *

   This lists the appropriate dev value for the devices on the list.
   Locate your CD burner, and use the three numbers separated by
   commas as the value for dev. In this case, the CRW device is
   1,5,0, so the appropriate input would be dev=1,5,0. There are
   easier ways to specify this value; see cdrecord(1) for details.
   That is also the place to look for information on writing audio
   tracks, controlling the speed, and other things.

     --------------------------------------------------------------

  18.6.5. Duplicating Audio CDs

   You can duplicate an audio CD by extracting the audio data from
   the CD to a series of files, and then writing these files to a
   blank CD. The process is slightly different for ATAPI and SCSI
   drives.

   SCSI Drives

    1. Use cdda2wav to extract the audio.

 % cdda2wav -v255 -D2,0 -B -Owav

    2. Use cdrecord to write the .wav files.

 % cdrecord -v dev=2,0 -dao -useinfo  *.wav

       Make sure that 2,0 is set appropriately, as described in uU
       18.6.4 ,`.

   ATAPI Drives

    1. The ATAPI CD driver makes each track available as
       /dev/acddtnn, where d is the drive number, and nn is the track
       number written with two decimal digits, prefixed with zero as
       needed. So the first track on the first disk is /dev/acd0t01,
       the second is /dev/acd0t02, the third is /dev/acd0t03, and so
       on.

       Make sure the appropriate files exist in /dev. If the entries
       are missing, force the system to retaste the media:

 # dd if=/dev/acd0 of=/dev/null count=1

    2. Extract each track using dd(1). You must also use a specific
       block size when extracting the files.

 # dd if=/dev/acd0t01 of=track1.cdr bs=2352
 # dd if=/dev/acd0t02 of=track2.cdr bs=2352
 ...

    3. Burn the extracted files to disk using burncd. You must
       specify that these are audio files, and that burncd should
       fixate the disk when finished.

 # burncd -f /dev/acd0 audio track1.cdr track2.cdr ... fixate

     --------------------------------------------------------------

  18.6.6. Duplicating Data CDs

   You can copy a data CD to a image file that is functionally
   equivalent to the image file created with mkisofs(8), and you can
   use it to duplicate any data CD. The example given here assumes
   that your CDROM device is acd0. Substitute your correct CDROM
   device.

 # dd if=/dev/acd0 of=file.iso bs=2048

   Now that you have an image, you can burn it to CD as described
   above.

     --------------------------------------------------------------

  18.6.7. Using Data CDs

   Now that you have created a standard data CDROM, you probably want
   to mount it and read the data on it. By default, mount(8) assumes
   that a file system is of type ufs. If you try something like:

 # mount /dev/cd0 /mnt

   you will get a complaint about !S:Incorrect super block!", and no
   mount. The CDROM is not a UFS file system, so attempts to mount it
   as such will fail. You just need to tell mount(8) that the file
   system is of type ISO9660, and everything will work. You do this
   by specifying the -t cd9660 option mount(8). For example, if you
   want to mount the CDROM device, /dev/cd0, under /mnt, you would
   execute:

 # mount -t cd9660 /dev/cd0 /mnt

   Note that your device name (/dev/cd0 in this example) could be
   different, depending on the interface your CDROM uses. Also, the
   -t cd9660 option just executes mount_cd9660(8). The above example
   could be shortened to:

 # mount_cd9660 /dev/cd0 /mnt

   You can generally use data CDROMs from any vendor in this way.
   Disks with certain ISO 9660 extensions might behave oddly,
   however. For example, Joliet disks store all filenames in two-byte
   Unicode characters. The FreeBSD kernel does not speak Unicode
   (yet!), so non-English characters show up as question marks. (The
   FreeBSD CD9660 driver includes hooks to load an appropriate
   Unicode conversion table on the fly. Modules for some of the
   common encodings are available via the sysutils/cd9660_unicode
   port.)

   Occasionally, you might get !S:Device not configured!" when trying
   to mount a CDROM. This usually means that the CDROM drive thinks
   that there is no disk in the tray, or that the drive is not
   visible on the bus. It can take a couple of seconds for a CDROM
   drive to realize that it has been fed, so be patient.

   Sometimes, a SCSI CDROM may be missed because it did not have
   enough time to answer the bus reset. If you have a SCSI CDROM
   please add the following option to your kernel configuration and
   rebuild your kernel.

 options SCSI_DELAY=15000

   This tells your SCSI bus to pause 15 seconds during boot, to give
   your CDROM drive every possible chance to answer the bus reset.

     --------------------------------------------------------------

  18.6.8. Burning Raw Data CDs

   You can choose to burn a file directly to CD, without creating an
   ISO 9660 file system. Some people do this for backup purposes.
   This runs more quickly than burning a standard CD:

 # burncd -f /dev/acd1 -s 12 data archive.tar.gz fixate

   In order to retrieve the data burned to such a CD, you must read
   data from the raw device node:

 # tar xzvf /dev/acd1

   You cannot mount this disk as you would a normal CDROM. Such a
   CDROM cannot be read under any operating system except FreeBSD. If
   you want to be able to mount the CD, or share data with another
   operating system, you must use mkisofs(8) as described above.

     --------------------------------------------------------------

  18.6.9. Using the ATAPI/CAM Driver

   Contributed by Marc Fonvieille.

   This driver allows ATAPI devices (CD-ROM, CD-RW, DVD drives
   etc...) to be accessed through the SCSI subsystem, and so allows
   the use of applications like sysutils/cdrdao or cdrecord(1).

   To use this driver, you will need to add the following line to
   your kernel configuration file:

 device atapicam

   You also need the following lines in your kernel configuration
   file:

 device ata
 device scbus
 device cd
 device pass

   which should already be present.

   Then rebuild, install your new kernel, and reboot your machine.
   During the boot process, your burner should show up, like so:

 acd0: CD-RW <MATSHITA CD-RW/DVD-ROM UJDA740> at ata1-master PIO4
 cd0 at ata1 bus 0 target 0 lun 0
 cd0: <MATSHITA CDRW/DVD UJDA740 1.00> Removable CD-ROM SCSI-0 device
 cd0: 16.000MB/s transfers
 cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed

   The drive could now be accessed via the /dev/cd0 device name, for
   example to mount a CD-ROM on /mnt, just type the following:

 # mount -t cd9660 /dev/cd0 /mnt

   As root, you can run the following command to get the SCSI address
   of the burner:

 # camcontrol devlist
 <MATSHITA CDRW/DVD UJDA740 1.00>   at scbus1 target 0 lun 0 (pass0,cd0)

   So 1,0,0 will be the SCSI address to use with cdrecord(1) and
   other SCSI application.

   For more information about ATAPI/CAM and SCSI system, refer to the
   atapicam(4) and cam(4) manual pages.

     --------------------------------------------------------------

18.7. Creating and Using Optical Media (DVDs)

   Contributed by Marc Fonvieille. With inputs from Andy Polyakov.

     --------------------------------------------------------------

  18.7.1. Introduction

   Compared to the CD, the DVD is the next generation of optical
   media storage technology. The DVD can hold more data than any CD
   and is nowadays the standard for video publishing.

   Five physical recordable formats can be defined for what we will
   call a recordable DVD:

     * DVD-R: This was the first DVD recordable format available. The
       DVD-R standard is defined by the DVD Forum. This format is
       write once.

     * DVD-RW: This is the rewriteable version of the DVD-R standard.
       A DVD-RW can be rewritten about 1000 times.

     * DVD-RAM: This is also a rewriteable format supported by the
       DVD Forum. A DVD-RAM can be seen as a removable hard drive.
       However, this media is not compatible with most DVD-ROM drives
       and DVD-Video players; only a few DVD writers support the
       DVD-RAM format.

     * DVD+RW: This is a rewriteable format defined by the DVD+RW
       Alliance. A DVD+RW can be rewritten about 1000 times.

     * DVD+R: This format is the write once variation of the DVD+RW
       format.

   A single layer recordable DVD can hold up to 4,700,000,000 bytes
   which is actually 4.38 GB or 4485 MB (1 kilobyte is 1024 bytes).

     -a`: A distinction must be made between the physical media and
     the application. For example, a DVD-Video is a specific file
     layout that can be written on any recordable DVD physical media:
     DVD-R, DVD+R, DVD-RW etc. Before choosing the type of media, you
     must be sure that both the burner and the DVD-Video player (a
     standalone player or a DVD-ROM drive on a computer) are
     compatible with the media under consideration.

     --------------------------------------------------------------

  18.7.2. Configuration

   The program growisofs(1) will be used to perform DVD recording.
   This command is part of the dvd+rw-tools utilities
   (sysutils/dvd+rw-tools). The dvd+rw-tools support all DVD media
   types.

   These tools use the SCSI subsystem to access to the devices,
   therefore the ATAPI/CAM support must be added to your kernel. If
   your burner uses the USB interface this addition is useless, and
   you should read the uU 18.5 ,` for more details on USB devices
   configuration.

   You also have to enable DMA access for ATAPI devices, this can be
   done in adding the following line to the /boot/loader.conf file:

 hw.ata.atapi_dma="1"

   Before attempting to use the dvd+rw-tools you should consult the
   dvd+rw-tools' hardware compatibility notes for any information
   related to your DVD burner.

     -a`: If you want a graphical user interface, you should have a
     look to K3b (sysutils/k3b) which provides a user friendly
     interface to growisofs(1) and many others burning tools.

     --------------------------------------------------------------

  18.7.3. Burning Data DVDs

   The growisofs(1) command is a frontend to mkisofs, it will invoke
   mkisofs(8) to create the file system layout and will perform the
   write on the DVD. This means you do not need to create an image of
   the data before the burning process.

   To burn onto a DVD+R or a DVD-R the data from the /path/to/data
   directory, use the following command:

 # growisofs -dvd-compat -Z /dev/cd0 -J -R /path/to/data

   The options -J -R are passed to mkisofs(8) for the file system
   creation (in this case: an ISO 9660 file system with Joliet and
   Rock Ridge extensions), consult the mkisofs(8) manual page for
   more details.

   The option -Z is used for the initial session recording in any
   case: multiple sessions or not. The DVD device, /dev/cd0, must be
   changed according to your configuration. The -dvd-compat parameter
   will close the disk, the recording will be unappendable. In return
   this should provide better media compatibility with DVD-ROM
   drives.

   It is also possible to burn a pre-mastered image, for example to
   burn the image imagefile.iso, we will run:

 # growisofs -dvd-compat -Z /dev/cd0=imagefile.iso

   The write speed should be detected and automatically set according
   to the media and the drive being used. If you want to force the
   write speed, use the -speed= parameter. For more information, read
   the growisofs(1) manual page.

     --------------------------------------------------------------

  18.7.4. Burning a DVD-Video

   A DVD-Video is a specific file layout based on ISO 9660 and the
   micro-UDF (M-UDF) specifications. The DVD-Video also presents a
   specific data structure hierarchy, it is the reason why you need a
   particular program such as multimedia/dvdauthor to author the DVD.

   If you already have an image of the DVD-Video file system, just
   burn it in the same way as for any image, see the previous section
   for an example. If you have made the DVD authoring and the result
   is in, for example, the directory /path/to/video, the following
   command should be used to burn the DVD-Video:

 # growisofs -Z /dev/cd0 -dvd-video /path/to/video

   The -dvd-video option will be passed down to mkisofs(8) and will
   instruct it to create a DVD-Video file system layout. Beside this,
   the -dvd-video option implies -dvd-compat growisofs(1) option.

     --------------------------------------------------------------

  18.7.5. Using a DVD+RW

   Unlike CD-RW, a virgin DVD+RW needs to be formatted before first
   use. The growisofs(1) program will take care of it automatically
   whenever appropriate, which is the recommended way. However you
   can use the dvd+rw-format command to format the DVD+RW:

 # dvd+rw-format /dev/cd0

   You need to perform this operation just once, keep in mind that
   only virgin DVD+RW medias need to be formatted. Then you can burn
   the DVD+RW in the way seen in previous sections.

   If you want to burn new data (burn a totally new file system not
   append some data) onto a DVD+RW, you do not need to blank it, you
   just have to write over the previous recording (in performing a
   new initial session), like this:

 # growisofs -Z /dev/cd0 -J -R /path/to/newdata

   DVD+RW format offers the possibility to easily append data to a
   previous recording. The operation consists in merging a new
   session to the existing one, it is not multisession writing,
   growisofs(1) will grow the ISO 9660 file system present on the
   media.

   For example, if we want to append data to our previous DVD+RW, we
   have to use the following:

 # growisofs -M /dev/cd0 -J -R /path/to/nextdata

   The same mkisofs(8) options we used to burn the initial session
   should be used during next writes.

     -a`: You may want to use the -dvd-compat option if you want
     better media compatibility with DVD-ROM drives. In the DVD+RW
     case, this will not prevent you from adding data.

   If for any reason you really want to blank the media, do the
   following:

 # growisofs -Z /dev/cd0=/dev/zero

     --------------------------------------------------------------

  18.7.6. Using a DVD-RW

   A DVD-RW accepts two disc formats: the incremental sequential one
   and the restricted overwrite. By default DVD-RW discs are in
   sequential format.

   A virgin DVD-RW can be directly written without the need of a
   formatting operation, however a non-virgin DVD-RW in sequential
   format needs to be blanked before to be able to write a new
   initial session.

   To blank a DVD-RW in sequential mode, run:

 # dvd+rw-format -blank=full /dev/cd0

     -a`: A full blanking (-blank=full) will take about one hour on a
     1x media. A fast blanking can be performed using the -blank
     option if the DVD-RW will be recorded in Disk-At-Once (DAO)
     mode. To burn the DVD-RW in DAO mode, use the command:

 # growisofs -use-the-force-luke=dao -Z /dev/cd0=imagefile.iso

     The -use-the-force-luke=dao option should not be required since
     growisofs(1) attempts to detect minimally (fast blanked) media
     and engage DAO write.

     In fact one should use restricted overwrite mode with any
     DVD-RW, this format is more flexible than the default
     incremental sequential one.

   To write data on a sequential DVD-RW, use the same instructions as
   for the other DVD formats:

 # growisofs -Z /dev/cd0 -J -R /path/to/data

   If you want to append some data to your previous recording, you
   will have to use the growisofs(1) -M option. However, if you
   perform data addition on a DVD-RW in incremental sequential mode,
   a new session will be created on the disc and the result will be a
   multi-session disc.

   A DVD-RW in restricted overwrite format does not need to be
   blanked before a new initial session, you just have to overwrite
   the disc with the -Z option, this is similar to the DVD+RW case.
   It is also possible to grow an existing ISO 9660 file system
   written on the disc in a same way as for a DVD+RW with the -M
   option. The result will be a one-session DVD.

   To put a DVD-RW in the restricted overwrite format, the following
   command must be used:

 # dvd+rw-format /dev/cd0

   To change back to the sequential format use:

 # dvd+rw-format -blank=full /dev/cd0

     --------------------------------------------------------------

  18.7.7. Multisession

   Very few DVD-ROM drives support multisession DVDs, they will most
   of time, hopefully, only read the first session. DVD+R, DVD-R and
   DVD-RW in sequential format can accept multiple sessions, the
   notion of multiple sessions does not exist for the DVD+RW and the
   DVD-RW restricted overwrite formats.

   Using the following command after an initial (non-closed) session
   on a DVD+R, DVD-R, or DVD-RW in sequential format, will add a new
   session to the disc:

 # growisofs -M /dev/cd0 -J -R /path/to/nextdata

   Using this command line with a DVD+RW or a DVD-RW in restricted
   overwrite mode, will append data in merging the new session to the
   existing one. The result will be a single-session disc. This is
   the way used to add data after an initial write on these medias.

     -a`: Some space on the media is used between each session for
     end and start of sessions. Therefore, one should add sessions
     with large amount of data to optimize media space. The number of
     sessions is limited to 154 for a DVD+R, about 2000 for a DVD-R,
     and 127 for a DVD+R Double Layer.

     --------------------------------------------------------------

  18.7.8. For More Information

   To obtain more information about a DVD, the dvd+rw-mediainfo
   /dev/cd0 command can be ran with the disc in the drive.

   More information about the dvd+rw-tools can be found in the
   growisofs(1) manual page, on the dvd+rw-tools web site and in the
   cdwrite mailing list archives.

     -a`: The dvd+rw-mediainfo output of the resulting recording or
     the media with issues is mandatory for any problem report.
     Without this output, it will be quite impossible to help you.

     --------------------------------------------------------------

18.8. Creating and Using Floppy Disks

   Original work by Julio Merino. Rewritten by Martin Karlsson.

   Storing data on floppy disks is sometimes useful, for example when
   one does not have any other removable storage media or when one
   needs to transfer small amounts of data to another computer.

   This section will explain how to use floppy disks in FreeBSD. It
   will primarily cover formatting and usage of 3.5inch DOS floppies,
   but the concepts are similar for other floppy disk formats.

     --------------------------------------------------------------

  18.8.1. Formatting Floppies

    18.8.1.1. The Device

   Floppy disks are accessed through entries in /dev, just like other
   devices. To access the raw floppy disk, simply use /dev/fdN.

     --------------------------------------------------------------

    18.8.1.2. Formatting

   A floppy disk needs to be low-level formated before it can be
   used. This is usually done by the vendor, but formatting is a good
   way to check media integrity. Although it is possible to force
   larger (or smaller) disk sizes, 1440kB is what most floppy disks
   are designed for.

   To low-level format the floppy disk you need to use fdformat(1).
   This utility expects the device name as an argument.

   Make note of any error messages, as these can help determine if
   the disk is good or bad.

     --------------------------------------------------------------

      18.8.1.2.1. Formatting Floppy Disks

   Use the /dev/fdN devices to format the floppy. Insert a new
   3.5inch floppy disk in your drive and issue:

 # /usr/sbin/fdformat -f 1440 /dev/fd0

     --------------------------------------------------------------

  18.8.2. The Disk Label

   After low-level formatting the disk, you will need to place a disk
   label on it. This disk label will be destroyed later, but it is
   needed by the system to determine the size of the disk and its
   geometry later.

   The new disk label will take over the whole disk, and will contain
   all the proper information about the geometry of the floppy. The
   geometry values for the disk label are listed in /etc/disktab.

   You can run now bsdlabel(8) like so:

 # /sbin/bsdlabel -B -r -w /dev/fd0 fd1440

     -a`: Since FreeBSD 5.1-RELEASE, the bsdlabel(8) utility replaces
     the old bsdlabel(8) program. With bsdlabel(8) a number of
     obsolete options and parameters have been retired; in the
     example above the option -r should be removed. For more
     information, please refer to the bsdlabel(8) manual page.

     --------------------------------------------------------------

  18.8.3. The File System

   Now the floppy is ready to be high-level formated. This will place
   a new file system on it, which will let FreeBSD read and write to
   the disk. After creating the new file system, the disk label is
   destroyed, so if you want to reformat the disk, you will have to
   recreate the disk label.

   The floppy's file system can be either UFS or FAT. FAT is
   generally a better choice for floppies.

   To put a new file system on the floppy, issue:

 # /sbin/newfs_msdos /dev/fd0

   The disk is now ready for use.

     --------------------------------------------------------------

  18.8.4. Using the Floppy

   To use the floppy, mount it with mount_msdos(8). One can also use
   emulators/mtools from the ports collection.

     --------------------------------------------------------------

18.9. Creating and Using Data Tapes

   The major tape media are the 4mm, 8mm, QIC, mini-cartridge and
   DLT.

     --------------------------------------------------------------

  18.9.1. 4mm (DDS: Digital Data Storage)

   4mm tapes are replacing QIC as the workstation backup media of
   choice. This trend accelerated greatly when Conner purchased
   Archive, a leading manufacturer of QIC drives, and then stopped
   production of QIC drives. 4mm drives are small and quiet but do
   not have the reputation for reliability that is enjoyed by 8mm
   drives. The cartridges are less expensive and smaller (3 x 2 x 0.5
   inches, 76 x 51 x 12 mm) than 8mm cartridges. 4mm, like 8mm, has
   comparatively short head life for the same reason, both use
   helical scan.

   Data throughput on these drives starts ~150 kB/s, peaking at
   ~500 kB/s. Data capacity starts at 1.3 GB and ends at 2.0 GB.
   Hardware compression, available with most of these drives,
   approximately doubles the capacity. Multi-drive tape library units
   can have 6 drives in a single cabinet with automatic tape
   changing. Library capacities reach 240 GB.

   The DDS-3 standard now supports tape capacities up to 12 GB (or
   24 GB compressed).

   4mm drives, like 8mm drives, use helical-scan. All the benefits
   and drawbacks of helical-scan apply to both 4mm and 8mm drives.

   Tapes should be retired from use after 2,000 passes or 100 full
   backups.

     --------------------------------------------------------------

  18.9.2. 8mm (Exabyte)

   8mm tapes are the most common SCSI tape drives; they are the best
   choice of exchanging tapes. Nearly every site has an Exabyte 2 GB
   8mm tape drive. 8mm drives are reliable, convenient and quiet.
   Cartridges are inexpensive and small (4.8 x 3.3 x 0.6 inches; 122
   x 84 x 15 mm). One downside of 8mm tape is relatively short head
   and tape life due to the high rate of relative motion of the tape
   across the heads.

   Data throughput ranges from ~250 kB/s to ~500 kB/s. Data sizes
   start at 300 MB and go up to 7 GB. Hardware compression, available
   with most of these drives, approximately doubles the capacity.
   These drives are available as single units or multi-drive tape
   libraries with 6 drives and 120 tapes in a single cabinet. Tapes
   are changed automatically by the unit. Library capacities reach
   840+ GB.

   The Exabyte !S:Mammoth!" model supports 12 GB on one tape (24 GB
   with compression) and costs approximately twice as much as
   conventional tape drives.

   Data is recorded onto the tape using helical-scan, the heads are
   positioned at an angle to the media (approximately 6 degrees). The
   tape wraps around 270 degrees of the spool that holds the heads.
   The spool spins while the tape slides over the spool. The result
   is a high density of data and closely packed tracks that angle
   across the tape from one edge to the other.

     --------------------------------------------------------------

  18.9.3. QIC

   QIC-150 tapes and drives are, perhaps, the most common tape drive
   and media around. QIC tape drives are the least expensive
   !S:serious!" backup drives. The downside is the cost of media. QIC
   tapes are expensive compared to 8mm or 4mm tapes, up to 5 times
   the price per GB data storage. But, if your needs can be satisfied
   with a half-dozen tapes, QIC may be the correct choice. QIC is the
   most common tape drive. Every site has a QIC drive of some density
   or another. Therein lies the rub, QIC has a large number of
   densities on physically similar (sometimes identical) tapes. QIC
   drives are not quiet. These drives audibly seek before they begin
   to record data and are clearly audible whenever reading, writing
   or seeking. QIC tapes measure (6 x 4 x 0.7 inches; 152 x 102 x 17
   mm).

   Data throughput ranges from ~150 kB/s to ~500 kB/s. Data capacity
   ranges from 40 MB to 15 GB. Hardware compression is available on
   many of the newer QIC drives. QIC drives are less frequently
   installed; they are being supplanted by DAT drives.

   Data is recorded onto the tape in tracks. The tracks run along the
   long axis of the tape media from one end to the other. The number
   of tracks, and therefore the width of a track, varies with the
   tape's capacity. Most if not all newer drives provide
   backward-compatibility at least for reading (but often also for
   writing). QIC has a good reputation regarding the safety of the
   data (the mechanics are simpler and more robust than for helical
   scan drives).

   Tapes should be retired from use after 5,000 backups.

     --------------------------------------------------------------

  18.9.4. DLT

   DLT has the fastest data transfer rate of all the drive types
   listed here. The 1/2" (12.5mm) tape is contained in a single spool
   cartridge (4 x 4 x 1 inches; 100 x 100 x 25 mm). The cartridge has
   a swinging gate along one entire side of the cartridge. The drive
   mechanism opens this gate to extract the tape leader. The tape
   leader has an oval hole in it which the drive uses to !S:hook!"
   the tape. The take-up spool is located inside the tape drive. All
   the other tape cartridges listed here (9 track tapes are the only
   exception) have both the supply and take-up spools located inside
   the tape cartridge itself.

   Data throughput is approximately 1.5 MB/s, three times the
   throughput of 4mm, 8mm, or QIC tape drives. Data capacities range
   from 10 GB to 20 GB for a single drive. Drives are available in
   both multi-tape changers and multi-tape, multi-drive tape
   libraries containing from 5 to 900 tapes over 1 to 20 drives,
   providing from 50 GB to 9 TB of storage.

   With compression, DLT Type IV format supports up to 70 GB
   capacity.

   Data is recorded onto the tape in tracks parallel to the direction
   of travel (just like QIC tapes). Two tracks are written at once.
   Read/write head lifetimes are relatively long; once the tape stops
   moving, there is no relative motion between the heads and the
   tape.

     --------------------------------------------------------------

  18.9.5. AIT

   AIT is a new format from Sony, and can hold up to 50 GB (with
   compression) per tape. The tapes contain memory chips which retain
   an index of the tape's contents. This index can be rapidly read by
   the tape drive to determine the position of files on the tape,
   instead of the several minutes that would be required for other
   tapes. Software such as SAMS:Alexandria can operate forty or more
   AIT tape libraries, communicating directly with the tape's memory
   chip to display the contents on screen, determine what files were
   backed up to which tape, locate the correct tape, load it, and
   restore the data from the tape.

   Libraries like this cost in the region of $20,000, pricing them a
   little out of the hobbyist market.

     --------------------------------------------------------------

  18.9.6. Using a New Tape for the First Time

   The first time that you try to read or write a new, completely
   blank tape, the operation will fail. The console messages should
   be similar to:

 sa0(ncr1:4:0): NOT READY asc:4,1
 sa0(ncr1:4:0):  Logical unit is in process of becoming ready

   The tape does not contain an Identifier Block (block number 0).
   All QIC tape drives since the adoption of QIC-525 standard write
   an Identifier Block to the tape. There are two solutions:

     * mt fsf 1 causes the tape drive to write an Identifier Block to
       the tape.

     * Use the front panel button to eject the tape.

       Re-insert the tape and dump data to the tape.

       dump will report !S:DUMP: End of tape detected!" and the
       console will show: !S:HARDWARE FAILURE info:280 asc:80,96!".

       rewind the tape using: mt rewind.

       Subsequent tape operations are successful.

     --------------------------------------------------------------

18.10. Backups to Floppies

  18.10.1. Can I Use Floppies for Backing Up My Data?

   Floppy disks are not really a suitable media for making backups
   as:

     * The media is unreliable, especially over long periods of time.

     * Backing up and restoring is very slow.

     * They have a very limited capacity (the days of backing up an
       entire hard disk onto a dozen or so floppies has long since
       passed).

   However, if you have no other method of backing up your data then
   floppy disks are better than no backup at all.

   If you do have to use floppy disks then ensure that you use good
   quality ones. Floppies that have been lying around the office for
   a couple of years are a bad choice. Ideally use new ones from a
   reputable manufacturer.

     --------------------------------------------------------------

  18.10.2. So How Do I Backup My Data to Floppies?

   The best way to backup to floppy disk is to use tar(1) with the -M
   (multi volume) option, which allows backups to span multiple
   floppies.

   To backup all the files in the current directory and sub-directory
   use this (as root):

 # tar Mcvf /dev/fd0 *

   When the first floppy is full tar(1) will prompt you to insert the
   next volume (because tar(1) is media independent it refers to
   volumes; in this context it means floppy disk).

 Prepare volume #2 for /dev/fd0 and hit return:

   This is repeated (with the volume number incrementing) until all
   the specified files have been archived.

     --------------------------------------------------------------

  18.10.3. Can I Compress My Backups?

   Unfortunately, tar(1) will not allow the -z option to be used for
   multi-volume archives. You could, of course, gzip(1) all the
   files, tar(1) them to the floppies, then gunzip(1) the files
   again!

     --------------------------------------------------------------

  18.10.4. How Do I Restore My Backups?

   To restore the entire archive use:

 # tar Mxvf /dev/fd0

   There are two ways that you can use to restore only specific
   files. First, you can start with the first floppy and use:

 # tar Mxvf /dev/fd0 filename

   The utility tar(1) will prompt you to insert subsequent floppies
   until it finds the required file.

   Alternatively, if you know which floppy the file is on then you
   can simply insert that floppy and use the same command as above.
   Note that if the first file on the floppy is a continuation from
   the previous one then tar(1) will warn you that it cannot restore
   it, even if you have not asked it to!

     --------------------------------------------------------------

18.11. Backup Strategies

   Original work by Lowell Gilbert.

   The first requirement in devising a backup plan is to make sure
   that all of the following problems are covered:

     * Disk failure

     * Accidental file deletion

     * Random file corruption

     * Complete machine destruction (e.g. fire), including
       destruction of any on-site backups.

   It is perfectly possible that some systems will be best served by
   having each of these problems covered by a completely different
   technique. Except for strictly personal systems with very
   low-value data, it is unlikely that one technique would cover all
   of them.

   Some of the techniques in the toolbox are:

     * Archives of the whole system, backed up onto permanent media
       offsite. This actually provides protection against all of the
       possible problems listed above, but is slow and inconvenient
       to restore from. You can keep copies of the backups onsite
       and/or online, but there will still be inconveniences in
       restoring files, especially for non-privileged users.

     * Filesystem snapshots. This is really only helpful in the
       accidental file deletion scenario, but it can be very helpful
       in that case, and is quick and easy to deal with.

     * Copies of whole filesystems and/or disks (e.g. periodic rsync
       of the whole machine). This is generally most useful in
       networks with unique requirements. For general protection
       against disk failure, it is usually inferior to RAID. For
       restoring accidentally deleted files, it can be comparable to
       UFS snapshots, but that depends on your preferences.

     * RAID. Minimizes or avoids downtime when a disk fails. At the
       expense of having to deal with disk failures more often
       (because you have more disks), albeit at a much lower urgency.

     * Checking fingerprints of files. The mtree(8) utility is very
       useful for this. Although it is not a backup technique, it
       helps guarantee that you will notice when you need to resort
       to your backups. This is particularly important for offline
       backups, and should be checked periodically.

   It is quite easy to come up with even more techniques, many of
   them variations on the ones listed above. Specialized requirements
   will usually lead to specialized techniques (for example, backing
   up a live database usually requires a method particular to the
   database software as an intermediate step). The important thing is
   to know what dangers you want to protect against, and how you will
   handle each.

     --------------------------------------------------------------

18.12. Backup Basics

   The three major backup programs are dump(8), tar(1), and cpio(1).

     --------------------------------------------------------------

  18.12.1. Dump and Restore

   The traditional UNIX backup programs are dump and restore. They
   operate on the drive as a collection of disk blocks, below the
   abstractions of files, links and directories that are created by
   the file systems. dump backs up an entire file system on a device.
   It is unable to backup only part of a file system or a directory
   tree that spans more than one file system. dump does not write
   files and directories to tape, but rather writes the raw data
   blocks that comprise files and directories.

     -a`: If you use dump on your root directory, you would not back
     up /home, /usr or many other directories since these are
     typically mount points for other file systems or symbolic links
     into those file systems.

   dump has quirks that remain from its early days in Version 6 of
   AT&T UNIX (circa 1975). The default parameters are suitable for
   9-track tapes (6250 bpi), not the high-density media available
   today (up to 62,182 ftpi). These defaults must be overridden on
   the command line to utilize the capacity of current tape drives.

   It is also possible to backup data across the network to a tape
   drive attached to another computer with rdump and rrestore. Both
   programs rely upon rcmd(3) and ruserok(3) to access the remote
   tape drive. Therefore, the user performing the backup must be
   listed in the .rhosts file on the remote computer. The arguments
   to rdump and rrestore must be suitable to use on the remote
   computer. When rdumping from a FreeBSD computer to an Exabyte tape
   drive connected to a Sun called komodo, use:

 # /sbin/rdump 0dsbfu 54000 13000 126 komodo:/dev/nsa8 /dev/da0a 2>&1

   Beware: there are security implications to allowing .rhosts
   authentication. Evaluate your situation carefully.

   It is also possible to use dump and restore in a more secure
   fashion over ssh.

   1/2d"O 18-1. Using dump over ssh

 # /sbin/dump -0uan -f - /usr | gzip -2 | ssh -c blowfish \
           targetuser@targetmachine.example.com dd of=/mybigfiles/dump-usr-l0.gz

   Or using dump's built-in method, setting the environment variable
   RSH:

   1/2d"O 18-2. Using dump over ssh with RSH set

 # RSH=/usr/bin/ssh /sbin/dump -0uan -f targetuser@targetmachine.example.com:/dev/sa0 /usr

     --------------------------------------------------------------

  18.12.2. tar

   tar(1) also dates back to Version 6 of AT&T UNIX (circa 1975). tar
   operates in cooperation with the file system; it writes files and
   directories to tape. tar does not support the full range of
   options that are available from cpio(1), but it does not require
   the unusual command pipeline that cpio uses.

   On FreeBSD 5.3 and later, both GNU tar and the default bsdtar are
   available. The GNU version can be invoked with gtar. It supports
   remote devices using the same syntax as rdump. To tar to an
   Exabyte tape drive connected to a Sun called komodo, use:

 # /usr/bin/gtar cf komodo:/dev/nsa8 . 2>&1

   The same could be accomplished with bsdtar by using a pipeline and
   rsh to send the data to a remote tape drive.

 # tar cf - . | rsh hostname dd of=tape-device obs=20b

   If you are worried about the security of backing up over a network
   you should use the ssh command instead of rsh.

     --------------------------------------------------------------

  18.12.3. cpio

   cpio(1) is the original UNIX file interchange tape program for
   magnetic media. cpio has options (among many others) to perform
   byte-swapping, write a number of different archive formats, and
   pipe the data to other programs. This last feature makes cpio an
   excellent choice for installation media. cpio does not know how to
   walk the directory tree and a list of files must be provided
   through stdin.

   cpio does not support backups across the network. You can use a
   pipeline and rsh to send the data to a remote tape drive.

 # for f in directory_list; do
 find $f >> backup.list
 done
 # cpio -v -o --format=newc < backup.list | ssh user@host "cat > backup_device"

   Where directory_list is the list of directories you want to back
   up, user@host is the user/hostname combination that will be
   performing the backups, and backup_device is where the backups
   should be written to (e.g., /dev/nsa0).

     --------------------------------------------------------------

  18.12.4. pax

   pax(1) is IEEE/POSIX's answer to tar and cpio. Over the years the
   various versions of tar and cpio have gotten slightly
   incompatible. So rather than fight it out to fully standardize
   them, POSIX created a new archive utility. pax attempts to read
   and write many of the various cpio and tar formats, plus new
   formats of its own. Its command set more resembles cpio than tar.

     --------------------------------------------------------------

  18.12.5. Amanda

   Amanda (Advanced Maryland Network Disk Archiver) is a
   client/server backup system, rather than a single program. An
   Amanda server will backup to a single tape drive any number of
   computers that have Amanda clients and a network connection to the
   Amanda server. A common problem at sites with a number of large
   disks is that the length of time required to backup to data
   directly to tape exceeds the amount of time available for the
   task. Amanda solves this problem. Amanda can use a !S:holding
   disk!" to backup several file systems at the same time. Amanda
   creates !S:archive sets!": a group of tapes used over a period of
   time to create full backups of all the file systems listed in
   Amanda's configuration file. The !S:archive set!" also contains
   nightly incremental (or differential) backups of all the file
   systems. Restoring a damaged file system requires the most recent
   full backup and the incremental backups.

   The configuration file provides fine control of backups and the
   network traffic that Amanda generates. Amanda will use any of the
   above backup programs to write the data to tape. Amanda is
   available as either a port or a package, it is not installed by
   default.

     --------------------------------------------------------------

  18.12.6. Do Nothing

   !S:Do nothing!" is not a computer program, but it is the most
   widely used backup strategy. There are no initial costs. There is
   no backup schedule to follow. Just say no. If something happens to
   your data, grin and bear it!

   If your time and your data is worth little to nothing, then !S:Do
   nothing!" is the most suitable backup program for your computer.
   But beware, UNIX is a useful tool, you may find that within six
   months you have a collection of files that are valuable to you.

   !S:Do nothing!" is the correct backup method for /usr/obj and
   other directory trees that can be exactly recreated by your
   computer. An example is the files that comprise the HTML or
   PostScript version of this Handbook. These document formats have
   been created from SGML input files. Creating backups of the HTML
   or PostScript files is not necessary. The SGML files are backed up
   regularly.

     --------------------------------------------------------------

  18.12.7. Which Backup Program Is Best?

   dump(8) Period. Elizabeth D. Zwicky torture tested all the backup
   programs discussed here. The clear choice for preserving all your
   data and all the peculiarities of UNIX file systems is dump.
   Elizabeth created file systems containing a large variety of
   unusual conditions (and some not so unusual ones) and tested each
   program by doing a backup and restore of those file systems. The
   peculiarities included: files with holes, files with holes and a
   block of nulls, files with funny characters in their names,
   unreadable and unwritable files, devices, files that change size
   during the backup, files that are created/deleted during the
   backup and more. She presented the results at LISA V in Oct. 1991.
   See torture-testing Backup and Archive Programs.

     --------------------------------------------------------------

  18.12.8. Emergency Restore Procedure

    18.12.8.1. Before the Disaster

   There are only four steps that you need to perform in preparation
   for any disaster that may occur.

   First, print the bsdlabel from each of your disks (e.g. bsdlabel
   da0 | lpr), your file system table (/etc/fstab) and all boot
   messages, two copies of each.

   Second, determine that the boot and fix-it floppies (boot.flp and
   fixit.flp) have all your devices. The easiest way to check is to
   reboot your machine with the boot floppy in the floppy drive and
   check the boot messages. If all your devices are listed and
   functional, skip on to step three.

   Otherwise, you have to create two custom bootable floppies which
   have a kernel that can mount all of your disks and access your
   tape drive. These floppies must contain: fdisk, bsdlabel, newfs,
   mount, and whichever backup program you use. These programs must
   be statically linked. If you use dump, the floppy must contain
   restore.

   Third, create backup tapes regularly. Any changes that you make
   after your last backup may be irretrievably lost. Write-protect
   the backup tapes.

   Fourth, test the floppies (either boot.flp and fixit.flp or the
   two custom bootable floppies you made in step two.) and backup
   tapes. Make notes of the procedure. Store these notes with the
   bootable floppy, the printouts and the backup tapes. You will be
   so distraught when restoring that the notes may prevent you from
   destroying your backup tapes (How? In place of tar xvf /dev/sa0,
   you might accidentally type tar cvf /dev/sa0 and over-write your
   backup tape).

   For an added measure of security, make bootable floppies and two
   backup tapes each time. Store one of each at a remote location. A
   remote location is NOT the basement of the same office building. A
   number of firms in the World Trade Center learned this lesson the
   hard way. A remote location should be physically separated from
   your computers and disk drives by a significant distance.

   1/2d"O 18-3. A Script for Creating a Bootable Floppy

 #!/bin/sh
 #
 # create a restore floppy
 #
 # format the floppy
 #
 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

 # place boot blocks on the floppy
 #
 bsdlabel -w -B /dev/fd0c fd1440

 #
 # newfs the one and only partition
 #
 newfs -t 2 -u 18 -l 1 -c 40 -i 5120 -m 5 -o space /dev/fd0a

 #
 # mount the new floppy
 #
 mount /dev/fd0a /mnt

 #
 # create required directories
 #
 mkdir /mnt/dev
 mkdir /mnt/bin
 mkdir /mnt/sbin
 mkdir /mnt/etc
 mkdir /mnt/root
 mkdir /mnt/mnt                  # for the root partition
 mkdir /mnt/tmp
 mkdir /mnt/var

 #
 # populate the directories
 #
 if [ ! -x /sys/compile/MINI/kernel ]
 then
          cat &lt;&lt; EOM
 The MINI kernel does not exist, please create one.
 Here is an example config file:
 #
 # MINI -- A kernel to get FreeBSD onto a disk.
 #
 machine         "i386"
 cpu             "I486_CPU"
 ident           MINI
 maxusers        5

 options         INET                    # needed for _tcp _icmpstat _ipstat
                                         #            _udpstat _tcpstat _udb
 options         FFS                     #Berkeley Fast File System
 options         FAT_CURSOR              #block cursor in syscons or pccons
 options         SCSI_DELAY=15           #Be pessimistic about Joe SCSI device
 options         NCONS=2                 #1 virtual consoles
 options         USERCONFIG              #Allow user configuration with -c XXX

 config          kernel  root on da0 swap on da0 and da1 dumps on da0

 device          isa0
 device          pci0

 device          fdc0    at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr
 device          fd0     at fdc0 drive 0

 device          ncr0

 device          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            # required by INET
 pseudo-device   gzip            # Exec gzipped a.out's
 EOM
          exit 1
 fi

 cp -f /sys/compile/MINI/kernel /mnt

 gzip -c -best /sbin/init &gt; /mnt/sbin/init
 gzip -c -best /sbin/fsck &gt; /mnt/sbin/fsck
 gzip -c -best /sbin/mount &gt; /mnt/sbin/mount
 gzip -c -best /sbin/halt &gt; /mnt/sbin/halt
 gzip -c -best /sbin/restore &gt; /mnt/sbin/restore

 gzip -c -best /bin/sh &gt; /mnt/bin/sh
 gzip -c -best /bin/sync &gt; /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

 #
 # create the devices nodes
 #
 cd /mnt/dev
 ./MAKEDEV std
 ./MAKEDEV da0
 ./MAKEDEV da1
 ./MAKEDEV da2
 ./MAKEDEV sa0
 ./MAKEDEV pty0
 cd /

 #
 # create minimum file system table
 #
 cat &gt; /mnt/etc/fstab &lt;&lt;EOM
 /dev/fd0a    /    ufs    rw  1  1
 EOM

 #
 # create minimum passwd file
 #
 cat &gt; /mnt/etc/passwd &lt;&lt;EOM
 root:*:0:0:Charlie &:/root:/bin/sh
 EOM

 cat &gt; /mnt/etc/master.passwd &lt;&lt;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

 #
 # umount the floppy and inform the user
 #
 /sbin/umount /mnt
 echo "The floppy has been unmounted and is now ready."

     --------------------------------------------------------------

    18.12.8.2. After the Disaster

   The key question is: did your hardware survive? You have been
   doing regular backups so there is no need to worry about the
   software.

   If the hardware has been damaged, the parts should be replaced
   before attempting to use the computer.

   If your hardware is okay, check your floppies. If you are using a
   custom boot floppy, boot single-user (type -s at the boot:
   prompt). Skip the following paragraph.

   If you are using the boot.flp and fixit.flp floppies, keep
   reading. Insert the boot.flp floppy in the first floppy drive and
   boot the computer. The original install menu will be displayed on
   the screen. Select the Fixit--Repair mode with CDROM or floppy.
   option. Insert the fixit.flp when prompted. restore and the other
   programs that you need are located in /mnt2/rescue (/mnt2/stand
   for FreeBSD versions older than 5.2).

   Recover each file system separately.

   Try to mount (e.g. mount /dev/da0a /mnt) the root partition of
   your first disk. If the bsdlabel was damaged, use bsdlabel to
   re-partition and label the disk to match the label that you
   printed and saved. Use newfs to re-create the file systems.
   Re-mount the root partition of the floppy read-write (mount -u -o
   rw /mnt). Use your backup program and backup tapes to recover the
   data for this file system (e.g. restore vrf /dev/sa0). Unmount the
   file system (e.g. umount /mnt). Repeat for each file system that
   was damaged.

   Once your system is running, backup your data onto new tapes.
   Whatever caused the crash or data loss may strike again. Another
   hour spent now may save you from further distress later.

     --------------------------------------------------------------

18.13. Network, Memory, and File-Backed File Systems

   Reorganized and enhanced by Marc Fonvieille.

   Aside from the disks you physically insert into your computer:
   floppies, CDs, hard drives, and so forth; other forms of disks are
   understood by FreeBSD - the virtual disks.

   These include network file systems such as the Network File System
   and Coda, memory-based file systems and file-backed file systems.

   According to the FreeBSD version you run, you will have to use
   different tools for creation and use of file-backed and
   memory-based file systems.

     -a`: Use devfs(5) to allocate device nodes transparently for the
     user.

     --------------------------------------------------------------

  18.13.1. File-Backed File System

   The utility mdconfig(8) is used to configure and enable memory
   disks, md(4), under FreeBSD. To use mdconfig(8), you have to load
   md(4) module or to add the support in your kernel configuration
   file:

 device md

   The mdconfig(8) command supports three kinds of memory backed
   virtual disks: memory disks allocated with malloc(9), memory disks
   using a file or swap space as backing. One possible use is the
   mounting of floppy or CD images kept in files.

   To mount an existing file system image:

   1/2d"O 18-4. Using mdconfig to Mount an Existing File System Image

 # mdconfig -a -t vnode -f diskimage -u 0
 # mount /dev/md0 /mnt

   To create a new file system image with mdconfig(8):

   1/2d"O 18-5. Creating a New File-Backed Disk with mdconfig

 # dd if=/dev/zero of=newimage bs=1k count=5k
 5120+0 records in
 5120+0 records out
 # mdconfig -a -t vnode -f newimage -u 0
 # bsdlabel -w md0 auto
 # newfs md0a
 /dev/md0a: 5.0MB (10224 sectors) block size 16384, fragment size 2048
         using 4 cylinder groups of 1.25MB, 80 blks, 192 inodes.
 super-block backups (for fsck -b #) at:
  160, 2720, 5280, 7840
 # mount /dev/md0a /mnt
 # df /mnt
 Filesystem 1K-blocks Used Avail Capacity  Mounted on
 /dev/md0a       4710    4  4330     0%    /mnt

   If you do not specify the unit number with the -u option,
   mdconfig(8) will use the md(4) automatic allocation to select an
   unused device. The name of the allocated unit will be output on
   stdout like md4. For more details about mdconfig(8), please refer
   to the manual page.

   The utility mdconfig(8) is very useful, however it asks many
   command lines to create a file-backed file system. FreeBSD also
   comes with a tool called mdmfs(8), this program configures a md(4)
   disk using mdconfig(8), puts a UFS file system on it using
   newfs(8), and mounts it using mount(8). For example, if you want
   to create and mount the same file system image as above, simply
   type the following:

   1/2d"O 18-6. Configure and Mount a File-Backed Disk with mdmfs

 # dd if=/dev/zero of=newimage bs=1k count=5k
 5120+0 records in
 5120+0 records out
 # mdmfs -F newimage -s 5m md0 /mnt
 # df /mnt
 Filesystem 1K-blocks Used Avail Capacity  Mounted on
 /dev/md0        4718    4  4338     0%    /mnt

   If you use the option md without unit number, mdmfs(8) will use
   md(4) auto-unit feature to automatically select an unused device.
   For more details about mdmfs(8), please refer to the manual page.

     --------------------------------------------------------------

  18.13.2. Memory-Based File System

   For a memory-based file system the !S:swap backing!" should
   normally be used. Using swap backing does not mean that the memory
   disk will be swapped out to disk by default, but merely that the
   memory disk will be allocated from a memory pool which can be
   swapped out to disk if needed. It is also possible to create
   memory-based disk which are malloc(9) backed, but using malloc
   backed memory disks, especially large ones, can result in a system
   panic if the kernel runs out of memory.

   1/2d"O 18-7. Creating a New Memory-Based Disk with mdconfig

 # mdconfig -a -t malloc -s 5m -u 1
 # newfs -U md1
 /dev/md1: 5.0MB (10240 sectors) block size 16384, fragment size 2048
         using 4 cylinder groups of 1.27MB, 81 blks, 256 inodes.
         with soft updates
 super-block backups (for fsck -b #) at:
  32, 2624, 5216, 7808
 # mount /dev/md1 /mnt
 # df /mnt
 Filesystem 1K-blocks Used Avail Capacity  Mounted on
 /dev/md1        4846    2  4458     0%    /mnt

   1/2d"O 18-8. Creating a New Memory-Based Disk with mdmfs

 # mdmfs -M -s 5m md2 /mnt
 # df /mnt
 Filesystem 1K-blocks Used Avail Capacity  Mounted on
 /dev/md2        4846    2  4458     0%    /mnt

   Instead of using a malloc(9) backed file system, it is possible to
   use swap, for that just replace malloc with swap in the command
   line of mdconfig(8). The mdmfs(8) utility by default (without -M)
   creates a swap-based disk. For more details, please refer to
   mdconfig(8) and mdmfs(8) manual pages.

     --------------------------------------------------------------

  18.13.3. Detaching a Memory Disk from the System

   When a memory-based or file-based file system is not used, you
   should release all resources to the system. The first thing to do
   is to unmount the file system, then use mdconfig(8) to detach the
   disk from the system and release the resources.

   For example to detach and free all resources used by /dev/md4:

 # mdconfig -d -u 4

   It is possible to list information about configured md(4) devices
   in using the command mdconfig -l.

     --------------------------------------------------------------

18.14. File System Snapshots

   Contributed by Tom Rhodes.

   FreeBSD offers a feature in conjunction with Soft Updates: File
   system snapshots.

   Snapshots allow a user to create images of specified file systems,
   and treat them as a file. Snapshot files must be created in the
   file system that the action is performed on, and a user may create
   no more than 20 snapshots per file system. Active snapshots are
   recorded in the superblock so they are persistent across unmount
   and remount operations along with system reboots. When a snapshot
   is no longer required, it can be removed with the standard rm(1)
   command. Snapshots may be removed in any order, however all the
   used space may not be acquired because another snapshot will
   possibly claim some of the released blocks.

   The un-alterable snapshot file flag is set by mksnap_ffs(8) after
   initial creation of a snapshot file. The unlink(1) command makes
   an exception for snapshot files since it allows them to be
   removed.

   Snapshots are created with the mount(8) command. To place a
   snapshot of /var in the file /var/snapshot/snap use the following
   command:

 # mount -u -o snapshot /var/snapshot/snap /var

   Alternatively, you can use mksnap_ffs(8) to create a snapshot:

 # mksnap_ffs /var /var/snapshot/snap

   One can find snapshot files on a file system (e.g. /var) by using
   the find(1) command:

 # find /var -flags snapshot

   Once a snapshot has been created, it has several uses:

     * Some administrators will use a snapshot file for backup
       purposes, because the snapshot can be transfered to CDs or
       tape.

     * File integrity, fsck(8) may be ran on the snapshot. Assuming
       that the file system was clean when it was mounted, you should
       always get a clean (and unchanging) result. This is
       essentially what the background fsck(8) process does.

     * Run the dump(8) utility on the snapshot. A dump will be
       returned that is consistent with the file system and the
       timestamp of the snapshot. dump(8) can also take a snapshot,
       create a dump image and then remove the snapshot in one
       command using the -L flag.

     * mount(8) the snapshot as a frozen image of the file system. To
       mount(8) the snapshot /var/snapshot/snap run:

 # mdconfig -a -t vnode -f /var/snapshot/snap -u 4
 # mount -r /dev/md4 /mnt

   You can now walk the hierarchy of your frozen /var file system
   mounted at /mnt. Everything will initially be in the same state it
   was during the snapshot creation time. The only exception is that
   any earlier snapshots will appear as zero length files. When the
   use of a snapshot has delimited, it can be unmounted with:

 # umount /mnt
 # mdconfig -d -u 4

   For more information about softupdates and file system snapshots,
   including technical papers, you can visit Marshall Kirk McKusick's
   website at http://www.mckusick.com/.

     --------------------------------------------------------------

18.15. -oI-oD--aAAP:!DEGtAB(Quota)

   -oI-oD-DEGtAB(Quota)A:Y(c)oS:@.~"t^2ICURW-a-o?iYENIYEN\-`a!A
   YENiYENHYENI"O"i"IYENI-aI(c)I,s^2O-a-oYENiYENI-aAAP:!CURjCURp!A(c)I-aIAE(R)
   *-a-oA` 1/4AE|h^1e!C
   ^3oYEN\-`a^3q+-`YENI|b|hCURH|@YENI-a-o"t^2IAo^1OCURW!A
   |]NOTDEGn"i|U"IYENI-aI(c)I|U,s^2O(c)O-`a^1BYENI-a-o"t^2I,e. 1/2!C
   |p|^1CUR@"O!A'NYENiA
   *S:K-oI-oD--aAAP:!^3QNOTY"IYENI-aI(c)INOTY,s^2OYENth^3!-O-oE!C

     --------------------------------------------------------------

  18.15.1. +-OYENI-oI-oD-DEGtAB

   |bYENI-oI-oD-DEGtABCURS:<<e!A 1/2D-YENy 1/2T>>{ kernel
   CURw,g|^3S:@NOTUAo:^3](c)w!ACUR]'NNOTO kernel
   ^3](c)wAEn|^3CURU+-^3o|ae!G

 options QUOTA

   ^1w^3]-a-o GENERIC kernel "ACUR-L-.|YEN[CURW^3oP:u!A
   (c)OYENHYn+-OYENI'NYEN^2>>YYEN[CURW!A"A<<.s 1/2sA:P:!B|w,E
   kernel!C kernel ^3](c)w^3!CURAYENiDEGN 3/4\ uU 8 ^3^1
   -a-o>>!(c)u!C

   +-uuU'NNOTO|b /etc/rc.conf ^3](c)w+-ODEGE-oI-oD-DEGtAB!C 
   1/2D-YEN[CURWCURU|C^3o|ae!G

 enable_quotas="YES"

   NOTDEGCURF-`aS:oS:^1u
   1/2-a-o+-+--oTH-oI-oD-DEGtAB-a-o+-ODEGE!AAU|^3CUR@O^3](c)wYENiYENHYENI!C
   ^3q+-`P:} 3/4-:(R)E!A quotacheck(8) u{|!.|AENOTd|UAE(R)
   *"t^2ICURW-a-oDEGtAB!C quotacheck(8) YENiYENH
   1/2T<<ODEGtAB,e(R)AE(R)w-a-o,e(R)AE>>P^1e>>UAE(R)
   *"t^2I-a-o,e(R)AE|^3^2AA|X!C |y^3oYEN\-`aCUR].||bP:}
   3/4-:(R)E!A.|^1i+-ODEGE(R)EP:!^3y|"NOTU.i(c)uAAa-a-o 1/4vAAT!C
   Y.Q,o^1L^3o"BAEJ!A<<hYENiYENH|b /etc/rc.conf YEN[CURW!G

 check_quotas="NO"

   ^3I<<a!AnDEGO+-oS:i /etc/fstab "O+-OYENIYENHAE(R)
   *"t^2INOTDEG^1iP:H-a-o-oI-oD-DEGtABYEN\-`a!C
   CUR]YENiYENH+-OYENIDEGw^1i"IYENI-aI(c)I,s^2O!A
   (c)I-aI"a-aINOTO|^3CURS:-a-o-oI-oD-DEGtAB!C

   Yn+-OYENIDEGw^1i"IYENI-aI-a-oDEGtAB!AYENiYENH|b /etc/fstab
   CUR-on^3](c)w-a-oAE(R) *"t^2IYEN[CURW userquota ?iP:u!C CURn|p!G

 /dev/da1s2g   /home    ufs rw,userquota 1 2

   |P^2zYn+-OYENIDEGw^1i,s^2O-a-oDEGtAB!A<<hS:aee-a-o userquota '<<|"
   groupquota S:YYENi!C |OYn"a-aI|P(R)E+-OYENI!A "-o>>o<<hNOTO!G

 /dev/da1s2g    /home    ufs rw,userquota,groupquota 1 2

   DEGw^1i"IYENI-aIYENHCURI,s^2O-a-o-oI-oD-DEGtAB^3](c)wAE!A^1w^3]CURAS:O.|(c)n|b,OAE(R)
   *"t^2I(R)UYENO/?y-a-o quota.user YENHCURI quota.group !C
   ^2O,`^3!CURA 1/2D-DEGN 3/4\ fstab(5)!C Ao:uM fstab(5)
   '-L-"`iYENiYENHNOTDEGDEGtAB^3](c)wAE<<u:(c)w"a:YENL|aCURe!A|y"ACUR-L-<<O/A:^3|p|^1S:@!A
   |]NOTDEG|U-oO/-oI-oD-DEGtAB-oTH^2zCURu"a"ACUR-L-"-L-+-o^1i^3o"C,^1w^3]E-`aAHCURS:
   1/4u(c)EAAU:CURAE!C

   +-uCURU"O'NYENiYENHYENI.s kernel "O<<P:} 3/4-:!C /etc/rc
   .||UDEGEDEGo|aeNOTUAo:<<u:YENOYENH^1i /etc/fstab
   |^3^3](c)wDEGtAB-oTH^2z-a-o^3!CURA!AS:@-a`i(c)l^3](c)w!C
   (c)OYENH"ACUR-L->>Yn^3vCUR@CURaDEGE^2-L-YENINOTUAo:-aAA-a-oDEGtAB^3](c)wAE!C

   YEN?+-` 3/4THS:@^1Lu{CURCUR!A"ACUR-L->>YnCURaDEGEDEGo|ae
   quotacheck(8)!Bquotaon(8) !Bquotaoff(8) ^3o"C,<<u:YENO!C
   CUR-L-^1L!AYnS:o 1/4o+-xNOTUAo: 3/4THS:@CURe|!-a-o,U:!A
   (c)I^3\YENiYENH 3/4\AA-aNOTUAo:-a-o manual  1/2uCURW>>!(c)u!C

     --------------------------------------------------------------

  18.15.2. ^3](c)wDEGtAB"i

   CUR@YEN^1P:}(c)l+-OYENIDEGtAB-oTH^2zCURS:<<a!A 1/2D-DEGO+-o
   1/2T>>{NOTOS:_|^3-u-a-o+-OYENI!C
   YENiYENHYEN'CURU|C<<u:YENO"OS:@A^2^3aeAENOTd!G

 # quota -v

   A^3,OYENiYENHNOTY"`i|^3Ao:|UAE(R) *"t^2I-a-oDEGtABP:q!A
   YENHCURI^2{|b"IYENIP:q-a-o-oKnDEGT(R)S:!C

   ^2{|bYENiYENHP:}(c)lYENI edquota(8)
   "O^3](c)w|U-oI-oD-DEGtAB-a-o"i!C

   |^3'X-oO/?iP:uYENiYENHYENI"O"i"IYENI-aI(c)I,s^2O(c)O-`a^1BYENI-a-o-oI-oD--aAAP:!!A
   YENHCURI(c)O-`a<<O/YENss-a-oAE(R) * 1/4AEP:q|h^1e!C
   YENiYENH"I-oI-oD--aAAP:!(block DEGtAB)(c)IAE(R) * 1/4AEP:q (inode
   DEGtAB)!A(c)I-aI.fDEGt"a-aICUR@DEG_^3](c)w!C
   |O"C-oO/"iAUYENiYENH^2OCURANOTDEG"aAth!G hard(uw(c)E)CURW!Bsoft(
   1/4u(c)E)CURW!C

   uw(c)ECURWNOTOCUR-L--`aP:W^1L-a-o!C
   CUR@YEN^1"IYENI-aI^1F"`iuw(c)ECURW(R)E!A 'NuL-ak|b,OAE(R)
   *"t^2ICURWA:~A:o"IYENIS:o|h-a-o"IYENI-aAAP:!CURF!C
   A|"O"O>>!!AY|^3|`i"IYENI-aI-a-ouw(c)ECURWNOTDEG 500
   KB!A|OYENO/<<eYENICURF 490 KB!A "-o>>oYENL'NYENu-`a|A|hYENI 10 KB
   |OCURw!AYn.s 1/4W-a-oAE(R) *|^3 11 KB 'N.|YEN-c-+-N!C

   uM|O!A
   1/4u(c)ECURW<<hYENiCUR^1^3\CUR@(c)w(R)EP:!CUR-o-a-oP:WAB"IYENI!A^3oNOTq'AP:!-oUNOTDEG
   grace period( 1/4e'A)!A^1w^3]ENOTOCUR@P:g!C
   Y"IYENI-aI<<uA:oP:WAB"IYENI"AP:WYENX grace period |O^1O'A!A<<h
   1/4u(c)ECURW'N.|A`aNOTDEGuw(c)ECURW!A
   |OCUR-L-CUR^1^3\,O"IYENI-aIA:~A:o.s 1/4W-aAAP:!!C -a
   1/2"`i,O"IYENI-aI-a-o-aAAP:!CURw,g^2M"`iS:C(c)o
   1/4u(c)ECURWCURS:<<a!ACUR~.|<<^3] grace period!C

   CURU+-<<hNOTO"IYENI edquota(8) -a-o"OCURl!C |bDEGo|ae edquota(8)
   (R)E!A.|P:iCURJ^3](c)w-oI-oD-DEGtABCURW-a-o 1/2s?e
   3/4^1CUR-o!A|U:(c)oNOTOthCUR@-oO/ 1/2s?e 3/4^1<<huo/+-z-a-o EDITOR
   Ao^1OAAU: 1/4AE|O(c)w!AY"S^3](c)w EDITOR -a-o,U:!A<<h.|YENI vi 
   1/2s?e 3/4^1!C

 # edquota -u test

 Quotas for user test:
 /usr: kbytes in use: 65, limits (soft = 50, hard = 75)
         inodes in use: 7, limits (soft = 50, hard = 60)
 /usr/var: kbytes in use: 0, limits (soft = 50, hard = 75)
         inodes in use: 0, limits (soft = 50, hard = 60)

   CUR@-e"O>>!!A"CO+-ODEGECURF-oI-oD-DEGtAB-a-oAE(R)
   *"t^2I^3-L-.||^3"a|ae^3](c)w!C ^2A:CUR@|aeNOTO block
   CURW!A|OYENtCUR@|ae<<hNOTO inode CURW!C
   YnS:oS:i-oI-oD-DEGtABCURW!AYENu>>Yn *S:i<<a+--a-o 1/4AEES:YYENi!C
   A|"O"O>>!!A n 1/4WYEN[^3o|`i"IYENI-aI-a-o block CURW^3!CURA!GS:a
   1/4u(c)ECURW 50  1/2ONOTDEG 500!A uw(c)ECURW<<hYENN 75  1/2ONOTDEG
   600 !AYENu>>Y *S:iCURU+-^3o|ae!G

 /usr: kbytes in use: 65, limits (soft = 50, hard = 75)

   S:iNOTDEGCURU|C!G

 /usr: kbytes in use: 65, limits (soft = 500, hard = 600)

   uM<<a|sAEA-:P:}<<a!A.s-a-oDEGtAB^3](c)w'N.|YENssS:YYENI(R)A:!C

   |^3(R)EO.|.QCUR@|,S:iCURj 1/2d^3o UID
   -a-o+-b,^1^3](c)w!A^3o(R)EYENiYENHYENI edquota(8) -a-o -p DEGN
   1/4AEYEN\-`a"OS:^1|"!C -oYENy!A S:aNOTYO+-b,^1
   1/2ONOTDEG.Qn-a-oNOTUAo:DEGtAB!AuM<<aYENiYENHYENI edquota -p
   protouser startuid-enduid CURS:Ath-a-oCURe|!"OS:i!C
   A|"O"O>>!!ADEG^2^3] test ^3o+-b,^1CURw,g^3](c)w|nNOTUAo:DEGtAB!A
   uM<<anS:i-a-o^1iP:HNOTDEG UID +-q 10,000 "`i 19,999 -a-o+-b,^1!A
   "-o>>o'NYENiYENHCURU|C<<u:YENO"O^3](c)w|P 1/4E-a-oDEGtAB!G

 # edquota -p test 10000-19999

   ^2O,`>>!(c)u 1/2D-DEGN 3/4\ edquota(8)!C

     --------------------------------------------------------------

  18.15.3. AENOTd-oI-oD-DEGtAB^3](c)w!B-oI-oD-"IYENIP:q

   YENiYENHYENI quota(1) (c)I repquota(8)
   "OAENOTd-oI-oD-DEGtAB^3](c)w!A YENHCURI-oI-oD-"IYENIP:q!C quota(1)
   YENiYENI"OAENOTd^3aeCUR@"IYENI-aI(c)I,s^2O-a-o-oI-oD-DEGtAB!B
   -oI-oD-"IYENIP:q!C
   CUR-L-^1LCUR@-e+-b,^1YENu-`aNOTd|UCURv-a-oYENHCURI|UCURv,s^2O-a-o-oI-oD-DEGtAB!B
   -oI-oD-"IYENIP:q!AYENu|^3"t^2I-oTH^2z-aI+-b,^1CUR~-`a^1iNOTY(c)O|^3"IYENI-aI!B
   ,s^2O-a-oDEGtAB^3](c)w>>P"IYENIP:q!C |O repquota(8)
   <<hYENiYENHNOTY"`i(c)O|^3CURw+-ODEGE-oI-oD-DEGtAB-a-oAE(R)
   *"t^2I^3](c)w!B-oI-oD-"IYENIP:q-oKn!C

   CURU+-"OCURl<<hNOTO|b"aO|^3DEGtAB^3](c)w-a-oAE(R) *"t^2ICURW!AYEN'
   quota -v -a-oAAaYENU:u^2-aG!G

 Disk quotas for user test (uid 1002):
      Filesystem  usage    quota   limit   grace   files   quota   limit   grace
            /usr      65*     50      75   5days       7      50      60
        /usr/var       0      50      75               0      50      60

   |bCURW+-^3o"OCURCUR!A,O"IYENI-aI|b /usr -a-o 1/4u(c)EDEGtABNOTO 50
   KB!A^1e>>UCURWCURw,gP:WAB|hYENI 15 KB!A|O grace period AU|^3 5
   CURN'N^1O'A!C  1/2D--a`.N^3oONOTP,^1 *
   NOTO-aiYENU:YENO/<<e,O"IYENI-aICURw,gP:WP:V"a:DEGtAB-a-o
   1/4u(c)ECURWCURF!C

   CUR@-e"O>>!!AY"IYENI-aI"A"S|^3YENI"`iNOTYOAE(R) *"t^2I!A
   "-o>>o'N-oa,OAE(R) *|^3+-OYENI-oI-oD-DEGtAB!A|b quota(1)
   CUR]CUR-L-.|AAaYENU:YENX"O!C |O -v DEGN
   1/4AE<<hYENiYENHS:a^3o"C,AE(R) *"t^2I^3-L-YENth^3!|CYENX"O!A
   CURn|pCURW"OCURCUR-a-o /usr/var!C

     --------------------------------------------------------------

  18.15.4. ^3z^1L NFS "IYENI-oI-oD-DEGtAB

   NFS server -oYYENiYENH+-j"iYENH quota
   subsystem(DEGtABCURl"t^2I)"OYENI-oI-oD-DEGtAB!C |O NFS client
   -oY<<hYENiYENH^3z^1L rpc.rquotad(8) daemon "OAAy quota(1)
   <<u:YENOS:`i"`iNOTUAo:DEGtAB,e(R)AE!ACUR]'NYENiYENHAAy client
   -oY-a-o"IYENI-aI^1iNOTY"a:DEGtAB-a-o^2Ip,e(R)AE!C

   Yn+-OYENI rpc.rquotad!AYENiYENH|b /etc/inetd.conf
   YEN[CURWCURU|CAth|u:^3](c)w!G

 rquotad/1      dgram rpc/udp wait root /usr/libexec/rpc.rquotad rpc.rquotad

   uM<<a<<+-O inetd S:YYENi!G

 # kill -HUP `cat /var/run/inetd.pid`

     --------------------------------------------------------------

18.16. Encrypting Disk Partitions

   Contributed by Lucky Green.

   FreeBSD offers excellent online protections against unauthorized
   data access. File permissions and Mandatory Access Control (MAC)
   (see uU 16 ^3^1) help prevent unauthorized third-parties from
   accessing data while the operating system is active and the
   computer is powered up. However, the permissions enforced by the
   operating system are irrelevant if an attacker has physical access
   to a computer and can simply move the computer's hard drive to
   another system to copy and analyze the sensitive data.

   Regardless of how an attacker may have come into possession of a
   hard drive or powered-down computer, both GEOM Based Disk
   Encryption (gbde) and geli cryptographic subsystems in FreeBSD are
   able to protect the data on the computer's file systems against
   even highly-motivated attackers with significant resources. Unlike
   cumbersome encryption methods that encrypt only individual files,
   gbde and geli transparently encrypt entire file systems. No
   cleartext ever touches the hard drive's platter.

     --------------------------------------------------------------

  18.16.1. Disk Encryption with gbde

    1. Become root

       Configuring gbde requires super-user privileges.

 % su -
 Password:

    2. Add gbde(4) Support to the Kernel Configuration File

       Add the following line to the kernel configuration file:

       options GEOM_BDE

       Rebuild the kernel as described in uU 8 ^3^1.

       Reboot into the new kernel.

     --------------------------------------------------------------

    18.16.1.1. Preparing the Encrypted Hard Drive

   The following example assumes that you are adding a new hard drive
   to your system that will hold a single encrypted partition. This
   partition will be mounted as /private. gbde can also be used to
   encrypt /home and /var/mail, but this requires more complex
   instructions which exceed the scope of this introduction.

    1. Add the New Hard Drive

       Install the new drive to the system as explained in uU 18.3
       ,`. For the purposes of this example, a new hard drive
       partition has been added as /dev/ad4s1c. The /dev/ad0s1*
       devices represent existing standard FreeBSD partitions on the
       example system.

 # ls /dev/ad*
 /dev/ad0        /dev/ad0s1b     /dev/ad0s1e     /dev/ad4s1
 /dev/ad0s1      /dev/ad0s1c     /dev/ad0s1f     /dev/ad4s1c
 /dev/ad0s1a     /dev/ad0s1d     /dev/ad4

    2. Create a Directory to Hold gbde Lock Files

 # mkdir /etc/gbde

       The gbde lock file contains information that gbde requires to
       access encrypted partitions. Without access to the lock file,
       gbde will not be able to decrypt the data contained in the
       encrypted partition without significant manual intervention
       which is not supported by the software. Each encrypted
       partition uses a separate lock file.

    3. Initialize the gbde Partition

       A gbde partition must be initialized before it can be used.
       This initialization needs to be performed only once:

 # gbde init /dev/ad4s1c -i -L /etc/gbde/ad4s1c

       gbde(8) will open your editor, permitting you to set various
       configuration options in a template. For use with UFS1 or
       UFS2, set the sector_size to 2048:

 $FreeBSD: src/sbin/gbde/template.txt,v 1.1 2002/10/20 11:16:13 phk Exp $
 #
 # Sector size is the smallest unit of data which can be read or written.
 # Making it too small decreases performance and decreases available space.
 # Making it too large may prevent filesystems from working.  512 is the
 # minimum and always safe.  For UFS, use the fragment size
 #
 sector_size     =       2048
 [...]

       gbde(8) will ask you twice to type the passphrase that should
       be used to secure the data. The passphrase must be the same
       both times. gbde's ability to protect your data depends
       entirely on the quality of the passphrase that you choose.
       [23]

       The gbde init command creates a lock file for your gbde
       partition that in this example is stored as /etc/gbde/ad4s1c.

         -a`.Ngbde lock files must be backed up together with the
         contents of any encrypted partitions. While deleting a lock
         file alone cannot prevent a determined attacker from
         decrypting a gbde partition, without the lock file, the
         legitimate owner will be unable to access the data on the
         encrypted partition without a significant amount of work
         that is totally unsupported by gbde(8) and its designer.

    4. Attach the Encrypted Partition to the Kernel

 # gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c

       You will be asked to provide the passphrase that you selected
       during the initialization of the encrypted partition. The new
       encrypted device will show up in /dev as /dev/device_name.bde:

 # ls /dev/ad*
 /dev/ad0        /dev/ad0s1b     /dev/ad0s1e     /dev/ad4s1
 /dev/ad0s1      /dev/ad0s1c     /dev/ad0s1f     /dev/ad4s1c
 /dev/ad0s1a     /dev/ad0s1d     /dev/ad4        /dev/ad4s1c.bde

    5. Create a File System on the Encrypted Device

       Once the encrypted device has been attached to the kernel, you
       can create a file system on the device. To create a file
       system on the encrypted device, use newfs(8). Since it is much
       faster to initialize a new UFS2 file system than it is to
       initialize the old UFS1 file system, using newfs(8) with the
       -O2 option is recommended.

 # newfs -U -O2 /dev/ad4s1c.bde

         -a`: The newfs(8) command must be performed on an attached
         gbde partition which is identified by a *.bde extension to
         the device name.

    6. Mount the Encrypted Partition

       Create a mount point for the encrypted file system.

 # mkdir /private

       Mount the encrypted file system.

 # mount /dev/ad4s1c.bde /private

    7. Verify That the Encrypted File System is Available

       The encrypted file system should now be visible to df(1) and
       be available for use.

 % df -H
 Filesystem        Size   Used  Avail Capacity  Mounted on
 /dev/ad0s1a      1037M    72M   883M     8%    /
 /devfs            1.0K   1.0K     0B   100%    /dev
 /dev/ad0s1f       8.1G    55K   7.5G     0%    /home
 /dev/ad0s1e      1037M   1.1M   953M     0%    /tmp
 /dev/ad0s1d       6.1G   1.9G   3.7G    35%    /usr
 /dev/ad4s1c.bde   150G   4.1K   138G     0%    /private

     --------------------------------------------------------------

    18.16.1.2. Mounting Existing Encrypted File Systems

   After each boot, any encrypted file systems must be re-attached to
   the kernel, checked for errors, and mounted, before the file
   systems can be used. The required commands must be executed as
   user root.

    1. Attach the gbde Partition to the Kernel

 # gbde attach /dev/ad4s1c -l /etc/gbde/ad4s1c

       You will be asked to provide the passphrase that you selected
       during initialization of the encrypted gbde partition.

    2. Check the File System for Errors

       Since encrypted file systems cannot yet be listed in
       /etc/fstab for automatic mounting, the file systems must be
       checked for errors by running fsck(8) manually before
       mounting.

 # fsck -p -t ffs /dev/ad4s1c.bde

    3. Mount the Encrypted File System

 # mount /dev/ad4s1c.bde /private

       The encrypted file system is now available for use.

     --------------------------------------------------------------

      18.16.1.2.1. Automatically Mounting Encrypted Partitions

   It is possible to create a script to automatically attach, check,
   and mount an encrypted partition, but for security reasons the
   script should not contain the gbde(8) password. Instead, it is
   recommended that such scripts be run manually while providing the
   password via the console or ssh(1).

   As of FreeBSD 5.2-RELEASE, there is a new rc.d script provided.
   Arguments for this script can be passed via rc.conf(5), for
   example:

 gbde_autoattach_all="YES"
 gbde_devices="ad4s1c"

   This will require that the gbde passphrase be entered at boot
   time. After typing the correct passphrase, the gbde encrypted
   partition will be mounted automatically. This can be very useful
   when using gbde on notebooks.

     --------------------------------------------------------------

    18.16.1.3. Cryptographic Protections Employed by gbde

   gbde(8) encrypts the sector payload using 128-bit AES in CBC mode.
   Each sector on the disk is encrypted with a different AES key. For
   more information on gbde's cryptographic design, including how the
   sector keys are derived from the user-supplied passphrase, see
   gbde(4).

     --------------------------------------------------------------

    18.16.1.4. Compatibility Issues

   sysinstall(8) is incompatible with gbde-encrypted devices. All
   *.bde devices must be detached from the kernel before starting
   sysinstall(8) or it will crash during its initial probing for
   devices. To detach the encrypted device used in our example, use
   the following command:

 # gbde detach /dev/ad4s1c

   Also note that, as vinum(4) does not use the geom(4) subsystem,
   you cannot use gbde with vinum volumes.

     --------------------------------------------------------------

  18.16.2. Disk Encryption with geli

   Contributed by Daniel Gerzo.

   A new cryptographic GEOM class is available as of FreeBSD 6.0 -
   geli. It is currently being developed by Pawel Jakub Dawidek
   <pjd@FreeBSD.org>. Geli is different to gbde; it offers different
   features and uses a different scheme for doing cryptographic work.

   The most important features of geli(8) are:

     * Utilizes the crypto(9) framework !X!X when cryptographic
       hardware is available, geli will use it automatically.

     * Supports multiple cryptographic algorithms (currently AES,
       Blowfish, and 3DES).

     * Allows the root partition to be encrypted. The passphrase used
       to access the encrypted root partition will be requested
       during the system boot.

     * Allows the use of two independent keys (e.g. a !S:key!" and a
       !S:company key!").

     * geli is fast - performs simple sector-to-sector encryption.

     * Allows backup and restore of Master Keys. When a user has to
       destroy his keys, it will be possible to get access to the
       data again by restoring keys from the backup.

     * Allows to attach a disk with a random, one-time key !X!X
       useful for swap partitions and temporary file systems.

   More geli features can be found in the geli(8) manual page.

   The next steps will describe how to enable support for geli in the
   FreeBSD kernel and will explain how to create a new geli
   encryption provider. At the end it will be demonstrated how to
   create an encrypted swap partition using features provided by
   geli.

   In order to use geli, you must be running FreeBSD 6.0-RELEASE or
   later. Super-user privileges will be required since modifications
   to the kernel are necessary.

    1. Adding geli Support to the Kernel Configuration File

       Add the following lines to the kernel configuration file:

 options GEOM_ELI
 device crypto

       Rebuild the kernel as described in uU 8 ^3^1.

       Alternatively, the geli module can be loaded at boot time. Add
       the following line to the /boot/loader.conf:

       geom_eli_load="YES"

       geli(8) should now be supported by the kernel.

    2. Generating the Master Key

       The following example will describe how to generate a key
       file, which will be used as part of the Master Key for the
       encrypted provider mounted under /private. The key file will
       provide some random data used to encrypt the Master Key. The
       Master Key will be protected by a passphrase as well.
       Provider's sector size will be 4kB big. Furthermore, the
       discussion will describe how to attach the geli provider,
       create a file system on it, how to mount it, how to work with
       it, and finally how to detach it.

       It is recommended to use a bigger sector size (like 4kB) for
       better performance.

       The Master Key will be protected with a passphrase and the
       data source for key file will be /dev/random. The sector size
       of /dev/da2.eli, which we call provider, will be 4kB.

 # dd if=/dev/random of=/root/da2.key bs=64 count=1
 # geli init -s 4096 -K /root/da2.key /dev/da2
 Enter new passphrase:
 Reenter new passphrase:

       It is not mandatory that both a passphrase and a key file are
       used; either method of securing the Master Key can be used in
       isolation.

       If key file is given as !S:-!", standard input will be used.
       This example shows how more than one key file can be used.

 # cat keyfile1 keyfile2 keyfile3 | geli init -K - /dev/da2

    3. Attaching the Provider with the generated Key

 # geli attach -k /root/da2.key /dev/da2
 Enter passphrase:

       The new plaintext device will be named /dev/da2.eli.

 # ls /dev/da2*
 /dev/da2  /dev/da2.eli

    4. Creating the new File System

 # dd if=/dev/random of=/dev/da2.eli bs=1m
 # newfs /dev/da2.eli
 # mount /dev/da2.eli /private

       The encrypted file system should be visible to df(1) and be
       available for use now.

 # df -H
 Filesystem     Size   Used  Avail Capacity  Mounted on
 /dev/ad0s1a    248M    89M   139M    38%    /
 /devfs         1.0K   1.0K     0B   100%    /dev
 /dev/ad0s1f    7.7G   2.3G   4.9G    32%    /usr
 /dev/ad0s1d    989M   1.5M   909M     0%    /tmp
 /dev/ad0s1e    3.9G   1.3G   2.3G    35%    /var
 /dev/da2.eli   150G   4.1K   138G     0%    /private

    5. Unmounting and Detaching the Provider

       Once the work on the encrypted partition is done, and the
       /private partition is no longer needed, it is prudent to
       consider unmounting and detaching the geli encrypted partition
       from the kernel.

 # umount /private
 # geli detach da2.eli

   More information about the use of geli(8) can be found in the
   manual page.

     --------------------------------------------------------------

    18.16.2.1. Encrypting a Swap Partition

   The following example demonstrates how to create a geli encrypted
   swap partition.

 # dd if=/dev/random of=/dev/ad0s1b bs=1m
 # geli onetime -d -a 3des ad0s1b
 # swapon /dev/ad0s1b.eli

     --------------------------------------------------------------

    18.16.2.2. Using the geli rc.d Script

   geli comes with a rc.d script which can be used to simplify the
   usage of geli. An example of configuring geli through rc.conf(5)
   follows:

 geli_devices="da2"
 geli_da2_flags="-p -k /root/da2.key"

   This will configure /dev/da2 as a geli provider of which the
   Master Key file is located in /root/da2.key, and geli will not use
   a passphrase when attaching the provider (note that this can only
   be used if -P was given during the geli init phase). The system
   will detach the geli provider from the kernel before the system
   shuts down.

   More information about configuring rc.d is provided in the rc.d
   section of the Handbook.

     --------------------------------------------------------------

18.17. Encrypting Swap Space

   Written by Christian Bru:ffer.

   Swap encryption in FreeBSD is easy to configure and has been
   available since FreeBSD 5.3-RELEASE. Depending on which version of
   FreeBSD is being used, different options are available and
   configuration can vary slightly. From FreeBSD 6.0-RELEASE onwards,
   the gbde(8) or geli(8) encryption systems can be used for swap
   encryption. With earlier versions, only gbde(8) is available. Both
   systems use the encswap rc.d script.

   The previous section, Encrypting Disk Partitions, includes a short
   discussion on the different encryption systems.

     --------------------------------------------------------------

  18.17.1. Why should Swap be Encrypted?

   Like the encryption of disk partitions, encryption of swap space
   is done to protect sensitive information. Imagine an application
   that e.g. deals with passwords. As long as these passwords stay in
   physical memory, all is well. However, if the operating system
   starts swapping out memory pages to free space for other
   applications, the passwords may be written to the disk platters
   unencrypted and easy to retrieve for an adversary. Encrypting swap
   space can be a solution for this scenario.

     --------------------------------------------------------------

  18.17.2. Preparation

     -a`: For the remainder of this section, ad0s1b will be the swap
     partition.

   Up to this point the swap has been unencrypted. It is possible
   that there are already passwords or other sensitive data on the
   disk platters in cleartext. To rectify this, the data on the swap
   partition should be overwritten with random garbage:

 # dd if=/dev/random of=/dev/ad0s1b bs=1m

     --------------------------------------------------------------

  18.17.3. Swap Encryption with gbde(8)

   If FreeBSD 6.0-RELEASE or newer is being used, the .bde suffix
   should be added to the device in the respective /etc/fstab swap
   line:

 # Device                Mountpoint      FStype  Options         Dump    Pass#
 /dev/ad0s1b.bde         none            swap    sw              0       0
      

   For systems prior to FreeBSD 6.0-RELEASE, the following line in
   /etc/rc.conf is also needed:

 gbde_swap_enable="YES"

     --------------------------------------------------------------

  18.17.4. Swap Encryption with geli(8)

   Alternatively, the procedure for using geli(8) for swap encryption
   is similar to that of using gbde(8). The .eli suffix should be
   added to the device in the respective /etc/fstab swap line:

 # Device                Mountpoint      FStype  Options         Dump    Pass#
 /dev/ad0s1b.eli         none            swap    sw              0       0
      

   geli(8) uses the AES algorithm with a key length of 256 bit by
   default.

   Optionally, these defaults can be altered using the
   geli_swap_flags option in /etc/rc.conf. The following line tells
   the encswap rc.d script to create geli(8) swap partitions using
   the Blowfish algorithm with a key length of 128 bit, a sectorsize
   of 4 kilobytes and the !S:detach on last close!" option set:

 geli_swap_flags="-a blowfish -l 128 -s 4096 -d"

   Please refer to the description of the onetime command in the
   geli(8) manual page for a list of possible options.

     --------------------------------------------------------------

  18.17.5. Verifying that it Works

   Once the system has been rebooted, proper operation of the
   encrypted swap can be verified using the swapinfo command.

   If gbde(8) is being used:

 % swapinfo
 Device          1K-blocks     Used    Avail Capacity
 /dev/ad0s1b.bde    542720        0   542720     0%
      

   If geli(8) is being used:

 % swapinfo
 Device          1K-blocks     Used    Avail Capacity
 /dev/ad0s1b.eli    542720        0   542720     0%
      

     --------------------------------------------------------------

          ^3^1 19. GEOM: Modular Disk Transformation Framework

   Written by Tom Rhodes.

19.1. .S:z

   YEN>>^3^1^2[>>\|p|o|b FreeBSD -a-o GEOM NOT[-ocCURU"IYENI-oI-oD-!A
   YEN]S:tYENI"O^3](c)w'X-oO/+-`YENI-a-o RAID
   -a-o+-+-"iCURu"a!CYEN>>^3^1CUR-L-.|^2`CURJ+-'DEGQ GEOM
   |p|o^3B^2z(c)^3 1/4h-a-o I/O!A^3oAth,eDEGT 1/2D-DEGN|O geom(4)
   CURINOTUAo:-a-o SEE ALSO ^3!YEN-:!CYEN>>^3^1CUR]<<D RAID
   ^3](c)w<<u:<<n!A|b^3o,IYENu.|DEGQ 1/2 *YENO/<<e GEOM CURa:'(c)-a-o
   RAID  1/4O|!!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!J

     * ^3z^1L GEOM YENiCURa:'(c)th"C, 1/4O|!-a-o RAID!C

     * |p|o"IYENIDEGoYEN>>CURu"a"ODEGt,m!B 3/4THS:@!B-ouAA@CUR-L-|P
       1/4O|!-a-o RAID!C

     * |p|o^3z^1L GEOM
       "OS:^1|"Ae(R)g(mirror)!BCURA'^2^3su^2(stripe)!BYEN[+-K(encrypt)
       !B>>.-oY^3s+-u-oI-oD-uYEN!C

     * .i GEOM NOT[-ocCURU-a-o-oI-oD-uoYENIDEGYAD!A|p|o+-AEDEG-L-!C

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!J

     * CURF,N FreeBSD |p|oNOTY<<Y-oI-oD-(uU 18 ^3^1) !C

     * -a 3/4^1D|p|o^3](c)w!B|w,E.s-a-o FreeBSD (R)O:CURss (uU 8
       ^3^1) !C

     --------------------------------------------------------------

19.2. GEOM  3/4E 1/2 *

   GEOM ^3z^1L privoder(S:Y /dev/ CURU-a-o-S(R)i,E,mAE(R) *) "O
   3/4TH+-+- classes(|p Master Boot Records!B BSD labels uYEN) !CGEOM
   CURa:'(c)|h-oO/^3nAAe RAID DEGt,m!A^3z^1L GEOM |s"u(R)E!A
   S:@.~"t^2I(c)MA^3YENIu{|!CUR-L-.|.NAN"`i GEOM |s|b!C

     --------------------------------------------------------------

19.3. RAID0 - CURA'^2^3su^2(striping)

   Written by Tom Rhodes YENB Murray Stokely.

   CURA'^2^3su^2(striping)
   YENiYENI"O^3su^2|hO-oI-oD-|"NOTDEGCUR@CURjP:o-aAAP:!!C
   <<U:|h(R)EOuwAAe+-+-"i 3/4^1YENiYENHS:^1|"^3oYENo"AE!ACUR-L-^1L
   GEOM CUR]'-L-"NCURF^3nAAe-a(c)YEN>>-a-o
   RAID0!ACUR]'NNOTOCURA'^2^3su^2(striping)!C

   |b RAID0 ,I!A,e(R)AE.|^3QCURACURA|"<<U:|hP:o!A |ACURA'^2
   1/4gCURJYENth^3!-a-o-oI-oD-!C"O|pn 1/4gCURJ 256k
   -a-o,e(R)AE"`i^3aeCUR@-oI-oD-!A|b YEN|O-oI-oD--a-o RAID0
   CURCURYENi|P(R)E 1/4gCURJ 64k "`iYEN|O-oI-oD-,I!A
   |]|^1YENiCURj'T'-L-CURE I/O
   (R)A:-`a!C|p-aG"IYENIS:o|h-a-o-oI-oD-+-+-"i 3/4^1!A I/O
   (R)A:-`aYENi|A'-L-CURE!C

   YENN(c)oAA-a(c)I 1/4g(R)E.||P"BYENae?u^1i^3\|h-oI-oD-P:i|ae I/O
   ^3B^2z!A|]|^1 RAID0 -a-o"CO-oI-oD-YEN^2P:.CURjCURpCUR@ 1/4E!C

   Disk Striping Illustration

   YENIYEN 1/4(R)ae|!CURAE-a-o ATA
   -oI-oD-"O<<O/YENssCURA'^2^3su^2(striping)

    1. ,u:CURJ geom_stripe kernel module!G

 # kldload geom_stripe.ko

    2. 1/2T(c)w+- 3/4,u:AI(mount point)|s|b!C
       |p-aG.QYENICURA'^2^3su^2(striping)-a-o-aAAP:!DEGuNOTDEG(R)UYENO/?y(root
       partition!AS:Y / )!A <<hYENyYENIO 1/4E(R)E-a-o+- 3/4,u:AI!A|p
       /mnt!G

 # mkdir /mnt

    3. 1/2T>>{nYENI"OCURA'^2^3su^2(striping)-a-o,E,m|W-oU!A+-uuU<<O/YENss.s-a-oCURA'^2^3su^2(striping)!C
       "O|pCURU+--a-o<<u:YENO.|CURA'^2^3su^2(striping)"aOYEN
       1/4"IYENI!B(c)|YEN 1/4CURA^3IDEGI-a-o ATA -oI-oD-(/dev/ad2
       (c)M /dev/ad3) !G

 #
                 gstripe label -v st0 /dev/ad2 /dev/ad3

 # gstripe label -v st0 /dev/ad2 /dev/ad3

    4. YENICURU+--a-o<<u:YENO"O<<O/YENssCURA^3IDEGI-ai(partition
       table)!G

 # bsdlabel -wB /dev/stripe/st0

    5. DEG-L-CURFYENy<<e<<O/YENss-a-o st0 !A^3oO"BAEJAU.||b
       /dev/stripe CURU.s 1/4W"aO,E,m!G st0a (c)M st0c!C S:QYENI
       newfs <<u:YENOYENiYENH|b st0a <<O/YENssAE(R) *"t^2I!G

 # newfs -U /dev/stripe/st0a

       ?A^1oCURW.||^3CUR@DEGi
       1/4AE|rP:EAm|O^1L!A'XNOTiA:A<<a'N.|S:^1|"!C|^1(R)E-aAAP:!CURw<<O/YENss!A
       YENiYENI"O+- 3/4,u:"IYENICURF!C

   CURU+-<<u:YENOYENiYENI"OCURaDEGE+-
   3/4,u:CURA'^2^3su^2(striping)-aAAP:!!G

 # mount /dev/stripe/st0a /mnt

   |p-aGn|bP:} 3/4-:(R)E|UDEGE+- 3/4,u:!A|b /etc/fstab
   YEN[CURJ^3oP:o-aAAP:!-a-o,eDEGT!G

 # echo "/dev/stripe/st0a /mnt ufs rw 2 2" \
     >> /etc/fstab

   |O geom kernel module
   YEN^2P:.|b"t^2I-a`i(c)lCURAE(R)E|UDEGE,u:CURJ!A |]|^1|b
   /boot/lodaer.conf YEN[CURJCUR@|ae!G

 # echo 'geom_stripe_load="YES"' >> /boot/loader.conf

     --------------------------------------------------------------

19.4. RAID1 - Ae(R)g(Mirroring)

   ^3\|hYENo/.~(c)IOCURHYENICURaYENIAe(R)g(mirroring)
   "OCUR-L-CURCURA_"t^2IP:i|ae^3AEYEN-:!C Ae(R)gA^2^3ae"O>>!'NNOTO|b
   B -oI-oD-CURW<<AD-CUR@YEN-: A -oI-oD--a-o,e(R)AE!A (c)I-aI C+D
   -oI-oD-<<AD- A+B -oI-oD--a-o,e(R)AE!CCUR-L- 1/2 *^3](c)w|p|o!A
   ^3I<<n-a-oNOTO(c)O|^3-oI-oD-(c)ICURA^3IDEGI(partition)
   CURW-a-o,e(R)AE^3-L-.|^3Q 1/2AE>>s!A
   CURS:<<aYENi|bCUR-L-CURCURA_-aADEGE-a-o+-!-apCURU'_`i!B^3AEYEN-:,e(R)AE!A"IAx|s-a-o,e(R)AES:o|wYENth!C

   P:}(c)lCURS:<<e!A 1/2D-YENy
   1/2T(c)w"t^2ICURW|^3"aO(R)eP:qNOTU|P-a-o-oI-oD-!A <<a+--a-o
   1/2d"ODEG^2^3]^3o"aAu-oI-oD-NOTO direct access(da(4)) SCSI
   -oI-oD-!C

   -oYENyS:UIDEG^2^3] FreeBSD
   |w,E|b^2A:CUR@O-oI-oD-CURW!AYENBYENu|^3"aOCURA^3IDEGI(partition)!C
   "a:CURCURCUR@ONOTOYENae'<<CURA^3IDEGI(swap
   partition!ACURjCURpNOTDEG RAM
   -a-o"a?)!A|O^3NCURU-a-oYENthYENI(c)o(R)UYENO/?y(S:Y /!A root file
   system)!C.iuMn|bCUR-L-|P+- 3/4,u:AI(mount point)
   CURAYENXS:o|hCURA^3IDEGI (partition) CUR]YENiYENH!ACUR-L-^1LAo/<<
   *.|CURj'T'-L-CURE!A|]NOTDEGYEN^2P:.CURaDEGE 3/4THS:@ bsdlabel(8)
   (c)M fdisk(8) CURu"a!C

   <<P:} 3/4-:"AuYEN"`i"t^2IS:^1YENth-a`i(c)lCURAES:^1^2|!AYENI root
   unCURJ!C

   <<O/YENss /dev/mirror/gm ,E,m"AYENH /dev/da1 ^3su^2!G

 # gmirror label -vnb round-robin gm0 /dev/da1

   ^3o(R)E"t^2IA^3,O.||^A^3!G

 Metadata value stored on /dev/da1.
 Done.

   -a`i(c)lCURAE GEOM!A^3oDEGES:@.||UDEGE,u:CURJ
   /boot/kernel/geom_mirror.ko kernel module!G

 # gmirror load

     -a`: ^3oDEGES:@A^3,O.||b /dev/mirror CURU<<O/YENss gm0
     ,E,mu^2AI(device node)!C

   |b^3oO.s<<O/-a-o gm0 ,E,mCURW|w,mCUR@-e-a-o fdisk label (c)MP:}
   3/4-:-oIDEGI!G

 # fdisk -vBI /dev/mirror/gm0

   +-uuU|w,m bsdlabel ,eDEGT!G

 # bsdlabel -wB /dev/mirror/gm0s1

     -a`: |p-aG|s|b|hO slice (c)MCURA^3IDEGI(partition)!A DEGO+-o
     *S:iCURW"a<<u:YENO-a-oDEGN 1/4AE!AYENBYENtCUR@O-oI-oD-CURW-a-o
     slice (c)MCURA^3IDEGI(partition) CURjCURpYEN^2P:.NOTU|P!C

   YENI newfs(8) CURu"a|b gm0s1a ,E,mu^2AI<<O/YENss^1w^3]-a-oAE(R)
   *"t^2I!G

 # newfs -U /dev/mirror/gm0s1a

   "t^2I.||LYENX^3\|h,eDEGT(c)MCUR@CURjDEGi
   1/4AE|r!A^3oNOTOYEN?+-`-a-o!C 
   1/2T>>{NOTOS:_|^3>>{|o?u>>~!A+-uuU'NYENiYENH+-N^3oO,E,m+-
   3/4,u:"`i /mnt +- 3/4,u:AI(mount mount)!G

 # mount /dev/mirror/gm0s1a /mnt

   +-uuU+-N`iYEN>>P:} 3/4-:-oI-oD--a-o,e(R)AE.h^2 3/4"`i.s-a-oAE(R)
   *"t^2I (/mnt)!C 1/2d"ONOTOYENI dump(8) (c)M restore(8)
   !ACUR-L-^1LYENI dd(1) CUR]YENiYENH!C

 # dump -L -0 -f- / |(cd /mnt && restore -r -v -f-)

   DEGo|aeCURWz<<u:YENO(R)E!AYENun+-N<<e.i-a-oAE(R) *"t^2I+-
   3/4|bYEN? 1/2T-a-o|`i,m!AA^3,O'N-`a|"YEN\!C

   +-uuU 1/2s?e /mnt/etc/fstab AE+-N swap file "-o|ae^2
   3/4DEG-L-(c)Iuu,NDEG_"O!C [24] 1/2D-DEGN|OCURU+- 1/2d"O!A"A(R)U
   3/4U.s-oI-oD- *S:i"a:YEN|-a-oAE(R) *"t^2I,eDEGT!G

 # Device                Mountpoint      FStype  Options         Dump    Pass#
 #/dev/da0s2b             none            swap    sw              0       0
 /dev/mirror/gm0s1a       /               ufs     rw              1       1

   |bYENO/<<e-a-o(R)UYENO/?yCURI.s-a-o(R)UYENO/?y<<O/YENss boot.conf
   AE(R) *!A ^3oOAE(R) *YENiYENH!yADEGS:U!z"t^2I BIOS P:} 3/4-:!G

 # echo "1:da(1,a)/boot/loader" > /boot.config

 # echo "1:da(1,a)/boot/loader" > /mnt/boot.config

     -a`: |b"aO(R)UYENO/?yCURW^3-L-.s 1/4WAE(R)
     *NOTONOTDEGCURF|wYENthDEG_"-L-!A
     |p-aG|]NOTDEGNOTY"C,`i|].s-a-o(R)UYENO/?yuL-akP:}
     3/4-:!A|U:CURO:AUYENiYENI`iYEN>>-a-o(R)UYENO/?y!C

   +-uuU|b /boot/loader.conf .s 1/4W"a|ae!G

 # echo 'geom_mirror_load="YES"' >> /mnt/boot/loader.conf

   ^3o.|<<u:YENU: loader(8) |bP:} 3/4-:(R)E,u:CURJ geom_mirror.ko
   kernel module!C

   <<P:} 3/4-:!G

 # shutdown -r now

   |p-aGCUR@CURAP:P:S:Q!A"t^2IA^3,O.|+-q gm0s1a ,E,mP:} 3/4-:!A
   +-uCURU"OYENX^2{ login '-L-YENU:ue+-!C|p-aGYENX?uCURF!A  1/2D-DEGN
   3/4\CURU+- Troubleshooting "-oCUR@,`!C ^2{|bYENiYENH+-N da0
   -oI-oD-YEN[CURJ gm0 ,E,m!G

 # gmirror configure -a gm0
 # gmirror insert gm0 /dev/da0

   "a:CURCUR -a -oX 1/4D-S:iP:D gmirror(8)
   "IYENI!u|UDEGE|P"B(automatic synchronization)!v!A"O|p|UDEGE|P"B
   1/4gCURJ-oI-oD--a-oDEGES:@!C manual
   >>!(c)uCURF|p|o<<<<O/!B"uYENN-oI-oD-uYEN!ACUR-L-^1L manual ,I-a-o
   1/2d"ONOTOYENI data |OCUR-L-NOTO gm0!C

     --------------------------------------------------------------

  19.4.1. Troubleshooting

    19.4.1.1. "t^2IuL-akP:} 3/4-:

   |p-aGP:} 3/4-:'-L-YENU:Ath|u:^3o 1/4E!G

 ffs_mountroot: can't find rootvp
 Root mount failed: 6
 mountroot>

   1/2D-YENI 3/4-: 3/4^1+--aOCURW-a-o Power <<o:P:s(c)I reset
   <<o:P:s"O<<P:} 3/4-:!A"A|bP:} 3/4-:?i^3ae?i (6)!A ^3o
   1/4ECURl!A"t^2I'N.|P:iCURJ loader(8) YENae 1/2I 1/4O|!!C^3o(R)EO!A
   1/2D-.OCURU+-<<u:YENO"OCURaDEGE,u:CURJ(c)O>>Y-a-o kernel module
   !ACUR]'NNOTO geom_mirror.ko!G

 OK? load geom_mirror.ko
 OK? boot

   |p-aG^3o
   1/4E|"YEN\CURF-a-o,U:!A-aiYENU:|]NOTDEGNOTY"C,`i|]uL-ak|UDEGE,u:CURJ
   kernel module!C  1/2D-+-N!G

 options GEOM_MIRROR

   YEN[CURJ"`i(R)O:CURss^3](c)wAE(kernel configuration file)!A<<
   1/2s"A|w,E(R)O:CURss!C ^3oA^3,O-`a,N"M^3oODEGYAD!C

     --------------------------------------------------------------

                   ^3^1 20. The Vinum Volume Manager

   Originally written by Greg Lehey.

20.1. Synopsis

   No matter what disks you have, there are always potential
   problems:

     * They can be too small.

     * They can be too slow.

     * They can be too unreliable.

   One way some users safeguard themselves against such issues is
   through the use of multiple, and sometimes redundant, disks.

   In addition to supporting various cards and controllers for
   hardware RAID systems, the base FreeBSD system includes the Vinum
   Volume Manager, a block device driver that implements virtual disk
   drives.

   Vinum provides more flexibility, performance, and reliability than
   traditional disk storage, and implements RAID-0, RAID-1, and
   RAID-5 models both individually and in combination.

   This chapter provides an overview of potential problems with
   traditional disk storage, and an introduction to the Vinum Volume
   Manager.

     --------------------------------------------------------------

20.2. Disks Are Too Small

   Vinum is a so-called Volume Manager, a virtual disk driver that
   addresses these three problems. Let us look at them in more
   detail. Various solutions to these problems have been proposed and
   implemented:

   Disks are getting bigger, but so are data storage requirements.
   Often you will find you want a file system that is bigger than the
   disks you have available. Admittedly, this problem is not as acute
   as it was ten years ago, but it still exists. Some systems have
   solved this by creating an abstract device which stores its data
   on a number of disks.

     --------------------------------------------------------------

20.3. Access Bottlenecks

   Modern systems frequently need to access data in a highly
   concurrent manner. For example, large FTP or HTTP servers can
   maintain thousands of concurrent sessions and have multiple
   100 Mbit/s connections to the outside world, well beyond the
   sustained transfer rate of most disks.

   Current disk drives can transfer data sequentially at up to
   70 MB/s, but this value is of little importance in an environment
   where many independent processes access a drive, where they may
   achieve only a fraction of these values. In such cases it is more
   interesting to view the problem from the viewpoint of the disk
   subsystem: the important parameter is the load that a transfer
   places on the subsystem, in other words the time for which a
   transfer occupies the drives involved in the transfer.

   In any disk transfer, the drive must first position the heads,
   wait for the first sector to pass under the read head, and then
   perform the transfer. These actions can be considered to be
   atomic: it does not make any sense to interrupt them.

   Consider a typical transfer of about 10 kB: the current generation
   of high-performance disks can position the heads in an average of
   3.5 ms. The fastest drives spin at 15,000 rpm, so the average
   rotational latency (half a revolution) is 2 ms. At 70 MB/s, the
   transfer itself takes about 150 -L-gs, almost nothing compared to
   the positioning time. In such a case, the effective transfer rate
   drops to a little over 1 MB/s and is clearly highly dependent on
   the transfer size.

   The traditional and obvious solution to this bottleneck is !S:more
   spindles!": rather than using one large disk, it uses several
   smaller disks with the same aggregate storage space. Each disk is
   capable of positioning and transferring independently, so the
   effective throughput increases by a factor close to the number of
   disks used.

   The exact throughput improvement is, of course, smaller than the
   number of disks involved: although each drive is capable of
   transferring in parallel, there is no way to ensure that the
   requests are evenly distributed across the drives. Inevitably the
   load on one drive will be higher than on another.

   The evenness of the load on the disks is strongly dependent on the
   way the data is shared across the drives. In the following
   discussion, it is convenient to think of the disk storage as a
   large number of data sectors which are addressable by number,
   rather like the pages in a book. The most obvious method is to
   divide the virtual disk into groups of consecutive sectors the
   size of the individual physical disks and store them in this
   manner, rather like taking a large book and tearing it into
   smaller sections. This method is called concatenation and has the
   advantage that the disks are not required to have any specific
   size relationships. It works well when the access to the virtual
   disk is spread evenly about its address space. When access is
   concentrated on a smaller area, the improvement is less marked.
   ^1IS:I 20-1 illustrates the sequence in which storage units are
   allocated in a concatenated organization.



   ^1IS:I 20-1. Concatenated Organization

   An alternative mapping is to divide the address space into
   smaller, equal-sized components and store them sequentially on
   different devices. For example, the first 256 sectors may be
   stored on the first disk, the next 256 sectors on the next disk
   and so on. After filling the last disk, the process repeats until
   the disks are full. This mapping is called striping or RAID-0
   [25]. Striping requires somewhat more effort to locate the data,
   and it can cause additional I/O load where a transfer is spread
   over multiple disks, but it can also provide a more constant load
   across the disks. ^1IS:I 20-2 illustrates the sequence in which
   storage units are allocated in a striped organization.



   ^1IS:I 20-2. Striped Organization

     --------------------------------------------------------------

20.4. Data Integrity

   The final problem with current disks is that they are unreliable.
   Although disk drive reliability has increased tremendously over
   the last few years, they are still the most likely core component
   of a server to fail. When they do, the results can be
   catastrophic: replacing a failed disk drive and restoring data to
   it can take days.

   The traditional way to approach this problem has been mirroring,
   keeping two copies of the data on different physical hardware.
   Since the advent of the RAID levels, this technique has also been
   called RAID level 1 or RAID-1. Any write to the volume writes to
   both locations; a read can be satisfied from either, so if one
   drive fails, the data is still available on the other drive.

   Mirroring has two problems:

     * The price. It requires twice as much disk storage as a
       non-redundant solution.

     * The performance impact. Writes must be performed to both
       drives, so they take up twice the bandwidth of a non-mirrored
       volume. Reads do not suffer from a performance penalty: it
       even looks as if they are faster.

   An alternative solution is parity, implemented in the RAID levels
   2, 3, 4 and 5. Of these, RAID-5 is the most interesting. As
   implemented in Vinum, it is a variant on a striped organization
   which dedicates one block of each stripe to parity of the other
   blocks. As implemented by Vinum, a RAID-5 plex is similar to a
   striped plex, except that it implements RAID-5 by including a
   parity block in each stripe. As required by RAID-5, the location
   of this parity block changes from one stripe to the next. The
   numbers in the data blocks indicate the relative block numbers.



   ^1IS:I 20-3. RAID-5 Organization

   Compared to mirroring, RAID-5 has the advantage of requiring
   significantly less storage space. Read access is similar to that
   of striped organizations, but write access is significantly
   slower, approximately 25% of the read performance. If one drive
   fails, the array can continue to operate in degraded mode: a read
   from one of the remaining accessible drives continues normally,
   but a read from the failed drive is recalculated from the
   corresponding block from all the remaining drives.

     --------------------------------------------------------------

20.5. Vinum Objects

   In order to address these problems, Vinum implements a four-level
   hierarchy of objects:

     * The most visible object is the virtual disk, called a volume.
       Volumes have essentially the same properties as a UNIX disk
       drive, though there are some minor differences. They have no
       size limitations.

     * Volumes are composed of plexes, each of which represent the
       total address space of a volume. This level in the hierarchy
       thus provides redundancy. Think of plexes as individual disks
       in a mirrored array, each containing the same data.

     * Since Vinum exists within the UNIX disk storage framework, it
       would be possible to use UNIX partitions as the building block
       for multi-disk plexes, but in fact this turns out to be too
       inflexible: UNIX disks can have only a limited number of
       partitions. Instead, Vinum subdivides a single UNIX partition
       (the drive) into contiguous areas called subdisks, which it
       uses as building blocks for plexes.

     * Subdisks reside on Vinum drives, currently UNIX partitions.
       Vinum drives can contain any number of subdisks. With the
       exception of a small area at the beginning of the drive, which
       is used for storing configuration and state information, the
       entire drive is available for data storage.

   The following sections describe the way these objects provide the
   functionality required of Vinum.

     --------------------------------------------------------------

  20.5.1. Volume Size Considerations

   Plexes can include multiple subdisks spread over all drives in the
   Vinum configuration. As a result, the size of an individual drive
   does not limit the size of a plex, and thus of a volume.

     --------------------------------------------------------------

  20.5.2. Redundant Data Storage

   Vinum implements mirroring by attaching multiple plexes to a
   volume. Each plex is a representation of the data in a volume. A
   volume may contain between one and eight plexes.

   Although a plex represents the complete data of a volume, it is
   possible for parts of the representation to be physically missing,
   either by design (by not defining a subdisk for parts of the plex)
   or by accident (as a result of the failure of a drive). As long as
   at least one plex can provide the data for the complete address
   range of the volume, the volume is fully functional.

     --------------------------------------------------------------

  20.5.3. Performance Issues

   Vinum implements both concatenation and striping at the plex
   level:

     * A concatenated plex uses the address space of each subdisk in
       turn.

     * A striped plex stripes the data across each subdisk. The
       subdisks must all have the same size, and there must be at
       least two subdisks in order to distinguish it from a
       concatenated plex.

     --------------------------------------------------------------

  20.5.4. Which Plex Organization?

   The version of Vinum supplied with FreeBSD 9.1 implements two
   kinds of plex:

     * Concatenated plexes are the most flexible: they can contain
       any number of subdisks, and the subdisks may be of different
       length. The plex may be extended by adding additional
       subdisks. They require less CPU time than striped plexes,
       though the difference in CPU overhead is not measurable. On
       the other hand, they are most susceptible to hot spots, where
       one disk is very active and others are idle.

     * The greatest advantage of striped (RAID-0) plexes is that they
       reduce hot spots: by choosing an optimum sized stripe (about
       256 kB), you can even out the load on the component drives.
       The disadvantages of this approach are (fractionally) more
       complex code and restrictions on subdisks: they must be all
       the same size, and extending a plex by adding new subdisks is
       so complicated that Vinum currently does not implement it.
       Vinum imposes an additional, trivial restriction: a striped
       plex must have at least two subdisks, since otherwise it is
       indistinguishable from a concatenated plex.

   -ai(R)ae 20-1 summarizes the advantages and disadvantages of each
   plex organization.

   -ai(R)ae 20-1. Vinum Plex Organizations

                Minimum  Can add  Must be                             
    Plex type   subdisks subdisks  equal          Application
                                   size   
                                          Large data storage with     
   concatenated 1        yes      no      maximum placement           
                                          flexibility and moderate    
                                          performance                 
                                          High performance in         
   striped      2        no       yes     combination with highly     
                                          concurrent access           

     --------------------------------------------------------------

20.6. Some Examples

   Vinum maintains a configuration database which describes the
   objects known to an individual system. Initially, the user creates
   the configuration database from one or more configuration files
   with the aid of the vinum(8) utility program. Vinum stores a copy
   of its configuration database on each disk slice (which Vinum
   calls a device) under its control. This database is updated on
   each state change, so that a restart accurately restores the state
   of each Vinum object.

     --------------------------------------------------------------

  20.6.1. The Configuration File

   The configuration file describes individual Vinum objects. The
   definition of a simple volume might be:

     drive a device /dev/da3h
     volume myvol
       plex org concat
         sd length 512m drive a

   This file describes four Vinum objects:

     * The drive line describes a disk partition (drive) and its
       location relative to the underlying hardware. It is given the
       symbolic name a. This separation of the symbolic names from
       the device names allows disks to be moved from one location to
       another without confusion.

     * The volume line describes a volume. The only required
       attribute is the name, in this case myvol.

     * The plex line defines a plex. The only required parameter is
       the organization, in this case concat. No name is necessary:
       the system automatically generates a name from the volume name
       by adding the suffix .px, where x is the number of the plex in
       the volume. Thus this plex will be called myvol.p0.

     * The sd line describes a subdisk. The minimum specifications
       are the name of a drive on which to store it, and the length
       of the subdisk. As with plexes, no name is necessary: the
       system automatically assigns names derived from the plex name
       by adding the suffix .sx, where x is the number of the subdisk
       in the plex. Thus Vinum gives this subdisk the name
       myvol.p0.s0.

   After processing this file, vinum(8) produces the following
   output:

       # vinum -> create config1
       Configuration summary
       Drives:         1 (4 configured)
       Volumes:        1 (4 configured)
       Plexes:         1 (8 configured)
       Subdisks:       1 (16 configured)

         D a                     State: up       Device /dev/da3h        Avail: 2061/2573 MB (80%)

         V myvol                 State: up       Plexes:       1 Size:        512 MB

         P myvol.p0            C State: up       Subdisks:     1 Size:        512 MB

         S myvol.p0.s0           State: up       PO:        0  B Size:        512 MB

   This output shows the brief listing format of vinum(8). It is
   represented graphically in ^1IS:I 20-4.



   ^1IS:I 20-4. A Simple Vinum Volume

   This figure, and the ones which follow, represent a volume, which
   contains the plexes, which in turn contain the subdisks. In this
   trivial example, the volume contains one plex, and the plex
   contains one subdisk.

   This particular volume has no specific advantage over a
   conventional disk partition. It contains a single plex, so it is
   not redundant. The plex contains a single subdisk, so there is no
   difference in storage allocation from a conventional disk
   partition. The following sections illustrate various more
   interesting configuration methods.

     --------------------------------------------------------------

  20.6.2. Increased Resilience: Mirroring

   The resilience of a volume can be increased by mirroring. When
   laying out a mirrored volume, it is important to ensure that the
   subdisks of each plex are on different drives, so that a drive
   failure will not take down both plexes. The following
   configuration mirrors a volume:

         drive b device /dev/da4h
         volume mirror
       plex org concat
         sd length 512m drive a
           plex org concat
             sd length 512m drive b

   In this example, it was not necessary to specify a definition of
   drive a again, since Vinum keeps track of all objects in its
   configuration database. After processing this definition, the
   configuration looks like:

         Drives:         2 (4 configured)
         Volumes:        2 (4 configured)
         Plexes:         3 (8 configured)
         Subdisks:       3 (16 configured)

         D a                     State: up       Device /dev/da3h        Avail: 1549/2573 MB (60%)
         D b                     State: up       Device /dev/da4h        Avail: 2061/2573 MB (80%)

     V myvol                 State: up       Plexes:       1 Size:        512 MB
     V mirror                State: up       Plexes:       2 Size:        512 MB

     P myvol.p0            C State: up       Subdisks:     1 Size:        512 MB
     P mirror.p0           C State: up       Subdisks:     1 Size:        512 MB
     P mirror.p1           C State: initializing     Subdisks:     1 Size:        512 MB

     S myvol.p0.s0           State: up       PO:        0  B Size:        512 MB
         S mirror.p0.s0          State: up       PO:        0  B Size:        512 MB
         S mirror.p1.s0          State: empty    PO:        0  B Size:        512 MB

   ^1IS:I 20-5 shows the structure graphically.



   ^1IS:I 20-5. A Mirrored Vinum Volume

   In this example, each plex contains the full 512 MB of address
   space. As in the previous example, each plex contains only a
   single subdisk.

     --------------------------------------------------------------

  20.6.3. Optimizing Performance

   The mirrored volume in the previous example is more resistant to
   failure than an unmirrored volume, but its performance is less:
   each write to the volume requires a write to both drives, using up
   a greater proportion of the total disk bandwidth. Performance
   considerations demand a different approach: instead of mirroring,
   the data is striped across as many disk drives as possible. The
   following configuration shows a volume with a plex striped across
   four disk drives:

         drive c device /dev/da5h
         drive d device /dev/da6h
         volume stripe
         plex org striped 512k
           sd length 128m drive a
           sd length 128m drive b
           sd length 128m drive c
           sd length 128m drive d

   As before, it is not necessary to define the drives which are
   already known to Vinum. After processing this definition, the
   configuration looks like:

         Drives:         4 (4 configured)
         Volumes:        3 (4 configured)
         Plexes:         4 (8 configured)
         Subdisks:       7 (16 configured)

     D a                     State: up       Device /dev/da3h        Avail: 1421/2573 MB (55%)
     D b                     State: up       Device /dev/da4h        Avail: 1933/2573 MB (75%)
     D c                     State: up       Device /dev/da5h        Avail: 2445/2573 MB (95%)
     D d                     State: up       Device /dev/da6h        Avail: 2445/2573 MB (95%)

     V myvol                 State: up       Plexes:       1 Size:        512 MB
     V mirror                State: up       Plexes:       2 Size:        512 MB
     V striped               State: up       Plexes:       1 Size:        512 MB

     P myvol.p0            C State: up       Subdisks:     1 Size:        512 MB
     P mirror.p0           C State: up       Subdisks:     1 Size:        512 MB
     P mirror.p1           C State: initializing     Subdisks:     1 Size:        512 MB
     P striped.p1            State: up       Subdisks:     1 Size:        512 MB

     S myvol.p0.s0           State: up       PO:        0  B Size:        512 MB
     S mirror.p0.s0          State: up       PO:        0  B Size:        512 MB
     S mirror.p1.s0          State: empty    PO:        0  B Size:        512 MB
     S striped.p0.s0         State: up       PO:        0  B Size:        128 MB
     S striped.p0.s1         State: up       PO:      512 kB Size:        128 MB
     S striped.p0.s2         State: up       PO:     1024 kB Size:        128 MB
     S striped.p0.s3         State: up       PO:     1536 kB Size:        128 MB



   ^1IS:I 20-6. A Striped Vinum Volume

   This volume is represented in ^1IS:I 20-6. The darkness of the
   stripes indicates the position within the plex address space: the
   lightest stripes come first, the darkest last.

     --------------------------------------------------------------

  20.6.4. Resilience and Performance

   With sufficient hardware, it is possible to build volumes which
   show both increased resilience and increased performance compared
   to standard UNIX partitions. A typical configuration file might
   be:

         volume raid10
       plex org striped 512k
         sd length 102480k drive a
         sd length 102480k drive b
         sd length 102480k drive c
         sd length 102480k drive d
         sd length 102480k drive e
       plex org striped 512k
         sd length 102480k drive c
         sd length 102480k drive d
         sd length 102480k drive e
         sd length 102480k drive a
         sd length 102480k drive b

   The subdisks of the second plex are offset by two drives from
   those of the first plex: this helps ensure that writes do not go
   to the same subdisks even if a transfer goes over two drives.

   ^1IS:I 20-7 represents the structure of this volume.



   ^1IS:I 20-7. A Mirrored, Striped Vinum Volume

     --------------------------------------------------------------

20.7. Object Naming

   As described above, Vinum assigns default names to plexes and
   subdisks, although they may be overridden. Overriding the default
   names is not recommended: experience with the VERITAS volume
   manager, which allows arbitrary naming of objects, has shown that
   this flexibility does not bring a significant advantage, and it
   can cause confusion.

   Names may contain any non-blank character, but it is recommended
   to restrict them to letters, digits and the underscore characters.
   The names of volumes, plexes and subdisks may be up to 64
   characters long, and the names of drives may be up to 32
   characters long.

   Vinum objects are assigned device nodes in the hierarchy
   /dev/vinum. The configuration shown above would cause Vinum to
   create the following device nodes:

     * The control devices /dev/vinum/control and
       /dev/vinum/controld, which are used by vinum(8) and the Vinum
       daemon respectively.

     * Block and character device entries for each volume. These are
       the main devices used by Vinum. The block device names are the
       name of the volume, while the character device names follow
       the BSD tradition of prepending the letter r to the name. Thus
       the configuration above would include the block devices
       /dev/vinum/myvol, /dev/vinum/mirror, /dev/vinum/striped,
       /dev/vinum/raid5 and /dev/vinum/raid10, and the character
       devices /dev/vinum/rmyvol, /dev/vinum/rmirror,
       /dev/vinum/rstriped, /dev/vinum/rraid5 and /dev/vinum/rraid10.
       There is obviously a problem here: it is possible to have two
       volumes called r and rr, but there will be a conflict creating
       the device node /dev/vinum/rr: is it a character device for
       volume r or a block device for volume rr? Currently Vinum does
       not address this conflict: the first-defined volume will get
       the name.

     * A directory /dev/vinum/drive with entries for each drive.
       These entries are in fact symbolic links to the corresponding
       disk nodes.

     * A directory /dev/vinum/volume with entries for each volume. It
       contains subdirectories for each plex, which in turn contain
       subdirectories for their component subdisks.

     * The directories /dev/vinum/plex, /dev/vinum/sd, and
       /dev/vinum/rsd, which contain block device nodes for each plex
       and block and character device nodes respectively for each
       subdisk.

   For example, consider the following configuration file:

         drive drive1 device /dev/sd1h
         drive drive2 device /dev/sd2h
         drive drive3 device /dev/sd3h
         drive drive4 device /dev/sd4h
     volume s64 setupstate
       plex org striped 64k
         sd length 100m drive drive1
         sd length 100m drive drive2
         sd length 100m drive drive3
         sd length 100m drive drive4

   After processing this file, vinum(8) creates the following
   structure in /dev/vinum:

         brwx------  1 root  wheel   25, 0x40000001 Apr 13 16:46 Control
         brwx------  1 root  wheel   25, 0x40000002 Apr 13 16:46 control
         brwx------  1 root  wheel   25, 0x40000000 Apr 13 16:46 controld
         drwxr-xr-x  2 root  wheel       512 Apr 13 16:46 drive
         drwxr-xr-x  2 root  wheel       512 Apr 13 16:46 plex
         crwxr-xr--  1 root  wheel   91,   2 Apr 13 16:46 rs64
         drwxr-xr-x  2 root  wheel       512 Apr 13 16:46 rsd
         drwxr-xr-x  2 root  wheel       512 Apr 13 16:46 rvol
         brwxr-xr--  1 root  wheel   25,   2 Apr 13 16:46 s64
         drwxr-xr-x  2 root  wheel       512 Apr 13 16:46 sd
         drwxr-xr-x  3 root  wheel       512 Apr 13 16:46 vol

         /dev/vinum/drive:
     total 0
     lrwxr-xr-x  1 root  wheel  9 Apr 13 16:46 drive1 -> /dev/sd1h
     lrwxr-xr-x  1 root  wheel  9 Apr 13 16:46 drive2 -> /dev/sd2h
     lrwxr-xr-x  1 root  wheel  9 Apr 13 16:46 drive3 -> /dev/sd3h
     lrwxr-xr-x  1 root  wheel  9 Apr 13 16:46 drive4 -> /dev/sd4h

     /dev/vinum/plex:
     total 0
     brwxr-xr--  1 root  wheel   25, 0x10000002 Apr 13 16:46 s64.p0

     /dev/vinum/rsd:
     total 0
     crwxr-xr--  1 root  wheel   91, 0x20000002 Apr 13 16:46 s64.p0.s0
     crwxr-xr--  1 root  wheel   91, 0x20100002 Apr 13 16:46 s64.p0.s1
     crwxr-xr--  1 root  wheel   91, 0x20200002 Apr 13 16:46 s64.p0.s2
     crwxr-xr--  1 root  wheel   91, 0x20300002 Apr 13 16:46 s64.p0.s3

     /dev/vinum/rvol:
     total 0
     crwxr-xr--  1 root  wheel   91,   2 Apr 13 16:46 s64

     /dev/vinum/sd:
     total 0
     brwxr-xr--  1 root  wheel   25, 0x20000002 Apr 13 16:46 s64.p0.s0
     brwxr-xr--  1 root  wheel   25, 0x20100002 Apr 13 16:46 s64.p0.s1
     brwxr-xr--  1 root  wheel   25, 0x20200002 Apr 13 16:46 s64.p0.s2
     brwxr-xr--  1 root  wheel   25, 0x20300002 Apr 13 16:46 s64.p0.s3

     /dev/vinum/vol:
     total 1
     brwxr-xr--  1 root  wheel   25,   2 Apr 13 16:46 s64
     drwxr-xr-x  3 root  wheel       512 Apr 13 16:46 s64.plex

     /dev/vinum/vol/s64.plex:
     total 1
     brwxr-xr--  1 root  wheel   25, 0x10000002 Apr 13 16:46 s64.p0
     drwxr-xr-x  2 root  wheel       512 Apr 13 16:46 s64.p0.sd

     /dev/vinum/vol/s64.plex/s64.p0.sd:
     total 0
     brwxr-xr--  1 root  wheel   25, 0x20000002 Apr 13 16:46 s64.p0.s0
     brwxr-xr--  1 root  wheel   25, 0x20100002 Apr 13 16:46 s64.p0.s1
     brwxr-xr--  1 root  wheel   25, 0x20200002 Apr 13 16:46 s64.p0.s2
     brwxr-xr--  1 root  wheel   25, 0x20300002 Apr 13 16:46 s64.p0.s3

   Although it is recommended that plexes and subdisks should not be
   allocated specific names, Vinum drives must be named. This makes
   it possible to move a drive to a different location and still
   recognize it automatically. Drive names may be up to 32 characters
   long.

     --------------------------------------------------------------

  20.7.1. Creating File Systems

   Volumes appear to the system to be identical to disks, with one
   exception. Unlike UNIX drives, Vinum does not partition volumes,
   which thus do not contain a partition table. This has required
   modification to some disk utilities, notably newfs(8), which
   previously tried to interpret the last letter of a Vinum volume
   name as a partition identifier. For example, a disk drive may have
   a name like /dev/ad0a or /dev/da2h. These names represent the
   first partition (a) on the first (0) IDE disk (ad) and the eighth
   partition (h) on the third (2) SCSI disk (da) respectively. By
   contrast, a Vinum volume might be called /dev/vinum/concat, a name
   which has no relationship with a partition name.

   Normally, newfs(8) interprets the name of the disk and complains
   if it cannot understand it. For example:

 # newfs /dev/vinum/concat
 newfs: /dev/vinum/concat: can't figure out file system partition

     -a`: The following is only valid for FreeBSD versions prior to
     5.0:

   In order to create a file system on this volume, use the -v option
   to newfs(8):

 # newfs -v /dev/vinum/concat

     --------------------------------------------------------------

20.8. Configuring Vinum

   The GENERIC kernel does not contain Vinum. It is possible to build
   a special kernel which includes Vinum, but this is not
   recommended. The standard way to start Vinum is as a kernel module
   (kld). You do not even need to use kldload(8) for Vinum: when you
   start vinum(8), it checks whether the module has been loaded, and
   if it is not, it loads it automatically.

     --------------------------------------------------------------

  20.8.1. Startup

   Vinum stores configuration information on the disk slices in
   essentially the same form as in the configuration files. When
   reading from the configuration database, Vinum recognizes a number
   of keywords which are not allowed in the configuration files. For
   example, a disk configuration might contain the following text:

 volume myvol state up
 volume bigraid state down
 plex name myvol.p0 state up org concat vol myvol
 plex name myvol.p1 state up org concat vol myvol
 plex name myvol.p2 state init org striped 512b vol myvol
 plex name bigraid.p0 state initializing org raid5 512b vol bigraid
 sd name myvol.p0.s0 drive a plex myvol.p0 state up len 1048576b driveoffset 265b plexoffset 0b
 sd name myvol.p0.s1 drive b plex myvol.p0 state up len 1048576b driveoffset 265b plexoffset 1048576b
 sd name myvol.p1.s0 drive c plex myvol.p1 state up len 1048576b driveoffset 265b plexoffset 0b
 sd name myvol.p1.s1 drive d plex myvol.p1 state up len 1048576b driveoffset 265b plexoffset 1048576b
 sd name myvol.p2.s0 drive a plex myvol.p2 state init len 524288b driveoffset 1048841b plexoffset 0b
 sd name myvol.p2.s1 drive b plex myvol.p2 state init len 524288b driveoffset 1048841b plexoffset 524288b
 sd name myvol.p2.s2 drive c plex myvol.p2 state init len 524288b driveoffset 1048841b plexoffset 1048576b
 sd name myvol.p2.s3 drive d plex myvol.p2 state init len 524288b driveoffset 1048841b plexoffset 1572864b
 sd name bigraid.p0.s0 drive a plex bigraid.p0 state initializing len 4194304b driveoff set 1573129b plexoffset 0b
 sd name bigraid.p0.s1 drive b plex bigraid.p0 state initializing len 4194304b driveoff set 1573129b plexoffset 4194304b
 sd name bigraid.p0.s2 drive c plex bigraid.p0 state initializing len 4194304b driveoff set 1573129b plexoffset 8388608b
 sd name bigraid.p0.s3 drive d plex bigraid.p0 state initializing len 4194304b driveoff set 1573129b plexoffset 12582912b
 sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b driveoff set 1573129b plexoffset 16777216b

   The obvious differences here are the presence of explicit location
   information and naming (both of which are also allowed, but
   discouraged, for use by the user) and the information on the
   states (which are not available to the user). Vinum does not store
   information about drives in the configuration information: it
   finds the drives by scanning the configured disk drives for
   partitions with a Vinum label. This enables Vinum to identify
   drives correctly even if they have been assigned different UNIX
   drive IDs.

     --------------------------------------------------------------

    20.8.1.1. Automatic Startup

   In order to start Vinum automatically when you boot the system,
   ensure that you have the following line in your /etc/rc.conf:

 start_vinum="YES"               # set to YES to start vinum

   If you do not have a file /etc/rc.conf, create one with this
   content. This will cause the system to load the Vinum kld at
   startup, and to start any objects mentioned in the configuration.
   This is done before mounting file systems, so it is possible to
   automatically fsck(8) and mount file systems on Vinum volumes.

   When you start Vinum with the vinum start command, Vinum reads the
   configuration database from one of the Vinum drives. Under normal
   circumstances, each drive contains an identical copy of the
   configuration database, so it does not matter which drive is read.
   After a crash, however, Vinum must determine which drive was
   updated most recently and read the configuration from this drive.
   It then updates the configuration if necessary from progressively
   older drives.

     --------------------------------------------------------------

20.9. Using Vinum for the Root Filesystem

   For a machine that has fully-mirrored filesystems using Vinum, it
   is desirable to also mirror the root filesystem. Setting up such a
   configuration is less trivial than mirroring an arbitrary
   filesystem because:

     * The root filesystem must be available very early during the
       boot process, so the Vinum infrastructure must already be
       available at this time.

     * The volume containing the root filesystem also contains the
       system bootstrap and the kernel, which must be read using the
       host system's native utilities (e. g. the BIOS on PC-class
       machines) which often cannot be taught about the details of
       Vinum.

   In the following sections, the term !S:root volume!" is generally
   used to describe the Vinum volume that contains the root
   filesystem. It is probably a good idea to use the name "root" for
   this volume, but this is not technically required in any way. All
   command examples in the following sections assume this name
   though.

     --------------------------------------------------------------

  20.9.1. Starting up Vinum Early Enough for the Root Filesystem

   There are several measures to take for this to happen:

     * Vinum must be available in the kernel at boot-time. Thus, the
       method to start Vinum automatically described in uU 20.8.1.1
       ,` is not applicable to accomplish this task, and the
       start_vinum parameter must actually not be set when the
       following setup is being arranged. The first option would be
       to compile Vinum statically into the kernel, so it is
       available all the time, but this is usually not desirable.
       There is another option as well, to have /boot/loader (uU
       12.3.3 ,`) load the vinum kernel module early, before starting
       the kernel. This can be accomplished by putting the line:

 vinum_load="YES"

       into the file /boot/loader.conf.

     * Vinum must be initialized early since it needs to supply the
       volume for the root filesystem. By default, the Vinum kernel
       part is not looking for drives that might contain Vinum volume
       information until the administrator (or one of the startup
       scripts) issues a vinum start command.

         -a`: The following paragraphs are outlining the steps needed
         for FreeBSD 5.X and above. The setup required for FreeBSD
         4.X differs, and is described below in uU 20.9.5 ,`.

       By placing the line:

 vinum.autostart="YES"

       into /boot/loader.conf, Vinum is instructed to automatically
       scan all drives for Vinum information as part of the kernel
       startup.

       Note that it is not necessary to instruct the kernel where to
       look for the root filesystem. /boot/loader looks up the name
       of the root device in /etc/fstab, and passes this information
       on to the kernel. When it comes to mount the root filesystem,
       the kernel figures out from the device name provided which
       driver to ask to translate this into the internal device ID
       (major/minor number).

     --------------------------------------------------------------

  20.9.2. Making a Vinum-based Root Volume Accessible to the Bootstrap

   Since the current FreeBSD bootstrap is only 7.5 KB of code, and
   already has the burden of reading files (like /boot/loader) from
   the UFS filesystem, it is sheer impossible to also teach it about
   internal Vinum structures so it could parse the Vinum
   configuration data, and figure out about the elements of a boot
   volume itself. Thus, some tricks are necessary to provide the
   bootstrap code with the illusion of a standard "a" partition that
   contains the root filesystem.

   For this to be possible at all, the following requirements must be
   met for the root volume:

     * The root volume must not be striped or RAID-5.

     * The root volume must not contain more than one concatenated
       subdisk per plex.

   Note that it is desirable and possible that there are multiple
   plexes, each containing one replica of the root filesystem. The
   bootstrap process will, however, only use one of these replica for
   finding the bootstrap and all the files, until the kernel will
   eventually mount the root filesystem itself. Each single subdisk
   within these plexes will then need its own "a" partition illusion,
   for the respective device to become bootable. It is not strictly
   needed that each of these faked "a" partitions is located at the
   same offset within its device, compared with other devices
   containing plexes of the root volume. However, it is probably a
   good idea to create the Vinum volumes that way so the resulting
   mirrored devices are symmetric, to avoid confusion.

   In order to set up these "a" partitions, for each device
   containing part of the root volume, the following needs to be
   done:

    1. The location (offset from the beginning of the device) and
       size of this device's subdisk that is part of the root volume
       need to be examined, using the command:

 # vinum l -rv root

       Note that Vinum offsets and sizes are measured in bytes. They
       must be divided by 512 in order to obtain the block numbers
       that are to be used in the disklabel command.

    2. Run the command:

 # disklabel -e devname

       for each device that participates in the root volume. devname
       must be either the name of the disk (like da0) for disks
       without a slice (aka. fdisk) table, or the name of the slice
       (like ad0s1).

       If there is already an "a" partition on the device
       (presumably, containing a pre-Vinum root filesystem), it
       should be renamed to something else, so it remains accessible
       (just in case), but will no longer be used by default to
       bootstrap the system. Note that active partitions (like a root
       filesystem currently mounted) cannot be renamed, so this must
       be executed either when being booted from a !S:Fixit!" medium,
       or in a two-step process, where (in a mirrored situation) the
       disk that has not been currently booted is being manipulated
       first.

       Then, the offset the Vinum partition on this device (if any)
       must be added to the offset of the respective root volume
       subdisk on this device. The resulting value will become the
       "offset" value for the new "a" partition. The "size" value for
       this partition can be taken verbatim from the calculation
       above. The "fstype" should be 4.2BSD. The "fsize", "bsize",
       and "cpg" values should best be chosen to match the actual
       filesystem, though they are fairly unimportant within this
       context.

       That way, a new "a" partition will be established that
       overlaps the Vinum partition on this device. Note that the
       disklabel will only allow for this overlap if the Vinum
       partition has properly been marked using the "vinum" fstype.

    3. That's all! A faked "a" partition does exist now on each
       device that has one replica of the root volume. It is highly
       recommendable to verify the result again, using a command
       like:

 # fsck -n /dev/devnamea

   It should be remembered that all files containing control
   information must be relative to the root filesystem in the Vinum
   volume which, when setting up a new Vinum root volume, might not
   match the root filesystem that is currently active. So in
   particular, the files /etc/fstab and /boot/loader.conf need to be
   taken care of.

   At next reboot, the bootstrap should figure out the appropriate
   control information from the new Vinum-based root filesystem, and
   act accordingly. At the end of the kernel initialization process,
   after all devices have been announced, the prominent notice that
   shows the success of this setup is a message like:

 Mounting root from ufs:/dev/vinum/root

     --------------------------------------------------------------

  20.9.3. Example of a Vinum-based Root Setup

   After the Vinum root volume has been set up, the output of vinum l
   -rv root could look like:

 ...
 Subdisk root.p0.s0:
                 Size:        125829120 bytes (120 MB)
                 State: up
                 Plex root.p0 at offset 0 (0  B)
                 Drive disk0 (/dev/da0h) at offset 135680 (132 kB)

 Subdisk root.p1.s0:
                 Size:        125829120 bytes (120 MB)
                 State: up
                 Plex root.p1 at offset 0 (0  B)
                 Drive disk1 (/dev/da1h) at offset 135680 (132 kB)
        

   The values to note are 135680 for the offset (relative to
   partition /dev/da0h). This translates to 265 512-byte disk blocks
   in disklabel's terms. Likewise, the size of this root volume is
   245760 512-byte blocks. /dev/da1h, containing the second replica
   of this root volume, has a symmetric setup.

   The disklabel for these devices might look like:

 ...
 8 partitions:
 #        size   offset    fstype   [fsize bsize bps/cpg]
   a:   245760      281    4.2BSD     2048 16384     0   # (Cyl.    0*- 15*)
   c: 71771688        0    unused        0     0         # (Cyl.    0 - 4467*)
   h: 71771672       16     vinum                        # (Cyl.    0*- 4467*)
        

   It can be observed that the "size" parameter for the faked "a"
   partition matches the value outlined above, while the "offset"
   parameter is the sum of the offset within the Vinum partition "h",
   and the offset of this partition within the device (or slice).
   This is a typical setup that is necessary to avoid the problem
   described in uU 20.9.4.3 ,`. It can also be seen that the entire
   "a" partition is completely within the "h" partition containing
   all the Vinum data for this device.

   Note that in the above example, the entire device is dedicated to
   Vinum, and there is no leftover pre-Vinum root partition, since
   this has been a newly set-up disk that was only meant to be part
   of a Vinum configuration, ever.

     --------------------------------------------------------------

  20.9.4. Troubleshooting

   If something goes wrong, a way is needed to recover from the
   situation. The following list contains few known pitfalls and
   solutions.

     --------------------------------------------------------------

    20.9.4.1. System Bootstrap Loads, but System Does Not Boot

   If for any reason the system does not continue to boot, the
   bootstrap can be interrupted with by pressing the space key at the
   10-seconds warning. The loader variables (like vinum.autostart)
   can be examined using the show, and manipulated using set or unset
   commands.

   If the only problem was that the Vinum kernel module was not yet
   in the list of modules to load automatically, a simple load vinum
   will help.

   When ready, the boot process can be continued with a boot -as. The
   options -as will request the kernel to ask for the root filesystem
   to mount (-a), and make the boot process stop in single-user mode
   (-s), where the root filesystem is mounted read-only. That way,
   even if only one plex of a multi-plex volume has been mounted, no
   data inconsistency between plexes is being risked.

   At the prompt asking for a root filesystem to mount, any device
   that contains a valid root filesystem can be entered. If
   /etc/fstab had been set up correctly, the default should be
   something like ufs:/dev/vinum/root. A typical alternate choice
   would be something like ufs:da0d which could be a hypothetical
   partition that contains the pre-Vinum root filesystem. Care should
   be taken if one of the alias "a" partitions are entered here that
   are actually reference to the subdisks of the Vinum root device,
   because in a mirrored setup, this would only mount one piece of a
   mirrored root device. If this filesystem is to be mounted
   read-write later on, it is necessary to remove the other plex(es)
   of the Vinum root volume since these plexes would otherwise carry
   inconsistent data.

     --------------------------------------------------------------

    20.9.4.2. Only Primary Bootstrap Loads

   If /boot/loader fails to load, but the primary bootstrap still
   loads (visible by a single dash in the left column of the screen
   right after the boot process starts), an attempt can be made to
   interrupt the primary bootstrap at this point, using the space
   key. This will make the bootstrap stop in stage two, see uU 12.3.2
   ,`. An attempt can be made here to boot off an alternate
   partition, like the partition containing the previous root
   filesystem that has been moved away from "a" above.

     --------------------------------------------------------------

    20.9.4.3. Nothing Boots, the Bootstrap Panics

   This situation will happen if the bootstrap had been destroyed by
   the Vinum installation. Unfortunately, Vinum accidentally
   currently leaves only 4 KB at the beginning of its partition free
   before starting to write its Vinum header information. However,
   the stage one and two bootstraps plus the disklabel embedded
   between them currently require 8 KB. So if a Vinum partition was
   started at offset 0 within a slice or disk that was meant to be
   bootable, the Vinum setup will trash the bootstrap.

   Similarly, if the above situation has been recovered, for example
   by booting from a !S:Fixit!" medium, and the bootstrap has been
   re-installed using disklabel -B as described in uU 12.3.2 ,`, the
   bootstrap will trash the Vinum header, and Vinum will no longer
   find its disk(s). Though no actual Vinum configuration data or
   data in Vinum volumes will be trashed by this, and it would be
   possible to recover all the data by entering exact the same Vinum
   configuration data again, the situation is hard to fix at all. It
   would be necessary to move the entire Vinum partition by at least
   4 KB off, in order to have the Vinum header and the system
   bootstrap no longer collide.

     --------------------------------------------------------------

  20.9.5. Differences for FreeBSD 4.X

   Under FreeBSD 4.X, some internal functions required to make Vinum
   automatically scan all disks are missing, and the code that
   figures out the internal ID of the root device is not smart enough
   to handle a name like /dev/vinum/root automatically. Therefore,
   things are a little different here.

   Vinum must explicitly be told which disks to scan, using a line
   like the following one in /boot/loader.conf:

 vinum.drives="/dev/da0 /dev/da1"

   It is important that all drives are mentioned that could possibly
   contain Vinum data. It does not harm if more drives are listed,
   nor is it necessary to add each slice and/or partition explicitly,
   since Vinum will scan all slices and partitions of the named
   drives for valid Vinum headers.

   Since the routines used to parse the name of the root filesystem,
   and derive the device ID (major/minor number) are only prepared to
   handle !S:classical!" device names like /dev/ad0s1a, they cannot
   make any sense out of a root volume name like /dev/vinum/root. For
   that reason, Vinum itself needs to pre-setup the internal kernel
   parameter that holds the ID of the root device during its own
   initialization. This is requested by passing the name of the root
   volume in the loader variable vinum.root. The entry in
   /boot/loader.conf to accomplish this looks like:

 vinum.root="root"

   Now, when the kernel initialization tries to find out the root
   device to mount, it sees whether some kernel module has already
   pre-initialized the kernel parameter for it. If that is the case,
   and the device claiming the root device matches the major number
   of the driver as figured out from the name of the root device
   string being passed (that is, "vinum" in our case), it will use
   the pre-allocated device ID, instead of trying to figure out one
   itself. That way, during the usual automatic startup, it can
   continue to mount the Vinum root volume for the root filesystem.

   However, when boot -a has been requesting to ask for entering the
   name of the root device manually, it must be noted that this
   routine still cannot actually parse a name entered there that
   refers to a Vinum volume. If any device name is entered that does
   not refer to a Vinum device, the mismatch between the major
   numbers of the pre-allocated root parameter and the driver as
   figured out from the given name will make this routine enter its
   normal parser, so entering a string like ufs:da0d will work as
   expected. Note that if this fails, it is however no longer
   possible to re-enter a string like ufs:vinum/root again, since it
   cannot be parsed. The only way out is to reboot again, and start
   over then. (At the !S:askroot!" prompt, the initial /dev/ can
   always be omitted.)

     --------------------------------------------------------------

               ^3^1 21. Virtualization(ueAA 3/4-: 3/4^1)

   Contributed by Murray Stokely.

21.1. Synopsis

   ueAA 3/4-: 3/4^1^3nAAeYENiYENHAAy|PCUR@YENx 3/4-:
   3/4^1+-oYENH|P(R)EDEGo|ae|h-oO/S:@.~"t^2I!C |b PC CURW!A
   ^3q+-`^3oAth"t^2I^3-L-NOTO|b+-JYEND(host) 3/4-: 3/4^1CURW,EueAA
   3/4-: 3/4^1^3nAAe!A"OP:]CUR@DEGi guest OS !C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!J

     * host OS YENHCURI guest OS -a-oDEGIS:O!C

     * |p|o|b.f,u: Intel CPU -a-o Apple(R) Macintosh ^1q,-L-CURW|w,E
       FreeBSD !C

     * |p|o|b Linux CURWYENH Xen(TM) "O|w,E FreeBSD!C

     * |p|o|b Microsoft Windows CURWYENH Virtual PC |w,E FreeBSD!C

     * |p|o|bueAA 3/4-: 3/4^1^1i FreeBSD "t^2IS:@(c)E-`a
       1/2O(R)O!AYENH"u+-o^3I"I(R)A:-`a!C

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!J

     * AA,N UNIX CURI FreeBSD NOTUAo:DEGoYEN>>.S:(c)A (uU 3 ^3^1)!C

     * -a 3/4^1D|p|o|w,E FreeBSD(uU 2 ^3^1)!C

     * -a 3/4^1D|p|o^3](c)w-oo,o(uU 29 ^3^1)!C

     * -a 3/4^1D|p|oYENH ports/packages "O|w,EA^3YENIu{|! (uU 4
       ^3^1)!C

     --------------------------------------------------------------

21.2. |w,E FreeBSD NOTDEG Guest OS

  21.2.1. MacOS CURW-a-o Parallels

   Mac -a(c)-a-o Parallels Desktop CURDNOTOYENiYENI(c)o.fDEGt Intel
   CPU YENHCURI Mac OS 10.4.6 YENHCURW-a-o Apple Mac
   ^1q,-L--a-oDEGO.~^3nAAe!C FreeBSD NOTO"a:|^3S:^1 3/4aCURa:'(c)-a-o
   guest OS CURS:CUR@!C |b Mac OS X ,E|n Parallels <<a!A
   YEN^2P:.DEGw^1i(c)O+-y|w,E-a-o guest OS "OS:@NOTUAo:-a-oueAA 3/4-:
   3/4^1^3](c)w!C

     --------------------------------------------------------------

    21.2.1.1. |b Parallels/Mac OS(R) X CURW|w,E FreeBSD

   |b Mac OS X/Parallels CURW|w,E FreeBSD -a-o^2A:CUR@"BNOTO.s
   1/4WueAA 3/4-: 3/4^1!C |pCURU(c)OYENU:!A|b'-L-YENU:uo/u!CUR-o
   1/2D-+-N Guest OS Type CURA:?iNOTDEG FreeBSD!G

   "A"I 3/4U|U">>Y"D"O^3W^1-ouw-oD-(R)eP:q,oDEGO
   3/4D-AAe-a-oCURADEGt!C ^1iCURj|h 1/4AE|b Parallels
   "IYENI-a-o+-!-ap|O"YEN!ACURjNOTu 4GB uw-oD-YENHCURI 512MB RAM
   'NDEG-:YENICURF!G

   +-uCURU"O!A?i 3/4U:-oo,o-oO/AthYENHCURI-oo,oYENd!G

   ^3I<<a!AAx|s^3](c)wAE'NS:^1|"^3](c)wCURF!G

   |b FreeBSD ueAA 3/4-: 3/4^1.s 1/4W<<a!A'NYENiYENHA:~A:oYENH"a:|w,E
   FreeBSD!C |w,ECURe+-!ACURn,u|n-a-oS:@-akNOTO"IYENI(c)xCURe-a-o
   FreeBSD YENu-oD-(c)I-aI+-q(c)xCURe FTP -,CURU,u: ISO image AE!C
   Y+-z-a-o Mac YEN>> 3/4-:CURw,g|^3,O ISO AE!A (c)I-aI Mac
   -a-oYENu-oD- 3/4-:CUR-o|^3(c)n|w,ECURu!A"-o>>o'NYENiYENH|b FreeBSD
   -a-o Parallels uo/u!YENkCURU"CUR<<o:CURUYENu-oD-CURu^1IYENU:!C
   +-uuU.|YENX^2{CUR@Ouo/u!!AYENiYENHS:aueAA 3/4-:
   3/4^1CUR-o-a-oYENu-oD- 3/4-:^3](c)w"`i,O ISO AE!A
   (c)I-aINOTO^1eAAeYENu-oD- 3/4-:!C

   ^3]|nYENu-oD-CURu"O. 1/2CURS:<<a!A'NYENiYENH<<o:CURU<<P:}
   3/4-:^1IYENU:YENH<<P:} FreeBSD ueAA 3/4-: 3/4^1!C Parallels
   .|YENH-S(R)i BIOS P:} 3/4-:!A"A>>P'P:^3q-a-o BIOS CUR@
   1/4E.|YENyAENOTdNOTOS:_|^3YENu-oD- 3/4-:!C

   |^1(R)E!AYEN|'N.|S:a:"`i FreeBSD |w,ECURu!A"AP:}(c)l|b uU 2 ^3^1
   CUR-o(c)OCURP:^2D-"`i-a-o sysinstall |w,E^1Lu{!C
   ^3o(R)EOCUR]YENiP:P:<<K,E X11!A|yYENyCUR-L-nP:i|aeNOTUAo:^3](c)w!C

   S:^1|"|w,E^1Lu{CURS:<<a!A'NYENiYENH<<P:}e,E-a-o FreeBSD ueAA 3/4-:
   3/4^1!C

     --------------------------------------------------------------

    21.2.1.2. |b Mac OS X/Parallels CURW^3](c)w FreeBSD

   S:a FreeBSD |"YEN\,E"`i Mac OS X -a-o Parallels
   CURS:<<a!AAU>>YnS:@CUR@"C,^3](c)w"BAEJ!A YENH<<K+-NueAA 3/4-:
   3/4^1CUR-o-a-o FreeBSD ^3I"ICURAE!C

    1. ^3](c)w boot loader DEGN 1/4AE

       ^3I<<n-a-o"BAEJCURDNOTOAC,YENN 1/2ODEG kern.hz "ODEGS:C
       Parallels Ao^1OCUR-o FreeBSD -a-o CPU |uYENI^2v!C YENiYENH|b
       /boot/loader.conf CUR-oYEN[CURWCURU|C^3](c)wS:YYENi!G

 kern.hz=100

       YCUR-L-S:@^3o^3](c)w!A"-o>>oYENuNOTO idle -aNOT-oA-a-o FreeBSD
       (Parallels guest OS) 'N.||bP:E^3aeCUR@^3B^2z 3/4^1-a-o iMac(R)
       CURW|uCURFCURjNOTu 15% -a-o CPU |uYENI^2v!C S:@CURWz
       *S:iCURS:<<a!A|uYENI^2v'N.|DEG|U:CURjNOTu 5%!C

    2. ^3](c)w.s-a-o kernel ^3](c)wAE

       YENiYENH(c)nCURssS:a(c)O|^3 SCSI!BFireWire!BUSB
       NOTUAo:^3]^3AE^3-L-^2 3/4DEG-L-!C Parallels |^3'-L-"N ed(4)
       -a-oueAA-ooYENd!A|]|^1!ADEG-L-CURF ed(4) YENHCURI miibus(4)
       YENHYEN~-a-o"a:YENL-oo,oYENdCUR]^3-L-YENiYENH+-q kernel
       CURCUR^2 3/4DEG-L-!C

    3. ^3](c)w-oo,o

       YENiYENH'AueAA 3/4-: 3/4^1A^2^3aeYENI DHCP "O^3](c)w>>P Mac
       NOTU|P-a-o LAN -oo,oAo^1O!AYENun|b /etc/rc.conf CUR-oYEN[CURW
       ifconfig_ed0="DHCP" S:YYENiS:^1|"!C
       "a:YENLP:iP:YEN-a-o-oo,o^3](c)wCURe|!!A 1/2D-DEGN|O uU 29
       ^3^1!C

     --------------------------------------------------------------

  21.2.2. |b Linux ^3z^1L Xen(TM) P:] FreeBSD

   Contributed by Fukang Chen (Loader).

   Xen hypervisor CURDNOTOP:}(c)n. 1/2 1/2X-a-o paravirtualization
   ^2-L-<<~!A"AYENNDEGO.~CUR 1/2YENq(XenSource)'-L-"NCURa:'(c)!C
   Guest OS ^3q+-`^3Q-oUNOTDEG domU domains!A|O host OS
   <<hNOTO^3Q-oUNOTDEG dom0!C |b Linux CURW<<O/YENss FreeBSD ueAA
   3/4-: 3/4^1-a-o^2A:CUR@"B!A<<hNOTO|w,E Linux dom0 -a-o Xen!C
   |bYEN>>"OCURCUR!A host OS CURDNOTO Slackware Linux!C

     --------------------------------------------------------------

    21.2.2.1. |b Linux dom0 CURW^3](c)w Xen 3

    1. +-q XenSource -oo-,CURU,u: Xen 3.0

       +-q http://www.xensource.com/ CURU,u: xen-3.0.4_1-src.tgz!C

    2. ,NA-L-AY

 # cd xen-3.0.4_1-src
 # KERNELS="linux-2.6-xen0 linux-2.6-xenU" make world
 # make install

         -a`: NOTDEG dom0 <<.s 1/2sA:P: kernel!G

 # cd xen-3.0.4_1-src/linux-2.6.16.33-xen0
 # make menuconfig
 # make
 # make install

         AA-a(c)-a-o Xen YENi-`a>>YnYENI make ARCH=xen menuconfig

    3. 1/4WYEN[?iP:u"`i Grub -a-o menu.lst ?i^3ae

       *S:i /boot/grub/menu.lst YEN[CURWCURU|C^3](c)w!G

 title Xen-3.0.4
 root (hd0,0)
 kernel /boot/xen-3.0.4-1.gz dom0_mem=262144
 module /boot/vmlinuz-2.6.16.33-xen0 root=/dev/hda1 ro

    4. <<P:} 3/4-:"AP:iCURJ Xen

       -oYENy!A *S:i /etc/xen/xend-config.sxp YEN[CURWCURU|C^3](c)w!G

 (network-script 'network-bridge netdev=eth0')

       +-uCURU"O!A'NYENiYENH+-ODEGE Xen!G

 # /etc/init.d/xend start
 # /etc/init.d/xendomains start

       ^2{|b dom0 CURw,gP:}(c)l^1BS:@!G

 # xm list
 Name                                      ID   Mem VCPUs      State   Time(s)
 Domain-0                                   0   256     1     r-----  54452.9

     --------------------------------------------------------------

    21.2.2.2. FreeBSD 7-CURRENT domU

   +-q http://www.fsmware.com/ CURU,u:.fDEGt Xen 3.0 -a-o FreeBSD
   domU kernel NOTUAo:AE(R) *

     * kernel-current

     * mdroot-7.0.bz2

     * xmexample1.bsd

   S:a xmexample1.bsd ^3](c)wAE(c)n"`i /etc/xen/!A"A *S:i kernel CURI
   disk image NOTUAo:|`i,m!C YENHCURUNOTOYENU: 1/2d-a-o"OCURl!G

 kernel = "/opt/kernel-current"
 memory = 256
 name = "freebsd"
 vif = [ '' ]
 disk = [ 'file:/opt/mdroot-7.0,hda1,w' ]
 #on_crash    = 'preserve'
 extra = "boot_verbose"
 extra += ",boot_single"
 extra += ",kern.hz=100"
 extra += ",vfs.root.mountfrom=ufs:/dev/xbd769a"

   "a:CURCUR mdroot-7.0.bz2 AEnDEGO+-o,NA-L-AYCURS:!C

   +-uCURU"O!An *S:i kernel-current ^3](c)wAE-a-o __xen_guest
   CURp,`!A"AYEN[CURW Xen 3.0.3 (c)O>>Y-a-o VIRT_BASE!G

 # objcopy kernel-current -R __xen_guest
 # perl -e 'print "LOADER=generic,GUEST_OS=freebsd,GUEST_VER=7.0,XEN_VER=xen-3.0,BSD_SYMTAB,VIRT_BASE=0xC0000000\x00"' > tmp
 # objcopy kernel-current --add-section __xen_guest=tmp

 # objdump -j __xen_guest -s kernel-current

 kernel-current:     file format elf32-i386

 Contents of section __xen_guest:
  0000 4c4f4144 45523d67 656e6572 69632c47  LOADER=generic,G
  0010 55455354 5f4f533d 66726565 6273642c  UEST_OS=freebsd,
  0020 47554553 545f5645 523d372e 302c5845  GUEST_VER=7.0,XE
  0030 4e5f5645 523d7865 6e2d332e 302c4253  N_VER=xen-3.0,BS
  0040 445f5359 4d544142 2c564952 545f4241  D_SYMTAB,VIRT_BA
  0050 53453d30 78433030 30303030 3000      SE=0xC0000000.

   ^2{|bYENiYENH.s 1/4W"A+-ODEGE domU AAo!G

 # xm create /etc/xen/xmexample1.bsd -c
 Using config file "/etc/xen/xmexample1.bsd".
 Started domain freebsd
 WARNING: loader(8) metadata is missing!
 Copyright (c) 1992-2006 The FreeBSD Project.
 Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
 The Regents of the University of California. All rights reserved.
 FreeBSD 7.0-CURRENT #113: Wed Jan  4 06:25:43 UTC 2006
     kmacy@freebsd7.gateway.2wire.net:/usr/home/kmacy/p4/freebsd7_xen3/src/sys/i386-xen/compile/XENCONF
 WARNING: DIAGNOSTIC option enabled, expect reduced performance.
 Xen reported: 1796.927 MHz processor.
 Timecounter "ixen" frequency 1796927000 Hz quality 0
 CPU: Intel(R) Pentium(R) 4 CPU 1.80GHz (1796.93-MHz 686-class CPU)
   Origin = "GenuineIntel"  Id = 0xf29  Stepping = 9
   Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,
   DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
   Features2=0x4400<CNTX-ID,<b14>>
 real memory  = 265244672 (252 MB)
 avail memory = 255963136 (244 MB)
 xc0: <Xen Console> on motherboard
 cpu0 on motherboard
 Timecounters tick every 10.000 msec
 [XEN] Initialising virtual ethernet driver.
 xn0: Ethernet address: 00:16:3e:6b:de:3a
 [XEN]
 Trying to mount root from ufs:/dev/xbd769a
 WARNING: / was not properly dismounted
 Loading configuration files.
 No suitable dump device was found.
 Entropy harvesting: interrupts ethernet point_to_point kickstart.
 Starting file system checks:
 /dev/xbd769a: 18859 files, 140370 used, 113473 free (10769 frags, 12838 blocks, 4.2% fragmentation)
 Setting hostname: demo.freebsd.org.
 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
           inet6 ::1 prefixlen 128
           inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
           inet 127.0.0.1 netmask 0xff000000
 Additional routing options:.
 Mounting NFS file systems:.
 Starting syslogd.
 /etc/rc: WARNING: Dump device does not exist.  Savecore not run.
 ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib
 a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout
 Starting usbd.
 usb: Kernel module not available: No such file or directory
 Starting local daemons:.
 Updating motd.
 Starting sshd.
 Initial i386 initialization:.
 Additional ABI support: linux.
 Starting cron.
 Local package initialization:.
 Additional TCP options:.
 Starting background file system checks in 60 seconds.

 Sun Apr  1 02:11:43 UTC 2007

 FreeBSD/i386 (demo.freebsd.org) (xc0)

 login:

   ^2{|b domU A^3,OYENiYENHP:] FreeBSD 7.0-CURRENT kernel!G

 # uname -a
 FreeBSD demo.freebsd.org 7.0-CURRENT FreeBSD 7.0-CURRENT #113: Wed Jan  4 06:25:43 UTC 2006
 kmacy@freebsd7.gateway.2wire.net:/usr/home/kmacy/p4/freebsd7_xen3/src/sys/i386-xen/compile/XENCONF  i386

   +-uCURU"ONOTO^3](c)w domU -a-o-oo,o!AFreeBSD domU
   .|YENIYENN,^1NOTDEG xn0 -a-o-S(R)i-oo,oYENd!G

 # ifconfig xn0 10.10.10.200 netmask 255.0.0.0
 # ifconfig
 xn0: flags=843<UP,BROADCAST,RUNNING,SIMPLEX> mtu 1500
     inet 10.10.10.200 netmask 0xff000000 broadcast 10.255.255.255
     ether 00:16:3e:6b:de:3a
 lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
       inet6 ::1 prefixlen 128
       inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
       inet 127.0.0.1 netmask 0xff000000

   |b dom0 Slackware CURWA^3,O.|YENX^2{CUR@"C, Xen
   +-MYENI-a-o-oo,oYENd!G

 # ifconfig
 eth0      Link encap:Ethernet  HWaddr 00:07:E9:A0:02:C2
           inet addr:10.10.10.130  Bcast:0.0.0.0  Mask:255.0.0.0
           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
           RX packets:815 errors:0 dropped:0 overruns:0 frame:0
           TX packets:1400 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:204857 (200.0 KiB)  TX bytes:129915 (126.8 KiB)

 lo        Link encap:Local Loopback
           inet addr:127.0.0.1  Mask:255.0.0.0
           UP LOOPBACK RUNNING  MTU:16436  Metric:1
           RX packets:99 errors:0 dropped:0 overruns:0 frame:0
           TX packets:99 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:9744 (9.5 KiB)  TX bytes:9744 (9.5 KiB)

 peth0     Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
           RX packets:1853349 errors:0 dropped:0 overruns:0 frame:0
           TX packets:952923 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:2432115831 (2.2 GiB)  TX bytes:86528526 (82.5 MiB)
           Base address:0xc000 Memory:ef020000-ef040000

 vif0.1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
           RX packets:1400 errors:0 dropped:0 overruns:0 frame:0
           TX packets:815 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:129915 (126.8 KiB)  TX bytes:204857 (200.0 KiB)

 vif1.0    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
           RX packets:3 errors:0 dropped:0 overruns:0 frame:0
           TX packets:2 errors:0 dropped:157 overruns:0 carrier:0
           collisions:0 txqueuelen:1
           RX bytes:140 (140.0 b)  TX bytes:158 (158.0 b)

 xenbr1    Link encap:Ethernet  HWaddr FE:FF:FF:FF:FF:FF
           UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
           RX packets:4 errors:0 dropped:0 overruns:0 frame:0
           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:0
           RX bytes:112 (112.0 b)  TX bytes:0 (0.0 b)

 # brctl show
 bridge name     bridge id           STP enabled         interfaces
 xenbr1          8000.feffffffffff   no                  vif0.1
                                                         peth0
                                                         vif1.0

     --------------------------------------------------------------

  21.2.3. Windows CURW-a-o Virtual PC

   Virtual PC NOTO Microsoft -a-o Windows
   ^3nAAe^2-L-<<~!AYENiYENHS:KP:OCURU,u:"IYENI!C NOTUAo:"t^2I>>Y"D!A
   1/2D-DEGN 3/4\   system requirements >>!(c)u!C |b
   Microsoft Windows ,ES:^1 Virtual PC CURS:<<a!A
   YEN^2P:.DEGw^1i(c)O+-y|w,E-a-oueAA 3/4-:
   3/4^1"OS:@NOTUAo:^3](c)w!C

     --------------------------------------------------------------

    21.2.3.1. |b Virtual PC/Microsoft(R) Windows CURW|w,E FreeBSD

   |b Microsoft Windows/Virtual PC CURW|w,E FreeBSD
   -a-o^2A:CUR@"BNOTO.s 1/4WueAA 3/4-: 3/4^1!C |pCURU(c)OYENU:!A
   |b'-L-YENU:uo/u!CUR-o 1/2D-?i 3/4U: Create a virtual machine!G

   uM<<a|b Operating system ^3B?i Other!G

   "A"I 3/4U|U">>Y"D"O^3W^1-ouw-oD-(R)eP:q,oDEGO
   3/4D-AAe-a-oCURADEGt!C ^1iCURj|h 1/4AE|b Virtual PC "IYENI FreeBSD
   -a-o+-!-ap|O"YEN!ACURjNOTu 4GB uw-oD--aAAP:!YENHCURI 512MB RAM
   'NDEG-:YENICURF!G

   Ax|s^3](c)wAE!G

   +-uCURU"O?iee(c)O.s 1/4W-a-o FreeBSD ueAA 3/4-: 3/4^1!A"A<<o:CURU
   Settings!AYENH^3](c)w-oo,o-oO/AthYENHCURI-oo,oYENd!G

   |b FreeBSD ueAA 3/4-: 3/4^1.s 1/4W<<a!A'NYENiYENHA:~A:oYENH"a:|w,E
   FreeBSD!C |w,ECURe+-!ACURn,u|n-a-oS:@-akNOTO"IYENI(c)xCURe-a-o
   FreeBSD YENu-oD-(c)I-aI+-q(c)xCURe FTP -,CURU,u: ISO image AE!C
   Y+-z-a-o Windows AE(R) *"t^2ICUR-oCURw,g|^3,O ISO AE!A
   (c)I-aIYENu-oD- 3/4-:CUR-o|^3(c)n|w,ECURu!A"-o>>o'NYENiYENH|b
   FreeBSD ueAA 3/4-: 3/4^1CURW^3s<<o:"aCURU!AYENHP:}(c)l+-ODEGE!C
   +-uuU|b Virtual PC uo/u!CUR-o<<o: CD |A<<o: Capture ISO Image...
   !C +-uuU.|YENX^2{CUR@Ouo/u!!AYENiYENHS:aueAA 3/4-:
   3/4^1CUR-o-a-oYENu-oD- 3/4-:^3](c)w"`i,O ISO AE!A
   (c)I-aINOTO^1eAAeYENu-oD- 3/4-:!C

   ^3]|nYENu-oD-CURu"O. 1/2CURS:<<a!A'NYENiYENH<<P:}
   3/4-:!ACUR]'NNOTOYENy<<o: Action |A<<o: Reset S:YYENi!C Virtual PC
   .|YENH-S(R)i BIOS P:} 3/4-:!A"A>>P'P:^3q BIOS CUR@
   1/4E.|YENyAENOTdNOTOS:_|^3YENu-oD- 3/4-:!C

   |^1(R)E!AYEN|'N.|S:a:"`i FreeBSD |w,ECURu!A"AP:}(c)l|b uU 2 ^3^1
   CUR-o(c)OCURP:^2D-"`i-a-o sysinstall |w,E^1Lu{!C
   ^3o(R)EOCUR]YENiP:P:<<K,E X11!A|yYENyCUR-L-nP:i|aeNOTUAo:^3](c)w!C

   S:^1|"|w,ECURS:<<a!ADEGO+-oS:aYENu-oD-CURuDEGhYENX(c)I-aI ISO
   image DEGhCURu!C ^3I<<a!A S:a,E|n-a-o FreeBSD ueAA 3/4-:
   3/4^1<<P:} 3/4-:S:YYENi!C

     --------------------------------------------------------------

    21.2.3.2.  1/2O 3/4a Microsoft Windows/Virtual PC CURW-a-o FreeBSD

   |b Microsoft Windows CURWYENH Virtual PC ,E|n FreeBSD
   <<a!AAU>>YnS:@CUR@"C,^3](c)w"BAEJ!A YENH<<K+-NueAA 3/4-:
   3/4^1CUR-o-a-o FreeBSD ^3I"ICURAE!C

    1. ^3](c)w boot loader DEGN 1/4AE

       ^3I<<n-a-o"BAEJCURDNOTOAC,YENN 1/2ODEG kern.hz "ODEGS:C
       Virtual PC Ao^1OCUR-o FreeBSD -a-o CPU |uYENI^2v!C YENiYENH|b
       /boot/loader.conf CUR-oYEN[CURWCURU|C^3](c)wS:YYENi!G

 kern.hz=100

       YCUR-L-S:@^3o^3](c)w!A"-o>>oYENuNOTO idle -aNOT-oA-a-o FreeBSD
       Virtual PC guest OS 'N.||bP:E^3aeCUR@^3B^2z
       3/4^1-a-o^1q,-L-CURW|uCURFCURjNOTu 40% -a-o CPU |uYENI^2v!C
       S:@CURWz *S:iCURS:<<a!A|uYENI^2v'N.|DEG|U:CURjNOTu 3%!C

    2. ^3](c)w.s-a-o kernel ^3](c)wAE

       YENiYENH(c)nCURssS:a(c)O|^3 SCSI!BFireWire!BUSB
       NOTUAo:^3]^3AE^3-L-^2 3/4DEG-L-!C Virtual PC |^3'-L-"N de(4)
       -a-oueAA-ooYENd!A|]|^1DEG-L-CURF de(4) YENHCURI miibus(4)
       YENHYEN~-a-o"a:YENL-oo,oYENdCUR]^3-L-YENiYENH+-q kernel
       CURCUR^2 3/4DEG-L-!C

    3. ^3](c)w-oo,o

       YENiYENH'AueAA 3/4-: 3/4^1A^2^3aeYENI DHCP "O^3](c)w>>P
       host(Microsoft Windows) NOTU|P-a-o LAN -oo,oAo^1O!AYENun|b
       /etc/rc.conf YEN[CURW ifconfig_de0="DHCP" S:YYENiS:^1|"!C
       "a:YENLP:iP:YEN-a-o-oo,o^3](c)wCURe|!!A 1/2D-DEGN 3/4\ uU 29
       ^3^1!C

     --------------------------------------------------------------

  21.2.4. |b MacOS CURW-a-o VMware

   Mac CURW-a-o VMWare Fusion CURDNOTOYENiYENI(c)o.fDEGt Intel CPU
   YENHCURI Mac OS 10.4.9 CURS: Apple Mac YENHCURW-a-o Apple Mac
   ^1q,-L-CURS:DEGO.~^3nAAe!C FreeBSD NOTO"a:|^3S:^1
   3/4aCURa:'(c)-a-o guest OS CURS:CUR@!C |b Mac OS X CURW,ES:^1
   VMWare Fusion CURS:<<a!A YEN^2P:.DEGw^1i(c)O+-y|w,E-a-o guest OS
   "OS:@NOTUAo:-a-oueAA 3/4-: 3/4^1^3](c)w!C

     --------------------------------------------------------------

    21.2.4.1. |b VMWare/Mac OS X CURW|w,E FreeBSD

   -oYENyDEGo|ae VMWare Fusion!A|O"a: Virtual Machine Library
   CUR].|AHCURS:CUR@"O:,u:CURJ!A^3o(R)E 1/2D-<<o: "New" "O<<O/YENss
   VM(ueAA 3/4-: 3/4^1)!G

   +-uuU.||^3 New Virtual Machine Assistant "O"oS:U+-z<<O/YENss VM!A
   1/2D-<<o: Continue A:~A:o!G

   |b Operating System ?i Other!AYENHCURI Version ^3B 1/2D-?i
   3/4U:NOTOS:_n FreeBSD (c)I FreeBSD 64-bit!A^3o^3!YEN-:
   1/2D-"I|U">>Y"DNOTOS:_|^3n 64-bit CURa:'(c)|O(c)w!G

   +-uuU^3](c)w VM image AEn|s"`i|o^3B!AYENHCURI"M(c)w|W-oU!G

   "M(c)w,O VM -a-oueAAuw-oD-nYENI|hCURj!G

   ?i 3/4U:n,E VM -a-oCURe|!NOTDEG|o!AnYENI ISO image
   AE(c)I-aIYENu-oD- 3/4-:!G

   <<o: Finish YENHS:^1^2|!A+-uuU'N.|+-ODEGE,O VM!G

   +-uuU'N.OYENH(c)^1|w,E FreeBSD -a-oCURe|!"O,E!AYCUR-L- 1/4o-a-o,U:
   1/2D-DEGN 3/4\ uU 2 ^3^1!G

   ,ES:^1CURS:<<a!A'NYENiYENH *S:iCUR@"C, VM ^3](c)w!A^1^3NOTODEGO
   3/4D-AAeCURjCURp!G

     -a`: VM |b^1BS:@CURS:(R)E!ACUR-L--`a *S:i VM -a-ouwAAe^3](c)w!C

   1/2O 3/4a VM -a-o CPU  1/4AEP:q!G

   YENu-oD-
   3/4-:-aNOT-oA!A^3q+-`CUR-L-|A>>YnYENI-a-o(R)EO!A'NYENiYENHCURAA_"a:>>P
   VM -a-o^3s+-u!G

   ^3I<<anS:i-a-o<<hNOTO VM -a-o-oo,o^3](c)w!C YDEG-L-CURF Host OS
   CURS:YEN~-a-o 3/4-: 3/4^1CUR]-`a^3s"`i VM!A"-o>>o 1/2D-?i Connect
   directly to the physical network (Bridged)!AS:_<<h'N?i Share the
   host's internet connection (NAT) S:YYENiAAy VM ^3s"`i Internet!A
   |yYEN~+-<<huL-ak^3sCURJ,O VM!C

   S:iS:^1CURWz^3](c)wCURS:<<a!A'NYENiYENH+-ODEGE.s,ES:'-a-o FreeBSD
   ueAA 3/4-: 3/4^1!C

     --------------------------------------------------------------

    21.2.4.2.  1/2O 3/4a Mac OS X/VMWare CURW-a-o FreeBSD

   S:a FreeBSD |"YEN\,E"`i Mac OS X -a-o VMWare
   CURS:<<a!AAU>>YnS:@CUR@"C,^3](c)w"BAEJ!A YENH<<K+-NueAA 3/4-:
   3/4^1CUR-o-a-o FreeBSD ^3I"ICURAE!C

    1. ^3](c)w boot loader DEGN 1/4AE

       ^3I<<n-a-o"BAEJCURDNOTOAC,YENN 1/2ODEG kern.hz "ODEGS:C VMWare
       Ao^1OCUR-o FreeBSD -a-o CPU |uYENI^2v!C YENiYENH|b
       /boot/loader.conf CUR-oYEN[CURWCURU|C^3](c)wS:YYENi!G

 kern.hz=100

       YCUR-L-S:@^3o^3](c)w!A"-o>>oYENuNOTO idle -aNOT-oA-a-o FreeBSD
       (VMWare guest OS) 'N.||bP:E^3aeCUR@^3B^2z 3/4^1-a-o iMac
       CURW|uCURFCURjNOTu 15% -a-o CPU |uYENI^2v!C S:@CURWz
       *S:iCURS:<<a!A |uYENI^2v'N.|DEG|U:CURjNOTu 5%!C

    2. ^3](c)w.s-a-o kernel ^3](c)wAE

       YENiYENH(c)nCURssS:a(c)O|^3 FireWire!BUSB
       NOTUAo:^3]^3AE^3-L-^2 3/4DEG-L-!C VMWare |^3'-L-"N em(4)
       -a-oueAA-ooYENd!A |]|^1!ADEG-L-CURF em(4) YENHCURI miibus(4)
       YENHYEN~-a-o"a:YENL-oo,oYENd!A CUR]^3-L-YENiYENH+-q kernel
       CURCUR^2 3/4DEG-L-!C

    3. ^3](c)w-oo,o

       YENiYENH'AueAA 3/4-: 3/4^1A^2^3aeYENI DHCP "O^3](c)w>>P host
       Mac NOTU|P-a-o LAN -oo,oAo^1O!AYENun|b /etc/rc.conf YEN[CURW
       ifconfig_em0="DHCP" S:YYENi!C
       "a:YENLP:iP:YEN-a-o-oo,o^3](c)wCURe|!!A 1/2D-DEGN|O uU 29
       ^3^1!C

     --------------------------------------------------------------

21.3. YENH FreeBSD NOTDEG Host OS

   YENO/<<e!A(c)|YEN 1/4|^3YENo|oueAA 3/4-:
   3/4^1^3nAAe|^3(c)xCUReCURa:'(c) FreeBSD S:@NOTDEG host OS!A
   |yAEZ|hCURH^3-L-|^3|bYENIAA-a(c) VMware
   (c)O'-L-"N-a-o^3oP:uYEN\-`a!C
   CUR-L-^1L!AYENO/<<eCURw,g|^3CURHNOTDEGAAy Xen -`aDEG-:YENH FreeBSD
   NOTDEG host OS NOTDEGYENO/ 1/4D-!A|OP:i|aeNOTUAo:CURuS:@!C

     --------------------------------------------------------------

          ^3^1 22. >>y"t^3](c)w - I18N/L10N YENI-ak>>P^3](c)w

   Contributed by Andrey Chernov. Rewritten by Michael C. Wu.

22.1. .S:z

   YENN(c)o FreeBSD
   NOTOCURAS:GYENthYEN@NOTE-a-o"IYENI-aICURIS:OCURu(c)OCURa:<<u-a-opue!AYEN>>^3^1YENDn+-'DEGQ-a-oNOTO
   FreeBSD
   -a-oDEGe>>UCURAE!BYEN>>CURgCURAEA:^3AD!AYENH<<KAAyYENA>>yCUR-L-NOTO^>>y"t-a-oCURHCUR]-`aP:P:S:QS:^1|"|UP:uCURuS:@!C
   |bS:@.~"t^2I!BA^3YENIu{|!"a-oO/ 1/4h+-!AYENDn^3-L-NOTO^3z^1L i18n 
   1/4D-.C,"O^1eS:@-a-o!A(c)OYENH!A
   ^3o,IS:UI+-N.|CURP:^2D-CURjP^1BS:@CURe|!!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!J

     * |U-oO/CUR-L-|P-a-o>>y"YEN>>P|aDEGI^3](c)w|p|o|bS:@.~"t^2ICURWP:i|ae
       1/2s 1/2X!C

     * |p|o^3](c)wunCURJYENI-a-o shell >>y"tAo^1O!C

     * |p|o+-NS:A-a-o console ^3]NOTDEG^>>yYENHYEN~-a-o>>y"t^3](c)w!C

     * |p|o"IYENICUR-L-|P>>y"t-a-o^3](c)w!A"OAAy X Window
       ^1BS:@S:o?ECURA!C

     * thAa:YENiYENHS:a:"`iS:o|h>>P i18n
       ^3W(R)aeNOTU(R)e-a-oA^3YENIu{|!^3W(R)ae,e(R)AE!C

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!J

     * -a 3/4^1D|p|oYENH ports/packages "O|w,EA^3YENIu{|!(uU 4
       ^3^1)!C

     --------------------------------------------------------------

22.2. L10N DEGoA|.S:(c)A

  22.2.1. CURDEG>>oNOTO I18N/L10N?

   u{|!P:}uoCURHu^2ss-oDS:a internationalization AY 1/4gNOTDEG
   I18N!ACURCURP:!-a-o 1/4AE|r 18
   CURDNOTO^3I<<e>>P^3I<<a+-|rYENACURS:P:!-a-o|rYENAO 1/4AEA`(c)M!A
   |O L10N CUR]NOTOYENHCUR@ 1/4E-a-oCURe|!!ANOTO !S:localization!"
   -a-oAY 1/4g!C YENun|^3^2AA|X I18N/L10N
   ^3W(R)ae!B"o(c)w-a-oA^3YENIu{|!!A'NYENiYENHAAy"IYENI-aI"I|U|U>>y"t|OS:@^3](c)w!C

   I18N A^3YENIu{|!NOTOYENH I18N P:}uoCURu"a"OP:i|aeP:}uo-a-o!A
   YEN|YENiYENHAAyu{|!P:}uoCURHu^3z^1L
   1/4gA^2^3ae-a-oCURaa|rAE!A'NYENiYENHS:aDEGo|aeue+-CURW-a-o?i^3ae!BDEGT(R)S:A
   1/2A:P:NOTDEG|U>>y"t-a-o-a(c)YEN>>!C
   S:UI+-j-P<<O/A:^3u{|!P:}uoCURHu?i'`^3oO^1CA,^3W<<h!C

     --------------------------------------------------------------

  22.2.2. NOTDEG|o,O"IYENI I18N/L10N!H

   YENun|^3^2AA|X I18N/L10N 
   1/4D-.C,!A'NYENiYENH>>'AP|aNOTY!B?eCURJ!B^3B^2z<<D^CURaa-a-o,e(R)AE!C

     --------------------------------------------------------------

  22.2.3. I18N CURa:'(c)th"C,>>y"t!H

   I18N (c)M L10N "A<<D FreeBSD
   (c)O-S|^3-a-o!AYENO/<<e^3oYEN@NOTECURW-a-o'XYENGYENoCUR@YENDn>>y"t^3-L-|^3CURa:'(c)!A
   ^1^3NOTO!GCURCURCURaa!B
   1/4wCURaa!BCUReCURaa!BAuCURaa!B-akCURaa!B<<XCURaa!BP:V<<nCURaauYENuYEN!C

     --------------------------------------------------------------

22.3. "IYENI>>y"t^3](c)w(Localization)

   I18N (c)M L10N "A<<D FreeBSD
   (c)O-S|^3-a-o!A|ONOTO|@^3q-a-o^1CA,^3W<<h!C S:UI^1-aAyS:A|b
   FreeBSD YEN@NOTECURCUR|P 1/4E?i|u^3oP:u^1CA,^3W<<h!C

   Locale ^3](c)wYENNCURTO^3!CURA(c)O^2O|"!G>>y"YENYENN 1/2X(Language
   Code)!BDEGe 1/2X(Country Code)!B 1/2s 1/2X(Encoding)!C
   (c)OYENH!ALocale -a-o^3](c)w|W-oU'NNOTOYENN^3oCURTOCUR@DEG_^2O|"!G

 >>y"YENYENN 1/2X_DEGe 1/2X. 1/2s 1/2X

     --------------------------------------------------------------

  22.3.1. >>y"YEN!BDEGe 1/2X

   "IYENI-aIYEN^2P:.nYENy-a 3/4^1D^3o"C,-S(c)w-a-oDEGe
   1/2X!B>>y"YENYENN 1/2X(DEGe
   1/2X.|S:iP:DA^3YENIu{|!,O"IYENIthCUR@-oO/>>y"YEN)!A CUR~-`aAAy
   FreeBSD (c)I"a:YENLCURa:'(c) I18N -a-o UNIX Ath"t^2IS:@ locale
   NOTUAo:^3](c)w!C |^1YEN~!A-ooP:AsA:y 3/4^1(borwser)!BSMTP/POP YEND
   3/4-:!BWeb YEND 3/4-:uYENCUR]^3-L-YENH^3oNOT[-ocNOTDEGYEND!C
   CURU+-NOTO|p|o"IYENI!y>>y"YENYENN 1/2X!BDEGe 1/2X!z-a-o"OCURl!G

      >>y"YENYENN 1/2X/DEGe 1/2X                A^2CURP:              
   en_US                            ^CURaa(NOTu:DEGe)                 
   ru_RU                            <<XCURaa(<<XDEGe)                 
   zh_TW                            YEN?AAeCURCURCURaa(YENxAEW)       

     --------------------------------------------------------------

  22.3.2.  1/2s 1/2X

   |^3"C,>>y"YEN"A<<D+-A:YENI ASCII  1/2s 1/2X!AYENi-`aNOTO!G
   8-bit!Bwide (c)I multibyte |rCUR,!A,O+-! 1/2D-DEGN 3/4\
   multibyte(3)!C ,uYENj|-a-ou{|!YENi-`auL-akYEN?
   1/2TS:PS:O!B(c)I>>~S:PNOTDEG-S(R)i+-+-"i|rCUR,!C|O,u.s-a-ou{|!^3-L-YENiYENH?e>>{
   8-bit |rCUR,!C
   YENN(c)o|Uu{|!-a-oS:@-akCUR-L-CUR@!A"IYENI-aIYENi-`a>>Yn|b
   1/2sA:P:u{|!(R)E!AYEN[CURW wide (c)I multibyte
   |rCUR,-a-oCURa:'(c)^3](c)w!A(c)INOTOYEN? 1/2T 1/2O 3/4aCUR~|ae!C
   n?eCURJ!B^3B^2z wide (c)I multibyte |rCUR,-a-o,U:!AYENi|h|hS:QYENI
   FreeBSD Ports Collection CUR-o|^3|UDEGe>>y"YEN-a(c)YEN>>-a-ou{|!!C
   ,O+-! 1/2D-DEGN 3/4\ FreeBSD |U port CURCUR-a-o I18N
   NOTUAo:CURaaYENo!C

   Specifically, the user needs to look at the application
   documentation to decide on how to configure it correctly or to
   pass correct values into the configure/Makefile/compiler.

   Some things to keep in mind are:

     * Language specific single C chars character sets (see
       multibyte(3)), e.g. ISO8859-1, ISO8859-15, KOI8-R, CP437.

     * Wide or multibyte encodings, e.g. EUC, Big5.

   You can check the active list of character sets at the IANA
   Registry.

     -a`: FreeBSD use X11-compatible locale encodings instead.

     --------------------------------------------------------------

  22.3.3. I18N Applications

   In the FreeBSD Ports and Package system, I18N applications have
   been named with I18N in their names for easy identification.
   However, they do not always support the language needed.

     --------------------------------------------------------------

  22.3.4. Setting Locale

   Usually it is sufficient to export the value of the locale name as
   LANG in the login shell. This could be done in the user's
   ~/.login_conf file or in the startup file of the user's shell
   (~/.profile, ~/.bashrc, ~/.cshrc). There is no need to set the
   locale subsets such as LC_CTYPE, LC_CTIME. Please refer to
   language-specific FreeBSD documentation for more information.

   You should set the following two environment variables in your
   configuration files:

     * LANG for POSIX setlocale(3) family functions

     * MM_CHARSET for applications' MIME character set

   This includes the user shell configuration, the specific
   application configuration, and the X11 configuration.

     --------------------------------------------------------------

    22.3.4.1. Setting Locale Methods

   There are two methods for setting locale, and both are described
   below. The first (recommended one) is by assigning the environment
   variables in login class, and the second is by adding the
   environment variable assignments to the system's shell startup
   file.

     --------------------------------------------------------------

      22.3.4.1.1. Login Classes Method

   This method allows environment variables needed for locale name
   and MIME character sets to be assigned once for every possible
   shell instead of adding specific shell assignments to each shell's
   startup file. User Level Setup can be done by an user himself and
   Administrator Level Setup require superuser privileges.

     --------------------------------------------------------------

        22.3.4.1.1.1. User Level Setup

   Here is a minimal example of a .login_conf file in user's home
   directory which has both variables set for Latin-1 encoding:

 me:\
         :charset=ISO-8859-1:\
         :lang=de_DE.ISO8859-1:

   Here is an example of a .login_conf that sets the variables for
   Traditional Chinese in BIG-5 encoding. Notice the many more
   variables set because some software does not respect locale
   variables correctly for Chinese, Japanese, and Korean.

 #Users who do not wish to use monetary units or time formats
 #of Taiwan can manually change each variable
 me:\
         :lang=zh_TW.Big5:\
         :lc_all=zh_TW.Big:\
         :lc_collate=zh_TW.Big5:\
         :lc_ctype=zh_TW.Big5:\
         :lc_messages=zh_TW.Big5:\
         :lc_monetary=zh_TW.Big5:\
         :lc_numeric=zh_TW.Big5:\
         :lc_time=zh_TW.Big5:\
         :charset=big5:\
         :xmodifiers="@im=xcin": #Setting the XIM Input Server

   See Administrator Level Setup and login.conf(5) for more details.

     --------------------------------------------------------------

        22.3.4.1.1.2. Administrator Level Setup

   Verify that the user's login class in /etc/login.conf sets the
   correct language. Make sure these settings appear in
   /etc/login.conf:

 language_name:accounts_title:\
         :charset=MIME_charset:\
         :lang=locale_name:\
         :tc=default:

   So sticking with our previous example using Latin-1, it would look
   like this:

 german:German Users Accounts:\
         :charset=ISO-8859-1:\
         :lang=de_DE.ISO8859-1:\
         :tc=default:

   Before changing users Login Classes execute the following command

 # cap_mkdb /etc/login.conf

   to make new configuration in /etc/login.conf visible to the
   system.

      Changing Login Classes with vipw(8)

   Use vipw to add new users, and make the entry look like this:

 user:password:1111:11:language:0:0:User Name:/home/user:/bin/sh

      Changing Login Classes with adduser(8)

   Use adduser to add new users, and do the following:

     * Set defaultclass = language in /etc/adduser.conf. Keep in mind
       you must enter a default class for all users of other
       languages in this case.

     * An alternative variant is answering the specified language
       each time that

 Enter login class: default []:

       appears from adduser(8).

     * Another alternative is to use the following for each user of a
       different language that you wish to add:

 # adduser -class language

      Changing Login Classes with pw(8)

   If you use pw(8) for adding new users, call it in this form:

 # pw useradd user_name -L language

     --------------------------------------------------------------

      22.3.4.1.2. Shell Startup File Method

     -a`: This method is not recommended because it requires a
     different setup for each possible shell program chosen. Use the
     Login Class Method instead.

   To add the locale name and MIME character set, just set the two
   environment variables shown below in the /etc/profile and/or
   /etc/csh.login shell startup files. We will use the German
   language as an example below:

   In /etc/profile:

 LANG=de_DE.ISO8859-1; export LANG
 MM_CHARSET=ISO-8859-1; export MM_CHARSET

   Or in /etc/csh.login:

 setenv LANG de_DE.ISO8859-1
 setenv MM_CHARSET ISO-8859-1

   Alternatively, you can add the above instructions to
   /usr/share/skel/dot.profile (similar to what was used in
   /etc/profile above), or /usr/share/skel/dot.login (similar to what
   was used in /etc/csh.login above).

   For X11:

   In $HOME/.xinitrc:

 LANG=de_DE.ISO8859-1; export LANG

   Or:

 setenv LANG de_DE.ISO8859-1

   Depending on your shell (see above).

     --------------------------------------------------------------

  22.3.5. Console Setup

   For all single C chars character sets, set the correct console
   fonts in /etc/rc.conf for the language in question with:

 font8x16=font_name
 font8x14=font_name
 font8x8=font_name

   The font_name here is taken from the /usr/share/syscons/fonts
   directory, without the .fnt suffix.

   Also be sure to set the correct keymap and screenmap for your
   single C chars character set through sysinstall (/stand/sysinstall
   in FreeBSD versions older than 5.2). Once inside sysinstall,
   choose Configure, then Console. Alternatively, you can add the
   following to /etc/rc.conf:

 scrnmap=screenmap_name
 keymap=keymap_name
 keychange="fkey_number sequence"

   The screenmap_name here is taken from the
   /usr/share/syscons/scrnmaps directory, without the .scm suffix. A
   screenmap with a corresponding mapped font is usually needed as a
   workaround for expanding bit 8 to bit 9 on a VGA adapter's font
   character matrix in pseudographics area, i.e., to move letters out
   of that area if screen font uses a bit 8 column.

   If you have the moused daemon enabled by setting the following in
   your /etc/rc.conf:

 moused_enable="YES"

   then examine the mouse cursor information in the next paragraph.

   By default the mouse cursor of the syscons(4) driver occupies the
   0xd0-0xd3 range in the character set. If your language uses this
   range, you need to move the cursor's range outside of it. To
   enable the workaround for FreeBSD, add the following line to
   /etc/rc.conf:

 mousechar_start=3

   The keymap_name here is taken from the /usr/share/syscons/keymaps
   directory, without the .kbd suffix. If you are uncertain which
   keymap to use, you use can kbdmap(1) to test keymaps without
   rebooting.

   The keychange is usually needed to program function keys to match
   the selected terminal type because function key sequences cannot
   be defined in the key map.

   Also be sure to set the correct console terminal type in /etc/ttys
   for all ttyv* entries. Current pre-defined correspondences are:

               Character Set                     Terminal Type        
   ISO8859-1 or ISO8859-15                cons25l1                    
   ISO8859-2                              cons25l2                    
   ISO8859-7                              cons25l7                    
   KOI8-R                                 cons25r                     
   KOI8-U                                 cons25u                     
   CP437 (VGA default)                    cons25                      
   US-ASCII                               cons25w                     

   For wide or multibyte characters languages, use the correct
   FreeBSD port in your /usr/ports/language directory. Some ports
   appear as console while the system sees it as serial vtty's, hence
   you must reserve enough vtty's for both X11 and the pseudo-serial
   console. Here is a partial list of applications for using other
   languages in console:

           Language                          Location                 
   Traditional Chinese       chinese/big5con                          
   (BIG-5)                   
   Japanese                  japanese/kon2-16dot or                   
                             japanese/mule-freewnn                    
   Korean                    korean/han                               

     --------------------------------------------------------------

  22.3.6. X11 Setup

   Although X11 is not part of the FreeBSD Project, we have included
   some information here for FreeBSD users. For more details, refer
   to the Xorg web site or whichever X11 Server you use.

   In ~/.Xresources, you can additionally tune application specific
   I18N settings (e.g., fonts, menus, etc.).

     --------------------------------------------------------------

    22.3.6.1. Displaying Fonts

   Install Xorg server (x11-servers/xorg-server) or XFree86 server
   (x11-servers/XFree86-4-Server), then install the language TrueType
   fonts. Setting the correct locale should allow you to view your
   selected language in menus and such.

     --------------------------------------------------------------

    22.3.6.2. Inputting Non-English Characters

   The X11 Input Method (XIM) Protocol is a new standard for all X11
   clients. All X11 applications should be written as XIM clients
   that take input from XIM Input servers. There are several XIM
   servers available for different languages.

     --------------------------------------------------------------

  22.3.7. Printer Setup

   Some single C chars character sets are usually hardware coded into
   printers. Wide or multibyte character sets require special setup
   and we recommend using apsfilter. You may also convert the
   document to PostScript or PDF formats using language specific
   converters.

     --------------------------------------------------------------

  22.3.8. Kernel and File Systems

   The FreeBSD fast filesystem (FFS) is 8-bit clean, so it can be
   used with any single C chars character set (see multibyte(3)), but
   there is no character set name stored in the filesystem; i.e., it
   is raw 8-bit and does not know anything about encoding order.
   Officially, FFS does not support any form of wide or multibyte
   character sets yet. However, some wide or multibyte character sets
   have independent patches for FFS enabling such support. They are
   only temporary unportable solutions or hacks and we have decided
   to not include them in the source tree. Refer to respective
   languages' web sites for more information and the patch files.

   The FreeBSD MS-DOS filesystem has the configurable ability to
   convert between MS-DOS, Unicode character sets and chosen FreeBSD
   filesystem character sets. See mount_msdos(8) for details.

     --------------------------------------------------------------

22.4. Compiling I18N Programs

   Many FreeBSD Ports have been ported with I18N support. Some of
   them are marked with -I18N in the port name. These and many other
   programs have built in support for I18N and need no special
   consideration.

   However, some applications such as MySQL need to be have the
   Makefile configured with the specific charset. This is usually
   done in the Makefile or done by passing a value to configure in
   the source.

     --------------------------------------------------------------

22.5. Localizing FreeBSD to Specific Languages

  22.5.1. Russian Language (KOI8-R Encoding)

   Originally contributed by Andrey Chernov.

   For more information about KOI8-R encoding, see the KOI8-R
   References (Russian Net Character Set).

     --------------------------------------------------------------

    22.5.1.1. Locale Setup

   Put the following lines into your ~/.login_conf file:

 me:My Account:\
         :charset=KOI8-R:\
         :lang=ru_RU.KOI8-R:

   See earlier in this chapter for examples of setting up the locale.

     --------------------------------------------------------------

    22.5.1.2. Console Setup

     * Add the following line to your /etc/rc.conf file:

 mousechar_start=3

     * Also, use following settings in /etc/rc.conf:

 keymap="ru.koi8-r"
 scrnmap="koi8-r2cp866"
 font8x16="cp866b-8x16"
 font8x14="cp866-8x14"
 font8x8="cp866-8x8"

     * For each ttyv* entry in /etc/ttys, use cons25r as the terminal
       type.

   See earlier in this chapter for examples of setting up the
   console.

     --------------------------------------------------------------

    22.5.1.3. Printer Setup

   Since most printers with Russian characters come with hardware
   code page CP866, a special output filter is needed to convert from
   KOI8-R to CP866. Such a filter is installed by default as
   /usr/libexec/lpr/ru/koi2alt. A Russian printer /etc/printcap entry
   should look like:

 lp|Russian local line printer:\
         :sh:of=/usr/libexec/lpr/ru/koi2alt:\
         :lp=/dev/lpt0:sd=/var/spool/output/lpd:lf=/var/log/lpd-errs:

   See printcap(5) for a detailed description.

     --------------------------------------------------------------

    22.5.1.4. MS-DOS FS and Russian Filenames

   The following example fstab(5) entry enables support for Russian
   filenames in mounted MS-DOS filesystems:

 /dev/ad0s2      /dos/c  msdos   rw,-Wkoi2dos,-Lru_RU.KOI8-R 0 0

   The option -L selects the locale name used, and -W sets the
   character conversion table. To use the -W option, be sure to mount
   /usr before the MS-DOS partition because the conversion tables are
   located in /usr/libdata/msdosfs. For more information, see the
   mount_msdos(8) manual page.

     --------------------------------------------------------------

    22.5.1.5. X11 Setup

    1. Do non-X locale setup first as described.

    2. If you use Xorg, install x11-fonts/xorg-fonts-cyrillic
       package.

       Check the "Files" section in your /etc/X11/xorg.conf file. The
       following lines must be added before any other FontPath
       entries:

 FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/misc"
 FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/75dpi"
 FontPath   "/usr/X11R6/lib/X11/fonts/cyrillic/100dpi"

       If you use a high resolution video mode, swap the 75 dpi and
       100 dpi lines.

    3. To activate a Russian keyboard, add the following to the
       "Keyboard" section of your xorg.conf file.

 Option "XkbLayout"   "us,ru"
 Option "XkbOptions"  "grp:toggle"

       Also make sure that XkbDisable is turned off (commented out)
       there.

       For grp:caps_toggle the RUS/LAT switch will be CapsLock. The
       old CapsLock function is still available via Shift+CapsLock
       (in LAT mode only). For grp:toggle the RUS/LAT switch will be
       Right Alt. grp:caps_toggle does not work in Xorg for unknown
       reason.

       If you have !S:Windows!" keys on your keyboard, and notice
       that some non-alphabetical keys are mapped incorrectly in RUS
       mode, add the following line in your xorg.conf file.

 Option "XkbVariant" ",winkeys"

         -a`: The Russian XKB keyboard may not work with
         non-localized applications.

     -a`: Minimally localized applications should call a
     XtSetLanguageProc (NULL, NULL, NULL); function early in the
     program.

     See   KOI8-R for X Window for more instructions on localizing
     X11 applications.

     --------------------------------------------------------------

  22.5.2. Traditional Chinese Localization for Taiwan

   The FreeBSD-Taiwan Project has an Chinese HOWTO for FreeBSD at
   http://netlab.cse.yzu.edu.tw/~statue/freebsd/zh-tut/ using many
   Chinese ports. Current editor for the FreeBSD Chinese HOWTO is
   Shen Chuan-Hsing <statue@freebsd.sinica.edu.tw>.

   Chuan-Hsing Shen <statue@freebsd.sinica.edu.tw> has created the  
   Chinese FreeBSD Collection (CFC) using FreeBSD-Taiwan's
   zh-L10N-tut. The packages and the script files are available at
   ftp://freebsd.csie.nctu.edu.tw/pub/taiwan/CFC/.

     --------------------------------------------------------------

  22.5.3. German Language Localization (for All ISO 8859-1 Languages)

   Slaven Rezic <eserte@cs.tu-berlin.de> wrote a tutorial how to use
   umlauts on a FreeBSD machine. The tutorial is written in German
   and available at http://www.de.FreeBSD.org/de/umlaute/.

     --------------------------------------------------------------

  22.5.4. Japanese and Korean Language Localization

   For Japanese, refer to http://www.jp.FreeBSD.org/, and for Korean,
   refer to http://www.kr.FreeBSD.org/.

     --------------------------------------------------------------

  22.5.5. Non-English FreeBSD Documentation

   Some FreeBSD contributors have translated parts of FreeBSD to
   other languages. They are available through links on the main site
   or in /usr/share/doc.

     --------------------------------------------------------------

                    ^3^1 23. S:o.s!BCURE-AA FreeBSD

   Restructured, reorganized, and parts updated by Jim Mock. Original
   work by Jordan Hubbard, Poul-Henning Kamp, John Polstra, YENB Nik
   Clayton.

23.1. .S:z

   FreeBSD
   NOTOO<<uA:ouo(R)i-a-oS:@.~"t^2I!C^1i(c)o^3ssAAwDEGl"D.sAA!B"e?E-a-o"IYENI-aI|O"YEN!A
   |^3<<U:|hCURe-akYENiYENH"I+-z-a-o"t^2I>>'APS:o.sNOTDEG^3I.s-a(c)!C
   -a`.N!G"A<<D"COCURH^3-L-
   3/4A|X^3o>>oDEGu!I!@YEN>>^3^1YENDnNOTO"oS:U+-z"M(c)w"`i(c)^3n,oP:}uo-a(c)YEN>>!A
   (c)INOTOn"IYENI,uA(c)w-a-oA:AYENX-a(c)!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!J

     * FreeBSD-STABLE >>P
       FreeBSD-CURRENT!@^3o"aCURACURa:-a-oCUR-L-|PCURS:^3B!F

     * |p|oYENH CSup, CVSup, CVS (c)I CTM "OS:o.sS:A-a-o"t^2I

     * |p|oYENH make buildworld uYEN<<u:YENO"O<<.s 1/2sA:P:!B|w,E
       3/4aO base system!C

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!J

     * YENy^3]|nS:A-a-o-oo,o(uU 29 ^3^1)!C

     * -a 3/4^1D|p|o^3z^1L port/package |w,E^3nAAe(uU 4 ^3^1)!C

     --------------------------------------------------------------

23.2. FreeBSD-CURRENT vs. FreeBSD-STABLE

   FreeBSD |^3"aOuo(R)iCURACURa:!GFreeBSD-CURRENT CURI
   FreeBSD-STABLE!CYEN>>,`+-N.|^3DEGA:oCURP:^2D-!A"ACURP:^2D-YEN|ICURAS:OCURSNOTO|p|oS:o.s!C
   -oYENy!AYENyCURP:^2D- FreeBSD-CURRENT!A+-uuU|ACURP:^2D-
   FreeBSD-STABLE!C

     --------------------------------------------------------------

  23.2.1. "IYENI^3I.s-a-o FreeBSD CURRENT

   ^3o,I|A|,+-j 1/2O!AFreeBSD-CURRENT NOTO FreeBSD P:}uo-a-o
   !S:^3I<<e 1/2u!"!C FreeBSD-CURRENT
   "IYENI-aIP:.|^3,u+-j-a-oS:TH^3N-`aCURO!A
   |OYENBA^3,On|^3-`aCURO|UCURv,N"MS:xAo/-a-o"t^2IDEGYAD!C Y+-zNOTO
   FreeBSD .sCURa!A "-o>>o 1/2D-|b|w,E<<e^3I|nYENyCURT<<a:!C

     --------------------------------------------------------------

    23.2.1.1. CURDEG>>oNOTO FreeBSD-CURRENT!H

   FreeBSD-CURRENT NOTO FreeBSD -a-o^3I.s-a(c)!CYEN|YEN]S:t!G
   CUR'|bNOTauoP:YENNOTq!B^1eAAc,(c)E 1/2e-a-o *S:i!B^1L'c,(R)E'A-a-o
   3/4-:"i!A ^3o"C,-aF|e|bCURUCUR@|,YEN?|! relase
   -a-o-a(c)YEN>>YENi-`a.||^3!ACUR]YENi-`aCUR-L-.||^3-a-o!C 
   3/4"-oTH|^3^3\|h FreeBSD P:}uo-aI"CCURN^3-L-.| 1/2sA:P:
   FreeBSD-CURRENT source code!A |y|^3(R)E^3o"C,`i(c)l 1/2XNOTOuL-ak
   1/2sA:P:|"YEN\!C Ao:uM!A^3o"C,DEGYAD^3q+-`.| 3/4"S:O:,N"M!A |y
   FreeBSD-CURRENT
   "`i(c)^3NOTO+-a"O-ES:T(c)INOTO|hCURF.QnYENI-a-o.sYEN\-`a!BS:iu
   1/2!A ^3oAIYENDn"u"M(c)o+-zS:o.s`i(c)l 1/2X-a-o(R)E
   3/4-:NOTDEG|o|O(c)w!I

     --------------------------------------------------------------

    23.2.1.2.  1/2O:>>Yn FreeBSD-CURRENT!H

   FreeBSD-CURRENT  3/4A|XCURU|C^3oCURTAthCURH!G

    1. FreeBSD -aA,s|"u!G?n.YEN+-M-a`(c)o source tree
       -a-oNOTYCUR@^3!YEN-:!A YENHCURI>>{NOTDEG<<O<<uNOTDEG
       !S:current(^3I.s-aNOT-oA)!" NOTDEGu'^1i>>Y"D-a-oCURH!C

    2. FreeBSD -aA,s|"u!GNOTDEGCURF 1/2T<<O FreeBSD-CURRENT -`aDEG-:
       3/4"YENi-`a|a-ou<<u|b^3IA(c)w-a-o-aNOT-oA!A
       |OYENDDEGE-aa(R)EP:!,N"MDEGYAD-a-o'u,O-aI!C |^1YEN~!AAU|^3^1i
       FreeBSD -`a'-L-YENX"aAAe<<O/A:^3YENHCURIS:iu
       1/2CURe|V!A"A'-L-YENX patch  *YEN?AE-a-oCURH!C

    3. YENuNOTOAo:CURss(c)I-aI.QDEGN|O(CURn|p!AYENuNOTO 3/4\AA-a!A
       |O<<DDEGo|ae)-a-oCURH!C
       ^3o"C,CURH|^3(R)ECUR].|DEGu"C,uu,N!A(c)IDEG^A:m`i(c)l 1/2X!C

     --------------------------------------------------------------

    23.2.1.3. FreeBSD-CURRENT "ACUR-L-NOTO CURDEG>>o!H

    1. DEGl"D^3I.sYEN\-`a!C AAYEN>>!,I+-|^3"C,<<U:>>AA-a-o.sYEN\-`a!A
       "AS:AE+-ae|"NOTDEG+-z(c)P^3o-a-oCURHCURCUR^2A:CUR@O^1A,O-a-oCURH!A
       |]|^1+-N FreeBSD-CURRENT uo/NOTDEG"u+-o.mAA-a(c)-a-o+-P:(R)|!C
       3/4"-oTH!A+-z-`aDEG-:|]|^1-oYENyAA,N"`i^3I.s-a-oYEN\-`a!A
       |y^3oCUR].N"yuUYYENX^2{.s-a-o bug (R)E!A+-zCUR]NOTO-o.i"a:
       1/2A:!C

    2. *'_ bug -a-o^3t|"-ak!C |]NOTDEG FreeBSD-CURRENT
       -a-oYENo|o-a(c)YEN>>|b *'_CURw-a 3/4 bug
       -a-o|P(R)E!ACURSYENi-`a.|^2-L-YENI.s-a-o bug!C

    3. uL(c)OCUR-L-|b-a-o !S:officially supported!"!C
       S:UI.|-oECURO"oS:UCURWz FreeBSD-CURRENT
       -a-o"-oCURT-oO/AthS:O-a-o !S:legitimate!" "IYENI-aI!A
       |yS:UI"S(R)EP:!NOTDEGYENLI'-L-"NS:TH^3NCURa:'(c)!C
       ^3oCUR-L-YENN-aiS:UI<<U:'c|H!A(c)INOTOCUR-L-.QADEGS:UCURH(YNOTO-a-o,U:!A
       S:UICUR]CUR-L-.|NOTDEG FreeBSD S:VCUROCURF)
       !A^1e|bNOTO|]NOTDEGS:UICURA"YENF^3N!AuL-ak"CCURN|^u-a
       1/4AE|EODEGYAD!A |O|P(R)EA:~A:oP:}uo FreeBSD!C YENiYENH
       1/2T(c)w-a-oCUR@AI'NNOTO!A |bS:iu 1/2 FreeBSD
       (c)INOTO|^u-aCURjP:q|^3Ao:^1eAAc, 1/2X-a-oDEGYADCURS:P:!!A
       YnDEGuO?i 3/4U:-a-o,U:!AP:}uo-aI.|?i 3/4U:<<e-aI!C

     --------------------------------------------------------------

    23.2.1.4. "IYENI FreeBSD-CURRENT

    1. YEN[CURJ freebsd-current CURI cvs-all  1/2 * 3/4A!C
       ^3oCUR-L-^3aeYENuNOTOO<<O/A:^3!ACUR]NOTO YEN^2P:. S:@-a-o!C
       Y+-z"Sq 3/4\ freebsd-current
       !A"-o>>o'N.|?u^1LS:OCURH^1iYENO/<<e"t^2I-aNOT-oA-a-o>>!(c)u!A|ONOT\-O|bS:OCURHCURw,N-a-oDEGYAD!C
       S:o<<n-a-oNOTO!AYENi-`a.|?uYEN-c-CUR@"C,^1iCURv"(c)O-oTH"t^2I|w|MNOTU.i<<n-a-oCUR
       1/2S:i!C

       |b cvs-all CURW<<hYENiYENHNOTY"`i"CO commit NOTo:?y!A
       |]NOTDEG^3o"C,DEGO?y.|^3s+-a 1/4vAAT"a:YENLNOTUAo:,eDEGT!C

       nq 3/4\^3o"C, 1/2 * 3/4A(c)I"a:YENL 1/2 * 3/4A!A 1/2D-DEGN|O
       http://lists.FreeBSD.org/mailman/listinfo "AAI?i.Qq
       3/4\-a-o^3!CURAS:YYENi!C |U:(c)o"a:YENL<<aA:o"BAEJ|p|oP:i|ae!A
       |b"-o,I.||^3>>!(c)u!C

    2. +-q FreeBSD mirror -, "u+-o`i(c)l 1/2X!C
       |^3"a-oO/CURe|!YENiYENH^1F|"!G

         a. YENH csup (c)I cvsup u{|!.fDEGt|`i(c)o
            /usr/share/examples/cvsup AE|WNOTDEG standard-supfile
            -a-o supfile!C
            ^3oNOTOCURj(R)a^3I+-`+-AAE-a-oCURe|!!A|]NOTDEGYEN|YENiYENHAAy+-zS:a
            3/4aO tree ^3-L-S:`i|^"O!A
            CURS:<<a'NYENu"u|^3S:o.s-a-o^3!CURAS:YYENi!C
            |^1YEN~!A^3\|hCURH.|S:a csup (c)I cvsup (c)n"`i cron
            YENH(c)w'A|UDEGES:o.s!C +-zP:.n|Uq<<ez-a-o supfile 
            1/2d"OAE!A "ADEGw^1i|U"-oo,oAo^1OYENH 1/2O 3/4a csup (c)I
            cvsup NOTUAo:^3](c)w!C

         b. "IYENI CTM CURu"a!C Y-oo,oAo^1OCUR-L-"I
            (CURW-ooP:OYENIP:Q!A(c)IYENu-`aYENI email |OCURw) CTM
            .|CURn,u 3/4A|X+-z-a-o>>Y"D!C
            uM|O!A^3oCUR]|^3CUR@"C,-aS:A:^3"AYENB+-`S:`i"`iCUR@"C,|^3DEGYAD-a-oAE(R)
            *!C |]|^1!A <<U:CURO:CURH.|YENIYEN|!C
            ^3oCUR]uu(c)wCURFCUR-L--`a-ao/'A"I?`a^3oOS:o.sCURe|!!C
            YNOTO"IYENI 9600 bps modem (c)IAW
            1/4eS:oCURj-a-oCURW-oo-aI!A<<O/A:^3"IYENI CVSup !C

    3. YS:`i source code
       NOTOnYENI"OP:]-a-o!A|OCUR-L-P:EYENuNOTONOTYNOTY|OCURw!A
       "-o>>o'NS:`i  3/4aO
       FreeBSD-CURRENT!A|OCUR-L-nYENuS:`i^3!CURA!C
       |]NOTDEGCURj^3!CURA-a-o source code ^3-L-.|NOTU"I"`i"a:YENL
       source code Ao,`^3!CURA!A YNOTO+-zYENu
       1/2sA:P:"a:CURCURCUR@^3!YEN-:!A<<OAO.|<<U:^3A.D-!C

       |b 1/2sA:P: FreeBSD-CURRENT CURS:<<e!A 1/2D-YENJ^2O 3/4\AA-a
       /usr/src CUR-o-a-o Makefile!C 
       3/4"-oTHYENuNOTOCURE-AA^3!CURA-aF|e|OCURw!A+-z|U:CURO:CUR]nYENy
       ,E.s-a-o kernel YENHCURI<<.s 1/2sA:P: world!C |^1YEN~!A|h|h
       3/4\AA-a FreeBSD-CURRENT P:l>> 1/4 1/2 * 3/4A YENHCURI
       /usr/src/UPDATING CUR]NOTOYEN^2P:.-a-o!A CUR~-`a-a
       3/4^1DYENO/<<eP:i<< *NOTO<<c,
       1/4EYENHCURICURUCUR@-a(c).||^3CURDEG>>o.s-aF|e!C

    4. 1/4o:|aa!IY+-zYEN?|bP:] FreeBSD-CURRENT!A S:UI<<U:.Q-a
       3/4^1D+-z^1i(c)oYEN|-a-o.Q-akNOTOCURDEG>>o!ACUR
       *"a:NOTOYEN[+-jth"C,YEN\-`a!A (c)I,O
       *YEN?th"C,?u>>~-a-o<<O/A:^3!C
       |p-aG+-z|b<<O/A:^3(R)E-`a-athCURWNOTUAo:u{|! 1/2X-a-o,U:!A
       "-o-uNOTOCURO'ICURF!I

     --------------------------------------------------------------

  23.2.2. "IYENI^3I.s-a-o FreeBSD STABLE

    23.2.2.1. CURDEG>>oNOTO FreeBSD-STABLE!H

   FreeBSD-STABLE
   NOTOS:UI-a-oP:}uoCURACURa:!AYENDn-a-ouo|ae-a(c)'NYENN|^1|O"O!C
   ^3oOCURACURa:.|YENHCUR-L-|P^3t<< *S:@
   *S:iAAU:CURAE!A"AYENBDEG^2^3]^3o"C,NOTO^2A:CUR@|,P:iCURJ
   FreeBSD-CURRENT P:i|ae'u,O!C uM|O!A^3o CUR'uM
   A:Y(c)oP:}uoCURCUR-a-oCURACURa:!A
   CUR]'NNOTO>>!|bNOTY"C,(R)EO!AFreeBSD-STABLE
   YENi-`a.|!BCUR]YENi-`aCUR-L-.|^2AA|XCUR@"C,-S(R)i>>Y"D!C
   YEN|YENuCUR-L-^1LNOTOYENtCUR@OP:}uoCURACURa:|OCURw!AYENi-`aCUR-L-CURO
   3/4A|XCUR@-e"IYENI-aI!C

     --------------------------------------------------------------

    23.2.2.2.  1/2O:>>Yn FreeBSD-STABLE!H

   Y+-z|^3?^3 1/2`iYENhDEGlAU:!BDEG^A:m FreeBSD
   P:}uo^1Lu{(c)IS:@"C,DEG^A:m!A CUR *"a:NOTO.|,o FreeBSD
   +-uCURU"O-a-o !S:Ao:Aa:(c)E!" uo|ae|^3Ao:!A A^3,O|O 1/4{+-A:YENI
   FreeBSD-STABLE!C

   Ao:uM|wYENth-o|NOT}-a-o *,ECUR].|P:iCURJ FreeBSD-STABLE
   CURACURa:!A |yCUR-L-YEN^2P:EP:E|]|^1|O >>Yn YENhYENI
   FreeBSD-STABLE!C FreeBSD "CP:u security advisory(|wYENthCUR
   1/2S:i) ^3-L-.|,N>>!|p|oYENh *'_|^3"u:"`i 1/4vAAT-a-o-a(c)YEN>>
   [26]
   !AYP:E|]NOTDEG|wYENth|]-A|OYENh+-A:YENIP:}uoCURACURa:!AAo:uM.|,N"M^2{|^3CURw-a
   3/4DEGYAD!A |yCUR]YENi-`a+-a"OCUR@"C, 1/4c,AA-a-oDEGYAD!C

   3/4"-oTHS:UI-oECURO 1/2T<<O FreeBSD-STABLE
   CURACURa:|bYENo|o(R)EOS:!-`aYEN? 1/2T 1/2sA:P:!B^1BS:@!A
   |y"SCURH-`aDEG-:
   3/4a<<OYEN|AH(R)E^3-L-YENiYENH^2AA|XCURWzYENO/-a-o!C
   |^1YEN~!AAo:uM`i(c)l 1/2X|bP:iCURJ FreeBSD-STABLE
   CURS:<<e!A^3-L-.|YENy|b FreeBSD-CURRENT P:}uoS:^1^2|!A|y"IYENI
   FreeBSD-CURRENT -a-oCURH^2|^3-o>>.CURn FreeBSD-STABLE
   "IYENI-aI"O-a-oCURO:!A(c)OYENH^3q+-`|^3"C,DEGYAD!AYENi-`a|b
   FreeBSD-CURRENT CURn,u"SCURH-a`.N"`i!AAHuU FreeBSD-STABLE
   "IYENI-aI-a-o 1/4s-ax"IYENICUR~.|-B^2{!C

   YENN(c)oCURWz^3o"C,^2zYENN!AS:UI"ACUR-L-+-AAE -a 1/4YENO/DEGlAH
   FreeBSD-STABLE!A|OYENBS:o<<n-a-oNOTO!AS:O|b`i(c)l 1/2X(c)|YEN
   1/4,gS:^1 3/4a'u,OCURS:<<e!A 'N 1/2A:DEGES:a production server
   A`a^2 3/4"`i FreeBSD-STABLE Ao^1O!C

   Y+-z"S|^3^3o"C,|h-a-o(R)EP:!!B-oe-<<-a-o,U:!A"-o+-AAE+-z"IYENI^3I.s-a-o
   FreeBSD uo|ae-a(c)S:YYENi!A"A+-A:YENI"a:(c)O'-L-"N-a-o binary
   S:o.s 3/4-:"i"OS:^1|"CURE-AAA`a^2 3/4!C

     --------------------------------------------------------------

    23.2.2.3. "IYENI FreeBSD-STABLE

    1. q 3/4\ freebsd-stable list!C YENiYENHAAy+-zAH(R)EAA,N
       FreeBSD-STABLE -a-o^3nAAe
       1/2sA:P:(R)E-a-oNOTU"IAo:<<Y!AYENHCURI"a:YENL>>Y-SS:O-a`.N-a-oDEGYAD!C
       P:}uo-aI|b|O 1/4{CUR@"C,|^3-aS:A:^3-a-o
       *YEN?(c)IS:o.s(R)E!A'N.|YENy|b^3o,Iuo<<H>>!(c)u!A
       u^1"IYENI-aI|^3 3/4-:.|YENiYENHCURIA^3!A
       NOTYYENLI^1i(c)O'-L--a-oS:oS:iNOTOS:_|^3CURDEG>>o<<O/A:^3(c)IDEGYAD!C

       |O cvs-all list ^3oAa:YENiYENHNOTY"`i"CO commit log!A
       "a:CURCURYEN]NOTACURF^3\|hCURCUR-aO:-a-o,eDEGT!A"O|pCUR@"C,YENi-`auoYENI-a-oAa:>>U(R)A:A^3uYENuYEN!C

       .QnYEN[CURJ^3o"C,^3q<<H 1/2 * 3/4A-a-o,U:!AYENun"`i
       http://lists.FreeBSD.org/mailman/listinfo AICURU.Qq 3/4\-a-o
       list S:YYENi!C "a: 3/4l-a-o"BAEJ|b-ooP:CURW.||^3>>!(c)u!C

    2. YYEN'-oan|w,ECUR@OYENth.s-a-o"t^2I!A"AYENBS:AE+-ae,E
       FreeBSD-STABLE "CCURe(c)w'A-a-o snapshot!A"-o>>o 1/2D-DEGN
       3/4\ Snapshots -ooP:YENHAA,NNOTUAo:^2O,`!C
       |^1YEN~!ACUR]YENi+-q mirror -, "O|w,E^3I.s-a-o FreeBSD-STABLE
       uo|ae-a(c)!A"A^3z^1LCURU|C-a-o-a-o>>!(c)u"OS:o.s"`i^3I.s-a-o
       FreeBSD-STABLE `i(c)l 1/2X!C

       YCURw,E-a-oNOTO FreeBSD
       YENH<<e-a-o-a(c)YEN>>!A|O.Q^3z^1L`i(c)l 1/2XCURe|!"OCURE-AA!A
       "-o>>oCUR]NOTOYENiYENHS:QYENI FreeBSD mirror -, "OS:^1|"!C
       YENHCURUCURP:^2D-"a-oO/CURe|!!G

         a. YENH csup (c)I cvsup u{|!.fDEGt|`i(c)o
            /usr/share/examples/cvsup AE|WNOTDEG stable-supfile -a-o
            supfile!C ^3oNOTOCURj(R)a^3I+-`+-AAE-a-oCURe|!!A
            |]NOTDEGYEN|YENiYENHAAyS:AS:a 3/4aO tree ^3-L-S:`i|^"O!A
            CURS:<<a'NYENu"u|^3S:o.s-a-o^3!CURAS:YYENi!C
            |^1YEN~!A^3\|hCURH.|S:a csup (c)I cvsup (c)n"`i cron
            YENH(c)w'A|UDEGES:o.s!C +-zP:.n|Uq<<ez-a-o supfile 
            1/2d"OAE!A"ADEGw^1i|U"-oo,oAo^1OYENH 1/2O 3/4a csup (c)I
            cvsup NOTUAo:^3](c)w!C

         b. "IYENI CTM S:o.sCURu"a!C
            Y-oo,oCUR-L-S:O:(c)I-oo,oP:OYENIP:Q!A"-o>>oYENiYENH|O
            1/4{+-A:YENI!C

    3. CUR@-e|O"YEN!AY+-`>>Y|s"u^3I.s`i(c)l 1/2X!A|OCUR-L-p,u-oo,oAW
       1/4e-a-o,U:!A YENiYENH"IYENI csup (c)I cvsup (c)I ftp!C
       S:_<<h!A'N|O 1/4{ CTM!C

    4. |b 1/2sA:P: FreeBSD-STABLE CURS:<<e!A 1/2D-YENyYENJ^2O
       3/4\AA-a /usr/src CUR-o-a-o Makefile AE!C 
       3/4"-oTHYENuNOTOCURE-AA^3!CURA-aF|e|OCURw!A+-z|U:CURO:CUR]nYENy
       ,E.s-a-o kernel YENHCURI<<.s 1/2sA:P: world!C |^1YEN~!A|h|h
       3/4\AA-a FreeBSD-STABLE P:l>> 1/4 1/2 * 3/4A YENHCURI
       /usr/src/UPDATING CUR]NOTOYEN^2^3AE-a-o!A ^3o 1/4ECUR~-`a-a
       3/4^1DYENO/<<eP:i<< *NOTO<<c,
       1/4E!AYENHCURICURUCUR@-a(c).||^3th"C,.s-aF|e!C

     --------------------------------------------------------------

23.3. S:o.sS:A-a-o Source

   FreeBSD p^1-o`i(c)l 1/2X|^3^3\|h^3z^1L-oo,o((c)I
   email)-a-oCURe|!"OS:o.s!A uL 1/2
   *NOTOS:o.s"-oCUR@P:o>>aDEG`i!A^3o"C,YENthYENN+-z|U|ae"M(c)w!C
   S:UIYENDn'-L-"N-a-oNOTO Anonymous CVS!BCVSup !BCTM!C

     A:uS:iAo:uMYENiYENHYENuS:o.s^3!CURA`i(c)l
     1/2X!A|yDEGssCUR@CURa:'(c)-a-oS:o.sNOTyu{NOTOS:o.s 3/4aO tree!A
     "AYENB<< 1/2s
     userland(CURn|p!GYENN"IYENI-aIYENhDEGo|ae-a-o(c)O|^3u{|!!A^1^3NOTO
     /bin!B/sbin CUR-o-a-ou{|!)YENHCURI kernel `i(c)l 1/2X!C
     YYENuS:o.s^3!CURA-a-o source tree!B(c)IYENu|^3 kernel
     ^3!CURA!B(c)IYENu|^3 userland
     ^3!CURA!A^3q+-`.|^3y|"CUR@"C,?u>>~!A^1^3NOTO!G
     1/2sA:P:?u>>~!Bkernel panic!B,e(R)AE.'.luYEN !C

   Anonymous CVS CURI CVSup S:!NOTO+-A: pull  1/4O|!"OS:o.s`i(c)l
   1/2X!C YENH CVSup NOTDEG"O!A "IYENI-aI((c)I cron script).|DEGo|ae
   cvsup u{|!!A<<a-aI.|>>PNOTYCUR@YENx cvsupd |o/-aA
   3/4^1S:@"C,CURNOTDEGE!A YENHS:o.sNOTUAo:`i(c)l 1/2XAE(R) *!C
   +-z(c)O|NOT"`iS:o.s.|NOTO.i(R)E^3I.s-a-o!A
   |OYENBYENu.||NOT"`i>>YS:o.s-a-o^3!CURA!C
   |^1YEN~!ACUR]YENiYENH<<U:>>'APYENh^3](c)wnS:o.s-a-o 1/2d^3o!C
   S:o.s.|YENN|o/-aA 3/4^1,oYEN>>
   3/4-:CURn^1iCURS:<<a!AYENaYENX.i(R)E+-z(c)O>>Yn-a-oS:o.sAE(R)
   *u^1S:A!C Anonymous CVS -a-o.S:(c)ANOTU^1i(c)o CVSup
   "O+-oS:oA^2^3ae"C,!A|]NOTDEGYEN|YENuNOTO CVS
   -a-o(c)u|u|OCURw!ACUR@ 1/4EAAyS:AYENi+-q>>.-oY-a-o CVS repository
   "uYENX^3I.s`i(c)l 1/2X!C uM|O CVSup
   |b^3oCURe+-.|S:o|^3(R)A:^2v!ACUR-L-^1L Anonymous CVS
   ^1i.sCURa|O"YEN!ANOTOYENIDEG_"OCURn,uA^2^3ae!C

   YENtCUR@-oO/CURe|!<<hNOTO CTM!C YEN|"ACUR-L-NOTOYENHYENae
   1/2I|!CURP:+-"OCURn^1i+-z(c)O 3/4O:|^3-a-o sources (c)M|o/-aA
   3/4^1CURW-a-o sources (c)INOTO+-z"u+-o-a-oS:o.s^3!YEN-:!C
   NOTUCURI-a-o!A.||^3CUR@O script
   AE+-M-auYENI"O?eANAAU:S:o^1L-a-oAE(R) *!A^3oOu{|!NOTOYENN CTM
   |o/-aA 3/4^1"ODEGo|ae!A "CCURN.|CURn^1i
   1/4AE|,!A"AS:a"a|,DEGo|ae'AP:!CUR-oAAU:S:o^1L-a-oAE(R)
   *YEN[YENHA-L-AY!A "Au^1YEN|ICUR@OS:C,,^1!AuM<<a'NYEN[YENH 1/2s
   1/2X(YENuYENI printable ASCII |rCUR,)!A "AYENH email
   -a-oCURe|!+-HYENX!C .i+-z|NOT"`iYEN|-a-o(R)EO!A^3o"C, !S:CTM
   deltas!" 'NYENiYENHYENN ctm_rmail(1)
   u{|!"O^3B^2z!A,Ou{|!.||UDEGE,N 1/2X!B 1/2T>>{!B
   (R)MYENI^3o"C,AAU:S:o!C ^3ou{S:C,CURn CVSup
   "O>>!NOTOS:O:+-o|hCURF!A |OYENB!A^3oO 1/4O|!^1iS:UI-a-o|o/-aA
   3/4^1"O>>!NOTOCURn,u>>'AP-a-o!A|]NOTDEG^3oNOTOCUR@O push -a-o
   1/4O|!!A|O<<D pull -a-o 1/4O|!!C

   .iuM!A^3o 1/4EDEGuCUR].|+-a"OCUR@"C,CUR-L-<<K!C
   YCUR-L-CURpCURssS:a+-z^3!YEN-:-a-ou{|!^2MDEG-L-+- 1/4CURF!A CVSup
   .|DEG>>'uYENX"O!A"A|UDEGENOTDEG+-zS:aCUR-L-"NOT-a-o^3!YEN-:,E>>o!C
   CTM "ACUR-L-.|NOTDEG+-zDEGu^3o"C,DEGES:@!C Y^2M+-
   1/4CURF+-z-a-o^3!YEN-: source
   (|OYENB"S^3AEYEN-:)!A+-zYENiYENH+-qAYP:}(c)l(+-q^3I.s-a-o CVS
   !S:base delta!")"AYENI CTM "O<<<<O/YEN|I !A(c)INOTOYENI Anonymous
   CVS "OS:^1|"!A YENunS:aCUR-L-YEN? 1/2T-a-o|aCUReNOTaa+-
   1/4!A|A<<.sDEGu|P"B-a-oDEGES:@S:YYENi!C

     --------------------------------------------------------------

23.4. <<.s 1/2sA:P: !S:world!"

   |bS:o.s FreeBSD -a-o source tree "`i^3I.sCURS:<<a(uL 1/2 *NOTO
   FreeBSD-STABLE!B FreeBSD-CURRENT
   uYENuYEN)!A+-uCURU"O'NYENiYENHYENI^3o"C, source tree "O<<.s
   1/2sA:P:"t^2I !C

     DEGu|n^3AEYEN-:|bS:@YENo|oCURjDEGES:@ CURS:<<e
     nDEGO+-oYENyS:a"t^2IS:@^3AEYEN-:-a-o<<n(c)EuLP:.+-j 1/2O!C 
     3/4"-oTH<<.s 1/2sA:P: world NOTO
     (YENun|^3.OCURaaYENo<<u:YENU:YENhS:@-a-o,U:)CUR@YENo<<U:A^2^3ae-a-o"AE+-!!A|yYENX?uCUR]NOTO|b(c)OAo/S:K-a-o!C
     YENtYEN~!AS:OCURH|b source tree
     CUR-L-.V.d^2V-a-o?u>>~!ACUR]YENi-`a.|^3y|""t^2IuL-akP:} 3/4-: !C

     1/2D- 1/2T>>{|UCURvCURwS:@S:'NOTUAo:^3AEYEN-:!A"AYENBCURaAa:|^3
     fixit -oICURu(c)IP:} 3/4-:YENu-oD-!C
     +-zYENi-`aYENA>>.CUR]YENICUR-L-"`i^3o"C,-aF|e!A
     |y|wYENth^2A:CUR@A`CURn"AE<<a>>!(c)e-op"O+-o|nS:a!I

     q 3/4\NOTUAo:-a-o Mailing ListFreeBSD-STABLE YENHCURI
     FreeBSD-CURRENT CURACURa:!AYEN>> 1/2eCURW'NNOTOA:Y(c)o  
     P:}uoP:YENNOTq!C NOTDEG FreeBSD
     S:@DEG^A:m-a-oCUR]^3-L-NOTOCURH!ADEG,-o,CUR].|YENC,?u>>~!C

     |^3(R)EO^3o"C,?u>>~"AuLCURjA-a!AYENuNOTO.|AAy"t^2I^2-L-YENI.s-a-o?u>>~A:uS:i|OCURw!C
     |^3(R)E<<hNOTO"aAo/!AYENi-`a.| 3/4EPCUR-L--`aP:} 3/4-:(c)IAE(R)
     *"t^2I-a-o.'.l((c)IS:oAV)!C

     Y^1J"`iAth|u:DEGYAD!AP:K<<E 1/4D-ADNOTDEG !S:heads up(-a`.N)!"
     P:}AY-a-o<<H"`iNOTUAo:-a-o mailing
     list!A"AA?^2M.!DEGYADAIYENHCURI.| 1/4vAATth"C,"t^2I!C
     |bDEGYADAo,N"M<<a!A|AP:K 1/4D-ADNOTDEG !S:all clear(CURw,N"M)!"
     P:}AY-a-oAn(c)u<<H!C

     YYENI-a-oNOTO FreeBSD-STABLE (c)I FreeBSD-CURRENT!A<<oCURSCUR-L-
     3/4\AA-a FreeBSD-STABLE P:l>> 1/4 1/2 * 3/4A (c)I
     FreeBSD-CURRENT P:l>> 1/4 1/2 * 3/4A -a-oDEGQ 1/2
     *!A"-o>>o.|NOTO|US:a:^3A.D-|OCURw!C

     CUR-L-nYENI make
     worldCUR@DEGi|'A-a-oAACURaaYENo^3-L-.|<<O/A:^3>>!"IYENI make
     world!C ^3o
     1/4EDEGu.|,o^1LCUR@"C,<<n"BAEJ!A<<O/A:^3YENu|^3|bS:A-a
     3/4^1D|UCURv|bS:@CURDEG>>o!A|A^3o>>oDEGu!C |bu'CURj|h
     1/4AE-a-o+-!-apCURU!A 1/2D-CUR-L-nP:AYENI make world!A
     |O,OS:iYENICURU+-CURP:^2D--a-oCURe|!!C

     --------------------------------------------------------------

  23.4.1. S:o.s"t^2I-a-o 1/4D-.C,CURe|!

   nCURE-AA"t^2I<<e!ACUR@(c)wnYENyNOTd 3/4\ /usr/src/UPDATING
   CURaaYENo!AYENHAA,N buildworld
   CURS:<<e>>YnS:@th"C,"AE+-!(c)I-a`.N"AEP:u!A
   uM<<aCUR~YENICURU|C"BAEJ!G

 # make buildworld
 # make buildkernel
 # make installkernel
 # reboot

     -a`: |bCURO: 1/4AE-aNOT-ap!AYENi-`a>>YnYENy|b buildworld
     "BAEJCURS:<<eYENyS:@ mergemaster -p CUR~-`aS:^1|"!C
     |U:(c)o|o(R)E>>Yn(c)ICUR-L->>Yn!A 1/2D-DEGN 3/4\ UPDATING
     CUR-o-a-o>>!(c)u!C
     CUR@-e"O>>!!AYENunCUR-L-NOTOP:i|ae,o-a(c),^1(major)-a-o FreeBSD
     -a(c)YEN>>CURE-AA!A 'NYENi^2CUR^1L^3o"BAEJ!C

   S:^1|" installkernel CURS:<<a!A>>Yn<<P:} 3/4-:"ACURA"`i single
   user  1/4O|!(A|"O!GCUR]YENiYENH|b loader
   '-L-YENU:^2AA,^1<<a+-YEN[CURW boot -s)!C +-uCURU"ODEGo|ae!G

 # mergemaster -p
 # make installworld
 # mergemaster
 # reboot

     Read Further
     ExplanationsCURWz"BAEJYENuNOTO"oS:U+-zCURE-AA-a-oA^2^3ae>>!(c)u|OCURw!AYn^2M.!AA,N"CCUR@"BAEJ!A
     CUR *"a:NOTOY+-y|U|aeYEN'^3y kernel ^3](c)w!A'NS:o,O
     3/4\AA-aCURU+--a-oCUR-o(R)e!C

     --------------------------------------------------------------

  23.4.2.  3/4\AA-a /usr/src/UPDATING

   |bS:@YENo|o"AE+-!CURS:<<e!A 1/2D-DEGEYEN^2YENy 3/4\AA-a
   /usr/src/UPDATING ((c)I|b source code CUR-oAth|u:-a-oCURaaYENo) !C
   ^3oYEN-:CURaaYENo.| 1/4g"`iYENi-`a
   3/4D^1J-a-oDEGYAD!A(c)I<<u:(c)w"-o"C,.|DEGo|ae-a-o<<u:YENOP:P:S:C,NOTDEG|o!C
   |p-aGS:A 3/4-: 3/4^1^2{|b-a-o UPDATING
   CURaaYENo>>P^3oAa:-a-o'yz|^3 1/2A:NOTd-!BYENUNOTTHCURS:^3B!A"-o>>o
   1/2D-YENH 3/4-: 3/4^1CURW-a-o UPDATING NOTDEG.C,!C

     <<n: uM|O!A|p|PYENy<<e(c)Oz!A^3ae^3aeYENu 3/4a 3/4\AA-a UPDATING
     "ACUR-L--`aS:^1YENth"uYENN mailing list!C
     ^3o"a-aI^3-L-NOTOCURNOT,E-a-o!A|OCUR-L-NOTU+-AEYEN,!C

     --------------------------------------------------------------

  23.4.3. AENOTd /etc/make.conf

   AENOTd /usr/share/examples/etc/make.conf YENHCURI /etc/make.conf!C
   ^2A:CUR@YEN-:CURaaYENoCURDNOTOCUR@"C,"t^2I^1w^3]E !V
   CUR-L-^1L!ACURj^3!CURA^3-L-^3Quu,NDEG_"O!C NOTDEGCURF|b<<.s
   1/2sA:P:(R)E-`aDEG-:"IYENI^3o"C,!A  1/2D-S:a^3o"C,^3](c)wYEN["`i
   /etc/make.conf!C  1/2D--a`.N|b /etc/make.conf
   -a-oYENo|o^3](c)wCUR].| 1/4vAAT"`i"C|,"IYENI make -a-ou^2-aG!A
   |]|^1^3](c)wCUR@"C,
   3/4A|X|UCURv"t^2I-a-o?iP:u.|NOTOCUR-L-?u-a-oS:@-ak!C

   CUR@-e"IYENI-aI^3q+-`.|+-q /usr/share/examples/etc/make.conf 
   1/2AE>>s CFLAGS YENHCURI NO_PROFILE CURS:Ath-a-o^3](c)w"`i
   /etc/make.conf!A"A,NDEG-L-NOTUAo:uu,N|LDEGO !C

   |^1YEN~!ACUR]YENiYENH,O,ONOTY"a:YENL^3](c)w (COPTFLAGS!B
   NOPORTDOCS uYENuYEN)!ANOTOS:_^2AA|X|UCURv(c)O>>Y!C

     --------------------------------------------------------------

  23.4.4. S:o.s /etc CUR-o-a-o^3](c)wAE

   |b /etc YENO/?y.||^3"t^2I-a-oNOTUAo:^3](c)wAE!A YENHCURIP:}
   3/4-:(R)E-a-o|UP:u-aADEGE+-ODEGE script!C |^3"C, script AH FreeBSD
   -a(c)YEN>>-a-oCUR-L-|P|O|^3"C,(R)t^2S:!C

   "a:CURCUR|^3"C,^3](c)wAE.||b"CCURe^1BS:@-a-o"t^2I,ICUR].|YENI"`i!C
   CUR *"a:NOTO /etc/group!C

   |^3(R)EO|b make installworld |w,E^1Lu{CURCUR!A
   .|>>YnYENy<<O/YENssNOTY"C,-S(c)w+-b,^1(c)I,s^2O!C
   |bP:i|aeCURE-AACURS:<<e!AYEN|IYENi-`a"ACUR-L-|s|b!A
   |]|^1CURE-AA(R)E'N.|^3y|"DEGYAD!C |^3(R)EO make buildworld
   .|YENyAENOTd^3o"C,(c)O>>Y-a-o+-b,^1(c)I,s^2ONOTOS:_CURw|^3|s|b!C

   A|O^3o 1/4E-a-o"OCURl!A^1^3NOTONOTY|,CURE-AACURS:<<aYEN^2P:..s
   1/4W smmsp +-b,^1!C Y"IYENI-aI(c)|YEN 1/4.s
   1/4W,O+-b,^1'NnS:^1|"CURE-AA 3/4THS:@-a-o,U:!A .||b mtree(8)
   ^1A,O<<O/YENss /var/spool/clientmqueue (R)EuoYENIYEN-c-+-N!C

   ,N-akNOTO|b buildworld P:YENNOTqCURS:<<e!AYENyDEGo|ae
   mergemaster(8) "A.fDEGt -p ?iP:u!C YEN|.|CURn^1i"-o"C,DEGo|ae
   buildworld (c)I installworld (c)O>>YCURS:Ao:Aa:^3](c)wAE!C
   YS:A(c)OYENI-a-oNOTO|'ACUR'YEN 1/4CURa:'(c) -p -a-o mergemaster
   -a(c)YEN>>!A"-o>>o-a 1/2+-u"IYENI source tree
   CUR-o-a-o.s-a(c)S:YYENi!G

 # cd /usr/src/usr.sbin/mergemaster
 # ./mergemaster.sh -p

     '-L-YENU:: Y+-zNOTODEG 3/4DEGo"g(paranoid)!A
     YENiYENH^1^3CURU+-^3o 1/4EYENh,OuUAENOTd"t^2ICURW|^3th"C,AE(R)
     *A:Y(c)oCURwS:i|W(c)I^3QS:RDEG-L--a-o,s^2O !G

 # find / -group GID -print

     ^3o.|AAaYENU:(c)O|^3^2AA|XnS:a:-a-o GID ,s^2O
     (YENiYENHNOTO,s^2O|W-oU!A(c)I-aINOTO,s^2O-a-o
     1/4AE|rYENN,^1)-a-o(c)O|^3AE(R) *!C

     --------------------------------------------------------------

  23.4.5. CURA'<<"`i Single User  1/4O|!

   +-zYENi-`a.|.Q|b single user  1/4O|!CURU 1/2sA:P:"t^2I!C
   DEG-L-CURFYENiYENH(c)uAAaS:oS:O:S:^1|"CURS:YEN~!A|w,E^1Lu{CURCUR+-N.|^2o-A^3\|h<<n-a-o"t^2IAE(R)
   *!A YEN]NOTA(c)O|^3"t^2I binaries!Blibraries!Binclude AE(R)
   *uYEN!C Y|b^1BS:@CURCUR-a-o"t^2I(CUR
   *"a:|^3^3\|h"IYENI-aI|bYENI-a-o(R)EO)CUR-oS:oS:i^3o"C,AE(R) *!A
   "-oA^2-a 1/2NOTO|US:a:^3A.D--a-oS:@-ak!C

   YENtCUR@-oO/ 1/4O|!NOTOYENy|b multi-user  1/4O|!CURU
   1/2sA:P:|n"t^2I!AuM<<a|ACURA"`i single user  1/4O|!YENh|w,E!C
   Y+-zCURn,u^3ssAAw^3o-oO/CURe|!!AYENu>>Y|b build( 1/2sA:P:^1Lu{)
   S:^1|"CURS:<<a!A |AYENhDEGo|aeCURU+--a-o"BAEJS:YYENi!C CUR@-a
   1/2"`iYENiCURA'<< single user  1/4O|!(R)E!A|AYENhDEGo|ae
   installkernel (c)I installworld S:YYENi!C

   CURA'<<NOTDEG root "YEN-:YEN'!G

 # shutdown now

   ^3o 1/4E'N.|+-q`iYEN>>-a-o multi-user  1/4O|!CURA'<<"`i single
   user  1/4O|!!C

   DEG-L-|^1CURS:YEN~CUR]YENiYENH<<P:} 3/4-:!A+-uuU|bP:}
   3/4-:?i^3ae^3B?i 3/4U: !S:single user!" ?iP:u!C
   |p|^1CUR@"O'N.|P:iCURJ single user  1/4O|!!A uM<<a|b shell
   '-L-YENU:^2AA,^1^3B?eCURJ!G

 # fsck -p
 # mount -u /
 # mount -a -t ufs
 # swapon -a

   ^3o 1/4E.|YENyAENOTdAE(R) *"t^2I!A"A<<.s+-N / S:iYENHYENiAA-a
   1/4g-a-o 1/4O|!+- 3/4,u:!AYENHCURI /etc/fstab
   CUR-o(c)O^3](c)w-a-o"a:YENL UFS AE(R) *"t^2I!A^3I<<a+-OYENI swap
   -oIDEGI!C

     -a`: Y CMOS (R)EA:ANOTO^3]NOTDEG.i|a(R)EP:!!A|O<<D GMT
     (R)EDEGI(Y date(1) <<u:YENO"SAAaYENU:YEN?
     1/2T-a-o(R)EP:!!B(R)EDEGI)!A"-oYENi-`a>>Yn|A?eCURJCURU|C<<u:YENO!G

 # adjkerntz -i

     ^3o"BAEJYENiYENH 1/2T>>{+-z-a-o.i|a(R)EDEGI^3](c)wNOTOS:_YEN?
     1/2T !X!X S:_<<hCURe<<a.|^3y|"CUR@"C,DEGYAD!C

     --------------------------------------------------------------

  23.4.6. ^2 3/4DEG-L- /usr/obj

   |b<<.s 1/2sA:P:"t^2I-a-o^1Lu{CURCUR!A
   1/2sA:P:u^2-aG.|(c)n"`i(^1w^3]+-!-ap) /usr/obj CUR-o!C
   ^3o,I+--a-oYENO/?y.|^1iA^3"`i /usr/src -a-oYENO/?yu^2-oc!C

   NOTaa+- 1/4^3oYENO/?y!AYENiYENHAAyYENH<<a-a-o make buildworld
   ^1Lu{S:oS:O:CUR@"C,!A|OYENBYENiA *S:KYENH<<e
   1/2sA:P:-a-o-aF|e,o^2{|b-a-o^2V^2c|bCUR@DEG_-a-oNOTU"I?uP:A !C

   |O|^3"C, /usr/obj CUR-o-a-oAE(R)
   *YENi-`a.|^3](c)wCUR-L-YENiS:oDEGE-a-o flag(^2O,` 1/2D-DEGN 3/4\
   chflags(1))!A|OYEN^2P:.YENy(R)^3+- 1/4^3o"C, flag ^3](c)wCUR~|ae
   !C

 # cd /usr/obj
 # chflags -R noschg *
 # rm -rf *

     --------------------------------------------------------------

  23.4.7. <<.s 1/2sA:P: Base System

    23.4.7.1. <<O-d 1/2sA:P:-a-oNOTo:?y

   <<O/A:^3 3/4i|"|n^2ss-oD!AS:aDEGo|ae make(1)
   (R)E^2-L-YENI-a-oNOTo:?y|sDEG_"O!C ^3o
   1/4EY|^3thAa:YENX?u!A'N.||^3?u>>~DEGT(R)S:-a-oNOTo:?y!C
   Ao:uM^3ae^3ae^3o 1/4E!A S:AYENi-`aCUR-L--a
   3/4^1D|p|oCURA-aRNOTOthAa:YENXCURFS:A!A|yYS:aS:ADEGYADDEGO?yP:K"`i
   FreeBSD NOTUAo:-a-o mailing list
   'NYENiYENH|^3CURHYENiYENHADEG|-L-NOTYNOTO<<c,>>oCUR@|^"AE+-!!C

   ^3IA^2^3ae-a-oCUReNOTO'NNOTOYENI script(1)
   <<u:YENO!A"AYEN[CURWDEGN 1/4AE (S:A.Q|s(c)nDEGO?y-a-oAE(R)
   *|`i,m!BAE|W)S:YYENi!C ^3o"BAEJA^3,O|b<<.s
   1/2sA:P:"t^2I(R)E'NnS:@!AuM<<a|bS:^1|" 1/2sA:P:<<a?eCURJ exit
   S:YYENiA-:P:}!C

 # script /var/tmp/mw.out
 Script started, output file is /var/tmp/mw.out
 # make TARGET
 !K compile, compile, compile !K
 # exit
 Script done, !K

   ^1iCURF!AAU|^3CUR@AI 3/4"P:qS:OS:aAE(R) *|s"`i /tmp YENO/?yCUR-o!C
   |]NOTDEG<<P:} 3/4-:CURS:<<a!A
   ^3oYENO/?yCUR-o-a-o-aF|e^3-L-.|^3Q^2M-aAA!C CURn,uS:'u
   1/2-a-o|aCUReNOTO /var/tmp (|pCURW"O(c)OYENU:) (c)I-aINOTO root
   -a-o(R)aYENO/?y!C

     --------------------------------------------------------------

    23.4.7.2.  1/2sA:P: Base System

   -oYENy 1/2D-YENyCURA'<<"`i /usr/src YENO/?y!G

 # cd /usr/src

   (.iuM!ADEG-L-<<DS:AS:a source code
   (c)n"`i"a:YENL|aCURe!AY-uNOTO^3o 1/4E!A
   'NCURA'<<"`i"-oOYENO/?yS:YYENi)!C

   "IYENI make(1) <<u:YENO"O<<.s 1/2sA:P: world!C ^3o<<u:YENO.|+-q
   Makefile AE(^3oAE.| 1/4g FreeBSD -a-ou{|!,O|p|o<<.s
   1/2sA:P:!BYENHth"C,P:P:S:C,"O
   1/2sA:P:uYENuYEN)YENhAA-a"uNOTUAo:<<u:YENO!C

   CUR@-eCURU<<u:YENO-a-o(R)ae|!|pCURU!G

 # make -x -DVARIABLE target

   |b^3oO"OCURl!A-x NOTOS:A.QP:C,u^1 make(1) -a-o?iP:u!A^2O,`>>!(c)u
   1/2D-DEGN 3/4\ make(1) >>!(c)u!A ,I+-|^3NOTUAo: 1/2d"O>>!(c)u!C

   -DVARIABLE <<hNOTOS:aAAU: 1/4AE^3](c)wP:C,u^1 Makefile!C
   ^3o"C,AAU: 1/4AE.|+-+-"i Makefile -a-o|aeNOTDEG!C ^3o"C,^3](c)w>>P
   /etc/make.conf -a-oAAU: 1/4AE^3](c)wNOTOCUR@ 1/4E!A
   YENuNOTOYENtCUR@-oO/^3](c)wCURe|!|OCURw!C

 # make -DNO_PROFILE target

   CURW+--a-o"OCURl<<hNOTOYENtCUR@-oO/^3](c)wCURe|!!ACUR]'NNOTOth"C,CUR-L-n!C
   ^3oO"OCURlCURCUR-a-o.N<<a:NOTOCUR-L-YENh 1/2sA:P: profiled
   libraries!A(R)A:-aG'N|p|P^3](c)w|b /etc/make.conf -a-o

 NO_PROFILE=    true     #    Avoid compiling profiled libraries

   target <<hNOTOS:iP:D make(1) ,OYENhDEGuth"C,!C "CO Makefile
   ^3-L-.|(c)w,qCUR-L-|P-a-o !S:targets!"!AuM<<a"I+-z(c)Ou^1-a-o
   target 'N.|"M(c)w.|DEGuth"C,DEGES:@ !C

   Some targets are listed in the Makefile, but are not meant for you
   to run. Instead, they are used by the build process to break out
   the steps necessary to rebuild the system into a number of
   sub-steps.

   Most of the time you will not need to pass any parameters to
   make(1), and so your command like will look like this:

 # make target

   Where target will be one of many build options. The first target
   should always be buildworld.

   As the names imply, buildworld builds a complete new tree under
   /usr/obj, and installworld, another target, installs this tree on
   the current machine.

   Having separate options is very useful for two reasons. First, it
   allows you to do the build safe in the knowledge that no
   components of your running system will be affected. The build is
   !S:self hosted!". Because of this, you can safely run buildworld
   on a machine running in multi-user mode with no fear of
   ill-effects. It is still recommended that you run the installworld
   part in single user mode, though.

   Secondly, it allows you to use NFS mounts to upgrade multiple
   machines on your network. If you have three machines, A, B and C
   that you want to upgrade, run make buildworld and make
   installworld on A. B and C should then NFS mount /usr/src and
   /usr/obj from A, and you can then run make installworld to install
   the results of the build on B and C.

   Although the world target still exists, you are strongly
   encouraged not to use it.

   Run

 # make buildworld

   It is possible to specify a -j option to make which will cause it
   to spawn several simultaneous processes. This is most useful on
   multi-CPU machines. However, since much of the compiling process
   is IO bound rather than CPU bound it is also useful on single CPU
   machines.

   On a typical single-CPU machine you would run:

 # make -j4 buildworld

   make(1) will then have up to 4 processes running at any one time.
   Empirical evidence posted to the mailing lists shows this
   generally gives the best performance benefit.

   If you have a multi-CPU machine and you are using an SMP
   configured kernel try values between 6 and 10 and see how they
   speed things up.

     --------------------------------------------------------------

    23.4.7.3. Timings

   Many factors influence the build time, but fairly recent machines
   may only take a one or two hours to build the FreeBSD-STABLE tree,
   with no tricks or shortcuts used during the process. A
   FreeBSD-CURRENT tree will take somewhat longer.

     --------------------------------------------------------------

  23.4.8. Compile and Install a New Kernel

   To take full advantage of your new system you should recompile the
   kernel. This is practically a necessity, as certain memory
   structures may have changed, and programs like ps(1) and top(1)
   will fail to work until the kernel and source code versions are
   the same.

   The simplest, safest way to do this is to build and install a
   kernel based on GENERIC. While GENERIC may not have all the
   necessary devices for your system, it should contain everything
   necessary to boot your system back to single user mode. This is a
   good test that the new system works properly. After booting from
   GENERIC and verifying that your system works you can then build a
   new kernel based on your normal kernel configuration file.

   On FreeBSD it is important to build world before building a new
   kernel.

     -a`: If you want to build a custom kernel, and already have a
     configuration file, just use KERNCONF=MYKERNEL like this:

 # cd /usr/src
 # make buildkernel KERNCONF=MYKERNEL
 # make installkernel KERNCONF=MYKERNEL

   Note that if you have raised kern.securelevel above 1 and you have
   set either the noschg or similar flags to your kernel binary, you
   might find it necessary to drop into single user mode to use
   installkernel. Otherwise you should be able to run both these
   commands from multi user mode without problems. See init(8) for
   details about kern.securelevel and chflags(1) for details about
   the various file flags.

     --------------------------------------------------------------

  23.4.9. Reboot into Single User Mode

   You should reboot into single user mode to test the new kernel
   works. Do this by following the instructions in uU 23.4.5 ,`.

     --------------------------------------------------------------

  23.4.10. Install the New System Binaries

   If you were building a version of FreeBSD recent enough to have
   used make buildworld then you should now use installworld to
   install the new system binaries.

   Run

 # cd /usr/src
 # make installworld

     -a`: If you specified variables on the make buildworld command
     line, you must specify the same variables in the make
     installworld command line. This does not necessarily hold true
     for other options; for example, -j must never be used with
     installworld.

     For example, if you ran:

 # make -DNO_PROFILE buildworld

     you must install the results with:

 # make -DNO_PROFILE installworld

     otherwise it would try to install profiled libraries that had
     not been built during the make buildworld phase.

     --------------------------------------------------------------

  23.4.11. Update Files Not Updated by make installworld

   Remaking the world will not update certain directories (in
   particular, /etc, /var and /usr) with new or changed configuration
   files.

   The simplest way to update these files is to use mergemaster(8),
   though it is possible to do it manually if you would prefer to do
   that. Regardless of which way you choose, be sure to make a backup
   of /etc in case anything goes wrong.

     --------------------------------------------------------------

    23.4.11.1. mergemaster

   Contributed by Tom Rhodes.

   The mergemaster(8) utility is a Bourne script that will aid you in
   determining the differences between your configuration files in
   /etc, and the configuration files in the source tree /usr/src/etc.
   This is the recommended solution for keeping the system
   configuration files up to date with those located in the source
   tree.

   To begin simply type mergemaster at your prompt, and watch it
   start going. mergemaster will then build a temporary root
   environment, from / down, and populate it with various system
   configuration files. Those files are then compared to the ones
   currently installed in your system. At this point, files that
   differ will be shown in diff(1) format, with the + sign
   representing added or modified lines, and - representing lines
   that will be either removed completely, or replaced with a new
   line. See the diff(1) manual page for more information about the
   diff(1) syntax and how file differences are shown.

   mergemaster(8) will then show you each file that displays
   variances, and at this point you will have the option of either
   deleting the new file (referred to as the temporary file),
   installing the temporary file in its unmodified state, merging the
   temporary file with the currently installed file, or viewing the
   diff(1) results again.

   Choosing to delete the temporary file will tell mergemaster(8)
   that we wish to keep our current file unchanged, and to delete the
   new version. This option is not recommended, unless you see no
   reason to change the current file. You can get help at any time by
   typing ? at the mergemaster(8) prompt. If the user chooses to skip
   a file, it will be presented again after all other files have been
   dealt with.

   Choosing to install the unmodified temporary file will replace the
   current file with the new one. For most unmodified files, this is
   the best option.

   Choosing to merge the file will present you with a text editor,
   and the contents of both files. You can now merge them by
   reviewing both files side by side on the screen, and choosing
   parts from both to create a finished product. When the files are
   compared side by side, the l key will select the left contents and
   the r key will select contents from your right. The final output
   will be a file consisting of both parts, which can then be
   installed. This option is customarily used for files where
   settings have been modified by the user.

   Choosing to view the diff(1) results again will show you the file
   differences just like mergemaster(8) did before prompting you for
   an option.

   After mergemaster(8) is done with the system files you will be
   prompted for other options. mergemaster(8) may ask if you want to
   rebuild the password file and will finish up with an option to
   remove left-over temporary files.

     --------------------------------------------------------------

    23.4.11.2. Manual Update

   If you wish to do the update manually, however, you cannot just
   copy over the files from /usr/src/etc to /etc and have it work.
   Some of these files must be !S:installed!" first. This is because
   the /usr/src/etc directory is not a copy of what your /etc
   directory should look like. In addition, there are files that
   should be in /etc that are not in /usr/src/etc.

   If you are using mergemaster(8) (as recommended), you can skip
   forward to the next section.

   The simplest way to do this by hand is to install the files into a
   new directory, and then work through them looking for differences.

     Backup Your Existing /etcAlthough, in theory, nothing is going
     to touch this directory automatically, it is always better to be
     sure. So copy your existing /etc directory somewhere safe.
     Something like:

 # cp -Rp /etc /etc.old

     -R does a recursive copy, -p preserves times, ownerships on
     files and suchlike.

   You need to build a dummy set of directories to install the new
   /etc and other files into. /var/tmp/root is a reasonable choice,
   and there are a number of subdirectories required under this as
   well.

 # mkdir /var/tmp/root
 # cd /usr/src/etc
 # make DESTDIR=/var/tmp/root distrib-dirs distribution

   This will build the necessary directory structure and install the
   files. A lot of the subdirectories that have been created under
   /var/tmp/root are empty and should be deleted. The simplest way to
   do this is to:

 # cd /var/tmp/root
 # find -d . -type d | xargs rmdir 2>/dev/null

   This will remove all empty directories. (Standard error is
   redirected to /dev/null to prevent the warnings about the
   directories that are not empty.)

   /var/tmp/root now contains all the files that should be placed in
   appropriate locations below /. You now have to go through each of
   these files, determining how they differ with your existing files.

   Note that some of the files that will have been installed in
   /var/tmp/root have a leading !S:.!". At the time of writing the
   only files like this are shell startup files in /var/tmp/root/ and
   /var/tmp/root/root/, although there may be others (depending on
   when you are reading this). Make sure you use ls -a to catch them.

   The simplest way to do this is to use diff(1) to compare the two
   files:

 # diff /etc/shells /var/tmp/root/etc/shells

   This will show you the differences between your /etc/shells file
   and the new /var/tmp/root/etc/shells file. Use these to decide
   whether to merge in changes that you have made or whether to copy
   over your old file.

     Name the New Root Directory (/var/tmp/root) with a Time Stamp,
     so You Can Easily Compare Differences Between Versions:
     Frequently rebuilding the world means that you have to update
     /etc frequently as well, which can be a bit of a chore.

     You can speed this process up by keeping a copy of the last set
     of changed files that you merged into /etc. The following
     procedure gives one idea of how to do this.

      1. Make the world as normal. When you want to update /etc and
         the other directories, give the target directory a name
         based on the current date. If you were doing this on the
         14th of February 1998 you could do the following:

 # mkdir /var/tmp/root-19980214
 # cd /usr/src/etc
 # make DESTDIR=/var/tmp/root-19980214 \
     distrib-dirs distribution

      2. Merge in the changes from this directory as outlined above.

         Do not remove the /var/tmp/root-19980214 directory when you
         have finished.

      3. When you have downloaded the latest version of the source
         and remade it, follow step 1. This will give you a new
         directory, which might be called /var/tmp/root-19980221 (if
         you wait a week between doing updates).

      4. You can now see the differences that have been made in the
         intervening week using diff(1) to create a recursive diff
         between the two directories:

 # cd /var/tmp
 # diff -r root-19980214 root-19980221

         Typically, this will be a much smaller set of differences
         than those between /var/tmp/root-19980221/etc and /etc.
         Because the set of differences is smaller, it is easier to
         migrate those changes across into your /etc directory.

      5. You can now remove the older of the two /var/tmp/root-*
         directories:

 # rm -rf /var/tmp/root-19980214

      6. Repeat this process every time you need to merge in changes
         to /etc.

     You can use date(1) to automate the generation of the directory
     names:

 # mkdir /var/tmp/root-`date "+%Y%m%d"`

     --------------------------------------------------------------

  23.4.12. Rebooting

   You are now done. After you have verified that everything appears
   to be in the right place you can reboot the system. A simple
   shutdown(8) should do it:

 # shutdown -r now

     --------------------------------------------------------------

  23.4.13. Finished

   You should now have successfully upgraded your FreeBSD system.
   Congratulations.

   If things went slightly wrong, it is easy to rebuild a particular
   piece of the system. For example, if you accidentally deleted
   /etc/magic as part of the upgrade or merge of /etc, the file(1)
   command will stop working. In this case, the fix would be to run:

 # cd /usr/src/usr.bin/file
 # make all install

     --------------------------------------------------------------

  23.4.14. Questions

   23.4.14.1. Do I need to re-make the world for every change?

   23.4.14.2.

   23.4.14.3. Can I remove /usr/obj when I have finished?

   23.4.14.4. Can interrupted builds be resumed?

   23.4.14.5. How can I speed up making the world?

   23.4.14.6. What do I do if something goes wrong?

   23.4.14.1. Do I need to re-make the world for every change?

   There is no easy answer to this one, as it depends on the nature
   of the change. For example, if you just ran CVSup, and it has
   shown the following files as being updated:

 src/games/cribbage/instr.c
 src/games/sail/pl_main.c
 src/release/sysinstall/config.c
 src/release/sysinstall/media.c
 src/share/mk/bsd.port.mk

   it probably is not worth rebuilding the entire world. You could
   just go to the appropriate sub-directories and make all install,
   and that's about it. But if something major changed, for example
   src/lib/libc/stdlib then you should either re-make the world, or
   at least those parts of it that are statically linked (as well as
   anything else you might have added that is statically linked).

   At the end of the day, it is your call. You might be happy
   re-making the world every fortnight say, and let changes
   accumulate over that fortnight. Or you might want to re-make just
   those things that have changed, and be confident you can spot all
   the dependencies.

   And, of course, this all depends on how often you want to upgrade,
   and whether you are tracking FreeBSD-STABLE or FreeBSD-CURRENT.

   23.4.14.2.

   My compile failed with lots of signal 11 (or other signal number)
   errors. What has happened?

   This is normally indicative of hardware problems. (Re)making the
   world is an effective way to stress test your hardware, and will
   frequently throw up memory problems. These normally manifest
   themselves as the compiler mysteriously dying on receipt of
   strange signals.

   A sure indicator of this is if you can restart the make and it
   dies at a different point in the process.

   In this instance there is little you can do except start swapping
   around the components in your machine to determine which one is
   failing.

   23.4.14.3. Can I remove /usr/obj when I have finished?

   The short answer is yes.

   /usr/obj contains all the object files that were produced during
   the compilation phase. Normally, one of the first steps in the
   make buildworld process is to remove this directory and start
   afresh. In this case, keeping /usr/obj around after you have
   finished makes little sense, and will free up a large chunk of
   disk space (currently about 340 MB).

   However, if you know what you are doing you can have make
   buildworld skip this step. This will make subsequent builds run
   much faster, since most of sources will not need to be recompiled.
   The flip side of this is that subtle dependency problems can creep
   in, causing your build to fail in odd ways. This frequently
   generates noise on the FreeBSD mailing lists, when one person
   complains that their build has failed, not realizing that it is
   because they have tried to cut corners.

   23.4.14.4. Can interrupted builds be resumed?

   This depends on how far through the process you got before you
   found a problem.

   In general (and this is not a hard and fast rule) the make
   buildworld process builds new copies of essential tools (such as
   gcc(1), and make(1)) and the system libraries. These tools and
   libraries are then installed. The new tools and libraries are then
   used to rebuild themselves, and are installed again. The entire
   system (now including regular user programs, such as ls(1) or
   grep(1)) is then rebuilt with the new system files.

   If you are at the last stage, and you know it (because you have
   looked through the output that you were storing) then you can
   (fairly safely) do:

 !K fix the problem !K
 # cd /usr/src
 # make -DNO_CLEAN all

   This will not undo the work of the previous make buildworld.

   If you see the message:

 --------------------------------------------------------------
 Building everything..
 --------------------------------------------------------------

   in the make buildworld output then it is probably fairly safe to
   do so.

   If you do not see that message, or you are not sure, then it is
   always better to be safe than sorry, and restart the build from
   scratch.

   23.4.14.5. How can I speed up making the world?

   * Run in single user mode.

   * Put the /usr/src and /usr/obj directories on separate file
     systems held on separate disks. If possible, put these disks on
     separate disk controllers.

   * Better still, put these file systems across multiple disks using
     the ccd(4) (concatenated disk driver) device.

   * Turn off profiling (set !S:NO_PROFILE=true!" in /etc/make.conf).
     You almost certainly do not need it.

   * Also in /etc/make.conf, set CFLAGS to something like -O -pipe.
     The optimization -O2 is much slower, and the optimization
     difference between -O and -O2 is normally negligible. -pipe lets
     the compiler use pipes rather than temporary files for
     communication, which saves disk access (at the expense of
     memory).

   * Pass the -jn option to make(1) to run multiple processes in
     parallel. This usually helps regardless of whether you have a
     single or a multi processor machine.

   * The file system holding /usr/src can be mounted (or remounted)
     with the noatime option. This prevents the file system from
     recording the file access time. You probably do not need this
     information anyway.

 # mount -u -o noatime /usr/src

       A:uS:iThe example assumes /usr/src is on its own file system.
       If it is not (if it is a part of /usr for example) then you
       will need to use that file system mount point, and not
       /usr/src.

   * The file system holding /usr/obj can be mounted (or remounted)
     with the async option. This causes disk writes to happen
     asynchronously. In other words, the write completes immediately,
     and the data is written to the disk a few seconds later. This
     allows writes to be clustered together, and can be a dramatic
     performance boost.

       A:uS:iKeep in mind that this option makes your file system
       more fragile. With this option there is an increased chance
       that, should power fail, the file system will be in an
       unrecoverable state when the machine restarts.

       If /usr/obj is the only thing on this file system then it is
       not a problem. If you have other, valuable data on the same
       file system then ensure your backups are fresh before you
       enable this option.

 # mount -u -o async /usr/obj

       A:uS:iAs above, if /usr/obj is not on its own file system,
       replace it in the example with the name of the appropriate
       mount point.

   23.4.14.6. What do I do if something goes wrong?

   Make absolutely sure your environment has no extraneous cruft from
   earlier builds. This is simple enough.

 # chflags -R noschg /usr/obj/usr
 # rm -rf /usr/obj/usr
 # cd /usr/src
 # make cleandir
 # make cleandir

   Yes, make cleandir really should be run twice.

   Then restart the whole process, starting with make buildworld.

   If you still have problems, send the error and the output of uname
   -a to FreeBSD general questions P:l>> 1/4 1/2 * 3/4A. Be prepared
   to answer other questions about your setup!

     --------------------------------------------------------------

23.5. Tracking for Multiple Machines

   Contributed by Mike Meyer.

   If you have multiple machines that you want to track the same
   source tree, then having all of them download sources and rebuild
   everything seems like a waste of resources: disk space, network
   bandwidth, and CPU cycles. It is, and the solution is to have one
   machine do most of the work, while the rest of the machines mount
   that work via NFS. This section outlines a method of doing so.

     --------------------------------------------------------------

  23.5.1. Preliminaries

   First, identify a set of machines that is going to run the same
   set of binaries, which we will call a build set. Each machine can
   have a custom kernel, but they will be running the same userland
   binaries. From that set, choose a machine to be the build machine.
   It is going to be the machine that the world and kernel are built
   on. Ideally, it should be a fast machine that has sufficient spare
   CPU to run make buildworld and make buildkernel. You will also
   want to choose a machine to be the test machine, which will test
   software updates before they are put into production. This must be
   a machine that you can afford to have down for an extended period
   of time. It can be the build machine, but need not be.

   All the machines in this build set need to mount /usr/obj and
   /usr/src from the same machine, and at the same point. Ideally,
   those are on two different drives on the build machine, but they
   can be NFS mounted on that machine as well. If you have multiple
   build sets, /usr/src should be on one build machine, and NFS
   mounted on the rest.

   Finally make sure that /etc/make.conf on all the machines in the
   build set agrees with the build machine. That means that the build
   machine must build all the parts of the base system that any
   machine in the build set is going to install. Also, each build
   machine should have its kernel name set with KERNCONF in
   /etc/make.conf, and the build machine should list them all in
   KERNCONF, listing its own kernel first. The build machine must
   have the kernel configuration files for each machine in
   /usr/src/sys/arch/conf if it is going to build their kernels.

     --------------------------------------------------------------

  23.5.2. The Base System

   Now that all that is done, you are ready to build everything.
   Build the kernel and world as described in uU 23.4.7.2 ,` on the
   build machine, but do not install anything. After the build has
   finished, go to the test machine, and install the kernel you just
   built. If this machine mounts /usr/src and /usr/obj via NFS, when
   you reboot to single user you will need to enable the network and
   mount them. The easiest way to do this is to boot to multi-user,
   then run shutdown now to go to single user mode. Once there, you
   can install the new kernel and world and run mergemaster just as
   you normally would. When done, reboot to return to normal
   multi-user operations for this machine.

   After you are certain that everything on the test machine is
   working properly, use the same procedure to install the new
   software on each of the other machines in the build set.

     --------------------------------------------------------------

  23.5.3. Ports

   The same ideas can be used for the ports tree. The first critical
   step is mounting /usr/ports from the same machine to all the
   machines in the build set. You can then set up /etc/make.conf
   properly to share distfiles. You should set DISTDIR to a common
   shared directory that is writable by whichever user root is mapped
   to by your NFS mounts. Each machine should set WRKDIRPREFIX to a
   local build directory. Finally, if you are going to be building
   and distributing packages, you should set PACKAGES to a directory
   similar to DISTDIR.

                            IV. -oo,o^3qDEGT

   FreeBSD NOTOCUR@-oO/
   1/4s-ax-a-o^3Q"IYENI|bDEG-a(R)A:-`a-a-o-oo,o|o/-aA
   3/4^1CURCUR-a-oS:@.~"t^2I!A^3o"C,^3^1,`YEN]S:tCURF!G

     * S:C,|CDEGd-^3qDEGT

     * PPP (c)M PPPoE

     * ^1qCURlP:lYENo

     * DEGo|ae-oo,o|o/-aAu{|!

     * " 3/4CURoAd-

     * "a:YENL-a-oP:iP:YEN-oo,oYENDAD

   ^3o"C,^3^1,`NOTOAAy+-z|b>>YnNOTd,e(R)AE-a-o(R)EOA 1/2
   3/4\YENI-a-o!C
   +-zCUR-L->>Yn"I.O-S(c)w-a-oP:P:S:C,"OAA-a!ACUR]CUR-L->>Yn+-N^3o"C,^3^1,`YENth^3!AA-a^1LCURS:<<aCUR~+-N
   FreeBSD YENI|b-oo,oAo^1OCURU!C

   CUR-o(R)eYENO/?y

   24. Serial Communications

   25. PPP and SLIP

   26. ^1qCURlP:lYENo

   27. Network Servers

   28. " 3/4CURoAd-

   29. -oo,oP:iP:YEN 1/2mYEN\(c)D-

     --------------------------------------------------------------

                     ^3^1 24. Serial Communications

24.1. Synopsis

   UNIX has always had support for serial communications. In fact,
   the very first UNIX machines relied on serial lines for user input
   and output. Things have changed a lot from the days when the
   average !S:terminal!" consisted of a 10-character-per-second
   serial printer and a keyboard. This chapter will cover some of the
   ways in which FreeBSD uses serial communications.

   After reading this chapter, you will know:

     * How to connect terminals to your FreeBSD system.

     * How to use a modem to dial out to remote hosts.

     * How to allow remote users to login to your system with a
       modem.

     * How to boot your system from a serial console.

   Before reading this chapter, you should:

     * Know how to configure and install a new kernel (uU 8 ^3^1).

     * Understand UNIX permissions and processes (uU 3 ^3^1).

     * Have access to the technical manual for the serial hardware
       (modem or multi-port card) that you would like to use with
       FreeBSD.

     --------------------------------------------------------------

24.2. Introduction

  24.2.1. Terminology

   bps

           Bits per Second !X!X the rate at which data is transmitted

   DTE

           Data Terminal Equipment !X!X for example, your computer

   DCE

           Data Communications Equipment !X!X your modem

   RS-232

           EIA standard for hardware serial communications

   When talking about communications data rates, this section does
   not use the term !S:baud!". Baud refers to the number of
   electrical state transitions that may be made in a period of time,
   while !S:bps!" (bits per second) is the correct term to use (at
   least it does not seem to bother the curmudgeons quite as much).

     --------------------------------------------------------------

  24.2.2. Cables and Ports

   To connect a modem or terminal to your FreeBSD system, you will
   need a serial port on your computer and the proper cable to
   connect to your serial device. If you are already familiar with
   your hardware and the cable it requires, you can safely skip this
   section.

     --------------------------------------------------------------

    24.2.2.1. Cables

   There are several different kinds of serial cables. The two most
   common types for our purposes are null-modem cables and standard
   (!S:straight!") RS-232 cables. The documentation for your hardware
   should describe the type of cable required.

     --------------------------------------------------------------

      24.2.2.1.1. Null-modem Cables

   A null-modem cable passes some signals, such as !S:Signal
   Ground!", straight through, but switches other signals. For
   example, the !S:Transmitted Data!" pin on one end goes to the
   !S:Received Data!" pin on the other end.

   You can also construct your own null-modem cable for use with
   terminals (e.g., for quality purposes). This table shows the
   RS-232C signals and the pin numbers on a DB-25 connector. Note
   that the standard also calls for a straight-through pin 1 to pin 1
   Protective Ground line, but it is often omitted. Some terminals
   work OK using only pins 2, 3 and 7, while others require different
   configurations than the examples shown below.

   -ai(R)ae 24-1. DB-25 to DB-25 Null-Modem Cable

   Signal       Pin #                         Pin #       Signal      
   SG           7           connects to       7           SG          
   TD           2           connects to       3           RD          
   RD           3           connects to       2           TD          
   RTS          4           connects to       5           CTS         
   CTS          5           connects to       4           RTS         
   DTR          20          connects to       6           DSR         
   DTR          20          connects to       8           DCD         
   DSR          6           connects to       20          DTR         
   DCD          8           connects to       20          DTR         

   Here are two other schemes more common nowadays.

   -ai(R)ae 24-2. DB-9 to DB-9 Null-Modem Cable

   Signal       Pin #                         Pin #       Signal      
   RD           2           connects to       3           TD          
   TD           3           connects to       2           RD          
   DTR          4           connects to       6           DSR         
   DTR          4           connects to       1           DCD         
   SG           5           connects to       5           SG          
   DSR          6           connects to       4           DTR         
   DCD          1           connects to       4           DTR         
   RTS          7           connects to       8           CTS         
   CTS          8           connects to       7           RTS         

   -ai(R)ae 24-3. DB-9 to DB-25 Null-Modem Cable

   Signal       Pin #                         Pin #       Signal      
   RD           2           connects to       2           TD          
   TD           3           connects to       3           RD          
   DTR          4           connects to       6           DSR         
   DTR          4           connects to       8           DCD         
   SG           5           connects to       7           SG          
   DSR          6           connects to       20          DTR         
   DCD          1           connects to       20          DTR         
   RTS          7           connects to       5           CTS         
   CTS          8           connects to       4           RTS         

     -a`: When one pin at one end connects to a pair of pins at the
     other end, it is usually implemented with one short wire between
     the pair of pins in their connector and a long wire to the other
     single pin.

   The above designs seems to be the most popular. In another
   variation (explained in the book RS-232 Made Easy) SG connects to
   SG, TD connects to RD, RTS and CTS connect to DCD, DTR connects to
   DSR, and vice-versa.

     --------------------------------------------------------------

      24.2.2.1.2. Standard RS-232C Cables

   A standard serial cable passes all of the RS-232C signals straight
   through. That is, the !S:Transmitted Data!" pin on one end of the
   cable goes to the !S:Transmitted Data!" pin on the other end. This
   is the type of cable to use to connect a modem to your FreeBSD
   system, and is also appropriate for some terminals.

     --------------------------------------------------------------

    24.2.2.2. Ports

   Serial ports are the devices through which data is transferred
   between the FreeBSD host computer and the terminal. This section
   describes the kinds of ports that exist and how they are addressed
   in FreeBSD.

     --------------------------------------------------------------

      24.2.2.2.1. Kinds of Ports

   Several kinds of serial ports exist. Before you purchase or
   construct a cable, you need to make sure it will fit the ports on
   your terminal and on the FreeBSD system.

   Most terminals will have DB-25 ports. Personal computers,
   including PCs running FreeBSD, will have DB-25 or DB-9 ports. If
   you have a multiport serial card for your PC, you may have RJ-12
   or RJ-45 ports.

   See the documentation that accompanied the hardware for
   specifications on the kind of port in use. A visual inspection of
   the port often works too.

     --------------------------------------------------------------

      24.2.2.2.2. Port Names

   In FreeBSD, you access each serial port through an entry in the
   /dev directory. There are two different kinds of entries:

     * Call-in ports are named /dev/ttydN where N is the port number,
       starting from zero. Generally, you use the call-in port for
       terminals. Call-in ports require that the serial line assert
       the data carrier detect (DCD) signal to work correctly.

     * Call-out ports are named /dev/cuadN. You usually do not use
       the call-out port for terminals, just for modems. You may use
       the call-out port if the serial cable or the terminal does not
       support the carrier detect signal.

         -a`: Call-out ports are named /dev/cuaaN in FreeBSD 5.X and
         older.

   If you have connected a terminal to the first serial port (COM1 in
   MS-DOS), then you will use /dev/ttyd0 to refer to the terminal. If
   the terminal is on the second serial port (also known as COM2),
   use /dev/ttyd1, and so forth.

     --------------------------------------------------------------

  24.2.3. Kernel Configuration

   FreeBSD supports four serial ports by default. In the MS-DOS
   world, these are known as COM1, COM2, COM3, and COM4. FreeBSD
   currently supports !S:dumb!" multiport serial interface cards,
   such as the BocaBoard 1008 and 2016, as well as more intelligent
   multi-port cards such as those made by Digiboard and Stallion
   Technologies. However, the default kernel only looks for the
   standard COM ports.

   To see if your kernel recognizes any of your serial ports, watch
   for messages while the kernel is booting, or use the /sbin/dmesg
   command to replay the kernel's boot messages. In particular, look
   for messages that start with the characters sio.

     '-L-YENU:: To view just the messages that have the word sio, use
     the command:

 # /sbin/dmesg | grep 'sio'

   For example, on a system with four serial ports, these are the
   serial-port specific kernel boot messages:

 sio0 at 0x3f8-0x3ff irq 4 on isa
 sio0: type 16550A
 sio1 at 0x2f8-0x2ff irq 3 on isa
 sio1: type 16550A
 sio2 at 0x3e8-0x3ef irq 5 on isa
 sio2: type 16550A
 sio3 at 0x2e8-0x2ef irq 9 on isa
 sio3: type 16550A

   If your kernel does not recognize all of your serial ports, you
   will probably need to configure your kernel in the
   /boot/device.hints file. You can also comment-out or completely
   remove lines for devices you do not have.

   On FreeBSD 4.X you have to edit your kernel configuration file.
   For detailed information on configuring your kernel, please see uU
   8 ^3^1. The relevant device lines would look like this:

 device          sio0    at isa? port IO_COM1 irq 4
 device          sio1    at isa? port IO_COM2 irq 3
 device          sio2    at isa? port IO_COM3 irq 5
 device          sio3    at isa? port IO_COM4 irq 9

   Please refer to the sio(4) manual page for more information on
   serial ports and multiport boards configuration. Be careful if you
   are using a configuration file that was previously used for a
   different version of FreeBSD because the device flags and the
   syntax have changed between versions.

     -a`: port IO_COM1 is a substitution for port 0x3f8, IO_COM2 is
     0x2f8, IO_COM3 is 0x3e8, and IO_COM4 is 0x2e8, which are fairly
     common port addresses for their respective serial ports;
     interrupts 4, 3, 5, and 9 are fairly common interrupt request
     lines. Also note that regular serial ports cannot share
     interrupts on ISA-bus PCs (multiport boards have on-board
     electronics that allow all the 16550A's on the board to share
     one or two interrupt request lines).

     --------------------------------------------------------------

  24.2.4. Device Special Files

   Most devices in the kernel are accessed through !S:device special
   files!", which are located in the /dev directory. The sio devices
   are accessed through the /dev/ttydN (dial-in) and /dev/cuadN
   (call-out) devices. FreeBSD also provides initialization devices
   (/dev/ttydN.init and /dev/cuadN.init on FreeBSD 6.X, /dev/ttyidN
   and /dev/cuaidN on FreeBSD 5.X and older) and locking devices
   (/dev/ttydN.lock and /dev/cuadN.lock on FreeBSD 6.X, /dev/ttyldN
   and /dev/cualdN on FreeBSD 5.X and older). The initialization
   devices are used to initialize communications port parameters each
   time a port is opened, such as crtscts for modems which use
   RTS/CTS signaling for flow control. The locking devices are used
   to lock flags on ports to prevent users or programs changing
   certain parameters; see the manual pages termios(4), sio(4), and
   stty(1) for information on the terminal settings, locking and
   initializing devices, and setting terminal options, respectively.

     --------------------------------------------------------------

    24.2.4.1. Making Device Special Files

     -a`: FreeBSD 5.0 includes the devfs(5) filesystem which
     automatically creates device nodes as needed. If you are running
     a version of FreeBSD with devfs enabled then you can safely skip
     this section.

   A shell script called MAKEDEV in the /dev directory manages the
   device special files. To use MAKEDEV to make dial-up device
   special files for COM1 (port 0), cd to /dev and issue the command
   MAKEDEV ttyd0. Likewise, to make dial-up device special files for
   COM2 (port 1), use MAKEDEV ttyd1.

   MAKEDEV not only creates the /dev/ttydN device special files, but
   also the /dev/cuaaN, /dev/cuaiaN, /dev/cualaN, /dev/ttyldN, and
   /dev/ttyidN nodes.

   After making new device special files, be sure to check the
   permissions on the files (especially the /dev/cua* files) to make
   sure that only users who should have access to those device
   special files can read and write on them !X!X you probably do not
   want to allow your average user to use your modems to dial-out.
   The default permissions on the /dev/cua* files should be
   sufficient:

 crw-rw----    1 uucp     dialer    28, 129 Feb 15 14:38 /dev/cuaa1
 crw-rw----    1 uucp     dialer    28, 161 Feb 15 14:38 /dev/cuaia1
 crw-rw----    1 uucp     dialer    28, 193 Feb 15 14:38 /dev/cuala1

   These permissions allow the user uucp and users in the group
   dialer to use the call-out devices.

     --------------------------------------------------------------

  24.2.5. Serial Port Configuration

   The ttydN (or cuadN) device is the regular device you will want to
   open for your applications. When a process opens the device, it
   will have a default set of terminal I/O settings. You can see
   these settings with the command

 # stty -a -f /dev/ttyd1

   When you change the settings to this device, the settings are in
   effect until the device is closed. When it is reopened, it goes
   back to the default set. To make changes to the default set, you
   can open and adjust the settings of the !S:initial state!" device.
   For example, to turn on CLOCAL mode, 8 bit communication, and
   XON/XOFF flow control by default for ttyd5, type:

 # stty -f /dev/ttyd5.init clocal cs8 ixon ixoff

   System-wide initialization of the serial devices is controlled in
   /etc/rc.d/serial. This file affects the default settings of serial
   devices.

     -a`: On FreeBSD 4.X, system-wide initialization of the serial
     devices is controlled in /etc/rc.serial.

   To prevent certain settings from being changed by an application,
   make adjustments to the !S:lock state!" device. For example, to
   lock the speed of ttyd5 to 57600 bps, type:

 # stty -f /dev/ttyd5.lock 57600

   Now, an application that opens ttyd5 and tries to change the speed
   of the port will be stuck with 57600 bps.

   Naturally, you should make the initial state and lock state
   devices writable only by the root account.

     --------------------------------------------------------------

24.3. Terminals

   Contributed by Sean Kelly.

   Terminals provide a convenient and low-cost way to access your
   FreeBSD system when you are not at the computer's console or on a
   connected network. This section describes how to use terminals
   with FreeBSD.

     --------------------------------------------------------------

  24.3.1. Uses and Types of Terminals

   The original UNIX systems did not have consoles. Instead, people
   logged in and ran programs through terminals that were connected
   to the computer's serial ports. It is quite similar to using a
   modem and terminal software to dial into a remote system to do
   text-only work.

   Today's PCs have consoles capable of high quality graphics, but
   the ability to establish a login session on a serial port still
   exists in nearly every UNIX style operating system today; FreeBSD
   is no exception. By using a terminal attached to an unused serial
   port, you can log in and run any text program that you would
   normally run on the console or in an xterm window in the X Window
   System.

   For the business user, you can attach many terminals to a FreeBSD
   system and place them on your employees' desktops. For a home
   user, a spare computer such as an older IBM PC or a Macintosh can
   be a terminal wired into a more powerful computer running FreeBSD.
   You can turn what might otherwise be a single-user computer into a
   powerful multiple user system.

   For FreeBSD, there are three kinds of terminals:

     * Dumb terminals

     * PCs acting as terminals

     * X terminals

   The remaining subsections describe each kind.

     --------------------------------------------------------------

    24.3.1.1. Dumb Terminals

   Dumb terminals are specialized pieces of hardware that let you
   connect to computers over serial lines. They are called !S:dumb!"
   because they have only enough computational power to display,
   send, and receive text. You cannot run any programs on them. It is
   the computer to which you connect them that has all the power to
   run text editors, compilers, email, games, and so forth.

   There are hundreds of kinds of dumb terminals made by many
   manufacturers, including Digital Equipment Corporation's VT-100
   and Wyse's WY-75. Just about any kind will work with FreeBSD. Some
   high-end terminals can even display graphics, but only certain
   software packages can take advantage of these advanced features.

   Dumb terminals are popular in work environments where workers do
   not need access to graphical applications such as those provided
   by the X Window System.

     --------------------------------------------------------------

    24.3.1.2. PCs Acting as Terminals

   If a dumb terminal has just enough ability to display, send, and
   receive text, then certainly any spare personal computer can be a
   dumb terminal. All you need is the proper cable and some terminal
   emulation software to run on the computer.

   Such a configuration is popular in homes. For example, if your
   spouse is busy working on your FreeBSD system's console, you can
   do some text-only work at the same time from a less powerful
   personal computer hooked up as a terminal to the FreeBSD system.

     --------------------------------------------------------------

    24.3.1.3. X Terminals

   X terminals are the most sophisticated kind of terminal available.
   Instead of connecting to a serial port, they usually connect to a
   network like Ethernet. Instead of being relegated to text-only
   applications, they can display any X application.

   We introduce X terminals just for the sake of completeness.
   However, this chapter does not cover setup, configuration, or use
   of X terminals.

     --------------------------------------------------------------

  24.3.2. Configuration

   This section describes what you need to configure on your FreeBSD
   system to enable a login session on a terminal. It assumes you
   have already configured your kernel to support the serial port to
   which the terminal is connected!X!Xand that you have connected it.

   Recall from uU 12 ^3^1 that the init process is responsible for
   all process control and initialization at system startup. One of
   the tasks performed by init is to read the /etc/ttys file and
   start a getty process on the available terminals. The getty
   process is responsible for reading a login name and starting the
   login program.

   Thus, to configure terminals for your FreeBSD system the following
   steps should be taken as root:

    1. Add a line to /etc/ttys for the entry in the /dev directory
       for the serial port if it is not already there.

    2. Specify that /usr/libexec/getty be run on the port, and
       specify the appropriate getty type from the /etc/gettytab
       file.

    3. Specify the default terminal type.

    4. Set the port to !S:on.!"

    5. Specify whether the port should be !S:secure.!"

    6. Force init to reread the /etc/ttys file.

   As an optional step, you may wish to create a custom getty type
   for use in step 2 by making an entry in /etc/gettytab. This
   chapter does not explain how to do so; you are encouraged to see
   the gettytab(5) and the getty(8) manual pages for more
   information.

     --------------------------------------------------------------

    24.3.2.1. Adding an Entry to /etc/ttys

   The /etc/ttys file lists all of the ports on your FreeBSD system
   where you want to allow logins. For example, the first virtual
   console ttyv0 has an entry in this file. You can log in on the
   console using this entry. This file also contains entries for the
   other virtual consoles, serial ports, and pseudo-ttys. For a
   hardwired terminal, just list the serial port's /dev entry without
   the /dev part (for example, /dev/ttyv0 would be listed as ttyv0).

   A default FreeBSD install includes an /etc/ttys file with support
   for the first four serial ports: ttyd0 through ttyd3. If you are
   attaching a terminal to one of those ports, you do not need to add
   another entry.

   1/2d"O 24-1. Adding Terminal Entries to /etc/ttys

   Suppose we would like to connect two terminals to the system: a
   Wyse-50 and an old 286 IBM PC running Procomm terminal software
   emulating a VT-100 terminal. We connect the Wyse to the second
   serial port and the 286 to the sixth serial port (a port on a
   multiport serial card). The corresponding entries in the /etc/ttys
   file would look like this:

 ttyd1(1)  "/usr/libexec/getty std.38400"(2)  wy50(3)  on(4)  insecure(5)
 ttyd5   "/usr/libexec/getty std.19200"  vt100  on  insecure
          

   (1)
           The first field normally specifies the name of the
           terminal special file as it is found in /dev.
   (2)
           The second field is the command to execute for this line,
           which is usually getty(8). getty initializes and opens the
           line, sets the speed, prompts for a user name and then
           executes the login(1) program.

           The getty program accepts one (optional) parameter on its
           command line, the getty type. A getty type configures
           characteristics on the terminal line, like bps rate and
           parity. The getty program reads these characteristics from
           the file /etc/gettytab.

           The file /etc/gettytab contains lots of entries for
           terminal lines both old and new. In almost all cases, the
           entries that start with the text std will work for
           hardwired terminals. These entries ignore parity. There is
           a std entry for each bps rate from 110 to 115200. Of
           course, you can add your own entries to this file. The
           gettytab(5) manual page provides more information.

           When setting the getty type in the /etc/ttys file, make
           sure that the communications settings on the terminal
           match.

           For our example, the Wyse-50 uses no parity and connects
           at 38400 bps. The 286 PC uses no parity and connects at
           19200 bps.

   (3)
           The third field is the type of terminal usually connected
           to that tty line. For dial-up ports, unknown or dialup is
           typically used in this field since users may dial up with
           practically any type of terminal or software. For
           hardwired terminals, the terminal type does not change, so
           you can put a real terminal type from the termcap(5)
           database file in this field.

           For our example, the Wyse-50 uses the real terminal type
           while the 286 PC running Procomm will be set to emulate at
           VT-100.

   (4)
           The fourth field specifies if the port should be enabled.
           Putting on here will have the init process start the
           program in the second field, getty. If you put off in this
           field, there will be no getty, and hence no logins on the
           port.
   (5)
           The final field is used to specify whether the port is
           secure. Marking a port as secure means that you trust it
           enough to allow the root account (or any account with a
           user ID of 0) to login from that port. Insecure ports do
           not allow root logins. On an insecure port, users must
           login from unprivileged accounts and then use su(1) or a
           similar mechanism to gain superuser privileges.

           It is highly recommended that you use !S:insecure!" even
           for terminals that are behind locked doors. It is quite
           easy to login and use su if you need superuser privileges.

     --------------------------------------------------------------

    24.3.2.2. Force init to Reread /etc/ttys

   After making the necessary changes to the /etc/ttys file you
   should send a SIGHUP (hangup) signal to the init process to force
   it to re-read its configuration file. For example:

 # kill -HUP 1

     -a`: init is always the first process run on a system, therefore
     it will always have PID 1.

   If everything is set up correctly, all cables are in place, and
   the terminals are powered up, then a getty process should be
   running on each terminal and you should see login prompts on your
   terminals at this point.

     --------------------------------------------------------------

  24.3.3. Troubleshooting Your Connection

   Even with the most meticulous attention to detail, something could
   still go wrong while setting up a terminal. Here is a list of
   symptoms and some suggested fixes.

     --------------------------------------------------------------

    24.3.3.1. No Login Prompt Appears

   Make sure the terminal is plugged in and powered up. If it is a
   personal computer acting as a terminal, make sure it is running
   terminal emulation software on the correct serial port.

   Make sure the cable is connected firmly to both the terminal and
   the FreeBSD computer. Make sure it is the right kind of cable.

   Make sure the terminal and FreeBSD agree on the bps rate and
   parity settings. If you have a video display terminal, make sure
   the contrast and brightness controls are turned up. If it is a
   printing terminal, make sure paper and ink are in good supply.

   Make sure that a getty process is running and serving the
   terminal. For example, to get a list of running getty processes
   with ps, type:

 # ps -axww|grep getty

   You should see an entry for the terminal. For example, the
   following display shows that a getty is running on the second
   serial port ttyd1 and is using the std.38400 entry in
   /etc/gettytab:

 22189  d1  Is+    0:00.03 /usr/libexec/getty std.38400 ttyd1

   If no getty process is running, make sure you have enabled the
   port in /etc/ttys. Also remember to run kill -HUP 1 after
   modifying the ttys file.

   If the getty process is running but the terminal still does not
   display a login prompt, or if it displays a prompt but will not
   allow you to type, your terminal or cable may not support hardware
   handshaking. Try changing the entry in /etc/ttys from std.38400 to
   3wire.38400 remember to run kill -HUP 1 after modifying
   /etc/ttys). The 3wire entry is similar to std, but ignores
   hardware handshaking. You may need to reduce the baud rate or
   enable software flow control when using 3wire to prevent buffer
   overflows.

     --------------------------------------------------------------

    24.3.3.2. If Garbage Appears Instead of a Login Prompt

   Make sure the terminal and FreeBSD agree on the bps rate and
   parity settings. Check the getty processes to make sure the
   correct getty type is in use. If not, edit /etc/ttys and run kill
   -HUP 1.

     --------------------------------------------------------------

    24.3.3.3. Characters Appear Doubled; the Password Appears When Typed

   Switch the terminal (or the terminal emulation software) from
   !S:half duplex!" or !S:local echo!" to !S:full duplex.!"

     --------------------------------------------------------------

24.4. Dial-in Service

   Contributed by Guy Helmer. Additions by Sean Kelly.

   Configuring your FreeBSD system for dial-in service is very
   similar to connecting terminals except that you are dealing with
   modems instead of terminals.

     --------------------------------------------------------------

  24.4.1. External vs. Internal Modems

   External modems seem to be more convenient for dial-up, because
   external modems often can be semi-permanently configured via
   parameters stored in non-volatile RAM and they usually provide
   lighted indicators that display the state of important RS-232
   signals. Blinking lights impress visitors, but lights are also
   very useful to see whether a modem is operating properly.

   Internal modems usually lack non-volatile RAM, so their
   configuration may be limited only to setting DIP switches. If your
   internal modem has any signal indicator lights, it is probably
   difficult to view the lights when the system's cover is in place.

     --------------------------------------------------------------

    24.4.1.1. Modems and Cables

   If you are using an external modem, then you will of course need
   the proper cable. A standard RS-232C serial cable should suffice
   as long as all of the normal signals are wired:

   -ai(R)ae 24-4. Signal Names

   Acronyms Names                                                     
   RD       Received Data                                             
   TD       Transmitted Data                                          
   DTR      Data Terminal Ready                                       
   DSR      Data Set Ready                                            
   DCD      Data Carrier Detect (RS-232's Received Line Signal        
            Detector)                                           
   SG       Signal Ground                                             
   RTS      Request to Send                                           
   CTS      Clear to Send                                             

   FreeBSD needs the RTS and CTS signals for flow control at speeds
   above 2400 bps, the CD signal to detect when a call has been
   answered or the line has been hung up, and the DTR signal to reset
   the modem after a session is complete. Some cables are wired
   without all of the needed signals, so if you have problems, such
   as a login session not going away when the line hangs up, you may
   have a problem with your cable.

   Like other UNIX like operating systems, FreeBSD uses the hardware
   signals to find out when a call has been answered or a line has
   been hung up and to hangup and reset the modem after a call.
   FreeBSD avoids sending commands to the modem or watching for
   status reports from the modem. If you are familiar with connecting
   modems to PC-based bulletin board systems, this may seem awkward.

     --------------------------------------------------------------

  24.4.2. Serial Interface Considerations

   FreeBSD supports NS8250-, NS16450-, NS16550-, and NS16550A-based
   EIA RS-232C (CCITT V.24) communications interfaces. The 8250 and
   16450 devices have single-character buffers. The 16550 device
   provides a 16-character buffer, which allows for better system
   performance. (Bugs in plain 16550's prevent the use of the
   16-character buffer, so use 16550A's if possible). Because
   single-character-buffer devices require more work by the operating
   system than the 16-character-buffer devices, 16550A-based serial
   interface cards are much preferred. If the system has many active
   serial ports or will have a heavy load, 16550A-based cards are
   better for low-error-rate communications.

     --------------------------------------------------------------

  24.4.3. Quick Overview

   As with terminals, init spawns a getty process for each configured
   serial port for dial-in connections. For example, if a modem is
   attached to /dev/ttyd0, the command ps ax might show this:

  4850 ??  I      0:00.09 /usr/libexec/getty V19200 ttyd0

   When a user dials the modem's line and the modems connect, the CD
   (Carrier Detect) line is reported by the modem. The kernel notices
   that carrier has been detected and completes getty's open of the
   port. getty sends a login: prompt at the specified initial line
   speed. getty watches to see if legitimate characters are received,
   and, in a typical configuration, if it finds junk (probably due to
   the modem's connection speed being different than getty's speed),
   getty tries adjusting the line speeds until it receives reasonable
   characters.

   After the user enters his/her login name, getty executes
   /usr/bin/login, which completes the login by asking for the user's
   password and then starting the user's shell.

     --------------------------------------------------------------

  24.4.4. Configuration Files

   There are three system configuration files in the /etc directory
   that you will probably need to edit to allow dial-up access to
   your FreeBSD system. The first, /etc/gettytab, contains
   configuration information for the /usr/libexec/getty daemon.
   Second, /etc/ttys holds information that tells /sbin/init what tty
   devices should have getty processes running on them. Lastly, you
   can place port initialization commands in the /etc/rc.d/serial
   script.

   There are two schools of thought regarding dial-up modems on UNIX.
   One group likes to configure their modems and systems so that no
   matter at what speed a remote user dials in, the local
   computer-to-modem RS-232 interface runs at a locked speed. The
   benefit of this configuration is that the remote user always sees
   a system login prompt immediately. The downside is that the system
   does not know what a user's true data rate is, so full-screen
   programs like Emacs will not adjust their screen-painting methods
   to make their response better for slower connections.

   The other school configures their modems' RS-232 interface to vary
   its speed based on the remote user's connection speed. For
   example, V.32bis (14.4 Kbps) connections to the modem might make
   the modem run its RS-232 interface at 19.2 Kbps, while 2400 bps
   connections make the modem's RS-232 interface run at 2400 bps.
   Because getty does not understand any particular modem's
   connection speed reporting, getty gives a login: message at an
   initial speed and watches the characters that come back in
   response. If the user sees junk, it is assumed that they know they
   should press the Enter key until they see a recognizable prompt.
   If the data rates do not match, getty sees anything the user types
   as !S:junk!", tries going to the next speed and gives the login:
   prompt again. This procedure can continue ad nauseam, but normally
   only takes a keystroke or two before the user sees a good prompt.
   Obviously, this login sequence does not look as clean as the
   former !S:locked-speed!" method, but a user on a low-speed
   connection should receive better interactive response from
   full-screen programs.

   This section will try to give balanced configuration information,
   but is biased towards having the modem's data rate follow the
   connection rate.

     --------------------------------------------------------------

    24.4.4.1. /etc/gettytab

   /etc/gettytab is a termcap(5)-style file of configuration
   information for getty(8). Please see the gettytab(5) manual page
   for complete information on the format of the file and the list of
   capabilities.

     --------------------------------------------------------------

      24.4.4.1.1. Locked-speed Config

   If you are locking your modem's data communications rate at a
   particular speed, you probably will not need to make any changes
   to /etc/gettytab.

     --------------------------------------------------------------

      24.4.4.1.2. Matching-speed Config

   You will need to set up an entry in /etc/gettytab to give getty
   information about the speeds you wish to use for your modem. If
   you have a 2400 bps modem, you can probably use the existing D2400
   entry.

 #
 # Fast dialup terminals, 2400/1200/300 rotary (can start either way)
 #
 D2400|d2400|Fast-Dial-2400:\
         :nx=D1200:tc=2400-baud:
 3|D1200|Fast-Dial-1200:\
         :nx=D300:tc=1200-baud:
 5|D300|Fast-Dial-300:\
         :nx=D2400:tc=300-baud:

   If you have a higher speed modem, you will probably need to add an
   entry in /etc/gettytab; here is an entry you could use for a
   14.4 Kbps modem with a top interface speed of 19.2 Kbps:

 #
 # Additions for a V.32bis Modem
 #
 um|V300|High Speed Modem at 300,8-bit:\
         :nx=V19200:tc=std.300:
 un|V1200|High Speed Modem at 1200,8-bit:\
         :nx=V300:tc=std.1200:
 uo|V2400|High Speed Modem at 2400,8-bit:\
         :nx=V1200:tc=std.2400:
 up|V9600|High Speed Modem at 9600,8-bit:\
         :nx=V2400:tc=std.9600:
 uq|V19200|High Speed Modem at 19200,8-bit:\
         :nx=V9600:tc=std.19200:

   This will result in 8-bit, no parity connections.

   The example above starts the communications rate at 19.2 Kbps (for
   a V.32bis connection), then cycles through 9600 bps (for V.32),
   2400 bps, 1200 bps, 300 bps, and back to 19.2 Kbps. Communications
   rate cycling is implemented with the nx= (!S:next table!")
   capability. Each of the lines uses a tc= (!S:table continuation!")
   entry to pick up the rest of the !S:standard!" settings for a
   particular data rate.

   If you have a 28.8 Kbps modem and/or you want to take advantage of
   compression on a 14.4 Kbps modem, you need to use a higher
   communications rate than 19.2 Kbps. Here is an example of a
   gettytab entry starting a 57.6 Kbps:

 #
 # Additions for a V.32bis or V.34 Modem
 # Starting at 57.6 Kbps
 #
 vm|VH300|Very High Speed Modem at 300,8-bit:\
         :nx=VH57600:tc=std.300:
 vn|VH1200|Very High Speed Modem at 1200,8-bit:\
         :nx=VH300:tc=std.1200:
 vo|VH2400|Very High Speed Modem at 2400,8-bit:\
         :nx=VH1200:tc=std.2400:
 vp|VH9600|Very High Speed Modem at 9600,8-bit:\
         :nx=VH2400:tc=std.9600:
 vq|VH57600|Very High Speed Modem at 57600,8-bit:\
         :nx=VH9600:tc=std.57600:

   If you have a slow CPU or a heavily loaded system and do not have
   16550A-based serial ports, you may receive !S:sio!" !S:silo!"
   errors at 57.6 Kbps.

     --------------------------------------------------------------

    24.4.4.2. /etc/ttys

   Configuration of the /etc/ttys file was covered in  1/2d"O 24-1.
   Configuration for modems is similar but we must pass a different
   argument to getty and specify a different terminal type. The
   general format for both locked-speed and matching-speed
   configurations is:

 ttyd0   "/usr/libexec/getty xxx"   dialup on

   The first item in the above line is the device special file for
   this entry !X!X ttyd0 means /dev/ttyd0 is the file that this getty
   will be watching. The second item, "/usr/libexec/getty xxx" (xxx
   will be replaced by the initial gettytab capability) is the
   process init will run on the device. The third item, dialup, is
   the default terminal type. The fourth parameter, on, indicates to
   init that the line is operational. There can be a fifth parameter,
   secure, but it should only be used for terminals which are
   physically secure (such as the system console).

   The default terminal type (dialup in the example above) may depend
   on local preferences. dialup is the traditional default terminal
   type on dial-up lines so that users may customize their login
   scripts to notice when the terminal is dialup and automatically
   adjust their terminal type. However, the author finds it easier at
   his site to specify vt102 as the default terminal type, since the
   users just use VT102 emulation on their remote systems.

   After you have made changes to /etc/ttys, you may send the init
   process a HUP signal to re-read the file. You can use the command

 # kill -HUP 1

   to send the signal. If this is your first time setting up the
   system, you may want to wait until your modem(s) are properly
   configured and connected before signaling init.

     --------------------------------------------------------------

      24.4.4.2.1. Locked-speed Config

   For a locked-speed configuration, your ttys entry needs to have a
   fixed-speed entry provided to getty. For a modem whose port speed
   is locked at 19.2 Kbps, the ttys entry might look like this:

 ttyd0   "/usr/libexec/getty std.19200"   dialup on

   If your modem is locked at a different data rate, substitute the
   appropriate value for std.speed instead of std.19200. Make sure
   that you use a valid type listed in /etc/gettytab.

     --------------------------------------------------------------

      24.4.4.2.2. Matching-speed Config

   In a matching-speed configuration, your ttys entry needs to
   reference the appropriate beginning !S:auto-baud!" (sic) entry in
   /etc/gettytab. For example, if you added the above suggested entry
   for a matching-speed modem that starts at 19.2 Kbps (the gettytab
   entry containing the V19200 starting point), your ttys entry might
   look like this:

 ttyd0   "/usr/libexec/getty V19200"   dialup on

     --------------------------------------------------------------

    24.4.4.3. /etc/rc.d/serial

   High-speed modems, like V.32, V.32bis, and V.34 modems, need to
   use hardware (RTS/CTS) flow control. You can add stty commands to
   /etc/rc.d/serial to set the hardware flow control flag in the
   FreeBSD kernel for the modem ports.

   For example to set the termios flag crtscts on serial port #1's
   (COM2) dial-in and dial-out initialization devices, the following
   lines could be added to /etc/rc.d/serial:

 # Serial port initial configuration
 stty -f /dev/ttyd1.init crtscts
 stty -f /dev/cuad1.init crtscts

     --------------------------------------------------------------

  24.4.5. Modem Settings

   If you have a modem whose parameters may be permanently set in
   non-volatile RAM, you will need to use a terminal program (such as
   Telix under MS-DOS or tip under FreeBSD) to set the parameters.
   Connect to the modem using the same communications speed as the
   initial speed getty will use and configure the modem's
   non-volatile RAM to match these requirements:

     * CD asserted when connected

     * DTR asserted for operation; dropping DTR hangs up line and
       resets modem

     * CTS transmitted data flow control

     * Disable XON/XOFF flow control

     * RTS received data flow control

     * Quiet mode (no result codes)

     * No command echo

   Please read the documentation for your modem to find out what
   commands and/or DIP switch settings you need to give it.

   For example, to set the above parameters on a U.S. Robotics(R)
   Sportster(R) 14,400 external modem, one could give these commands
   to the modem:

 ATZ
 AT&C1&D2&H1&I0&R2&W

   You might also want to take this opportunity to adjust other
   settings in the modem, such as whether it will use V.42bis and/or
   MNP5 compression.

   The U.S. Robotics Sportster 14,400 external modem also has some
   DIP switches that need to be set; for other modems, perhaps you
   can use these settings as an example:

     * Switch 1: UP !X!X DTR Normal

     * Switch 2: N/A (Verbal Result Codes/Numeric Result Codes)

     * Switch 3: UP !X!X Suppress Result Codes

     * Switch 4: DOWN !X!X No echo, offline commands

     * Switch 5: UP !X!X Auto Answer

     * Switch 6: UP !X!X Carrier Detect Normal

     * Switch 7: UP !X!X Load NVRAM Defaults

     * Switch 8: N/A (Smart Mode/Dumb Mode)

   Result codes should be disabled/suppressed for dial-up modems to
   avoid problems that can occur if getty mistakenly gives a login:
   prompt to a modem that is in command mode and the modem echoes the
   command or returns a result code. This sequence can result in a
   extended, silly conversation between getty and the modem.

     --------------------------------------------------------------

    24.4.5.1. Locked-speed Config

   For a locked-speed configuration, you will need to configure the
   modem to maintain a constant modem-to-computer data rate
   independent of the communications rate. On a U.S. Robotics
   Sportster 14,400 external modem, these commands will lock the
   modem-to-computer data rate at the speed used to issue the
   commands:

 ATZ
 AT&B1&W

     --------------------------------------------------------------

    24.4.5.2. Matching-speed Config

   For a variable-speed configuration, you will need to configure
   your modem to adjust its serial port data rate to match the
   incoming call rate. On a U.S. Robotics Sportster 14,400 external
   modem, these commands will lock the modem's error-corrected data
   rate to the speed used to issue the commands, but allow the serial
   port rate to vary for non-error-corrected connections:

 ATZ
 AT&B2&W

     --------------------------------------------------------------

    24.4.5.3. Checking the Modem's Configuration

   Most high-speed modems provide commands to view the modem's
   current operating parameters in a somewhat human-readable fashion.
   On the U.S. Robotics Sportster 14,400 external modems, the command
   ATI5 displays the settings that are stored in the non-volatile
   RAM. To see the true operating parameters of the modem (as
   influenced by the modem's DIP switch settings), use the commands
   ATZ and then ATI4.

   If you have a different brand of modem, check your modem's manual
   to see how to double-check your modem's configuration parameters.

     --------------------------------------------------------------

  24.4.6. Troubleshooting

   Here are a few steps you can follow to check out the dial-up modem
   on your system.

     --------------------------------------------------------------

    24.4.6.1. Checking Out the FreeBSD System

   Hook up your modem to your FreeBSD system, boot the system, and,
   if your modem has status indication lights, watch to see whether
   the modem's DTR indicator lights when the login: prompt appears on
   the system's console !X!X if it lights up, that should mean that
   FreeBSD has started a getty process on the appropriate
   communications port and is waiting for the modem to accept a call.

   If the DTR indicator does not light, login to the FreeBSD system
   through the console and issue a ps ax to see if FreeBSD is trying
   to run a getty process on the correct port. You should see lines
   like these among the processes displayed:

   114 ??  I      0:00.10 /usr/libexec/getty V19200 ttyd0
   115 ??  I      0:00.10 /usr/libexec/getty V19200 ttyd1

   If you see something different, like this:

   114 d0  I      0:00.10 /usr/libexec/getty V19200 ttyd0

   and the modem has not accepted a call yet, this means that getty
   has completed its open on the communications port. This could
   indicate a problem with the cabling or a mis-configured modem,
   because getty should not be able to open the communications port
   until CD (carrier detect) has been asserted by the modem.

   If you do not see any getty processes waiting to open the desired
   ttydN port, double-check your entries in /etc/ttys to see if there
   are any mistakes there. Also, check the log file /var/log/messages
   to see if there are any log messages from init or getty regarding
   any problems. If there are any messages, triple-check the
   configuration files /etc/ttys and /etc/gettytab, as well as the
   appropriate device special files /dev/ttydN, for any mistakes,
   missing entries, or missing device special files.

     --------------------------------------------------------------

    24.4.6.2. Try Dialing In

   Try dialing into the system; be sure to use 8 bits, no parity, and
   1 stop bit on the remote system. If you do not get a prompt right
   away, or get garbage, try pressing Enter about once per second. If
   you still do not see a login: prompt after a while, try sending a
   BREAK. If you are using a high-speed modem to do the dialing, try
   dialing again after locking the dialing modem's interface speed
   (via AT&B1 on a U.S. Robotics Sportster modem, for example).

   If you still cannot get a login: prompt, check /etc/gettytab again
   and double-check that

     * The initial capability name specified in /etc/ttys for the
       line matches a name of a capability in /etc/gettytab

     * Each nx= entry matches another gettytab capability name

     * Each tc= entry matches another gettytab capability name

   If you dial but the modem on the FreeBSD system will not answer,
   make sure that the modem is configured to answer the phone when
   DTR is asserted. If the modem seems to be configured correctly,
   verify that the DTR line is asserted by checking the modem's
   indicator lights (if it has any).

   If you have gone over everything several times and it still does
   not work, take a break and come back to it later. If it still does
   not work, perhaps you can send an electronic mail message to the
   FreeBSD general questions P:l>> 1/4 1/2 * 3/4A describing your
   modem and your problem, and the good folks on the list will try to
   help.

     --------------------------------------------------------------

24.5. Dial-out Service

   The following are tips for getting your host to be able to connect
   over the modem to another computer. This is appropriate for
   establishing a terminal session with a remote host.

   This is useful to log onto a BBS.

   This kind of connection can be extremely helpful to get a file on
   the Internet if you have problems with PPP. If you need to FTP
   something and PPP is broken, use the terminal session to FTP it.
   Then use zmodem to transfer it to your machine.

     --------------------------------------------------------------

  24.5.1. My Stock Hayes Modem Is Not Supported, What Can I Do?

   Actually, the manual page for tip is out of date. There is a
   generic Hayes dialer already built in. Just use at=hayes in your
   /etc/remote file.

   The Hayes driver is not smart enough to recognize some of the
   advanced features of newer modems!X!Xmessages like BUSY, NO
   DIALTONE, or CONNECT 115200 will just confuse it. You should turn
   those messages off when you use tip (using ATX0&W).

   Also, the dial timeout for tip is 60 seconds. Your modem should
   use something less, or else tip will think there is a
   communication problem. Try ATS7=45&W.

     -a`: As shipped, tip does not yet support Hayes modems fully.
     The solution is to edit the file tipconf.h in the directory
     /usr/src/usr.bin/tip/tip. Obviously you need the source
     distribution to do this.

     Edit the line #define HAYES 0 to #define HAYES 1. Then make and
     make install. Everything works nicely after that.

     --------------------------------------------------------------

  24.5.2. How Am I Expected to Enter These AT Commands?

   Make what is called a !S:direct!" entry in your /etc/remote file.
   For example, if your modem is hooked up to the first serial port,
   /dev/cuad0, then put in the following line:

 cuad0:dv=/dev/cuad0:br#19200:pa=none

   Use the highest bps rate your modem supports in the br capability.
   Then, type tip cuad0 and you will be connected to your modem.

   Or use cu as root with the following command:

 # cu -lline -sspeed

   line is the serial port (e.g./dev/cuad0) and speed is the speed
   (e.g.57600). When you are done entering the AT commands hit ~. to
   exit.

     --------------------------------------------------------------

  24.5.3. The @ Sign for the pn Capability Does Not Work!

   The @ sign in the phone number capability tells tip to look in
   /etc/phones for a phone number. But the @ sign is also a special
   character in capability files like /etc/remote. Escape it with a
   backslash:

 pn=\@

     --------------------------------------------------------------

  24.5.4. How Can I Dial a Phone Number on the Command Line?

   Put what is called a !S:generic!" entry in your /etc/remote file.
   For example:

 tip115200|Dial any phone number at 115200 bps:\
         :dv=/dev/cuad0:br#115200:at=hayes:pa=none:du:
 tip57600|Dial any phone number at 57600 bps:\
         :dv=/dev/cuad0:br#57600:at=hayes:pa=none:du:

   Then you can do things like:

 # tip -115200 5551234

   If you prefer cu over tip, use a generic cu entry:

 cu115200|Use cu to dial any number at 115200bps:\
         :dv=/dev/cuad1:br#57600:at=hayes:pa=none:du:

   and type:

 # cu 5551234 -s 115200

     --------------------------------------------------------------

  24.5.5. Do I Have to Type in the bps Rate Every Time I Do That?

   Put in an entry for tip1200 or cu1200, but go ahead and use
   whatever bps rate is appropriate with the br capability. tip
   thinks a good default is 1200 bps which is why it looks for a
   tip1200 entry. You do not have to use 1200 bps, though.

     --------------------------------------------------------------

  24.5.6. I Access a Number of Hosts Through a Terminal Server

   Rather than waiting until you are connected and typing CONNECT
   <host> each time, use tip's cm capability. For example, these
   entries in /etc/remote:

 pain|pain.deep13.com|Forrester's machine:\
         :cm=CONNECT pain\n:tc=deep13:
 muffin|muffin.deep13.com|Frank's machine:\
         :cm=CONNECT muffin\n:tc=deep13:
 deep13:Gizmonics Institute terminal server:\
         :dv=/dev/cuad2:br#38400:at=hayes:du:pa=none:pn=5551234:

   will let you type tip pain or tip muffin to connect to the hosts
   pain or muffin, and tip deep13 to get to the terminal server.

     --------------------------------------------------------------

  24.5.7. Can Tip Try More Than One Line for Each Site?

   This is often a problem where a university has several modem lines
   and several thousand students trying to use them.

   Make an entry for your university in /etc/remote and use @ for the
   pn capability:

 big-university:\
         :pn=\@:tc=dialout
 dialout:\
         :dv=/dev/cuad3:br#9600:at=courier:du:pa=none:

   Then, list the phone numbers for the university in /etc/phones:

 big-university 5551111
 big-university 5551112
 big-university 5551113
 big-university 5551114

   tip will try each one in the listed order, then give up. If you
   want to keep retrying, run tip in a while loop.

     --------------------------------------------------------------

  24.5.8. Why Do I Have to Hit Ctrl+P Twice to Send Ctrl+P Once?

   Ctrl+P is the default !S:force!" character, used to tell tip that
   the next character is literal data. You can set the force
   character to any other character with the ~s escape, which means
   !S:set a variable.!"

   Type ~sforce=single-char followed by a newline. single-char is any
   single character. If you leave out single-char, then the force
   character is the nul character, which you can get by typing Ctrl+2
   or Ctrl+Space. A pretty good value for single-char is
   Shift+Ctrl+6, which is only used on some terminal servers.

   You can have the force character be whatever you want by
   specifying the following in your $HOME/.tiprc file:

 force=<single-char>

     --------------------------------------------------------------

  24.5.9. Suddenly Everything I Type Is in Upper Case??

   You must have pressed Ctrl+A, tip's !S:raise character,!"
   specially designed for people with broken caps-lock keys. Use ~s
   as above and set the variable raisechar to something reasonable.
   In fact, you can set it to the same as the force character, if you
   never expect to use either of these features.

   Here is a sample .tiprc file perfect for Emacs users who need to
   type Ctrl+2 and Ctrl+A a lot:

 force=^^
 raisechar=^^

   The ^^ is Shift+Ctrl+6.

     --------------------------------------------------------------

  24.5.10. How Can I Do File Transfers with tip?

   If you are talking to another UNIX system, you can send and
   receive files with ~p (put) and ~t (take). These commands run cat
   and echo on the remote system to accept and send files. The syntax
   is:

   ~p local-file [remote-file]

   ~t remote-file [local-file]

   There is no error checking, so you probably should use another
   protocol, like zmodem.

     --------------------------------------------------------------

  24.5.11. How Can I Run zmodem with tip?

   To receive files, start the sending program on the remote end.
   Then, type ~C rz to begin receiving them locally.

   To send files, start the receiving program on the remote end.
   Then, type ~C sz files to send them to the remote system.

     --------------------------------------------------------------

24.6. Setting Up the Serial Console

   Contributed by Kazutaka YOKOTA. Based on a document by Bill Paul.

     --------------------------------------------------------------

  24.6.1. Introduction

   FreeBSD has the ability to boot on a system with only a dumb
   terminal on a serial port as a console. Such a configuration
   should be useful for two classes of people: system administrators
   who wish to install FreeBSD on machines that have no keyboard or
   monitor attached, and developers who want to debug the kernel or
   device drivers.

   As described in uU 12 ^3^1, FreeBSD employs a three stage
   bootstrap. The first two stages are in the boot block code which
   is stored at the beginning of the FreeBSD slice on the boot disk.
   The boot block will then load and run the boot loader
   (/boot/loader) as the third stage code.

   In order to set up the serial console you must configure the boot
   block code, the boot loader code and the kernel.

     --------------------------------------------------------------

  24.6.2. Serial Console Configuration, Terse Version

   This section assumes that you are using the default setup and just
   want a fast overview of setting up the serial console.

    1. Connect the serial cable to COM1 and the controlling terminal.

    2. To see all boot messages on the serial console, issue the
       following command while logged in as the superuser:

 # echo 'console="comconsole"' >> /boot/loader.conf

    3. Edit /etc/ttys and change off to on and dialup to vt100 for
       the ttyd0 entry. Otherwise a password will not be required to
       connect via the serial console, resulting in a potential
       security hole.

    4. Reboot the system to see if the changes took effect.

   If a different configuration is required, a more in depth
   configuration explanation exists in uU 24.6.3 ,`.

     --------------------------------------------------------------

  24.6.3. Serial Console Configuration

    1. Prepare a serial cable.

       You will need either a null-modem cable or a standard serial
       cable and a null-modem adapter. See uU 24.2.2 ,` for a
       discussion on serial cables.

    2. Unplug your keyboard.

       Most PC systems probe for the keyboard during the Power-On
       Self-Test (POST) and will generate an error if the keyboard is
       not detected. Some machines complain loudly about the lack of
       a keyboard and will not continue to boot until it is plugged
       in.

       If your computer complains about the error, but boots anyway,
       then you do not have to do anything special. (Some machines
       with Phoenix BIOS installed merely say !S:Keyboard failed!"
       and continue to boot normally.)

       If your computer refuses to boot without a keyboard attached
       then you will have to configure the BIOS so that it ignores
       this error (if it can). Consult your motherboard's manual for
       details on how to do this.

         '-L-YENU:: Set the keyboard to !S:Not installed!" in the
         BIOS setup. You will still be able to use your keyboard. All
         this does is tell the BIOS not to probe for a keyboard at
         power-on. Your BIOS should not complain if the keyboard is
         absent. You can leave the keyboard plugged in even with this
         flag set to !S:Not installed!" and the keyboard will still
         work.

         -a`: If your system has a PS/2(R) mouse, chances are very
         good that you may have to unplug your mouse as well as your
         keyboard. This is because PS/2 mice share some hardware with
         the keyboard and leaving the mouse plugged in can fool the
         keyboard probe into thinking the keyboard is still there. It
         is said that a Gateway 2000 Pentium 90 MHz system with an
         AMI BIOS that behaves this way. In general, this is not a
         problem since the mouse is not much good without the
         keyboard anyway.

    3. Plug a dumb terminal into COM1 (sio0).

       If you do not have a dumb terminal, you can use an old PC/XT
       with a modem program, or the serial port on another UNIX box.
       If you do not have a COM1 (sio0), get one. At this time, there
       is no way to select a port other than COM1 for the boot blocks
       without recompiling the boot blocks. If you are already using
       COM1 for another device, you will have to temporarily remove
       that device and install a new boot block and kernel once you
       get FreeBSD up and running. (It is assumed that COM1 will be
       available on a file/compute/terminal server anyway; if you
       really need COM1 for something else (and you cannot switch
       that something else to COM2 (sio1)), then you probably should
       not even be bothering with all this in the first place.)

    4. Make sure the configuration file of your kernel has
       appropriate flags set for COM1 (sio0).

       Relevant flags are:

            0x10

                    Enables console support for this unit. The other
                    console flags are ignored unless this is set.
                    Currently, at most one unit can have console
                    support; the first one (in config file order)
                    with this flag set is preferred. This option
                    alone will not make the serial port the console.
                    Set the following flag or use the -h option
                    described below, together with this flag.

            0x20

                    Forces this unit to be the console (unless there
                    is another higher priority console), regardless
                    of the -h option discussed below. The flag 0x20
                    must be used together with the 0x10 flag.

            0x40

                    Reserves this unit (in conjunction with 0x10) and
                    makes the unit unavailable for normal access. You
                    should not set this flag to the serial port unit
                    which you want to use as the serial console. The
                    only use of this flag is to designate the unit
                    for kernel remote debugging. See The Developer's
                    Handbook for more information on remote
                    debugging.

                      -a`: In FreeBSD 4.0 or later the semantics of
                      the flag 0x40 are slightly different and there
                      is another flag to specify a serial port for
                      remote debugging.

       Example:

 device sio0 at isa? port IO_COM1 flags 0x10 irq 4

       See the sio(4) manual page for more details.

       If the flags were not set, you need to run UserConfig (on a
       different console) or recompile the kernel.

    5. Create boot.config in the root directory of the a partition on
       the boot drive.

       This file will instruct the boot block code how you would like
       to boot the system. In order to activate the serial console,
       you need one or more of the following options!X!Xif you want
       multiple options, include them all on the same line:

            -h

                    Toggles internal and serial consoles. You can use
                    this to switch console devices. For instance, if
                    you boot from the internal (video) console, you
                    can use -h to direct the boot loader and the
                    kernel to use the serial port as its console
                    device. Alternatively, if you boot from the
                    serial port, you can use the -h to tell the boot
                    loader and the kernel to use the video display as
                    the console instead.

            -D

                    Toggles single and dual console configurations.
                    In the single configuration the console will be
                    either the internal console (video display) or
                    the serial port, depending on the state of the -h
                    option above. In the dual console configuration,
                    both the video display and the serial port will
                    become the console at the same time, regardless
                    of the state of the -h option. However, note that
                    the dual console configuration takes effect only
                    during the boot block is running. Once the boot
                    loader gets control, the console specified by the
                    -h option becomes the only console.

            -P

                    Makes the boot block probe the keyboard. If no
                    keyboard is found, the -D and -h options are
                    automatically set.

                      -a`: Due to space constraints in the current
                      version of the boot blocks, the -P option is
                      capable of detecting extended keyboards only.
                      Keyboards with less than 101 keys (and without
                      F11 and F12 keys) may not be detected.
                      Keyboards on some laptop computers may not be
                      properly found because of this limitation. If
                      this is the case with your system, you have to
                      abandon using the -P option. Unfortunately
                      there is no workaround for this problem.

       Use either the -P option to select the console automatically,
       or the -h option to activate the serial console.

       You may include other options described in boot(8) as well.

       The options, except for -P, will be passed to the boot loader
       (/boot/loader). The boot loader will determine which of the
       internal video or the serial port should become the console by
       examining the state of the -h option alone. This means that if
       you specify the -D option but not the -h option in
       /boot.config, you can use the serial port as the console only
       during the boot block; the boot loader will use the internal
       video display as the console.

    6. Boot the machine.

       When you start your FreeBSD box, the boot blocks will echo the
       contents of /boot.config to the console. For example:

 /boot.config: -P
 Keyboard: no

       The second line appears only if you put -P in /boot.config and
       indicates presence/absence of the keyboard. These messages go
       to either serial or internal console, or both, depending on
       the option in /boot.config.

       Options                     Message goes to                    
       none                        internal console                   
       -h                          serial console                     
       -D                          serial and internal consoles       
       -Dh                         serial and internal consoles       
       -P, keyboard present        internal console                   
       -P, keyboard absent         serial console                     

       After the above messages, there will be a small pause before
       the boot blocks continue loading the boot loader and before
       any further messages printed to the console. Under normal
       circumstances, you do not need to interrupt the boot blocks,
       but you may want to do so in order to make sure things are set
       up correctly.

       Hit any key, other than Enter, at the console to interrupt the
       boot process. The boot blocks will then prompt you for further
       action. You should now see something like:

 >> FreeBSD/i386 BOOT
 Default: 0:ad(0,a)/boot/loader
 boot:

       Verify the above message appears on either the serial or
       internal console or both, according to the options you put in
       /boot.config. If the message appears in the correct console,
       hit Enter to continue the boot process.

       If you want the serial console but you do not see the prompt
       on the serial terminal, something is wrong with your settings.
       In the meantime, you enter -h and hit Enter/Return (if
       possible) to tell the boot block (and then the boot loader and
       the kernel) to choose the serial port for the console. Once
       the system is up, go back and check what went wrong.

   After the boot loader is loaded and you are in the third stage of
   the boot process you can still switch between the internal console
   and the serial console by setting appropriate environment
   variables in the boot loader. See uU 24.6.6 ,`.

     --------------------------------------------------------------

  24.6.4. Summary

   Here is the summary of various settings discussed in this section
   and the console eventually selected.

     --------------------------------------------------------------

    24.6.4.1. Case 1: You Set the Flags to 0x10 for sio0

 device sio0 at isa? port IO_COM1 flags 0x10 irq 4

   Options in          Console during boot  Console during Console in 
   /boot.config        blocks               boot loader    kernel     
   nothing             internal             internal       internal   
   -h                  serial               serial         serial     
   -D                  serial and internal  internal       internal   
   -Dh                 serial and internal  serial         serial     
   -P, keyboard        internal             internal       internal   
   present             
   -P, keyboard absent serial and internal  serial         serial     

     --------------------------------------------------------------

    24.6.4.2. Case 2: You Set the Flags to 0x30 for sio0

 device sio0 at isa? port IO_COM1 flags 0x30 irq 4

   Options in          Console during boot  Console during Console in 
   /boot.config        blocks               boot loader    kernel     
   nothing             internal             internal       serial     
   -h                  serial               serial         serial     
   -D                  serial and internal  internal       serial     
   -Dh                 serial and internal  serial         serial     
   -P, keyboard        internal             internal       serial     
   present             
   -P, keyboard absent serial and internal  serial         serial     

     --------------------------------------------------------------

  24.6.5. Tips for the Serial Console

    24.6.5.1. Setting a Faster Serial Port Speed

   By default, the serial port settings are: 9600 baud, 8 bits, no
   parity, and 1 stop bit. If you wish to change the speed, you need
   to recompile at least the boot blocks. Add the following line to
   /etc/make.conf and compile new boot blocks:

 BOOT_COMCONSOLE_SPEED=19200

   See uU 24.6.5.2 ,` for detailed instructions about building and
   installing new boot blocks.

   If the serial console is configured in some other way than by
   booting with -h, or if the serial console used by the kernel is
   different from the one used by the boot blocks, then you must also
   add the following option to the kernel configuration file and
   compile a new kernel:

 options CONSPEED=19200

     --------------------------------------------------------------

    24.6.5.2. Using Serial Port Other Than sio0 for the Console

   Using a port other than sio0 as the console requires some
   recompiling. If you want to use another serial port for whatever
   reasons, recompile the boot blocks, the boot loader and the kernel
   as follows.

    1. Get the kernel source. (See uU 23 ^3^1)

    2. Edit /etc/make.conf and set BOOT_COMCONSOLE_PORT to the
       address of the port you want to use (0x3F8, 0x2F8, 0x3E8 or
       0x2E8). Only sio0 through sio3 (COM1 through COM4) can be
       used; multiport serial cards will not work. No interrupt
       setting is needed.

    3. Create a custom kernel configuration file and add appropriate
       flags for the serial port you want to use. For example, if you
       want to make sio1 (COM2) the console:

 device sio1 at isa? port IO_COM2 flags 0x10 irq 3

       or

 device sio1 at isa? port IO_COM2 flags 0x30 irq 3

       The console flags for the other serial ports should not be
       set.

    4. Recompile and install the boot blocks and the boot loader:

 # cd /sys/boot
 # make clean
 # make
 # make install

    5. Rebuild and install the kernel.

    6. Write the boot blocks to the boot disk with disklabel(8) and
       boot from the new kernel.

     --------------------------------------------------------------

    24.6.5.3. Entering the DDB Debugger from the Serial Line

   If you wish to drop into the kernel debugger from the serial
   console (useful for remote diagnostics, but also dangerous if you
   generate a spurious BREAK on the serial port!) then you should
   compile your kernel with the following options:

 options BREAK_TO_DEBUGGER
 options DDB

     --------------------------------------------------------------

    24.6.5.4. Getting a Login Prompt on the Serial Console

   While this is not required, you may wish to get a login prompt
   over the serial line, now that you can see boot messages and can
   enter the kernel debugging session through the serial console.
   Here is how to do it.

   Open the file /etc/ttys with an editor and locate the lines:

 ttyd0 "/usr/libexec/getty std.9600" unknown off secure
 ttyd1 "/usr/libexec/getty std.9600" unknown off secure
 ttyd2 "/usr/libexec/getty std.9600" unknown off secure
 ttyd3 "/usr/libexec/getty std.9600" unknown off secure

   ttyd0 through ttyd3 corresponds to COM1 through COM4. Change off
   to on for the desired port. If you have changed the speed of the
   serial port, you need to change std.9600 to match the current
   setting, e.g. std.19200.

   You may also want to change the terminal type from unknown to the
   actual type of your serial terminal.

   After editing the file, you must kill -HUP 1 to make this change
   take effect.

     --------------------------------------------------------------

  24.6.6. Changing Console from the Boot Loader

   Previous sections described how to set up the serial console by
   tweaking the boot block. This section shows that you can specify
   the console by entering some commands and environment variables in
   the boot loader. As the boot loader is invoked at the third stage
   of the boot process, after the boot block, the settings in the
   boot loader will override the settings in the boot block.

     --------------------------------------------------------------

    24.6.6.1. Setting Up the Serial Console

   You can easily specify the boot loader and the kernel to use the
   serial console by writing just one line in /boot/loader.rc:

 set console="comconsole"

   This will take effect regardless of the settings in the boot block
   discussed in the previous section.

   You had better put the above line as the first line of
   /boot/loader.rc so as to see boot messages on the serial console
   as early as possible.

   Likewise, you can specify the internal console as:

 set console="vidconsole"

   If you do not set the boot loader environment variable console,
   the boot loader, and subsequently the kernel, will use whichever
   console indicated by the -h option in the boot block.

   In versions 3.2 or later, you may specify the console in
   /boot/loader.conf.local or /boot/loader.conf, rather than in
   /boot/loader.rc. In this method your /boot/loader.rc should look
   like:

 include /boot/loader.4th
 start

   Then, create /boot/loader.conf.local and put the following line
   there.

 console=comconsole

   or

 console=vidconsole

   See loader.conf(5) for more information.

     -a`: At the moment, the boot loader has no option equivalent to
     the -P option in the boot block, and there is no provision to
     automatically select the internal console and the serial console
     based on the presence of the keyboard.

     --------------------------------------------------------------

    24.6.6.2. Using a Serial Port Other Than sio0 for the Console

   You need to recompile the boot loader to use a serial port other
   than sio0 for the serial console. Follow the procedure described
   in uU 24.6.5.2 ,`.

     --------------------------------------------------------------

  24.6.7. Caveats

   The idea here is to allow people to set up dedicated servers that
   require no graphics hardware or attached keyboards. Unfortunately,
   while most systems will let you boot without a keyboard, there are
   quite a few that will not let you boot without a graphics adapter.
   Machines with AMI BIOSes can be configured to boot with no
   graphics adapter installed simply by changing the !S:graphics
   adapter!" setting in the CMOS configuration to !S:Not installed.!"

   However, many machines do not support this option and will refuse
   to boot if you have no display hardware in the system. With these
   machines, you will have to leave some kind of graphics card
   plugged in, (even if it is just a junky mono board) although you
   will not have to attach a monitor. You might also try installing
   an AMI BIOS.

     --------------------------------------------------------------

                         ^3^1 25. PPP and SLIP

   Restructured, reorganized, and updated by Jim Mock.

25.1. Synopsis

   FreeBSD has a number of ways to link one computer to another. To
   establish a network or Internet connection through a dial-up
   modem, or to allow others to do so through you, requires the use
   of PPP or SLIP. This chapter describes setting up these
   modem-based communication services in detail.

   After reading this chapter, you will know:

     * How to set up user PPP.

     * How to set up kernel PPP.

     * How to set up PPPoE (PPP over Ethernet).

     * How to set up PPPoA (PPP over ATM).

     * How to configure and set up a SLIP client and server.

   Before reading this chapter, you should:

     * Be familiar with basic network terminology.

     * Understand the basics and purpose of a dialup connection and
       PPP and/or SLIP.

   You may be wondering what the main difference is between user PPP
   and kernel PPP. The answer is simple: user PPP processes the
   inbound and outbound data in userland rather than in the kernel.
   This is expensive in terms of copying the data between the kernel
   and userland, but allows a far more feature-rich PPP
   implementation. User PPP uses the tun device to communicate with
   the outside world whereas kernel PPP uses the ppp device.

     -a`: Throughout in this chapter, user PPP will simply be
     referred to as ppp unless a distinction needs to be made between
     it and any other PPP software such as pppd. Unless otherwise
     stated, all of the commands explained in this chapter should be
     executed as root.

     --------------------------------------------------------------

25.2. Using User PPP

   Updated and enhanced by Tom Rhodes. Originally contributed by
   Brian Somers. With input from Nik Clayton, Dirk Fro:mberg, YENB
   Peter Childs.

  25.2.1. User PPP

    25.2.1.1. Assumptions

   This document assumes you have the following:

     * An account with an Internet Service Provider (ISP) which you
       connect to using PPP.

     * You have a modem or other device connected to your system and
       configured correctly which allows you to connect to your ISP.

     * The dial-up number(s) of your ISP.

     * Your login name and password. (Either a regular UNIX style
       login and password pair, or a PAP or CHAP login and password
       pair.)

     * The IP address of one or more name servers. Normally, you will
       be given two IP addresses by your ISP to use for this. If they
       have not given you at least one, then you can use the enable
       dns command in ppp.conf and ppp will set the name servers for
       you. This feature depends on your ISPs PPP implementation
       supporting DNS negotiation.

   The following information may be supplied by your ISP, but is not
   completely necessary:

     * The IP address of your ISP's gateway. The gateway is the
       machine to which you will connect and will be set up as your
       default route. If you do not have this information, we can
       make one up and your ISP's PPP server will tell us the correct
       value when we connect.

       This IP number is referred to as HISADDR by ppp.

     * The netmask you should use. If your ISP has not provided you
       with one, you can safely use 255.255.255.255.

     * If your ISP provides you with a static IP address and
       hostname, you can enter it. Otherwise, we simply let the peer
       assign whatever IP address it sees fit.

   If you do not have any of the required information, contact your
   ISP.

     -a`: Throughout this section, many of the examples showing the
     contents of configuration files are numbered by line. These
     numbers serve to aid in the presentation and discussion only and
     are not meant to be placed in the actual file. Proper
     indentation with tab and space characters is also important.

     --------------------------------------------------------------

    25.2.1.2. Creating PPP Device Nodes

   Under normal circumstances, most users will only need one tun
   device (/dev/tun0). References to tun0 below may be changed to
   tunN where N is any unit number corresponding to your system.

   For FreeBSD installations that do not have devfs(5) enabled
   (FreeBSD 4.X and earlier), the existence of the tun0 device should
   be verified (this is not necessary if devfs(5) is enabled as
   device nodes will be created on demand).

   The easiest way to make sure that the tun0 device is configured
   correctly is to remake the device. To remake the device, do the
   following:

 # cd /dev
 # sh MAKEDEV tun0

   If you need 16 tunnel devices in your kernel, you will need to
   create them. This can be done by executing the following commands:

 # cd /dev
 # sh MAKEDEV tun15

     --------------------------------------------------------------

    25.2.1.3. Automatic PPP Configuration

   Both ppp and pppd (the kernel level implementation of PPP) use the
   configuration files located in the /etc/ppp directory. Examples
   for user ppp can be found in /usr/share/examples/ppp/.

   Configuring ppp requires that you edit a number of files,
   depending on your requirements. What you put in them depends to
   some extent on whether your ISP allocates IP addresses statically
   (i.e., you get given one IP address, and always use that one) or
   dynamically (i.e., your IP address changes each time you connect
   to your ISP).

     --------------------------------------------------------------

      25.2.1.3.1. PPP and Static IP Addresses

   You will need to edit the /etc/ppp/ppp.conf configuration file. It
   should look similar to the example below.

     -a`: Lines that end in a : start in the first column (beginning
     of the line)!X!X all other lines should be indented as shown
     using spaces or tabs.

 1     default:
 2       set log Phase Chat LCP IPCP CCP tun command
 3       ident user-ppp VERSION (built COMPILATIONDATE)
 4       set device /dev/cuaa0
 5       set speed 115200
 6       set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \
 7                 \"\" AT OK-AT-OK ATE1Q0 OK \\dATDT\\T TIMEOUT 40 CONNECT"
 8       set timeout 180
 9       enable dns
 10
 11    provider:
 12      set phone "(123) 456 7890"
 13      set authname foo
 14      set authkey bar
 15      set login "TIMEOUT 10 \"\" \"\" gin:--gin: \\U word: \\P col: ppp"
 16      set timeout 300
 17      set ifaddr x.x.x.x y.y.y.y 255.255.255.255 0.0.0.0
 18      add default HISADDR

   Line 1:

           Identifies the default entry. Commands in this entry are
           executed automatically when ppp is run.

   Line 2:

           Enables logging parameters. When the configuration is
           working satisfactorily, this line should be reduced to
           saying

 set log phase tun

           in order to avoid excessive log file sizes.

   Line 3:

           Tells PPP how to identify itself to the peer. PPP
           identifies itself to the peer if it has any trouble
           negotiating and setting up the link, providing information
           that the peers administrator may find useful when
           investigating such problems.

   Line 4:

           Identifies the device to which the modem is connected.
           COM1 is /dev/cuaa0 and COM2 is /dev/cuaa1.

   Line 5:

           Sets the speed you want to connect at. If 115200 does not
           work (it should with any reasonably new modem), try 38400
           instead.

   Line 6 & 7:

           The dial string. User PPP uses an expect-send syntax
           similar to the chat(8) program. Refer to the manual page
           for information on the features of this language.

           Note that this command continues onto the next line for
           readability. Any command in ppp.conf may do this if the
           last character on the line is a ``\'' character.

   Line 8:

           Sets the idle timeout for the link. 180 seconds is the
           default, so this line is purely cosmetic.

   Line 9:

           Tells PPP to ask the peer to confirm the local resolver
           settings. If you run a local name server, this line should
           be commented out or removed.

   Line 10:

           A blank line for readability. Blank lines are ignored by
           PPP.

   Line 11:

           Identifies an entry for a provider called !S:provider!".
           This could be changed to the name of your ISP so that
           later you can use the load ISP to start the connection.

   Line 12:

           Sets the phone number for this provider. Multiple phone
           numbers may be specified using the colon (:) or pipe
           character (|)as a separator. The difference between the
           two separators is described in ppp(8). To summarize, if
           you want to rotate through the numbers, use a colon. If
           you want to always attempt to dial the first number first
           and only use the other numbers if the first number fails,
           use the pipe character. Always quote the entire set of
           phone numbers as shown.

           You must enclose the phone number in quotation marks (")
           if there is any intention on using spaces in the phone
           number. This can cause a simple, yet subtle error.

   Line 13 & 14:

           Identifies the user name and password. When connecting
           using a UNIX style login prompt, these values are referred
           to by the set login command using the \U and \P variables.
           When connecting using PAP or CHAP, these values are used
           at authentication time.

   Line 15:

           If you are using PAP or CHAP, there will be no login at
           this point, and this line should be commented out or
           removed. See PAP and CHAP authentication for further
           details.

           The login string is of the same chat-like syntax as the
           dial string. In this example, the string works for a
           service whose login session looks like this:

 J. Random Provider
 login: foo
 password: bar
 protocol: ppp

           You will need to alter this script to suit your own needs.
           When you write this script for the first time, you should
           ensure that you have enabled !S:chat!" logging so you can
           determine if the conversation is going as expected.

   Line 16:

           Sets the default idle timeout (in seconds) for the
           connection. Here, the connection will be closed
           automatically after 300 seconds of inactivity. If you
           never want to timeout, set this value to zero or use the
           -ddial command line switch.

   Line 17:

           Sets the interface addresses. The string x.x.x.x should be
           replaced by the IP address that your provider has
           allocated to you. The string y.y.y.y should be replaced by
           the IP address that your ISP indicated for their gateway
           (the machine to which you connect). If your ISP has not
           given you a gateway address, use 10.0.0.2/0. If you need
           to use a !S:guessed!" address, make sure that you create
           an entry in /etc/ppp/ppp.linkup as per the instructions
           for PPP and Dynamic IP addresses. If this line is omitted,
           ppp cannot run in -auto mode.

   Line 18:

           Adds a default route to your ISP's gateway. The special
           word HISADDR is replaced with the gateway address
           specified on line 17. It is important that this line
           appears after line 17, otherwise HISADDR will not yet be
           initialized.

           If you do not wish to run ppp in -auto, this line should
           be moved to the ppp.linkup file.

   It is not necessary to add an entry to ppp.linkup when you have a
   static IP address and are running ppp in -auto mode as your
   routing table entries are already correct before you connect. You
   may however wish to create an entry to invoke programs after
   connection. This is explained later with the sendmail example.

   Example configuration files can be found in the
   /usr/share/examples/ppp/ directory.

     --------------------------------------------------------------

      25.2.1.3.2. PPP and Dynamic IP Addresses

   If your service provider does not assign static IP addresses, ppp
   can be configured to negotiate the local and remote addresses.
   This is done by !S:guessing!" an IP address and allowing ppp to
   set it up correctly using the IP Configuration Protocol (IPCP)
   after connecting. The ppp.conf configuration is the same as PPP
   and Static IP Addresses, with the following change:

 17      set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.255

   Again, do not include the line number, it is just for reference.
   Indentation of at least one space is required.

   Line 17:

           The number after the / character is the number of bits of
           the address that ppp will insist on. You may wish to use
           IP numbers more appropriate to your circumstances, but the
           above example will always work.

           The last argument (0.0.0.0) tells PPP to start
           negotiations using address 0.0.0.0 rather than 10.0.0.1
           and is necessary for some ISPs. Do not use 0.0.0.0 as the
           first argument to set ifaddr as it prevents PPP from
           setting up an initial route in -auto mode.

   If you are not running in -auto mode, you will need to create an
   entry in /etc/ppp/ppp.linkup. ppp.linkup is used after a
   connection has been established. At this point, ppp will have
   assigned the interface addresses and it will now be possible to
   add the routing table entries:

 1     provider:
 2      add default HISADDR

   Line 1:

           On establishing a connection, ppp will look for an entry
           in ppp.linkup according to the following rules: First, try
           to match the same label as we used in ppp.conf. If that
           fails, look for an entry for the IP address of our
           gateway. This entry is a four-octet IP style label. If we
           still have not found an entry, look for the MYADDR entry.

   Line 2:

           This line tells ppp to add a default route that points to
           HISADDR. HISADDR will be replaced with the IP number of
           the gateway as negotiated by the IPCP.

   See the pmdemand entry in the files
   /usr/share/examples/ppp/ppp.conf.sample and
   /usr/share/examples/ppp/ppp.linkup.sample for a detailed example.

     --------------------------------------------------------------

      25.2.1.3.3. Receiving Incoming Calls

   When you configure ppp to receive incoming calls on a machine
   connected to a LAN, you must decide if you wish to forward packets
   to the LAN. If you do, you should allocate the peer an IP number
   from your LAN's subnet, and use the command enable proxy in your
   /etc/ppp/ppp.conf file. You should also confirm that the
   /etc/rc.conf file contains the following:

 gateway_enable="YES"

     --------------------------------------------------------------

      25.2.1.3.4. Which getty?

   Configuring FreeBSD for Dial-up Services provides a good
   description on enabling dial-up services using getty(8).

   An alternative to getty is mgetty, a smarter version of getty
   designed with dial-up lines in mind.

   The advantages of using mgetty is that it actively talks to
   modems, meaning if port is turned off in /etc/ttys then your modem
   will not answer the phone.

   Later versions of mgetty (from 0.99beta onwards) also support the
   automatic detection of PPP streams, allowing your clients
   script-less access to your server.

   Refer to Mgetty and AutoPPP for more information on mgetty.

     --------------------------------------------------------------

      25.2.1.3.5. PPP Permissions

   The ppp command must normally be run as the root user. If however,
   you wish to allow ppp to run in server mode as a normal user by
   executing ppp as described below, that user must be given
   permission to run ppp by adding them to the network group in
   /etc/group.

   You will also need to give them access to one or more sections of
   the configuration file using the allow command:

 allow users fred mary

   If this command is used in the default section, it gives the
   specified users access to everything.

     --------------------------------------------------------------

      25.2.1.3.6. PPP Shells for Dynamic-IP Users

   Create a file called /etc/ppp/ppp-shell containing the following:

 #!/bin/sh
 IDENT=`echo $0 | sed -e 's/^.*-\(.*\)$/\1/'`
 CALLEDAS="$IDENT"
 TTY=`tty`

 if [ x$IDENT = xdialup ]; then
         IDENT=`basename $TTY`
 fi

 echo "PPP for $CALLEDAS on $TTY"
 echo "Starting PPP for $IDENT"

 exec /usr/sbin/ppp -direct $IDENT

   This script should be executable. Now make a symbolic link called
   ppp-dialup to this script using the following commands:

 # ln -s ppp-shell /etc/ppp/ppp-dialup

   You should use this script as the shell for all of your dialup
   users. This is an example from /etc/passwd for a dialup PPP user
   with username pchilds (remember do not directly edit the password
   file, use vipw(8)).

 pchilds:*:1011:300:Peter Childs PPP:/home/ppp:/etc/ppp/ppp-dialup

   Create a /home/ppp directory that is world readable containing the
   following 0 byte files:

 -r--r--r--   1 root     wheel           0 May 27 02:23 .hushlogin
 -r--r--r--   1 root     wheel           0 May 27 02:22 .rhosts

   which prevents /etc/motd from being displayed.

     --------------------------------------------------------------

      25.2.1.3.7. PPP Shells for Static-IP Users

   Create the ppp-shell file as above, and for each account with
   statically assigned IPs create a symbolic link to ppp-shell.

   For example, if you have three dialup customers, fred, sam, and
   mary, that you route class C networks for, you would type the
   following:

 # ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-fred
 # ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-sam
 # ln -s /etc/ppp/ppp-shell /etc/ppp/ppp-mary

   Each of these users dialup accounts should have their shell set to
   the symbolic link created above (for example, mary's shell should
   be /etc/ppp/ppp-mary).

     --------------------------------------------------------------

      25.2.1.3.8. Setting Up ppp.conf for Dynamic-IP Users

   The /etc/ppp/ppp.conf file should contain something along the
   lines of:

 default:
   set debug phase lcp chat
   set timeout 0

 ttyd0:
   set ifaddr 203.14.100.1 203.14.100.20 255.255.255.255
   enable proxy

 ttyd1:
   set ifaddr 203.14.100.1 203.14.100.21 255.255.255.255
   enable proxy

     -a`: The indenting is important.

   The default: section is loaded for each session. For each dialup
   line enabled in /etc/ttys create an entry similar to the one for
   ttyd0: above. Each line should get a unique IP address from your
   pool of IP addresses for dynamic users.

     --------------------------------------------------------------

      25.2.1.3.9. Setting Up ppp.conf for Static-IP Users

   Along with the contents of the sample
   /usr/share/examples/ppp/ppp.conf above you should add a section
   for each of the statically assigned dialup users. We will continue
   with our fred, sam, and mary example.

 fred:
   set ifaddr 203.14.100.1 203.14.101.1 255.255.255.255

 sam:
   set ifaddr 203.14.100.1 203.14.102.1 255.255.255.255

 mary:
   set ifaddr 203.14.100.1 203.14.103.1 255.255.255.255

   The file /etc/ppp/ppp.linkup should also contain routing
   information for each static IP user if required. The line below
   would add a route for the 203.14.101.0 class C via the client's
   ppp link.

 fred:
   add 203.14.101.0 netmask 255.255.255.0 HISADDR

 sam:
   add 203.14.102.0 netmask 255.255.255.0 HISADDR

 mary:
   add 203.14.103.0 netmask 255.255.255.0 HISADDR

     --------------------------------------------------------------

      25.2.1.3.10. mgetty and AutoPPP

   Configuring and compiling mgetty with the AUTO_PPP option enabled
   allows mgetty to detect the LCP phase of PPP connections and
   automatically spawn off a ppp shell. However, since the default
   login/password sequence does not occur it is necessary to
   authenticate users using either PAP or CHAP.

   This section assumes the user has successfully configured,
   compiled, and installed a version of mgetty with the AUTO_PPP
   option (v0.99beta or later).

   Make sure your /usr/local/etc/mgetty+sendfax/login.config file has
   the following in it:

 /AutoPPP/ -     -                     /etc/ppp/ppp-pap-dialup

   This will tell mgetty to run the ppp-pap-dialup script for
   detected PPP connections.

   Create a file called /etc/ppp/ppp-pap-dialup containing the
   following (the file should be executable):

 #!/bin/sh
 exec /usr/sbin/ppp -direct pap$IDENT

   For each dialup line enabled in /etc/ttys, create a corresponding
   entry in /etc/ppp/ppp.conf. This will happily co-exist with the
   definitions we created above.

 pap:
   enable pap
   set ifaddr 203.14.100.1 203.14.100.20-203.14.100.40
   enable proxy

   Each user logging in with this method will need to have a
   username/password in /etc/ppp/ppp.secret file, or alternatively
   add the following option to authenticate users via PAP from the
   /etc/passwd file.

 enable passwdauth

   If you wish to assign some users a static IP number, you can
   specify the number as the third argument in /etc/ppp/ppp.secret.
   See /usr/share/examples/ppp/ppp.secret.sample for examples.

     --------------------------------------------------------------

      25.2.1.3.11. MS Extensions

   It is possible to configure PPP to supply DNS and NetBIOS
   nameserver addresses on demand.

   To enable these extensions with PPP version 1.x, the following
   lines might be added to the relevant section of /etc/ppp/ppp.conf.

 enable msext
 set ns 203.14.100.1 203.14.100.2
 set nbns 203.14.100.5

   And for PPP version 2 and above:

 accept dns
 set dns 203.14.100.1 203.14.100.2
 set nbns 203.14.100.5

   This will tell the clients the primary and secondary name server
   addresses, and a NetBIOS nameserver host.

   In version 2 and above, if the set dns line is omitted, PPP will
   use the values found in /etc/resolv.conf.

     --------------------------------------------------------------

      25.2.1.3.12. PAP and CHAP Authentication

   Some ISPs set their system up so that the authentication part of
   your connection is done using either of the PAP or CHAP
   authentication mechanisms. If this is the case, your ISP will not
   give a login: prompt when you connect, but will start talking PPP
   immediately.

   PAP is less secure than CHAP, but security is not normally an
   issue here as passwords, although being sent as plain text with
   PAP, are being transmitted down a serial line only. There is not
   much room for crackers to !S:eavesdrop!".

   Referring back to the PPP and Static IP addresses or PPP and
   Dynamic IP addresses sections, the following alterations must be
   made:

 13      set authname MyUserName
 14      set authkey MyPassword
 15      set login

   Line 13:

           This line specifies your PAP/CHAP user name. You will need
           to insert the correct value for MyUserName.

   Line 14:

           This line specifies your PAP/CHAP password. You will need
           to insert the correct value for MyPassword. You may want
           to add an additional line, such as:

 16      accept PAP

           or

 16      accept CHAP

           to make it obvious that this is the intention, but PAP and
           CHAP are both accepted by default.

   Line 15:

           Your ISP will not normally require that you log into the
           server if you are using PAP or CHAP. You must therefore
           disable your !S:set login!" string.

     --------------------------------------------------------------

      25.2.1.3.13. Changing Your ppp Configuration on the Fly

   It is possible to talk to the ppp program while it is running in
   the background, but only if a suitable diagnostic port has been
   set up. To do this, add the following line to your configuration:

 set server /var/run/ppp-tun%d DiagnosticPassword 0177

   This will tell PPP to listen to the specified UNIX domain socket,
   asking clients for the specified password before allowing access.
   The %d in the name is replaced with the tun device number that is
   in use.

   Once a socket has been set up, the pppctl(8) program may be used
   in scripts that wish to manipulate the running program.

     --------------------------------------------------------------

    25.2.1.4. Using PPP Network Address Translation Capability

   PPP has ability to use internal NAT without kernel diverting
   capabilities. This functionality may be enabled by the following
   line in /etc/ppp/ppp.conf:

 nat enable yes

   Alternatively, PPP NAT may be enabled by command-line option -nat.
   There is also /etc/rc.conf knob named ppp_nat, which is enabled by
   default.

   If you use this feature, you may also find useful the following
   /etc/ppp/ppp.conf options to enable incoming connections
   forwarding:

 nat port tcp 10.0.0.2:ftp ftp
 nat port tcp 10.0.0.2:http http

   or do not trust the outside at all

 nat deny_incoming yes

     --------------------------------------------------------------

    25.2.1.5. Final System Configuration

   You now have ppp configured, but there are a few more things to do
   before it is ready to work. They all involve editing the
   /etc/rc.conf file.

   Working from the top down in this file, make sure the hostname=
   line is set, e.g.:

 hostname="foo.example.com"

   If your ISP has supplied you with a static IP address and name, it
   is probably best that you use this name as your host name.

   Look for the network_interfaces variable. If you want to configure
   your system to dial your ISP on demand, make sure the tun0 device
   is added to the list, otherwise remove it.

 network_interfaces="lo0 tun0"
 ifconfig_tun0=

     -a`: The ifconfig_tun0 variable should be empty, and a file
     called /etc/start_if.tun0 should be created. This file should
     contain the line:

 ppp -auto mysystem

     This script is executed at network configuration time, starting
     your ppp daemon in automatic mode. If you have a LAN for which
     this machine is a gateway, you may also wish to use the -alias
     switch. Refer to the manual page for further details.

   Make sure that the router program is set to NO with the following
   line in your /etc/rc.conf:

 router_enable="NO"

   It is important that the routed daemon is not started, as routed
   tends to delete the default routing table entries created by ppp.

   It is probably worth your while ensuring that the sendmail_flags
   line does not include the -q option, otherwise sendmail will
   attempt to do a network lookup every now and then, possibly
   causing your machine to dial out. You may try:

 sendmail_flags="-bd"

   The downside of this is that you must force sendmail to re-examine
   the mail queue whenever the ppp link is up by typing:

 # /usr/sbin/sendmail -q

   You may wish to use the !bg command in ppp.linkup to do this
   automatically:

 1     provider:
 2       delete ALL
 3       add 0 0 HISADDR
 4       !bg sendmail -bd -q30m

   If you do not like this, it is possible to set up a !S:dfilter!"
   to block SMTP traffic. Refer to the sample files for further
   details.

   All that is left is to reboot the machine. After rebooting, you
   can now either type:

 # ppp

   and then dial provider to start the PPP session, or, if you want
   ppp to establish sessions automatically when there is outbound
   traffic (and you have not created the start_if.tun0 script), type:

 # ppp -auto provider

     --------------------------------------------------------------

    25.2.1.6. Summary

   To recap, the following steps are necessary when setting up ppp
   for the first time:

   Client side:

    1. Ensure that the tun device is built into your kernel.

    2. Ensure that the tunN device file is available in the /dev
       directory.

    3. Create an entry in /etc/ppp/ppp.conf. The pmdemand example
       should suffice for most ISPs.

    4. If you have a dynamic IP address, create an entry in
       /etc/ppp/ppp.linkup.

    5. Update your /etc/rc.conf file.

    6. Create a start_if.tun0 script if you require demand dialing.

   Server side:

    1. Ensure that the tun device is built into your kernel.

    2. Ensure that the tunN device file is available in the /dev
       directory.

    3. Create an entry in /etc/passwd (using the vipw(8) program).

    4. Create a profile in this users home directory that runs ppp
       -direct direct-server or similar.

    5. Create an entry in /etc/ppp/ppp.conf. The direct-server
       example should suffice.

    6. Create an entry in /etc/ppp/ppp.linkup.

    7. Update your /etc/rc.conf file.

     --------------------------------------------------------------

25.3. Using Kernel PPP

   Parts originally contributed by Gennady B. Sorokopud YENB Robert
   Huff.

  25.3.1. Setting Up Kernel PPP

   Before you start setting up PPP on your machine, make sure that
   pppd is located in /usr/sbin and the directory /etc/ppp exists.

   pppd can work in two modes:

    1. As a !S:client!" !X!X you want to connect your machine to the
       outside world via a PPP serial connection or modem line.

    2. As a !S:server!" !X!X your machine is located on the network,
       and is used to connect other computers using PPP.

   In both cases you will need to set up an options file
   (/etc/ppp/options or ~/.ppprc if you have more than one user on
   your machine that uses PPP).

   You will also need some modem/serial software (preferably
   comms/kermit), so you can dial and establish a connection with the
   remote host.

     --------------------------------------------------------------

  25.3.2. Using pppd as a Client

   Based on information provided by Trev Roydhouse.

   The following /etc/ppp/options might be used to connect to a Cisco
   terminal server PPP line.

 crtscts         # enable hardware flow control
 modem           # modem control line
 noipdefault     # remote PPP server must supply your IP address
                 # if the remote host does not send your IP during IPCP
                 # negotiation, remove this option
 passive         # wait for LCP packets
 domain ppp.foo.com      # put your domain name here

 :<remote_ip>    # put the IP of remote PPP host here
                 # it will be used to route packets via PPP link
                 # if you didn't specified the noipdefault option
                 # change this line to <local_ip>:<remote_ip>

 defaultroute    # put this if you want that PPP server will be your
                 # default router

   To connect:

    1. Dial to the remote host using Kermit (or some other modem
       program), and enter your user name and password (or whatever
       is needed to enable PPP on the remote host).

    2. Exit Kermit (without hanging up the line).

    3. Enter the following:

 # /usr/src/usr.sbin/pppd.new/pppd /dev/tty01 19200

       Be sure to use the appropriate speed and device name.

   Now your computer is connected with PPP. If the connection fails,
   you can add the debug option to the /etc/ppp/options file, and
   check console messages to track the problem.

   Following /etc/ppp/pppup script will make all 3 stages automatic:

 #!/bin/sh
 ps ax |grep pppd |grep -v grep
 pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill ${pid}
 fi
 ps ax |grep kermit |grep -v grep
 pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi

 ifconfig ppp0 down
 ifconfig ppp0 delete

 kermit -y /etc/ppp/kermit.dial
 pppd /dev/tty01 19200

   /etc/ppp/kermit.dial is a Kermit script that dials and makes all
   necessary authorization on the remote host (an example of such a
   script is attached to the end of this document).

   Use the following /etc/ppp/pppdown script to disconnect the PPP
   line:

 #!/bin/sh
 pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
 if [ X${pid} != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill -TERM ${pid}
 fi

 ps ax |grep kermit |grep -v grep
 pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi

 /sbin/ifconfig ppp0 down
 /sbin/ifconfig ppp0 delete
 kermit -y /etc/ppp/kermit.hup
 /etc/ppp/ppptest

   Check to see if pppd is still running by executing
   /usr/etc/ppp/ppptest, which should look like this:

 #!/bin/sh
 pid=`ps ax| grep pppd |grep -v grep|awk '{print $1;}'`
 if [ X${pid} != "X" ] ; then
         echo 'pppd running: PID=' ${pid-NONE}
 else
         echo 'No pppd running.'
 fi
 set -x
 netstat -n -I ppp0
 ifconfig ppp0

   To hang up the modem, execute /etc/ppp/kermit.hup, which should
   contain:

 set line /dev/tty01     ; put your modem device here
 set speed 19200
 set file type binary
 set file names literal
 set win 8
 set rec pack 1024
 set send pack 1024
 set block 3
 set term bytesize 8
 set command bytesize 8
 set flow none

 pau 1
 out +++
 inp 5 OK
 out ATH0\13
 echo \13
 exit

   Here is an alternate method using chat instead of kermit:

   The following two files are sufficient to accomplish a pppd
   connection.

   /etc/ppp/options:

 /dev/cuaa1 115200

 crtscts         # enable hardware flow control
 modem           # modem control line
 connect "/usr/bin/chat -f /etc/ppp/login.chat.script"
 noipdefault     # remote PPP serve must supply your IP address
                 # if the remote host doesn't send your IP during
                 # IPCP negotiation, remove this option
 passive         # wait for LCP packets
 domain <your.domain>    # put your domain name here

 :               # put the IP of remote PPP host here
                 # it will be used to route packets via PPP link
                 # if you didn't specified the noipdefault option
                 # change this line to <local_ip>:<remote_ip>

 defaultroute    # put this if you want that PPP server will be
                 # your default router

   /etc/ppp/login.chat.script:

     -a`: The following should go on a single line.

 ABORT BUSY ABORT 'NO CARRIER' "" AT OK ATDT<phone.number>
   CONNECT "" TIMEOUT 10 ogin:-\\r-ogin: <login-id>
   TIMEOUT 5 sword: <password>

   Once these are installed and modified correctly, all you need to
   do is run pppd, like so:

 # pppd

     --------------------------------------------------------------

  25.3.3. Using pppd as a Server

   /etc/ppp/options should contain something similar to the
   following:

 crtscts                         # Hardware flow control
 netmask 255.255.255.0           # netmask (not required)
 192.114.208.20:192.114.208.165  # IP's of local and remote hosts
                                 # local ip must be different from one
                                 # you assigned to the Ethernet (or other)
                                 # interface on your machine.
                                 # remote IP is IP address that will be
                                 # assigned to the remote machine
 domain ppp.foo.com              # your domain
 passive                         # wait for LCP
 modem                           # modem line

   The following /etc/ppp/pppserv script will tell pppd to behave as
   a server:

 #!/bin/sh
 ps ax |grep pppd |grep -v grep
 pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill ${pid}
 fi
 ps ax |grep kermit |grep -v grep
 pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi

 # reset ppp interface
 ifconfig ppp0 down
 ifconfig ppp0 delete

 # enable autoanswer mode
 kermit -y /etc/ppp/kermit.ans

 # run ppp
 pppd /dev/tty01 19200

   Use this /etc/ppp/pppservdown script to stop the server:

 #!/bin/sh
 ps ax |grep pppd |grep -v grep
 pid=`ps ax |grep pppd |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing pppd, PID=' ${pid}
         kill ${pid}
 fi
 ps ax |grep kermit |grep -v grep
 pid=`ps ax |grep kermit |grep -v grep|awk '{print $1;}'`
 if [ "X${pid}" != "X" ] ; then
         echo 'killing kermit, PID=' ${pid}
         kill -9 ${pid}
 fi
 ifconfig ppp0 down
 ifconfig ppp0 delete

 kermit -y /etc/ppp/kermit.noans

   The following Kermit script (/etc/ppp/kermit.ans) will
   enable/disable autoanswer mode on your modem. It should look like
   this:

 set line /dev/tty01
 set speed 19200
 set file type binary
 set file names literal
 set win 8
 set rec pack 1024
 set send pack 1024
 set block 3
 set term bytesize 8
 set command bytesize 8
 set flow none

 pau 1
 out +++
 inp 5 OK
 out ATH0\13
 inp 5 OK
 echo \13
 out ATS0=1\13   ; change this to out ATS0=0\13 if you want to disable
                 ; autoanswer mode
 inp 5 OK
 echo \13
 exit

   A script named /etc/ppp/kermit.dial is used for dialing and
   authenticating on the remote host. You will need to customize it
   for your needs. Put your login and password in this script; you
   will also need to change the input statement depending on
   responses from your modem and remote host.

 ;
 ; put the com line attached to the modem here:
 ;
 set line /dev/tty01
 ;
 ; put the modem speed here:
 ;
 set speed 19200
 set file type binary            ; full 8 bit file xfer
 set file names literal
 set win 8
 set rec pack 1024
 set send pack 1024
 set block 3
 set term bytesize 8
 set command bytesize 8
 set flow none
 set modem hayes
 set dial hangup off
 set carrier auto                ; Then SET CARRIER if necessary,
 set dial display on             ; Then SET DIAL if necessary,
 set input echo on
 set input timeout proceed
 set input case ignore
 def \%x 0                       ; login prompt counter
 goto slhup

 :slcmd                          ; put the modem in command mode
 echo Put the modem in command mode.
 clear                           ; Clear unread characters from input buffer
 pause 1
 output +++                      ; hayes escape sequence
 input 1 OK\13\10                ; wait for OK
 if success goto slhup
 output \13
 pause 1
 output at\13
 input 1 OK\13\10
 if fail goto slcmd              ; if modem doesn't answer OK, try again

 :slhup                          ; hang up the phone
 clear                           ; Clear unread characters from input buffer
 pause 1
 echo Hanging up the phone.
 output ath0\13                  ; hayes command for on hook
 input 2 OK\13\10
 if fail goto slcmd              ; if no OK answer, put modem in command mode

 :sldial                         ; dial the number
 pause 1
 echo Dialing.
 output atdt9,550311\13\10               ; put phone number here
 assign \%x 0                    ; zero the time counter

 :look
 clear                           ; Clear unread characters from input buffer
 increment \%x                   ; Count the seconds
 input 1 {CONNECT }
 if success goto sllogin
 reinput 1 {NO CARRIER\13\10}
 if success goto sldial
 reinput 1 {NO DIALTONE\13\10}
 if success goto slnodial
 reinput 1 {\255}
 if success goto slhup
 reinput 1 {\127}
 if success goto slhup
 if < \%x 60 goto look
 else goto slhup

 :sllogin                        ; login
 assign \%x 0                    ; zero the time counter
 pause 1
 echo Looking for login prompt.

 :slloop
 increment \%x                   ; Count the seconds
 clear                           ; Clear unread characters from input buffer
 output \13
 ;
 ; put your expected login prompt here:
 ;
 input 1 {Username: }
 if success goto sluid
 reinput 1 {\255}
 if success goto slhup
 reinput 1 {\127}
 if success goto slhup
 if < \%x 10 goto slloop         ; try 10 times to get a login prompt
 else goto slhup                 ; hang up and start again if 10 failures

 :sluid
 ;
 ; put your userid here:
 ;
 output ppp-login\13
 input 1 {Password: }
 ;
 ; put your password here:
 ;
 output ppp-password\13
 input 1 {Entering SLIP mode.}
 echo
 quit

 :slnodial
 echo \7No dialtone.  Check the telephone line!\7
 exit 1

 ; local variables:
 ; mode: csh
 ; comment-start: "; "
 ; comment-start-skip: "; "
 ; end:

     --------------------------------------------------------------

25.4. Troubleshooting PPP Connections

   Contributed by Tom Rhodes.

   This section covers a few issues which may arise when using PPP
   over a modem connection. For instance, perhaps you need to know
   exactly what prompts the system you are dialing into will present.
   Some ISPs present the ssword prompt, and others will present
   password; if the ppp script is not written accordingly, the login
   attempt will fail. The most common way to debug ppp connections is
   by connecting manually. The following information will walk you
   through a manual connection step by step.

     --------------------------------------------------------------

  25.4.1. Check the Device Nodes

   If you reconfigured your kernel then you recall the sio device. If
   you did not configure your kernel, there is no reason to worry.
   Just check the dmesg output for the modem device with:

 # dmesg | grep sio

   You should get some pertinent output about the sio devices. These
   are the COM ports we need. If your modem acts like a standard
   serial port then you should see it listed on sio1, or COM2. If so,
   you are not required to rebuild the kernel, you just need to make
   the serial device. You can do this by changing your directory to
   /dev and running the MAKEDEV script like above. Now make the
   serial devices with:

 # sh MAKEDEV cuaa0 cuaa1 cuaa2 cuaa3

   which will create the serial devices for your system. When
   matching up sio modem is on sio1 or COM2 if you are in DOS, then
   your modem device would be /dev/cuaa1.

     --------------------------------------------------------------

  25.4.2. Connecting Manually

   Connecting to the Internet by manually controlling ppp is quick,
   easy, and a great way to debug a connection or just get
   information on how your ISP treats ppp client connections. Lets
   start PPP from the command line. Note that in all of our examples
   we will use example as the hostname of the machine running PPP.
   You start ppp by just typing ppp:

 # ppp

   We have now started ppp.

 ppp ON example> set device /dev/cuaa1

   We set our modem device, in this case it is cuaa1.

 ppp ON example> set speed 115200

   Set the connection speed, in this case we are using 115,200 kbps.

 ppp ON example> enable dns

   Tell ppp to configure our resolver and add the nameserver lines to
   /etc/resolv.conf. If ppp cannot determine our hostname, we can set
   one manually later.

 ppp ON example> term

   Switch to !S:terminal!" mode so that we can manually control the
   modem.

 deflink: Entering terminal mode on /dev/cuaa1
 type '~h' for help

 at
 OK
 atdt123456789

   Use at to initialize the modem, then use atdt and the number for
   your ISP to begin the dial in process.

 CONNECT

   Confirmation of the connection, if we are going to have any
   connection problems, unrelated to hardware, here is where we will
   attempt to resolve them.

 ISP Login:myusername

   Here you are prompted for a username, return the prompt with the
   username that was provided by the ISP.

 ISP Pass:mypassword

   This time we are prompted for a password, just reply with the
   password that was provided by the ISP. Just like logging into
   FreeBSD, the password will not echo.

 Shell or PPP:ppp

   Depending on your ISP this prompt may never appear. Here we are
   being asked if we wish to use a shell on the provider, or to start
   ppp. In this example, we have chosen to use ppp as we want an
   Internet connection.

 Ppp ON example>

   Notice that in this example the first p has been capitalized. This
   shows that we have successfully connected to the ISP.

 PPp ON example>

   We have successfully authenticated with our ISP and are waiting
   for the assigned IP address.

 PPP ON example>

   We have made an agreement on an IP address and successfully
   completed our connection.

 PPP ON example>add default HISADDR

   Here we add our default route, we need to do this before we can
   talk to the outside world as currently the only established
   connection is with the peer. If this fails due to existing routes
   you can put a bang character ! in front of the add. Alternatively,
   you can set this before making the actual connection and it will
   negotiate a new route accordingly.

   If everything went good we should now have an active connection to
   the Internet, which could be thrown into the background using
   CTRL+z If you notice the PPP return to ppp then we have lost our
   connection. This is good to know because it shows our connection
   status. Capital P's show that we have a connection to the ISP and
   lowercase p's show that the connection has been lost for whatever
   reason. ppp only has these 2 states.

     --------------------------------------------------------------

    25.4.2.1. Debugging

   If you have a direct line and cannot seem to make a connection,
   then turn hardware flow CTS/RTS to off with the set ctsrts off.
   This is mainly the case if you are connected to some PPP capable
   terminal servers, where PPP hangs when it tries to write data to
   your communication link, so it would be waiting for a CTS, or
   Clear To Send signal which may never come. If you use this option
   however, you should also use the set accmap option, which may be
   required to defeat hardware dependent on passing certain
   characters from end to end, most of the time XON/XOFF. See the
   ppp(8) manual page for more information on this option, and how it
   is used.

   If you have an older modem, you may need to use the set parity
   even. Parity is set at none be default, but is used for error
   checking (with a large increase in traffic) on older modems and
   some ISPs. You may need this option for the Compuserve ISP.

   PPP may not return to the command mode, which is usually a
   negotiation error where the ISP is waiting for your side to start
   negotiating. At this point, using the ~p command will force ppp to
   start sending the configuration information.

   If you never obtain a login prompt, then most likely you need to
   use PAP or CHAP authentication instead of the UNIX style in the
   example above. To use PAP or CHAP just add the following options
   to PPP before going into terminal mode:

 ppp ON example> set authname myusername

   Where myusername should be replaced with the username that was
   assigned by the ISP.

 ppp ON example> set authkey mypassword

   Where mypassword should be replaced with the password that was
   assigned by the ISP.

   If you connect fine, but cannot seem to find any domain name, try
   to use ping(8) with an IP address and see if you can get any
   return information. If you experience 100 percent (100%) packet
   loss, then it is most likely that you were not assigned a default
   route. Double check that the option add default HISADDR was set
   during the connection. If you can connect to a remote IP address
   then it is possible that a resolver address has not been added to
   the /etc/resolv.conf. This file should look like:

 domain example.com
 nameserver x.x.x.x
 nameserver y.y.y.y

   Where x.x.x.x and y.y.y.y should be replaced with the IP address
   of your ISP's DNS servers. This information may or may not have
   been provided when you signed up, but a quick call to your ISP
   should remedy that.

   You could also have syslog(3) provide a logging function for your
   PPP connection. Just add:

 !ppp
 *.*     /var/log/ppp.log

   to /etc/syslog.conf. In most cases, this functionality already
   exists.

     --------------------------------------------------------------

25.5. Using PPP over Ethernet (PPPoE)

   Contributed (from
   http://node.to/freebsd/how-tos/how-to-freebsd-pppoe.html) by Jim
   Mock.

   This section describes how to set up PPP over Ethernet (PPPoE).

     --------------------------------------------------------------

  25.5.1. Configuring the Kernel

   No kernel configuration is necessary for PPPoE any longer. If the
   necessary netgraph support is not built into the kernel, it will
   be dynamically loaded by ppp.

     --------------------------------------------------------------

  25.5.2. Setting Up ppp.conf

   Here is an example of a working ppp.conf:

 default:
   set log Phase tun command # you can add more detailed logging if you wish
   set ifaddr 10.0.0.1/0 10.0.0.2/0

 name_of_service_provider:
   set device PPPoE:xl1 # replace xl1 with your Ethernet device
   set authname YOURLOGINNAME
   set authkey YOURPASSWORD
   set dial
   set login
   add default HISADDR

     --------------------------------------------------------------

  25.5.3. Running ppp

   As root, you can run:

 # ppp -ddial name_of_service_provider

     --------------------------------------------------------------

  25.5.4. Starting ppp at Boot

   Add the following to your /etc/rc.conf file:

 ppp_enable="YES"
 ppp_mode="ddial"
 ppp_nat="YES"   # if you want to enable nat for your local network, otherwise NO
 ppp_profile="name_of_service_provider"

     --------------------------------------------------------------

  25.5.5. Using a PPPoE Service Tag

   Sometimes it will be necessary to use a service tag to establish
   your connection. Service tags are used to distinguish between
   different PPPoE servers attached to a given network.

   You should have been given any required service tag information in
   the documentation provided by your ISP. If you cannot locate it
   there, ask your ISP's tech support personnel.

   As a last resort, you could try the method suggested by the
   Roaring Penguin PPPoE program which can be found in the Ports
   Collection. Bear in mind however, this may de-program your modem
   and render it useless, so think twice before doing it. Simply
   install the program shipped with the modem by your provider. Then,
   access the System menu from the program. The name of your profile
   should be listed there. It is usually ISP.

   The profile name (service tag) will be used in the PPPoE
   configuration entry in ppp.conf as the provider part of the set
   device command (see the ppp(8) manual page for full details). It
   should look like this:

 set device PPPoE:xl1:ISP

   Do not forget to change xl1 to the proper device for your Ethernet
   card.

   Do not forget to change ISP to the profile you have just found
   above.

   For additional information, see:

     * Cheaper Broadband with FreeBSD on DSL by Renaud Waldura.

     * Nutzung von T-DSL und T-Online mit FreeBSD by Udo Erdelhoff
       (in German).

     --------------------------------------------------------------

  25.5.6. PPPoE with a 3Com(R) HomeConnect(R) ADSL Modem Dual Link

   This modem does not follow RFC 2516 (A Method for transmitting PPP
   over Ethernet (PPPoE), written by L. Mamakos, K. Lidl, J. Evarts,
   D. Carrel, D. Simone, and R. Wheeler). Instead, different packet
   type codes have been used for the Ethernet frames. Please complain
   to 3Com if you think it should comply with the PPPoE
   specification.

   In order to make FreeBSD capable of communicating with this
   device, a sysctl must be set. This can be done automatically at
   boot time by updating /etc/sysctl.conf:

 net.graph.nonstandard_pppoe=1

   or can be done immediately with the command:

 # sysctl net.graph.nonstandard_pppoe=1

   Unfortunately, because this is a system-wide setting, it is not
   possible to talk to a normal PPPoE client or server and a 3Com
   HomeConnect(R) ADSL Modem at the same time.

     --------------------------------------------------------------

25.6. Using PPP over ATM (PPPoA)

   The following describes how to set up PPP over ATM (PPPoA). PPPoA
   is a popular choice among European DSL providers.

     --------------------------------------------------------------

  25.6.1. Using PPPoA with the Alcatel SpeedTouch(TM) USB

   PPPoA support for this device is supplied as a port in FreeBSD
   because the firmware is distributed under Alcatel's license
   agreement and can not be redistributed freely with the base system
   of FreeBSD.

   To install the software, simply use the Ports Collection. Install
   the net/pppoa port and follow the instructions provided with it.

   Like many USB devices, the Alcatel SpeedTouch(TM) USB needs to
   download firmware from the host computer to operate properly. It
   is possible to automate this process in FreeBSD so that this
   transfer takes place whenever the device is plugged into a USB
   port. The following information can be added to the /etc/usbd.conf
   file to enable this automatic firmware transfer. This file must be
   edited as the root user.

 device "Alcatel SpeedTouch USB"
     devname "ugen[0-9]+"
     vendor 0x06b9
     product 0x4061
     attach "/usr/local/sbin/modem_run -f /usr/local/libdata/mgmt.o"

   To enable the USB daemon, usbd, put the following the line into
   /etc/rc.conf:

 usbd_enable="YES"

   It is also possible to set up ppp to dial up at startup. To do
   this add the following lines to /etc/rc.conf. Again, for this
   procedure you will need to be logged in as the root user.

 ppp_enable="YES"
 ppp_mode="ddial"
 ppp_profile="adsl"

   For this to work correctly you will need to have used the sample
   ppp.conf which is supplied with the net/pppoa port.

     --------------------------------------------------------------

  25.6.2. Using mpd

   You can use mpd to connect to a variety of services, in particular
   PPTP services. You can find mpd in the Ports Collection, net/mpd.
   Many ADSL modems require that a PPTP tunnel is created between the
   modem and computer, one such modem is the Alcatel SpeedTouch Home.

   First you must install the port, and then you can configure mpd to
   suit your requirements and provider settings. The port places a
   set of sample configuration files which are well documented in
   PREFIX/etc/mpd/. Note here that PREFIX means the directory into
   which your ports are installed, this defaults to /usr/local/. A
   complete guide to configure mpd is available in HTML format once
   the port has been installed. It is placed in
   PREFIX/share/doc/mpd/. Here is a sample configuration for
   connecting to an ADSL service with mpd. The configuration is
   spread over two files, first the mpd.conf:

 default:
     load adsl

 adsl:
     new -i ng0 adsl adsl
     set bundle authname username (1)
     set bundle password password (2)
     set bundle disable multilink

     set link no pap acfcomp protocomp
     set link disable chap
     set link accept chap
     set link keep-alive 30 10

     set ipcp no vjcomp
     set ipcp ranges 0.0.0.0/0 0.0.0.0/0

     set iface route default
     set iface disable on-demand
     set iface enable proxy-arp
     set iface idle 0

     open

   (1)
           The username used to authenticate with your ISP.
   (2)
           The password used to authenticate with your ISP.

   The mpd.links file contains information about the link, or links,
   you wish to establish. An example mpd.links to accompany the above
   example is given beneath:

 adsl:
     set link type pptp
     set pptp mode active
     set pptp enable originate outcall
     set pptp self 10.0.0.1 (1)
     set pptp peer 10.0.0.138 (2)

   (1)
           The IP address of your FreeBSD computer which you will be
           using mpd from.
   (2)
           The IP address of your ADSL modem. For the Alcatel
           SpeedTouch Home this address defaults to 10.0.0.138.

   It is possible to initialize the connection easily by issuing the
   following command as root:

 # mpd -b adsl

   You can see the status of the connection with the following
   command:

 % ifconfig ng0
 ng0: flags=88d1<UP,POINTOPOINT,RUNNING,NOARP,SIMPLEX,MULTICAST> mtu 1500
      inet 216.136.204.117 --> 204.152.186.171 netmask 0xffffffff

   Using mpd is the recommended way to connect to an ADSL service
   with FreeBSD.

     --------------------------------------------------------------

  25.6.3. Using pptpclient

   It is also possible to use FreeBSD to connect to other PPPoA
   services using net/pptpclient.

   To use net/pptpclient to connect to a DSL service, install the
   port or package and edit your /etc/ppp/ppp.conf. You will need to
   be root to perform both of these operations. An example section of
   ppp.conf is given below. For further information on ppp.conf
   options consult the ppp manual page, ppp(8).

 adsl:
  set log phase chat lcp ipcp ccp tun command
  set timeout 0
  enable dns
  set authname username (1)
  set authkey password (2)
  set ifaddr 0 0
  add default HISADDR

   (1)
           The username of your account with the DSL provider.
   (2)
           The password for your account.

     A:uS:iBecause you must put your account's password in the
     ppp.conf file in plain text form you should make sure than
     nobody can read the contents of this file. The following series
     of commands will make sure the file is only readable by the root
     account. Refer to the manual pages for chmod(1) and chown(8) for
     further information.

 # chown root:wheel /etc/ppp/ppp.conf
 # chmod 600 /etc/ppp/ppp.conf

   This will open a tunnel for a PPP session to your DSL router.
   Ethernet DSL modems have a preconfigured LAN IP address which you
   connect to. In the case of the Alcatel SpeedTouch Home this
   address is 10.0.0.138. Your router documentation should tell you
   which address your device uses. To open the tunnel and start a PPP
   session execute the following command:

 # pptp address adsl

     '-L-YENU:: You may wish to add an ampersand (!S:&!") to the end
     of the previous command because pptp will not return your prompt
     to you otherwise.

   A tun virtual tunnel device will be created for interaction
   between the pptp and ppp processes. Once you have been returned to
   your prompt, or the pptp process has confirmed a connection you
   can examine the tunnel like so:

 % ifconfig tun0
 tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1500
         inet 216.136.204.21 --> 204.152.186.171 netmask 0xffffff00
         Opened by PID 918

   If you are unable to connect, check the configuration of your
   router, which is usually accessible via telnet or with a web
   browser. If you still cannot connect you should examine the output
   of the pptp command and the contents of the ppp log file,
   /var/log/ppp.log for clues.

     --------------------------------------------------------------

25.7. Using SLIP

   Originally contributed by Satoshi Asami. With input from Guy
   Helmer YENB Piero Serini.

     --------------------------------------------------------------

  25.7.1. Setting Up a SLIP Client

   The following is one way to set up a FreeBSD machine for SLIP on a
   static host network. For dynamic hostname assignments (your
   address changes each time you dial up), you probably need to have
   a more complex setup.

   First, determine which serial port your modem is connected to.
   Many people set up a symbolic link, such as /dev/modem, to point
   to the real device name, /dev/cuaaN (or /dev/cuadN under
   FreeBSD 6.X). This allows you to abstract the actual device name
   should you ever need to move the modem to a different port. It can
   become quite cumbersome when you need to fix a bunch of files in
   /etc and .kermrc files all over the system!

     -a`: /dev/cuaa0 (or /dev/cuad0 under FreeBSD 6.X) is COM1, cuaa1
     (or /dev/cuad1) is COM2, etc.

   Make sure you have the following in your kernel configuration
   file:

 device   sl

   Under FreeBSD 4.X, use instead the following line:

 pseudo-device   sl      1

   It is included in the GENERIC kernel, so this should not be a
   problem unless you have deleted it.

     --------------------------------------------------------------

    25.7.1.1. Things You Have to Do Only Once

    1. Add your home machine, the gateway and nameservers to your
       /etc/hosts file. Ours looks like this:

 127.0.0.1               localhost loghost
 136.152.64.181          water.CS.Example.EDU water.CS water
 136.152.64.1            inr-3.CS.Example.EDU inr-3 slip-gateway
 128.32.136.9            ns1.Example.EDU ns1
 128.32.136.12           ns2.Example.EDU ns2

    2. Make sure you have hosts before bind in your /etc/host.conf on
       FreeBSD versions prior to 5.0. Since FreeBSD 5.0, the system
       uses the file /etc/nsswitch.conf instead, make sure you have
       files before dns in the hosts line of this file. Without these
       parameters funny things may happen.

    3. Edit the /etc/rc.conf file.

         1. Set your hostname by editing the line that says:

 hostname="myname.my.domain"

            Your machine's full Internet hostname should be placed
            here.

         2. Designate the default router by changing the line:

 defaultrouter="NO"

            to:

 defaultrouter="slip-gateway"

    4. Make a file /etc/resolv.conf which contains:

 domain CS.Example.EDU
 nameserver 128.32.136.9
 nameserver 128.32.136.12

       As you can see, these set up the nameserver hosts. Of course,
       the actual domain names and addresses depend on your
       environment.

    5. Set the password for root and toor (and any other accounts
       that do not have a password).

    6. Reboot your machine and make sure it comes up with the correct
       hostname.

     --------------------------------------------------------------

    25.7.1.2. Making a SLIP Connection

    1. Dial up, type slip at the prompt, enter your machine name and
       password. What is required to be entered depends on your
       environment. If you use Kermit, you can try a script like
       this:

 # kermit setup
 set modem hayes
 set line /dev/modem
 set speed 115200
 set parity none
 set flow rts/cts
 set terminal bytesize 8
 set file type binary
 # The next macro will dial up and login
 define slip dial 643-9600, input 10 =>, if failure stop, -
 output slip\x0d, input 10 Username:, if failure stop, -
 output silvia\x0d, input 10 Password:, if failure stop, -
 output ***\x0d, echo \x0aCONNECTED\x0a

       Of course, you have to change the username and password to fit
       yours. After doing so, you can just type slip from the Kermit
       prompt to connect.

         -a`: Leaving your password in plain text anywhere in the
         filesystem is generally a bad idea. Do it at your own risk.

    2. Leave the Kermit there (you can suspend it by Ctrl-z) and as
       root, type:

 # slattach -h -c -s 115200 /dev/modem

       If you are able to ping hosts on the other side of the router,
       you are connected! If it does not work, you might want to try
       -a instead of -c as an argument to slattach.

     --------------------------------------------------------------

    25.7.1.3. How to Shutdown the Connection

   Do the following:

 # kill -INT `cat /var/run/slattach.modem.pid`

   to kill slattach. Keep in mind you must be root to do the above.
   Then go back to kermit (by running fg if you suspended it) and
   exit from it (q).

   The slattach(8) manual page says you have to use ifconfig sl0 down
   to mark the interface down, but this does not seem to make any
   difference. (ifconfig sl0 reports the same thing.)

   Some times, your modem might refuse to drop the carrier. In that
   case, simply start kermit and quit it again. It usually goes out
   on the second try.

     --------------------------------------------------------------

    25.7.1.4. Troubleshooting

   If it does not work, feel free to ask on freebsd-net mailing list.
   The things that people tripped over so far:

     * Not using -c or -a in slattach (This should not be fatal, but
       some users have reported that this solves their problems.)

     * Using s10 instead of sl0 (might be hard to see the difference
       on some fonts).

     * Try ifconfig sl0 to see your interface status. For example,
       you might get:

 # ifconfig sl0
 sl0: flags=10<POINTOPOINT>
         inet 136.152.64.181 --> 136.152.64.1 netmask ffffff00

     * If you get !S:no route to host!" messages from ping(8), there
       may be a problem with your routing table. You can use the
       netstat -r command to display the current routes :

 # netstat -r
 Routing tables
 Destination      Gateway            Flags     Refs     Use  IfaceMTU    Rtt    Netmasks:

 (root node)
 (root node)

 Route Tree for Protocol Family inet:
 (root node) =>
 default          inr-3.Example.EDU  UG          8   224515  sl0 -      -
 localhost.Exampl localhost.Example. UH          5    42127  lo0 -       0.438
 inr-3.Example.ED water.CS.Example.E UH          1        0  sl0 -      -
 water.CS.Example localhost.Example. UGH        34 47641234  lo0 -       0.438
 (root node)

       The preceding examples are from a relatively busy system. The
       numbers on your system will vary depending on network
       activity.

     --------------------------------------------------------------

  25.7.2. Setting Up a SLIP Server

   This document provides suggestions for setting up SLIP Server
   services on a FreeBSD system, which typically means configuring
   your system to automatically startup connections upon login for
   remote SLIP clients.

     --------------------------------------------------------------

    25.7.2.1. Prerequisites

   This section is very technical in nature, so background knowledge
   is required. It is assumed that you are familiar with the TCP/IP
   network protocol, and in particular, network and node addressing,
   network address masks, subnetting, routing, and routing protocols,
   such as RIP. Configuring SLIP services on a dial-up server
   requires a knowledge of these concepts, and if you are not
   familiar with them, please read a copy of either Craig Hunt's
   TCP/IP Network Administration published by O'Reilly & Associates,
   Inc. (ISBN Number 0-937175-82-X), or Douglas Comer's books on the
   TCP/IP protocol.

   It is further assumed that you have already set up your modem(s)
   and configured the appropriate system files to allow logins
   through your modems. If you have not prepared your system for this
   yet, please see uU 24.4 ,` for details on dialup services
   configuration. You may also want to check the manual pages for
   sio(4) for information on the serial port device driver and
   ttys(5), gettytab(5), getty(8), & init(8) for information relevant
   to configuring the system to accept logins on modems, and perhaps
   stty(1) for information on setting serial port parameters (such as
   clocal for directly-connected serial interfaces).

     --------------------------------------------------------------

    25.7.2.2. Quick Overview

   In its typical configuration, using FreeBSD as a SLIP server works
   as follows: a SLIP user dials up your FreeBSD SLIP Server system
   and logs in with a special SLIP login ID that uses
   /usr/sbin/sliplogin as the special user's shell. The sliplogin
   program browses the file /etc/sliphome/slip.hosts to find a
   matching line for the special user, and if it finds a match,
   connects the serial line to an available SLIP interface and then
   runs the shell script /etc/sliphome/slip.login to configure the
   SLIP interface.

     --------------------------------------------------------------

      25.7.2.2.1. An Example of a SLIP Server Login

   For example, if a SLIP user ID were Shelmerg, Shelmerg's entry in
   /etc/master.passwd would look something like this:

 Shelmerg:password:1964:89::0:0:Guy Helmer - SLIP:/usr/users/Shelmerg:/usr/sbin/sliplogin

   When Shelmerg logs in, sliplogin will search
   /etc/sliphome/slip.hosts for a line that had a matching user ID;
   for example, there may be a line in /etc/sliphome/slip.hosts that
   reads:

 Shelmerg        dc-slip sl-helmer       0xfffffc00                autocomp

   sliplogin will find that matching line, hook the serial line into
   the next available SLIP interface, and then execute
   /etc/sliphome/slip.login like this:

 /etc/sliphome/slip.login 0 19200 Shelmerg dc-slip sl-helmer 0xfffffc00 autocomp

   If all goes well, /etc/sliphome/slip.login will issue an ifconfig
   for the SLIP interface to which sliplogin attached itself (SLIP
   interface 0, in the above example, which was the first parameter
   in the list given to slip.login) to set the local IP address
   (dc-slip), remote IP address (sl-helmer), network mask for the
   SLIP interface (0xfffffc00), and any additional flags (autocomp).
   If something goes wrong, sliplogin usually logs good informational
   messages via the syslogd daemon facility, which usually logs to
   /var/log/messages (see the manual pages for syslogd(8) and
   syslog.conf(5) and perhaps check /etc/syslog.conf to see to what
   syslogd is logging and where it is logging to).

     --------------------------------------------------------------

    25.7.2.3. Kernel Configuration

   FreeBSD's default kernel (GENERIC) comes with SLIP (sl(4))
   support; in case of a custom kernel, you have to add the following
   line to your kernel configuration file:

 device   sl

   Under FreeBSD 4.X, use instead the following line:

 pseudo-device   sl      2

     -a`: The number at the end of the line is the maximum number of
     SLIP connections that may be operating simultaneously. Since
     FreeBSD 5.0, the sl(4) driver is !S:auto-cloning!".

   By default, your FreeBSD machine will not forward packets. If you
   want your FreeBSD SLIP Server to act as a router, you will have to
   edit the /etc/rc.conf file and change the setting of the
   gateway_enable variable to YES.

   You will then need to reboot for the new settings to take effect.

   Please refer to uU 8 ^3^1 on Configuring the FreeBSD Kernel for
   help in reconfiguring your kernel.

     --------------------------------------------------------------

    25.7.2.4. Sliplogin Configuration

   As mentioned earlier, there are three files in the /etc/sliphome
   directory that are part of the configuration for
   /usr/sbin/sliplogin (see sliplogin(8) for the actual manual page
   for sliplogin): slip.hosts, which defines the SLIP users and their
   associated IP addresses; slip.login, which usually just configures
   the SLIP interface; and (optionally) slip.logout, which undoes
   slip.login's effects when the serial connection is terminated.

     --------------------------------------------------------------

      25.7.2.4.1. slip.hosts Configuration

   /etc/sliphome/slip.hosts contains lines which have at least four
   items separated by whitespace:

     * SLIP user's login ID

     * Local address (local to the SLIP server) of the SLIP link

     * Remote address of the SLIP link

     * Network mask

   The local and remote addresses may be host names (resolved to IP
   addresses by /etc/hosts or by the domain name service, depending
   on your specifications in the file /etc/nsswitch.conf, or in
   /etc/host.conf if you use FreeBSD 4.X), and the network mask may
   be a name that can be resolved by a lookup into /etc/networks. On
   a sample system, /etc/sliphome/slip.hosts looks like this:

 #
 # login local-addr      remote-addr     mask            opt1    opt2
 #                                               (normal,compress,noicmp)
 #
 Shelmerg  dc-slip       sl-helmerg      0xfffffc00      autocomp

   At the end of the line is one or more of the options:

     * normal !X!X no header compression

     * compress !X!X compress headers

     * autocomp !X!X compress headers if the remote end allows it

     * noicmp !X!X disable ICMP packets (so any !S:ping!" packets
       will be dropped instead of using up your bandwidth)

   Your choice of local and remote addresses for your SLIP links
   depends on whether you are going to dedicate a TCP/IP subnet or if
   you are going to use !S:proxy ARP!" on your SLIP server (it is not
   !S:true!" proxy ARP, but that is the terminology used in this
   section to describe it). If you are not sure which method to
   select or how to assign IP addresses, please refer to the TCP/IP
   books referenced in the SLIP Prerequisites (uU 25.7.2.1 ,`) and/or
   consult your IP network manager.

   If you are going to use a separate subnet for your SLIP clients,
   you will need to allocate the subnet number out of your assigned
   IP network number and assign each of your SLIP client's IP numbers
   out of that subnet. Then, you will probably need to configure a
   static route to the SLIP subnet via your SLIP server on your
   nearest IP router.

   Otherwise, if you will use the !S:proxy ARP!" method, you will
   need to assign your SLIP client's IP addresses out of your SLIP
   server's Ethernet subnet, and you will also need to adjust your
   /etc/sliphome/slip.login and /etc/sliphome/slip.logout scripts to
   use arp(8) to manage the proxy-ARP entries in the SLIP server's
   ARP table.

     --------------------------------------------------------------

      25.7.2.4.2. slip.login Configuration

   The typical /etc/sliphome/slip.login file looks like this:

 #!/bin/sh -
 #
 #       @(#)slip.login  5.1 (Berkeley) 7/1/90

 #
 # generic login file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 inet $4 $5 netmask $6

   This slip.login file merely runs ifconfig for the appropriate SLIP
   interface with the local and remote addresses and network mask of
   the SLIP interface.

   If you have decided to use the !S:proxy ARP!" method (instead of
   using a separate subnet for your SLIP clients), your
   /etc/sliphome/slip.login file will need to look something like
   this:

 #!/bin/sh -
 #
 #       @(#)slip.login  5.1 (Berkeley) 7/1/90

 #
 # generic login file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 inet $4 $5 netmask $6
 # Answer ARP requests for the SLIP client with our Ethernet addr
 /usr/sbin/arp -s $5 00:11:22:33:44:55 pub

   The additional line in this slip.login, arp -s $5
   00:11:22:33:44:55 pub, creates an ARP entry in the SLIP server's
   ARP table. This ARP entry causes the SLIP server to respond with
   the SLIP server's Ethernet MAC address whenever another IP node on
   the Ethernet asks to speak to the SLIP client's IP address.

   When using the example above, be sure to replace the Ethernet MAC
   address (00:11:22:33:44:55) with the MAC address of your system's
   Ethernet card, or your !S:proxy ARP!" will definitely not work!
   You can discover your SLIP server's Ethernet MAC address by
   looking at the results of running netstat -i; the second line of
   the output should look something like:

 ed0   1500  <Link>0.2.c1.28.5f.4a         191923        0   129457     0   116

   This indicates that this particular system's Ethernet MAC address
   is 00:02:c1:28:5f:4a !X!X the periods in the Ethernet MAC address
   given by netstat -i must be changed to colons and leading zeros
   should be added to each single-digit hexadecimal number to convert
   the address into the form that arp(8) desires; see the manual page
   on arp(8) for complete information on usage.

     -a`: When you create /etc/sliphome/slip.login and
     /etc/sliphome/slip.logout, the !S:execute!" bit (i.e., chmod 755
     /etc/sliphome/slip.login /etc/sliphome/slip.logout) must be set,
     or sliplogin will be unable to execute it.

     --------------------------------------------------------------

      25.7.2.4.3. slip.logout Configuration

   /etc/sliphome/slip.logout is not strictly needed (unless you are
   implementing !S:proxy ARP!"), but if you decide to create it, this
   is an example of a basic slip.logout script:

 #!/bin/sh -
 #
 #       slip.logout

 #
 # logout file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 down

   If you are using !S:proxy ARP!", you will want to have
   /etc/sliphome/slip.logout remove the ARP entry for the SLIP
   client:

 #!/bin/sh -
 #
 #       @(#)slip.logout

 #
 # logout file for a slip line.  sliplogin invokes this with
 # the parameters:
 #      1        2         3        4          5         6     7-n
 #   slipunit ttyspeed loginname local-addr remote-addr mask opt-args
 #
 /sbin/ifconfig sl$1 down
 # Quit answering ARP requests for the SLIP client
 /usr/sbin/arp -d $5

   The arp -d $5 removes the ARP entry that the !S:proxy ARP!"
   slip.login added when the SLIP client logged in.

   It bears repeating: make sure /etc/sliphome/slip.logout has the
   execute bit set after you create it (i.e., chmod 755
   /etc/sliphome/slip.logout).

     --------------------------------------------------------------

    25.7.2.5. Routing Considerations

   If you are not using the !S:proxy ARP!" method for routing packets
   between your SLIP clients and the rest of your network (and
   perhaps the Internet), you will probably have to add static routes
   to your closest default router(s) to route your SLIP clients
   subnet via your SLIP server.

     --------------------------------------------------------------

      25.7.2.5.1. Static Routes

   Adding static routes to your nearest default routers can be
   troublesome (or impossible if you do not have authority to do
   so...). If you have a multiple-router network in your
   organization, some routers, such as those made by Cisco and
   Proteon, may not only need to be configured with the static route
   to the SLIP subnet, but also need to be told which static routes
   to tell other routers about, so some expertise and
   troubleshooting/tweaking may be necessary to get
   static-route-based routing to work.

     --------------------------------------------------------------

      25.7.2.5.2. Running GateD(R)

     -a`: GateD is proprietary software now and will not be available
     as source code to the public anymore (more info on the GateD
     website). This section only exists to ensure backwards
     compatibility for those that are still using an older version.

   An alternative to the headaches of static routes is to install
   GateD on your FreeBSD SLIP server and configure it to use the
   appropriate routing protocols (RIP/OSPF/BGP/EGP) to tell other
   routers about your SLIP subnet. You will need to write a
   /etc/gated.conf file to configure your GateD; here is a sample,
   similar to what the author used on a FreeBSD SLIP server:

 #
 # gated configuration file for dc.dsu.edu; for gated version 3.5alpha5
 # Only broadcast RIP information for xxx.xxx.yy out the ed Ethernet interface
 #
 #
 # tracing options
 #
 traceoptions "/var/tmp/gated.output" replace size 100k files 2 general ;

 rip yes {
   interface sl noripout noripin ;
   interface ed ripin ripout version 1 ;
   traceoptions route ;
 } ;

 #
 # Turn on a bunch of tracing info for the interface to the kernel:
 kernel {
   traceoptions remnants request routes info interface ;
 } ;

 #
 # Propagate the route to xxx.xxx.yy out the Ethernet interface via RIP
 #

 export proto rip interface ed {
   proto direct {
       xxx.xxx.yy mask 255.255.252.0 metric 1; # SLIP connections
   } ;
 } ;

 #
 # Accept routes from RIP via ed Ethernet interfaces

 import proto rip interface ed {
   all ;
 } ;

   The above sample gated.conf file broadcasts routing information
   regarding the SLIP subnet xxx.xxx.yy via RIP onto the Ethernet; if
   you are using a different Ethernet driver than the ed driver, you
   will need to change the references to the ed interface
   appropriately. This sample file also sets up tracing to
   /var/tmp/gated.output for debugging GateD's activity; you can
   certainly turn off the tracing options if GateD works correctly
   for you. You will need to change the xxx.xxx.yy's into the network
   address of your own SLIP subnet (be sure to change the net mask in
   the proto direct clause as well).

   Once you have installed and configured GateD on your system, you
   will need to tell the FreeBSD startup scripts to run GateD in
   place of routed. The easiest way to accomplish this is to set the
   router and router_flags variables in /etc/rc.conf. Please see the
   manual page for GateD for information on command-line parameters.

     --------------------------------------------------------------

                        ^3^1 26. ^1qCURlP:lYENo

   Original work by Bill Lloyd. Rewritten by Jim Mock.

26.1. .S:z

   !S:^1qCURlP:lYENo!"(c)I-aI<<U-oU-a-o email!A
   CURDNOTO^2{CURu"IYENI^3I 1/4s-ax-a-o. 3/4^3qCURe|!CURS:CUR@!C
   YEN>>^3^1YENDnCURP:^2D-|p|o|b FreeBSD CURW|w,E!B ^3](c)w email
   -aADEGE!AYENHCURI|p|o|b FreeBSD |NOTuo<<HYENo!F
   uM|O^3o"ACUR-L-NOTOS:^1 3/4a-a-oDEGN|OCURaYENU!A
   ^1e>>UCURW^3\|h>>Y|OP:q-a-o<<n"AEP:u"AYEN
   1/4'-L-CURI!AY+-yAA,N^2O,` 1/2D-DEGN 3/4\ -ath?y B
   CUR-o-a-oDEGN|O(R)NA:y!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!J

     * th"C,^3nAAeCUR,YENo>>P|NOTuo^1qCURlP:lYENo|^3Ao:!C

     * FreeBSD CUR-o-a-o sendmail DEGoYEN>>^3](c)wAE|bth!C

     * >>.-oY<<H 1/2c>>PYEN>> 3/4-:<<H 1/2c-a-oDEGIS:O!C

     * |p|o-ay 3/4 *
       spammer((c)US:-L-P:lYENo>>s^3y-aI)<<D-ak^1BYENI+-z-a-oP:lYENo|o/-aA
       3/4^1S:@NOTDEG relay(A`auoCURCURA:~AI)!C

     * |p|o|w,E!B^3](c)w"a:YENL Mail Transfer Agent(MTA) "O"uYENN
       sendmail!C

     * |p|o^3B^2z+-`"-L--a-oP:lYENo|o/-aA 3/4^1DEGYAD!C

     * |p|o"IYENI UUCP "OP:i|ae SMTP!C

     * |p|o^3](c)w"t^2I!A"I"a:YENu-`auoDEGeP:lYENo!C

     * |p|o|b 1/4.+-uCURW-ooAo^1OCURCUR!A|NOTuoP:lYENo!C

     * |p|o^3](c)w SMTP AAc,AO!AYENHYEN[+-j|wYENth(c)E!C

     * |p|o|w,E!B"IYENI Mail User Agent(MUA) u{|!!ACURn|p mutt
       "O|NOTuoP:lYENo!C

     * |p|o+-q>>.-oY POP (c)I IMAP YEND 3/4-:YENhCURU,u:P:lYENo!C

     * |p|o|b|NOT<<HCURe+-!A|UDEGE(R)MYENIP:lYENo^1LAo!C

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!J

     * YENy^3]|nS:A-a-o-oo,o (uU 29 ^3^1)!C

     * -`aYEN? 1/2TNOTDEGP:lYENo|o/-aA 3/4^1^3](c)w DNS (uU 27
       ^3^1)!C

     * -a 3/4^1D|p|o^3z^1L port/package |w,E^3nAAe (uU 4 ^3^1)!C

     --------------------------------------------------------------

26.2. "IYENI^1qCURlP:lYENo

   |b email YENae'<<-a-o^1Lu{CURCUR|^3 5
   OYENDn^3!CURA!ACURAS:ONOTO!GMUA!BMTA!B DNS!B  >>.-oY(c)IYEN>>
   3/4-:-a-o<<H 1/2c!A.iuMAU|^3 P:lYENoYEND 3/4-:YEN>>" !C

     --------------------------------------------------------------

  26.2.1. MUA u{|!

   YEN]NOTACUR@"C,CURaa|rCURP:+--a-ou{|!!A^1^3NOTO mutt!B pine!Belm!B
   and mail!AYENHCURI GUI CURP:+--a-ou{|!!A ^1^3NOTO balsa!B xfmail
   uYENuYEN!C |^1YEN~!AAU|^3S:o !S: 1/2AEAo/-a-o!" ^1^3NOTO WWW AsA:y
   3/4^1!C ^3o"C,u{|!.|P:lYENo^3B^2zYENaeu^1 !S:P:lYENoYEND
   3/4-:!"!A(c)I-aI^3z^1L(c)IYENs MTA(Y|^3-a-o,U:)(c)I-aINOTO^3z^1L
   TCP "OP:C,>> 1/4P:lYENo!C

     --------------------------------------------------------------

  26.2.2. Mailhost Server Daemon

   FreeBSD ships with sendmail by default, but also support numerous
   other mail server daemons, just some of which include:

     * exim;

     * postfix;

     * qmail.

   The server daemon usually has two functions!X!Xit is responsible
   for receiving incoming mail as well as delivering outgoing mail.
   It is not responsible for the collection of mail using protocols
   such as POP or IMAP to read your email, nor does it allow
   connecting to local mbox or Maildir mailboxes. You may require an
   additional daemon for that.

     A:uS:iOlder versions of sendmail have some serious security
     issues which may result in an attacker gaining local and/or
     remote access to your machine. Make sure that you are running a
     current version to avoid these problems. Optionally, install an
     alternative MTA from the FreeBSD Ports Collection.

     --------------------------------------------------------------

  26.2.3. Email and DNS

   The Domain Name System (DNS) and its daemon named play a large
   role in the delivery of email. In order to deliver mail from your
   site to another, the server daemon will look up the remote site in
   the DNS to determine the host that will receive mail for the
   destination. This process also occurs when mail is sent from a
   remote host to your mail server.

   DNS is responsible for mapping hostnames to IP addresses, as well
   as for storing information specific to mail delivery, known as MX
   records. The MX (Mail eXchanger) record specifies which host, or
   hosts, will receive mail for a particular domain. If you do not
   have an MX record for your hostname or domain, the mail will be
   delivered directly to your host provided you have an A record
   pointing your hostname to your IP address.

   You may view the MX records for any domain by using the host(1)
   command, as seen in the example below:

 % host -t mx FreeBSD.org
 FreeBSD.org mail is handled (pri=10) by mx1.FreeBSD.org

     --------------------------------------------------------------

  26.2.4. Receiving Mail

   Receiving mail for your domain is done by the mail host. It will
   collect all mail sent to your domain and store it either in mbox
   (the default method for storing mail) or Maildir format, depending
   on your configuration. Once mail has been stored, it may either be
   read locally using applications such as mail(1) or mutt, or
   remotely accessed and collected using protocols such as POP or
   IMAP. This means that should you only wish to read mail locally,
   you are not required to install a POP or IMAP server.

     --------------------------------------------------------------

    26.2.4.1. Accessing remote mailboxes using POP and IMAP

   In order to access mailboxes remotely, you are required to have
   access to a POP or IMAP server. These protocols allow users to
   connect to their mailboxes from remote locations with ease. Though
   both POP and IMAP allow users to remotely access mailboxes, IMAP
   offers many advantages, some of which are:

     * IMAP can store messages on a remote server as well as fetch
       them.

     * IMAP supports concurrent updates.

     * IMAP can be extremely useful over low-speed links as it allows
       users to fetch the structure of messages without downloading
       them; it can also perform tasks such as searching on the
       server in order to minimize data transfer between clients and
       servers.

   In order to install a POP or IMAP server, the following steps
   should be performed:

    1. Choose an IMAP or POP server that best suits your needs. The
       following POP and IMAP servers are well known and serve as
       some good examples:

          * qpopper;

          * teapop;

          * imap-uw;

          * courier-imap;

    2. Install the POP or IMAP daemon of your choosing from the ports
       collection.

    3. Where required, modify /etc/inetd.conf to load the POP or IMAP
       server.

     A:uS:iIt should be noted that both POP and IMAP transmit
     information, including username and password credentials in
     clear-text. This means that if you wish to secure the
     transmission of information across these protocols, you should
     consider tunneling sessions over ssh(1). Tunneling sessions is
     described in uU 14.11.8 ,`.

     --------------------------------------------------------------

    26.2.4.2. Accessing local mailboxes

   Mailboxes may be accessed locally by directly utilizing MUAs on
   the server on which the mailbox resides. This can be done using
   applications such as mutt or mail(1).

     --------------------------------------------------------------

  26.2.5. The Mail Host

   The mail host is the name given to a server that is responsible
   for delivering and receiving mail for your host, and possibly your
   network.

     --------------------------------------------------------------

26.3. sendmail Configuration

   Contributed by Christopher Shumway.

   sendmail(8) is the default Mail Transfer Agent (MTA) in FreeBSD.
   sendmail's job is to accept mail from Mail User Agents (MUA) and
   deliver it to the appropriate mailer as defined by its
   configuration file. sendmail can also accept network connections
   and deliver mail to local mailboxes or deliver it to another
   program.

   sendmail uses the following configuration files:

            Filename                         Function                 
   /etc/mail/access           sendmail access database file           
   /etc/mail/aliases          Mailbox aliases                         
   /etc/mail/local-host-names Lists of hosts sendmail accepts mail    
                              for                                     
   /etc/mail/mailer.conf      Mailer program configuration            
   /etc/mail/mailertable      Mailer delivery table                   
   /etc/mail/sendmail.cf      sendmail master configuration file      
   /etc/mail/virtusertable    Virtual users and domain tables         

     --------------------------------------------------------------

  26.3.1. /etc/mail/access

   The access database defines what host(s) or IP addresses have
   access to the local mail server and what kind of access they have.
   Hosts can be listed as OK, REJECT, RELAY or simply passed to
   sendmail's error handling routine with a given mailer error. Hosts
   that are listed as OK, which is the default, are allowed to send
   mail to this host as long as the mail's final destination is the
   local machine. Hosts that are listed as REJECT are rejected for
   all mail connections. Hosts that have the RELAY option for their
   hostname are allowed to send mail for any destination through this
   mail server.

   1/2d"O 26-1. Configuring the sendmail Access Database

 cyberspammer.com                550 We do not accept mail from spammers
 FREE.STEALTH.MAILER@            550 We do not accept mail from spammers
 another.source.of.spam          REJECT
 okay.cyberspammer.com           OK
 128.32                          RELAY

   In this example we have five entries. Mail senders that match the
   left hand side of the table are affected by the action on the
   right side of the table. The first two examples give an error code
   to sendmail's error handling routine. The message is printed to
   the remote host when a mail matches the left hand side of the
   table. The next entry rejects mail from a specific host on the
   Internet, another.source.of.spam. The next entry accepts mail
   connections from a host okay.cyberspammer.com, which is more exact
   than the cyberspammer.com line above. More specific matches
   override less exact matches. The last entry allows relaying of
   electronic mail from hosts with an IP address that begins with
   128.32. These hosts would be able to send mail through this mail
   server that are destined for other mail servers.

   When this file is updated, you need to run make in /etc/mail/ to
   update the database.

     --------------------------------------------------------------

  26.3.2. /etc/mail/aliases

   The aliases database contains a list of virtual mailboxes that are
   expanded to other user(s), files, programs or other aliases. Here
   are a few examples that can be used in /etc/mail/aliases:

   1/2d"O 26-2. Mail Aliases

 root: localuser
 ftp-bugs: joe,eric,paul
 bit.bucket:  /dev/null
 procmail: "|/usr/local/bin/procmail"

   The file format is simple; the mailbox name on the left side of
   the colon is expanded to the target(s) on the right. The first
   example simply expands the mailbox root to the mailbox localuser,
   which is then looked up again in the aliases database. If no match
   is found, then the message is delivered to the local user
   localuser. The next example shows a mail list. Mail to the mailbox
   ftp-bugs is expanded to the three local mailboxes joe, eric, and
   paul. Note that a remote mailbox could be specified as
   <user@example.com>. The next example shows writing mail to a file,
   in this case /dev/null. The last example shows sending mail to a
   program, in this case the mail message is written to the standard
   input of /usr/local/bin/procmail through a UNIX pipe.

   When this file is updated, you need to run make in /etc/mail/ to
   update the database.

     --------------------------------------------------------------

  26.3.3. /etc/mail/local-host-names

   This is a list of hostnames sendmail(8) is to accept as the local
   host name. Place any domains or hosts that sendmail is to be
   receiving mail for. For example, if this mail server was to accept
   mail for the domain example.com and the host mail.example.com, its
   local-host-names might look something like this:

 example.com
 mail.example.com

   When this file is updated, sendmail(8) needs to be restarted to
   read the changes.

     --------------------------------------------------------------

  26.3.4. /etc/mail/sendmail.cf

   sendmail's master configuration file, sendmail.cf controls the
   overall behavior of sendmail, including everything from rewriting
   e-mail addresses to printing rejection messages to remote mail
   servers. Naturally, with such a diverse role, this configuration
   file is quite complex and its details are a bit out of the scope
   of this section. Fortunately, this file rarely needs to be changed
   for standard mail servers.

   The master sendmail configuration file can be built from m4(1)
   macros that define the features and behavior of sendmail. Please
   see /usr/src/contrib/sendmail/cf/README for some of the details.

   When changes to this file are made, sendmail needs to be restarted
   for the changes to take effect.

     --------------------------------------------------------------

  26.3.5. /etc/mail/virtusertable

   The virtusertable maps mail addresses for virtual domains and
   mailboxes to real mailboxes. These mailboxes can be local, remote,
   aliases defined in /etc/mail/aliases or files.

   1/2d"O 26-3. Example Virtual Domain Mail Map

 root@example.com                root
 postmaster@example.com          postmaster@noc.example.net
 @example.com                    joe

   In the above example, we have a mapping for a domain example.com.
   This file is processed in a first match order down the file. The
   first item maps <root@example.com> to the local mailbox root. The
   next entry maps <postmaster@example.com> to the mailbox postmaster
   on the host noc.example.net. Finally, if nothing from example.com
   has matched so far, it will match the last mapping, which matches
   every other mail message addressed to someone at example.com. This
   will be mapped to the local mailbox joe.

     --------------------------------------------------------------

26.4. Changing Your Mail Transfer Agent

   Written by Andrew Boothman. Information taken from e-mails written
   by Gregory Neil Shapiro.

   As already mentioned, FreeBSD comes with sendmail already
   installed as your MTA (Mail Transfer Agent). Therefore by default
   it is in charge of your outgoing and incoming mail.

   However, for a variety of reasons, some system administrators want
   to change their system's MTA. These reasons range from simply
   wanting to try out another MTA to needing a specific feature or
   package which relies on another mailer. Fortunately, whatever the
   reason, FreeBSD makes it easy to make the change.

     --------------------------------------------------------------

  26.4.1. Install a New MTA

   You have a wide choice of MTAs available. A good starting point is
   the FreeBSD Ports Collection where you will be able to find many.
   Of course you are free to use any MTA you want from any location,
   as long as you can make it run under FreeBSD.

   Start by installing your new MTA. Once it is installed it gives
   you a chance to decide if it really fulfills your needs, and also
   gives you the opportunity to configure your new software before
   getting it to take over from sendmail. When doing this, you should
   be sure that installing the new software will not attempt to
   overwrite system binaries such as /usr/bin/sendmail. Otherwise,
   your new mail software has essentially been put into service
   before you have configured it.

   Please refer to your chosen MTA's documentation for information on
   how to configure the software you have chosen.

     --------------------------------------------------------------

  26.4.2. Disable sendmail

   The procedure used to start sendmail changed significantly between
   4.5-RELEASE, 4.6-RELEASE, and later releases. Therefore, the
   procedure used to disable it is subtly different.

     A:uS:iIf you disable sendmail's outgoing mail service, it is
     important that you replace it with an alternative mail delivery
     system. If you choose not to, system functions such as
     periodic(8) will be unable to deliver their results by e-mail as
     they would normally expect to. Many parts of your system may
     expect to have a functional sendmail-compatible system. If
     applications continue to use sendmail's binaries to try to send
     e-mail after you have disabled them, mail could go into an
     inactive sendmail queue, and never be delivered.

     --------------------------------------------------------------

    26.4.2.1. FreeBSD 4.5-STABLE before 2002/4/4 and Earlier (Including
    4.5-RELEASE and Earlier)

   Enter:

 sendmail_enable="NO"

   into /etc/rc.conf. This will disable sendmail's incoming mail
   service, but if /etc/mail/mailer.conf (see below) is not changed,
   sendmail will still be used to send e-mail.

     --------------------------------------------------------------

    26.4.2.2. FreeBSD 4.5-STABLE after 2002/4/4 (Including 4.6-RELEASE
    and Later)

   In order to completely disable sendmail, including the outgoing
   mail service, you must use

 sendmail_enable="NONE"

   in /etc/rc.conf.

   If you only want to disable sendmail's incoming mail service, you
   should set

 sendmail_enable="NO"

   in /etc/rc.conf. However, if incoming mail is disabled, local
   delivery will still function. More information on sendmail's
   startup options is available from the rc.sendmail(8) manual page.

     --------------------------------------------------------------

    26.4.2.3. FreeBSD 5.0-STABLE and Later

   In order to completely disable sendmail, including the outgoing
   mail service, you must use

 sendmail_enable="NO"
 sendmail_submit_enable="NO"
 sendmail_outbound_enable="NO"
 sendmail_msp_queue_enable="NO"

   in /etc/rc.conf.

   If you only want to disable sendmail's incoming mail service, you
   should set

 sendmail_enable="NO"

   in /etc/rc.conf. More information on sendmail's startup options is
   available from the rc.sendmail(8) manual page.

     --------------------------------------------------------------

  26.4.3. Running Your New MTA on Boot

   You may have a choice of two methods for running your new MTA on
   boot, again depending on what version of FreeBSD you are running.

     --------------------------------------------------------------

    26.4.3.1. FreeBSD 4.5-STABLE before 2002/4/11 (Including 4.5-RELEASE
    and Earlier)

   Add a script to /usr/local/etc/rc.d/ that ends in .sh and is
   executable by root. The script should accept start and stop
   parameters. At startup time the system scripts will execute the
   command

 /usr/local/etc/rc.d/supermailer.sh start

   which you can also use to manually start the server. At shutdown
   time, the system scripts will use the stop option, running the
   command

 /usr/local/etc/rc.d/supermailer.sh stop

   which you can also use to manually stop the server while the
   system is running.

     --------------------------------------------------------------

    26.4.3.2. FreeBSD 4.5-STABLE after 2002/4/11 (Including 4.6-RELEASE
    and Later)

   With later versions of FreeBSD, you can use the above method or
   you can set

 mta_start_script="filename"

   in /etc/rc.conf, where filename is the name of some script that
   you want executed at boot to start your MTA.

     --------------------------------------------------------------

  26.4.4. Replacing sendmail as the System's Default Mailer

   The program sendmail is so ubiquitous as standard software on UNIX
   systems that some software just assumes it is already installed
   and configured. For this reason, many alternative MTA's provide
   their own compatible implementations of the sendmail command-line
   interface; this facilitates using them as !S:drop-in!"
   replacements for sendmail.

   Therefore, if you are using an alternative mailer, you will need
   to make sure that software trying to execute standard sendmail
   binaries such as /usr/bin/sendmail actually executes your chosen
   mailer instead. Fortunately, FreeBSD provides a system called
   mailwrapper(8) that does this job for you.

   When sendmail is operating as installed, you will find something
   like the following in /etc/mail/mailer.conf:

 sendmail         /usr/libexec/sendmail/sendmail
 send-mail       /usr/libexec/sendmail/sendmail
 mailq           /usr/libexec/sendmail/sendmail
 newaliases      /usr/libexec/sendmail/sendmail
 hoststat        /usr/libexec/sendmail/sendmail
 purgestat       /usr/libexec/sendmail/sendmail

   This means that when any of these common commands (such as
   sendmail itself) are run, the system actually invokes a copy of
   mailwrapper named sendmail, which checks mailer.conf and executes
   /usr/libexec/sendmail/sendmail instead. This system makes it easy
   to change what binaries are actually executed when these default
   sendmail functions are invoked.

   Therefore if you wanted /usr/local/supermailer/bin/sendmail-compat
   to be run instead of sendmail, you could change
   /etc/mail/mailer.conf to read:

 sendmail         /usr/local/supermailer/bin/sendmail-compat
 send-mail       /usr/local/supermailer/bin/sendmail-compat
 mailq           /usr/local/supermailer/bin/mailq-compat
 newaliases      /usr/local/supermailer/bin/newaliases-compat
 hoststat        /usr/local/supermailer/bin/hoststat-compat
 purgestat       /usr/local/supermailer/bin/purgestat-compat

     --------------------------------------------------------------

  26.4.5. Finishing

   Once you have everything configured the way you want it, you
   should either kill the sendmail processes that you no longer need
   and start the processes belonging to your new software, or simply
   reboot. Rebooting will also give you the opportunity to ensure
   that you have correctly configured your system to start your new
   MTA automatically on boot.

     --------------------------------------------------------------

26.5. Troubleshooting

   26.5.1. Why do I have to use the FQDN for hosts on my site?

   26.5.2.

   26.5.3.

   26.5.4. Why do I keep getting !S:Relaying Denied!" errors when
   sending mail from other hosts?

   26.5.1. Why do I have to use the FQDN for hosts on my site?

   You will probably find that the host is actually in a different
   domain; for example, if you are in foo.bar.edu and you wish to
   reach a host called mumble in the bar.edu domain, you will have to
   refer to it by the fully-qualified domain name, mumble.bar.edu,
   instead of just mumble.

   Traditionally, this was allowed by BSD BIND resolvers. However the
   current version of BIND that ships with FreeBSD no longer provides
   default abbreviations for non-fully qualified domain names other
   than the domain you are in. So an unqualified host mumble must
   either be found as mumble.foo.bar.edu, or it will be searched for
   in the root domain.

   This is different from the previous behavior, where the search
   continued across mumble.bar.edu, and mumble.edu. Have a look at
   RFC 1535 for why this was considered bad practice, or even a
   security hole.

   As a good workaround, you can place the line:

 search foo.bar.edu bar.edu

   instead of the previous:

 domain foo.bar.edu

   into your /etc/resolv.conf. However, make sure that the search
   order does not go beyond the !S:boundary between local and public
   administration!", as RFC 1535 calls it.

   26.5.2.

   sendmail says !S:mail loops back to myself!"

   This is answered in the sendmail FAQ as follows:

 I'm getting these error messages:

 553 MX list for domain.net points back to relay.domain.net
 554 <user@domain.net>... Local configuration error

 How can I solve this problem?

 You have asked mail to the domain (e.g., domain.net) to be
 forwarded to a specific host (in this case, relay.domain.net)
 by using an MX record, but the relay machine does not recognize
 itself as domain.net. Add domain.net to /etc/mail/local-host-names
 [known as /etc/sendmail.cw prior to version 8.10]
 (if you are using FEATURE(use_cw_file)) or add !S:Cw domain.net!"
 to /etc/mail/sendmail.cf.

   The sendmail FAQ can be found at http://www.sendmail.org/faq/ and
   is recommended reading if you want to do any !S:tweaking!" of your
   mail setup.

   26.5.3.

   How can I run a mail server on a dial-up PPP host?

   You want to connect a FreeBSD box on a LAN to the Internet. The
   FreeBSD box will be a mail gateway for the LAN. The PPP connection
   is non-dedicated.

   There are at least two ways to do this. One way is to use UUCP.

   Another way is to get a full-time Internet server to provide
   secondary MX services for your domain. For example, if your
   company's domain is example.com and your Internet service provider
   has set example.net up to provide secondary MX services to your
   domain:

 example.com.          MX        10      example.com.
                       MX        20      example.net.

   Only one host should be specified as the final recipient (add Cw
   example.com in /etc/mail/sendmail.cf on example.com).

   When the sending sendmail is trying to deliver the mail it will
   try to connect to you (example.com) over the modem link. It will
   most likely time out because you are not online. The program
   sendmail will automatically deliver it to the secondary MX site,
   i.e. your Internet provider (example.net). The secondary MX site
   will then periodically try to connect to your host and deliver the
   mail to the primary MX host (example.com).

   You might want to use something like this as a login script:

 #!/bin/sh
 # Put me in /usr/local/bin/pppmyisp
 ( sleep 60 ; /usr/sbin/sendmail -q ) &
 /usr/sbin/ppp -direct pppmyisp

   If you are going to create a separate login script for a user you
   could use sendmail -qRexample.com instead in the script above.
   This will force all mail in your queue for example.com to be
   processed immediately.

   A further refinement of the situation is as follows:

   Message stolen from the FreeBSD Internet service provider's P:l>>
   1/4 1/2 * 3/4A.

 > we provide the secondary MX for a customer. The customer connects to
 > our services several times a day automatically to get the mails to
 > his primary MX (We do not call his site when a mail for his domains
 > arrived). Our sendmail sends the mailqueue every 30 minutes. At the
 > moment he has to stay 30 minutes online to be sure that all mail is
 > gone to the primary MX.
 >
 > Is there a command that would initiate sendmail to send all the mails
 > now? The user has not root-privileges on our machine of course.

 In the !S:privacy flags!" section of sendmail.cf, there is a
 definition Opgoaway,restrictqrun

 Remove restrictqrun to allow non-root users to start the queue processing.
 You might also like to rearrange the MXs. We are the 1st MX for our
 customers like this, and we have defined:

 # If we are the best MX for a host, try directly instead of generating
 # local config error.
 OwTrue

 That way a remote site will deliver straight to you, without trying
 the customer connection.  You then send to your customer.  Only works for
 !S:hosts!", so you need to get your customer to name their mail
 machine !S:customer.com!" as well as
 !S:hostname.customer.com!" in the DNS.  Just put an A record in
 the DNS for !S:customer.com!".

   26.5.4. Why do I keep getting !S:Relaying Denied!" errors when
   sending mail from other hosts?

   In default FreeBSD installations, sendmail is configured to only
   send mail from the host it is running on. For example, if a POP
   server is available, then users will be able to check mail from
   school, work, or other remote locations but they still will not be
   able to send outgoing emails from outside locations. Typically, a
   few moments after the attempt, an email will be sent from
   MAILER-DAEMON with a !S:5.7 Relaying Denied!" error message.

   There are several ways to get around this. The most
   straightforward solution is to put your ISP's address in a
   relay-domains file at /etc/mail/relay-domains. A quick way to do
   this would be:

 # echo "your.isp.example.com" > /etc/mail/relay-domains

   After creating or editing this file you must restart sendmail.
   This works great if you are a server administrator and do not wish
   to send mail locally, or would like to use a point and click
   client/system on another machine or even another ISP. It is also
   very useful if you only have one or two email accounts set up. If
   there is a large number of addresses to add, you can simply open
   this file in your favorite text editor and then add the domains,
   one per line:

 your.isp.example.com
 other.isp.example.net
 users-isp.example.org
 www.example.org

   Now any mail sent through your system, by any host in this list
   (provided the user has an account on your system), will succeed.
   This is a very nice way to allow users to send mail from your
   system remotely without allowing people to send SPAM through your
   system.

     --------------------------------------------------------------

26.6. Advanced Topics

   The following section covers more involved topics such as mail
   configuration and setting up mail for your entire domain.

     --------------------------------------------------------------

  26.6.1. Basic Configuration

   Out of the box, you should be able to send email to external hosts
   as long as you have set up /etc/resolv.conf or are running your
   own name server. If you would like to have mail for your host
   delivered to the MTA (e.g., sendmail) on your own FreeBSD host,
   there are two methods:

     * Run your own name server and have your own domain. For
       example, FreeBSD.org

     * Get mail delivered directly to your host. This is done by
       delivering mail directly to the current DNS name for your
       machine. For example, example.FreeBSD.org.

   Regardless of which of the above you choose, in order to have mail
   delivered directly to your host, it must have a permanent static
   IP address (not a dynamic address, as with most PPP dial-up
   configurations). If you are behind a firewall, it must pass SMTP
   traffic on to you. If you want to receive mail directly at your
   host, you need to be sure of either of two things:

     * Make sure that the (lowest-numbered) MX record in your DNS
       points to your host's IP address.

     * Make sure there is no MX entry in your DNS for your host.

   Either of the above will allow you to receive mail directly at
   your host.

   Try this:

 # hostname
 example.FreeBSD.org
 # host example.FreeBSD.org
 example.FreeBSD.org has address 204.216.27.XX

   If that is what you see, mail directly to
   <yourlogin@example.FreeBSD.org> should work without problems
   (assuming sendmail is running correctly on example.FreeBSD.org).

   If instead you see something like this:

 # host example.FreeBSD.org
 example.FreeBSD.org has address 204.216.27.XX
 example.FreeBSD.org mail is handled (pri=10) by hub.FreeBSD.org

   All mail sent to your host (example.FreeBSD.org) will end up being
   collected on hub under the same username instead of being sent
   directly to your host.

   The above information is handled by your DNS server. The DNS
   record that carries mail routing information is the Mail eXchange
   entry. If no MX record exists, mail will be delivered directly to
   the host by way of its IP address.

   The MX entry for freefall.FreeBSD.org at one time looked like
   this:

 freefall                MX      30      mail.crl.net
 freefall                MX      40      agora.rdrop.com
 freefall                MX      10      freefall.FreeBSD.org
 freefall                MX      20      who.cdrom.com

   As you can see, freefall had many MX entries. The lowest MX number
   is the host that receives mail directly if available; if it is not
   accessible for some reason, the others (sometimes called !S:backup
   MXes!") accept messages temporarily, and pass it along when a
   lower-numbered host becomes available, eventually to the
   lowest-numbered host.

   Alternate MX sites should have separate Internet connections from
   your own in order to be most useful. Your ISP or another friendly
   site should have no problem providing this service for you.

     --------------------------------------------------------------

  26.6.2. Mail for Your Domain

   In order to set up a !S:mailhost!" (a.k.a. mail server) you need
   to have any mail sent to various workstations directed to it.
   Basically, you want to !S:claim!" any mail for any hostname in
   your domain (in this case *.FreeBSD.org) and divert it to your
   mail server so your users can receive their mail on the master
   mail server.

   To make life easiest, a user account with the same username should
   exist on both machines. Use adduser(8) to do this.

   The mailhost you will be using must be the designated mail
   exchanger for each workstation on the network. This is done in
   your DNS configuration like so:

 example.FreeBSD.org     A       204.216.27.XX           ; Workstation
                         MX      10 hub.FreeBSD.org      ; Mailhost

   This will redirect mail for the workstation to the mailhost no
   matter where the A record points. The mail is sent to the MX host.

   You cannot do this yourself unless you are running a DNS server.
   If you are not, or cannot run your own DNS server, talk to your
   ISP or whoever provides your DNS.

   If you are doing virtual email hosting, the following information
   will come in handy. For this example, we will assume you have a
   customer with his own domain, in this case customer1.org, and you
   want all the mail for customer1.org sent to your mailhost,
   mail.myhost.com. The entry in your DNS should look like this:

 customer1.org           MX      10      mail.myhost.com

   You do not need an A record for customer1.org if you only want to
   handle email for that domain.

     -a`: Be aware that pinging customer1.org will not work unless an
     A record exists for it.

   The last thing that you must do is tell sendmail on your mailhost
   what domains and/or hostnames it should be accepting mail for.
   There are a few different ways this can be done. Either of the
   following will work:

     * Add the hosts to your /etc/mail/local-host-names file if you
       are using the FEATURE(use_cw_file). If you are using a version
       of sendmail earlier than 8.10, the file is /etc/sendmail.cw.

     * Add a Cwyour.host.com line to your /etc/sendmail.cf or
       /etc/mail/sendmail.cf if you are using sendmail 8.10 or
       higher.

     --------------------------------------------------------------

26.7. SMTP with UUCP

   The sendmail configuration that ships with FreeBSD is designed for
   sites that connect directly to the Internet. Sites that wish to
   exchange their mail via UUCP must install another sendmail
   configuration file.

   Tweaking /etc/mail/sendmail.cf manually is an advanced topic.
   sendmail version 8 generates config files via m4(1) preprocessing,
   where the actual configuration occurs on a higher abstraction
   level. The m4(1) configuration files can be found under
   /usr/share/sendmail/cf. The file README in the cf directory can
   serve as a basic introduction to m4(1) configuration.

   The best way to support UUCP delivery is to use the mailertable
   feature. This creates a database that sendmail can use to make
   routing decisions.

   First, you have to create your .mc file. The directory
   /usr/share/sendmail/cf/cf contains a few examples. Assuming you
   have named your file foo.mc, all you need to do in order to
   convert it into a valid sendmail.cf is:

 # cd /etc/mail
 # make foo.cf
 # cp foo.cf /etc/mail/sendmail.cf

   A typical .mc file might look like:

 VERSIONID(`Your version number') OSTYPE(bsd4.4)

 FEATURE(accept_unresolvable_domains)
 FEATURE(nocanonify)
 FEATURE(mailertable, `hash -o /etc/mail/mailertable')

 define(`UUCP_RELAY', your.uucp.relay)
 define(`UUCP_MAX_SIZE', 200000)
 define(`confDONT_PROBE_INTERFACES')

 MAILER(local)
 MAILER(smtp)
 MAILER(uucp)

 Cw    your.alias.host.name
 Cw    youruucpnodename.UUCP

   The lines containing accept_unresolvable_domains, nocanonify, and
   confDONT_PROBE_INTERFACES features will prevent any usage of the
   DNS during mail delivery. The UUCP_RELAY clause is needed to
   support UUCP delivery. Simply put an Internet hostname there that
   is able to handle .UUCP pseudo-domain addresses; most likely, you
   will enter the mail relay of your ISP there.

   Once you have this, you need an /etc/mail/mailertable file. If you
   have only one link to the outside that is used for all your mails,
   the following file will suffice:

 #
 # makemap hash /etc/mail/mailertable.db < /etc/mail/mailertable
 .                             uucp-dom:your.uucp.relay

   A more complex example might look like this:

 #
 # makemap hash /etc/mail/mailertable.db < /etc/mail/mailertable
 #
 horus.interface-business.de   uucp-dom:horus
 .interface-business.de        uucp-dom:if-bus
 interface-business.de         uucp-dom:if-bus
 .heep.sax.de                  smtp8:%1
 horus.UUCP                    uucp-dom:horus
 if-bus.UUCP                   uucp-dom:if-bus
 .                             uucp-dom:

   The first three lines handle special cases where domain-addressed
   mail should not be sent out to the default route, but instead to
   some UUCP neighbor in order to !S:shortcut!" the delivery path.
   The next line handles mail to the local Ethernet domain that can
   be delivered using SMTP. Finally, the UUCP neighbors are mentioned
   in the .UUCP pseudo-domain notation, to allow for a uucp-neighbor
   !recipient override of the default rules. The last line is always
   a single dot, matching everything else, with UUCP delivery to a
   UUCP neighbor that serves as your universal mail gateway to the
   world. All of the node names behind the uucp-dom: keyword must be
   valid UUCP neighbors, as you can verify using the command uuname.

   As a reminder that this file needs to be converted into a DBM
   database file before use. The command line to accomplish this is
   best placed as a comment at the top of the mailertable file. You
   always have to execute this command each time you change your
   mailertable file.

   Final hint: if you are uncertain whether some particular mail
   routing would work, remember the -bt option to sendmail. It starts
   sendmail in address test mode; simply enter 3,0, followed by the
   address you wish to test for the mail routing. The last line tells
   you the used internal mail agent, the destination host this agent
   will be called with, and the (possibly translated) address. Leave
   this mode by typing Ctrl+D.

 % sendmail -bt
 ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
 Enter <ruleset> <address>
 > 3,0 foo@example.com
 canonify           input: foo @ example . com
 ...
 parse            returns: $# uucp-dom $@ your.uucp.relay $: foo < @ example . com . >
 > ^D

     --------------------------------------------------------------

26.8. Setting Up to Send Only

   Contributed by Bill Moran.

   There are many instances where you may only want to send mail
   through a relay. Some examples are:

     * Your computer is a desktop machine, but you want to use
       programs such as send-pr(1). To do so, you should use your
       ISP's mail relay.

     * The computer is a server that does not handle mail locally,
       but needs to pass off all mail to a relay for processing.

   Just about any MTA is capable of filling this particular niche.
   Unfortunately, it can be very difficult to properly configure a
   full-featured MTA just to handle offloading mail. Programs such as
   sendmail and postfix are largely overkill for this use.

   Additionally, if you are using a typical Internet access service,
   your agreement may forbid you from running a !S:mail server!".

   The easiest way to fulfill those needs is to install the
   mail/ssmtp port. Execute the following commands as root:

 # cd /usr/ports/mail/ssmtp
 # make install replace clean

   Once installed, mail/ssmtp can be configured with a four-line file
   located at /usr/local/etc/ssmtp/ssmtp.conf:

 root=yourrealemail@example.com
 mailhub=mail.example.com
 rewriteDomain=example.com
 hostname=_HOSTNAME_

   Make sure you use your real email address for root. Enter your
   ISP's outgoing mail relay in place of mail.example.com (some ISPs
   call this the !S:outgoing mail server!" or !S:SMTP server!").

   Make sure you disable sendmail, including the outgoing mail
   service. See uU 26.4.2 ,` for details.

   mail/ssmtp has some other options available. See the example
   configuration file in /usr/local/etc/ssmtp or the manual page of
   ssmtp for some examples and more information.

   Setting up ssmtp in this manner will allow any software on your
   computer that needs to send mail to function properly, while not
   violating your ISP's usage policy or allowing your computer to be
   hijacked for spamming.

     --------------------------------------------------------------

26.9. Using Mail with a Dialup Connection

   If you have a static IP address, you should not need to adjust
   anything from the defaults. Set your host name to your assigned
   Internet name and sendmail will do the rest.

   If you have a dynamically assigned IP number and use a dialup PPP
   connection to the Internet, you will probably have a mailbox on
   your ISPs mail server. Let's assume your ISP's domain is
   example.net, and that your user name is user, you have called your
   machine bsd.home, and your ISP has told you that you may use
   relay.example.net as a mail relay.

   In order to retrieve mail from your mailbox, you must install a
   retrieval agent. The fetchmail utility is a good choice as it
   supports many different protocols. This program is available as a
   package or from the Ports Collection (mail/fetchmail). Usually,
   your ISP will provide POP. If you are using user PPP, you can
   automatically fetch your mail when an Internet connection is
   established with the following entry in /etc/ppp/ppp.linkup:

 MYADDR:
 !bg su user -c fetchmail

   If you are using sendmail (as shown below) to deliver mail to
   non-local accounts, you probably want to have sendmail process
   your mailqueue as soon as your Internet connection is established.
   To do this, put this command after the fetchmail command in
   /etc/ppp/ppp.linkup:

   !bg su user -c "sendmail -q"

   Assume that you have an account for user on bsd.home. In the home
   directory of user on bsd.home, create a .fetchmailrc file:

 poll example.net protocol pop3 fetchall pass MySecret

   This file should not be readable by anyone except user as it
   contains the password MySecret.

   In order to send mail with the correct from: header, you must tell
   sendmail to use <user@example.net> rather than <user@bsd.home>.
   You may also wish to tell sendmail to send all mail via
   relay.example.net, allowing quicker mail transmission.

   The following .mc file should suffice:

 VERSIONID(`bsd.home.mc version 1.0')
 OSTYPE(bsd4.4)dnl
 FEATURE(nouucp)dnl
 MAILER(local)dnl
 MAILER(smtp)dnl
 Cwlocalhost
 Cwbsd.home
 MASQUERADE_AS(`example.net')dnl
 FEATURE(allmasquerade)dnl
 FEATURE(masquerade_envelope)dnl
 FEATURE(nocanonify)dnl
 FEATURE(nodns)dnl
 define(`SMART_HOST', `relay.example.net')
 Dmbsd.home
 define(`confDOMAIN_NAME',`bsd.home')dnl
 define(`confDELIVERY_MODE',`deferred')dnl

   Refer to the previous section for details of how to turn this .mc
   file into a sendmail.cf file. Also, do not forget to restart
   sendmail after updating sendmail.cf.

     --------------------------------------------------------------

26.10. SMTP Authentication

   Written by James Gorham.

   Having SMTP Authentication in place on your mail server has a
   number of benefits. SMTP Authentication can add another layer of
   security to sendmail, and has the benefit of giving mobile users
   who switch hosts the ability to use the same mail server without
   the need to reconfigure their mail client settings each time.

    1. Install security/cyrus-sasl2 from the ports. You can find this
       port in security/cyrus-sasl2. The security/cyrus-sasl2 port
       supports a number of compile-time options. For the SMTP
       Authentication method we will be using here, make sure that
       the LOGIN option is not disabled.

    2. After installing security/cyrus-sasl2, edit
       /usr/local/lib/sasl2/Sendmail.conf (or create it if it does
       not exist) and add the following line:

 pwcheck_method: saslauthd

    3. Next, install security/cyrus-sasl2-saslauthd, edit
       /etc/rc.conf to add the following line:

 saslauthd_enable="YES"

       and finally start the saslauthd daemon:

 # /usr/local/etc/rc.d/saslauthd start

       This daemon serves as a broker for sendmail to authenticate
       against your FreeBSD passwd database. This saves the trouble
       of creating a new set of usernames and passwords for each user
       that needs to use SMTP authentication, and keeps the login and
       mail password the same.

    4. Now edit /etc/make.conf and add the following lines:

 SENDMAIL_CFLAGS=-I/usr/local/include/sasl -DSASL
 SENDMAIL_LDFLAGS=-L/usr/local/lib
 SENDMAIL_LDADD=-lsasl2

       These lines will give sendmail the proper configuration
       options for linking to cyrus-sasl2 at compile time. Make sure
       that cyrus-sasl2 has been installed before recompiling
       sendmail.

    5. Recompile sendmail by executing the following commands:

 # cd /usr/src/lib/libsmutil
 # make cleandir && make obj && make
 # cd /usr/src/lib/libsm
 # make cleandir && make obj && make
 # cd /usr/src/usr.sbin/sendmail
 # make cleandir && make obj && make && make install

       The compile of sendmail should not have any problems if
       /usr/src has not been changed extensively and the shared
       libraries it needs are available.

    6. After sendmail has been compiled and reinstalled, edit your
       /etc/mail/freebsd.mc file (or whichever file you use as your
       .mc file. Many administrators choose to use the output from
       hostname(1) as the .mc file for uniqueness). Add these lines
       to it:

 dnl set SASL options
 TRUST_AUTH_MECH(`GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN')dnl
 define(`confAUTH_MECHANISMS', `GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN')dnl

       These options configure the different methods available to
       sendmail for authenticating users. If you would like to use a
       method other than pwcheck, please see the included
       documentation.

    7. Finally, run make(1) while in /etc/mail. That will run your
       new .mc file and create a .cf file named freebsd.cf (or
       whatever name you have used for your .mc file). Then use the
       command make install restart, which will copy the file to
       sendmail.cf, and will properly restart sendmail. For more
       information about this process, you should refer to
       /etc/mail/Makefile.

   If all has gone correctly, you should be able to enter your login
   information into the mail client and send a test message. For
   further investigation, set the LogLevel of sendmail to 13 and
   watch /var/log/maillog for any errors.

   For more information, please see the sendmail page regarding  
   SMTP authentication.

     --------------------------------------------------------------

26.11. Mail User Agents

   Contributed by Marc Silver.

   A Mail User Agent (MUA) is an application that is used to send and
   receive email. Furthermore, as email !S:evolves!" and becomes more
   complex, MUA's are becoming increasingly powerful in the way they
   interact with email; this gives users increased functionality and
   flexibility. FreeBSD contains support for numerous mail user
   agents, all of which can be easily installed using the FreeBSD
   Ports Collection. Users may choose between graphical email clients
   such as evolution or balsa, console based clients such as mutt,
   pine or mail, or the web interfaces used by some large
   organizations.

     --------------------------------------------------------------

  26.11.1. mail

   mail(1) is the default Mail User Agent (MUA) in FreeBSD. It is a
   console based MUA that offers all the basic functionality required
   to send and receive text-based email, though it is limited in
   interaction abilities with attachments and can only support local
   mailboxes.

   Although mail does not natively support interaction with POP or
   IMAP servers, these mailboxes may be downloaded to a local mbox
   file using an application such as fetchmail, which will be
   discussed later in this chapter (uU 26.12 ,`).

   In order to send and receive email, simply invoke the mail command
   as per the following example:

 % mail

   The contents of the user mailbox in /var/mail are automatically
   read by the mail utility. Should the mailbox be empty, the utility
   exits with a message indicating that no mails could be found. Once
   the mailbox has been read, the application interface is started,
   and a list of messages will be displayed. Messages are
   automatically numbered, as can be seen in the following example:

 Mail version 8.1 6/6/93.  Type ? for help.
 "/var/mail/marcs": 3 messages 3 new
 >N  1 root@localhost        Mon Mar  8 14:05  14/510   "test"
  N  2 root@localhost        Mon Mar  8 14:05  14/509   "user account"
  N  3 root@localhost        Mon Mar  8 14:05  14/509   "sample"

   Messages can now be read by using the t mail command, suffixed by
   the message number that should be displayed. In this example, we
   will read the first email:

 & t 1
 Message 1:
 From root@localhost  Mon Mar  8 14:05:52 2004
 X-Original-To: marcs@localhost
 Delivered-To: marcs@localhost
 To: marcs@localhost
 Subject: test
 Date: Mon,  8 Mar 2004 14:05:52 +0200 (SAST)
 From: root@localhost (Charlie Root)

 This is a test message, please reply if you receive it.

   As can be seen in the example above, the t key will cause the
   message to be displayed with full headers. To display the list of
   messages again, the h key should be used.

   If the email requires a response, you may use mail to reply, by
   using either the R or r mail keys. The R key instructs mail to
   reply only to the sender of the email, while r replies not only to
   the sender, but also to other recipients of the message. You may
   also suffix these commands with the mail number which you would
   like make a reply to. Once this has been done, the response should
   be entered, and the end of the message should be marked by a
   single . on a new line. An example can be seen below:

 & R 1
 To: root@localhost
 Subject: Re: test

 Thank you, I did get your email.
 .
 EOT

   In order to send new email, the m key should be used, followed by
   the recipient email address. Multiple recipients may also be
   specified by separating each address with the , delimiter. The
   subject of the message may then be entered, followed by the
   message contents. The end of the message should be specified by
   putting a single . on a new line.

 & mail root@localhost
 Subject: I mastered mail

 Now I can send and receive email using mail ... :)
 .
 EOT

   While inside the mail utility, the ? command may be used to
   display help at any time, the mail(1) manual page should also be
   consulted for more help with mail.

     -a`: As previously mentioned, the mail(1) command was not
     originally designed to handle attachments, and thus deals with
     them very poorly. Newer MUAs such as mutt handle attachments in
     a much more intelligent way. But should you still wish to use
     the mail command, the converters/mpack port may be of
     considerable use.

     --------------------------------------------------------------

  26.11.2. mutt

   mutt is a small yet very powerful Mail User Agent, with excellent
   features, just some of which include:

     * The ability to thread messages;

     * PGP support for digital signing and encryption of email;

     * MIME Support;

     * Maildir Support;

     * Highly customizable.

   All of these features help to make mutt one of the most advanced
   mail user agents available. See http://www.mutt.org for more
   information on mutt.

   The stable version of mutt may be installed using the mail/mutt
   port, while the current development version may be installed via
   the mail/mutt-devel port. After the port has been installed, mutt
   can be started by issuing the following command:

 % mutt

   mutt will automatically read the contents of the user mailbox in
   /var/mail and display the contents if applicable. If no mails are
   found in the user mailbox, then mutt will wait for commands from
   the user. The example below shows mutt displaying a list of
   messages:

   In order to read an email, simply select it using the cursor keys,
   and press the Enter key. An example of mutt displaying email can
   be seen below:

   As with the mail(1) command, mutt allows users to reply only to
   the sender of the message as well as to all recipients. To reply
   only to the sender of the email, use the r keyboard shortcut. To
   send a group reply, which will be sent to the original sender as
   well as all the message recipients, use the g shortcut.

     -a`: mutt makes use of the vi(1) command as an editor for
     creating and replying to emails. This may be customized by the
     user by creating or editing their own .muttrc file in their home
     directory and setting the editor variable or by setting the
     EDITOR environment variable. See http://www.mutt.org/ for more
     information about configuring mutt.

   In order to compose a new mail message, press m. After a valid
   subject has been given, mutt will start vi(1) and the mail can be
   written. Once the contents of the mail are complete, save and quit
   from vi and mutt will resume, displaying a summary screen of the
   mail that is to be delivered. In order to send the mail, press y.
   An example of the summary screen can be seen below:

   mutt also contains extensive help, which can be accessed from most
   of the menus by pressing the ? key. The top line also displays the
   keyboard shortcuts where appropriate.

     --------------------------------------------------------------

  26.11.3. pine

   pine is aimed at a beginner user, but also includes some advanced
   features.

     A:uS:iThe pine software has had several remote vulnerabilities
     discovered in the past, which allowed remote attackers to
     execute arbitrary code as users on the local system, by the
     action of sending a specially-prepared email. All such known
     problems have been fixed, but the pine code is written in a very
     insecure style and the FreeBSD Security Officer believes there
     are likely to be other undiscovered vulnerabilities. You install
     pine at your own risk.

   The current version of pine may be installed using the mail/pine4
   port. Once the port has installed, pine can be started by issuing
   the following command:

 % pine

   The first time that pine is run it displays a greeting page with a
   brief introduction, as well as a request from the pine development
   team to send an anonymous email message allowing them to judge how
   many users are using their client. To send this anonymous message,
   press Enter, or alternatively press E to exit the greeting without
   sending an anonymous message. An example of the greeting page can
   be seen below:

   Users are then presented with the main menu, which can be easily
   navigated using the cursor keys. This main menu provides shortcuts
   for the composing new mails, browsing of mail directories, and
   even the administration of address book entries. Below the main
   menu, relevant keyboard shortcuts to perform functions specific to
   the task at hand are shown.

   The default directory opened by pine is the inbox. To view the
   message index, press I, or select the MESSAGE INDEX option as seen
   below:

   The message index shows messages in the current directory, and can
   be navigated by using the cursor keys. Highlighted messages can be
   read by pressing the Enter key.

   In the screenshot below, a sample message is displayed by pine.
   Keyboard shortcuts are displayed as a reference at the bottom of
   the screen. An example of one of these shortcuts is the r key,
   which tells the MUA to reply to the current message being
   displayed.

   Replying to an email in pine is done using the pico editor, which
   is installed by default with pine. The pico utility makes it easy
   to navigate around the message and is slightly more forgiving on
   novice users than vi(1) or mail(1). Once the reply is complete,
   the message can be sent by pressing Ctrl+X. The pine application
   will ask for confirmation.

   The pine application can be customized using the SETUP option from
   the main menu. Consult http://www.washington.edu/pine/ for more
   information.

     --------------------------------------------------------------

26.12. Using fetchmail

   Contributed by Marc Silver.

   fetchmail is a full-featured IMAP and POP client which allows
   users to automatically download mail from remote IMAP and POP
   servers and save it into local mailboxes; there it can be accessed
   more easily. fetchmail can be installed using the mail/fetchmail
   port, and offers various features, some of which include:

     * Support of POP3, APOP, KPOP, IMAP, ETRN and ODMR protocols.

     * Ability to forward mail using SMTP, which allows filtering,
       forwarding, and aliasing to function normally.

     * May be run in daemon mode to check periodically for new
       messages.

     * Can retrieve multiple mailboxes and forward them based on
       configuration, to different local users.

   While it is outside the scope of this document to explain all of
   fetchmail's features, some basic features will be explained. The
   fetchmail utility requires a configuration file known as
   .fetchmailrc, in order to run correctly. This file includes server
   information as well as login credentials. Due to the sensitive
   nature of the contents of this file, it is advisable to make it
   readable only by the owner, with the following command:

 % chmod 600 .fetchmailrc

   The following .fetchmailrc serves as an example for downloading a
   single user mailbox using POP. It tells fetchmail to connect to
   example.com using a username of joesoap and a password of XXX.
   This example assumes that the user joesoap is also a user on the
   local system.

 poll example.com protocol pop3 username "joesoap" password "XXX"

   The next example connects to multiple POP and IMAP servers and
   redirects to different local usernames where applicable:

 poll example.com proto pop3:
 user "joesoap", with password "XXX", is "jsoap" here;
 user "andrea", with password "XXXX";
 poll example2.net proto imap:
 user "john", with password "XXXXX", is "myth" here;

   The fetchmail utility can be run in daemon mode by running it with
   the -d flag, followed by the interval (in seconds) that fetchmail
   should poll servers listed in the .fetchmailrc file. The following
   example would cause fetchmail to poll every 600 seconds:

 % fetchmail -d 600

   More information on fetchmail can be found at
   http://fetchmail.berlios.de/.

     --------------------------------------------------------------

26.13. Using procmail

   Contributed by Marc Silver.

   The procmail utility is an incredibly powerful application used to
   filter incoming mail. It allows users to define !S:rules!" which
   can be matched to incoming mails to perform specific functions or
   to reroute mail to alternative mailboxes and/or email addresses.
   procmail can be installed using the mail/procmail port. Once
   installed, it can be directly integrated into most MTAs; consult
   your MTA documentation for more information. Alternatively,
   procmail can be integrated by adding the following line to a
   .forward in the home directory of the user utilizing procmail
   features:

 "|exec /usr/local/bin/procmail || exit 75"

   The following section will display some basic procmail rules, as
   well as brief descriptions on what they do. These rules, and
   others must be inserted into a .procmailrc file, which must reside
   in the user's home directory.

   The majority of these rules can also be found in the procmailex(5)
   manual page.

   Forward all mail from <user@example.com> to an external address of
   <goodmail@example2.com>:

 :0
 * ^From.*user@example.com
 ! goodmail@example2.com

   Forward all mails shorter than 1000 bytes to an external address
   of <goodmail@example2.com>:

 :0
 * < 1000
 ! goodmail@example2.com

   Send all mail sent to <alternate@example.com> into a mailbox
   called alternate:

 :0
 * ^TOalternate@example.com
 alternate

   Send all mail with a subject of !S:Spam!" to /dev/null:

 :0
 ^Subject:.*Spam
 /dev/null

   A useful recipe that parses incoming FreeBSD.org mailing lists and
   places each list in its own mailbox:

 :0
 * ^Sender:.owner-freebsd-\/[^@]+@FreeBSD.ORG
 {
         LISTNAME=${MATCH}
         :0
         * LISTNAME??^\/[^@]+
         FreeBSD-${MATCH}
 }

     --------------------------------------------------------------

                        ^3^1 27. Network Servers

   Reorganized by Murray Stokely.

27.1. .S:z

   This chapter will cover some of the more frequently used network
   services on UNIX systems. We will cover how to install, configure,
   test, and maintain many different types of network services.
   Example configuration files are included throughout this chapter
   for you to benefit from.

   After reading this chapter, you will know:

     * How to manage the inetd daemon.

     * How to set up a network file system.

     * How to set up a network information server for sharing user
       accounts.

     * How to set up automatic network settings using DHCP.

     * How to set up a domain name server.

     * How to set up the Apache HTTP Server.

     * How to set up a File Transfer Protocol (FTP) Server.

     * How to set up a file and print server for Windows clients
       using Samba.

     * How to synchronize the time and date, and set up a time
       server, with the NTP protocol.

   Before reading this chapter, you should:

     * Understand the basics of the /etc/rc scripts.

     * Be familiar with basic network terminology.

     * Know how to install additional third-party software (uU 4
       ^3^1).

     --------------------------------------------------------------

27.2. The inetd !S:Super-Server!"

   Contributed by Chern Lee.

  27.2.1. Overview

   inetd(8) is referred to as the !S:Internet Super-Server!" because
   it manages connections for several services. When a connection is
   received by inetd, it determines which program the connection is
   destined for, spawns the particular process and delegates the
   socket to it (the program is invoked with the service socket as
   its standard input, output and error descriptors). Running one
   instance of inetd reduces the overall system load as compared to
   running each daemon individually in stand-alone mode.

   Primarily, inetd is used to spawn other daemons, but several
   trivial protocols are handled directly, such as chargen, auth, and
   daytime.

   This section will cover the basics in configuring inetd through
   its command-line options and its configuration file,
   /etc/inetd.conf.

     --------------------------------------------------------------

  27.2.2. Settings

   inetd is initialized through the /etc/rc.conf system. The
   inetd_enable option is set to NO by default, but is often times
   turned on by sysinstall with the medium security profile. Placing:

 inetd_enable="YES"

   or

 inetd_enable="NO"

   into /etc/rc.conf can enable or disable inetd starting at boot
   time.

   Additionally, different command-line options can be passed to
   inetd via the inetd_flags option.

     --------------------------------------------------------------

  27.2.3. Command-Line Options

   inetd synopsis:

   inetd [-d] [-l] [-w] [-W] [-c maximum] [-C rate] [-a address |
   hostname] [-p filename] [-R rate] [configuration file]

   -d

           Turn on debugging.

   -l

           Turn on logging of successful connections.

   -w

           Turn on TCP Wrapping for external services (on by
           default).

   -W

           Turn on TCP Wrapping for internal services which are built
           into inetd (on by default).

   -c maximum

           Specify the default maximum number of simultaneous
           invocations of each service; the default is unlimited. May
           be overridden on a per-service basis with the max-child
           parameter.

   -C rate

           Specify the default maximum number of times a service can
           be invoked from a single IP address in one minute; the
           default is unlimited. May be overridden on a per-service
           basis with the max-connections-per-ip-per-minute
           parameter.

   -R rate

           Specify the maximum number of times a service can be
           invoked in one minute; the default is 256. A rate of 0
           allows an unlimited number of invocations.

   -a

           Specify one specific IP address to bind to. Alternatively,
           a hostname can be specified, in which case the IPv4 or
           IPv6 address which corresponds to that hostname is used.
           Usually a hostname is specified when inetd is run inside a
           jail(8), in which case the hostname corresponds to the
           jail(8) environment.

           When hostname specification is used and both IPv4 and IPv6
           bindings are desired, one entry with the appropriate
           protocol type for each binding is required for each
           service in /etc/inetd.conf. For example, a TCP-based
           service would need two entries, one using tcp4 for the
           protocol and the other using tcp6.

   -p

           Specify an alternate file in which to store the process
           ID.

   These options can be passed to inetd using the inetd_flags option
   in /etc/rc.conf. By default, inetd_flags is set to -wW, which
   turns on TCP wrapping for inetd's internal and external services.
   For novice users, these parameters usually do not need to be
   modified or even entered in /etc/rc.conf.

     -a`: An external service is a daemon outside of inetd, which is
     invoked when a connection is received for it. On the other hand,
     an internal service is one that inetd has the facility of
     offering within itself.

     --------------------------------------------------------------

  27.2.4. inetd.conf

   Configuration of inetd is controlled through the /etc/inetd.conf
   file.

   When a modification is made to /etc/inetd.conf, inetd can be
   forced to re-read its configuration file by sending a HangUP
   signal to the inetd process as shown:

   1/2d"O 27-1. Sending inetd a HangUP Signal

 # kill -HUP `cat /var/run/inetd.pid`

   Each line of the configuration file specifies an individual
   daemon. Comments in the file are preceded by a !S:#!". The format
   of /etc/inetd.conf is as follows:

 service-name
 socket-type
 protocol
 {wait|nowait}[/max-child[/max-connections-per-ip-per-minute]]
 user[:group][/login-class]
 server-program
 server-program-arguments

   An example entry for the ftpd daemon using IPv4:

 ftp     stream  tcp     nowait  root    /usr/libexec/ftpd       ftpd -l

   service-name

           This is the service name of the particular daemon. It must
           correspond to a service listed in /etc/services. This
           determines which port inetd must listen to. If a new
           service is being created, it must be placed in
           /etc/services first.

   socket-type

           Either stream, dgram, raw, or seqpacket. stream must be
           used for connection-based, TCP daemons, while dgram is
           used for daemons utilizing the UDP transport protocol.

   protocol

           One of the following:

                  Protocol                    Explanation             
           tcp, tcp4               TCP IPv4                           
           udp, udp4               UDP IPv4                           
           tcp6                    TCP IPv6                           
           udp6                    UDP IPv6                           
           tcp46                   Both TCP IPv4 and v6               
           udp46                   Both UDP IPv4 and v6               

   {wait|nowait}[/max-child[/max-connections-per-ip-per-minute]]

           wait|nowait indicates whether the daemon invoked from
           inetd is able to handle its own socket or not. dgram
           socket types must use the wait option, while stream socket
           daemons, which are usually multi-threaded, should use
           nowait. wait usually hands off multiple sockets to a
           single daemon, while nowait spawns a child daemon for each
           new socket.

           The maximum number of child daemons inetd may spawn can be
           set using the max-child option. If a limit of ten
           instances of a particular daemon is needed, a /10 would be
           placed after nowait.

           In addition to max-child, another option limiting the
           maximum connections from a single place to a particular
           daemon can be enabled. max-connections-per-ip-per-minute
           does just this. A value of ten here would limit any
           particular IP address connecting to a particular service
           to ten attempts per minute. This is useful to prevent
           intentional or unintentional resource consumption and
           Denial of Service (DoS) attacks to a machine.

           In this field, wait or nowait is mandatory. max-child and
           max-connections-per-ip-per-minute are optional.

           A stream-type multi-threaded daemon without any max-child
           or max-connections-per-ip-per-minute limits would simply
           be: nowait.

           The same daemon with a maximum limit of ten daemons would
           read: nowait/10.

           Additionally, the same setup with a limit of twenty
           connections per IP address per minute and a maximum total
           limit of ten child daemons would read: nowait/10/20.

           These options are all utilized by the default settings of
           the fingerd daemon, as seen here:

 finger stream  tcp     nowait/3/10 nobody /usr/libexec/fingerd fingerd -s

   user

           This is the username that the particular daemon should run
           as. Most commonly, daemons run as the root user. For
           security purposes, it is common to find some servers
           running as the daemon user, or the least privileged nobody
           user.

   server-program

           The full path of the daemon to be executed when a
           connection is received. If the daemon is a service
           provided by inetd internally, then internal should be
           used.

   server-program-arguments

           This works in conjunction with server-program by
           specifying the arguments, starting with argv[0], passed to
           the daemon on invocation. If mydaemon -d is the command
           line, mydaemon -d would be the value of
           server-program-arguments. Again, if the daemon is an
           internal service, use internal here.

     --------------------------------------------------------------

  27.2.5. Security

   Depending on the security profile chosen at install, many of
   inetd's daemons may be enabled by default. If there is no apparent
   need for a particular daemon, disable it! Place a !S:#!" in front
   of the daemon in question in /etc/inetd.conf, and then send a
   hangup signal to inetd. Some daemons, such as fingerd, may not be
   desired at all because they provide an attacker with too much
   information.

   Some daemons are not security-conscious and have long, or
   non-existent timeouts for connection attempts. This allows an
   attacker to slowly send connections to a particular daemon, thus
   saturating available resources. It may be a good idea to place
   max-connections-per-ip-per-minute and max-child limitations on
   certain daemons.

   By default, TCP wrapping is turned on. Consult the hosts_access(5)
   manual page for more information on placing TCP restrictions on
   various inetd invoked daemons.

     --------------------------------------------------------------

  27.2.6. Miscellaneous

   daytime, time, echo, discard, chargen, and auth are all internally
   provided services of inetd.

   The auth service provides identity (ident, identd) network
   services, and is configurable to a certain degree.

   Consult the inetd(8) manual page for more in-depth information.

     --------------------------------------------------------------

27.3. Network File System (NFS)

   Reorganized and enhanced by Tom Rhodes. Written by Bill Swingle.

   Among the many different file systems that FreeBSD supports is the
   Network File System, also known as NFS. NFS allows a system to
   share directories and files with others over a network. By using
   NFS, users and programs can access files on remote systems almost
   as if they were local files.

   Some of the most notable benefits that NFS can provide are:

     * Local workstations use less disk space because commonly used
       data can be stored on a single machine and still remain
       accessible to others over the network.

     * There is no need for users to have separate home directories
       on every network machine. Home directories could be set up on
       the NFS server and made available throughout the network.

     * Storage devices such as floppy disks, CDROM drives, and Zip(R)
       drives can be used by other machines on the network. This may
       reduce the number of removable media drives throughout the
       network.

     --------------------------------------------------------------

  27.3.1. How NFS Works

   NFS consists of at least two main parts: a server and one or more
   clients. The client remotely accesses the data that is stored on
   the server machine. In order for this to function properly a few
   processes have to be configured and running.

     -a`: Under FreeBSD 4.X, the portmap utility is used in place of
     the rpcbind utility. Thus, in FreeBSD 4.X the user is required
     to replace every instance of rpcbind with portmap in the
     forthcoming examples.

   The server has to be running the following daemons:

   Daemon                         Description                         
   nfsd    The NFS daemon which services requests from the NFS        
           clients.                                                   
   mountd  The NFS mount daemon which carries out the requests that   
           nfsd(8) passes on to it.                                   
   rpcbind This daemon allows NFS clients to discover which port the  
           NFS server is using.                                       

   The client can also run a daemon, known as nfsiod. The nfsiod
   daemon services the requests from the NFS server. This is
   optional, and improves performance, but is not required for normal
   and correct operation. See the nfsiod(8) manual page for more
   information.

     --------------------------------------------------------------

  27.3.2. Configuring NFS

   NFS configuration is a relatively straightforward process. The
   processes that need to be running can all start at boot time with
   a few modifications to your /etc/rc.conf file.

   On the NFS server, make sure that the following options are
   configured in the /etc/rc.conf file:

 rpcbind_enable="YES"
 nfs_server_enable="YES"
 mountd_flags="-r"

   mountd runs automatically whenever the NFS server is enabled.

   On the client, make sure this option is present in /etc/rc.conf:

 nfs_client_enable="YES"

   The /etc/exports file specifies which file systems NFS should
   export (sometimes referred to as !S:share!"). Each line in
   /etc/exports specifies a file system to be exported and which
   machines have access to that file system. Along with what machines
   have access to that file system, access options may also be
   specified. There are many such options that can be used in this
   file but only a few will be mentioned here. You can easily
   discover other options by reading over the exports(5) manual page.

   Here are a few example /etc/exports entries:

   The following examples give an idea of how to export file systems,
   although the settings may be different depending on your
   environment and network configuration. For instance, to export the
   /cdrom directory to three example machines that have the same
   domain name as the server (hence the lack of a domain name for
   each) or have entries in your /etc/hosts file. The -ro flag makes
   the exported file system read-only. With this flag, the remote
   system will not be able to write any changes to the exported file
   system.

 /cdrom -ro host1 host2 host3

   The following line exports /home to three hosts by IP address.
   This is a useful setup if you have a private network without a DNS
   server configured. Optionally the /etc/hosts file could be
   configured for internal hostnames; please review hosts(5) for more
   information. The -alldirs flag allows the subdirectories to be
   mount points. In other words, it will not mount the subdirectories
   but permit the client to mount only the directories that are
   required or needed.

 /home  -alldirs  10.0.0.2 10.0.0.3 10.0.0.4

   The following line exports /a so that two clients from different
   domains may access the file system. The -maproot=root flag allows
   the root user on the remote system to write data on the exported
   file system as root. If the -maproot=root flag is not specified,
   then even if a user has root access on the remote system, he will
   not be able to modify files on the exported file system.

 /a  -maproot=root  host.example.com box.example.org

   In order for a client to access an exported file system, the
   client must have permission to do so. Make sure the client is
   listed in your /etc/exports file.

   In /etc/exports, each line represents the export information for
   one file system to one host. A remote host can only be specified
   once per file system, and may only have one default entry. For
   example, assume that /usr is a single file system. The following
   /etc/exports would be invalid:

 # Invalid when /usr is one file system
 /usr/src   client
 /usr/ports client

   One file system, /usr, has two lines specifying exports to the
   same host, client. The correct format for this situation is:

 /usr/src /usr/ports  client

   The properties of one file system exported to a given host must
   all occur on one line. Lines without a client specified are
   treated as a single host. This limits how you can export file
   systems, but for most people this is not an issue.

   The following is an example of a valid export list, where /usr and
   /exports are local file systems:

 # Export src and ports to client01 and client02, but only
 # client01 has root privileges on it
 /usr/src /usr/ports -maproot=root    client01
 /usr/src /usr/ports               client02
 # The client machines have root and can mount anywhere
 # on /exports. Anyone in the world can mount /exports/obj read-only
 /exports -alldirs -maproot=root      client01 client02
 /exports/obj -ro

   You must restart mountd whenever you modify /etc/exports so the
   changes can take effect. This can be accomplished by sending the
   HUP signal to the mountd process:

 # kill -HUP `cat /var/run/mountd.pid`

   Alternatively, a reboot will make FreeBSD set everything up
   properly. A reboot is not necessary though. Executing the
   following commands as root should start everything up.

   On the NFS server:

 # rpcbind
 # nfsd -u -t -n 4
 # mountd -r

   On the NFS client:

 # nfsiod -n 4

   Now everything should be ready to actually mount a remote file
   system. In these examples the server's name will be server and the
   client's name will be client. If you only want to temporarily
   mount a remote file system or would rather test the configuration,
   just execute a command like this as root on the client:

 # mount server:/home /mnt

   This will mount the /home directory on the server at /mnt on the
   client. If everything is set up correctly you should be able to
   enter /mnt on the client and see all the files that are on the
   server.

   If you want to automatically mount a remote file system each time
   the computer boots, add the file system to the /etc/fstab file.
   Here is an example:

 server:/home    /mnt    nfs     rw      0       0

   The fstab(5) manual page lists all the available options.

     --------------------------------------------------------------

  27.3.3. Practical Uses

   NFS has many practical uses. Some of the more common ones are
   listed below:

     * Set several machines to share a CDROM or other media among
       them. This is cheaper and often a more convenient method to
       install software on multiple machines.

     * On large networks, it might be more convenient to configure a
       central NFS server in which to store all the user home
       directories. These home directories can then be exported to
       the network so that users would always have the same home
       directory, regardless of which workstation they log in to.

     * Several machines could have a common /usr/ports/distfiles
       directory. That way, when you need to install a port on
       several machines, you can quickly access the source without
       downloading it on each machine.

     --------------------------------------------------------------

  27.3.4. Automatic Mounts with amd

   Contributed by Wylie Stilwell. Rewritten by Chern Lee.

   amd(8) (the automatic mounter daemon) automatically mounts a
   remote file system whenever a file or directory within that file
   system is accessed. Filesystems that are inactive for a period of
   time will also be automatically unmounted by amd. Using amd
   provides a simple alternative to permanent mounts, as permanent
   mounts are usually listed in /etc/fstab.

   amd operates by attaching itself as an NFS server to the /host and
   /net directories. When a file is accessed within one of these
   directories, amd looks up the corresponding remote mount and
   automatically mounts it. /net is used to mount an exported file
   system from an IP address, while /host is used to mount an export
   from a remote hostname.

   An access to a file within /host/foobar/usr would tell amd to
   attempt to mount the /usr export on the host foobar.

   1/2d"O 27-2. Mounting an Export with amd

   You can view the available mounts of a remote host with the
   showmount command. For example, to view the mounts of a host named
   foobar, you can use:

 % showmount -e foobar
 Exports list on foobar:
 /usr                               10.10.10.0
 /a                                 10.10.10.0
 % cd /host/foobar/usr

   As seen in the example, the showmount shows /usr as an export.
   When changing directories to /host/foobar/usr, amd attempts to
   resolve the hostname foobar and automatically mount the desired
   export.

   amd can be started by the startup scripts by placing the following
   lines in /etc/rc.conf:

 amd_enable="YES"

   Additionally, custom flags can be passed to amd from the amd_flags
   option. By default, amd_flags is set to:

 amd_flags="-a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map"

   The /etc/amd.map file defines the default options that exports are
   mounted with. The /etc/amd.conf file defines some of the more
   advanced features of amd.

   Consult the amd(8) and amd.conf(5) manual pages for more
   information.

     --------------------------------------------------------------

  27.3.5. Problems Integrating with Other Systems

   Contributed by John Lind.

   Certain Ethernet adapters for ISA PC systems have limitations
   which can lead to serious network problems, particularly with NFS.
   This difficulty is not specific to FreeBSD, but FreeBSD systems
   are affected by it.

   The problem nearly always occurs when (FreeBSD) PC systems are
   networked with high-performance workstations, such as those made
   by Silicon Graphics, Inc., and Sun Microsystems, Inc. The NFS
   mount will work fine, and some operations may succeed, but
   suddenly the server will seem to become unresponsive to the
   client, even though requests to and from other systems continue to
   be processed. This happens to the client system, whether the
   client is the FreeBSD system or the workstation. On many systems,
   there is no way to shut down the client gracefully once this
   problem has manifested itself. The only solution is often to reset
   the client, because the NFS situation cannot be resolved.

   Though the !S:correct!" solution is to get a higher performance
   and capacity Ethernet adapter for the FreeBSD system, there is a
   simple workaround that will allow satisfactory operation. If the
   FreeBSD system is the server, include the option -w=1024 on the
   mount from the client. If the FreeBSD system is the client, then
   mount the NFS file system with the option -r=1024. These options
   may be specified using the fourth field of the fstab entry on the
   client for automatic mounts, or by using the -o parameter of the
   mount(8) command for manual mounts.

   It should be noted that there is a different problem, sometimes
   mistaken for this one, when the NFS servers and clients are on
   different networks. If that is the case, make certain that your
   routers are routing the necessary UDP information, or you will not
   get anywhere, no matter what else you are doing.

   In the following examples, fastws is the host (interface) name of
   a high-performance workstation, and freebox is the host
   (interface) name of a FreeBSD system with a lower-performance
   Ethernet adapter. Also, /sharedfs will be the exported NFS file
   system (see exports(5)), and /project will be the mount point on
   the client for the exported file system. In all cases, note that
   additional options, such as hard or soft and bg may be desirable
   in your application.

   Examples for the FreeBSD system (freebox) as the client in
   /etc/fstab on freebox:

 fastws:/sharedfs /project nfs rw,-r=1024 0 0

   As a manual mount command on freebox:

 # mount -t nfs -o -r=1024 fastws:/sharedfs /project

   Examples for the FreeBSD system as the server in /etc/fstab on
   fastws:

 freebox:/sharedfs /project nfs rw,-w=1024 0 0

   As a manual mount command on fastws:

 # mount -t nfs -o -w=1024 freebox:/sharedfs /project

   Nearly any 16-bit Ethernet adapter will allow operation without
   the above restrictions on the read or write size.

   For anyone who cares, here is what happens when the failure
   occurs, which also explains why it is unrecoverable. NFS typically
   works with a !S:block!" size of 8 K (though it may do fragments of
   smaller sizes). Since the maximum Ethernet packet is around
   1500 bytes, the NFS !S:block!" gets split into multiple Ethernet
   packets, even though it is still a single unit to the upper-level
   code, and must be received, assembled, and acknowledged as a unit.
   The high-performance workstations can pump out the packets which
   comprise the NFS unit one right after the other, just as close
   together as the standard allows. On the smaller, lower capacity
   cards, the later packets overrun the earlier packets of the same
   unit before they can be transferred to the host and the unit as a
   whole cannot be reconstructed or acknowledged. As a result, the
   workstation will time out and try again, but it will try again
   with the entire 8 K unit, and the process will be repeated, ad
   infinitum.

   By keeping the unit size below the Ethernet packet size
   limitation, we ensure that any complete Ethernet packet received
   can be acknowledged individually, avoiding the deadlock situation.

   Overruns may still occur when a high-performance workstations is
   slamming data out to a PC system, but with the better cards, such
   overruns are not guaranteed on NFS !S:units!". When an overrun
   occurs, the units affected will be retransmitted, and there will
   be a fair chance that they will be received, assembled, and
   acknowledged.

     --------------------------------------------------------------

27.4. Network Information System (NIS/YP)

   Written by Bill Swingle. Enhanced by Eric Ogren YENB Udo
   Erdelhoff.

  27.4.1. What Is It?

   NIS, which stands for Network Information Services, was developed
   by Sun Microsystems to centralize administration of UNIX
   (originally SunOS) systems. It has now essentially become an
   industry standard; all major UNIX like systems (Solaris, HP-UX,
   AIX(R), Linux, NetBSD, OpenBSD, FreeBSD, etc) support NIS.

   NIS was formerly known as Yellow Pages, but because of trademark
   issues, Sun changed the name. The old term (and yp) is still often
   seen and used.

   It is a RPC-based client/server system that allows a group of
   machines within an NIS domain to share a common set of
   configuration files. This permits a system administrator to set up
   NIS client systems with only minimal configuration data and add,
   remove or modify configuration data from a single location.

   It is similar to the Windows NT(R) domain system; although the
   internal implementation of the two are not at all similar, the
   basic functionality can be compared.

     --------------------------------------------------------------

  27.4.2. Terms/Processes You Should Know

   There are several terms and several important user processes that
   you will come across when attempting to implement NIS on FreeBSD,
   whether you are trying to create an NIS server or act as an NIS
   client:

        Term                          Description                     
                  An NIS master server and all of its clients         
                  (including its slave servers) have a NIS            
   NIS domainname domainname. Similar to an Windows NT domain name,   
                  the NIS domainname does not have anything to do     
                  with DNS.                                           
                  Must be running in order to enable RPC (Remote      
                  Procedure Call, a network protocol used by NIS). If 
   rpcbind        rpcbind is not running, it will be impossible to    
                  run an NIS server, or to act as an NIS client       
                  (Under FreeBSD 4.X portmap is used in place of      
                  rpcbind).                                           
                  !S:Binds!" an NIS client to its NIS server. It will 
                  take the NIS domainname from the system, and using  
   ypbind         RPC, connect to the server. ypbind is the core of   
                  client-server communication in an NIS environment;  
                  if ypbind dies on a client machine, it will not be  
                  able to access the NIS server.                      
                  Should only be running on NIS servers; this is the  
                  NIS server process itself. If ypserv(8) dies, then  
                  the server will no longer be able to respond to NIS 
                  requests (hopefully, there is a slave server to     
                  take over for it). There are some implementations   
   ypserv         of NIS (but not the FreeBSD one), that do not try   
                  to reconnect to another server if the server it     
                  used before dies. Often, the only thing that helps  
                  in this case is to restart the server process (or   
                  even the whole server) or the ypbind process on the 
                  client.                                             
                  Another process that should only be running on NIS  
                  master servers; this is a daemon that will allow    
   rpc.yppasswdd  NIS clients to change their NIS passwords. If this  
                  daemon is not running, users will have to login to  
                  the NIS master server and change their passwords    
                  there.                                              

     --------------------------------------------------------------

  27.4.3. How Does It Work?

   There are three types of hosts in an NIS environment: master
   servers, slave servers, and clients. Servers act as a central
   repository for host configuration information. Master servers hold
   the authoritative copy of this information, while slave servers
   mirror this information for redundancy. Clients rely on the
   servers to provide this information to them.

   Information in many files can be shared in this manner. The
   master.passwd, group, and hosts files are commonly shared via NIS.
   Whenever a process on a client needs information that would
   normally be found in these files locally, it makes a query to the
   NIS server that it is bound to instead.

     --------------------------------------------------------------

    27.4.3.1. Machine Types

     * A NIS master server. This server, analogous to a Windows NT
       primary domain controller, maintains the files used by all of
       the NIS clients. The passwd, group, and other various files
       used by the NIS clients live on the master server.

         -a`: It is possible for one machine to be an NIS master
         server for more than one NIS domain. However, this will not
         be covered in this introduction, which assumes a relatively
         small-scale NIS environment.

     * NIS slave servers. Similar to the Windows NT backup domain
       controllers, NIS slave servers maintain copies of the NIS
       master's data files. NIS slave servers provide the redundancy,
       which is needed in important environments. They also help to
       balance the load of the master server: NIS Clients always
       attach to the NIS server whose response they get first, and
       this includes slave-server-replies.

     * NIS clients. NIS clients, like most Windows NT workstations,
       authenticate against the NIS server (or the Windows NT domain
       controller in the Windows NT workstations case) to log on.

     --------------------------------------------------------------

  27.4.4. Using NIS/YP

   This section will deal with setting up a sample NIS environment.

     -a`: This section assumes that you are running FreeBSD 3.3 or
     later. The instructions given here will probably work for any
     version of FreeBSD greater than 3.0, but there are no guarantees
     that this is true.

     --------------------------------------------------------------

    27.4.4.1. Planning

   Let us assume that you are the administrator of a small university
   lab. This lab, which consists of 15 FreeBSD machines, currently
   has no centralized point of administration; each machine has its
   own /etc/passwd and /etc/master.passwd. These files are kept in
   sync with each other only through manual intervention; currently,
   when you add a user to the lab, you must run adduser on all 15
   machines. Clearly, this has to change, so you have decided to
   convert the lab to use NIS, using two of the machines as servers.

   Therefore, the configuration of the lab now looks something like:

      Machine name        IP address             Machine role         
   ellington          10.0.0.2            NIS master                  
   coltrane           10.0.0.3            NIS slave                   
   basie              10.0.0.4            Faculty workstation         
   bird               10.0.0.5            Client machine              
   cli[1-11]          10.0.0.[6-17]       Other client machines       

   If you are setting up a NIS scheme for the first time, it is a
   good idea to think through how you want to go about it. No matter
   what the size of your network, there are a few decisions that need
   to be made.

     --------------------------------------------------------------

      27.4.4.1.1. Choosing a NIS Domain Name

   This might not be the !S:domainname!" that you are used to. It is
   more accurately called the !S:NIS domainname!". When a client
   broadcasts its requests for info, it includes the name of the NIS
   domain that it is part of. This is how multiple servers on one
   network can tell which server should answer which request. Think
   of the NIS domainname as the name for a group of hosts that are
   related in some way.

   Some organizations choose to use their Internet domainname for
   their NIS domainname. This is not recommended as it can cause
   confusion when trying to debug network problems. The NIS
   domainname should be unique within your network and it is helpful
   if it describes the group of machines it represents. For example,
   the Art department at Acme Inc. might be in the !S:acme-art!" NIS
   domain. For this example, assume you have chosen the name
   test-domain.

   However, some operating systems (notably SunOS) use their NIS
   domain name as their Internet domain name. If one or more machines
   on your network have this restriction, you must use the Internet
   domain name as your NIS domain name.

     --------------------------------------------------------------

      27.4.4.1.2. Physical Server Requirements

   There are several things to keep in mind when choosing a machine
   to use as a NIS server. One of the unfortunate things about NIS is
   the level of dependency the clients have on the server. If a
   client cannot contact the server for its NIS domain, very often
   the machine becomes unusable. The lack of user and group
   information causes most systems to temporarily freeze up. With
   this in mind you should make sure to choose a machine that will
   not be prone to being rebooted regularly, or one that might be
   used for development. The NIS server should ideally be a stand
   alone machine whose sole purpose in life is to be an NIS server.
   If you have a network that is not very heavily used, it is
   acceptable to put the NIS server on a machine running other
   services, just keep in mind that if the NIS server becomes
   unavailable, it will affect all of your NIS clients adversely.

     --------------------------------------------------------------

    27.4.4.2. NIS Servers

   The canonical copies of all NIS information are stored on a single
   machine called the NIS master server. The databases used to store
   the information are called NIS maps. In FreeBSD, these maps are
   stored in /var/yp/[domainname] where [domainname] is the name of
   the NIS domain being served. A single NIS server can support
   several domains at once, therefore it is possible to have several
   such directories, one for each supported domain. Each domain will
   have its own independent set of maps.

   NIS master and slave servers handle all NIS requests with the
   ypserv daemon. ypserv is responsible for receiving incoming
   requests from NIS clients, translating the requested domain and
   map name to a path to the corresponding database file and
   transmitting data from the database back to the client.

     --------------------------------------------------------------

      27.4.4.2.1. Setting Up a NIS Master Server

   Setting up a master NIS server can be relatively straight forward,
   depending on your needs. FreeBSD comes with support for NIS
   out-of-the-box. All you need is to add the following lines to
   /etc/rc.conf, and FreeBSD will do the rest for you.

    1. nisdomainname="test-domain"

       This line will set the NIS domainname to test-domain upon
       network setup (e.g. after reboot).

    2. nis_server_enable="YES"

       This will tell FreeBSD to start up the NIS server processes
       when the networking is next brought up.

    3. nis_yppasswdd_enable="YES"

       This will enable the rpc.yppasswdd daemon which, as mentioned
       above, will allow users to change their NIS password from a
       client machine.

     -a`: Depending on your NIS setup, you may need to add further
     entries. See the section about NIS servers that are also NIS
     clients, below, for details.

   Now, all you have to do is to run the command /etc/netstart as
   superuser. It will set up everything for you, using the values you
   defined in /etc/rc.conf.

     --------------------------------------------------------------

      27.4.4.2.2. Initializing the NIS Maps

   The NIS maps are database files, that are kept in the /var/yp
   directory. They are generated from configuration files in the /etc
   directory of the NIS master, with one exception: the
   /etc/master.passwd file. This is for a good reason, you do not
   want to propagate passwords to your root and other administrative
   accounts to all the servers in the NIS domain. Therefore, before
   we initialize the NIS maps, you should:

 # cp /etc/master.passwd /var/yp/master.passwd
 # cd /var/yp
 # vi master.passwd

   You should remove all entries regarding system accounts (bin, tty,
   kmem, games, etc), as well as any accounts that you do not want to
   be propagated to the NIS clients (for example root and any other
   UID 0 (superuser) accounts).

     -a`: Make sure the /var/yp/master.passwd is neither group nor
     world readable (mode 600)! Use the chmod command, if
     appropriate.

   When you have finished, it is time to initialize the NIS maps!
   FreeBSD includes a script named ypinit to do this for you (see its
   manual page for more information). Note that this script is
   available on most UNIX Operating Systems, but not on all. On
   Digital UNIX/Compaq Tru64 UNIX it is called ypsetup. Because we
   are generating maps for an NIS master, we are going to pass the -m
   option to ypinit. To generate the NIS maps, assuming you already
   performed the steps above, run:

 ellington# ypinit -m test-domain
 Server Type: MASTER Domain: test-domain
 Creating an YP server will require that you answer a few questions.
 Questions will all be asked at the beginning of the procedure.
 Do you want this procedure to quit on non-fatal errors? [y/n: n] n
 Ok, please remember to go back and redo manually whatever fails.
 If you don't, something might not work.
 At this point, we have to construct a list of this domains YP servers.
 rod.darktech.org is already known as master server.
 Please continue to add any slave servers, one per line. When you are
 done with the list, type a <control D>.
 master server   :  ellington
 next host to add:  coltrane
 next host to add:  ^D
 The current list of NIS servers looks like this:
 ellington
 coltrane
 Is this correct?  [y/n: y] y

 [..output from map generation..]

 NIS Map update completed.
 ellington has been setup as an YP master server without any errors.

   ypinit should have created /var/yp/Makefile from
   /var/yp/Makefile.dist. When created, this file assumes that you
   are operating in a single server NIS environment with only FreeBSD
   machines. Since test-domain has a slave server as well, you must
   edit /var/yp/Makefile:

 ellington# vi /var/yp/Makefile

   You should comment out the line that says

 NOPUSH = "True"

   (if it is not commented out already).

     --------------------------------------------------------------

      27.4.4.2.3. Setting up a NIS Slave Server

   Setting up an NIS slave server is even more simple than setting up
   the master. Log on to the slave server and edit the file
   /etc/rc.conf as you did before. The only difference is that we now
   must use the -s option when running ypinit. The -s option requires
   the name of the NIS master be passed to it as well, so our command
   line looks like:

 coltrane# ypinit -s ellington test-domain

 Server Type: SLAVE Domain: test-domain Master: ellington

 Creating an YP server will require that you answer a few questions.
 Questions will all be asked at the beginning of the procedure.

 Do you want this procedure to quit on non-fatal errors? [y/n: n]  n

 Ok, please remember to go back and redo manually whatever fails.
 If you don't, something might not work.
 There will be no further questions. The remainder of the procedure
 should take a few minutes, to copy the databases from ellington.
 Transferring netgroup...
 ypxfr: Exiting: Map successfully transferred
 Transferring netgroup.byuser...
 ypxfr: Exiting: Map successfully transferred
 Transferring netgroup.byhost...
 ypxfr: Exiting: Map successfully transferred
 Transferring master.passwd.byuid...
 ypxfr: Exiting: Map successfully transferred
 Transferring passwd.byuid...
 ypxfr: Exiting: Map successfully transferred
 Transferring passwd.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring group.bygid...
 ypxfr: Exiting: Map successfully transferred
 Transferring group.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring services.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring rpc.bynumber...
 ypxfr: Exiting: Map successfully transferred
 Transferring rpc.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring protocols.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring master.passwd.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring networks.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring networks.byaddr...
 ypxfr: Exiting: Map successfully transferred
 Transferring netid.byname...
 ypxfr: Exiting: Map successfully transferred
 Transferring hosts.byaddr...
 ypxfr: Exiting: Map successfully transferred
 Transferring protocols.bynumber...
 ypxfr: Exiting: Map successfully transferred
 Transferring ypservers...
 ypxfr: Exiting: Map successfully transferred
 Transferring hosts.byname...
 ypxfr: Exiting: Map successfully transferred

 coltrane has been setup as an YP slave server without any errors.
 Don't forget to update map ypservers on ellington.

   You should now have a directory called /var/yp/test-domain. Copies
   of the NIS master server's maps should be in this directory. You
   will need to make sure that these stay updated. The following
   /etc/crontab entries on your slave servers should do the job:

 20      *       *       *       *       root   /usr/libexec/ypxfr passwd.byname
 21      *       *       *       *       root   /usr/libexec/ypxfr passwd.byuid

   These two lines force the slave to sync its maps with the maps on
   the master server. Although these entries are not mandatory, since
   the master server attempts to ensure any changes to its NIS maps
   are communicated to its slaves and because password information is
   vital to systems depending on the server, it is a good idea to
   force the updates. This is more important on busy networks where
   map updates might not always complete.

   Now, run the command /etc/netstart on the slave server as well,
   which again starts the NIS server.

     --------------------------------------------------------------

    27.4.4.3. NIS Clients

   An NIS client establishes what is called a binding to a particular
   NIS server using the ypbind daemon. ypbind checks the system's
   default domain (as set by the domainname command), and begins
   broadcasting RPC requests on the local network. These requests
   specify the name of the domain for which ypbind is attempting to
   establish a binding. If a server that has been configured to serve
   the requested domain receives one of the broadcasts, it will
   respond to ypbind, which will record the server's address. If
   there are several servers available (a master and several slaves,
   for example), ypbind will use the address of the first one to
   respond. From that point on, the client system will direct all of
   its NIS requests to that server. ypbind will occasionally
   !S:ping!" the server to make sure it is still up and running. If
   it fails to receive a reply to one of its pings within a
   reasonable amount of time, ypbind will mark the domain as unbound
   and begin broadcasting again in the hopes of locating another
   server.

     --------------------------------------------------------------

      27.4.4.3.1. Setting Up a NIS Client

   Setting up a FreeBSD machine to be a NIS client is fairly
   straightforward.

    1. Edit the file /etc/rc.conf and add the following lines in
       order to set the NIS domainname and start ypbind upon network
       startup:

 nisdomainname="test-domain"
 nis_client_enable="YES"

    2. To import all possible password entries from the NIS server,
       remove all user accounts from your /etc/master.passwd file and
       use vipw to add the following line to the end of the file:

 +:::::::::

         -a`: This line will afford anyone with a valid account in
         the NIS server's password maps an account. There are many
         ways to configure your NIS client by changing this line. See
         the netgroups section below for more information. For more
         detailed reading see O'Reilly's book on Managing NFS and
         NIS.

         -a`: You should keep at least one local account (i.e. not
         imported via NIS) in your /etc/master.passwd and this
         account should also be a member of the group wheel. If there
         is something wrong with NIS, this account can be used to log
         in remotely, become root, and fix things.

    3. To import all possible group entries from the NIS server, add
       this line to your /etc/group file:

 +:*::

   After completing these steps, you should be able to run ypcat
   passwd and see the NIS server's passwd map.

     --------------------------------------------------------------

  27.4.5. NIS Security

   In general, any remote user can issue an RPC to ypserv(8) and
   retrieve the contents of your NIS maps, provided the remote user
   knows your domainname. To prevent such unauthorized transactions,
   ypserv(8) supports a feature called !S:securenets!" which can be
   used to restrict access to a given set of hosts. At startup,
   ypserv(8) will attempt to load the securenets information from a
   file called /var/yp/securenets.

     -a`: This path varies depending on the path specified with the
     -p option. This file contains entries that consist of a network
     specification and a network mask separated by white space. Lines
     starting with !S:#!" are considered to be comments. A sample
     securenets file might look like this:

 # allow connections from local host -- mandatory
 127.0.0.1     255.255.255.255
 # allow connections from any host
 # on the 192.168.128.0 network
 192.168.128.0 255.255.255.0
 # allow connections from any host
 # between 10.0.0.0 to 10.0.15.255
 # this includes the machines in the testlab
 10.0.0.0      255.255.240.0

   If ypserv(8) receives a request from an address that matches one
   of these rules, it will process the request normally. If the
   address fails to match a rule, the request will be ignored and a
   warning message will be logged. If the /var/yp/securenets file
   does not exist, ypserv will allow connections from any host.

   The ypserv program also has support for Wietse Venema's TCP
   Wrapper package. This allows the administrator to use the TCP
   Wrapper configuration files for access control instead of
   /var/yp/securenets.

     -a`: While both of these access control mechanisms provide some
     security, they, like the privileged port test, are vulnerable to
     !S:IP spoofing!" attacks. All NIS-related traffic should be
     blocked at your firewall.

     Servers using /var/yp/securenets may fail to serve legitimate
     NIS clients with archaic TCP/IP implementations. Some of these
     implementations set all host bits to zero when doing broadcasts
     and/or fail to observe the subnet mask when calculating the
     broadcast address. While some of these problems can be fixed by
     changing the client configuration, other problems may force the
     retirement of the client systems in question or the abandonment
     of /var/yp/securenets.

     Using /var/yp/securenets on a server with such an archaic
     implementation of TCP/IP is a really bad idea and will lead to
     loss of NIS functionality for large parts of your network.

     The use of the TCP Wrapper package increases the latency of your
     NIS server. The additional delay may be long enough to cause
     timeouts in client programs, especially in busy networks or with
     slow NIS servers. If one or more of your client systems suffers
     from these symptoms, you should convert the client systems in
     question into NIS slave servers and force them to bind to
     themselves.

     --------------------------------------------------------------

  27.4.6. Barring Some Users from Logging On

   In our lab, there is a machine basie that is supposed to be a
   faculty only workstation. We do not want to take this machine out
   of the NIS domain, yet the passwd file on the master NIS server
   contains accounts for both faculty and students. What can we do?

   There is a way to bar specific users from logging on to a machine,
   even if they are present in the NIS database. To do this, all you
   must do is add -username to the end of the /etc/master.passwd file
   on the client machine, where username is the username of the user
   you wish to bar from logging in. This should preferably be done
   using vipw, since vipw will sanity check your changes to
   /etc/master.passwd, as well as automatically rebuild the password
   database when you finish editing. For example, if we wanted to bar
   user bill from logging on to basie we would:

 basie# vipw
 [add -bill to the end, exit]
 vipw: rebuilding the database...
 vipw: done

 basie# cat /etc/master.passwd

 root:[password]:0:0::0:0:The super-user:/root:/bin/csh
 toor:[password]:0:0::0:0:The other super-user:/root:/bin/sh
 daemon:*:1:1::0:0:Owner of many system processes:/root:/sbin/nologin
 operator:*:2:5::0:0:System &:/:/sbin/nologin
 bin:*:3:7::0:0:Binaries Commands and Source,,,:/:/sbin/nologin
 tty:*:4:65533::0:0:Tty Sandbox:/:/sbin/nologin
 kmem:*:5:65533::0:0:KMem Sandbox:/:/sbin/nologin
 games:*:7:13::0:0:Games pseudo-user:/usr/games:/sbin/nologin
 news:*:8:8::0:0:News Subsystem:/:/sbin/nologin
 man:*:9:9::0:0:Mister Man Pages:/usr/share/man:/sbin/nologin
 bind:*:53:53::0:0:Bind Sandbox:/:/sbin/nologin
 uucp:*:66:66::0:0:UUCP pseudo-user:/var/spool/uucppublic:/usr/libexec/uucp/uucico
 xten:*:67:67::0:0:X-10 daemon:/usr/local/xten:/sbin/nologin
 pop:*:68:6::0:0:Post Office Owner:/nonexistent:/sbin/nologin
 nobody:*:65534:65534::0:0:Unprivileged user:/nonexistent:/sbin/nologin
 +:::::::::
 -bill

 basie#

     --------------------------------------------------------------

  27.4.7. Using Netgroups

   Contributed by Udo Erdelhoff.

   The method shown in the previous section works reasonably well if
   you need special rules for a very small number of users and/or
   machines. On larger networks, you will forget to bar some users
   from logging onto sensitive machines, or you may even have to
   modify each machine separately, thus losing the main benefit of
   NIS: centralized administration.

   The NIS developers' solution for this problem is called netgroups.
   Their purpose and semantics can be compared to the normal groups
   used by UNIX file systems. The main differences are the lack of a
   numeric ID and the ability to define a netgroup by including both
   user accounts and other netgroups.

   Netgroups were developed to handle large, complex networks with
   hundreds of users and machines. On one hand, this is a Good Thing
   if you are forced to deal with such a situation. On the other
   hand, this complexity makes it almost impossible to explain
   netgroups with really simple examples. The example used in the
   remainder of this section demonstrates this problem.

   Let us assume that your successful introduction of NIS in your
   laboratory caught your superiors' interest. Your next job is to
   extend your NIS domain to cover some of the other machines on
   campus. The two tables contain the names of the new users and new
   machines as well as brief descriptions of them.

         User Name(s)                      Description                
   alpha, beta               Normal employees of the IT department    
   charlie, delta            The new apprentices of the IT department 
   echo, foxtrott, golf, ... Ordinary employees                       
   able, baker, ...          The current interns                      

      Machine Name(s)                     Description                 
   war, death, famine,    Your most important servers. Only the IT    
   pollution              employees are allowed to log onto these     
                          machines.                                   
   pride, greed, envy,    Less important servers. All members of the  
   wrath, lust, sloth     IT department are allowed to login onto     
                          these machines.                             
   one, two, three, four, Ordinary workstations. Only the real        
   ...                    employees are allowed to use these          
                          machines.                                   
                          A very old machine without any critical     
   trashcan               data. Even the intern is allowed to use     
                          this box.                                   

   If you tried to implement these restrictions by separately
   blocking each user, you would have to add one -user line to each
   system's passwd for each user who is not allowed to login onto
   that system. If you forget just one entry, you could be in
   trouble. It may be feasible to do this correctly during the
   initial setup, however you will eventually forget to add the lines
   for new users during day-to-day operations. After all, Murphy was
   an optimist.

   Handling this situation with netgroups offers several advantages.
   Each user need not be handled separately; you assign a user to one
   or more netgroups and allow or forbid logins for all members of
   the netgroup. If you add a new machine, you will only have to
   define login restrictions for netgroups. If a new user is added,
   you will only have to add the user to one or more netgroups. Those
   changes are independent of each other: no more !S:for each
   combination of user and machine do...!" If your NIS setup is
   planned carefully, you will only have to modify exactly one
   central configuration file to grant or deny access to machines.

   The first step is the initialization of the NIS map netgroup.
   FreeBSD's ypinit(8) does not create this map by default, but its
   NIS implementation will support it once it has been created. To
   create an empty map, simply type

 ellington# vi /var/yp/netgroup

   and start adding content. For our example, we need at least four
   netgroups: IT employees, IT apprentices, normal employees and
   interns.

 IT_EMP  (,alpha,test-domain)    (,beta,test-domain)
 IT_APP  (,charlie,test-domain)  (,delta,test-domain)
 USERS   (,echo,test-domain)     (,foxtrott,test-domain) \
         (,golf,test-domain)
 INTERNS (,able,test-domain)     (,baker,test-domain)

   IT_EMP, IT_APP etc. are the names of the netgroups. Each bracketed
   group adds one or more user accounts to it. The three fields
   inside a group are:

    1. The name of the host(s) where the following items are valid.
       If you do not specify a hostname, the entry is valid on all
       hosts. If you do specify a hostname, you will enter a realm of
       darkness, horror and utter confusion.

    2. The name of the account that belongs to this netgroup.

    3. The NIS domain for the account. You can import accounts from
       other NIS domains into your netgroup if you are one of the
       unlucky fellows with more than one NIS domain.

   Each of these fields can contain wildcards. See netgroup(5) for
   details.

     -a`: Netgroup names longer than 8 characters should not be used,
     especially if you have machines running other operating systems
     within your NIS domain. The names are case sensitive; using
     capital letters for your netgroup names is an easy way to
     distinguish between user, machine and netgroup names.

     Some NIS clients (other than FreeBSD) cannot handle netgroups
     with a large number of entries. For example, some older versions
     of SunOS start to cause trouble if a netgroup contains more than
     15 entries. You can circumvent this limit by creating several
     sub-netgroups with 15 users or less and a real netgroup that
     consists of the sub-netgroups:

 BIGGRP1  (,joe1,domain)  (,joe2,domain)  (,joe3,domain) [...]
 BIGGRP2  (,joe16,domain)  (,joe17,domain) [...]
 BIGGRP3  (,joe31,domain)  (,joe32,domain)
 BIGGROUP  BIGGRP1 BIGGRP2 BIGGRP3

     You can repeat this process if you need more than 225 users
     within a single netgroup.

   Activating and distributing your new NIS map is easy:

 ellington# cd /var/yp
 ellington# make

   This will generate the three NIS maps netgroup, netgroup.byhost
   and netgroup.byuser. Use ypcat(1) to check if your new NIS maps
   are available:

 ellington% ypcat -k netgroup
 ellington% ypcat -k netgroup.byhost
 ellington% ypcat -k netgroup.byuser

   The output of the first command should resemble the contents of
   /var/yp/netgroup. The second command will not produce output if
   you have not specified host-specific netgroups. The third command
   can be used to get the list of netgroups for a user.

   The client setup is quite simple. To configure the server war, you
   only have to start vipw(8) and replace the line

 +:::::::::

   with

 +@IT_EMP:::::::::

   Now, only the data for the users defined in the netgroup IT_EMP is
   imported into war's password database and only these users are
   allowed to login.

   Unfortunately, this limitation also applies to the ~ function of
   the shell and all routines converting between user names and
   numerical user IDs. In other words, cd ~user will not work, ls -l
   will show the numerical ID instead of the username and find .
   -user joe -print will fail with !S:No such user!". To fix this,
   you will have to import all user entries without allowing them to
   login onto your servers.

   This can be achieved by adding another line to /etc/master.passwd.
   This line should contain:

   +:::::::::/sbin/nologin, meaning !S:Import all entries but replace
   the shell with /sbin/nologin in the imported entries!". You can
   replace any field in the passwd entry by placing a default value
   in your /etc/master.passwd.

     A:uS:iMake sure that the line +:::::::::/sbin/nologin is placed
     after +@IT_EMP:::::::::. Otherwise, all user accounts imported
     from NIS will have /sbin/nologin as their login shell.

   After this change, you will only have to change one NIS map if a
   new employee joins the IT department. You could use a similar
   approach for the less important servers by replacing the old
   +::::::::: in their local version of /etc/master.passwd with
   something like this:

 +@IT_EMP:::::::::
 +@IT_APP:::::::::
 +:::::::::/sbin/nologin

   The corresponding lines for the normal workstations could be:

 +@IT_EMP:::::::::
 +@USERS:::::::::
 +:::::::::/sbin/nologin

   And everything would be fine until there is a policy change a few
   weeks later: The IT department starts hiring interns. The IT
   interns are allowed to use the normal workstations and the less
   important servers; and the IT apprentices are allowed to login
   onto the main servers. You add a new netgroup IT_INTERN, add the
   new IT interns to this netgroup and start to change the
   configuration on each and every machine... As the old saying goes:
   !S:Errors in centralized planning lead to global mess!".

   NIS' ability to create netgroups from other netgroups can be used
   to prevent situations like these. One possibility is the creation
   of role-based netgroups. For example, you could create a netgroup
   called BIGSRV to define the login restrictions for the important
   servers, another netgroup called SMALLSRV for the less important
   servers and a third netgroup called USERBOX for the normal
   workstations. Each of these netgroups contains the netgroups that
   are allowed to login onto these machines. The new entries for your
   NIS map netgroup should look like this:

 BIGSRV    IT_EMP  IT_APP
 SMALLSRV  IT_EMP  IT_APP  ITINTERN
 USERBOX   IT_EMP  ITINTERN USERS

   This method of defining login restrictions works reasonably well
   if you can define groups of machines with identical restrictions.
   Unfortunately, this is the exception and not the rule. Most of the
   time, you will need the ability to define login restrictions on a
   per-machine basis.

   Machine-specific netgroup definitions are the other possibility to
   deal with the policy change outlined above. In this scenario, the
   /etc/master.passwd of each box contains two lines starting with
   !S:+!". The first of them adds a netgroup with the accounts
   allowed to login onto this machine, the second one adds all other
   accounts with /sbin/nologin as shell. It is a good idea to use the
   !S:ALL-CAPS!" version of the machine name as the name of the
   netgroup. In other words, the lines should look like this:

 +@BOXNAME:::::::::
 +:::::::::/sbin/nologin

   Once you have completed this task for all your machines, you will
   not have to modify the local versions of /etc/master.passwd ever
   again. All further changes can be handled by modifying the NIS
   map. Here is an example of a possible netgroup map for this
   scenario with some additional goodies:

 # Define groups of users first
 IT_EMP    (,alpha,test-domain)    (,beta,test-domain)
 IT_APP    (,charlie,test-domain)  (,delta,test-domain)
 DEPT1     (,echo,test-domain)     (,foxtrott,test-domain)
 DEPT2     (,golf,test-domain)     (,hotel,test-domain)
 DEPT3     (,india,test-domain)    (,juliet,test-domain)
 ITINTERN  (,kilo,test-domain)     (,lima,test-domain)
 D_INTERNS (,able,test-domain)     (,baker,test-domain)
 #
 # Now, define some groups based on roles
 USERS     DEPT1   DEPT2     DEPT3
 BIGSRV    IT_EMP  IT_APP
 SMALLSRV  IT_EMP  IT_APP    ITINTERN
 USERBOX   IT_EMP  ITINTERN  USERS
 #
 # And a groups for a special tasks
 # Allow echo and golf to access our anti-virus-machine
 SECURITY  IT_EMP  (,echo,test-domain)  (,golf,test-domain)
 #
 # machine-based netgroups
 # Our main servers
 WAR       BIGSRV
 FAMINE    BIGSRV
 # User india needs access to this server
 POLLUTION  BIGSRV  (,india,test-domain)
 #
 # This one is really important and needs more access restrictions
 DEATH     IT_EMP
 #
 # The anti-virus-machine mentioned above
 ONE       SECURITY
 #
 # Restrict a machine to a single user
 TWO       (,hotel,test-domain)
 # [...more groups to follow]

   If you are using some kind of database to manage your user
   accounts, you should be able to create the first part of the map
   with your database's report tools. This way, new users will
   automatically have access to the boxes.

   One last word of caution: It may not always be advisable to use
   machine-based netgroups. If you are deploying a couple of dozen or
   even hundreds of identical machines for student labs, you should
   use role-based netgroups instead of machine-based netgroups to
   keep the size of the NIS map within reasonable limits.

     --------------------------------------------------------------

  27.4.8. Important Things to Remember

   There are still a couple of things that you will need to do
   differently now that you are in an NIS environment.

     * Every time you wish to add a user to the lab, you must add it
       to the master NIS server only, and you must remember to
       rebuild the NIS maps. If you forget to do this, the new user
       will not be able to login anywhere except on the NIS master.
       For example, if we needed to add a new user jsmith to the lab,
       we would:

 # pw useradd jsmith
 # cd /var/yp
 # make test-domain

       You could also run adduser jsmith instead of pw useradd
       jsmith.

     * Keep the administration accounts out of the NIS maps. You do
       not want to be propagating administrative accounts and
       passwords to machines that will have users that should not
       have access to those accounts.

     * Keep the NIS master and slave secure, and minimize their
       downtime. If somebody either hacks or simply turns off these
       machines, they have effectively rendered many people without
       the ability to login to the lab.

       This is the chief weakness of any centralized administration
       system. If you do not protect your NIS servers, you will have
       a lot of angry users!

     --------------------------------------------------------------

  27.4.9. NIS v1 Compatibility

   FreeBSD's ypserv has some support for serving NIS v1 clients.
   FreeBSD's NIS implementation only uses the NIS v2 protocol,
   however other implementations include support for the v1 protocol
   for backwards compatibility with older systems. The ypbind daemons
   supplied with these systems will try to establish a binding to an
   NIS v1 server even though they may never actually need it (and
   they may persist in broadcasting in search of one even after they
   receive a response from a v2 server). Note that while support for
   normal client calls is provided, this version of ypserv does not
   handle v1 map transfer requests; consequently, it cannot be used
   as a master or slave in conjunction with older NIS servers that
   only support the v1 protocol. Fortunately, there probably are not
   any such servers still in use today.

     --------------------------------------------------------------

  27.4.10. NIS Servers That Are Also NIS Clients

   Care must be taken when running ypserv in a multi-server domain
   where the server machines are also NIS clients. It is generally a
   good idea to force the servers to bind to themselves rather than
   allowing them to broadcast bind requests and possibly become bound
   to each other. Strange failure modes can result if one server goes
   down and others are dependent upon it. Eventually all the clients
   will time out and attempt to bind to other servers, but the delay
   involved can be considerable and the failure mode is still present
   since the servers might bind to each other all over again.

   You can force a host to bind to a particular server by running
   ypbind with the -S flag. If you do not want to do this manually
   each time you reboot your NIS server, you can add the following
   lines to your /etc/rc.conf:

 nis_client_enable="YES" # run client stuff as well
 nis_client_flags="-S NIS domain,server"

   See ypbind(8) for further information.

     --------------------------------------------------------------

  27.4.11. Password Formats

   One of the most common issues that people run into when trying to
   implement NIS is password format compatibility. If your NIS server
   is using DES encrypted passwords, it will only support clients
   that are also using DES. For example, if you have Solaris NIS
   clients in your network, then you will almost certainly need to
   use DES encrypted passwords.

   To check which format your servers and clients are using, look at
   /etc/login.conf. If the host is configured to use DES encrypted
   passwords, then the default class will contain an entry like this:

 default:\
         :passwd_format=des:\
         :copyright=/etc/COPYRIGHT:\
         [Further entries elided]

   Other possible values for the passwd_format capability include blf
   and md5 (for Blowfish and MD5 encrypted passwords, respectively).

   If you have made changes to /etc/login.conf, you will also need to
   rebuild the login capability database, which is achieved by
   running the following command as root:

 # cap_mkdb /etc/login.conf

     -a`: The format of passwords already in /etc/master.passwd will
     not be updated until a user changes his password for the first
     time after the login capability database is rebuilt.

   Next, in order to ensure that passwords are encrypted with the
   format that you have chosen, you should also check that the
   crypt_default in /etc/auth.conf gives precedence to your chosen
   password format. To do this, place the format that you have chosen
   first in the list. For example, when using DES encrypted
   passwords, the entry would be:

 crypt_default   =       des blf md5

   Having followed the above steps on each of the FreeBSD based NIS
   servers and clients, you can be sure that they all agree on which
   password format is used within your network. If you have trouble
   authenticating on an NIS client, this is a pretty good place to
   start looking for possible problems. Remember: if you want to
   deploy an NIS server for a heterogenous network, you will probably
   have to use DES on all systems because it is the lowest common
   standard.

     --------------------------------------------------------------

27.5. Automatic Network Configuration (DHCP)

   Written by Greg Sutter.

  27.5.1. What Is DHCP?

   DHCP, the Dynamic Host Configuration Protocol, describes the means
   by which a system can connect to a network and obtain the
   necessary information for communication upon that network. FreeBSD
   versions prior to 6.0 use the ISC (Internet Software Consortium)
   DHCP client (dhclient(8)) implementation. Later versions use the
   OpenBSD dhclient taken from OpenBSD 3.7. All information here
   regarding dhclient is for use with either of the ISC or OpenBSD
   DHCP clients. The DHCP server is the one included in the ISC
   distribution.

     --------------------------------------------------------------

  27.5.2. What This Section Covers

   This section describes both the client-side components of the ISC
   and OpenBSD DHCP client and server-side components of the ISC DHCP
   system. The client-side program, dhclient, comes integrated within
   FreeBSD, and the server-side portion is available from the
   net/isc-dhcp3-server port. The dhclient(8), dhcp-options(5), and
   dhclient.conf(5) manual pages, in addition to the references
   below, are useful resources.

     --------------------------------------------------------------

  27.5.3. How It Works

   When dhclient, the DHCP client, is executed on the client machine,
   it begins broadcasting requests for configuration information. By
   default, these requests are on UDP port 68. The server replies on
   UDP 67, giving the client an IP address and other relevant network
   information such as netmask, router, and DNS servers. All of this
   information comes in the form of a DHCP !S:lease!" and is only
   valid for a certain time (configured by the DHCP server
   maintainer). In this manner, stale IP addresses for clients no
   longer connected to the network can be automatically reclaimed.

   DHCP clients can obtain a great deal of information from the
   server. An exhaustive list may be found in dhcp-options(5).

     --------------------------------------------------------------

  27.5.4. FreeBSD Integration

   FreeBSD fully integrates the ISC or OpenBSD DHCP client, dhclient
   (according to the FreeBSD version you run). DHCP client support is
   provided within both the installer and the base system, obviating
   the need for detailed knowledge of network configurations on any
   network that runs a DHCP server. dhclient has been included in all
   FreeBSD distributions since 3.2.

   DHCP is supported by sysinstall. When configuring a network
   interface within sysinstall, the second question asked is: !S:Do
   you want to try DHCP configuration of the interface?!". Answering
   affirmatively will execute dhclient, and if successful, will fill
   in the network configuration information automatically.

   There are two things you must do to have your system use DHCP upon
   startup:

     * Make sure that the bpf device is compiled into your kernel. To
       do this, add device bpf (pseudo-device bpf under FreeBSD 4.X)
       to your kernel configuration file, and rebuild the kernel. For
       more information about building kernels, see uU 8 ^3^1.

       The bpf device is already part of the GENERIC kernel that is
       supplied with FreeBSD, so if you do not have a custom kernel,
       you should not need to create one in order to get DHCP
       working.

         -a`: For those who are particularly security conscious, you
         should be warned that bpf is also the device that allows
         packet sniffers to work correctly (although they still have
         to be run as root). bpf is required to use DHCP, but if you
         are very sensitive about security, you probably should not
         add bpf to your kernel in the expectation that at some point
         in the future you will be using DHCP.

     * Edit your /etc/rc.conf to include the following:

 ifconfig_fxp0="DHCP"

         -a`: Be sure to replace fxp0 with the designation for the
         interface that you wish to dynamically configure, as
         described in uU 11.8 ,`.

       If you are using a different location for dhclient, or if you
       wish to pass additional flags to dhclient, also include the
       following (editing as necessary):

 dhcp_program="/sbin/dhclient"
 dhcp_flags=""

   The DHCP server, dhcpd, is included as part of the
   net/isc-dhcp3-server port in the ports collection. This port
   contains the ISC DHCP server and documentation.

     --------------------------------------------------------------

  27.5.5. Files

     * /etc/dhclient.conf

       dhclient requires a configuration file, /etc/dhclient.conf.
       Typically the file contains only comments, the defaults being
       reasonably sane. This configuration file is described by the
       dhclient.conf(5) manual page.

     * /sbin/dhclient

       dhclient is statically linked and resides in /sbin. The
       dhclient(8) manual page gives more information about dhclient.

     * /sbin/dhclient-script

       dhclient-script is the FreeBSD-specific DHCP client
       configuration script. It is described in dhclient-script(8),
       but should not need any user modification to function
       properly.

     * /var/db/dhclient.leases

       The DHCP client keeps a database of valid leases in this file,
       which is written as a log. dhclient.leases(5) gives a slightly
       longer description.

     --------------------------------------------------------------

  27.5.6. Further Reading

   The DHCP protocol is fully described in RFC 2131. An informational
   resource has also been set up at http://www.dhcp.org/.

     --------------------------------------------------------------

  27.5.7. Installing and Configuring a DHCP Server

    27.5.7.1. What This Section Covers

   This section provides information on how to configure a FreeBSD
   system to act as a DHCP server using the ISC (Internet Software
   Consortium) implementation of the DHCP suite.

   The server portion of the suite is not provided as part of
   FreeBSD, and so you will need to install the net/isc-dhcp3-server
   port to provide this service. See uU 4 ^3^1 for more information
   on using the Ports Collection.

     --------------------------------------------------------------

    27.5.7.2. DHCP Server Installation

   In order to configure your FreeBSD system as a DHCP server, you
   will need to ensure that the bpf(4) device is compiled into your
   kernel. To do this, add device bpf (pseudo-device bpf under
   FreeBSD 4.X) to your kernel configuration file, and rebuild the
   kernel. For more information about building kernels, see uU 8
   ^3^1.

   The bpf device is already part of the GENERIC kernel that is
   supplied with FreeBSD, so you do not need to create a custom
   kernel in order to get DHCP working.

     -a`: Those who are particularly security conscious should note
     that bpf is also the device that allows packet sniffers to work
     correctly (although such programs still need privileged access).
     bpf is required to use DHCP, but if you are very sensitive about
     security, you probably should not include bpf in your kernel
     purely because you expect to use DHCP at some point in the
     future.

   The next thing that you will need to do is edit the sample
   dhcpd.conf which was installed by the net/isc-dhcp3-server port.
   By default, this will be /usr/local/etc/dhcpd.conf.sample, and you
   should copy this to /usr/local/etc/dhcpd.conf before proceeding to
   make changes.

     --------------------------------------------------------------

    27.5.7.3. Configuring the DHCP Server

   dhcpd.conf is comprised of declarations regarding subnets and
   hosts, and is perhaps most easily explained using an example :

 option domain-name "example.com";(1)
 option domain-name-servers 192.168.4.100;(2)
 option subnet-mask 255.255.255.0;(3)

 default-lease-time 3600;(4)
 max-lease-time 86400;(5)
 ddns-update-style none;(6)

 subnet 192.168.4.0 netmask 255.255.255.0 {
   range 192.168.4.129 192.168.4.254;(7)
   option routers 192.168.4.1;(8)
 }

 host mailhost {
   hardware ethernet 02:03:04:05:06:07;(9)
   fixed-address mailhost.example.com;(10)
 }

   (1)
           This option specifies the domain that will be provided to
           clients as the default search domain. See resolv.conf(5)
           for more information on what this means.
   (2)
           This option specifies a comma separated list of DNS
           servers that the client should use.
   (3)
           The netmask that will be provided to clients.
   (4)
           A client may request a specific length of time that a
           lease will be valid. Otherwise the server will assign a
           lease with this expiry value (in seconds).
   (5)
           This is the maximum length of time that the server will
           lease for. Should a client request a longer lease, a lease
           will be issued, although it will only be valid for
           max-lease-time seconds.
   (6)
           This option specifies whether the DHCP server should
           attempt to update DNS when a lease is accepted or
           released. In the ISC implementation, this option is
           required.
   (7)
           This denotes which IP addresses should be used in the pool
           reserved for allocating to clients. IP addresses between,
           and including, the ones stated are handed out to clients.
   (8)
           Declares the default gateway that will be provided to
           clients.
   (9)
           The hardware MAC address of a host (so that the DHCP
           server can recognize a host when it makes a request).
   (10)
           Specifies that the host should always be given the same IP
           address. Note that using a hostname is correct here, since
           the DHCP server will resolve the hostname itself before
           returning the lease information.

   Once you have finished writing your dhcpd.conf, you can proceed to
   start the server by issuing the following command:

 # /usr/local/etc/rc.d/isc-dhcpd.sh start

   Should you need to make changes to the configuration of your
   server in the future, it is important to note that sending a
   SIGHUP signal to dhcpd does not result in the configuration being
   reloaded, as it does with most daemons. You will need to send a
   SIGTERM signal to stop the process, and then restart it using the
   command above.

     --------------------------------------------------------------

    27.5.7.4. Files

     * /usr/local/sbin/dhcpd

       dhcpd is statically linked and resides in /usr/local/sbin. The
       dhcpd(8) manual page installed with the port gives more
       information about dhcpd.

     * /usr/local/etc/dhcpd.conf

       dhcpd requires a configuration file, /usr/local/etc/dhcpd.conf
       before it will start providing service to clients. This file
       needs to contain all the information that should be provided
       to clients that are being serviced, along with information
       regarding the operation of the server. This configuration file
       is described by the dhcpd.conf(5) manual page installed by the
       port.

     * /var/db/dhcpd.leases

       The DHCP server keeps a database of leases it has issued in
       this file, which is written as a log. The manual page
       dhcpd.leases(5), installed by the port gives a slightly longer
       description.

     * /usr/local/sbin/dhcrelay

       dhcrelay is used in advanced environments where one DHCP
       server forwards a request from a client to another DHCP server
       on a separate network. If you require this functionality, then
       install the net/isc-dhcp3-relay port. The dhcrelay(8) manual
       page provided with the port contains more detail.

     --------------------------------------------------------------

27.6. Domain Name System (DNS)

   Contributed by Chern Lee.

  27.6.1. Overview

   FreeBSD utilizes, by default, a version of BIND (Berkeley Internet
   Name Domain), which is the most common implementation of the DNS
   protocol. DNS is the protocol through which names are mapped to IP
   addresses, and vice versa. For example, a query for
   www.FreeBSD.org will receive a reply with the IP address of The
   FreeBSD Project's web server, whereas, a query for ftp.FreeBSD.org
   will return the IP address of the corresponding FTP machine.
   Likewise, the opposite can happen. A query for an IP address can
   resolve its hostname. It is not necessary to run a name server to
   perform DNS lookups on a system.

   DNS is coordinated across the Internet through a somewhat complex
   system of authoritative root name servers, and other smaller-scale
   name servers who host and cache individual domain information.

   This document refers to BIND 8.x, as it is the stable version used
   in FreeBSD. Versions of FreeBSD 5.3 and beyond include BIND9 and
   the configuration instructions may be found later in this chapter.
   Users of FreeBSD 5.2 and other previous versions may install BIND9
   from the net/bind9 port.

   RFC1034 and RFC1035 dictate the DNS protocol.

   Currently, BIND is maintained by the Internet Software Consortium
   http://www.isc.org/.

     --------------------------------------------------------------

  27.6.2. Terminology

   To understand this document, some terms related to DNS must be
   understood.

       Term                          Definition                       
   Forward DNS  Mapping of hostnames to IP addresses                  
   Origin       Refers to the domain covered in a particular zone     
                file                                                  
   named, BIND, Common names for the BIND name server package within  
   name server  FreeBSD                                               
   Resolver     A system process through which a machine queries a    
                name server for zone information                      
   Reverse DNS  The opposite of forward DNS; mapping of IP addresses  
                to hostnames                                          
                The beginning of the Internet zone hierarchy. All     
   Root zone    zones fall under the root zone, similar to how all    
                files in a file system fall under the root directory. 
   Zone         An individual domain, subdomain, or portion of the    
                DNS administered by the same authority                

   Examples of zones:

     * . is the root zone

     * org. is a zone under the root zone

     * example.org. is a zone under the org. zone

     * foo.example.org. is a subdomain, a zone under the example.org.
       zone

     *  1.2.3.in-addr.arpa is a zone referencing all IP addresses
       which fall under the 3.2.1.* IP space.

   As one can see, the more specific part of a hostname appears to
   its left. For example, example.org. is more specific than org., as
   org. is more specific than the root zone. The layout of each part
   of a hostname is much like a file system: the /dev directory falls
   within the root, and so on.

     --------------------------------------------------------------

  27.6.3. Reasons to Run a Name Server

   Name servers usually come in two forms: an authoritative name
   server, and a caching name server.

   An authoritative name server is needed when:

     * one wants to serve DNS information to the world, replying
       authoritatively to queries.

     * a domain, such as example.org, is registered and IP addresses
       need to be assigned to hostnames under it.

     * an IP address block requires reverse DNS entries (IP to
       hostname).

     * a backup name server, called a slave, must reply to queries
       when the primary is down or inaccessible.

   A caching name server is needed when:

     * a local DNS server may cache and respond more quickly than
       querying an outside name server.

     * a reduction in overall network traffic is desired (DNS traffic
       has been measured to account for 5% or more of total Internet
       traffic).

   When one queries for www.FreeBSD.org, the resolver usually queries
   the uplink ISP's name server, and retrieves the reply. With a
   local, caching DNS server, the query only has to be made once to
   the outside world by the caching DNS server. Every additional
   query will not have to look to the outside of the local network,
   since the information is cached locally.

     --------------------------------------------------------------

  27.6.4. How It Works

   In FreeBSD, the BIND daemon is called named for obvious reasons.

            File                          Description                 
   named                  the BIND daemon                             
   ndc                    name daemon control program                 
   /etc/namedb            directory where BIND zone information       
                          resides                                     
   /etc/namedb/named.conf daemon configuration file                   

   Zone files are usually contained within the /etc/namedb directory,
   and contain the DNS zone information served by the name server.

     --------------------------------------------------------------

  27.6.5. Starting BIND

   Since BIND is installed by default, configuring it all is
   relatively simple.

   To ensure the named daemon is started at boot, put the following
   line in /etc/rc.conf:

 named_enable="YES"

   To start the daemon manually (after configuring it):

 # ndc start

     --------------------------------------------------------------

  27.6.6. Configuration Files

     --------------------------------------------------------------

    27.6.6.1. Using make-localhost

   Be sure to:

 # cd /etc/namedb
 # sh make-localhost

   to properly create the local reverse DNS zone file in
   /etc/namedb/master/localhost.rev.

     --------------------------------------------------------------

    27.6.6.2. /etc/namedb/named.conf

 // $FreeBSD$
 //
 // Refer to the named(8) manual page for details.  If you are ever going
 // to setup a primary server, make sure you've understood the hairy
 // details of how DNS is working.  Even with simple mistakes, you can
 // break connectivity for affected parties, or cause huge amount of
 // useless Internet traffic.

 options {
         directory "/etc/namedb";

 // In addition to the "forwarders" clause, you can force your name
 // server to never initiate queries of its own, but always ask its
 // forwarders only, by enabling the following line:
 //
 //      forward only;

 // If you've got a DNS server around at your upstream provider, enter
 // its IP address here, and enable the line below.  This will make you
 // benefit from its cache, thus reduce overall DNS traffic in the
 Internet.
 /*
         forwarders {
                 127.0.0.1;
         };
 */

   Just as the comment says, to benefit from an uplink's cache,
   forwarders can be enabled here. Under normal circumstances, a name
   server will recursively query the Internet looking at certain name
   servers until it finds the answer it is looking for. Having this
   enabled will have it query the uplink's name server (or name
   server provided) first, taking advantage of its cache. If the
   uplink name server in question is a heavily trafficked, fast name
   server, enabling this may be worthwhile.

     A:uS:i127.0.0.1 will not work here. Change this IP address to a
     name server at your uplink.

         /*
          * If there is a firewall between you and name servers you want
          * to talk to, you might need to uncomment the query-source
          * directive below.  Previous versions of BIND always asked
          * questions using port 53, but BIND 8.1 uses an unprivileged
          * port by default.
          */
         // query-source address * port 53;

         /*
          * If running in a sandbox, you may have to specify a different
          * location for the dumpfile.
          */
         // dump-file "s/named_dump.db";
 };

 // Note: the following will be supported in a future release.
 /*
 host { any; } {
         topology {
                 127.0.0.0/8;
         };
 };
 */

 // Setting up secondaries is way easier and the rough picture for this
 // is explained below.
 //
 // If you enable a local name server, don't forget to enter 127.0.0.1
 // into your /etc/resolv.conf so this server will be queried first.
 // Also, make sure to enable it in /etc/rc.conf.

 zone "." {
         type hint;
         file "named.root";
 };

 zone "0.0.127.IN-ADDR.ARPA" {
         type master;
         file "localhost.rev";
 };

 // NB: Do not use the IP addresses below, they are faked, and only
 // serve demonstration/documentation purposes!
 //
 // Example secondary config entries.  It can be convenient to become
 // a secondary at least for the zone where your own domain is in.  Ask
 // your network administrator for the IP address of the responsible
 // primary.
 //
 // Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
 // (This is the first bytes of the respective IP address, in reverse
 // order, with ".IN-ADDR.ARPA" appended.)
 //
 // Before starting to setup a primary zone, better make sure you fully
 // understand how DNS and BIND works, however.  There are sometimes
 // unobvious pitfalls.  Setting up a secondary is comparably simpler.
 //
 // NB: Don't blindly enable the examples below. :-)  Use actual names
 // and addresses instead.
 //
 // NOTE!!! FreeBSD runs BIND in a sandbox (see named_flags in rc.conf).
 // The directory containing the secondary zones must be write accessible
 // to BIND.  The following sequence is suggested:
 //
 //      mkdir /etc/namedb/s
 //      chown bind:bind /etc/namedb/s
 //      chmod 750 /etc/namedb/s

   For more information on running BIND in a sandbox, see Running
   named in a sandbox.

 /*
 zone "example.com" {
         type slave;
         file "s/example.com.bak";
         masters {
                 192.168.1.1;
         };
 };

 zone "0.168.192.in-addr.arpa" {
         type slave;
         file "s/0.168.192.in-addr.arpa.bak";
         masters {
                 192.168.1.1;
         };
 };
 */

   In named.conf, these are examples of slave entries for a forward
   and reverse zone.

   For each new zone served, a new zone entry must be added to
   named.conf.

   For example, the simplest zone entry for example.org can look
   like:

 zone "example.org" {
         type master;
         file "example.org";
 };

   The zone is a master, as indicated by the type statement, holding
   its zone information in /etc/namedb/example.org indicated by the
   file statement.

 zone "example.org" {
         type slave;
         file "example.org";
 };

   In the slave case, the zone information is transferred from the
   master name server for the particular zone, and saved in the file
   specified. If and when the master server dies or is unreachable,
   the slave name server will have the transferred zone information
   and will be able to serve it.

     --------------------------------------------------------------

    27.6.6.3. Zone Files

   An example master zone file for example.org (existing within
   /etc/namedb/example.org) is as follows:

 $TTL 3600

 example.org. IN SOA ns1.example.org. admin.example.org. (
                         5               ; Serial
                         10800           ; Refresh
                         3600            ; Retry
                         604800          ; Expire
                         86400 )         ; Minimum TTL

 ; DNS Servers
 @       IN NS           ns1.example.org.
 @       IN NS           ns2.example.org.

 ; Machine Names
 localhost       IN A    127.0.0.1
 ns1             IN A    3.2.1.2
 ns2             IN A    3.2.1.3
 mail            IN A    3.2.1.10
 @               IN A    3.2.1.30

 ; Aliases
 www             IN CNAME        @

 ; MX Record
 @               IN MX   10      mail.example.org.

   Note that every hostname ending in a !S:.!" is an exact hostname,
   whereas everything without a trailing !S:.!" is referenced to the
   origin. For example, www is translated into www.origin. In our
   fictitious zone file, our origin is example.org., so www would
   translate to www.example.org.

   The format of a zone file follows:

 recordname      IN recordtype   value

   The most commonly used DNS records:

   SOA

           start of zone authority

   NS

           an authoritative name server

   A

           a host address

   CNAME

           the canonical name for an alias

   MX

           mail exchanger

   PTR

           a domain name pointer (used in reverse DNS)

 example.org. IN SOA ns1.example.org. admin.example.org. (
                         5               ; Serial
                         10800           ; Refresh after 3 hours
                         3600            ; Retry after 1 hour
                         604800          ; Expire after 1 week
                         86400 )         ; Minimum TTL of 1 day

   example.org.

           the domain name, also the origin for this zone file.

   ns1.example.org.

           the primary/authoritative name server for this zone.

   admin.example.org.

           the responsible person for this zone, email address with
           !S:@!" replaced. (<admin@example.org> becomes
           admin.example.org)

   5

           the serial number of the file. This must be incremented
           each time the zone file is modified. Nowadays, many admins
           prefer a yyyymmddrr format for the serial number.
           2001041002 would mean last modified 04/10/2001, the latter
           02 being the second time the zone file has been modified
           this day. The serial number is important as it alerts
           slave name servers for a zone when it is updated.

 @       IN NS           ns1.example.org.

   This is an NS entry. Every name server that is going to reply
   authoritatively for the zone must have one of these entries. The @
   as seen here could have been example.org. The @ translates to the
   origin.

 localhost       IN A    127.0.0.1
 ns1             IN A    3.2.1.2
 ns2             IN A    3.2.1.3
 mail            IN A    3.2.1.10
 @               IN A    3.2.1.30

   The A record indicates machine names. As seen above,
   ns1.example.org would resolve to 3.2.1.2. Again, the origin
   symbol, @, is used here, thus meaning example.org would resolve to
   3.2.1.30.

 www             IN CNAME        @

   The canonical name record is usually used for giving aliases to a
   machine. In the example, www is aliased to the machine addressed
   to the origin, or example.org (3.2.1.30). CNAMEs can be used to
   provide alias hostnames, or round robin one hostname among
   multiple machines.

 @               IN MX   10      mail.example.org.

   The MX record indicates which mail servers are responsible for
   handling incoming mail for the zone. mail.example.org is the
   hostname of the mail server, and 10 being the priority of that
   mail server.

   One can have several mail servers, with priorities of 3, 2, 1. A
   mail server attempting to deliver to example.org would first try
   the highest priority MX, then the second highest, etc, until the
   mail can be properly delivered.

   For in-addr.arpa zone files (reverse DNS), the same format is
   used, except with PTR entries instead of A or CNAME.

 $TTL 3600

 1.2.3.in-addr.arpa. IN SOA ns1.example.org. admin.example.org. (
                         5               ; Serial
                         10800           ; Refresh
                         3600            ; Retry
                         604800          ; Expire
                         3600 )          ; Minimum

 @       IN NS   ns1.example.org.
 @       IN NS   ns2.example.org.

 2       IN PTR  ns1.example.org.
 3       IN PTR  ns2.example.org.
 10      IN PTR  mail.example.org.
 30      IN PTR  example.org.

   This file gives the proper IP address to hostname mappings of our
   above fictitious domain.

     --------------------------------------------------------------

  27.6.7. Caching Name Server

   A caching name server is a name server that is not authoritative
   for any zones. It simply asks queries of its own, and remembers
   them for later use. To set one up, just configure the name server
   as usual, omitting any inclusions of zones.

     --------------------------------------------------------------

  27.6.8. Running named in a Sandbox

   For added security you may want to run named(8) as an unprivileged
   user, and configure it to chroot(8) into a sandbox directory. This
   makes everything outside of the sandbox inaccessible to the named
   daemon. Should named be compromised, this will help to reduce the
   damage that can be caused. By default, FreeBSD has a user and a
   group called bind, intended for this use.

     -a`: Various people would recommend that instead of configuring
     named to chroot, you should run named inside a jail(8). This
     section does not attempt to cover this situation.

   Since named will not be able to access anything outside of the
   sandbox (such as shared libraries, log sockets, and so on), there
   are a number of steps that need to be followed in order to allow
   named to function correctly. In the following checklist, it is
   assumed that the path to the sandbox is /etc/namedb and that you
   have made no prior modifications to the contents of this
   directory. Perform the following steps as root:

     * Create all directories that named expects to see:

 # cd /etc/namedb
 # mkdir -p bin dev etc var/tmp var/run master slave
 # chown bind:bind slave var/*(1)

            (1)
                    named only needs write access to these
                    directories, so that is all we give it.
     * Rearrange and create basic zone and configuration files:

 # cp /etc/localtime etc(1)
 # mv named.conf etc && ln -sf etc/named.conf
 # mv named.root master

 # sh make-localhost
 # cat > master/named.localhost
 $ORIGIN localhost.
 $TTL 6h
 @       IN      SOA     localhost. postmaster.localhost. (
                         1       ; serial
                         3600    ; refresh
                         1800    ; retry
                         604800  ; expiration
                         3600 )  ; minimum
         IN      NS      localhost.
         IN      A               127.0.0.1
 ^D

            (1)
                    This allows named to log the correct time to
                    syslogd(8).
     * If you are running a version of FreeBSD prior to 4.9-RELEASE,
       build a statically linked copy of named-xfer, and copy it into
       the sandbox:

 # cd /usr/src/lib/libisc
 # make cleandir && make cleandir && make depend && make all
 # cd /usr/src/lib/libbind
 # make cleandir && make cleandir && make depend && make all
 # cd /usr/src/libexec/named-xfer
 # make cleandir && make cleandir && make depend && make NOSHARED=yes all
 # cp named-xfer /etc/namedb/bin && chmod 555 /etc/namedb/bin/named-xfer(1)

       After your statically linked named-xfer is installed some
       cleaning up is required, to avoid leaving stale copies of
       libraries or programs in your source tree:

 # cd /usr/src/lib/libisc
 # make cleandir
 # cd /usr/src/lib/libbind
 # make cleandir
 # cd /usr/src/libexec/named-xfer
 # make cleandir

            (1)
                    This step has been reported to fail occasionally.
                    If this happens to you, then issue the command:

 # cd /usr/src && make cleandir && make cleandir

                    and delete your /usr/obj tree:

 # rm -fr /usr/obj && mkdir /usr/obj

                    This will clean out any !S:cruft!" from your
                    source tree, and retrying the steps above should
                    then work.

       If you are running FreeBSD version 4.9-RELEASE or later, then
       the copy of named-xfer in /usr/libexec is statically linked by
       default, and you can simply use cp(1) to copy it into your
       sandbox.

     * Make a dev/null that named can see and write to:

 # cd /etc/namedb/dev && mknod null c 2 2
 # chmod 666 null

     * Symlink /var/run/ndc to /etc/namedb/var/run/ndc:

 # ln -sf /etc/namedb/var/run/ndc /var/run/ndc

         -a`: This simply avoids having to specify the -c option to
         ndc(8) every time you run it. Since the contents of /var/run
         are deleted on boot, it may be useful to add this command to
         root's crontab(5), using the @reboot option.

     * Configure syslogd(8) to create an extra log socket that named
       can write to. To do this, add -l /etc/namedb/dev/log to the
       syslogd_flags variable in /etc/rc.conf.

     * Arrange to have named start and chroot itself to the sandbox
       by adding the following to /etc/rc.conf:

 named_enable="YES"
 named_flags="-u bind -g bind -t /etc/namedb /etc/named.conf"

         -a`: Note that the configuration file /etc/named.conf is
         denoted by a full pathname relative to the sandbox, i.e. in
         the line above, the file referred to is actually
         /etc/namedb/etc/named.conf.

   The next step is to edit /etc/namedb/etc/named.conf so that named
   knows which zones to load and where to find them on the disk.
   There follows a commented example (anything not specifically
   commented here is no different from the setup for a DNS server not
   running in a sandbox):

 options {
         directory "/";(1)
         named-xfer "/bin/named-xfer";(2)
         version "";             // Don't reveal BIND version
         query-source address * port 53;
 };
 // ndc control socket
 controls {
         unix "/var/run/ndc" perm 0600 owner 0 group 0;
 };
 // Zones follow:
 zone "localhost" IN {
         type master;
         file "master/named.localhost";(3)
         allow-transfer { localhost; };
         notify no;
 };
 zone "0.0.127.in-addr.arpa" IN {
         type master;
         file "master/localhost.rev";
         allow-transfer { localhost; };
         notify no;
 };
 zone "." IN {
         type hint;
         file "master/named.root";
 };
 zone "private.example.net" in {
         type master;
         file "master/private.example.net.db";
         allow-transfer { 192.168.10.0/24; };
 };
 zone "10.168.192.in-addr.arpa" in {
         type slave;
         masters { 192.168.10.2; };
         file "slave/192.168.10.db";(4)
 };

   (1)
           The directory statement is specified as /, since all files
           that named needs are within this directory (recall that
           this is equivalent to a !S:normal!" user's /etc/namedb).
   (2)
           Specifies the full path to the named-xfer binary (from
           named's frame of reference). This is necessary since named
           is compiled to look for named-xfer in /usr/libexec by
           default.
   (3)
           Specifies the filename (relative to the directory
           statement above) where named can find the zone file for
           this zone.
   (4)
           Specifies the filename (relative to the directory
           statement above) where named should write a copy of the
           zone file for this zone after successfully transferring it
           from the master server. This is why we needed to change
           the ownership of the directory slave to bind in the setup
           stages above.

   After completing the steps above, either reboot your server or
   restart syslogd(8) and start named(8), making sure to use the new
   options specified in syslogd_flags and named_flags. You should now
   be running a sandboxed copy of named!

     --------------------------------------------------------------

  27.6.9. Security

   Although BIND is the most common implementation of DNS, there is
   always the issue of security. Possible and exploitable security
   holes are sometimes found.

   It is a good idea to read CERT's security advisories and to
   subscribe to the FreeBSD security notifications P:l>> 1/4 1/2 *
   3/4A to stay up to date with the current Internet and FreeBSD
   security issues.

     '-L-YENU:: If a problem arises, keeping sources up to date and
     having a fresh build of named would not hurt.

     --------------------------------------------------------------

  27.6.10. Further Reading

   BIND/named manual pages: ndc(8) named(8) named.conf(5)

     * Official ISC BIND Page

     * BIND FAQ

     * O'Reilly DNS and BIND 4th Edition

     * RFC1034 - Domain Names - Concepts and Facilities

     * RFC1035 - Domain Names - Implementation and Specification

     --------------------------------------------------------------

27.7. BIND9 and FreeBSD

   Written by Tom Rhodes.

   The release of FreeBSD 5.3 brought the BIND9 DNS server software
   into the distribution. New security features, a new file system
   layout and automated chroot(8) configuration came with the import.
   This section has been written in two parts, the first will discuss
   new features and their configuration; the latter will cover
   upgrades to aid in move to FreeBSD 5.3. From this moment on, the
   server will be referred to simply as named(8) in place of BIND.
   This section skips over the terminology described in the previous
   section as well as some of the theoretical discussions; thus, it
   is recommended that the previous section be consulted before
   reading any further here.

   Configuration files for named currently reside in
   /var/named/etc/namedb/ and will need modification before use. This
   is where most of the configuration will be performed.

     --------------------------------------------------------------

  27.7.1. Configuration of a Master Zone

   To configure a master zone visit /var/named/etc/namedb/ and run
   the following command:

 # sh make-localhost

   If all went well a new file should exist in the master directory.
   The filenames should be localhost.rev for the local domain name
   and localhost-v6.rev for IPv6 configurations. As the default
   configuration file, configuration for its use will already be
   present in the named.conf file.

     --------------------------------------------------------------

  27.7.2. Configuration of a Slave Zone

   Configuration for extra domains or sub domains may be done
   properly by setting them as a slave zone. In most cases, the
   master/localhost.rev file could just be copied over into the slave
   directory and modified. Once completed, the files need to be
   properly added in named.conf such as in the following
   configuration for example.com:

 zone "example.com" {
         type slave;
         file "slave/example.com";
         masters {
                 10.0.0.1;
         };
 };

 zone "0.168.192.in-addr.arpa" {
         type slave;
         file "slave/0.168.192.in-addr.arpa";
         masters {
                 10.0.0.1;
         };
 };

   Note well that in this example, the master IP address is the
   primary domain server from which the zones are transferred; it
   does not necessary serve as DNS server itself.

     --------------------------------------------------------------

  27.7.3. System Initialization Configuration

   In order for the named daemon to start when the system is booted,
   the following option must be present in the rc.conf file:

 named_enable="YES"

   While other options exist, this is the bare minimal requirement.
   Consult the rc.conf(5) manual page for a list of the other
   options. If nothing is entered in the rc.conf file then named may
   be started on the command line by invoking:

 # /etc/rc.d/named start

     --------------------------------------------------------------

  27.7.4. BIND9 Security

   While FreeBSD automatically drops named into a chroot(8)
   environment; there are several other security mechanisms in place
   which could help to lure off possible DNS service attacks.

     --------------------------------------------------------------

    27.7.4.1. Query Access Control Lists

   A query access control list can be used to restrict queries
   against the zones. The configuration works by defining the network
   inside of the acl token and then listing IP addresses in the zone
   configuration. To permit domains to query the example host, just
   define it like this:

 acl "example.com" {
         192.168.0.0/24;
 };

 zone "example.com" {
         type slave;
         file "slave/example.com";
         masters {
                 10.0.0.1;
         };
         allow-query { example.com; };
 };

 zone "0.168.192.in-addr.arpa" {
         type slave;
         file "slave/0.168.192.in-addr.arpa";
         masters {
                 10.0.0.1;
         };
         allow-query { example.com; };
 };

     --------------------------------------------------------------

    27.7.4.2. Restrict Version

   Permitting version lookups on the DNS server could be opening the
   doors for an attacker. A malicious user may use this information
   to hunt up known exploits or bugs to utilize against the host.

     A:uS:iSetting a false version will not protect the server from
     exploits. Only upgrading to a version that is not vulnerable
     will protect your server.

   A false version string can be placed the options section of
   named.conf:

 options {
         directory       "/etc/namedb";
         pid-file        "/var/run/named/pid";
         dump-file       "/var/dump/named_dump.db";
         statistics-file "/var/stats/named.stats";
         version         "None of your business";
 };

     --------------------------------------------------------------

27.8. Apache HTTP Server

   Contributed by Murray Stokely.

     --------------------------------------------------------------

  27.8.1. Overview

   FreeBSD is used to run some of the busiest web sites in the world.
   The majority of web servers on the Internet are using the Apache
   HTTP Server. Apache software packages should be included on your
   FreeBSD installation media. If you did not install Apache when you
   first installed FreeBSD, then you can install it from the
   www/apache13 or www/apache20 port.

   Once Apache has been installed successfully, it must be
   configured.

     -a`: This section covers version 1.3.X of the Apache HTTP Server
     as that is the most widely used version for FreeBSD. Apache 2.X
     introduces many new technologies but they are not discussed
     here. For more information about Apache 2.X, please see
     http://httpd.apache.org/.

     --------------------------------------------------------------

  27.8.2. Configuration

   The main Apache HTTP Server configuration file is installed as
   /usr/local/etc/apache/httpd.conf on FreeBSD. This file is a
   typical UNIX text configuration file with comment lines beginning
   with the # character. A comprehensive description of all possible
   configuration options is outside the scope of this book, so only
   the most frequently modified directives will be described here.

   ServerRoot "/usr/local"

           This specifies the default directory hierarchy for the
           Apache installation. Binaries are stored in the bin and
           sbin subdirectories of the server root, and configuration
           files are stored in etc/apache.

   ServerAdmin you@your.address

           The address to which problems with the server should be
           emailed. This address appears on some server-generated
           pages, such as error documents.

   ServerName www.example.com

           ServerName allows you to set a host name which is sent
           back to clients for your server if it is different to the
           one that the host is configured with (i.e., use www
           instead of the host's real name).

   DocumentRoot "/usr/local/www/data"

           DocumentRoot: The directory out of which you will serve
           your documents. By default, all requests are taken from
           this directory, but symbolic links and aliases may be used
           to point to other locations.

   It is always a good idea to make backup copies of your Apache
   configuration file before making changes. Once you are satisfied
   with your initial configuration you are ready to start running
   Apache.

     --------------------------------------------------------------

  27.8.3. Running Apache

   Apache does not run from the inetd super server as many other
   network servers do. It is configured to run standalone for better
   performance for incoming HTTP requests from client web browsers. A
   shell script wrapper is included to make starting, stopping, and
   restarting the server as simple as possible. To start up Apache
   for the first time, just run:

 # /usr/local/sbin/apachectl start

   You can stop the server at any time by typing:

 # /usr/local/sbin/apachectl stop

   After making changes to the configuration file for any reason, you
   will need to restart the server:

 # /usr/local/sbin/apachectl restart

   To restart Apache without aborting current connections, run:

 # /usr/local/sbin/apachectl graceful

   Additional information available at apachectl(8) manual page.

   To launch Apache at system startup, add the following line to
   /etc/rc.conf:

 apache_enable="YES"

   If you would like to supply additional command line options for
   the Apache httpd program started at system boot, you may specify
   them with an additional line in rc.conf:

 apache_flags=""

   Now that the web server is running, you can view your web site by
   pointing a web browser to http://localhost/. The default web page
   that is displayed is /usr/local/www/data/index.html.

     --------------------------------------------------------------

  27.8.4. Virtual Hosting

   Apache supports two different types of Virtual Hosting. The first
   method is Name-based Virtual Hosting. Name-based virtual hosting
   uses the clients HTTP/1.1 headers to figure out the hostname. This
   allows many different domains to share the same IP address.

   To setup Apache to use Name-based Virtual Hosting add an entry
   like the following to your httpd.conf:

 NameVirtualHost *

   If your webserver was named www.domain.tld and you wanted to setup
   a virtual domain for www.someotherdomain.tld then you would add
   the following entries to httpd.conf:

 <VirtualHost *>
 ServerName www.domain.tld
 DocumentRoot /www/domain.tld
 </VirtualHost>

 <VirtualHost *>
 ServerName www.someotherdomain.tld
 DocumentRoot /www/someotherdomain.tld
 </VirtualHost>

   Replace the addresses with the addresses you want to use and the
   path to the documents with what you are using.

   For more information about setting up virtual hosts, please
   consult the official Apache documentation at:
   http://httpd.apache.org/docs/vhosts/.

     --------------------------------------------------------------

  27.8.5. Apache Modules

   There are many different Apache modules available to add
   functionality to the basic server. The FreeBSD Ports Collection
   provides an easy way to install Apache together with some of the
   more popular add-on modules.

     --------------------------------------------------------------

    27.8.5.1. mod_ssl

   The mod_ssl module uses the OpenSSL library to provide strong
   cryptography via the Secure Sockets Layer (SSL v2/v3) and
   Transport Layer Security (TLS v1) protocols. This module provides
   everything necessary to request a signed certificate from a
   trusted certificate signing authority so that you can run a secure
   web server on FreeBSD.

   If you have not yet installed Apache, then a version of Apache
   1.3.X that includes mod_ssl may be installed with the
   www/apache13-modssl port. SSL support is also available for
   Apache 2.X in the www/apache20 port, where it is enabled by
   default.

     --------------------------------------------------------------

    27.8.5.2. Dynamic Websites with Perl & PHP

   In the past few years, more businesses have turned to the Internet
   in order to enhance their revenue and increase exposure. This has
   also increased the need for interactive web content. While some
   companies, such as Microsoft, have introduced solutions into their
   proprietary products, the open source community answered the call.
   Two options for dynamic web content include mod_perl & mod_php.

     --------------------------------------------------------------

      27.8.5.2.1. mod_perl

   The Apache/Perl integration project brings together the full power
   of the Perl programming language and the Apache HTTP Server. With
   the mod_perl module it is possible to write Apache modules
   entirely in Perl. In addition, the persistent interpreter embedded
   in the server avoids the overhead of starting an external
   interpreter and the penalty of Perl start-up time.

   mod_perl is available a few different ways. To use mod_perl
   remember that mod_perl 1.0 only works with Apache 1.3 and mod_perl
   2.0 only works with Apache 2. mod_perl 1.0 is available in
   www/mod_perl and a statically compiled version is available in
   www/apache13-modperl. mod_perl 2.0 is avaliable in www/mod_perl2.

     --------------------------------------------------------------

      27.8.5.2.2. mod_php

   Written by Tom Rhodes.

   PHP, also known as !S:PHP: Hypertext Preprocessor!" is a
   general-purpose scripting language that is especially suited for
   Web development. Capable of being embedded into HTML its syntax
   draws upon C, Java, and Perl with the intention of allowing web
   developers to write dynamically generated webpages quickly.

   To gain support for PHP5 for the Apache web server, begin by
   installing the www/mod_php5 port.

   This will install and configure the modules required to support
   dynamic PHP applications. Check to ensure the following lines have
   been added to /usr/local/etc/apache/httpd.conf:

 LoadModule php5_module        libexec/apache/libphp5.so
 AddModule mod_php5.c
     <IfModule mod_php5.c>
         DirectoryIndex index.php index.html
     </IfModule>

     <IfModule mod_php5.c>
         AddType application/x-httpd-php .php
         AddType application/x-httpd-php-source .phps
     </IfModule>

   Once completed, a simple call to the apachectl command for a
   graceful restart is needed to load the PHP module:

 # apachectl graceful

   The PHP support in FreeBSD is extremely modular so the base
   install is very limited. It is very easy to add support using the
   lang/php5-extensions port. This port provides a menu driven
   interface to PHP extension installation. Alternatively, individual
   extensions can be installed using the appropriate port.

   For instance, to add support for the MySQL database server to
   PHP5, simply install the databases/php5-mysql port.

   After installing an extension, the Apache server must be reloaded
   to pick up the new configuration changes.

 # apachectl graceful

     --------------------------------------------------------------

27.9. File Transfer Protocol (FTP)

   Contributed by Murray Stokely.

     --------------------------------------------------------------

  27.9.1. Overview

   The File Transfer Protocol (FTP) provides users with a simple way
   to transfer files to and from an FTP server. FreeBSD includes FTP
   server software, ftpd, in the base system. This makes setting up
   and administering an FTP server on FreeBSD very straightforward.

     --------------------------------------------------------------

  27.9.2. Configuration

   The most important configuration step is deciding which accounts
   will be allowed access to the FTP server. A normal FreeBSD system
   has a number of system accounts used for various daemons, but
   unknown users should not be allowed to log in with these accounts.
   The /etc/ftpusers file is a list of users disallowed any FTP
   access. By default, it includes the aforementioned system
   accounts, but it is possible to add specific users here that
   should not be allowed access to FTP.

   You may want to restrict the access of some users without
   preventing them completely from using FTP. This can be
   accomplished with the /etc/ftpchroot file. This file lists users
   and groups subject to FTP access restrictions. The ftpchroot(5)
   manual page has all of the details so it will not be described in
   detail here.

   If you would like to enable anonymous FTP access to your server,
   then you must create a user named ftp on your FreeBSD system.
   Users will then be able to log on to your FTP server with a
   username of ftp or anonymous and with any password (by convention
   an email address for the user should be used as the password). The
   FTP server will call chroot(2) when an anonymous user logs in, to
   restrict access to only the home directory of the ftp user.

   There are two text files that specify welcome messages to be
   displayed to FTP clients. The contents of the file /etc/ftpwelcome
   will be displayed to users before they reach the login prompt.
   After a successful login, the contents of the file /etc/ftpmotd
   will be displayed. Note that the path to this file is relative to
   the login environment, so the file ~ftp/etc/ftpmotd would be
   displayed for anonymous users.

   Once the FTP server has been configured properly, it must be
   enabled in /etc/inetd.conf. All that is required here is to remove
   the comment symbol !S:#!" from in front of the existing ftpd line
   :

 ftp     stream  tcp     nowait  root    /usr/libexec/ftpd       ftpd -l

   As explained in  1/2d"O 27-1, a HangUP Signal must be sent to
   inetd after this configuration file is changed.

   You can now log on to your FTP server by typing:

 % ftp localhost

     --------------------------------------------------------------

  27.9.3. Maintaining

   The ftpd daemon uses syslog(3) to log messages. By default, the
   system log daemon will put messages related to FTP in the
   /var/log/xferlog file. The location of the FTP log can be modified
   by changing the following line in /etc/syslog.conf:

 ftp.info      /var/log/xferlog

   Be aware of the potential problems involved with running an
   anonymous FTP server. In particular, you should think twice about
   allowing anonymous users to upload files. You may find that your
   FTP site becomes a forum for the trade of unlicensed commercial
   software or worse. If you do need to allow anonymous FTP uploads,
   then you should set up the permissions so that these files can not
   be read by other anonymous users until they have been reviewed.

     --------------------------------------------------------------

27.10. File and Print Services for Microsoft Windows clients (Samba)

   Contributed by Murray Stokely.

     --------------------------------------------------------------

  27.10.1. Overview

   Samba is a popular open source software package that provides file
   and print services for Microsoft Windows clients. Such clients can
   connect to and use FreeBSD filespace as if it was a local disk
   drive, or FreeBSD printers as if they were local printers.

   Samba software packages should be included on your FreeBSD
   installation media. If you did not install Samba when you first
   installed FreeBSD, then you can install it from the net/samba3
   port or package.

     --------------------------------------------------------------

  27.10.2. Configuration

   A default Samba configuration file is installed as
   /usr/local/etc/smb.conf.default. This file must be copied to
   /usr/local/etc/smb.conf and customized before Samba can be used.

   The smb.conf file contains runtime configuration information for
   Samba, such as definitions of the printers and !S:file system
   shares!" that you would like to share with Windows clients. The
   Samba package includes a web based tool called swat which provides
   a simple way of configuring the smb.conf file.

     --------------------------------------------------------------

    27.10.2.1. Using the Samba Web Administration Tool (SWAT)

   The Samba Web Administration Tool (SWAT) runs as a daemon from
   inetd. Therefore, the following line in /etc/inetd.conf should be
   uncommented before swat can be used to configure Samba:

 swat   stream  tcp     nowait/400      root    /usr/local/sbin/swat

   As explained in  1/2d"O 27-1, a HangUP Signal must be sent to
   inetd after this configuration file is changed.

   Once swat has been enabled in inetd.conf, you can use a browser to
   connect to http://localhost:901. You will first have to log on
   with the system root account.

   Once you have successfully logged on to the main Samba
   configuration page, you can browse the system documentation, or
   begin by clicking on the Globals tab. The Globals section
   corresponds to the variables that are set in the [global] section
   of /usr/local/etc/smb.conf.

     --------------------------------------------------------------

    27.10.2.2. Global Settings

   Whether you are using swat or editing /usr/local/etc/smb.conf
   directly, the first directives you are likely to encounter when
   configuring Samba are:

   workgroup

           NT Domain-Name or Workgroup-Name for the computers that
           will be accessing this server.

   netbios name

           This sets the NetBIOS name by which a Samba server is
           known. By default it is the same as the first component of
           the host's DNS name.

   server string

           This sets the string that will be displayed with the net
           view command and some other networking tools that seek to
           display descriptive text about the server.

     --------------------------------------------------------------

    27.10.2.3. Security Settings

   Two of the most important settings in /usr/local/etc/smb.conf are
   the security model chosen, and the backend password format for
   client users. The following directives control these options:

   security

           The two most common options here are security = share and
           security = user. If your clients use usernames that are
           the same as their usernames on your FreeBSD machine then
           you will want to use user level security. This is the
           default security policy and it requires clients to first
           log on before they can access shared resources.

           In share level security, client do not need to log onto
           the server with a valid username and password before
           attempting to connect to a shared resource. This was the
           default security model for older versions of Samba.

   passdb backend

           Samba has several different backend authentication models.
           You can authenticate clients with LDAP, NIS+, a SQL
           database, or a modified password file. The default
           authentication method is smbpasswd, and that is all that
           will be covered here.

   Assuming that the default smbpasswd backend is used, the
   /usr/local/private/smbpasswd file must be created to allow Samba
   to authenticate clients. If you would like to give all of your
   UNIX user accounts access from Windows clients, use the following
   command:

 # grep -v "^#" /etc/passwd | make_smbpasswd > /usr/local/private/smbpasswd
 # chmod 600 /usr/local/private/smbpasswd

   Please see the Samba documentation for additional information
   about configuration options. With the basics outlined here, you
   should have everything you need to start running Samba.

     --------------------------------------------------------------

  27.10.3. Starting Samba

   To enable Samba when your system boots, add the following line to
   /etc/rc.conf:

 samba_enable="YES"

   You can then start Samba at any time by typing:

 # /usr/local/etc/rc.d/samba.sh start
 Starting SAMBA: removing stale tdbs :
 Starting nmbd.
 Starting smbd.

   Samba actually consists of three separate daemons. You should see
   that both the nmbd and smbd daemons are started by the samba.sh
   script. If you enabled winbind name resolution services in
   smb.conf, then you will also see that the winbindd daemon is
   started.

   You can stop Samba at any time by typing :

 # /usr/local/etc/rc.d/samba.sh stop

   Samba is a complex software suite with functionality that allows
   broad integration with Microsoft Windows networks. For more
   information about functionality beyond the basic installation
   described here, please see http://www.samba.org.

     --------------------------------------------------------------

27.11. Clock Synchronization with NTP

   Contributed by Tom Hukins.

     --------------------------------------------------------------

  27.11.1. Overview

   Over time, a computer's clock is prone to drift. The Network Time
   Protocol (NTP) is one way to ensure your clock stays accurate.

   Many Internet services rely on, or greatly benefit from,
   computers' clocks being accurate. For example, a web server may
   receive requests to send a file if it has been modified since a
   certain time. In a local area network environment, it is essential
   that computers sharing files from the same file server have
   synchronized clocks so that file timestamps stay consistent.
   Services such as cron(8) also rely on an accurate system clock to
   run commands at the specified times.

   FreeBSD ships with the ntpd(8) NTP server which can be used to
   query other NTP servers to set the clock on your machine or
   provide time services to others.

     --------------------------------------------------------------

  27.11.2. Choosing Appropriate NTP Servers

   In order to synchronize your clock, you will need to find one or
   more NTP servers to use. Your network administrator or ISP may
   have set up an NTP server for this purpose!X!Xcheck their
   documentation to see if this is the case. There is an online list
   of publicly accessible NTP servers which you can use to find an
   NTP server near to you. Make sure you are aware of the policy for
   any servers you choose, and ask for permission if required.

   Choosing several unconnected NTP servers is a good idea in case
   one of the servers you are using becomes unreachable or its clock
   is unreliable. ntpd(8) uses the responses it receives from other
   servers intelligently!X!Xit will favor unreliable servers less
   than reliable ones.

     --------------------------------------------------------------

  27.11.3. Configuring Your Machine

     --------------------------------------------------------------

    27.11.3.1. Basic Configuration

   If you only wish to synchronize your clock when the machine boots
   up, you can use ntpdate(8). This may be appropriate for some
   desktop machines which are frequently rebooted and only require
   infrequent synchronization, but most machines should run ntpd(8).

   Using ntpdate(8) at boot time is also a good idea for machines
   that run ntpd(8). The ntpd(8) program changes the clock gradually,
   whereas ntpdate(8) sets the clock, no matter how great the
   difference between a machine's current clock setting and the
   correct time.

   To enable ntpdate(8) at boot time, add ntpdate_enable="YES" to
   /etc/rc.conf. You will also need to specify all servers you wish
   to synchronize with and any flags to be passed to ntpdate(8) in
   ntpdate_flags.

     --------------------------------------------------------------

    27.11.3.2. General Configuration

   NTP is configured by the /etc/ntp.conf file in the format
   described in ntp.conf(5). Here is a simple example:

 server ntplocal.example.com prefer
 server timeserver.example.org
 server ntp2a.example.net

 driftfile /var/db/ntp.drift

   The server option specifies which servers are to be used, with one
   server listed on each line. If a server is specified with the
   prefer argument, as with ntplocal.example.com, that server is
   preferred over other servers. A response from a preferred server
   will be discarded if it differs significantly from other servers'
   responses, otherwise it will be used without any consideration to
   other responses. The prefer argument is normally used for NTP
   servers that are known to be highly accurate, such as those with
   special time monitoring hardware.

   The driftfile option specifies which file is used to store the
   system clock's frequency offset. The ntpd(8) program uses this to
   automatically compensate for the clock's natural drift, allowing
   it to maintain a reasonably correct setting even if it is cut off
   from all external time sources for a period of time.

   The driftfile option specifies which file is used to store
   information about previous responses from the NTP servers you are
   using. This file contains internal information for NTP. It should
   not be modified by any other process.

     --------------------------------------------------------------

    27.11.3.3. Controlling Access to Your Server

   By default, your NTP server will be accessible to all hosts on the
   Internet. The restrict option in /etc/ntp.conf allows you to
   control which machines can access your server.

   If you want to deny all machines from accessing your NTP server,
   add the following line to /etc/ntp.conf:

 restrict default ignore

   If you only want to allow machines within your own network to
   synchronize their clocks with your server, but ensure they are not
   allowed to configure the server or used as peers to synchronize
   against, add

 restrict 192.168.1.0 mask 255.255.255.0 nomodify notrap

   instead, where 192.168.1.0 is an IP address on your network and
   255.255.255.0 is your network's netmask.

   /etc/ntp.conf can contain multiple restrict options. For more
   details, see the Access Control Support subsection of ntp.conf(5).

     --------------------------------------------------------------

  27.11.4. Running the NTP Server

   To ensure the NTP server is started at boot time, add the line
   ntpd_enable="YES" to /etc/rc.conf. If you wish to pass additional
   flags to ntpd(8), edit the ntpd_flags parameter in /etc/rc.conf.

   To start the server without rebooting your machine, run ntpd being
   sure to specify any additional parameters from ntpd_flags in
   /etc/rc.conf. For example:

 # ntpd -p /var/run/ntpd.pid

     -a`: Under FreeBSD 4.X, you have to replace every instance of
     ntpd with xntpd in the options above.

     --------------------------------------------------------------

  27.11.5. Using ntpd with a Temporary Internet Connection

   The ntpd(8) program does not need a permanent connection to the
   Internet to function properly. However, if you have a temporary
   connection that is configured to dial out on demand, it is a good
   idea to prevent NTP traffic from triggering a dial out or keeping
   the connection alive. If you are using user PPP, you can use
   filter directives in /etc/ppp/ppp.conf. For example:

  set filter dial 0 deny udp src eq 123
  # Prevent NTP traffic from initiating dial out
  set filter dial 1 permit 0 0
  set filter alive 0 deny udp src eq 123
  # Prevent incoming NTP traffic from keeping the connection open
  set filter alive 1 deny udp dst eq 123
  # Prevent outgoing NTP traffic from keeping the connection open
  set filter alive 2 permit 0/0 0/0

   For more details see the PACKET FILTERING section in ppp(8) and
   the examples in /usr/share/examples/ppp/.

     -a`: Some Internet access providers block low-numbered ports,
     preventing NTP from functioning since replies never reach your
     machine.

     --------------------------------------------------------------

  27.11.6. Further Information

   Documentation for the NTP server can be found in
   /usr/share/doc/ntp/ in HTML format.

     --------------------------------------------------------------

                         ^3^1 28. " 3/4CURoAd-

   Contributed by Joseph J. Barbish. Converted to SGML and updated by
   Brad Davis.

     --------------------------------------------------------------

28.1. .S:z

   " 3/4CURoAd--`aDEG-:^1LAoS:A-a-o"t^2ICURCURP:iYENX-a-oNOTyP:q!C "
   3/4CURoAd-CUR]-`aAC,YENN^3],mCUR@(c)I|h^2O!u^3W<<h(rules)!v
   "OAENOTdS:A-a-o-oo,o^3su^2CURCURP:iYENX-a-o-oo,o<<EYEN](network
   packets)!A "AYENB-`aCUR^1^3\(c)I-ay 3/4 *"a:^3q^1L!C ^3o"C,"
   3/4CURoAd--a-o^3W<<hYENiYENHAENOTd<<EYEN]CURCUR-a-o-S 1/4x!A
   ^3o"C,-S
   1/4x^2[>>\!A|yCUR-L-(c)oNOTY"C,^3qDEGT"o(c)wAth<<NOT!BYEND
   3/4-:|`iS:}-a-o"O. 1/2(c)IYENO/-a-o!A
   YENHCURI^3s+-uDEGd-(port)-a-o"O. 1/2CURIYENO/-a-o!C

   " 3/4CURoAd--`aDEG-:CURj'T|a 1/4W+-jYEND
   3/4-:(c)INOTO-oo,o-a-o|wYENth(c)E!C
   YEN|CUR]-`aDEG-:YENI"ODEGo|aeCURU|C"AEP:u!G

     * <<OAA@(c)I^1jA-:S:ACUR-o^3!-oo,o-a-oA^3YENIu{|!!B-aADEGEYENHCURI
       3/4-: 3/4^1!A S:K(c)o^3Q"O|U Internet
       CURCURS:ACUR-L-.Qn-a-oP:C,?e(c)O 1/4vAAT

     * "i(c)I,TCURiCUR-o^3!-oo,o^1i Internet -a-o|s"u-aADEGE

     * CURa:'(c)!u-oo,o|`iS:}A`a'<<!v(network address translation ,
       NAT)!AYEN|YENiYENHCUR^1^3\S:A-a-oCUR-o^3!-oo,o"IYENI private
       IP |`iS:}"AYENiYENH|@|PCURA"ECUR@O^3aeCUR@^3s
       1/2u"`i-oo>>U-oo,oCURW
       (YENi|P(R)EYENI^3aeCUR@IP|`iS:}(c)INOTOCUR@^2OCUR 1/2|@-ooS:})

   AA-aS:^1^3o^3^1CURS:<<a!AS:A+-N.|-a 3/4^1D!G

     * |p|o 3/4A.i|aqYENX<<EYEN]^1LAo-a-o^3W<<h!C

     * FreeBSD CURCURCUR-o<<O/-a-o" 3/4CURoAd-CURS:P:!-a-o(R)t^2S:!C

     * |p|o"IYENICURI^3](c)w OpenBSD -a-o PF " 3/4CURoAd-!C

     * |p|o"IYENICURI^3](c)w IPFILTER!C

     * |p|o"IYENICURI^3](c)w IPFW!C

   |b 3/4\AA-a^3o^3^1CURS:<<e!AS:AYEN^2P:.!G

     * CURF,NDEGoYEN>>-a-o FreeBSD (c)M Internet AE[(c)A

     --------------------------------------------------------------

28.2. ^2L 1/2I" 3/4CURoAd-.S:(c)A

   DEGoYEN>>CURW"
   3/4CURoAd-^3W<<hYENiCURANOTDEG"a-oO/<<NOT-oA!ACURAS:ONOTDEG!G!uexclusive!vYENHCURI
   !uinclusive!v!C
   !uexclusive!vAth|u:!uP:A|W^3ae!v!AYEN|YENyCUR^1^3\(c)O|^3<<EYEN]^3q^1L!A
   uM<<a^1HCURI^3W<<h-a-o<<EYEN]<<h,TCURi^3q^1L" 3/4CURoAd-!C
   NOTUCURI-a-o!A!uinclusive!vAth|u:!uYENO|W^3ae!v!AYEN|YENy 3/4
   *|i(c)O|^3<<EYEN]^3q^1L!A
   uM<<aYENuCUR^1^3\|^3^2AA|X^3W<<h-a-oCUR~YENi^3q^1L" 3/4CURoAd-!C

   3/4aAAe"O>>!!A!uinclusive!v|!" 3/4CURoAd-.|CURn!uexclusive!v|!"
   3/4CURoAd-|wYENth"C,!C
   |]NOTDEG!uinclusive!v(c)uAAaDEGS:CCURFCUR-L-YEN^2n-a-o.AI!C

   |^1YEN~!A"IYENI!ustateful firewall!vYENiAAy|wYENth(c)ES:oA:Y+-K!C
   YEN|.|<<uA:oDEGO?y^3q^1L" 3/4CURoAd-P:}(c)n-a-o^3s 1/2u!A
   "AYENBYENuCUR^1^3\^2AA|X^2{|s(c)IP:}+-O.s-a-o^3s
   1/2uCUR~-`a^3q^1L" 3/4CURoAd-!C -aNOT-oA"
   3/4CURoAd--a-o-EAINOTO|p-aG|b<<D+-`S:O:-a-o^3t<<
   *CURUP:}+-O^3\|h.s^3s 1/2u!A
   'NYENi-`a.|"u:"`i-ayu'|!-aADEGES:d-A>>(DoS, Denial of Service)!C
   |bCURj|h 1/4AE-a-o" 3/4CURoAd-CURe(R)
   *CURCUR!ACUR]YENiYENHYENaeCURe^1BYENI!ustateful
   !vCURI!unon-stateful!v " 3/4CURoAd--a-o^2O|X!AAAy,O-oo-,-a-o"
   3/4CURoAd-^1F"`i^3I"ICURAE!C

     --------------------------------------------------------------

28.3. " 3/4CURoAd-NOTUAo:^3nAAe

   |b FreeBSD DEGoYEN>>"t^2ICURCURCUR-o<<O/|^3CURT-oO/CUR-L-|P-a-o"
   3/4CURoAd-^3nAAe(R)MYENo!C YEN|ICURAS:ONOTO IPFILTER (CUR]'NNOTO
   IPF)!B IPFIREWALL (CUR]'NNOTO IPFW)!A YENHCURI OpenBSD -a-o
   PacketFilter (S:Y|^3|W-a-o PF)!C FreeBSD
   CUR]|^3"aOCUR-o<<O/-a-oNOTyP:q+-+--oTH(R)MYENo(DEGoYEN>>CURWNOTO+-+-"iAW
   1/4e-a-o"IYENI)!G altq(4) YENHCURI dummynet(4)!C
   ^3q+-`S:UI^2ss-oDS:a Dummynet >>P IPFW CUR@"O:^1BYENI!A |O ALTQ
   <<hNOTO.fDEGt IPF/PF CUR@|P"IYENI!C Ao:uM IPF!BIPFW YENHCURI PF
   NOTO"IYENICUR-L-|P-a-o^1eDEGuCURe|!CURI^3W<<h>>y-ak!A
   |yNOTOYEN|I^3-L-"IYENI^3W<<h"O+-+-"iNOTOS:_CUR^1^3\,e(R)AE<<EYEN]P:iYENXS:A-a-o"t^2I!C

   FreeBSD NOTDEG|o.|CUR-o<<O/^3\|hCUR-L-|P-a-o"
   3/4CURoAd-^3nAAe(R)MYENo!A^3oNOTO|]NOTDEGCUR-L-|PCURH.||^3CUR-L-|P-a-o>>Y"D
   !BDEG 3/4|n!A<<U:Ao/>>!thCUR@O"
   3/4CURoAd-^3nAAe(R)MYENoNOTO^3I|n-a-o!C

   |OuS:-aIDEG 3/4|n IPFILTER -a-o`i|]!ANOTO|]NOTDEG^1BYENI|b NAT
   Ao^1O-a-o(R)EO!AYEN|-a-o-aNOT-oA^3W<<hNOTONOTU^1iA^2^3ae^3\|h-a-o!C
   |OYENBYEN|CUR-o<<O/-a-o FTP
   YENN^2z!ACUR]A^2CURAECURF|p|o^3](c)w|wYENth-a-o^1iYEN~ FTP
   -aADEGE^3W<<h!C

   YEN?YENN(c)o(c)O|^3-a-o"
   3/4CURoAd-^3-L-NOTOYENH!uAENOTd!B+-+-"i(c)O?i(c)wCURS:<<EYEN]!v-a-o^1eS:@!A(c)OYENH!A
   "i(c)w" 3/4CURoAd-^3W<<h-a-oCURH'NS:oYEN^2P:.CURF,N TCP/IP
   |p|o^1BS:@!A YENHCURI|p|o+-+-"i<<EYEN]|bYEN?+-` session
   -a-o|U-oO/S:@YENI!C S:o,O-oE-a-o>>!(c)u!A 1/2D-DEGN 3/4\!G
   http://www.ipprimer.com/overview.cfm!C

     --------------------------------------------------------------

28.4. OpenBSD <<EYEN]^1LAo 3/4^1 (Packet Filter, PF)CURI ALTQ

   |b 2003 |~ 6 CUReYEN-:!AOpenBSD -a-o" 3/4CURoAd-^3nAAe PF ^3Q^2
   3/4'O"`i FreeBSD CURCUR!A"AYENB|NOT?y(c)o Ports Collection CUR-o!C
   |O 2004 |~ 11 CUReYEN-:(c)Ouo|ae-a-o FreeBSD 5.3
   -a(c)CUR]NOTO^2A:CUR@|,+-N PF 
   3/4a|XNOTDEGDEGoA|"t^2I-a-oCUR@^3!CURA!C
   PFNOTOOS:^1^3AE!BYENthYEN\-`a-a-o" 3/4CURoAd-!A "AYENB"a|^3?i
   3/4U:(c)E ALTQ(YENae?u|i|C!AAlternate Queuing) -a-oYEN\-`a!C
   ALTQ'-L-"NCURF!uQoS!v (Quality of Service)AW 1/4e-oTH"iYEN\-`a!A
   YEN|YENiYENHYENI^1LAo^3W<<h-a-oCURe|!"O<<O>>U|U-oO/CUR-L-|P-aADEGE-a-oAW
   1/4e!C YENtYEN~!AOpenBSD p^1-oCURCURCURw,g^1i PF
   -a-o"IYENI<<u:<<n'-L-"NCURF,O-oE-a-o,N>>!!A
   |]|^1|b^3oYEN>>CURaYENUCURCURS:UICUR-L-.|S:@<<
   1/2AE-a-oAO/z!A|OYENuCURP:^2D-.S:n!C

   S:o|hAo:(c)o PF
   -a-o,eDEGTYENi(c)oCURU|C-ooS:}NOTd,ss!Ghttp://pf4freebsd.love2party.net/.

     --------------------------------------------------------------

  28.4.1. +-OYENI PF

   PF |b FreeBSD 5.3 CURS:<<a-a-o"t^2ICURCUR!A'NYENiYENH>>'AP"IYENI
   kernel DEGE-oA 1/4O^2O"O,u:CURJ!C |b rc.conf CURCURYEN[CURJ
   pf_enable="YES" <<a!A "t^2I'N.|,u:CURJ PF -a-o kernel DEGE-oA
   1/4O^2O!C^3o 1/4O^2O.||b<<O/YENss(R)ECUR]+-OYENI pflog(4)
   DEGO?yYEN\-`a!C

     -a`: ^3oO 1/4O^2O.|DEG^2^3] kernel CUR-oCURw|^3 options INET
     (c)M device bpf!C DEG-L-<<D 1/2sA:P: kernel (R)ECURw|b^1^3NOTO
     make.conf(5) ^3](c)wAECURCURYEN[CURJ NOINET6( FreeBSD 6.0
     YENH<<a-a-o-a(c)YEN>><<hNOTO NO_INET6) ^3o 1/4ECUR~.|A
     *S:KCUR-L-YEN'P:} IPv6 CURa:'(c)!A S:_<<h pf 
     1/4O^2O|P(R)ECUR]>>Yn options INET6!ACUR]'NNOTO IPv6 CURa:'(c)!C

   CUR@YEN^1,u:CURJ PF -a-o kernel  1/4O^2O(c)INOTOAR-oA 1/2sA:P:CURJ
   kernel CUR-o!A 'NYENiYENH"IYENI pfctl "O+-ODEGE(c)IAo:^3NOT pf!C

   CURU+-^3oO"OCURlYENU: 1/2d|p|o+-ODEGE pf!G

 # pfctl -e

   pfctl NOTO"IYENI pf " 3/4CURoAd--a-o<<u:YENO!C
   YnCURF,NS:o,O-oE-a-o pfctl ^1BYENI!A 1/2D-NOTd 3/4\ pfctl(8) 
   1/2uCURWCURaYENU!C

     --------------------------------------------------------------

  28.4.2. kernel ?iP:u

   |b 1/2sA:P: FreeBSD kernel
   (R)E!A"ACUR-L-YEN^2S:^1YENthYEN[CURJCURU|C-a-o?iP:u"O+-OYENI PF!C
   |b^3o,IYENuNOTOn|CYENXu^1S:ADEGN|O-a-oCUR@"C,,eDEGT|OCURw!C +-N PF
    1/2sA:P:CURJ kernel CURCUR!A.| 3/4EPuL-ak"IYENI kernel
   -a-oDEGE-oA,u:CURJ 1/4O^2O!C

   ^3](c)w PF -a-o kernel ?iP:u 1/2d"O|b kernel `i(c)l 1/2XCURCUR-a-o
   /usr/src/sys/conf/NOTES!AA`aP:KCUR-o(R)e|pCURU!G

 device pf
 device pflog
 device pfsync

   device pf NOTOYENI"O+-ODEGE!upacket filter(<<EYEN]^1LAo)!v -a-o"
   3/4CURoAd-CURa:'(c)!C

   |O device pflog!A|^1YEN\-`an,ECUR-L-,ENOTOYENi!AYEN|.|+-ODEGE
   pflog(4)!AYENH bpf(4) (R)ae|!"ODEGO?y-oo,oNOTyP:q!C pflogd(8)
   daemon <<hNOTOYENI"ONOTo:?y^3o"C,DEGT(R)S:!A"A|s|buw-oD-CURW!C

   device pfsync!A|^1YEN\-`an,ECUR-L-,ENOTOYENi!AYEN|.|+-ODEGE
   pfsync(4)!AYENiYENHYENI"O-oE+-+-!u-aNOT-oA-a-oS:iAAU:!v!C 
   1/2D--a`.N!G device pfsync"ACUR-L-NOTO kernel DEGE-oA
   1/4O^2O!An"IYENI-a-o,U:!A YEN^2P:.n 1/2sCURJ|Uq-a-o kernel
   CURCURCUR~|ae!C

   ^3o"C,^3](c)w+-N.||bS:A 1/2sA:P:CURI|w,E|n.s kernel
   <<aCUR~.|YENI(R)A:!C

     --------------------------------------------------------------

  28.4.3. rc.conf "a:YENLNOTUAo:-a-o?iP:u

   S:A>>Yn|b /etc/rc.conf
   CURCURYEN[CURJCURU|C-a-o^3](c)w!AYENH<<K|b"t^2I+-ODEGE(R)E+-OYENI
   PF!G

 pf_enable="YES"                 # +-OYENI PF (|p-aG>>Yn-a-o,U:,u:CURJ 1/4O^2O)
 pf_rules="/etc/pf.conf"         # PF " 3/4CURoAd-^3W<<h^3](c)wAE
 pf_flags=""                     # pfctl +-ODEGE(R)E-a-o-athYEN[?iP:u
 pflog_enable="YES"              # +-ODEGE pflogd(8)
 pflog_logfile="/var/log/pflog"  # pflogd Ax|sDEGO?yAE(R) *-a-o|aCURe
 pflog_flags=""                  # pflogd +-ODEGE(R)E-athYEN[-a-o?iP:u

   |p-aG+-z-a-o" 3/4CURoAd-<<a+-|^3O
   LAN(DEGIDEG`i-oo,o)!A"An^3z^1LYEN|"OA`aDEGe<<EYEN]!A
   'NYEN^2P:.n^3](c)wCURU|C?iP:u!G

 gateway_enable="YES"            # +-OYENI LAN Gateway

     --------------------------------------------------------------

  28.4.4. +-OYENI ALTQ

   ALTQ YENu|^3|b 1/2sCURJ FreeBSD kernel CURCURCUR~-`aYENI(R)A:!C
   CUR-L-NOTO(c)O|^3-a-o-oo,oYENdAAXDEGEu{|!^3-L-CURa:'(c) ALTQ!C 
   1/2D-NOTY altq(4)  1/2uCURWCURaYENU"OCURF,NS:A"IYENI-a-o FreeBSD
   -a(c)YEN>>CURCURCURa:'(c)AAXDEGEu{|!-a-o^2M^3ae!C
   CURU+-(c)O|C-a-o+-N.|+-OYENI ALTQ CURI"a:YENL-athYEN[YEN\-`a!G

 options         ALTQ
 options         ALTQ_CBQ        # Class Bases Queuing (CBQ)
 options         ALTQ_RED        # Random Early Detection (RED)
 options         ALTQ_RIO        # RED In/Out
 options         ALTQ_HFSC       # Hierarchical Packet Scheduler (HFSC)
 options         ALTQ_PRIQ       # Priority Queuing (PRIQ)
 options         ALTQ_NOPCC      # Required for SMP build

   options ALTQ NOTO+-OYENI ALTQ YENDNOT[-oc!C

   options ALTQ_CBQ .|+-OYENI!uCBQ!v (Class Based Queuing)CURa:'(c)!C
   CBQ CUR^1^3\S:A divide a connection's bandwidth into different
   classes or queues to prioritize traffic based on filter rules.

   options ALTQ_RED enables Random Early Detection (RED). RED is used
   to avoid network congestion. RED does this by measuring the length
   of the queue and comparing it to the minimum and maximum
   thresholds for the queue. If the queue is over the maximum all new
   packets will be dropped. True to its name, RED drops packets from
   different connections randomly.

   options ALTQ_RIO enables Random Early Detection In and Out.

   options ALTQ_HFSC enables the Hierarchical Fair Service Curve
   Packet Scheduler. For more information about HFSC see:
   http://www-2.cs.cmu.edu/~hzhang/HFSC/main.html.

   options ALTQ_PRIQ enables Priority Queuing (PRIQ). PRIQ will
   always pass traffic that is in a higher queue first.

   options ALTQ_NOPCC enables SMP support for ALTQ. This option is
   required on SMP systems.

     --------------------------------------------------------------

  28.4.5. Creating Filtering Rules

   The Packet Filter reads its configuration rules from the
   pf.conf(5) file and it modifies, drops or passes packets according
   to the rules or definitions specified there. The FreeBSD
   installation comes with a default /etc/pf.conf which contains
   useful examples and explanations.

   Although FreeBSD has its own /etc/pf.conf the syntax is the same
   as one used in OpenBSD. A great resource for configuring the pf
   firewall has been written by OpenBSD team and is available at
   http://www.openbsd.org/faq/pf/.

     A:uS:iWhen browsing the pf user's guide, please keep in mind
     that different versions of FreeBSD contain different versions of
     pf. The pf firewall in FreeBSD 5.X is at the level of OpenBSD
     version 3.5 and in FreeBSD 6.X is at the level of OpenBSD
     version 3.7.

   The FreeBSD packet filter P:l>> 1/4 1/2 * 3/4A is a good place to
   ask questions about configuring and running the pf firewall. Do
   not forget to check the mailing list archives before asking
   questions.

     --------------------------------------------------------------

28.5. IPFILTER (IPF) " 3/4CURoAd-

     -a`:
     |^1CUR@,`-a-oCUR-o(R)eCUR'|b^3DEGA:o,EYENR!BS:o.s!A(c)OYENHYEN>>,`CUR-o(R)eYENi-`a"AYEN
     1/4S:^1YENth^2AA|X^2{-ap!C

   IPFILTER -a-oS:@-aINOTDEG Darren Reed!CIPFILTER
   "A<<D+-o,jNOTY-S(c)wS:@.~"t^2ICUR~|ae!G YEN|NOTOO,o OS YENYENx-a-o
   open source A^3YENIu{|!!AYENBCURw^3Q^2 3/4'O"`i
   FreeBSD!BNetBSD!BOpenBSD!BSunOS!BHP/UX YENHCURI Solaris
   ^3o"C,S:@.~"t^2ICURW!C|^1YEN~!AIPFILTER
   -a-oCURa:'(c)!B-ouAA@CUR]NOTU.i?n.YEN!ACUR]|^3(c)w'AA:AYENX-a-oS:o.s-a(c)!C

   IPFILTER is based on a kernel-side firewall and NAT mechanism that
   can be controlled and monitored by userland interface programs.
   The firewall rules can be set or deleted with the ipf(8) utility.
   The NAT rules can be set or deleted with the ipnat(1) utility. The
   ipfstat(8) utility can print run-time statistics for the kernel
   parts of IPFILTER. The ipmon(8) program can log IPFILTER actions
   to the system log files.

   IPF was originally written using a rule processing logic of !uthe
   last matching rule wins!v and used only stateless type of rules.
   Over time IPF has been enhanced to include a !uquick!v option and
   a stateful !ukeep state!v option which drastically modernized the
   rules processing logic. IPF's official documentation covers the
   legacy rule coding parameters and the legacy rule file processing
   logic. The modernized functions are only included as additional
   options, completely understating their benefits in producing a far
   superior secure firewall.

   The instructions contained in this section are based on using
   rules that contain the !uquick!v option and the stateful !ukeep
   state!v option. This is the basic framework for coding an
   inclusive firewall rule set.

   An inclusive firewall only allows packets matching the rules to
   pass through. This way you can control what services can originate
   behind the firewall destined for the public Internet and also
   control the services which can originate from the public Internet
   accessing your private network. Everything else is blocked and
   logged by default design. Inclusive firewalls are much, much more
   secure than exclusive firewall rule sets and is the only rule set
   type covered herein.

   For detailed explanation of the legacy rules processing method
   see: http://www.obfuscation.org/ipf/ipf-howto.html#TOC_1 and
   http://coombs.anu.edu.au/~avalon/ip-filter.html.

   IPF -a-o FAQ |`i(c)o http://www.phildev.net/ipf/index.html.

     --------------------------------------------------------------

  28.5.1. +-OYENI IPF

   IPF is included in the basic FreeBSD install as a separate run
   time loadable module. The system will dynamically load the IPF
   kernel loadable module when the rc.conf statement
   ipfilter_enable="YES" is used. The loadable module was created
   with logging enabled and the default pass all options. You do not
   need to compile IPF into the FreeBSD kernel just to change the
   default to block all, you can do that by just coding a block all
   rule at the end of your rule set.

     --------------------------------------------------------------

  28.5.2. kernel ?iP:u

   |b 1/2sA:P: FreeBSD kernel
   (R)E!A"ACUR-L-YEN^2S:^1YENthYEN[CURJCURU|C-a-o?iP:u"O+-OYENI IPF!C
   |b^3o,IYENuNOTOn|CYENXu^1S:ADEGN|O-a-oCUR@"C,,eDEGT|OCURw!C +-N
   IPF  1/2sA:P:CURJ kernel CURCUR!A.| 3/4EPuL-ak"IYENI kernel
   -a-oDEGE-oA,u:CURJ 1/4O^2O!C

   Sample kernel config IPF option statements are in the
   /usr/src/sys/conf/NOTES kernel source (/usr/src/sys/arch/conf/LINT
   for FreeBSD 4.X) and are reproduced here:

 options IPFILTER
 options IPFILTER_LOG
 options IPFILTER_DEFAULT_BLOCK

   options IPFILTER enables support for the !uIPFILTER!v firewall.

   options IPFILTER_LOG enables the option to have IPF log traffic by
   writing to the ipl packet logging pseudo!X!Xdevice for every rule
   that has the log keyword.

   options IPFILTER_DEFAULT_BLOCK changes the default behavior so any
   packet not matching a firewall pass rule gets blocked.

   These settings will take effect only after you have built and
   installed a kernel with them set.

     --------------------------------------------------------------

  28.5.3. YENiYENI-a-o rc.conf ?iP:u

   P:.|b /etc/rc.conf CUR-oYEN[CURJCURU|CCUR-o(R)e!AYENH<<K|bP:}
   3/4-:(R)E'N.|+-OYENI IPF!G

 ipfilter_enable="YES"             # Start ipf firewall
 ipfilter_rules="/etc/ipf.rules"   # IPF " 3/4CURoAd-^3W<<h^3](c)wAE
 ipmon_enable="YES"                # +-OYENI IP -oE+-+-DEGO?y
 ipmon_flags="-Ds"                 # D = "IYENI-aADEGEu{S:C, (daemon) +-ODEGE
                                   # s = "IYENI syslog DEGO?y
                                   # v = DEGO?y(c)o tcp window, ack, seq
                                   # n = +-N IP CURI port ^1iA^3|U:|W-oUCURCUR

   If you have a LAN behind this firewall that uses the reserved
   private IP address ranges, then you need to add the following to
   enable NAT functionality:

 gateway_enable="YES"              # +-OYENI LAN Gateway
 ipnat_enable="YES"                # Start ipnat function
 ipnat_rules="/etc/ipnat.rules"    # rules definition file for ipnat

     --------------------------------------------------------------

  28.5.4. IPF

   The ipf command is used to load your rules file. Normally you
   create a file containing your custom rules and use this command to
   replace in mass the currently running firewall internal rules:

 # ipf -Fa -f /etc/ipf.rules

   -Fa means flush all internal rules tables.

   -f means this is the file to read for the rules to load.

   This gives you the ability to make changes to your custom rules
   file, run the above IPF command, and thus update the running
   firewall with a fresh copy of all the rules without having to
   reboot the system. This method is very convenient for testing new
   rules as the procedure can be executed as many times as needed.

   See the ipf(8) manual page for details on the other flags
   available with this command.

   The ipf(8) command expects the rules file to be a standard text
   file. It will not accept a rules file written as a script with
   symbolic substitution.

   There is a way to build IPF rules that utilizes the power of
   script symbolic substitution. For more information, see uU 28.5.9
   ,`.

     --------------------------------------------------------------

  28.5.5. IPFSTAT

   The default behavior of ipfstat(8) is to retrieve and display the
   totals of the accumulated statistics gathered as a result of
   applying the user coded rules against packets going in and out of
   the firewall since it was last started, or since the last time the
   accumulators were reset to zero by the ipf -Z command.

   See the ipfstat(8) manual page for details.

   The default ipfstat(8) command output will look something like
   this:

 input packets: blocked 99286 passed 1255609 nomatch 14686 counted 0
  output packets: blocked 4200 passed 1284345 nomatch 14687 counted 0
  input packets logged: blocked 99286 passed 0
  output packets logged: blocked 0 passed 0
  packets logged: input 0 output 0
  log failures: input 3898 output 0
  fragment state(in): kept 0 lost 0
  fragment state(out): kept 0 lost 0
  packet state(in): kept 169364 lost 0
  packet state(out): kept 431395 lost 0
  ICMP replies: 0 TCP RSTs sent: 0
  Result cache hits(in): 1215208 (out): 1098963
  IN Pullups succeeded: 2 failed: 0
  OUT Pullups succeeded: 0 failed: 0
  Fastroute successes: 0 failures: 0
  TCP cksum fails(in): 0 (out): 0
  Packet log flags set: (0)

   When supplied with either -i for inbound or -o for outbound, it
   will retrieve and display the appropriate list of filter rules
   currently installed and in use by the kernel.

   ipfstat -in displays the inbound internal rules table with rule
   number.

   ipfstat -on displays the outbound internal rules table with the
   rule number.

   The output will look something like this:

 @1 pass out on xl0 from any to any
 @2 block out on dc0 from any to any
 @3 pass out quick on dc0 proto tcp/udp from any to any keep state

   ipfstat -ih displays the inbound internal rules table, prefixing
   each rule with a count of how many times the rule was matched.

   ipfstat -oh displays the outbound internal rules table, prefixing
   each rule with a count of how many times the rule was matched.

   The output will look something like this:

 2451423 pass out on xl0 from any to any
 354727 block out on dc0 from any to any
 430918 pass out quick on dc0 proto tcp/udp from any to any keep state

   One of the most important functions of the ipfstat command is the
   -t flag which displays the state table in a way similar to the way
   top(1) shows the FreeBSD running process table. When your firewall
   is under attack this function gives you the ability to identify,
   drill down to, and see the attacking packets. The optional
   sub-flags give the ability to select the destination or source IP,
   port, or protocol that you want to monitor in real time. See the
   ipfstat(8) manual page for details.

     --------------------------------------------------------------

  28.5.6. IPMON

   In order for ipmon to work properly, the kernel option
   IPFILTER_LOG must be turned on. This command has two different
   modes that it can be used in. Native mode is the default mode when
   you type the command on the command line without the -D flag.

   Daemon mode is for when you want to have a continuous system log
   file available so that you can review logging of past events. This
   is how FreeBSD and IPFILTER are configured to work together.
   FreeBSD has a built in facility to automatically rotate system
   logs. That is why outputting the log information to syslogd is
   better than the default of outputting to a regular file. In the
   default rc.conf file you see the ipmon_flags statement uses the
   -Ds flags:

 ipmon_flags="-Ds" # D = start as daemon
                   # s = log to syslog
                   # v = log tcp window, ack, seq
                   # n = map IP & port to names

   The benefits of logging are obvious. It provides the ability to
   review, after the fact, information such as which packets had been
   dropped, what addresses they came from and where they were going.
   These all give you a significant edge in tracking down attackers.

   Even with the logging facility enabled, IPF will not generate any
   rule logging on its own. The firewall administrator decides what
   rules in the rule set he wants to log and adds the log keyword to
   those rules. Normally only deny rules are logged.

   It is very customary to include a default deny everything rule
   with the log keyword included as your last rule in the rule set.
   This way you get to see all the packets that did not match any of
   the rules in the rule set.

     --------------------------------------------------------------

  28.5.7. IPMON Logging

   Syslogd uses its own special method for segregation of log data.
   It uses special groupings called !ufacility!v and !S:level!".
   IPMON in -Ds mode uses security (local0 in 4.X) as the
   !ufacility!v name. All IPMON logged data goes to security (local0
   in 4.X). The following levels can be used to further segregate the
   logged data if desired:

 LOG_INFO - packets logged using the "log" keyword as the action rather than pass or block.
 LOG_NOTICE - packets logged which are also passed
 LOG_WARNING - packets logged which are also blocked
 LOG_ERR - packets which have been logged and which can be considered short

   To setup IPFILTER to log all data to /var/log/ipfilter.log, you
   will need to create the file. The following command will do that:

 # touch /var/log/ipfilter.log

   The syslog function is controlled by definition statements in the
   /etc/syslog.conf file. The syslog.conf file offers considerable
   flexibility in how syslog will deal with system messages issued by
   software applications like IPF.

   Add the following statement to /etc/syslog.conf for FreeBSD 5.X
   and later:

 security.* /var/log/ipfilter.log

   Or add the following statement to /etc/syslog.conf for
   FreeBSD 4.X:

 local0.* /var/log/ipfilter.log

   The security.* (local0 for 4.X) means to write all the logged
   messages to the coded file location.

   To activate the changes to /etc/syslog.conf you can reboot or bump
   the syslog task into re-reading /etc/syslog.conf by running
   /etc/rc.d/syslogd reload (killall -HUP syslogd in FreeBSD 4.X).

   Do not forget to change /etc/newsyslog.conf to rotate the new log
   you just created above.

     --------------------------------------------------------------

  28.5.8. The Format of Logged Messages

   Messages generated by ipmon consist of data fields separated by
   white space. Fields common to all messages are:

    1. The date of packet receipt.

    2. The time of packet receipt. This is in the form HH:MM:SS.F,
       for hours, minutes, seconds, and fractions of a second (which
       can be several digits long).

    3. The name of the interface the packet was processed on, e.g.
       dc0.

    4. The group and rule number of the rule, e.g. @0:17.

   These can be viewed with ipfstat -in.

    1. The action: p for passed, b for blocked, S for a short packet,
       n did not match any rules, L for a log rule. The order of
       precedence in showing flags is: S, p, b, n, L. A capital P or
       B means that the packet has been logged due to a global
       logging setting, not a particular rule.

    2. The addresses. This is actually three fields: the source
       address and port (separated by a comma), the -> symbol, and
       the destination address and port. 209.53.17.22,80 ->
       198.73.220.17,1722.

    3. PR followed by the protocol name or number, e.g. PR tcp.

    4. len followed by the header length and total length of the
       packet, e.g. len 20 40.

   If the packet is a TCP packet, there will be an additional field
   starting with a hyphen followed by letters corresponding to any
   flags that were set. See the ipmon(8) manual page for a list of
   letters and their flags.

   If the packet is an ICMP packet, there will be two fields at the
   end, the first always being !uICMP!v, and the next being the ICMP
   message and sub-message type, separated by a slash, e.g. ICMP 3/3
   for a port unreachable message.

     --------------------------------------------------------------

  28.5.9. Building the Rule Script with Symbolic Substitution

   Some experienced IPF users create a file containing the rules and
   code them in a manner compatible with running them as a script
   with symbolic substitution. The major benefit of doing this is
   that you only have to change the value associated with the
   symbolic name and when the script is run all the rules containing
   the symbolic name will have the value substituted in the rules.
   Being a script, you can use symbolic substitution to code
   frequently used values and substitute them in multiple rules. You
   will see this in the following example.

   The script syntax used here is compatible with the sh, csh, and
   tcsh shells.

   Symbolic substitution fields are prefixed with a dollar sign: $.

   Symbolic fields do not have the $ prefix.

   The value to populate the symbolic field must be enclosed with
   double quotes (").

   Start your rule file with something like this:

 ############# IPF ^3W<<h(c)RYENO 1/2Z-a-oP:}(c)l  ########################

 oif="dc0"            # ^1iYEN~-oo,o,E,m-a-o|W-oU
 odns="192.0.2.11"    # ISP -a-o DNS |o/-aA 3/4^1 IP |`iS:}
 myip="192.0.2.7"     # +-qS:U-a-o ISP '-L-"N-a-oAR-oA IP
 ks="keep state"
 fks="flags S keep state"

 # You can choose between building /etc/ipf.rules file
 # from this script or running this script "as is".
 #
 # Uncomment only one line and comment out another.
 #
 # 1) This can be used for building /etc/ipf.rules:
 #cat > /etc/ipf.rules << EOF
 #
 # 2) This can be used to run script "as is":
 /sbin/ipf -Fa -f - << EOF

 # Allow out access to my ISP's Domain name server.
 pass out quick on $oif proto tcp from any to $odns port = 53 $fks
 pass out quick on $oif proto udp from any to $odns port = 53 $ks

 # Allow out non-secure standard www function
 pass out quick on $oif proto tcp from $myip to any port = 80 $fks

 # Allow out secure www function https over TLS SSL
 pass out quick on $oif proto tcp from $myip to any port = 443 $fks
 EOF
 ################## End of IPF rules script ########################

   That is all there is to it. The rules are not important in this
   example; how the symbolic substitution fields are populated and
   used are. If the above example was in a file named
   /etc/ipf.rules.script, you could reload these rules by entering
   the following command:

 # sh /etc/ipf.rules.script

   There is one problem with using a rules file with embedded
   symbolics: IPF does not understand symbolic substitution, and
   cannot read such scripts directly.

   This script can be used in one of two ways:

     * Uncomment the line that begins with cat, and comment out the
       line that begins with /sbin/ipf. Place ipfilter_enable="YES"
       into /etc/rc.conf as usual, and run script once after each
       modification to create or update /etc/ipf.rules.

     * Disable IPFILTER in system startup scripts by adding
       ipfilter_enable="NO" (this is default value) into /etc/rc.conf
       file.

       Add a script like the following to your /usr/local/etc/rc.d/
       startup directory. The script should have an obvious name like
       ipf.loadrules.sh. The .sh extension is mandatory.

 #!/bin/sh
 sh /etc/ipf.rules.script

       The permissions on this script file must be read, write,
       execute for owner root.

 # chmod 700 /usr/local/etc/rc.d/ipf.loadrules.sh

   +-q^2{|bDEG_!A.i"t^2IP:} 3/4-:(R)E'N.|,u:CURJS:A(c)O^3]-a-o IPF
   ^3W<<h!C

     --------------------------------------------------------------

  28.5.10. IPF ^3W<<h

   A rule set is a group of ipf rules coded to pass or block packets
   based on the values contained in the packet. The bi-directional
   exchange of packets between hosts comprises a session
   conversation. The firewall rule set processes the packet two
   times, once on its arrival from the public Internet host and again
   as it leaves for its return trip back to the public Internet host.
   Each TCP/IP service (i.e. telnet, www, mail, etc.) is predefined
   by its protocol, source and destination IP address, or the source
   and destination port number. This is the basic selection criteria
   used to create rules which will pass or block services.

   IPF was originally written using a rules processing logic of !uthe
   last matching rule wins!v and used only stateless rules. Over time
   IPF has been enhanced to include a !uquick!v option and a stateful
   !ukeep state!v option which drastically modernized the rule
   processing logic.

   The instructions contained in this section are based on using
   rules that contain the !uquick!v option and the stateful !ukeep
   state!v option. This is the basic framework for coding an
   inclusive firewall rule set.

   An inclusive firewall only allows services matching the rules
   through. This way you can control what services can originate
   behind the firewall destined for the public Internet and also
   control the services which can originate from the public Internet
   accessing your private network. Everything else is blocked and
   logged by default design. Inclusive firewalls are much, much
   securer than exclusive firewall rule sets and is the only rule set
   type covered herein.

     A:uS:iWhen working with the firewall rules, be very careful.
     Some configurations will lock you out of the server. To be on
     the safe side, you may wish to consider performing the initial
     firewall configuration from the local console rather than doing
     it remotely e.g. via ssh.

     --------------------------------------------------------------

  28.5.11. Rule Syntax

   The rule syntax presented here has been simplified to only address
   the modern stateful rule context and !ufirst matching rule wins!v
   logic. For the complete legacy rule syntax description see the
   ipf(8) manual page.

   A # character is used to mark the start of a comment and may
   appear at the end of a rule line or on its own line. Blank lines
   are ignored.

   Rules contain keywords. These keywords have to be coded in a
   specific order from left to right on the line. Keywords are
   identified in bold type. Some keywords have sub-options which may
   be keywords themselves and also include more sub-options. Each of
   the headings in the below syntax has a bold section header which
   expands on the content.

   ACTION IN-OUT OPTIONS SELECTION STATEFUL PROTO SRC_ADDR,DST_ADDR
   OBJECT PORT_NUM TCP_FLAG STATEFUL

   ACTION = block | pass

   IN-OUT = in | out

   OPTIONS = log | quick | on interface-name

   SELECTION = proto value | source/destination IP | port = number |
   flags flag-value

   PROTO = tcp/udp | udp | tcp | icmp

   SRC_ADD,DST_ADDR = all | from object to object

   OBJECT = IP address | any

   PORT_NUM = port number

   TCP_FLAG = S

   STATEFUL = keep state

     --------------------------------------------------------------

    28.5.11.1. ACTION

   The action indicates what to do with the packet if it matches the
   rest of the filter rule. Each rule must have a action. The
   following actions are recognized:

   block indicates that the packet should be dropped if the selection
   parameters match the packet.

   pass indicates that the packet should exit the firewall if the
   selection parameters match the packet.

     --------------------------------------------------------------

    28.5.11.2. IN-OUT

   A mandatory requirement is that each filter rule explicitly state
   which side of the I/O it is to be used on. The next keyword must
   be either in or out and one or the other has to be coded or the
   rule will not pass syntax checks.

   in means this rule is being applied against an inbound packet
   which has just been received on the interface facing the public
   Internet.

   out means this rule is being applied against an outbound packet
   destined for the interface facing the public Internet.

     --------------------------------------------------------------

    28.5.11.3. OPTIONS

     -a`: These options must be used in the order shown here.

   log indicates that the packet header will be written to the ipl
   log (as described in the LOGGING section below) if the selection
   parameters match the packet.

   quick indicates that if the selection parameters match the packet,
   this rule will be the last rule checked, allowing a
   !ushort-circuit!v path to avoid processing any following rules for
   this packet. This option is a mandatory requirement for the
   modernized rules processing logic.

   on indicates the interface name to be incorporated into the
   selection parameters. Interface names are as displayed by
   ifconfig(8). Using this option, the rule will only match if the
   packet is going through that interface in the specified direction
   (in/out). This option is a mandatory requirement for the
   modernized rules processing logic.

   When a packet is logged, the headers of the packet are written to
   the IPL packet logging pseudo-device. Immediately following the
   log keyword, the following qualifiers may be used (in this order):

   body indicates that the first 128 bytes of the packet contents
   will be logged after the headers.

   first If the log keyword is being used in conjunction with a
   !ukeep state!v option, it is recommended that this option is also
   applied so that only the triggering packet is logged and not every
   packet which thereafter matches the !ukeep state!v information.

     --------------------------------------------------------------

    28.5.11.4. SELECTION

   The keywords described in this section are used to describe
   attributes of the packet to be interrogated when determining
   whether rules match or not. There is a keyword subject, and it has
   sub-option keywords, one of which has to be selected. The
   following general-purpose attributes are provided for matching,
   and must be used in this order:

     --------------------------------------------------------------

    28.5.11.5. PROTO

   proto is the subject keyword and must be coded along with one of
   its corresponding keyword sub-option values. The value allows a
   specific protocol to be matched against. This option is a
   mandatory requirement for the modernized rules processing logic.

   tcp/udp | udp | tcp | icmp or any protocol names found in
   /etc/protocols are recognized and may be used. The special
   protocol keyword tcp/udp may be used to match either a TCP or a
   UDP packet, and has been added as a convenience to save
   duplication of otherwise identical rules.

     --------------------------------------------------------------

    28.5.11.6. SRC_ADDR/DST_ADDR

   The all keyword is essentially a synonym for !ufrom any to any!v
   with no other match parameters.

   from src to dst: the from and to keywords are used to match
   against IP addresses. Rules must specify BOTH source and
   destination parameters. any is a special keyword that matches any
   IP address. Examples of use: !ufrom any to any!v or !ufrom
   0.0.0.0/0 to any!v or !S:from any to 0.0.0.0/0!v or !ufrom 0.0.0.0
   to any!" or !ufrom any to 0.0.0.0!v.

   IP addresses may be specified as a dotted IP address numeric
   form/mask-length, or as single dotted IP address numeric form.

   There is no way to match ranges of IP addresses which do not
   express themselves easily as mask-length. See this web page for
   help on writing mask-length: http://jodies.de/ipcalc.

     --------------------------------------------------------------

    28.5.11.7. PORT

   If a port match is included, for either or both of source and
   destination, then it is only applied to TCP and UDP packets. When
   composing port comparisons, either the service name from
   /etc/services or an integer port number may be used. When the port
   appears as part of the from object, it matches the source port
   number; when it appears as part of the to object, it matches the
   destination port number. The use of the port option with the to
   object is a mandatory requirement for the modernized rules
   processing logic. Example of use: !ufrom any to any port = 80!v

   Port comparisons may be done in a number of forms, with a number
   of comparison operators, or port ranges may be specified.

   port "=" | "!=" | "<" | ">" | "<=" | ">=" | "eq" | "ne" | "lt" |
   "gt" | "le" | "ge".

   To specify port ranges, port "<>" | "><"

     A:uS:iFollowing the source and destination matching parameters,
     the following two parameters are mandatory requirements for the
     modernized rules processing logic.

     --------------------------------------------------------------

    28.5.11.8. TCP_FLAG

   Flags are only effective for TCP filtering. The letters represents
   one of the possible flags that can be interrogated in the TCP
   packet header.

   The modernized rules processing logic uses the flags S parameter
   to identify the tcp session start request.

     --------------------------------------------------------------

    28.5.11.9. STATEFUL

   keep state indicates that on a pass rule, any packets that match
   the rules selection parameters should activate the stateful
   filtering facility.

     -a`: This option is a mandatory requirement for the modernized
     rules processing logic.

     --------------------------------------------------------------

  28.5.12. Stateful Filtering

   Stateful filtering treats traffic as a bi-directional exchange of
   packets comprising a session conversation. When activated,
   keep-state dynamically generates internal rules for each
   anticipated packet being exchanged during the bi-directional
   session conversation. It has the interrogation abilities to
   determine if the session conversation between the originating
   sender and the destination are following the valid procedure of
   bi-directional packet exchange. Any packets that do not properly
   fit the session conversation template are automatically rejected
   as impostors.

   Keep state will also allow ICMP packets related to a TCP or UDP
   session through. So if you get ICMP type 3 code 4 in response to
   some web surfing allowed out by a keep state rule, they will be
   automatically allowed in. Any packet that IPF can be certain is
   part of an active session, even if it is a different protocol,
   will be let in.

   What happens is:

   Packets destined to go out the interface connected to the public
   Internet are first checked against the dynamic state table, if the
   packet matches the next expected packet comprising in a active
   session conversation, then it exits the firewall and the state of
   the session conversation flow is updated in the dynamic state
   table, the remaining packets get checked against the outbound rule
   set.

   Packets coming in to the interface connected to the public
   Internet are first checked against the dynamic state table, if the
   packet matches the next expected packet comprising a active
   session conversation, then it exits the firewall and the state of
   the session conversation flow is updated in the dynamic state
   table, the remaining packets get checked against the inbound rule
   set.

   When the conversation completes it is removed from the dynamic
   state table.

   Stateful filtering allows you to focus on blocking/passing new
   sessions. If the new session is passed, all its subsequent packets
   will be allowed through automatically and any impostors
   automatically rejected. If a new session is blocked, none of its
   subsequent packets will be allowed through. Stateful filtering has
   technically advanced interrogation abilities capable of defending
   against the flood of different attack methods currently employed
   by attackers.

     --------------------------------------------------------------

  28.5.13. Inclusive Rule Set Example

   The following rule set is an example of how to code a very secure
   inclusive type of firewall. An inclusive firewall only allows
   services matching pass rules through and blocks all other by
   default. All firewalls have at the minimum two interfaces which
   have to have rules to allow the firewall to function.

   All UNIX flavored systems including FreeBSD are designed to use
   interface lo0 and IP address 127.0.0.1 for internal communication
   within the operating system. The firewall rules must contain rules
   to allow free unmolested movement of these special internally used
   packets.

   The interface which faces the public Internet is the one where you
   place your rules to authorize and control access out to the public
   Internet and access requests arriving from the public Internet.
   This can be your user PPP tun0 interface or your NIC that is
   connected to your DSL or cable modem.

   In cases where one or more NICs are cabled to private LANs behind
   the firewall, those interfaces must have a rule coded to allow
   free unmolested movement of packets originating from those LAN
   interfaces.

   The rules should be first organized into three major sections: all
   the free unmolested interfaces, the public interface outbound, and
   the public interface inbound.

   The rules in each of the public interface sections should have the
   most frequently matched rules placed before less commonly matched
   rules, with the last rule in the section blocking and logging all
   packets on that interface and direction.

   The Outbound section in the following rule set only contains
   'pass' rules which contain selection values that uniquely identify
   the service that is authorized for public Internet access. All the
   rules have the 'quick', 'on', 'proto', 'port', and 'keep state'
   option coded. The 'proto tcp' rules have the 'flag' option
   included to identify the session start request as the triggering
   packet to activate the stateful facility.

   The Inbound section has all the blocking of undesirable packets
   first, for two different reasons. The first is that these things
   being blocked may be part of an otherwise valid packet which may
   be allowed in by the later authorized service rules. The second
   reason is that by having a rule that explicitly blocks selected
   packets that I receive on an infrequent basis and that I do not
   want to see in the log, they will not be caught by the last rule
   in the section which blocks and logs all packets which have fallen
   through the rules. The last rule in the section which blocks and
   logs all packets is how you create the legal evidence needed to
   prosecute the people who are attacking your system.

   Another thing you should take note of, is there is no response
   returned for any of the undesirable stuff, their packets just get
   dropped and vanish. This way the attacker has no knowledge if his
   packets have reached your system. The less the attackers can learn
   about your system, the more time they must invest before actually
   doing something bad. The inbound 'nmap OS fingerprint' attempts
   rule I log the first occurrence because this is something a
   attacker would do.

   Any time you see log messages on a rule with 'log first'. You
   should do an ipfstat -hio command to see the number of times the
   rule has been matched so you know if you are being flooded, i.e.
   under attack.

   When you log packets with port numbers you do not recognize, look
   it up in /etc/services or go to
   http://www.securitystats.com/tools/portsearch.php and do a port
   number lookup to find what the purpose of that port number is.

   Check out this link for port numbers used by Trojans
   http://www.simovits.com/trojans/trojans.html.

   The following rule set is a complete very secure 'inclusive' type
   of firewall rule set that I have used on my system. You can not go
   wrong using this rule set for your own. Just comment out any pass
   rules for services that you do not want to authorize.

   If you see messages in your log that you want to stop seeing just
   add a block rule in the inbound section.

   You have to change the dc0 interface name in every rule to the
   interface name of the Nic card that connects your system to the
   public Internet. For user PPP it would be tun0.

   Add the following statements to /etc/ipf.rules:

 #################################################################
 # No restrictions on Inside LAN Interface for private network
 # Not needed unless you have LAN
 #################################################################

 #pass out quick on xl0 all
 #pass in quick on xl0 all

 #################################################################
 # No restrictions on Loopback Interface
 #################################################################
 pass in quick on lo0 all
 pass out quick on lo0 all

 #################################################################
 # Interface facing Public Internet (Outbound Section)
 # Interrogate session start requests originating from behind the
 # firewall on the private network
 # or from this gateway server destine for the public Internet.
 #################################################################

 # Allow out access to my ISP's Domain name server.
 # xxx must be the IP address of your ISP's DNS.
 # Dup these lines if your ISP has more than one DNS server
 # Get the IP addresses from /etc/resolv.conf file
 pass out quick on dc0 proto tcp from any to xxx port = 53 flags S keep state
 pass out quick on dc0 proto udp from any to xxx port = 53 keep state

 # Allow out access to my ISP's DHCP server for cable or DSL networks.
 # This rule is not needed for 'user ppp' type connection to the
 # public Internet, so you can delete this whole group.
 # Use the following rule and check log for IP address.
 # Then put IP address in commented out rule & delete first rule
 pass out log quick on dc0 proto udp from any to any port = 67 keep state
 #pass out quick on dc0 proto udp from any to z.z.z.z port = 67 keep state


 # Allow out non-secure standard www function
 pass out quick on dc0 proto tcp from any to any port = 80 flags S keep state

 # Allow out secure www function https over TLS SSL
 pass out quick on dc0 proto tcp from any to any port = 443 flags S keep state

 # Allow out send & get email function
 pass out quick on dc0 proto tcp from any to any port = 110 flags S keep state
 pass out quick on dc0 proto tcp from any to any port = 25 flags S keep state

 # Allow out Time
 pass out quick on dc0 proto tcp from any to any port = 37 flags S keep state

 # Allow out nntp news
 pass out quick on dc0 proto tcp from any to any port = 119 flags S keep state

 # Allow out gateway & LAN users non-secure FTP ( both passive & active modes)
 # This function uses the IPNAT built in FTP proxy function coded in
 # the nat rules file to make this single rule function correctly.
 # If you want to use the pkg_add command to install application packages
 # on your gateway system you need this rule.
 pass out quick on dc0 proto tcp from any to any port = 21 flags S keep state

 # Allow out secure FTP, Telnet, and SCP
 # This function is using SSH (secure shell)
 pass out quick on dc0 proto tcp from any to any port = 22 flags S keep state

 # Allow out non-secure Telnet
 pass out quick on dc0 proto tcp from any to any port = 23 flags S keep state

 # Allow out FBSD CVSUP function
 pass out quick on dc0 proto tcp from any to any port = 5999 flags S keep state

 # Allow out ping to public Internet
 pass out quick on dc0 proto icmp from any to any icmp-type 8 keep state

 # Allow out whois for LAN PC to public Internet
 pass out quick on dc0 proto tcp from any to any port = 43 flags S keep state

 # Block and log only the first occurrence of everything
 # else that's trying to get out.
 # This rule enforces the block all by default logic.
 block out log first quick on dc0 all

 #################################################################
 # Interface facing Public Internet (Inbound Section)
 # Interrogate packets originating from the public Internet
 # destine for this gateway server or the private network.
 #################################################################

 # Block all inbound traffic from non-routable or reserved address spaces
 block in quick on dc0 from 192.168.0.0/16 to any    #RFC 1918 private IP
 block in quick on dc0 from 172.16.0.0/12 to any     #RFC 1918 private IP
 block in quick on dc0 from 10.0.0.0/8 to any        #RFC 1918 private IP
 block in quick on dc0 from 127.0.0.0/8 to any       #loopback
 block in quick on dc0 from 0.0.0.0/8 to any         #loopback
 block in quick on dc0 from 169.254.0.0/16 to any    #DHCP auto-config
 block in quick on dc0 from 192.0.2.0/24 to any      #reserved for docs
 block in quick on dc0 from 204.152.64.0/23 to any   #Sun cluster interconnect
 block in quick on dc0 from 224.0.0.0/3 to any       #Class D & E multicast

 ##### Block a bunch of different nasty things. ############
 # That I do not want to see in the log

 # Block frags
 block in quick on dc0 all with frags

 # Block short tcp packets
 block in quick on dc0 proto tcp all with short

 # block source routed packets
 block in quick on dc0 all with opt lsrr
 block in quick on dc0 all with opt ssrr

 # Block nmap OS fingerprint attempts
 # Log first occurrence of these so I can get their IP address
 block in log first quick on dc0 proto tcp from any to any flags FUP

 # Block anything with special options
 block in quick on dc0 all with ipopts

 # Block public pings
 block in quick on dc0 proto icmp all icmp-type 8

 # Block ident
 block in quick on dc0 proto tcp from any to any port = 113

 # Block all Netbios service. 137=name, 138=datagram, 139=session
 # Netbios is MS/Windows sharing services.
 # Block MS/Windows hosts2 name server requests 81
 block in log first quick on dc0 proto tcp/udp from any to any port = 137
 block in log first quick on dc0 proto tcp/udp from any to any port = 138
 block in log first quick on dc0 proto tcp/udp from any to any port = 139
 block in log first quick on dc0 proto tcp/udp from any to any port = 81

 # Allow traffic in from ISP's DHCP server. This rule must contain
 # the IP address of your ISP's DHCP server as it's the only
 # authorized source to send this packet type. Only necessary for
 # cable or DSL configurations. This rule is not needed for
 # 'user ppp' type connection to the public Internet.
 # This is the same IP address you captured and
 # used in the outbound section.
 pass in quick on dc0 proto udp from z.z.z.z to any port = 68 keep state

 # Allow in standard www function because I have apache server
 pass in quick on dc0 proto tcp from any to any port = 80 flags S keep state

 # Allow in non-secure Telnet session from public Internet
 # labeled non-secure because ID/PW passed over public Internet as clear text.
 # Delete this sample group if you do not have telnet server enabled.
 #pass in quick on dc0 proto tcp from any to any port = 23 flags S keep state

 # Allow in secure FTP, Telnet, and SCP from public Internet
 # This function is using SSH (secure shell)
 pass in quick on dc0 proto tcp from any to any port = 22 flags S keep state

 # Block and log only first occurrence of all remaining traffic
 # coming into the firewall. The logging of only the first
 # occurrence stops a .denial of service. attack targeted
 # at filling up your log file space.
 # This rule enforces the block all by default logic.
 block in log first quick on dc0 all
 ################### End of rules file #####################################

     --------------------------------------------------------------

  28.5.14. NAT

   NAT stands for Network Address Translation. To those familiar with
   Linux, this concept is called IP Masquerading; NAT and IP
   Masquerading are the same thing. One of the many things the IPF
   NAT function enables is the ability to have a private Local Area
   Network (LAN) behind the firewall sharing a single ISP assigned IP
   address on the public Internet.

   You may ask why would someone want to do this. ISPs normally
   assign a dynamic IP address to their non-commercial users. Dynamic
   means that the IP address can be different each time you dial in
   and log on to your ISP, or for cable and DSL modem users when you
   power off and then power on your modems you can get assigned a
   different IP address. This IP address is how you are known to the
   public Internet.

   Now lets say you have five PCs at home and each one needs Internet
   access. You would have to pay your ISP for an individual Internet
   account for each PC and have five phone lines.

   With NAT you only need a single account with your ISP, then cable
   your other four PCs to a switch and the switch to the NIC in your
   FreeBSD system which is going to service your LAN as a gateway.
   NAT will automatically translate the private LAN IP address for
   each separate PC on the LAN to the single public IP address as it
   exits the firewall bound for the public Internet. It also does the
   reverse translation for returning packets.

   NAT is most often accomplished without the approval, or knowledge,
   of your ISP and in most cases is grounds for your ISP terminating
   your account if found out. Commercial users pay a lot more for
   their Internet connection and usually get assigned a block of
   static IP address which never change. The ISP also expects and
   consents to their Commercial customers using NAT for their
   internal private LANs.

   There is a special range of IP addresses reserved for NATed
   private LAN IP address. According to RFC 1918, you can use the
   following IP ranges for private nets which will never be routed
   directly to the public Internet:

   Start IP 10.0.0.0     -                  Ending IP 10.255.255.255  
   Start IP 172.16.0.0   -                  Ending IP 172.31.255.255  
   Start IP 192.168.0.0  -                  Ending IP 192.168.255.255 

     --------------------------------------------------------------

  28.5.15. IPNAT

   NAT rules are loaded by using the ipnat command. Typically the NAT
   rules are stored in /etc/ipnat.rules. See ipnat(1) for details.

   When changing the NAT rules after NAT has been started, make your
   changes to the file containing the NAT rules, then run ipnat
   command with the -CF flags to delete the internal in use NAT rules
   and flush the contents of the translation table of all active
   entries.

   To reload the NAT rules issue a command like this:

 # ipnat -CF -f /etc/ipnat.rules

   To display some statistics about your NAT, use this command:

 # ipnat -s

   To list the NAT table's current mappings, use this command:

 # ipnat -l

   To turn verbose mode on, and display information relating to rule
   processing and active rules/table entries:

 # ipnat -v

     --------------------------------------------------------------

  28.5.16. IPNAT Rules

   NAT rules are very flexible and can accomplish many different
   things to fit the needs of commercial and home users.

   The rule syntax presented here has been simplified to what is most
   commonly used in a non-commercial environment. For a complete rule
   syntax description see the ipnat(5) manual page.

   The syntax for a NAT rule looks something like this:

 map IF LAN_IP_RANGE -> PUBLIC_ADDRESS

   The keyword map starts the rule.

   Replace IF with the external interface.

   The LAN_IP_RANGE is what your internal clients use for IP
   Addressing, usually this is something like 192.168.1.0/24.

   The PUBLIC_ADDRESS can either be the external IP address or the
   special keyword 0/32, which means to use the IP address assigned
   to IF.

     --------------------------------------------------------------

  28.5.17. How NAT works

   A packet arrives at the firewall from the LAN with a public
   destination. It passes through the outbound filter rules, NAT gets
   his turn at the packet and applies its rules top down, first
   matching rule wins. NAT tests each of its rules against the
   packets interface name and source IP address. When a packets
   interface name matches a NAT rule then the [source IP address,
   i.e. private LAN IP address] of the packet is checked to see if it
   falls within the IP address range specified to the left of the
   arrow symbol on the NAT rule. On a match the packet has its source
   IP address rewritten with the public IP address obtained by the
   0/32 keyword. NAT posts a entry in its internal NAT table so when
   the packet returns from the public Internet it can be mapped back
   to its original private IP address and then passed to the filter
   rules for processing.

     --------------------------------------------------------------

  28.5.18. Enabling IPNAT

   To enable IPNAT add these statements to /etc/rc.conf.

   To enable your machine to route traffic between interfaces:

 gateway_enable="YES"

   To start IPNAT automatically each time:

 ipnat_enable="YES"

   To specify where to load the IPNAT rules from:

 ipnat_rules="/etc/ipnat.rules"

     --------------------------------------------------------------

  28.5.19. NAT for a very large LAN

   For networks that have large numbers of PC's on the LAN or
   networks with more than a single LAN, the process of funneling all
   those private IP addresses into a single public IP address becomes
   a resource problem that may cause problems with the same port
   numbers being used many times across many NATed LAN PC's, causing
   collisions. There are two ways to relieve this resource problem.

     --------------------------------------------------------------

    28.5.19.1. Assigning Ports to Use

   A normal NAT rule would look like:

 map dc0 192.168.1.0/24 -> 0/32

   In the above rule the packet's source port is unchanged as the
   packet passes through IPNAT. By adding the portmap keyword you can
   tell IPNAT to only use source ports in a range. For example the
   following rule will tell IPNAT to modify the source port to be
   within that range:

 map dc0 192.168.1.0/24 -> 0/32 portmap tcp/udp 20000:60000

   Additionally we can make things even easier by using the auto
   keyword to tell IPNAT to determine by itself which ports are
   available to use:

 map dc0 192.168.1.0/24 -> 0/32 portmap tcp/udp auto

     --------------------------------------------------------------

    28.5.19.2. Using a pool of public addresses

   In very large LANs there comes a point where there are just too
   many LAN addresses to fit into a single public address. By
   changing the following rule:

 map dc0 192.168.1.0/24 -> 204.134.75.1

   Currently this rule maps all connections through 204.134.75.1.
   This can be changed to specify a range:

 map dc0 192.168.1.0/24 -> 204.134.75.1-10

   Or a subnet using CIDR notation such as:

 map dc0 192.168.1.0/24 -> 204.134.75.0/24

     --------------------------------------------------------------

  28.5.20. Port Redirection

   A very common practice is to have a web server, email server,
   database server and DNS server each segregated to a different PC
   on the LAN. In this case the traffic from these servers still have
   to be NATed, but there has to be some way to direct the inbound
   traffic to the correct LAN PCs. IPNAT has the redirection
   facilities of NAT to solve this problem. Lets say you have your
   web server on LAN address 10.0.10.25 and your single public IP
   address is 20.20.20.5 you would code the rule like this:

 rdr dc0 20.20.20.5/32 port 80 -> 10.0.10.25 port 80

   or:

 rdr dc0 0/32 port 80 -> 10.0.10.25 port 80

   or for a LAN DNS Server on LAN address of 10.0.10.33 that needs to
   receive public DNS requests:

 rdr dc0 20.20.20.5/32 port 53 -> 10.0.10.33 port 53 udp

     --------------------------------------------------------------

  28.5.21. FTP and NAT

   FTP is a dinosaur left over from the time before the Internet as
   it is known today, when research universities were leased lined
   together and FTP was used to share files among research
   Scientists. This was a time when data security was not a
   consideration. Over the years the FTP protocol became buried into
   the backbone of the emerging Internet and its username and
   password being sent in clear text was never changed to address new
   security concerns. FTP has two flavors, it can run in active mode
   or passive mode. The difference is in how the data channel is
   acquired. Passive mode is more secure as the data channel is
   acquired be the ordinal ftp session requester. For a real good
   explanation of FTP and the different modes see
   http://www.slacksite.com/other/ftp.html.

     --------------------------------------------------------------

    28.5.21.1. IPNAT Rules

   IPNAT has a special built in FTP proxy option which can be
   specified on the NAT map rule. It can monitor all outbound packet
   traffic for FTP active or passive start session requests and
   dynamically create temporary filter rules containing only the port
   number really in use for the data channel. This eliminates the
   security risk FTP normally exposes the firewall to from having
   large ranges of high order port numbers open.

   This rule will handle all the traffic for the internal LAN:

 map dc0 10.0.10.0/29 -> 0/32 proxy port 21 ftp/tcp

   This rule handles the FTP traffic from the gateway:

 map dc0 0.0.0.0/0 -> 0/32 proxy port 21 ftp/tcp

   This rule handles all non-FTP traffic from the internal LAN:

 map dc0 10.0.10.0/29 -> 0/32

   The FTP map rule goes before our regular map rule. All packets are
   tested against the first rule from the top. Matches on interface
   name, then private LAN source IP address, and then is it a FTP
   packet. If all that matches then the special FTP proxy creates
   temp filter rules to let the FTP session packets pass in and out,
   in addition to also NATing the FTP packets. All LAN packets that
   are not FTP do not match the first rule and fall through to the
   third rule and are tested, matching on interface and source IP,
   then are NATed.

     --------------------------------------------------------------

    28.5.21.2. IPNAT FTP Filter Rules

   Only one filter rule is needed for FTP if the NAT FTP proxy is
   used.

   Without the FTP Proxy you will need the following three rules:

 # Allow out LAN PC client FTP to public Internet
 # Active and passive modes
 pass out quick on rl0 proto tcp from any to any port = 21 flags S keep state

 # Allow out passive mode data channel high order port numbers
 pass out quick on rl0 proto tcp from any to any port > 1024 flags S keep state

 # Active mode let data channel in from FTP server
 pass in quick on rl0 proto tcp from any to any port = 20 flags S keep state

     --------------------------------------------------------------

    28.5.21.3. FTP NAT Proxy Bug

   As of FreeBSD 4.9 which includes IPFILTER version 3.4.31 the FTP
   proxy works as documented during the FTP session until the session
   is told to close. When the close happens packets returning from
   the remote FTP server are blocked and logged coming in on port 21.
   The NAT FTP/proxy appears to remove its temp rules prematurely,
   before receiving the response from the remote FTP server
   acknowledging the close. A problem report was posted to the IPF
   mailing list.

   The solution is to add a filter rule to get rid of these unwanted
   log messages or do nothing and ignore FTP inbound error messages
   in your log. Most people do not use outbound FTP too often.

 block in quick on rl0 proto tcp from any to any port = 21

     --------------------------------------------------------------

28.6. IPFW

     -a`:
     |^1CUR@,`-a-oCUR-o(R)eCUR'|b^3DEGA:o,EYENR!BS:o.s!A(c)OYENHYEN>>,`CUR-o(R)eYENi-`a"AYEN
     1/4S:^1YENth^2AA|X^2{-ap!C.

   The IPFIREWALL (IPFW) is a FreeBSD sponsored firewall software
   application authored and maintained by FreeBSD volunteer staff
   members. It uses the legacy stateless rules and a legacy rule
   coding technique to achieve what is referred to as Simple Stateful
   logic.

   The IPFW sample rule set (found in /etc/rc.firewall) in the
   standard FreeBSD install is rather simple and it is not expected
   that it used directly without modifications. The example does not
   use stateful filtering, which is beneficial in most setups, so it
   will not be used as base for this section.

   The IPFW stateless rule syntax is empowered with technically
   sophisticated selection capabilities which far surpasses the
   knowledge level of the customary firewall installer. IPFW is
   targeted at the professional user or the advanced technical
   computer hobbyist who have advanced packet selection requirements.
   A high degree of detailed knowledge into how different protocols
   use and create their unique packet header information is necessary
   before the power of the IPFW rules can be unleashed. Providing
   that level of explanation is out of the scope of this section of
   the handbook.

   IPFW is composed of seven components, the primary component is the
   kernel firewall filter rule processor and its integrated packet
   accounting facility, the logging facility, the 'divert' rule which
   triggers the NAT facility, and the advanced special purpose
   facilities, the dummynet traffic shaper facilities, the 'fwd rule'
   forward facility, the bridge facility, and the ipstealth facility.

     --------------------------------------------------------------

  28.6.1. Enabling IPFW

   IPFW is included in the basic FreeBSD install as a separate run
   time loadable module. The system will dynamically load the kernel
   module when the rc.conf statement firewall_enable="YES" is used.
   You do not need to compile IPFW into the FreeBSD kernel unless you
   want NAT function enabled.

   After rebooting your system with firewall_enable="YES" in rc.conf
   the following white highlighted message is displayed on the screen
   as part of the boot process:

 ipfw2 initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled

   The loadable module does have logging ability compiled in. To
   enable logging and set the verbose logging limit, there is a knob
   you can set in /etc/sysctl.conf by adding these statements,
   logging will be enabled on future reboots:

 net.inet.ip.fw.verbose=1
 net.inet.ip.fw.verbose_limit=5

     --------------------------------------------------------------

  28.6.2. Kernel Options

   It is not a mandatory requirement that you enable IPFW by
   compiling the following options into the FreeBSD kernel unless you
   need NAT function. It is presented here as background information.

 options    IPFIREWALL

   This option enables IPFW as part of the kernel

 options    IPFIREWALL_VERBOSE

   Enables logging of packets that pass through IPFW and have the
   'log' keyword specified in the rule set.

 options    IPFIREWALL_VERBOSE_LIMIT=5

   Limits the number of packets logged through syslogd(8) on a per
   entry basis. You may wish to use this option in hostile
   environments which you want to log firewall activity. This will
   close a possible denial of service attack via syslog flooding.

 options    IPFIREWALL_DEFAULT_TO_ACCEPT

   This option will allow everything to pass through the firewall by
   default, which is a good idea when you are first setting up your
   firewall.

 options    IPV6FIREWALL
 options    IPV6FIREWALL_VERBOSE
 options    IPV6FIREWALL_VERBOSE_LIMIT
 options    IPV6FIREWALL_DEFAULT_TO_ACCEPT

   These options are exactly the same as the IPv4 options but they
   are for IPv6. If you do not use IPv6 you might want to use
   IPV6FIREWALL without any rules to block all IPv6

 options    IPDIVERT

   This enables the use of NAT functionality.

     -a`: If you do not include IPFIREWALL_DEFAULT_TO_ACCEPT or set
     your rules to allow incoming packets you will block all packets
     going to and from this machine.

     --------------------------------------------------------------

  28.6.3. /etc/rc.conf Options

   If you do not have IPFW compiled into your kernel you will need to
   load it with the following statement in your /etc/rc.conf:

 firewall_enable="YES"

   Set the script to run to activate your rules:

 firewall_script="/etc/ipfw.rules"

   Enable logging:

 firewall_logging="YES"

     A:uS:iThe only thing that the firewall_logging variable will do
     is setting the net.inet.ip.fw.verbose sysctl variable to the
     value of 1 (see uU 28.6.1 ,`). There is no rc.conf variable to
     set log limitations, but it can be set via sysctl variable,
     manually or from the /etc/sysctl.conf file:

 net.inet.ip.fw.verbose_limit=5

   If your machine is acting as a gateway, i.e. providing Network
   Address Translation (NAT) via natd(8), please refer to uU 29.9 ,`
   for information regarding the required /etc/rc.conf options.

     --------------------------------------------------------------

  28.6.4. The IPFW Command

   The ipfw command is the normal vehicle for making manual single
   rule additions or deletions to the firewall active internal rules
   while it is running. The problem with using this method is once
   your system is shutdown or halted all the rules you added or
   changed or deleted are lost. Writing all your rules in a file and
   using that file to load the rules at boot time, or to replace in
   mass the currently running firewall rules with changes you made to
   the files content is the recommended method used here.

   The ipfw command is still a very useful to display the running
   firewall rules to the console screen. The IPFW accounting facility
   dynamically creates a counter for each rule that counts each
   packet that matches the rule. During the process of testing a
   rule, listing the rule with its counter is the one of the ways of
   determining if the rule is functioning.

   To list all the rules in sequence:

 # ipfw list

   To list all the rules with a time stamp of when the last time the
   rule was matched:

 # ipfw -t list

   To list the accounting information, packet count for matched rules
   along with the rules themselves. The first column is the rule
   number, followed by the number of outgoing matched packets,
   followed by the number of incoming matched packets, and then the
   rule itself.

 # ipfw -a list

   List the dynamic rules in addition to the static rules:

 # ipfw -d list

   Also show the expired dynamic rules:

 # ipfw -d -e list

   Zero the counters:

 # ipfw zero

   Zero the counters for just rule NUM:

 # ipfw zero NUM

     --------------------------------------------------------------

  28.6.5. IPFW Rule Sets

   A rule set is a group of ipfw rules coded to allow or deny packets
   based on the values contained in the packet. The bi-directional
   exchange of packets between hosts comprises a session
   conversation. The firewall rule set processes the packet twice:
   once on its arrival from the public Internet host and again as it
   leaves for its return trip back to the public Internet host. Each
   tcp/ip service (i.e. telnet, www, mail, etc.) is predefined by its
   protocol, and port number. This is the basic selection criteria
   used to create rules which will allow or deny services.

   When a packet enters the firewall it is compared against the first
   rule in the rule set and progress one rule at a time moving from
   top to bottom of the set in ascending rule number sequence order.
   When the packet matches a rule selection parameters, the rules
   action field value is executed and the search of the rule set
   terminates for that packet. This is referred to as !uthe first
   match wins!v search method. If the packet does not match any of
   the rules, it gets caught by the mandatory ipfw default rule,
   number 65535 which denies all packets and discards them without
   any reply back to the originating destination.

     -a`: The search continues after count, skipto and tee rules.

   The instructions contained here are based on using rules that
   contain the stateful 'keep state', 'limit', 'in'/'out', and via
   options. This is the basic framework for coding an inclusive type
   firewall rule set.

   An inclusive firewall only allows services matching the rules
   through. This way you can control what services can originate
   behind the firewall destine for the public Internet and also
   control the services which can originate from the public Internet
   accessing your private network. Everything else is denied by
   default design. Inclusive firewalls are much, much more secure
   than exclusive firewall rule sets and is the only rule set type
   covered here in.

     A:uS:iWhen working with the firewall rules be careful, you can
     end up locking your self out.

     --------------------------------------------------------------

    28.6.5.1. Rule Syntax

   The rule syntax presented here has been simplified to what is
   necessary to create a standard inclusive type firewall rule set.
   For a complete rule syntax description see the ipfw(8) manual
   page.

   Rules contain keywords: these keywords have to be coded in a
   specific order from left to right on the line. Keywords are
   identified in bold type. Some keywords have sub-options which may
   be keywords them selves and also include more sub-options.

   # is used to mark the start of a comment and may appear at the end
   of a rule line or on its own lines. Blank lines are ignored.

   CMD RULE_NUMBER ACTION LOGGING SELECTION STATEFUL

     --------------------------------------------------------------

      28.6.5.1.1. CMD

   Each new rule has to be prefixed with add to add the rule to the
   internal table.

     --------------------------------------------------------------

      28.6.5.1.2. RULE_NUMBER

   Each rule has to have a rule number to go with it.

     --------------------------------------------------------------

      28.6.5.1.3. ACTION

   A rule can be associated with one of the following actions, which
   will be executed when the packet matches the selection criterion
   of the rule.

   allow | accept | pass | permit

   These all mean the same thing which is to allow packets that match
   the rule to exit the firewall rule processing. The search
   terminates at this rule.

   check-state

   Checks the packet against the dynamic rules table. If a match is
   found, execute the action associated with the rule which generated
   this dynamic rule, otherwise move to the next rule. The
   check-state rule does not have selection criterion. If no
   check-state rule is present in the rule set, the dynamic rules
   table is checked at the first keep-state or limit rule.

   deny | drop

   Both words mean the same thing which is to discard packets that
   match this rule. The search terminates.

     --------------------------------------------------------------

      28.6.5.1.4. Logging

   log or logamount

   When a packet matches a rule with the log keyword, a message will
   be logged to syslogd with a facility name of SECURITY. The logging
   only occurs if the number of packets logged so far for that
   particular rule does not exceed the logamount parameter. If no
   logamount is specified, the limit is taken from the sysctl
   variable net.inet.ip.fw.verbose_limit. In both cases, a value of
   zero removes the logging limit. Once the limit is reached, logging
   can be re-enabled by clearing the logging counter or the packet
   counter for that rule, see the ipfw reset log command.

     -a`: Logging is done after all other packet matching conditions
     have been successfully verified, and before performing the final
     action (accept, deny) on the packet. It is up to you to decide
     which rules you want to enable logging on.

     --------------------------------------------------------------

      28.6.5.1.5. Selection

   The keywords described in this section are used to describe
   attributes of the packet to be interrogated when determining
   whether rules match the packet or not. The following
   general-purpose attributes are provided for matching, and must be
   used in this order:

   udp | tcp | icmp

   or any protocol names found in /etc/protocols are recognized and
   may be used. The value specified is protocol to be matched
   against. This is a mandatory requirement.

   from src to dst

   The from and to keywords are used to match against IP addresses.
   Rules must specify BOTH source and destination parameters. any is
   a special keyword that matches any IP address. me is a special
   keyword that matches any IP address configured on an interface in
   your FreeBSD system to represent the PC the firewall is running on
   (i.e. this box) as in 'from me to any' or 'from any to me' or
   'from 0.0.0.0/0 to any' or 'from any to 0.0.0.0/0' or 'from
   0.0.0.0 to any' or 'from any to 0.0.0.0' or 'from me to 0.0.0.0'.
   IP addresses are specified as a dotted IP address numeric
   form/mask-length, or as single dotted IP address numeric form.
   This is a mandatory requirement. See this link for help on writing
   mask-lengths. http://jodies.de/ipcalc

   port number

   For protocols which support port numbers (such as TCP and UDP). It
   is mandatory that you code the port number of the service you want
   to match on. Service names (from /etc/services) may be used
   instead of numeric port values.

   in | out

   Matches incoming or outgoing packets, respectively. The in and out
   are keywords and it is mandatory that you code one or the other as
   part of your rule matching criterion.

   via IF

   Matches packets going through the interface specified by exact
   name. The via keyword causes the interface to always be checked as
   part of the match process.

   setup

   This is a mandatory keyword that identifies the session start
   request for TCP packets.

   keep-state

   This is a mandatory> keyword. Upon a match, the firewall will
   create a dynamic rule, whose default behavior is to match
   bidirectional traffic between source and destination IP/port using
   the same protocol.

   limit {src-addr | src-port | dst-addr | dst-port}

   The firewall will only allow N connections with the same set of
   parameters as specified in the rule. One or more of source and
   destination addresses and ports can be specified. The 'limit' and
   'keep-state' can not be used on same rule. Limit provides the same
   stateful function as 'keep-state' plus its own functions.

     --------------------------------------------------------------

    28.6.5.2. Stateful Rule Option

   Stateful filtering treats traffic as a bi-directional exchange of
   packets comprising a session conversation. It has the
   interrogation abilities to determine if the session conversation
   between the originating sender and the destination are following
   the valid procedure of bi-directional packet exchange. Any packets
   that do not properly fit the session conversation template are
   automatically rejected as impostors.

   'check-state' is used to identify where in the IPFW rules set the
   packet is to be tested against the dynamic rules facility. On a
   match the packet exits the firewall to continue on its way and a
   new rule is dynamic created for the next anticipated packet being
   exchanged during this bi-directional session conversation. On a no
   match the packet advances to the next rule in the rule set for
   testing.

   The dynamic rules facility is vulnerable to resource depletion
   from a SYN-flood attack which would open a huge number of dynamic
   rules. To counter this attack, FreeBSD version 4.5 added another
   new option named limit. This option is used to limit the number of
   simultaneous session conversations by interrogating the rules
   source or destinations fields as directed by the limit option and
   using the packet's IP address found there, in a search of the open
   dynamic rules counting the number of times this rule and IP
   address combination occurred, if this count is greater that the
   value specified on the limit option, the packet is discarded.

     --------------------------------------------------------------

    28.6.5.3. Logging Firewall Messages

   The benefits of logging are obvious: it provides the ability to
   review after the fact the rules you activated logging on which
   provides information like, what packets had been dropped, what
   addresses they came from, where they were going, giving you a
   significant edge in tracking down attackers.

   Even with the logging facility enabled, IPFW will not generate any
   rule logging on it's own. The firewall administrator decides what
   rules in the rule set he wants to log and adds the log verb to
   those rules. Normally only deny rules are logged, like the deny
   rule for incoming ICMP pings. It is very customary to duplicate
   the ipfw default deny everything rule with the log verb included
   as your last rule in the rule set. This way you get to see all the
   packets that did not match any of the rules in the rule set.

   Logging is a two edged sword, if you are not careful, you can lose
   yourself in the over abundance of log data and fill your disk up
   with growing log files. DoS attacks that fill up disk drives is
   one of the oldest attacks around. These log message are not only
   written to syslogd, but also are displayed on the root console
   screen and soon become very annoying.

   The IPFIREWALL_VERBOSE_LIMIT=5 kernel option limits the number of
   consecutive messages sent to the system logger syslogd, concerning
   the packet matching of a given rule. When this option is enabled
   in the kernel, the number of consecutive messages concerning a
   particular rule is capped at the number specified. There is
   nothing to be gained from 200 log messages saying the same
   identical thing. For instance, five consecutive messages
   concerning a particular rule would be logged to syslogd, the
   remainder identical consecutive messages would be counted and
   posted to the syslogd with a phrase like this:

 last message repeated 45 times

   All logged packets messages are written by default to
   /var/log/security file, which is defined in the /etc/syslog.conf
   file.

     --------------------------------------------------------------

    28.6.5.4. Building a Rule Script

   Most experienced IPFW users create a file containing the rules and
   code them in a manner compatible with running them as a script.
   The major benefit of doing this is the firewall rules can be
   refreshed in mass without the need of rebooting the system to
   activate the new rules. This method is very convenient in testing
   new rules as the procedure can be executed as many times as
   needed. Being a script, you can use symbolic substitution to code
   frequent used values and substitution them in multiple rules. You
   will see this in the following example.

   The script syntax used here is compatible with the 'sh', 'csh',
   'tcsh' shells. Symbolic substitution fields are prefixed with a
   dollar sign $. Symbolic fields do not have the $ prefix. The value
   to populate the Symbolic field must be enclosed to "double
   quotes".

   Start your rules file like this:

 ############### start of example ipfw rules script #############
 #
 ipfw -q -f flush       # Delete all rules
 # Set defaults
 oif="tun0"             # out interface
 odns="192.0.2.11"      # ISP's DNS server IP address
 cmd="ipfw -q add "     # build rule prefix
 ks="keep-state"        # just too lazy to key this each time
 $cmd 00500 check-state
 $cmd 00502 deny all from any to any frag
 $cmd 00501 deny tcp from any to any established
 $cmd 00600 allow tcp from any to any 80 out via $oif setup $ks
 $cmd 00610 allow tcp from any to $odns 53 out via $oif setup $ks
 $cmd 00611 allow udp from any to $odns 53 out via $oif $ks
 ################### End of example ipfw rules script ############

   That is all there is to it. The rules are not important in this
   example, how the Symbolic substitution field are populated and
   used are.

   If the above example was in /etc/ipfw.rules file, you could reload
   these rules by entering on the command line.

 # sh /etc/ipfw.rules

   The /etc/ipfw.rules file could be located anywhere you want and
   the file could be named any thing you would like.

   The same thing could also be accomplished by running these
   commands by hand:

 # ipfw -q -f flush
 # ipfw -q add check-state
 # ipfw -q add deny all from any to any frag
 # ipfw -q add deny tcp from any to any established
 # ipfw -q add allow tcp from any to any 80 out via tun0 setup keep-state
 # ipfw -q add allow tcp from any to 192.0.2.11 53 out via tun0 setup keep-state
 # ipfw -q add 00611 allow udp from any to 192.0.2.11 53 out via tun0 keep-state

     --------------------------------------------------------------

    28.6.5.5. Stateful Ruleset

   The following non-NATed rule set is an example of how to code a
   very secure 'inclusive' type of firewall. An inclusive firewall
   only allows services matching pass rules through and blocks all
   other by default. All firewalls have at the minimum two interfaces
   which have to have rules to allow the firewall to function.

   All UNIX flavored operating systems, FreeBSD included, are
   designed to use interface lo0 and IP address 127.0.0.1 for
   internal communication with in the operating system. The firewall
   rules must contain rules to allow free unmolested movement of
   these special internally used packets.

   The interface which faces the public Internet, is the one which
   you code your rules to authorize and control access out to the
   public Internet and access requests arriving from the public
   Internet. This can be your ppp tun0 interface or your NIC that is
   connected to your DSL or cable modem.

   In cases where one or more than one NIC are connected to a private
   LANs behind the firewall, those interfaces must have rules coded
   to allow free unmolested movement of packets originating from
   those LAN interfaces.

   The rules should be first organized into three major sections, all
   the free unmolested interfaces, public interface outbound, and the
   public interface inbound.

   The order of the rules in each of the public interface sections
   should be in order of the most used rules being placed before less
   often used rules with the last rule in the section being a block
   log all packets on that interface and direction.

   The Outbound section in the following rule set only contains
   'allow' rules which contain selection values that uniquely
   identify the service that is authorized for public Internet
   access. All the rules have the, proto, port, in/out, via and keep
   state option coded. The 'proto tcp' rules have the 'setup' option
   included to identify the start session request as the trigger
   packet to be posted to the keep state stateful table.

   The Inbound section has all the blocking of undesirable packets
   first for two different reasons. First is these things being
   blocked may be part of an otherwise valid packet which may be
   allowed in by the later authorized service rules. Second reason is
   that by having a rule that explicitly blocks selected packets that
   I receive on an infrequent bases and do not want to see in the
   log, this keeps them from being caught by the last rule in the
   section which blocks and logs all packets which have fallen
   through the rules. The last rule in the section which blocks and
   logs all packets is how you create the legal evidence needed to
   prosecute the people who are attacking your system.

   Another thing you should take note of, is there is no response
   returned for any of the undesirable stuff, their packets just get
   dropped and vanish. This way the attackers has no knowledge if his
   packets have reached your system. The less the attackers can learn
   about your system the more secure it is. When you log packets with
   port numbers you do not recognize, look the numbers up in
   /etc/services/ or go to
   http://www.securitystats.com/tools/portsearch.php and do a port
   number lookup to find what the purpose of that port number is.
   Check out this link for port numbers used by Trojans:
   http://www.simovits.com/trojans/trojans.html.

     --------------------------------------------------------------

    28.6.5.6. An Example Inclusive Ruleset

   The following non-NATed rule set is a complete inclusive type
   ruleset. You can not go wrong using this rule set for you own.
   Just comment out any pass rules for services you do not want. If
   you see messages in your log that you want to stop seeing just add
   a deny rule in the inbound section. You have to change the 'dc0'
   interface name in every rule to the interface name of the NIC that
   connects your system to the public Internet. For user ppp it would
   be 'tun0'.

   You will see a pattern in the usage of these rules.

     * All statements that are a request to start a session to the
       public Internet use keep-state.

     * All the authorized services that originate from the public
       Internet have the limit option to stop flooding.

     * All rules use in or out to clarify direction.

     * All rules use via interface name to specify the interface the
       packet is traveling over.

   The following rules go into /etc/ipfw.rules.

 ################ Start of IPFW rules file ###############################
 # Flush out the list before we begin.
 ipfw -q -f flush

 # Set rules command prefix
 cmd="ipfw -q add"
 pif="dc0"     # public interface name of NIC
               # facing the public Internet

 #################################################################
 # No restrictions on Inside LAN Interface for private network
 # Not needed unless you have LAN.
 # Change xl0 to your LAN NIC interface name
 #################################################################
 #$cmd 00005 allow all from any to any via xl0

 #################################################################
 # No restrictions on Loopback Interface
 #################################################################
 $cmd 00010 allow all from any to any via lo0

 #################################################################
 # Allow the packet through if it has previous been added to the
 # the "dynamic" rules table by a allow keep-state statement.
 #################################################################
 $cmd 00015 check-state

 #################################################################
 # Interface facing Public Internet (Outbound Section)
 # Interrogate session start requests originating from behind the
 # firewall on the private network or from this gateway server
 # destine for the public Internet.
 #################################################################

 # Allow out access to my ISP's Domain name server.
 # x.x.x.x must be the IP address of your ISP.s DNS
 # Dup these lines if your ISP has more than one DNS server
 # Get the IP addresses from /etc/resolv.conf file
 $cmd 00110 allow tcp from any to x.x.x.x 53 out via $pif setup keep-state
 $cmd 00111 allow udp from any to x.x.x.x 53 out via $pif keep-state

 # Allow out access to my ISP's DHCP server for cable/DSL configurations.
 # This rule is not needed for .user ppp. connection to the public Internet.
 # so you can delete this whole group.
 # Use the following rule and check log for IP address.
 # Then put IP address in commented out rule & delete first rule
 $cmd 00120 allow log udp from any to any 67 out via $pif keep-state
 #$cmd 00120 allow udp from any to x.x.x.x 67 out via $pif keep-state

 # Allow out non-secure standard www function
 $cmd 00200 allow tcp from any to any 80 out via $pif setup keep-state

 # Allow out secure www function https over TLS SSL
 $cmd 00220 allow tcp from any to any 443 out via $pif setup keep-state

 # Allow out send & get email function
 $cmd 00230 allow tcp from any to any 25 out via $pif setup keep-state
 $cmd 00231 allow tcp from any to any 110 out via $pif setup keep-state

 # Allow out FBSD (make install & CVSUP) functions
 # Basically give user root "GOD" privileges.
 $cmd 00240 allow tcp from me to any out via $pif setup keep-state uid root

 # Allow out ping
 $cmd 00250 allow icmp from any to any out via $pif keep-state

 # Allow out Time
 $cmd 00260 allow tcp from any to any 37 out via $pif setup keep-state

 # Allow out nntp news (i.e. news groups)
 $cmd 00270 allow tcp from any to any 119 out via $pif setup keep-state

 # Allow out secure FTP, Telnet, and SCP
 # This function is using SSH (secure shell)
 $cmd 00280 allow tcp from any to any 22 out via $pif setup keep-state

 # Allow out whois
 $cmd 00290 allow tcp from any to any 43 out via $pif setup keep-state

 # deny and log everything else that.s trying to get out.
 # This rule enforces the block all by default logic.
 $cmd 00299 deny log all from any to any out via $pif

 #################################################################
 # Interface facing Public Internet (Inbound Section)
 # Interrogate packets originating from the public Internet
 # destine for this gateway server or the private network.
 #################################################################

 # Deny all inbound traffic from non-routable reserved address spaces
 $cmd 00300 deny all from 192.168.0.0/16 to any in via $pif  #RFC 1918 private IP
 $cmd 00301 deny all from 172.16.0.0/12 to any in via $pif     #RFC 1918 private IP
 $cmd 00302 deny all from 10.0.0.0/8 to any in via $pif          #RFC 1918 private IP
 $cmd 00303 deny all from 127.0.0.0/8 to any in via $pif        #loopback
 $cmd 00304 deny all from 0.0.0.0/8 to any in via $pif            #loopback
 $cmd 00305 deny all from 169.254.0.0/16 to any in via $pif   #DHCP auto-config
 $cmd 00306 deny all from 192.0.2.0/24 to any in via $pif       #reserved for docs
 $cmd 00307 deny all from 204.152.64.0/23 to any in via $pif  #Sun cluster interconnect
 $cmd 00308 deny all from 224.0.0.0/3 to any in via $pif         #Class D & E multicast

 # Deny public pings
 $cmd 00310 deny icmp from any to any in via $pif

 # Deny ident
 $cmd 00315 deny tcp from any to any 113 in via $pif

 # Deny all Netbios service. 137=name, 138=datagram, 139=session
 # Netbios is MS/Windows sharing services.
 # Block MS/Windows hosts2 name server requests 81
 $cmd 00320 deny tcp from any to any 137 in via $pif
 $cmd 00321 deny tcp from any to any 138 in via $pif
 $cmd 00322 deny tcp from any to any 139 in via $pif
 $cmd 00323 deny tcp from any to any 81 in via $pif

 # Deny any late arriving packets
 $cmd 00330 deny all from any to any frag in via $pif

 # Deny ACK packets that did not match the dynamic rule table
 $cmd 00332 deny tcp from any to any established in via $pif

 # Allow traffic in from ISP's DHCP server. This rule must contain
 # the IP address of your ISP.s DHCP server as it.s the only
 # authorized source to send this packet type.
 # Only necessary for cable or DSL configurations.
 # This rule is not needed for .user ppp. type connection to
 # the public Internet. This is the same IP address you captured
 # and used in the outbound section.
 #$cmd 00360 allow udp from any to x.x.x.x 67 in via $pif keep-state

 # Allow in standard www function because I have apache server
 $cmd 00400 allow tcp from any to me 80 in via $pif setup limit src-addr 2

 # Allow in secure FTP, Telnet, and SCP from public Internet
 $cmd 00410 allow tcp from any to me 22 in via $pif setup limit src-addr 2

 # Allow in non-secure Telnet session from public Internet
 # labeled non-secure because ID & PW are passed over public
 # Internet as clear text.
 # Delete this sample group if you do not have telnet server enabled.
 $cmd 00420 allow tcp from any to me 23 in via $pif setup limit src-addr 2

 # Reject & Log all incoming connections from the outside
 $cmd 00499 deny log all from any to any in via $pif

 # Everything else is denied by default
 # deny and log all packets that fell through to see what they are
 $cmd 00999 deny log all from any to any
 ################ End of IPFW rules file ###############################

     --------------------------------------------------------------

    28.6.5.7. An Example NAT and Stateful Ruleset

   There are some additional configuration statements that need to be
   enabled to activate the NAT function of IPFW. The kernel source
   needs 'option divert' statement added to the other IPFIREWALL
   statements compiled into a custom kernel.

   In addition to the normal IPFW options in /etc/rc.conf, the
   following are needed.

 natd_enable="YES"                   # Enable NATD function
 natd_interface="rl0"                # interface name of public Internet NIC
 natd_flags="-dynamic -m"            # -m = preserve port numbers if possible

   Utilizing stateful rules with divert natd rule (Network Address
   Translation) greatly complicates the rule set coding logic. The
   positioning of the check-state, and 'divert natd' rules in the
   rule set becomes very critical. This is no longer a simple
   fall-through logic flow. A new action type is used, called
   'skipto'. To use the skipto command it is mandatory that you
   number each rule so you know exactly where the skipto rule number
   is you are really jumping to.

   The following is an uncommented example of one coding method,
   selected here to explain the sequence of the packet flow through
   the rule sets.

   The processing flow starts with the first rule from the top of the
   rule file and progress one rule at a time deeper into the file
   until the end is reach or the packet being tested to the selection
   criteria matches and the packet is released out of the firewall.
   It is important to take notice of the location of rule numbers 100
   101, 450, 500, and 510. These rules control the translation of the
   outbound and inbound packets so their entries in the keep-state
   dynamic table always register the private LAN IP address. Next
   notice that all the allow and deny rules specified the direction
   the packet is going (IE outbound or inbound) and the interface.
   Also notice that all the start outbound session requests all
   skipto rule 500 for the network address translation.

   Lets say a LAN user uses their web browser to get a web page. Web
   pages use port 80 to communicate over. So the packet enters the
   firewall, It does not match 100 because it is headed out not in.
   It passes rule 101 because this is the first packet so it has not
   been posted to the keep-state dynamic table yet. The packet
   finally comes to rule 125 a matches. It is outbound through the
   NIC facing the public Internet. The packet still has it's source
   IP address as a private LAN IP address. On the match to this rule,
   two actions take place. The keep-state option will post this rule
   into the keep-state dynamic rules table and the specified action
   is executed. The action is part of the info posted to the dynamic
   table. In this case it is "skipto rule 500". Rule 500 NATs the
   packet IP address and out it goes. Remember this, this is very
   important. This packet makes its way to the destination and
   returns and enters the top of the rule set. This time it does
   match rule 100 and has it destination IP address mapped back to
   its corresponding LAN IP address. It then is processed by the
   check-state rule, it's found in the table as an existing session
   conversation and released to the LAN. It goes to the LAN PC that
   sent it and a new packet is sent requesting another segment of the
   data from the remote server. This time it gets checked by the
   check-state rule and its outbound entry is found, the associated
   action, 'skipto 500', is executed. The packet jumps to rule 500
   gets NATed and released on it's way out.

   On the inbound side, everything coming in that is part of an
   existing session conversation is being automatically handled by
   the check-state rule and the properly placed divert natd rules.
   All we have to address is denying all the bad packets and only
   allowing in the authorized services. Lets say there is a apache
   server running on the firewall box and we want people on the
   public Internet to be able to access the local web site. The new
   inbound start request packet matches rule 100 and its IP address
   is mapped to LAN IP for the firewall box. The packet is them
   matched against all the nasty things we want to check for and
   finally matches against rule 425. On a match two things occur. The
   packet rule is posted to the keep-state dynamic table but this
   time any new session requests originating from that source IP
   address is limited to 2. This defends against DoS attacks of
   service running on the specified port number. The action is allow
   so the packet is released to the LAN. On return the check-state
   rule recognizes the packet as belonging to an existing session
   conversation sends it to rule 500 for NATing and released to
   outbound interface.

   Example Ruleset #1:

 #!/bin/sh
 cmd="ipfw -q add"
 skip="skipto 500"
 pif=rl0
 ks="keep-state"
 good_tcpo="22,25,37,43,53,80,443,110,119"

 ipfw -q -f flush

 $cmd 002 allow all from any to any via xl0  # exclude LAN traffic
 $cmd 003 allow all from any to any via lo0  # exclude loopback traffic

 $cmd 100 divert natd ip from any to any in via $pif
 $cmd 101 check-state

 # Authorized outbound packets
 $cmd 120 $skip udp from any to xx.168.240.2 53 out via $pif $ks
 $cmd 121 $skip udp from any to xx.168.240.5 53 out via $pif $ks
 $cmd 125 $skip tcp from any to any $good_tcpo out via $pif setup $ks
 $cmd 130 $skip icmp from any to any out via $pif $ks
 $cmd 135 $skip udp from any to any 123 out via $pif $ks


 # Deny all inbound traffic from non-routable reserved address spaces
 $cmd 300 deny all from 192.168.0.0/16  to any in via $pif  #RFC 1918 private IP
 $cmd 301 deny all from 172.16.0.0/12   to any in via $pif  #RFC 1918 private IP
 $cmd 302 deny all from 10.0.0.0/8      to any in via $pif  #RFC 1918 private IP
 $cmd 303 deny all from 127.0.0.0/8     to any in via $pif  #loopback
 $cmd 304 deny all from 0.0.0.0/8       to any in via $pif  #loopback
 $cmd 305 deny all from 169.254.0.0/16  to any in via $pif  #DHCP auto-config
 $cmd 306 deny all from 192.0.2.0/24    to any in via $pif  #reserved for docs
 $cmd 307 deny all from 204.152.64.0/23 to any in via $pif  #Sun cluster
 $cmd 308 deny all from 224.0.0.0/3     to any in via $pif  #Class D & E multicast

 # Authorized inbound packets
 $cmd 400 allow udp from xx.70.207.54 to any 68 in $ks
 $cmd 420 allow tcp from any to me 80 in via $pif setup limit src-addr 1


 $cmd 450 deny log ip from any to any

 # This is skipto location for outbound stateful rules
 $cmd 500 divert natd ip from any to any out via $pif
 $cmd 510 allow ip from any to any

 ######################## end of rules  ##################

   The following is pretty much the same as above, but uses a self
   documenting coding style full of description comments to help the
   inexperienced IPFW rule writer to better understand what the rules
   are doing.

   Example Ruleset #2:

 #!/bin/sh
 ################ Start of IPFW rules file ###############################
 # Flush out the list before we begin.
 ipfw -q -f flush

 # Set rules command prefix
 cmd="ipfw -q add"
 skip="skipto 800"
 pif="rl0"     # public interface name of NIC
               # facing the public Internet

 #################################################################
 # No restrictions on Inside LAN Interface for private network
 # Change xl0 to your LAN NIC interface name
 #################################################################
 $cmd 005 allow all from any to any via xl0

 #################################################################
 # No restrictions on Loopback Interface
 #################################################################
 $cmd 010 allow all from any to any via lo0

 #################################################################
 # check if packet is inbound and nat address if it is
 #################################################################
 $cmd 014 divert natd ip from any to any in via $pif

 #################################################################
 # Allow the packet through if it has previous been added to the
 # the "dynamic" rules table by a allow keep-state statement.
 #################################################################
 $cmd 015 check-state

 #################################################################
 # Interface facing Public Internet (Outbound Section)
 # Interrogate session start requests originating from behind the
 # firewall on the private network or from this gateway server
 # destine for the public Internet.
 #################################################################

 # Allow out access to my ISP's Domain name server.
 # x.x.x.x must be the IP address of your ISP's DNS
 # Dup these lines if your ISP has more than one DNS server
 # Get the IP addresses from /etc/resolv.conf file
 $cmd 020 $skip tcp from any to x.x.x.x 53 out via $pif setup keep-state


 # Allow out access to my ISP's DHCP server for cable/DSL configurations.
 $cmd 030 $skip udp from any to x.x.x.x 67 out via $pif keep-state

 # Allow out non-secure standard www function
 $cmd 040 $skip tcp from any to any 80 out via $pif setup keep-state

 # Allow out secure www function https over TLS SSL
 $cmd 050 $skip tcp from any to any 443 out via $pif setup keep-state

 # Allow out send & get email function
 $cmd 060 $skip tcp from any to any 25 out via $pif setup keep-state
 $cmd 061 $skip tcp from any to any 110 out via $pif setup keep-state

 # Allow out FreeBSD (make install & CVSUP) functions
 # Basically give user root "GOD" privileges.
 $cmd 070 $skip tcp from me to any out via $pif setup keep-state uid root

 # Allow out ping
 $cmd 080 $skip icmp from any to any out via $pif keep-state

 # Allow out Time
 $cmd 090 $skip tcp from any to any 37 out via $pif setup keep-state

 # Allow out nntp news (i.e. news groups)
 $cmd 100 $skip tcp from any to any 119 out via $pif setup keep-state

 # Allow out secure FTP, Telnet, and SCP
 # This function is using SSH (secure shell)
 $cmd 110 $skip tcp from any to any 22 out via $pif setup keep-state

 # Allow out whois
 $cmd 120 $skip tcp from any to any 43 out via $pif setup keep-state

 # Allow ntp time server
 $cmd 130 $skip udp from any to any 123 out via $pif keep-state

 #################################################################
 # Interface facing Public Internet (Inbound Section)
 # Interrogate packets originating from the public Internet
 # destine for this gateway server or the private network.
 #################################################################

 # Deny all inbound traffic from non-routable reserved address spaces
 $cmd 300 deny all from 192.168.0.0/16  to any in via $pif  #RFC 1918 private IP
 $cmd 301 deny all from 172.16.0.0/12   to any in via $pif  #RFC 1918 private IP
 $cmd 302 deny all from 10.0.0.0/8      to any in via $pif  #RFC 1918 private IP
 $cmd 303 deny all from 127.0.0.0/8     to any in via $pif  #loopback
 $cmd 304 deny all from 0.0.0.0/8       to any in via $pif  #loopback
 $cmd 305 deny all from 169.254.0.0/16  to any in via $pif  #DHCP auto-config
 $cmd 306 deny all from 192.0.2.0/24    to any in via $pif  #reserved for docs
 $cmd 307 deny all from 204.152.64.0/23 to any in via $pif  #Sun cluster
 $cmd 308 deny all from 224.0.0.0/3     to any in via $pif  #Class D & E multicast

 # (c)Uu' ident
 $cmd 315 deny tcp from any to any 113 in via $pif

 # (c)Uu'(c)O|^3-a-o Netbios -aADEGE. 137=name, 138=datagram, 139=session
 # Netbios NOTO MS/Windows -oo,oCURA"E-aADEGE
 # -ay 3/4 *(c)O|^3-a-o MS/Windows YEND 3/4-:|W-oU|o/-aA 3/4^1hosts2 name server requests 81
 $cmd 320 deny tcp from any to any 137 in via $pif
 $cmd 321 deny tcp from any to any 138 in via $pif
 $cmd 322 deny tcp from any to any 139 in via $pif
 $cmd 323 deny tcp from any to any 81  in via $pif

 # (c)Uu'YENo|o-a-o(c)u?d-"`i^1FCURS:<<EYEN]
 $cmd 330 deny all from any to any frag in via $pif

 # Deny ACK packets that did not match the dynamic rule table
 $cmd 332 deny tcp from any to any established in via $pif

 # Allow traffic in from ISP's DHCP server. This rule must contain
 # the IP address of your ISP's DHCP server as it's the only
 # authorized source to send this packet type.
 # Only necessary for cable or DSL configurations.
 # This rule is not needed for 'user ppp' type connection to
 # the public Internet. This is the same IP address you captured
 # and used in the outbound section.
 $cmd 360 allow udp from x.x.x.x to any 68 in via $pif keep-state

 # Allow in standard www function because I have Apache server
 $cmd 370 allow tcp from any to me 80 in via $pif setup limit src-addr 2

 # Allow in secure FTP, Telnet, and SCP from public Internet
 $cmd 380 allow tcp from any to me 22 in via $pif setup limit src-addr 2

 # Allow in non-secure Telnet session from public Internet
 # labeled non-secure because ID & PW are passed over public
 # Internet as clear text.
 # Delete this sample group if you do not have telnet server enabled.
 $cmd 390 allow tcp from any to me 23 in via $pif setup limit src-addr 2

 # Reject & Log all unauthorized incoming connections from the public Internet
 $cmd 400 deny log all from any to any in via $pif

 # Reject & Log all unauthorized out going connections to the public Internet
 $cmd 450 deny log all from any to any out via $pif

 # This is skipto location for outbound stateful rules
 $cmd 800 divert natd ip from any to any out via $pif
 $cmd 801 allow ip from any to any

 # Everything else is denied by default
 # deny and log all packets that fell through to see what they are
 $cmd 999 deny log all from any to any
 ################ End of IPFW rules file ###############################

     --------------------------------------------------------------

                  ^3^1 29. -oo,oP:iP:YEN 1/2mYEN\(c)D-

29.1. .S:z

   YEN>>^3^1+-NCURP:^2D-CUR@"C,P:iP:YEN-a-o-oo,o^3](c)wYENDAD!C

   AA-aS:^1^3o^3^1!A+-z+-NCURF,N!G

     * gateway(^1h^1D)CURI route(,oYENN)-a-o.S:(c)A!C

     * |p|o^3](c)w IEEE 802.11 YENHCURIAAA-aTH(Bluetooth(R))^3]^3AE!C

     * |p|oYENH FreeBSD S:@NOTDEG bridge( 3/4o+-u)!C

     * |p|oNOTDEGuL-oD-"t^2I^3](c)w-oo,oP:} 3/4-:!C

     * |p|o^3](c)w NAT(Network Address Translation)!C

     * |p|o^3z^1L PLIP CURe|!"O^3s+-u"aYENx^1q,-L-!C

     * |p|o|b FreeBSD CUR-o^3](c)w IPv6!C

     * |p|o^3](c)w ATM!C

     * |p|oYENhu 1/2YENI FreeBSD -a-o CARP(Common Access Redundancy
       Protocol)YEN\-`a !C

   |bP:}(c)l 3/4\AA-a^3o^3^1CURS:<<e!A+-z>>Yn!J

     * AA,N /etc/rc NOTUAo: script -a-o.S:(c)A!C

     * 1/4o+-xDEGoYEN>>+-`YENI-a-o-oo,o^3N>>y!C

     * -a 3/4^1D|p|o^3](c)w!B|w,E.s-a-o FreeBSD kernel (uU 8 ^3^1)!C

     * -a 3/4^1D|p|o^3z^1L port/package |w,E^3nAAe (uU 4 ^3^1) !C

     --------------------------------------------------------------

29.2. Gateways and Routes

   Contributed by Coranth Gryphon.

   NOTDEGCURFAAyCUR@^3!^1q,-L--`aS:a:"`iYENtCUR@^3!^1q,-L-!A|]|^1YEN^2>>Yn|^3CUR@-oO/
   3/4-:"i!A AAy^3o^3!^1q,-L--a 3/4^1D,O<<c,>>oDEGu!A^3oO
   3/4-:"i'NNOTO,oYENN?i 3/4U: (routing)!C
   CUR@+-o/,oYENN(!S:route!")NOTOYENNCUR@^1i|`iS:}(c)O(c)w,q-a-o!GCUR@ONOTO
   !S:YENO/-a-o|a(destination)!"YENHCURIYENtCUR@O<<hNOTO^1h^1D
   (!S:gateway!")!C
   ^3o^1i|`iS:}-aiYENU:nDEGe"`iYENO/-a-o|a-a-o<<EYEN]!A
   YEN^2P:.,g^1L^1h^1D!C YENO/-a-o|aCURANOTDEGCURT-oO/Ath<<NOT!GYEND
   3/4-:!BCURl-oo,o(subnet)!B^1w^3],oYENN( !S:default route!"!C
   Y^3-L-"S|^3"a:YEN|-a-o,oYENNYENiYENH"IYENI!A
   ^3o(R)E'N.|"IYENI^1w^3],oYENN!Auy<<aS:UI.|^1i^1w^3],oYENNS:@P:iCUR@"B-a-o>>!(c)u!C
   |^1YEN~!A ^1h^1DCUR]YENiCURANOTDEGCURT-oO/Ath<<NOT!GYEND
   3/4-:!BP:C,?eCURP:+-(interface!ACUR]-oUNOTDEG
   !S:links!")!BCURACURO-oo,ouwAAe|`iS:}(MAC addresses)!C

     --------------------------------------------------------------

  29.2.1.  1/2d"O

   NOTDEGCURFCURe<<K>>!(c)uCUR-L-|PAth<<NOT-a-o,oYENN?i
   3/4U:(routing)!AYENHCURU"IYENI netstat
   <<u:YENO-a-ou^2-aGS:@NOTDEGCURP:^2D- 1/2d"O!G

 % netstat -r
 Routing tables

 Destination      Gateway            Flags     Refs     Use     Netif Expire

 default          outside-gw         UGSc       37      418      ppp0
 localhost        localhost          UH          0      181       lo0
 test0            0:e0:b5:36:cf:4f   UHLW        5    63288       ed0     77
 10.20.30.255     link#1             UHLW        1     2421
 example.com      link#1             UC          0        0
 host1            0:e0:a8:37:8:1e    UHLW        3     4601       lo0
 host2            0:e0:a8:37:8:1e    UHLW        0        5       lo0 =>
 host2.example.com link#1             UC          0        0
 224              link#1             UC          0        0

   The first two lines specify the default route (which we will cover
   in the next section) and the localhost route.

   The interface (Netif column) that this routing table specifies to
   use for localhost is lo0, also known as the loopback device. This
   says to keep all traffic for this destination internal, rather
   than sending it out over the LAN, since it will only end up back
   where it started.

   The next thing that stands out are the addresses beginning with
   0:e0:. These are Ethernet hardware addresses, which are also known
   as MAC addresses. FreeBSD will automatically identify any hosts
   (test0 in the example) on the local Ethernet and add a route for
   that host, directly to it over the Ethernet interface, ed0. There
   is also a timeout (Expire column) associated with this type of
   route, which is used if we fail to hear from the host in a
   specific amount of time. When this happens, the route to this host
   will be automatically deleted. These hosts are identified using a
   mechanism known as RIP (Routing Information Protocol), which
   figures out routes to local hosts based upon a shortest path
   determination.

   FreeBSD will also add subnet routes for the local subnet
   (10.20.30.255 is the broadcast address for the subnet 10.20.30,
   and example.com is the domain name associated with that subnet).
   The designation link#1 refers to the first Ethernet card in the
   machine. You will notice no additional interface is specified for
   those.

   Both of these groups (local network hosts and local subnets) have
   their routes automatically configured by a daemon called routed.
   If this is not run, then only routes which are statically defined
   (i.e. entered explicitly) will exist.

   The host1 line refers to our host, which it knows by Ethernet
   address. Since we are the sending host, FreeBSD knows to use the
   loopback interface (lo0) rather than sending it out over the
   Ethernet interface.

   The two host2 lines are an example of what happens when we use an
   ifconfig(8) alias (see the section on Ethernet for reasons why we
   would do this). The => symbol after the lo0 interface says that
   not only are we using the loopback (since this address also refers
   to the local host), but specifically it is an alias. Such routes
   only show up on the host that supports the alias; all other hosts
   on the local network will simply have a link#1 line for such
   routes.

   The final line (destination subnet 224) deals with multicasting,
   which will be covered in another section.

   Finally, various attributes of each route can be seen in the Flags
   column. Below is a short table of some of these flags and their
   meanings:

   U Up: The route is active.                                         
   H Host: The route destination is a single host.                    
   G Gateway: Send anything for this destination on to this remote    
     system, which will figure out from there where to send it.       
   S Static: This route was configured manually, not automatically    
     generated by the system.                                         
     Clone: Generates a new route based upon this route for machines  
   C we connect to. This type of route is normally used for local     
     networks.                                                        
   W WasCloned: Indicated a route that was auto-configured based upon 
     a local area network (Clone) route.                              
   L Link: Route involves references to Ethernet hardware.            

     --------------------------------------------------------------

  29.2.2. Default Routes

   When the local system needs to make a connection to a remote host,
   it checks the routing table to determine if a known path exists.
   If the remote host falls into a subnet that we know how to reach
   (Cloned routes), then the system checks to see if it can connect
   along that interface.

   If all known paths fail, the system has one last option: the
   !S:default!" route. This route is a special type of gateway route
   (usually the only one present in the system), and is always marked
   with a c in the flags field. For hosts on a local area network,
   this gateway is set to whatever machine has a direct connection to
   the outside world (whether via PPP link, DSL, cable modem, T1, or
   another network interface).

   If you are configuring the default route for a machine which
   itself is functioning as the gateway to the outside world, then
   the default route will be the gateway machine at your Internet
   Service Provider's (ISP) site.

   Let us look at an example of default routes. This is a common
   configuration:

 [Local2]  <--ether-->  [Local1]  <--PPP--> [ISP-Serv]  <--ether-->  [T1-GW]
      

   The hosts Local1 and Local2 are at your site. Local1 is connected
   to an ISP via a dial up PPP connection. This PPP server computer
   is connected through a local area network to another gateway
   computer through an external interface to the ISPs Internet feed.

   The default routes for each of your machines will be:

          Host             Default Gateway            Interface       
   Local2             Local1                     Ethernet             
   Local1             T1-GW                      PPP                  

   A common question is !S:Why (or how) would we set the T1-GW to be
   the default gateway for Local1, rather than the ISP server it is
   connected to?!".

   Remember, since the PPP interface is using an address on the ISP's
   local network for your side of the connection, routes for any
   other machines on the ISP's local network will be automatically
   generated. Hence, you will already know how to reach the T1-GW
   machine, so there is no need for the intermediate step of sending
   traffic to the ISP server.

   It is common to use the address X.X.X.1 as the gateway address for
   your local network. So (using the same example), if your local
   class-C address space was 10.20.30 and your ISP was using 10.9.9
   then the default routes would be:

                    Host                         Default Route        
   Local2 (10.20.30.2)                    Local1 (10.20.30.1)         
   Local1 (10.20.30.1, 10.9.9.30)         T1-GW (10.9.9.1)            

   You can easily define the default route via the /etc/rc.conf file.
   In our example, on the Local2 machine, we added the following line
   in /etc/rc.conf:

 defaultrouter="10.20.30.1"

   It is also possible to do it directly from the command line with
   the route(8) command:

 # route add default 10.20.30.1

   For more information on manual manipulation of network routing
   tables, consult route(8) manual page.

     --------------------------------------------------------------

  29.2.3. Dual Homed Hosts

   There is one other type of configuration that we should cover, and
   that is a host that sits on two different networks. Technically,
   any machine functioning as a gateway (in the example above, using
   a PPP connection) counts as a dual-homed host. But the term is
   really only used to refer to a machine that sits on two local-area
   networks.

   In one case, the machine has two Ethernet cards, each having an
   address on the separate subnets. Alternately, the machine may only
   have one Ethernet card, and be using ifconfig(8) aliasing. The
   former is used if two physically separate Ethernet networks are in
   use, the latter if there is one physical network segment, but two
   logically separate subnets.

   Either way, routing tables are set up so that each subnet knows
   that this machine is the defined gateway (inbound route) to the
   other subnet. This configuration, with the machine acting as a
   router between the two subnets, is often used when we need to
   implement packet filtering or firewall security in either or both
   directions.

   If you want this machine to actually forward packets between the
   two interfaces, you need to tell FreeBSD to enable this ability.
   See the next section for more details on how to do this.

     --------------------------------------------------------------

  29.2.4. Building a Router

   A network router is simply a system that forwards packets from one
   interface to another. Internet standards and good engineering
   practice prevent the FreeBSD Project from enabling this by default
   in FreeBSD. You can enable this feature by changing the following
   variable to YES in rc.conf(5):

 gateway_enable=YES          # Set to YES if this host will be a gateway

   This option will set the sysctl(8) variable net.inet.ip.forwarding
   to 1. If you should need to stop routing temporarily, you can
   reset this to 0 temporarily.

   Your new router will need routes to know where to send the
   traffic. If your network is simple enough you can use static
   routes. FreeBSD also comes with the standard BSD routing daemon
   routed(8), which speaks RIP (both version 1 and version 2) and
   IRDP. Support for BGP v4, OSPF v2, and other sophisticated routing
   protocols is available with the net/zebra package. Commercial
   products such as GateD are also available for more complex network
   routing solutions.

     --------------------------------------------------------------

  29.2.5. Setting Up Static Routes

   Contributed by Al Hoang.

    29.2.5.1. Manual Configuration

   Let us assume we have a network as follows:

     INTERNET
       | (10.0.0.1/24) Default Router to Internet
       |
       |Interface xl0
       |10.0.0.10/24
    +------+
    |      | RouterA
    |      | (FreeBSD gateway)
    +------+
       | Interface xl1
       | 192.168.1.1/24
       |
   +--------------------------------+
    Internal Net 1      | 192.168.1.2/24
                        |
                    +------+
                    |      | RouterB
                    |      |
                    +------+
                        | 192.168.2.1/24
                        |
                      Internal Net 2
        

   In this scenario, RouterA is our FreeBSD machine that is acting as
   a router to the rest of the Internet. It has a default route set
   to 10.0.0.1 which allows it to connect with the outside world. We
   will assume that RouterB is already configured properly and knows
   how to get wherever it needs to go. (This is simple in this
   picture. Just add a default route on RouterB using 192.168.1.1 as
   the gateway.)

   If we look at the routing table for RouterA we would see something
   like the following:

 % netstat -nr
 Routing tables

 Internet:
 Destination        Gateway            Flags    Refs      Use  Netif  Expire
 default            10.0.0.1           UGS         0    49378    xl0
 127.0.0.1          127.0.0.1          UH          0        6    lo0
 10.0.0/24          link#1             UC          0        0    xl0
 192.168.1/24       link#2             UC          0        0    xl1

   With the current routing table RouterA will not be able to reach
   our Internal Net 2. It does not have a route for 192.168.2.0/24.
   One way to alleviate this is to manually add the route. The
   following command would add the Internal Net 2 network to
   RouterA's routing table using 192.168.1.2 as the next hop:

 # route add -net 192.168.2.0/24 192.168.1.2

   Now RouterA can reach any hosts on the 192.168.2.0/24 network.

     --------------------------------------------------------------

    29.2.5.2. Persistent Configuration

   The above example is perfect for configuring a static route on a
   running system. However, one problem is that the routing
   information will not persist if you reboot your FreeBSD machine.
   The way to handle the addition of a static route is to put it in
   your /etc/rc.conf file:

 # Add Internal Net 2 as a static route
 static_routes="internalnet2"
 route_internalnet2="-net 192.168.2.0/24 192.168.1.2"

   The static_routes configuration variable is a list of strings
   separated by a space. Each string references to a route name. In
   our above example we only have one string in static_routes. This
   string is internalnet2. We then add a configuration variable
   called route_internalnet2 where we put all of the configuration
   parameters we would give to the route(8) command. For our example
   above we would have used the command:

 # route add -net 192.168.2.0/24 192.168.1.2

   so we need "-net 192.168.2.0/24 192.168.1.2".

   As said above, we can have more than one string in static_routes.
   This allows us to create multiple static routes. The following
   lines shows an example of adding static routes for the
   192.168.0.0/24 and 192.168.1.0/24 networks on an imaginary router:

 static_routes="net1 net2"
 route_net1="-net 192.168.0.0/24 192.168.0.1"
 route_net2="-net 192.168.1.0/24 192.168.1.1"

     --------------------------------------------------------------

  29.2.6. Routing Propagation

   We have already talked about how we define our routes to the
   outside world, but not about how the outside world finds us.

   We already know that routing tables can be set up so that all
   traffic for a particular address space (in our examples, a class-C
   subnet) can be sent to a particular host on that network, which
   will forward the packets inbound.

   When you get an address space assigned to your site, your service
   provider will set up their routing tables so that all traffic for
   your subnet will be sent down your PPP link to your site. But how
   do sites across the country know to send to your ISP?

   There is a system (much like the distributed DNS information) that
   keeps track of all assigned address-spaces, and defines their
   point of connection to the Internet Backbone. The !S:Backbone!"
   are the main trunk lines that carry Internet traffic across the
   country, and around the world. Each backbone machine has a copy of
   a master set of tables, which direct traffic for a particular
   network to a specific backbone carrier, and from there down the
   chain of service providers until it reaches your network.

   It is the task of your service provider to advertise to the
   backbone sites that they are the point of connection (and thus the
   path inward) for your site. This is known as route propagation.

     --------------------------------------------------------------

  29.2.7. Troubleshooting

   Sometimes, there is a problem with routing propagation, and some
   sites are unable to connect to you. Perhaps the most useful
   command for trying to figure out where routing is breaking down is
   the traceroute(8) command. It is equally useful if you cannot seem
   to make a connection to a remote machine (i.e. ping(8) fails).

   The traceroute(8) command is run with the name of the remote host
   you are trying to connect to. It will show the gateway hosts along
   the path of the attempt, eventually either reaching the target
   host, or terminating because of a lack of connection.

   For more information, see the manual page for traceroute(8).

     --------------------------------------------------------------

  29.2.8. Multicast Routing

   FreeBSD supports both multicast applications and multicast routing
   natively. Multicast applications do not require any special
   configuration of FreeBSD; applications will generally run out of
   the box. Multicast routing requires that support be compiled into
   the kernel:

 options MROUTING

   In addition, the multicast routing daemon, mrouted(8) must be
   configured to set up tunnels and DVMRP via /etc/mrouted.conf. More
   details on multicast configuration may be found in the manual page
   for mrouted(8).

     --------------------------------------------------------------

29.3. Wireless Networking

   Loader, Marc Fonvieille, YENB Murray Stokely.

     --------------------------------------------------------------

  29.3.1. Wireless Networking Basics

   Most wireless networks are based on the IEEE 802.11 standards. A
   basic wireless network consists of multiple stations communicating
   with radios that broadcast in either the 2.4GHz or 5GHz band
   (though this varies according to the locale and is also changing
   to enable communication in the 2.3GHz and 4.9GHz ranges).

   802.11 networks are organized in two ways: in infrastructure mode
   one station acts as a master with all the other stations
   associating to it; the network is known as a BSS and the master
   station is termed an access point (AP). In a BSS all communication
   passes through the AP; even when one station wants to communicate
   with another wireless station messages must go through the AP. In
   the second form of network there is no master and stations
   communicate directly. This form of network is termed an IBSS and
   is commonly known as an ad-hoc network.

   802.11 networks were first deployed in the 2.4GHz band using
   protocols defined by the IEEE 802.11 and 802.11b standard. These
   specifications include the operating frequencies, MAC layer
   characteristics including framing and transmission rates
   (communication can be done at various rates). Later the 802.11a
   standard defined operation in the 5GHz band, including different
   signalling mechanisms and higher transmission rates. Still later
   the 802.11g standard was defined to enable use of 802.11a
   signalling and transmission mechanisms in the 2.4GHz band in such
   a way as to be backwards compatible with 802.11b networks.

   Separate from the underlying transmission techniques 802.11
   networks have a variety of security mechanisms. The original
   802.11 specifications defined a simple security protocol called
   WEP. This protocol uses a fixed pre-shared key and the RC4
   cryptographic cipher to encode data transmitted on a network.
   Stations must all agree on the fixed key in order to communicate.
   This scheme was shown to be easily broken and is now rarely used
   except to discourage transient users from joining networks.
   Current security practice is given by the IEEE 802.11i
   specification that defines new cryptographic ciphers and an
   additional protocol to authenticate stations to an access point
   and exchange keys for doing data communication. Further,
   cryptographic keys are periodically refreshed and there are
   mechanisms for detecting intrusion attempts (and for countering
   intrusion attempts). Another security protocol specification
   commonly used in wireless networks is termed WPA. This was a
   precursor to 802.11i defined by an industry group as an interim
   measure while waiting for 802.11i to be ratified. WPA specifies a
   subset of the requirements found in 802.11i and is designed for
   implementation on legacy hardware. Specifically WPA requires only
   the TKIP cipher that is derived from the original WEP cipher.
   802.11i permits use of TKIP but also requires support for a
   stronger cipher, AES-CCM, for encrypting data. (The AES cipher was
   not required in WPA because it was deemed too computationally
   costly to be implemented on legacy hardware.)

   Other than the above protocol standards the other important
   standard to be aware of is 802.11e. This defines protocols for
   deploying multi-media applications such as streaming video and
   voice over IP (VoIP) in an 802.11 network. Like 802.11i, 802.11e
   also has a precursor specification termed WME (later renamed WMM)
   that has been defined by an industry group as a subset of 802.11e
   that can be deployed now to enable multi-media applications while
   waiting for the final ratification of 802.11e. The most important
   thing to know about 802.11e and WME/WMM is that it enables
   prioritized traffic use of a wireless network through Quality of
   Service (QoS) protocols and enhanced media access protocols.
   Proper implementation of these protocols enable high speed
   bursting of data and prioritized traffic flow.

   Since the 6.0 version, FreeBSD supports networks that operate
   using 802.11a, 802.11b, and 802.11g. The WPA and 802.11i security
   protocols are likewise supported (in conjunction with any of 11a,
   11b, and 11g) and QoS and traffic prioritization required by the
   WME/WMM protocols are supported for a limited set of wireless
   devices.

     --------------------------------------------------------------

  29.3.2. Basic Setup

    29.3.2.1. Kernel Configuration

   To use wireless networking you need a wireless networking card and
   to configure the kernel with the appropriate wireless networking
   support. The latter is separated into multiple modules so that you
   only need to configure the software you are actually going to use.

   The first thing you need is a wireless device. The most commonly
   used devices are those that use parts made by Atheros. These
   devices are supported by the ath(4) driver and require the
   following line to be added to the /boot/loader.conf file:

 if_ath_load="YES"

   The Atheros driver is split up into three separate pieces: the
   driver proper (ath(4)), the hardware support layer that handles
   chip-specific functions (ath_hal(4)), and an algorithm for
   selecting which of several possible rates for transmitting frames
   (ath_rate_sample here). When you load this support as modules
   these dependencies are automatically handled for you. If instead
   of an Atheros device you had another device you would select the
   module for that device; e.g.:

 if_wi_load="YES"

   for devices based on the Intersil Prism parts (wi(4) driver).

     -a`: In the rest of this document, we will use an ath(4) device,
     the device name in the examples must be changed according to
     your configuration. A list of available wireless drivers can be
     found at the beginning of the wlan(4) manual page. If a native
     FreeBSD driver for your wireless device does not exist, it may
     be possible to directly use the Windows driver with the help of
     the NDIS driver wrapper.

   With a device driver configured you need to also bring in the
   802.11 networking support required by the driver. For the ath(4)
   driver this is at least the wlan(4) module; this module is
   automatically loaded with the wireless device driver. With that
   you will need the modules that implement cryptographic support for
   the security protocols you intend to use. These are intended to be
   dynamically loaded on demand by the wlan(4) module but for now
   they must be manually configured. The following modules are
   available: wlan_wep(4), wlan_ccmp(4) and wlan_tkip(4). Both
   wlan_ccmp(4) and wlan_tkip(4) drivers are only needed if you
   intend to use the WPA and/or 802.11i security protocols. If your
   network is to run totally open (i.e., with no encryption) then you
   do not even need the wlan_wep(4) support. To load these modules at
   boot time, add the following lines to /boot/loader.conf:

 wlan_wep_load="YES"
 wlan_ccmp_load="YES"
 wlan_tkip_load="YES"

   With this information in the system bootstrap configuration file
   (i.e., /boot/loader.conf), you have to reboot your FreeBSD box. If
   you do not want to reboot your machine for the moment, you can
   just load the modules by hand using kldload(8).

     -a`: If you do not want to use modules, it is possible to
     compile these drivers into the kernel by adding the following
     lines to your kernel configuration file:

 device ath               # Atheros IEEE 802.11 wireless network driver
 device ath_hal           # Atheros Hardware Access Layer
 device ath_rate_sample   # John Bicket's SampleRate control algorithm.
 device wlan              # 802.11 support (Required)
 device wlan_wep          # WEP crypto support for 802.11 devices
 device wlan_ccmp         # AES-CCMP crypto support for 802.11 devices
 device wlan_tkip         # TKIP and Michael crypto support for 802.11 devices

     With this information in the kernel configuration file,
     recompile the kernel and reboot your FreeBSD machine.

   When the system is up, we could find some information about the
   wireless device in the boot messages, like this:

 ath0: <Atheros 5212> mem 0xff9f0000-0xff9fffff irq 17 at device 2.0 on pci2
 ath0: Ethernet address: 00:11:95:d5:43:62
 ath0: mac 7.9 phy 4.5 radio 5.6

     --------------------------------------------------------------

  29.3.3. Infrastructure Mode

   The infrastructure mode or BSS mode is the mode that is typically
   used. In this mode, a number of wireless access points are
   connected to a wired network. Each wireless network has its own
   name, this name is called the SSID of the network. Wireless
   clients connect to the wireless access points.

     --------------------------------------------------------------

    29.3.3.1. FreeBSD Clients

      29.3.3.1.1. How to Find Access Points

   To scan for networks, use the ifconfig command. This request may
   take a few moments to complete as it requires that the system
   switches to each available wireless frequency and probes for
   available access points. Only the super-user can initiate such a
   scan:

 # ifconfig ath0 up scan
 SSID            BSSID              CHAN RATE  S:N   INT CAPS
 dlinkap         00:13:46:49:41:76    6   54M 29:0   100 EPS  WPA WME
 freebsdap       00:11:95:c3:0d:ac    1   54M 22:0   100 EPS  WPA

     -a`: You must mark the interface up before you can scan.
     Subsequent scan requests do not require you to mark the
     interface up again.

   The output of a scan request lists each BSS/IBSS network found.
   Beside the name of the network, SSID, we find the BSSID which is
   the MAC address of the access point. The CAPS field identifies the
   type of each network and the capabilities of the stations
   operating there:

   E

           Extended Service Set (ESS). Indicates that the station is
           part of an infrastructure network (in contrast to an
           IBSS/ad-hoc network).

   I

           IBSS/ad-hoc network. Indicates that the station is part of
           an ad-hoc network (in contrast to an ESS network).

   P

           Privacy. Data confidentiality is required for all data
           frames exchanged within the BSS. This means that this BSS
           requires the station to use cryptographic means such as
           WEP, TKIP or AES-CCMP to encrypt/decrypt data frames being
           exchanged with others.

   S

           Short Preamble. Indicates that the network is using short
           preambles (defined in 802.11b High Rate/DSSS PHY, short
           preamble utilizes a 56 bit sync field in contrast to a 128
           bit field used in long preamble mode).

   s

           Short slot time. Indicates that the 802.11g network is
           using a short slot time because there are no legacy
           (802.11b) stations present.

   One can also display the current list of known networks with:

 # ifconfig ath0 list scan

   This information may be updated automatically by the adapter or
   manually with a scan request. Old data is automatically removed
   from the cache, so over time this list may shrink unless more
   scans are done.

     --------------------------------------------------------------

      29.3.3.1.2. Basic Settings

   This section provides a simple example of how to make the wireless
   network adapter work in FreeBSD without encryption. After you are
   familiar with these concepts, we strongly recommend using WPA to
   set up your wireless network.

   There are three basic steps to configure a wireless network:
   selecting an access point, authenticating your station, and
   configuring an IP address. The following sections discuss each
   step.

     --------------------------------------------------------------

        29.3.3.1.2.1. Selecting an Access Point

   Most of time it is sufficient to let the system choose an access
   point using the builtin heuristics. This is the default behaviour
   when you mark an interface up or otherwise configure an interface
   by listing it in /etc/rc.conf, e.g.:

 ifconfig_ath0="DHCP"

   If there are multiple access points and you want to select a
   specific one, you can select it by its SSID:

 ifconfig_ath0="ssid your_ssid_here DHCP"

   In an environment where there are multiple access points with the
   same SSID (often done to simplify roaming) it may be necessary to
   associate to one specific device. In this case you can also
   specify the BSSID of the access point (you can also leave off the
   SSID):

 ifconfig_ath0="ssid your_ssid_here bssid xx:xx:xx:xx:xx:xx DHCP"

   There are other ways to constrain the choice of an access point
   such as limiting the set of frequencies the system will scan on.
   This may be useful if you have a multi-band wireless card as
   scanning all the possible channels can be time-consuming. To limit
   operation to a specific band you can use the mode parameter; e.g.:

 ifconfig_ath0="mode 11g ssid your_ssid_here DHCP"

   will force the card to operate in 802.11g which is defined only
   for 2.4GHz frequencies so any 5GHz channels will not be
   considered. Other ways to do this are the channel parameter, to
   lock operation to one specific frequency, and the chanlist
   parameter, to specify a list of channels for scanning. More
   information about these parameters can be found in the ifconfig(8)
   manual page.

     --------------------------------------------------------------

        29.3.3.1.2.2. Authentication

   Once you have selected an access point your station needs to
   authenticate before it can pass data. Authentication can happen in
   several ways. The most common scheme used is termed open
   authentication and allows any station to join the network and
   communicate. This is the authentication you should use for test
   purpose the first time you set up a wireless network. Other
   schemes require cryptographic handshakes be completed before data
   traffic can flow; either using pre-shared keys or secrets, or more
   complex schemes that involve backend services such as RADIUS. Most
   users will use open authentication which is the default setting.
   Next most common setup is WPA-PSK, also known as WPA Personal,
   which is described below.

     -a`: If you have an Apple AirPort(R) Extreme base station for an
     access point you may need to configure shared-key authentication
     together with a WEP key. This can be done in the /etc/rc.conf
     file or using the wpa_supplicant(8) program. If you have a
     single AirPort base station you can setup access with something
     like:

 ifconfig_ath0="authmode shared wepmode on weptxkey 1 wepkey 01234567 DHCP"

     In general shared key authentication is to be avoided because it
     uses the WEP key material in a highly-constrained manner making
     it even easier to crack the key. If WEP must be used (e.g., for
     compatibility with legacy devices) it is better to use WEP with
     open authentication. More information regarding WEP can be found
     in the uU 29.3.3.1.4 ,`.

     --------------------------------------------------------------

        29.3.3.1.2.3. Getting an IP Address with DHCP

   Once you have selected an access point and set the authentication
   parameters, you will have to get an IP address to communicate.
   Most of time you will obtain your wireless IP address via DHCP. To
   achieve that, simply edit /etc/rc.conf and add DHCP to the
   configuration for your device as shown in various examples above:

 ifconfig_ath0="DHCP"

   At this point, you are ready to bring up the wireless interface:

 # /etc/rc.d/netif start

   Once the interface is running, use ifconfig to see the status of
   the interface ath0:

 # ifconfig ath0
 ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1
         inet 192.168.1.100 netmask 0xffffff00 broadcast 192.168.1.255
         ether 00:11:95:d5:43:62
         media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps)
         status: associated
         ssid dlinkap channel 6 bssid 00:13:46:49:41:76
         authmode OPEN privacy OFF txpowmax 36 protmode CTS bintval 100

   The status: associated means you are connected to the wireless
   network (to the dlinkap network in our case). The bssid
   00:13:46:49:41:76 part is the MAC address of your access point;
   the authmode line informs you that the communication is not
   encrypted (OPEN).

     --------------------------------------------------------------

        29.3.3.1.2.4. Static IP Address

   In the case you cannot obtain an IP address from a DHCP server,
   you can set a fixed IP address. Replace the DHCP keyword shown
   above with the address information. Be sure to retain any other
   parameters you have set up for selecting an access point:

 ifconfig_ath0="inet 192.168.1.100 netmask 255.255.255.0 ssid your_ssid_here"

     --------------------------------------------------------------

      29.3.3.1.3. WPA

   WPA (Wi-Fi Protected Access) is a security protocol used together
   with 802.11 networks to address the lack of proper authentication
   and the weakness of WEP. WPA leverages the 802.1X authentication
   protocol and uses one of several ciphers instead of WEP for data
   integrity. The only cipher required by WPA is TKIP (Temporary Key
   Integrity Protocol) which is a cipher that extends the basic RC4
   cipher used by WEP by adding integrity checking, tamper detection,
   and measures for responding to any detected intrusions. TKIP is
   designed to work on legacy hardware with only software
   modification; it represents a compromise that improves security
   but is still not entirely immune to attack. WPA also specifies the
   AES-CCMP cipher as an alternative to TKIP and that is preferred
   when possible; for this specification the term WPA2 (or RSN) is
   commonly used.

   WPA defines authentication and encryption protocols.
   Authentication is most commonly done using one of two techniques:
   by 802.1X and a backend authentication service such as RADIUS, or
   by a minimal handshake between the station and the access point
   using a pre-shared secret. The former is commonly termed WPA
   Enterprise with the latter known as WPA Personal. Since most
   people will not set up a RADIUS backend server for wireless
   network, WPA-PSK is by far the most commonly encountered
   configuration for WPA.

   The control of the wireless connection and the authentication (key
   negotiation or authentication with a server) is done with the
   wpa_supplicant(8) utility. This program requires a configuration
   file, /etc/wpa_supplicant.conf, to run. More information regarding
   this file can be found in the wpa_supplicant.conf(5) manual page.

     --------------------------------------------------------------

        29.3.3.1.3.1. WPA-PSK

   WPA-PSK also known as WPA-Personal is based on a pre-shared key
   (PSK) generated from a given password and that will be used as the
   master key in the wireless network. This means every wireless user
   will share the same key. WPA-PSK is intended for small networks
   where the use of an authentication server is not possible or
   desired.

     A:uS:iAlways use strong passwords that are sufficiently long and
     made from a rich alphabet so they will not be guessed and/or
     attacked.

   The first step is the configuration of the
   /etc/wpa_supplicant.conf file with the SSID and the pre-shared key
   of your network:

 network={
   ssid="freebsdap"
   psk="freebsdmall"
 }

   Then, in /etc/rc.conf, we indicate that the wireless device
   configuration will be done with WPA and the IP address will be
   obtained with DHCP:

 ifconfig_ath0="WPA DHCP"

   Then, we can bring up the interface:

 # /etc/rc.d/netif start
 Starting wpa_supplicant.
 DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 5
 DHCPDISCOVER on ath0 to 255.255.255.255 port 67 interval 6
 DHCPOFFER from 192.168.0.1
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPACK from 192.168.0.1
 bound to 192.168.0.254 -- renewal in 300 seconds.
 ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1
       inet 192.168.0.254 netmask 0xffffff00 broadcast 192.168.0.255
       ether 00:11:95:d5:43:62
       media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps)
       status: associated
       ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
       authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit txpowmax 36
       protmode CTS roaming MANUAL bintval 100

   Or you can try to configure it manually using the same
   /etc/wpa_supplicant.conf above, and run:

 # wpa_supplicant -i ath0 -c /etc/wpa_supplicant.conf
 Trying to associate with 00:11:95:c3:0d:ac (SSID='freebsdap' freq=2412 MHz)
 Associated with 00:11:95:c3:0d:ac
 WPA: Key negotiation completed with 00:11:95:c3:0d:ac [PTK=TKIP GTK=TKIP]

   The next operation is the launch of the dhclient command to get
   the IP address from the DHCP server:

 # dhclient ath0
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPACK from 192.168.0.1
 bound to 192.168.0.254 -- renewal in 300 seconds.
 # ifconfig ath0
 ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1
       inet 192.168.0.254 netmask 0xffffff00 broadcast 192.168.0.255
       ether 00:11:95:d5:43:62
       media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/48Mbps)
       status: associated
       ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
       authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit txpowmax 36
       protmode CTS roaming MANUAL bintval 100

     -a`: If the /etc/rc.conf is set up with the line
     ifconfig_ath0="DHCP" then it is no need to run the dhclient
     command manually, dhclient will be launched after wpa_supplicant
     plumbs the keys.

   In the case where the use of DHCP is not possible, you can set a
   static IP address after wpa_supplicant has authenticated the
   station:

 # ifconfig ath0 inet 192.168.0.100 netmask 255.255.255.0
 # ifconfig ath0
 ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1
       inet 192.168.0.100 netmask 0xffffff00 broadcast 192.168.0.255
       ether 00:11:95:d5:43:62
       media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/36Mbps)
       status: associated
       ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
       authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit txpowmax 36
       protmode CTS roaming MANUAL bintval 100

   When DHCP is not used, you also have to manually set up the
   default gateway and the nameserver:

 # route add default your_default_router
 # echo "nameserver your_DNS_server" >> /etc/resolv.conf

     --------------------------------------------------------------

        29.3.3.1.3.2. WPA with EAP-TLS

   The second way to use WPA is with an 802.1X backend authentication
   server, in this case WPA is called WPA-Enterprise to make
   difference with the less secure WPA-Personal with its pre-shared
   key. The authentication in WPA-Enterprise is based on EAP
   (Extensible Authentication Protocol).

   EAP does not come with an encryption method, it was decided to
   embed EAP inside an encrypted tunnel. Many types of EAP
   authentication methods have been designed, the most common methods
   are EAP-TLS, EAP-TTLS and EAP-PEAP.

   EAP-TLS (EAP with Transport Layer Security) is a very
   well-supported authentication protocol in the wireless world since
   it was the first EAP method to be certified by the Wi-Fi alliance.
   EAP-TLS will require three certificates to run: the CA certificate
   (installed on all machines), the server certificate for your
   authentication server, and one client certificate for each
   wireless client. In this EAP method, both authentication server
   and wireless client authenticate each other in presenting their
   respective certificates, and they verify that these certificates
   were signed by your organization's certificate authority (CA).

   As previously, the configuration is done via
   /etc/wpa_supplicant.conf:

 network={
   ssid="freebsdap" (1)
   proto=RSN  (2)
   key_mgmt=WPA-EAP (3)
   eap=TLS (4)
   identity="loader" (5)
   ca_cert="/etc/certs/cacert.pem" (6)
   client_cert="/etc/certs/clientcert.pem" (7)
   private_key="/etc/certs/clientkey.pem" (8)
   private_key_passwd="freebsdmallclient" (9)
 }

   (1)
           This field indicates the network name (SSID).
   (2)
           Here, we use RSN (IEEE 802.11i) protocol, i.e., WPA2.
   (3)
           The key_mgmt line refers to the key management protocol we
           use. In our case it is WPA using EAP authentication:
           WPA-EAP.
   (4)
           In this field, we mention the EAP method for our
           connection.
   (5)
           The identity field contains the identity string for EAP.
   (6)
           The ca_cert field indicates the pathname of the CA
           certificate file. This file is needed to verify the server
           certificat.
   (7)
           The client_cert line gives the pathname to the client
           certificate file. This certificate is unique to each
           wireless client of the network.
   (8)
           The private_key field is the pathname to the client
           certificate private key file.
   (9)
           The private_key_passwd field contains the passphrase for
           the private key.

   Then add the following line to /etc/rc.conf:

 ifconfig_ath0="WPA DHCP"

   The next step is to bring up the interface with the help of the
   rc.d facility:

 # /etc/rc.d/netif start
 Starting wpa_supplicant.
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPACK from 192.168.0.20
 bound to 192.168.0.254 -- renewal in 300 seconds.
 ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1
       inet 192.168.0.254 netmask 0xffffff00 broadcast 192.168.0.255
       ether 00:11:95:d5:43:62
       media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
       status: associated
       ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
       authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit
       txpowmax 36 protmode CTS roaming MANUAL bintval 100

   As previously shown, it is also possible to bring up the interface
   manually with both wpa_supplicant and ifconfig commands.

     --------------------------------------------------------------

        29.3.3.1.3.3. WPA with EAP-TTLS

   With EAP-TLS both the authentication server and the client need a
   certificate, with EAP-TTLS (EAP-Tunneled Transport Layer Security)
   a client certificate is optional. This method is close to what
   some secure web sites do , where the web server can create a
   secure SSL tunnel even if the visitors do not have client-side
   certificates. EAP-TTLS will use the encrypted TLS tunnel for safe
   transport of the authentication data.

   The configuration is done via the /etc/wpa_supplicant.conf file:

 network={
   ssid="freebsdap"
   proto=RSN
   key_mgmt=WPA-EAP
   eap=TTLS (1)
   identity="test" (2)
   password="test" (3)
   ca_cert="/etc/certs/cacert.pem" (4)
   phase2="auth=MD5" (5)
 }

   (1)
           In this field, we mention the EAP method for our
           connection.
   (2)
           The identity field contains the identity string for EAP
           authentication inside the encrypted TLS tunnel.
   (3)
           The password field contains the passphrase for the EAP
           authentication.
   (4)
           The ca_cert field indicates the pathname of the CA
           certificate file. This file is needed to verify the server
           certificat.
   (5)
           In this field, we mention the authentication method used
           in the encrypted TLS tunnel. In our case, EAP with
           MD5-Challenge has been used. The !S:inner authentication!"
           phase is often called !S:phase2!".

   You also have to add the following line to /etc/rc.conf:

 ifconfig_ath0="WPA DHCP"

   The next step is to bring up the interface:

 # /etc/rc.d/netif start
 Starting wpa_supplicant.
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPACK from 192.168.0.20
 bound to 192.168.0.254 -- renewal in 300 seconds.
 ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1
       inet 192.168.0.254 netmask 0xffffff00 broadcast 192.168.0.255
       ether 00:11:95:d5:43:62
       media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
       status: associated
       ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
       authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit
       txpowmax 36 protmode CTS roaming MANUAL bintval 100

     --------------------------------------------------------------

        29.3.3.1.3.4. WPA with EAP-PEAP

   PEAP (Protected EAP) has been designed as an alternative to
   EAP-TTLS. There are two types of PEAP methods, the most common one
   is PEAPv0/EAP-MSCHAPv2. In the rest of this document, we will use
   the PEAP term to refer to that EAP method. PEAP is the most used
   EAP standard after EAP-TLS, in other words if you have a network
   with mixed OSes, PEAP should be the most supported standard after
   EAP-TLS.

   PEAP is similar to EAP-TTLS: it uses a server-side certificate to
   authenticate clients by creating an encrypted TLS tunnel between
   the client and the authentication server, which protects the
   ensuing exchange of authentication information. In term of
   security the difference between EAP-TTLS and PEAP is that PEAP
   authentication broadcasts the username in clear, only the password
   is sent in the encrypted TLS tunnel. EAP-TTLS will use the TLS
   tunnel for both username and password.

   We have to edit the /etc/wpa_supplicant.conf file and add the
   EAP-PEAP related settings:

 network={
   ssid="freebsdap"
   proto=RSN
   key_mgmt=WPA-EAP
   eap=PEAP (1)
   identity="test" (2)
   password="test" (3)
   ca_cert="/etc/certs/cacert.pem" (4)
   phase1="peaplabel=0" (5)
   phase2="auth=MSCHAPV2" (6)
 }

   (1)
           In this field, we mention the EAP method for our
           connection.
   (2)
           The identity field contains the identity string for EAP
           authentication inside the encrypted TLS tunnel.
   (3)
           The password field contains the passphrase for the EAP
           authentication.
   (4)
           The ca_cert field indicates the pathname of the CA
           certificate file. This file is needed to verify the server
           certificat.
   (5)
           This field contains the parameters for the first phase of
           the authentication (the TLS tunnel). According to the
           authentication server used, you will have to specify a
           specific label for the authentication. Most of time, the
           label will be !S:client EAP encryption!" which is set by
           using peaplabel=0. More information can be found in the
           wpa_supplicant.conf(5) manual page.
   (6)
           In this field, we mention the authentication protocol used
           in the encrypted TLS tunnel. In the case of PEAP, it is
           auth=MSCHAPV2.

   The following must be added to /etc/rc.conf:

 ifconfig_ath0="WPA DHCP"

   Then, we can bring up the interface:

 # /etc/rc.d/netif start
 Starting wpa_supplicant.
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPREQUEST on ath0 to 255.255.255.255 port 67
 DHCPACK from 192.168.0.20
 bound to 192.168.0.254 -- renewal in 300 seconds.
 ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
       inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1
       inet 192.168.0.254 netmask 0xffffff00 broadcast 192.168.0.255
       ether 00:11:95:d5:43:62
       media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps)
       status: associated
       ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
       authmode WPA2/802.11i privacy ON deftxkey UNDEF TKIP 2:128-bit
       txpowmax 36 protmode CTS roaming MANUAL bintval 100

     --------------------------------------------------------------

      29.3.3.1.4. WEP

   WEP (Wired Equivalent Privacy) is part of the original 802.11
   standard. There is no authentication mechanism, only a weak form
   of access control, and it is easily to be cracked.

   WEP can be set up with ifconfig:

 # ifconfig ath0 inet 192.168.1.100 netmask 255.255.255.0 ssid my_net \
             wepmode on weptxkey 3 wepkey 3:0x3456789012

     * The weptxkey means which WEP key will be used in the
       transmission. Here we used the third key. This must match the
       setting in the access point.

     * The wepkey means setting the selected WEP key. It should in
       the format index:key, if the index is not given, key 1 is set.
       That is to say we need to set the index if we use keys other
       than the first key.

         -a`: You must replace the 0x3456789012 with the key
         configured for use on the access point.

   You are encouraged to read ifconfig(8) manual page for further
   information.

   The wpa_supplicant facility also can be used to configure your
   wireless interface with WEP. The example above can be set up by
   adding the following lines to /etc/wpa_supplicant.conf:

 network={
   ssid="my_net"
   key_mgmt=NONE
   wep_key3=3456789012
   wep_tx_keyidx=3
 }

   Then:

 # wpa_supplicant -i ath0 -c /etc/wpa_supplicant.conf
 Trying to associate with 00:13:46:49:41:76 (SSID='dlinkap' freq=2437 MHz)
 Associated with 00:13:46:49:41:76

     --------------------------------------------------------------

  29.3.4. Ad-hoc Mode

   IBSS mode, also called ad-hoc mode, is designed for point to point
   connections. For example, to establish an ad-hoc network between
   the machine A and the machine B we will just need to choose two IP
   adresses and a SSID.

   On the box A:

 # ifconfig ath0 inet 192.168.0.1 netmask 255.255.255.0 ssid freebsdap mediaopt adhoc
 # ifconfig ath0
   ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
           inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
           inet6 fe80::211:95ff:fec3:dac%ath0 prefixlen 64 scopeid 0x4
           ether 00:11:95:c3:0d:ac
           media: IEEE 802.11 Wireless Ethernet autoselect <adhoc> (autoselect <adhoc>)
           status: associated
           ssid freebsdap channel 2 bssid 02:11:95:c3:0d:ac
           authmode OPEN privacy OFF txpowmax 36 protmode CTS bintval 100

   The adhoc parameter indicates the interface is running in the IBSS
   mode.

   On B, we should be able to detect A:

 # ifconfig ath0 up scan
   SSID            BSSID              CHAN RATE  S:N   INT CAPS
   freebsdap       02:11:95:c3:0d:ac    2   54M 19:0   100 IS

   The I in the output confirms the machine A is in ad-hoc mode. We
   just have to configure B with a different IP address:

 # ifconfig ath0 inet 192.168.0.2 netmask 255.255.255.0 ssid freebsdap mediaopt adhoc
 # ifconfig ath0
   ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
           inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1
           inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
           ether 00:11:95:d5:43:62
           media: IEEE 802.11 Wireless Ethernet autoselect <adhoc> (autoselect <adhoc>)
           status: associated
           ssid freebsdap channel 2 bssid 02:11:95:c3:0d:ac
           authmode OPEN privacy OFF txpowmax 36 protmode CTS bintval 100

   Both A and B are now ready to exchange informations.

     --------------------------------------------------------------

  29.3.5. FreeBSD Host Access Points

   FreeBSD can act as an Access Point (AP) which eliminates the need
   to buy a hardware AP or run an ad-hoc network. This can be
   particularly useful when your FreeBSD machine is acting as a
   gateway to another network (e.g., the Internet).

     --------------------------------------------------------------

    29.3.5.1. Basic Settings

   Before configuring your FreeBSD machine as an AP, the kernel must
   be configured with the appropriate wireless networking support for
   your wireless card. You also have to add the support for the
   security protocols you intend to use. For more details, see uU
   29.3.2 ,`.

     -a`: The use of the NDIS driver wrapper and the Windows drivers
     do not allow currently the AP operation. Only native FreeBSD
     wireless drivers support AP mode.

   Once the wireless networking support is loaded, you can check if
   your wireless device supports the host-based access point mode
   (also know as hostap mode):

 # ifconfig ath0 list caps
 ath0=783ed0f<WEP,TKIP,AES,AES_CCM,IBSS,HOSTAP,AHDEMO,TXPMGT,SHSLOT,SHPREAMBLE,MONITOR,TKIPMIC,WPA1,WPA2,BURST,WME>

   This output displays the card capabilities; the HOSTAP word
   confirms this wireless card can act as an Access Point. Various
   supported ciphers are also mentioned: WEP, TKIP, WPA2, etc., these
   informations are important to know what security protocols could
   be set on the Access Point.

   The wireless device can now be put into hostap mode and configured
   with the correct SSID and IP address:

 # ifconfig ath0 ssid freebsdap mode 11g mediaopt hostap inet 192.168.0.1 netmask 255.255.255.0

   Use again ifconfig to see the status of the ath0 interface:

 # ifconfig ath0
   ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
           inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
           inet6 fe80::211:95ff:fec3:dac%ath0 prefixlen 64 scopeid 0x4
           ether 00:11:95:c3:0d:ac
           media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
           status: associated
           ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
           authmode OPEN privacy OFF txpowmax 38 bmiss 7 protmode CTS burst dtimperiod 1 bintval 100

   The hostap parameter indicates the interface is running in the
   host-based access point mode.

   The interface configuration can be done automatically at boot time
   by adding the following line to /etc/rc.conf:

 ifconfig_ath0="ssid freebsdap mode 11g mediaopt hostap inet 192.168.0.1 netmask 255.255.255.0"

     --------------------------------------------------------------

    29.3.5.2. Host-based Access Point without Authentication or
    Encryption

   Although it is not recommended to run an AP without any
   authentication or encryption, this is a simple way to check if
   your AP is working. This configuration is also important for
   debugging client issues.

   Once the AP configured as previously shown, it is possible from
   another wireless machine to initiate a scan to find the AP:

 # ifconfig ath0 up scan
 SSID            BSSID              CHAN RATE  S:N   INT CAPS
 freebsdap       00:11:95:c3:0d:ac    1   54M 22:1   100 ES

   The client machine found the Access Point and can be associated
   with it:

 # ifconfig ath0 ssid freebsdap inet 192.168.0.2 netmask 255.255.255.0
 # ifconfig ath0
   ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
           inet6 fe80::211:95ff:fed5:4362%ath0 prefixlen 64 scopeid 0x1
           inet 192.168.0.2 netmask 0xffffff00 broadcast 192.168.0.255
           ether 00:11:95:d5:43:62
           media: IEEE 802.11 Wireless Ethernet autoselect (OFDM/54Mbps)
           status: associated
           ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
           authmode OPEN privacy OFF txpowmax 36 protmode CTS bintval 100

     --------------------------------------------------------------

    29.3.5.3. WPA Host-based Access Point

   This section will focus on setting up FreeBSD Access Point using
   the WPA security protocol. More details regarding WPA and the
   configuration of WPA-based wireless clients can be found in the uU
   29.3.3.1.3 ,`.

   The hostapd daemon is used to deal with client authentication and
   keys management on the WPA enabled Access Point.

   In the following, all the configuration operations will be
   performed on the FreeBSD machine acting as AP. Once the AP is
   correctly working, hostapd should be automatically enabled at boot
   with the following line in /etc/rc.conf:

 hostapd_enable="YES"

   Before trying to configure hostapd, be sure you have done the
   basic settings introduced in the uU 29.3.5.1 ,`.

     --------------------------------------------------------------

      29.3.5.3.1. WPA-PSK

   WPA-PSK is intended for small networks where the use of an backend
   authentication server is not possible or desired.

   The configuration is done in the /etc/hostapd.conf file:

 interface=ath0 (1)
 debug=1 (2)
 ctrl_interface=/var/run/hostapd (3)
 ctrl_interface_group=wheel (4)
 ssid=freebsdap (5)
 wpa=1 (6)
 wpa_passphrase=freebsdmall (7)
 wpa_key_mgmt=WPA-PSK (8)
 wpa_pairwise=CCMP TKIP (9)

   (1)
           This field indicates the wireless interface used for the
           Access Point.
   (2)
           This field sets the level of verbosity during the
           execution of hostapd. A value of 1 represents the minimal
           level.
   (3)
           The ctrl_interface field gives the pathname of the
           directory used by hostapd to stores its domain socket
           files for the communication with external programs such as
           hostapd_cli(8). The default value is used here.
   (4)
           The ctrl_interface_group line sets the group (here, it is
           the wheel group) allowed to access to the control
           interface files.
   (5)
           This field sets the network name.
   (6)
           The wpa field enables WPA and specifies which WPA
           authentication protocol will be required. A value of 1
           configures the AP for WPA-PSK.
   (7)
           The wpa_passphrase field contains the ASCII passphrase for
           the WPA authentication.

             A:uS:iAlways use strong passwords that are sufficiently
             long and made from a rich alphabet so they will not be
             guessed and/or attacked.

   (8)
           The wpa_key_mgmt line refers to the key management
           protocol we use. In our case it is WPA-PSK.
   (9)
           The wpa_pairwise field indicates the set of accepted
           encryption algorithms by the Access Point. Here both TKIP
           (WPA) and CCMP (WPA2) ciphers are accepted. CCMP cipher is
           an alternative to TKIP and that is strongly preferred when
           possible; TKIP should be used solely for stations
           incapable of doing CCMP.

   The next step is to start hostapd:

 # /etc/rc.d/hostapd forcestart

 # ifconfig ath0
   ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 2290
           inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
           inet6 fe80::211:95ff:fec3:dac%ath0 prefixlen 64 scopeid 0x4
           ether 00:11:95:c3:0d:ac
           media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
           status: associated
           ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
           authmode WPA2/802.11i privacy MIXED deftxkey 2 TKIP 2:128-bit txpowmax 36 protmode CTS dtimperiod 1 bintval 100

   The Access Point is running, the clients can now be associated
   with it, see uU 29.3.3.1.3 ,` for more details. It is possible to
   see the stations associated with the AP using the ifconfig ath0
   list sta command.

     --------------------------------------------------------------

    29.3.5.4. WEP Host-based Access Point

   It is not recommended to use WEP for setting up an Access Point
   since there is no authentication mechanism and it is easily to be
   cracked. Some legacy wireless cards only support WEP as security
   protocol, these cards will only allow to set up AP without
   authentication or encryption or using the WEP protocol.

   The wireless device can now be put into hostap mode and configured
   with the correct SSID and IP address:

 # ifconfig ath0 ssid freebsdap wepmode on weptxkey 3 wepkey 3:0x3456789012 mode 11g mediaopt hostap \
         inet 192.168.0.1 netmask 255.255.255.0

     * The weptxkey means which WEP key will be used in the
       transmission. Here we used the third key (note that the key
       numbering starts with 1). This parameter must be specified to
       really encrypt the data.

     * The wepkey means setting the selected WEP key. It should in
       the format index:key, if the index is not given, key 1 is set.
       That is to say we need to set the index if we use keys other
       than the first key.

   Use again ifconfig to see the status of the ath0 interface:

 # ifconfig ath0
   ath0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
           inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255
           inet6 fe80::211:95ff:fec3:dac%ath0 prefixlen 64 scopeid 0x4
           ether 00:11:95:c3:0d:ac
           media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
           status: associated
           ssid freebsdap channel 1 bssid 00:11:95:c3:0d:ac
           authmode OPEN privacy ON deftxkey 3 wepkey 3:40-bit txpowmax 36 protmode CTS dtimperiod 1 bintval 100

   From another wireless machine, it is possible to initiate a scan
   to find the AP:

 # ifconfig ath0 up scan
 SSID            BSSID              CHAN RATE  S:N   INT CAPS
 freebsdap       00:11:95:c3:0d:ac    1   54M 22:1   100 EPS

   The client machine found the Access Point and can be associated
   with it using the correct parameters (key, etc.), see uU
   29.3.3.1.4 ,` for more details.

     --------------------------------------------------------------

  29.3.6. Troubleshooting

   If you are having trouble with wireless networking, there are a
   number of steps you can take to help troubleshoot the problem.

     * If you do not see the access point listed when scanning be
       sure you have not configured your wireless device to a limited
       set of channels.

     * If you cannot associate to an access point verify the
       configuration of your station matches the one of the access
       point. This includes the authentication scheme and any
       security protocols. Simplify your configuration as much as
       possible. If you are using a security protocol such as WPA or
       WEP configure the access point for open authentication and no
       security to see if you can get traffic to pass.

     * Once you can associate to the access point diagnose any
       security configuration using simple tools like ping(8).

       The wpa_supplicant has much debugging support; try running it
       manually with the -dd option and look at the system logs.

     * There are also many lower-level debugging tools. You can
       enable debugging messages in the 802.11 protocol support layer
       using the wlandebug program found in
       /usr/src/tools/tools/net80211. For example:

 # wlandebug -i ath0 +scan+auth+debug+assoc
   net.wlan.0.debug: 0 => 0xc80000<assoc,auth,scan>

       can be used to enable console messages related to scanning for
       access points and doing the 802.11 protocol handshakes
       required to arrange communication.

       There are also many useful statistics maintained by the 802.11
       layer; the wlanstats tool will dump these informations. These
       statistics should identify all errors identified by the 802.11
       layer. Beware however that some errors are identified in the
       device drivers that lie below the 802.11 layer so they may not
       show up. To diagnose device-specific problems you need to
       refer to the drivers' documentation.

   If the above information does not help to clarify the problem,
   please submit a problem report and include output from the above
   tools.

     --------------------------------------------------------------

29.4. Bluetooth

   Written by Pav Lucistnik.

     --------------------------------------------------------------

  29.4.1. Introduction

   Bluetooth is a wireless technology for creating personal networks
   operating in the 2.4 GHz unlicensed band, with a range of 10
   meters. Networks are usually formed ad-hoc from portable devices
   such as cellular phones, handhelds and laptops. Unlike the other
   popular wireless technology, Wi-Fi, Bluetooth offers higher level
   service profiles, e.g. FTP-like file servers, file pushing, voice
   transport, serial line emulation, and more.

   The Bluetooth stack in FreeBSD is implemented using the Netgraph
   framework (see netgraph(4)). A broad variety of Bluetooth USB
   dongles is supported by the ng_ubt(4) driver. The Broadcom BCM2033
   chip based Bluetooth devices are supported via the ubtbcmfw(4) and
   ng_ubt(4) drivers. The 3Com Bluetooth PC Card 3CRWB60-A is
   supported by the ng_bt3c(4) driver. Serial and UART based
   Bluetooth devices are supported via sio(4), ng_h4(4) and
   hcseriald(8). This section describes the use of the USB Bluetooth
   dongle.

     --------------------------------------------------------------

  29.4.2. Plugging in the Device

   By default Bluetooth device drivers are available as kernel
   modules. Before attaching a device, you will need to load the
   driver into the kernel:

 # kldload ng_ubt

   If the Bluetooth device is present in the system during system
   startup, load the module from /boot/loader.conf:

 ng_ubt_load="YES"

   Plug in your USB dongle. The output similar to the following will
   appear on the console (or in syslog):

 ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2
 ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82, bulk-out=0x2
 ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83, isoc-out=0x3,
       wMaxPacketSize=49, nframes=6, buffer size=294

     -a`: The Bluetooth stack has to be started manually on FreeBSD
     6.0, and on FreeBSD 5.X before 5.5. It is done automatically
     from devd(8) on FreeBSD 5.5, 6.1 and newer.

     Copy /usr/share/examples/netgraph/bluetooth/rc.bluetooth into
     some convenient place, like /etc/rc.bluetooth. This script is
     used to start and stop the Bluetooth stack. It is a good idea to
     stop the stack before unplugging the device, but it is not
     (usually) fatal. When starting the stack, you will receive
     output similar to the following:

 # /etc/rc.bluetooth start ubt0
 BD_ADDR: 00:02:72:00:d4:1a
 Features: 0xff 0xff 0xf 00 00 00 00 00
 <3-Slot> <5-Slot> <Encryption> <Slot offset>
 <Timing accuracy> <Switch> <Hold mode> <Sniff mode>
 <Park mode> <RSSI> <Channel quality> <SCO link>
 <HV2 packets> <HV3 packets> <u-law log> <A-law log> <CVSD>
 <Paging scheme> <Power control> <Transparent SCO data>
 Max. ACL packet size: 192 bytes
 Number of ACL packets: 8
 Max. SCO packet size: 64 bytes
 Number of SCO packets: 8

     --------------------------------------------------------------

  29.4.3. Host Controller Interface (HCI)

   Host Controller Interface (HCI) provides a command interface to
   the baseband controller and link manager, and access to hardware
   status and control registers. This interface provides a uniform
   method of accessing the Bluetooth baseband capabilities. HCI layer
   on the Host exchanges data and commands with the HCI firmware on
   the Bluetooth hardware. The Host Controller Transport Layer (i.e.
   physical bus) driver provides both HCI layers with the ability to
   exchange information with each other.

   A single Netgraph node of type hci is created for a single
   Bluetooth device. The HCI node is normally connected to the
   Bluetooth device driver node (downstream) and the L2CAP node
   (upstream). All HCI operations must be performed on the HCI node
   and not on the device driver node. Default name for the HCI node
   is !S:devicehci!". For more details refer to the ng_hci(4) manual
   page.

   One of the most common tasks is discovery of Bluetooth devices in
   RF proximity. This operation is called inquiry. Inquiry and other
   HCI related operations are done with the hccontrol(8) utility. The
   example below shows how to find out which Bluetooth devices are in
   range. You should receive the list of devices in a few seconds.
   Note that a remote device will only answer the inquiry if it put
   into discoverable mode.

 % hccontrol -n ubt0hci inquiry
 Inquiry result, num_responses=1
 Inquiry result #0
        BD_ADDR: 00:80:37:29:19:a4
        Page Scan Rep. Mode: 0x1
        Page Scan Period Mode: 00
        Page Scan Mode: 00
        Class: 52:02:04
        Clock offset: 0x78ef
 Inquiry complete. Status: No error [00]

   BD_ADDR is unique address of a Bluetooth device, similar to MAC
   addresses of a network card. This address is needed for further
   communication with a device. It is possible to assign human
   readable name to a BD_ADDR. The /etc/bluetooth/hosts file contains
   information regarding the known Bluetooth hosts. The following
   example shows how to obtain human readable name that was assigned
   to the remote device:

 % hccontrol -n ubt0hci remote_name_request 00:80:37:29:19:a4
 BD_ADDR: 00:80:37:29:19:a4
 Name: Pav's T39

   If you perform an inquiry on a remote Bluetooth device, it will
   find your computer as !S:your.host.name (ubt0)!". The name
   assigned to the local device can be changed at any time.

   The Bluetooth system provides a point-to-point connection (only
   two Bluetooth units involved), or a point-to-multipoint
   connection. In the point-to-multipoint connection the connection
   is shared among several Bluetooth devices. The following example
   shows how to obtain the list of active baseband connections for
   the local device:

 % hccontrol -n ubt0hci read_connection_list
 Remote BD_ADDR    Handle Type Mode Role Encrypt Pending Queue State
 00:80:37:29:19:a4     41  ACL    0 MAST    NONE       0     0 OPEN

   A connection handle is useful when termination of the baseband
   connection is required. Note, that it is normally not required to
   do it by hand. The stack will automatically terminate inactive
   baseband connections.

 # hccontrol -n ubt0hci disconnect 41
 Connection handle: 41
 Reason: Connection terminated by local host [0x16]

   Refer to hccontrol help for a complete listing of available HCI
   commands. Most of the HCI commands do not require superuser
   privileges.

     --------------------------------------------------------------

  29.4.4. Logical Link Control and Adaptation Protocol (L2CAP)

   Logical Link Control and Adaptation Protocol (L2CAP) provides
   connection-oriented and connectionless data services to upper
   layer protocols with protocol multiplexing capability and
   segmentation and reassembly operation. L2CAP permits higher level
   protocols and applications to transmit and receive L2CAP data
   packets up to 64 kilobytes in length.

   L2CAP is based around the concept of channels. Channel is a
   logical connection on top of baseband connection. Each channel is
   bound to a single protocol in a many-to-one fashion. Multiple
   channels can be bound to the same protocol, but a channel cannot
   be bound to multiple protocols. Each L2CAP packet received on a
   channel is directed to the appropriate higher level protocol.
   Multiple channels can share the same baseband connection.

   A single Netgraph node of type l2cap is created for a single
   Bluetooth device. The L2CAP node is normally connected to the
   Bluetooth HCI node (downstream) and Bluetooth sockets nodes
   (upstream). Default name for the L2CAP node is !S:devicel2cap!".
   For more details refer to the ng_l2cap(4) manual page.

   A useful command is l2ping(8), which can be used to ping other
   devices. Some Bluetooth implementations might not return all of
   the data sent to them, so 0 bytes in the following example is
   normal.

 # l2ping -a 00:80:37:29:19:a4
 0 bytes from 0:80:37:29:19:a4 seq_no=0 time=48.633 ms result=0
 0 bytes from 0:80:37:29:19:a4 seq_no=1 time=37.551 ms result=0
 0 bytes from 0:80:37:29:19:a4 seq_no=2 time=28.324 ms result=0
 0 bytes from 0:80:37:29:19:a4 seq_no=3 time=46.150 ms result=0

   The l2control(8) utility is used to perform various operations on
   L2CAP nodes. This example shows how to obtain the list of logical
   connections (channels) and the list of baseband connections for
   the local device:

 % l2control -a 00:02:72:00:d4:1a read_channel_list
 L2CAP channels:
 Remote BD_ADDR     SCID/ DCID   PSM  IMTU/ OMTU State
 00:07:e0:00:0b:ca    66/   64     3   132/  672 OPEN
 % l2control -a 00:02:72:00:d4:1a read_connection_list
 L2CAP connections:
 Remote BD_ADDR    Handle Flags Pending State
 00:07:e0:00:0b:ca     41 O           0 OPEN

   Another diagnostic tool is btsockstat(1). It does a job similar to
   as netstat(1) does, but for Bluetooth network-related data
   structures. The example below shows the same logical connection as
   l2control(8) above.

 % btsockstat
 Active L2CAP sockets
 PCB      Recv-Q Send-Q Local address/PSM       Foreign address   CID   State
 c2afe900      0      0 00:02:72:00:d4:1a/3     00:07:e0:00:0b:ca 66    OPEN
 Active RFCOMM sessions
 L2PCB    PCB      Flag MTU   Out-Q DLCs State
 c2afe900 c2b53380 1    127   0     Yes  OPEN
 Active RFCOMM sockets
 PCB      Recv-Q Send-Q Local address     Foreign address   Chan DLCI State
 c2e8bc80      0    250 00:02:72:00:d4:1a 00:07:e0:00:0b:ca 3    6    OPEN

     --------------------------------------------------------------

  29.4.5. RFCOMM Protocol

   The RFCOMM protocol provides emulation of serial ports over the
   L2CAP protocol. The protocol is based on the ETSI standard TS
   07.10. RFCOMM is a simple transport protocol, with additional
   provisions for emulating the 9 circuits of RS-232 (EIATIA-232-E)
   serial ports. The RFCOMM protocol supports up to 60 simultaneous
   connections (RFCOMM channels) between two Bluetooth devices.

   For the purposes of RFCOMM, a complete communication path involves
   two applications running on different devices (the communication
   endpoints) with a communication segment between them. RFCOMM is
   intended to cover applications that make use of the serial ports
   of the devices in which they reside. The communication segment is
   a Bluetooth link from one device to another (direct connect).

   RFCOMM is only concerned with the connection between the devices
   in the direct connect case, or between the device and a modem in
   the network case. RFCOMM can support other configurations, such as
   modules that communicate via Bluetooth wireless technology on one
   side and provide a wired interface on the other side.

   In FreeBSD the RFCOMM protocol is implemented at the Bluetooth
   sockets layer.

     --------------------------------------------------------------

  29.4.6. Pairing of Devices

   By default, Bluetooth communication is not authenticated, and any
   device can talk to any other device. A Bluetooth device (for
   example, cellular phone) may choose to require authentication to
   provide a particular service (for example, Dial-Up service).
   Bluetooth authentication is normally done with PIN codes. A PIN
   code is an ASCII string up to 16 characters in length. User is
   required to enter the same PIN code on both devices. Once user has
   entered the PIN code, both devices will generate a link key. After
   that the link key can be stored either in the devices themselves
   or in a persistent storage. Next time both devices will use
   previously generated link key. The described above procedure is
   called pairing. Note that if the link key is lost by any device
   then pairing must be repeated.

   The hcsecd(8) daemon is responsible for handling of all Bluetooth
   authentication requests. The default configuration file is
   /etc/bluetooth/hcsecd.conf. An example section for a cellular
   phone with the PIN code arbitrarily set to !S:1234!" is shown
   below:

 device {
         bdaddr  00:80:37:29:19:a4;
         name    "Pav's T39";
         key     nokey;
         pin     "1234";
       }

   There is no limitation on PIN codes (except length). Some devices
   (for example Bluetooth headsets) may have a fixed PIN code built
   in. The -d switch forces the hcsecd(8) daemon to stay in the
   foreground, so it is easy to see what is happening. Set the remote
   device to receive pairing and initiate the Bluetooth connection to
   the remote device. The remote device should say that pairing was
   accepted, and request the PIN code. Enter the same PIN code as you
   have in hcsecd.conf. Now your PC and the remote device are paired.
   Alternatively, you can initiate pairing on the remote device.

   On FreeBSD 5.5, 6.1 and newer, the following line can be added to
   the /etc/rc.conf file to have hcsecd started automatically on
   system start:

 hcsecd_enable="YES"

   The following is a sample of the hcsecd daemon output:

 hcsecd[16484]: Got Link_Key_Request event from 'ubt0hci', remote bdaddr 0:80:37:29:19:a4
 hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's T39', link key doesn't exist
 hcsecd[16484]: Sending Link_Key_Negative_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4
 hcsecd[16484]: Got PIN_Code_Request event from 'ubt0hci', remote bdaddr 0:80:37:29:19:a4
 hcsecd[16484]: Found matching entry, remote bdaddr 0:80:37:29:19:a4, name 'Pav's T39', PIN code exists
 hcsecd[16484]: Sending PIN_Code_Reply to 'ubt0hci' for remote bdaddr 0:80:37:29:19:a4

     --------------------------------------------------------------

  29.4.7. Service Discovery Protocol (SDP)

   The Service Discovery Protocol (SDP) provides the means for client
   applications to discover the existence of services provided by
   server applications as well as the attributes of those services.
   The attributes of a service include the type or class of service
   offered and the mechanism or protocol information needed to
   utilize the service.

   SDP involves communication between a SDP server and a SDP client.
   The server maintains a list of service records that describe the
   characteristics of services associated with the server. Each
   service record contains information about a single service. A
   client may retrieve information from a service record maintained
   by the SDP server by issuing a SDP request. If the client, or an
   application associated with the client, decides to use a service,
   it must open a separate connection to the service provider in
   order to utilize the service. SDP provides a mechanism for
   discovering services and their attributes, but it does not provide
   a mechanism for utilizing those services.

   Normally, a SDP client searches for services based on some desired
   characteristics of the services. However, there are times when it
   is desirable to discover which types of services are described by
   an SDP server's service records without any a priori information
   about the services. This process of looking for any offered
   services is called browsing.

   The Bluetooth SDP server sdpd(8) and command line client
   sdpcontrol(8) are included in the standard FreeBSD installation.
   The following example shows how to perform a SDP browse query.

 % sdpcontrol -a 00:01:03:fc:6e:ec browse
 Record Handle: 00000000
 Service Class ID List:
         Service Discovery Server (0x1000)
 Protocol Descriptor List:
         L2CAP (0x0100)
                 Protocol specific parameter #1: u/int/uuid16 1
                 Protocol specific parameter #2: u/int/uuid16 1

 Record Handle: 0x00000001
 Service Class ID List:
         Browse Group Descriptor (0x1001)

 Record Handle: 0x00000002
 Service Class ID List:
         LAN Access Using PPP (0x1102)
 Protocol Descriptor List:
         L2CAP (0x0100)
         RFCOMM (0x0003)
                 Protocol specific parameter #1: u/int8/bool 1
 Bluetooth Profile Descriptor List:
         LAN Access Using PPP (0x1102) ver. 1.0

   ... and so on. Note that each service has a list of attributes
   (RFCOMM channel for example). Depending on the service you might
   need to make a note of some of the attributes. Some Bluetooth
   implementations do not support service browsing and may return an
   empty list. In this case it is possible to search for the specific
   service. The example below shows how to search for the OBEX Object
   Push (OPUSH) service:

 % sdpcontrol -a 00:01:03:fc:6e:ec search OPUSH

   Offering services on FreeBSD to Bluetooth clients is done with the
   sdpd(8) server. On FreeBSD 5.5, 6.1 and newer, the following line
   can be added to the /etc/rc.conf file:

 sdpd_enable="YES"

   Then the sdpd daemon can be started with:

 # /etc/rc.d/sdpd start

   On FreeBSD 6.0, and on FreeBSD 5.X before 5.5, sdpd is not
   integrated into the system startup scripts. It has to be started
   manually with:

 # sdpd

   The local server application that wants to provide Bluetooth
   service to the remote clients will register service with the local
   SDP daemon. The example of such application is rfcomm_pppd(8).
   Once started it will register Bluetooth LAN service with the local
   SDP daemon.

   The list of services registered with the local SDP server can be
   obtained by issuing SDP browse query via local control channel:

 # sdpcontrol -l browse

     --------------------------------------------------------------

  29.4.8. Dial-Up Networking (DUN) and Network Access with PPP (LAN)
  Profiles

   The Dial-Up Networking (DUN) profile is mostly used with modems
   and cellular phones. The scenarios covered by this profile are the
   following:

     * use of a cellular phone or modem by a computer as a wireless
       modem for connecting to a dial-up Internet access server, or
       using other dial-up services;

     * use of a cellular phone or modem by a computer to receive data
       calls.

   Network Access with PPP (LAN) profile can be used in the following
   situations:

     * LAN access for a single Bluetooth device;

     * LAN access for multiple Bluetooth devices;

     * PC to PC (using PPP networking over serial cable emulation).

   In FreeBSD both profiles are implemented with ppp(8) and
   rfcomm_pppd(8) - a wrapper that converts RFCOMM Bluetooth
   connection into something PPP can operate with. Before any profile
   can be used, a new PPP label in the /etc/ppp/ppp.conf must be
   created. Consult rfcomm_pppd(8) manual page for examples.

   In the following example rfcomm_pppd(8) will be used to open
   RFCOMM connection to remote device with BD_ADDR 00:80:37:29:19:a4
   on DUN RFCOMM channel. The actual RFCOMM channel number will be
   obtained from the remote device via SDP. It is possible to specify
   RFCOMM channel by hand, and in this case rfcomm_pppd(8) will not
   perform SDP query. Use sdpcontrol(8) to find out RFCOMM channel on
   the remote device.

 # rfcomm_pppd -a 00:80:37:29:19:a4 -c -C dun -l rfcomm-dialup

   In order to provide Network Access with PPP (LAN) service the
   sdpd(8) server must be running. A new entry for LAN clients must
   be created in the /etc/ppp/ppp.conf file. Consult rfcomm_pppd(8)
   manual page for examples. Finally, start RFCOMM PPP server on
   valid RFCOMM channel number. The RFCOMM PPP server will
   automatically register Bluetooth LAN service with the local SDP
   daemon. The example below shows how to start RFCOMM PPP server.

 # rfcomm_pppd -s -C 7 -l rfcomm-server

     --------------------------------------------------------------

  29.4.9. OBEX Object Push (OPUSH) Profile

   OBEX is a widely used protocol for simple file transfers between
   mobile devices. Its main use is in infrared communication, where
   it is used for generic file transfers between notebooks or PDAs,
   and for sending business cards or calendar entries between
   cellular phones and other devices with PIM applications.

   The OBEX server and client are implemented as a third-party
   package obexapp, which is available as comms/obexapp port.

   OBEX client is used to push and/or pull objects from the OBEX
   server. An object can, for example, be a business card or an
   appointment. The OBEX client can obtain RFCOMM channel number from
   the remote device via SDP. This can be done by specifying service
   name instead of RFCOMM channel number. Supported service names
   are: IrMC, FTRN and OPUSH. It is possible to specify RFCOMM
   channel as a number. Below is an example of an OBEX session, where
   device information object is pulled from the cellular phone, and a
   new object (business card) is pushed into the phone's directory.

 % obexapp -a 00:80:37:29:19:a4 -C IrMC
 obex> get telecom/devinfo.txt devinfo-t39.txt
 Success, response: OK, Success (0x20)
 obex> put new.vcf
 Success, response: OK, Success (0x20)
 obex> di
 Success, response: OK, Success (0x20)

   In order to provide OBEX Object Push service, sdpd(8) server must
   be running. A root folder, where all incoming objects will be
   stored, must be created. The default path to the root folder is
   /var/spool/obex. Finally, start OBEX server on valid RFCOMM
   channel number. The OBEX server will automatically register OBEX
   Object Push service with the local SDP daemon. The example below
   shows how to start OBEX server.

 # obexapp -s -C 10

     --------------------------------------------------------------

  29.4.10. Serial Port Profile (SPP)

   The Serial Port Profile (SPP) allows Bluetooth devices to perform
   RS232 (or similar) serial cable emulation. The scenario covered by
   this profile deals with legacy applications using Bluetooth as a
   cable replacement, through a virtual serial port abstraction.

   The rfcomm_sppd(1) utility implements the Serial Port profile. A
   pseudo tty is used as a virtual serial port abstraction. The
   example below shows how to connect to a remote device Serial Port
   service. Note that you do not have to specify a RFCOMM channel -
   rfcomm_sppd(1) can obtain it from the remote device via SDP. If
   you would like to override this, specify a RFCOMM channel on the
   command line.

 # rfcomm_sppd -a 00:07:E0:00:0B:CA -t /dev/ttyp6
 rfcomm_sppd[94692]: Starting on /dev/ttyp6...

   Once connected, the pseudo tty can be used as serial port:

 # cu -l ttyp6

     --------------------------------------------------------------

  29.4.11. Troubleshooting

    29.4.11.1. A remote device cannot connect

   Some older Bluetooth devices do not support role switching. By
   default, when FreeBSD is accepting a new connection, it tries to
   perform a role switch and become master. Devices, which do not
   support this will not be able to connect. Note that role switching
   is performed when a new connection is being established, so it is
   not possible to ask the remote device if it does support role
   switching. There is a HCI option to disable role switching on the
   local side:

 # hccontrol -n ubt0hci write_node_role_switch 0

     --------------------------------------------------------------

    29.4.11.2. Something is going wrong, can I see what exactly is
    happening?

   Yes, you can. Use the third-party package hcidump, which is
   available as comms/hcidump port. The hcidump utility is similar to
   tcpdump(1). It can be used to display the content of the Bluetooth
   packets on the terminal and to dump the Bluetooth packets to a
   file.

     --------------------------------------------------------------

29.5. Bridging

   Written by Andrew Thompson.

  29.5.1. Introduction

   It is sometimes useful to divide one physical network (such as an
   Ethernet segment) into two separate network segments without
   having to create IP subnets and use a router to connect the
   segments together. A device that connects two networks together in
   this fashion is called a !S:bridge!". A FreeBSD system with two
   network interface cards can act as a bridge.

   The bridge works by learning the MAC layer addresses (Ethernet
   addresses) of the devices on each of its network interfaces. It
   forwards traffic between two networks only when its source and
   destination are on different networks.

   In many respects, a bridge is like an Ethernet switch with very
   few ports.

     --------------------------------------------------------------

  29.5.2. Situations Where Bridging Is Appropriate

   There are many common situations in which a bridge is used today.

     --------------------------------------------------------------

    29.5.2.1. Connecting Networks

   The basic operation of a bridge is to join two or more network
   segments together. There are many reasons to use a host based
   bridge over plain networking equipment such as cabling
   constraints, firewalling or connecting pseudo networks such as a
   Virtual Machine interface. A bridge can also connect a wireless
   interface running in hostap mode to a wired network and act as an
   access point.

     --------------------------------------------------------------

    29.5.2.2. Filtering/Traffic Shaping Firewall

   A common situation is where firewall functionality is needed
   without routing or network address translation (NAT).

   An example is a small company that is connected via DSL or ISDN to
   their ISP. They have a 13 globally-accessible IP addresses from
   their ISP and have 10 PCs on their network. In this situation,
   using a router-based firewall is difficult because of subnetting
   issues.

   A bridge-based firewall can be configured and dropped into the
   path just downstream of their DSL/ISDN router without any IP
   numbering issues.

     --------------------------------------------------------------

    29.5.2.3. Network Tap

   A bridge can join two network segments and be used to inspect all
   Ethernet frames that pass between them. This can either be from
   using bpf(4)/tcpdump(1) on the bridge interface or by sending a
   copy of all frames out an additional interface (span port).

     --------------------------------------------------------------

    29.5.2.4. Layer 2 VPN

   Two Ethernet networks can be joined across an IP link by bridging
   the networks to an EtherIP tunnel or a tap(4) based solution such
   as OpenVPN.

     --------------------------------------------------------------

    29.5.2.5. Layer 2 Redundancy

   A network can be connected together with multiple links and use
   the Spanning Tree Protocol to block redundant paths. For an
   Ethernet network to function properly only one active path can
   exist between two devices, Spanning Tree will detect loops and put
   the redundant links into a blocked state. Should one of the active
   links fail then the protocol will calculate a different tree and
   reenable one of the blocked paths to restore connectivity to all
   points in the network.

     --------------------------------------------------------------

  29.5.3. Kernel Configuration

   This section covers if_bridge(4) bridge implementation, a netgraph
   bridging driver is also available, for more information see
   ng_bridge(4) manual page.

   The bridge driver is a kernel module and will be automatically
   loaded by ifconfig(8) when creating a bridge interface. It is
   possible to compile the bridge in to the kernel by adding device
   if_bridge to your kernel configuration file.

   Packet filtering can be used with any firewall package that hooks
   in via the pfil(9) framework. The firewall can be loaded as a
   module or compiled into the kernel.

   The bridge can be used as a traffic shaper with altq(4) or
   dummynet(4).

     --------------------------------------------------------------

  29.5.4. Enabling the Bridge

   The bridge is created using interface cloning. To create a bridge
   use ifconfig(8), if the bridge driver is not present in the kernel
   then it will be loaded automatically.

 # ifconfig bridge create
 bridge0
 # ifconfig bridge0
 bridge0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
         ether 96:3d:4b:f1:79:7a
         id 00:00:00:00:00:00 priority 32768 hellotime 2 fwddelay 15
         maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
         root id 00:00:00:00:00:00 priority 0 ifcost 0 port 0

   A bridge interface is created and is automatically assigned a
   randomly generated Ethernet address. The maxaddr and timeout
   parameters control how many MAC addresses the bridge will keep in
   its forwarding table and how many seconds before each entry is
   removed after it is last seen. The other parameters control how
   Spanning Tree operates.

   Add the member network interfaces to the bridge. For the bridge to
   forward packets all member interfaces and the bridge need to be
   up:

 # ifconfig bridge0 addm fxp0 addm fxp1 up
 # ifconfig fxp0 up
 # ifconfig fxp1 up

   The bridge is now forwarding Ethernet frames between fxp0 and
   fxp1. The equivalent configuration in /etc/rc.conf so the bridge
   is created at startup is:

 cloned_interfaces="bridge0"
 ifconfig_bridge0="addm fxp0 addm fxp1 up"
 ifconfig_fxp0="up"
 ifconfig_fxp1="up"

   If the bridge host needs an IP address then the correct place to
   set this is on the bridge interface itself rather than one of the
   member interfaces. This can be set statically or via DHCP:

 # ifconfig bridge0 inet 192.168.0.1/24

   It is also possible to assign an IPv6 address to a bridge
   interface.

     --------------------------------------------------------------

  29.5.5. Firewalling

   When packet filtering is enabled, bridged packets will pass
   through the filter inbound on the originating interface, on the
   bridge interface and outbound on the appropriate interfaces.
   Either stage can be disabled. When direction of the packet flow is
   important it is best to firewall on the member interfaces rather
   than the bridge itself.

   The bridge has several configurable settings for passing non-IP
   and ARP packets, and layer2 firewalling with IPFW. See
   if_bridge(4) for more information.

     --------------------------------------------------------------

  29.5.6. Spanning Tree

   The bridge driver implements the Rapid Spanning Tree Protocol
   (RSTP or 802.1w) with backwards compatibility with the legacy
   Spanning Tree Protocol (STP). Spanning Tree is used to detect and
   remove loops in a network topology. RSTP provides faster Spanning
   Tree convergence than legacy STP, the protocol will exchange
   information with neighbouring switches to quickly transition to
   forwarding without creating loops.

   The following table shows the supported operating modes:

             OS Version               STP Modes       Default Mode    
   FreeBSD 5.4!X!XFreeBSD 6.2      STP              STP               
   FreeBSD 6.3+                    RSTP or STP      STP               
   FreeBSD 7.0+                    RSTP or STP      RSTP              

   Spanning Tree can be enabled on member interfaces using the stp
   command. For a bridge with fxp0 and fxp1 as the current
   interfaces, enable STP with the following:

 # ifconfig bridge0 stp fxp0 stp fxp1
 bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         ether d6:cf:d5:a0:94:6d
         id 00:01:02:4b:d4:50 priority 32768 hellotime 2 fwddelay 15
         maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
         root id 00:01:02:4b:d4:50 priority 32768 ifcost 0 port 0
         member: fxp0 flags=1c7<LEARNING,DISCOVER,STP,AUTOEDGE,PTP,AUTOPTP>
                 port 3 priority 128 path cost 200000 proto rstp
                 role designated state forwarding
         member: fxp1 flags=1c7<LEARNING,DISCOVER,STP,AUTOEDGE,PTP,AUTOPTP>
                 port 4 priority 128 path cost 200000 proto rstp
                 role designated state forwarding

   This bridge has a spanning tree ID of 00:01:02:4b:d4:50 and a
   priority of 32768. As the root id is the same it indicates that
   this is the root bridge for the tree.

   Another bridge on the network also has spanning tree enabled:

 bridge0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         ether 96:3d:4b:f1:79:7a
         id 00:13:d4:9a:06:7a priority 32768 hellotime 2 fwddelay 15
         maxage 20 holdcnt 6 proto rstp maxaddr 100 timeout 1200
         root id 00:01:02:4b:d4:50 priority 32768 ifcost 400000 port 4
         member: fxp0 flags=1c7<LEARNING,DISCOVER,STP,AUTOEDGE,PTP,AUTOPTP>
                 port 4 priority 128 path cost 200000 proto rstp
                 role root state forwarding
         member: fxp1 flags=1c7<LEARNING,DISCOVER,STP,AUTOEDGE,PTP,AUTOPTP>
                 port 5 priority 128 path cost 200000 proto rstp
                 role designated state forwarding

   The line root id 00:01:02:4b:d4:50 priority 32768 ifcost 400000
   port 4 shows that the root bridge is 00:01:02:4b:d4:50 as above
   and has a path cost of 400000 from this bridge, the path to the
   root bridge is via port 4 which is fxp0.

     --------------------------------------------------------------

  29.5.7. Advanced Bridging

    29.5.7.1. Reconstruct Traffic Flows

   The bridge supports monitor mode, where the packets are discarded
   after bpf(4) processing, and are not processed or forwarded
   further. This can be used to multiplex the input of two or more
   interfaces into a single bpf(4) stream. This is useful for
   reconstructing the traffic for network taps that transmit the
   RX/TX signals out through two separate interfaces.

   To read the input from four network interfaces as one stream:

 # ifconfig bridge0 addm fxp0 addm fxp1 addm fxp2 addm fxp3 monitor up
 # tcpdump -i bridge0

     --------------------------------------------------------------

    29.5.7.2. Span Ports

   A copy of every Ethernet frame received by the bridge will be
   transmitted out a designated span port. The number of span ports
   configured on a bridge is unlimited, if an interface is designated
   as a span port then it may not also be used as a regular bridge
   port. This is most useful for snooping a bridged network passively
   on another host connected to one of the span ports of the bridge.

   To send a copy of all frames out the interface named fxp4:

 # ifconfig bridge0 span fxp4

     --------------------------------------------------------------

    29.5.7.3. Private Interfaces

   A private interface does not forward any traffic to any other port
   that is also a private interface. The traffic is blocked
   unconditionally so no Ethernet frames will be forwarded, including
   ARP. If traffic needs to be selectively blocked then a firewall
   should be used instead.

     --------------------------------------------------------------

    29.5.7.4. Sticky Interfaces

   If a bridge member interface is marked as sticky then dynamically
   learned address entries are treated at static once entered into
   the forwarding cache. Sticky entries are never aged out of the
   cache or replaced, even if the address is seen on a different
   interface. This gives the benefit of static address entries
   without the need to pre-populate the forwarding table, clients
   learnt on a particular segment of the bridge can not roam to
   another segment.

   Another example of using sticky addresses would be to combine the
   bridge with VLANs to create a router where customer networks are
   isolated without wasting IP address space. Consider that CustomerA
   is on vlan100 and CustomerB is on vlan101. The bridge has the
   address 192.168.0.1 and is also an internet router.

 # ifconfig bridge0 addm vlan100 sticky vlan100 addm vlan101 sticky vlan101
 # ifconfig bridge0 inet 192.168.0.1/24

   Both clients see 192.168.0.1 as their default gateway and since
   the bridge cache is sticky they can not spoof the MAC address of
   the other customer to intercept their traffic.

   Any communication between the VLANs can be blocked using private
   interfaces (or a firewall):

 # ifconfig bridge0 private vlan100 private vlan101

   The customers are completely isolated from each other, the full
   /24 address range can be allocated without subnetting.

     --------------------------------------------------------------

    29.5.7.5. SNMP Monitoring

   The bridge interface and STP parameters can be monitored via the
   SNMP daemon which is included in the FreeBSD base system. The
   exported bridge MIBs conform to the IETF standards so any SNMP
   client or monitoring package can be used to retrieve the data.

   On the bridge machine uncomment the
   begemotSnmpdModulePath."bridge" = "/usr/lib/snmp_bridge.so" line
   from /etc/snmp.config and start the bsnmpd daemon. Other
   configuration such as community names and access lists may need to
   be modified. See bsnmpd(1) and snmp_bridge(3) for more
   information.

   The following examples use the Net-SNMP software
   (net-mgmt/net-snmp) to query a bridge, the net-mgmt/bsnmptools
   port can also be used. From the SNMP client host add to
   $HOME/.snmp/snmp.conf the following lines to import the bridge MIB
   definitions in to Net-SNMP:

 mibdirs +/usr/share/snmp/mibs
 mibs +BRIDGE-MIB:RSTP-MIB:BEGEMOT-MIB:BEGEMOT-BRIDGE-MIB

   To monitor a single bridge via the IETF BRIDGE-MIB (RFC4188) do

 % snmpwalk -v 2c -c public bridge1.example.com mib-2.dot1dBridge
 BRIDGE-MIB::dot1dBaseBridgeAddress.0 = STRING: 66:fb:9b:6e:5c:44
 BRIDGE-MIB::dot1dBaseNumPorts.0 = INTEGER: 1 ports
 BRIDGE-MIB::dot1dStpTimeSinceTopologyChange.0 = Timeticks: (189959) 0:31:39.59 centi-seconds
 BRIDGE-MIB::dot1dStpTopChanges.0 = Counter32: 2
 BRIDGE-MIB::dot1dStpDesignatedRoot.0 = Hex-STRING: 80 00 00 01 02 4B D4 50
 ...
 BRIDGE-MIB::dot1dStpPortState.3 = INTEGER: forwarding(5)
 BRIDGE-MIB::dot1dStpPortEnable.3 = INTEGER: enabled(1)
 BRIDGE-MIB::dot1dStpPortPathCost.3 = INTEGER: 200000
 BRIDGE-MIB::dot1dStpPortDesignatedRoot.3 = Hex-STRING: 80 00 00 01 02 4B D4 50
 BRIDGE-MIB::dot1dStpPortDesignatedCost.3 = INTEGER: 0
 BRIDGE-MIB::dot1dStpPortDesignatedBridge.3 = Hex-STRING: 80 00 00 01 02 4B D4 50
 BRIDGE-MIB::dot1dStpPortDesignatedPort.3 = Hex-STRING: 03 80
 BRIDGE-MIB::dot1dStpPortForwardTransitions.3 = Counter32: 1
 RSTP-MIB::dot1dStpVersion.0 = INTEGER: rstp(2)

   The dot1dStpTopChanges.0 value is two which means that the STP
   bridge topology has changed twice, a topology change means that
   one or more links in the network have changed or failed and a new
   tree has been calculated. The dot1dStpTimeSinceTopologyChange.0
   value will show when this happened.

   To monitor multiple bridge interfaces one may use the private
   BEGEMOT-BRIDGE-MIB:

 % snmpwalk -v 2c -c public bridge1.example.com
 enterprises.fokus.begemot.begemotBridge
 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseName."bridge0" = STRING: bridge0
 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseName."bridge2" = STRING: bridge2
 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseAddress."bridge0" = STRING: e:ce:3b:5a:9e:13
 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseAddress."bridge2" = STRING: 12:5e:4d:74:d:fc
 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseNumPorts."bridge0" = INTEGER: 1
 BEGEMOT-BRIDGE-MIB::begemotBridgeBaseNumPorts."bridge2" = INTEGER: 1
 ...
 BEGEMOT-BRIDGE-MIB::begemotBridgeStpTimeSinceTopologyChange."bridge0" = Timeticks: (116927) 0:19:29.27 centi-seconds
 BEGEMOT-BRIDGE-MIB::begemotBridgeStpTimeSinceTopologyChange."bridge2" = Timeticks: (82773) 0:13:47.73 centi-seconds
 BEGEMOT-BRIDGE-MIB::begemotBridgeStpTopChanges."bridge0" = Counter32: 1
 BEGEMOT-BRIDGE-MIB::begemotBridgeStpTopChanges."bridge2" = Counter32: 1
 BEGEMOT-BRIDGE-MIB::begemotBridgeStpDesignatedRoot."bridge0" = Hex-STRING: 80 00 00 40 95 30 5E 31
 BEGEMOT-BRIDGE-MIB::begemotBridgeStpDesignatedRoot."bridge2" = Hex-STRING: 80 00 00 50 8B B8 C6 A9

   To change the bridge interface being monitored via the
   mib-2.dot1dBridge subtree do:

 % snmpset -v 2c -c private bridge1.example.com
 BEGEMOT-BRIDGE-MIB::begemotBridgeDefaultBridgeIf.0 s bridge2

     --------------------------------------------------------------

29.6. Link Aggregation and Failover

   Written by Andrew Thompson.

     --------------------------------------------------------------

  29.6.1. Introduction

   The lagg(4) interface allows aggregation of multiple network
   interfaces as one virtual interface for the purpose of providing
   fault-tolerance and high-speed links.

     --------------------------------------------------------------

  29.6.2. Operating Modes

   failover

           Sends and receives traffic only through the master port.
           If the master port becomes unavailable, the next active
           port is used. The first interface added is the master
           port; any interfaces added after that are used as failover
           devices.

   fec

           Supports Cisco EtherChannel. This is a static setup and
           does not negotiate aggregation with the peer or exchange
           frames to monitor the link, if the switch supports LACP
           then that should be used instead.

           Balances outgoing traffic across the active ports based on
           hashed protocol header information and accepts incoming
           traffic from any active port. The hash includes the
           Ethernet source and destination address, and, if
           available, the VLAN tag, and the IPv4/IPv6 source and
           destination address.

   lacp

           Supports the IEEE 802.3ad Link Aggregation Control
           Protocol (LACP) and the Marker Protocol. LACP will
           negotiate a set of aggregable links with the peer in to
           one or more Link Aggregated Groups. Each LAG is composed
           of ports of the same speed, set to full-duplex operation.
           The traffic will be balanced across the ports in the LAG
           with the greatest total speed, in most cases there will
           only be one LAG which contains all ports. In the event of
           changes in physical connectivity, Link Aggregation will
           quickly converge to a new configuration.

           Balances outgoing traffic across the active ports based on
           hashed protocol header information and accepts incoming
           traffic from any active port. The hash includes the
           Ethernet source and destination address, and, if
           available, the VLAN tag, and the IPv4/IPv6 source and
           destination address.

   loadbalance

           This is an alias of fec mode.

   roundrobin

           Distributes outgoing traffic using a round-robin scheduler
           through all active ports and accepts incoming traffic from
           any active port. This mode will violate Ethernet frame
           ordering and should be used with caution.

     --------------------------------------------------------------

  29.6.3. Examples

   1/2d"O 29-1. LACP aggregation with a Cisco switch

   This example connects two interfaces on a FreeBSD machine to the
   switch as a single load balanced and fault tolerant link. More
   interfaces can be added to increase throughput and fault
   tolerance. Since frame ordering is mandatory on Ethernet links
   then any traffic between two stations always flows over the same
   physical link limiting the maximum speed to that of one interface.
   The transmit algorithm attempts to use as much information as it
   can to distinguish different traffic flows and balance across the
   available interfaces.

   On the Cisco switch add the interfaces to the channel group.

 interface FastEthernet0/1
  channel-group 1 mode active
  channel-protocol lacp
 !
 interface FastEthernet0/2
  channel-group 1 mode active
  channel-protocol lacp
 !

   On the FreeBSD machine create the lagg interface.

 # ifconfig lagg0 create
 # ifconfig lagg0 up laggproto lacp laggport fxp0 laggport fxp1

   View the interface status from ifconfig; ports marked as ACTIVE
   are part of the active aggregation group that has been negotiated
   with the remote switch and traffic will be transmitted and
   received. Use the verbose output of ifconfig(8) to view the LAG
   identifiers.

 lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         options=8<VLAN_MTU>
         ether 00:05:5d:71:8d:b8
         media: Ethernet autoselect
         status: active
         laggproto lacp
         laggport: fxp1 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>
         laggport: fxp0 flags=1c<ACTIVE,COLLECTING,DISTRIBUTING>

   The switch will show which ports are active. For more detail use
   show lacp neighbor detail.

 switch# show lacp neighbor
 Flags:  S - Device is requesting Slow LACPDUs
         F - Device is requesting Fast LACPDUs
         A - Device is in Active mode       P - Device is in Passive mode

 Channel group 1 neighbors

 Partner's information:

                   LACP port                        Oper    Port     Port
 Port      Flags   Priority  Dev ID         Age     Key     Number   State
 Fa0/1     SA      32768     0005.5d71.8db8  29s    0x146   0x3      0x3D
 Fa0/2     SA      32768     0005.5d71.8db8  29s    0x146   0x4      0x3D

   1/2d"O 29-2. Failover mode

   Failover mode can be used to switch over to another interface if
   the link is lost on the master.

 # ifconfig lagg0 create
 # ifconfig lagg0 up laggproto failover laggport fxp0 laggport fxp1

 lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
         options=8<VLAN_MTU>
         ether 00:05:5d:71:8d:b8
         media: Ethernet autoselect
         status: active
         laggproto failover
         laggport: fxp1 flags=0<>
         laggport: fxp0 flags=5<MASTER,ACTIVE>

   Traffic will be transmitted and received on fxp0. If the link is
   lost on fxp0 then fxp1 will become the active link. If the link is
   restored on the master interface then it will once again become
   the active link.

     --------------------------------------------------------------

29.7. Diskless Operation

   Updated by Jean-Franc,ois Dockes. Reorganized and enhanced by Alex
   Dupre.

   A FreeBSD machine can boot over the network and operate without a
   local disk, using file systems mounted from an NFS server. No
   system modification is necessary, beyond standard configuration
   files. Such a system is relatively easy to set up because all the
   necessary elements are readily available:

     * There are at least two possible methods to load the kernel
       over the network:

          * PXE: The Intel Preboot eXecution Environment system is a
            form of smart boot ROM built into some networking cards
            or motherboards. See pxeboot(8) for more details.

          * The Etherboot port (net/etherboot) produces ROM-able code
            to boot kernels over the network. The code can be either
            burnt into a boot PROM on a network card, or loaded from
            a local floppy (or hard) disk drive, or from a running
            MS-DOS system. Many network cards are supported.

     * A sample script (/usr/share/examples/diskless/clone_root)
       eases the creation and maintenance of the workstation's root
       file system on the server. The script will probably require a
       little customization but it will get you started very quickly.

     * Standard system startup files exist in /etc to detect and
       support a diskless system startup.

     * Swapping, if needed, can be done either to an NFS file or to a
       local disk.

   There are many ways to set up diskless workstations. Many elements
   are involved, and most can be customized to suit local taste. The
   following will describe variations on the setup of a complete
   system, emphasizing simplicity and compatibility with the standard
   FreeBSD startup scripts. The system described has the following
   characteristics:

     * The diskless workstations use a shared read-only / file
       system, and a shared read-only /usr.

       The root file system is a copy of a standard FreeBSD root
       (typically the server's), with some configuration files
       overridden by ones specific to diskless operation or,
       possibly, to the workstation they belong to.

       The parts of the root which have to be writable are overlaid
       with md(4) file systems. Any changes will be lost when the
       system reboots.

     * The kernel is transferred and loaded either with Etherboot or
       PXE as some situations may mandate the use of either method.

     -a`.NAs described, this system is insecure. It should live in a
     protected area of a network, and be untrusted by other hosts.

   All the information in this section has been tested using FreeBSD
   5.2.1-RELEASE.

     --------------------------------------------------------------

  29.7.1. Background Information

   Setting up diskless workstations is both relatively
   straightforward and prone to errors. These are sometimes difficult
   to diagnose for a number of reasons. For example:

     * Compile time options may determine different behaviors at
       runtime.

     * Error messages are often cryptic or totally absent.

   In this context, having some knowledge of the background
   mechanisms involved is very useful to solve the problems that may
   arise.

   Several operations need to be performed for a successful
   bootstrap:

     * The machine needs to obtain initial parameters such as its IP
       address, executable filename, server name, root path. This is
       done using the DHCP or BOOTP protocols. DHCP is a compatible
       extension of BOOTP, and uses the same port numbers and basic
       packet format.

       It is possible to configure a system to use only BOOTP. The
       bootpd(8) server program is included in the base FreeBSD
       system.

       However, DHCP has a number of advantages over BOOTP (nicer
       configuration files, possibility of using PXE, plus many
       others not directly related to diskless operation), and we
       will describe mainly a DHCP configuration, with equivalent
       examples using bootpd(8) when possible. The sample
       configuration will use the ISC DHCP software package (release
       3.0.1.r12 was installed on the test server).

     * The machine needs to transfer one or several programs to local
       memory. Either TFTP or NFS are used. The choice between TFTP
       and NFS is a compile time option in several places. A common
       source of error is to specify filenames for the wrong
       protocol: TFTP typically transfers all files from a single
       directory on the server, and would expect filenames relative
       to this directory. NFS needs absolute file paths.

     * The possible intermediate bootstrap programs and the kernel
       need to be initialized and executed. There are several
       important variations in this area:

          * PXE will load pxeboot(8), which is a modified version of
            the FreeBSD third stage loader. The loader(8) will obtain
            most parameters necessary to system startup, and leave
            them in the kernel environment before transferring
            control. It is possible to use a GENERIC kernel in this
            case.

          * Etherboot, will directly load the kernel, with less
            preparation. You will need to build a kernel with
            specific options.

       PXE and Etherboot work equally well; however, because kernels
       normally let the loader(8) do more work for them, PXE is the
       preferred method.

       If your BIOS and network cards support PXE, you should
       probably use it.

     * Finally, the machine needs to access its file systems. NFS is
       used in all cases.

   See also diskless(8) manual page.

     --------------------------------------------------------------

  29.7.2. Setup Instructions

    29.7.2.1. Configuration Using ISC DHCP

   The ISC DHCP server can answer both BOOTP and DHCP requests.

   ISC DHCP 3.0 is not part of the base system. You will first need
   to install the net/isc-dhcp3-server port or the corresponding
   package.

   Once ISC DHCP is installed, it needs a configuration file to run
   (normally named /usr/local/etc/dhcpd.conf). Here follows a
   commented example, where host margaux uses Etherboot and host
   corbieres uses PXE:

 default-lease-time 600;
 max-lease-time 7200;
 authoritative;

 option domain-name "example.com";
 option domain-name-servers 192.168.4.1;
 option routers 192.168.4.1;

 subnet 192.168.4.0 netmask 255.255.255.0 {
   use-host-decl-names on; (1)
   option subnet-mask 255.255.255.0;
   option broadcast-address 192.168.4.255;

   host margaux {
     hardware ethernet 01:23:45:67:89:ab;
     fixed-address margaux.example.com;
     next-server 192.168.4.4; (2)
     filename "/data/misc/kernel.diskless"; (3)
     option root-path "192.168.4.4:/data/misc/diskless"; (4)
   }
   host corbieres {
     hardware ethernet 00:02:b3:27:62:df;
     fixed-address corbieres.example.com;
     next-server 192.168.4.4;
     filename "pxeboot";
     option root-path "192.168.4.4:/data/misc/diskless";
   }
 }
          

   (1)
           This option tells dhcpd to send the value in the host
           declarations as the hostname for the diskless host. An
           alternate way would be to add an option host-name margaux
           inside the host declarations.
   (2)
           The next-server directive designates the TFTP or NFS
           server to use for loading loader or kernel file (the
           default is to use the same host as the DHCP server).
   (3)
           The filename directive defines the file that Etherboot or
           PXE will load for the next execution step. It must be
           specified according to the transfer method used. Etherboot
           can be compiled to use NFS or TFTP. The FreeBSD port
           configures NFS by default. PXE uses TFTP, which is why a
           relative filename is used here (this may depend on the
           TFTP server configuration, but would be fairly typical).
           Also, PXE loads pxeboot, not the kernel. There are other
           interesting possibilities, like loading pxeboot from a
           FreeBSD CD-ROM /boot directory (as pxeboot(8) can load a
           GENERIC kernel, this makes it possible to use PXE to boot
           from a remote CD-ROM).
   (4)
           The root-path option defines the path to the root file
           system, in usual NFS notation. When using PXE, it is
           possible to leave off the host's IP as long as you do not
           enable the kernel option BOOTP. The NFS server will then
           be the same as the TFTP one.

     --------------------------------------------------------------

    29.7.2.2. Configuration Using BOOTP

   Here follows an equivalent bootpd configuration (reduced to one
   client). This would be found in /etc/bootptab.

   Please note that Etherboot must be compiled with the non-default
   option NO_DHCP_SUPPORT in order to use BOOTP, and that PXE needs
   DHCP. The only obvious advantage of bootpd is that it exists in
   the base system.

 .def100:\
   :hn:ht=1:sa=192.168.4.4:vm=rfc1048:\
   :sm=255.255.255.0:\
   :ds=192.168.4.1:\
   :gw=192.168.4.1:\
   :hd="/tftpboot":\
   :bf="/kernel.diskless":\
   :rp="192.168.4.4:/data/misc/diskless":

 margaux:ha=0123456789ab:tc=.def100
          

     --------------------------------------------------------------

    29.7.2.3. Preparing a Boot Program with Etherboot

   Etherboot's Web site contains   extensive documentation mainly
   intended for Linux systems, but nonetheless containing useful
   information. The following will just outline how you would use
   Etherboot on a FreeBSD system.

   You must first install the net/etherboot package or port.

   You can change the Etherboot configuration (i.e. to use TFTP
   instead of NFS) by editing the Config file in the Etherboot source
   directory.

   For our setup, we shall use a boot floppy. For other methods
   (PROM, or MS-DOS program), please refer to the Etherboot
   documentation.

   To make a boot floppy, insert a floppy in the drive on the machine
   where you installed Etherboot, then change your current directory
   to the src directory in the Etherboot tree and type:

 # gmake bin32/devicetype.fd0
        

   devicetype depends on the type of the Ethernet card in the
   diskless workstation. Refer to the NIC file in the same directory
   to determine the right devicetype.

     --------------------------------------------------------------

    29.7.2.4. Booting with PXE

   By default, the pxeboot(8) loader loads the kernel via NFS. It can
   be compiled to use TFTP instead by specifying the
   LOADER_TFTP_SUPPORT option in /etc/make.conf. See the comments in
   /usr/share/examples/etc/make.conf for instructions.

   There are two other make.conf options which may be useful for
   setting up a serial console diskless machine:
   BOOT_PXELDR_PROBE_KEYBOARD, and BOOT_PXELDR_ALWAYS_SERIAL.

   To use PXE when the machine starts, you will usually need to
   select the Boot from network option in your BIOS setup, or type a
   function key during the PC initialization.

     --------------------------------------------------------------

    29.7.2.5. Configuring the TFTP and NFS Servers

   If you are using PXE or Etherboot configured to use TFTP, you need
   to enable tftpd on the file server:

    1. Create a directory from which tftpd will serve the files, e.g.
       /tftpboot.

    2. Add this line to your /etc/inetd.conf:

 tftp    dgram   udp     wait    root    /usr/libexec/tftpd      tftpd -l -s /tftpboot

         -a`: It appears that at least some PXE versions want the TCP
         version of TFTP. In this case, add a second line, replacing
         dgram udp with stream tcp.

    3. Tell inetd to reread its configuration file. The
       inetd_enable="YES" must be in the /etc/rc.conf file for this
       command to execute correctly:

 # /etc/rc.d/inetd restart

   You can place the tftpboot directory anywhere on the server. Make
   sure that the location is set in both inetd.conf and dhcpd.conf.

   In all cases, you also need to enable NFS and export the
   appropriate file system on the NFS server.

    1. Add this to /etc/rc.conf:

 nfs_server_enable="YES"

    2. Export the file system where the diskless root directory is
       located by adding the following to /etc/exports (adjust the
       volume mount point and replace margaux corbieres with the
       names of the diskless workstations):

 /data/misc -alldirs -ro margaux corbieres

    3. Tell mountd to reread its configuration file. If you actually
       needed to enable NFS in /etc/rc.conf at the first step, you
       probably want to reboot instead.

 # /etc/rc.d/mountd restart

     --------------------------------------------------------------

    29.7.2.6. Building a Diskless Kernel

   If using Etherboot, you need to create a kernel configuration file
   for the diskless client with the following options (in addition to
   the usual ones):

 options     BOOTP          # Use BOOTP to obtain IP address/hostname
 options     BOOTP_NFSROOT  # NFS mount root file system using BOOTP info
        

   You may also want to use BOOTP_NFSV3, BOOT_COMPAT and
   BOOTP_WIRED_TO (refer to NOTES).

   These option names are historical and slightly misleading as they
   actually enable indifferent use of DHCP and BOOTP inside the
   kernel (it is also possible to force strict BOOTP or DHCP use).

   Build the kernel (see uU 8 ^3^1), and copy it to the place
   specified in dhcpd.conf.

     -a`: When using PXE, building a kernel with the above options is
     not strictly necessary (though suggested). Enabling them will
     cause more DHCP requests to be issued during kernel startup,
     with a small risk of inconsistency between the new values and
     those retrieved by pxeboot(8) in some special cases. The
     advantage of using them is that the host name will be set as a
     side effect. Otherwise you will need to set the host name by
     another method, for example in a client-specific rc.conf file.

     -a`: In order to be loadable with Etherboot, a kernel needs to
     have the device hints compiled in. You would typically set the
     following option in the configuration file (see the NOTES
     configuration comments file):

 hints           "GENERIC.hints"

     --------------------------------------------------------------

    29.7.2.7. Preparing the Root Filesystem

   You need to create a root file system for the diskless
   workstations, in the location listed as root-path in dhcpd.conf.

     --------------------------------------------------------------

      29.7.2.7.1. Using make world to populate root

   This method is quick and will install a complete virgin system
   (not only the root file system) into DESTDIR. All you have to do
   is simply execute the following script:

 #!/bin/sh
 export DESTDIR=/data/misc/diskless
 mkdir -p ${DESTDIR}
 cd /usr/src; make buildworld && make buildkernel
 cd /usr/src/etc; make distribution

   Once done, you may need to customize your /etc/rc.conf and
   /etc/fstab placed into DESTDIR according to your needs.

     --------------------------------------------------------------

    29.7.2.8. Configuring Swap

   If needed, a swap file located on the server can be accessed via
   NFS.

     --------------------------------------------------------------

      29.7.2.8.1. NFS Swap

   The kernel does not support enabling NFS swap at boot time. Swap
   must be enabled by the startup scripts, by mounting a writable
   file system and creating and enabling a swap file. To create a
   swap file of appropriate size, you can do like this:

 # dd if=/dev/zero of=/path/to/swapfile bs=1k count=1 oseek=100000

   To enable it you have to add the following line to your rc.conf:

 swapfile=/path/to/swapfile

     --------------------------------------------------------------

    29.7.2.9. Miscellaneous Issues

      29.7.2.9.1. Running with a Read-only /usr

   If the diskless workstation is configured to run X, you will have
   to adjust the XDM configuration file, which puts the error log on
   /usr by default.

     --------------------------------------------------------------

      29.7.2.9.2. Using a Non-FreeBSD Server

   When the server for the root file system is not running FreeBSD,
   you will have to create the root file system on a FreeBSD machine,
   then copy it to its destination, using tar or cpio.

   In this situation, there are sometimes problems with the special
   files in /dev, due to differing major/minor integer sizes. A
   solution to this problem is to export a directory from the
   non-FreeBSD server, mount this directory onto a FreeBSD machine,
   and use devfs(5) to allocate device nodes transparently for the
   user.

     --------------------------------------------------------------

29.8. ISDN

   A good resource for information on ISDN technology and hardware is
   Dan Kegel's ISDN Page.

   A quick simple road map to ISDN follows:

     * If you live in Europe you might want to investigate the ISDN
       card section.

     * If you are planning to use ISDN primarily to connect to the
       Internet with an Internet Provider on a dial-up non-dedicated
       basis, you might look into Terminal Adapters. This will give
       you the most flexibility, with the fewest problems, if you
       change providers.

     * If you are connecting two LANs together, or connecting to the
       Internet with a dedicated ISDN connection, you might consider
       the stand alone router/bridge option.

   Cost is a significant factor in determining what solution you will
   choose. The following options are listed from least expensive to
   most expensive.

     --------------------------------------------------------------

  29.8.1. ISDN Cards

   Contributed by Hellmuth Michaelis.

   FreeBSD's ISDN implementation supports only the DSS1/Q.931 (or
   Euro-ISDN) standard using passive cards. Some active cards are
   supported where the firmware also supports other signaling
   protocols; this also includes the first supported Primary Rate
   (PRI) ISDN card.

   The isdn4bsd software allows you to connect to other ISDN routers
   using either IP over raw HDLC or by using synchronous PPP: either
   by using kernel PPP with isppp, a modified sppp(4) driver, or by
   using userland ppp(8). By using userland ppp(8), channel bonding
   of two or more ISDN B-channels is possible. A telephone answering
   machine application is also available as well as many utilities
   such as a software 300 Baud modem.

   Some growing number of PC ISDN cards are supported under FreeBSD
   and the reports show that it is successfully used all over Europe
   and in many other parts of the world.

   The passive ISDN cards supported are mostly the ones with the
   Infineon (formerly Siemens) ISAC/HSCX/IPAC ISDN chipsets, but also
   ISDN cards with chips from Cologne Chip (ISA bus only), PCI cards
   with Winbond W6692 chips, some cards with the Tiger300/320/ISAC
   chipset combinations and some vendor specific chipset based cards
   such as the AVM Fritz!Card PCI V.1.0 and the AVM Fritz!Card PnP.

   Currently the active supported ISDN cards are the AVM B1 (ISA and
   PCI) BRI cards and the AVM T1 PCI PRI cards.

   For documentation on isdn4bsd, have a look at
   /usr/share/examples/isdn/ directory on your FreeBSD system or at
   the homepage of isdn4bsd which also has pointers to hints, erratas
   and much more documentation such as the isdn4bsd handbook.

   In case you are interested in adding support for a different ISDN
   protocol, a currently unsupported ISDN PC card or otherwise
   enhancing isdn4bsd, please get in touch with Hellmuth Michaelis
   <hm@FreeBSD.org>.

   For questions regarding the installation, configuration and
   troubleshooting isdn4bsd, a freebsd-isdn mailing list is
   available.

     --------------------------------------------------------------

  29.8.2. ISDN Terminal Adapters

   Terminal adapters (TA), are to ISDN what modems are to regular
   phone lines.

   Most TA's use the standard Hayes modem AT command set, and can be
   used as a drop in replacement for a modem.

   A TA will operate basically the same as a modem except connection
   and throughput speeds will be much faster than your old modem. You
   will need to configure PPP exactly the same as for a modem setup.
   Make sure you set your serial speed as high as possible.

   The main advantage of using a TA to connect to an Internet
   Provider is that you can do Dynamic PPP. As IP address space
   becomes more and more scarce, most providers are not willing to
   provide you with a static IP anymore. Most stand-alone routers are
   not able to accommodate dynamic IP allocation.

   TA's completely rely on the PPP daemon that you are running for
   their features and stability of connection. This allows you to
   upgrade easily from using a modem to ISDN on a FreeBSD machine, if
   you already have PPP set up. However, at the same time any
   problems you experienced with the PPP program and are going to
   persist.

   If you want maximum stability, use the kernel PPP option, not the
   userland PPP.

   The following TA's are known to work with FreeBSD:

     * Motorola BitSurfer and Bitsurfer Pro

     * Adtran

   Most other TA's will probably work as well, TA vendors try to make
   sure their product can accept most of the standard modem AT
   command set.

   The real problem with external TA's is that, like modems, you need
   a good serial card in your computer.

   You should read the FreeBSD Serial Hardware tutorial for a
   detailed understanding of serial devices, and the differences
   between asynchronous and synchronous serial ports.

   A TA running off a standard PC serial port (asynchronous) limits
   you to 115.2 Kbs, even though you have a 128 Kbs connection. To
   fully utilize the 128 Kbs that ISDN is capable of, you must move
   the TA to a synchronous serial card.

   Do not be fooled into buying an internal TA and thinking you have
   avoided the synchronous/asynchronous issue. Internal TA's simply
   have a standard PC serial port chip built into them. All this will
   do is save you having to buy another serial cable and find another
   empty electrical socket.

   A synchronous card with a TA is at least as fast as a stand-alone
   router, and with a simple 386 FreeBSD box driving it, probably
   more flexible.

   The choice of synchronous card/TA v.s. stand-alone router is
   largely a religious issue. There has been some discussion of this
   in the mailing lists. We suggest you search the archives for the
   complete discussion.

     --------------------------------------------------------------

  29.8.3. Stand-alone ISDN Bridges/Routers

   ISDN bridges or routers are not at all specific to FreeBSD or any
   other operating system. For a more complete description of routing
   and bridging technology, please refer to a networking reference
   book.

   In the context of this section, the terms router and bridge will
   be used interchangeably.

   As the cost of low end ISDN routers/bridges comes down, it will
   likely become a more and more popular choice. An ISDN router is a
   small box that plugs directly into your local Ethernet network,
   and manages its own connection to the other bridge/router. It has
   built in software to communicate via PPP and other popular
   protocols.

   A router will allow you much faster throughput than a standard TA,
   since it will be using a full synchronous ISDN connection.

   The main problem with ISDN routers and bridges is that
   interoperability between manufacturers can still be a problem. If
   you are planning to connect to an Internet provider, you should
   discuss your needs with them.

   If you are planning to connect two LAN segments together, such as
   your home LAN to the office LAN, this is the simplest lowest
   maintenance solution. Since you are buying the equipment for both
   sides of the connection you can be assured that the link will
   work.

   For example to connect a home computer or branch office network to
   a head office network the following setup could be used:

   1/2d"O 29-3. Branch Office or Home Network

   Network uses a bus based topology with 10 base 2 Ethernet
   (!S:thinnet!"). Connect router to network cable with AUI/10BT
   transceiver, if necessary.

 ---Sun workstation
 |
 ---FreeBSD box
 |
 ---Windows 95
 |
 Stand-alone router
    |
 ISDN BRI line

   If your home/branch office is only one computer you can use a
   twisted pair crossover cable to connect to the stand-alone router
   directly.

   1/2d"O 29-4. Head Office or Other LAN

   Network uses a star topology with 10 base T Ethernet (!S:Twisted
   Pair!").

     -------Novell Server
     | H |
     |   ---Sun
     |   |
     | U ---FreeBSD
     |   |
     |   ---Windows 95
     | B |
     |___---Stand-alone router
                 |
         ISDN BRI line

   One large advantage of most routers/bridges is that they allow you
   to have 2 separate independent PPP connections to 2 separate sites
   at the same time. This is not supported on most TA's, except for
   specific (usually expensive) models that have two serial ports. Do
   not confuse this with channel bonding, MPP, etc.

   This can be a very useful feature if, for example, you have an
   dedicated ISDN connection at your office and would like to tap
   into it, but do not want to get another ISDN line at work. A
   router at the office location can manage a dedicated B channel
   connection (64 Kbps) to the Internet and use the other B channel
   for a separate data connection. The second B channel can be used
   for dial-in, dial-out or dynamically bonding (MPP, etc.) with the
   first B channel for more bandwidth.

   An Ethernet bridge will also allow you to transmit more than just
   IP traffic. You can also send IPX/SPX or whatever other protocols
   you use.

     --------------------------------------------------------------

29.9. Network Address Translation

   Contributed by Chern Lee.

  29.9.1. Overview

   FreeBSD's Network Address Translation daemon, commonly known as
   natd(8) is a daemon that accepts incoming raw IP packets, changes
   the source to the local machine and re-injects these packets back
   into the outgoing IP packet stream. natd(8) does this by changing
   the source IP address and port such that when data is received
   back, it is able to determine the original location of the data
   and forward it back to its original requester.

   The most common use of NAT is to perform what is commonly known as
   Internet Connection Sharing.

     --------------------------------------------------------------

  29.9.2. Setup

   Due to the diminishing IP space in IPv4, and the increased number
   of users on high-speed consumer lines such as cable or DSL, people
   are increasingly in need of an Internet Connection Sharing
   solution. The ability to connect several computers online through
   one connection and IP address makes natd(8) a reasonable choice.

   Most commonly, a user has a machine connected to a cable or DSL
   line with one IP address and wishes to use this one connected
   computer to provide Internet access to several more over a LAN.

   To do this, the FreeBSD machine on the Internet must act as a
   gateway. This gateway machine must have two NICs!X!Xone for
   connecting to the Internet router, the other connecting to a LAN.
   All the machines on the LAN are connected through a hub or switch.

     -a`: There are many ways to get a LAN connected to the Internet
     through a FreeBSD gateway. This example will only cover a
     gateway with at least two NICs.

   _______       __________       ________
  |       |     |          |     |        |
  |  Hub  |-----| Client B |-----| Router |----- Internet
  |_______|     |__________|     |________|
      |
  ____|_____
 |          |
 | Client A |
 |__________|

   A setup like this is commonly used to share an Internet
   connection. One of the LAN machines is connected to the Internet.
   The rest of the machines access the Internet through that
   !S:gateway!" machine.

     --------------------------------------------------------------

  29.9.3. Configuration

   The following options must be in the kernel configuration file:

 options IPFIREWALL
 options IPDIVERT

   Additionally, at choice, the following may also be suitable:

 options IPFIREWALL_DEFAULT_TO_ACCEPT
 options IPFIREWALL_VERBOSE

   The following must be in /etc/rc.conf:

 gateway_enable="YES" (1)
 firewall_enable="YES" (2)
 firewall_type="OPEN" (3)
 natd_enable="YES"
 natd_interface="fxp0" (4)
 natd_flags="" (5)

   (1)
           Sets up the machine to act as a gateway. Running sysctl
           net.inet.ip.forwarding=1 would have the same effect.
   (2)
           Enables the firewall rules in /etc/rc.firewall at boot.
   (3)
           This specifies a predefined firewall ruleset that allows
           anything in. See /etc/rc.firewall for additional types.
   (4)
           Indicates which interface to forward packets through (the
           interface connected to the Internet).
   (5)
           Any additional configuration options passed to natd(8) on
           boot.

   Having the previous options defined in /etc/rc.conf would run natd
   -interface fxp0 at boot. This can also be run manually.

     -a`: It is also possible to use a configuration file for natd(8)
     when there are too many options to pass. In this case, the
     configuration file must be defined by adding the following line
     to /etc/rc.conf:

 natd_flags="-f /etc/natd.conf"

     The /etc/natd.conf file will contain a list of configuration
     options, one per line. For example the next section case would
     use the following file:

 redirect_port tcp 192.168.0.2:6667 6667
 redirect_port tcp 192.168.0.3:80 80

     For more information about the configuration file, consult the
     natd(8) manual page about the -f option.

   Each machine and interface behind the LAN should be assigned IP
   address numbers in the private network space as defined by RFC
   1918 and have a default gateway of the natd machine's internal IP
   address.

   For example, client A and B behind the LAN have IP addresses of
   192.168.0.2 and 192.168.0.3, while the natd machine's LAN
   interface has an IP address of 192.168.0.1. Client A and B's
   default gateway must be set to that of the natd machine,
   192.168.0.1. The natd machine's external, or Internet interface
   does not require any special modification for natd(8) to work.

     --------------------------------------------------------------

  29.9.4. Port Redirection

   The drawback with natd(8) is that the LAN clients are not
   accessible from the Internet. Clients on the LAN can make outgoing
   connections to the world but cannot receive incoming ones. This
   presents a problem if trying to run Internet services on one of
   the LAN client machines. A simple way around this is to redirect
   selected Internet ports on the natd machine to a LAN client.

   For example, an IRC server runs on client A, and a web server runs
   on client B. For this to work properly, connections received on
   ports 6667 (IRC) and 80 (web) must be redirected to the respective
   machines.

   The -redirect_port must be passed to natd(8) with the proper
   options. The syntax is as follows:

      -redirect_port proto targetIP:targetPORT[-targetPORT]
                  [aliasIP:]aliasPORT[-aliasPORT]
                  [remoteIP[:remotePORT[-remotePORT]]]

   In the above example, the argument should be:

     -redirect_port tcp 192.168.0.2:6667 6667
     -redirect_port tcp 192.168.0.3:80 80

   This will redirect the proper tcp ports to the LAN client
   machines.

   The -redirect_port argument can be used to indicate port ranges
   over individual ports. For example, tcp 192.168.0.2:2000-3000
   2000-3000 would redirect all connections received on ports 2000 to
   3000 to ports 2000 to 3000 on client A.

   These options can be used when directly running natd(8), placed
   within the natd_flags="" option in /etc/rc.conf, or passed via a
   configuration file.

   For further configuration options, consult natd(8)

     --------------------------------------------------------------

  29.9.5. Address Redirection

   Address redirection is useful if several IP addresses are
   available, yet they must be on one machine. With this, natd(8) can
   assign each LAN client its own external IP address. natd(8) then
   rewrites outgoing packets from the LAN clients with the proper
   external IP address and redirects all traffic incoming on that
   particular IP address back to the specific LAN client. This is
   also known as static NAT. For example, the IP addresses 128.1.1.1,
   128.1.1.2, and 128.1.1.3 belong to the natd gateway machine.
   128.1.1.1 can be used as the natd gateway machine's external IP
   address, while 128.1.1.2 and 128.1.1.3 are forwarded back to LAN
   clients A and B.

   The -redirect_address syntax is as follows:

 -redirect_address localIP publicIP

   localIP   The internal IP address of the LAN client.               
   publicIP  The external IP address corresponding to the LAN client. 

   In the example, this argument would read:

 -redirect_address 192.168.0.2 128.1.1.2
 -redirect_address 192.168.0.3 128.1.1.3

   Like -redirect_port, these arguments are also placed within the
   natd_flags="" option of /etc/rc.conf, or passed via a
   configuration file. With address redirection, there is no need for
   port redirection since all data received on a particular IP
   address is redirected.

   The external IP addresses on the natd machine must be active and
   aliased to the external interface. Look at rc.conf(5) to do so.

     --------------------------------------------------------------

29.10. Parallel Line IP (PLIP)

   PLIP lets us run TCP/IP between parallel ports. It is useful on
   machines without network cards, or to install on laptops. In this
   section, we will discuss:

     * Creating a parallel (laplink) cable.

     * Connecting two computers with PLIP.

     --------------------------------------------------------------

  29.10.1. Creating a Parallel Cable

   You can purchase a parallel cable at most computer supply stores.
   If you cannot do that, or you just want to know how it is done,
   the following table shows how to make one out of a normal parallel
   printer cable.

   -ai(R)ae 29-1. Wiring a Parallel Cable for Networking

   A-name A-End B-End Descr. Post/Bit 
   DATA0  2     15    Data   0/0x01   
   -ERROR 15    2            1/0x08   
   DATA1  3     13    Data   0/0x02   
   +SLCT  13    3            1/0x10   
   DATA2  4     12    Data   0/0x04   
   +PE    12    4            1/0x20   
   DATA3  5     10    Strobe 0/0x08   
   -ACK   10    5            1/0x40   
   DATA4  6     11    Data   0/0x10   
   BUSY   11    6            1/0x80   
   GND    18-25 18-25 GND    -        

     --------------------------------------------------------------

  29.10.2. Setting Up PLIP

   First, you have to get a laplink cable. Then, confirm that both
   computers have a kernel with lpt(4) driver support:

 # grep lp /var/run/dmesg.boot
 lpt0: <Printer> on ppbus0
 lpt0: Interrupt-driven port

   The parallel port must be an interrupt driven port, you should
   have lines similar to the following in your in the
   /boot/device.hints file:

 hint.ppc.0.at="isa"
 hint.ppc.0.irq="7"

   Then check if the kernel configuration file has a device plip line
   or if the plip.ko kernel module is loaded. In both cases the
   parallel networking interface should appear when you use the
   ifconfig(8) command to display it:

 # ifconfig plip0
 plip0: flags=8810<POINTOPOINT,SIMPLEX,MULTICAST> mtu 1500

   Plug the laplink cable into the parallel interface on both
   computers.

   Configure the network interface parameters on both sites as root.
   For example, if you want to connect the host host1 with another
   machine host2:

                  host1 <-----> host2
 IP Address    10.0.0.1      10.0.0.2

   Configure the interface on host1 by doing:

 # ifconfig plip0 10.0.0.1 10.0.0.2

   Configure the interface on host2 by doing:

 # ifconfig plip0 10.0.0.2 10.0.0.1

   You now should have a working connection. Please read the manual
   pages lp(4) and lpt(4) for more details.

   You should also add both hosts to /etc/hosts:

 127.0.0.1               localhost.my.domain localhost
 10.0.0.1                host1.my.domain host1
 10.0.0.2                host2.my.domain

   To confirm the connection works, go to each host and ping the
   other. For example, on host1:

 # ifconfig plip0
 plip0: flags=8851<UP,POINTOPOINT,RUNNING,SIMPLEX,MULTICAST> mtu 1500
         inet 10.0.0.1 --> 10.0.0.2 netmask 0xff000000
 # netstat -r
 Routing tables

 Internet:
 Destination        Gateway          Flags     Refs     Use      Netif Expire
 host2              host1            UH          0       0       plip0
 # ping -c 4 host2
 PING host2 (10.0.0.2): 56 data bytes
 64 bytes from 10.0.0.2: icmp_seq=0 ttl=255 time=2.774 ms
 64 bytes from 10.0.0.2: icmp_seq=1 ttl=255 time=2.530 ms
 64 bytes from 10.0.0.2: icmp_seq=2 ttl=255 time=2.556 ms
 64 bytes from 10.0.0.2: icmp_seq=3 ttl=255 time=2.714 ms

 --- host2 ping statistics ---
 4 packets transmitted, 4 packets received, 0% packet loss
 round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms

     --------------------------------------------------------------

29.11. IPv6

   Originally Written by Aaron Kaplan. Restructured and Added by Tom
   Rhodes. Extended by Brad Davis.

   IPv6 (also known as IPng !S:IP next generation!") is the new
   version of the well known IP protocol (also known as IPv4). Like
   the other current *BSD systems, FreeBSD includes the KAME IPv6
   reference implementation. So your FreeBSD system comes with all
   you will need to experiment with IPv6. This section focuses on
   getting IPv6 configured and running.

   In the early 1990s, people became aware of the rapidly diminishing
   address space of IPv4. Given the expansion rate of the Internet
   there were two major concerns:

     * Running out of addresses. Today this is not so much of a
       concern anymore since RFC1918 private address space
       (10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16) and Network
       Address Translation (NAT) are being employed.

     * Router table entries were getting too large. This is still a
       concern today.

   IPv6 deals with these and many other issues:

     * 128 bit address space. In other words theoretically there are
       340,282,366,920,938,463,463,374,607,431,768,211,456 addresses
       available. This means there are approximately 6.67 * 10^27
       IPv6 addresses per square meter on our planet.

     * Routers will only store network aggregation addresses in their
       routing tables thus reducing the average space of a routing
       table to 8192 entries.

   There are also lots of other useful features of IPv6 such as:

     * Address autoconfiguration (RFC2462)

     * Anycast addresses (!S:one-out-of many!")

     * Mandatory multicast addresses

     * IPsec (IP security)

     * Simplified header structure

     * Mobile IP

     * IPv6-to-IPv4 transition mechanisms

   For more information see:

     * IPv6 overview at playground.sun.com

     * KAME.net

     --------------------------------------------------------------

  29.11.1. Background on IPv6 Addresses

   There are different types of IPv6 addresses: Unicast, Anycast and
   Multicast.

   Unicast addresses are the well known addresses. A packet sent to a
   unicast address arrives exactly at the interface belonging to the
   address.

   Anycast addresses are syntactically indistinguishable from unicast
   addresses but they address a group of interfaces. The packet
   destined for an anycast address will arrive at the nearest (in
   router metric) interface. Anycast addresses may only be used by
   routers.

   Multicast addresses identify a group of interfaces. A packet
   destined for a multicast address will arrive at all interfaces
   belonging to the multicast group.

     -a`: The IPv4 broadcast address (usually xxx.xxx.xxx.255) is
     expressed by multicast addresses in IPv6.

   -ai(R)ae 29-2. Reserved IPv6 addresses

     IPv6 address   Prefixlength  Description           Notes         
                       (Bits)    
   ::               128 bits     unspecified    cf. 0.0.0.0 in IPv4   
   ::1              128 bits     loopback       cf. 127.0.0.1 in IPv4 
                                 address        
                                                The lower 32 bits are 
                                                the IPv4 address.     
   ::00:xx:xx:xx:xx 96 bits      embedded IPv4  Also called !S:IPv4   
                                                compatible IPv6       
                                                address!"             
                                                The lower 32 bits are 
   ::ff:xx:xx:xx:xx 96 bits      IPv4 mapped    the IPv4 address. For 
                                 IPv6 address   hosts which do not    
                                                support IPv6.         
   fe80:: - feb::   10 bits      link-local     cf. loopback address  
                                                in IPv4               
   fec0:: - fef::   10 bits      site-local                           
   ff::             8 bits       multicast                            
                                                All global unicast    
                                                addresses are         
   001 (base 2)     3 bits       global unicast assigned from this    
                                                pool. The first 3     
                                                bits are !S:001!".    

     --------------------------------------------------------------

  29.11.2. Reading IPv6 Addresses

   The canonical form is represented as: x:x:x:x:x:x:x:x, each !S:x!"
   being a 16 Bit hex value. For example
   FEBC:A574:382B:23C1:AA49:4592:4EFE:9982

   Often an address will have long substrings of all zeros therefore
   one such substring per address can be abbreviated by !S:::!". Also
   up to three leading !S:0!"s per hexquad can be omitted. For
   example fe80::1 corresponds to the canonical form
   fe80:0000:0000:0000:0000:0000:0000:0001.

   A third form is to write the last 32 Bit part in the well known
   (decimal) IPv4 style with dots !S:.!" as separators. For example
   2002::10.0.0.1 corresponds to the (hexadecimal) canonical
   representation 2002:0000:0000:0000:0000:0000:0a00:0001 which in
   turn is equivalent to writing 2002::a00:1.

   By now the reader should be able to understand the following:

 # ifconfig

 rl0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
          inet 10.0.0.10 netmask 0xffffff00 broadcast 10.0.0.255
          inet6 fe80::200:21ff:fe03:8e1%rl0 prefixlen 64 scopeid 0x1
          ether 00:00:21:03:08:e1
          media: Ethernet autoselect (100baseTX )
          status: active

   fe80::200:21ff:fe03:8e1%rl0 is an auto configured link-local
   address. It is generated from the MAC address as part of the auto
   configuration.

   For further information on the structure of IPv6 addresses see
   RFC3513.

     --------------------------------------------------------------

  29.11.3. Getting Connected

   Currently there are four ways to connect to other IPv6 hosts and
   networks:

     * Getting an IPv6 network from your upstream provider. Talk to
       your Internet provider for instructions.

     * Tunnel via 6-to-4 (RFC3068)

     * Use the net/freenet6 port if you are on a dial-up connection.

     --------------------------------------------------------------

  29.11.4. DNS in the IPv6 World

   There used to be two types of DNS records for IPv6. The IETF has
   declared A6 records obsolete. AAAA records are the standard now.

   Using AAAA records is straightforward. Assign your hostname to the
   new IPv6 address you just received by adding:

 MYHOSTNAME           AAAA    MYIPv6ADDR

   To your primary zone DNS file. In case you do not serve your own
   DNS zones ask your DNS provider. Current versions of bind (version
   8.3 and 9) and dns/djbdns (with the IPv6 patch) support AAAA
   records.

     --------------------------------------------------------------

  29.11.5. Applying the needed changes to /etc/rc.conf

    29.11.5.1. IPv6 Client Settings

   These settings will help you configure a machine that will be on
   your LAN and act as a client, not a router. To have rtsol(8)
   autoconfigure your interface on boot all you need to add is:

 ipv6_enable="YES"

   To statically assign an IP address such as  
   2001:471:1f11:251:290:27ff:fee0:2093, to your fxp0 interface, add:

 ipv6_ifconfig_fxp0="2001:471:1f11:251:290:27ff:fee0:2093"

   To assign a default router of 2001:471:1f11:251::1 add the
   following to /etc/rc.conf:

 ipv6_defaultrouter="2001:471:1f11:251::1"

     --------------------------------------------------------------

    29.11.5.2. IPv6 Router/Gateway Settings

   This will help you take the directions that your tunnel provider
   has given you and convert it into settings that will persist
   through reboots. To restore your tunnel on startup use something
   like the following in /etc/rc.conf:

   List the Generic Tunneling interfaces that will be configured, for
   example gif0:

 gif_interfaces="gif0"

   To configure the interface with a local endpoint of MY_IPv4_ADDR
   to a remote endpoint of REMOTE_IPv4_ADDR:

 gifconfig_gif0="MY_IPv4_ADDR REMOTE_IPv4_ADDR"

   To apply the IPv6 address you have been assigned for use as your
   IPv6 tunnel endpoint, add:

 ipv6_ifconfig_gif0="MY_ASSIGNED_IPv6_TUNNEL_ENDPOINT_ADDR"

   Then all you have to do is set the default route for IPv6. This is
   the other side of the IPv6 tunnel:

 ipv6_defaultrouter="MY_IPv6_REMOTE_TUNNEL_ENDPOINT_ADDR"

     --------------------------------------------------------------

    29.11.5.3. IPv6 Tunnel Settings

   If the server is to route IPv6 between the rest of your network
   and the world, the following /etc/rc.conf setting will also be
   needed:

 ipv6_gateway_enable="YES"

     --------------------------------------------------------------

  29.11.6. Router Advertisement and Host Auto Configuration

   This section will help you setup rtadvd(8) to advertise the IPv6
   default route.

   To enable rtadvd(8) you will need the following in your
   /etc/rc.conf:

 rtadvd_enable="YES"

   It is important that you specify the interface on which to do IPv6
   router solicitation. For example to tell rtadvd(8) to use fxp0:

 rtadvd_interfaces="fxp0"

   Now we must create the configuration file, /etc/rtadvd.conf. Here
   is an example:

 fxp0:\
         :addrs#1:addr="2001:471:1f11:246::":prefixlen#64:tc=ether:

   Replace fxp0 with the interface you are going to be using.

   Next, replace 2001:471:1f11:246:: with the prefix of your
   allocation.

   If you are dedicated a /64 subnet you will not need to change
   anything else. Otherwise, you will need to change the prefixlen#
   to the correct value.

     --------------------------------------------------------------

29.12. Asynchronous Transfer Mode (ATM)

   Contributed by Harti Brandt.

  29.12.1. Configuring classical IP over ATM (PVCs)

   Classical IP over ATM (CLIP) is the simplest method to use
   Asynchronous Transfer Mode (ATM) with IP. It can be used with
   switched connections (SVCs) and with permanent connections (PVCs).
   This section describes how to set up a network based on PVCs.

     --------------------------------------------------------------

    29.12.1.1. Fully meshed configurations

   The first method to set up a CLIP with PVCs is to connect each
   machine to each other machine in the network via a dedicated PVC.
   While this is simple to configure it tends to become impractical
   for a larger number of machines. The example supposes that we have
   four machines in the network, each connected to the ATM network
   with an ATM adapter card. The first step is the planning of the IP
   addresses and the ATM connections between the machines. We use the
   following:

                 Host                          IP Address             
   hostA                            192.168.173.1                     
   hostB                            192.168.173.2                     
   hostC                            192.168.173.3                     
   hostD                            192.168.173.4                     

   To build a fully meshed net we need one ATM connection between
   each pair of machines:

               Machines                      VPI.VCI couple           
   hostA - hostB                    0.100                             
   hostA - hostC                    0.101                             
   hostA - hostD                    0.102                             
   hostB - hostC                    0.103                             
   hostB - hostD                    0.104                             
   hostC - hostD                    0.105                             

   The VPI and VCI values at each end of the connection may of course
   differ, but for simplicity we assume that they are the same. Next
   we need to configure the ATM interfaces on each host:

 hostA# ifconfig hatm0 192.168.173.1 up
 hostB# ifconfig hatm0 192.168.173.2 up
 hostC# ifconfig hatm0 192.168.173.3 up
 hostD# ifconfig hatm0 192.168.173.4 up

   assuming that the ATM interface is hatm0 on all hosts. Now the
   PVCs need to be configured on hostA (we assume that they are
   already configured on the ATM switches, you need to consult the
   manual for the switch on how to do this).

 hostA# atmconfig natm add 192.168.173.2 hatm0 0 100 llc/snap ubr
 hostA# atmconfig natm add 192.168.173.3 hatm0 0 101 llc/snap ubr
 hostA# atmconfig natm add 192.168.173.4 hatm0 0 102 llc/snap ubr

 hostB# atmconfig natm add 192.168.173.1 hatm0 0 100 llc/snap ubr
 hostB# atmconfig natm add 192.168.173.3 hatm0 0 103 llc/snap ubr
 hostB# atmconfig natm add 192.168.173.4 hatm0 0 104 llc/snap ubr

 hostC# atmconfig natm add 192.168.173.1 hatm0 0 101 llc/snap ubr
 hostC# atmconfig natm add 192.168.173.2 hatm0 0 103 llc/snap ubr
 hostC# atmconfig natm add 192.168.173.4 hatm0 0 105 llc/snap ubr

 hostD# atmconfig natm add 192.168.173.1 hatm0 0 102 llc/snap ubr
 hostD# atmconfig natm add 192.168.173.2 hatm0 0 104 llc/snap ubr
 hostD# atmconfig natm add 192.168.173.3 hatm0 0 105 llc/snap ubr

   Of course other traffic contracts than UBR can be used given the
   ATM adapter supports those. In this case the name of the traffic
   contract is followed by the parameters of the traffic. Help for
   the atmconfig(8) tool can be obtained with:

 # atmconfig help natm add

   or in the atmconfig(8) manual page.

   The same configuration can also be done via /etc/rc.conf. For
   hostA this would look like:

 network_interfaces="lo0 hatm0"
 ifconfig_hatm0="inet 192.168.173.1 up"
 natm_static_routes="hostB hostC hostD"
 route_hostB="192.168.173.2 hatm0 0 100 llc/snap ubr"
 route_hostC="192.168.173.3 hatm0 0 101 llc/snap ubr"
 route_hostD="192.168.173.4 hatm0 0 102 llc/snap ubr"

   The current state of all CLIP routes can be obtained with:

 hostA# atmconfig natm show

     --------------------------------------------------------------

29.13. Common Access Redundancy Protocol (CARP)

   Contributed by Tom Rhodes.

   The Common Access Redundancy Protocol, or CARP allows multiple
   hosts to share the same IP address. In some configurations, this
   may be used for availability or load balancing. Hosts may use
   separate IP addresses as well, as in the example provided here.

   To enable support for CARP, the FreeBSD kernel must be rebuilt
   with the following option:

 device  carp

   CARP functionality should now be available and may be tuned via
   several sysctl OIDs. Devices themselves may be loaded via the
   ifconfig command:

 # ifconfig carp0 create

   In a real environment, these interfaces will need unique
   identification numbers known as a VHID. This VHID or Virtual Host
   Identification will be used to distinguish the host on the
   network.

     --------------------------------------------------------------

  29.13.1. Using CARP For Server Availability (CARP)

   One use of CARP, as noted above, is for server availability. This
   example will provide failover support for three hosts, all with
   unique IP addresses and providing the same web content. These
   machines will act in conjunction with a Round Robin DNS
   configuration. The failover machine will have two additional CARP
   interfaces, one for each of the content server's IPs. When a
   failure occurs, the failover server should pick up the failed
   machine's IP address. This means the failure should go completely
   unnoticed to the user. The failover server requires identical
   content and services as the other content servers it is expected
   to pick up load for.

   The two machines should be configured identically other than their
   issued hostnames and VHIDs. This example calls these machines
   hosta.example.org and hostb.example.org respectively. First, the
   required lines for a CARP configuration have to be added to
   rc.conf. For hosta.example.org, the rc.conf file should contain
   the following lines:

 hostname="hosta.example.org"
 ifconfig_fxp0="inet 192.168.1.3 netmask 255.255.255.0"
 cloned_interfaces="carp0"
 ifconfig_carp0="vhid 1 pass testpast 192.168.1.50/24"

   On hostb.example.org the following lines should be in rc.conf:

 hostname="hostb.example.org"
 ifconfig_fxp0="inet 192.168.1.4 netmask 255.255.255.0"
 cloned_interfaces="carp0"
 ifconfig_carp0="vhid 2 pass testpass 192.168.1.51/24"

     -a`: It is very important that the passwords, specified by the
     pass option to ifconfig, are identical. The carp devices will
     only listen to and accept advertisements from machines with the
     correct password. The VHID must also be different for each
     machine.

   The third machine, provider.example.org, should be prepared so
   that it may handle failover from either host. This machine will
   require two carp devices, one to handle each host. The appropriate
   rc.conf configuration lines will be similar to the following:

 hostname="provider.example.org"
 ifconfig_fxp0="inet 192.168.1.5 netmask 255.255.255.0"
 cloned_interfaces="carp0 carp1"
 ifconfig_carp0="vhid 1 advskew 100 pass testpass 192.168.1.50/24"
 ifconfig_carp1="vhid 2 advskew 100 pass testpass 192.168.1.51/24"

   Having the two carp devices will allow provider.example.org to
   notice and pick up the IP address of either machine should it stop
   responding.

     -a`: The default FreeBSD kernel may have preemption enabled. If
     so, provider.example.org may not relinquish the IP address back
     to the original content server. In this case, an administrator
     may !S:nudge!" the interface. The following command should be
     issued on provider.example.org:

 # ifconfig carp0 down && ifconfig carp0 up

     This should be done on the carp interface which corresponds to
     the correct host.

   At this point, CARP should be completely enabled and available for
   testing. For testing, either networking has to be restarted or the
   machines need to be rebooted.

   More information is always available in the carp(4) manual page.

                               V. -ath?y

   CUR-o(R)eYENO/?y

   A. "u+-o FreeBSD -a-oCURe|!

   B. DEGN|OCURaaA:m

   C. -oo>>U-oo,oCURW-a-o,e. 1/2

   D. PGP Keys

     --------------------------------------------------------------

                   -ath?y A. "u+-o FreeBSD -a-oCURe|!

A.1. CDROM CURI DVD uo|aeDEGO

  A.1.1. ^2DEG,E^2-L-<<~-a-o^1sDEGa^3B!G

   FreeBSD ^2DEG,E^2-L-<<~(S:t FreeBSD
   YENu-oD-CURI"a:YENLCUR@"C,^3nAAe!B(R)N+-CURaaYENo)-a-o^1sDEGa.~-aI!G

     *     CompUSA
           WWW: http://www.compusa.com/
         

     *     Frys Electronics
           WWW: http://www.frys.com/
         

     --------------------------------------------------------------

  A.1.2. CD CURI DVD |XP:DEG

   FreeBSD YENu-oD-(CD CURI DVD)-a-o-oo,o^1sDEGa.~-aI!G

     *   BSD Mall by Daemon News
         PO Box 161
         Nauvoo, IL 62354
         USA
         Phone: +1 866 273-6255
         Fax: +1 217 453-9956
         Email: <sales@bsdmall.com>
         WWW: http://www.bsdmall.com/freebsd1.html
               

     *   BSD-Systems
         Email: <info@bsd-systems.co.uk>
         WWW: http://www.bsd-systems.co.uk
               

     *   FreeBSD Mall, Inc.
         3623 Sanford Street
         Concord, CA  94520-1405
         USA
         Phone: +1 925 674-0783
         Fax: +1 925 674-0821
         Email: <info@freebsdmall.com>
         WWW: http://www.freebsdmall.com/
               

     *   Hinner EDV
         St. Augustinus-Str. 10
         D-81825 Mu:nchen
         Germany
         Phone: (089) 428 419
         WWW: http://www.hinner.de/linux/freebsd.html
               

     *   Ikarios
         22-24 rue Voltaire
         92000 Nanterre
         France
         WWW: http://ikarios.com/form/#freebsd
               

     *   JMC Software
         Ireland
         Phone: 353 1 6291282
         WWW: http://www.thelinuxmall.com

     *   Linux CD Mall
         Private Bag MBE N348
         Auckland 1030
         New Zealand
         Phone: +64 21 866529
         WWW: http://www.linuxcdmall.co.nz/

     *   The Linux Emporium
         Hilliard House, Lester Way
         Wallingford
         OX10 9TA
         United Kingdom
         Phone: +44 1491 837010
         Fax: +44 1491 837016
         WWW: http://www.linuxemporium.co.uk/products/freebsd/
               

     *   Linux+ DVD Magazine
         Lewartowskiego 6
         Warsaw
         00-190
         Poland
         Phone: +48 22 860 18 18
         Email: <editors@lpmagazine.org>
         WWW: http://www.lpmagazine.org/

     *   Linux System Labs Australia
         21 Ray Drive
         Balwyn North
         VIC - 3104
         Australia
         Phone: +61 3 9857 5918
         Fax: +61 3 9857 8974
         WWW: http://www.lsl.com.au
               

     *   LinuxCenter.Ru
         Galernaya Street, 55
         Saint-Petersburg
         190000
         Russia
         Phone: +7-812-3125208
         Email: <info@linuxcenter.ru>
         WWW: http://linuxcenter.ru/freebsd

     --------------------------------------------------------------

  A.1.3. ,g 3/4PDEGO(Distributors)

   YS:ANOTODEGIDEG`i,g 3/4PDEGO!A"A.QYENN^2z,g 3/4P FreeBSD
   YENu-oD-^2-L-<<~-a-o,U:!A 1/2D->>PCURU|C-a-oYENN^2zDEGOApA'!G

     *     Cylogistics
           809B Cuesta Dr., #2149
           Mountain View, CA 94040
           USA
           Phone: +1 650 694-4949
           Fax: +1 650 694-4953
           Email: <sales@cylogistics.com>
           WWW: http://www.cylogistics.com/
         

     *     Ingram Micro
           1600 E. St. Andrew Place
           Santa Ana, CA  92705-4926
           USA
           Phone: 1 (800) 456-8000
           WWW: http://www.ingrammicro.com/
                 

     *     Kudzu, LLC
           7375 Washington Ave. S.
           Edina, MN 55439
           USA
           Phone: +1 952 947-0822
           Fax: +1 952 947-0876
           Email: <sales@kudzuenterprises.com>
         

     *     LinuxCenter.Ru
           Galernaya Street, 55
           Saint-Petersburg
           190000
           Russia
           Phone: +7-812-3125208
           Email: <info@linuxcenter.ru>
           WWW: http://linuxcenter.ru/freebsd
         

     *     Navarre Corp
           7400 49th Ave South
           New Hope, MN 55428
           USA
           Phone: +1 763 535-8333
           Fax: +1 763 535-0341
           WWW: http://www.navarre.com/
         

     --------------------------------------------------------------

A.2. FTP -,

   The official sources for FreeBSD are available via anonymous FTP
   from a worldwide set of mirror sites. The site
   ftp://ftp.FreeBSD.org/pub/FreeBSD/ is well connected and allows a
   large number of connections to it, but you are probably better off
   finding a !S:closer!" mirror site (especially if you decide to set
   up some sort of mirror site).

   The FreeBSD mirror sites database is more accurate than the mirror
   listing in the Handbook, as it gets its information from the DNS
   rather than relying on static lists of hosts.

   Additionally, FreeBSD is available via anonymous FTP from the
   following mirror sites. If you choose to obtain FreeBSD via
   anonymous FTP, please try to use a site near you. The mirror sites
   listed as !S:Primary Mirror Sites!" typically have the entire
   FreeBSD archive (all the currently available versions for each of
   the architectures) but you will probably have faster download
   times from a site that is in your country or region. The regional
   sites carry the most recent versions for the most popular
   architecture(s) but might not carry the entire FreeBSD archive.
   All sites provide access via anonymous FTP but some sites also
   provide access via other methods. The access methods available for
   each site are provided in parentheses after the hostname.

   Central Servers, Primary Mirror Sites, Armenia, Australia,
   Austria, Brazil, Canada, China, Czech Republic, Denmark, Estonia,
   Finland, France, Germany, Greece, Hong Kong, Iceland, Ireland,
   Israel, Italy, Japan, Korea, Latvia, Lithuania, Netherlands, New
   Zealand, Norway, Poland, Portugal, Romania, Russia, Saudi Arabia,
   Slovak Republic, Slovenia, South Africa, Spain, Sweden,
   Switzerland, Taiwan, Turkey, Ukraine, United Kingdom, USA.

   (as of UTC)

   Central Servers

              * ftp://ftp.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6)

   Primary Mirror Sites

           In case of problems, please contact the hostmaster
           <mirror-admin@FreeBSD.org> for this domain.

              * ftp://ftp1.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp3.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp4.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6)

              * ftp://ftp5.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp6.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp7.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp8.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp9.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp10.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6)

              * ftp://ftp11.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp12.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp13.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp14.FreeBSD.org/pub/FreeBSD/ (ftp / http)

   Armenia

           In case of problems, please contact the hostmaster
           <hostmaster@am.FreeBSD.org> for this domain.

              * ftp://ftp1.am.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

   Australia

           In case of problems, please contact the hostmaster
           <hostmaster@au.FreeBSD.org> for this domain.

              * ftp://ftp.au.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.au.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp3.au.FreeBSD.org/pub/FreeBSD/ (ftp)

   Austria

           In case of problems, please contact the hostmaster
           <hostmaster@at.FreeBSD.org> for this domain.

              * ftp://ftp.at.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6)

   Brazil

           In case of problems, please contact the hostmaster
           <hostmaster@br.FreeBSD.org> for this domain.

              * ftp://ftp.br.FreeBSD.org/pub/FreeBSD/ (ftp / http)

              * ftp://ftp2.br.FreeBSD.org/pub/FreeBSD/ (ftp / http)

              * ftp://ftp3.br.FreeBSD.org/pub/FreeBSD/ (ftp / rsync)

              * ftp://ftp4.br.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp5.br.FreeBSD.org

              * ftp://ftp6.br.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp7.br.FreeBSD.org/pub/FreeBSD/ (ftp)

   Canada

           In case of problems, please contact the hostmaster
           <hostmaster@ca.FreeBSD.org> for this domain.

              * ftp://ftp.ca.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.ca.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp3.ca.FreeBSD.org/pub/FreeBSD/ (ftp)

   China

           In case of problems, please contact the hostmaster
           <hostmaster@cn.FreeBSD.org> for this domain.

              * ftp://ftp.cn.FreeBSD.org/pub/FreeBSD/ (ftp)

   Czech Republic

           In case of problems, please contact the hostmaster
           <hostmaster@cz.FreeBSD.org> for this domain.

              * ftp://ftp.cz.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6 / rsync / rsyncv6)

              * ftp://ftp2.cz.FreeBSD.org/pub/FreeBSD/ (ftp / http)

   Denmark

           In case of problems, please contact the hostmaster
           <hostmaster@dk.FreeBSD.org> for this domain.

              * ftp://ftp.dk.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6)

   Estonia

           In case of problems, please contact the hostmaster
           <hostmaster@ee.FreeBSD.org> for this domain.

              * ftp://ftp.ee.FreeBSD.org/pub/FreeBSD/ (ftp)

   Finland

           In case of problems, please contact the hostmaster
           <hostmaster@fi.FreeBSD.org> for this domain.

              * ftp://ftp.fi.FreeBSD.org/pub/FreeBSD/ (ftp)

   France

           In case of problems, please contact the hostmaster
           <hostmaster@fr.FreeBSD.org> for this domain.

              * ftp://ftp.fr.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp1.fr.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp2.fr.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp3.fr.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp4.fr.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6 / rsync / rsyncv6)

              * ftp://ftp5.fr.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp6.fr.FreeBSD.org/pub/FreeBSD/ (ftp / rsync)

              * ftp://ftp7.fr.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp8.fr.FreeBSD.org/pub/FreeBSD/ (ftp)

   Germany

           In case of problems, please contact the hostmaster
           <de-bsd-hubs@de.FreeBSD.org> for this domain.

              * ftp://ftp.de.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp1.de.FreeBSD.org/freebsd/ (ftp / http /
                rsync)

              * ftp://ftp2.de.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp3.de.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp4.de.FreeBSD.org/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp5.de.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp6.de.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp7.de.FreeBSD.org/pub/FreeBSD/ (ftp / http)

              * ftp://ftp8.de.FreeBSD.org/pub/FreeBSD/ (ftp)

   Greece

           In case of problems, please contact the hostmaster
           <hostmaster@gr.FreeBSD.org> for this domain.

              * ftp://ftp.gr.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.gr.FreeBSD.org/pub/FreeBSD/ (ftp)

   Hong Kong

              * ftp://ftp.hk.FreeBSD.org/pub/FreeBSD/ (ftp)

   Iceland

           In case of problems, please contact the hostmaster
           <hostmaster@is.FreeBSD.org> for this domain.

              * ftp://ftp.is.FreeBSD.org/pub/FreeBSD/ (ftp / rsync)

   Ireland

           In case of problems, please contact the hostmaster
           <hostmaster@ie.FreeBSD.org> for this domain.

              * ftp://ftp.ie.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.ie.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp3.ie.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

   Israel

           In case of problems, please contact the hostmaster
           <hostmaster@il.FreeBSD.org> for this domain.

              * ftp://ftp.il.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6)

   Italy

           In case of problems, please contact the hostmaster
           <hostmaster@it.FreeBSD.org> for this domain.

              * ftp://ftp.it.FreeBSD.org/pub/FreeBSD/ (ftp)

   Japan

           In case of problems, please contact the hostmaster
           <hostmaster@jp.FreeBSD.org> for this domain.

              * ftp://ftp.jp.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.jp.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp3.jp.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp4.jp.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp5.jp.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp6.jp.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp7.jp.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp8.jp.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp9.jp.FreeBSD.org/pub/FreeBSD/ (ftp)

   Korea

           In case of problems, please contact the hostmaster
           <hostmaster@kr.FreeBSD.org> for this domain.

              * ftp://ftp.kr.FreeBSD.org/pub/FreeBSD/ (ftp / rsync)

              * ftp://ftp2.kr.FreeBSD.org/pub/FreeBSD/ (ftp / http)

   Latvia

           In case of problems, please contact the hostmaster
           <hostmaster@lv.FreeBSD.org> for this domain.

              * ftp://ftp.lv.FreeBSD.org/pub/FreeBSD/ (ftp / http)

              * ftp://ftp2.lv.FreeBSD.org/pub/FreeBSD/ (ftp)

   Lithuania

           In case of problems, please contact the hostmaster
           <hostmaster@lt.FreeBSD.org> for this domain.

              * ftp://ftp.lt.FreeBSD.org/pub/FreeBSD/ (ftp / http)

   Netherlands

           In case of problems, please contact the hostmaster
           <hostmaster@nl.FreeBSD.org> for this domain.

              * ftp://ftp.nl.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp2.nl.FreeBSD.org/pub/FreeBSD/ (ftp)

   New Zealand

              * ftp://ftp.nz.FreeBSD.org/pub/FreeBSD/ (ftp / http)

   Norway

           In case of problems, please contact the hostmaster
           <hostmaster@no.FreeBSD.org> for this domain.

              * ftp://ftp.no.FreeBSD.org/pub/FreeBSD/ (ftp / rsync)

              * ftp://ftp3.no.FreeBSD.org/pub/FreeBSD/ (ftp)

   Poland

           In case of problems, please contact the hostmaster
           <hostmaster@pl.FreeBSD.org> for this domain.

              * ftp://ftp.pl.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.pl.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6 / rsync / rsyncv6)

   Portugal

           In case of problems, please contact the hostmaster
           <hostmaster@pt.FreeBSD.org> for this domain.

              * ftp://ftp.pt.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.pt.FreeBSD.org/pub/freebsd/ (ftp)

              * ftp://ftp4.pt.FreeBSD.org/pub/ISO/FreeBSD/ (ftp)

   Romania

           In case of problems, please contact the hostmaster
           <hostmaster@ro.FreeBSD.org> for this domain.

              * ftp://ftp.ro.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp1.ro.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6)

   Russia

           In case of problems, please contact the hostmaster
           <hostmaster@ru.FreeBSD.org> for this domain.

              * ftp://ftp.ru.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp2.ru.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp3.ru.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp4.ru.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp5.ru.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp6.ru.FreeBSD.org/pub/FreeBSD/ (ftp)

   Saudi Arabia

           In case of problems, please contact the hostmaster
           <ftpadmin@isu.net.sa> for this domain.

              * ftp://ftp.isu.net.sa/pub/ftp.freebsd.org/ (ftp)

   Slovak Republic

           In case of problems, please contact the hostmaster
           <hostmaster@sk.FreeBSD.org> for this domain.

              * ftp://ftp.sk.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6 / rsync / rsyncv6)

              * ftp://ftp2.sk.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6)

   Slovenia

           In case of problems, please contact the hostmaster
           <hostmaster@si.FreeBSD.org> for this domain.

              * ftp://ftp.si.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.si.FreeBSD.org/pub/FreeBSD/ (ftp)

   South Africa

           In case of problems, please contact the hostmaster
           <hostmaster@za.FreeBSD.org> for this domain.

              * ftp://ftp.za.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.za.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp3.za.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp4.za.FreeBSD.org/pub/FreeBSD/ (ftp)

   Spain

           In case of problems, please contact the hostmaster
           <hostmaster@es.FreeBSD.org> for this domain.

              * ftp://ftp.es.FreeBSD.org/pub/FreeBSD/ (ftp / http)

              * ftp://ftp2.es.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp3.es.FreeBSD.org/pub/FreeBSD/ (ftp)

   Sweden

           In case of problems, please contact the hostmaster
           <hostmaster@se.FreeBSD.org> for this domain.

              * ftp://ftp.se.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.se.FreeBSD.org/pub/FreeBSD/ (ftp / rsync)

              * ftp://ftp3.se.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp4.se.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6 / rsync / rsyncv6)

              * ftp://ftp5.se.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp6.se.FreeBSD.org/pub/FreeBSD (ftp / http)

   Switzerland

           In case of problems, please contact the hostmaster
           <hostmaster@ch.FreeBSD.org> for this domain.

              * ftp://ftp.ch.FreeBSD.org/pub/FreeBSD/ (ftp / http)

   Taiwan

           In case of problems, please contact the hostmaster
           <hostmaster@tw.FreeBSD.org> for this domain.

              * ftp://ftp.tw.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                rsync / rsyncv6)

              * ftp://ftp2.tw.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6 / rsync / rsyncv6)

              * ftp://ftp3.tw.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp4.tw.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp5.tw.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp6.tw.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp7.tw.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp8.tw.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp9.tw.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp10.tw.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp11.tw.FreeBSD.org/pub/FreeBSD/ (ftp / http)

              * ftp://ftp12.tw.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp13.tw.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp14.tw.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp15.tw.FreeBSD.org/pub/FreeBSD/ (ftp)

   Turkey

              * ftp://ftp.tr.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp2.tr.FreeBSD.org/pub/FreeBSD/ (ftp / rsync)

   Ukraine

              * ftp://ftp.ua.FreeBSD.org/pub/FreeBSD/ (ftp / http)

              * ftp://ftp2.ua.FreeBSD.org/pub/FreeBSD/ (ftp / http)

              * ftp://ftp7.ua.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp8.ua.FreeBSD.org/pub/FreeBSD/ (ftp / http)

              * ftp://ftp11.ua.FreeBSD.org/pub/FreeBSD/ (ftp)

   United Kingdom

           In case of problems, please contact the hostmaster
           <hostmaster@uk.FreeBSD.org> for this domain.

              * ftp://ftp.uk.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.uk.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp3.uk.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp4.uk.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp5.uk.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp6.uk.FreeBSD.org/pub/FreeBSD/ (ftp)

   USA

           In case of problems, please contact the hostmaster
           <hostmaster@us.FreeBSD.org> for this domain.

              * ftp://ftp1.us.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp2.us.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp3.us.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp4.us.FreeBSD.org/pub/FreeBSD/ (ftp / ftpv6 /
                http / httpv6)

              * ftp://ftp5.us.FreeBSD.org/pub/FreeBSD/ (ftp / rsync)

              * ftp://ftp6.us.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp7.us.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp8.us.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp9.us.FreeBSD.org

              * ftp://ftp10.us.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp11.us.FreeBSD.org/pub/FreeBSD/ (ftp)

              * ftp://ftp12.us.FreeBSD.org/pub/FreeBSD/ (ftp / rsync)

              * ftp://ftp13.us.FreeBSD.org/pub/FreeBSD/ (ftp / http /
                rsync)

              * ftp://ftp14.us.FreeBSD.org/pub/FreeBSD/ (ftp / http)

              * ftp://ftp15.us.FreeBSD.org/pub/FreeBSD/ (ftp)

     --------------------------------------------------------------

A.3. Anonymous CVS

  A.3.1. anoncvs A^2CURP:

   Anonymous CVS (or, as it is otherwise known, anoncvs) is a feature
   provided by the CVS utilities bundled with FreeBSD for
   synchronizing with a remote CVS repository. Among other things, it
   allows users of FreeBSD to perform, with no special privileges,
   read-only CVS operations against one of the FreeBSD project's
   official anoncvs servers. To use it, one simply sets the CVSROOT
   environment variable to point at the appropriate anoncvs server,
   provides the well-known password !S:anoncvs!" with the cvs login
   command, and then uses the cvs(1) command to access it like any
   local repository.

     -a`: The cvs login command, stores the passwords that are used
     for authenticating to the CVS server in a file called .cvspass
     in your HOME directory. If this file does not exist, you might
     get an error when trying to use cvs login for the first time.
     Just make an empty .cvspass file, and retry to login.

   While it can also be said that the CVSup and anoncvs services both
   perform essentially the same function, there are various
   trade-offs which can influence the user's choice of
   synchronization methods. In a nutshell, CVSup is much more
   efficient in its usage of network resources and is by far the most
   technically sophisticated of the two, but at a price. To use
   CVSup, a special client must first be installed and configured
   before any bits can be grabbed, and then only in the fairly large
   chunks which CVSup calls collections.

   Anoncvs, by contrast, can be used to examine anything from an
   individual file to a specific program (like ls or grep) by
   referencing the CVS module name. Of course, anoncvs is also only
   good for read-only operations on the CVS repository, so if it is
   your intention to support local development in one repository
   shared with the FreeBSD project bits then CVSup is really your
   only option.

     --------------------------------------------------------------

  A.3.2. Using Anonymous CVS

   Configuring cvs(1) to use an Anonymous CVS repository is a simple
   matter of setting the CVSROOT environment variable to point to one
   of the FreeBSD project's anoncvs servers. At the time of this
   writing, the following servers are available:

     * Austria(P:o/|aS:Q):
       :pserver:anoncvs@anoncvs.at.FreeBSD.org:/home/ncvs (Use cvs
       login and enter any password when prompted.)

     * France(-akDEGe):
       :pserver:anoncvs@anoncvs.fr.FreeBSD.org:/home/ncvs (pserver
       (password !S:anoncvs!"), ssh (no password))

     * Germany( 1/4wDEGe):
       :pserver:anoncvs@anoncvs.de.FreeBSD.org:/home/ncvs (Use cvs
       login and enter the password !S:anoncvs!" when prompted.)

     * Germany( 1/4wDEGe):
       :pserver:anoncvs@anoncvs2.de.FreeBSD.org:/home/ncvs (rsh,
       pserver, ssh, ssh/2022)

     * Japan(CUReYEN>>):
       :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs (Use cvs
       login and enter the password !S:anoncvs!" when prompted.)

     * USA(NOTu:DEGe): freebsdanoncvs@anoncvs.FreeBSD.org:/home/ncvs
       (ssh only - no password)

 SSH HostKey: 1024 a1:e7:46:de:fb:56:ef:05:bc:73:aa:91:09:da:f7:f4 root@sanmateo.ecn.purdue.edu
 SSH2 HostKey: 1024 52:02:38:1a:2f:a8:71:d3:f5:83:93:8d:aa:00:6f:65 ssh_host_dsa_key.pub

     * USA(NOTu:DEGe): anoncvs@anoncvs1.FreeBSD.org:/home/ncvs (ssh
       only - no password)

 SSH HostKey: 1024 8b:c4:6f:9a:7e:65:8a:eb:50:50:29:7c:a1:47:03:bc root@ender.liquidneon.com
 SSH2 HostKey: 2048 4d:59:19:7b:ea:9b:76:0b:ca:ee:da:26:e2:3a:83:b8 ssh_host_dsa_key.pub

   Since CVS allows one to !S:check out!" virtually any version of
   the FreeBSD sources that ever existed (or, in some cases, will
   exist), you need to be familiar with the revision (-r) flag to
   cvs(1) and what some of the permissible values for it in the
   FreeBSD Project repository are.

   There are two kinds of tags, revision tags and branch tags. A
   revision tag refers to a specific revision. Its meaning stays the
   same from day to day. A branch tag, on the other hand, refers to
   the latest revision on a given line of development, at any given
   time. Because a branch tag does not refer to a specific revision,
   it may mean something different tomorrow than it means today.

   uU A.7 ,` contains revision tags that users might be interested
   in. Again, none of these are valid for the Ports Collection since
   the Ports Collection does not have multiple revisions.

   When you specify a branch tag, you normally receive the latest
   versions of the files on that line of development. If you wish to
   receive some past version, you can do so by specifying a date with
   the -D date flag. See the cvs(1) manual page for more details.

     --------------------------------------------------------------

  A.3.3. Examples

   While it really is recommended that you read the manual page for
   cvs(1) thoroughly before doing anything, here are some quick
   examples which essentially show how to use Anonymous CVS:

   1/2d"O A-1. Checking Out Something from -CURRENT (ls(1)):

 % setenv CVSROOT :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs
 % cvs login
 At the prompt, enter the password !S:anoncvs!".
 % cvs co ls
          

   1/2d"O A-2. Using SSH to check out the src/ tree:

 % cvs -d freebsdanoncvs@anoncvs.FreeBSD.org:/home/ncvs co src
 The authenticity of host 'anoncvs.freebsd.org (128.46.156.46)' can't be established.
 DSA key fingerprint is 52:02:38:1a:2f:a8:71:d3:f5:83:93:8d:aa:00:6f:65.
 Are you sure you want to continue connecting (yes/no)? yes
 Warning: Permanently added 'anoncvs.freebsd.org' (DSA) to the list of known hosts.

   1/2d"O A-3. Checking Out the Version of ls(1) in the 6-STABLE
   Branch:

 % setenv CVSROOT :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs
 % cvs login
 At the prompt, enter the password !S:anoncvs!".
 % cvs co -rRELENG_6 ls
          

   1/2d"O A-4. Creating a List of Changes (as Unified Diffs) to ls(1)

 % setenv CVSROOT :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs
 % cvs login
 At the prompt, enter the password !S:anoncvs!".
 % cvs rdiff -u -rRELENG_5_3_0_RELEASE -rRELENG_5_4_0_RELEASE ls
          

   1/2d"O A-5. Finding Out What Other Module Names Can Be Used:

 % setenv CVSROOT :pserver:anoncvs@anoncvs.jp.FreeBSD.org:/home/ncvs
 % cvs login
 At the prompt, enter the password !S:anoncvs!".
 % cvs co modules
 % more modules/modules
          

     --------------------------------------------------------------

  A.3.4. Other Resources

   The following additional resources may be helpful in learning CVS:

     * CVS Tutorial from Cal Poly.

     * CVS Home, the CVS development and support community.

     * CVSweb is the FreeBSD Project web interface for CVS.

     --------------------------------------------------------------

A.4. Using CTM

   CTM is a method for keeping a remote directory tree in sync with a
   central one. It has been developed for usage with FreeBSD's source
   trees, though other people may find it useful for other purposes
   as time goes by. Little, if any, documentation currently exists at
   this time on the process of creating deltas, so contact the
   ctm-users mailing list for more information and if you wish to use
   CTM for other things.

     --------------------------------------------------------------

  A.4.1. Why Should I Use CTM?

   CTM will give you a local copy of the FreeBSD source trees. There
   are a number of !S:flavors!" of the tree available. Whether you
   wish to track the entire CVS tree or just one of the branches, CTM
   can provide you the information. If you are an active developer on
   FreeBSD, but have lousy or non-existent TCP/IP connectivity, or
   simply wish to have the changes automatically sent to you, CTM was
   made for you. You will need to obtain up to three deltas per day
   for the most active branches. However, you should consider having
   them sent by automatic email. The sizes of the updates are always
   kept as small as possible. This is typically less than 5K, with an
   occasional (one in ten) being 10-50K and every now and then a
   large 100K+ or more coming around.

   You will also need to make yourself aware of the various caveats
   related to working directly from the development sources rather
   than a pre-packaged release. This is particularly true if you
   choose the !S:current!" sources. It is recommended that you read
   Staying current with FreeBSD.

     --------------------------------------------------------------

  A.4.2. What Do I Need to Use CTM?

   You will need two things: The CTM program, and the initial deltas
   to feed it (to get up to !S:current!" levels).

   The CTM program has been part of FreeBSD ever since version 2.0
   was released, and lives in /usr/src/usr.sbin/ctm if you have a
   copy of the source available.

   The !S:deltas!" you feed CTM can be had two ways, FTP or email. If
   you have general FTP access to the Internet then the following FTP
   sites support access to CTM:

   ftp://ftp.FreeBSD.org/pub/FreeBSD/CTM/

   or see section mirrors.

   FTP the relevant directory and fetch the README file, starting
   from there.

   If you wish to get your deltas via email:

   Subscribe to one of the CTM distribution lists. ctm-cvs-cur
   supports the entire CVS tree. ctm-src-cur supports the head of the
   development branch. ctm-src-4 supports the 4.X release branch,
   etc.. (If you do not know how to subscribe yourself to a list,
   click on the list name above or go to
   http://lists.FreeBSD.org/mailman/listinfo and click on the list
   that you wish to subscribe to. The list page should contain all of
   the necessary subscription instructions.)

   When you begin receiving your CTM updates in the mail, you may use
   the ctm_rmail program to unpack and apply them. You can actually
   use the ctm_rmail program directly from a entry in /etc/aliases if
   you want to have the process run in a fully automated fashion.
   Check the ctm_rmail manual page for more details.

     -a`: No matter what method you use to get the CTM deltas, you
     should subscribe to the ctm-announce mailing list. In the
     future, this will be the only place where announcements
     concerning the operations of the CTM system will be posted.
     Click on the list name above and follow the instructions to
     subscribe to the list.

     --------------------------------------------------------------

  A.4.3. Using CTM for the First Time

   Before you can start using CTM deltas, you will need to get to a
   starting point for the deltas produced subsequently to it.

   First you should determine what you already have. Everyone can
   start from an !S:empty!" directory. You must use an initial
   !S:Empty!" delta to start off your CTM supported tree. At some
   point it is intended that one of these !S:started!" deltas be
   distributed on the CD for your convenience, however, this does not
   currently happen.

   Since the trees are many tens of megabytes, you should prefer to
   start from something already at hand. If you have a -RELEASE CD,
   you can copy or extract an initial source from it. This will save
   a significant transfer of data.

   You can recognize these !S:starter!" deltas by the X appended to
   the number (src-cur.3210XEmpty.gz for instance). The designation
   following the X corresponds to the origin of your initial
   !S:seed!". Empty is an empty directory. As a rule a base
   transition from Empty is produced every 100 deltas. By the way,
   they are large! 70 to 80 Megabytes of gzip'd data is common for
   the XEmpty deltas.

   Once you have picked a base delta to start from, you will also
   need all deltas with higher numbers following it.

     --------------------------------------------------------------

  A.4.4. Using CTM in Your Daily Life

   To apply the deltas, simply say:

 # cd /where/ever/you/want/the/stuff
 # ctm -v -v /where/you/store/your/deltas/src-xxx.*

   CTM understands deltas which have been put through gzip, so you do
   not need to gunzip them first, this saves disk space.

   Unless it feels very secure about the entire process, CTM will not
   touch your tree. To verify a delta you can also use the -c flag
   and CTM will not actually touch your tree; it will merely verify
   the integrity of the delta and see if it would apply cleanly to
   your current tree.

   There are other options to CTM as well, see the manual pages or
   look in the sources for more information.

   That is really all there is to it. Every time you get a new delta,
   just run it through CTM to keep your sources up to date.

   Do not remove the deltas if they are hard to download again. You
   just might want to keep them around in case something bad happens.
   Even if you only have floppy disks, consider using fdwrite to make
   a copy.

     --------------------------------------------------------------

  A.4.5. Keeping Your Local Changes

   As a developer one would like to experiment with and change files
   in the source tree. CTM supports local modifications in a limited
   way: before checking for the presence of a file foo, it first
   looks for foo.ctm. If this file exists, CTM will operate on it
   instead of foo.

   This behavior gives us a simple way to maintain local changes:
   simply copy the files you plan to modify to the corresponding file
   names with a .ctm suffix. Then you can freely hack the code, while
   CTM keeps the .ctm file up-to-date.

     --------------------------------------------------------------

  A.4.6. Other Interesting CTM Options

    A.4.6.1. Finding Out Exactly What Would Be Touched by an Update

   You can determine the list of changes that CTM will make on your
   source repository using the -l option to CTM.

   This is useful if you would like to keep logs of the changes, pre-
   or post- process the modified files in any manner, or just are
   feeling a tad paranoid.

     --------------------------------------------------------------

    A.4.6.2. Making Backups Before Updating

   Sometimes you may want to backup all the files that would be
   changed by a CTM update.

   Specifying the -B backup-file option causes CTM to backup all
   files that would be touched by a given CTM delta to backup-file.

     --------------------------------------------------------------

    A.4.6.3. Restricting the Files Touched by an Update

   Sometimes you would be interested in restricting the scope of a
   given CTM update, or may be interested in extracting just a few
   files from a sequence of deltas.

   You can control the list of files that CTM would operate on by
   specifying filtering regular expressions using the -e and -x
   options.

   For example, to extract an up-to-date copy of lib/libc/Makefile
   from your collection of saved CTM deltas, run the commands:

 # cd /where/ever/you/want/to/extract/it/
 # ctm -e '^lib/libc/Makefile' ~ctm/src-xxx.*

   For every file specified in a CTM delta, the -e and -x options are
   applied in the order given on the command line. The file is
   processed by CTM only if it is marked as eligible after all the -e
   and -x options are applied to it.

     --------------------------------------------------------------

  A.4.7. Future Plans for CTM

   Tons of them:

     * Use some kind of authentication into the CTM system, so as to
       allow detection of spoofed CTM updates.

     * Clean up the options to CTM, they became confusing and counter
       intuitive.

     --------------------------------------------------------------

  A.4.8. Miscellaneous Stuff

   There is a sequence of deltas for the ports collection too, but
   interest has not been all that high yet.

     --------------------------------------------------------------

  A.4.9. CTM Mirrors

   CTM/FreeBSD is available via anonymous FTP from the following
   mirror sites. If you choose to obtain CTM via anonymous FTP,
   please try to use a site near you.

   In case of problems, please contact the ctm-users mailing list.

   California, Bay Area, official source

              * ftp://ftp.FreeBSD.org/pub/FreeBSD/development/CTM/

   South Africa, backup server for old deltas

              * ftp://ftp.za.FreeBSD.org/pub/FreeBSD/CTM/

   Taiwan/R.O.C.(YENxAEW/CURCURuO/YENADEGe)

              * ftp://ctm.tw.FreeBSD.org/pub/FreeBSD/development/CTM/

              * ftp://ctm2.tw.FreeBSD.org/pub/FreeBSD/development/CTM/

              * ftp://ctm3.tw.FreeBSD.org/pub/FreeBSD/development/CTM/

   If you did not find a mirror near to you or the mirror is
   incomplete, try to use a search engine such as alltheweb.

     --------------------------------------------------------------

A.5. Using CVSup

  A.5.1. CVSup A^2CURP:

   CVSup is a software package for distributing and updating source
   trees from a master CVS repository on a remote server host. The
   FreeBSD sources are maintained in a CVS repository on a central
   development machine in California. With CVSup, FreeBSD users can
   easily keep their own source trees up to date.

   CVSup uses the so-called pull model of updating. Under the pull
   model, each client asks the server for updates, if and when they
   are wanted. The server waits passively for update requests from
   its clients. Thus all updates are instigated by the client. The
   server never sends unsolicited updates. Users must either run the
   CVSup client manually to get an update, or they must set up a cron
   job to run it automatically on a regular basis.

   The term CVSup, capitalized just so, refers to the entire software
   package. Its main components are the client cvsup which runs on
   each user's machine, and the server cvsupd which runs at each of
   the FreeBSD mirror sites.

   As you read the FreeBSD documentation and mailing lists, you may
   see references to sup. Sup was the predecessor of CVSup, and it
   served a similar purpose. CVSup is used much in the same way as
   sup and, in fact, uses configuration files which are
   backward-compatible with sup's. Sup is no longer used in the
   FreeBSD project, because CVSup is both faster and more flexible.

     --------------------------------------------------------------

  A.5.2. Installation

   The easiest way to install CVSup is to use the precompiled
   net/cvsup package from the FreeBSD packages collection. If you
   prefer to build CVSup from source, you can use the net/cvsup port
   instead. But be forewarned: the net/cvsup port depends on the
   Modula-3 system, which takes a substantial amount of time and disk
   space to download and build.

     -a`: If you are going to be using CVSup on a machine which will
     not have XFree86 or Xorg installed, such as a server, be sure to
     use the port which does not include the CVSup GUI,
     net/cvsup-without-gui.

     --------------------------------------------------------------

  A.5.3. CVSup Configuration

   CVSup's operation is controlled by a configuration file called the
   supfile. There are some sample supfiles in the directory
   /usr/share/examples/cvsup/.

   The information in a supfile answers the following questions for
   CVSup:

     * Which files do you want to receive?

     * Which versions of them do you want?

     * Where do you want to get them from?

     * Where do you want to put them on your own machine?

     * Where do you want to put your status files?

   In the following sections, we will construct a typical supfile by
   answering each of these questions in turn. First, we describe the
   overall structure of a supfile.

   A supfile is a text file. Comments begin with # and extend to the
   end of the line. Lines that are blank and lines that contain only
   comments are ignored.

   Each remaining line describes a set of files that the user wishes
   to receive. The line begins with the name of a !S:collection!", a
   logical grouping of files defined by the server. The name of the
   collection tells the server which files you want. After the
   collection name come zero or more fields, separated by white
   space. These fields answer the questions listed above. There are
   two types of fields: flag fields and value fields. A flag field
   consists of a keyword standing alone, e.g., delete or compress. A
   value field also begins with a keyword, but the keyword is
   followed without intervening white space by = and a second word.
   For example, release=cvs is a value field.

   A supfile typically specifies more than one collection to receive.
   One way to structure a supfile is to specify all of the relevant
   fields explicitly for each collection. However, that tends to make
   the supfile lines quite long, and it is inconvenient because most
   fields are the same for all of the collections in a supfile. CVSup
   provides a defaulting mechanism to avoid these problems. Lines
   beginning with the special pseudo-collection name *default can be
   used to set flags and values which will be used as defaults for
   the subsequent collections in the supfile. A default value can be
   overridden for an individual collection, by specifying a different
   value with the collection itself. Defaults can also be changed or
   augmented in mid-supfile by additional *default lines.

   With this background, we will now proceed to construct a supfile
   for receiving and updating the main source tree of
   FreeBSD-CURRENT.

     * Which files do you want to receive?

       The files available via CVSup are organized into named groups
       called !S:collections!". The collections that are available
       are described in the following section. In this example, we
       wish to receive the entire main source tree for the FreeBSD
       system. There is a single large collection src-all which will
       give us all of that. As a first step toward constructing our
       supfile, we simply list the collections, one per line (in this
       case, only one line):

 src-all

     * Which version(s) of them do you want?

       With CVSup, you can receive virtually any version of the
       sources that ever existed. That is possible because the cvsupd
       server works directly from the CVS repository, which contains
       all of the versions. You specify which one of them you want
       using the tag= and date= value fields.

         A:uS:iBe very careful to specify any tag= fields correctly.
         Some tags are valid only for certain collections of files.
         If you specify an incorrect or misspelled tag, CVSup will
         delete files which you probably do not want deleted. In
         particular, use only tag=. for the ports-* collections.

       The tag= field names a symbolic tag in the repository. There
       are two kinds of tags, revision tags and branch tags. A
       revision tag refers to a specific revision. Its meaning stays
       the same from day to day. A branch tag, on the other hand,
       refers to the latest revision on a given line of development,
       at any given time. Because a branch tag does not refer to a
       specific revision, it may mean something different tomorrow
       than it means today.

       uU A.7 ,` contains branch tags that users might be interested
       in. When specifying a tag in CVSup's configuration file, it
       must be preceded with tag= (RELENG_4 will become
       tag=RELENG_4). Keep in mind that only the tag=. is relevant
       for the Ports Collection.

         A:uS:iBe very careful to type the tag name exactly as shown.
         CVSup cannot distinguish between valid and invalid tags. If
         you misspell the tag, CVSup will behave as though you had
         specified a valid tag which happens to refer to no files at
         all. It will delete your existing sources in that case.

       When you specify a branch tag, you normally receive the latest
       versions of the files on that line of development. If you wish
       to receive some past version, you can do so by specifying a
       date with the date= value field. The cvsup(1) manual page
       explains how to do that.

       For our example, we wish to receive FreeBSD-CURRENT. We add
       this line at the beginning of our supfile:

 *default tag=.

       There is an important special case that comes into play if you
       specify neither a tag= field nor a date= field. In that case,
       you receive the actual RCS files directly from the server's
       CVS repository, rather than receiving a particular version.
       Developers generally prefer this mode of operation. By
       maintaining a copy of the repository itself on their systems,
       they gain the ability to browse the revision histories and
       examine past versions of files. This gain is achieved at a
       large cost in terms of disk space, however.

     * Where do you want to get them from?

       We use the host= field to tell cvsup where to obtain its
       updates. Any of the CVSup mirror sites will do, though you
       should try to select one that is close to you in cyberspace.
       In this example we will use a fictional FreeBSD distribution
       site, cvsup99.FreeBSD.org:

 *default host=cvsup99.FreeBSD.org

       You will need to change the host to one that actually exists
       before running CVSup. On any particular run of cvsup, you can
       override the host setting on the command line, with -h
       hostname.

     * Where do you want to put them on your own machine?

       The prefix= field tells cvsup where to put the files it
       receives. In this example, we will put the source files
       directly into our main source tree, /usr/src. The src
       directory is already implicit in the collections we have
       chosen to receive, so this is the correct specification:

 *default prefix=/usr

     * Where should cvsup maintain its status files?

       The CVSup client maintains certain status files in what is
       called the !S:base!" directory. These files help CVSup to work
       more efficiently, by keeping track of which updates you have
       already received. We will use the standard base directory,
       /var/db:

 *default base=/var/db

       If your base directory does not already exist, now would be a
       good time to create it. The cvsup client will refuse to run if
       the base directory does not exist.

     * Miscellaneous supfile settings:

       There is one more line of boiler plate that normally needs to
       be present in the supfile:

 *default release=cvs delete use-rel-suffix compress

       release=cvs indicates that the server should get its
       information out of the main FreeBSD CVS repository. This is
       virtually always the case, but there are other possibilities
       which are beyond the scope of this discussion.

       delete gives CVSup permission to delete files. You should
       always specify this, so that CVSup can keep your source tree
       fully up-to-date. CVSup is careful to delete only those files
       for which it is responsible. Any extra files you happen to
       have will be left strictly alone.

       use-rel-suffix is ... arcane. If you really want to know about
       it, see the cvsup(1) manual page. Otherwise, just specify it
       and do not worry about it.

       compress enables the use of gzip-style compression on the
       communication channel. If your network link is T1 speed or
       faster, you probably should not use compression. Otherwise, it
       helps substantially.

     * Putting it all together:

       Here is the entire supfile for our example:

 *default tag=.
 *default host=cvsup99.FreeBSD.org
 *default prefix=/usr
 *default base=/var/db
 *default release=cvs delete use-rel-suffix compress

 src-all

     --------------------------------------------------------------

    A.5.3.1. The refuse File

   As mentioned above, CVSup uses a pull method. Basically, this
   means that you connect to the CVSup server, and it says, !S:Here
   is what you can download from me...!", and your client responds
   !S:OK, I will take this, this, this, and this.!" In the default
   configuration, the CVSup client will take every file associated
   with the collection and tag you chose in the configuration file.
   However, this is not always what you want, especially if you are
   synching the doc, ports, or www trees !X!X most people cannot read
   four or five languages, and therefore they do not need to download
   the language-specific files. If you are CVSuping the Ports
   Collection, you can get around this by specifying each collection
   individually (e.g., ports-astrology, ports-biology, etc instead of
   simply saying ports-all). However, since the doc and www trees do
   not have language-specific collections, you must use one of
   CVSup's many nifty features: the refuse file.

   The refuse file essentially tells CVSup that it should not take
   every single file from a collection; in other words, it tells the
   client to refuse certain files from the server. The refuse file
   can be found (or, if you do not yet have one, should be placed) in
   base/sup/. base is defined in your supfile; our defined base is
   /var/db, which means that by default the refuse file is
   /var/db/sup/refuse.

   The refuse file has a very simple format; it simply contains the
   names of files or directories that you do not wish to download.
   For example, if you cannot speak any languages other than English
   and some German, and you do not feel the need to read the German
   translation of documentation, you can put the following in your
   refuse file:

 doc/bn_*
 doc/da_*
 doc/de_*
 doc/el_*
 doc/es_*
 doc/fr_*
 doc/it_*
 doc/ja_*
 doc/nl_*
 doc/no_*
 doc/pl_*
 doc/pt_*
 doc/ru_*
 doc/sr_*
 doc/tr_*
 doc/zh_*

   and so forth for the other languages (you can find the full list
   by browsing the FreeBSD CVS repository).

   With this very useful feature, those users who are on slow links
   or pay by the minute for their Internet connection will be able to
   save valuable time as they will no longer need to download files
   that they will never use. For more information on refuse files and
   other neat features of CVSup, please view its manual page.

     --------------------------------------------------------------

  A.5.4. Running CVSup

   You are now ready to try an update. The command line for doing
   this is quite simple:

 # cvsup supfile

   where supfile is of course the name of the supfile you have just
   created. Assuming you are running under X11, cvsup will display a
   GUI window with some buttons to do the usual things. Press the go
   button, and watch it run.

   Since you are updating your actual /usr/src tree in this example,
   you will need to run the program as root so that cvsup has the
   permissions it needs to update your files. Having just created
   your configuration file, and having never used this program
   before, that might understandably make you nervous. There is an
   easy way to do a trial run without touching your precious files.
   Just create an empty directory somewhere convenient, and name it
   as an extra argument on the command line:

 # mkdir /var/tmp/dest
 # cvsup supfile /var/tmp/dest

   The directory you specify will be used as the destination
   directory for all file updates. CVSup will examine your usual
   files in /usr/src, but it will not modify or delete any of them.
   Any file updates will instead land in /var/tmp/dest/usr/src. CVSup
   will also leave its base directory status files untouched when run
   this way. The new versions of those files will be written into the
   specified directory. As long as you have read access to /usr/src,
   you do not even need to be root to perform this kind of trial run.

   If you are not running X11 or if you just do not like GUIs, you
   should add a couple of options to the command line when you run
   cvsup:

 # cvsup -g -L 2 supfile

   The -g tells CVSup not to use its GUI. This is automatic if you
   are not running X11, but otherwise you have to specify it.

   The -L 2 tells CVSup to print out the details of all the file
   updates it is doing. There are three levels of verbosity, from -L
   0 to -L 2. The default is 0, which means total silence except for
   error messages.

   There are plenty of other options available. For a brief list of
   them, type cvsup -H. For more detailed descriptions, see the
   manual page.

   Once you are satisfied with the way updates are working, you can
   arrange for regular runs of CVSup using cron(8). Obviously, you
   should not let CVSup use its GUI when running it from cron(8).

     --------------------------------------------------------------

  A.5.5. CVSup File Collections

   The file collections available via CVSup are organized
   hierarchically. There are a few large collections, and they are
   divided into smaller sub-collections. Receiving a large collection
   is equivalent to receiving each of its sub-collections. The
   hierarchical relationships among collections are reflected by the
   use of indentation in the list below.

   The most commonly used collections are src-all, and ports-all. The
   other collections are used only by small groups of people for
   specialized purposes, and some mirror sites may not carry all of
   them.

   cvs-all release=cvs

           The main FreeBSD CVS repository, including the
           cryptography code.

                distrib release=cvs

                        Files related to the distribution and
                        mirroring of FreeBSD.

                doc-all release=cvs

                        Sources for the FreeBSD Handbook and other
                        documentation. This does not include files
                        for the FreeBSD web site.

                ports-all release=cvs

                        The FreeBSD Ports Collection.

                          <<n: If you do not want to update the whole
                          of ports-all (the whole ports tree), but
                          use one of the subcollections listed below,
                          make sure that you always update the
                          ports-base subcollection! Whenever
                          something changes in the ports build
                          infrastructure represented by ports-base,
                          it is virtually certain that those changes
                          will be used by !S:real!" ports real soon.
                          Thus, if you only update the !S:real!"
                          ports and they use some of the new
                          features, there is a very high chance that
                          their build will fail with some mysterious
                          error message. The very first thing to do
                          in this case is to make sure that your
                          ports-base subcollection is up to date.

                          <<n: If you are going to be building your
                          own local copy of ports/INDEX, you must
                          accept ports-all (the whole ports tree).
                          Building ports/INDEX with a partial tree is
                          not supported. See the   FAQ.

                             ports-accessibility release=cvs

                                     Software to help disabled users.

                             ports-arabic release=cvs

                                     Arabic language support.

                             ports-archivers release=cvs

                                     Archiving tools.

                             ports-astro release=cvs

                                     Astronomical ports.

                             ports-audio release=cvs

                                     Sound support.

                             ports-base release=cvs

                                     The Ports Collection build
                                     infrastructure - various files
                                     located in the Mk/ and Tools/
                                     subdirectories of /usr/ports.

                                       -a`: Please see the important
                                       warning above: you should
                                       always update this
                                       subcollection, whenever you
                                       update any part of the FreeBSD
                                       Ports Collection!

                             ports-benchmarks release=cvs

                                     Benchmarks.

                             ports-biology release=cvs

                                     Biology.

                             ports-cad release=cvs

                                     Computer aided design tools.

                             ports-chinese release=cvs

                                     Chinese language support.

                             ports-comms release=cvs

                                     Communication software.

                             ports-converters release=cvs

                                     character code converters.

                             ports-databases release=cvs

                                     Databases.

                             ports-deskutils release=cvs

                                     Things that used to be on the
                                     desktop before computers were
                                     invented.

                             ports-devel release=cvs

                                     Development utilities.

                             ports-dns release=cvs

                                     DNS related software.

                             ports-editors release=cvs

                                     Editors.

                             ports-emulators release=cvs

                                     Emulators for other operating
                                     systems.

                             ports-finance release=cvs

                                     Monetary, financial and related
                                     applications.

                             ports-ftp release=cvs

                                     FTP client and server utilities.

                             ports-games release=cvs

                                     Games.

                             ports-german release=cvs

                                     German language support.

                             ports-graphics release=cvs

                                     Graphics utilities.

                             ports-hebrew release=cvs

                                     Hebrew language support.

                             ports-hungarian release=cvs

                                     Hungarian language support.

                             ports-irc release=cvs

                                     Internet Relay Chat utilities.

                             ports-japanese release=cvs

                                     Japanese language support.

                             ports-java release=cvs

                                     Java utilities.

                             ports-korean release=cvs

                                     Korean language support.

                             ports-lang release=cvs

                                     Programming languages.

                             ports-mail release=cvs

                                     Mail software.

                             ports-math release=cvs

                                     Numerical computation software.

                             ports-mbone release=cvs

                                     MBone applications.

                             ports-misc release=cvs

                                     Miscellaneous utilities.

                             ports-multimedia release=cvs

                                     Multimedia software.

                             ports-net release=cvs

                                     Networking software.

                             ports-net-im release=cvs

                                     Instant messaging software.

                             ports-net-mgmt release=cvs

                                     Network management software.

                             ports-net-p2p release=cvs

                                     Peer to peer networking.

                             ports-news release=cvs

                                     USENET news software.

                             ports-palm release=cvs

                                     Software support for Palm(TM)
                                     series.

                             ports-polish release=cvs

                                     Polish language support.

                             ports-portuguese release=cvs

                                     Portuguese language support.

                             ports-print release=cvs

                                     Printing software.

                             ports-russian release=cvs

                                     Russian language support.

                             ports-science release=cvs

                                     Science.

                             ports-security release=cvs

                                     Security utilities.

                             ports-shells release=cvs

                                     Command line shells.

                             ports-sysutils release=cvs

                                     System utilities.

                             ports-textproc release=cvs

                                     text processing utilities (does
                                     not include desktop publishing).

                             ports-ukrainian release=cvs

                                     Ukrainian language support.

                             ports-vietnamese release=cvs

                                     Vietnamese language support.

                             ports-www release=cvs

                                     Software related to the World
                                     Wide Web.

                             ports-x11 release=cvs

                                     Ports to support the X window
                                     system.

                             ports-x11-clocks release=cvs

                                     X11 clocks.

                             ports-x11-fm release=cvs

                                     X11 file managers.

                             ports-x11-fonts release=cvs

                                     X11 fonts and font utilities.

                             ports-x11-toolkits release=cvs

                                     X11 toolkits.

                             ports-x11-servers release=cvs

                                     X11 servers.

                             ports-x11-themes release=cvs

                                     X11 themes.

                             ports-x11-wm release=cvs

                                     X11 window managers.

                projects-all release=cvs

                        Sources for the FreeBSD projects repository.

                src-all release=cvs

                        The main FreeBSD sources, including the
                        cryptography code.

                             src-base release=cvs

                                     Miscellaneous files at the top
                                     of /usr/src.

                             src-bin release=cvs

                                     User utilities that may be
                                     needed in single-user mode
                                     (/usr/src/bin).

                             src-contrib release=cvs

                                     Utilities and libraries from
                                     outside the FreeBSD project,
                                     used relatively unmodified
                                     (/usr/src/contrib).

                             src-crypto release=cvs

                                     Cryptography utilities and
                                     libraries from outside the
                                     FreeBSD project, used relatively
                                     unmodified (/usr/src/crypto).

                             src-eBones release=cvs

                                     Kerberos and DES
                                     (/usr/src/eBones). Not used in
                                     current releases of FreeBSD.

                             src-etc release=cvs

                                     System configuration files
                                     (/usr/src/etc).

                             src-games release=cvs

                                     Games (/usr/src/games).

                             src-gnu release=cvs

                                     Utilities covered by the GNU
                                     Public License (/usr/src/gnu).

                             src-include release=cvs

                                     Header files (/usr/src/include).

                             src-kerberos5 release=cvs

                                     Kerberos5 security package
                                     (/usr/src/kerberos5).

                             src-kerberosIV release=cvs

                                     KerberosIV security package
                                     (/usr/src/kerberosIV).

                             src-lib release=cvs

                                     Libraries (/usr/src/lib).

                             src-libexec release=cvs

                                     System programs normally
                                     executed by other programs
                                     (/usr/src/libexec).

                             src-release release=cvs

                                     Files required to produce a
                                     FreeBSD release
                                     (/usr/src/release).

                             src-sbin release=cvs

                                     System utilities for single-user
                                     mode (/usr/src/sbin).

                             src-secure release=cvs

                                     Cryptographic libraries and
                                     commands (/usr/src/secure).

                             src-share release=cvs

                                     Files that can be shared across
                                     multiple systems
                                     (/usr/src/share).

                             src-sys release=cvs

                                     The kernel (/usr/src/sys).

                             src-sys-crypto release=cvs

                                     Kernel cryptography code
                                     (/usr/src/sys/crypto).

                             src-tools release=cvs

                                     Various tools for the
                                     maintenance of FreeBSD
                                     (/usr/src/tools).

                             src-usrbin release=cvs

                                     User utilities
                                     (/usr/src/usr.bin).

                             src-usrsbin release=cvs

                                     System utilities
                                     (/usr/src/usr.sbin).

                www release=cvs

                        The sources for the FreeBSD WWW site.

   distrib release=self

           The CVSup server's own configuration files. Used by CVSup
           mirror sites.

   gnats release=current

           The GNATS bug-tracking database.

   mail-archive release=current

           FreeBSD mailing list archive.

   www release=current

           The pre-processed FreeBSD WWW site files (not the source
           files). Used by WWW mirror sites.

     --------------------------------------------------------------

  A.5.6. For More Information

   For the CVSup FAQ and other information about CVSup, see The CVSup
   Home Page.

   Most FreeBSD-related discussion of CVSup takes place on the
   FreeBSD technical discussions P:l>> 1/4 1/2 * 3/4A. New versions
   of the software are announced there, as well as on the FreeBSD
   announcements P:l>> 1/4 1/2 * 3/4A.

   Questions and bug reports should be addressed to the author of the
   program at <cvsup-bugs@polstra.com>.

     --------------------------------------------------------------

  A.5.7. CVSup Sites

   CVSup servers for FreeBSD are running at the following sites:

   Central Servers, Primary Mirror Sites, Armenia, Australia,
   Austria, Brazil, Canada, China, Costa Rica, Czech Republic,
   Denmark, Estonia, Finland, France, Germany, Greece, Hungary,
   Iceland, Ireland, Israel, Italy, Japan, Korea, Kuwait, Kyrgyzstan,
   Latvia, Lithuania, Netherlands, New Zealand, Norway, Philippines,
   Poland, Portugal, Romania, Russia, San Marino, Slovak Republic,
   Slovenia, South Africa, Spain, Sweden, Switzerland, Taiwan,
   Thailand, Turkey, Ukraine, United Kingdom, USA.

   (as of UTC)

   Central Servers

              * cvsup.FreeBSD.org

   Primary Mirror Sites

              * cvsup1.FreeBSD.org

              * cvsup2.FreeBSD.org

              * cvsup3.FreeBSD.org

              * cvsup4.FreeBSD.org

              * cvsup5.FreeBSD.org

              * cvsup6.FreeBSD.org

              * cvsup7.FreeBSD.org

              * cvsup8.FreeBSD.org

              * cvsup9.FreeBSD.org

              * cvsup10.FreeBSD.org

              * cvsup11.FreeBSD.org

              * cvsup12.FreeBSD.org

              * cvsup13.FreeBSD.org

              * cvsup14.FreeBSD.org

              * cvsup15.FreeBSD.org

              * cvsup16.FreeBSD.org

              * cvsup18.FreeBSD.org

   Armenia

              * cvsup1.am.FreeBSD.org

   Australia

              * cvsup.au.FreeBSD.org

   Austria

              * cvsup.at.FreeBSD.org

   Brazil

              * cvsup.br.FreeBSD.org

              * cvsup2.br.FreeBSD.org

              * cvsup3.br.FreeBSD.org

              * cvsup4.br.FreeBSD.org

              * cvsup5.br.FreeBSD.org

   Canada

              * cvsup1.ca.FreeBSD.org

   China

              * cvsup.cn.FreeBSD.org

              * cvsup2.cn.FreeBSD.org

   Costa Rica

              * cvsup1.cr.FreeBSD.org

   Czech Republic

              * cvsup.cz.FreeBSD.org

   Denmark

              * cvsup.dk.FreeBSD.org

              * cvsup2.dk.FreeBSD.org

   Estonia

              * cvsup.ee.FreeBSD.org

   Finland

              * cvsup.fi.FreeBSD.org

              * cvsup2.fi.FreeBSD.org

   France

              * cvsup.fr.FreeBSD.org

              * cvsup1.fr.FreeBSD.org

              * cvsup2.fr.FreeBSD.org

              * cvsup3.fr.FreeBSD.org

              * cvsup4.fr.FreeBSD.org

              * cvsup5.fr.FreeBSD.org

              * cvsup8.fr.FreeBSD.org

   Germany

              * cvsup.de.FreeBSD.org

              * cvsup2.de.FreeBSD.org

              * cvsup3.de.FreeBSD.org

              * cvsup4.de.FreeBSD.org

              * cvsup5.de.FreeBSD.org

              * cvsup6.de.FreeBSD.org

              * cvsup7.de.FreeBSD.org

              * cvsup8.de.FreeBSD.org

   Greece

              * cvsup.gr.FreeBSD.org

              * cvsup2.gr.FreeBSD.org

   Hungary

              * cvsup.hu.FreeBSD.org

   Iceland

              * cvsup.is.FreeBSD.org

   Ireland

              * cvsup.ie.FreeBSD.org

              * cvsup2.ie.FreeBSD.org

   Israel

              * cvsup.il.FreeBSD.org

   Italy

              * cvsup.it.FreeBSD.org

   Japan

              * cvsup.jp.FreeBSD.org

              * cvsup2.jp.FreeBSD.org

              * cvsup3.jp.FreeBSD.org

              * cvsup4.jp.FreeBSD.org

              * cvsup5.jp.FreeBSD.org

              * cvsup6.jp.FreeBSD.org

   Korea

              * cvsup.kr.FreeBSD.org

              * cvsup2.kr.FreeBSD.org

              * cvsup3.kr.FreeBSD.org

   Kuwait

              * cvsup1.kw.FreeBSD.org

   Kyrgyzstan

              * cvsup.kg.FreeBSD.org

   Latvia

              * cvsup.lv.FreeBSD.org

              * cvsup2.lv.FreeBSD.org

   Lithuania

              * cvsup.lt.FreeBSD.org

              * cvsup2.lt.FreeBSD.org

              * cvsup3.lt.FreeBSD.org

   Netherlands

              * cvsup.nl.FreeBSD.org

              * cvsup2.nl.FreeBSD.org

              * cvsup3.nl.FreeBSD.org

   New Zealand

              * cvsup.nz.FreeBSD.org

   Norway

              * cvsup.no.FreeBSD.org

   Philippines

              * cvsup1.ph.FreeBSD.org

   Poland

              * cvsup.pl.FreeBSD.org

              * cvsup2.pl.FreeBSD.org

              * cvsup3.pl.FreeBSD.org

   Portugal

              * cvsup.pt.FreeBSD.org

              * cvsup2.pt.FreeBSD.org

              * cvsup3.pt.FreeBSD.org

   Romania

              * cvsup.ro.FreeBSD.org

              * cvsup1.ro.FreeBSD.org

              * cvsup2.ro.FreeBSD.org

              * cvsup3.ro.FreeBSD.org

   Russia

              * cvsup.ru.FreeBSD.org

              * cvsup2.ru.FreeBSD.org

              * cvsup3.ru.FreeBSD.org

              * cvsup4.ru.FreeBSD.org

              * cvsup5.ru.FreeBSD.org

              * cvsup6.ru.FreeBSD.org

              * cvsup7.ru.FreeBSD.org

   San Marino

              * cvsup.sm.FreeBSD.org

   Slovak Republic

              * cvsup.sk.FreeBSD.org

   Slovenia

              * cvsup.si.FreeBSD.org

              * cvsup2.si.FreeBSD.org

   South Africa

              * cvsup.za.FreeBSD.org

              * cvsup2.za.FreeBSD.org

   Spain

              * cvsup.es.FreeBSD.org

              * cvsup2.es.FreeBSD.org

              * cvsup3.es.FreeBSD.org

   Sweden

              * cvsup.se.FreeBSD.org

              * cvsup2.se.FreeBSD.org

   Switzerland

              * cvsup.ch.FreeBSD.org

   Taiwan

              * cvsup.tw.FreeBSD.org

              * cvsup3.tw.FreeBSD.org

              * cvsup4.tw.FreeBSD.org

              * cvsup5.tw.FreeBSD.org

              * cvsup6.tw.FreeBSD.org

              * cvsup7.tw.FreeBSD.org

              * cvsup8.tw.FreeBSD.org

              * cvsup9.tw.FreeBSD.org

              * cvsup10.tw.FreeBSD.org

              * cvsup11.tw.FreeBSD.org

              * cvsup12.tw.FreeBSD.org

              * cvsup13.tw.FreeBSD.org

              * cvsup14.tw.FreeBSD.org

   Thailand

              * cvsup.th.FreeBSD.org

   Turkey

              * cvsup.tr.FreeBSD.org

              * cvsup2.tr.FreeBSD.org

   Ukraine

              * cvsup3.ua.FreeBSD.org

              * cvsup5.ua.FreeBSD.org

              * cvsup6.ua.FreeBSD.org

   United Kingdom

              * cvsup.uk.FreeBSD.org

              * cvsup2.uk.FreeBSD.org

              * cvsup3.uk.FreeBSD.org

              * cvsup4.uk.FreeBSD.org

   USA

              * cvsup1.us.FreeBSD.org

              * cvsup2.us.FreeBSD.org

              * cvsup3.us.FreeBSD.org

              * cvsup4.us.FreeBSD.org

              * cvsup5.us.FreeBSD.org

              * cvsup6.us.FreeBSD.org

              * cvsup7.us.FreeBSD.org

              * cvsup8.us.FreeBSD.org

              * cvsup9.us.FreeBSD.org

              * cvsup10.us.FreeBSD.org

              * cvsup11.us.FreeBSD.org

              * cvsup12.us.FreeBSD.org

              * cvsup13.us.FreeBSD.org

              * cvsup14.us.FreeBSD.org

              * cvsup15.us.FreeBSD.org

              * cvsup16.us.FreeBSD.org

              * cvsup18.us.FreeBSD.org

     --------------------------------------------------------------

A.6. Using Portsnap

  A.6.1. Portsnap A^2CURP:

   Portsnap is a system for securely distributing the FreeBSD ports
   tree. Approximately once an hour, a !S:snapshot!" of the ports
   tree is generated, repackaged, and cryptographically signed. The
   resulting files are then distributed via HTTP.

   Like CVSup, Portsnap uses a pull model of updating: The packaged
   and signed ports trees are placed on a web server which waits
   passively for clients to request files. Users must either run
   portsnap(8) manually to download updates or set up a cron(8) job
   to download updates automatically on a regular basis.

   For technical reasons, Portsnap does not update the !S:live!"
   ports tree in /usr/ports/ directly; instead, it works via a
   compressed copy of the ports tree stored in /var/db/portsnap/ by
   default. This compressed copy is then used to update the live
   ports tree.

     -a`: If Portsnap is installed from the FreeBSD Ports Collection,
     then the default location for its compressed snapshot will be
     /usr/local/portsnap/ instead of /var/db/portsnap/.

     --------------------------------------------------------------

  A.6.2. Installation

   On FreeBSD 6.0 and more recent versions, Portsnap is contained in
   the FreeBSD base system. On older versions of FreeBSD, it can be
   installed using the sysutils/portsnap port.

     --------------------------------------------------------------

  A.6.3. Portsnap Configuration

   Portsnap's operation is controlled by the /etc/portsnap.conf
   configuration file. For most users, the default configuration file
   will suffice; for more details, consult the portsnap.conf(5)
   manual page.

     -a`: If Portsnap is installed from the FreeBSD Ports Collection,
     it will use the configuration file /usr/local/etc/portsnap.conf
     instead of /etc/portsnap.conf. This configuration file is not
     created when the port is installed, but a sample configuration
     file is distributed; to copy it into place, run the following
     command:

 # cd /usr/local/etc && cp portsnap.conf.sample portsnap.conf

     --------------------------------------------------------------

  A.6.4. Running Portsnap for the First Time

   The first time portsnap(8) is run, it will need to download a
   compressed snapshot of the entire ports tree into
   /var/db/portsnap/ (or /usr/local/portsnap/ if Portsnap was
   installed from the Ports Collection). For the beginning of 2006
   this is approximately a 41 MB download.

 # portsnap fetch

   Once the compressed snapshot has been downloaded, a !S:live!" copy
   of the ports tree can be extracted into /usr/ports/. This is
   necessary even if a ports tree has already been created in that
   directory (e.g., by using CVSup), since it establishes a baseline
   from which portsnap can determine which parts of the ports tree
   need to be updated later.

 # portsnap extract

     -a`: In the default installation /usr/ports is not created. If
     you run FreeBSD 6.0-RELEASE, it should be created before
     portsnap is used. On more recent versions of FreeBSD or
     Portsnap, this operation will be done automatically at first use
     of the portsnap command.

     --------------------------------------------------------------

  A.6.5. Updating the Ports Tree

   After an initial compressed snapshot of the ports tree has been
   downloaded and extracted into /usr/ports/, updating the ports tree
   consists of two steps: fetching updates to the compressed
   snapshot, and using them to update the live ports tree. These two
   steps can be specified to portsnap as a single command:

 # portsnap fetch update

     -a`: Some older versions of portsnap do not support this syntax;
     if it fails, try instead the following:

 # portsnap fetch
 # portsnap update

     --------------------------------------------------------------

  A.6.6. Running Portsnap from cron

   In order to avoid problems with !S:flash crowds!" accessing the
   Portsnap servers, portsnap fetch will not run from a cron(8) job.
   Instead, a special portsnap cron command exists, which waits for a
   random duration up to 3600 seconds before fetching updates.

   In addition, it is strongly recommended that portsnap update not
   be run from a cron job, since it is liable to cause major problems
   if it happens to run at the same time as a port is being built or
   installed. However, it is safe to update the ports' INDEX files,
   and this can be done by passing the -I flag to portsnap.
   (Obviously, if portsnap -I update is run from cron, then it will
   be necessary to run portsnap update without the -I flag at a later
   time in order to update the rest of the tree.)

   Adding the following line to /etc/crontab will cause portsnap to
   update its compressed snapshot and the INDEX files in /usr/ports/,
   and will send an email if any installed ports are out of date:

 0 3 * * * root portsnap -I cron update && pkg_version -vIL=

     -a`: If the system clock is not set to the local time zone,
     please replace 3 with a random value between 0 and 23, in order
     to spread the load on the Portsnap servers more evenly.

     -a`: Some older versions of portsnap do not support listing
     multiple commands (e.g., cron update) in the same invocation of
     portsnap. If the line above fails, try replacing portsnap -I
     cron update with portsnap cron && portsnap -I update.

     --------------------------------------------------------------

A.7. CVS Tags

   When obtaining or updating sources using cvs or CVSup, a revision
   tag must be specified. A revision tag refers to either a
   particular line of FreeBSD development, or a specific point in
   time. The first type are called !S:branch tags!", and the second
   type are called !S:release tags!".

     --------------------------------------------------------------

  A.7.1. Branch Tags

   All of these, with the exception of HEAD (which is always a valid
   tag), only apply to the src/ tree. The ports/, doc/, and www/
   trees are not branched.

   HEAD

           Symbolic name for the main line, or FreeBSD-CURRENT. Also
           the default when no revision is specified.

           In CVSup, this tag is represented by a . (not punctuation,
           but a literal . character).

             -a`: In CVS, this is the default when no revision tag is
             specified. It is usually not a good idea to checkout or
             update to CURRENT sources on a STABLE machine, unless
             that is your intent.

   RELENG_6

           The line of development for FreeBSD-6.X, also known as
           FreeBSD 6-STABLE

   RELENG_6_1

           The release branch for FreeBSD-6.1, used only for security
           advisories and other critical fixes.

   RELENG_6_0

           The release branch for FreeBSD-6.0, used only for security
           advisories and other critical fixes.

   RELENG_5

           The line of development for FreeBSD-5.X, also known as
           FreeBSD 5-STABLE.

   RELENG_5_5

           The release branch for FreeBSD-5.5, used only for security
           advisories and other critical fixes.

   RELENG_5_4

           The release branch for FreeBSD-5.4, used only for security
           advisories and other critical fixes.

   RELENG_5_3

           The release branch for FreeBSD-5.3, used only for security
           advisories and other critical fixes.

   RELENG_5_2

           The release branch for FreeBSD-5.2 and FreeBSD-5.2.1, used
           only for security advisories and other critical fixes.

   RELENG_5_1

           The release branch for FreeBSD-5.1, used only for security
           advisories and other critical fixes.

   RELENG_5_0

           The release branch for FreeBSD-5.0, used only for security
           advisories and other critical fixes.

   RELENG_4

           The line of development for FreeBSD-4.X, also known as
           FreeBSD 4-STABLE.

   RELENG_4_11

           The release branch for FreeBSD-4.11, used only for
           security advisories and other critical fixes.

   RELENG_4_10

           The release branch for FreeBSD-4.10, used only for
           security advisories and other critical fixes.

   RELENG_4_9

           The release branch for FreeBSD-4.9, used only for security
           advisories and other critical fixes.

   RELENG_4_8

           The release branch for FreeBSD-4.8, used only for security
           advisories and other critical fixes.

   RELENG_4_7

           The release branch for FreeBSD-4.7, used only for security
           advisories and other critical fixes.

   RELENG_4_6

           The release branch for FreeBSD-4.6 and FreeBSD-4.6.2, used
           only for security advisories and other critical fixes.

   RELENG_4_5

           The release branch for FreeBSD-4.5, used only for security
           advisories and other critical fixes.

   RELENG_4_4

           The release branch for FreeBSD-4.4, used only for security
           advisories and other critical fixes.

   RELENG_4_3

           The release branch for FreeBSD-4.3, used only for security
           advisories and other critical fixes.

   RELENG_3

           The line of development for FreeBSD-3.X, also known as
           3.X-STABLE.

   RELENG_2_2

           The line of development for FreeBSD-2.2.X, also known as
           2.2-STABLE. This branch is mostly obsolete.

     --------------------------------------------------------------

  A.7.2. Release Tags

   These tags refer to a specific point in time when a particular
   version of FreeBSD was released. The release engineering process
   is documented in more detail by the Release Engineering
   Information and Release Process documents. The src tree uses tag
   names that start with RELENG_ tags. The ports and doc trees use
   tags whose names begin with RELEASE tags. Finally, the www tree is
   not tagged with any special name for releases.

   RELENG_6_1_0_RELEASE

           FreeBSD 6.1

   RELENG_6_0_0_RELEASE

           FreeBSD 6.0

   RELENG_5_5_0_RELEASE

           FreeBSD 5.5

   RELENG_5_4_0_RELEASE

           FreeBSD 5.4

   RELENG_4_11_0_RELEASE

           FreeBSD 4.11

   RELENG_5_3_0_RELEASE

           FreeBSD 5.3

   RELENG_4_10_0_RELEASE

           FreeBSD 4.10

   RELENG_5_2_1_RELEASE

           FreeBSD 5.2.1

   RELENG_5_2_0_RELEASE

           FreeBSD 5.2

   RELENG_4_9_0_RELEASE

           FreeBSD 4.9

   RELENG_5_1_0_RELEASE

           FreeBSD 5.1

   RELENG_4_8_0_RELEASE

           FreeBSD 4.8

   RELENG_5_0_0_RELEASE

           FreeBSD 5.0

   RELENG_4_7_0_RELEASE

           FreeBSD 4.7

   RELENG_4_6_2_RELEASE

           FreeBSD 4.6.2

   RELENG_4_6_1_RELEASE

           FreeBSD 4.6.1

   RELENG_4_6_0_RELEASE

           FreeBSD 4.6

   RELENG_4_5_0_RELEASE

           FreeBSD 4.5

   RELENG_4_4_0_RELEASE

           FreeBSD 4.4

   RELENG_4_3_0_RELEASE

           FreeBSD 4.3

   RELENG_4_2_0_RELEASE

           FreeBSD 4.2

   RELENG_4_1_1_RELEASE

           FreeBSD 4.1.1

   RELENG_4_1_0_RELEASE

           FreeBSD 4.1

   RELENG_4_0_0_RELEASE

           FreeBSD 4.0

   RELENG_3_5_0_RELEASE

           FreeBSD-3.5

   RELENG_3_4_0_RELEASE

           FreeBSD-3.4

   RELENG_3_3_0_RELEASE

           FreeBSD-3.3

   RELENG_3_2_0_RELEASE

           FreeBSD-3.2

   RELENG_3_1_0_RELEASE

           FreeBSD-3.1

   RELENG_3_0_0_RELEASE

           FreeBSD-3.0

   RELENG_2_2_8_RELEASE

           FreeBSD-2.2.8

   RELENG_2_2_7_RELEASE

           FreeBSD-2.2.7

   RELENG_2_2_6_RELEASE

           FreeBSD-2.2.6

   RELENG_2_2_5_RELEASE

           FreeBSD-2.2.5

   RELENG_2_2_2_RELEASE

           FreeBSD-2.2.2

   RELENG_2_2_1_RELEASE

           FreeBSD-2.2.1

   RELENG_2_2_0_RELEASE

           FreeBSD-2.2.0

     --------------------------------------------------------------

A.8. AFS Sites

   AFS servers for FreeBSD are running at the following sites:

   Sweden

           The path to the files are:
           /afs/stacken.kth.se/ftp/pub/FreeBSD/

 stacken.kth.se         # Stacken Computer Club, KTH, Sweden
 130.237.234.43         #hot.stacken.kth.se
 130.237.237.230        #fishburger.stacken.kth.se
 130.237.234.3          #milko.stacken.kth.se

           Maintainer <ftp@stacken.kth.se>

     --------------------------------------------------------------

A.9. rsync Sites

   The following sites make FreeBSD available through the rsync
   protocol. The rsync utility works in much the same way as the
   rcp(1) command, but has more options and uses the rsync
   remote-update protocol which transfers only the differences
   between two sets of files, thus greatly speeding up the
   synchronization over the network. This is most useful if you are a
   mirror site for the FreeBSD FTP server, or the CVS repository. The
   rsync suite is available for many operating systems, on FreeBSD,
   see the net/rsync port or use the package.

   Czech Republic

           rsync://ftp.cz.FreeBSD.org/

           Available collections:

              * ftp: A partial mirror of the FreeBSD FTP server.

              * FreeBSD: A full mirror of the FreeBSD FTP server.

   Germany

           rsync://grappa.unix-ag.uni-kl.de/

           Available collections:

              * freebsd-cvs: The full FreeBSD CVS repository.

           This machine also mirrors the CVS repositories of the
           NetBSD and the OpenBSD projects, among others.

   Netherlands

           rsync://ftp.nl.FreeBSD.org/

           Available collections:

              * vol/4/freebsd-core: A full mirror of the FreeBSD FTP
                server.

   United Kingdom

           rsync://rsync.mirror.ac.uk/

           Available collections:

              * ftp.FreeBSD.org: A full mirror of the FreeBSD FTP
                server.

   United States of America

           rsync://ftp-master.FreeBSD.org/

           This server may only be used by FreeBSD primary mirror
           sites.

           Available collections:

              * FreeBSD: The master archive of the FreeBSD FTP
                server.

              * acl: The FreeBSD master ACL list.

           rsync://ftp13.FreeBSD.org/

           Available collections:

              * FreeBSD: A full mirror of the FreeBSD FTP server.

     --------------------------------------------------------------

                        -ath?y B. DEGN|OCURaaA:m

   Ao:uM 1/2uCURW>>!(c)u(manual pages)|^3'-L-"N FreeBSD
   |UO-S(c)w^3!CURA(c)u 1/2T-a-o>>!(c)u!A |yYEN|I<<oAo/S:K|^3!uCURp
   3/4C,|OCURj?o!vCURS: 3/4N!A^1^3NOTO|p|oAAy
   3/4aO"t^2I^1BS:@P:P:-oZ!C |]|^1!A "Aa:|^3 UNIX
   "t^2I-oTH^2z-a-o|n(R)NYENHCURI|n-a-o"IYENICURaYENUNOTOCUR-L-YENi(c)I-E-a-o!C

     --------------------------------------------------------------

B.1. FreeBSD NOTUAo:-a-o(R)NA:y!BAo/>>x

   <<D^>>y-a-o(R)NA:y!BAo/>>x!G

     * FreeBSD CURJ-au>>PA^3YENI(YENu-oD->>"uO/-a(c))
       (AcAAeCURCURCURaa)!A ^3O-oOCURaaCURAE !A1997!C ISBN
       9-578-39435-7

     * FreeBSD S:TH^3NCUR-o^1o (FreeBSD Unleashed
       A^2AAeCURCURA:P:-a(c))!A  3/4-:+-nCURu.~YENX-a(c)-aA !C ISBN
       7-111-10201-0

     * FreeBSD "IYENICURjYENth^2A:CUR@-a(c) (A^2AAeCURCURCURaa)!A 
       3/4-:+-nCURu.~YENX-a(c)-aA!C ISBN 7-111-07482-3

     * FreeBSD "IYENICURjYENth^2A:CURG-a(c) (A^2AAeCURCURCURaa)!A 
       3/4-:+-nCURu.~YENX-a(c)-aA!C ISBN 7-111-10286-X

     * FreeBSD Handbook ^2A:CURG-a(c) (A^2AAeCURCURA:P:-a(c))!A
       CURHYENAP:l^1qYENX-a(c)-aA !C ISBN 7-115-10541-3

     * FreeBSD 3.x Internet DEG-a-AA-aADEGE
       3/4^1-a-oNOT[^3]>>P-oTH^2z (A^2AAeCURCURCURaa)!A ^2MuO/CURj
       3/4C,YENX-a(c)-aA !C ISBN 7-900625-66-6

     * FreeBSD & Windows P:DEG|"^2O-oo^1eDEGE (A^2AAeCURCURCURaa)!A
       CURCURDEGeAAK^1DYENX-a(c)-aA !C ISBN 7-113-03845-X

     * FreeBSD -oo-,NOT[^3]^1eDEGE
       (A^2AAeCURCURCURaa)!ACURCURDEGeAAK^1DYENX-a(c)-aA !C ISBN
       7-113-03423-3

     * FreeBSD for PC 98'ers (CUReCURaa)!ASHUWA SystemCo, LTD !C ISBN
       4-87966-468-5 C3055 (c)w>>u 2900 CUReP:e!C

     * FreeBSD (CUReCURaa)!ACUTT!C ISBN 4-906391-22-2 C3055 (c)w>>u
       2400 CUReP:e!C

     * Complete Introduction to FreeBSD (CUReCURaa)!AShoeisha Co.,
       Ltd!C ISBN 4-88135-473-6 (c)w>>u 3600 CUReP:e!C

     * Personal UNIX Starter Kit FreeBSD (CUReCURaa)!A ASCII!C ISBN
       4-7561-1733-3 (c)w>>u 3000 CUReP:e!C

     * FreeBSD Handbook (CUReCURaaA:P:-a(c))!A ASCII!C ISBN
       4-7561-1580-2 (c)w>>u 3800 CUReP:e!C

     * FreeBSD mit Methode ( 1/4wCURaa)!AComputer und Literatur
       Verlag/Vertrieb Hanser!A1998!C ISBN 3-932311-31-0

     * FreeBSD 4 - Installieren, Konfigurieren, Administrieren (
       1/4wCURaa)!AComputer und Literatur Verlag!A2001!C ISBN
       3-932311-88-4

     * FreeBSD 5 - Installieren, Konfigurieren, Administrieren (
       1/4wCURaa)!AComputer und Literatur Verlag!A2003!C ISBN
       3-936546-06-1

     * FreeBSD de Luxe ( 1/4wCURaa)!A Verlag Modere Industrie!A
       2003!C ISBN 3-8266-1343-0

     * FreeBSD Install and Utilization Manual (CUReCURaa)!AMainichi
       Communications Inc. !A1998!C ISBN 4-8399-0112-0

     * Onno W Purbo, Dodi Maryanto, Syahrial Hubbany, Widjil Widodo  
       Building Internet Server with FreeBSD (|LYENS:CURaa)!AElex
       Media Komputindo!C

     * FreeBSD S:^1YENth+-'-A (Absolute BSD: The Ultimate Guide to
       FreeBSD AcAAeCURCURCURaaA:P:-a(c))!ACURW(c)_!A2003!C ISBN
       986-7944-92-5

     * FreeBSD 6.0NOT[^3]-oTH^2z>>PA^3YENI
       (AcAAeCURCURCURaa)!A^3O-oO!A2006!CISBN 9-575-27878-X

   ^CURaa-a-o(R)NA:y!BAo/>>x!G

     * Absolute BSD: The Ultimate Guide to FreeBSD!A No Starch
       Press!A2002!C ISBN: 1886411743

     * The Complete FreeBSD!A O'Reilly!A2003!C ISBN: 0596005164

     * The FreeBSD Corporate Networker's Guide!A
       Addison-Wesley!A2000!C ISBN: 0201704811

     * FreeBSD: An Open-Source Operating System for Your Personal
       Computer!AThe Bit Tree Press!A2001!C ISBN: 0971204500

     * Teach Yourself FreeBSD in 24 Hours!A Sams!A2002!C ISBN:
       0672324245

     * FreeBSD 6 Unleashed!A Sams!A2006!C ISBN: 0672328755

     * FreeBSD: The Complete Reference!A McGrawHill!A2003!C ISBN:
       0072224096

     --------------------------------------------------------------

B.2. "IYENI>>!(c)uCURaYENU

     * Computer Systems Research Group, UC Berkeley. 4.4BSD User's
       Reference Manual. O'Reilly & Associates, Inc., 1994. ISBN
       1-56592-075-9

     * Computer Systems Research Group, UC Berkeley. 4.4BSD User's
       Supplementary Documents. O'Reilly & Associates, Inc., 1994.
       ISBN 1-56592-076-7

     * UNIX in a Nutshell. O'Reilly & Associates, Inc., 1990. ISBN
       093717520X

     * Mui, Linda. What You Need To Know When You Can't Find Your
       UNIX System Administrator. O'Reilly & Associates, Inc., 1995.
       ISBN 1-56592-104-6

     * Ohio State University |^3 1/4P: 1/4g UNIX CURP:^2D--a-o
       1/2Ou{!A"A'-L-"N HTML (c)I PostScript
       "a-oO/(R)ae|!"NCURHAsA:y!C

       UNIX CURP:^2D--a-o,qCURjS:QCURaaA 1/2A:P:-a(c)
       !A|P(R)EYEN>>CURaaYENoCUR]NOTO FreeBSD Italian Documentation
       Project CURS:CUR@!C

     * Jpman Project, Japan FreeBSD Users Group. FreeBSD User's
       Reference Manual (CUReCURaaA 1/2A:P:)!C Mainichi
       Communications Inc., 1998. ISBN4-8399-0088-4 P3800E.

     * Edinburgh University NOTDEG UNIX .sCURa(c)O 1/4P: 1/4g-a-o
       Online Guide <<u:CURTH>>!(c)u!C

     --------------------------------------------------------------

B.3. "t^2I-oTH^2z<<u:<<n

     * Albitz, Paul and Liu, Cricket. DNS and BIND, 4th Ed. O'Reilly
       & Associates, Inc., 2001. ISBN 1-59600-158-4

     * Computer Systems Research Group, UC Berkeley. 4.4BSD System
       Manager's Manual. O'Reilly & Associates, Inc., 1994. ISBN
       1-56592-080-5

     * Costales, Brian, et al. Sendmail, 2nd Ed. O'Reilly &
       Associates, Inc., 1997. ISBN 1-56592-222-0

     * Frisch, AEleen. Essential System Administration, 2nd Ed.
       O'Reilly & Associates, Inc., 1995. ISBN 1-56592-127-5

     * Hunt, Craig. TCP/IP Network Administration, 2nd Ed. O'Reilly &
       Associates, Inc., 1997. ISBN 1-56592-322-7

     * Nemeth, Evi. UNIX System Administration Handbook. 3rd Ed.
       Prentice Hall, 2000. ISBN 0-13-020601-6

     * Stern, Hal Managing NFS and NIS O'Reilly & Associates, Inc.,
       1991. ISBN 0-937175-75-7

     * Jpman Project, Japan FreeBSD Users Group. FreeBSD System
       Administrator's Manual (CUReCURaaA 1/2A:P:)!C Mainichi
       Communications Inc., 1998. ISBN4-8399-0109-0 P3300E.

     * Dreyfus, Emmanuel. Cahiers de l'Admin: BSD 2nd Ed. (-akCURaa),
       Eyrolles, 2004. ISBN 2-212-11463-X

     --------------------------------------------------------------

B.4. u{|!^3]p(R)v<<u:<<n

     * Asente, Paul, Converse, Diana, and Swick, Ralph. X Window
       System Toolkit. Digital Press, 1998. ISBN 1-55558-178-1

     * Computer Systems Research Group, UC Berkeley. 4.4BSD
       Programmer's Reference Manual. O'Reilly & Associates, Inc.,
       1994. ISBN 1-56592-078-3

     * Computer Systems Research Group, UC Berkeley. 4.4BSD
       Programmer's Supplementary Documents. O'Reilly & Associates,
       Inc., 1994. ISBN 1-56592-079-1

     * Harbison, Samuel P. and Steele, Guy L. Jr. C: A Reference
       Manual. 4th ed. Prentice Hall, 1995. ISBN 0-13-326224-3

     * Kernighan, Brian and Dennis M. Ritchie. The C Programming
       Language. 2nd Ed. PTR Prentice Hall, 1988. ISBN 0-13-110362-8

     * Lehey, Greg. Porting UNIX Software. O'Reilly & Associates,
       Inc., 1995. ISBN 1-56592-126-7

     * Plauger, P. J. The Standard C Library. Prentice Hall, 1992.
       ISBN 0-13-131509-9

     * Spinellis, Diomidis. Code Reading: The Open Source
       Perspective. Addison-Wesley, 2003. ISBN 0-201-79940-5

     * Spinellis, Diomidis. Code Quality: The Open Source
       Perspective. Addison-Wesley, 2006. ISBN 0-321-16607-8

     * Stevens, W. Richard and Stephen A. Rago. Advanced Programming
       in the UNIX Environment. 2nd Ed. Reading, Mass. :
       Addison-Wesley, 2005. ISBN 0-201-43307-9

     * Stevens, W. Richard. UNIX Network Programming. 2nd Ed, PTR
       Prentice Hall, 1998. ISBN 0-13-490012-X

     * Wells, Bill. !S:Writing Serial Drivers for UNIX!". Dr. Dobb's
       Journal. 19(15), December 1994. pp68-71, 97-99.

     --------------------------------------------------------------

B.5. ^2`CURJS:@.~"t^2I

     * Andleigh, Prabhat K. UNIX System Architecture. Prentice-Hall,
       Inc., 1990. ISBN 0-13-949843-5

     * Jolitz, William. !S:Porting UNIX to the 386!". Dr. Dobb's
       Journal. January 1991-July 1992.

     * Leffler, Samuel J., Marshall Kirk McKusick, Michael J Karels
       and John Quarterman The Design and Implementation of the
       4.3BSD UNIX Operating System. Reading, Mass. : Addison-Wesley,
       1989. ISBN 0-201-06196-1

     * Leffler, Samuel J., Marshall Kirk McKusick, The Design and
       Implementation of the 4.3BSD UNIX Operating System: Answer
       Book. Reading, Mass. : Addison-Wesley, 1991. ISBN
       0-201-54629-9

     * McKusick, Marshall Kirk, Keith Bostic, Michael J Karels, and
       John Quarterman. The Design and Implementation of the 4.4BSD
       Operating System. Reading, Mass. : Addison-Wesley, 1996. ISBN
       0-201-54979-4

       (YEN>>(R)N^2A:CURG^3^1-a-o -oo,o-a(c) NOTO FreeBSD
       CURaaYENop^1-o-a-oCUR@^3!YEN-:!AYENHCURI^2A:CURE^3^1-a-o^3!CURAYENiYENH|b
       ^3oAa:S:a:"`i)

     * Marshall Kirk McKusick, George V. Neville-Neil The Design and
       Implementation of the FreeBSD Operating System. Boston, Mass.
       : Addison-Wesley, 2004. ISBN 0-201-70245-2

     * Stevens, W. Richard. TCP/IP Illustrated, Volume 1: The
       Protocols. Reading, Mass. : Addison-Wesley, 1996. ISBN
       0-201-63346-9

     * Schimmel, Curt. Unix Systems for Modern Architectures.
       Reading, Mass. : Addison-Wesley, 1994. ISBN 0-201-63338-8

     * Stevens, W. Richard. TCP/IP Illustrated, Volume 3: TCP for
       Transactions, HTTP, NNTP and the UNIX Domain Protocols.
       Reading, Mass. : Addison-Wesley, 1996. ISBN 0-201-63495-3

     * Vahalia, Uresh. UNIX Internals -- The New Frontiers. Prentice
       Hall, 1996. ISBN 0-13-101908-2

     * Wright, Gary R. and W. Richard Stevens. TCP/IP Illustrated,
       Volume 2: The Implementation. Reading, Mass. : Addison-Wesley,
       1995. ISBN 0-201-63354-X

     --------------------------------------------------------------

B.6. ,e|w>>aDEG`i-a-oDEGN|OCURaaA:m

     * Cheswick, William R. and Steven M. Bellovin. Firewalls and
       Internet Security: Repelling the Wily Hacker. Reading, Mass. :
       Addison-Wesley, 1995. ISBN 0-201-63357-4

     * Garfinkel, Simson and Gene Spafford. Practical UNIX & Internet
       Security. 2nd Ed. O'Reilly & Associates, Inc., 1996. ISBN
       1-56592-148-8

     * Garfinkel, Simson. PGP Pretty Good Privacy O'Reilly &
       Associates, Inc., 1995. ISBN 1-56592-098-8

     --------------------------------------------------------------

B.7. uwAAeCURe+--a-oDEGN|OCURaaA:m

     * Anderson, Don and Tom Shanley. Pentium Processor System
       Architecture. 2nd Ed. Reading, Mass. : Addison-Wesley, 1995.
       ISBN 0-201-40992-5

     * Ferraro, Richard F. Programmer's Guide to the EGA, VGA, and
       Super VGA Cards. 3rd ed. Reading, Mass. : Addison-Wesley,
       1995. ISBN 0-201-62490-7

     * Intel Corporation ^3q+-`.|YENH PDF (R)ae|!|b developer web
       site -oo-,(c)nYENLI-a-o CPU!B'^1CURu^2O!BNOTUAo:
       1/4D-.C,-a-o^3W(R)ae(R)NCURaaYENo!C

     * Shanley, Tom. 80486 System Architecture. 3rd ed. Reading,
       Mass. : Addison-Wesley, 1995. ISBN 0-201-40994-1

     * Shanley, Tom. ISA System Architecture. 3rd ed. Reading, Mass.
       : Addison-Wesley, 1995. ISBN 0-201-40996-8

     * Shanley, Tom. PCI System Architecture. 4th ed. Reading, Mass.
       : Addison-Wesley, 1999. ISBN 0-201-30974-2

     * Van Gilluwe, Frank. The Undocumented PC, 2nd Ed. Reading,
       Mass: Addison-Wesley Pub. Co., 1996. ISBN 0-201-47950-8

     * Messmer, Hans-Peter. The Indispensable PC Hardware Book, 4th
       Ed. Reading, Mass: Addison-Wesley Pub. Co., 2002. ISBN
       0-201-59616-4

     --------------------------------------------------------------

B.8. UNIX  3/4uYENv^2W. 1/2

     * Lion, John Lion's Commentary on UNIX, 6th Ed. With Source
       Code. ITP Media Group, 1996. ISBN 1573980137

     * Raymond, Eric S. The New Hacker's Dictionary, 3rd edition. MIT
       Press, 1996. ISBN 0-262-68092-0. Also known as the Jargon File

     * Salus, Peter H. A quarter century of UNIX. Addison-Wesley
       Publishing Company, Inc., 1994. ISBN 0-201-54777-5

     * Simon Garfinkel, Daniel Weise, Steven Strassmann. The
       UNIX-HATERS Handbook. IDG Books Worldwide, Inc., 1994. ISBN
       1-56884-203-1. Out of print, but available   online.

     * Don Libes, Sandy Ressler Life with UNIX !X!X special edition.
       Prentice-Hall, Inc., 1989. ISBN 0-13-536657-7

     * BSD +-UAD-!G
       http://www.FreeBSD.org/cgi/cvsweb.cgi/src/share/misc/bsd-family-tree
       (c)I FreeBSD  3/4-: 3/4^1CUR-o-a-o
       /usr/share/misc/bsd-family-tree !C

     * The BSD Release Announcements collection. 1997.
       http://www.de.FreeBSD.org/de/ftp/releases/

     * Networked Computer Science Technical Reports Library.
       http://www.ncstrl.org/

     * Old BSD releases from the Computer Systems Research group
       (CSRG). http://www.mckusick.com/csrg/: The 4CD set covers all
       BSD versions from 1BSD to 4.4BSD and 4.4BSD-Lite2 (but not
       2.11BSD, unfortunately). The last disk also holds the final
       sources plus the SCCS files.

     --------------------------------------------------------------

B.9. Ao/>>x!B'AYENZ

     * The C/C++ Users Journal. R&D Publications Inc. ISSN 1075-2838

     * Sys Admin !X!X The Journal for UNIX System Administrators
       Miller Freeman, Inc., ISSN 1061-2688

     * freeX !X!X Das Magazin fu:r Linux - BSD - UNIX ( 1/4wCURaa)
       Computer- und Literaturverlag GmbH, ISSN 1436-7033

     --------------------------------------------------------------

                  -ath?y C. -oo>>U-oo,oCURW-a-o,e. 1/2

   P:i(R)i,S:O:-a-o FreeBSD
   "I+-o^2{|^3-a-o|L"e!BYEN+-'CAAe,oCUR-L-CURWYEN|-a-o^3I.sP:i<< *!I
   CURI|O 1/4AE|`i-a(c)YEN>>-a-o,e.
   1/2!ACUR]^3\|^3(R)E"ACUR-L-NOTO^3I|n!A|y^3q+-`NOTODEGssCUR@CUR@O,oCURW^3I.sP:i(R)i-a-oCURe|!!C
   YEN?YENN(c)o FreeBSD NOTO"O|U(c)o^3\|hS:OCURu-a-oS:VCURO!A(c)OYENH
   1/4sCURj-a-o"IYENI-aI,sCUR]^3q+-`S:e-otuU
   !S:ITS:TH^3NCURa:'(c)^3!-au!" -a-o"CUR|a!C YENunu
   1/2YENI^1qCURlP:lYENo(c)M USENET
   .s>>D,s^2O'NYENiYENH<<U:S:O:^3t|aApA'^3o"C,-aA,sCURF!C

   YENHCURUA^2CURP:>>P FreeBSD -aA,s.fCURW 1/2u-a-oYENDnCURe|!!C
   YS:AAU-a 3/4^1D"a:YENL^3o,I"S|^3|CYENX-a-o,e. 1/2!A 1/2D-S:i-a 3/4
   FreeBSD documentation project P:l>> 1/4 1/2 *
   3/4A!AYENH<<KS:UIS:o.s!C

     --------------------------------------------------------------

C.1. P:l>> 1/4 1/2 * 3/4A(Mailing Lists)

   Ao:uM!ACURj^3!YEN-:-a-o FreeBSD P:}uoCURHu^3-L-|^3NOTY USENET
   .s>>D,s^2O!A
   S:UICUR]CUR-L--`a<<OAOS:UIYENA>>.YENiYENHCURI(R)E+-o-a
   3/4+-z-a-oDEGYAD!C CUR *"a:NOTO!AY+-zYENu|b
   comp.unix.bsd.freebsd.* "a:CURCUR,s^2OCUR-ouoDEGY-a-o,U:!C
   <<O/A:^3+-z+-NDEGYADuo"`i 3/4A.i-a-oP:l>> 1/4 1/2 * 3/4A(mailing
   list)CURW!ACUR-L-|yYENiYENH|P(R)EAAy FreeBSD
   P:}uo-aI(c)M"a:YENLNOTY 3/4I-a
   3/4^1D!A^3q+-`CUR]YENiYENH+-o"`iCUR@O,u|n-a-o(^3IDEG_
   1/2X.|CURn,uS:O:)-a-o|^A^3!C

   YEN>>CURaa<<a+-CURP:^2D--a-oNOTO|U|!CUR-L-|P-a-oP:l>> 1/4 1/2 *
   3/4A!BDEGQ 1/2 *^3W<<h(charter)!C |bq 3/4\YENo|o list CURS:<<e!A
   1/2D-YENy 3/4\AA-aDEGQ 1/2 *^3W<<h!C q 3/4\^3o"C, list
   -a-oCURHI^2{|b"CCURN^3-L-.||NOT"`i 1/4AE|E<<E FreeBSD
   NOTUAo:<<HYENo!C |ODEGQ 1/2
   *^3W<<h-a-o"iq!A<<h|^3S:U(c)o'-L-CURE(c) 1/4|^1DEGQ 1/2 *<<~
   1/2e!C S:_<<h!A^3o"C,DEGQ 1/2 * FreeBSD -a-o list ^2 *+-N^3'CURJ.
   3/4^3qCUR-L-"}!A|OYEN-c-YENh"a:`iYEN>>NOTu:.N!C

   ^1i(c)o,O|bthO list uoDEGYA:+-+-o<<U:-oA'b-a-o(R)EO!A'N"ONOTYNOTY
   !m|p|o|b FreeBSD-questions mailing list CURW+-o"`iYEN?,N!n
   CUR@CURaaS:a

   |buo-aiDEGYAD!B|^AD-"`i list CURS:<<e!A 1/2D-YENyAA-a^1L   FreeBSD
   Mailing Lists +-`"-L-DEGYu-aP:DEG(FAQ) CUR@CURaaYENH 3/4C,.||p|ou
   1/2YENI mailing list !ACUR~-`aA *S:K^1^3NOTO,g+-`<<
   1/2AE-a-oCURe,gCURaa!B 3/4OCURaaCURS:Ath-a-o"AE+-!uoYENI!C

   YENth^3!-a-o mailing lists DEGQ 1/2 *DEGO?y^3-L-YENiYENH|b  
   FreeBSD WWWYEND 3/4-:
   CURWS:a:"`i!CYEN|'-L-"NCURF<<U:'I-a-oAo:Aa:|r.j'MYEN\-`a!AYENiAAy+-zS:a:"`i+-`YENIDEGYu-aP:DEG(FAQ)
   !C|O|b mailing lists CURWuoDEGYCURS:<<e!ACUR]
   1/2D-YENy.j'MNOTOS:_CURw|^3,Nu-a!C

     --------------------------------------------------------------

  C.1.1. List CUR@A:y-ai

   CUR@-e 1/2 * 3/4A!G YENHCURU-a-o list ^3-L-NOTOCUR@-e(c)E
   1/2e!A|OYENBCURj(R)aYENiYENH|UYENN|aDEGN>>P!A
   S:UICUR]^1-aAyCURj(R)aq 3/4\!G

          List |W-oU                                YENO/-a-o                       
cvs-all                        (c)O|^3-a-o FreeBSD '-L-YENae(commit)DEGO?y          
freebsd-advocacy               FreeBSD 'cAA]-oO:u^1qYENx                            
freebsd-announce               CUR 1/2YENNOT<<n"AEYENo!Bp^1-o" 1/2u{,O              
freebsd-arch                   NOT[-ocNOTauoDEGQ 1/2 *                              
freebsd-bugbusters             FreeBSD                                              
                               DEGYAD|^^3o/(PR),e(R)AE(R)w-a-o-ouAA@A:^3AD>>PCURu"a 
freebsd-bugs                   Bug |^^3o/                                           
freebsd-chat                   <<DS:TH^3NYENaeNOTy-a-o FreeBSD -aA,s^2aCURNDEGI     
freebsd-current                DEGQ 1/2 * FreeBSD-CURRENT -a(c)YEN>>-a-o FreeBSD    
freebsd-isp                    FreeBSD -a-o ISP .~-aIS:TH^3NYENaeNOTyDEGI           
freebsd-jobs                   FreeBSD CURHCURO>>E|ae                               
                               FreeBSD Core team -a-o policy CUReDEGwDEGQ 1/2       
freebsd-policy                 *DEGI!C^3o,ICURaa^3^1CUR-L-|h!AYENBYENu core team    
                               CUR~YENiuo"YEN!C                                     
freebsd-questions              "IYENIDEGYADCURIS:TH^3NCURa:'(c)                     
freebsd-security-notifications |wYENth-o|NOT}^3q-a 3/4                              
freebsd-stable                 DEGQ 1/2 * FreeBSD-STABLE -a(c)YEN>>-a-o FreeBSD     
freebsd-test                   1/2 *                                                
                               3/4A.sCURauo-aiDEGI!A^3o,IYENiYENHAAyS:ACURp,O"CURa  

   S:TH^3N 1/2 * 3/4A!G YENHCURU list
   YENDNOTOnYENH+-'DEGQS:TH^3NDEGYADNOTDEGYEND!A |bYEN[CURJq
   3/4\CURIDEGQ 1/2 *CURS:<<e!A 1/2D-DEGEYEN^2YENJ^2O 3/4\AA-a"CO
   list -a-o-a(c)^3W(charter)!A |]NOTDEGYEN|I-a-oDEGQ 1/2
   *CUR-o(R)e^3-L-|^3<<U:A:YAO-a-o"i!C

      List |W-oU                          YENO/-a-o                      
  freebsd-acpi        ACPI YENHCURI^1qCURO-oTH^2zA:^3AD                  
  freebsd-afs         ^2 3/4'O AFS "`i FreeBSD                           
  freebsd-aic7xxx     NOTauo Adaptec AIC 7xxx -a-oAAXDEGEu{|!            
  freebsd-alpha       ^2 3/4'O FreeBSD "`i Alpha "t^2INOT[-oc            
  freebsd-amd64       ^2 3/4'O FreeBSD "`i AMD64 "t^2INOT[-oc            
  freebsd-apache      +-'DEGQ Apache NOTUAo:-a-o ports A:^3AD            
  freebsd-arm         ^2 3/4'O FreeBSD "`i ARM(R) CPU NOT[-oc            
  freebsd-atm         |b FreeBSD CURW"IYENI ATM -oo,o                    
  freebsd-audit       Source code -a-o 1/2](R)O:(audit)p^1-o             
  freebsd-binup       NOTauo binary -a-oCURE-AACURe|!                    
  freebsd-bluetooth   |b FreeBSD CURCUR"IYENIAAA-aTH(Bluetooth)S:TH^3N   
  freebsd-cluster     S:a FreeBSD |bAOP:DEGNOT[-ocAo^1O(clustered        
                      environment)-a-o^1BYENI                            
  freebsd-cvsweb      CVSweb -a-o-ouAA@                                  
  freebsd-database    DEGQ 1/2 *|U|!,e(R)AE(R)w|b FreeBSD                
                      -a-oNOTauo!B^1BYENI                                
  freebsd-doc         1/4P: 1/4g FreeBSD NOTUAo:CURaaYENo                
  freebsd-drivers     1/4P: 1/4g FreeBSD YENI-a-oAAXDEGEu{|!             
  freebsd-eclipse     FreeBSD -a-o Eclipse IDE CURu"a.RYENI-aIYENaeNOTy  
  freebsd-emulation   |b FreeBSD CURW                                    
                      1/4OAA"a:YENL"t^2I!A|p!GLinux!BMS-DOS!BWindows     
  freebsd-firewire    FreeBSD -a-o FireWire(R) (iLink, IEEE 1394)        
                      CURe+-S:TH^3NYENaeNOTy                             
  freebsd-fs          AE(R) *"t^2I-a-o+-'DEGQ!BNOTauo                    
  freebsd-geom        GEOM A:^3AD-a-o+-'DEGQ!BNOTauo                     
  freebsd-gnome       ^2 3/4'O GNOME CURI GNOME NOTUAo:A^3YENI^3nAAe     
  freebsd-hackers     CUR@-eS:TH^3NA:^3AD-a-o+-'DEGQ                     
  freebsd-hardware    FreeBSD CURW-a-o|U|!uwAAeDEGYADYENaeNOTy           
  freebsd-i18n        FreeBSD -a-o|h>>yCURAE(Internationalization)       
  freebsd-ia32        FreeBSD |b IA-32 (Intel x86)                       
                      YENYENxCURW-a-o"IYENI+-'DEGQ                       
  freebsd-ia64        ^2 3/4'O FreeBSD "`i Intel -a-oYEN 1/4"O IA64      
                      YENYENxNOT[-oc                                     
  freebsd-ipfw        ^1i ipfw(IP firewall) -a-oS:TH^3N+-'DEGQ           
  freebsd-isdn        ISDN NOTauo                                        
  freebsd-java        Java u{|!P:}uo-aIYENHCURI^2 3/4'O JDKs "`i FreeBSD 
                      CURW                                               
  freebsd-kde         ^2 3/4'O KDE YENHCURI KDE NOTUAo:A^3YENIu{|!       
  freebsd-lfs         ^2 3/4'O LFS "`i FreeBSD                           
  freebsd-libh        .sYEN@YENN-a-o|w,E!BYEN'YEN](R)MYENo 3/4-:"i       
  freebsd-mips        ^2 3/4'O FreeBSD "`i MIPS(R)                       
  freebsd-mobile      Ao:(c)o|UAth mobile                                
                      computing(CURn|p!GuS:DEGO<<NOT^1q,-L-)-a-oNOTaDEGQ 
  freebsd-mozilla     S:a Mozilla ^3nAAe^2 3/4'O"`i FreeBSD              
  freebsd-multimedia  |U|! 1/4vu^1BYENI!B^3nAAe                          
  freebsd-new-bus     |U|! bus NOT[-oc-a-oS:TH^3N+-'DEGQ                 
  freebsd-net         -oo,o^1BYENI+-'DEGQ>>P TCP/IP source code          
  freebsd-openoffice  ^2 3/4'O OpenOffice.org CURI StarOffice "`i        
                      FreeBSD                                            
  freebsd-performance |bDEG-a(R)A:-`a/t^2u:Ao^1OCURU-a-o(R)A:-`a         
                      1/2O(R)O(tuning)A:^3AD                             
  freebsd-perl        +-'DEGQ Perl NOTUAo: ports -a-o-ouAA@              
  freebsd-pf          pf(packet filter) " 3/4CURoAd- 3/4-:"i-a-o+-'DEGQ  
  freebsd-platforms   DEGQ 1/2 *uU<<(c)o^2 3/4'O port "`i<<D Intel       
                      NOT[-ocYENYENx-a-oA:^3AD                           
  freebsd-ports       Ao:(c)o Ports Collection -a-o^1BYENI!B+-'DEGQ      
  freebsd-ports-bugs  ports NOTUAo:-a-o bugs/PRs                         
  freebsd-ppc         ^2 3/4'O FreeBSD "`i PowerPC(R) "t^2INOT[-oc       
  freebsd-proliant    FreeBSD |b HP ProLiant YEND                        
                      3/4-:YENYENx-a-o"IYENIYENaeNOTy                    
  freebsd-python      Python |b FreeBSD CURW"IYENI-a-o|U|!A:^3AD!C       
                      QA(Quality Assurance)DEGQ 1/2                      
  freebsd-qa          *!A^3q+-`.|"M(c)wNOTOS:_CURw,g"`i^1FYENiYENH       
                      release -a-ou{<< *                                 
  freebsd-rc          rc.d  3/4-:"i-a-oDEGQ 1/2 *!BNOTauo                
  freebsd-realtime    FreeBSD CURW realtime extensions -a-oNOTauo        
  freebsd-scsi        SCSI CURe+-A:^3AD                                  
  freebsd-security    FreeBSD |wYENth-o|NOT}A:^3AD                       
  freebsd-small       |b'OCURJ|!uwAAeAo^1O-a-oA^3YENI!B+-'DEGQ           
  freebsd-smp         CPU ^1i-oU|hCURu^3B^2z(SMP, [A]Symmetric           
                      Multiprocessing)-a-oA^3YENI!BNOTaDEGQ              
  freebsd-sparc64     ^2 3/4'O FreeBSD "`i Sparc(R) YENYENxNOT[-oc       
  freebsd-standards   FreeBSD >>P C99 CURI POSIX                         
                      1/4D-.C,-a-oNOTU(R)eA:^3AD                         
  freebsd-threads     FreeBSD CURW-a-o Threading ^1BYENI!B+-'DEGQ        
  freebsd-testing     FreeBSD -a-o(R)A:-`a>>PA(c)w(c)E'u,O               
  freebsd-tokenring   FreeBSD -a-o Token Ring                            
                      CURa:'(c)-a-oA^3YENI!B+-'DEGQ                      
  freebsd-usb         FreeBSD -a-o USB CURa:'(c)-a-oA^3YENI!B+-'DEGQ     
  freebsd-vuxml       VuXML -o|NOT}^3q^3o/NOT[-oc-a-o+-'DEGQ             
  freebsd-x11         X11 |b FreeBSD -a-o^1BYENI                         

   |^3q 3/4\"i-a-o 1/2 * 3/4A!G YENHCURU-a-o lists
   NOTODEGw^1iCUR@"C,-S(c)wn"D-a-oAA-a-aI|O^3]!A |OYENB"ACUR-L-
   3/4A|X.i|"NOTOCUR@-e-a-oCUR 1/2P:}DEGQ 1/2 *DEGI!C
   +-z^3I|nYENy|bNOTY"C,S:TH^3NDEGQ 1/2
   *DEGIDEGN>>PCUR@NOTq(R)EP:!-a-oDEGQ 1/2 *<<a!A|A?i 3/4U:q
   3/4\^3o"C,|^3"i-a-o 1/2 * 3/4A!C
   |]NOTDEG|p|^1CUR@"O!A+-zYENiYENHCURF,N"`i|b^3o"C,DEGQ 1/2
   *DEGIuo"YEN(c)OP:.-a-oAS:>>o:!C

       List |W-oU                        YENO/-a-o                    
   freebsd-hubs        NOTM(R)g-,YENx(mirror)-a-oYENaeNOTyDEGQ 1/2    
                       *DEGI                                          
   freebsd-user-groups -aA,sP:!-a-o"o 1/2O                            
   freebsd-vendors     Vendors pre-release coordination               
   freebsd-www         www.FreeBSD.org -a-o-oTH^2z-ouAA@              

   1/2 * 3/4A-a-o-oKn-a(c)!G CURWz-a-o|U lists
   ^3-L-|^3-oKn-a(c)(digest)!A |bq 3/4\ list
   CURS:<<a!A'NYENiYENHYENyYENH|UCURv+-b,^1unCURJ!AuM<<aOCURHq
   3/4\?iP:u"-oAa:S:iNOTDEG-oKn-a(c)S:YYENi!C

   CVS lists: YENHCURU-a-o lists NOTO'-L-"Nu^1.QnNOTY|UO tree
   -a-o'-L-YENae(commit)NOTo:?y!A  1/2D--a`.N!GYENLINOTO
   DEGssAA-a(Read-Only) (c)E 1/2e-a-o list
   !A|OYENBCUR-L--`a+-H<<Hu^1^3o!C

 List |W-oU            Source DEGIDEG`i                YEN>>DEGIA^2CURP: (source for)      
cvs-all      /usr/(CVSROOT|doc|ports|projects|src) YENth^3!-a-oAAU:S:oDEGO?y(YEN]NOTA|UAth 
                                                   CVS commit)                             
cvs-doc      /usr/(doc|www)                        doc CURI www trees                      
                                                   -a-o(c)O|^3AAU:S:oNOTo:?y               
cvs-ports    /usr/ports                            ports tree -a-o(c)O|^3AAU:S:oNOTo:?y    
cvs-projects /usr/projects                         projects tree -a-o(c)O|^3AAU:S:oNOTo:?y 
cvs-src      /usr/src                              src tree -a-o(c)O|^3AAU:S:oNOTo:?y      

     --------------------------------------------------------------

  C.1.2. n|p|oq 3/4\

   nq 3/4\ list -a-o,U:!A 1/2D-YENH.AE^1<<<<o:CURUCURWz list |W-oU!A
   (c)INOTO"`i http://lists.FreeBSD.org/mailman/listinfo
   uM<<aS:YYENiNOTD?i|^3?^3 1/2`i-a-o list "Oq 3/4\CURF!A
   ,O-ooP:.|<<u:YENU:S:A|p|oP:i|aeq 3/4\-a-o"BAEJ!C

   To actually post to a given list you simply send mail to
   <listname@FreeBSD.org>. It will then be redistributed to mailing
   list members world-wide.

   To unsubscribe yourself from a list, click on the URL found at the
   bottom of every email received from the list. It is also possible
   to send an email to <listname-unsubscribe@FreeBSD.org> to
   unsubscribe yourself.

   Again, we would like to request that you keep discussion in the
   technical mailing lists on a technical track. If you are only
   interested in important announcements then it is suggested that
   you join the FreeBSD announcements P:l>> 1/4 1/2 * 3/4A, which is
   intended only for infrequent traffic.

     --------------------------------------------------------------

  C.1.3. List Charters

   All FreeBSD mailing lists have certain basic rules which must be
   adhered to by anyone using them. Failure to comply with these
   guidelines will result in two (2) written warnings from the
   FreeBSD Postmaster <postmaster@FreeBSD.org>, after which, on a
   third offense, the poster will removed from all FreeBSD mailing
   lists and filtered from further posting to them. We regret that
   such rules and measures are necessary at all, but today's Internet
   is a pretty harsh environment, it would seem, and many fail to
   appreciate just how fragile some of its mechanisms are.

   Rules of the road:

     * The topic of any posting should adhere to the basic charter of
       the list it is posted to, e.g. if the list is about technical
       issues then your posting should contain technical discussion.
       Ongoing irrelevant chatter or flaming only detracts from the
       value of the mailing list for everyone on it and will not be
       tolerated. For free-form discussion on no particular topic,
       the FreeBSD chat P:l>> 1/4 1/2 * 3/4A is freely available and
       should be used instead.

     * No posting should be made to more than 2 mailing lists, and
       only to 2 when a clear and obvious need to post to both lists
       exists. For most lists, there is already a great deal of
       subscriber overlap and except for the most esoteric mixes (say
       !S:-stable & -scsi!"), there really is no reason to post to
       more than one list at a time. If a message is sent to you in
       such a way that multiple mailing lists appear on the Cc line
       then the Cc line should also be trimmed before sending it out
       again. You are still responsible for your own cross-postings,
       no matter who the originator might have been.

     * Personal attacks and profanity (in the context of an argument)
       are not allowed, and that includes users and developers alike.
       Gross breaches of netiquette, like excerpting or reposting
       private mail when permission to do so was not and would not be
       forthcoming, are frowned upon but not specifically enforced.
       However, there are also very few cases where such content
       would fit within the charter of a list and it would therefore
       probably rate a warning (or ban) on that basis alone.

     * Advertising of non-FreeBSD related products or services is
       strictly prohibited and will result in an immediate ban if it
       is clear that the offender is advertising by spam.

   Individual list charters:

   freebsd-acpi

           ACPI and power management development

   freebsd-afs

           Andrew File System

           This list is for discussion on porting and using AFS from
           CMU/Transarc

   freebsd-announce

           Important events / milestones

           This is the mailing list for people interested only in
           occasional announcements of significant FreeBSD events.
           This includes announcements about snapshots and other
           releases. It contains announcements of new FreeBSD
           capabilities. It may contain calls for volunteers etc.
           This is a low volume, strictly moderated mailing list.

   freebsd-arch

           Architecture and design discussions

           This list is for discussion of the FreeBSD architecture.
           Messages will mostly be kept strictly technical in nature.
           Examples of suitable topics are:

              * How to re-vamp the build system to have several
                customized builds running at the same time.

              * What needs to be fixed with VFS to make Heidemann
                layers work.

              * How do we change the device driver interface to be
                able to use the same drivers cleanly on many buses
                and architectures.

              * How to write a network driver.

   freebsd-audit

           Source code audit project

           This is the mailing list for the FreeBSD source code audit
           project. Although this was originally intended for
           security-related changes, its charter has been expanded to
           review any code changes.

           This list is very heavy on patches, and is probably of no
           interest to the average FreeBSD user. Security discussions
           not related to a particular code change are held on
           freebsd-security. Conversely, all developers are
           encouraged to send their patches here for review,
           especially if they touch a part of the system where a bug
           may adversely affect the integrity of the system.

   freebsd-binup

           FreeBSD Binary Update Project

           This list exists to provide discussion for the binary
           update system, or binup. Design issues, implementation
           details, patches, bug reports, status reports, feature
           requests, commit logs, and all other things related to
           binup are fair game.

   freebsd-bluetooth

           Bluetooth in FreeBSD

           This is the forum where FreeBSD's Bluetooth users
           congregate. Design issues, implementation details,
           patches, bug reports, status reports, feature requests,
           and all matters related to Bluetooth are fair game.

   freebsd-bugbusters

           Coordination of the Problem Report handling effort

           The purpose of this list is to serve as a coordination and
           discussion forum for the Bugmeister, his Bugbusters, and
           any other parties who have a genuine interest in the PR
           database. This list is not for discussions about specific
           bugs, patches or PRs.

   freebsd-bugs

           Bug reports

           This is the mailing list for reporting bugs in FreeBSD.
           Whenever possible, bugs should be submitted using the
           send-pr(1) command or the WEB interface to it.

   freebsd-chat

           Non technical items related to the FreeBSD community

           This list contains the overflow from the other lists about
           non-technical, social information. It includes discussion
           about whether Jordan looks like a toon ferret or not,
           whether or not to type in capitals, who is drinking too
           much coffee, where the best beer is brewed, who is brewing
           beer in their basement, and so on. Occasional
           announcements of important events (such as upcoming
           parties, weddings, births, new jobs, etc) can be made to
           the technical lists, but the follow ups should be directed
           to this -chat list.

   freebsd-core

           FreeBSD core team

           This is an internal mailing list for use by the core
           members. Messages can be sent to it when a serious
           FreeBSD-related matter requires arbitration or high-level
           scrutiny.

   freebsd-current

           Discussions about the use of FreeBSD-CURRENT

           This is the mailing list for users of FreeBSD-CURRENT. It
           includes warnings about new features coming out in
           -CURRENT that will affect the users, and instructions on
           steps that must be taken to remain -CURRENT. Anyone
           running !S:CURRENT!" must subscribe to this list. This is
           a technical mailing list for which strictly technical
           content is expected.

   freebsd-cvsweb

           FreeBSD CVSweb Project

           Technical discussions about use, development and
           maintenance of FreeBSD-CVSweb.

   freebsd-doc

           Documentation project

           This mailing list is for the discussion of issues and
           projects related to the creation of documentation for
           FreeBSD. The members of this mailing list are collectively
           referred to as !S:The FreeBSD Documentation Project!". It
           is an open list; feel free to join and contribute!

   freebsd-drivers

           Writing device drivers for FreeBSD

           This is a forum for technical discussions related to
           device drivers on FreeBSD. It is primarily a place for
           device driver writers to ask questions about how to write
           device drivers using the APIs in the FreeBSD kernel.

   freebsd-eclipse

           FreeBSD users of Eclipse IDE, tools, rich client
           applications and ports.

           The intention of this list is to provide mutual support
           for everything to do with choosing, installing, using,
           developing and maintaining the Eclipse IDE, tools, rich
           client applications on the FreeBSD platform and assisting
           with the porting of Eclipse IDE and plugins to the FreeBSD
           environment.

           The intention is also to facilitate exchange of
           information between the Eclipse community and the FreeBSD
           community to the mutual benefit of both.

           Although this list is focused primarily on the needs of
           Eclipse users it will also provide a forum for those who
           would like to develop FreeBSD specific applications using
           the Eclipse framework.

   freebsd-emulation

           Emulation of other systems such as Linux/MS-DOS/Windows

           This is a forum for technical discussions related to
           running programs written for other operating systems on
           FreeBSD.

   freebsd-firewire

           FireWire (iLink, IEEE 1394)

           This is a mailing list for discussion of the design and
           implementation of a FireWire (aka IEEE 1394 aka iLink)
           subsystem for FreeBSD. Relevant topics specifically
           include the standards, bus devices and their protocols,
           adapter boards/cards/chips sets, and the architecture and
           implementation of code for their proper support.

   freebsd-fs

           File systems

           Discussions concerning FreeBSD file systems. This is a
           technical mailing list for which strictly technical
           content is expected.

   freebsd-geom

           GEOM

           Discussions specific to GEOM and related implementations.
           This is a technical mailing list for which strictly
           technical content is expected.

   freebsd-gnome

           GNOME

           Discussions concerning The GNOME Desktop Environment for
           FreeBSD systems. This is a technical mailing list for
           which strictly technical content is expected.

   freebsd-ipfw

           IP Firewall

           This is the forum for technical discussions concerning the
           redesign of the IP firewall code in FreeBSD. This is a
           technical mailing list for which strictly technical
           content is expected.

   freebsd-ia64

           Porting FreeBSD to IA64

           This is a technical mailing list for individuals actively
           working on porting FreeBSD to the IA-64 platform from
           Intel, to bring up problems or discuss alternative
           solutions. Individuals interested in following the
           technical discussion are also welcome.

   freebsd-isdn

           ISDN Communications

           This is the mailing list for people discussing the
           development of ISDN support for FreeBSD.

   freebsd-java

           Java Development

           This is the mailing list for people discussing the
           development of significant Java applications for FreeBSD
           and the porting and maintenance of JDKs.

   freebsd-jobs

           Jobs offered and sought

           This is a forum for posting employment notices and resumes
           specifically related to FreeBSD, e.g. if you are seeking
           FreeBSD-related employment or have a job involving FreeBSD
           to advertise then this is the right place. This is not a
           mailing list for general employment issues since adequate
           forums for that already exist elsewhere.

           Note that this list, like other FreeBSD.org mailing lists,
           is distributed worldwide. Thus, you need to be clear about
           location and the extent to which telecommuting or
           assistance with relocation is available.

           Email should use open formats only !X!X preferably plain
           text, but basic Portable Document Format (PDF), HTML, and
           a few others are acceptable to many readers. Closed
           formats such as Microsoft Word (.doc) will be rejected by
           the mailing list server.

   freebsd-kde

           KDE

           Discussions concerning KDE on FreeBSD systems. This is a
           technical mailing list for which strictly technical
           content is expected.

   freebsd-hackers

           Technical discussions

           This is a forum for technical discussions related to
           FreeBSD. This is the primary technical mailing list. It is
           for individuals actively working on FreeBSD, to bring up
           problems or discuss alternative solutions. Individuals
           interested in following the technical discussion are also
           welcome. This is a technical mailing list for which
           strictly technical content is expected.

   freebsd-hardware

           General discussion of FreeBSD hardware

           General discussion about the types of hardware that
           FreeBSD runs on, various problems and suggestions
           concerning what to buy or avoid.

   freebsd-hubs

           Mirror sites

           Announcements and discussion for people who run FreeBSD
           mirror sites.

   freebsd-isp

           Issues for Internet Service Providers

           This mailing list is for discussing topics relevant to
           Internet Service Providers (ISPs) using FreeBSD. This is a
           technical mailing list for which strictly technical
           content is expected.

   freebsd-openoffice

           OpenOffice.org

           Discussions concerning the porting and maintenance of
           OpenOffice.org and StarOffice.

   freebsd-performance

           Discussions about tuning or speeding up FreeBSD

           This mailing list exists to provide a place for hackers,
           administrators, and/or concerned parties to discuss
           performance related topics pertaining to FreeBSD.
           Acceptable topics includes talking about FreeBSD
           installations that are either under high load, are
           experiencing performance problems, or are pushing the
           limits of FreeBSD. Concerned parties that are willing to
           work toward improving the performance of FreeBSD are
           highly encouraged to subscribe to this list. This is a
           highly technical list ideally suited for experienced
           FreeBSD users, hackers, or administrators interested in
           keeping FreeBSD fast, robust, and scalable. This list is
           not a question-and-answer list that replaces reading
           through documentation, but it is a place to make
           contributions or inquire about unanswered performance
           related topics.

   freebsd-pf

           Discussion and questions about the packet filter firewall
           system

           Discussion concerning the packet filter (pf) firewall
           system in terms of FreeBSD. Technical discussion and user
           questions are both welcome. This list is also a place to
           discuss the ALTQ QoS framework.

   freebsd-platforms

           Porting to Non Intel platforms

           Cross-platform FreeBSD issues, general discussion and
           proposals for non Intel FreeBSD ports. This is a technical
           mailing list for which strictly technical content is
           expected.

   freebsd-policy

           Core team policy decisions

           This is a low volume, read-only mailing list for FreeBSD
           Core Team Policy decisions.

   freebsd-ports

           Discussion of !S:ports!"

           Discussions concerning FreeBSD's !S:ports collection!"
           (/usr/ports), ports infrastructure, and general ports
           coordination efforts. This is a technical mailing list for
           which strictly technical content is expected.

   freebsd-ports-bugs

           Discussion of !S:ports!" bugs

           Discussions concerning problem reports for FreeBSD's
           !S:ports collection!" (/usr/ports), proposed ports, or
           modifications to ports. This is a technical mailing list
           for which strictly technical content is expected.

   freebsd-proliant

           Technical discussion of FreeBSD on HP ProLiant server
           platforms

           This mailing list is to be used for the technical
           discussion of the usage of FreeBSD on HP ProLiant servers,
           including the discussion of ProLiant-specific drivers,
           management software, configuration tools, and BIOS
           updates. As such, this is the primary place to discuss the
           hpasmd, hpasmcli, and hpacucli modules.

   freebsd-python

           Python on FreeBSD

           This is a list for discussions related to improving
           Python-support on FreeBSD. This is a technical mailing
           list. It is for individuals working on porting Python, its
           3rd party modules and Zope stuff to FreeBSD. Individuals
           interested in following the technical discussion are also
           welcome.

   freebsd-questions

           User questions

           This is the mailing list for questions about FreeBSD. You
           should not send !S:how to!" questions to the technical
           lists unless you consider the question to be pretty
           technical.

   freebsd-scsi

           SCSI subsystem

           This is the mailing list for people working on the SCSI
           subsystem for FreeBSD. This is a technical mailing list
           for which strictly technical content is expected.

   freebsd-security

           Security issues

           FreeBSD computer security issues (DES, Kerberos, known
           security holes and fixes, etc). This is a technical
           mailing list for which strictly technical discussion is
           expected. Note that this is not a question-and-answer
           list, but that contributions (BOTH question AND answer) to
           the FAQ are welcome.

   freebsd-security-notifications

           Security Notifications

           Notifications of FreeBSD security problems and fixes. This
           is not a discussion list. The discussion list is
           FreeBSD-security.

   freebsd-small

           Using FreeBSD in embedded applications

           This list discusses topics related to unusually small and
           embedded FreeBSD installations. This is a technical
           mailing list for which strictly technical content is
           expected.

   freebsd-stable

           Discussions about the use of FreeBSD-STABLE

           This is the mailing list for users of FreeBSD-STABLE. It
           includes warnings about new features coming out in -STABLE
           that will affect the users, and instructions on steps that
           must be taken to remain -STABLE. Anyone running
           !S:STABLE!" should subscribe to this list. This is a
           technical mailing list for which strictly technical
           content is expected.

   freebsd-standards

           C99 & POSIX Conformance

           This is a forum for technical discussions related to
           FreeBSD Conformance to the C99 and the POSIX standards.

   freebsd-usb

           Discussing FreeBSD support for USB

           This is a mailing list for technical discussions related
           to FreeBSD support for USB.

   freebsd-user-groups

           User Group Coordination List

           This is the mailing list for the coordinators from each of
           the local area Users Groups to discuss matters with each
           other and a designated individual from the Core Team. This
           mail list should be limited to meeting synopsis and
           coordination of projects that span User Groups.

   freebsd-vendors

           Vendors

           Coordination discussions between The FreeBSD Project and
           Vendors of software and hardware for FreeBSD.

     --------------------------------------------------------------

  C.1.4. Filtering on the Mailing Lists

   The FreeBSD mailing lists are filtered in multiple ways to avoid
   the distribution of spam, viruses, and other unwanted emails. The
   filtering actions described in this section do not include all
   those used to protect the mailing lists.

   Only certain types of attachments are allowed on the mailing
   lists. All attachments with a MIME content type not found in the
   list below will be stripped before an email is distributed on the
   mailing lists.

     * application/octet-stream

     * application/pdf

     * application/pgp-signature

     * application/x-pkcs7-signature

     * message/rfc822

     * multipart/alternative

     * multipart/related

     * multipart/signed

     * text/html

     * text/plain

     * text/x-diff

     * text/x-patch

     -a`: Some of the mailing lists might allow attachments of other
     MIME content types, but the above list should be applicable for
     most of the mailing lists.

   If an email contains both an HTML and a plain text version, the
   HTML version will be removed. If an email contains only an HTML
   version, it will be converted to plain text.

     --------------------------------------------------------------

C.2. Usenet Newsgroups

   In addition to two FreeBSD specific newsgroups, there are many
   others in which FreeBSD is discussed or are otherwise relevant to
   FreeBSD users. Keyword searchable archives are available for some
   of these newsgroups from courtesy of Warren Toomey
   <wkt@cs.adfa.edu.au>.

     --------------------------------------------------------------

  C.2.1. BSD Specific Newsgroups

     * comp.unix.bsd.freebsd.announce

     * comp.unix.bsd.freebsd.misc

     * de.comp.os.unix.bsd (German)

     * fr.comp.os.bsd (French)

     * it.comp.os.freebsd (Italian)

     --------------------------------------------------------------

  C.2.2. Other UNIX Newsgroups of Interest

     * comp.unix

     * comp.unix.questions

     * comp.unix.admin

     * comp.unix.programmer

     * comp.unix.shell

     * comp.unix.user-friendly

     * comp.security.unix

     * comp.sources.unix

     * comp.unix.advocacy

     * comp.unix.misc

     * comp.bugs.4bsd

     * comp.bugs.4bsd.ucb-fixes

     * comp.unix.bsd

     --------------------------------------------------------------

  C.2.3. X Window System

     * comp.windows.x.i386unix

     * comp.windows.x

     * comp.windows.x.apps

     * comp.windows.x.announce

     * comp.windows.x.intrinsics

     * comp.windows.x.motif

     * comp.windows.x.pex

     * comp.emulators.ms-windows.wine

     --------------------------------------------------------------

C.3. World Wide Web Servers

   Central Servers, Armenia, Australia, Austria, Belgium, Brazil,
   Canada, China, Costa Rica, Czech Republic, Denmark, Estonia,
   Finland, France, Germany, Greece, Hong Kong, Hungary, Iceland,
   Italy, Japan, Korea, Kuwait, Kyrgyzstan, Latvia, Lithuania,
   Netherlands, Norway, Philippines, Portugal, Romania, Russia, San
   Marino, Slovak Republic, Slovenia, South Africa, Spain, Sweden,
   Switzerland, Taiwan, Thailand, Turkey, Ukraine, United Kingdom,
   USA.

   (as of UTC)

     * Central Servers

          *  http://www.FreeBSD.org/

     * Armenia

          * http://www1.am.FreeBSD.org/ (IPv6)

     * Australia

          *  http://www.au.FreeBSD.org/

          *  http://www2.au.FreeBSD.org/

     * Austria

          * http://www.at.FreeBSD.org/ (IPv6)

     * Belgium

          *  http://freebsd.unixtech.be/

     * Brazil

          * http://www.br.FreeBSD.org/ (IPv6)

          *  http://www2.br.FreeBSD.org/www.freebsd.org/

          *  http://www3.br.FreeBSD.org/

     * Canada

          *  http://www.ca.FreeBSD.org/

          *  http://www2.ca.FreeBSD.org/

     * China

          *  http://www.cn.FreeBSD.org/

     * Costa Rica

          *  http://www1.cr.FreeBSD.org/

     * Czech Republic

          * http://www.cz.FreeBSD.org/ (IPv6)

     * Denmark

          * http://www.dk.FreeBSD.org/ (IPv6)

     * Estonia

          *  http://www.ee.FreeBSD.org/

     * Finland

          *  http://www.fi.FreeBSD.org/

          *  http://www2.fi.FreeBSD.org/

     * France

          *  http://www.fr.FreeBSD.org/

          *  http://www1.fr.FreeBSD.org/

     * Germany

          *  http://www.de.FreeBSD.org/

     * Greece

          *  http://www.gr.FreeBSD.org/

     * Hong Kong

          *  http://www.hk.FreeBSD.org/

     * Hungary

          *  http://www.hu.FreeBSD.org/

          *  http://www2.hu.FreeBSD.org/

     * Iceland

          *  http://www.is.FreeBSD.org/

     * Italy

          *  http://www.it.FreeBSD.org/

          *  http://www.gufi.org/mirrors/www.freebsd.org/data/

     * Japan

          * http://www.jp.FreeBSD.org/www.FreeBSD.org/ (IPv6)

     * Korea

          *  http://www.kr.FreeBSD.org/

          *  http://www2.kr.FreeBSD.org/

     * Kuwait

          *  http://www.kw.FreeBSD.org/

     * Kyrgyzstan

          *  http://www.kg.FreeBSD.org/

     * Latvia

          *  http://www.lv.FreeBSD.org/

          *  http://www2.lv.FreeBSD.org/

     * Lithuania

          *  http://www.lt.FreeBSD.org/

     * Netherlands

          *  http://www.nl.FreeBSD.org/

          *  http://www2.nl.FreeBSD.org/

     * Norway

          *  http://www.no.FreeBSD.org/

     * Philippines

          *  http://www.FreeBSD.org.ph/

     * Portugal

          *  http://www.pt.FreeBSD.org/

          *  http://www1.pt.FreeBSD.org/

          *  http://www4.pt.FreeBSD.org/

          *  http://www5.pt.FreeBSD.org/

     * Romania

          *  http://www.ro.FreeBSD.org/

          *  http://www1.ro.FreeBSD.org/

          *  http://www2.ro.FreeBSD.org/

          *  http://www3.ro.FreeBSD.org/

     * Russia

          *  http://www.ru.FreeBSD.org/

          *  http://www2.ru.FreeBSD.org/

          *  http://www3.ru.FreeBSD.org/

          *  http://www4.ru.FreeBSD.org/

          *  http://www5.ru.FreeBSD.org/

     * San Marino

          *  http://www.sm.FreeBSD.org/

     * Slovak Republic

          *  http://www.sk.FreeBSD.org/

     * Slovenia

          *  http://www.si.FreeBSD.org/

          *  http://www2.si.FreeBSD.org/

     * South Africa

          *  http://www.za.FreeBSD.org/

          *  http://www2.za.FreeBSD.org/

     * Spain

          *  http://www.es.FreeBSD.org/

          *  http://www2.es.FreeBSD.org/

          *  http://www3.es.FreeBSD.org/

     * Sweden

          *  http://www.se.FreeBSD.org/

          *  http://www2.se.FreeBSD.org/

     * Switzerland

          * http://www.ch.FreeBSD.org/ (IPv6)

          * http://www2.ch.FreeBSD.org/ (IPv6)

     * Taiwan

          * http://www.tw.FreeBSD.org/ (IPv6)

          *  http://www2.tw.FreeBSD.org/

          *  http://www3.tw.FreeBSD.org/

          *  http://www4.tw.FreeBSD.org/

          * http://www5.tw.FreeBSD.org/ (IPv6)

          *  http://www6.tw.FreeBSD.org/

          *  http://www7.tw.FreeBSD.org/

     * Thailand

          *  http://www.th.FreeBSD.org/

     * Turkey

          *  http://www.tr.FreeBSD.org/

          *  http://www2.tr.FreeBSD.org/

          * http://www3.tr.FreeBSD.org/ (IPv6)

     * Ukraine

          *  http://www.ua.FreeBSD.org/

          *  http://www2.ua.FreeBSD.org/

          *  http://www5.ua.FreeBSD.org/

          *  http://www4.ua.FreeBSD.org/

     * United Kingdom

          *  http://www1.uk.FreeBSD.org/

          *  http://www3.uk.FreeBSD.org/

     * USA

          *  http://www2.us.FreeBSD.org/

          * http://www5.us.FreeBSD.org/ (IPv6)

     --------------------------------------------------------------

C.4. Email Addresses

   The following user groups provide FreeBSD related email addresses
   for their members. The listed administrator reserves the right to
   revoke the address if it is abused in any way.

      Domain        Facilities           User Group              Administrator     
ukug.uk.FreeBSD.org Forwarding <freebsd-users@uk.FreeBSD.org> Lee Johnston         
                    only                                      <lee@uk.FreeBSD.org> 

     --------------------------------------------------------------

C.5. Shell Accounts

   The following user groups provide shell accounts for people who
   are actively supporting the FreeBSD project. The listed
   administrator reserves the right to cancel the account if it is
   abused in any way.

           Host               Access     Facilities    Administrator     
                                         Email, Web                      
  dogma.freebsd-uk.eu.org Telnet/FTP/SSH space,     Lee Johnston         
                                         Anonymous  <lee@uk.FreeBSD.org>
                                         FTP        

     --------------------------------------------------------------

                           -ath?y D. PGP Keys

   In case you need to verify a signature or send encrypted email to
   one of the officers or developers a number of keys are provided
   here for your convenience. A complete keyring of FreeBSD.org users
   is available for download from
   http://www.FreeBSD.org/doc/pgpkeyring.txt.

     --------------------------------------------------------------

D.1. Officers

  D.1.1. Security Officer Team <security-officer@FreeBSD.org>

 pub  1024D/CA6CDFB2 2002-08-27 FreeBSD Security Officer <security-officer@FreeBSD.org>
      Key fingerprint = C374 0FC5 69A6 FBB1 4AED  B131 15D6 8804 CA6C DFB2
 sub  2048g/A3071809 2002-08-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 7788 characters]
 KRrlaWusbYfqZn4BQsSpYw90evo=
 =BvhO
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.1.2. Core Team Secretary <core-secretary@FreeBSD.org>

 pub   2048R/2CA49776 2012-07-23
       Key fingerprint = 89F6 C031 B4E3 D472 E4CE  8372 4D58 FDCD 2CA4 9776
 uid                  FreeBSD Core Team Secretary <core-secretary@freebsd.org>
 sub   2048R/BBAD1C98 2012-07-23

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v2.0.19 (FreeBSD)

 mQENBFANQTEBCADwvspc52P27Eq2Wdm0/kbaEC84FHSud6fZdn1Zhib/7fjuAHoV
 U+61w64t9KQVA5NHKviO19j+7dm4CY20aOJHjcHj89q7NpIfE/05J/krTAJ0Ysk+
 HdztzVOD3Zt5c9wGVKKfXbzQ3AAoISmJWF5K8a5oJo1wPt4xD4J0up9OzHOQRUjM
 MKXOYkg/8RVNrdcuVJt/31wkhpsm0Bf6AnHzUybHdgnzSdhFEiQoWg+OFC3X6X4B
 gWH32fo2FiZNsogvLEbd5fdiGPxbsT58p3D6Zd83e7IhffPxjFMlCq2ZL506drAy
 jbadDdk7d76RWvDDuFGykFXwJOtxoKuH/drFABEBAAG0OEZyZWVCU0QgQ29yZSBU
 ZWFtIFNlY3JldGFyeSA8Y29yZS1zZWNyZXRhcnlAZnJlZWJzZC5vcmc+iQE4BBMB
 AgAiBQJQDUExAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRBNWP3NLKSX
 dlVTB/9BZ7FcZK2YDB9ervPig3t35Z7ips/4KKbpnTwkWw4QktwkGEOLsAr2fdRC
 XBkRiTMzT2Zwh/M8OzNkDcgJcHic5EQSIKOF0HEj/YuCE7HOBvSkxo70wHN8F1eJ
 8mqTETgv6P2BpeM3pPoMeisGAhp9NFQWYb5N7Bb5x+U2jjLnDAjmcuc1AkzrOlth
 gPrs73PY0rnu73acrzrThavCaKRO/40+Xmp88+QYHhvGjsUF54kbjXitiFQJP9ha
 ZdV22OjIigm3tOmOkPGFHMHG7g1GYp52NLbeDcytMX42eYZi1pOSvovoi3OImRb5
 rMNvryEmT6yTWC93MJOKbQe7Yn8LiEYEEBECAAYFAlAN0EQACgkQk13vRKCTJitF
 ngCffyTfE6cq5Osi9c3QGFVHYxC8uAUAn3MZ4iqGJirIXdaNT8YCK79Brdw0iJwE
 EAECAAYFAlAN0JkACgkQ/KbBSP+K4wUKiAP/TqgTqqV7mCIwesCGf6MaYNlhdv0S
 GYuPNa3RfSTbEHMyhDt9FPjaiiHpuYSl39e1/tNPFO5+48XrKsII4lu8Qgjgakgu
 KeYt8cFTjSzAX9lz9uNMieZE4Lv1/mkc8LEKYfmbaipxwPVcaxz1HiGakPIITTJ3
 34jo2LkqZBII8Xq5AQ0EUA1BMQEIALrp6i6T/r8rqpTSUU6Y6RAzKe8tMW/hCs/0
 pJt4MdIVxboVg1WgNwZuKk3srJIim60REEaR0JG8awMG+GIf9t3BMckIsQ8Pm9W9
 VQ0084iVuhUQcrjpmI+T6fsX0ssX1AFrO7lH6hLXVEXoNmCaXG3lIc1OGlR8lYi7
 r7xAbCYkFz+2isttqZxcn/CNPSRzn+CXE/jNMaikNQGouUrF8twi3ubyzYhpBvVj
 dn1PO+KFLD/kbo5rPx3+sdgw65d8XedVMiS+U5OVVpY57zoYLjeCb/QTAR/Yunen
 epd3OlwW6fR2959njWbhPFG1Wfj9FR6kgw18hpcaY/qzLN87MvcAEQEAAYkBHwQY
 AQIACQUCUA1BMQIbDAAKCRBNWP3NLKSXdsXeB/9WxOG4sVcRYmcru1z6Y6L6XnIh
 IEn/awPWt5MY3qtTZzFBXWIyxJnQYr+U2Wk2ano6Vqc8Uco+GuXqA0IfMsmcCciV
 vYTUxQUmqqRxepJ0Yw0FZdcQ7V0aaUNStlqyfWopZsSycVvPrp+jOwPO1gP57DkI
 yGUDK+3tDoSuFCYIAf+0ZYhJiYI2y86T7UQ5j+m98c2VZejtFBRtBmEwu/dsuQqw
 UgbOFW6RakI1waLsGxZoG4nZCRWsDqN3NVe9agQy5FzVTHHiCqx0HZx2usdwpov+
 UWiwIJwPX1hpxtgkBOq/DG0go94EybMGrzSXFCP6NccYpmGY3o+8bYI4HjLY
 =Y5nS
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.1.3. Ports Management Team Secretary <portmgr-secretary@FreeBSD.org>

 pub   2048R/BBC4D7D5 2012-07-24
       Key fingerprint = FB37 45C8 6F15 E8ED AC81  32FC D829 4EC3 BBC4 D7D5
 uid                  FreeBSD Ports Management Team Secretary <portmgr-secretary@FreeBSD.org>
 sub   2048R/5F65CFE7 2012-07-24

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFAOzqYBCACYd+KGv0/DduIRpSEKWZG2yfDILStzWfdaQMD+8zdWihB0x7dd
 JDBUpV0o0Ixzt9mvu5CHybx+9lOHeFRhZshFXc+bIJOPyi+JrSs100o7Lo6jg6+c
 Si2vME0ixG4x9YjCi8DisXIGJ1kZiDXhmVWwCvL+vLInpeXrtJnK8yFkmszCOr4Y
 Q3GXuvdU0BF2tL/Wo/eCbSf+3U9syopVS2L2wKcP76bbYU0ioO35Y503rJEK6R5G
 TchwYvYjSXuhv4ec7N1/j3thrMC9GNpoqjVninTynOk2kn+YZuMpO3c6b/pfoNcq
 MxoizGlTu8VT4OO/SF1y52OkKjpAsENbFaNTABEBAAG0R0ZyZWVCU0QgUG9ydHMg
 TWFuYWdlbWVudCBUZWFtIFNlY3JldGFyeSA8cG9ydG1nci1zZWNyZXRhcnlARnJl
 ZUJTRC5vcmc+iQE4BBMBAgAiBQJQDs6mAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIe
 AQIXgAAKCRDYKU7Du8TX1QW2B/0coHe8utbTfGKpeM4BY9IyC+PFgkE58Hq50o8d
 shoB9gfommcUaK9PNwJPxTEJNlwiKPZy+VoKs/+dO8gahovchbRdSyP1ejn3CFy+
 H8pol0hDDU4n7Ldc50q54GLuZijdcJZqlgOloZqWOYtXFklKPZjdUvYN8KHAntgf
 u361rwM4DZ40HngYY9fdGc4SbXurGA5m+vLAURLzPv+QRQqHfaI1DZF6gzMgY49x
 qS1JBF4kPoicpgvs3o6CuX8MD9ewGFSAMM3EdzV6ZdC8pnpXC8+8Q+p6FjNqmtjk
 GpW39Zq/p8SJVg1RortCH6qWLe7dW7TaFYov7gF1V/DYwDN5iQEcBBABAgAGBQJQ
 DuVrAAoJENk3EJekc8mQ3KwIAImNDMXAF8ajPwCZFpM6KDi3F/jpwyBPISGY1oWu
 YPEi1zN94k5jS90aZb3W8Y8x4JTh35Ewb6XODi3uGLSLCmnlqu2a80yPfXf5IuWm
 IQdFNQxvosj9UHrg+icZGFmm+f0hPJxMTsZREv3AvivQfnb/N3xIICxW4SjKSYXQ
 cq4hr4ObhUx7GKnjayq+ofU2cRlujr87uOH0fO3xhOJG4+cX5mI1HGK38k0Csc1z
 qYa/66Qe5dnIZz+sNXpEPMLAHIt1a45UB967igJdZSDFN33bPl1QWmf3aUXU3d1V
 ttiSyHkpm4kb9KgsDkUk1IJ5nUe9OXydWtoqNW5afDa5N0aIRgQQEQIABgUCUA7l
 wwAKCRB59uBxdBRinNh2AJ41+zfsaQSRHWvSkqOXGcP/fgOduwCfUJDT+M1eXe2u
 dmKof/9yzGYMirK5AQ0EUA7OpgEIAMzcSWKX+T66lfKXUV5J9+hXuOauu9WLW2dl
 q0+w9AlWfGfgGbMZz/7YmNUqzNjHqQngNsQQIShrFgVqNWkZOZn2TpLCrIl7Itl3
 gVYXWZQpKzjCgU1Ymp+yNZR+fWZzSDF9DZdLZY9y9SI3lljb33o+N1EVfNUvRJks
 KY2lm6Gra9gPtaCZLuZu5zw/SSDnJBNU8wbMoce8yFDfcOjCq+4BcPAws8qcFCsm
 ICmE6FZvEJZE/y9wdH7kB1oU+kThpOKPEgu9YmubXNU81MxhGdQEDvG2525iSwQy
 r3lhwqGngJEcyDc6A/cAJ/c+KZ4pc3ufULSgtXDqlJLE7wUg4esAEQEAAYkBHwQY
 AQIACQUCUA7OpgIbDAAKCRDYKU7Du8TX1Th6B/4uVcoIFXcKaj1/GAZjeZl0M4mG
 TUKIjjfCITrMaV+Ftp1wo+ZujAAlepyQ1VesMlB/P1bw0AvZx2qwntaGjbB1yc9B
 2pmLeYBydBtW2LgXLiafxRIy2uPFxSO510IyR5/K5cGTIyvz1o9ZcNlmYnpL4rs0
 xAx/HN2ErRiUmvoGHvBMqt1yVQHtlUDoSJqFoBg0d7Vn4K8mvyHRBW/45ox0huV1
 H2yNLzcKpX/N9gakkCjxv2YseDJgSYLwM+Ee9Tx/FgZm5jRYw3pcVcn8/NPojIBG
 /Wi/dTH3gTQtigdaRZoPdZkE7Iqu2o8FS1SSvDaZRwJHS5pAQjvDIDI8xoZR
 =k9Rx
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

D.2. Core Team Members

  D.2.1. Thomas Abthorpe <tabthorpe@FreeBSD.org>

 pub   2048R/A473C990 2010-05-28
       Key fingerprint = D883 2D7C EB78 944A 69FC  36A6 D937 1097 A473 C990
 uid                  Thomas Abthorpe (FreeBSD Committer) <tabthorpe@FreeBSD.org>
 uid                  Thomas Abthorpe <tabthorpe@abthorpe.org>
 uid                  Thomas Abthorpe <tabthorpe@goodking.ca>
 uid                  Thomas Abthorpe <tabthorpe@goodking.org>
 uid                  Thomas Abthorpe <thomas@goodking.ca>
 sub   2048R/8CA60EE0 2010-05-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 70158 characters]
 QzgBefclBFqxGuJeC7jwAK5OvvZU
 =ie5/
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.2.2. Gavin Atkinson <gavin@FreeBSD.org>

 pub   1024D/A093262B 2005-02-18
       Key fingerprint = 313A A79F 697D 3A5C 216A  EDF5 935D EF44 A093 262B
 uid                  Gavin Atkinson <gavin@16squared.co.uk>
 uid                  Gavin Atkinson (FreeBSD key) <gavin@FreeBSD.org>
 uid                  Gavin Atkinson (Work e-mail) <ga9@york.ac.uk>
 uid                  Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
 sub   2048g/58F40B3D 2005-02-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 26730 characters]
 c1hAq4PIfgnpiErVWkaOiwCfcQSb29qCLTwsVXBkqZr02JdmGdg=
 =w86g
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.2.3. John Baldwin <jhb@FreeBSD.org>

 pub  1024R/C10A874D 1999-01-13 John Baldwin <jbaldwin@weather.com>
      Key fingerprint = 43 33 1D 37 72 B1 EF 5B  9B 5F 39 F8 BD C1 7C B5
 uid                            John Baldwin <john@baldwin.cx>
 uid                            John Baldwin <jhb@FreeBSD.org>
 uid                            John Baldwin <jobaldwi@vt.edu>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 4748 characters]
 =BVS/
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.2.4. Konstantin Belousov <kib@FreeBSD.org>

 pub   4096R/C1BCAD41 2012-11-17
       Key fingerprint = 7DE0 3388 64AC 53C3 7B88  3A79 90C2 B92B C1BC AD41
 uid                  Konstantin Belousov <kib@FreeBSD.org>
 uid                  Konstantin Belousov <kostikbel@gmail.com>
 uid                  Konstantin Belousov <kib@kib.kiev.ua>
 sub   4096R/3BBC8F64 2012-11-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 5016 characters]
 Z3HzdaVN+w==
 =+dQH
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.2.5. David Chisnall <theraven@FreeBSD.org>

 pub   4096R/65C4F55D 2012-11-28
       Key fingerprint = 3E8F 5E9F 7586 F090 AC2C  58C2 BA06 FF14 65C4 F55D
 uid                  David Chisnall <theraven@FreeBSD.org>
 sub   4096R/04B2A21D 2012-11-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Comment: GPGTools - http://gpgtools.org

 mQINBFC2eZ0BEAC7IeD+/alxWAqAR6YBi6XTfftZc83e6Q0q3PN7cCacCzbrsFSF
 8qTe3uJIsMTKprvF4/8kTvJG2/zeS8hUxpRhRe0I/7hDxErluQpeMf7lGdutrTCS
 J3GE+xgAI1Ho71FSOQjCvbFi+OoRNGFH6EjzNxzP8GWuv0nRmKO5Lo3l8Y839Hfv
 p8JCx1Yq3R72zfkcpwAPAj0aKICqHYlWOldL8nz/vAE31MWwcZwdyt/7IrnpzlA+
 +LSEMtj8brMid5xdxSeIg7sbgjdsenj9HOeYl4Y3Kpp5t3lHnXfAQza/b0ZCbFuG
 wnCPYJj3WJ3fH8JbUcgABUhJPCsjOvVJcOBOjlmrFYNmnOk2uZSRPX3lGf0egu+p
 RPjyIuJlVjGIMnLMChSBE0YlzWPk3UKMnTld8pbwnKuQJXrgQKkSL6Ip+0MiVZ+0
 9rcGm0LfkuK3KN49vnXdcTzaLzTbAeDcoI5h5jijeiuCYANsZow4/5euSfUB6hLE
 tf8xiz7haa7la8exx926L0kHMODHNXzmh8NM1gbFS0VR8sjgW1t2/A9Nesx3BAr+
 6pY9L5qI0+XWMtQX/OFlQqpBOB0IefK3nQgF4FD390iqsM+fM6lZT+Qo1bD5FpQL
 X1pLbonSZ64oGQaddG+fSfwVcXi5xw7axMqF7FFrshuOfj6ylDzkLyl0JQARAQAB
 tCVEYXZpZCBDaGlzbmFsbCA8dGhlcmF2ZW5ARnJlZUJTRC5vcmc+iQI5BBMBAgAj
 BQJQtnmdAhsvBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQugb/FGXE9V3I
 xRAAlqizLbx4VkE/qziv+K9Di/P8BOI8fMlOBvWtO1NcvjYh2gpvS0v3ZcVhkfIb
 XLgUCRX6v5DeTEXEFAF7O3DPKYzKNlrwGbKmmn+akcUElkflmqQc4eVjc7NlEyJx
 sKhnZlpK0dAsG5r6KY4Hs8EqITJepi0ct2JtJZtW0OqhY++R5E7jXX9WvnyYtx1g
 NpY1oSagDbTH0QCUdU4Tspxvddr5PYQX841Cbsd6W0QO9moU5G5Se0q7sAsQSjnQ
 FdgmstYWnhD2a6QaCbSXdEG9Fzphx1S6kjQToZk56U+6GcgXWqOYJ/SqdxuUFkIV
 x3I8AdNNiVnFoHJ4k6FUGls2af1xRilJuU5Yd4ps3Ec1g8FpCzdNCi/uUVtAaUaY
 unU9od12zM36mL7ScF2WY7LAweXGjfuiswL/FzvraGbotYNQRJ12tbbQMyNIyGma
 X3DWsaiIto69IxxaIDgqoBptCibgIY2aJJ7OcCnQJ0aOAvdFnoQtcLKB6IusZS3K
 1Cj4sqVoqFzjCrY6RjNHjhNaeAf//E30GRow8j78dO2Ur2wG7jQOQJCRNqa1I8iy
 EUCc9Y2p2XHzHVNiHJzYJeHjxzoBefjZ4qY57a3PQicVPGR80WOPIVgyzVZYyy56
 NGrw5HxSrK1tf8nYi0E4/g2vBbPScQC1TaR1U8XyPUqjNeu5Ag0EULZ5nQEQANHm
 xy9h6ZKDqY1Go83OiB7R/sEkhHQyoN6bLvch+Ar+SIp4JoKd95z7UsSvsH+SiTgh
 82g1zgnw80IY32kyuWzcts6imGocVqeiCyUVESxkZssOq+pyvi9mBj7NiVhKH+bR
 vxYlu2+YG4OW0Vts4e9B7287xT6Bg/VrPmCJENjdSXD+WizeFQE0X7Am6F/PdPAy
 F6JLUYZFK2kZ+P9sCfJIBIEhjHbbBzaJL2MhnmLSDeTQAUKmNxAOU/Z0evR5uWHA
 vbicjJp/rbenUdu3a00shLWQR/whZLhJKD+ZspUOz/6sTOTs39AbVW9M/ychNb+x
 GsbOlgEi++LDX2lJlk1dDAl/NnXnFqIpcS0Q7vsr7dLLbDIaWyeROEtXkTthDPI2
 z/q75iLPU9X38bSsd7PqKH6TWK6dzDOMzuoJtAj+bjOcGoKxMzsrHunUs5fDHgds
 /rr0mnXr4oXUmIq8l9trzt+W0o0mzk1sBo1Jlzv27ClZBAdcEIccDL4bLGMXswYo
 RoBcIUD1zncVnhyujoqAJtLno82x1+XBWsJRWJq04lfMOcCpShvrHxoUj0H/oF1S
 tTUA+yJ7YFiXjlTU/5kAMmpU5XgSa+C33saWGg/FAnOPqHN3GMwT7Mqg+PmdmdWT
 B49CykN0GJwnub4KQlCspmFbo1iIxOrMXNHmoYydABEBAAGJBD4EGAECAAkFAlC2
 eZ0CGy4CKQkQugb/FGXE9V3BXSAEGQECAAYFAlC2eZ0ACgkQrHrkMQSyoh03thAA
 xu90VRRj69kWO+i5wRO2++Hb4an32PwwxfJSFBh6yYUqj98T4XiuhvJOHFlvBftE
 HXRiN4nJejyZuqmj7qHfwvpMRcmnmC4uFDFrzM3W7jj2LbiqAO1XTlGf7ApoKptU
 uJSb8SuCAp9HuTpn+FBOVeL0LP2RDOCE/1vJ3ZpkfMHA/UM0XtGOED+lRe/SidOd
 ISxF0OcUs3XV8VHDaIaqqaDIJ85MjO8xA/dWm+/R2UtytyM/YdIRgwmtsFsAE7gt
 gYiIc6PBhpUZX/etF+RDriBGv9QCTEHkiVdHtpgfUXGdubi0qHODG4cs2U80OIuf
 QBqiAMEitP8Irown2tkqc8H8CCkbFGpHyKK7eQGgmBfbcJA/Cn8Nn1q2hzU1MBOY
 L2zZ0tsxKrdtkU3+JDOovYjT4pkyyPgG+RALO/4m38pbvozCjx3pmjEJYOX+ALQW
 +7P6J3KfAtkvgG1oZjVKM8XbeUjRF87F8IprceIkXBoTW8zZtKfDaOe+Hfgmc5pG
 U+vkyGjtp5TQBF85K6EyiH3qegPanAiNf+oPUbwhOVl7nqW6sSz5DlJMTb+Qa3XA
 uRRjCxnhmfusX2o4+KW9+22QF8SqrkgIMk5eq0ex7RFXogIfI1cXHSLTDbWP7EL2
 aDtVsnD7aE1Vs9TXairGnD0mEbckSLktU+zpJGr7VrQehQ/9G/GbRNSJR1XgtsGN
 2wCiwqz/h91ltc0hhzADhXQs90DK8dGRDiP55DUKpLQRMov+JWQqanDaJBLprsRh
 TFr6GxV8foSQMSdCbC3lwiMzca5pOfWMiHv7BawlYNDSLdCMaAXOhUYDTzjia23t
 8xUBzSpuF0m1DpntOPxA6r4vvtZVXsyjtSwaCI8qLAPnwHYBAFiXjsxaCbhDXGv3
 sVD1l5Nfj3uJRfX+MhhtXH7u7kYfVUDpYm8oCENlv3p94O8HotoofnCK+DjRWP+d
 8VFzLQEyXTR+WYXm6qs21UPhnqRIAuqEbJ1Hwqbe+5V7OClV6iHPBrKx43RkOFtu
 xg1RioYz0FzuaiN4GoGeUUjmVGNXYt4xbKfQkctLeRG4lmb90q2Co16NWJytdOVY
 l69oryIACMqVhTUxf/vVYaQD7y2KdF2vw2AMW4BHtydBIfDSwbwor1nbv04y/tId
 wz0DmzFIWQ4WyqJgQEBnR6vDFXhSfvP8Dng12YKVY64/DzboxnFfBtKlrsZ3ABXS
 XPrCchELEaWSGO8ONmmpbMYBPp9UNrSRyDhewm4Qb9SCN9JVSmiNXtz9eSwhD9Ih
 HTT1GQ2bs7+ZL0mBJ7DqVcSNv3BtLVvPJBtxeEL6dvEu4580HnvKZM7JsEA2GupP
 JHb9JdgKmF4SXR4Z6/y3LFUPc4g=
 =70vB
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.2.6. Hiroki Sato <hrs@FreeBSD.org>

 pub   1024D/2793CF2D 2001-06-12
       Key fingerprint = BDB3 443F A5DD B3D0 A530  FFD7 4F2C D3D8 2793 CF2D
 uid                  Hiroki Sato <hrs@allbsd.org>
 uid                  Hiroki Sato <hrs@eos.ocn.ne.jp>
 uid                  Hiroki Sato <hrs@ring.gr.jp>
 uid                  Hiroki Sato <hrs@FreeBSD.org>
 uid                  Hiroki Sato <hrs@jp.FreeBSD.org>
 uid                  Hiroki Sato <hrs@vlsi.ee.noda.tus.ac.jp>
 uid                  Hiroki Sato <hrs@jp.NetBSD.org>
 uid                  Hiroki Sato <hrs@NetBSD.org>
 uid                  Hiroki Sato <hrs@ec.ss.titech.ac.jp>
 uid                  Hiroki Sato <hrs@ieee.org>
 uid                  Hiroki Sato <hrs@acm.org>
 sub   1024g/8CD251FF 2001-06-12

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 51810 characters]
 Ln0edjW0+EBUAJ9r3AFbkHwm1E84aDQXsaLjWVwWEA==
 =ddbo
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.2.7. Peter Wemm <peter@FreeBSD.org>

 pub  1024D/7277717F 2003-12-14 Peter Wemm <peter@wemm.org>
      Key fingerprint = 622B 2282 E92B 3BAB 57D1  A417 1512 AE52 7277 717F
 uid                            Peter Wemm <peter@FreeBSD.ORG>
 sub  1024g/8B40D9D1 2003-12-14
 pub  1024R/D89CE319 1995-04-02 Peter Wemm <peter@netplex.com.au>
      Key fingerprint = 47 05 04 CA 4C EE F8 93  F6 DB 02 92 6D F5 58 8A
 uid                            Peter Wemm <peter@perth.dialix.oz.au>
 uid                            Peter Wemm <peter@haywire.dialix.com>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 6134 characters]
 =7AWH
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.2.8. Martin Wilke <miwi@FreeBSD.org>

 pub   1024D/B1E6FCE9 2009-01-31
       Key fingerprint = C022 7D60 F598 8188 2635  0F6E 74B2 4884 B1E6 FCE9
 uid                  Martin Wilke <miwi@FreeBSD.org>
 sub   4096g/096DA69D 2009-01-31

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEmE02QRBACEWV7eL0shCAA+vdpkBCMxrQkbRAceOs8+uhsaocAai3TCiyUg
 Byzo9OKlenJ+bcZHFsBx0mUDPBRFF/NJPfhh0EpkMRc6VKvCHsuvjr1717gcWbLa
 ibbvard6cFAAUDXGIn0/hPABtBidFcA4vIb3EQES0PbnXEVfOz1gymojlwCg4/8D
 0ZICstqkxQMN+K6p/bpCV9cD/iMHVKnPCD9z9Bk9IJtkDGQ66OQpopY+oxUy9ZZE
 yO6Gnf8vDjPmPZ5RcDXu0XHlUpUF4yYkdnUKt9u71SVeDlBAQeFwRgDj0zbYKskA
 Py9YdR7bXbDPIuuAZyJv/93MKryHAEyr8aieAoRZ5zslRcOUrRbzueKi68P01xM2
 H6Y3A/0bE+8jz0WWugB4d/D1qmpnxIHIbzWN4S2NICJmMcj/jgoC+p+DTl7TH6Rw
 KfTt199A4n/g8bfrI86hOQWNY9l9CcBqxwJNMhlY5a3Y6y81tj98oIFuTonyZEDd
 GZmXp4JBDEIYHVVL0XyD6pvFT2NLr0UHWAFZwsiWK+W0IrByWLQfTWFydGluIFdp
 bGtlIDxtaXdpQEZyZWVCU0Qub3JnPohgBBMRAgAgBQJJhNNkAhsDBgsJCAcDAgQV
 AggDBBYCAwECHgECF4AACgkQdLJIhLHm/OnvuACg499DhQhK0dsl+rDk2l+Y40Ec
 DiMAoNVTN6ybdr16bfoIoYddjsnKn9rPuQQNBEmE02QQEACo7w/pIuz1jhyXiKMh
 n6/LWwQNdIl5WT4E4DSB2/NmIVkGTwyyUET1nE4NyOVJWeHujK+PxZbtmx7OVe6J
 niwxv2NeWJ7EkLoeDTrSBKrFCqWRHpbN3bSUAaXiwU9HeHMbGjvvVRg86gzrPKlG
 I5blbT5N5QgQESuvS5eOgGZLbUptNIGwA0hUWOPN1YR6584XGeV0N18GzcB2nXn3
 4Tj82IpeqF/iRY2VxZU3EcN4BoeDYcibPygA3521jWvPOnC9/uqeY/RsORKvyLsT
 CsEx3pRew0vhbJ8me8WkFPwVczJNWqdhEjxMm0NS9FyBDRgXTn7cROJiuonrGWtY
 6HOEHIFsCIzCTfXG0zDaC6kc3k7g4Xlz3juzOL/mhDjnbH+G6VlqfHb6KP3YZnU5
 fXtwFTRF/AFDv58m7PFGwAWjIU3mARzbhdKN71FQnp6aEdWIY/3ZyTAs+En1RWgR
 bHEO7Jg+55V6pH/Cn1p/aIXYDOqIp9HMi9w8nxM2mFt55MiqdUX4RkPxwUdy6BPK
 22LxmxYBv4XrdQNbwy2n7k8H+wfQrKhP+oEKM9WFLTXpKPf52xTB4svJMd1yBZXZ
 FJZSArffJ/QlZ2HgC37V2HcXUOlvU1K+tan/xY2NbJmuetMU7N/ePUWyi4mg3Nww
 EzUpR59KjrqNI2if2qX7yjCB7wADBQ/8D2LYxz9SCqp6iebELuTBWbHtBX2r5xyl
 Z6CuDyjHQy+LOW2D2WEq3b1jI46HFp5O381jKNDJxx2z6o9E9dV63wFbGWIxoAec
 TEdbtf5NBKljFsEtdSg8xdaQa/8FdnTm9EK1MV3C8KqH8e1VBGaHDOlPU1t9zrhO
 Nc96n8OCl4yk+VldoVycqIgdpta4e8jR6kMGLlCXq4Mq6xR5usUoo6jSab4PSEC4
 BZDE4WCzbrahrsJGK4hVmpzi9ofGiqOPf0+XUWG7Na6HyW4GJPohVmjJHyjwc4rf
 bHtJTu53Hk6S10HHYwbRJz1YO+08KrybtvdzXgTv2C/dYBmjheN2ylKmaXYo6bAa
 GcVmW3gFEUTWQd8qQtUJzL6LgreUjuY9xv7Z9nUc7SL63XfAjs3H75vavNWZ8Y/J
 Su/WuKXKxkJDLwzcKHnUVOegEXe0Q6+Khe056WSJ3VtF8+tAaksN7RRslrf1MmVt
 nVag81z/1UvOwNsyLVEucPnh/8LZxD3plUvscKm3w7rsuWiQ/Wtn/NCW9MBeZuxR
 QAUnfWbvHPBo1Dgo1essw+Q4crMGAprk/T8/kPuxrHQ3ZydT0e+t+noDCxcLeoP+
 oqS1A/Za+idThWujkwos8clIyW4HryqAejrFhtzhfC8ELkpkjq0B7Yd/8Zv52O1T
 haaPTklRPcuISQQYEQIACQUCSYTTZAIbDAAKCRB0skiEseb86WULAKC5M2ASX7/v
 bNgnr3BzKKDpkqoskACfcKvwwi1c4AsPtLPxbySr6dUwhlg=
 =S3Qn
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

D.3. Developers

  D.3.1. Ariff Abdullah <ariff@FreeBSD.org>

 pub   1024D/C5304CDA 2005-10-01
       Key fingerprint = 5C7C 6BF4 8293 DE76 27D9  FD57 96BF 9D78 C530 4CDA
 uid                  Ariff Abdullah <skywizard@MyBSD.org.my>
 uid                  Ariff Abdullah <ariff@MyBSD.org.my>
 uid                  Ariff Abdullah <ariff@FreeBSD.org>
 sub   2048g/8958C1D3 2005-10-01

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEM+MioRBACP2lgLXXL1cIqZ8sdgUMaon8gBQWTn40tjTV3N6GtR+NUYbQI2
 Fcg43aopA9VVoeVyBlCSAyaiLTzZkyg1XRDqsjz9BnRWotwTX2e26ndVgsUzmXs6
 NjBcCYYNfVQ09BN3B05FRlPRpveMzCkZCFmWJCzjAYBMg/60fSia2In4twCg6Pr9
 Bp/eR5Ny9z4WzpIsynAt6rMD/1pDoV+FbZ6iw80Zq7pdyspPdPCRIzXhYsoe5uTX
 kjWRWixctbphxgvMheQWZNPNhDyDo/YvuPa2qtrHCDqRYSgmAHPC+NWfyoJhCMjG
 WMjcW9wWZ0j2Oc2uCTvficrGKF8U9ol6E+x6tlc5Cw2jjrPkwJCd70W9SByrgIdv
 51bNA/4nBw7S9grYcnKChYu9mGMsAixCXzMeIVc043Y2SD1NBg59ZNiaSkmRyD6E
 dCYRDhQeF2CePV3ZhlXDxOm6vD2l4H+9sQ1TRlEP/ARejwJrPPRO+plCf8pLDgj+
 78Kj2OlEwC+ziMdXyk8W91FhtCCDXQgDnf3ND/h4IWTzrVD0dbQjQXJpZmYgQWJk
 dWxsYWggPGFyaWZmQE15QlNELm9yZy5teT6IYAQTEQIAIAIbAwIeAQIXgAUCQ1EY
 kQYLCQgHAwIEFQIIAwQWAgMBAAoJEJa/nXjFMEza1FsAnjbSH6NqUl+VC42MGNYG
 6xGCfJoxAJ93L2Zf9C/ug6afFr4Bh/HoJbFiOrQiQXJpZmYgQWJkdWxsYWggPGFy
 aWZmQEZyZWVCU0Qub3JnPohgBBMRAgAgAhsDAh4BAheABQJDURiFBgsJCAcDAgQV
 AggDBBYCAwEACgkQlr+deMUwTNqW7wCeLHdcpasWMJgoqfLIM8PTJ/UlZ28AoLF0
 V2UMd0CdWCANmPNdZcME6jietCdBcmlmZiBBYmR1bGxhaCA8c2t5d2l6YXJkQE15
 QlNELm9yZy5teT6IYAQTEQIAIAIbAwIeAQIXgAUCQ1EYnQYLCQgHAwIEFQIIAwQW
 AgMBAAoJEJa/nXjFMEzaMs0An0gHq10v/5mnLWBYqnwZ+SnZNCYbAKDaTpCa6ddQ
 7jdr/lmi8XwK+blRqLkCDQRDPjIxEAgAudaX6QqmUT7UjXmxjlNr6wdDT0BDCu9H
 ZJuYt9Nf5V0Yd9ExfhRKh2YoYoW0790gka92R7uvrs7FJiu35KrYvOUjmwbouVf8
 Cg2fQqDcw0Lj/CD0meEduZOS4moxv/5GcJc2vsQ1BDsRwX0DmLQYXIaqIsRSo4U4
 KxWi/zZC5TF1Iwo7JyGY1Gc1SMZuWeZC/qx8bQxvkLx1q3qyZybjUtE2WkfqH0bI
 /XCpN5kxDciq/U1IP0H2pU/Md/OAvylKID6uR9yPh9kaOOhcvmOID9oWIMbE8a7x
 eAQ0QkEVpoexA+5DbUarPzjfqUprpZCydaE8s7Gzy/ocegAYqiGQKwADBQf/fxph
 6IW/Be5YFg15+9wZ+1MlEszXw9pZnkLU4Ypwz6ksNjrbpHcEbBdK45kw17pOL+WW
 Yie5tA/b8ndzoga/qyaOa7lH3b4pA78GMhGd7gSzrziNkuE7Yc3WNqjpRVYmVgH+
 9K0rjJaK55hhKDdEGj1jMXNXAXtXra70DNWZt88HLs85goWm7vnnsiPBgOVquYEB
 /q5ExD/E46TkxF5/Kl02LyHTcyhWsUjksmoEi1O/wxXOAxi/GM3QRrkbF7voaC+d
 Og5pxQXsftoXsk5fBEDBD1iCqqs1m2IJIUwuMxVlcc+IvD/eYejrtNlkzh5NLash
 evj4a81s2LLPh5qd3YhJBBgRAgAJBQJDPjIxAhsMAAoJEJa/nXjFMEzaXHkAoLi5
 OZgXddFLJYSXXnK3iwzYho2tAJ0Ze7tHvJd2md4VSth52CSBYDEemA==
 =2tPN
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.2. Thomas Abthorpe <tabthorpe@FreeBSD.org>

 pub   2048R/A473C990 2010-05-28
       Key fingerprint = D883 2D7C EB78 944A 69FC  36A6 D937 1097 A473 C990
 uid                  Thomas Abthorpe (FreeBSD Committer) <tabthorpe@FreeBSD.org>
 uid                  Thomas Abthorpe <tabthorpe@abthorpe.org>
 uid                  Thomas Abthorpe <tabthorpe@goodking.ca>
 uid                  Thomas Abthorpe <tabthorpe@goodking.org>
 uid                  Thomas Abthorpe <thomas@goodking.ca>
 sub   2048R/8CA60EE0 2010-05-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 70158 characters]
 QzgBefclBFqxGuJeC7jwAK5OvvZU
 =ie5/
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.3. Eitan Adler <eadler@FreeBSD.org>

 pub   4096R/8FC8196C 2011-02-11
       Key fingerprint = 49C7 29DF E09C 0FC7 A1C4  6ECB A338 A6FC 8FC8 196C
 uid                  Eitan Adler <lists@eitanadler.com>
 sub   4096R/18763D51 2011-02-11
 sub   4096R/DAB9CF9B 2011-02-11

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 5214 characters]
 +sVQiiwYDqAYyG8DgM0FX7dOC0bTQOSHPJe4E5+xGU7v1g==
 =SP5X
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.4. Shaun Amott <shaun@FreeBSD.org>

 pub   1024D/6B387A9A 2001-03-19
       Key fingerprint = B506 E6C7 74A1 CC11 9A23  5C13 9268 5D08 6B38 7A9A
 uid                  Shaun Amott <shaun@inerd.com>
 uid                  Shaun Amott <shaun@FreeBSD.org>
 sub   2048g/26FA8703 2001-03-19
 sub   2048R/7FFF5151 2005-11-06
 sub   2048R/27C54137 2005-11-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBDq2bMERBAD+HhpI3J/ftblnkB3BKL4SlcPuRgpzd+qdEZpVFBW9TF4RwZhq
 uVvuhTwcLsTlv8QBoCkUU2Wf508RnG14EtW1hoqciHRSKyKmCOOz5GNYQB9z0VkL
 n/KH3yxYtCVqcr/ZJPXSyGGSzLUuCxX8SgaByYOV8XWJbqlE44nmvTEqNwCg9CV9
 +Ifdl4ohYfPhvQGAQ0Z51JcD/0YNZMWcWruqawPYwQmzIiS5FB7bZa2etPkBzA+/
 EYVdO5L/8CfRy/QTsuF5w9OkRTVGzicjP5j8T0aGziARA7T7LdPGYdQQ8bR9cAWt
 TGeZmlGas4vbz22FN5mEMU1xO6EArt3RFq4uL2ePWM/nmRiTGWVWfZN9ps0qL0VV
 PPd4A/9oa3eSYuJs9bzyFtm4h0rAyQyr7koNIia3757kMQr1L/OmBXUiPS6r51EX
 WISBLslMksGtfLdzlprd21x7Y+iRhwysjX9fyoul5Tzn9HENbZdp5ACeEjFFX7LX
 K1sI6ZVeFDMfwex+TMBmWfv66HGzRgBCpjN3TtcOwHPNo6x6g7QdU2hhdW4gQW1v
 dHQgPHNoYXVuQGluZXJkLmNvbT6IYwQTEQIAIwIbAwIeAQIXgAIZAQUCRK2r0QYL
 CQgHAwIEFQIIAwQWAgMBAAoJEJJoXQhrOHqa4A8AoLpKui3MGaN7QoP7+ABKFjar
 IVzkAJ0XMx2qfpovyhKEaD5mIVmE/HPdm7QfU2hhdW4gQW1vdHQgPHNoYXVuQEZy
 ZWVCU0Qub3JnPohgBBMRAgAgAhsDAh4BAheABQJEravfBgsJCAcDAgQVAggDBBYC
 AwEACgkQkmhdCGs4eppDtwCg5tYU74gBC7sqeDhEXKimC/7Tz0MAnjduBqG32uxo
 mc/IV69B0JSmJr6quQINBDq2bOAQCADLeZzD6b21ivZMLkZ8FD7gtkUK1x0CIcgz
 IWyyJgdPYc19woloRg6oytRDmrdaOI4Nw7x1Bqgosh33oawDL9DG8Z+ElnXNIx2x
 vAQpApWffU+CHKpk2lL66hZtAGOM3Hx3SGk0s25JamtsTwao1ZEoYTnIsnuvTEF4
 j84CAPEMITXKxON5fncm6y1aHZVbYy+wzfj7Tdz6YvLmasAMYE/Ycw9q1u8s7Am5
 UAPL/N7XLfD78WIAwKuLQOIkNjHHMA4EWnxOy+eDy5Ew6HYebF+mEhX2Nh7X0v0a
 7y7insRJGLCbapNR5SxX4nzgedw7LQCHUBKNlOxpFALRyXr+1onnAAURB/9lx5+X
 RzlJ/jN2vIQKV1Fdn/jdFSN32LhjjvTOla8g8hMgvdkawOiclCKIC8X8SZtXhwM+
 hTHj0OvYsJE1fu+xMOKLtMD+ayDwf2pxTK5GKIGLsvsigUTlM6asEBtQsvWyMATe
 Prao20BrxdEYb9xfEmdEGnmfXdbHN0PV7EvBE6UeuyiRdUcVtWaGaQXr0yw0nf1h
 O/VjuEIhjnZQYxjwrg+YY7EvHUWGIa2945ZpTl4ShGNjy1MQHsSrB5kN3D6N0wuz
 fU1wC1bSyaI+hcuEWvmr79i6sF06d7fvbtZ3HkvvjLmdY5W0GYlzxIxhzwU5FXrW
 fSjIbd+Jy/l0I+hiiEYEGBECAAYFAjq2bOAACgkQkmhdCGs4epr4pwCg4BZwVjOp
 QEQDCX5x8hQOu9rjGwcAnA7Xr9tPHD1DGinmsMh0c3rLC5cFuQELBENtYrQBCADm
 P/CuDdbokktItDF5wjpoj1oZ1zw76uNZnYqFD8bHjonxuUSJSHRgpfG1bEgpVLoT
 Zdx5yqJWI+fPOfTUctAciqiEt7ZFx2oujSe+nOpxDt9lN8148tVvBnhLrywFchn1
 Wgw4gZVIEjAcDpJ4zMblNJE8dskAK+eiO/UKkaLz9AqOLZrslCSxATwt8P3tSLFr
 PbyM52gtNHFcUriKoKyn+2KDS0EzYGPGPHI4LA+2kCCze2eYTTCKW4PgMYoxcYzu
 N2M6JtHSfHIUKsxBiAk41fH+8YudNZUx+SkZNbF3bnj6i7UHYuGpPZVOEpt0Hhou
 GFCzMU1FhWSuF6dtfOxRAAYpiEkEGBECAAkFAkNtYrQCGwIACgkQkmhdCGs4eppY
 egCgvQoZETQ7CgB6SeYKqpTdhf2S4/8An3WQnyj05jRtui6cGw6xHHts8lbEuQEL
 BENtYtgBCADYpNwsVwVgPJ2JxnJE0ovRQIrkrKDWpD46zqm+/ZO0iJQ7W82S9YNK
 0wCshHao6NdnVaz2TmGYeVzdG7ABXituW+FKpdHBcZ5OwcjXqC05XqMK2hmsbRXd
 FKcXgUZu6CJhUGa0sUsZ8Wbh2piw8ElewWwEAokF/BZWq9dEVSsGAlbYcBnXWpuF
 OSQkNiTcKlVxFVezGvbrzI6lTPr8qXdilRhecwAVu2FG9B4yfSrFq5UnTgI1QXtB
 QMYLnAm19J24fFDxz6G8wnp14eW7KSJgDS7A3pZwvzXaC9s059iZ84mOOssgf8cB
 ewI/TROWjZhd5oaHeknieHoplrvvLChXAAYpiEkEGBECAAkFAkNtYtgCGwwACgkQ
 kmhdCGs4epqDsQCfcoBp9tmmAEVGQ1dskrPb576rp/QAoOxAhjPsMbEXTa6q1lxG
 NnNrFxKZ
 =zwEb
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.5. Henrik Brix Andersen <brix@FreeBSD.org>

 pub   1024D/54E278F8 2003-04-09
       Key fingerprint = 7B63 EF32 7831 A704 220D  7E61 BFE4 387E 54E2 78F8
 uid                  Henrik Brix Andersen <henrik@brixandersen.dk>
 uid                  Henrik Brix Andersen <brix@FreeBSD.org>
 uid                  Henrik Brix Andersen <hbn@terma.com>
 uid                  Henrik Brix Andersen <brix@osaa.dk>
 sub   1024g/3B13C209 2003-04-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 13992 characters]
 iiCBRqfHnRhf3pTlzxGDUQCgw+Jkqwvej2KCMft2Xavc7w2qYVU=
 =79B1
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.6. Matthias Andree <mandree@FreeBSD.org>

 pub   1024D/052E7D95 2003-08-28
       Key fingerprint = FDD0 0C43 6E33 07E1 0758  C6A8 BE61 8339 052E 7D95
 uid                  Matthias Andree <mandree@freebsd.org>
 uid                  Matthias Andree <matthias.andree@gmx.de>
 sub   1536g/E65A83DA 2003-08-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD9Nuq4RBACDKQ43BknR+in3WdxPVF5GFkKGmozIhDuuNhDA6FietVo2JOhP
 4/GRALlfhYbI1j15LcbxXn9JYd4pDrg9RBHf7t0aC0IkkltE4/uZBNeKqaJnzIA5
 665WMBeTfWgdDB667V6KP+1hfC22Jck2JTwxBCaTnG28W3QR0L9Q0e3ZbwCg/UI9
 UFAU+PaAJVUm70xMFAO90fUD/0XuCLvRuKUmcxR7cSUFloMPxTJCLmPqR7b2o1zL
 EYFRnuiPEFg8SZ/5VGfs7vajvmKjX1soKxac1msPvJeiq37MEh9x14RCryNOMtv9
 650M3a4Uro898N40s2vKgRHhw4aCcZh1igEWeRNyRGFFlaDuy9HuW7EpFq8mjAwy
 h2x/A/wOUUn4FtGrfpwBdnUZZ94DNC1E7gNAWyNf92a+buySZDd0XsEazeGo0bGN
 B6nVcuc5jGqaLX+pXLtxrq2Lh0GjlODcsUs0fvbADvpbHeWtHoqLOdJRi1bnCsJT
 Ot5LFNlZy8hwoN+/NOBZKOk/v3LKePwqEdmBz+9ax+tIjI8HCrQoTWF0dGhpYXMg
 QW5kcmVlIDxtYXR0aGlhcy5hbmRyZWVAZ214LmRlPohfBBMRAgAfBQI/TbquAhsD
 BwsJCAcDAgEDFQIDAxYCAQIeAQIXgAAKCRC+YYM5BS59lY/1AJ0RvFdTrsAviBlF
 UA6GC1U5PNvw1gCfS2au0LW6SrNWWE+2enInOczX8gmInAQTAQIABgUCP0264wAK
 CRAnRKAdJr9cqaWDBADKS6cII7VZXIVLsdb8v746rDTusEz4RFGZOjhxK6biLBRz
 8cXniiP79MMGVIKZzxsFih+V/FtbNzZF9vmxjmv3bMQ5D5YYIEAsES9y4idiUFXu
 Czl7hJZNm9D1BXxnkXhTkqubrATpihVI7Kut4lrJh5cyLGsvlrAN+tXTfW1R9Yjc
 BBMBAgAGBQI/TbtDAAoJEINSvXixLRLzp+MF+wZ4PPVkZRCF5rRbNYFKOkuNWJmk
 LqGSwB7FdCWsXxoTeqU5E+Ib/AOA6TY+ENeZ5rriZWqLfhLWrUCw+r6Os6THY6zc
 l2474vMyG+On52Em5MFq5TGCaf6pWjcQAfSTQ1lTPAB7YA6mCX3BKMzLf+kHNChh
 iKWnJtvbgxEBtJJgptXq2wo5Najn1i6W1b3Z4OtbVqjXCvkdmsnTOp04ZG1ynqYb
 rQIY8t5T1wQ/m9HZcZZVb6N27uok3aMKZUrj/ohGBBMRAgAGBQI/dyE1AAoJEB0m
 GvTFSg6/6wwAnRctuSt22uDYE8H+vTlyq5qHpYBcAJ0b6tPAjKUP2eDb0/0AVTou
 G6Gc4IhGBBIRAgAGBQJA9hgSAAoJENmqtencLigvlsYAn1hrZQpzw8LGCPGMia40
 yrNFlxNgAJ9qweVaomRpw3gQUYC1Dux0xVZHEohGBBIRAgAGBQJC6ISOAAoJEGuS
 vENlxpT3+pcAn0UL5+OOOeuD1f9BwcJZ8MldnTFRAJ9gUGsdGi2t+DCU+fxpmxQ3
 F7x6GYhGBBMRAgAGBQI/V40OAAoJENjDuVLpGrm5yXYAnR2tFGRlrv1IEbiTAr+k
 10Wt4B7ZAJ9Jboh8SkhFi4BzYTPhd1h1R7W2V4hJBDARAgAJBQJBVxI5Ah0AAAoJ
 ENmqtencLigvIK0AoOeSxDKHD0aJL4BrhvHmyXUA2Qh6AKDzwAxnN+1cD1iuFdM/
 +kShdNiauohgBBMRAgAgAhsDAh4BAheABQJJnTmlBgsJCAcDAgQVAggDBBYCAwEA
 CgkQvmGDOQUufZW9/wCZAZ+9Jw6ozaW2DWXS33cbuGHQycsAoIjDqfGlbp+78sfb
 neEL0JreDalitCVNYXR0aGlhcyBBbmRyZWUgPG1hbmRyZWVAZnJlZWJzZC5vcmc+
 iGAEExECACAFAksDY3UCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRC+YYM5
 BS59lev4AJsFEopLiyNULL2jR8OFVVmQDv2yogCfXk89lfNgz92tVjGUxhA8Nm/h
 8AW5AY0EP026sxAGAPbWLZ/O4knBmNdDfmrCZFHO1ZNQK536voaHUTHdLjYgXoS4
 7iiYTWYeGiI5k2hnv59bj6zFGMQpc2qyUcp4kMeQlTW9HdIsFQ9Bk1xr7zyzpWeM
 HEyAKwoIz5rRvazxkalOd8Uzk9c0M/SMCw6nzOsDfnJAyBZvManCN/GqY+a18mmI
 8xI2nRrs0vKpLUfhGHtIrtjCKGhFbW6BC/x4Y0jtCBgUG5W1jxy0jKASVkhTbTY7
 kX+j6GUBRaicBsm7FwADBQYApYR9TX2Mod3yR6kDk0rYf3q0MP0UJrIDJS0yWtOv
 9wv06JXi6GcBPNSQbMqhKo5hgws6Zbh42xY/ofuHIMqA1K+49QwKPvfmzk8JpXhQ
 P36Miq6osBlIxsW9EVamRy03zS8iG47xlISPh7tHP0t27vzKo4qjf6hDkoPtr168
 9/jR2Ajg3srlrtHP0hUC58nw8l/W+9gELewHdv7aVrPcZSeAPjeHmYHd9iZdql11
 eUWJV0RZAh7BIJv35eZWjMuQiEkEGBECAAkFAj9NurMCGwwACgkQvmGDOQUufZXO
 JwCgwJGxWtPsNxanIetRYI7OiA35A+0An3xt2lPyLbkTdQ27liwG7Hf+PInH
 =PvSJ
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.7. Will Andrews <will@FreeBSD.org>

 pub  1024D/F81672C5 2000-05-22 Will Andrews (Key for official matters) <will@FreeBSD.org>
      Key fingerprint = 661F BBF7 9F5D 3D02 C862  5F6C 178E E274 F816 72C5
 uid                            Will Andrews <will@physics.purdue.edu>
 uid                            Will Andrews <will@puck.firepipe.net>
 uid                            Will Andrews <will@c-60.org>
 uid                            Will Andrews <will@csociety.org>
 uid                            Will Andrews <will@csociety.ecn.purdue.edu>
 uid                            Will Andrews <will@telperion.openpackages.org>
 sub  1024g/55472804 2000-05-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 39332 characters]
 =inzo
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.8. Dimitry Andric <dim@FreeBSD.org>

 pub   1024D/2E2096A3 1997-11-17
       Key fingerprint = 7AB4 62D2 CE35 FC6D 4239  4FCD B05E A30A 2E20 96A3
 uid                  Dimitry Andric <dimitry@andric.com>
 uid                  Dimitry Andric <dim@xs4all.nl>
 uid                  Dimitry Andric <dimitry.andric@tomtom.com>
 uid                  [jpeg image of size 5132]
 uid                  Dimitry Andric <dim@nah6.com>
 uid                  Dimitry Andric <dim@FreeBSD.org>
 sub   4096g/6852A5C5 1997-11-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 19404 characters]
 p3ZoprcVEgZAeA==
 =PPl8
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.9. Eric Anholt <anholt@FreeBSD.org>

 pub   1024D/6CF0EAF7 2003-09-08
       Key fingerprint = 76FE 2475 820B B75F DCA4  0F3E 1D47 6F60 6CF0 EAF7
 uid                  Eric Anholt <eta@lclark.edu>
 uid                  Eric Anholt <anholt@FreeBSD.org>
 sub   1024g/80B404C1 2003-09-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD9dFQARBACzmGtuaKFqQwoRV32TI4ANBPHPlXkKXJ1WYQQkahzP/VfzNOUH
 VbjIMQqrNPawOcrFyEFuI/FJLWXewhrcrM+of831BXWqnQ7ketGqKUO3xT18N1MG
 BVCx7F1wpPW42YkhFVAubZ5tyHLOVSc+iJZVGgZ5mUi57odqZ1l+rnqpjwCgnXx5
 tas++vGBPk70vcIP+ZmswGMEAI0Lfr7Qy42P6hbYJZpk/NVAvXMZMUyK7fti2lR8
 BCOQr8lSdFUZMAqOhlGSfr75Lp8YhR4R4qCSISPXIbtkpYpS5A4YOk22qljLfyrC
 vki3U3Qum1eO2L67jswb+hQ7pCeaddNm9Jmsg+CJOZl6nfDIJpC8yoXH76W8tXAm
 1DgiA/96RKTseIR0z79ahlxX5HDr2A5bPM5CZBdPba4tSuFIwd28HVUdLhJmsGpC
 uVnQ5VnhBh5coNBhcb+ngZCOr9NvvyvwrxdYYGvuABeWS3v2UGx7XnJQmBQubWYq
 CEk3wScZWhEoFchvPEVfXtzNBjI6sF1FWMYkAhHaYiH4M7rBiLQgRXJpYyBBbmhv
 bHQgPGFuaG9sdEBGcmVlQlNELm9yZz6IWQQTEQIAGQUCP10VAAQLBwMCAxUCAwMW
 AgECHgECF4AACgkQHUdvYGzw6veNhgCgij4I47kRmhRkdzJeftLig2TG8/gAnRcb
 r7ah3d3nPKNLRN+nQDTp0uxctBxFcmljIEFuaG9sdCA8ZXRhQGxjbGFyay5lZHU+
 iF4EExECAB4FAj/CqF0CGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQHUdvYGzw
 6vfvYgCeIy1G5U6YPFK2QZNhB7SazQXwvjgAoJmxWRZr8zKOmcMiYFf1tj05UDhC
 uQENBD9dFQEQBACpBlENAalxZonZ7K2NU6xiH/qz+XI+ZU6WQh58iUlM0QPUU8ta
 Ot8uQUL5DT6G5myFDZufYomYrdzaLxuZbzpWzDOFGqb9aWLlHC16ydWbIRvPif0D
 ar9wFJX3b5DFkVICUYXTKTx/O/VqcpGHH7tLInuipYRapOBrUw1LU87qLwADBQP+
 KbuF41ujgb7QfPX5x5Cdg9D9SZAQyxu5TbsSXmc4fuel10QFMdWyMEUW2rMLixYn
 cWw7AfziHCy3uWOOm1qxm8npYCIRp0jG3M/Jydc8iQTqL59v0/UBOxPQ1pYZxE/8
 EOmbHRHe9BQt4pfouuLVKXGzxg3NW6nXXNQVEeOyqFaIRgQYEQIABgUCP10VAQAK
 CRAdR29gbPDq9y8MAJ0dP1d27SdsNNU4d8nFpwrXfXXa2wCfRvgv8i7ziyodkgwl
 B8LNmWvWUn8=
 =2V8B
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.10. Marcus von Appen <mva@FreeBSD.org>

 pub   1024D/B267A647 2009-02-14
       Key fingerprint = C7CC 1853 D8C5 E580 7795  B654 8BAF 3F12 B267 A647
 uid                  Marcus von Appen <freebsd@sysfault.org>
 uid                  Marcus von Appen <mva@freebsd.org>
 sub   2048g/D34A3BAF 2009-02-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEmWjSoRBACy4CsdR35YB6pGzU1aa1mbTkLuF44VBjV8O9qji80zo/VJs3JL
 El0wIhM9pg6zObKkzOU5HJFU/6uazzzDnc+A8y3NJL3u+HoX/7c03e3yUZ6xl7PC
 ua8tO3IAQiB/cg/Ltb6iJa8FflfmCKGE0I2DXeR2vN9PpgQVkJW+/NSDbwCg2Nxm
 mfeO83a7C28G/MV70z5CTg0EAKdHCkACr+iB1WpOIKEmFkZRD0NXHEXYa6L2kPdY
 XPNJ893yu5YUmHMFNUdVxoIKaUKpIGPa+V4q6ojAilWJiaEB74W+teqNBzwhzyNv
 xfp/W6fNJtvC1DJkrxkag0penU9ZROkVEnZajIclFh5la3muxX07Qf2HjGZM3Cqb
 nz6PA/9gdPecNwo1N+9aX/CGrCw0DC1QVFc1HJqcL3pe2qQkMVDO7sfQkewtQOW9
 H2ZrDWlVxIohQ9/+vbKV1uOcJr5+egSGNTCNNuimh9Kp4LYMc1vNouQe1D9fsCXW
 2kcgO8FozH0O3uJ60gCak2K06iA+mGziNYLQH3IvjVswivxOyLQiTWFyY3VzIHZv
 biBBcHBlbiA8bXZhQGZyZWVic2Qub3JnPohgBBMRAgAgBQJJlo0qAhsDBgsJCAcD
 AgQVAggDBBYCAwECHgECF4AACgkQi68/ErJnpkfulACeI1WVnhrKTq/+O2Djbpuu
 Nyj/MYMAn0BMDpy4frZjlIMfhazixfk4cbjNtCdNYXJjdXMgdm9uIEFwcGVuIDxm
 cmVlYnNkQHN5c2ZhdWx0Lm9yZz6IYAQTEQIAIAUCSZwX8QIbAwYLCQgHAwIEFQII
 AwQWAgMBAh4BAheAAAoJEIuvPxKyZ6ZH48AAnRraNz0aFuSHUFaw8LXjROOTwld/
 AKCvawhTgwYKX3YjLzu9Jcc1t3UNj7kCDQRJlo0qEAgA2acv4O4JFQCzgJXhCQqn
 KHFeEqOcgpKlvIGlgfP4/hVOCms2LK3qk10JpcbDbkBn0cBW7usxvA3mDiF2ZnrY
 wIwAROI7SNSY60PydR6DXc6I21VAd7hmmcpqkJFXaSMvKkQcq7sAJGlSYVpPuBqZ
 1kCIu2vlPBdpT4W1hHxf7l4Q+h2ge4+C2beRv9V9vRVdlXeSqJT1o5EgE5CjZ6sV
 Eh+9/TQdkRAoGgQG4LZvDuhWfsSkDU6x/soFKOPCdTF/LytW8YZ6asN1EpVJihAe
 GseQdkwP8iK9Co90Ab27+5WVVrP+xkY+rULOngW2vIwJrWic6nk/a0/0MrPjFn3k
 IwADBQf/dMsSQncKSSn8Tg9KeeBLftirddz+Mos1j+1PYOc88vrMrHVodBfNtJlG
 zxAGwFyLtk/yA8/MuW219t57O3W49VYh+I8NenzlRmZr/ahn8t79UD7+SWmy8L5e
 3XD2+w9WTj9Lx1V41wFKvxVLItNAik58Oi9MHa/wR1LMRIeGFAVHWAZcxYLLKfGR
 lYcMmMTY4906sjJ6Z+ZVYILnTR360JdeiZbFdaCFGf2yUoM+HeA2+975CaRagu+N
 /HZKW4JSsiu15fvaLTPwFG6YXKcHL2zI0Vc5UF5nd9GGZdX9Y4ffBi3aPXgIOJm5
 eAf29A6Ne3/llt3RG3TduGacd1WghYhJBBgRAgAJBQJJlo0qAhsMAAoJEIuvPxKy
 Z6ZHPMYAn1s6Sdc/4Kkv8KQ0KaJNwmkQYkcSAKDLkzy/Ph4mOMm8jO6ZL+Orpo21
 CQ==
 =HKIb
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.11. Marcelo Araujo <araujo@FreeBSD.org>

 pub   1024D/53E4CFA8 2007-04-27
       Key fingerprint = 9D6A 2339 925C 4F61 ED88  ED8B A2FC 4977 53E4 CFA8
 uid                  Marcelo Araujo (Ports Committer) <araujo@FreeBSD.org>
 sub   2048g/63CC012D 2007-04-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEYxSRMRBACUOhoJNgNPJtP5AcENhALcif0n7o785oCDaTGrMNPV75DdnR8o
 +mHl4POS1bZ7RYHdo7SHCbJqu0nLO4OCeAagamnK4lW+qaa0KaC6WxBiS2/K3qFe
 Y4mDMQRPxBNUWUh7A6VpXMBWk8n6ieyMGLiLQj7+d0fImSY3NdX547qZswCgnjln
 RlpLKFjRIRtNt9RKZQbm0JcD+gMXo+MoUHHKKnSKIQt3u7rnN3Mpnr4OGsa7J6KJ
 whm6GPX0zHzjKUhXCDOJwaYBpOJYNLTTNS3nKpq7GOkQDg7Q4I89/Q8S6AVwCvX1
 N4Jdeebm0jJBrzVNdbezIYEBwL5k+2YN6FcaC1yKBTk3N7qF7/4dmfRNO14qLFaz
 E7T3A/94lP7YT9FHqmNr9RPuy9rmz1bZhU/7tEimLF2o2Y6ntxsbSY1StVHJj0ln
 cCNlMV4vrIP6Ce73W51Vw1iKNapQy2113lWVfc6dwLdhRxWDVMNPKW8ESxqrFSJ9
 IVTzZvPQoqrXOsuVKTej0MC395UbdiLGWckmsJIYVrPaX+C7lrQ1TWFyY2VsbyBB
 cmF1am8gKFBvcnRzIENvbW1pdHRlcikgPGFyYXVqb0BGcmVlQlNELm9yZz6IYAQT
 EQIAIAUCRjFJEwIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEKL8SXdT5M+o
 kMEAn26jMz7Tux/fTt8Z6V59+qhhd62EAKCGEPvDrh8Ye46LyJJj2ZeA8sWNtrkC
 DQRGMUkmEAgAgSVxd8hyDpx7nndMLjTIfpla4/mOP6VSkmzF0Enj1ESzOeTVC765
 gtnjjsFq5Vy5Gv3wdLwwDkcCij5FkBCgSi9EBcp5ooFpNfN9UtHT6/2Z9X7laLiS
 qQtS7xbqU1bxUQ4sK6AdjhOgzdDz8KOeWUjs6WO+/Touq/gouggxMbg/SWjywsfk
 SkgJ9SwH/o+QXvTEloyTwqwA7ptckvFKeBiyiA8RI/T2wqHUHmRE7YrI+HZz1b8q
 kPqALkZFoZVgYEVHjIuuuT5KttaQYvAdHgWjgTTjugeCfHj186yQbIG3TOD0ToLc
 KXFycft7oYFku55Elo0bRS2mxT6/SptmrwADBQf9Gws09t+AcOYUaLH3V8EKLg24
 1r/aEfu7tPYMZ/xHmibOkxxxQgJEUAIqE4jZY6fMrwUj4F9p4Q8E3mN/wkpY2qHJ
 4yUI71cv7NEOeXLvU3bdS5wwvlEK3obIJZfhzefmUncPQ+pEVdbtoGT2ehosqe4K
 nw+bBE9q1Q8elF4mr6mNTavSZBs2FTJ84S009pbMyqyZZZ61RL1H0XmZV4s03Ywf
 tJpc/uTSwgB5I9SiSi1clafGLRzWx4BzToIeHmE70Ycl1PGJQ5kmf2tmTPrVbKCX
 F/4+S3Sn85D9s3jk6LfxMfLiSzErBkkV/zZaXcNFTPfGZ21Dp6/0IyKF+HnNuYhJ
 BBgRAgAJBQJGMUkmAhsMAAoJEKL8SXdT5M+omBEAn3t4uIC5dceYeU8j15UnzECK
 pAWBAJwI/yul4wCtXeyIhg0vYCrExTl5Wg==
 =3ciY
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.12. Mathieu Arnold <mat@FreeBSD.org>

 pub   1024D/FE6D850F 2005-04-25
       Key fingerprint = 2771 11F4 0A7E 73F9 ADDD  A542 26A4 7C6A FE6D 850F
 uid                  Mathieu Arnold <mat@FreeBSD.org>
 uid                  Mathieu Arnold <mat@mat.cc>
 uid                  Mathieu Arnold <mat@cpan.org>
 uid                  Mathieu Arnold <m@absolight.fr>
 uid                  Mathieu Arnold <m@absolight.net>
 uid                  Mathieu Arnold <mat@club-internet.fr>
 uid                  Mathieu Arnold <marnold@april.org>
 uid                  Mathieu Arnold <paypal@mat.cc>
 sub   2048g/EAD18BD9 2005-04-25

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 32604 characters]
 ydMjrsBH+qwhoiGI8wCfdTd4ZU99kETGpnFIfO7mDHd1VEE=
 =vtoU
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.13. Satoshi Asami <asami@FreeBSD.org>

 pub  1024R/1E08D889 1997-07-23 Satoshi Asami <asami@cs.berkeley.edu>
      Key fingerprint = EB 3C 68 9E FB 6C EB 3F  DB 2E 0F 10 8F CE 79 CA
 uid                            Satoshi Asami <asami@FreeBSD.ORG>

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQCNAzPVyoQAAAEEAL7W+kipxB171Z4SVyyL9skaA7hG3eRsSOWk7lfvfUBLtPog
 f3OKwrApoc/jwLf4+Qpdzv5DLEt/6Hd/clskhJ+q1gMNHyZ5ABmUxrTRRNvJMTrb
 3fPU3oZj7sL/MyiFaT1zF8EaMP/iS2ZtcFsbYOqGeA8E/58uk4NA0SoeCNiJAAUR
 tCVTYXRvc2hpIEFzYW1pIDxhc2FtaUBjcy5iZXJrZWxleS5lZHU+iQCVAwUQM/AT
 +EqGN2HYnOMZAQF11QP/eSXb2FuTb1yX5yoo1Im8YnIk1SEgCGbyEbOMMBznVNDy
 5g2TAD0ofLxPxy5Vodjg8rf+lfMVtO5amUH6aNcORXRncE83T10JmeM6JEp0T6jw
 zOHKz8jRzygYLBayGsNIJ4BGxa4LeaGxJpO1ZEvRlNkPH/YEXK5oQmq9/DlrtYOJ
 AEUDBRAz42JT8ng6GBbVvu0BAU8nAYCsJ8PiJpRUGlrz6rxjX8hqM1v3vqFHLcG+
 G52nVMBSy+RZBgzsYIPwI5EZtWAKb22JAJUDBRAz4QBWdbtuOHaj97EBAaQPA/46
 +NLUp+Wubl90JoonoXocwAg88tvAUVSzsxPXj0lvypAiSI2AJKsmn+5PuQ+/IoQy
 lywRsxiQ5GD7C72SZ1yw2WI9DWFeAi+qa4b8n9fcLYrnHpyCY+zxEpu4pam8FJ7H
 JocEUZz5HRoKKOLHErzXDiuTkkm72b1glmCqAQvnB4kAlQMFEDPZ3gyDQNEqHgjY
 iQEBFfUEALu2C0uo+1Z7C5+xshWRYY5xNCzK20O6bANVJ+CO2fih96KhwsMof3lw
 fDso5HJSwgFd8WT/sR+Wwzz6BAE5UtgsQq5GcsdYQuGI1yIlCYUpDp5sgswNm+OA
 bX5a+r4F/ZJqrqT1J56Mer0VVsNfe5nIRsjd/rnFAFVfjcQtaQmjiQCVAwUQM9uV
 mcdm8Q+/vPRJAQELHgP9GqNiMpLQlZig17fDnCJ73P0e5t/hRLFehZDlmEI2TK7j
 Yeqbw078nZgyyuljZ7YsbstRIsWVCxobX5eH1kX+hIxuUqCAkCsWUY4abG89kHJr
 XGQn6X1CX7xbZ+b6b9jLK+bJKFcLSfyqR3M2eCyscSiZYkWKQ5l3FYvbUzkeb6K0
 IVNhdG9zaGkgQXNhbWkgPGFzYW1pQEZyZWVCU0QuT1JHPg==
 =39SC
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.14. Gavin Atkinson <gavin@FreeBSD.org>

 pub   1024D/A093262B 2005-02-18
       Key fingerprint = 313A A79F 697D 3A5C 216A  EDF5 935D EF44 A093 262B
 uid                  Gavin Atkinson <gavin@16squared.co.uk>
 uid                  Gavin Atkinson (FreeBSD key) <gavin@FreeBSD.org>
 uid                  Gavin Atkinson (Work e-mail) <ga9@york.ac.uk>
 uid                  Gavin Atkinson <gavin.atkinson@ury.york.ac.uk>
 sub   2048g/58F40B3D 2005-02-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 26730 characters]
 c1hAq4PIfgnpiErVWkaOiwCfcQSb29qCLTwsVXBkqZr02JdmGdg=
 =w86g
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.15. Joseph S. Atkinson <jsa@FreeBSD.org>

 pub   2048R/21AA7B06 2010-07-14
       Key fingerprint = 5B38 63B0 9CCA 12BE 3919  9412 CC9D FC84 21AA 7B06
 uid                  Joseph S. Atkinson <jsa@FreeBSD.org>
 uid                  Joseph S. Atkinson <jsa.bsd@gmail.com>
 uid                  Joseph S. Atkinson <jsa@wickedmachine.net>
 sub   2048R/5601C3E3 2010-07-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEw9JfkBCACYbhnwk/miOjf46p2L6WXieiOHXd8No26MCqfF8J4MnzzqYI3w
 //hll+jcx4KqUeLhYQZJsGt5C912Pi1akA79CW99AFF4YXKSr002mo2br0/aGCtz
 YS+0CfdpHG+WUds+hUWmqDD5hUCH91FRsp5vLjrmxec/zTy/uzeQ/BIrr1PbGqLp
 EjKL8OL082s3raHdHA2P+xWAVJJU8FDZaZMdlQpQ0hoE0H8WxImnohIzXTbsYyGn
 k0ZbJmdxyp4BwiXqhNYyUQyU558mytW1UYTBnxUnUtyr4Mv05AgdBu44ZEs0qR7D
 MzJK0eST4Id/xN0Vgliw99aah5ugrpYmmP3VABEBAAG0Jkpvc2VwaCBTLiBBdGtp
 bnNvbiA8anNhLmJzZEBnbWFpbC5jb20+iQE4BBMBAgAiAhsDBgsJCAcDAgYVCAIJ
 CgsEFgIDAQIeAQIXgAUCTD4P5AAKCRDMnfyEIap7BshbB/4sdAZ2d0oC9+z5g89K
 Q04ZwB1ci7IPEFL1R5cexiy6Tffl4Lk+MO7LSB8dWZYyXCHklzojJQxizXgJjIAI
 +n9he2ERiRy4vsR4UGHDDx8vAoeiUmOVuvN84kn0//BiyMvghlDgFAXGTWO9N5Vt
 5QIdpuxzOBwa4g8RNXREVWAUXg3gOKAxlKsuVT1iKYvmfIVctiebYT+2togP7ASn
 AH2tbyq8/DBxPICaKCWazPTLtwjODbpkCpOFT9xv4jKep4eLrPBs8/c0NxrSrNh6
 8pNMdhR0pZdoZK5cz+aUaDkCRXuN5AGyoq3bjjbK+ZsZ+js0l5VABpznZBcbtMDB
 oKjyiEYEEBECAAYFAkw+DtAACgkQvlQxDBfwqjd5zQCgsKrfOUH7/kTiiSkuzQaF
 dh0aX5cAnj3KWkRRJ4vWv8Wuudj21+9uz2WziQE7BBMBAgAlAhsDBgsJCAcDAgYV
 CAIJCgsEFgIDAQIeAQIXgAUCTD0vGQIZAQAKCRDMnfyEIap7BnyTB/9/eq2FRn8A
 1BgYvM8dqhiXx36jGOlIbUAphCOXI9me++B3qdEvDolqPFJV3gaMzLX5G3TmrJRj
 BZ8dzL18TpIQFUexr28jsBNA8KBehzhqmTb58d6acePrj9IuumPIzi+K6+CZwbgd
 1E8w1Qpk4SRZgSbUtOXtltmmgpV14WMq/4cv18ViQ5u9Xqx4AbCMOlurkpEXCF4v
 5g+FMyXHHBK4chzJJu8m1WffihQ0Agnu6Nr0p8Atnqu+mYEhZwCyPcVoAoq3Jmxr
 dW31p2/ruyjPs2gmJ5KW8iabgkT+UI5Z9c3V7Og0xe9SoXhQHgKv2iKEjY6hQs/w
 sQrWDJRxWsHrtCpKb3NlcGggUy4gQXRraW5zb24gPGpzYUB3aWNrZWRtYWNoaW5l
 Lm5ldD6JATgEEwECACICGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheABQJMPS8U
 AAoJEMyd/IQhqnsGQzEIAJLCxnC4LCYRvcCksOmhA+ot9oXES6HEGR+b5oldvGsz
 AZyn2twhTOcHBTjS+NqV49Jl9FeiChHO9Z1KzbE8OfSle66xdQA0zzUHSRF/YYBi
 cM/Nl+BA4MVEJnfJdT0iDtOjAxlvf/2eEg4dN26hEmVrzkAgUXW6RAIabSdvs58L
 DP++6nJONOhYQa/ph2eJSsnLNI3s2aIDyQUiZIKTrLjS0S28r6pyVxCL8rxZDeNP
 5APxYuaXxAp7PpQg5i6rFTjOxiVcZq7I9AT6HfK2bq5BbUALbYJG+L8tOkvLt2ZN
 U1Oqp0qAN5GqtXDkW972y093PXuMUN9faumQqvKDcQuIRgQQEQIABgUCTD4O4AAK
 CRC+VDEMF/CqN7oVAKCwkr0UwFhDDsRo6GX/9jLJSDiXkACfQWEijaQwdg2vOx3f
 eFBx5dJ2K+e0JEpvc2VwaCBTLiBBdGtpbnNvbiA8anNhQEZyZWVCU0Qub3JnPokB
 OwQTAQIAJQIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AFAkw+D+gCGQEACgkQ
 zJ38hCGqewbqzgf+KcT2D/SzGcZ0rmb3bSgUotGesuyFARkGr8YbJWVZBYmjtf1B
 bAVsrwBQR9PZZhtSMMyPnhciLQJaLkYwBv1ONTyV+Bc+ZRwfQuKDvDPoIvHKjKIa
 7EsGw1KTnpq2U1Xp8HoDdFqOv/G3af2E3jJUjxKHmLXTuaNvrgQyBhRm+7Jy7rXI
 V3v94dG1UvhtTF47c4T0BanysVNSWe/f1OQikY6J6bdNq95xF+/wOYzUAxfytDTq
 Ko8J9Y3QwCYea4K3ellxNdfJI5abWLSI+s1sSyTyg/7/4d8/IcGgGGmaQ0e9kSa2
 PZ0wHh68tkDBn8U60FIP5cy+bJuLRGopT2kDqohGBBARAgAGBQJMPg7gAAoJEL5U
 MQwX8Ko3P/cAnjloNxXgyrJUBp31OtlD5JyL81FiAJ9naRMq963euz/HuXgoNd/8
 m3d2kIkBOAQTAQIAIgUCTD0nNQIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AA
 CgkQzJ38hCGqewbkhAgAhfxgjsQrP1E6IekrhcpnLZACBwuQSFkCz+6gRZhZL/Ca
 3s/FLhkX9SSFlGCkEeISWEP2Y0qeMVZX+Xx2JlTjICzjEWrpu/2JC6eOACZIIWMi
 FxjEJ4rWxN/5lGaMEkFpY+BNI75jlK1rswN4997uGSZcz1EUdLdqOJHZZeu3f74r
 lV12Up8JIQzmxUOePOBNkNWJmFvCWedbxouHvLRZm5ClNSRED1fhS9XWel/UNfIg
 yLe+jiNRJeqFIrARCDwgoWvNMLuRM0anEf0irlsbz/tDrOPnX4nOCNPjH/5XP84g
 n11pw+RAShkirln8MeRqMS86TyamdXQWrUqJrf60IrkBDQRMPSX5AQgAvDd8Gg3P
 VmVWN2b8BjnmdefLWsjE7u0tJxCYW2tb8UbBJWagid7GS+pq4U7JNbbnLNQshXwJ
 7kLtFW9o99ql+oMkxctKpjmN6ZHUMmMtLenHkyrFVQtUzGZI13R0v9s5QqAg6O+v
 ZvESo9TlfLAoCBJmzqkp1jhqv/e2G437FNeSUqlVCq6mNqk3sLlY+Zh6RjADb1CT
 5HB0HWVzrUOj2xcvzrYduTjJJ7VQS4E4WGSTFyMVnEqvDahnaG0iTMeTn2Nfm/yk
 NMZ3knreBYrXC4lbvCVQugNifWqUj4LL0y+3DCJAG4TzMmeiomjvlVAOxYlpTAzF
 zIuuGl2eilO3FQARAQABiQEeBBgBAgAJBQJMPSX5AhsMAAoJEMyd/IQhqnsGm/gH
 +NvCjlIBTOWGEdBW75B0UTeSTCiAv3+CNbjk57mvA4k4iq7BM7KffLJtAKI4Oode
 MbrI8DqOvjav3uNUeiq+/CZJNZ/vOQUmgKpPRv+y5oDt2vMikTYxUAIuMItn0zoO
 jSQ2krVYxypf0tmZG9RSkk/EQrd5kOrSVdyrau5WTIhlcCle7BU/a1bYL+IX6kuL
 XEqr+vQDcqnpdCkmH/iNII9T1TSVaheELHfPQFdNemLfIiHef8F1oaKYesNR/QpE
 /nWvgalA/AtaOtMn8ls+FolKTYt1g77dS2c5RAJIo/RyLZKVfV3YEHjREjN8lVVn
 wmKGlCQF5zC50z2aIiJy6w==
 =99Ow
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.16. Philippe Audeoud <jadawin@FreeBSD.org>

 pub   1024D/C835D40E 2005-04-13
       Key fingerprint = D090 8C96 3612 15C9 4E3E  7A4A E498 FC2B C835 D40E
 uid                  Philippe Audeoud <jadawin@tuxaco.net>
 uid                  Philippe Audeoud <philippe@tuxaco.net>
 uid                  Philippe Audeoud <philippe.audeoud@sitadelle.com>
 uid                  Philippe Audeoud <jadawin@freebsd.org>
 sub   2048g/EF8EA329 2005-04-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 10692 characters]
 7GNJJ3W8MechFeaHW8gi7wCfcvqc/uB5T9hc40vmQZTSMGsVwIo=
 =Ed5M
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.17. Timur I. Bakeyev <timur@FreeBSD.org>

 pub   1024D/60BA1F47 2002-04-27
       Key fingerprint = 84BF EAD1 607D 362F 210E  69B3 0BF0 6412 60BA 1F47
 uid                  Timur I. Bakeyev (BaT) <timur@bat.ru>
 uid                  Timur I. Bakeyev <timur@gnu.org>
 uid                  Timur I. Bakeyev (BaT) <bat@cpan.org>
 uid                  Timur I. Bakeyev (BaT) <timur@FreeBSD.org>
 uid                  Timur I. Bakeyev (BaT) <timur@gnome.org>
 uid                  Timur I. Bakeyev <timur@gnome.org>
 sub   2048g/8A5B0042 2002-04-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 34320 characters]
 0I7kYcd8hY9Z7akRmB7QZbKLRukAn1figHfNRdbksZ1MgA42+z1QS/fv
 =r3u1
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.18. Glen Barber <gjb@FreeBSD.org>

 pub   2048R/A0B946A3 2010-08-03 [expires: 2017-04-25]
       Key fingerprint = 78B3 42BA 26C7 B2AC 681E  A7BE 524F 0C37 A0B9 46A3
 uid                  Glen Barber <gjb@FreeBSD.org>
 uid                  Glen Barber <glen.j.barber@gmail.com>
 uid                  Glen Barber <gjb@glenbarber.us>
 sub   2048R/6C0527E5 2010-08-03

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBExXeNsBCAC7wmKFOV+UjSn48hWaRAImN0uGgJRVAYPWcNogyw000o0vMKjk
 5sNm5YUv2DutTVBQAHytkKGYX78ogpltIkvkr5K0eptVpl2iuWQNyGc4Nq418ZJa
 hgDLZOtMO4plEmbViLFuz97D6V7yNPSAX6adiCh3A0kc+GwCOhXtQrn/OWxZa4Uw
 FCGD6uqFXM6s+kkgtqFlWuFB4tAM5epxt++WLEyLCL/znRhZK+tTstZxqLudJnFB
 ooFOEffYvDB1pNWOarBmSKHncYNjHRqEcNFyMXJ9Fn39I50QDvoh9ps83V+NjuE/
 FYzt3MmYA1j9H79tDYpJp7OEvGY5sJCZrMKjABEBAAG0HUdsZW4gQmFyYmVyIDxn
 amJARnJlZUJTRC5vcmc+iQFSBBMBAgA8AhsDBgsJCAcDAgQVAggDBBYCAwECHgEC
 F4ACGQEFCQyoT5oFAk+fMEUSGGhrcDovL3BncC5taXQuZWR1AAoJEFJPDDeguUaj
 NYUH+wS18HZnyFexvxYTP8wHvp68+LlPCSmouq6yqwHaB6qkv8vRS/9lrEGff8a9
 Ya5BeaSJ2+YllCIC6f3lnSRHJ3mINEGuny1UHpSMUys8vGdAqC0JsoLgMGU9GUE1
 1bYgweLBh5Z9xa7UESLUyGh8GEpcdkQzzXYFa/rmQyfwOt8yw7OjzRzTuHe91b5D
 iM3u/DhqIc6HfJs2cm4HEf5Hp6WFQH9vKH8MTeQYGAoxVZ6epzoRfTbbrDX8Dd/v
 hoxMYATTOOc7/kvITSqFxJ9cWuthHtQ6zwqR5dsMXl+XMPnDD3u8YP/xCgnhRJ3I
 NAjoUHP76YkFe33SRkqM4oKzY1m0JUdsZW4gQmFyYmVyIDxnbGVuLmouYmFyYmVy
 QGdtYWlsLmNvbT6JAVEEEwECADsCGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheA
 BQkMqE+aBQJPnzBLEhhoa3A6Ly9wZ3AubWl0LmVkdQAKCRBSTww3oLlGo4mICACr
 42CZKktecfngCYzx0N39KAn55jiZmUeoxs8OGsbi7j98Bd3IU7tQEz7Czqsmv5D1
 aACctF2n4z5i41ekpfzlzkHeSPrR/Ul3e9CjTVyYf/RYYwootcL0tJiBJK/Hyd0u
 5mHPC+jyFSBoMYccncsnaOVrZx69tuVKfgLR9wk+ysYwrzXHAq8nuXhKd3SHJ7IP
 Zp1EoXhyYLL06kIU0/z64UdNKmWwNo2qtQa755KPCFnEfv2wDUXbHU6W53AVlKif
 pSijWxY5eCuyy7VWMfNuT28zUxS4IiCE3JKKYcxCkXjsaRbaUSSabaZpF30i/kXD
 KVidRkqSLkL1RQE1VRYmtB9HbGVuIEJhcmJlciA8Z2piQGdsZW5iYXJiZXIudXM+
 iQFPBBMBAgA5AhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AFCQyoT5oFAk+fMEwS
 GGhrcDovL3BncC5taXQuZWR1AAoJEFJPDDeguUajNq0H/3FSIfM0aBB84iX4lOSn
 qzx9L6ubMWgOdYI0vTqDMnrWcbSYr706hVu9tGbKBncRkF5jIT4Qb5Z2QRCgVHMN
 xZ1/dtnm/sKaMPYEKnBo+gorY4ub4IxS5vpzi/HcR1APYyjxZ4a8k3NsDoImgVr4
 laOwYA/LSvi0xWnqtP12DDwgUkx1Ay+x02CFMMyupLOJ7QT/NJOpToiTACaiiPdX
 xmVIQm0dbM2cWYM0IKaz4D+5P3H9nxEdRsMK3pSbg9UqHjd6J2vwbAy8IomMNYrh
 /Zi6fgx6MblYHe0DQ5LmTwcFc1FZZrZ1XHJGDBU5buvqaa5ZFFPcnrCKXAfRgEej
 5gK0HkdsZW4gQmFyYmVyIDxnamIzNUBkcmV4ZWwuZWR1PokBSgQwAQIANAUCT58n
 4S0dIE5vIGxvbmdlciBzZW5kaW5nIG1haWwgZnJvbSBkcmV4ZWwgYWNjb3VudC4A
 CgkQUk8MN6C5RqMyvAf+M+xe9XdwWWCEyJ3GBSMhmXnC+c2303IdafSoFsm7cB8l
 nzvSHhjPQ9zC6W7wyFgUs2c5fOh5TeLtqo2AOHkvcyGRgqMViW8hIPaJU9ekxfui
 uLwpGwArRJwayEeyMT74Ry5/tEsDLLchoBMU3627jzJEQudFM3dYtc7gsinZOefJ
 S0aXNOT9yjtNB1RsVHVNfwW1pEkxIKEFwWu/aqcMA3jBYCVhs02jZg0jYTbPqjUF
 NPv8JFVb0+cSGNnGpmYKHQk8c+t3I2LLIthcDFFwc+eiPsSf39HrdP+oX/sFK9yY
 s0m8QlLR0yoJ2zOehy8r4e3vGWGN0iDjfAYojhPZw7kBDQRMV3jbAQgAyksBRs9a
 IpEU+j37aGKMhntVy4zCIALaZYV+E75nbhY3yjxHKiOlwOt4y8n4AxIPGvm7qneH
 acnASuKtlkmn7KvKhaxqVVkbk2l04w4kaHqDV0pGsve8CLv2KLQHDwq9MEKvwPqv
 ep3DXyocpe75cmvXfLyaTbmPk46+qPcXGlfNXXpMJbjy7RH51glx3rZS5uycoijK
 oNsblHdLCPvaTgpwyw7bHEpkgpoIFLoUwCog3xyUDZeQKtJwzCPDeJLZ8hxosye4
 y55KxcNIvEzAyV9dru444rbYVBm4W2lE15mGsaNZWzMcHohj9XRWepDCJwCC1i98
 eImAPsnoW4O7BQARAQABiQEfBBgBAgAJBQJMV3jbAhsMAAoJEFJPDDeguUaja6QH
 /2iofGwiJ9v59fmONgldH1o8W4n2A/IKAMB6xjPsSnVi/foAgl0l99JDOzMtVWk5
 Sa3tk5Hml4FDipAYYcfWG6IHlQ5CnRxdTYJ2mAU9eVjf60xmyhEgmvfC5hUPZDVv
 PeVouxzGCO0ZhnGnJnos0v3FXpJXL0bkroCyUWGDrwH708hXjWdwS0cNqCqsWaZf
 4k43+qdPA3qrQ9kdKDZTlDENDp4ORfiXr0Ae0fGMnCVx01qQfgyYY+M+X6CcnZuj
 2FtSaogz6k6ZDrkYC04XdywznP4eBWnokNSO/RGNAyIlsw3NwGu54NGzygaBQ+cs
 FP+168tqFBrd4DNIVjsbY1g=
 =KOGO
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.19. Nick Barkas <snb@FreeBSD.org>

 pub   2048R/DDADB9DC 2010-07-27
       Key fingerprint = B678 6ECB 303D F580 A050  098F BDFF 4F3D DDAD B9DC
 uid                  S. Nicholas Barkas <snb@freebsd.org>
 sub   2048R/36E181FB 2010-07-27
 sub   2048R/BDA4BED3 2010-07-29
 sub   2048R/782A8737 2010-07-29

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBExPKloBCADqhzBB/vYRc48HeilsVn6jNqbAvJyLsXSw281lu0joK5EHY/0u
 B3h+RmSSYcd23UCyLrMn4a6qGIa8T086feYEyACbwORe/4kFeuFLNmgZbAvs3ePr
 FTg2HqvErdhT/DcHLpBloAlJefwppKrN6tGyM6M49wvUZQhxq0TNZdEqSDM1MWnB
 dJsS4M2MNEO2kyBgLgcedb9h4uCK93AcEFzVImgW7+QVh6/97WNaHD0YN0TtmE/e
 /oA7rV5J05334kT8Y2Ejk9gIVVcKcu551P5FSn4uS2kZtuLMSJ9rgkM458p+s+8J
 vY4nhCB2cvT70OMx8I+2Iqlsztl/mf9fuGNdABEBAAG0JFMuIE5pY2hvbGFzIEJh
 cmthcyA8c25iQGZyZWVic2Qub3JnPokBNwQTAQgAIQUCTE8qWgIbAwULCQgHAwUV
 CgkICwUWAgMBAAIeAQIXgAAKCRC9/0893a253JD/B/wJIERQO91u09cz6mk7V4Jh
 Wj6+9ptevVDWTJrqM+yOhSEvaGxUqBAEhhhuIkiWwHNr5DZOEFBar5oQrZ74rOsR
 qY5b4/J1IYxm6B3S60KY2wUtazd/9Gz36lKPY9QmkSg7UcJXlPh45HTmKIXAjmNj
 ke6BUTrVYyXrv2CAtxKgSmX9SQFvR2j90tu5pu4LrnWujh/MK+DNY1AVxsKgEXPr
 KFYvLe/2YWEtyJFh7cNbtWt2sl1JAhxJ9mIarBrzLoWpy/AjogMLWIcGoAv9zunV
 tbWeoq9TkFzIi14kFuy5WJkBZynlvvwtIqiap+iV1qv20UBzVFLA/MjZ8TlM3pbs
 iEYEEBEIAAYFAkxPKu0ACgkQyLJCen51gqSVpQCfcYp1zGIiKNlGjaLdIz7HChcz
 uQAAoIYU20rzffZwbZNnvHpIIEIi8WcvuQENBExPKloBCADq9E7GPd/YXTu56kc9
 HEbnes9oG8+kN7v3c7Xnesu1N+B1R/cb7au9sA9Ao1LOJrqMd/jXhN3JlwYlwyQs
 kmfCZSh3J7EK3v+6vZ31zjv7lTi3kRyqqwRN51HNwIoq73nNp+V1Eu5SzjkFiUVo
 8H3V2wkSdtJygXT/BI9QY3A6pm7S4whNor75Gqyr7C15B6teDaVEWB/Zc7XqyQwL
 6Xy//1GdPCPeaqkNKYmlRyzz9SxJ8lnt4vZIK6CSeuRtJAscIod1XV+yaO2aZxJQ
 HjBVOlsktm+Q8//svB+UtziQ0HSxUri388HEyNk4MIxHx8nWySBVzmsKPodw76pX
 TmrPABEBAAGJAR8EGAEIAAkFAkxPKloCGwwACgkQvf9PPd2tudwhDQgA47c2h7lT
 lSnwtFRqhRPM7jByR4TN9BvK0TEcrh5jzGyEgrfSZCymgE43WpYO8emOSfTA/b77
 OFiewH/w4g/xZqV6UNDjQ6PWQb6oLvxERlagBOZEh7yx+13uI/x0SFvcqPdXgPwy
 SqcHLMkYdy9IWJOXt6BPNAQ8st9qBX8ThDuLavbI0j6wrajQH9CtnbcAH3/tQ05w
 9wXyNU7mWW+zA6h6OWWMRAyKYYfjdZhIA5Z1OiH8M7RYACJheZKGNze6VHoJGh7e
 QFHAlBMWyDB9gMyXj4sapf3ruiJymvu9cQBSlPiOD6MT27IyOmO52rMakwbYdZdr
 viwiYtHal67xjrkBDQRMUZiOAQgAj6wYdH2nsYMkxnY82KyIHC8Eh4r9YyuTmyNr
 vwOtXgSapxePv2Efcypkni9tdE1LnuGI9V0kPr7oFq7KdLqHxGwsBe75jV/4krHO
 5K5NQyOtih/1a31KBOKi5JWU2nFqUz8AzUYtUX2VKFZXOshyQGx+rSFy83rawe5f
 6JjWL2j2XGvndfkoWRV2fs1spe0pmzUPsjG6CgqDScIWwDqmey7UShR1cbxH+Mt9
 th0sMuM6J6ZO9tXpGOzM4CXaMU/qe1AiQCX7Qve3A1NFCCOofBt3x6xBSJZOko3P
 765eYWHvdBSddm8csuzPOuwGN375ooltfuK4bCRoaUOxCtDKiwARAQABiQI+BBgB
 CAAJBQJMUZiOAhsCASkJEL3/Tz3drbncwF0gBBkBCAAGBQJMUZiOAAoJEMd3KaK9
 pL7TW8oH/RviVB9OmDURm/CKeCbva+7XACaJdHTgsWnEyPG0rjX6MhkCu6YYtlcS
 K7HsmC/U37gs+sQq/n/M7Zd2oMd1vnYINuiIxHDyxIMnLiWTEgNvjTXtFaFggewD
 BNGg2i+2h0I80hLVTHPBqbXKupIwtdFQEu39exF8jBsJTfPnjbeboxwFTuCdiiK4
 4CminqsZ5CLDWXHzCLqC0CyZkJ1Ka76K6iOhUr8Impxqeh/JW08gBu9pN4ccvCrJ
 On5Zyw8A0Es0cTRqqnsbcgBjoUY3+S6mEvYQPTfiEh0oWiJGw5dFIHkhpoJGxmn7
 6+lA3nvxgvK/9mdQU4jXoYGI8qlJ55EXygf/T8S6pvkSDB/jbB0dVjO0b7D7hG+I
 XYPwp00rZ8VHTxairtqqxTAU8MaXXnJFIm+owa7OYYB4ctPuIS7tW3fLJ/Q9P8bc
 h8hZb9pDa9Ybuo4wHnxrgmytDA7OV6qeJEAepP7VhQcjYXwNlDsNKlghie9EJliP
 WUuZRapKXcv1R3MpC7dNG3I8FVEY3K/+ZH8xj6dcHEBw1QXihFGNF5frTOLD3tIn
 QwW+B2+JdWg+7MpUdf8ewNkBGfRAYNnH7nGkd7QJ7XEY5ly92RtrZo0AJudKz1HY
 Hg5RdUX2Pi/RUOSZ9bZpZ4v8gKqhNgWpAxIl3lgK4Y3D66nmTAZxv4z7iLkBDQRM
 UZjfAQgAzVZU/brxCgrK6PgB3Q+Dvq7l9oHmh/Tx7wRUqB0whf1PDUQ/G1isZbH2
 1j/kkB/Xu4NDEk9HObcfwLJ/Px8AeKgzRe+MO2sK6A4mfsKli3VUYnMzRbYmmeRb
 KYqBgski+2Ne4BlOi+eRmzq/jNbql6TmFtePLYcYaxKtarxvvOP+bmcsPLT1eHMV
 kiU6s7xm6JpBhvv3mR1/EGuopMzgtxKQLTGO14yCbw6N6PplUFqFJee/TnNwkMCI
 ixFg8SW6C2uCnzstmTtGRu8IceYF1J2WZoTacna0O4oLjBB3gwWqyxKF5B9ytwhr
 1GARL007xvQ4o9iz4JIu652nTHI2lwARAQABiQEfBBgBCAAJBQJMUZjfAhsgAAoJ
 EL3/Tz3drbncp9QIALLfYa0pzg3hzMK5SlHl45r9K+oFpXtK3JvW8l2U4PCnMjQt
 Z29bdPk5n/aqO6IzwgQm3zQFhXK3M5o12Bhj0oZu1pzOY8DDiXMgR4czByqzrsFP
 dFUsLmkzDp/nlAqsjBoof5YnYk1YoiHaBwBpEQvU2N5UO4GVGsC6K1Osw15FX8aZ
 HS8WTOzRGe/ctlZRjFhgY8kyrRcvSPNrJlx7pentqqMMPwDQzp+ig6YECQuPTPkN
 JkUdQ8GUTwVpXcuGRIhrWNYjbzuWcam8ywaXmesESvIJ+XJqJQ3eqmy0sspGsiXZ
 w7zsUcXBoDCfj8IfFwAxKholDgQBBt1pQcCbgIk=
 =zoiI
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.20. Simon Barner <barner@FreeBSD.org>

 pub   1024D/EBADA82A 2000-11-10
       Key fingerprint = 67D1 3562 9A2F 3177 E46A  35ED 0A49 FEFD EBAD A82A
 uid                  Simon Barner <barner@FreeBSD.org>
 uid                  Simon Barner <barner@in.tum.de>
 uid                  Simon Barner <barner@informatik.tu-muenchen.de>
 uid                  Simon Barner <barner@gmx.de>
 sub   2048g/F63052DE 2000-11-10

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBDoMJEMRBAD9C2z1pr1D+V0OgztcnlU7sBqGQyjYFmzWhEDPquPdMQwIDtMs
 FH1QeE/90uc8J35Y2Ba1/O9b9zG13t2rSXz9zenGo89thgcaptTY527UAoNJZXqO
 1UbBsq+wfOuVTAnFSue9bdgyzqx6jmJpIqvm8J06iesBrXyB70U1oSF2AQCg/zR4
 QTdnrmfpDoC2vLpYdd/emmMEAJgbd14BbLebVrxUiS85dGbrWon1SxjxTza3vR1+
 3npc+VMpeoEOiCXaBwpMAq7dzbzalaU1dgkr031x98ZpXPIyEi9KkBLZ9kPZRzIV
 okH+XIZ3IU+eUFuLKuGg9xWtweOq4xL9X0Epe7uU3DouGaVN6i099zP9w2e2eLPk
 07grBADECiS7ejh3pYFwe9dSOKN5iI1SlAqNH69mvMEsPOPYVbsJmYU6dhPdEWa3
 O7o6CCho3gUejhdl+z7dnrsxHOHRHFAIr5o1gvIGkmKCn4H02KIr+S7cI11pqjJO
 mofEJ5w21I7Lr1fL7AA/7pZgnWePZaPeh9fXlQ8kAoJ/0UTemLQfU2ltb24gQmFy
 bmVyIDxiYXJuZXJAaW4udHVtLmRlPohTBBARAgALBQI6DCRWBAsDAQIAEgkQCkn+
 /eutqCoHZUdQRwABATxcAJ0ZfEhRc3q0UIY9eZtY2L+s7glyMgCg/UjC7MEKC1xq
 oHWkz5Zjz1oaXCKIPwMFEDqOp3zb0kX8s7KhLBECxOwAoLku1efxcFzT9B3loRuu
 lISktrZEAKD37jQuRlMyWf20uU13gSfJtCeLl7QvU2ltb24gQmFybmVyIDxiYXJu
 ZXJAaW5mb3JtYXRpay50dS1tdWVuY2hlbi5kZT6IUwQQEQIACwUCOgwkQwQLAwEC
 ABIJEApJ/v3rragqB2VHUEcAAQEnzwCfYt2w8JvMG7FD8Ae+sBa6bUpaB6cAoIQM
 0d25+IpshigRTM3djVgabwtGiD8DBRA6jqdN29JF/LOyoSwRAq9mAJ99N2SXxuOh
 SDt1dd3axBQS7U1dSACgjX8LFHWBZ75KSLNr22LMKuSEk1y0HFNpbW9uIEJhcm5l
 ciA8YmFybmVyQGdteC5kZT6IUwQQEQIACwUCOgwkTQQLAwECABIJEApJ/v3rragq
 B2VHUEcAAQFxcACfQfBW95c31MHGvSanzCk+D245McMAoI8nSI4dqDbGIPppKK92
 cq098ZyxiD8DBRA6jqds29JF/LOyoSwRAnNHAKDvjMCXb8PXP0zufz/nEksQwwaw
 4wCg0Li4kAQhbnKgLXOFq1sVB2GtfqW0IVNpbW9uIEJhcm5lciA8YmFybmVyQEZy
 ZWVCU0Qub3JnPoheBBMRAgAeBQJCHMdDAhsjBgsJCAcDAgMVAgMDFgIBAh4BAheA
 AAoJEApJ/v3rragqCKMAoM5MXsScnfdD/rKoHkyfIWAOrHQSAKDDLfdDG1pMsfMa
 /4O0QPY3LN9hFbkCDQQ6DCRDEAgA9kJXtwh/CBdyorrWqULzBej5UxE5T7bxbrlL
 OCDaAadWoxTpj0BV89AHxstDqZSt90xkhkn4DIO9ZekX1KHTUPj1WV/cdlJPPT2N
 286Z4VeSWc39uK50T8X8dryDxUcwYc58yWb/Ffm7/ZFexwGq01uejaClcjrUGvC/
 RgBYK+X0iP1YTknbzSC0neSRBzZrM2w4DUUdD3yIsxx8Wy2O9vPJI8BD8KVbGI2O
 u1WMuF040zT9fBdXQ6MdGGzeMyEstSr/POGxKUAYEY18hKcKctaGxAMZyAcpesqV
 DNmWn6vQClCbAkbTCD1mpF1Bn5x8vYlLIhkmuquiXsNV6TILOwACAgf/bGaz5lw7
 KGb1+Yl0n+GXfFF/OwDbujxVoGn1KM+dKbColaX44Sr/L60px4cQ56ZxX1e6hxJi
 TaLrrtx3bxZSTUlJuzuNdOA0vfcw4yQzrPql12op9K2DVeoo/WzBwZecM1eeg+VU
 s4vlQuG46c3NbeTvXpuSyoHzDVgf5XMtwI/qTditup1g6tlViur0BMrUNJ6WZSpO
 TLAgN1DKjuEi1FGVEs2n+BSEGBk2dM2325j6qYQtE6iXEEc18s/xyT+CSEQYfAP3
 4/4UsCOi4pmuy/+OlBXYEv7rg8O0EpUqT4Po0BbhrMCdwzlhbb3LpMHyTwYSPdEi
 A9+h9Mv9c0QK9og/AwUYOgwkQwpJ/v3rragqEQIJBACg27m44rBDabiRWXVEGny1
 8o9/o+UAoI65F9bRERosGt0m0f0q1WwwdGcz
 =HMUk
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.21. Artem Belevich <art@FreeBSD.org>

 pub   2048R/9ED4C836 2011-03-28
       Key fingerprint = 7400 D541 07ED 3DF3 3E97  F2D5 8BDF 101C 9ED4 C836
 uid                  Artem Belevich <artemb@gmail.com>
 uid                  Artem Belevich <art@freebsd.org>
 sub   2048R/55B0E4EB 2011-03-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE2QwLUBCADc/D9RfANjFOApCDIAcYU4QeKmbk+kMvSHrKgesr1OFuIMdQRE
 n6O8VncPlxRvElWRgLCwOOm6wW5KQDqAJ5poLzNh3GQ/DljGvZr+VmbK8BRVM/ik
 oFmzv/7ebDY8e72Hne7klT9K6TIIeP35BNL18ft0xmhrIlVQHWr4jXz0pl9gzIwp
 qnkuwdd8X6I/jsvPCEiXhqB0px/LEFgtJ9OR0k3MW48AAmVir/aWAQJ3/vysNLXj
 T8jJSm9QDZTuyFCHmT45TYhx6oanFexpvGXtYr62cBAk3rlMiUcY5Mp938RQzjXY
 dB7dVHoTtDSb3eJRL5ZZpXROiVnulcRv1ZdHABEBAAG0IEFydGVtIEJlbGV2aWNo
 IDxhcnRAZnJlZWJzZC5vcmc+iQE4BBMBAgAiBQJNkic1AhsDBgsJCAcDAgYVCAIJ
 CgsEFgIDAQIeAQIXgAAKCRCL3xAcntTINk42B/97vlVDERJfPNRg5kUFqW+R7VHN
 q1atqa6xY6r4NZzjmtkeyDVItzwSOohA0H1N9NsgNaJStcuruiqyfekohnZ3xHKi
 PMOwfebH1zX69K+J7M8GAtrT0APifScd+pU17kphhqjLoCoH0BY3AM8HR//AJkKb
 U68GZF1fA8LWdRlfx7xZSalPyQXMibXtfmb7t/AqoNgQYs2nXUhs2ENZtZHDAVlb
 2/LkDJ6OezOW7/Q4KZyeYcgzXYGchkXGhCV+8fiP5JZMaXZocJ8saO1R7pxR/fEu
 Lc9oQUCPzx7m0bI/mgmO3aKOREXrQTRX5ZwfAuLubEHougfIMfzIfAq/Iiy1tCFB
 cnRlbSBCZWxldmljaCA8YXJ0ZW1iQGdtYWlsLmNvbT6JATsEEwECACUCGwMGCwkI
 BwMCBhUIAgkKCwQWAgMBAh4BAheABQJNk67XAhkBAAoJEIvfEBye1Mg26o0H/0f2
 oHP7o9zgcetork2zFEAlQyDYHW3X3IXXMrTk7xWsHJuu6hyVeeDuVFzp8TkrNOVq
 P9+hZqzy9g40iFXzQkFWo0X576XokQXk7rAqYCr0OBUDZ0uDrltMI1VoEtODCcdc
 bJMd46zchrhq0vl28FmwAXX0F8zH/9I5fWH/KWfUlQNGs8NklCP2HueFogrGeSNE
 lHVGmIJPqa90WXWmDZOBADeMBiWqLzgWR/0Vt48B7PJ1vwrJCyedbTGlwdbRaXGn
 g+Gyx0933AgPWiqobSvXOddqXVXj95YSqEVUlh3BQlj3ZbOxbkleyhf52mi3T/jp
 AIztYwhSi6iUHj/QRGiJARwEEAECAAYFAk2Q2MEACgkQ/95rP8ShvBXBLwf/UIB1
 ITOTfkmDamaR5w3FEKjQU6xN+LBy3+EBwcRiF5ydYLSdPmp5WpVc7EevkT+9Z4CL
 zzUQtx+Eyeql1W1PuK3SRAY98cmtNTE9A4KZyeCRgdoUiYqZl0bIzNKpAbNEFdKR
 CGOqt2/VpvFwePuVM65r06yL5qpL1im7Qlb3FUw40haczggd3nGSfq3kVj1Tmii/
 qDsT2ozkgIqbP6ubFXrLrElr8f77cd0F6nSnfjJdidju1WUsRPdNOhaJs6b3xIla
 BITUdDmfW30VJ62iRNhejbYI4S3zBNQt6yeGQhD2rLECD6ApjYjHEkMgBelnnkt7
 u1mlLz1lrGvk1dLnIIhGBBARAgAGBQJNkUtVAAoJEAsVQr2N9aGwA3wAnA2nWLTn
 E3JUtZuYrJ7NC5CHeV4mAJ0RVXXg9vDYFcqBmQnBNHWcmyAXaIhGBBARAgAGBQJN
 ke2gAAoJEG/I2r1/mpuimZcAn03PXI364s2DGDD50ClvVWyGaVWPAJ4lXabM9YA5
 1JKgYqXLUPCcuo+pyoikBBABAQAOBQJNkeaMBwZhcnRlbQAACgkQZWCprDT5+dW0
 DAP7BCGFNwYNpunxjM41mk4LRgHUAmeml2n2iVM1rCx6E+ph3SoFORJBJVLVaExp
 GEgiXA64K70M14aaN2BVKMjxmWyRGcjbXuslWNzWi2xLFX9+g/hj42CjW7+0mFZe
 /kXb/5Hnj9KnKGjaUKtyz65mIH6OVBPjdw2tJwCB8kQsr1uIRgQQEQIABgUCTZER
 lwAKCRBO0l+IUo9QMPMrAKCo5kaHkO+E0gxZbjMA+3yHdMvTfQCcCH6ssxbaAdXS
 lL5ASz/aIhXEZbmJATgEEwECACIFAk2QwLUCGwMGCwkIBwMCBhUIAgkKCwQWAgMB
 Ah4BAheAAAoJEIvfEBye1Mg2fu0H/3dwETQ93nmEorD13/Elyp8SNPiHCoLyQ1uF
 GMQyLkZpqazvzE5WKdrwdoWLHkqMKevm8XBqtt9F94Trce7iT249tYFyMQb2+Irl
 Xha6DVFYE9y0p8vfc1nHQnn3xyHrYA1jFRN9Rt+ha3YKtALq7iSKleovJLwvCHqF
 8z1IPUU3+8IOw/2KzFMGb2I+vs4HbYr+Ed0UfZVlONkMHyHfZPN18jUZbUqNC6GU
 5TXiVmy0t6WTsth6UQY8d4EpIP+4griCAevy8Hqq0GnBUz7eyHoHJ3/U/H9+1NgV
 rIFHh+6UKHkWkmVM2wTM+J2E/bB27bNmt8noNaxHDip2MEzZZGe5AQ0ETZDAtQEI
 AML9itZRzpVYiQDfGcj0/YgJP/y2jEDGNnuN7Of9sVhhzxMvEXzlSd631b656kdT
 WcmbBim6eDtjRlbKJIAIbDyMXekTl0LLwWL0yfzaRIXwFxoD2CL/BbmWvwaJeckW
 VsIrFIXK3bLWulCfA83foS76azHVSOOp9EZQg/cJOaCOt1zyvS8rS8Qx0QBp+vSb
 ZHA1lDI2WYNoAm2e9lb3wta44es9VaCBWobWMRgHxIWrkjmZs9e4ejXKO59YEkng
 S53AylrZVYlyrKbeskqmxn7z9y6ciniFD5af5cEcGfuC9BH6i4Jwma+3ZWgGDZI4
 lOgzLWd4TS1ZD+jAeZkpwZkAEQEAAYkBHwQYAQIACQUCTZDAtQIbDAAKCRCL3xAc
 ntTINmuwCAC41x0gd7aeTRbtlNhYyuGmHo/yHMqHdjmiXTtsBCrsipSAQZQiNiUO
 XupVArSGB7MIaatCtqviOAyQ42172onOzcfB/iQRj0bknjNbItJMqtOFz0u79vN9
 JmWxYcFr5Mf1l/pupFcgNM0zt1KQkeOGm5Y3WJkq3CkAqIsd/MDbUU91Y6kzj3ZJ
 g6uoPYYKThH6KX3Y3undXTv1jlmPdbMHUYFg1GzvY2ujQJeQisMDfxWV2COYSF+Z
 fa8kp8xfSMnCWJCnbnmDdRe1W3zQ2uDKvoLBQNoF9lLrYAEzu3M5wKS1+W1Om00P
 yCBkjpo4Ly8FcmqW800W8yVAArhNUCID
 =IDLa
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.22. Anton Berezin <tobez@FreeBSD.org>

 pub  1024D/7A7BA3C0 2000-05-25 Anton Berezin <tobez@catpipe.net>
      Key fingerprint = CDD8 560C 174B D8E5 0323  83CE 22CA 584C 7A7B A3C0
 uid                            Anton Berezin <tobez@tobez.org>
 uid                            Anton Berezin <tobez@FreeBSD.org>
 sub  1024g/ADC71E87 2000-05-25

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDks22ERBACsqOob/YoPnaI/xubQKn/CCUFsaEMqL14TZ+FSlCphq3uZ7Y0W
 Qg2eqaTp97lG2NTVNEzF7K0yr/C3ofEQmTINQTd7DmEj04DDlR+t8BMFe6Xz2sBI
 WlEPD54ZfJVqhEX5P6T0xe9hiqjXKwQHHl1skKniKeO07o3K/4bCDDMfKwCg5DY1
 /2j/Gid0YmxsJCIlg9kzRGMD/1lkSkQ0KrPH3RVPMrkRWE3rvvMES/F7jYNfKDQj
 X5lJDKoIQyWh1JwAmW/O10V+24Vl6JEFNQ4QJ7ix9hlkI59YS4TERxCUGGDpl3jr
 Lae6FFxYc1D5H8LLpiTSApmZcLxUE8CFoZJLySHgjp8qzvA60wMOjkfkWMgw3BpE
 N8DVA/9UF+5ue4bLHsPn7Jv5NzOkzaTgC/9O3UZUj/jYOp/vkI+0wPnP0U5f304P
 iLpYl1tlCEpciWF88MS5k3+8zsk8trqorss/XQfFzhHVtvRtgVxj87V0Z01E2ZZr
 YlqrnzHKQZOAKM2X9FiRZOAkndkkpeB+7SSeXDP62I56B+690LQfQW50b24gQmVy
 ZXppbiA8dG9iZXpAdG9iZXoub3JnPohWBBMRAgAWBQI5LNthBAsKBAMDFQMCAxYC
 AQIXgAAKCRAiylhMenujwBepAKCCtVcVRS40E9SY4Su8GTOBVoH4UwCgu3gK3zMy
 /QhZnnhmTKaguG6XopqIRgQQEQIABgUCOSz5ngAKCRCBvdPEDh+beRnEAJ9xU+6P
 TJrLGk8PKtO+UY8Zt7MTxgCdHYzFsXZ81j9HY0Z4EaHkQBXv1JmITAQQEQIADAUC
 OS6PpwUDCWdTAAAKCRDXjLzlZqdLMXMaAJwOE+6Jh5PnfHc09x3JKN4/a0v63wCg
 6GdysmObSBQXATzYBuhy/0eFCCC0IUFudG9uIEJlcmV6aW4gPHRvYmV6QEZyZWVC
 U0Qub3JnPohXBBMRAgAXBQI7JNTmBQsHCgMEAxUDAgMWAgECF4AACgkQIspYTHp7
 o8CQ3wCeI+P8VsHzHpfmUMa5kCzjBeqj3zcAoKYmyZUSxhV9TBQPo2WQ7zF3zcoB
 tCFBbnRvbiBCZXJlemluIDx0b2JlekBjYXRwaXBlLm5ldD6IVwQTEQIAFwUCOyTV
 DwULBwoDBAMVAwIDFgIBAheAAAoJECLKWEx6e6PATIsAn3clXqExEiP/Q/IDQb7e
 /yolgMrRAKDPw+6ZxTOJFba2HWEto0PwQ/COE7kBDQQ5LNt+EAQAjHltp9g75EOw
 pEDSUvK/B0aRUsjoIyAokRuW9Tg8S0xIhtV8ogcklvcXjQbjiEsAiO13hX7zmdmb
 yH7xLiSjea/m/whmNr9K094BS1K5i7mmUqNEFOyPB7VkPbRs5gF0dCkHT5uVgqFJ
 HSbss3zPyGYEBi8uDokIfOt4o5CEMYsAAwUD/269N/UwZkO4+NYivNX0ZpcUouqV
 YDPQ8YLwSrkwWpG7UNvNHd1HS43OWwAOy585SkLpZkjlW58NqyXJuWVC0xJtdTrI
 MKTZ3IJNXMK2wdK+nBuTL4IvJwkf04pwFel80F2NtgUjR3ZgIlRNvFtvtCkNPg0j
 t7J8pPvL2vU5hz7HiEYEGBECAAYFAjks234ACgkQIspYTHp7o8Bj7wCfSZsld8vv
 iM02pWobJy/VvsBJKU8An2auT0HLmVLClDph/fQa+k1R2qsR
 =ISZ3
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.23. Damien Bergamini <damien@FreeBSD.org>

 pub   2048R/D129F093 2005-03-02
       Key fingerprint = D3AB 28C3 1A4A E219 3145  54FE 220A 7486 D129 F093
 uid                  Damien Bergamini <damien.bergamini@free.fr>
 uid                  Damien Bergamini <damien@FreeBSD.org>
 sub   2048R/9FBA73A4 2005-03-02

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQELBEIlmIgBCAC0YtqJTRZ/ri1bBd6NyFd3r4fWx/M5NeqIYOa7S1x/b3wjlAdD
 Q6/mPMkGYqtUiQx9kMhrmZJHz/nC6SFxw0nSxKOfsvOQZgyJbeKZ7NS3SReOzUD1
 Xao0pt6yPH9eeLduI9R5AL+XMvWvPfWgh/kZbOoC25F3TrQQkp+lbmu//cxzn6Y5
 OybyTKiF0heYOcBOrmtp5AU9LZWdsEH2rDXBnEIFLTL3qK/HuJariizqUnPjDb1y
 OfNldKLkcq3Cs8QNpSGrrbWMoLvCtIXAY1kYRywKfT0BgTH6JOoGz6n1dLQHKubZ
 WCsyqzO07M43O5vhSLDXS3L4St2srV1XblaVAAYptCVEYW1pZW4gQmVyZ2FtaW5p
 IDxkYW1pZW5ARnJlZUJTRC5vcmc+iQE0BBMBAgAeBQJCJZiIAhsDBgsJCAcDAgMV
 AgMDFgIBAh4BAheAAAoJECIKdIbRKfCTKlMIAJmIx4DZmHkbpSHxERQyN4kQizY/
 x+7L2CuwuAtjabo1wlcE/XacMx01qN7FL931PGi9UEWxdp3FTu2MMH4e7DmY0F8A
 7oEbFecE1bjDRKLkRBFo+R6yHvZ9YjGB7dFlsTwaM4FpTfrgg81j3MSIHdg5i8G6
 OA5eBJSiL7IN3ftcxIoutYXfPnrOksba7ThEZ9631ft3athczyaISAtdQkIIO7J8
 pBBTkE4wbh1AzPRDmeN8DDU9h/pH9W0uVTOCqhAXnSE9C5kZ3SBhvXBPeN9vtHa6
 pyR6uqg2+N5FSJ5lENvCeRKC2W80m/an8n/1WCK6QuFTr02uVuGShksBTdy0K0Rh
 bWllbiBCZXJnYW1pbmkgPGRhbWllbi5iZXJnYW1pbmlAZnJlZS5mcj6JATQEEwEC
 AB4FAkIlo0sCGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQIgp0htEp8JOVTQgA
 nah0cBkhmPhPVVKNGTQScbdPgu7TTLcAB4SVJHN4Je8ml/OeWrIaNXeQDD8wdfJZ
 svlddxvxB8r6ScJ3ZtLsSHQnGLejgiEsHEO+Fi/xmt1D+pn0l2dK+GMC4E8dPd5w
 ZGLg9nFDZolgLQP664eqzx3A+NSgh5A6IteAtrRDg+3uzlquhJNWqup01pymcery
 Cv0rnMaZJTjE2IsMyzc6hw9CQ9AC3YVfXT/xMlSe9cB3C1EDtmHkKQOpzarheQOT
 Xi4rqScHJTevKT4Pz50uYwoAC8B793ZRKJ5cYH0G3YuDB4lhPaOeAxOi4Ftt97De
 HTeeIqXmrDV2kOu3t7ifTrkBCwRCJZi8AQgAzF1fU7BHdNHHTFTmT9f/TWIoEhsv
 4oKue/cyAmVGjeg4jEFn6001JWjojzxe8IZzdYwAgOwHGRbfxiirvd1nzxJlOBVg
 8BfrplMcRAMh61IprrU310cd6tVDyxvFqENLM9fgCnAwWAEldZoOSBBgPmiV5+Cp
 xZJu959KpsoG6TuAn2PYUXdttjvdGgzU0lyji43GHZ58yJYtruFfikWoXJXlXvuh
 9GjNqFk28vKi4b7HBR79zvtyQLT+xkRLcGMbQemLeCQmi/O4umDpkVovDn/FgaPB
 iEZmtRbHtCAODO1vW4YrYvMYGlB224hQcUuiOiEMn8P/oMkg8dXe52xFEQAGKYkB
 HwQYAQIACQUCQiWYvAIbDAAKCRAiCnSG0Snwk/baCACJ3Ed4SX2BTo+jqt5f0hZx
 OO4s1B3MAD7y8LzL85QySYdr/3e5i1IrgLTVOH1UQQ2Bvpk/Ly3M40FBUapHzuOa
 TpOfqk3nHwj+o7HuFQr3yzVl5o50fQPkXhwf2PMr0iQLuwHdFzmF/A5aNW9lunsT
 ICRXApvEEQU/eq2nSUrIINxSYbzuXHfkNWjcFX0DIv3V/ZKBxCnVQknc7YFXmqXC
 PEjAsMS6mj7fzkr2c+JDH+AK7Y1gexDyjoSqZb7HeTiy1c4x+UXDs4605XAwKpZK
 757qxfG/ThAKmn2/xiy3bCYmHR9PQ0lBCCkXdNeRgdklUkawzZQdcqrO8ElYJERp
 =uQuq
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.24. Tim Bishop <tdb@FreeBSD.org>

 pub   1024D/5AE7D984 2000-10-07
       Key fingerprint = 1453 086E 9376 1A50 ECF6  AE05 7DCE D659 5AE7 D984
 uid                  Tim Bishop <tim@bishnet.net>
 uid                  Tim Bishop <T.D.Bishop@kent.ac.uk>
 uid                  Tim Bishop <tdb@i-scream.org>
 uid                  Tim Bishop <tdb@FreeBSD.org>
 sub   4096g/7F886031 2000-10-07

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 8712 characters]
 5ACdHjn4iuMiXZA8cDDPAi8VybndPak=
 =F66Y
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.25. Grzegorz Blach <gblach@FreeBSD.org>

 pub   2048R/D25B0682 2012-11-03 [expires: 2014-11-03]
       Key fingerprint = 225B 941C A886 05C6 1C87  9C03 DE72 593D D25B 0682
 uid                  Grzegorz Blach <gblach@FreeBSD.org>
 sub   2048R/5DE28719 2012-11-03 [expires: 2014-11-03]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFCVjegBCACjZOtHgTAG3s3XOVJt1VVM3LZTKKx0K5Aip1c4TDetBTkNIPCb
 V9UiflZUGv9v6OEF0O5rRwS6WwTLxjhuA9io9mSBWuCfZywsRSShpZQbEMZq5/F+
 OgHOMav3Gc+ITwvM/nFPtU2OHj1h3t4n6IBbuVfPh4Yb9TJsAWQlUchWAOBj7CG0
 oqfR2PuDbYFtXNnGVrpZZuxxBI9onvY0n5w2gmtmO9+GFQ8Ob9K6EI/jwqPVGSQK
 Tch14aaeRF5Uh+Ua7UDXKyZFBJUuGEvtHcn7eDNFEs4SY4tW7he6VGiCwr3gU3pZ
 CdQwEUDwXkBm/JZ8JjsDOq8NVtTX3d0mViTRABEBAAG0I0dyemVnb3J6IEJsYWNo
 IDxnYmxhY2hARnJlZUJTRC5vcmc+iQE+BBMBAgAoBQJQlY3oAhsDBQkDwmcABgsJ
 CAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRDeclk90lsGgt6gB/4vyw2faWL5MntH
 grGiwqdeCdm1x++zGjxrs30RLaHPmSVXYA/bQIBbnVs/kR2wRpCO9fxl9xQ5bBnZ
 vHwK9+hbGqli/eqWuvgwRYmkIAd/xLVN8Ffyj73RXRead6bmpOQ8e2Osabttyccc
 Un4V8OZptpIYLbdnVGsiB147GYnooPv5uJ6RD+Wz+iSORFzcFEA6VD0Ft6vxe1on
 +dBxpHO8Np1wID8JH3Gl6oGfpYcPsp1QVknMZ197+94QNHgN23xzDVuKkbjFb1Du
 N7SegRdm1wwhF0QlqIWPIQT8jXY7WX1NWV6ns8gOUXChJxGMPRsOxCuhQJp8crsS
 q32CqqDmuQENBFCVjegBCAC56QSMFVZjklZSA9mxNm6GZyBcUoAYISM2hg4QSN92
 /8CY84TXiAB9x8+KoYeVukMu5B/2BhNW4bWA/3GwMk0tn1s2ZEVFz9ZbTBPmTA1Z
 x1wZOKdr4Y5feOO73ouBW1cyR4AgbYEsQtllfb3yQ2CukouEJNjesDT+zDAJnIS9
 JG+1MGngMIxddKasNfBliiN0iNNbGEKpFvcNpTBnIpbQ55/yMMJ9CZmey/1HFKBO
 setIET7f1Z3f2tUoxku73QhwfwBlrw269S4Aeuvk80bZa1YZLoQiZ5B2WqFz4V4H
 uxk9WgqOQ/gJEFCOYkpLjSctCuFQnLefsV44gveB+LU7ABEBAAGJASUEGAECAA8F
 AlCVjegCGwwFCQPCZwAACgkQ3nJZPdJbBoLnwwf/Z8bFOlDaLWkCP4K8Uz6kHGno
 nvRPc6l76aJhqDPceEiDU1DumjTSokQNj2i9jKqhM/b2cPLIwWbYbkypLer9R00o
 AJcM1i2nkZXRLRMIFfQTZUmXMSZvZ5NG+MyiSAI9zpfw/psgUUad6mDUZafYVWez
 KnCFybbJ2TwcFzFcHxi4desKNnrh/NTIt7XyFVof9Wkz8Zt9cGGf/BxQPA9oPbvd
 b8wN9Yjegb4OunNmHc309cuVCktSlr7u4kdMUn0LuZmi4xZj2XY0+GuHErD49G1b
 x4+G59TE5S619vSAcdjtmvXDvV8no1Y9ENp/blCkeKcGBoWZKc6dHSw3RsMawA==
 =/8wY
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.26. Martin Blapp <mbr@FreeBSD.org>

 pub  1024D/D300551E 2001-12-20 Martin Blapp <mb@imp.ch>
      Key fingerprint = B434 53FC C87C FE7B 0A18  B84C 8686 EF22 D300 551E
 sub  1024g/998281C8 2001-12-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDwhwB0RBACelK3FYxd6cT5ukbiSdVLHPLfzgH3F34JfS6Q4FMXgEAPtx7iy
 U4Lc8A4Z2gCq1ZHBZTzKc61U+nzHe+eUWtAj0h3qDP4DOd7JCZbh4SW6dMIC7MAM
 /9J5br6e2fIIn3rzbROXSW7CJPox2D/zZcT1b727Wgy5NHUob3qej/zhwwCgrZ0o
 KBapUXgnKhesQzKlH2wWCJkD/3njAzJsFS7nDdTssMtd7ip9W97uNOFLuJ1/Sg5S
 332BUby73hNzSXlS4rhtQB6NVBRLfGASuEYBJQIEz6aao/lDprIxTusCTrO/EGqa
 Dy5y4XE1ClIyZ0yVw05UJiTOZ7Mu/kUTBBzQ2i15lxjzXBt9pNifvtcKBhcDmdzQ
 zepQA/9Jio4IBFmjPDsl3kpvA8KqP7VXKFMMBVT9SztYVIeiFgbvff/YCqzkE5RD
 0PWUFPF3o8rzsCovlpySfUNLUlfqxEZ+5+/5ky7AbJ6Vmyn7Tl+mBSZs4mTV7ktN
 526ngUaW2j+aO2SdWao/di+sRutrgRjJqyvgGn1YGnrSoKbMJ7QYTWFydGluIEJs
 YXBwIDxtYkBpbXAuY2g+iFcEExECABcFAjwhwB0FCwcKAwQDFQMCAxYCAQIXgAAK
 CRCGhu8i0wBVHh3IAKCDMueq8RCcRO+3Lc+uQyXqDKCf3QCgpVWa7oS6lTiNxwSP
 enZ7+4g+TkK5AQ0EPCHAIhAEAI3iAhZEDBjyJvPS74CXq1ypWvXfQUCYADCc/Cuv
 3xrr1p4ff3oYc+IIVdeOQktKWRP1dK7v1JLmqFsNQQIs+NtgHyO+azyX5vJGVRTg
 aCIuMMTnrDBC7VbAnWXtTHF5VKmmd891Y+nk68p5YVnRPc/fReXEY6dA9lqW0bN2
 f2jLAAMGA/9rMbPpnRy+uvaAQChkHvOV1RnDAhN2R+U9u3d0uNnv7sWa/TJrcdig
 KNUsUvXqIXVkqEMrYHTbCVC4mLMd51MLARiIKOaHeynRZYkEmdi5X7EiBLS9dCUe
 7+vMz4jV6MRIGyr8TBy3CEFIdAnpY6EIVd326PzYIgx8UZw3oEvjGIhGBBgRAgAG
 BQI8IcAiAAoJEIaG7yLTAFUetM4AoJg56qwlr8E1iEs0F33G6POGCWnCAJ4mW9E3
 25TD51pcom8Plwy1BkuBSw==
 =oE+K
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.27. Warren Block <wblock@FreeBSD.org>

 pub   2048R/A1F360A3 2011-09-14
       Key fingerprint = 3A44 4DEC B304 5191 8A41  C317 5117 4BB6 A1F3 60A3
 uid                  Warren Block <wblock@FreeBSD.org>
 uid                  Warren Block <wblock@wonkity.com>
 sub   2048R/51F483F3 2011-09-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE5wBOQBCADWbqntvghQ1fBqaz7e+TmdobJf74hD8lC5f5qfAn6iGwbSJf3k
 3wWyNJvXYVBXzDaYIuU0R5Chl3+bKN12CrMRD5oUpFEtmmzRObHfuGCCAwHvxt9k
 ex6ektaCwriwoJanRAhxGDOihUt6Z4GPh5N8ye50HfDC7WehKNs0ovOCXBFAx73d
 uxWDno2eMawnveTjhXXo+XGxqLWCZVs4cu8RR2xG5W1OXCsLaVRy2xuFRd8gRhjA
 46XN4T8H7Db30tLKVVG0bzA4bhciGnS0BNaU3D3sdF+CzF6gcQcEwMirit1PLIlT
 X4rRYnzRaGij4keLJ/nccasdhK4eDCFHQpuJABEBAAG0IVdhcnJlbiBCbG9jayA8
 d2Jsb2NrQHdvbmtpdHkuY29tPokBOAQTAQIAIgUCTnAE5AIbAwYLCQgHAwIGFQgC
 CQoLBBYCAwECHgECF4AACgkQURdLtqHzYKNPOAf/fXurCr2Ma2zkehWSsi0xXmpM
 V2U19nF5l8FoAkOO6yZ3KIQffXmYx9vNG6LpHss3VbZ8HwMQW/Mj/HU2iSElT/vk
 njrSTn+OwwPEN3C9eqTAXuQ8LU2QAVf0GCviKD8ptMiwBLSHNeAUeqxqVzpbGjNP
 XcgN+dBBcmscog1hxRA4DvxaCFCaH5aQ1YTyHpOiCmmno02+oC+IwbKZP8S3CX54
 8opqPH8R2x3QD8wxHfwr/fgcbFZ+DFjcEIWBLgpbur1qJd9NXerWtIOfQLn9yBQD
 paHSmyETSoLQac6GnuUE9c7Y4mt7ONA6dYe8wW0u7GvRXITNkUJ/RvjdYLyk5bQh
 V2FycmVuIEJsb2NrIDx3YmxvY2tARnJlZUJTRC5vcmc+iQE4BBMBAgAiBQJOcPa6
 AhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRBRF0u2ofNgo5UXCACAjadR
 flSIKuZu5KM+9W+VMDrPGvji4g6aJbFFXWq4zlmYYKp03kiqTRPAKtV6D8Syu5SC
 2BuX5yYART0gTkxo30uRws80HkZDAs7Cc8eFgzAf1YJyljYeIU4EBhxxMrF2EoUE
 wSdTM5JFk/jgZpidsdpox8o7TNWDGMLe9cBn1TPJZw3TGSRQitjdwfnLGGjsCNp1
 4HOkbqWggUIdpET3WaAnpHhT1FBnim5rNOvBocReXO2F2vtkqfaKD2hzc6qQMkPz
 64PLqAsVTwwCtSEein5Ukr9cb68nn2GmBAZHlA5yu23h0M1E674AR7lR9ounAMzY
 bNQmQlq+tbSPmDBLuQENBE5wBOQBCADEU7rOPsqF06y46wCqfRu90Sq0Gy3R6GQL
 h1pubHbb4IQ1ep1ZcaD1Gpx4KvrMKCaha+iOVDN2WsDzl4vrB0KQNyeqtwDHZtcN
 VQ+RORHh/3D9YOp5EQ+ObJQddl4m3f5Y2AJ3kRG8z7rLxqlcvnPmuf7MYXg+zhai
 EcSYnbq89vBRiyzpZIODuXcGbuvJOdoAt+sf4CmAwe9eh1LLN+OErBjs/TjAe9n4
 Kb4rUBhrbrCHHcWu3vnQcABfTOlWZ6+mr9wkl+Yq38nsZHDIx2RCrbDMpEEDCAlg
 WJ5ceqFdKz3VS+zKk+cz81jPREBOFBfRgVWMpAdsJFXhJU/1ueiPABEBAAGJAR8E
 GAECAAkFAk5wBOQCGwwACgkQURdLtqHzYKNKIwgAwCmfYjROytjVozXhF8Pw/DfX
 K/V+KaceWMlMjQfZgxA7pibbb1+Z7uhwygLZrGV3+QH/htdDQ1wvZrjOLFl9AIMr
 7ylObT89n99riGjDNpNH4urIyO9Oxjoql5s6RMlpsOlnnqlstTzEHZa05JvpZTbI
 XKBr4AIJ45uqtr9fFwvoNF6W9NeQrDXYDjbTVrbQNbOEfRIE6tTr9csNwaFUNe93
 eDdhkPFNHu+6Yrecm1DhVaVwiS9LKp4cmM8py16562Cjqy4msnSHpCNnQlBLgtv3
 T2BXRsuxVCXviMsADblyXqB4b/h00n9rDyE3Db+lsrTjX0nhAyBGhO/XBnC3ng==
 =Hoyp
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.28. Vitaly Bogdanov <bvs@FreeBSD.org>

 pub  1024D/B32017F7 2005-10-02 Vitaly Bogdanov <gad@gad.glazov.net>
      Key fingerprint = 402E B8E4 53CB 22FF BE62  AE35 A0BF B077 B320 17F7
 uid                            Vitaly Bogdanov <bvs@freebsd.org>
 sub  1024g/0E88C62E 2005-10-02

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEM/sJgRBAD26RM3o9QC+V5JO6/zr3ffRnNb08Bc6YIvpTd8yUhc4AIa1Zbg
 QHoUNZ0pOLffeZ3i0wnqV3lMV1cPMtvSRWlvh+XSiSg8hYlnh7+oAwmqs0Zev1r7
 w/In683ytXREuidcak8qWq4GAkET20sIICV7Ye56HJDlKrtOjUWDhVQJvwCg8jUp
 CDtJ8V6Cw6GgjxH1iaNR1X0EAMKCUJwZgIoh2Rpqfrbwv92AD7dmaJJLVfnUSMCE
 GvjcZ+O41PpvWi3PkxmgA3Zb0sJ3OSfgPi3Tnj3Nllyhqnf3WO1Yumzq3myBg+F/
 qH9a8BXvVJlk/2cbYUC6uJeGMCC971X3hceu51J41k0ano7/ALIWeoUC1HhkAOaP
 f7IoBADkQCDuIvdJ7KebBMgXIHwAJnycVZsXXQPlOx0gty4+OVMY9PfpEm7T+1DM
 mWwuckntM9tSYuInbUPco70LBxuHHBNnhiUOTkijZ5GK/VF+WPnqOEopkjL7LD2q
 wSYqGaBPbl/noAoEb3Nx7h8D94kJUF7Gchs9fCH6UxHd+/Q8jbQhVml0YWx5IEJv
 Z2Rhbm92IDxidnNAZnJlZWJzZC5vcmc+iF4EExECAB4FAkM/sJgCGwMGCwkIBwMC
 AxUCAwMWAgECHgECF4AACgkQoL+wd7MgF/cbhwCghoShm9pCHbiUjXin1mR+0HaU
 XvAAniOPVmeKUuBBKCc3KLPIhfCCKt9viEYEEBECAAYFAkM/zzcACgkQhdRQRWtp
 GwOrjACfRJUhoojMI3sBMsjH9IuCwj8CikoAn3RlHMmCAx7JIiAMmg2gC1qjIUsU
 tCRWaXRhbHkgQm9nZGFub3YgPGdhZEBnYWQuZ2xhem92Lm5ldD6IXgQTEQIAHgUC
 Qz+yTQIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRCgv7B3syAX91XMAKDJ89F+
 46BctXCALIn53c89waWDrQCgmCHSVr/rVUMU6fnyHtoNvYXtkFuIRgQQEQIABgUC
 Qz/PMwAKCRCF1FBFa2kbA/bwAJ4mwlXag5w3scB7heyAtqr7w6491QCghh/fVv3t
 EOFNlmwonrudaMSIYTm5AQ0EQz+wmRAEAKke9/e3jLaDx8i86+J0eTOAypCQy7WU
 QajhZDFqBHbBQTDRbcYG1dLYd/sC9oUwqgaLe+yEYw3JdfsiaiHsE2yZ/S4S2wTL
 7MrUqOc1aVPu95c3Xcef13DKCMx36B4EbMwJa00bU5ut6/7tHly5Edb8nkn5vKP4
 00TbjMa/3ZCHAAMFA/9OffxCzJmwUjCOxAg2GBberPxovtCtwAw7goKZzuga9+9Q
 dZBICMIc4l/I+zjDlphF/k9I5CQGOwoKTo+OCsZN7SSAB94NV9BEoA1MX9drWv0y
 CZJlD1bSrcPFVjWajXqC6NpAAiCdQapvV1sJK0F09v/RTHdPAZcRnpg/YS2jDohJ
 BBgRAgAJBQJDP7CZAhsMAAoJEKC/sHezIBf3nP8AoNBIM6JqCrnzQealKln3Tc+t
 HMPIAJ9td+R2zFqwuX+IMk135J0T/PXeaw==
 =bBFz
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.29. Roman Bogorodskiy <novel@FreeBSD.org>

 pub   2048R/08C2226A 2010-12-03
       Key fingerprint = 8BA4 DF2A D14F 99B6 37E0  0070 C96D 5FFE 08C2 226A
 uid                  Roman Bogorodskiy <bogorodskiy@gmail.com>
 uid                  Roman Bogorodskiy <novel@FreeBSD.org>
 uid                  Roman Bogorodskiy <rbogorodskiy@apache.org>
 uid                  Roman Bogorodskiy <rbogorodskiy@griddynamics.com>
 sub   2048R/EC4ED237 2010-12-03

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEz5PvIBCADEywRgDxobBqM8Ue21Jh2U7HgS4j5gzACCKF6H++QcS0ohTbw1
 HQXsnVMNAwp3orG+ksukxKyxOFVnf2oWsoQ+ZKg9+jKg0oU2fnTgsqlVjTHrWHXR
 Gp51w+swR4cQQMdO/v696KGD6igT/PVXUCliPl/SaSy3CMxQnMJiNVcUCf3F9Y5D
 vuceManrZJ43fX6ztkHuhyoGxH/AWGNU2UkZO6TKYo7zJ1TNG437gDTyKy3O5gtF
 PTqJ5OknqJPitoqLXBksjCwq3iyDmqKkppSi8JO2Su27pgwmNfRWo8r4jnLVpEpH
 eCd7Fu/TimB2McIw0mJgN4tveZ+u/8RpAXQfABEBAAG0KVJvbWFuIEJvZ29yb2Rz
 a2l5IDxib2dvcm9kc2tpeUBnbWFpbC5jb20+iQE7BBMBAgAlAhsDBgsJCAcDAgYV
 CAIJCgsEFgIDAQIeAQIXgAUCTPlApAIZAQAKCRDJbV/+CMIiaj70CACwDlzGw16o
 /Ucu1vtK5IOyIhChX3hHSp0MgDYcw7hVpmSvOnjIxgZfXHRlRVU0fvI18HaeHjQT
 iQ5MtEBnrUoWKFzMDFp8+vJ/0bDtDRIjIRMDimIxVdhHddPsdtzVLDJjbjG0TG29
 bNp8dU5eUyfmtxOeEckz198WrkKVc2l7Ynh2n2KacslK86nO/KQQcHSj59Builns
 d7GBdLGZauq8oqowM7n2NoMRWDkX2TqVQyL+a6diD29KahcvF9wXNoTw8vVox/gP
 gUdmclhktS8ybV8eSd8wT+4lT+s4Fnv1Df3yMeGhMHYkCyaUgdgW+4mE+olxsGZs
 PdrCevva6DsMtCVSb21hbiBCb2dvcm9kc2tpeSA8bm92ZWxARnJlZUJTRC5vcmc+
 iQE4BBMBAgAiBQJM+T91AhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRDJ
 bV/+CMIiajt2CACNuGoZu99U0gubBgNhrmAg1VuZTGTpi0PtqQ4i1+K3nWdne/di
 lpgD6PKNj2IWH9CRQpQ9XnGw1HnSFgc1YjNXMNPCF7zwkjR5rWKH0OJ8zkK/bpGl
 KymWLaIxFEaCUZpyuDWJBLXu8u680RTU8+6SDY1iDB7Wu6OZ4OIrVCPEpgLgrsGq
 eqozWHyS4L8Lqa717lmRffv78fRxWh9AdetpL6EG2IMJ4SyCTOTveT1H/ylMZtiq
 Il169YHlNut56Dr+Hu1BlJ/1YqWPFbQEyhRfuJKxt2XFyQDC3CK/9eVDDZfiHJGl
 G2yCxfBsa4KOF5COX3augYjVG8fjO2LIYBkEtCtSb21hbiBCb2dvcm9kc2tpeSA8
 cmJvZ29yb2Rza2l5QGFwYWNoZS5vcmc+iQE4BBMBAgAiBQJM+T+kAhsDBgsJCAcD
 AgYVCAIJCgsEFgIDAQIeAQIXgAAKCRDJbV/+CMIiahpBCADDMiQVoIId4eKs+zn3
 Et4u6x7uqXau07Oaa+Piyu80VY7+D8zZlccZb+fwJzIg/AyLnpjoJQWJbnbaktrM
 4o6Mz6inO0p8jdH5IaFOJezl1sZcQNWDs59zGoIHdgTd9/r2KmbKxLphXsxrAfZ5
 molQvKpbOTCit44i9Db5jrVbUwA+AEJm/YNDDB0e2kvQ44YDFRdG53erOIcJ513u
 gtWFj0FKVhYIQ7s+lZm5nELc0gEvI110hu0VOZDe5gFwZxqQikNjzj+7dmg9Un16
 WYufSXxNV4ZrUKZfstGUBJh8WM0HJXZmdo45VCMcK9JanuFsM8r4KiI2YtsLrlnI
 jftbtDFSb21hbiBCb2dvcm9kc2tpeSA8cmJvZ29yb2Rza2l5QGdyaWRkeW5hbWlj
 cy5jb20+iQE4BBMBAgAiBQJM+T/EAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIX
 gAAKCRDJbV/+CMIialYSB/9nudV91Z1EpEZDCHNnndusvZznvd1OK5bKm0bBEUnj
 coYk5LgCJ7pxJF0vhGFA1Nwd/b8lH7e1E/G/WvAQT80oEnFwVPs1IVD5LNBcsQUT
 YoMuasJt/4w1LCmCN03DuoN2erPHl6TawPr0Jd4hdP8yTwPMlG0MSZCHYA4iwqub
 c2aKOoG0WEwazocyfgidsiU2H8kY7UtY22Gw0baOO2ZfBx5GKb4gT3LIt4HDBZLW
 OeCtvkwgf7OIhN9vaPpxIlHC/eiCxPiqacyChHlc2GrrbVka+siKBx9kcTtIdKAB
 ObqhAGSmOmcWblfmIyfog9o5Ay+/yKebOBwhNnM5zRhuuQENBEz5PvIBCAC/11gz
 Xp0sE8pczDkJ14UmZRwlx1HsQemL+D+x5B2hBvBZpgjBUEKb3jp09za7LgVpkwck
 Rs57kKWbtXmVJFlevT5Efu2nh+PhjcA2yaZeekLrMke3/AaeXg4GATCc5wyW22c1
 v+Yyn8p5nblrmwX6Sdv3LegPGZjpVvx74lviVOEwqZ7AsO2OaN/Hnb5jjudLDQIp
 EMU82A+8tVMXrINe963ubG35S419TrijH92OiWHLk4QxtW6dGfZFtr/Rn5LibIa/
 x/mS9/uaps2fOMIT2E2joC654nyRTgHRpaOGJoJALH+nc8CaeWnN5vXpaGjMIgHz
 6OATngfCbRpyRTXDABEBAAGJAR8EGAECAAkFAkz5PvICGwwACgkQyW1f/gjCImr4
 Pwf+KIIYsfBv2ZL87HoUJWI6InAljXNduzh5Z1LBwqRFQILEdKbRTxHRCQFbuQXz
 XuoG9Sm+SQJuWEapSgfVc5AjCLwkS6fe5POYKZi+bJVg+WG9phyA3ahkomevQeN9
 RiMmoUHLyTT5pJcmkUemjKOR68L0sSQxZSa6E1jymn6eV8G4WQIrgxkbG0+n8jlL
 Gh45Z32XSPRcvLmP/R24m94y4hRcFf7+zi/8jsWsLhhQeKXLekTYkxl9KFnGTG1Q
 Awe4IQFbQ3JTtPucKIc5Nhc7psmvbLrRLIY47b+5Y9HaSepcm+7p4MNlsOE1Tj0G
 at3c73i8nATVo8CdE9D1rxmG3A==
 =Iduw
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.30. Renato Botelho <garga@FreeBSD.org>

 pub   4096R/9F625790 2012-11-28 [expires: 2017-11-27]
       Key fingerprint = E3DA 9B2A 6160 99CB 4B31  7641 F1F0 E7A1 9F62 5790
 uid                  Renato Botelho (FreeBSD) <garga@FreeBSD.org>
 uid                  Renato Botelho (Personal) <rbgarga@gmail.com>
 uid                  Renato Botelho (FreeBSD) <garga.bsd@gmail.com>
 sub   4096R/473CC82A 2012-11-28 [expires: 2017-11-27]

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Comment: GPGTools - http://gpgtools.org

[encoded data, 6794 characters]
 =jV+3
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.31. Alexander Botero-Lowry <alexbl@FreeBSD.org>

 pub   1024D/12A95A7B 2006-09-13
       Key fingerprint = D0C3 47F8 AE87 C829 0613  3586 24DF F52B 12A9 5A7B
 uid                  Alexander Botero-Lowry <alexbl@FreeBSD.org>
 sub   2048g/CA287923 2006-09-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEUHm3YRBAC/bBl9E1saFAVuS5wtnBQ7BbXPOr21SBExZ3t+f8k2PG2SsKYL
 xNMAn1drC9UdbUVcQDzlGcWQONYRKj4kWoYSYNDOElwa7Rv/f4z4NnIhOxxT6G+M
 qQTFWj6MjrCVPZh+b5Y3DTdmNxuJq+Yf9+DFsxc0i+xhMrbbjuokWRFdxwCgvb8Y
 fLNYJqjf9V5hhnvt3K2/L9sD/2frMKR7o1Ie3CgQbhZgYLkGlMmAlyrKLamdRzRl
 AmjJ35mkIQ9iu36BpsUmVL9WPjy2sdep0FyRLRgu5/q9qhJxy31GsVYv5y9m9+px
 X+00CN1a/5g1d6gxLUY30KsOL8OXSqwmq36iJHEsRxFfs9NJ/dBui1cFW0dDNmdg
 nE9xA/0aX+9BPSiu/hXFa5A2Q8fCB1wOcaru+QzgbY7nWnse2PQ7Nsv0xEMkaYdT
 AqA9I/UyssYeRygD7H8edd24xy39EBAVLLCD57Tjye2fCOyWBIGJU7Jtc4b/DJgm
 6bP2bSscB44ybBmlWdza2sgui9D4beWQvEVZGgpsnqnCjJQDOLQrQWxleGFuZGVy
 IEJvdGVyby1Mb3dyeSA8YWxleGJsQEZyZWVCU0Qub3JnPohgBBMRAgAgBQJFB5t2
 AhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQJN/1KxKpWntZ4wCfWY5pLq6V
 rCpsAiGcIniMBUoueTYAn0b5suADC5pawqBP/Xbv95e69gDWuQINBEUHm5sQCADC
 7ynjQmBXd8q2Ei9ab6oO6Q4XbEu2eMLcm1C4b1cu8Riyb0bYI8fQ0JkYPWBDdgvG
 iVuDGHjLRCJm8LDV4VAhpkn6obPaDW2ZVf3urkAsCszSmv0jlEO+grOj48c7sLeR
 NpZX76FCKFtgHClQOSfR/9eoKFQh5jveWgSQ0gEW95gGQShy1cTi1XUdJdxilL6G
 GNBfSNgAFwQBkepgzjR853bVysoZEF0Z9MF/PZgmAXoPYTs54tA24LSETmBo5BjA
 yUTI6Dv4+jKXqmDphX6BjxeJkYxlKAyVBgNrKZahPoyOPd0FvMINn4MpOJdpq3sv
 PSXwbexIrroMJQz7nR9vAAQLB/95AIR3oGIOhDCAUwf18K0Uv+v2cKVhClHqyAGy
 zHjyoyEoSnhApWVXD2hNvqfxy37t5/5EzaU0mvC0GMpv0trBa9uBRk8GrXgILnzh
 dYjhbSPZStx3D/0lFBLHt9qYjFFQweKNun9coOV0TzdXigH5PFxiks90Qc/sfr6N
 v6hXA4MAe81zeEdQafBkreHDo9fL4i+GwxF9novXNZ0C+YNJ6+3wOIJwacCZ1bdy
 gWTM8pTa7vtvtA0Pk4CZpGKSICg/jDq9dZT+vaNGFnKvQOQv1RPNLs/QqfvUo4ZF
 khopn5yHXGJjLZp0Zds4MdqXLddUNHXW20Yki11eZ9NXK1KdiEkEGBECAAkFAkUH
 m5sCGwwACgkQJN/1KxKpWnuSYgCeOgBV4svD8sqNBVN467Le6aLzPxIAoKsNXerk
 njcpzY8FzVuY52JnLNP4
 =CUqZ
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.32. Sofian Brabez <sbz@FreeBSD.org>

 pub   1024D/2487E57E 2011-03-15 [expires: 2016-03-14]
       Key fingerprint = 05BA DC7E F628 DE3F B241  BFBB 7363 51F4 2487 E57E
 uid                  Sofian Brabez <sbrabez@gmail.com>
 uid                  Sofian Brabez <sbz@FreeBSD.org>
 uid                  Sofian Brabez <sbz@6dev.net>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBE1/aRgRBAC9Nx9U/fn59g14PQ11t3prLTwrfzVYbEtPHWCNs0YDcB6G5M8f
 8OpsPxousOkEy7xMYd8Xfzps9OSppH6Jwd/+GEiwaAT5G4tJ3X17aak/9fUUsir0
 g+NohLUcflYszZlzLG01a8VH3AkDZgwkS/93IuQxPTmSX1ao56oHQvJ0rwCg2T3s
 +GgcLz5A+NJZ5jY4lv+R/OkD/2BPrDN6+B+e1znlnl8Nk0N0fmLjvYjgkJSA37E/
 zAUh7mtpQroSo5vdy0/ODbbLL/JmcS52I9LOC/aakykSd7aS1Lw5vDvhG+bLWB/H
 eYWC35PtI08XnFDaKaycu0TnayrggEOpNJnMfOSviGMsvbnksas03RCFeAd63APg
 kXafBAC4x7c6iEsUmpVTn60mOTf4OVGGA8CN00HpyXfDgb2exuLfwAn34qNaNcd+
 yVU1Hu3WPgQzQbTorqwi7zmjn80gmpYJjAW67zeeY9QLnuNdD93uJOIscjYltrl9
 Ft5+lefMyTCb04Uc8lLAvoiZ+T7G/uyyRZnJ/5vzgr7xIeCPQLQhU29maWFuIEJy
 YWJleiA8c2JyYWJlekBnbWFpbC5jb20+iGsEExECACsCGwMGCwkIBwMCBhUIAgkK
 CwQWAgMBAh4BAheAAhkBBQJPcussBQkJZyyUAAoJEHNjUfQkh+V+oTEAniEEpQyD
 8sYsmOPJA9Kj3rlGdHoqAJ40pp9l42h+6HsOfzWmNXEOfA0g4bQfU29maWFuIEJy
 YWJleiA8c2J6QEZyZWVCU0Qub3JnPohoBBMRAgAoAhsDBgsJCAcDAgYVCAIJCgsE
 FgIDAQIeAQIXgAUCT3LrLwUJCWcslAAKCRBzY1H0JIflfkaDAJ9HOCFfC7uBDucx
 DraxT8X+3GNcbwCg1tl7zbIuEJj+7x6TkNNqR/6la/G0HFNvZmlhbiBCcmFiZXog
 PHNiekA2ZGV2Lm5ldD6IaAQTEQIAKAIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgEC
 F4AFAk9y6y8FCQlnLJQACgkQc2NR9CSH5X6FTACgkK8Gxmb4hqgmk/lvrHqylgei
 tbEAniRE2s/taMog7hd/8sgTn5w4yYyluQENBE1/aRgQBACNIAMTtiB/KjSfsFIb
 n2vc4284SvwPNhdO0RWj0n7shgf6Y7F13nY/CbOFUPz1AI1SgJdRxGJOcfwVS3Dh
 3YisqgGpnY5bdc5TDo2XzqWF+JgkePKTfvTnP3P2sYzGC+oMlAQkzZaQl8rBRvXe
 vpxNZIW6EpGEsBYBnxd2Cl97mwADBgP+PcBxmCc4bosldea851AiCkHyMBR0f/0I
 ldbawynpYFOwZVytmrWvuWcp86lnsPEkmBuOjBbK5WgNJzIO2XdmtaNuN4Ll9dHr
 AEcLFDMSerNkPAvkzMzNsu6L5ZVrBtXQr6omN8DLcau+6uRXq3wZrQZ2o97/pByP
 nmxopGDMt16ITwQYEQIADwUCTX9pGAIbDAUJAeEzgAAKCRBzY1H0JIflfhBRAKCu
 puEkAZ1svXS/c8Ei8FS70bQIlgCg188vwbrylTHwyH6aIlwU2lIqVXA=
 =4ffD
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.33. Edson Brandi <ebrandi@FreeBSD.org>

 pub   3072R/FFD3035B 2012-11-26 [expires: 2017-11-25]
       Key fingerprint = 443B 5363 564F 06C3 EA54  9482 209E 9B54 FFD3 035B
 uid                  Edson Brandi <ebrandi@FreeBSD.org>
 uid                  Edson Brandi <ebrandi@fugspbr.org>
 uid                  Edson Brandi <ebrandi@ebrandi.eti.br>
 uid                  Edson Brandi <edson.brandi@gmail.com>
 uid                  Edson Brandi <ebrandi@primeirospassos.org>
 uid                  Edson Brandi <ebrandi@gmail.com>
 uid                  Edson Brandi <ebrandi@fug.com.br>
 uid                  Edson Brandi <contato@edsonbrandi.com>
 uid                  Edson Brandi (Born 1977-08-14 in S. S. DA GRAMA, SP - Brazil)
 sub   3072R/A34B8175 2012-11-26 [expires: 2013-11-26]
 sub   3072R/4EB0E0EA 2012-11-26 [expires: 2013-11-26]
 sub   3072R/89917E73 2012-11-26 [expires: 2013-11-26]

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Comment: GPGTools - http://gpgtools.org

[encoded data, 14124 characters]
 JohSO6LvfbnE3gWmaNyKWNJvAOEbvt/CND595QivXyIHSVE=
 =aO2j
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.34. Hartmut Brandt <harti@FreeBSD.org>

 pub  1024D/5920099F 2003-01-29 Hartmut Brandt <brandt@fokus.fraunhofer.de>
      Key fingerprint = F60D 09A0 76B7 31EE 794B  BB91 082F 291D 5920 099F
 uid                            Hartmut Brandt <harti@freebsd.org>
 sub  1024g/21D30205 2003-01-29

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.1 (FreeBSD)

 mQGiBD43wzYRBACpuUuayKjLpf+tMndpkOwxmpaPkLFxiA/dI1iWjY8I9ItDLZyM
 LqgYXemOOga6vbTvIUq7Bjzl3oR72kjNX3J1EljsMj7dxksoY5lflEMdxAyzdVoI
 +/cu+cWiP0Z9unKpYmTk8S13sUTtZc0+ixioaUvHzSJ0nxQMpIW7dqCDewCgmSVR
 6i2aK4oImAa9+ZbCxg7fCxcD/2xgAAwJSmaiaV/0As3A6IO0eSkbkzFSkMF+ms7C
 OtrHr1zmdM7h8MaGg/jw0Z6eZalYD7AclLvXDW0rxCMFwh06SC2axUTk+aE+vcys
 fuSk/HJtnktHUxZDgb28jf4X6zfcdTKE5dt5a9w3XHHPgdTXjGn7+sQNR4CWDcvq
 1qNQBACOqNxJdCC9tDLycRoupNSwzldMKVBZ2/JdQjfCIq6d8HPMNVLU8PGlDjoy
 RN4QkMZLbwV9Gaigk2DR6vvi8meARADt53x4OjS4W3O/Pc/Aj8rsUcF2mRU/wiJC
 8VkQsnaci5GuaYAssgKroOTZQzxHkOjbk4FeQ70C+wxovRsTh7QrSGFydG11dCBC
 cmFuZHQgPGJyYW5kdEBmb2t1cy5mcmF1bmhvZmVyLmRlPohfBBMRAgAfAhsDBAsH
 AwIDFQIDAxYCAQIeAQIXgAIZAQUCPjlTfwAKCRAILykdWSAJnxpyAJ9eHCdgiEt/
 +Z5Ms8Qe3ekWTYTy1gCfdVWLF2MrZNL/MYOgBhhex70gKzu0IkhhcnRtdXQgQnJh
 bmR0IDxoYXJ0aUBmcmVlYnNkLm9yZz6IXAQTEQIAHAUCPjlT2QIbAwQLBwMCAxUC
 AwMWAgECHgECF4AACgkQCC8pHVkgCZ+BBQCeMpgFMMm4siEtrzqdisrRaxJJvosA
 nA7UDwOVoHDZaAkFD0HNcUsTkO3KuQENBD43wzcQBADsEH8o/9tD01ScNfhoMbK4
 N7GsIJNFwQf0+MQuplpXQx4eBpI9ST1ZoAUXeM1j4jk5PIAMJzt8w6BAGgcU4iUG
 Un0R/QMTTXVkfovdSe9FW7/QtUjRtTQz3QOfZTkekYauFIiW+lSmH3BDwRXhpKgM
 e19eQZYOPRfLCnLLwqdr9wADBQQA5tIdzlDS80CNZxxoFDKlvOghtrIzPG/wIwGV
 at2clZMLhXESxDxDkpwT7XP1GRLyN/Plh/4k2vwxni7nOJ8BIch7rRh3E48TJat1
 iZ99SFc9iibED5hY/HrKlc/kphFnUuEr/kk82UCv9p4/d2V1+8v1N+Cy2jCGvrip
 IQ6v2fOIRgQYEQIABgUCPjfDNwAKCRAILykdWSAJn0J4AJwMsjovUA6jCJRMEzOS
 kIakJgqJvgCeNLKyNEkyJZh0wZUcEg1zYLRYp/w=
 =+h/9
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.35. Oliver Braun <obraun@FreeBSD.org>

 pub  1024D/EF25B1BA 2001-05-06 Oliver Braun <obraun@unsane.org>
      Key fingerprint = 6A3B 042A 732E 17E4 B6E7  3EAF C0B1 6B7D EF25 B1BA
 uid                            Oliver Braun <obraun@obraun.net>
 uid                            Oliver Braun <obraun@freebsd.org>
 uid                            Oliver Braun <obraun@haskell.org>
 sub  1024g/09D28582 2001-05-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBDr1p9kRBADrTCmhk/+XY9Jc34z36wp8zy1rbxGBy80enJM+aFPHks/iYPxR
 WA1tB8BEdGPJliUMYcNGeo+ZX3As1+xxo7NJCc7Zd7Gfs1+fMOXPwKGt02mr+Nje
 +nF9XMfdGPP0IcK9lzkVeEdH2JP41pS2SmrMwsTE/eGv9pFEnnmRxeuFcwCg1RYc
 f8freOk8v68+J99mCUUAGl8EANePcxWbRYgH5KulTzE5nYIt9WBn247T7goE3yn1
 R2VddSXXGhs0byRxXpNAcrysyGshIQY0nnZSB5AUt27tZJucoT1p/BtBFQ6hLCQe
 kaIRL0sdXrVJZn3/Q1G7vJWD6wwS35dro5PsYYPDI+qL1tISlWHZNQ2Y6jGdqhc4
 Len0A/4nV78yB7cLvHksxwvbdtVVn8eVo1B2U+/b4cXhevHAl8AmNN+usmEodxxe
 8FYWV8jY323xiYSMrCpYT9FuD3r2qORMOGWpg0zth6BkhdgH1z2i7koKkGIfc4mV
 6oea3ep5uaU82r1sGe7/cVzMGUwzZq9xizwODfbmSW6E+vdAjLQgT2xpdmVyIEJy
 YXVuIDxvYnJhdW5AdW5zYW5lLm9yZz6IXwQTEQIAHwIbAwQLBwMCAxUCAwMWAgEC
 HgECF4ACGQEFAj4YDoEACgkQwLFrfe8lsbr7rgCg1K0Zl8CPgrQG7BEaZqzSiIM6
 IZAAnjz5ifN2xHJSOJiLYloidZsikNFQtCBPbGl2ZXIgQnJhdW4gPG9icmF1bkBv
 YnJhdW4ubmV0PohcBBMRAgAcBQI9Y1sqAhsDBAsHAwIDFQIDAxYCAQIeAQIXgAAK
 CRDAsWt97yWxuv0CAJ9lUDzKKdaCp/8mJjlXLjlSZaaJTgCfXIqQr58p5MSFkVdL
 hLbK1P1l8FK0IU9saXZlciBCcmF1biA8b2JyYXVuQGZyZWVic2Qub3JnPohcBBMR
 AgAcBQI9Y1tFAhsDBAsHAwIDFQIDAxYCAQIeAQIXgAAKCRDAsWt97yWxukHLAJ9u
 oP9cIdBXldt7XfQ/5xK2fUsHPgCdFIR7cK0l0spO2xjzbzhoPPVShbq0IU9saXZl
 ciBCcmF1biA8b2JyYXVuQGhhc2tlbGwub3JnPoheBBMRAgAeBQJAViQBAhsDBgsJ
 CAcDAgMVAgMDFgIBAh4BAheAAAoJEMCxa33vJbG6MhIAoJ3dqHVStQdGzLPTGbtP
 Zq8wG0jmAKCzMo+si/LFBZAnOqYN3g2yVOOc6rkBDQQ69afaEAQAlaNzX3ql+XfL
 obAAIWW/TdY9Yh6r0fFFoK2Mdt6vungWhzSWb63DprREXyW1k6QbPQxL+pAfeCYZ
 oXQuNBmsUpO1Xn6ViEGRd53D07sNJfBrE/5w3hwL+c9lWSJlt0vHKzFtPAmqenBd
 fA0fs9afiew2sHhk/jz/FAwWcnF4aC8AAwUD/0upFaHEZsf8sVmSEew5tAtZ6i3x
 zaBjhaDv3sYobza57S8mXYhscK+nNHx3bP036wJ0z8ypqb5oCqGzWUkj9OpYZs0u
 Tbpla/MoCI9N1Ch8LfQkWPuvYjHF6LSY3wpZKaNWfeZPCmMT5XPqjuxDB1pCmnAU
 OizLyimZU2Y8tfQWiEYEGBECAAYFAjr1p9oACgkQwLFrfe8lsbqmfgCffgEhvau1
 1EUoZmkdnzUg2rbKYnQAn1fVK9TjWnJWQ/YDOn9hmMZWYjib
 =wrrS
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.36. Max Brazhnikov <makc@FreeBSD.org>

 pub   1024D/ACB3CD12 2008-08-18
       Key fingerprint = 4BAA 200E 720A 0BD1 7BB0  9DFD FBD9 08C2 ACB3 CD12
 uid                  Max Brazhnikov <makc@FreeBSD.org>
 uid                  Max Brazhnikov <makc@issp.ac.ru>
 sub   1024g/5FAA4088 2008-08-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEipViERBACsCTYd7As236qQw4dG/xB8p3XbN7pFP/C4yjRJak2QZfsOQ4mR
 7liBgXc0FevU6FQOW4XrcRbQeGFlRE5pb3idwhTKNc58TEifGM2s2ZGgRrR0aIF+
 9s5ZbVNp75FgSsN+9ksAOmz1nSj+M9Ikz464YvA3bHvKP8QQCpPpBgiuSwCg5IBV
 XSvep/e502PHqsiP8H1zGjMD/0xDwDdLfnN1R5tuNDfZEN09BSRlYYFPmMlP177i
 DBCF/2gF1bQ7KL42qBCr49ngVMAEAUlmZwBIN0XvfGe0KWDvc4G/CYqcOiWhbBEA
 pvtJZHE1C/kIRFS/IiM7BVmkdVnn1MzJrGSVPAF85e/iyc1K05C/qCuulqm1aLpf
 8dOeBACDvyvk2uE7R11REnKa6FKvzS2X32YclSM2sApwl+LnFO9eT500Rxzy9ldP
 jKlKR/dO0DwUKxnUO6DOHAEZzvutx1f6ZJksXk/0OsSNkn7+TIt3pKb10udpcCag
 k/ik+o7v+2XB7BlydRBPwcaJE4fq+CWyAbgRfKROetwfTI3ItrQgTWF4IEJyYXpo
 bmlrb3YgPG1ha2NAaXNzcC5hYy5ydT6IYAQTEQIAIAUCSKlWIQIbIwYLCQgHAwIE
 FQIIAwQWAgMBAh4BAheAAAoJEPvZCMKss80S1+cAn0+WKUu5TxrXSF4N8WlRK0mU
 1tcdAJ9Fcv54PisOdQiVUSIw25LqSqWyJbQhTWF4IEJyYXpobmlrb3YgPG1ha2NA
 RnJlZUJTRC5vcmc+iGAEExECACAFAkiyz/wCGyMGCwkIBwMCBBUCCAMEFgIDAQIe
 AQIXgAAKCRD72QjCrLPNEjtdAJ4tcsvvos2CoXmZsTJxuVF0RaEwigCdHgBapPWu
 MPyv9FLRzdWelOfZ3m+5AQ0ESKlWIRAEAOzibN5tPXiGKAHPwaQgnVQiaKv/7HUr
 FVfqycyXJC0/nmJ59UNpJ+0Y4GDwDRYqWqGyyd9diKAUomUwbIuQ71BUibmIZQS0
 3v0jgcfnJAhgz7EFGewgQLHsYwzwTDtPNQCqxDEUwDLKla72ksuodqzx92Dj6SSP
 AfFN/6B2bvQbAAMGA/9XFhkt0SAqXV09CXs3QuHdzuJ0PLadaz31bWITmSLqW2FU
 /EwXt1615g/E/qIwa1PzjZT8JQDAEHKbT5XPXtTzvOAUp8JK2wW9P6JQ6YPT14Vy
 /9PiMvLThxNY3zWjWChWuEf8zohd922OSqlSE8vgOm0H7XUe480/FeP3RP1EKohJ
 BBgRAgAJBQJIqVYhAhsMAAoJEPvZCMKss80StqIAoKpjMeYK0fSi6GpfIaojuz59
 eHHiAJ9ws2o67xPKbWgdqMxn4MfLK+ojbg==
 =m+ns
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.37. Jonathan M. Bresler <jmb@FreeBSD.org>

 pub  1024R/97E638DD 1996-06-05 Jonathan M. Bresler <jmb@Bresler.org>
      Key fingerprint = 31 57 41 56 06 C1 40 13  C5 1C E3 E5 DC 62 0E FB
 uid                            Jonathan M. Bresler <jmb@FreeBSD.ORG>
 uid                            Jonathan M. Bresler
 uid                            Jonathan M. Bresler <Jonathan.Bresler@USi.net>
 uid                            Jonathan M. Bresler <jmb@Frb.GOV>

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 6600 characters]
 pX25BMHqkEMHAxahVagzguPetlTIHxHGRSH3lg==
 =ttzj
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.38. Antoine Brodin <antoine@FreeBSD.org>

 pub   1024D/50CC2671 2008-02-03
       Key fingerprint = F3F7 72F0 9C4C 9E56 4BE9  44EA 1B80 31F3 50CC 2671
 uid                  Antoine Brodin <antoine@FreeBSD.org>
 sub   2048g/6F4AFBE5 2008-02-03

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEelsqARBAC37tcs27BitWt9YeIYmpRNgtRH/ndAm8ecJK+7IuEqo1t9IglY
 Uy+lI1xW1H4LrIbmSKmwfg3Gj3lm+12avQ8mf0vVbl2RVxfOQZY2C127Qv6Mg/Ox
 Fwxb7UCWzYi+XAf5XVHyzKLaLq/S56serWDX+mGY83kLhVKXy7pL98bwewCgtr1D
 miY3vAu1NMoWPuZ/2kvLLh8D/i1Zisp0EE5B4QjRFbaSUzfk3tImTKLQtbj4F3S2
 Zo4hh3IRYLGq2OMJ+gH5c5KXMhaxqiK8XCO1pHNdCyaL1PZDW9s0sxPiVv5DDxHU
 Lm1BXyTIJyuAC8KVnMWIfHVoqIX45m0Br6IFyiHU3CFBSsarkC8088HViilTYGd1
 8InNA/4+wVDMqnht2/YeMqyYevKOGw69Dqe+1jeTNOg7h/1EOL2Sytg9EIfyTf71
 IxJAhsKU1ibjAMubERoTN16rPgTx4yrDtRSdfbmnHxrreih6PKsbiaKy76cnYaxz
 sz4VontIIaH+Ye+VmVIQsBS/QIBBki0j9YAzNDcJqCdWKcoeb7QkQW50b2luZSBC
 cm9kaW4gPGFudG9pbmVARnJlZUJTRC5vcmc+iGAEExECACAFAkelsqACGwMGCwkI
 BwMCBBUCCAMEFgIDAQIeAQIXgAAKCRAbgDHzUMwmcdHwAKCrHa3q1ixEdvmpU1Ny
 2SpQrmvslgCfef8t/hiaMLSuyZEsjR1x8cp6hiK5Ag0ER6WyoBAIAJScQspDgp5D
 P/K1ZdT86Ux7Nv2UhZilYF0LPkvZBdfTC80RpjrUvz1m8ZObbCsUO5Ag0j3+Wtms
 6CVaQqfT2RoRyjcnNVJGadWqKmOWVkvZYzHQPl8SZNENYurFFhfy4MCxXf5drkH3
 CV5QqY1onhuvsfl69UZ54e6X3+DjQ3KdtqyyqUez7Qe20ZdIcgC43HcEuqAbAOxm
 /K0zDNvHpjwgleNoFBd8GZfD/biD9EMnhiCBq5rS8Jqh73e9wLtkMfssQunA7ELx
 ZVuC7M5dBBMjRUp0dswAKAgdcaLA0D1NGUNSno35Rzur7sluufivfjLwn+qRLRBM
 FPR+ggIO/Y8AAwUIAIBR74TtznV04mci4vHDds4HX0RI/hxawivtanEAGZvV54hS
 XUnVqpIVgTqKCtmS3gqoQMQBf1+25Rq7UJlVNl4/AoLcl9ZfR140hTSd888OwcB2
 MAHd9CgUXjTHcFQj8tXFhPiWY7SfFwheLDFJUgCqB/ilgPf1XGOYuZfvBxkyXd8p
 TC2sx4iFSUBbY4S6UZN8uokpRZDbTHUPgLHAoOg1lzrzUvZuknEzbcBDgQoVwLWD
 9UCZxl1wxly6oZkq+uggXg7zxWuE5CMdWtz9/FA3CRtRBTqZnHrMM9hlHGgxTYan
 bBTs793WWsKf8rhTRqNDqQdN07YxsmTi3129OSeISQQYEQIACQUCR6WyoAIbDAAK
 CRAbgDHzUMwmcYHKAJ0c3chle4XcJ5c7+0odRWmOZ8m0IwCgndOwp3kjZUZFbAu0
 AxHti2KSFZc=
 =HznU
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.39. Diane Bruce <db@FreeBSD.org>

 pub   2048R/8E9CAA7B 2012-05-16
       Key fingerprint = 8B08 E022 705D 0083 64C4  5E60 5148 0C74 8E9C AA7B
 uid                  Diane Bruce <db@db.net>
 uid                  Diane Bruce <db@FreeBSD.org>
 sub   2048R/932E5985 2012-05-16

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE+0LDEBCAC5tZOH1o7XBusdsINQKzGPksqrS+JJXMbbVkHML1dgrrYK69/p
 psKdwQ3uLkKTVutB25M7BkSaK/UqOuCtTOu14jOa4PUeTnkFyGMC79MxIexa44e1
 vyAY7/UnEZghtakIvdY5o8VipFJvD2OY84JfoIgAlwRTNmc+dyMfFaZr5xKb0s72
 AiMdx+p5okBVG/tpA08LZ9pwENv7ov0L3Mo6VSwaZVsq8O6sU9L3MW24EKUsffXG
 Um9gyfHS7xsX16ebsIWhzNq6BdSNondm011q/ndVQzCkSFtPDwmuaiO2wkMasIQ5
 Ff2GczH8ybjmAWB9ZSruoa3G6T3B95QEu1o/ABEBAAG0HERpYW5lIEJydWNlIDxk
 YkBGcmVlQlNELm9yZz6JATgEEwECACIFAk+0LDECGwMGCwkIBwMCBhUIAgkKCwQW
 AgMBAh4BAheAAAoJEFFIDHSOnKp74hQH/iwyMhVYcfNViyIllr8J3U0nJjWo5zIR
 sfONs9QdK9THF2XPzkz6wUmNQZzRHG1g5EbLwPHtP/cAUMebDHajHpp+TayXJIXZ
 7UJd4eSSI1sLVG/cj567C3UwSSBnt2OTNX/aZqqnQ37Q4jkPbpPb3nfjBlOMX++9
 ynU+8TlJdxddLtQZfbrA/71s49LIOT6XnK0hyXwss0F3YowjTfnV4D3VsZJb+JZO
 jNvz/WCzgeIJ2C7l9wYEqnKOfRYGqNxyh/cs/hH1c/hWvPN9e/0ACfMRuxV2+PMI
 kZv0X+shADk/61f+bNIE6w6ZKX7Vf4FoC4UkJVBdJ303DKPionfqT860F0RpYW5l
 IEJydWNlIDxkYkBkYi5uZXQ+iQE4BBMBAgAiBQJPwh4JAhsDBgsJCAcDAgYVCAIJ
 CgsEFgIDAQIeAQIXgAAKCRBRSAx0jpyqe76zB/45T78DroUrVyM90bCIiJjlYubr
 zkdLA9+8ZDstfw6Ism53hHhT90drNW77lb2SV+VpJYLXbyLGwg4/cNF6+Gv8dK3r
 joJziiJosWdxQIfXt8JoyI3Z3BAxC8lf6wv5UvX4UFTA/AklLsXkm+IaxeKsGu5G
 4JrwZOVgsMQIx/e/o4hWhbF6a8j3O7dHgHmA2XD6CVDYyclEHj48iJWGgib4pkJJ
 hhPGe1kgbasMcWbJw2B6A+08WC0Ju6R+GlPba4sllxQUVoKOiA1xXC6KIo0DiOld
 qhOdBMUi4NC0kIldm8d/Da0xzH+vqCUgrbBEBWjbASAHGNqY+u4cV7vCGyW7uQEN
 BE+0LDEBCAC9h0wHaL9XcT1nss9D1XYGAOywW2nhVJuX3GNPwtys4Al5XX4w0qD7
 KQs8LRlXqE313xFi/x8/DeVHoN15xAUxFrDrW74zK8pP7UpyN3f6LTf7axFGEMSt
 fQ+ZQ3kt1vwDdb4CY0a/uhPejkwRu94ngWotnHriecHZmVzsqy/I+xXvk2OnkM4L
 39JwIxGYmB5WO93xvCc50bpY1sEK0kxnO6uwi60+BgC5GLf7vqJY72wtz/JmI2wq
 q+0XAx9PyOv/ZefFZpWRiMzkfcsxUWYzI6DbyfLKrOVzjw6zJ3/eMsk4HUHiqkBF
 xq4GqHoIiEic0rQhiXLueiuLanpStosTABEBAAGJAR8EGAECAAkFAk+0LDECGwwA
 CgkQUUgMdI6cqnsSlgf/VyweVvSVjN3v7XfSxQJFIR7nlGNRmhbGeshm8pG2hpTl
 GzyMM6lqbo7DBb9ZC5VFEMr2IjIfxrSfdzgeB0RCjzuwemcjcaCX5yFq1Gv/91oW
 C43qI0kc/moII+wGmS/r3YNX28gC7heYcwlgruGJB8imhJG5UUHP0dkSJdA5sa9V
 ZnURsCOgj4ZuBRadm+SG25/L6PJ661bk7+3uOHk3yU+qJbwHx2z4+b/nlG1i+Z+q
 ZdriSl+zvil1fCPxKXQRiI1iRUOtL6hMLlF3UsCQM/UlMd2z3WBOOl1fyov9F9mT
 lPDochXXSanmCk14kS8h7hQLldWnrsaqFrBHAg1BCw==
 =cCnT
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.40. Christian Bru:ffer <brueffer@FreeBSD.org>

 pub  1024D/A0ED982D 2002-10-14 Christian Brueffer <chris@unixpages.org>
      Key fingerprint = A5C8 2099 19FF AACA F41B  B29B 6C76 178C A0ED 982D
 uid                            Christian Brueffer <brueffer@hitnet.rwth-aachen.de>
 uid                            Christian Brueffer <brueffer@FreeBSD.org>
 sub  4096g/1DCC100F 2002-10-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 76164 characters]
 otqKGK6X6iceCg==
 =yns3
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.41. Markus Bru:ffer <markus@FreeBSD.org>

 pub   1024D/78F8A8D4 2002-10-21
       Key fingerprint = 3F9B EBE8 F290 E5CC 1447  8760 D48D 1072 78F8 A8D4
 uid                  Markus Brueffer <markus@brueffer.de>
 uid                  Markus Brueffer <buff@hitnet.rwth-aachen.de>
 uid                  Markus Brueffer <mbrueffer@mi.rwth-aachen.de>
 uid                  Markus Brueffer <markus@FreeBSD.org>
 sub   4096g/B7E5C7B6 2002-10-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD20hPARBADzumxDOkMdttpWKphTxFC/j0+MJRW5UmFjd43c301LEMFSJMkv
 06EukQSOVWGyGL70v/4NWx25BiLhLDIb4feE5SZccQTnjxXYCjkQ4LfcolqTAzga
 L3GLNF356vKLQPlv6J5ah3vdZHa8Djh8q0s6CHAPi2rhEVbO2x7IcRW6MwCg/0+E
 KmRtdsifDJ00iBEMpJAApccD/As/bzVXI4FZwjwIMdep9+He7rwL/xGK+ZmRUEoN
 iiIxfd2oOkwDXZuFqTGftONd9Apao+FefTbcpEfv7sBVzHCJBn2bTr5mTjDwuA8v
 hGQ/7+QyKIFPmsL5KZYPkBcRA195UBSdwEPdERGH+aWvDTVJieyetAiD78WTd5ez
 T0V1BADwVnc1ABRMz6e8HK+78G/4vMHKPPEC7YbSmOo25FKR7XimUIlvGfj+CNO5
 w6QSDJaIRo9yOCPEacMe91NeZskPlEEXN/KIOlV11vTZ/pVDMETnzdarNo2B7J2K
 4HQzTYBzfFHdCrKP0tExSCy0iN2lWzSI57S9o8YxgnwrmuJPN7QtTWFya3VzIEJy
 dWVmZmVyIDxicnVlZmZlckBwaG9lbml4LXN5c3RlbXMuZGU+iEkEMBECAAkFAkTZ
 3xQCHSAACgkQ1I0Qcnj4qNRBCwCglhvWAuZ+9bWZ64EXP9wHLiQYT1sAoPGL96ae
 YBK0wnq1TWjE9GPTYFXAiFUEEBECABUICwkIBwMCAQoFGwMAAAAFAkTZzskACgkQ
 1I0Qcnj4qNTguQCdHFTLRplJE7g607rCVSxDCefYw8QAoIMaWQv0Iflm5aAR0F47
 3WrjQplWiEYEExECAAYFAj20imoACgkQbHYXjKDtmC1WawCfUZkir7Dy7wP3hiNA
 X8yo78CpuFYAoMJtyYVOf8fayYICxujAO3zU2pjViEwEEBECAAwFAj53axIFAwHi
 hQAACgkQT4OMtyagqBYphwCdFiRae7gCvrB/jFA8ceyXaEP44doAnj41sLHZFGWI
 ZUmQmNTiNfZXYoQQiEwEEBECAAwFAj53IYwFAwHihQAACgkQdROiNhMQLPXCqgCf
 SgcJhp/6tnpjypjXWH9t6uKHg+MAoMYnXWc7iXVFvi99BonJW15V63uptCxNYXJr
 dXMgQnJ1ZWZmZXIgPGJ1ZmZAaGl0bmV0LnJ3dGgtYWFjaGVuLmRlPohPBBARAgAP
 BQI9tIVmCAsJCAcDAgEKAAoJENSNEHJ4+KjUCJQAoMsgaMOze2p3Iaz0/fK/Xmeb
 654IAKCDmJpex0C61bzfczSdaxXPPyIbJIhGBBMRAgAGBQI9tIpzAAoJEGx2F4yg
 7Zgt0WUAn1WbgrMzw02LdGQQLBMzY5CYXKxTAJ9uvEu5kTB1jFhMa/rM7r04dipM
 cYhMBBARAgAMBQI+d2sSBQMB4oUAAAoJEE+DjLcmoKgWxiwAoPKtxw1TpXp/6KTr
 YZD67bOTJA8+AKDzxW0tIl7ij/nnNE9gob7cSeCfuohMBBARAgAMBQI+dyGMBQMB
 4oUAAAoJEHUTojYTECz1ZIwAoIW7tPHgp/AAUso8L1C62O2WF4l6AJ9jsLQ7cBnL
 81TJ74C3Zey4iU0PNLQtTWFya3VzIEJydWVmZmVyIDxtYnJ1ZWZmZXJAbWkucnd0
 aC1hYWNoZW4uZGU+iFwEExECABwFAj4kssACGwMECwcDAgMVAgMDFgIBAh4BAheA
 AAoJENSNEHJ4+KjUzWsAoMhZqjpybn0KgRf8Br3eExRIbpcfAKC+OlKaKZLRSgbz
 +6Pig+YQiPnOK4hGBBMRAgAGBQI+JLiDAAoJEGx2F4yg7Zgt9j4AoPUVdFwcegkz
 /rAuVD5T3psicMzIAKDgKHpuYGnx9WLeK0fcIS9uAMrVzLQkTWFya3VzIEJydWVm
 ZmVyIDxtYXJrdXNARnJlZUJTRC5vcmc+iF4EExECAB4FAkA33goCGwMGCwkIBwMC
 AxUCAwMWAgECHgECF4AACgkQ1I0Qcnj4qNSSjgCdHF9CzCm9j6uX5aCpJ5Cg2qG7
 ktMAoMhccEzyNtzKGskfzazD1oTJdTjNiEYEExECAAYFAkA34C4ACgkQbHYXjKDt
 mC1PfwCg5bAwdeUZ/YgXy9UF4qpEX6fH6BEAoIS2DnUx4qlcuuhBUp9RXnST2G2k
 tCRNYXJrdXMgQnJ1ZWZmZXIgPG1hcmt1c0BicnVlZmZlci5kZT6IYQQTEQIAIQIb
 AwYLCQgHAwIDFQIDAxYCAQIeAQIXgAUCRNnO0QIZAQAKCRDUjRByePio1PgQAKD0
 YBsRWZpJv+i8MS5yTzympEWFOwCg9nEzWeocm8GIKu/EWjoCX+G1LOiIRgQTEQIA
 BgUCQDfgMAAKCRBsdheMoO2YLRWlAJoCSpQjOyb69ZXMoDKx7naBi5aNAQCg+Zl9
 IW0wDSUhTsHnwOf+Tf5sACG5BA0EPbSE8BAQAPkYoH5aBmF6Q5CV3AVsh4bsYezN
 RR8O2OCjecbJ3HoLrOQ/40aUtjBKU9d8AhZIgLUV5SmZqZ8HdNP/46HFliBOmGW4
 2A3uEF2rthccUdhQyiJXQym+lehWKzh4XAvb+ExN1eOqRsz7zhfoKp0UYeOEqU/R
 g4Soebbvj6dDRgjGzB13VyQ4SuLE8OiOE2eXTpITYfbb6yUOF/32mPfIfHmwch04
 dfv2wXPEgxEmK0Ngw+Po1gr9oSgmC66prrNlD6IAUwGgfNaroxIe+g8qzh90hE/K
 8xfzpEDp19J3tkItAjbBJstoXp18mAkKjX4t7eRdefXUkk+bGI78KqdLfDL2Qle3
 CH8IF3KiutapQvMF6PlTETlPtvFuuUs4INoBp1ajFOmPQFXz0AfGy0OplK33TGSG
 SfgMg71l6RfUodNQ+PVZX9x2Uk89PY3bzpnhV5JZzf24rnRPxfx2vIPFRzBhznzJ
 Zv8V+bv9kV7HAarTW56NoKVyOtQa8L9GAFgr5fSI/VhOSdvNILSd5JEHNmszbDgN
 RR0PfIizHHxbLY7288kjwEPwpVsYjY67VYy4XTjTNP18F1dDox0YbN4zISy1Kv88
 4bEpQBgRjXyEpwpy1obEAxnIByl6ypUM2Zafq9AKUJsCRtMIPWakXUGfnHy9iUsi
 GSa6q6Jew1XrPdYXAAICD/9aiTfaH5Vs6Ms4bUQIeOLvadkQy4eVVKIXehBRAJ0X
 SVed1BNBwyBPUtuphL2BvX7Vx69418nwd5heQMAaWjps91W/3tXq6IseBlVGQcZ/
 K3ICoafLYS8kp5i5ksX+2jvCF/H4KtDzODYBQOnC2TgVY3q/UncJDKjOS0Rfellh
 a/PI4wd8k0i2PKB3iqZ2kgetMD7ioU9hSQz2UHSsx3t88vj+QhuXLA/PsIBso8py
 X/6gxAUhGZKFMOJbqAowUXxQjyChVi9Rr08tM4PvDN2SD3XYhODrCLeNuGeKnoYG
 3HkX09xJglxLUHsTU6ZHx7EK+vkEdTd74RzzFf4wJnMPnT3TKNX1u5P+DOZ5bjBZ
 2O0ze3qLk9fBZxpiP2ev7GDMnQAeqb8Ox7lmGFUH1UARXhaicIhWTnfq3kJsCY4a
 DI7yHGu0Q1pg/R7V2ZGLgBTamItb6mUWGCBE5AF6AYVJQ1UU4We4FAfMmaiEb2ZE
 Gi60ff1jAR1PxAnEDHvb316Wv5GXRf3r6EZUQyuQSnWiIhgCs3EqbBUzbZvCVtHZ
 vLX7HZ10HzpHEdwNVpFAurUyP1DgRCCt1qKeDLui+t4N/WgP1EdQXpkmy+79Kcq4
 ny+HLaMgYuKSk+khJhA/l7xfMk3JNwlp1adMS8/FgScU/NS629UPsK0fJ1Mwlk5Z
 w4hMBBgRAgAMBQI9tITwBRsMAAAAAAoJENSNEHJ4+KjURHIAniigU3LNmmT0gemQ
 7wb7L8No/lEcAKCDziXLMavHZGnIuNydVv7D1XEllA==
 =rJ5H
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.42. Sean Bruno <sbruno@FreeBSD.org>

 pub   2048R/08E81687 2012-10-15
       Key fingerprint = B9F9 138F 349C D3B2 2AA4  1398 1909 45DC 08E8 1687
 uid                  Sean Bruno (clusteradm and developer key) <sbruno@freebsd.org>
 sub   2048R/BCC23981 2012-10-15

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFB8Jw0BCACYRC4xwboUcSZTAMO941WSdPDQoqefN9m6mbel9JwskGlCGnfO
 +H+AIZUW0eKzG8tywaXhcqoMrW6Ie9wOce7qF0+W3DnFsWk6XRf2guHAu5aqiD5h
 Q/0pMrgQZ+yiBsvqKZr5A0IDscm6v0Hu3brzyoLdKqLGHr1vSIZNv8d2irqjDtoZ
 6y3EdDJXpMpUsagHdTl55uWZkkwLRQY83KLwemjU4qF2lxozHmjhD3dKTs8+NhQe
 K+0vJDaPyjhARDrTl1HBwlbqqy5tmh8QeNkgltW3tnSzC3d9xqU1cDcnTkgGJtkH
 G99/5/4WG/wLcAORjm/t7igvq/2shWnmhzGNABEBAAG0PlNlYW4gQnJ1bm8gKGNs
 dXN0ZXJhZG0gYW5kIGRldmVsb3BlciBrZXkpIDxzYnJ1bm9AZnJlZWJzZC5vcmc+
 iQE4BBMBAgAiBQJQfCcNAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRAZ
 CUXcCOgWh2jwB/9WEMzPw/xIcn47xg3uyawWiY8XZWvhrUUNdACzLw9xpNhSIYf1
 rfbYdW9IW1wWVXyiGOunhLf7eylhdatQkjNPHH3rCATQVwfQbk/ONMP3OVy9hEhW
 SF1r1aWQZsdSEwvQNF4jlQ9un45YcgS8AqfnbRUgOhMfyaCk2f26sfZlsqcZnFto
 /aBx53hHT82+2KckvWBySOO58EKMVHV2MtuCQGUVikKKnNdWn617tyMhjcNd/UFL
 eZ9le0RQVGKjhCGP/o7TKDyHd68CVeUb4SKVQmIo5AnvNbGB7ZlmgsO5+xsq7PEg
 4mzP65ivXhqhvAYek8zWELWQUlqjBbDr9MP3uQENBFB8Jw0BCAD8kd0hCt9bhAAF
 fS0vY7mt5n/r0AlP2mQ4H+/fj3AxY1v/zF8qyzDA1JKzgUUQSAA10J8F/AJFtlXi
 c/T4kVEIBMxW6OLv2mhaEHXM4Sxgoro91xk9VXZptsCX6qcqlrTaAKAhs2QlfepO
 dxeG1LI0Jr6gunzV7+geVEY4apDPcVzkA+hZruM2BQ31MsSSOaJG4CxfY4OE1Hzw
 d+/pYrqzBoog2/2G2N7mcLuGtfjp5cN4K7/X14b2fqyn/HUvQA6VbuCW5zWgO5Yi
 viEv6alhU1StaF30qLr0zh25U6P0PIho5L9nefO1NXTiuuZAiJEmjlXD5MRvM9gO
 e+PWRdkbABEBAAGJAR8EGAECAAkFAlB8Jw0CGwwACgkQGQlF3AjoFof9rQf/UKgT
 03FSToSRn2VeIBost9JIuiYiOiTnT+7kyRxNkhAYS9vSWmicTXvHGxl7TzSyB4qN
 3TzltJOXvjiWeZ4kymt/1EiIIh3gz4QHjtB/2sJSTDTLacx13ZlM+Mk89sAnzMIe
 z11ENGFXFGcBQ4kTxJqenZwy1TZ2xQQoU30Yx9tHq/Nhlva+HUzL5y+MNsZefyN0
 BK4THdSDa1R1d5NikagUIknxt/ildP0GA2sUDLc91+dIbvqRMHXfteTRMGgu3EUy
 U+n4GrVj3+u3Ex1I3KJJplKYhKa5zQ5uNIbqL2ntOldwO9HiaI8Xxb16Xqv7kvlH
 IPDYZOY+KgLZ7L/TOg==
 =egdB
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.43. Oleg Bulyzhin <oleg@FreeBSD.org>

 pub   1024D/78CE105F 2004-02-06
       Key fingerprint = 98CC 3E66 26DE 50A8 DBC4  EB27 AF22 DCEF 78CE 105F
 uid                  Oleg Bulyzhin <oleg@FreeBSD.org>
 uid                  Oleg Bulyzhin <oleg@rinet.ru>
 sub   1024g/F747C159 2004-02-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEAjnDYRBACecNDd39vZ9wnodFlATK+xvhlyX4M3FBEV34t9eVZtJz4916yb
 nLZmHwY6awt+nm6FGciSPucfu7stBCqvPURWEThJgAyXbxEVNyXmXrZ2F5OyNMyM
 EcbuqLZTjYxxN5mxUYswtiNDmdWn+Ivmw46wTOl5Pu+B7W2KVl8mwwbAjwCgl9hA
 puTWWN0zFklDJIuLx9eVxnsEAI+QaACe8H2l3XFpNkp6n680ZlW7FBZDDOYjCS4z
 nhFg7Bca74t6vnn5Q4miLnDDyOPkZqMBD2nLUkcK/kMfe5uqDUWf/i6sFDwv7d6I
 9Ag4tUWLkhxAqaqomesfI2yS4o+QGTJgQdGU3IUrOnMJD7Ascwj7304lYuqYcaqT
 KQHSA/9eTg26Ihn9uBpGit+slgkmTHmKgAbg7IaSHSEYRbpmnc0Je794zeWns/oI
 vAyGNxEFpPQMVrSXHnFmK9AOcLcfssE24a3zw7So33asH2Ha9yYBrfKGrTCPZAsa
 uUGrKbGmXQ0oXDjjqV4anvC2QI5pEJvMbHJ+Xyq5xQN73ttJxrQdT2xlZyBCdWx5
 emhpbiA8b2xlZ0ByaW5ldC5ydT6IXgQTEQIAHgUCQCOcNgIbAwYLCQgHAwIDFQID
 AxYCAQIeAQIXgAAKCRCvItzveM4QXzXVAJ9RD4kKNcvV8UmuBM66osVfZ/7yIwCg
 htVf/ZfKdcob1zQsBNNpmzkpduKIRgQTEQIABgUCQCOgsQAKCRD9LjUgMMgeateB
 AKC0iX0NNspa5EnBYGE/eEe+LxRs6ACfUqA0s50e2goJznaIcLTgZXtDECGIRgQT
 EQIABgUCQDIZWwAKCRCF1FBFa2kbA7N9AKCbDyp3g6vRN7dQKBb35s7gLp8yIwCd
 EH/ivmrxZSaHlrOMJjt6rnmuFqa0IE9sZWcgQnVseXpoaW4gPG9sZWdARnJlZUJT
 RC5vcmc+iGAEExECACAFAkOMPS0CGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAK
 CRCvItzveM4QX+tfAKCLk3zeTyzbbN6TqYpnqocno4H9kACePQaaDytLX+zk4plw
 sywqPLv67SG5AQ0EQCOcNxAEAIUR6Uj/bLAu0/FSGDSCXfjuThVT1lh1rCLQkbBw
 TxNiwHPHHSQRa654aoYbQdi9x6M7fzE6Uzmdj1Gs/UBYZhhsrlkL+Ls/xuhe3Kh3
 E6lho11qPhjYXmFHk42VhtVlOcikZ/Azgqgycfql81H3bKWv6jA0el9SnX4yk5qf
 tgZTAAMFA/9T7/ty76bNeP3/LcY9ZL9KYWB8v8pJ9jEt/RfBXB0GTuV/H+bzTjSc
 PwhT8Fam9Fo+r02tUJfqA+XlOJf6IXPlLPRfvzHhiBJSBPuMvB6vYs5zrlUzkgNE
 VFHBr+TxpUWBq4ZtI9K8YUbPD+s86irYn9fHlnj9qnYsod3ySvU0xYhJBBgRAgAJ
 BQJAI5w3AhsMAAoJEK8i3O94zhBfFzAAnAg+W9rkVVdYu33hNqpX8E1t2kShAJwK
 V8DuSaXJtEgVE7Wp5CeArqtwUg==
 =/2pb
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.44. Michael Bushkov <bushman@FreeBSD.org>

 pub   1024D/F694C6E4 2007-03-11 [expires: 2008-03-10]
       Key fingerprint = 4278 4392 BF6B 2864 C48E  0FA9 7216 C73C F694 C6E4
 uid                  Michael Bushkov <bushman@rsu.ru>
 uid                  Michael Bushkov <bushman@freebsd.org>
 sub   2048g/5A783997 2007-03-11 [expires: 2008-03-10]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEXzleYRBADIqilbqBfzstvMByOY3QlvQD9QIGQLwZbziOMByQPwgzgBFk6x
 OA7NOfSKONPTsLtIOSc+CbuyEfw5jJiXsQ3Ox71Zp2JTra/bTim/WwJKC5Kc+egl
 CD6KO7GMTCBb102m2x97G+rNjGS8n7Uf7ITgoj9QtxBjpAC3K1ZcPoAcjwCgobcT
 q5MUrCqPHrnlZ87BnbT/3m0D/15hcV+qndPCShIqFTYbTSG18X7lBNTONZXmCm04
 5dRcJrz4qLvsCYkBrmOCrKbYViQCQWiT7/G3Jzc+WtGFirYibU1TxBprZuP99gX0
 Hea3gvgodlje7eq3Dz7Hx9uFgN8pfw2wWlEgdkuYk72s3lSJN6+TGWzXuWnRYYJ1
 H8XtBACpByr9qcCaJ9yNAwDbDZhj03zSeZoIQz6d/3tDv7SkzDlVyxErJCO7CiHg
 JlxN0+paX0gW06xkLmwSESerJVbxEIoejdkdxebqPEIQN+9Se6Q2tkefMWd93IwL
 MP8sXgUBE6PEmFZTwI1/Av+vR7aI1pPk+yIrKTV2KyC7yCULMrQlTWljaGFlbCBC
 dXNoa292IDxidXNobWFuQGZyZWVic2Qub3JnPohmBBMRAgAmBQJF85XmAhsDBQkB
 4TOABgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQchbHPPaUxuSKCQCdEAIOx9JT
 lAxIOwL6ApsukCI1bgcAnjkybnn6t4WWYy7IvmwMMJJ17oe0tCBNaWNoYWVsIEJ1
 c2hrb3YgPGJ1c2htYW5AcnN1LnJ1PohmBBMRAgAmBQJF85xpAhsDBQkB4TOABgsJ
 CAcDAgQVAggDBBYCAwECHgECF4AACgkQchbHPPaUxuS8xgCgjJ4lLhI3wDP8Rnhv
 Iy9UW5BuBEYAoI22XNE3OHvBdsmUyUvVji8yKt4auQINBEXzlgAQCADnAWwYquUZ
 mbrZ9/UO4abD7Nm0vipplm/O078SMdonir+HKWZStjuvIHhpPDGI0wCpg/v24B3w
 QVGiQhXWRL1cbvjDmiQG7GFdG6u4c1+2S6Evx+fp5DCjUMaoygd/KwF5tmxE5M2R
 7SOYueuuxcDiYi4qJs9lroNxnwG2/VkrcPxlek1QbRVjs+TuRnzTaUzXbU7kli6y
 PUhBucf6nB0cPHG6VVn8N0Kki+HBaQjYOxtBCO2B5E0uRq0Y25l9Vt9s/0TfYnYb
 E0/sLj0XSBu8WWmXtW7QrtLPN0Tb6XrTeIaWW7HLy1ACVlzniu5oeumVKiW5nsW4
 uJ/6kF5Fuu2PAAMFCADNuQ0Irmhub799B7h+FJVtNu1IxptmvJnD/RoWXhAtVo79
 c176MEqS/8tghzdq/zXhr4DPMiTDWf1p4ynKFFkpQaWkHO28cvu3rc0tdpkI2d+s
 zKT6fFNn3kqQ7Eq5xgijSK8+aTWoUhqFvxkhLIcColuPK2TmQ+uIxjtu62lU52eZ
 DDePyHFGVWqtkZ99k1vGxZRf+vVXaKTBkGY3Pek04knpP5ROGA+JjL/Ew5o4SWfn
 FeD9aJ+xtZ9VqTUyl+U4XwIYlRcWzbqsbGp0D0jgry5Xhiggngd7xtNSB9/44HuU
 C5EQWVi35HKNdXMq4wsOMG68DCTE3XOABa5yPY7TiE8EGBECAA8FAkXzlgACGwwF
 CQHhM4AACgkQchbHPPaUxuQTrQCcCfrtwSXFegD9D0DpYWa6iIy9glIAniDIOvRb
 4L8/nn1Nbu+PBNHamCHi
 =zD+p
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.45. Jayachandran C. <jchandra@FreeBSD.org>

 pub   1024D/3316E465 2010-05-19
       Key fingerprint = 320B DB08 4FE3 BCFD 60AF  E4DB F486 015F 3316 E465
 uid                  Jayachandran C. <jchandra@freebsd.org>
 sub   2048g/1F7755F9 2010-05-19

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEv0XOgRBAC9mFTzSKBVumlXJwWdkt7HvSRKo64Zs7BO/tYzt4dWVIzWwUC/
 Z/Ns/X3Plb+sXp7mcvs+oLKiHw3qrRT5wPbef3V9hFfZiKdOfmeOv5fx1sIXejBC
 Cqq5ocAoq0bqf1S9i7vnuqfyH+9SRPOv0O6EnKCU+7sVMFXAuxDhm1+u/wCgwRj3
 tNFbsptDZ/K5SMLM44ldK98EAKpSRVSMHrI/nxXvrNcPhedsC9MXyMOYE/q1la5k
 b+qNrD9QCJRwbz1LvoJGeOzEmtmZ3afT048Uks+RE03w+BhqJnuFgpAKqA39Fop0
 MBvDuZ7Wy3iigebX35PAQ3h4FhwDTzsu9aEg2Iv/WksDqluQJcMkt8sn5NffhZho
 z726A/0dPVvHy0dart8LHKfou07u8y5/950UVITjGlQJ3RGvwQV7aPEjgpJQlQqR
 BMr3TOOJ3YGHY6xkaJk1fijb8MpSlihIr+Lyvhu8xVb3GCrPCh4Bff8fO35+wpBO
 62p09dL4mJcD1mELJhMAMPpqXAXD2Ho76/RQ1yZlmH/xyAPTg7QmSmF5YWNoYW5k
 cmFuIEMuIDxqY2hhbmRyYUBmcmVlYnNkLm9yZz6IYAQTEQIAIAUCS/Rc6AIbAwYL
 CQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEPSGAV8zFuRlnKEAoKcsMnIQFgek8hHO
 6a5pFO2DBto9AJ9GLTOc3OBdX1oFFQh/rsRYKPkMIbkCDQRL9FzoEAgAk8FWde22
 yzxXI/qWRo+o6Ptm9Hae4reggr0boqeQCnV4ksLd01s7tJoaGlogi9OTLrq+OV4E
 CvkcKKHSltijMsITEwF0BwfrR1C1I59yUYABtGkw6f3bBApHNcDhl6dpcHymP8CM
 PiBrx5s63ja/CAKFaScUCUe7A5vYK91BwAJJ/IK9UONU9TUyimRRv2C86rQWV15N
 R8WE55iMdmFsu/Rkv5P3IPNzaIjcvY19iJOuxfeDTiKDp9j1QWwUOShrAHXa/Cra
 JvcNo4Iu3VeLKpaFW5zBvIbfQCa8LfRwfLPSEM+tCk9nH5zXSvwf6dDWvN66oo1j
 p2eAjrUEFnfqOwADBQf/VGVl9qx/d8NMjhMdaV6qvq8DfHy4I/BXQFERgKkFfrAd
 n1oGEJCT1fHtJNN79nCbyZ2dlfKqr6+Xcdy7RKInGHs9DwK4KfVU5dA5L3f81wZs
 OoMNuk64kjTAN867PzWdv7o+2seSa/9phsWEpCD+9qtRLiOcIZ8xeoecBS3iS3mp
 aT1HZuMLFMm8XEJSA4l8QfupBigr7Gq8z0ChwfMCZsVlVx3MtrTmuVlPnbJ4g0ku
 28MACNiHkbfW5A7XhJ8re+Rc83so8ak26mO0FQeh5qsiVj4z/pmFGrYmeH94CLr+
 bC+1nwkbAFxjZrRuFzct1y+oe3MSU0UUKTXUikovr4hJBBgRAgAJBQJL9FzoAhsM
 AAoJEPSGAV8zFuRlI3kAoI9Pl1nGD/sEvV9aGkLfAK7v9A9JAKC8ReU1wrQlM3z9
 oA5JjxumuE274w==
 =kEVt
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.46. Jesus R. Camou <jcamou@FreeBSD.org>

 pub   1024D/C2161947 2005-03-01
       Key fingerprint = 274C B265 48EC 42AE A2CA  47D9 7D98 588A C216 1947
 uid                  Jesus R. Camou <jcamou@FreeBSD.org>
 sub   2048g/F8D2A8DF 2005-03-01

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEIkZzcRBACrskMO6BYlK30ghgpDYTou1UEgp0Y4QdghWeEP5kppuDy7kf87
 CoKVvE/u+pVd7aFoTMa7ikqxKH4Kh7wnDEbFnzeZGtsf0Fzw5oHgoaQQlZHGRtr1
 49UuyFnRWVKyI8IXS25Ie5p6ZlbAVFINOdJuP81gku8SffsoifnKIiWrTwCgzhTU
 uS1rg+TpKkiRnkXXtpVF9k0D/3/OADlTo77GAWMXl6HBTaB3BXB53Q4PozvGDter
 lWGKbx6uYvLq3ZPX1XBUapzJ3eoEfCsA++FeSzK+tue/ulbLiXmFhXSQWtXoRo5D
 I75uOoXlrc45uLc9XkOpeZ5dF4a1iJOGHe/hD4mmyrWIM+E6cy1lL4EetM35ZiEM
 lHqDBACehJoEdCAVMOcfQLs33/iTBRBE7Z6fN9DCH3kTvoYcgpZsFAX2WQFz085/
 zHJ3NVFSH8LCi/6ck5ZeXCasAS3L99Q/io4WwmlqDj/b4PBdfoefInLJkroijcQ5
 B2I2cH2Ss5kkwqj9PovanMWNY6Irv2szIViIeThB+l6hiuzaK7QjSmVzdXMgUi4g
 Q2Ftb3UgPGpjYW1vdUBGcmVlQlNELm9yZz6IXgQTEQIAHgUCQiRnNwIbAwYLCQgH
 AwIDFQIDAxYCAQIeAQIXgAAKCRB9mFiKwhYZR31UAJ91fYdpk0PNNr14jtURyeeS
 upTEEACdH7tOg9LmYNxAi0iKWVInoA/TNmW5Ag0EQiRnPBAIAIKVE+F4De4BWuab
 6LREy3VmvNQgHSF8lHJm4TWKYGEkNhG+sIRFdJExqKG+N+El9QY4QGgezdogQIYk
 RBSg7nWzVrs7DiHJqC4PB/f23bzJl24Cg05jtxvZBz7t4lNXwY9G4kTmDb815FXd
 1p8gwa1KCNsTlKVRJxbaku9gHsO2JZigLMzzF1Zt1vGtaSHX5SyjhOdMOFtjuLed
 NAgl9vgAoMpXLf2Saom38Lgv/jnWz9OfST0P+OA/JmqN5DqeRTlyVZdQ8i8bduYX
 xmtbBPOGHWxwUDxiXMULkdjkLLrY1UaizR6/ULI6+cPrPLZFdnr+5GK6ZoTXyJ2n
 EUUxpGMAAwUH/iPguYUdGVnwKiwqojHq9DzDb09qvPg+UIEjwZA9mPExfMPLo/1b
 2NLgOF7pqeluXfiN84i58sipi4/ntlsNSzCYKCH2t2Wmfjdfpa3N4JaVptLR650x
 Lzj3egnWJKpHVSO+v1U7BSYBnaVPGfOMQVlSO5ra41SiVyZq6laX30PXXIFP6Ocx
 VWECVLmTR+L1g/5Nvq/L6NPv3ziuSLbSpvkLhTxLosaQwYFwPE7mLKgERUKDNc1u
 EXqyf8No4LKyO9V6VLckMgG4qbjQZhm9ozCmEYoKFZLafsq8czdNIKi4JV/8aUjU
 CsR5Dc8XAdwzPq6DBcikn1UBnvotbHtAFNiISQQYEQIACQUCQiRnPAIbDAAKCRB9
 mFiKwhYZRw2hAJ4mmNxtlCe9yUHRCzxsUxl36gQYtwCfQZ3f8K4dxPU2ClJ46fTf
 FqQS584=
 =KYGd
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.47. Jose Alonso Cardenas Marquez <acm@FreeBSD.org>

 pub   1024D/9B21BC19 2006-07-18
       Key fingerprint = 4156 2EAC A11C 9651 713B  3FC1 195F D4A8 9B21 BC19
 uid                  Jose Alonso Cardenas Marquez <acm@FreeBSD.org>
 sub   2048g/ADA16C52 2006-07-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBES8etwRBADeB8shuQ3GGp/AozsOggqLnSmFwCS8nGN+rnE+4LHuRzkL4Kh0
 pgzalpPre7DohKjX2uzq9lTjjmsrTKZLM+yaNZ9fFMHC1uHxZnV9/c7tC97oQQXl
 FjMmemGZGA3VMhh5jEtjT5EJIvPBB4SBVhVhBJ24ananUD9KmUHTyP8GrwCgxMJ6
 +NrGKVeu5QYVLo9oVo26J+0EALkWeeHI8PE3f0jOqS+Voym3jQPLw7pvx+HoySw1
 X0c0YRa9uJVH2e8aFMMsCzT/sP492IksJvtRNpzDSJJyYM3zukzH+l7J2vwDvKgD
 YknZJE0pAS0GRAVbZQ9u6bez2+CUrGZW7Bvablo7r3nBHyhI2SpeM6naXlS4AJ6I
 9dbaBACm82l0Uwip/WoJM0r/lB6eXMz9tFeRgfnPY3+G0Y9pFpdxTX0q5M73L6u2
 PeXbWI2XPyPqw0wqda5YNlcRylXJmzLFGQzR6opqIbOEzRE+IinyQwQlcAv3qzBU
 p7qCplhjblcyAhWTlM5XsrAWxXHyNFrSCCPDgW296+8b6b94s7QuSm9zZSBBbG9u
 c28gQ2FyZGVuYXMgTWFycXVleiA8YWNtQEZyZWVCU0Qub3JnPohgBBMRAgAgBQJE
 vHrcAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQGV/UqJshvBm6wgCgqtDd
 lyjakeTr7YVdNmpaI/UxpG8An0jtgTDD2M+CioUqGN1SNTkA/6cWuQINBES8euQQ
 CACt+RPVEUX/qDk3Qh6E1Zrm410mAJLfgG70tz02ApDXhW6aZccW97rH3pec+RDW
 fZVaSW4xHjUQMu1JaXK0dD++UWifuhYF+GUfi2NQflcy600VjM4v1HMZulTE5/0n
 NfPU4s2Vu0w1JcuXryjy5O8+ur10wQ4HFnL+qSDmXY2UKKTHA7vVrBTmysELDuj5
 N6T9+xxuR7EJG3lwTREgPnr5nRlyZBxgAd6k/AJ8i2X1YiGix2KI2fk/HYdgl3FL
 xnLXrLE43mAwQjcmkMruNkebjfAAnp6vKvSOLZ3mqoPNhP6SPGTPxoskcHqHhvXh
 L3Y7/Qqga4sg+P8tZ4YTx4SHAAMFB/92KAG0TePM8+gtp64oOp9RuUELjT35f5RZ
 0ZJZ1JromyMjOc6FRh1a9HiVzY2Vq99S/r8S5QoNH6vppxGjSL3Vs6vJg79eT5Jc
 ODdEZhoSzqmc/TwTHfOeHiFJJk8kAtX33CIHBUDM0p3OaJDj3weYi0TUWcxcvlFg
 p4RIYHCkmJj1/sI+0U8Jw35nSK4uNwW8MCl9a2hwHCtfnvQBfotybc4+YuwFesT2
 SDRit/mXxYkmi/a5GPB0To/e/QSBuk7MMNtLv0oF8LCrfaN76XOmahxjaSYidA4H
 LUFNqtRL9J5/T4VSZsrSl+Gb6HQIaMoGPbXmFk3i6FzNP7VDViZ2iEkEGBECAAkF
 AkS8euQCGwwACgkQGV/UqJshvBlwLQCgqDaWuJOgfV0r5li2gRPUMI5XCscAoIG2
 pLZLUWFiL2unIMhkFZSQbZZj
 =I2hD
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.48. Pietro Cerutti <gahr@FreeBSD.org>

 pub   1024D/9571F78E 2006-05-17
       Key fingerprint = 1203 92B5 3919 AF84 9B97  28D6 C0C2 6A98 9571 F78E
 uid                  Pietro Cerutti <gahr@gahr.ch>
 uid                  Pietro Cerutti (The FreeBSD Project) <gahr@FreeBSD.org>
 sub   2048g/F24227D5 2006-05-17 [expires: 2011-05-16]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBERq43MRBACwBpnAQKjba4//RauFjrfImT2/oiaNWsxq/oYloEhFl971iMsw
 LCaXDtgt8qJDj4RFqiQbcaNBONsht5d6vM2u9fSPq+8aqTwKBUgwUV7EVeBluhk+
 S/iG04HU5lrYjklvmMwkOMUJsuCN8Sj2R6Bc0oyNGbIk/eF3G8Pj70GKqwCg5TzU
 iz2NkNzhoyZIAyL0jyY2/1kD/jSj16M2A3SvH2n1dtNRiNkceKdb8GFEoX3/Irdf
 rt12YcOhjm98XvRhDFJa1R2UgLul6q38YxcLH+rOH9nmlTy2HIYh1HuAPtftR678
 ApOeznte0gxEstliD/AJ9sR9IfvzS105E5OGCWzZc6AMJa7MT4XVAlEogHWZCxou
 4eDMA/4najs55j1kz8khhLiAX0SUJj92XpjmpSFLvFB8D4JpeNtWKGx/wt9uwYBr
 GqnFpP7JHUFowTgg4LjgM3r+W+s1TyUZ5cBlgTgp1Qh6y0h98X6Pbppu1GEhTvWP
 9FlvKNK1+bYNKKvUFHc5nLRK+0M7e0IP6yws2O9RN6rkb6UU8rQdUGlldHJvIENl
 cnV0dGkgPGdhaHJAZ2Foci5jaD6IYwQTEQIAIwIbIwYLCQgHAwIEFQIIAwQWAgMB
 Ah4BAheAAhkBBQJKwl4hAAoJEMDCapiVcfeOp+oAnR9QXvf5u9vyeU3vnAo7CiyW
 LE6GAJ9Pip8AO5c9BvjTjsRhVH9O+447qohpBBMRAgApAhsjBQkJZgGABgsJCAcD
 AgQVAggDBBYCAwECHgECF4AFAkUULcYCGQEACgkQwMJqmJVx944wAQCggfm9PIqo
 j6KZAih/TjByBR7kcAgAnRqnqUHf95IzrsGn6d7b+IhfvKh7iH4EExECAD4CGyMF
 CQlmAYAGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAIZAQUCRc3QKxQYaHR0cDovL3Bn
 cC5taXQuZWR1dAAKCRDAwmqYlXH3jswNAJ9KqPCEaiTKejBDeI+ZjLemDPYFogCg
 vC7oKdYHCRU/i9jgcsiycL3wuce0N1BpZXRybyBDZXJ1dHRpIChUaGUgRnJlZUJT
 RCBQcm9qZWN0KSA8Z2FockBGcmVlQlNELm9yZz6IYAQTEQIAIAUCR7xw2AIbIwYL
 CQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEMDCapiVcfeOw5AAoMjUQZiqAGONGzJt
 T3RI1sHhl/p8AJ9ytrTA/gwo66j9K+qNDxQ9kUXqubkCDQREauOLEAgAv+OK9YPB
 4r5+9aZ9/tV6ItolxheP3skoV9ISg4T0ltZM8jLtBLqPY5qWlGRrAbh3ZHkOvrrf
 Y/bfGxPg/qlOe+ewqTnAA7IQcBXObENVfrq2gm35aluNcHbFutYGrkAThuFst1qJ
 bPowBBmQgR7RH5/lWbn3Qnisthsm6J5JldjgcfXth9usyXsGXCP1zZ10Sj2Q090S
 uSEEC/PfBpSbgkEMtTEJfirmVKTp0gPfIdUn/HhT3ed4kkZXkQJvvI/t3Glyp7RY
 5nMYPr219vJ+bYP6yxm9gdfLey6A4gEprtncF/7MTUpib3MvgBpmPRq9yV4LHbhi
 DbXHaoXG1uZVvwADBQf/TkvaVZK55GKm527FenxU4hf0fWG3orqKAI/p3AhPj7l/
 T1nLGWHMku22j61zx9N5xPElMLFdcs4+BX/ltzZdhFS67k+Ya/CLy0G3we8KQSqo
 UTzlP7Mr1aJtXiNXUbadNrkSX1DlRV5RP6ro73vvaFXPwHTxSmRRHg/UgE0B5+tJ
 kuNmK2whTDRR6rfpEcdIS1Tms8IUnva0ZI0QSnhzUcxv+YrV8TX11/NC0FlmhxTz
 ncM1pa6w0yGC/E48uG3NuElPenqM1h05xe9BntWbBPjB1TYa80jYNbLA/KdKEZlK
 1klP2PnNoAX3HoKOm/1rkYEywGfxXuJezX4fYLrdxYhPBBgRAgAPBQJEauOLAhsM
 BQkJZgGAAAoJEMDCapiVcfeOsdgAnAhRFj8Q7p39kg5LmO/zsDXCD8wOAKCDV7iQ
 R8Dblj7cX+WKPwwhnrNq0Q==
 =UXRy
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.49. Dmitry Chagin <dchagin@FreeBSD.org>

 pub   1024D/738EFCED 2009-02-27
       Key fingerprint = 3F3F 8B87 CE09 9E10 3606  6ACA D2DD 936F 738E FCED
 uid                  Dmitry Chagin <dchagin@freebsd.org>
 uid                  Dmitry Chagin (dchagin key) <chagin.dmitry@gmail.com>
 sub   2048g/6A3FDFF9 2009-02-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEmoPBkRBACM2PQ+WGI38Z5NtkF50MuYyv0u4qSaWtx5Tquch2sgBDjxjebI
 XQYuyzM9piV4ZSZHFyjvFCHjLhPg7Ae6xaeaOwPsGQ2Q+bSC92PoTC3bDdHW1hPV
 6s8KxrFcelHLwhmF56WIALoI6E6IF60KztuISLm0VDG0Wy3lP8QAeoWbgwCg0fY1
 iOETR0ZP09ophWg8CPUxyvcD/3NFr6GEVUuFX4ENQkX2GTrvEB1IBS3v9JvEMlUX
 bShFXWGHB+3ynBvw/EiuOgIB6Jzay3prP9rdGW4NSV7ZMa3Yw6OdhVpQ0ticn4zU
 FiqLL6x8SKXKSm9BvjFuWADe3Lnu/ekY1lYTM4iWPNdA2LjRUHwpDIHcHWgcCzkn
 CfY+A/0eKkj+/VTddCspDaXuTmgGlkz90LsA0cLv6gRO3IV+0t80TgohtsCdR2X/
 Yf7fi8GsaMdhgJZNm9dMz/zD7ZkQ+OyQN7NkB1zkwg2RwOnbbjTa+HECtsr2Znb6
 B85MamlnHN0WHNgexaC6c7ezEFq+RMBKRVJJGwehZXpT185T57Q1RG1pdHJ5IENo
 YWdpbiAoZGNoYWdpbiBrZXkpIDxjaGFnaW4uZG1pdHJ5QGdtYWlsLmNvbT6IYAQT
 EQIAIAUCSag8GQIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJENLdk29zjvzt
 eLcAn3hUOTepQzeJqPuTFl2Z2dM10HHKAJ9DJRmSIAwHBGPzlAFFzKKFW+OoV7Qj
 RG1pdHJ5IENoYWdpbiA8ZGNoYWdpbkBmcmVlYnNkLm9yZz6IYAQTEQIAIAUCSam5
 zAIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJENLdk29zjvztRJYAn0cIluug
 IS7YO6a+Bf0FByX3jlndAJ9k3HAxpt9i9R0wFkFmbMX0He86bLkCDQRJqDwZEAgA
 jMe9QT4KYOHsLQsF5vHBq/+W+Lniy6OqEB1GSK9P/vqVIqVa7v7NXX/B5R8UiQMz
 fSNcYH/BTN1lb8Pe7pAIBpqPhKBi7NAW1Ddy9399co1c37ncf6HEa2P0tpJbTrG0
 Eww9nUiFbhjWUHSY0MT57mHQHdCSlqNFl2jaV91CQaNybt9z8JLO301vQXP4LLND
 a/FQ3TdBEIXFLs/H8QKLBe5TBgd2lXy9qpZsii7xpfNXKG1qqIa8sfUoJO5Ng2GB
 K6tJUFh/J548BLt/c/p1KJo8ovJB70DiOaznRc+Tu8rR03ehdfrJ5FpDoxC6UAa8
 7FpXWxjM6L3N/T01NcaXUwADBQf7BpNvsT/QzV74wnGXoi9aUE84ojkIAm9X4Q78
 dfdCvSFWUACcvsB/d7XLcCXOZ1NJ1E8Tdjjmr24MRQRUY8MhDt47ngsTyDhDW5l9
 EQ/ByjX3wlRBNP5qEDVkLudfRE6LlEye2NSNpXYs1Naw6U/deUggNZMwriVCuRI6
 TPc/bKeq7+378EBaKc8ckuRdv8LWsIdaKQ6rQZh1CB6LpSsL9OjcRpKvK8yYas6I
 kWUr07xvvlVyRVLcrNyQwp2QnfK8fXeH2I/Qg9QwcV+cXyKzH4vka9zrR1A9SAHJ
 iOyMXJBy+GzoYLf/y7/u/LOVAm09P4tQ/7V/DY7nxiOabSioTIhJBBgRAgAJBQJJ
 qDwZAhsMAAoJENLdk29zjvztGEAAoNFpe2XX37q3yAaNfiZgEABrxsgZAJ9yH0YJ
 QrmO4sxq5l7AD6K+KNahRQ==
 =ER/k
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.50. Hye-Shik Chang <perky@FreeBSD.org>

 pub  1024D/CFDB4BA4 1999-04-23 Hye-Shik Chang <perky@FreeBSD.org>
      Key fingerprint = 09D9 57D6 58BA 44DD CAEC  71CD 0D65 2C59 CFDB 4BA4
 uid                            Hye-Shik Chang <hyeshik@gmail.com>
 sub  1024g/A94A8ED1 1999-04-23

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 4224 characters]
 b7AAzA==
 =dqQP
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.51. Jonathan Chen <jon@FreeBSD.org>

 pub  1024D/2539468B 1999-10-11 Jonathan Chen <jon@spock.org>
      Key fingerprint = EE31 CDA1 A105 C8C9 5365  3DB5 C2FC 86AA 2539 468B
 uid                            Jonathan Chen <jon@freebsd.org>
 uid                            Jonathan Chen <chenj@rpi.edu>
 uid                            Jonathan Chen <spock@acm.rpi.edu>
 uid                            Jonathan Chen <jon@cs.rpi.edu>
 sub  3072g/B81EF1DB 1999-10-11

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 5016 characters]
 qnfGSEooSVFz5kPTaACgtZYK1PfljVCb4e0xoy8XkArq/8s=
 =cJgh
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.52. Jonathan Anderson <jonathan@FreeBSD.org>

 pub   1024D/E3BBCA48 2006-06-17
       Key fingerprint = D7C6 9096 874F 707E 48F8  FAB7 22A6 6E53 E3BB CA48
 uid                  Jonathan Anderson <jonathan@FreeBSD.org>
 uid                  Jonathan Anderson <jonathan.anderson@ieee.org>
 uid                  Jonathan Anderson <anderson@engr.mun.ca>
 uid                  Jonathan Anderson <jonathan.anderson@mun.ca>
 sub   2048g/A703650D 2006-06-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBESUcI4RBACIrp/6emcURG5g8edmVyp6d/PcuRDcy3i+YJSXqLPp/3qfM2J5
 kVMCQvgFSXX75K5HvZU6mMMtHYGCComtn67O1MbUSyVUZlNW2PwUr77Nc34MgcYF
 fzU7siy8Pc8LqIy3JUtHwi+qmt/+UsQBTCO+2heK5xMj6zklm7qRfOo0rwCg65HO
 lViBItJSZuZnIqz5chlFbhcD+wdg1tyXl+HW/d9E6LxMigAct7fFMHd5aA5EWWr1
 plTfSSxOETAsX1afsEBfrr6d8jLVri1tfDvRHe/30YxRv6rTZ64GLIXD2WEoN3yg
 NvRVRkOeFPtN8K1gHEKRrcp9ZJfGG80F6d/RMk++AAbg/pI5ne6AxEiR1cAHmwGF
 HlfzA/4/bmU3m2n2SEbBRAOugrYcSRF0OvPsju2K34pooAnePs/S/zJdILIism3W
 1Hjjp46R6kEtvY1ykulseQzRk+IpF9Esc2tJA3VSHL0Z2uI/1fg2mCGc0nk+t4MB
 oqJshJLlR0S7LerduZ/Rc1zErb4nfhG88GzH2Z6fawZtantmjLQuSm9uYXRoYW4g
 QW5kZXJzb24gPGpvbmF0aGFuLmFuZGVyc29uQGllZWUub3JnPohgBBMRAgAgBQJF
 Im7qAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQIqZuU+O7ykiR8wCglscB
 c4qLHc61O+WbG1AVlgMrvXAAn0R2OaVyHU33lcxpP9AZHsOYmhcFiGAEExECACAF
 AkSUcI4CGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRAipm5T47vKSCC6AKCG
 fne/4SQaTeR2HtTM8lJGMQZCDACfffBWKNxqzE9C1pp21dlJPyhOLwu0KEpvbmF0
 aGFuIEFuZGVyc29uIDxhbmRlcnNvbkBlbmdyLm11bi5jYT6IYAQTEQIAIAUCRSJu
 zAIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJECKmblPju8pIj08AniQCG2Zu
 dFFzMubFUI5RK/s/KmYQAKCzEY9efR+f1sJKSo9/I1QZuNNQ0rQsSm9uYXRoYW4g
 QW5kZXJzb24gPGpvbmF0aGFuLmFuZGVyc29uQG11bi5jYT6IYAQTEQIAIAUCSBtj
 iwIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJECKmblPju8pIAtQAoIifNHQi
 kGm5CIgOxMgMAc4zZWaQAKCG2cl5XbQkANEp/5LB0AJkVyP5KrQoSm9uYXRoYW4g
 QW5kZXJzb24gPGpvbmF0aGFuQEZyZWVCU0Qub3JnPohiBBMRAgAiBQJMrKDcAhsD
 BgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRAipm5T47vKSJPMAJsHHtHqP65y
 av3mDwxrHqnGYCNw6QCfSSK/rPic0fGdI+kwKphP+t804+S5Ag0ERJRwlxAIAKGW
 DtckTk++NzYHbfCmCa0mCtUg4BQ0752ZRUZS73V/dP4LYBmOS7ubppIWC8XJ8vCA
 YKesQYBde3Ly3TrZfzdlDLBlua2YzmLQgwZvTzfalzcUrbHzFWy+mGqXBBfnclV6
 tYwMDmsVxsukpIVsZzWpEMBBrrd3Zsr9SZG8rjyfiiuv5kvrdPpGv/w9INCcqvMV
 CTi7whrJn8MBwD/rNVuZqa8kW1dN65xKN98Jn5RA5JCX7kY04gIyUL6x0dHnJZ/c
 dfRSMgHPTROiajnzHrd9Olm4e05Dijd5vAffF9rxNtlJNTPDaN57RhhdTK1ZE6mr
 zWocL33kLML77+3rVZcAAwUH/0sXk1iRq1cs6D99VsEpK5Yu12U8OTUk8cPZF+8C
 HsT0c5xCbaPENBebs8gtgS1/oURvO/lgNmthPFEdyD60l0u+wt2BSmua9s+tFsUH
 uWgTSx0k6Z3rw9wZV/YUxe5PLEJ1JJGi3YY7qCG0BqFbbHcpkrtj6X4+H0Y01MzO
 1BdklQ548jHb6wZn6BW+dZikz/vE7urxhx73CpRWerLtq0EpFzsdRc9DzChqmxwX
 WZFpSAZT4fbEipdmK6dtNPJoTeHpB4zxTX1Cj1HHCKRw13dFlr+CMBnQnhJOOaM0
 kh22yyLrR4rikuEqnhfB79Gw6dxlJltTUKNuPHk4D14Uh5CISQQYEQIACQUCRJRw
 lwIbDAAKCRAipm5T47vKSCIMAJ9i5XNgXRnS+qoCDrSgrvf78e6zugCgh+4Wscpb
 rOIHnGJFBTAXFZR7KjQ=
 =PbEt
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.53. ^3--oO:+-d <loader@FreeBSD.org>

 pub   4096R/6BD4DDE6 2012-10-26
       Key fingerprint = A33E 88AB D358 DA49 59A6  B263 A9A2 599C 6BD4 DDE6
 uid                  loader <loader@FreeBSD.org>
 uid                  loader <loader@FreeBSDMall.com>
 sub   4096R/1036D26C 2012-10-26

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBFCKlFgBEAC1gfhqlgka219RDGpoUEn1tIl8XaNBDAMyd+EShil2ILN5Qqg5
 TgMPiHgwuKMil0VGd8+BMNVv/XISFPv9fhIaTzhhtovD4Hffiu2s7DMB73BqY+Re
 piDXy54sP4Q38dnC2NTQUSCgj05iE5U4ucH+wwIV++iU7zWTb5gPVnloXTf8W5sn
 6hKO+1iqYz3SuiswTx+lpD5wx/K+sCTzxPCtpa0QrWzh2f7+nijaRa9AiAVOg56z
 Tb+lsucSyCsiIGK2HCvVuROlRW9l8R5Jgc94P3P88aOh1FLCiMKiHymxAaeOziWd
 sBpA5y15lAmCpKtjYedRL49L1kUKjlLbQ0KCsn/Ze7cd7Q70FHhvzdvgoiHaJEVg
 hbYHByychJz5bn/uJZfowrnmi3dW0qCo+ipW7bpayING8mgqY2a0B17ahYCCxtPj
 Ii3FC08HdBFQ4zFqRFwTe3WWCMYbTAHi54bmy2StOplIRzwazIEuuXCo4An1S0Vj
 NMZxmFvbJY9yJ6c64yhTZKfASSZGpoFt7qGLSvu0ADlDg8YYQgkldrzCJD6qZoXk
 x3ARVJS0cW13hxzbOzmSpG2kxigHfr0qrtstBjRPMfVfJkC5cTatGFwD+zuFyX/D
 8ZRQim0u8NXU3w9AAMxrb7mfFbRr7SyLt0oZzJJ078v1WzjBBT5O6YyIBQARAQAB
 tB9sb2FkZXIgPGxvYWRlckBGcmVlQlNETWFsbC5jb20+iQI4BBMBAgAiBQJQipRY
 AhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRCpolmca9Td5rvzD/48NART
 XvFESTkgo2du58dR6XIPPJGH+ZXZwbTq9fdhhgJHYdD7Du4VLRQDJ5fFGFnES76u
 I2qQlNvlAMfyrRryUGK6RFU3JMAp52F+NCm7yPcyyu/kKIlMjyJ3jjlWRzOdJAKX
 N7sdOvowaV/rXf4gKQ9sPl2Ni/e+gi4yQVAHbUVwXwbqf8/ZOpn1/GGGkXsiIqRw
 MmlGRapUaeNx03Uh/n0kVBZhc9iIvQ/2VXdI1Ulu1AUZ7a/gu+Y7b87pEaFilhQM
 Mipo4LgV6UeDtHeKOF/Dfyn3SBPuYmZiKJYeSm10nnG2eWYedSonoJ2tXbo5FbOI
 6zprSBCioViahJ61+FAY3rxyEvjOPx7HtWWmi3V3G6FCnnxvOMbgKkgadcFvPDHO
 hDdx6o4QQVTeb/FzIZ4UMqWursPRK7HU9e9f0B31ovj7B3kw39O6OzU3w9aIX+Zc
 SKiPf5gLAG2XNH9dPMxwJ6Wl8bfeeeIU45EUOe5RldckmtJoRCqSPkvpMTm2FesK
 O/dgYiDPGMBHHFmABMutyhX7KI4Ltl2UqfIa/lreFiXYK72syQG6Gd1moek8EG/V
 BqT0oEqIa9k15mFFMFrj+X6ZEHsMOkY2hrqEJDqR15JB4HzY4IJY8gfOk8Twn+i8
 c6obMChlLIn+FhkBCZu6hZEMXQ94LkWc4L9OurQbbG9hZGVyIDxsb2FkZXJARnJl
 ZUJTRC5vcmc+iQI4BBMBAgAiBQJQipS7AhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIe
 AQIXgAAKCRCpolmca9Td5nrXD/9y0Da4t+PMVUt8P+IH3VVbcsO9JQuFiaGotfl6
 uU9+DlHe31eGmpaIptTuz1B/YqiC/S2uc3R/f1sW6K/Zyo8CR/LtioHHE3HnJtUO
 rNau9MiKyAkVHB2oEVeTjWAkDESDLuc3bCkOO78SHiXgHaRu7XeN8KxlhioI+gPq
 ozTFN5weFyXTQnp75CM3dtbJE57VyiWuan+nivaMwOz1/WMIYzEgX0T9n6aRtiwo
 qnfp8/gJCIzGHN/TWeoFHN3s24B0ZWH/K3VhcOgSb0JV1qMKETaMsKd1y3T9XKu3
 igBfRjz3U9EZfb+lklWsnRn4ArSVdI9u13tlFQJkYUq7/kbFpSJuc1sUxgLlsjdd
 E0RJQwR+gH3k3ERQtc9S/yxSgb09YX6lj6pN6Anpmh15MmuAP9G0Rn6MRLsHzIBO
 4mHYoKX2G3FRwoPcWt/gVCzNrX42Tt7OI2h2l5JmXMJfaFhbDyvg3YYK0r8Nx2H5
 vKXFugdep2d3Qwu7od2824CMSnXfLcNbdAlkdTDMC/8btq+wHmZ8E3cP88EfF7ZV
 eudPVFxCCZ3q1ziIwAa/Qx5KUtWXKZsxLixHQxTMQUCUdbmW5/aTZxLbwxrGCZoj
 YOsmy+w4aqq4gjumPzTGU3+gQc2w5hPN0yLkgRd2+Ev00yeE1lMN7nOWvWwhlWLO
 0unVxbkCDQRQipRYARAAvr39W/sawsnXrbVLc8uwPgQPtq9hTkMqGwlJJu9fVac/
 7tasIxPvUSO5HH0mDTdzIVKKeEqQ0a1XYgmZrp6Gxa/Sxl7G6ENuDrjec73SoQGX
 Pux6hj5ioAKDTl+I4z0K52HRcPStQt9phHz3Qnwp/P8C7WX84m2ActPHnhn9KAzX
 sAEi1XOGHq2zh5iABFc5PFjqe7D2CfTrnJCVqs0NteHfia1JEgTdIK5HPStnx7jK
 eeMSm0I6ft5pY1zumpLG0P9BI7LysFmMvX3EMgRJ6x20OX6VsB9oQwuhINZYmvca
 ncRPeA8L7CMQQN0q6RtZWctanvPGJkr5ojZJhiPNihX7bxo05fta06Z18u9cuvhP
 Qda//K76xgHZrT3y618qxWco2mqvtJ1avATPphaJpibUCJyZyOv+TlhgThJLINQA
 Lx0Y6KrVT2ZT2+HU2r2C1ngCM99beYq04Pu43dKPMGed9chUDrUIenu3D1oGpxlX
 mEygzNycqXgfL9bY3KZa90yveCk3IAurAwBMxrzcAFxu3QniaEjuYXtQzfZWaMpn
 aTEGnKxvAHO+luCxlrn59MbGvVtMuKUo9dwgrxI28v2fxBoAt5xdSgrQcp8+VD9V
 2AL3RpuczdVR22ZbUF96MIQNSSmqth+Dm/vXZm9XmvycexHo1A0Wc+pGiiyOSF8A
 EQEAAYkCHwQYAQIACQUCUIqUWAIbDAAKCRCpolmca9Td5kMmD/9NISt9gHM5utFh
 PndSvmVKO4Diaypc5AHbP/0ywIeZME8AspCzPXmZe6L4jeotYOOp667XCAIM7Wlu
 4vUeOIRUpuuZYMFuECbk/b+VvoHmkUKO/5XgG5n8PgHS5vMrA111nuGpQ7B+FwrK
 SaScP+OBjZoQzd+G054rMM0fhiF9/sIftBP/WPbGcETHS/cHXb9co+JZyvNfcE7Z
 OfJ/gd8fZIIhBUDgkClTmca6iyRiPA6HH0qSrFiIZuDtvuU9BMkLe83ivqPPscid
 1iUfuR9rbFpPB2gWXHF/X70SlMTHfojITtgcNUfMjI3eBP6mSnNF4zQnf/CJtvL6
 SAjGsWb8uvRv3Q/F9vv4DeNVXrEV9tXj0HXJIJeO1uMS7PJC8bfl97ExVXxFhjV/
 LkBL1/VgB5IpFIzjEeJLUtk9ePP0CVKw1pCZpMrL7UvrImKeI3XDRfD3f+N3w+fW
 REIs1X9HjO4e36+UDPp6EK04EtpYleFB9kAxv72HAmmWIgyPFNLCuo0/k+e7UZL4
 yOcvpGSVlQH/6bgS+HxoN5vtDfEgmmqDhtGP4ImvDBHEmNGA8+U7i+Q9qdCqWNgq
 VyPAMMlmqrY7alOo1ih3htkZiGpNJs/BxdZqm8R/bnIccGUwecMWUJZzHcc62UCX
 DPodrx7PwaXno88xFjmqosI94Et7mQ==
 =qJuU
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.54. ^3-NOTYEN-aA <luoqi@FreeBSD.org>

 pub  1024D/2926F3BE 2002-02-22 Luoqi Chen <luoqi@FreeBSD.org>
      Key fingerprint = B470 A815 5917 D9F4 37F3  CE2A 4D75 3BD1 2926 F3BE
 uid                            Luoqi Chen <luoqi@bricore.com>
 uid                            Luoqi Chen <lchen@onetta.com>
 sub  1024g/5446EB72 2002-02-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDx2qBMRBADYSjvWKVcUxUb1aR1VjHTlFo6zc6PHMK8W3CRin7lY3NgsYsmZ
 n0IvGQIDEHhTpOEWLS0S6A/bseaGUir52X6spZ8i5hfd7Ps9RmeS0oHx0XDS9JTJ
 HXFE5RjExHbLnw4DbsaqR4Fl1V7NJU2U/nkiJILJd/PGPZsdstKYv5QvnwCgmwr7
 QZlkTV/m61MmbMAEpEFWaecD/Rp5Qb9S5NGVplNeNqub4fC+Ydarkorr8qBJN9Va
 xu1Qgj3sOAoxmuOnZ99YAgXhs9Bqe4QsrQfs1cMUVzZsl3FIffh92HkrLmdJlsjX
 8lrRT694cIP7+ELNGKJ/zaXI3j2cnQPVqUO1icVfijqatqDg8bgQS8C8CGQX6e6h
 ADKGA/9cIY450gMvrtbR3/bqH+IgvBCUog5RXv0y8c80sJnzeqawx2BuziFvv6mZ
 Kv0PJ2vnWok0NHcyuBHkkEt+ujYlMQXHZ6wRykYxIUzM8tl+9129tSNEK+GdcCOZ
 rfbwm8scs+VmzrHXP+saOPcHPBr0e/KPPixNN1I5HB3yI0ILSLQeTHVvcWkgQ2hl
 biA8bHVvcWlAYnJpY29yZS5jb20+iFcEExECABcFAjx2qnEFCwcKAwQDFQMCAxYC
 AQIXgAAKCRBNdTvRKSbzvmmrAJ9FVK0lT4Qym+qzj0EA6TP3V42cwACfQl+ClPzJ
 zngykscMJW07MBXkQ9i0HUx1b3FpIENoZW4gPGxjaGVuQG9uZXR0YS5jb20+iFcE
 ExECABcFAjx2qpkFCwcKAwQDFQMCAxYCAQIXgAAKCRBNdTvRKSbzvkEwAKCRteUw
 2X3XbPsVDCBZarrkf113YgCeIHmhkDHbauw4UlUO1tYNVObn5dO0Hkx1b3FpIENo
 ZW4gPGx1b3FpQEZyZWVCU0Qub3JnPohXBBMRAgAXBQI8dq6XBQsHCgMEAxUDAgMW
 AgECF4AACgkQTXU70Skm876CUQCggJuwNIJy6f05Ka17RYn+j8hEQhwAnicDXnsy
 5SEYN6amlHdqN/HwXCsbuQENBDx2qBUQBACifA9hUBBYNqCcXTs8Jk1MCcToMFob
 vRt/SK2EcwjZ9aF9sIX3tJFrOHEe/bIcDMX19e480T4+BBs9MyHdnKgPR6vP8ZEe
 FvT8+44Wd6psLB1LwsE8UpJ3CbLjkgafTpJIlh4NP5iM2p+2ugUIRM2ZaAG7MOMK
 Ec47KOEb6yI9ywADBgP9F+p+zQ1Z/qVekBooIKU4xKBryGb/XIPJi/Pgapgr3oE9
 kKH4iObbvMBSV3kd4a0+FSEXSZyRnMD1AG+dWhAHgb9rbjtICp3hZOKCMfdZxFVg
 QStZO8vP5EhQYYtIXiNmOvkkBPqb+to5RgFFez8oIdPlMUq2Hf9MBIY6XDoNJl+I
 RgQYEQIABgUCPHaoFQAKCRBNdTvRKSbzvh9GAJ9K3KifYIBOHlsmRLF75mgKQk/c
 0wCeIOeVykZkImOxs0pEQMR/4g47Wjs=
 =RNuY
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.55. Andrey A. Chernov <ache@FreeBSD.org>

 pub   1024D/964474DD 2006-12-26
       Key fingerprint = 0F63 1B61 D76D AA23 1591  EA09 560E 582B 9644 74DD
 uid                  Andrey Chernov <ache@freebsd.org>
 uid                  [jpeg image of size 4092]
 sub   2048g/08331894 2006-12-26

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v2.0.16 (FreeBSD)

[encoded data, 7854 characters]
 2a7K69vHoDfSFMjp2trLswGcAJ9RFN/fKYunmZzi/STcxm8mj4AJRw==
 =+4em
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.56. Alexander V. Chernikov <melifaro@FreeBSD.org>

 pub   1024D/2675AB69 2008-02-17
       Key fingerprint = 00D2 E063 2FB0 2990 C602  50FD C1C2 7889 2675 AB69
 uid                  Alexander V. Chernikov <melifaro@yandex-team.ru>
 uid                  Alexander V. Chernikov <melifaro@ipfw.ru>
 uid                  Alexander V. Chernikov <melifaro@freebsd.org>
 sub   4096g/BC64F40C 2008-02-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEe4fOYRBADWmfOzx8cXvVytbw87eVlU84SXo3tZYeffxQkJ4JzGoA4Tq79w
 2nTLPSnd42W8gTZ/dxEzhbij3RW5mcvc9r6N5YsOw3eKC30NQMM05nV5/yX1owj4
 +eZ1YUZdJKUshhWax9dL23BDLEPRWfKsBWS2osqjIPy6WhDgTlDBz9rJGwCgqK5g
 Z7sULpLNE0nnJPQEWL8zt7MEAIIYKjPXf3BvrDtsOHWpOK4hZgf2X9oCfoFymVdp
 cQ6oCWsigmKyGuy3JyyA22UDRfZer3TqNCwd/ynHYXMmYl2IZ4TtV23wGGQDGyxw
 cu1SRhTcPRftCMI2r/6E1vHSqSSdmWwBv6gdN2kVSqx+REchIhuyWWWhMr2A64DI
 S6rxA/wMn97Q+ayj0S2t9u7NbUXQPcB1hiv5qMXWMFco3NokOsUdvK31v8m5fO4P
 Zzzz2JceN+6ae901C2Nrc25ZhujjtLs7XviqUB/GPLymfGUaCpRlm0XReKJPYQKo
 V4jAXxjzrevEWTtNwaC73V0x/w+CKWVhyfUCUcf6HdGkil4CPrQpQWxleGFuZGVy
 IFYuIENoZXJuaWtvdiA8bWVsaWZhcm9AaXBmdy5ydT6IYAQTEQIAIAUCSeHOPQIb
 AwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEMHCeIkmdatpMIgAmwQewwBOZf6E
 EvGSx78VopWKwtyFAJ0Q0gEIyhtgVjHlGgdOhhaN7D7a7bQtQWxleGFuZGVyIFYu
 IENoZXJuaWtvdiA8bWVsaWZhcm9AZnJlZWJzZC5vcmc+iGIEExECACIFAk6LOVIC
 GwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEMHCeIkmdatpwXgAn2Sf2rEX
 g3wYOqke+DBqtgY7TAxPAJ9Qo6HmdRlACa5S3WR3xFFdx5SIYLQwQWxleGFuZGVy
 IFYuIENoZXJuaWtvdiA8bWVsaWZhcm9AeWFuZGV4LXRlYW0ucnU+iGIEExECACIF
 Ak6LOc0CGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEMHCeIkmdatpU64A
 oIl4yXypO/ve5VmpqWodSg2KpI81AJ4l9hRomH4gu1ku36RcejuWkYoSVLkEDQRH
 uH1AEBAAxMbUjr0N//HxCwCrCp/zy/yyF+tjYCoVxlFjeui8Uxc3QpDmsxDBgLed
 YggRT9VEFBHEF9T9edsK+2Rjs96saGcyolKnfeQSxz9ua6Vst39vAdjBzqmVXWJW
 DEgU9kAMmLsONi5nO5SaB0GpnhNttG5NM9J4lgZ5HUNnyCMEGUCOXa4R8R7sykS9
 K2IfJZLsXWmvXXHD53B1uYROPTn+HrDixwdoYFDltedGKez+GPdP28PeBWeIJhQQ
 f1oxmlgNU8L++BaiGmY/QXBVRm/Z3NOuWi99NupN32LgZNCGdiZLvltgYaQcnYRh
 08Br2Imu5vK9XpoDHs8a1AO5OBJVoysdu1ESnyzuvmrRewbG14+8kPi/4EKo8lnP
 bYGUVwh3R8QrSSzki8v+AZagh7Shf9m37QZtIzsycqqiE/S4o1kCyOk4q8vooRMU
 852oXyHyF0BDPd21gfz6b2bKyi7eDT8apzrrZ+Z7yY+4TCg0D9m/LloT9cEag15T
 XxkuPqOF6gq7vMqm3GDa+X4wXgrVhNwbKHT3hAo/eSoQTdB5PeWELZ5ykV6Ik/6U
 ccG3GZjPMSbQU217PlmTVKmv2yrwHXxAZECQAlhZUIEkyVBHQBYuSH/37r8DM4im
 btIL6A++CoJZpf71YjEiPDiQc/ono9CPtMGsbPl3uekhYxdwM9MAAwYQAJRqYdYc
 Xb2IhEEbcdnE1FKzO/e3d+O1ze+diefS7/Lxd9zAPdmHY9W3duzFgQv50F69kKUr
 JzZF77o8X1dlpD/ip2Moimh0rb40PrP/AasCiww4hgXKfsDInqSMKDK4KaZZCKFf
 4N6yGD2KAqqGnJfNNzIrdxpH0BjeXXZm+Fzmr5M/eWMDGOJZmYnKCSF7dStdwVZH
 Ld7RUvpQ3cR+lQUI6hYTMhXPqR7mEDAHq7IYzbA1HBp1c1P4vywD/myTi4wevomE
 1/GprPYlocXaytWiRjJvGjLw8lg0E6utQRLhoPKIIp9CsNBw8IQRZ+qINtyO6pk5
 oxnuq+yan2ixb10hBx1yQg6PLmgUaWqPihjZ+i1qtpLoMV4BGxzWn11+o8Mh0skH
 rmKP7DEbX6Ctee36gr6ULZATsje4OyC98T9wzNmLDYOV9Zusukd5Kxb4f6MuDO8D
 B8ky12ZLA9s7+RmT1Vx51pXOj2YnTT7RE2+QWu/gUfm8gWsq8tSwowzuE84QcwfX
 2/W3oN4QIVUqWULzC+vUV0TnLO8K5fqgn8AkX2ta5pIYF0t8+KN/nb8mgV81w6cV
 ii1Uhv1yRMyro7D+eURm07yvpWyeLfILnm4U/PoFx4JK++UehPB+QACs0bKZ9AOh
 kTjflPiKorAw13Mv/BinmgRPnSJZzqUEW3ILiEkEGBECAAkFAke4fUACGwwACgkQ
 wcJ4iSZ1q2ldngCgh5mTawBEKWXNJXXVFGfo3CiWc8AAn2wCkHDEhZjrsq+OqQ7b
 j2THTkZc
 =2RPV
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.57. Sean Chittenden <seanc@FreeBSD.org>

 pub  1024D/EE278A28 2004-02-08 Sean Chittenden <sean@chittenden.org>
      Key fingerprint = E41F F441 7E91 6CBA 1844  65CF B939 3C78 EE27 8A28
 sub  2048g/55321853 2004-02-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEAlrEIRBACQ1ZZIej0e8esRdDxmuSv96bv1NTDBaEx7P649JM8a3afUvnQl
 JkA/ryZsKAnw1OeIK907Cs5HdaG1lD9ttpQolG5ZN23K01CuHUvq6yY+evwDV31D
 rKwYfALKfdhtAaymxM7RRsNNV8OkXLg0SEtBit4lbdY79vqiVC3PeWYvIwCgyOlb
 7dw3f2mNtm280LybDSjn5KcD/2gWssJVtQgssnCi0Jto8csULw4OKyJHvXX06Qkf
 lnXKcCJTBMgXZf0cZpYhuyqMUZfsVJaF0lMJ85J8zD+Of3G/KwuCqW7jqpom0zw9
 mgsmhZ1rZCbf4cG1orpGSSfmsi5IFoe+mWEJgHwIKlLYd/XDfT1q81swa2AlcjbE
 Pod+A/0cNSOWz4rj1ZjcxYsxg0sZES5eFEHfIJ+5g3yMbNPcvbQhlSClgDD1Z46p
 6bEZA4+vL2kJH+29E1Q0M6H4OB2rY/Co5TypocuazZR1kwkJY+bQtFqPrcCm67Er
 GYl3qcbtV8Wgn153k6DnMUc7by2iTrJiRjWw4LNVhRZn3/dj8LQlU2VhbiBDaGl0
 dGVuZGVuIDxzZWFuQGNoaXR0ZW5kZW4ub3JnPoheBBMRAgAeBQJAJaxCAhsDBgsJ
 CAcDAgMVAgMDFgIBAh4BAheAAAoJELk5PHjuJ4ooG+EAoJP+RzGsCHKYGaLhok0/
 B0hBnIKtAJ0YTlDINuquFtqFTeZgwTUg4jeHFbkCDQRAJaxTEAgAqKA+B8+oo31g
 N7Q6uw1rR5F6M2fFBwPrYU9w6bM7qX6e/oy3epL8BgtzdlHyzcux/hLGDHGP6mku
 lwH5wGSjqfbk3guI1ogl+e0EjblIeUEAA1R/k2o8xt/HINhXiCjQhY6AJL9cljGz
 NQY/ecR9d4HEvjc+Ticgyt4h6WSGMTpjjY+Y0bWrxsXi5ZAsCNYEuRgdaRM52aXR
 gGkSqMBOKSKAPGc35Jh4nzvPSKjXmkXutCnPNcO+qPoro5j2Dx53ZkfB7Raj6CiY
 C8VQ8PDEpjELTq8fuOqqrl911RDYAOECWEqyim78qROuhgq5750w1CJj3K8o2FDE
 Qap5jNPiUwADBQf/bk9Es1QDyDTPLC7Look1OS50vhotrHce7P+uab++khm03ajq
 XmNuTYifQY0kgzzEBaELw4+isBf1NV1vvPK9P6k6FCx+1mcNYzItRLBo15MtcXlB
 IqkD3v/BnhVgT0PqJT6jO8glKCmhEq+GurXqydIfEzWCbz0+snVK769Q9rJHHUf8
 icDKfUI1m7javdnXVrpA1kKZM8Omis+BfO17XDBLYZuVW5rAJDzG42YM8H1mrqBa
 GL806X/3i55d2RfgrljiZvXBpdOZRnM21w6hxNuj3OaVxqrQn9hOgzBcVdSZWc9b
 vxpmZ2j1vx7i4xNq5dzcBqxMKDcAcwomLWgjHohJBBgRAgAJBQJAJaxTAhsMAAoJ
 ELk5PHjuJ4oob8sAoI0szWtufl86pHsG0AwxjsykDS38AJ0SAW5Nr1N1HlZlrtlG
 0ev24JoBxQ==
 =yGes
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.58. Junho CHOI <cjh@FreeBSD.org>

 pub  1024D/E60260F5 2002-10-14 CHOI Junho (Work) <cjh@wdb.co.kr>
      Key fingerprint = 1369 7374 A45F F41A F3C0  07E3 4A01 C020 E602 60F5
 uid                            CHOI Junho (Personal) <cjh@kr.FreeBSD.org>
 uid                            CHOI Junho (FreeBSD) <cjh@FreeBSD.org>
 sub  1024g/04A4FDD8 2002-10-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.0 (FreeBSD)

 mQGiBD2qLwkRBADbZ6Rsv7guMTzGT9lj4eIE29vj0ZZNWFepFEqEmWK0jMLAATX0
 koXkP/qWsuGBhVHcSyZtVG+MYTwAzo5nBszx12CNL/GkEokQ/9FXi+cA3W5TJZTE
 ssMq0PPwqCB7+s/4DBmc3uI22TCOI7J26XkftuwkdihCMG/gk+cgKkzZ7wCggaBp
 02a96DwV/78wUZy9C8B6uMMD/j5jAO2HOubn5CRZrOpko3za+qVsk6yTCmq12z+t
 r9veYORoVohxVTIY+xpeHQVlOe5URTiKO0Uvu34Tl34x0BbSLBWrGU8UTMA4+hpl
 QTUK1GI1DheFPGGGxbt9w40nslRVw2Or7GA/XHexCDwx5KZpJNtO8c/MqdlzAae5
 CuYQA/9bb5T8xhamrsOFTmdLY3wPM2efnp5d3luwA2Fe3SdC5Rkoa2fDye5w7fy1
 9YX638Nw0YU6P/xmygdBjqxKs28/6evo79KAWONL0dl20pEYoj3yVz58C3YGLEFe
 p9ggrBf41MjnnMg+D7NdBOHtISfOrU3TtB/1DiGE3+QpMwuOHrQqQ0hPSSBKdW5o
 byAoUGVyc29uYWwpIDxjamhAa3IuRnJlZUJTRC5vcmc+iFkEExECABkFAj2qLwkE
 CwcDAgMVAgMDFgIBAh4BAheAAAoJEEoBwCDmAmD1SyYAn3JBBPs/6lAQ55HLjew2
 suN8XP8RAJ9OBFQhUphqmQ/shjrwbNRBsgDbc7QmQ0hPSSBKdW5obyAoRnJlZUJT
 RCkgPGNqaEBGcmVlQlNELm9yZz6IXAQTEQIAHAUCPa7Z7gIbAwQLBwMCAxUCAwMW
 AgECHgECF4AACgkQSgHAIOYCYPW9MgCeOYgOUTCIsagnCymketJwQoGBEpsAnik+
 bL1lPnomVghlMMUgU8wxB9sQtCFDSE9JIEp1bmhvIChXb3JrKSA8Y2poQHdkYi5j
 by5rcj6IXAQTEQIAHAUCPa7aJwIbAwQLBwMCAxUCAwMWAgECHgECF4AACgkQSgHA
 IOYCYPVI0gCbBZEg/a9K4BAY5HQ7wFOp6u/G+nYAnRgb4zUmf2M57dxEx2hm93pI
 aKP/uQENBD2qLxAQBADMGxA9f5QYLFnR/XZ+Hqa/YCeqFMZ3hC4KnjWBDDXfI0Cv
 HMLBIW5027NPIDeN95998T5YJPDm1TY5Cort72CTDS3eIfoG0iGwIzzLfXrZB7Zc
 1BukNV5NMFeKPO7pX6k4R0aQr0SQUmcdYD7t6V/M4xswVOwcECk/W9BuGA/9NwAD
 BwQAy8LmYyssQdjImAASQABcpdOua5orv0ojYMu+edGmjd0WqhXToUHcDfQgL6YA
 kO/4g37ysvGwlpj8U7cZwabMO/zwnryyOEeGEA+5aCsji4VRZHOkdflcuBOXj0nR
 9yHmPFfwWTxLtV9ajLCP4vXqKPrKciS8SbuLYzvx+lnUiCqIRgQYEQIABgUCPaov
 EAAKCRBKAcAg5gJg9eZZAJ90E4gu6VACob81uH3MxWmgjpG2iwCfeNTe1Wz7EO3K
 z54TjDmC4biJg2M=
 =g8A3
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.59. Crist J. Clark <cjc@FreeBSD.org>

 pub  1024D/FE886AD3 2002-01-25 Crist J. Clark <cjclark@jhu.edu>
      Key fingerprint = F04E CCD7 3834 72C2 707F  0A8F 259F 8F4B FE88 6AD3
 uid                            Crist J. Clark <cjclark@alum.mit.edu>
 uid                            Crist J. Clark <cjc@freebsd.org>
 sub  1024g/9B6BAB99 2002-01-25

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDxRQfMRBACvHk6znTM5boH4k+2+anGxRuPxPPIJgo6Ny385v60FtJjwLwDh
 9LwvZZjpjXi7MM/0FRfUE4bqzrdBtUm6XXGC8v/FTH72TemXR54yr2zuCTcX3jML
 e7wjrO0SO1cttASSeb8OsVQEqiMT4VRm94AYdQvS8bNxbqlog9PYmhh6lwCgwDYl
 Br/IhYSKQTugPEb8nSyP3e0D/izp3mt4NXcULIp0PZFpvnGZAMLq8moZ3cYa+8nM
 kRCWd/1/94lCd1YM8f3lQsaEvRuWaw7rT1ENknSb5TZnEMsTvV03CM4DMzH63Zde
 wgl8Xne5lF/WyiSsjUeSkmvCExFA83fz/Cv8/fk6K2O2Ajo0b33Rb7WLH/gb4U4s
 9ZkEA/48XB6/s0vGFVnELRSXbc6wCHbnhG0/58ewSbJ2XjyIFFFmeqIF2bpLhuRT
 YTBz3styfrjeAqsi9t4gtcEK3vyvF83ql5b23u5/V/+O/ZLwk3kceYmjM0mbETil
 FajrLZjaWXpTRQauL/tsqxItBI4BNuTvnh9bizQY8V7xzAgMwLQlQ3Jpc3QgSi4g
 Q2xhcmsgPGNqY2xhcmtAYWx1bS5taXQuZWR1PohXBBMRAgAXBQI8UUHzBQsHCgME
 AxUDAgMWAgECF4AACgkQJZ+PS/6IatMaGgCgqdklRK39OoUma5sl44pEl7R3GhAA
 n1680hBnTGdIR4wxFY39uX9zK708tCBDcmlzdCBKLiBDbGFyayA8Y2pjQGZyZWVi
 c2Qub3JnPohXBBMRAgAXBQI8UUKgBQsHCgMEAxUDAgMWAgECF4AACgkQJZ+PS/6I
 atPX0wCghHE+X/oyrMbMrCsdwubBf1WudnAAn2WHoVNZpzgMck2MhFdwa/1rAJI1
 tCBDcmlzdCBKLiBDbGFyayA8Y2pjbGFya0BqaHUuZWR1PohXBBMRAgAXBQI8UULc
 BQsHCgMEAxUDAgMWAgECF4AACgkQJZ+PS/6IatOKKACgsnfy7ZCxEWmdnY+c9KLm
 x0V1Zy0An34Ky4kzHxDYDTIoO6XRS48+/aljuQENBDxRQfoQBADouiAUldDORJkG
 K7fN81SWvocuySMOL/dEv6UQnBgR4lmjmaLog3QMbGIsJqiPRLDDS3PMkYf1dgDy
 6hPmMkWF/xd13Vpk4S5sIjrqTBGoE9f0SPbcDPIjRj+htXFcI+qvhvdceYi24Zvs
 xGX90jb+fimZdrJNtobfEqJaYOkrDwADBQQAsCwtAczuP/aM624+UYBrNMCmHpRS
 ZAOAnp7Hz83GafkWynaNRDYan2KsBrZJmbZ3MJ6kyUj6k37Keh1c7pR5DsY202on
 9haB3lTZv+j2QooPyj9Ityd985eqiRwAMBuOrpaCpot7zYlwiG/Lx/0P00RZ+Jdz
 hyidSKrsudGAp0OIRgQYEQIABgUCPFFB+gAKCRAln49L/ohq06htAKC7SFr0uQmS
 9fjEOFsF9oPMMxgFwQCgjvMA6reNmNAm0i6ycFh3QVYEUic=
 =C4zW
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.60. Joe Marcus Clarke <marcus@FreeBSD.org>

 pub  1024D/FE14CF87 2002-03-04 Joe Marcus Clarke (FreeBSD committer address) <marcus@FreeBSD.org>
      Key fingerprint = CC89 6407 73CC 0286 28E4  AFB9 6F68 8F8A FE14 CF87
 uid                            Joe Marcus Clarke <marcus@marcuscom.com>
 sub  1024g/B9ACE4D2 2002-03-04

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDyDmj4RBADa/Icz5Xl+cJUGNxC/tWgXWqcA9VA8GN+PeqKhXS0BnVHntdsQ
 xbpFUUKK4ld0Zex/Rec1jgC/ikExJHHIee8ZVcHqP+tsWexi83/ZvEdzI95diBp2
 Is5fYp8P8hdIBNQSOoc1jVYrTJUaZgJK2uBzbkh/WbipwsQbueRzXqPORwCgsPNr
 StLzqOpjrA7FdUz/JVQf5+8D/1SiKAOFiW4TxY+fS09lqiLs3mbXjvw23iQwLxje
 4vBd4+b9iAUWOsSretSKv6OE9ZlD4FYea8HmMgEkuKfXGc8GvTq4J1uHZ0gcVbrB
 GmxAUBPPaAENYEJfJf7dcysKVAl14ZQVIvzAGJAZHGuegD7uekGKnOEA61R3ze4a
 M2zNA/96I77l0qiMc6J7gXmiD5uxC7FsSCFj5sqTYMgBqzIYEZjU/tTUbth84xcR
 i4X0WNkaILqq1mOcBfmzQMvzG1n1CydmJU6iF1ewle6cIui9TQYg5CESrJF7xid4
 vVXRz+xi6hc1+0bSaoJa3sfpNrSSr0lKGdWHZozWdQjOvTMCXbQoSm9lIE1hcmN1
 cyBDbGFya2UgPG1hcmN1c0BtYXJjdXNjb20uY29tPohXBBMRAgAXBQI8g5o+BQsH
 CgMEAxUDAgMWAgECF4AACgkQb2iPiv4Uz4c6rgCgg7XXmcYqcIlJdDl0aGU8r0Dl
 kfYAn3W4oHUReFhATFkj2d+7zu+Rsu2MtEJKb2UgTWFyY3VzIENsYXJrZSAoRnJl
 ZUJTRCBjb21taXR0ZXIgYWRkcmVzcykgPG1hcmN1c0BGcmVlQlNELm9yZz6IVwQT
 EQIAFwUCPK4tTQULBwoDBAMVAwIDFgIBAheAAAoJEG9oj4r+FM+H7U0AoICIVoBe
 9B8bo1lrvHh+UF7GY/WaAJ9C2mCThFrmqxCr2bCtR12UoPCPqrkBDQQ8g5pAEAQA
 qk1J4LBDLeWs6ZOkPDYYcKCSAu0qlzEf5YP/TcSeZcjJyXILgesFXcayoy1v7ILP
 QSXj4p5uzRyn0fuGqiTvajjxMZz1aSkvgGyS+gc+PDmi4SJ2N/tX2isrul8MK+NG
 eUsLuZaM1JKhgKpq9yuu3D3ELG7ESga7xsOs1V/sSd8AAwUD/20XByIlsUUC/65K
 G/DQ1WfX2gNuy5If9tSPQ6h1Lno5Hv3ow3ktybIoQSxbcBo28nA/Gzg5NFGVkkqf
 OkH2xtS6V0K/WjzsrloBHCPFiKp2yHpXfKubxl8yefQPTMj8hLwlBKrNiN1fz5/6
 29TIkEwDwrUwHxQreE7FAzPMqHORiEYEGBECAAYFAjyDmkAACgkQb2iPiv4Uz4cn
 uQCfX1zNrahRTWz/HRpF7ms8qZqzdOIAn1uuu6Jst43pDzanBHUOBzUP6ymA
 =Bu/6
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.61. Nik Clayton <nik@FreeBSD.org>

 pub  1024D/2C37E375 2000-11-09 Nik Clayton <nik@freebsd.org>
      Key fingerprint = 15B8 3FFC DDB4 34B0 AA5F  94B7 93A8 0764 2C37 E375
 uid                            Nik Clayton <nik@slashdot.org>
 uid                            Nik Clayton <nik@crf-consulting.co.uk>
 uid                            Nik Clayton <nik@ngo.org.uk>
 uid                            Nik Clayton <nik@bsdi.com>
 sub  1024g/769E298A 2000-11-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 5610 characters]
 PbUkrewAn0exWATudMNC4IQf18YvII1t4Cn8
 =9wNg
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.62. Benjamin Close <benjsc@FreeBSD.org>

 pub   1024D/4842B5B4 2002-04-10
       Key fingerprint = F00D C83D 5F7E 5561 DF91  B74D E602 CAA3 4842 B5B4
 uid                  Benjamin Simon Close <Benjamin.Close@clearchain.com>
 uid                  Benjamin Simon Close <benjsc@FreeBSD.org>
 uid                  Benjamin Simon Close <benjsc@clearchain.com>
 sub   2048g/3FA8A57E 2002-04-10

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBDy0zIgRBACh/FYaouoKpVZdsPe6buzrEmX4WcsR8iPjQVmwQ4lgsfZpWq1o
 sMhiL870bhH/79xyvnatqU1yi9+kwgE8dZu3aSOgazjx+NVOD8jES7ADXzfi20Pi
 Rvjz3svuys+vB9dIpl0LORxSTE+k3SGH9PpMb7wZMt+vFVdExYheLk9xtwCg4uCg
 ulPV+AArye1TUaKrTbSw2IsD/RZpbYly4g/eck63e3QualpecRCWHpiVshtgjz/0
 IvKxT1PXSYw2pk3WRFQ/VjBX0fh0KS22LfudVbdMfeXboj97Jw6VFToVDTNIhs6R
 olpD0RSTNH89dBRtdxijgL53lmAs7pMico2vs2h+nWKWLhv604tDs5UFbJ5BMtQn
 9se5BACNtLS3XCo9kDib4wMBPxL/9TWPAYXLAqSrJ8bwbcuVBUu5f4e/5Y5/iawh
 v3yiluQkxxuriWBkR6H9cyZPkKHWvWwOz8opx+DTBu87JdqRxBl4kqz+zCAi1Xt+
 k0kHtdH3fx8IFlk28weUX3k2re4Oxv8KuJPXv2a/pJ2Huwm1dbQpQmVuamFtaW4g
 U2ltb24gQ2xvc2UgPGJlbmpzY0BGcmVlQlNELm9yZz6IYAQTEQIAIAUCRdO57gIb
 AwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEOYCyqNIQrW0wPQAoIThGdS9li5S
 opcG4sIpSvq+LP8KAJ4l9dlSK8TGzOYQNQXtH1nG1VgVnLQ0QmVuamFtaW4gU2lt
 b24gQ2xvc2UgPEJlbmphbWluLkNsb3NlQGNsZWFyY2hhaW4uY29tPohhBBMRAgAh
 AhsDBgsJCAcDAgMVAgMDFgIBAh4BAheABQJF07qeAhkBAAoJEOYCyqNIQrW0+X8A
 nj6vcRrZAym/K50Oh7SzAjpIPPAdAJ4tb10v8+NIKlOWtlJTfymWWclrw4hGBBAR
 AgAGBQJFtrC4AAoJEOI7fnC0Z/C/9BMAoKyQtUy239PRDHv3tCArmgILCBkOAJwJ
 HQnXOY8UerFlsojuQUOXzjO9CbQsQmVuamFtaW4gU2ltb24gQ2xvc2UgPGJlbmpz
 Y0BjbGVhcmNoYWluLmNvbT6IXgQTEQIAHgUCP0XAlAIbAwYLCQgHAwIDFQIDAxYC
 AQIeAQIXgAAKCRDmAsqjSEK1tF9/AKDFyCSwKZHqpvnnb6nexV1hQv0VSwCfVk71
 pMjm3TldaUvv0qXWIM93pVKIRgQQEQIABgUCRbawugAKCRDiO35wtGfwv7P+AKCp
 Tyc8C0gvNlgXXGVC2uKYKGp4NACfd4lgKHvkWGEhkU8uKgqSZWb2lg60KkJlbmph
 bWluIFNpbW9uIENsb3NlIDxiZW5qc2NAc2VuZXQuY29tLmF1PohvBDARAgAvBQJF
 tqbCKB0gU2VuZXQgQWNjb3VudCBpcyBubyBsb25nZXIgb3duZWQgYnkgbXkACgkQ
 5gLKo0hCtbRfdgCg195mpBKyK+E//F6a5Zm8aaHl3/MAoNdFYmNi/EuNVc3q1pDw
 9H9AHAHkuQINBDy0zKQQCACQzjhHd5xdiSkXCd/LAIm5vmbMZKm658hJMOT833hb
 k4dKvdNYOkgNSVTr67vUlqt3o9aR8EDchXLvi0I/OtDFrwE0tUgoWjMC8bcSq2Hb
 uuVvxhD3ZQi0Bhy2dYijj8FGrVD+PJ3XUj4t2F1BheZ1pkar/cj+OEdgRAEnZzQS
 mjY34P73ijpwiTv60jynOFTA4dX1hHFKdi2fsl2cZOrMstvCFS1XkC/O7kZKhrM5
 v6/5fulfNNAa080lUuXfDOg9G/JsjKpmugrSutphxwILWElfiGiRfXdokFvXqbXt
 sEW0l5r9VSSqMg7UTaWJE03mEnLjb6jrTpm26z2aawYzAAMFB/9ESYyVMFCLDeRC
 tCcq3nRzMFZCYLE3l8Y17mcyx5GZGkK945jqJRcenG3xWJCqrXlHA3tbZ7+Gc4OF
 kr3BNBs3vK0CFdtVFFKJT1aiuEEXlHalRDI8eAAAkG91OKMCb7DWudK/zzNmFWTz
 oJS5ar4Ymb8g42bsfaJ4iI7GsnlgvRQk8HZJAggMdpEEXTIqOLS0L7mjYKwCHdNp
 se/DgXdFhrbfCT8QF6vZonSfDzRqm1HqGJxR8iIZQJFr+2mdrcPsXkMQ9pX2YzSn
 ucTolTlqBqES0a1RrnFuzi7QczFk/JzGHkz5O8JQFBdcK6gAxWI9p62LVvR3b05s
 mdFTJMLKiEYEGBECAAYFAjy0zKQACgkQ5gLKo0hCtbRuIgCfXvphwuXuzadBStxj
 djDr44BdiAcAoLK+kkFZqHGI0YmMDuKMtYDmU05n
 =/2rY
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.63. Tijl Coosemans <tijl@FreeBSD.org>

 pub   2048D/20A0B62B 2010-07-13
       Key fingerprint = 39AA F580 6B44 5161 9F86  ED49 7E80 92D8 20A0 B62B
 uid                  Tijl Coosemans <tijl@coosemans.org>
 uid                  Tijl Coosemans <tijl@freebsd.org>
 sub   2048g/7D71BA74 2010-07-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQMuBEw8inYRCAC0m+IcLYrq65xB7Dkdbgcftj9dec89l9efYgMQir5mB2T9FeP1
 PxsCK+RBdjaqNpDfKzGncJQgzRmm1lPjlaU4IG+zpdw2pZlNmQm+dj+H8d99dF1S
 tWYGkNIUOIStC67ESkqG/Jfz/tRaVxYluavqz/V7JKka+ecqtcRB8FOGUKNavRHT
 uBRYplhg+SOP35VMfkUmnLNDA4XVlcSeT7JXlxQuX6x3QRAyjmWnk5a26Qsvw8WQ
 0PEV68EqyNpKUtp9DrjPj32cZQcBwe2IF0rGSEGUB7AZD1IKZXhVruVdii1rqEI3
 /vyDV/ilhIr4OM+npmZDJP4uR/DEiWN+wAnnAQCJTPG+avA2qxNpcgIGaKoB2r3U
 r+zWatUP/1P/k5XLPwgArRe4u2YCS0KECT+PYbroO24NsPrLXxoCPW8SBGKUvHWJ
 AheOffbZI3cLx3bY+e2tcYUPJOu+uuRQEOInTa+IqA5gXziTtarhMBL4P1jzFPtp
 Cw7NWIsCzIwOqRzot3xVKWNpj0NRkHM0A4w2eG7duK5i/QAqozz6IsxRu5iSCJXH
 zBfYVlatkW5pa2dZVsDQuRoh7EGypxoCvDaFoJj8Xh2YzWwvzj90wA3mzPFIbwh8
 Rq8qXW0KQMY94N21kZEMnwrafew/HFXT9gbRC0hdhCx7hc6kPyrce+em9R6he84z
 ORQP3yAxuxe/7LSneO3+DzmG+BtILbycxcaj6z8nDQgAqTVbHF7RT26U3f5tEg1T
 4uBoUBHCWQ2eIxFLa0JF8S9qhyndAn//AveJYOai78PfHCRnTro+t5g8WI0wBE9+
 XC0ZsDZCj6fCoEydEHuUQ0EHKiYEyARDRxQOcz+LlR77akX3YaIZG4aEvM4U6dhX
 LlE2Onx7skoxswyOi9m+AsFLhnwVV8BnJgEkDbUTOoMaXznwhmXxlGikYsqIlhI1
 PTmqqZv0a5qtx+6JS0aHsWohxYAVXNMUXY/E8QvNWyYMdjsNtApscfh/CPbkGbUx
 K6HK/fSPWdEs3UxpNZoS9jR4tXpQGxk/SL5w4BjSSLkt//gJPUO3/rjdgVLGUSjG
 GrQhVGlqbCBDb29zZW1hbnMgPHRpamxAZnJlZWJzZC5vcmc+iHoEExEIACICGwMG
 CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheABQJMQXT1AAoJEH6AktggoLYr+R0A/3lm
 gLXdoJSpUorg5FfBL1cF7jOfXlMfcp4DV59QUFyIAQCGAEZs1BWJnKkvSFypl/pM
 J8Sq72ELI7JztmTqSdoGC7QjVGlqbCBDb29zZW1hbnMgPHRpamxAY29vc2VtYW5z
 Lm9yZz6IfQQTEQgAJQIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AFAkxBdPYC
 GQEACgkQfoCS2CCgtiveRAD8D90DCFmTbS6TEjQUuufyL4QWqOPfg1Lx1hVOYUSf
 OEoA/RdT58l+jHRib9i5uU73QJLOJqmFj4/A9pdAI7nkz6e3uQINBEw8inYQCAD7
 4OILfjW1wNRBie7dUGpKKNSYqjhqmKjKzWnU4PPHBuFhzxiGnKwtM8hBgsKtiR3u
 teXKfn6jWggriKZpzUcgjnLw3b6N5MGSeTEdlh2DTGLEPm/2j8EHb1QEezIp9Rd6
 A4V3YZpCKvxgzV9x5z7k20XF/tlz+0Oo6JmmLWIJEXMyZHNMyLxLi5kqnTiimHmn
 /u2JjAJU07lIUk0PmCv8tU5bku0QmsYYdLyhAlTpeB/T5n208Lo6G5FnsN3tE5fP
 N3vB1C51055aaEbVuaQcUXcvg/0dBxTO5h0sibmrQqZdWLWdcLis27vGtH1yR/0T
 n8tgBqnmqXFU4rtBqdtXAAMFB/0efCK8VYnJBzHjzXOj9Zs7TQMDqf3SZyMA05Us
 KjOxWI4W1WmoN9s0X/99q+7nfzDbD4VB16qR70u72QYIqhaJ8xdMdnWeQS8VYnxW
 Kx7tnkUzKAf2xYM5BAGkr+V8EIjDmCAGXCbX5xz9oA83I/LGRXMzWs1GRt2tHAOf
 gzEk9PXsX+LhDMrCx6cgDSzbAAByYh1VuIOVE06AKOH7Yvizl5M3E03O/b8qszTB
 sD8sHqj39ShXJCXTgT+JNxWhXw4+xSo3SGIQfSwaGemsS/2VIWZ11a2KNozZM/rY
 +vmMth9Mi9G6/kXXMo3gG6UVgoX8z1ji1/sOECRVpJbUyHHSiGEEGBEIAAkFAkw8
 inYCGwwACgkQfoCS2CCgtivrMwEAiTl/f9HIMpFwzdUSmGwWOzdlAZMDKy5q+I7i
 e6gXZYsA/idi8cKOdjNsakA7+KFPNPqg3a3mH8NiZv7CIMeb9kfq
 =JjyN
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.64. Raphael Kubo da Costa <rakuco@FreeBSD.org>

 pub   4096R/18DCEED6 2011-10-03
       Key fingerprint = 6911 54FE BA6E 6106 5789  7099 8DD0 7D21 18DC EED6
 uid                  Raphael Kubo da Costa (Personal key) <rakuco@FreeBSD.org>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBE6JE6gBEADepD890SrcOODbfeymiA8jKbWIpTKfvbzEB6u6wpRck1VLmXCq
 DlZNju0M4GkILWp9fP4gBsarYrN3YmNP4H/hpBRIJou5hfPsggCs/q2go6bAPN4g
 VsJ4IlPXlGDDsMGDMpjqUFmpc911DOPC/b0d0Jzk+BX+ViAKP6AJt/jNcJgQQ1IZ
 UpQCU31yVdQhO4LjY6KXJgdb9jt5hxgeW75L/eBw802rhLBAMTy6VJBjgR+rKQeY
 thElDWbs5SlDoADb9HmEx7ws2vTn5jr+6UQAwPqO/sZBd3QunjNh8QPqC16s8+qV
 cPpV6S0mfm40o1dxN7GOOx6UTYc6jS+9cV+HRwNjm+DwFmHf+yeIVZvmYLuQ5jg4
 a8Vo7Lm4up3nHS/lLBi8pt14D7tctSww4eEDdi3ofbbV9XmPsEkhpEsCeSyMIh1+
 nIpcE9LAl7LF1BeenyQDekqstBeM8FNCf5rxl/dMi1B5nkTurOaF8F3Ntg0DhNWR
 2vMEWVAA9WKu/xl9z0OeOiXfUUis7ntUqLCjtUU6/3gRc6JVSJOXQzfsBqgv452N
 KdOSrZ0LLv7nIL63vuIMOAWEoijEnpvSTYCcCIqsAf/aFUwEp85Ag89isZk3JY7G
 M9XExA7bh0eujWMKimr+VHfuZP7jHLoJ8bQg0J9tJ0cVSgdRj9c3IMM2cwARAQAB
 tDlSYXBoYWVsIEt1Ym8gZGEgQ29zdGEgKFBlcnNvbmFsIGtleSkgPHJha3Vjb0BG
 cmVlQlNELm9yZz6JAjgEEwECACIFAk6JE6gCGy8GCwkIBwMCBhUIAgkKCwQWAgMB
 Ah4BAheAAAoJEI3QfSEY3O7WufIP/R61I9pGVqIFW7zDFvt2Pu+kowInTzqePjdI
 lxRe4a0Rz7KY7Ss/vHcqEO+gR+isLL06kuC7CAOwP7keqV45MD5fEWhub5HLwOQt
 25f5GqWiVd2qCR33zWNPA/COIh7k0sqZTrEnu1rObVeLnk8nHsgYyQHnnHcuFJzw
 M29146oDZ7x4wEcKJk3v5qRISt4has4mocHyksgQ1dgPnEP99VxYXOyKI498yJ4l
 5RzgxHNos7u2X1zueLHp0tcY8p1Bga5ULQ64h6l2RUj9JleVTfjS5ukBmNcXkCLe
 pVIblCNes66Nc0/0BqjVp5PSoVfIUYpUMRAJsO+818NP3RtFh8mfVCKi4bKIp6kP
 Pj2MC8sTa7X9JwFsBkHXYa1ETf5f8yQoLSorRV9sWNhpItHVQ5+OWkCeH8Dmmkjn
 OTBSRqUQCqk7dv68N3vMZKLo7DYuTKHsRNpK2tPrhsL3kEXSHupTHHlgqQmwNhJo
 vZ+4SUwWWAzEDL51wl+BwDYx9Adp09BF+ZpBksaefLu+boPE0ywmyM/lYDytjN8f
 72JEIciCk7zeLcxvDQ8LkEn4F8Oinivze64KwGUSmnOcIsFDDXaLvS/fmi82p8g5
 2G4fYepJUXRshbFECxc7ByjuvlBnONerxII2iJluYfQOhSJ9gy1c05TtNG8yLFrD
 Ga+xNN6yiQIcBBABAgAGBQJOiSpAAAoJEPs3PUX4s20oD1YP/jWpI1OnZiyNJW3O
 nWAdQxIDCnVL5FajHZVSoj+XQc0kBdUXFYsZDN4CMU/OUbNAW2PPctsIgkfFGvP4
 OJTKE9Hjn7NzRMbLaFaRLPEV8rDODkXRz9MnlA3GUeuMONqtSHpgdKcNwoct/KYA
 j3viWP/uWJosGrXVA7GAyyAZQUaGqlK7983RmkfA90gnlEhAwNoKUhVPTydXNa+m
 UWcAkTiKOHEYHttB2bXj29cleVm1I3sEG5ZZ4Nz2V07F050vPeYN5U/BpUKGXogY
 VXK7yXztSJWxtgd8aTP2kiqf3b26KSAiEW1ov/4OlRBBaFZI0McHLTjy1LPV3noZ
 HYgoObnqjVuuPu0RLoJqbD1u74hMXi4pGR/Q0BTmUTYklsbSg7iH9JbB0Q6Vb938
 lh860kAfTjoB6pnHNsTKnT8+OhYOB4hFveDuRkpJBdmy70p6KXwhL+oeQztNGFc9
 XXuqZX7HH+cAOX2xCmTu/pNg4XdgUddwTo9aZhGciBSmuuz+NyHLkFW+tOiKKCgz
 YPLVkDJP1h/206YLVGjEomKiSpNDwWmq21eaWMkpVROccXUJqrzQ9lq33dmMlfgX
 Km7nxDBZeCCenTvwhVMrP5zNMi387G5z7zL+AmsR9j9JRtfnjgehyPqFVv4qEi+F
 CnnWxLMKpuIcZBJTJj4DevmqihGS
 =FjO0
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.65. Bruce Cran <brucec@FreeBSD.org>

 pub   2048R/6AF6F99E 2010-01-29
       Key fingerprint = 9A3C AE57 2706 B0E3 4B8A  8374 5787 A72B 6AF6 F99E
 uid                  Bruce Cran <brucec@FreeBSD.org>
 uid                  Bruce Cran <bruce@cran.org.uk>
 sub   2048R/1D665CEE 2010-01-29

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEti1ioBCACz7CnTd0jZAT+OOYC9dRgBFMw/n/rI5tP0Y9QkQ6452oc0jYWC
 iHxdsV0YYAEoa1dl8x6aTnzOw41LXxZN4dllj537cf6BW+/gHTiPRReI5nZkWqWw
 tI6rG1MGK9VRvRVpyXgENA1f2qcA7zRmEmlomFtll2jviwXZ+dIifPcznuKvZext
 rB1XilX4UMS1gWIyQX1XZqNsokpD8itfkyyNLJu1Jjn3vlka0iwWbgu6Wb/LSzCg
 NKg0azcyxVDSRY7gEyasNgOKYJQxGYww7q72PE7lysgOjBnZHi5v9t+1oQfJsVYH
 8iyf3/V/y7J9NGPAAUtzIt3vPK7ISG6xxko7ABEBAAG0HkJydWNlIENyYW4gPGJy
 dWNlQGNyYW4ub3JnLnVrPokBOAQTAQIAIgUCS2LWKgIbAwYLCQgHAwIGFQgCCQoL
 BBYCAwECHgECF4AACgkQV4enK2r2+Z7m4wf+KfpgT8d0t7ecWL9UGqy2XlyqVu47
 0SQ9WQA51MBtbHtLBXZIJtSB55OJRwPoWD7UyY0jHfa7CdltP1munjpF7CGXY6dj
 J3MnAdGMGIvs+dpUHP7g1T5nIBJItQyNJS/mulABsMGes9bIFY3Mk3ulEZI92bMg
 VwjVs9/MJi9rkI/wN38sZ5nxtFp95Lot95E/f1nbIMas6ybn6HB83n+XO5hgk3wm
 k7SmNuTO1MI9WzfRLOXS7OhLA6ldXOgd9bYUEmaWqiHg2CB5HC8PsTxbs27Qzgyr
 FKBTYsHZYcusJ3EHJhwngD5tP+SjZYqe7Of9/mnhKgh0I1DF1YCSy5tLn7QfQnJ1
 Y2UgQ3JhbiA8YnJ1Y2VjQEZyZWVCU0Qub3JnPokBOAQTAQIAIgUCS2LWWwIbAwYL
 CQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQV4enK2r2+Z5aAAf9E+slz3MljqfM
 zcF97g6oKMEIFHaXlWraELeJ2qasom/M9AayjrAhB69ADTX/0GeGuwa8SqU/J9qY
 IDpH0Nr9fyp7jiTCsXU4jcvnetuhAbuIcyjNBBmgDcINFsA3aJtllpnePzJNvgdm
 rFpCqvdBFrV2+B12lvF1E9WAIzKJj04NEMt91f3DiMmBRcL00X4XToXT0EhPuHow
 Uls2XcbvMMRwWRT9EYsiPWRT+o6IlKP7qB8uS7vOIjzGRRVXBIoB8rnOR3XZ9aB6
 P55fzmpQNz3HravpuZCP6RBfJCLRvgqdQwQF+xFJnyxGJU+Ts9vZc/0g/xwj+fl2
 Raa+oIWBFbkBDQRLYtYqAQgAwkPY0gb+61cDkFdFWBumgdRHcXCjtWfxcCpFNKuB
 E8ELyj1ER0YNX03PzgiNOz3ywKTKG00sa1RE3dchBILQbk4DG1xGRgUZzU+SDJoA
 UgdPinyxbKa1ACNvtieoDnVVbWXafDgySfxj+cLIxH9y+ORUTGNZ01Ij6FgtfJmG
 Qs63ilWHE/m4k3zsYCfc4N/dMBtlkNjF7UN3Pk1cVvOHDrXsenUr9Ab+r983MlgU
 LigZ2M7zwJzP4nUSKhAw/uIp8wTPAmWe2C89H4SjMUOSxUHAN9tpgwWPPX1SrajA
 F610KysdtKXj4Nb3xnlaIF5k+8S5O0rwbQ0jEqG/tQCqSwARAQABiQEfBBgBAgAJ
 BQJLYtYqAhsMAAoJEFeHpytq9vme1voIAJmo2Td1/ne2DpKK9dSX025pE2lFr2B9
 P7JyW69s2LEo5EQBh4ZdCABud+p+1YwFedCb3O1N9+AVpxTbV6DZzzoSXQOgR/EN
 5tD2/dCDE0c61IX08KaG3NSTZ+vSxbbFJOhNYOh8wQ1cBzEEWfFw2+fH65jxQ+wX
 kuQwJfoHNlxDPwoxkRI8iHUM1i8t4g6aGAV3yec73FDFB+2rgs/Exr9AK0WgpaPI
 wIx2FcHlOoOfxvLYup4BqBTMCMD0rvdnXH5L5Q9ZxNtM4nXiRin5VGBMdhk2T1JB
 6k0ky+QKtYoxvRt9055XWPSHiOEBlu8ec7EKb7liplIZVoIdpIh2bgs=
 =XNzi
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.66. Frederic Culot <culot@FreeBSD.org>

 pub   1024D/34876C5B 2006-08-26
       Key fingerprint = 50EE CE94 E43E BA85 CB67  262B B739 1A26 3487 6C5B
 uid                  Frederic Culot <culot@FreeBSD.org>
 uid                  Frederic Culot <frederic@culot.org>
 sub   2048g/F1EF901F 2006-08-26

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBETwuAsRBACaptn8vJ5o5RZkWQUvr3EpBW91+hZtYLM+oBpk6+BayiPAW02f
 aAP6XTrl3GE6hK5+lZWMdxeu733Ukq72cLwbSNefpXi1A9/7IU+bsUWKgSRL/O4z
 HQziOHx+UgFr+uWdKbIssFmIPSJbsI0IOZV1p1mLVDCz97QG8JvyJA7AEwCg7XLC
 0Rsiev0R71ErTCHmuZXoVt0D/ilNo5WJyA8mQ7wmfQsRUnV+GXXOYk2OdhrfqPnh
 B4WVqBd/duf7Hn8TzGF+ee90N7PjlOXa7VH8wQcKKSNUDGWcV++xJQ/ZxeB7g2Ya
 R+JeQy64fVu2+Zi8IehUt96k85mVZtb09J9C+t4+isRsZUb+A/tlcMLlYxcPSaai
 vGA+A/sH2RRyDJFTMGfqmpRSpm716mgWE1Oyk8rjqpRLOjlrgmORHNSSIawSpAHs
 PQrC5ouBWFRe6pCBLpd+xcvaqmnkVBYrVZFmI2ElTYWwviF8aQ7HHP7TVek4EZoE
 xjQ2YDxKlFN287s9yc8HXIiPcwLO6yPhDa1ZLEoebGLDp+nHI7QjRnJlZGVyaWMg
 Q3Vsb3QgPGZyZWRlcmljQGN1bG90Lm9yZz6IYAQTEQIAIAUCRPC4CwIbAwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJELc5GiY0h2xbJ9wAoKf/6b8O9hlrKE6kFfr1
 h4FuwX/XAJ49WDVUxcf+jFYluXwHmzRW8biSarQiRnJlZGVyaWMgQ3Vsb3QgPGN1
 bG90QEZyZWVCU0Qub3JnPohiBBMRAgAiBQJMuXzFAhsDBgsJCAcDAgYVCAIJCgsE
 FgIDAQIeAQIXgAAKCRC3ORomNIdsW/A0AKDVBYK/Y91Wz31ws7Rxy7/LpvL6DgCg
 4jNUurzgT1i0vFuBfPLQx5LEZSe5Ag0ERPC4GBAIAJFsfHsMTmxdNfKtzMpGOJF0
 dLMLwwjPyKkVPtZZ5LZclo+7jjyg7dAYvY05o2ppQ1TH0LjTV333qWItSbv88Dkq
 f/pn8tS0/for45dVnuJbTAkkc+khPHCJ08iZsl/X1IYBj3bteb1z2jZr6M2JEQyN
 qUbbuop3zDoOVMx++lsR5+Q1/+BVuJGw5SuLVhTdNOjiwta3x+eSH4Jzqfb918SB
 uiaQyPcdMGBDd1VyVkJZU2dIFp7olJbi6T+leY1+TUdvXvzmBqB/0XtQfOfc3hQb
 Te5HP9IhiAQkhe9fdsOZpcAJuWS1HvKZT/Ck8UqKTWU3epzTlEN5LiTuisRiUGMA
 AwYH/3eopRoq31zWXlfWI5bETU/DDna48gzpz/P8cc0ge/7YO/sGyB3jtF3D1htI
 rS1dp7I1P8+H42vwAje18uxg1IKZeQ/ffFl29BTqWM71rALuPyXR80JjT6gggTRl
 Bj/YEVUyxD+PXG2qRBNtYOCDLUtKbFzpaGV/ViONkSfzKTNIdjyDlTp8UGWRXteI
 903NQSogGxVew/0wrlyXURoBKWZu34Y6awcvQSmDGLzWqEpVbyVofAjjtE06iIXF
 u9vd3RPua/WkTjZELE2Xs6hkxGoWfsmpnsKuMS4zZDr0olIbBtMiQGp8nbOQrJPe
 5ax09EyO4fJYj4KqY7vfHdMMjByISQQYEQIACQUCRPC4GAIbDAAKCRC3ORomNIds
 Wy+LAJ9s/SE8+ysRtHJq4zYNkOyzXpt6VACgjcPRoqpDhE0y8V+QniOWN6eJ0Ls=
 =h8ph
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.67. Aaron Dalton <aaron@FreeBSD.org>

 pub   1024D/8811D2A4 2006-06-21 [expires: 2011-06-20]
       Key fingerprint = 8DE0 3CBB 3692 992F 53EF  ACC7 BE56 0A4D 8811 D2A4
 uid                  Aaron Dalton <aaron@freebsd.org>
 sub   2048g/304EE8E5 2006-06-21 [expires: 2011-06-20]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBESZZ5YRBADZ18WQp9eda97kmLEVNkYUkTbWn90/9ViXP5lWhWDvdIwXXa+S
 byVbZI75QkYrvhhyDQPwK2pwF3v/nGaBhQvO666uWWyqBAC+FTjc6GQ/tVTe67Pp
 dBVlY3X2QadAIWOYHFWNhG58jAXDnuz9po/w/h5t/6wayVElamu/jPBwBwCg48VZ
 4q1oQ7M474YPBsyLfmkLEu8EAJwdgos/BxJ0a39PFtI768+6SS4e+B7qt5UDd30l
 87rvKoW3gXuf4Vn00Y8m+aK+mUjsWeQfDCF6Kj7/ecGNSkfvwmsEDnRMujyapX6J
 wuJ6DzKgrc3zEBXVK5g+JBrSZDGetkdl8jndG0lmxIqxqnx1R+uxiWNs9NAdeP1P
 F7vCBADAPoKaAEW0LlsOE0zIylP5e+LTBd6MQeZ8zISlNqMHDX9F174Fo4CFH/pI
 nW588yf/ChScuONLPIPbMBkvoC34yLEGluvjZov0cjySqzcTN/TkZ7iH1NrkYe71
 /z0Pe6jWY8p4KjK6C6dKok8b1ZI/btmJyuv6bkTzM5kQlxg43bQgQWFyb24gRGFs
 dG9uIDxhYXJvbkBmcmVlYnNkLm9yZz6IZgQTEQIAJgUCRJlnlgIbIwUJCWYBgAYL
 CQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEL5WCk2IEdKkTFIAoJwahC11/B2TXIk8
 9PioqX0c5nU5AJ0YGkpXIzDzF6QskMWWQq64fMuE6rkCDQREmWehEAgAzFoPIPXW
 +sMFJs/DzCYMzHglYmNzHr8wCfvNq3hiiHUfk9EtcUaMnVI6TMkoEEF4mXMpf7oc
 uCjU0+CZMf2GV+bLkxs2rNePyjzTuoig1vsl9RFA+1tMfLrUsUKwoPjLZUbHHApl
 S1x4k+TaLanT+tSQar//WNuA5JrmxRXSyYXu/2y5VSi+niaNKupNYXfqr53SuW2J
 xh90I90hzgBzQypWNNDEIN1c/lkgIvWm7RbbBliX9Y23iUeFkzmLbOUcpLSy3zj3
 9I3eCshQdFv5UT54N8rMAg6hGC5jfeqy4mVpMLWst3Y/Od+DBv/F9xnaquGW7LYp
 Pz+H4fJzdC79hwADBQf/XyMpsvO4z1N+8DaVybwMedLd4ExSkIAsAI3MTS1mtNu9
 mFm9GQULWvUH1YXBFnVVidibc7zdTwVEAPFhc/uZ5unxqzbUAj5whkCBUF53ZpVv
 nsskZZ3aUEh4hEM6S1t1kc7+HptpMgaSxEcjy+ylybMEzBQ14Mh38sEavfoeDvfb
 aP1AtLQh/+ehQZHeA6px3PvdDeevM6zLoAY6yEKtd5QaSrvhIuP91HKeQjPgM8yy
 IZTWM050axPzKZOCf2VsB78QUNVGcfFrbScleBvaVbdOh/ZgxGOgD7LOhhgivV1m
 dLQ+3W66/GuUVDHap5hdzPuoUgFTodlzilfqjpaekohPBBgRAgAPBQJEmWehAhsM
 BQkJZgGAAAoJEL5WCk2IEdKkNGoAoMBfaOMRp7+OtWsx8pkGGlFszVCDAKC0rEFY
 lBcUW4xcel1cl7I40JK+lQ==
 =bsX2
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.68. Baptiste Daroussin <bapt@FreeBSD.org>

 pub   1024D/49A4E84C 2008-11-19
       Key fingerprint = A14B A5FC B860 86DE 73E2  B24C F244 ED31 49A4 E84C
 uid                  Baptiste Daroussin <bapt@etoilebsd.net>
 uid                  Baptiste Daroussin <baptiste.daroussin@gmail.com>
 uid                  Baptiste Daroussin <bapt@FreeBSD.org>
 sub   2048g/54AB46B4 2008-11-19

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEkkLyARBACYi5Qr3qvyrpp0rgqK4cAwteOZbhB3Jt2uxuzrKnKeTw3y4DrG
 lD+7wAwKmLapXFobxCmndhXNnWw1Viy+hiBN5id8c6TmLF+I4lbxL1Nmzl++ifVr
 OdOTqXH/L6kbKF80bY3zhgzR6EtH/0UjL6aXNWyLv/2l88+vx+Qrc5NhJwCgwzkS
 RbUjFKhyAxh7APNTUqV/ZfUD/3nnu/ti17KqQhiRgm6qup2ZPOOpOtlJ8J4dDFtd
 crmhH/ViE5ze8hPVTymufvLj3dWJXB3gA4CJbMmD9qQMaNJ1q7tEIe1MVNUEVop3
 4BEl0oRJyeUlT9QuVqM2GzsBeIiTikZMMpRlZOuuYwm5sbx3nrDHaiBKAkthZF0z
 l9dlA/9QdSfmViz/x7B9Oa7WfkvmAH4/nMIxaBsliNAtK6peaPFo9M03wgfh0eo0
 3JjLAVFbembVkYkA9HqqMFx7Z1W0i1WJAr5SC7gX6Pf3pQPmKIKJKJykXzIRmL6M
 boUYksuTrtZIDiz/luiEg3wVUONLe6iX18v4RzvS03F3T4HAULQxQmFwdGlzdGUg
 RGFyb3Vzc2luIDxiYXB0aXN0ZS5kYXJvdXNzaW5AZ21haWwuY29tPohgBBMRAgAg
 BQJJJC8gAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQ8kTtMUmk6EwjzQCg
 u6livnP3Mpb8zzzAvfNloYFVW6AAnRwemMVD3FRe1Rn+Ci3lfgySMDmltCVCYXB0
 aXN0ZSBEYXJvdXNzaW4gPGJhcHRARnJlZUJTRC5vcmc+iGIEExECACIFAkxO2FcC
 GwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEPJE7TFJpOhMb0YAnjOkFOYw
 8gjML7yPL7w3WNukE/XzAJ94L1XFYK7seJA4zHkMI1nTG3SZjLQnQmFwdGlzdGUg
 RGFyb3Vzc2luIDxiYXB0QGV0b2lsZWJzZC5uZXQ+iGIEExECACIFAkxO2G4CGwMG
 CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEPJE7TFJpOhMSlsAnj1fB+Mtca/J
 umANnc/GL7iWGjStAKCkEJmZyABghRDR8HxMzJEgfGYZ97kCDQRJJC8gEAgA3nSj
 7ISAocQ76ew5bSc+aW/cLqnAvWnEFOtwneahbOOrwpLRt1CtCC7bFsWnkqsFJT6N
 UFcc1dJl0D0+JMql1+uvyiBK4kLGhw/kayWqGhWVYAwul375lLxyj+Er3zGAMdLv
 vbGtg4+8vt6jpF1CvKLQzGQ3UJDlCKz3XST/tRUUFoq/5lD58wqJBOyjKgv+nU5g
 nmVJbmsNtRH8gArX1b1Mld4pnfYdMcRVpbna7Ct78GJDbvsRZnR+YlMMc7De0zd1
 /oeYo7TBc8isPRxFvdd6d6GIuDPuiK6EXZphrwzQSqG3/hp9SHgC6of9yVzP3wFi
 mrVRyyUQKVHYX21u0wADBQgAvbwssU0S6THyBaPr6S+tbTKS8is81SZ87kiUmu1J
 /qyKHXkl/aiC39DBX+a2nr9hUbtUsdYlEmWf4LMACm4jt0mPKrL2EbAUSRCVqJ0M
 c9TliU7X+ULExN7DNa7B93ux4TaGr04CjEuQxfdg3Ob1YDeJ6bzKIK8f64eB51as
 31mUaWC5Jwsj8O1XgP/yNvKi0vnJb4bBava0h2U75oU9GzeWr644KRnh2FGKwpnX
 HSqFq3opG/PR4PbSYkf2R2Eeo7Ox46iCWRrNjjgHXK/GjH8skjXoWWmD9S0h73b9
 KNDXRPD49G0P4yvNV6p08laVUl3G6A63aA1/cBqVGFsyg4hJBBgRAgAJBQJJJC8g
 AhsMAAoJEPJE7TFJpOhMLooAoI1+f30zI1xxIXjy08NLxCQv+9nbAKChzUNzc5OI
 D2+VxC1zkCRqhNa+rg==
 =NqtT
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.69. Ceri Davies <ceri@FreeBSD.org>

 pub   1024D/34B7245F 2002-03-08
       Key fingerprint = 9C88 EB05 A908 1058 A4AE  9959 A1C7 DCC1 34B7 245F
 uid                  Ceri Davies <ceri@submonkey.net>
 uid                  Ceri Davies <ceri@FreeBSD.org>
 uid                  Ceri Davies <ceri@opensolaris.org>
 sub   1024g/0C482CBC 2002-03-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 9306 characters]
 kY8idgc=
 =eKfA
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.70. Brad Davis <brd@FreeBSD.org>

 pub   1024D/ED0A754D 2005-05-14 [expires: 2014-02-21]
       Key fingerprint = 5DFD D1A6 BEEE A6D4 B3F5  4236 D362 3291 ED0A 754D
 uid                  Brad Davis <so14k@so14k.com>
 uid                  Brad Davis <brd@FreeBSD.org>
 sub   2048g/1F29D404 2005-05-14 [expires: 2014-02-21]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEKGCoMRBADKcY+c0DClCJ6cqBHMdye/IiDENT6SMUV8S1T3Iz8UDUrYjtbR
 JbM5w3ZrV3+h7HsUZaNGL6hFwxqFFQrnzBU3+BzpgTTTCC78hAX1HIoYWcfNnqjI
 zrIMjhU7wcS7hwFTdJ25eiqXSRVpoMWEpXo8JSWVTUNIuGkQlg579CZ8JwCg5alM
 xDHxzIugCp9nuFWwavjus5kD/iznJW8yKOstdRrnosBmhA8Ijq3cv1H2NfEfmloV
 nw/1g3mY0DtBUnzLGZ3uNUUZhSe82zKI1984dYSKoCCry0y/g4pCuyTswqpl/WTc
 hc9rSUFleVu05MXKoO70WSSMQGLPYLnd4VrGShz5hPtZKq2CZIQvwiAcacUwoOGJ
 J/ghA/9HD9/z7QeArsR0KfkLrZ34YH0o5e3Otz3dub3B7M6rU9MuFZ4uThhp5GHo
 0E1puC5ay0mpFlWuxikWPCwzOK7kiVuea+89iFLs6u+blUETGI3SM48FbrMKQqDh
 HZMjBWg6caY9GaWsehNxk3TuGZpA7m7Kf8Udtr9YJdRHr/HifrQcQnJhZCBEYXZp
 cyA8YnJkQEZyZWVCU0Qub3JnPohmBBMRAgAmAhsDBgsJCAcDAgQVAggDBBYCAwEC
 HgECF4AFAkmhqiMFCRCBoSAACgkQ02Iyke0KdU1jEgCfR0pvvRQA3M9Z0zM2dV6i
 YafSCb0AoJotX8m6wArtMpmii/b0QyaT+5HBiEYEExECAAYFAkL1jHAACgkQF47i
 dPgWcsWHqQCfeR97YtQHwn2yDP2k9oX6fZ9Pt60AniZRZ5BMSkyftCpR3zx6Jxl9
 9wd0tBxCcmFkIERhdmlzIDxzbzE0a0BzbzE0ay5jb20+iGQEExECACQCGwMGCwkI
 BwMCAxUCAwMWAgECHgECF4AFAkmhqigFCRCBoSAACgkQ02Iyke0KdU0iMACbBLqL
 fva236Xw2c0DMH1sf6ebiOoAoKCawBu8IV9+T0W82BFOaXzyqu6QiEwEExECAAwF
 AkKHJxkFgwPBSmoACgkQtNcQog5FH33KrQCgswgrktUdXLWjwCmnIOA7087u4ywA
 nA/Bhi+ww9U9hDQmSBohzbyRoRTCiEYEExECAAYFAkL1jHQACgkQF47idPgWcsXn
 tgCfSPZ5hwGie++UvBuozWrxv+xiv2gAnj1XiI9dmD3xucoPTbuKRB1CF1jsuQIN
 BEKGCr8QCACsjQLDvnrcRsGno7O4sUoDRj7C6tAS6ahv779OodNW03c/EL1U1thD
 qhrNvN6M/BSG+tzuJyFFnSLHfkJXxEn3XQVYcF7dV4HStotxRMSBFRFqFizf4VGX
 72mqArAeKEYW3W+mmEGJTqjRvvMxEfl2XRtGUASkSGkKvrXuq6CeJdYPgPLg6PtM
 NcQ2RlwdvOV5zutUa76zHnKZeQ/fzyR8w5HZNUxPltgjSU2NeVIOLTCakXZRWT8X
 7BnUlCUIamRLmLdxTlizW/bHIzHZ0Zl1sA/uDCea90NgV/0s8gz2HFIKnNJQ5332
 DIQvtaezFVLT+0hTyDKb/P6QRgmK3TEPAAMHB/9j3bI+ifWv4dp2NzfxXW64P3l8
 zcA1nms+EYYn0HlswwPARndsi6zlb7nF+NRluMZYkyqkNAH/0fdUQONQw8U6A4JO
 3gS9YQ++mSubtQcLCT8h+vzscS+GVoKsSl7FwuY0IP1cFx6bOuN+lNfZHU/AZDzQ
 Jyj5OfDvpupbulT92gqUakMSgmz5uqX8AbIDLnqJzJTW1UgJ5Ft7RrFVCFAufJcy
 nl7grHRf30e8lVL0KqdqsLcwWKNY8ZceBOij6OQwbnFezZlTGV5KyshCur6pyby9
 H697clLqFspFH7euqjbq2hICPOIXD/SEl99lgTTGB2LCaVhxTnjgMTttQDgciE8E
 GBECAA8CGwwFAkmhqU8FCRCBoBAACgkQ02Iyke0KdU2xNwCfQJJkClJonK//zUJ9
 vC9Jz8J4J5wAnjPFHkl5oQLsHRM0l7kB4cJDQeos
 =HfL5
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.71. Pawel Jakub Dawidek <pjd@FreeBSD.org>

 pub  1024D/B1293F34 2004-02-02 Pawel Jakub Dawidek <Pawel@Dawidek.net>
      Key fingerprint = A3A3 5B4D 9CF9 2312 0783  1B1D 168A EF5D B129 3F34
 uid                            Pawel Jakub Dawidek <pjd@FreeBSD.org>
 uid                            Pawel Jakub Dawidek <pjd@FreeBSD.pl>
 sub  2048g/3EEC50A7 2004-02-02 [expires: 2006-02-01]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEAeUYARBAD2RoYfLkSt38R06MpFesDgXVvgSb7q2GGTiMLZE7iJ8iKQU7Rx
 DkpW7EkpJ/YGPXro0KumkIGoPCsMF1eLENUhGhyMosN5Yb9Y7DXsOv3QcCKIfBlM
 P3Y+Y7By0GvSYPvYK9GZI2ZvSXyTraxB1eO/7c+aqS7wdwx3bCsVKnyzBwCg+nXQ
 izSD3wmwDYxffxN4dawiD2sD/00L95dq5XhM9nISjWJOjGsPJqyzoZZH2pemOgcq
 SeNimi0yWOWeZh/bxbjUYI5RXdBXGdwQxW6DKFU9o9NFe4se1jZcbPjuRtkbBXqz
 Mkh4kv2pvZ+rHu41kqzOZ0z+rbZld2U28R76xtx3RI4OXvJ8z01RHzAEwJ1G6s3D
 wI6iBADy+KSjJmfgP1rAcNPuwW7T7L2H9fLNTp3mmWZZDj6n4fykcwM9Jtz/K4QE
 i3GHNB2AnmR8yiPE2m87ObsKV7d8UK4WP0OLfbr7d7TZ0jDscBhlyfYgKYDFHaJH
 8O+L7df2oQU31wYEvYOP/mSTPO7F5TJZm3/Pygp/JkKnPDCnY7QlUGF3ZWwgSmFr
 dWIgRGF3aWRlayA8cGpkQEZyZWVCU0Qub3JnPohkBBMRAgAkBQJAHlGAAhsDBQkD
 wmcABgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEBaK712xKT80dOwAoNjy2Xrebr+p
 AQroKNQnIzaR2QysAKCXRA9XldUcwxSOzRJNhDktAKQbZbQkUGF3ZWwgSmFrdWIg
 RGF3aWRlayA8cGpkQEZyZWVCU0QucGw+iGQEExECACQFAkAeUbQCGwMFCQPCZwAG
 CwkIBwMCAxUCAwMWAgECHgECF4AACgkQForvXbEpPzQudACbB3QlE/GfSY+umOHI
 y+3UjdMKuGMAn2JC4vrcEPwg8XMF5iEIaEZ0tNmVtCdQYXdlbCBKYWt1YiBEYXdp
 ZGVrIDxQYXdlbEBEYXdpZGVrLm5ldD6IZAQTEQIAJAUCQB5R1AIbAwUJA8JnAAYL
 CQgHAwIDFQIDAxYCAQIeAQIXgAAKCRAWiu9dsSk/NByVAJ91gG7VGmIK1H1LyHnW
 ZPI8T7WRBwCeP644asOCGfje3+NjA0F9OHoL2z+5Ag0EQB5RhhAIALfZ2Kq/Yd1j
 X4+kdVgCQqHP9tEHjYLwGICL3Y1i+whLqUx/X+MZmt4vNZLaoaqRXhMD8A5c9tN4
 06ODB6afzS0feQE/s3j0bKRviTvUedg+CLvt9anqf092gRt1MnKAAWsw+WNqfCNI
 xsONpWWS5LL11PLyEOhxqsEvcx2IpswjG398MINFwHo7dUielCDpAPgu8tCVLpWb
 GqUBiWdqzq9jxvIS7obYUmr0VBqElP16LrcvoUs8W+AGvkfTZW3iX6yPhfpnycKy
 OnStwtO28Ud2BlRrp1YLJWv8oZcYDP5p0GyhbmCbj6qG+BrA8XbIgASFZHK65CWr
 ++Zc5tztIBMAAwUIAJVrsEErdqxbj7qdJXVebkQZLe/hr5fFOGdOwMmvNbsI2nHj
 0B/L8Gfw1v2N6K5ST68mSH5gPpDDkLqDfqY6OcN2LBhVvOdEGJv7kp8x0XK/vsbj
 jARiO6l7ZrtH4E78oiHzYK1yGFNMi6c5zpO6BXRUAVmKptL/BRu0UPRMfScyIbnP
 gT0dcOiTazJ5U9Ol+Mjk4S/YLqe/05JQvmzKzSht6E8BbgiZxwsrWB+CLpLwglbg
 f4NX+BAjApvoesbhkLOY03bSgP6CsRbL7izgVmfAHbOJk5eIYjSEIOcqIMyg3cp0
 kZI7omon6uhjl36Ad1uEwjkW7jPgCz9a62bLr3eITwQYEQIADwUCQB5RhgIbDAUJ
 A8JnAAAKCRAWiu9dsSk/NOa+AKC/grZ0DrDsO9LtCEQKwTcP7EQYBQCgsk9ZmVug
 9caBiftOC/+/0ej5qqg=
 =/cMH
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.72. Brian S. Dean <bsd@FreeBSD.org>

 pub  1024D/723BDEE9 2002-01-23 Brian S. Dean <bsd@FreeBSD.org>
      Key fingerprint = EF49 7ABE 47ED 91B3 FC3D  7EA5 4D90 2FF7 723B DEE9
 sub  1024g/4B02F876 2002-01-23

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDxOCiIRBACyyyoMk5OyGdOkR0a4fj8zPJ2AOielQ1BYv7JlIWdNeMHdQ0gj
 liTgXwDimeBnElw7sNrmdfocfwKbmX33exFPa3AkJgLflBcuH9+xE3ozgzMl6t76
 QL90PPIc24Er670NnhF7Smvubus4IdckvM24kuUTINmiuFzVwuwWdXdwvwCght6R
 HPpuFeiMZHRJAiHmu9AkKrkEAJRLmRGgdqTQ6RRIQobqGS+1grl6AsXHzKfvjx8I
 //12yrFiUcXE+167I529OW2i4ilmVjBmnwwe3750ZKBIp8OUBkMkfMuTSyCCFD22
 CX4N7D68d8eCJiCqv0jMZGnoWoMulmWzdyplcg/FhdLzUfpXLWX7/9gzy9k8hKBT
 Ou2UBACRLG7zwgKcYx4yjHhsCxuqGOeKtcfF49ghCp1s+wPsnXy8b6ZAY3wFeHC5
 LFyUsQFarizV0aeqJoOXEB296xZYPpgW6C+rajd1WVi7zhPxsfYedldX8HtGDMKm
 FRN88P75OGjMdFOYrpXTqUAJnoTUN4UynLV6WbfM7Cne0syg9rQfQnJpYW4gUy4g
 RGVhbiA8YnNkQEZyZWVCU0Qub3JnPohXBBMRAgAXBQI8TgoiBQsHCgMEAxUDAgMW
 AgECF4AACgkQTZAv93I73un4TwCfWqT0UeeEn9qstLTycDZF6oiKUusAn2dZRiNX
 06KUv2qJk2g88nUsBXgDuQENBDxOCiQQBADXY+I+CYMmiant5TBMzh5JfqhW2FXa
 aZDgi5XTVAStL6AaygeLIaVSSUUuOxiD4JB7vxHYB7pyVg71/lg5moud8NP2HNKW
 YR2mZjCQ9bHRQRqqPBTMrSHJpq10cZ6grxvVmte/oC4cI35wL8HEe2WwChZgk0tS
 YrA5PRt/UGWLLwAECwP/SxokqxcRa3lZqkpdwLgLWpyx1KNBg7wIJYLmALI0UxpS
 ezweD7OukikqZ1BYlaaWZ7N++r4sNDR9WTIv0ySNovxJnnlyo6FzD9RD7ijQbAvp
 nhpikigC+GvdnvmreMXYztc9WvFeJT/S8LGDkDHcm0ECmBDo3EA8W0+sOQsZxk2I
 RgQYEQIABgUCPE4KJAAKCRBNkC/3cjve6eroAKCCMN4s5AqvTy38BWmspFvSu90I
 IwCfTGutfs+PGUY9JJoabnnfJhfIgNA=
 =MFJO
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.73. Carl Delsey <carl@FreeBSD.org>

 pub   4096R/FB3B5D38 2013-01-15
       Key fingerprint = F0E5 3849 C6C3 668B 68A3  BCC7 6031 E963 FB3B 5D38
 uid                  Carl Delsey <carl@FreeBSD.org>
 sub   4096R/256F29D3 2013-01-15

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBFD1xcgBEAC3HQc1DEYR8DN4kwDkh3a/Ox4YxYH0ZoIprcsnAyHFmQRONidO
 UTFl5nx/r2562/N1eofQBFPt3YI0jVSiVkHKLRapoZBdZagPnEa3YH/t9e6CK5b2
 Au0Ycj66n6JVwyGwSnFYZAPmOULgWy5qMUpI0IYAyRJsRz+qa1pSMCwgibZ1gPa1
 b23if+AI1o0aIPF09KNpiQW4lNt98WKiHvIKPJh6u0fi26tqvNGUHAMeM3SmTbGZ
 m2S8l469EDPHm4MGE5wFo11IKBCB8mczg/iGzCjfj96DNyGivgDuC0Xdx/7EoP2L
 sm3batAQoa6kIUCibF3lgnEzszWfQq2O0vuA30g7tq+Eqnc611ErahGiFGKShJY+
 GfGFPuc30GFAo0hC6de7VigXDBwBV17vUM14nxwlkBNpXfca+ulkMQyIeY5U1KrC
 HQBWPV8Iq8XqjvvgIuoGeMHJrRXh/BqjE8er+rUXtyZqXD1MdxHoVpzdRopta9M9
 vfUQgB/9yjmZ3VHri5+6pENoTw9wGeLs+pOmdRXdDSbMdVf1S4qxXA7W7uqJW1LR
 Om7wkC4ezJkuubq9aqqBbgsqXwsXfSbAmuIhtYXZd5kmpQcpHbU2UVzwVWvmNvOe
 DLY/CBtsoMhMi/8XMHZ6w3x7ezj8rfzLGcoFuibKIfCO+duZAcvTtOFjfwARAQAB
 tB5DYXJsIERlbHNleSA8Y2FybEBGcmVlQlNELm9yZz6JAjgEEwECACIFAlD1xcgC
 GwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEGAx6WP7O1048HQP/R4qDGHq
 D/OdFXB6URU4Z+EvWNcG55KPR0v5/FI8ouOJBBgfEMCdtBrus/F2lMX5lcl5vyeO
 6WWwInuL8E710b+siDbawjHpzceG9/B/p3Hee6/dAOooyNrPGMmf1fI2G7o+7vcy
 SmTe2zb1kitT/IcRi6O2ieX581m+gCVdTkRmVwLG4+kG70vHPrdUCMujzUQVZ2zK
 sRjjWTXn2WLfGW/h81NsXncdJROhU9CI/DY/BVDCu1syfkopp4hdINBrSKiD3Tmn
 /9W0RRMTqwGtnuFI0rdEg68RXyOVlugHwl7AxYhxJnW9tqV1SWuCPkFADmcv+RXo
 2st1xQbFI5GzkQUMcYfYvguR3/v6YRE6U8yIP3FOUDsorpjrAGIQKPAQ8gVHEpew
 VmPm/jd5wOWDeUgG4380R9u4ymAYB/31NciA0MpSqwcNzI8hOeQeBOPGXkR4jNN2
 DsiXEQgDq/3ONkEf9c0b7ogbsXTiM2YwvLc/sR12QrOQSfrMhABz6oWNKYxLbFCs
 mIHp64BXslu1V3cewRpl8cqL3qpfc9Fi+tXzer6wpzXlJOx7nZa/vR5cNqGfZqRm
 bry1X8kRGVRxNWOTrsd5nPZcowovY2VMS/BB6/DrEVN8EELMDvcW7Z0LGe2Q8i/x
 jioRtTIwxRFNw+e+OkZWKAGIzJh2ButnbDROuQINBFD1xcgBEACjVfkC1YzwqVy5
 VyWMaMFyvKe6Ojpt8jb51+N1kf81Mc46r9W1QFMTFZ5VDEJgHabNZ2AyTnrt1sK3
 KghiznMycTvNOQHJQSGR/ANe0HiKMru0QoWz7S7nfY/ij0f28HoF0pql8qlUU+2w
 Namm7lTOCTBUpuniDDFrmuZaOcj9vZlUt9HGtLE+sbMKsdXFmPM6hyWVYX2s1i++
 zzAvFEIbsubML9QGDNl6sfK0XsmJEgBFTITiC/wtcguzszVkc1NsHPtRfga9D2Yw
 cKb+4Sog1NddMICCd/bRGgA2tAh+CP3DqstiRJ3/IRJECOaw65a40B2HRhUGyCTg
 PmVTDqlr/HKcqhLRHXWbXL1L06mj2xuTa/okaqyKdrbNAg7kIaZGf9k3aXeMngAm
 CuFpzzh4nyK2v1Mk4Fz8IXwivfR4QB1Wno93tyHH3lHc1bgM7Nj+uoYO/yM0hKco
 nKtFMRkWVkF+MbNCPqEV1LMnG01Hko1tWZLOsDyxMtUcnLuUqoafYElyO9XjyOyn
 7M+eM5lD/wJabrywdt/J+0IGSiW4b3kMZPObkCVn6uITvrbRn5yJXdSqFbWFhdZC
 KBeqvNTcnD7kpV5tRSnjft5XmeiqGC9d+RtBJnAeidRsvPtnZmlBhLFPGPiIsti/
 lhV1PMOyCBrOTLWzWhipHlNNGXpa2QARAQABiQIfBBgBAgAJBQJQ9cXIAhsMAAoJ
 EGAx6WP7O104AW0P/jxRtYXu6QL4Dv8+qYEGfQ3lL9Rd3YgQbtF4jrbwKFdf/O0r
 kxboJ5mCdXFjRdkH7/3n5X3VaonvTVPV3J2gpjLxfenLo4IQHw7yKr5XtVjevjpm
 DmXmUIPnWAvd1o8SnMwUrm4hlFvHjNyP7bOKonNnwOwWdiNSs3WeZ4MoDomPtO3e
 kRZI5tf14gj5g72AQshy/h1QmgvoWyLS2BMt96V637bomxpaUS8BYG3qucXZvXoC
 0csSt1RuH79U+QUnxJADFx6r+kgq0wCUEtHRwF2Sgjm0CTtIHlVVHpTFVnj7zTg5
 KuYxEncCydwpCsxkelVXQ62km7XbxfLNojMejYGc7w5NEF5jJ+xXvYfSh9TrfuCJ
 Pf4OF5/w8DPyIl1PWF8M5ubVPh7ryvdbcrGvrxAdY4qc8aOGVj09i0Yr4ZMkug4n
 AG2Jvw2+ksLoSpdWXAg0lzYZx7DvmvpcLRRALngu/zv2WozrCQvBMZ4lTYfjxAdN
 ywiBvWWQerzAYaxb3NIqEdY0sxPk+fNoeRH/t9Q6AOz56I/KeP1PadUEmuOoffxj
 /4UBZgCwBuHMV1yfcPLulPBFhSQu7K8IknnWMeUDK5W6jdF1IHJiz8X1a/QQTttB
 EIfympKF2+1xCR6TlNDkXxWm0Ai7DfnwdoWTGIFY2x80oU1IKLE4gFzVDWgY
 =jP+Z
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.74. Vasil Dimov <vd@FreeBSD.org>

 pub   1024D/F6C1A420 2004-12-08
       Key fingerprint = B1D5 04C6 26CC 0D20 9525  14B8 170E 923F F6C1 A420
 uid                  Vasil Dimov <vd@FreeBSD.org>
 uid                  Vasil Dimov <vd@datamax.bg>
 sub   4096g/A0148C94 2004-12-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEG3FBQRBACTPLU4+bnd9eNmB/xp17OCQdMez/lpGrFWcYRh6w0RqUEt3AAL
 o2dhleKR/RgaQtkLmNvJQnMVUkrH4dHCTDcPDF7jTUIDxxSa9YmO58Q8ITV9XrjF
 8H3bhY4xYA2VGhd13GrRYHtexGtVbBLtAex9Q+U0DBTmKO47C4cnw2cZiwCg44yq
 qn13lHY4WlhJ7WB75n6t4x8D/2tazzoHbKUZF7gxFaeeFfIDo7Qd2S4Sq0UZgy2b
 J6Api3TAkD/aL6Znh8YEn5ZyMBQzCrJEt5Fizw//nnUYKL/DMF0nVR2WeU87WnQM
 wxKSoS1qNHpXRj5y5cDHHqiOSLdDJeBb8VGb9EE9oxG13kX91F5uwRj2m+YcUl7M
 rdnoA/98GJVhBQLfCT7AIu8AeoWgMYdjUVsBQ7yZfMntrumfDqy47r2gFNEGMgRB
 oN+wITfGhRW+GPtP/TCZr0iqZkz+H1gqnuK+h0j6Jhvq9hY0kEI4O6JgaoozgvdD
 9pZEaN1q8/FiSinUOjJLfnja6RYhxv/P+3fWq7GPdK6Bt2kDlbQbVmFzaWwgRGlt
 b3YgPHZkQGRhdGFtYXguYmc+iF4EExECAB4FAkG3FBQCGwMGCwkIBwMCAxUCAwMW
 AgECHgECF4AACgkQFw6SP/bBpCD2FACfao0eHQOosHyTTKE9ClYzi4xsoowAoLZj
 QYqpUePBscVIoXHwmXcTkN9wtBxWYXNpbCBEaW1vdiA8dmRARnJlZUJTRC5vcmc+
 iGAEExECACAFAkPPwzoCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRAXDpI/
 9sGkIJwpAKDMIALqzizC9vo+vts0rxFYmPZsCACgzmPcOFXV8+xtIx5vUKQTuPiy
 sT65BA0EQbcViRAQAJbrD3+6HrMUYIlEXlkKm6QrCvwNS6JkxSjisX8rMZHfo9PS
 kGEg50sDpzrQPQm9/3SyHjmFdrvKLKoAscz1pkzqRq7/Gu3/t36vQ8DbCddwDwf0
 hAwpB7ZMUiTkPvCv8C2ZUYdvCZEiDHJSIr2jbdYjYXwU/Ry//aUNzPLoFMwmDzl1
 IjUPMLL0FufcJpVH7vJSOTxDAVTnyrXSZbKlKUWYVCxSxoHO7zFvWQ4s6QoIct3a
 ouFmZIVlySDE4G0MDshDoHOD/Z53d4Mfn41zhPYgEPAtR7g4xcvIq93MVHlFndys
 d/cSJ5uTOjcRyHmvL0KrApyXUA6f2Qek9XfXIH9bYdAtvQNvDpxKZNpIPEWIoN68
 N5en8u/RfvbacQ/WBYvoS9qMqqLmOA1oxHZwnmi0o8pA+CyUcy2hNoVmySj8Bg5w
 LSMosUHQXYEeH0hUhJIbHu96h+mcy79Mcev0u+zeXM/UN8HLAoHH2T1R6kEOVFba
 d1Ib4CY1zFFUyVwCbYH5CBDXKEND7CI11T6jmPzvX2WFOPnw9irSnafSyL/Ndebr
 VyRPQQWLe9uE2Dd/gQagxoaGX2gGVAPkJ9rEToZVtvV6g04RQSdk/31+aLepaj79
 4bvt0LJmAa24Cyh9XFC9QNieuz9QxUKD4RyJkfN5HLU7dCHRrdQXbDnFMaTHAAMH
 D/9hLUMKLDasVD+5L55mWoCep06YexBCt1QLW0uMPNun/fH4TQtVakDC2YM8bufh
 JzR1zBt8sdfpErWGqQ/+TN4P/9lzr0uDs3p/TQEzaeqEs9ChjccIUFKC/lp2xDYh
 BB7BqvsKWbvjktZ1HN7ZGHM4YIGxOK/hcQua1ov5WbJ6V9DXEmi6EguVsq2uEtQu
 V/8DwHtv4JZpPUUQmqL6VKkGPc1uLmiejjbq2aUJmbqsLMZfx7cAe4UbeR7ILaZn
 +UtQaNdNe04D5OH67E4Ntk4VaZz32uvdJ+v9Yx9TQYJ2nadWd5IuHm/KaPlFzXbk
 8vlyFZS8e4hE2Jvaopuzx3fecCg6MIQ6pc5Jxko4EAsoSaGRwGNodQWQGPc2DZxb
 Isy1BIZO5XrYXU4MzSOkhR4iJtap3UxFJaImxRBeO/z0//MI7BxDOpNw3zUDWt1w
 lAR2DY/Eyfrsx8SK/MdS4ds2j22rJdFGhuxO+uHJ+eZC70pccVRqRPMMs4uDA77r
 TpDB6VHEsqC9MTMzkw47Bt5My/qzrn/DbAAw3qkI4kPfynmYmoNwiegtD8fYD0XR
 JVlvQ7mnU0ZCHKcEh9Gjwqpg21/4kewaPxwlF1NXescn/proYpLv9uUwgVHCHVfy
 ntTKlGc22bcHlUXrdbCaC7d4Xj8SdhKER1Fl4wqmDGJdY4hJBBgRAgAJBQJBtxWJ
 AhsMAAoJEBcOkj/2waQgxQEAoN8d1808ijz/VASozvQNLAKOgEdcAKDA7JkB9MnX
 XmPkHj0KHckscg/fYw==
 =Yp1b
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.75. Roman Divacky <rdivacky@FreeBSD.org>

 pub   1024D/3DC2044C 2006-11-15
       Key fingerprint = 6B61 25CA 49BC AAC5 21A9  FA7A 2D51 23E8 3DC2 044C
 uid                  Roman Divacky <rdivacky@freebsd.org>
 sub   2048g/39BDCE16 2006-11-15

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEVa4hkRBADRcg44myl39Jv+OO9DMl2XjrS9JwguZSVjCHY2Tj4urjsEjcwf
 3ykYpJbXkK0KHHP5VTfoIp0MwoQdS4Xx5uHMHg/re5gws7KU4DXFmc9gWd1+eVXK
 PEMfWVG94qS7pG9e5aS7znglPNVUUBMKVI0VgD4fsML/92RFJl7iLFY7uwCghVfP
 952asGrNrV9T9+GBOxKUjvMD/3be37yXGBcS2f3Py6gHbv4vC0CFtfXUM6Zclz6Z
 8FGv0sYDaTW94FPkXqmcUaIjH5KMyig8Y93UquZ04stFgYkxwku1drHZb4hnuqmv
 NR4qvycMye1dMC9824+FpZkhP6ItjMcbE1PxRhQVU7dyO0dFyUlEEiMrTPhzLiJj
 aR6pA/9nW7NSJIaSnDrJ8Uq4NEIjyTidU5JCZLJJxTbSbEe5FrOSINENppVbmUzj
 CMXqyP4sHXtEA53Dl38dDjWz08A/c4dK+lwxtjDQ0NrLpXHrnqWc7tNW3XtayCiH
 KjYTUbj2kHV4Kva73zJBAlN0N+D58TfQQDisnaw/cGebU+5/ULQkUm9tYW4gRGl2
 YWNreSA8cmRpdmFja3lAZnJlZWJzZC5vcmc+iGAEExECACAFAkVa4hkCGwMGCwkI
 BwMCBBUCCAMEFgIDAQIeAQIXgAAKCRAtUSPoPcIETDXXAJ4t7ojZLL46SN/zLVTT
 4qylgoqfNACfSvpuziRIUKGLO/YdkYe1hiJqknG5Ag0ERVriIxAIAInh7G4TY8ky
 NObKXToSjpvxNhY4JQMsJ43dCHTkT6CwAes96mhAscYF3KfBcIFhv3Oj6LhyMe8l
 J9A8wcAPnYzOzjiZLrITF0IlVM1L9VT49tkvidOUMykKvluYKMmntH8fCi5pBKc8
 Y7FQ5Kc3MZ/2dge5k95mpuWmuAjAVJXKd2ONAPSRwnxplJo1kA7Bvp632TRbDEjx
 mwtg48FI4Blwu19i8rpwzRf0iCp78UF2ypoyrRqzudLXcMT4yS2yU4z4mbU91qbc
 PNCkaMP9/HyoHnIA38bs0tMUUawKCeQZgCkTV1R+V/J5uoRIMsSBGfX81RADvEB6
 HtYPrUFCYs8ABA0H/0PBej8RqZJmWU7qlpoEX4gEG8FpcsNG2RGNjuSu6l19xk1E
 RF5tYg2N3hnqioWri1t3BJn1qpHgSL+mJJRqf00c2U5XUKuxAvTWjARyqa2G+WiF
 hPc1pmE9Ty2n9XkmT7G3jidTNHXbqsjEK0OCZdLJHOkTuStUjn8Mz2PpvlZoj0Mo
 VYEE3Paet8mFH+Y/EjHKTe30RymAOQOlc3gKEP/2qkp0Zqkb0FqklLCUQvvjn37k
 /oIcF/lvmIieN/on565dggchLRWCX7dMI6QDtEnd72jwpGo30oVUC3NlKoEggcFA
 jiVbPR/F4UhBtjcB6GCiLHvREKjL17gCVwMv4mKISQQYEQIACQUCRVriIwIbDAAK
 CRAtUSPoPcIETGfTAJ4tppNp16pURW2x6Yi3GwY12/Rb9gCdGiT6lz3e0Ffo3EDl
 3I1WppEoQQw=
 =5OWm
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.76. Alexey Dokuchaev <danfe@FreeBSD.org>

 pub  1024D/3C060B44 2004-08-23 Alexey Dokuchaev <danfe@FreeBSD.org>
      Key fingerprint = D970 08A4 922C 8D63 0C19  8D27 F421 76EE 3C06 0B44
 sub  1024g/70BAE967 2004-08-23

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEEpzAURBACu7RDb0dP0oorBa7j0Do1auzG1N2wQgTMIHoo7DhspaGjvN0RJ
 /dozO04jqyWopb/cA7iWMqn/7gX9ckHrKa1ugQRb8P7AhIZNmfc0B5AOCqeGo8gi
 o9y/XBhFRS3Osxxe0j2bIoL3pk0EBjHaa477yiZyWNjq5j8rPf/h7DudtwCgx14M
 iEwmKZ4hWMzeaKYcOFTIn1UEAJtUMrBbxMxchDnIuAn3Oz3ESpGpxSDVcTHUxoIl
 3A+mizXetzWX8lmEP8GM2oM1/dRCiF+l2v5tcnBO52PT1cFst28W6Ytyf1PamIFC
 GNL2CZUz/ZVRBPEZb7CfXJYupYd1AiYNCoSyh9bOv4Fin3Uhm+Ds1n6x3yulCFyo
 PJ9pA/wOMpGwCNSpNLcfz3gG5dh7PR2rhh0D0w7jZbO/l8D/81inThfBRb7B4KIP
 v1Cl/ynm+M4XS7Fy3xjfPHbUvHY/DNr9rqI0qsGU9qTubuBO+I647tjLFem8gaue
 yESeoU4okXMPblPXh8r93JIfbmi/rMcuddblJ5kw6U/IYYGGS7QkQWxleGV5IERv
 a3VjaGFldiA8ZGFuZmVARnJlZUJTRC5vcmc+iF4EExECAB4FAkEpzAUCGwMGCwkI
 BwMCAxUCAwMWAgECHgECF4AACgkQ9CF27jwGC0QXdwCgwTxjqqG9DppWUVvfQklR
 7O7d/QoAnj9qF7prbDCAq43MQJIJ1AP6x/4UuQENBEEpzAYQBACsVmYX94l7jndx
 byPUZl5SlKLJFSTIymPGLebcdNg8rF86aq/9d8nRrkrqUWtpQtWeAZw2GZn0n/vz
 kRbmaqMaHkmdg9g9xT2qstOL0rZhCyvLWVeNYUjgkNWi7Be3yjb11RLPOanpug5z
 Rfu6I/7qjOcVEoa3cjlahdK//xleWwADBQP9EWsXY1iKSQ1k1B3N3+EEWbzuOzaH
 upo7fLwamIVuX7K95YIqOawMlhERBD8MUxfrzJkOIbVI/81g802Iq1D2Xv46hvCP
 J8oszCeFjqixsOkg3HmdUyvTHnODBHsQMoy/37r5voAElx/LXc4Dm9DSR0rSTpXh
 mUdHtM0Y6XYEcoCISQQYEQIACQUCQSnMBgIbDAAKCRD0IXbuPAYLRD9GAJ91NEgg
 OHfLL9Taov5GEDVjEaD8MACfeTqtFRD4Piuxg64CGOdNBCJ5+p4=
 =abIH
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.77. Dima Dorfman <dd@FreeBSD.org>

 pub   1024D/69FAE582 2001-09-04
       Key fingerprint = B340 8338 7DA3 4D61 7632  098E 0730 055B 69FA E582
 uid                  Dima Dorfman <dima@trit.org>
 uid                  Dima Dorfman <dima@unixfreak.org>
 uid                  Dima Dorfman <dd@freebsd.org>
 sub   2048g/65AF3B89 2003-08-19 [expires: 2005-08-18]
 sub   2048g/8DB0CF2C 2005-05-29 [expires: 2007-05-29]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBDuVKxQRBACAKP3+q7GJT2OMujrs3EgY2hdrTtLatgzpYGHsyewpckAhMPv0
 RGyVpcmXdArWQFMfBdO76TO3r6/CKRTEAAW7UieQwCqflr/qRWfaiMkqIDxll6wU
 ZdayDmuLPlp76xN7Cvy4p34lq91VNdrZ3FesMXH1xTPrnaJX4zhFEd1/QwCgnmvP
 UrU63yhExZOs0Cpo9ruLa8ED/0t2nNIoOM2cUghN6Lnh45cY1O+jnjJ4QMOi7bEs
 XwS4sIZLzZ6F07RCTTbcyRkrrh+WqX89z35ppi6PM2GZS3Zgz+W+gtzvrhhBcIHm
 0INVgsJJE8Afa2EzA2HIXsKl462Rojo8hmFXO34lCnQTe5khzLZVlUSxVpdoucvE
 ew/OA/0Sdos8xBWc5cFz7iycKpDCNjEuvMroPaFH0I9wPAX3ZBQeyHVLsUYDZKFb
 xDYlfLPfRikkxolxF+kuzqejgPMJe8aBZfPK8fIhn3IJw/5mOETGnaAPSQDCuN81
 jIQ20Dancod59Axoj53VB5bvUW49Z5lapV6rGLb78YuYxxQcUbQcRGltYSBEb3Jm
 bWFuIDxkaW1hQHRyaXQub3JnPohaBBMRAgAaBQsHCgMEAxUDAgMWAgECF4ACGQEF
 AjvcEb8ACgkQBzAFW2n65YJotACfQgyy6ccNJM++ogr4UI0QItTsSPkAoIYl/xWT
 hgWobGIOvCQzU2AV+NUgiEYEEBECAAYFAkKZC0EACgkQbDa6AvWDdPy/XgCfVqbe
 ZkvcFSken2EtrJ8I6husA2cAn2EsQdRTMlE+6A6Iwcg3gjPB6h57iFcEExECABcF
 AjvcEb4FCwcKAwQDFQMCAxYCAQIXgAAKCRAHMAVbafrlgvGXAJ0ZLXbxOz0dDh94
 SFIxkRe8KE8gVgCfcHnXtUP4oWpyHZ61Ptg/vbv+EMyIRgQTEQIABgUCQHWoBwAK
 CRDsbL+biYKsuZgQAKDQM/ws0qDgBBl78R3+bdiBepazCACfcqjBRkMtZRFL5k/T
 RD9PZHKVh4G0IURpbWEgRG9yZm1hbiA8ZGltYUB1bml4ZnJlYWsub3JnPohXBBMR
 AgAXBQI7lSsUBQsHCgMEAxUDAgMWAgECF4AACgkQBzAFW2n65YJTVQCeN8TR8YIV
 DYcq40EP6zU4UkwR1YYAnRsA1eDMeLWTtOW1DY1ajeoWY5N2iEYEEBECAAYFAkKZ
 C0QACgkQbDa6AvWDdPzaUQCfSU5c41XaVSRSnB+GbfjwWNksL8gAnjHNveKXl6s1
 bFK8FmUxZOQCVfRViEYEExECAAYFAkB1qAwACgkQ7Gy/m4mCrLkHyACgl4+J+DZB
 ugNnNwBDLvvptU8wS74AmgM/8NVgFiD+lV6xZeqqOecUPfK5tB1EaW1hIERvcmZt
 YW4gPGRkQGZyZWVic2Qub3JnPohXBBMRAgAXBQI7nKCzBQsHCgMEAxUDAgMWAgEC
 F4AACgkQBzAFW2n65YLOxgCfQb+DcmfgjgC65ecR/JGVHooiOloAn24vuwXem5o5
 5Ghiu8IOXmucO4jMiEYEEBECAAYFAkKZC0QACgkQbDa6AvWDdPxymQCfbffQmqj/
 8wkxEmExYxVeiXEUp7sAoJ+D1qNrbFeKnMo8QhzG6BqYtcuniEYEExECAAYFAkB1
 qAwACgkQ7Gy/m4mCrLl2+QCfV1iY/JPWDYMiC6SYtB5T4v7wjeYAoLqi88pkNlBo
 OwiKsYETI24p/yWhuQENBDuVKxgQBADyhmTjQD9dOI/M4X9sF+Nvt67rQvAu3j3G
 0stq7Pu8jtEdbRaz35izFxfwnY+/RHK7PXCVoAHze5yfZu6qxMxKZd/mcy+1C43Y
 WQ8C0M/pXg/YX3Qm08xTqUm7G8Cx6AS8/1s95MaSuc71E7bfMV5I6ja6+AjcMyD2
 hJiu8gewOwADBgQAl5YGq9pqpDqGYpGDFuc0Lwyu/vmEMS46EesbYC2CJGyyPpjs
 eRx/yitJe0lzURA96Kgb6qwz7OTzZOzyE/Qb+fNLwh3MOwgSbusqeHyRIC0w6ElJ
 rikyJwpmnGdPPU3Cwerp0oTHpqGRENjbcYOaaHE2iWk0wrw0869ipHnOQReITAQY
 EQIADAUCO5Ur2AUJA8JnwAAKCRAHMAVbafrlgrCeAJ4nDFNUblhVC9rNBzOMaKJA
 wqM0lACdGZS6w22ACrd0nHQcl8u34qGcy+65Ag0EP0H2xBAIAKGqfY3rPRteNSuJ
 c+0DJq+Rlp5eS5gIXI5LZ73WrSrbTuu0gx+ZTm9bz8WnAN8lM0DyJ3JkJfy0FOBR
 VLh0K/ksQ1NNwKqWrx4ZS4cKV2LMtAZe5IOsLxvYuLV4cPOrCeNZku42ehVV+n4O
 FR5UjxmXLW31mYdbo2TeNtABUCipszCvOpJ93L1FyBpAFACuBzMEO1DOMvtijXzt
 DJHDvOISFQLivOnPn9G99TPNJr4IQas7HPkCOqto8Z5kl+AbywYIWqYBJTEPp9f4
 VLwEegEGXZXRsdlIRPavwaw1i4pDT1GKEYKr84uw/MEm+LMzNiBKWIe1PjGUWmXT
 +qMC6bcAAwUIAJsJaBPPPFbO2Jhup4rkt11ea5spnACnte3FLWU3QR3Gm+9EbqHu
 BhkF1FhMcFNIzJMxbBSCPCxA6tgbw3C0frl6BtraNZDW0FThYcV+xundkZZN4zQc
 CWk8AS+A1metHy7SFldRo8ApBC8jWsUfdUw57QzKIv6lJoJhUV526pYcMwOkh824
 7aIwAD9Aq+QjMFBxvIsQSK2Spoag0/PUSi9gQ5Gs1GeqHHQ1Z93z+xn5y/fuumOW
 rb16/7b1lWYV77dOU3GqSgR3AlBqiU+zX+J7DEUs1w0HshGwZKOFYEP3RXqn7ePh
 sSQT2eHhyi5kb30Cjcah5emKagnUw+kcUnSITAQYEQIADAUCP0H2xAUJA8JnAAAK
 CRAHMAVbafrlgsEXAJwP0lOmgpEO/a658GuZPDFWDF/5WQCgicjIwyEShBkrEKX0
 Lwi7CPdGAz25Ag0EQpkMrBAIAOWN8f2FC5Ms8ivOr28XdvkDmUXEoDd9RDmJXcue
 4icY2gikIg41w2AoVAOtBO3B24kZaMIyPiprFoQg0S3HKky7uC0h6Hrwdh2BRdgb
 QSZ7X87yfBwvyKzcwv8vHM3/yQVdz0wXL9lnOJc6TZnATK/NeVJg94Hh+yk/tfOL
 Mx/NGvdJqzar9ZHP1fRxRRJNdpQfr1jO5CMCI7VQS6M/bhXJZyP3hif6BD0kg20n
 R1yv1pl7IeLl9XTfkFOrLhezCQCt9zQ3fVF1fDVi+MfDXEaikXZUrHqeEhx1QZcf
 hpTn8T7ooOrOm/Uv1EgPDsEyrFe9cwbcX70M706hitlFoUMAAwUH/2fd7p0HcUyE
 qbo0upsnVPsVrBk0ea1TKen+SI3p/QVp7QqoQoSrbQtfk0TbH+xhEv1ZI6PJsafa
 LOP3z/2ULOj6f9O4sXh4bAMuI8L9Ay4+s4RouTSYcEYr+IDnj0S7IgkHpOJraM7U
 6VE3nmoe6TutIAbkvyTVs+AVuPiBCutLKe6inIGGUM8+afdDm8rymfVyJDPpH4jm
 afsVGIXcKtGh0XdG+cJ3KzJSJp1gwFXBPmcUWuwBpD/MuAXQgkMvh6Eh5BcZ61Q/
 evjDpUENG8r+U7qvWG2ncuhrCEWj0qKp+7WFXazoxF7WRPRL76fUpckuJP0nZhYd
 pOWpB9BV7zKITwQYEQIADwUCQpkMrAIbDAUJA8JnAAAKCRAHMAVbafrlgrQ5AJsF
 SdOjEfuDShMW+extgDK2AHuqVACfSooNbyT/XUaU6pQQdj4pH0p2+u0=
 =hGAK
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.78. Bryan Drewery <bdrewery@FreeBSD.org>

 pub   4096R/3C9B0CF9 2012-04-06 [expires: 2017-04-05]
       Key fingerprint = 36FE BE99 2F52 80DF 4811  362A 6E78 2AC0 3C9B 0CF9
 uid                  Bryan Drewery <bryan@shatow.net>
 uid                  Bryan Drewery <bdrewery@gmail.com>
 uid                  Bryan Drewery <bryan@xzibition.com>
 uid                  Bryan Drewery <bdrewery@FreeBSD.org>
 sub   4096R/9E2CE2D3 2012-04-06 [expires: 2017-04-05]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 10758 characters]
 SmNk9K30XXHue6DK2khQiL6a0j4UlQ==
 =BeOM
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.79. Olivier Duchateau <olivierd@FreeBSD.org>

 pub   2048R/22431859 2012-05-28 [expires: 2017-05-27]
       Key fingerprint = C057 112A 4A27 B5F2 CD8F  6C9A FC5A 0167 2243 1859
 uid                  Olivier Duchateau <duchateau.olivier@gmail.com>
 sub   2048R/63A85BDF 2012-05-28 [expires: 2017-05-27]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE/DXkcBCADjybF75g/rvQ3dC+D7Obg8QQu8Ab4yHE4cL+wvuEh1vGxRYOYr
 4HPpN9Qyyai8Vlj3LnFMw5kt3OTF6Z3OS5IUWJgSplFxZfOIj5ESzs9qvy8qOU1F
 cE0dAOX6Q69ZPD78zngWNFv5XkrxOP2sA241/YLpXO73sYnT0ydtSZhKd0QI58Bm
 xlarUGJa4d4JTYMaeuTQ1vo54aB9NL0KMZK6GfRvnX8CuNlwGaJy9Jt4oSJ0JopK
 Yn0bpCaRGd5T2uZJ2hx1d3jtWNzhFMBl2JaG1jXXLd29q8WvaSRlP0/j/+R8ppk/
 2DAQe6gT0XEjP+np5BsYF9HoCYJ+vFtvZqgRABEBAAG0L09saXZpZXIgRHVjaGF0
 ZWF1IDxkdWNoYXRlYXUub2xpdmllckBnbWFpbC5jb20+iQE+BBMBAgAoBQJPw15H
 AhsjBQkJZgGABgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRD8WgFnIkMYWT6u
 B/4slussVLNLn7CbB7VMmo6ppCxx4BM1Mhk4stoUl5/3ENCMIG5anIMwfyG+NFK5
 Jr640U0yZcW7jX+Mg+IrGn2eWKfrPf/kyzbeMPeyDFF833EDNnliAALgni6+ZhXl
 Pct74exlzQoKkLkkDd131Cd7HUlA8XrUroibH2QyTR6upA61VMSdUXBHHdp4xD4P
 opu0Cz1kGoe99St19oFLvZPl28DUZeSLd1lAw1o3vl7RYAmI/OBz+/6lSpvHG9Zc
 aco/QNRQO38lTg9sMh5kmhIOMRBgZcGR7TFlgKcLJJbmCp+kb/jIYizKnkN8SHSt
 ab3E8ug7yaCXyvQFPHoLH1jnuQENBE/DXkcBCAC11rT2hrSvpEj9OVRwucUmKnqa
 LYcqeLNUIqy8Z76TpSSXVLXt5DH2kI7IizaQmBfkH9S6iFlJLkbOAHZ6XcjaIcBX
 VLMpBz5Mi8HUvTO+6vMFs9x/8R4+fryDNCn5wa63ktwvUZky1JFdbfZVhoV2M0AZ
 KZnvV5o8pZrzYv05TOf8H0+sYD7bNKSNa7g8dBfdBt/wVLcF7Q5aTeal/xyWhf8d
 kIZdwK4jbsYBL53cwLNNameDXAdMthKjCMndgofv6dYaHDMDh+nEwye8I7IHINxg
 t20j/eTRQB3b3gs/UWDgUHtLjEaWgLNpQx7mQQhZTcCwtZtWZOXsh6M0K40bABEB
 AAGJASUEGAECAA8FAk/DXkcCGwwFCQlmAYAACgkQ/FoBZyJDGFkJVAf/Rk/Vvs9X
 duEst9LL46h2PS078Bbk2eGH+/kigVF6tPHSWKggmB0RVzoiG0GXxv51Jta2PHZM
 Twuw7oNqsu5UZjTC1UQ77ZY42W25dkaMgDalPYNU+kd55//YIzuj9l9po+Xr2o8j
 aAWKh/nIjeAze8AMxRxHud7HWE1pE8mDG7VS5Hreu/Wxu9IA7h2UalXD3psLoVuJ
 EoZEgaQlTEJIAkcHLi51qojn1DDQ2L3JS+w4YfnPfnPtzQWu2GX3TGMAaLKqmNIF
 01Xi8q/GmlFbmBPrgIqZQS6SUb/CKLYKWyelw7dxmSkhNoXed9uqHHvHI2zMG76t
 PKHyAijtO5HocA==
 =kXkO
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.80. Bruno Ducrot <bruno@FreeBSD.org>

 pub   1024D/7F463187 2000-12-29
       Key fingerprint = 7B79 E1D6 F5A1 6614 792F  D906 899B 4D28 7F46 3187
 uid                  Ducrot Bruno (Poup Master) <ducrot@poupinou.org>
 sub   1024g/40282874 2000-12-29

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBDpMfbARBADvuMgOIlEdTWlb4XvAu1YEfCijox47muRNbkA0yb0drMwYnV05
 tZ5cOK1uVELQ+gtGK7lDS5rQ68LPpXFMVva98skkVimzgfmQiqDOXiYW4BVE1qmO
 THpb5dIpHoXqTDILTLVomf6d8Z2re+IJUNvbrBFM616wndIQqux/O5LHDwCg1Hky
 KrYDoOT1lcDgSGH6RcqSoAkEAI+D4y6JpBctutEGWNcgijLv36g09LYNeC/gD2aq
 0bS/4c44eoPkMCBBn8MM9AIsK5sfne2GuglHcUM2U82s5UbZcQl8vzcyG9AVGQGl
 aoO/duxFKPQC70/xEa26Bwjv78cVWm6hLHoMZRXvsprr3pQpuZHmzPWwwxipqXkY
 gYApA/wMrLwdewzd4yEMB5O6y9WSd+FUA/y1MS1+9epdbzPnpUszR2QKlA+XblfD
 8KdxxUjIjt6WOXEhQ0GCWfRauB0MAZHTMkA/NVnmR+pI6FSJ9LJ4s6+BoFRbKdDp
 JY6yJUZzqRgxgo7tIcpRsRuXP4zu8KYlCPL0Al3gSW2DlKYxirQwRHVjcm90IEJy
 dW5vIChQb3VwIE1hc3RlcikgPGR1Y3JvdEBwb3VwaW5vdS5vcmc+iFYEExECABYF
 AjpMfbAECwoDBAMVAwIDFgIBAheAAAoJEImbTSh/RjGHWXsAn0/3nHkOH2WxLdWl
 ANdjJDzkMLywAJwN6CBCDKSbN7OzfNHTx3XAEVUUmbkBDQQ6TH21EAQAiEIQKsg7
 Pi2k3L9fFnDDAcFgh2oL/MpHgN4kKYx2aoTr02O3rBmK3ADCIBqj3dlWMavIOuzu
 1DvmvsloIcDwsMsc846bjQq0R20VaiNz4NJqZfhS2/xYPzJo9sPTncJOGQowjv+J
 GqlkmvLVSLSzYPh7OZjdw3SxS3zFPEQg0ccAAwcD/iZIddUIenySJdgs8WIe26X5
 r34/0TlyxiwtlzefYpVHHYD8CzVhYPD+iWUpDv/10HC7c58JTxNUGyN2UGcaDNRc
 g/VJqRahYxz9LokB+vRPmCyoP8bhLkrp0fHZFnFpH4IY4WQecLBfYJZZF/K7TLLz
 O5tine3BIL/LpM0nhVWJiEYEGBECAAYFAjpMfbUACgkQiZtNKH9GMYe/7ACfTNKi
 dschnmutxCWw5fcsyqP9oYcAn0Cf7InoUX5AUFaj4dFZ4IN+9L/m
 =LTGr
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.81. Alex Dupre <ale@FreeBSD.org>

 pub  1024D/CE5F554D 1999-06-27 Alex Dupre <sysadmin@alexdupre.com>
      Key fingerprint = DE23 02EA 5927 D5A9 D793  2BA2 8115 E9D8 CE5F 554D
 uid                            Alex Dupre <ale@FreeBSD.org>
 uid                            [jpeg image of size 5544]
 uid                            Alex Dupre <ICQ:5431856>
 sub  2048g/FD5E2D21 1999-06-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 15114 characters]
 CC/qqMn8MWKJ0CbiXiTSu7dpojYAnjslrpODNzSntRQ5rK0SawJXsWWk
 =CMdE
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.82. Peter Edwards <peadar@FreeBSD.org>

 pub  1024D/D80B4B3F 2004-03-01 Peter Edwards <peadar@FreeBSD.org>
      Key fingerprint = 7A8A 9756 903E BEF2 4D9E  3C94 EE52 52F7 D80B 4B3F
 uid                            Peter Edwards <pmedwards@eircom.net>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEBDlWwRBACjdnvu/rCOVEjpYmlmQmmmYZ0hbUdustNozm8dtKpg2w+zED3z
 9kHcoXEY2i1jxmJrHd4PPcvMutJB5AuYU4NiBmdMgBgfZvW7yaD+tHfvgozNyEKa
 3Gcddamy/ENCFKoSTEuCDxH77zf6DXh/B/Ekjav0sZnGHPqFhUdKzwh21wCg57uM
 Z3aL0+sIhiNYEJK93yjXt0sD/2F6+T7dj7wjdCPsb3mh5YSTjGeSXjnXHfeFQmmA
 /dPyOkWOAuTo2uR3AeVRrJ6rslKLqyl773HX+eM5b52gIsFZ+CzSEiHSrHEqOR/o
 3jzzGWhZb3Q/dbeWsPrtw32XUOdiijH5h2PyfKQ6reu+lpH8oKTbvOoycguHnsiN
 8zt/BACCRoxdjw3f5L4RMfbdxN8/9GLcDzjv27s4Jn17snXuOyNzWxky+hNW5InM
 wG92m9/a4XtZX6viK4sY8kfFLvAx95vaRiPJOPdUIx6Hk34HHsXdQ6XbUaadlBuG
 Mxr+aT2o01qzxi+dS8+SWXjCBwT5mRVdOZq7RFYd73I+FrzltLQkUGV0ZXIgRWR3
 YXJkcyA8cG1lZHdhcmRzQGVpcmNvbS5uZXQ+iF4EExECAB4FAkBEXVYCGwMGCwkI
 BwMCAxUCAwMWAgECHgECF4AACgkQ7lJS99gLSz9lewCgtKJX8EySD4x42LoZ8imS
 gYzQ2AMAnjAlfeFF6q4Lqiv6ikUW7uSGu2WitCJQZXRlciBFZHdhcmRzIDxwZWFk
 YXJARnJlZUJTRC5vcmc+iGEEExECACECGwMGCwkIBwMCAxUCAwMWAgECHgECF4AF
 AkBEXiQCGQEACgkQ7lJS99gLSz/1ugCgwj+RyWcUk2WtWZlox7rmTG9ymDsAoJ+r
 ckrEYUJfPdH0GKonpipJQwL6
 =73v6
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.83. Daniel Eischen <deischen@FreeBSD.org>

 pub   4096R/7D15560B 2012-11-17
       Key fingerprint = 0039 2133 69CA 14D3 236A  E331 361A 68B2 7D15 560B
 uid                  Daniel Eischen <deischen@FreeBSD.org>
 sub   4096R/A51F81F7 2012-11-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBFCntAUBEACwjEAEbH8GDWGH+6ciSSocVDFFdMvlLWaoHOEjqsVMmotgP6dz
 M7oxf221fPVcck+fB/pngSFglsCtyZP1Lp4/3r0ynaOZJSEhSBpoHeIJas2ZA70W
 3zMfUZICFqkZkg51XTS5Iv031QHlIZIRx45FOjobVQ5F6romkxpdfyh/7/LDNru3
 xy7JVU9TBM48cFWwHmCOBYajDB3NOshSBhXEwiQH3y6Eo17RSaS4TJnwWIWFn1E5
 Z6fVArPclwqhRzgiy+vFD6WWfLBS4+AQPqn1y2/7fgo4L4Ai+4hWIcYXtMWpvtMF
 WpYXF7p0UFUBB7oq22933713RNPQJ+bUQMV0drmuSuy5frJMQrOUgV96l7i5oHMi
 fkaUVq2PDNZa/rFbMx6CN8cmce8TXEnz8FajRA9NbtHPYfmPUS6LX2F7VjT9KL2r
 wlF07fLtLbxCnq2aG3O6V2hrkJdWZ+6970s09LsdpTS03gfpSHvEUpoBeQY3jszU
 fgo0qpzpYGWOVdkTtyvzomhNNOjNMEE9X+718v9vtWn5aK7/0c2edyb4G5uBCcea
 Qpp1m6QWB7NSfTQ1oSTAaTQOViZrnfBSVluJNwqx51MS30bxxuhkEwQg8yiF106J
 zFiBNNnMGXPjoT6pnfcOzlB64d3WyF/4Vzrlo7mF6NSYmjiJ4GoU3xDW+QARAQAB
 tCVEYW5pZWwgRWlzY2hlbiA8ZGVpc2NoZW5ARnJlZUJTRC5vcmc+iQI4BBMBAgAi
 BQJQp7QFAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRA2GmiyfRVWCxkk
 D/9owvhg0m87gtGjQdup5CscStSZdOF+UGSFBzhWF3NySppSDea/KiDk6oLJ55H0
 wssYsKg3tUEilrJCp2JxT5AbP6N08xv7CY3iTpiRV7ltcRwNNKfGUAjf53OYX8md
 SBc4+kjWpqMpkTMDOKeo/B0cepaLkNhbSbUtNfvv/ws+2chXuLNjpFKeSUSuIB3M
 n0exku1/b5phJEorqfYNrSNro9OljabCF8e2GxdHAhvz8+pU+PI9HvXqgRYPe8F2
 DJj+3tOaCGDbmccw1V3pBIrx25GbsThzxPQAbZRSSwqXBwSN1WII2/nIky1n9Xyl
 e0d7+iHiMSc3L6LcSPc5xmocRadzOj3PVVN+Wyjx9fvJtb0bZ4a2QH3jyKyrouKn
 7+zwm81saf9PnUvgdN38xiuY6r4a8GoqecVPpMiGmvo8MtkiFvZURvJYGD/wj/eu
 anzAPoFyIAiPfIzXJWBCCLKmy1IiRa+OuABsVFMqdS7MUTQSvAG+O87at4wuPjJT
 nikZtRg+f79LitvwvMjUIDAnERv87A2Y9BQTCu+yVeL5ezT9xKeuKSJ13qs+/kKf
 feRW7WoSIltPGVWLVSrHErk9Oi4632pBzSWQIYSR3BQeXrnalG4fkXxoA8AyHlRO
 LlUlTpW6JYkmY8XbD8FPjmvWZb8mRQpmRJ2HTNb27FL81bkCDQRQp7QFARAA1npZ
 ouUZy+eMJtJcFZvKVxG17m76N4rAOrzLC998bjVJXrWz78k75u+pCU0n298AR8SA
 7m980S+1upBxTwYUw9GIIwhQ6EzPtdFAePvWni0IT1AV4SPy97PSFfWSlB+8Df9P
 YKOU+wG7K/MJqiHxuGCC+tXQrTRjL++VgGxDWyotEEH/5F0ARfYxFIXe6Pzo0su4
 TK22jPf37GX/mJmdh+i4pN57pOkCVqFIfxbcAHtVU7zTtrU3f8+mVIJ6KfNeUgoD
 Xc48Icm5ZemZyHqOkLev6p49a6wRmrKx9CuQTLIDXKAc1fx7NuzvJ/5OMP/b6IUt
 sxtW9/fI97ueS4X3cMvx678fi3Ukq8NvtXbX0uePOddaS8Bg2EQjtTkKXjMEkNsm
 9oxmzLEyIUOQ0XDHE/7JpzJb1qSgEYNKV7yiHev0KX1xWUXfljQ0hV+4ROJ9cm3V
 LvHQvUxrqBr1gRqzVk/WK3U8WrkbKKSbLrGtL/l2+Db68wvL5DIP4a/P578dX3qv
 HMh2cDEoNwrZpgN88AtvEgZpmJMco8SY06UrGuaAUI/PbgCJt3go4BklD2BzBFxS
 y2LNZKQciezphlO4GlD1BG7y4qkPn7SiNSTbB0/8jP7siJquXfzRwS6M+btAIZHC
 HJ8Flx3jUdkXWh5N26GDxRcQqTavgR1LKp5lSq8AEQEAAYkCHwQYAQIACQUCUKe0
 BQIbDAAKCRA2GmiyfRVWCyWmD/4z2vs/MOjXsHp7vBo2MASTPiPuIKZYM7rq4cDV
 f06FUT+kekugLO8Dhz/3YsiPNctArcuL6UKDpvM5IBE8SnWzOWX1iVpcRuTLdkOS
 8ZrXHXTYNDCjXRqh15U3X13mjNON3yyHlqNb9GGe6GwieyeIMjN1Q+aZN4RKsl36
 V1Qg/X1/n+7KlH3yaeC5mz0BqK08L7ROECPTLZrnWBmchHZaC5m6xywAnZDSqg9t
 VXqRiG9D17Ksp0RrG6Cg5zewIh/HmZ/m6RGzW8EaaXWHfftZJPKGFIMvOK9tsQpp
 X7Dcu/DxmdNwdTC9hyOMbszrF/mQ+rvOJM30+FFY5BqDK2/fw6NxCqoMqbxdqwEP
 OcB6DavnJ2IBFKFxfweuq6ywOfFaHkCDYq/SFKVsf4JcWAT6VxrEfVZVhxh7YQgE
 3zJGU1uOvLCxuq624+rbcV3EQyh78hyUuVzyD4eUBoNT2bfQM3YXTTsaKWqEDUUp
 LoI/GcYTXMwAYqoVyWtoLGjmEFlPsgNchCLpDtWaAxTiTTZGsN5DwOK6rR++77t/
 0pSQjB82AMC/OyZFTQ7OhnNSuHYTc8OYG8dz40Zr+QzXN3z69+gfp5OHXvevQuPU
 0op41UoAM1NqcVu1jWqqrv+jq1CDdPmZ4HqT2SIhDQWrdIGIqs1wC/v97Mr3irL1
 bwlGxw==
 =J3ZL
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.84. Josef El-Rayes <josef@FreeBSD.org>

 pub  2048R/A79DB53C 2004-01-04 Josef El-Rayes <josef@FreeBSD.org>
      Key fingerprint = 58EB F5B7 2AB9 37FE 33C8  716B 59C5 22D9 A79D B53C
 uid                            Josef El-Rayes <josef@daemon.li>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQELBD/4Zd0BCADEH+EDDjEX2ztufB5dele5Bt4XBg3cYncvlTsVEDLR89xtwmFs
 3no9Hs0ImTQwplsDgbixBL3DXWi46dwVK0MGYIUycJxLfsgFdlWngcXYkpWF3O8g
 v4YhytcVi9uSBy8oNB7huiY8IXh4XPgiOKztgCVJZbIgi8ahoif04eHTT9YGOL5x
 Qu+n7D74zAcgzK0XO+O+WXB8EoO/saJxzcCIeEGzfCjq4VyL6JB+1c9CgWlrpI7K
 LOpFqrN2qHygIMxCicp/163AdxD9I1hUtlF/sZYY9BpkbweLLqxKf4qtDYAMZLuS
 xFGfIG8f0imfFeTXt85FgYGxqLMlmdjFefIpAAYptCBKb3NlZiBFbC1SYXllcyA8
 am9zZWZAZGFlbW9uLmxpPokBOgQTAQIAJAUCP/hl3QIbAwUJAeEzgAYLCQgHAwID
 FQIDAxYCAQIeAQIXgAAKCRBZxSLZp521PM0PB/91jWBC7yI2obxE+VGsItduiPhC
 0x+Z33suGP8f7ewGBlztKC8y5N9jCGCfG9auwkJ9Xo27zCpMIkba4CfbRqyLxWoh
 ZluHQg5uge7AGefmsdfDsfZq5mPNtUkB8uVn3tXGwVVsxknw8PGtw25wbDCOXTCi
 t6L70v1gJfK8UxFhu0VCdOxbRAuQoIkE+bSO6g8bJrt6JFzhVpuHdgxwJbziWYSp
 nEJUN4Eou4UfCteVQrkh2O7ArHMmAEb89s5xbfNrQ4NdVBXHfsrzEDhWOqgiQ/4m
 o2DAs8iy2aCbWRaKG6G57g+uwhbqEN3gkeDfjhcpBMLqQy8drqx+erNGVYnKtCJK
 b3NlZiBFbC1SYXllcyA8am9zZWZARnJlZUJTRC5vcmc+iQE6BBMBAgAkBQJABsPr
 AhsDBQkB4TOABgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEFnFItmnnbU8miAIALbu
 Y15l3+9kNlv4Arv26aYrRcIYEUcCLIGZnD93NPnyEza4WwsUbCvYgNpKb/wojAA3
 xUdzHtRUfDp++eQU72S7DcRkkTt5vrnwKnH9kMsr2/hCIaO3ESiOVoPeJy91fHEF
 I9K1qP5noJQjfjr1w4ib86spyVb5LH3QPEnyvDX/UTBYiYu8UUYonitLZ3iHk1Ku
 x9SQoPszvkxdM1+d25pbG1uSV8JQRym6TsPQp3RwpbCy5hnwMbDLaWl6fbRwtAxZ
 i6A0cppdbgi+DDrOFoFKuU25YKKOKl76Vy+cpjYPBPRH3mOTYd/i2xliEP56dTJU
 4QqDJPpnJdmvXiCFt5k=
 =UfKm
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.85. Lars Engels <lme@FreeBSD.org>

 pub   1024D/C0F769F8 2004-08-27
       Key fingerprint = 17FC 08E1 5E09 BD21 489E  2050 29CE 75DA C0F7 69F8
 uid                  Lars Engels <lars.engels@0x20.net>
 sub   1024g/8AD5BF9D 2004-08-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEEvjRYRBAC1jMkUf5HrEQcNSLSK4NogjNTuwxE9d4PjgOiJ04L/haKeUAaB
 x21REw659FNCOW/HDuCzNH4POFQYoe2dyS3lV4xk+YsoJ50NuoCro/tiigBztKB6
 u/Ukq8bReroNwjP1Q2TnCHWxzDIq2HJ2FQtbXXlWKe7ZBu/LFwAsHLenLwCgzkp1
 i0gxqzxWrzIApMiKWB+HORED/3Jjom3MOEZfr27aYvY18700uXui6GAkcxTj2/6X
 s1MVpQt8F/BAgKYkw8Q3qOgoaJPHpnBQXMIB5TXCkXxZYwvUFlLHMOghpZE6/eHn
 3+UdvqsxHGa59Ym7HYzS1IExBVNfof4MVsunQtnGaHyQDMrKt2zF2MmTgASzITWW
 GyOjA/0Qc0K+hUBPsiaVpNcCZs6vPxeU1qSZamyZlVIjfQgRkTGN94bJD7l4qzaK
 hpmOLF8eD6+pA936HVhLfmPsNFkpFgw10oQQVYIVx/Thj5tOX2o7VbXUdQEkdTTO
 t75c2UqZIdPKet/btF+NPnnT3P8u0UdVvpvMeq7thLuJLkDDo7QiTGFycyBFbmdl
 bHMgPGxhcnMuZW5nZWxzQDB4MjAubmV0PoheBBMRAgAeBQJBL40WAhsDBgsJCAcD
 AgMVAgMDFgIBAh4BAheAAAoJECnOddrA92n4OuIAn08LIWiZX5vZ5GvClSsa30Wp
 2LG5AJ98fEToSwavm0tAuDHU1kPoDhPSqohGBBMRAgAGBQJBL48NAAoJEI90JpT7
 YBR5I/kAnA3vnk2qg91m3nocHy6nS2tShMUzAJ9RQ1orEGxFGukfgtY9iTTG4Tpg
 /4hzBBARAgAzBQJCVYkTBYMB4TOAJhpodHRwOi8vd3d3LmNhY2VydC5vcmcvaW5k
 ZXgucGhwP2lkPTEwAAoJENK7DQFl0P1Yg9UAn0/WHYshCUKP551shW3EtjUFvSF/
 AJ9EhPPzNRdgS5cs8Hifvd29McguHohGBBARAgAGBQJD/deEAAoJEAwB9WIgsQYJ
 9lYAn3MTmAp+MZn64phFp346NFhy1tRwAJ4xd16I6dRhDMSiNVPQPybwAZTfirkB
 DQRBL40XEAQAobWOOZBUJm+Twj/sGj0bUdlZ5H1Qos5uWEEjamcElcmN4dG6Dyjl
 X+X4dmcAQADm2JH5aajdWKKDjDNaTRbdV9XCe/iogYD9UhbPEQuHovTuDaOQrRsF
 nSCcXH1GABWF+Cp2JA4FVS1gmHykr+u9DZP7CsOosI6PWmOYwySidHsAAwUD/jVL
 iRLUj2qR3ejYTa61ATT5wb6UtuIohpvBNFj4t3V+LWATXmuOP1mYhy3SmoxUcmFj
 uULJ2GHHb+wNnP8YpGdxRVFkBV2grnpKqPdCkcm1ON707w2d3aDCEl9KGzhEvg68
 c4CF0hVkLGIs0qeZfsOwxE4jdYpPl8YuuRZV2ah3iEkEGBECAAkFAkEvjRcCGwwA
 CgkQKc512sD3afjgrgCguloybHuwhKsmOnnD6HSp1G/s4mkAn2VeB3Euh8fg6W/9
 gcKK4GHoPC8/
 =T+Zj
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.86. Udo Erdelhoff <ue@FreeBSD.org>

 pub  1024R/E74FA871 1994-07-19 Udo Erdelhoff <uer@de.uu.net>
      Key fingerprint = 8C B1 80 CA 2C 52 73 81  FB A7 B4 03 C5 32 C8 67
 uid                            Udo Erdelhoff <ue@nathan.ruhr.de>
 uid                            Udo Erdelhoff <ue@freebsd.org>
 uid                            Udo Erdelhoff <uerdelho@eu.uu.net>
 uid                            Udo Erdelhoff <uerdelho@uu.net>

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQCNAi4rWsAAAAEEAM1u8Y60omElX7Wtrh75P8K0L2Gp6omV6iDuwl9kXYhN94jF
 DE1F4xpkRDWvQxsWbYeIk2F3VYGuN12BhbRNcNqoyniQt2XMmbdEmp6ltumH5WbG
 jR5Xg0LkJ5AJmxvjJXXA9q+/eTfmyTfPjnCL70cTMWHdUl+EBUPoh1XnT6hxAAUR
 tCFVZG8gRXJkZWxob2ZmIDx1ZUBuYXRoYW4ucnVoci5kZT6JAJUDBRA0K3Q0Q+iH
 VedPqHEBAe9vBAC+el5mJpqPkC/+om/SSE7mxyuUqHAx1tNUymL8gTuV3mFB0goM
 xkxhUOMMYe9z2zyi+RXrECfLT2OqqUA60EZpl6Mgymj8SVZSv4ZwXdU8cgynYNfX
 T1pC57mN9mxL10vTTJEix7QsrVz0W479/IkBrhW9nTidQtORW1Si5T5IA7QeVWRv
 IEVyZGVsaG9mZiA8dWVAZnJlZWJzZC5vcmc+iQCVAwUTOwzFWUPoh1XnT6hxAQGl
 eQP/bLMp1qSdkt2/BKchpx+lhOemCmT3LHQ1sNzelb7dBwnsvE3Z9lOycH2pm1ro
 j6x3vmcDAqZ1yh2eFEVNK5abfhuI3QH+9QdgvMcSIQgF3VIMer7JXxNtFFX8JRKm
 +YfLfDifcK+B2HRkpMt9ETY8b3/cYz+gbdKNe4nVde5KPT20IlVkbyBFcmRlbGhv
 ZmYgPHVlcmRlbGhvQGV1LnV1Lm5ldD6JAJUDBRM7DMX9Q+iHVedPqHEBAYHUA/4l
 j98KC7y8cjapO4Hi0r/eO7gUwDujvrBMYbWuhmNCO6xlPfwRNm76tnNiTFdqVLat
 XSrQwEUys9Mq9xe2F2RuqSfYWjmHKX3/gNW3gRJbnBqO1QN6CDqo39a7LgllqFf4
 yFj9V6i1c0WSBiOeWy75DHpsfXHupMxZWPPRWh0TnbQfVWRvIEVyZGVsaG9mZiA8
 dWVyZGVsaG9AdXUubmV0PokAlQMFEzsMxhFD6IdV50+ocQEBzqsD/0nX9rV5cAcd
 jFTayQvoAjb/nIN+TJVHumuC/Glp9fKHlfTjMnsUawma+iQESjUB8XgyeJ0WvR8M
 vQGEMowYr1YTtFiYfFOvrzXZmhB6NfhFV3s34ZLDeBnncUqkas79Pi9G9AP2Y/Mc
 c//i2owj58xTfocYNT5IxVVYjB72Py+3tB1VZG8gRXJkZWxob2ZmIDx1ZXJAZGUu
 dXUubmV0PokAlQMFEzsMxiND6IdV50+ocQEBBJsD/1SVP70fNa3ShAn18+yEXOIL
 TlFYCUmGaBIeAsd7r8tXFYbf5STAOEOiqBB9Y7V1tV4IriACru+9wo5wBQoCLBT1
 RNj4NhwVvkGReTDsA+Zz/vUULrbklVKO724DktO0+WRbn/w99trttuUTGvTHRER3
 BjuOfJ/QoLlnLAsDBMov
 =TCJD
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.87. Ruslan Ermilov <ru@FreeBSD.org>

 pub  1024D/996E145E 2004-06-02 Ruslan Ermilov (FreeBSD) <ru@FreeBSD.org>
      Key fingerprint = 274E D201 71ED 11F6 9CCB  0194 A917 E9CC 996E 145E
 uid                            Ruslan Ermilov (FreeBSD Ukraine) <ru@FreeBSD.org.ua>
 uid                            Ruslan Ermilov (IPNet) <ru@ip.net.ua>
 sub  1024g/557E3390 2004-06-02 [expires: 2007-06-02]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 4884 characters]
 xfUIyIEOONF8sN1I
 =tea/
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.88. Lukas Ertl <le@FreeBSD.org>

 pub  1024D/F10D06CB 2000-11-23 Lukas Ertl <le@FreeBSD.org>
      Key fingerprint = 20CD C5B3 3A1D 974E 065A  B524 5588 79A9 F10D 06CB
 uid                            Lukas Ertl <a9404849@unet.univie.ac.at>
 uid                            Lukas Ertl <l.ertl@univie.ac.at>
 uid                            Lukas Ertl <le@univie.ac.at>
 sub  1024g/5960CE8E 2000-11-23

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.5 (FreeBSD)

 mQGiBDoc52gRBADCgyiLgEDhBbalLQ1VGkvfbdazaBHQRdGjsEPwPEG1xSI/5FFm
 0497ZJEYkUG4rXbgaNATSSS8yrqJ5i0rX2t3Y1TYOVim8gLq5ntUQtAdhHtnZD3n
 GbiBLRNRTD/HYd73ta4V789JMheUrQt192IRZZG8iKMjjaW+YQ5Z7nQxZwCglyEp
 33kslkv25cFVFWEHUhLvck8D/2iTzX35onmQkXdYEk8S8sS71UoSBgf0q5/4D6aq
 /Oq4zUYiChC7WGNNMjLSWDPsvt4U01SHfZVMOmbgJXmY6gE88tv32pGkLaIW+f3v
 BkKLwO8le5GvnfTA+xTyADcrqiZBdtH0zDd1jY61XCsAFyJmMnM+xbwT/dXa+Jtk
 h3CZA/sFdlpJrH65GHcuyuI/6bGwUkQqpTMCmYeXQjcEsTt2bWQ+knaAFJ7q2+uZ
 fmmzlhqNuPZ45TTd6BdRFtJFFOndi45yEZsSN7XNBcHGx5MshL4jCEtqQEDfUogd
 UbwkJtgK0URxFyZ906xhVwgwvX8eW9CzPj0wYsbYLZtGZ4zVobQnTHVrYXMgRXJ0
 bCA8YTk0MDQ4NDlAdW5ldC51bml2aWUuYWMuYXQ+iF8EExECABcFAjoc6IYFCwcK
 AwQDFQMCAxYCAQIXgAASCRBViHmp8Q0GywdlR1BHAAEBbQcAn0oa/bdjZ3ofFKf4
 1GT/UYftjziKAJ0Wzsy8sDahkaJbyWzKupp8Q7Uzy4hGBBARAgAGBQI7oHuHAAoJ
 EKkf+mOb7TNKOesAoIDjx0iq2xsnFfcECkh/zheU5HShAKCpROLbXal5pK3U2XC8
 t44oAXDL7IhGBBARAgAGBQI9S8/aAAoJEBBfSR2o12TYudcAoNufp4D+vHXyCX+g
 K/RMOpcLQmFUAJ9TbuD0ghWzqYY1VGdxrDusUux8dIhGBBARAgAGBQI9O+wTAAoJ
 EEUnYQZfFVEBfVsAnj/sw5aUDA2vEghr6ZgwzCmzPzeaAKCAMiJxQpog5s1HD71V
 3ZhLgk+KWoicBBMBAgAGBQI+sYSdAAoJEC3GaJzjyx7FiZkD/1H+Y2A1iZLXGBb0
 16UTUb7Dk2E6VO81SPtviliM8mx4onuvEHHJq789gi8N3TolhLPnPj1ZfEAGslIX
 5/JQRx71qhk3hDnGNaszxrgoTkYHQaaoxgZyeoWYP2wVHYF3eTXFLjh3Q8ZAZMGX
 yNwsYvvdMTIEP9kIQV/5oyuI4H+eiEYEEBECAAYFAkC9Dq0ACgkQ/PmauBrc0r5s
 +ACfetNYnG+BDKQzDeVgBsP/9depWVkAoI4Ey+1kZmeIdMAwnHOSV8b2TF/GtCBM
 dWthcyBFcnRsIDxsLmVydGxAdW5pdmllLmFjLmF0PohfBBMRAgAXBQI6HOdoBQsH
 CgMEAxUDAgMWAgECF4AAEgkQVYh5qfENBssHZUdQRwABASlAAJ497mVoCv4YJtvI
 begRpjXIpnPRhACffoiU3BSc8pN7gUlWtGZDB8Y1Xh6IRgQQEQIABgUCO6B7gAAK
 CRCpH/pjm+0zSu47AJ9KbtPOqVhHdF5APDbrc3olf7lyNACfc4M3ZZLSXzG2fsoH
 LoVX93P4xKaIRgQQEQIABgUCPUvP1AAKCRAQX0kdqNdk2FxfAJ9WA+1axtpqoafb
 5KAMCZB0ALSg/ACdFFizbtQM51ebXiNVhcT3rmVorCeIRgQQEQIABgUCPTvsEAAK
 CRBFJ2EGXxVRAcQuAJ9YP7X9N3xWPpgWF91eHfOtsCS0OQCfdKlgYCv3vJfFNjFj
 H9pNkBgjrtmInAQTAQIABgUCPrGEmAAKCRAtxmic48sexRS4A/412GhjArnp4sER
 F50HACd++Dmajzjbaycih0UyFk9Jhx7lkpNMFV0EyNKJq9unBfvuX4ji8kuq62ln
 I+p/avkjBkpqN9XH0YIQkCYh7X/I5saVWTSqUJGZMPR0HrnJziWyOAiQWEfJc4/A
 yY6IuS4HMIRvlcVql9MgMWUvsiCwiYhGBBARAgAGBQJAvQ6tAAoJEPz5mrga3NK+
 5uMAmgOksIQqUnvIB9AA/egOVWPNTIABAJ9iWClWufO9VSjm+uKCXFoEZbBAfbQc
 THVrYXMgRXJ0bCA8bGVAdW5pdmllLmFjLmF0PohfBBMRAgAXBQI6HOhwBQsHCgME
 AxUDAgMWAgECF4AAEgkQVYh5qfENBssHZUdQRwABAdfRAJ9sUaTyswjTHMCSqZHN
 ZDAsCVhyDACfehlPEYgA/zu0rHhQW1fFxRlkhTaIRgQQEQIABgUCO6B7hwAKCRCp
 H/pjm+0zSh21AJ9sa+U9/NyXhVUm+HjhpV/bL0Le7QCfVc80UHqb3b0Dcen+jov7
 tiJ3eraIRgQQEQIABgUCPUvP2gAKCRAQX0kdqNdk2A3wAKCR+d/9qrGqzpGoBLQA
 b9SRAjl/BQCgop5t90WbPwuJm/AVdbE+N6As2w+IRgQQEQIABgUCPTvsEwAKCRBF
 J2EGXxVRASlFAKCFlpd7McKT98cATC+8Sd4RFNAUVACfRHTANXgfK7hmvvD0pWr5
 nofT7p+InAQTAQIABgUCPrGEnQAKCRAtxmic48sexfwPA/9WyE6OAshMZUuCjHvo
 nHt0G+qomn+6CrPrps9il0ofWAWHEDMM57OkUYu8O1uY4G2WDfcUGx3XrzHxqsch
 Seeb5/aD4z57ZQzdGz6zRyorJxHJ2S4vTvLv5QWSKCBqYUEEYgPC22C+JHCfvTcx
 76bDE41skqjwcJNNo0sPcMHAMYhGBBARAgAGBQJAvQ6tAAoJEPz5mrga3NK+qYEA
 oLuLq1uPXXdYnrJ4e+c3qI3Te5FBAJ9lkHFlMp+6lcQ/fN3kSxWMrH1ohLQbTHVr
 YXMgRXJ0bCA8bGVARnJlZUJTRC5vcmc+iF4EExECAB4FAkAmTJ0CGwMGCwkIBwMC
 AxUCAwMWAgECHgECF4AACgkQVYh5qfENBsty0QCbB6IgEk3WC8br8usvNqWt2t3y
 93IAnjwh2DGgCRk9AH7fdNoSF+an6CquiEYEEBECAAYFAkC9DqgACgkQ/PmauBrc
 0r7yNgCfegCimXz8NHxxTnfsz3UU++dz4jYAn1nPAh8hwYPh1rWUjHh/ATX356x4
 uQENBDoc54kQBACRE1IriFYgaKg3pDeBPDM/BUflmZSlC50NIgCadloOGwu3AFcs
 ooWwN9nsVehbN9xjfZa34/xXo09Rn14o5kTKYGSqzYY0XbsNjZl5uj0gTGFRmjS7
 fNoWpdsfh38xXZAJOghxd/KFRV5fdnKoEPz+ARNo2DRZpiiEJUa14e6lpwAEDQP/
 TvA9mc8OEa9dn0AzCRwvITqx80WBRBVBl9bC+fx4R/CCt0O+gtkoPBlAdY/r0+XQ
 ZhCeOROXy7e1sbAMm0U0QHgckne83VgzV9TAWHtP2dfGgtOzUE4PlUVBerTCGADP
 FTN+kcvV6U/O+knnJGmnxxOq/9qtkdtEHvyAzWjehPaITgQYEQIABgUCOhzniQAS
 CRBViHmp8Q0GywdlR1BHAAEBIkQAn19uApjyy6+M+JD7Qt8inbcYjk7cAJ0eNltS
 Fv2s0kptGIN2izILm1myaA==
 =qAVp
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.89. Brendan Fabeny <bf@FreeBSD.org>

 pub   2048R/9806EBC1 2010-06-08 [expires: 2012-06-07]
       Key fingerprint = 2075 ADD3 7634 A4F9 5357  D934 08E7 06D9 9806 EBC1
 uid                  b. f. <bf@freebsd.org>
 sub   2048R/1CD0AD79 2010-06-08 [expires: 2012-06-07]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEwNjXUBCACWeNjUFZ8rzqxrEIdL3wVrvkWVwaf5HW0YwoIMq7ba3hRcPWuv
 yr3frrdvqJv9rHJYA8f6uE5dCkb7OSI3YXHC5QN/H9xB1bvRuSUyD1MwmuihUX/A
 7yk7HzUE3sXy1U3QIMJWgpvnN242OZtH2XlanuSoDdBL4Qh2Fw7ywQaZvzNlZKUa
 hPF0Ty7wci/5xuKB7T72Qk4vAYYqxUxYJR/5ox8vM/xiAh5XxPbOuAF0p/wQiiRi
 NjF/f6tluQu6Q6VFwHXGcZvJK39nNNpadsDCegdRCUUFJsHm8dSjlIyi5CTyUsXf
 btdlagPTlhiBtOYgtcfRZoPBLFjVafjqqL57ABEBAAG0FmIuIGYuIDxiZkBmcmVl
 YnNkLm9yZz6JAT4EEwECACgFAkwNjXUCGwMFCQPCZwAGCwkIBwMCBhUIAgkKCwQW
 AgMBAh4BAheAAAoJEAjnBtmYBuvBVG4H/Rc/AqfFfQi+qph0HKggVJyzEKvhVWhR
 8RZ+8zS4t72b4kIJT8FUOiHMpq/+qC+Lt5MFPCtxmOETDgpD9GM1EkgJ1rSDrN8m
 kbXuQ9Z95KztU0tGsv87JT0xSpxeMnYaQ1NWx5bkKG5AOf6ZZaUVas0XH8/9QCFH
 gqy7Xe2eGsLO52ZH/4AI8cFc0FPF17hSWTIAwIyuxcRLas+KdV1j74xaBu6parX3
 2FoquEFRAPoEcuey2aSWoo4OCBCoGYqh4mhWbEuLOac0NP3oLDFjEDJhE7UT+0gx
 W5LLwPr0FARkAbRZp84vt9rD5MrhNcZy0X3PBpykium4OrEIp5l9OM65AQ0ETA2N
 dQEIAK1D1POvE2tRnTeNRW6lw/bu9zx8d4PS2R7GepQkbUWQxpgcwSEoB1JGN8jw
 0iKD8KRoFLwQx+TizzRShRsOeYj7beK6rY5H1C0DbrQX6T7eMumOVV2RklVFqYiZ
 HcJh8LGjJN/tKt4k7OnDs40lHOFHxvKW+PiKogfiWDKpc/wns9mAhcXrbT0SZ4Be
 qbQOsZMfUbvOZUek4+lOZuaCb0M3QU47bsFrJonPn7VEHw7mkhTNL9a6KKc4ZqQw
 52ECVq4dKjNIkvaQZyosA7tRCr+CBYUumE6fssk72SdT0RD/tgHgKfgWZ9mxB3R0
 l7CCm8v4c24tZQuuGQG26WWeD8sAEQEAAYkBJQQYAQIADwUCTA2NdQIbDAUJA8Jn
 AAAKCRAI5wbZmAbrwabXB/9ggUz/04tDZdX4pDsfDoBKtnJ9r1yNWrniBBNlcVLZ
 G+3BwF5EfZAA/q3lSJmC4BVzaDUwrrL/zbPb0WhE5cGG/byLiByXsEDVSId4Kv/Z
 bLaPyox8RIYUL/wCjt/57FIORwGVhUr8oDDRLeSoIsazXWhvWfx9qCdzcZTabSkN
 74Q0WxQuOagvpl4Kcf3eQEQuB+BvxDQx9JvEXUZanurRP018uTdXficJ5MS+SwXq
 gJUSSPybwVjK/ll1G33185jnSQSFNwGq1udet7vkDjQKNmkcev1SJY1g0S9iFKRz
 e6dmnydHGtQ0508cCusMPNCQ4HRhQHEW7w5yu1J4t3UY
 =bgLz
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.90. Guido Falsi <madpilot@FreeBSD.org>

 pub   2048R/56CBD293 2012-04-12
       Key fingerprint = F317 2057 E17E 4E3A 3DA5  9E1D 1AE6 860E 56CB D293
 uid                  Guido Falsi <madpilot@FreeBSD.org>
 uid                  Guido Falsi <mad@madpilot.net>
 sub   2048R/1F9772C5 2012-04-12

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE+G+l0BCADi/WBQ0aRJfnE7LBPsM0G3m/m3Yx7OPu4iYFvS84xawmRHtCNj
 WIntsxuXfptkmEo3Rsw816WUrek8dxoUAYdHd+EcpBcnnDzfDH5LW/TZ4gbrFezr
 HPdRp7wdxi23GN80qPwHEwXuF0X4Wy5V0OO8B6VT/nA0ADYnBDhXS52HGIJ/GCUj
 gqJn+phDTdCFLvrSFdmgx4Wlc0W5Z1p5cmDF9l8L/hc959AeyNf7I9dXnjekGM9g
 Vv7UDUYzCifR3U8T0fnfdMmS8NeI9NC+wuREpRO4lKOkTnj9TtQJRiptlhcHQiAl
 G1cFqs7EQo57Tqq6cxD1FycZJLuC32bGbgalABEBAAG0Hkd1aWRvIEZhbHNpIDxt
 YWRAbWFkcGlsb3QubmV0PokBOAQTAQIAIgUCT4b6XQIbAwYLCQgHAwIGFQgCCQoL
 BBYCAwECHgECF4AACgkQGuaGDlbL0pOWigf/YVTVf3+ZRnzeGP7CjGV1Wrrxzjc8
 h8W64NZasV0XLHGFjl5MYwtm9jJ9gbL8Ubtqstey7lYpjOk2fG6YDhY5eptWCpR6
 1QqYrioukhCfKbodSk6PnIZcx719nJVK2P7ihdFEN78TavpBwqIf9hGEcKkMpbRF
 Qv1mYvXDhKVwQGY+8bkH/a/pAWmIyD4qMfKCMurH5DexxEt5SYWu5BB5hd/DWyZ0
 wuZ+F79KMPzLBPJW5cpdLNbrvenSqFZGJEGhtTp7GFJJr6lTy8VLBArxmFHiY5jG
 yR45eZEGDcz86FfGgvPnnpi7aNCc/ROdF7fnZYPh8uZGGjQbd4EYK4xMzbQiR3Vp
 ZG8gRmFsc2kgPG1hZHBpbG90QEZyZWVCU0Qub3JnPokBOAQTAQIAIgUCT4b7cwIb
 AwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQGuaGDlbL0pPa4ggAitrBDz1O
 eoSGLYI4RACHHe6pZm42hLo3KJKCxEKa1KdPYY6AfhRxuv8jftKRXUHcroeSgvqX
 A3waN/ko6AuqZOITVbdFPBLuXw9K92eMz2LuDfnVHiZOKO3FrAH8lxB/8qB7diqv
 VXiDof7BBcdRK2YdOFu6m422vNGmG9H97l6RPQVPJV8+alxubryLZvBmcpR7H9M0
 gQIHKRiHxv5JgwuEQ1/ZrJGMIhZLYB3u2dMqEy2dLmO1bqqMHLhGhOlAPqhHXEiC
 RNGVDj2uhUJR90dv5j+SH5T0bUhyg3Li+SD0h893ClJ+c/5ryPQBnWEyc4tnV9ih
 Cuz7iBUvLwWztLkBDQRPhvpdAQgAsd6mrOq1GSZwlzRscNQa9W2WB/3Tj4ON4PL2
 e9B+hc9lT/ny2zB3agXu5wbsXTzwxgJpQT7hNHkCSckW98h3HRjFfhZPNCgInuUG
 sjcNyVguQh+/47ckhph0s7U+6B4yNuIiqQZk4mo8WgCNj1YIihVmGWEsgDOwMaaj
 bDYZ0r1/3GkKlYjOXeUuT/WgourrSR5oZJVNA/k4X2H7M3JUr1BSc32L7BJt8M7A
 ntul6k17J0L8GmkvLvTUtQTO+p+DYQMna2ngD3PbAvQRcbEGnkg9ABrdEF0Wp4Gx
 +gGGWsyFKlHvPdMtgWAy3JsS+rQapG6LoW3yUJpwpEpA86KdBwARAQABiQEfBBgB
 AgAJBQJPhvpdAhsMAAoJEBrmhg5Wy9KTNfEH/R0zTYbvDdCEirZkfJYD4SbrvPaz
 hGvCihGra+H0O4C/oZmDhKmf8hy3D0LxsWwJS0exdEoXirwBJOAdWhcBlCz6NEs7
 jtHf1rVTBGxmveSU5v+pn4spljJVn/FInw9TAys8z0ezptMm3qDzPEv0UE26FFNV
 i6cHeJoPaVSZStMa+eRjkhzX+Ju0vj9ZL5d8YJhI9eM1TKvciQTVhZbECuXIon4e
 7BaX7sVnRFW7YCHcacyJii10iwNLzq6CgL8RUxgawat78VenlJmisneR221no5mn
 2NbmuXXJ3sPZcaVii3apAtu1bdApLvi7U2N99uVfgQoZ3MDXCSUuyDJgc+s=
 =pMfj
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.91. S-oa(R)| <rafan@FreeBSD.org>

 pub   1024D/86FD8C68 2004-06-04
       Key fingerprint = DC9E 5B4D 2DDA D5C7 B6F8  6E69 D78E 1091 86FD 8C68
 uid                  Rong-En Fan <rafan@infor.org>
 uid                  Rong-En Fan <rafan@csie.org>
 uid                  Rong-En Fan <rafan@FreeBSD.org>
 sub   2048g/42A8637E 2009-01-25 [expires: 2012-07-08]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 4752 characters]
 D/Fet8nCx6Ef1M1J4Q==
 =1iVI
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.92. Stefan Farfeleder <stefanf@FreeBSD.org>

 pub  1024D/8BEFD15F 2004-03-14 Stefan Farfeleder <stefan@fafoe.narf.at>
      Key fingerprint = 4220 FE60 A4A1 A490 5213  27A6 319F 8B28 8BEF D15F
 uid                            Stefan Farfeleder <stefanf@complang.tuwien.ac.at>
 uid                            Stefan Farfeleder <stefanf@FreeBSD.org>
 uid                            Stefan Farfeleder <stefanf@ten15.org>
 sub  2048g/418753E9 2004-03-14 [expires: 2007-03-14]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEBUhZkRBACOyBTXaf9n0gkvq52yhACaPjUpAY4c+Z+xDM5jZZNpcaEyuU5N
 ipJdvlKIIkfB+Jka5TxiUBskSo6cegPW7k3G9/as+39SeOexEw5aH1WROcrqD1Wq
 iBTJ/Ey8eVleGTP/3vpbUoT3gcNZuus00J75OmJV06xyTA9M0tSy1/aIxwCgrbCJ
 Xr3wLOPYiGXf5WbWfy08DmUEAI2xYIycYgZ7ogcqFcu6gShO/uTcXkZL0xOIC8el
 rAC/HciJagmvYPjQimQeKhqyX+uvnhguiS+XZYx9yqegOG1dSOVWw6FJTYgzKeT7
 6tHmaplB4JQLkUSBn8p2fsyXAaIA4M+2c9fYf59El5+OyfOhGfAEJNJv1oGLYWic
 Bbt0A/98H+rPmPwtv4ntIvCq5xkvjENzmG6WerNF5dXHsoG6Lnhe++4jUquHseEI
 +u4ou+v1it5vBTnPI2Wz02WP1Oyz7JC0cPAbrTGz+eaaNV+M1wD7yqj1poW74buk
 4hJ+myIqC1dRrliAyrr75xHl3pr212+8Cty8RTiNF9xgICtH3bQoU3RlZmFuIEZh
 cmZlbGVkZXIgPHN0ZWZhbkBmYWZvZS5uYXJmLmF0PohnBBMRAgAnAhsDBQkFo5qA
 BgsJCAcDAgMVAgMDFgIBAh4BAheABQJAmCd/AhkBAAoJEDGfiyiL79FfqEoAn0cP
 NQJYvSLWsU4gD/cffKUtLEKiAJ47lf0I7dFdAJSqqxSCOrw7iuWhTrQxU3RlZmFu
 IEZhcmZlbGVkZXIgPHN0ZWZhbmZAY29tcGxhbmcudHV3aWVuLmFjLmF0PohkBBMR
 AgAkBQJAVIenAhsDBQkFo5qABgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEDGfiyiL
 79FfeOMAnR6XllE6b+BKnoRjBOC06PXfoK0jAJ4yDtL0vkYkW9LRmoFkWpxJYilU
 ALQnU3RlZmFuIEZhcmZlbGVkZXIgPHN0ZWZhbmZARnJlZUJTRC5vcmc+iGUEExEC
 ACUFAkCYJIMCGwMFCQWjmoAHCwkIBwMCAQMVAgMDFgIBAh4BAheAAAoJEDGfiyiL
 79FfwykAoIes15zWxNJ7iQr1n4rP+x1LidM5AKCDakRpNHAdMiaJJRNrHt9I1kOu
 FbQlU3RlZmFuIEZhcmZlbGVkZXIgPHN0ZWZhbmZAdGVuMTUub3JnPohlBBMRAgAl
 BQJAmC7cAhsDBQkFo5qABwsJCAcDAgEDFQIDAxYCAQIeAQIXgAAKCRAxn4soi+/R
 X//IAKCmPHdkW+JyvXq8Ph/4AcoSYGltQgCeOyA+WXLvjD8s36h1ITQXleLr0Ju5
 Ag0EQFSFrBAIANrcNEggDb7bS/TkhZg5CEw0HP0bFOogCowNgGZ/9EzZA1SvABYb
 vun0RyK0Ceh51Vr0Lb01i6cIDTH/cBVMqXX75YPusncMzsEuMdBCzMqKRPCpimUD
 jFmMIBrkbtu8OTwaL+Xy1j7/SyfYv8fV6q6ibGWgN4pcyDmItTWYRNnR1G4EdIvl
 a2CgQr7AgzWPGeeZLrUqUuLjYKwZ5JUqch3ooU4e+eFkYjovMyiC5E23UxZWyDZQ
 DA1aOizxH7519R5l1YDsrqjZdVz3Ks7iCPYZ+T2QMGM7oUDjbt0xAhQCt15yj2K7
 f0m6KtmHWzwgf5Dagcph00anBMldDQ1RqscAAwUIAMReNMLnk1jhYUYoitYNDJTO
 Pp1X5bk66+b5yHW2Ul9DDboe9tp37AoSJf1hEI7eyB1qkKO3bt9nePKOuAe64ft9
 jMYEm70IS3tmo3hHyTbLuOpxF3f7ZHmai2gXPdDmIczDqkE1PneX9gJQadQTqvky
 4PVHKVUGTBScI0S830ZBbIsvoYimjGCPMuz4UT0vKR3XLay4RjwCYC6waqRuJoBq
 rfm/vmx6/GNfb/jwZgN3QYPgTptx65eAdEAy2C3Y7RbMrbx9qqvx5TxaS2yVFy6X
 6gIrSmFSFE8rplPDActw1V4YMyuwnyVvGe93pYwYfxzM/BxN09V9QBQUhIa7TMiI
 TwQYEQIADwUCQFSFrAIbDAUJBaOagAAKCRAxn4soi+/RXy2fAJ99u5jBvCIXuEPa
 rLB9utH3lU/ymgCcD/fpfY9v7wyOrivOy6Wz3ZWjdnQ=
 =9khA
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.93. Babak Farrokhi <farrokhi@FreeBSD.org>

 pub   1024D/7C810476 2005-12-22
       Key fingerprint = AABD 388F A207 58B4 2EE3  5DFD 4FC1 32C3 7C81 0476
 uid                  Babak Farrokhi <farrokhi@FreeBSD.org>
 uid                  Babak Farrokhi <babak@farrokhi.net>
 sub   2048g/2A5F93C7 2005-12-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEOquWMRBADPeAMeFy9OMbD3PxFjNmPIuY9CMb/fP9G3KNugVwLoHj29pXHS
 QDo9OGHmA6udL6ZjZt/cWsU6CBwrVmr7nnqIXwOFGsvv4sT4cQJd51ypMFcvrYvi
 UmdfnNZWeggviCMYdZErMqVdH7QKZyZ/7xB1IBV/66Bu768nQlSpTmqTYwCgwpUr
 8V37ACzVXUZ/1CPqtadIe50D/1rlR4GTzMnmJGBbqY4c2nNtaUA2HEzI11QsHvFp
 jTEcHI/RdhLv8dcFFAD0PmLC+5W7OydXvQXBfWzVXmrEPzFprwOc79wfCB+JzOt9
 JzyClVDYvhYd0f2kxrXOR3ddLaBCMU9A/NxvDL05TCE8b3rSuV2VRT6E6A45/88t
 aKKvA/9ewMdS3zicyyK33FTYTecGJc6Kt1ke/spq6jo6k3+L94Z7eZrZrhXGMRYg
 Ibbm3VuxoPeIqyY8SujHwNNzP7PqGp8MVefjzktldMyvbJex8oIyB0NMrHTJ2JTp
 ScJAetOE/mXYhMSACgWbebu6uBEigmaz1D4WNU/ITf8xuX784rQjQmFiYWsgRmFy
 cm9raGkgPGJhYmFrQGZhcnJva2hpLm5ldD6IYAQTEQIAIAUCQ6q5YwIbAwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJEE/BMsN8gQR2iM4AoKXtRmdbGhmrJ3cW6lcd
 gP4IUfUkAJ9mqLQk3ztstsPzzovhwV4sIH2VgbQlQmFiYWsgRmFycm9raGkgPGZh
 cnJva2hpQEZyZWVCU0Qub3JnPohgBBMRAgAgBQJFUO2LAhsDBgsJCAcDAgQVAggD
 BBYCAwECHgECF4AACgkQT8Eyw3yBBHZd/gCgmHXJVgY+AwvJvL2v2qG6+P2EsP4A
 nimm5LNueFg2PbDsRb+Iz53zw8d6uQINBEOquXEQCADPKrfxmpqJEbVpJV1PfcLJ
 KpvF/0s1NEhvrXVnm0GhId8R96n22E9oD7QYTw/+TkdCksw0dcAIvFH2y++HNQoE
 NVgoyVW32Rw076Va8nizA2icB6hEJwKiI400qKjZknj2pnILPHORq+Zl43sHaXnB
 imchl5U9gZI4EXCRC0u87oLd0IHuFMUGYEfhsxninLpmFNPjS55zEhPDIBTuFFiN
 NFZ8aLxq6APGd1lbLJhYnQIYZJreaI3lXc0VYqjkaB5WBeYXKNNF3y39yNY3SXFt
 /dwIP60IoaIAjARFLqvUNYOsHpjsVAItxxMdTpAlX28VYWsr3quGL97Xhd4NfDvb
 AAMFB/9ep1jcpFocEOurMYZkIrPE0CdgdeWzlhHhW2F38cZTj46WxoAY21QOfjRx
 tCcGDrKNNwoHO3TIsuPrEI1OtJ4y8b7Pj2zuv/kUAEMUjl5dutg2kIDz5cs5zxI6
 4HhUx17vQGTOK3l1I2JxoNrMKPcDKxegHqYqpzb6vEr3gsKT7GSeMBREq0rvfZfQ
 ZmZTLfdy0AiQ6KsVt1YV9wUE7Kq5OmhjVZNovhZtxO/tzppQLNX/62wdf1OmFZIn
 xWrYFHeH/N+QGBmMRf0NMb0oOn4nEMem9QhSRcW9UcyU1K7Usa3m3WG7qrmcq+ri
 9RVM7/8wJCKNJD1ej35rMQYVrolIiEkEGBECAAkFAkOquXECGwwACgkQT8Eyw3yB
 BHZy+ACgqz3KenkNoTQKFv4nrGUHnAqMm5sAn2Z+BhMOzEhuimOTVLXVzKuipov0
 =vL0B
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.94. Chris D. Faulhaber <jedgar@FreeBSD.org>

 pub  1024D/FE817A50 2000-12-20 Chris D. Faulhaber <jedgar@FreeBSD.org>
      Key fingerprint = A47D A838 9216 F921 A456  54FF 39B6 86E0 FE81 7A50
 uid                            Chris D. Faulhaber <jedgar@fxp.org>
 sub  2048g/93452698 2000-12-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDpBP9wRBACTXnvtFjxGYNH2xj0oZ09ggebJAzNOz6FiQKBkYo76EtyhFU2U
 s8F6HJmhAVJVEodJiA2V+mbVVI9wG1r+yFxgpC4JCdtozSt2cgKHlfFcrAUn/bVX
 p3ZiVio4/tWVS4kcOZcN/gfXxykG3Z6IgeMct4P/v+Yby5FKrjFcHUXrYwCgpTuq
 u89HjAet3e4MOkJ43QDOqf0D/jQTRdivb0N302svCzG1ccc1y7YhiLN7GEY6VttK
 Dkb9psNQFlgd+GNOpQqXXvh0EhzC0sA+lNo6F6rWZsrtQD/i2vAubzmtvgsF+UIp
 268IbgRs1RHW5ZOqzkvDjMN+8/Kk/v4qQ+62WAuP2/iZn6bAjAfBPd5SGa97SZ3E
 d0sjA/9o+3jTgxhNz56fxQb/e2B4lqPxuIsorxB28hmXliOVRQBHwx4e8XNvN2Xz
 WklapX3AWKP/D1ZyzxNEaBezu4NBFpl9HqudFDyFeRzyrhGSD/f3XtlDTHD5hv31
 +LSprexLW8nxbsKKjX94LnyYItRGcf7gU5z1V73amT0vedaXj7QjQ2hyaXMgRC4g
 RmF1bGhhYmVyIDxqZWRnYXJAZnhwLm9yZz6IVwQTEQIAFwUCOkE/3AULBwoDBAMV
 AwIDFgIBAheAAAoJEDm2huD+gXpQaPQAnR/EryK6lqRdUFT3CQkf9a7mds4SAJ9b
 Uh/4pgPEMHVqh/mYuabRi+D0vYhGBBARAgAGBQI6Zft3AAoJENwfuC7pkT1X3MwA
 oPeTrHw/8GFopppT/LtI41zM4NZ8AKCEPsKoGwmtolGYwCTGc4sZje1lTIhGBBAR
 AgAGBQI6Z05CAAoJENh2/K3Z1dz40l4AoLHYYCgZoCWLtS4ybw7MZK5ZbIkXAJoC
 C5q0lY5Kg+UReRewOH1vzz/wyYhGBBARAgAGBQI6gqxpAAoJEJ0r034T/C2b5uYA
 oK8oK8CubWexgX1rJoKRINWBjEtoAJoCOat7l1Q6xjBN1E8fqn7f09Vfo7QnQ2hy
 aXMgRC4gRmF1bGhhYmVyIDxqZWRnYXJARnJlZUJTRC5vcmc+iFcEExECABcFAjpB
 aRwFCwcKAwQDFQMCAxYCAQIXgAAKCRA5tobg/oF6UJDOAJwKrq6xPbruIKSiL3O0
 0Npnq1h4yACfXIkxgKsR5KxKk6kr58ZxZd2Dsn6IRgQQEQIABgUCOmdOSQAKCRDY
 dvyt2dXc+AxbAKCzZ1Rvjn6P2kLaCo7/2A6LOetihQCfdL8Wo82cTXSpsGTJg4LU
 FjlE9XGIRgQQEQIABgUCOoKsdgAKCRCdK9N+E/wtm+CiAKCCd05PPCM3ffd85LKm
 +cRR3PTybgCgu5y+kYYTJB3hBchxggLCrJ166wm5Ag0EOkFAfBAIANHkcMb9WQWx
 1A390MV8UFdR8eqiYZfuFHaNwgT3Ou+0QcawP6uC9gbeqEpNnlHrE3giJvP7BrNM
 zut7Y2Ca5FJ1oy0m48OwmZY5AP2lN1CsIoU1bOCQ48R3KCB6Wb2dE442MEdMen73
 +HzNnLiFGwifqn5yAHVIzfKilhpRUFr5lbZJkBk5NIc+Ny+ZK1JHXuJZ3jdKFBu/
 Gusip9Dpd+UANyF8Tq+S3YfP8lFu7zA1JAHu5LnDOo/K1gZ6EZJxc5hYUu98Y6Xv
 6EJLEwjKHNZLI8skX2uXR/0zQsZNz5FbSVGdQfYJlq9q3eDZBBoibc4Pf8LPOXLM
 HhKyj39FE4sAAwUIALTlJVYI4353pzebM8D9mtqXrXY1qusNqm63pWHosPuG75XT
 2hOmjuFFyoC7TEsMe57BUag3HiWyNR/CrVw9AppqZ1s4O/zAo4HlkJbZ9rhv9IO9
 FiTR5FWtNCArAQJWpflRMYuVthZVVTGEM+zx2BTNhBdU4LEtRMz28E/r+tn72sMc
 ypZv6/FSs5Rn0/rO4zYiIisk3ZLYCbJMHQIxjAIdwH2XJBYbbuyN9GbCLVOcIlkt
 sbdwCNIQXY7rBX7g4Br16NCo0g35p/92s9QFFN6GJIzdOpbq7JVHnkZhMLfJgGhm
 JIS85paJGy0bbb4qPnE+Tmi3apYe3tZ8FjkKRfKIRgQYEQIABgUCOkFAfAAKCRA5
 tobg/oF6UKe8AJ9QmSqCD+d8ex1kMxJ0SZZqIcSO+gCfUUTrdZCUu9yC3KJIjvzH
 6r7mPk8=
 =R6MH
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.95. Brian F. Feldman <green@FreeBSD.org>

 pub  1024D/41C13DE3 2000-01-11 Brian Fundakowski Feldman <green@FreeBSD.org>
      Key fingerprint = 6A32 733A 1BF6 E07B 5B8D  AE14 CC9D DCA2 41C1 3DE3
 sub  1024g/A98B9FCC 2000-01-11 [expires: 2001-01-10]

 pub  1024D/773905D6 2000-09-02 Brian Fundakowski Feldman <green@FreeBSD.org>
      Key fingerprint = FE23 7481 91EA 5E58 45EA  6A01 B552 B043 7739 05D6
 sub  2048g/D2009B98 2000-09-02

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDh63HoRBADnIWpOjAts71A8JG07tKjUYV72Ky0nWN9HAtS8FJTGeT1eXwGI
 Wxgl0mTrmb+fUWuEt1xyB+0h9uzwbWgrojBiVEyPbfdORFvOlWQ5VXub41vxz0Es
 AvQt/HptyH5UKPHCtK/5WbgAHPZldlp5rBPA/E9OnsfgVeSf23eyqkup8wCgi7g5
 nKKJ1LaE0Y1eVhGLaOSYP+MD/0j69SjwjUpIAe47u1SJLsx/K+vP6Mx7oqw2gD1v
 Ap6sJnpNVx9vpr+DozYGrGFb+LnnML2/JqU2OQswCBRWmqkATJDrrdg+VyXIdyXV
 slk/6paQ/qPjcnyLFXWgQuyoL1me+4e36LFCxFTRVcfvO6kidOXGmDQ2ue/Khjef
 XLRWBADK40RjC89IrGX4PuapS9fOSj++GfWHZsdxuxSYT205sZhMOiTECR+DPZ5p
 06si2rPf6GbS/3zPEYd8J5wzHTS5kk3venhpxjze1ltloDQm6hD7/yJdK9poBa8P
 kRuEYqM8RNWpwNKu1x8SsqyyYy/JzceAAXs1zAs3g7CoLHGag7QtQnJpYW4gRnVu
 ZGFrb3dza2kgRmVsZG1hbiA8Z3JlZW5ARnJlZUJTRC5vcmc+iFwEExECABwFAjh6
 3HoFCQHhM4AECwoEAwMVAwIDFgIBAheAAAoJEMyd3KJBwT3j9EAAn0c1DQKEVawy
 t2zfgVxyIYsw+ca+AJ9CrtFiZ3yQIp0Y2alhcRBhM+13I7kBDQQ4etyeEAQAhBiJ
 oc5q7eotOiSkna9BDGxlxg8fM2+wb/MBTrOUZ+BkbsVYRNBQnzzYtczS7uwXt4Fc
 Oy0iBD+uOEhVDZgXNQLFg6HxyN+xikgWiPx0vKjQVIfKB1R1Uqh2VIslGc90TS8f
 WTo+7gkcwR5Kjq6m8rs8qeFa0GqrtTP+bRBoj9sAAwUD/AvVkkCNJK7pRWDWVSJk
 NPmvEJ/8i+YahBLcUkg+4H8nSh+fNdhI2ED6CN5ZU7yYiTN5iAc9HJLDLFzHRIDX
 KyGS3JqzwrT6+HKTaS2fVKFVeGVgzlTvczWizabEZAOMQOrV3F46ei4STqBjM09/
 nNhGlL2ce641KZ6zgdtCG6PaiEwEGBECAAwFAjh63J4FCQHhM4AACgkQzJ3cokHB
 PeNuVgCfdFUKo5EQLwqnGxcw5zAzqDnFVkcAn0o58BEAPRr2RoAHHWWJn5JoyJD1
 mQGiBDmwog8RBAC+zE0IpGNV1naZh9os6S//ct1MfEMBoHH2TQhajIfLVraWA1I9
 AbOTuYYsPgxqK44ZnPUnNLmgIRBeVJXklXsdvjtMrh7QMj7evAGneT4vVdVj/9aY
 7mEBuQephgvE4bUM7RPvOc/paiY08+HANljrvxcmMhygDTP5SEp/QJn7zwCghB66
 YVHI5u4xBAcHiHbyJWShmekEAIUWEIL4I33C9/yuenYogKLLS2/wmMYMCM5uMTkF
 jls9KtfW/TQz8M8ZU6xdVBQjvDpw9G96l78amjiMN9Gm32C8m3HJaN0V+4SGJjiQ
 fL07gu60LG0phnk1CtWLVQnH0LuIyB8jJeoaeYmS2Xv0rLLeMQ/hgUcQB8xu61Z4
 n1shBACf1w7B9ivEhBGWBsjuX2gTfW2eS4Mprs7FD1/8f/wbdvhitMdjZOFjOIO8
 yi/2W6B6T3suTcUgdC2qFmXkiWUun5kpGp/KRvrYm2eKpfveOL0HgD7juEZtBJcT
 zV4oMel8TlZidIjIgLUeTbGfxbYPm0gONEGZHsymlZg9/7sDS7QtQnJpYW4gRnVu
 ZGFrb3dza2kgRmVsZG1hbiA8Z3JlZW5ARnJlZUJTRC5vcmc+iFYEExECABYFAjmw
 og8ECwoEAwMVAwIDFgIBAheAAAoJELVSsEN3OQXWVdUAnR13DerFrFdS3xufFox/
 m9T+VKs6AJ0Y7mgJalqPTTalJB3fbWUeIsZBsLkCDQQ5sKJfEAgA5LI3C4rGWWbG
 cGZMLDhuBhjcoSFeWnrVVVZAPEm92+LcrfoT1Slp/2+KcKTJN/uQA0EpNmgUFBYr
 3vSoVoVm10xBxBIX0zP7uPQNYKoJX3gLBiRZ3xOo4A6VqEpRbo5yjj3rshN4IO9B
 T9zqx0ZoHSSsCds0Ax/m+0eSTghl+Shle1tbJstgcoxf6peKa6XcOAJWtQ+r6hZB
 Z1tpjmIrfaeG/26da858C4TcogNhi1cpbyfQTZA7070JBnpRjhcQpELT4hRsJV2G
 BX0dZn2hJOb5J5zl2M0N0Yx2BHM6mVT+oUc4EvfRn6fuhVRwIuckxwXaA31vWNPh
 v+S9VD5BqwADBQgAjOXR9HNAh/teG0p4ynOlWx5G+tBWSfqWAKOSpi9SKb2Zipjg
 bVNjmO4zNYhdAK6YbyQgrDrwUVPWoc8OieUACujklkY11eg8QFGr+tJow7iCMOPL
 ES5vW1sBUl7dN+4tf5QTg5q9EGHL2rTndEVeutFbcKPR8YQXdu/U5hdO9zha5fd0
 RWjG7zLTaukO4mT2bTuojgCrnsvZ4D0XRW+SUcfXZrbKcsoFiU3q+EvlOuWg0W5b
 FcFfAXSAzC2CpZlQV3hhSDkgeM3cbnb0hv7feSIizFpqFbNyOgarqymZIU07HcX5
 c44etbO++GQ/tMI7oCPUb9a5jIt/YqPvIvmPDohGBBgRAgAGBQI5sKJfAAoJELVS
 sEN3OQXWr4MAnjpZdSq11IEN34VjwhD+eBMcxjqaAJ4yDvFd8u5ehurCY+KjWSXo
 uPPUsA==
 =oR1w
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.96. Mario Sergio Fujikawa Ferreira <lioux@FreeBSD.org>

 pub   1024D/75A63712 2006-02-23 [expires: 2007-02-23]
       Key fingerprint = 42F2 2F74 8EF9 5296 898F  C981 E9CF 463B 75A6 3712
 uid                  Mario Sergio Fujikawa Ferreira (lioux) <lioux@FreeBSD.org>
 uid                  Mario Sergio Fujikawa Ferreira <lioux@uol.com.br>
 sub   4096g/BB7D80F2 2006-02-23 [expires: 2007-02-23]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEP9+FkRBACKcQPLBb7vcUuQTM+Zqfwsd44vzULREV7qHVvTqJWDsFyQd4hz
 /rX86mmHiS/fOh68SonP6QdXO2i+d+LshgLTVPBlW92TXsFYP09FUWWx2dm0P249
 P7xoIcQ7slhHnSVuPDObzm5T7yDXL02OeO6qonN62IjjxB8xzFo+W6SsAwCg2BtA
 gvPq1hyeXVXlbItG/9Hbul8D/0yjvmED7dj7eQpm6LvjswjkMoRdg6cgR+/N9LdP
 GIdjGHkfFnW8hRg7QAPzmstkhtY1I3zEjVVCcYjJrIibaqBAUAx0v5HszLKKRnrI
 ZZm4IXKFpkVC2sV475FpFTPXIiHmyzq1lbpgAQXX71yFNJ7hsEuYx1z2Ihblz/B+
 KHJ8A/9UNVEPc4s2YgjntQSDWRY+Vcr6M4bN/+ogCJ7XYN5lcHjB+gUD8kAWupEH
 1hDV3WFahpG1i0MusOZM+dggTXSshd76z0JlOJjbywEv2Z2nb+1b1GU4EY+2RlTi
 nP9rO7EqtPhHjNkpXfsSHFOC3qfcsDhphXOJeOFwwhMhkxmkHbQxTWFyaW8gU2Vy
 Z2lvIEZ1amlrYXdhIEZlcnJlaXJhIDxsaW91eEB1b2wuY29tLmJyPohmBBMRAgAm
 BQJD/fhZAhsDBQkB4TOABgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQ6c9GO3Wm
 NxJtqwCfZrWhCzRFNX2TkVEW1zMS0mw5aLwAnRUNKvayClkvdqHMLksYTFtUu4RT
 tDpNYXJpbyBTZXJnaW8gRnVqaWthd2EgRmVycmVpcmEgKGxpb3V4KSA8bGlvdXhA
 RnJlZUJTRC5vcmc+iGYEExECACYFAkP9+lYCGwMFCQHhM4AGCwkIBwMCBBUCCAME
 FgIDAQIeAQIXgAAKCRDpz0Y7daY3EiNhAKCLZTyIxlE0tU91Cy6YxRKCu1Kv5ACg
 rbLcuizHmkAx/du+XaG+aveC4Ui5BA0EQ/35pBAQAL9uIr9y2BwxMeHbj6LLmoPC
 DmQnzXWWWIZPtEyWlUv6ANLvtNX8M0ZWzfy4Z4EXof6/m3Z8KsAEZf22AObR+CA1
 mgRRmDxVfWDU3fYYIVwMTQ/IqjWz5TPfldXySqxtW/Zm16ODYv3c+tnu/KX/M/WQ
 1l9pLfIB9G3NlnHwHTWBdIQhomXLzurW0yuq4LXobA/nQmOWmrQwjXNk1zzO+p5t
 v18thaXoF9pGObS86oCCfwaUMg4RD6PtizVUSA+frFmcR0/kpNGAWw4gIqHY++9c
 Ri+Tjvbii0ZhBZNb3l2spqhg7zMAqzQ/wR0kJt09FegN6vClMLDBJW5Rveb7u4XT
 e01JY5E9h2Nt/RaJQ2RgaoD0bNLx32Zda0GOzidFAK+0QzOGvfMKimaye3YkWRXg
 GFZFHH4k0FIcRd461ta4aN0VMKbpRbYxZP8oxmN3VrJdrf91Qqton2Ljrqk4ndQA
 xb6zbtJeobx6MiYlDf4GB4Wgm4g2L/BYH+ObV5QqnTnwMIjP6Y3BvP941d7eX6VM
 cpJq3ueDK+FHbF+KEozHycvlZrj+el5SuWXtNdOVma/DUQjHJ1DHMmciVqZwArnm
 Ygg7f0G7dMxBi4n4OdHHSkJXwth4ojbZf+zDDQnHmt7J04/EArgEvBKxOGEh8EcR
 evS6bR8NvH7lfXjl+7AbAAMFD/9DHsJNi6bx5sciwo7xvwx9NZY2MTHBxaWV3iWj
 9OIoiklZt8Ca8a4ukDc5d2t/DrGr/rtKsUyQ7utEhfdKr17TYZH9mW9ZzOKp5sjO
 aWOcmFCGMjemejPedAlH8sBD4I4zg+Ph/tMRgAjyw/ZkhXlUbVJ4ooibU1uix5Wy
 AcxXSyrCOCLbVfpcCphiXCRlFsVuyiTkjM1D3STr6M6YSq5vTpbWkUvHs9c1pgqh
 51SoGR8tcyUM3JUvY5fTos1sRlIS6XexXEvmBe51jcuV+4I9cI2cXWVpWU09zBTE
 mF0WSgs2pXZftMpbLwaTSjzGA4VNQQ5jocsfWUP58HgBCyO4x8G+N1A9PWYtKUoB
 WVcjjl2ak8G0mbTGb03QaIDAy2CVkeKYVws6ZTQBZtfKiO8Vz2UQcklRNTPTxYHo
 69kIY47+6WW44huXc81ACGx2GXXDZtqxasysRtzAzl6U/FKy2lHE7Buyjh7VKYI1
 7IncPhl/XyEBWTESAppWvd3WiCdT0zq6wpwxrdpLprWblqxLRttK2Emwe2KhvDk4
 3jdj/KOlMi2OUa600mbRfjX78MbNHisLUEG1ceMXaQY3quaerb3Q1N8Rptn8sT1U
 RMqbVlP4fxFwJg9F8nyLYzBcVm1H9WGFoojCqQ3htuvI8kca6I/UQxHG7V9Meqbm
 uFqP7YhPBBgRAgAPBQJD/fmkAhsMBQkB4TOAAAoJEOnPRjt1pjcSt1UAn19TWL7b
 atBvRWIroNaSp6+y2jWHAJwMSHg8w1dVEw3XxYR1fhEhE1hBWA==
 =lXvC
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.97. Matthew Fleming <mdf@FreeBSD.org>

 pub   2048R/A783DAA2 2012-11-22 [expires: 2016-11-22]
       Key fingerprint = 773F E069 BE98 CE96 4AC6  B8AB 1A1B 255E A783 DAA2
 uid                  Matthew D Fleming <mdf356@gmail.com>
 uid                  Matthew D Fleming <mdf@FreeBSD.org>
 sub   2048R/4015B7AA 2012-11-22 [expires: 2016-11-22]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFCuekUBCACkHoIh2nUlNPfiYBtDsfHcNhFhEsTdDfkNehRjZ3s+1awLJlqJ
 tHCVH/EW9qfwe8zw402ApJDrY335Z2kNWwKAYRzi83v/LhWKRlg6ppZwPFOEHuy1
 COlNTM/zDWSt5Iz/e3FSZfZojo5qzd27Urnox9waDv19XL/oxw0un99rCveCpkq5
 J9CjfDJWGgzQgN557jZb7AICHBU7YtUmieyelutaWjVmPNmrg6vPoC98WvRYCzL4
 +tKMssvEC17Eh3ON8gFqwooX7x7o3v3DlIk9twZ2EUVSjsDR3h/10G0+mql9Wev+
 2W8B9Hug2PYJo0DQFySIk9kqsF4UTWzrfwY3ABEBAAG0JE1hdHRoZXcgRCBGbGVt
 aW5nIDxtZGYzNTZAZ21haWwuY29tPokBQgQTAQIALAIbLwUJB4YfgAcLCQgHAwIB
 BhUIAgkKCwQWAgMBAh4BAheABQJQrnpyAhkBAAoJEBobJV6ng9qiURIH/jABasim
 3nP4RejGOOjO0o5WJIAtVF2eIXxHqBbHN5fd0550VIc5EaN85zoUsFtPxDdA1HJU
 oJFY2TjF4dWA10JoAAkRaxQVl4XXd4BjHRNuObjdda8t631k68fjO1SPWLutOC2T
 kQx2CjxNx5FHosd5J9YkMDfEPSFOqEO8P5sc6MFmtB29jHm1XLQvqdC0DuDTBQe8
 feLMA3AkCZj3NhzrslMBij/nSUreOBxv824E9CnBvCwkToYXNkvhIRw6cyJ8fCrt
 jKTSMYnLfGv+IJ5+U6Oe5+IQGjNA3iRghxxmQwta3IKu+5QsQDeqlrqOTxMdyZW5
 qD2zWa8sUt5TUby0I01hdHRoZXcgRCBGbGVtaW5nIDxtZGZARnJlZUJTRC5vcmc+
 iQE/BBMBAgApBQJQrnqIAhsvBQkHhh+ABwsJCAcDAgEGFQgCCQoLBBYCAwECHgEC
 F4AACgkQGhslXqeD2qLP2AgAnUy3PJwZHgDdr5oEqHxVCESOKsUpM3LYvp4YXrJL
 rAcVPZbdWN0ZfkytxZNDQXugiIEMbGgsuOw59f80L+GBHP1sHiTR9J2oEUtg/bW8
 yyqjFSE3fc7maKf/0pFskC+GGyFjRxpMj13oCdMyb1/mn5NjlCJjtMb+f7fy+8Sm
 m5rcBxTWiQDM3FJrNH0WmP9EVYtsBbBkSqPRRsVsbjFTSBzdecTnzJ+k64NDzmw+
 Hss1DeJtcVncykCbQMEvnwmeRvaiCU1kPqo7SAeQZxgbIBc0DZEKYXoF+QEmxGSR
 ojSV6wEIt4YS8Jf1ERvF7uiytXMXA7tfLGpeIyTEpgWrWrkBDQRQrnpFAQgAm/oq
 amIJqQdoQdKiy1+fsOvyULpkDTwzi2nx/A/Jmgh2UZp5ezuGDILfLklM3GbNUACW
 KLDti59xu74x3km7g2MrVHzWzl2Xc0NZDk3sAE2xohrMq342w5ckUXLCuMQ38zU0
 BqQ1jJ6yVeu1zQg46q2NbeW4TA96a3Ac1arVphN9VjrXFCUVeGQLPFQpHklRIZPC
 mDzGEibZvpd0WpJix6E+MOhmDBaoWk0Fu7i6sSD3z1CP++kv9UYItrgSJCPM1Q1I
 brA1AN3LaZBlNoxBIPtXmM1lSQFuimlvM5ECmJcgbXYiJGP2Sd1AWFQDxkqmRhN7
 4MBnZIE2nzIQ1nAa2wARAQABiQJEBBgBAgAPBQJQrnpFAhsuBQkHhh+AASkJEBob
 JV6ng9qiwF0gBBkBAgAGBQJQrnpFAAoJEI7H4BFAFbeqDBwH/R9b90wBmSTIBKrQ
 M5k1SU4AcsPzpBkwV7PmXNgsolzlP6yDPeovDx5sHBKdZwNd/Ac1mCCjAgnbFFy4
 b0s7syUtpF7Bql25kCzgqUFHfrdYqvC99J32a1mJze3U3bNydCvvF3wKVH9RiSb8
 Gu7dtdOVV9rXbloF/sDzOnFsOuZMjDP9wovTZLLP0ohKDDG0sb+ReBa3Om+p2xUq
 NiaZL2VQoOfT4ptjhNJEiokfCYUYh8bjG9stAbuXLuDaCWg5C+7uyosIQtuojzbj
 9Ss1NKe+2SPSq+4a4wc7I/Xa5ytOYyJANYaAyPpnFoIc18VY1hi8eWHnbsXNv4JT
 +VZOWSOeWAgAjXryQBZ5L3zamdC/YvVHRLyeQ0ZoHihRbOdNygFTIr7NnR3NUrCT
 gKB/I5kzznroNc8NsR3Vhsfs4XVbb5EIYb3gi3b/0c0j5JzcD9/c/SHuf4xtgu5i
 nx5UhQYTceNmDnjact7UUi+1CdqUN4Pyt/Njwim/pW/ZfkvSM2fWkTWshngYVnXu
 Ph4pEb/NkOXG3csWCM0SfjJz1xCQPkTBRoz0d6f2pUmhPHwiGpSbMMlcrO5Pfk1J
 dKK6o7rJO/Ts16Yq8Fsh/WA3kJpSKJ2CrzIhKWKcBOoQh0L0qND+ZX3dNgb9OURU
 156vpSWN4W+DpFUoSSRJYJNqlyOf13a1rQ==
 =BME2
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.98. Tony Finch <fanf@FreeBSD.org>

 pub  1024D/84C71B6E 2002-05-03 Tony Finch <dot@dotat.at>
      Key fingerprint = 199C F25B 2679 6D04 63C5  2159 FFC0 F14C 84C7 1B6E
 uid                            Tony Finch <fanf@FreeBSD.org>
 uid                            Tony Finch <fanf@apache.org>
 uid                            Tony Finch <fanf2@cam.ac.uk>
 sub  2048g/FD101E8B 2002-05-03

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.7 (FreeBSD)

[encoded data, 5214 characters]
 KnkOqXNQ7FzYXOIPK74=
 =7TEa
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.99. Marc Fonvieille <blackend@FreeBSD.org>

 pub  1024D/4F8E74E8 2004-12-25 Marc Fonvieille <blackend@FreeBSD.org>
      Key fingerprint = 55D3 4883 4A04 828A A139  A5CF CD0F 51C0 4F8E 74E8
 uid                            Marc Fonvieille <marc@blackend.org>
 uid                            Marc Fonvieille <marc@freebsd-fr.org>
 sub  1024g/37AD4E7D 2004-12-25

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEHNnEURBADK+anixdFH+aSxIGLw1soiwMXSiVPD56dmoA/VAFqrE3XVo/y6
 bPqpSNwvvhL8Um2v9G/7EDMorqekYErS3sgUOtrA05NSJlOUJk/97ZFzAlGZ4/u3
 CwtpFBdiATaCvAdMocWhxVkyIFvo6AqVNz6RkTldJUuwVzGelXWk9IfI1wCg586A
 r7CU9HIsVJD7/vIbIIsKDncEAKYh6XKEBHWI1pF3Ony+rPhlXCV9W3yraiBb/YXS
 XaPr2Wy3XC86ufHZs8ewug40DqcSfRobj7qV5II1CMoVrwhUuJ9Y087ETjt7xC9d
 xI4jrkVZlaRt0m/LUKLLfz6L9KaLWRkBfFhOjJH6TAv779q0n/KfaiU48Xuue6ff
 KNDtA/96/oTg9+NWjm47zCdQeyZGzEE27btvzbrLZuG6TcP7gAV0F6udGbImgw1f
 mKrQZn4ZtVKCKS8IzTn/UM/P26Pn9JOzDKd2voPE9Ee8D0L8ywg3mxmBdm+TY9vs
 r2OEV89Nc2sJZm5CeiqEvfACI8KwbExqWy5TW7Qz+zLi3zk+ErQjTWFyYyBGb252
 aWVpbGxlIDxtYXJjQGJsYWNrZW5kLm9yZz6IXgQTEQIAHgIbAwYLCQgHAwIDFQID
 AxYCAQIeAQIXgAUCQhzb7QAKCRDND1HAT4506BdRAKCaBqu+lvdAp3fhgIJxL0XY
 YG6vhgCeIyaLMYFzQfii5s20wePEhG3rfMq0JU1hcmMgRm9udmllaWxsZSA8bWFy
 Y0BmcmVlYnNkLWZyLm9yZz6IXgQTEQIAHgUCQc2dRAIbAwYLCQgHAwIDFQIDAxYC
 AQIeAQIXgAAKCRDND1HAT4506PmiAKDanV0mSeUSRJuDmfA13o4ELsQ38gCfaEgn
 LyzKfRawEhJdqsGPWW/fnte0Jk1hcmMgRm9udmllaWxsZSA8YmxhY2tlbmRARnJl
 ZUJTRC5vcmc+iGEEExECACECGwMGCwkIBwMCAxUCAwMWAgECHgECF4AFAkIc2/AC
 GQEACgkQzQ9RwE+OdOisEwCfY8xxYIhN0w9CSUbsN1/EoYp0D+gAoLedf7wiwvmQ
 O0XpcJaXgtlO4x6fuQENBEHNnEgQBADPHKv6eOKxk2HPrm180rVAM6/d3LQkBEGL
 Ma4QuSXXbTDXpzfrt6YOLi+ILe/hu5DNnGbQyvkBB1lLdmqW03lat1ape9wytNoA
 kHOX2C4kom2WA3FvtAoxojmylEn8S0koH7RUuhhTM29rVBap0W+UpwpnxmtbGXEO
 NciLWy5CzwADBQP8CSp5Hh4+7uXIRpp+RQ8PKJ2vQVnf7c+QTPDN5MLXEv1UK9gK
 vtb4sms2yr2IuBMP1FSAFN6DpedjoZSKimxqCyMNbyy0io2pMrNDCpqCadKOyLWN
 gJhJTxE+3kYeZqzZExvf8q+faQqXp91bbS4XZ4JzgAkT3B0mvQ1OHlVlAauISQQY
 EQIACQUCQc2cSAIbDAAKCRDND1HAT4506PAVAKCWlLnQdfJsRZtt0Q880glcLzc8
 SwCg47K+qs1q5klc1cCIaCj+/TtsLCk=
 =rg/z
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.100. Pete Fritchman <petef@FreeBSD.org>

 pub  1024D/74B91CFD 2001-01-30 Pete Fritchman <petef@FreeBSD.org>
      Key fingerprint = 9A9F 8A13 DB0D 7777 8D8E  1CB2 C5C9 A08F 74B9 1CFD
 uid                            Pete Fritchman <petef@databits.net>
 uid                            Pete Fritchman <petef@csh.rit.edu>
 sub  1024g/0C02AF0C 2001-01-30

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDp2C0ERBADDEONsb7B2tbhvATFEmuw64H7A+W9Kk6NMunEF9kp1VguwRP2w
 pjtAon2QbvM7HABE7t3IHnDhhS61kLpN3Zxdxwt994s+jRMZ1s/p/XIP5/eIx5ds
 BgKZk45sm2qdg0vRKAPF+On5voQttbBvBdOVMWOmr60Fc3I+BTNuAgaEHwCg++GC
 1P4Upv9OHJCQ7JI7gKa3qQcD/3HWzaGMwyuvcuzWFDLpfv2kuYxNutg75+l0K83p
 hCFxorUVw16+j4r1/464GnTAhvfp16Z7ReODy53NOlG9/fQXAE1nHZp93kFnkgLF
 uIQZQKTiYsHP5eqt42gOGmX4lBRpJlpTNsdlSr8CC9VUvzqZ+H6wG4epDE2jUnFD
 +kmRA/oCBoq5k3Hm4gyi3Y1F8cLUGU9YFDzhzTkDQiZc1Wqd/QlnvMW6vci7MRKv
 eeeZHQOpzOSxzuPo+b/Prn1ssluAi2IIPObxrq5Gcz9lQ7/xqrvQH5EosbpH5zQM
 35ku8psPGcRqcRKG7OecAoYpioLLWc5UJ/SoKAoxqzecICf3qLQjUGV0ZSBGcml0
 Y2htYW4gPHBldGVmQGRhdGFiaXRzLm5ldD6IVwQTEQIAFwUCPCEaTAULBwoDBAMV
 AwIDFgIBAheAAAoJEMXJoI90uRz9hSgAn0Yp/3lUexQCv3MEjwm7l7XhZi5IAKC8
 Qnw/RCmcFjahkHQTXXZmW+rSwokCFQMFEDrzKkoSaX0gm5SkDQEBszoQAKvEeQYp
 zt242YB6MVU88HavNYkonemSqA5s1fbg3dwA4TT6TTJ/757W47vbFnzjb/AmGIJb
 r8moK8rC+6mnSC2IewsaFqkDRFSRp42XLxyVdwdkJKY/L0Of8rOpWlUsW/Zk6dIE
 XFUs+5bjSEO9DiMQjmd4upPTF6r4o0jddW+wn0thrqNk+3ghd35q4HjtFnYMruMv
 BKzLUYfyLkYA16w45nOF9Lr1Tz6oNzdVEJXrubpdHsHMs2sFQlrnD9A6EMog/ouD
 g2N1ASr6UycE9s2nyVXM5W0WVahAhdMosrUCuzDlhGWv6mQqjTNZfl27/+LJd5sM
 QEv0MQoTf/fzOI7kJdPsNGTibnnTuE99atLXpbNhsKj82BjYgAAeycutTw3Qy6CX
 B6fpdWa1PE+BNSdOUbiAtxyV4XPcw84C6rvk7mZepYVBYPKUrupPM9OY1d/mCEE4
 zDFv6o9UjiZabQmzKq7T8wKZgV+Pl14dpHcR+xd7tZP79duLdyIkxOe6Z2xbnqY5
 NlOar2AfMNtes7GIkknx1p+2koRfqh+W1mPH02Vjgi09ru+kY27jzxHmswRlu67q
 3r69rGouXBgIJQ1OnyOPXLKY/iglgkRIXGmAoU2R3Ii/X0lsQRYA5XdtiBodezQd
 gCuJ1XfK6W4xWjZsONGmEhNN9RezUJKoMSeziEYEEBECAAYFAjwhG2AACgkQF47i
 dPgWcsVClwCcDW2kRANOyFNhbBhDE4OHOPTAau4AnA/8TasNnyJLhAxeYFiQhpuI
 fiRDiEYEEBECAAYFAjv9fJwACgkQXvSymrg2XlXuQgCeNou9DlCKpHZF7os0/9K3
 xV/hva8AnjNqFXvpIZPylro1vJkzgHh3I4SkiEYEEBECAAYFAjxOdVEACgkQ2z94
 QKW3O1wm8QCgx5i66wSVMIhs+Yvb0He27mJFW64Amwdkruw5+oN0NUm8HHHCAqFV
 S4HitCJQZXRlIEZyaXRjaG1hbiA8cGV0ZWZARnJlZUJTRC5vcmc+iFcEExECABcF
 AjwhGlEFCwcKAwQDFQMCAxYCAQIXgAAKCRDFyaCPdLkc/VorAKD3J94O/gJeEgYW
 R+adK3SewjnB6QCfQK+70Io6Jlz3GmoS8+/c3o2hSUyIRgQQEQIABgUCPCEbYgAK
 CRAXjuJ0+BZyxSERAJ4z//S1Bzb2OUl7ozm899AYR8W1LQCbBkDibniWmMf6Gwy7
 fL9Flyks7yKIRgQQEQIABgUCO/18pgAKCRBe9LKauDZeVd66AJ44EAAjhGopDGym
 iCGXJV0EvKo01QCgiGW4Tr5DZG2mY1aqCtBgl9UIz/qIRgQQEQIABgUCPE51VwAK
 CRDbP3hApbc7XBD4AJ0Q7a37xCQKlc/m1uxQ62JxgvgHWgCfQFAKfveCwE3W/Fpy
 +glLmP0/ZTe0IlBldGUgRnJpdGNobWFuIDxwZXRlZkBjc2gucml0LmVkdT6IVwQT
 EQIAFwUCPCEaUQULBwoDBAMVAwIDFgIBAheAAAoJEMXJoI90uRz9gnoAoPosyzKa
 niM7FvhR4xLDLaazqe/gAJ9eE0hFz6NDr5h9nRZ1qfU8BK6NM4hGBBARAgAGBQI8
 IRtjAAoJEBeO4nT4FnLF08EAmwXdi9L+Yq3liDz2FYledwRRqO8ZAJ9hax4xk4ue
 E2B8IogV9WHnnRSci4hGBBARAgAGBQI7/XymAAoJEF70spq4Nl5V7ucAn2K6WfjX
 4vncJacQLGLVuh3tMCAWAJ430sgOCEmwY2bAdNfu/+WYe6YxwIhGBBARAgAGBQI8
 TnVXAAoJENs/eECltztcBPoAn3zovCq0kHyFqm1x0QPDtlAkRG4gAJ4gCD4Le8Rq
 43M+s91wrrTyNOutobkBDQQ6dgtUEAQA3sN519zCh7owShpNYRObr//qeAZnPcx1
 69ZscNuVDy4EoKeyiLletkmnwNes1IDpq1RslCkHa8UOjFy0jby9cjePCJNo0b8Q
 5qG/4iJf1020PT8AMxvL/H/SZH27ueF6PxkpSgDSsz/e92c7CeYpTu+n+xBYsLO9
 GtNi5asTvKcAAwcEAL+HRDhWp0dDD4AxTa5evEl7GFy22y5sFVDHA9eukt70/d0d
 nAi5d14uA/LbAIWyLCE6KC23MAJOgrQSc2PbOa2O45rx3dDw5RoqXDqyn9xPM304
 hFzXgllOFOTYKMy6G4DBOv5KWKgVOx03XyIPqAVAObw3rHzewU0wXhD5Qk/QiEYE
 GBECAAYFAjwhGssACgkQxcmgj3S5HP24HgCfdErc/JU9fVJIH/iLTbWo28vu5yMA
 oIDNzwMAwpXoLZkEkk/dMUDTsFCy
 =ZbG1
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.101. Bernhard Fro:hlich <decke@FreeBSD.org>

 pub   1024D/CF5840D4 2008-01-07 [expires: 2015-05-05]
       Key fingerprint = 47F6 BDF1 DF9E 81E2 2C54  8A06 E796 7A5A CF58 40D4
 uid                  Bernhard Fro:hlich <decke@FreeBSD.org>
 uid                  Bernhard Fro:hlich <decke@bluelife.at>
 sub   2048g/4E51CE79 2008-01-07

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEeCHjoRBACSaB/CWwMs6NSHptLM0nqOigdiEMILpAOtekIVkzQ/0zB+G/fw
 J/vtVPoRZu0NlINwCSfnnOSpx0yZuX7CDJVVcGxWf2wt2Ly+1U/j5CnP1QV6dLhz
 iCbrvfV0GwXGvmJVhxX5lbVB3adzODgPa5S1v/Cj2Dbmqx6KFyMRsaepUwCg/dSE
 ZQdHiAOL7zh21WTtNbXvXqMEAIdk1WvclSjR8tv5HRQYOzlXZo2+EIeJklxNuBe9
 BuGNax1Su2R+Feq/qH0xSTayZmkKV1U7ECFq6PFYUpbn2aroSMmJTQKifsBk5M+J
 8Yrxg/tulUTiwi3FlrKkVyf3JNCmtDZbZGgCHAXUgIJbnHNzW2nRYk3LeeBJ4T74
 3VTZA/0Z8Gti+9zYP4RvCnbufsBO8dS7H3qMaaDa+Jnj2KYnLbQXhUH0hSRPePZd
 ylPSYMYhbvZxLF+kVoxRPKn4o5o524ECkO4tJuQwZV72xCRemyMalhyObfPUv3Pv
 2c9DTpeP6fiO+lK4jPSqjFUQ+wdJz/qxXYdvCnfperQftmGvILQmQmVybmhhcmQg
 RnLDtmhsaWNoIDxkZWNrZUBibHVlbGlmZS5hdD6IZAQTEQIAJAIbAwYLCQgHAwID
 FQIDAxYCAQIeAQIXgAUCS+MdjgUJDccA1AAKCRDnlnpaz1hA1JVIAKCMAnvJIfw1
 +r+G0Ke38mRrnhzJRACgnnSswoyJD0lvmZR8VIGvBOQ72AK0JkJlcm5oYXJkIEZy
 w7ZobGljaCA8ZGVja2VARnJlZUJTRC5vcmc+iGgEExECACgFAkvjHfsCGwMFCQ3H
 ANQGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEOeWelrPWEDUO+cAn3ccQBd/
 abvhD/0pllCsWvT/ULv8AKDx/E1tUCqUkenPB1JcIv5sQ6e/DLkCDQRHgh5eEAgA
 mjk/OYgnOp2A6FTh7AlWOVlrpo+DPQ4bxGXUYtudxptm3hUtaV64zWzL1EF5Ky7u
 YNuJw3CGHX6tDV0KZ6kYGphkcjkv9i/T3U1YaqTklgmbzkSgIcuCzHP+6z91SnjY
 VL+HG4egz3GPBn+vWORt78JxgLjLlLQoLQhAliQK4v0+J11kXMT5mZc6IUpilJNw
 qLbsMKPUxYV8bco3NTMfmkcdJah9ymGQOiRHsTt9VCuvXClnpDF7TpxRd/BICfdZ
 JyNQYTvVV0d/g24zumsyxgcI0qup+NKic/M3G/+4Bo+f57FRRndARktAUqc2NSGK
 mTlqsOuJZ0RPDmwGTIcPAwADBQf/dZUT6idKhsd0kpaHpX0V/LES8kFdh3mNiU3s
 IEOeF9jslZEg3Bl2/AmOIVKWheu8396CjqKr+vjmXlEKABj3YF2ARFj9yg/epZdq
 OGyVjWkw4JhigVmtbc/BhNX1uMy/SlBpZUIyubvtp21f8YOdLQcV2in+x/Vfovhj
 kp2ms7fX0PnfwSy3Q27B5bvlU/jPxsog8dJ9Mf0tfoEWs0DBrPkDjBbvwu0VM2Qq
 JOasZHOS2qAAnE77X0dkA1c1eQeXtgoLbqMrWdp6tS532KiTQN85GRMJbECocMUE
 pfez5pVX7oYxsotEqIfBHqqgx4Zv//oA0fE9dIAc+RawKq64C4hJBBgRAgAJBQJH
 gh5eAhsMAAoJEOeWelrPWEDUtV4AnA6B3aXqQMK3LGBF5RYuPqIf2BeZAKCo6fV+
 qu2NvCjYzT8RrLvqANb1wQ==
 =ucJ/
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.102. Bill Fumerola <billf@FreeBSD.org>

 pub  1024D/7F868268 2000-12-07 Bill Fumerola (FreeBSD Developer) <billf@FreeBSD.org>
      Key fingerprint = 5B2D 908E 4C2B F253 DAEB  FC01 8436 B70B 7F86 8268
 uid                            Bill Fumerola (Security Yahoo) <fumerola@yahoo-inc.com>
 sub  1024g/43980DA9 2000-12-07

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGhBDov9skRBADzrOg1JwL+kHv1dTePFR2lNrErbMe+WVeP1sdGuKcYTP15VQyJ
 WV/6ZoUGsihAmFGcGyJuhcUJbvlvqRf4ZlwD80a1y33SNxxsqe8n5dm4Wy9FElL5
 bjs4L0kGJlSL8KnYYUTQKEDBcTch3+GTjgS4NQBZWy4h0W6EWqgxr7CZYwCgpeB3
 tnDcY3ELA5EP6Bx8wZN97zUEAJo972g6HplZyuyjqqTjdztXNgD+DlsyNpNkEfqs
 AnZcr4aqEeyMNtGl8gPIc9JwPPSlX5OfmjCm3zWtEjwrHway6YPggXqX8efuY3lo
 LxVfjRt6NLI0TuV0FhojgHuJYB9RsXQFZxbYH8A/j6jQHbiN3wTyYHtaAJJ/iELg
 82oWA/dTeR0kjvjgrfB1MiFCH4AL77bZWuxSv1CvV09DlYtSxfLpyBm4OHvDZmOv
 V6zT9COM2+f2/EMI15cNllYXB3WnwfYit9tZtEFBl1+OshqYBbcNkser1pBd5jP7
 fDAkpDYGx5OgpqAS8hz4XLPZdS/HXSegodYKinU0p0Rzza6KtDdCaWxsIEZ1bWVy
 b2xhIChTZWN1cml0eSBZYWhvbykgPGZ1bWVyb2xhQHlhaG9vLWluYy5jb20+iFcE
 ExECABcFAjov9skFCwcKAwQDFQMCAxYCAQIXgAAKCRCENrcLf4aCaPIbAJ41RzBA
 OuxYwZFUSbMbU5PHENe6ngCfcnVzDC5+lkssh628m3GTG0EjINS0NUJpbGwgRnVt
 ZXJvbGEgKEZyZWVCU0QgRGV2ZWxvcGVyKSA8YmlsbGZARnJlZUJTRC5vcmc+iFcE
 ExECABcFAjvw0YEFCwcKAwQDFQMCAxYCAQIXgAAKCRCENrcLf4aCaMcVAJ9brBw2
 LPC2RcZpsm5S//dETM/qFwCgiuPpVVwBP7ibzn5xQVNAdB12xOa5AQ0EOi/2yxAE
 AL/FYZQw0b7NrD04j6dxrp7wBjgd19ux4zQocXgXPlzpBZxQ4A4/icGOLnIU+vDu
 ltbpf7aMTd/mJokJwx9pE82pOgxk6i42c5qKkwkmjhO2/4FFk8HXco2DJ9roRi0n
 eBJztXskUY4cVavKdXNeJY2JUeBYvmrnREWG1W2/0ZMzAAMFA/4ytkv46phPokQe
 s7yy67bEeHiydjvf3uM+v1z3xWoLw5ZU+8hLdFkESpZ7u+qA1mj3i7LNBZhfA5Bt
 Cgl10v9DWX9cda2HlMjyyI9p3dfPlOcAh69PMwexJ1VYPtizK4ZkC8dNk0rTVPOf
 SYftSsFGdDbUAq3ZokhjLkVRFY1LxYhGBBgRAgAGBQI6L/bLAAoJEIQ2twt/hoJo
 ewUAnRRikiShfD9wCuyMazVJ9+FZLWiiAJ0YFgos24sNEFq5rA4I8UZU0LZ5Iw==
 =y5FR
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.103. Andriy Gapon <avg@FreeBSD.org>

 pub   2048R/A651FE2F 2009-02-16
       Key fingerprint = F234 4D58 DEFF 5E3A 4E0F  13BC 74A5 2D27 A651 FE2F
 uid                  Andriy Gapon (FreeBSD) <avg@FreeBSD.org>
 uid                  Andriy Gapon (FreeBSD) <avg@freebsd.org>
 uid                  Andriy Gapon (FreeBSD) <avg@icyb.net.ua>
 sub   4096R/F9A4D312 2009-02-16

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEmZYYwBCADCrWmjbSj/846S7irndSa66XI//DVoOrTu/thqFyluQQmhhRuB
 +ndX79CWe2IRvr3l4bIaD3Lx2pq6OsUPWOsOAJSt90FGkynqSmO9MbcjD8ZE9Hkb
 mgqIW2NtEnCiVw20OlI2OfjhyavEcFAHxHsITRFVDlmjxutlyDkPmWXPNjsjfCaI
 FmzObn+W1adLT3r835x5mst9vBfuRFCTnm/yCHStkPTpW2mZ3njfDWEiQKc0ANaw
 EOEthnekr0jRvJmnC53JsJlwVH9yv9CY5EM5gVehmKuRok8NcVaPdNA7M9CATpaC
 eYQ+by4j5RBSMgXlFxhjHxM6VfGNv5vb6KG/ABEBAAG0KEFuZHJpeSBHYXBvbiAo
 RnJlZUJTRCkgPGF2Z0BmcmVlYnNkLm9yZz6JATYEEwECACACGwMGCwkIBwMCBBUC
 CAMEFgIDAQIeAQIXgAUCTZIc5wAKCRB0pS0nplH+Lza+B/9yy9a2zLMK9TmzETmI
 sE+1gPZiV5BjnM5lAFhdeENb23cRhHAKfzZ3k/A/op/Dzode5926x+naJ21fouo6
 2eZBckvQ1A3HZSST1aVkgjxGW3l33JkE8hOcT1cjrjTcf2eePsQ88roQaDnyqzB3
 rVq2sAvmREyNEMA6NoKImKZSzWEOHg453riYhFYGoxSf9UjpLWpn6slx0E6iNjwO
 J3yGBTuKufnRvV2PInFvZMWZV3G5NECT5XfHcEOswx4nKUx3dV2NYKkSqJm3rCHL
 qamRmCfYPIHTfrw46dLRzF018AhG8Rh5rEX1vho/Ooy9ePWLBs+nLXHzu+pLMMiL
 d5UQiQE2BBMBAgAgBQJJmWGMAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQ
 dKUtJ6ZR/i/z5ggAqDEr8y18n4KkBz8c9HckXLyNYSQVqcqBggKXPJ0Rvc40eSEX
 M0hQkh08c2rg0alZPuwomDu7/SiOM+4Aj7ICeIPrfYqLqrYwYFmnuNWWXgHerf7A
 q9pNP6H5DVS82M6ZNtNloeJ9E/q58E2OVDgGhcVSlhgsY1wfxlqXkbcJwFYCx9e3
 SIAzmYtVWkkTNpBMMUIQql5IieGIpjEbIUZ0Zx9+v3yxRmEut3HY+XkfWEPob4MF
 FhktdqDtwS6Y+O6KSuDFk0B4cTLPdB+E8WGXpgkqbscHLcM3CuDnv6MMEfHsBa+K
 rzszNTVedZaezkWLVYs9KXIApIZYweohN+Ps2ohGBBARAgAGBQJJmYZWAAoJEHw/
 DPwEk8oCXQ4An06+0XBfrYPk5+hn6PC1GRqq/WxyAJ4utLidh5rYkF1WYOL11L93
 gt04XbQoQW5kcml5IEdhcG9uIChGcmVlQlNEKSA8YXZnQGljeWIubmV0LnVhPokB
 NgQTAQIAIAUCSZliXgIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEHSlLSem
 Uf4vGu8H/RHu6JgpkTreeoxsvY/2aqtukLc+asDRs2l+ie7jBI7K+B4r/EnQxOdJ
 RO/kstvWD6oXjktlKRheyOdwP6Id8sgPryJIcFJbFDCAt483VwSkOBx5z/ZhOlYF
 3OULpDgS0a6dmzmOEQL1rjAOoHG5HOF7E0MSJHM3RtnCqD8TZPt5jShd+nCl3Cx8
 B64+eITAQlIWNKt4zCDvXA8gBvkdy4yJ4qfGOWoMRbvFDSetPJ1aeHFW8mh5V0H3
 eYqeaG1D0r8bpxXSrvkC7mrLRq7O2ZeLxdor+nJjEJuaFI9EL+7oGj0ruvHr4zG0
 ZfxhB3VUsLWR80LHcl8RMDw/VASclCy0KEFuZHJpeSBHYXBvbiAoRnJlZUJTRCkg
 PGF2Z0BGcmVlQlNELm9yZz6JATsEEwECACUCGwMGCwkIBwMCBhUIAgkKCwQWAgMB
 Ah4BAheABQJNkhznAhkBAAoJEHSlLSemUf4v3jcH/1/K3ismEtZOFHWXL4lbH5WS
 /XdfVyFvrZtDwZYtFZJYKv6KVW0uyk1wc9PMR7Zj5c85krTwUxMbYxXWAqxuVJMq
 2iqCkny8MSReJcLPYuBzmAaSIGy9MOsh2ZNtcXTB8zHAMH51hYUK+QPpM/HuTrqr
 4F+wLxnl0udi4BUbo3pIvxexneGdxxVi2mbTtMzjJGwS4JwnrGdmUJaZDDb8FL/U
 Ev98KIJK4HqXJPZYEBoSqwCgDaWh032l3JM5yZ+qsT9er+dwOhG+zHNliQ6bIkou
 2geD+/6//UmsY0gXsvLJrlhASQoXUZ72Mh6tiQpOvCqm4m25nYyIspnQBK7u9hu5
 Ag0ESZlhwAEQANe1Q5ZfTOc+6I7SS7KBrbz+Rdo0iEg6or7rrKUC62Vm8aX97yzB
 sgXzwQXBjD64DiJ1Lely+RRdE1Rs77/b81WHOYYBExtrcNXmbwxWqSs7Vxf8yBd/
 uB9n24sf2KhbVFKOeGXiB+76Ls6QF3cOmQeeyGR+Rk7Trk4O/UxUPnoGFTM7yuFj
 Znf5R2c2BfprUvZ1OdIax3BxqDAkTF1BvmdAYeTqf+45+2DY1qD5w0o5AcCOovOk
 0mj/3qUbFMngtaVgiEnQEUYpH8RKvFecaB13JAOjvcf8HppNtMiY/WC2vKeBI8XT
 VP4JB8h0agalQUabcXpMdA+J8Q5s0zFAueYfzfDOtjxjgoA3c7GKk8Hkj4rtaa1n
 bTgIGJ4of+gpuNSA+AmLOPrLAcSmxQWsayfvrMdCWIwjSkbqB4yAiffIdI11buH4
 4XmU9VoB/EuyxZ0eWft61kBQIKtMES+YMiEEEHb8R8I/2wgJx35hywHUlOKn163e
 m8Rcwbm/i9Myx4pc9RVSsz9IBsUebHOi3v0kfVrxLIwpqfUc/Ryla/+BW3W08WeJ
 5AW/hv+OU7HHnNTaBeNTX0MRe6BxjbDYT+M0iizIU7itI8Ki/wDYhhbwKq+WLvoz
 PHoHQv4rRnuwdvW8LQmdrIE21k+5XrphH1jIOMo3GosT2wEopaIbjC9dABEBAAGJ
 AR8EGAECAAkFAkmZYcACGwwACgkQdKUtJ6ZR/i8Gswf/WvKsYhmIPPzshU9e2LYX
 CNYSsoaayqcwpH4z2UzFOQ6GdOJqDaPYCvFS+gllkktfKJ+qXjvwMrJOyyONVIr3
 4XJTKc+5dX2kKMu/CnSNkBD+nfDotUk9Hd1Z5zGaNrPwy02y9KWqYASKIWNNFItt
 L0XEnMfW8CLWQrLzmKRlxWZPC1LkTnYVtxH7RrM3VTbBBfyeMypbdj7Wc1/kEu4x
 qXgTI6FhXkgTR8Ag1LGP4x32rzBSQtuMayhOSUUQZrJpcQYQpSl3j/AGaXuC4sHR
 pgpomR3B98cCUwcJuQJtCK03W57UmaATzhsOLAzTARzC9+OmDsItyFnveYUKQQEU
 wg==
 =/KPo
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.104. Beat Ga:tzi <beat@FreeBSD.org>

 pub   1024D/774249DB 2009-01-28 [expires: 2014-01-27]
       Key fingerprint = C410 3187 5B29 DD02 745F  0890 40C5 BCF7 7742 49DB
 uid                  Beat Gaetzi <beat@FreeBSD.org>
 sub   2048g/173CFFCA 2009-01-28 [expires: 2014-01-27]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEmAbU8RBACOi7LAumjK/zBMpQDMrR55L9xJh1vTYpiKayLth9ZPlsg57pa8
 4p93pSTs7XKcHIO8zqr+LpFFxtafUVoFwzDhwwhO8mX97oakPK/LG2ItUYYZ5302
 RX0UclTrMNt2UM+0nrTI/uoh/azn5S+gJNYYTEJy96QzOtY0eGj/dDvOWwCgg3hb
 fN0crXO6FKY+fshrgQUdKX8D/1PWjcXge7sM3tlR9z0ETZe35qEljmTXpT4sPky6
 KmUF4ymBqhWCTn10WQjuOjhEXhF3rHQ/omgOr/dBQFZefBtcYKHUBq3lvmd0cuFB
 xVJRQErw5U8r343EeaZOFY+ale9iNTfwkl8AyrkaazUH/j3qu4ZnGdf+Wum1P/SF
 8ijyA/9XcujJJuXMT717d5yY1Vx1Dn+aYLV4y3OiniJBQFP9CU2lX+Iw1sfuTGml
 zx8+RPTlL+S3+nz2XkiYwHVi6wlthhGIOgE5DfG1r9FG5PZJtBr3pQau9BilT1TU
 3rXZp2z/tkNEQTagSB4ObCAQ5bTOuxli41TPFuHxmn4Q1YrmkLQeQmVhdCBHYWV0
 emkgPGJlYXRARnJlZUJTRC5vcmc+iGYEExECACYFAkmAbU8CGyMFCQlmAYAGCwkI
 BwMCBBUCCAMEFgIDAQIeAQIXgAAKCRBAxbz3d0JJ20jPAJwOdzYWw9hZSEFtUf40
 lGSurerRAwCfWN8iMDBntKPMBt3j5QQWWSkPxx25Ag0ESYBtTxAIAK2WncBXO3CK
 VTcGY5jvbqKWsJ+JUJqZylaV3FW6YzAMKKw380m2khT823qgC5XBja+nm0IQn2ec
 34D3XKl8gjf4WWJog6y/DAnxvwdtsS+Wwq0/ownCF1pvFiIt1tAw54i5fmqpwZj1
 UPQE2IRc54y9yFdGNSuV0He9ZdJGxXKx2GW71rHlgWCfxXmD+GtwzFs76jn04bwk
 lj3YM/AVr+6C3OGrUv0lIzD26kPxpbZHPSx2a6imBk5HQKVsuYqqeI5ZMOnkbwPn
 GuEu7tVn0Y0lwVyBqYf1qe4u2e/38Kg7e/X7Vk/OTSh0FMJ5ZsakKUjedvJ5DA91
 gUJBmGkopmMAAwUH/jQX8T1IlDgmZN2T8FUc3hnQjcYdOPRJv2Qx2DeXK4OI4DCX
 KWxVGXeGVd+EpKgYCSmBYx5UA6MKN17nmoQei2MuVigxE07cCx6BjASTmHxex3r9
 EGl8luGmEkzhTajYfu+13dvMMQVYuyQTwB6dMioaw7j6lE5GBG06NvRfzik3mI5n
 ms487lKYcqAJ+iFk1a8Lbtof3xoHi9gYl3pWQ/rXirY8sp02e2FgC6iFvE/4+hD+
 DCdkkCZOJMIl23JVm4VLWC8Ak1Z5PnOXPzXwS1hEX1KjRyrW/Z1EwNcCK8zSNQH+
 bknf8dxan+46/iwig5ejA9N0lyy6gooFXeiYCQqITwQYEQIADwUCSYBtTwIbDAUJ
 CWYBgAAKCRBAxbz3d0JJ28NNAJ9II48hjLq4PRAYpsDHXGH+2wSr1wCdF1Kq1fEU
 WlCtH7Ew40yBxy/bVJ0=
 =h59X
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.105. Daniel Gerzo <danger@FreeBSD.org>

 pub   1024D/DA913352 2007-08-30 [expires: 2008-08-29]
       Key fingerprint = 7372 3F15 F839 AFF5 4052  CAC7 1ADA C204 DA91 3352
 uid                  Daniel Gerzo <gerzo@rulez.sk>
 uid                  Daniel Gerzo <danger@rulez.sk>
 uid                  Daniel Gerzo (The FreeBSD Project) <danger@FreeBSD.org>
 uid                  Daniel Gerzo (Micronet, a.s.) <gerzo@micronet.sk>
 sub   2048g/C5D57BDC 2007-08-30 [expires: 2008-08-29]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEbXBHMRBACh5wwMt0bmOk2lR4xDsjHRiJI8lIOUzLDmSW/1DJHsKQ+ipDBw
 lMg9cIx6Yp0JS6GQxhd14pFkJ0VKVVt9oVcXWc0OYBcnrPtVcRFietE7wTG6fcrM
 Iw+ZQLuIn/UkFUhwN7254W2k+krFKjq9EDGExL0s3P8FwWkGuBKAM3HUpwCgvuW8
 jn5wGoIU1pLDmIYzKCxXDJsD+wfuIQIUMW5GEfFwkEl1i8C64fkCjVXv5y23J5uE
 PfBHEJK8dFv55re6fnZKqAJMnARHAFY0Z2IH/538wZc787P7PULYxsGrB4DQgnlL
 af8AWgpcGFm6mz6QA7mLj9h8zv/PwZmcrfawV8YDJNiow4CsSGB5A1UUZUU6lSsk
 IP0jA/4wjVIOamzJZUJyVPIM1WqMUag2VBieUFmgf6M0sn8wlyR7feAUJbnmkeAH
 j24T6DPd+A3HgKKMZrfRqGc253VsyxbtX/M6F+85mmsecV0vmRl0oVJgIg7Aq+bB
 0TMBtANZR50ouQqWs1uLku0F5VhODoVUDw97LZPv5ei7P/p+a7QeRGFuaWVsIEdl
 cnpvIDxkYW5nZXJAcnVsZXouc2s+iGYEExECACYFAkbXBHMCGwMFCQHhM4AGCwkI
 BwMCBBUCCAMEFgIDAQIeAQIXgAAKCRAa2sIE2pEzUlHJAKC+SEfHXVuLZ+lghF3I
 MU+e1em9cQCdHcVupnW+57s9mcD5NZuzDASBHcG0N0RhbmllbCBHZXJ6byAoVGhl
 IEZyZWVCU0QgUHJvamVjdCkgPGRhbmdlckBGcmVlQlNELm9yZz6IZgQTEQIAJgUC
 RtcIXAIbAwUJAeEzgAYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEBrawgTakTNS
 fwEAn16FpSi/Lctq/aV5Mh1XpFD0ses5AJ4z4w938apaw0vzw9RiqDEBvbHqBLQx
 RGFuaWVsIEdlcnpvIChNaWNyb25ldCwgYS5zLikgPGdlcnpvQG1pY3JvbmV0LnNr
 PohmBBMRAgAmBQJG1wiAAhsDBQkB4TOABgsJCAcDAgQVAggDBBYCAwECHgECF4AA
 CgkQGtrCBNqRM1LpSACgh1YZQWrHaL4asAutBLgbuR5q0CsAmwbzvWAC7MZvRvKF
 oE3NWnDztIwutB1EYW5pZWwgR2Vyem8gPGdlcnpvQHJ1bGV6LnNrPohmBBMRAgAm
 BQJG1wijAhsDBQkB4TOABgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQGtrCBNqR
 M1IX9ACdFDZd8fIFjkuVujkVlgvHn85h+n4AnR7VpjT3dETOfjCqKrqB7O+OmzGt
 uQINBEbXBHgQCACba+8VX1EqhOGaDuZSu+PXgk0W0muTckSA3l+tPvpjeiTqW8mc
 JBwE437fzy/cVYx8m+fEoixFo4D5kcDORm65e5M4B9ECiJjw1hojXoVWF2aliLhV
 cjyL6v5VQ4SKuYny4cceX7igyFWb1Jcx4zBzC2TGLprq6v2JJyyPJsiksjMQZiZv
 otSkbc4jFDkJU1P8mst8hAYe7aZdjO0ccFw3Lii2NlXAjlM6XYGHUCEeW05S+NkP
 S8dmWCFfKdAGhYXC20Y5F/MrYTpP0mKUPAuVlL0Qa+scqBcceHcXgPywID3df2pe
 2WdcEojzW3BEtLGVZw7LEexYBEQz8ngGUT+fAAMFB/923hvNPjOEG9EA/5GaLivR
 vZftvACEUxzZc7nCpEqWXEeH/Hh536Lj2SKi4MxzXHH44KpfzjAoa/NBk3VrSu1w
 zZPBv+/lJvAj2HOych16CNpwfx57BTWYBpilcQ7j8BeWB9F5VsQ4ffGrnW+xZRfq
 JTTG+sNKG7LMGhvuHB2NAdlEyoEX+XrzJw4WzA+eZo7g9kzLOGY/hdK3V846Nl3b
 pA3iSpVOaI7gprhmjK1ESz58/fLFVyFYh0ZXradk80K1cxiUV93Zo79Uvw5K8tde
 gr+9LUWouND7BXxRJ5AiaiwSwa64D6Qq8OREYF4c8qIl9cwWmE6qlR86Yc+C7f3k
 iE8EGBECAA8FAkbXBHgCGwwFCQHhM4AACgkQGtrCBNqRM1L9mQCfb+hnPmlNyP3H
 FyIZslqXMLP79BQAnR09l4FnL36xldwsMrqll6kRxh+K
 =z5Yc
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.106. Simon J. Gerraty <sjg@FreeBSD.org>

 pub   1024D/B6CC76BF 2002-06-12
       Key fingerprint = F3BA D6CB E1F8 02EA 705F  BCAD 6125 F840 B6CC 76BF
 uid                  Simon J. Gerraty <sjg@crufty.net>
 uid                  Simon J. Gerraty <sjg@juniper.net>
 uid                  Simon J. Gerraty <sjg@NetBSD.org>
 uid                  Simon J. Gerraty <sjg@FreeBSD.org>
 sub   1024g/D94B72B9 2002-06-12

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD0HgfwRBAD1ot+1Z3HB+9TlPHseSUNVDa5Br2bHYbCs/A9KT811yU1l3Ac3
 N2PfoTQ8Ab33KIikHVPHVVJCf4AFrzwwEfHnesj8fb4fi2IJA98rMI4eJwAmwygY
 /JtLa+XvRV6csY4LGIeoLk6zFyTSoRJru2x8riKpLpnW99ikDCmZ9Lb99wCgsRYc
 YbxxmF7pnwLIJSr+rRjNGb8EAMAg08/cjOkGvKAH6G3F1SZ1iLM3i8U4XnsYIHBS
 CKtYhAFoxb1qZZrKj2jdrrnHVRcbX/CDrLa7BHTevn6zLR55dL8syqLQLszZhWU4
 1LP/F5Ip4dde1cI3Bk42tQffSsTdcKjY5ZS3+454zv4zwlab3UsxCjhbFTJ87y22
 1xCtA/9WrgV4BB3k3aUufvfPBdD4C5kTL9M+1wH4dk/gTQVN3NUAV2pmjAxamV8X
 dBniQ4FV/Xie+ZQ5icjU7Z7RxrujTdpWDik6PseZ6uMFhUGD6OJ7YjsbrGNrqxNR
 kdqher1uOFpKS8xNF3VOY6pu5ZMSOxHp4aIVDIloo/7imz73frQhU2ltb24gSi4g
 R2VycmF0eSA8c2pnQGNydWZ0eS5uZXQ+iFwEExECABwECwcDAgMVAgMDFgIBAh4B
 AheABQJBVLglAhkBAAoJEGEl+EC2zHa/vLkAn08uo+1C8nmjMBZnUf7MeFpDAXER
 AKCHVoJsQYlfiYI96SQcej7ARU6AW4hGBBMRAgAGBQJBLnfaAAoJEKQYbZp/MyRy
 BPoAn37FZUlR7U3IQ+32g+IzPyfrg8UcAJ0QtNVK49vVOLhj+szbyWcDEVo4e4ic
 BBABAgAGBQI9s034AAoJENH1egG0XgGRVkwD/1pTJ5Ml5O0gmZMxqPZhGKRVeqCe
 XdPJ3iYki6j3XUhm6ZtKoXusJWnxzpKlheAW9O+ndC3H8/7fwwsv4jy97kuMvJfc
 +P3vWXNf350JnOwt72SmGloMGzodXRXr4uw8dLgtA1FElj37mPJOzWNOGfeu4VpF
 i61PmW2hTgE2Wx5iiEYEEhECAAYFAkFUVloACgkQDsmuPPFOO2fY0QCbBXDHMZQK
 lLNt5kbmjOxXt6uQJvoAnRniqwYc39bzrFS8ctILeYqgBL8YiEYEEhECAAYFAkFU
 VmYACgkQ3x41pRYZE/igXACfUTD4mGJ5MmzeRM7o3s7yT2XflCwAn38mei5uuyBz
 9jGaaOzNkDMLABUSiEYEEhECAAYFAkFUVtEACgkQBvNiUvznL2W34QCfZbhz7i5O
 EvvtFlMCjJ8TTSF6f4QAoJu3rlR1zA6dUpHng3sLQjIjFAOziJwEEgECAAYFAkFU
 Vv8ACgkQ1Fm8Ub+2PWH/cgP9HSR5dpy6aDgBJ19ii38gk41NCpt83t3Sa91G/KBc
 GmjrwxjwFbQEy5ovfmsveDYahYMxa2J97OZ2zhNGYOP1Fu124glJb3x23ADsWfZG
 srJwRMhsfKyZr9LaScQOGRD44eHo7tOlIEL8cYPWmijJGwK48ixNRr3ocoIkgS9C
 G7iIRgQSEQIABgUCQVRXKwAKCRAHduAdKGef/O0VAJ9vtJgR1RRVR/6fAdJ+SKrF
 gWk4DQCdHojx0q5/4YpSjZpoqq7g9YXQb7e0IlNpbW9uIEouIEdlcnJhdHkgPHNq
 Z0BqdW5pcGVyLm5ldD6IXAQTEQIAHAUCQS0p/gIbAwQLBwMCAxUCAwMWAgECHgEC
 F4AACgkQYSX4QLbMdr+osgCeIpK1DebkokoLNgzCLjCwhKBUd5MAn2+0m7H4S9ka
 iMdlGW6amQZcOeVoiEYEEhECAAYFAkFUVlcACgkQDsmuPPFOO2eGiACeJlmOfMUg
 5CzUeUaCd/xUMlVUldkAnjBo/YpM+c3Nh86ETrC9+LsHfJjziEYEEhECAAYFAkFU
 VmQACgkQ3x41pRYZE/jCQACcCcwD+Yql8BRsY4GKaWrxA+kLrPsAni/dyq7k36ka
 u4gdyTbedyPvo6cfiEYEEhECAAYFAkFUVssACgkQBvNiUvznL2UlvwCgwzsZtAf3
 o/a3Q9J9VcaFZkjoAugAn0BmYr/OdysRhmkQrAzdk+n42lNYiJwEEgECAAYFAkFU
 VvcACgkQ1Fm8Ub+2PWFQzAP/dypY/ZPmmy8h649R9hyTC3x5qQWpagqPwCsoLJAq
 VHOP34X+ZlXaI1v0m2SqduvDiVk0wXIwRWrLuCnxki0wej5JUqRz/Su0MQQ9x3Ao
 blF9wRFX4NSvq5T8Dyf+g9dJKWHGpy9Ggqd+z3SGavEzgb/SvnbxBl9N3oOO666M
 x0eIRgQSEQIABgUCQVRXKAAKCRAHduAdKGef/GvjAKCNDifMvJ9+JkVZbCxZr6Uh
 DNUHqwCgnKPy9JoVDtg19pDRYxRlWy9f67O0IVNpbW9uIEouIEdlcnJhdHkgPHNq
 Z0BOZXRCU0Qub3JnPohcBBMRAgAcBQJBLSnNAhsDBAsHAwIDFQIDAxYCAQIeAQIX
 gAAKCRBhJfhAtsx2v0A/AJ9bog4D7lZtM6ay0AXi1ox7vmJNPwCfTWghbU2l3kIH
 a6v5sRXnvUucFjS0IlNpbW9uIEouIEdlcnJhdHkgPHNqZ0BGcmVlQlNELm9yZz6I
 YAQTEQIAIAUCUIXB7AIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEGEl+EC2
 zHa/F9oAnj9jk2P0r97KtjAGdtMXDhoYz4VTAKCBBrRtjYhyt7lxW/PKO/7RtChR
 nLkBDQQ9B4H+EAQAnl0L2SS4Q/2CgxD7f9t9m8ODaQw2ODdk0Gi+FFGRWNfWVti3
 RUnea/Vv+SLn34QQuZhfhBVhUmnCNNz4Z3tg9YJhbfsXhduXuENgVyqHKFiO2VPC
 aowekPWknKTWogNZplIwtKh8yP0SXp0LXqhgfNWkE0JxVkX9aRDhjzHQD1cAAwUD
 /j3LKByGwW86ZDPeGwNDs/j1BxTggiXQdgsZNd26H47ZDgEvaKsuaPiIayyk/Zpw
 4L0z7HQsrXIfu/k8UJTeQUNaT//pVQMsYrZVB3B5Zq3H/fAWiFB1ZiLlpnu8xY0i
 RVyTc49glth8sB7uwGkkLzu3hPxx6rE9QJZ+OwrhpWYiiEYEGBECAAYFAj0Hgf4A
 CgkQYSX4QLbMdr+pYgCdHb/l5Z5GYen/nafceceLNUiRVXsAmwZX5knj6YwlLZZg
 U4BS88b/Bo4u
 =onBO
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.107. Justin T. Gibbs <gibbs@FreeBSD.org>

 pub   2048R/45A4FC2F 2012-02-10
       Key fingerprint = B98A C3AB 412B 094B D6FE  E713 FA5A 1E30 45A4 FC2F
 uid                  Justin T. Gibbs <gibbs@FreeBSD.org>
 uid                  Justin T. Gibbs <gibbs@FreeBSDFoundation.org>
 uid                  Justin T. Gibbs <gibbs@scsiguy.com>
 sub   2048R/AF6927F8 2012-02-10

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE81gtkBCADBTdiqSfNlj7xp76ZXuzlpSJfsKmdlVRUQAuIbSGRg1iyMYURU
 TB03QsHsQYXyBtF0IV1tgrjOssFcIzbnjfoN93JQgR1ECJjhSwa2LfeEc2YKtgrX
 tZUUoKKBFqPcEgzoX/K7Lqg5Gl9cxwqaYg0fIyIq1t2qh3CrSeP4QFqIoJF/VuA0
 2B7pGh6GDRtBiQ5QxKqQ7ZsZF8nZd6RQlR+9jn3bAV/NP3RzswfjyodSQnLQB350
 KrP23AOgFKk8kkVJWG5fR0GGfjj/AhVIaewQIvCoitXEaxXZMZHgJISRe4HkZQFY
 1ZGRvb5ATX0P/STPT257LK0Q/+dFROpCQxYlABEBAAG0LUp1c3RpbiBULiBHaWJi
 cyA8Z2liYnNARnJlZUJTREZvdW5kYXRpb24ub3JnPokBOAQTAQIAIgUCTzWDogIb
 LwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQ+loeMEWk/C+OnAf9Ei7DeVjV
 Urcap8ryNrG/wNWRyJ5SJdlF35C26vsQ56wcQMktDgJ7/3o/Of7vSpLv1+OHz72+
 xmDRUreWIec2xK/1vPCqfwbArVpsVqR9lWCS1Q0/wL/3SvQlpJ7jiFPE2v3D4FzV
 xxuR70C4iA09fWoje0Nr9VjG9vgvoM/0iY8Tnpd9eE1/pCEKir9hNMRbtQqvL5ig
 QIZeVBTBjPvf1QKQzAIIv1tE+aQXxXvXl5i6WcEGR7FBpit+/34jLtXHtv2EThiF
 +k9SljudfIZJm7ZoECFzBhm3lbz9s6mny3xRu0FlovYmVO13pQAfVDoVTSBKRfGS
 F2Ed6K9yVOxgKrQjSnVzdGluIFQuIEdpYmJzIDxnaWJic0BzY3NpZ3V5LmNvbT6J
 ATgEEwECACIFAk81gtkCGy8GCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEPpa
 HjBFpPwvF1gH/37hwu8Ac+pJMWb0u0WeDtZIUAhswqHcJ2XHWWTTT6WXqEyen4NJ
 VI6+FRK7NZJ7Ndk0CPuiA74ijWVCJOLDv4aWjpLjHA/x6kQpd0l1TIDQ7KhpTGGh
 +YCUS113b4wBRD3vCn6XgTOeJ7+T8CEiNu6fvll7oPCbirjfz/q4hUPPjH5xy/ja
 4UywsNSMOTU1jXUgK0+Rx+q/R83tV1UTNTvOCfcqjZjYGhJojpA5/Zhzs6qklX0o
 wckrl7nUZqYPT3cASBgdlLUnaM57hqRnNHHouxiLf9eNddMjjnFck/zgppflhpWO
 Csk4JE7OLV33gfAOyrV6plIE9D+i1WDKsPS0I0p1c3RpbiBULiBHaWJicyA8Z2li
 YnNARnJlZUJTRC5vcmc+iQE4BBMBAgAiBQJPNYPKAhsvBgsJCAcDAgYVCAIJCgsE
 FgIDAQIeAQIXgAAKCRD6Wh4wRaT8L4SdCACNxgQwEp5EwBnzxN8y2jMcFIGBqeI9
 YiGEa+fF9yvQ7uQ+KGAIpV3yqqV6pYrbSj6OvWg9Gw9GVvQyR00XftNxQ2OGfXfL
 a2ejx7h2JvEgJrPryLRd6pwiMm9CXMJnf3vBYRU+Szg4Cf2sMmLtDJpeLXCq9RHT
 bDfOhA4Z2NL6osdr39EZOCrJ3lEqtFSNYLqV69vC4VRxr3W2CEYjt3JeJeSeGNBj
 RQ8vHF7m/SL6PCK0lRv7iB3UmJyYA8hoo13jUqPWn8mDdNjgSVnfOwOUCqe2l73s
 Y+P99m+nyC8iNilNL88NvdbXujNTGY+meo+DPLCeYFiW2pUtQMIQr9SLuQENBE81
 gtkBCADFt/8yGtnWeqruGZHf5tJDCNLJ8YJ49k2qB2L/ytycqb0JOeG1gSj42D13
 9+kgqf9vunZg1n9alP7R14qsponE9n6RAdTFXYEGyHLCwt+TgNiI9V49AyGaXxnC
 BlO48nZO47zCN6CHqx/MEfCTabwOCFPXs2uMXQwYki0R3DJ/So+OSOE7CPsZGbcH
 U+ruDmei+tP49AC4cUm8XB0LrsoSRh34XpZ2pup6Xw1Fd/dyQ2FtM68vh7cGV+Hq
 HdjvoeM9eF4+wpN6Yij0tYekYDqexlQDRh+1v4Eeq3rznZhXZFW4KxGB1uXATHMA
 8J7/XORlhRXYpH9aLiE/tlsBCUHPABEBAAGJAj4EGAECAAkFAk81gtkCGy4BKQkQ
 +loeMEWk/C/AXSAEGQECAAYFAk81gtkACgkQP2fwK69pJ/jmZQf/Rc/AH+736Fh7
 aLhbhF+Ag71Hkph9ByBIoSdbUUgFf67foTjze0r9f4/qH6jLxg9c377ttSwmivUY
 UXT6Xt/NQ7hkd+BpxbBocgBaRS9fq+QfZ22GCuJDsFVvMA6eioYUMg9rHkhO3Ep6
 ysNhPphbCsNjRAMZTJA8UBI+FS3+MkpBzkQSMyrH0DlyoYsk3Am99uLn/wZlWCME
 Gg9tSpseJ6N1YKKor0wZBkBLvpHWJefu/E9h7JJ6Qci78pdjeMvoD2tx5t56eweR
 QUx8O5smlcU6PNUW0LFQdrSF32cTy7gqqMzOHK6xqaqliCyrc6L0HlrvB64fNCSn
 4Q1RVEfTPRepCACMNNNNq6dJlw+cPHQBSVyYIZzRkuZkdKUJLnaUduzePV4NrzPg
 AG1gkDqk8zlat/kdOoHCiI7D8agWluCEa/dy7So2WD0F+Hs8p/3yYXLjGfRBSDyJ
 R+fHozVRiZukEOQtElV5M2BwJ6ql5mmL3cFszDfvXAvM8JaJDa0D/8qndLaxBtC3
 U0K/APQxUPvpcOWAJO2lt8GaVr1nRsRTW91z8wSq+iwBCqIqPY4SAbLDaSPoe3Lk
 QMf92sOvKDojCx1WcjHBedyREyeZKNdWyauvYQAJm3oYpgkU0Qdnq+yb/F8homjq
 p74XqpZ/mgqZi+JmS/oDsRIZVbUjIyFB66IX
 =nVkv
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.108. Pedro Giffuni <pfg@FreeBSD.org>

 pub   2048D/422BDFE4 2011-12-06
       Key fingerprint = A12B 7C6B 54C0 921B C64F  7B35 58DF 6813 422B DFE4
 uid                  Pedro Giffuni (FreeBSD key signature) <pfg@FreeBSD.org>
 sub   2048g/43A91DE0 2011-12-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQMuBE7db1cRCACtLqHlWpOFR3RqqXWBlItnk4Gm6NqT94ZbMoY+GSkLVbOxa2tL
 +ScfosjZ11Fl5UGaM2fQSVG4LgggZEDlMZrCTCRRepNX0sWcbb3QGGShERESzkjj
 wOm2PW5ta9hPCdACvNjRPzvueZjWJdmlhQNO0BzaHznwqhoqk6LqmEEtFNu7WFCy
 PzECfCkgRqJU3Z/EJaLd9kMZ6d2CqCz3sYF+P3/NyXrugK20PKQr/Lb1uL2R9FOl
 S6019GD/xfwMkNVn0CzvMXFTp4V/ecGB26Y0gt9JJBS+32JaY+aG7ULDGVs3zv1R
 1Fi1ohEyqVsuxjM8+NTaIQ/28rNSzI7EoBczAQDIh2oMj891s/47H8i69e8XR4xj
 fxJ3VZDgAYCss8qGBQgAguxmf5x4EVfCDjucL1cHgFMv3x4Jdv0RwrqOdOztGvEJ
 XyKJi8H5uIuLO543Q0Rj0GKqzYA4f43J13BCdXHoh6b/Tp1i8Q5nrk7gFQRy1fF0
 O3kbpl9nt1XH1+GVQdBEs3lHAFYNcJIsYW8KAm1FpfjGRdelVYprmM6ErEIwnDR/
 twDp6JNxBl0lyDjCYVbax4n0Bheit42CDSGn8MDraZBenRp2M6TxC64jQEYV8tW2
 J+W2gAyZJeDXUq5Yp5X59ZzvF7aXr1DZ1b3J3l9ySPkxMWoxdbp5Sxkko04SdE0F
 Db+DmyIbUlN6Q1hKBnDDJ0yIJXFJ+w7Lqa/lEKh/eQf9F+4Ugh0MQOqLv2nDPF91
 4y9vDFB5Po1Vt9PwZSEC10oTYEZ1udjwhlu7cz3KvdZHoo9c8xXma/IDx+cTzWbF
 hMUlTH6txcx+4KEPqf2MCPJHhGNPNrnN4pRgGbDy/iGrJzOXSgh+sIltgM142W/J
 n7saCWgidxfsR6EIrVD3pFIYgKS7FT0dadSrHsqRuION8pbqJwwXMwu7o192tdHM
 ZGk3JyjUWFOnuug5O1MHd6hTQUkf/ZZukW/h+ROgMmghVobIGZ0ne1tlUD0hLLRq
 FnJb3EIlS0fNb740X40OA57V90hQtJvcrjL26lRMbS2MeRDnCwZcI/3YJ/p47xFv
 RLQ3UGVkcm8gR2lmZnVuaSAoRnJlZUJTRCBrZXkgc2lnbmF0dXJlKSA8cGZnQEZy
 ZWVCU0Qub3JnPoh6BBMRCAAiBQJO3W9XAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIe
 AQIXgAAKCRBY32gTQivf5NcqAQCdccZvB3SGbyf6fljXVIwOQx8/3SLs9gHT3KQd
 YCu8ggEAootBvhSjxTJUyhwveMJSQKstb6VfUynyaDDAz8EF5Nu5Ag0ETt1vVxAI
 ALpKZlQRfMMr7zbN64GtgGL0ouSDoGeuQbRLcrePZ0RaNmBkvz7TbGk5AdLjE6vY
 ybMKjKCXNvjvvdOCghyl9M9xIG/rjttgiOEGMzfLXqgjZZXVUvXAk/2x5c6jg6IF
 vHmGrXfk1Oqw3u1IV9KbveGQ1HVJxYsi8jt/7uRnneYmTvzE16Puj23xM9fvDoMS
 MHAMudWiKt7qjwBy3Eq4KZbO8DwzIUno+ECKb+De9P2Dy6ikFGCcweGADLTVLE47
 ySVKtBdiLzieefJbd8Qhe28kF/glJuFVKnTYceYpVGgs+Ul7WxQIgRCdFfo2P/Jn
 BtN9NFBPAw0WNPNDjg/cPrsAAwUH/R+lrO8j/OupArfnuvZc90cbCXYEeqMu6jME
 X2AcUSGo934F9qPPQxWnX4qJD1cztGGrTFOKWxt+aGN2+qe6Q/fIvaNYTb+Duh1l
 oTNtGmVYPX/HGF/XTm0Vd3BgcpXXEv0XNs2gQwNgCyQCwEMmYUt/DUuW6qzkZs9l
 ZA2Sjm0eBTPat2DBORp0KUvqe//STk93ZNcLDnj1EnVqa0piJk9zcDivEy6zx4gP
 tGFPdY0qWCDZjiFk+wB6/XzEDu+jFMERxPCB2FFateKjxswRlBGL34xThCv1SBEZ
 XoD+w6FJ9bx/jPy/muMe7ku+SDm8smRBipOm5V90y04a8AHxF3uIYQQYEQgACQUC
 Tt1vVwIbDAAKCRBY32gTQivf5Lq0AQC7xOYsjWskIoge0aL6RwWAXhYwFOejC4Js
 h5BxxBSeRgD6AqolGR9yRNeSdg0ee9GfNWC1UZKNOIiQ3NDvwOjvb9c=
 =fr2c
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.109. Palle Girgensohn <girgen@FreeBSD.org>

 pub   2048R/4A6BAAAD 2012-02-23 [expires: 2016-02-23]
       Key fingerprint = BD8C 332C E630 31D6 2FDB  80BD 5FF2 A161 4A6B AAAD
 uid                  Palle Girgensohn <girgen@pingpong.net>
 uid                  [jpeg image of size 8260]
 uid                  Palle Girgensohn <girgen@FreeBSD.org>
 sub   2048R/6BC41243 2012-02-23 [expires: 2016-02-23]

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Comment: GPGTools - http://gpgtools.org

[encoded data, 14322 characters]
 Yr1aTjn6KMAcsSmMcYdcrJKClIdqQnzQEKRbANJygs+a1XSAB21NKdQ=
 =RtWL
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.110. Philip M. Gollucci <pgollucci@FreeBSD.org>

 pub   1024D/DB9B8C1C 2008-04-15
       Key fingerprint = B90B FBC3 A3A1 C71A 8E70  3F8C 75B8 8FFB DB9B 8C1C
 uid                  Philip M. Gollucci (FreeBSD Foundation) <pgollucci@freebsd.org>
 uid                  Philip M. Gollucci (Riderway Inc.) <pgollucci@riderway.com>
 uid                  Philip M. Gollucci <pgollucci@p6m7g8.com>
 uid                  Philip M. Gollucci (ASF) <pgollucci@apache.org>
 sub   2048g/73943732 2008-04-15

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEgER9QRBADEnqKDo2SQwM99dEQW6sEoFafQm592R98bDFZC1CqmBhZaj9nG
 ksxyX82s/PaOoosKZR3hsMcDOJgYkHfTKIMU6aDVMrONfsgLF4V6meTaBHW5uSOI
 cJBsW/TSTsOq21yrp6995jSTsHZxV0CpFDZWGCowefxvbRoAz/89pUBxYwCglOYk
 btty+eanC+la8LUuLn1na1kEAI9wXI6wRbc4Qv4dppmNwiBsu0aDW2bOe6TNU5nj
 MMU5dMQkQ+FkHBFNyF3Fy5Uvm5zhGhlPKRTW9nOmLzZQBf9kj1G2giq5MN3fs4jg
 k15/93Jm3TnyV8LZxP4cBU42HhuL3b6rzFFNVgDLw4PJuSqjt/JTNhNtCwYW+nqS
 g08zBAC0FuxTJzna5X8Y2o5o+J2yU0kIB+y+fmGeaN5zg4VsM64Nexhc2X3HJbXd
 31hPqySdBl6DQP/I9U00S/C2Qb6MVwTDYR2DBltoeqoHOJKGLvqB5N01DAVg8kAK
 31PpMdFhkfZwM2ZsHfoGbnEB2fMd4Fb/+DwbjrckwdG1w8P2t7Q7UGhpbGlwIE0u
 IEdvbGx1Y2NpIChSaWRlcndheSBJbmMuKSA8cGdvbGx1Y2NpQHJpZGVyd2F5LmNv
 bT6IYAQTEQIAIAUCSARRtAIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEHW4
 j/vbm4wcSz8Anj92jZBlcifpDwdiUvTZdGO28CjQAKCT4jeiJcLCbhnXaXonBCzw
 DRw5s7QpUGhpbGlwIE0uIEdvbGx1Y2NpIDxwZ29sbHVjY2lAcDZtN2c4LmNvbT6I
 YAQTEQIAIAUCSARH1AIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEHW4j/vb
 m4wcM20An10tzTX41D6qcEjOBqMzwyydrYoyAJ0Qs9fj/ct7iDCphvNwCcjNGMlx
 ZrQvUGhpbGlwIE0uIEdvbGx1Y2NpIChBU0YpIDxwZ29sbHVjY2lAYXBhY2hlLm9y
 Zz6IYAQTEQIAIAUCSARRmwIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEHW4
 j/vbm4wchSkAn2DyHStIDMIXwKH8LAgut1wpf4sgAJwNKynACF0+sok5YupxxZkm
 QFJsNbQ/UGhpbGlwIE0uIEdvbGx1Y2NpIChGcmVlQlNEIEZvdW5kYXRpb24pIDxw
 Z29sbHVjY2lAZnJlZWJzZC5vcmc+iGAEExECACAFAkiGRaMCGwMGCwkIBwMCBBUC
 CAMEFgIDAQIeAQIXgAAKCRB1uI/725uMHK3IAJ9n6VjOWpymuzHE7xN/xlJu2j5l
 uACeIqegqdXAaqRS4+olfTDN/nvoYWe5Ag0ESARH1BAIAJGalt0PcCClgFjAWdKr
 2+wNm8CrgW8cm62p1KZ9rxTHqpDEQopa8Y2G86pKDmhjJQmPmepcZx2ZhnBc0UVj
 qBA9bEDnVJU/ysuxjYrjswYNP+5ZemUsk5IZgnZOLQod6ewWtcdZ7EPJYOfKNAvo
 1TMNFZqA6CLKUgjPpokRdolseRkyuS5q5XM4InraptSvv6G6SXRiDBwChbwfbJG/
 82ClmnuInhDzmc4gg5flrU6RprLu/PPx8SSIRkVHNZdPL3cF5pocETruqdkcb8yD
 aC4kIIqsn1XeBYLXS5lYbZBexR0i4i0xkjXnErrGu2lgGm65RwF+hvRsDC7RIC0c
 9hMAAwUH/0UY8w+pGeGMgZJHiLSoaK6pTXv1/ega4na1vGglnBeGXB2Cj6jKgv3j
 6a9XLRtaw5owhTLAX0uWt1XOw8ojm+vgVBvXJO7ljUI99/Zov5IQRZfy4TN8dOY4
 1TNgGiwaUU/rh+MIQy5hFCQPGRjIUKIkOGEBKOaZEkTV6Hr9rFCokpcTILF73JB+
 hI2EHwnXzpFKmzB1zwbNvtv4QiyozROvc558n13WP8OdmdGNv0jNcytqEIaB+PZM
 wMcLMjikPHKUxfHcdmwCezpIBKG2T/5xgzTCMxQ0UbfIYLnsOfJrCm+akw2VbQ+R
 TdP5dVLKITdFUk3nydirHpN5JYkH31WISQQYEQIACQUCSARH1AIbDAAKCRB1uI/7
 25uMHPq4AKCSdNolzpw8MfWfj4LU2ZVlbflHHQCfWUK39VTu4mNu5nPmuM6gmewD
 rNE=
 =SgIy
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.111. Daichi GOTO <daichi@FreeBSD.org>

 pub  1024D/09EBADD6 2002-09-25 Daichi GOTO <daichi@freebsd.org>
      Key fingerprint = 620A 9A34 57FB 5E93 0828  28C7 C360 C6ED 09EB ADD6
 sub  1024g/F0B1F1CA 2002-09-25

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.0 (FreeBSD)

 mQGiBD2RGpURBACZe4DKSXi6jCkn4eZHJr7nGPISQr4YUq3rDqcOSUlFPBZlVd8S
 pYnfkNNW8HTxl0+qd5kIXiQxuvWxCrTNzoS0gPO3IQcICkAqbIICK0A1KFFx4Zen
 +muTp/e7bDhStcMEelXc+/3mLReBJf/d6e4For6P/rqVmMAcm5A2GO4quwCgmrSD
 fLt9NGJ+mtiXFxloHe57l/sD/3nanV7H4zk9gPJZA9b8UKpbZZmsyljTuYOAULL1
 oh3CZDYvKZZ3E1v9exVDadSGvbps1bL1okku27nNd9BnlnSxZ+sQbfJtvEoBMUwH
 HJnAhTU5sW0UJv6K7goZ283npX8fFjyDWJ4+XJ1Qq1e+VMF5QeZVRFiIJ6NztM7F
 6b1NA/0dwFApYGf2r8YV5uJPeSsWH94Mx4PTtIXp+WOovQ434wzuBUMiHxeeuv4z
 LP9Vjf40s0GoC0TLz8wB2awUrO8aWwgg9SUf5yO+jKZ9BchBgnqjju81zAG5sbUc
 ogMUrENjqIJgFCkHcnbxo2IHOygwjezvZeM/svcxJ1bW/gZlwLQgRGFpY2hpIEdP
 VE8gPGRhaWNoaUBmcmVlYnNkLm9yZz6IWQQTEQIAGQUCPZEalQQLBwMCAxUCAwMW
 AgECHgECF4AACgkQw2DG7QnrrdZetACfY5hq9W8pDo/vGEaCZWQtpTpW+EUAn0jx
 G2nWbw6EDoGxa62mmqy9rFyMuQENBD2RGpYQBADjmTUn3Gk/tkVzIgVm8wdfuMPb
 n08JkuNLUDYjxWRfRmVZHpT3L+e7rUwKFrcmMRM+kMSsnWKhmhwpkI4Tqgi5/lmg
 kN8R+kr6gm40lEAc8tNPNzbE4ueKSAwW8QKqC2iHAqe0l4SjvDEns5M3mARPEtfn
 tdEsQGeyGYlxsG+MhwADBQQA0HSyz2a2mMvyn7IfG7f7t3zuL5tXoFARYQ2FYMWn
 VSkydfzYuBc6kX3oskR1QMv4EDgX0hIUglvTIb918Qj+4tx5CKsUKnZFflGYfY2C
 qwVwR9SPPdX7rhytqkalH8HyuLm2XuRaf/pzo23tAivSXNFhfQhvybFtLdPBJ6yK
 3XaIRgQYEQIABgUCPZEalgAKCRDDYMbtCeut1qqBAKCDnLRYCpUm4eyVG+Ycsn6B
 giZvyQCeKeQZPCnz6RKllxb8E/E17bdhN24=
 =T2MZ
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.112. Marcus Alves Grando <mnag@FreeBSD.org>

 pub   1024D/CDCC273F 2005-09-15 [expires: 2010-09-14]
       Key fingerprint = 57F9 DEC1 5BBF 06DE 44A5  9A4A 8BEE 5F3A CDCC 273F
 uid                  Marcus Alves Grando <marcus@sbh.eng.br>
 uid                  Marcus Alves Grando <marcus@corp.grupos.com.br>
 uid                  Marcus Alves Grando <mnag@FreeBSD.org>
 sub   2048g/698AC00C 2005-09-15 [expires: 2010-09-14]

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.4.2 (FreeBSD)

 mQGiBEMpwEsRBADcnD1kRdYoPvpKLjT1w1T5p1fT/LAimANGHXVoZxusjNdJjleF
 7SNfN6V+sjm8bdUjZb3VJr3oA21sdwIKXzamhtbaDRAAvKdYIRecTaLId8SqI3dO
 mZtLVo0A7XNkjVMtyLn8lPKpdiHPOc05/x8sVLNZ2LR/xFJnbdT5bomy2wCgmIOF
 EaoJmSuh5trZRiKIAeIodfMD/3zaTMjI7eLziJG2IWdxceN40vUX555gCpeFEQtD
 DfVV++32c7BN0j9o8VFl3W1vsQ3Elhm9GRlb5hZbRo53Z1YTJEzogXTGBVipJGID
 cDo/bCmRuMSarsT+M6R1NF6uToSBeVZyCtA/DDbJHNvYD5VeOJKsdaQ7hYtctoJ6
 ms7hBADD8AeV5gLZOjOIFTAkX1ibEksxz/P8aUFjnj0QmPe98/RI02e/iYVVdPgz
 HgrTA+gF0X7nIicn+KhBgOT0MTx6bf9DFzmk1KaFBA6vnQ9alw1WtRHGsIm0OgD/
 Jn5tRQFriUS5PWQP8FKXcUfmqOd0WtLebPicX66nOba+NKdU+LQvTWFyY3VzIEFs
 dmVzIEdyYW5kbyA8bWFyY3VzQGNvcnAuZ3J1cG9zLmNvbS5icj6IZgQTEQIAJgUC
 QynBHgIbAwUJCWYBgAYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEIvuXzrNzCc/
 UUwAmwVe85K4Ljml9AgBKbNn5juVRkr7AJ96PWlTFr/IdKq+1m3Zw7Hyt93cf7Qm
 TWFyY3VzIEFsdmVzIEdyYW5kbyA8bW5hZ0BGcmVlQlNELm9yZz6IZgQTEQIAJgUC
 QynASwIbAwUJCWYBgAYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEIvuXzrNzCc/
 6koAnjbYaFve7vZz3DW2qTBnYXp/n5IAAJ9+2EStzCP3tnKb/hjOxotstQufCrQn
 TWFyY3VzIEFsdmVzIEdyYW5kbyA8bWFyY3VzQHNiaC5lbmcuYnI+iGYEExECACYF
 AkMpzVMCGwMFCQlmAYAGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRCL7l86zcwn
 P+oFAJ4tcY+w4DVH+x7euh4K6ECBqM73PACbB2QBuJrDOtTxoYdmiH3XdHCytT+5
 Ag0EQynAUhAIAKD52CU2Xp69qfo/j/1aLgiMhgLpx56ySAb9SzZySUHadyptFpJR
 i3glUnoUh9dfU1jr8Y0f1oChCmm9TOZnQJWR7LOrO+av3gxnRtVMkvVr8eAPG3o6
 C3VZop7FPxR05Jmy0EtIxweEgNGmCX/p58T9LAM50E9FacmwYAIn77O5zXcJVnBI
 m9Ih05Hy4nGIoyF4iBA/NZQL10glMnwc6p82AiMj1FI6i6iDdPYBeiHKUXkyZ+Q7
 Df+HkelT3zot4DPKBeGBSFyQENOjHCp4wl27DsfiJXViy2NRz5lzrSFgvc0ZIUus
 Ia5d9nG+OE67JKU4qT5xgJL5+eOe1lXsHgcAAwUIAJKuSmq6lvF4NWN8HWDimXBE
 Ol8jNHf+miaLgMxOhAOeD4TQHpqgEhnf02koUbGDbli/AS1oC6WGhKSekgYKZCkf
 zmvRNEkCJCOMG3bOcKEokHiujcyQHWf8k4WmBQe0hGalrE+oaLti5H2/jAqUqYFi
 tHWRUeJDgfwOXRalI3YJJyjfBzE6ckE1kFWoEeXDuZdER9kusWWVrX38mdniwoKj
 7e+GtfYo+riB4Nb/TSuQjw45DKVaqYNi13P2P1EmHwmrSjnL3Yrck3x/vDrCKa0c
 2+BAMAaLVnOGdaYT1xsaMBGcgSkybQoOmvMm5hdtxURqi7k/TbaNhV/etSzfB/CI
 TwQYEQIADwUCQynAUgIbDAUJCWYBgAAKCRCL7l86zcwnPw4iAJ9rVaOA1zKrzwRX
 CLE2Xxf/FkN6JQCfZU7PjkJvE9jqgsBVfMhi6S6kNZ8=
 =rDV2
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.113. Peter Grehan <grehan@FreeBSD.org>

 pub  1024D/EA45EA7D 2004-07-13 Peter Grehan <grehan@freebsd.org>
      Key fingerprint = 84AD 73DC 370E 15CA 7556  43C8 F5C8 4450 EA45 EA7D
 sub  2048g/0E122D70 2004-07-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEDzjb8RBADNg1Ak3kReZLn5N6aGm/0ofeBsZDK31HgXFoQnXpZWuPf4Dcuz
 EztxDMfAhCdQPuFm+u2av7YiOc4Xmxmety18CwBP4E0w2Wf2RKdI7CdeVshn5epo
 kTMTn8pDu3ZDzui6Uvnjuc6y51VzL4zJwNNZAF5Vs1gXr+V7aDbvb1/6PwCgtX5K
 XQHfTdms5d6yhYwyQ4SrJ6sD/izS3iZBHe/nDdTBnSIA4sIdcZUn+sRfX7/GPs3H
 9JgYbI/+fatLEUShiKaNTCCibNRXx1OqFk0w+vs1pRz/ziE+G7uV7tglS3h8LMnO
 Q/6y8WwTMiv2seCKyiuvGxG2NMT7OAdrSNe8xPIlNRBdxvANFlgnfPsypXRfjJ5g
 1mqxBACaho98/zNgFpClOwAxw1Il0TX1c2EGB0e10FJ77rDNiPCWSnsPu5LB8mhL
 FfeGdx+zVVj5G4tMVIdJgZ5T4IpELPY1rpqf75F4mBrWTnmd7g9X1S//U8j7pNet
 JDVlymYg9DJvtKnfOHXqViwV8g2X0EwKsOpjo3IBZ0Oepw3wfbQhUGV0ZXIgR3Jl
 aGFuIDxncmVoYW5AZnJlZWJzZC5vcmc+iFsEExECABsFAkDzjb8GCwkIBwMCAxUC
 AwMWAgECHgECF4AACgkQ9chEUOpF6n19yACeNpRdDKA7qDA1vKGyjJIEdeAhqT4A
 nRC1CUpFTve3psN3cPWymDzSiHl5uQINBEDzjcsQCACkCgzuJRaPnoWmOZCk58ya
 +2Tbxd3qHtDDwMnY8NKi15FA0Cs40PUffHtWrxW1qcmm7QRmhHpR49tR1f7xT7CR
 OX5QKPa2axjv1mk9MKC4BtMe851UIMZ8vWbm/Obo9UdNYqEQEXT5TY6PbkiC8tDH
 5i00MBg6mkYtK9xU1OjJUp1YHuqalWgMEW1nUFM1CV1Fbk/SqLzyNcC0biTRMUkZ
 aZ1MgF6oxBIj/InO0f7gVoL3Jb5BC9bOUo3NkHCUQDBPwfLXR3lfrQLo7fLckYaN
 j85Ap6NXJr88vINfU+xn/MeVwTGYw9ejh4sujp3d57wP9Ym3PaR2SkoPdZO323oH
 AAQLB/wMC99y55a2jnP9IOsI+UIgWFWDmVqDhdgdp7asKjW2aUhX1k4CGPw7AdTL
 dtBdxqxFNp72fZPZ53ZIn0z2bogyYOOT4aWbTFiqKyU6CScCpeunKs+/qz0pw0f5
 /TdHgDCBrlMLihNiC0Tvtf/BzTLR3pqDshts8x82qKSjhxExazbBxJ23A4El53I8
 zZLQLD+vqJaFylhze8DNC3J/V4NgD1Vdporrz9L+QZuJXDGUyp6Gj4uteAu0W/My
 4+5zrs9Ym/TSmC4y3PLoqAeJv5I3E+6YqMo4c7XcLuJWO8jzg6aRlQmc/WgvVANW
 juieqW0bcYqNu2F/GeUcgvD3dWt7iEYEGBECAAYFAkDzjcsACgkQ9chEUOpF6n2l
 QACglTS9Ryv4oLwvXTNK2j2RLiH1VZEAn1YaLCp5rtafXPpdMdCOuJXo7MjC
 =UNPF
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.114. Jamie Gritton <jamie@FreeBSD.org>

 pub   1024D/8832CB7F 2009-01-29
       Key fingerprint = 34F8 1E62 C7A5 7CB9 A91F  7864 8C5A F85E 8832 CB7F
 uid                  James Gritton <jamie@FreeBSD.org>
 sub   2048g/94E3594D 2009-01-29

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEmCOzURBACOSQ8S2bwRYqXrfV9/pT8BmnGl7GYrkbDtJqL0IaTV1Bmdw7ed
 qcDjMT55c2LEQlO7w2EG5z7JfaBnP+jV3X/gtH37gcqClcJRxJ2uhT7fShzmRR/U
 5iTbAt0BwDF/W5LFmxajhZvw8NJKeMk8j0kUwdTzSKalN+iAhXEhqx/uWwCgz2qg
 9utCYdwfeSmRwebBIQhPq4MD/2bWpo3/Vw3PZzNsja1l/s8jQjxkMoXJ8LlYFoYW
 vc5lMBeR0nb1lZrnBvQGkEJVSPLXLvTBYireyqai8pt+Uk7D1oRevpsD/rIsSZBV
 MVSa8jUqPF0HC0vWrDd98HDq/RJ3SD4HHhiWJ2wA8YrftyeHzZ0kiJYzggQ3UPM6
 +x52A/0U2kBqBq+HqA7YWTEo4pn2W3adZCT8mwmsDdEnC/uTvA0BHBN1HfgCxwee
 TSqOwssFioHCVu+N/lxKjqy9ftHI4ljSuYOPpC3q+LwFdVjbCQ6ynILNKp89QiK6
 B5TphmOTQJ4ytVxr/tcvzDOCxbtyG6t7eCJBlfEgGjZLQu7uYrQhSmFtZXMgR3Jp
 dHRvbiA8amFtaWVARnJlZUJTRC5vcmc+iGAEExECACAFAkmCOzUCGwMGCwkIBwMC
 BBUCCAMEFgIDAQIeAQIXgAAKCRCMWvheiDLLfwhyAKCP4JGKCayDfY1f7sBXhYSa
 6Zr5KwCfSy1evNxNmp5TwB7RBpEZpL2R2C+5Ag0ESYI7NRAIANiluE6e3GNLyLTc
 cc/SQ5NdW4/B89yDQkZi/f7mUAMiS73iKoe555EVI/JIFsHUduHeYMB/ERDHNSUj
 RmWVkb4r8eVSlMVvoU8sBYGqihoYtFXYT7rj8vvq6ufkF9RtBJLTLzikEg07jfQk
 EzKr1eFOl0v76UGnmqrYiTXOAJoXQIH4+Kt3pWd8jz0Lsc3Kd4+eMW2A+eXSpShb
 yuQhvtIkSdOLDa9PV03Y/GweSCbTKa5+oTmCoKvXJYjDHwkuj7n2dog8vo64Oy1h
 z8mPPFyDXr1OitDdA78Vvpu8afz3Uev9DMaKd6WIEtVUprLOXyuSixn0x0rvImes
 t6lHX3MAAwUIANKigPUT7boxzc93BdWUOKrZEnjN7zVnIqUMizVgi0K9nLM+lSpm
 exPfoEZqCIBmAmDRYO50Y5Lwb2R6V0qHFBmIvZZ9Ih4YosXuu6oFhKHjamRK6JXI
 hh5mMrOZnfDRn5YGEr3ZCEOGzdW0pY1t8THd6mtXmK7iIKKy+3u/WHf0tCJDRXk6
 7ETBWwqFTE3XpZz09aHRV2470GKESSbs1Q4Cobc8ZIifNzr8kfnWPm/EH2UCNpnZ
 K2UvAxi6SRYVWIY11SRS/am+DRGweKfm9+NZpHEk2yJknHd95Q3IVw+fX+2yKVQe
 L+X9H5BR1y6XxKbxqrlWF5I2FDJo4BzOA1eISQQYEQIACQUCSYI7NQIbDAAKCRCM
 WvheiDLLf1rdAJ976PPYVcvK8Q/zKQrMv7pff09z2QCgut3uY8LEhlK39qZCF9Cl
 2+bu5gU=
 =Uux7
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.115. Barbara Guida <bar@FreeBSD.org>

 pub   2048R/3DF5F750 2012-11-13
       Key fingerprint = D367 F6C8 2A5F 2921 70D2  B446 27DD 6FD6 3DF5 F750
 uid                  Barbara Guida <bar@FreeBSD.org>
 uid                  Barbara Guida <barbara.freebsd@gmail.com>
 sub   2048R/1DF7506C 2012-11-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFChmNUBCAD6H/nOlsSUv1C4GJUHns+0YmdcqwpoF06+mcfJXQ9ZIYz0mNqd
 7b03NpOzSscwiBHazZfACldGB3+6A8cNMvCH5BbENjeX6m89i8tEzYA2eDf74fw/
 0ldHyHZdnZuXJSQgooztjRmzo/5I2g2ScdhhYAOW5aqEqlFrQexD+0ijhwUU7ylR
 BtMlSwGozHpoynwtSNsOZVyXtEQ4CidgDY6sKx3jhGePh1Pqh4KI4mDCNh7hT48I
 v5elyTTHKj8Fw435SNfFqCzVE6M+POuN5Zydetk2ru57RD+0fnCsNc9sngLRVBM0
 xxOokNE7FpzsIBQ6tzLz+lZCz9L9uzuHjHdXABEBAAG0KUJhcmJhcmEgR3VpZGEg
 PGJhcmJhcmEuZnJlZWJzZEBnbWFpbC5jb20+iQE4BBMBAgAiBQJQoZjVAhsjBgsJ
 CAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRAn3W/WPfX3UKDpB/wJijev63A8tQ64
 IqQvakpS5RAsrVJ0WqtP31Cb7aFWkelmyIabwOgfzeNgTyF2pdAI1+6mx24/C9AB
 ke2HwFvg7rXGeIm4S34tCvixDiJ85WHX08/V7f97//brueXE9EPjNZx9g9+fjPXE
 I9XAmVRMi1ZfF8HUHZUrJoEAUCK7lpa7WKmcItW/T/ojLVFSl3j3FJP1dJk6iHKW
 upKLjZ1gA33IriHkYkieXkPLCvZw/LD+Ei7KYyf7UacumQjx/T/jp2q282qyJ25A
 p7FEYY2oBQS7GHd+RLvkxZ2PeQJTgyoEoQEd0C6XU0oHpo658NToc91FKA0jfjcD
 cjESoWDRtB9CYXJiYXJhIEd1aWRhIDxiYXJARnJlZUJTRC5vcmc+iQE4BBMBAgAi
 BQJQsk/8AhsjBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRAn3W/WPfX3UH9V
 B/0a5kosi/15TTmv+Y2cFNtMm+LxGUv/xCZ+oaWJyTUAWojEWvaek4//PZ3XMVxh
 K48VvQNxMWZOsZc6mo/gelEaUZJ0mtR/FdK8CiMynKQkfifsjsz1Sjf0o8WdCr5U
 ghGKdj33ssw/z4cxPUTgeGGwPjnI4O+ZuD4SIk0MydQREaltmdBxpAm68mKLZCjB
 /lT6TiD7NRKVM+2KZXgNzdjiSQG4aSa21V/d2bk0mZWVvj51Oqx+vlfs3/u+cO6A
 msslous7RMR4fuZAh6Uewky4OsDdyEcVCsTciG6QatqYVXfCXM/3bOXX53eisfIJ
 iTcbOJdO+qBzqC5e37ffOG1IuQENBFChmNUBCADOHnVkZkSyHz9iagHZcJ8UlA91
 87movEUtJLFRQbgRK3T7qqxwVMJMKGPrOZpkg8l6zPENbbvVWBQmjjoN8v5T6WWH
 tRY14AB4I0tJMfNSYoU3Jg6u/vthw86y7SBrcapvrABJ1vVHGm8W3Zsjftcs2sEr
 iEp33O9hh8QU/Ynr1GUg1IKAC/14mthymSi534DGjnVID6H+Hcpm1pvKJpkf0AvZ
 d0/pcI8vySZpHw4DKO8bF2zPoeT/E46xPj8U+PP9aCrryOVCh7lc2nnVJeIe6jgC
 JO3ka/qRyHb8Er1mJpl2IISfG3Sg60vQVKou+/xsOp3GkrZYj2YHwTKk4ckRABEB
 AAGJAR8EGAECAAkFAlChmNUCGwwACgkQJ91v1j3191Atbgf/e9uK+1tHJgRl5rdU
 gzRHHrR1S4BtoYe/dYC1UvbXjZOthbVAoLOZDcU/eU9qTQI57Bcl+JdjQr9ZClbc
 akxYNKp7PtTDARBwNmbU96Dpf1ef8XdwiyD7Ifl6mgDkevE9AaSxOQjQzaePiK9h
 r8DSxlL7wDQ2QqsDU0mdnOxS99v0le4FoItlpujtcWwXG5eTnEejD1VmCorumNTD
 cksouKVOSfzl67swNUr5/8gx1PV0WvCmCCzVoXjg5Mpn7rtBxH8nOUDrXKTuRtRr
 KQmTCRJk7gkKyUDkdfhyoPXo0E2rRzVKw+BvzmmHRqGd9K7ixac/5QFHfvuNtYyn
 AA+Qvw==
 =8co3
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.116. John-Mark Gurney <jmg@FreeBSD.org>

 pub   1024D/6D3FA396 2011-03-03 [expires: 2016-03-01]
       Key fingerprint = 54BA 873B 6515 3F10 9E88  9322 9CB1 8F74 6D3F A396
 uid                  John-Mark Gurney <jmg@FreeBSD.org>
 uid                  John-Mark Gurney <jmg@funkthat.com>
 sub   4096g/0A4C095E 2011-03-03 [expires: 2016-03-01]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBE1v4mkRBADosekDv7XPyOWmKL+iT+Oc1/FUHxO3U5OC8CHEYQxoLod4jJjy
 x1GJ+nqZcwtnhww2/1+ty3LwHvsCYj5jeIsCMpjHp456+2Hdw1w2fC8hH0ENZR85
 5SnQGh/Ev7N3m00znbZLf0xPoaUZKFxa6Tmv0KflCw2Y2WCsN4qyhYCkVwCgzjni
 jXdXdi8ejv+dFKBmb5Vo6GUEAIlLD2ofYOsa3gQtdIyh9irx8PSri8qRAA05VcFM
 cE8r6F5pU53f9wFcD5KFVLXNRby8cdNhWar+K6WAhICGnck6ytmqVE/udZzLLmjX
 6qedsMpQSmkXB6xmUnBx8DQAfH4+V68l00qsZ9pJphNG3+L9uUERQwWDQP/ZYzVp
 R3hVA/9PXTqcF1384HKOeeddBowCPDJUmYeVm0d9jZatOwnrnhDnZgT+LDS96xm0
 R1yO577ka67c2bsDT2pbSYL5hkLWytXtLZr0nbTcczMJ1Bg4XIW+/QTkh09c/xhV
 J3pol7PAnrflYqAAaioxffVapFoyBdOui1KjrmPfVruHjj10RbQjSm9obi1NYXJr
 IEd1cm5leSA8am1nQGZ1bmt0aGF0LmNvbT6IZgQTEQIAJgUCTW/iaQIbAwUJCWYB
 gAYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEJyxj3RtP6OWS0EAoJE6fKmBrwM2
 vBWK7mVbThebaQuNAKCbgANUv2cKs5Jy2hAVjTjno5rr3rQiSm9obi1NYXJrIEd1
 cm5leSA8am1nQEZyZWVCU0Qub3JnPohmBBMRAgAmBQJNb+MKAhsDBQkJZgGABgsJ
 CAcDAgQVAggDBBYCAwECHgECF4AACgkQnLGPdG0/o5aKVQCfZiykMZLK0FR9vGuc
 QGBtjzNLs2sAmwfgI2Cnbzk8JXGxMGOFbHY4YV7zuQQNBE1v4mkQEADPw1wOhnre
 1LzHlU58meteE/Vy+OnwbYf5zzVqo04Sdl/BYGZhI/M7EQwSGV1FZV4r9JQg7j18
 rrPKT3vf5TYFBpXfgRYxxYxM2g8zCbqeJe5B1BmRu3Hj5hHi1m5P7M+cLSGUE03P
 pAMD11zyqJK1f7oF6ywpWD8Lcxc4n/tHzVUrH/fM6DuQE4Yb5RWQ+nVVDTyJ51Qf
 seD9PAIcLzCCjOB6qP882auQ+jfvld4+yWbpl0wQF0K8YXHtZyAaQUMANcgd6Lyd
 eQMwSN6gi6GxZVaUniAMPJr1lKd/tiLDxBcDDAdYYoDaHiCyab2dXcrhG4fCRmPT
 IYZbO3SPstlCKoo5ff8AUiF/K9gz6ON3MloYp7fdDBjgQtUIVXfb9NRxElNLsGvf
 qIVHOCVe3s1e1hCg7YRuDHLLsmVQfol9k2MhFiGIphaxgr4keurGdUN4S8KnzJTW
 KiTJ2U+P00oi6/McNqRRulbh3kk1UTlkjWtfHDfWwCsZtT1XaX5dD+7QCUJDOXF4
 gbdX4K943uQIrcbO1G+n9dMGCahHlTnrLa+AYaHkv4P0mRvxB4P6t1GHGJ2vBsSX
 YEi8iUP/ee3WM1TGnhL4lleuklsxpVLyZ8TrSpbjrbLgpHPgrAmheGt1agPr6oJ7
 0UZw/CTDBrzC4ASHPMhIjwZOgyVYs8+AIwADBRAAhAfgy4b32n2bbR4Qo2GhA4Qw
 LVRkB81cBzuP8iVuLHYHy887HEYITmD6+Em0TxUpavuntHUIDlHfNNPgTIv/j2Na
 am1cPziXCCOvEfM2nEhi3cyo88kT5/aUO5PcuLX1p1oJQJTK25wYzdduuyHozsyR
 2XYb/UfIrxtuSyyHuJEhXrdbL7tp2b0PsQn3Fv45UOtaHqp+J20UnFwkTqKakx6w
 oUwCNj+jTCthbnBmwNIuo4+Gu2ipYbWZ67lJLVE6zJ0/kJk3JAcTooZsIfIlSUUe
 F4Z40LJipOitIsGwGwYCUHQLiYBfcnJNoT2PWatACnrhO4SQAl3EHls2oOFObXWN
 FVCj2XD76Q/6TZ4Gxbzkf3ExVQapTeoBVtxpU/Bxa3TFy4fN8Ogvf+XAn/CTH9N5
 TwbxxvFd8RXolTVdKAPE3EoZNkNW9bO2oQOCrh2dNlvVOye8H33y5kJie8kM6CrI
 O79tyV3owu2hD7wNOIan7Pkh0VN4d4F0fTWrO1VdyKDdHKY9XQKYXQnMo7kBvFd4
 sSu8ljkaeDMTeQYSJrc+YdsthmA3E69y9OATObiS0gcl/Y7teP9dF/K1DIate8Z5
 6b333Fg0yesBl997Z6kQSMAFhwQlkq959hC+urfYd5fx4/306WoUJqy+ZR1eN0cZ
 CnZoL8O3SmZG9WTMYOaITwQYEQIADwUCTW/iaQIbDAUJCWYBgAAKCRCcsY90bT+j
 lrfTAKDLLzG4jeNeYJYz5lfmsgnt9A8YGgCgw78CtZGQhCM1stwwnMKXzADhlU0=
 =HmsJ
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.117. Mateusz Guzik <mjg@FreeBSD.org>

 pub   2048R/21489259 2012-06-03
       Key fingerprint = 3A9F 25FF ABF6 BB23 5C70  C61B 96D3 5178 2148 9259
 uid                  Mateusz Guzik <mjg@freebsd.org>
 sub   2048R/EA19FE8D 2012-06-03

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE/LxOsBCAClEi5g5IYj8O/1uc7Li2lpx/0fPAZ6/LwOMjvzRHDHEc/yCo9N
 /zTYToL+dQBgIxYj07PVyPp584CuxvesS4VYU+VXXJxxdtMq9gEi+siVCt0cwpWm
 bVGTZgLcqZqUT/sJfPqyREmU+hUcR+ELHGjD2zEiOJZg2dB+EoqE9NLFcoUGasRq
 WKpfqdm50ipVbTU3SdK2mh5CnqC4xp5LXgBYa0tZkQFNh9mSf1PXouj7Zn89Ghzk
 TaS+ZbyBWgftvZRxqUaxtK34N1zdMKcWzcLsOAaWLyepBkvDzh2tZ55PYml7f+Zf
 7s0e1n5Sr5T9GysJAazd4Sny/6Gcu+Bm4ToLABEBAAG0H01hdGV1c3ogR3V6aWsg
 PG1qZ0BmcmVlYnNkLm9yZz6JATgEEwECACIFAk/LxOsCGwMGCwkIBwMCBhUIAgkK
 CwQWAgMBAh4BAheAAAoJEJbTUXghSJJZBlAH/0i5SyqIB9CBKrtUGrvytgCRc3Ji
 4bPlXc9uLRs88AFj0Y9G79vioIgg3Rnm0B7fOtlcBsFTV/kZqUEcO3iR8MJDR7oZ
 rAEyEG/fn++afroh1iqgEyOIaO7msQvNqb0NB/HJIj1EknWqVAYBZ4WiRcli7R5A
 P/JT0ArgTLuKu17MkOhn0sBiZdrep3fN7z2OgY+BNgbydb7O/T6B8hjah+TX7rAB
 R+EmggzXVwQbDQBTah+BjeER3jSd11zP7e4mO7CEkg5b8dXnWaF+n2aj05iM/axK
 Pms+tZwO47/OKI17ZjeAjxAWrZcWuavWY2BDNzmCYpuq+x3x8D75VUMBnX65AQ0E
 T8vE6wEIANUeU+eTvPlGr2ODloNKL+KWTHDpcpdKyljCvKA/7pI0FX8Ojp7dCtvz
 UyXRhL0EuzG8ywUhxpf+KkuOlxD23Q6+FiKDL3oTtwAmYaaslo69zgLEX0ohN51K
 6QOPQlGFdAxHbp7DVb5peJyC43G2+5JWdwNq13Ha3nGWvWn1Qql3A9xik7/oFRit
 NATwdp2oecyFBkfhkQrGbecOmaa/hEW8eUg6pgfz8A+Tk9KjaKqJGc5vplANvddo
 3ngU/PfIoUb40onLz6ytzUdYyHXiEkcx+Dgu6Pb6t17osFHjb5FlcnYnrKen64hU
 IAAH9ckP5HqsOE5wIM9M+X5JczNtY78AEQEAAYkBHgQYAQIACQUCT8vE6wIbDAAK
 CRCW01F4IUiSWRr7B/dr9JsKVhfaXzF0L7cnzYWV5QqJCkvCuklEqd+yOdKPfJig
 ZJVtjFVlRO8u4l/Z+F433Pw+gvBkR8vVTw2Ni62vyIspR1CTG0X06Vp+5qHzVOZd
 LWkQWlbVDgWedAY6i5ABscW2VM9wenrDJu0DuSMHTdsCp8Z3L+rvBjRLmA4WzyQd
 O/IUyrZmyJP87S9RgEe4L7JhDcWNDglJEEgX+Qgd7FJOUBASlRr5aUZ0iYM00mth
 d/EdBbJp+tCbCOfxFhXp6ULDkS9ExN/NwVDL/GBXu5ckU1shOVoDwPO2Ib0lfXkA
 r7vGsL7VXiKw7ITHQKDJ/dc8ab83QPdl3W3QeSc=
 =gTKh
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.118. Jason E. Hale <jhale@FreeBSD.org>

 pub   3072D/8F2E5907 2012-09-07
       Key fingerprint = 009C 54BF 32D0 F373 8126  C8A1 D8DD 2CA4 8F2E 5907
 uid                  Jason E. Hale <jhale@FreeBSD.org>
 uid                  Jason E. Hale <bsdkaffee@gmail.com>
 sub   4096g/7081A001 2012-09-07

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQSuBFBJ7kMRDACdF9DTaE8bAAGh3Q/Dd5Ckst0s8Qs7cJrb0qWGRUqV8vmvJr3J
 b5v+Bgb4wSN2UM+Gl9EJ485e2zJ5TkzrUgo3rFu1quPLnPehHDI97fYtA3CxbNCm
 j9tyvqmMKbkKwHkTvyIV+Rk8HBbWQcF3fSaVDqqi/XodkpXUrn2zom6Cy2/yC2+J
 H4+ebR9QjQYoXxYl3MlM8p/W8QBU/65TZPCFAdvI9bWL2f8qHdU9TdIOvboGiWbh
 gsDIYqEmI+2GzOrPvnuTPoKLuaJv+6MVdnnnqKGo/xMVml3Kj5QgDzjvs4+xVVAx
 D+7mCXs9LBYwujO/Wraq7ljr2+5ZER1EiW/jQgNc7jeg4rVQk35eF1Jiar/ztwhg
 Sll1xbynuY41si+1O/dMxtP/Wa7ouvcinpzAVdT1JfAr1P/nm4ASicGCKlLkhROb
 OdNaxvckoFB2W5PLccsRPOmCMveck3HrbCYh7Wj4GMPcnai4pvwG7Wd0xHjtQ4yj
 rXqvB7mf+DL6sZMBAIroA/8lcVGnVc1avUWb2sJ0Yy8r8xZfGYb6b74XnhHNC/45
 iQx3kLh9oUp8I6VygyYM0G2dbDOaN75omszFgFhxzzD6nRXZweTRd7j4Z5BRclsK
 MVzZLI5ZRC3wOmcwxlELbANE6kaME8RU4g8ywXUHeR3hD6nJ02SQIJpUojFxezz8
 7cTwK3s2O+8f9d9UqMUXq+xpBBg26pDLrr+eITHxiY4Tecbnc+76W5rgfvaJaCM9
 yl6sMESUztG3qqibJ2iYy4tB2UmLWBMCu1tvSkA3B+jj2MLLMRs2OZunsbmozI9p
 OdPqkPScQuAlYHpDgVp/eMmd+vO7lLuWc1feSJ8HHL5l27i/kSnstDe/NVF8QHsL
 dKShZsITn94h80HG5rmgaGyTnw+t+K4dN6rb1+Xsm9Vx6i3E+57HTcQi37o/R2Vv
 jgHp6wtvv09mubWdvHk01+tZRV9md0+EPjDsmBA5DSDp9Ccr2D4k1B4ovezEqltT
 R8ctjkhPtZ1cv6UD81volzTE3N432Uz6Q1RvpROn2MzitirogG1LBYjhnfdhRfML
 /Ag1LAu8EiEhDpt1GANT7NuQ/0zl7VwhEDFbEW7F8g9qgG3YnrXdbg41PrELJ6xu
 VIrtz8tr8M5GbhbaZhRx88X/4XQFW7EiA4dmOlymwi5oxe1cgwzz/Z7khhNU7XAI
 poByqiUzEO5viWP2nYL07ewu9nJ1EVcsdffH2FNooSMfAcH+ZmdMoK+kMOfb/G9E
 DNYX3+RmrHfSnVbYJD45qIuYm8P8OgOcGTE6cgmSlRn6ki93e+to44ThwTSMWM/z
 NmleNL2CwsX/whKGqZAaO3yRyAnTHIDOEfgf66wXMudvA0otEybHFxZnyj/KreQw
 3SUWQkHBBxuaO1lVaPSE4qt+RIGsJM2ZzWZaDWkMN+qnJPJbr0tUjCVF1g+NUqCa
 5gPmvJHDrLdmTBtlJbXfL255TnaGGwkN8zhYoqEyRa5MDz1tlYkD+cnbVU6xyXRC
 nk7GZBR46j0uNl2W+rX9xoHFwNncGRrjKcr5z8+3R/e8CBYrvCwLebYhehegfo/u
 MrQjSmFzb24gRS4gSGFsZSA8YnNka2FmZmVlQGdtYWlsLmNvbT6IegQTEQgAIgUC
 UEnuQwIbIwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQ2N0spI8uWQf5/QD+
 JvzZL8okil73+M92RWXntxmwzZqylmCu8Id/St350ekA/2L4pbH+x1CDqWWHzL8v
 qN6nyTkvwzgJQmANRIHKISb8tCFKYXNvbiBFLiBIYWxlIDxqaGFsZUBGcmVlQlNE
 Lm9yZz6IegQTEQgAIgUCUE51KQIbIwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AA
 CgkQ2N0spI8uWQcMagD+J4u9BeA16uYSEFwc+eyklyH6qjJtnSoo/7NKefYULBwA
 /A6wPS6lXIgwV/ErxBPLooDOUBDpd9FGVAlo/Bru4DrnuQQNBFBJ7kMQEACBiPvP
 Klj+EbBXY7U0FYVLwONECLJ71B6dolunqQ08rGniXFaOO7B4a1ho5AJzfpCOWPq4
 20rmo59H+5HaGUuT8JJfk1V8zfxaMV6ze+qOacRt+0uAfMiBvtanAbnIojcdnhWK
 pxWZkV1VNma0xBkxNuZDy0D8rQ8c/wPlD2Lv/b7QXvk1rlSSNzw5JuwVk6TAGD66
 o+QG9wCkV/jfZUgRpiKSuiYrgGxQZAsAcW5xDlfHA9rPPfmcCRzKwxq+63AIbwcE
 LFJQPYO19JNzDBJ8RskTVnQfhL28U2Dx8jiDB/Qsy3m4fC+L29hLx8+YVQBsq1YX
 uDaqtfKEnYO/495ydsCMH9qv6LxdrXuRXNglov1TCLXiDt0s6rCdCAkpTEDta7gv
 RH8Ncycwo3YFOniQwwvV18n1dJlzue8o7OeGaw9YwA2JZlecJ5YPKOPpmmxaIrZy
 m4aR7NUKVSOa2eg5jPc9rMRCnduZAu/nVRtOlEPQWHIsebq5o4UBDi3Nd4bCcRGy
 3Fv+rWl8hC6oK31X/s545TTIJbsLbVSYA58rCMwGkwa6UjJJybOzhD/AgiRU4S4g
 aQT0Yt0c3cBZyjJteCOG4BG5TJexi/59mOcC4dhQuD3du3sfpI0g+PFoZXQYJ3+g
 xwAqLjHCnTe971RB6+Kud2UJc6uzSqBeH+z36wADBQ/+LXh7HQiC0GaB1p9SrbiL
 X4d9vjQgjmbI1Zz76C8Cfd+Vk6LGiU00VKTdNKs1QnKfcOaJqly+xEsxj9prE2zr
 jmU9RzYKSBDXKMdmfBFbvF30QSRlmiFuOwSNUHNOG31c5J4c0zluJFbZzSw5zFGy
 cKiRBZ7DlZuSnNviGqyl/AUkVVLQLnHbBUAEvlCXcvaFhwfTzT5sUgSWcUL0O1Kt
 89w2pmTjRSIKBsANb48WyujoeD0NjkBXVXDN1n7+1EjKh0v/DzhQgz6kuhY8PK8j
 NKzolth2cDeOlGlR/xupyNZW1KpLmYOB37tACJtFWcRG0NKMqzTfzAVAl1Hll1Vp
 qA0Ccou16KmCvUqwLWtEsmTswPCS0V3QKt2K0RccfpLQFNjKE5Qj1oguqhheFcB6
 TjU2XPEShGelPtB18FCcE9i/DYsNfRAfaN2DevPLGeZBUqV2Vbz94+4oJRSZCO94
 nUCAvp8l65euazPVsU/Xa74r9R3jmZa98XnoxlNWVgQ8mT+XcXfEqKow7kuO46vO
 6QKPR4qi33oKV0qt4v4hztypHNTzkhSbSSM9lhy68kNho6o42EqcTsJFpaKMW9SF
 PT0DcXLNQFhXJYH9nSdaW3VE+/2xygCEzNz4NROfaXU67wopqIb2GIx1NmZpgaA5
 be4BWQaHtyiLjJj6PIDWjLWIYQQYEQgACQUCUEnuQwIbDAAKCRDY3Sykjy5ZBwCX
 AP9elLKCOSeYFcEqwlvEZd3GASS4tAJPf7hPU04NEX4ntAD/QVdcx3kXm7z2IxLS
 qpi7F0myf/uBWfkmV1doJFiQMf4=
 =b+Om
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.119. Daniel Harris <dannyboy@FreeBSD.org>

 pub  1024D/84D0D7E7 2001-01-15 Daniel Harris <dannyboy@worksforfood.com>
      Key fingerprint = 3C61 B8A1 3F09 D194 3259  7173 6C63 DA04 84D0 D7E7
 uid                            Daniel Harris <dannyboy@freebsd.org>
 uid                            Daniel Harris <dh@askdh.com>
 uid                            Daniel Harris <dh@wordassault.com>
 sub  1024g/9DF0231A 2001-01-15

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.7 (FreeBSD)

 mQGiBDpjbB4RBADW+4fkXvVjAZ0A1X4wgXJQ4Eyes1LH7sTexP/Zm7sg1D/R9zV5
 w2kBwOhICRX/hxVL76YZv2MTNL/d3pV3ZW2yV3Z6H7Pq7s4oVn2q35owUwLQZfSI
 SBTnBiVN7NqMZ/kzCCdWBwg/4G2FVNFwc7RyuOFQL3ly1PBtgbANbpCyfwCg3QXB
 K6AtFaEP2MA+SWWHQD2dNxcEAI11cbOHbYU8asIxbqYYyPOMgPsaLlPiTh6JQOO0
 2OiGxoQlmZvkhlWf8B9ahCeYoKgA1zPqdHA2C9YMvOV2LvN+/Qi0n3hpqkfM7lLC
 QMJgm1KxIzccWY9Iz09GRlIFm2JPaCVLsKh1QPW50c3yO9TMSa6lXwiRgvxPz76C
 JHniBACa25NHH3x8zx5KA0FgMM15Wc481777CFVsKazNay00G0HogSICZ5lHffdi
 1O5u+qQHchVKL0Lbe1zhdbVHdSAbEqnKTqseVMQ6I1TVu4gO89B72aY1RxAnAYjh
 PAb5W/RhZBSR5NDVZyANnqaGE7U7KMqn4/E0lC7w1TzoIZvDMrQkRGFuaWVsIEhh
 cnJpcyA8ZGFubnlib3lAZnJlZWJzZC5vcmc+iFcEExECABcFAjpjbB4FCwcKAwQD
 FQMCAxYCAQIXgAAKCRBsY9oEhNDX55peAJ9NKai2qEcFLxzC14qDz80zBGwP0ACf
 YhsW5qhTw/Rck1Id2W1alUEXMre0KURhbmllbCBIYXJyaXMgPGRhbm55Ym95QHdv
 cmtzZm9yZm9vZC5jb20+iFoEExECABoFCwcKAwQDFQMCAxYCAQIXgAIZAQUCOmOL
 hgAKCRBsY9oEhNDX5wXyAKC6VLe3svRc+FgmmjPS/EWvi83sDACeOpmPRbViajOw
 4MUhKA7hxnRlBeG0HERhbmllbCBIYXJyaXMgPGRoQGFza2RoLmNvbT6IXAQTEQIA
 HAUCPSJfQAIbAwQLBwMCAxUCAwMWAgECHgECF4AACgkQbGPaBITQ1+dSxQCgsBwM
 uDviakYEKswiv6zMHfYBBCEAnjMyu+oxjKOWOo+of2qmtQH2LNg9tCJEYW5pZWwg
 SGFycmlzIDxkaEB3b3JkYXNzYXVsdC5jb20+iFwEExECABwFAj0iX2ACGwMECwcD
 AgMVAgMDFgIBAh4BAheAAAoJEGxj2gSE0Nfn6bIAoJlPaQlqk4wbNGoscjigAp0R
 B9ooAJ41JxSh9w2S16mFTGNKvVpjXw15BbQyRGFuaWVsIEhhcnJpcyA8ZGFubnli
 b3lAZGFubnlib3kud29ya3Nmb3Jmb29kLmNvbT6ISQQwEQIACQUCPSJiFAIdIAAK
 CRBsY9oEhNDX558OAJ9iOqCDUX4cdNMSZ1KBQg1gfTn1yACfZNL6BY+mYC+XV83L
 7DXacstXHlSIVwQTEQIAFwUCOmOLtgULBwoDBAMVAwIDFgIBAheAAAoJEGxj2gSE
 0NfnaM4An1YVu3iDtrG314UIuZoTw3zd9ucxAJ4yg3vWB6ceg06KuyaGTJSdZ1Oa
 p7kBDQQ6Y2wkEAQA0RSR8vkmX33oyYl+LwlOmemSKbSQFZNImw5TDcRYX83fa1Z1
 4oIgJSk1h5l2jx/+29chVR1nTNqPYlRQEDMxVby9rMq2RAnjorM6oDdtIQIBNJ63
 vmUcUiORGnKhC0waajpmZibcxoUFk1KcLyfxOT0JTOLgsJfqdqUENIc6NqsAAwUE
 ALaLYnBOoIr5Wm/KC7wRtS4gHeeOeskZyyoa3+AeBorDl0VvpgYwlNdAaP4xJrx+
 CH6UYnxrMgCXG1l4dupkGXOCRPlAcM2ouEyDIGHRTVqHy40khZnWzN7xfZhKNcVd
 FxeHqOG61ZrhcMboxZrdJC7hK+sYrbngeKRiDs4VRoOuiEYEGBECAAYFAjpjbCQA
 CgkQbGPaBITQ1+foeACgme+2LKdFkytbn/JUhBqPYVAD8KQAnjP+IDVQ3PDEKRkv
 AFGJ6i5SrWJ6
 =j+GD
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.120. Daniel Hartmeier <dhartmei@FreeBSD.org>

 pub  1024R/6A3A7409 1994-08-15 Daniel Hartmeier <dhartmei@freebsd.org>
      Key fingerprint = 13 7E 9A F3 36 82 09 FE  FD 57 B8 5C 2B 81 7E 1F

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQCNAi5P5owAAAEEAMIKNuDnLGiTOzk3kGMmz1ii9FbYEM6fKdf0jSi0YSTxSWAn
 7EZbBehJ3yTAYuCaGSEGXEWismycc98LnH2Fb0uI2EsJ0CVLJqxsOL3DK8XE0YOk
 HjSKUpmJkh/BKrMAmUnqhbD6YIBiKnZh3ABt9+a7A+SakJQxvtQ9cYxqOnQJAAUR
 tFVEYW5pZWwgSGFydG1laWVyIChMYW5nYWNrZXJzdHJhc3NlIDE2LCA2MzMwIENo
 YW0sIFN3aXR6ZXJsYW5kKSA8ZGFuaWVsQGJlbnplZHJpbmUuY3g+iQCVAwUQQGso
 RdQ9cYxqOnQJAQFBSwP+IIm2bFprpayabQ/VgXp10OD3sgIEtH8c99sU91LyotNT
 ySif8DS+ujliDk5wVnaOlzqrV4sga8d2ybM81hdW0nxI9dNxLIp+ti90OecZMF6M
 4PlsdkYGnqZDzXlFg4o70GSAWKjL9RTG5JvNnYWS453mCjYc3O4dm+1zzADfgcy0
 J0RhbmllbCBIYXJ0bWVpZXIgPGRoYXJ0bWVpQG9wZW5ic2Qub3JnPokAlQIFE0Br
 JFTUPXGMajp0CQEBkqMD/0D1K1hTJc8u5K3gpsk9LrnOVYpP3zHbSe94oLO5tHv/
 b/Y1626xqcMKYfAIk435asuPnGRkMjgpsxPUKksfWMlUqW4aIiX7di6aMuWkgSBI
 BXguu1Dk/qRImOZkNzWc3V+/CQ+PIauy2rZubfW2+oVkW1iEmmO7I/nPqDxDBNBI
 tCdEYW5pZWwgSGFydG1laWVyIDxkaGFydG1laUBmcmVlYnNkLm9yZz6JAJUDBRBA
 cX8u1D1xjGo6dAkBATkoA/9aDk7yNvh6urP9EWcPv5mjJt0yYIIjGpV7VH2P+mTa
 dK14ah24HSaTjh4psJg/uFw4egAs2XxDKXrf1SHCaaVajC3VQGvKq6V2Ytmgw6qe
 Rtt+NtrXVJn5EUnMY3+G8YCXugulym6bUWaC1x6PC0Y2IEzRkM3H5Et78gd2zujB
 o7QqRGFuaWVsIEhhcnRtZWllciA8ZGhhcnRtZWlAanVuaXNwaGVyZS5uZXQ+iQCV
 AgUTQGsk+NQ9cYxqOnQJAQEV6QP/ZFHefmwjiex7zEU9uhzjEdZhDlM0szKULUoo
 TB4x3yiXiYlzK2aqppXbV+vl+t2VLhd3McH+SKSiKwoBVWrdqsXguruIjUYGMAJI
 aE+Zh3OGUs8sZhtQqn3nE4+VngpyXwPwXPrDhQiwwJRxj+01lupNwS0Z6cAPmD4A
 W1L0aSc=
 =HsTV
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.121. Olli Hauer <ohauer@FreeBSD.org>

 pub   2048R/5D008F1A 2010-07-26
       Key fingerprint = E9EE C9A5 EB4C BD29 74D7  9178 E56E 06B3 5D00 8F1A
 uid                  olli hauer <ohauer@FreeBSD.org>
 uid                  olli hauer <ohauer@gmx.de>
 sub   2048R/5E25776E 2010-07-26

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBExNy2wBCACnfGsjuSER/VsGsmS+w4R/Z7t1nnLydNTHCLkQn/UHpCFrmtZL
 +Mil1qgsE3+japETQ5LOsJaJOhrfGXtqD51baVm/CqCkj6Hl7I5Ex0GDqmKyMBrx
 SqBKvxRLwQF4yrvfoqQsfbMVnPPysFabbJrnMS+6vCfu8DnYkg1RgJTq3j/WZUHw
 fuHT3zJwliyKJjQrWEFLeHXsOvtfBIJ5XX0s3NKrfBITsScTXgjCMUZwyadKC3q6
 Y++c4iOfZFbzPA/8+mt3EAhBrYbD2nIJUIqM+PJkaCfP5IqDgSb7bKPCjof4M8CX
 OwjWCMh1kfYVmf+j26tkBmM7ueIq4eTMHFSLABEBAAG0H29sbGkgaGF1ZXIgPG9o
 YXVlckBGcmVlQlNELm9yZz6JATgEEwECACIFAkxNy2wCGwMGCwkIBwMCBhUIAgkK
 CwQWAgMBAh4BAheAAAoJEOVuBrNdAI8adCIH/iNoEYrMzla448FSilwIolYjcX4x
 6F2y4diB4OMdv7WE7D3dPVhrgYAZlfNqT3QZt1ADQePt4/v/QjgQ+03SS1/UdRRJ
 Pc82L/TWZ4Jd6r7H+yIoTKLDwcMW6vpcP0uFoduLw1Cg3u6VNiW3fSGtjU8FfLa/
 TaohaA2Dxq25Vd7B8/6tmRsZ36oIPecEWQ4XqpNrR7DBhbgJmY2TPIOD6cQlmnZG
 x4TfzYKFtCG4PaX4v8VIuwpyhBzjWuKoFi44N7l/mYreD5et0G3865HK1ZtJ01ax
 VDyyMWOadFK736w7iGmPRKi19XU0bhdvt1PX9dSWe5dvRGaqpTyyEEHx9sS0Gm9s
 bGkgaGF1ZXIgPG9oYXVlckBnbXguZGU+iQE4BBMBAgAiBQJMTcuLAhsDBgsJCAcD
 AgYVCAIJCgsEFgIDAQIeAQIXgAAKCRDlbgazXQCPGrckCACebFzIU4TmOaQA/kaV
 djHZ6A6oxaFWQVC3NLOYQlOoarXr4KHdtjnlBrXvQP/a8L/RPdrlNteBbk2FrXxz
 3BpCGHE13ScSm9HVtM94WyZiUUzERc3QOLHNM20236a8PstePRjy59G/gH/rgrdq
 j0iCKg7hF3jaYRAm6DNgivFb8QWZ3e6wt/QBMovZj6Mlhy8xR+fjUjlslNAeJ9dX
 4ozeoFXp+IaSztdBzZsUsbourE0L6CfSuI0EYn+wIXuyu8xQs1eqmJ3NyBYNoedm
 ko68wqVQCd0MCWRJbpikaxvkMLDVUt09raWDEkgLkRDSYIDwCQrioGUXndZpeBkd
 W8vmuQENBExNy2wBCADFHqQ/L3Iyj4Sx35/ljLYje0XRXR0WI3QN0ZZSSMXF1RpV
 LQKH2RMUV0KC3eUfb6yYZoKzNiY6V8CTkglTaBAy24a5gVm5sI4SO4mY0ml54TwM
 GDMp1kbVEjTscwzlKp20LHua0W+P9oj9kn9HkKt5CrZvx4nuE1lIMxzIyXVLKSmQ
 GxtzpFA59oObzw6+h5klahFP5HCeD9p1ikUaKRQDWLKldf221pU1DbM0YLrVCG3m
 bA/kxfrghP44R4uQDs9SWi1Ezot9f7DvOeVFmPINaFHnF95eEDfuaqJEZbG6j758
 YyasYjK+Ed5oi3NZVGjMZFThA9Px0rdYkMXgl8QvABEBAAGJAR8EGAECAAkFAkxN
 y2wCGwwACgkQ5W4Gs10AjxooWAf8C/e9xYKOFsuKRaP9Z48KJ4fMJSlzIVwolBAY
 5+Ok7X9gJ7gMw/WvXFsi+zammuHOseFICsELWKW4wmmv20rIu8o8Grk//M1E8Baj
 t0RpRG6ZUa0Emn7DALYI079DXofjWfzN6J8Ff7u7OY4rkq3CRYomAOUKsKQNtF7A
 saFIZz9GEhZQ0DnONsi+k87yt8U3N1Pjf7sv7dIouVuoT7AMGA8IfGjyGxaBqydA
 4bWSIHO1pZbuuxxNidE42C7SIFQplwyEHEKPl1mteMDJxKGnR7sb5SNvDsf5t4B1
 9C9j9upXeOqx2OqfUoN7dXT7uNmc9My6Ng9yJwFTHat6xPSgjg==
 =cHUi
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.122. Emanuel Haupt <ehaupt@FreeBSD.org>

 pub   3072D/329A273C 2012-11-17 [expires: 2013-11-17]
       Key fingerprint = 920C A49A 5A23 F9E3 4EB0  4387 AB90 5C56 329A 273C
 uid                  Emanuel Haupt <ehaupt@FreeBSD.org>
 sub   3072g/70183B96 2012-11-17 [expires: 2013-11-17]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQSuBFCnfG4RDADPgmrXmj/FXtx0ilhLSpDYevUYhhoyLywIWmgjrcBBTCPcO0IC
 Vn2aQI68hnTI4BTWc+aDXbzDOK7KT1o9E+2Rw12qKcbV/psrkmi+Hg0mFttB47aW
 rZG9lYPM/KBudXCoojlF/Ip2n+KkLX/QHN8ip8A8RkOsMk2dAgVyXT9RK78MTVx0
 CkTXhhJcmYJkYuyZdy8y1nlTt1LhO3GPmKRmdqkFG+H5B/zhgHy0tpSKJ67or8yX
 1RvPIxv4Wr4vTengA4p//kibbLOa9rsa4aSjjZvDvOHA/o7Lo3ZypRj+0kYtbT0R
 vP4w4+I8x7Dtgdjl7m05m7MSVMwQHn8alV61EHket8F1wXaxJ5HxbJDeuZkQCgpK
 g6I9CPoNmc5qgmd0Ad9QKWNhDPaWmx8fMCXTJB0+QBX+4ENJHzFioev4ynOxesxL
 L3UZqxV54/QDPcYfZxyfu0K4K9OASEOwrrLpqAil1bahMmZKkO5JfcIw5dJLb9TQ
 jNLz5kudt0qGwrcBAJTo8KTz7pPqnQVKABgwm8gJzZRtTOkb8WqRMYsTJRFpC/9L
 Xy2DnVGmkD4mWD4rWr/mDG2l+FT66cP1HiDBQoJAkGJXgx5DLcPgQwVu7vS1utFb
 x1/nawvnq6Qp/yaAe4UentHUZADgVdogx0AEbCf1QN1e6l3h/S5UKZjLHBu6FKDs
 0HX2rPGwxGTHWw3WiXfM0NHgpAvzg1j3cdjQhT/NDKek8Z0Gr4CnNdVgfbOBM12y
 rSGKlEeVpCf8DFYbMEMu9zFJ6J3JiNBR2U5/EOImYZe79qRr9MS8x58/nj+pc/jx
 MDa7C/ckXIauo2qN4XWsiTFITlsKpQMtIpdNkfd/kZQ9fl6i4w1eWwtCVrcqYs/d
 TI3o489D57jGaeppRjT3yEXyOYgyb4Amd10rzW8PtAA+S+CK7S0enY1vXznotG/u
 5/lhDrldnxJ3cq8LfqG5KePfdcUy1dQK4Vfnlbf3dyIpuSPwXNJd78x2wcElKYrk
 almK070xn/Lf00HuczwxCCHNZ6HdrZAkvO9u9MI7mxp28Y6RZCMq1Ieh7Y+k/6sL
 /38tgyFk44ekdbwLuXveFfEivqoRHPoFyP8UYK/c91bnBGF9Bs6eCcX6W7sENv36
 QzbUgZe8RQJWxQjpU3GvRahe6mG3B5bOySnCTqsJjlPxuKI6XKfhl1UE1K1tqi1p
 3CtUNCLLgmsPNyFq+JNBh2OjFdz/tQA6aKN6aXU006amKbctY1J55xlgIONgt3fy
 LJYb1S30+H0FFm7SCtPX6Q80IgMJv3bvYg/vcEcE7Wz7k8gtiVZhv4synviVgXAq
 jOR1j3Gtf5K1gev9iNTmSxKyJgmZcxUEQuJxGI9Y3sxxKGVomT3Fv0PLF98KNM4z
 s8bGH4ha2epy9BuY8kHNnlEvY9IN5cxyDbgmkK8Gj3YwH00wNcz6YocAC+AGhMmJ
 hBb5BiDZaFAv8tBQO0rEPwMhPs57xZC+0OtFcYfWLO8OYA0QjrqfncgbJEcw2v/Y
 6tV5WiWgpKgcKwgDzFVkAJgrmyd8I5aYlmdLE8uqEMvPLAnrbnnX9MnbXnLfC/t6
 WrQiRW1hbnVlbCBIYXVwdCA8ZWhhdXB0QEZyZWVCU0Qub3JnPoiABBMRCAAoBQJQ
 p3xuAhsDBQkB4TOABgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRCrkFxWMpon
 PKQgAQCJe+bYbZTr6ULASwjtBNV0Yrigpsnm6qzAlqYkPuEpmwD/T7OiSNqV9vvY
 FeHu/gyUyfDgsL+CWNwvcqWYMenQ6Cu5Aw0EUKd8bhAMAO9ELP2diWa2I54Mcg84
 RjtV1Rf6qHz7vfZC55UYnQhqnXu0Tl9L925GWoRFZFebhSLXD33W/zc/s0/olv9F
 caPUnM2hHKbLATEIeFqmtJ0OLSvvmTk9CubFby1c5HKPXtKlZZFSp8lh26Mtoi+e
 BH4TL6AUuYTjIHvr6QRaj26k/D8GY3wINikipl8epwka3xTL0BPN/ANQZVDk1Sal
 5dTIVj29QLVe6iE9Ijw9UQsq8rR3Ik0fYfjQYhkzm0yH5cSw5L4uDIU4gOEu5C8L
 SyxY6qmZDn7ElIVv78lSmDgIcOTCuSFFyyqj1P4QB3UPyR/ClnTX/uambNu8qIa2
 0XwNSLhu70rsY2ln6URFXmuTk7d535LLPCRaf/PRnz7M41iAOOMhJRjhf3WZ+6wV
 f6akRVsSm27j2w6N/ZtiM45A29MmJz/ujcuG3CGz3Ha72dNtgS/UC4kXbbnXUklo
 SVjaUzRGhjpN+x93h/Kp5qFKeC9W0jhUeECk/M60D+LsuwADBQv/faGAWHcWWGVY
 PgbSyguLTT8NlSrkGYgcwTLiOyEgLXJNfdlJrKq7gp9xQtKs7CccFfEsY8j9+3qo
 /xqiuxUtLo3ur6k3yFtvwU0k16fq/aSdo70VFBnHYefjky0r2WRPTSO3PTvRmRkO
 hBcJ4ZOwn8JIPxTH7mNcdJMGwW08kJFZOC1nQaBSvg30U5vlfiREBXMBidCv3BDl
 fRFeaBPCUQsXacLoFmOEzXOfWQrZ/y1HUxPOFMQqFwLtEeaQq5hf/uG1wdUMfb1B
 FDlXtSYAk20LHBLsAQRnOlQDS9g8geLy2tttbcPpdTehI/pIrcay8gXEEestLm5E
 cqfoR5fg+7tnPyf9wcc+GsWhgWw6PM75whraLaEvPNd9nXl4GooHgykw/nVFOEK4
 7WU2pPcXEi7DV66tssOBWXZxMtJ29zQeT8siH0fUdnBriQyzBoFeNRXhF33pcHPn
 DTY5IW1KzI86GT34IF6p8xQCp6g4TRTMZfU95+GhcCDSK6Fny1sLiGcEGBEIAA8F
 AlCnfG4CGwwFCQHhM4AACgkQq5BcVjKaJzwQpAD/UfTcReU55HdN/5tI/0Fr6Kku
 0ZbDaulknl6JnRmdK4kA/1YU7l50NXukqvMxsaGhde7X0XYDptq/FZN2J1xKTsqN
 =MqAu
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.123. John Hay <jhay@FreeBSD.org>

 pub  2048R/A9275B93 2000-05-10 John Hay <jhay@icomtek.csir.co.za>
      Key fingerprint = E7 95 F4 B9 D4 A7 49 6A  83 B9 77 49 28 9E 37 70
 uid                            John Hay <jhay@mikom.csir.co.za>
 uid                            Thawte Freemail Member <jhay@mikom.csir.co.za>
 uid                            John Hay <jhay@csir.co.za>
 uid                            John Hay <jhay@FreeBSD.ORG>

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQENAzkZeP4AAAEIAMKg3LRpUCJdg9V9Pr0KIdvaQeItf5Fcrbh0GE4skfNPKeTg
 TQifwdG/GrMPYJBPHU8JnFqumLUnd2VSoFEJ/6W5SOZP2l5ZCq496pGCSekpe+kR
 dN3Ra+GoR+cWVLKuXj+IxA0Ziv2WEl027TnMhWGf/DHLdoWvSwJdVrGnk0KjBJGr
 HwWE6VGlhBSoOWMa9T0tb3sRVTEIJXDCn8f12eixx8XCzwIQJSgWC+ThrY+ZO/hz
 FRR5yl+izJfffQiLjc4yY0rXqDu9K3i+/0lWywcbnqMtRj8Pnr3j3Lzft+xex2ml
 qX68fE6dxof6Tc3GQCEqelj0IOAb8Zqy2qknW5MABRG0IkpvaG4gSGF5IDxqaGF5
 QGljb210ZWsuY3Npci5jby56YT6JARUDBRA8TDj/8Zqy2qknW5MBAeMwB/9R+Nvd
 bPPkvll4Qaw9I1FwM3iaMDM4IkqR6r+Gsi+RYIClYmRBU1HXZzKyNR/Ysy0thnIe
 YO2yg7U2nYJ00ysSZl1Hd7R9EQBuYZk647PMKbQ+pQ4k9KiO1ObT9JivWz6u6R3l
 gJMnCUEi6s+xW88eeTDBO/AKE9eUUBDZ765M3WcVmGfDYNpW/D3tX7taGcFT80DG
 VXKnFHAP2Um8IZeHXKGqh/jTTNCqwz7oj3GfVzzGEnmwI+goZScQWUl5J708MnOf
 uxiuOMBs7SLsvg1d7iEkO1oCDClv72i2Sr4rPuybIPMMPIpx/DpAZAIiMYHJ6PdK
 nMXSYgk0GOjx72pttCBKb2huIEhheSA8amhheUBtaWtvbS5jc2lyLmNvLnphPokB
 FQMFEDkZeP7xmrLaqSdbkwEBzGMIAJLwFCCICbR+kqejjFh2BznIOT69PIfE422e
 C2yD23fC/lqZ6LixxGrsZK5TxRycWw7fq06h77kd/RX8UMFErphMTkIapt+wLLoX
 qGLcY1dVyNhW34SutdHzXkMFo6T8COAautpnAMhrSh4dBw6XQUreVqc1BsyXL4vT
 LyI1/E8E3wELJZHldWQ7ldvXPUOaoJp5PJ0FIV3Nvme9g8U0BrZT/NjH06mYgsKW
 +40ZjeRycvA9Yjh+ONAOdX5ijn7QbixjSehFsmdpx+KdNyZbp6iAIurf7ysEp2Qm
 N6K/3EukEnVvy7Nn1L8+7K4IDkK+TocpG/m/P67w1AlrW0tNAMe0LlRoYXd0ZSBG
 cmVlbWFpbCBNZW1iZXIgPGpoYXlAbWlrb20uY3Npci5jby56YT6JAJUDBRA5HN4y
 wnPlMN5G9U8BAQVeA/0V4alPthF5+FVL7GJ14R7IQee3NkepbsCQrWfDl11DJkyn
 DxyISqzQd/ur1v5gziOMppQ35rekRYxqqmcKSg8oZtcQ8WFfrMPOYDDn8uTXmwX4
 OgLuW2EnJc0y1JiKuew1tHRQuoObZtO9yePRKkq+cPgLn+yrjPjGAJ1AuUL56bQa
 Sm9obiBIYXkgPGpoYXlAY3Npci5jby56YT6JARUDBRA5HOfE8Zqy2qknW5MBAXAc
 B/9QuIZEQJDfYJyv5Ztu9mtEUZoFfavYmLnLvbUz0rwZOzv8/krEQtkdVvkWYWQc
 JSal11h7L1EyY1YzrTnANkq4KUboeiR3X6RZ+z0p1pg5C0imWFdMpqnY3croHkQy
 0zU/d/kDd9mU3xismVbDa9xSJHbFh5KDpvnbeRxh5VIXcdiJ+RbM9VNqsMmZwCBS
 DgY/pyRuyiMM91L9IfWlOUwllAEHwedQg+ja4/M1gyiGKr7rmiE5LH9xbInvRR2F
 rQKDtmU49MS7ybHoLfZ9GXKo8iTNOuXE7OGOx8kIuapiNwKm2wayng8utIxGacoO
 hp8D0uj3dgTFUZ3pcMSxtjWEtBtKb2huIEhheSA8amhheUBGcmVlQlNELk9SRz6J
 ARUDBRA5HOgL8Zqy2qknW5MBATYEB/90qkiF+JTQZMN2wwlLkXiadUd1uHK8Um7q
 f19t1pI2Is0BNxtBwVY1OlrkpFkSkpSUHEmVKUVhHjsHVV+r+EdJ4dTcsT6c5cCJ
 i7avfz8duVbym09yDLytnBGr3te7tkmalwk3JkjXJhiMuUW9w9woCuVWRexlABDm
 Md8JjvyLqIe6bNkIcE9GvHhQQUYegYqVhDqzKH+cme1olSYDDjt458yMYo6UXu+x
 g7gESluIgGpK5hKI/MAw3r/XgOliBa9igg816jrTFiX1oZT6dgDKlzxNS7J/O/EM
 GOmNi8N03Qx819oKlUaMHAFPNeUfdT74bqVYbDo/GJptzaQtUiMv
 =l5Xu
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.124. Sheldon Hearn <sheldonh@FreeBSD.org>

 pub  1024D/74A06ACD 2002-06-20 Sheldon Hearn <sheldonh@starjuice.net>
      Key fingerprint = 01A3 EF91 9C5A 3633 4E01  8085 A462 57F1 74A0 6ACD
 sub  1536g/C42F8AC8 2002-06-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBD0R0hQRBACPEDZc2XKdvIq9F4ofeq/EUB8ISFQ6kaVPcb5ingy5ND+0MUbz
 K9U+q6Ik8d67KfHHvqGn7XTOXxGu2WS6rIa4ElFHtG/9lpgYtOFRZJxM8nv5+zCn
 elu18skUNup1y3uIwvhNUY3OPSzVkHC+tUPWfW/8DqdJzud/l8sDFDRtBwCgtixB
 FHJ2jRXInApVzwLcjpgVJq8D/ixzt0O/Zg2p62/qyAHac7M1sEc2QarCAGwRbuNw
 jHRtglxQw/GT2NACWqy7lVHKd37ciCrXg9QrTjotJtMcoJbCitYvbQo2RHfEeIyN
 yw7rffTQ4CpB51KxNhUWHcUfe6Jhx2hgHzehJg7hYnbtSv5hJcn2DXMSHHyHwBri
 hpldBACI7iJxl2MtFUHBo3XW27WYDzTNTh2LUaMcIaowMW/+vIDds6EI71dCAjuU
 Ai8DcNacMtE0xRdtNzDMS8vgYWBVLkHv2ENVdLfpxhM72iu4tmPKGF5AXK191dvJ
 qPge41Z2/57191Xt+keYtuSQDtXwZfSu1uLOHBa0BBvmppBOtrQmU2hlbGRvbiBI
 ZWFybiA8c2hlbGRvbmhAc3Rhcmp1aWNlLm5ldD6IVwQTEQIAFwUCPRHSFAULBwoD
 BAMVAwIDFgIBAheAAAoJEKRiV/F0oGrNMRsAnAlWdC5LkmEF3hZjNAIA8gMxkfnZ
 AJ4k6LXdmHMSSPbd48MbDYq67yzOG7kBjQQ9EdIrEAYAib54xuFqjHpvLxXmqFRl
 qAgAD5XpavuJisxGjfm7aTVWIpR/OOVFYkW59YInHM7dDHL0Y7tQETeEKf9pj6kF
 TMyWFoBjtdazqSmq2YXOvI00N27IKT9eqxJ/qR8QgIqBMNkraP9QKi60ASDIRUtl
 OZSfokSbAKkZMTyS086CgWw0bCPXRCvQLHDjga3KCbht0AjrZFkGmi6r4+rXFnT6
 D3JrNSQ0Hj2qFEixHtZvXTsqgsEkOEtoe5taMFSygM0jAAMFBf97Ip2a/kPkXNt0
 p+2xmWIFEDim7J9Cwl5viTb1t8fOKx69hFDQ2BwPNDZd1HvlrYTpuJ23uTrDOZsw
 IT/wVc/IQ9nn4+mkxOmq9iTHCBS99OXz4IsODT3W1sgzUfl+mdqJP8xfEnsyqy6G
 ivOoR3QdZg7rxvOU98HhDQ1iJX3rCtLNFGisrovDF33oHMEE4oHvSMXeg65JXWiU
 EpEpioINjrA3P+TL+fMv1tb4+wSUPqTWX34Gx4UfDKnMedxl6j2IRgQYEQIABgUC
 PRHSKwAKCRCkYlfxdKBqzVtaAJ42mqzwmJCpk8fdsfkHUt5uGTN8sgCfdmDni1OD
 NWQi1mhQOXZX9oGgyso=
 =PTeT
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.125. Mike Heffner <mikeh@FreeBSD.org>

 pub  1024D/CDECBF99 2001-02-02 Michael Heffner <mheffner@novacoxmail.com>
      Key fingerprint = AFAB CCEB 68C7 573F 5110  9285 1689 1942 CDEC BF99
 uid                            Michael Heffner <mheffner@vt.edu>
 uid                            Michael Heffner <mikeh@FreeBSD.org>
 uid                            Michael Heffner <spock@techfour.net>
 uid                            Michael Heffner (ACM sysadmin) <mheffner@acm.vt.edu>
 sub  1024g/3FE83FB5 2001-02-02

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDp6LpYRBACHINF1K2lJiWCFAgY36X+NFDvgbRe9U7BKy2Q8ZPouMOi/GIwW
 iocDyVwRnK8tC3D1BM3THs3cFW0aPsSOTGngZE8rTs8lm53UWi1UApTUztjH3odp
 OynMb/Dj3k8SOWkq5mYYzl+38jsz067tRDlij4s4I3EjwcBQJOhnUUWV0wCgpDBc
 wAx9TBVCSY9H5YLtCrJbnOED/iwQH58xpFLxQO1FDYlUCZgZaASm0luft13HuCrM
 Zj2oDgJZOcuP2AshoJXnKavDjwBIvgf/p6cPZ9CS0sF8WI+v/LHN/EUQQoXXNzD5
 ZujgMh1w35nMvl7fSJRDaie9HggnUx+ODtWimmROpiicDXb849asCrUUEcpU0V3G
 wYaxA/96OWzf/TCr6CZABFBCLq2VwX3Run3ttBiXOVI69gEDj95mfeDUxPQH4JNt
 /hI1B61Ab3/yDWmjzrW7Kb2i9URK4OKw/95YjoC2g0t/CFrmFi82UwMsmUp4mIqJ
 eUrQ202IY2zCqCEtHcTbUdXrP1eFkGmi77s+KzzzknO63+efXbQhTWljaGFlbCBI
 ZWZmbmVyIDxtaGVmZm5lckB2dC5lZHU+iFcEExECABcFAjp6LpYFCwcKAwQDFQMC
 AxYCAQIXgAAKCRAWiRlCzey/mTswAJ9uujS3rA/mJcR8TH33q6SRhZSeFgCePzaT
 lOAkDv2LVm0F+V5CBex2gkqIRgQQEQIABgUCOs49wgAKCRDCpSwr0i8VsUrfAKDi
 Cffo5C6Ei5xHtWRA0DpHChOoOgCgqwDeqC4zLU/lB/jKYdGX37VPMQO0I01pY2hh
 ZWwgSGVmZm5lciA8bWlrZWhARnJlZUJTRC5vcmc+iFcEExECABcFAjp/gWcFCwcK
 AwQDFQMCAxYCAQIXgAAKCRAWiRlCzey/mRbDAJ9BS5FWb+Dj4IHlRYsr6IHCXxet
 LQCgmpN9GwBWNxzBlbAQEw1O8anp5xiIRgQQEQIABgUCOs491gAKCRDCpSwr0i8V
 sfQXAKDW4IsDEKGr1rYpO4IIZPMl2hVLJQCcCRUr0Mfce6AXKUYBfjAlZmddN0u0
 JE1pY2hhZWwgSGVmZm5lciA8c3BvY2tAdGVjaGZvdXIubmV0PohXBBMRAgAXBQI6
 f4GRBQsHCgMEAxUDAgMWAgECF4AACgkQFokZQs3sv5mRMwCffitElKCHTC+tF8hQ
 R9Tdb87+PH4An3jlIX+TAD/u6CjyAZ9fR8nEXeVUtDRNaWNoYWVsIEhlZmZuZXIg
 KEFDTSBzeXNhZG1pbikgPG1oZWZmbmVyQGFjbS52dC5lZHU+iFcEExECABcFAjrF
 NgQFCwcKAwQDFQMCAxYCAQIXgAAKCRAWiRlCzey/mTbAAJsEIOjmXPBxqyrpS0QF
 lrJtDENffQCgmWgC/5AezMfJwtu+s001BNw7oRmIRgQQEQIABgUCOs493QAKCRDC
 pSwr0i8VsWB7AKCZe9euDml2vgJAaaPt34ptUl4UHACg4SZK21iSMmLW+cI6L8iw
 gGvDcPe0Kk1pY2hhZWwgSGVmZm5lciA8bWhlZmZuZXJAbm92YWNveG1haWwuY29t
 PohXBBMRAgAXBQI7RpsRBQsHCgMEAxUDAgMWAgECF4AACgkQFokZQs3sv5m0ogCf
 RV9e/JXy1ixgKCVoqzaIQ3j2MBQAoJwtV25V4gpucQxysqRrWTB65Ja+uQENBDp6
 LqIQBACFcO+vvM6/ItdzUhX3vIihiKENou4FchXwc/u7uchsLs589+PwaYWXqtPH
 E9YSjXYo9y87Sl6ciOagBL6rJZ8oNKc/ylRmx42iSTdAdEKCgK355kmXiWgaAm/W
 CT5YIETaY+D9TrBDD+c+ofB8vhekxAlr30FAnX6VmUJFi5xfrwADBwP+LiUdpsML
 kdJj0Y8PmbB3Gxle3X9w+6hBkoP8Z0q5dzG3Y3mGYpgLd4Ytf1KEKUm68BDJgcvf
 41B2Y6Ptp7mSRAufbymIRihNKH78fleaziWsux2CYJGZvsJzuYrlzgwuTzcLQKL6
 MfRXZHPyt+1SwQeV6pIE0DBZLHg9a0Ak5sqIRgQYEQIABgUCOnouogAKCRAWiRlC
 zey/mfYtAKCVze8DK+0HP1fTQyDajO7o9RTIVACeIwhXBEbRN8cH0BsG/8Qn5sZo
 2Q8=
 =/joR
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.126. Martin Heinen <mheinen@FreeBSD.org>

 pub  1024D/116C5C85 2002-06-17 Martin Heinen <mheinen@freebsd.org>
      Key fingerprint = C898 3FCD EEA0 17ED BEA9  564D E5A6 AFF2 116C 5C85
 uid                            Martin Heinen <martin@sumuk.de>
 sub  1024g/EA67506B 2002-06-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD0NjbIRBACZTF4rK66+y43uXsV8CHSefx5lRHaLPFMNga+sUBRIFcwu9WbS
 KSP/r60Gf/mNK4EUX3/+3gVljrgpAbQL9X9MV/SO50aZM8JMrUkUwjuzzzFKplT7
 bdB2zWhexWemFsE0F1G5NpxkqMg/E0aiZb5P9MVJyGLlF1hCwhWsNG0OewCgzQ/b
 yAEMk03PPk3DOaM4d/Vdf38D/j4O+TJPSjMf58wRGkrT+BmLCvFvg1OsUOMgyQPC
 Y07yO6WmSiZV5ynqb4bS5m3jfQmG1I2wK+dIf8SHyaVgqZiUpfqrsFV2qwfZXcod
 C8a8b/kmEbdMk1j+jZ8qxSScrKCHKqdEs1UihCt/F1kVVd8gqYbWouICxF4GoU4Z
 ANmHA/4xVNIInKVghFk9lMaK9lDgQs02laaTWLWzcSfe28ADds3Jdur0Ox06tgeU
 zdktWQvRYpIjqiQCCFLN18l6Lc5qyTg6fnx2yWpWJMb/xumUz7A79X0TBN8WG71n
 zfJLHtn7fCjsi5009s7Ahu//Q7pGN8FvkrZHZ3xNw+3pAaoawrQfTWFydGluIEhl
 aW5lbiA8bWFydGluQHN1bXVrLmRlPohZBBMRAgAZBQI9DY2yBAsHAwIDFQIDAxYC
 AQIeAQIXgAAKCRDlpq/yEWxchZjRAJ4s0v1VXJmkm7kj3kMM0Z8xMNoJaACgkcMu
 T1ID/2v+A1X7+suOzrWMr5aIRgQTEQIABgUCPZGohAAKCRCteU9X9uLnUzW3AJ9T
 0Hzs6ZZq3HAYuSVkLReaZEhyGQCfb7goCt5RLbxx+3AMyyX5uh1boQmIRgQTEQIA
 BgUCPZGlrAAKCRD5Ay7lt7i0eYdWAKDEeKMbkRTSZKsKelQwiD+T3me3tQCfVMLi
 9mkjolOAXpAOVX3Igy5QHUS0I01hcnRpbiBIZWluZW4gPG1oZWluZW5AZnJlZWJz
 ZC5vcmc+iFwEExECABwFAj/Q6/UCGwMECwcDAgMVAgMDFgIBAh4BAheAAAoJEOWm
 r/IRbFyFjSMAniK+uu6ts+tLchT7+npgPJ0wmyCXAKCmCmXrSUTnPG5DwiVD66h6
 aL2GHbkBDQQ9DY20EAQAh4G77oKy6pQB1+dhbbLsfb3UeRWv7i/w21Y1tSriZ5gm
 HhofJRuczvrhI9V23wRVOKs417TGJzytDIfp/huycYMigAQXikmFBJSqIC2ktJEi
 0DGhhne4XBdJENiHV8rb3/mk+Ffes/88DmoU45fpAwY1YN1jH8WO5mEq2aKCjHcA
 AwUD/jBsaAoUeNO00hwuZuWYNM4nvX57nptObVzP54/TfKs4GmdWzcfI2JB+5eFp
 rjtNCK+tosTQd73VzMWKk0fwiIew+GsB+g/ibK/WJW0lS6fktW2nPG2mGRblLtf4
 8W4ZmtZUqFTBSbmZOcsxQ/LahRosX82NbQyFPwuFMEBqYho5iEYEGBECAAYFAj0N
 jbQACgkQ5aav8hFsXIU0ogCeLnzxBftyPv5iS52Ear+q/mPZL7oAniB0B6mFArQV
 gtLJNL6KejWqSh3V
 =Z84i
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.127. Niels Heinen <niels@FreeBSD.org>

 pub  1024D/5FE39B80 2004-12-06 Niels Heinen <niels.heinen@ubizen.com>
      Key fingerprint = 75D8 4100 CF5B 3280 543F  930C 613E 71AA 5FE3 9B80
 uid                            Niels Heinen <niels@defaced.be>
 uid                            Niels Heinen <niels@heinen.ws>
 uid                            Niels Heinen <niels@FreeBSD.org>
 sub  2048g/057F4DA7 2004-12-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEG0KFcRBACgVFt+tcJtDzCAHLta1UxWlT5ucTeSfsNyhfYRdoz+IBtJ7bE+
 8ydX/y8ZG9Rbb6SCP176Cq/sHj5hDlxp62k/7csOcLvjqPC5dbZG8hgxerygXLE4
 b76zjI5KLOyCDRyqh+DEBO4uuopZ7ACoJMRhCWyfgqJomlGy0Mr/BzfffwCghsiF
 7TsOUyQcV0vlxSXBF5bZ5I0D+gIVZSjLsS8IXUIZiK3dRFvHm4aWrcxwlGKsfJ4J
 wGvOMR5laNHXINUYaoEBdiUaCWW6J5lesluX7/g9+X8t9mvfMmDrVlrJKoc8zlhM
 o29TB4oL5mM7jHjy0Dw8q/n1i1ydWQgu8a3v7giuoYaOKX4N58qWDDGBbd1jOkol
 bnqIA/9+kVIr92q211LsR3GJTFMMs/f6nbDwiyZdpzxE7b2Xu5d175wjX1wqJT9C
 pgS+8p8+Puj+KyVJCGQTw31Cba7W54bOxfbJ62rheh/xVBwfDwdus3XH3WEH9KRm
 pLXRowTqliAzl3CEu+iFqJKqUQ5AYe0PhhcT1Tbf6PHp7iQdTrQmTmllbHMgSGVp
 bmVuIDxuaWVscy5oZWluZW5AdWJpemVuLmNvbT6IYQQTEQIAIQIbAwYLCQgHAwID
 FQIDAxYCAQIeAQIXgAUCQbQ42AIZAQAKCRBhPnGqX+ObgGqSAJ4/ld+x0v6/64Up
 +1IPobpSdvjgzgCeI7Kp4K1Td7QNQG6Afc9nY4WTj+60H05pZWxzIEhlaW5lbiA8
 bmllbHNAZGVmYWNlZC5iZT6IXgQTEQIAHgUCQbQrdgIbAwYLCQgHAwIDFQIDAxYC
 AQIeAQIXgAAKCRBhPnGqX+ObgIDjAJ9iqh9KLsBXEl3T9U4xsLpqKHoPugCfWm4T
 jRLWPt0TEGm+0nmtlG1dP4+0Hk5pZWxzIEhlaW5lbiA8bmllbHNAaGVpbmVuLndz
 PoheBBMRAgAeBQJBtChXAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEGE+capf
 45uAc5kAoIIA2lj2dycq87whxsoWq/vpdb6sAJ4iHMxJ8xN9QiJ+NiFZkNds4+iZ
 uLQgTmllbHMgSGVpbmVuIDxuaWVsc0BGcmVlQlNELm9yZz6IXgQTEQIAHgUCQb1m
 XAIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRBhPnGqX+ObgB8fAJ9xsptfCNqT
 ceHQzE6KvCAGUvTSQgCeMNrLow2tqvi1cbrKyJHNwb8uace5Ag0EQbQoZRAIAMCB
 AJMtUeb1EZKoeHhMiaOoIfQP1u9CAEeLEcv6QhqqY/8qQdoQXLpdfjXkKV5K1DcK
 1nYzBatU3DIHqP0qVD1Sfm8tqV55Y42wKmMlA0nM/ryJrf+9b2kx0p3Uff6PIErU
 6KA9BE8a07j/bJKaA5Qfr2WNlzsV7Pvj7kyx/wCOB1zCPlZGDIlCW0vYrT9rRmz0
 EINBEPqJLYAFBZ3eJ1+0a8lWf1ERhmF2nzz9Kr03nN5NA1iiQj3G6M3VgCMcC7XX
 DgDVycSt7ipFV7+2fUtRxKFJgIwvvkaDKsWb2vpzEcj+D7rAoGEiJmfwBbFDMB81
 N9lBLHbAQ8fl9pdaHiMAAwYH/ReHUkVakaHWhC02VAwYudIcTIwJ8FnZ6afU8av8
 mHSZFoL0ytUguxeJW4009z4TKU/9EfWt9V2HqnUQpff98YI/ysHkWuGLwplIe0N+
 l2TNpIBYoYkyQwjHygqR+PaYG6X7ncICFqJTgbjFDjCPu4v+um8CNoT3dlzqYXIH
 T2AX9zkS7600dRLqE1Zl684atsYQduYWdVPwh9fzER5zjwRk3My61fR7uYGpxwoc
 SxZOQOU17s21G/pgqv/oZAPqLdUfLXQ2ZG+naMfp8xMpsbJpWPF0Fnqklx3VZKM8
 Zx2MStJaqeoPVDjlvAbLPvOioFCUAcIO62N0IcK4yV69YJyISQQYEQIACQUCQbQo
 ZQIbDAAKCRBhPnGqX+ObgBR1AJ4itGc8L05AY6C35TL+ilvXDp1uagCfR9Dxmg2u
 9RkYrA9581ilMd2RCkU=
 =x4MH
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.128. Jaakko Heinonen <jh@FreeBSD.org>

 pub   1024D/53CCB781 2009-10-01 [expires: 2014-09-30]
       Key fingerprint = 3AED A2B6 B63D D771 1AFD  25FA DFDF 5B89 53CC B781
 uid                  Jaakko Heinonen (FreeBSD) <jh@FreeBSD.org>
 sub   4096g/BB97397E 2009-10-01 [expires: 2014-09-30]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBErEzQERBADR7BDREKjIL93LbSG2d9n/wdzYYYwKk41zpPeIWy7CbUgTwDho
 66nNEpHQ+bjRK2cV5f24M0wh82ZQJA/smqaHCAGNpL2/LVZumXRaK0RLLpUZHqXS
 NGs6/4/tBSPMIyLyJPiQC/gWRfevDVHeGKEUyHE7eWqUavuZ6WVnYFhAVwCgj7Iv
 ZewKUicKkfjG1JsIozm82nEEAKA8rJ3awfRLx8dxlOkv8R2UgEGY8OOLpFbr+P4X
 vnkxBp/lhlAFQCFKesO+T5ijE+QNsZHdcIcsfbAlfrUGJnd4IrdhXe1Y3yxYI8m2
 E4kckHIUG80Y5vqSM/oxn195AbWDCKZ7/y838gr1fU3xEt6Np7VeZs7hSqXaur6n
 GVYpA/4uoFquzOTGGTNMQQRlhAB+09kt4BMpX5dAQ4J11v5YE6YTikm9q+U2N5IG
 OZkHOPMSHHlUGjwXQHhEzXuDdUurMwS8YEZzdj2DE6F8S3p3SPCDC5om27mY55/o
 rzT+J2M1kCh11HLxXmOsO0CcAi/6Mzo7smi7+SpFj4MwuQX+frQqSmFha2tvIEhl
 aW5vbmVuIChGcmVlQlNEKSA8amhARnJlZUJTRC5vcmc+iGYEExECACYFAkrEzQEC
 GwMFCQlmAYAGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDf31uJU8y3gXT3AJ9a
 owVGvneYWqJMSeg3EL4ayEMiUACdE3r0oaRkUbDlJYLZ8eVgRINpen+5BA0ESsTN
 ARAQANEvv0rWyXcy/gucz7AZdbGQwjfM+rw2kRDYW2osDtBx9os7DFnzK/AtqJNX
 vW3YPbLGcrQxw4Tm0Ye6V2edkTSWN/jnvbsLiHrsphPSRi2nFU9XYjdKzqvMy5uM
 P6iHlQ4/TNoH/kCrFiMLzRvYkllZ6g3y2LnrVXjSgW+LIX8x63O57k44CGx/OeWP
 nG/eBEccmdRHA5FNYnzVDQxCJG/lrKv/V3L1tYIiKYo9oR7Ma6+5sCPz5udWX8l2
 VRmi6pe2nUA6H8reyuIUu91UfyIUn1CcgRnfhu7kJRYcFeCka3p2aLqP1L9dZ+Qu
 6YMqDsGFXKt1yZwhzUkmwnB+PgOq4Nr8YxJ97Q7ErjSBtaJ8rCHPVscV/Due5ZNB
 x0MoFtdu5t6QkDYeJlJlo+gVu3oIg2N8rlHYvEFL6kboNC3b2eejZR1vMYLajrJC
 hQe8qE00TT3rcnpGUWm6aJS0CTehGZtj4mD4PEvo9lZprC3xY5D/HA1+WIadXt7K
 /I93BDGw+WXlMq/+q1u9kYJiuCqKnFW9zs58v3tYcs2zorpO8Pb5wDmewAMxEQkf
 /4PiRB22RX4ivF5fqAoP1SRpgtqe3HjqDcS51FgRHpt8mIk/3C/WHQcNy3nLjRN9
 JzKzDdzNRv0U8HO0tibhdhiFcR+3Hyv/ncahF2lMx+cUOWszAAMGD/49jCbzC9D2
 Nh/6gOj0arpIE6iQNGZx6AxRvOdU2ibdaLGKLoHNVGqvCXxkPND5ySfnsGvrmzlO
 r5Dbvc7wfJojqqqQl0O4CfoIOl1oG42qilTiw8ClbW63lmRNkpd3XWGiraKo15fG
 RoIR/y9b0wl3zcZqqZswHf890XjDen0Ue04fkiRpad93QsVV4YB96oesSXP55d/5
 r8ZbOgwgEie210iijW4P1OTyv3xQCvxecRVcU4xIplcfHAKXtk3S62BUJq+/w36U
 IkQDhX053iw4V5XHgd0U7/JSaOM6bv+KbOyL3cLq+HURohUbgq3NsriR3ZxAZlBC
 vBchVGJojdZlsBCwjSjdXgcM9GLuf/yR9bu6TAvXyfZV2ad2LQQowtOrEVnteyOl
 Cy57oQ2NPfxZUYohTu6Bqp3GO9Zr9Q7NsFF0oefm26oXOq2+HW3r7xRyWTr1G4ir
 PZtdEUO/aG8d2BrrAtAMy8OkgxZBXDqG3RgcqJ1y8nIUAqNRvcQemGLVBg/R0oeT
 iRpH0s2gvdx9vWnnFk2BuR5b7Qt2kl7s3rfhHqx2Ruc+2kJLqLzq59Twp7G/RmPA
 ZKat/ioGXqOXgVKypaV13fFgdZb/EBfuXe62s+nZ6Cppblq/k1J/Ok0j/RV1MW4J
 jSkn3JVQuBLREdGxuhOzQChVIrAmiror34hPBBgRAgAPBQJKxM0BAhsMBQkJZgGA
 AAoJEN/fW4lTzLeBzc4Aniw1FfFM0wsfY8siG2dk/ZQJbavVAJ0e7JR01Dfum7WB
 T5KpyVoV09QzVQ==
 =YKVk
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.129. Jason Helfman <jgh@FreeBSD.org>

 pub   2048R/4150D3DC 2011-12-18 [expires: 2021-12-15]
       Key fingerprint = 8E0D C457 9A0F C91C 23F3  0454 2059 9A63 4150 D3DC
 uid                  Jason Helfman <jgh@FreeBSD.org>
 sub   2048R/695B1B92 2011-12-18 [expires: 2021-12-15]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE7uUe0BCAC2rJ274YwwpqkG1SvbLlcdJPQqctt3ELAv/3Jhw7LJ1RjMbZs2
 3QNs4oz/Qb0Ge2kj6/NhJ/VpBqDcv0av9mwbZvN4NR+eA78Nj8tKgRYB67Daf8EA
 NtmJJ1sfzMhEceRWjiDK71XBSGSzaUqGG3x2oJBpoWuaRAUEDl7TvjZAOUTw1/1v
 dXZvO5+cFIlBAhbsuiKSQ5IiWzlv9toqO6biicQak8e27pM8XCfj5Vx/xs3OtSbf
 lX6QZCIVW5lBgRihDjfR695w1fBe5nM+9GwifIhIBXA2sjAvsb1j+4te9PIpNo5q
 u/vn/y5Bh0S201zg8gbdAic/XJ+OpN5CptJdABEBAAG0H0phc29uIEhlbGZtYW4g
 PGpnaEBGcmVlQlNELm9yZz6JAT4EEwECACgFAk7uUe0CGwMFCRLMAwAGCwkIBwMC
 BhUIAgkKCwQWAgMBAh4BAheAAAoJECBZmmNBUNPcKtEIALSkfF5Sem7A9X6f2jN3
 u0/sshrmMzM2irUiFvgbXp4F5vbZk58Nb3O35ds3rSZ9AZ1kbrAWvXnbaMH1pyzo
 bnx7HNkibErZ4UmIG8i8b9Vrtllho2iIVaHJlBEAaq3OlCXzkvKeQbR1n83V4jB1
 d+zeMRTzO1ItnxlqZajxDpiHAgopP7covZU456YvnrmI6Xf3ZP0t7gJCotOdYcTO
 EY97pEJQKT8CuA/j/rkSDW8GfUBb+T65L/h2zysQn8pMQfrLO2+wUwYUc0QyGZSs
 9mdnmZs4XQmmQQUIwyzftzEMjM9KJKmJ6qhZ+Apm8UZ8snKy9jH8AWS2O+SaGrgP
 Ryq5AQ0ETu5R7QEIAKpA5Or5loBPXoTa2UWpSI22MHqHlKz8wHDjyWe2yyK13hjs
 VSi31Dx0KZ0K0PMD19OUXzsAb54UQSZZtbKjXdJeiJpzyzh9eVEBy11tl6AC0H4o
 2qWLZFUOMbxaGDvfKWf6xkzIdjiPk+mBUx6AEsDUHX0alACmBgiulMzof9btGgQc
 oYcR63kscoNz2tx7M1pJ6Za50Eaal6DZCYkmp4yHv2xCkZ1cnTH94mN5YwmlWotS
 ysMUy+05qTrL5ZXn+Az1Bewo62n1pkOHWIgiogcTUpibAflZsgI9iFEQbJns3U+C
 kyQh9xiXs6I2CHTFTngG6S2a1NcFGplSxEBVuG8AEQEAAYkBJQQYAQIADwUCTu5R
 7QIbDAUJEswDAAAKCRAgWZpjQVDT3POnB/0XZUzuA8ytqhnzkxY25Kr/Oc8wczM3
 XYs4DpL1TnghePjkjdEKhbC+1qDyg1kSQmf7L/uGV7n1pLFLBLwv72lYnaAMmbOk
 Xidc1LhB4YMrxc6tyFfER+ypw26FqfuvNk3QAGdqWvFQqq8dSyvA8KKDaP3ehKha
 /pmEJOC80jqIp5Ofa7J2QMPJ/kfegsjAMbQEqgcBmt8Rb7xM7NrFkPDcWRoB75Ca
 xoRV2eiDxMmNoTPDnjGyycndaaOgoAhXwpoAnmxIVVHs26qOxOyoq9ZYhVgx9o/S
 dAHXDxMry5RLmXQj4uDPTrUvGpxcEbOzVPBWrmoqDJe5Ll0rwaQ/DXZG
 =hr4n
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.130. Guy Helmer <ghelmer@FreeBSD.org>

 pub   2048R/8F1CEBC4 2012-05-22
       Key fingerprint = 483E 9E6C C644 2520 C9FE  4E87 9989 CCAF 8F1C EBC4
 uid                  Guy Helmer <guy.helmer@palisadesystems.com>
 uid                  Guy Helmer <guy.helmer@gmail.com>
 uid                  Guy Helmer <ghelmer@freebsd.org>
 sub   2048R/2073E3F8 2012-05-22

 pub  1024R/35F4ED2D 1997-01-26 Guy G. Helmer <ghelmer@freebsd.org>
      Key fingerprint = A2 59 4B 92 02 5B 9E B1  B9 4E 2E 03 29 D5 DC 3A
 uid                            Guy G. Helmer <ghelmer@cs.iastate.edu>
 uid                            Guy G. Helmer <ghelmer@palisadesys.com>

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Comment: GPGTools - http://gpgtools.org

 mQENBE+7tGoBCAC7+hE4BIgc5qCn78MQ4cCtCC+hHhIx1FGuJwnchrD7SprF9oPG
 YYUGIlxq5xdS+SIhCPWlRCZh6iyOgnnRI31Lc0ZwU61iietn0zaT6foJiOmSwmeZ
 chNSeVY1jd2D8Kfj5H2mcLsL3ViBtPG2SW6ru3cWbH86fcYSSFQzOX29MoaPkV1u
 WNh8nzT4ztbzEz9RHZni6z2bPxMEwkDkU4H113XUK9VOxN/+XeUSVQcX1EPxqqYu
 xBlzRKbQ9WdsMMxp5S38NoQQlg36n0pISIFVfUdO/m9HX8fhkzYtfcdb12NvBZpZ
 /TQk3B5t1x/i1BR63RBPFmddqHcFyrT6m3YxABEBAAG0IUd1eSBIZWxtZXIgPGd1
 eS5oZWxtZXJAZ21haWwuY29tPokBOQQTAQIAIwUCT7vZWgIbAwcLCQgHAwIBBhUI
 AgkKCwQWAgMBAh4BAheAAAoJEJmJzK+PHOvENL8H/10XQDIj6H9c2twS+F2LejHD
 /ucyN1WjN/dMTH4W3adzqtPSlCnLFvzIFY9udxkHQiDY5l07WLAbPr60pR0h2f6A
 bO298TtX7j/7ciNzhMyyakucla0S3y4JMiVg6vpPb+eo3z2RcgDSyLRY7DV8CHHn
 EzBFbtaCtNbULprtdXlN7y4T59wiYyixXKAS5J31iOfDh9YVkaQBfmT6grmVhunf
 FyIpPo3jjiHY6JR81mtX1/P05X4oUpgVJF+2nj5f5VKmBNmulJk9w8XlA76Ct6gM
 ZiFF02gBmi4xe5QnrOZZewH2zwMsPAA1Ltvm3lmO5HLQwLaLU9vadkCFwuoz30G0
 IEd1eSBIZWxtZXIgPGdoZWxtZXJAZnJlZWJzZC5vcmc+iQE5BBMBAgAjBQJPu9k5
 AhsDBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQmYnMr48c68RvCAf9FANU
 RoGTxm+K7VZZf/zZuiSuNtzDV+cVfRvTLIjlO+qU3z45iCTzl6ldrZbhATQz4U22
 KyBlURCuPbZikec8XcKZo5j6NPe6g9bR22dgqhx0btwGZPeiMf7c3lHvuq2nQO1d
 GAz8ZWwgrOKfZTqRQLhE+CJZyblX3u9PMwel39l4wXXkOaJ8ln0IqXMy0KL2YwIC
 B+55ocoNFRDjoyv1mNTLRaTL1PzC1cLilmXiiT3ws3FBchb0rP80+mFRU4+4gt5X
 0FrJVN3ALsnLC1NWQkAK6XGNBCaklM/feTPaEsv2GuttGvlBuaI1lTn01/B2aJlR
 BA8QioJmHYg6MzygVbQrR3V5IEhlbG1lciA8Z3V5LmhlbG1lckBwYWxpc2FkZXN5
 c3RlbXMuY29tPokBOwQTAQIAJQIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AF
 Ak+8DFwCGQEACgkQmYnMr48c68QClgf/faCi2pId3tPhXNFsly7n+eWFJ3TOaLSi
 7Y6mQMIFlO5Q6R582xJj9szQR2BuUFeV/TzJNJz0X7UbsgvHrAfDlxByp4R3RL5A
 Av952UlQe4CTEIAcYB4714iSdbIM5WGtKog6jYale+ZUT4zgit8vhMHmjcw7Dviv
 OYFRxOKZ3bV3NCXZdkLFyLRUQUEooaUNb3tBbl9SOd2mY2NVMxXhXA8NQxRpNkWz
 WXQpISbfFI8oXkRVPl5z6oLaJE1D+TTrV9juo5j4qY47yXr0FPItd+wQ0QhxwuH+
 goHdJFlZ2R03tcnfg+JtXCslKYAHk/mKJXwFCVLc7l+NjTud6y4PVrkBDQRPu7Rq
 AQgAwcKaIzsFOXe5xRo8RxUpTVXUnEish6KCcaQL+U4Hat3Satg/Pk+8BRI2CgJL
 7GFgmSYcoRtDRYrPkv2I4yNJIVHW5CvAktUCw8IEOdav05bO7Y8QUI2RkQOyDXOa
 JXoUk5VTrJOjV/J7SrY3dJ1AaCDsOtRQf8ZKaU/rW6CzZE+biFXctktWhCzm8wje
 uyjA0Qw+AZ6htOo24RqaFrK0DwTu9wtMP3m5M25MimiA/pXQ2ogJlNVHOywKhlYl
 tEEeMwm67IFgwIzr7fmbO4V2CJulS0JKVvJFQfC+eE9oTjJN65GP93hfUARTeeL5
 R8a7uQ7wcPKfRIm8xpEilip0+QARAQABiQEfBBgBAgAJBQJPu7RqAhsMAAoJEJmJ
 zK+PHOvE83oH/0xBhkMPYCw0Hz5xbBSnh0F0nM8EmrtjJaKaCnBCSDOEX7FoWjnw
 fsC4eNrCtv9pnk+7c5IbXxUO8bxeNmhL5WEwt2YteYgrq4oTzTtP5V7XufXXq4oX
 MEfU0sy11OTMz5nHxoV/NMlMKCdQQEy4jIXV8yrB+2BpU90u60Tkis5LL/jvuQi4
 24QTk9VhOEKwhHbrW5+iOSs/KBUdSEO8TqjjiNvpkNR6AST2swjsUSoqKtIOcnYL
 OaMgiZygedIDrWXmZ0cRH1ehSp7tx4CIuEeF3JJyAhOzyYgm6o9l4zh97ZehMDaN
 LHJVsBw1wu7qPsG6jx0IC/eMXZKIPSk/c+s=
 =p7q+
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.131. Maxime Henrion <mux@FreeBSD.org>

 pub  1024D/881D4806 2003-01-09 Maxime Henrion <mux@FreeBSD.org>
      Key fingerprint = 81F1 BE2D 12F1 184A 77E4  ACD0 5563 7614 881D 4806
 sub  2048g/D0B510C0 2003-01-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.1 (FreeBSD)

 mQGiBD4dlrYRBADhXves+DDbhv8dD1LyC7e+RIASp8rEN0mJDVarhEy45KxRZcD2
 hE9dLXZU/5hcdK7yfatneg5xGFiedFJ+u/HcsMkxeb60+RUcF6Ec5L8PJmCwIQl3
 3xP7UmC203YufvyidQSayOk4LDyg5WVGEXiN5KuShJC+feAwvtAao5eHnwCg5CmE
 y6rO8Bh/K2MQxP8CXCoLG80EAINd8twMsRIIqAxtVWeG0yudtgYdvhpbGrNKoq2b
 cxmfunLAQmHim1jL5run1St3ZACyuP4brckPiBAOxVoRcIMOGPk04Lw3blKQ7u02
 6aOKKlGvW2pF5/Wh6v/q7gzAucn1HJYcGK7Xc8IvfdIZJl/tTeCo0/smxND4EWhU
 C94zA/0bvNhgntEwLF8x6UJnZXfQ8/LGl/NkSTyTMA1QqRrrik1oN4mYOAHE05Y4
 Oija6MSgD8YDRcrxxr8Dwh4pqS/+FlEsV5y4A4OoYbPW5L6FAbEpKO86jbE3FK20
 lX9Li5+woBWaTuLRcU2Tk69WLeOTdOrs+f50S1xWB4DJKBjmu7QgTWF4aW1lIEhl
 bnJpb24gPG11eEBGcmVlQlNELm9yZz6IWQQTEQIAGQUCPh2WtgQLBwMCAxUCAwMW
 AgECHgECF4AACgkQVWN2FIgdSAaZtQCcDxSj1KNFQXWXPl+U27Sl2/IbKEgAoNDq
 Yn86zUh4NPJZJb3P174CFRK0uQINBD4dlxYQCADaMWMhYNWemjrdioJoZU3vYkup
 IcQg422OZoxWYcUz6zKVHZuPdXSAFO+Edrt8QwvYrjhSiOSF9NNnFgNGMBGmqOg9
 Kfk5rIKnENNQP8H8CZtzlDjJXVoMAeTfaeV9+ztHwWKk6XagjLApl9Fx42Quu4Po
 JdvJNHhq5Bf299jecRsWmSo7DtpNnzGC2HFWRkGdkkNmpK7hFe9m3YsFuP3nCFps
 RXCFMx9t2Bneh1eM+NqogjON+vyZzOUB32WY+x9Kz6Xf29auU1PSNYz+1LC7JAYk
 f4CrFA6wexQHKe/nXwlik3/JeFSPAsp/VsmvaHOenZTOfmtBT4ruOwqn8DGzAAMF
 B/4tHAo7/sAMgvkz0qHAxV1DjOjB5AQSs4phksYWYN1uaJq2//oD/jjifmmkhAq0
 JLEeKDquvuNot9dtJ/75DF/XNa0Upt4Hq509Wm4o5NBN/CxRzMn6oU+K86S6RF1x
 JidNNI+CsTfdkNnCn0x6OjRsG0j+CUbwRrs4CJ/7ZWkuMCclLBKoI+rAwd5YM4eI
 noSrSZ4/2Uct7CyVm2aGIh5ofR75L7k92qZ/D5hN0wwKrL42bO8gJqPGPgsCtr9m
 OcT2DtOxkS9ir2QRyD7SelKM4pmSbxvk8S/IzrNS7dvKiO0xQXsvf+sG9rZOJ2vF
 i3in0uB9SeXAzsqNCqtEkSbeiEYEGBECAAYFAj4dlxYACgkQVWN2FIgdSAadQACg
 z3dGbsy32PBhRn/t1lXp1120VrAAn04hxsFX0HEKt6sqAcpIuzdTVrEM
 =8gWX
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.132. Wen Heping <wen@FreeBSD.org>

 pub   2048R/A03F07DA 2012-12-10
       Key fingerprint = 0258 F2C7 C123 E627 9E14  B4BA 270F 30AA A03F 07DA
 uid                  Wen Heping (wen) <wen@FreeBSD.org>
 sub   2048R/CFC8D6A9 2012-12-10

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFDFsuEBCACSJ//UOaDvnQbfeQIiQsRcg1fc2GlcyKnJxTv8H4N0NVw4c579
 D/zEPhRIQTcwrEL677xdeNWtxvYkQeePdrvu4OhXW6IfrZp5H8tedMNqh34MxykE
 J3EC7HmH8J85ondMFSsg8OtBolpDB7KLMJBuIbQ0GDXniijcp9muVVbiRCZ7vhqC
 1J8BJKZDGALD7GLttTfkK56xvp2H69aodYBeNsJcUxAj09gYW5rBLId8NgyPwQhR
 vR7C+VQgz1vlVT/YTvzMX6ZigbaH2nCJTgC1/LK1HJT9hkJIeUNskZwcAOoBA2L1
 DXhgTdkxFKVOb8F0d6wvYSdeVfAWZc8xzWVdABEBAAG0IldlbiBIZXBpbmcgKHdl
 bikgPHdlbkBGcmVlQlNELm9yZz6JATgEEwECACIFAlDFsuECGwMGCwkIBwMCBhUI
 AgkKCwQWAgMBAh4BAheAAAoJECcPMKqgPwfafzkH+wWio4GRrgvK8K5DoIkGgmk4
 bVdXd6g9T+sVGw7F5HTkCbiW83BAmTb49a8uDI4qRSDIEPLOSBbbSlzYcBqHZ9gf
 1/G2JaL6UzlMhdoUZUS3biIoGKFDGXrKBmFoSvMN3MKNnAajAP1rTyzk2bC5EhNV
 CsGL+KOC/JXBfHZ/wxXTgk++Wvm8bcZDXmYMptWsRaHMZKbkdakX9dmPtHmv1g7N
 3AIPSLrrjYDdWfejK8KvPKQuHnq0A9tLS4NOnSY8Ls1Wg3WfE1qvYZ2oEziVrMEu
 GIAxDQfFAN31GR81lDFW9FybAPqeuakD/cUuuyJ+15hUYb4fcmk7RHbxQrTcfHm5
 AQ0EUMWy4QEIANmhcffZZcinDeNMTFba+m4hSV28diXeGyoXfeRWkdk3+fOGywNl
 +/HfYrXXSoDcfkmooUljMvGCj+vupP4obXeOY4MrcnzUYnUWjpfY6mQXejXGgAQy
 x2lcNF6W/g8jl80nnz+hfTEncg0xzNwFDE9ZzR7+G5x6uub0Xl30Rsc+3z6eabFS
 AQ5fFw1lEvt6Y8CGXCx86CPB6SQIJ0FddoHPL2LElSiuenaS7AKnnau9XqxwouD6
 MdFqDQJ601lZBhEWmIlWRBj9YAEwwgnvK6/OFCHcIRjFl6beQVFO2xyk35SZOq4I
 HL7GPs0+bg5D+f7a3ugzqt876LlMVuUQmEkAEQEAAYkBHwQYAQIACQUCUMWy4QIb
 DAAKCRAnDzCqoD8H2v+UB/9mpvePA5lZrFne+s/PyTZu0rI7+Mj67Yj3DywxVf3j
 pqzjeRlZgVoZ0HbVry+2wUk1IN2eWMJy1PECTAyK5tybdtl8ckNvGhrMi9ilF6gk
 WIn9wXRiduuCZ0hj+STtlsdGBCThz9JqMVr093uqHqe+kB6TSu6/uVMZ3LhyMEeQ
 oUkoDMlG3wMMKpD/mzLeJTTycXSZ9VzDmQMOOZAC7UypLri9ykjRAVc8J5c+1RA+
 +dsNw0DTEtGxHsObfdTlrCP0vohTxOdGjWuXHKYTttrM5koc7M2eM4WSEXkpIKb7
 g7S0ogl+qD7RokD6CChkH7fnFesT2ksU8KvE/0a+/8Un
 =7kGj
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.133. Dennis Herrmann <dhn@FreeBSD.org>

 pub   4096R/F7CDCAA1 2012-08-26
       Key fingerprint = 0587 E730 68A6 2646 A991  505D CD9B 3A87 F7CD CAA1
 uid                  Dennis 'dhn' Herrmann (Everybody wants to go to heaven, but nobody wants to die) <dhn@FreeBSD.org>
 sub   4096R/0A6D554F 2012-08-26

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBFA53CUBEACp73aYyWCTkvQVk+4cCoXBZfG3OcYU/dEl0LEexPY5DdrVJjyj
 KwXU1L6zatwdwptTN3c4IQK3xsM6QfqinpkJAuaYg4/ry/Cl1EkZRRDt/ZJdv/o8
 I/g3HNCHIit+VZBO+EscDcNVvsjfZIiH9ES1vdmeIpsaBtoMM26YDeOxZKKKWrV7
 CnsUskXp6LWF8rtVlhF/UVbjI+r2qiK61jGp9Em+aiCYBubT5EmacyfeH194F8Ic
 7n1neSFGf+AmS0p/PaHM/R2ANeX2sZeDT89LDSxdTdV6IiBRzWah5V9fxnxuRKTY
 Xca04i7MNNNUg+pUCzl+ewSUq4CKVatFrk6oaa4nD50DTDmicBNGUhlptYxxICi3
 zqkiNO5NpJID7XW/lnVUr5Eenteu7m476mvJTJcendeT6oIMMDmokS1yXMoFo1o0
 RrfKO2ExM9rFye85bPFtyrl2LPulCXUvoWoIYVmSL6Smcy9hdVP4SPiiZnz7PzEE
 msb8tJekHoDpiWiCaFe9xR4dWjhRiQKCD/EuRD/vRSCzK3Hpjv+pwBYed4oL3iJa
 PMwAbIAMN4JMtqQMNTUO7zT2JuV4nkl6GMHRl8fWrjTInq7I6Rmj1HKeqg/kCc/K
 wHxaYg+iSETQ1hAyG4wMhHGa0KCHuBDDdG4dAf2oPCA/sC97Thg7qJk+EwARAQAB
 tGJEZW5uaXMgJ2RobicgSGVycm1hbm4gKEV2ZXJ5Ym9keSB3YW50cyB0byBnbyB0
 byBoZWF2ZW4sIGJ1dCBub2JvZHkgd2FudHMgdG8gZGllKSA8ZGhuQEZyZWVCU0Qu
 b3JnPokCOAQTAQIAIgUCUDncJQIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AA
 CgkQzZs6h/fNyqHEphAAlQvd1p8FTQFlaNKBWhV8kPGXWa6H9XCp/lXTmyyRz6QT
 rPQSSwyxoqyp4K7jZryXvugLfqMeVCEmGGbQwInnjX5osTbuLCgu5Vjc5+kUkWFC
 CWmzEXxXsDBCIVvWFunWwFbbqVbcRc8XCxuLCGbfFg8eh7K3fGEqRkAiEvGOfewj
 eAJ/+ZdVnnVFIqq1Hp4NvaBVDuJMM/QmVZwYxo6ab4a4QDG9UgRsFbgZYrqCANZ1
 NxvmtvLqH3aKjWHRscqelZpdBX0RET2PoYtSj4rqAeDcOReWaAqYyq99WNKmI8W4
 H9KBZErSCCwwRy0fhwg1oy1THRKj/tfXxqJ2NMmmwTqoquj0QwL/ySPwd9ltvn0s
 5L77xlDiZAaqdPp0kMy/prKarPwn1ip/Bdh7KuaygOppW7LgAAs3ufoh/7cOkLUI
 x3tPofVQXCa9GmSwiePDzquzG6iOTBLMdfGbt2VM5dFgSrH9/US70PcXil6jMKkZ
 mpW0fn+aG1m0hjajgSkYk9YPKRSRpHtrdNDvPjHLDN9U9qw1W23rn/FbCnQSrLwN
 U2nbroPxHW+tXvJCtoT6YgEsjKMK9kbLqe9vGBvdsBJLWD850xmCMGmWIs7TN/nf
 JWD3Z4Wdd50KKEm7mgYfNVO4Nnmf0Sh4VwY9Bleq0uL7Ess8qxEgHH54YU5/HXa5
 Ag0EUDncJQEQAMlNtCRF68IFM58ZS72JLBJGlWIfD3lyKYL4rvPnMmMStF661lJc
 gx9MoQzxiTIxWEIJkHZPYJ5bNlO4fMumBZwjXAktq6akhNBg2Yh3On6oMAFF7rCp
 5kGPABbHAOLqrBiHCkiXwr1Ipi9ShnVLypqxqBoB9MNQT8DCNYXKbnO5Ggc0nTHE
 WllC05oJdWcyDHlsidDG9Prvcb5LKsE40soOEkNapvSlNOdI/CmGwM1721TpJ+0k
 hNSk1howZk3P+WOZdlWmm6LKkm043sd2jx/3OXbFsSdLh/EZ3X5R/XFTmowYXe2u
 4pntc5OYsNe/LIHDgDOEXjnJr2qfxn05PFo+Q/sp+dA+oZmwq+4d/ntnzz3QA3Ku
 FHWJhyQiaeRqbB54kWozjuKCuyD1iSTXlWWQWw4Bu1gIGvCWMP8X0s1/XKP7wBhX
 JIMiIzFc8Q9k3QRW5X/xufIvcUnnBDanb2sPajEFKYF4rS8n/gomMtveL5IKmmPq
 Tl25vcFJLUd30xWlYPV0frUJj8dXBc+3/DwPa4Nslt/RtP7EXF/FIBaL8dLrD192
 XRvwq1yYkDTs6vKZBX62gA82C0iYJyAJ0DhpNdM0Qky8Xu/VxZE20ngJu4NZaYBF
 lhsRyXb14iflN2Y0+CGtB7fOTK6VNyXmWXTabhhBglxap38p6javFO2ZABEBAAGJ
 Ah8EGAECAAkFAlA53CUCGwwACgkQzZs6h/fNyqH5sA//UL0ta6a+rDINTE/3FyG0
 u//mtChlq8enJJABM7qWhOP7NFipKlEeVQLFJyywXCKRzy01lt9mB9m+FrDyYOO1
 LbM/VXNFvsysKv80AgyhPfpUfQWvGXL/DAXLChLzABB1Mr8jrw69Mx3zDUSA/3xg
 gGoF/MBt+ozMW8YNy5RUfp7X/ogpryk5gtvuRtbbmBmSfD/jF0vQnRLyq09XFEvn
 YhdR7dLlZ+duvjvrHfLh1fu8GP/YD1fuOUASdEiFiiaF250u9vN1qtorgj1f5J1N
 cG3L/FBZ1w6+sUfwU+0JtsPPW1n4OpQVEzNhLNmGU7LpQjQPB1JMNlh2Kq59CHkr
 FKfe/m6+AJ3i1ixgWLfs1SUOFSRY4rWewrTIXl8JQHPobxjdebYZUEdcfuAJeLsZ
 GmJNTnuHGyMMGGPRABFbO6PXcSryrWZ02kM2LpPJ/dqhA/szmFoTKePyPzuQu7Ri
 eUVgEDhU9bj+UQNV7DyR2OwweLvNHvlICPZtkwK8s4n44CpLfnLyN9RmZKkLrhA0
 WIc0ZWH6xEvwnwqVzseAg1W6uyx3nZl2KED4wmTwadUIHgmPmH9m5gy2xXAulOeJ
 f0NoRDGFLUk9tMQ0ivF+fSwy2k5v0d24MT77JDjUetkEMRZtAD1q4ESHCVHoGMU6
 0JTFuwbvNUiIKGhuHbBvP3I=
 =EizD
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.134. Justin Hibbits <jhibbits@FreeBSD.org>

 pub   2048R/37BE2DB9 2011-12-01
       Key fingerprint = 8A12 7064 4F3D 339A 191D  AD52 30C7 858E 37BE 2DB9
 uid                  Justin Hibbits <chmeeedalf@gmail.com>
 uid                  Justin Hibbits <jhibbits@freebsd.org>
 uid                  Justin Hibbits <jrh29@alumni.cwru.edu>
 sub   2048R/A8DA156F 2011-12-01

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE7X15QBCADiNw8zUVjBDrQ8p58bL9PmPXcoDXVeHBkKg6gG4/TQMFFoDczH
 SAUjauRVV39w2cmnn1D2xtc/7r3CCewNxvXy872zOXxmF+hDWKn04m1Qz+P09MeZ
 8VhgOj8lsoaGLyxHxWKtwRJxOPvMYnO42AVrBL1fxRpGvGciWpROWx8D0O203Ozk
 rS1Ten2lvyuH92zo/PSEqSihUv01lAMeIxBmTv2GhGkIU3j/00Liz5Q4q37pvsx0
 ZOQ0jS7ptbM1O2PGg0/zfeBtTnQtn4C+9hAdfP1WAZE3nV5d77qWbmuxaRGNz37n
 5D/NAqFBvvTEKa91bwhQtRpzWdOZYDr4RJVJABEBAAG0JUp1c3RpbiBIaWJiaXRz
 IDxqaGliYml0c0BmcmVlYnNkLm9yZz6JATgEEwECACIFAk7X15QCGwMGCwkIBwMC
 BhUIAgkKCwQWAgMBAh4BAheAAAoJEDDHhY43vi25TJAIAMmmE6o++muwuGy7oOeq
 UfMg8uG3KAym6pRash1h23yInLAv9aeZDMnXl/te3BW57Yb0tpVnqZ5l0RDcL6bz
 /WtHTrM9lXps2Pw/FYaLArU6+VJ1p0xJlE1w3w2J/LHXVNmeeCcowbmZiSuFtvQk
 sqh5qy8kab4jiKDFsXBX5XXfdqPvfaNRIs/LbPo93UlPaM0yyKyMqq5d3Fj+6NO6
 3Ak2ez7cXls7XQutaqBZ4JnvKY1wfo+8NnmD/AQa38udQA2rDaBjeQRIfFAwUGpX
 M7vzilLuX+IY7R9JtvNFk99X4CmKqQjvH7XeIfw/pbAF1fUAk8iA0VIPhzbcMaC6
 Ikq0Jkp1c3RpbiBIaWJiaXRzIDxqcmgyOUBhbHVtbmkuY3dydS5lZHU+iQE4BBMB
 AgAiBQJO1+3KAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRAwx4WON74t
 uTpECACcO4uA7fdp+VrqJarsHUB9o8Y+T3ay6zY3Q+OtkYtQ5fB0C8J+WlE2piLZ
 boNtCG6LKlvXSvS0nMHERXFq/7M6ScZNq8IwByMwnQHn8woyvkXlqMvjfdjIvqYi
 dy89GA0BCy20gZxeOWhKpo0epmCegR6+KyU1/PS3Kfrm/C2bG+Ig3uNJ4wyUL4hF
 i42X/CF52BFmJFO66DIMCkahB0ell+7fEB0JSDx3RZhW0zql1Ldv4gWAmLcNUSCR
 3a+z7pwcu7oGTkiK8OmD4IHj2x7D7L/r2j+ElCW3iG2TLH7tAeMq9Se/RwOGbVBX
 0/bRHGIoWXRI95cNext1gqZHX2TjtCVKdXN0aW4gSGliYml0cyA8Y2htZWVlZGFs
 ZkBnbWFpbC5jb20+iQE4BBMBAgAiBQJO1+3fAhsDBgsJCAcDAgYVCAIJCgsEFgID
 AQIeAQIXgAAKCRAwx4WON74tuWpWB/4sZlHQzbbxgLlsKYWxQzkIzRyC9M25rjVu
 V4iLZfRaRo3axVzE8/51S0sp2u0QTLcS6UGIEHP5XGSs8zoVBjnp7jN7gYDlHV01
 d27Lhins3+4VQy7Mn91o8yym9Q0NFPSbxjuK95MWz36rcwv00jl+9M1cM5ViH+bX
 Nnvkusjh38JY4CxWau+C2mf9ZFluApk5UtE8m6nd8BKHBDrXSSMHMonsb5RUOnOW
 EJHAAMmu92gc3QXbixg17Kde1hWrKy0kl3bNh/Jk905+AYMcm3N9AAVOKKlbtiGd
 7+VqcnIRP60un13zBzy+cn2HBh+8VLRMxUOKt7/soy7fa3K+EcVxuQENBE7X15QB
 CACddKAhd8RiNDW7/F1uPTiRuASsxnNuKyt9NKh+BPKuIyrcQN0ft1PhdCvI44Bi
 crDKvZFLQN8twsE+ld7S9eCl7Y3rVEGbUZ7otGHEdgNfYR607dgzIyT/Jba0tB97
 3xgWrXOfu1utM0bSq8XWBHBUAG3tHMKp7v3nI+Hp8NSbPtnZ846IhhByz380CHEl
 k/xle22jjRwgLX/bl2usLzD7+F85jzzx70Mcv1oACD8g3o3QSZwuSPVw2Bs5l8VF
 2l3lFfZD8FlM+R313rbaCE0YcMjPbzxfmk82Bd6V6QtVZdqwAFbav40KVBDEF1lc
 bJitNJ2mSiFiA3YqOuwBf4xVABEBAAGJAR8EGAECAAkFAk7X15QCGwwACgkQMMeF
 jje+LbmNJwf+NlcIyBXWGptJJ35Mj0ZRLroFBk7j109YohA210PXmOZIrAQkoaSO
 HyR/hXosaEOLCoqQh6DKIcfRZPjLgdS9rKtzWzIEHoW+vyFKmJANXLcbDXQlTdth
 KfPhAXBQOKp5gCOTHJsSb5kL60c5g6eNE0gU108GmbSrOc1wQoLHArQmoE/HEYla
 vCYJlXoAEp4cisE9FHuol5WD9+iPMufJQa0nVuConSFt4RpGmLyBPEictlRv/pxZ
 s2FlOFtcv8Ozr1qt0guXQLPmDXPs/B0gpYh5URqqB3NsGXeJRMbprQOytOXwE53B
 XLo7QbjbR21i/BQSm+3OeFiS0o/BNee3bw==
 =bC0X
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.135. Peter Holm <pho@FreeBSD.org>

 pub   1024D/CF244E81 2008-11-17
       Key fingerprint = BE9B 32D8 89F1 F285 00E4  E4C5 EF3F B4B5 CF24 4E81
 uid                  Peter Holm <pho@FreeBSD.org>
 sub   2048g/E20A409F 2008-11-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEkh8ugRBAC6djNybj/k+sW8z4TZeC9M1PuSSuJlmCxF/h35rN1bJMHiaVaz
 umG5AjNwYtKilXO+bpj3OUQDz86j/vMpETy44lOaxr5f65lkP/tXATjVpSkxuimp
 vUHi6wRaCHLbyMGHRfuOX1E1yrYm6E3UvjrNnl8bhOJ9paUkk3El+gKm/wCgtIS4
 07Fb+Mft+7a9Ti8cUKP4rSEEALh/nGAsKInUmw3ybZ4c68yVjOUOhbDgAjU8zwb7
 vVzVpCythAEailx0l5UDzVSD8oszLiSDFLf93rfS7AyWx2/C/6kayLH7nYnmHmI6
 Evv/uZ/o4Tw8l2BmqEMwMIBRi37et9tTJNEKMAAUaah81KRcE9CPp91f3oKutOAq
 BkG6A/9e2II1FvJRLzeGRB4FuNm4yqnRvA+LCPE24qEWGoVu55KvSsrb/kQEUxHh
 46K6d1UCWYIlAPhV/CGstv2CfW4zDXOBlDg8kdQz9VFlzyz8sSs6ZP6b7kUzrSRp
 tq6mgiLKaTFYtm/BaUgYXpSI2uTlgujhC2v40pzeKN65Ph2H8bQcUGV0ZXIgSG9s
 bSA8cGhvQEZyZWVCU0Qub3JnPohgBBMRAgAgBQJJIfLoAhsDBgsJCAcDAgQVAggD
 BBYCAwECHgECF4AACgkQ7z+0tc8kToFTVgCfU8q5hy5tJ9ZEs9ScXPuIZ/vA4XkA
 njuLqq+giT5SvrrckuA8I1iFgsezuQINBEkh8ugQCADzK4XaJN07zeKtivb4sass
 fejhXyMJ5kwNqK+DRqMcHkbh6PCKpoOo7xjnk7e1MdTp2UeGifzTUEXz9iPdLFoW
 0O2iCppIgUEVfeShzOqEtiP0qpdDmc9RHbA17R8V8jaNWxmJtbI3Oid/7ubVPBfv
 KkPlsyut4A0yXBSxhqpLnaDpDVfMuUFbdMK+aYLABZMQaj6SJOf8bsHrBL6/j05T
 A0ZJkwPrV+ATbCXLUCAQ8q9rza292OFdLq5/iOQQa8mXhR+egd+NP1GLDEze/kx7
 5gNQJLnfS5GUBJMSIzLIC5Nn+WPzdmK5tMT/NLhzRbtqmWoAfQcW/kcEAUlNbGJP
 AAMFCADe1t3CP+Utgy0QAmqkipgKwvs32CsRgye2ocxtrN8GRaunFSutyESBNCHP
 VH/jh2rTZ6KjVvgBcruaT8B83YtYgOnFpe+4FZr7iwlSVL1CcEwWRDD+oujebAUL
 MaLTcToWbggvbUbOtu+VNKooDYFbFoZvUs9I/49RRdcLfC7dxOfl0+51WTUTB4g+
 d/rxtExYkvh19QEWsj6lyR6icwRhtrn2S+0oZ0JQ/mjCoqdrGNiiGPXzKrUnpSK1
 b1hrtZ3E5BoWJuXu4Y4hHHzoxGW3ggVeTp/+X2K0DfKu0itGJML98oe1hXbbDaht
 O+s3+Nrro2j0Hx3JiQB1wB9merWsiEkEGBECAAkFAkkh8ugCGwwACgkQ7z+0tc8k
 ToElPACgjLamE6WKd9zLyyoyZcV2H55qlZAAnitC7OHmghbHiw+LuQZ5Je7M6sik
 =KODn
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.136. Michael L. Hostbaek <mich@FreeBSD.org>

 pub  1024D/0F55F6BE 2001-08-07 Michael L. Hostbaek <mich@freebsdcluster.org>
      Key fingerprint = 4D62 9396 B19F 38D3 5C99  1663 7B0A 5212 0F55 F6BE
 uid                            Michael L. Hostbaek <mich@freebsdcluster.dk>
 uid                            Michael L. Hostbaek <mich@icommerce-france.com>
 uid                            Micahel L. Hostbaek <mich@freebsd.dk>
 uid                            Michael L. Hostbaek <mich@the-lab.org>
 uid                            Michael L. Hostbaek <mich@freebsd.org>
 sub  1024g/8BE4E30F 2001-08-07

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 10296 characters]
 nQO5zgCfXsb8wtA8I0ngWwOQxrnRRE7+Smw=
 =j3Mm
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.137. Po-Chuan Hsieh <sunpoet@FreeBSD.org>

 pub   4096R/CC57E36B 2010-09-21
       Key fingerprint = 8AD8 68F2 7D2B 0A10 7E9B  8CC0 DC44 247E CC57 E36B
 uid                  Po-Chuan Hsieh (FreeBSD) <sunpoet@FreeBSD.org>
 uid                  Po-Chuan Hsieh (sunpoet) <sunpoet@sunpoet.net>
 sub   4096R/ADE9E203 2010-09-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 5478 characters]
 KQ==
 =zTaI
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.138. ^3\YENssCURaa <lwhsu@FreeBSD.org>

 pub   1024D/2897B228 2005-01-16
       Key fingerprint = B6F7 170A 6DC6 5D1A BD4B  D86A 416B 0E39 2897 B228
 uid                  Li-wen Hsu <lwhsu@lwhsu.org>
 uid                  Li-wen Hsu <lwhsu@lwhsu.ckefgisc.org>
 uid                  Li-wen Hsu <lwhsu@lwhsu.csie.net>
 uid                  Li-wen Hsu <lwhsu@ckefgisc.org>
 uid                  Li-wen Hsu <lwhsu@csie.nctu.edu.tw>
 uid                  Li-wen Hsu <lwhsu@ccca.nctu.edu.tw>
 uid                  Li-wen Hsu <lwhsu@iis.sinica.edu.tw>
 uid                  Li-wen Hsu <lwhsu@cs.nctu.edu.tw>
 uid                  Li-Wen Hsu <lwhsu@FreeBSD.org>
 sub   2048g/16F82238 2005-01-16

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEHqTvcRBADP+Q221qvMPX+Dweyy/FN00fiDzAcR0jLz6wdIMoyVB9A88STi
 QX5dNU97F8nDpefPL1WD3K62je3enfakfVIhJ0MvYFQXzJhNtLy3kI61ZhUa4UuJ
 I0u7XeQCI/yMDZUxo7H2H1A9CkUweRs3E0MsgqDCVDBRUi9tT7/rjhDacwCgsJqS
 ARkBCjY20J7zlyH198zKJDMD/18hFpRDQRd9yvzUbKiOEr4A3/k3uTqazG7Oyyq4
 6Q8Qk1T8H319u48ghYHH390Ectpau/RnDCWO2gie2zyuAwxcnSI3TR62OJ6MjPjp
 HX6Qcv12jLGBSgFB2y5tAU45775dSgK0I7L4lWvSUl4lQoMeGtmw3G4R9DPGD9LY
 ROxRA/43ZE6W6/TxZWNuB7HchliXJbJJpz28rGTk+YpcqT1eYPr/UG5xYHA/ng3V
 v0nvvnQC5yg3Y+QZzMUGH7yHXXsjwhjloqE3tnASRmVH/tLSN4EdqMzSj/cNIhbh
 QeB5/ceJn2b/LaIQHHlZRqQ/GcTlBc15KuT22djds+EuOmZ6cLQcTGktd2VuIEhz
 dSA8bHdoc3VAbHdoc3Uub3JnPohjBBMRAgAjAhsDBgsJCAcDAgQVAggDBBYCAwEC
 HgECF4AFAkYR+1oCGQEACgkQQWsOOSiXsigCXQCeI9z4NhiiMWt0+KvSpJgb6cay
 4JIAn1V8pCjQBzl9h0LYHJUYRMloZW89tCVMaS13ZW4gSHN1IDxsd2hzdUBsd2hz
 dS5ja2VmZ2lzYy5vcmc+iF4EExECAB4CGwMGCwkIBwMCAxUCAwMWAgECHgECF4AF
 AkYR+1YACgkQQWsOOSiXsigUMwCdG9CjWDICffzc6Vf8piqPltHR3kUAoK0L5tyn
 XSvubm3/ZG69ib0lIRyDiEYEEBECAAYFAkMQYP4ACgkQOl4Wbdx2/rkfFACfQNNe
 0TQp4hKFtNv0vkfrHDtyKOYAn2mIMC8V3kLDWNqvMUc8/5+xsruHtCFMaS13ZW4g
 SHN1IDxsd2hzdUBsd2hzdS5jc2llLm5ldD6IXgQTEQIAHgUCQepRxQIbAwYLCQgH
 AwIDFQIDAxYCAQIeAQIXgAAKCRBBaw45KJeyKJYxAKCFkYQ+TSt4kRH8w+ACWxs3
 6qyrVACfdiuMVpWWxB+3BgwBFCkUuEOVl9OIRgQQEQIABgUCQxBhAAAKCRA6XhZt
 3Hb+uSD2AJ4jZxlc4Heyhw0Q5d8d2VuVI1vergCggEKzeYfumSfnuAjXAIFSGpS7
 DgW0H0xpLXdlbiBIc3UgPGx3aHN1QGNrZWZnaXNjLm9yZz6IXgQTEQIAHgUCQepQ
 xgIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRBBaw45KJeyKKjJAJ9Flo61BT2X
 3BQ5u5iOnusFx/4q6QCgn30dMlmfOF0TPwpWsTCk9GbUMi2IRgQQEQIABgUCQxBh
 AAAKCRA6XhZt3Hb+uaKdAKCkrpXaqUB55v7uBABMnaqgfoZB5gCePmp/WY3HFXCS
 8xxrAA1BLaTk0Ay0I0xpLXdlbiBIc3UgPGx3aHN1QGNzaWUubmN0dS5lZHUudHc+
 iF4EExECAB4FAkHqTvcCGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQQWsOOSiX
 sih8KACfflM50pxzQ0d2X46BDKZFrFXK0dAAoJp2iqma9MK+pozZrHNU5yJrZ1Dw
 iEYEEBECAAYFAkMQYQAACgkQOl4Wbdx2/rnwwgCgg3/pjsqknto8cjq1xeOUr24O
 i2oAn3RKRLYT2nN1LrsxljBqNspO0ZuUtCNMaS13ZW4gSHN1IDxsd2hzdUBjY2Nh
 Lm5jdHUuZWR1LnR3PohgBBMRAgAgBQJC8jOKAhsDBgsJCAcDAgQVAggDBBYCAwEC
 HgECF4AACgkQQWsOOSiXsihfAgCgnha7UtlqUbcHsJIalJg/+CeQpa8AnjvsJo8I
 IYl//PVhLHS2iO2m+7aOiEYEEBECAAYFAkMQYQAACgkQOl4Wbdx2/rlIowCffTdU
 DbUBqY4dn/d44aygEZUfozsAoIXB8+STvXmn2FTbqE9alVpVbWkqtCRMaS13ZW4g
 SHN1IDxsd2hzdUBpaXMuc2luaWNhLmVkdS50dz6IXwQTEQIAIAUCQveLcAIbAwYL
 CQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEEFrDjkol7IoAT8Al3omyiFP/jRhmTKI
 Az86Bj19h8sAoJRgTS43Dtp6dGMSbu1I6/elRAJoiEYEEBECAAYFAkMQYQAACgkQ
 Ol4Wbdx2/rnTkACfZNFUg7qbpMP52aeXAzbJj0e6OGAAnRcK6A3SR6medWLOu/m+
 7rbTump5tCFMaS13ZW4gSHN1IDxsd2hzdUBjcy5uY3R1LmVkdS50dz6IYAQTEQIA
 IAUCREMMaQIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEEFrDjkol7IoJjkA
 oIhMekhRo0dGN0pnP7oXQQfnYQEGAJoCjUvsMh2a9gxy9693BgU5r/lv2LQeTGkt
 V2VuIEhzdSA8bHdoc3VARnJlZUJTRC5vcmc+iGAEExECACAFAkYR9F0CGwMGCwkI
 BwMCBBUCCAMEFgIDAQIeAQIXgAAKCRBBaw45KJeyKAQtAJ0a2zPC9awCbSB0zgrs
 Bl1Qnhd6GwCeJfSTTHOQDzPQfe4DI59amsrTjZ+5Ag0EQepPLRAIALLltW3u2Laq
 cKyQl59v0+TfH8Zt3pRPtjLzuTe8rSdPueCZuAMAntHFevtFGhwLseF305ytRb/y
 y4CuGEoU07qjQHZdGuDTKsZF1Yjdj1ANA7J1uTOlVVZxYLH15p43prUBbtUwL963
 r2Op0tltM1QgEcvqg7pbb14H4XiI6n23dpwmvqMsccDxzxQO2uHYE3dYh7hXLbiA
 jW0+KB7dw33f5zIYPuv0jixsPLxx+S4vp9jd5mr+lMm5C0PhyRun/doAYOP+UEwh
 b7A199br6mGHJgsOX3Gh76NukpExMOIdTLNd+Dkf4BtoQyhSnbz58bQE6UuNplb0
 qp784OllPJ8ABAsH/A8cJ7GMutCmMQOrMZkcR0OYc4cOjFGK98CFp14/VvTgIMbs
 joMA7p/U8COrNvufEzMvHoeuTWGVY4rCgtggGuAyv7FnIMoldUrSpYNvKgHve74D
 zKGk5RlhK8V5lTtRnuBdJ2JN4ugxTODeCnRaRHgUDuErSOYEhgXznwBlx38Qk9BM
 82FBNCThg55QHhFktXt7YMsnxJkrek52MrH2FfbJwEMo29q+aaGtQCLjlqKLlfDJ
 hVXaieoeskOZFDMt2JPvXvtthxRN6IYPKQ02AMKroNFKQn0P5DFyT0VhxgkjWsLD
 97CP/CSEmms8BopwGjaulFylIWLRwdS5ej7Sz1uISQQYEQIACQUCQepPLQIbDAAK
 CRBBaw45KJeyKPY6AKCIR/vAbC8oqyr9HrlhDtfxHgmf2QCfZBeYLPercGOTQ2OX
 MTZHdxZQQYQ=
 =uV7d
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.139. J(R)x>>" <foxfair@FreeBSD.org>

 pub  1024D/4E9BCA59 2003-09-01 Foxfair Hu <foxfair@FreeBSD.org>
      Key fingerprint = 280C A846 CA1B CAC9 DDCF  F4CB D553 4BD5 4E9B CA59
 uid                            Foxfair Hu <foxfair@drago.fomokka.net>
 uid                            Howard Hu <howardhu@yahoo-inc.com>
 sub  1024g/3356D8C1 2003-09-01

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD9TDBwRBACs0PcLGuginQVidy1QScHuKS9G7gd8smYI2FcSsk/AkBhqIkWv
 hieu+iXlpxyZYCDDPKPhieDLkTHc9hYOGG7oTJhBMXUrUqBIk+sqeeUAl/eh0grX
 wUU2khj8EkYC1f6p9AKu25zoyXHxjnKulMhrZRIItg7jVJLaFQn2A9KCkwCgyVeF
 jCegTvZWikBuoXmDI/K3OuUD/19Za3DHV+H0dmfAG7JdVwTW7mJ3nCWJFvlpTSSU
 9Di4VCVj8kUGmo/kRgpZ6gwlCaPmwh/wWiT/vHVQqdd+EH/k/ITs+zWrPOnWCxLY
 zV0BEKtW4kdaP5H9ttNh3Wj1GRpyxh/FrMP7zJfdgze2WoRY57j+H9Kuw2s/42RU
 zYDAA/9wIriNXAj6pFB+J2sCqYXIMNDNDQh6lYFNFgTS/WPYJoA8PWY62oFc0V6n
 ES8GOXjyEya428vedVy/G9kj7cB/IiTTy8Hj7JjhUk/rSIPXMMtNyvM6vQ++f1IV
 1qSzR9sijpmpk/M2RusUQwBP131PnCzSCmAZB8gvcNSlbA9gnrQmRm94ZmFpciBI
 dSA8Zm94ZmFpckBkcmFnby5mb21va2thLm5ldD6IXgQTEQIAHgIbAwYLCQgHAwID
 FQIDAxYCAQIeAQIXgAUCQh1SIQAKCRDVU0vVTpvKWcmhAJ996hkp7RKzCsO1R4wh
 81QBqxZ87QCdH2JXwcclPFAF/XKpS5kbQbKdW8a0IEZveGZhaXIgSHUgPGZveGZh
 aXJARnJlZUJTRC5vcmc+iGEEExECACECGwMGCwkIBwMCAxUCAwMWAgECHgECF4AF
 AkIdUuwCGQEACgkQ1VNL1U6bylmL+gCgle9BEVLP/FKDTEsz6pYH/hdVMzgAn2kg
 KyplWAdJKjQ4AHlKOzi1DKj0tCJIb3dhcmQgSHUgPGhvd2FyZGh1QHlhaG9vLWlu
 Yy5jb20+iF4EExECAB4CGwMGCwkIBwMCAxUCAwMWAgECHgECF4AFAkIdUiUACgkQ
 1VNL1U6bylmacACglEvdvs5wMSB3EEP4qp46uKdXlt8Anivwqzf9dhjw07omH35k
 Ll7D5wGouQENBD9TDB8QBAD+sEewy1REDPQWycqdZVWzxmiS1X+TzSAgfcc7/QKv
 AZEsGADvhHcvaACTBuYRVr8DyzUxFUxeNByWSkLe7N5Hmaqauw681zsI+2osfXbW
 Jkp3JUybeFSIN5pacLNP5+DEAOzzphCF8ALv9H/MB8J9dRhZwDkY7SKt/cSNh4Cz
 xwADBQP/aD4exhzoF1iXR4879xEAAsRy3CCaoiPNeE4Aj9mWmjqEMzWYOjDeZ2zF
 W8Jrn2i+tOVGFpg2FKwtuqU8JRs/lqbedYUlM3UQl2pqGSV2tAziuLKKkzPnKWo6
 79hIhrjQCEPk1MqipoL6l8qZb8vbBpoCee5NF772jR85ai0ZdGmISQQYEQIACQIb
 DAUCP3rhagAKCRDVU0vVTpvKWU/OAKCE4tEk79yRFtmSNNa+ddafxcuyagCeI9MA
 byQOCAi708pPSIquH3oiM8o=
 =P50z
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.140. P:A<<CCURs <chinsan@FreeBSD.org>

 pub   1024D/350EECFA 2006-10-04
       Key fingerprint = 1C4D 0C9E 0E68 DB74 0688  CE43 D2A5 3F82 350E ECFA
 uid                  Chin-San Huang (lab) <chinsan@chinsan2.twbbs.org>
 uid                  Chin-San Huang (FreeBSD committer) <chinsan@FreeBSD.org>
 uid                  Chin-San Huang (Gmail) <chinsan.tw@gmail.com>
 sub   2048g/35F75A30 2006-10-04

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEUjcNoRBACNcrOsDaRrFQMnMjnNViPfgBakMnwy28P/tfZvg+vx/5iRt73p
 5RrBE3dJZyAIOg+3st7sgtVuqeymh8JmoRlVFqLKEpCM1NNqq6TNHhlLBAuIYtTL
 hqN2knPM1m/IZp1Y4a5Z1OVnM6/fqItkxql4SX+GJ5815Lvh+1lokr8eMwCg9w2Q
 HgsgytJkYiFGJpkw1YOfwFUD/2oALyshDDCQIshX2xHPk+zLTMQva7uqDy8AUJLO
 o0DfaofDhkGjZnLpuFrc16eyfaYZw+mO149WTMpWrzCi+SmCXje6MSywINHneql+
 X6OzJCazYCGUfkSbwtAH89gIRKJiQKQfi4xhDrn8Iu+x3YtOKKxnrEVGX2S8fKka
 6YJ9A/99q0NX+543o6/kjfOz6Q44xzoyalBXT36THsFm239AaOejufu+HeyTZs02
 rvrF7IGgga1eUeQwx9gvRNFX65CkUc3AOTVfK2Tn36QJcGfm6r3ZYFWKjAMJ3haf
 aElE7Bs2zGergI0KNOid8rjC6osA3NVYSGI4mKIuQcBoxUNf6bQ4Q2hpbi1TYW4g
 SHVhbmcgKEZyZWVCU0QgY29tbWl0dGVyKSA8Y2hpbnNhbkBGcmVlQlNELm9yZz6I
 YAQTEQIAIAUCRSNw2gIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJENKlP4I1
 Duz6zsMAn1oP0sY1yRMo8jr7iCCdGtw2FuISAJ9crrnri2tcPS3281HX/4xk66dq
 c7QtQ2hpbi1TYW4gSHVhbmcgKEdtYWlsKSA8Y2hpbnNhbi50d0BnbWFpbC5jb20+
 iGAEExECACAFAkUjdFgCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDSpT+C
 NQ7s+pzxAJ98bMcpWM9Vd/YvB2tx2tK3zH89GQCgqOGeoJQvB+MWFM1oVbP5jmJS
 wDu0MUNoaW4tU2FuIEh1YW5nIChsYWIpIDxjaGluc2FuQGNoaW5zYW4yLnR3YmJz
 Lm9yZz6IYAQTEQIAIAUCRSN1FwIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJ
 ENKlP4I1Duz6QX0AnRiAfY8Ngh14cBzYH193/LSIuebEAJ9wY9Gz9WQbwb7QlJEX
 cOmrejGiTbkCDQRFI3FNEAgAsPAXITBR7gx+9AyYwzvtIUjzo+viSfVHusyZccu8
 82qzPKYF3J1QewFczrL6GbPCNqw2c/IZ0Sn8leGgVw5cwP+eUNtcbuQIa8Hpgl0Y
 Ns5WZlr94NXTdU8+mO8WXugzsumUnScnKFhrzEQQKYbbAIavBAzVAoj8Bu2UDaCB
 fCc4S6OwHgUTuLHDRA0b8YXe4Zc/VbblSIZFosga3vishPOCuj0YWjLjdkXHFZ+Y
 We4oDxnMT/yPBcp1/7wqEhTid1dgJvu9R2N9IFSxHTxoHiEsEFa9z619/imVPXGF
 rmcoJb5vG/NSH6cMHr5KP60H4ze0pwMKJ3had+YJSIJGBwADBQgAm9eGbCZ3RUin
 Kh/AJSsVfzW0snA4V1sv3ovSOekROs9YoUkalx8Ywt4fZkGHFWvYXLVb1KnmW3+O
 juhfrjsgmaizQhSMHT47C21XJSvAWuXXZrF6PaIiPAo6q56wjfSS62ycj7z1UlSS
 SDEusPgFG3LfYBuM2wjRYYXZ2plAcxhGt2oM5Mf4Tjom1Y1GHp4m9VOIa+0D0HZI
 +oNYlOteR6I2tWg90bXJcAd6VlSwYi25b/KRkzYyHlU84o11UJnBnG8HgaN6E92w
 QAQTtIUd6PxLWYBG0ni4vtD2ZwyGKAH26QJIUC4bLYdfoZ7V7/MbwI4JEliGjZCl
 INqt4mrYsohJBBgRAgAJBQJFI3FNAhsMAAoJENKlP4I1Duz6TJkAoNRkeWHFV+q1
 WHzk4XJLFtL8cNyBAJ4u3Mfd7xo3Bx8pAs1vSTWooWb7Pg==
 =IROz
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.141. Davide Italiano <davide@FreeBSD.org>

 pub   2048R/4CB47484 2012-01-17
       Key fingerprint = B5C9 77F5 1E67 D110 8D19  7587 EB95 EA82 4CB4 7484
 uid                  Davide Italiano <davide@FreeBSD.org>
 sub   2048R/91F7443D 2012-01-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE8WAbIBCADhylJPj/E3+cPj2CH/96OKzQ1sjdiyzgQVeLinmztCCk+McsEf
 qOwyc5iZfZC0MPJUr7y/3E71HKPC+rTMkOQBHsCL4UWcbJB+3AsA5Ii5WsZKFfQn
 85q8kT9m99MFn8oqZWuzMFkU8zAOEB56+em0xrAI67SyrCPHVS1oWd4Rj45YSUKr
 em7JmyrYEcTRg7rMkPYJyuiWkDR3nAaJw2lScobg+JaHN757QZTtspS6x277Nx8c
 CU7pYauCI/CNdEPUcLAMBH561396IajWvTKirtL7jYZWw0FYpamof2sBCq672Uzb
 XJXufe4Urg4vKoR9giG7Y1kI49XCLmplwnWVABEBAAG0JERhdmlkZSBJdGFsaWFu
 byA8ZGF2aWRlQEZyZWVCU0Qub3JnPokBOAQTAQIAIgUCTxYBsgIbAwYLCQgHAwIG
 FQgCCQoLBBYCAwECHgECF4AACgkQ65Xqgky0dITCvwf/feerE+d+AGvbecD7lQyk
 d/LJs2bshZz+CnsCsbF/mArpbPMJTlgYCMZmEKKSR//nEo0cFyi0B6RR5QzQsouL
 uadHPuwxpuw/7ECdS9QhqEU2O7uoWdgh6kJSR37cbRmmmu0zNp0pMYv2TKrHabQz
 432iuF8I8puOc9++sYLrlFBXfs80TTU7S2+qAfTRqgqAz5IdWZM7F4w+CbbJGfqj
 ePWoXCB7+6MhYby+5JXkpCEpdyGMRL8WZElpB2W91k3zBmkE5bZG2r3Z99hMc/dN
 +nJxI94zYN13HtD+Yoaej2/RJh9zmTWF/pUT58tb63EOLlrOfiiw6NJ6x8PVM9v7
 JrkBDQRPFgGyAQgAvKmBYKFSJur0CiXeY6m3CW0JTS8mK1FYjKp+QckbnRomG2Vf
 olXjcjlTLkLcq46vff2uI8MDNviE5rGYWSJxwYjAbY3QJR36pbdI+ulYEJqnFNii
 jFWv9wvbddNc/L34Pa9o5P/NUf733r+V4gvyqb/Rh5dWQGH8IJCgnZZZYK8YnRiq
 UFnisiZ6gsIXk9rbxd4JHOiOxUop8xSxdeRHEkxe2FQvN8S+HzxrH8lucoIvH1Fp
 red8KUSjOLD1O9LFFSabJ6lA8ytAJ01KP+4svBk/J6bEMwmNXITVtmW+dyTSmS7z
 ynOMre7AG6s8OpdWX2lAKyLL4yosGLiOFjDW9QARAQABiQEfBBgBAgAJBQJPFgGy
 AhsMAAoJEOuV6oJMtHSEJhQIAI6NAWdB4IRBoDfEuo3myxdTn+hKtUDk8jgsmfV9
 6yphv3BDwvQDIoAPjxMewp0UrIH0yEyIduPdZ6Gs9VcDfqWxyP1kGxt0GbKJmHzK
 glmLF5VZbuGKsZDhv0JtWbi17NOt7uiXY9sW9efqaDxgvNSXrXHtDPNzePuo2wLg
 LZcw5VlCg+JftFb7OA72Brcir1zj6EyMgtdo5P2Z2iW/MgWiaKb98hi8tnycIDiu
 tyawSXvl7k/AfQ5hHjwz4zKf+2bQ9cf8ou7wsJ6pOT35AKP9/CeIOslj6cqXE3dL
 MjKE+ZKsBG1d7NkQSQk9MEDk6PdAtigwAgwdYpPhX8Sl2es=
 =pP7Y
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.142. Jordan K. Hubbard <jkh@FreeBSD.org>

 pub  1024R/8E542D5D 1996-04-04 Jordan K. Hubbard <jkh@FreeBSD.org>
      Key fingerprint = 3C F2 27 7E 4A 6C 09 0A  4B C9 47 CD 4F 4D 0B 20

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQCNAzFjX0IAAAEEAML+nm9/kDNPp43ZUZGjYkm2QLtoC1Wxr8JulZXqk7qmhYcQ
 jvX+fyoriJ6/7ZlnLe2oG5j9tZOnRLPvMaz0g9CpW6Dz3nkXrNPkmOFV9B8D94Mk
 tyFeRJFqnkCuqBj6D+H8FtBwEeeTecSh2tJ0bZZTXnAMhxeOdvUVW/uOVC1dAAUR
 tCNKb3JkYW4gSy4gSHViYmFyZCA8amtoQEZyZWVCU0Qub3JnPog/AwUQND7kZgis
 sbaj1yqUEQIhvACeJ58983s/0jjThuj6WeTP6hLZNHgAn0o2KINvhw+Oc8uQk5m2
 aTiVgVQxiQEVAwUQNcJNdAyPjrKngh89AQHA7wgAg3QnT0BcF/zp0VRMUZwAysRC
 o4Xkgv4oaisCPO5jERGEp8NlXuMD6wJCrGRZ9xVwTbSRXJVirNkiSKj1rnNc/pPA
 DbjsmQ+3nhLU+YwNgc2VEhiVpeU2iOL7ircc/YN8epdFPbzn2timb98b+/qlaSiz
 m+g8pxnY4USn1b4CnzyirD7mvHhV61k0mrUSmaKzgg2Ppeo2qPzn4w44hgT5/jjm
 iEMzoH8zFrN3pwcUYYhH5rNWNnqUIMwuPOEHn4Wp+sMti4yOqQxNHnP0Mv6mxS8+
 UKRhtDXU0Ra0SaIhaNRw0k0YLEbO/lteTRc+7cAPBs+QUTa6xbVxIzsBAWLC7IkA
 lQMFEDF8ldoff6kIA1j8vQEBDH4D/0Zm0oNlpXrAE1EOFrmp43HURHbij8n0Gra1
 w9sbfo4PV+/HU8ojTdWLy6r0+prH7NODCkgtIQNpqLuqM8PF2pPtUJj9HwTmSqfa
 T/LMztfPA6PQcsyT7xxdXl0+4xTDl1avGSJfYsI8XCAy85cTs+PQwuyzugE/iykJ
 O1Bnj/paiD8DBRA0FhC0XatM0mFMec0RAgaSAJ4kHkYXQO/74W5m/7ZvQa3CPR8E
 /QCgpHafK/S6PWQsSOChmVjwrZDVP8qJAJUDBRAxe+Q9a1pnjYGyp3kBAV7XA/oC
 SL/Cc2USpQ2ckwkGpyvIkYBPszIcabSNJAzm2hsU9Qa6WOPxD8olDddBuJNiW/gz
 nPC4NsQ0N8Zr4IqRX/TTDVf04WhLmd8AN9SOrVv2q0BKgU6fLuk979tJutrewH6P
 R2qBOjAaR0FJNk4pcYAHeT+e7KaKy96YFvWKIyDvc4hGBBARAgAGBQI1f/BdAAoJ
 ELwCvAMsr1lwqUEAnjOz1VWwJeI2QZMNEHO8RLURWHSYAKDqG+S3NzCeiKM3RRzc
 FubwdsfYLIhGBBARAgAGBQI5ZAxAAAoJEMN1Z4b84RmYUt4AoOtidEj2yIZubvvT
 kB+moQ1+ZscyAJ9dhz4GLNev7zNNfdAKi8JqoqfMlokAlQMFEDF75Qb1FVv7jlQt
 XQEBdn0D/0X2Auka6RU2R46NqrFB0kZNL5rGH8BuTRz+cqEATLGkCXknJDeJ9iTo
 EeE++VOL0utmhcYDyyT95Th5FNlXO8YQLgb7Gxq+UT/HOS7zznlBMs+mQK6dSlB6
 7XDNoitRQTpmOHTmKYVsljJA4GBMWm6pawKuxSmX7aavwgYjEbmsiEYEEBECAAYF
 AjmtSQAACgkQLKRaTx+AVKjiTQCg9FfHlNeMts2GcXWplPQya7GEQtMAn0nrzupn
 fRNx6+Gi0Km+WSlUQkMF
 =ZyVN
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.143. Konrad Jankowski <versus@FreeBSD.org>

 pub   1024D/A01C218A 2008-10-28
       Key fingerprint = A805 21DC 859F E941 D2EA  9986 2264 8E5D A01C 218A
 uid                  Konrad Jankowski <versus@freebsd.org>
 sub   2048g/56AE1959 2008-10-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEkHYgARBACdbmFESh/3csPP37dJBDTkAfWcUck6myVTVYu3dFgwDPA0iCs9
 HolmEV9qZA6m/ljZYG6b9ycHe2M7Xq3Mopdvw7Sa3ab7b2PRLu1WbKUIS/HlOXNH
 p3Dg3/Zhf1raBKMg4F0x0pbQm9+friN44SlnLlQK5M2224X786/VTlVv/wCg3YFE
 CufrZUsIPZndUVGh+/seBbMD/2fhNQhreWxF9QFCMohC/pGSfg1sddpWMqh6R0bF
 aSXfJwYivDLcTp4JYPpZilScBFgSxsfLKboRBElj+k7cj2e8nK4xzfoX+xsGrRDm
 t8uPqISnw8bvRGS3bZNuTt3NqHpXeiL1aEEEEMk7tKuGwlwf/KmA4BYq+eWDM7Hz
 EWPLA/kBJn5jAO99l/h1yGzYiWwy4a5iQd2sZg+M60bC3s9xP8ZvCPhm4qGuis9/
 dxzKxz7hPQ2CamU9DlpnoCeZQ8mttyqnipsnMVniI3A79xSjCP2dNkVWvimc5uWw
 e9ME6DAa2ldmN7fkj/b6ahvCiBZLVc2jv/fcmHcP8IzvhHLhT7QlS29ucmFkIEph
 bmtvd3NraSA8dmVyc3VzQGZyZWVic2Qub3JnPohgBBMRAgAgBQJJB2IAAhsDBgsJ
 CAcDAgQVAggDBBYCAwECHgECF4AACgkQImSOXaAcIYr8cwCgzjJgksYSmXwES8lI
 vri3HicZZUIAoKfdyp1VxyUvbm39iwIMsUBpMCTduQINBEkHYgAQCACT3lbgvRwF
 lzEkL7JnyMaHkw5Lh77Sl2cRu1+fouQeGxRw5CZFwcIUkZWJDgBLxFHJiAtjw5xz
 UnVDm1RWBLXdNn4/KvWOUx2ElPweL58q+j/45qfwISg7JyJckRAvACQ2bLT+2jlc
 iDInZiV9OAnwT3OhBb0a6dvMsbDcIk25QlcS/axVdCYp/ELN4jlgL3Vk0NoQfalo
 rtj/vALu5soRJgq5keyroDlCc2fDp3iISCBngx1xoFBaYaJHo7XSbXnCes3NhAEd
 DkY0QCBWQGyqW/ULGrIdgyGtszpxSlecPmaRlxpmTjAQT0mX+rGE8vBkgH/pDgqt
 icql1p3f9ofnAAMFB/9NCp6oARpDfPTG6upM+oUPwginu23w2ux7uecZuouL640w
 Yj4vssTGDhuP3QRQsDrlhXdHdkUvSuguXpG8EGf4GjflV/AvvXJDmOO3LB4TCQmw
 I+Umsc/4BCP6r/YowSyYmQENJ8VIf+Ps+WfoeGS6UzbEpZbAFfBMpNSQbzwDSa+6
 kh+eAHOZiPUjtoao+eyrvqEK+rpydN3G2D3UOJVsbYbG/3R0zD1sBnNBaqAub4zr
 vMBB0Fuml/pBzhFl+2VrS420Bfy6d83uPriNmlXlTyrX/kSxYVMkVm+lfqrjhSO9
 dj2t5lqpUSCRLO3Wbs/97zIi6Vn2fphH5iA1qI/fiEkEGBECAAkFAkkHYgACGwwA
 CgkQImSOXaAcIYoobwCeK8Jy/4hOkaFBHbi/WJ/SHaJGyNkAn35fpqrdHuOO2L6C
 Tuizqar0AwZZ
 =xCbj
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.144. Weongyo Jeong <weongyo@FreeBSD.org>

 pub   1024D/22354D7A 2007-12-28
       Key fingerprint = 138E 7115 A86F AA40 B509  5883 B387 DCE9 2235 4D7A
 uid                  Weongyo Jeong <weongyo.jeong@gmail.com>
 uid                  Weongyo Jeong <weongyo@freebsd.org>
 sub   2048g/9AE6DAEE 2007-12-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEd0e+0RBACwYdXNeIplh+WEQ9ywP1wJyTpGe2rVvkOLlJNpTJpVX7JT508G
 KuYI2B+Rn/V+1+AicL9tsUAnWX/tDma3bYw0Ls68LvD/571k2GYG3CMTy5FSrrtp
 3v3N75jHDsfulUzHL3LHsa/CA5qzuL819KIaUfTKY0A107vcI3m0v4emEwCg2BaW
 OyiO9pic/WnPi4tuFjLpeEcEAIzLSKzAiZZ7U8ESKAtonwYqdu0BIRFpp0kedXqD
 M9cTts8VjqjdMOm55xvI7h9EGjH+crFZBlZD0NWXD00NrrQdHifulSrv5l3Wtgn8
 xilqUhiYUcPQu2DHSuVlShvNZO6/rYA8R45axAfQv8rFo8NV0oElH+bvGq1mwRKY
 ciJ0A/9lN68t6G3LKmaSfWz13IUJT0E2qy27NnSb4RuKE2TuqyIMFzXh5+jjnp3U
 zRDX6KrYLju5Ire9GGJEMsGs28B5r3HXUPADqVIS8i6dW/npZlyizU7MfoRDFiRe
 btMpnYx7d4qnpKMpEm1J15JF84YrNGvkE55z7+g5zG0ua9KZgLQjV2Vvbmd5byBK
 ZW9uZyA8d2Vvbmd5b0BmcmVlYnNkLm9yZz6IYAQTEQIAIAUCR3R77QIbAwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJELOH3OkiNU16VAEAoKnaR60kp0PF+O70GH7y
 v4k26FJqAKCycX2eM5PzjVzbAKHq0yMRj7tkbbQnV2Vvbmd5byBKZW9uZyA8d2Vv
 bmd5by5qZW9uZ0BnbWFpbC5jb20+iGAEExECACAFAkd0fKQCGwMGCwkIBwMCBBUC
 CAMEFgIDAQIeAQIXgAAKCRCzh9zpIjVNenkDAKCGZSCJTG2dSCbEH3kLTpYdAnfM
 gwCfay7fmNNMrN31IhC2jddWylvSDlW5Ag0ER3R8ARAIALZoci+sXDkhF0ahtePy
 ZszOeKUg8MHIac5RID5CfjGsTsbfAv7eM7TBocAJOKBxhD/suqsdomMBMwoMKYdv
 R4tKCosDopYGwNFNtryXrOQctNKxIf31kc8UnqGfgRAwjABorBRJCQdBZEBm+93k
 lDl0azEWPFuwzZ+dA12dw0jF1/n7TAIkvaA7joFfNvZ8a2WAfJvoal0/nUqmJCmB
 ntaWEdZP5rOEUvVBn117W8D5B8YHp//TM7T3eT4M4Lp7wUQIiwT7fGgRWCIfIrGd
 GZSEykjB/keyIip2Hh//0Ft0Ot8D+4wYz9YhH/RRmfBDMBhW898B1rEewhc0wmjH
 txMAAwUH/iB1/HLYV9ckHT6i/UDl8lEsw5CMxftnEI6wY2i9MWqTSTiuoNE+PQAA
 kicGwxrxxtvLccdFE4WOOQsh9oyzbOeWWBrtxzloRBzaxC9dx+tQaOzzJAUjaEaV
 wneSg2x62naLiztaQ9U66g81BwSyT8NF7uYjsCyvPsrHwDELNcPdDXQ2q0GKj0I5
 tSgqMOPwohYRRS3hYfoPnYZOshdwYErtMCola0hZn7LXJopRByQyT/x2N6WW0zGY
 YxJemF80JqLrf9RtZVSsTeqT7Sd0+kcgPq3wcoqDXKTEQ+K4yjcE7c3hqhowQU72
 2S6S4JjYQhKvdJykZRuvynQGeuT8H8KISQQYEQIACQUCR3R8AQIbDAAKCRCzh9zp
 IjVNepJjAKCIgdGxVdwuToMZ7z1n2mJEulHr8wCfdimx3iKjNLlAE154wBx3v9Rr
 trI=
 =5yOU
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.145. Peter Jeremy <peterj@FreeBSD.org>

 pub   1024D/F00FB887 2005-10-20
       Key fingerprint = 0BF7 7A72 5894 EBE6 4F4D  7EEE FE8A 47BF F00F B887
 uid                  Peter Jeremy <peterjeremy@acm.org>
 uid                  [jpeg image of size 4413]
 uid                  Peter Jeremy <peter.jeremy@auug.org.au>
 uid                  Peter Jeremy <peterjeremy@optusnet.com.au>
 uid                  Peter Jeremy (preferred) <peter@rulingia.com>
 uid                  Peter Jeremy <peterj@freebsd.org>
 sub   2048g/7E0B423B 2005-10-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 26334 characters]
 fl2shbeC4ccb6tc+jg==
 =5gZR
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.146. Tatuya JINMEI <jinmei@FreeBSD.org>

 pub   1024D/ABA82228 2002-08-15
       Key fingerprint = BB70 3050 EE39 BE00 48BB  A5F3 5892 F203 ABA8 2228
 uid                  JINMEI Tatuya <jinmei@FreeBSD.org>
 uid                  JINMEI Tatuya <jinmei@jinmei.org>
 uid                  JINMEI Tatuya (the KAME project) <jinmei@isl.rdc.toshiba.co.jp>
 sub   1024g/8B43CF66 2002-08-15

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD1b+Q4RBACetpZD+bWytVmQ3Itmu0ZBfSDF6FVyUQuKS3OZmvsZHxxqq1+u
 erHNhmyte/aCI/YrEUzHPT5LU+9LMpRQD0AwSs3Ot2vUzokSiTu8ZqhoWBcsosKK
 eKM73V7NiTgBGuJ3UxVmKNXzUZhRjGHuekB/ZCCv1pDg9B3HPL8ty+2M6wCgu02T
 +vMZW0VeByn79Lpmm2nu/F0D/3NN4e8ZtLTbUJxJb/hHhLzOr8XahZCqsNF2bj0C
 0u2SzkelDa5iVDWwiOkg7xI154REAALOG1FnLyO4bRPkcQ/EO5tbzXoVn0I6MPWA
 EiwBfVRXzP10MDHhqH0NvT8pyA4ex/BflaeFem9HItRjfojdqEUYVAACceAdLQLG
 MknWA/4hfAAp+dPcU8iHmd7AemuGoOhu5AAKbp2S4vwozJEFiv67wD/+WFXVggUx
 wbQ3X7oNiOLeg9OASDV5qtbGPATHikYagWVjndqmvxO1FiL6BnQBnzAVzOEN3L2K
 Ex566bUw/2R/dr/zhOc3BKxCV50T2Xe4u/cEiYkUbLj6+Y8V2bQhSklOTUVJIFRh
 dHV5YSA8amlubWVpQGppbm1laS5vcmc+iGAEExECACAFAkYDPqYCGyMGCwkIBwMC
 BBUCCAMEFgIDAQIeAQIXgAAKCRBYkvIDq6giKEOZAJ0Z/iUCa6UrrsVmKiP4a9qB
 0jFUCgCgn/3mQxdtXTA6SOlFFsisaxsIXIW0P0pJTk1FSSBUYXR1eWEgKHRoZSBL
 QU1FIHByb2plY3QpIDxqaW5tZWlAaXNsLnJkYy50b3NoaWJhLmNvLmpwPohZBBMR
 AgAZBQI9W/kOBAsHAwIDFQIDAxYCAQIeAQIXgAAKCRBYkvIDq6giKBtcAJ9DRqXt
 h8WEpjgr+sD9OuaYqmV8nACfSdo2Ml+Qfz2Rad9OtZodmELCCi20IkpJTk1FSSBU
 YXR1eWEgPGppbm1laUBGcmVlQlNELm9yZz6IYAQTEQIAIAUCRhkdkgIbIwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJEFiS8gOrqCIo11cAoIJT7N2GMSNXAujnuIvc
 HnBtgk5zAJ4qDo/En3ic8E7h7zc4lT/WQQDhRrkBDQQ9W/kQEAQA1Q07/j0kScL1
 WF9EeXVEyLpTxHZ7owTI+KrRcQ6Vc6KABu1cwhE78ANVfn/CkWVXHyDEnWEIvaz2
 QYwz47sqOxdOg/AmHFVd8xouengw32KNjViVBMsW/l8VzyAVvvGGNuQ+f7zDZ/P9
 v9WwwRcrgL9g+uAnrJJo/wttIBqhSk8AAwUEAIqcIez2zlkwGayFeLqgwuw4PCbd
 kGtXs0l2mQljv8GWuTRJ5D8aD0nlM9MNaSLB7xq6igMriP/NyfIVv0aLJwRH8ilx
 RBYosGvm+nEmUtakhU/77uXcLtipoUGi+y1reFRVSoypJil6lqDTjKtWQlWA7xOG
 QzGMdgoBC1d55jXXiEYEGBECAAYFAj1b+RAACgkQWJLyA6uoIigNBwCgsUFgZMfR
 sEybYW4cWwBNhNTqE9wAnRf9BFkzpn3ZyD+NBkjx2INcitoD
 =ISn8
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.147. Michael Johnson <ahze@FreeBSD.org>

 pub  1024D/3C046FD6 2004-10-29 Michael Johnson (FreeBSD key) <ahze@FreeBSD.org>
      Key fingerprint = 363C 6ABA ED24 C23B 5F0C  3AB4 9F8B AA7D 3C04 6FD6
 uid                            Michael Johnson (pgp key) <ahze@ahze.net>
 sub  2048g/FA334AE3 2004-10-29

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEGCy1ARBAD/K2SbL6XiTJ3Rn/weuN/L78ROUltIoRGOkZE4971fLcAbtIsf
 nANWDrpDqbhLgEbZLeCn/EIWOPqrYyKpCGu/IoZ6kx7UPtUH4eooJBarrrQPJVV1
 mfW5ktDry3AoiaUH+jL47AxFCb/bh7Rc11vrhLKdnc74wI+nu2cyk2llkwCgwX78
 nlN2qTrbXxOEAPpJjMontfsEAL+4sS9DOay7NkZq2B2p9AZnSsXQg6/r8Epqznqj
 yPQBm489UcIZy2FiBwaUR7w0fMh5xNX0FE3xFiTd4VUTgUJUSqpYtdfI7IHvJXml
 P/VK14CtgRY2B24wpDPMae32hGBFUwSE9Frb5NiKlxMC4+fR71wZS7MtxTnwJ1v/
 MoVaA/9FyoKCAw3Dqnf5W89dj5W5x35jLKSLobEhhUB2S2LPiwBa5A79euMvgtk0
 gKeh6IslXKOmCO148ws7HSaErBIBVBDpfOsqcQJTcd5lvEbslp+z2oCKeQK3pgQ5
 aEHp8IJ3YgQEHz+YityOF0jCMGNJTFAz18U4RzVxSe55iyT/17QpTWljaGFlbCBK
 b2huc29uIChwZ3Aga2V5KSA8YWh6ZUBhaHplLm5ldD6IWwQTEQIAGwUCQYLLUAYL
 CQgHAwIDFQIDAxYCAQIeAQIXgAAKCRCfi6p9PARv1oW2AKC0xjNgjhL1EHPtFOXH
 kGz24lF4QQCfQxkoJBq0CkLQrYvdA3MLP+IJ6ba0ME1pY2hhZWwgSm9obnNvbiAo
 RnJlZUJTRCBrZXkpIDxhaHplQEZyZWVCU0Qub3JnPoheBBMRAgAeBQJBgtexAhsD
 BgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEJ+Lqn08BG/W4JwAoJaU6MbisTlg4EMF
 jfE+wNptwO4kAJ46A0W6SiLWbK09gu7YlgfLgdYAmbkCDQRBgstcEAgAvD4PzCsh
 muLtNkPVKSlk2eZbqlIuyapbuIo6rHk8fo7fkfqVOOrnGOrAT5/sflmnG3H0BLvF
 4pkk7tyRtg3hz8qGACCA4SRf48TxRERpIUoW5R2cVBsMBTnpspRaFu8OdBL0dwXs
 LmH797gxDXCGXzSU5xKBSQN4LfoEuLr1qQmPbuPW+Rdi3hrdk1eGsJ03rU5RExzQ
 ck+J7a5VWsyghNCSj1Rzuw+0OVGBijJW51FD9QU+Eqb3seL7E19mWC3FMU34RFwn
 5lbxolY43iPV0jc0MFcV4POHUSZ8ot9xbQpcAClTyXZh21QEIFzYjJe9ZeVWKOqH
 UZS1naB4k98G6wADBggAnRlPolzcjJvqvv5Hfv7oDeDARNxqeKTj+fPXIHR0Gh34
 8HMfmxsFzS6nsrrVc43Q6Iaso5hbdP4UvE0/HzhPALzCTeZGpZF54pffg9Pqb84U
 p+D59I+b88RDBvvfwF0OBg6du08Rdkv9JfG3R+QZembK+IhUa5yxhtfbQmI6Y01r
 phtx4FAKZw4Xp2eb7IBoZWktfcOE99UJcl9hUmBHJXRznQoCHz5OwAKA6a/0b7j7
 B3bPxj+tLlQksdmRbEJKVBa3LQm09PkxfZj8iahvQbp23p5VSJDKzNDrgmsqaCpV
 CFNgMvYLvtxC2xA0uNtaRpdZRLS/11NUj3oJIULv8IhGBBgRAgAGBQJBgstcAAoJ
 EJ+Lqn08BG/WFK0AnjdWWBxG7slwI8u1W+7uRsuh6NXMAJ9r+6Br6mlEtsoWrMel
 IlhG1mVq6A==
 =I7wA
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.148. Mark Johnston <markj@FreeBSD.org>

 pub   2048R/80A62628 2012-12-19
       Key fingerprint = AFEF AD33 1C4E FFE5 141E  0157 05A4 DA8B 80A6 2628
 uid                  Mark Johnston <markj@freebsd.org>
 sub   2048R/47C7D3C2 2012-12-19

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFDRQycBCADMNjnbsXUOlvy35VnAJWE3zHAPqmXKqUTh0t0LWEtaD8KaNMHY
 egadQNWYwJAjzAI07+3grk8xcJLVjbbB+rC45tNPAxjAf9Jd5WZkZO7vKX0tIDLc
 Kteqp/5UB8SZ+XuhrtzLkObbEccwt66CF8vsUps5hWm1d+Nfxd798sjGmB8uzRJm
 gO2RrVtrOW7OQG+aFjBwlQvaiYavQ08z/xE2b83Y4Jp7c1FlqneFmK4xWSMO1qEE
 Qre8+iizDnPkGVabSLGJxE/EjTpHVBSawkXBgs9AOBoUR95fRr2Qc7GtP0NCHiNP
 FecGq5vCdIVyejUVzWmviYP7y0roG3yE+AppABEBAAG0IU1hcmsgSm9obnN0b24g
 PG1hcmtqQGZyZWVic2Qub3JnPokBOAQTAQIAIgUCUNFDJwIbAwYLCQgHAwIGFQgC
 CQoLBBYCAwECHgECF4AACgkQBaTai4CmJihAPwgAn9yH8EQiyS2x2qy5Zecl80Yz
 sLHSjc0uCBCNyzaLgGnMkqQDljyJzgY8DOL2vCWgSO0uJvb52Zl3nwxNoeMpwA3f
 rcaurFUUTCNmq4YfAHxjkbi5vQI0uJP7StFcFRPcnBOF/ddi+KUdc++xhqvcKBF9
 uHVLK+6MMp4I9ofXNdrenfqXaODDTIaSO3SnL690OFSAAkueDN5hjJRuuEprbZFP
 qyfzwHAot/Owy6Db7LA9MrE4GQFDszA+wvXrreMDdPIVV8dXXZvuS2oEVV9XoTUY
 +VkcOdO+UlD1DWyEP1cZYhyzhwJo8G7ZZJO7JpLB6M6c5bdAyMtHW/aAinh+J7kB
 DQRQ0UMnAQgAxnBvgp1D8Ek07hhV89yhPkucEuxi5Gz8doYedzB6uOUGFdUK8y9B
 gwo8dSjIY3i4rVpJlarJNvd1XE2Pu3YlwvW1Gyo4pa1M5Q/QeQ8thW4k8F4r+RGN
 6qqk085diUKWSwyhjAULOYSWBEbRaPp9L3FNr3uYncrAFhKN3n/o3+18DG2tS++/
 DavKZdNgFKnoLEZeTSOAdvwkTjcWV6lRVcI8vsbi1bl5dA7qCbhfRmJJEaMqhCG8
 bEIJ6r5JtmDNwOzCnl2wS0UsmsMV2lj5BGiRmyw3xdxDGYTICm0j+YUce9lb2V6H
 PWcHCil+Jcg1pJ5oKai4uR1Oo97slmoiXQARAQABiQEfBBgBAgAJBQJQ0UMnAhsM
 AAoJEAWk2ouApiYoo+QH/RLaL2ouB/bxkED60YgdaiOHX+3ZUeXwh5SHapS2cFXU
 ySUcYmFe3fbsXoyeOi4E1AG2k2PyVk/cA/HDNr8eiqgFO91dQ6RnY+VnbN+DGRGl
 9oW7kqY/7kV0ExXpPGSmxdobpeCVkSO3WzY9XKC5VUosc/jCm3+6NqZaCnIIMUNA
 qUD25P9stIBvEv+QrkRn+9vnSHbyvnQvaHWMLrItMgyjrZdd4LevLQaCo3bc5+eI
 4ZhBjHErzC4PmeKgy0ancqWMNfgdZ3fzk8Tcwfy20S+b+TicU0xlQnx8bkPlksCJ
 h7pRVYuHo9VkueYsh5UoyrMJhYe7DQ4lGbv2fj9KHZ4=
 =b1OB
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.149. Trevor Johnson <trevor@FreeBSD.org>

 pub  1024D/3A3EA137 2000-04-20 Trevor Johnson <trevor@jpj.net>
      Key fingerprint = 7ED1 5A92 76C1 FFCB E5E3  A998 F037 5A0B 3A3E A137
 sub  1024g/46C24F1E 2000-04-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDj+agARBAC1AfvgGQEVdLwS0dirwaN+pDDWWiaSWBNRNo4T4KKG2vyhhnUi
 f2PcjPx8rYLvbokJFltoTWos3lS8hD8PZGBDlImOPzffdm/GYEmr1mE8fQvzjdKD
 iOTqQi5IYYhLZIMmUpBTK7XN2zrM8VrkgCpb5TYtBrQUPheWs/SZ31EvLwCglUPA
 T54Joolfvk0Y8I6dSGYctpUD/3teZiYwem99CE3b1tsqavQ1MUfjwSPZQq8wjVe8
 GZUtwaeExugAxNjXIJeXiaCij7S6JSTS0ytyxZ5/O1QFmBhuD/7zjNFD8yB8nu8x
 slma7mVhMuhqkwU06hTkp6MNNJ7kRItoVETtLqR5mW+0UUSZyePQFIH9U7TKPG3W
 vYMIA/9btsMQD/7QA9p/m5OP4sfdVdNCZ32tJ534bMjDYyf/P8k7QzvDWU8f7lbk
 3vX5pSmHplws0PwSZITmRarMdEH9ucP+24m06MQ7YmDYyLlUCestT2gAxnB5/X1h
 fJnmdCLi/Vt19WrVM79ebddbCqCaoz0xv+1qOQmPue/vKXIH87QfVHJldm9yIEpv
 aG5zb24gPHRyZXZvckBqcGoubmV0PohWBBMRAgAWBQI4/moABAsKBAMDFQMCAxYC
 AQIXgAAKCRDwN1oLOj6hN4YuAJwOTOURcLpgAx4HT43jNxDYCsT7DACdFdGCwsi4
 w5ZiCeoizmoBMFvYTa65AQ0EOP5qIhAEAMAerdyvcs7DOxpsli24gkKJxCwHSq9U
 23k283XpZHOp/0eS6WEJMHMyQ7BRrx3X6mkSgBEnHdO6MetBQjOHdjSb8ycotrJa
 H9eMkZ/Iky6dbiWpPLI4ytS4Q8Z4oEGjUTm7pJiE/pgmaCX/kv0WMs/35En+42sY
 VoVU9bDI+X+3AAMFA/435RbM6ywO/kL8D3lhwINGEIqmxWpJDlXPPJf2pLiWZZVK
 MLGkHOTe2kUdd+E6WcoRZdGblOKxLACrlKpJa91aw1ftQT6rt0k8GDCGLT/33FWx
 2IRSf5sHmz8IOm6L8TcZU31hdWqpDLmiIj+IjUCx8+eAUjZcVRoj6BYnWc1Z64hG
 BBgRAgAGBQI4/moiAAoJEPA3Wgs6PqE3PKYAnikfYo//UA7/jrDuTXzqPmi/Un5f
 AKCFsfcXDbLGfWaAqe2YzeDR2Z55/A==
 =N4HT
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.150. Tom Judge <tj@FreeBSD.org>

 pub   2048R/81E22216 2012-05-27 [expires: 2017-05-26]
       Key fingerprint = 8EF8 36C8 44A6 9576 6ADB  EB0E 4252 33DC 81E2 2216
 uid                  Tom Judge <tom@tomjudge.com>
 uid                  Tom Judge <tjudge@sourcefire.com>
 uid                  Tom Judge <tj@freebsd.org>
 sub   2048R/2CA4AA0D 2012-05-27 [expires: 2017-05-26]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE/CXmEBCAC8MHbsbti3GMu7pJN9c7MjfHOyY7ZFGZ5KWET7KCgYr2uUydwB
 ZNaNIZczdNuYTE3Q1o4F7A7EW9bsfD5b8zZZK9usE5kBZJQdZhEnd6mJSKsV2CwM
 CBwnl+e1+9ITMOxD1CL8rjQ2JhIUi6DADtVO6N5eSB4I1qKE2rd9uyvQkjBWNOjF
 d8QgfcFEzvXL28zzkBPMoYJuZOQ2RrUZUr2GQZJkLbWi1GZPwEJ8bxuHXyAkvRgp
 SDQNW9jnM3mhcsSn1rm568JLGJVz17pjxoM7CJLOYm63vl2nJWo5e/VDyIYu3XA2
 H+9UXMaoar+2wNSk1bDe4QDSqjQr6bjkiODdABEBAAG0IVRvbSBKdWRnZSA8dGp1
 ZGdlQHNvdXJjZWZpcmUuY29tPokBPgQTAQIAKAUCT8JetQIbIwUJCWYBgAYLCQgH
 AwIGFQgCCQoLBBYCAwECHgECF4AACgkQQlIz3IHiIhaP7gf+OHV0TjB9DAVbiuKM
 7itp9AsWvXAtEJaydaYyDJgBkJdncshtG+dzhKTDxoYExGVGaNDCvw6sNld2fINb
 staofgMYs3ZucuKaGL2V0vcPvAR8y/6a+k2xKfdHW6UE8YCYbJJMNOP6gdGvF7Rx
 OP169r/YJulOi9fzPkU7YuH7Bc3/mumLK+n7jpd14uEvpQlER5OydA9j4inS/sMH
 7yOEJP5jIRmp2RzJid0zJj6Mm4IJo72gjqK8/3OdY0ZspI3VJIZAMLDrKpEMWI2i
 qkDovYBGI3sCAnyxAf66II44MaZs5Zg99kJ09mUjw8Yzn72lU1W+A0v5DqfpskKf
 1u3fubQaVG9tIEp1ZGdlIDx0akBmcmVlYnNkLm9yZz6JAT4EEwECACgFAk/CXqcC
 GyMFCQlmAYAGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEEJSM9yB4iIWssIH
 /1GsA1JAt11mheL4sVZ5g6lrokXsDrpSNQ2QrECJs5ZfDLn1z8Zhi8SdP6vyQ16B
 /bHwnGFHzwxmbUq5jhDJyhZO16halh+ZQSFVbfjJXAu3T4D1Zxl8HFSf5WccalKW
 vkFtr9J0dGEH/xOSj5zUtF9/eO7AEMYdgevpzT2tqztY8r8Ka3TFTaK1uV3ZfqV9
 qpavwNPzJ7c3Td5fsYHAai45eb5UFFHfWfT3nbo0718TE9NXbP4JGZghdawmQUf6
 W8KbQuGmg2qwlO7hpMYXHrf7nv6C05iYwWuJ8j7LLfnlN0s3FiaNw5W0IrKmOxxI
 jmSO+2dkr5hjidy0hlkHCym0HFRvbSBKdWRnZSA8dG9tQHRvbWp1ZGdlLmNvbT6J
 AUEEEwECACsCGyMFCQlmAYAGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheABQJPwl7M
 AhkBAAoJEEJSM9yB4iIWO7wIAKdLANMK1j4s9FG8qzxnchCeXEwygGYvXy3nfOXa
 H1vM6641ADlA/8B1Y8JqU7Zg5AyR/8fv3SDLpGAre5wJX5Rxdd8/zn1B6tcbgno5
 KtGC1s6Gug3UtFWmLxCNMdM7cFByQc5Yz966j/VxDEDvjXyymqizvGMtEzH430gR
 UnC9BqZnq7KUeh97qwZr+G5pSBdKRASUcCDgCB48AAknY4cZLoxOJs2GJXzOPlnE
 /gQsv5ZC/eBS2f9fjQzgP2RDL5yMgdpUQjwZgkXW9q167aIwJwzExkD4zf2hLW2w
 E/KYi5LRjV7UgIu4kUu7bQZAmfBE44nd//qzp06ikF3jWeCJAT4EEwECACgFAk/C
 XmECGyMFCQlmAYAGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEEJSM9yB4iIW
 HkoH/ib5LvcVNUcwcrrQU5w5W2AbuQG8DmSWgaWWZa6Fd/76hYq8UtUkRX4eXIem
 Ju1/aAo3YpaiMJ81AnQopWZixbxTgDOM9P7javlMMo36qDwe2N++BcsojfJaCf4H
 H/vt/dvIahKKLNsy5nDMPAZl+Cb/33uZjjbBkOP9YFvxKJcrkBjoF7rkmT8kewT8
 Va6LPVCxLSORAivr5nEo7lr8Of4CuGHChSNBQofZEqlujipVwEUYt4x7rRCE6c3g
 xG+d7omaNOSYDtT35Wk85UVzE9S09RdLEieJ3rgpaYW0hr/D/19qL72TCUxBoUbs
 /wASrbtxYEiSHIo5Mp494fSkdd25AQ0ET8JeYQEIAKToUksGvdHmeqiC1nOZWUjF
 y5GRBue8pDwIKDy7uWMZvS+a+au5YEIFsKl7uusoYYu1mKuAE4qebnPlY9us/PlP
 EDPFK9YIYVnmk+NAQFMxE46TQpfAXT0QFxPcKYE6MR4YezoDOdvDjd23dqYe5deD
 sjrbYenlJJleFWRYWwFQ187tgNnMXgwEURCjYUc4jop1d8IBq128v5PW1cuEqKJ0
 4YsWp2C1TToxvhw24ZBqKW0BvDMP17omDk7IyD/Q3BnImU1fB/9T8TIYGp7Fp1ey
 /Abu63bkkixUpJAs9RbNfyZ2dQBFzlYGWuVfcYKleZGNKP9tXdRXKU6FWDyTgyMA
 EQEAAYkBJQQYAQIADwUCT8JeYQIbDAUJCWYBgAAKCRBCUjPcgeIiFow/CACyVF2z
 V/2AenlR6b/oEEOHHOrRCUjRFdNdfJyd5xB9tY83RPnxOIN+ImHKTHpCbO8XXPr+
 /69y9SyFSbeIXssKpQkoDpBxoLBTLRHWvLxIsMvj1MS3yt3Y45mcKGLYUTUCFoLL
 ZBfTFUbhV7Inhrw57nKMO+F43JV35wO/2HvgtVXhMyvSOwSuh+rmWyvBI+bbQTeW
 L/16IV6bqLvKPF64Udc636mr2As1gDyFYYbzoKunXGfs9V2e9tHOg7MhbGh+RGTQ
 QsYzGa7JqrqvENdXRniOZG9PVQ6okKNPWyaSF93R0dkuJ3nN7j/dcBWcvLKZ5q1M
 Zm0FKdW5eJP4ewW8
 =jKVY
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.151. Alexander Kabaev <kan@FreeBSD.org>

 pub   1024D/C9BE5D96 2002-07-01
       Key fingerprint = 7474 A847 DBF5 50A5 FC3E  F223 43AC F58C C9BE 5D96
 uid                  Alexander Kabaev <kabaev@gmail.com>
 uid                  Alexander Kabaev (FreeBSD committer account ID) <kan@FreeBSD.ORG>
 sub   1024g/534D9E06 2002-07-01

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD0fyVQRBAC6DXZDVJoFc4CPKODmJmep0t5dD+ObG0hYiMfo4ygDAvsftJPv
 ZR69EUbKCqVOXPy5InOR1o1xwERvNVXxBGOFwAdoU4eJt/f3ttR6YSLWDG3iHWRQ
 Fze9mtZ3bCBcdv8V0pXint/w41y9nBmG03F+Ag2toD5mHYqV+9vqH3XTmwCg7Rq9
 K/Pk7Z5lAR/XWyJv6Bk8op0D/j6Jef2ate9+NwBAti+9GgIocBGx36X/SpZonGOV
 xtX5E2MranZGCVnbdW1hXfKLaiRrooSxbGpMnFbjqY+peHZ905pd+3v++L0sGSUA
 gLbGL+5GFDO/WGay0vTUBs7Bl+1cbsdeQ67+08WuIRfcbDjA9fYxI9LLTb4J+IrD
 Ni36A/9WBGxkXNJCTrtAqhCoHRgfo1CHNk+U3KiIlwFfvi1WRkqEgFNQ6aLNsPcT
 DkIoPLj2hqKf0Pfrr1MWGcQF1uYxtW8diFH9FzlZpkwXvHPOBsJSWtH8qcZ7atFC
 EIwvZzurMbYWaTGNYMEL3kj9aRjKb2OnsKABZ25H1cioFReMx7QnQWxleGFuZGVy
 IEthYmFldiA8a2FuQGthbi5kbnNhbGlhcy5uZXQ+iEkEMBECAAkFAlCtcHYCHSAA
 CgkQQ6z1jMm+XZYzSwCgx20s6h6+tB6nj7gs0mHRmXEd9rkAn3PbiVCY7AvRcQKd
 jzMg1fh609+NiF4EExECAB4FAkLcBooCGyMGCwkIBwMCAxUCAwMWAgECHgECF4AA
 CgkQQ6z1jMm+XZYJIACePCBQpk+mw0WvLAkE7I5DkeCv4w0An3MKAuq3Acnzxw5J
 1U5XsB0nooiStEFBbGV4YW5kZXIgS2FiYWV2IChGcmVlQlNEIGNvbW1pdHRlciBh
 Y2NvdW50IElEKSA8a2FuQEZyZWVCU0QuT1JHPohZBBMRAgAZBQI9H8lUBAsHAwID
 FQIDAxYCAQIeAQIXgAAKCRBDrPWMyb5dltYPAKDD2YYKr7ZDEbVKAdyHOyF5dl+h
 3wCdFWg9dC8w6dD7nUKvg9b8cq91byy0I0FsZXhhbmRlciBLYWJhZXYgPGthYmFl
 dkBnbWFpbC5jb20+iF4EExECAB4FAkLcBkICGyMGCwkIBwMCAxUCAwMWAgECHgEC
 F4AACgkQQ6z1jMm+XZadUgCggxcqTFp+zV2YOM+cDlVtreVZDo0An1kXV2vUaxap
 0fQTq2QMfGyMbsG8uQENBD0fyVQQBADOlRurkQxMzKcXE8Wfb9dimYC9gyNso19f
 yKAJGxD1lgvJeVyf2OR4k/d6ctQAcNuv3qT0al9rE5DQMiI3fC6xLA/xJekqDCu6
 LLjdwLYXJtjSq6HyY2qUS4+sdPJSpVadaMKE1jLVEYCtXi/Q1gTfwPDQp0GzSS7i
 gyouzi3QuwADBQP/d8b4C53pgkrcHQ/xOv4UW5KQrJg5DZMMxZ6gF3IGFGF99kHi
 d+zBtrzzlq6PmFpDf69LRaISk0qnjDAsrRt/ypnsRnQ6YOmTSSOKK6y7runPTwaP
 /gSFeDFk+9ZNxjebpcoN6SHFxi3V/4ITVJfXQJIU/BT05A6LeZGYykTdrCOIRgQY
 EQIABgUCPR/JVAAKCRBDrPWMyb5dlpHKAJ4x+Ltw0UyNi82weZpghm6b02OVvQCb
 BB6jh/RjnfLoZ/Cq2dke6K5Heok=
 =4r9K
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.152. Benjamin Kaduk <bjk@FreeBSD.org>

 pub   4096R/8302FE9F 2011-08-20 [expires: 2013-07-21]
       Key fingerprint = 9FD9 F966 D914 5101 BE59  FE13 2D29 EEED 8302 FE9F
 uid                  Benjamin Kaduk <bjk@FreeBSD.org>
 sub   4096R/28698ABE 2011-08-20 [expires: 2013-08-19]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBE5QM/IBEAD4VgPZlyj/d8iPgLAUdW/bOXUe6yY04TBmrf9V2q4U7bzpa1/a
 tuwfiachcg4xogW4jPDIBSfGyKRF/2EyKiQjIr9lT+oj05H4JeFNJe5zojIg3M2y
 iAfSkHcz1NhKQztSQe9jD6qx1samNugyD8CmNorUz43WS9ZCHI1lVFXTBzjAB7D3
 WNQvq0azhmph6EPNmFVjLuOeYpWNt+4ZfaSIbifSO+7fwfI/AN1+dTtiwBFaFvJI
 QR6P42bQY73fBL3I8nVEF2Yk1MT9pnm8s2gA/kDPNCM7qTnyDmF8R/7jsdqMXaHh
 ChDEdD8arAo01DHQdlMNBHUkMOLyw0h8WGhtBPoAr8VpvnEReNqP/utnk0slM4Kp
 uRIo0ktB1oldgYJgj/Bj7dal7wtMMA5uttYzNCvoAyiZmj4YxurfiiBd4+MM2hWG
 vP8FJj/GaAADICE0d6V0NUOkB4duzw6avCnoCXnUNYrTJrdqCisumOWydfGHGx+f
 8ktj0gajCKE1VUe6lw9oT26VR0j2M7Cn63hpmRY9j72zle7cFVBElEUu3nA/25H6
 XHoiDX4W3sU8CCiAydWnhVkK75RosD9CedmUMtMe+X/1IaCe+VI7QkxF1/Qk/VBM
 AVnMoxQbNSqHUMAPUQ+J+V66qgGPneF0x0P/xSrlGhrBUEmlqFXl7TMZ5wARAQAB
 tCBCZW5qYW1pbiBLYWR1ayA8YmprQEZyZWVCU0Qub3JnPokCQQQTAQIAKwIbAwUJ
 A5sm6wYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AFAk9ZaRsCGQEACgkQLSnu7YMC
 /p/GlhAAwOROwxkzieQG28HJ9hg0trVGM5z/MtBaUFLIihKjcPJhMIv41iatynj7
 1FOAfmWbnJuWCOUzHOEzUo6Slkowu9FP1rl/NMVFgohnrMkUsYnZHIGr7lCtNo9E
 kwGlp0sFAS2KlvsOZszqlWVYtlpVkkAaAPz+YoTFOAmNNUC3aKXbnRCOFVTDCn4p
 nMKmubAui0V9cr/1gG2lT2xs7+le5iriFj49TK/+JnVtY7sZ8iF+K8PFPO8H/1lc
 eQupOIqv3D0FbvnFVlc6bqO6yWsedtS7qSGatdC9FznbcsET2SruarklyLPTfS6c
 Srw284iVkdDgqjFg/CTy8A9ve6BFe/fa8Mp2YbZVivDxZVMZQ5csRqwttZJaiV43
 TktAtKC4tRnMDBENgCKFysV4n8ihrR53P2Q2DwoOcwFZu4MbJ4pxeN4wevrzNJ9g
 VhNlverp7qakFMY6UxcW8iZ521WaPxDOMW1ewr39kEFVZDPwfhflWtaSVC9CcbFs
 6+QINcrb0ExtDU19TznAc2OlFBHEao2Kgf9r8DjVuHTqeVbZUN+p8QmVNwAeCHoG
 03lvMv8uRSWMftBmfsR8DdM13Fgaeywd8odmAw5tILmM2KZYWX5lcz4nEwXlG4wg
 LIRqWv2zXxv49ZjCZy3q0XqGcgUZaEPBIue0tluTJKljHSsh7Zq5Ag0ETlA0OQEQ
 AM08zan83E8KDfJGmXQKmH389BbmNxYswsAgvLVjOua7hOMw0VQp9R1/Ku9r97p2
 g7OOKan45BkVDJUwj01oyjBcbYhi2mjq0W3wIWkVn75cVyqGMNBoDywB8N/Ara+k
 2QXjR/MOQUBuC3HfcExtUj8UKur5ud0gRMwg5lABuXcCqWVcbfQBJ2fu2zbFPWha
 NVtq6cm6CQIzZm6mqMJ7lVzBpgp/TsDlLbkiTjUxyjNTNvjuGhg2nSvalkqz5J2K
 Vyz1lVNm/yLm6tG7PIxKeVlHgtj1M8nCbiCSpU/bkmBP4qirZMe+MjUER2B6xf6p
 ydqLSKEZ31qRPDaUhaH9kVv96+zvO3PacE1ecAv/mlO8YwStLO9tcRZX8rXP6jLA
 uJ7yjSy47RXbfh296NqanplWz6XctSplLqXTFiN+DNiNEPFCgRucQMwbsqKkX8ro
 61EYwuKk0k0g0P3Q/06MQ9yf8McOLCNAdM4WJR1B7fCT5CDI3siOJ40lKbgjgaJ6
 HcvjP9n0ymZEgNCvP7BRclsGTV5G3LZrYyGOsJTCcjmTG9qHFJ32ADM+K38OHFO6
 G6lvciHQ8jfsJQg4XmIwpBLtCLNpGvObDwZLst7kdztdtKXnZUXoFLhGvEb8GMds
 CILLXdJ1o0nGXyX1Jg6JQWLdVZKyFInCsCxqjSQtPgezABEBAAGJAiUEGAECAA8F
 Ak5QNDkCGwwFCQPCZwAACgkQLSnu7YMC/p8UxhAArTP7S5Jor0148D6kDqFvJiBt
 ny+LTLOWC5/Nj70KgmhLxzuClg9784+mXWwi7Dp3uNpBbgC1OqUh3WuDw4YNommz
 qW+9xy7otBfEMn6slxRyla+o2l9kCrwWdA8e1gYHVjWxV6hlFiF7mWPwewqoW73+
 UDlesC0iuqctxKhXodPZn92DE6XJjJPCDvFHNj0ukuQ6K4U6jIZy6DHomp+Mcwhz
 0q907AKMOZOLm/ISUSwbACRf6UgvQO5frJItoA3vKVF88LvmbdnorCkUjz7A4VTV
 4sFnUtZ6PUWubFAhVEhlBl2FIgpKayZa0gdrRC/gpZKEhVP/C4SpHBPssyT7UU5o
 KX4zYy6sC1dkhlF5v1JEFVZFkOe+FC8QFsVPRQThkCAXEv/aAkX1fHRVzE2LuD8M
 0jujPxw9lupuTyRVztT5bLhvSv4VwbEHqUAEYrNBKdgLGSWEpwaEr612QZ2al6jU
 wngtmeuV3waKVAmrEOa4j56mxk3gDiSD2pVuDiEKzhOheRIpWxhbw8pfUrVF0Ta6
 4y5n7f+J60i4k5oHp0kUeux9vlV1WbNJWTWwvL9wQHL28UZTp5EGz1ishp40slHh
 mvLOEdAUP6o76clFDaqzmzSw9lR18qrRsyyiKDyLo8WwTjeBu0zVCdaaRt84QS+g
 umeN61KbYXYUxVazdIg=
 =hh9s
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.153. Poul-Henning Kamp <phk@FreeBSD.org>

 pub  1024R/0358FCBD 1995-08-01 Poul-Henning Kamp <phk@FreeBSD.org>
      Key fingerprint = A3 F3 88 28 2F 9B 99 A2  49 F4 E2 FA 5A 78 8B 3E

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQCNAzAdpMIAAAEEALHDgrFUwhZtb7PbXg3upELoDVEUPFRwnmpJH1rRqyROUGcI
 ooVe7u+FQlIs5OsXK8ECs/5Wpe2UrZSzHvjwBYOND5H42YtI5UULZLRCo5bFfTVA
 K9Rpo5icfTsYihrzU2nmnycwFMk+jYXyT/ZDYWDP/BM9iLjj0x9/qQgDWPy9AAUR
 tCNQb3VsLUhlbm5pbmcgS2FtcCA8cGhrQEZyZWVCU0Qub3JnPokAlQMFEDDmryQA
 8tkJ67sbQQEBPdsEALCj6v1OBuJLLJTlxmmrkqAZPVzt5QdeO3Eqa2tcPWcU0nqP
 vHYMzZcZ7oFg58NZsWrhSQQDIB5e+K65Q/h6dC7W/aDskZd64jxtEznX2kt0/MOr
 8OdsDis1K2f9KQftrAx81KmVwW4Tqtzl7NWTDXt44fMOtibCwVq8v2DFkTJyiD8D
 BRA0Pu7GCKyxtqPXKpQRAhhSAJ9Z/WCnDtISX4FU9bF/5QKEvmvtGgCgsKyY1mk7
 0ow22bUmdvPOz9zJxQOJAHUDBRAwIIYjCn10cvEMm80BAVrEAv9+1GycVrDVEVEX
 cNTQ3CX+HiZKNXsNWruNcrU2+/djtR4l069ZysWvx14NPtnefRxspzlUH6CrRMNg
 R2pGJTUDZNZs58RsYv+BdHE4V/oZifP1fMI7ZuW0NIRjHhUIweGJAJUDBRAxSx5c
 H3+pCANY/L0BAY+TA/9YQPISXYaS+5r0I60wCJ+i3a9PC69Zak2ikgTHQi97LhpV
 tEsP3SAYInDw4YMS2oU9w1XxoiLLd9hUpcZlmO8Ip3vNF+E2ZCfR4sNzKarY5fdo
 +sxzatGWRPgnHjbm6RHWCw6qJACDD3VpaFjx2XD8QrOTyiObnbHhWBdoEAIyNohG
 BBARAgAGBQI5rUlcAAoJECykWk8fgFSoTiIAoJa59BqzeoS1ytJdiFLzK6GjEl+c
 AJ9AErDKZKYLaAYa7LSLzt78zlN4+YkAlQMFEDF+jX1rWmeNgbKneQEBCrID/i/r
 i8/eXUXRJp2fqJqzvrWGTP9Ix1O4vMguah9IILijgpYyOJYkezZKijjVCVmLX7Ew
 fNXfYkqLAWUa08eov4QfJfJDgfe+Z/3/UoX7RcJoy2AjTBZQzOI9JMkrzFdtFGYw
 Mr/QXhOdVVpSGeZ/6Hkrs7pd2Z6MNNrRf81ZyJyYiQCVAwUQNBDRpnW7bjh2o/ex
 AQG7ggP+NcUV4mCzYx1MM05kz8Vt8OEjirEBthSypLf5FrXrJ3xZ38CNX4gckTY2
 iYVaXxStSMIaKdeLDM+ArU58UmtL06DXBAu8CXRfzgEDwxM/0FCvjDvoj9FuSyBR
 KtUIg7wwnCXJ2NI+hxYYF5eVWNtnFfPK4mTsf5Mb7O4jkG4Fw0iJAJUDBRAzBiva
 s1pi61mfMj0BAeIhA/9fG0FYVdoFGBUsSFE2lLTth1T4uxkaUs5l6E30vhSckUdB
 A806kx7LaAXtj3loE7Dn/XFLm+VCnCZEUKe1ayb+Cp3Mrqu6V+vWvkDL3gs7lMAL
 q5w27f3pji+jVPIPVJOdELjroqW+a1C0C0UaBeU5FYsv1REvNxEV3WEPTJd31okA
 lQMFEDjGXEvKbyuD/AwC1QEBMcwD+wWwOmzXE7wpIEZ1p5KsRiVBQ4F1VEo4LviQ
 kE0jUx8/i0/Y+kRpb3sZc+yh84qYA9vrRe8IDqc1a66ZvGUPZOsfiICpJoH4ftPz
 8xMLgyfHZrSR+wICStXNAKok8Oq6a56+Vxjh7wpNDoObN5XfYyAr23yNoPh07pP7
 dXNRfGKiiQCVAwUQMTlDoO9huekR1Y7VAQGy+AP/Rzp+UGtJavbSiPx5EnXOXxkA
 /+ulXQgQG9vdkWwewkvxDNOzHW3KkUWCGtPtIMENznbFj3QlYB+USIaf1ogvlD5E
 dXGPDfTINpE8CX2WXzajfgYFpYETDzduwjoWDZfEN9zZfQqQS62VgAReOIz3k9BL
 708z/+WUO0++RLGCmImJAJUDBRAxfJXn9RVb+45ULV0BAXJ8A/9K6NT6VLZZC5q3
 g7bBk5DWuzBS3oK2Ebww6xzsD2R9edltoz1J3GPngK0CWpHh4kw5iTaRWoC2YJYR
 NG6icnGvlMAl1/urqQHJVhxATINm8oljDKsj1RBJ6VKBzNbCJIHTVpX0AJoqUQX2
 Idi8goFr0fAm7cD2CBb1JhoAdzEfO4g/AwUQNX+5mPxGGtR+MqsrEQI2aQCgmSzO
 SfQxEtKMshB0VJCgAi9exqgAoNosC8C/0kFMiGI8djBrxiQ1O2vpiQCVAwUQOa+C
 q6WQ7KI7msylAQFqcQP/e5kOmx+qu99qwEkrwpTWzpfpgGl1BuEsKDIRk6VOmo7o
 egtd8kzRjL+S2OUgUWA9l6i4uUXsTJWIDzqPOc8i2vI/OfelnKIGu/uTZ/A2Az8V
 7+6hhPhIZ+JHZ3ep5rTd++4+SyCFLXWiCl8NmQwdhmJpsWUtHavEsC3NBgW+5rOI
 RgQQEQIABgUCOe5/HwAKCRAj54bpvu2UbkMWAKCLrzhdCCmJoA1/ljX7HbXDuf3u
 cACgrwhPV6ZGrKEn1Hkl7Z88ICwAGXSJAJUDBRA57n6ATVYoIXkFDBEBAficA/4s
 HQMoCC4q6OHVor7iZt33ypvjvaKRiS58A/SgAc0Y8P60GqpuAEcLUl07V5/hAcwW
 WKGGX1LwBmRxvhbNn2tHUVAj3oB7UM0KSUa7KvltcaqXFYIyjYkAROkgm7oTWMaY
 vN5H6JucyOJdlkqzvAACtagXntUEwxJ4ptHxwpylJohGBBARAgAGBQI57nf5AAoJ
 EF1SHIzmsVAWoJgAnR/1FVW1EE7BnHJDt/GpIR5mq11kAJ9RmTUUaedL+I/xCn8g
 OViHwwcea4hGBBARAgAGBQI57oQcAAoJECAVMdWEXf7dOzsAnApDRHpSZZwB7DbE
 03ZPUqZUaCV4AJ9pGurLhFjYo0jVR+CH1MrqkjxVWw==
 =GwRf
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.154. Sergey Kandaurov <pluknet@FreeBSD.org>

 pub   2048R/10607419 2010-10-04
       Key fingerprint = 020B EC25 7E1F 8BC5 C42C  513B 3F4E 97BA 1060 7419
 uid                  Sergey Kandaurov (freebsd) <pluknet@freebsd.org>
 uid                  Sergey Kandaurov <pluknet@gmail.com>
 sub   2048R/5711F73B 2010-10-04

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEyp1pcBCAC1kRi74jv2nnEhN+nPwBiru4aEDeR+REKtg96ZF5kocDbHsDWD
 tmU84sfsPEFCXj12qEPRzucS4VwIjWND6EC0rYPBHXlFDzHnZLBXyIKYcKIU5eHA
 1tA+41J9ZaRX4268ODvLIf9gz0hAh2suQ3v3dbX8dnec7ZHUJEOH9zg1BTFoZ2jj
 Xv9PHI5aPsNA9qMcgQpVWDayw3mp5/guyw0lN1SBIQqm/lC7L7qcYexHxkq2+LQf
 fy3pPQxkAVbk8PHyRkGrJnC2CLf9ixqtXRLNmNiHa72at9Js/xLsYcc5aVX056wh
 9nxghZuRzg3gtLpDV0Ae3BQUU9/ljdKmjkfpABEBAAG0JFNlcmdleSBLYW5kYXVy
 b3YgPHBsdWtuZXRAZ21haWwuY29tPokBOAQTAQIAIgUCTKnWlwIbAwYLCQgHAwIG
 FQgCCQoLBBYCAwECHgECF4AACgkQP06XuhBgdBmo9AgAtPBg2HTHzJN9qrhMgzKL
 g3VbZ2+pBNMTzpGjcMJTiCn6Ch9YmIX9IAknQk5lgQuQAliGEBNIARb3An8JtjPr
 NbpHyRLXwjLL1aIUnvUmVjJfCKy3W3GFUiK9e85kUH/wFBjX+G+YPHho1kGvb5N9
 yAG9SbzBl8sfYyR9sblDwMsST1SNRxOF/LClKcFD2VrgTvMcQ6+jS74F/cQEIqxw
 vbd1pUEdd13EfezwSg0dO7ZPmd146wLXIJzJ9cvijOqNYZRsuEYJemCT8CZu/0B4
 /PQBozdKZWOWkGctxw1WUT2yQaL/3rIby8hPzp9d7BhB6Sqv4I9kpkx+iRrv7xrf
 /7QwU2VyZ2V5IEthbmRhdXJvdiAoZnJlZWJzZCkgPHBsdWtuZXRAZnJlZWJzZC5v
 cmc+iQE4BBMBAgAiBQJMqeGtAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAK
 CRA/Tpe6EGB0GVy1B/9rz6f/CMS2dnq2dBudDPIX9Boz7FLf21QG3deapV02Rjv8
 WuSWO/dhanDHVvFRNe8DmxfNgwvNr+ODLc3nTh3PGUVJdQ6VIJnMuIOLroc/w+TI
 CgeEqe6a3sC0GJuJU+paDmh4rOciyfAvzwhDc6qBiwOIjcwjOLOWSjBlJT8CS1jk
 TpOt3akFUTG9vD/svjSWQdreTL9DicwmefNS2+oWBuLXN5dqQB9FDl83+G7IenX7
 it5E9/tvcVVi7OqdUwGeV2eDoQFFrEzzII5KLwt3CwzpSEgCmu81t8hJHbbuTbqK
 ZcOx3d7Lq2h/td6WDkHXbF0vNSUboSRX/uN0m2A+uQENBEyp1pcBCADpKKpK8I/7
 GlsNAntUUFZqwXniLdRxJUmGLh0ZNKnagGYjz1v5kunomAy4fyIPTqHKUWP8c9E1
 pV6r5CD2JupM6lHv7INCcSaYNVBOTKTEe2i6L8GHzhCLGWQLU9JRHuRPNesDwo2b
 0zpuXtsS1DEg3cpp5IVCCFNV9HW6bN93jL1+HDI64aisiRdAXKiol+w6t5Ev70YM
 VvQK/YF3aBWw1HETJkPwoondfZ4XMpMlkbk5MjJOS76T65uGQYAuhcd6PN/J/mtH
 KnS2waj7q1dvDBeXaTAwKm/Oeew3s8ggcz3JDQ/EcB48xfi1k4vQWc3j6UteYrqU
 PqIKoCV/bT7RABEBAAGJAR8EGAECAAkFAkyp1pcCGwwACgkQP06XuhBgdBnTzQf+
 PFVidYjiACW+9CsL/zoA1QqPm2IhTBDp9S6GrfSruEFNfbthEOuSuAX7VqZPT2GG
 S1aRaY9LduOGrzdtvRfLvnSsz31wjwG2Rkb6OUbX/jzPaL/KYikt++VCdR9T/S4W
 B1QeLzybuQWQQMnDyb+kMpxmF7lHkhJgQhzElhEuZlkYhiALLS2AkXOQi3tmBe7r
 sF5/J4jcjI4O45jx/Mdhdx4I4Fn5pN4TXQjBC0kFOaldy7l6WVk/yZzKNJjBoASv
 JMyuua8AiGc8fvez9PeSIqkrNJcrCcDaLxpmXzMjxbwKgulfBk4NY5YXKC9/Vi1D
 ZHTrB5rRodo5ARlH/LF9IQ==
 =RXWt
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.155. Coleman Kane <cokane@FreeBSD.org>

 pub   1024D/C5DAB797 2007-07-22
       Key fingerprint = FC09 F326 4318 E714 DE45  6CB0 70C4 B141 C5DA B797
 uid                  Coleman Kane (Personal PGP Key) <cokane@cokane.org>
 uid                  Coleman Kane (Personal PGP Key) <cokane@FreeBSD.org>
 sub   2048g/5C680129 2007-07-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEaj6Z4RBADnHGSN+HpgYx4kwj2c//kuW91OOYhYlstDCeVTlNc/7YpbgF3T
 KQKBWHu7uqygI7IeboCuCltP7D+PcXTVdBlh6X4aiwV0XSBCAF4ZngCb56OsSBYd
 MPjygHV3TH2TKe4PGqH+MZ3umogB3TZVMLpz4S0WyxXjUxLm5tYn7rOCCwCghTRd
 00JiGg0u59cT1/GiD2KYE40D/03DKCm4IvMRFsxc3IGhXQc3rQJVhBBAxnnzBA+s
 R3i0xKzGqBslEUG+AxUMFjohjQgTWjFRa1PTFgHih95Z1lR0/oO5teyDfxjeAPA5
 2hUoB3PF5NUFeMWXPCoSyb48uswJ5CCeX/IA5lVO891+jQh1LHIFQDa/rB6zeYzQ
 HaSXBAC3RheXdRaEFGt2JkNqAZxEQVtiWe5tebdm2oh1RaIfMQ+U1p4X9EBQQjGq
 6JeeUsO56HXECEgCyk46fgo2xNwIXqYi42sQlIGn8JDBwOLyjD4iJpz2uxC2NO9J
 GKUOMdsdydUpfdkF7tWu1rGXXmzGcUUkHXgKsF3jf739FyGAubQzQ29sZW1hbiBL
 YW5lIChQZXJzb25hbCBQR1AgS2V5KSA8Y29rYW5lQGNva2FuZS5vcmc+iGMEExEC
 ACMCGyMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAUCRqPskwIZAQAKCRBwxLFBxdq3
 l7aXAJ9829PUx9ST75k3L6/nfkejftuUFwCeN5vqGr5uZlkCQr+Bx45HbcyFQp+0
 NENvbGVtYW4gS2FuZSAoUGVyc29uYWwgUEdQIEtleSkgPGNva2FuZUBGcmVlQlNE
 Lm9yZz6IYAQTEQIAIAUCRqPstQIbIwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJ
 EHDEsUHF2reXPTgAn2uPDHMfAoaLp+Eg2FfIuMlVNgfEAJ9xBcFz8kLTrAbKnthL
 S0yBqAUrv7kCDQRGo+meEAgA22OriKy6l+mvGIqbwk67Yz2zcVtHx8Jq8uuyt4Ue
 JfuK9H8rDOz783oF3++ywf07xqtl70rH+KHSNfVyXUetVXfBUZfo5bTwxokQWE54
 eJukJyZeDYXpaJ8ro083lkHsqE9vtTSwJfU4rqRpu67nC80WSkke0t/35sHKqwJI
 WXlHniGD3dJt+ZTy6hxzcx3WjlNDNUEq6iSl28XNzWdvpKIrah/ksO5O2akmaZcB
 SXtHthWdX58hOCHBhS1QQSKvThL3VlFtsi7EhW4/rNekDomypLxHGErprjMGV3GF
 509kI2vn7NoA1G4sxrESZK9sNIC+KmdWO0MQ4NYhB0NAnwADBQf/XFiDa83fYJUN
 LBqGGgeOPE+pyBS6gVrw6Kz62nFFgfW9hHtYgItzS4XrDHCc8TCSG4zOBqBY4Qvh
 HgJ1Fa8rppbMUMI32egtfY0/cu8NVWtHlYp9aQp5tM/0zPu5RaRpQxafs9e5j4gf
 fd6mY3ro3vJjZ6UczORKFBHxLDg/F6UCeOZsv8Ii72YDqzZEFdBUMJH7ArHFKndd
 ZxkN7+iGXZorHnTJj8mXSDYmvyaI+Gfn/dea9RDp9h75257cHhnbaDd4ZvlUK7JQ
 8HFb6jM0LsadfDuSSMLUYFozqeG1MVCJgn/Rv0i4FMlI0QK/6r7njvvfR6p4mLl5
 n9r0NOG11YhJBBgRAgAJBQJGo+meAhsMAAoJEHDEsUHF2reXJO0AnitUss1PV58K
 ++igcU+jU/EAsjbNAJkBlxLkkDzmxfWATLWri1+qzA5WDA==
 =L430
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.156. Takenori KATO <kato@FreeBSD.org>

 pub   4096R/3CF9ACE7 2012-10-02
       Key fingerprint = 5B72 AEF9 B2F9 069D 54FE  CF60 444F 91C8 3CF9 ACE7
 uid                  KATO Takenori <kato@FreeBSD.org>
 uid                  KATO Takenori <kato@nendai.nagoya-u.ac.jp>
 sub   4096R/1C593356 2012-10-02

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBFBqmsMBEAC90DnVvsY6rkCOX0qBI41V5vtTmI/dAJ2bdyHoehdXYDTmMr+l
 EhbiNNCk2UGvrfeQBhC4AbVrDb6CPXvM3A+WJHZZb2CHQWva5281fZorQ8oT54UR
 cJirR56jz9VJeBALVV4SkyRVC1YN4xPbscb0K764jVNad2m/vJbrAYJ/ma8UQrfj
 EsdTjcXJPzTJkvpJt29nGWG4rDbcsboZ+KIjDkWLVG4JJ6VhHFH2wAriseZtgpx5
 d6p6qABKqvB//pTEF25eQgM0fViH/y+ZSjfwG1A0S1DjdowJD4DHpknryyfGctFe
 cF/c2G7NH0BqA7xQja2+sSR/9WoPbd6UiM/RBUdsUr838ubgRcF0omWgCKHlHCcH
 YNbh2BAITlutH2H0xgLavjS2MWbwuekAeHrvgg2epmg9so41LrMVqDuj+myML6ch
 TluMqAq/NPZmG77A1K50DIEwv5+zarP8LppfJJDs74Y+VhAq4rrwjyMnRFLZiZ0/
 DwjTdW9NC1QlHI9SVHb7P3Qwm1zvY6b6RWoAbh3v3y2nvLhT0fQPVQcuahlnLFyW
 AstSjEqWAf1Sji6A83sPdf8sqUHoHaT5INFrAyKhbigwNkHD7tn4KAgKiQP5h2Hd
 d5aWrlSW4naam3ezVc3w/R9AIEm18h10feX5U6BydasJ1P4BJOcN+fjYEQARAQAB
 tCpLQVRPIFRha2Vub3JpIDxrYXRvQG5lbmRhaS5uYWdveWEtdS5hYy5qcD6JAjgE
 EwECACICGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheABQJQaptzAAoJEERPkcg8
 +azng9YP/AzK6MYRv9VzDCZ3rLmVPDlSN8IpaGtuWsOvqLMSuGUPCsHMZYA4vYni
 DJFWINabOtwyzW0ol9Sosnx+/mL3EeqARkVbIN4J8zFe+1FZk0tFs+72Sai0OF8c
 o9i16GPhdLaLC5PvPhcVpxteG2StmPvi4zJ8ALCJ/sUODXrmeWLDXG4jwmx14fIz
 52T+Jw30hXwf2j5XDeP87ApPPAueAu2WuK//Ez2zl/A7AExuP+iqYkmgqBf6QDxB
 c57UAHg6p70x8lgqku/QLdIb4O2CgkG38LySSM9epfXOFApd3hPFWZMKrPp9wbak
 0PlLmf/OmcmRMBRF5YNF/9Qax/Xs1zpAvBiLgbXpEjOhlA6wrZPGD/Dcf4EbxJYP
 2Er5eddT2ymDs7W8dZXmoESP+EzGOwzx3fj+x/yssQ8j2p3Kwd35+LUFfIVBnT3U
 QBper1r3fjmwRa90DZ6JWSKMx2WylJWSKTevPpuj3CtYbfBlWQWBbr/rqC25FfmB
 EeK7tb0GpNk3E2S5pGFBS3SzpmsG0LPiyawYqcKKmyu1QCHqfQzdv2y7XfwJntZS
 53+TRnybZifAPZtmoHzWjTFC5E0h15CUjN9Wh2n23MIkcXcELjHUF/QIs8ZO5xTd
 EaSM9UY89PnL62lEH3Bd8HYiFvYtwIenzULSuV797rsI/nrpfOkWtCBLQVRPIFRh
 a2Vub3JpIDxrYXRvQEZyZWVCU0Qub3JnPokCOAQTAQIAIgIbAwYLCQgHAwIGFQgC
 CQoLBBYCAwECHgECF4AFAlBqm3YACgkQRE+RyDz5rOdSxg/9Fw3Pf2rYwxLS13ro
 2Ssh1MGhYTsGAgLmMgpdtEWZefXI1C6bh7yVAd/yb8E2rP3dI1GgVlKHOW+2y6Qd
 ii5DVT/mcQtAx0YYyXTmX47QijvU4FYILwKugq7ck0ifuocON459sRgP0BmeAy3d
 ufGZELJv/aTbLlgBH9Ig/oV2+t0yWl6RhpQwcqf5WgUH6UYbrdg615gOn/egPRav
 u476WUuKDHJWgLppa+LYffO3fx9Di3MMJ8r/lF4aRyFUsnJ7yAbbSpHb4a2+qEMN
 O0IH76VRQf7HbkBAr7wsYUOD7AOFJMquPXD2zdv+cf8qC5ePd2CNjgKgogkxJxB7
 oyxhcKQdmaZJrKY24rIjSqrc/yYV1ibqGM+5oym8lSp231t/F7KwIMWybIyXZK6q
 VIRxeQ6M7bMGTSE7qx1RyfW/qpW86cNkFC3qk+KPJNF3hnD20bAFygZJLqVD+FLI
 4iQNS0zk4DZJqzgnDde9961ErXpCFr/UZeorM/ikTzGOEi11j6SgxZD8zenQCE8L
 dxSDVIoAIiJYANsQeENhJYlLz/42IfECT5WHYibG3OMUbVGpOM2lWz4UV71vwaCj
 Q9uTUfgi5CL/49GmH1zbpobVs+ug/P4xkS3RNYjk6dGz3AxAjeKtSzCfoL60q0EW
 D4lEnOesaTBIUlF+uuJHVs7MjJ65Ag0EUGqawwEQANEtPnmoB3ESxmMjtirpPhQX
 IOoghAictNWkYNj22y2Bu0vc2TjxWmcteCqTLlGfep8SOD26w7wi1TaR47qupglU
 H50XuTpT1GZFxsJnk2jqMDeYkmaQxVFJNdURc4G1yUdBnJ+t08ywchhhvsIYVxq6
 xQeaBId6Hm3MjVxxzpkW3EdTxl+R4chUP6YlpCTASj+W5XOjt+iXjgjYvFzoD1f7
 Ov3eAqzx5WCqhxsz6Z/7GcDaQSD3zduqVUpOFz1xe/RwXmawxbztv6A6tPZdn+jE
 IscyDMRQ4S7z45/JZo9dCAL9Dwx0ZYxnqE4KFGvUmSkEpEu7Wv34IiMxm18mGgFO
 DFYrprNSbIpf4Ag9WGhQO4/vJ/0gdcNPIva9WzJczwq3lDC45zu/b/ovv4r74isb
 rgBlUpvc/0R7vaXdJ+zIYFanHa+OT9qv2V5UiUgxhpGQaaohh4b3BNqNmHSVYzyw
 JsQmg5RxaPFouyOMUf/QNeByRmXW/MrAhM/jbUA2/p6AYV0YK8Jjwx2NzRAKjVIq
 XJNd0Ux+XLrV7kjRAR4sN/3/mWTOTPfhfuC+zuqN3inbhkISO0DBa9a6Afh871ON
 gvlTWuHLQtjZlAhKBamKh+RvN0xIvYhE96LfgMgIFn3ooscksiArS0SgEcygHYRH
 CMbAPBroFjodIlhiTM1tABEBAAGJAh8EGAECAAkFAlBqmsMCGwwACgkQRE+RyDz5
 rOfoFhAAurRAxoVkhBCrTk1Zx75q6MP9zR4IvazkShRlemE1uXMtymJiY/gcRwIP
 TJyYKuSxWookp0bzaiJG0nts6y76F7jculvf0GQrOyGgGqA3EMVT6Rh9ZZHTfvGe
 ZIjZeKje4Xr02WjxzG8JJCLjZw2hM7raeYmTGK/4WUgxq36qBdT5WI1d3ok6CN2b
 KgZHvkBkvQrRMxnXCunBHqHcPS+V/JXngorfjnABWlOeHwyL41pLvxo0PqCcFO0X
 aW+1m94LXdbIWCPCaXvDlf+1+kwIhx+hG5tiPRAerZrkhoDqfxltOePhKhaYSxNh
 iQfGwPukKCDcZaxi6Atz4MySFSCUYeV03n/mfKoJ2TpFqebkhIukI/CEqNe8IaHU
 21YD+X3b7HlPGkfReLCFo+C8Pq07XgDupTK0846szVR+VVPDnXTW1O4LjeegXU+J
 8lmBYlHhEzNw6twujNIwdkRIJlLIbSP1KU1e05vizf0h75T8ZpeZPgSojF2ujk9x
 UUjE0FKoc2bZmWdiPpoQCezAkY3TZ8/nByyZK66VC39Dn06nmNYvJjWTard5wRUP
 8GY6UEtAU6wvthrPo40UwxTcTO8C8kzMr44DlPwwIWFYrNcpQqYjinCgyG/Xulpu
 FpvjPC8fF6emgWE1QyRgZqcjBdFpOqlBQH8nyjchmfhodkiS+EA=
 =jQtb
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.157. Josef Karthauser <joe@FreeBSD.org>

 pub  1024D/E6B15016 2000-10-19 Josef Karthauser <joe@FreeBSD.org>
      Key fingerprint = 7266 8EAF 82C2 D439 5642  AC26 5D52 1C8C E6B1 5016
 uid                            Josef Karthauser <joe@tao.org.uk>
 uid                            Josef Karthauser <joe@uk.FreeBSD.org>
 uid                            [revoked] Josef Karthauser <josef@bsdi.com>
 uid                            [revoked] Josef Karthauser <joe@pavilion.net>
 sub  2048g/1178B692 2000-10-19

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 6534 characters]
 p5J1gj4xWykgTuA=
 =U6zf
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.158. Vinod Kashyap <vkashyap@FreeBSD.org>

 pub  1024R/04FCCDD3 2004-02-19 Vinod Kashyap (gnupg key) <vkashyap@freebsd.org>
      Key fingerprint = 9B83 0B55 604F E491 B7D2  759D DF92 DAA0 04FC CDD3

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mIsEQDQwdAEEANxnThVC8GNO9VXTjWFhJh7XgMLHf9jDd0B1804WUqc3c76r8y/k
 AXZ8e3kNH1rpa+VJ0rYQnurQg5BeFQny8TzU6PC9QSdqNKSCvhai6B+w3t15sKJK
 nGZ7DwyoyuShMFNMVF250KS7dEZnYy8yrtopCIWJAWzuzuQQtmUYk4B5AAYptDBW
 aW5vZCBLYXNoeWFwIChnbnVwZyBrZXkpIDx2a2FzaHlhcEBmcmVlYnNkLm9yZz6I
 tAQTAQIAHgUCQDQwdAIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRDfktqgBPzN
 031cA/9ZuwCRbYhTHWzOhQuT8dm7Bby0wEq+KzkULXd/ExgxCu/54t9M7csD378X
 /Fg2erLP2J8cYIcVXmdtIJO8AwZRw5GgmVP+h1sEY+KT8jiJNlX2hB/9qCmng3FY
 ItLBY2t7XVmTPMw8BLANE7PJ1LKT/OoUHEk0OjK53KKGNU2oUA==
 =VzLE
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.159. Kris Kennaway <kris@FreeBSD.org>

 pub  1024D/68E840A5 2000-01-14 Kris Kennaway <kris@citusc.usc.edu>
      Key fingerprint = E65D 0E7D 7E16 B212 1BD6  39EE 5ABC B405 68E8 40A5
 uid                            Kris Kennaway <kris@FreeBSD.org>
 uid                            Kris Kennaway <kris@obsecurity.org>
 sub  2048g/03A41C45 2000-01-14 [expires: 2006-01-14]

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 4356 characters]
 iPF6/kmr9BBQtr2aUQCfb2ycB69cTi+09jXD31k8PffbIis=
 =nTL1
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.160. Giorgos Keramidas <keramida@FreeBSD.org>

 pub   1024D/318603B6 2001-09-21
       Key fingerprint = C1EB 0653 DB8B A557 3829  00F9 D60F 941A 3186 03B6
 uid                  Giorgos Keramidas <keramida@FreeBSD.org>
 uid                  Giorgos Keramidas <keramida@ceid.upatras.gr>
 uid                  Giorgos Keramidas <keramida@hellug.gr>
 uid                  Giorgos Keramidas <keramida@linux.gr>
 uid                  Giorgos Keramidas <gkeramidas@gmail.com>
 sub   1024g/50FDBAD1 2001-09-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 18018 characters]
 rkbWaRVzAJ4oA62xKNbHfUJWJOrlny+YSCPRpg==
 =PK2k
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.161. Max Khon <fjoe@FreeBSD.org>

 pub   1024D/6B87E212 2009-02-17
       Key fingerprint = 124D EC6C 6365 D41A 497A  9C3E FCF3 8708 6B87 E212
 uid                  Max Khon <fjoe@FreeBSD.org>
 uid                  Max Khon <fjoe@samodelkin.net>
 sub   2048g/CB71491D 2009-02-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEmbEFERBACe5xJF2u+R6020qrAb42ZcqdTUFDepqVWI/qrxXoEpC+fxAD4x
 9s8zilNIZkG6NVpEr7swAWG3+XMSqM5vdtGDj09JFsGEuREB05JTzIBtqGGKWuEn
 Mhg/3K1ZxPPwAokm0Sr3kiGk0Q0O+dTesc1kq6xjuDYC1CrLKwVewp8GqwCg2irJ
 MsYAfODJFAXdK37hG9T5TB0D/2CqorXSukQ2L4U7aFOYlWtDnY61c+gLC9JKJSD1
 TfNTjlJqfu7/1LqVglFZ54Pp6mXYSheq1N853jBFFKAfByiTvD8BFbUsCue/aJHc
 W+STjM8J9fY+oyi/OMZdgdseQ9fn4Y87sK9As/JsE/z4V+kn0V7+x2mqTJwqsSNe
 1JyPBACeQ+yEVchDkoyK+lPgjHYQIqrPbu4SrRalR/WkAwPE95b3j8RHNsX9PL6T
 J3yDxXTOxQgfoCVhS0KPgLoLKTfRf3CvSZYduFkWJgeCtoKaYn9nBzcnlnCjrGvh
 1bplgiOX/4x07aHEYgVRan1Wed2pPjpT7WWy6NDC0VP2HmvpN7QeTWF4IEtob24g
 PGZqb2VAc2Ftb2RlbGtpbi5uZXQ+iGAEExECACAFAkmbEFECGwMGCwkIBwMCBBUC
 CAMEFgIDAQIeAQIXgAAKCRD884cIa4fiEr9CAKCYt+Yc1AiBqAkz1fwDxLC6Kim4
 LQCfXGLJOc7rvsR7lNT8ftexwa36dq+0G01heCBLaG9uIDxmam9lQEZyZWVCU0Qu
 b3JnPohgBBMRAgAgBQJJmxB0AhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQ
 /POHCGuH4hLIcgCfZ8MJjAT+wFB5DfbtNELP72xoTqoAoNXtUquEkBo3pkt2M089
 xPqKnBDvuQINBEmbEFEQCAD49pzUGeoNT6HqnHx56l/+eqMljCm9OMUpt3CeNU5j
 UisWVb4yv83VP8cliLDYw5pWCm4TTSbsG+OdYrwm2l+lIVIUeST0XMxK4VeoNTJF
 DavUs2r6XS0Lspr60Ynnp8z8bA5/O/C82DB9AGo4dpew6ybQoXRyY3O1JAWBucuh
 Y/ti5hGtKT/n82XHYtD/Z8BcHN6DVEsU+tn6FWeKu1yZqen98ZN/KOO0GhBAgTn0
 AyxVYC7sbsul8OHBgNKhUvukIBIHCjZWPYTqJwrwKwlrGLENiUd0sgcugRP7sEEI
 iGdqT3/uy+IcaKP8iHPWUD3lrqV9d74JXjFu7GZoMId3AAMFB/9MT4CxcJGMBBs6
 +icdnFwHIGAxBkUXFCSgQsVr4OyhHx8Ac+WDIIeHLF83kd1PKG+ecAxhxwF+MlgG
 kU/Qk9pVwBJBM/Gs+hrwOQODsf5+sp3CcudICSzAXtzm1A01CQVfqQYCscZDQvW6
 ikJZspLLJkbHG+p103C6xsmcOM3qFJN3erQpwRfhqwvKSwH7/pjxijEc6tvTzj3X
 nW/rAUZIHlB4PzSlLZ4plFLgYMBt73ewlt6lKXmMrnhFwJtcA+2bIQd3dAWo3Eba
 feGK5hqHATowvVgLjx+ihE4TdpA7kXyfZ+nP2bGFaCR8JnWVtKZkTqaWrU9xRPpB
 3YwQNOtBiEkEGBECAAkFAkmbEFECGwwACgkQ/POHCGuH4hLFaQCfbr9tE8O9EUjf
 Mre0CBDDd2Ck2sIAnigLJE2wP8hPmK9bSvzEcd1qKpnT
 =3qdH
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.162. Manolis Kiagias <manolis@FreeBSD.org>

 pub   1024D/6E0FB494 2006-08-22
       Key fingerprint = F820 5AAF 7112 2CDD 23D8  3BDF 67F3 311A 6E0F B494
 uid                  Manolis Kiagias <manolis@FreeBSD.org>
 uid                  Manolis Kiagias <sonicy@otenet.gr>
 uid                  Manolis Kiagias (A.K.A. sonic, sonicy, sonic2000gr) <sonic@diktia.dyndns.org>
 sub   2048g/EB94B411 2006-08-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBETrHk0RBADYhjqulMVEFFnTMQcFbUpNad/uZ589qbTFE0wzbEy1EOQZfcCW
 p1m6gq5e/aijOC5cj7bg1OBPSiDZWXT2/Y22eiEYK0ghpTrb0Y69xhLtZI5om5eD
 HmdNhytM48cyhvc7gqm3hBNtLWVNskcHRQU7rd/S1cjQHS5LnHgpPgnVrwCghFub
 wCn4j+jZtbwjuksX9TIreC8D/jlA2Q4CfoJuXTBkTCIXwFSXWRg71VIP/Mv54JaN
 g778e5QxiEowNJ6OwYfbkOa491QEERGWxs1FI0WCrrc1OXJVCUau3/kiKpZYC/cW
 CiTEDIeEsw2AHKuOVWhkbbhtUTms57gBqQ2+9IHmkcmKcusw9I5mAiGLLfGLgfBC
 VpDrBACc8jLhV8kMmfW1x0QGYkQ0/k/rA8/nDo2bfe7+bXoGmGjFvUKiMJT7C54O
 nnMfTKWlOvSrc6HZ3ijKNMTL/NteI5TeBO7Cd24BzzwEnqyAx+2wI4WUSKcxmew7
 BcXQi1UYhim+bobn1ksQ/vlDDWBBqYyyh+l/h4m5S5lG5dXGebQiTWFub2xpcyBL
 aWFnaWFzIDxzb25pY3lAb3RlbmV0LmdyPohgBBMRAgAgBQJGX/+iAhsDBgsJCAcD
 AgQVAggDBBYCAwECHgECF4AACgkQZ/MxGm4PtJRMsACePa4SsmNDWV8DXv/oo5D7
 XJwoAlUAn2sO1W8dSzyt8dKcU4a9/8/7UGSniEYEEBECAAYFAkfmBh8ACgkQ1g+U
 GjGGA7YpWACfa0OiwJ498UvMtC7FO1IDaz1XCCUAnApZ6SbLcInAs8HiWc7MxwQy
 CYAmtE1NYW5vbGlzIEtpYWdpYXMgKEEuSy5BLiBzb25pYywgc29uaWN5LCBzb25p
 YzIwMDBncikgPHNvbmljQGRpa3RpYS5keW5kbnMub3JnPoheBBMRAgAeBQJE6x5N
 AhsDBgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEGfzMRpuD7SUA84An2lUyH/uT4WO
 6VnWvAojQn67VlI1AJ97ZjmCpjDzesP/ymHtsfLqZN7BqoheBBMRAgAeBQJE6x5N
 AhsDBgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEGfzMRpuD7SUA84An3wjXvFKgYi2
 3n0tI1s+fmhvW6+0AJ9tLgfRP8kfsJ5k5cIQiGp2+NbGsohGBBARAgAGBQJH5gYf
 AAoJENYPlBoxhgO2nnwAoLD6IlMVRwFPZwJUpdnaBvllZshiAKCImg/wIzfQ1OOg
 +325y5Ym+a0TWbQlTWFub2xpcyBLaWFnaWFzIDxtYW5vbGlzQEZyZWVCU0Qub3Jn
 PohgBBMRAgAgBQJIMxZ9AhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQZ/Mx
 Gm4PtJSDCgCZARCfhV4ITYxz5lOJrhpLlBmFjhsAnisPyWloawVqmZgq/k46r8Om
 IgyxuQINBETrHnEQCACMx04CokMkxgtf1Jt/XqIFL7PT+ieA5n4cSkUwMmFcHN/Z
 W26WjAbhOXYCgnMH58fZa8qD25ao5KGdYbL7t1Zbt01hbyQiZgh1J92jvSQ9cg1A
 q6cq465Wng9W16X1D4MNi97F37DEp5g0T4sFVBoAnApGU4kVpjfKcdb0IU//eQBJ
 KGuhG8BtHM8w2RmAvHV4Kyf3VROXh9Hsk+VRDmCQRO9D9ZZFC8zxG0KNcqtC3hym
 qlIgIpZVK/INqRocdLMhQxL2ULZpneGzHDTqVCmfSSeNfnFr9d5GLd7ROMBuYMTx
 KS7TQyAN/xC3RMKyZmFSliSpQFw/AOUnG9i0Z/nDAAMFB/wIarW6c1h+lgP+B6vn
 sRI9StPYzS9QYogCpK6jwEMsmAzRGUrWgw+uIyxujKqcIlWypELDzPZJ34sjoRYy
 CCIHfdyNhFAGiZXKmdjETFFsFEN+Q3c58mXHYnVg65taQU01ISpwRhL0wsG4uws6
 QFVzX6lgIwtoIEPUr7ptr8N0zLUI9BE3S077WuscEnQMUiRcY9XmnP3ms1tQviVa
 ShTRG0yhVAg77YH7/PAS5tflVD8RlY5B3QFX9gTEXz9vhfgIy3FxWppP3GiVkXsy
 29GMMW8/sq9k8cpJrBRyfEXGhR+FCpgT9Vixo60iWpIfF2RaxxI0yUu5XnjcyAQj
 tWO6iEkEGBECAAkFAkTrHnECGwwACgkQZ/MxGm4PtJTy8QCfY3IIv45shk4Um8ts
 x4PX/wzHxscAoIHPNcR8OKoESON7vCoepxdHTQ9n
 =3/vj
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.163. Jung-uk Kim <jkim@FreeBSD.org>

 pub   2048R/D932A1CE 2012-11-19
       Key fingerprint = 2202 B5FB 78B7 A303 4919  B7C7 25E9 69B1 D932 A1CE
 uid                  Jung-uk Kim <jkim@FreeBSD.org>
 sub   2048R/41858FC6 2012-11-19

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFCqm1kBCADdoV45Z2rQ1wOqE1kuEJah67+nsKRI13YlHvg1ILW72ny/Ku+p
 +CT7E0ZpIxYUwc1P6KmheCXq234wRjmSZ7/krDHdFezT2ZUiwRZlWnnDjEIpzxok
 m92W18Qi7o8CMTou3iTKtTVq/c2R5TcrcC8y/TACXPFABhpHNngmIbIrQGUsHifE
 YuJwiETr8s76HhdJwtZIWPGSjFW+Yl817e9X0Pa4A1/Y3bsA/KNmZW+CIkv/zy5k
 g8wpGomR+JrLdt+5MUziZA8gqCJycZa640RUGAF3QtdMHd2t1/ERQx/wje0LXBdD
 p+0fG5b9IUH/UBtT4OJr3WjNJr7Lufz2KElPABEBAAG0Hkp1bmctdWsgS2ltIDxq
 a2ltQEZyZWVCU0Qub3JnPokBOAQTAQIAIgUCUKqbWQIbAwYLCQgHAwIGFQgCCQoL
 BBYCAwECHgECF4AACgkQJelpsdkyoc6sbwf/YC84nBelpcachGrIhPV4DLcvCA4e
 T5e1G5WN6WWehpio7yMoM3G4TbTvrDpzrlFIIYxVKEyNRxfRLKeKIDjb4S/vzVbY
 nH8kuwYSlaVSmHOzu9fwfgiceElKMukVbQRTOBa3e8JLxoRG3A1TCo6AZXMY+PnN
 8UIWHbrwjyqOprXlZMC7BLyE5cu7oEHWpiwkXIuy3FJzfs06yzPSxH6DNGJSFZVk
 oHReo8fUBMs1Imn6w1DrDunepan88WAhRTQjM0kM0MrWI8oEnhtoYwWSm9FMpwK/
 mdcdxTMuak4+GqKgZiOj02vMzqRYYEijCrUx4dKsU6SGJ6SMNJd01ETu/YhGBBMR
 AgAGBQJQqpyZAAoJEJpWstW/ap1TgYcAoM4MdE4GFn11n3b0nrEA+LzYQgDlAJ9j
 0YnyI/0Il/zsgOuXLvt8+MeJSrkBDQRQqptZAQgApPIqqTzBVG6NukFvKzak0CrC
 4zrsRfUGskoYXQTqdeM+ajRdZ/zMebcFdut/RDwJhPMJ4UV8HfGGwhae0Yy/qWs2
 9NoNsmhicj+jrrSZLYsnjrnDqCjJ6wLHOEKhcPd9e/J3QdUlfI3tll+i1eqvr2xW
 kd+ct6IownrdvEhBzQsEQBgJYKy+pQ0KqAoJ9x5bnRN8dXzdq8o1FoVEN6zXNeGt
 n7TT9xMDMyJeItlvOOQyDr30Ne0vBBlPKJX7oiqEri/N4CeIDhUS6fd6qk9/ENwI
 jEThKJB1xJFzXWKpeZ9XsxPVSJn7KpBiiWYhh3Bphs+oitaTntpo3GYWfyzf+QAR
 AQABiQEfBBgBAgAJBQJQqptZAhsMAAoJECXpabHZMqHO6KkH/R1KWRN+t6zZRJ7h
 Xkf39iZ7DgentWwnSjKTUryPsUrr2IliFo/z2vef3dlV+RxoTIvK38Tj6hcN8KtS
 YSdCDuQrmGg6x6JzoO0RnFhZz753JqMVCeWnLKcUZXd2j3fanOAE/vvvYFFS5aq2
 KYb99fj3Cf6q9TkRIKpjD4/P1XBcOrmrJLbsWAqNhESCFlTgXdTF0hdsRsoelebw
 watpgAdCNH6aPbx7DjAyVI6HxNODbWrwFGOxRRJvmP5dyGOD+LuFNJtmjJKwrZK7
 ODRzrEZSW7T0Ghor/LWs8r7UDP9HWibxLF5K6Vsgh78ncA9PHxDsXGIMbgkynyfm
 ONweM/o=
 =cRAI
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.164. Zack Kirsch <zack@FreeBSD.org>

 pub  1024D/1A725562 2010-11-05 Zack Kirsch <zack@freebsd.org>
      Key fingerprint = A8CC AA5E FB47 A386 E757  A2B8 BDD2 0684 1A72 5562
 sub  1024g/6BFE2C06 2010-11-05

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEzUTbERBACySFcOGxN2msGiMvx9yhyQuklGdDgYKAzm/TNlImVQF6q3qhcb
 CJ6FaE99kFG5EmQXT8uCRSzb3/dIvNrhjTxrmT63kjs67mKnyHky3wP0NHCNSmZs
 b5Ky3h/SPOpb06S4zmhI7MGEm/xwBkQqc2YqfYTzRW83VNS9e/sTNzzwBwCguOPz
 Hr++4PFj0nr8I6r5HKMrfzcD/i5B4dhi25M/KlQsM2dh3r/z8KZ/79gmHKBJMrHg
 zI3sczQvXNo7jgaJwqgSInlfSoKKFyBw6Oqr0kP31E0K6ZKdrbpH982BSx5qtGe2
 xnDJNHrSOtgFqg3EW9DaYImdUmUOeW31evMwhjCYGSZF6iNVh6sahfZNFwmEgUXU
 +zBJA/0YeIPcQNdOapJ8H/ATRH7SLyMME+GIOx+85VCD2VBOq+WCSN8U7gJ/FFTn
 0NCVAVtPt/IAOMCZTob2as0C4w3Ho3YZTnl0jl1taYCRQnENQoVoT7cCqN4auypU
 0H2EvGPGUie+iZ4r+G2LLdrqPMiR5UTRcZuPk9O3VWXPpeJuoLQeWmFjayBLaXJz
 Y2ggPHphY2tAZnJlZWJzZC5vcmc+iF4EExECAB4FAkzUTbECGwMGCwkIBwMCAxUC
 AwMWAgECHgECF4AACgkQvdIGhBpyVWKvcwCfXGP1APXbQMWyacrwv4vfCjdTUpYA
 njYDgW1ok7AiabZjdT6APpGeqDKyuQENBEzUTbIQBACYKMjEfC82aby7YMRmNqCR
 IDU43ipbpRsUSz+TdHe61OYBL3eOFM5N4gp7tTmLisoW7AzFdiDgM9CUv9V/+ucO
 cM+Kmloqe65XWyCQchCISe5+8mMqFG617aDvQihHjho473IxlersxGS76WG7RDUn
 EP7gQeU/MzBcKi5Wk1ocOwADBQP/ZAgj3Oub0ntbBealsqEydjhysMMCOjOWJ75h
 lmBfH++UXiN3rFdzHzGlwLhTLY6I992YZM5fYPw/ta3w5Y2Cm8c3QqG+RcoyK+dH
 c9ce80Ddq1DV4F7RWNhjl3ej9kOneb0XhPdZ3FVDlc0P/88+5nL4bRLMuzp7g5rI
 ONhG5W+ISQQYEQIACQUCTNRNsgIbDAAKCRC90gaEGnJVYhriAJ0Y6dyrFOU4sLuR
 +KLw5h/8RgCNPwCfVayO/zLdURlB+BOpbmyxn6WnCLg=
 =sdsn
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.165. Jakub Klama <jceel@FreeBSD.org>

 pub   2048R/2AAEA67D 2011-09-27
       Key fingerprint = 40D6 097A 174F 511B 80EB  F3A3 0946 4193 2AAE A67D
 uid                  Jakub Klama <jceel@FreeBSD.org>
 sub   2048R/5291BC4D 2011-09-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE6BwQkBCACllA3LvksIethpx05Q3MwzG/bAcPBlclrl/tRlPtPGYqYlSfRc
 iVWKzOHq7k9+vVkaMmGwCyjj7/AE4vw2MPWCKODX2awW7xG7mcHWUZBYBcK4b+Wp
 2kpUrxyeZwSmzdqj3p4t9vSyY9njTNkRaJ3B1ozlEx+8vq3SgFHZFglHjuyyDi0R
 S8jMIXrHJb3mhnTABRh90vIj0eHHsuq75YwnWdBNyFU8t50zT/mshUCGlX7UWqEX
 WhsXXlqNqcFRW/AGpqwj8lHcLC7SyrNB8wu37L+duIqcmnTeT6aOjHc57Zle8Jdj
 EtUVtRoJ4txRnHLQM3B4sZ7ybP3sCTMnPzV/ABEBAAG0H0pha3ViIEtsYW1hIDxq
 Y2VlbEBGcmVlQlNELm9yZz6JATgEEwECACIFAk6BwQkCGwMGCwkIBwMCBhUIAgkK
 CwQWAgMBAh4BAheAAAoJEAlGQZMqrqZ9C9wH+gJzw7uvpz5VwJRN3buK4n46v8qU
 YFQrWwGzVO0R5QMrFcN6x7FzZupLFx3BOih1ak3UPVyJ3fcMCORAHU1QkCnwCBnm
 IUNRGPwC2WvD0hiBcBXpe6BRbshyeWkvqaclnSvcOWUZP58gmJnLZjCs5ke+se/T
 gZgSTTuN7mMFCG7MA4EXcvtIX8VWXWVyXufXFdBQnQkuLtboetYE692063YUIslK
 URw53loB9jonBkZ2lWPkN6Q0HF/34HrP/Bw4ZZnYZ/gzfFhoQdrRxCBaK7R2TrJ2
 kF2FSUtsCHJWgLq0cYygf4pCz7oYTt9x5IuubH4SDAjV65JgMic2RKkehE25AQ0E
 ToHBCQEIAMopCcGmuQPYBVgEcl1bEtwG87mJJzpTNBlOaE7JCUK7KSI+9qE5o5Tu
 jqFF39mu3Gr1kecsmtNNfCNW+ja9MtTatcnsMWMhZ5uNFUG3y2+Kotp1DEWTAZcM
 9TnX9IrnyLQvyLVJT5LI4qEcsAYHrLyJMrCu7c53M+RVigvimniKvW0yBZECxqYv
 nq/b0BSJovmtdXnO3wHLgz3dDcMnOAgGNsMpBztoRjiC5ssSCEfnCMLXVjmOa6Ji
 kRL740TTNK1HK00Wk0pfi5NEiTq+XTyFg0ekeMZIIIRQZHkFFA/ThJoEvvOb9pv5
 vkxifCjz0NFTecttnpVDSPWq77KYM7UAEQEAAYkBHwQYAQIACQUCToHBCQIbDAAK
 CRAJRkGTKq6mfXU6B/93a1Us9ESZfzwjg5kd2Rf9GtzJkEUlEKKJWkG7eK/6p3pr
 Qlrv2S4coikPCbasdxi4INbQbtDP44Hr6LNCRXB4VCeDbOA0W5H4hO4y1kWXbdTN
 X1pTXBPgj5kFe9lFQK9arHDgJsJaqKtDETlTmH/iI9xc51ZM5aeB4i963KixnPFy
 KFHjjAynTZSIMd8JXYul+kWpSSP5dckvW4G97PPoqbz4lsDUsgjf5Lg1lhThjlDz
 Jwm8yXz0fqORkB+wlEj1fsF5itmP+sG0YipncjFXGf/0ToggRucsSlDWBV7l9wBo
 HeAGT9bpY64DAhB5SLQBDphtBChiit4TJqkWVs/4
 =Rt4u
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.166. Andreas Klemm <andreas@FreeBSD.org>

 pub  1024D/6C6F6CBA 2001-01-06 Andreas Klemm <andreas.klemm@eu.didata.com>
      Key fingerprint = F028 D51A 0D42 DD67 4109  19A3 777A 3E94 6C6F 6CBA
 uid                            Andreas Klemm <andreas@klemm.gtn.com>
 uid                            Andreas Klemm <andreas@FreeBSD.org>
 uid                            Andreas Klemm <andreas@apsfilter.org>
 sub  2048g/FE23F866 2001-01-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDpXnNsRBACosqQnFwHgBcl+H2TXLWG/uAAdcZ3d4vlC9tKIPif/WovfOTuA
 CM5KMb1Of2uAQm5S6KpSCDSudZIZw2az3ka5ESQt82kgd/1Ue8FJDdPkGY1RZrEp
 Zq7VDPfENAM8NuYCXIdVYpd860tIfongUbpgHq9dA/bgoDDHXlaBQzUMNwCgurYO
 XH1FSx7vApyBFqaE9ZKglRED/jbd0UeQ8E2Y8jvoHgn9kDGjqgTxNerLK2g7gRgx
 o0U2do7kjKKWoUfij/x3RRpGUDzkB9xhibyoPQKuVim4NVNdoUoqjuSDnoDT+XtL
 B8bYGXAAROPXu1AT1r/P5k3kSHDExu1qfLEk9Sch7CKrVdNaZHsrknbmFPPmhdsf
 zz17A/oCfA5tXthQ4YOlmyjJXiMmiD/aX1fQovjayQDD/diNYQ/z3JUuaA01Nhw4
 02LDFCk0xO2T8wWIC8Ox9J7twKKBT9Ep1MpZw/mY7XlpTFP82ls15pNIshogjlX8
 23aBC+xrRda6SqTAnqsneyxGujSkS4sNubUWaQf0UUfcxZpA77QlQW5kcmVhcyBL
 bGVtbSA8YW5kcmVhc0BrbGVtbS5ndG4uY29tPohXBBMRAgAXBQI6V5zbBQsHCgME
 AxUDAgMWAgECF4AACgkQd3o+lGxvbLqQrwCbBNMKCTamyfzbL+69hya4MTApyOgA
 oIBKu//LaM9gC+rfYUSFRaVY5PJetCNBbmRyZWFzIEtsZW1tIDxhbmRyZWFzQEZy
 ZWVCU0Qub3JnPohXBBMRAgAXBQI6V51BBQsHCgMEAxUDAgMWAgECF4AACgkQd3o+
 lGxvbLpvuACeJLJc2HBP42h8lVDWTZwV3qstGXUAn3yIgz/FK7+//Ax2ceO115u9
 T76ptCVBbmRyZWFzIEtsZW1tIDxhbmRyZWFzQGFwc2ZpbHRlci5vcmc+iFcEExEC
 ABcFAjpXnVgFCwcKAwQDFQMCAxYCAQIXgAAKCRB3ej6UbG9suq2VAJ9TDD3a6fsP
 E79VBmop25fpGRsmAACgobOH43x4KJJxNSFM+sOY2QCv+rS0K0FuZHJlYXMgS2xl
 bW0gPGFuZHJlYXMua2xlbW1AZXUuZGlkYXRhLmNvbT6IVwQTEQIAFwUCOledhAUL
 BwoDBAMVAwIDFgIBAheAAAoJEHd6PpRsb2y6vC8AoIPWrHd+jYEXzo838pxFoJ+x
 v0N5AJ9kyfJz4y0UjGdwMrfLCRL1+h/OwLkCDQQ6V50XEAgA7nyqQb43D5Nl+4bd
 pwt+JqTn9/MnmG1Cw0h3++JAMijW/WTGGrpgpuFhtvfjs0nJ3FZMlDjdRfJ2LKa4
 xR4J/2gIkYzvuI+JaiojvyaKnO/VZC10zH+kQmEfAZTSONucKPOPPrOX87fJ/SLC
 RRPJdjR/kcub/yR7lZ9jI+5fKmv06Vgdx5agvL92eY14FdEhg4BiN99CKyOIdTPF
 xgj2bCultqldQ0FhB5Iw+IYwqV6BJsRewrNJNoXcYLeHkOyf3ULxYwYmu/wh24jW
 ibfotTy/hvRO6CBG1+r+Svqxj161T8vtFWEDdlMW9Efog3O7zjI8lXWF2pOgGWt3
 7g99GwADBQf7BlcqJ8R4BrI/Z8cJbvWWBftMC/dx8F63ISjq65PKc5izq4fSlJWb
 AEDyTv59Gv7qDSQ+ECnjivw+FBu//BY993kXLIE2KB0AY6jgMz7F4JsBhYofGMSE
 uCFgvh9c3EO326RtkgsQKM4pOC6LFZRAedjo6LZzm9k2JZK2Xv8fsLZIW9dSEtqG
 ch32Uu9AfThrFnZ6cApeRnxWZe3btBXbgxK2w3jT16j+CtIbeJGWdF8NN7IZ4+4v
 PzdDAVBwAR2iUz9vn/d0fGhVYLHBFekfB0jyl9gfgPLkXyMorDOhJ1nhdAI9Jm6g
 7FThPfNDzfgEPEgSyVuMqEoti01u0dw7AIhGBBgRAgAGBQI6V50XAAoJEHd6PpRs
 b2y6l8wAmQHMTVyf5sddE7j9+RCEC9L3VluJAJsFafICjeu6dBMwi4QQaB0zqja4
 7A==
 =E/l3
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.167. Johann Kois <jkois@FreeBSD.org>

 pub  1024D/DD61C2D8 2004-06-27 Johann Kois <J.Kois@web.de>
      Key fingerprint = 8B70 03DB 3C45 E71D 0ED4  4825 FEB0 EBEF DD61 C2D8
 uid                            Johann Kois <jkois@freebsd.org>
 sub  1024g/568307CB 2004-06-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEDetekRBAD7mBgP351FCNnqp360OUy+ZKCr2IxUU/Tyffqyrrgiol16kTEO
 bpImo5cgZcw+y3wTSgGxwbb+UmUcJhLDO0olDNOCOYdBzzKfTyZwLzgVaC/XZ2dE
 LQa+3FnIp0btyU9vermk7GqWJqvVUTnMSjinqWS0MfgrcuEXjXTQ1b3b6wCgutKz
 BhEasg38JthFvIownezYwHcEALNJsxEnsfEMm+DQXPUvWTiScu2QR2v0BVVzfg1w
 DMaEnSjw44NF+cyyKXfqx3hYkboRw66GMvcbfl7AYh7ThfDjof5MHfBbe6aeJwd+
 pyVS9BRiXMDbwnuPm31K1zsyCr6XeQquM204Jb1fdMiFEi22A2VxQxAY4cjenvgx
 2UIFBACBHtPfsK8QyAXlNtTQqvMEQe01pXm3u90pL8DBoWsWR9vDIlnJLaMgi2jG
 xBNQp9UP9ZxS+BiAoEkUficsoPvoMkzQBSnfcDJfnyCXranBuuhsF4mzvEO8uLJw
 4NwT+7jij0udeWe3Ymd4ppWHEADhx7PLdYdq4Kczuu0XcGqHarQbSm9oYW5uIEtv
 aXMgPEouS29pc0B3ZWIuZGU+iGEEExECACECGwMGCwkIBwMCAxUCAwMWAgECHgEC
 F4AFAkGV02gCGQEACgkQ/rDr791hwtgJbwCfeBGfFaR0IIUhvfVy7GYFQUjHuYQA
 nR0Vl/9xS9SbGpk9nqDCHooXgrCPtB9Kb2hhbm4gS29pcyA8amtvaXNAZnJlZWJz
 ZC5vcmc+iF4EExECAB4FAkGTw+cCGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQ
 /rDr791hwtg4zgCeNkjhClKqeDjTWvoSuh805WDuXnUAoKFid8813Hg7HATB4UwD
 3KvmHBIFuQENBEDetekQBADtrxEvnshp47wNGP33Vwas4RtDVp40lC51yVFj9Ior
 zXhq9SD20gz8qPCwG3a4Srhbh3rgjPvzzqcjSE/axk5+LwJ2KHySlpfwu4wTtddf
 o6JzlJYWtQE+bcp65vnd6L5DGJsm1KmRTOZOL6wWxTXft4lgxfg1MEbzOKcL5YnU
 BwADBQP9FCPfDZYwAsZya5h3aAd9yg6dvDsObs1D1MMIiygr54/cmGUiPcI6zaga
 hTfDiDGanlBk1idFVKh0A6ZEza55NA45lJ02W9amWvrjG+PB8wTX4IWRAmDN4ql4
 QuahtHsciUVzw4BtHhPtM1+DpT+C6aPwclpmxX2Az8tHDjHKdq+ISQQYEQIACQUC
 QN616QIbDAAKCRD+sOvv3WHC2ICsAJ0fvZ0rq70bwTIWfgYq3N3fSZfR6wCfdrgZ
 /8nwcdMpTA2LAo1YbndxFW8=
 =VCND
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.168. Sergei Kolobov <sergei@FreeBSD.org>

 pub  1024D/3BA53401 2003-10-10 Sergei Kolobov <sergei@FreeBSD.org>
      Key fingerprint = A2F4 5F34 0586 CC9C 493A  347C 14EC 6E69 3BA5 3401
 uid                            Sergei Kolobov <sergei@kolobov.com>
 sub  2048g/F8243671 2003-10-10

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD+GP80RBACjmIRFKqJ337zOjW51eExucWRny0pu5fuGaxuJmGSbKaJRAORU
 1jx9i/Cxcw7iwrnbR5xeyjWLDb7FIAemPltBItt0tE9H4pQXgP8d8VL3eehguMda
 o0yfP7WUm3U9uriJEJ8141Yql5IR0e8isQa+YsYbkd2RmDdCMDdC3W0Q9wCgsquv
 jc1gvAh7ypvhk8VLhflAeZcD/jQclE6S2zLZ1DSP2Q5mmuMS2ouRV6Z+fbWKF9XF
 TSxdLevWcXmPqvsXFT75cz8pcBIw4c/wVd8OsPU2fd+1LZCFdms1PqLjhUfXgVbP
 Q1Pl8zCAyriSnR2+BDwUMGzEgidkTjmjlbwhGzPsSJ8rv4i18xYs/JbmkeAV/ZBA
 e6jrA/wMU3ho5aIJ69KxZb3bmPVHYrqL8Q3n51uYausLxdHDMxVvjL06VAGWbF/h
 TdiFJ1ngMKfcfzI5/awpKwb9FPbERuNvmT10MDKumFW3xSAJMRzxh7O61u8N7dmc
 xLdirICQMRN2jPo3v8T2ANsdydVTn89nqdpg4Bo9Rsz/Fdnrm7QjU2VyZ2VpIEtv
 bG9ib3YgPHNlcmdlaUBrb2xvYm92LmNvbT6IXgQTEQIAHgUCP4Y/zQIbAwYLCQgH
 AwIDFQIDAxYCAQIeAQIXgAAKCRAU7G5pO6U0ASlRAJ4mnVHx0rA5dhw0scFGOddP
 cH/w9wCdG6HPWlDpXFB5nkpQalMnGzLAkka0I1NlcmdlaSBLb2xvYm92IDxzZXJn
 ZWlARnJlZUJTRC5vcmc+iF4EExECAB4FAj+VJGgCGwMGCwkIBwMCAxUCAwMWAgEC
 HgECF4AACgkQFOxuaTulNAHJ7wCfbcMzZiTmwuTD7wLTxvzC35OQE1YAn3et7KAt
 aLZuVXYIDROr33RIlfcUuQINBD+GQA4QCACIrLJbs3SkUJpuvYC1N/iykFYGHKPM
 L+XCCK3A4HL6f+GyCpvajz62cjUfuXv/pkLjcYANnqKKPJu6Bj2rFmOG785R/RPD
 o2dl+zlZ0fggQAv8zZqIP2KyQRSVa44Pxc/G1V5odcg/QOcKU+FZrkRXoz8SqfDU
 OEfarQP687+DU+Th0Nwn5M20+0ml7yw0/y9DtggWXzlWyIdYfhU+8HckvzgXnUFA
 tPdfDUzUxEjvVBUwZ5iHtUlId6sHiiTCS/fbnRzwJA1Pu1E52B2AfsLxFrwV5cRC
 ASfi7IGhZazGCctqZi4hbWQCB/+ipEVGct+bD9BpW9yS/JiMAxcwE0ubAAMFB/9F
 k6mZUzBbxQkSbXP4w1VSxf2m/lIV9v9M0LCMwjmcsJzsdLUG/i3Zo+hAjT+GznMU
 DVzPHq55LiNs2MKC8WKHXgXFCB2uoZvlGu88I2JjucoeibtC7zbKmVOntuY55zTk
 uiGkGRawIIKC6oqVFV0EGXxrcJ6v3/0vgBQSva08reETZaUFe3ivt0rU0NSbhVJ0
 1WiPXk9wFY0ccemUVmdcX4hhC0yyBB0px4qbEBY3+mtHpFVh/r24GXvWXkbLowGd
 nmKeigX/tlRyYgPHLM2goUHUYe0erbKp2fyeQhockLOWY0DBFcFRK2kSx9HYdtcI
 N45tvtkBza2O8C7uCtwgiEkEGBECAAkFAj+GQA4CGwwACgkQFOxuaTulNAGwbwCe
 P3RXUuqmNGYCM0IXPlop9XLZIcQAn1B9zRfHFJm7tgMI0A6Avybs7V8i
 =EDjf
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.169. Maxim Konovalov <maxim@FreeBSD.org>

 pub  1024D/2C172083 2002-05-21 Maxim Konovalov <maxim@FreeBSD.org>
      Key fingerprint = 6550 6C02 EFC2 50F1 B7A3  D694 ECF0 E90B 2C17 2083
 uid                            Maxim Konovalov <maxim@macomnet.ru>
 sub  1024g/F305DDCA 2002-05-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBDzqHSERBACUPYN18/fnXdsI3CsH/UgX7CL1yLSgTCTbEA7p/jPA78svM0Kt
 aHdZG+mhZH9u//SaPuKPoF6OST7pb5ee48bppzL8v1+zYIAUWib/ImR/ZEGi5SzM
 mYtNCrK3YTblaHoeKKSrVwYvFi4HYQZWG3hcXaozhZRVQTnGnDdQYriSVwCg24Pl
 UzXu1n8lw+4zDlW3eGIkxEMD/RpnH5n8maXO5MYRvuBpGGTF7x3iV0somnLhQ1Th
 1WD/7OhRRzfRpXarG8ObyxyPx52et6tGV9IjSdO+uuVgtTUFRKsr6QYk/y49blnt
 pGtd4kTHMy99Zt/GP/CBBWn7dQtMGABDobA0ZU5ILkSlZ+DHtZLEkIXljhxIyhbw
 sIQzBACKTwIrcF0trhi2dibKMOWqy8RYP5iKe1vXy5SCdcU7HxicHGzI0oRdlCHT
 jh0pik8YWI24d18UdHDhvWHxbF/QCBbW+RAyiNASzzdsiIswo9Zvras/NZbnagHB
 tP80kBhLVC4udmO7GKYxKjpgsuqihaFJdcpoxx8J6mv2sTxK1rQjTWF4aW0gS29u
 b3ZhbG92IDxtYXhpbUBtYWNvbW5ldC5ydT6IWQQTEQIAGQUCPOodIQQLBwMCAxUC
 AwMWAgECHgECF4AACgkQ7PDpCywXIIOv9ACfdAHOpcAmtGrNB7f73DIYjZSRt+8A
 njYiaKCJ2lZpj9b4JEa7C2uIoFVJiJwEEwEBAAYFAjzqOncACgkQIkYMagPC+y3J
 ngP+OjIKj3GrGZD8LXE7mK++WiAqlVyC79x5g28q12EUkZYzLGIkGuz4/NA3wcel
 d5G6dvV+7JEzEf3sAT7/iUcIgYhIepEWFEUhngvNhi+qf/FqVuT9bYz4UkHEL2Z2
 Soxgk/W+N914SgLWiSKE+hClD4NjsN/h1rT/kA3kEMKRkw6IRgQTEQIABgUCPOo6
 HwAKCRD31D6TzwF+V9VbAJ0alq+w7D5p6jk69ApdFv6qWHZ8pQCglKhTRm9d/78N
 gZZxXPyTY3qYAs2IRgQSEQIABgUCPXS68QAKCRDc/7Ca5SeztQNbAJ9XzTZBQ6wY
 X0UKVtj8E5X8CVTMmQCaA/iZu8kibLfaFPPSeTjocghSdzeIRgQREQIABgUCPPI3
 LQAKCRDkwbNJgRZkuSIXAJ0REQ1xY6OFvWLLY7vtPhSkEbsXJgCeJXaVc7+6A/l/
 P7RGJoVA2aqqSryIRgQSEQIABgUCPjwGgAAKCRAL8GQSYLofR8p1AJ9NLtBZCdpd
 p8oG67sSD9EGk3+hWQCg/KkUjHGmVSGmQU2A+CX8MN80lSKIRgQTEQIABgUCPmtE
 jAAKCRBOOAZa8Q9p19UWAJ42kJIpDGF+/PoSnZ2kKXev6Pwd0wCffoPGbdkFDn4U
 1QkH1LfBS1fzZ9u0I01heGltIEtvbm92YWxvdiA8bWF4aW1ARnJlZUJTRC5vcmc+
 iFwEExECABwFAjzqNHkCGwMECwcDAgMVAgMDFgIBAh4BAheAAAoJEOzw6QssFyCD
 NvgAniuAmAatY9m/JXsO8Pf4Gaqn8sdDAJ9w9iEjbVIrHicNoGig+JZ2MzoXaIic
 BBMBAQAGBQI86jp6AAoJECJGDGoDwvstnBYEAIbMNUUVHnlBJyylGD9ILRi+6hM4
 3OVjUMtSi3+wWxSX8iLnC8wfSUClEcbhEsgLo88IH9KARIMRP5GVZd4IdfQ944AC
 O64TgKe+Gywk5LW5BwVJOMpXLlrZ13nEM48hoiLipn5c4sx7fKBTJKQkz1KOrNfh
 IvL1t+wZ4XMUCDiWiEYEExECAAYFAjzqOiIACgkQ99Q+k88BflctgACgnBG5BoSe
 NBw4L8ZU1sgm+ioMzboAoIprTOjAbKoE7JP1Lp4sw7yQ3s6hiEYEEhECAAYFAj10
 uvgACgkQ3P+wmuUns7XTmACgghrnoPXCydTbuzTMvihKf+YFMv0AoIwLXMMrcZfV
 E7VisZO7LHKPNAsZiEYEERECAAYFAjzyNzAACgkQ5MGzSYEWZLn4mACgtfoD3CAL
 hinoyXOMFMbGrZhBXVAAn0iSmTDzGG/ez7IhxVfxDgronhLQiEYEEhECAAYFAj48
 BogACgkQC/BkEmC6H0f6WACgj0hsYBO/cd8yReuHn7G2Uy8ITXEAn1gPWD0th/V5
 Z+3evG91zU45tYOoiEYEExECAAYFAj5rRI8ACgkQTjgGWvEPadefrACfa6HcGH4h
 P7H1OYrFtAspVdWKYmIAnjKIN8ukxtmZUxBo6XH+Aomk7bDOuQENBDzqHSQQBACC
 eenGIATI8xuuYEWX4Q+6RD68CY8exYlHgBKug4rkjNFu+S7FjhCzklyCJ4txdLfE
 HI8rqTvH56nQT/SRAs4oeTyGJoRxH+OvOK0SMJGuSduegNEPR6wShdgJcsEmeeqb
 GuZjWxa9p79biD9reWXCEhFrGjwAZDLMDJvoWAu+awADBgP+OsRhHT1r+PeD2tWA
 /x2wAMgfePG2fEI2QQg0BZtyEK+NBA5uWFZZTQUqO2MPGOxqfAKPlmBBE+tJBAbQ
 E16+IzXJZ+DUv1JhlV+/b2vJDD3OcwEJaIk+/IQpDkGRwteevdRxDTfqaRI11XbD
 YwM4u2aJPTjxyXHxXiV9P69wrmSIRgQYEQIABgUCPOodJAAKCRDs8OkLLBcgg0I2
 AKDEBTYIFJjK1nTwXRYfHEx4ietiLQCfbMUkZi0uCFW71DQ/w6Sq7ZuUwgI=
 =WWB9
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.170. Taras Korenko <taras@FreeBSD.org>

 pub   1024D/8ACCC68B 2010-03-30
       Key fingerprint = 5128 2A8B 9BC1 A664 21E0  1E61 D838 54D3 8ACC C68B
 uid                  Taras Korenko <taras@freebsd.org>
 uid                  Taras Korenko <ds@ukrhub.net>
 uid                  Taras Korenko <tarasishche@gmail.com>
 sub   2048g/8D7CC0FA 2010-03-30 [expires: 2015-03-29]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEuyDPQRBACLuLqogLkae6WFGyvW6JQ5J670eCEbey6vtH6xpb8DLeJR4VDC
 qAMPhDc9QbDz/ynz3dd2p5T2OYQd7q2CKY/DiwPdelUIpaiPPx+PweANvy2kFOXr
 Ahj9Bmpb28BMj1n9nXj3/hJLwgmQz8YDkHp1NDPCRV8u9/v4LT3vaVbdUwCg46LD
 cPg9RlzeFcIhiYM5J6Q1wzED/3uUNgjFrz2Ak/FTQ+3FDuG0IR7rfJ+nbqX1HgvL
 qsCPB6tRZTC4S5V51D6Uy6dJ5oE9HB4hTcwzalQ0CkjVoJm2qZ9bG1AOUlJRpPch
 Q9rK9ZuDrZfDFxUvpVsMPfaX74esmstIDsJsCrSeFANpSNYVxkf78YZH9ZkNu1yP
 ra3kA/41pO5rHBROKKLB8qVnKisApiYK7WX87yroiZXQKMzVXWn/t9NMkWTatmJC
 Yc7IARco/MoW1OD6FB1Xy+oUJcusTBcVsbPbERd4j5Q5LBHD8O7EBmHNP8HsNh+2
 q8QugNyEQVcY5Fjv5OkrIj8A0EDt982Ow/bt78KlO26Jzqmg77QdVGFyYXMgS29y
 ZW5rbyA8ZHNAdWtyaHViLm5ldD6IYgQTEQIAIgIbAwYLCQgHAwIGFQgCCQoLBBYC
 AwECHgECF4AFAkwjcFEACgkQ2DhU04rMxoufqwCaAsi0A/6lMNrT5UsXoPnL/WZQ
 M74AoNLInd8Jk/uJinoIjzOQdJs7+wQfiGgEExECACgFAkuyDPQCGwMFCQlmAYAG
 CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJENg4VNOKzMaL0QkAoJ1hd9N1zvKL
 ug2Nn6GmYkLM6wAUAJ4vTyU1ST3Xq9Rt72F4iq/Tmb9HiLQlVGFyYXMgS29yZW5r
 byA8dGFyYXNpc2hjaGVAZ21haWwuY29tPohiBBMRAgAiAhsDBgsJCAcDAgYVCAIJ
 CgsEFgIDAQIeAQIXgAUCS7WyBQAKCRDYOFTTiszGi7F4AJ9++/0INO37orBkdKbQ
 LvgVAjO6ZgCg0b6qRXhDz8P0Nj1P9ZgmfLZa2He0HlRhcmFzIEtvcmVua28gPGRz
 QHVrci1jb20ubmV0PohJBDARAgAJBQJLtcNSAh0AAAoJENg4VNOKzMaLRewAoJy7
 QuyfXZ4kk2AxY27dgdGi9W/HAKCYEbgwje7vSQNP8AKJQ3Bxg8d4yIhJBDARAgAJ
 BQJLtdgqAh0AAAoJENg4VNOKzMaL5zkAniFyFwkqpbjsbi62NX4QE9nfqbwNAKCt
 Mj8TW9/cPWFUfXbRA7MEusx+h4hiBBMRAgAiBQJLtcLvAhsDBgsJCAcDAgYVCAIJ
 CgsEFgIDAQIeAQIXgAAKCRDYOFTTiszGi+U+AJ9cYLWPHrsh24iCVlopHKflDlaI
 4wCdG3zN13yfxr4d2WUoRGC0Wh0lwIqIYgQTEQIAIgUCS7XXLgIbAwYLCQgHAwIG
 FQgCCQoLBBYCAwECHgECF4AACgkQ2DhU04rMxotK3ACg3NdQFkLLbzTfw8IZ9Egf
 v4kRyJ4AoIUiDHa6q4BRSmjAFa9ml3kJowRWtCFUYXJhcyBLb3JlbmtvIDx0YXJh
 c0BmcmVlYnNkLm9yZz6IZQQTEQIAJQIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgEC
 F4AFAkwjcFECGQEACgkQ2DhU04rMxovdVgCfSRNVxs+9vDTZT9h90xDfEZLlRkoA
 njBF2lvR+2aLQOYiJNxzkk917ESKuQINBEuyDPQQCADACvXGQJxNsMPvXwnE9VEm
 zUzW9bppWJ/Qa50Jmh2yRxvxtrxjLTA97Juiee7gUWFrD1OFFsDf529wrl1sWsTj
 L6Qi3VhwQA2EP4wRRdIoNYl9dIUQJu+8ZpH6YaV54qiSoUeGR/hOBt7/GP+p7wGX
 RavX2RKY+vAYSqTNWsbRMJLtnUYMNtPBcOZgp0QP1Lo5JQS3iBMwY/1mfF0XBT9t
 ckbn0eMsPKIEr/1XAaCSbPuJknyvMQPwhM/ziQFAZwDYpYOh2Dy5Op2Y9tR5DBQv
 R8b1Qh2S7HYn7CcS5I9ADXwgFp7652YNLDt9rfPj+pY9IdhmfZQ2idWiQUjPPe83
 AAMFB/9ax486+NgOULnbm7rV3Bmc9ofNicuD2KmpIXkNxPve03KQJo1nKOi3G7dn
 FVO7XlL5O6+h+4LpbFJz71eLCSjjgVdokO6Z3X+HjUKn12vl/0X7hZCUsRD6MheJ
 bfvD4XJWyP34rcWZcn43YHb9audmMTlOBfQU2HRw8kF7S5IDSqqxU3CcTGQ3zn8x
 Z7PdN6IHATkLFXNx6DKyVGyYE2FNz1ne/OZSn/rIa+uwvWzlzp6FEtMzd2YZ7hzl
 JPaa0C7kX4L/h28gLURrBaPwTcTbNoRYP+/FniNbzq4AfnW8EUypHI3XzOI9tGVe
 NkhSfmgVGMMhWj4iAl7mRzarSjCKiE8EGBECAA8FAkuyDPQCGwwFCQlmAYAACgkQ
 2DhU04rMxotsaACfY4fC/jfZOwrRFRr7iNNMrcN+42QAoK4HfkkuKzKb0Nx/JVyi
 EsKTn7/B
 =meSB
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.171. Joseph Koshy <jkoshy@FreeBSD.org>

 pub  1024D/D93798B6 2001-12-21 Joseph Koshy (FreeBSD) <jkoshy@freebsd.org>
      Key fingerprint = 0DE3 62F3 EF24 939F 62AA  2E3D ABB8 6ED3 D937 98B6
 sub  1024g/43FD68E9 2001-12-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDwi3FcRBADkiWSSJSOX38CIPgbUnnDQ8S79eZ0zQYnYn5aeRMi7w0B4SnQP
 1DcFZ/EHNtQWJTCaQBWQZZWvL1ZjdK284YrpSKs7gfoV5BufcFqKatewWZUfsUad
 FEKTXLXlZa55151UtFy9erkA22VWHmqkauDFYl4DiOtaUWCX1Gg8xCvB3wCg0sbC
 /VtANEu2XbxUp5pGmReNn50EAM4vLWfZk3T2woHN0VBOwEk0BM216zfJQGLFUFqT
 nLKezO/QqoCCcVpH7rwV0V6NI1w6YOSx14CU+s83iyyO0KlRypoptWKBoA+cjs/y
 3Iy05K147YfWUhgkKcyw/Qwx8wCDaetG+qZCX4nY0EByezFe504uDkcxk5BrqBX8
 E6kzA/9vSG+J4aejKRw9z7Ku5cLV9ygXCksu325uY2t+J6b+48cT8eFMOpgUHyNV
 m5ypOL31KYRPkOzK+iiDoTPODh4Zg8YZLsgWdTrC0ZQW2nWPNd3Zv+tLAmiwVjIV
 x4XqtFXh4nhI2eM/PXhdN37R48OKB0DmrvdH819/2+9upNvO/bQrSm9zZXBoIEtv
 c2h5IChGcmVlQlNEKSA8amtvc2h5QGZyZWVic2Qub3JnPohXBBMRAgAXBQI8IuKv
 BQsHCgMEAxUDAgMWAgECF4AACgkQq7hu09k3mLaWwQCbBEeFWt8z4HlnAys0FYB8
 /U63eqkAnjKz2Lxj14N8QYtbtFThZRB5fq5cuQENBDwi3GIQBAC79Y5tcPi18bZd
 REXZmDOnLc0gHD9y6PHgR92BUCWQuafcxfQqqY2ESF/JQ0dFfBEkCAmYU2YkPZA5
 A7skmv9zHun/bXAP02hrvMU1Gt0ZHIzDV0EaO+uxY8eSKg4JuxZzpgzWCIxI/6uh
 ZhOuEF/uql7IDKMQcOfsvVrF8cZfNwAECwP/UvxNG/RUOlOHdRo3hY3H5l7zmaCi
 AwUU6Z+LxDn+fwERX7wL5rasafi1r7/9VvGADfelpxKR0kZM1eKYPtri1zS6Zm5a
 CC+QVyyoTcb+x0mWForq6FxLDf7+l/O0TuEG7VOH4RgLaT2N33yoScEvxdB/Qo4w
 KnT39F7lYjbzBvGIRgQYEQIABgUCPCLcYgAKCRCruG7T2TeYth30AKCzp2KXBqsa
 N6wOyM+tHQ4DKNMasgCglJCipoxpnnvCsGiZJv9AgNQFDGM=
 =a9D2
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.172. Wojciech A. Koszek <wkoszek@FreeBSD.org>

 pub   1024D/C9F25145 2006-02-15
       Key fingerprint = 6E56 C571 9D33 D23E 9A61  8E50 623C AD62 C9F2 5145
 uid                  Wojciech A. Koszek <dunstan@FreeBSD.czest.pl>
 uid                  Wojciech A. Koszek <wkoszek@FreeBSD.org>
 sub   4096g/3BBD20A5 2006-02-15

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEPzlGcRBADVxGiWQYCSd/HJfQi958sIFwxgfaFLyKaD4u8yhdG6s7SOz6mR
 0jTdoMfg90n8CUvDIXeHj8Hhot2gLLmOK8BHXdR5/PBkvoOEAiqWjmFSsxUKyKTU
 ntYgpIwNtitVVdunp/kBk/w36Ue5veNL2GtqbVRMgp//ebV3GBZtAr/QowCg+w6K
 5vebaggZg2H4EcdAJ8N+5wcEAK4PGjLtf6KWwFh81TihtD91EAVIMjsZO6vzofK0
 QpMdHDI0QZgvraCpsoLppYpj3dp5XL6mxRCCpFpWhhRP8aocR2ujvXYJY49qGi/5
 EowE0UuIrdv52ubCHlUWcyYdrnIa/QAh9JpHJIGdIVlysjRujygctUH1HK6zZYSa
 8R0DA/4o0up4kfwkdm7FGbFy5arNR/Zbe51dsgkA4aPPn3MymIBR1Tb4z+M0uHya
 VKyER9ISP7gafpjpZ9y4D5lDWwL0m5oLfgm4PqMJ6/44D4chDRlnkM8w/l6VqSq8
 XVmU9iKH0J+O3/jX0tE2Mbk2gL0pZKeBPcnkBHLSkLUHWNrETrQoV29qY2llY2gg
 QS4gS29zemVrIDx3a29zemVrQEZyZWVCU0Qub3JnPoheBBMRAgAeBQJD85RnAhsD
 BgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEGI8rWLJ8lFF8hAAoJemHjhjIrhB/WY+
 pFmKwfqNWN4YAKDzV97FKMrQsq2ECzvWSV6hF7QMkLQtV29qY2llY2ggQS4gS29z
 emVrIDxkdW5zdGFuQEZyZWVCU0QuY3plc3QucGw+iF4EExECAB4FAkPzlaYCGwMG
 CwkIBwMCAxUCAwMWAgECHgECF4AACgkQYjytYsnyUUXbMwCgqqKc+pI+XY398xJS
 phO65/Z5dQAAnRVA0RLAJHRzSN9aHy9RyCucN5oJuQQNBEPzlJEQEAD7Lq9Bd3jR
 e4C1u6kZCnKsbkNl5Ogor3cwoowydWrwrP9KBis6s7e4Zsek4ylR1QzV77G1ar5/
 9ecjDM+Vok/R0sGkufRUfD7XBI1mG1KJwnxZYm8aRYCERTRoXDThoJwUoHzwVn9y
 Xi3gyvS8GRLCWlAXYwJrYHn5ccCKfrOSdQG10ZWEj45zDUGFw+PSRtAOfCze5cAl
 txiDbiOER1/ryQaKutMPT3A0zDbTuG30/m9F7XDXsF/S+7kWzyfO0156xKORcJSD
 pYMILFsadN4WzSJSJFvUTVSJ4b7ljomKEJCjZF+cbPDNoiNUobLedTAkMPpPigF0
 KjVGX/yaUEaMR1GvDQ+UF7zf8ncyrdcOUtacvc7M3hL9Q5noO/CbHvqRW0g3Gvys
 kHkQJNL215gd8wxCrTv0OWfDWhOOIHjiCFTA1JGukVh49wt1bYAzn0uz+QOGfcIt
 JllvKP5vrvjtL9LpXsWgoKO96Ijr2t72ofuG+q702u0/E9G8oTNSzyi7t+KThxEB
 5VpoJItTE7A8nmuqubArIzHKyVvThsQE/xMeTE5zruN/PmsdV5zWHuJU6MArtYUa
 tNr5KXzK6UDsmdHG4bUjShjUh3wrAHLIodR0gRISM8Nnyf1l5XBh+iiCoqQmscZ2
 +4la+9Z5j6FrRDf16CDx1n7bx6vTkMYG6wADBQ//SJf5I+N2pAKpV8u60B1LI85i
 84JOGvCenEeLqnK7td1IRAkKkv0anyqMSpxTFdxect8tUPKttvTSkn8x44Seexx3
 1bfwgYoCnUUwxNegu3kv+gLfCJwsIbXjXyHqEapPHNmbTPmlZKWa26TO1Cx3W5QA
 UahlUkhFhMhbfnsxu4hJsMD/i6SPCGEhbp0jfHvXQc0VdUGJla8TOJXzfdPtwozn
 skDrrmugYtt3x2Dzf3eYr+p3EScE18uMBvcSvbN1w2ZOz9jIaO/mQ6dGpFGejo9n
 D+8KAb3ke/ZQ0ov4gnWXsKQLdQsVUuPt14cLsXfK1jhlaydtEmP8h24pR2CVUkow
 2N2E7KzXsE0ZPc6na1r9WkI85Hd1y5qZ0zxOVijraFYu436LXewqgPSXvwlc0jMe
 Uw2DgMEHK+AvMpNVwVGs8IYwVfy1EYLRguP/DR9NsmzVONEfkQxVSzUoGlk//m0b
 bSqpA99Mbye+clfEjh0H8kgx9xOYmKTyygZRCC9sKD8W4WstZQ+33UxssaVu9qrf
 m7qDl9+GYT+s8JDhzUazNvKi+xbiy7wJtIE0dShMJKN2/m2iP+PH6RE3GMfWaxjB
 Pp0qn5VxJ3Ev/VFervSP6SnMuE3BqJ+aU/bSVx9mZMMLsrHuG+qA5vCC5vOtnHJQ
 zJ7o8u8XzbuX+v2pq9SISQQYEQIACQUCQ/OUkQIbDAAKCRBiPK1iyfJRRZQ0AKC4
 7SDQifU3JEpy7s5MsTtZQ+DuUQCeInUZzNAQW4xzNapS3xMV2mJ+6tY=
 =sg8v
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.173. Alex Kozlov <ak@FreeBSD.org>

 pub   2048R/0D1D29A0 2012-03-01 [expires: 2024-02-27]
       Key fingerprint = 7774 4FCF 6AC9 126B BD0E  DBF3 5EBF 4968 0D1D 29A0
 uid                  Alex Kozlov <ak@freebsd.org>
 sub   2048R/2DD82C65 2012-03-01 [expires: 2024-02-27]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE9PQzABCADlsyzEaEjFoIM3Z0ob7pYdIDXZD9T1p1+4o3AMTlS1Bq4WWJb9
 Y5er+hcpISDHVmn4FAnIJfstZa4x5jBpbs7D3NzF07yj+jrxJ85A1FEGrViS0YPI
 I2kannA53W9q+bSkj7PztFVnj3JR7HQR2yTCxWE0M9BTuXpmwJCMOD+GUJkB9/2M
 jCRmuZhB+0QD26BC20VDiLQcXN7Y3iQOkc/k4QUt0/bN8cTXghNnJEbWT7uFdPZv
 XPKmGfmNnfnI7cuK+Wc16OTe+24fn7y3CTnHm3tEai23ZbeT7qCkfsFG/5e5BRhQ
 XJNeMXbQ/Um3kHPD7LBkO8mPab/qsOXrkeO3ABEBAAG0HEFsZXggS296bG92IDxh
 a0BmcmVlYnNkLm9yZz6JAT4EEwECACgFAk9PQzACGwMFCRaOagAGCwkIBwMCBhUI
 AgkKCwQWAgMBAh4BAheAAAoJEF6/SWgNHSmgIzgIANNwch8RoaAW2rnpWVDGyLjP
 476zCfJVIA3DDEhM5dhAIlEyqe7jYh4kwWw7+Dk8yZQMEnZZ1Dst3qasiD+CviQc
 pQgKOy2kERvPkYyLES8GiS6RD178RSRzZIpnhaE9Fl/rdjfSOOdtNlNFdmUK4WLz
 GCxaJx+betmXKzImIIhkgGhisvhTg+P9saDRiVV5CwQNPJnlJXUUraaxXoNMosVx
 BZX24aQQByaRxY2CyA0IVGhnwhgd5dCh/TI37/h/CW9RBTahvxhQcgaC2pCgPvl/
 Pu6EdT2w5vAmWv4dF+QRBoEqZpdhUoOe70W4xh6oV3MhA+BwWMoPuZsYCLjfPbu5
 AQ0ET09DMAEIAOkzC6DXsskYWl4NRlFnakaf/My802Jkw42cNuCIrClkl2R/sJZD
 wMLq0JDPcffNJJD8CP3ivo0huh6m17Jw/Gg92iijmfoL1YPPx2ZO3HOv+li0JMy7
 yYOUYRNccUP3RqBpja1upldDLXharu9CN0H7VzIJxSwmQkqcRWvcw/PkM9brJ071
 ghyp99p26pT2II65O6pQOnBN2MSeWP4QY/EiqLn2ldOm+aeH1VfoiAKyiObrgJ8h
 tEJrFfkdKYa4+mEQze47lVJAywTeojLKumswHctp+UiF/+Msk6Sutnkj0i/a23h/
 pqYekr6fod0QkwJxdopfBHGLUyh7aHUwIi0AEQEAAYkBJAQYAQIADwUCT09DMAIb
 DAUJFo5qAAAKCRBev0loDR0poDDXB/ddOa8+TBg5aU0oVPQ+bDA60b7sRb0rmrn+
 hB1mXpdMtI0kHnJxUUI6Rx3tlfD2XE9P89oFyDxiOKjLFLAs6Rj9fCzp3EijARzu
 7EUl9+Guo9p4jAOiQ0e52XN+Qz+eYa3SLDj/A3Ql2hbp7jWKa8xtM32oyC5nAL1Z
 YRx+p9eVNT1UwwQkpiYG8VviSZZQBVoiG9h1mLzkzDj6EmEOaI78L/MjTJV4Gvcy
 tn0QaaYzTPIYUVbm269WNbuRaNbVdw3u0yhgV4OKaWjTpx6Ngv7EMJ8+SK74udGk
 nejHYo4sCxROs2Je3yo1hYgrVxj/8tNWj8Phl6nWoSssGpbdIOs=
 =iXGb
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.174. Steven Kreuzer <skreuzer@FreeBSD.org>

 pub   1024D/E0D6F907 2009-03-16 [expires: 2013-04-25]
       Key fingerprint = 8D8F 14D6 ED9F 6BD0 7756  7A46 66BA B4B6 E0D6 F907
 uid                  Steven Kreuzer <skreuzer@exit2shell.com>
 uid                  Steven Kreuzer <skreuzer@freebsd.org>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEm+VN4RBACfYJ2U3THLZz/soW+0z18vsGdndRtf/i1FDPxr6gy53/VVOMPx
 a1usmGriEtK0En7cwWlPQlr5SdXl/pUNKsIZkClkZnctWPeSM3mYj6zC3HcUyruV
 rDNKUYLOYP8dCEtWu7IN0TQKH6xnqLljCFCQYK7lA4zRL7N1S/hExcBsbwCgzT6V
 aI0NyeWVcAjs/+t8s4RJkC8D/jNpGb6IuRumkjYZ5GmElelckkmIQvGs2aiBkbE8
 IRtDS3VnSUWCN8rWJqqHuwg0QgaDVIHPz5KnMQfv7gbsoGilTx8mTgDEk1P62t4b
 Y4YLKJhriaXyrSuQETPinqM3qYvEKysm5bkgiRNEcFHGUZznec2LGtFxPOGAacKn
 EwcpA/9UIKdxxsPx8sHCU6L+Teq9DXpeRLRCy/1DJAHXs2BixAGX8kTvvdKnGjNR
 CoZ+SLAc4OUqotg649y8nrQi+xGcZbP+9p+2MXD0AlQogBcpNPNJdsNtagPEgkZi
 NLoS9UwYdY3+HM7zWAgiOg0Anrf+6CUG+9xVz+cRf5hClLFGJ7QlU3RldmVuIEty
 ZXV6ZXIgPHNrcmV1emVyQGZyZWVic2Qub3JnPohmBBMRAgAmAhsDBgsJCAcDAgQV
 AggDBBYCAwECHgECF4AFAk23P6oFCQe7UcwACgkQZrq0tuDW+QfKqACgvzI4CWz2
 hEt03iQ+qoP5NbYAxu0AniE9DLJRYuevocbjNpB/U1IHGxsTtChTdGV2ZW4gS3Jl
 dXplciA8c2tyZXV6ZXJAZXhpdDJzaGVsbC5jb20+iGYEExECACYCGwMGCwkIBwMC
 BBUCCAMEFgIDAQIeAQIXgAUCTbc/twUJB7tRzAAKCRBmurS24Nb5B5zBAKDKEAfh
 5zGnGMhId4CwBWzTjjSCbgCfYARIZbqf4jet43O5LmU8sPiLFyy5BA0ESb5U3hAQ
 AN+WjDnYNXdKX5rhlhmsnrvcvfFX+75SN99VPTEMYqH5g+u1pVWV0gthfyanx0cs
 3hID/9d9afGmhsN0o0KwRTetGLDXkg5kF8OtOmh70+HEwU4kkWPgI/K4SbRVzIIX
 3Z8BRb+T5cZkMyIH2Xk5SkhATDGygHaGbYQUr+AJEstEU2NmdwZUejz7jl5hS970
 4rrEmoRE29VxsVD46Lqtm9GoeSyaRjeC5MsAHTIbvZrY4Uibm9kWgIc8z7397Jf9
 x4LNbrDRzikScPD34NRnaxBh2cWFzj/75/cz3rZEnmkqATTz768A7gCMXHsDpj+i
 dr2VlKR1TINas7N8FsiWwdcX1q/+5w+jeZU5wEMtZ7EU8adOQ9/8A0rM+Pt6DWaW
 euHrW1zhKG+FTzVR4dAedY3B5nmBwYLTS8fVdLaCc6oItD8v74pl4eTPNu/99eUK
 OVxZX4j4r15ISobcz5BGqTD88H7o7yceVZEyF83Xyuu76t2jnziunvPIUvyurTIR
 qK12Xn2xdYA1fW5zMCG4fX7G3y3CDM/MRz0Zai7XrhB+hRoB0LcJM3e1mAvi7mgB
 xdAiFWhjyPqiXGKtNeoj3YB+x7AiRM2+cNCZtAa17Q6EJPDCw9paI7z9ZGp+0ZUk
 hw43hw6eROffNJGxM5iuCphgJq98sHmGlK88OIeSO4WrAAMGEACYmu8vX8DZ74qf
 0D57roBD30hqtYtubvGxByebo3kQFPibiCGtp1tF3mF6a3VNDrDHWyTk8j5QSMdI
 KhKhxp6SwsYZ9ctbuF4jTmQzj0LTbxTu2LJH35tvfr6BmIzdc/3DoX9g80ab2vZf
 fkEsAOrpCaWWZkyMiOR5AWZlKTKBdhw/InAYHMMsnfl9zPOmVuemIn7SbEyTBlIt
 6kFXoBM6Qh25bK4Oa54s1l9GbwQ8Wn11gWO3Q9x1xrnuf4Sk+9ZMACB6UaEnNIFg
 ht/nZ9jSPKve+x8id8QJI2ffulvyq0vf2lsFoHldEsmjPmw+cYiBiL/h3otD0epq
 HRryygU5aPT8+C6bsF0zAIj0TEdRd0Ka7dl0cJeUQ2fYzitAXW+fHMgV8FNrWAtK
 5meZq6VdH3+OMGja0MpgT4liN5y+Pl1yxgWNKvh2eQNC3FMghEv1orAjf4sOVtb8
 YvMiIIXUOqW8EGFUTOxmbeejR6v6zNwJ/oLdvxa2AbBzca8wvGL2Xn6GzYJdhNEo
 we1Ks3t2T3bYV9oPGGSvTonCmktMQqV5Gn5HTlcun9Y120i/xingh0wvUkG8I9U5
 KZl8KGZvL3yjLRmBQvslUodh4SnFKWyryEz+fCDttMu3fxb4aLoReEloFg0kzECs
 yNbcDR+xYG4HW9OvkVSATFCdTHA+NYhPBBgRAgAPBQJJvlTeAhsMBQkDwmcAAAoJ
 EGa6tLbg1vkH8+AAoMqNZ50ShwH+0Npym64qgJNi+NuDAKCO9MAnFB77gBU7LJnn
 97ttC8vSig==
 =hOc2
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.175. Gabor Ko:vesdan <gabor@FreeBSD.org>

 pub   1024D/2373A6B1 2006-12-05
       Key fingerprint = A42A 10D6 834B BEC0 26F0  29B1 902D D04F 2373 A6B1
 uid                  Gabor Kovesdan <gabor@FreeBSD.org>
 sub   2048g/92B0A104 2006-12-05

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEV1zhcRBAC4T9pbx3J+/0qY5k3IVGMGpI31SZHwtO0ijDBA3V0mIOUpty/E
 2AnAQ/7GZEvWtMd3pE5xwoicgSQbPcnsHG9kqG43vvr2DdByY9lavqoXPOXKeQnr
 U/Z5eYvOgT5Da6USxXI5obFdNsCwwKYt7Sbvfj6L+FVWSS8HW54f9xuqLwCgwCRv
 TxVBZJ4xERWsk3nJH4B/GKkD/20ddbTHSTBuBpulmoOUNBcrnIEYPRCDvF/e07yz
 sp3KJeMegdPEwBoy6bF9R8HkVgSEx/jdMSZNeMeAOpAKDlTUyTNJRgzVwqu+SgOj
 GT8IzhLNFaZ7wiKoA0yRhGb77C3IPzjSbcOI9A3vn9DkStWfDtjTIOxh7FxF9+H5
 c5z9A/9++LOF8L9VPHUNi4h/L/jE6CWSZgeTUIMkSwALrochNi9xIr+kS5pPxUPZ
 MHVdG0+gK3wNLD6KGpBnHB65wWbb85fukY9y4YgEv0+TjpPwkbwlAbKtt7cf7RA1
 mYtYStbOedPBAE8Y89cAcmQ4a4ViJFWfSTLJorAAy73pVns7ibQiR2Fib3IgS292
 ZXNkYW4gPGdhYm9yQEZyZWVCU0Qub3JnPohgBBMRAgAgBQJFdc4XAhsDBgsJCAcD
 AgQVAggDBBYCAwECHgECF4AACgkQkC3QTyNzprFGOACfYLDfWSz4Ke3HN+suyrD4
 iwnZpycAni9084/VZ5iAadc6I1o81cGFX9GtuQINBEV1ziAQCADQBlmiWzgTaAem
 j1rFzVhEe3bSRg4qmcyiUyIbVWj8Ecc71c33fSHdgjHnAqKGjxKIkf7qoSziLWL7
 b2dxUiI/M7OUTi2Tdy3nJa/GJ+PK3CK4oM/oSMGOSUz7d3ZaKwZX4d/GmpCZ6U6w
 XFPymLOQtlDRTyz31QPCQXnI2CD2yswSdrHID/LuBDx+24vA2NyGy7WdUmSSchnE
 aw0fYTiHbjqI4xsTS6wkRJ4QRcHg8vyXc9Xd0/TKtaFBURWfHDC9RWNjisrhc6q1
 89o0QHBW+UqcYdWPUgTO38hr7k8U8LNJT0a7axsgwiwLr1oSS8z/RjdiFwuArM5M
 PQgkvMYLAAMFCACIMIO2gjtPL64mLy6If2TPBTqb+g+HaWWk4lxsUN3A7A5y9TXk
 w3Hx2jcig6P95jIKyiTJkV5ZqcUuwtEWK/nK6M4o8x7QQwLAfH6x/wfsb9Gays+K
 wT448Xhi05cOnIuKyFXXzaNRgGe/G+fxpxqEjmgP5y2NjB+KG/h4/Am25h9Ylm+P
 EYq8QMxwYS+3TpfCMmgnqTymegNZpbQ32nJYKnxn9j58sLqgp7BjekgAYi79z+Zx
 0HoeGPiehGLdymoj5aaiTCZfTB5CRMyn+dbvXUpl8hdAEG72q5D7JH8yicOANHUd
 NdMIcDxTJcHnDQeXdSrVWGTQmt4iuwfweKlmiEkEGBECAAkFAkV1ziACGwwACgkQ
 kC3QTyNzprFoGQCfZdGMd7cQFoCW1DBGMnNJ9AO5WmQAoIM4BtfriXvx3Tov88ES
 DHOhFMi+
 =jLzS
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.176. Ana Kukec <anchie@FreeBSD.org>

 pub   2048R/510D23BB 2010-04-18
       Key fingerprint = 0A9B 0ABB 0E1C B5A4 3408  398F 778A C3B4 510D 23BB
 uid                  Ana Kukec <anchie@FreeBSD.org>
 sub   2048R/699E4DDA 2010-04-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEvLStoBCACxnU/0ujcU5D0Ph4eGJhRfFSxoH/CBIH1AnaQyrsmzMCfdFav+
 IS9qdAHeNN1GugOKwvbP1TQQWQjGNiPMaUzWVE55PrLfQhTq3q2t6Q/9MUIXEKkX
 p3bruBe7eruQb4sN9Q113lLTZBTs8GsWI+iAqaeuT2eKhYuJlqI37Zp/36k87cTE
 sQg37HtSfkjLOCEbxH9q6JGCi0rwa4DqlPfwoPEyyMuTcwcRm4QhNKUvJ9jRFze9
 YYMXQIgBMX5L0j94mnq52HkXstv2rK0xURKANtXcqb0ciQUoXTRN0K0cYHPbNHWS
 PqZMhpTYd9d+SKYHuOGUJbsLhtaGzBLK9SQ3ABEBAAG0HkFuYSBLdWtlYyA8YW5j
 aGllQEZyZWVCU0Qub3JnPokBOAQTAQIAIgUCS8tK2gIbAwYLCQgHAwIGFQgCCQoL
 BBYCAwECHgECF4AACgkQd4rDtFENI7ub6gf9HsBwaT7CmPenZPPJk+/GXDiNWPW+
 Q7c6rAEA3072j+h/RDTnhKip9R6/4SankmrQSA0NCO1EiTzsgV/3cS0k4v0XKBrT
 10B1WrxI5Tx0osEYNP4GhPWkEO/6jCTF+8EsKyPujOvw9ps/OBgdYhD+gwv94SX5
 IymGWrBeyncmJDefcvA1UoL5XjhgGtv6qhmzPmN0+PamJlPd0X2W0fb/w9/od+5+
 o7olzxiy0kVaYXBizKVQ482x/oN3kXwzMmxkhN4zmoJpOzvjBOw4Ar5WiYldgL8x
 ZggWcR0NLVejeyi5VBPxsPh3vfvfvvjhxfHuS/bLGyBa/tO0bKxTpbD9frkBDQRL
 y0raAQgAsOEgWecCnr55Ny/V3LI+apr6wq5Rt37E+szExLEzGPQCeSE2BKWDNHGv
 KWYuTow6dZtCySg7GXW0fEV+QEvWvDa3y/zGjZOSVwcm7pk3Vm3Pnuv9a52wG6gm
 +a0M/68T121UK37+u5u25OHZaMaGl2poaeD/D+jzzvYvEDk6C84FNDmLXZjMtiuS
 NmLsc+kZodFbsrUjdFZXykFKP4a4D8Gq4nPLvDjRB5ZNKFjy1HQxpOJAkZpK0wgz
 t1AymA+9oom984jiPlV3DSrxrJoAndQeHoKDz2dhdZ9E1CC0Al5aAhVn94nfdwee
 GEL8N1KTtQLBmP4QXFtOAupBiqq0IQARAQABiQEfBBgBAgAJBQJLy0raAhsMAAoJ
 EHeKw7RRDSO7B1gH/3I75IrWb9AAEQRYIoGJW4/vPB2CQ0juG2XX657wzgDzL8uD
 E8Lb4zQJa1RtSj8Ma/Qx+cL7BNWypZAUIrXrhZiVdAjvnQ87CyW2bjZ1w4zsv1Qm
 mbKT6TmfMuGQLUjnoOwdRh77TfyLirKsXx1535UY6gH3YFAiZaf5H4yosC49tizF
 l5WNOv4DmHSJ5npLItAORSrBDeJWk2wLjp7N+7Hy9lbyMegAwYMQSrQTwNRGok0K
 ufjKvZwbUTmo/MYaLncTWpWl/ZFL21s90vBM36q0RiPDVCkZvqrdwyqb56Fr4KUH
 yl7TOEgJibW2V19o1SPGrF7QFfC3nE7S407UmRc=
 =+R9q
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.177. Roman Kurakin <rik@FreeBSD.org>

 pub   1024D/C8550F4C 2005-12-16 [expires: 2008-12-15]
       Key fingerprint = 25BB 789A 6E07 E654 8E59  0FA9 42B1 937C C855 0F4C
 uid                  Roman Kurakin <rik@FreeBSD.org>
 sub   2048g/D15F2AB6 2005-12-16 [expires: 2008-12-15]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEOikikRBADU4oWe1rkbd6R8HeOR5I/Uw6gGk0zrBPNkyT9PAtNKFYgAOotZ
 fJbo1czDlN5cstvqBOUKbmeOwqkMi3/DT1N0VjGq6eocBCvBhHZ/PIyIonV18JGI
 /wYYQ2k0jAOpehd7QYYB6w06gi+siJ9UY6iEhVxrO8rF5Er7RYXICubDEwCgszsF
 U/rIMr+yw52uGDe4d1wyICkEAKI7uw05tkwQutLzjx1ZOCu1o8zLepZ1QMRDn8io
 EyMRY/pCvge7k1kjmm/6eZ3M39fPrvwcpfsRF/dlgEeQI9Pn0HDJWG7eU/zg0wrQ
 VkvELJ6qtJvlQRKMh51EfLkR00Fy0HsBWfc4U82GvBLU5fPL1FujMeVLJtZ0W3q+
 nHjUA/4z0JVp6vNCkPOr+BiJhdJsiAYkGUdqHR/mZcChcRD9jJVRO1JDQQSvP3o1
 GvFqqRU5VsvYXKVKlVoWQiKGu0Hf/ZIOnY8ek49nTsUTm1MDPIFqMl182uxr3s40
 DhBmKzhufDBkgtNdpC2SU0h5mwkF09Xo1goVMn5DTbQfRfNfF7QfUm9tYW4gS3Vy
 YWtpbiA8cmlrQEZyZWVCU0Qub3JnPohmBBMRAgAmBQJDopIpAhsDBQkFo5qABgsJ
 CAcDAgQVAggDBBYCAwECHgECF4AACgkQQrGTfMhVD0yS6gCfQyXa2JPiyfy0EFzQ
 HGwWrDPjzjsAn0IJZGfMUiTegcmtpu0lNv6nMUiEiEYEEBECAAYFAkOjJ6YACgkQ
 TclL2LcfYF1uNACgxXMrlmzdzmMwriLK+T4OKcffa/sAoOCL19v4pPw4R4KI3o7O
 MOacY9bIiEYEEBECAAYFAkOjvw0ACgkQryLc73jOEF8XvQCfWcxEwIwZ4eZld/Qf
 eB1hsxJeDxUAnA/ftOsZtbG4o299udw71y57GHMPiEYEEBECAAYFAkOj44IACgkQ
 hdRQRWtpGwOERQCdH2AVEiuQohXgOX2PdCIZYiufCEEAoJgGONTdR1U3cp1X4Hhc
 cuAX+Z1IiEYEEBECAAYFAkOj7gcACgkQXeTX/hlJ3IB1CgCfbgMdPkgLWLQ0HHKx
 rR1nB3hzAiIAnjOwE3TRytoNLPAAuECgudqkqpnRuQINBEOiklMQCACBiZ5wcv8t
 jUjCX2iZ7D5qQiWuJYPhMpBS4hV4mZXhM+pSjFctc9PFw+WHlaRFXn7zGYP404AS
 tvqmnZBInBdal+L7r9OhPj7vrQcYDHJTMDflHK/YhfBwMj8/r2jkV4Ja4ji9nazr
 Gbq1wJpP1jrsBuFU0Qy4HRZwSyKrFNGqAEsiZPxgMAY16fi3IuVbE78HlUq+0I6Z
 C90z5MbGFGSsZRbWJSxSCOqQ7YxqoaCqxxNeF6fIYQdL4hatuH287dqmru6ST6j0
 ApQF+mnmlwKnrLSzXw0Hbvfj8ZrGyAc9cLz2oCwVwvLsP+ohiNBDHc+FFXcBxIcy
 kZi1+6AxjhXfAAMFB/9abRCZ9AoTa+Hd6ajC77l/Ul4jlj+R+DKQ466kj+WYOdeO
 XQtF3e1g89cEX1S3lnjIZGS3uGZ9YehtxMwBXlOCIyyLhNxlRWS4YJeC2E1q1kZm
 +xs6IC47g1E5yVpm3qcUp6HKwO0SGLQiN3ECSZfBtNEcEScAFGq802lLLKnMRBfV
 DpwXP4jop+90NSKP4RKzgYdXXz3SAq3heKeuBOHl3biaTmvh/FSoZtcGSqWLPR85
 d+5GZVJRzrwGqrGN/3zRvd1PbTpeJ/pbT/saFtsVCmlPoUOpKeyDHGlPotQo67gu
 1cwcr8h0D+oYPMLlspZFuMXvLPxaNB8oRLyxVzUhiE8EGBECAA8FAkOiklMCGwwF
 CQWjmoAACgkQQrGTfMhVD0wzaQCglkceiB8ksT3+rwFRApwaWTO8ey0An3w0Diff
 8juSFfJ2ZBIPyPzTGgMu
 =0i68
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.178. Hideyuki KURASHINA <rushani@FreeBSD.org>

 pub  1024D/439ADC57 2002-03-22 Hideyuki KURASHINA <rushani@bl.mmtr.or.jp>
      Key fingerprint = A052 6F98 6146 6FE3 91E2  DA6B F2FA 2088 439A DC57
 uid                            Hideyuki KURASHINA <rushani@FreeBSD.org>
 uid                            Hideyuki KURASHINA <rushani@jp.FreeBSD.org>
 sub  1024g/64764D16 2002-03-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.1 (FreeBSD)

 mQGiBDybt48RBAC/KCE5CLVZsYvpmgrbum7JHgIgnX39EPMQmL9Y3LmYy6Iwh+OF
 iIjIqW6cDeCcxHoJBwbSUerC5ueriwZCh46gSnLVjnmBLlGFXyxYbSfFGetMVVSR
 6OpiQuITp4ZhVw/UoCGloNsIFKg6l4JMwqZmsrZPdl+zUU79RV9Zb4XhFwCgsRIo
 1mf9I3rNZ8f1Jv69nUR/lJkEAJB6fY1rtUNUwq+JXOnFGD0KnC8isQNyOeQ7Y1il
 HQ9mGVKuUC3Zh0FzvdsU7Ks2ss9ynxfbFXnyyAOqXwTzU9pMuW5oLOUmjqwEfAhV
 4S0xcnPcfGGJ671NNeqa8X4LQv6ECWai6O4CbA4aluRqhHNxT9dgEai8RN434LQE
 tGxcA/4mIlvVoM2c2DRjD4+/Oj+i80ZMpOgE1RkuQmXoZ/DwLD3EHbIBX4cNffOd
 FzxYrKCrXD50MehIw/IhFfHN/GdEN7NT87M3j/ydSYFluoiLv8FXO00mr8cDi3wF
 q+LGbniEhVcW6wpUz9zVFmdLAp3HQi1uRAHqYmdSs6gqjl/+pLQqSGlkZXl1a2kg
 S1VSQVNISU5BIDxydXNoYW5pQGJsLm1tdHIub3IuanA+iF8EExECAB8CGwMECwcD
 AgMVAgMDFgIBAh4BAheAAhkBBQI+L/K/AAoJEPL6IIhDmtxXgj8An1YuXcp0iurB
 ZYHiaYMzAb+lYhALAJsEAKTyeqO0plIvHBV49L5CErZo87QoSGlkZXl1a2kgS1VS
 QVNISU5BIDxydXNoYW5pQEZyZWVCU0Qub3JnPohcBBMRAgAcBQI+OM7uAhsDBAsH
 AwIDFQIDAxYCAQIeAQIXgAAKCRDy+iCIQ5rcVwyNAJ9Y5N6lIMXVy4sYCdgQvqDR
 xkUN0gCgrsbQwfTOBcy8Mw/UmGOE4/fwrNa0K0hpZGV5dWtpIEtVUkFTSElOQSA8
 cnVzaGFuaUBqcC5GcmVlQlNELm9yZz6IXAQTEQIAHAUCPjjO/wIbAwQLBwMCAxUC
 AwMWAgECHgECF4AACgkQ8vogiEOa3FerLwCfRPWW7lC/pAVdD2Jo+8rcWTKQ1xEA
 oIQ/on62k7YBO+buO+K472a/cW2MuQENBDybt6UQBAD/ZGmvwhzt9YWhF9q7mLOT
 iEMzL2AzBryLzzUphejgDlJN/TIoDtaJfMyNkO16FbUq/WLQbKYFKfDunqx+eVSi
 PsneeYw9nAdlcXVgHRjoL3vj5O7PIg4qqps2mnLKEOXLAH2PNTYY6+8T0NQicdht
 YIraowzLoKRdINuDQrCpEwADBgP9H4CwbNJtQAHwS9ATmfL6F2Bg9LWe1godSWkM
 N+nBxKvMqrajJWfxV09f9gzn0qmMZT9u2DwcADzRQLC3jkzgOD1f8UiAuCuDEE1a
 vg1iCuyiI6m+MMWCkOCj/69wIu1ilmWqkn8SeoEwN+hwqHa20ue7vBhXreQanJim
 sq38ZdCIRgQYEQIABgUCPJu3pQAKCRDy+iCIQ5rcVzT/AKCgYOyEMpIxXYVI5gYM
 CwQ3hkJ28gCePnTu3Ke6lPoQsMAo3TzKkUO9Wj0=
 =cXJQ
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.179. Jun Kuriyama <kuriyama@FreeBSD.org>

 pub  1024D/FE3B59CD 1998-11-23 Jun Kuriyama <kuriyama@imgsrc.co.jp>
      Key fingerprint = 5219 55CE AC84 C296 3A3B  B076 EE3C 4DBB FE3B 59CD
 uid                            Jun Kuriyama <kuriyama@FreeBSD.org>
 uid                            Jun Kuriyama <kuriyama@jp.FreeBSD.org>
 sub  2048g/1CF20D27 1998-11-23

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDZZXiQRBACWc1PcCjIpTl6aCyOMVfz4jlRSKblwib2s07TBwbgR1zMhbPie
 O2K4ZJqTcG4EnbMLEyYMbYwvNdOfUIjMW3VI1PJhRwWthTcbUjubzTu8Zxw+sKME
 ansth0xZW7Ax29UWQcTPxs4SRsCPFO8t+aWwZOm6z0fb5l1vMmKNJuw1+wCg3ZZB
 qK93hQPaOObwglnAIrgNpScD/j0VCEeC8fTMk+ZIo+z0+bUGPGU5cq+4XVXABYLn
 wMfR6Wr5Ys/3VCx4Oyzzgp/HBzcE5HxJukJ2ur3m9IE+uFfY4+HEFiwL++Ke4TWU
 7rn4rKjJYhGJ6iqGFwuxwmHdjcBh/38X0kmrCxyPYpt6xO+sJBP+QOABw3PFlMkF
 PUY5A/9RGU4mm6K7cteNdbHDI8yFNorQs8W8fRb8yP8bw1T8qB5+/rQ5jxAfA5sr
 FCuZsKNFdph9z/I3eFYVW4P8+9gmI2FAAAocWheSyKttAFHx63JRyBqXq9xmHKST
 kuaoQVXeFycSULAPkV67j0/zDL2mis6bRpPopINGgjkia16u6LQjSnVuIEt1cml5
 YW1hIDxrdXJpeWFtYUBGcmVlQlNELm9yZz6IVwQTEQIAFwUCOmRRlgULBwoDBAMV
 AwIDFgIBAheAAAoJEO48Tbv+O1nN4+YAoKeQztEcbPBbbX7DZAHOsGZLrZ2NAJ9a
 WEoFGMT3keQDjtjUI9c8IMh/l7QmSnVuIEt1cml5YW1hIDxrdXJpeWFtYUBqcC5G
 cmVlQlNELm9yZz6IVwQTEQIAFwUCPE3sswULBwoDBAMVAwIDFgIBAheAAAoJEO48
 Tbv+O1nNMp4An22RFzdv9zdNLlcY9GLPFyUrniqiAJ9F9Rhic6qBaXynksNw51Do
 +cLWkbQkSnVuIEt1cml5YW1hIDxrdXJpeWFtYUBpbWdzcmMuY28uanA+iFcEExEC
 ABcFAjxN7RoFCwcKAwQDFQMCAxYCAQIXgAAKCRDuPE27/jtZzYFdAJ9BFckSo4/r
 SMe9UqbRMPK+8FUumwCfYH1pt4t6jFlulLk+9wYA9wISL3e5Ag0ENllesBAIAMSU
 hrKdEdKzQXHzkoE4Nzl3hb6dtDmjgYr+3X95wBkUvtrk2CeYG3RC1PNwd1sEFEWp
 IiSzOaQDzxZmtBGpMkQ1It+CW4sC5Cs2TQ59VHLFw7HWSYMNj+RchWuWkhwipnX5
 8wu6To12Mu2MnyLszX2QIUxrQme7UpKkJgCct60C1DZLoQuZmfEZEyXmSfJsizeq
 eeJuusZwOWDH0ixuFVK/5A2RwaWFMftdhh/Vw0EkxdQnMJ+7zJ/hbY64VR7uz8oI
 5smfjVe0yqXMACREUzXmqn+Dc6Pz6ESVTv2XwIy0UxqxiYk1J98Cf3ffi5+e/q1d
 rej2PzArpfzaygu88uMAAwUIAI/IiiQJupz9BaCws/K6j4Qs5iWRiSB7vaZfgCr9
 c6vx+mIXX1Pblity5TOn9qXMv7vUM/dgmWSBbkkrvfD++H4ybJjpcOZN+peeGd0G
 /UfiQFMarsj9MozAmhzI5L00JqLOf4u/XBv0rh5HOX6t+M9MfZYL3C7bn/LxmDif
 prT8jxoA2SC+lPGSzI+M+ay/mz8kDmGD7fCS+uAFo5T1kjU+ed2dhXnl16gRR8NO
 6yAdURIC+xs6P+7L8uOiZfuk0gzn5RC6CYrEKiGZf9VqTRA2vcirPNEZR44jYXS3
 nL7x9pIsHyCyxEvojut7iGWO6qbaW/c+MRjcA8jgp9OuFROIRgQYEQIABgUCNlle
 sAAKCRDuPE27/jtZzZksAKDbznARmDIIxZjHfAry2UJFBPQbvgCgl/ERQfF++Uvw
 hLaVfesP/NCIt5Y=
 =AoU9
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.180. Rene Ladan <rene@FreeBSD.org>

 pub   4096R/0A3789B7 2012-11-18
       Key fingerprint = 101A 716B 162B 00E5 5BED  EA05 ADBB F861 0A37 89B7
 uid                  Ren&#65533;Ladan <rene@freebsd.org>
 sub   4096R/B67184C6 2012-11-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBFCpUocBEADZA+p2mpQBevhEqqRwwsiYVj2wPOsGRaTfyxSmRj4ZwAxuGLOw
 0CVglKt6geZXnl7+OCBBVLkyJuMxrMsYYB93FlObQEAc5shtQa8EfypFUXqwC5OE
 C4rJ/e2gSZ+S35txDhXfz5+w2RYSVckrwSEEVWQKQV36rw5tbxHN3plhQ4+LGeTA
 ak1dKW1yP8nyYufJ94h8vyma4fUHVZ2GEu/lBM/YW1Kl4ofjWZ8w/HJlOt2eOy6T
 Bngjw7E167eqFxN+M5TRyK9XT9Yg6cSNF5OBaBEOgchhKwl2rWYcgJO5YncdpKmQ
 mbzNYIwYAlG9bILa+1usodrE7E4h5l5DHXNND3w0cT+oQ4+NZ7WvQSHVRuPRzJEc
 tjdev+saeNdfqFnJSx84tg6yrv11GMiqagFdvuUFWmcoyffJR46zMPEh/rKJRBAu
 6kktwwhGdJIYw4t0V785Q9vs+xrcs2oKeedJCjQn4tX+TgiWTIEbRx3leA/7f7nI
 PsgaPDzFkKm6gkLKDmJVXrYUJYvyYxUasMO/LRD4CXsH06KtF6l/wQEAyEQRXFn4
 0TnhDNvzT/c3GM3jFoR7rfesyRWqEat1YaI56rEc5TJTv/OlDzSjABZ7qZUhpukE
 NDQGlWAQbxWTfdUCE7Tvq94jG5Nz+OtN6H5sYK2aUdKsDoYkCa1eK8dQHQARAQAB
 tB5SZW7DqSBMYWRhbiA8cmVuZUBmcmVlYnNkLm9yZz6JAjgEEwECACIFAlCpUocC
 GwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEK27+GEKN4m3F9YQAM56gtQF
 lU0xJzttaBCjSONNWYppz6Rdirwst4tUecFsapxjPN0jEpixpmDRspnZuG5kN9bq
 s/UlUuyDK2pE+2mYK8Nj7G+7vyAfDmLghf/f/8ykoZ8kOWE7eA4h7ycz4ebAglll
 eFwIoSf8QcGVFWvo7BaXK0w1aKrSPxJXazhR+cmF8ads2fqJlV4A/Rq74GfCoIvI
 uyIzh4tG1SiqrOG69dtQUwvlritM3L+k0Wxb1Wg2iStt/zQSRpiS9lM7PvYKZZJk
 XRHfDZWjcgqGx3Ap1d5fw3RS9F+hMf1jUp/d10tcgNPe0TytHxW/Rgmc7u8PDbdZ
 1YEvpbWQu5GBGbD65zjcr+mq0eT88rjOyAwje2MiM+XF3XrVMM1fNe+2oMeyzA2B
 gPFG46nOXdEjc4uDACgfvb5JeffnBMtnBQTmO6YQ+ogS5X7b8QUdh6JQlNc8Tbg1
 jQbtYUYOrqO9KpRmQR8oanm9uLul8EFGhTwlUfBkgY3kstiJvisSQmwVdgv6MYue
 oRvPf/iwWjC8ApslsPY4926uo/1MF5RiJyGR2wxhNNxXQBy0WiIqyOGbCcrsUkx6
 Xr48aNuw/yxHoRiX8bGkg0m/NBHUn/G8vLT2LO6jkcSXLnlIlKY/lWoIwQnMXV8z
 Knr8WxcGdjZ6E/2VomLQQx0jb4aj9mp16YDTiEYEEBECAAYFAlCpWAQACgkQjJ5k
 euVkK/xR0QCfTgWGJ2jvWobVNz7GAz7O2nzYovMAnRf9Ig3UsQYfh1VztDWI75sc
 vxdCuQINBFCpUocBEACd0U3FCpxiWZz187gNwN7Fm4dSV60JN0ZrDQWynNoONqap
 jiNIgG1vdiC+TsEC+Rzoy7HfaFS9N8YEPepmEULrP8IQ8geV86AJHbhhTDlMHpal
 GwJnjTgRvUXllKImbIDX7sbgFrPLFg5RHFl+d8fazE/CKXeZ5QZ8IZnjV45Jmz1s
 +6OJ8ZgVaoH+VyWpy6HEoTseKmEC2ERDX8y5NPDEvPkjVoH+nttOL2qHxsCwoHxP
 dDAHuVZtpH1DBEXHXLyLBTgTUj88CqHGyJMCEhtt7IcMIqe2XeGoLTwRL30n4cYN
 4mBMRU2gAg8mko+nsNKQ9lCYk7j7vyxuxlrs6a5hBOIYbf61Z+mULKnFdYNDM+u5
 2Ne2a1bWfLUwjYxXEg67T8zOPn6XKASF+6tjtucKzjMyOxIDn1M06su02Uwq/f0U
 DQZNeTdiUP7kdE0W+OwaIboBbOXdM9bE4t5Fl1jQStFFe3Ciadpq5PI8bShqYWET
 +19PSjJJY0ILPMiX1TuiN7ErIXZ7d9MKPwCbX9YBggrkoGXYv43MGBUHkdvHP3ZS
 6cPOuLyUfrlmZ8X4mz2YyfjD0KqGumLoTpCQIPnX8MJDhAyAA4TH4gaz0TEU4SFh
 uOgVy2hAa1oCJG7UJ15mAz6c+WriVWkZCD2TPgZ50JKGzDcEOfvpt01SneEE+QAR
 AQABiQIfBBgBAgAJBQJQqVKHAhsMAAoJEK27+GEKN4m32ngQAI74KZiHjG8yivui
 dS2BqkzamBr047BjZMIJN5Jwgs9R6ojTWqxcj1IkNkeKqewmJkBlCGfaXQkNdgKw
 wno4qthdEJIOj6NmzrdlFHrhq+FX9xz3DdV2KO6l/sTafVCGkKXBVLueEUZQ5pKv
 /++HPUsVC/n3OtVD6ZtlbkSrCkjwRtovniQsSqfoH5iFgRwOTU5uhQMC/9ckwSqd
 8DPb2kE7rm/GFtJmub3tC5BfNBEOG1wlE329BdlPe+LtsvUq5S3puWn96zh+qFGb
 Ir215xEN1aALjezrnIV7R/5KgpwqTZZp35EGzSLwITKy4B92Tm46FXtD11OEf5eM
 6vMlpsbd5gTSMvl4RgBpHWFrr6Mb6AMLNjDSD1QDafttay7ZvOx95rCU3lCbJfov
 E59i8v8WR1yNMXwe6/v7ZGeGFpatVbx+kXSgIkHiCFbGOtv1aFXuophuIYHmYMO3
 sxYtR3Eqjlv5rFtv8eA/oYvXDeh7DwQhMJ3Cy9yvbz/NzaH+fyDizSnCgFWm0XBg
 CEeYErpsegcqhFtbuJRF0FdP7OhrSgGgYSOssRzeOhTbcafbPlt/ngEleSYRQXKn
 Ffomz4fcGjZjVcLMiJDm6A2Dvii36jGjeU61W6DaS7ILqMvdjSUnO6+eUuUY8Dyg
 HQ/SHnxO1mCp/Oz6KhHd/Yhg+jM6
 =RTPm
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.181. Julien Laffaye <jlaffaye@FreeBSD.org>

 pub   2048R/6AEBE420 2011-06-06
       Key fingerprint = 031A B449 B383 5C3B B618  E2F4 BAD0 0F0E 6AEB E420
 uid                  Julien Laffaye <jlaffaye@FreeBSD.org>
 sub   2048R/538B8D5B 2011-06-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE3sxXABCADDNxQCO8nHrTUJMV3tTT4Q1m9Cx0ZVeo1f/qUF3IMO346VYbQ7
 4ghzG7cwW2Ey8uGJmMl25p6CLIMG8eFPJHvtwCFa2CB8abab/WsfELNUOuMFyW8c
 HrnZp7B3I5YnlcIhm8RlP4labHTcU8mkjd9tlabmvWcXIIMKZO6IxSk43h8Btnol
 AUW8eyHi9so5ohwnGT/0OYskYlPKpBUAIXIOmaXmg08bdix/EjWtWRaHVWxdMIQl
 ZMseByIlSTGCSdEooZOFELfaPWOWFFQ0wTi/fiepDWB9WG8VvZH+1wcxotlCOVnZ
 jcpYeK2scPg4BabHtd/r2UxDsxMClZkg8LG/ABEBAAG0JUp1bGllbiBMYWZmYXll
 IDxqbGFmZmF5ZUBGcmVlQlNELm9yZz6JATgEEwECACIFAk3sxXACGwMGCwkIBwMC
 BhUIAgkKCwQWAgMBAh4BAheAAAoJELrQDw5q6+QgIl4IAMEHNmSxHv8XxeGDNWwJ
 iw6RirQOcm4WPpWGtvChlvZ8uTuZgPlqdSBQEGu7bSWTTK6zplOVmK4DYpUL2Hl3
 /2/SursUjkKO2QUkny7m/fT9qlJP+PAbXiqVa2naI55QvOuXNNx4zSusP8q7abbR
 bCtYHDeFE/DPNLI8GD/0Hmd8NWrPvHIwhGsK2ZzTuoGUV8q7zqgjlu7JB2JwH9dI
 tdMrVM2OgFLt3Mrb5F1C5J26nut/UVSkHPC1eW7mg8HnvCUK41HA1tKhkbXD8uMP
 7D3zgsuU35GHA5p9ARlETIauiVNsDzNgxWwU57BJ5hvGsmycF4M5i2/IOx/V5p2g
 yr25AQ0ETezFcAEIAMI/+5rGOIwZwC8qGny1upk8z/XxCReW3liTVOe+f1CaPOIh
 nLTpyD7+Mxts64IDO2tYQWZTw98yayGP8xCRKjBkgjOIgX/SInoAc5YAUMWMOtl4
 3kGqR+RboQWKKq83VPNGRnwTXu3RMlonyt5T2RV86lgIbDSabaAUnLjWDpgP7POI
 /IrpKLSJp21TXHMGobpxeLcXqPApRdKgJL9bP3+jLqbKJmLzhgwzjxpIosAWqRkb
 PJdZejCfdC8mU1DpKCDUQRLVD0Sbh69jsSiepSh6BIn+lDpfRH1nLoGAhomG6kwC
 pG4hCXAB6V2EvF0EBQmDMmORlDJFejDpHEbXxlEAEQEAAYkBHgQYAQIACQUCTezF
 cAIbDAAKCRC60A8OauvkIN0qB/iBrnK5dmFQ4aGQesa+2myOCMgiszggnbzXDFA/
 eky/jkIQiAr2xUAwQZz3iPrwzSpopCcPXKHnN7gsfRBUZ7ns2JmJWmyU4gxadbFl
 kMvB+i24Cav9/ucE8r0wyJKcquI3PiS4qpUzDEdNG/k+B9/Z4oqKRCcxrjSrwnuy
 iNFiIUl3AQvTgHQBpZGl9DA9zdAM+iPbm7zFwQBCpFeysEOv4bCAfHFuRGJ4xKyq
 tM+aBqAYzEWQTj+WBz+zYBHOY8VOn42fwBRWeR8+Ml0BxebrNh/uJZOjJp/IBZbc
 39ZjPt8SvaBUTAfKGXPZ9O2NSNEExRAKFQ01NDQfN8xxH/Y=
 =QYhu
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.182. Clement Laforet <clement@FreeBSD.org>

 pub  1024D/0723BA1D 2003-12-13 Clement Laforet (FreeBSD committer address) <clement@FreeBSD.org>
      Key fingerprint = 3638 4B14 8463 A67B DC7E  641C B118 5F8F 0723 BA1D
 uid                            Clement Laforet <sheepkiller@cultdeadsheep.org>
 uid                            Clement Laforet <clement.laforet@cotds.org>
 sub  2048g/23D57658 2003-12-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD/bH3wRBADoVem06r8ivhxQhCOEH06GAg5J6iqqlKIo5BmOiQ8IHo8JzA9z
 TwFNbhUCMWzUusH56nNHKOTuFV7wHiR8nvK0y2yU5qTK3MHbfSeMVy4rFAKgyZae
 Wf1lxRHU+W/EksFaC31ljkF01TGHVMtpKPzDSttgrrMtgstT7QKWTKcggwCg8bVn
 g7MH9udGaSNY5hO3l9wIcusEAMD+erpSZgVfwojT/pliCwnvKRwNByhIWqz2y3Ly
 M2+VR/IjFlpOvT4Ytrn2VC4V1duahdowNQh5x0vUPagRRYKx67OEbIcisKsGQTnT
 m4FSRUfULKZ3M016uSsYNbuopctjrxHE1YJfskHmLnIHjnXhJjfmouQqOX8nQSh0
 ryjCBADTi6z4ZvH3CF/C1egPsmYzJ14H2t51JUSHwEWWaj3LkILEGvHsywCIT7Xd
 R34B0hPIn/ihsJF4XBEiqJlZmFhfFUmSR3/No4TYKOtMAzfo6GtMv8q19U/LQaVY
 1wYY0rWCqfzwcH9vSLlpHL9afqNBnVK3XiBGMCmXZw+4klu+f7QvQ2xlbWVudCBM
 YWZvcmV0IDxzaGVlcGtpbGxlckBjdWx0ZGVhZHNoZWVwLm9yZz6IXgQTEQIAHgIb
 AwIeAQIXgAUCP9sirQYLCQgHAwIDFQIDAxYCAQAKCRCxGF+PByO6HcPlAJ9gLehC
 AhRMepAZrGdPsPFoMB283gCbB6y04aeQlXaa9+xAm6C0ciAiXj+0K0NsZW1lbnQg
 TGFmb3JldCA8Y2xlbWVudC5sYWZvcmV0QGNvdGRzLm9yZz6IXgQTEQIAHgIbAwIe
 AQIXgAUCP9siqgYLCQgHAwIDFQIDAxYCAQAKCRCxGF+PByO6HT+eAKCBj8MXtxmq
 l0PuLGLnR04gnauqPACg8Rtgb2XwCrgcZFcjS1Fl7/SmTE20QUNsZW1lbnQgTGFm
 b3JldCAoRnJlZUJTRCBjb21taXR0ZXIgYWRkcmVzcykgPGNsZW1lbnRARnJlZUJT
 RC5vcmc+iF4EExECAB4FAj/gQ+4CGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQ
 sRhfjwcjuh2wLwCfZ0Sqh6DY5U2ZDj+JrdqX1qzEaGMAn30UALtH14r1jMPPq6xn
 UuMfFjyLuQINBD/bH4QQCACbO8LantesOQKcxZS6WPSLhIoZerdMJ/b4DCd22GGu
 IM4eoWiYPX73cTMbN9cTEObaA0hvXEdn8vWl9/RBV6aL/fYhAqTVGWhXu6MBJiAv
 0zFeliJl2+7MqzZjjr8GSFkhM3tXEzFr+7r7/Bqnp8hdzMFUS2dLcL+ZTXJuq9s+
 xUNnwt0+Qy13VQU9whTZNZy3PHHa3XRc5IbZ5FnqMM3D7twlt0sS6j253b3CXw31
 qEREoLutw25X8pbQeYJW8st0xIEY9z0MikBOJvKPAUani5+eWjuJC0FlXYM4qSnz
 zhBpDbQBuhQu5JgPPiXlBq+ta/prm6FyJjcK+EyJsMGnAAMFB/9DIGugG/5F+4XC
 dTvFluD8zbP6zwqWRuHX9JmA+oso6ruDHiZ+Ckdz0xBfD8yoyENIRnLmBxx11uZN
 upAlM2itsvAwHMm6zKGLwlN+74vhoCTzvDFtnyTSgC8as4kk4XCax2QMAueFpW+2
 8/SSLqIK2UWT8/5SkP0QaN5qSFgRwhGxYgyVP8pflrjL32u+fEwo8EjNnOUHX4WY
 uzdzq1t+0K2AnZH5TiUCPy9iLP8o3rBm89Qdh45wzqN9DOGePoc0v4opQK9+3TRa
 vYAx6izrRajiGgUHLcYeL2nQxyi3LBkKvbp4Bw/dpxGTdmPhtyU8jYqdP5SQbrFJ
 4DwXqs4biEkEGBECAAkFAj/bH4QCGwwACgkQsRhfjwcjuh3mfgCguHMdGD3Orm8e
 pAU+aCOCPVkkx7AAn2yhe79FYbHDx5Dx2LAfRRRyfxjR
 =lVoL
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.183. Max Laier <mlaier@FreeBSD.org>

 pub   1024D/3EB6046D 2004-02-09
       Key fingerprint = 917E 7F25 E90F 77A4 F746  2E8D 5F2C 84A1 3EB6 046D
 uid                  Max Laier <max@love2party.net>
 uid                  Max Laier <max.laier@ira.uka.de>
 uid                  Max Laier <mlaier@freebsd.org>
 uid                  Max Laier <max.laier@tm.uka.de>
 sub   4096g/EDD08B9B 2005-06-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 11418 characters]
 01jfP2YAn3DLpgqbfVb0MZfxffpFg3K6fWkX
 =jGQA
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.184. Erwin Lansing <erwin@FreeBSD.org>

 pub   1024D/15256990 1998-07-03
       Key fingerprint = FB58 9797 299A F18E 2D3E  73D6 AB2F 5A5B 1525 6990
 uid                  Erwin Lansing <erwin@lansing.dk>
 uid                  Erwin Lansing <erwin@FreeBSD.org>
 uid                  Erwin Lansing <erwin@droso.dk>
 uid                  Erwin Lansing <erwin@droso.org>
 uid                  Erwin Lansing <erwin@aauug.dk>
 sub   2048g/7C64013D 1998-07-03

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v2.0.17 (FreeBSD)

[encoded data, 19998 characters]
 Ae/NaLI=
 =l+7U
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.185. Ganael Laplanche <martymac@FreeBSD.org>

 pub   1024D/10B87391 2006-01-13
       Key fingerprint = D59D 984D 8988 7BB9 DA37  BA77 757E D5F0 10B8 7391
 uid                  Ganael LAPLANCHE <ganael.laplanche@martymac.org>
 uid                  Ganael LAPLANCHE <martymac@martymac.com>
 uid                  Ganael LAPLANCHE <ganael.laplanche@martymac.com>
 uid                  Ganael LAPLANCHE <martymac@martymac.org>
 uid                  Ganael LAPLANCHE <martymac@pasteur.fr>
 uid                  Ganael LAPLANCHE <ganael.laplanche@pasteur.fr>
 uid                  Ganael LAPLANCHE <martymac@FreeBSD.org>
 sub   2048g/D65069D5 2006-01-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEPHZKURBAD/4O6BhuBlZH0ptJMLl3p/A+Ts0gBinSPtBL0tA82TBSm2uFRd
 8ehlKBMwyNQg1coTJWW8omEwAb+o4E8vwS4OOzzSCesNMgnXganMEE/STapgbXvi
 fh5Equ1GEeYyFvj9jaUGVoy1OxQzRAmVWtsV3RiV+mHDrBSJjLkS1CdaiwCg/RDB
 GxVmtywOwdmahcaHZb+dMD8D/1j417FsO9vnsenyS3fjLRNJJuIBevyX4WFqn9Bu
 fpt9M2l1C7YXvu4TMGkobUvmMsyEoPmQKAm66ickDUEnrwsLGzRWJBN/yoN4CSoS
 vqS04f59qObOfJa+a64Lg6Y5EGzzqnQvQK1A8Fdw1uSXAcauzucEMyld4sOsIEXi
 sLuFA/905RotLj6DVEl70+z3in4J64G9lLWdwOVmlANi8zUpIVUYobTJOMTdT7zI
 xNhYcjYqIc3WIAJycCJPMk9hk9SCra9ETNcU6GkusmyFdNr5YmRSRnz0etlTW6rF
 P7Dgj9b/jKMPh4NHJ8+cO77EPCsN8tz60LuMLXRboHAdrAi5j7QwR2FuYWVsIExB
 UExBTkNIRSA8Z2FuYWVsLmxhcGxhbmNoZUBtYXJ0eW1hYy5vcmc+iGUEExECACUC
 GyMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheABQJMmnBZAhkBAAoJEHV+1fAQuHOR
 SloAoNpk638zaargeIyuzTKfV3OEt8bDAJ4oXhCjGOmIhDbIjILHQLDG9ozsV7Qo
 R2FuYWVsIExBUExBTkNIRSA8bWFydHltYWNAbWFydHltYWMuY29tPohiBBMRAgAi
 BQJMmm9xAhsjBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRB1ftXwELhzkZ/q
 AKDyek8AbHNoIEFU4aKj9ZAxCyy57ACgtCnaOXA8TRY4ehdyAKHwwYROoJW0MEdh
 bmFlbCBMQVBMQU5DSEUgPGdhbmFlbC5sYXBsYW5jaGVAbWFydHltYWMuY29tPohi
 BBMRAgAiBQJMmm9OAhsjBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRB1ftXw
 ELhzkRNMAJ9gKkxH4i/zQvgtw32ilPgyVvlnqQCfRDI6ESnizQdNyXWwnTbzXnD2
 Afy0KEdhbmFlbCBMQVBMQU5DSEUgPG1hcnR5bWFjQG1hcnR5bWFjLm9yZz6IYgQT
 EQIAIgUCTJpvXwIbIwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQdX7V8BC4
 c5HzwgCg1hCgLsdxVIT6kx9/ejMcfITITJAAoO6xYuVfkCBk0lprOgAWeeWXsP5O
 tCZHYW5hZWwgTEFQTEFOQ0hFIDxtYXJ0eW1hY0BwYXN0ZXVyLmZyPohiBBMRAgAi
 BQJMmnSxAhsjBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRB1ftXwELhzkS7s
 AKDpM9SQcvBVkmHQBrb0B0ZaRMIU2ACg6NTKumOvbvDgF49sRaVXHl3WLZO0Lkdh
 bmFlbCBMQVBMQU5DSEUgPGdhbmFlbC5sYXBsYW5jaGVAcGFzdGV1ci5mcj6IYgQT
 EQIAIgUCTJxEgwIbIwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQdX7V8BC4
 c5FD5QCgyc4QAoRqHFkyCcPIn2Onyh7OcLAAoIahqNOxLn6qTNKHTEc8uhKauHvW
 tCdHYW5hZWwgTEFQTEFOQ0hFIDxtYXJ0eW1hY0BGcmVlQlNELm9yZz6IYgQTEQIA
 IgUCTJ02PQIbIwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQdX7V8BC4c5Ga
 NwCg5LZThwqJ5ArvQVRDlgJDAub1jWEAoKUE1GjKMNd3y9H4AFAqr/kukqhTuQIN
 BEPHZMIQCACJjfWn16Cg7jpvy/SsGAulMEcLI6Glkzp+g0/JyYvNfvvaRGX1hJNw
 6pr1u0yU2FJuZo5b+avZu7P7UnCu2ZWRk8y0WVNHG5lie/jPy0rQBF/DhP6FVqk/
 TdcDECa1Ncp9EE9vCuZGvEgzjvzgxhQ06/d6Rtzxy3C1P79c0j661raPeWzX62M0
 Cj0a0ljdvvm25hv41VT1GAyX/punhrhnBiZwm6UGVu9SQNsOD15pWqMKD26lpwP9
 qA9XHnsOknL3yXl542T9BWffZh2I8OUE0XL1LSSsoPC6a7wV/Vx7cgTDLU3Pv55l
 ERY0p8uadTOCIu36tPkmkuJfoWJF4OQfAAMFB/9YTQ1dN+c2yl8C80VJO07wdNln
 VKQNcCKtuIJXRygcqC4gj8EI4qMofuJ4JTSWdApJjp9AgxFWol6AyYnW6oQU9A3D
 GVfeCc4MpduCFpdnex4U82UdwPB8905kAmuH13OIV3vIEqknpqaygDrJ95E1rYUQ
 lHzlQTHk+JxdqeDvvQfmrLRhPzgQtlukl4wjy+Kbp7Cr3X247c+5y1iAFCJ+o+VO
 dSlNlckHSWbV8yKvJMy7iF/HfvxJmMR1koU+SvCuOcL6A/CvS0JdLo6gIJJwRHFb
 +4iZBR9UUuU4AQBH4HIeSCFREczk8BTIPR/97OQI7FmGUSFTafxLHrww2p/3iEYE
 GBECAAYFAkPHZMIACgkQdX7V8BC4c5HIQQCdGivImEAN/fic1R59mKWpF2NRNJwA
 nRUyAyZp4AGCki3wKPxtkeS0295b
 =DB+6
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.186. Greg Larkin <glarkin@FreeBSD.org>

 pub   1024D/1C940290 2003-10-09
       Key fingerprint = 8A4A 80AA F26C 8C2C D01B  94C6 D2C4 68B8 1C94 0290
 uid                  Greg Larkin (The FreeBSD Project) <glarkin@FreeBSD.org>
 uid                  Gregory C. Larkin (SourceHosting.Net, LLC) <glarkin@sourcehosting.net>
 uid                  [jpeg image of size 6695]
 sub   2048g/47674316 2003-10-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 11352 characters]
 Wl3f9A7RglYuxkgxVKnWlXgWtigAmgKgQFhgdX1L2lIHUi27R3dYoD10
 =VNnr
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.187. Frank J. Laszlo <laszlof@FreeBSD.org>

 pub   4096R/012360EC 2006-11-06 [expires: 2011-11-05]
       Key fingerprint = 3D93 21DB B5CC 1339 E4B4  1BC4 AD50 C17C 0123 60EC
 uid                  Frank J. Laszlo <laszlof@FreeBSD.org>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBEVPgQYBEACvR8zsof8gLi7pF4331BIVluP61Z4ICzkg2lWLB0Gj1feCbBcA
 neds8gqHJ7vxArQeYTBV6Gefk4mvCecxo2LGFEcsDuns2X1hf1pXz4AKvtYoVL0e
 ytW5s3bRdxX+gekv3KxVQjv4tJU2surbW0Hv17Z4m4ZbRfn17dzvpMwtiZmP3kMX
 N0qAeBs4MZxmWhfYHapc8du75XfpvvD2W4I9VBJXd6DLKNksjq0/Ih3Ygh4kEVxH
 6xQT+lL+6yVWTl8XQpJs3u0OPpY/dVjI98DaZucW/Lkh/+uxZm5ndExi4bFJ40rY
 KfqCsbGAYPOj4HKDkcgNZu+MbC6nIuIuh/eK8ZIpSlSdkzJ2r46wOBHLUJlJoxH/
 P4Ly5cXu5lUX2Mf8/HahPSY++5xIoSI1mpqruJyQZxhF4J56X1Bn0BnMmFt+uXF7
 O8bjQi4XQJBurcSkAuBnTQlohuAXDfIqeGqqMN6iDGTGCOL9R5WZ6nasyDL+qPA5
 WK/ooxINQWPWbTikYb3PZK7v8ABBj6TYAAGxAYrly7boIVKxYUFbotH4Y8dmXUEr
 p8Hj+tFZCk6AKBn/lCLsM/vTs0ylaSHJOhQc49fj/PETGSQLVjd8iH0l87MfLd9i
 iLnd0m/Y+ecCobgQDGnDQiFqvsJF6VI+/bisOJiE/HdOyo9j9K3jJ1l4gQARAQAB
 tCVGcmFuayBKLiBMYXN6bG8gPGxhc3psb2ZARnJlZUJTRC5vcmc+iQI8BBMBAgAm
 BQJFT4EGAhsDBQkJZgGABgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQrVDBfAEj
 YOwJtw/+Pe7qOPCqTUyi+w9k0829sinZIkLxpqJPSzzYaHQ1QGIOg4wO5yCER49n
 Sp7V/S1cNKXTIR+YU2Pf2dj/s7Ot6bRXl9dDnUgMjkvNEEIO6a9gazZSfD6+5ECL
 DFEcJ6n4En02dCjsZQ3uR9DITAZcd/Y3Gczaplwd9LHpUoh/nG1Dj02+6fB0E1wQ
 ebm518PDvbCaQvggYIPc8DvS5DO3GSRLQ64a2bILYOP1UXPGn4X/0yoayieyO6lD
 HFA1gVCROtgG1II0ylDWH+Klp4nAyRcqoYfF5kHWsvQS9N27gf90F0XEALjxCCEu
 Osy4rtDvg1mU1AK0eflyZImJBFfEOXZrEM2TYo+H5X1KLEMlCzgz/5MoOQ3F896u
 K1Rb95LuF2BJOJsnYbHTEURwloif0U5VIbuH6s37bVjkXDbHcQo1UGwQM/v6tPaG
 YirZCgh+NpKChuO43XvQTG7CL21qqten+DOh6MBPtBK9TeZIeuGPiUkS1WcCwRbp
 QwmK2wZeVaZKReqLJO0QXq06dgd4iaiN7W8p6HZe3LYbnR5d8SWyPp2RQxESOOF7
 3atOTQXB5hn+pXuHpH1qKK6RkiD62pMd2RgRJlCdKZXM5UKjpAV7w/k15qiZuZg+
 N0Jkod50e8O7CLTZdXTTYpifOkjdnycBY24X1Ra0IqkTC69zPrs=
 =xm1s
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.188. Dru Lavigne <dru@FreeBSD.org>

 pub   1024D/C6AA2E94 2013-01-22
       Key fingerprint = 6CC4 2180 F27C 29B6 5A9C  EC0D A454 DC05 C6AA 2E94
 uid                  Dru Lavigne <dru@freebsd.org>
 sub   1024g/7FAC82EA 2013-01-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBFD+vdwRBAD2rMN1ZfqBN9PCvrGHaatVwfORzhr6gSFFjxk5Z6HhnGsQSO8r
 NAmU9wdINOXJ2M9tqpDXV7R9nEHTvcvjZ4Eolc+fNwGTpglpDX8F8bp5VaQ4+aW5
 nwDs+JoLw94MSfbrviXCDe73Eyp4EGMoZ7PlVwvJ8oloIv7T2qtlAeUlRwCgjH4v
 BOGZab9uoAqaBzMYk13FM/cD+gKe8+bewQyp8sthXrZWYbyyyIu0MdfMxpRZ45aU
 eDrxuZL536qvaiAy3DmnF/nHkZX3/6XTSlkgyQbzLnI9OZVcDFA/Dke5qVk+xUqp
 Vyei9HNOsS3u/Nn70HoFijsYUq+hY7aefxoMtJfer+aiJNJRj32DvUP/ZdeJ8jCQ
 9ZtdBACEmRZ2UjYYMklBZdp71/HFLc+0+hxl7IU6H609Fqace+aCKRrZZ1QzzNK6
 /DEnR6BYPN3eSzMoLLoAvLIzpfaUx/IfHxbyjCaXi0cYYZ9FkUUt7a3qJLSZGnK2
 tA1Fw3kFBBO60t9T9cQXHv/sd3bXmIP8eUe++5dfJ5UmmK1f6rQdRHJ1IExhdmln
 bmUgPGRydUBmcmVlYnNkLm9yZz6IYgQTEQIAIgUCUP693AIbIwYLCQgHAwIGFQgC
 CQoLBBYCAwECHgECF4AACgkQpFTcBcaqLpThwQCffhk585hEfh9LHkYzVZIpu3DT
 cqAAn2BgkvA9qN6qJnDtpcKoQh+nnjCeuQENBFD+vdwQBACc80FRBODUmXvpVKxZ
 ql/tAKl30ij0OVLHLdQQH4W3+LuO0U1Uxle5IbwQHfZh6KtyH1AwafBLZ/lg6ihh
 ImtvvlAoPhGqeKi2L08djYYRsaQl8snCPrcwVtUiAPqVXCkIFzmcA1dlFRUg68re
 /f8uSKt41FqtkR3v+QsHdflOHwADBQP9GaQUxdrLssRNH/fEkMg8xZYLGOOg8hcX
 BwNujIol+Yyq5QZFMZxaFbmdKhCnVH46cOFheHpgRQcwfoMLk4yfZkmw4W1ANyI6
 hzzFHtnSLYG7CGkgQE6NS+bjTAxVWGK48SsUxS2RcxPAQmLqTEHTgoav43L/6gAY
 N2QsQo4b3NmISQQYEQIACQUCUP693AIbDAAKCRCkVNwFxqoulMOJAJ9VIUzfi5Y5
 GN4vvJ8KQE4+RZBRLACeOgRRbnd+Xsbu2V6mez1KHF4UUVw=
 =lVUC
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.189. Sam Lawrance <lawrance@FreeBSD.org>

 pub   1024D/32708C59 2003-08-14
       Key fingerprint = 1056 2A02 5247 64D4 538D  6975 8851 7134 3270 8C59
 uid                  Sam Lawrance <lawrance@FreeBSD.org>
 uid                  Sam Lawrance <boris@brooknet.com.au>
 sub   2048g/0F9CCF92 2003-08-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD87mDQRBADpSK4q7J5JpjHMPdlp4ieo4jJR9V63tvptpBOAk/nuhWnY3fpu
 Z7pcxOy5I5hZDIu2kn2zkBv4CTsn9yxdWgJaSKU9nQMYpfFdCnajo0HTwV72+7eK
 u86VDWZeWuuUIiHVNBUILClbOadmRFDxuCCjyE+V97o4CiUu350M28YdBwCg6LE8
 dpO9NELy9LJxyhPBE51iS4cD/2CdsCXzmKaFTa+w5fCOSBzNv516qY1GEkNvmDrD
 e3dgeyxaembidWjjU2vqOZmWFP64jgayvyFZChGMlRab78GKXH7DIGGrXWp9v7B9
 JjCqDyuX3NGaxCDFUNJYR6nt7Q93sAT85oAV9EPeFFEx7Ksd4C1iKlGlohGwleb5
 TCngBADX+A5DR9eI9E8loh9NmT4HVzvjk9kvk/vq9i0MqxgcEBodgRPibVKWTWOj
 MR0T+3qOzLGiVjIL2FzVF1na27hGJmXupxU4dWoKVGR85JYNOoFBNuR2HZsim+iy
 sX0gK6ejsxVhhx6Q+CQgCQ80TzuY/dD2qFuOGkda0P9Ro62yt7QkU2FtIExhd3Jh
 bmNlIDxib3Jpc0Bicm9va25ldC5jb20uYXU+iFsEExECABsFAj87mDQGCwkIBwMC
 AxUCAwMWAgECHgECF4AACgkQiFFxNDJwjFmBaQCcDJfb0SfPgEimiFVhsQOJccxJ
 F1UAoKJrgMOoY10RAqM822JzOnn9mGXutCNTYW0gTGF3cmFuY2UgPGxhd3JhbmNl
 QEZyZWVCU0Qub3JnPoheBBMRAgAeBQJCWzEGAhsjBgsJCAcDAgMVAgMDFgIBAh4B
 AheAAAoJEIhRcTQycIxZWoEAoNefUsJBBCoZSmfVIPEh4g1oDmOFAJ9H6Q4/hfh4
 hFTLxU7p2bLgbdjGHbkCDQQ/O5hBEAgA5LFaiwqsnyrdVB+Y7S511ZPmQOi8UwfQ
 04PIWyt9a1MwGSYdUpzGAieMLe4KG6olMlLH0X/qxkVjbukwPyybeN7RNUZE1DD7
 KGbVOWpyQHhAB4EPfzRJFYQEmT1x7tk0nVbF7emuK9iG+Z3et6Io58QjOgyEMLYU
 UjwzCE2NYjJmMLEy1e+icfEkOs30s8XPrus/GNffVlsxmHEzxtsicw+AVnlrjLtG
 xZ5DsNRqJM14L9X5qR3O0dq3BnKGZPOctIF6bRv0AC9lX9kQ1saFqv8iEHoHZ2vD
 2eIplYu/bviD+lI+w6zrq/KgNHQ1n9ngzs/N14lN9C57dHTS7U9nJwADBQgAhWSk
 YnYr5vUskZgVmf0joVgYNBqXIBKo3qXx0DYxGOT18EbKhtSYCar4Uhjob9fUhQop
 nEd00GQVZwDTL3/STCXUUSaHRJhK9yCwgvQ+/q58yW1JvMrCA6uaca89y9DnfWxv
 0lFbOdLJJQNrgLCyNweLhZcEjOSTQO6EZB5OX+z4Dgfxd/5DKWr19JKw54Qtus3s
 9zZhVoQoXzWiDlYdtuGUjnVQvycegOxwjFN/TP9IQpQS8HFMfEu5GLTbRAQ3zirS
 W4FtGaeI7cUqap6ot2BRd1prAXyThXHxYAARaYib/xvCLRDTfXCHgJXbqEiJ72Yy
 FgGYqFTRrTTgxiXo9IhGBBgRAgAGBQI/O5hBAAoJEIhRcTQycIxZLQgAniGrL6cw
 +rQG5xLeJ6hrbllYV+8cAKCmIpsp54t97HWvJTKN9GhbpQhojQ==
 =iBxM
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.190. Nate Lawson <njl@FreeBSD.org>

 pub   1024D/60E5AC11 2007-02-07
       Key fingerprint = 18E2 7E5A FD6A 199B B08B  E9FB 73C8 DB67 60E5 AC11
 uid                  Nate Lawson <nate@root.org>
 sub   2048g/CDBC7E1B 2007-02-07

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEXKYeQRBACVxgl1l+IwFK3aZ96X+BHzeUuGfAAWSqzZuJq0rVXhUU0KnGy6
 r2HLJKwGlSQ0tP7rsYy34fDZy5BB1JajHNUIhb5SJFZH3VltQuZ3mnaLWJajm4Q2
 c3TRBVVFcm4y0x/QiCcz3JvCUWHaPUUWlpbrkt57O5NTVlneOtruZtYPwwCg+3Ft
 WjNU4ppXEbbsLHsIri5gPCUD/2e7RFkq1KaaqA0wfwictFgxuOZX00Do1kIFfoE6
 0jKSxU3P8E01H68vZs8vGuVOLVE1pXoWoJa68zVOWkLCTE1z2U5YJumZL1mDRRHt
 VfqlsaHNBLIRd9qAZsj3F5aSFu1/hCOiUkgLWQa9e/BAv76L+mCIJ+g5bU0YTEhx
 XoFwA/9dF3JFdQCkrzbhS9/BSjEIXDCl7e9Yt4/6jTg14fr9Pb5hyUYYxu6i5v59
 TgSdxSFUd3MaZmH3Kewg++9oqewNEYdOu/gmx7GiSKr3k0FlX+aK7UsVDjEr55Gi
 XH5pqUce7y8bmx03a/pa0Lq5WLvPnfUaplWeoCmmAXeYmRFYqbQbTmF0ZSBMYXdz
 b24gPG5hdGVAcm9vdC5vcmc+iGAEExECACAFAkXKYeQCGwMGCwkIBwMCBBUCCAME
 FgIDAQIeAQIXgAAKCRBzyNtnYOWsEUGfAKC9mTqJd/PjHdTG0YZkBr0Y0PLmCwCb
 Bl/VHprr5SrFDBdZy+vB5GIEhme5Ag0ERcph7BAIAJKt5PBfx/CEqBDS+JkDyYLG
 RA3johtfG5HPVPOX1iFJgDLx/5ZKIsK3oxJLkkZQDBjzJgU+GcffBwafaTObEbid
 D2rtwtqfM2EgoSntvJhrP09Qfx1/MOZs4MVJbGEec9egMgFRzUSKZ2xiYNqKOWL4
 dL0TOyeLg7HQne1fuOOFEJZJtCxHAm75z6Q8deYHr7bQQ6NZuYc2qsOLjBX+M6Ig
 d+r5p3vhkeg0uUzkRR9bAmtaDT3BFfxfMG0b4iTBpDW5UQ2Cp0NG+SAEaXVCYNcA
 kKHZGTTI9e6a8AimsP1wOKs1TsE7WSLsk0Y1U6E7OuHLdmGwZygipfkUXR5v/hMA
 AwUH/jLrMCAzZaCh6m6mrJ2HYCASRSfGKAbmfqPymEICfZ3Y+FeCCFopeatMZPyE
 R6gEzHyu1hlSHV6yTfxRDV+gO6Pl9snsucJtD//ZnfNZenKsFoGJM8qu758jBA5m
 FY5bTlkySmFJYHGAtpMap85j32iA3B24VmgIZ+rE/YVQUbbkaFrKN7Crvm+PgH1u
 xbLrkjypklyo3iZZQo75W7SobSvyqnG3LRXkXsS1U1m3QWcLqIjKZTrrhbV3IIRK
 +A0rSRKXpDt5lOYIqbJ+PwwGexlgzb31vJa0+N8qjdvbbMZIOA7mDVauEYsETkU0
 Wtl5Rc1M8Qx2IISH+K3AGXHqn3iISQQYEQIACQUCRcph7AIbDAAKCRBzyNtnYOWs
 EcVTAKDj9JrwUwygZFNG+oWsOA3/ikA7qQCfQkYnj9q6E0Z21p/ZTDptic+qSEI=
 =yO1b
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.191. Jeremie Le Hen <jlh@FreeBSD.org>

 pub   2048D/8BF6CF92 2012-04-18
       Key fingerprint = 66C9 B361 16CA BFF6 5C07  DA0A 28DE 3702 8BF6 CF92
 uid                  Jeremie Le Hen <jeremie@le-hen.org>
 uid                  Jeremie Le Hen <jeremie@lehen.org>
 uid                  Jeremie Le Hen <ttz@chchile.org>
 uid                  Jeremie Le Hen <jlh@FreeBSD.org>
 sub   2048g/045479A3 2012-04-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 4488 characters]
 UKKVCUMfZqGpV5v3omGhzzE5C56S6ilzU7nRDYwU
 =kKtL
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.192. S:o<<U(c)u <leeym@FreeBSD.org>

 pub   1024D/93FA8BD6 2007-05-21
       Key fingerprint = DEC4 6E7F 69C0 4AC3 21ED  EE65 6C0E 9257 93FA 8BD6
 uid                  Yen-Ming Lee <leeym@leeym.com>
 sub   2048g/899A3931 2007-05-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEZQ5iYRBADg09p5ljHhIDwhH8i265BFEL1AyW3EPEOb0CyFErp3K4H7+IpG
 FeaHUrB2i4MYs2r9gAMHadBMTXZJv7ECq2AUQfm3vTKeBjVVz/N7jsEDcmH6bObY
 XvfRlp9618IBRCDdcbD3Qs0Bv4tM+e0oNYBTsOWAO+bfpHYPk5wORxq6ewCg8DWN
 J/THLd42Fd4HTfxTC4tTa6UEAMPz7iASUbyJr7//O/Uu+05MBKX8wuNdrH2XPUWq
 MwLcgEpKSFl0xjpJUMpr3eWGvAg0Vz1UzxDUvZUwbj/5nXh2olNoMH2LQY0QwXGG
 TPudevBeJ6W+UaEGCAH4Yy25hxxr9h8XI5KRlPCOjQ8i6H+EZbLRTLgOrvBWvD8B
 Ob8dBACGxoySAQP+leHIe9nrKyZ00tkNI6WPEPAG+14yiCgWLJnWKi7maIHzjG+1
 1Fz5+nyMUtHofmLvNyDA/V1e2LFXDjH3v/PcTCQON8EnHAoYmqSRAZMBMmDpU1Af
 f/vbiOg1zwhwAhdO8y6GZHcJGJjJ8lJYs151ehSS2Oa+NRCfH7QeWWVuLU1pbmcg
 TGVlIDxsZWV5bUBsZWV5bS5jb20+iGAEExECACAFAkZQ5iYCGwMGCwkIBwMCBBUC
 CAMEFgIDAQIeAQIXgAAKCRBsDpJXk/qL1q9tAJ0fy0MkFt+hNcvb0OMqTRJvjYlB
 KACgluazpF5ATo+dNtJifOd8kMBxB+C5Ag0ERlDmLBAIAKOlmONAuOtrVXvRw2gr
 wYNA4bjQrv44PLCMGuicddC1S6+Ngp+F2bjq43iyDk06i4eXBop0uqzkGA56pCVW
 51mSLThl5q/1dixiLDOSy/9Scuei57KuP5MOk5GpFBU/OZv0R+1ZaK+718+jI8/E
 NGOt/rZ3ZaTR94rAn9yQzVp4prVw4F7r6Vrp9mVu2qgoYKpwpfuR4nw1kq80Z1R8
 TxtUrGFYSY7nRTPI6FI6fo6BVPMAw01Xh3oKfDfrecaNtNNgM/DvkrBvZsVHu3NO
 M2yAVL6LP/Sjv0uF1pK/WjP27hzvO3yha2KYS3oBu4zysyVbi7QuFvm5FmF0mKik
 JosAAwYH/RWHzWWtpgXdbMUrPxFTmFhXCVVuyiHG0h3bMZigKtAMcjjYRMenhiRm
 e5Z5si4VzzpaaZaVY6T7hmzM3cran4VH6dFdZy6qhBFzlJphpLwnJti/FMrF2CdY
 1kthUC0fxeEDPBkYvV1izBrPQ915XYXuXdJjbk/ATqeIKsqEHWSmTCLcLLtWn9Nt
 X8DWU+GHMbaMAbtEfL+i8vg0WIOeSE4tlQwIkvSzfXh6Rysr7NtOuYzADD6ORRkg
 Q9K802n7IYXqWhZTWKijXpf+n+NzWdXC/1UZambcfo1gcS1fotmrO3Fmq3+FgJ/A
 YPmudGbHwUlAXVfJ47Atxggoe0znf5CISQQYEQIACQUCRlDmLAIbDAAKCRBsDpJX
 k/qL1tpnAJ9MKjKh4P+ePXeQ+yIwfPza+MnFcwCgvVONrkQ6Byi+tZ1ilTlKR+8+
 xnc=
 =XiOT
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.193. Sam Leffler <sam@FreeBSD.org>

 pub   1024D/BD147743 2005-03-28
       Key fingerprint = F618 F2FC 176B D201 D91C  67C6 2E33 A957 BD14 7743
 uid                  Samuel J. Leffler <sam@freebsd.org>
 sub   2048g/8BA91D05 2005-03-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEJHnP8RBACRTtM4Fb2oRITEwfTLIKSa5Mk0m1A7Pitd1qkjtAyFCi5V6uF/
 2FXPP3Ux3M8xzrvkQNnWkYvGh5MSgkkJ0nszUvh63m5Lp1Yr/EMQr03v1HfqGKF2
 SALv7eVJ3XHEEGsYq6KOcJ+2n3FkL6bwGXkXSya85a+EwQ+/aBhpEOEKwwCgl4N4
 oTMEgh2Z06ZkMJrqbf4/P38EAIAN93nvAN14v41zw25b4USFzqH/JFTG3utAVxiB
 NgTEkD+OkktxJFoTrZxfxoU6Od4tl+yIyhKJgj/QlH5pA/mpMeaXh+TQ0/EQAzml
 d/sw7vXV3WJ+zXIZeh51yuHBY817e7izcnfmY33UrOdf4DtcplmUrfQd1eVMSo45
 K2b3A/9a0tg7NhdfkL06b97oyKb0L8F92Q1sO6J5sgsEjNrUVrFnNU0DIDgbi/0t
 oBpnqIDa09hhBJ1XYcxU4KMxBLpuIeuk2cDCUCVeeEDmx98GIss3hKO8YWzB40y6
 7vtdh5lveaNV4+CA2xL/cDXscl+poRQA5tR0efR16jckEaEcVrQjU2FtdWVsIEou
 IExlZmZsZXIgPHNhbUBmcmVlYnNkLm9yZz6IXgQTEQIAHgUCQkec/wIbAwYLCQgH
 AwIDFQIDAxYCAQIeAQIXgAAKCRAuM6lXvRR3Q7whAJ9e9jjfVscKVirvWN5IM2j0
 60Q50QCglAppekJH6jWStTwoq1EroBFPKUy5Ag0EQkedCBAIAKmxNvJW/W+PrE+T
 JjKw6dbqUqAUNIGWnr6xgL7KYBpx5eo0XH3RCVzvRSfboA1+nXauTn/FhOtWMw0J
 dkHrMQhxKSDhWOxeftKuiRiVLPXxF7PX0JMOadxOuqNSt1VWcuTxxBB2wva2Rb48
 JscdFbT2u7+PHNarDgUnEobobdvbzh4F1ACaesUq4s2y8jH+YJTaBqJJuZLjLwti
 C2zv7skf40I5ldud4/7ARGuumpjTrqZFQeQwPKX975X+jw5SBUJXA1ckKcgTp0s5
 Yk+O5+yUkt6yzDO+CAYEaZ/xfpOhwmqSIXtdo+ilm2q3y5l+nyEVidYncRWRWYyO
 iaXOJdcAAwUH/0Ixl92WezOXBqMrKVaA+abCN6t6n9zxSnwfVo92Vlfqj8Huz3Hk
 55e1in3P01xXdNKnapYNkCg70WbtNQtCh0nJdGGDEWVqJsjiqDDMYa7QLahV7HPB
 RyOtoAXnTWPpyk0d5WEXPLJ3vPjxqv5wKTmav3JcvVahSVWi2wmWAgfQJXYRvCU3
 EEQ5KqtCBrQNdBsSRnzgDsMY2kAh02VuGTbkVlQz/rI7HAYEOL8SoR489O/MTE+b
 5HtUT70rk57/3jR3QtiH/3Q7OqnPh/ATjO+pnPuhfqHiQWLWRDigJNheH/B+1Hmn
 sHiSWrUmlaI0bzyIVW4Xft3nu/wH3QVSSWOISQQYEQIACQUCQkedCAIbDAAKCRAu
 M6lXvRR3Q1SUAJ45iX7Ka9rb5pwAmY+fyfpuO4qgJwCfW4VAl3+NLCCP4A0Y8wlb
 UtEtg3M=
 =kR9a
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.194. Jean-Yves Lefort <jylefort@FreeBSD.org>

 pub   1024D/A3B8006A 2002-09-07
       Key fingerprint = CC99 D1B0 8E44 293D 32F7  D92E CB30 FB51 A3B8 006A
 uid                  Jean-Yves Lefort <jylefort@FreeBSD.org>
 uid                  Jean-Yves Lefort <jylefort@brutele.be>
 sub   4096g/C9271AFC 2002-09-07

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD16LoERBACHLA0g5LE31OgOwlPPpQHnOciC0S7/mTj+XBGMi3uS8ts2K2pM
 biEm7+xsyakCP98ucTs/OQmCizSrqMRJbCSX6TW/qx2hWw+QREZWZhTL+3pRJ2eX
 ip+wyuOuUjlFJ28fIlil7XPAv2ly4tP6umC41+jT2BTgQObegm+17uzsmwCggCZg
 VopF7lI3hUtJd58PTatZt/MD/RLMBRG2eZYfOGpHLF9jg7AoUNouMFSMADyYRLwS
 vlUrcR3HlwjqKq99WucWCAkneBym7yRuNDUeZI1VBxasG8/KQKL9mEB9iweufSiT
 qF4v5Hk95wpkbE4v2jGvLsvzE1D0Jj4fJgdm+Oiq/wrFIYeL6R2gzbhLn96X313x
 appTA/wJix+jwlo8cgvmaCrJMVcHlaCiSkDM1UlKDQSPB5VxXazeW4EvN9YpIr54
 aWzQ5elL3zhGfJZwtY+KwqBWeaHrvE6VJ8kjl9Ol0+VP7MObgfxgb9VB1oktKGuL
 zbeVnCVZXbaqkxeym9kB+VUJPYJJiLGOztUHBjvxGazIxTXhIbQmSmVhbi1ZdmVz
 IExlZm9ydCA8anlsZWZvcnRAYnJ1dGVsZS5iZT6IWQQTEQIAGQUCPXougQQLBwMC
 AxUCAwMWAgECHgECF4AACgkQyzD7UaO4AGqT/ACfRmyJHE6XFGGVvNU3Gx1E0vpe
 scsAn1yHaROu1BCUra0S4BNPVidE50iitCdKZWFuLVl2ZXMgTGVmb3J0IDxqeWxl
 Zm9ydEBGcmVlQlNELm9yZz6IXgQTEQIAHgUCQlv5mQIbIwYLCQgHAwIDFQIDAxYC
 AQIeAQIXgAAKCRDLMPtRo7gAahOSAJ4qAsR/hQO7F1SZ8CrRqRQoz39GXACeJxqC
 bP08SjMi0oW2ZGGQH7A5oH25BA0EPXovJBAQAIf12QdmBkGQYGGEBhmFUk9XU9Au
 9fxbrEc94kDisD2zpXPRuOblVTE2lVNaxXN/aVdf1AJHtpexdKjc/opvIa4TJuTI
 vBA5gZk6AEpkAgJYHme3joJIHJtyHEms4HNO+yvnYXBGmFTkc/ak1o+rBwbWkvUw
 IbksCSBpUWolzyThbVrRR5P7+HNsp+RcKgo8dJsU7SaP6VVmAIBTWyObXZm+eRpJ
 yJMnTXUxWz7W4ywvMu9OF6C/4e4x+ueBQJ5xYRpyZbEol0BdiVQRoxEnsc1I2S4A
 c5YWZuMnzRtkQV4mQfhqWrPQ5nLfVc1V5yp7PGyeJRAwIZCbTBD4wNBePXhTQ+CP
 JDVVaJW7W2ComgI/1tjy9K5IYMLSXSmbvCg+A/qxEuhQQHPhlvZA4FLhxZaTZpXl
 EHyvxyLxridyRfRzmE6SVCA3eyr12ewKaTXimBmcRvP0vrt4nL/SS5rlKh6RsJbQ
 k0ETLBi6Zq3y0HIcA/8He2OSusyhgEBJaO8de9RF2APUOCcbt7Dz0f40iVz11pGN
 8yfFb5BW7XYwnprZbD43QXjB/N7lD7lTRghLxLl0QSLs7GoQj2fXQiGenOnhsMIo
 pQ0b8G8J2jCJleBBdNGQ2tedBzyUVgap3zFuy6yPIoKsip8JJNOJEz4WcpZrBJPc
 UE6VNqkUzb/MHcxPAAMHD/0f8AUCDh2x8Kv1YENpefaN8WCQw1NeSgZtLuPYg9Op
 7znNk+Xkl7WpZROz9s0S8AIGNr5BCpDxCg/AtdA1+fsiQXi05bV5N63LPQZNtLjV
 oAvsnyn+p/ZGVnW6JhfPedJQY62jDmty4dnYNYSZWvIXnVDdRILIgGGnPp1Or6HQ
 nurqIdKSnGIO1Zz00e5hGMPUsylsNBvesrHKbbzKbgp59cwvhoHk2oet5aK0+Ici
 aIcCaWyjCGH/d53YTIf5ZRx3glDWbgRadPCVZiaDGdNQenF6zAVyXiJOa912sW2x
 WcyhEa86imh0lfYSm1KJFYgnXLv33hlmQ2iiF4kBVk8Y6qU4BIDRJYDcPToNjmEt
 lOwA3m3gkembU8uxy3mpE1L/iNb73i68xwfCHlZ1LzCnUShOl8aw5fu7C3qcytUp
 t3gaD0TeHuqS4XIYBgDjNRPILW6e7IlK+3yQE9cLgMb6+vNQuHfkYr4TuRSUTWlM
 sWK2opEq/z7e3LWdJrU78yHTBTVV9Myf46JpcWE2KYrCRHk564329Jvfe+uByYSJ
 lCXogYpFo3HbaAyIjmcZDgbDHFaYnJ0dq/NZmK1rFVbBm2Z6qW1laG1X6ke+KcNY
 HoUwEqEkYeOsovwkH0veLxvfDzBGtp33V3OgVuYa6WA51tpJQH7KgTvh5ETJBHzY
 TYhGBBgRAgAGBQI9ei8kAAoJEMsw+1GjuABqd9EAn3E2CMMkEWdOtVjwTu+wWhuv
 3bMQAJ4soo0qCyPCVz4Y0Ly5jvYWToXt0w==
 =kszM
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.195. Alexander Leidinger <netchild@FreeBSD.org>

 pub   1024D/72077137 2002-01-31
       Key fingerprint = AA3A 8F69 B214 6BBD 5E73  C9A0 C604 3C56 7207 7137
 uid                  Alexander Leidinger <netchild@FreeBSD.org>
 uid                  [jpeg image of size 19667]
 sub   2048g/8C9828D3 2002-01-31

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 30360 characters]
 BJmDy7UZOmvcCZ83fBsMArrC8MkAn3zKySx5vPY/ocOMjEcB099D7B/I
 =H22z
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.196. Andrey V. Elsukov <ae@FreeBSD.org>

 pub   2048R/10C8A17A 2010-05-29
       Key fingerprint = E659 1E1B 41DA 1516 F0C9  BC00 01C5 EA04 10C8 A17A
 uid                  Andrey V. Elsukov <ae@freebsd.org>
 uid                  Andrey V. Elsukov <bu7cher@yandex.ru>
 sub   2048R/0F6D64C5 2010-05-29

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEwBF1kBCADB9sXFhBEUy8qQ4X63Y8eBatYMHGEFWN9ypS5lI3RE6qQW2EYb
 xNk7qUC521YIIS1mMFVBEfvR7J9uc7yaYgFCEb6Sce1RSO4ULN2mRKGHP3/Sl0ij
 ZEjWHV91hY1YTHEFZW/0GYinDf56sYpDDehaBF5wkWIo1+QK5nmj3vl0DIDCMNd7
 QEiWpyLVwECgLX2eOAXByT8BbCqVhJGcG6iFP7/B9Ll6uX5gb8thM9LM+ibwErDB
 VDGiOgvfxqidab7fdkh893IBCXa82H9NCNwnEtcgzh+BSKK5BgvPohFMgRwjti37
 TSxwLu63QejRGbZWSz3OK3jMOoF63tCgn7FvABEBAAG0JUFuZHJleSBWLiBFbHN1
 a292IDxidTdjaGVyQHlhbmRleC5ydT6JATgEEwECACIFAkwBF1kCGwMGCwkIBwMC
 BhUIAgkKCwQWAgMBAh4BAheAAAoJEAHF6gQQyKF6qmYIAI6ekfm1VA4TvqankI1I
 SE6ku4jV7UlpIQlEbE7/8n3Zd6teJ+pGOQhN5qk8QE7utdPdbktAzi+x7LIJVzUw
 4TywZLXGrkP7VKYkfg6oyCGyzITghefQeJtr2TN4hYCkzPWpylkue8MtmqfZv/6r
 oyqwTbN++E09FQNvTgRUYJYTeQ1qOsxNRycwvw3dr2rOfuxShbzaHBB1pBIjGrMg
 8fC5pd65ACH5zuFVA0CoTNGMDrEZSfBkTW604UUHFFXeCoC3dwDZRKOWJ3GmMXns
 65Ai5YkA63BSHEE1Qle3VBhdcG1w0CB5FBV3pB27UVnf0jEbysrDqW4qN7XMRFSW
 NAy0IkFuZHJleSBWLiBFbHN1a292IDxhZUBmcmVlYnNkLm9yZz6JATsEEwECACUC
 GwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheABQJMB/ruAhkBAAoJEAHF6gQQyKF6
 MLwH/3Ri/TZl9uo0SepYWXOnxL6EaDVXDA+dLb1eLKC4PRBBjX29ttQ0KaWapiE6
 y5/AfzOPmRtHLrHYHjd/aiHXGMLHcYRXD+5GvdkK8iMALrZ28X0JXyuuZa8rAxWI
 WmCbYHNSBy2unqWgTI04Erodk90IALgM9JeHN9sFqTM6zalrMnTzlcmel4kcjT3l
 yYw3vOKgoYLtsLhKZSbJoVVVlvRlGBpHFJI5AoYJSyfXoN0rcX6k9X7Isp2K50Yj
 qxV4v78xluh1puhwZyC0p8IShPrmrp9Oy9JkMX90o6UAXdGUKfdExJuGJfUZOFBT
 tNIMNIAKfMTjhpRhxONIr0emxxC5AQ0ETAEXWQEIAJ2p6l9LBoqdH/0JPEFDY2t2
 gTvAuzz+8zs3R03dFuHcNbOwjvWCG0aOmVpAzkRa8egn5JB4sZaFUtKPYJEQ1Iu+
 LUBwgvtXf4vWpzC67zs2dDuiW4LamH5p6xkTD61aHR7mCB3bg2TUjrDWn2Jt44cv
 oYxj3dz4S49U1rc9ZPgD5axCNv45j72tggWlZvpefThP7xT1OlNTUqye2gAwQrav
 XpZkl5JG4eOqJVIUX316iE3qso0iXRUtO7OseBf0PiVmk+wCahdreHOeOxK5jMhY
 kPKVn7z1sZiB7W2H2TojbmcKHZC22sz7Z/H36Lhg1+/RCnGzdEcjGc8oFHXHCxUA
 EQEAAYkBHwQYAQIACQUCTAEXWQIbDAAKCRABxeoEEMihegkYCAC3ivGYNe2taNm/
 4Nx5GPdzuaAJGKWksV+w9mo7dQvU+NmI2az5w8vw98OmX7G0OV9snxMW+6cyNqBr
 VFTu33VVNzz9pnqNCHxGvj5dL5ltP160JV2zw2bUwJBYsgYQWfyJJIM7l3gv5ZS3
 DGqaGIm9gOK1ANxfrR5PgPzvI9VxDhlr2juEVMZYAqPLEJe+SSxbwLozBcFCNdDA
 yXcaAzXsx/E02YWm1hIWNRxanAe7Vlg7OL+gvLpdtrYCMg28PNqKNyrQ87LQ49O9
 50IIZDOtNFeR0FGucjcLPdS9PiEqCoH7/waJxWp6ydJ+g4OYRBYNM0EmMgy1N85J
 JrV1mi5i
 =KVzv
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.197. Dejan Lesjak <lesi@FreeBSD.org>

 pub  1024D/96C5221F 2004-08-18 Dejan Lesjak <lesi@FreeBSD.org>
      Key fingerprint = 2C5C 02EA 1060 1D6D 9982  38C0 1DA7 DBC4 96C5 221F
 uid                            Dejan Lesjak <dejan.lesjak@ijs.si>
 sub  1024g/E0A69278 2004-08-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEEj2LwRBACdxv/Z/TqPsaxTmKrXZSOPnQca8L9UksW+71kI7YouAkbnnTyB
 maf7zCs0BDcUU6t2mO5ijJlxXe7Y4yMx/3mwGX9iWfWh5U9xobG0STcU8ET3ZQmZ
 /AM1vSL/weLK42YHxyqSrudt/oWxH4iDZFz5I/HI1DRwZMFhft3ja+pdYwCggAu5
 GwYrQlQJHJcCFbxnYUGJX/sEAJXyzea8rzP7dTUsaOYcLitIpy/eDI3vkB0aW7Uh
 JSicWASPW2erv99f1p2gkVQ0b0lrpMwPrysotfN6wLLYR0fowCWHm7hnASgohFpq
 VwB7aj0HDEHne7EIr6geSpnO8Y4QUtbFVWo9cq7HGzrB8NhwpLXQ5g9RgB+H9SS7
 SzVXA/4qPOAoJ8Fp+ZSznd46yd+dgFmVpSJuTs3g+hFolSioEkbi66fHwPMWeifS
 i02AkU8m/qiGMAXRwBm7s5jeLwQyJX38S4PnupPg8pOjZtLVYoTWaM19yuMGS5S/
 ryF5MaCGtuB72Wnsp67aZIkaHjfS4QAKo0WVH8yucnyOS+BFsrQiRGVqYW4gTGVz
 amFrIDxkZWphbi5sZXNqYWtAaWpzLnNpPoheBBMRAgAeBQJBI9i8AhsDBgsJCAcD
 AgMVAgMDFgIBAh4BAheAAAoJEB2n28SWxSIfMJkAnjxPSokKlZtVhYhAcgX9as76
 sadXAJ4yo003F9ilZw6avaThCBltR/MqWbQfRGVqYW4gTGVzamFrIDxsZXNpQEZy
 ZWVCU0Qub3JnPoheBBMRAgAeBQJBJQwqAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheA
 AAoJEB2n28SWxSIfOHYAnA9quQ97rU3eJHb1LzOTpwZVMSDxAJwJnLzSFQHfJu1f
 seG9fTyt5UpBAbkBDQRBI9jCEAQAza9XDZevfbu9BYjDESbKo38SRgyTd5/lIgzH
 IlF+9zGr2e9PH1WOIPr0m9m3LYQzkL3YiUm23UoJO7uhvWvCpxfChwVx3VFwM7Yz
 WqWBV+W27aZNROEmh5KheJACE/m6j0R6UECiRHZS/EsHP8FNG8roWro23ApNR0Vh
 zZ6iVNcABAsD/3glWDyCWMA/eX/YGPw3xN3hkENgruwtWKkK6TW6kYv94k4iD/b5
 bRsmIvGd31AM5/Qv/IQd7epXb2ovDaKvMl6+jAJb1NMCSzOkCnoqcQoKB0ed33d0
 JOVWuA34WCMZ2zHLFEtwuQkHZqmyNQcxRLGLkODo4WWsYNU7KeGHvAJDiEkEGBEC
 AAkFAkEj2MICGwwACgkQHafbxJbFIh9+8ACeNr7M+KLI/eWu6Nig8877cjrEP3QA
 n1Kfo14Pijwx26kysheLFV1jutrq
 =IfeN
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.198. Achim Leubner <achim@FreeBSD.org>

 pub   2048R/2E15B3C1 2013-01-22
       Key fingerprint = 2A48 0317 D477 2A07 2AD9  CF1C 7C1D 832E 2E15 B3C1
 uid                  Achim Leubner <achim@freebsd.org>
 sub   2048R/E275EF01 2013-01-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFD+q6cBCAD8XsjHzsyljaRIF8Qz8NeXaiZWq0KZ8NHRJ4ahZLN5kvhk2D3+
 Y+iiMl6AesqTP/oobtXkeUFVlr0bwBBHpIRoOmGzxI5aorMH5Yv3dfY9u5HgkAW1
 E//0VK92QyH4O7q0adquRmymjR9pD2yjoXgIFg6P4cHoEg1hLyf3FOHHCSEYdXVm
 A5iBP7w+7aIkcUQiRVXHc3CojDZrkpSGwA/Pp9ywple8p7GqxoBr/4i/qYQeCNMI
 97EO7c+BSfBrbgvWiYPY7+eIyV6AZFl9NfEfdko/7HLRkbL6Hh3jSXR/SZQ31WZ7
 ct2z5GqJpEx1CDcIw1nxFYQ5uCLbzfyWT2JpABEBAAG0IUFjaGltIExldWJuZXIg
 PGFjaGltQGZyZWVic2Qub3JnPokBOAQTAQIAIgUCUP6rpwIbAwYLCQgHAwIGFQgC
 CQoLBBYCAwECHgECF4AACgkQfB2DLi4Vs8EW0AgAnkiKp8Hu40tgwLymXdK5eM2K
 nywLNJ7MBUwuX9rn0QIQ5gy26ktHCNxONZLacsApdsCAlH4vKk89G38wXUq6OgGn
 NQ+4uqoSVuUeR4A4GKdGjVNld/r33v3nq+QgGitGHjgpMtEPf+ZfCfZ8GxZG/oi9
 kBpQMsA61sigcYZytbhGM8qy4aCqpgOKys2VifEgtOHx5jr7JZRYLrBkyftyvVS6
 t9BDg1rdy9dcdKCaXp52H/qEZL/CO2gFLDR9t4ul+NalIN+nkPBiwS3hu9kn0Y5Q
 vDU4Kw8D7CW4dalqOMipOetvMwYVEmv5YiCJwzcoMIFpl2aOvef5yoQdozagGrkB
 DQRQ/qunAQgAzEocPpUQIsc5dlY3+Pa69WU6+qjIlVHbH6eZ5hWgi1AFMRf/KJGv
 HzZJElAXUz4dEhSAMhbHdWD0h6e0NalD7Uzea5Ay0m0mrKlZ1Ijo3lCrSXpKRwyZ
 terxnHZ3kc3XFUabk6kZfLkZsnm/+L2n0OX/dXvugeH+uAbjtYggBosun2mYSKtV
 x5+8WK3EaeLkh+0Ml5DiYfReQcS8r5ZCwfM+EtgP+ckmqHVQOXIy63WwHDPC/82U
 msQmbLGBw1RMezEckpQMksgC6pbqbp5gVxl+xUjz36JBHEW+MeOZLDiKasNw8tO8
 G5sQIYSKh/Vcb1imeZIb/bvagtLIJp4EEQARAQABiQEfBBgBAgAJBQJQ/qunAhsM
 AAoJEHwdgy4uFbPBunYIAMDQe8m2VtABvUq0SS/MubKRKVASiWQZkvxqh7stDgl0
 J0bsk0O6egWk++lsXTRGr6SwV1fkYawZVLAkoiMyovLC0iFoUZTmkHE4fYUFJX+u
 S6C9UURhpGpETLVI9sLfREDYWIWf7pvaSUmhF5RHcugcLhu5I1JZdJjoHXkpCbFO
 8xOK7D0KBFVCSnm/b2yo8cfHi8LFLqsqPvf5mJx/iKuTSGJe2XRvA3D7BgH8/Lcz
 QKsWBslP5TlIwh0Zy5mabAEKzGzVWY5laM9lXGbZrG9ALwEzSRgZCUWTS/EfC9jE
 WtMvwG0kYv1rFDqiRdjtqD1ja59uRXGdiUb7++BX7cQ=
 =jnyf
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.199. Chuck Lever <cel@FreeBSD.org>

 pub   1024D/8FFC2B87 2006-02-13
       Key fingerprint = 6872 923F 5012 F88B 394C  2F69 37B4 8171 8FFC 2B87
 uid                  Charles E. Lever <cel@freebsd.org>
 sub   2048g/9BCE0459 2006-02-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEPxAWERBACkn7HyvqMEJbJcf5eSJ57WR4Xoo1PU1GIsAYhdFhDOvmeWRZcH
 kwUyFyol4X3P7RyibrvZwnvc+nrqXqATzVeDHT2NhcTTeG7fq4E4a3VpdqR10uV5
 nswMRw/Arci7vuAQnmHzOYfnNP1ng6qLjA/CUizQ01WakhQeHGtbM9Q5XwCg2GEW
 H6d78/rWY2Lb2wo6cS+9Du0D/01cO9zPg+Mh2T43XdLMjnVp17jR99SuNajqJbBJ
 pNehq8yA6wb3ahZPjKtXpgELu7YI7omxhqcq1mxKvXa262aV72qdWqWoqvZzX0hU
 lOckg6Q6EO7qGvU/jOY02/tmHdzQy6UJzHB7JVsfZ9DGH5xW23AYmbD4WF8jXtyL
 Ey2eA/91IZpxEK7guIBt0FE0qMSCh5VOOlzOQkV+KtLswzEVPOWw/93wGpd/uilx
 jZESPZ70cSWuCWwY15FEFts/gs5gPhCs1h4asQI0Shft3sgQrBhE1/hg2uENccHR
 y1Af75hwezkwFkE2DUXFQqLuUlGu0sOtG+b7+IPrYuaGAB/yBLQiQ2hhcmxlcyBF
 LiBMZXZlciA8Y2VsQGZyZWVic2Qub3JnPohgBBMRAgAgBQJD8QFhAhsDBgsJCAcD
 AgQVAggDBBYCAwECHgECF4AACgkQN7SBcY/8K4dpvQCeMv7yFBMFOPxa8lF15IYP
 8LRYjaYAoJyIupvj/RgaM5zZXZdPUS+gro9SuQINBEPxAWkQCACPOzcRL0LbFubW
 3c8aJODeBG91aQRPz+ndMItFW6/+CW3EmyCGyaG8uxdtY0SOx0yALj4PiSj35s8u
 wqfsWFRuNixODl9lE8ihq4d5qfeiwpcAR9wVNwgnXD9boKXOOFwb70W+9pI/I4zX
 igHFxZQpndROhIFO1RLdoBlB89vV5iX/qzPKHFfmbbIkY4zvAsvW2MCly1WiEC2y
 GT5GJTFZgko5/VBFzb3VDvA0grCGGTbHK1hnfuuvouQPnbuawdSZO2XGMc2pFcKW
 gh+fgdw5Y/oQZelJKhLaL8Lz27buTz2sj5O/cYv5n7wDD/kSnb7+pd//qagox3JZ
 bGXKTED3AAMFB/42KW+FULr4keaGuhAZ07hrNs73Uw3QTTNIUYYOkSJVvgold8RX
 HMP38WANIkHtB3LBaZBxhqAOp2R5AppIPfyDrp1q0lTOGpzWfsQNQd10KRsXZGkf
 K6INVa6kpzQhNDxBUyLh4onp7hZyt9zXdZrfYJLexbxrxkP1LDRDNJJAY29LnVR2
 vyDHPrB6mmgijy07S6yKwC6iJIRoU8w4X3xFqIQ+KcA6VBhXqtqxSjk7GQnwyB7Z
 7l4Qg8iZvX5qj753w6BDEwDtXlCCbocDVsu5xcLRPwMN8BgH7XcYCwmZFEU7IgEk
 RAhqiHsjpnO7al5a+HQJi/KMOs5aDfwdkI48iEkEGBECAAkFAkPxAWkCGwwACgkQ
 N7SBcY/8K4fTZgCgiVDpYWzuROUmau+CUT/UVCatpHUAoIyg/KnHhe9PUB9Gav5+
 /KWhtyRy
 =T2Vu
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.200. Greg Lewis <glewis@FreeBSD.org>

 pub  1024D/1BB6D9E0 2002-03-05 Greg Lewis (FreeBSD) <glewis@FreeBSD.org>
      Key fingerprint = 2410 DA6D 5A3C D801 65FE  C8DB DEEA 9923 1BB6 D9E0
 uid                            Greg Lewis <glewis@eyesbeyond.com>
 sub  2048g/45E67D60 2002-03-05

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBDyFNecRBACKn+4b36n2/e55yTfpLXS9a57gQNgx0WXBfbK9LMLf2D8otD+0
 z1DW2eclAOwJVtPftjvYP0HKFVC8Pes9Wvp6Z0sIEPpdkL2NPlUuxXUyh1b92u7n
 Bpt7Uwsom88fnn+BOPrvvPL8Arg3JBen+Jd8o9yRoABCYku8vQF6CEUDcwCgmHJd
 9hZ/kRb1rLdSLssB4VMQ3zED/0/SVm+6XV+2ObXn9FKQpCC6sMSq+PCoR9NzAVRI
 njTtkpyR0fjJZr69IN2E2MWPonv38Xg1tWJnR3fKUOnNqwiVHBQKKrKa9lGWsZQp
 TrR+ihtJ9hC626dCq9JDb1Ls7TXn9ha+d0WNuqiwugto/myHm/GVlCANhGzUuDNU
 Mo27A/46YEAMuhSQWOxgSZ/Z5g0ybgpswVePrxvD4sX2/AVfKClOYpPiNJe+S7YT
 JmfIPkpP2P7v+87BaN/uWgaFmxlhpUOIuat44w52EwwGB+K24cGgq52XncZsYTYH
 SrLitkRtt35tVdnn1v3gmDi83M8W/YunflpeJAgJC0QzxKuar7QiR3JlZyBMZXdp
 cyA8Z2xld2lzQGV5ZXNiZXlvbmQuY29tPohXBBMRAgAXBQI8hTXnBQsHCgMEAxUD
 AgMWAgECF4AACgkQ3uqZIxu22eCkCACfUuNYpGGlFboDl5FZeXlor/k/hogAnjyq
 /Vw8amjEN34PGuqBPQpMnFrwtClHcmVnIExld2lzIChGcmVlQlNEKSA8Z2xld2lz
 QEZyZWVCU0Qub3JnPoheBBMRAgAeBQJA/XNpAhsDBgsJCAcDAgMVAgMDFgIBAh4B
 AheAAAoJEN7qmSMbttnguMYAn14cqGfabS626P1D4GMcSkSagzaZAJ9LyH+vMrfn
 OI2x9+VLyaTSAvm4zbkCDQQ8hTajEAgAmuQukPFaefkzE7DTIgSDIc5vRmUHDs01
 bGp36R7f5GEmXwNtCZ+Mf+H54QSzuNh1QaJ6Nq/iYd35LA03/I7AgUFwSX1cEc/n
 fNjxqS27CAab6nIt9Syb9WAAKUKDMwZCjHBNv49CAPyVVb1aTUCJyUcv1gGSMNHX
 r2bkWpa4nIN4+rqD3hifHCX1j/2XMkmYY8NCVTY52zqO4sCbh+ohAMfYtW2yV2Iz
 z4ngppp0fUbmlGV6DVvTC1Mi61UCDkhO+TZFlE3qXeGlP5GR0SbpdQmPiI0Jpinq
 Zs43gcd2xtiUBM7HAMoQDpyFirDuyDKUgMWJrtJtAwWa4cf4Luh/fwAFEQf/dqpH
 bl48tu+REAPrjk9NWaGVqi1vv0r4LJXo8db9aGxwwAzKXDhwqHo69E6l4/Rd+hsa
 sIJE7vGNbGK+uerTg/W3jot90MqraplXHuS54TjOMyzWSSG7S6ypmDf5YnK3xQE4
 NfTYvC2GxphotkE+QmBzmeft/Mo3opVYlv3OOBqiQoCYB348rXczxEUPam3bFBw1
 wp5XjA0kqYRcUbxNE5AK9c+g6R2c/jT96EnDZDpMRCNZiAKHFLEjtHy66BiVHKvg
 tijWD0kxtlWV8KAKN6OhUpSSsCv53jsCIntNARAVENOKOV0RQVDfJgykeK+3eeNr
 UdIjAWFAWcVOEw5TQohGBBgRAgAGBQI8hTajAAoJEN7qmSMbttngHb4An37mZU8r
 E3SGCAlTJCLV1JxRDXVyAJsFBVshxisn1GycdT3UCwcJVAHJ5Q==
 =bx2+
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.201. S:oo/E <delphij@FreeBSD.org>

 pub   1024D/CAEEB8C0 2004-01-28
       Key fingerprint = 43B8 B703 B8DD 0231 B333  DC28 39FB 93A0 CAEE B8C0
 uid                  Xin LI <delphij@FreeBSD.org>
 uid                  Xin LI <delphij@frontfree.net>
 uid                  Xin LI <delphij@delphij.net>
 uid                  Xin LI <delphij@geekcn.org>

 pub   1024D/42EA8A4B 2006-01-27 [expired: 2008-01-01]
       Key fingerprint = F19C 2616 FA97 9C13 2581  C6F3 85C5 1CCE 42EA 8A4B
 uid                  Xin LI <delphij@geekcn.org>
 uid                  Xin LI <delphij@FreeBSD.org>
 uid                  Xin LI <delphij@delphij.net>

 pub   1024D/18EDEBA0 2008-01-02 [expired: 2010-01-02]
       Key fingerprint = 79A6 CF42 F917 DDCA F1C2  C926 8BEB DB04 18ED EBA0
 uid                  Xin LI <delphij@geekcn.org>
 uid                  Xin LI <delphij@FreeBSD.org>
 uid                  Xin LI <delphij@delphij.net>

 pub   2048R/3FCA37C1 2010-01-10 [expired: 2012-01-10]
       Key fingerprint = 27EA 5D6C 9398 BA7F B205  8F70 04CE F812 3FCA 37C1
 uid                  Xin LI <delphij@delphij.net>
 uid                  Xin LI <delphij@gmail.com>
 uid                  Xin LI <delphij@geekcn.org>
 uid                  Xin LI <delphij@FreeBSD.org>

 pub   4096R/2E54AB2C 2011-12-05
       Key fingerprint = D95C D3C3 8FA8 25C2 C62B  9FEA 0887 6D93 2E54 AB2C
 uid                  Xin Li <delphij@geekcn.org>
 uid                  Xin Li <delphij@delphij.net>
 uid                  Xin Li <delphij@FreeBSD.org>
 sub   4096R/7832B740 2011-12-05
 sub   2048R/BC50FBB3 2011-12-05 [expires: 2013-12-05]
 sub   2048R/C894647D 2011-12-05 [expires: 2013-12-05]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 27060 characters]
 SN0=
 =idxn
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.202. +-c,(R)ouO/ <avatar@FreeBSD.org>

 pub  1024R/F4013AB1 1998-05-13 Tai-hwa Liang <avatar@FreeBSD.org>
      Key fingerprint = 5B 05 1D 37 7F 35 31 4E  5D 38 BD 07 10 32 B9 D0
 uid                            Tai-hwa Liang <avatar@mmlab.cse.yzu.edu.tw>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQCNAzVZoYQAAAEEANP5N0PqWEDO1ml4yfxXCQ+hEhaXyaGyNboh6uLX7uNPXQTI
 9veETXNd20Fu+8yuzVFJk+KmmGerUzduHLXm6q+szHBvEQoJ2ZGk9AL9jj2JjFRj
 rCRsf6mk8SWuL0xDBTu04bZZ2ttNDxNiymNTqdBVZmX6Mdg/T2i3mv/0ATqxAAUR
 tCtUYWktaHdhIExpYW5nIDxhdmF0YXJAbW1sYWIuY3NlLnl6dS5lZHUudHc+iQCV
 AwUTNz0HC2i3mv/0ATqxAQGQ2QQAww0WfeHFmupfTBWWdmNSX9eCDIfN7Wsuiu54
 DgCi7T7ixQa6reIsMAKx1KHNX/GSBr+t3nyHT7N12Ee09qKXywQAw9W2nrdMGE1V
 nENHEFgJtvnoN76U1goANEfZGnLLhyuDoMyZGCZmVG6FiV6EoKrWxfwq+jV0Y9K0
 3AI/Cny0IlRhaS1od2EgTGlhbmcgPGF2YXRhckBGcmVlQlNELm9yZz6JAJUDBRNC
 H/ubaLea//QBOrEBASTEA/9H+78uZl6JvHwGKOXyZkrRCLTUgifJcR3thVfynGrM
 AImheJwqgVP7FQojDk8xBCBQ1b3tpwpeRPwE0V/Dr5MkFLfiaVgCIfMibqcc9zuH
 i4RYcRqKswiO3pFeDMyHiSxylURcHfx73CYijIDyG+HPiCQ4OGd95VJywUzOVddn
 +g==
 =jIT8
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.203. ^1u^^3C, <ijliao@FreeBSD.org>

 pub  1024D/11C02382 2001-01-09 Ying-Chieh Liao <ijliao@CCCA.NCTU.edu.tw>
      Key fingerprint = 4E98 55CC 2866 7A90 EFD7  9DA5 ACC6 0165 11C0 2382
 uid                            Ying-Chieh Liao <ijliao@FreeBSD.org>
 uid                            Ying-Chieh Liao <ijliao@csie.nctu.edu.tw>
 uid                            Ying-Chieh Liao <ijliao@dragon2.net>
 uid                            Ying-Chieh Liao <ijliao@tw.FreeBSD.org>
 sub  4096g/C1E16E89 2001-01-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 5346 characters]
 =NLH6
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.204. Ulf Lilleengen <lulf@FreeBSD.org>

 pub   1024D/ADE1B837 2009-08-19 [expires: 2014-08-18]
       Key fingerprint = 3822 B4E6 6D1C 6F71 4AA8  7A27 ADDF C400 ADE1 B837
 uid                  Ulf Lilleengen <ulf.lilleengen@gmail.com>
 uid                  Ulf Lilleengen <lulf@pvv.ntnu.no>
 uid                  Ulf Lilleengen <lulf@stud.ntnu.no>
 uid                  Ulf Lilleengen <lulf@FreeBSD.org>
 uid                  Ulf Lilleengen <lulf@idi.ntnu.no>
 sub   2048g/B5409122 2009-08-19 [expires: 2014-08-18]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEqMMZ8RBACHcol8F7dxjIhS+FYaeAW5YhB93p3ym1oCrnIQ8cGih0baXMoB
 VjTXm9OmrhOONntRzf+JDQYDQbSg5YtqyHJkY6613j+K2tCAOAQ44xxCDPAiuQfL
 fy8pL+b6qcLuwMFJkaNMU/bpNRxYn1+nMWy5pigWM6E5IXZ27rBkWb8SrwCg1G0w
 A1T/kieE8LbEgAODP5tHC+8D/0ponWwn79+Ll+juhDXe26jC6HMAfHCyb0gAKocd
 2vqsozzW78nmJCuCvu+p3sb4RC+Ck7zRGkj64cBjp5Xt9+m2DVBEJHZrGAHSR3fa
 2L54tWvNS+b2ZHXMxYFIEi3JbDm2iqg5i+Q/1T0AMW8HTTZSoYo3q1QCApsbmck0
 DgIhA/9z2oFqc4CMoBgilh0f4LC8xoDAtbvluzQwhr3uvp4c0N6ZBpHPPFows6P3
 cSqBw4uHF6XmZyzySkhUpUsAZ7B2yHnIaMQrBHgt5AovchIiNNXg6dIhtq6PTGP2
 xTuubLZCR2ZEp91OqFY2kWkFeCQ3PuOcdfQduLHs2Id3JOqPGbQhVWxmIExpbGxl
 ZW5nZW4gPGx1bGZAcHZ2Lm50bnUubm8+iGYEExECACYFAkqMMZ8CGwMFCQlmAYAG
 CwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRCt38QAreG4N7Y5AJ4qWuEUuglfftxc
 qYBNEsu3BgoHZQCeJQ0s4fhnjgBWkNPB3+SMnfRBR8W0IlVsZiBMaWxsZWVuZ2Vu
 IDxsdWxmQHN0dWQubnRudS5ubz6IZgQTEQIAJgUCSox2XQIbAwUJCWYBgAYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJEK3fxACt4bg3BeAAnRSgnBH1oWkjXpnVgoaL
 ey9fZpmdAKCZSuOXiuJyPfLw0fmIE2ck5MVCULQhVWxmIExpbGxlZW5nZW4gPGx1
 bGZARnJlZUJTRC5vcmc+iGYEExECACYFAkqMdm8CGwMFCQlmAYAGCwkIBwMCBBUC
 CAMEFgIDAQIeAQIXgAAKCRCt38QAreG4NwkdAKCp3vXkrV4DTU/uzYl7C2PLNPdp
 OgCgo92+rW97x6V0toYmqlX6gX02+xu0IVVsZiBMaWxsZWVuZ2VuIDxsdWxmQGlk
 aS5udG51Lm5vPohmBBMRAgAmBQJKjHZ7AhsDBQkJZgGABgsJCAcDAgQVAggDBBYC
 AwECHgECF4AACgkQrd/EAK3huDfifwCglUcGDEWuptwn0MBR996pjWZGRqsAnjSi
 ztpBg8l0p7mX4qRD+EIroWiatClVbGYgTGlsbGVlbmdlbiA8dWxmLmxpbGxlZW5n
 ZW5AZ21haWwuY29tPohmBBMRAgAmBQJKjHaLAhsDBQkJZgGABgsJCAcDAgQVAggD
 BBYCAwECHgECF4AACgkQrd/EAK3huDelVgCgiGTNGXfoIdtGOko2oIyTZ6tTlbQA
 nArzMsDvinZNUCP4yPPWpRnq4CcpuQINBEqMMZ8QCACQxMbl1cKH2ItbjjDZatPV
 IASoAuBeqqaJnlCko6UX1Lajm3anB0gZvm97qI/yG9AO06wNBi984Z8vv0a2in05
 zM10r8Ft2GTWlFxMZqJePiDl3gWMg2jhPcRfLlODTHLa+tO5rx8liw+RBs8wg5z9
 RUDrrHAKViosS9alz4Lb8+jfCTjOM/VA6PkGg9HV7+lMMRkHkvUaSJfxkj3ILydZ
 /SkYwlLMFFAcod6X1VDwLzIPP5Lqkshc5PuGB58eSqh+nkpoNJWjw5zJlA8Tg/++
 C2Pq7zjY8O95oCFqDLCFNdQcBbiui3EU7YwcrsvaRlaeiMUiwnjOltyE8Th7a/sz
 AAMGB/9S1DMaIHJ8JVHG57hS1EuWqjfRGIcuchMrRdGvZPHd3hNw3/5FvXVPi+6g
 5FoZqAPH7I0gweUZof83lPJi64CFZKZkz+9YSmLqEuGjdSgB//wCSDVrwwKCiGDJ
 D1HJhFtVmsS3L/VyH7c5icEB/oCJZhG2GwgKXEEe58Ai1VfCGCArNTm+h/NmG0xr
 S46lxiAzvV945mF9n4jImFBJzOGL3U+kfp38niN/TkEHA1JtNbqpnOuMKKOWNSSM
 gIArMZKZnyrQsEalrJr+9nTPBLdsNSSNE4N+l7EjvrnTRthBzrfYfoHKKaO8x8rm
 fCD/rgO6U3X2gsM23xdjn9D0uZ+FiE8EGBECAA8FAkqMMZ8CGwwFCQlmAYAACgkQ
 rd/EAK3huDdJUgCgo/E3aF2+Xs7gWumo8ff0IBM3yEsAn1FYPHYU4rtHj/rtzVLB
 L1JhS/1K
 =sCn9
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.205. -aL-aF 1/4Y <clive@FreeBSD.org>

 pub  1024D/A008C03E 2001-07-30 Clive Lin <clive@tongi.org>
      Key fingerprint = FA3F 20B6 A77A 6CEC 1856  09B0 7455 2805 A008 C03E
 uid                            Clive Lin <clive@CirX.ORG>
 uid                            Clive Lin <clive@FreeBSD.org>
 sub  1024g/03C2DC87 2001-07-30 [expires: 2005-08-25]

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: PGP Key Server 0.9.6

[encoded data, 5940 characters]
 tF/cItKqIqZ9RhFcg+IisxgUtQ==
 =g51D
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.206. Po-Chien Lin <pclin@FreeBSD.org>

 pub   4096R/865C427F 2013-02-05
       Key fingerprint = CF3B AB13 4C94 6388 B047  B599 8B28 1692 865C 427F
 uid                  Po-Chien Lin <pclin@FreeBSD.org>
 uid                  Po-Chien Lin <linpc@cs.nctu.edu.tw>
 sub   4096R/F31280BA 2013-02-05

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBFEQZwsBEACkqROTbfKgAUYdaT+6hIetN1r9hcN8G7je42QWC9+zMyZemqhc
 KmokdKrq/l6HklJMjzISCKK2tWPdqhYV+NPkcZSvLPpCcba1MIvMVGr3MWuKxbD4
 Hb4dZ5c8t6gs3xM9hdP0ENNTLTchZrxydvmN8NBnzUbf7ZWBjuuT+HodSARVFBIs
 EDe7Qwa6ubUNpFYzWhbqQO9lJJRqIH4hNRDJaps6Hxdz/Hb3F8xR+SYne33ytU7H
 h6LWS5eVY1DMFG4vZq/hhZoymmg/TVDIe5msOB7o7Wlo3U2p4ybs0ySMjtDUk6EX
 0nwMEHfFgFpSlJd1G914OZWK3fFnL0ZXlkaQiOkfFhL5q1bwDBXFG3EXXS9x/eTM
 wJIk1ydNiMUhvdRbfaQMpaKWnv9r/EycJasqxbpXyEH0LSUH1vCGxDJ7o3KVWm8+
 LTxR2oiSHIL1Y3ucB2reveDFjP9yyensq4BW15bY10bqVT2RS80xPmK3eRU7qwPW
 9E02Uw7FYWNyFAUDXV73vhroHhdoBliGOGGcAQBUnsUdPzmSyqV1iUczcygEq1mz
 Ef1dS9xAoY/ShwBZQspPT0GiEeTIRORKQtmcf1gzVC9QA3ZCtldJLfkVON3gklS2
 98Haq5fkAjffvufhMld7BPggKMxSzKlRlrAsaWQdNLQSq2lS4itiXK2NAQARAQAB
 tCNQby1DaGllbiBMaW4gPGxpbnBjQGNzLm5jdHUuZWR1LnR3PokCNwQTAQoAIQUC
 URBnCwIbAwULCQgHAwUVCgkICwUWAgMBAAIeAQIXgAAKCRCLKBaShlxCf/5yD/91
 wEGhITTEW/UM3fG5v4JTbta/33Dy0DChTnPTR1Xur/pGzgtIC+hSk0OOUhGLE74H
 A/YamQcB9KR6jxXBQEuEmSFlpBp9FsFcdtJIvBFxj9G1qM5yS1QFqHCykko1I2EQ
 zfS+3tbh8Vs/Q7pKV5Qn10ezJLz9jgGUeQcSriexgYC79wHqMkk+fp+0bNXpBnht
 2zPnxv5wns1JIX+k4lAQCrM6AZsu9Po3EVJYFblz/z/6KCxeih7FtnUbCO2PUx9f
 x2OyQV8ATgbP4sjwjiDW5mwxU7ngGu/GHsGI9AqpuPJw3FVXPbqcP7tQ2hoIe7ic
 7HDrew801nxVQqvnGXABb7liReLVEIRKPgEHvEjNAraCf9OUU2o1hT76TNDfPW+w
 Qyf2iX5WwVFnE7Fb+fKl0e0vOvrGe3+EZsy97E6kX165pM+dQCFY+B36wkddsCd2
 0z3FcygbAclxtwUj/osGJeP4bcJ/nuK2a9d/Wx7vjx3hvGAheIOipb3/qWkBIFWE
 cedz2PXl8mdpW04Fjlu5nQRNVUU4MK2YS7bigIOGm7o+Z4Kw8cUy5GiYWql1vaEM
 JC0JD5SwoP6YleYQbBV9NeqyFIX0KzaHU0CEkBMsQzk1dY6sXa+gVesXzX6tEbNs
 Pc5l3BBx2MFofA9AhdhE5wO2DWoKO4sndGkhzTWihLQgUG8tQ2hpZW4gTGluIDxw
 Y2xpbkBGcmVlQlNELm9yZz6JAjcEEwEKACEFAlEXxtsCGwMFCwkIBwMFFQoJCAsF
 FgIDAQACHgECF4AACgkQiygWkoZcQn+OOxAAhQFkrTuhTUEzrrENwm5hxwk556Lb
 Nc/w+vr/HxUTcsYHzVlefyVaSvoMgInN8RFU+FSPzTv+y56HvsNhLXBZ8elWxGZA
 CZWIhpwG86XGoOjY1BAuXTPRQ193k/h4XMS4zVZ9qrS3dmQZZjR/7y7RzRLk7cNH
 cjjvXDLKLnaEJfcMOqqePSF4Wh4O8jwjZERCsn3hJwm/l2LtNlIXCSvg9RTVhaNa
 6yYP0h1Y2pLD6QyhSiqJvyobD3e56Wt5GD+q77yISPSdxxoCh/7r+VPw+KxedYL4
 9vitNjzbbsUH/l88cigWbVXTawuGq1JiqFzpsjRn/tMq1rz3vWJBDNRM9lbRqWdT
 2gd/SNLnKQ89RCH9ZDBlUAduh3Qdcwe7ux+3UYW9DK+Hg+WpkkjFxYfNICybkKzC
 P7MoXbwaiAkyeqGVUGleec17aqQG+Qu2RxmMF6rGhjZEbofYbxMkTLmPr+0uPN2d
 buSDgNtY+3j+PbZuy+l4auaCL4b80WCQ0TG1kQxknlLsBAsIyOkkCLkTdktejKNw
 5ZVLqR5gxRKzUVp47jvQI9m5QNpPz3BChgpuG1skOUNflW0Iho9VHtWv2wPR3apS
 /hnygJ1WugXYsZND7WKmZNR34nk/8/a7boI6NhrMrx5/LpoP/1W0U5czLWVa3diR
 UFSfs+FmH4WUMc25Ag0EURBnCwEQALlNKjHQABEQlAS9OI6BgnlM+jDPclwslKPR
 WTcPWp9Of4C5qU1ywg2qzPiuAEn/gQhYHifKmnzW2b9tvl+ySgn7xTxU5L1yaIux
 vBciS3ffyfhmC9cHMudkrpMX8iJ6tCV0qlbzBclNTlWlO4OjR6k+sONfRyVnySBR
 S9E2Vm6LQDfIbZMAyZ0OAeES6uYiqi/MucgjaKS+tSOa3IWpkXuxmXy4t8B06QPU
 ek9U3kJR/rS8s59IiFnCskyh8FJwSsg6o1hiuQCiozLxI0UAM8Pq1U7+4bxbOoil
 kNYzbcHsWHTVbopD8hPIlncQDbY8RKKg7ZAu3BZIez56LlsqDGuomFwz6yfuKZG7
 VpuZtvz5mSO63GXOFyeNuC/RhZ8lYoWiT4EYESqSJ8kHwx/EnJjVboALoYGcmdP4
 nkY1NwntkzQSpZBuvixIahyfyFLeSpC2+wg7cr2AyS/ze/FMCR77mwviA5bpQXim
 OiDCt5zaqbPYElXza+Mt6cmlbXt4bINvyAAlJQTz7RX1DnjLQIlG40ad2CeJJROk
 m2OhFzYhIHJScMXHGnOxyJFYNvI22xpMhorH1mH1mc2pjUDO9amzbQ5qIo0CTy0J
 O28/TIZ2jiZusfmbFvrQ4Zv/aTy7qwtoK7FYyHjgZOH1veRjT42EGsz3bGOyMz8b
 QQC0XLjTABEBAAGJAh8EGAEKAAkFAlEQZwsCGwwACgkQiygWkoZcQn9zcA//RiOx
 +c4H3hHXBhV1vnT3eZhCHh0fVkH+OZU7n0msO7Qp0b5tM6/GMeGpxC0jLIK/lQ9+
 PvwRvlMENO//tES8ZGnDuqC88MmxlNP3qb7fpyNZX91QJt+oDDUB+WKPvouTBF3H
 rzSZBJGa5ChttL0QSare9enKhu0axeH5DufRMzpAtg3mbzPmJlO1EdU3FGQDP351
 VuDNlQSJdvJwk2KL+X2yfu5gqMa7dTwPfqRhN2rWklZCTBBbYiWlUqb/zgiFz4I0
 JCjGdL7930SJZD19EDWSxHweNzmqSRt2u7tvUOpxd1XDLaBQW4WfOzf2gYpPhTwS
 VwJK3YZPpLH3xvbRiCRSY3Lj5r3KpstzDSa7YnRD7WqUcya4bQrs0CppJDisaR8g
 LCvM9B271wAC1+aS4xIPqbWsCVhTUAg5pxiwOHMqdSBayAXVMOduDLJ+fUy4qknJ
 gk2z6X8l0w1YUVmbXlNw+pdaFIRGw+TneQMAeI9FJHewKhLGN1MP/6ZyvUiZ8w/t
 h5F88+tsxlWOY6UIXsZ3p2qGbAGd4qfefEVVJe+Ab5FwtvEH0/auj7uZ36oenx9A
 +WF98OpWjUhDEi8kigV34BysDSQx1nsbILJYlFsQJauO9LSebv9qYwX0yLPZJJoR
 uDqUBEUq3MHcpGRlsG7GQlW40AibKEA7Gd1OPbo=
 =2C5J
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.207. Yi-Jheng Lin <yzlin@FreeBSD.org>

 pub   2048R/A34C6A8A 2009-07-20
       Key fingerprint = 7E3A E981 BB7C 5D73 9534  ED39 0222 04D3 A34C 6A8A
 uid                  Yi-Jheng Lin (FreeBSD) <yzlin@FreeBSD.org>
 sub   2048R/B4D776FE 2009-07-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEpkXvABCADnsekA8rnN29OpRPBgLBo2RzYI3b+FCSkPqDatHJuGSfTqFUgi
 2WI8QItI0toqcePNpNtgyHie5jqsX3/yFBRGO1xyCSIEMSbMiOtZZizYLqlLW9pZ
 seNxwHBetogToNoveYHXNGsrptkqir5mx+vtSO5o6DFcDZYQRgZq9NTnKnuJkYwK
 wnujkHcTpUVw9pmnwj6ZxZ5V8fboCzd9ET1SmWH6194tpJ0Fq/HX9qGfF/c6Kl+e
 Hwz7TFi/hpMwsdwjz07SrDi8bumuWNpwZprOzHKORbHfdg3GZaEPcLhF7qjvYunk
 osYrnyUmz7+FpTJVg3u2Pp3eL0xdXU4TuwTfABEBAAG0KllpLUpoZW5nIExpbiAo
 RnJlZUJTRCkgPHl6bGluQEZyZWVCU0Qub3JnPokBNgQTAQIAIAUCSmRe8AIbAwYL
 CQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEAIiBNOjTGqKQTYH/3kkQL00ibVSNCHH
 2VNfnV9tyIDBIorMHFctEZ+zTQ/mQRxXUS3gpD9pg4nYNJtrstIWxH9Y8GxDTjQ/
 pJsVbZ6WcYXANwihoH1jQetSR4ZZDLrVynSWQ2WeYg0XEedKxV6ZmxZQPAbN742o
 T8ehZpThFSaPVDtIYFh0eVnPkwsmR/mC5DQDGkwb2p2bsxdbkYCWLLRiS5buGFyZ
 iHZSe+D+mRJq5kxZriy2pSXcQUlqZk3jvpC9mXr8QzAwyzbPwHRak5NNuQxxCJGh
 CBDzTSB9OsJrLd7WOxISii2k9ZszP69EymO3wTpSnoCPyUllOsdMa0291xv8kw0c
 3ytWz/65AQ0ESmRe8AEIAMYk6s/25zGN9qnfbTjwtxPD2/K5AeyJaQ+kZ5kiOZqn
 DlpMawMccq+yvh25oX3j0NUug4j35FKFZqnzpLx4KizbJjhZX+V826lVsf9kx6mR
 UmpYAlOb1qQUZMuR2+41eVnuieAqNyFH4pjp2zR6mhaoI82a1AMeOdhVOLfTl1+Z
 mj2sL+1J+fkcBxuhMEC30elVKxuQo/8NphZlnZe/819Q3HDsuw2mEiQMWH2y/5B3
 aSpm7/LY/L13YI8oUNWZrvjJZYSYyFyhDryzkP60251Dhfwlu2792Jt2Y4dm/zVW
 Yi/QpUdoPLRqEQjipiBg1sWLH1UGYys4muUxBoUQItcAEQEAAYkBHwQYAQIACQUC
 SmRe8AIbDAAKCRACIgTTo0xqimB4CAC9MJzYzpUgnlhh275aZs6pXJnK9dty7HpQ
 zJ6UpoR7oBcmYivlAXaFBB0jxsAAzu3wKXwC9IOZZAB5y9keXWkG/2zdutJJ687a
 HAjXUUPi3QIF1uPGgvpEQPNfn+Gki8c3B/QOCVhKg9UEtewRzT8tZqCubeZLmc7L
 NbNX5xOta92KD29XOCXX+6htRJ3aBTn6nNzRdBpuVxKhzd+eLg4gRMKJebDfDXrG
 fkDmHta2l1EdhlLxyLCvLd0x0mMGS9rMBuEaTvc5hka6YsM7hhGMZe//CjCO8mGl
 CZyUepEymoFG7nCPpMTgZFxCHzOOljsoaEeOxg6aS2kNv2sTcDkJ
 =cF/N
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.208. Mark Linimon <linimon@FreeBSD.org>

 pub   1024D/84C83473 2003-10-09
       Key fingerprint = 8D43 1B55 D127 0BFC 842E  1C96 803C 5A34 84C8 3473
 uid                  Mark Linimon <linimon@FreeBSD.org>
 uid                  Mark Linimon <linimon@lonesome.com>
 sub   1024g/24BFF840 2003-10-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD+E2XERBADU5F4DbwP8KaHN1H+yz8zaPjOSLJushNA8Qu0hN7GXqd5vgRDc
 zzzeZIzVVxPVdrQ+I24UwSIYu4ww6nfum6kRv/i5khxbYM4zGGPG7s5pmqIECum1
 tKvJ21IE823lcJtUp0C4qhCTZvoc3lADMn9cPgOSJClzHjAYDasOTy9hhwCgsTqP
 aHntu6Uj3BYpurWHJSePWrED+QExF2asNPehIOZ4l7dwpaeGSTxeINH1FYnlF+J1
 N8lvpFQ2H3sfSViVgAtqM27Y/jOf3EkQH0Wym0iCczOxEUFbNH5NWAm6IOVT9owo
 tkh2PZgyfN0AJZBPh9d/oMN2MEKPb6wcqr3c67ZmQG7B+LGliBSVYhWDbd6E2YHb
 bvKVBAC0pL8fzNldEQUUYDTTrWhMVCr7IGzwrd6cEhIZ6b5kqQd1IsIChVG3jCVL
 wWGSgmXY4J7i4Ujsx8k/f6CluNLwmP5t9caycz32QdJAWkzQq2x4AQUy56HDbvui
 QFOqD+PGWqvoUUyJqLbzoASI5dcV35OY+m37Z1Wxhsn22WBE0rQjTWFyayBMaW5p
 bW9uIDxsaW5pbW9uQGxvbmVzb21lLmNvbT6IWwQTEQIAGwUCP4TZcQYLCQgHAwID
 FQIDAxYCAQIeAQIXgAAKCRCAPFo0hMg0c5j/AJwO+VSVExRY8saToDKF3hVe4wNE
 EwCeKFf5ysZjQIJY3pJ9tUzm8o3tX+i0Ik1hcmsgTGluaW1vbiA8bGluaW1vbkBG
 cmVlQlNELm9yZz6IXgQTEQIAHgUCP4yK4wIbAwYLCQgHAwIDFQIDAxYCAQIeAQIX
 gAAKCRCAPFo0hMg0c8c4AJ99m0hHLctAVXjfZYurZBnl2dUL7gCgiG83BXm30rBa
 POtWm2AstMb6uVm5AQ0EP4TZcxAEAMQPPoRMfBR3cRc/T5NsWunFlZA6nB+3BkVd
 p0ham4FoseEh7q+hqa8udARMpTc4LIIL4FU6lIa4L0s3Z77d4bXfJmwlUHuUMSk0
 tnG003D4VDBc3HWSSX/W/CRyN+OBxPljJywTjI4goyXx9Lc31qwpGqYy5Ao8X6EA
 TT9g3IgzAAMFA/wMgON1JxPGr8MSvSLHLMY/xn2PR8lSVZmOlbhNE5hL2FzyFME+
 Pnc8hR31cohFjSXR7hb6SOWrZjYpdIVsa6qdqXIRDbcb5sKEGv9959W8yt+L/kNr
 RlN3oExA2pkYpEQfLpH0HdMmbU61NR0cI6p4ZZly4p6JR0kEajaUOlq/cohGBBgR
 AgAGBQI/hNlzAAoJEIA8WjSEyDRz9lwAn0pJVzrxxaB/PqtJsu034bH5PnlDAJ9G
 axdzE7A6F/UPmrURep9QFDq70w==
 =GflG
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.209. Tilman Keskino:z <arved@FreeBSD.org>

 pub   1024D/807AC53A 2002-06-03 [expires: 2013-09-07]
       Key fingerprint = A92F 344F 31A8 B8DE DDFA  7FB4 7C22 C39F 807A C53A
 uid                  Tilman KeskinAP:z <arved@arved.at>
 uid                  Tilman KeskinAP:z <arved@FreeBSD.org>
 sub   1024g/FA351986 2002-06-03 [expires: 2013-09-07]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 127314 characters]
 bbJlJih0AJoCWn8cneSXT3oShBlbt8J3l133BA==
 =viLB
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.210.  1/4B'E <dryice@FreeBSD.org>

 pub   1024D/77B67874 2005-01-28
       Key fingerprint = 8D7C F82D D28D 07E5 EF7F  CD25 6B5B 78A8 77B6 7874
 uid                  Dryice Dong Liu (Dryice) <dryice@FreeBSD.org>
 uid                  Dryice Dong Liu (Dryice) <dryice@liu.com.cn>
 uid                  Dryice Dong Liu (Dryice) <dryice@hotpop.com>
 uid                  Dryice Dong Liu (Dryice) <dryiceliu@gmail.com>
 uid                  Dryice Dong Liu (Dryice) <dryice@dryice.name>
 sub   2048g/ECFA49E4 2005-01-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEH5vYcRBACrnHaj1X13n0hL3jIXgjAzr63mBoKyJ4YOxJmRZ0Zg/PqmV3m8
 a6JoUrzIeDpgGIqzYqoTRM2vj6qCh57vml3CWJJo1armgTkhOaZRQprrpQ/Hwl6Y
 dTw/ptyZoh5IGrplm/UHiYy+aeQok19cNh7Jd/DePkrSm0IwtafWV4Z6twCgkzpM
 /oO2360jPUbYhr3blugFy3sD/jaj15xl8GU2d7EFW4xXvK+nZFaxfo7frC/OCae9
 k2LmAvgYfG5PrRhiGFERwWx5+a35N5hXhsGktK79QJaHk/8Eir54a7eCDN/nLXu7
 6D11DQJHMUvIISgvffeAJODNjnYu8qMOD3x6S7kmp3BsrVnlO+SJ3L63sO85SdAq
 txC4A/9BobGoDqZGEfgDlDyWNLa1OSWr9Ummg+NvgGo+twKtxDfVgTm2K2G8xvVY
 IBvnYbOMhyokT0TLHwX8ALO2uWhlupmSaF9U4JbUBBeLB0vPuE8wRXq1/L/+PVQ6
 7vNqUIK/rDKtf8XkKOXFpJcv2YyMXkwpx2ZbkJfQ2LQqyR94T7QsRHJ5aWNlIERv
 bmcgTGl1IChEcnlpY2UpIDxkcnlpY2VAbGl1LmNvbS5jbj6IdgQTEQIANgIbAwYL
 CQgHAwIDFQIDAxYCAQIeAQIXgBcYaHR0cDovL3d3d2tleXMucGdwLm5ldAUCRZC5
 RgAKCRBrW3iod7Z4dNAnAJ9VuaLBzcQ8Uo9Pqgz5WgxeuB5BIgCbBhak9RpYegH2
 VrTH1RPKTW/3ZhC0LERyeWljZSBEb25nIExpdSAoRHJ5aWNlKSA8ZHJ5aWNlQGhv
 dHBvcC5jb20+iHYEExECADYCGwMGCwkIBwMCAxUCAwMWAgECHgECF4AXGGh0dHA6
 Ly93d3drZXlzLnBncC5uZXQFAkWQuU4ACgkQa1t4qHe2eHSKeACeNUVs50MWpAtb
 J3InqDgm4Dq4Q9oAmwfIY6EOBFTjAnezfC8IPtK2heAytC5EcnlpY2UgRG9uZyBM
 aXUgKERyeWljZSkgPGRyeWljZWxpdUBnbWFpbC5jb20+iHYEExECADYCGwMGCwkI
 BwMCAxUCAwMWAgECHgECF4AXGGh0dHA6Ly93d3drZXlzLnBncC5uZXQFAkWQuU4A
 CgkQa1t4qHe2eHTGLwCfUBZ0JjgK8wSPAM5Ym3qHZVaVIvMAn3sQ6SY+k4MMG4rg
 aArF3cV+64uLtC1EcnlpY2UgRG9uZyBMaXUgKERyeWljZSkgPGRyeWljZUBkcnlp
 Y2UubmFtZT6IYAQTEQIAIAIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheABQJFkLlO
 AAoJEGtbeKh3tnh0smEAn0EP6UJC0Nk2QkbSIqU+vka21Y/vAJ9DEriyRKcuxU4M
 9/cF5Veh5j/wDLQtRHJ5aWNlIERvbmcgTGl1IChEcnlpY2UpIDxkcnlpY2VARnJl
 ZUJTRC5vcmc+iGMEExECACMCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAIZAQUC
 RZC5TgAKCRBrW3iod7Z4dD3eAJ9Y9J2jCe6ZXtkC163oUSruBS3zFACeKTP7ggGE
 +jYjWiWA2usVKjARdIm5Ag0EQfm9wBAIALlY2EbWQGEJ+8JPbKxUYra75P/ng1h6
 BTK2SSiSCq5y64acd3dRtkhRr5RKsEFN/6KApRlrwgYMl7hIQHL39oFKf9NatTgs
 aUxX/tmy1SYPKwkxXGIH1XMOwyPVcSMGFOf/y542xdYg3X/Vdm2KrDWGeVGOtY8M
 dtOA4yXaA987meCbtTmPCpLx40z0QCZHQ/llZ9k1sVNlSsUodRz1FFdhfYKX30+B
 76J4PuCvi1al95FS2CulesoNkDKVTZOCydM5wYPbMilr9fDd914q5U2Kv4MRWTRn
 CyFazvr5qn5QXm/4DrAjn6QhgFhTJOlSbW1RbKPOibQNVwShJkis4uMAAwUIAJUz
 L2r6tFmgtw4pb3+INO07UzJaQ9EuOy3R+cdFOOJjXVCiXUu1hXmr37TXq/UJMU1f
 V+BFhw1JfK7r8nqGo0Uh934uHULku29cCm7mdvoqere+SqeD82UClZWwIJUokS84
 LJSDjNdGt31SuogziM9kEpxdWnMODOfAGTKA9Vb/KYE4hMut3jreEACHpDXEyjJf
 mBmYNzav93sJhUn0RaTDtpnAz3zPCNOYmWcX1u0e3i4Dr0Ll1jms6YilGoov9CiF
 F6ES3z1qZflpYDtqFNJQsKKzjrRIkQoZAnyWnl5mMGYbZIQiNNChpjlDkXdj3waV
 ZVYhiqyJJx7OwGR54qCISQQYEQIACQUCQfm9wAIbDAAKCRBrW3iod7Z4dAKpAKCH
 NB6TLQ63B4potbH4PhOgr2MgaACdF7mPUJhqXN6mPboqNZdkVkmnjEU=
 =No5H
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.211.  1/4BS:I <nemoliu@FreeBSD.org>

 pub   1024D/ECC7C907 2007-07-10
       Key fingerprint = B62E 3109 896B B283 E2FA  60FE A1BA F92E ECC7 C907
 uid                  Tong LIU <nemoliu@FreeBSD.org>
 sub   4096g/B6D7B15D 2007-07-10

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEaS8qERBACaZz5sEl2I6ZKN0bcqTm2G2jrxPKmX7jBxXhlwonMSfX725Jz6
 fiYxo8MN0709R1xk4tKLJZGM1cxNItFVi0+8bdfdqc88u3cabTM9qYd1hoy3uJtO
 Z8YHGbwzcQfU81r0cs/7xHYROjU1DjM7ixa3aVqokoq+N0nIHNztsDzNkwCgjQrV
 NoU5rFgzsvxbzNmrLSMxpckD/39CGIg1ic4qeuNHEHoTRIGgCffFGr/VOW1m1zYL
 h5nX0qpE8e3y3c7YwX9yxueJtVTZV2HSP8/yILkBMb48ggUcYLaaPFthGAnggx7g
 XB0bLw1TYxeykQoV6MIUf+LXVggJV8js2lZmpC/eUwnbGtDj8ShidE4RlqyMvwtW
 /K7BA/9ZrFZkf/2KysdzweIV4HJG3tntx/bOJDGN/ndp7s7E54iTpTIQLEaXs4r+
 Fb4tEork0p/BrsH2VpDp+O6SjsvpxlOxUN94BkUtwvNj0v2rAXwjEz8RNCXWPoVJ
 G8juOTAtLmgG5Bj+8JOHlHdO1nMZXfAzxYWwVAjE9K1z71kEFbQeVG9uZyBMSVUg
 PG5lbW9saXVARnJlZUJTRC5vcmc+iGAEExECACAFAkaS8qECGwMGCwkIBwMCBBUC
 CAMEFgIDAQIeAQIXgAAKCRChuvku7MfJB2bKAJsHeFHOGni/1CmTS/IcyOYMmChi
 rQCfSjwIUFej0kqsSo0VqLTAjYO0Xxi5BA0ERpLyoRAQAMrvUD7fP2937y24s55C
 MmmGiMxUsutflqt4mIpGf5Ssj0//h2bjFxknChyx7uc9BhnxXPMc1zN+V1onm64N
 eDMZon6LL3ThZvIVFbrjkRv+O1Iqh82k66HNTSl21/FQ8mL3/0E77yfrd8uZSrTa
 cQOdFNYMN5qUbG5U3R6S76CaYX6oN8ctJFXN8PLO2CCn5KBAJ3CWvdcmoadWq6rf
 w7qA0Q6FNXYQq+PxvxNKei9w6xcnDc0DA0/TzaOm3lUQnIQWivgtMa7zkM98LfRu
 wAV7Nn2Op6IeQv2e1i5zT9tL7Au7hUiDXzO2upae3D70tPcUER7k6J7NfWaBfsZA
 CZ9X+jNxECL1RzZnsNRtLMHfIE6YJCc6Onw+PuBE8147hF4bNv79+5JX5XkB7UBd
 8KMHkpCUA4ANo9WTt29JdhUi2hChdATXiIKodWLuUjXjOczDe1HA69BPA6w/RL1C
 OChSEm0M6rYLx8a2X2rpIE+fONE1l9gtWPB1OBOs3/yKO+ozknnbUpMIZpCdq5mP
 BTuLaNAEWTpQUVEJ/32lLdSf0qYtqpn+WycSGXYA0cqRWXYCldTRaA5n4kYC+9ho
 yIueGCwW0D68QGXo+s4VuSaRwTu3kwkQ1H+srwK+pd1wMSabzaN3YgOT6g/L5lrI
 el3jspkgLpEHXYCk8WIZtaCjAAMGEADAsLKwES5Ig7Z3+LFMTFxK3rGMIoUizQpW
 kHUAcwO58jud6t0pxyz5RtYyoAXeCxEGYt5xhYgdcnbWDjraEN94ptOdLeFRa1IG
 y+LIr3+oWF4s4aJqe2WiFd8Fbhlw29YH+CF7E27m6byeYiH6mSB/KuBH9cFicG9B
 mSf6li6ZkL8NGNZ9l1ouOH1TA9hePO7RsHjP38unUFbSg6l9gfiaZF+sNXddZoQc
 qcstmQ2VJQkatqAAPTLwMEIYJvjY+DeKZAHbHfv97eMIe9F2aQ1OdAmL4lyownVk
 fILsTGZ4OOI6KvJD8QcQxn9g5bUwoxIoR1y7AoIYUe84sX5xqo7byzOqlcGQIa5B
 ss21LvP+0gJxrxb8Y1+jDqn8Y3wEe7V5pEchMU9BsTpPD6MNqdkZSiUCA+Yz1P90
 WgO3UbzlDTp19XeOmfCN5srlI2irtijkmKnzLmJFPU3oVnS70vxTZ6JghBERuxa0
 8si44lj1uPztWIc86BmYfEPZ8yuaVve8bI0Cmr/IDUfHlX8/wQ59TV+utMvPrx+e
 ukPoY3Ybxg1r/M2JSEqUmh8czViNrJDqWtEdOYf/oriSJ1mtenq+mEyxwlrgJR5x
 ZAFB/X2eZm/vEnlXttxgRlhT4HBAw6j8ju70BXbUm2boDlQDyQnPG2jA4RbTnvUw
 2aN3vWATPohJBBgRAgAJBQJGkvKhAhsMAAoJEKG6+S7sx8kHi2gAn2xTy641n6vL
 QzMTDTvTKnwMTWoMAKCDsxLiKzQoXpl9Z24xb9BxFdIgLA==
 =nL7g
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.212. Zachary Loafman <zml@FreeBSD.org>

 pub   1024D/4D65492D 2009-05-26
       Key fingerprint = E513 4AE9 5D6D 8BF9 1CD3  4389 4860 D79B 4D65 492D
 uid                  Zachary Loafman <zml@FreeBSD.org>
 sub   2048g/1AD659F0 2009-05-26

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEocVOYRBACUSj+Rt8ZAKD0QoT4yHgh+f74lmw0pegpzvQ1DNBhGdVWfIM77
 n6hK4QSYPhSNT/Zz6qqsZlcnuSyXwKDcu82rOUJmo44UalWbWF/wvz4ICuMMttCy
 WRko6Z+lfzILBr+simnAUX2v9mIxfnkg8mEN5/rMc4rOda49Vbcdc0aFEwCg4/or
 HctUnKwa6r+ArXlZ8bxLX4sD/2A3JzXegkrD6LOwGA/STqNhuolad6ZZpvJGpr1n
 gsYX5ihLaYuxBBWK1ech3Rm8GojvsOpmcc5YTtjb37n/YU9WYoKcmpJukdEYNeSZ
 BQPi7jVXUb3joJobOT1LFYjrOX8/MoOgIxPI7RBM27G5Uarxe0RpF8r94bUxEqMb
 SkgHA/9KqKfxHB7suexO993OtM4fTcnJjCfarcL8qpBOQlYLAP2Q3IGZpjE39Bmy
 tnDNwrZ/8jZrJxBttZ5Fjt01pvMAEpFVHm+QNheqBOqpyN4jmyOsvmSjd4YL5ZZQ
 hUhuPS/dtInONvWvBmOHBsoKdrgoUPO2EuMW1pCm/0i7xHGCtLQhWmFjaGFyeSBM
 b2FmbWFuIDx6bWxARnJlZUJTRC5vcmc+iGAEExECACAFAkocVOYCGwMGCwkIBwMC
 BBUCCAMEFgIDAQIeAQIXgAAKCRBIYNebTWVJLe4bAJ0Q8l/7TIpaYFGoaHUkv/YF
 VdcR/QCfVOdEcCe3gPZ2k5KLC1D8V4ESKue5Ag0EShxU5hAIAI7OSBr9s4l3skaB
 +lVNxA/eEkigb0ghP+OoLVRvd7k3LZpjM27jqMhdmu/8U9bTRTX6kA7Ur7uRF1La
 aSrc6unoufkWcm+w7M9sQv1vwdxOg/D9CZttjMxNJs18VRQokair4OAR9mMXybMT
 hBw3H8B+H0AZh7eLTMXUX8q6fc/Dy7u+sOq6fnCY3vIVUUDaw5XaRKI/mWDmQcMa
 4hB79gvNxHjCs2oF5ntyaCF4nsggmZ2guOjN9oBoo6gm09QFlVA5Nwz/g5s84m0t
 Gtz8sGSPK339kwaT2Tym6yR8UszENlyjG1wVVaQhBPHvE706jOlPXc2JasNKoSqX
 Flyj7icAAwUH/0z2SEPs78Ws3eZq58axkafUowgB31tEM9Ke0jLNy1nGkcC+poyh
 Shl4DNyUbLb86J4FrkFa7bmJi8VHteZYjTxrY9usKLKGkbZV8qNd8ry1emG0Lx2g
 JM5jcRp6ghT2qufHF9PukKwkmNRJJgvAbgSgLi9dWkMymmpo0LsKfKmnoVCy34tV
 704K7JOOBHob6Gi9vMXLYkBUPJCn8BALbZi0WRR/D5bB+OHucjJpEp6lHXYihkX7
 xgSyrzkI2fvDLmJg6/jmtsrQwJFScf2E24IWO5JGLRsuqoE1UUcnmqQKLZ+iH7vI
 fSYNaY/TcB55V2TmpzpYmkGBgI8G1dygrAqISQQYEQIACQUCShxU5gIbDAAKCRBI
 YNebTWVJLTvyAKC5FWGAM6MJaj/cNvWfkdMFaZqAGgCfaktgPFqyozZiZQuoJM5D
 +FztFoI=
 =isE1
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.213. Juergen Lock <nox@FreeBSD.org>

 pub   1024D/1B6BFBFD 2006-12-22
       Key fingerprint = 33A7 7FAE 51AF 00BC F0D3  ECCE FAFD 34C1 1B6B FBFD
 uid                  Juergen Lock <nox@FreeBSD.org>
 sub   2048g/251229D1 2006-12-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEWMWfERBAC6P55NRPt7PWHQk3e3cp6yAYpxsNH4TyMZUNKFjE9E+g4GDe1F
 fd1ebE/as+qcZ7rnIoEqXMYyXW/8X8kdE7FJVoJBmH3RdlaJhHSxogrAHZJ87PWH
 yGC4mP7F2zvLjUqB2fUC6gYUJybmYi7F6run1zPKLr5A5Polx/SpqL52IwCg/5Kq
 vo2Lc3ceBT0L5BKOWFLHBWMEAI/OIOXhv4Hsu0k0Ol+Zdwp3vkw+geBo0MVHp0/P
 XItW5TM5Xi0iqQAcBU2KmPKUinaIJEEPAat5sPMZ/0BUsdmhlD6BqIp0qC8LXm9g
 Tqmenm3WpiJPsd486lW6dxzFqOZKdb6qq87SJ7ajnPB12SykRW26VkyHzNCqiETL
 LigDA/sFPsm499ccL62BwkRGax93iYylhsrV7zXT8FXAPIS/S7JasvaiyHTvRv8K
 u9XSO453WZtzN7TkNp6i3Vw1SSxbrwCRZZ7nspEdMXWF9ZdTtSq8mpA3R74X7dKM
 SXPbbsTFfQ5JR9v8x5T201nFiM/jPteU6WbfyQc1MuMCUqwzm7QeSnVlcmdlbiBM
 b2NrIDxub3hARnJlZUJTRC5vcmc+iGAEExECACAFAkWMWfECGwMGCwkIBwMCBBUC
 CAMEFgIDAQIeAQIXgAAKCRD6/TTBG2v7/bkFAJ9/NodQJ3G3mLhNkT/rv4ncgpOV
 KQCdGm6jx53ESn4s8YJAPKWgym0AKTq5Ag0ERYxZ/RAIAMR6vbusFDGVMpB6AWhC
 cru/N6Qz/kfB6+Ufy2nXcYMMaD2c4MiSUSV6pF08s+xx8oqh6DiGdPvdJQ19ZAdw
 BJaD3tc2EeIv7Eh0upHhC7CuRk3eHHd+KaKFquLGU4HNMEvxXkW+DZ0wWrbVIu0N
 vRBYXJlil7B3RE9+9yQLdoK1IA/N7DtUvbezVC3Px/ZuNe+cnI5neXZVnm9ks9E4
 qlghKSdb2LLghwfBy0JRqssZnvvqS+kRz0LJgKIX57pSrHfx0L5Rwu1JWqvmWKYV
 hkCogZFXpn31ArmmJ54O5KEP4hYNR2FcF8hwNjMqfij29QRi7xpxDLQYgUjM/kTl
 g1MAAwUH/2TJn6E3LtPX7ceMUKVyJRO/OsS7/r8nX8hPRmX/cnnoHTtYOQ1S2F9J
 0IFTZKubxfyhp9ldRx55GiDWyRvGhhjCOuUH7VCSPMCURbMOHi67EDfqbHPzhKcZ
 1lmeqpETmPx4SbVQ9vQ1802gsyZzNy3BQcoK9GIw1Bg6KLYVQ/9rcSDHAB+ULVF+
 YkthjJcPDQPdcn8Zy+xGDuciav9HPaeRXK8nXvx8ERDti99GiuHI/S5+t3wDeTPT
 dZuMiiJYsVc3QuuEN4eMseohFUX6R/Mnm2L0qFc43k3h0vmOoTu65dMEnYZdsKiI
 wXTiy7GaMXH69Iuq9QK5wAQGHwTDbJGISQQYEQIACQUCRYxZ/QIbDAAKCRD6/TTB
 G2v7/Z/1AJ9MfhLFFNtQHDgvIwjgQa2xJX+N5QCfQKUy9vBwNhrVvrH86hoDMhjV
 d1Y=
 =E5fg
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.214. Remko Lodder <remko@FreeBSD.org>

 pub   4096R/3F774079 2012-11-11 [expires: 2016-11-11]
       Key fingerprint = 7EE4 C4AF DCA3 E0B4 479B  A344 7135 8ED6 3F77 4079
 uid                  Remko Lodder <remko@FreeBSD.org>
 sub   4096R/59F38CB0 2012-11-11 [expires: 2016-11-11]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBFCf95oBEACz4PPTc2UpVgNdSDcuTYsMvyZeyeEgdcz57Xyogxfhnwd0SPE1
 XHxmMSlyVuASlGidrez4Nl77dZBBFsLNbPCGk1xJJ4QZfM0Encmmb6C6FIpDzLpG
 ye2oHAeUcKjRGXrSBWAnzMuy7iYdFMTU9TSfib9ZeuEB/rDKb/BaorKHMMVMtR4H
 GZS9+OOv/BYe8d4ZDlF20o67fFdqC7dzHiImr0yu8bFZ9ba4oKcJ1pLs5A45edfv
 TXLWAezexPcEIgJQuDK6CHBHObKeBWkzaon3mo5TV/KD3w28xXmBZzP/2rawfoc7
 IovQQDPqruRLi6y0ffGOg9JMAA55Ev+actcVnD74ySqvHOJxyeKmw9gnkqoTFtcH
 ANVehE7Jz/0VHW+dDauBZj+A9MhLqJKwZ4972ECkWj5x2hzSaIpp+6f5jq8bq0Uq
 hsOR2vkgfSENyHLgzHiXlZLOpX+EoIqFfNjzYyfRdfMzChmg2I9GSrhQlAjZ2P0b
 1Zkocx07HS3FBeEKAs5obS5DkkvN7SzchZJ8njbCIKzQkqtOz2N9HWKkcjcGqTbz
 eSp+iHq4UfLZ1P/DYrv/28/BT1GgmXRABWqkxwEXcDBTUy03mVg1UNP65/keqly+
 t4MItth4T727Tntukx5ag6y1LR2XLweGDye/4gi5TbUymelUmGqysMbEhQARAQAB
 tCBSZW1rbyBMb2RkZXIgPHJlbWtvQEZyZWVCU0Qub3JnPokCPgQTAQIAKAIbLwUJ
 B4YfgAIeAQIXgAUCUKAL3gYLCQgHAwIGFQgCCQoLBBYCAwEACgkQcTWO1j93QHmS
 pg//Yxnxg0Ym11xffAWFhO2RLVziStwtqsyhrNG02lrXUCE8tnLsPp5cZ9p7MTAT
 jiYNW6Cq+f89WePwhBlO9b/LlUt/MUxrxNyhR6ipt/8Vk5WBTbPq6hjFlDGc4bF7
 b8/sJlJ02L3MNld3FrFQCccJe3kQNxOiT4yrCjYTuQdFRfvoE62HO8QDmUfgwlVG
 mFWdNziFxb4ews9L0MXBm8j0BrIp+PA35so6MHW7y13kXhP+WXC3CO71tUWs7TxS
 OP9Wov4vygjAHtNMD7q6qQeIo2VklSMbsfuzt0SRu237RLwFHWN/DlZXJXnR6soN
 ghD31ZrjtQZg/gp8IBcJ9GHkzXMqqdE956Nj0V+76taSzpU+J107Kh8nA4YdssAH
 TasjpvI2Hh4ArIDzIuHjD1P5rhwFtdqzyQWcbFQHLGrRPy7Dzb0b3IKJ6KFJpkVD
 SBZZRGC/O+TcDKTziWeJ2j0OMf81DWb92BXMcaCjRYwxNTL759Daxv0KJPtXAAVM
 X8GFUlzRSQq8xVVh2tksyWKOc6btAP+MMT4DcOtmzlqkuVmMW7jir1gw+AsEq/9m
 6rbhxsXZRVVyK4LCSsZcaz9BsCE7RvodPCuBgj9lcijLkiZX9H0ZIjoBU/Vktw7j
 t6Ta+WqKdswFLuJaz/c6i+aH61M+DHPIR6RMbG5zvuldLI65Ag0EUJ/3mgEQALbM
 Rer4CO8NIbn3NjfYhVi4zHdq3UyOSgdsLhKs37pyd6SKVlouvMZngQVEJvNZTrWE
 2bL0JQRDw627iRSSg8vgOtwobE3e4S/cFB2YZE28uax7HeeYD/ZdekgwZWlbhfnF
 02j+lir5LKZm6UK5ofdQ93fKjS1oBDM9OOJDYz3kF87og0kd0DBdK6rx3WggZSMj
 hhzb8lhJm2QZuP5mq61oO7sTk8FzVw7zf0yj9ccfFicWedGnPYsKjz2QRmeER3s7
 Ectkgy5U1x+MmnKlsc6p2R61kg18Bj7C7YKlYJRjbq8+yMQZgfxGLj1mKB8KQcM+
 ehB/7KSF8+OS78v1zg/nVnablhz1JIJRmV2lJG32L1ZCpnJELMpsjbbkc0/F2kCJ
 RNgj5Z+wUjKAmJRZlx/NUTsMiityXYBhv6Jzsth+t7VaRmnidt7Hep6ifAxkA1P+
 6Fge9JFFOp6xIy1LnVoQgmKxKzmujizpqkwUBIzkzAuPD4oqER0c7u23az/dU6+s
 kEl/6zbASFB4CMIk7aWBNKklYUdAfLH+iKM+xtHdlQjc34IINDx/E1uE9LKVzLud
 ZVxDcwrarV80FzKm12mtJCHcnfN/0b3RFhdnlJ/2vDcqK4nQu8oKQXTXM2OAF5w7
 na/z0UpMaelkzz2oT/WITqlzlVoAKujFe9AWPK4pABEBAAGJBEQEGAECAA8FAlCf
 95oCGy4FCQeGH4ACKQkQcTWO1j93QHnBXSAEGQECAAYFAlCf95oACgkQqMPbslnz
 jLD8AQ/9EbALH+yZbw05tjCkqG+Qfd7Psd7/sHdqh9JsuKb0X+4hIeWRofBpFHen
 spFaWudgZ460lP5ghtXZ7oykLwH2clF2g+j0TpQMeSDUUX0GSP9RJzQHWF7lqeze
 F/7mStJrouGbkX+2Gv3bTMy6g7Di05cJbScDBpZ390l+9EUUZ4umuMYx6W6HML7L
 av6o4Rq2GwvOy8x2ldsF0pUKU6vb58VQIKypvf8E2ZjDQ1zj8psizZh23V6imUCv
 dR5HrZKREb2xM7M8PbfGOXDuX+8FYF7vu92aTSuu4AyNqWhooUKTnuY6HN2MSjax
 DDDG0KlTvkFc2MpFGxwdMPi0u9tsxVDT3maZVFSTSimTUZxv3fQZlGnPMZOUtmU9
 8q1neaX4Hh9uNQKN0lSn+ly0PfB3+qyVfbtRGyTs6ZS8HziGzWZuF/vCZPt/ne60
 rYktI12bKMBLeK0ovDlAoRoTzg/qNqlK3dHePdYtdJlXUpXEOYwX+vUCC7s5RJPn
 gKDUZcSWNZbaniA9LPBg6VMpCRAbuewm8M1pmcSMdns2//dRaOYtTNqJTDnVrRKn
 j4nzQuFGhGjezgW67E4LvNrI4M8XpHFzu5h+OLqjtlCccDh+tu5WJd6rmh0cq3jR
 5N04oxJbsDaW5JNjnGDPT7ax4udn9M/FeMefyo6MCIdPvuoWxSt1xBAAjPhJCjCM
 /F9BlPyfL5Rgm1RN+67SpfmbEDqDJVV0TsF7RhjWDg1fX8ja0v5o4UtlI/xtk27j
 E5zfJlXwoH1IdzHiLXoRKN/XWm6ss5G+uSpKI3JC73gibSKTCz/WCXKdUOmEcMxJ
 8W9RtwcG0nR3duGu4FQCsrV/teLXxHS6HFoa1g4Zy1iLUaZimKOFM40Kit5v7DuQ
 T+beJSdTfd/RCTCiuxD6Z66lAt7/GDxRKNN8t3wSDhVhqCpRdqmUzwA13zqZkrk3
 tmglpvPPMqC9MHKGIeAVPq2dGnCcWr/sUN3CWscWLrd3cfJ9AXU8mNJ8rGPMb3zE
 yKW8JL0iChtfsmbMh0UZjDH7nvH5FJQFYfYUewmQ5/bVqZIZOobRl4dd7Q9thQD3
 jC0b/LHERrNrnWCel480NlcjKAtXGORAYjM5OqnAP5WR/jwrkUqBtRXfTWcwgrwK
 MTlPRw9X1wqeXQZFTK9RDAkytjUwrmfbaDeyJpI+6oXzUfNMzvJ07YN1J5HJz9HA
 pmuHN7XTIUQESrD5xbneN7u7uizQ8zdht0bZbhgN/yn9OeBqbLA8LdmJ/y//eWW+
 9bgvhQz7uihiaXjc/DfB9oo+2yE5U8ZMoW/bNfMSHFu4Nj0y9NzbbWgRIrNeTPUG
 5sGIhylLEgeij8uoeFOeA1qMqbhYORfYOxE=
 =+q/B
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.215. Alexander Logvinov <avl@FreeBSD.org>

 pub   1024D/1C47D5C0 2009-05-28
       Key fingerprint = 8B5F 880A 382B 075E E707  9DB2 E135 4176 1C47 D5C0
 uid                  Alexander Logvinov <alexander@logvinov.com>
 uid                  Alexander Logvinov (FreeBSD Ports Committer) <avl@FreeBSD.org>
 uid                  Alexander Logvinov <ports@logvinov.com>
 uid                  Alexander Logvinov <logvinov@gmail.com>
 uid                  Alexander Logvinov <logvinov@yandex.ru>
 sub   2048g/60BDD4BB 2009-05-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEoeNvgRBADOJSDLfbgPuLl4Y1QO/1BjX2MFveYtMacSLpaJURRewkBmoKBz
 iXa9a5A+uKiQTtX8S8bnkvwmpzEua8RMWUN/XXb8aZc7DPcZbP9NFNaNZ8BLgnLC
 FK1gIEpJpcodAQ0K5HAGiLwjsK3RdM78pvDUJDDmWPaflk8llx4H7kjjTwCgwIRy
 /8f8FHQV3zUIGqmJDt5019cEALE+LTHjCOZkk0YKqVETY7IAKX48t/o3t+ybkqcC
 zFYIRA0v7FR/ipxkNgSzi+tKMaExDuFuV9aZEhepS54eXriXyGmzvevINlHlFgh+
 60WrUGIlkVtQYCW4EeP7kB66u6uV6PnKqFUXPLoF7MDg5nrJqaX7r4+9d0JopClN
 1L52BADKV1retnbON3PP460z4j9IJspst9n1AZ3y9S5ojZ0IvhL9UsjazvRheTCm
 fArizJMTtDUo9SxWXCtpfxruYJSB5jlhkZFMC1oj484mxm/MgNxJ8mov2RAT1Pu4
 85PjDNtAKq7yrTf8x7PbNVpoJkU98lZQ84Bt4RbaqechA3l/l7QrQWxleGFuZGVy
 IExvZ3Zpbm92IDxhbGV4YW5kZXJAbG9ndmlub3YuY29tPohjBBMRAgAjAhsDBgsJ
 CAcDAgQVAggDBBYCAwECHgECF4AFAkoeN8wCGQEACgkQ4TVBdhxH1cBPpgCfYR9i
 yz3P8GnzGKzKacDhYSSRdlAAnikohHSQEqzFyKimalh+Vk+yv1mutD5BbGV4YW5k
 ZXIgTG9ndmlub3YgKEZyZWVCU0QgUG9ydHMgQ29tbWl0dGVyKSA8YXZsQEZyZWVC
 U0Qub3JnPohgBBMRAgAgBQJKHjeCAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AA
 CgkQ4TVBdhxH1cCloQCdGWWbAGInaDd3AqGI07kIeHUfZjMAoKmujjBeu/1n8bsO
 OwUIcOutIiBRtCdBbGV4YW5kZXIgTG9ndmlub3YgPHBvcnRzQGxvZ3Zpbm92LmNv
 bT6IYAQTEQIAIAUCSh43kwIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEOE1
 QXYcR9XA8FUAn2F8Y9LTsvK/GJAMU2gboZY1DCxnAJ9XnCdD3w7uQscd+sqIJKuV
 KlYsDbQnQWxleGFuZGVyIExvZ3Zpbm92IDxsb2d2aW5vdkBnbWFpbC5jb20+iGAE
 ExECACAFAkoeN6UCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDhNUF2HEfV
 wG/MAJoDJLimxPsysGqpRWMYb36855NBLACgn8ICeVtfyqCoxAv0YIYk3K0M9we0
 J0FsZXhhbmRlciBMb2d2aW5vdiA8bG9ndmlub3ZAeWFuZGV4LnJ1PohgBBMRAgAg
 BQJKHje5AhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQ4TVBdhxH1cBWygCf
 fvEVUFOSzEPylUJMZt2NKaiwomQAoKY66bHiWUIReF5NliBlsM3bv5qyuQINBEoe
 NvgQCACVC9Ks/nhrOVuHu9rj52KRW5J7S+20ZOZFOb90iVFCwFSn3/TstqGnao9X
 NQBiopv+i5s5AdmVjUyHnTSMggqVGfxltgG6ttxmY+iU7N/+aIXkbPzHZ/qZgKv5
 ey5MhS+kFV8Jh2IGV6beaQM0KNJ9LV9Hq1+V4ae0ulaGYFrNnbwI/rdXZ7vEETCF
 EVM3NP6xsgiw1NQ/V6b7iriTroeRytu7XoRlchik/7sQBLBwUvIVAD7BdHqjQ1NF
 SILyTr3aPagu1CxARmkCCDX2sfcqT2/9wVECubbgcUMRjVHm7k5BsZK7fGmHcBZg
 /5Rl7ngtUYwsR4h47A0aH4IPZ7AzAAMFB/47qL+Rb4wqF+sCWM/QqCrgFqMwz1JI
 qc26U0+a6bZ6kJBbMzvBcdrVFRfn52qacCdfFpdI6Yz3fWQyzrAZwqjCTPaGBeEd
 rSVbonW5dDjJTkSiKMlo53D19PcNklSjFnCrPeF4aFQ4VbT3RioWh9P00xhCHPQB
 hsg+cU9rm5ZASMht3K+k+bgpHT9gPVzckZTC73l3xaNetTDnHlRDw8ATvBYcUfYr
 kDp3tgkZ7a1pPRMz1oOKNWtxW5Z07HLj0Lt2xyZDe0BSImiAa7MYC4PKLi5VlDKB
 GPjLDrM9K1XUM3Gp8O3bd5qjnsueu6XOdGZA93g4wjXmzDqhFIXy5T69iEkEGBEC
 AAkFAkoeNvgCGwwACgkQ4TVBdhxH1cA3KwCfV8uCW9P5gm0+Dfm1miO/j6rvexcA
 niBfAchAUVjJn+UKjAd5RD1SFTAm
 =bSSP
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.216. Isabell Long <issyl0@FreeBSD.org>

 pub   4096R/EB83C2BD 2009-09-26
       Key fingerprint = D55A 42E7 0974 EFD9 3939  56B9 6E6B E425 EB83 C2BD
 uid                  Isabell Long <isabell@issyl0.co.uk>
 uid                  Isabell Long <me@issyl0.co.uk>
 uid                  Isabell Long <isabell121@gmail.com>
 uid                  Isabell Long (BitFolk Ltd.) <isabell@bitfolk.com>
 uid                  Isabell Long (College) <IL18685@woking.ac.uk>
 uid                  Isabell Long (The Open University) <il948@my.open.ac.uk>
 uid                  Isabell Long (Mailing lists address.) <lists@issyl0.co.uk>
 uid                  Isabell Long (YRS) <isabell@youngrewiredstate.org>
 uid                  Isabell Long (FreeBSD) <issyl0@FreeBSD.org>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 13992 characters]
 PMOrsNYPKCBRPOLtvcqn+iDQ1A==
 =yYCC
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.217. Scott Long <scottl@FreeBSD.org>

 pub  1024D/017C5EBF 2003-01-18 Scott A. Long (This is my official FreeBSD key) <scottl@freebsd.org>
      Key fingerprint = 34EA BD06 44F7 F8C3 22BC  B52C 1D3A F6D1 017C 5EBF
 sub  1024g/F61C8F91 2003-01-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.1 (FreeBSD)

 mQGiBD4p5ccRBAC+tbiJm4bc9dO8oaRhVGqWmNhYfi2GnX4AM2h+L7bcIU/7jWVn
 uWGe/PFHDcuOpEov/XRw1gmgoNh2DopTxf363DVMevmGW3R1842YMmLvCYZ7C0Rd
 0GdbHW1xXeRSygs6peLcPGQ/7ISK0BHMudFim5FrpD0tq3qrqRmuGgls2wCgyF37
 u+ZoP3xiP0wANhoWJtyBWQEEAIeYSHvIPKFIo9FG/+wckx9Fc+hLXPKwoETBPof7
 Wft9zXiYyowuGj6/ydb6v229nI3lJwVPR8X6Ptjf6rO1vjf7uUED9dNBLr10vdW6
 jYClBT8lqJAq3DzEpDk2kOlhYwtrykyld9Ys/7vgliuBB0XRUxGVNieqDck7PZWL
 ewz5A/947m/ZrlZbn6+jsshGk30/pEXZUhcDnUBwW26GuFk0TGlXBha3N0NFwqz3
 a7qnJcvSTKfeZJY5NCwqzCo/rLpmaNd9JCUrgwSd1MI9Txrbj3lDRy5dj4FZBQ2N
 BVgni7SRKaiPw1KeEprSOR8yiM9ZjbV1g5zPeZ2bZhSMCP7mdbREU2NvdHQgQS4g
 TG9uZyAoVGhpcyBpcyBteSBvZmZpY2lhbCBGcmVlQlNEIGtleSkgPHNjb3R0bEBm
 cmVlYnNkLm9yZz6IWQQTEQIAGQUCPinlxwQLBwMCAxUCAwMWAgECHgECF4AACgkQ
 HTr20QF8Xr9fvgCfUMy+qlN9qQtwMFAKWViSllk0xYgAnApLMv95d6Ecrj7+U9Et
 liAwNQXWiEYEEhECAAYFAj4p8nkACgkQtNcQog5FH332EQCghR98TNpvYGdrsg6Q
 S3BngO5n3VgAn1zo89iPy8VMP/kXq2jlzs/74+i2iEYEExECAAYFAj4p9igACgkQ
 2MoxcVugUsOwsQCfY34hwJIc8MapwIy8fWmCeLs4T0IAn0aVpewWF99H6SapelNP
 hvDzTYLIiQCVAwUQPioA7mVgqaw0+fnVAQEUHgP9EJXxzQlkaN8VsfRJo/UFmC4z
 wGkwu2yatUjMSZR58VpS9rF6CH1rzmNFtZZmIh6ItQ/mPaUDW2yObWBRL2r9vkVx
 e+DPcpcZAebM3ibjsOg05cftcphv41rLak0C2Nec3MXnxT15O7fcO6aO+d4oJ2Yi
 oL7YJX6RHrqNCTQn6/65AQ0EPinlyxAEAIGtuZXdf7K51Gb9jijgdV1NMPKwujoq
 K9f1PZocpDve0vwXN6AvzJ1L/LTrZPvBZ0UCAJR/zVtz4H2bnSqalbd8j8bmxfYx
 0SA3QNAKJhgBGNlnK4HvAGJCs8oXYp+6Ph9WWlTcPzkfscPFc42VcUEdfL/5kyLr
 OvGAUW6D7iCnAAMFA/9CWXarz2QMrkduiasc8bhSmv2lVOfUVcIdz9imc72Z5GUk
 FBiQJ2kuqJrxMUqAgoccnJ9R0QVZwCaQyRNakEQEcENBKq9Haa5LLo7nD3CAiqIi
 URqloJORSzXoQCrw8OelbBp9RaEqVdCecbNqAbA8Ru4NIwcyZCgvnX/bUTKq54hG
 BBgRAgAGBQI+KeXLAAoJEB069tEBfF6/XBkAoJtQ4ECj3ntS2xlODgB8N+cKIsdb
 AJ9Lwk2EEIZhvzhwvhpwIKAhWhHcmQ==
 =C3Jv
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.218. Rick Macklem <rmacklem@FreeBSD.org>

 pub   1024D/7FB9C5F1 2009-04-05
       Key fingerprint = B9EA 767A F6F3 3786 E0C7  434A 05C6 70D6 7FB9 C5F1
 uid                  Rick Macklem <rmacklem@freebsd.org>
 sub   1024g/D0B20E8A 2009-04-05

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEnY+RIRBAClGSwgcIr4i7G4CYEa2cBHRC2UOB75/AXFqxmzAOcype8WInbX
 f4xLBa63VMoM7eis27BouVRcHI64oREIL9yvvMPwRD2ZINY5UD/zkls7fw9F2NyJ
 AgntQEPRDkk14AEiIX5uvB3l+JyKmbMNpJuhrKpbxc5qvaDTgD02y9TurwCgguAy
 pMVQu2mtVccXkSb7WEh95SkD/0jTFzDTcuowbxALrPgQtlGEXo7RYLPIFxTI748F
 h8Tgra3flWp2QPAnWBJEzrz+9rl8wqQ2ddb9IydwtY49BjKIrXhj2Lh+8l/1oDKr
 RXzRbNH/lGHhmphW42DgM9mOCCoSWugUEu458I89FjuoncdBiDdi7HUxPy/rZ5MA
 tnRRBACWL22M5MPfD9dl9SHvnoBz47nwlBeg0Oxl22oNfiyTQdJ1q+g/wGpDPAll
 eqs3Svky7gj+f5375K/DEYaeFSRynXeetpdqpkBDlp4mRdDGcpd/4ImAx6deQTXo
 EraidVlZ0Fjr5cP+mFzoI41LAhTJa/VUoUkMxq+gJAsXsSF39LQjUmljayBNYWNr
 bGVtIDxybWFja2xlbUBmcmVlYnNkLm9yZz6IWQQTEQIAGQUCSdj5EgQLBwMCAxUC
 AwMWAgECHgECF4AACgkQBcZw1n+5xfFFBQCfbFJpzSEXUgmoEl4RBgoPNzu9SOgA
 mwW8fBCx0RDGfho/8S/PjZLQ38JCuQENBEnY+RYQBADMlW1YS4ZhBh4PCOXTJsjT
 Vda2DEn1W+2BzZw9j/DFAFjm0U05rlEsfz584Y/SLlPNbCZ979//3K7XxicRw7zm
 E1Mzahy2jrmGGJv2GfAZ+YyJPGA/xndNA3/ocT1x03LMWNbZwFBe4Kk5ShoqPgl3
 cO28w3TJUnrUZyo+h3WhpwAEDQQAkwVB18LmtI0CW4H0/jMgiz5B0z3yZdlinbif
 +EEFHhhdp1tXtxA/jyp3FsW7hOlGXQi/tACcxJ2UBcYAZh03+x7bUMnJpisPDnJ3
 UilCuwk5cAkQmGeAQ7ukNNBwVhJ0ZfW7p2lZ2RwW7zSjPK7RMW1EL4Scwpey/ojb
 Tv9fVXmIRgQYEQIABgUCSdj5FgAKCRAFxnDWf7nF8WUfAJ0TTs+DTEkwHeE4mHAA
 CqfpXJXMhACggkoKIIAH+lHNqv3Uy9q5RFd8t3I=
 =F39a
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.219. DEG". 1/2-E <bmah@FreeBSD.org>

 pub   1024D/5BA052C3 1997-12-08
       Key fingerprint = F829 B805 207D 14C7 7197  7832 D8CA 3171 5BA0 52C3
 uid                  Bruce A. Mah <bmah@acm.org>
 uid                  Bruce A. Mah <bmah@ca.sandia.gov>
 uid                  Bruce A. Mah <bmah@ieee.org>
 uid                  Bruce A. Mah <bmah@cisco.com>
 uid                  Bruce A. Mah <bmah@employees.org>
 uid                  Bruce A. Mah <bmah@freebsd.org>
 uid                  Bruce A. Mah <bmah@packetdesign.com>
 uid                  Bruce A. Mah <bmah@kitchenlab.org>
 sub   2048g/B4E60EA1 1997-12-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 30954 characters]
 vUps4fdR3nZq/MRKTsIAoI5BR4LrbaOwqe1M5HlH1W/jDLIp
 =D0KC
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.220. Ruslan Mahmatkhanov <rm@FreeBSD.org>

 pub   2048R/F60D756F 2011-11-10
       Key fingerprint = 9D18 8A88 304C B78B 8003  0379 4574 0BAF F60D 756F
 uid                  Ruslan Mahmatkhanov <rm@FreeBSD.org>
 sub   2048R/B658C269 2011-11-10

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE67bzoBCAC/blN8XOxBx7pBlsAAwFJgxYOSYCw4fTFMoyoUBWEHuq0LcNIn
 BO4CqVyCiWcwMl/cLIh/1OHLjpU9orNrMSnJGdCvB2FAFYNm204ZMi3guRMe5xXZ
 zvxSa0v6zQtTRCEs5ny44XryxbZkPE5GGgyd4+sZVAcW65SX8hbmoIvL3v33Fq1w
 eom0nYBxU1EDIwZMl09FWaL02vBvlbSh3CYvmDTS6WD2t1ItDxhUG06+zoJs2YCb
 6f+iUk3ZLYon06aX3VB3lmT6ffSdAEX6uT4V5NJ0B60xhQP7WAEmSm9ScbnFIme2
 jpZcun5TKywwm7OSyOk36Z3EQyyxOSHRNJ3nABEBAAG0JFJ1c2xhbiBNYWhtYXRr
 aGFub3YgPHJtQEZyZWVCU0Qub3JnPokBOAQTAQIAIgUCTrtvOgIbAwYLCQgHAwIG
 FQgCCQoLBBYCAwECHgECF4AACgkQRXQLr/YNdW96jgf+Kyc7hvCTNlkisTOAYZ9+
 9n85WGcPLO+vyZJ6xlP41V02opzCjCVrddz3t4sq7eCFw7DTSIFovC6Cw7rAWgx5
 pa2idb6fhk/DMUwpd9I9CG9dm41WBWVkxRV3KMYyF2TYwH7VgL8KdvX1C7ZkD39V
 NKWHcSPwWxCEnrvfcGZz+wOHeZytSeC4Gpd4sEnAVj0HjulLXmF4YHN/cNy9Zl52
 +Pt1iSzjV5WJ9ywbruhOxQ7B8q9DQDveWdtSMbaZNzW8JHlj+gy8Ww/UvdsesjQu
 NE6Tc+QPIigBsx+MTbAwByDY6xj9OOCGNPeAxQFjNpz+iRS3Yuz04VxMy+z3cD5t
 YrkBDQROu286AQgA5FORCn/VS3x+aUO0zAHm/WmTJZFRxrmdkDexFZgxuHjidGUU
 fbGzvyu/1fRtft/3Np/M4aRpSI96qbYXLyCeJgQjNp36YRKqJkBiPBDQ9QLZpP6L
 nJn/NzF6/5pKLt+Sg3SdOV1x/4t+tkmcMa2+Y+yEjd9YWE67Cc5RevfO1As4B00v
 jFTl5LWxOc2kzVoB4OxxOLCdj/2zkIyxEPe4z/KswGDQsmsAfivHVcT1Kpas6Jr+
 sxCwZhSNy/BSuYtwHqGV8xw8vZlJkrOIn25StwW7hVf1oNYQnwTSBRwGnU8WVsqH
 /2VfIatSzoJ9L5EzoVjkgNxQ+9T5xrqf8G2ddQARAQABiQEfBBgBAgAJBQJOu286
 AhsMAAoJEEV0C6/2DXVvDjcH/1/sV6J33aR2Wk4fT8ChWWuUl3Dx7CnDUuCvKo/v
 oppP/bW473lbV+AlbG8WUpsCUqKy5WkU4uHjSfp3F1UAPDBTU0lgcj30jr13sGLH
 n4+WReFFZfDIwIBWNHqbLmPHEG2jItF7ssxL/nsYqTo1UWsI+3fToJX98Irz0PXL
 mX0e8pWdDe+pR34OcYDRB6Fe17cKE/5wpVSvd3+YZ7AYuq5wxfwvZVdOhcXSnWS0
 ksMRQMkG5A6BEY0ZpAZWNwRO1TcVqEJC4L6ujls1/sZEOIKSDj9UU1OC4tQYAsx2
 /yW99HFkq/4I+yL4zFzmqPug4j3GXKkNGqFNmExVys5uXv4=
 =Ykam
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.221. Mike Makonnen <mtm@FreeBSD.org>

 pub  1024D/7CD41F55 2004-02-06 Michael Telahun Makonnen <mtm@FreeBSD.Org>
      Key fingerprint = AC7B 5672 2D11 F4D0 EBF8  5279 5359 2B82 7CD4 1F55
 uid                            Michael Telahun Makonnen <mtm@tmsa-inc.com>
 uid                            Mike Makonnen <mtm@identd.net>
 uid                            Michael Telahun Makonnen <mtm@acs-et.com>
 sub  2048g/E7DC936B 2004-02-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEAj2wYRBACHexVRaQ9QldEPYx/ukn2dcSi1H0ZFByRZvdB4ukm+z4FxfhWt
 mw9gaq88mWLySchgnv7tkJDVGeZa4PLxDTdOpnEC1dDcjOCJiHAlo6gmBKGSP4hn
 h5XfpEvyS8EQqbMD47CBAYstj9upnLYwpGYfU8x72tUUaJv9+mww9MC1gwCg5xYP
 /iBwPb87nkOdB93/pQnxLW8D/iGeIKt0Zw602CTQvNnFjB/0RcO3JpwU7wn0ptCr
 5/1OAKWEyYGfHGt6DZtNPzRLJBXmLmlYpCXDn7ZB48sz4Xgrf+05j0/lPHsAdrPK
 OKCz/CJR/aGIPPTLQNTbMWg3pL47F+cfFhDwgQ8yzzYdQZlyDSv3ANPm+YZQKXKr
 LhwLA/4mX5+hW2ntcnPXUOfnya6/KIufDBqjl620heB6cbrFLv9IcqVvDiVfICYH
 jluYx+wqtKMVLa35fs5nF1Qv+wLelLjay+YdlYpeCCG5MzA3w5WJOK28vk5uAaDi
 1rSep5ePi5ENmhiWRprvx4qPZef7MDWQ6rTR88781J/ENdV2JLQrTWljaGFlbCBU
 ZWxhaHVuIE1ha29ubmVuIDxtdG1AdG1zYS1pbmMuY29tPoheBBMRAgAeBQJAI/Zg
 AhsDBgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEFNZK4J81B9V7aQAn1mBnIqieZIE
 T0IJd3Lk168oZKodAKDVaBuIZerbQDHPIPaJUSrUAe1NUrQqTWljaGFlbCBUZWxh
 aHVuIE1ha29ubmVuIDxtdG1ARnJlZUJTRC5Pcmc+iGEEExECACECGwMGCwkIBwMC
 AxUCAwMWAgECHgECF4AFAkAj9w0CGQEACgkQU1krgnzUH1VdiQCfcLWbaIY470p+
 h04RXpg+xQm4I5cAni9caDZovhablGxWXnMYcYADz7W/tB5NaWtlIE1ha29ubmVu
 IDxtdG1AaWRlbnRkLm5ldD6IXgQTEQIAHgUCQCP1xwIbAwYLCQgHAwIDFQIDAxYC
 AQIeAQIXgAAKCRBTWSuCfNQfVXYXAJ96JaLB3DA9YSZU6Aan4Sej2jb8NwCfTw0e
 Q3zx1z4ckf84ZHO6+U5tGeO0KU1pY2hhZWwgVGVsYWh1biBNYWtvbm5lbiA8bXRt
 QGFjcy1ldC5jb20+iF4EExECAB4FAkAj9jMCGwMGCwkIBwMCAxUCAwMWAgECHgEC
 F4AACgkQU1krgnzUH1VKpACdGThHL9XMCCm+XANPFsq8JJL7uPIAmQFoL7uMxJFX
 ZkmGhFi9jN2DadQsuQINBEAj2xEQCACtWPMKOwphtmOC82oyZf3PQRcyhd0BtDl3
 P8EJg3fonvnZIKkiIdo5QMnFlCUd33lqkiLaduwk64SYBHHHkMGCtaViRC+1ukcA
 ehJuv7QaybNCpPUdXXA8MUm1MqSflIKI164OpoFNFHIC2aWG65QNaMOkbHLcAu17
 5czXYMN9d5iXeZSur9DSrCLz0vRxjaWZ2ksr0jvijFasXsfydiCB0MXE3reZ8Yln
 koRIMCsLcPOGZVi/7Gn3FRWpCd0H9Z3UUVRAHLDfNySwI3+NqZWdUwk2gu/jZ7at
 3b/PmGR12zHj2sL0OPg+f7rDSfOZfeR7YnM38McGhhd/XXg2+4yvAAMFCACSzNxE
 ibtE9JfVIBhA3UD4qE8jFug5Uy13/NM672gDr7lnPY3d3pZeVKWnWEqQQhrKF8Tl
 G6vOT/noCeTLO1Mcz+JeUY2WlTj5AGktehT2bLgV6PAGIUUP0zifqR47kx32b8qA
 ZSwTUqus1QFD9YIbSfqbZu17FLk4AN8BSeUfM6Ktq5nR26+5v8WqMsGfXPvZSGRG
 GqwTN94sW2B2GV2ep4OghClycSdl9CBfhawpaR1NjNXadtEWv0Ww8ctGfojR8Qoo
 SVWPeXcmMGIF84gnmzeCOdAZU2psqBJ5XCus9HArm09enyVReMxrWAgcKxroRK6V
 KzjDkeYkYI7PySStiEkEGBECAAkFAkAj2xECGwwACgkQU1krgnzUH1WPyACggAOh
 k3grQGtqSllXt/GlhTaCdogAn24UzgrsnW6yzrpNeoWcmyDFJ4nR
 =TuyI
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.222. David Malone <dwmalone@FreeBSD.org>

 pub   512/40378991 1994/04/21 David Malone <dwmalone@maths.tcd.ie>
             Key fingerprint = 86 A7 F4 86 39 2C 47 2C  C1 C2 35 78 8E 2F B8 F5

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: 2.6.3ia

 mQBNAi22tqgAAAECAPARUB5VpJvYQyHAzL0WITkJmKG1lpwFMPz4jenjJRplPr33
 OvKxQcXh1bAWNVFiJVDJsWwnfif94wQdVUA3iZEABRG0JERhdmlkIE1hbG9uZSA8
 ZHdtYWxvbmVAbWF0aHMudGNkLmllPokAlQIFEDCwQ4yqxsuiiP+uKQEBricEAKAE
 f18kbKpFKU/DPRVhVYlLHCkzXLzZCiTxBUGjMaXZswKwrjVLF2l8mrNQhqC9L953
 AGyUYNfPLtqw7b088v3ATCIrZ+izWyE27IrjZWSS57GZiDtnkm6moarG79yANBql
 LBc0sK077cHEC+/gDwXNBLg0NNpHkaVXPxixt/ETiQBVAgUQMK+p+pFKk8pIl/up
 AQF0QQH+ME6vPoS2+FgSN1q9R1hwmwEPAaYdyfhv2lj1/6KYDEaO9Lhw2u57nW7z
 CDpir9gNN0X9U3XrIxlJ7wWxa1k2PokAVQIFEC7vu/zjBB1VQDeJkQEBWFsCANX+
 qJO8J6qeJW8gcrmxMBA0l2MjEHcu8XNky6YT3yS6So72yL1lZbG78Sew03fXnWNS
 GyhRrPz7sURNLtJDNDo=
 =wpn4
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.223. Dmitry Marakasov <amdmi3@FreeBSD.org>

 pub   1024D/F9D2F77D 2008-06-15 [expires: 2010-06-15]
       Key fingerprint = 55B5 0596 FF1E 8D84 5F56  9510 D35A 80DD F9D2 F77D
 uid                  Dmitry Marakasov <amdmi3@amdmi3.ru>
 uid                  Dmitry Marakasov <amdmi3@FreeBSD.org>
 sub   2048g/2042CDD8 2008-06-15

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEhVTssRBADF9Mfvn18A7k1V8XOzgZGrqf2jbzWMklD5IgPtziN2vla1gTk4
 OuvL3aR52ZGE95LjD4iy52jNpAijefBhR/vmgF3IAuLTLXYJTFR5qck9nXNhO2hK
 OtS2yuzoUVEHUSENuj3WFieQJJGyyLZv88iAv85VSyhFqYWG4apkKMnJtwCgmMkC
 DWhsfLPvVSd+pDVGE7A38nED/3b4xN3fhfbmoa84s80GsVVRZaYLWmb+aWgTJatS
 y362CQkLjTAzO6G/6hVyEDJpJCJs81uEq61QZAiGBmru+vK16JNhQ0Ic5l2GBI+a
 VPcXm7O56Na8G1CVF32L0HePwflxl3hB+t6wR4OUj/Vy17Sz1+qjb2ixEUoaGw7r
 hagVBADCu8vNQkg/lplaSj5gz+aoaf8qyE9teS6yq9nZjHGWKa106NJlWtFIYJin
 X2FGpXJ8HCPMU10jDLFmgrYw6y1Tdb+hUhwd2MXXyvWZ5wY+j9PSN1p9Nii/N4Ak
 tu0impFfhzGPD2Fnn04xQ0BMtulqT/tNvirVZBraAiGcZXlzhrQlRG1pdHJ5IE1h
 cmFrYXNvdiA8YW1kbWkzQEZyZWVCU0Qub3JnPohmBBMRAgAmAhsDBgsJCAcDAgQV
 AggDBBYCAwECHgECF4AFAkhVYGkFCQPCeJ4ACgkQ01qA3fnS930PKQCeLA7oB70W
 N3cHh9wXFsa49it52mMAoJS21FFsCD2BkEyMiBPZ0dGF7yo7iGAEExECACAFAkhV
 T6sCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDTWoDd+dL3fcmrAJkBW8ne
 ngKYN3trV8KemDfCdzbOJACfbGHkP1as9MXV4CfPKBOxLirwT1OIZgQTEQIAJgIb
 AwYLCQgHAwIEFQIIAwQWAgMBAh4BAheABQJIVVwVBQkFo6fKAAoJENNagN350vd9
 JhkAnjJ33/8+hUAx//V6LfbBQKOTQI45AKCD5f3aw8qIijQTBfdcnI6cpga3SYhg
 BBMRAgAgAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AFAkhVXOkACgkQ01qA3fnS
 931VNQCfeOrFql3/Fn/ipRBXS2BaP2orubwAniIwTnODjmBSEa+NPXbA+WHUTVR5
 tCNEbWl0cnkgTWFyYWthc292IDxhbWRtaTNAYW1kbWkzLnJ1PohpBBMRAgApAhsD
 BgsJCAcDAgQVAggDBBYCAwECHgECF4AFCQPCeJ4FAkhVYMwCGQEACgkQ01qA3fnS
 933XmQCeOCTQYuvEkbBZBRmxqqqtjwTD1pMAoIbdfbVz52in24ws8rR3aqKEwcLc
 iGAEExECACAFAkhVTssCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDTWoDd
 +dL3fd8aAJ0ZeDCt4wLmXKwmUReY18i73YkkowCfcNljbcOGtI+36MlO8uwC1Xhf
 g/2IZgQTEQIAJgIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheABQJIVVwkBQkFo6fK
 AAoJENNagN350vd9XSEAnj5MNrTagKZ6x+tPpVybpg1m1JRkAJ4yjqDpLITy239m
 4YdPgEpJDxlCNohgBBMRAgAgAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AFAkhV
 XN0ACgkQ01qA3fnS931rwgCglmXVTHyg3qrLjNqWr8Rnv9BfGAUAn12fqUCfYaun
 jvLwWDxuk2vFkms6uQINBEhVTssQCADL4G5MUKbIROpcZnDNjMHsDKI78U01JOpR
 RVzN4v0rvECH0KsrR0zg0XI9/ljSC4KdqrOZyI1f4gTZ07XGMkaXRET4bfvcJE4d
 TUcYzGNdx6+uICWf7PJt/wc4SpdzK+SlskZO/MmgClUXl0YeuADBTXolnB0BTpAA
 dUM4Hy0jgXJoOZ5xj95+ejQU2BhrKEr6aSBrbCcZ9ToWLRAMAJwc239cOlQfX0ba
 dBu+FF9rPdsvi2cSy1ALis5fmjBkTDsNCOanxB4GMTdkIkNztNVnnuHyJplOoArD
 SdZJlps+McfLxPHKM6aN+iJY/ndL82bISlohJRxfv9K67ur+OKmXAAMFB/9hqaE0
 vONs13OVlZMJGWYZND+WcVc4Q/WtiPBPy+8ZH+Fh1P60sZsJup/vcl5esdbrtaMd
 YASOh5nPhBRsSQ3Yr2F/acuXhTA2NT7ubbpYi1/PV10BgYvz4ijgnknNVGoRZOeR
 IlZE4ZmpYIXk56IbhjHFhOCHefNGNDVMF9xMwMcwO+nii+GfhfvaiSG34SnCRYyR
 SxcEudqunMPOJQdGqdRTlQLE3i+xDJk15VKWjUF4ZGIxVhG0aVepEDKXXFdFx5s0
 ax7k+B7SQyP17+7sL8gGNjUpQYEdJLpxaB9gs0jF31Yh0tGHY2Yk4kb7U91gszAI
 m8q4owrHaOzUC4RViEkEGBECAAkFAkhVTssCGwwACgkQ01qA3fnS931r1wCfajgY
 wFcbQu8CJvmbDXSYZi5aFfwAoILimrxBtjaW0XbsHY9YfjAST2Q2
 =6qxA
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.224. Koop Mast <kwm@FreeBSD.org>

 pub  1024D/F95426DA 2004-09-10 Koop Mast <kwm@rainbow-runner.nl>
      Key fingerprint = C66F 1835 0548 3440 8576  0FFE 6879 B7CD F954 26DA
 uid                            Koop Mast <kwm@FreeBSD.org>
 sub  1024g/A782EEDD 2004-09-10

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.6 (FreeBSD)

 mQGiBEFCGHYRBACI9ERMi5j2009Juy2kpXS860i9tJJ10mM9TNuCZVYcPRRTiSWe
 Q+YySmBtR9TA3OZfd6BA9EqusEgcwUJpxjZ8zjGzirj/OjcPtKwM9ZO6dadeMNaE
 wT32bJDUw//2ky2xflJCsjg+TSO7PxQi3g/YEWfau6Istg8PKfzHQan0EwCgxwrV
 6JijZQ85jIgQoceJjkwBLHsD+gKeeSUG7g2CO+NJf2d0tBj+l22QzmeAtlnuUskd
 nHKDAzzty80e4HXkUYw8IMueR7Fe2Tjx20OvVSkzMwiZYqevIJHVhiouCFZxYpSa
 JQHPYLpMXMVZ1X8d17tjbFRBXWmNrDcEhb4m3WoDKfQD/qbMCwBErsQ0t15dddnQ
 BVyqA/93dSzMYRC+Zm6Hzfk5Dz2MsvsxEE30ysSwFjIZ06RtYPKlN0x3ABCGba8f
 o5H0P6+gobJRLTQfK4xDS4J3G/d7TWO1bZGk9MPEzCJDexTt5yfKsY2jZRVRrikE
 fIbdSUgLnczBdUno5qC9IyMhGNa8O92GsjleDm7D+p+wkkoyCrQbS29vcCBNYXN0
 IDxrd21ARnJlZUJTRC5vcmc+iF4EExECAB4FAkFCGHYCGwMGCwkIBwMCAxUCAwMW
 AgECHgECF4AACgkQaHm3zflUJtqlWgCfWKIRLzsvZjBjuck31Ep8sEDP0GgAn17m
 X0hYq8W+2gbHbmYeqIFefHs9tCFLb29wIE1hc3QgPGt3bUByYWluYm93LXJ1bm5l
 ci5ubD6IXgQTEQIAHgUCQUK9MgIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRBo
 ebfN+VQm2sH2AKCnwIQ3C8+62/uQh05mqXqdzAaU8gCdEkRN+L9HY1OwFlSDi6Tc
 OAWLTPG5AQ0EQUIYdxAEAItGBQMO4f4rHYh9zc4fd62RhBfMHJpY1ex6HeiHt3pb
 i6KfBUai1zRYxgq9F+8qR9WgBLF1VhA4O0nCU9/FKOChc19W7xKa2auvE22Kq1ta
 xjCszahtPTDGIBs4K8u0fH/Gx4VSikQcfIGNd3IK4vALbLfH+iK/1RJNXPzQ9A4H
 AAMFA/4+UBNqZPucstZgmEwVB2H1Bt671fQqODpWj2eOMIYJWXKraUxdIjUqzm9K
 QhC7LBj9ihsn+LRsO49oWIAv5bks4zC0STACJ+Lx+FMb1i5ayAp/03DoZyrjRnGb
 SIY8Dtqonut2nic0NQ4XD5uqTkx2t7xlKJay/n4Nop2uqwajOYhJBBgRAgAJBQJB
 Qhh3AhsMAAoJEGh5t835VCbaOZEAn3wkQ7xISlGUox1/aiPU1CafRrZyAKCXgDLa
 wlCa23ftqh2DPxkAXtCnEA==
 =FIQv
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.225. Ed Maste <emaste@FreeBSD.org>

 pub   2048R/50A17BF4 2012-12-18
       Key fingerprint = 0C08 ECC9 3A0A 8500 AB95  B553 49C4 7851 50A1 7BF4
 uid                  Ed Maste <emaste@freebsd.org>
 sub   2048R/08FA5F72 2012-12-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFDQkJMBCADPPfZXZY16ONN40Z6afHF3hxGZsczwVUQ7qlNQzjfvUk5MJV7H
 VeKpLAN9pHLk9tg2xTXzcMbGe/baBQrw4kt23SwvQ1Q034nRcolio6rx4sq/E7EH
 vxRmwCgn4n/g1b/S8xzcXqFeDpdhY1RAbWdpQwscaj4hSCEAo2KrJ3tlsZqVRu35
 wKAW5eVlrPZghi3jTPQxzdz4QNqLFR5aQdp5MrxhKcm6rnC7JeyuLAFruWoHBoqg
 5P8dKjEMNPBzIJdWC2iEWqsiVOrJZ5YbCpZtbPlM82oGCUoC1QmW4kip3BJSBAJK
 wZlwRvHiMbjhjDGJaliHVx8G8NiJPrdDZlMdABEBAAG0HUVkIE1hc3RlIDxlbWFz
 dGVAZnJlZWJzZC5vcmc+iQE4BBMBAgAiBQJQ0JCTAhsDBgsJCAcDAgYVCAIJCgsE
 FgIDAQIeAQIXgAAKCRBJxHhRUKF79BotCADC09bvfZqcpiFH3HeQbH2SKeK6vNpI
 v1Uoib443EBajOKw19JkjOmPzwnFrKF1WSXrKYpp1iwUlvNgR1C+nMeGPOQCtLzU
 g49uuoC5q6FdMJIdYKjbVziga96UZme6kuSUUdv5/aumEuOfVvHewZQNWUdq1zbj
 RuBBesSKWULmUW4K7cBRGGvmAqIpWLL2lmZheT3WHzmLIwwqE4Xs8sgfijxxXrzz
 tAi7NVVEbOtDxlKZYINKXGXm4xfomuY4eAg+pCH58kEwgEudEspNQP+axJ0Bovh5
 yq7cVm7zHbmrxSWSzLjAfprs84m3XIoX9wzlit2tydUbQxlALqcqpDffuQENBFDQ
 kJMBCADODYSrW+MNgYsqOZpg7hQL+oWPak+DJW+mAe93D0T6iS7g7ZDX7XSSl+LE
 R/9bLa6alA7qXDJFf41yl9Gw7vP7k5SFAT0mukffR4wiXqsTKcdGj8LxV8JllAQT
 h3r38gNhZRDr4UQ1MZxWseeZx6myj8vskCiv4Rd0qEOlOE7AgiJdUdUoVLnjZkDE
 o+UbOhqSfSCWEQNItJ7dRGsmxGAUH4pIZcdu4NIYINt2yNIQCO/NTDFj80dpIWxt
 Q1BNqL45ZkWG0B3J1j4tsze7dGvWnXZfJQyvTeNeSg6WteyqQSQ98WgvFQkWceUv
 1ooA5bHG0xAtg2OI4L2ZvzLINfrRABEBAAGJAR8EGAECAAkFAlDQkJMCGwwACgkQ
 ScR4UVChe/RV3wf9F+TfpN7DC7m7+5aACXpDB86xCSGG4COtSyU8Gs0tgS84aE/b
 KUCdRZOwvz5dHAQUaPcgRNuNYscu2aAN4DYdPWrU59tn1s6+xYvWpgkzt+GGsni3
 gsz7vot3vUEzf7kOMV+NgdBEEIKgUT3TuIU5wQ/fevYGN1gdMeXiYSJ+PSfaZWnr
 Eee3zGU6TtR1WUgjQLoSdvDPzsFaNYSbCGYKXwSQOw7ysp1tY6Wai3teMb1Q9YNe
 BpQCsjEhGSuocr1R34+Nvmo6OcOpSeqEN3XRlz4PIGcXUY9Jp9gtGBSeFLasihfC
 SDQa/FThS6824wFQfaya638NZbjhCzrtxx4gdA==
 =aAkV
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.226. Cherry G. Mathew <cherry@FreeBSD.org>

 pub   2048R/2D066FE1 2007-05-22
       Key fingerprint = FBF1 89FF 81BB E1C7 6C1B  378D 3438 20E9 2D06 6FE1
 uid                  Cherry G. Mathew (FreeBSD email) <cherry@FreeBSD.org>
 uid                  "Cherry G. Mathew" (NetBSD email) <cherry@NetBSD.org>
 sub   2048R/7B2C4166 2007-05-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEZTf9YBCADFEcWIsNVwa8mnrwbdKa8s5ezy8hFROEA6mo1lxQ8V0qWvZ3Zw
 JlevoFIYOXvlghvxJPJYLZRr94gxknxxv0YJUYKZ3EWMA3ygCdQiEg6QDyfSM0rW
 usBwsJcGq53q/eWSUrcHz/dFZ+qNXVw1i+bkjFCdR/5Xh89WU3A4edsE+PptWET9
 R+M6pKoK3ntteo2/Gm7ar28QqmxBJvbGWWHLi1RhXzKwNaeDfUXlt4Q9dJ9HKxUO
 FlembFVIoxhttBi2n/gW3zZDBCFOvZ68JlS6SExhTRs5HzoTkMeLryASo+BSdaAy
 A5rst/AX5ZRAit3QC/0f1AtDFKqPVhcDoqtFABEBAAG0NSJDaGVycnkgRy4gTWF0
 aGV3IiAoTmV0QlNEIGVtYWlsKSA8Y2hlcnJ5QE5ldEJTRC5vcmc+iQE2BBMBAgAg
 BQJGU3/WAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQNDgg6S0Gb+FX8AgA
 mJusgMFurc4udGNQFbId6/rRNDyVxmaBudrxGGWlWcFpf3QTDJPAxOoneF8pTRik
 UG1+BHreatDmcHyuRgt8EQB6m9uU6A2zHEZebobJYVX2egeiwgnNa2J9TKY46RCW
 IV3CCyr9mKtSDCAuX6FNrEaJUnmmJbB3nRa+VqlngAX0LS2UGEzLYcEnujCMvx2b
 XsoK8wDfRPuCnpTfGFMB3+//yy4OSIN9iNJqaatLv27GXnziMu8EJqNXbmbCDNoI
 Z4yR9nkPC8JR9aFmCtgsyBRFy13l98pzSIVGpYVd0F1N0lDzN6raxbvreSDOcNj3
 9kLvr9s6Gr56F15q9WrLaIicBBABAgAGBQJGXfyZAAoJELOuUtxCgar5r2wEAIs6
 tNebLZ921O3dWr7WbU3GRHCrih5rP0WTA4kMQ+lw+O5vAe6HI/3AwoCXmR+g2R07
 SzF0YpE28ddzitpQoz8y+UCXKOI3frPEkbDu5xBtpZ3hT0nz3gp8Rp8SRBiUdZDn
 0xPX4TEZ5q83Ee7JUzO0cRx6YwYnJN3MEGij9HGUiEYEEBECAAYFAkaKsUYACgkQ
 iYEmcnvdc3fvJwCeK3tNzHwUdgU3Ytk7MCG8R/kpJAcAnRn4UnP/WPvNcLoK4CDs
 HZQBJJgdiQEcBBABAgAGBQJH91SBAAoJEL5Kg/C+npPiIxsIAKE/Mzi2qEGjsUQH
 x8ascoW9lUrV84VHD0/gMnSwH8vqTYhBV3iBKHu0jDQvrqIUbt5OgdEsZRNVeKCu
 fLRTTRQleJLuxtBjRoYNcAZuCB48o/b1J/13qESxHg6KtcdUNznrNYTBq/bYKDn+
 vOvbYr89weNis9Wo26REpCpdryLscA6dw6dOkgRZB9FHaAQDpWxVWmGwo/lPYPzW
 ipqIu1WVAYayqGS5bwUG+n1hLilzjX3parIxOATc5Vg1VGxigKGqggsnYhjekFgm
 UxOMeI3yGLCbinNxFfNu/AMdzn8i4dsf6BwpP4tfvz9eYBm9bRdloUpaaMZW7bLc
 8CcG9tWIRgQQEQIABgUCT1wwVQAKCRCruG7T2TeYtsGYAJ0UTJgeCzmzTypQ3BCi
 m5Lh2gDVlQCgo6NBMIvkCzOSh69bwiL+a4d5yQO0NUNoZXJyeSBHLiBNYXRoZXcg
 KEZyZWVCU0QgZW1haWwpIDxjaGVycnlARnJlZUJTRC5vcmc+iQE4BBMBAgAiBQJP
 bG7FAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRA0OCDpLQZv4WC+B/9f
 46B8mz08EcqrvuxP00eVwbNEAMrW0mj2DgOH5XGgyZKtHRrXMbFcsD5CHSQOZjjk
 BNATddsV8Ac4ufGKwC9kitGoNXzv9XQei1Hx/t1iNxSV9bPqt3RatJHx8A3rap1U
 urVTYld8CtauyDhGyCeJefas/O7cPiZ+ZVYFyPP7nlOrh3e4My2orUmQzZGRhLP1
 fbSnLXioZP0GnwxOoDUpCB9v9uNnsM8Tw97ki/rdaMJCePDp0715qNbhmhBTuhjj
 rqZe6y7uYnSW9CqTtN7c5OfkjAm+HZ1LC+GBc4F/moW8OwyfO+RwtpfqZpbAe8o5
 9pKYy7XfzL0jfkjHAfziuQENBEZTgEkBCADKg0wr+u01O99MaQJS51kaZBTncWdW
 fOkAU50DyndBgAQE1uIbuiR8L4t9m02/RxRqj9uFewQ3rGZ3iC3cVgFxyrzk4Odp
 EXCE8uF8WYtwUQ5yumdHqp6igFEf3sYE/pm1axM8b4LPcauRz10ZKweL3M+bh15c
 0guQyTn+lsKohODj031yMxj/uhjwZ3u/Lbv4is1Oe2K2jKrLGLqPKpS1r9XlmSli
 7Ly2T5g/aTXBbrt4a1GfSgS9Dzt8nFp8c4vFH1zprNVFb4FU3Kuzn5iW/DjhNxH8
 ovAt9HdfQw+4G/sUOCBwyEFXpxK66B+uKdFkMZiy00voeAi0naK8RHKXABEBAAGJ
 AR8EGAECAAkFAkZTgEkCGwwACgkQNDgg6S0Gb+HUaQf/QVmRj777D/nussHDTgjM
 /h3AA7KLExgT6uEHiEb/0uyi9lmFkxiQHVzXBkcOjdNVcvrm8Rmg7H0bSUU2rbMP
 PWMC+4roBVJnilcPdHQFFkFDO8HaC7Pi5R3X9Xe6aT+tu67bmRGhqCLtgG1StKPI
 qphIPAh9Qzk1q9FDkjDClbJA+lt3rzRDX4qLuSXaBQqxygqgNAEbUGbgsPnsOOQT
 wC+oXxhCyDd8WS6kSHqZzjMW0n+zN5n6Hsihld/GVnM73VoNbM+tOlgg6XMu39+4
 NcjdiFPMOhGWTYuyU5ZRRY/uCt7b1ULilfv4iBa2Ttd9yTRo/aBe5GSry1CNZy1K
 Rg==
 =lSy5
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.227. Makoto Matsushita <matusita@FreeBSD.org>

 pub   1024D/20544576 1999-04-18
       Key fingerprint = 71B6 13BF B262 2DD8 2B7C  6CD0 EB2D 4147 2054 4576
 uid                  Makoto Matsushita <matusita@matatabi.or.jp>
 uid                  Makoto Matsushita <matusita@FreeBSD.org>
 uid                  Makoto Matsushita <matusita@jp.FreeBSD.ORG>
 uid                  Makoto Matsushita <matusita@ist.osaka-u.ac.jp>
 sub   1024g/F1F3C94D 1999-04-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBDcZe6YRBACDOZSZ5cWE6IvNkx2Ht6S/VdIY1OXFU8n+cOVxNIHFWXPUOrFG
 F526VZoPfjURnslubdxXC8TKGspX96uc1jdROHvEwsxUUELyzZ7G5oJ5wd4jHwjq
 K5zwV5FZoNm1SHdeN0FqZB9rlJdOt0kxVZS+b1PUc0j1i4oDNZz7+8rc0wCgltLi
 c2i5RQzjuvJvF9P8OYGujHcD/3Tq02ov/aNX+jIoO58uuOBZpYFL7ZfbCeiMs+4A
 dmvjTI9MpfLBP711iu1asuikx6HLQts9UTVk36qP9ubNmFi54kDHsej7Ce8m+dOu
 Cjcjle6Be71MGLq4YUxd9xZmGGDPhEFnHWbB/QPP4n/m3DN3hblWBgP2PsgmqDyK
 518dA/0bhL5pvw5LSaRtGxxWvFBInfWGzC5EuLw4ERZW+bEFB0To08ZnocLRN/E6
 tZ2JTr2O5aMLqUEM3jgsIvs9EOGUBwPRzyOQXpc2uQemn7J0pL6PQfuBIaUI/NOu
 ULM0gQfLIV3wOP6Y5gH0FBcLt/ofrqdYys0C6zTq3LqDW5FdQbQoTWFrb3RvIE1h
 dHN1c2hpdGEgPG1hdHVzaXRhQEZyZWVCU0Qub3JnPohfBBMRAgAXBQI71CCFBQsH
 CgMEAxUDAgMWAgECF4AAEgkQ6y1BRyBURXYHZUdQRwABAc3PAJ0VtHlKCmR8IjdR
 KJxY0C5fdmaDGwCfecy3f/dYGQsljHhv0Wr2PxciscS0K01ha290byBNYXRzdXNo
 aXRhIDxtYXR1c2l0YUBtYXRhdGFiaS5vci5qcD6IYAQTEQIAGAMLCgMDFQMCAxYC
 AQIXgAUCQ5F4YAIZAQASB2VHUEcAAQEJEOstQUcgVEV23p8AoJKAqle5nC6Wi6yO
 TZtcr4axeBnAAJ9ABx4gqACagCDc/OMk3pmtb4sy1bQrTWFrb3RvIE1hdHN1c2hp
 dGEgPG1hdHVzaXRhQGpwLkZyZWVCU0QuT1JHPohdBBMRAgAVBQI3GX1RAwsKAwMV
 AwIDFgIBAheAABIJEOstQUcgVEV2B2VHUEcAAQE6EwCdEPG7N7vmhgYEqmZqPLm6
 oqjHOpIAnAr1FfVDPXpfE2SmXUZenG7+5MwntC5NYWtvdG8gTWF0c3VzaGl0YSA8
 bWF0dXNpdGFAaXN0Lm9zYWthLXUuYWMuanA+iGAEExECACAFAkORd40CGyMGCwkI
 BwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDrLUFHIFRFdraSAJ91gKAjNH0XzAKohpQV
 vo3uT7LNvwCeJSxDm0hpmaOpa+LCcabNP91SyhS5AQ0ENxl8HhAEAITl4uP+i5aY
 Wr7mPBLAaWfoQ4fyT3pUThtStiymqsrEDFKhVqA/KD3PUV1CeOBc9oq69x1+pUlk
 VYz3vDrvk0hP+dy6nerUEbkdGtMKLvGzakdond55jgSTZ6CPHxqyLva06QpY8tj9
 CODunFUE+MPVV4Lf9U4wMeEDZFEYvcajAAMFA/9kKoDY1ur1mAPJRWAcEONxnwiW
 qe7l++fg/294wra8IkAbF760iMnqq63qavsGT6xStMi9EwZC687p86sFex6KF+uv
 P04CTAyt+FAph7oa44AdWJo4tJ4SP8xIznOiZS8clWwxTaqv9Ncy6LZwbZf/P427
 egF1zuv5A/MTO3KD7YhOBBgRAgAGBQI3GXweABIJEOstQUcgVEV2B2VHUEcAAQEr
 7gCdHJTTs41XBpfprQCErm3tGXwRrG0An1zUSEtG1AA4jFXNgIlud0OO4aMm
 =aY+v
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.228. Martin Matuska <mm@FreeBSD.org>

 pub   1024D/4261B0D1 2007-02-05
       Key fingerprint = 17C4 3F32 B3DE 3ED7 E84E  5592 A76B 8B03 4261 B0D1
 uid                  Martin Matuska <martin@matuska.org>
 uid                  Martin Matuska <mm@FreeBSD.org>
 uid                  Martin Matuska <martin.matuska@wu-wien.ac.at>
 sub   2048g/3AC9A5A6 2007-02-05

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEXHDPMRBACme6PyRAt6LcfVO5LiPbtq6rYu4e8zrUjd7o+FiCEYjdF8VwXU
 3RQ76f1cx2tnNyvv7KEQX2/NyPHQH/3n3Cu5w8BToQrV6sEAMP59nWOIKSNTXNGN
 BAbFXvRDC1vlPXyXaeRt6InF90FmJ/ZJpTX1wYGenYymZtBSPd3q1iK6DwCgn/I2
 9FLTUjOm2qknqLGGZJ/w96cD/i6CDQa1VzwyplIKCbPDqNyJh3qW23JMkW3OGwRk
 nY8H4RrR3LNfCpiBuzw8JtO8vDT/NoUKG4rXFMYz0pPfPbWnJD+qtGEl3fXtNC3f
 a4YwTTDil5VSi846IjHK2rEwDvUkMAyiEbthOIf2U8JRn0KThPYb0alPyNuF+zaM
 HUUxA/wNYHb/qjqCI0iwSNxTYKeruBcua4yg7NKeeHtA0an95CfT+AyEW6inQ0Od
 WSrDljmZbq0YGFndRZnxlwClzA2ueS3+/F4ADvn0kONhzXfVewRayOHXLiXlcV2d
 4+g3oYMWVsR/DAi12ezzvkHnDWsSeeXPKkBXMAczmKd484RpbLQfTWFydGluIE1h
 dHVza2EgPG1tQEZyZWVCU0Qub3JnPohgBBMRAgAgBQJGEkt4AhsDBgsJCAcDAgQV
 AggDBBYCAwECHgECF4AACgkQp2uLA0JhsNH48wCfbHM5Tu8ABaGHO1Nlv0jtrc8L
 D4UAnjIzKUyR6A0ReHlqZyAQA7XQ0lxztCNNYXJ0aW4gTWF0dXNrYSA8bWFydGlu
 QG1hdHVza2Eub3JnPohiBBMRAgAjAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AF
 AkYSS5kCGQEACgkQp2uLA0JhsNH6FQCdH3LhF9TLVQbd5q5sYYR48zmXaPoAljRf
 JtDTR6ZLdjVowmZAmSlsFda0LU1hcnRpbiBNYXR1c2thIDxtYXJ0aW4ubWF0dXNr
 YUB3dS13aWVuLmFjLmF0PohgBBMRAgAgBQJGEkthAhsDBgsJCAcDAgQVAggDBBYC
 AwECHgECF4AACgkQp2uLA0JhsNHkiQCeMQACotd+npbhK1pJMKBcFOHrzUwAoJYn
 ZRIacsYvjMBNsx4UUkfYs70wuQINBEXHDQUQCADlHvWxPueR0sgha8L1Fwp4yTE6
 AbqAnkYw/nC/2q/oUDg97VFdZM0tOi67sLYHic3Fj/Il7w78jctdlpagW52b+R2J
 l3LFOYlbmbWkUj7iUFrDA0QZwO9IZw2yxDP3zkEMvPh9YtngmgI8CKRtXrxgY3+7
 9gEN/evBiEgS9rN5/tGI5V2Pt+VTXWfw25zRnOTTThgL/sRtqKykSJ6nsJfwO2DY
 0VFpb9ndFR/zG4ozJLupV+ku0EQv2xXlOdvhdWkLgXN+JRtrP1CxWzPTA6CP+m/X
 cYiT498yBauwk+JTGqeOKUfn27vpycGmf/VGwBoh2GrhzXRnOVBkDXb20ztzAAMF
 B/4/cFjtT3rdyJpFRoSl81Nvj8/DvP1ICovH2YUY+bIdUU83Id6AqKv5vOWhlhbR
 5Np9EtWkdyInXHhzs1MDm1xdNFmwkVFJB+M/XNmj5lgZ+e1riuoo07WcwKN8LdBY
 oOoSoKViSzEoJwlkQazOCAURSWHIlr7rYwM17oAgDjJ4PjBs4l3zjIt+wNU40wYy
 JOnBxjyK5ucKUAHq/6vgLmvj+QZvhcDLpKxRvw5M9PLeD1iomiY3qzNRlOF4aUr7
 GX8wbk+a9rsiC8dIGn++9D3BrvGvVLqxEruflXmpokyalalitIL3N3WitPjMu7gW
 EUotHnqcf3TGK7N7ffv0SXRpiEkEGBECAAkFAkXHDQUCGwwACgkQp2uLA0JhsNHl
 SgCgn7/wkepKhD2TrONJELS0/iy8WjcAnRhJSMsrJApfDOhu0ER1TqP+cFy5
 =HbmE
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.229. Sergey Matveychuk <sem@FreeBSD.org>

 pub   1024D/B71F605D 1999-10-13
       Key fingerprint = 4704 F374 DB28 BEC6 51C8  1322 4DC9 4BD8 B71F 605D
 uid                  Sergey Matveychuk <sem@FreeBSD.org>
 uid                  Sergey Matveychuk <sem@ciam.ru>
 uid                  Sergey Matveychuk <sem@core.inec.ru>
 sub   2048g/DEAF9D91 1999-10-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 4686 characters]
 /CYAn14opUDUCjxXXd3vrkwzNCIrYQ5i
 =iDu9
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.230. Tom McLaughlin <tmclaugh@FreeBSD.org>

 pub   1024D/E2F7B3D8 2005-05-24
       Key fingerprint = 7692 B222 8D23 CF94 1993  0138 E339 E225 E2F7 B3D8
 uid                  Tom McLaughlin (Personal email address) <tmclaugh@sdf.lonestar.org>
 uid                  Tom McLaughlin (Work email address) <tmclaughlin@meditech.com>
 uid                  Tom McLaughlin (FreeBSD email address) <tmclaugh@FreeBSD.org>
 sub   2048g/16838F62 2005-05-24

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEKSlvMRBACEIyrOE2NlPjwg7bS3nUC4S/D1nPV22eEJ0ga9+LNHlQnsJON3
 lGOU6iMGa6QaBoqg7Qw3aL6FaJlogNQfIPWZCRZdfJjlbw0Yd6EzCpMqoowB+4y6
 XuObOhie5bdHFK8NVk9n1BZGUELcnPGMdhPPIQ/UHq7Rlhbqh8qkcA0imwCgzNEV
 oPAY1SeozW0kBE6YUXXGQXkD+wRzl9As4+1CE3ZgxUWtoNqYvZMNWYTbO0ZWMx6i
 YWJ5GkLCMdVqNZ7iCteeDBVoRzLEbD/FyVzazPm7FBSxzK71EC+C4Ybt2IQPWfBK
 Q0GI+2ghQ/HyLh4gLCLP5XEk9aw9DwXGJt2q7HngEJli5o8LFVo3Qiu5X+QeC7QN
 r6uGA/9/raZnDF33jfAlx1jrHnFVEa1xzs81q2LK2ii+RdU5bvTJQchoHFRKZMBW
 HszbXB4f+wqkSkj6B7od8hBINJwdumQXdjO6nybh2abkCT2f/nyK7ktCcq027AD4
 BjWWFltUZpvspzq724SOEyBsbYJp4YTB2wys+gcyDF/ugaJCl7Q+VG9tIE1jTGF1
 Z2hsaW4gKFdvcmsgZW1haWwgYWRkcmVzcykgPHRtY2xhdWdobGluQG1lZGl0ZWNo
 LmNvbT6IYAQTEQIAIAUCQyJDcgIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJ
 EOM54iXi97PYq4MAoJeuQSfnGZsPBIpzOZ0vHmf/ZV4ZAJ4kKyQrqbxup6u/vMWG
 lS9JqYlZj4hGBBARAgAGBQJDnF0IAAoJEMYEPFZyB3E3kccAnRcxLZQIxgo0T22x
 GUDB8tkAUUOTAJ93N4aVydp/zrDo+OE1HStNFEsWvohGBBARAgAGBQJDnGKmAAoJ
 EHninGCwBj/nLhoAn3sa1+X0ccAhA+iPHo1mypN2uKUqAJ9B46J73q8E7PU17U6k
 RHY/7eCLaIkBIgQQAQIADAUCQ826swUDABJ1AAAKCRCXELibyletfK2IB/9GoKeE
 G2qDTfQbwG2Gbj4sW2FjaeNryneSTxXRMpK5dBwiMi07iM8Ze+8NdE9KlOzA9I1r
 tkYgR32UCfteyQXU8YvsKf6Q4wRqKbpckqI43zXMdvXyzG23P6/gR/Ozqh96Z9vA
 i6WdnvxjZaY6jItk357LJPQDP6zQncKFfcw7W+QAPx2N8BrUUy8U94kW6URhS01R
 d3NP8JylEXqqF6L7cSxcmO3A2QAVjzDpmfWu6AvREuYY7dkSSZWGK9hpoEjPN5GS
 LDgwRaiYZKHYz8Bx2UUA6sqaoebqAHY09bHIZ4fMiEkm7SSf5PsoS0emb9O0q5U1
 tHI8+6LkM6Zhs57CtENUb20gTWNMYXVnaGxpbiAoUGVyc29uYWwgZW1haWwgYWRk
 cmVzcykgPHRtY2xhdWdoQHNkZi5sb25lc3Rhci5vcmc+iGMEExECACMCGwMGCwkI
 BwMCBBUCCAMEFgIDAQIeAQIXgAUCQyJDgwIZAQAKCRDjOeIl4vez2IaCAJ98fPNG
 gmITFIYH+M3UBkw1YTvfAgCfQdAkDAFJxVrvDZBDliO2NB6jAu+IRgQQEQIABgUC
 Q5xdBgAKCRDGBDxWcgdxN2PzAJ9d7HmdkCyM5CN7cgG6BaZ87AHY5wCfUjblYg9y
 tsrTj2+ip8f05PC7zhCIRgQQEQIABgUCQ5xipAAKCRB54pxgsAY/5+exAJ94yol5
 HuRwmESdxzjj9S70GoYbsgCgxad9osFjtuxHHX37vaxUgJyLEbGJASIEEAECAAwF
 AkPNurMFAwASdQAACgkQlxC4m8pXrXxT7wf+Ji6vtaE5wjEI3/puKsHfGJmmHklL
 UBkcl5acntPLPxhXa2Z742ZZW+3QXeUyyXnqU1/BSn6/NBYO6I8yUJc5QptnlCvQ
 sJpwJlnTd7jBhSzN+L1xGxxvmmq2LfzLIleW8ye27vBOW4JDPDSgz4gVTKRqc0JV
 1EYULkWCGpfDA/xPP+4Lhizz57Q6EqLVurxMjNLE2mqV7feIvYoGLxOX0RxbNSpT
 +uJ+6ydpyE8UhykkQwgN0vhaokwSHC1KWWFH0ET38hcdFvaVrWZsrG/GwGg0T0mG
 23CvIdBUGH9U0roJjUa6CDDQz8ohR0P04lFpVsgDi9AVPEFWTX4gcUwyILQ9VG9t
 IE1jTGF1Z2hsaW4gKEZyZWVCU0QgZW1haWwgYWRkcmVzcykgPHRtY2xhdWdoQEZy
 ZWVCU0Qub3JnPohgBBMRAgAgBQJDIkMNAhsDBgsJCAcDAgQVAggDBBYCAwECHgEC
 F4AACgkQ4zniJeL3s9hsCQCgjLOKwwiG6bABO6ue0mjHpvR6nhUAnidSAywDgVQa
 nv8Ev+hIv4/QpD2PiEYEEBECAAYFAkOcXQgACgkQxgQ8VnIHcTcenACeNyN5PiZU
 TJ72eTxbc60q6PpkVOIAnRInAWvK8iW8I7uGOMBmyYtZWfu8iEYEEBECAAYFAkOc
 YqYACgkQeeKcYLAGP+czFwCgkAtsuKGoojwfo/Rg6p9RCazIUjYAoJ0xxWeuZ/df
 7lkbyqcRGJOfLeBBiQEiBBABAgAMBQJDzbqzBQMAEnUAAAoJEJcQuJvKV618rKkH
 /1kUl4Cqj3n9a+acjUnl5gH1r6SVUuNK6pPJPVpBXDOGWQQPfVYl2LTtFfzIh+e0
 q7J5os8timFbi/6HaI3RNV21XoqrDVgmRA8lApxM3dfB0hlJ6jx9eoUjHgi4n08w
 nX3g43I0zoRc3lQPHFc0jV9yRhgAln2yHmrvdcW0SUb8Zv/FvyG26W1gyEvl0cPE
 /AvKerTr2oP3aKnWtQfylovIw6Y+MmP3AynlvYghY7qw5QSnw3PhITvoFh4Lg4hI
 c/AoY69TAdf4d+kHtbo9vssMoT/NAIaAN3K8hdzSmJ0Ifsj7/K9+qtYz3r3c/+Qz
 1pH6hqz1u13upXLo/slPV7S5Ag0EQpKW9hAIANJJ8W4+BYSzM6ihW2ElYyt3h2hp
 WXptNPnrZDAoqx7YtCyPnUpn6dJrlsz2NTJiW7ahdsCQqrCyMTRCzAZAbFN1s8Se
 0hlREeHxGBIw+trapap/B2u0VQHDfVEL/9ib+jUFm+Gp3izgcgf4y3tvJRmmPCgj
 Y9fFcFu7PrntYsK91OkgungUriZ1fbjx0OkHRaz7nnq+On+dVElFh2iTwpZKrG3L
 7Qws/iVWamLOSQ14d3fzWN/Y7pF09QjOo5i/iyN1QEYiOffYaUthWr7lJ35muuaH
 yEMeodSNkKCF+BqpmmWKgJohopQ1/f36WjwlaVKaRh0zCIxcpX5xPtSoMzMAAwYH
 /2OiL+gBLaaTC5okydoeHAE+G5TobT4CI2fw2P9htDWVYf1eIriTRYKywSyjF+YS
 nCc8hleBDCwrUY03GXCFEOq0SAR97cfRhzxlHps3n3iAuZp9TwcGDiskL0wAaNS8
 43AKNHlKRNWxXoCE4oBlq/t1+DV+7BnjdI+MCAUe8h4y/jACIxpxnRKjmAcN2qDh
 THauJKvmUjw5W9SvgDU8sHNXRAdTbCrDj3iEAvZ2bTUMLmh9h0tKhwmVD14IMpDp
 7ZELqCgJgtHjv9kAg0Yz/Dy34jdLgypTJzUreQcJYvv5Krp1QLRTMMtoMtkop56+
 oKcUsj5bqschZLFzuL2hj3WISQQYEQIACQUCQpKW9gIbDAAKCRDjOeIl4vez2KQu
 AJ999gXGK70qxOzC8xOb3luxRKE/TwCgleUyV4VszS8i918p+td30+xsf1M=
 =DTOK
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.231. Jean Milanez Melo <jmelo@FreeBSD.org>

 pub   1024D/AA5114BF 2006-03-03
       Key fingerprint = 826D C2AA 6CF2 E29A EBE7  4776 D38A AB83 AA51 14BF
 uid                  Jean Milanez Melo <jmelo@FreeBSD.org>
 uid                  Jean Milanez Melo <jmelo@freebsdbrasil.com.br>
 sub   4096g/E9E1CBD9 2006-03-03

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEQItSoRBAC0Dd1LYWYUcjRH9XabIefY+5q+Mwi7iBdvUjq96c/LgGZLXbG8
 ZlK92kraOdWvwrPcYUCjYQwwesOmjXryXPoS+AYiz9iVs7AR/A9drFECh50wfaiL
 J7X4kSpR9zDgju/yVPyT3rhE4ZEZ/81txqdu5DSG5+vD8dLoXdb3EziXFwCg8Njt
 Lcb+ETI3MvK0M4A5HpuBvTEEAK2H7mNZ5BoLCrB81244e1BFwd16raITUv7DiF11
 Wl4kFowGt0K9P0d6QxmL3bEdeud2wfNaVjAuiO2B32XlV4xskZmfalniN6fsX9b9
 jnzJzpFvR4tPeZdpw07ePYJXh5vZjx4Mkflv9X2+rWafLiw5vkmwPnkQPcnhWnD+
 Ia0UA/40hZZvC9h20eH9hAcJA865wLxzmUijzgAGHjXVjhNT2oYGneNeY70auub7
 hGVL7GwsDSYc76W6IhJOcAjgHcCfa3uGerFR56T9se0ysmlBrONiYTokVZ3vKFp6
 m9ZceaPiE94RtHsVVkDa+F2KWeGU1As8gskVBP8MycodYb8XgLQuSmVhbiBNaWxh
 bmV6IE1lbG8gPGptZWxvQGZyZWVic2RicmFzaWwuY29tLmJyPohgBBMRAgAgBQJE
 CLUqAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQ04qrg6pRFL/NCgCgg1C8
 cFGpWahx1wgZ8IQxsmCSUV0An2YnP/Q4w10WTe6qp+I+H7c7k900tCVKZWFuIE1p
 bGFuZXogTWVsbyA8am1lbG9ARnJlZUJTRC5vcmc+iGAEExECACAFAkQxmpoCGwMG
 CwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDTiquDqlEUv6McAKDC5MusdUU0kl9T
 /ymavKEu9a349wCfXWEu9GgVb0CCZ8Agx3BHHIuZNo65BA0ERAi2QBAQAPB4mj53
 L9vbS2WLCAPMMn4ZGDYGXbe1pB/mjRbZlTGnUYWE3NO1fLYXEaoilRsvcEKtbsWp
 Ynuk8Ou4DaNoVyX9I6I18rs5KMZBiLOvQZFYCBbJYSIn/nNycOqsTy6Nw9mz7mrw
 I6e6EhiYh/AQ+MI3zID3iYnbQlQFZo4gLMFTLKklpiV+DaPoDiEkQPGn+0mmLEIO
 pmCqiDTxCIrig7feExCXJa2+CXLj2OS+r6su38O7WJiGMq0i9nCeu+4NnezoKPwt
 +s5kVYAjOSzDRybWz0UDzi9M7Kxu9tFoxEQUikLDMdqSklPfRs95TEmpXIvksn3A
 lub2Vfum6/kdRNkxPPbUuyEvtzeCc87LB2cLpP2+EXcfHCe7MdrtowWleRqXymXa
 Lyun7uKk2etFpEIfAqCPC1Yd8Jf2coyVY/n+a6yotWzCtQ4vogO2dTTKmj17kkcW
 1CXZz4W73Jut9ixZmYL/zOJj61j+2S7K7VLfSNrP8H8SACH0oHxYP89BaqOSOO2N
 0DtvyhFfS0OsxAEBa/EgtCAZiON4nZdQGPyDvq2/uQ1SGxbykTCvgxElAQfyUh7x
 lctdQQ6f6MEEPHapdDwpnqX5TAcdY7v9eE+/DZNTeswUBc03qtqxee1II3K3+Rvl
 4R+DuGn/oPdgksnX0kX0wtHgclXRsZ6x+wEfAAMFD/9S7Z0ee7WeH4WwU9Mf9gSp
 3JGafoInoJZNSRsKAl4VFC8axivUGyUzJdTbADoRXDR6NfqJE94u+pP3vx4AAvVH
 cvzfGj10GlUOwQGbQxaYGgYtqVgQ6MKeS6A3xaj63WgBFtx8bbt3e9XTnjPto2ZC
 U/pM3lmwsvxHoJGgisRvEfdQeWW2cJlxcBfpqat1/2MFBK60Wd0WAr0x6A3m5xpy
 ejftkcUa08BT4LSiGAsmuNKtUYULA9OrbvJreUa90lrM+6sZy2Edh/kulNmXgS4Q
 Y+OVptuhHSgBeME+j/fM5+p3Uyyaa45xmCFxnx5u/XBWhzMiPvi/m+qYkXPECFLx
 CiZ4OC7Xso79UeMmYq+CTDMWR6pe6iGVQZhRH69ShA+c545Eic/RoOv4ra8se7/U
 R5BU29AWWtapMq50/h321Oi+JmmfJHrte9Kd6RdyahuvtlWb7bgnKPwzpaRXYtbt
 H9SskRTdESK14AwH2eUVAP66Dfr5xBoyuS2g9MkRxxhjHWmMi4TAyh47VgXUxOPF
 Uh1eFsIqVa1scXFaimmicdnbg7N5iVoqIIiuc2Q5P1xIuTUdxw1SjXOInmjAszO7
 Ckad599/WaNFS/pkDOgt8yfQaLOKCqVuKkimWa8YuZkm0g/aY1n1cE7TvNpxdrS+
 dw6TU3idxbY/DuNsWfHfrYhJBBgRAgAJBQJECLZAAhsMAAoJENOKq4OqURS/QrYA
 oIelyoPYInm4v6UTBo3XhOwNkHWbAJ0XXqE5J3Zv8FCqjQsJTFCmmNSoGg==
 =CyrL
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.232. Kenneth D. Merry <ken@FreeBSD.org>

 pub  1024D/54C745B5 2000-05-15 Kenneth D. Merry <ken@FreeBSD.org>
      Key fingerprint = D25E EBC5 F17A 9E52 84B4  BF14 9248 F0DA 54C7 45B5
 uid                            Kenneth D. Merry <ken@kdm.org>
 sub  2048g/89D0F797 2000-05-15

 pub  1024R/2FA0A505 1995-10-30 Kenneth D. Merry <ken@plutotech.com>
      Key fingerprint = FD FA 85 85 95 C4 8E E8  98 1A CA 18 56 F0 00 1F

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQCNAzCUT6IAAAEEAL6dJExgqBvPOEKuRtkeb1b+bcUkMV+TtiT5GPXcYlYeYuDH
 Veh5BK+ib0sULahN2lGdgIWEwcnyGokELvc9ZwWyjgcopWRCoY+VkCzz4YIqtiHy
 T8VUw6bIidslytDjG6wAp2zDtAR75uOM0bLDMsoXQ1s6sP0HMRv1TA4voKUFAAUR
 tCRLZW5uZXRoIEQuIE1lcnJ5IDxrZW5AcGx1dG90ZWNoLmNvbT6JAJUDBRA5NLf9
 G/VMDi+gpQUBAf4sBAC21xtMkZsdR/FoHzg8fppFN623p/ALXJVBEA52W/FPfqVd
 4tAJeViU6UgtFBxvu1J7ctXM9O4r+xd040ZTtWVDZSRhssZN3hBGx31El66niUIU
 IfJBco0nkfUreuKw3MX6vrZkuNc/WGFaQo96JCsYTt7OSzZQu/vpa3gLH5kThJkB
 ogQ5H426EQQAxAaz+YSEAmOES6KLRJW0otN/whsuTPIbksydLGrRUpvGivG9Ohe6
 khLnXE0ApknWxb2aqvP5oRHfB2nx0ZPpm1hdrjMgD/574GT4gskyTdRKd9hdCUrc
 lcS0WohvsI8si7kKJawa5F0zy08pNOIFstL1YRdQBzfFYHl30aGAXFcAoOnEpqZ6
 ffE4E19IexMDmb1KA+s/A/0ctHXLB/5vlUjOpGB7bI3yHHgTT6r1C56WkXQ49SV9
 Ad2sN4nrvNKdNBJcN1oAvPh49WBWcSAwTTpub87rl5B8vQEoUHOBWQMUrGCU3/yD
 KopmHBvtROsP/3KGiCfrteWCdy6aonQLv4TXOeqYMstbU0MjNBVgmAItoxqz1237
 CgQAlO/5jMCLdxricI+1f7Gd0zwbxHe1JUV7kjLqMx1JZ75LlxuIiQbJgMpWVNXu
 j0O8df5mbhh1+G4K9O/p+Cg19+r5ghc8Ms0YOEkYRlKp0be8uzrCu7qItGfLKMsP
 t1eU2RJ5YPkD0bOjcVxlFQmXkQ791jncpOdrz2O1qgMLpr+0Hktlbm5ldGggRC4g
 TWVycnkgPGtlbkBrZG0ub3JnPohWBBMRAgAWBQI5H426BAsKBAMDFQMCAxYCAQIX
 gAAKCRCSSPDaVMdFtRS5AJ49YIU1IAJl2cs1g5gDgXPoY/RdsACffJZMBGaXpcfm
 ZpRRIAtzq+Vv5Yi0Iktlbm5ldGggRC4gTWVycnkgPGtlbkBGcmVlQlNELm9yZz6I
 VwQTEQIAFwUCPE+i4AULBwoDBAMVAwIDFgIBAheAAAoJEJJI8NpUx0W1RBgAn01T
 zuWhCWOShHSfKM+sXcD1YrwPAJ4jr1tE0c1rZ1Lnz5YYZefpSnt2mLkCDQQ5H451
 EAgA0k1+aZvnxXw7WBcuEcT8VRBUfdYSrXVEi8R7xjKrw06U92cDSkqdA16rImto
 u0SSTFTnUXXHLdAuf2nsHplrzjEAgrMUWTtRTtaPKrtCwWE9Tk6lSxOO3+HA3mGn
 I3Hl1KgTErIbqIAIhftJXpW63Xt1CZtJ5fOKCyNAL4obe+gkmsyNTPwYw1iEVG1N
 exIdkm4Rr8TWohJ/b0ql3rEv9y/nKRj23OYGDGKKGY03svz5Q/TB1CdQdlfXhtEN
 Uz674NimuiP0NyBp0Un+hPnr9IuoEILuQhAYOnji3G1OVEQCBFONGT6CLugoPrgQ
 0/KeCgIxB59TVkLm41yukcukzwAEDQf9EpA2dTA4k5rr451jRPbR1a19knOAz7Z9
 J0tWWbySXGw1ZMLMf7BA7bnnIqDeuKLkxIwc4UGQqiXmmKbbdy0pYPQSC6dxIsFE
 8vnL7RLZKhTLi6bFPj6Wspik0H1GnmvRwlaJ+Fn8g7pG6Pi1B497dTmZU3TX8s11
 XT09jftPjHLeziCBXu4OE/a0Gqc59r0A0bG94RbaW1rVmnX9KuvMpv9Wfx1AN2eB
 jrfpDPoMd8JU5Fn8KATvLlXPkSqQ+iQxOvYs6iXhoDrugPuo5bEF6sJBc/iC7ZmR
 kuy9zUh6K1uAYJoZferxiaglJH+pyrkBBDLjj3Akw5pSmJesekGwsohGBBgRAgAG
 BQI5H451AAoJEJJI8NpUx0W1UJMAoIrd17bhiZx3eYtAgi+1IwaTx8QeAJ4plmqJ
 sGDiYyJDVnPYxZcEN0h06w==
 =CRmh
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.233. Dirk Meyer <dinoex@FreeBSD.org>

 pub  1024R/331CDA5D 1995-06-04 Dirk Meyer <dinoex@FreeBSD.org>
      Key fingerprint = 44 16 EC 0A D3 3A 4F 28  8A 8A 47 93 F1 CF 2F 12
 uid                            Dirk Meyer <dirk.meyer@dinoex.sub.org>
 uid                            Dirk Meyer <dirk.meyer@guug.de>

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 6336 characters]
 =b0g6
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.234. Yoshiro Sanpei MIHIRA <sanpei@FreeBSD.org>

 pub  1024R/391C5D69 1996-11-21 sanpei@SEAPLE.ICC.NE.JP
      Key fingerprint = EC 04 30 24 B0 6C 1E 63  5F 5D 25 59 3E 83 64 51
 uid                            MIHIRA Yoshiro <sanpei@sanpei.org>
 uid                            Yoshiro MIHIRA <sanpei@FreeBSD.org>
 uid                            MIHIRA Yoshiro <sanpei@yy.cs.keio.ac.jp>
 uid                            MIHIRA Yoshiro <sanpei@cc.keio.ac.jp>
 uid                            MIHIRA Yoshiro <sanpei@educ.cc.keio.ac.jp>
 uid                            MIHIRA Yoshiro <sanpei@st.keio.ac.jp>

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQCNAzKTzO0AAAEEAMVsAcUX89qHkwlI03RlAYBqQa00TFmgPwZs8sWvNUqTGtlK
 kOXcN9WNBvwzMYtEk/u5C1HukqISnFkDW7ZKYm+Um1sQPioFHTwDC6R2HRDZBCV7
 0fROlQpb479iBlr8wNAYDhOs0rl25FpE/uAXYThW9Ik/apgXN4rTGxk5HF1pAAUR
 tCJNSUhJUkEgWW9zaGlybyA8c2FucGVpQHNhbnBlaS5vcmc+iQCVAwUQNu4ch4rT
 Gxk5HF1pAQHYiQP+IoxOpfpSPg8Gr7MUtoU3WZPY/5IuKoOwnFNFcSyuhrgn/OOB
 pbxkYjTO3MLh7Xa+9sPigevHy/sNA4vVZdjk05sjRfAZxIWPrinRy/kzva0KOY69
 u1QfX+Vx2mfq/EfMJMHP/Am0H71nOfAZsscKlb/jmuo1TxIpCUx+wWmNn5+0I1lv
 c2hpcm8gTUlISVJBIDxzYW5wZWlARnJlZUJTRC5vcmc+iQCVAwUQOY7IlorTGxk5
 HF1pAQGQBgP+MXSjPfcnNhNfUmeLu8sM63DnrFIfRP9E+n/yhZT0wO51r2LmF4ZX
 YI04IJCywJiPjEpCFXNAhqDfypkTXWcbLTxX6gE5GNqii5iq+z+UuO4panpJO5OY
 4H0/90cH6I/zl93EZN9wfZJghn66vgL4tDTgILdRPekIOB23JQIXsf60KE1JSElS
 QSBZb3NoaXJvIDxzYW5wZWlAeXkuY3Mua2Vpby5hYy5qcD6JAJUDBRAyk8ztitMb
 GTkcXWkBAf3zA/9sDB0n/UlsH9hzaw4r2k0FT9F7Ixtk2i/vqmHDUUcrlEqGaeko
 /3Q+et2KzepX981mI7N2jdClqJgjlHapGoIQWZL3Jy7ocgCXDTYwGU2cFRF7kzkz
 h3FyYotm6bMi5F53GamkVbYZfogLo1MW7jmqIydJNdT1oseDbrwkjvXwdLQlTUlI
 SVJBIFlvc2hpcm8gPHNhbnBlaUBjYy5rZWlvLmFjLmpwPokAlQMFEDKUUFiK0xsZ
 ORxdaQEBjuIEALtVC6fjyDiRnZ3ReckdTO7k83VUTZiQH+2cMFNd8gi+O2sZ3YnW
 6veQI45VB3oHD9kzMjol3B1ld7iKcQzHC6qUEviW+mTRRN2Y26DB704FNeUrqm1A
 LO8NPL6iNKFvUNsu3T0ZRY7oX9a9nMmcD7M2bm6jxrhckS8hY7x1D0xftCpNSUhJ
 UkEgWW9zaGlybyA8c2FucGVpQGVkdWMuY2Mua2Vpby5hYy5qcD6JAJUDBRAylFA5
 itMbGTkcXWkBARgCA/0RBudh/8z/HWdX0GC0m3I0zIAOiGfmnJMPkzLryXuOQsbE
 dg28b193QnwTz6/ASF6PLJkivcd1vREXCz3C+jHz6OGs5jUKcSf5c0ZaIE4T21Hq
 LPKHSj0cYxgiC0auwY46m/yfO8I0bdiM6Ki3fSBTlTmDlNhWxOQ4Ic2RamKNNrQl
 TUlISVJBIFlvc2hpcm8gPHNhbnBlaUBzdC5rZWlvLmFjLmpwPokAlQMFEDKUTtSK
 0xsZORxdaQEBjWYD/i3EOU8lEoje9jTBHfQaps9BQgviFSaHk0G41emKszLSLnGQ
 BeMGZTyWda6sTSqeLKg56HEmmVGzC/nHlhwspC6bdYaBmOpnSmmzxVstcYq8oiXI
 mlfFEcL5DJEau1VTBP56Fk4GCffaibCTRGYrQcJz4yLfATjYsni5Y8zXqhWItBdz
 YW5wZWlAU0VBUExFLklDQy5ORS5KUIkAlQMFEDrvMx2K0xsZORxdaQEBTgAD/jO7
 tb78V3muNw+rfD8tA+yWXw8IdC4QHCa+Ga6Uwf9nw0WD+fuuz0I2La4iaC3FPtTs
 1hz1QlmrztffL3tfsePDeN59nz89m+WPW/Cu+mLY2Eim2Hm6AWKVvtxtndunOSls
 xQLr0uhvNN5BOzEqv2V+l0MrwadPxUrHG0izqmGJ
 =cmvD
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.235. Robert Millan <rmh@FreeBSD.org>

 pub   4096R/DEA2C38E 2009-08-14
       Key fingerprint = A537 F029 AAAE 0E9C 39A7  C22C BB9D 98D9 DEA2 C38E
 uid                  Robert Millan <rmh@debian.org>
 uid                  Robert Millan <rmh@freebsd.org>
 uid                  Robert Millan <rmh@gnu.org>
 sub   4096R/65A0A9CE 2009-08-14
 sub   4096R/41F37946 2009-08-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.4.10 (GNU/kFreeBSD)

[encoded data, 6864 characters]
 7fVqteO/XfSiMTZTJrYaUBysbAgWKKhKKWcL8cQT5w==
 =WNe8
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.236. Stephen Montgomery-Smith <stephen@FreeBSD.org>

 pub   2048R/9A92D807 2011-06-14
       Key fingerprint = 2B61 D82E 168E F08B 6E08  712E 2DF1 2BD1 9A92 D807
 uid                  Stephen Montgomery-Smith <stephen@freebsd.org>
 sub   2048R/A4BA6560 2011-06-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE32uWIBCADUDbhOVgIwECdOVmR/GT/P3L2S9r/E079PRooPFPxLoqAxC+Me
 DoxyYoAR0RFWBs3Qcrf6bilhuovPdZOJ9+BgkGNp/Nu6QayC+4m2IvEZqFhV4Lqn
 5Dk+qmHGbCaM4K8L+vebdzDf6CAdIWo/ufaxBW2OzsuTi43QjYTH1/bs4NhpJRc1
 vLgXEgxE9JJ1TJVm+B0Oa7tnsr6VUZg5BszByFtSnnt0sV0pFaQ33/WSU6XdYUZ+
 RT1nhxfJ/p5NiP6e9h+IqnGf9yz/DtXiW9sqs4bYHs3qjZUB6HhECsSZMyaei1eh
 lvzQR23irMXHYHLI0aJUuNoC3f0qDLjzqJTdABEBAAG0LlN0ZXBoZW4gTW9udGdv
 bWVyeS1TbWl0aCA8c3RlcGhlbkBmcmVlYnNkLm9yZz6JATgEEwECACIFAk32uWIC
 GwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEC3xK9GaktgH4DcH/3NBVtRd
 HMfrieIAMyUYkjw0ddcAsBqakaDPDkNauv2+pAUDNhvJ4XUBPUxRm2OyLatHnHPe
 CPPTibNyb3OYgrbccBI1aMQPnKn5s03X0+5Y2Y/5qYzls6bA97MlJWNaWDl9rI7J
 hV7T6YPxzwkva7R8VRHdMoOY8qsErfA168Iy0pm3m28KBU+dnOHxcdA7GHqkggVm
 T+KpkuRnTv3Z1wrna4ejkbl+VEF2VXh6e1AOENSel7ujgWg3j2ZfOwy4wzBGxe4m
 h7GO/7AxvMfBqP10KXBOc6Vp6bw54O4n8CTX+CjGKP2ZvrwntOwvLThj4o1y2lyZ
 ojqcoYjGwIxx72e5AQ0ETfa5YgEIAJgDBvxMoNpKwuKJIbi85a97J8dHGr16XADU
 3xBQe87nNAgOKj4/LYaO93syaFHoiP4KgU+A3l93tKXrd9vOpyBASID1VJehDPp0
 3wHpQHGdVuleaobWJjSGJqCxT+fIa9s0vZgX4uGqa++neFKYTKsYC0T4ZglWsVfQ
 /ZFYLZekCjmW+GUR1k8pfR+n8YN1Tnc1kBN/iytQ7BZg01HA3376KyoKbQDR3XgO
 /fQPySu0JUJ67xNyxz0HsxPEvn3q4+34+SwNjh8pf/7dS9iyfr72juo/MqxU3sSa
 xz18l0RsvZk2YBpewnN7AFQf7fIXObFzr8RXpOGE7OVI6tAMvEEAEQEAAYkBHwQY
 AQIACQUCTfa5YgIbDAAKCRAt8SvRmpLYB7krB/48W8EaOYk8dWPMw4QF55ozMFD0
 H4ooqQdRV+83ddWg3BNjX8w3aX6kxG4JZkrIesrl+ZLh6HCtinGehociZXNhxYMI
 P7FwGl+Q2i8YcMqHih3/7/Hfh9d7C7F9JWB2Y048tfs2jXwpnGY1NRngrnWE8mJ0
 XWQ+5Fk51xR+0qdb62ly0PVv3zigypBLmkOFK6knmrZo2E1s+rAGyadcDZSrHodU
 tgvV8afN+V95Qp5vH2WGlK7wBPyteqXLrIO5JL+cTcKuZBAbpmUrxmHlUE3t2QTm
 BuJg0zCxtNGxMlx3WeX9LtWqsGx4VFOpfTwF+DC8w976faOY4QcGgD5WcV0y
 =DJbN
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.237. Marcel Moolenaar <marcel@FreeBSD.org>

 pub  1024D/61EE89F6 2002-02-09 Marcel Moolenaar <marcel@xcllnt.net>
      Key fingerprint = 68BB E2B7 49AA FF69 CA3A  DF71 A605 A52D 61EE 89F6
 sub  1024g/6EAAB456 2002-02-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDxk42sRBACyzSSCLYA90zaZoMlg4zhMXhciG/YuiBZ005q0s9W9cuFFxwOM
 0mLFbBHQKj5TG5TNswnf9VreRg8lRPCzgQ63atc10RU2tfa88hIjWZ4G4WEFDeXS
 hlj4dIA6KO93UEoJmIyR7hswisb086mK4dM9hq9FxJT7YQ63PkUYmd+pfwCgjX/y
 xM6+aPj0sXuOvAcVVmrnp8UD/2pEd8kxAKIaWmxOm9aGB0/E6vjZWxCk1+CO7tgG
 4gInFYUnqniPB4JOXOWriwBGPx5IqWYwYpgeuoi/KeE/Wn7bRUEeCbBGEmJkHO9l
 3xJuPX8JKDkGuTNDvR3SINKSzx7gb77eGorwxV7e4FXBeXOyXLxgDqDhh7Sjv5/4
 ikr2A/99b5t1akHlNe1ITpuEETDNRcfu38/KW/nF3p1IKQ4Q+exSlEJzPFupYNoZ
 O7uD3A0YCNf3jIY52ufkZXqhqfsp6aRLetbqDcKVrZWSudAzGAEk3Q85a6Ei4mUB
 tfv4dmXQOLzfAFHezhCQIt5LIPJ5Dmz/a26+u0DmlfisgP5ltbQkTWFyY2VsIE1v
 b2xlbmFhciA8bWFyY2VsQHhjbGxudC5uZXQ+iFcEExECABcFAjxk42sFCwcKAwQD
 FQMCAxYCAQIXgAAKCRCmBaUtYe6J9pN3AJ982m/rtLgyiuHl1IM+/xfsZ460SACb
 BM7V955SU4T2b+1FW1ieOuuZEKC5AQ0EPGTjbBAEAKbxUKuiOJsAQnGKTXtbyRdR
 Y6BZQK9tPNXEIjIUZ94Crs9lVq/P3kyvpR/ziL+Yt3agUAELiX+cggUZ5KRzKBmo
 PJ6ZdWOuKLRN2+PfK1QVOQayeZV11XZAsPwyHI2v/hvjJnFvQNTEXWLZsBNnfTdx
 0zi5RBNhf5Gt1hyuT4cvAAMFA/9xKQ7aKkvi+C7KafwH6B5X6lIQxRbTQuaZaqKL
 M8pDmVLqo3er7S1ullwMWfarQLHtlwirX9IOQN833TCDev9QeeYZZ5g2MpWO5nx4
 kxEOAK6Lg+QBg4RcoLK9CpHUpLoChGQzNaDudztUixwVaaigj21O4PXFr9pmLLZk
 vj7AN4hGBBgRAgAGBQI8ZONsAAoJEKYFpS1h7on2XgAAnj0B9B7g4XPMXjizKVNP
 YLC2BYjgAJ4tZI/tGYxHex5RCeFv/fG4wN593g==
 =R/4a
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.238. Kris Moore <kmoore@FreeBSD.org>

 pub   1024D/6294612C 2009-05-26
       Key fingerprint = 8B70 9876 346F 1F97 5687  6950 4C92 D789 6294 612C
 uid                  Kris Moore <kmoore@freebsd.org>
 sub   2048g/A7FFE8FB 2009-05-26

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEob9xURBACHaqCbAqwyIXO0HHHCAVYPqVkhhr2FIS+yTvVJnCQa6G1KIasT
 LKGK0Z/Ae+suMsQoT9e1Pw/zhErm++aRSYqdTzyuMUjEDXtgsfp27rdQZRNiWDwz
 2/gd1nSEWYAKqUh5i0iJ89tkiL3JJx7/FD1+Nfp2sk318usUshT9/T+L6wCgmRvG
 A61Yo0rszOQexAwZ6PqE9fUD/3tGobQB17xQIca/AwUDyR2cw1lGs3S2ZN2G5xAT
 QL+h30wplhrrIO3lkyZQ7p71ZTPiAf5b5eTrXWrXVtO2Um3+wU04yhBVcmO9DeO/
 F6SLVzJLCRyTSNUSZNmWrl1EOFWooNnfBI4Emjke46g89hIbhYlS+qRL+qN0ugpR
 SnfmA/9d/UiazKlhp3fX9EwYRQmOC4WXDxuWS91I7kH0xsbHR/BHFJbUHDr0shsB
 lNRmfxwaZjiC6oHsJE0Du6FcSncYSfAChLrt+fqGvNgXf4hDIjsUtu2d5sxgoarv
 EvaSwfh/gelNuTnsgQll26LaeYjgmJgwf4Hb7I62UkkPuU5LMrQfS3JpcyBNb29y
 ZSA8a21vb3JlQGZyZWVic2Qub3JnPohgBBMRAgAgBQJKG/cVAhsDBgsJCAcDAgQV
 AggDBBYCAwECHgECF4AACgkQTJLXiWKUYSypOQCcCQagomGK/P/P4OedoFUDw5ZY
 2qIAnjRRTC0mRqUbIjaf/FWNuU2qtbiMuQINBEob9xUQCAD/zeiP1+Ru7ffCZwZo
 QTPjuYvm/PnAeeL2fBqN/Q367UuqR6RlqV03lo5nFxD1phheP0BmH6b0qyMh2dxi
 /6nq32g9b0Wb8s93pqYimxtujpNnWmZhwparaUm9tPyIGRdJ6wj8G43gOwyjDdwi
 GBPDAdSAqVZI0m+l59F5lsPiYJDGSkYENjLd6T7aAd0JzDjd0YLTx1+WLir6OrLG
 p1j81rBRCGRNipN7tGB0/pEB/mutU8GlDTTFaD1cWT4X3RGGP9MOH1UuS4wZXzJX
 8duq+4fKlpKEPOyJ9R51D25a9V71Dybdx/5mo+Bsec8T5+N0f4hK6utrnJvSQTes
 vinLAAMGB/wNS78TRKqFdjz83F/LB42srwFqDCKz03Pns6Fzespha8zWKOTiNOk7
 2WuXl6qWXhZ1aSithGzoWX3Xm6m0m3ZYk9wE+rDqT7Z3/T0tKiHmwG5z3QpuLOnp
 LGuBH/ra2gbyC+Ycj/faYXOz6Chf0e67bNRru9OGf289Q/EVcm39DinYBK1jrHcq
 xZ+b8jxtOWygo2D0SIS/hl4ljMDMaj/J8itwJXj0OyuoJ1IZkW32L4RN3jIXTUgn
 pGyhtw3wO4V5nhdj+YgvhP2VW1K2SVW1SqExlYdvB+HigKV5oHzTNluILcJgs4BY
 ntHqlJQ57QKxWImxvFZmS9MBaf69Tb68iEkEGBECAAkFAkob9xUCGwwACgkQTJLX
 iWKUYSziLQCeOWM0aLs+/NIGsNo/Lc2N4YTQ4pUAn0rL6J3fe3flPx5pBoj/SSto
 jjB9
 =yaw0
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.239. Dmitry Morozovsky <marck@FreeBSD.org>

 pub   1024D/6B691B03 2001-07-20
       Key fingerprint = 39AC E336 F03D C0F8 5305  B725 85D4 5045 6B69 1B03
 uid                  Dmitry Morozovsky <marck@rinet.ru>
 uid                  Dmitry Morozovsky <marck@FreeBSD.org>
 sub   2048g/44D656F8 2001-07-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 20786 characters]
 =iYsU
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.240. Alexander Motin <mav@FreeBSD.org>

 pub   1024D/0577BACA 2007-04-20 [expires: 2012-04-18]
       Key fingerprint = 0E84 B263 E97D 3E48 161B  98A2 D240 A09E 0577 BACA
 uid                  Alexander Motin <mav@freebsd.org>
 uid                  Alexander Motin <mav@mavhome.dp.ua>
 uid                  Alexander Motin <mav@alkar.net>
 sub   2048g/4D59D1C2 2007-04-20 [expires: 2012-04-18]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEYouBIRBACKCnll/QyL7oh1g8bNwX4mX4QDz26jOjGW624VOCOb0jarxzV/
 s8NF5V7ddCLMbf8wqA2QqeyrNm+e0FdsLbxVAN6NtF6hRCK0Uwc438toERXBLq5j
 Ss6Ofc3n9KBdTbUDfTp3t9Tda1oajF7JqembMz6cIWXmcU5P+7a5b48KCwCg6dhG
 X2f8H0s3WZkFi4gDXkUOMMUD/AxfkpYNv3CMGZx/6XVAlNltOoNRG2j41tn1Bhkz
 3xgPueod38HbXewTESMVm1qPW3IdNLCrVXg8/TxeUw97h8d1Xa3wfX2DEDfUSCWp
 IyH+gAchvZxJebdf8UpGtXMrJPzVznMHmChs8pavhnZfqtJ2tplFEf18HLbvzU8r
 0GpGA/4hNHGvKtts3CTV7XoQlQrWqhl9okjAUarLjrf2iCVsUhyE3UpXmp0il5bq
 mhfVv5b4FHUkrSipOsJmVSLgoc0muL9G0BNvLkMi3/vUi/6TOjANYOCnUF324cKv
 9o7ojNylp6eTh79wx80tHt99ZgNh1butSlQAQSTXk0aLLbOSqrQjQWxleGFuZGVy
 IE1vdGluIDxtYXZAbWF2aG9tZS5kcC51YT6IZgQTEQIAJgUCRii9JQIbIwUJCWYB
 gAYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJENJAoJ4Fd7rKBAsAnR3+WbuhVRDu
 7AVndqKop+Qwg68hAJ9W8/4LOHr2XjLT37RQyxPgtodbvrQfQWxleGFuZGVyIE1v
 dGluIDxtYXZAYWxrYXIubmV0PohmBBMRAgAmBQJGKL0GAhsjBQkJZgGABgsJCAcD
 AgQVAggDBBYCAwECHgECF4AACgkQ0kCgngV3uspZMgCfafiI8rCSzlLwyWRXCpyH
 smEYsgcAoMuqcyGJ9P1yzcddYw9SZUjkoj1dtCFBbGV4YW5kZXIgTW90aW4gPG1h
 dkBmcmVlYnNkLm9yZz6IaQQTEQIAKQIbIwUJCWYBgAYLCQgHAwIEFQIIAwQWAgMB
 Ah4BAheABQJGKL0sAhkBAAoJENJAoJ4Fd7rKJFoAoNe3pxIgHjKb+mjocFUrzkAn
 O5pkAKClil44JNQKWePpy+xNRNG8ko5487kCDQRGKLgSEAgA8Y2EXU8EbnSyZ5AL
 RyHn7axmxr7p2qzEkDI8EidMlJOxfyCj7b3t+5QbIbieb/pnDMGuXPc+7lcK7Owf
 pu9DTvWPdLRjvXNFJbuRH5mXVUdHS3j7GnAqqgb8ydTbUrKRwY2BijJaU8imXibc
 +ujXgO/ZVrvYpiXtZx38cwfoIDA+LFpQlLBUUkV7GRpBYcrkrVEGMrLBAPht+l71
 Y/IBMht4z5VBFMxJ13TogMseOKKDrRVsxmMqbBjr/S23pVZqpjQYGwkNo96+JxeD
 pQGlbbbRftiuObXEZsk4yGp56jXTieZLUlq9L1ELkzHIjPhNoeudx/tdtgZPSwsp
 I6M7SwADBQgA2eUilFtIbEsAizp1Jd88J+2Z/dZ3M0LK7rqZuBVQdeJZbpYBfL9v
 +JEbjw1e8HV2goYtwkVgfP3tJX/xqzmwIZxd3wLLzDucPrtmQJfDDcD3fDBVvCeZ
 Z+EjaGp8/rIE/h0LCk9XXHjK+JOZaKt8tsCtkpp5nbAMaPRBrCm9sGB9Oyt0rrU2
 /ryvMIf4W602iKDka5oUl1fhNP7R2lnkLRK8OPEPdboVxOrzzdBB8XN67B3kzDRt
 +nBHqFZNn6GafIYpvoJS1jqAskug2IjmEUIxDxEuD2EhIiayLAuwmGnR8d3iPVcJ
 /KF/URy/Y7PBtkE2amogd725uRTxXOXAA4hPBBgRAgAPBQJGKLgSAhsMBQkJZgGA
 AAoJENJAoJ4Fd7rKMlYAoNZbw8I7WBascnxVyObkqE5rLKxJAJ46TGlVlvBS+PXT
 L4EaOMcBYbTvTg==
 =ZML6
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.241. Felippe de Meirelles Motta <lippe@FreeBSD.org>

 pub   1024D/F2CF7DAE 2008-09-02 [expires: 2010-09-02]
       Key fingerprint = 0532 A900 286D DAFD 099D  394D 231B AF20 F2CF 7DAE
 uid                  Felippe de Meirelles Motta (FreeBSD Ports Committer) <lippe@FreeBSD.org>
 sub   2048g/38E8EEF3 2008-09-02 [expires: 2010-09-02]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEi8sBIRBADJt1SLW/mX5HmXKgbG72GXupRR8V+lDbtquXx6dJ+3E62S9xFx
 KehNrX8YcYnp+dcuHktXxQPJ/BAzOnvPdHKgzdXMARO5ApOfQ2VDgZgAcs0dVEnn
 LILvxiwQ7YlyJjOTJwbcHBpsTdolhNooi2FEE3N5ShSMRlPoH3GXF1qdnwCgqV/g
 IlQTCLudKrApFqNIbDCrPh8D/AmN2MdnlnIk6d7zUgLWuu3coohYIYOxaZ+ovKDb
 S8siSZ5uaEZOhWHVLVGYXTmzLrCK7TUBKdK1sW7YrYKQdPjhYnYXrwS4AaWupWwX
 K+fZWTaZsJiGLbOIrszAd2hRHUgQ5VeeoM0eD9eyAWHp5SVi9YcixMUNbn5ERPu4
 ppK2A/sHynDjmkXHXzuNwN8dwcUjTMTVt9bxGrLVJHcJUsK527dv6/UG1CfZYnzT
 nca4GNO42/FBjQtyJaTQd76aJQ/PSU88MMGuMUh9LYl9rRdMQKn4FXm/6t7NZOqx
 qvXzEC8jFw1BOvxhmykSEZDlwZFwQngDre9Ux68Eu6Nut554yrRIRmVsaXBwZSBk
 ZSBNZWlyZWxsZXMgTW90dGEgKEZyZWVCU0QgUG9ydHMgQ29tbWl0dGVyKSA8bGlw
 cGVARnJlZUJTRC5vcmc+iGYEExECACYFAki8sBICGwMFCQPCZwAGCwkIBwMCBBUC
 CAMEFgIDAQIeAQIXgAAKCRAjG68g8s99rlhsAJwNTFc1W0eu3Em6+RjD9WZWtX/1
 0QCfb2riDssKYX42D7HhVjDvTe1BtXq5Ag0ESLywEhAIAOQrj0PRt1WOC3Gh1njF
 KDacQl1aJ5f52yaz0FLpu7igTRS/8ET1+uHvIwzcSbbG/4xWqPwirMxpNZwpFMzX
 9l8bURIX5szmJ+bEl4VH+La1p+w31YswBn0PDTSYtWhaIn1LMXED4e2Kg/wUCpLT
 M8htMa1pg0F2ZcmvbNZFuXMd3BBAkvWrRJTYuDXy8HHnbALjUd40laUDT3Wi6FRB
 W3HFj5lIiEjnJG52iTSxWVEkoChy7l/qDQ0zsguCCZZvLfdQz2DAFscjX/HltuUK
 s/gkzVR4jZDVMQPqCATuCvDYHrDWJnfU/R317Eg2kp2tJrNibrnFX+ciISSuq1+t
 UmMAAwUH/1XXvFtLACv8NFLVFVWM9wA70ZTLjZEEfewbWRYgT1yvOChn7H2ef3mn
 I7/WoLF3ntm8Qcw6TcSrzVbZjgdWpS65Wc5YZn1rMb6nP419kjDQPjvB8RUA1g9v
 7LuOv8qeqqo1/mT6PIh8ZnhWR42ei8l3QcbyGJMQGPHyUZk84qbd1TI9gO5GjWHZ
 LIi80DPb0cpazMCIgYjrqZsOoq4XcYJZah85Eu9jdqbx8aDNnag4NeO+9jhy1msg
 xC7WuLYPctfFZ3q5ZwdvvtfluyeKjqY5mzkAuXKbtK66yMLugU4NnR1IeS7oI212
 NF2FmCRAkCMB26n8sd7xavpd9uF+6ciITwQYEQIADwUCSLywEgIbDAUJA8JnAAAK
 CRAjG68g8s99rkWyAJ9b53BhFJ6+49cr0IIZLxVBGlWNnACfX4O3OOhx8kClRzsH
 1wm6VFjn7qg=
 =q3W+
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.242. Rich Murphey <rich@FreeBSD.org>

 pub  1024R/583443A9 1995-03-31 Rich Murphey <rich@lamprey.utmb.edu>
      Key fingerprint = AF A0 60 C4 84 D6 0C 73  D1 EF C0 E9 9D 21 DB E4

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQCNAy97V+MAAAEEALiNM3FCwm3qrCe81E20UOSlNclOWfZHNAyOyj1ahHeINvo1
 FBF2Gd5Lbj0y8SLMno5yJ6P4F4r+x3jwHZrzAIwMs/lxDXRtB0VeVWnlj6a3Rezs
 wbfaTeSVyh5JohEcKdoYiMG5wjATOwK/NAwIPthB1RzRjnEeer3HI3ZYNEOpAAUR
 tCRSaWNoIE11cnBoZXkgPHJpY2hAbGFtcHJleS51dG1iLmVkdT6JAJUDBRAve15W
 vccjdlg0Q6kBAZTZBACcNd/LiVnMFURPrO4pVRn1sVQeokVX7izeWQ7siE31Iy7g
 Sb97WRLEYDi686osaGfsuKNA87Rm+q5F+jxeUV4w4szoqp60gGvCbD0KCB2hWraP
 /2s2qdVAxhfcoTin/Qp1ZWvXxFF7imGA/IjYIfB42VkaRYu6BwLEm3YAGfGcSw==
 =QoiM
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.243. Akinori MUSHA <knu@FreeBSD.org>

 pub  1024D/9FD9E1EE 2000-03-21 Akinori MUSHA <knu@and.or.jp>
      Key fingerprint = 081D 099C 1705 861D 4B70  B04A 920B EFC7 9FD9 E1EE
 uid                            Akinori MUSHA <knu@FreeBSD.org>
 uid                            Akinori MUSHA <knu@idaemons.org>
 uid                            Akinori MUSHA <knu@ruby-lang.org>
 sub  1024g/71BA9D45 2000-03-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDjXWqERBACDCxgN9+yMfpm3yvkYp+P4Uw6xxPdcZ9RvnTRkBX9zXaRgSPmM
 zeZ63LpB99uVphVZrv/EdlyTf+cRdz6VXXRcTBloA/FsyY86IluBnWCH054WyXzr
 7az5WB9yDbPnlwcSL919bq0UqTuQUlQswdQAoDQG5LNNZNa0T01ydYtNlwCg3weS
 I/nEJrGCXGy2wrjg8LiwQ28D/Re2JHQPTYqDEZl6wj5U83wT55ChnTrjPRbGmr/C
 UdJP6CZQg6+DXYGYulcp3oL4btcdFDRFglJzmQNkUYmqiVC20SMVKUctrOCAI60P
 7VE40UtXz9EounPSRQQ1lSdMNeRwrZ9o7IcrSj0EBw8lw3d2WxyM2Rs2crZWfOI2
 mu8dA/9LbmAw5sLk5Lo5i41nAWP76pyuGxSia6zMRdML6ynoC5kmyrI9TwW5LNU/
 Lsq1Ru2XSA+CwSBpTt0vdwS88dDwPGxRuUHhWVpa1M5t7K7uYODB1cD5AyNoNnR/
 lHpxfPZOJNdA3OPgfssN9K+PIuhbBU5xONCoAcdC9TEqSezfUrQfQWtpbm9yaSBN
 VVNIQSA8a251QEZyZWVCU0Qub3JnPohWBBMRAgAWBQI411qhBAsKBAMDFQMCAxYC
 AQIXgAAKCRCSC+/Hn9nh7n1bAJ4vkEQX0JkcYgltt0Vv5qkS3bGqNgCguxfhuEzZ
 vBzpAW9/XdstjA/DSPS0HUFraW5vcmkgTVVTSEEgPGtudUBhbmQub3IuanA+iFYE
 ExECABYFAjnly3oECwoEAwMVAwIDFgIBAheAAAoJEJIL78ef2eHu7RoAoKn5Lw0y
 C+/lju5+pV0WI5dmxTzxAKDJRtsRSTBcJ7ohvzztxZqyjfSK+bQgQWtpbm9yaSBN
 VVNIQSA8a251QGlkYWVtb25zLm9yZz6IVgQTEQIAFgUCOZGiowQLCgQDAxUDAgMW
 AgECF4AACgkQkgvvx5/Z4e4t+ACgnr8RmYw81/oC7MKS2CSoFb9cg6sAnjKay6ho
 14iMG+YcFNbjxwGvSE9EtCFBa2lub3JpIE1VU0hBIDxrbnVAcnVieS1sYW5nLm9y
 Zz6IVgQTEQIAFgUCOeXLZwQLCgQDAxUDAgMWAgECF4AACgkQkgvvx5/Z4e5+zQCf
 Z/09J5FOgAqw3UrTTAzR6QWicG0AoJdlBcdUltEO4WV+q3FRlw4RVnA8uQENBDjX
 WqwQBAC09OxAmKbGn9FETdMA/5abvOY7JgNcFhQutEVnJ90mF/npBucWkCRbOr83
 t+NB0h5Te+lV/c+mjPyOemfWdAK4R9zQsat+ZqATv4Vgiy0UbJ/5TPfSraNK+QkX
 nxcDrhpcJXZhX6VYzbWdRSn8xSZzPT19qq0BFafz9UhZKXnLDwAEDQP/dpZe0jWw
 rED/Kbyr8CDoEKuun/5gPi5xmNz9iJlyvcsdOgok7yen0HHWgdaZAGX3GzjpB5gA
 aISX/kK66s+NeM1XQ7YXpcI8naf0jPa6N3SNWjLf3xPxLbMk0SyaGnrnSQNikk/H
 Bk2Nqyn0kcEaaBbdfrgkuuQWPnBDrq2EdOOIRgQYEQIABgUCONdarAAKCRCSC+/H
 n9nh7oxxAKC+gMyhZmSZdTvT3a2Y0RDOx5kRLACeP3JEvGZAZuo1sJeEw504+jr8
 1Xo=
 =M+Al
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.244. Thomas Mo:stl <tmm@FreeBSD.org>

 pub  1024D/419C776C 2000-11-28 Thomas Moestl <tmm@FreeBSD.org>
      Key fingerprint = 1C97 A604 2BD0 E492 51D0  9C0F 1FE6 4F1D 419C 776C
 uid                            Thomas Moestl <tmoestl@gmx.net>
 uid                            Thomas Moestl <t.moestl@tu-bs.de>
 sub  2048g/ECE63CE6 2000-11-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDoj/ekRBACnO84k2i5lLHZKscyV8tjQSkkr26hasdbc/uyV7HTiPhMUjEAz
 Pamk+bDmy/Ls8k0SJ1l0vILBBd31G5VYtKonIrgp4vZ9gV0fBdCyFDXb8bh11Pk3
 pEZiG9vJevq40OPvsThLKHCLNhZ5zLPp6gd0IHwRJ0LU94pouFXd33MzrwCg4gTJ
 K00Dw0w1hFtUsq6WjNC+1B8D/2WiEuzBMnO6gz0p/eJ1eZ7mvrBXLQZ0u5vJ3eg2
 CCPrtS1ZITq3ICPDN6biEiMgtRmlYn/VYvDQqxwNE0X2yMfB/9sdah45zma9EeVn
 Iy8meaCFDLhm4aIYc1foUuz3WbCNlJFY5xYPXCMXLkC65xdybHKng5TXh6NOOWf3
 PfCWBACPMotTRKttAuw5YcZE5VDrSXPYHu/jm2CpIVmrac7+kDj9pGH9sB7BdUxw
 vczqtAT0jk7MrT+u3FH9wBtEFTXl7ksGTmDOFWJgYn3ZOEaVaX/OqD89UNhrOA2v
 ZOaaoKMYxK/pszPdr1Ghd6BQCmYKtLBlFYiTDRM5UMVHTqN7VrQfVGhvbWFzIE1v
 ZXN0bCA8dG1vZXN0bEBnbXgubmV0PohXBBMRAgAXBQI6I/3pBQsHCgMEAxUDAgMW
 AgECF4AACgkQH+ZPHUGcd2xMLwCfdEkPZVBgEmYnlyOKfyTSslMhud0AoKDKZNXA
 huNslb4KF8yKWBNRwfPStCFUaG9tYXMgTW9lc3RsIDx0Lm1vZXN0bEB0dS1icy5k
 ZT6IVwQTEQIAFwUCOo01FgULBwoDBAMVAwIDFgIBAheAAAoJEB/mTx1BnHdsOfMA
 n1xd4f7iAe6id42DLg4W3fibsCwsAJ0cT2lf08RhHkT+zLVoubyIDoY6ILQfVGhv
 bWFzIE1vZXN0bCA8dG1tQEZyZWVCU0Qub3JnPohXBBMRAgAXBQI6pO9pBQsHCgME
 AxUDAgMWAgECF4AACgkQH+ZPHUGcd2z+7gCdF5fq/lebn3/gp40O8xP/J0XFbiIA
 oKJP186L04qpSNamc/qG3gs7h3DGuQINBDoj/wkQCACl8M8ObSTJaOY4SgoQkKgB
 CkJJP5ScUpfYV9w3dxKL/77cyfghfYsnAWuA9yXJcjA0F+u+jRf8gS7OaHD9H9Mm
 pMGq54Aa0KUQaDbL/Jzf5zrKS/RASHzl1vYXuZB1OIzPfeAIx9u3UaziVEGXJha3
 1KgTur+TU+F94ZFTi8uApq2VoNT6sFi/V2x79bxlLFr9M9yD/0+kMZKovWRODy6T
 gWJzzcdd//dkvKp22tNf6C2wq8Bu60cWR81+awgG2otgZjCPUs2Bwhqa5opeUqGn
 J+f+PXo6+m2UF21m1vLARENuumu6SXf3XqGIUiQbT6jCdJORzwaxeCiMfu0qNnUX
 AAQLB/9u9gZN0N0r21ZjM6ZRmDC/REouCdYHEj49+f9g/xLXCfacpWVcrK9lIrcg
 hxRE2mQ/nlQLeHroC3Dp1AfThKSPFX3PRD/9CcRu480imT84ljf+6vonAZ20Edm5
 vVO+UoJMZQ2G+rWRRf4bDfwFoyDw3DsNmUL4yH8m2RpTxXn0pQtD2riJD8CBCXEP
 K95TYT4MomJ7Szg7O5/QLngfw0q6QdKRm1vEIP7r6t+UbVNp9+5g9qvz4aqm3beY
 pw1QCDHcqpDITnlTxTdV2SgNpF8JPg7joaOa36AxWwRzfLFyzyw/JGQE8RwJa8BN
 iTu0IrKuiF1biRxqiYO887GBA/8QiEYEGBECAAYFAjoj/wkACgkQH+ZPHUGcd2xN
 TACgkS0AGqqd2nLtWhpbE72tD660tv8AoI24cRkUa2op32mti5zfLLMsM4AZ
 =76WN
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.245. Masafumi NAKANE <max@FreeBSD.org>

 pub  1024D/CE356B59 2000-02-19 Masafumi NAKANE <max@wide.ad.jp>
      Key fingerprint = EB40 BCAB 4CE5 0764 9942  378C 9596 159E CE35 6B59
 uid                            Masafumi NAKANE <max@FreeBSD.org>
 uid                            Masafumi NAKANE <max@accessibility.org>
 uid                            Masafumi NAKANE <kd5pdi@qsl.net>
 sub  1024g/FA9BD48B 2000-02-19

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.2 (FreeBSD)

 mQGiBDiuMYURBACEgL3d4mL0pojugj8TZFEQef+MKkXB3lazrqV2ahgWqt6K24qr
 5fZrGkI8vxmYR4VkI1eLfe0Q4LoBZifL5nJYEvMvWPmdLuYjp4iwjgBdzLnwr59+
 k8+T/fohGDOqx45voCdq68Jmxg283zFGQ4FChMP3ZMlOPmFRIp01C84xxwCguNFG
 BVPeuM0y7JH0ucRygUqc4acD/jfe/UEjGBWxOCfZYOnXEp4NXWis3xRyUDO3cuoG
 8M8MEmg0dX0onFuNU5yrEBFtzPw2GO6DMM8h5hJXdSWkiyusn05PGk/jVSP9/MD5
 TYyqKL1tG/fKUgtevZSi7o1x/N0bgIBqmzd30Cqx29p7juVV+SBcKCRT1qloz6fc
 a5B6A/wJD5n3HOAStsWpZ6To/Apdb4A3PD4+ePfQxSICsHCFg/M04FkrG48So2qc
 7dSq6UH3xLsoiRIUonwCQsT+PaQQMrZNKjfal9xlEFfw1TV/squ+oNE8E24Lkzxt
 8Kkn86Ec5uiUlRulSMG9HJuWM+9Qu7TF76FWP8llVp6ELkYCGrQhTWFzYWZ1bWkg
 TkFLQU5FIDxtYXhARnJlZUJTRC5vcmc+iFcEExECABcFAjv4RDQFCwcKAwQDFQMC
 AxYCAQIXgAAKCRCVlhWezjVrWUEIAKCgwVSawCg1Lzrbf8uZdMAfeOWFXQCcD7EF
 tsdhbEV62AOUeQQWPr9de1O0J01hc2FmdW1pIE5BS0FORSA8bWF4QGFjY2Vzc2li
 aWxpdHkub3JnPohXBBMRAgAXBQI7+ERfBQsHCgMEAxUDAgMWAgECF4AACgkQlZYV
 ns41a1lUuwCgsIhWJdtPBebkV6w+NQ/8jlkJgrwAnj9lZkiTAgl1E/vcF7yPbY7f
 HlHetCBNYXNhZnVtaSBOQUtBTkUgPGtkNXBkaUBxc2wubmV0PohXBBMRAgAXBQI7
 +ESBBQsHCgMEAxUDAgMWAgECF4AACgkQlZYVns41a1nv1ACggYgtKhaprmMs30oz
 yoC0NatFJ44AoI0XSPh2G9zHEjF8AyYAe6sVCLqvtCBNYXNhZnVtaSBOQUtBTkUg
 PG1heEB3aWRlLmFkLmpwPohXBBMRAgAXBQI7+EljBQsHCgMEAxUDAgMWAgECF4AA
 CgkQlZYVns41a1lYRwCcC8l4PdrwHKNrZlTW6vod6kYgR3YAni8iLUZW5Se6nTH9
 WuN0XYPpZRG5uQENBDiuMdYQBADVzBBn5+1UQVCLS51y6eCD3TidT/uJAr+eeiWZ
 IbTmXrltNm5rGs7OT9QYNLhCFFPYKJxa9hFbrGpgserEFnqBfxcbMLa/wyIm9m/l
 MI+NNCAU4IpgDWtgjf1kjzwnJPwH69YzcqS2jlEKIjkCrEa/Bpr1Nvo4aLvqlTR8
 tJh+1wAECwP/YBMEMx/zgTvS3Jtji6nPceRe8icGRHb4SD7MVF/WxYu5VK7wlmuw
 9I9WXnHyYaL4c6Q49FAvwhkppByqJFL0txyJ8+nNa6H5mit8m6dcsCMG3NzyvxBP
 082h/MWbJn3Xdg89lp4UG3UP8sV1oWyIchd8rqxFk/EVB7fVQWNz/gKIRgQYEQIA
 BgUCOK4x1gAKCRCVlhWezjVrWUlcAJ467I5lFNlkwcENe5vND+DPaWyreQCfddOu
 6Va2/bf7Ln4TKyl17uRro7Y=
 =VmY5
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.246. Maho Nakata <maho@FreeBSD.org>

 pub   1024D/F28B4069 2009-02-09
       Key fingerprint = 3FE4 99A9 6F41 8161 4F5F  240C 8615 A60C F28B 4069
 uid                  Maho NAKATA (NAKATA's FreeBSD.org alias) <maho@FreeBSD.org>
 sub   2048g/6B49098E 2009-02-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEmPtPkRBADEcSQQGME+Df6I9jnjUBNMxvX8aMAH0+SKJEn0xTZvu9WLQmJv
 Bx1Hh6AN8fD7OONFBYGsDAxbbgFnwxc/KPBctXHUxoTE3lRTFRwYJJKIKvrDhFjr
 qDWwLJ9TsUn/pDsBflPFe57okBlPgSywTLGLuurOaT7oda6Z2K0FOiALVwCgn/b2
 7R19gm0uKjzsEPejafW6lZMD+wQK4qETffrdqRoVRnzzpTa+xa60kQxxsIeibffy
 dovqH7HIWeqiqDwls17zmbMc7auNliyN7VJ1bQ2C5SkojMUqgEsVle/8gfe0cWhS
 2jJ8A3Xg+/IzYwj+TtlWqUkzx/b1Ck8v/9aRmLtTNo9OdC8H9Nu1onF3Cp0WqsiN
 gwNHA/4+8w5D5gouNWfuYkkzoQQ2jIFJ4zhe0GCb2MIrqKrf0N40NOcYFLi4eJ8F
 W1DAdQbQjfMMlYAknm7MBpnsagTqjS9MniPVygYUUre/xMx0tszvWdGdRSjEY/5U
 AXoCevBci0meKTm5ZSDb2RPOLezF/zOV82IY3T+OKXTHcLSeubQ7TWFobyBOQUtB
 VEEgKE5BS0FUQSdzIEZyZWVCU0Qub3JnIGFsaWFzKSA8bWFob0BGcmVlQlNELm9y
 Zz6IYAQTEQIAIAUCSY+0+QIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEIYV
 pgzyi0Bpf4UAnjOqrSHlb4NdW+ulVFu3o8W1hbTKAJwIdn91S2W9V3ueKsbFqq62
 8dPYsbkCDQRJj7T5EAgAuaHr5IuEXaxoUcoZryGZweRs+G2Oh+jsMIvMABVGMZJ1
 iov7vSypm1EF6/cO3O+rn+Zcpuf4XKPP3TK1oKWLIYRgdkvTWwzVc/PGWRHdr6/S
 fo1B8/jr9tWW50p+s+KZoMPV/Rdz84AN8bNZVAMxNWXooYrGMxMvEDg3rX8KZW57
 25KF+GlYYBoIXxatMYGlZKz2lcaeD7Mf9EFs9jtpyZ2lhlXjWu3NZBdf4ClzWt/C
 uQI2mM2oEX6oZEDCgWvGoIPKzMruI/lAPi8I4Q9A3fH7azEz/BHW6yqLcXfmUrMe
 jsGTS/ovpV/dyxqNzsVpt203ZBxSSkSjOOMO4OzBOwADBQf+LVc888G6GxeCJGxp
 X+uACx6ziuaGO2AIvfUWN2KlDEpiCHwKf1L4FBE6mKm2l9ZloNyisnL8nvC/lmes
 whiTQkiVgB014EDhR7IoljZQJwpJqWC6HCwED08In2O/fI4JX3XiPbUzYSmQSpd0
 tMMBVBwkB3m8SnTaF7cnYrZVGL2oCrBxfbYYhxDtxmGnD3q1/me7dixUJLbEHSmj
 wXvORtzMuADmNuz3RkkEKrtHXgqtqYluZwb3VNlRa9T/MxMYMfMA9V8IYw4gQkM0
 xEM4UOUuweNyXRUSyuvcLQJthhWiw+Yfi9ATzdbnbwh1rwwVOoIhcM4QHBgPhnir
 vrn/k4hJBBgRAgAJBQJJj7T5AhsMAAoJEIYVpgzyi0BpqXQAnjkUgOmypg8bF5kd
 ZDVC/M0s8sUfAJwIJuJHTepRSP6qVkZKiXF5TRMt2A==
 =Rtch
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.247. Yoichi NAKAYAMA <yoichi@FreeBSD.org>

 pub  1024D/E0788E46 2000-12-28 Yoichi NAKAYAMA <yoichi@assist.media.nagoya-u.ac.jp>
      Key fingerprint = 1550 2662 46B3 096C 0460  BC03 800D 0C8A E078 8E46
 uid                            Yoichi NAKAYAMA <yoichi@eken.phys.nagoya-u.ac.jp>
 uid                            Yoichi NAKAYAMA <yoichi@FreeBSD.org>
 sub  1024g/B987A394 2000-12-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (GNU/Linux)
 Comment: KUHASIKU WA http://www.gnupg.org/ WO GORANKUDASAI

 mQGiBDpK8uIRBACY5SwFQXiqzDlO1k/syoFoiFIFl/Dp+QmwK2oovIvlBVo/1gbx
 EhXrKRrfC67KSxxdUsgN290v/VVTmq8Opy1/RF+RAdxM3JrUfkcm5+IBWbSUfXFP
 i8OXBVgh7wNENVtwwD52F+0CFIWZXkClaif4DGkf38V6LJ6hBIycxuNDQwCggXTT
 Kj5SP2hFC0ueyQtPDoJEgbED/0bPL9R08io82IQqksOR9IUy0OdFJkLVWLnollEY
 LGjXa/AHgE8L8oWU/2eF1WM4JrtVRdcKe0Ja2e9LuH6IonGAdwqUeeAOwA/RdGj3
 63EglH5ugv4rZZKWZ3/piuNXvtq0bhAfl6zBHi5iUB4bgPVoVJGn3VyykPWxdqfX
 sT5+A/wIml11cFMogN3RXy/2Y3JRWeBtUCfdoRjeQPgK8++krm2Pr/AtHgcqNSjI
 W0slX4cLou2TEhV3BHb/4npsdaY0BzYgL7V1YggCv0Pu1s2D53Nzi30V66SRP0BZ
 OlNTA88WdMfoF3ttb04swSenG9X8dbpyYEdlvxNbbKKbUiBORbQxWW9pY2hpIE5B
 S0FZQU1BIDx5b2ljaGlAZWtlbi5waHlzLm5hZ295YS11LmFjLmpwPohXBBMRAgAX
 BQI6SvLiBQsHCgMEAxUDAgMWAgECF4AACgkQgA0MiuB4jkZz3wCeIi857V2zyRA7
 gRVsx+DcoCLeC3YAn2G3gFd+v14iZHXrPaqpd1gSjjayiEYEEhECAAYFAj2pty0A
 CgkQFwU5DuZsm7CchQCfdD/itI8d/uhmH9A0upJYYoYS46YAoOAfpFKvAGe/vBpw
 dy40SxBG/qELtCRZb2ljaGkgTkFLQVlBTUEgPHlvaWNoaUBGcmVlQlNELm9yZz6I
 VwQTEQIAFwUCPai4HwULBwoDBAMVAwIDFgIBAheAAAoJEIANDIrgeI5GKx0An1kh
 KzDAfR7Fzba/V7DHq2BRLcRQAJ9nZFgBncerxFMYAanwJruIYtPnJYhGBBIRAgAG
 BQI9qbcxAAoJEBcFOQ7mbJuwe4kAn1E2VVFpLajGFYgipCmMgpxRXPmxAKCUa/ee
 BEW5LPNf8xhaeIGlAtPZm7Q0WW9pY2hpIE5BS0FZQU1BIDx5b2ljaGlAYXNzaXN0
 Lm1lZGlhLm5hZ295YS11LmFjLmpwPohXBBMRAgAXBQI9qLhMBQsHCgMEAxUDAgMW
 AgECF4AACgkQgA0MiuB4jkYrnQCfUgkHO/ioUTHeBtYJHGeL9qthlnMAnikYzk6K
 gDV8cHI/ETcNoh542Q6piEYEEhECAAYFAj2ptzEACgkQFwU5DuZsm7A/JgCgvX8u
 hjU7WPofTfM2d11+j+ywHm4AnRS8iRNMqbP9+crcNzCRSQ7OZFqluQENBDpK8vEQ
 BAClmz0m/wuG01nst/7X+riyNgZ3j3oRurb9Fg2pb7wkci6nlhzCHTcFNCZiY1nS
 Vp+/3tRkC7HQPz3zhYo3ieCf12NUweJ8jhbZubp1fYY9ubKoj12I+LXTfZf3kA5G
 UD/n1nkAqxH2yP3eVz1BpKUc+Lz+5USiDo+XfrvfxQcZHwADBQP9GejakrIdVKcA
 /4UTWnMh8HK2b7tDLwLKyJg/8lagBkIAH5tPpCXi1qXuvHe+T9SjbdwW/lyxSARV
 FAz1ejp4QEWsAGQ/pchjb+S+iYvNq0VfzkZPqFFllLMaQc9mo6blgGgSEqLNpba6
 gDmVTJZ5jAhVxFBhRPwchSdPP3ewVRWIRgQYEQIABgUCOkry8QAKCRCADQyK4HiO
 RpwtAJ0alZHYWdBCXaPF9G9HCl/T40wzJQCdF5K4aEEsIG1P0WmNjbY4PEAVndc=
 =NZ/b
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.248. Edward Tomasz Napierala <trasz@FreeBSD.org>

 pub   1024D/8E53F00E 2007-04-13
       Key fingerprint = DD8F 91B0 12D9 6237 42D9  DBE1 AFC8 CDE9 8E53 F00E
 uid                  Edward Tomasz Napierala <trasz@FreeBSD.org>
 sub   2048g/7C1F5D67 2007-04-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEYfTV8RBADcVRh6fWX1XI43cTrdJBctCOxf9jZ6eedmhajkpMRhg7b0JPPL
 cYL6H1x1xqKbXtKxWE+BzQfdDJNJhwjQIwaXityWHihnkw5XBCRMuCGrUuaW/pPQ
 31EX1Am9d8k+ckUK8tPMNuWM8+ZYjXTJppLg20pIPBRwvmRR/hrHDhMvbwCglDGC
 ZfTHYkv36MFnkPHJH4iaQIkEAKoy+bcyOiJK0iuAx5KeF3CxP53Nd4sbsHKcbibP
 OsWJKKUHPlVTts6bUvM6RH+zUHOeWpXmgNvZTsvmoLU/E0I80BN5ngdOwV7oqeAk
 V03iltsBGIeBv5B0xxYDyQBuo52LV5CGZ7F65o1jGF8LWfZbtPh02gTmhYymmLeV
 QryDA/0WbmKavL5Dh7L4Ugz1JVIC6miD399IsLV+XewJjcaXnnngIplz0ZjK9hHx
 kuG4w3pi450z6gMTmpY1IPC7R158j/fLhygYLhB0sffXaGs50nizBlBoZNR/RZRJ
 7Ik1Q1E4dV5kVhgqBs6qPCfAdVMKGTWpM3xF2uyFT5xbuVPxIbQrRWR3YXJkIFRv
 bWFzeiBOYXBpZXJhbGEgPHRyYXN6QEZyZWVCU0Qub3JnPohgBBMRAgAgBQJGH01f
 AhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQr8jN6Y5T8A7L7wCfa7dxDhHm
 WYOcaZ3PiBCxbMyMeW4An2regIquPmK4ZyrJkfXGd7BmmgGKuQINBEYfTV8QCACv
 /cPnRLjvnYJdozvbzoBqC4m2sAmBClDV9cRtIGXu//ULZ0CnDmEByfp7W2Aqlm4a
 +WnDBlbKaP4td0uwvly3m2hNH3DS/7/aBaDYhPUeetmIP3GZrelGlQHqe1ldJuwD
 KEiR0ANagAikuSiO8Fv76YY2dFmUSWh6mNd6+/F6hYahByJbDXrsYNSMI7BtpH/C
 fPaSew66982uu86IGIZPREfKSYouLuuHPUwrGRbcwyeIL5y/0i6Eyxi3JuPHCYSa
 a0jX5VQ8Gn3P3SukTdK+rWaJQMlzjbdaZknB/GeRDEc6ND3eqdmQa/PdnkGVwHeI
 S17IutKHDCsxDqSJgak7AAMGCACJtwmr70SqnOxtHugDB0G4tAEN+poeol9zfEnE
 A1nZImvDNLUoX11YZRLHCc9nz2V7HIzTacNL8ue5DenmtSs72S3zHM/DnIhXjx8r
 hBFrSW/DdJB80LLcC/NhRcl3U6sof4nzYuipkgr7evAeoZqWpHiYcuag0ZRRH5Jv
 4Yh3R8zFYAg2NSKs2Q3CCX4c0vs1boZ1f2x4QQhxTpsDkjJxGPJ8OEAR7W5BjDOY
 KZBL9+02bzJKnOcbrtRkbylGZAQCxX9DoZDGHSCqaUBZMJZzWauW6xcwd4s91pMQ
 MVG1u5WHvZlOEo1Cg3Y9QSyehMKkcLwyuBj2zP+ijlkIBuFhiEkEGBECAAkFAkYf
 TV8CGwwACgkQr8jN6Y5T8A6VnwCfZdSh5TaDbb0wjcyUkVYAWZIo4n0AoJOfSvnF
 MeOHsJ51PEblZGwvjW0k
 =hc/r
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.249. David Naylor <dbn@FreeBSD.org>

 pub   1024D/FF6916B2 2008-04-09
       Key fingerprint = 6540 B47C 54AA 3EBA B23B  58AC 51A6 8580 FF69 16B2
 uid                  David Naylor <dbn@freebsd.org>
 uid                  David Naylor <naylor.b.david@gmail.com>
 sub   4096g/77FA885C 2008-04-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEf9J+oRBACuI27aa4Vrp/GkerkQPTMlag96B5Kyi4rxtz2rVyHuR0eROYEb
 L8h1YxtfQhJpFc1FeCO2URZxwUeQoIdHhosIOEF5NQfH9ach7HN3uAo+CgXE8O2w
 NW4fyhnCchCvQ+1QZ5bD4fAdHLuGbOIQYZHy5rtvZXY6O1iIgK0VfCzJJwCgj12j
 VqgqLxRsNoqA+aqmyDeDJ7UD/jMduH2sxw5NPkCRK/sAXVd5fvdNVqJbHifE9gnh
 h+qF6xXUAe8wEP+OPoxj8oOrRjnUIpuw0wAhuLi3OAY07HoAZGn86I+u2puwL9aF
 ptmw+R5t4CXGgzoWJy297TcXNK+AeOULo58MxsetS9oH0daLuhmCYW939ADWYSZK
 SrQEA/sFxpY1EqrIrIiAmr035NwkKJQTU6qISudJtHrejMYuTtzBb8sUKwEFAnOd
 Advg6OfXlNFkfBFi0nTW5J7Jv5BZngLkP6+Pog524kmKWHzxJXrCYhBTknGOde4t
 O1ZyBXuV/Pc0BnKdmS3y06mp9/f7+n0SDPS299W/m0+I3ZjcWLQnRGF2aWQgTmF5
 bG9yIDxuYXlsb3IuYi5kYXZpZEBnbWFpbC5jb20+iGAEExECACAFAkf9J+oCGyMG
 CwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRBRpoWA/2kWskfcAKCNC1yYmCXCTJjX
 p2KtstdaP5qxKACfd8xTJZ4M3rlsylHi4OSjAr073Lu0HkRhdmlkIE5heWxvciA8
 ZGJuQGZyZWVic2Qub3JnPohiBBMRAgAiBQJQ8mYdAhsjBgsJCAcDAgYVCAIJCgsE
 FgIDAQIeAQIXgAAKCRBRpoWA/2kWsotrAJ4z49iqbPtwpgO6ejJECj49LeMinACf
 bGofnCJ8e4cL5OoL7eFW5ancTxu5BA0ER/0n/hAQAPH8yN5SncUXBzP8WdTsLQbN
 +eGCGh65e8JYt1ZomY7LQYnUS5paZ7exD3YRcEdLvo5i2N7ntvBBMad7Z00k61mQ
 9HxEp9AUV4tNjAcELdUNTzYbx425UtwtcJCCrYOw1QGcTGuvEy3pGWOxTPJul8kb
 strYIVXoslbH8UZHpf7tmLCTV6e/Ta65WeVKVVcxC+PORIRFIq+Ft6ynJIIXIkK1
 LGn68yV05mlzWhohZBixkMr4Kolh6hwUZNZvfc3aAAc0z0FI+YqmOgX2SifVhAOe
 niA4fI8u0txDwhARATIp5ES8epCXvvI06EplVJUmpeX1nXs1GegOrFJtHjuNkH7I
 9irNIQzXouR+PBE0EhDgEkGQ7hM6xAk8khnoQUZxYfytaZvpRGvXupFPWAbhY2EK
 Ag4W/k5UMz4zS/gBHOcWUqOC+YRrcfB/9CfFz7/p2YrCPXeQD92p54nfJwtGIEKi
 kvTd+4Qg0qlUXxdKZAoW1p+8lO9Z2UeypmmbR/ixqQzqDJPyt+mMaQxom8trdi82
 Q5D+CDoRHsDtdCmeocLhjuNgqEfPTHYBvnkD7daEyJUlFh6Ir/s31bQq/vy4JZuo
 3QUwn96upPvYdJ6Ova9+AvQejdVgECi6L4re8unX81K0Y7guTR6R67n1mvhvA2P6
 sXe/m2mJU4Qzx6FV6iIrAAMFEADafXKtPRTuPNSXx3UIEfA+eN/zgdeli8wgL/I5
 XGYt9N61Yk+CzayNGgdd0dW/wEKjeaARylzh4Fnt8flciXluarVvhbTKZ2H3cGEk
 fy8K6+ciQZWc9xXyIalitS/0IBpLEqH1fysKZkdsEaqabPrft/233WY0NT8P/dXG
 p6ZIrDLS2QHvzu6+jiymE95eN6sXxN211S4kk9ylsq2eRTNTLIvG4SEmb6dsZ/XH
 fQ2vu5B83DI1K/tZzOdUeUnJ/LrmknHPNOyMoFzjr35m6avuQNi6W5DsqjSnowfh
 7Q59ycRYW2Thqenigukjwka3vtDgBQmL95q1ChL0rrU+ilAmFZ1Hql+Fy5K3a0Ez
 QtLg+0Up9EqUsdBU/+agIeR6abS1jk4ZX73sWgZhoyy/J2TtUNDXkyu8FM1LwMbZ
 L9F2fsAXUKzP+7Ec8t72Y1oCGdnDhAVZ6fP331E860urCU7GVew/B4mP8ntL9L0O
 kR5LhDHRoe7CguqFuP2fK0mMeD0FOzCJax5jfeFlT8DVwyZTcvifPUd6rIXuahLZ
 Mxdj8jc0aiwSB0028D24i4NfstKte/CqXNUwFbfvz+gGyHjJxvi5C7zxyHqwNIhU
 oByeBFBpaLf5eQYAYbTOxN5GqM5X8EZsFiFNTS+4iq+SlJogINVjiYSNaBaK0RDl
 XBsV7IhJBBgRAgAJBQJH/Sf+AhsMAAoJEFGmhYD/aRay0pIAnRKVCvAwdHYoVWQL
 zVPFqfdKGvieAKCEVFYc/8pBcdFH6X/+68UlQbSqrg==
 =0MGk
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.250. Alexander Nedotsukov <bland@FreeBSD.org>

 pub  1024D/D004116C 2003-08-14 Alexander Nedotsukov <bland@FreeBSD.org>
      Key fingerprint = 35E2 5020 55FC 2071 4ADD  1A4A 86B6 8A5D D004 116C
 sub  1024g/1CCA8D46 2003-08-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD87tOARBACkfv0/19ar/kUNsj2vL+APjo/cx0A0bubEmaPhwNuLOjtafdNm
 /pUULYi28lDVDxQJ8UM1voqrCcue+finCyy+k2L0nR37tlUA4t/+GH4gq4y2xL7S
 o/D5DqHDA0cTDAIQCbdD/rj3Z7nJw2Vkn3tAwZ6NUXV7OdLS+csbpJIjmwCg0HB1
 tzahpgegUe5XauCly+NXNMMD/3UcnNA7kBKSZMcuOVq7TkqYYvQZPoroK3yYcAZL
 Yo4WoPEyjtlD/ZpZVysQiSMxLXRHjsEbMAMZL7Tx/Sav01XUiBHBGDHXaWWVdqmg
 efxtBeoG7MZxAAXBLfcSeV0bjkd9oGWW/inHrl0NgEljZQqo1kbIEb5asooyT18v
 vZgjA/9l8xZdOlSJv7Ct+VGrfMStMmpBCn7IRSjeJRq2pNe0pbJtzXAnAwyrB62X
 gF6n7ONKdLk/WPihRdfrc4BZnNIWZU0q5P11rOENQEnToprAOYebhmS6cY0lx0SR
 M00HVTTgzsNVWDy9h+uOobicBSHPh2La7KGnFRtMb6pZFg5Y2LQoQWxleGFuZGVy
 IE5lZG90c3Vrb3YgPGJsYW5kQEZyZWVCU0Qub3JnPohbBBMRAgAbBQI/O7TgBgsJ
 CAcDAgMVAgMDFgIBAh4BAheAAAoJEIa2il3QBBFsAUoAoIGf7gn1DPL+Miw3/2W1
 YdJPT3TjAJ9LOVjgV1mZks+FjRdl1IETcJ4fPLkBDQQ/O7TjEAQA9yIaEvU/Vbj0
 L1xFjIOGEyM5vFvn5xP2LibOI7hUH+cMDaWkBgrSLqsI7k6P3HSTVWpkKUTl+vJe
 OJnIx1gFE/WJDPK5trnjzHQI9kWf6j8EREXCFuuvDy3QhuJiHTjB+I8IVYh+oiXl
 6SNo0ekvQd6KZlkPUXy8rczb8Y+A7GsAAwUD/iPYrIWC4xSX8kL6HFjaE2fS42EW
 iyfyb7slFSE2xtRf+xZyBa2Mu5XQsg+vJcSBsjrxpYdd+OuyTLuYRsYvuLZnB65H
 tTli1/ous2J56useJyeik9wJfFyZBlOtmw1QFLxELly+XgKiyGRNkTrws+smyFjC
 GWwhlhc40r824oWPiEYEGBECAAYFAj87tOMACgkQhraKXdAEEWySXACgwFVr9ZgH
 TYnmgWGXAmQWvJV+xAQAn2HlGDmOpuTDzfO5PvXOOWnFjvIt
 =bcPN
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.251. George V. Neville-Neil <gnn@FreeBSD.org>

 pub   1024D/440A33D2 2002-09-17
       Key fingerprint = AF66 410F CC8D 1FC9 17DB  6225 61D8 76C1 440A 33D2
 uid                  George V. Neville-Neil <gnn@freebsd.org>
 uid                  George V. Neville-Neil <gnn@neville-neil.com>
 sub   2048g/95A74F6E 2002-09-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD2Gwe4RBACw78PVfE2fA9U0mISJrV1ohjdkzVTly0WQ/YwMgyB/J/Z/M35G
 zIc8yKi8YR/6QYGqgEzeKAhrUIDyBfudhaJ527gyR3Xi+QHgWMQDvd41NlqM5DBn
 yIVKj10DmDYjcHm29M1OHAkXKZT6tHCqp1dKFD7EXtY1bOakvN7TIKld7wCg6AS/
 iPmIvGE7wpFlcFkYIjjL4ksD/iKpKneEwB7dEksyDQX8l18v58x0lH334WDgRO5a
 X3Wlc4He8b3kWzBWK0z81XE8Z7ip0Io13LHhamLp1P1eDX4sWKQpJmdRtHziC9R6
 4GwW9P7aCUCCf91XxaYEU2j755u1Zby3gF1tbookwO1iXQERYuo3ZHezH1bkdRk2
 HNecA/9+HCfVESjRFPfOEVqljx+Lm5atTx5VX/D/6iprDUARn0YgW5xrwM8doeNI
 UxkBOUszEUPDpXPnMI5RWB+0siQhZl3yX+lUPtASrEj84rpOSXZtNPAkHit/iwva
 pW75gZjt9yN7IhVQVw8O2OMTRGNoWsshzKzznqxNP3p1JYYq/rQtR2VvcmdlIFYu
 IE5ldmlsbGUtTmVpbCA8Z25uQG5ldmlsbGUtbmVpbC5jb20+iFkEExECABkFAj2G
 we4ECwcDAgMVAgMDFgIBAh4BAheAAAoJEGHYdsFECjPS6hUAni/U8Zbrr+TFHLt3
 cLg0VWnWxCI/AKCNqxRmA/HlZLPRzhVCQODgfbOG4LQoR2VvcmdlIFYuIE5ldmls
 bGUtTmVpbCA8Z25uQGZyZWVic2Qub3JnPohgBBMRAgAgBQJDtkW7AhsjBgsJCAcD
 AgQVAggDBBYCAwECHgECF4AACgkQYdh2wUQKM9LtQACfTi75crWjtxxVJUmGSn2+
 CDnlCesAnRqM+XSv9/KnZ3O/GRtpkNwT9NCJuQINBD2GwgUQCACvJfoCKfRo3y1J
 kaisLLtSVsqCeF1mlwfBGyvD0Lu0VnDGuy9aHExafNEbUaW+OQe0YXtZeX70CUPF
 nizBcDEsHEj1pC9HoZCSoYXtqORBa3ZIUwz+jJbjHJErs7XM/EshhAollC14rXKt
 K7+UVCw5JkCmialF7LAyWgqeBilwtKUBpIaXquf0/qws+uOikcZb3UttamQFUW0Y
 l4KKHP24cvCOXSlx8Kl9l2rQzfedjQPXI98zkcR3SEjZ07cDs+mQOTax2OgVS3F2
 nDUEqLQmAiftHFWQ0h3RBpEYLGTNd3gXXxJPxZdR7YIBnxvJ7RZM5qGgZfTc0Jm4
 aM5s+As3AAMFB/0dVB40Fvk74U6mwHLMwEkzHiZoVVZPBUMsuqb3FlgZrMYmwa3q
 APNhPhWSO9pLQlPJ99nFFj1lRUU7OO/oihsdKLEfT2CT5tqa6fAWoiSQIKBBbkrm
 bQedeXPWtvJezS0FY17rOfK8242Lnq+djS8ihBxSKpCVbwWO1DPktu6hGzWQz+x2
 B91jbMfM9/n00xEkZ4Z2H0dSZNY2WKqK+MkqAiYf6uJBs7BZV391WWQ1fagCP/Tf
 HPM0gDnwFfqSJmxJzPm3upTmYgoSRqri7NH3Wec5pY15b67JFHMpMFbgauEsiDSi
 CCk4YxHfge4SMe6noPICAjN6PCkIMDldxi+ZiEYEGBECAAYFAj2GwgUACgkQYdh2
 wUQKM9KJgACgwzfFmUB4diy5sTzLVLE3TCqwnJYAn39ByQnv/FeLGSY/blYrVsQK
 aCpC
 =SotO
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.252. Simon L. Nielsen <simon@FreeBSD.org>

 pub   1024D/FF7490AB 2007-01-14
       Key fingerprint = 4E92 BA8D E45E 85E2 0380  B264 049C 7480 FF74 90AB
 uid                  Simon L. Nielsen <simon@FreeBSD.org>
 uid                  Simon L. Nielsen <simon@nitro.dk>
 sub   2048g/E3F5A76E 2007-01-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEWqLYARBADUgEaHYK73qi4nXVO1DfcVKqzWZw0lDYXv3mVQO74Y41hP7QV4
 IyvRuuWmKK0vm+ibh4WQTRGhqeSr+tDrgUIqs/tavDVx27DdBeOi5fQwFiyM0s3B
 1o3VOzfmW3nOEAEEfAd/zQJVrz0GG6ao22zFSVRHEpJle8QD/HTsZ5sWIwCgiYNX
 Ok6oK9IdCky3kl0xwE/wkpMD/jKoZaj2/rc7t8ZtwBf9mQFECou+SsM5YFFMx2JV
 nHShx/6z/d1PWu59fnPOP/t+QkqBa4ds5msot4wJFqsFwuTmtCYySsK8j9yBbh6B
 KH2Iyjwnr3IFU2PopIxzscuGT4EKbLes925X6tjCfx+r4uGIVSJ6Xzu+9jGXK0KI
 TZshBADIuS+wneCYZ1Wnc/cwaG3SMXaVTOkThQS+l66o3BfXX77TN0HbjB+/CmP/
 lWjcUv4tTYfmI5kQg4pRA7rSEsMBwec19CIy+mf9QD1HDVNGex1tGdGNz7oaOvwm
 oT2nug8mCt+77q4ESQOmfHzLjIQqKh9D8zX08atp7EVhHw2sH7QhU2ltb24gTC4g
 TmllbHNlbiA8c2ltb25Abml0cm8uZGs+iGAEExECACAFAkWqLeQCGwMGCwkIBwMC
 BBUCCAMEFgIDAQIeAQIXgAAKCRAEnHSA/3SQqxOqAJ9qfsJx+6hT6qXy9k0Hkuto
 pyh+lgCfS+cAvWkzwcTlZwmj7xnVMqex1T2IRgQQEQIABgUCRao0HgAKCRAV1ogE
 ymzfsoOMAJ4qsIQaHkhYT6FB06o9Hjd0JElbzACgkPVfATTcp5dDhiry+UMCPxfl
 4Wu0JFNpbW9uIEwuIE5pZWxzZW4gPHNpbW9uQEZyZWVCU0Qub3JnPohjBBMRAgAj
 AhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AFAkWqMP8CGQEACgkQBJx0gP90kKtq
 rwCfc6UlwvCI+OQ8PV4Y7xVVNK8ZWLsAnjAOOQET1C1XacStkK9icK7u/n/fiEYE
 EBECAAYFAkWqNBwACgkQFdaIBMps37LD1wCgmeJUFusBpliqQMpOYaP3KL9/HDIA
 oJox4FwHo8yhvqG7ww92FMeknNCxuQINBEWqLa0QCADNQVSiZOL9KwsEGkCLtUGQ
 l7hmf9iuis/GxokTE/9aPYiCKx29wjo4b4pURS/gHdNGU70KNfqli96Q1zlS9CGY
 KhQoce0ZDOxpO/6ZZzaOtLw5x2/8M45BDJU45STx54+F/7Lt3hZMNMlNvjZGF/W7
 f5vcsPHqGAyFjDkjuL8QQqhsbaPsCTlqngFYh8/4F06+cd4GM85xGu/LM9M91TP6
 9ulvz4H/5TiUNvDjt1e82soRhwY9bwHxq7b6s3Q4Wgwo9l2Y2oW4T+TVpcCvgu2D
 vUSXo4U1ygPFl/CQ2Mz5IEp7e0aanzOU5FhMeEoAkJewRq5747noEcnygiPUuoOT
 AAMFB/9KyjWpXwovVjmNITIB1JPuZSO7NLhA10SpeFz0YXJVIiteQcHnUHOUn+7i
 tO8XbOg79a2Pz/5tLuX8YqNQQjODFKpFnFymlFr+aPpzEJPoXWHG1FkcM7rjmLpy
 gj6eokmEdQdr5CflY+IkJMNC0DxDfhsI17fQVAsaScWgnmSgfCNYT7uPFw8K8omH
 WawyIlZuAKa+l1Q03IFt0oDLqLrcMK7DnSJvSkyM7WcH+3ObsMaCXVziD9LOlW5B
 M3mZyXS3Z5A8/menv1lRYm7kxCt17HEmhxnHM5waqFyK0y++X86lNpwmBQZgzTN0
 2bCE2wlPqyT1LCVu4s9RAyET4hy6iEkEGBECAAkFAkWqLa0CGwwACgkQBJx0gP90
 kKt1pACfS9WAfr2P8Vx/ps3WYdd8QYumnQsAnAwoaIe1d968x4FIKOewpptF/JdB
 =ggBj
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.253. Robert Noland <rnoland@FreeBSD.org>

 pub   1024D/8A9F44E3 2007-07-24
       Key fingerprint = 107A 0C87 E9D0 E581 677B  2A28 3384 EB43 8A9F 44E3
 uid                  Robert C. Noland III <rnoland@FreeBSD.org>
 uid                  Robert C. Noland III (Personal Key) <rnoland@2hip.net>
 sub   2048g/76C3CF00 2007-07-24

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEamZvMRBACgUM3B+Z/7yw5DtYP+4jNaSvvJBNPtLbHeCcXzAytD/Le3Tx/g
 /joJFJZS92agbQSt6p9SPnw1xguQ2YMdBQ5LFbE5ZgrXnDX9JUWjhyjTPKRbkFPx
 5G+JkTG9I75/ZVq6AhcOjXwsq/mkANhu87uOPRO2Uf/e01o3CplYIjRVPwCgiqwz
 wycuIxPvmWX3ao5gkV5iUgMD/2cVqZQ/uareIN2HF559LZkfjGdBA7U4H1cOD7hr
 pK27HTNcSAMpHP368AY5nSEUezQ8iOArCxx2xYMIvyxeaQ5wFgQ0kuwb21JieUdm
 6+cQ3uynJMSVVic5T4qoyC3mpu00VNBpCLJIk2zLk8CPDPQot6yB41622xXXHaix
 1efSA/9oJBP+6Ffdrni7hxAEgP2uG/lXQ/oG67UljMC1LFkiV0irE9O6G5UXFEVE
 FOQfXmXqLRoIjWaqDLdfADerSl6jeva70UfbiGfxHHkbltMZi2v3Xd6H2wmZKcSl
 RDYhdvNIhNDXfGAoaYneHN+JWYPDYebG5MyN1QyU5+kB7n7grrQ2Um9iZXJ0IEMu
 IE5vbGFuZCBJSUkgKFBlcnNvbmFsIEtleSkgPHJub2xhbmRAMmhpcC5uZXQ+iGAE
 ExECACAFAkamZvMCGyMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRAzhOtDip9E
 47ceAKCI+rqu84IxKD8Rb+a1hL/+NqHotACeIg6ZGwFCNA2OOUchxF3hXvJ+mfqI
 RgQQEQIABgUCRqZ50wAKCRACwq9DxPQf7Ay9AJ9xShA298xcySmevKvX8sWC3LQ4
 iwCfbsQ7+AB2L4j25YgHK9CjF6f8s2K0KlJvYmVydCBDLiBOb2xhbmQgSUlJIDxy
 bm9sYW5kQEZyZWVCU0Qub3JnPohgBBMRAgAgBQJIhOEYAhsjBgsJCAcDAgQVAggD
 BBYCAwECHgECF4AACgkQM4TrQ4qfROOE6QCcC085r5aDgvzVDPvrZU+pSitB+BgA
 niwufou7zDg3AJGyf1MeuuFaZ1r9uQINBEamZvMQCACOvnyHYPRaWC7fFfrdqGxj
 C5ZnjHjYTg4vIUgVmPE096H+WflesmgOZ8bQH6J+3Pzpf+l6HimYtF+gMvDLIz0I
 HD1K2z75Ne6WlPKh8Is4lty1+knbOIDLqCSgFWcU1hAkj+Yr//oqUTlJ9qIrghoj
 L4w7QdMHGb7jMMLL/VHg+MXnQliD/UFAk9oF+/UbTfQwsanJXaydby0yjmXecyMo
 X20orSA/UKJe59Rc7sGOHf7uFoVByqsWQ/yesRmVsjxMNFGNMz1ekKFKHop7xcAj
 8DLYnrvdilD3MuC28USAZjSa2b84+oQJADQL1r+wT1bqWCEUvaIqf64b3Tpt8bIf
 AAMFB/9J9pOfPljyE3D0jy2azVr41mK7FG32FBpz4S1SIeq8DAz9OI+XuCoXd2Ol
 FA6oSepyBxG1Cz2dzhkobE3COPzwS6jRzPdsmZtkJ1Lp/t7w0FSMlOYqNkdD9OCb
 OxraGoL4PfoPgCsH80dY/On7e8COQs6rRPTOmx+FGqkdEaNXVyF8A7EoIUNi881j
 Cn82QjfR4pwFJ4KNeJRt+kBVE2j//VmsqlMcc1xBPzSwcO2YaURhF90qB9ql+bZx
 ENkoYgqdbkQwcPugdKJm4GzaX7OhdGprjH/E7Yj7fFmXhE2VsyQ8heGjKrRHgy/g
 4mTYKTTJnYHSXO+MThJ6JPwcgHxUiEkEGBECAAkFAkamZvMCGwwACgkQM4TrQ4qf
 ROMFAgCfYpxRT6ReISfiSqGLMBQndCh2ol0Anie8hp/BanOvY2jOiUUcfvyhIqrZ
 =bQIC
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.254. Anders Nordby <anders@FreeBSD.org>

 pub  1024D/00835956 2000-08-13 Anders Nordby <anders@fix.no>
      Key fingerprint = 1E0F C53C D8DF 6A8F EAAD  19C5 D12A BC9F 0083 5956
 uid                            Anders Nordby <anders@FreeBSD.org>
 sub  2048g/4B160901 2000-08-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDmXNAsRBAD0WcmPy11DRvDsEpadBPCATmPrvAImfj5XjcxBAJlBJoc9fiq4
 8OcnipVdId6STdVKvB3K3h9aNsb75+rD/W3nMi8MumjyXJoHAf8d68cnjppizcPd
 uQPOy76lkbiyV9OYBtaNQqmU8hE8MTr5Kew9NBCoC4SB4NX8kVh8iglrZwCg8J4F
 ltBYDz+Z5ZGoh54fnYN6IAED/jO7ISCvWbFtnzCw1FOghcgueqrWoy0OYKq8ZfuO
 m046fuIlHcswJOKLLexTajsYAC0WWe9H3SvKvv1etexMh5SsrgWTsSuIvlPfG4oj
 D5vIYqvH5NiqJdh9qiFEzGsv44jgESDVy9qaErbXRVe9htuRZqbtEPnB5cRRwTr1
 WhfuBADW1VLXj3UGw4OeBBd5KPIYXCx7RKS4nfrlBCqMcIaiD+K42U+7PXEJB8uM
 2sJ6uRYs0j4tTLBbDC2TC1QfT5NIVLG5wWkIh+jL7PODH+i4LF8n0pQyuLwJOFAx
 s6RIHNPB2fdI5sqB9lMIBszlb896wVJf9PPWFAt/5Aekw7eTLbQiQW5kZXJzIE5v
 cmRieSA8YW5kZXJzQEZyZWVCU0Qub3JnPohXBBMRAgAXBQI76xZsBQsHCgMEAxUD
 AgMWAgECF4AACgkQ0Sq8nwCDWVZnYgCg4fzk40pYLg3iNayO9dDNp4yHS/MAoLi/
 WCYhNOS0TMpap9SQXC/2e0MZtB1BbmRlcnMgTm9yZGJ5IDxhbmRlcnNAZml4Lm5v
 PohXBBMRAgAXBQI76xekBQsHCgMEAxUDAgMWAgECF4AACgkQ0Sq8nwCDWVaoNACd
 HR57Uuyyti+OqVr4zaVEIgg+bYwAoMcFR3xdqArQmp561541p+k1IBUWuQINBDmX
 NGsQCADRkDqg2uW9mn5YCXlzx9KlhAfPRny6kF4+B+ga0ZaIzJng2pY8EsAxKn88
 yH6ERs/PYdsy/AyksG8vzuc9CalW8JFEc+kvtJIL0HhBonlInaeUWHPixGEcOPcW
 ab8dPhW3zfEgOqquky21d8Zg+G3Z29tmKGcYKSQgt6W59z7vITK7+gv7tOGp2IpZ
 1kGqPZn+JqvB3n/uWo3rTxOGA/tduMwfESA5gHmEzKmU/17yIkE0SflKOp0VIGdl
 Fp1A1ULJDDVXjtDkxFvZ1I+WpqF7p9FCgy/OHUfUa0py3uHIEKMahqpAZ9e8D+GI
 nGizPR33ZY5PfM72ABXeGhFnweP/AAQNB/9HPBzxoJJFJNLyosSlI+Wkmh51K/nC
 EawQG6a+tgL6cPHgJQkgthPUywkI+2g7SUSurgPz0hRCPg2PjHP3PwVhjKzUgfAj
 y9eVnu+JSpst/a0Y5LEQdNnwG+Y+Cs0q9xj4T1VXw8B9fA3y1wS1a13zCQjfLrZP
 ziIGjHIBvpOFrSU3ML1rRaVfQpm2wQXsGHzjkaZq7HQy2EOVLzik34XkPBY1DrnY
 nSEwSurfjTrKTLNYsN53xCGwJ2w2347qXr04j87XhRmGCJQ/Nrrin4z4LQ/zNm5Z
 bErlts8PAfR13kqP7rx/H1n5obhpOoXUqb4Rm94c0r/s9JRah9ppgADRiEYEGBEC
 AAYFAjmXNGsACgkQ0Sq8nwCDWVbTvwCcCG0X50Tq7V4NeGgREttltmR7UlYAoOgK
 1OFsIdCCq6JjrwvfN7ry3pwc
 =clge
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.255. Michael Nottebrock <lofi@FreeBSD.org>

 pub  1024D/6B2974B0 2002-06-06 Michael Nottebrock <michaelnottebrock@gmx.net>
      Key fingerprint = 1079 3C72 0726 F300 B8EC  60F9 5E17 3AF1 6B29 74B0
 uid                            Michael Nottebrock <lofi@freebsd.org>
 uid                            Michael Nottebrock <lofi@tigress.com>
 uid                            Michael Nottebrock <lofi@lofi.dyndns.org>
 uid                            Michael Nottebrock <michaelnottebrock@web.de>
 uid                            Michael Nottebrock <michaelnottebrock@meitner.wh.uni-dortmund.de>
 sub  1024g/EF652E04 2002-06-06 [expires: 2004-06-15]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBDz/lNYRBAD6n1LJ1BQMhRrjVBC4JQVBh6PBBM1cdbhOMyMgX5G4wacsb6CH
 bNY9UAPAp7Gfx9GPPQkMsQiMSuLCaklFfnlyqmJV0xsXx+P5eUodc8x5OtokTWKF
 gux+FSGQNKC9hEkWAOpqPN8y89RHgk7S8epyqImmVh7jVqc5I36A6/nyNwCgrB3H
 bvi4Drig8zKzYc1DRFpOE+0D/2rL1DP4ri8w9VCTn7VfJ/uP2erRQsfZDkYbu3HN
 eUEBR2zr4QR538mY5IlKis87+noYOVvgaFBfVa/eQD3xVEzy0mNhErSQK75+im0U
 rAdF3CDEAbt/nGwbuh24KcaOyqQpaNBxvzDNdICADSYpsNj4sLz0jlxLpEHPFx3T
 HQzvBACSHzXKnkb9k8aePTUJQXKcml5mCDQJPR6u6rYK8pe9TOEmLA4w4FOgbXae
 cPNYv8nLKtuyjehVTzvV+4ktuMPXsF1Y8SrmexJWsiLO/TF2pYDXMjB7LaIGTK5r
 cVdArpC6ocMfACIWtCYZQ1TIKDbyZ0uyfPQmj5uc1lFkTDzX07QlTWljaGFlbCBO
 b3R0ZWJyb2NrIDxsb2ZpQGZyZWVic2Qub3JnPohlBBMRAgAlBQI/Gm4SAhsDBQkD
 z34yBwsJCAcDAgEDFQIDAxYCAQIeAQIXgAAKCRBeFzrxayl0sKI8AJ41OXMiupy5
 Rsdvi0g79QRxn3A+QQCfSlp7i/ilZ0HsY53FZVvEesAzljO0Lk1pY2hhZWwgTm90
 dGVicm9jayA8bWljaGFlbG5vdHRlYnJvY2tAZ214Lm5ldD6IRgQQEQIABgUCPUHt
 HwAKCRAqx4djq0R7TjsLAKC2+xaNwzlmPOiciH3r2UMXWelSSQCgjp1Ccn7KKZU8
 JbJKeblYOd5mdBqITAQREQIADAUCPtf6PgWDAdeSEAAKCRB2rO4B/qKj/iLEAJ47
 RPw/TfOBwTi/Twy4bLQ1/ESs+wCcDr6yapPrSalhl2/ZTcYNA5/QtBiIaAQTEQIA
 KAIbAwcLCQgHAwIBAxUCAwMWAgECHgECF4AFCQPPfjIFAj8abm8CGQEACgkQXhc6
 8WspdLAzYwCcCQhe30GiQE1/wJOKFsNCojh549YAnjEOaKibthqelUfOxfM0aNjg
 yi0eiGwEERECAC0FAj7vBPwFgwHgDgwgGmh0dHA6Ly93d3cudG9laG9sZC5jb20v
 cm9ib3RjYS8ACgkQEFgWhcUhCX6ecQCXaLPLqW22Nsr8rtBzJgYSMStJVwCggirL
 XuYNu9sTSrMPZvZrIonU1T2IRgQREQIABgUCPu8rOAAKCRBLKkiX052g47mvAJ0e
 D22tcuXsxh7kxJt1M3k+HK3zkwCfZ5Gp7XT1/5QwTxz1/qBw9+/DK5S0JU1pY2hh
 ZWwgTm90dGVicm9jayA8bG9maUB0aWdyZXNzLmNvbT6IRgQQEQIABgUCPUHtJwAK
 CRAqx4djq0R7TvSMAKCvUNGMzBNDxh/ud0bsd+Q5s1NgNACfbbIyqyv0SRXQaBVG
 EZOV/IqXwxSIZQQTEQIAJQIbAwcLCQgHAwIBAxUCAwMWAgECHgECF4AFAj7t34gF
 CQPPfjIACgkQXhc68WspdLAD2gCgnT7aSz8Xl5xcPsNmionCS8ydPx8AoJEeYBT3
 JV7fbVpniGBaDhxwPfJFiG0EERECAC0FAj7vBPIFgwHgDhYgGmh0dHA6Ly93d3cu
 dG9laG9sZC5jb20vcm9ib3RjYS8ACgkQEFgWhcUhCX5cdwCdFVRkxIwY2e8UBlFD
 0ZHphsssjOwAn0t3+rPg5PQLRxGkOUn+0xbUhTgYtClNaWNoYWVsIE5vdHRlYnJv
 Y2sgPGxvZmlAbG9maS5keW5kbnMub3JnPohGBBARAgAGBQI9Qe0nAAoJECrHh2Or
 RHtOGWgAn17Mh/ojUaq2wypC7Lgxk2aD7ZbwAJ9TNFfNY+tUb32LNUCrxe5hdfyS
 C4hlBBMRAgAlAhsDBwsJCAcDAgEDFQIDAxYCAQIeAQIXgAUCPu3fiAUJA89+MgAK
 CRBeFzrxayl0sFpNAJ91EregVsaf77emPMy2tU0r7TBWeACfau/Nv9ZgZSBWSG13
 AllSOYqbIUmIbQQREQIALQUCPu8E6AWDAeAOICAaaHR0cDovL3d3dy50b2Vob2xk
 LmNvbS9yb2JvdGNhLwAKCRAQWBaFxSEJfmJ9AKCo2zsgoH6naSKd3Rduo+7hfM7Y
 uACeO4R4dZBZNEPbaZPcBEaRrMW+4um0LU1pY2hhZWwgTm90dGVicm9jayA8bWlj
 aGFlbG5vdHRlYnJvY2tAd2ViLmRlPohGBBARAgAGBQI9Qe0nAAoJECrHh2OrRHtO
 vW8AoIuikn8ryz7dgs1TjnOgrXQekbpnAJ4mnjfM38IzIRiwYR1iljvkIFv9iIhl
 BBMRAgAlAhsDBwsJCAcDAgEDFQIDAxYCAQIeAQIXgAUCPu3fiAUJA89+MgAKCRBe
 Fzrxayl0sOG4AKCAoTHv/Nzk/fcSTiQWLxEKn2yYRwCeJjnKO5xs7Oj5nTg1BuGC
 J9kjTx+IbQQREQIALQUCPu8E3gWDAeAOKiAaaHR0cDovL3d3dy50b2Vob2xkLmNv
 bS9yb2JvdGNhLwAKCRAQWBaFxSEJfq8nAJsFK6NX9COUfRYJrkePGeSpUeVQcACe
 JoiaiD4BClMnupSxHIe6FJmHyK60QU1pY2hhZWwgTm90dGVicm9jayA8bWljaGFl
 bG5vdHRlYnJvY2tAbWVpdG5lci53aC51bmktZG9ydG11bmQuZGU+iEwEExECAAwF
 Aj7hnCoFgwHN8CQACgkQKseHY6tEe07xqwCglAxylGcu7GsXoz6OS+U+QNUbWL0A
 oPui61DotXxm/VZvblBBToTr4KwOiGUEExECACUCGwMHCwkIBwMCAQMVAgMDFgIB
 Ah4BAheABQI+7d+IBQkDz34yAAoJEF4XOvFrKXSwJAUAnA5LnR/voJz2mnP1Tkl4
 5khGcQSLAJ0QSEFiXOemfKbS4FsKF2a49Pa7W4hsBBERAgAtBQI+7wTUBYMB4A40
 IBpodHRwOi8vd3d3LnRvZWhvbGQuY29tL3JvYm90Y2EvAAoJEBBYFoXFIQl+rzEA
 l3vk3WJrq+S26dWPl1wGXyFjtS4AnRJSpjM6Ua7eAfS8Pfdk+UsfXJmAuQENBDz/
 lNcQBACS3xasZ+RNnFwCK+sXnnXQYbkHUsW/BTcUaTk6eyaEsSb/lTdz8uyJ/8ao
 xSuPr87ZEDaVFth5tEbFfJUd9DOYwt0QFRK65hqzY1MOIIiDiVUW8dVsdcZfokom
 r9RElz9VQre7vJwaSW1aEsYTvMZC9D9MNiPrW6oHjxUvWIlmPwADBQP/UYgPqe0t
 SYEJnnew99CSIGDMozRakmwHK5bH7bUkaFk3PSpk3a3EAqE9bmQI/a1SKBSCDdAU
 0Iev5UXbTbYF+0f+36UQqLxZIPb9hVU/ExjJnf056iFSprfYnJY1hVTR9kT67c8Q
 9fGK3L1CNVn2EF+UJOrtWcccUfE84lJ0aoyITAQYEQIADAUCPu3flgUJA89+PwAK
 CRBeFzrxayl0sChVAJ0RTya/2yxHW7j7mV0aTgCw3bixpwCfV2KBo9ZKGn5pojA8
 isNkDxI+R1w=
 =LE25
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.256. David O'Brien <obrien@FreeBSD.org>

 pub  1024R/34F9F9D5 1995-04-23 David E. O'Brien <defunct - obrien@Sea.Legent.com>
      Key fingerprint = B7 4D 3E E9 11 39 5F A3  90 76 5D 69 58 D9 98 7A
 uid                            David E. O'Brien <obrien@NUXI.com>
 uid                            deobrien@ucdavis.edu
 uid                            David E. O'Brien <whois Do38>
 uid                            David E. O'Brien <obrien@FreeBSD.org>
 uid                            David E. O'Brien <dobrien@seas.gwu.edu>
 uid                            David E. O'Brien <obrien@cs.ucdavis.edu>
 uid                            David E. O'Brien <defunct - obrien@media.sra.com>
 uid                            David E. O'Brien <obrien@elsewhere.roanoke.va.us>
 uid                            David E. O'Brien <obrien@Nuxi.com>

 pub  1024D/7F9A9BA2 1998-06-10 "David E. O'Brien" <obrien@cs.ucdavis.edu>
      Key fingerprint = 02FD 495F D03C 9AF2 5DB7  F496 6FC8 DABD 7F9A 9BA2
 uid                            "David E. O'Brien" <obrien@NUXI.com>
 uid                            "David E. O'Brien" <obrien@FreeBSD.org>
 sub  3072g/BA32C20D 1998-06-10

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 11022 characters]
 lSVmAKDF3kyQAZDAyz+21MQJnmJ2O5dFJg==
 =cMCa
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.257. Jimmy Olgeni <olgeni@FreeBSD.org>

 pub   2048R/6450AE47 2012-11-01
       Key fingerprint = 7133 AB4D DFC8 0A0D F891  B0D2 90B7 A98E 6450 AE47
 uid                  Giacomo Olgeni <olgeni@olgeni.com>
 uid                  Jimmy Olgeni <olgeni@FreeBSD.org>
 uid                  Giacomo Olgeni <olgeni@moviereading.com>
 uid                  Giacomo Olgeni <olgeni@unimaccess.com>
 uid                  Giacomo Olgeni <olgeni@colby.it>
 uid                  Giacomo Olgeni <olgeni@colby.eu>
 uid                  Giacomo Olgeni <olgeni@colby.tv>
 sub   2048R/1988BB4B 2012-11-01

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 4488 characters]
 F9RpaqHRxeuchYZH3JlhZ4NLHKYCMm9vwnBDpa61tH8I
 =1fdp
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.258. Philip Paeps <philip@FreeBSD.org>

 pub   4096R/C5D34D05 2006-10-22
       Key fingerprint = 356B AE02 4763 F739 2FA2  E438 2649 E628 C5D3 4D05
 uid                  Philip Paeps <philip@paeps.cx>
 uid                  Philip Paeps <philip@nixsys.be>
 uid                  Philip Paeps <philip@fosdem.org>
 uid                  Philip Paeps <philip@freebsd.org>
 uid                  Philip Paeps <philip@pub.telenet.be>
 sub   1024D/035EFC58 2006-10-22 [expires: 2010-10-13]
 sub   2048g/6E5FD7D6 2006-10-22 [expires: 2010-10-14]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 176418 characters]
 Vxk4GMyfzQpi9Sd1ZvWLZupmKm6i70IoKxfppi/HNF3fVt4u
 =srgn
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.259. Josh Paetzel <jpaetzel@FreeBSD.org>

 pub   2048D/F6F63F01 2012-09-21
       Key fingerprint = 1D8D 506E B58C BD10 DC8C  97E1 D6AD 8621 F6F6 3F01
 uid                  Josh Paetzel <josh@tcbug.org>
 uid                  Josh Paetzel <josh@ixsystems.com>
 uid                  Josh Paetzel <jpaetzel@FreeBSD.org>
 sub   2048R/F32EF801 2012-09-21
 sub   2048R/51F1335D 2012-09-21
 sub   2048g/9BC280CD 2012-09-21
 sub   2048g/CC793500 2012-09-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 7854 characters]
 Nl2zzZmlpV4i
 =ExWp
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.260. Gabor Pali <pgj@FreeBSD.org>

 pub   1024D/9E3F9BE6 2008-04-17 [expires: 2013-04-16]
       Key fingerprint = DA0B 2143 0FC8 EE5F E211  D329 7D4B 6E18 9E3F 9BE6
 uid                  Gabor PALI <pgj@FreeBSD.org>
 uid                  PALI Gabor Janos <pali.gabor@gmail.com>
 sub   2048g/A780C60B 2008-04-17 [expires: 2013-04-16]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEgGzt8RBADdmkWC/Q4tpLhYpw9oidgWjyRRx/MgPRrGhtAvVdNTjbVoT4bl
 5e+v3CHoBih7KIh0BVQrux+H4UJ1Fou1wwwCrPH6ismBR5P9iZEGmBR/K0+1gBph
 /aUBANM1QG1FpAKMsYytqXiNk7mH/+oxomsbXBg8ZFGzlOWCwp3gvMZBGwCg7UY8
 YtV9L46nZMFIfzlj/tkNzh8EAMeF8nLv2qFsBT3ihYJRb27c/GtsnSUCQgwU5CVS
 Zx0QVb/zpy0syLHO+AeJnUIQWBKOhPpysXRlyMpjDlPu2b/VS9av01uLeHCCR9YE
 G/Jp4mCNswD0RLoQh0WrNtdr0kR0htr8mZrkRbZo+YoZPCdp/lD5JNq6fkS/Dgc+
 OGBsBACIOunHi0iEMnThJNznfLSA4hmjSdkrI249U5Ie8KfA5aXxaCX5o68tMgUV
 s/9hUBIc9cKoAkUf8t1XEADTik544HYm9FNULU55K1yEoG6dQrVm1HYVSl7uklE2
 mHkkg15nqapedChp2a+UhXYK4IthrBYcI4YVvQMBsMIFvo63krQqUMOBTEkgR8Oh
 Ym9yIErDoW5vcyA8cGFsaS5nYWJvckBnbWFpbC5jb20+iGYEExECACYFAkgG0YIC
 GyMFCQlmAYAGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRB9S24Ynj+b5rQSAKCs
 f7zv5XU0wXzKF9Y/9kIH2CKg2ACcDIvhQGclbBZy1NWr96IEkesPVd20HEdhYm9y
 IFBBTEkgPHBnakBGcmVlQlNELm9yZz6IaQQTEQIAKQIbIwUJCWYBgAYLCQgHAwIE
 FQIIAwQWAgMBAh4BAheABQJIBtGPAhkBAAoJEH1LbhieP5vmlK8An3aLBPTXu/f0
 dWAovygPqgvjreGXAKDUrndv2PP84EhK4f4HDDwfeIVyPbkCDQRIBs7fEAgAyLRw
 XdnvIKENQFgcjI2XyPtcbe+mCs2miAdRWKPRq+RuVLu7ub1kYK13W9pYTJL5LAiF
 TBVm31uuoiN/sQaJMDz/Hz2DOLRsEcb+d5f/9ssiPUxMdYKnE+kYwXRvm15y6Z6G
 dNhFZWleNpFRuPYqy/HaUb5q8/quF5VcH/cDVS1tSTErPtM7i3mmnJOpdIdBrCPe
 VVJXZo5MWUp1wG2IIuyap8ddM5S/kHhhyujLxLNDnlTxYogGZz0qad/R3LeiYTfl
 Drn9cZzvFdPlmrSvdw78RH0tB09fRLoI8KjGHi/bTiF9Pai75OUwVMv4PmxjAF6s
 OLU9q8zGpr8XE2ykwwADBQf/XVmkCPL+BRd45e40ayCo4sqfMoh0mK6dP66FmO90
 tAHtlIfkK74mcb/XrHC0KoX7c/TSaG9C8uJ7NGYzEFQzlzY8LlAfW/P+LjIpXjk5
 frEItGm0fCNU/+eBwcobO9gfWHDHucfocar8/pnot2PhwJpRFy1/xUa8oHXxNfW5
 IXnb67uCDPl4xFy9GkPPsgFZ4QI9+S7do0XYDEwfvzELeNTANAzMK+jIs5yzJ7mB
 mwI9orFltPfmc1y/EVc08LlR7qCsbosb/HMHO3jaMeKq1NIHyzRd70RZn5ow4B0Z
 zPQTJCWzfM0L5vAF96N/Rmrigwsg83+dE/a5e2791WRCRIhPBBgRAgAPBQJIBs7f
 AhsMBQkJZgGAAAoJEH1LbhieP5vmWAMAn2t7GwTeP9Hq3t1I1uU8AUGgS47cAJ0Q
 0CAkpRuxhi2FZn58aNBhvQPcog==
 =JvPF
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.261. Hiten Pandya <hmp@FreeBSD.org>

 pub  1024D/938CACA8 2004-02-13 Hiten Pandya (FreeBSD) <hmp@FreeBSD.org>
      Key fingerprint = 84EB C75E C75A 50ED 304E  E446 D974 7842 938C ACA8
 uid                            Hiten Pandya <hmp@backplane.com>
 sub  2048g/783874B5 2004-02-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEAscLQRBADERe+RX2eJpYLoaJ7d29B8YcTYzNlsfzghM1R1/Dx2RDy5poKa
 Jn9j+Iptq1qS9GkTHXFcQh8LT2K7wnE/MZTCxkZvg2ZkfQbJ4Z+0z3A1A6Kvg0tH
 X5aqmPUeLXvnps7nqZxkhl2ibcjhH/VYZK3mdRikd1wtJD1EhbbeqaR8BwCgkQAG
 vdJHN9gfjLLcM12EitkjoUcEALoo1bPoULWd4YhVH7W5L3Qp0dr1vf5pYC/V7FQ+
 8yPXZtGzMvIld8iX1sv/zsw4EoXXsaRzJo/ixdCS1WYBPowryu0G/LX5w0RTTGHc
 ihcHLm6ZmyNuIsTQ1ifLNASJoLkNBlQAuA0VG4evAujrmaWyEHbbIDSQKUJOjL9u
 jb2HA/9pycrr3+735Aa7B5jThN6p1XEC8GQg5MDx23QnTPj9QHXH4qs7s+hwxZq9
 3WkVFBcJtDBi8PeEVqfD/QPeU3ewbnNnfaF46miGV1iG1mzU4zMq4n5oBdijf5eL
 cRRdOJytYKTvlSCe8gf0MzfaB3RqD8+Cjcs3PtQOy1VT4aQiv7QgSGl0ZW4gUGFu
 ZHlhIDxobXBAYmFja3BsYW5lLmNvbT6IXgQTEQIAHgUCQCxw7AIbAwYLCQgHAwID
 FQIDAxYCAQIeAQIXgAAKCRDZdHhCk4ysqEPZAJ9ByMndfTtnnVIbsyHc2NjDp5F/
 vgCeP6o87Lw4aHuGo5guA9yeWwtwAla0KEhpdGVuIFBhbmR5YSAoRnJlZUJTRCkg
 PGhtcEBGcmVlQlNELm9yZz6IYQQTEQIAIQIbAwYLCQgHAwIDFQIDAxYCAQIeAQIX
 gAUCQCxxDgIZAQAKCRDZdHhCk4ysqLchAJ4+01/uQVdqdDeESGodcvgKsrieqACb
 BIW7HMvh85WqofTeAK5pJu7hCM25Ag0EQCxw2BAIAPXEkkg6lSxGRmVH1yzRnSKr
 /M48xyRXYDrRPaVVBFkC4Af3CR5MjncJtjbzm7xH82glC67cksRTfTZRs7kJsid+
 g62V53dAu1Uoj8ecSDhblb8yW3rTLKVqGcliGcTRFivcm+ZFm0kc0xCQE3rd1COX
 NLEomMV6xuZ9PVzDAbJwAoGdpCYsCl09eZrTErueQ7pEVsLx9/0zQSmC/uDFEVZ7
 23GsJg23+EUBT5KuTxQ4i0k++Ccr4HR/OiUy6KmyXSNsKsBsXwm3map3Debqqqx1
 ssrDXa+PHkKEUrONQBoYbZ17DpPZb+NKWibi0Vp1HKPP2vZl4NZQC0GBLXbEudMA
 AwYIAOYhwVTWKQSgeEZUNe4PwvHczx8/3VNjYZGY6/ZRjgmfO3+MagjonZqfxYha
 GpsEV17NXm4WIg6HWtI43JwIWfkUybsdxQVH4i5lWYuA26wD6UtNXw9laPHKXonR
 DvmKDC6K0iFbSxTqXRZVQ//wMxh58/Yw/fX+fYtmH6u6kPaL+CPRkhQLezTzZWHj
 2wF6v+frdglW1/LpwpCFndb1i5+36ogZ5ZudG/iz53QzlOF0IZSGHIb9tlQ+4gUn
 KfxpQloI+5vAyqpHDKIH9K26wTBzKsp5Mt4W6cLfgjXs7TNc8BVT8d4rmmbGpGnG
 pSjj7b1q6EhpIVBkAMLw7qanLlCISQQYEQIACQUCQCxw2AIbDAAKCRDZdHhCk4ys
 qAuZAJ0VNEtJSZOAGetxBJ/BMWahVD8xeQCfVKwTHdPh83Qcf28xx81icY5OKY0=
 =rF4D
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.262. Dima Panov <fluffy@FreeBSD.org>

 pub   1024D/93E3B018 2006-11-08
       Key fingerprint = C73E 2B72 1FFD 61BD E206  1234 A626 76ED 93E3 B018
 uid                  Dima Panov (FreeBSD.ORG Committer) <fluffy@FreeBSD.ORG>
 uid                  Dima Panov (at home) <Fluffy@Fluffy.Khv.RU>
 uid                  Dima Panov (at home) <fluffy.khv@gmail.com>
 sub   2048g/89047419 2006-11-08

 pub   4096R/D5398F29 2009-08-09
       Key fingerprint = 2D30 2CCB 9984 130C 6F87  BAFC FB8B A09D D539 8F29
 uid                  Dima Panov (FreeBSD.ORG Committer) <fluffy@FreeBSD.ORG>
 uid                  Dima Panov (at Home) <fluffy@Fluffy.Khv.RU>
 uid                  Dima Panov (at GMail) <fluffy.khv@gmail.com>
 sub   4096R/915A7785 2009-08-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 6732 characters]
 gvGn3mxLairK5wBG/6nAxa+uon8t9tl7FKwiMg==
 =Jlk7
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.263. Andrew Pantyukhin <sat@FreeBSD.org>

 pub   1024D/6F38A569 2006-05-06
       Key fingerprint = 4E94 994A C2EF CB86 C144  3B04 3381 67C0 6F38 A569
 uid                  Andrew Pantyukhin <infofarmer@gubkin.ru>
 uid                  Andrew Pantyukhin <sat@FreeBSD.org>
 uid                  Andrew Pantyukhin <infofarmer@gmail.com>
 uid                  Andrew Pantyukhin <infofarmer@mail.ru>
 sub   2048g/5BD4D469 2006-05-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBERdJJkRBACMPYQjOqisztbRuKcG254kVS+eoBqWqFKY98x03KtgEYn2/Em2
 EU4sPfhr1PYabCT5oxmaIhmBRuwryM2V/Py4Gl+dfJ4+cmRt9/LXQPyWymSlCXj6
 U5mTqCeOId45PWU4lis44vN7DgAKZptu5GoUAWxnfh7M/K0UQGU/MNOPSwCgnt26
 U60GErf8Fao0V31YPjRJko8D/1F7m5LNW9zzEMF3WFQURluoOxrmaAnehfYA+HgX
 kcM5t0SZFnsdOCbsKLMxl1E9qgbF9mAwTU2MfJFNhEuCUWZlYs7a69XSbr9HgI7p
 cqeHFhpbKTfWT65bJ863jnsMwS9/mRHNka5CeNFh2Pz06mzV3JherOQIq3lcBAri
 TnaEA/4st0qZe6VawiZgGgGbamLtS/iUMxhmC0SAv/pdYVieeXmXi0E3b1mA39Mi
 oRvFL3gT24UsVEaazwcwqnnifOqlApCGubSitYM+OPa2DyoYDUoCP0A9DgohSrRr
 /+yCES6zTQOv5fV6DoX8tvEQ+2+3DictO2FLuqUC5joBu1+42bQjQW5kcmV3IFBh
 bnR5dWtoaW4gPHNhdEBGcmVlQlNELm9yZz6IYAQTEQIAIAUCRF0kmQIbAwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJEDOBZ8BvOKVp4HwAoJZ1Z1SB73vCYs9cxyuP
 mhVV47b2AJ410LsvceMdtc+g7LZ5Qm6jHNmCaLQoQW5kcmV3IFBhbnR5dWtoaW4g
 PGluZm9mYXJtZXJAZ21haWwuY29tPohgBBMRAgAgBQJEXSYbAhsDBgsJCAcDAgQV
 AggDBBYCAwECHgECF4AACgkQM4FnwG84pWnW1ACfV2rsfdxtJkFxl3xClNRoTZm9
 llwAniiNDnbJXOjId704Scb/LDYymESptCZBbmRyZXcgUGFudHl1a2hpbiA8aW5m
 b2Zhcm1lckBtYWlsLnJ1PohgBBMRAgAgBQJEXSbFAhsDBgsJCAcDAgQVAggDBBYC
 AwECHgECF4AACgkQM4FnwG84pWnbLACfQ5S3OAPZEJj/7zb3z3Xr/1AP4PYAn3LF
 f/4tcV8P5NZw0wxqYUMmWtHstChBbmRyZXcgUGFudHl1a2hpbiA8aW5mb2Zhcm1l
 ckBndWJraW4ucnU+iGAEExECACAFAkRdJxQCGwMGCwkIBwMCBBUCCAMEFgIDAQIe
 AQIXgAAKCRAzgWfAbzilaVj1AKCZyDzhFFyymsLh7ykuQLQnLPy55wCePzG4LA7y
 mwPr3zKG/6BTOql0t5y5Ag0ERF0knRAIAMGIx2+t+/Q6AEVLhSeQ1WHUBbjsuVDB
 qMT4RZaiMq/UA2QSWFTuqylpV6rlvLR3d54MOvn3hlgj6zzEnoIj2WLFFtcJzVuF
 VbrBRLCjDgAOC75Kt1LJEOIcJwyZ9c5gGau4Ng8zyYkbYBJ3qmhtnjF1+m39uRc3
 +4CPRdlLTa0Dc0cbQ/hEE1VzWwXM61oxWKwHBk2hluv4AAhzjrenT9yUqmemc/fA
 U53feBIZrWNS7dzyL/L+jc516vHkvhNeHqyzZcmLktXshgfeLTe3qDsXnt+F3qr+
 4M+nTfkATdRQvSfs12KNAke76Bx6mjArNXh/sazc1nr4SJgZQ53b/dcAAwUH/AqU
 YZNJzrMDW1JBJtGvjo41T46WcXjw7pHQvzciOuYRVsclc2reXEHa8aZ62Q1LsThz
 d12lm47R8NQcMO8n+avrIuomuBooANf6QruKf8MMFlRGxs9Gryu+839NadbZHRsk
 NcfJG35WiKMksl6MSfMxSdhl0BhBk4pgPPJT1t+FY7yDf+N4DgCaDuRnXnTLPrxp
 LukXPTCtXjostVQ1Mv0kcTtnUu9yGeoBNhpUWQrOy5CI1Vqp8K0xMDbRojDSRni7
 zl9gfnzxO5V47llfhoNTEjLsZZ/8n3Od6KRMMUTgClRFe2la42u+R0CDAIRkNkI+
 WCPc8mM1TsGgw43LxnKISQQYEQIACQUCRF0knQIbDAAKCRAzgWfAbzilaRRRAJ9R
 iYtTvkXAj78Xt8J5FMOoiCo6TQCdGj7U+SJHD3NDwqmkvfMc7Vp/iqs=
 =47um
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.264. Navdeep Parhar <np@FreeBSD.org>

 pub   1024D/ACAB8812 2009-06-08
       Key fingerprint = C897 7AFB AFC0 4DA9 7B76  D991 CAB2 2B93 ACAB 8812
 uid                  Navdeep Parhar <np@FreeBSD.org>
 sub   2048g/AB61D2DC 2009-06-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEosaGcRBACOXnXquGEW53BjpMt2jViod/TUf1xgjMekcbDxqOODPeX7eYfr
 wJ8G6BCNOpGjBmWDu/JcNj4Z+gmTilJ6WLZQ7ecFZfEeO91pt6ys0cyWh0xfO+/m
 T83D7W81S/kqrJBkQbBIdV6LumevdErHo272r8RcMELC4Ru87eRtX3hmEwCgnnGN
 JMpQFUfYTt5XE7nY0yQoeV8D/0OcWmJbEZWxX9O7AuliCe3zd2Dw0B4LB9SZ2Dis
 7+gpVd3xVgYnt5wRE9kM+ThgrMA/wqr807qmEG6bcfUsfwwGN9YUtNF3xAN07cXT
 s026sCIFNZK816PrThBzCgkwR7pDpkMzGWIBr8WiXXy0eB+JlQ6UV4PEiXuZ5ulz
 P0b1A/9CZm3wJfrNC0r1gMyrfVedg4zwKU997bmPLGcYs+rWXDTI9CvMseOUYn4C
 oDZQCp/9zxuHK+VU7Y/w0c/hVE5ERACSn4SjN2unEDstK9njZBMHEPVkAe/YvSG5
 cmc97SHlVE+eu/bbLKcvFb6rRLPOaVFQJMJA2VJEGWtYhvP7ZbQfTmF2ZGVlcCBQ
 YXJoYXIgPG5wQEZyZWVCU0Qub3JnPohgBBMRAgAgBQJKLGhnAhsDBgsJCAcDAgQV
 AggDBBYCAwECHgECF4AACgkQyrIrk6yriBL0MQCfUJOiS2PbJFDeiav1ylcXXwfp
 ggAAoJRoS7GDENGyM4BzjJ4b0ptZqTLRuQINBEosaGcQCACFCWs47SL4DQA6bNDl
 VJu4w8wLf8uVOyatuGmdXX8Y/OTVQJgA3vS+ODNVJCxhKVlvhcn7bhBdGdWKS9K+
 lr8+eEvr4hf2bQpesoHC+uFgKyILkCBNL8raixbhysyq0pfZWWDJMyn+G42BG1yJ
 Ji+bykygdpYnbIVA8dYHmBibI8mkPKOHSohjXT1SRfGGn+l1w54OO4NlJhCXMkjT
 A/Z9Bt4XeaiR85uJi0UUfV8FGZHhgSvT+/P1xIvz+nytuehSP/QLXl13CtAG/nKV
 kAcZnsT/3NrJ4Z2r45k+c50Wrf210scAaBogrrV5eIHfNGgOANApN8+8vj+aXO4p
 XRuXAAMFB/44ea8rd+P5N3OMrfuM8i91Qe1bJ+BIoroKPOr8jvCry0h3QpdfLKUN
 IgaqbS3JZeBJ8HHnWSGCF+o6H5gzRe1hvylPEclLPDCuPe7T746h9Mzejf2hNDJv
 Og+BuweDZW4KhovVbdS+syJEvpGF4bO8qgHT2CKgruXSHbFetdQWbkM0rfMmTuo0
 GcR2BEVrPb/SPFv64ZZyAZzmnGO4vT1bzClnTzJixrDpH74M3vSEYegMB4KdbLYB
 i8Jx4QUKgVEhJHjJubKWX4etyU/uuehOC3xYrmr1UXvsom3U8r36Dvdo77Yr3dgD
 VXa7bolNx0TIhdWxZI+R4z9E75QY+/wgiEkEGBECAAkFAkosaGcCGwwACgkQyrIr
 k6yriBI+JQCfUxgyqGtzZvLh5Al7gsTmRc11PLwAniD3NfWGRcO2+9uxSSQqRH1y
 wC4n
 =tqY8
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.265. Rui Paulo <rpaulo@FreeBSD.org>

 pub   4096R/39CB4153 2010-02-03
       Key fingerprint = ABE8 8465 DE8F F04D E9C8  3FF6 AF89 B2E6 39CB 4153
 uid                  Rui Paulo <rpaulo@FreeBSD.org>
 uid                  Rui Paulo <rpaulo@gmail.com>
 sub   4096R/F87D2F34 2010-02-03

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBEtpXcMBEADA2Fye/cDy2Tiay+ieM9avchk+igtnLNdmHv+07rHP4OMXfJ2D
 HcAl0+Mbehs7vLQBKvpIFXJAE4z2JAaLw16g/o8AUEO0/tchFy+RGjqxzwrY6Xv8
 ur3+lyezJ/Xs34yQb7h+m2i7gxp2lXsk15zc/V3bJ3EGnTPAxTD0/UGT5UMBSK8a
 TVH/YTvYuAoQ162qtjrfdSWgO83+mJHtyO52asF6Jcv4PxTc1KjPNJ4CF4qmRAGn
 0RH+KCHN4PWxfLx7tZm3W1y28rEOkzjezqRs+etz4yGwK0oiQU0l0xJ/HocgmQyK
 HTytMRU6SJZ0YWqMOr0avZzjIkupcKYwVjOEy0p80gcREj0ka3aep7PCUh07ftgJ
 w24Oon6xMVt17sGyqqAAzfVVWiCa790SRYsuu5cQdel9RnyH9ozWWM6Ki6q+cq0v
 mSWwS4TIqWWkXxZsF0H8C4TM2UkzskwfZDvAw1qlmmEsZ18x5+SWCYf2k4j7as49
 jXFUZRU2XBF1enVkqFYKnHwTpAMk9JmFsFXMQv+WMTndoEjSi1YG/NRLRboaIT0X
 i6+AHTAdh3oZ8bqdifE1jJCivWPn/sAsUICkpuagGygDFHC3q+5BgYVyMnJuS284
 +gB5HKZ3ww0gk10xc0EG/fMoSUEed96vceyk4qTBxfCl+bM/2KstlXfAjQARAQAB
 tBxSdWkgUGF1bG8gPHJwYXVsb0BnbWFpbC5jb20+iQI4BBMBAgAiBQJLaV3DAhsD
 BgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRCvibLmOctBU4ypD/0ci/Gt1KaD
 khN95sad+8ZJFK4K6W4o0g+dMjDa9Bb1U2gfyKobO/I2FWg9z9a5PTO5BaeOtU6L
 iGwhNVJ0iOfZrAr+cnUvbDL6cJa1gy9khzvNtVj/eUAd1d7RPImTcwq6Dn4fTstZ
 122vuDQZeh82e8W9srJPEcGgPvSk3XIZF/gilRBPcfN6KmOt0Ixx7U2rqU0sblG+
 jQKG8nsDO1huNt1dYgCh34vxeVzvsvGqFeilh1a0cvxN6+GQa07uF732lA77lMB1
 +1fEhiS/n7K+6T0w51sNjoieQAn5pE2hw8Q4QZ4HTaXaI4YG2n7dOclTtDYm3FCv
 Vdtd+4Wn2l/2VpUQfJ26Ge/BslqgF4RiljyAQ2fLcPhR1GWFzsvgDuNZRSM395xi
 nS54SGVsmMkEPoblIPCvhG26C7UszmcUfjyI++0nMRhCK/R4n/aV0VKxBWoUIhrD
 uksOFfO3jmI/58fmYD4WvDyvv9nyeo7E3MpGQMAZdNPKBdJSmFHzRFvC7LGgLxaT
 lR5uXyPEMrly68FjPiYqHDhUP4TxsBy/IBwPkizxoTtS2OEvR0uQDR0vXAY1+Njv
 YEeob+aaL8WNM4FfDZ1ZBd7Ux+qnDXuxuvR4MU7WlrzHunqWFirC1o3PslMbHNP7
 oz09YhXXNLSM+6j3Jb4zDEfsgsg02SpqxbQeUnVpIFBhdWxvIDxycGF1bG9ARnJl
 ZUJTRC5vcmc+iQI4BBMBAgAiBQJLaV3zAhsDBgsJCAcDAgYVCAIJCgsEFgIDAQIe
 AQIXgAAKCRCvibLmOctBU8XwD/48GsS6Zxmc1I1qhnGPf7+b6VeHgSyTHtu62TjA
 BGoGHeBcBiMe48ws8Atoi92EiA7pM+43aW6Hkkc/h9/1cGugsPHz3G1haw6/ikSv
 X1TU4Z3Sf+5E9NaWL0nT8o0LtQ4ZJ0BriesejV3fRXckE9gbsqOaP5legSqs8xje
 mk9lio2VkHGlBC23d4z0NFsXv2+Y/ilrvvoJMWANGaV/Ejgscb2EvK3xGgxOB8cA
 MvybOjLvDKbXAx0LfL2VtPIdsF38n744B1bsr7yreYQvMkjYxR5ASgaVVx80Bowb
 CntPsNWzyTSNMeL9IfKd5spO7QawJ9dNQzTG38SE3svv2iAf6f8uS2WNmVQxQHDv
 oB+mZ/ertNsxE0VdFBTzOuwnoRzurtOHUZnRvt4zLFOfunEQOMeo4HnXIoCHbaIK
 svXmSRl8+lK/jn5Sm7uXFVMPWCEwOlGfcey/30mAUj+9aY8TBEII6xy3d6n64cpf
 26scuS9KaYBCuqOECmQ4wDZKHHVsWQqjSeH1WOH94E47IYYhecJB+yaleP2E/4LU
 CokiRbyLlAklpT4P9x4RFt+MoWHrKMlesiR8NBVpdhV/rZSk0eF+vDuoqdrNA+8k
 dyPkWCRiKra3rRc+cdQeoD8tW+7Gg8mcFnyC+UOdTyHF1bSxP/hoODW+eu0mm+Q5
 OPlB6LkCDQRLaV3DARAA3XVIRwiM8YFt2haoWsU1yoBPTQhACxaH5YNXfgtbV4dn
 ENswRzVyDi3UvOSmC4CX645b+4RslzFTAW5iq2b0ExV0TQqEHsCuujCItUmdYeql
 6stEgVfNBiRVeYFa+6a3rWkh7dD0UDxk0PDA6pkWbUMgOGUwm+oVB6irHvcllN3q
 DAGouG23BuurPyFXC8ripXp1Oj/1PJcH5gr6Z675raaRbQuXa4ysLAPMbfxKPpON
 FhVJ77ilFzDFRknFPYBNoodQYLSmFqOZZ5rqYnBK5aiJFiDBSgYQtCJ4cbx4gCwd
 Xs9wF1lOZcKSiA9L47BZOmUL/nvGOXff/ImN5abBhJzxgm37niqZlRbHEaQ+8pJ/
 jLLqL7wzRXw7YpzVyXD+ru431nFBO5nUbfa9Q1b5VPVgsYV7r/3j8Purv+PeCZTJ
 RAU/qUBm7FhxStwPT/5jBM/oSdwLYX16naa4xGKgXwyccZ97vUsspRQnSDaxmbaz
 4s1iwClPauHfRir57opc51sL7IypnGBfnKXzebApbZcnKgYFKxVZbIVoaNFlHc5S
 Ti5CcP031vFf9R4uB0Til9qIgyzdUVpRTg0XNGxQjSh/n6/76gpQqah0jh60ae80
 frB74alM6JCdJHmYWzr664FMnplUx4JTiggAL9CMpU1Y6kYTkPMrk/dpfcAf4JUA
 EQEAAYkCHwQYAQIACQUCS2ldwwIbDAAKCRCvibLmOctBU7KiEACFQ4Dd2cR3ybc2
 rppjM7hI4i6wvpqDu3qD+4xjKfa1h7Ihtxh/QInl6a6cwTwKhM68gIM/43nrMrsD
 vfukfNGvgavrxdNQlxAbItEybDP7PFJEqIEjCBl36KAAYMbkzlXloYAHX3eyIz4Y
 ZOKGVF2lQkhqmA/SrmM2Wqk/uB4oATrbzOUvKFa+9R+PVV7MMZbpM0tiVak2fUn1
 M2N3S+t2usxMXVIfHjv9LexEokaWZcr+vj8NM3X/HVYiv+YXf3bO5D2Yw67ISa49
 ucFYpbOChs5a3ONrfd5v3smvkWE1ReWsPzpJ286lnGj8ZOhe0R/P+xv+dRBJzf9M
 mQTHR6L1VOgVmYkjONbZDCd+Q/Xhcuj4qeTPQtbh5ek5PqsQ6sukppn7YccbyMoA
 HHyZzZJsByT5M1DqjsioOiiW1iCRjXZfKttxx1So7aTmpsH4i7V6P0s848sME30p
 6yCsgCJgt3YPJFQqtMRCczmPWYMFKqBxQT//akRnThlIRCC1rjJBML1yoLvTzG0u
 16vOXdfscrwaGM/fOyC1sZEypyeXT7LjojQvVPfBBY/qXKjLckdpZ0YeXNSoquku
 dixFpPDnlUBdk/iuCcVRtWg8B5fPN/fbeJVRpNXnedw8aNes9JZhnj5jmTXYUlqA
 ik5Vxm3qOoCKPgBkTCUAZTCmZZ13YA==
 =vI+5
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.266. Mark Peek <mp@FreeBSD.org>

 pub  1024D/330D4D01 2002-01-27 Mark Peek <mp@FreeBSD.org>
      Key fingerprint = 510C 96EE B4FB 1B0A 2CF8  A0AF 74B0 0B0E 330D 4D01
 sub  1024g/9C6CAC09 2002-01-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDxThkERBACPf5/QHmyM944qrl3hWlWvK9fZZR2c37rhxAeqDJ8WsEMPBTZK
 WPn9BsMk+2d8e62FkzYo6L5juekd8invwd1nnszFFJdTDWx+vpMMgYuHBmme0QuP
 OnlU2FwJUCknw5Ed5pYV8F6azGgUNjYKIIJi/L3D9S2qDZ7l+3DgD0knKwCg4o8Z
 ZE2vd9uQw0AZ7lIa+li3hB8D/jHrVZqHxhOuUbxIXoJG3g54mH4i9GF8uN8ZdhA0
 9AxLVLzjLr4CQd97++LdSLagSvgD9N6OrtMPeqge4Frr1anJ+LRPDeOQhd0meJZB
 iCiekil4DSOsowqgmIG7DlAJx+PNV66qO1ExX1fv1ugyoWHJqYmdBSF9x1fHU788
 GxCtBACC9DLBMmMVu1Fsw3rnkZaR7xX1a1Bu95ZUu6TKJP6qUS5GnQOxF7dDjuwX
 /uRinkQ7W9vR4UuVvcV+Ct5R/yq7e+SfLb+YFQ2BmWeGNs5AVLxIZsZ0ar16fwB9
 XdxxHU/IkA3kYo4JfTvi3QXjLn4mbYUuBIVGAL63UO1kx1c8crQaTWFyayBQZWVr
 IDxtcEBGcmVlQlNELm9yZz6IVwQTEQIAFwUCPFOGQQULBwoDBAMVAwIDFgIBAheA
 AAoJEHSwCw4zDU0BXeQAoMlSoeOO5WtFMyC8viNAafpPcT6hAKCcjmQyI/cI0id2
 PMX9ZOfrKd/ma7kBDQQ8U4ZDEAQAw9gcDj02cAlUh8G9bLIQazPLJnX0fah7KB3O
 kxh8wFn0LliP7W7HLB+nQNyO4TfNgI0bhVyKDQQbKI2xJ4hylo9Z1K2R7GilgCnB
 FUqIp0MdqAswX2Dq7KXoyYAZRBOnQounUMaQ+6cfRI37mWc6dC2uY5qHne4zmLML
 /lVOjVMAAwYD/1ZArkN4IDk/VALPnzW4VYcCcT+101DMZfIMvHK2MiwWFmO+Er/K
 gIo9DrybHNQ6+bVQh/F6PSlxDrgWey7dQbHQSssC364v3RPOCmuBJCMTEszaais3
 VekHF9i9NMsUzbGpowaQv+YKMFQu4Rtlwaq7NUp/cD4a+jaxto9ij4EliEYEGBEC
 AAYFAjxThkMACgkQdLALDjMNTQHvuQCg1PrMlcafQ3BUaXAQRlGoyvF2WcQAn17c
 HA1RAO/MXM99nT62+AKLlpeb
 =mfY+
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.267. Peter Pentchev <roam@FreeBSD.org>

 pub   1024D/16194553 2002-02-01
       Key fingerprint = FDBA FD79 C26F 3C51 C95E  DF9E ED18 B68D 1619 4553
 uid                  Peter Pentchev <roam@ringlet.net>
 uid                  Peter Pentchev <roam@cnsys.bg>
 uid                  Peter Pentchev <roam@sbnd.net>
 uid                  Peter Pentchev <roam@online.bg>
 uid                  Peter Pentchev <roam@orbitel.bg>
 uid                  Peter Pentchev <roam@FreeBSD.org>
 uid                  Peter Pentchev <roam@techlab.office1.bg>
 uid                  Peter Pentchev <roam@hoster.bg>
 uid                  Peter Pentchev <roam@space.bg>
 sub   1024g/7074473C 2002-02-01

 pub   4096R/2527DF13 2009-10-16
       Key fingerprint = 2EE7 A7A5 17FC 124C F115  C354 651E EFB0 2527 DF13
 uid                  Peter Pentchev <roam@ringlet.net>
 uid                  Peter Pentchev <roamer@users.sourceforge.net>
 uid                  Peter Pentchev <roam@cpan.org>
 uid                  Peter Pentchev <roam@cnsys.bg>
 uid                  Peter Pentchev <roam@sbnd.net>
 uid                  Peter Pentchev <roam@online.bg>
 uid                  Peter Pentchev <roam@orbitel.bg>
 uid                  Peter Pentchev <roam@FreeBSD.org>
 uid                  Peter Pentchev <roam@techlab.office1.bg>
 uid                  Peter Pentchev <roam@hoster.bg>
 uid                  Peter Pentchev <roam@space.bg>
 uid                  Peter Pentchev <roam-guest@alioth.debian.org>
 uid                  Peter Pentchev <ppentchev@alumni.princeton.edu>
 sub   4096R/D0B337AA 2009-10-16

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 161436 characters]
 jjAqbYfJRPjeyqTOUA==
 =S5L6
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.268. Denis Peplin <den@FreeBSD.org>

 pub  1024D/485DDDF5 2003-09-11 Denis Peplin <den@FreeBSD.org>
      Key fingerprint = 495D 158C 8EC9 C2C1 80F5  EA96 6F72 7C1C 485D DDF5
 sub  1024g/E70BA158 2003-09-11

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD9gSfARBAC0ZC5VEuEzqk8KQ3tFam5rugDTaigVzYDmT6XBrQuVwYrFY5zj
 gz3o87e/KGmvh0FgpulhoJpkOW9l7oPQpp0wvEm45WRq17+7quW9VppgVCzs79FL
 Cc77A4g5LAuO27i1yygfMfPrr6J/M5bM2FyuUS35QvKBTlkZiB/Zt1d1QwCgzJML
 PdRvozXQdg6/bPc+M3Wh9AsD/0NxL7cwGExg57hnxA3oNB4M7IM1MwbDDaEQvJbW
 Ls8c+x2UMzdE4XHMhr940GiwUzEa1lyy0M7FmB+cdFgqhJ1VFjYE6VyGkyYtticL
 my6Im5S4Pfvx7pO2qLmYW+OnbnC6FFgFPbsAZVl/1fy4hN7U2zQIMw3kIodFBnyN
 RMsvA/9uzITCim3ov/9x4OYX0BfUNNmczIZMvXbmcuDH+NfwkGu9pmRitx/AWHGJ
 chOv4vMuMnBHU12TV1dstlWrb+Q5DVrnbVUq90mUbxg2emvlv+xK2oZ9EBKjAv/z
 NFqySi52vd+OmgopbVI6bI2+VdKrKeNcDByt/2zRGo9Y9hDULbQeRGVuaXMgUGVw
 bGluIDxkZW5ARnJlZUJTRC5vcmc+iFsEExECABsFAj9gSfAGCwkIBwMCAxUCAwMW
 AgECHgECF4AACgkQb3J8HEhd3fUzKwCgj1hA+IDNLHGdD+ua2bs3nPcL+vMAnjR8
 6CwsvOZIL5cr0EyveMsGNWqnuQENBD9gSfIQBAD+YKY2v46TD994B3h0KtAI8/Zd
 aJ+K1yUNIDxjueo7v+c3jKaWPgX1h+Cr/O936IVnG1zg81zEF0Ly6NcwWrj70UDO
 deA4tvx8HQoYfjwRA2kYAv73yvt+UG6WS3cGkX28dcLb8/JEV5M64AYKhgqRX12m
 VJWIKdqMYzho8n0mCwADBQQA9WcaZB8RVj22I88DA6okYxiU2vqAN+QUvZfX0X1/
 7Rh3mB8iAXBuASEw6NbQnGtky8RlkTDgYu1UJt0aSV2U2CXKOyPCJut0Ka+YYtOM
 prdHmnNSksNvwThju8F6js51nrf3D/7L9SFhc+W8JTfa8iz9Zfgq1HQkZ3foSO5J
 W0CIRgQYEQIABgUCP2BJ8gAKCRBvcnwcSF3d9Ut3AJ9WFh2gFxmqE8O3B85dO4yx
 z/OvxQCgsQynjVGZI9JJn1W0KOAYSbihdu4=
 =kQUf
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.269. Christian S.J. Peron <csjp@FreeBSD.org>

 pub   1024D/033FA33C 2009-05-16
       Key fingerprint = 74AA 6040 89A7 936E D970  DDC0 CC71 6954 033F A33C
 uid                  Christian S.J. Peron <csjp@FreeBSD.ORG>
 sub   2048g/856B194A 2009-05-16

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEoO/iURBAC3FVq7xH4uRIEWRvmPzD1azqtwlQE3zipCf4K9B4EjKidksgP0
 56qAkWMvngWG7OW9YNCtZYgDNAINOGdw2pZYioERq7U+cdIPKSZrIP5WrpORdi8A
 4i3VmRKh19ztJEGb8jvthYDlEyvoABXmz/Bi3YHDkfjT0py02SnkcjikxwCgkGkL
 rNwWGviRd6hsBZZEeximSKcD/0OAthVoMmk4bMByWPoEWf5i3I3JHDeC4g3oEgYp
 7dxMaxboqjFmiTZ2xMwdR9wlpwE0ITSeVj5pMtswr8q3ghLdlXOpd4wn/vLu51/G
 ra7cFgNex3kCb+5tLfqZQCiK/Y8fQ6TJdowaxN0xtrdGbTtUR0BJMi7/AhNF1GxW
 HeE6A/4n/K5Z8EDq7e5HZ5S0lx3MAKy1QgS1tnO0aaHK3v+DtD4xbe9aV2ls39sh
 2Xu+z5QGkrx7q3HOSnC/DzMSYDG5I45GGNdDoBVmJ6IfvNICzXgM4hDh8KgIXNZZ
 PEkHN+uwTWCnIj1yhothpk86XBvyiEAbCTwQ5jWBmZkvLI2GdrQnQ2hyaXN0aWFu
 IFMuSi4gUGVyb24gPGNzanBARnJlZUJTRC5PUkc+iGAEExECACAFAkoO/iUCGwMG
 CwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRDMcWlUAz+jPOYNAJ9WfWDy0ZlOC7q7
 KUyrq7e49no1SgCeO4nUcK5nLZKkyGXxTbnghFZegGS5Ag0ESg7+JRAIAM8UbDPn
 dVBYrvJqBwdWQA17XN6jycQC2smWLnJ6geaQfBgXAff5/Hn1LtPPG58k048yF6QF
 xOCzPOTrkjaL8GlyKGLK9jfctyC+zRl5FvNyJIBIgFRsJjBB9K3FpZEsxWltSyqc
 5mxf4D8VwJeDfWdgeqVgORapBruHm3MAf5B13PfBN8lV2Yqbo520U6ZWUtdTscsL
 2QLTZcrIN5aq5Wsuy4r8H90h3JYcOUK4PJTBNLmlmLEuTlENbv8E5YVvvgx/ZJ9H
 lX9FWz+w/hrEQIR2xnF8MJeAaOR3Q6cKgvFrH7PUHwvYxAXkXGWv6xsJ4VEA7a3g
 IOytL1l/8Zo0fiMAAwYH/3Sn6JzdbiF7peLiQ3SqbNSQV3aKxNP+PuGvuALiHKKd
 WgF5xjrBfgSjJbybwm4YtNfqLU/x8SEtEXVkyMozgWSMn2K/vFrgwURjG92IhDXJ
 bOzEDyx86/iJosMn2glcb9eBYGrmz92H+9a1Q1xMyuk7uD/+nFcJOj3GqnuFK54L
 //A6ott10Ddgg8JB3jehrzrOeg8/IdPifhT845X9q24b3kG0orzCIOk0/xyUyps+
 9A3j54Fp/atyVmHFPRedjGMwYPIqKQvFnzYuaoN/NT1yJZEFbyud/h1Kpi4+Z2/C
 Te9glz71eqlUSond5WFnLSd7GSuUxXprwC0bGQ61tASISQQYEQIACQUCSg7+JQIb
 DAAKCRDMcWlUAz+jPNDzAJ4lJdUYDs8aONEFRW/TpLMiepzPqACeN0HmbLJjwaVk
 tI1h5vM9MqGGVwo=
 =p6fK
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.270. Gerald Pfeifer <gerald@FreeBSD.org>

 pub  1024D/745C015A 1999-11-09 Gerald Pfeifer <gerald@pfeifer.com>
      Key fingerprint = B215 C163 3BCA 0477 615F  1B35 A5B3 A004 745C 015A
 uid                            Gerald Pfeifer <Gerald.Pfeifer@vibe.at>
 uid                            Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
 uid                            Gerald Pfeifer <gerald@pfeifer.at>
 uid                            Gerald Pfeifer <gerald@FreeBSD.org>
 sub  1536g/F0156927 1999-11-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 30096 characters]
 =3Uph
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.271. Giuseppe Pilichi <jacula@FreeBSD.org>

 pub   4096R/8B9F4B8B 2006-03-08
       Key fingerprint = 31AD 73AE 0EC0 16E5 4108  8391 D942 5F20 8B9F 4B8B
 uid                  Giuseppe Pilichi (Jacula Modyun) <jacula@FreeBSD.org>
 uid                  Giuseppe Pilichi (Jacula Modyun) <jaculamodyun@gmail.com>
 uid                  Giuseppe Pilichi (Jacula Modyun) <gpilch@gmail.com>
 uid                  Giuseppe Pilichi (Jacula Modyun) <jacula@gmail.com>
 sub   4096R/FB4D05A3 2006-03-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 6402 characters]
 Z8VhMQ0Xfpv8p6kgxG3PEbR9wWq75cRBbNOEApw6YpKxlRCbKH8=
 =jIdO
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.272. John Polstra <jdp@FreeBSD.org>

 pub  1024R/BFBCF449 1997-02-14 John D. Polstra <jdp@polstra.com>
      Key fingerprint = 54 3A 90 59 6B A4 9D 61  BF 1D 03 09 35 8D F6 0D

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQCNAzMElMEAAAEEALizp6ZW9QifQgWoFmG3cXhzQ1+Gt+a4S1adC/TdHdBvw1M/
 I6Ok7TC0dKF8blW3VRgeHo4F3XhGn+n9MqIdboh4HJC5Iiy63m98sVLJSwyGO4oM
 dkEGyyCLxqP6h/DU/tzNBdqFzetGtYvU4ftt3RO0a506cr2CHcdm8Q+/vPRJAAUR
 tCFKb2huIEQuIFBvbHN0cmEgPGpkcEBwb2xzdHJhLmNvbT6JAJUDBRAzBNBE9RVb
 +45ULV0BAWgiA/0WWO3+c3qlptPCHJ3DFm6gG/qNKsY94agL/mHOr0fxMP5l2qKX
 O6a1bWkvGoYq0EwoKGFfn0QeHiCl6jVi3CdBX+W7bObMcoi+foqZ6zluOWBC1Jdk
 WQ5/DeqQGYXqbYjqO8voCScTAPge3XlMwVpMZTv24u+nYxtLkE0ZcwtY9IkAlQMF
 EDMEt/DHZvEPv7z0SQEBXh8D/2egM5ckIRpGz9kcFTDClgdWWtlgwC1iI2p9gEhq
 aufy+FUJlZS4GSQLWB0BlrTmDC9HuyQ+KZqKFRbVZLyzkH7WFs4zDmwQryLV5wkN
 C4BRRBXZfWy8s4+zT2WQD1aPO+ZsgRauYLkJgTvXTPU2JCN62Nsd8R7bJS5tuHEm
 7HGmiQCVAwUQMwSvHB9/qQgDWPy9AQFAhAQAgJ1AlbKITrEoJ0+pLIsov3eQ348m
 SVHEBGIkU3Xznjr8NzT9aYtq4TIzt8jplqP3QoV1ka1yYpZf0NjvfZ+ffYp/sIaU
 wPbEpgtmHnVWJAebMbNs/Ad1w8GDvxEt9IaCbMJGZnHmfnEqOBIxF7VBDPHHoJxM
 V31K/PIoYsHAy5w=
 =cHFa
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.273. Kirill Ponomarew <krion@FreeBSD.org>

 pub   1024D/AEB426E5 2002-04-07
       Key fingerprint = 58E7 B953 57A2 D9DD 4960  2A2D 402D 46E9 AEB4 26E5
 uid                  Kirill Ponomarew <krion@voodoo.bawue.com>
 uid                  Kirill Ponomarew <krion@guug.de>
 uid                  Kirill Ponomarew <krion@FreeBSD.org>
 sub   1024D/05AC7CA0 2006-01-30 [expires: 2008-01-30]
 sub   2048g/C3EE5537 2006-01-30 [expires: 2008-01-30]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 11022 characters]
 6MXOtw==
 =3Md4
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.274. Stephane E. Potvin <sepotvin@FreeBSD.org>

 pub   1024D/3097FE7B 2002-08-06
       Key fingerprint = 6B56 62FA ADE1 6F46 BB62  8B1C 99D3 97B5 3097 FE7B
 uid                  Stephane E. Potvin <sepotvin@videotron.ca>
 uid                  Stephane E. Potvin <stephane.potvin@telcobridges.com>
 uid                  Stephane E. Potvin <stephane_potvin@telcobridges.com>
 uid                  Stephane E. Potvin <sepotvin@FreeBSD.org>
 sub   2048g/0C427BC9 2002-08-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD1QNM0RBADbw1IMsD6ShBkXQirwG9TUFkBfZOaGUB9nZZTGZzkDWsj9/8FP
 TacAKze6REEdtfADFyYolZrps+o0xVUI3ib5kzXnzz8yj41HTzR7PG0FcgINt5Ls
 yuq+d3ETSu2AALwNfolKy/9yIIcRFl1bI5cawOua5MB4VUaf4JHiyOikfwCg/zsO
 QReMvoKLcZkn9pcCH6EZHtkEAIxZKMcRaIuGe0vF3oP4GfuEXIa7K7R9ez0u3iiD
 inNPQ5vQuY0qJMLbZAu6wyqEP9wVXCdAiclBbPYRb9tabcV5gFkuXpLvq5E7pGkN
 hRF/rUeDxf/EKIklqe63KNqgzMZ2nM8lvoDkUrdSQL5dc2Y5a6VIq22QsgaraYmo
 j4p7BACAfCiZjND9VcNAQmTvEyNGslQ63gzUfE7D8Xlx2Glv4PP9AmZ2X+FRliY4
 YaARKDK+62bNTrJjQGiaIzz9LsFV5zpYvHBQ9KP6NIp5bP3ljaUwyAJt5+GT8sGZ
 ZOBpSmau+s8RmSPajjvSwACjWF9tP19IJMtnk+pMn1SGiVbMA7QqU3RlcGhhbmUg
 RS4gUG90dmluIDxzZXBvdHZpbkB2aWRlb3Ryb24uY2E+iEYEEBECAAYFAj3s8qYA
 CgkQpvaYsfdm3ZH1VgCg3x3Qbvq/n5W/xonGXqI6+LJXLw0Anj5AgE0GPTC1naYn
 KpFmD9Hb+m6LiFgEEBECABgFAj1QNM0ICwMJCAcCAQoCGQEFGwMAAAAACgkQmdOX
 tTCX/nvccgCeIGN+hK7GND/4+9BbHpXOOnnlsJ0AoOavUpZeUj/t6pw+ld4CU7t5
 iUrhtDVTdGVwaGFuZSBFLiBQb3R2aW4gPHN0ZXBoYW5lLnBvdHZpbkB0ZWxjb2Jy
 aWRnZXMuY29tPohGBBARAgAGBQI94tEZAAoJEJnTl7Uwl/57WiQAniYT7h0K32tZ
 1+PkyM0UUvu/Vg3JAKD2VXNsiI3w3o/xm20IqR/UwZtAVLQ1U3RlcGhhbmUgRS4g
 UG90dmluIDxzdGVwaGFuZV9wb3R2aW5AdGVsY29icmlkZ2VzLmNvbT6IRgQQEQIA
 BgUCPeLNjQAKCRCZ05e1MJf+e0K7AJ9YssAR7btTX0oE9MNYYVQBbfYNpACfdyiD
 QeQhD+7FNqs4cZ+GEsWMxJ+0LVN0ZXBoYW5lIEUuIFBvdHZpbiA8c3RlcGhhbmVf
 cG90dmluQG5tc3MuY29tPohxBDARAgAxBQJD6jKhKh0gSSBubyBsb25nZXIgd29y
 ayBmb3IgTk1TIENvbW11bmljYXRpb25zLgAKCRCZ05e1MJf+ewE7AJsEexwRGNC9
 uR8JUPjttVJG012/VQCfVg4M1xq2+h3Ys/DecKUVxt0uVsK0KVN0ZXBoYW5lIEUu
 IFBvdHZpbiA8c2Vwb3R2aW5ARnJlZUJTRC5vcmc+iGAEExECACAFAkXQf8MCGwMG
 CwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRCZ05e1MJf+ey10AJsHFjVs9WEaui/i
 L9xfITeCmwkd/gCcDlRcmGUW3ov/jmeDzGFrE+MQsqK5Ag0EPVA0zRAIAPZCV7cI
 fwgXcqK61qlC8wXo+VMROU+28W65Szgg2gGnVqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ
 +AyDvWXpF9Sh01D49Vlf3HZSTz09jdvOmeFXklnN/biudE/F/Ha8g8VHMGHOfMlm
 /xX5u/2RXscBqtNbno2gpXI61Brwv0YAWCvl9Ij9WE5J280gtJ3kkQc2azNsOA1F
 HQ98iLMcfFstjvbzySPAQ/ClWxiNjrtVjLhdONM0/XwXV0OjHRhs3jMhLLUq/zzh
 sSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZlp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZ
 Jrqrol7DVekyCzsAAgIH/3fG4jw0qo+iUk3wwS3oLPf5USbiPYOjUZ9jpaII8pYE
 iH7i741cPL8qNpFgshJANd4sz3Iu/hu3xj8aWaZ+jDOM674U69lcv1hl/rrHESIR
 oHIwfjmExLtnFl/2NvQ7uKM2jKoJNERtbi5P7PfLqD2Y8xK1W8cFZmPuD404SBRu
 ubk5BrYXv94VU8rxE34uhOEuAW/I6uv7DhCcr+bVJzJQYCsHxHh79kHsHEW6KAGb
 W34S96t9m8mgl7Kb+KCS7CqmqlmP4/itf/26wfXf5ynhRrWpUuc+jbf6n9afjjzm
 0CWCBS6/f2OALgJX+J5DUG5TggtFVKMMQRf5Bv79F0mITAQYEQIADAUCPVA0zQUb
 DAAAAAAKCRCZ05e1MJf+e4YEAKD8ArLrD9l/sJDn45ZDBjs3PxAEWwCgoy+go5Wt
 0MmiyLIGfKRYTeFnh6A=
 =AbPN
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.275. Mark Pulford <markp@FreeBSD.org>

 pub  1024D/182C368F 2000-05-10 Mark Pulford <markp@FreeBSD.org>
      Key fingerprint = 58C9 C9BF C758 D8D4 7022  8EF5 559F 7F7B 182C 368F
 uid                            Mark Pulford <mark@kyne.com.au>
 sub  2048g/380573E8 2000-05-10

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDkY4OYRBADvB+3Uh68SGrlbrq1MTAN/gnVaj4ztmA15X13bunGYdLKLEJdq
 rd9xFv5OgxGZXJ+sDhbKomJ7yrBGtUwC5kIrKXN+MPbO60yy30+kIVLKjXIv1d+c
 MlWhjFzHra7WGFmvhzYnbOI/zjlOR68iKHnwxhtKFOK9m2O3voURWLEuqwCgzK/S
 j4UGrPUmZf9XOZcKdnN07nMEAJrNh6aoVgK1xwpyO9uTURuCppqAUym/fr4xNQqh
 mngblwIACnV9FpBi1ogtX1iDo4YeQa7t7ALgdwTBbU8upVFYzoVByid9ibNu3OKv
 j9JvL55jUVg0wv6a8bEWjxnNK/zVa/HCzTbAzHob0CSgH9WmEJJEUIqI2/PG2dj+
 ZX3QA/4y6Gon6iya2wk0Zs7mrTj80kxLRMnuPN6geTGVNTfrxat+sA1PVpT2WWSo
 qOrPoyxcpUBbJ3VlFmuYDDgld4lJiGD/2SG5BkD6OoGlRnD5AMgUxQtQFnkloao0
 3md8UDucIJnJRF94pttQtv4lVKaocm4z0Fx6cWC4Ysupj1AG0rQfTWFyayBQdWxm
 b3JkIDxtYXJrQGt5bmUuY29tLmF1PohWBBMRAgAWBQI5GODmBAsKBAMDFQMCAxYC
 AQIXgAAKCRBVn397GCw2jxyVAKCbPwK2rDZx/oahfd4M7XJ4GoF0xQCcDExtL+DK
 wOugUQwfVIExB+HBM3y0IE1hcmsgUHVsZm9yZCA8bWFya3BARnJlZUJTRC5vcmc+
 iFcEExECABcFAjse9k4FCwcKAwQDFQMCAxYCAQIXgAAKCRBVn397GCw2j/OXAJsF
 bdYQGgCs3sXMOdb7pNUi2DL2kgCdFOFSojmWV9mulpzH6ceb/fKgoJC5Ag0EORjh
 UxAIAMrmc2VXtnp/WWhGne6yTirnnWjR/c+rSK8ixbAqTkdYnocY6gtBJliR7LSh
 Cv2RD8TaUc0ZZseHC5vR7VZKXobXUF7QqB1Rgzz/CpsFeEmxxQxZrVKNjwcMloSt
 wmH17yW5tBDg8+6KhFwHj40oV88/49L8utVMEW80gh9O9TlYw5qCAp5QKqkFS52A
 hO54xjTNdEpv/9yXpwQfgUqkAHM8MQhsaxmKCIQXUGt6Lp13aHDAYtMizED0LBjV
 3P3qCoc03P9k2nWwGGU7dukncYNNuLDW9xwkAfV9VQuPYCHEBiPTcRnn99imyvNz
 FNhOElHDttCyKtt1FdZZVAQzXusAAwYH/18mnEMMv4rMZglYb0PRCxaxwQYkxESt
 KyXEclTc0kgyaZnf4Vbdz1rroxxZLIf+16p/MVNFierz/7d5FbJYggCDSsBAaj4r
 Qe2/Os3oCnHyyQY+zF9Ac30CsxzgDxMYxYGJHr6x+s9cloZ3WwBFAO0bMoS/9T/9
 /S7L0d0litecox5et2yEw4AqHdCslGx5mX0os66uh99eeEwW2EQHSLklwUPReb7U
 6m+fNyWxq5w+qTPG+zcXdiW/117T1aONVmg29tSNW8S/syha2PCJ+IoordBus4mU
 kfa49yCuXyZAYDNLbkiqMVTDCqrH2+n1mbUuhRBaSZEvgqVfVLZzRziIRgQYEQIA
 BgUCORjhUwAKCRBVn397GCw2j7T3AJ0ZDGzVqNQBE07ntRKuzQQmou8YhwCgibYR
 ZJyP31xlO+Lt5FgzzeqcQwU=
 =DKp2
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.276. Alejandro Pulver <alepulver@FreeBSD.org>

 pub   1024D/945C3F61 2005-11-13
       Key fingerprint = 085F E8A2 4896 4B19 42A4  4179 895D 3912 945C 3F61
 uid                  Alejandro Pulver (Ale's GPG key pair) <alepulver@FreeBSD.org>
 uid                  Alejandro Pulver (Ale's GPG key pair) <alejandro@varnet.biz>
 sub   2048g/6890C6CA 2005-11-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEN3W2YRBACt8uucrC3Gv8Q2PoAppL0Gdmy+ufJkvp+e3QpNnEvYPU7jivtZ
 MBuMVzadeiE2FMfzAhD90bLOxomZSwIKAc+uiMqqXrciOGMEBFFcHNOgHGI48me3
 fBvzQ4weJjGQrdUVOuQOtCNEmPHHdXOG0Vks+2ZD2czYDmixUkysso1gXwCg5ETt
 H/u9qXgKHxwQN1znhppBHu8D/2/ikj7Y8S5evZauwQ5m1qBMz7GS4FyXH8LZPPC3
 KJW9AHiNSOl4a0g6bH17OTaa6OOljyO0MzbM0UQDJON9JvGLH4q3ML0QQ145yfvQ
 fxLbFMU0B3MSOgFUkpRrWflbsleBp0BH6MCUNzdhDVgyQxyLkyr+mdX6m7N+EiF1
 m882A/9hz6+cmex12xdJnhx/frVL2Ji2deY4JntneNcZS7FBCWCe5d4weYUlLUJa
 sAZuwe/8q5BftMfHXeJzwLc+8zJ2EU6HEX7QdJTezSb7Mjh8Py8T/7TkyjK9LYJ7
 hg8BSx7hQ0xo1KJoDx057GjkE2PGW+ngUyAExGvZHc4Gos3lgLQ8QWxlamFuZHJv
 IFB1bHZlciAoQWxlJ3MgR1BHIGtleSBwYWlyKSA8YWxlamFuZHJvQHZhcm5ldC5i
 aXo+iF4EExECAB4FAkN3W2YCGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQiV05
 EpRcP2HiqACfSVe9jQLEj8zM/iMLO3S5aLY6EawAnjIo6VapDopNW66BjRzFKQ+D
 P56HtD1BbGVqYW5kcm8gUHVsdmVyIChBbGUncyBHUEcga2V5IHBhaXIpIDxhbGVw
 dWx2ZXJARnJlZUJTRC5vcmc+iGAEExECACAFAkQy/PwCGwMGCwkIBwMCBBUCCAME
 FgIDAQIeAQIXgAAKCRCJXTkSlFw/YcLPAKDTcYP8Uso5mQls/wFYuOsfruyyXQCa
 A/xZlNpAz+akVuPQZRh4qqHH0nC5Ag0EQ3dbdRAIALqYTavt1809JFOCuiaOZBeC
 /qK5Hvi70rgyIyUJj6q0RrC6FzEOTKGQIaLZSdxhG50lw2KFOCkq0ARfhdrezR0a
 0WQApeSb63hd1lvOz8ocyPkUI1IKc7aD0aQfcplaf3NmQJ6HF0rEzenRUoxy3mro
 R1yddUO/HosbvaeSCRabM1ORqx/G3WFfmX6dHuLltvbModDmOr04QbQ4+gctmplR
 qtk7eRXAFAG+Fo7lkhF0z1KUFQF56kL3rDXaAQzE/Vv6Rgk9vOYGXLJQdngNIXhC
 KVzrkqrZXj4El1gfSR1Dl32AzZtY6acGF2GvMGm2R2udTHsYeyCYXKlBRu6xakMA
 AwUH/iRn8SsuszctzdLqNxideej+9FQ+nHaMBw3Y+N1tlkHeDVmPDNiTotOzYo/V
 aRhW3bAebwEQr5bOs/6bnDrK86b2PUuwC/XtE9nXF9f1QQvApIyKzW6VG/FsQIpd
 +5lNWfRDKmoUZpMeKg9bQCjeFk8tFXsnp6kn8NhEAMCCeDwiWYUl8pcFlNIwPs1M
 brkZ7QCbA8OFAK0YkzUqYmvKPIS2SjpMA+uPJ0674v8kMuh9VhcQj/1RKKR0q2Fm
 sUykWFoGEp1FAVpMkKa2cKS3vYgpobMjVYeMWhsWXAFM9hZT9gI5oKVo7ECUZEBO
 f9dufNDZ1UHAHlAojMMCW53/fGSISQQYEQIACQUCQ3dbdQIbDAAKCRCJXTkSlFw/
 YY8XAKCxojHrj/8OzUI3PFFTS1/afkj3HwCgz5wfMMjyDZG8rUt9ZFbUVN/RPs8=
 =iWC8
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.277. Thomas Quinot <thomas@FreeBSD.org>

 pub  1024D/393D2469 1999-09-23 Thomas Quinot <thomas@cuivre.fr.eu.org>
  Empreinte de la cl&#65533;= 4737 A0AD E596 6D30 4356  29B8 004D 54B8 393D 2469
 uid                            Thomas Quinot <thomas@debian.org>
 uid                            Thomas Quinot <thomas@FreeBSD.org>
 sub  1024g/8DE13BB2 1999-09-23

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.7 (FreeBSD)

[encoded data, 5606 characters]
 =mFN1
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.278. Herve Quiroz <hq@FreeBSD.org>

 pub  1024D/85AC8A80 2004-07-22 Herve Quiroz <hq@FreeBSD.org>
      Key fingerprint = 14F5 BC56 D736 102D 41AF  A07B 1D97 CE6C 85AC 8A80
 uid                            Herve Quiroz <herve.quiroz@esil.univ-mrs.fr>
 sub  1024g/8ECCAFED 2004-07-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBED/zxERBADJcZlF+Rzm8wL5lPTTPA1zLwa9u4ZZeVheS9vRGTOC6Sfi2NV9
 feWCM4TR9CVtp2tAcVlrXjBzvhbeNajssCPn94qUh4z8ERJKT1R8n4zlilTcMTSQ
 qZ9t7mIpcpsmpCO1FvfozjfexpUSeLHONKlwHhXXQFdJm6bw3X+kZKUeQwCgut4g
 ilrxtY66n6pzC7jt8GaM1ikD+gLzk88lPNHA8hZurRaYoRD2cD7jOMk0WNuuRZLA
 4LsG+hJUyrPU5vLKou+2iXl6MBvjlYwY3FS5wc1PZ9tRRbMNIq71xCTXmSapks50
 M+/cVYhJhQTVWCFhY+HZLDJpiaeMEkTHqoXo6ePVSMgFDQXADv/hMIPkNheXzmXM
 yhw0BAC75FBSMcRJz8jOaHXSZ7AM9EdMhH4mru1YyfLzwqk0DQS7ToXc8mEpo9SJ
 c/rYfSHf6Egx9856sncCfLvoTScZDwWXvB7kJPOfXK0u8KK1uZBDAqEacmm2oEHd
 Xi0KbfW1zyqIPnLKjgu57OqSGyDBKzC2XuQvWcNk7Sol/Yxp9rQsSGVydmUgUXVp
 cm96IDxoZXJ2ZS5xdWlyb3pAZXNpbC51bml2LW1ycy5mcj6IXgQTEQIAHgUCQP/P
 EQIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRAdl85shayKgHKNAJ9/qmkJgaMW
 zOFnMUGcH/fc9ksrZwCbBhYIuo/nnHe9tC53mIlqDoXOz/a0HUhlcnZlIFF1aXJv
 eiA8aHFARnJlZUJTRC5vcmc+iF4EExECAB4FAkEOc8MCGwMGCwkIBwMCAxUCAwMW
 AgECHgECF4AACgkQHZfObIWsioA0SgCdF2eAlmqyihMQVf/T8r/x6x385vIAoIhZ
 hhYxTsWZ4dUA1XmbEfZxMQPvuQENBED/zxMQBAC8M+1oDgxVjVnYlhapOHWNMDlU
 1LolN2B9sUm56K0UaCpnCsrm2Jc/kzr1egmjqxGkV1dIih65W+oPZQOBqq4mAvPI
 SRlE0MrcPCeRyzN4zSwqwu1o0rcCWaacPpNxnG5icluD1RPBDucRPhc8gFMmcfEq
 5pgw3LU58ZIrvB3FLwADBQQAjM9l/u6o0CVwRZ6XshuJQnc7Kt+su/xyZjkYqURp
 sZ8Q9xWgKI4Tv/x+IbgkU5D2vCu6FyfDpBMWsNnSxVJ8FaHCWDKLpDHxB0+RUcme
 HRcpvV+HnLvJtF1V0dRB3XVtD8h6TcGuntFlKHFTKKQk4H5X+fbsUdq4ycNwgNm/
 IfyISQQYEQIACQUCQP/PEwIbDAAKCRAdl85shayKgJrjAJ9S1aS1G9Vpq0kYjZHp
 pFmvrw+CbgCeIgeeepmX9+n+2YEAuWfJlX2KZCs=
 =Snnd
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.279. Doug Rabson <dfr@FreeBSD.org>

 pub   1024D/59F57821 2004-02-07
       Key fingerprint = 9451 C4FE 1A7E 117B B95F  1F8F B123 456E 59F5 7821
 uid                  Doug Rabson <dfr@nlsystems.com>
 sub   1024g/6207AA32 2004-02-07

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEAlXqcRBADYFElOoUIMntNwwMiVO/7bQQGYgo0HOz2ih10GpP3iyNletvOt
 AbH7AFCB/D6eHO/pOs3khk3ys3xL618e8vxttN7/jC+GWlPb6zReE92A75iP7+ud
 aDCccDlpfsoLfTt8FlZnFuA+d6gJ48Aie5meq1T/IlFV/EJGZ3BfTyKkAwCg545G
 dnVFL0hRjIJkz6Bs5xKqpxUEAIpfe1Ik8aXgwgbW35dZPUtUNDU3OmullZO8z2BU
 HefkZDyL+y5MBO/9aGtjN+TpnhmhWcVKD7rhTsL4w8v719Kq3cGFfNL/E1D6YyCp
 /BU0/Hm9+1MMxPg+nIUkhU4HmtZGoLT71xRSendbZjCr+s31XXxA5YbLruztTRFT
 YcNyA/oDbsyMIcEemO7F2ypq2FPlnjjCISS2Fr0HsBQltedY1Kr+hfOnjYAcMfIQ
 QyojMPl3bV4IFcavIhkiQBPBwGJsj/SNgNhOek9v9c4iuLpXzzbOfO4WiRBkpUY/
 Fzefogi7d+9t/PyPVzd5Rzwx4eqrTYOeMT8TJmGLWkoUwbMe1rQfRG91ZyBSYWJz
 b24gPGRmckBubHN5c3RlbXMuY29tPohbBBMRAgAbBQJAJV6nBgsJCAcDAgMVAgMD
 FgIBAh4BAheAAAoJELEjRW5Z9Xghhw8An02BsS5+rEgyF+f+byeZy5sIrDnJAKDK
 GpoGPWfwZ8leK1MqENlxZZerx7kBDQRAJV6oEAQAvo0FvU58ew8t5XAo27wvwpxV
 pdWoKRTF7lS7ENfhwoiHVW2qsX/TfxyRw50BEtDUlFe7lBqSyskJ/3ejcVXuJ5cm
 vYmxrUEfas57AnBsJqFerQhqB2Pr6BwDUU9kpmJv9vAlt/vdX6lIkXTfvGcrSFWF
 7cDEL++0tD63ULOVQ4sAAwYD/1CUpkXjwmFkg72LddRrvmXtKxk3crql4dYj/wjQ
 JeWeZQT+HKOOIHYFENZAqC8GSfQ621DeFD+TIN9SNeBG8K1LNqxUk71QAwiYSz2R
 Cm3n97esKKD2SB0yJDQJo+MsQ7PKdQPJtCDk34x0JvA4eijiTj9yGdQX8jWi8Sd7
 H0NPiEYEGBECAAYFAkAlXqgACgkQsSNFbln1eCGOuwCeLy66OJdIebn1pU3UXo8O
 xlFnyncAoOYrXS8vPETOhlx/yeBVsgfX1vcL
 =ZXPM
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.280. Lars Balker Rasmussen <lbr@FreeBSD.org>

 pub   1024D/9EF6F27F 2006-04-30
       Key fingerprint = F251 28B7 897C 293E 04F8  71EE 4697 F477 9EF6 F27F
 uid                  Lars Balker Rasmussen <lbr@FreeBSD.org>
 sub   2048g/A8C1CFD4 2006-04-30

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBERUw7QRBADJY85JY9QB4nxv3rXAPnlW59gLmWzuuVNnKBrQsoD5jq6WrDEs
 fqqU2h/JwHB06RZMm/VUSH9MnsrxpGGKbIuJ9bRn9zA4qbgP0kPCMoyb9AmyGEYx
 bIp0N1PeYni64IQH3XGaycloWNhNDDLv6o+c6e+wNnRfUv1qygKhM8vf5wCgyN3/
 KgxrTIo27FnrLDatjxYgHeMEAKtOpeyGk8VhkxXX7t6/sD1HPvDiuYLfM/14VKWB
 ZXaWcOzhytZRFbu/DDG2sMiMFdK8Xu7a1Zsfa683kmpgqHkG0FYcS14Y8yHDU1IM
 GpCRz18v8tZwW4N1npJ/vthpL1B4Hx0SUhGo2HgE85pRHdsDbhp0S6pZW2ff25wZ
 ljhABACI2/zM6SbfibbyRsvJcyW/TOfnEOxHUFfqT3SFYAP79hRBsqCN8v4fSR54
 Tf+jHv7uYVH2lK3zED3sXn2VCgjD3jJNLkeGB6qY/WnWYCB63YwUXk2igOqGijJq
 XEVplNG6ExaQIco5vilOseqWuW5ONJKMM+iEi5TpfV1cPGFpAbQnTGFycyBCYWxr
 ZXIgUmFzbXVzc2VuIDxsYnJARnJlZUJTRC5vcmc+iGAEExECACAFAkRUw7QCGwMG
 CwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRBGl/R3nvbyf/xeAJ98F2AdELJxK6Po
 3rTPUqnJK+GZawCfX/0jvc82JWnGwbDcpyp0+xUJ/xe5Ag0ERFTEKxAIAP2AWduS
 +WfuTAqZlD2aIzyvzZPOJ7a8ZDmUtBDxbxuBetLMqC3oFMoZ1/857wV3J7Jvxx7u
 LFbpdYS/0zXTjyKE/NWqeHIuGH9fDOIDuUKT1ZkEh+OzfWQaUihYTib330LwWP1s
 9J8zLCJM1SdQSHVDOG9m+28JXH4ITmK3LkR3zdb/QYEOyFmHfhSqVQpZ/KEBYZ1K
 Kn0gItwqDILuk4v8BvR3ioWF1Ywod6JEMAgJvwypyDlyglvVVvav8UcOYIYfyv2i
 6g2EjIqmCpzaEa3m/RumCWaCLIIeZUqpM+rIfQyKcjgU8J254dFMqFYFIX7iFGnO
 FVhT8tyNXolkKWMAAwYIAPrna0LxXoNVdwCyAW6pcNR9LkWsalQ+cCTS15jnguq5
 V6HmMHsbAIwcXqZn6benX5g6Gx68gIrSS/c3iBMS3jiauIu/bjvhdTMLr0v/jXpp
 7HjdOkgwfdE184hxVzsO0w3UeWFVhmb6sW/Wb9OtdRTj160mHj5UsCycg7Q75R20
 2sBke5vP6o22CCNOZQxM615oFDgotYO/D5I8h/x08IQHlyxzgG2VXFbb/vvibOVs
 iFA246TaRzxYjo4pJ7apRKhXWX9Bm6Tl/X3X41idqbkZXXcdOV8i1jjJ+8hvmUXX
 BTrU4DyOHeRrKD2GRBGMn8WxhPL0DN+w2zBRpRdM7sWISQQYEQIACQUCRFTEKwIb
 DAAKCRBGl/R3nvbyfw7kAKCnpl/jNh5Hx0mkJ6BEDWlmGzuvMACeM95BWxxghmcn
 J6BmOEuZ+TPmHxc=
 =6byw
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.281. Chris Rees <crees@FreeBSD.org>

 pub   2048R/1E12E96A 2012-08-26
       Key fingerprint = 8C57 BE3B D320 5FFC C4C3  C0B0 900F 45A6 1E12 E96A
 uid                  Chris Rees <crees@FreeBSD.org>
 sub   2048R/C10740CD 2012-08-26 [expires: 2013-08-26]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFA55DwBCADLmiSSORwcGwNoCi2X02jPmS2lcZXWp5uCtzx0ybPM65tIQAII
 L5e8QzyrV+r/yyNdGJIKtl4ty69aVodQ6n6Xf2BGqmm/x6jlvg2BrJgNHYfAjkIV
 tugkbwsMQxHkNmOlB+fURVPJk9xub4pz9kRRdtXJ3DiImQRw5XVe2ZvBXZuu2nOz
 jw2zArEaBSLbjo1MlXWJvvuyA2ktaKcAjFyfz/VJ8M/RDbJdfYDB9Q78jrr4uwIM
 lyWSWUD8RxAvbWw0My2tr1Nu9FDvsydbKygGnZ+7oo4zvqncGZ+0am6D3XSsOcaf
 /bzB8pIGJ1hsSe9JHvYpLvnWCwP+AJtKTPwFABEBAAG0HkNocmlzIFJlZXMgPGNy
 ZWVzQEZyZWVCU0Qub3JnPokBOAQTAQIAIgUCUDnkPAIbAwYLCQgHAwIGFQgCCQoL
 BBYCAwECHgECF4AACgkQkA9Fph4S6WoK/gf/eghgBaGoxfXXbNZwZNIC0NUhISas
 XVYnKNpKCojFl80ZGzI5mPAFUiQm6aMh3fSrzTIB1uxxd9T9A3KN5ghf9jjtOmpU
 +uYEm1aW4wHYSWzKDfgfV3QlFOROBn02V8xc1XPaZr0pqBCSJ18BDVwsI8UG9odw
 /vPrrcE/Gm3psKJRwaHVGTtvJYPZYB5dQM5XD0shvj7DDSdut5l7DGDGUhp6Q8R3
 2iMkCSTbaJEQNMzUqoIIw/oPrgsVeNxG7zFrkxbdl4YLmuzy9nZhRPLZ7lWpoRrf
 3lsvo7WktMEXiW+uAX23wKH3P0gSypcsJ/jbb0nfV1r13/8O8plXwo5Z9LkBDQRQ
 OeTHAQgA5GzHZKoE3obEg4Ey/hW5xp/OvyQr9hruwwd5CSxendMJWlmwT9V4QTDl
 RNtn6n37n70wJxjUHdDrr34ItKhWN0AGy71LKcGBrfMenSW2IugB06/kSik3ti2m
 fVI9TJ/gTT4uSppM2MTMmRPw1YR9VOGvO3CED4NfVa4EajCUtMMoEVaFCk6hPhzs
 pSLcnvN+DUVR00RwGQJveHObRCDR10olA0PrLn7hqU2XAlnCAnclSPLjj3pLH9hi
 vWkoeXr8PKNC50yWqclyuTKo+HsUkanDLgfC9kq+ffLvebUayaYfGyYpBKcxzcBs
 uLEJhbh26NBqVfp1q7fTnxvNMVMUnwARAQABiQElBBgBAgAPBQJQOeTHAhsMBQkB
 4TOAAAoJEJAPRaYeEulqcrIH/iO/VQq5gLquEQfzFdIl0I2HIyey/bNpkhDLiLNv
 xPVpflymH9c90fdEXUYrI1HSbYKuACRsiXhu+SaQ0uvfBZuPDQZ7XWweuPB8y+fe
 s86MmAyFXGs8gLisYREnGyltNK3goX+FiZeXdMkE7u+FfFSgMgP02/Ki85F2hj7B
 nFAyaERP9vCeK20dUKSXn+y7+xqbTZBg7Ic9krSNsi77IyuAQ11BMe+vQVVoEhGO
 TdjgE2VJzDiS1FXcvFWh93f3AQ9yAUqkstHMzKAfkwqm4y3SFYCS1xK5YUszImAa
 2T9qZkw+R7dFEM20OWtNiz6P80+BRw/KAL0PwDFCyU4MoC4=
 =QoyM
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.282. Jim Rees <rees@FreeBSD.org>

 pub   512/B623C791 1995/02/21 Jim Rees <rees@umich.edu>
           Key fingerprint =  02 5F 1B 15 B4 6E F1 3E  F1 C5 E0 1D EA CC 17 88

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.7 (OpenBSD)

 mQBNAi9Kb+IAAAECAOaa/3k5Zo+9i/fUPQfU4fzrRFwNifp7ujcxLNFsnMgcWeJZ
 XMd6iGiomTlBSlIHeNKa+JMGPmBTRrL7I7Yjx5EABRG0GUppbSBSZWVzIDxyZWVz
 QHVtaWNoLmVkdT6JAFUDBRBDA7AqRrL7I7Yjx5EBAQSTAf0WL+tTm+n0NFF2xQUO
 ZfxpuqnERjNQY5KaWQuC6qk4UOVCwoBNA24ZxY7TifvhsNErMHMc6HTKGvzhyGyV
 q/pGiQEVAwUQOhrmBjZ8FqYKL4flAQGcEwgAwPj2xt3ITbeUWf6HiqA1u6FiIy+w
 T+GZC2Mit4UQNdjKuNJad7t56Wqem57IhOGDWGYZJoZki65y9jD0BB7MixjuQhhW
 CV/vjdiX+pDxa0HG/75CNS7PVribIuhpbTFR2tG/EZh0sl8yMUpYho81yUDMeHVN
 UV8YqerlqntgqVra2cfPanScFve9YYXVgEbM2wQyWnEG6q0wPL+upmoZ8ppozHfr
 dVYiOonwl6QrgtzavI3tHTHtxDajMJpnQLC0rWHQRmY0Xd9xs+YUpaoUcOQFUH8L
 PEp7d1OQDd6KJOV+mQ/Bf7tZwl7as3cl/16nCMZoDJVGNGCuug4vEeV36IkAlQIF
 EDMEqXeGvtRXff+FMwEBX3sD/1Uf0sqHFBfFtuphKG5ZK9cz12NRANLpVf0welRX
 Y/Yp9AIL9xGGiEFvlma1TN8IA50Gxgxq7cEiHDWT2Zh4Hps0VWmuH9vGwc84D6PW
 JXuuPV4sdfCZnJUj+g13P7ypSlPSS8WIDVET5vG+K5m8jOQJ0NPsWGaZMGknXfLT
 ZDWDiQCVAwUQL8yKYkDqOE5/AdFlAQEmFgP/VwyNP37Vaunu7DdvBblDMpfMStds
 9GY0Jmhe7q1EkkGjwSJHtkn31yPwdb/93d25puCU6rZ1+qw5jKMY9qa8RvCOnnNF
 vN0fOqGso+We3q2rGamjBYtVnihYBni7jCBTJ1lvHixWM5XjyGkIQsRBoh3qNUNA
 I3LeH1ArE3IHzDSJAJUDBRAvxTnlxS1HbQ2/kG0BAeaxA/wPKsCrDl3qJsxrLPUP
 tMfXhGBeOZWPMx1rulCknHpTgfjPpA7soh7K9zi9LAatR08sotD7oAFWslP/OR/F
 DsaLWztFjSmu1laZyU5E7yCIsHgILX0aIsazYW0UoYqCm87FDzHP1kjXs7c6mgOJ
 g2YIY6o3UH4azIigo37B52J6Ng==
 =O0QA
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.283. Benedict Reuschling <bcr@FreeBSD.org>

 pub   1024D/4A819348 2009-05-24
       Key fingerprint = 2D8C BDF9 30FA 75A5 A0DF  D724 4D26 502E 4A81 9348
 uid                  Benedict Reuschling <bcr@FreeBSD.org>
 sub   2048g/8DA16EDD 2009-05-24

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEoZOPQRBADIhhxLB7VS78ooK4j9HuEjamF7QZTXvti7rtJdnJRZtpHW2Tzo
 GWbmlyYBQoGTk8DVuUoQCO6yy0PNe9CVUDxyXz5dUL8/fSfAOhwZowXF7X5mSP5I
 2G70oN9PgdMhxazIPoUlRFAtuDEZl8udtCOVyhiLylXnHj3LJS6XG2oetwCg33hC
 UWM/ZW2XZUt7+LQfdbTvgycD/AqrDrqazX86fI5MjeRuXB75i6OCUGorcWH2T8i+
 P6r3+1A1zjxhXcYMsCI4CDBHo2Z9oq2LN7ullvutfQA3sFR2KxuJmOa7GqHFI7Zl
 PYiRD4Zkuma2bAxIzer65IwQaaC58MCoBxTUqyKys4cv0Lalj6bh+yVArG0v8is2
 5E8aBAC4GptIHT6kfx1515W/1aBiPo+2Qu3227FLyNypKu3x/EwmFu3igbir6EOf
 uQLbjWclnJv2IXZhxiS08EoD6sFFrgDYAcXa3qPpIMjYEEmH5RziISGDwqCazgFY
 63paO2B8aHJB1W+A7jz7PYMsLNXt0JhwG4hLgK8fWT0NKG2TSLQlQmVuZWRpY3Qg
 UmV1c2NobGluZyA8YmNyQEZyZWVCU0Qub3JnPohgBBMRAgAgBQJKGTj0AhsjBgsJ
 CAcDAgQVAggDBBYCAwECHgECF4AACgkQTSZQLkqBk0hwvACeKQW/gMO7z6hv57J2
 4Ed012vx6mIAoL2JyQyqhtwjM3QJ90ZCvB073uTmuQINBEoZOPQQCACi/zTUlqiY
 dA+XNPPH93JSArILJcRIamP8n+Ans6akcluVONe5qRG1txgpclh9/v0Cv3qkr3hM
 Whm3Hh0zCtlrpZbd3oS1qdejpnCJxWTyISI/n6LXyoZ9YHI+IdYkcQowxxFDw+0J
 jIF/ROzHRyAmHqN0ORPyN0a+Xu4st+lgWBCj84op2xzzId+d4mTTyjvlAzbBaijI
 xMdbca3R5V4ISFzGiOHtEWQYb0lUz/DZVXYC22JnQdqtOJy/vZ9IMsSdi0tWsugo
 DGRtfdLAsg6PHIQZgTwbfehQmdSsLAAy43uvs1ywT7Nh0ffCmQawvvOhUOlIrYXU
 jxnIxQkncTqDAAMFB/91mznM5M2NWRhEIG5p0SKJaq4rrXUngMA0Tl4dhrJhlkol
 TfTTlS2u8jSjEK+39Lbs8uWZDXg8PHK2i8LOmgmuf1JfRV0clJMa01D/ZHIBRVB/
 TrJ3ia9rM7EG+2GBFzjkuMEpKBFrW/YLtCJZUdYfyQRjtLRCa3NEfQolvUvA3V+W
 ehixnxIpUJrz3JjLGcDVJx0tkgtFV8f1D6O9WEUc9jLzAM7ehrqbA1QQFlnwDcZo
 T1m0+Js3cIOfiLMqHB6iZi0tBTj5A2h5C/lWVCdw0HYjZkRKc2uG7nFfv++9mqS4
 HyiCcDiyStR01S/CuV5TCLZ17tW1Ihi53EGO8K3hiEkEGBECAAkFAkoZOPQCGwwA
 CgkQTSZQLkqBk0jJ8ACcDgRWhxql58ou07O1MZZbCBzDnkwAoI0ngzxuGBDgIIyx
 vPpqAjKmWnR2
 =WFIY
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.284. Tom Rhodes <trhodes@FreeBSD.org>

 pub   1024D/FB7D88E1 2008-05-07
       Key fingerprint = 8279 3100 2DF2 F00E 7FDD  AC2C 5776 23AB FB7D 88E1
 uid                  Tom Rhodes (trhodes) <trhodes@FreeBSD.org>
 sub   4096g/7B0CD79F 2008-05-07

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v2.0.9 (FreeBSD)

 mQGiBEghRtARBACBmf/XQ3g+mMyEodjtSWZ7wkXEPiOog5koWRiUmR29y/yBWfFu
 M4YUau2au6+VushGJOvF7u5qR0Ii/2MPI0CzUZ3qQ3/WaQvMAIM1N5QXWIpFbcJ5
 5hl1sS3oGQahu0TYbXR9TeXfMmH2dq/UMnW8ACZjZubdGirQQ+ST3kLSTwCg88c4
 H5T9wIRgyFixvOoMZAHXz2sD/1NST3YT98MXJAuJhKwDqf20RLB4nLysohLNBKIp
 v/YBv4LBlOJznsTdGCRgsEnRjG8u6sXGxfp0iFC4P0T7J/zUwV054Sbrqzmo43oI
 0f5qUhYDt/D+WYSdnM/PjNdLm2v+DReiiQmRcDModoBU9eDHJDhonUShIeR7D9zA
 H4C3A/41Y3Zbue9A225HkJDBSnswc+D9dBQ3oOebUvboGq9kP/ItWEZRq6suZbzZ
 2wGUJbB6GpStU6KjY2YpVtty48VS/E8O3lYOoBA/UWZRo/d/z2nVtdBdN7Wpii8L
 OS8pFPNzqKCHZJa3AXjbF+i/KQtIh7cS14PCTH+2Y4xXx8FstbQqVG9tIFJob2Rl
 cyAodHJob2RlcykgPHRyaG9kZXNARnJlZUJTRC5vcmc+iGAEExECACAFAkghRtAC
 GwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRBXdiOr+32I4W6kAKDazwoit6cJ
 Pfb20vKzvBGIAeVY+QCdF0y43ZXQvF+xVK0zYN7SHC646lq5BA0ESCFG0BAQAKYg
 s+2gPS9eP9zIgsKa46liNInASY+ECaE4qKbFeSnMQwlhl0hu2+SI8ZaoyUDhNeBY
 h1C/f+PQ3YDYbtRe62f/aDQyOxKe+p8FEG/RregBrZviSxawo2zioHiTkbV17/Vv
 T64Vj2pwupXAUzwfIq9p8I7XIA+sG9vHVKiathXxygWYlQAeGnGVYFUyPAv6KJFs
 d/bOIB0+3MqwdQ+rDKvBS+dGOXnf8WVEXDQXcf/E0xV9rE2+jd96NkawuuGRGiV9
 KvI0YHL6lCeR0ZOMqdygAgeyi/C4ee4IdToKzsXQVs3CAXLAI0FX9lFTuaAyRCQy
 OY9vbf5LyBFnyf/XqYIJE3xPp5M9doLYRf4X9pAxc1560Gb/OJw+STJGtEpuhN9p
 S+S5CLD99dc0ehxYdsvkXDNYFCiDEVo56uwkNsHu0TIsYvD/hkh3P8a7OZxpY/QO
 pbbat7KtCWgToKvTMt1UAF+vDPYcTKr1o3Fr1+HsbOZJrQNXPHx8pvfD5gkIYsZT
 utZYTKttCw/OE2aTlCe2U8Vvz1p0mcaxqKRkIjPja3fKkDzvy7xc4CUZRioWvBml
 X31N8XDMS5D+1nXz1RgXfVHnMqixmKRgSQj80sQK4Dk02a8l/TMgLMeWkK4tL7Tn
 /JCD4m86wHq1SgNHxoBh2b42aDUE4SN44Gj45EwzAAMGD/45ZzhhhaImBtWmAawR
 SOW/9UbK2rnxqK0+NN5Jr/5e/l/5vGfsVVMROx2X3qY/YOjjNoea/sTjLezvuSnV
 nJn91Gxw2RhnvUC4UcxU7QjLIfg3g+TS9cgKSAMQ1HHrMKUh7mbd+xg3XjqTCes0
 UEd4HNCgajgojwFxhpESEsUXkuwTeei46jDN41EscvQQCkn/tpwW+OwHEO4uVJ1h
 NvesKvb/cvDjX1BVpPWc/sN8YguUq6Fcqmhhy4td2pTnuMDjF0va5HsVQrRqr6SV
 suAu+L+Ni5mNiY+vnqx8UkHkZoJml8FgbCR2Ftbuqi1+PCyfuW/qJOAJXLaeg2dq
 eze0ZzYHVtXTbVKZO/w37H2TKO6K4ElbJjTZi5EVoAn8VaSlx6uv0pfoZn9U9mrb
 UbOvb7DdDlgIRSp1RY+viJgiJ5yNNJYaFg8/SOfZo7Ypxhhs8oHXdOyMnbUU+a7g
 bTQdQJ/1BhAh+IYWfbbTYXqv/JKs1ZSjs/dimUKTWmDjaBPiuySQ+GKjvXVJErrL
 qPdEso8oeJ9r81X6u0GI6ZfUNTO/2WwdkkqDzixtcTHpTf5F5IKNC2k2VU1aVHB3
 wR0HV706dUi9PNCGOczpV0nWwiqM2vMWqf6B5ok94hQGur7pWHHpRmR+yTH+fNbj
 dsMVspd6Jf0Kf5EEhCYSMoruHYhJBBgRAgAJBQJIIUbQAhsMAAoJEFd2I6v7fYjh
 N8MAnA0vfLesP3eTe8VtzfnKtUWHWHGlAJ9a6oA2KcW/v4vCLDjFXJLruKKGjg==
 =S+Kg
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.285. Benno Rice <benno@FreeBSD.org>

 pub  1024D/87C59909 2002-01-16 Benno Rice <benno@FreeBSD.org>
      Key fingerprint = CE27 DADA 08E3 FAA3 88F1  5B31 5E34 705A 87C5 9909
 uid                            Benno Rice <benno@jeamland.net>
 sub  1024g/4F7C2BAD 2002-01-16 [expires: 2007-01-15]

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.7 (FreeBSD)

 mQGiBDxFDgwRBADSAPXXRSDeS8jX0younPZ8dPSW9UBSCn9GKgyV37q6rrwaHlSm
 CspUTL/92h92nhosLkNa8Xq4P7oZJ1NUijPGIXAxuwOjkE2lxBP+0Kxzkjrc0FF/
 ZQK6cqpVjtrTCGBo3+im6v/dw2UnmILM1GrV+TpcmTvyGMJjXT4VB+xtiwCgiv56
 PVM6qCrd5p3NXlveaiYoXwMD/Rza1QobPGHlpX0hkj7bPS0YApNEY8F82yZ0vArY
 NHiQ7lUW+wLWL3+/+h/O8T6tjE7FeKdoI9+U/EQ+3tIbUVpDWbURJtJVyCE/rD/M
 9kDjXxp/74aICSIlRxPMA8AGAP2Zv7a4GZIlhBVmDu3tKlDvatUiRU9HPACOZqQU
 FpR/A/wJRDr64ICA5/N0qB3e9Rgxg66LcjFl40jwM1Hd/8c6JlLE/vcdowcqxHPd
 yEgKZoJoKYN5Y7WXnQUvrkD5O3b68MGfJRjlvxCML+yedD0lDntzJE2O8NQdATnB
 cj1CraaXHvtN5sddw8Gtih6/8p835fcsQyr/V1BKhoTGCTtkpLQfQmVubm8gUmlj
 ZSA8YmVubm9AamVhbWxhbmQubmV0PohdBBMRAgAdBQI8RQ4MBQkJZgGABQsHCgME
 AxUDAgMWAgECF4AACgkQXjRwWofFmQmD1QCggnxa96nN9TOz2aLsVQ2qszwzBBQA
 oIHKFC8JXYP8FH0fA91zLnceWeLDiEYEEBECAAYFAjxaJggACgkQo8kg3R/NoURX
 hgCfY64+KES+rcptZLiA5hoAvX13gsAAoMOiUC/0Non6V/srofbjO8HFM/IziEYE
 EBECAAYFAjxYkvYACgkQDCFCcmAm26bQlgCgjapRIU7hMjz5HBnZgNr418+JVRkA
 oI2DYOP10H4gBZPwT574rkvlrXiKiQEVAwUQPGs/CGfCgI8zwWJ7AQFkGQf+LQO4
 gNf0j9z/LIyKA2mCT5C8Zjh0h7DmRxiiU+4N+bIUuZy7hSVlyWnJMG1JTKMiK1Ss
 nUReCTkNM70rBnxOQV3BlcHksb9ZsrECy8icfslRJGpQmQlrUxppHSyb7UJh5d69
 C5xpDEFUBpTgSZw5JKDOui8gZL14TcthoP5vuj9geo+DWWogyYq0umiaZSDzGeSa
 ST6+ebL1ne+F8hVdxSHcTChFVfrHDWdgAhkGBantTsfbETTwnBHH/k+INu6LxBkC
 JAZMw50vKs739Z+Zxx/gSRd2CDnSlUsoMgJGKLX5MGWmCqEPw8uyBT/T9t8GOAg+
 sx5XjhBhe3PmVPTKNIkAlQMFEDxrQDpVLh4uc9KIpQEBgk4D/RaNrMtwjUoITVdY
 UwNLGdh2JC2d3pM2b0DUoL1rcXwctmc5z3I5co2c/r9k00PGzWv6D3LYboTd/bxk
 lPvn+6uIYmisl7CknFnCLO7lbILkEBGpQHE/8Z7EAI2zUZ/bi3VKcKAFooNPv+2p
 HteKkkVc6z82BWCI0bzH+v/Z0Yu+iEYEEBECAAYFAjxrRMMACgkQUgAclY4JAiON
 BQCgiIf8HrEU/qOoM9BMRwW/1RYeVhIAnjWu/jgHWJVvdPpfG4UIJKpk8DaliEYE
 EBECAAYFAjxrRR4ACgkQjDKM/xYG25XSygCffF0SdJ+WNXkxspiC2BzQAldql78A
 n27raDOotEaHxv5/qatznaWJja5UiEYEEBECAAYFAjxrS7EACgkQGPUDgCTCeAJj
 kwCfa3fOqwWcLbVO9we8um2rkZl4qZoAoKLH4FUXz3qldvVyRvhbSlDWGwP0iEYE
 EBECAAYFAjxrS58ACgkQIfnFvPdqm/WWRgCfaGeUlRGzWSQQZzg2pMz+eC/yFuAA
 n1+qQO7UVEzxTnoD3hAg1T/mLsaDiEYEEBECAAYFAjzPTrEACgkQzerIIuwxO7XE
 yACg5rmr96yl/M/qQ3DIFrx/Md6eJYAAoOStOGPS/9Fly4Dv7T9Cx7Dsz4QDtB5C
 ZW5ubyBSaWNlIDxiZW5ub0BGcmVlQlNELm9yZz6IXQQTEQIAHQUCPEUPdgUJCWYB
 gAULBwoDBAMVAwIDFgIBAheAAAoJEF40cFqHxZkJlowAnA4n58ngka4X6ycZCpXo
 YNRu1R8iAJ46BzE35MLJtgJQztGSnWngoLhCVohGBBARAgAGBQI8WiYKAAoJEKPJ
 IN0fzaFEho0AniKI34jtQurc2v0PlnTAze7AKRmmAJ0Qfp0DhFEbuWqv2dJbJCnh
 9wYOs4hGBBARAgAGBQI8WJL6AAoJEAwhQnJgJtumuDgAn2NODtyfzrThSVz9xls5
 A4CrpDvHAKCywVtdpH4aYFNtHZPt48wxar+mgYkBFQMFEDxrPxRnwoCPM8FiewEB
 nH8IAJ6w9TU1kRNm4ifVR9yp3/FMBZXNnor4FykOjOZISowfFGY3wwNWGnbCSa7B
 5spkDiqnBFwMwbcTQXo56OEWNAir0hAkUEQD7GUMcZmEWy8ZaQIedN3SHhydfR6X
 aNar7uHyi0yi19sgq1/Jnu8DLsPio75gSv1h95anIvoGE1YpkTNGemQ6SyGs7rQ5
 7QuYXqN6P60cJLC0kwEZ4YbcN1OuZ6iSj31TDVp8EzDCkFm6eMQ0wI6UPpdlymxE
 gfFAV3oDlj4ZG6pzNw/ZcvQFeqMNgM+c0j+omZsFlPvW4wfZAV+cevVV5ATosYSd
 PMas2WxPXG7pAwhyRIgyq33/09yJAJUDBRA8a0A+VS4eLnPSiKUBAWl9A/9kN+3x
 nxr8iU8sZMef8PpFMUNj4gp5ARDw/Q3Sx7jlGJEyuLGbeH0Zu/mTvpV6vQzcm3NQ
 EB51WQx8EmizIbtX1PfpyRgKLOXGll0M8D0c5JOdZAAAXYVa6AtFm36rZ9dbM2UM
 XGNClNt9zXUXK/sufCVC1z6vm87I+RJOUhF91YhGBBARAgAGBQI8a0SzAAoJEFIA
 HJWOCQIj7r8An2XwJ4WHnootgfqCUcIfbr4y70QgAJ9ngcIvPy1q8UKMdLk/Y5Ti
 V8TlE4hGBBARAgAGBQI8a0UkAAoJEIwyjP8WBtuV9uMAn0BBM8hO1iCUp9UD8bQ3
 Ptp3xrC1AJ9Bn+yVzTVl1x55X71sglUWxtQixIhGBBARAgAGBQI8a0u0AAoJEBj1
 A4AkwngCupEAoMzM2E10s/451EDjYkdr1fKo9tV/AKDfSYJ2vOJx7JzciRfj5hQJ
 v+81GIhGBBARAgAGBQI8a0uiAAoJECH5xbz3apv1pQQAoNKsi+LOvlXM2GGkzQoY
 Pz9xDxs/AKDgm87TPdaMYhI2P0AzCTHJenYalYhGBBARAgAGBQI8z063AAoJEM3q
 yCLsMTu16gsAn2OJb5oK/QYgO0EpREcYF6EVOLegAKCipUzr16GCumxYGj5cEngb
 7ZkFfLkBDQQ8RQ4OEAQAu5zqbppTM975ccYXxCUx2OECAdzxoSgsJe3kunbvZOSy
 i28t4V+H1+54ks8AOlihN5XBgZAR0ohJ7RTe/5l/EV9rZcY+Tnf75UskLbjifzZP
 Qxd9zYZ2sUbv9oJnX8ORiphIRKlfVjbe8tqdaexQ382FQwUVcC+yc1u2Ye5vffcA
 AwUEALlq/J7TvHXtjeY4BgKsApAxGzyf4roPuXADurCLoaXrUclUsU3KWOFOToW+
 rxQQYAjz1T/lXSOGVzDCaQf6IVIWBYEVu3ZWTI8/amp37hoLdiiU/x0VWVkgjyfX
 VTdIdsmnDaoTAVq+r+JyIubzRcr79SpOEIo5bPl+km/6R/S3iEwEGBECAAwFAjxF
 Dg4FCQlmAYAACgkQXjRwWofFmQkGSwCdEHZJnes6qzSKL6bXiBr0veCSQNoAn0PD
 YbCuiDguaEN052KDrSoDvk4S
 =L0S4
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.286. Beech Rintoul <beech@FreeBSD.org>

 pub   2048D/68DFAE1F 2013-02-26
       Key fingerprint = D58B 3E9D B0E3 E081 EC6F  69D9 CDA3 51DD 68DF AE1F
 uid                  Beech Rintoul <beech@freebsd.org>
 sub   2048g/960F45D9 2013-02-26

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQMuBFEsS9ARCACeJJ0k7CU+53G9GGNcDfJil1iS3QZlgIgCRXnH6zkyWrwCOL0V
 JeGa3EzIvYGyQy+nunwmSmfVSpn5bZYu9S0feACLPVOXs5bHIm8TwEhq2xZkTdtb
 uZXe8+TSqRYqo9rE0szZ1+8zMTvuv8VWlSV5bfSsZad3BexdVvVSY7VXT3ew9KuZ
 PsKikkjNFkEuNYjx1rbNwoAG2hN78oeyZVRF+M4oascxT54Rk3QohS3NgFhI/GFZ
 eJsplVUyQhBjfjs7TETCQ3rdNnJSz/7YYXQVmlh+m+XL8z3Vwh8PDPUeqy3rNwTd
 KFaCU/yFLXCE+WP55FRxb8fHoYvUrTW5MGunAQD29x/4HoFP2ulTV4VLN2bnRK5R
 yS++Ijwt35E8DBdcNwgAhN+AyGnql+bA4BvbJQ6LUejNyAXM/3mmGIgho/58cDrJ
 oYbonXk10FTrNMUurSuCS7VaVl9lPux/Rvhy8XhzGtqTe7B6BmM3i4C9VQr98u9U
 LxkdA6nCZoe0oNZcaNRQWusCiSkb2w7h9IbUVPfgrQrmd80U+uFhTNg0aCGDfhfV
 Ihpp1Y8WQa1zNSElBBAwVO2+g2rXFnzUrFIrwV3dYA498t6lHB75ByF9YXhzkuv3
 TzZgj8mnZiFhXUx7mlaKeEbP1Me+QzvWFRW0nXizwzNwf8Bho+fgLCO/SG83WNml
 XiTFUMHP6nzicwwc0S+YuzxM+6/8FkCJqzubPzETAwf/fIdH/cC2blP8jQJxXrPf
 3raotWPqk2F8EbdpLBIpz4YJ1nwTDbboPDFdDK6/8rvvLA2VLZ8dSOyHZYy80gni
 gzA6uPMbFW7q9xftBRW2kaNaUAkRyaBG2S/CvX+7IYD/OmU7YN7gpEP4mAZ7BWeE
 A+RAEvUByrUqhsGeeX6oMT0JMq/8C+mz1o6Coza9QqPznJdTv8tHW9avgnFu3nHT
 TeWbn/RHkhDvbV4X0hu9CoHrVdOFqvnPqSBKaVQsTM15ZynKoMELK+Uk4jey/DyJ
 HdTwzQgch8yCC6GbMHrowgpf04CJN9Ov3/uKBFXU3/DMuFc0oiXpIfE/DC1WzYMY
 rrQhQmVlY2ggUmludG91bCA8YmVlY2hAZnJlZWJzZC5vcmc+iHoEExEIACIFAlEs
 S9ACGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEM2jUd1o364faYEA/Am4
 DBaFHTlgOdZGzqYqMqIsdGhOHH+d2EpnsC1mDW/NAQCjwSwHZYMf0cv00Y1rbjvk
 +Iageuyp6rIOdiQ0Pksc1rkCDQRRLEvQEAgAp8Q394Hz77rS0OB/sc8klQcOfEAi
 HsEnYjYBm1VIP5GMhShC9mzzw9Je0kCMdWLHWBXc1VsyMcH15luy+rwJBr2YgVwV
 mK5gml/jOSc9dm58YoUXikKO3dJ44kM5JSxfLDfLMDH4TTTmEyGf7RyFlxWO7VVa
 qAz6bsmklHbGxXRC4lGTYF8+4vGJYlc7Y/GaV+mC39hfDaXho1w1O1SpcvKBZWsb
 k0oHgGzlNl5gn1S00ZOjusXHtkUtGsHj8tPGXurBW7aac5iRwMbLbcOy7aD368oV
 kSGUGjHcx1Z9u4O/g3uPUdnsXsI/N7HYLb6dMpumAl/IwEjFXwju/Jxr0wADBgf/
 SNK1Nsg0a97MAci9O1Qp57awCrWB73hNwGw+qC3xSduWmlS4MLZH+DGocv9JOHhW
 d180tTf081svVnWYURaubWsI5N6vgywcXkYt+yvqUcLvttQXYeJS2jTL+1vRErkp
 oEueYzJhZ+sVk+0gG+R6dtsWSwWWXYQ1LdlVeXhbbVWqs3kvGq5IQP0ZngvC8OsC
 tCat6hzTEIlbhSVErdKsrVBYMELZWleJX5RcbX9rPykTJqyH/2bANBAT8uLROHAk
 pQ4rnQD3TeCSmP0pDYT4TWAcpxe69aU/a6p591kW0CI7dSZVHrao6q+hmHLWDk4K
 ELGLyiM/IaOrKyDBPi8C/IhhBBgRCAAJBQJRLEvQAhsMAAoJEM2jUd1o364fA+cB
 ALaWj7vG0OqUqGgLxCdSZw6bCME/vU/TNRmn0IgAYOQTAQDe/sdsNUs/MzFJi0re
 0roDMXVUSkNFP4PN4u5jyuzVBQ==
 =EWeR
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.287. Matteo Riondato <matteo@FreeBSD.org>

 pub   1024D/1EC56BEC 2003-01-05 [expires: 2009-09-07]
       Key fingerprint = F0F3 1B43 035D 65B1 08E9  4D66 D8CA 78A5 1EC5 6BEC
 uid                  Matteo Riondato (Rionda) <matteo@FreeBSD.ORG>
 uid                  Matteo Riondato (Rionda) <rionda@riondabsd.net>
 uid                  Matteo Riondato (Rionda) <rionda@gufi.org>
 uid                  Matteo Riondato (Rionda) <matteo@riondato.com>
 uid                  Matteo Riondato (Rionda) <rionda@riondato.com>
 uid                  Matteo Riondato (Rionda) <rionda@FreeSBIE.ORG>
 uid                  Matteo Riondato (Rionda) <rionda@autistici.org>
 sub   2048g/87C44A55 2008-09-23 [expires: 2009-09-23]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 13002 characters]
 LlxcQeUB
 =cJab
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.288. Ollivier Robert <roberto@FreeBSD.org>

 pub   1024D/7DCAE9D3 1997-08-21
       Key fingerprint = 2945 61E7 D4E5 1D32 C100  DBEC A04F FB1B 7DCA E9D3
 uid                  Ollivier Robert <roberto@keltia.freenix.fr>
 uid                  Ollivier Robert <roberto@FreeBSD.org>
 sub   2048g/C267084D 1997-08-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.4.2 (FreeBSD)

[encoded data, 13728 characters]
 izq3ic4=
 =mgE0
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.289. Craig Rodrigues <rodrigc@FreeBSD.org>

 pub   1024D/3998479D 2005-05-20
       Key fingerprint = F01F EBE6 F5C8 6DC2 954F  098F D20A 8A2A 3998 479D
 uid                  Craig Rodrigues <rodrigc@freebsd.org>
 uid                  Craig Rodrigues <rodrigc@crodrigues.org>
 sub   2048g/AA77E09B 2005-05-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEKOK8MRBADOO9VIucM2dGygVera0+Hcu9ud2f3MrcfVgsB7/awfE/MgIYtC
 CFtCJrD1Ml+p/spmiuzJNDSamT8NHywsG5R+GO0EC76+mfL3hwXvGUJoQV+NcDu6
 99s6OUWTimi5OPOURzG7lXYpO0wVysx3R5Nzg7tIC06fmXNXuj02JvCm+wCgqkPx
 nZgCFoqq2mHoiLL59CUExbED/iOnglDOuZsncR9xRZJfbSLUJf5z9NE413FXAx3f
 THY7+akGk8kWChrOeyIvLvSGmkHHFQXgh1umG4fFd7TCJ0Sexh44s5q0ROjEK4ge
 nwAsS0iheMB6JqW8ibBfawr2iwu3ZAkqfelU+NSbHm4sEeHxEGyJtZKA7rOPGDm8
 YOBZA/45n2E/Z6hv6D4Bm1xEDGNICK28uTqzXh0wyCJJtVOortd4CmKZZrZJj7am
 3aDdtFUZ1yZc5FW2E0xLa7Oz8HUj7eMT7Ljfd0c5yNna7WcNjqWNAz6WMhHByRZv
 nOPiUMQNvCbyrKw9OsFKNNbrSnjQcc/5yy0SiIMVm4rydXzK0bQoQ3JhaWcgUm9k
 cmlndWVzIDxyb2RyaWdjQGNyb2RyaWd1ZXMub3JnPoheBBMRAgAeBQJCjivDAhsD
 BgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJENIKiio5mEedzB0AoIXeENkxV41KlJMV
 z0ozHJ/q1ESdAKCimzfOMwz7Qyauo4VHs4rk7NEPerQlQ3JhaWcgUm9kcmlndWVz
 IDxyb2RyaWdjQGZyZWVic2Qub3JnPoheBBMRAgAeBQJCjjVzAhsDBgsJCAcDAgMV
 AgMDFgIBAh4BAheAAAoJENIKiio5mEedT6wAn0IjcGqARj8Qe+JZThbQCQbH0ERp
 AJ4w1pYLdsKphwaEB8GakvaeRsrBTLkCDQRCjivkEAgAo5DHUcjEBK54Vo2S403y
 InnfqiiUDXqb8Oof18CICB6JgA3NjP5g9BE5+7dI8relt4Q0ILg2IJvISIlfmyDl
 +GuegA3dMo1IrghmtI5+IWN2mm1iNy96jpJ1TQhvHTFDlETdV/BE57CcO1ZnKHiW
 m9G3GjnMrunVyLMEY+6TJ6ykqP2VzYBsc847iCv477LdYFe1+vedZb8Bk9xpeeZJ
 tuT3O+JiR+B/SHISpycxyM3ei+C7eRRC8wV+khOw/8xirJ1Wzyg3GrolQPtJsTNG
 mqg6DXIYPY5wbF3SUBT5ZA7pLPxXhUWNewU/8mXisuM0hp7nz9VLQ4JfbMuvGF2j
 wwADBQf/SCUw06q5l8qdJ9G3WFfPOE449mq5uXHGlfeamCkjx9/SzI/8yldrxwdF
 5XiAZWRpeQoksUbPI+tmxWqi8NDxt+KLDNhSCg0+C8KRFBY0ZI4CDmUg+MX9Mix2
 ir/RK6eoEYNXdt32raX7MzQP87LTL+cnxJzbQ702HYpVqrJUOgSRwQ3posbp7hwV
 djfiE38r9Hd/E4ZxxAIT3GafZ12KzxQZ8dSxoa/2tP8VfAfe9jt/XX4F0QD2yIGV
 2wJMd/CZWTZgDfNW1anGR+9AyV9dT+8cYi36fkgTQb5rN25rJKzHd9RA/EGJXSU4
 l1hNG4gBpYjF5gD/UTuSgGI6XInycYhJBBgRAgAJBQJCjivkAhsMAAoJENIKiio5
 mEedTS8AoIa+gNX84jClqNvPR5lMlQGKeB4HAKCaEmhTA9kGSY5JW3hsfDiwfr0a
 PA==
 =hHZm
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.290. Guido van Rooij <guido@FreeBSD.org>

 pub  1024R/599F323D 1996-05-18 Guido van Rooij <guido@gvr.org>
      Key fingerprint = 16 79 09 F3 C0 E4 28 A7  32 62 FA F6 60 31 C0 ED
 uid                            Guido van Rooij <guido@gvr.win.tue.nl>

 pub  1024D/A95102C1 2000-10-25 Guido van Rooij <guido@madison-gurkha.nl>
      Key fingerprint = 5B3E 51B7 0E7A D170 0574  1E51 2471 117F A951 02C1
 uid                            Guido van Rooij <guido@madison-gurkha.com>
 sub  1024g/A5F20553 2000-10-25

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 6864 characters]
 jwCgnb++jBLoAgqu7BiWMBVe9sCLfMY=
 =qL8T
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.291. Eygene Ryabinkin <rea@FreeBSD.org>

 pub   3072D/8152ECFB 2010-10-27
       Key fingerprint = 82FE 06BC D497 C0DE 49EC  4FF0 16AF 9EAE 8152 ECFB
 uid                  Eygene Ryabinkin <rea-fbsd@codelabs.ru>
 uid                  Eygene Ryabinkin <rea@freebsd.org>
 uid                  Eygene Ryabinkin <rea@codelabs.ru>
 sub   3072g/5FC03749 2010-10-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQSuBEzH2sQRDACbyiYQw1PE+ibv2KuXe5HmlHtZoMAN5/KaPOHsyNmY3IHLm/IK
 yIHjrjvl8JFGI78OkY8nalplLRtsY1F6ZVRVXR1Xb0Bez4wXn4wN5Nkk5VKwKosM
 DRc51OTKB5ke4wzTN4NBkaOt4ZOoiJwXDVCHsY7JHxAR9zBuhyB2VRusFOVtJxkR
 W29lmVDaFTY3JDnrWVPTmsNA2jubEiBkDFQyEl8qqJEvVZIHM0I3X5TxesekC5BA
 cDSsbyIe6MuSQcr9/8L+RpChP/2s4Wn4Y8ElF6AJGaP9OZCSlfzSMCIEyQ2oWPTi
 xKBS9/gDGy7mk5qSp/jMfr7hw+3C4Q661/TfUT1TXLBCqChXRz4w9CmjzIMPxBe9
 LwUiqhY8iwKLubaX9shDlE7+7unBRpx/nbsD1v/ceV95tcJtWR6Yqez0npwb1ZeI
 y+L5oPXB7dz6/qV5W/MPrq2U8GBECcG3T+yDG3JJQ21irF32tNVEJ2NgPlykzuQ3
 QItCVyeks5fb4fcBAJl1JYzNHErP8O/CvXK19V5rMZjISNOLa8wVFh4BcFsLC/4l
 6FLF9mxGeL/KGY9bkrwJHX8m+BrbbOQ6Me+L8F3dj3xxcHyozQdcb/YZoM68r+Vz
 hZcuD0qBwyT51ay3joywOv+MpvQYWEQWTzmeeQYF/3I89rP8uCb78MBxmZ8ZYl2V
 D1u5ayXr4fU1qyz2G0Sc2F/Mmf2ztGU+qagz4N9EVc2BfoaMUH8M06HbBeABTq4d
 L8Mmtkxuw6WoAjzqVTt1UzU1kH7KVDvoCGxBxA9lWtTmwEfR3ORDiIONdDGGr6uG
 BEUrXJvnpiCdT1UZjRCbu6V7GZdyP19J71owoeK2/8TNfy95A5fmf42tbDXMcYS7
 l854SUyAPV3W4hizbkH2qMA69IQ5MimpAFPewo66eybY1quyE6dSoXF3BOUyWuA0
 E5QVax82LG/Af0pKN2rvS/sAlJ4+ypyoTTJJAyzJlKZWiuTDTs+J5WQi4VmcYWb6
 vBGkPZtZifuJ6vWCsUn8Nz0DxYXe1CquASWjmTvjTAawRe3iojSMeZqPnJwHC8oL
 /3TYpVp9HuJyiJHXLv95at+6GTTipkBRr4Wb01vYTM9PxfSWodemJgpApAO7NA+f
 xuiQImuIzYGW9TD0SNGzAAlAS8nlVagHkElC9svKPowr7NSa3PSvfjaC0hU+Chot
 +xtrOPi4o/FYTMDlVXf8zONkpvtIbdgq+5Os6eiU+BZWiOV6XH7v5fE2EeGV7af8
 0JtBHFFdCF6k/mcAZHVDnOGHbnxZyJTN78/IAunQJN8OkaglVZw1hs5/RLYBD6yD
 DLg5X/L6Q0E9/QREsDNR6M9+MqB40tMXhEbgQ4KRUVB1tvLkR9xMJdXES8HeZGz+
 RO0AXvdtMvDTGmnGf8TfbGOuhZnxQeP5JEgpzDJioF4Xyh2x5nzBpWTdGKUtcks/
 NBLqhYAUKYEqDH2gkoKV48asWg+zk4tnXuP4zCBrYwjpvtIJ6K2ohcS5mfUC56aC
 11ERZRSa9Dv7m7YC1qwOcm5bzl4Wo7YTsjpNA1qNN1SRfj6Tg4EwDlMI7yXdVc/g
 FLQiRXlnZW5lIFJ5YWJpbmtpbiA8cmVhQGZyZWVic2Qub3JnPoh6BBMRCAAiAhsD
 Ah4BAheABQJMx91bBgsJCAcDAgYVCAIJCgsEFgIDAQAKCRAWr56ugVLs+4w7APkB
 Zz1D9ReL+KjraRZBZ3Fpm1tkfOR7UiLGQ3azWPaGpAD/XTyvWUQ9Z5bq0tlpvl0F
 S49eQKgElc+NobSL1dJTYIu0IkV5Z2VuZSBSeWFiaW5raW4gPHJlYUBjb2RlbGFi
 cy5ydT6IegQTEQgAIgIbAwIeAQIXgAUCTMfdYQYLCQgHAwIGFQgCCQoLBBYCAwEA
 CgkQFq+eroFS7PvmdAD+OlXfczBZQvCS5gIZmRZCPBWLK642agRmb/nd3tG5kg8A
 /1gF/+8YHvIqfPkieazssEgsbRcdLR69BEcS/dRGVAlltCdFeWdlbmUgUnlhYmlu
 a2luIDxyZWEtZmJzZEBjb2RlbGFicy5ydT6IegQTEQgAIgIbAwIeAQIXgAUCTMfd
 YQYLCQgHAwIGFQgCCQoLBBYCAwEACgkQFq+eroFS7Psg+wD/XddXeZFpl1vRZHCW
 j3qjnJ6EpVx6jtMAr6/74TtNQDIA/1KPGg072ZpF5a3sG7a28hHHdYI6PLZRV6pe
 xhtcuTjfuQMNBEzH2sQQDACjG6PeNnW/ktQEwZRIbmG87WZQ5xeZ1LeJi/U+5bZu
 abW83T0EeBAB0UXKRw2n/sUG0xMSj141JcvUtACwK0VKJ3GpCXV5QAbw1QSORGw1
 ecyJIhQOOTv4ChRQFRio0nm3vDM/MVELLRZga266BjzV2K/Ip06TCOfllj518uAC
 TB5jtoNL7W0fJi/sARhqYuZ4KTe8w72bBdJQilwYjTd/I+3ZrGtciKEYO6lLdlRc
 wZM68J+JQ1lWLDN0Ru/IGNsKzpwYMdqdvNGWuB64cgNyULhSwhWdNFQLTwywXMe5
 LFloYSoE2cA5veGNbTnTT/fUtpjxPREnqVu6+KQ22Ah9ALavZxcLJlO50fk+BGwZ
 SspTTo22YKb+Orr6OD9d032/3c07YHHNsHGdfl9l1wWRXRcOXTIuSTQXf1P300WI
 5TmehRr167DBq1lyHY4NNd6PY4lujlPYVNohtrz7z8jzFsmtopLWeA+dzEiOAxtn
 MIp0k6bmECFl7VwmIcBCWWcAAwUMAJcgSolujAeSkYIr6JDugBOmcMjnZvsELRDy
 C9iZ7cOY3PyZFCPJPyhj6jKZa3cPPUdapI8LxvaIPwgZgLpNUsGpU4DI2Ua4IWXB
 8ZB+cz4SHVBYvdfrPmoLO6G8D1TC/4HOX7+fhR/WgLY2fSkGh9MHd2Q9tHscW8wB
 5IGzE7XbqH/LBG4aO6rP+pp1nY0bCTH1I8pM1cesemo4aYSnPSUo8TwGIkteyn67
 /hK9CEegeeME4ni8oCz6i6ADjlFlGoYDKbURDL+7tc+0aDkW7T2xR2tU/bnYMHit
 1ZERDYbnnt9cSIOfzkKKCVGVaBrAz7Kde/qUKHwTBOE5WAorTCcjIrF0dfoXte1N
 Jm+LhEcV8FvUQJII3XsM1IziyXYh78HIbbSCUJ8o7Ubu11ThCqOsKFc1OXQaJ73B
 cMU3YkExgPWQQFxEbmCHN2EfDhcMyQpxlQf1REBDVvPG5takhxrzqhwahOFUILAL
 U+H2p7ftqy+yiSG83KJaPdN+gf+tDYhhBBgRCAAJBQJMx9rEAhsMAAoJEBavnq6B
 Uuz7gCoA/iMltPIt/6YHyrNh/riEP6Zb9rWOzf588Zbkdvgbwui5AP9zHdexwBA5
 Edu6GCfjXE66i3XaSUcQWu+g8BMQUo5Huw==
 =xPkv
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.292. Aleksandr Rybalko <ray@FreeBSD.org>

 pub   2048R/4B7B7A4E 2011-05-24
       Key fingerprint = BB9F D01D 7327 0B33 B2F5  6C72 EC49 E6ED 4B7B 7A4E
 uid                  Aleksandr Rybalko (Aleksandr Rybalko FreeBSD project identification) <ray@freebsd.org>
 sub   2048R/99F9F9EF 2011-05-24

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE3b+zABCACwiwsbEdmRqU1Tsb/ErrEGYPO6uGPy04niDFSwT4EoW9tJmX94
 bZSfD07hMUHm3yk3sSNBVPYYqvolCd+Wa/aSBo22Ru8MT5gtFT6QmRmo0r4ye6hp
 0jddGbTE3gS62ojQCDayRrSWhqYDtxMTVhF28+GVf9Yb8xD7booHz+soOEOp/lyi
 rMbAKKpAKKzlbTg+JF4xuNAOCQeYq/iw+5/Yv0WRdlPFlAhefpC9HGnm7Ci2oX9O
 yadz6O5B8Z3mvXrprHVf/gZaxpMbqHtiCwUCOjyu+65AJxZ2RtXOZGlgixVldzZ5
 1/PkPjf66PNOE/jei7lQfoiXSelbMsn/0m89ABEBAAG0VkFsZWtzYW5kciBSeWJh
 bGtvIChBbGVrc2FuZHIgUnliYWxrbyBGcmVlQlNEIHByb2plY3QgaWRlbnRpZmlj
 YXRpb24pIDxyYXlAZnJlZWJzZC5vcmc+iQE4BBMBAgAiBQJN2/swAhsDBgsJCAcD
 AgYVCAIJCgsEFgIDAQIeAQIXgAAKCRDsSebtS3t6TkqnCACNpw7DnH7mPLVtJ9Hk
 5V6kzsY0Fkt155HcOw5IqK2UJUqGZTa1Y6SMjqC7Joq7P/3myjWOyN62xByQ/kcL
 VT3Ee9Nonknkjx1S/7Y9aVlCoT3koB/no9BQRgTsWX2oHUEakBftYq/8sx/1jzAc
 YN9DffiOIfXH43435MtYc5dct8lRaQkMXL6hDrswqqnsC2lefISiRojWgSpX2Iax
 VsR9KA/gDGXcFQLYG19ivgQ/MWMwfHCQd5EyPa3JGsx/G3Me0uA2YC8igzuEG/PJ
 29G2eAhA48T1iDbmD7rHsMRdNvr9+0vHemNLyBysyzS+d1opwAE3HPeFYslbRfQp
 UxJuuQENBE3b+zABCADfEA5d/HafarrCijuoKqv7miY4JeknD9CezUiI9KgsjIAQ
 Nv6ObNUoAAZyO/tmKyK1c6ohOQn1m5knH9ldSU0aj/loeBwD/tSjqenqI3rk+XH9
 ZUW1t8U/2fEt152hbaZIeW3X5ovSwNJxL5GCjvqiy1bNq6rV7hiQfnwET3cV/FmA
 KJUlxRZKNbJn3VutSIF4vgOVJTdZy/0dDcpUubHcfVFXeZRiBMQiBqy/WW80VL9l
 /RZ8js/ArM7fNqnHtGN4Hgxfh5HEUJtQncYs1JNkFiUD6aYL3zsJAbcXcfyEwo6Y
 Hpsn8hxuEYpAVzsaO7E63Vdgyag1b8ELRBbYpranABEBAAGJAR8EGAECAAkFAk3b
 +zACGwwACgkQ7Enm7Ut7ek5nnwf/V0kzZ9N92h8oes2ZWwnuWWbZewdp5p1AZmaj
 FDeM2Usiqb9tOWizJwKI6B9Z66S2TdLTrCwtcPWhrr/MPfWTNffCgrVI4jOczCeT
 Jm9Y6OBVdlT16sqF2gskwLlA73R64TYJxS7uYAjOMvhFzXeZuJv2BLxSI2NBvpfh
 HfvoeBAM7NRmuJrUXz90ik117bzEcuEBwIDRc/fGUvSdWm3a+AmbVtyPR24RFMGb
 OK2UWrTXa9TiTAKKLWKyDDYf/B4nOtGoF+OCkpwLgTNJE5kwh+PnJjN7wsdiAvL0
 2cUXjLV5wX/C2w1FFMtM7PA/7aURr6CNmS+00mriikVFT++FDA==
 =Q1YE
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.293. Niklas Saers <niklas@FreeBSD.org>

 pub  1024D/C822A476 2004-03-09 Niklas Saers <niklas@saers.com>
      Key fingerprint = C41E F734 AF0E 3D21 7499  9EB1 9A31 2E7E C822 A476
 sub  1024g/81E2FF36 2004-03-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEBNxyoRBAC22NnMqcH1hXXkz+jC+U2QGzOJdGHZtLRXDRpS4blFtRgAf4ab
 tZY6LJUMnjmdgaPP3Mc7YE/ITF1hGnzYF2jbJazNm17nMSP/66dGJt9dK4XAE4cc
 5nYo3GnEkacAa1zUvM6e9OGaAIkndBDUW6+a9aSQNcNyMnYL1/APv+wdIwCg2G4C
 N221QrjrGbxVQPiBM51lY98D/11d/h8aOHYkf+nirhIj9GvRmXJfD3RANZUDjOsj
 OKGgUNlXm/AT6I226v9urfdtrhMg+5zdO+I2p7dZMad/RpnSYo0GMdLRzOlN6aoI
 +4JYoACq2C7iR8pmItb+L4Nl5nNBwmcLBXD+HaZebGffZy9Uvy/A5G0ty08I8LKm
 5STvA/kBMybZhX+RTq5v1Kzau63bMBJR8MPHyWYAIBW2wTMJM1ndW5RrbIMJ71qC
 8DFFTHFJd97s/fqBMQ9rj094CdDxCYQJUkZy5+qiBkRta//iSlgsi54Xhj9prgPj
 nBMWxUjAI5Ih0VPIp3/z/q5aQRvey8Ro5JWmduzH0KpLv2Qe17QfTmlrbGFzIFNh
 ZXJzIDxuaWtsYXNAc2FlcnMuY29tPoheBBMRAgAeBQJATccqAhsDBgsJCAcDAgMV
 AgMDFgIBAh4BAheAAAoJEJoxLn7IIqR2/y0AnRetbhzvjj3kKOV28bx2Qt+YRA/j
 AJ4yY9wDPJpwq63IsGeo3BYXi32zPbkBDQRATcc5EAQA2SipeeJJjvrzqqILHNA7
 X+m/PAJonO4QhyIEXXMhzNGdiUVJ7wli23gGVF0Cj3V97Yw5KFGco3qOvvsWkO4c
 CLwd3NHbVL6OHKM36LcFd+a6RiJO9qAGGixyqUIkqYeWCmpObihrkZy9WADsSJTc
 /qOrLghJ0GyR4Ga8CoFNT/sAAwUEANfA3lWeTj3QZcDnJZYejt1aJWt7oUBQ/KOc
 HhTjY/A7zkQsAdgbcmuhzSiIH6eoofTwNOl/Kl0ieSdIyFMFfVxrmYEN/HUUUI4q
 J+BgWZgppinaeUEabnZPfY03T+ZanJ3DmB8s8x4HdpFi3jgtWY0KfDhDfHtNIeRu
 CYmLAzjYiEkEGBECAAkFAkBNxzkCGwwACgkQmjEufsgipHbIOQCfSaudT6wnsh4G
 6D9TZkji6aDqUBwAoKqxWnOya/v/MqcgrXGSCih7phIL
 =Hz+C
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.294. Boris Samorodov <bsam@FreeBSD.org>

 pub   1024D/ADFD5C9A 2006-06-21
       Key fingerprint = 81AA FED0 6050 208C 0303  4007 6C03 7263 ADFD 5C9A
 uid                  Boris Samorodov (FreeBSD) <bsam@freebsd.org>
 sub   2048g/7753A3F1 2006-06-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBESZt5sRBACyDUDxsmkdq0XNNJfbsdVO07/vtUc+rP5hBEdMzbetPnLdujSX
 JtwzS2b5kQFk1ONAuTs9udlcZhhq5T2FIyhqpvgLG3tnt4gDabRgFsOL6oB4dFKv
 yL5emRwnch+wYlwfaoWXsXpWfdHQCwFfL39lsYLIR/aXcMwjXF1wl9yl6wCglkCt
 NECUgmsoUYE1iOyC5PnqHkMD/088reqeJuH2hWHupCOihIOOddQPiKX3EY1Y6piO
 I3aQFxOq8BdYw+3WAlBs4vegMmzk9MYEwP2STsVcPE+eu55m1GCRRds++oyv9tQO
 TFZVsYEuvJALvHSW3InTGHWfhQPrHcdodyRjhgo2bKY1RwO3RHYDRRQj5i8LDn/9
 kRSiA/9Y9Cl8Abr7kuPbgw7uWb8lRta9/le1UWQXpU6GAZHXEgppHenDaRqvbaag
 MhXXiKuuFAz4LNHf8UDqyQ4fjjfR0EajIivV17hpzagPWIzzEdr4j3RBpwHMYLbV
 1yfyml5QT46amMd2Vwq83Zgn0cUObu8E0IITqTMkweEvH+soOrQsQm9yaXMgU2Ft
 b3JvZG92IChGcmVlQlNEKSA8YnNhbUBmcmVlYnNkLm9yZz6IYAQTEQIAIAUCRJm3
 mwIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEGwDcmOt/Vyam2gAoJHvCp76
 i+XiNv4R3pJgG0ZxTCjOAJ0S46VswPDByVJZNF95pfy1qEDb/rkCDQREmbekEAgA
 vAUui6QrSn//3FHeSvH1smd0432C1r8IHvR7m0Ki+F1cRolkWF29y6JMpoPcXrWC
 D5OpGfZaZQ9SwhedFr776xAwMDWAHlrHEpPC4OE3RPq7YWENc40hL+ZKfsZhGA89
 H8fiU18UdDlARgg1PDBbVi+F4ZFfKSyNcTUO3brIIpUy5OfAdTkgl3JFKERlqZic
 ZWjS9PXjsyaeTYn1Ny2T9WZqbk9Ghsb2/t8bIyayu9KNnI+vRSafRtaomeUEsKme
 YZyU4pLutea2Zj6u8BtEVyxp9Gcy0Whn/HwQc/FZE91Z6UzViucBqKmFmw3A/OHF
 HV3DAxd2ctkBrt5jzgJA2wADBQf/dD7RVzfD2ea+jpgqJW5EFDqYebjPLab5GZJ6
 uUWWZu73ynDm92lemzcT67JYirU0H0sQ6QmcZ9ZwqqdW/taCjvpsXPFb88B9AL9c
 aQD41otxgpCF/zMQwgS24DCrdtPXiKceTjHNEAMOM9xS3FBNAWjy23Jz6rIt3ROD
 o0X3iAta9cT71Q6/u6BYo1YRuLIAWZ1rpkELb06NUxsVuEQmBKGMBKf00LEw+AV8
 0FkaEukzFuG1u3k2qkeFJEZW0C6d04JT5jsskRiTrIzkd1FTyaEdueaZoiPBQybX
 KE9GyClXn1RMWA+dzAjjNvJOo556NAIpebgvXMd1rHSRxumHdIhJBBgRAgAJBQJE
 mbekAhsMAAoJEGwDcmOt/VyaOikAnRQNCxBdrbQSOLIxrChaMU5tNejQAJ4hpoO4
 tGfWhh+Ib0+vCD7UaSphYg==
 =fafd
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.295. Mark Santcroos <marks@FreeBSD.org>

 pub   1024D/DBE7EB8E 2005-03-08
       Key fingerprint = C0F0 44F3 3F15 520F 6E32  186B BE0A BA42 DBE7 EB8E
 uid                  Mark Santcroos <marks@ripe.net>
 uid                  Mark Santcroos <mark@santcroos.net>
 uid                  Mark Santcroos <marks@freebsd.org>
 sub   2048g/FFF80F85 2005-03-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEItZGARBADLwd04ILGjaq1OV/1cNTU36Ggwx2fKt1OQSFgfzkQDB2Ff0R/P
 xXLBhx3mVEcTt/vNcniqyOA3Pdla6nVtxFFMDcXhEN/d6Xsv6UY0s5B6zoJ6tx9J
 2lpP2YQeA0sCGPnl6QjFYX1pbehPO7CSen0ApDBmfJx/B0J8AwCh9utzmwCgwmBt
 KvC79obIrPNdTr8quYyYZf0EALQbGGXPhgZN8A8u+PebwIajKxMTxqPnJbcImwRd
 GOjdRQ79BT2Ze3g97ReKjQCCqOFY0Gz9XMd+OGfG5MfDwe4pGXx6DUxOYOJqL+2p
 5MjDbpmcmemtIaC1AwchhCsqcQVo7jbH4ewsxsb33cIktX6lidVxjUZQaTioPcah
 t0eABACy2edSB2D3KXk7zoNMnfo2ew++Aot8EsL4TOVOrJkx9p0gEKKgL4ED+y8Q
 4cw6chINnqQWIQ4WxyTHeVjw/SIgVfOBEFhvaZFtC9wfDTk+1G2DeMuyw/KDK7fi
 J9KOUhAtKPKTl4D0nZN5rOULgPDgq5WaTjxkWLcs9UjcpDCQhrQjTWFyayBTYW50
 Y3Jvb3MgPG1hcmtAc2FudGNyb29zLm5ldD6IXgQTEQIAHgUCQi1kYAIbAwYLCQgH
 AwIDFQIDAxYCAQIeAQIXgAAKCRC+CrpC2+frjrUsAKCWZHuLZGVk+bWwOh9E/eH1
 I5FTzACeII0hwrpqPwlxOyNHMiF32+SYc9+IRgQTEQIABgUCQl9moAAKCRAVEq5S
 cndxfy5TAJ4o2kmigp9+7Pg8vtGQeJwSgk9dSwCfXo/xBlHKAF1q0MF24MDcLx1q
 4m+0Ik1hcmsgU2FudGNyb29zIDxtYXJrc0BmcmVlYnNkLm9yZz6IXgQTEQIAHgUC
 Ql9s1gIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRC+CrpC2+frjsirAKCdbg00
 iJcryV1H8H7POuWA5cpqBwCeJC7RbQcBAU4hg5kY3Q6yuVLYD9m0H01hcmsgU2Fu
 dGNyb29zIDxtYXJrc0ByaXBlLm5ldD6IXgQTEQIAHgUCQl9s8QIbAwYLCQgHAwID
 FQIDAxYCAQIeAQIXgAAKCRC+CrpC2+frjqw4AJ42EWPG0JCtzDpUx2fCWM73SJ0x
 NACfRxkme8yMSHLPRDYFQ6up3y98+VS5Ag0EQi1kixAIALfhPatM8pRDvjbMuw+x
 z046aF+ygNF3Z+jQYMv2+TNx72MUa2GMM8WloInYu/sbJLuv6yMXKbtGx2wQAAkB
 Ayd8Ink2dniabAummzHuRPLycQ869QJGg0+xCq8pifCsUXh3Nec4IFjkVs73hn3+
 fcyN/bSO5uVzAsLgRczJX1zhipi0joFijFW8V3hk61VPDuB3UM0EzqelA8VMsreu
 wrs6N4BCRVcqDvncTrV+8CAPdRuBMk1NFffQTM79G68UIq64OZSs7uJTOsqLj4uh
 EE8V1rbqoaxNUq1KKIcQxIOMtyMbXnDuM5fXTqKD+2MEmiJE1D7nE2qzmczOFJ+9
 qZ8AAwUH/Rvg8dNLeZXrsYL5A249GjKZOdv9NpmSpEBtjp2mMeodZBVO6u1KlcfT
 N078WY3f/Z3vTt8mqg6woWS4M3l37mDbNb7508HjVC8rALC3ZueCRb/COvTssxBV
 TCvRcJmDYdhGxGAAIRGPiYx+9UF94AE37UgxAiLbTHCCimJmMn/tXvNsX2Qr1oKL
 oYI6kINNYE7uZ9oqZ72zQoJdCBBxyBwRRHj0axzNgtXjK55yUrHDYDnLvu1dr23K
 85Wje6ZVWbKp1+qbZ0tPmPPWb7QYH728MDHzkdcPp+B/QSiJPBxv25CXn9hZBLYQ
 sAUeOwsaps1T4OJoybYNQihLifueGC+ISQQYEQIACQUCQi1kiwIbDAAKCRC+CrpC
 2+frjhtvAKC8dlrD4umaE+9r0LyOx/+il2rXeQCgvUTSvbtlZo87oKp0EtGn++rf
 IdA=
 =F4/l
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.296. Bernhard Schmidt <bschmidt@FreeBSD.org>

 pub   1024D/5F754FBC 2009-06-15
       Key fingerprint = 6B87 C8A9 6BA5 6B18 11CF  8C38 A1B7 0731 5F75 4FBC
 uid                  Bernhard Schmidt <bschmidt@FreeBSD.org>
 uid                  Bernhard Schmidt <bschmidt@techwires.net>
 sub   1024g/1945DC1D 2009-06-15

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEo2DaERBAD6iTY24oR5YgIAGmKudAPxNNLLaZPm5tsa1eQjNCRp/WPLIXCS
 /x2oZPk8JoKOPnHNuvfzKnDwh3sB/hKAQOwSTHmtKQ7Gq9Uq/IpuQXHOfF3JqJ8p
 4pOEHCSdJPv1rGNdv2Uh5Pmas3qfkI1pcn44B/XAYDVoYC2CsHmTHSMfwwCgwKIP
 BELVfQZDMaV/Zkv1etazaLsEAJXHS06o4TFVmrHzvhMPlBmS/MDJyt04MaqJwCkh
 IzZGpJ6c2rS+a9UOj5Fy8zeim3f94U5L4pUJUmn2SitHTGm14A+ZN7r2dmBC8jw5
 Oki0tbz3yObM6KSzYV2BuZ7BLP65KXAlUnHM5h4rw/EJaTL6bm0Z0sOLpc74KnZd
 qgi9BADzkJnZ0VKRRZ18xfdbPqa8FMeHJI/IhlBrwEPSeRqEjZCtTYfePzutbpm7
 YRpXk2cMe+k6Xt+FrSVF4elNT5/b3SjWjmZr7jLQ+/RvN+AH/5Ru9bQHVfuL6uSY
 zoHgl9Y5RKJMkzWfdn1LknaRIqE/ciWq22cESYJ8e/Wrk8lFVLQpQmVybmhhcmQg
 U2NobWlkdCA8YnNjaG1pZHRAdGVjaHdpcmVzLm5ldD6IYAQTEQIAIAUCSjYNoQIb
 AwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEKG3BzFfdU+8UXMAnRd2NUzksPzw
 xY9oQMyjeP1cg1R/AKCWoPmmPjJDsf1/CQIkMFMb7RuTDLQnQmVybmhhcmQgU2No
 bWlkdCA8YnNjaG1pZHRARnJlZUJTRC5vcmc+iGIEExECACIFAkttpeICGwMGCwkI
 BwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEKG3BzFfdU+8Ht8AoJS8LxsUX8jA7J6S
 WKwM9JPJ+adJAKCPcJC5vcz1C78IB2XBmnbbKmrYLLkBDQRKNg2hEAQAzfaS1s2p
 EOwwH6ZS9JJ0mnoEfVUkO2I3yfMvXZ4HVkf/lmjQziSsgtbOUPIsIZxh/0V7sDU6
 4ShmeYcY2GpBRE5NFAOo721nOMzXtSbwhUt8ZNZkWXLOCXE/oaS1UoPTQ8KW21IN
 prsFPuVORaZPn1BKXSt/g0l2mkKDdgjMLe8AAwUD/RCMR4fDfuKULk+PG4DrGuyz
 sz/6MC7cmxH76SBzLARw7HOKFXQoVPUfBbQ8oi5ynqFobgENEL5iiWrPhRHLYiJ1
 ee/RiroqJlDxSHno5qU4FIjVGm6b1WbunQ1m3bmK4ExFrygOvHwI0RhoySoAhxiR
 vttEGBF27GMdkRaaUyniiEkEGBECAAkFAko2DaECGwwACgkQobcHMV91T7wEHwCg
 tY2Mbu5ssnZVqMYfEKlx2QIJvZYAnRkudrXyV2F4QME4eLCgAXrjDptm
 =FKOV
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.297. Wolfram Schneider <wosch@FreeBSD.org>

 Type Bits/KeyID    Date       User ID
 pub  1024/2B7181AD 1997/08/09 Wolfram Schneider <wosch@FreeBSD.org>
             Key fingerprint = CA 16 91 D9 75 33 F1 07  1B F0 B4 9F 3E 95 B6 09

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: 2.6.3ia

 mQCNAzPs+aEAAAEEAJqqMm2I9CxWMuHDvuVO/uh0QT0az5ByOktwYLxGXQmqPG1G
 Q3hVuHWYs5Vfm/ARU9CRcVHFyqGQ3LepoRhDHk+JcASHan7ptdFsz7xk1iNNEoe0
 vE2rns38HIbiyQ/2OZd4XsyhFOFtExNoBuyDyNoe3HbHVBQT7TmN/mkrcYGtAAUR
 tCVXb2xmcmFtIFNjaG5laWRlciA8d29zY2hARnJlZUJTRC5vcmc+iQCVAwUQNxnH
 AzmN/mkrcYGtAQF5vgP/SLOiI4AwuPHGwUFkwWPRtRzYSySXqwaPCop5mVak27wk
 pCxGdzoJO2UgcE812Jt92Qas91yTT0gsSvOVNATaf0TM3KnKg5ZXT1QIzYevWtuv
 2ovAG4au3lwiFPDJstnNAPcgLF3OPni5RCUqBjpZFhb/8YDfWYsMcyn4IEaJKre0
 JFdvbGZyYW0gU2NobmVpZGVyIDxzY2huZWlkZXJAemliLmRlPokAlQMFEDcZxu85
 jf5pK3GBrQEBCRgD/jPj1Ogx4O769soiguL1XEHcxhqtrpKZkKwxmDLRa0kJFwLp
 bBJ3Qz3vwaB7n5gQU0JiL1B2M7IxVeHbiIV5pKp7FD248sm+HZvBg6aSnCg2JPUh
 sHd1tK5X4SB5cjFt3Cj0LIN9/c9EUxm3SoML9bovmze60DckErrRNOuTk1IntCJX
 b2xmcmFtIFNjaG5laWRlciA8d29zY2hAYXBmZWwuZGU+iQEVAwUQNmfWXAjJLLJO
 sC7dAQEASAgAnE4g2fwMmFkQy17ATivljEaDZN/m0GdXHctdZ8CaPrWk/9/PTNK+
 U6xCewqIKVwtqxVBMU1VpXUhWXfANWCB7a07D+2GrlB9JwO5NMFJ6g0WI/GCUXjC
 xb3NTkNsvppL8Rdgc8wc4f23GG4CXVggdTD2oUjUH5Bl7afgOT4xLPAqePhS7hFB
 UnMsbA94OfxPtHe5oqyaXt6cXH/SgphRhzPPZq0yjg0Ef+zfHVamvZ6Xl2aLZmSv
 Cc/rb0ShYDYi39ly9OPPiBPGbSVw2Gg804qx3XAKiTFkLsbYQnRt7WuCPsOVjFkf
 CbQS31TaclOyzenZdCAezubGIcrJAKZjMIkAlQMFEDPs+aE5jf5pK3GBrQEBlIAD
 /3CRq6P0m1fi9fbPxnptuipnoFB/m3yF6IdhM8kSe4XlXcm7tS60gxQKZgBO3bDA
 5QANcHdl41Vg95yBAZepPie6iQeAAoylRrONeIy6XShjx3S0WKmA4+C8kBTL+vwa
 UqF9YJ1qesZQtsXlkWp/Z7N12RkueVAVQ7wRPwfnz6E3tC5Xb2xmcmFtIFNjaG5l
 aWRlciA8d29zY2hAcGFua2UuZGUuZnJlZWJzZC5vcmc+iQCVAwUQNxnEqTmN/mkr
 cYGtAQFnpQP9EpRZdG6oYN7d5abvIMN82Z9x71a4QBER+R62mU47wqdRG2b6jMMh
 3k07b2oiprVuPhRw/GEPPQevb6RRT6SD9CPYAGfK3MDE8ZkMj4d+7cZDRJQ35sxv
 gAzQwuA9l7kS0mt5jFRPcEg5/KpuyehRLckjx8jpEM7cEJDHXhBIuVg=
 =3V1R
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.298. Ed Schouten <ed@FreeBSD.org>

 pub   4096R/3491A2BB 2011-03-12 [expires: 2016-03-10]
       Key fingerprint = A110 5982 A887 74A2 F4B1  D70A 6E5E D8FE 3491 A2BB
 uid                  Ed Schouten (The FreeBSD Project) <ed@FreeBSD.org>
 uid                  Ed Schouten <ed@80386.nl>
 sub   4096R/81BB41E6 2011-03-12 [expires: 2016-03-10]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBE178rsBEACsON0CrmLDqNRy1sLCwcfi97Ses8MsBZ/PRIdqxNzMarUj4fRM
 YrqcB6xTdmqcpsp+b1RtrQ0VknibTZhk8bNeLqBeAlcKi5vN390Jru5o5YWL2+J+
 55En1EbI7wJahtWiMvjKsMf98RK107pxS5BBmgwyuN+Zm1/vh0pVzXnQ13ox7YM8
 g/x8mMAE2mT5PzACTTr2o0MTzu05wbdlOQiN61K+Ti41pPKglSf6hKn2G/JcKs1E
 Dd16dVO9fawURdceeL7x4+AzRUp6pO+VLHV9/chMZFnfSXo6yJliq/9AYTY9eAEC
 ZhTCEUj0CZ+tz5dJxTMynxlbDryIBg+j9Of8XYyjynM2E45ohtTqW4V6+ogGnCju
 dDZIupTOyEvSNTEfi+Aaf4QurLIhKiY5WkEAzbimHyfFkSlukYsdTe9AV5xdiejw
 AcRECfXWXCMvxZ5DjLDI2ZhxDgRJY2ttQwcQrQKpr9ojT/MkDND/EPDrl+NzRsxG
 KiAOnZ05YNBm3KkjlFxe7YzspInc2eWLFKQohisR4MOcJnM6VAl86jOOmIxMY2T1
 N3LzaVi7Vb2IYnv+Vyn5dMp5TmwCc55ESdE9YBE6NytkWh3xJ3e7mG+zBdzK/fQb
 K/XAVeUhxuMPCaG159jN4czNSy7q9CK96deFaVcTL59rLxAHOXMVi2XP+wARAQAB
 tBlFZCBTY2hvdXRlbiA8ZWRAODAzODYubmw+iQI+BBMBAgAoBQJNe/K7AhsDBQkJ
 ZgGABgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRBuXtj+NJGiuyWgEACIIGiE
 NWyrh6IzFw1w6L2yVx/U22PI6itd/W+/ZXm1d7Y0e6Nq9s5zVjConLn+IVifcM9R
 sJk6KUbHym/DKf3OOdddaZuvjZRM30V/6FjCkmz+pTsEWXYFyIK2WAkce3qDqzeX
 3JvwQA8MD99bgpCsUOD/KZ0jxyHEi9B04W5FDTTaMAp6JTSQDSmYAUYpg2INbv+P
 s+semFR3bQaW3sJSC8lfOEjVrk9vwE4tRlfPWcleoj9aE4/V4BGMbOxlRZMd55nG
 KVw/BayKPLsTbbrtMzNaVRYd2EUJ1H5ZHnj45yZOgz+bODwNMPRi7unwFdJxd1xl
 HYTluAq9ufOzs/FQaGi4QcAA76hF6TQdtkAhNn3fqP8i0440oP9GTa5ueUg9kMfH
 DzGQMH3+NLFwAz1QTXPyL4HbKTaEFUDZDLJyr2HJQnWXtXe9u48m4JPg2+FH/aEN
 4CB2eu6B5Ntfp6pd+mmOi/WoXWpJuw6P5+zuJ2UCThSVBsSnpRs+UKaIH2w/jyOq
 FFsqblBDio/ByDKB3/OwcCF7inNSGCvPYPl0b+fzFAZqk/kREuOYUHpgq1H8ap0y
 +VtO7y8/lWjl0qxR2M7svYZQ4lmgaByN/89xX4wznIzOCbseqGVisvGoo6C7hTFA
 6+vCoeEEmcjaejk6adXuyXLmfN22ECD08XO4ZbQyRWQgU2Nob3V0ZW4gKFRoZSBG
 cmVlQlNEIFByb2plY3QpIDxlZEBGcmVlQlNELm9yZz6JAj4EEwECACgFAk2S9+sC
 GwMFCQlmAYAGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEG5e2P40kaK7aRUP
 /jMy8K+JxshXmHMg6hEWGymWskqXqCYokWNQ7Wf/dJCPrkKT2XXiW4F9QR2X8lhP
 1jN8nfgr3kzJXFUIqJ3mRaNEPe4dMSihGMhnaEcpkHrJHOIXaNo9G8kiKjprvmH8
 AcBtf8alPV4rJDHJC1KazbJG28pmoiA4rDs8HMfFFPPx9cfJRMedRho9uAiETxyx
 WL8FKbp8anSQFEeE/o8BLmBEBpUsWxI7TfbLnOwak5Yh9QPbRbGxuFdTQ2lv883I
 2hOSCVN4vOxsXLXZerncsDcJBxMnYp7j/egyFZfXXQ5D3VweC/kZKBVzgeZhHiQc
 qVQgW8nJskKNqh7Y1Zvx0vw+3ITNC3B6mlI9IvArIuHiTHw6nvI7TS9Wj5B33PYm
 uADEy93DW0G/zbtCDoBD2+HMyADzr+YssqWgIKtAwG+1ErlI6M/6aVnsUiYyBVG1
 IYCyumCMKX4A+IIIhWv2+aFcvN2e7YDGS1rQjbBQ3Gx4id6p/tfnXIJxQUtkWNP7
 L8OElcvFZTa/Stg8YieyP4hhcmaRppjMA35mAMOz2OATeOzKPNfCOB+h7FE1Fedu
 HNDomCaoDhY3Wj5SO8L6cohjhDZQ50t67c7MRNiMgGFQ8ScPs8LcPo3j+/O3z5MR
 P1LhKVMQ+joR0jrmZNoqsHsaTjIPRNgts6MI6vjwc2dtuQINBE178rsBEADfx0ps
 fxMnqy7uh2PZKCdh5It3xRVcEXSa+y5x2fz7SA1JhC2bVX7bNhQwaQmTUdR/3y8k
 eiOw89pfpzQdaLWRbqLccCqJrTkRPTm+sOvDq4uCC/OAtEvMmmlcGZVGyFsOzwyO
 Bsb7FMf6gsTuSsfFIwH8wUotUHIPRH0r3gawk4LgU70ysZL5gEQusU2Z65XRlPqZ
 E3gts68+cG1XUE0DtCzeHDNFKGVVVqUI4eEZl4wqzFRCxnBe0GjiSEIL9sONXiNE
 okbN9AZcPIQtbikeqRFD6oHezUUdJImP0DS0cpPepjGzh5VmqJuvV7JPE6A5AvPc
 pFis9NuQa2y/7xDqpQKjtvDrJKWmAhDuA1tpgXXKc26hZtzmGb1l/Qeglvsz19bf
 lfk/fJ3B1OURMFHQq3oYf6/zvDPB2N1R84WVm5BTIeZPT0oWIBE9KHpN38Drsmc1
 3pFhBDUTnPf/sdLfIDKX7apcPNJAGkNYnClL39pIQeK+sJKaO49iqOJYoKQbcJrX
 OKq6cjAZgkA/R5UaMTE0E2NMKgMbkCILcjrX+7w1Ui7V/CxPdgqyjk2QIaQO7pxr
 9bDogjVNAc9mFvMwDyHviF2XMNKlTTMbKsgLfEP7KAC6Mx2mQdcGmNReOTJqRZzQ
 aiC005tLDKQRXVi8yg97b9uh9iO3e7nPKqQaUwARAQABiQIlBBgBAgAPBQJNe/K7
 AhsMBQkJZgGAAAoJEG5e2P40kaK7nEMQAIzxlWA6EnNEWHRJFHOouIlkMqUvb4jn
 N+DYZSEBedbZd+73MdhEYwqPFuR7a6bMcO3PhVwmKyjEbgT/4xP4Fs8udPDkLiIO
 O0PlSQNuGuW+ZDWhl6iww+7ZetW767mDPqo2RfiEmn3lKA42Gs5EzrS8GtcOsfkb
 1vzNy7eoiu782F1ebb/+D2ujxETjSpl7Q6fzufoGTx4Ok8TmxG1qdN+P6bVCQMoL
 aWM+YGXh1OqPM+kXCAMZB8vbrCHtwoQ1JTbb0YJmmWuxorVy43f7FSXpNjusuf5J
 Qcweg2kG2t1MctzXx03eUb2PQZFvR69+1zBQys3IXLl22VKR2ZEK70QTO5Iv8G3o
 L+Cn4wJ2jEr0yC5h7rtzaNpsR2vzvv+XAzqwZiFWO7cGRDjdxnddSWuJu69Tyfdd
 5DqO3BUJxNIz3Nua2VE4+Dyr08jnewSfIVLPoJ8bG7vHaUdDVgit8DvUJS66j5EL
 dfigxRu1mtmZufwPkqjffXSIqKGYWDjMZY92/qQ9pb5ruOxT9Esok03wwHLq1SF6
 MCHY7I15DiNTU0Ia1rPEnJ1o5+QMHjOvAxeHkZekLZMFQQ5AMQdMbRzLUW7NKtPR
 /55zHT0WB5ZmCLX4iuV2x1a/37sQnjX+w3IYO/451vwZ8cRPjwyOOV+skciuCx+d
 Y6j1y6QnLaPN
 =FiVI
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.299. David Schultz <das@FreeBSD.org>

 pub  1024D/BE848B57 2001-07-19 David Schultz <das@FreeBSD.ORG>
      Key fingerprint = 0C12 797B A9CB 19D9 FDAF  2A39 2D76 A2DB BE84 8B57
 uid  David Schultz <dschultz@uclink.Berkeley.EDU>
 uid  David Schultz <das@FreeBSD.ORG>
 sub  2048g/69206E8E 2001-07-19

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBDtXc9MRBADg4tN94el8rq0ZMUqB2jEVACg/UfYjtsaboDL4HBBUH+P+Wxic
 9JqotcTbT8pJGeRpeXbfO0YHaAFnUfilhoFkeLyAgDvnUP9Z77DjFpliLAKlvuCz
 Lxi4UxgQXRdedNCg3omrxQWx7Yx067GT/yw4RgvogOuYBX0l3AJ25/WBxQCg/6Dj
 TMTu6iYR2Y6dEL4NGs9PnBMEAKBlhelAhzYoMpcWpk2VITUgONMW+Oi2JDTmwDd+
 1FAUDc1mHSoNBKPUrCWyXiwfzL09/ROlK/KMR6YoYtV6d66zZ/dQNuzrMhsis+Ou
 PCtvcaR5NGln49THgcw7/K5gTjwrG1xA/wcwnvUp6sxjh4p88meI/LNBAstixb3z
 FiLDA/9pAqn42B9ZBL1le98DTiLDemHvQFgXu8Oj20IIF0umyJRBfKwDY6iIx0gd
 1rUKua6XnqMSEg+LmHmSfDBaAOsFTdnL7wVU0tLF0V9goxU4qDZjw5EeMEqnk7tg
 /6REIvtdOA/GLOmr/Q0WA4JEukcih3AQ9iFnwg7WAp0S4GF6gLQsRGF2aWQgU2No
 dWx0eiA8ZHNjaHVsdHpAdWNsaW5rLkJlcmtlbGV5LkVEVT6JAEsEEBECAAsFAjtX
 c9MECwMBAgAKCRAtdqLbvoSLV78JAKD4iJ2kNeTsYQnWZ2DeytAeqVaKFwCfTIQE
 lFPZyaQr7yjthREE+8SPZCG0H0RhdmlkIFNjaHVsdHogPGRhc0BGcmVlQlNELk9S
 Rz6JAEsEEBECAAsFAj5S1iEECwMBAgAKCRAtdqLbvoSLV4b5AKCljokqRgi/pbDa
 ZebYLluQCIkbgQCg+jSKAIi1r+CZiaCJdqk193IZVnm5Ag0EO1dz0xAIAPZCV7cI
 fwgXcqK61qlC8wXo+VMROU+28W65Szgg2gGnVqMU6Y9AVfPQB8bLQ6mUrfdMZIZJ
 +AyDvWXpF9Sh01D49Vlf3HZSTz09jdvOmeFXklnN/biudE/F/Ha8g8VHMGHOfMlm
 /xX5u/2RXscBqtNbno2gpXI61Brwv0YAWCvl9Ij9WE5J280gtJ3kkQc2azNsOA1F
 HQ98iLMcfFstjvbzySPAQ/ClWxiNjrtVjLhdONM0/XwXV0OjHRhs3jMhLLUq/zzh
 sSlAGBGNfISnCnLWhsQDGcgHKXrKlQzZlp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZ
 Jrqrol7DVekyCzsAAgIH/1AtvAGCJchvLFoaR5KNocKcoUMe2NrpRrFS3DsYOsXU
 0U95pmAHJaMt+wv4UDs/wNzOzC6stRML+3lg6sYnSgddH+N/DA0b5jQSAyNWlL87
 j08h3ATaPeDD6qhqFRe3uzpQMAJJWbeTdyiT2vwgglgcaJWuVjYSfkkxX7AVDFHw
 C4IOuZ0aQhHyHQsGQURTg+sotMx+kX68o7oGZqBBOcr8VdFyrlq0Tq1b/i0fJnn2
 Nz5hY+OOXbyeoJbaY0KiGnnMwHmeZ2eJWk1cCHUZnrY5WOxYQHail2KHXxhYuPoI
 xsL0y+XdErX+lc2BiEbvXROs+VxEo/3/BVJXAIar3nCJAD8DBRg7V3PTLXai276E
 i1cRAsj2AKC26JMJWsvd93UUWRXDKmU46MgLggCfTOIjPheQwY9VCN3jO9YROzij
 QVE=
 =qhh7
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.300. Michael Scheidell <scheidell@FreeBSD.org>

 pub   2048R/34622C1D 2011-11-16
       Key fingerprint = 0A0C 9ECA 18EC 47AC C715  2187 91B9 F9FE 3462 2C1D
 uid                  Michael Scheidell <scheidell@freebsd.org>
 sub   2048R/8F241971 2011-11-16

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBE7EJJwBCACw/7AoltcqlzLBZfdNZTb/9zMBRV2X7Qz8jtOrmFj10GpasMCe
 oHWLXHyWbuVgsu2QeANorUcEMvVpkCkNWG8EewKH5QbUcehqPfs8L51N+8Xxdzr3
 LlAoOiDFI6FWhDrHvdXRgzWM0xU7OMAxPkXpVNhT4cTmLwWGXmVNtxL48MRTsUz4
 XRMkXpfEEfXJ0xGsz+Q5AMSUbUIAOq6cKCreIk1s2Ir9UHHBJ5E68W4jHFk/PnYP
 WAx1z+PugI932b1RmnZEycjs2U+QN925vJ+V1172tU31TOPF3yTVkeltV/R7yXgB
 Pn5iDDrhILjOjWxj3xOGXJja/ikERYAPUEqLABEBAAG0KU1pY2hhZWwgU2NoZWlk
 ZWxsIDxzY2hlaWRlbGxAZnJlZWJzZC5vcmc+iQE4BBMBAgAiBQJOxCScAhsDBgsJ
 CAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRCRufn+NGIsHabBCACaxRmi/WgvVt5y
 r/9DfYDKMBRZwdvTmPqSc3qa/HyCH5b8pIzEep0UsVw977LmOnMbHr9TEzU9YuF0
 XyA1WZNdzjnVjlRl2VW6/Cwo28jnwnESiGD/KNdU0e0T4ntqP4eLEd7t4Y4WhpTk
 JBidX0r6d2+CQyCFk74zDc5eTXS/sLZZJommr5JIo75L7LWetuxR6AFrZ3SDdanc
 ktHJspZAN69yVb3XxoDveVF0XXE/RSeStWtWHLJNN0r+6Oq2CAf1fJZhFOZybPhs
 zYy6xWFp3N+myhq9HgPmlQcB8BCPHu++S55Ybe+4ZDqtuLaALQaT20zr73Vv4VHi
 QMiB/TYnuQENBE7EJJwBCAC7Qjm0lGOxZy0JoPTkZ32KW84TxsQ8IH/6QhAP2AVN
 kCaVrlZcGaZKd2WBQIcd0Br6FErD+jrYB9+hv1kGj/2Q3dL9UbB/Ee7ywm6++rLc
 RdRhlyeG1or+zjcQEvJyYEzyGdJi4R1+6SIQLaJiPrGL2GvGWfx7xk7UoJe9vayX
 ie9LNBoqq/qlXNRRRAu8DvOk4LIRcZHwv1urwZIGoK/Kmj0DQJ8+mrqXBugkI35G
 /XVeIgOzAoDGHkIR+eHGp7iOaAxDWwRGgtcYp8hgUASLgMxOM7npc1agozdFD20A
 PmI5uLqS0nmHiGaQYbS9azkZh5zwDKXaq6xz0LDuBcgHABEBAAGJAR8EGAECAAkF
 Ak7EJJwCGwwACgkQkbn5/jRiLB1lPwf/bQmsQnuQIM1O4cWxS8zKqFp30k1GaU9k
 GEAUEeY9JB6z/vhhleNwiMV6DbIfzFN71JWs00iyI0NAXDjNp+PLR+lBXH0Ztca0
 C4N7vqNnbsg5CleKK5n66fOc/HVB86rpmBFU2ji2ZQ3NO+A47XlGKyHgPvZ//XfW
 +WfeuCJ3tCWnx7lVTFXh/tIKO4fPyJ+dmp0JzumT7lmwG9YPwKovx6s42DD+62NM
 kf1yKac03ta650N6s90zB6XswCa8Geb4pn2f2PGkobY7OUfqymf+Rnj/kfnkRFo6
 sHoeErC1UGxAi59bZaVJ69y1/fmJrRD92ymTEj4DZowEs02c5NhwtA==
 =S4If
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.301. Jens Schweikhardt <schweikh@FreeBSD.org>

 pub  1024D/0FF231FD 2002-01-27 Jens Schweikhardt <schweikh@FreeBSD.org>
      Key fingerprint = 3F35 E705 F02F 35A1 A23E  330E 16FE EA33 0FF2 31FD
 uid                            Jens Schweikhardt <schweikh@schweikhardt.net>
 sub  1024g/6E93CACC 2002-01-27 [expires: 2005-01-26]

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDxUIHoRBACGAbIspofa2HTwV0Y81ZgrizVgvsHduKRMYmu9scX6eFSQWC2a
 JLXXnMJMK97LG2m6qX/hzjxZKU/n2eNpHa3h9zLYQ/8VdN+AFHGZtgmZ7xe7UpBI
 V2YohykdmgKqg8WuVQGrNTwbkaAFeLnG3yXhR83qukRvv+qFfXbEF+1S2wCg6lLg
 YJ6U4J1pfTO95Rd4hw5v6DsD/0hUfa6C6C6xjME6P7r/ORd91+nJsfO0pcV1rK0s
 yCMdAy/zdUlKpsNF9vS0qhCFonuOHWxMEe7D8L80oUAwlk4RrFBm+Ch7RoBGYGru
 aEom/7JGNoRqUD2CKbFnkAYi9HP6XlXcpgm3GO4c4VtIcEbgywjw7rNhmNoYLrZV
 YUb0A/9mNCqpPTd8ngm7kPyTTMJitYEVaBPXEdiPueYJND+eI9AQkcqYhs6LWq4c
 jgmTNeImQ+kR1UeDj3dOwUDqhGmLPN60nD+Q2oHHBif8NJOu47mx1dgdriM9FsTN
 3UbeSve+mY8Z8zcPIYKl2UJLPZckWgq4pZRrE147cnKHSHHM9LQtSmVucyBTY2h3
 ZWlraGFyZHQgPHNjaHdlaWtoQHNjaHdlaWtoYXJkdC5uZXQ+iF0EExECAB0FAjxU
 IHoFCQWjmoAFCwcKAwQDFQMCAxYCAQIXgAAKCRAW/uozD/Ix/ZB8AJ989jyDH1G2
 T1KMoNd7gPk9tAw1VACfXJgkrI42ShC4cHz37xrVLXeJp9i0KEplbnMgU2Nod2Vp
 a2hhcmR0IDxzY2h3ZWlraEBGcmVlQlNELm9yZz6IXQQTEQIAHQUCPFQ+0AUJBaOa
 gAULBwoDBAMVAwIDFgIBAheAAAoJEBb+6jMP8jH9P+YAoM72fnNwxxcDjb+3Mv3A
 CfbHonYCAJ9lfK9fIbkgfAHo+2kwnOEN4yWxzLkBDQQ8VCB/EAQAzzIqOgms7u+e
 UKampP/5U9G78HA3GIkVLcAeq5FfpFtls4NmSKz240zNxXmABWTSlBmOQvMdhB08
 vRbzEsxPoVdNaF+QvRZYEr5+2bOM1pnHqYYMyUKwN83LXgTDnXxas4mtrkgngZTe
 tGdFQ3PIVqW4jV0MmnEmaqde0nMJ6XsAAwUD/2z82PDDwFBu1Ogogh63qE69HSQt
 8weHX+Skmi75jE3r2niUlx6B0IfLXzFqP33vyrsov7QHgAuOjNficisbC73o3gjp
 voJ2RYB2IfUCgeFvipLpqY1TWJ3bF52TYnJg4rrEWd5OWs4FB0iaJ78LVWgq3WsN
 zfgcgfQ38d+scJu4iEwEGBECAAwFAjxUIH8FCQWjmoAACgkQFv7qMw/yMf1PIwCg
 nSP0i+q9jhEf9T5xA0+qg2yYB/IAnjvd/tA+2/5bP4pObE/oRNjIVZBZ
 =YPu9
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.302. Matthew Seaman <matthew@FreeBSD.org>

 pub   1024D/60AE908C 2005-12-17 [expires: 2012-03-21]
       Key fingerprint = B555 2A96 274E D248 5734  0EB4 F0C8 E4E7 60AE 908C
 uid                  Matthew Seaman <m.seaman@infracaninophile.co.uk>
 uid                  Matthew Seaman <m.seaman@black-earth.co.uk>
 uid                  Matthew Seaman <matthew@freebsd.org>
 sub   2048g/58BFDA29 2005-12-17 [expires: 2012-03-21]
 sub   1024D/9B19F956 2006-12-18 [expires: 2012-03-21]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 8052 characters]
 sg4yrGkH4IXKBB8csDYR5w==
 =IPI8
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.303. Thomas-Martin Seck <tmseck@FreeBSD.org>

 pub   1024D/DF46EE05 2000-11-22
       Key fingerprint = A38F AE66 6B11 6EB9 5D1A  B67D 2444 2FE1 DF46 EE05
 uid                  Thomas-Martin Seck (Privat 2) <tmseck@netcologne.de>
 uid                  Thomas-Martin Seck (Privat) <tmseck@web.de>
 uid                  Thomas-Martin Seck (FreeBSD) <tmseck@FreeBSD.org>
 sub   2048g/3DC33B0F 2000-11-22

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGhBDocG/ERBAC6QZ2lUZYVTAqov7yLfcDY6CFKncdQH1k0aV65fME1va1nelTy
 qIE9+1unTXyFCTY8ZWhlrgblwH7oSHkVgk+WOOcBVEYvjY9n3Y5reNqKV3Qj3gYH
 GzSheBeRvgDgKKF0kaG01sQby7zneJMDepy4JkuMiXqc+S9nM75Gf7naawCg+viP
 cLaa0z0UzbO341zHTgerHacD901GiZS6SgHrjmGKorhmul/CPyIN5OIdbt9YJANh
 /R+w8c1XCgbmuHS0gCHiyYG1Sy1rRhbptlqWxEhJjZSud3Ne2Hxh16IUFhTrFqr3
 xgkH6FiGw+a0tD6Jk44UBsbdgNcU7Qr424phgga4yDYjn+lDW0RkO89ElhHZsrLj
 uGkD/1Ela0htkQoWgZW0I0XO+LNBsnuxPwqqG3vM1VLhSzrFH0CHKeQqYt9iHV/M
 eD1KIdIXzoPBfRbFLM1ktE/3AlomrgXp9WtxfXhzWNcWFzYLUajAxlGYD2wT+3H7
 Tpm1/hKQcJJG2xMRCyeZcOf+pTWaqCbLLTsy0G+MY/j5Rug1tDRUaG9tYXMtTWFy
 dGluIFNlY2sgKFByaXZhdCAyKSA8dG1zZWNrQG5ldGNvbG9nbmUuZGU+iGIEExEC
 ABoFCwcKAwQDFQMCAxYCAQIXgAUCQR+T+AIZAQASB2VHUEcAAQEJECREL+HfRu4F
 hQsAoIYCMipK3ugbNfOUW+1BMpPiNnm8AJ9kyX6rm8M8Doj/qCKJF36gxrTo/7Qr
 VGhvbWFzLU1hcnRpbiBTZWNrIChQcml2YXQpIDx0bXNlY2tAd2ViLmRlPohfBBMR
 AgAXBQI6HBvxBQsHCgMEAxUDAgMWAgECF4AAEgkQJEQv4d9G7gUHZUdQRwABAbOv
 AJ4y63dcgJXV9Vcw0SUMdJ66IK7d6ACgzX0WCMIVWiNBey1/ZHOgHaE5Kku0MVRo
 b21hcy1NYXJ0aW4gU2VjayAoRnJlZUJTRCkgPHRtc2Vja0BGcmVlQlNELm9yZz6I
 YgQTEQIAIgUCUTZfLgIbIwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQJEQv
 4d9G7gUH7wCfUxSv8PJY/gF8wYEY9xC2YJdK9yQAnjOz54d/B3GGMsBiAKzM8qZT
 zTXruQINBDocHF0QCACoDJirnOAYUdRKgOpFrDupOuSPexu6Dz6WRxV1hNwaAajD
 lmgHK+7W8Yb0wd+8bKASi7aonkbZOhRfkJ5DbrjgqNGyJjCRHgqGboyGyR9Mezyc
 W5kNLNWhwtBiBU/5zExgSQaQKHOvQeFXIfa9gJQy9hn4qMAXs80jvns1siNwbQHn
 TKRP35G7FI69FS5tBfEFata3qyhv2KP2yxlRyTv532yq2k1di07vXKEiS/UrbFJ7
 tRpO+cfXy0iXADtRMPt4EMeBffmDI7B2DS75Hn3RArKjk9/8AvuFLbkgbdEzvsB4
 l706H+ziB7X9YmDDkKFpMW/SONbCWETrjK7KP0wnAAQLB/94xzi6sqLcJhVp4QBH
 ekzCYoxrUmlb+wH8DerIftT4S2BpV6cF2vVD2KfmDpwmZ3MaF83OvaT7dcZ8fZ1r
 1afkqIpXdwjI70c3cKOAnrZkVZAma6E9EYvi1Ww8mxLJ+ClvWh7fVpQmppqJMfdM
 ZgU5egCYliv/QQGp+SyNXNOkfttIsA8EWruJo/33nAvG0bqzwh7X+SQsK4MVidD1
 7/5srXHMlBN5zBqRaRq0lakpT8xDlB2NqlQTMb6wnHscV3ZqUzaszEXvhXnUwSPr
 a820urDh6o/hnsF/VH7gCJmkkVV7Ei1MjIp8H6Zs0A8se/XlYlf5OlZB8chqJ+mP
 r2tuiE0EGBECAAYFAjocHF0AEgkQJEQv4d9G7gUHZUdQRwABAZtlAJdyRMT4dZ2D
 wiimJm8jZ2BOhV/UAKCBrBb3jVIe9FUC3JpwMajuZ1gbSg==
 =p6Le
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.304. Stanislav Sedov <stas@FreeBSD.org>

 pub   4096R/092FD9F0 2009-05-23
       Key fingerprint = B83A B15D 929A 364A D8BC  B3F9 BF25 A231 092F D9F0
 uid                  Stanislav Sedov <stas@FreeBSD.org>
 uid                  Stanislav Sedov <stas@SpringDaemons.com>
 uid                  Stanislav Sedov (Corporate email) <stas@deglitch.com>
 uid                  Stanislav Sedov (Corporate email) <stas@ht-systems.ru>
 uid                  Stanislav Sedov (Corporate email) <ssedov@3playnet.com>
 uid                  Stanislav Sedov <ssedov@mbsd.msk.ru>
 uid                  Stanislav Sedov (Corporate email) <ssedov@swifttest.com>
 sub   4096R/6FD2025F 2009-05-23

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 14124 characters]
 syiKxh4=
 =OeD1
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.305. Johan van Selst <johans@FreeBSD.org>

 pub   4096R/D3AE8D3A 2009-09-01
       Key fingerprint = 31C8 D089 DDB6 96C6 F3C1  29C0 A9C8 6C8D D3AE 8D3A
 uid                  Johan van Selst
 uid                  Johan van Selst <johans@gletsjer.net>
 uid                  Johan van Selst <johans@stack.nl>
 uid                  Johan van Selst <johans@FreeBSD.org>
 uid                  Johan van Selst (GSWoT:NL50) <johans@gswot.org>
 sub   2048R/B002E38C 2009-09-01
 sub   2048R/1EBCAECB 2009-09-01
 sub   2048R/639A1446 2009-09-01
 sub   3072D/6F2708F4 2009-09-01
 sub   4096g/D6F89E83 2009-09-01

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 40392 characters]
 jJLQtFy144uCNLgL5JagmqMiXx9rL6dHFHc=
 =sXgu
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.306. Bakul Shah <bakul@FreeBSD.org>

 pub   1024D/86AEE4CB 2006-04-20
       Key fingerprint = 0389 26E8 381C 6980 AEC0  10A5 E540 A157 86AE E4CB
 uid                  Bakul Shah <bakul@freebsd.org>
 sub   2048g/5C3DCC24 2006-04-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBERHS6MRBAC60MHcIa5gqGjSmHLxJeZTkLTDK0zEo7MRJuMeF90Py7wdP9Fy
 jmRhyBS/tYfOtPrpHwAdn5FIkVzajEklv9L0/JiUx5WDrmJFWqIgRLdRPYw909hE
 7pW3uTs2qotWjeA8ecefzlTX9gdZVgy2uPhihMG9cn7pL1aXluca8AUsIwCg4lUf
 8pL0Pn6pZ6xP7nG1hEvkzr8D/1LR5Bm47RboJ+dvoMf9lwlXiEBP0m40100urcxR
 7e+AHDX2yr6s4edx7pPRCq2ubPgzK2rYv4NHN943AY8EYbrazp5F3EItDOLHmIus
 JasvCgPTb7HYWO7Q28redJyUIfBUTPgVVk2z4EuCb5QKDU2/2DyqWThrLEwTCTRh
 mR82A/sHQE/xib0291VjMxGKiatd2Xm5hu7dSzCeZwc/5uF0g33OYcd02fosyERd
 96SWmGigFWLbQ/kFiAoN0OAlQQoNPuWjGzIJVrxiy9y3Fw2hnoiV3MAWAGr43+UI
 FR+XB/MxOKIozYrMouhZHtmw237fKVH6Ewe/rFkthkgm9P9BpLQeQmFrdWwgU2hh
 aCA8YmFrdWxAZnJlZWJzZC5vcmc+iGAEExECACAFAkRHS6MCGwMGCwkIBwMCBBUC
 CAMEFgIDAQIeAQIXgAAKCRDlQKFXhq7ky+oMAJ9Cth9LlPV2on7lTedInW/6T2mh
 YQCgm6bY4yyoJbjUxop0bcuKYGVVuSO5Ag0EREdLsRAIAK/+InMhz/qJB/+Rwq08
 K6TtPPkAs5+IcFQqjShCtFWiaZrvBqvcTPDqVIMu6CAnBf6QTOKQc+L7lSUE6QdI
 0mE3jiieYJ/cDzSqntYZBkC5glW0AzemgyllQRlqKrIawWu8M+SwZipvKb0YCIFo
 rmhoHCjzK/DKlSi0MOjPVTbsyS/rTvhAoXxodogKfNzRpb4MwDjM4Lda9mO+hKlI
 93CsBCzNZaOECYJ/1vkpuGqOBhvezrLtNCYFmul2JtVMyCb86mOIJAeiwn/hiZu5
 eU3QYdvcCOfYh//B8AZOVSW1x8HYzMFXuznVtx1P5ygvtWY3u+uIlXC274XuV0aJ
 NNMAAwUH/1rSg/fSdVGEG3ge+sGtFKHPOaGW014dt5nHCePrhLwHIe/udyZPCD3a
 axp6RVlx5Yvw2+nMBWiW65KACBUQslSHbeM5u2aPH6HaAAEYCJ682vKUWyEHGljJ
 zDBBANYKThYwle1xRxiE5MT9B2Bz33z2/BQnCgo21KYAU/2bwi2qVG0jyF0i6ryP
 6r5w2zZbZA/0IINcwENYRhYdtU+QtyB/HqX//nshVnxZFgG0pIPET5ltq9VM+6Fj
 hxJ2RXwGOxBJW3+yLw5JuDVrqoOz2lAOulY2uiQY1Nk9xHDBKZ1U172BugHuOIbW
 EAgbLB4QFuIE0HF1h6bNSISULLt0/yuISQQYEQIACQUCREdLsQIbDAAKCRDlQKFX
 hq7kyxbGAKDdITbPvXRBxINGLWTcNxtRqjXl0gCbBVmMqSG99Tl8uB7wTZRDjtCX
 5DU=
 =iFzp
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.307. Gregory Neil Shapiro <gshapiro@FreeBSD.org>

 pub  1024R/4FBE2ADD 2000-10-13 Gregory Neil Shapiro <gshapiro@gshapiro.net>
      Key fingerprint = 56 D5 FF A7 A6 54 A6 B5  59 10 00 B9 5F 5F 20 09
 uid                            Gregory Neil Shapiro <gshapiro@FreeBSD.org>

 pub  1024D/F76A9BF5 2001-11-14 Gregory Neil Shapiro <gshapiro@FreeBSD.org>
      Key fingerprint = 3B5E DAF1 4B04 97BA EE20  F841 21F9 C5BC F76A 9BF5
 uid                            Gregory Neil Shapiro <gshapiro@gshapiro.net>
 sub  2048g/935657DC 2001-11-14

 pub  1024D/FCE56561 2000-10-14 Gregory Neil Shapiro <gshapiro@FreeBSD.org>
      Key fingerprint = 42C4 A87A FD85 C34F E77F  5EA1 88E1 7B1D FCE5 6561
 uid                            Gregory Neil Shapiro <gshapiro@gshapiro.net>
 sub  1024g/285DC8A0 2000-10-14 [expires: 2001-10-14]

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 12144 characters]
 LsOLmQ==
 =GprF
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.308. Arun Sharma <arun@FreeBSD.org>

 pub  1024D/7D112181 2003-03-06 Arun Sharma <arun@sharma-home.net>
      Key fingerprint = A074 41D6 8537 C7D5 070E  0F78 0247 1AE2 7D11 2181
 uid                            Arun Sharma <arun@freebsd.org>
 uid                            Arun Sharma <arun.sharma@intel.com>
 sub  1024g/ACAD98DA 2003-03-06 [expires: 2005-03-05]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD5my2cRBADKOgeJz+IX/4UT65iwvAMoR5SMctMAEGNHvTk96H0DSYmDmqPE
 6D4PWxjiAmbFdMmxGvmPlZDGRk7IpZhrvmsAuAvwImA/UyGb3Qnb0zOoOlAIQiGz
 NXRvum8vzoTeW5r9ghLOKkBuze1qi8PZdT+ztreaYcPPZBI9zPNfnZd29wCg4Sqo
 eWA46NgWICUsOpC3dkhAmdMEAKBUmh8p4kOZQq5LPv3y1fo+5MBI1gnawiJoO955
 nzVuisH5h1yaNjz0nkB5VtEG2Ub2mhBjckze4EP4FzPgIpOhSMdGfNh67rrByvv5
 DD/SBwjULSEGbBlywn462QDb1X0PxFX5C6IYK2Q6i/vbWkOFMI2dVuQX0PUq9zjN
 D5QJA/sFeXR7NcutCUaLknFCaV1cBTITJNurKn5Vm3QQq5s6R2cFTxdouHcSNkto
 EbhcAvMapxlWl146h7mAtLsXXa5s3wuMWq+igOXUk0wkcm8CqvSQtnVYl4Xy/Ll3
 zXKxtzKHZ1YxAdYQXGkesBuaSafCN6VYDFFSEwChHrwe1sV9obQiQXJ1biBTaGFy
 bWEgPGFydW5Ac2hhcm1hLWhvbWUubmV0PohiBBMRAgAiBQkDwmcABAsHAwIDFQID
 AxYCAQIeAQIXgAIZAQUCPmbLaAAKCRACRxrifREhgYRWAJwLdcAEvjkJf5bHy975
 R7q7Rp4KUACgq214dvKu35ysWriNNxu2jtIj1he0HkFydW4gU2hhcm1hIDxhcnVu
 QGZyZWVic2Qub3JnPohiBBMRAgAiBQI+ZsydAhsDBQkDwmcABAsHAwIDFQIDAxYC
 AQIeAQIXgAAKCRACRxrifREhgVrxAKCXiBsYhu++BPQX9prGf2BeKNYaswCfaS2Z
 eNyZsxSNedBb26k8ARWrZzq0I0FydW4gU2hhcm1hIDxhcnVuLnNoYXJtYUBpbnRl
 bC5jb20+iGIEExECACIFAj5q4pcCGwMFCQPCZwAECwcDAgMVAgMDFgIBAh4BAheA
 AAoJEAJHGuJ9ESGBbWIAnRAlo9PVZzdar5pmWDGspeyGk63ZAJ9X3x6ZQSD7uYeB
 ajKe61NpPAamJbkBDQQ+ZstqEAQAkgu4UWlgyF1IeMM+vwHQ43zik3Rn6nhpJXRb
 Arpg4QyVHQNQshVT4XsmSvcgw0TSUub0x5m23dqnhcoB/mk0kAIymVQiEaa4SLjI
 tTXd93yRvSgPd8JEUNFwcSE43ZJrrmSAqIc6MUJ0hI/pAeCFvRWYQ80+82xx30Vn
 fJLOJR8AAwUD/R2xFX5geJ7W8OyLtB5XQirkL1YPGLNNx4lyAPXFJc1s1KwfZ90q
 LYNw2qLRIacYKmY2X9BrWADXPrEZIDKljn+Awz34lSwerLHWwYDDoeyjfMt4Mmra
 MsV8UIjaBGO1ptbqEDSVeb1tiWQGa622pT5YaZp/r/OFdlmg+JvkAzHkiEwEGBEC
 AAwFAj5my2oFCQPCZwAACgkQAkca4n0RIYGWkgCgxhDAezhK5kiSC4N74g9ifsF2
 jl8AnjujFRJcMfV2R28jiZ2BS9mnvqjU
 =klyl
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.309. Wesley Shields <wxs@FreeBSD.org>

 pub   1024D/17F0AA37 2007-12-27
       Key fingerprint = 96D1 2E6B F61C 2F3D 83EF  8F0B BE54 310C 17F0 AA37
 uid                  Wesley Shields <wxs@FreeBSD.org>
 uid                  Wesley Shields <wxs@atarininja.org>
 sub   2048g/2EDA1BB8 2007-12-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEdzy+MRBACwXYsfLwZzbzYru+XqMIFKVIIszXJK61UejvQqcuaZRNLSQyM8
 Fc5dI6AfciZV9tH8LDqYmd/vDtzjmBp/h2SPqQfiVuREQ0+c+aplvWvWc2TjFQg6
 CZbb730TtazPXbObZvSMRvLeRM32W9Abj5L8DXoQbpMtC8cllG21fsY4hwCgyngp
 xK9e32zih9ddXk+NgjK627MD/iPPyo0N4cb9omNwOCot8YIRpdJhmvR/yPh+8rmW
 NUu61gV8jn2XB6Ldto8/dR7chqqbBU7bS+hsk/lmbOuLNe2XkQA3e7dd0EEHSYYf
 mx6zjw/dEb9EBANAWI6QOyjNM9npWb/shZi8Pehcty08t2eytd4M7wPI9zLAXsMV
 M3nUBACgxIoW4e9yXeNQ3CI2KD/Dbup+SNha1uCEmzN5A0VfPJzyi4Avdtl9URGC
 HUFnUAs5B366yQTgmkjUcfcWqTKBicp4TAZ2KbuDzMX6f6cikb9bdbl4P62vN718
 5iclN77KfTfc6j4aOdIbnc6J9GStvYY0R2eZRKkr3CsqSuebxrQjV2VzbGV5IFNo
 aWVsZHMgPHd4c0BhdGFyaW5pbmphLm9yZz6IYAQTEQIAIAUCR3PL4wIbAwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJEL5UMQwX8Ko3juoAn3bIDWeVAWOfi1XjXdaA
 HN7HKkMKAJ9RJ4F67NZKo37U5E3UnnVSRLCZ27QgV2VzbGV5IFNoaWVsZHMgPHd4
 c0BGcmVlQlNELm9yZz6IYAQTEQIAIAUCR348ggIbAwYLCQgHAwIEFQIIAwQWAgMB
 Ah4BAheAAAoJEL5UMQwX8Ko3KPQAoJYfbksQ/n/1FitmpqJb+AmpOmkPAKCVXF0g
 Clk43/Af2rVb3Vm91NmuvLkCDQRHc8voEAgA6Tped4TSVLcdXmDMeHvt29i/9rGw
 EO6lbwUZfamHGasMALyhWC2/nWhoCdo6tTP2XT9guEX5eu/FoN+nAEIKKHqNiiuZ
 6jyOuzUFD/d6n8pUkjHRLqLxFznbgW8f0aaG4rNJTQEQy6+X4/yKEvzRxjroNbZQ
 l300+liw6Q5OztzgMjhkcva4Gxf+aVhVMueGVuANj1QhPPqvIT2roRsBY6PPNCGY
 AaymLWBq51UbvE5j2jtCF2nfxYnajauqnJpZK0tSkLMkxWd/Khvv7GmO4v47qx/U
 DTx6iQP/i43JZIqSg8zSGjY9Lr9XJpzxr4FVyW/rs5X3Fp9ZCQxF3Sty5wAECwf/
 Zs93KXphXLWhCal07JQsu0T2y81+EXRue7QltZs+VTHvGZuc949dgnZrq6iRckpD
 unMRJUXNrKP6BFNOJuDAVRVOxxDQc+ydVGwpQFzJes8/9C0TYOaw0k+ayCZapfVf
 L6zktK+g8oYOXVjjdo8hX9xsus5ie69x73Csve59VmGgCwvywuLUcjCWEgMZGRY0
 hBL9ec4uRDVRIdsl15hQ3NGwdxiDEPkJu8QzQv/t4cde+omnI0UdH+Ywk6FZ2qxj
 62QaoTvFhuNfWUdmnEAbIkfRCFnHVEL5KcQs0Z9CM2V6qS4kdD9wzthhYtcRgWjS
 paW/fPyNYLmXuYgvfyk8XIhJBBgRAgAJBQJHc8voAhsMAAoJEL5UMQwX8Ko3AxYA
 mgKQnqx2baAJtOI7VsgWeTBFEi+HAKCaIQDFpsRsUtsuEYpqj+/zH1bwhA==
 =kNwv
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.310. Norikatsu Shigemura <nork@FreeBSD.org>

 pub   1024D/7104EA4E 2005-02-14
       Key fingerprint = 9580 60A3 B58A 0864 79CB  779A 6FAE 229B 7104 EA4E
 uid                  Norikatsu Shigemura <nork@cityfujisawa.ne.jp>
 uid                  Norikatsu Shigemura <nork@ninth-nine.com>
 uid                  Norikatsu Shigemura <nork@FreeBSD.org>
 sub   4096g/EF56997E 2005-02-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEIQ08kRBACP8kqP9uJbHt3w8lPR08oRyvhkUgDO4ZtkragusqjwQ2qfv1GM
 P/cr01I7QH5k8cexhrjroWoaeXIcMUvNtMOODgj+BhjF+9mj66FG4ed9RkVxvqo4
 3v41Hed0bX3z1vrnTNC4KBfS2HZChIZr1ZnQbosW+MRAcvclgOkF4RFYZwCgtdPh
 WQv9+Lo5QHqpt2hgz8tWklUD/RXBD2HpVfbQX0zkwKUYrHIoE+0oMizzFTdQe4RP
 HsGiCfZ19msSb4Pjewm1K+Rhg6wUq9hCE0gX2U9J1BUtXtqAoy4xY1JSPg40bigo
 +kjEAIJ6mA/a1UJXpJ7lDMBzKtwWfxc7F48M2iIJLUaXQzSVyWcZ/V5e9y/1VBsS
 MclmA/9+1Zr0zrpl8/HnqLfHiyT/3CNGKPodqfEb6qkSP2M9RtYRTmeX9BBVh9of
 JyfAlkD3XlDyT+wmLSZKTRvAVeenBe9ApvJIYvShVU3m0R6nfDtREmWtILtFf3Jf
 fwDvNJRoRL0UwkR3AbbMEkhe+6fzUHir5jRCPlV2EiJYrurEsrQpTm9yaWthdHN1
 IFNoaWdlbXVyYSA8bm9ya0BuaW50aC1uaW5lLmNvbT6IXgQTEQIAHgUCQhDTyQIb
 AwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRBvriKbcQTqTkIIAJ4vawXwVjgwFZGT
 wx+99FNG27QbygCeMaOv1igYzwl3AR2Ex5DQA4kSHPi0Jk5vcmlrYXRzdSBTaGln
 ZW11cmEgPG5vcmtARnJlZUJTRC5vcmc+iF4EExECAB4FAkIRRbQCGwMGCwkIBwMC
 AxUCAwMWAgECHgECF4AACgkQb64im3EE6k70XQCgkVmB4DE5TioLKXQjDLhFarws
 7VoAn34rlYTkNXPKyyCfYNKnFy4Kvtd9tC1Ob3Jpa2F0c3UgU2hpZ2VtdXJhIDxu
 b3JrQGNpdHlmdWppc2F3YS5uZS5qcD6IXgQTEQIAHgUCQhFFyAIbAwYLCQgHAwID
 FQIDAxYCAQIeAQIXgAAKCRBvriKbcQTqTka+AKCkKxW56I7qwivXmENPOmIpSCoq
 kgCgkXJC9xya2xLdpejt0QHA5vKdqDO5BA0EQhDUlxAQAL3egLJ0c9xHZnD4u5c5
 xVixwR7I0AvHynNRNqbXKPg2sPBAwDjh/zN8EUSR6tOL28WGlk35x6iYopvixb91
 NKwFzk47Zv9k+71JGKtaSVpxhttI6gO8AabD5mkpxXbaZZhj/mw/7+pliDLZQXRW
 aDJgCwD7XngxVIVkUetTmLT7Zchmj6332X/B0NdG8zRDXoH8CStJdJJdegwJ+zQe
 U0MRZRl9VoHjSAagL2Hk9rrlDwMUN00ectEGurih5CA6qVWAL18GIConndLwD2KK
 a9J854xf1y/VtQKDzU2I3f7eQfgUZs+f6XBGm4mqFJg3+h1dEx+i7wgVZfEN9b9o
 i2JyVk4kHNvuHQt6Eg6oL42Y58v/sbqIrroxtVPciBvYaw2bfQfhfzOS7Ho/P53O
 TXGNUBznH2RIW/GWhJlT9zgfqnchn2D3YUZ2Fa63gItvUwVYoRDPygxMhGqxGRsr
 HIr0envWXjpmozE+aBV89rsWk8f4bt1mp4jiMHKRo6Z8/50wkzWDBtSSguzig2ac
 gMDhGG2QWEKTuOYS7EM6FEz4vhX4KZKk1DGVNkpK5736QE6MNqILlcsPcfGsT3QU
 +7u4DFHQHGg7rdLFpBnKH5KtzHaJugChrxKhJiRTuriM8GzFYvKwOMVrtfThsX65
 ZEzXsIirWKNmDoetffGx9MuTAAMFD/42QLAegFaiqHwjiK5ju+YUu0kme/VMu2/O
 0rXIHDFruxCV9wWzICsvb5Ung7DBFgVTumI2FVLepzVkqXjhye0XJE0IiFdyydMc
 2ahcuwoKsTlCbGzqqsgLcVXmSbrSyDZUjvfPnuOWZjSy3QALssLvbWl33bFl88H2
 VvxRjk4AIDkJm6Q9i8fTp7tbyJfdtJqCFMU2MHK46vPVP8jQqg+mLhh/hPOhoknU
 mlE9DrTGLOqoa8A9hOXjyrZuNeIb8+PMc8YPytFaIOL1Kt93qjJrF1wauzEaeZx2
 fQMpHW5Ud7x+CwSrDK3QV4MLWLMFzP6bb4a7bf57Y9OLn30KWx6ia/Ff5ZYHANH/
 4fK0fgaD1TropYUMkTXn+CjN8GeaEM3tz6FUWYUBjqa2n2coLfFR5kSBK/sO2MmO
 BpFXNqcUiZ198exbqmaF6fpbBaIn2eo3LGGbw4gK4/nmGQb9wvoBPwJFcMXmhN8R
 ymYE+jOFvMJ3W+9DHnryYK9t3b/+5Us3BC/oQKu13e+snXAAcQhtgNTjExU7qzcJ
 CsEwOOdwZF8Zf/0aPgFmkm/PXghZYJfdbmLLbhEdSOmikm3B7pBx2S1ZTAAoXIuB
 uofutdCctHUJs9Qj3ZRE8L+vRWlnzufhX2knX//WegDRpD0wdc94g0BqZpOT0Iuq
 fBx0K+foFYhJBBgRAgAJBQJCENSXAhsMAAoJEG+uIptxBOpOFfoAn20qdgTPaPmI
 Dx8oV0GpgT6zW3ITAKC0fDtfsq7z1vlOerBQRbCc4Rtmeg==
 =/u/r
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.311. Shteryana Shopova <syrinx@FreeBSD.org>

 pub   1024D/1C139BC5 2006-10-07
       Key fingerprint = B83D 2451 27AB B767 504F  CB85 4FB1 C88B 1C13 9BC5
 uid                  Shteryana Shopova (syrinx) <shteryana@FreeBSD.org>
 sub   2048g/6D2E9C98 2006-10-07

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEUn9lsRBADbufFsrk3YtL2jzdLYUufYV9goSp7joMMOwSLhSWf/98DoaW/d
 1bhwr9yAFfA81/ByuCEkigZl6jUW5AEEDuoJ4hxZG6th7OasSMCLHrGv4QCIDsiR
 Yo3TUFlh3Fg7SYZAxmGsMm44u/nB/0oZOWJeTzu4IkoG2QCfoRi+RUIEZwCgupdk
 xn2tovdQA+y5l7uxhm6MW2ED/Am3BVCM5EojGESa8QKTynKoWOzPFSvUvarqORru
 pEpmy5JdPjmf5mnfPvWcyccgAIi4VyuyGeqckFOJBBUaQ7w0Es7G9p+egp/e7UVC
 vgAVRKtSzix3TuXaaB04K3IJVY9vmEwTGO8Jy70Ab1hI/R4MbUUfzuWVaKUic9jB
 p3oRBAC8RgIM9zBTOtbsFTQ/LpiBL2X6oSRrJBvaLtFZEyG4aDGPxF/ESdfzIPrW
 3YePPinAgB1EhVawmP/uj3zhZQML3g69tVu9YhMhRb6C7v1h/nVC73wT3KDnGrPS
 eZzFhgHDr4zfEomXoR+HLjP3u9EMguyzlCfEO58QtTgeXKzZcrQyU2h0ZXJ5YW5h
 IFNob3BvdmEgKHN5cmlueCkgPHNodGVyeWFuYUBGcmVlQlNELm9yZz6IYAQTEQIA
 IAUCRSf2WwIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEE+xyIscE5vFGEEA
 nAhEEHq5H3tzKRdgX+PFn8wyzSgqAJsECHYU7maqvBfs8l34AOwuoK+TR7kCDQRF
 J/Z0EAgAxyVxRfbMBrSUGeCXI1FSWvqZJkrLUeQ2aCN0FiEmrjUMqTgkiZcxortS
 BS9Iuk8aEXv7d4S6qhJLfidM5XgxZs/wXFHNO30S+HHw5EwQuSDg1OGM/vY2i5y0
 hJqZuQos3SpUWx2Hl3y/BlExt+D5jwFyU9hUE1nNru3SltmryJwr+6PDFfom5iYc
 1FZpfnm60ZPK0cWDYk04uMYebgXd55acArmPvZMdzEYl/ChrB2GEv/JTVCJZZY0q
 rfI7WE2wwPb6/+WK+QINb9fqAdGsOlpOgkuFo7Xu+iKdH/EDGWnKQkLMPClM1xMK
 dclJKMz5y+l/GB/dTYWH4NtGeiIk5wADBwf/TLTluCRCFKDHkBuV68mJs/ShXpXw
 tnhaFF5snAmmtAH0zk81byw4Wt1+MUMYZ1rYrmhqyhXcqnAcHYatUbj2lyvzvCxo
 W2qdW6CE+0bj/pCM41oeRZi4LzJx3pYwSS2fPWaBWAeWZ6qLrHWT8lc0RrJMlteJ
 kDnchDP9AVxmi4bvpmUbNPdERDEE66XFtQ3zXpzmb0hLV1Hcv60KVYd3zzRADOaM
 tRnRMN53/yC0C+DDDoV6H4TJwxiTo5MTT7s9a9H/EfMY40RxFGjwojRukCTGWpuh
 pJf2WBCsnvBqVsqJLeOHyxwlbJhm/KXVRbFoAp6rZTshQ8M2kplmygIJEYhJBBgR
 AgAJBQJFJ/Z0AhsMAAoJEE+xyIscE5vFzHMAnjcjCi17pcNEGqdUuGWLXFCyQ5X/
 AKCNc4ZJinPdFRM5W3TXJmKRuGTOVw==
 =DE3R
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.312. (R)}CURT(R)o <vanilla@FreeBSD.org>

 pub  1024D/ACE75853 2001-11-20 Vanilla I. Shu <vanilla@FreeBSD.org>
      Key fingerprint = 290F 9DB8 42A3 6257 5D9A  5585 B25A 909E ACE7 5853
 sub  1024g/CE695D0E 2001-11-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDv5ys0RBACm/dkRFFWNFb6pafzsHX3YHfyYBQAhyoT5ZPvvh7e6RdHYdxYc
 tYjgtOid4jL20Uz7kXYwT5OVYo/l9j/AqknacYoboO5AHcJrfO3QjfztJaorUSqv
 w9dv6DSOQWwTmexeshp6v5aEsOpDbfPtUnFBwcJe5lOBsokk2CqkzI/XqwCgv49G
 uNLbdtIN87CrUwyiLG5nsSED/35/A/9b/KNwjBoBbheCJDByHNPd9svQIpVWTuk5
 i5RKVQQET4ZD5tPQWPnSZ95ztkkwcjjOak+esHK85yTYXXjrfcP7JiE3HIZhyj3S
 dxWaOFEbSE3Xc0BT+8BOAPFfb2WMSdCQFowkRqbMiFudLnz4tZnBmTQcuxqp4G7S
 AFh8A/4jBhhkKaw0KeWtkFKugVgUWZNWZ54aJhUaLg5wGbSTNME74YLO0Xc+wkjY
 id3gG5ayJyecZXCMUf175/ZaSPeNRCBOfMjDnl3G05b/huBFUnXzxTkWCcmopOwW
 5tz4C69UVP1UHg4XMu+f6D48srIaFu+DOMTwniL95vqcGkCUJrQkVmFuaWxsYSBJ
 LiBTaHUgPHZhbmlsbGFARnJlZUJTRC5vcmc+iFcEExECABcFAjv5ys0FCwcKAwQD
 FQMCAxYCAQIXgAAKCRCyWpCerOdYU/oHAJ4kKjpX6iMF1Y0FjPMyFiyUlgjT7ACf
 a3czQMrflxJC/VNuzMAmzA19j3y5AQ0EO/nKzRAEALHq1lBY0OBQBeV7sGOvTaBN
 itMZeVDrGDYUQ9xunaDsEHfz2fD3jXCZLaUayv4LZeWzRr4DbnK4F0AmZLR1v5h3
 LxBuvqHPRma5RyyFRftwTNHM+DWu6TSqnE43QS7Ci+z8ua96CmcDa+PnEfubyNLE
 dco8gfE4oHDqni1R2qVfAAMFA/4uVSYj/DvIzckbZ05FjG+pg4HKsyxyFeFsrm9D
 8JD9tC26k4YxLG5FPBdKRsDrN/lZbnLWHTtZqhE3WlX6DRlea93T9Vi2skbujKcN
 mbao5pyVXWl1dboFquP8ku91CRTZvmdLF6IBnPo0LfOu4jD6DsD5O0UZ7lD/Y+6p
 8WcDfohGBBgRAgAGBQI7+crNAAoJELJakJ6s51hTsJUAoIB80SN0z90ocSdxYGwl
 xkOSm2cvAJ93DigXb3moOsw3BRLlLPQRS6TZxg==
 =aR5H
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.313. Ashish SHUKLA <ashish@FreeBSD.org>

 pub   4096R/E74FA4B0 2010-04-13
       Key fingerprint = F682 CDCC 39DC 0FEA E116  20B6 C746 CFA9 E74F A4B0
 uid                  Ashish SHUKLA <wahjava@gmail.com>
 uid                  Ashish SHUKLA <wahjava@googlemail.com>
 uid                  Ashish SHUKLA <wahjava.ml@gmail.com>
 uid                  Ashish SHUKLA <wahjava@members.fsf.org>
 uid                  Ashish SHUKLA <wahjava@perl.org.in>
 uid                  Ashish SHUKLA <wahjava@users.sourceforge.net>
 uid                  Ashish SHUKLA <wah.java@yahoo.com>
 uid                  Ashish SHUKLA <wah_java@hotmail.com>
 uid                  Ashish SHUKLA <ashish.shukla@airtelmail.in>
 uid                  Ashish SHUKLA <wahjava@member.fsf.org>
 uid                  [jpeg image of size 4655]
 uid                  Ashish SHUKLA (FreeBSD Committer Address) <ashish@FreeBSD.ORG>
 sub   4096R/F20D202D 2010-04-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 44352 characters]
 72HtYsmNE4TLbl0fMctolg==
 =ID+y
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.314. Bruce M. Simpson <bms@FreeBSD.org>

 pub  1024D/860DB53B 2003-08-06 Bruce M Simpson <bms@freebsd.org>
      Key fingerprint = 0D5F 1571 44DF 51B7 8B12  041E B9E5 2901 860D B53B
 sub  2048g/A2A32D8B 2003-08-06 [expires: 2006-08-05]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD8xcj4RBADp/ttN/vrU8xXimyZDEJ3NbJXMRAdWin8hhY5cVDT6n6t6Kih2
 5Z+orVfRUA77yyYprxpkMKJvfsRspWvJeM9/7duQe6C7CSUNwB3bXCj5Q7PG9Oqa
 a6ZNPQ8k0EGZkFRgbbkru8wpcttMr4ngsdIm5cU7Y/bk3O2L8kh/Do1XwwCgraUA
 0z9KKZR+PpMgM6YXmAy0fh0D/3EP//MLIF7RW+wyabjmTGxMB9RapZXlZLTjFFeX
 sOrAhgcjFodwigDHEqLtG5I75wz+z2vuyaLtTPHYy9fkFxKXNE8wNWj++6GMJO3l
 OWRyWNlDLX0d3D22vVWOeh/rLq+PvsEHso1TnOJrYn4Dn4VwVXzSIaGmzGAPuPoO
 KaT7A/9Pgc8gwGPtG31yrp6AixoMZ32wVdxuqndD3M9XK+jtcdDtKvICQcMWCL5T
 E8dwmb2qzN13bBILJHktut5JvjgOgYOJeLZKPAMRZz4MON7KcKNZKmPBuNw1a6cF
 KGkBJfbCh1GIx7DyF/CcFeg4/7IhQoANYZQNc9Zm/tRbg531SLQhQnJ1Y2UgTSBT
 aW1wc29uIDxibXNAZnJlZWJzZC5vcmc+iGEEExECACEFAj8xcj4FCQWjmoAGCwkI
 BwMCAxUCAwMWAgECHgECF4AACgkQueUpAYYNtTv0bgCgkdyW3YFhooTeMExQJT5Q
 FbCTYS4AnReju20M/WngliTt9bdbnbmPeGFOuQINBD8xclEQCADhc4W1TgKJBO6M
 bEnWC16IXR3U8sXU7meMMbclb5vWt3j1jHVczrYVdkEyGxzu+ydxVlPhdGXtxT1W
 8CBjXsfz8DRKs9nMttqPj5u6KQdr+O0zWiZZkoqOdT29X7WZNKWQreKK10PgvmDu
 1rzf0Y87B7M0qnqjKjhqinVhLrOHqJIwfFQmB/E06MOhE3BQqYXc5qvBuq4U9y7X
 Qt/Cxfobw47iwAJEJIExai4mMsbXXtydsj9O1tg20c7IBzJEEDecOFJPhIKtcQ7p
 kRNjVGwAkQhWmXsPZHKkMjgnkhTmH0L7MT2YGK6LHvLiuAbjULYiSZ7WLXMDe3iJ
 al4lDNSrAAMGB/9X9K1Dmdu6pWOub3zkgNybFFh8OoguKJkdO/bh1RejzeNfI9Q1
 M8gO3ePzgXF3+BgJIblOA77t6OhNUQLRcjSs/xZwXG5KVQjRF3XJGkLZQIl3JGmB
 i5eNE/rBIMHSPn4GM8FSDZ8bPGzgaTBhEIos/8nCMpyxf70f+gsbjjW/Dq2HXHNr
 wToHezXX1LzzCqIl2fJgubrMXVbKYQBLy7d/IQnfZp1sGfvTcSJSZXT3wo6MH1EP
 jUpwmfVOGDN1NDQTbuu1vYqSETt2xzIq4R/+y8/xbm8YKBYDCL2EyCGQcwWhFU4C
 RAgXFkuWPiXx/PjfYC4YpKd57/7xgRO9i++LiEwEGBECAAwFAj8xclEFCQWjmoAA
 CgkQueUpAYYNtTtwzQCfc42CUSzItmXxtmWaVRxFSbnwJTsAoKPQ1LsUmEHNo+1s
 X7criQoU0Axa
 =iL/w
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.315. Dmitry Sivachenko <demon@FreeBSD.org>

 pub  1024D/13D5DF80 2002-03-18 Dmitry Sivachenko <mitya@cavia.pp.ru>
      Key fingerprint = 72A9 12C9 BB02 46D4 4B13  E5FE 1194 9963 13D5 DF80
 uid                            Dmitry S. Sivachenko <demon@FreeBSD.org>
 sub  1024g/060F6DBD 2002-03-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDyVYkARBAC2Z/8odq3zwRIQZ9XOF4ZoQ8ITJRrTUwwYjwOf4Kz6gTH+zIGt
 Q57m5w1Scse3J/fDdIZzw0gJgH0XRpKOonWi23di4B3Oyvrdr1Zm6OlqUjoty8CC
 7jo5WlLF/05Vai2HCUmFeqiukCN0mfm3Fd8S+hf1IpE1gaIxCKNvYaf14wCgpoVG
 Tqi+lIMCktV/vxUf3h7KgOsD/3nBeANz3U+Izr9g/AsF/FnHXeawl2m7USaIB7b1
 4CFrQp8FDl6TCAtPHQyQ6pdnh0HZ3h+7cfPB1poRaXUvDimQZR9KHZO9uIilpC2n
 MdBjbkXmvVQ5FhOJz49cXw51Lck11n/+OuP4N4TcIHdt0DQJoUrGIB6X6Op9aOrP
 Ob70A/sFsFfebYdfH8loLsJkHU8VbB2Y0KZBXSnhysQ9muvj1HqT+n66o/3SliCE
 R3cNVMgg51pqxzUC0o6qTVKJbfOrI5b2tbYjvx87ejugQwafhKu8t1liDuUYQK0Q
 S549pzLKUr/NUvJaYU//6QlFIPNSzwB6x4wjrWAKBv6Vn+x0c7QoRG1pdHJ5IFMu
 IFNpdmFjaGVua28gPGRlbW9uQEZyZWVCU0Qub3JnPohXBBMRAgAXBQI8lWJABQsH
 CgMEAxUDAgMWAgECF4AACgkQEZSZYxPV34DFVgCfREoIUfpKaEeGyzl0zKThVC7J
 XccAnjiB85SwuNAxMraQuGDJXojukUfwtCVEbWl0cnkgU2l2YWNoZW5rbyA8bWl0
 eWFAY2F2aWEucHAucnU+iFcEExECABcFAjyVY4cFCwcKAwQDFQMCAxYCAQIXgAAK
 CRARlJljE9XfgA6GAJ9RFwXlNqYap2SI14IPRjX9ZAzvjACeOC/Elh0HkwQ2HZMT
 edpgzOuknUK5AQ0EPJViRRAEAO4VdFfYGd/amgG2MDGqD269Kb5vTFbS5mDczgjM
 6gXZgOjhbvj3x2auo+Pfos6M/bOtHuIk7QFOeOEJ1wcg8wgE3L3kFQPeEPeOgKBk
 /eA1ExIW3hiPeuwNxT3iWEv0GF/rvCSeSK3nuuDBNmkSpJ4LHIyO8Kf5YJNp8+6D
 yJ8rAAMFA/4jaulRHxSsWlFIm3gpBR9aiXGGX1pZTuJpXqjAQcRzDa9cuVatiSJS
 H9wzfE8R4353s5HpaY3AkVRjY6s9AB8bygGdUCQjuIuifTS4+tG/wmaXNgyqBqaB
 6V9gTgfW/7XqcJUGeLLMUpccSRZhlQvHd18aTfPWPB49xu2+arw6P4hGBBgRAgAG
 BQI8lWJFAAoJEBGUmWMT1d+AYlgAoKZWZs7rDLdQbn2d0CVwmWb6hQLhAJ9E/r8N
 n3jf2PI8Psl2wtgvWazpaA==
 =mkxU
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.316. Jesper Skriver <jesper@FreeBSD.org>

 pub  1024D/F9561C31 2001-03-09 Jesper Skriver <jesper@FreeBSD.org>
      Key fingerprint = 6B88 9CE8 66E9 E631 C9C5  5EB4 22AB F0EC F956 1C31
 uid                            Jesper Skriver <jesper@skriver.dk>
 uid                            Jesper Skriver <jesper@wheel.dk>
 sub  1024g/777C378C 2001-03-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 4290 characters]
 Crfzumk=
 =Ru0+
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.317. Ville Skytta: <scop@FreeBSD.org>

 pub  1024D/BCD241CB 2002-04-07 Ville Skytt&#65533;<ville.skytta@iki.fi>
      Key fingerprint = 4E0D EBAB 3106 F1FA 3FA9  B875 D98C D635 BCD2 41CB
 uid                            Ville Skytt&#65533;<ville.skytta@xemacs.org>
 uid                            Ville Skytt&#65533;<scop@FreeBSD.org>
 sub  2048g/9426F4D1 2002-04-07

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.7 (GNU/Linux)

 mQGiBDywu5YRBACKxY/5WzdUtpL2aK2Yy/Yde2spYiEP2vKj3bs+ovV7a9129lki
 ldCu8PhoJO+x+96+AwbrR/T5FlXyQrInMa9U5os/8/HQjTXtY/oeq+UNDNFZrnMR
 Gu0zYICbzgd1rW/tnZJBkB3X2Ao6k0hSATGmP5/sowT7EBSdaM7ZhhqOywCg5A5n
 J7+062MfzdS/3KoSn+Utex8D/2BN/BMLvrItQBUjy0tn8Vsomx+FHbFKOm1cuOeq
 smhsOmsANwIafiZnK4+SnQlVbXJLM6exNTqSimH93y7Q9BX7hmWYl0XVpUui0mBR
 UrVG00PEa0jTLasOkvlyYBS1En4gZ5J2ArE2cYFPkv7jndqJ/pAAZkG+tQnXJ8l5
 g0SLA/4tJHLJ6kPad98V3cVbTfhY2Dn/i+QbHvzBbBj+bETLEUdqOKzADGrWoJeE
 fADfxYi24wHkpH3U781p4SldZpOUvkyYj7YmjqZP0AH6SsKI3i52z1BDQF49gRcD
 uc0sSmv57yvjKCk1Cehen4/qaVcqXWTZ5NfyGb+hbHLtA2FxSrQjVmlsbGUgU2t5
 dHTDpCA8dmlsbGUuc2t5dHRhQGlraS5maT6IWgQTEQIAGgULBwoDBAMVAwIDFgIB
 AheAAhkBBQI8sLuXAAoJENmM1jW80kHL8KkAn1yTiwsMLq9GsqA44hkh1Sk0etM/
 AJ9BiDSqgX0S/wzyXAqfYcsmxS96qbQnVmlsbGUgU2t5dHTDpCA8dmlsbGUuc2t5
 dHRhQHhlbWFjcy5vcmc+iFcEExECABcFAj0dWzwFCwcKAwQDFQMCAxYCAQIXgAAK
 CRDZjNY1vNJBywFtAJ9NCVHRa6GxtfTxae+6ZkTh08xQZQCfcGNMwhcSGJUyjKI2
 eYucgrkwp2C0IFZpbGxlIFNreXR0w6QgPHNjb3BARnJlZUJTRC5vcmc+iFwEExEC
 ABwFAj0di4oCGwMECwcDAgMVAgMDFgIBAh4BAheAAAoJENmM1jW80kHLzoYAoLqR
 3unds+O73Z3EppJna4gECkQ0AJ0Uye7ZXLMTJo7pNmZSBSz6bA/qFLkCDQQ8sLvS
 EAgAinenfe1g5Cdp8bf72+idBePq0zHyPUOpCuFGkiKXecXpgQUHCVYM8IiafB1M
 Or9V97vy1H56sr+HaBsC75mpuPC7lnltoY+zq0zIkNbi20+p/546W7A5MV66xtTx
 D6uUSyZ3jksAaVch+6yQNNxr3CDWiNSjomkK1ExPsjaPAA82L4yExAJJGwUYAPOS
 B1Gw6N3dUtoNuQwJdcw8fjsaRektXsHm6Nnm++3gB0YJ4/x3gcvxlNlONHNp5vdW
 msQAJtWj4isSMfqi6Y4SQsw2MWOKrYr8Lt++m4cQC6/VZXafTR/TrDZCqYhwovyX
 vgLMdKfxTZLqsyZwgWDxFKOEewADBQf8CCEh65lRfWQG3MopboOs2fFp3BsfVMvA
 stV5AYktLHvwGXTW0rx7sCdb3kBtKjiuNFob3gis2Nd05NUxFrzrZsyaktyDiZmT
 gjmEL1LvodDg/mXLRQgl3QDzUL1nlfFQRkcKqlDfCYezbgYFxCy4EGsC86cf8s8F
 ZI0hyXXY+zir+xJ/w4KBtL+cY5LJExh0FyPfNnL+tXUthRuN9wxZwVyQ9I4RTlkv
 ybb8VTWEgzkIf5BiDZalvcOJNAujptlgz2cLnV4Kzu55Xy7jOi5YfYjMbSDa6W5c
 vO/wbcAG3gwZOoeHBRjwTNkn4iBkDPq71o1LDDxHvWUVAO+jU3TrZYhGBBgRAgAG
 BQI8sLvSAAoJENmM1jW80kHL1RMAoNsmDIuxlUf3YwjAr/fSqBOKWgN0AKDc0CBV
 uZAqlAL0tDv8Fiz3HvICMQ==
 =mEvy
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.318. Andrey Slusar <anray@FreeBSD.org>

 pub   1024D/AE7B5418 2005-12-12
       Key fingerprint = DE70 C24B 55A0 4A06 68A1  D425 3C59 9A9B AE7B 5418
 uid                  Andrey Slusar <anray@ext.by>
 uid                  Andrey Slusar <anrays@gmail.com>
 uid                  Andrey Slusar <anray@FreeBSD.org>
 sub   2048g/7D0EB77D 2005-12-12

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEOdg/YRBACkP7DeG+wypqbAvKYmIYMBHsYFCmIf5928MvpCgwO4idtg76IX
 Qd/AQH0sF2uFJiikI9NiJuq3OUXsyRk+7xltLLrgzl7/0GTT6jej8tWFH0AU1/0r
 nYhUJ/svVe+QNNEbMOvCCcZLslv4/fuak4Ilvgcb/SAir8iUL+nfNzwLwwCgw+fG
 2DBpULmZtyMUMZYwyi2UQ2cD/jycHnx1+AHLt24OajcWBoBG88DlcK3ERpg/J+D3
 PYoNfs4qcEhU4UVQw5vhMXBnWxD+BiZf6yrh/GRay11oqShMWl/B4UQrZZBwXBVN
 Lvx4aY6LRA/DAUd0R2CUIwsjaaeBQ2gmvISau4UjtE1ezNI5s/E7oFDNDKkv06Z2
 hrucA/9G3+UlrLhDWd2+VMt99O5FFEhtHbClMUXIhXYwFS/41zy7cGf9p4wA+IQC
 SeXns1bvdZYBxPAYTgDK0XGP8yi0TMpICcXB4v9gkqKIIuO3scB3mH+We66RG5mI
 7sls5BoJ3ARfsJuidRS1Uu0TXqCTcj2NTCtDNWd82nRarNpDwLQgQW5kcmV5IFNs
 dXNhciA8YW5yYXlzQGdtYWlsLmNvbT6IYAQTEQIAIAUCQ52D9gIbAwYLCQgHAwIE
 FQIIAwQWAgMBAh4BAheAAAoJEDxZmpuue1QYMTQAnRGPeBTIOHdEj4nOmVtECGhv
 jpqsAJ4pcMFoOwSyCqy5YXoetkQWrsq3IrQhQW5kcmV5IFNsdXNhciA8YW5yYXlA
 RnJlZUJTRC5vcmc+iGAEExECACAFAkOdhSwCGwMGCwkIBwMCBBUCCAMEFgIDAQIe
 AQIXgAAKCRA8WZqbrntUGGMkAJ45WS+CK9Uh2UYk3kGG6/jmx3kVFACgl3ALZehS
 E1Z1ifNha7XLh8C+U3G0HEFuZHJleSBTbHVzYXIgPGFucmF5QGV4dC5ieT6IYAQT
 EQIAIAUCQ52FUAIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEDxZmpuue1QY
 MzsAnA1T9Wkp8yaxQmPBuuvZNrTdJOBjAJ0TJrwVeQW/+3zffBICU+rptKA8xLkC
 DQRDnYP9EAgAjavYUHgBttL7+qFwfeOJ3oW+sNVNsMp4VGWvy6QeVCeFvVK+Kpb/
 eN9ScAFJM+8wzhNHv3eyXFht0jwSadX48a0FzcYApm+pP3OH6y4Osxhz27P2tc2u
 yzKMV19nZz28cikY2mtH3Y2GtSyn8pOIL2Ar4sc+hK1LnszGTPf6YgLSBlJSnGH5
 +TMg1Pxq/CSDIq4zEv9IyBLlbuK+w1/fqDzLBT5L51FdKDUpsCBZNPaRiin+ZkBx
 LI742GusIYz+aIcwsRBDONnWdemAHbtSFDxMup5SSEvlAtEU5O0gO6bZx3tv+WZT
 6EJ66QsE5IszzTGkw0qK/H/BrsEbyOPbOwADBQf9FOrU6qF1Zj/ONad4vzbjDrn5
 nI1vnrBkJ2QJnMM/d6V2ItUVjz9myqXTgteERmwN60DD1jrTqsw5xWHJ/rjJCoW6
 mUHWjVkUram3OL/HO96t8zmTZDynrGXfnzLqykkLgJVsVmoU/1OCusY6h0CMAiWr
 altooE6mD4dpBQq1svwJEe98/X97LJix0J8W1QLOwOi8lD5kApFf6feTRCzJKcOy
 Szr3NiiwYGGRyHDQhe13KiGoJZQbhoJlbpS7krBTAxyUll6RRtQmlITLF5wmP0jV
 JWPN2tZ5BdmqYEqOoH4h6Dj+D1glXT19YN6kh+CV1w/d6iWWiB1lDXwDOQMtFYhJ
 BBgRAgAJBQJDnYP9AhsMAAoJEDxZmpuue1QY+tUAoK4RQLo2F+0c9PlfrfUOYpOk
 GAzYAJ0dMZ6xeDy4UKlIBdDq4KPZk8IGzQ==
 =vOBB
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.319. Florian Smeets <flo@FreeBSD.org>

 pub   1024D/C942BF09 2008-10-24
       Key fingerprint = 54BB 157B 8DB2 9E46 4A3C  69AB 6A9A 3C3F C942 BF09
 uid                  Florian Smeets <flo@smeets.im>
 uid                  Florian Smeets <flo@kasimir.com>
 uid                  Florian Smeets <flo@FreeBSD.org>
 sub   2048g/4AAF040E 2008-10-24

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEkBvUMRBADvY21WeriAMR1JjTxq3UGnj/gJL1WLXxym4OkZqIOmwcMdL4Rg
 BWzbp5n0eTiY4+p463NC0rRWSoJYnuncUD9uJNW8Hsne/MZ//eUC0TVQOmQeX4vy
 vdeCj2H/Q+oAa/AFqbBAA2bcvqWuwiQ6vg3aSWHXzYtrVPoWFqc0myW2mwCg5j+l
 GKb8J4zs3RX6koAzT++JrcED/RxUcUp9Hh0/J53qwq/OrhdG8R+TVUSqA8Zdc8Gj
 YTqmr58Rrlb5C6EpiWL716B7+iS2sxU0pDlrOhK2xzCnBhaViNjrrEMCiYPm1OyM
 QJAwAlV8aulWKK5bullZ/IoOwfN0Y/3xqcyb8pvNNk6FGueb+c4CCRZA069Arrxd
 ix2IBAC7QAMM8TKpZjuMtRdP+InmJhIkq4YRDXcdIzQopTSuaQlAZ55SX1YPHcn+
 kYQDZhsJr1mQYcpxNSV/+GJmnMNcaLMOdtM6IwyV6B75k+FRr2TDDAHmLXl9+SvI
 QXCqy47IFLWrAtByq6bmnngMqDz+YQJF+yZIoRvLRtBf21g80bQeRmxvcmlhbiBT
 bWVldHMgPGZsb0BzbWVldHMuaW0+iGMEExECACMCGwMGCwkIBwMCBBUCCAMEFgID
 AQIeAQIXgAIZAQUCTOudOgAKCRBqmjw/yUK/CR7LAJ4+IhYW52GMrD3HFP6aMcbi
 a6i49wCgkDLQgMjlhmrxqZBcrNSGzKHXmhi0IEZsb3JpYW4gU21lZXRzIDxmbG9A
 a2FzaW1pci5jb20+iGAEExECACACGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAUC
 TOudOgAKCRBqmjw/yUK/CRckAKCuViBlM0f2r8KK+KLl8pyfVBXJ3QCbBifsn5Tm
 NFB5i5+GQqr6rbl1yZ+0IEZsb3JpYW4gU21lZXRzIDxmbG9ARnJlZUJTRC5vcmc+
 iGIEExECACIFAkz1m1sCGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEGqa
 PD/JQr8JCcMAoNtjrCmNfjb1ZjLZ8uZwN7R31DpNAJ9q3fORQoIZcYmBl6b1X1Xd
 v6+VYbkCDARJAb1DEAgAvVokUAGgNoLIb5atFee/teRvn8+WDIOwWHNMZ/F3w9fO
 1kPovV97Ux0n8mt6O0Z5bERo7rnK5vAqbd9xvW8HXjSdJxvYT23FyrwPyEKnvXvA
 92/yuZ+y7L+xxoHn4RqtFGg1d8iM3C5yGS3o1P54RRAbZ+8oc1p08k1kYosI2a06
 gIKKbvxVZH3ePv1Xl1b25gQKhj14GHm87xq3qclFtiDdP2fZIX5+H2uLwqJGhcPY
 ab3sl8DVLlSr/r4fUzPhSI6vk6MsuVCPUqqwTBybbIFrGMQxmJQjr8UCb/455gZw
 8eRDAxAgPttnk8Iqql/VTxEY3MzlQLGquCC0CpreBwADBQf41qghbeUBIng/1/NT
 6BJkk8irsNCfNeHHCPjkeaR+Dz/3lQb7tJyQ8TVD3i51rDhqaThONi3NqIrs9tLg
 zJOWBvooOzoQ5sGAi/ZtwmIFpRwX2vIm359ZXw2Z8C8HdFshDKcQ2k8cV4z7mbOg
 HVQHPIzXaySglp1m0KHkB9F2ph60l/QNYojXyNI2q+T/vBJMnf9OnF18lPOui2Sp
 peb0CFQ01KSUMXR+oK4p1JKjq52ua4eAo1gk0U931rBr9kZfN1mhcUvD3eSVUwZS
 wKmgZuZLu38IACQGrSBcgHDcBlc5eHTFuoKUn1cEJWi6J4wG6xFsrsYguyN0HF7m
 CVi1iEkEGBECAAkCGwwFAkz1UBQACgkQapo8P8lCvwmVNgCfcS6lzlVs9R2ut11P
 Qpic1Iujn8EAnjI/dpcnSOomuzyI7ZC3xvZLCtch
 =Bnxg
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.320. Gleb Smirnoff <glebius@FreeBSD.org>

 pub   2048D/6C7E5E82 2013-01-30 [expires: 2023-08-25]
       Key fingerprint = 6E06 7260 B83D CF2C A93C  566F 5185 0968 6C7E 5E82
 uid                  Gleb Smirnoff <glebius@FreeBSD.org>
 sub   2048g/11E89DCE 2013-01-30 [expires: 2023-08-25]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQMuBFEJEjsRCACPZlXm85H4IyUgAJeLYYuEIFnPfrwk8VklH9zqaRYtIdd+Mm8t
 GoUQeESq6e6ZcTkYcsBwpvSASnqTCJZNCZTovGtDjJgJIWCglUi1l4y9VMhcjlO7
 9DcAtzY7mmBy4j/DcMQgMZqs70XZi1z/fJTmHyFrMmHJO0aPpX5Nhi/lPyIqBGSg
 mdypdW/Ni1GlSQbdC+kqiRshynoNM3dqZqtJlNT9OMieIhcjnjPWX7jxXmKQdauz
 XN0fe+OjyJDuBGMGNYzj0X8RnQoFojc3w336l4u1sbYck/gKrzPTVy0j/zo3mFrb
 DjHQ48Bm3Kb2U3NPy4Bay2nLJyVNUA+yo2pDAQCr1Qk15XOwHF8tQemWUeWMSWqR
 zc2nUWHV6bteCu1wWQf8Cm0VhQUJSFoD5M9SxSoW1jJZmhgUMie/VFgWLYSf/Jt3
 lee5N7SZPkOJEI4xtgzXq9h7IusdUTGQ0TTeIbwjfcCEx4k8JKTRmS1X0VPWhLa5
 zyxUCuMPp7H5woAEan6Uf98hq9Btn1f+/7y07UPVGoxTNLYbPxCYIlyluEtU84po
 q2ObWJpjUWZ6egV99kML1nWBwqBG6MmcLQVXbNj69dL8/He60fu07pLNSShTEZ4x
 1gNKv0CWqmYFZ82rMejorODsqC3GbVD8oyAf5tP3M737Jwwbvm8G+dhZsNz1etvQ
 o2DhZqAhVd2zfeFEYkcZVq6ccn0HQuLtZ10weQ3+lggAhV/dWrVgY4enzHP+5rjn
 lVx/jrtk7cYC5EL5yD9+KqR7Qk5uQzb49AuqshnX0BCBdHohSwNQB6sYWPEPE/Pu
 f6yv/sylBJowUTyk/HzFyVed+GhqMkmkvCAlby+4x3XyTeMs6SQ/VjSeSrxUW/GB
 ikVKSoJJ/VZHCW9/EkgFTft4JjQvOdDct6EJWpZGXs8IQ9xUp1ZXzgMjOJDrqksS
 rsvzjxC9LEZ2SSomnBK1SePmP40OhXArCzzQJPqCDjb75M7N3AGPtpPCAzYxHWqf
 mkqkyAL3pLTi9MidLHOTA0RHSL3o0Bg4hkb8aoWT/zMFCJbpZeBVwj2XVJJyZFs6
 urQjR2xlYiBTbWlybm9mZiA8Z2xlYml1c0BGcmVlQlNELm9yZz6IgwQTEQgAKwIb
 AwUJE9+MgAYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AFAlEJMqgCGQEACgkQUYUJ
 aGx+XoJEjAD/WR1FV3zTAIUh7WODpusveyFoD8yyj4+9SYpKyzOIYTkA/100uUkS
 Kljaq5ZQbi4HG14d1sVUlQfbkkk9IBXTT5aTuQINBFEJEjsQCADAd9dNiSLBOry0
 Zsefo3+SroPM4OREGxvoXfwb5vnsYybFSpL7Pw4G+nXxejetNZCBOuZVQcYXmZ2t
 Yw+mqjVWdw4z8YWq08arZmQQnReDnrxWx+o0dw6lr9cnUp6rlIb0+u8TVOn2n3aH
 0OhitsiNtF6AwkdikOy2LV+1fC/QVeC4LvZCv9ou4cDl5cHzYLHC5PAbInOR/h4s
 Kw0jLSdpu7SLKgW1fA6lFz1v9KjoM5wrXaBQafTzMHNPQk/soEt8weAwSx7AwZdV
 KBVL0Q4a3MVASR/aS4s6s3LI6BRyPUGUvTUD4HxO+9Fpjisl/uuEPfLx3vUyQGG9
 ecXLexYbAAMGB/9pOX8i5v0C7SkKfuChtEM24c6tr+Ax4X6+p4HIiMjRkLMG1Wtt
 IEf/71gwyfVfQpsTPJ1T+Nxz1OlRSsW7Kt/TQu1nXXN663/hwRFBYGfzC1y0jXEE
 isgKk8a6bWM/Mext1KkMiOqcMoXA7DfO7SSUQ0ll6+fgspCmlcQ0Vrtac35bhncT
 ITwr3ByZk2gZ3EyWcKvMQydGX04+9nJRWScbSrCNxS125+0fUGrOEw/DgZWVx0pl
 LiPlRQS26yFjsgFIXZ89nhyP04uNa4LAdwg1cAnM7Uu4la5I/RAyc49MPhRsYx7X
 spXMbphDiAd4g93YY8ET9gIIf8X5tmCAE7VJiGcEGBEIAA8FAlEJEjsCGwwFCRPf
 jIAACgkQUYUJaGx+XoIYOgD/YCabXZzzgRnhKzjzRN74aJcNvFHTceBXCnGtkzW/
 BfgA/1U9GK6yEjClcH/7BzF5D6f3arBmw5Embx8C0y/ToekH
 =EioC
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.321. Ken Smith <kensmith@FreeBSD.org>

 pub  1024D/29AEA7F6 2003-12-02 Ken Smith <kensmith@cse.buffalo.edu>
      Key fingerprint = 4AB7 D302 0753 8215 31E7  F1AD FC6D 7855 29AE A7F6
 uid                            Ken Smith <kensmith@freebsd.org>
 sub  1024g/0D509C6C 2003-12-02

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD/MDZIRBACfyWbQW/cZnu504r57DAQbCbTYNG7V/TgfZwphIPyC8YnLtmJv
 vLdtl7+ToiG7UJUJsBE9OJdb1qA7JP5+jha/TlzIAUMW8doWNyI52nM1zHzBAZVE
 aB4Gxy7pib9yBsrGYiLbuV5YfB7TUyea31OXpZ4jPl1E6RxlYdVuzEhq0wCgnOeC
 SuO0cJZMXisY7DhoF1Q8ucEEAIALzShJ6bbjABbcvMWmoRwXvIcBsAcjKSdRcIp0
 AP+9i3PSZkNXV7rfYM3+SydTa3sJIVBbdXChQakcZqu9+rmfL53rErErYuRwKqhX
 mkp4+3GO7cKm0Oya1xLF9es/OfkKcQ9LxkEytNEnU7xlUNoP8fkCMJcBIwagzPfY
 7UAzBACEwGP/o1e0R36jOAjrUZsxe63Zopz5138bYdZtmsqwI+QHK6+/tS5I7FCL
 EQZL6fEjR7gF1lcj3gC2nypjO1aqodx0hShlNnz9d3uJ0q8EChjJuc30UhjgTcbb
 ZQv3hssKHkvTJ5ch0x+ohYCfH+Gcd8jbXCZvvS8PcI66DRaz3rQgS2VuIFNtaXRo
 IDxrZW5zbWl0aEBmcmVlYnNkLm9yZz6IXgQTEQIAHgUCP8wW5gIbAwYLCQgHAwID
 FQIDAxYCAQIeAQIXgAAKCRD8bXhVKa6n9nfpAJ9MHcwNehlbFRJn8B9tlLBE2JvU
 aQCeLuore1PhiLZPjHriz0/npGn9xDuIRgQTEQIABgUCQLQblAAKCRDYyjFxW6BS
 wyFIAJkBI9/2PBvvTvB0FZUF2yd3JEQJMgCgpWVGTdChec2z/YGMQ/EeTgNDThy0
 JEtlbiBTbWl0aCA8a2Vuc21pdGhAY3NlLmJ1ZmZhbG8uZWR1PohhBBMRAgAhAhsD
 BgsJCAcDAgMVAgMDFgIBAh4BAheABQI/zB/pAhkBAAoJEPxteFUprqf2oVkAnj0Y
 vcFOkVU9JWyJJKieWL/+OuNSAJkBvi/uFt2RgkNgUOvHR61SxZrGeYhGBBMRAgAG
 BQJAtBtxAAoJENjKMXFboFLDvxkAn21uVgtvwLN82vOpKTvBzwAUVK/gAKCKEQDk
 vfyMyQZayoFeC8cMagaUCbkBDQQ/zA2UEAQAqYnqd58qHyrKfsw3SrTE74/4qneU
 ra7FY74jcUhGhrxOElG5hXrHHEHo+0M+0zFwhqedecj2GZbrzGEl5SxVsme3slAf
 Gt5OaAk/ojOY5d5rTezG5v7jSr4EX0JKDkdlve8RozHsutXznsXmUY/BfO1qACek
 herQeczznycJPZ8AAwUD/1MF+jo626W+4/gMgjgCQ+saOiNI6AnGlS879MUjV0Ef
 j6aPfAJ5Xi7zNqkM+HdNBxjPtyxIK8RqmdAjHDMR8FjlZjf+svwuL2CfXk4jCk02
 OXD4dxJK74w/ZTK2kSW1VW63+5K1lgsRmZvnTpGZ4ijxj4H0r2bJFQ7iUd2kNxpO
 iEkEGBECAAkFAj/MDZQCGwwACgkQ/G14VSmup/YeOgCfcaCQpDfKaEvYiw7XJryW
 b4OXclEAnArceW10G489Csi2QR94q7clHU0G
 =gLKU
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.322. Ben Smithurst <ben@FreeBSD.org>

 pub  1024D/2CEF442C 2001-07-11 Ben Smithurst <ben@LSRfm.com>
      Key fingerprint = 355D 0FFF B83A 90A9 D648  E409 6CFC C9FB 2CEF 442C
 uid                            Ben Smithurst <ben@vinosystems.com>
 uid                            Ben Smithurst <ben@smithurst.org>
 uid                            Ben Smithurst <ben@FreeBSD.org>
 uid                            Ben Smithurst <csxbcs@comp.leeds.ac.uk>
 uid                            Ben Smithurst <ben@scientia.demon.co.uk>
 sub  1024g/347071FF 2001-07-11

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDtMtwMRBADrWbrHZdss5Nlj/VpLW92lUpmYdmw5l2wYRtTTeHXrfvUk++pX
 dJ0l1bSC829hokrlQiJZJdiPqu0fGnhxXoeA5QMvrtjMAG8E+MRSLIUaay08SLeJ
 NhQR/ymiLFmh5ZyzXyG+qhZj7/xw3ynHLQ/KHPhRJpAs9ef0x0rgMZxJQwCg00Y2
 8eIQKg3mikkLllnK7OHgMYED/jEhj6G2BLjKc/QliKn7KZZ2Ev4MMKUj36LPgzqH
 VTEhliqbRylW/nCFWhMyxbqzRjR0t6ng3PJYlSltcwwJheySHRogxV/gUvYMwQau
 WKkyFZfiO8/OBZkbuQotLI+4tU2cQFzBTuFIogh3Eg6PRDKUFx6g1AlbloFgmimX
 mdHABADTVFYFKHY9YuUTfpD0S0uLFQrtj3xyZGfA4tjXtc1xCgSmkxIVUoTzg09u
 EtcEvo8FzmmH5JQQV7cM8TTZutSFcHuCftwbhoMH562YkbuY160TCDHB9xc7hzk3
 uzij7HKskm0b6QmMCI6LAYHhAuTk1IKY03DwLBIgEX8g68wyBbQjQmVuIFNtaXRo
 dXJzdCA8YmVuQHZpbm9zeXN0ZW1zLmNvbT6IVwQTEQIAFwUCO0y3AwULBwoDBAMV
 AwIDFgIBAheAAAoJEGz8yfss70Qsc6oAn2Kxzsk/d1GDM4VssT3U3jaHDX5FAJ9l
 jFv088oFIgnhUiBOmoPEcwnozrQhQmVuIFNtaXRodXJzdCA8YmVuQHNtaXRodXJz
 dC5vcmc+iFcEExECABcFAjtMvDsFCwcKAwQDFQMCAxYCAQIXgAAKCRBs/Mn7LO9E
 LEV6AKClm5AuE0PobuyUVri0ZPT4Qzn/SwCfUO4Q/dz2kXJfcoi+svIdboVWsz60
 H0JlbiBTbWl0aHVyc3QgPGJlbkBGcmVlQlNELm9yZz6IVwQTEQIAFwUCO0y8XgUL
 BwoDBAMVAwIDFgIBAheAAAoJEGz8yfss70QsqkIAn3CdGD3kdBP8cNCWB/mmdlJJ
 2Ba5AJsGjmI0R+adewxQuNIGxPuwfuhqSrQnQmVuIFNtaXRodXJzdCA8Y3N4YmNz
 QGNvbXAubGVlZHMuYWMudWs+iFcEExECABcFAjtMv/4FCwcKAwQDFQMCAxYCAQIX
 gAAKCRBs/Mn7LO9ELCM3AJsF3zHJhMdP7zGhP1Sbwh0vOA8WYQCgxONfpOQhAWu/
 WwnZZnwNjUcnbh+0KEJlbiBTbWl0aHVyc3QgPGJlbkBzY2llbnRpYS5kZW1vbi5j
 by51az6IVwQTEQIAFwUCO0zAYQULBwoDBAMVAwIDFgIBAheAAAoJEGz8yfss70Qs
 txUAoKltbmA6D+5e4f43LWOOqfv6P/jOAJ0eUczvTczRuBzg+7fs0MsrtYtteLQd
 QmVuIFNtaXRodXJzdCA8YmVuQExTUmZtLmNvbT6IVwQTEQIAFwUCO0zAkgULBwoD
 BAMVAwIDFgIBAheAAAoJEGz8yfss70Qs57MAoK3vUyOUBVsEoHitX5eXJDos2JnX
 AKC4pG7X9x0EziSKSi/SFmRRNhx267kBDQQ7TLcHEAQAoByKPA5d5RrBOmmVb6cA
 5T0sQvYBsgHpn5INcPr4/B3pAXROzu+SveIh1yg6f5poE4LhxQ0Yva0sCPVI3WPU
 YDpOSu4l0BikO26sQ1WdGYpRiTxuFaqzKLapIiDOz1lpY4o5yChEKtJw6t94Hckr
 Ss6dPH9uE4hoaWxdbvquTrMAAwUD/RrkuvBBqAjN7flRrnNuQA04j8Oc5/znRiHQ
 Ojq8i0w7t1qrT5zCNbd1S4Avo8hc5+G6ap9nv5KA3G9TKsgBQjcCB038k/k0pzRg
 JZhIOVBXpbPb8ZahMk7Tdm7nGgILJzfW0cg2AwToKpEcxEVrhdtTjc11/J4q+wBO
 07lDXfYgiEYEGBECAAYFAjtMtwcACgkQbPzJ+yzvRCzdZwCZAXcRSox3VdhHpoJV
 FlnCmFbg4FAAmgPfaRZc9BE1SF825LsiKDAvUzs+
 =D508
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.323. Dag-Erling C. Smo/rgrav <des@FreeBSD.org>

 pub   4096R/F94E87B2 2013-02-15 [expires: 2015-01-01]
       Key fingerprint = 578A 3F4F 9E04 9FCF 3576  BF82 BB9B 471B F94E 87B2
 uid                  Dag-Erling SmA,rgrav <des@usit.uio.no>
 uid                  Dag-Erling SmA,rgrav <des@des.no>
 uid                  Dag-Erling SmA,rgrav <des@freebsd.org>
 uid                  [jpeg image of size 4779]
 sub   4096R/F4DE87F5 2013-02-15 [expires: 2015-01-01]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 13992 characters]
 maNTtSyMU9A54ib2sgN0GwxijcvwPyqT
 =ToCZ
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.324. Maxim Sobolev <sobomax@FreeBSD.org>

 pub  1024D/888205AF 2001-11-21 Maxim Sobolev <sobomax@FreeBSD.org>
      Key fingerprint = 85C9 DCB0 6828 087C C977  3034 A0DB B9B7 8882 05AF
 uid                            Maxim Sobolev <sobomax@mail.ru>
 uid                            Maxim Sobolev <sobomax@altavista.net>
 uid                            Maxim Sobolev <vegacap@i.com.ua>

 pub  1024D/468EE6D8 2003-03-21 Maxim Sobolev <sobomax@portaone.com>
      Key fingerprint = 711B D315 3360 A58F 9A0E  89DB 6D40 2558 468E E6D8
 uid                            Maxim Sobolev <sobomax@FreeBSD.org>
 uid                            Maxim Sobolev <sobomax@mail.ru>
 uid                            Maxim Sobolev <vegacap@i.com.ua>

 pub  1024D/6BEC980A 2004-02-13 Maxim Sobolev <sobomax@portaone.com>
      Key fingerprint = 09D5 47B4 8D23 626F B643  76EB DFEE 3794 6BEC 980A
 uid                            Maxim Sobolev <sobomax@FreeBSD.org>
 uid                            Maksym Sobolyev (It's how they call me in official documents. Pretty lame...) <sobomax@portaone.com>
 uid                            Maksym Sobolyev (It's how they call me in official documents. Pretty lame...) <sobomax@FreeBSD.org>
 sub  2048g/16D049AB 2004-02-13 [expires: 2005-02-12]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 7524 characters]
 KMzwh2yhNHGuxYtOAKCQWvphJCOXG2iv+epUwNTl9f24EA==
 =Z1Sd
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.325. Brian Somers <brian@FreeBSD.org>

 pub  1024R/666A7421 1997-04-30 Brian Somers <brian@freebsd-services.com>
      Key fingerprint = 2D 91 BD C2 94 2C 46 8F  8F 09 C4 FC AD 12 3B 21
 uid                            Brian Somers <brian@awfulhak.org>
 uid                            Brian Somers <brian@FreeBSD.org>
 uid                            Brian Somers <brian@OpenBSD.org>
 uid                            Brian Somers <brian@uk.FreeBSD.org>
 uid                            Brian Somers <brian@uk.OpenBSD.org>

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

[encoded data, 6864 characters]
 3mPjEgv3yQyXxmScDQ==
 =g4uu
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.326. Stacey Son <sson@FreeBSD.org>

 pub   1024D/CE8319F3 2008-07-08
       Key fingerprint = 64C7 8D92 C1DF B940 1171  5ED3 186A 758A CE83 19F3
 uid                  Stacey Son <sson@FreeBSD.org>
 uid                  Stacey Son <stacey@son.org>
 uid                  Stacey Son <sson@byu.net>
 uid                  Stacey Son <sson@secure.net>
 uid                  Stacey Son <sson@dev-random.com>
 sub   2048g/0F724E52 2008-07-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEhzbmMRBADtX9HSSMMgEPkwKw0xpJHuBOudjSkMwJRm3CfUZrWpgBhybof0
 wGTZZRk1wdaMZL+4MoZoxG1OObzeLitFt7GAZMNb+8hhGMc91rF/Ayyg9e51rnRE
 DetvoKwMHo12Qj003HSiyhjrWQQRmsUCQeRmVWzPmXZLI4JJgXryrl0pqwCg9cn+
 lMFo9RgnmBGM6+pKXnLYQWED/35bjcbiL3zBXczPz4ERjVn+7N0w5x6aSR1luvq3
 7RzkzZ14tbbNetniPJwitL/PCrZIeA4K0/qiE+YendJfihOJ+NtFlpELBv/FmHHZ
 NlAnyT6CzvtLZm5JccSuNO7Jslg82mzPfSwxZOzwwilF/WEpJ1cw7HDXvpSfWu7Q
 CMlVA/4irRd9oq187iFDgDodFzKEvoZYvmn9evcNhXUkoOADMoph2NUgy3x6WUUG
 syeXSTZFTGjRVTpOaHHGyaO1WC2cbAUqDowhURBgQMWyRTzBQ0MJ12ZmaLpwt79r
 SqCQgtMV/nhbPJ33oFoB+K4gL8bNB3ts5OOFI3K34XA8x24OxbQbU3RhY2V5IFNv
 biA8c3RhY2V5QHNvbi5vcmc+iGAEExECACAFAkhzbmMCGwMGCwkIBwMCBBUCCAME
 FgIDAQIeAQIXgAAKCRAYanWKzoMZ8/sRAKDBQ5RTKLb5A7ZYLOdWtExokCppnQCb
 Bc5ODSrb1mHH7zyAWd1EMN9vO1a0GVN0YWNleSBTb24gPHNzb25AYnl1Lm5ldD6I
 YAQTEQIAIAUCSHNu2wIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEBhqdYrO
 gxnzK2sAn0o03XkCjtXNFfyc39//6SDtT/jhAJ9mtqaGZSlyc96GmkevNo6XZ8Ft
 bLQcU3RhY2V5IFNvbiA8c3NvbkBzZWN1cmUubmV0PohgBBMRAgAgBQJIc28YAhsD
 BgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQGGp1is6DGfMKAgCgyqafXmVhbY3o
 refBOqWKwQSuIRcAoN9jKw1ATmoDYxJT4l9CkvML+EPntCBTdGFjZXkgU29uIDxz
 c29uQGRldi1yYW5kb20uY29tPohgBBMRAgAgBQJIc29CAhsDBgsJCAcDAgQVAggD
 BBYCAwECHgECF4AACgkQGGp1is6DGfO2LwCg3bPn+JtwFDh/BLifAQ/73N7N/4YA
 oL+f1VMA8fiO/C7w3ccGttIB8cXNtB1TdGFjZXkgU29uIDxzc29uQEZyZWVCU0Qu
 b3JnPohgBBMRAgAgBQJIc29iAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQ
 GGp1is6DGfPuewCgtH+NgftuvDOsUoL+Aa9oVWnHCSAAoIFUzeQYjAgXUeLZeX+5
 AO4UNMAyuQINBEhzbmMQCACDtZg1SKY/SydXiG+9BhIgZ9A3Kr2+AbcYWHqhr82U
 4+hjTSrOuvfqGsiI+CXBKeZqCsyntT8bG+NFfPIqP9mIy/6qQjftcPIP9q3Ib5is
 yJ/vO8mQrN1StiLzwqCfHhlUOKv4K3AZGeSF/WxLve0hPLnMI+D0BlP5kf6u8sjS
 QLW0Mtwjvkq4quOGcEiAN/r75xmPketPwME8JdzecSAWkixM4rkkm/weLRe32bjK
 564Sm0JDuRWgCyUSQjyEXjAzgrIjstxPvZleilucbBBy8ngbLu4rei3erbhGOtdZ
 Z3RWbB1WaVopWcmBLpQ+qcG1XuK+FkD0otHTEl+lT4rrAAMGB/0QA6PGZI31Vzce
 6k08p27J+vHdr0rK3O5KCJCQ05OUzhg3Vp/9HeOvQqJYK+C1f8EmNwfuJpL04tV0
 gBmX7DJU6SYhT+iyVRruauHttsh3Us9q6JaeDKO6lvzPhZeLYbi5cpWu40maiOH3
 dkhpnYSb/V/gipfu9k8PCZX6WJmzDcF34kF1e/hcRzPeYVjACILf9qn4QkJf1SJm
 IHJqN96/YjzQsO/SRB9q46RFagz2CMknchh2n9X51J/a/fEVHKR0Anv7Orxia+Jw
 i88yO43uKOTpaNEumFrhKHoJoEA5LqHGGzHRQJOoxN6h4ydq7AkPSVBZwqoIDTaB
 RiKVn6R6iEkEGBECAAkFAkhzbmMCGwwACgkQGGp1is6DGfNzzQCgtC62/2mZeZs3
 7LcMsO/q+4VdAk4An12bm3nDCYxciQr72p+ASCei0tkD
 =uagC
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.327. Nicolas Souchu <nsouch@FreeBSD.org>

 pub  1024D/C744F18B 2002-02-13 Nicholas Souchu <nsouch@freebsd.org>
      Key fingerprint = 992A 144F AC0F 40BA 55AE  DE6D 752D 0A6C C744 F18B
 sub  1024g/90BD3231 2002-02-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: Pour information voir http://www.gnupg.org

 mQGiBDxq4ZARBACJSN3t0e7d8A7LNfvsKsNNfMWbANu/f3vEhDEj4D4X2QLKyk8t
 Ti5/wO2Z7HJiT5QfI3zeRWetvHMWXhAYc24GrTUMdCt2zhUjufi5BdysmcbLiZFt
 9wjJpJITW4A6W7YP55ORkZs6ye/j4Luf7YN4xISWvM9/kzpUtU8R6txC3wCgq28H
 0tdFPUDvyAwr+97vHs97z/UEAIFPSIAsrH00DuudiLpqZB0LE+BcDsSKgxBQsZJT
 06EQQaE9XMN4f46nAtxzFhSbGZL4qIBUO3Ny1Pp0rqjCfumuwONLXZSK829LaaJn
 WfZ5ux9ZjvfYJ86NgUV2tFnwZm2UYQXc4234FfzfebeiSmYI27BMvLJ28xXU+pNw
 vUvhA/9uPu+i3Dk+ha+0UaBTp/HNTAveoTKH6lNOS12XhCNNPQUL0gonJTeWThRO
 z4YttxgLa5I/MoNsub0+GtNrlyhLyHKzjBBHEqJHJp7+zkyfCODnJaxUqoKskUSD
 QF5VX6v6vEQl5UBjGwonHmzsrnuqTb9pyYhfPTch9n22eS6ZqrQkTmljaG9sYXMg
 U291Y2h1IDxuc291Y2hAZnJlZWJzZC5vcmc+iFcEExECABcFAjxq4ZAFCwcKAwQD
 FQMCAxYCAQIXgAAKCRB1LQpsx0Txi0J7AJ9q3/ulyXnWjGWlR0L+3QtfPKI5EgCf
 WTLlr+SXYF+nrW4VvQcJvuyzZyG5AQ0EPGrhlBAEAKQjsjIRO+kHT+9qCYsw6HPi
 BYzH++xP0i5143trUJ66FoEfqOl4UqHwNJ7GEXq9MWgzBH9wDL69Bb4kSKQ9vKwD
 EgAnXObS3FOUPLK5AMXc5jy8rRaUru58+cGs1cNIg69zgQ3FQyWF0FHI7kGsAdz9
 8iUZhXL22I7+EVBgd9DLAAMGA/9oK+Xjo7xdLZvkW8b4nNIA7Xyml2uMLYjg/OVg
 qRkVU5f7KM2oHna7+VtvdJrIl9bTVc6mrTl6GY1/0GYb1edgSu2Axg+msj3fVkGd
 8hWuNQ/T5v45kgPcoJxWLzaWWkDeLQAf5tq/QVmN8hofl6UsrsNDvYTBbl7129uo
 3BJbG4hGBBgRAgAGBQI8auGUAAoJEHUtCmzHRPGLta8An39UVQwz3OgsZQ5e8upC
 VEBCvTUmAJ9/8mbmXF+Ii/JdY6STmU1MMfmQvQ==
 =A6my
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.328. Suleiman Souhlal <ssouhlal@FreeBSD.org>

 pub  1024D/2EA50469 2004-07-24 Suleiman Souhlal <ssouhlal@FreeBSD.org>
      Key fingerprint = DACF 89DB 54C7 DA1D 37AF  9A94 EB55 E272 2EA5 0469
 sub  2048g/0CDCC535 2004-07-24

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEECPOARBACeiKSpedo952tApwSI+rrDIrp5LOC5FG1crAiTpAqy6aP+n60z
 c2euoVDGjH/ncUZ+TxUK/MkzSOFXTjU0TETFgq2UMxSzZCLwPrmQibfHbmnF08+g
 0EjlslsszccPgTEZz6F85aZGYWjU4dhQ1VYP+y5Im88CgahggCB6J+8hHwCggMu3
 f51egcdCrodzFvL8poUYKi8D/i644gOjVN/YamHS5QUGNPJ9xkcq5G4OfK+Ubjq8
 6T1dd7UkJ22sePpKGtRhPNATeEar/HwzLB7r2h+UAD4Yrl6+//EwWB73BgxyCqcB
 X57s57K3+UMblbLR3NWJAD/HpxIBFxXfj55VPk6aH6GX5LzayMxfZVYccMyWOcsK
 UZaNA/0aJkearTpmitBL49fOhz8Je/QIF6riigkdOuyx62yAtYRNrVbDrQvvornR
 Z1CLUp+mixUc3bT+emLFpz2ZXmGqCr9BMAqENh0gayGeekyk8IYLQudFSidL3yHo
 WErc76neXoBE/5M/v7jZCrQS9loS0vITFsui0Rv95BcsNbV0iLQnU3VsZWltYW4g
 U291aGxhbCA8c3NvdWhsYWxARnJlZUJTRC5vcmc+iF4EExECAB4FAkECPOACGwMG
 CwkIBwMCAxUCAwMWAgECHgECF4AACgkQ61Xici6lBGkj0QCbBe+RP2fX0+t1fiU/
 oOcORVeRc3UAn3Y7M2TfTKmSh+5RXsaxcVKWDqZauQINBEECPPgQCACOxltxnJKq
 MHIW1P1u4pjby/v0ZsVWbhqmPzW1L/o0SHbBdPkLn+NZmOKG3sXFkitq1nnXQMq0
 pdWwEK55rN3+iYMpq2OJgubsEDJbo39Lom49w3xXs3ElHKWmgjNUMmiGi3yA3Q5P
 p9E13ze+ZBTTZrlj9xtTsXYPCkoihcjA8iD1G52CJYuVQOCxeKo3d8EZi4sFXhTs
 yGfK7ipLN2jO4H8LSrImMlT5z/ePmhTgo59A+vsIShklJpRlHqYB861sMobUlbCd
 0n7Fng8pD9jIG63usHJgU32AVEeZ9BMaZ5Gjsm7KvIwJH+w8DGnR7016hleSXSEk
 wVbS7zjXKfAPAAQNB/9GQcWpnuKYlVa7olq9XOVHe2pHrnK20wLy14ormB245Aip
 gTCN/SEIgwc09nF2QXXXhzZrxsFCPphgJh7CT8g25LCJ2rchOhCpShNS43I1ol3d
 II4nK0DtXUJc/3qG5PgPaNLHHyskwIIyfL2rKRlufTgByzF3AKXHweJQ9suxGkGS
 i2+l1NBwLwsjee59gEyKXT/cbfkV/IgA+NBpj7QaDs0yhsbPSDAJszbo53aBAB9U
 sZjWP9tkrzaP1eoSbl+LFttLtrivG/v8HZuPlI4lELeRboslI1aUUfZVt7xx4A6P
 u3L1DWOYm9rQ0q1KMlhGQKa/JBtaKy73wwzZujSWiEkEGBECAAkFAkECPPgCGwwA
 CgkQ61Xici6lBGnrNQCbBljRUNo/9EHyCk0D07YM27DYC+8Anj9wU0uuZE798XZ6
 n4y0m1iMcuSh
 =Fl75
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.329. Ulrich Spo:rlein <uqs@FreeBSD.org>

 pub   2048R/4AAF82CE 2010-01-27 [expires: 2015-01-26]
       Key fingerprint = 08DF A6A0 B1EB 98A5 EDDA  9005 A3A6 9864 4AAF 82CE
 uid                  Ulrich SpAP:rlein <uqs@spoerlein.net>
 uid                  Ulrich Spoerlein <uspoerlein@gmail.com>
 uid                  Ulrich SpAP:rlein (The FreeBSD Project) <uqs@FreeBSD.org>
 uid                  Ulrich SpAP:rlein <ulrich.spoerlein@web.de>
 sub   2048R/162E8BD2 2010-01-27 [expires: 2015-01-26]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEtgnPMBCAC3bCUDqq+6pLElEuqGoN33TBfDGjX3CPciCBGBY33u0ThbKFHO
 8VYStfwkwofutees9itDAjbQbJ7vIiQSe/1gt9WLfVUhgo6j57i5lbuVi/P3RMMA
 QjJBSZM/0r67XBqUXdye0xnPuJDKs5LmfY+23AWiWroRieeEBhbkJBQOyvY/fEdE
 dQ4A26/aLR+PDIxB8vrmsTRgwLYmxpnXqPkbmQ1tjS3MtsPgUMAaEQQOyoZJ7A9k
 loivX3S44GGTmehrKaCOivMtK21zR66Sslfr2zCCvzHXp8votrRorTBOGSTMC9ed
 Gp4ZlCAWa243NOVgCYWLsUAT7sutuI97VZunABEBAAG0J1VscmljaCBTcG9lcmxl
 aW4gPHVzcG9lcmxlaW5AZ21haWwuY29tPokBPwQTAQIAKQUCS2CfxQIbAwUJCWYB
 gAcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEKOmmGRKr4LOtLIH/0G99k70
 FWtU8wLnHAw4d5dkV+MpSJOiNK3xfqoEgzcBSnK8h4kkEibwzsUggtIvIQ/xkLzF
 oihFGhL/14+yM9aiyp3cVjPT7TqCN7j0kfKxwDOf7otAAwI+hYUrVG1XVM7qe7Gq
 sIS6ucEAnhjK5s/vxI2wJM8xcEQvx2ubPPtuSYAn3k/+JryIfSJaAiSmxuAfYEsf
 TBKmACwQ0CfthLkOSnBp3xNbmXnOJ7mVA/wZwTZjD2Vm4Iu9SGBNF+gsx7Jhs0/X
 ow6JpY4YsoZehFHzeLg3RINUdq5qmB0eqg0VbYV3YcH0a31nOUTGqrztfJs/V4Ap
 M8pJ3WbDrPugqDaISgQQEQIACgUCS2CgGwMFAngACgkQ524iJyD+6d3PZgCfZ+Ow
 SV3Z2p3IE3rQgIf+f67SZxEAn08H7gIDjHWv6P9Mt0JveEgBqqaftCRVbHJpY2gg
 U3DDtnJsZWluIDx1cXNAc3BvZXJsZWluLm5ldD6JAUEEEwECACsCGwMFCQlmAYAG
 CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheABQJLYKDuAhkBAAoJEKOmmGRKr4LODJYH
 /j7RKNrmeszuP7hQ0sQpnn+8xmbp6bmNyXK+h3L78y1mVagMWlrJRbPe8QVLR9xq
 AmI7jIR4oVkcLhm/jnYnlqIAIyNLgrOQ6dIFMbwzd26AYS/Ozy7Grl+THXZJMcZ1
 YTNNcPpmUsC7U76viLLw2CKTMzP3LHribNCoNmfhvplGdZibwW3so+ZjEzrhmjtP
 efLnYmD2AlsJADMhmOy7vgEUSdz7UnIiVgInpf11yQQWarAwAoiKxDSR1D3MaQcW
 JmyG8mhRqyJmFtbmARZaH/eGm+QyZKYuFY//NY9/ugt8xBhhUTeWN80dwZnx2rw2
 6kLsWh3iy36yWNRF1sY7x4WISgQQEQIACgUCS2Ce8wMFAngACgkQ524iJyD+6d35
 ogCghywJlVYXlcjHCqUJkZ4mc8/sW9cAnjUU3AThywjlZFNaB4ngPYGIXHZxtDhV
 bHJpY2ggU3DDtnJsZWluIChUaGUgRnJlZUJTRCBQcm9qZWN0KSA8dXFzQEZyZWVC
 U0Qub3JnPokBPwQTAQIAKQUCS2CfRwIbAwUJCWYBgAcLCQgHAwIBBhUIAgkKCwQW
 AgMBAh4BAheAAAoJEKOmmGRKr4LOELkH+gOD9ML6IDd4Hdu5I7JcmquHejOJoEQ9
 rJRmbExegiCLtTtxI98f2GF9fMgYbKEZ2DRv9dT4tRYhJgm2ko6kf+BsLv1ilP9j
 MRJmzFe5RtVt+ot03+8bgN2TAQ6J0DknMT4sbpKWfMKgw8DQCDgK6aUxAHE/PO2f
 49Wdb6ZxXIwYQKBUsPhAB/a4Jn7C3cjG/CqtkcsWm/INNdrr8wmqFQlQByYkE8bN
 U/LS8UEIf64o59sQW8qmZfMwy7MWsL5VDvJwG/llAAYK5V+Uu+kLDwn3Vuxp5144
 rR7HgAgt+lX3IuMjvM72bc0ooljxqfGRwyfXkVqS0u7YKMIylibWlwmISgQQEQIA
 CgUCS2CfegMFAngACgkQ524iJyD+6d2hcQCfXmKCFRSNF7KxaIqfFbAZUFhHR6MA
 n0G6al32pXWhiV2i3sHyjDq3YCrCtCpVbHJpY2ggU3DDtnJsZWluIDx1bHJpY2gu
 c3BvZXJsZWluQHdlYi5kZT6JAT8EEwECACkFAktgn6MCGwMFCQlmAYAHCwkIBwMC
 AQYVCAIJCgsEFgIDAQIeAQIXgAAKCRCjpphkSq+CzppbB/9X2o72Knam5vdu9nAK
 vmkXmOmKMtp9gJ6MDXLCG/a8DME5weE37i3lmHkm/lKThNRteLajeWz1OWTEODSD
 4lq9BOpr0fDVtSEGsrgQOIj6m/RGpKhmKmyZcsGhTC9OXpcrUk5QnFFb47+25PhC
 I6cfzADL06WGPDkTEFsB2f7ugJw00iC2Kcr35YG5TvvSR/tGRCo6HZ7ooTbLAVmu
 wMrAxwIsPv/ycFBZ5e4DQiIaxsVDPS5sQDHmoIhhRgOovoIinXXCpEl0JvnkegLG
 P9ZWHsmUEIlzU20iMBDmwDmxbsMhtiIFpSNNwA1c3wE786mTQ31vcvscR5p6JJCe
 v9yHiEoEEBECAAoFAktgn/4DBQJ4AAoJEOduIicg/undB58AniViZmymFbmu6LcB
 IQdX7tOfkKQKAKC1L+dB4cKQwTLHMv+PTm3ZZQUCiLkBDQRLYJzzAQgAs/C4imB/
 b+pPBbSm85RC5tgzng8RgF9S1WXVUJupa7QEetNn58yodQr+j+ACoNeX3EKHd58m
 Ja2HyU/cKo0UwNOJA6iKwfrWXOGj7DigxdZdZ9QE/IyzsyrQPIbAVxZn1v3zmpTn
 ngueh9dUda0KKzeq8n5J6OjpS+G6wrMe1tnicM1vh18wIS1JNU/EgQ3hQ5y6Docs
 4xjiYmmO+UlmW/SiiFhwR0b5pwEaQwSLLX4OjEdpxb4E2gxh4+V0Bk1BzpS6GygU
 Qvk1Ct/elQZX3Cyo88OlLSG/UiYGI04JDuyA8wwbriQezVMn0PbVXdo6tR7pqpCD
 QAtI+LFEM9VjbwARAQABiQElBBgBAgAPBQJLYJzzAhsMBQkJZgGAAAoJEKOmmGRK
 r4LOtMEIAIrN0mDZgdvcsV6RmSfoWWawDOklTOh96B20iKYKWxBSOrGNwAAkJRfL
 4E+y/fu3DMoNUKJAAUZvjTOAl2YXv6U5LNK6IDQ5vGtERKS4VukBeDdgK9bLj95P
 cOQ2khuq4RVRL+4H4sdZyxLDD7Dad77rsuavECIK72Dlb9KX+/HJuHERxpqPNAjs
 FlQv2pfbfbr+SoOTjknLCIjct+lDV//y72WwlJeEYWQhKjVJupxPBGOyQEDCofML
 FvzDnuVl4Ft3qP/dLNwObtfghIz604M0aCpYwtItHA35zHRI/R7u24VtluA4D+Bc
 vKKK08LFvCJ5WIK8LKm1Ad/oQh3yuwI=
 =h+sB
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.330. Rink Springer <rink@FreeBSD.org>

 pub   1024D/ECEDBFFF 2003-09-19
       Key fingerprint = A8BE 9C82 9B81 4289 A905  418D 6F73 BAD2 ECED BFFF
 uid                  Rink Springer <rink@il.fontys.nl>
 uid                  Rink Springer (FreeBSD Project) <rink@FreeBSD.org>
 uid                  Rink Springer <rink@stack.nl>
 sub   2048g/3BC3E67E 2003-09-19

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD9quKgRBADeV4lxkbaQyNZMKsSxS5DJHYKbIy150H97+m+J3vYI9IPhBtlc
 oqnlQTaIpoSn3N8ExxwMADRmevRhTHLhXxgfym5iDEAlIAr5uDMKPfwc3yUPPjkG
 CKKUQhEZeRvrPZyE8D/CicuSDtunnsXttK+7xLsWAS00gCr+cHsMPebivwCgyMiT
 z4YpZ8AlVx1ZDxHIR1CgZMEEAIIcBI4MB9cfOhu9Mje++qIHyAz2jsK6d7/Xu4ua
 r2eyDKb5zsbQCwALBRi/vXdR8lt4XvDjvmHQ36J5vGDnfA5t+KtgmQ3EXInggk0M
 ZTEvnFL1q3H+bHCKsf436Cb4Nq/bPQMCznPQ7IQjiMBWJPRd6Fv93kowNKdtEAlG
 cOn3BADGc8z7dEq+xwNmeXvc0jWJpZXTzT+9eRSQK61wqyJH2gWu8wd1T37pa32H
 Efp3Wod5IUFaS7E5P7kthuoMwhKYu5YJJBOA/iV4a1BAKjTJO7sGPwXXIvKMpoYS
 wcnicf1rhZ1kSLmX06PA8x+2GFPK9ZSBU0XXhbV09JcpTSbScLQyUmluayBTcHJp
 bmdlciAoRnJlZUJTRCBQcm9qZWN0KSA8cmlua0BGcmVlQlNELm9yZz6IYAQTEQIA
 IAUCQ8tX5wIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEG9zutLs7b//Bm8A
 oKysvuif0y9iIRSvLA0KBBDYBA1MAKCWEpH45Gv3c5lR4keGHo6O1EuFv7QdUmlu
 ayBTcHJpbmdlciA8cmlua0BzdGFjay5ubD6IXgQTEQIAHgUCQb6gRgIbAwYLCQgH
 AwIDFQIDAxYCAQIeAQIXgAAKCRBvc7rS7O2//ygBAJ9uO+LYKzNfgcKAv8EwEmKg
 UWvd+ACgstc4SYQz7IDk2V9ELXsLZNJHu+G0IVJpbmsgU3ByaW5nZXIgPHJpbmtA
 aWwuZm9udHlzLm5sPohhBBMRAgAhAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheABQJD
 y1ntAhkBAAoJEG9zutLs7b//5pEAniSKnGBZhNgxgPI4xFrBefn1FX1nAKCJ7l21
 9H5w2fIng8oy+Mc/lipRE4hGBBIRAgAGBQI/un1kAAoJEAahzEOamxxah3cAoK6L
 o2tmYvVDKzXSuyODzWGMIPO3AKCoqHpnLbHUVCK6uNCtUMsP10k4EYhGBBMRAgAG
 BQI/unuMAAoJEAdJki0OPZOdHooAoIY0GBH5xaMQHLT7U/H4kEJoy8gqAKCEFO00
 fn3ipm+gEe1xpp+B4ghWOIhGBBMRAgAGBQJBdq2kAAoJEOU3f22J7zgDoi0AnRHx
 J54/6qgkzk3XYWytM8kORJ8LAJ4kbjFKaxN4FMrfmCXyiobPAdFX4ohGBBARAgAG
 BQJA30+nAAoJEMsdesnWoa8+Ql8AnA7jacrDH6VeCyCVPG3bCehRJGFlAJ9cy75M
 r+7vyd7HiIDkumKda0v1yYhGBBARAgAGBQJCLf29AAoJEHs456GxToKx7HoAoKDH
 l2h5HvFTNZR2yeHfjMr4XKqqAJwPng1h5Oq444Na6toMTxeYmfiQCIhGBBMRAgAG
 BQJCLf3cAAoJEGjhJSt9pcU7QtsAoJFIRKi0yuJBTyaZHUYc9/CspFwOAKCv2fGI
 ZYVRDvIILnXZayCVPJbtsIhGBBIRAgAGBQJBp3poAAoJEFECJ1+oE9XuIDMAoN+y
 gQsgchoxgjgj7xvc+phiXrx0AJ0Wrk5qkVMxH4SThHTmUcWtgUy08ohGBBARAgAG
 BQJCoEL0AAoJEJlSOEh18JoRhu0AoJM7SvWSprG7QDHKOnEXf6naqFjoAJ9r0RXn
 b38Vh6C/S1mkkvlLMhrObYhGBBARAgAGBQJCwePKAAoJEDYDstQq8oA+VQMAniJr
 UHQpCWO9Gl7P2U9mSUM9bmXGAJ44+xRxWgmcbaB5MfNxc/+EhttYoIhGBBARAgAG
 BQJCwln/AAoJECtXItZQPuZ/ie4An23xXBcj8uubd0RH4T4eytcsT/APAJ9UVS4C
 +A6oZ2syWMhLwhM8De7aaYhGBBARAgAGBQJCwl/cAAoJELm9u3R/Ejcr/sEAnAmt
 TRDaCx52VtTFUCZ3gqdJJ2nNAJ9LiD6qEUEsR78lj8KtHIFd3gJyXYhGBBARAgAG
 BQJCwl/jAAoJEO0ktfyslxhcw1kAoIeAi1yRgvSjscfriPPLJsfItirAAJ4svEJC
 OZRTtcLaPTCGljgzNHe1mYhGBBARAgAGBQJCwnenAAoJELa66j1B5mvZtVwAnibO
 IGxb784vCzraDVqA/eewItNfAJ9FqdOZYw/CovHLAj3w2nXFTsGvx4hGBBARAgAG
 BQJCwr9aAAoJELOADYxWullRPjYAoIJm0zbOeXuCRFTtpHMyjVb1VLPQAJ0RAtgr
 Ms9M9CZrOhojTARULOlEYIhGBBMRAgAGBQJCwZauAAoJEEJrd6pui7AhX0gAoMAp
 9Xqrbmk/RMZrNc0l1qo7Z81TAKCfroUBS3Ecih8v1jGmTgPUSkTV8ohGBBARAgAG
 BQJDHqqEAAoJEAYGnPKWlFfwIZ8An3dUfKJR8MQkDF46pY7ehQzyjoyhAJ9I4yiG
 pkBKVRlQnl83NxXeL9jGuYhGBBARAgAGBQJDIKKmAAoJEF924XqIxu326E8AnRSy
 bi01ic4Un4XXDT7zs9BX0GtCAJsEgPknCSS/yYPgK+Duk45J3jdf2IhGBBIRAgAG
 BQJCywt8AAoJECdq1e/TZ18Ig28AoJbmYoCkCeUozLToGrESAo5OuhWGAKCYdOzJ
 9sPgsvr8x/xa8whXrdIB8YhGBBMRAgAGBQJC0F7lAAoJEBLMC0rbivl4Qu4An21t
 BQWlJyrHZ8ZxLeWb3bLC5RjtAJ9zdPh+fDYt4/Z4h9twvCe3nKfAeLkCDQQ/ari1
 EAgA8g7iohL/Ws7gm0fHBa1iStYxJxK6p9oy5zvuN8vfgVsj4Efjm/eS2l1RH6lP
 jw27XdtAMBuEctGFAhtBajgdYhryBhOKeUIOZo94QkRLMRf2mw1gAM/yaTVlixTt
 imq2S8KfLYLTKb8T/ysQQLhaGHuI37pN4BIdISskMiFpDS3vuquN1Q7y6i3cmUUa
 8z7km9Gx98uQfPesUPn+pcAgkL0f5LBH5smNeobJ2TbVTfqKm8070NZ4md8kYtZX
 9YvF7W+6CT/gK0mYwbMkoJdyiGHXLmzbWwnhf8LrOH4cB+2SaGowaNwNon93KHX5
 gyTo5Ok/VSWqtacxKg0i7JBT2wADBQf9EDMyjJ8AoCH2/fGePWfpTb6y+z465AO6
 UA0LUNcMjVO3Fm8KrgvIf/k0SFuEkXfchVPmeBdR8uGR47+A3U/49wJObRrnKjNJ
 BtNZBxqW5rtWHAO470MQ1B89c7Wu2f5SJfqu4HJjy7LAWNCJ//KQ+tsLYrhVawbZ
 /fmmt1cur1qJA/C0OqNhay3CBw00dr4IE5nzUw1qjXQ1Oc1h82JMV3IimPG/Mqkr
 cmwbg++OY0U21uEcya002rhfWSNiNLxlAthFHqK1LNDd5EsePRHkUbRXKM0TWvV1
 8fSN39nNtd3O8nMZn9KvmFyKY6uDAYegHv+Qg3L47VJu2UKVrVVhYIhJBBgRAgAJ
 BQI/ari1AhsMAAoJEG9zutLs7b//78UAoLxcADrltOZuLTJMieSR9zw7nruqAJ98
 hpneRV17ciF5APqU2SSiDrugQg==
 =Gfya
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.331. Vsevolod Stakhov <vsevolod@FreeBSD.org>

 pub   4096R/90081437 2012-05-16 [expires: 2017-05-15]
       Key fingerprint = DD9A 126C E675 1EA5 2A97  04A3 0764 7B67 9008 1437
 uid                  Vsevolod Stakhov <vsevolod@FreeBSD.org>
 sub   4096R/4A5A0B54 2012-05-16 [expires: 2017-05-15]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBE+zi7oBEADSVzrn0+T2LBXDUHA+NvgRGwGPoYQ/FqnDDE9GlYVPH1xAsUIU
 9d+YHC50qiAs8HoDyH2k286VHKqfkB3WOv5Ruw/SIwt0deTLadJbuO2vGim5KKK6
 hW64jQxwYREcwqW70RYaokmHfJrrwlOWNRj+PW+bolqLQLJSYJY3CdKsFa2AkmGH
 wy8lbIX40uCJrL7Out8o5uMwUgdvjUm+U5xqcF43eKTKm7b3D7p5UYhZxr5vySKH
 OHOqO/vzZHKU495dzoRTuUy0gmhztzbnSURdkLaXdjSGOxziMjfrbU0bzmGv92iP
 BA9sMxQtxUm3RZ5SLISmfbJX8/P8SvWW5dOkNKYicL502YLjv8DPeHbnwqqOLKmv
 4JLNPWjbpYjH6Hxt1AdomFH1AYw0UxDreWfBKpNrpyKm0dYzBYyt3PMfEMcdmIDf
 TE6M975wz5j23SecAb2H6snEgcIDE63/yMstskl1tDS0PwjuDLiNxHRv4QweV3Aw
 iszxNxqB5N/A5RdrBta88lI+HmMSL9YbwBRyKmsMqadcgUnJP/HP7cn1cBV2t5RI
 tGW85fPpHl3NNQ4lSzlj0cYI07mqPCpRxLwU+3pqc6qOe+lEU/DKoufIoH5C4cq6
 UjjnQtIqRJBOTyOV2WCIcF/SwYhb+GZq2MOx+TdugSoBRiobz4RpweF28wARAQAB
 tCdWc2V2b2xvZCBTdGFraG92IDx2c2V2b2xvZEBGcmVlQlNELm9yZz6JAj4EEwEC
 ACgFAk+zi7oCGwMFCQlmAYAGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEAdk
 e2eQCBQ3SloP/18wYAAZHQ1dBRapE3bYOtrDx1P0Vx34+6ZkeM7W41bIZTEaURH3
 sF7Dkz99HYHh7E6SAazTqze7Y4CwT8KNeR+J60hYLJOpDfRXphaL01lke5kMOh7A
 C2OxlWtttN7gOrGzLVsdJmJDRHPvIs9hAku+FWdbjXTcTp8ZbGpzMgQ0455p2TRk
 8RPziWZYW48DXeB1lIc76b5A+6yvloaGDTkZujttwzWMhqcM4+v2B43g4MJ+CMnw
 z5ve8jNRmPtdWhoIQreQk/ahibjmi/T83bvEIBkeOZpDcDZoTmjgvUbDxJgyh8uJ
 wjkFAiUg/lKn37H/3JhXV0gteLG8Rg7Aa4JdozVth5qRsMqECBz4K7EE4cPmN7St
 /1may13JI4AIALYxS8ZF7lNEBI1K0TeNlx0rDui48ZPM3vsu3NcxWucGWoxCvPlr
 UhNLRa7ftHcd2wPW5n/GVa3OzLsYCfJ4a6o4lwM4hDxWuFINfq/zuDoOJZLzcvw5
 Htv5tYbi0MjQqibQPOVKQiRwUr1nWv7fUpu4OhRDbdJA+srfmQorBKkU/q0E8E+Z
 eO5kM8m606+LfjvcU64Kt2f8i0PIZNv7+tvPym1GPjKzF0eAGFEcaItlXGy8fOSe
 E/EmzfQO9O7S0PLihgWROnoVw9OQ0wshDYKUX3qteCZQ3/CU64FMGJT2uQINBE+z
 i7oBEADrRY3nyIHRwWIyCIALje4U5useU9BmEkKCcMJglfD+DGC0PPK1JOsOBpZu
 WaBSFo6V2cmbz+19YghogjYkxNDQdrlQ/P9smye70BczdAYcQ8CmzNIE0I4JjbNb
 U2FsZ3q+T6rvINcU00H+86bnoVPCmxXbpqwET+0c+Z9uK9Xrs8aZlEq19XdUH2pj
 60/Xieb+Js5MEhI37BsXpR8DoTpl0rCF1VRMnloDxA9fHeTjUsOBb2TeXJPYPN4H
 IhNlCye6EScOJQ2u4VNBIOSOOmG2H/UgyLhVL4sVeRqDVfvGYGoGO8uyhJfAosge
 n1QcFm6qpsuUjSSQZnwiSR694vHZo/P/7eRFxwFp0WXcIy5AJEd0hn7Gr4sYLOZl
 VNc1mWMS8YJH6kr58h5iymcdMQo6dge2HrgE6qVvPf9OozeNes6bFtYjw+1AQ6ut
 OJ+7qHplFvjLI5Nz6wK15fooeGK3s0r2suLPTQO4bHywTahYiUB0page9IJmrCTl
 rTcPtDj9wuSE1Hj+IlQy8OIAr/Fu4TRIbUezJBTdq/aJTC/zDtaXRjCxqhAfCqu5
 q1qDi+K1ezXvbzCwuLn85qSwbCmTX9p7MKmlAk2ldAxB26x6g7CWRupRZgnU+AUw
 3IA7lxysOJxyqcKqoLwz804Mb/8UTTXU/tbi7e9u8Klou4S/lwARAQABiQIlBBgB
 AgAPBQJPs4u6AhsMBQkJZgGAAAoJEAdke2eQCBQ3/hAP/3LWc9/s5rgHFKiBjlRs
 ELVKgLpcoNvyEEETdDvkluQZ2kL4XteyiKgyya+6AX70X1uRn08PwGO4sgvEEj4L
 vRJhPORNegy3v0CZ5wH0bOeDQF+DA2yNFOFHSjKVeEnKWTHE7NdB6bBlH9n5R5ZY
 nBhvajXTsi94vXBnZtTQMpzjhdZNxQHhKOC0Y9on5JIMnMBeCOT4PRyGoDm6XBjl
 hfZYt3mJ1Hy4QrsLVA5dNhhbK2dKaYm3APvpJBl3aFCUzH4eyLOx5YSOoeJLxUTQ
 shrn/D2BClKOCC1nx7T3qs8Svf9R/vO2T1EOWn4f6J/fqUl5LT5xi62OvdbfDxaw
 tjW1q2HDwS15xoXkEyrYXCEMCD9Fi8PmuY0HMLlldngNDVNI/JlIq+CTX/84Of4m
 toMd48Vw71TDmIsfdo2Fn+MkOva0LTb2/TtvvDmvRf9mGZL1jv67m2J/lNTFGd3i
 f1b9xv49lPYg5ZbsStHsn923azxpgvrPeE5CxqHCjWjrfEMG1xYwWdGMvLfunj9m
 5qkfns3r8YIDAwSRGKinf/THjZWyfNA1+It5UdTiilfJ6iMNQPxOl/TMDjEOUIEe
 VZEeXRSqCwfwq78hD+I0f+ityKiQWZpnSTTrXLLXJVcd0P0HJwiz3fLuBkjRdKJ1
 XCbWVeYyJqaMXExTQIx+F+uj
 =EHpi
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.332. Ryan Steinmetz <zi@FreeBSD.org>

 pub   1024D/7AD7FAF2 2004-01-21
       Key fingerprint = EF36 D45A 5CA9 28B1 A550  18CD A43C D111 7AD7 FAF2
 uid                  Ryan Steinmetz <zi@FreeBSD.org>
 uid                  Ryan Steinmetz <rpsfa@rit.edu>
 uid                  Ryan Steinmetz <zi@zi0r.com>
 sub   1024g/058BC057 2004-01-21
 sub   4096g/0EB108D2 2006-02-27
 sub   1024D/FEF36DD7 2006-02-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEAO4+ARBACIMxKRWYAPaeAW2k6Qqlf1mWoRkJV+FWxFrrkPM1z6FWsiBFWc
 ZNWYAQ5BvtY+5qtga1FHBMhExINCcgtJf+NQh+U38OjfpIOnTZXku+Sw1Gll1fH2
 Ws+v/wwgC/SCh3RtUSYc1u7oa3i1QTvi2Dnk57AIfvVUv2hm9f4bg83/iwCg9yVU
 QkFFxz0TYPQmTUE98bxy//cD/ijSfviyGs+QyDpCB7l8I03VeZqZlk4zct/wNGeh
 DuYITyMzb5eqhffvo9LrovAPbuEc2voPmYdRXhW/kEXc6PLu+84mY73A1EQSKPje
 R1iQ4ska23zu/hNGLhQYQwX6kVX9PzG30X1MLuVFn3rEy9FxS6CpY+36x1U3zmnr
 lYHBA/sHE0Zrvm2fE+F0BKyEhZJ7+Vj3hwqtpkKdFW9+4xgPXUylFtMMhB5cgFSY
 R/LEqAqmJmPOdgs/961yFrDZliLtvjVrfpOOQ78JbkO01WF7EdARrdV6ii9VaQ6D
 sbZFrX976wqzDGdLvQIOGjGMILO7bxCs3k3dGdD5WyxJQusANrQeUnlhbiBTdGVp
 bm1ldHogPHJwc2ZhQHJpdC5lZHU+iGAEExECACAFAkQChWECGwMGCwkIBwMCBBUC
 CAMEFgIDAQIeAQIXgAAKCRCkPNERetf68mWkAJ9F+kZDo7hh/zf9vaIzFIJP20Gs
 aQCdEtZrQIm/2mxcXY4abobIVk3XCC60HFJ5YW4gU3RlaW5tZXR6IDx6aUB6aTBy
 LmNvbT6IXgQTEQIAHgUCQA7o7QIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRCk
 PNERetf68jeoAJ9I2uKiZnKtElTpIrGZhPFpU2iZYwCghNN3q8Qrcn4bRj/bo/UL
 LA0wUNO0H1J5YW4gU3RlaW5tZXR6IDx6aUBGcmVlQlNELm9yZz6IYgQTEQIAIgUC
 Th+NnwIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQpDzREXrX+vKSiQCg
 rkCRl23wMtHw3Q36BsDCJ/4UMs0An3Nfjjgg/+PC8TQmaL/mnATr0PDbuQENBEAO
 4/AQBAC1qtLY3Zx/gesnPL7Rm9kCE7L5YP1heENlm0FWSzd0zCH4qHjqzSGRVyb+
 0s+ZRRW4heECpF1+eS4W2f2PX8siVrm+hg1q+Tx5Ag1q2Qf8MaQU2nmk9FBWUhCS
 83EK/a7DGAELezGIZ3wKR6MQwZty7+oasM2XKfqIzd+c73375wADBwP+M7AQzrba
 JtrPooPANNO7a1i7gxU9Yz9UmQTYJbiq8GRExMpFJU7l0UkiiT5vN2q+rSBpIobg
 /bADCqODiV0QkqhQ6ASQiUK4ZGvy8Xn+QOQQJtM4YfSUl5bUapRGPND9LgxcCEk7
 Ts2EA916rQf06qCi0tgBf1FNTT1LIjoQdxaISQQYEQIACQUCQA7j8AIbDAAKCRCk
 PNERetf68jxHAJ9xEUFCrSG9NHMTwqXDIe4qkC7SGQCgjRZlBZUz7kXN0TFj3olD
 TJbmAAW5BA0ERAKKIBAQAKTtcqjWCqgwrXL8goWyb2G9a/DvVSj1iYXpXz1O0neO
 BF+Vd8+S0/6XW4bHCMhqWKNAbq4LSUsukxpHcGtMTdAu51/dhyFd97exGNYFFa0y
 7jeQNkkMoElia9s7/SZjfLkdoWr/ULCfSvwuhlO2KzynVffrskJzrG6XeCZZWnHP
 7/YVl2BjOxLj0hQDMgy9me4QMEwBwO37p8y/j+6ckZ8+6tw9GckWq/mvfZSAvWNO
 HIt23jt6AGmfvYu3NWbAnBMHOOtqfZEHlp70ST3Ss8pMjBYTy4vdBJk6aJfzPdF/
 lyoSna1tAu3PteM50h1y/iz1RnzTOJ6X+80nR3jDRRsT/SskZ6c/jmBpLT4f4eBU
 uuOLd/pBwkLKlsBVDzszQJIMNNpsptt/t280aJ5w+qbwD8RkG1bSTI7lLzk/++b4
 qqwkcjlHAxKpL5BrI0iiKgpQv051b3YKD5YBj/oBTSLuPapABiIOWJeWNPEg7A7m
 z036iQjlTKSw0DToT2FuwkDNs4vrI+ZKVxXdOnSjP2Do2scVz+Xi1s1X/U+1UgBp
 j+RWQv3dRXQedhUU/OtLf6tV0z86nALFw3DTW6bYEy4OzO+JB6erBBvbmjZrmeZf
 Tc7sfvK6ObnEfHHOxLMhONv2rjwISeor0SrfaYRxSiJmUHL3bwjcERuJd4eZe/FH
 AAQLD/4gTmCxHIAuMhieUzmLxe3SFDI3yhOq83lhiH4vTnAGkC5flgi9NizOPjci
 FeeUCBXF2STNfprqT/1539RII3PBEdIjGaNTTSui7AEaoox/2yG3UxVUU7UwIliH
 CtqEQAv4vva1TSp+dz7yiDVFYdCSyc6oXzwk0JlI3rZYo/TqGL5AdO53XsWvHHQZ
 jN2NkFJ5n8EuT2ZrDZPlCYsj+pGfdLR3jhC5M+vf+pFSZQF1R47oG2gC+I7z3W+U
 d0FYjSVscBFNDoUu6eBewsklN0RFsi119lCT4HDt7DX75mjDyjh65neR+nBlLDKo
 Bf5J9TKmTZZH0HCVWFwuKGTDpkgfWpeXk92HJTdmUZGCAs11GbQVQrEZOHNrm6UV
 Ie95E58NhYm6QmQI89BAHFl7ALdNSJ4IphJtcdpOK4iGH1ST7twviXaeppf0d9H2
 Bel7se+CRgnRWNxlSuyvvO0IHH0DvPdakMe7orY7cf247J+cRFLCDZkTmEjLdWF9
 WPgq3lGbVujO3WB/AIL1c5lHt8tRDMVE6xY2m18Qk7Cpn86l4d7jk5WIn9yT7/kw
 I7LTREviKwpBtxHPg69ezvk+pLsgtzPXZG05wAAiCWPn806JZsydV/M2QeHifpjC
 MxfCGjtqGkxHInlHorwQWqzBsrzAGJ/X1pvnrly3kdAtpIIt5YhJBBgRAgAJBQJE
 AoogAhsMAAoJEKQ80RF61/ryIdAAoNFlpXW7Ppd8VTNDlIlDyOt+AbarAJ9DDpM2
 igWchUGfMc58ROj90F+UL7kBogREAopcEQQAoerIQGAyddxqLupWOIO2Qhcwrwyl
 yF8LBL3JnTCcGamKHN9d72hIHZdyb5lAI+f5LKbozE3Eew23WaVWNRnonkTpVVKu
 x8n50O2O7zD/cVgJ+b8rWCkoUX41GhTX+IZOJoNRqhxA7VG20hmH8320T3DJmhpR
 PtshG2GkKlpdaLcAoPhJo8KXeaTisvCDiWXYxrVWV6hJA/9SEDTAgHH6Hejb4URi
 REoYswQ+WLFBhcT43iZyrZFodsc0B0gY2jGdJMcELDrLaTqwsotDD/5NMvDfOVww
 zw/ci6vTC+2q1kpvu7tcVYvUdSI3kr2zjW+7sZIKdoZYegxK3CmKsjOY4W+u8JlK
 tzAHPLzvHM9f/jVCiQWSJGBfPAQAg/iM1PZOZqs4M+WgcpxMrgLSLhLAL1tZD0gs
 BBBOtOQArt7DSojzlKGjpkClnkuBO5GU2jkqejAorI+WWoZ49gjkaXsqoHG0lH0H
 vhuH59NEAzT8fUg4oVmoOs2lf+hW8sEpXEvD+aZNaiiYOyWDPX0m4YSmvQJzSqN1
 /b1VJ1SIkQQYEQIACQIbAgUCTgfd1ABSRyAEGRECAAYFAk4H3c8ACgkQ0sPSsv7z
 bdd7IwCaAgx3ViZioKiAwMTsKZayZk9RTmQAoKRETnJf1b9965mcbGSQ3f+dz/TE
 CRCkPNERetf68pz3AKDInU4gBEw57s2XC3trJMB8HpYTWwCgsuZ8XADa3kCnjG8Z
 ZTV4zXhavRs=
 =wi3x
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.333. Randall R. Stewart <rrs@FreeBSD.org>

 pub   1024D/0373B8B2 2006-09-01
       Key fingerprint = 74A6 810E 6DEA D69B 6496  5FA9 8AEF 4166 0373 B8B2
 uid                  Randall R Stewart <randall@lakerest.net>
 uid                  Randall R Stewart <rrs@cisco.com>
 uid                  Randall R Stewart <rrs@FreeBSD.org>
 sub   2048g/88027C0B 2006-09-01

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBET3848RBADitK8bahB8Ftqi9wtYsFRGfdm645cTF5fAnxFjC+ouPfLk+cfD
 I6VG1Vib3T+SYTTJ3xPm7tV6RLLlRsdAfSE4P73o5qVe85Dq4JBKYgdCms+0Z7B+
 O0yB7B0KClaXhZpsQtK8yLtROjiJxw1WQ9uOS/me5AHi2cZruoOcYxkzbwCguMmd
 tOy1SL5V2RLfJiQKAFQ23M8D/3m42RjkoMB791fuJ/pH3i98EuXhCwrSv7eZ3xYU
 TY93OwMEwPYaABK3jSygMETj9hu2pYFbrAFKSHQVPLcUBrKYw9+Fjd4XTOOxYZeI
 /+n0xSRk4W+sIQX97jCbvCrtk9jqIz2NQt9IlKxG0Xniio/Q8PsNNbO+jd5HSXqE
 ja2oA/9+r3LUi3jKH9rpY6x4Qz/DBpcNK4v5Fz24mtkwTfjyfC2nTlG58bSbmulE
 1tfOLDL5BHmGoyWIqaFzIVIA5oGo9EYG2RCx7Vr+WgsY6jr5tX7HlhByoE5Wemoz
 YN5CDC9KCKe7TCpVJtlq57c02kE0OT3gqYsflidfV50Qzt9jI7QhUmFuZGFsbCBS
 IFN0ZXdhcnQgPHJyc0BjaXNjby5jb20+iGAEExECACAFAkT3848CGwMGCwkIBwMC
 BBUCCAMEFgIDAQIeAQIXgAAKCRCK70FmA3O4suHBAJ9kvtlm5qy8c6qSizjcvuzj
 q4gFJQCgqthVasQ5jNFZf1p4vM+gD1T84M+0I1JhbmRhbGwgUiBTdGV3YXJ0IDxy
 cnNARnJlZUJTRC5vcmc+iGAEExECACAFAkT39KoCGwMGCwkIBwMCBBUCCAMEFgID
 AQIeAQIXgAAKCRCK70FmA3O4slQYAKCNWFpgxPkfqz7PoTUcobiXbu7EAQCcCj0F
 mj5AKPyuPbwP3JT7Cyf4Fs60KFJhbmRhbGwgUiBTdGV3YXJ0IDxyYW5kYWxsQGxh
 a2VyZXN0Lm5ldD6IYAQTEQIAIAUCRPf07QIbAwYLCQgHAwIEFQIIAwQWAgMBAh4B
 AheAAAoJEIrvQWYDc7iyy60AmgLBwWw0LjdY6+zyUyUhRm9s4vZEAJ9F6dw61khm
 NQlfhpvoBh24pl6GTrkCDQRE9/OUEAgA7GAeZ2BgjNDYa42+GV6uo1FxadTNppdN
 gG22xgg+4SXnWZ25O8dofrHIwP9rk/qomw452MoAlVevV20uYthVqAXBWRGEhO/q
 zKfyZxTe8aCOs1mjCKu9fPkSgNUDoCl6jCac/5mDdcLdVT3domBJvGiqqSQ/B1JA
 3YWrYCnnLTUN2a2aPW0ZK14zCSjaWQFDcm8kPi1WwKu9yldGnAPoT03+JF4KN0kB
 YkdmfEAFOJ4kjm2UROJc2aVUtjeMH3nqvdlTmuw6c6cmMMSIlXkcrTO7gRLmnx2J
 HgSdukq0vEtgND6O/o0n9Rnr+UccOCCz6EJkltL9knjKwutdQz9x8wADBQgAkEfc
 D/VQ1sUCgS5xyrer45zxW5NdeuFI+h12D94MKopczr73p+7Tc1bSDZK1M4e432qV
 8hNy8Q6gYowhuuBqxI0LYcEtrJld0ma4cnMraRjkId2jmyK82c+O/K1w+vcGUsYu
 nxYBiGwtTTo/R+202kp6VGD7jnIxGQs5WsMmnh8EL1m4BXeFm6BzfT29SuV4bdoZ
 6/YHyPLGVgtnPBCNQUjLvXqdaOlk3E1wCBd4A90pC1dDiN1rsAxOTcxwgyKfasXx
 CZsdBaXEYYUIfm9WrAFc1S/baV613184I1duBfCJWMKxGXMSr68CeFQ+I1036lsZ
 IdHoq+Y3nZ5jPRUIYohJBBgRAgAJBQJE9/OUAhsMAAoJEIrvQWYDc7iyXiAAn3XC
 FR1XLpBIlAr5dn8ozSpbwfoHAJ9ZDFSqbQt/EDawxqaoYP+4p4Q85w==
 =jM4N
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.334. Murray Stokely <murray@FreeBSD.org>

 pub  1024D/0E451F7D 2001-02-12 Murray Stokely <murray@freebsd.org>
      Key fingerprint = E2CA 411D DD44 53FD BB4B  3CB5 B4D7 10A2 0E45 1F7D
 sub  1024g/965A770C 2001-02-12

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Comment: For info see http://www.gnupg.org

 mQGiBDqHuqsRBACMfFOo/NFWEADUNcCq/6yvGLAZL1V4okeB+zTlIf/NJCiA/AT2
 AKiFNd4T3lYLlUjm44/OcPhelAqFSrtgmBLovWJibt7nva0dlOIXStQQSikzMOzV
 4tgtiQF2ONXIqFlGcEfKo5/fcxrsJ2EpQqNX7ujGtsKHpsZpkqrcL74GowCgzuwK
 PxnD+AHoa6YiX6LIhZA3ciMEAIS1vMlXFQJD1m7831ej8gBtdRVqYVHS3RohJmyY
 91eGsVdDnDtywmWUA3sg/LTRRU77zx36MbAp40XZJJeSfLUp3UeKrcxSoxpI3L/V
 C/V6BBnOLDQ5GcUiRwQTSClh8Ck2Hyi1msA00FZJxTdgPpa+CJANwAM5M+y3DJ6+
 uZSpA/9/CNa8aRcI/OPfs5SeTA/m9SSV+ITSAIfcaVYflquqQwnNh+c7SJ+3Poys
 BUahaTVcFHRrRmrVGUytek18i77cNe4ZItlUn1qu/yZwbVyTdGek8Zbv3pGIzP8r
 8r57HwL8Gi252Yv5ovCRThzsshEfN5yQizbKgHiWWmr/1FEyUbQjTXVycmF5IFN0
 b2tlbHkgPG11cnJheUBmcmVlYnNkLm9yZz6JAJUDBRA7PNuWDu2852ZqdCEBAbUv
 A/9SDqoqWGmNNtNG9prUMqe+Rx3HqkukymKicFzvEkCjULQa1sH2TeM7ZxfqDh86
 hbtJEzF2/AsbYIhk6fg7adEV4+8WfZs3TRCHxBlWY2BXEW/9zWmSL/4YNox+BQSQ
 yo7ue4S2K2wfk2JgJeh1e/rEuBk1oR+G9NxfT7eKNT8W4IhGBBARAgAGBQI7cIWo
 AAoJEA9QMphcQTsIRsEAn0QX5oqWK3a6wPhbNHPjkhUH6jfFAJ9+kLllZ+J8AkVl
 LwTQ+owZAVuSA4hGBBARAgAGBQI6r/ZnAAoJECAVMdWEXf7dtnoAnj373ngJc4AU
 WJ+B6QXGhLmBJ988AJ4+qzDA2FJQqDUr+u+iW50y0QAYAIhGBBARAgAGBQI8XEdU
 AAoJECjR4s8DTnOXdFcAoO9z1mz2n/TRMnWu9TbnOBEoWxDZAJ912Q+CPxILPTWf
 0vZNhA/86cW354kAlQMFEDqeC5tlYKmsNPn51QEB+cMEAKc0MMTo/JO7QRQEqBTi
 VWRLXfCjPaA0XCXtw8/oc1OY2wpECRg8baemNZKnpXy1y6iQdUfJGXU8UfiK0Tvg
 e10Rr7v7AdLugriggcElksLLYhgfALy8C6dr5yCcT/gcQN6qCJ4/144eBIry8EaZ
 MYdxqIM7/5Exb8E7wK2gY2wviEYEEBECAAYFAjtNN/gACgkQbCk0DjIZ+YLIQACd
 Fk/ofe08SuTTYiTGHY0lCeSfIicAn2WzGB3b8n2lcA2q6xZhFVGCjXbUiD8DBRA7
 PMC4d84pxY+hLiARAncDAKC/Ote5mlNMwt/N6uJAJEnVLk6fMgCfXXwjERQ4uNfT
 btsBo3oR93gSuLOIRgQQEQIABgUCOzub0QAKCRCTqAdkLDfjdVI2AJ0QHSmZV7v+
 Vf5ZL/iydysCTabdpgCeP3/6CAiw7KjlAYhMatYRwIUSpFCIVwQTEQIAFwUCOoe6
 qwULBwoDBAMVAwIDFgIBAheAAAoJELTXEKIORR995IcAniQ+bgl1JAocyhGbknOz
 z55c9i+XAJ0Q4/tU3vPZ3TkrU8xK8Zct2qvkNIhGBBARAgAGBQI7jq3rAAoJEMiT
 /MUn0FXbpeoAnA3VZSq+WIMQWoBffOxa3qQ4gZaqAKDVf3cq9j8JxhINE55bNjpw
 6HLiAohGBBARAgAGBQI7c/gUAAoJEOd14yTbQbOH8ksAnR4yNm3N9dlHZzG8SG2h
 6jVXStWgAKCFQPVqEYS072jmEQc+pwhoKE5aN4kAlQMFEDqdf131FVv7jlQtXQEB
 YWQD/jEXwixBkuVVuLboFETpUCdMeVc6BpPzrHdfa52aPFKHqt416fAeeeXRly6l
 AxMDdJPxU2ZG3abR4iiaqDKWwiluFkEwLBL0AE2Qx2R/nNZqEYNB0BSUQNPH/Q//
 kG6mLOAVVvRLAL5R3MEeK/Y0ErH/7JXn8JPrl/rKqwCbIsL1iQCVAwUQPMskr22D
 N4pRurLtAQGBKwQAiXOCEjXh0ItyqSJltkb/6Z2DYJw6ypRikRJ+yTypNHD1EobE
 s1wOQS0EHzyXyIu7y2lj9pMhf4aVdYnMObBarg2IDx20qUkCKVEr+evccPxIsXt6
 CZh9Q6D5eaSyjziS0RuHpEubzVPY+raR0u90VJKU4YNzmht9D+ZNKRuTupiIRgQQ
 EQIABgUCPMskzAAKCRDTST7w0perjoE8AJ4uqL6O5gfCXSPKxcGF4scxAu9nQACc
 DpJ7Vx5Y7fMJMmDWAiox1+uHE9m5AQ0EOoe6rRAEAPF15Mz5Kg25Az3g+7OB37Qf
 ZukClm8gdjR9ziTS+rkjYxeP+j+BmrQNyqdyM+dNGiEk+TgJiBy6otjE3RSQHuVw
 xin9yMIuTxa6xh0PX+sV5aW03YUViglWkevdMDLTAaEUwc0y2fZv1as6Huk4k5LK
 NanNMRnU2giytGuCTyq7AAMFA/wMMI9Px5Q0/p3iNDXZ5YQ6zbDR/aC/q2lxN38F
 UJOEnMaSpZvD/EE/gpmI2naHQuGS5C3RrCrX3/7IGGEVE9U0dl+krreVDDxz/yXY
 hX2D+5ZvriekJZHPmek20gT9i9gm3xLl2e0zS1zQ6BcYCtX5kVwIW5PTs09/MVvw
 scShNohGBBgRAgAGBQI6h7qtAAoJELTXEKIORR99rLsAn2+OxqxPJK8ZmYPKX1JK
 qN+IdvKuAKC6p9c3lJBbYHFlhxPDhBvgBaSOKw==
 =WyeV
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.335. Volker Stolz <vs@FreeBSD.org>

 pub  1024R/3FD1B6B5 1998-06-16 Volker Stolz <vs@freebsd.org>
      Key fingerprint = 69 6F BD A0 2E FE 19 66  CF B9 68 6E 41 7D F9 B9
 uid                            Volker Stolz <stolz@i2.informatik.rwth-aachen.de> (LSK)
 uid                            Volker Stolz <vs@foldr.org>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 12474 characters]
 G7oQ/NdFiVk5IOo=
 =r3Jh
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.336. Ryan Stone <rstone@FreeBSD.org>

 pub   1024D/3141B73A 2010-04-13
       Key fingerprint = 4A6D DC04 DDC5 0822 2687  A086 FD3F 16CB 3141 B73A
 uid                  Ryan Stone (FreeBSD) <rstone@freebsd.org>
 sub   2048g/A8500B5F 2010-04-13

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEvD5ncRBADjSSeOophd6EZMLRUyyqvBTYhHJiCmYqDfog+PG84/Fsb7sXXe
 3W8uZ/Wob/wF8vZey+7V9aK8eoJP9aK52SIMFUR8hdbXTrwhHlTc1QrFWLXjVqJ7
 Ct+ORGcqsUO9P/KwG6Waf8UG1Dnb4IZ2bQCoy+hEXpwiE8KLhR5X3vdq3wCgjARv
 ef8JXQvjUiiGUmPTtwumbmMD/0QmTbZOhdjC1TbIEOoj5BRZKWUv6rj2bXJL+miw
 DCTdpwwn5VfmZiYHeTcCclyPH+GfkNAhrYf4XQ0qUBtB054A+0ZuK/oEbHpqw8ky
 0qj2GGCt0m1LybiX0g9MhEZU9/Coq69TGoAFcysGisrEq4gJm29oc1gcXKXdXAem
 pP9NA/wLMp4p5BTd7Q+9fVJo2X7JTAtCL3djhvFpgbSeExhKCHflH+g0gw7qiMKv
 po1ozRY0r0fwr/gv/LcIh/XBImeyodj9Hnx3xd1jhToGoVP4Olm54PxNKLtcRize
 7CfrQr8TPG6MCY10EGVczIz6Qel7izPdqacXeeB8u8RYnoh4d7QpUnlhbiBTdG9u
 ZSAoRnJlZUJTRCkgPHJzdG9uZUBmcmVlYnNkLm9yZz6IYAQTEQIAIAUCS8PmdwIb
 AwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEP0/FssxQbc6NYEAn3Mm+6fmwl8H
 JuLh1vhMkmO+liK4AJ9m5Btl2vy1eKMfijZ2a/zIbGcydrkCDQRLw+Z3EAgA9LNT
 KPMCyYCuRn0OjAMiCcHiaj20sbY5kO8o6GSOT3Gk8cXxNQgglcvfYxuGxKjG3uIs
 9+1Sa1uGkyVwTCt9DUo9EGvtLxZx/AUU88M3aVF8kt3WiIjTEow2EiS1D7gmancP
 PI2snFh3qqbkN3oWcD3rg9uEwxa9i7ptb/45KnCFJ1bB4jDkuNRqeEOGg7uPV8sZ
 /s8EYFqTl5mW8hTvUY/XgKZl8TvFHxDDXQlA83OWa7RW1JI6G6zuJPHA7q1zwKFF
 DZTabKaXB/gQHYj+j5fx8FgzIa3J7s6MUnZLq4e3xf/3yWOgfsRAxgMjL4WUe/GF
 6vOvE3oxTbUMrQ8FQwADBQf/awmIQZWNMi1aVo2Jls5GpvcV0QZTo5HCcItzoEax
 rY8HMaaApvbiGFckN75O08GuKPEtoet232CEBet2D0NS+VKqp3yBcRwKELTttOFl
 fi0ZUWH/Mk5NEJUSR+lUzptNGRmtu4ftPW/apjrtzRTR6k7KxVPZ0q171qQfF90n
 zFeWklDK1lw1PGWk5X0p4qHCCMs+6l+TEgYjCXZdaDJ/e29bNmXdz3ZBiWbu/Kjw
 jk4s6/17TVXl/KhDAyvfZ3IN3d9BN6h+R1gqE/cp7tGvgDTVZ4+nPm8NVaOr5sOl
 4L9EagqjMAqQzcbhtWHG8PE76P7wnbU2I5pHbexqLlTpGIhJBBgRAgAJBQJLw+Z3
 AhsMAAoJEP0/FssxQbc6JK4AnjiZo91wrPy2ZqMytQaPL3SJcmv8AJ9Q9jvmFruu
 qi/JXA9b5UcmNn7xoA==
 =J2di
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.337. So/ren Straarup <xride@FreeBSD.org>

 pub   1024D/E683AD40 2006-09-28
       Key fingerprint = 8A0E 7E57 144B BC25 24A9  EC1A 0DBC 3408 E683 AD40
 uid                  Soeren Straarup <xride@xride.dk>
 uid                  Soeren Straarup <xride@FreeBSD.org>
 uid                  Soeren Straarup <xride@x12.dk>
 sub   2048g/2B18B3B8 2006-09-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEUcBVMRBACN3a/+siykVNlKvwCmd4HVMogG+Oljeu9wyLsI8dJ9Y81bkY0h
 fi7ve3Tfu4GeRcirnrc2FV9Fcsv4dt9DtYQ7PQTPH8kjrSXr3kQoiHE4fGGJl4IK
 IVIHj+iC26JJgbqFcSU7CKGdvZIOJ17IPPh/HhunKBv9ljNJ5MM+WL8kJwCg20Ez
 J3CRnHM90EFk/nfAlJRvXk0D/3rqR1ODyY/8fFDtpOIjkApkw7k2eoJsfqy7tbtX
 YwdMKQptAvz2NxW4Qjfo3NbgGbfN6eAlhoy9Srcfm886KPMA22ZAvCWopFNbqAGX
 e2iOEwbU4JflSq5vLsIhOVz133W6mK1c7VJ0cf2zl+iRWtISES4fOY5s9rEacIjA
 NcAHA/0ak6bks8LqzC64zFdI6bj2FfJbOoTrga1/FQEBSw8bET14S20G/713ZCD+
 tQXXrs8I9YjBQREsKYmy0ixFYFmxMvG0NxkIyrwD/GEqpBbNdkJlx7pUhqv3zyRY
 rzvcmca7jIguu6K9nYi3t45nmCVo4ku9EE34YHzvgFQ15+1LdbQjU29lcmVuIFN0
 cmFhcnVwIDx4cmlkZUBGcmVlQlNELm9yZz6IYAQTEQIAIAUCRRwGPAIbAwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJEA28NAjmg61AFysAmgIisxdd6032Jk2xeI17
 gcHuzXvuAKC5z1x4XxCwELWC9mk9HUlVTWcMW7QeU29lcmVuIFN0cmFhcnVwIDx4
 cmlkZUB4MTIuZGs+iGAEExECACAFAkUcBVMCGwMGCwkIBwMCBBUCCAMEFgIDAQIe
 AQIXgAAKCRANvDQI5oOtQAvaAJwIhTZcNVO1HKFwW5+hfnpE55hAMwCgtgTvelBA
 dhl0HgdkEN+HWtZzEnC0IFNvZXJlbiBTdHJhYXJ1cCA8eHJpZGVAeHJpZGUuZGs+
 iGAEExECACAFAkUcBtACGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRANvDQI
 5oOtQBgzAJ0e+6mp3n17yH4hAzcE2toJ/CPBPgCgrDC3mRdXEOD8Gegm80agUykc
 Fq65Ag0ERRwFhBAIAPf3jtvf8pJMZoO7SQ3/Et3jla1POUcJuk9T70om/Fqi9Y1b
 mxTXR7yu5Rue/ZSN20laoywnJQAJ3BENx7mZHZwCzZDfEU9QU6WipPykt7KbhBG7
 DjXBONGY34wl4RearvGn61FuL77/pkSA1XQ4+5U/hWIisTWnHRufxoykhlyo7QTN
 x/S1bEXA6eTtfT7acA8sZfMRiqb8opOtJPiSMO7vBEYHfkleUGhSJwI7R7ghux2z
 y92Sp1sFO7xb7ZVlKVPo+edqbu5mKRLvhykLiA7keNv/YGkfVjPgLthAo14JIL3b
 95dOkGV/iI+DlYWPa/sDOM2KL0S/wJ7dXMtMVO8AAwUIANqJ9nqvDnWMoiJ2/Zuc
 H9y7CMmSZEdzQwKqaJysyDqiV6LAK9TXsxzzl1UXximPMCb2qwtVGOaRKAPR8qjD
 9GQc0Lb/BCFQ213o0eb+pvq7fFmUxrt7kMUvbwRGhiRbHyo1qf/z+VA2bntosYmW
 9YSpa9eoE3iXr3cF6wQVw/nUF7jm6QQ4M3ak1MiaoICxxCy1x2WzW9mrUePPWz25
 x0Pj0+R3mnWMTewLC6kk3QFM3usdxudGXJqDVch3w47BHV59WgSnzYPshGFp0VlU
 xeJNWJYu0DM/8WeOvRdf/5VdxwJGDtxRyQSDX6niYHWg6tL2Bx1cCxJnnzLLnXDp
 PziISQQYEQIACQUCRRwFhAIbDAAKCRANvDQI5oOtQObqAJ4gRDoYRjl6DWCd2DgO
 ECDwvMM5wACgiAYFjP/BOSY6RZdSBTxOSdyeVdk=
 =Dgd4
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.338. Marius Strobl <marius@FreeBSD.org>

 pub   1024D/E0AC6F8D 2004-04-16
       Key fingerprint = 3A6C 4FB1 8BB9 4F2E BDDC  4AB6 D035 799C E0AC 6F8D
 uid                  Marius Strobl <marius@FreeBSD.org>
 uid                  Marius Strobl <marius@alchemy.franken.de>
 sub   1024g/08BBD875 2004-04-16

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEB/3xIRBADGjxOPVRN2LvXTd6jXqKf4/6pPVPQlKqtwpOZj9JgDVE+V0Elf
 kjvwfCXA0gqt7kkal8i2TU9v2g6IIKP1eUoNpBy/s15Wc8JMlESB6CkfFPNkqj5o
 ohRSoKuB8dud0KR3T531rPfQNmsVRWtxrPYigkrtYZHiTPSZFgL0e+RiBwCg+i3+
 p9+1JBby6tthOolOGdr54xUEAIYounibXk8p54DJeunp0rMbzKYvbXYTOyc4HbD0
 t9kOH+VI3BJ+DlEuCejgwRkxkisjhQbSTa4+EGROKYcVIBBTtsj8JGHiNyRVSQ0D
 +A1KDuZQh7iDwuyatT0xvcvFw52In0dj3RK5hDV2ZX1ec1WiEMKdf8It+WdTSQPT
 UUF+BAC1WEPU92FZefdEDIQQHu17xsCestDOyd6xUBpxyPV2dyUwm8k7OhRalNuk
 nAIXfbZcVVZ/+RWDdfiftoSxQmODQg0JtzhtGEQO2q/FozsCy4Bx8XPk6CQmPMJk
 x/o8MwR50qDlsmcMRR2NDF+I1QOyRpEmugZ6sO+WXm8bkj1J6rQpTWFyaXVzIFN0
 cm9ibCA8bWFyaXVzQGFsY2hlbXkuZnJhbmtlbi5kZT6IXgQTEQIAHgUCQH/fEgIb
 AwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRDQNXmc4KxvjaHxAJ9+D0jNIIFzozzz
 6n/bx6N+yV2rwgCfZRtKVbN4QNEBod9tfer2TgmRlqGIawQQEQIAKwUCR3O7DgWD
 AeKFAB4aaHR0cDovL3d3dy5jYWNlcnQub3JnL2Nwcy5waHAACgkQ0rsNAWXQ/VgC
 ywCgjtPLCzZAAgOuFiLwNw4vF6ZXJBQAnRPxbc9SwccyaGrkk8kiCX1nxVmFiJwE
 EAECAAYFAkd2QQ0ACgkQ722CQfCBGV1D4QQAgo9MiuMFTfyjZn/qfQmSenruVgSW
 GpKiz6DTPhmT767GqaVqaaChoWqPY6/PGPTbk71NleF1v2HU1Orzoj3KqgzE6vVM
 MMfmMXJ7y/A9hg+xImKuThiwMzfJJQ+nrvCc1beJIiMxhJJLHxmBJZve/mbMUs3V
 HC4tGEcdrGecFY2IRgQQEQIABgUCR4ekWwAKCRD09yJxgsm6KU0pAKCIgvYV8BNI
 ES5/8AK02J2lApE5kwCgxetWv8ToTTbUhW2AhaIEHlg8KQi0Ik1hcml1cyBTdHJv
 YmwgPG1hcml1c0BGcmVlQlNELm9yZz6IYAQTEQIAIAUCR3QWxQIbAwYLCQgHAwIE
 FQIIAwQWAgMBAh4BAheAAAoJENA1eZzgrG+NU0AAn1xgOlGk3+FpLagxQh6/O94Y
 8iz1AKDvu7Im3yfxj4LRh5UVKnNYMIJTtIicBBABAgAGBQJHdkEIAAoJEO9tgkHw
 gRld4JcD/j52TeNiPNJ4hDyd0QJUItk8RXcvBtrg2dSl0TGmNs2f1+3fjZ6vdrE+
 5Ry0qh38ywsxs7sEFURPavre4i7EbdOWv6NawUfaIsgXp8Os91bQr+UrXe2esAEC
 SICQS9hHI3qEl8hPqay7rPl/lXM3ivofmrRXXfBRCtxUqy8+CFoeiEYEEBECAAYF
 AkeHpFsACgkQ9PcicYLJuikeVQCdG97q3ZUAYRy7za8JihUzddma5wIAnRS7veJj
 ENbiKHg6MJc2BMFGZ9H4uQENBEB/3xUQBADFOTE426iijaR8FaZLMIRaSexGfOvc
 nPJFF+rkoktpQzP+9BKDwKvt1HmlDXaiaeJfwEfQdK7/oORh9+ynL9ag/KaocJtT
 8eAqhVnoC240NF+PhMlX7YblUwa9+M5MfNmDkNEV92ZFIJ8QjRAzn/G3rQIMo6ax
 BmsF+1P71QEIgwADBgP+Kbmf5TjcU45Wuc3ceZCAEm9o7VMhsU/tVu69x6QRu379
 HqJ9RDuAOdcBWQ/67Jw7blSbe3yWZpqhxLTWwYELJG7/XSNnIsFl3osF34lm0Y9M
 lJl+XBQ3UV2kPgtIMDTXDuklzuhdhbIlhWOXJJf48WkSxeB2WGnnlVvBCjBTx3+I
 SQQYEQIACQUCQH/fFQIbDAAKCRDQNXmc4KxvjWiAAKC5xnCwJYOHHwqreNa98Dah
 W9e6+QCgjchyumMlSJfpEEnGG8vU08TmXrs=
 =QOvV
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.339. Carlo Strub <cs@FreeBSD.org>

 pub   3072R/D06F0BD7 2012-11-25 [expires: 2017-11-24]
       Key fingerprint = 61A4 F2B8 2A6C B81E 5557  0798 78E7 DE70 D06F 0BD7
 uid                  Carlo Strub <cs@carlostrub.ch>
 uid                  Carlo Strub <cs@FreeBSD.org>
 sub   3072R/71C75997 2012-11-25 [expires: 2017-11-24]
 sub   3072R/318AEB16 2012-11-25 [expires: 2017-11-24]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 6996 characters]
 5w==
 =X5dP
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.340. S:-oNOTFP:(c) <clsung@FreeBSD.org>

 pub  1024D/956E8BC1 2003-09-12 Cheng-Lung Sung <clsung@FreeBSD.org>
      Key fingerprint = E0BC 57F9 F44B 46C6 DB53  8462 F807 89F3 956E 8BC1
 uid                            Cheng-Lung Sung (Software Engineer) <clsung@dragon2.net>
 uid                            Cheng-Lung Sung (Alumnus of CSIE, NCTU, Taiwan) <clsung@sungsung.csie.nctu.edu.tw>
 uid                            Cheng-Lung Sung (AlanSung) <clsung@tiger2.net>
 uid                            Cheng-Lung Sung (FreeBSD@Taiwan) <clsung@freebsd.csie.nctu.edu.tw>
 uid                            Cheng-Lung Sung (Ph.D. Student of NTU.EECS) <d92921016@ntu.edu.tw>
 uid                            Cheng-Lung Sung (FreeBSD Freshman) <clsung@tw.freebsd.org>
 uid                            Cheng-Lung Sung (ports committer) <clsung@FreeBSD.org>
 sub  1024g/1FB800C2 2003-09-12

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBD9iAJ0RBACJHmAyofYftDx6hFkYRkCrM999YrKxfYGybHI+MoN2fFPXMvSh
 idYzBGhij1a8E7DGuZ2fGwSxdUZXcUA9PlDPuTmxs/xI/ZgX/qnG4yPgeT7KfZ5g
 UqRpm0/gz/7g5UsvNBw0iUzSbI7tTXprErflhUXX6cC1bPHTeEQbHe+nSwCglpMT
 cpcV93CQpMX+GC16UvwC8MUD/2TzigXSQ9rJNoTLuhsibSK9fh0vzq6rhCrzy2Ma
 G4M9kLvApu7+8YEk9ydVk9EE0PxHTTXGAxnpZzTW/bCCcLubhBqv8eXs2GOOxzHG
 YXb9Oyo+FDe0EAEZ5Swmf/V2eAHV4bYDmXzW9okxIUK6skXtFxQ70DxqcmtAxlxa
 QLgbA/9plT+d5g2s1c11Z0p5CQbxa8sJu4nLFT36DzhR2BmhTEM/X2wSARGe7PKu
 LdWI1WfU4Avoj9sWehSF531tMekMSZ4lp0gb0rYOyzGTqTWjq32mkqep8MDP9cT9
 6H1UaSU96yyc1sprUdU7XDf7TA4jZp2LSLlOEB2UCOa0mBL9QLQ4Q2hlbmctTHVu
 ZyBTdW5nIChTb2Z0d2FyZSBFbmdpbmVlcikgPGNsc3VuZ0BkcmFnb24yLm5ldD6I
 YQQTEQIAIQIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAUCP4IzGQIZAQAKCRD4B4nz
 lW6Lwc3gAJ91P1UQoV68L7emHnjqlf3nK6qzmwCgiVtWyaqQJq4fayifeKfFmT2U
 0EyIRgQTEQIABgUCP2SPxwAKCRDm4NvoVAvGHGhiAJ90wTMq0zYb41tG8M+RoMyv
 oVsgtwCdGko61SUEB+884zRD2bHhwFMg+OiIXgQTEQIAHgUCP2IAnQIbAwYLCQgH
 AwIDFQIDAxYCAQIeAQIXgAAKCRD4B4nzlW6LweOrAKCRWdRCC8hQYwWCa4/upt6N
 hc+SRgCfVybP7alAFua8F010HJiSfXdNtFuIXgQTEQIAHgIbAwYLCQgHAwIDFQID
 AxYCAQIeAQIXgAUCQSQbpgAKCRD4B4nzlW6LwVB9AJ42/CQFoYKDRYz+XmCqBou9
 Y+Nm/QCfZv19FBbMSOfvRW6R7nJTSkf3Uj+IYQQTEQIAIQIbAwYLCQgHAwIDFQID
 AxYCAQIeAQIXgAUCP+GGogIZAQAKCRD4B4nzlW6LwUZ8AJ9q3BbkGIsEuhnp6rWX
 uSkcXYkWWACeNSCb9l9g/650wnXPEHcHsRpzBLK0UkNoZW5nLUx1bmcgU3VuZyAo
 QWx1bW51cyBvZiBDU0lFLCBOQ1RVLCBUYWl3YW4pIDxjbHN1bmdAc3VuZ3N1bmcu
 Y3NpZS5uY3R1LmVkdS50dz6IXgQTEQIAHgUCP2SMCwIbAwYLCQgHAwIDFQIDAxYC
 AQIeAQIXgAAKCRD4B4nzlW6Lwb3bAJ9mJttWnct/3ej1XlvmnAxRq6ZkOACfdZDT
 sLSo8DN73ZKDbiP73KqDPdmIRgQTEQIABgUCP2SPxQAKCRDm4NvoVAvGHONyAJ9t
 QrXQSZDkm71qAw+6HiERQ+qsEgCfWuA857Lrda9ZR8X7IJJ3XLO2HPi0LkNoZW5n
 LUx1bmcgU3VuZyAoQWxhblN1bmcpIDxjbHN1bmdAdGlnZXIyLm5ldD6IXgQTEQIA
 HgUCP4IyxQIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRD4B4nzlW6LwecsAJ9F
 HNrKHPsCJ6ZesY1gJI5HOVijvwCfb5G6dT2YW8TH8GNRFe7rWPXO1E60QkNoZW5n
 LUx1bmcgU3VuZyAoRnJlZUJTREBUYWl3YW4pIDxjbHN1bmdAZnJlZWJzZC5jc2ll
 Lm5jdHUuZWR1LnR3PoheBBMRAgAeBQI/gjLeAhsDBgsJCAcDAgMVAgMDFgIBAh4B
 AheAAAoJEPgHifOVbovBz+wAoIJhcDpcOVIACy+wboHG4nGOQfiWAJ45qvE09ckd
 IX+MDl7xez7OMqDU/rRCQ2hlbmctTHVuZyBTdW5nIChQaC5ELiBTdHVkZW50IG9m
 IE5UVS5FRUNTKSA8ZDkyOTIxMDE2QG50dS5lZHUudHc+iF4EExECAB4FAkAoN7AC
 GwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQ+AeJ85Vui8HhdACeNn9owhjpYr2y
 cYCkOFDv+q3xIF0AnAijfOOUq2oT0d0+B9sALIz0HHrEtDpDaGVuZy1MdW5nIFN1
 bmcgKEZyZWVCU0QgRnJlc2htYW4pIDxjbHN1bmdAdHcuZnJlZWJzZC5vcmc+iF4E
 ExECAB4FAkESZaACGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQ+AeJ85Vui8Em
 ywCdEDYOgC1/YxPHqyvEXGs+JTFFqfkAnjfkTpRPM492elqZkBlQimFGLeWutCRD
 aGVuZy1MdW5nIFN1bmcgPGNsc3VuZ0BGcmVlQlNELm9yZz6IXgQTEQIAHgUCQSQc
 2QIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRD4B4nzlW6LwZ4TAJ9hByDD2ep6
 ixTnazmBJSg3epv9tQCeOM4JaWNwvbOrF528n8PQcgpe/3W0NkNoZW5nLUx1bmcg
 U3VuZyAocG9ydHMgY29tbWl0dGVyKSA8Y2xzdW5nQEZyZWVCU0Qub3JnPoheBBMR
 AgAeBQJBJBoPAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJEPgHifOVbovB564A
 mQGePiZdxv8qVwvtdyf6m9SvosGoAJwPuv0oR/D4PIDKFYtlTqfYN35I47kBDQQ/
 YgCgEAQAwHkhKy54M/yuuJgb4Gcit2+fDnlRZ8yRJkGe8OSl7qx9Gaz0+kwe1Gir
 V+DQFGC/W3gJqjEN12jh11ZUabE3Seeofec94rDZz/YBkf5ofMT1+tN1kwr+ju7C
 lQdZCwNewaS2p6C5PsXCUQQ8ZHfgs8YB7Ze/TY6GvpOoDKqYHO8AAwUD/1ZvVV9P
 e36FE4RkHg3P1YLkMNs5fxleXD1l6LZ8ElQy1V0RVg8sD2W22xh0wP2W9RplsDYj
 UwFKuRtxxoEsdXvDNLaUyG4hXmNUVBz3b3tmZSvENiuj5EchJWO85T+AFT0g7ap5
 wWlxOqmvHC5NZRiAP1fpKpwoSvYTLP418YSsiEkEGBECAAkFAj9iAKACGwwACgkQ
 +AeJ85Vui8E94gCdEqq8xPwuUc/LJQyc1ziacZJ/FmQAnA41/zThbZg2nf994Wre
 OT332jJ8
 =EtCd
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.341. Gregory Sutter <gsutter@FreeBSD.org>

 pub  1024D/845DFEDD 2000-10-10 Gregory S. Sutter <gsutter@zer0.org>
      Key fingerprint = D161 E4EA 4BFA 2427 F3F9  5B1F 2015 31D5 845D FEDD
 uid                            Gregory S. Sutter <gsutter@freebsd.org>
 uid                            Gregory S. Sutter <gsutter@daemonnews.org>
 uid                            Gregory S. Sutter <gsutter@pobox.com>
 sub  2048g/0A37BBCE 2000-10-10

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 19668 characters]
 sTEQABKrEX0m
 =fxvp
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.342. Koichi Suzuki <metal@FreeBSD.org>

 pub  1024D/AE562682 2004-05-23 SUZUKI Koichi <metal@FreeBSD.org>
      Key fingerprint = 92B9 A202 B5AB 8CB6 89FC  6DD1 5737 C702 AE56 2682
 sub  4096g/730E604B 2004-05-23

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBECwLW0RBACY/obrnveQb489t+RYYeX4nXBW31V2DeDxv7YwEy4lA1K1ExoX
 lcmeLh/uQT1hoH9woQW0BXIM5ilBkrf55DVfrjJ6usonwPVoBoiShdWy8jOJ1SAl
 l2jJsWK2jMrPSqu4NBZoqpaJQ4pofLsI7WFtqC1zV5CWFcl8vMbNrZZT+wCg1HCw
 NXUwCl5TYkrlTNCZfGh/QrED/RbVx2hctxSwy2FpG+xxKKpahtGrSfHXOotxFz3R
 nx8ohWaBEnUjuT0ahJrFsa7yxmPNp78+0a7BgaxIMLEe0z2bprcAEqz9xDgwS5qG
 rxL+so/837fuqMfMyOC9TNgQ4UzzFv7Q/MSP/vgxWZdjtSWZGyduFkFRzNmNLdRA
 wlGWA/9QuX7ob5EQBGsAMABhcMwLahjKuXNcFDfa3He8km4fnzxFL7ySePKioxZZ
 eVt9zK/QDVCYTtHXPiLGDQ+FphIKWZy0lv9fSuwH/VWE+QBTO9CUCuiFBRX20tPN
 WSHiZIlbZc81dStuq8EZp0HL+1iHhtftHWHH+Vy708g74cXYUbQhU1VaVUtJIEtv
 aWNoaSA8bWV0YWxARnJlZUJTRC5vcmc+iF4EExECAB4FAkCwLW0CGwMGCwkIBwMC
 AxUCAwMWAgECHgECF4AACgkQVzfHAq5WJoL1tgCgt1IVzmHVdA3C5YtLbxOqyo5p
 k/oAn04MSF3ffr2jxFjUvCoPIVu/dOGXuQQNBECwLi4QEACR+yJIOCf/CfQOp2yY
 Ny1QpBm4Rm+NnkJLaPX0ZKxxfa5cHQpqRQl0anbbihRYA3x+TlmD7zR9rTX/Hg+z
 nMLdVE9mGz57Mex+GZMUa5RfXBP6RgGsnDfXVAXBjqW1ZAZ4zFiO4vQx8SCwGK6r
 67etzvTM+iujcPK2lzQippkG8AmaBNHlhL+vhV+ILplP+OY5Z8YY617DZFLB58ir
 dxO43vL5P1vQjFCpD6gJ0nIyAdJO0aT3ALUtrtXoIn+6Cf7sh/qtcNbR6I4FIutx
 Le1ujb4nniziZ1iOTW1AkNxqwwD0eYQjxZrHEK0CTkEOBmUsR5iQp3Zghq46yVYv
 VdFmbdZJ2rjGZJqZDMqUtNqpaqK3rPLknJt30IzOuDWoZ5ttNf+XmfM+4mrEuHTV
 0xpAbW5AL1BpUskMBAcqM30/aEBarDi4cKoVkBNs3m3FM/KGFMjGZc781DGKLhyr
 aVNPj6Bmvk1z05f0o+UHhavLhz8becfDRA+9ue2mmtFdZXdGMz6LL8cPKRLegZlo
 4vbQ4hz/9UZGBUJVWJG8X85x6fhtrkRglTAGentGvZdOTmOPMODMoECtALPSJKXd
 P3iJlL2iaPaMUNJSI6449aku6aT6J77/OFTWcNLaYNtF1goNLTQiTBjKj+ESwfVs
 WznjFNx8+boTYkXj/HjZq9KtdwADBw/8DDW5LTYmzCvpZk8z0vG6lKjdPurn+97b
 epaw26XlbQvXnxAg40ho1Maki94vDzPHtxj9rLaAv1xtoShtzBfKXum2umFxA+eo
 WTnQwGaU+t3U6ndDU7PIqKgjl3x7ufaDT9pjR5BnfWmg59uQ0sJPCdMFpe9MIcxa
 dS5yU9fyPcadmSvfFPr+4vYe5IWFdijfTDc89eTAeR6eTKvhRyAwrJPOpjeytTfM
 yYwmflv2vZ5RHh1BmNfVVQ35PmeySgGKCbu674m4MLeNsyyoLtZrnhGt+UfB0oCr
 ImbmI/OIggehV7jJlGdNQtZXbHJpr2R4GiJSFe0V3Dh33jkw3xS6iroG8+n2SMCg
 E8iuOM1S/9rrjSVtmJi9ziaqdPtZuX2GHFBfDO9dXCF76Vc+c2JlDM0w7ZWyzwgw
 W7IQtnX/ld2TkBcWq5bCs7/G0YOGxwWF+5PGE7ajwNtnEDoFVHRdbiFQk0i0Ve+R
 /yKEpDsCGI0LenCekQiefNSsTVJ2KkF5u5WZew/hcmtlKzQ+Iwt7OxpriEeak/y5
 UJn/e2nX52BWQA8x1x2gOFwVoyeXTe12AxLpLKcIXZTi2IT2wK7Xs/rJtypwIOkv
 j60zDWQpu0tzKcPm8Bl7SYTZDD5NhoHD19io6IAw4VCaUsne+VQgI42KPap8XJnK
 fOCo/EDR+ymISQQYEQIACQUCQLAuLgIbDAAKCRBXN8cCrlYmgsupAJ4iTiPj5Eh8
 HfhJj3uNv7V2KbhIOQCfacugQ/nUetHWqzg9Pv5WEbCKjEQ=
 =xwme
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.343. Ryusuke SUZUKI <ryusuke@FreeBSD.org>

 pub   1024D/63D29724 2009-12-18
       Key fingerprint = B108 7109 2E62 BECB 0F78  FE65 1B9A D1BE 63D2 9724
 uid                  Ryusuke SUZUKI <ryusuke@FreeBSD.org>
 uid                  Ryusuke SUZUKI <ryusuke@jp.FreeBSD.org>
 sub   1024g/5E4DD044 2009-12-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEsqyesRBACDA3KsPNZg2Q88N9Vhp0kpoLW2Yp0xWbJ01tD2PPcGCq4nGE0W
 NgEvynvUwVJ4ODryLEIL3Po79fBIpkOhjraWdFH4LMcXjOequoERDWCMLOSBzP4R
 PKPqhSvOGw0H54357fcjzo3X2ze9HnfiOI5d94qaUpnPeE8JioJQcTEW9wCg9wKy
 KijAwG/TQBIHrS/bp6F/4GED/iCdSQ09Q6ZQF497zS1oNTgXDmD/qaAzW8F0bu/D
 rp9v5GVWeN1vfXHAtvug7/kIOO/eFZqU7IZRIf9bSerWXtaSV34QZSS81UZOr4u9
 YUGG1qk/A2a06GFzPCzB80c57G1b2c7i9Ktbw5cQ5o01eLcbqkdLmc3OcjIjnmCy
 /wnfA/9tlfS50UU7RFfwj199z7R6vxZ8HNoW0DwyNT0G/Sumj96o7+GXqU6NGZ3c
 X4g0qQbF1NY5h3cXkR9y3w3TP+guQFWtJEqyXxykYHZWAmUfNbaG7xiWdP0iGa6N
 pAWzMjpeHFXKCLmD4WzRx82TPvxSaw8W7H3PQwi/QIj1yBFot7QnUnl1c3VrZSBT
 VVpVS0kgPHJ5dXN1a2VAanAuRnJlZUJTRC5vcmc+iGIEExECACIFAksqyesCGwMG
 CwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEBua0b5j0pckoPcAoNDzMLDEsOm+
 GxbYMxiTpRNqR3/IAJ9TZ2g1dD8D99ipOUIADN8DyEZRBbQkUnl1c3VrZSBTVVpV
 S0kgPHJ5dXN1a2VARnJlZUJTRC5vcmc+iGIEExECACIFAksqzV4CGwMGCwkIBwMC
 BhUIAgkKCwQWAgMBAh4BAheAAAoJEBua0b5j0pckOEIAn1Q0VUudnFwmFG2/Gim1
 u+C8cmZpAJ41a06jrPg/BwDeHLHVhd5FzmXyqrkBDQRLKsnrEAQAg7+aWadgT2+8
 C6Hb2GzSs3/sJnLUWCGfmzBqKNQwyTMAlXEBD1w6MIeYURz7PuPgkOvB8v8b5+2Y
 JBU6i1289khWYSq1pn7XgX988+GsX//IfqCHl9i/RnuO4dVL9KXl3lGFvftpsm+A
 /l+4NkyWo5T/wpzyrmNfuDrsuDUf92cABRMD/0NsHSpAxZpt67PoIrnAXIByQU9g
 grORKLEHjYe6XpuVsz8XPARBjskYScU9VcPEtWIUWh6PXCjNk4aiKwE0jY7XX0pE
 DeiZwa2WG2eFlDqJ03aPgxTQouwEKu3zuo7Xnd/dlAThHK0wZdNWmV6ebYah8rrt
 TJ3PrsYQNptn8iogiEkEGBECAAkFAksqyesCGwwACgkQG5rRvmPSlyQyTACeNfIm
 DBCNKmYGktQUlB1U9kf7o2MAoK1PxWrRo9/d+uKirJNnzdYXTJk4
 =69IH
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.344. Gary W. Swearingen <garys@FreeBSD.org>

 pub   1024D/FAA48AD5 2005-08-22 [expires: 2007-08-22]
       Key fingerprint = 8292 CC3E 81B5 E54F E3DD  F987 FA52 E643 FAA4 8AD5
 uid                  Gary W. Swearingen <garys@freebsd.org>
 sub   2048g/E34C3CA0 2005-08-22 [expires: 2007-08-22]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEMJW1ERBACGUsHdqFuQjrrtjpvx2pQ7GpZYl+HS/jVPn+0MjMcZwRtk2T+g
 b0/EzS/0oeOqv1biX/aZN19T31JGdlSm8FumpTc9zPgh830omlJx8V3g8wi0ZHzl
 UjGa2MkmkaCEVeP5bX/NyRljP6fpnOy+5h4F0WcpkqwlXRuhOzM8UgpXlwCgjjPk
 0CLI2jSVsnqIKtMdunOfsd0D/RaALnZrVkGtQfDX6MDo1Ws+ADGj8rGtmdN5TIoo
 ivJvilG/5HSL2nsqOcIKWA+C4lZqzMIlo5iPSz3BijMc1Ni6LaQo4E4zvh7ID5fs
 fXsMhiE7H2KNSGTjmmL/8Weq8Zgpu9TBD8CHUZLD6BU4Wmm9I/R49A16T5Gbylgs
 fEwaA/0VYP+u8TEechtQKLuAfOwL2ruFE0YKmnXq2S7MixFvSNaRilB/t41I1YcZ
 mcWbRlIBezvchln5qRommEKfp/sWVcocR+AuSTcLT3683SkeJ+9205bFx9xXJnrE
 PBhqjMmRNNlmijcBFZHk+W7tCJQBbLGJkpLfqllfVkJ+rY/NVrQmR2FyeSBXLiBT
 d2VhcmluZ2VuIDxnYXJ5c0BmcmVlYnNkLm9yZz6IZgQTEQIAJgUCQwlbUQIbAwUJ
 A8JnAAYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEPpS5kP6pIrVGPkAn0i58Ikn
 S9M9e7cMI9Fis6lXDoAxAJ9eRxZEgPn3aQ4DZ2ObnuKbKSqcw7kCDQRDCVtWEAgA
 7jU7l7ssKXwc+/ynNfiLAm9nvCY4jMw+CK6hwhtuOmrgFH14jeEY8wRVBrOUkVi9
 Y13Z3qkTk5DD4iX9f25iK8PJELU5XJWStuX64hIEyqowRZ5KkvsdydHjQ1x2koS5
 oTW5kD2nWChnBKI7iWPgRnFnfthrXE83ZY1sV+/OBRZH1ZS5KVxOzClcoTiTE5Q0
 Q4Py1vlS/Bw95Nhejef7gSf6fN+iV2DQn8KDF81+MIj1jTWt5LDa80G+T5yGWeuz
 asAZVzBfPEHbWbVmRjT9Ajmump1D/0gUvxSr0fpnVfPtEFJ/MbLdcV1kyTtI9YLm
 EWnov/J31bGCDlhGjYfaLwADBwf/TBu+b48oClOPFJznnNGVVJUdD528hfVor4Wy
 3ph3KXSfaysOmG1xo+nQ3JpdzbC3nXgfVGM2wGvFEgq7ogBZ9YZNzwSP0vseJlwn
 oXNKvKKDdCyVJC6Xi0Pd6L4beJRTjxf0LPQUjYdQbwrk2RqHXZ/RUapYjlfOWS2l
 4ZqHiMoO7ZIAj/bdBKxySu8qVs3zmu59SE+ZQgxSXwxw2mF09XWOLgXsKTfhXlkl
 ZyKhjcSlVfjy4SXiXy2zFCh9+T0eiCeEzz5kS0QkA3npOooIFftI2q0IKbHOExSA
 YwOocuVEW7eLzeBfCoDa0SoapeXcjyF7KbiDwQ8xu9gEIUkpXYhPBBgRAgAPBQJD
 CVtWAhsMBQkDwmcAAAoJEPpS5kP6pIrV3wIAniAehy9Ttb00FbjcevJetKN5PWe9
 AJ9XhpsYKAyHxoZLFzGdR3EGBJNAbQ==
 =EQll
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.345. Yoshihiro Takahashi <nyan@FreeBSD.org>

 pub   4096R/6624859E 2012-11-18
       Key fingerprint = 1CA5 445E 7ABD BC21 AEC0  7B89 47D7 4EFF 6624 859E
 uid                  Yoshihiro TAKAHASHI <nyan@furiru.org>
 uid                  Yoshihiro TAKAHASHI <nyan@FreeBSD.org>
 uid                  Yoshihiro TAKAHASHI <nyan@jp.FreeBSD.org>
 sub   4096R/362726EA 2012-11-18

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 5016 characters]
 818CVCU0zxY=
 =tAoH
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.346. Sahil Tandon <sahil@FreeBSD.org>

 pub   2048R/C016D977 2010-04-08
       Key fingerprint = 6AD2 BA99 8E3A 8DA6 DFC1  53CF DBD0 6001 C016 D977
 uid                  Sahil Tandon <sahil@tandon.net>
 uid                  Sahil Tandon <sahil@FreeBSD.org>
 sub   2048R/F7776FBC 2010-04-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEu9UIUBCADIzpO4fbzj8VTUxcUiw0+H8JhZeU7ItggiSPf2KYJ3LHsfM1Ch
 BCewETgOM2LCAWkH+fwZkqdkl3NqIuE/9vv9gpoTkW7ezlnKNFhSqoFDjOnt+8fx
 KUo0Qb7l7HuctYBPx0FXwWNuYn2V97di1Ef3l5wRzQklwiJL3L9+Z+2AiZ3x62Gl
 H/88oeR8NeVSD5IvpcLQ9y8ksyZ9jw28YcnAKgUcOJwBX6/HOJoWM2QxwJ042dCp
 KG7nFE6SOsl0Ll8+ZxrHlPtPDUMSjuC7Fy1l3K2ruA4cpCf4K28N0kKwVDIIW0pn
 /V279skrDvkYkNnSbqSazshAifHWmEWVQFkTABEBAAG0IFNhaGlsIFRhbmRvbiA8
 c2FoaWxARnJlZUJTRC5vcmc+iQE2BBMBAgAgBQJLvVCFAhsDBgsJCAcDAgQVAggD
 BBYCAwECHgECF4AACgkQ29BgAcAW2XfhJQgAxhM07wUXZoxGt1+xNiLwdfmM/ipV
 l/vHLs4G0uu89Vej3mw3dXq74VGNdepWTp9F+CnmvF75QYyuT4rrYk90OVlTV+Nk
 PvTmxL5G8EzlO4Tb85ipGEdm/tKydP5qrjboCGijyrBBrZXarCT9YsJXYivyThE+
 CLQNSSF6ZC7k78izDA6J6gn91psVru9q39UL4TAop0+PRwQWwUc3P1LMw2sb+GpV
 er9BtfDD8uaEcO9atazPBp1tv0OTrlFB36DUtJGKXjAErlx8jxsQWsP0s+ypHohs
 0TEovHkx2g+XR5yr7djMqqV+ffJHADHyccBRhvQajwk8lKrBhAY/6pOxWbQfU2Fo
 aWwgVGFuZG9uIDxzYWhpbEB0YW5kb24ubmV0PokBNgQTAQIAIAUCS71SowIbAwYL
 CQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJENvQYAHAFtl3LnwIAJsO+cEo1+2JJekC
 lTvgOF2dUf46xwU9x7c5AbeVUSgBpSIctPQgO8ILs0u3VpN3CWx/tfAw2R+Z9s0c
 8MgIERuKAMwr3Vfua/KN8qwD77/GCDylbndnxgd1cTJhvUArYJCm+ChN7wAcFXt4
 Bs6jJ/gSEtdT+Yk34ygOq0aRRTl5uXaKoSzZ9KVcf/57dgmVSD3JxnzbXJF+6Hv5
 FRIUZI6L+pbv4vf3nv0lvoR9ykuA8FgfDc5TPGX2eXFDECcKtME6qfxkM0l2aGHI
 gcEQyUoiOQV299Kj4xw9i+mQTWf4S+qOyBsJYJGe8tbGJNm8c0iSoXG9hUz88Zak
 HpD8VI65AQ0ES71QhQEIANV6IEZPecqdnNEykNoCOitjHjvHAOJB3HZBBPaNKO6n
 TAMntmsgvpnC+mv0GYYzDpGtQ+nfpOQkHpaOrs9K7b5JA7MABnursTn91p/sveRb
 en0g7IWjnddwVyy8G51QEd/0Pa76yjsOmdQ0EE5gSarBCQwpmV0mBSgaJ2xUIu1F
 +wcd2I6g5ii30B5TNd60J81USoTTYCdcYtus5ZwPkBew1FD4CZNhstWka6iSKBpb
 falSp8ZAZvEuOEA+WSf4OYVC3nQb18ULnv1DfkKUukxRdQg+OSWkwIJbyRbixiGZ
 KMTBM2xiiay8sjXupmEzruk7Fj/xK9aPrksgf1LTq3kAEQEAAYkBHwQYAQIACQUC
 S71QhQIbDAAKCRDb0GABwBbZd0FYB/4jYDlkWSPEsUSWT3kxHoxKukBtPvpnin/p
 Zq/ISHN/tijiSZ9jMjn5/2AN/C8IGcUqKR7iOFd8J035ZA2qGPTTrIIwYQ62No5U
 1RjM/OZPOL4jy6MWyvq44VOW46obr5REsZ3Zhf9yLFIjGDSGqAvWuiy3EMve99Tu
 s9CDZBaZ2pXLiQC7Zg8LNatfdrSra/F+lXYKdFi2ddNRsTC2wR3fTnGJjL+fOM8r
 zUwkMqiqxG28TUDiyuFl0wyZIV8KJC8+wfSKLuySH337iSSzPWBKROiOtFfE2j4Q
 f7QcTMOmDn31HgY/JpcmnsChPtGs5W8Ao9Dp3d6tlzA6iQSZ6iRQ
 =jPKa
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.347. TAKATSU Tomonari <tota@FreeBSD.org>

 pub   1024D/67F58F29 2009-05-17
       Key fingerprint = 6940 B575 FC4A FA26 C094  279A 4B9B 6326 67F5 8F29
 uid                  TAKATSU Tomonari <tota@FreeBSD.org>
 sub   2048g/18B112CD 2009-05-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEoPodURBACCCL74hQbB00H/yUtv9No6sBynaWyH/blLogfrVbNL+86XIKDz
 yricgZ6/GDT4tbpaxs+o0wPdI0SrvvZuvvLfiV4ZxiCa8TNJF5/4GEzjKE89Pmtr
 DMK/i4RCzhRfs+PfzQdTRA7aQ77mds/tYGJYsqk3m1bWwOGggMti4TBk4wCg21tx
 RTopEa+HVDn1NTLgsAs9a/0D/3lvX6trmF07ENwCp4VGzBRTAZUAGgXziQ2zdjVD
 WcIWPO9PLxM1C1Crifbh5IOFoCsrUZeEsuLalzEVWZ2O4NqLRiRfuSD4ku6Rnd/k
 DBwkHiDy03JfGybBNEKUGvhXhhu53uij6ZXxNW9xR0KclDmrBxxEyj/Y/GYMte3b
 gV0SA/97szSEf8LmQmUD1sd+VHDBaJ9QUe5xNEJ9+8ZfCsVh0zamLvrAOLnZY0mU
 hPr61esTetdjDv1UAbn/OPTMfp4oY6/4Xa59APshxuK6urXaKExwWrvio4OYTHq5
 N0Bq73HwZV1beY+yP8wRRI4AzPoeHa+vIOhfIIJO++v5u9Hrp7QjVEFLQVRTVSBU
 b21vbmFyaSA8dG90YUBGcmVlQlNELm9yZz6IYAQTEQIAIAUCSg+h1QIbAwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJEEubYyZn9Y8pRqYAoIpC8dx4p/BaKVxueFll
 Jm/w5qD5AKCC5KSc0zMxM0Iq3FigA/tDjiyj9LkCDQRKD6HVEAgAqVPZwxV9bFbv
 PU20xAQ6HA8YxPp6QYUbb+r8AoRmqPNLoDqfNglhMimj5nPEFLvBgDHQaPQcqcja
 5Qiz7j3I8xFrBbkCrx8xp4XYAQB8An4iy8np4Ys/YjvDjittYUn8CywN4rVGIppz
 S8BDY9Ufjy6v9iFERXGEGcW3x5gFA3S1hGJZ308QhlWMw6OachMadUnAXcoO30fe
 q8eITtyJZN2MESq7G5TtaywDHz3Gg1K7m68bPeQaeAHwkQBwC/0xvDtJ4uyq/Yp6
 sQrlWJN50vaTnSAQ9q+b0tHQMVxQnxU0dVYgtE50jpPHApbc21Krc6H7a8VhNu9R
 JIanzAEUEwADBggAgJ1JY8XGrOVeYJ9F6S7F6pZKxyj/pYYBYA5dAIOm1df+cpvu
 Knen7UTOb6CgkZqGlX0BbYwYsfzr3B4oS0P5ScqE5gNVeWrCItZrZV6fuA1ZGnNn
 bvnEZ3xCZsb49CtfUcMLqNp1KGVGg1iVvh5YA7mtBmp6W12sq5YM4jx20ph+AHrs
 8/eIts+MMJ70QDI+GoXtwgS5IfFQK4x62K8W0RAmp77/qvRE4hrdsL55UYwD1zuY
 qzwfQVNaPNUUiVDEyL6K3K5GYfkZ5zPz8iJ6sWtsuLEyG4CSWLwkAtJj0Xuc71vN
 W/gkbM4ZpQgqQGQDZvN44Sj/prcJlnbyh26ajohJBBgRAgAJBQJKD6HVAhsMAAoJ
 EEubYyZn9Y8p4EkAoI+bYGMuNB+i74EdgubvW/fTinfPAKDGBmZorrcBfYrnictP
 T1jCoBbEow==
 =0Wta
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.348. Romain Tartiere <romain@FreeBSD.org>

 pub   3072R/5112336F 2010-04-09
       Key fingerprint = 8234 9A78 E7C0 B807 0B59  80FF BA4D 1D95 5112 336F
 uid                  Romain TartiA"re <romain@blogreen.org>
 uid                  Romain TartiA"re (FreeBSD) <romain@FreeBSD.org>
 sub   3072R/C1B2B656 2010-04-09
 sub   3072R/8F8125F4 2010-04-09

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 4290 characters]
 D0I9xnspW9gc/oMcZf1G8kE/+iG0SeMnRQzEMxb6R/Q7ZPsT5cc=
 =AUXU
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.349. Sylvio Cesar Teixeira <sylvio@FreeBSD.org>

 pub   2048R/AA7395A1 2009-10-28
       Key fingerprint = B319 6AAF 0016 4308 6D93  E652 3C5F 21A2 AA73 95A1
 uid                  Sylvio Cesar Teixeira (My key) <sylvio@FreeBSD.org>
 sub   2048R/F758F556 2009-10-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEroxHYBCAD8d4HA1tGibcHpjyOTeiQ7+yclqvB8bzWazJf1OeHwHcY+Rt46
 gVxADP5QPLhMaiw4nYNr+bSg+RDIOG3bmxqDZpmw38508NWd/W8XjgQSV/PhnjU0
 pfrvhXfmGG/f6C5D5D+IRJ5dffW65YuDXtsIPTOuBCwmq9NSRK0/w4VZBL1+ihDi
 oDhAWnkxfaFXN5luY98o1GVxQNpd/ZKjb+lsvAwsoXDSjn3R2bGZbA2LBIFh1Y2f
 KHa1vL4p5ZaNp0hnHyGW0mxC+SWse7zA3c500Erbm5d5I0HUgCEGNdE6tEryklFT
 zr4HfPxclml+QnlCDVZDSAf3+ExKfNLlSwjdABEBAAG0M1N5bHZpbyBDZXNhciBU
 ZWl4ZWlyYSAoTXkga2V5KSA8c3lsdmlvQEZyZWVCU0Qub3JnPokBOAQTAQIAIgUC
 SujEdgIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQPF8hoqpzlaFKYQgA
 mO/vudKdpx8jYDFmCOIE0OorvjqXNue+0VowONs2qSWiGwsvwh7YDUg8ZKEiBZHZ
 KV29T32y0JIQJ8tKloCF+XS3IktqWA0hlXqnN+Kmw3H0+MmzjgzCPhfTxG8jUUns
 r3qnYrFQDLzQXr64rUi0o6SQsxcsyb3m3VZX/NWXLyZm3RlCOfQzIRHWKGsP7Q5+
 sMcLA/obV+C2cEOlsrT1EQWw6pBdhoPr55ssNG9Gs1oZtPhepoKjTq4X3VRIkm5n
 LEcR5WUOe9qOJxxLWSWI2lWl7KAMuGt7KmOpbSYZNWi6Z4ASm2U8KhtFIDmQINzJ
 Th4Qkph0TDAr1mhKSaRVZbkBDQRK6MR2AQgApzi1h0Oy/HVxC82JSxsfcQKNgQbF
 6H9d3gkyb57koVVP52jBhcXx4vpce7oSpyWkm/uH6ZGZi5qkjSBliy1SdE+daymV
 8FEh9KQCMPvM3BArrDlbHUzpgRDwxJ5E25FfY/ggFF6/uzY0vLsAtLdyWowOh5ZM
 Dt0sKXsAMzBRaZ8VsWeBfxJJpecRLa6igK7w0+oehWQ7v9iC+XqBpfXR2S4pxTi5
 bshXeEfezqkut0wg9UBQdOZwMdzV3kw2Zis/qvi6jte19FrH3JVe3jhuoZCVKxec
 aTL2nawtQHqCN+7MhTog3ap+ZhghWr7NK3wlPWYmk0fDCRLW2bzh7e8OawARAQAB
 iQEfBBgBAgAJBQJK6MR2AhsMAAoJEDxfIaKqc5WhBt4H/ArRP3bzyv5ejeCZ25fr
 OCR7Z1vwdFFWvWqEAPO70x9XolGZMEhuF7OVjZpIXFgjDPBAoN5nxn4A3SJqMcXg
 zDsfqOJC4N2JHwWluX4D/CZ6caWOfI0p0sM7hYyXaoAEouknPO97IvermEvmiqnO
 gpcqUHbDL9DRKBnMyqDsSE3S83kEyuwD86x+UXJNCJk6awcUTWoETg6tVrpJ6Jma
 ccMPVsn4QucbRYyY2e9tIvJ1YbcqZH2munFGa4UXeY5+UemX88tg0rHHIYoN1B0d
 qMSWsm6YwNRBuyFC4f6RkK5x3FQExsTd36UaDkxMbimkyAf2y9uMmHf49+anaTUb
 QaI=
 =7/gk
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.350. Ion-Mihai Tetcu <itetcu@FreeBSD.org>

 pub   4096R/F0808380 2012-11-19 [expires: 2014-11-19]
       Key fingerprint = BAEC BFED 67D8 7529 5B53  C636 C922 F9F4 F080 8380
 uid                  Ion-Mihai "IOnut" Tetcu <itetcu@FreeBSD.org>
 sub   4096R/54B3FFA0 2012-11-19 [expires: 2014-11-19]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBFCqY88BEADC4PsjeErkHL2ZzVDqQ1pWaQ3GMcqt43lws6RvSlMG8tBAEyb/
 tJlZEoEmLpPirSPk0exFQtscONTtNKVnLzjt4UXJX/tKtKE51EID2TZ+4fPPZeUn
 8B76Pqm69m0XPQQpcuQ9aykQ1wTXljFk8FFjh7D0XAcqezo5o++NEcluqJ69FJyI
 zwfCvzG7IdO+y5TkIgfeauqeYw/53lMv1KCIOkYfxNMCPbTO4+grfKOOL4WLJeTu
 PDjjd3BpgEFmbgJAmyuxJsVNWSWmDlquS78qrdNXbMSudb6jBZWP4fgK7ycQnYbE
 Lp27KORrUwrwLdthz/5ZBTo6hGehs/d5aGor7F+12Lwl3Vp0eHsEhklP3cmel+20
 i3RrOsuc8ijrkbLT6V/A3urz0t/qV4ijs1lYMLlq++YMuG4AZ08QBWiWGAKn4ust
 3DD/XFfogYiON7Mm4JwuGrQi8TuJXDNjZ6J9bdZPIwD9rmad6XjlcObF3BgZz9sN
 w92CDxwnlK+Jvex74c3tau2xPjGTPFe+Ld56cs1TcYNp7utg0DFe9FrZ4Cx3FpLU
 YDLQLHRbf4pbNz5KTK7swInkzsDUc4ZwPEnpSYiK0cCb0yGjx6P4nslQjS4zEeN3
 OeKbYIiQx7saZvGjmbcQ7A+wh6Qxg1DAoZa4HQ2hMtEWRLDJ6U8rBGNeNwARAQAB
 tCxJb24tTWloYWkgIklPbnV0IiBUZXRjdSA8aXRldGN1QEZyZWVCU0Qub3JnPokC
 PgQTAQIAKAUCUKpjzwIbLwUJA8JnAAYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AA
 CgkQySL59PCAg4DWkBAAiuYdL+cwFcsfUPXvNjNTURh91AnCJiU7MPev9nu6nqyk
 YWowa171FTcWZAm2JPvKqGEpqZr2sJtGDA1jgrtKpapN2u3S4E5ANDcMQSDjAdJ6
 XzmWhGW/62pZNtvZAkvxwsWNcXeRxLcTFZmPXKkNBMkFx/Q2Ww/m9nR6qtMkrOaE
 llVd92wXOviCrMLtnRsPmMSrZACM/lVTC2L+c+QUfggyAG/KQfiuuttmFqGnqKr6
 Ym3qYVkVWMiPrbauC5aHV0I4RmpaEaYBkxx85U+2sV5pAQZjeDiyqjuMirlgVMsF
 NcQ9jjjbHSVTHpFbvo6eAYritts0mYKnrqrb0pBuC9C5b3FQIIGSy0z0dPXz3d0q
 VFIIP7DMOJLr/WWzjRqOobQ7nH3P2nvQiZc9TnkgFPG5hKMBWAqaM5gZS7HJC10S
 PUvTL2P3f2UZJ+9poHB9O/AewUZCt/gmXa6GoQEUCZgQLGCu7YhtIkKf8duDaIPw
 6myVMU8tiwz6dYo635rUBA21amjcMR3SF6LgipF9+8Ul9fISrHLjNan3Yz4PCgc7
 mIc71wW2LYGvAq+cw2NBkgkxDPFj97CUkXljjdy/zsbnR19mKDwM0MTiAGmFs3BV
 bkF1KTlnw/tGj2T7mntY6+hNei/kjOgbpX5h7VArR8bgLouD5ce3p/tVl1DJxCu5
 Ag0EUKpjzwEQAKefY+dwYoax3I9GT+xcd86k0rExqXFJGEDM74UeQ9C02aegdSsP
 qB89WNW5UWS0RifjfBb+9gyc9hVCrrZV2GEeACRJDitoUhMa/sM0R5n41w3poBqw
 sf6PBkzu0UGs0JURFDGsWNV32wdD5n0swqEplWpAsLkT1GNeIxI0h9rA+h7jInTK
 u6yvoUxKu2fTwEjQQuPi7iJ3tooaBgfGs3YDpOgxqiiK81X1gSJVSONFawtTglwI
 xV4cuaug3PeYj7/dKV4Z/PRzzUd/KsXWPn2P95sr/7lVimYT6wAZfmUuCE7qQPsZ
 HQgNaRBlJ6p5HjbP1B0aZ3hVvlkn9su0Vo3MinZkaPjwbRu90DKxEryYQcrjjWMz
 +pXFUfi0Qzd1E9/b6vT87cHAOh/WhLN5oBYQl2aZUuVTwtGtJpLSOeKXk8f7QRHC
 wx0OO81S/Q1hkHRgUSzuNdsbfSnk/Jum8GED9E9kGPOS/PFJq+Ut2/JGMvGhkEWx
 s3UWFXB3hP+hFutqeq1EESeOFKBvTirWaKeLxPZnDI2zUumCZQDtZLrZL0q9f92S
 3w/mJr2jWJhfiFnZDewNOyucOrAzEDEiniRWIlY++HLUwxPTSKQ9cyU+8IVUkpwV
 n3DhJ86h53YY6XKxhD+0fKLLuhcu5phVc1oBpy2p96AtIVtBZQjn5Uu5ABEBAAGJ
 BEQEGAECAA8FAlCqY88CGy4FCQPCZwACKQkQySL59PCAg4DBXSAEGQECAAYFAlCq
 Y88ACgkQ5YhbO1Sz/6BJMQ/+ID8KXvH1tK4Ut93AL6fFAXVAHmQugiebUKQ5gp62
 p3L1+tLSm4ixC9iDqWdCpjJ+FaHWKpMTs7AOheRsaudyOtkdiIcMLvauoONxbWId
 Nwr/5sMmI+tJCdqUfhxPtr7dK7joUSEoVhHptiDUhUg6XmGz5skI56AWUGHqvH7e
 1x/XtfA5cykUkmBY+ngKa73I3qAcNNKYcaoIojo9IsZJqKeuGsEwM5LvLLzjUhjP
 UgFHYMgUaG88zul+Mc6iNzGzEx/08XOdravQ094NPjVhUQz84crQ1K/xskpubddu
 qPNtfeTAwXNkDM83jACTZ+Rl73yUOuUaLMbMZIwYbIlOfacY+E5JBgFEtBIxQ0oL
 moyH57RpfOKISjVSTuksT7PloORmHhbPNfiCFtcljGMGKxCiqSpW5VVmLt7BR5F4
 QSLR0F2GkCh1dibra4W8wBBJh/UKIO37n3iDFmuGXd7bmJbr+wHtTSMUwmrYrz9+
 oRjwjWwLF2IOTykFv+MejfsDm7vsRalXRsapeK2GHMZuCXTY4BLTNLdCYHjSzoLV
 Pr75Ux/qmRUTXUNrdGFA0NsPSVWaP2Wq67w0cbSTQllMhiq64Cps9+WuFq4moyD4
 jK32oPMWcuBn47UBTsIu5oQine+AxZtrMxmryGpG7N8bo0whJ6hoUedktAgB6jVs
 kNbopQ//e2NgZj6EFuM4x4wmeORGP9i6wKHnIC0aHwAakUPBij5MKsE+euyXn/ha
 eJHSfTmqsdfzE5AIapxTKqnxLM4nQxq9n7ZXd6lTedVIXlpZX9lo1Q1b055hPfcQ
 JNFF/9VZsdlzkFzlGjk8eOwxV2gL8epXN88ZSdwaNQFqQJCP908cDLfPWWGcb4Ua
 Mu1rKXgs/IVkbLHVg6h7juBEwjFUYH32M2csxaKPhGqj5/WYG0kgKceaIN+KSFqM
 bax6Lk9jq2SwmFP4SY3TlsBwek5wfT207p/UyuZNYclmkqfTW6UwdT3w/r8zNASy
 nLjYUxb1hH7ief/i4OV8NYs/Jtlnp5phhIcmlTXrqENEP7QGucEpPD3Rm2OJI9Mu
 uFrTZ7sOE+olIUzc7GPDziFHg03YsznF/+Kdm+Wm4qgSw3zng6/Vpfs0h8POTMB+
 Z7I37sCWNGyN7D+AzHNioJY+YUphYV1blPl2APQzSDly9JgCpYuXzjWtSDSulFaC
 ShcRS2prskb+Q0koUOXm4QgoohWEgxlnfLFlwK3XGSRWVI4YPDUQetwTIk++vJL/
 U3lrm+pbtqjjHAtJuL3gQDcHeZ3TpEjAVgeRXcXcoIlENf7rpHYH8E0rB/WdJutb
 ag1HZ2aiS78/akwbfCJ/nsf3OL4r9kdUBc/XT0pF37wMyeK97NY=
 =o4Z4
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.351. Mikhail Teterin <mi@FreeBSD.org>

 pub  1024R/3FC71479 1995-09-08 Mikhail Teterin <mi@aldan.star89.galstar.com>
      Key fingerprint = 5F 15 EA 78 A5 40 6A 0F  14 D7 D9 EA 6E 2B DA A4

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQCNAzBPh/0AAAEEAKiF0rNVbbuQue8Mo+knlGKtZJXWkLOhmdzE+FPxTSRv3TOS
 OHOfFbEbTlcuplvYv1US6o4liAyyx6vGLGa7ZW0zLFAtTOJTfwW3GPmcMTieOIK3
 wwzJtjH+wi7VeXIQCU/mOcLC9A8QaLqhJ86e3m9FODSFMIluSoucrgI/xxR5AAUR
 tC1NaWtoYWlsIFRldGVyaW4gPG1pQGFsZGFuLnN0YXI4OS5nYWxzdGFyLmNvbT6J
 AJUDBRAwT4kMH2ldntvsCqUBAVAcA/4x53VCfOx5Bm+BtneQNEvHgV8aqWW0tM4r
 31KtsSjMwuHF3kl7PJtCfVk4OpRvog4u9V5G7gtUhUIOi/Qfuia2YHvvxIh3sx7Z
 Gg22e4FxNzNob3qV+YiPOr+Aa6EoYfHB45eHSLFXryCBS60a0CfZies+CSzcHBy9
 /Zu51dCtnQ==
 =f57V
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.352. Gordon Tetlow <gordon@FreeBSD.org>

 pub  1024D/357D65FB 2002-05-14 Gordon Tetlow <gordont@gnf.org>
      Key fingerprint = 34EF AD12 10AF 560E C3AE  CE55 46ED ADF4 357D 65FB
 uid                            Gordon Tetlow <gordon@FreeBSD.org>
 sub  1024g/243694AB 2002-05-14

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.7 (FreeBSD)

 mQGiBDzhleARBACRg1KdGeSzgkTXaRoBCqnjTjxoBZR8HzRn2hs1hS3CBJVGfAKQ
 NOCyKFQWWqYIlKDIEA38767uW3yyKNSnQQI3Ad17ifWp37M1B4wdgGGmEAiyE3Z5
 v63120MJgRhejyZph2d2CfAPiLPq2LXy6UIUipuYQl0BICZnL6rDm+QAwwCg164x
 uMUutYhSdB9/hBLPECwtXeED/iE9eyJVcXvdambHZfcvySg5e5+z7Y8FMWQuhcO0
 svBIrhU/gr7S9lkwudOj3LPIffwCUBNerVDGuDUhu7iR0YIRDX6aN+LCkHFXK9x5
 ScLHIj0HHpbQLJeCeGAZnPpuIluFjRSaklVERHvio9gR2cOlo+iXRku/SbzPEzA4
 BTvYBACCKxLHWNFdyiZLIMsSVn4pJtgUzIfSw/auBALMft03fvXD0cNOm2RfhJj2
 Yc5U4k6PBBtoTTAaKVQ+D7CRHBhlg+Ls/aJSk7Dj8XJHdv0w1AkGz/OAJlJIDj9M
 RRCPyfhTq4nlsbFOrJuTcq5XMxbdd+voohkhgaiz9Lk+KNCQX7QiR29yZG9uIFRl
 dGxvdyA8Z29yZG9uQEZyZWVCU0Qub3JnPohZBBMRAgAZBQI84ZXgBAsHAwIDFQID
 AxYCAQIeAQIXgAAKCRBG7a30NX1l+5DrAJ4gSRjBxPBeGI8qjBCAEFlKA8MOawCc
 Cm2cEju+gP+x2a/op28O02bg7NWIRgQTEQIABgUCPQegzwAKCRAgFTHVhF3+3ahu
 AJ0S9r2mcQEfQ21ZzacV6sTyJkXtoACfSxld9fOItvrLPh6C52JecXfraCiIRgQT
 EQIABgUCPQeutAAKCRBdjovp8jga1Je6AJ4hlXGQAixShrEIb5bwTPWNKpQEbQCg
 5XcnCDTpR7MIjRHd1Dg1Q9DgpvKIRgQSEQIABgUCPQeyOAAKCRAY9QOAJMJ4Apoj
 AJ9Dp5QAmcAR6LVlPdE0usEtw2bgwgCg7pXfhaGhtMDvjJOWIardnhtKQ2eIRgQS
 EQIABgUCPQeyVgAKCRAh+cW892qb9Se9AJ425mHg4dJf88ye13TsQkMAsSgC4QCg
 jbqcE3gINIe3HJLam4stKTGcknCInAQSAQEABgUCPQeyQgAKCRB8S2dtoA4VY0ow
 A/9gHpO8ZsTMx17LtBEL0+p2x6Uf7QzWJRilbgVr7/nCiMoj04rdbft27DnQg1pU
 xu/Lzv32kkDLsWBfwV4bR9efa6Q9N5o+/eJZUuNVypxK1QHCrJ/oG2yeTtvVyixR
 zXoFGAGiQ8xJplAJ8keY3NKjYHssFogU2GmYc4EIak9HDIicBBIBAQAGBQI9B7JL
 AAoJENbgof5PvirdwdkEAKM7iNtj5DGZ0yOLFgumLiRr2a9IwAHu+su08Pjb9lj7
 oUO/TlMIKf7Y8xG61ydotBL7t4eZFAWyT9ej+UBp9sBh2O5mY6CLeBLnXlka41mP
 JyiDjK1hhTf2ccrkwrlCSDx19R1RQrjsndaTcb4AA9yZQdoetslI2FNqvXfsvtyO
 iJwEEwEBAAYFAj0HuzwACgkQtoTxfMEKh015jgQAiZAHy0Ql+xB5zTRTkRziZSt7
 uqHwF9KALoUd0UByFJPcqqtv0sWNcYVPu/rAAQFveG9bqi9rDPmxIuuEGl3TAyx+
 ZKtXQ5re6E4G0AoJCKOpUAZaRQHak/iJZHgpl1Yyy2dB56kt9xz6Q+rCPS8O3t7e
 giQzGOF5csFv465gB52IRgQQEQIABgUCPQewBQAKCRC1UrBDdzkF1ujVAKCAJrrj
 PUzvNvCSuGMNmf9Dyua5AQCfTEJusbNkJKgu7CxHqyzTMvVlQtyIRgQSEQIABgUC
 PQggAwAKCRDYyjFxW6BSw/5SAJ972HfP7sNl9poX8YGE0T3vN8apBQCg+WiUgSJO
 ZeYEQMiZKLwAxoMbape0H0dvcmRvbiBUZXRsb3cgPGdvcmRvbnRAZ25mLm9yZz6I
 XAQTEQIAHAUCPOGhOAIbAwQLBwMCAxUCAwMWAgECHgECF4AACgkQRu2t9DV9ZftV
 aQCfYIv+czm8hMN3wjxF6sA5D43vrMQAoKRTxRmyjxDnRe4QoAZRRzogt6stiEYE
 ExECAAYFAj0HoNIACgkQIBUx1YRd/t2B0QCbBG60aRGEgrQzMkpodzJbU5Itys4A
 oIS56noACXYphdM25tdfKPS+QesfiEYEExECAAYFAj0HrrcACgkQXY6L6fI4GtTj
 FACgiAuFsZW43/A3A9EATgD8s0tEmoMAoLHpxQUAQkvYlHobnsU2jSEImhDZiEYE
 EhECAAYFAj0HsjsACgkQGPUDgCTCeALbewCgokMlypquzasL3SExbdbXS27xCwoA
 ni4XvyoNd3GBePs4fy4yUjKyOTJqiEYEEhECAAYFAj0HslkACgkQIfnFvPdqm/V0
 MwCeOBidsDe/z1EzCFK3LJPDkBvQCP4An0UYz4df9J69dxmP2Eqn8JJsdUdIiJwE
 EgEBAAYFAj0HskUACgkQfEtnbaAOFWNKxgP8CfH/yozXDafD//91tmXwS6x4MSTX
 stkfOGfOT6dLqla201Z+CDsHayQwfwVzJdcVYU+5Xe8dwb/sK8JjLiwb2ASnnhZx
 nZLeHZYAi3U0oNscxrPZJ7Qz93KFrNf/No8HrmryU9TUFzhSHKjHyNeBH+TJEOj6
 PRLftHPubEkO1q2InAQSAQEABgUCPQeyTgAKCRDW4KH+T74q3YoXA/wIaJzGfsFF
 d3nlZKK8hfZD89eUSR8swV/Oy6Ctl8qOSk4XWFxtjRRzNS9BM/TYjd7cJBUOQDQK
 u+wQFMztJdKdmntwoBTrdg7HGMGtKnR5Ppzv2XuGOKuoXy2y3yDgRsZc3iFEweZR
 Ao42FBFU1wtDCV3+B1X4Gj6CJDMT9R3ItYicBBMBAQAGBQI9B7s/AAoJELaE8XzB
 CodNgcgD/RYAFt6mLWS+CGSk2MdB4eA1McDDJY3d+On8c672z1BdQjPeYdd/zWHj
 aqeMoc1j/ctisGogN1HUwujoI+xo4puraFnFiYyJR9lKFK9uMBVw/eRvp+29QYa7
 RY/6U/OD7cfUo0BMBS9ZhZHNg6GMPSlJWd87pF8N3mFrwRK1dVOziEYEEBECAAYF
 Aj0HsAoACgkQtVKwQ3c5BdYl0QCZAQrSvVWxwmwJq4qS4m9FgdWTucoAn2Dea8HQ
 oOPvLRj9IRh0jdzOWk45iEYEEhECAAYFAj0IIAYACgkQ2MoxcVugUsNSiQCgktJN
 6aCAHnusQajUnJ9expOWxYEAn18BPBKs8vdWvTJjNwqI9BAe6WUduQENBDzhleEQ
 BACPsAZpNNdGXIlKMXJhYOeg/CuPG5dt0Ucaq9YhmmUJw8tmuLL5D839BC79qaSr
 B9UTcuKdi0Kmaiu0nTas3h6ThDu+nqLpiGAUqkSST8jhJXF7e/X/ggMLatkBIvNs
 nDf4owUFjzsm9nmb2GPPecWGsyArPkRGCmV+nfEYvhBo+wADBgP/QZ29lUpgOu4b
 nhgE2LP3641zQHjMqvYrZKnHbmHVYUjZwuV2YUvdFPI21OYWlsAYyid8OUTN9RKS
 +CcDcHZhS9SS5otQLG9P/aKVh/C9H2mnRU0GbSt8hf0HX+y6nuzPe3iwE9O5rbxe
 S0c/zhrPuz3ZK0Y3e0Zb+tdd4NpOVxuIRgQYEQIABgUCPOGV4QAKCRBG7a30NX1l
 +wSEAKCHPJh+3QRUcI1DG53fij95oTDMaQCfU2DJ5U/pKSfJFjFvN7XRpacDZZI=
 =1nJ4
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.353. Lars Thegler <lth@FreeBSD.org>

 pub  1024D/56B0CA08 2004-05-31 Lars Thegler <lth@FreeBSD.org>
      Key fingerprint = ABAE F98C EA78 1C8D 6FDD  CB27 1CA9 5A63 56B0 CA08
 uid                            Lars Thegler <lars@thegler.dk>
 sub  1024g/E8C58EF3 2004-05-31

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEC7Hq8RBACUBh7OsXzgLr6Hz1QigRoSr5nWAUdj7Z9wNIcoE9t6J61MIUtP
 qGL3x73LspmwBGu/aC9muJ5b4Ont+BBBkVkC3Cdl7pKSvT70/ZB7TKw9f9HA9S67
 jK/NnrgG4R9amixfd0KyycNpf3yvug2FV5VZBiUqvuqWipqXacOxsD8rAwCgksWW
 74+msARYAf+mTeR7/NCEH3MEAJFfoV3APPGGECWfwrDmQT1IiBhObbjsVKbo4z7w
 yHxK+3Qm9nCG/sVthRll96C+rtAJKf+FEN8nvIx/9Z1UQ3Y7zTMgzlbz83BhhPnZ
 lAZEZI+EfmWsltzmyjJHnsvShRvjEp/YQ+0tfZV5uAPy2yrICw/rvozhCmqTox5l
 zOgXA/9mfbgbJR8NS7IwzcVSH+YEW06lyxLHjEd31aIj6wgX7O9H7JdXOytTqbSR
 VXN+5GjJhEaw9GmAd6tsvusHMy+1GBgY7TFFUNYO+JqHn6FKGzfPiFyxDyvyrF01
 QL033peqiNVxTS5nvJzmKQCpftlU3S85R+K62Alv6xO70HyaALQeTGFycyBUaGVn
 bGVyIDxsYXJzQHRoZWdsZXIuZGs+iF4EExECAB4FAkC7Hq8CGwMGCwkIBwMCAxUC
 AwMWAgECHgECF4AACgkQHKlaY1awygj74QCggWeR8IRwgHIsxVv5zItpzdtnkSsA
 n31ytm6noxfetU5J/5NnR6bwV4WetB5MYXJzIFRoZWdsZXIgPGx0aEBGcmVlQlNE
 Lm9yZz6IXgQTEQIAHgUCQLsjTQIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRAc
 qVpjVrDKCPikAJ9a/Or2be00A9PeXyoo+b7VuLAzhgCcCX9kI2DduTtitld/mY93
 vZDnQPO5AQ0EQLseuBAEALDSStxYn/CidImaPKwDZoYVpXpHucmBZ/nK/rFwMNh/
 /RZD8ZdBF1PEDf3EA78qTxEk7PfSnoEWcxmcNfiMSALiTkehI4nWQH7j0ZSwqC/5
 Du4lP1v1PSeR35IkC58n8kur74olLMdoYxlpVOwh7jGR9W/3MSEjQ7NJP9AZ4yw/
 AAMFBACv3/ZxNdO78IPVJ1kQsfGUnwfpiw9syDqK+CMA6FyTCI2VUc6kY0Wc23Qv
 uoGv8ROk75pa2MJxEH/GQJNSZerJCSzLqdCyEW4tuxxJPQ7celSZ7PL5QutBzytL
 4rUQ5bUlYQBFlCx6aOuG2+zQqiFbm1RqX7RYdOf3LnlRmkaTDIhJBBgRAgAJBQJA
 ux64AhsMAAoJEBypWmNWsMoIibYAn1x8xlAkuQC2ZlUID9ORxSIgEMyjAJ99nQWi
 rCVB/qZMKoL16f9mHKvJ4g==
 =OYqV
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.354. Jase Thew <jase@FreeBSD.org>

 pub   3072R/3EEAF1EB 2012-05-30
       Key fingerprint = F5FB 959F CF1B 6550 054E  2819 A484 BCDB 3EEA F1EB
 uid                  Jase Thew (FreeBSD) <jase@FreeBSD.org>
 uid                  Jase Thew <freebsd@beardz.net>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGNBE/GKjMBDADNtl6FXubTcr6FSa3k9bFMekyXgJgqBAmx8UfSo2D5YyD/TJfT
 Utm4nTRrnR7hJ3Cgi//WsrkgB5I89fwUpmNtx2CzTikg1XLooFI8s17qa5/HeBPR
 r6/dblmAen31FfgzAIJrSjLVPSsxRMAxANZVcMc9fMD581/QLzmp7BVY2pddHaSo
 xm1nJMVPsKLfvc/YYnS3+7Ro1QzxGOMkyULClgzDYx0PziY1IAeXZDoH5llwF2Dg
 mBy1NnHH1Q2Y/NZSwJW7xmLQTZsz5haHbz95sAwnkJKRDgU5fisUvTAaWfhOwbNj
 AQlPWynB1n/pc0SP7ROJdRqmZmxU+tDvZ7rtW2P1XHa99BQI0ULDQhybiKiU3PuK
 yMd/t04hLT4OuSIaiJeCDHfmu0DP/ZbjMhq4YcqRy0UcR5r2kVOxmVYpz8vTvkSc
 J+guTn0QrFZS0GB9LJCy7iBgHTuXEz7cn+rGiHYVtx9vn1Yl+XTBNriaRC/IgFPf
 5YZ57u7J2Vcd1icAEQEAAbQeSmFzZSBUaGV3IDxmcmVlYnNkQGJlYXJkei5uZXQ+
 iQG4BBMBAgAiBQJPxiozAhsvBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRCk
 hLzbPurx601bC/90gKFw7ybh057xvR/p7bGvTVEm7yP/sgmQJ7EuCqVy7RTb+VZW
 4EUhLwJMOnblRLCzNnbVoRPLzDe97rYG6i6jBjTMgCXz9ebQadxMi3CzHnDEdUe0
 x+UgsiEAETtzj79i4JUFBzv6VLMZVqUq/lxaozwmXkvFcCHG9mBSo+sZ2AwOoOvE
 cs01vOnBjug9RwpLxzKb6ZdwbleX2skJma50QaZJ5I5uVgFurWHeP+1vOTi/smhO
 y2y5YHEHjM6sNFNxsov3EhmwLa95NBkiKJRpP9GT6vAE4MLe/5HLSFXGW1q4xKf/
 UKydopCpt2d8OPqx902I75JyxmMXoMMTWQ3HEgJ0qML+mqATHi7H6CJ4hnYyzwVj
 zF18ZH+Ruab8M4WvoPxvasps4aRhYiCuZs+zC4sMkt1gcWygC25ZAKhKJtz+jm6w
 SJ7cLOopTcYOanHzRr8JkH32EYtrbchD7aSUabk8KfPbXcaTNrtu7khNPXbfCNM6
 M3cB7HViCDSBuEu0Jkphc2UgVGhldyAoRnJlZUJTRCkgPGphc2VARnJlZUJTRC5v
 cmc+iQG4BBMBAgAiBQJPxipWAhsvBgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAK
 CRCkhLzbPurx6xmHC/41e1BInZuSDM5l8dJeUQHXOcFfTSyz4KAoggPpNdfnfZ+o
 cdqQf7IhPqACkRvnETqmhsW9QwJHLhqcvA5x5BAtlulbjgg6qYYARjRnzl/1UjB+
 lOsnijgXJQCeDoWueLhj3tf/yrUqG+19Jrx6EHIZUpwDeVIXj76MfWwhpB4izMbY
 TdtjI0Lriwvs2RGE8fRjEw5hcl85uHFVrYzSEJ9zevS/BalBy9u1VH4gaCrhsbg4
 mpe1nxZU3Wm59uWNKFihUJBYW7PMWYTAtLa8QFtDXUqkoGXGE/30D+cuuOnQMdrt
 lU3eXwCn6E7zBeM52JKelJgYzBRm7kdKix5t+HIwpbVtqePSaPoiCNhtEdWuTYYU
 83Bek8nhHo6caaLPz8VAHvB/5MmsPUJ/upbIWssc56aHWX/obBCUJnjcJpHl+6Bb
 BNT2L84IDX1qzvSjwj3z1/BwXtsPORbbNyf4eQKXjeWngIU8cAex+b391g4sJMBh
 Q7X/U+bJgrjizCVI2VM=
 =r3h8
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.355. David Thiel <lx@FreeBSD.org>

 pub   1024D/A887A9B4 2006-11-30 [expires: 2011-11-29]
       Key fingerprint = F08F 6A12 738F C9DF 51AC  8C62 1E30 7CBE A887 A9B4
 uid                  David Thiel <lx@FreeBSD.org>
 sub   2048g/B9BD92C5 2006-11-30 [expires: 2011-11-29]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEVueHgRBACBqHSbbyc8BoznmojkguHMrDQtqISv33b9tpIsNSHDgz4Wpoqs
 MRwMPZpStu/FwULPzRUkceoYFIkyRyBwyIqTAD3uq2nisPR23ffDKRe8Q44Y8ccz
 sAtc7zPz/XpoI+2tLVGBCZyk9UOuIK1HkrmEjJ8uG2/eqyuckjO39oA/3wCgorer
 I3uzG/mJG7V0hHaCEkhQVx8D/3/i9YwqVVf2kqfKEGUASik/PXDpoeHfC/v6GFik
 Ss47TSaiuMOCoxF92m9EcOSoYCHOmdkJ1l+AVAWCZvKHKDM6J20dRr1zNqvR37jf
 FlmbF5B/MhRcjaSvrOLnZsP1wlz5sRkdAOdHNN/J/mwqkaatkFwtf7XcFMheB2qi
 1XvRA/kBi8lvPw7/PGibDIZXBxUmWVHLCU0dtrwKjbHE1HIpMwgjbTFrvh0pjmXh
 +qjn9VTcduP50Lrd/J3bh6WSgdc16xT2zxSAg9G8nJctDSJVgOJiYFUfLBpPBeLS
 O5ZN3GHw3TyLnDV/NvaAfzp1GXaGUB4kEuIaiaxxNugT82R3OLQcRGF2aWQgVGhp
 ZWwgPGx4QEZyZWVCU0Qub3JnPohmBBMRAgAmBQJFbnh4AhsDBQkJZgGABgsJCAcD
 AgQVAggDBBYCAwECHgECF4AACgkQHjB8vqiHqbTvNQCghqU1WwfsIQgI4bQn94M7
 z3PY/ZYAnRPT7soJ0GrlKAMRplxFoRWH1C1TuQINBEVueIUQCAC2nNYNyuKG/uCP
 l6/GUoumFRE8tcbH1jW5yrFbi8ahcoi71iCQ6Ozdx+XM/qIu13/iEJmTOvoVyOFf
 0pn0vVjgJ6yWek2oZmqh9Loj0WX2bRvV2uemOfvNwqUvDLCvbdftHgQAHOff5Tij
 GJxEBzDylhkAlF7MlZbCejiIJ7Of9fMC066Yi5M1lg5wAX1gPG27PiXJLMjcLI1B
 BsaIEtJsInd+UWsgjUE4tq1xoFhCeDZZWHCAyc7XyI7cy9FFQIII7SWkZ8TkZwKO
 T4UYyIHKtRFtgrMTkcXAc/Eul0LEo2z2e4L/G+8vF7q9LicIyv3/BF62fgx3iCKe
 HkJRWueDAAMFB/4lX+vF95ESlWuZ6DH1orSDKMzWlaJfl8ImE8nCT+QN/3ZauO7Y
 4kQ11jy2Q+vURzltl5r1uMgAheBR//qDp4OTlqxqSyYFx49iysd3rjP0vnc8WGD9
 BpGobsbcgw9axW6z278IZzJ7aroYBaceOHkEM6nNboZ1aKCn7jYqxFyzNUuJqqEY
 0vxx82C2wHIPb+b9k5LCz+kMrq8fGDPERYYcFFKHMuKZ9oyide/8hQ83KadXbvJB
 /GAqx+prMs8axuAMoGgksMRV7Er+eRZNqYyeCr31j+Oh4qpUbe1q3UPzkoUg9OMI
 qJXvBn5S1M2B8epkggu4y6HDsbVXqgT+NCaWiE8EGBECAA8FAkVueIUCGwwFCQlm
 AYAACgkQHjB8vqiHqbS5dACfWGE7OYOJs3lJUh0fHYJEYGfcOKMAn3Spx9LXSIcR
 mVETDDKHRmZTSiZX
 =iAPM
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.356. Fabien Thomas <fabient@FreeBSD.org>

 pub   1024D/07745930 2009-03-16
       Key fingerprint = D8AC EFA2 2FBD 7788 9628  4E8D 3F35 3B88 0774 5930
 uid                  Fabien Thomas <fabient@FreeBSD.org>
 sub   2048g/BC173395 2009-03-16

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEm+vTYRBAC03EXAZTDbUh/ShE+8WHHaB98hrIyAlHsMBRpWdouqNVbvEWBQ
 08to2fDMF8zpWY7GB6U1w8bH274bWjIFk9KkK9fLbfoKnwQOWBEB1IFOei/G/4Ro
 xfufEQUOWGjAcVlZp+/crXEJQEljWe4OOjh2Seruxo86qWmm6Pp8LkmPvwCg5+t8
 iQL/1Ud2c8fyLAS+AARuAhsD/R6MSZtQSselAtbGB5S01reSKO4enb7yFdU7Pcbp
 iBAqgE0khMZqcQFeOWyAiTFTqyt4t076R1s0G9uBoTCI5/sDslVvyaglnGVrL/Ej
 6WEyBEHXFHOS+pf7Aofke0wHyQhl9YrN22cEFEKWNDMCu2T+K0mP1AVKtnbLqwVG
 clIuA/9+qeScAK7n1Nu33c4WTkbhxdpxqcQGuUti+vHLrSy+wpZgEP4e3A1AurRs
 JXUGTuqT0g8wxpCMEassWuoOphrNUz3Y3ckspvo3PLbht8iWhkAS+YjvTgBPu+at
 rxqS4vuog8z12Gl5C69oUihXozh0c+9WNQUahsy2RM4ldFu3qbQjRmFiaWVuIFRo
 b21hcyA8ZmFiaWVudEBGcmVlQlNELm9yZz6IYAQTEQIAIAUCSb69NgIbAwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJED81O4gHdFkwWz4An1Jps5d16oHpy7qh7jro
 87IPMczmAJ0f4rYdOnxuFuRDnBLwVbdb1gLQcbkCDQRJvr02EAgAlrdKSnI726B0
 hGobE1BE7jwjS+u0ozmeTh1JLZH1rKNJd/LszO7ubB6X0VGA5ustPYVb1eVoSn6L
 LkvbspsdvNitklU8Ys4FF0dI9+AvrT4u84f8AjKKSTMHoTu6vv07Vm0qEdt2ZTim
 YTwG0OKuRbwCDNaMNzshkncWxWNd/KgrP9NlfdVJ/3NxlEl/GUm6v4bw1CM3F+n8
 DanJa1jKPk0krg0bdZc90flknwaH1rQckFrxICLa/9MnV8HjZEiE/h6M4Ay3Okb8
 zQnYywHqklRfvi2nUm85AZ+fJ1X06QCJD+Idg+/Tgk2SZ3oG+yOBS5GASiYiY5Bu
 3fUtBVc3CwADBQf+NFw7Lw9mLYqd7E8VFr81U6JH4WU2sG7YEqbcZ95jqiaOby99
 jaSZ0FKPGvm2V3VpgvXchzf7noqNMWUXbQadg5U/iJnRRhdhnVUbMq/T/mx5u9RL
 jH8Bp3zF5hElGpa/rPQ0TJSI9lltUUHD4c59FbgEXqmG69sTNcXBeH+w1LBoqmyS
 VQvLsPKan6FKfFDzvvuOxdP2SFor36zu7ecEuDz+teETk5ixRiu5wpEq7geqgZfW
 rgO/2HN5OgHJCIGvQfttUwzrDLw+RHiy5wM2f+S8wSi1bka3ggE39KPODMHQR6z8
 zunYn+Xjw+jL3zrDu/FAa58nbaFRuuFEqG/V5YhJBBgRAgAJBQJJvr02AhsMAAoJ
 ED81O4gHdFkwb+AAoKtrw8aIkc31k+gGotiqv2Z+v6ZoAKDKsv5LDbNe2fncnihP
 0wGrqiKLdg==
 =HImo
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.357. Thierry Thomas <thierry@FreeBSD.org>

 pub   1024D/C71405A2 1997-10-11
       Key fingerprint = 3BB8 F358 C2F1 776C 65C9  AE51 73DE 698C C714 05A2
 uid                  Thierry Thomas <thierry@pompo.net>
 uid                  Thierry Thomas <tthomas@mail.dotcom.fr>
 uid                  Thierry Thomas (FreeBSD committer) <thierry@FreeBSD.org>
 sub   1024R/C5529925 2003-11-26
 sub   2048g/05CF3992 2008-02-05

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 55308 characters]
 oMybWISax+SEH2PZ7dgbNw9pgQub
 =oY1+
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.358. Andrew Thompson <thompsa@FreeBSD.org>

 pub   1024D/BC6B839B 2005-05-05
       Key fingerprint = DE74 3F49 B97C A170 C8F1  8423 CAB6 9D57 BC6B 839B
 uid                  Andrew Thompson <thompsa@freebsd.org>
 uid                  Andrew Thompson <andy@fud.org.nz>
 sub   2048g/92E370FB 2005-05-05

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEJ5esIRBACGrMoYYIu2yCvXUOUgySagPjKetJ5zKOCFDa/Gl65tFtCcc3YR
 IjSDCvKuxcuS/qPo87pNP1sHPT0gVhMr+zcTrj8rgLWfC+CTzV3FPTdIA7LhVwer
 +evZ1jSHo/MY+GHTYBiDj/GiDkk8zBk6Sppo0OdzqZ0O8IW6tvh9n7RNZwCgrPYX
 rzBYHlAZxmZfQTDhgi8rPPcD/jH740waoG4l564X9hfkHDbxe2mrwKrcxfUbNi0h
 yIOTyl3glTULTno/xG6zxh4qG/COxIWhjC3Nkwllq+VzWqzYFoPIV4E/nvPNrLLY
 5a4/19ANLLkrw2kiLxNKLPu+SwnAF6cLdnbpPrGZSGOg/DhquXulAs8foTxv0SVN
 F5dAA/9O9GFOk9IcZ6D77A7Unysoxoa3WwqNHikJTo+bHvENJJw6BM1e93keLXbo
 bljw02y2cBXMz+cwd0S3ysj2tEPvEWpUJCVbCk7bB565R1TBb8SJB08MQ7PuOzbh
 PCCc9nB2TditjUTuL1yTrOW4qki1fHMA8ySNuYBiw/iUOkHgbbQhQW5kcmV3IFRo
 b21wc29uIDxhbmR5QGZ1ZC5vcmcubno+iF4EExECAB4FAkJ5esICGwMGCwkIBwMC
 AxUCAwMWAgECHgECF4AACgkQyradV7xrg5vQjACfboFkm4m9zZmor2J1+T5IknZ2
 z2EAnjX7sCxeTxGAUp0gv1+ijFir8Ju4tCVBbmRyZXcgVGhvbXBzb24gPHRob21w
 c2FAZnJlZWJzZC5vcmc+iF4EExECAB4FAkKUyikCGwMGCwkIBwMCAxUCAwMWAgEC
 HgECF4AACgkQyradV7xrg5tJswCdHh+UXADhzk4yJKgLuJlLYsSCK4YAn26SPktp
 Q2fQpBC3mGRRUYVRowhZuQINBEJ5eu8QCADgBVHTfrvthg1lDFvuZVlSgZueFEuq
 dBn0tyJULht4MyHAYzY1fBkKtRPxp/c+sGKzd/nXZ+zqQIJRYtrAviGAi9CyHTiI
 URcpMACCvofuRoMJ8djl35UzioL8O+icL2aoSq1w0MBzzkwTDcmaiceWVIC/RZka
 U0/irf31HSzAxGYO1wXtZuYp6BrEwcRezDZQUkO/riGKT9+UUppnTFVBbyelvVjt
 D9iyeRnL3GEOH0IvXbPRo400EwOHs4ieOZhNO4xyzj2qexMcbFq2nUis/qctukth
 lynv0mYVstLgS+GQiX8+VsbmK1QkTfKTY2ufTQDPJTcAa7Kneb+luDYzAAMFB/wP
 UyXix1pw1+qSJS6m6T7m6wmPj93/BoB+sadJvmjdaGcE5yKtCLdQYHZyI8Pvl3aA
 uktn+k/IxqSwLgJCSHv9CQ0AwN+kuIPHyy+hsJk1w5C8Qd4q8sYWecyt+aycYz7X
 Op9EB2rpKgg5E+RHFsuyx/X2dI4/n9XsF0xTDXmvBYHLw1E22rliiS9WlJ1C8UHn
 gjVZ8nqd4bI9HcwQMadtjXj0EcyarnJnrqLkJopzmLSJfOtnQvXyaTzwfS7fyQYs
 lnj+k/jJFULvgolWLmmfx149+3ou9c6c9KItAE8kfl7dSaEwOo4oE9cKluzhFHeC
 ezponq9OPdSpXUwBXjJgiEkEGBECAAkFAkJ5eu8CGwwACgkQyradV7xrg5szjQCf
 WQNYMndCd/TFxFqNF8k6Nu45/lIAn3oxSJ0Gc09OwQB4oiL6kHscyL/z
 =SFfV
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.359. Florent Thoumie <flz@FreeBSD.org>

 pub   1024D/5147DCF4 2004-12-04
       Key fingerprint = D203 AF5F F31A 63E2 BFD5  742B 3311 246D 5147 DCF4
 uid                  Florent Thoumie (FreeBSD committer address) <flz@FreeBSD.org>
 uid                  Florent Thoumie (flz) <florent@thoumie.net>
 uid                  Florent Thoumie (flz) <flz@xbsd.org>
 uid                  [jpeg image of size 1796]
 sub   2048g/15D930B9 2004-12-04

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 4620 characters]
 YhEx5U7AKdGZ55po
 =hxwJ
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.360. Jilles Tjoelker <jilles@FreeBSD.org>

 pub   4096R/D5AE6220 2011-07-02
       Key fingerprint = 4AF5 F1CC BDD7 700B F005  79A4 A2C4 C4D4 D5AE 6220
 uid                  Jilles Tjoelker <jilles@stack.nl>
 uid                  Jilles Tjoelker <tjoelker@zonnet.nl>
 uid                  Jilles Tjoelker (FreeBSD) <jilles@FreeBSD.org>
 sub   4096R/14CB5775 2011-07-02

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 12474 characters]
 IEaIwNPRRixodeSn4jA5GEXWP2WjJIEbF0vY9v/rYK5YOeTFKC03OBA=
 =sGf8
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.361. Ganbold Tsagaankhuu <ganbold@FreeBSD.org>

 pub   1024D/78F6425E 2008-02-26 [expires: 2013-02-24]
       Key fingerprint = 9B8E DC41 D3F4 F7FC D8EA  417C D4F7 2AEF 78F6 425E
 uid                  Ganbold <ganbold@freebsd.org>
 sub   2048g/716FCBF9 2008-02-26 [expires: 2013-02-24]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEfEDpoRBACh+3G72OFXvEjpBhfsiLhudF39C+E4zZ47xuWC9oAV/8y4jJdD
 70TjTBYydonraDCxhx+GdjfCzaN3PYw5fOMTric9xi3g8s11oKtzHG5NfgHfMIMV
 R1+7D2uXzgl/10JeYIz8DriaUBdHSKOhge5eNyXy6l1z1dPvnkP+/sQ0QwCgnaaU
 gIVvEj7qRiemJG0WRtWPU5sEAII5NYtidbx5SKM7/JzRtRI/BG497VVrcNVKbEZF
 jH5WklnTTQ1v9TnQfP7iksTZ6Ik6k86/opOagqtCRZ/Pdm9ldU/dZNFoA2f/4iER
 Od4Hhnm4rQ/rSUwXl6aZfE/26iBmH4/KkfkOX/mnRHAhs4EttXl1Nt7ew1BYwIAu
 +1eFA/40VV0lL93ab5aqvZ0fX6MmbXWjZXQ4q7YscqKclvGJK/BL4C7GTHk5Sn38
 uv+b9l39YR5yuZt2mByWyNCBBu8nXQ/vSjQ2V6wzFizAVZv3b6k13aGj4/ZUZiV3
 Q1WuU6qHvafvl0BJJBw4ywOC5gSU9eR2roGQb37fvcwH7nd747QdR2FuYm9sZCA8
 Z2FuYm9sZEBmcmVlYnNkLm9yZz6IZgQTEQIAJgUCR8QOmgIbIwUJCWYBgAYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJENT3Ku949kJe/EAAoIFqc0wekId4QcEDk35R
 OBMT0mpPAJsE2LsdqX17BXJLuVfuQuxIR9RLP7kCDQRHxA6aEAgA4w40fvHBJOqJ
 1RtowjBEX8uDEOwH2LlnKK7S5P5Z0PRM4/p+a4/P7KKRYAVehaBPc56TW4eqIXWE
 sjGNoJd8SIS+M7LIhlgBe0E0qKO1PXq7Alr5QMSR9aSS3z8NPWdKHU6+bJRomM8h
 1v8l0dBfFdYsrP11FXoAtRhkRnxB5E+A3rMJ35Uz5WPs/omz422M6SNziVn9lTXT
 N0Xk/pg3KHIVjosIakfbV25ZbrX0XYWNvh3zEhGyvbV5A4QuEXg4HSjYd43l5p+z
 FreZCrQh7IN4Oj1SfIbWzsoIygn9IacXQW/iASvpVcqP3yozcL8oi3VNSZtWY4fg
 jZZTIEJ04wADBggAoha5dSArTS2Tq04ArO/Mew4ZSZyOYg8Zay2TURrx1y2BU6on
 F56WwV2/C1qPzCOGDeVnYiXKKHnc9bNIefzKTMsJdIihw9N1CfD9h8MZ23GbhKcg
 VbiRC6t1b2BR1C7H52rPs8mXtywSGiI9pjzl8bA+ARCsvWHKe8R8iwL+jw+IVF6R
 94xcbHtK9EKOD7U2bVhiRb/uQiY6df6+VjL9lLoJMSLSWXWMtk3KJoFt6peB/XVu
 NIvbdxcU+xpgqz/SBPUs3MIgt9dG29UBsez56l0hgDAU7lcR0EIpCeBA4MskhInp
 AEJ38BJ6zL5MNmOOXWki2+FT4PbLjndwqxP0Y4hPBBgRAgAPBQJHxA6aAhsMBQkJ
 ZgGAAAoJENT3Ku949kJeYScAnAxcM/ZxE+XdjWrIazFTBJITMR0LAKCdaevdwU2m
 HFVwUGCsG1R5u7ctUQ==
 =rUEt
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.362. Michael Tuexen <tuexen@FreeBSD.org>

 pub   1024D/04EEDABE 2009-06-08
       Key fingerprint = 493A CCB8 60E6 5510 A01D  360E 8497 B854 04EE DABE
 uid                  Michael Tuexen <tuexen@FreeBSD.org>
 sub   2048g/F653AA03 2009-06-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEos/K0RBACA1Ck3ZLIpeSiYRNYG8RXCxbvHFOsI56DCwbRm6VXwjbbH32wv
 FZTxIR+A6LQQLCLDEvfklgI06Ksi4uWfAoLRB/CoiX7crEZGvYDc4kYSVjumjORh
 OzDtUiechd17/gyo4j+u1PDtw/5XXpSaTIRJO3g/UobVpUPjl4dMz4Ks/wCg25PC
 MPQI2rqriwffFak4PZdJ/JED/RSqsLqjsBOpk0hrY22VQrDhCHrWsVopq5hcqElw
 W1iuLMBhGK/Lursari5M8pSmjJVeWMEQwDqfF64MctbbfmOfMaRRggX2meVdMq3c
 o7bAWWEfstFB5WlUkCg6TIQjLV/4QbATfX2YkIcwuxiwC+CMq2trAJ/X8A6VdaOY
 tkHaA/4iyk4gCbvCxB1bhDp2HiDZfAWm5OlkHefzWeMIY7O4k5+vpaS69ui1xgYO
 WhXKB6RpDXcJzvZdBQqrXqFXdfBgOwhbUj1uOgkBCMpC7EXT07sxzvrnaW/RR51f
 KTeplrRMX0tXMij7nFh/WzJFSfFK+0W6+yaRVzXa42ds+VARd7QjTWljaGFlbCBU
 dWV4ZW4gPHR1ZXhlbkBGcmVlQlNELm9yZz6IYAQTEQIAIAUCSiz8rQIbAwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJEISXuFQE7tq+FHAAn36ou5m91emjHT6ziIWw
 80iHtiyiAJ9RL3W/bShdgmG0U3UKDnPrSwebdLkCDQRKLPytEAgApnToBctsJKyI
 YBJp2wusPzd+8H1Ab0VCcL4pcKWzCIy7dTJSknLpJV7c6ts82+pZBKUMp1XHfnsT
 Q8YwoaIUOQjkBqqlkrxqkexidwj3VVZfUvHfXvU8Hw4JM862MtYa6ZHRoz+ZSVQi
 x8idPMFhs+zD9Pb0ct6YsINeKiEGTGnanm3XJIIeNg1bOlrTjDiWB6KnlMmmeZ/R
 o4vGdnO7wsP03VtJBUnPNaQ8luAs4SHBTmC+tXNhBYwn7Kh5PGR1TVH2ROpPOYTS
 StOktseR6iMJ//6mJEBOt3cypOx2d7hbXfy/LOijg5Ku4FkUUmJrM4yDMgN/2bPw
 RGw8KgOvFwAFEQgAlw5VA4FwTgo/2+pDtQxtp96WuvQxw1IL1fPPNwGO7b2TVlj5
 KTqvsqx5MP9jLCTPi93KKAFzwFfzXxOD+Isd6AxeuotlxLOUXeCdcpeyYHepURYT
 7bjYg0DaaoqZopm0L+8c+hvOLfPaJLWVbUCEy219SeCA3xtGvRtFY1JXIFk9sbgZ
 y23S592sG/5CAantKyI+SHzZim2mj4iRiI9HlGDLpGn6QAyz5HX6a+TXdHijg/xK
 3T0xfBLn/xh5tSlBdzKR7cXSmzbtP9HL5rewVgVAqqg/Mzc93nD+gY67bMwAeyHq
 u2OCE6YkLNJz9kSqsSygcMDI8vKoPU8cqDvyyohJBBgRAgAJBQJKLPytAhsMAAoJ
 EISXuFQE7tq+/EgAoLrfM3GP7IAcTezTbs+BjUQcoWHhAJ9sJmO1S8JcXD8f9G2J
 AOE2UIkbvg==
 =adk0
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.363. Andrew Turner <andrew@FreeBSD.org>

 pub   2048R/31B31614 2010-07-01
       Key fingerprint = 08AC 2C57 F14F FDD1 2232  B5CD AA16 EFB8 31B3 1614
 uid                  Andrew Turner <andrew@freebsd.org>
 uid                  Andrew Turner <andrew@fubar.geek.nz>
 sub   2048R/9ACBF138 2010-07-01

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEwtKAIBCADBws3xAl7jWnOOAlcH/7Vv72z8eZyzSs8VqriCGftQNju024OM
 SglSEJFaM9wo1EmPwBDRbnCE3d0wKXstEUGvrPRDFokqunngQWTM6B7X7CLtm+pG
 +qdZ6rA3UOKw+WxP6ELaedg12+Nzz7KEMq6DXIrGz0vQaMwq8KcIIyOkoFU2Nhlc
 cRmvONus+WYd6I/kFj/u5k/8ILU20VyCg7fiAkZHwXzGUisCcKhyUeuENZi4yC35
 n2YtBEls2myhM49KD6vTlFVBhykV7KjoZcZ/Z4RO9pkvaWf97fEtWz1SaD+QY3kh
 tv/x9H+IAggoFMlRIy11pkJPNHAbPD4vaoU5ABEBAAG0JEFuZHJldyBUdXJuZXIg
 PGFuZHJld0BmdWJhci5nZWVrLm56PokBOAQTAQIAIgUCTC0oAgIbAwYLCQgHAwIG
 FQgCCQoLBBYCAwECHgECF4AACgkQqhbvuDGzFhS3twf+L8P3sOEqPQM+3+n8Wno0
 fCRtkw2XnOlAOsQec+YkRMmaRkRnW1aZb916s/KDbnKY4tbNZcVDuKuUVM2vzZy2
 krzEDx6eszV/VaweNHuM9FB0udtbmtYAu4tunipNtPK08+WQjZoiWjeq4HJEd+YM
 I0djeIE+m7O46LVh4mWwQEgVeLftFiexEWR3prHwgZDSND+02St5Y3zJZh1Yaogy
 xL1Hoh9H4zjWkVY/9FwpLORCiTsrnDp5bOCBxizBRJOIl7XnhPNoXv8gOJAqiBh/
 yx/0Oe0z5tqYkh5HsHgynueB9aMkTpVDryqEq8ArtF2L9PYwynsR9akannnFe65C
 krQiQW5kcmV3IFR1cm5lciA8YW5kcmV3QGZyZWVic2Qub3JnPokBOAQTAQIAIgUC
 TEFGsQIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQqhbvuDGzFhTBJgf/
 TwNZaesYaHdZVhFRYoGd/+GxvbltvvbOpKILvdqzM90jL2i6ap1Tj0sFggBAkiCP
 GAzlqGqqwqMQToYho1Q6NMMqzHsBMG0qInzkfQFFejB4hbrlW3yebvy3oHZ2iXzA
 o6ufEsD0YUGRVrUUN4/pLKA9DOeTcAkVBhMd7d9ty6eN5AM1oPzB8giMyVHZXII6
 InxkF1ULBgYvtypkq1bj+iXRMEd3vP8O+6PqECSIayWubiGAR2sHfrLje7qZuIu3
 3yv1WutpgkU0TLc5aZFXvglc3yH9Hr8+Uj0qkE2kh/4VJLqQJgcRo9qolM6R1A+i
 J0UzjIrqw5rkzyzL2Yo3F7kBDQRMLSgCAQgAyfM2CUuc5W7fYL5CyUd+kHvaXoIQ
 ZsEF9q9IlZEmCQlDzJhI4kIwZjdQvB2Q70Axdyo1XAF60CzVEx3oJPyGSstYI94d
 7MVKD4I18hCi3/EI9NfTCiujU5K8HclF4lFZdEyCgKidN1rOvvkCu+pKDy4bB3wr
 Afrire6WAH/jFeOOowshfcN4o/T4RByCFJSBQWMGN599JQvVBQSzbSFUDwNCE3E/
 Ob3EgYwIsqLQVY3y1UkeZri1QOqLHA92IRK+fZDnnjwHv+MWaARKACCVDbCSM2X6
 utvmzbPu9OnxTKzq85RzOKi8tiZykUf3Sc8GFItg8Fytma80GadB3NThCwARAQAB
 iQEfBBgBAgAJBQJMLSgCAhsMAAoJEKoW77gxsxYUCsEH/Ah4NUVLoDCA5Kt9mC+h
 Xh6u6n09DNBw6vrdAmRQVxmb999tKyYbp4oYdpr03KXO/I+gzAiSoY2QwZ+NB6b1
 6cUDgWTPmMdwLHGAjmegnEYst1pGbhSHOrePrWucVtKrMS9u4pZ2DIZo5urBJU/D
 cAPFBjQI6lkw9pw8O35ziArQ4h8brmFE0Kj0VYvcl9oAtLTc/yOCQZARalhMarcU
 TNmzmJnfSeYFvP/CwzarAiBFIkcNGq4ffC2WtnEgfZJRUapFRPF/XVx61Eu2tPSn
 pMx/kLUoZNpzT1Polj1ZXtBnWCocQKEQJBKh7ZMuNHIICpiHVLHQV9T9ZR/5Aba7
 BuY=
 =WLSs
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.364. Hajimu UMEMOTO <ume@FreeBSD.org>

 pub   1024D/BF9071FE 2005-03-17
       Key fingerprint = 1F00 0B9E 2164 70FC 6DC5  BF5F 04E9 F086 BF90 71FE
 uid                  Hajimu UMEMOTO <ume@mahoroba.org>
 uid                  Hajimu UMEMOTO <ume@FreeBSD.org>
 uid                  Hajimu UMEMOTO <ume@jp.FreeBSD.org>
 sub   2048g/748DB3B0 2005-03-17

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEI5K/4RBAD0LiHx/Tl4UyaX8yFUGjX1+PvATTJloNZGXl+jagSUQxCOp6Hv
 emDinSPskld/viupoAxjRImlkP905Y0Q6iDMne4s5fM/75lpeG9ztKRSgDQrQLTL
 HhXPXKNMtDV91yDqFEkwptS+0MaTMY0KrlR29RtGnpjoa347TU2BzU6TcwCgw+SL
 YdOWeSGs/7LKdUIyYlrldjkEAMqIQwnDl14vZBe9EOCrjSA4gHv6g2IQP1TRCpBu
 +/Fpi2+xcj117xO++uqMMzoi3aWwsqarao0/VSJ7ZD81by1H56Hnsp1d0r67neJy
 PKsyh2JfSQww9cxVkQjuZAjZNN1SLzDeA6xtSZrcmim+f0GIxlz3JFS9za/scs8x
 mGqzBADRF2My4V5HEMeScREj2hoquRv/uG727Nw+jftwiE+7TB7+JUwwyakAStNv
 x4+YEFAVSpKxyWgOeMqOWYd9bOSwJk40t9y1Gk6TTgV2C6sYwGHMSNOWYZbhYX7c
 84cxm2PtQFIq7g4Q30IkfAhYFzEwKmPJ8eV1zO0uNIhE+SO9QbQgSGFqaW11IFVN
 RU1PVE8gPHVtZUBGcmVlQlNELm9yZz6IXgQTEQIAHgIbAwYLCQgHAwIDFQIDAxYC
 AQIeAQIXgAUCQjxiFQAKCRAE6fCGv5Bx/qe3AJ99w7Ipfxs4CF3/+eCf53HO3FuI
 +wCdF/xyvVjjNdAYXCMxCHtUF85bD++0IUhhamltdSBVTUVNT1RPIDx1bWVAbWFo
 b3JvYmEub3JnPohhBBMRAgAhAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheABQJCPGIY
 AhkBAAoJEATp8Ia/kHH+3c4An3RGo6JduyjPTZFh0eCBezNgzxdnAJsGRRE6ERs8
 nyORm56bvSgRTw9VKLQjSGFqaW11IFVNRU1PVE8gPHVtZUBqcC5GcmVlQlNELm9y
 Zz6IXgQTEQIAHgUCQjxgkwIbAwYLCQgHAwIDFQIDAxYCAQIeAQIXgAAKCRAE6fCG
 v5Bx/iTtAKC+8mS7jAYMz3QsCe4dJeIPaJcFGQCcDQITgNpJcUmBZ5u21Jotvp1X
 T/y5Ag0EQjksbhAIAP1+LeYSauTBi/ST3343W0lkqYr6HgZMNS7RtoCGFWcjfiYU
 99ybRgr0XwH5yJrn6JASp27f/ve5cwt/7ERLZ7flcfFi53AekeuRjFDkThLx2N4I
 s29ZQZsYubdOKHapnMflnFE3PQfkB7Og1MoFxkp0kOAEP/rOyuLMc9CbUaWczxWo
 FS8bmZDJ5ZNzAQ2vQFu5ExxomOENApy3ZCm/Z6MU5YJ2trsP3dkYStyG+1pT4NsU
 R4+TIbQfFzwZjowiC5w8rM4FIV4FMQ+3YvIEVkT+M/93hLGakh5tQENsitj7JsrC
 VA2mkomV4Hnjj94YCxUiPu59kHgiKGgXbdnceX8AAwUIALF64I+guwCaHbjoRPVg
 HWRuU2NzuKN93xii+xyIpImf+S30aTbFy0D6ZTQRSCs34oVNMSkUzySVcVn9DTG5
 +KVCHCOnGMH/Iv3dRWlHZ3HX6Gvr/cRyhDfWYDEec7KCDGT7Q87UbmTZ9cmOh+/h
 M4ND0NoYU6/EaaOqyRH4D8/LAeg0YsEpilClYWhlXT7VS7noOBf1JuB9Q0nOGycR
 DstkHWJf5om82lH5FzAuh9kEAduv8JdBdsMh3Zh4N80tCV7OyBQFWHV0UgjARSLY
 msEuelzzaFcfR2vIrmpYIElr6JzHGBiux0XK3Qk98kexGRdbrDFpaxbrsjs1/8m9
 MVOISQQYEQIACQUCQjksbgIbDAAKCRAE6fCGv5Bx/mRWAKCAQQ67iDvQq08n+bHa
 QkK3EDOmqACfZmJe9AepCkPAUkvp0ketnOPBXAE=
 =QZ8N
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.365. Stephan Uphoff <ups@FreeBSD.org>

 pub  2048R/D684B04A 2004-10-06 Stephan Uphoff <ups@freebsd.org>
      Key fingerprint = B5D2 04AE CA8F 7055 7474  3C85 F908 7F55 D684 B04A
 uid                            Stephan Uphoff <ups@tree.com>
 sub  2048R/A15F921B 2004-10-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQELBEFkBF4BCADC9kZGlvNJcktMfbT1e6sp40J8qNWM9B92GpCo84BzTyKxvIiV
 HGWMivKMS0BdiE7pPVJXtsYFjNDues6drUBOtsUNlsK38sdxPT9UDupHVIXSxERb
 pyyn6ELPEJmP+3UwYzNM6DCfPm4ZorcvkLDE7E5XfYGZxMveuNIu2qmOYeKaJKiK
 t579i3co2YX7PXvUdbd6nw4vTyU7tC5KCFxCzs9FkNz2j2FJlZCe4AQCjhsv4odz
 oyppj25QhG5rXavOOOBcORL0BqzXGRozZ37K7u9CuPebxj37LFzChZk1s2aH5kzM
 fw9QZdUhJr9fkIv3FIfTVUvL2zXlpzmzsQBrAAYptB1TdGVwaGFuIFVwaG9mZiA8
 dXBzQHRyZWUuY29tPokBNAQTAQIAHgUCQWQEXgIbAwYLCQgHAwIDFQIDAxYCAQIe
 AQIXgAAKCRD5CH9V1oSwSr76B/wPoFdE6nFJ63egXDUHNUONVVqyHOWjoowq1f+C
 G0IV+07RmChOSccyVBFn3NIjZ1E7YMQm37SUhvgqY0XNF3usNkxBdlHpG3ixQEq4
 53HvI9JNHU6BTHVtGjDFW9ZhBFaOYVbCKHM2N+jq/RmZ+liD6QUC09jRo34ytDOo
 wsmccQ2p+8cN8aMizhxseGUS0Vo0oKIzSE4rKGXalcarG5vnZ4stP+acMMAiTiCV
 lMVHDtnC6Ca9e2H4ePmUBL0sHnM3r2+0e+SAb20yvi2PICOQ8vSEcbMt28WZPBxc
 0qmFkemVS4qHgGmd8Pe2a/OvPQxgujJ+q0uPwPfIJ05+24yOtCBTdGVwaGFuIFVw
 aG9mZiA8dXBzQGZyZWVic2Qub3JnPokBNAQTAQIAHgUCQWQF2AIbAwYLCQgHAwID
 FQIDAxYCAQIeAQIXgAAKCRD5CH9V1oSwSlrjB/9Z6KcBwseAGY+v1TwtI9I4bZ+z
 Vb62nKcYgFL7tJ0djIhrpl7l+lLr+RTvCG3A/vbERIxeameaOIHjUm/22KKRJEfK
 DJ1PcAVs8ApB//1/X8ahH3GZvPvFzH+aYBxCHEw4g+UrkXFFgwmogviwP8QT6mh5
 xtO9/fwnoHtCa0jZtRaOCCcQjAc4Vng1tGrKVE/E59LwmwlDErnqoT9jlSONDdx+
 T5K5/dVwCiDdKJSm6lTBY+bj4Z1k3Qi0N+0XQtMviuZ8I+ew0H6DF7tBRxrlBLSc
 VGUwILAUfbcFWMxbaQxB1PJEaThi6lSFJ8Pd0uZHZKeNoHJ5fcLxSQhudhcMuQEM
 BEFkBO0BCADQJijowH7QvQPpo+DqAv38fi8DxgwqbwpUdiA2P1eo5awU9xVNs49f
 XKG+QMMJHx5S6Bu3anOTKWlqZKfbOlTvlnW5anKRSngcW6kdoce2yb7wK0ovjFFB
 yFTBe7QOR4G4wOttU2Fa6lVUOApC5pvuubs3nWW1ovB0IFYitPTG8lcBkgJCCOPf
 /auv8ZxLYnaA55lvOupmh5WJjA8sqcwZneTTA1ATERmCRO0Y3Qp/jAiPb+vlnA1A
 PdOpEpjbDHpjfjoBUGo3oKiNJuFZ+XMzlcBcPkcyY25cfgLqYKo7uoR9x/itirDS
 CmBnXiimERYkaiU79+epo2giTtvHMCgnAAkBAYkBHwQYAQIACQUCQWQE7QIbDAAK
 CRD5CH9V1oSwSrHcB/4xXBMPUVZukcE0+5ok1ZxMN+kwFP/DVOdmrteI7H7vQ//s
 iZ0Hdg3RC4P6wYSGBbmIA695B3OUuRnIe4Xt1YcOkmSrPGQDvxbCLXTyxx8Ftv4D
 UhqSu3DFUwlIiN/qWdSHSie3EPcMYEMS4HDHlZSaZgrKXhMHLVI2oWDz5fT00sf/
 PLMpJqhveCYKOEi7Zu4ot8bDcfDt69I1MAhKSoAkni12+/fykvZXrxyvhwrKi8v9
 lbionqqljQ3/+q6olZcXDsgwUf9mXYGs/tz2DDx2FYfZAyh4Fso7q2yGOfu3XAo1
 0nKYeR0L8piSpZBWMKD09A9vzTbSSLfdcACIItS5
 =93PR
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.366. Bryan Venteicher <bryanv@FreeBSD.org>

 pub   4096R/E97DB7DB 2012-11-05
       Key fingerprint = 0F8F 11EF F4D2 EDCA ECEA  CB16 744C BF25 E97D B7DB
 uid                  Bryan Venteicher (DITC) <bryanv@daemoninthecloset.org>
 uid                  Bryan Venteicher (FreeBSD) <bryanv@freebsd.org>
 sub   4096R/2EBC1A46 2012-11-05

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQINBFCXauUBEACj+NbRz1VJJmbIz6PO3fV3bTeCaAIcBjKWzsaKogvEpuFaVlPX
 eqwKqoRqqbxHxRKfs3Matco+e1EwiWVfna426PB2S5g0+0AuNKo7lq/XtpsSZXp4
 vCPUvZUwpCio6ZYqiu26lVzQ2iZqz4wlsBmsh6pYaP9tNKuf08gPYu80kaclov+a
 /o6uC5A+cNS5u4v2Z+nojMKAOZ3IP5TECKtNVTvmEBlRwGQWKg9tgCGo8g0YOU8s
 XG0hltfpFTe0JAeVWY6k+fI6CXXTfa8U6mBBb5hhmM6Aaxx9j9e5XLXV+VhQck+V
 vJMRKnekfqACauhNvRQQHZsDnduCwn++ohW1kwm8/a0UPPrG0WkJa++GymTmUQwP
 hJ1/HBD3GS9LuxSb7oBCzqOSfiYhYzq1Mh+LiR94pzMfsykJDA2d/PG5uOO7xvL3
 lEdPMB8k/g9YFkWpNUEmVLKPt5vkZwRt2GcMhbIiexxXfOg0A6UhQJy7BWV9bXu1
 DqCeOzdUP1MBF0d/PrdxiF1yjPEHe5s5pVlwoT1PKfTYhVmtiakJINe5M9r79/h5
 Nvd7R/289x1pNLm4CiKcT75mnmb+p0ftQB/QCpk7xngc8xf1uoCPszpFYjp+ktVQ
 XAV8AKjAwjknfhwxxCX7+ijPjYQXVUNVVrFfgZZeJqoBnDTHXsuMDCZcmQARAQAB
 tC9CcnlhbiBWZW50ZWljaGVyIChGcmVlQlNEKSA8YnJ5YW52QGZyZWVic2Qub3Jn
 PokCOAQTAQIAIgUCUJdq5QIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQ
 dEy/Jel9t9vFUA/+K8LrI1I9pbN7hUlFQwxj/T6b6sQR/2vneKkNq0q6uj2GxoVo
 Y+r09sAtKENKi1rQBVPMGeZyt+gSWm4yk5pudzsLglHub+7ArFvzo4PzOd+y3j6h
 0r8zUtPZLQxg4gG9K2M0hev+Wmvvksh+NRUyEvbEgRmD2vP/aurAzMl8mIxKi5jK
 cSraBTP7slbuz7GR95/BCFV29ET1fczYOGrLEYfC9ucvHTWh6VVrEIFqjhJTrsMQ
 6X6cfTBm5Mv0VVnm9g5x610X3OH7YdRS9qlDr73vWCoFSCzzjawwv4j56tJIMLM7
 at5ZGsmBYEms2Fl5SOTcb2s12c2qPFf2e0YDcJjQiiX//hgV9/Dw+JEKkkZ739Ut
 r6TTP+icDMCAS7owOW555oYIxDakOsi46xU4XQ9lXjYqmOM68NF5clEw2cfC6H2i
 /smHClty57Ra3+RD55YOaT11qy9jJ6z5w0SwHMxVKnmuLL+wLrO8xFvz8YGtwTJx
 ULUgkyMU/g1NEDoiWetkydmjWa87J34/F3qo+Znz8FpTSx3syGJPtjirC242P0Hv
 aFEpobg+IieYj/y+tcBDrK7DcFhy+ddlPRikC33obf/pMe7Tq7XUDeGsAwRMDrZ8
 5Nz77ShoTyNVbQrjvMZ3mWUL6aIqQQiXYb30YX65qSfkbjeWFV/UqVWXwPe0NkJy
 eWFuIFZlbnRlaWNoZXIgKERJVEMpIDxicnlhbnZAZGFlbW9uaW50aGVjbG9zZXQu
 b3JnPokCOAQTAQIAIgUCUJdwvQIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AA
 CgkQdEy/Jel9t9v81g/9EgilQhRDnX+jbfI7wvIx7M2i1QeOV+Zige7fZiHS3038
 jbl0o/FylG+UfZiGRS6dr56wg52apG0GZMYN8v15b+w34x1jroCMp/NAXJFAb6Ju
 6molIDL07B8yWPRV78LJ71eG3lAsTmsXo72WvsbObAKmRKT1bOJkCnu6HCc4rMt8
 Gc2DVAfWM88/pnYu4VhDrs5q8hp5iblojiOu7wgDEapTd8+5aTCq1LEZYRit+k2L
 nl2FAXfswp6s+RhXS/4mNO9Bqr9Rj6SGLjbjEXUpNDzwjjyjaL+FgNvi/31yANml
 4rWEORrdzcFGdvgwKgSP25Xn85iMrJAme68fB1/4tMzyZ5TNugNU4X1ieL7gNNgN
 c3a18N+d1pnmfAkAqs6qvnysLrMJu/2wKbOmu42uZX3fEdAWkR8r233QJIvAp59n
 qEm3zRXZEOUUP3Pt0VCGZXQ4ztYP33kCWRJ7f/pIGq/gOZC5GZ2VRqDSv1VePoAH
 D9RJSKkxIFq62AvtJoyM5ahC6YpTf8DrdSsRW6/s1QdwSFIvd88wrfcVp4mwHyWm
 hGHIdcr2N/sppKdjFM0RVGEBh5X6XrQnWXfYYC8aNnYms1FYz3c1o2aYshT+FkC+
 fJ5QyMQeB/4VcOd6g3+BcFhb5ZYW4W9//D7jrYfkVyHloF2s81wGIOqqVywjwLS5
 Ag0EUJdq5QEQAKAFUhykhpw7uQe61dbFxCK/ZVzikZEjtcRfRZFQt4kXvd2PhyDc
 t+DyT8i/ZDSnP0UblRsSwTt4Ja6Yg0KUMbo9EIuvC5n7PVVktGAsIKZC1PrtMm84
 Gw1bBCm53LEwnrjhiPxXb2l3vX58wRXPRichZACxv5LsaFWlYAjqub9mkTV/MbFD
 4AG5X51gkqXQovTaOl3s0D/kpou9wv9nY9R0rKTis5z0K+hDrbl+l2WqaacZZWK/
 sPb+EjnAFvfNH3Y4jkp5Si0olmv9aKhCDuUMslENPN5j74Heap0zXWxXPlmVLBki
 wBwBaGsSKB6blnI+eJw5xqd3ast6qMUkW9JopCKztO1yrD5lB8dkRLxl2SepL2Z3
 QrYW5DVSlqX1mQyGoJ02Q1Z1bLipjqNoePwkjpsv4AAP4rXkWOZ50Yhi+DjVDpOs
 AsHCBSBE2GK6evzE0VIsHU+hKNHkcHhBmj8BnIJkhEVLPYF+r8ghLIGemtmkmSS5
 QzyCfr5KS3rELO3H1ZprvCddamOqbeWkeixcaz04NTCLBswTNPtqCueo77uo49IS
 kU52PVXjdOOea4nLiH8coUsxb1D9uEDBLPTI5zBM3BK9Xwv5jLjNLCm5e5HZTnJq
 2MDkqjruNTMQ9A3IFNcGKeNXILm5qm+HRJPDRmWSt90mq2mxWVr1i9stABEBAAGJ
 Ah8EGAECAAkFAlCXauUCGwwACgkQdEy/Jel9t9t2mQ//Sw5dWgrWDMDlVX7tJLtR
 I16tBJEvELkjUTTJkBRFazE6qT5L6Bvx+rewTkcq31cUqT8eAfqkk+mvVz6+L8XD
 N5pyMeUBSlZMrNF1Wsfc8F5nxLi8BnNixdAOpP9KJhC7KLzQuNpycSJMdX9nAfDx
 QHfQ8CVuqmnkYB34R6rpmyHHgN0kYBdA5q6MJzzlVATwO8oON9nCca60rFCbPZAX
 f6ZLRcFn+CIkZaEEmsEFK43mCy4jmH7DsabKtjyJdeaLAxyED1IxnQ1YWKSd4LBC
 ooYj87aZ34df7VpxBZe8/q4prwm+gEjM9V0gf2F+CgEB7m8JXmqXZ2id7p84PE7k
 UZJOBMTL1UegkiPXLb1thuCaSJodOLrf6t2W95v8auBb7fUAOXWNbQ2EId1IHPT7
 FOw2Yo32VjFOa/QUjKc98XlZBU4+0TZz1hZmsUaVRhhULqEc359DRdmNUfEDWv+P
 bDGiRwejjybGpb2f3lqnne3+7b1jEcLCI8k9VTklhj1l3flMWa5l0ubz57X2W9JM
 LkwHPSTICFJmJOU9KtWo6ujC1Rx20e5y+T8SMF4A9oDb/SuNRi+k0jhrYGsT+mWx
 De/WZ2m39Eshkbdd5R2izcYLuLV+nEcbj35ZsK+wgXkQqnSZK8JrjCArQvJuiJUl
 hvaQWSxKvtCA3RdI3vmKyQc=
 =6YAA
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.367. Jacques Vidrine <nectar@FreeBSD.org>

 pub  2048R/33C1627B 2001-07-05 Jacques A. Vidrine <nectar@celabo.org>
      Key fingerprint = CB CE 7D A0 6E 01 DC 61  E5 91 0A BE 79 17 D3 82
 uid                            Jacques A. Vidrine <jvidrine@verio.net>
 uid                            Jacques A. Vidrine <n@nectar.com>
 uid                            Jacques A. Vidrine <jacques@vidrine.cc>
 uid                            Jacques A. Vidrine <nectar@FreeBSD.org>
 uid                            Jacques A. Vidrine <n@nectar.cc>

 pub  1024D/1606DB95 2001-07-05 Jacques A. Vidrine <nectar@celabo.org>
      Key fingerprint = 46BC EA5B F70A CC81 5332  0832 8C32 8CFF 1606 DB95
 uid                            Jacques A. Vidrine <jvidrine@verio.net>
 uid                            Jacques A. Vidrine <n@nectar.com>
 uid                            Jacques A. Vidrine <jacques@vidrine.cc>
 uid                            Jacques A. Vidrine <nectar@FreeBSD.org>
 uid                            Jacques A. Vidrine <n@nectar.cc>
 sub  2048g/57EDEA6F 2001-07-05

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.1 (FreeBSD)

[encoded data, 30690 characters]
 mYuoZPQc42S78wCggnIdM5gSdDdYXWr4UZZJfTfdDkk=
 =lY5L
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.368. Alberto Villa <avilla@FreeBSD.org>

 pub   1024R/44350A8B 2010-01-24
       Key fingerprint = F740 CE4E EDDD DA9B 4A1B  1445 DF18 82EA 4435 0A8B
 uid                  Alberto Villa <avilla@FreeBSD.org>
 sub   1024R/F7C8254C 2010-01-24

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mI0ES1vM6gEEAMBJJFEzIesoeff/XaJ5baSLJwdZ87H26x51KPodOiCK4pvhSOvA
 1Cl+/moYBVOqhqzfNw2pX+EPWJpwRHToqZMba0rxALNhRaQgQAVk29V3bqsQhwBS
 yfwQirouhXGNaUGbdYh4ay0ZoyY0FUtKsj4GxhpWdHlKrjsHAliHM6U3ABEBAAG0
 IkFsYmVydG8gVmlsbGEgPGF2aWxsYUBGcmVlQlNELm9yZz6IuAQTAQIAIgUCS1vM
 6gIbAwYLCQgHAwIGFQgCCQoLBBYCAwECHgECF4AACgkQ3xiC6kQ1CoucYwP+N72o
 Hafp9Oj0004/rsgDKSLSfru89cusN7G7FyBYICjFQXJfwRAr3Mqo+4JwMVHPbQ6z
 ReRiMKN362M3e2cA5GMhtYqDTq7FSJzsWBUyfMhJmKOcP5rtQlm7sIt+XFGvOxRx
 6HXoduhiDmqmDUrxVxBYQTU5qGqkOXsIA/lITJ+4jQRLW8zqAQQA2HR/E+7JRr4r
 6WkpHb5WVe8w6ipuOpVRh9KjLOeDtxlCCuZ61asE6dVTYxhLrxhmzXcz7WQLJb++
 89DaQj5bSAFy3BfujeO+HUik9qB9Dv+t6eNh8SlPByxObyNx+NNNP6k5xiyx0cMC
 AMfUJbbZ91SN4gh+21yf2VqlS5uAlWUAEQEAAYifBBgBAgAJBQJLW8zqAhsMAAoJ
 EN8YgupENQqLLXUD/3qVTKnHAvQqu7EcdV4SEMbXtxHauN6tushMAbTiSI1tCz+3
 2nThTiXvLp4mQfwdH8uTQL+n3Yf3xZATAXe6Y/7Q+TvUp/Em3/5QOzdTEHirQDDe
 Cpks3VK9i/ud2nOl/TD1sy/5ad2aBKE2sAYgtILxAsdnxh4Cn4oBYc8Obg0N
 =UkFd
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.369. Nicola Vitale <nivit@FreeBSD.org>

 pub   1024D/F11699E5 2006-12-05
       Key fingerprint = 2C17 C591 2C6D 82BD F3DB  F1BF 8FC9 6763 F116 99E5
 uid                  Nicola Vitale (Public key for nivit@FreeBSD.org) <nivit@FreeBSD.org>
 sub   2048g/4C90805D 2006-12-05

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEV1n44RBADfkt4OUwHA7c8DbobkvhyXCRHC6w0NDQER6Q/uAE68nvEgPcdO
 dAvGXUpNNWFXbKEnIc7ANCm0V7F2VDfwANAzePY1wBfVM8UQBLuSV2WIAfs1beLl
 MZzO7sth2oeMuF7l7WwM31qwgRLTOOzXs7zG+m2uh1c1nMTKG9wgQ4rz8wCgmT5i
 oJ25GpzaM0kgX3HQWP/MkFMEAK5GUSesXqHc37fEnO4WVvdB5afc4RTDJzvniXBm
 nXkHin6uAWw4HSJOEOLPv8MtRZuIxOfznukjBpHnz19R0fEvWdRKzmDoc3Yn0BW+
 FdszOxY9Nt+LtY3/ZdcbgAtWu662/t3SvgWULgCQ7bvi0Nu75Zn3nui4j2uU5fNf
 6v4KA/9x8FXQ18BPO7EuYe5ewQwVaGWKvzrMmz8NsiZuRs4oxWXL1x0nSCumetKA
 03UHxGAQli+vuMNDcDXg5zpaGN7hIqS1N1fR7XEouvkgTDTUPsjjQUdmQ98lnEBf
 URB5D+qDq8nq7H9R/4rOmxKdiA8xmBzadnolJ69Iz9nyJ4mvb7RETmljb2xhIFZp
 dGFsZSAoUHVibGljIGtleSBmb3Igbml2aXRARnJlZUJTRC5vcmcpIDxuaXZpdEBG
 cmVlQlNELm9yZz6IXwQTEQIAIAUCRXWfjgIbAwYLCQgHAwIEFQIIAwQWAgMBAh4B
 AheAAAoJEI/JZ2PxFpnlNbMAoJWh5Yg1lOayXo3b8seKn09ers2UAJQLxlE9lS9G
 qzU9FITOFNllI+duuQINBEV1n5MQCADqyPgr+kjhfCz/2N8y3FmWr4CSE0b1S7rH
 i7fy27u0QcNK3vN/l0Vbj6dsacfP9DC3+aGw3W8uY8LK8q72AIAwLh1aoYtJfzMs
 v1kqY4shMAANF55VgcAb7lyHpSymFraVZCai0nzNyccjJtSNQgC9s1BkXeUrRTS2
 su078DDYVgbXs1S14PkZOyrZ+0R4y4M6QKvD8Th46K+mZMaXdcn+wlIvOISFQppP
 1htkyCnHexg5L6PE/VsdobiCyZ2zNKd+d6GUillVuO2Qpkq1dlLTPtRgFMnpjhRi
 L0+a84b8rs6TE9g/ZLKNOmfmbGTTk3u4vQ7u6Mky6GCGO8W8WHW7AAMFCAC9NGWK
 RU0l0hfHY3kjLll9Ygcnt42nAj4ipmnzMp0jAPV2AgShnzDJLZ1KHmJcUfby4I6c
 HDKrI5lt6B8OD1hAWbHaAJ1Js1vfiwGDqisra5ZvkfJQMY1CDv1orXeM/ZnWzLSp
 +PqVXA30ei/NtngXFYlw+BJHnbB18eKw25jT6n72Ls0T9xZscwgseAmSKZsrb6M+
 N0tjZkkueWRbvrFum1i8Hf+VYhCgRkQFcTtEEo/Ulb6GRDXaFLPZzklfQMvjgWel
 yfWpv5Qg6knJFGbQyZrJ/jNBAi7aM8XAuNhhjC1oHVyNlIRM1V+1MybvoheREjMY
 qcdWjs5YCrg43SWAiEkEGBECAAkFAkV1n5MCGwwACgkQj8lnY/EWmeXXJQCfW3pc
 YuXRQYv5d2NC5AfgnvxmjnEAmgPFcYvU/gGprH9Hz/bvXp3KrT7M
 =NcNR
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.370. Ivan Voras <ivoras@FreeBSD.org>

 pub   1024D/569C05C8 2000-05-24
       Key fingerprint = AB9A A555 C47C B61D BF83  154C 95D9 C041 569C 05C8
 uid                  Ivan Voras <ivoras@fer.hr>
 uid                  Ivan Voras <ivan.voras@fer.hr>
 uid                  Ivan Voras <ivoras@geri.cc.fer.hr>
 uid                  [jpeg image of size 4567]
 uid                  Ivan Voras <ivoras@sharanet.org>
 uid                  Ivan Voras <ivoras@gmail.com>
 uid                  Ivan Voras <ivoras@yahoo.com>
 uid                  Ivan Voras <ivoras@freebsd.org>
 uid                  Ivan Voras <ivan.voras@zg.t-com.hr>
 sub   1536g/149FDD60 2000-05-24

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 10758 characters]
 jWbYGkipB8aIvX0Z47A04fwAoP1rlccIBooCweN9TLWOsypKDtIR
 =9LWk
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.371. Stefan Walter <stefan@FreeBSD.org>

 pub   3072R/12B9E0B3 2003-03-06
       Key fingerprint = 85D8 6A49 22C7 6CD9 B011  5D6A 5691 111B 12B9 E0B3
 uid                  Stefan Walter <stefan@freebsd.org>
 uid                  Stefan Walter <sw@gegenunendlich.de>
 sub   3072R/6D35457A 2003-03-06

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGLBD5nXBoBDAC8weeyNQOMLmXMQ9r5UyPNpdmEsZa8bYmU9RGQ02Yb4R/81ucL
 AIT1iZzot9feJq16YowWxl+BeSv2XQEjwKFB+KEz9p8HLG2Yj5XX3jO1wPHtwW4y
 /zO5BwFKhBeEu/69eTw2JY3Q0cR/iQL0QKht7sPwS9aBqbWyMjaLpGQdn///P0B/
 MxNZ7iXHpAQR6sKq2MUbiwWtpdlLEKLbUiPqvLGg7C88CkACqXc4NGJrWL4eXtgL
 JmMv05JLhdI6nQhVNo+9WwBvcyqvEAd6i0FBTazh0SfrvVH8zQJ91QwnbsMLKo21
 83GkH/p0zt19oilrt18C4IpW3mWBheTaffl4PBVH6lvcPIRkEPhZZ5tkyG67rwfR
 r/vEo+//99XAwxwzGaiVKRlW2r0mVqmCLAjQpEkvfT2JiJt1okGwzCaWnjYAqk1r
 EDuaCBKwxPpk3pyb8MelybP3awbR+FrkYJzZf6LqzihS6StyERJKW8QbIf/+71PF
 iVciJtQ8at8n0dMABim0JFN0ZWZhbiBXYWx0ZXIgPHN3QGdlZ2VudW5lbmRsaWNo
 LmRlPokBsgQTAQIAHAUCPmdcGgIbAwQLBwMCAxUCAwMWAgECHgECF4AACgkQVpER
 GxK54LPAQwwAjA8bv7DeyVbTEIq1yyd+RDCEGwSRQPFxUCQW0tWwJoN0p+lNioIO
 zIYy3+cqQ9rr71EMMEl650NcYibo3ECPFZrjkN9mie79gNa33hGfAaG+2A8LbkRa
 HUyfRpFPmWPZ7XaXQHr2vRc6w9EuW1KGEVEEYElLM7YQSXENAqi/dN4DWQU/UFD6
 wMrOLDfftVhnJaeL9z6wQLN3+lY/EvBf8vzKFr6D2T0isx61tpqydMA+/hOcZOw+
 9mMJqYGWBSCp9hARDmd8wnL5O+jgiMAC7aXUWEk5uiQVVhCPxj2PN31j2YFwzEhl
 2NLVOHuu0A4dFpXH7wIXT6cEIltRis3/ReE7VuTQ5oplAXl24/OPp2VZKYOf0LX9
 NL6Z2Ea5rjuIQdVmXWtyJ2jZnxWqfiXiIKZoCMXHkE2eN+D+dpGWpWYWX87T0vUp
 O4Wo/m3PBN6Mvey99nBgRfHWICzzVkKGBoSNSYjN0w6m5pU1F6t0W/WFI6Jq3CcU
 QcJGQ4RK1zbCtCJTdGVmYW4gV2FsdGVyIDxzdGVmYW5AZnJlZWJzZC5vcmc+iQG2
 BBMBAgAgBQJEXbEzAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQVpERGxK5
 4LO6sAwApkJmvdlJwP/cBDD49IjKbUwjYRq5psU4dG9srDet0eLoUQtlI2KjdmSR
 aXAX995xXxzaO5jMSKNPQYIoSU3Ne+TaG8/yz9Ckb9uBgPvA8kJvcr2cyIwierz8
 ztvLEUV8/TAJTLA71Xzo5GBoM6wVoRXjYxZX+6ro1GagP5RJbotamn9q5Au66Ixi
 J4r8xeTQAKduQKgLwZadD0b5VJr9mJ4IsUTGQYmcob9UaHorU7ja6Q7WDtZYVfqT
 8CJxBBntmzlniYJXFFlvDJgiCxTcIFR3hlCPpvZ4X6YZ7uWTiK+UWrdJkJtwHu/t
 qiE4EN5dn+wvRVNX4iBmRR130tswGHfzA+O8wFqlMnYhkkZt5l5sHrMalSyczyEO
 3XfZEpRAcxxGeFTrMloeDWMIPBDUsKJdQhHniJ9HmjIEvh4c5IXnkUYd+pLZVShx
 ggXDyUVNaWjhVvwGz853mkWsto9DAe1dib9cn6xwa+WIxhlWnt+bjDzv1KM1gVh/
 p5LxDPeXuQGLBD5nXIIBDACletuXpBWOf2+nP4h+uU4gNP63bRh0bBznGnTORDJg
 5vQRmO2KKt3GTAWGC5pgWqF7GULGB494uSMX7WvIfwSYhzgZ0k1DT33WyPgo7whl
 JGNVyyyk/STEqijZCdzbti3zaFartl3oRl8UxJXMOC+jmt6XTnVl0WLfUkVFUIsV
 shXdqVntMJkoB/iGfKsn7KvzT/tQ8pNe476uuOQvzOFcZlipzWvFmK8p37oIjeZp
 ngFAleClsotOVL2VoRAdAmT6P+OxHCzk0Zcz6vz/3NA+WBxDPy/nk26Sd6suU5jb
 sT5hD2IGVcjZ7PuErJkAkvVJU2CrWpH7mw0mFNM6LKwFEdPkjlbndUMqMAn4z0W6
 hraotI9RySLoYJBpABjD5H7wjhf8OWu1i2ZiQuIX9hpab/RTm0jGNViothyNV6Sl
 udihv2cSuCSwVdOC+v6MDKsvWwBQteMO6LG8e7OTSRCF8r+EDdfw/ly7mGJJrx1G
 kwuSCQn+sbCFRxMXZ6BYomcABimJAZ8EGAECAAkFAj5nXIICGwwACgkQVpERGxK5
 4LPiHwv+L+BP/SknUreGZHfnNR0tEafVQTmQdbULOIJ0herPJzoLb6pPEe0GvsWp
 qQH/26hQusFrUtazAc89hYDFr3nLgdq4xiXY024ecVY2bU93Yz5K6GoiWcNwTJh3
 4IcP6xr08j1v9LjgEHwFo4DkBKe02JjhAr1WcO0Gt74lJIDElIYuKZW81DT16Kly
 45EPHdfjlC2PyvrhXk9fphB2T59H4DEkzlHrRK8EPr4zIXefDb82FFjVS38nD8TX
 grJAG7Czq0/wCcKsnOvuhT0ICNJsSSz/QVboKCbN2upUvuWyTti6NRevaF6FDbYf
 TVsdukZSt8/UBNHwCInbeLuorIMkPwcVr8r6oLv/JhWOS34y2V9OA2Zlx69cYQrp
 ssmXJmwaIJQ0h6E1MQzTUD4y4VUaTvdgvEN4vC6t8NfC1AN0xErjCGrwuZebE7ph
 8fLm/wloEhZv5v+UF/J1kOcxyFSQN/A/usPWgmUmmpghiRM4+Qk9nNbzoKRyfP0o
 Sjk9E6QR
 =iXXA
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.372. CURy.-c- <kaiw@FreeBSD.org>

 pub   1024D/AEB910EB 2006-09-27
       Key fingerprint = 3534 10A3 F143 B760 EF3E  BEDF 8509 6A06 AEB9 10EB
 uid                  Kai Wang <kaiw@FreeBSD.org>
 uid                  Kai Wang <kaiw@student.chalmers.se>
 uid                  Kai Wang <kaiwang27@gmail.com>
 uid                  Kai Wang <kaiw27@gmail.com>
 sub   2048g/1D5AA4DD 2006-09-27

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEUZ6yURBAD9qQ4Pz+LEm54dEtrDII566La8mVjMpZfp/xcPSY4Jsj9Rin4o
 XiJ4cevwTiAr7KBGbO4uJ/hRwOQMlql8vzwO+Bc66zLxwQfGpLniTvdEnsRmiwXn
 MOlc6Kd1SwxOk4rV/B6p1iJLZ6sXQPx9IlDskyJ0OhIYKBaYx4sjN4W3wwCg5QB7
 QSrzEldBYnrxVFLHfmQO6ikD/3sW06q+gAdSFwFCFEZmE0kaCVzQUrTwnyKWlRPx
 Fvk0PftHhbofybxiv3OFp/zHZMHRlcVqcYf7WRLww+QXRgFh6x5kkOoAFMVJzhYH
 xKcXSnqPph6M4H1GvRVo4G1FkdqEZ5z2hRwiryugSfuzRRHil4ewpZQeB4am+Llu
 H3UeA/wO4eqG62W13pRephwYO0ramQai+WV34z+DUGoKY2EMpsbE6+J85aiySvor
 BTfWq1Lh5Mg3RYGWLmLay+GDQE2YIc1EUrCgHlUpB+vB+3pqPq+5ssOixktylJna
 R40BAqOP/gO/sSBnCZpI9nNqtKDpONfS8xwDArEKaoqxxphD2LQjS2FpIFdhbmcg
 PGthaXdAc3R1ZGVudC5jaGFsbWVycy5zZT6IYAQTEQIAIAUCRgD96wIbAwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJEIUJagauuRDrMosAoIPJziIJtz3GBALxa4SG
 nIUGNliZAKC8yMp144zGxaumG1n4HZLNdaMwVLQeS2FpIFdhbmcgPGthaXdhbmcy
 N0BnbWFpbC5jb20+iGAEExECACAFAkUZ6yUCGwMGCwkIBwMCBBUCCAMEFgIDAQIe
 AQIXgAAKCRCFCWoGrrkQ69oVAJ9gWVClx+v3Hhvw2AjOyFaDT4hpnwCeP2ppw3M2
 nNkuXRtTI3uY+jwCSmm0G0thaSBXYW5nIDxrYWl3MjdAZ21haWwuY29tPohgBBMR
 AgAgBQJGAP2+AhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQhQlqBq65EOtj
 DQCfZOhljB+TJQncoZWMf/CvbT5I/ZYAnimgyJtouIZGXSTqU172qsr721aTtBtL
 YWkgV2FuZyA8a2Fpd0BGcmVlQlNELm9yZz6IYAQTEQIAIAUCRvwuFAIbAwYLCQgH
 AwIEFQIIAwQWAgMBAh4BAheAAAoJEIUJagauuRDr8iYAn0PbQX8TzGfG4VJkI/W1
 9Y2lQruoAJ4jtv0WxAV5CxIbBccVErg9rEdBdLkCDQRFGeswEAgA3/ArJRAwAXv5
 AOSioc12EGWSX9bpYWfcODoJL5ggaBLQKE8SiA+evSXgvfW9AD8S9T5ltLSAYXUb
 pbIWw/Nnp7w9+hC81fQI7mHoDe7oSsJa1mnyzibnqRczxy3V23cjqPLeZiRr3AkD
 mhBkONQron7mk23x1lTsHCgFmxBZWxNdnkIprmN37YkiUB0ky3/x3s7BVdat3hqQ
 ot3OF3i/6ugqW3qH8+Z3uEpWZr2yx5KwEJbUQNvgQqONlZsMDCp03jJuPIgnR/kA
 iRFIUmGLocgOqfL3JL+l7MflVQFFlzZNQqKK+WK2kXOc/C31AsVY0YJ4CsjTQyBa
 775LqpnTtwADBQf/WOJ8AztEUxh75zndmMV6tsUhq8K+cfaWR0e96zOP0eiO5IRW
 Z4muIXIBC7FxgyR628XAPm3a/IbMpD0Usure0MIQkmaza5ktGXG03KCpQYYhveJr
 3I69jJHUM7Vvrcl+a9wY3Ni5UgIfmWQzdpsVW707/SjZDcD9e3MWhASOThKb1wIM
 II7zgKICwGBr4VSwNVdikdHJ2wNhziuwJQHFxQs8rsXTLzHeJcWJfpZ1bi1P4Csw
 lsWosIFeKESAHoPsbpHHcS46cd6CXbOTLkonsUDqW5DZoN959MI8txkh54heZdXv
 al72Ksb969EL5ef//lDo/ex8aaVYaYwiI0H3VYhJBBgRAgAJBQJFGeswAhsMAAoJ
 EIUJagauuRDrkbkAoIe8dlhn35cPrbpcy4AtUGFlR0HTAJ96MT6WOnFqjfJJxo97
 Hps0V71KXA==
 =v7/U
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.373. Adam Weinberger <adamw@FreeBSD.org>

 pub   2048D/C57CF3A8 2012-11-15
       Key fingerprint = CCD9 F28A BD1D 50A1 8D08  18A7 F48B B195 C57C F3A8
 uid                  Adam Weinberger (FreeBSD) <adamw@FreeBSD.org>
 uid                  Adam Weinberger (adamw.org) <adamw@adamw.org>
 sub   2048g/9C6D0E30 2012-11-15

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQMuBFCkUjkRCACqWld1dYoNJjLlFZW1xjt524wQNaeDzl3GdNX81kkGUzsyseYg
 mmtlLXRSd2OqNHsTDwSqD9AmNErnn7tsOQL7bbUTxMdO3EOptiNwE9Xj9WKTuTSE
 Vy+jXusZAcBsg3TO4jccawanbbjOLUzi5X79J491/sr7dcTsJXcvkmAJWSeD7ho+
 U8HKFlXfU8qqWi2tkCVYJJlLUFBzuN3V6i4x0odTxDMKYUQ4dFx/96cwTbSHF92V
 3/jqeZMTglv8gKFHpK69M+uXN7/luRvj7mJ2e+kPFrBlC5dt13y2Q9PA328dqHBT
 dJMYS2oA5tSoTKWLLPIJYKGmEiEo8Qz+EQ4nAQCyuaILVdoSQLxJfU9hjkv3e4Ik
 9NjWOtUz3YdzLyRg8Qf+KjZj5e1k2MHnk0UJKLwCaeXaRfVpA9KpcJk/uUek6VSs
 aYWp92IHshvaDVyb8DfpSAbgtu+jvafbXDy87Wwp1Da+O9GV1pHqhNNLA4lrgDjF
 JkScn7M24x+y8dRbXy4gMe3/j+qdtDrhYoUicoQYHW6S/UrJg2p3QrN5V9aZj8Dj
 xY4xbURtzve9sSz5oeDjnQsJaDgLxX6UOn6JUMgV7pCCgfknw5nfGZBdzsOPz1da
 v9Gwh4QvMVx6O0JNfrkYI45xJ8AAWTRAlycTFifPmt+9niWmYFUAlKXtRbW+FPym
 cTQIsK3t0vxrOaBH1ml4uMTbrET8eJlLflfr3cJSkAf+NQ5JQe6vlr4+9AOTf8Q+
 h7KktDsscdCMYjjQ4aoCDuVfZQHXABeicgB1s9Cklha/QNy4VG43dkwIL8FWwGyc
 ueqnu9tlxY16sT/P6vk9/yTsRMVcKEBAKEtXQuTq04WD4Id1gkzbBD0wzwCbEo/F
 CjI/SxWMH/j0lVixcJYIpKgGj633rFOtUSoLsOWeJzNOIhcHIdz/qwlby14+Vd6u
 uzt3cDQ9SEd3G9DZQYIW2//ZkUnvxD3qK+sJIjJmL+ZU9eUXD8vvE79tDAOtknLw
 BbdLzwmJtNfP3v5DIWSmBYZfRTNRE7/W3Hn5cNe/DLO7hSQ5brWDmjMfXq9ovsRX
 j7QtQWRhbSBXZWluYmVyZ2VyIChhZGFtdy5vcmcpIDxhZGFtd0BhZGFtdy5vcmc+
 iHoEExEIACIFAlCkUjkCGwMGCwkIBwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEPSL
 sZXFfPOoM24A/ielXNpbFz2W4YDt5b6tR7cDzGuDHSQeqVlXpJ9zhLc5AP98s/06
 OkAXtmf98/FLU3NdouT7fIIm0Op19zfwEPxat7QtQWRhbSBXZWluYmVyZ2VyIChG
 cmVlQlNEKSA8YWRhbXdARnJlZUJTRC5vcmc+iHoEExEIACIFAlCkUysCGwMGCwkI
 BwMCBhUIAgkKCwQWAgMBAh4BAheAAAoJEPSLsZXFfPOoo94BAJkElhY9dt+9lk4Q
 AE5EjqxRvO1y8DFFb02qzphA68bVAQCAAeMt3ywQ9xPqPEal2IafGv4zF9CIJjFM
 r0HQMuD+HbkCDQRQpFI5EAgA+tX4pvhc37IfSmy4fYdxjbjB/B0s8me2nZn1kMHj
 +uJmUB+7WZUVrCXZwmsn4byN6i1jThQXvrZ+dLvUfxaQD6jOaiW81QwxeNYt1VJ0
 +8011m/eBw5xuu/Ozk07SChGLvg8Xhf4yryOgOpxEc83QXPGDbBGKhMhHecvCai0
 1/S+/VSPrx2fYSGiPqnWVpE1EqhaOSZ/iEpMDQhQF9nCbmeP5xJAUKIv3vv/82CP
 5b6eeHLaNCsvIrDYQha2d6mJewiiZnpnwkARwJMJRje6WCMrs/g/CUgeTHeyhScK
 E2iZk8DgIS0Cqr6DY6yjZLGkjLmUpLuzAFCFDac5sT8I2wADBgf+N1t6ab7/OYmh
 vVex7CjPuqmK9FFUiZj7CstKltjOBajRKh7oz6KqDGcXwjRCWA4cuU/7I7q6IaIS
 L5+hWwzrK5Y63YxA8/csZ41wTGQSVoD4blCEFqdhCaR/J0kz4KQqIGM9OmT3zi8R
 +H+gb4e1oXApX20j5lxeQifHTI9KTbB/SFd1GAIZBLfWRO6I1vqQtuqFVOvKZeIk
 kIErHBdQnhGsAaEPKdxqaEUaqMUmM+/3dLhj0qw06+KKpRU9FF02ADRDwfIYP2Tr
 v7QJOn5Dn/TIJVq1gpPLu+lBUKugezwnabkFZuB26gJQ3Aaqnb0W/rdRlMtmxXCw
 jRujwCiTGIhhBBgRCAAJBQJQpFI5AhsMAAoJEPSLsZXFfPOosIUA/3Rt/SEgBJdJ
 E8fbDlkdsC8RMIQLJ9lbBjP4EF6HQPsyAQCm7eszYZZzL7nRse7NVQop+HPULeox
 IpuNrKfM7zuBiw==
 =yHIG
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.374. Peter Wemm <peter@FreeBSD.org>

 pub  1024D/7277717F 2003-12-14 Peter Wemm <peter@wemm.org>
      Key fingerprint = 622B 2282 E92B 3BAB 57D1  A417 1512 AE52 7277 717F
 uid                            Peter Wemm <peter@FreeBSD.ORG>
 sub  1024g/8B40D9D1 2003-12-14
 pub  1024R/D89CE319 1995-04-02 Peter Wemm <peter@netplex.com.au>
      Key fingerprint = 47 05 04 CA 4C EE F8 93  F6 DB 02 92 6D F5 58 8A
 uid                            Peter Wemm <peter@perth.dialix.oz.au>
 uid                            Peter Wemm <peter@haywire.dialix.com>

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 6134 characters]
 =7AWH
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.375. Nathan Whitehorn <nwhitehorn@FreeBSD.org>

 pub   1024D/FC118258 2008-07-03
       Key fingerprint = A399 BEA0 8D2B 63B3 47B5  056D 8513 5B96 FC11 8258
 uid                  Nathan Whitehorn <nwhitehorn@freebsd.org>
 uid                  Nathan Whitehorn <nwhitehorn@icecube.wisc.edu>
 uid                  Nathan Whitehorn <nwhitehorn@physics.wisc.edu>
 uid                  Nathan Whitehorn <whitehorn@wisc.edu>
 sub   2048g/EDB55363 2008-07-03

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEhs+ZMRBACu6CWtdlJ/GkGO4O6epy4SKwxV2s64od5j3ZG/+CkdXfHVnvDf
 NAdvytDwRPjFdQtwDmLTcotdm9akMpmoI+nuTDOC/wyoojh3NlTp/YmzSLntBoaQ
 W2uwp8oAW4dszTMptgb3Dpce17cHQcCuQ8Ql9tnZlFOvm4XCP00y7pmGrwCg65cu
 0wxbDYVp2fpPIG0D67q03j8D/01g68qU+JQqCZtCTDSJ7tG4w5zlOH6Hu7Q9wRhb
 XBDKX6fiO9CiRDorgi54DoKqjQoHWnFXrKBcAughLEjle5BSZ+Z+eu/tfMwDEfhL
 FMMPuvT9BVG/nukn4ufmk8BqPbw5PGalYGbdJvvjbyWhVIu/dexqGe9mT3DD7gk0
 WZArA/95nvE5+LRH31Jugq1GJ7cqjJyd/IPQC96z7JXdme7oPQ8IYDsLjsT982MO
 8WvwNbQPnRrj3Sgjp7EcuaFt/J66P7KvpU1lQKJDfZgk1LTL0Nm8wzLj2tXSwZWg
 tSOZewMItr2yKwBlpGDsS5K7CCpbocsndrI5DOPEzuYr7y+56rQuTmF0aGFuIFdo
 aXRlaG9ybiA8bndoaXRlaG9ybkBpY2VjdWJlLndpc2MuZWR1PohgBBMRAgAgBQJI
 bPmTAhsDBgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQhRNblvwRglgkxwCgmC82
 iM6zfYaJwcFsqETyxS+9Vv4AoJCemsKBmBQiN7o5K84/DuaCZTWutC5OYXRoYW4g
 V2hpdGVob3JuIDxud2hpdGVob3JuQHBoeXNpY3Mud2lzYy5lZHU+iGAEExECACAF
 Akhs+tgCGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIXgAAKCRCFE1uW/BGCWCFSAJwL
 f5HwF8PEUIEo/25Dwr72JCW6DwCeIm2wQjiyXl+wy1QIP5eX5Emy+Pa0JU5hdGhh
 biBXaGl0ZWhvcm4gPHdoaXRlaG9ybkB3aXNjLmVkdT6IYAQTEQIAIAUCSGz66wIb
 AwYLCQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEIUTW5b8EYJY+GsAoINx6fjsHpdy
 JT0UWgiIr48kEhtcAKDetW0OzAVCF8HmXMHWR/zyjVqHSLQpTmF0aGFuIFdoaXRl
 aG9ybiA8bndoaXRlaG9ybkBmcmVlYnNkLm9yZz6IYAQTEQIAIAUCSGz7AQIbAwYL
 CQgHAwIEFQIIAwQWAgMBAh4BAheAAAoJEIUTW5b8EYJYgiQAoM04WRCQ0LI5L78O
 d4VFwQSiUiDtAJ43eEJzvlPmvR2geTEaB6lJGNrBMrkCDQRIbPmTEAgAypfp7UhW
 ZPvGO8EfI90WkCclB/H7hSfpTgcZfQafWis6YllJ/EC+orAdQ79I/vdp5x5as6VS
 HsvN/IXXxoL30uHj2PTFV4qi0Tx8YMcw3xUK+wskQ0HonWsmZZvqHBSMbh0+JpXg
 75ZHXxOg/kpaFIjYz7cML9jSFBxD1S1/kmHqFnJISJ5wFAeXJj1loPfTbu6x5NB5
 BGbR/ysii9FidJUAXPk2EviD82oltntcNrUJS29ghFwM3FO/sZFdStQppNTgDnwO
 mUFyYxpwzG8vMjWYl3DWlc8ozXtKRotGzzsXuwUvdnC9e9MRX8xsF7x1vMrV5j6+
 5SGMnz6KvRzRIwADBQgAhDEuTI6+glgo0Kale3FKlKaOdz9R26uTCWVlK32O98jp
 mrdCfG1u1cknYrLlIVZIlrTgu3WqjRS9j23z8mIKQNW6wudu+/50/N7wtlV8k/s3
 DKmoUjcXH1b7vPxxnhFbtg41COFOUziIyXkupHEOJeaF+Sz4EEi8nXMKBEoGFlYD
 rh61rOFsfrf24E3dIwdLyjoTify8trdL5pgug27pHPMgXXx5cjLooq73VFvzlqCA
 3zFyypgED7UsYMH9NjmyLlA77gK4gfuAlGXwEWyh99SVksrvvHqntHyg9p+HdCQJ
 GyYwRMNUXTfdSn4cWVc+Qip1jpgdH/bbIwZeTIMaIYhJBBgRAgAJBQJIbPmTAhsM
 AAoJEIUTW5b8EYJYA0wAoJ5oqyCt4TZRVfofTeTGcm8K+a8lAJ0YGUPg2rEaTf06
 QaoupCN+daK2wQ==
 =hP6F
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.376. Martin Wilke <miwi@FreeBSD.org>

 pub   1024D/B1E6FCE9 2009-01-31
       Key fingerprint = C022 7D60 F598 8188 2635  0F6E 74B2 4884 B1E6 FCE9
 uid                  Martin Wilke <miwi@FreeBSD.org>
 sub   4096g/096DA69D 2009-01-31

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEmE02QRBACEWV7eL0shCAA+vdpkBCMxrQkbRAceOs8+uhsaocAai3TCiyUg
 Byzo9OKlenJ+bcZHFsBx0mUDPBRFF/NJPfhh0EpkMRc6VKvCHsuvjr1717gcWbLa
 ibbvard6cFAAUDXGIn0/hPABtBidFcA4vIb3EQES0PbnXEVfOz1gymojlwCg4/8D
 0ZICstqkxQMN+K6p/bpCV9cD/iMHVKnPCD9z9Bk9IJtkDGQ66OQpopY+oxUy9ZZE
 yO6Gnf8vDjPmPZ5RcDXu0XHlUpUF4yYkdnUKt9u71SVeDlBAQeFwRgDj0zbYKskA
 Py9YdR7bXbDPIuuAZyJv/93MKryHAEyr8aieAoRZ5zslRcOUrRbzueKi68P01xM2
 H6Y3A/0bE+8jz0WWugB4d/D1qmpnxIHIbzWN4S2NICJmMcj/jgoC+p+DTl7TH6Rw
 KfTt199A4n/g8bfrI86hOQWNY9l9CcBqxwJNMhlY5a3Y6y81tj98oIFuTonyZEDd
 GZmXp4JBDEIYHVVL0XyD6pvFT2NLr0UHWAFZwsiWK+W0IrByWLQfTWFydGluIFdp
 bGtlIDxtaXdpQEZyZWVCU0Qub3JnPohgBBMRAgAgBQJJhNNkAhsDBgsJCAcDAgQV
 AggDBBYCAwECHgECF4AACgkQdLJIhLHm/OnvuACg499DhQhK0dsl+rDk2l+Y40Ec
 DiMAoNVTN6ybdr16bfoIoYddjsnKn9rPuQQNBEmE02QQEACo7w/pIuz1jhyXiKMh
 n6/LWwQNdIl5WT4E4DSB2/NmIVkGTwyyUET1nE4NyOVJWeHujK+PxZbtmx7OVe6J
 niwxv2NeWJ7EkLoeDTrSBKrFCqWRHpbN3bSUAaXiwU9HeHMbGjvvVRg86gzrPKlG
 I5blbT5N5QgQESuvS5eOgGZLbUptNIGwA0hUWOPN1YR6584XGeV0N18GzcB2nXn3
 4Tj82IpeqF/iRY2VxZU3EcN4BoeDYcibPygA3521jWvPOnC9/uqeY/RsORKvyLsT
 CsEx3pRew0vhbJ8me8WkFPwVczJNWqdhEjxMm0NS9FyBDRgXTn7cROJiuonrGWtY
 6HOEHIFsCIzCTfXG0zDaC6kc3k7g4Xlz3juzOL/mhDjnbH+G6VlqfHb6KP3YZnU5
 fXtwFTRF/AFDv58m7PFGwAWjIU3mARzbhdKN71FQnp6aEdWIY/3ZyTAs+En1RWgR
 bHEO7Jg+55V6pH/Cn1p/aIXYDOqIp9HMi9w8nxM2mFt55MiqdUX4RkPxwUdy6BPK
 22LxmxYBv4XrdQNbwy2n7k8H+wfQrKhP+oEKM9WFLTXpKPf52xTB4svJMd1yBZXZ
 FJZSArffJ/QlZ2HgC37V2HcXUOlvU1K+tan/xY2NbJmuetMU7N/ePUWyi4mg3Nww
 EzUpR59KjrqNI2if2qX7yjCB7wADBQ/8D2LYxz9SCqp6iebELuTBWbHtBX2r5xyl
 Z6CuDyjHQy+LOW2D2WEq3b1jI46HFp5O381jKNDJxx2z6o9E9dV63wFbGWIxoAec
 TEdbtf5NBKljFsEtdSg8xdaQa/8FdnTm9EK1MV3C8KqH8e1VBGaHDOlPU1t9zrhO
 Nc96n8OCl4yk+VldoVycqIgdpta4e8jR6kMGLlCXq4Mq6xR5usUoo6jSab4PSEC4
 BZDE4WCzbrahrsJGK4hVmpzi9ofGiqOPf0+XUWG7Na6HyW4GJPohVmjJHyjwc4rf
 bHtJTu53Hk6S10HHYwbRJz1YO+08KrybtvdzXgTv2C/dYBmjheN2ylKmaXYo6bAa
 GcVmW3gFEUTWQd8qQtUJzL6LgreUjuY9xv7Z9nUc7SL63XfAjs3H75vavNWZ8Y/J
 Su/WuKXKxkJDLwzcKHnUVOegEXe0Q6+Khe056WSJ3VtF8+tAaksN7RRslrf1MmVt
 nVag81z/1UvOwNsyLVEucPnh/8LZxD3plUvscKm3w7rsuWiQ/Wtn/NCW9MBeZuxR
 QAUnfWbvHPBo1Dgo1essw+Q4crMGAprk/T8/kPuxrHQ3ZydT0e+t+noDCxcLeoP+
 oqS1A/Za+idThWujkwos8clIyW4HryqAejrFhtzhfC8ELkpkjq0B7Yd/8Zv52O1T
 haaPTklRPcuISQQYEQIACQUCSYTTZAIbDAAKCRB0skiEseb86WULAKC5M2ASX7/v
 bNgnr3BzKKDpkqoskACfcKvwwi1c4AsPtLPxbySr6dUwhlg=
 =S3Qn
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.377. Nate Williams <nate@FreeBSD.org>

 pub  1024D/C2AC6BA4 2002-01-28 Nate Williams (FreeBSD) <nate@FreeBSD.org>
      Key fingerprint = 8EE8 5E72 8A94 51FA EA68  E001 FFF9 8AA9 C2AC 6BA4
 sub  1024g/03EE46D2 2002-01-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDxVl7cRBADbXnR4t/xRvvOSiPuGPnOGeamrphPbpPXsWD8Nm/pjfN3fhSfa
 0gv3Y2n/IyLTg93gWZhWloMznkdg59Oj0oPSUxjgPauVw4q6l3JJIcurJNlp/Q7l
 DH0KLFJ8GuL6zxAz7Jcx1BpAIEu+G2SnI8+ZuGvq+YwaDxPFavfCqmVaBwCg/iPu
 OI+84/W54yZXvxfUN7dkDmED/3CxYLGeWqPqE8B8Eq8BlmgfP/FwaqXXb6xR7jsE
 XBaqNOIita6Iz49sYTYKYY2rMv6dMXjX1FM13wNW3rS73xkNvuJz0WU6sWl9Hw1e
 kjNjCN2oIqkqB5/1H14NMSOcUPLqERP7goFIK7OAJejUmm5Nc3KjG1S2G97xxjPe
 39mlBAC0QFfa8J0Z6TORFa8Uqyx90pC/Y+I/S+y0vP/59ReP/PnQq/aUdDPLt5OZ
 edtpz7M4A2GtoVkWtedPRsw0hYK+Q3CtOMemQSnlfVjTZq5edL05Po09N89M/WMz
 hB9aRcdY7IN/btsQ0H12ZH+rEj+O4Adu+qEjsWePfW60Uj74GbQqTmF0ZSBXaWxs
 aWFtcyAoRnJlZUJTRCkgPG5hdGVARnJlZUJTRC5vcmc+iFcEExECABcFAjxVl7cF
 CwcKAwQDFQMCAxYCAQIXgAAKCRD/+YqpwqxrpMSwAKCVuyt4B1Pc1tAwRMEOmmZw
 2nGIIQCgyRvB49snyBl86TikYv97ZifyLmK5AQ0EPFWXuRAEAIghycOZtElvBhfw
 r7TisjtVtzKhbF0Kj9cGg5brCC8/bJLK7PxNe48NSdlqMJ7algumsgYR37b/QBmq
 sOSEa2wXCnvCSD0ol+bdPn+Psb+hyi+AVNmVgdlJwuxHUHny0lWQnxeQLrt07SAw
 Ye/Nnc+arH6GXzBwXSpsQ2sOaMajAAMGA/9Hzjkv6HmJkPlKT2TNx33mbLaDk8xv
 vAJXxogxDcUqDDwqszWPcqShaW0IkMZo+grZfykZJjA0/8QUCaEUwhnYIwHMQRdA
 uNegCF/D2x4yzkF4d9gKYCCykDUrwvFDztIhGkinyzu6+xwe9qFcL/esIxnnonz7
 Wx8/3e7pRvS2QIhGBBgRAgAGBQI8VZe5AAoJEP/5iqnCrGukuikAnAt8uA1EIv/5
 WDCIpvNp0lgmwes9AJ4vD1R35+Db6UIw+R5EJaxNBY84zg==
 =xbGI
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.378. Steve Wills <swills@FreeBSD.org>

 pub   2048R/207B1BA1 2010-09-02 [expires: 2011-09-02]
       Key fingerprint = 98FA 414A 5C2A 0EF9 CFD0  AD0D F5CF 62B3 207B 1BA1
 uid                  Steve Wills <swills@freebsd.org>
 uid                  Steve Wills <steve@mouf.net>
 sub   2048R/E9B254FD 2010-09-02 [expires: 2011-09-02]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBEx/EzEBCAC1Zje8FA0qGnqKv606untNjiluqEWTuwHOLPKLm0d1Pepb7A21
 33kagHn5I8n6k/H/0jE+a2omlmPo5yilKszJLfPYXmqfkb8ZThwYG9Ly+kb3d/i9
 m8qxlVktJ/Y/Cnzo1OzhUdxY4Icp0t4nVPZrHUkeA2DeuYK9zl4fq/wah6Z900/K
 tKBZqn8aPMbkjK6lFJAHNJ5gPNdyT74/nXyhyRMMLqRv0SfRRDRVcxdYW1RpZj7g
 d/CF/K7zAnG0uCeQA03/F2Mqagp0VW/4/QDF9+Y5Dia2oO01C7wAvyNjQsXjughh
 MRnYOfcescpw6r46mh1iLRGQa73X5V2vIwGDABEBAAG0HFN0ZXZlIFdpbGxzIDxz
 dGV2ZUBtb3VmLm5ldD6JAT4EEwECACgFAkx/EzECGwMFCQHhM4AGCwkIBwMCBhUI
 AgkKCwQWAgMBAh4BAheAAAoJEPXPYrMgexuhSr0IAKoef8NOJVAcFSPp8ke84k5Q
 ypyBtQLipQFjfhwyGiuP3H1+iC8BdSHSHYLKe/c3eC6V+3ybE0eSVr+AHRMMxyKQ
 DKi4W3VzZOpCjJ2CohhmywbDBTBK8svpbQsjanBPVIQGX8SDbnW2e7uocDbpOBkh
 wnpLCXsSe4He7XgMNHbEMsZ96xCXvPnn12Qtk8nE04ugUNMpCDFSvzsr5XYMoi+t
 fHtsGjYZzLju/zRV6hKTd0yqcrhq+8AR+9gtMGBzQQ5WOjQLaTQNXL/6UhlDJBaP
 AaaOM9mudn2UR0dkPKNfpSP76X82Q1N6iNrrkIYt4t3k/iFgIalcLDhiw3FKv7q0
 IFN0ZXZlIFdpbGxzIDxzd2lsbHNAZnJlZWJzZC5vcmc+iQE+BBMBAgAoBQJMgWXP
 AhsDBQkB4TOABgsJCAcDAgYVCAIJCgsEFgIDAQIeAQIXgAAKCRD1z2KzIHsboQUS
 B/4vQDhgf5SM8SZEGh3nMd0aBqXnxQ4wHMZ3Du/SdA8ezQ7bmtb2UOkkj+SknBVR
 AlDpXXCrqwUZfBvcnc6it1OmMyT/7TGkt5TaKyO5DM5lV8DKBGJI89CRGUT0GzxD
 pi8u3g2jH8gMFY9AZYWZ+xkQ070G86kSMyrtJIXvJXZ8EnT8+32Xpak/up4Tsxro
 3h6SYb2ZxTioSc2OhhPu0l8IydQcFON4tLjynmSvyrHyd0rQtQe9+yCdXHt5ceT7
 eLRGCQDZ7ANlqNGn/DZqELdAzo85uzavTliu4KMp4EO+OvWoYOP77MnHEtQJX2Sw
 f9W8z/oAk+Xfc3XY6xFsJ4wouQENBEx/EzEBCACqJlb0BTVxCWzmT4teI4g34tVX
 hAqQAIp853VCcIGXYUsQ5SeejhPpc5/8jxq2ntyY3H/l6CjcVAfMTARF+/yUMkGe
 vDopAsWD2m4PKgE8upaEP7/qfjsH5Izl6Oj79XFelwACvr6bi+rsDXr/UAwVqN3V
 d4pSHlZHpj/T+eu6+bM3y3Uhtkt+CtzMtPhtflAjiERhWc44qRAyLhiIuJe8Ubzd
 vDqsNo8kaYSJfHjrdJFdHgpvz9eiyHuAly+CF6Ne+FqBX/5OI2Hm4Amsxw7ycyrb
 lLoGVi7mn00eBT/B4ocb5GSaWuniBedip8hi5h7oK8JFqICA4BRYS0CO0WLnABEB
 AAGJASUEGAECAA8FAkx/EzECGwwFCQHhM4AACgkQ9c9isyB7G6Fgdgf+NFFmqmRr
 EbH0U813djSroqF6TjpsXS/XBYH3LnwiRojqNq7yBG9I2nWIRSZ3pGjDx8va9eZr
 9VPqdx0khKVKPl1TH1FMJYi+qvbkUqIQKc4UiFC4CHWbpCFe11HLi34L/uQWyWxq
 ityTpZFy9mlH1xsS2Fz1TVYiuwqe8e4fYasr1DOnWjyDU3c1UNoY8ZcIqckyFEUJ
 HJqlkdQ+bqO7wvzpk70pQU+Y9Ab61lANZnUkNSn0kzdqg1jJcMZpjEwsHo4zFbgw
 eMQuxxC31F4FhX/4XJGeFk/CgVNrJq/HJXAIRDbuOybQ6i7AqIhEGFPidlAcw3fz
 eYhPE7EaCOyuAA==
 =7zxq
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.379. Thomas Wintergerst <twinterg@FreeBSD.org>

 pub   1024D/C45CB978 2006-01-08
       Key fingerprint = 04EE 8114 7C6D 22CE CDC8  D7F8 112D 01DB C45C B978
 uid                  Thomas Wintergerst <twinterg@gmx.de>
 uid                  Thomas Wintergerst <twinterg@freebsd.org>
 uid                  Thomas Wintergerst
 uid                  Thomas Wintergerst <thomas.wintergerst@nord-com.net>
 uid                  Thomas Wintergerst <thomas.wintergerst@materna.de>
 sub   2048g/3BEBEF8A 2006-01-08
 sub   1024D/8F631374 2006-01-08
 sub   2048g/34F631DC 2006-01-08

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBEPBdXQRBACT86OgiQJqRNqy+gSXuAmYH5Cpqz1iBuv6o+uye7O3x6cTLg/r
 5JKnhu+rgW3fd1QgAZn07fwjcJQLAx5BcS/3R3aGYS+r7IH0M1+NoENjwXjOed2B
 E50r9DYyZjO+GtxqAp0SQI59aZOTaA3UDV0sRzM5xn3i+7P0GoBSHTtszwCgwVYb
 ixCmah6KYSvA7sy7RgEk3bUD/jhSchFtQV64L7AuUbci3plpwFYweSWYliFNjlL/
 g41uPjhIP5L38yG2R7sDY7sjdnvJ8b9ZTB43uCe6/HxHNTj8zX8i5c3AP+KxS87D
 NGnrcAYS2eR85w+EdGGQWcDMtQj6/JoW8BF8VdmDgpOmVMlqxrtGcQcY7fxUat1q
 slJCA/41xOy+1aJgWak2JRhOMEeyb+k0bTFKWUIZiVHIGk8RbegW0isRa20Fj8r7
 hT+oNEeCtIRyO16z3koVzZ0gLA8+JUPn0wEU5VuKpNsqiafFLjYy/mjaxlt7Pscn
 d2V53y+usYoOLFQs7GQooo6PPh6GluTBooFqmLea3U0CTs8MCLQkVGhvbWFzIFdp
 bnRlcmdlcnN0IDx0d2ludGVyZ0BnbXguZGU+iGEEExECACECGwMGCwkIBwMCAxUC
 AwMWAgECHgECF4AFAkPBgKICGQEACgkQES0B28RcuXhHPQCgrf5qxNn53vvWganB
 OLg9rU482DoAn398pRFSUp5aFo7Dz9+1e0wY+JGjtClUaG9tYXMgV2ludGVyZ2Vy
 c3QgPHR3aW50ZXJnQGZyZWVic2Qub3JnPoheBBMRAgAeBQJDwX1AAhsDBgsJCAcD
 AgMVAgMDFgIBAh4BAheAAAoJEBEtAdvEXLl4uEIAnjRG8femt+4gnF68wbKZJKnF
 eVcOAKCFNb+kdu2S2iU5yJehGPC2Yfi4VbQSVGhvbWFzIFdpbnRlcmdlcnN0iF4E
 ExECAB4FAkPBdXQCGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQES0B28RcuXgg
 6QCeOPFerndygwnAqnSgBEOXKl8jhpUAoIPLowj1HWWdva2jId1LfiuIdu3qtDRU
 aG9tYXMgV2ludGVyZ2Vyc3QgPHRob21hcy53aW50ZXJnZXJzdEBub3JkLWNvbS5u
 ZXQ+iF4EExECAB4FAkPBfOECGwMGCwkIBwMCAxUCAwMWAgECHgECF4AACgkQES0B
 28RcuXixFwCgjqi4KzU5QCpXPIAxX2pI0SIIBGAAn2qA0BNdstMGSPqCKuk2aeKK
 qr7dtDJUaG9tYXMgV2ludGVyZ2Vyc3QgPHRob21hcy53aW50ZXJnZXJzdEBtYXRl
 cm5hLmRlPoheBBMRAgAeBQJDwX0dAhsDBgsJCAcDAgMVAgMDFgIBAh4BAheAAAoJ
 EBEtAdvEXLl4n/8AoJddHunNAucAY+h66q2tF3hVIkwxAJoDvR58qhnLKR5zMIBC
 dgXKrtddILkCDQRDwXV7EAgAxeuBjuCZYxu9VwWjra5SIuPSBvGtDXFZ+8AVl6YZ
 12wi/KtEQvB3viClH85CYu0CMi7nV0DWjDsqvot3NitKBLMnzxNWp2NBM8btCIRW
 m1/nmM/dHDrbbEXDQeLwP5CTcK9Lq5x2psoLYLuuN5dxXGAuyOekfRpO6rVuLAvU
 r5lrV8Yr2T4Wwhe/uxZU3JRww7JqPjaEHT/AlAGwVLqbtPLmdgwK5Bb8NRAvxEmm
 Dea5ypFUsLQC3C297kKZ80I4cBXj14iBEnceB+M/kHH66aD+6oecTadCtlWh3051
 15nZFVZC+rRbf/VazjgXN9KdUsrxJ4hPAK9dCPjV8Z7eNwADBQf9E/Q0/OGNmGA6
 bdJSNvPSBD7i+RXkVRI4AiWhYLTw3sAvD5Zb4DPuSACwsoZegNqUqHH/aTqrb7Jg
 yQVgCBXUHsu3Kjjdaz5VgzLI/6v5nE7vyVaL80cU8xFnRdLKLCZ1S76bsGGnhKHQ
 7APJTTXX3TusdVKFo0tdx3o4oSBwRt939p74N33/PLp6NTpg2uNa2R29O+d8Ib00
 F68GuUmUMgGFpK+RVMgHO0ON/DGQjytTb5C8reethVstFXRnw7318bYdloN7wp5V
 KMuaVvR8sHcUIqpC+eYXJw7GxZO+4YRMAb3rkVN+AIgeoS7EnU1GbgyM6yXWV/Qo
 2xHt2gIwNIhJBBgRAgAJBQJDwXV7AhsMAAoJEBEtAdvEXLl4r40An01vu+UirSJP
 ABcaIIYdh5NW8fFOAJ9AosnjpsIlvpO2Rblw6tBoAvdxvrkBogRDwXyJEQQA7zb7
 /Lc8rllk/qKxtSK5USD9qc21tjV4oH8cX1pAzVfh67OqK6EWofRBejKs5z4wuIGU
 pi8I9YQa6o+TBe4Z/w0ZupWwoNxFtSKXedWPFplJ/GkMLZtIoG5n6Uec4zfEXMNV
 yeIMDkioZE/9AiZZXK2r5uKOFrbp2jutZIfIPGsAoKF+KSKZLfSukvQGySH/vVTt
 MwzZBACWeSOP/Iay+yK/oL5u+9ALiUpcWglFMHwaNbGUxGEIFptO7Zdk/K4uMrQh
 mspPzGT3FndAMoamA0Wq/OxUBJVjrUvSzckR/G5/MpIXuXjgYwrCuqf8B4PYOeRo
 2FKRHRcVpBRlQBC/pDbmvgx0Vy8OFoluOk9tgvWezOB5DC9GpQP+PsmlUePAbGI6
 /sb9tEfbC+8cjsaRZL+LGCSfXOn4q2jFhVxdY3941N0wwFu5cSzxp7iXFVAiGI9H
 qk1RapQ6gW+GTO/K9hVbccLXB3tdllpHJKRM27HXNieXe3DJ7tJxCFFfhGoPWpcF
 kQWy45AVPOWzSAWoLC6ecj9Ukouaij+ISQQYEQIACQUCQ8F8iQIbAgAKCRARLQHb
 xFy5eHBtAJ0SPgJdqpiKhzRCduBUr0vzOHqFoQCdFG3I2UC0Pb6Peszs8HZdVeKm
 NaC5Ag0EQ8F8sxAIAMi89otKQxeJCb0LKBtlrq3ogt3RCQPJ1sPir3D7EBm/VkKC
 WhlbliF75VTW8qWD2HA4DqPU81N9o7ZjCMX4Q2LwzfCv8liJ+ZXlHZsPuXlLmZHV
 jAqKBtc3zuE1nTd5fHQP4GtaGQKG+3v8p0t3JfpXgit4OGYANFbF1i3174Rfpp9T
 3LxRHX1iPDsj67FP79Ycr8w4tmdPBw2Z2Gh6M58hp9Z4ytEFfBUU1gD4tfl74L02
 IAoSpkH56d85z264k+bRK2D6aBnxCKU7BLztG8RAK/9GCAOqxv16I3oByvZNGMx7
 ECd13dkh4r3kXNliLg0bF3oMHaN0uqFt0Eoqif8AAwUH/2t7GFrqviBQwtr2em+o
 1Ac/dyqj8F/ciYPnlaomOEypdhI/M8lMFySkH7M54xl7e0FVHvWvxhHu2D3CWgxh
 0FW0gLS97HBbNxjYQCIFfNbT5WmRMPvihG5ym3TCOdo9UD445a4+DSqSLo/SZi8z
 G5lUuuI8OYRJQ/43ka4lzbdUAI8YjJnyk6YQlZ3t7eYTkeHWmOrlTCSz6c7jQoNQ
 rbIxrrkVi8kewd91853OekuLFZ6oZQtU/YLYFicacz8HE/r42uPsG2azeqqd19XF
 NJOFuTut4fdAYbVeztIN6xYdgx+tI/LGzTSoMurOYI/U5kk65ABqxC3kgyG0ad+W
 AYCISQQYEQIACQUCQ8F8swIbDAAKCRARLQHbxFy5eGGAAKC+QKCN4M/grwaBbTer
 B5lKgt0VCQCfdhlL5hMDBDoaMdMtBZXFL4/Vn10=
 =ArNG
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.380. Garrett Wollman <wollman@FreeBSD.org>

 pub  1024D/0B92FAEA 2000-01-20 Garrett Wollman <wollman@FreeBSD.org>
      Key fingerprint = 4627 19AF 4649 31BF DE2E  3C66 3ECF 741B 0B92 FAEA
 sub  1024g/90D5EBC2 2000-01-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDiHU3wRBADX+GS3fClPc0K3s2RePf2YeV+w7X3cmnWb0FLhAekfIzjLSHl8
 PWxXXQRtFyjR4KpsiwpGusX/nIJmaEoAdyqROKvpqYZPa3CjI2ldq1t1mj8lUOLo
 +ktQvgR/fZoveOl+HT1yIRZDsLrQWYE96lC8Xx2Iiip/16whzhE4rJfWvwCgyb+G
 a2jW0JaqmVRmyEqwzudoeqEEAKNUV5lmGRcs/GxwAJ7JRcxMI5QtoUBTfDKYyJZi
 t6pudVC9STIpMoEw9m4c5KRFixdiHno/dbkECvSzpTA1qAHiC2WxeTXAz91ySTfk
 iGNVlc670A+eC7Qi3ZGYhWKgKAvm0hOlYxOrU83u9naHKA+l4dOIGCQoZ7ElcfdO
 77T8BADQG/nzZcaoS0o9za11YcYMAWDiEHX2JyWF7+O+qJc7UmAGMZ4YHeYOBTkT
 6ybzjn5JhQtSr9YQglweYFjFYdeOmQAYow1MJxJvh0e0eoXwzOgdwJ8fzbxpHeAQ
 W9uuI754sm3U80ag7RvzgeWRX7HdETCtbFF8ZCWHSE7sj29ZB7QlR2FycmV0dCBX
 b2xsbWFuIDx3b2xsbWFuQEZyZWVCU0Qub3JnPohWBBMRAgAWBQI4h1N9BAsKBAMD
 FQMCAxYCAQIXgAAKCRA+z3QbC5L66jfWAJ9QRUBS9u2D9s861txzAAGDur0x/gCd
 ELqxcKVno9Q/l0DFb6c2ZIlkTT2IRgQQEQIABgUCOIdUpAAKCRAj54bpvu2UbtDT
 AJ9anhNRzF+bPhzGsoVJG1M0+aqsWgCfV6grZerQHY0jrzh7AcGCMNNDNYaInAQQ
 AQEABgUCOe58UwAKCRAff6kIA1j8vYq/BACbNYb6vCIi7/qEYF6dcBrEKf3sQ9mR
 U+ign91BqI1XR6KWREzMb7C/j/8ClreLp+UYpzf2dGiMtg6wo05VM9/wNTgQ9XGQ
 lm8VHRuMG6nKMxzMmugVhoKM16g4ongkLwV2GP7i/UULLl/YtBY0HHeZrvX5dFTI
 e0I71GmWy38WDIkAlQMFEDnug1NNVigheQUMEQEBX6EEAKTQbXGBs5XC1NuI3UdO
 DRvpRnzwY1KXlcJNWEUBFnwKqNdu23XyWT9VoMSHQwntTH1LkdYrrZJDQIlCchHS
 bRoobiveoUEqqHtWx9enhADBbSyl+SeDanOd1rx3jieplg8rseeqS7j2k5EUCaus
 wsk2W7zn4mpRNR25WuO8JOhjiD8DBRA57ojmGPUDgCTCeAIRAvbfAJ9SwgJaBMEF
 FYpRIoNsgvnHRaBmvACfVf1DdCW4EiCwtstuphmkZU9uv0aIPwMFEDnuiMGI4Xsd
 /OVlYRECVBkAnRJA6imAt+d9i2csxiReRI2xCrC/AKDjL3Wlp0ustkS1SkXiEZmX
 OcGfk4hGBBARAgAGBQI57oOaAAoJECAVMdWEXf7dfowAn3es+GZFfAzNl1BY3IdA
 kHBkpybbAJ0SghHeM67I6UvsD3OY4aKDu7D/g4hGBBARAgAGBQI57pd1AAoJEML8
 hqolOUaLhLEAoOj8APJHlYELhru0tPRZSfZYovDmAKD9rBzlJZzxeN36SfwkYiNW
 nnl0A4g/AwUQOfXFQNjKMXFboFLDEQK0OQCg2TuAY5h0Q7dgZgDe3dW/1zlLjskA
 oOFLVMM9s8oA8sTCTGAMqnca/3GduQENBDiHU6IQBACjT3ldbYOk2zYwEcaYhxom
 HuhAht9WhqRkBstdrJbmHw04zMNdRyodfbZk/DunKPnYPjSXVL2m3aXXdzPLXmMJ
 WTA7WykvMxBZX9A7GONMwWKOoZcEJheNagfgOa+be4rZ/S19AnUDBXQGDCgbXlYa
 BCrSRuAmfOVQ4VLW+3OovwAECwP/Z1P1kKWACm9Ual6GAlk+R1pASGOJS2kOyYkt
 0VvV9BBfYaxD+4E1xp6T4FEkdQk2Lz+91q/b6z7CA0Ed/2yNtm1HmVGyMc5yFRoj
 U38i0Lrxf0fo06g+ewwIXXEEuZrdGEFaxQpWTZ/uCFiGe1wtnGT91B4FDENxuIQ/
 IbrSxgOIRgQYEQIABgUCOIdTogAKCRA+z3QbC5L66mpDAKC1YD/4KeNybL31f9B9
 iq7OH/kskwCfeEvJINcMBk0UEdjpgO85woB6QKI=
 =stB+
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.381. Jo:rg Wunsch <joerg@FreeBSD.org>

 pub  1024D/69A85873 2001-12-11 Joerg Wunsch <j@uriah.heep.sax.de>
      Key fingerprint = 5E84 F980 C3CA FD4B B584  1070 F48C A81B 69A8 5873
 pub  1024D/69A85873 2001-12-11 Joerg Wunsch <j@uriah.heep.sax.de>
 uid                            Joerg Wunsch <joerg_wunsch@interface-systems.de>
 uid                            Joerg Wunsch <joerg@FreeBSD.org>
 uid                            Joerg Wunsch <j@ida.interface-business.de>
 sub  1024g/21DC9924 2001-12-11

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.6 (FreeBSD)

 mQGiBDwWI2kRBADM4C4YlBiLozC/bZDedK12BMLyfnv9yOppj/doC1cOEaE+xZNQ
 7/aDZfhi7FNQzt+ehh52DLihV91G7gOsACtUk3gLR8G+0q6U76dBY/gvAGzCYUu0
 bJwlQCcPMysF4sNEwvsuct1fIVAHa+660X6Q+WI+eADIwZyN8wR1GrEqswCg3uGM
 xm85EYtxPFx7tyxfA8q/d+MD/i+SPmt9xEZ/KZOMbQVPw/vYmeWW4lVZGG2HLKmH
 J2FiAW4YjryoNqhpbbqlJigxf6staqgnQL4uuzBrr6v+OIjbljTHA7fs0WA4mtTX
 u7YcAKPXBTztw/O+f3tZz08Ep+AHJ3Q+pTbbRQZpikGGdOpjfLcEyAQBh1rNA3zl
 /MiLA/9IL7yfpyiA6cjX+MuUCqlqbPW2awQOCsmDBOcpXdOYC+MsBUhlT7IcFtQd
 BUxUiqdIKlRtIT4l4LnqzhL2HASv6Zzc06zGS+tlG6BlpCGlSxz8fp4asbTYdJnp
 d7lqme75jOUNjygal5lxJApincaLjv+4IaNUWCC5RjQuRsd3t7QwSm9lcmcgV3Vu
 c2NoIDxqb2VyZ193dW5zY2hAaW50ZXJmYWNlLXN5c3RlbXMuZGU+iF8EExECAB8C
 GwMCHgECF4AFAkGkelUHCwkIBwMCAQMVAgMDFgIBAAoJEPSMqBtpqFhz3+0An1WU
 SyLW5PtVk8AN2wZOZoIbdpWJAJ9UZjNCICVixY7lc+me/lfu7+nCsIhzBBARAgAz
 BQJB4lonBYMB4TOAJhpodHRwOi8vd3d3LmNhY2VydC5vcmcvaW5kZXgucGhwP2lk
 PTEwAAoJENK7DQFl0P1Yu+kAn27zpfl6Angb/DIsaV6srJ6SB/hmAJoDHPErifuG
 2L4KGF3NcagZRoUl77QgSm9lcmcgV3Vuc2NoIDxqb2VyZ0BGcmVlQlNELm9yZz6I
 XwQTEQIAHwIbAwIeAQIXgAUCQaR6QgcLCQgHAwIBAxUCAwMWAgEACgkQ9IyoG2mo
 WHNIRwCgnTUFJ1krhK0XISLLossxl68fS0MAoJEjQcOZTKtIp8S4Dqo7/VJYUVKF
 iHMEEBECADMFAkHiWicFgwHhM4AmGmh0dHA6Ly93d3cuY2FjZXJ0Lm9yZy9pbmRl
 eC5waHA/aWQ9MTAACgkQ0rsNAWXQ/VjuVACeKGyJ5VTFr26fxsDgqrlfXjksoBMA
 mwRwLuhmlB2Pn+40rvnL2pletnCFtCJKb2VyZyBXdW5zY2ggPGpAdXJpYWguaGVl
 cC5zYXguZGU+iF8EExECAB8CF4AHCwkIBwMCAQMVAgMDFgIBAh4BBQJBpHqjAhkB
 AAoJEPSMqBtpqFhzMlgAnigTVSmOOtxzyVwJaZDDxeg9aQB6AJ9rnepmNfxu7F16
 wiaVo6US+2p0SohGBBARAgAGBQI8WsL5AAoJEHninGCwBj/nbsMAn1LuO73ckkBj
 VxG/Qzy6khbyelOHAJ43L5JMsDGyhodaCwZ/Xc5AKAm+IIhGBBARAgAGBQI8WsMg
 AAoJEMYEPFZyB3E3MPsAn2mgRnF3H7gjW814bjWgoWFBmPdEAJ9FQuryfHAGylj2
 lZ5R68k0JWEY+YicBBMBAQAGBQI9JF/ZAAoJEHW7bjh2o/ex+jkD/RNY+vvEo2NW
 RcKfCV53bYQaYInBBaMyLHjulxrDrUPfTjW6BzFMlEf4h+hlz2bV+uVBjhiJ2bFp
 qL2vE6HEHzkloVYfk+4E8NDTVMPrUjX/Nd8Y2dsfAWPzx3tvdHZiyzrEQhDtU/fJ
 gBOds8eKhxIyjwxTD5smbbqpJyWuh7kZiEYEExECAAYFAj0kZOUACgkQYQrfI5Z2
 HYyemACfRtNZdqGCp6FSlz4EAtEys+B4w5AAnRmk9vN+kS4hPBU9a6F5GgZCMpti
 iEYEEBECAAYFAj00IUMACgkQah06FlSR5oNAMACeJP8yYszO9wkRxZKu7fovNzgk
 +bIAoMQBBw7DtYtj/KzJKRXmoX277zRriEYEExECAAYFAj/GOYYACgkQwAfeuzCC
 U0VBbACgs3OzHeay5aoOwjJutpcFBx/yKMkAn16kZ+r522qJWbHMJuB3ukiWxY0d
 iEYEExECAAYFAkGGExoACgkQFbyd9tifJxTfsQCeLNVa4Ns4iq42JGfwVZvb5gRt
 YrIAni02UYsHBVESxl99372haKmgH4HwiEYEEhECAAYFAkGGJGkACgkQJHERf6lR
 AsE4kwCgzzgFZvvk4tdr6xM7s/p1gmgBosEAoMA6Ib7qfoOuSrrlUBvMte33EyNL
 iEYEExECAAYFAkGU+XwACgkQkgpJOuNBnRoxuQCfTKFHVPqSutt6CqKpsLGWeF4f
 Z7AAnAxEWkhRLMAk6EYKcx1LRTmN1B9giFcEExECABcFAjwWI2kFCwcKAwQDFQMC
 AxYCAQIXgAAKCRD0jKgbaahYc2QDAJ91rDkVGk75blkHwV92zSeUGbFFAgCffenL
 K+whbH3KD0+rhLtOTkv7AjyInAQTAQIABgUCQYyQfgAKCRAff6kIA1j8vfC1A/4s
 yV9FHODYYlko5XnMZG5ZQ0erCpF+kYt70XxzsiNSWDYUXX2mtNniJdWMBBzg9wL8
 1CBt+5koVclllxeWJmYIemXEXcdC1o+aQ10b+JEUQoYDuEFfLTAV/zrMhBCP2qIh
 Z/lpqdQu/vTCgK0FGA1HZ48i/q7v7tE57nS4A+AT/YhzBBARAgAzBQJB4lonBYMB
 4TOAJhpodHRwOi8vd3d3LmNhY2VydC5vcmcvaW5kZXgucGhwP2lkPTEwAAoJENK7
 DQFl0P1YqjgAoJuop2gK1sXFJsd7XhVtRCzXK70dAJ4zywlp9erDWgofGE7Kfuzn
 vkFheLQqSm9lcmcgV3Vuc2NoIDxqQGlkYS5pbnRlcmZhY2UtYnVzaW5lc3MuZGU+
 iF8EExECAB8CGwMCHgECF4AFAkGkelUHCwkIBwMCAQMVAgMDFgIBAAoJEPSMqBtp
 qFhzgrQAnjpusj+cjM07WYmSXgjY8QXUWmkUAKDJN9He1N83pEewpJ4p7HnxJeSk
 SIhzBBARAgAzBQJB4lonBYMB4TOAJhpodHRwOi8vd3d3LmNhY2VydC5vcmcvaW5k
 ZXgucGhwP2lkPTEwAAoJENK7DQFl0P1YMUMAnAzE1fKsKB3GP5bN/S+qkhv+Sqzc
 AJ9km5QT16De3Ramxa8XImxg+rKpNLkBDQQ8FiNuEAQAnbGJUHM83j9CulgGV2kj
 OB2n/3t0sRM+d+tZijBrhsOqSv2c4ld2rPaWyHpwF40ZvgAqYw/XtbTS32kS+DOO
 4zHQM5yI2OYf68TaYU6TQrApCYJVPmZcQZRCGl54RF63gPa6GmteYoEUnA03leyQ
 nWzV69A6xR2vwbfXo1eq8TcAAwUD/3/ITIMjlj8eJDzGHPRaBsoYspKF6nKCvBn3
 rfduyZm7b+yknZKpCYDr/E3jvwM2CfnMJgGXH6xKnL/Nn10Spah2WjDvZ7Mppflv
 BWHwL3J+qz4alKtnZDFg+PQnkZCafQI1YOU9Faduttb02fxWp6WKq60RmVbnW3rW
 Ovi1AB+liEYEGBECAAYFAjwWI24ACgkQ9IyoG2moWHPQWQCdGAwIL50YjOPOsZVl
 623Rq5N193sAoIx+WM012DbKtxLlfiAYHjoyGvA9
 =SfCl
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.382. (R)}P:h 3/4W <davidxu@FreeBSD.org>

 pub   1024D/48F2BDAB 2006-07-13 [expires: 2009-07-12]
       Key fingerprint = 7182 434F 8809 A4AF 9AE8  F1B5 12F6 3390 48F2 BDAB
 uid                  David Xu <davidxu@freebsd.org>
 sub   4096g/ED7DB38A 2006-07-13 [expires: 2009-07-12]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQGiBES19gwRBAC+gBYGtS96dDvWP3Tu/F+YGwMHVF2uKC57wDuIUK6FIQXCsHcV
 LjPQEF6JE+fWZZMb2pb7YKtP6f1glNUxf4LIQlpTBqQGxYcOQHnu8pgUhxNe8kfE
 Pi9l+O0pAipQAnu7vj/3+4uxHgDXtfJphew9nKQWtCKdz13YVUhxZZV9zwCgyLb1
 D5sAWB+FAcF87qJd4jeEpO0D/1YvKgd2rV5yQ7jT2Xxl7dpq2u3vEeI15ZNxmMCh
 sS+4CxBpCcX1GSNVqxJDahBLwsSoJQaDoaV20DlJkQZYSNoW0tUtEA8Gy5cMPr/2
 oNIjPHRUU/R1i3rzA3k6so0QhJardwj/q8X3PQ/+N4vY9RDFxk8xTlaFL05Yipv2
 fGVXA/0fFL6EmFG+n/3pc+HkeExXUZytUg4pCLugdLdIpQ/PcYo7suvXuVourLX1
 6AhLSwc4lHjxl7+BlxmBYCdCJsjSKJi0A4CgoypcSP4sMvm3QNhfwIp+6vs0Cqxb
 3FLsZ8F/+iP/IAgm9DmUp0EZhzpLC530d0c8hwFEoNX85eNp+7QeRGF2aWQgWHUg
 PGRhdmlkeHVAZnJlZWJzZC5vcmc+iGMEExECACMFAkS19gwFCQWjmoAGCwkIBwMC
 BBUCCAMEFgIDAQIeAQIXgAAKCRAS9jOQSPK9q1GfAJ9pk1BZz2y4RyALL9iJbE8U
 mWKYUgCfcyq5jIrFHEUMEtdg5ejf+a9I+xW5BA0ERLX2KxAQAITsM+U08mC2ZU5v
 70C9i2HtI/kU++PdENYnwsvk0PVd224zFJ7llWa6HT6k/Wv3ZqvphJ1Ebg9f1ztv
 iQWbNUt+xGVqoaq+wQPFreHUpenF8EzjCtE9fRexC5uO9Q1w1GbBw9nw4kjD1dxV
 wnZM88ZJXjdz58DN02BP3u19ugTM/jTlZvWfv0jplQZ5DzL48hLKTQiPGM7OrryS
 VQsSp9Sk0xuYPz+whUqB/PVPYYz3N3rBZYAF4sjGD0r3FSFilzIlQYqyGYYKDOML
 slI9OJhbMx5SEGdkZHf7DX3SVe8RiX29ghn2/q8SwsMQgoow4v6XG2vDRlXOHvNG
 zHMgqYvsNKWV+KpBH1d7qj10och4uOhwou9dTtEpQAtrgj189SQGAWwi0Z4pMior
 /jloMpjngtLeTYdk3O6Xb9Btel/0vISbV9+fwfAcZFd+XnRrUVjzQm3ZgipT3Fyu
 ZCDDwKJnw0oMtyhiZbVAzgfNuflr92P/Hr6B2OajsLLqRdKMv1OTBluQrSWyA0r1
 ZxZtaO19cBXseEVIBSShUH8XP2mH8Jy0LPkCeq1CAUF1CUwZaf0dNj9IU9DOO66u
 4gqEckmDqLqbQ2nvO2eOkuUV7ZNK+6PrsVcUu6WssoHw8N95mU62t2aa0bh0JLdp
 /Jy4Y6FYnHN8/PXPtz6CCnFsR1XXAAMFD/9TRC9ojYbMrgBxPP/yd6wjGuQ0p58M
 fDn5atdzYFAljTIgGJGUG6LB+bKOkpitdrrWh/gc4Fq6ZQYXHttRx7ZE68I8X5eP
 uv4C02zi2CC3CXy68W1bng31Wndjx9vAfUVXJjLwL4+SvSk9a4zGDG5a6FMoIF5I
 4PDwRz1MeTIpnlAkhjjHkFlfC5a35O1Qd27/HUyf7hQgwjYr6plTBruK5nZR7zTl
 x+0oo3jVakRWq2r6FcvFYRTgAFapmshdLYVR7gUNQ3CeCuSvIb+F1r1u7m7ZNVev
 dkq3GdJOOijgwUBASYvj8u6c18VbfFoUCFSK8Dulq2ih+Kp0yv9x3GuA4mJvuv32
 tDjcPie+cvKgsbYujZmS73aiKTMx1qhrb9ydxWd2wE9zRyB7wOw/5aSJu1HOZ7LN
 Mjt3xyJayJnAxmyXjB/kVzsheDv/L+CLnqoYa5kkytZ1rEn5YZiAJE22Z/Wlo8ld
 D50ukvVMRRjblKjess5Z9nRqHZD77049NvunclgCq6rKv/ofuQwtaHpiRevkMjfK
 khY6vUHeqJyBdsyJowHkckGbTzmHn6SobNqM9rPNeL1jROuCjSJinjXAvzGWl+F2
 DLQEXxIt7Vh6FGGH7ayUqOVQZ2r0Yq38+2bw0eFEDOcVNd1I7YqKvhfK5UNmuQZL
 Y7rUo93+DfEEtohMBBgRAgAMBQJEtfYrBQkFo5qAAAoJEBL2M5BI8r2rM0oAniZj
 Ck9uJx9JEVrFY5rzx5zoYMz6AKDHL9jTBoVfHC5flmdVzuqJ9IpDCg==
 =jyox
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.383. Maksim Yevmenkin <emax@FreeBSD.org>

 pub  1024D/F050D2DD 2003-10-01 Maksim Yevmenkin <m_evmenkin@yahoo.com>
      Key fingerprint = 8F3F D359 E318 5641 8C81  34AD 791D 53F5 F050 D2DD

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.2.2 (FreeBSD)

 mQGiBD97XL8RBACC3CMLdwZY/RcLw4PM6h2KYj+cG7TNSfNWszZO5HdQYrd6HZKQ
 h0cL7cyW1Low8a2ZulxtEjM1SfofzDlhNaTYhyjlO4xBnJM13dMFchmM4j4qF0Mu
 al1MEeO3EbLntFsh/aDX2sOKEavz5id8eKmAZKez2O5Z27bymkFf4o2UbwCg841B
 WuuWHsy4O1zrac0WidkS3G0D/jeVbYA09gylZA1KSd3djHE55lQDQrUt3+2xWxjG
 Lg60WIqys/yxei6nVO7/Wr6Q1WISiX0bYXAxHCZZQrT6cuNtEBntPPa9PnXRewUx
 8xwVCBIuSLK5Kw2WZ2FMuQWTzfd4fwt8P9vghJlaV3h5Byw3e6/MdoDID9Jkg/ml
 f5FuA/9kZBwtE4zKJvx3Pv7EG6T0w82QA0SFtcFyRnNarUIfqyUsFXNkr8hoQT3Z
 J5haO/lW2HW70KMr26GxK61XcF8LQtfvphv9M+4yF3+DZSu1YxUM1Vs/q27EQhXa
 3Cs4kJkKdzW2xDbIbuD5ZJQqFAzWX7IiTTNXnEGZStPTQMYZLbQnTWFrc2ltIFll
 dm1lbmtpbiA8bV9ldm1lbmtpbkB5YWhvby5jb20+iFsEExECABsFAj97XL8GCwkI
 BwMCAxUCAwMWAgECHgECF4AACgkQeR1T9fBQ0t01FQCfUR367fJJ37Wl4HvZVBoF
 peBX9ZEAniaaK/D+n/JttkgY8jJf2ZvjF0SSuQENBD97XMIQBACPpJjDdDw42++u
 vPMW/R7Iwqdpgs22T/bzVlFxDGx2uD9xaoNKI03jkOyUWiFlHbuifMRhxTwO5Vyg
 nj91Y0fk8hdd9bjT0ee7lJuQ8PBqzb/uEVGFIC+56/ocFzuBANdN5fzEfxp5AA0o
 zAPotyGEmLLK8+3ApZmAbsnQEveOwwADBQP+KgIxPzWAxYSn/MFPK2QBEjHuCCsS
 JB+VOShc/QaSn/wFEKc8Brjpr1KeAEi7dFrK4Sa2Rn2+k9tRSJptxi1m3Hrr0J2z
 0JofnF6cKkvmIsCse5OGCK/LJmuWHuNVqYI2X9Q0am+soHEYsRaqB/BDLT5Mw0mE
 5NO6455cKEcyizmIRgQYEQIABgUCP3tcwgAKCRB5HVP18FDS3b1HAJ9ZjWomBkE4
 1vaMSXyIopmSQNVxSQCg3J+fBmk0yhD2A8CIfxhpSRJDwus=
 =wV5Z
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.384. Bjoern A. Zeeb <bz@FreeBSD.org>

 pub   1024D/3CCF1842 2007-02-20
       Key fingerprint = 1400 3F19 8FEF A3E7 7207  EE8D 2B58 B8F8 3CCF 1842
 uid                  Bjoern A. Zeeb <bz@zabbadoz.net>
 uid                  Bjoern A. Zeeb <bzeeb@zabbadoz.net>
 uid                  Bjoern A. Zeeb <bz@FreeBSD.org>
 uid                  Bjoern A. Zeeb <bzeeb-lists@lists.zabbadoz.net>
 sub   4096g/F36BDC5D 2007-02-20

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 12540 characters]
 B8U1cYUAoI3ftziD88BkkQf1aD7jpiQwlW7/
 =N1dt
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.385. Niclas Zeising <zeising@FreeBSD.org>

 pub   4096R/EA4BF1EC 2012-11-28 [expires: 2013-12-31]
       Key fingerprint = A8DE D126 D346 E9CB 6176  AECB 0401 4392 EA4B F1EC
 uid                  Niclas Zeising <zeising@daemonic.se>
 uid                  Niclas Zeising (FreeBSD Project) <zeising@freebsd.org>
 uid                  Niclas Zeising (Lysator ACS) <zeising@lysator.liu.se>
 sub   4096R/BB8B5551 2012-11-29 [expires: 2013-12-31]
 sub   4096R/B8D43CD2 2012-11-29 [expires: 2013-12-31]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 6996 characters]
 AGKnizAGgU22dFYDKXsM/kldl7QM7wQ=
 =vzHR
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.386. Alexey Zelkin <phantom@FreeBSD.org>

 pub  1024D/9196B7D9 2002-01-28 Alexey Zelkin <phantom@FreeBSD.org>
      Key fingerprint = 4465 F2A4 28C1 C2E4 BB95  1EA0 C70D 4964 9196 B7D9
 sub  1024g/E590ABA4 2002-01-28

 -----BEGIN PGP PUBLIC KEY BLOCK-----
 Version: GnuPG v1.0.6 (FreeBSD)
 Comment: For info see http://www.gnupg.org

 mQGiBDxVhBMRBAD20EH9hS3S3gy73E1s//vYS1yo4GmmvzUzMTJo4HH6OMFT/MVn
 B51RXK5YlQ1cau4MWt2sifpWsG2hmmmPtOIaC6Mn4X8cEXmzy6qW5m+3RUdXB8rM
 pFSEVVEGhE9Sq+pTI1wB4VUJ5mhQtvWVJKsmuyf1YRa/zrr2zbZTIXg5EwCggloA
 GdcoFNm7p+cW56HJI1jZTpcD/jUyc4KLeimo+6Fn3z6NZh64GS+JmmCDe7mlcK2S
 XNPVq3tXXP3ZUKdv3faoMAgI1hSi82/32GINDkhiLPc0Q2tQZRDYKvyY/swgJSnV
 1LV8jlpk2VsmsYOp9hW4SJLAQUaejpZe4CwHpOfJWbPkXE83nVygA0lnN89dfhIH
 JaB8A/9VottMl88+CLzqF3AzN72R5tFWnSFMWumaODis+UvLW0XAMP4AHhvux/FS
 Pl+m2YtilHhib6lfMYuGalN84H7VxOBxjc9L4qORV9jP4cWEYXpxx0DTmmtFfLae
 xGGTyYNM1RiqmScXMF28Am1I+WhnLTql8DVFWr8XoZUbususg7QjQWxleGV5IFpl
 bGtpbiA8cGhhbnRvbUBGcmVlQlNELm9yZz6IVwQTEQIAFwUCPFWEEwULBwoDBAMV
 AwIDFgIBAheAAAoJEMcNSWSRlrfZ9yQAn0bnLWBjo47dKrS82X1VvbuokkNXAJsH
 oANWk5PoOZzySJ7st8/IyaLBErkBDQQ8VYQXEAQA2cEOpYzl8L5y8TErdj1lfpHt
 gxm1QFETl8HvZGb/hTRWVhIcUhtOLA2uftk1oDHbnp+FPsJuFTxanCaCSQVdtMEE
 I1zK/Qy384FjS1B6L3yq84yTKn+Gp8SbMX3ZWT+dVmy88yJpmo/yFiiN9d2hYy1q
 fCUWhbAoWeD7sqSeGL8ABA0D/Au95rpaYunrMhu5nVdvZpTbNEIEDLOTS337GWy7
 n1E9RG72ujCLFg8tbEmjEUFYfCZ/cW+6+2/Nj7zoGH9xXH6bRTfSKXojdKgNkUvL
 SLynpmFpUlFKc4fzSxx5EkCxH/zog9X2CQjMvxHmSD1/x+LeD0v/5WMsLvIdj6Op
 0KmziEYEGBECAAYFAjxVhBcACgkQxw1JZJGWt9nbrQCcCvSJho7n1r4+1PGTlcep
 ABxplbsAn05jPrtZLjln7aKcavCp8FICJ2TY
 =GYHE
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.387. ^3`i<<U(CURyYENA) <sephe@FreeBSD.org>

 pub   2048R/3E51FB42 2005-10-21
       Key fingerprint = 5F47 3861 7ABA 8773 9E32  0474 5C33 841C 3E51 FB42
 uid                  Sepherosa Ziehau (freebsd) <sephe@freebsd.org>
 uid                  Sepherosa Ziehau (sephe) <sepherosa@gmail.com>
 sub   2048R/7AA31321 2005-10-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQELBENYRSgBCADNXKEOqPFvo//r9KnH2BzwJOB8h8TmU3zS4fogC1HjYQfZmFRa
 MCguECmq730ulxo2hnBSq9VyLfwnL0W1vz4b+2vMbcO5v9TkvnPlL3OW/mAHjrAL
 u01ui5VR1TKxD12q/KIEQ49+Ir8z4THImm4WgKaYo37xrNMAZc2BSCHK30I8lda0
 2DG8hzDtlCE79ZbqNAPmQYewflaU/ga0kzI/MftFeIZA7K26krXBLlOIY142ckTd
 iB3wrC2s0tqjQMxQODQTvWyxoTLi1TGMY/zbXdc9aoXnuX6qKZEzTh6P5NU8cRto
 BDlNVTV1eFYvFy6NNkNVE4Jj3yk96xWwlRJdAAYptC5TZXBoZXJvc2EgWmllaGF1
 IChzZXBoZSkgPHNlcGhlcm9zYUBnbWFpbC5jb20+iQE2BBMBAgAgBQJDWEUoAhsD
 BgsJCAcDAgQVAggDBBYCAwECHgECF4AACgkQXDOEHD5R+0LrJQf9FD6NUteiA76n
 GtJ3FRPUbEL/GbDtg/Ad/goeOzQIgw60QSan+nuDIcWz50XWcxfnjkThRQP0CWwk
 wkpGlOQt0DsPpFq2oSaR8yXSqfUAPuzSohmuArAeAs5aNlr6FYaXiOsvSmOM1pGX
 7JkTvajjxcXcSLSTqJS43xbI8s/+gEqTJbOErNeWxdK6uHHVhGmWexzu1wrUzjxT
 +4SFEEOsL/ScF2ITzByPZO6oBTrZveNKcC/nOBZAnkfjqqc7jRMggY4zGvFtFgsl
 dbHwMqkWihoJvhqspoopCeGwt7sY1NFsTUFNOZp073C7rIig1vgHEWnhevleq+cK
 ridbUbY+YbQuU2VwaGVyb3NhIFppZWhhdSAoZnJlZWJzZCkgPHNlcGhlQGZyZWVi
 c2Qub3JnPokBNgQTAQIAIAUCRgkgdwIbAwYLCQgHAwIEFQIIAwQWAgMBAh4BAheA
 AAoJEFwzhBw+UftCiZIH/iSSBM5Nv3G8Y2cS1ui1Xc5KpChSt6CAqKTOiYxwWQ/B
 U6clllym0NvzjUxiJm4JuV0N8sAy8nhhs79SNRfYfNnGeHXmLS58MPszhnEnhgZm
 yuZFQdZ15T9Axf5gLmDqA8TYpcUYxssSm8PcJqoCGnbk28okwbRuwTUm9T/w4TXt
 28w7SEXK0GFBG3ZlKPZh1er61CSwM7l/aoCkyFoNHAfGssFd/t0OCD8ugfQf9zvk
 JKXsm15vQAhMJrbcIhMGPWKoLN/z8bQTHSN4AP8nGM7gq3zUKZwL5jrzAUtHGqGs
 jtIBX9oPT5GLCaXZNotcLh40aS8qtemVthLqFS+pNu25AQsEQ1hFXQEIAMQRgCMl
 1tgeNZlj6fN+JC4LU4DC+9R28tnzEXWFGud5XQx/EzNRQVDuiDqQKPmc86Ps77dl
 7iJNTxapBs+Ki+3VOP11/ZUzHukER4iWZRXwfYtCE2tu2ht53WtYqoqwt40rsCOh
 uzC66FIiZ9Woj4omL5br0lKj8kVqS+OKfLt452bWg0mV39lokA3Q0xVfhlL3Nuj0
 S2yJcP0G8kesu/Ol1z85EK4GMlrOfZOaaz1r4f1u3FwE3Fo8anjvnUM9UC+ImJq0
 Z6gZwbBQ0tk55Z2Bs2sSyNp5cDnNyxa9HPOpvNqEE4bD4pMzsRMlEUhgM1kTOe1x
 AwBsQscqG1ovCnUABimJAR8EGAECAAkFAkNYRV0CGwwACgkQXDOEHD5R+0J/WAf/
 aALJbyEU1nSvyeVp0mP6U9xRFnXM1G4zQ3mrFyMvYcQ0a2A3gr8E+Ejl5Lpg/7HU
 t1UvLSqn00dqXuI+BIm/exDmpfLKXouBLVGtDcSQ/EQl6SV3mkJrvH8rDkCakCOG
 Fho5cl3Ge8YThQW1jdjbo+zXJfC9+k4ienh7DC2Yd8cwpcYRAKeKFOdveSjW+Ox0
 NFmZYc0F+XfKZLJ9d1SrFH5/ytQRAVvMbkLo1nb92ZXBrSbTN+tsLZrEbcmuuuZb
 pP+0i1PJDqfCRVpYFnlPZsNzZU5c5ihABZ79/uSScAyuxlhRdZAVHSDc6cRyzB5w
 AshLLfnD1BoaFl+lzNnL2Q==
 =F5Wg
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.388. Andrey Zonov <zont@FreeBSD.org>

 pub   2048R/E8A68B1C 2012-08-17 [expires: 2016-08-17]
       Key fingerprint = 3DFF AA2F C10A A979 2FB9  A764 F145 4BB6 E8A6 8B1C
 uid                  Andrey Zonov <zont@FreeBSD.org>
 uid                  Andrey Zonov <andrey@zonov.org>
 sub   2048R/57FC2BD3 2012-08-17 [expires: 2016-08-17]

 -----BEGIN PGP PUBLIC KEY BLOCK-----

[encoded data, 5280 characters]
 +Is2qlWoT4cI+VuljBbdprk4
 =ElkT
 -----END PGP PUBLIC KEY BLOCK-----

     --------------------------------------------------------------

  D.3.389. Takuya ASADA <syuu@FreeBSD.org>

 pub   2048R/43788F78 2012-11-21
       Key fingerprint = 31CE 242E 6F4F F24F EEF4  D9BB 0890 2C5F 4378 8F78
 uid                  Takuya ASADA <syuu@freebsd.org>
 sub   2048R/A87B0906 2012-11-21

 -----BEGIN PGP PUBLIC KEY BLOCK-----

 mQENBFCs6CQBCACri3OLkH5JVQCN2GylV62LuXCc7g2TfLf0q7XtmieJAwvtfxOl
 LdBDC8d/WAqUWVEW1eMWgvCJlgCPIFedG+GDBYPUFYsy1cUDALEi+QSS1Jozovs/
 b3Rk7TIW7Fu2F9KQ7ivlEtPS1bjQHmhrkHxOloapWUSrP2IdIfllxKAN3BGas2+j
 hjkmSPmSe0FQBIOyEp/RHf8bJ4LtRa+NACjOZWydLft54hcHNbS6/ubHtHlJjMjm
 V+fbLfYZvWGV1R+7gnuUAVu6bqgY6Bc60gwHs9wcITXCSDAZv9CP7r6mazo4MTV6
 auXYSiuec+rLNO10ndHuOqZPS0EKLExMJStNABEBAAG0H1Rha3V5YSBBU0FEQSA8
 c3l1dUBmcmVlYnNkLm9yZz6JATgEEwECACIFAlCs6CQCGwMGCwkIBwMCBhUIAgkK
 CwQWAgMBAh4BAheAAAoJEAiQLF9DeI94mZkIAKOPCkQcK/XENDyZR9iZroMpg60K
 TXNR72JIymRrBlUgJXOgxJJDETOx3GjTSXql7CLxkdun3oCmatskN0vneMHCs6/M
 3UP8UKwiA/6lk6cmg6vfXQ/IreqQyyV3inBN6fJMscsQrtB+pmw6CD8U1tiAkbBI
 ExlKGkQG7Qy5FzQ1meyUP9XvD9JhaDe+3sWPK60kcSpskrQgZ0y2yWgJxWOw4meS
 E0blTt+wyTFySbEraoY2ZoZP5y9vcMJoh0OKBzpTVi156RM87P4t3IjWNaDlGSJD
 uf5oVIhavgKYVPXu5+EmVTjLAFaNYc7C9lGGa7bOW1LlEt6EKcrReVaWPX25AQ0E
 UKzoJAEIAMWEiRDeAR5IkJmiRg0J1ORCbCFGbbENEqt2lahTAxuM5QAzjZ/StCos
 DeUydqy0/gYJ1zntyDGFNBEgBT4ZPcy1uFPMoTefG1RpYTBiw/gMTCcsFI8JzihY
 ShoAKJGw+jDBDhnYslAfrmYrOwyGykXep8SpmkigWAxnhZtyzbXCSgLcOGloj2AT
 uLo8DDIg7D3cxgX81U79UFsm3WZH2BaTi9dqhhtJanmmLpbxtJTDLZUEoR3iZwdE
 Myu1ziW5y+y3sfTVUgTH2sj1TNSF4vE1q2rr5qud+g5PlwA+05wNdaHLr3u7Y8qf
 218W0fDXw3mMgwD3ryXvHDkEwqOIHzUAEQEAAYkBHwQYAQIACQUCUKzoJAIbDAAK
 CRAIkCxfQ3iPeHVhB/45lUQo04TLDaXYX+vw5pSFGmdOUUz+gCRstZ7X+6yeYRhC
 XquBBmiByiHle0obuxk3IBNtNVmoKwyYjicYr9YdRAhjr/ei/MzORryj2RZUTHra
 fm7o4B6E8T3tlM2gXJ1erdwZVVX7M1Tuxs6fM4ZZLfRlVwwQxgsW2KViZwe26a/h
 vV9Y3EYheFjrlUcV4sTWAJ6VbPoWrsTm81iQWrEo1Hq2zV+FbtGDuoAiYiLCzPo8
 WP7/oZA62Ri5vOAdj1mD4tRWlDLwGDhwO/9eXdT6BwV808pVUi/6CwLWbCiRShRI
 xLcPUUM3uzQJpPwgiTPDxEvmS4lZR5m94smK/tE+
 =7PcP
 -----END PGP PUBLIC KEY BLOCK-----

                            FreeBSD Glossary

   This glossary contains terms and acronyms used within the FreeBSD
   community and documentation.

                                   A

   ACL

           DEGN"-L-: Access Control List

   ACPI

           DEGN"-L-: Advanced Configuration and Power Interface

   AMD

           DEGN"-L-: Automatic Mount Daemon

   AML

           DEGN"-L-: ACPI Machine Language

   API

           DEGN"-L-: Application Programming Interface

   APIC

           DEGN"-L-: Advanced Programmable Interrupt Controller

   APM

           DEGN"-L-: Advanced Power Management

   APOP

           DEGN"-L-: Authenticated Post Office Protocol

   ASL

           DEGN"-L-: ACPI Source Language

   ATA

           DEGN"-L-: Advanced Technology Attachment

   ATM

           DEGN"-L-: Asynchronous Transfer Mode

   ACPI Machine Language (AML)

           Pseudocode, interpreted by a virtual machine within an
           ACPI-compliant operating system, providing a layer between
           the underlying hardware and the documented interface
           presented to the OS.

   ACPI Source Language (ASL)

           The programming language AML is written in.

   Access Control List (ACL)

   Advanced Configuration and Power Interface (ACPI)

           A specification which provides an abstraction of the
           interface the hardware presents to the operating system,
           so that the operating system should need to know nothing
           about the underlying hardware to make the most of it. ACPI
           evolves and supercedes the functionality provided
           previously by APM, PNPBIOS and other technologies, and
           provides facilities for controlling power consumption,
           machine suspension, device enabling and disabling, etc.

   Application Programming Interface (API)

           A set of procedures, protocols and tools that specify the
           canonical interaction of one or more program parts; how,
           when and why they do work together, and what data they
           share or operate on.

   Advanced Power Management (APM)

   Advanced Programmable Interrupt Controller (APIC)

   Advanced Technology Attachment (ATA)

   Asynchronous Transfer Mode (ATM)

   Authenticated Post Office Protocol (APOP)

   Automatic Mount Daemon (AMD)

           A daemon that automatically mounts a filesystem when a
           file or directory within that filesystem is accessed.

                                   B

   BIND

           DEGN"-L-: Berkeley Internet Name Domain

   BIOS

           DEGN"-L-: Basic Input/Output System

   BSD

           DEGN"-L-: Berkeley Software Distribution

   Basic Input/Output System (BIOS)

           The definition of BIOS depends a bit on the context. Some
           people refer to it as the ROM chip with a basic set of
           routines to provide an interface between software and
           hardware. Others refer to it as the set of routines
           contained in the chip that help in bootstrapping the
           system. Some might also refer to it as the screen used to
           configure the boostrapping process. The BIOS is
           PC-specific but other systems have something similar.

   Berkeley Internet Name Domain (BIND)

           An implementation of the DNS protocols.

   Berkeley Software Distribution (BSD)

           ^3oNOTOYENN U.C. Berkeley -a-o Computer Systems Research
           Group(CSRG) ?i"O.iS:@YENLI(c)OS:i"}!B *S:i^1L-a-o AT&T's
           32V UNIX |W-oU!CFreeBSD <<hNOTOYENN CSRG
           -a-o^3oOCURss|aalYENIYENX"O!C

   Bikeshed Building

           A phenomenon whereby many people will give an opinion on
           an uncomplicated topic, whilst a complex topic receives
           little or no discussion. See the FAQ for the origin of the
           term.

                                   C

   CD

           DEGN"-L-: Carrier Detect

   CHAP

           DEGN"-L-: Challenge Handshake Authentication Protocol

   CLIP

           DEGN"-L-: Classical IP over ATM

   COFF

           DEGN"-L-: Common Object File Format

   CPU

           DEGN"-L-: Central Processing Unit

   CTS

           DEGN"-L-: Clear To Send

   CVS

           DEGN"-L-: Concurrent Versions System

   Carrier Detect (CD)

           An RS232C signal indicating that a carrier has been
           detected.

   Central Processing Unit (CPU)

           Also known as the processor. This is the brain of the
           computer where all calculations take place. There are a
           number of different architectures with different
           instruction sets. Among the more well-known are the
           Intel-x86 and derivatives, Sun SPARC, PowerPC, and Alpha.

   Challenge Handshake Authentication Protocol (CHAP)

   Classical IP over ATM (CLIP)

   Clear To Send (CTS)

           An RS232C signal giving the remote system permission to
           send data.

   Common Object File Format (COFF)

   Concurrent Versions System (CVS)

                                   D

   DAC

           DEGN"-L-: Discretionary Access Control

   DDB

           DEGN"-L-: Debugger

   DES

           DEGN"-L-: Data Encryption Standard

   DHCP

           DEGN"-L-: Dynamic Host Configuration Protocol

   DNS

           DEGN"-L-: Domain Name System

   DSDT

           DEGN"-L-: Differentiated System Description Table

   DSR

           DEGN"-L-: Data Set Ready

   DTR

           DEGN"-L-: Data Terminal Ready

   DVMRP

           DEGN"-L-: Distance-Vector Multicast Routing Protocol

   Discretionary Access Control (DAC)

   Data Encryption Standard (DES)

   Data Set Ready (DSR)

   Data Terminal Ready (DTR)

   Debugger (DDB)

   Differentiated System Description Table (DSDT)

   Distance-Vector Multicast Routing Protocol (DVMRP)

   Domain Name System (DNS)

           The system that converts humanly readable hostnames (i.e.,
           mail.example.net) to Internet addresses and vice versa.

   Dynamic Host Configuration Protocol (DHCP)

           A protocol that dynamically assigns IP addresses to a
           computer (host) when it requests one from the server. The
           address assignment is called a !S:lease!".

                                   E

   ECOFF

           DEGN"-L-: Extended COFF

   ELF

           DEGN"-L-: Executable and Linking Format

   ESP

           DEGN"-L-: Encapsulated Security Payload

   Encapsulated Security Payload (ESP)

   Executable and Linking Format (ELF)

   Extended COFF (ECOFF)

                                   F

   FADT

           DEGN"-L-: Fixed ACPI Description Table

   FAT

           DEGN"-L-: File Allocation Table

   FAT16

           DEGN"-L-: File Allocation Table (16-bit)

   FTP

           DEGN"-L-: File Transfer Protocol

   File Allocation Table (FAT)

   File Allocation Table (16-bit) (FAT16)

   File Transfer Protocol (FTP)

           A member of the family of high-level protocols implemented
           on top of TCP which can be used to transfer files over a
           TCP/IP network.

   Fixed ACPI Description Table (FADT)

                                   G

   GUI

           DEGN"-L-: Graphical User Interface

   Giant

           The name of a mutual exclusion mechanism (a sleep mutex)
           that protects a large set of kernel resources. Although a
           simple locking mechanism was adequate in the days where a
           machine might have only a few dozen processes, one
           networking card, and certainly only one processor, in
           current times it is an unacceptable performance
           bottleneck. FreeBSD developers are actively working to
           replace it with locks that protect individual resources,
           which will allow a much greater degree of parallelism for
           both single-processor and multi-processor machines.

   Graphical User Interface (GUI)

           A system where the user and computer interact with
           graphics.

                                   H

   HTML

           DEGN"-L-: HyperText Markup Language

   HUP

           DEGN"-L-: HangUp

   HangUp (HUP)

   HyperText Markup Language (HTML)

           The markup language used to create web pages.

                                   I

   I/O

           DEGN"-L-: Input/Output

   IASL

           DEGN"-L-: Intel!|s ASL compiler

   IMAP

           DEGN"-L-: Internet Message Access Protocol

   IP

           DEGN"-L-: Internet Protocol

   IPFW

           DEGN"-L-: IP Firewall

   IPP

           DEGN"-L-: Internet Printing Protocol

   IPv4

           DEGN"-L-: IP Version 4

   IPv6

           DEGN"-L-: IP Version 6

   ISP

           DEGN"-L-: Internet Service Provider

   IP Firewall (IPFW)

   IP Version 4 (IPv4)

           The IP protocol version 4, which uses 32 bits for
           addressing. This version is still the most widely used,
           but it is slowly being replaced with IPv6.

           YENtDEGN"-L-: IP Version 6.

   IP Version 6 (IPv6)

           The new IP protocol. Invented because the address space in
           IPv4 is running out. Uses 128 bits for addressing.

   Input/Output (I/O)

   Intel!|s ASL compiler (IASL)

           Intel!|s compiler for converting ASL into AML.

   Internet Message Access Protocol (IMAP)

   Internet Printing Protocol (IPP)

   Internet Protocol (IP)

           The packet transmitting protocol that is the basic
           protocol on the Internet. Originally developed at the U.S.
           Department of Defense and an extremly important part of
           the TCP/IP stack. Without the Internet Protocol, the
           Internet would not have become what it is today. For more
           information, see   RFC 791.

   Internet Service Provider (ISP)

           A company that provides access to the Internet.

                                   K

   KAME

           Japanese for !S:turtle!", the term KAME is used in
           computing circles to refer to the KAME Project, who work
           on an implementation of IPv6.

   KDC

           DEGN"-L-: Key Distribution Center

   KLD

           DEGN"-L-: Kernel ld(1)

   KSE

           DEGN"-L-: Kernel Scheduler Entities

   KVA

           DEGN"-L-: Kernel Virtual Address

   Kbps

           DEGN"-L-: Kilo Bits Per Second

   Kernel ld(1) (KLD)

   Kernel Scheduler Entities (KSE)

           A kernel-supported threading system. See the project home
           page for further details.

   Kernel Virtual Address (KVA)

   Key Distribution Center (KDC)

   Kilo Bits Per Second (Kbps)

           Used to measure bandwith (how much data can pass a given
           point at a specified amount of time). Alternates to the
           Kilo prefix include Mega, Giga, Tera, and so forth.

                                   L

   LAN

           DEGN"-L-: Local Area Network

   LOR

           DEGN"-L-: Lock Order Reversal

   LPD

           DEGN"-L-: Line Printer Daemon

   Line Printer Daemon (LPD)

   Local Area Network (LAN)

           A network used on a local area, e.g. office, home, or so
           forth.

   Lock Order Reversal (LOR)

           The FreeBSD kernel uses a number of resource locks to
           arbitrate contention for those resources. A run-time lock
           diagnostic system found in FreeBSD-CURRENT kernels (but
           removed for releases), called witness(4), detects the
           potential for deadlocks due to locking errors. (witness(4)
           is actually slightly conservative, so it is possible to
           get false positives.) A true positive report indicates
           that !S:if you were unlucky, a deadlock would have
           happened here!".

           True positive LORs tend to get fixed quickly, so check
           http://lists.FreeBSD.org/mailman/listinfo/freebsd-current
           and the   LORs Seen page before posting to the mailing
           lists.

                                   M

   MAC

           DEGN"-L-: Mandatory Access Control

   MADT

           DEGN"-L-: Multiple APIC Description Table

   MFC

           DEGN"-L-: Merge From Current

   MFP4

           DEGN"-L-: Merge From Perforce

   MFS

           DEGN"-L-: Merge From Stable

   MIT

           DEGN"-L-: Massachusetts Institute of Technology

   MLS

           DEGN"-L-: Multi-Level Security

   MOTD

           DEGN"-L-: Message Of The Day

   MTA

           DEGN"-L-: Mail Transfer Agent

   MUA

           DEGN"-L-: Mail User Agent

   Mail Transfer Agent (MTA)

           An application used to transfer email. An MTA has
           traditionally been part of the BSD base system. Today
           Sendmail is included in the base system, but there are
           many other MTAs, such as postfix, qmail and Exim.

   Mail User Agent (MUA)

           An application used by users to display and write email.

   Mandatory Access Control (MAC)

   Massachusetts Institute of Technology (MIT)

   Merge From Current (MFC)

           MFC NOTOCUR@OAY 1/4g!AYEN|YENN-aiCURF !S:Merged From
           -CURRENT!" !A^3o|r^2'.||b CVS logs CURCUR+-`"-L-!A
           YENH-aiYENU:^3oNOTO+-q -CURRENT CURCUR
           3/4a|XP:i"a:YENLCURACURa:(^3q+-`NOTO -STABLE)-a-o patch
           (c)IYEN\-`a!C

   Merge From Perforce (MFP4)

           To merge functionality or a patch from the Perforce
           repository to the -CURRENT branch.

           YENtDEGN"-L-: Perforce.

   Merge From Stable (MFS)

           In the normal course of FreeBSD development, a change will
           be committed to the -CURRENT branch for testing before
           being merged to -STABLE. On rare occasions, a change will
           go into -STABLE first and then be merged to -CURRENT.

           This term is also used when a patch is merged from -STABLE
           to a security branch.

           YENtDEGN"-L-: Merge From Current.

   Message Of The Day (MOTD)

           A message, usually shown on login, often used to
           distribute information to users of the system.

   Multi-Level Security (MLS)

   Multiple APIC Description Table (MADT)

                                   N

   NAT

           DEGN"-L-: Network Address Translation

   NDISulator

           DEGN"-L-: Project Evil

   NFS

           DEGN"-L-: Network File System

   NTFS

           DEGN"-L-: New Technology File System

   NTP

           DEGN"-L-: Network Time Protocol

   Network Address Translation (NAT)

   Network File System (NFS)

   New Technology File System (NTFS)

           A filesystem developed by Microsoft and available in its
           !S:New Technology!" operating systems, such as
           Windows 2000, Windows NT and Windows XP.

   Network Time Protocol (NTP)

                                   O

   OBE

           DEGN"-L-: Overtaken By Events

   ODMR

           DEGN"-L-: On-Demand Mail Relay

   OS

           DEGN"-L-: Operating System

   On-Demand Mail Relay (ODMR)

   Operating System (OS)

           A set of programs, libraries and tools that provide access
           to the hardware resources of a computer. Operating systems
           range today from simplistic designs that support only one
           program running at a time, accessing only one device to
           fully multi-user, multi-tasking and multi-process systems
           that can serve thousands of users simultaneously, each of
           them running dozens of different applications.

   Overtaken By Events (OBE)

           Indicates a suggested change (such as a Problem Report or
           a feature request) which is no longer relevant or
           applicable due to such things as later changes to FreeBSD,
           changes in networking standards, the affected hardware
           having since become obsolete, and so forth.

                                   P

   p4

           DEGN"-L-: Perforce

   PAE

           DEGN"-L-: Physical Address Extensions

   PAM

           DEGN"-L-: Pluggable Authentication Modules

   PAP

           DEGN"-L-: Password Authentication Protocol

   PC

           DEGN"-L-: Personal Computer

   PCNSFD

           DEGN"-L-: Personal Computer Network File System Daemon

   PDF

           DEGN"-L-: Portable Document Format

   PID

           DEGN"-L-: Process ID

   POLA

           DEGN"-L-: Principle Of Least Astonishment

   POP

           DEGN"-L-: Post Office Protocol

   POP3

           DEGN"-L-: Post Office Protocol Version 3

   PPD

           DEGN"-L-: PostScript Printer Description

   PPP

           DEGN"-L-: Point-to-Point Protocol

   PPPoA

           DEGN"-L-: PPP over ATM

   PPPoE

           DEGN"-L-: PPP over Ethernet

   PPP over ATM (PPPoA)

   PPP over Ethernet (PPPoE)

   PR

           DEGN"-L-: Problem Report

   PXE

           DEGN"-L-: Preboot eXecution Environment

   Password Authentication Protocol (PAP)

   Perforce

           A source code control product made by Perforce Software
           which is more advanced than CVS. Although not open source,
           it use is free of charge to open-source projects such as
           FreeBSD.

           Some FreeBSD developers use a Perforce repository as a
           staging area for code that is considered too experimental
           for the -CURRENT branch.

   Personal Computer (PC)

   Personal Computer Network File System Daemon (PCNFSD)

   Physical Address Extensions (PAE)

           A method of enabling access to up to 64 GB of RAM on
           systems which only physically have a 32-bit wide address
           space (and would therefore be limited to 4 GB without
           PAE).

   Pluggable Authentication Modules (PAM)

   Point-to-Point Protocol (PPP)

   Pointy Hat

           A mythical piece of headgear, much like a dunce cap,
           awarded to any FreeBSD committer who breaks the build,
           makes revision numbers go backwards, or creates any other
           kind of havoc in the source base. Any committer worth his
           or her salt will soon accumulate a large collection. The
           usage is (almost always?) humorous.

   Portable Document Format (PDF)

   Post Office Protocol (POP)

   Post Office Protocol Version 3 (POP3)

   PostScript Printer Description (PPD)

   Preboot eXecution Environment (PXE)

   Principle Of Least Astonishment (POLA)

           |b FreeBSD -a-ouo(R)i^1Lu{CURCUR!AYENo|o-a-oS:iAAU:'T<<
           *!A^3-L-CUR-L-,OAAy"IYENI-aI^2ss-oD.P"`iCUR-L- 3/4A!C
           A|"O"O>>!!GYYENo.N 1/2ODEGE /etc/defaults/rc.conf
           CURCUR-a-o"t^2I+-ODEGEP:P:S:C,!A 'NNOTO^1HI POLA
           `i<<h-a-o-oe-<<!CYENo|oP:}uoCURHu!A^3-L-,O|bDEGuYENX<<CURjS:iAAU:<<e!A
           YENyCURT<<a:NOTOS:_.|>>P POLA `i<<h|^3(c)O^1HI!C

   Problem Report (PR)

           A description of some kind of problem that has been found
           in either the FreeBSD source or documentation. See  
           Writing FreeBSD Problem Reports.

   Process ID (PID)

           A number, unique to a particular process on a system,
           which identifies it and allows actions to be taken against
           it.

   Project Evil

           The working title for the NDISulator, written by Bill
           Paul, who named it referring to how awful it is (from a
           philosophical standpoint) to need to have something like
           this in the first place. The NDISulator is a special
           compatibility module to allow Microsoft Windows(TM) NDIS
           miniport network drivers to be used with FreeBSD/i386.
           This is usually the only way to use cards where the driver
           is closed-source. See src/sys/compat/ndis/subr_ndis.c.

                                   R

   RA

           DEGN"-L-: Router Advertisement

   RAID

           DEGN"-L-: Redundant Array of Inexpensive Disks

   RAM

           DEGN"-L-: Random Access Memory

   RD

           DEGN"-L-: Received Data

   RFC

           DEGN"-L-: Request For Comments

   RISC

           DEGN"-L-: Reduced Instruction Set Computer

   RPC

           DEGN"-L-: Remote Procedure Call

   RS232C

           DEGN"-L-: Recommended Standard 232C

   RTS

           DEGN"-L-: Request To Send

   Random Access Memory (RAM)

   Received Data (RD)

   Recommended Standard 232C (RS232C)

           A standard for communications between serial devices.

   Reduced Instruction Set Computer (RISC)

   Redundant Array of Inexpensive Disks (RAID)

   Remote Procedure Call (RPC)

   repocopy

           DEGN"-L-: Repository Copy

   Repository Copy

           repocopy(!S:repository copy!" -a-oAY 1/4g) 'NNOTO-a
           1/2+-u+-q CVS repository CURCUR 1/2AE>>sAE(R) *!C

           YCUR-L-YENI repocopy -a-oCURe|!!A"-o>>oYn|b repository
           CUR-o 1/2AE>>s!B^2 3/4DEGEAE(R) *-a-o,U:!A committer
           'NYEN^2P:.DEGo|ae cvs add "OS:aAE(R) *(c)n"`i.s|`i,m!A
           "AYENBAUnDEGo|ae cvs rm "OS:RDEG-L-AAAE!C

           eeA?-a-o^3o-oO/CURe|!-a-o-EAI|b(c)o!A,OAE-a-oCURS:<<eNOTUAo:NOTo:?y
           (CURn|p|b CVS logs
           CURCUR-a-oNOTUAo:P:uYENO/)"ACUR-L-.|AHCURS:|O
           1/2AE>>s"`i.s|aCUReYENh!C |O FreeBSD
           p^1-oCURCUR>>{NOTDEG^3o"C,
           3/4uYENvDEGO?y^3-L-NOTONOTU.i|^3YENI-a-o!A
           (c)OYENH.|,g+-`+-A:YENI repository copy -a-oCURe|!!C
           ^3oCUR]'NNOTONOTDEG|o repository -oTH^2zu.|-a 1/2+-u|b
           repository CUR-o 1/2AE>>sAE(R) *-a-oCURe|!!A |O<<D+-A:"u
           cvs(1) u{|!"OP:i|ae cvs add!B cvs rmCURS:Ath-a-oDEGES:@!C

   Request For Comments (RFC)

           A set of documents defining Internet standards, protocols,
           and so forth. See www.rfc-editor.org.

           Also used as a general term when someone has a suggested
           change and wants feedback.

   Request To Send (RTS)

   Router Advertisement (RA)

                                   S

   SCI

           DEGN"-L-: System Control Interrupt

   SCSI

           DEGN"-L-: Small Computer System Interface

   SG

           DEGN"-L-: Signal Ground

   SMB

           DEGN"-L-: Server Message Block

   SMP

           DEGN"-L-: Symmetric MultiProcessor

   SMTP

           DEGN"-L-: Simple Mail Transfer Protocol

   SMTP AUTH

           DEGN"-L-: SMTP Authentication

   SSH

           DEGN"-L-: Secure Shell

   STR

           DEGN"-L-: Suspend To RAM

   SMTP Authentication (SMTP AUTH)

   Server Message Block (SMB)

   Signal Ground (SG)

           An RS232 pin or wire that is the ground reference for the
           signal.

   Simple Mail Transfer Protocol (SMTP)

   Secure Shell (SSH)

   Small Computer System Interface (SCSI)

   Suspend To RAM (STR)

   Symmetric MultiProcessor (SMP)

   System Control Interrupt (SCI)

                                   T

   TCP

           DEGN"-L-: Transmission Control Protocol

   TCP/IP

           DEGN"-L-: Transmission Control Protocol/Internet Protocol

   TD

           DEGN"-L-: Transmitted Data

   TFTP

           DEGN"-L-: Trivial FTP

   TGT

           DEGN"-L-: Ticket-Granting Ticket

   TSC

           DEGN"-L-: Time Stamp Counter

   Ticket-Granting Ticket (TGT)

   Time Stamp Counter (TSC)

           A profiling counter internal to modern Pentium processors
           that counts core frequency clock ticks.

   Transmission Control Protocol (TCP)

           A protocol that sits on top of (e.g.) the IP protocol and
           guarantees that packets are delivered in a reliable,
           ordered, fashion.

   Transmission Control Protocol/Internet Protocol (TCP/IP)

           The term for the combination of the TCP protocol running
           over the IP protocol. Much of the Internet runs over
           TCP/IP.

   Transmitted Data (TD)

   Trivial FTP (TFTP)

                                   U

   UDP

           DEGN"-L-: User Datagram Protocol

   UFS1

           DEGN"-L-: Unix File System Version 1

   UFS2

           DEGN"-L-: Unix File System Version 2

   UID

           DEGN"-L-: User ID

   URL

           DEGN"-L-: Uniform Resource Locator

   USB

           DEGN"-L-: Universal Serial Bus

   Uniform Resource Locator (URL)

   Unix File System Version 1 (UFS1)

   Unix File System Version 2 (UFS2)

   Universal Serial Bus (USB)

   User ID (UID)

           A unique number assigned to each user of a computer, by
           which the resources and permissions assigned to that user
           can be identified.

   User Datagram Protocol (UDP)

                                   V

   VPN

           DEGN"-L-: Virtual Private Network

   Virtual Private Network (VPN)

     --------------------------------------------------------------

                            -a(c)YEN>>DEGO?y

   This book is the combined work of hundreds of contributors to
   !S:The FreeBSD Documentation Project!". The text is authored in
   SGML according to the DocBook DTD and is formatted from SGML into
   many different presentation formats using Jade, an open source
   DSSSL engine. Norm Walsh's DSSSL stylesheets were used with an
   additional customization layer to provide the presentation
   instructions for Jade. The printed version of this document would
   not be possible without Donald Knuth's TeX typesetting language,
   Leslie Lamport's LaTeX, or Sebastian Rahtz's JadeTeX macro
   package.

  -a`

[1]  ^3o'NNOTO i386 -a-o.N,q!C -a`.NS:Y"I+-zCUR-L-NOTO|b Intel -a-o 386 ^3B^2z    
     3/4^1CURWDEGo|ae FreeBSD !ACUR@ 1/4ENOTOi386!C                               
     ^3oCUR-L-NOTO<<u:S:A-a-o^3B^2z                                               
     3/4^1-a-o<<NOT,^1!A^3o,IAAaYENU:-a-oNOTOS:A^3B^2z 3/4^1-a-o!S:NOT[-oc!"      
[2]  ^3o"C,+-ODEGE-a-o script NOTO|bP:} 3/4-:-a-o(R)EO FreeBSD                    
     .||UDEGEDEGo|ae-a-ou{|!!C                                                    
     YENLIYENDn-a-oYEN\-`aNOTO+-N(c)O|^3,ODEGo|ae-a-o-aF|e^3](c)w|n!A             
     "A+-N+-z^3](c)w|"I'-oDEGo|ae-a-o-aADEGE+-ODEGE!C                             
[3]  |b syscons(4)!Batkbd(4)!Bvidcontrol(1)!BYENHCURI kbdcontrol(1)uYEN manual    
     page CURCUR!A^1i(c)o FreeBSD -a-o console CURIAa:                            
     1/2LAAXDEGEu{|!|^3,O^2O-a-oS:TH^3N>>!(c)u!C S:UI|b^3o,ICUR-L-DEGQ 1/2        
     *^2O,`!A |^3?^3 1/2`i-a-oAA-a-aIAH(R)EYENiYENH|b manual pages                
     CURCURNOTd"`iAo:(c)o^1BS:@CURe|!-a-oS:o,O^2OYENBS:^1 3/4a-a-o,NA:A!C         
[4]  CUR-L-S:^1YENthYEN? 1/2T!X!XAUNOTO|^3CURO: 1/4AE-aF|eCUR-L--`a^3QCURCURA_!C  
     "O|p|^3Ou{S:C,YEN?|b+-q-oo,oCURW-a-oS:O-a-o^1q,-L-AA-aCUR@OAE(R) *!A         
     |O"-o^3!^1q,-L-|]NOTDEGNOTY"C,^2zYENN^3sCUR-L-"`i ( 3/4-: 3/4^1^3QAo:+-      
     1/4!A(c)INOTO-oo,oA:e+- 1/4CURF)!A                                           
     "-o^3oOu{S:C,S:UI'N>>!YENLNOTOCUR@O!S:CUR-L--`aCURCURA_-a-o!"u{S:C,!C        
     ^3q+-`|b,g^1L"aCURAA:AYEN-aYENkCURS:<<a^3oOu{S:C,.|^1O(R)E!C                 
     .iuoYENI^1O(R)E-a-o(R)EO^3oOu{S:C,'N.|^3Qu^2S:o+- 1/4CURF!C                  
[5]  A:P:uu!GKarbon14 NOTO|VP:qA,^1I^3nAAe!AYENH<<eYENs                           
     Kontour!AS:o|CURS:<<e-oUNOTDEG Killustrator!C                                
[6]  A:P:uu!GS:AYEN^2P:.^3z^1L sane-frontends (c)I xsane "O+- 1/2'y               
[7]  A:P:uu!G>>OAEWYEN?AAeCURCURCURaa"IYENI-aINOTDEG zh-TW!C                      
[8]  The auto-tuning algorithm sets maxusers equal to the amount of memory in the 
     system, with a minimum of 32, and a maximum of 384.                          
[9]  Well..DEG-L-<<D+-z^3s+-u multiple terminals!A^3o-oO/+-!-apS:UI.||b uU 24     
     ^3^1 A?"`i!C                                                                 
[10] UID/GID ^3ICURjYENi"IYENI|U: 4294967295!A|y^3o 1/4E-a-o ID                   
     YENi-`a.|^1iCURwDEG^2^3] 1/2d^3o-a-o^3nAAe^3y|"A:Y<<DEGYAD!C                 
[11] Under FreeBSD the standard login password may be up to 128 characters in     
     length.                                                                      
[12] FreeBSD 6.0(S:t) CURS:<<a'NCUR-L->>Y^3o"BAEJ!C                               
[13] Other conditions may produce different failures. For instance, the file may  
     not be owned by the user attempting to relabel the object, the object may    
     not exist or may be read only. A mandatory policy will not allow the process 
     to relabel the file, maybe because of a property of the file, a property of  
     the process, or a property of the proposed new label value. For example: a   
     user running at low integrity tries to change the label of a high integrity  
     file. Or perhaps a user running at low integrity tries to change the label   
     of a low integrity file to a high integrity label.                           
[14] Due to a bug the security.mac.portacl.enabled sysctl variable will not work  
     on FreeBSD 5.2.1 or previous releases.                                       
[15] A:P:uu!GAo:uM|^3"C,^3]^3AE"S|^3!y-oD-CURu!z!A"O|p USB AH"-oD-!A              
     CUR-L-^1L|b|^1CUR'S:a Disk                                                   
     A:P:NOTDEG!y-oD-CURu,E,m!z!C|^1YEN~!ANOTDEGCURe<<KDEG_"-L-!A                 
     <<aCURaa(c)O|^3-a-o Disk ^3-L-A:P:NOTDEG!y-oI-oD-!z!C                        
[16] A:P:uu!GDEGo(c)oNOTU|P-a-o^2zYENN!A ^2{|b BSD partition +-`-oUNOTDEG BSD     
     label!A(c)IA^2-oU label!C                                                    
[17] A:P:uu!G|N^1e>>!S:UNOTYCUR-L-A'^3oYENy<<u:-a-oNOTOCURDEG>>o!H`iCURaaNOTO     
     sysinstall Label editor favors the e partition for non-root, non-swap        
     partitions.                                                                  
[18] A:P:uu!G|p-aG+-z|U(c)l|U:^2 *^3-L-CUR-L-YEN'-oa+-N^3oO-oI-oD-YENI(c)o        
     FreeBSD                                                                      
     CURS:YEN~-a-oS:@.~"t^2I!A"-oYENiYENH-oaNOTOO|n^2zYENN!CCUR-L-^1L'N-oa|p|^1!A 
     YENI slice  1/4O|!CUR]"SCURDEG>>oAa^3B'NNOTOCURF:-)!C                        
[19] A:P:uu!Gda NOTO direct access (disk) -a-oAY 1/4g!F ad NOTO ata disk -a-oAY   
     1/4g!C                                                                       
[20] A:P:uu!GS:U^1i^3oYENy-a-o.N<<a:"SCURDEG>>o<<HCURss!A`iCURaaNOTO IBM's OS/2   
     however, will !S:appropriate!" any partition it finds which it does not      
     understand.                                                                  
[21] A:P:uu!G`iCURaa^3o,INOTOYENI!u(c)M!v!A|ynuo/^1e>>U"IYENICURe|!|O(c)w!C       
     "O|pYENI RAID-0 'NCUR-L-.| 1/4WYEN[A(c)w<< * :)!C                            
[22] A:P:uu!G"O|p<<o: F1 YENiYENHP:iCURJ+-+-"iYENd BIOS CURS:Ath-a-o,eDEGT!C      
[23] For tips on how to select a secure passphrase that is easy to remember, see  
     the Diceware Passphrase website.                                             
[24] 1/2D--a`.N!A+-N fstab -a-o swap file                                         
     "-o|aeuu,NDEG_"O!A^3q+-`-aiYENU:!G+-z+-oYENIS:O-a-oCURe-ak"O<<<<O/           
     swap!C,O+-! 1/2D-DEGN|O uU 11.14 ,`!C                                        
[25] RAID stands for Redundant Array of Inexpensive Disks and offers various      
     forms of fault tolerance, though the latter term is somewhat misleading: it  
     provides no redundancy.                                                      
[26] uM|O!A^3oCUR]CUR-L-CUR@(c)wNOTOYEN? 1/2T!AS:UICUR-L-YENi-`aYENA>>.CURa:'(c)  
     FreeBSD (c)oCURe-a-o|U-oO/uo|ae-a(c)YEN>>!A                                  
     3/4"-oTH"COuo|ae-a(c)uoS:GCURS:<<a!A^3-L-CUR'.|<<uA:oCURa:'(c)               
     1/4AE|~CURS:CUR[!C Y+-yAA,N FreeBSD                                          
     YENO/<<e^1i(c)oAA-a(c)-a-oCURa:'(c)NOTFu|^2O,`!A 1/2D-DEGN 3/4\              
     http://www.FreeBSD.org/security/ !C                                          

     --------------------------------------------------------------

YEN>>CURaaCURI"a:YENLCURaaYENo!AYENiYENN|^1CURU,u:!Gftp://ftp.FreeBSD.org/pub/FreeBSD/doc/!C

        Y|^3 FreeBSD CURe+--oADEGY!A 1/2D-YENy 3/4\AA-a FreeBSD
         NOTUAo:CURaaYENo!A|pCUR-L--`a,N"M-a-o,U:!A|ANOT-c-,ss
                       <questions@FreeBSD.org>!C
  Ao:(c)oYEN>>CURaaYENo-a-oDEGYAD!A 1/2D-NOT-c-,ss <doc@FreeBSD.org>!C
