diff --git a/handbook/install.sgml b/handbook/install.sgml index 8d28e1e0e7..5d46a99a9d 100644 --- a/handbook/install.sgml +++ b/handbook/install.sgml @@ -1,858 +1,841 @@ - + Installing FreeBSD

So, you would like to try out FreeBSD on your system? This section is a quick-start guide for what you need to do. FreeBSD can be installed from a variety of media including CD-ROM, floppy disk, magnetic tape, an MS-DOS partition and, if you have a network connection, via anonymous ftp or NFS. Regardless of the installation media you choose, you can - get started by creating the installation disk + get started by creating the installation disks as described below. Booting your computer into the FreeBSD installer, even if you aren't planning on installing FreeBSD right away, will provide important information about compatibility between FreeBSD and your hardware which may, in turn, dictate which installation options are even possible. It can also provide early clues to any compatibility problems which could prevent FreeBSD running on your system at all. If you plan on installing via anonymous FTP then this installation floppy is all that you will need to download and create - the installation program itself will handle any further required downloading directly (using an ethernet connection, a modem and ppp dialup #, etc). For more information on obtaining the latest FreeBSD distributions, please see in the Appendix. So, to get the show on the road, follow these steps:

Review the section of this installation guide to be sure that your hardware is supported by FreeBSD. It may be helpful to make a list of any special cards you have installed, such as SCSI controllers, Ethernet adapters or sound cards. This list should include relevant configuration parameters such as interrupts (IRQ) and IO port addresses.

If you're installing FreeBSD from CDROM media then you have several different installation options:

If the CD has been mastered with El Torrito boot support and your system supports direct booting from CDROM (and many older systems do not), simply insert the CD into the drive and boot directly from it.

If you're running DOS and have the proper drivers to access your CD, run the install.bat script provided on the CD. This will attempt to boot into the FreeBSD installation straight from DOS (note: You must do this from actual DOS and not a Windows DOS box ). If you also want to install FreeBSD from your DOS partition (perhaps because your CDROM drive is completely unsupported by FreeBSD) then run the setup program first to copy the appropriate files from the CD to your DOS partition, afterwards running install.

If either of the two proceeding methods work then you can simply skip the rest of this section, otherwise your final option - is to create a boot floppy from the floppies\boot.flp - image - proceed to step 4 for instructions on how to do + is to create a set of boot floppies from the + floppies\kern.flp and floppies\mfsroot.flp + images - proceed to step 4 for instructions on how to do this.

-

If you don't have a CDROM distribution then simply download the file to your hard - drive, being sure to tell your browser to - save rather than display the file. - Note: This disk image can only be used with - 1.44 megabyte 3.5 inch floppy disks.

 +

If you don't have a CDROM distribution then simply read the to find out what files + you need to download first. -

Make the installation boot disk from the image file: +

Make the installation boot disks from the image files:

If you are using MS-DOS then download or get it from tools\fdimage.exe on the CDROM and then run it like so: -E:\> tools\fdimage floppies\boot.flp a: +E:\> tools\fdimage floppies\kern.flp a: The fdimage program will format the A: drive and then copy the - boot.flp image onto it (assuming that you're at the top + kern.flp image onto it (assuming that you're at the top level of a FreeBSD distribution and the floppy images live in the floppies subdirectory, as is typically the case). + Do the same for the mfsroot.flp image and you're set.

-

If you are using a UNIX system to create the floppy image: +

If you are using a UNIX system to create the floppy images: -% dd if=boot.flp of=disk_device +% dd if=kern.flp of=disk_device where disk_device is the /dev entry for the floppy drive. On FreeBSD systems, this is /dev/rfd0 for the A: drive and /dev/rfd1 for the B: drive.

-

With the installation disk in the A: drive, reboot your - computer. You should get a boot prompt something like this: - ->> FreeBSD BOOT ... -Usage: [[[0:][wd](0,a)]/kernel][-abcCdhrsv] -Use 1:sd(0,a)kernel to boot sd0 if it is BIOS drive 1 -Use ? for file list or press Enter for defaults -Boot: - - If you do not type anything, FreeBSD will automatically boot +

With the kern.flp disk in the A: drive, reboot your + computer. The next request you should get is for the mfsroot.flp + image, after which the installation will proceed normally. + + If you do not type anything at the boot prompt which + appears during this process, FreeBSD will automatically boot with its default configuration after a delay of about five seconds. As FreeBSD boots, it probes your computer to determine what hardware is installed. The results of this probing is displayed on the screen.

When the booting process is finished, The main FreeBSD installation menu will be displayed.

If something goes wrong...

Due to limitations of the PC architecture, it is impossible for probing to be 100 percent reliable. In the event that your hardware is incorrectly identified, or that the probing causes your computer to lock up, first check the section of this installation guide to be sure that your hardware is indeed supported by FreeBSD.

If your hardware is supported, reset the computer and when - the Boot: prompt comes up, type -c. This puts - FreeBSD into a configuration mode where you can supply + the visual kernel configuration choice is presented, take it. + This puts FreeBSD into a configuration mode where you can supply hints about your hardware. The FreeBSD kernel on the installation disk 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 use the - -c option at boot to tell FreeBSD where things are. + confiration editor to tell FreeBSD where things are.

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. Do not disable any device you will need during installation, - such as your screen (sc0). + such as your screen (sc0). If the installation wedges + or fails mysteriously after leaving the configuration editor, + you've probably removed or changed something you shouldn't have. + Simply reboot and try again.

In the configuration mode, you can: List the device drivers installed in the kernel. Disable device drivers for hardware not present in your system. Change the IRQ, DRQ, and IO port addresses used by a device driver. -

While at the config> prompt, type - help for more information on the available - commands. After adjusting the kernel to match how you have - your hardware configured, type quit at the - config> prompt to continue booting with the new - settings. +

After adjusting the kernel to match how you have + your hardware configured, type Q to continue booting + with the new settings. After FreeBSD has been installed, changes made in the configuration mode will be permanent so you do not have to reconfigure every time you boot. Even so, it is likely that you will want to build a custom kernel to optimize the performance of your system. See for more information on creating custom kernels. Supported Configurations

FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus based PC's, ranging from 386sx to Pentium class machines (though the 386sx is not recommended). Support for generic IDE or ESDI drive configurations, various SCSI controller, network and serial cards is also provided. A minimum of four megabytes of RAM is required to run FreeBSD. To run the X Window System, eight megabytes of RAM is the recommended minimum. Following is a list of all disk controllers and Ethernet cards currently known to work with FreeBSD. Other configurations may very well work, and we have simply not received any indication of this. Disk Controllers

WD1003 (any generic MFM/RLL) WD1007 (any generic IDE/ESDI) IDE ATA Adaptec 1505 ISA SCSI controller Adaptec 152x series ISA SCSI controllers Adaptec 1535 ISA SCSI controllers Adaptec 154x series ISA SCSI controllers Adaptec 174x series EISA SCSI controller in standard and enhanced mode. Adaptec 274x/284x/2940/2940U/3940 (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers Adaptec AIC7850 on-board SCSI controllers Adaptec AIC-6360 based boards, which includes the AHA-152x and SoundBlaster SCSI cards. Note: You cannot boot from the SoundBlaster cards as they have no on-board BIOS, which is necessary for mapping the boot device into the system BIOS I/O vectors. They are perfectly usable for external tapes, CDROMs, etc, however. The same goes for any other AIC-6x60 based card without a boot ROM. Some systems DO have a boot ROM, which is generally indicated by some sort of message when the system is first powered up or reset. Check your system/board documentation for more details. Buslogic 545S & 545c Note: that Buslogic was formerly known as "Bustek". Buslogic 445S/445c VLB SCSI controller Buslogic 742A/747S/747c EISA SCSI controller. Buslogic 946c PCI SCSI controller Buslogic 956c PCI SCSI controller NCR 53C810/53C815/53C825/53C860/53C875 PCI SCSI controller. NCR5380/NCR53400 (``ProAudio Spectrum'') SCSI controller. DTC 3290 EISA SCSI controller in 1542 emulation mode. UltraStor 14F/24F/34F SCSI controllers. Seagate ST01/02 SCSI controllers. Future Domain 8xx/950 series SCSI controllers. WD7000 SCSI controllers. With all supported SCSI controllers, full support is provided for SCSI-I & SCSI-II peripherals, including Disks, tape drives (including DAT) and CD ROM drives. The following CD-ROM type systems are supported at this time: SoundBlaster SCSI and ProAudio Spectrum SCSI (cd) Mitsumi (all models) proprietary interface (mcd) Matsushita/Panasonic (Creative) CR-562/CR-563 proprietary interface (matcd) Sony proprietary interface (scd) ATAPI IDE interface (experimental and should be considered ALPHA quality!) (wcd) Ethernet cards

Allied-Telesis AT1700 and RE2000 cards SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT based clones. SMC Elite Ultra and 9432TX based cards are also supported. DEC EtherWORKS III NICs (DE203, DE204, and DE205) DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) DEC DC21040/DC21041/DC21140 based NICs: ASUS PCI-L101-TB Accton ENI1203 Cogent EM960PCI Compex CPXPCI/32C D-Link DE-530 DEC DE435 Danpex EN-9400P3 JCIS Condor JC1260 Kingston KNE100TX Linksys EtherPCI Mylex LNP101 SMC EtherPower 10/100 (Model 9332) SMC EtherPower (Model 8432) SMC EtherPower (2) Zynx ZX314 Zynx ZX342 DEC FDDI (DEFPA/DEFEA) NICs Fujitsu FMV-181 and FMV-182 Fujitsu MB86960A/MB86965A Intel EtherExpress Intel EtherExpress Pro/100B 100Mbit. Isolan AT 4141-0 (16 bit) Isolink 4110 (8 bit) Lucent WaveLAN wireless networking interface. Novell NE1000, NE2000, and NE2100 ethernet interface. 3Com 3C501 cards 3Com 3C503 Etherlink II 3Com 3c505 Etherlink/+ 3Com 3C507 Etherlink 16/TP 3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III 3Com 3C590, 3C595 Etherlink III 3Com 3C90x cards. HP PC Lan Plus (27247B and 27252A) Toshiba ethernet cards PCMCIA ethernet cards from IBM and National Semiconductor are also supported.

Note: FreeBSD does not currently support PnP (plug-n-play) features present on some ethernet cards. If your card has PnP and is giving you problems, try disabling its PnP features. Miscellaneous devices

AST 4 port serial card using shared IRQ. ARNET 8 port serial card using shared IRQ. BOCA IOAT66 6 port serial card using shared IRQ. BOCA 2016 16 port serial card using shared IRQ. Cyclades Cyclom-y Serial Board. STB 4 port card using shared IRQ. SDL Communications Riscom/8 Serial Board. SDL Communications RISCom/N2 and N2pci sync serial cards. Digiboard Sync/570i high-speed sync serial card. Decision-Computer Intl. "Eight-Serial" 8 port serial cards using shared IRQ. Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound, Gravis UltraSound MAX and Roland MPU-401 sound cards. Matrox Meteor video frame grabber. Creative Labs Video spigot frame grabber. Omnimedia Talisman frame grabber. Brooktree BT848 chip based frame grabbers. X-10 power controllers. PC joystick and speaker. FreeBSD does not currently support IBM's microchannel (MCA) bus. Preparing for the Installation

There are a number of different methods by which FreeBSD can be installed. The following describes what preparation needs to be done for each type. Before installing from CDROM

If your CDROM is of an unsupported type, then please skip to . There is not a lot of preparatory work that needs to be done to successfully install from one of Walnut Creek's FreeBSD CDROMs (other CDROM distributions may work as well, though we cannot say for certain as we have no hand or say in how they are created). You can either boot into the CD installation directly from DOS using Walnut Creek's - supplied ``install.bat'' batch file or you can make a boot floppy with - the ``makeflp.bat'' command. [NOTE: If you are running - FreeBSD 2.1-RELEASE and have an IDE CDROM, use the - inst_ide.bat or atapiflp.bat batch files instead]. + supplied ``install.bat'' batch file or you can make boot floppies with + the ``makeflp.bat'' command. For the easiest interface of all (from DOS), type ``view''. This will bring up a DOS menu utility that leads you through all the available options. If you are creating the boot floppy from a UNIX machine, see for examples. of how to create the boot floppy. + guide"> for examples. of how to create the boot floppies. Once you have booted from DOS or floppy, you should then be able to select CDROM as the media type in the Media menu and load the entire distribution from CDROM. No other types of installation media should be required. After your system is fully installed and you have rebooted from the hard disk, you can mount the CDROM at any time by typing: mount /cdrom Before removing the CD again, also note that it is necessary to first type: umount /cdrom. Do not just remove it from the drive! Special note: Before invoking the installation, be sure that the CDROM is in the drive so that the install probe can find it. This is also true if you wish the CDROM to be added to the default system configuration automatically during the install (whether or not you actually use it as the installation media). Finally, if you would like people to be able to FTP install FreeBSD directly from the CDROM in your machine, you will find it quite easy. After the machine is fully installed, you simply need to add the following line to the password file (using the vipw command): ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent Anyone with network connectivity to your machine (and permission to log into it) can now chose a Media type of FTP and type in: ftp://your machine after picking ``Other'' in the ftp sites menu. Before installing from Floppy

If you must install from floppy disks, either due to unsupported hardware or simply because you enjoy doing things the hard way, you must first prepare some floppies for the install. You will need, at minimum, as many 1.44MB or 1.2MB floppies as it takes to hold all files in the bin (binary distribution) directory. If you are preparing these floppies under DOS, then THESE floppies *must* be formatted using the MS-DOS FORMAT command. If you are using Windows, use the Windows File Manager format command. Do not trust Factory Preformatted floppies! Format them again yourself, just to make sure. Many problems reported by our users in the past have resulted from the use of improperly formatted media, which is why I am taking such special care to mention it here! If you are creating the floppies from 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.44MB floppy disk) illustrates: fdformat -f 1440 fd0.1440 disklabel -w -r fd0.1440 floppy3 newfs -t 2 -u 18 -l 1 -i 65536 /dev/rfd0 (Use "fd0.1200" and "floppy5" for 5.25" 1.2MB disks). Then you can mount and write to them like any other file system. After you have formatted the floppies, you will need to copy the files onto them. The distribution files are split into chunks conveniently sized so that 5 of them will fit on a conventional 1.44MB floppy. Go through all your floppies, packing as many files as will fit on each one, until you have got all the distributions you want packed up in this fashion. Each distribution should go into a subdirectory on the floppy, e.g.: a:\bin\bin.aa, a:\bin\bin.ab, and so on. Once you come to the Media screen of the install, select ``Floppy'' and you will be prompted for the rest. Before installing from a MS-DOS partition

To prepare for installation from an MS-DOS partition, copy the files from the distribution into a directory called C:\FREEBSD. The directory tree structure of the CDROM must be partially reproduced within this directory so we suggest using the DOS xcopy command. For example, to prepare for a minimal installation of FreeBSD: C> MD C:\FREEBSD C> XCOPY /S E:\BIN C:\FREEBSD\BIN\ C> XCOPY /S E:\MANPAGES C:\FREEBSD\MANPAGES\ assuming that C: is where you have free space and E: is where your CDROM is mounted. For as many `DISTS' you wish to install from MS-DOS (and you have free space for), install each one under C:\FREEBSD - the BIN dist is only the minimal requirement. Before installing from QIC/SCSI Tape

Installing from tape is probably the easiest method, short of an on-line install using FTP or a CDROM install. The installation program expects the files to be simply tar'ed onto the tape, so after getting all of the files for distribution you are interested in, simply tar them onto the tape with a command like: cd /freebsd/distdir tar cvf /dev/rwt0 (or /dev/rst0) dist1 .. dist2 When you go to do the installation, you should also make sure that you leave enough room in some temporary directory (which you will be allowed to choose) to accommodate the full contents of the tape you have created. Due to the non-random access nature of tapes, this method of installation requires quite a bit of temporary storage. You should expect to require as much temporary storage as you have stuff written on tape. Note: When going to do the installation, the tape must be in the drive before booting from the boot floppy. The installation probe may otherwise fail to find it. Before installing over a network

You can do network installations over 3 types of communications links: Serial port SLIP or PPP Parallel port PLIP (laplink cable) Ethernet A standard ethernet controller (includes some PCMCIA). SLIP support is rather primitive, and limited primarily to hard-wired links, such as a serial cable running between a laptop computer and another computer. The link should be hard-wired as the SLIP installation does not currently offer a dialing capability; that facility is provided with the PPP utility, which should be used in preference to SLIP whenever possible. If you are using a modem, then PPP is almost certainly your only choice. Make sure that you have your service provider's information handy as you will need to know it fairly soon in the installation process. You will need to know how to dial your ISP using the ``AT commands'' specific to your modem, as the PPP dialer provides only a very simple terminal emulator. If you're using PAP or CHAP, you'll need to type the necessary ``set authname'' and ``set authkey'' commands before typing ``term''. Refer to the user-ppp and entries for further information. If you have problems, logging can be directed to the screen using the command . If you are using one of the supported PCMCIA ethernet cards, also be sure that it is plugged in before the laptop is powered on! FreeBSD does not, unfortunately, currently support hot insertion of PCMCIA cards during installation. You will also need to know your IP address on the network, the netmask value for your address class, and the name of your machine. Your system administrator can tell you which values to use for your particular network setup. If you will be referring to other hosts by name rather than IP address, you will also need a name server and possibly the address of a gateway (if you are using PPP, it is your provider's IP address) to use in talking to it. If you do not know the answers to all or most of these questions, then you should really probably talk to your system administrator first before trying this type of installation. Once you have a network link of some sort working, the installation can continue over NFS or FTP. Preparing for NFS installation

NFS installation is fairly straight-forward: Simply copy the FreeBSD distribution files you want onto a server somewhere and then point the NFS media selection at it. If this server supports only ``privileged port'' access (as is generally the default for Sun workstations), you will need to set this option in the Options menu before installation can proceed. If you have a poor quality ethernet card which suffers from very slow transfer rates, you may also wish to toggle the appropriate Options flag. In order for NFS installation to work, the server must support subdir mounts, e.g., if your FreeBSD &rel.current; distribution directory lives on: ziggy:/usr/archive/stuff/FreeBSD Then ziggy will have to allow the direct mounting of /usr/archive/stuff/FreeBSD, not just /usr or /usr/archive/stuff. In FreeBSD's /etc/exports file, this is controlled by the ``-alldirs'' option. Other NFS servers may have different conventions. If you are getting `Permission Denied' messages from the server then it is likely that you do not have this enabled properly. Preparing for FTP Installation

FTP installation may be done from any mirror site containing a reasonably up-to-date version of FreeBSD &rel.current;. A full menu of reasonable choices from almost anywhere in the world is provided by the FTP site menu. If you are installing from some other FTP site not listed in this menu, or you are having troubles getting your name server configured properly, you can also specify your own URL by selecting the ``Other'' choice in that menu. A URL can also be a direct IP address, so the following would work in the absence of a name server: ftp://165.113.121.81/pub/FreeBSD/&rel.current;-RELEASE There are two FTP installation modes you can use: FTP Active For all FTP transfers, use ``Active'' mode. This will not work through firewalls, but will often work with older ftp servers that do not support passive mode. If your connection hangs with passive mode (the default), try active! FTP Passive For all FTP transfers, use ``Passive'' mode. This allows the user to pass through firewalls that do not allow incoming connections on random port addresses. Note: Active and passive modes are not the same as a `proxy' connection, where a proxy FTP server is listening and forwarding FTP requests! For a proxy FTP server, you should usually give name of the server you really want as a part of the username, after an @-sign. The proxy server then 'fakes' the real server. An example: Say you want to install from ftp.freebsd.org, using the proxy FTP server foo.bar.com, listening on port 1234. In this case, you go to the options menu, set the FTP username to ftp@ftp.freebsd.org, and the password to your e-mail address. As your installation media, you specify FTP (or passive FTP, if the proxy support it), and the URL ftp://foo.bar.com:1234/pub/FreeBSD /pub/FreeBSD from ftp.freebsd.org is proxied under foo.bar.com, allowing you to install from _that_ machine (which fetch the files from ftp.freebsd.org as your installation requests them). Installing FreeBSD

Once you have taken note of the appropriate preinstallation steps, you should be able to install FreeBSD without any further trouble. Should this not be true, then you may wish to go back and re-read the relevant preparation section above for the installation media type you are trying to use, perhaps there is a helpful hint there that you missed the first time? If you are having hardware trouble, or FreeBSD refuses to boot at all, read the Hardware Guide provided on the boot floppy for a list of possible solutions. - The FreeBSD boot floppy contains all the on-line + The FreeBSD boot floppies contains all the on-line documentation you should need to be able to navigate through an installation and if it does not then we would like to know what you found most confusing. Send your comments to the &a.doc;. It is the objective of the FreeBSD installation program (sysinstall) to be self-documenting enough that painful ``step-by-step'' guides are no longer necessary. It may take us a little while to reach that objective, but that is the objective! Meanwhile, you may also find the following ``typical installation sequence'' to be helpful: - Boot the boot floppy. After a boot sequence - which can take anywhere from 30 seconds to 3 + Boot the kern.flp floppy and, when asked, remove it and + insert the mfsroot.flp floppy and hit return. After a boot + sequence which can take anywhere from 30 seconds to 3 minutes, depending on your hardware, you should be presented with a menu of initial choices. If the - floppy does not boot at all, or the boot hangs at some + kern floppy does not boot at all, or the boot hangs at some stage, go read the Q&A section of the Hardware Guide for possible causes. Press F1. You should see some basic usage instructions on the menu system and general navigation. If you have not used this menu system before then PLEASE read this thoroughly! Select the Options item and set any special preferences you may have. Select a Novice, Custom or Express install, depending on whether or not you would like the installation to help you through a typical installation, give you a high degree of control over each step of the installation or simply whizz through it (using reasonable defaults when possible) as fast as possible. If you have never used FreeBSD before then the Novice installation method is most recommended. The final configuration menu choice allows you to further configure your FreeBSD installation by giving you menu-driven access to various system defaults. Some items, like networking, may be especially important if you did a CDROM/Tape/Floppy installation and have not yet configured your network interfaces (assuming you have any). Properly configuring such interfaces here will allow FreeBSD to come up on the network when you first reboot from the hard disk. MS-DOS User's Questions and Answers

Many FreeBSD users wish to install FreeBSD on PCs inhabited by MS-DOS. Here are some commonly asked questions about installing FreeBSD on such systems.

Help! I have no space! Do I need to delete everything first? If your machine is already running MS-DOS and has little or no free space available for FreeBSD's installation, all is not lost! You may find the FIPS utility, provided in the tools directory on the FreeBSD CDROM or on the various FreeBSD ftp sites, to be quite useful. FIPS allows you to split an existing MS-DOS partition into two pieces, preserving the original partition and allowing you to install onto the second free piece. You first defragment your MS-DOS partition, using the DOS 6.xx DEFRAG utility or the Norton Disk tools, then run FIPS. It will prompt you for the rest of the information it needs. Afterwards, you can reboot and install FreeBSD on the new free slice. See the Distributions menu for an estimation of how much free space you will need for the kind of installation you want. Can I use compressed MS-DOS filesystems from FreeBSD? No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm), FreeBSD will only be able to use whatever portion of the filesystem you leave uncompressed. The rest of the filesystem will show up as one large file (the stacked/dblspaced file!). Do not remove that file! You will probably regret it greatly! It is probably better to create another uncompressed MS-DOS primary partition and use this for communications between MS-DOS and FreeBSD. Can I mount my MS-DOS extended partitions? Yes. DOS extended partitions are mapped in at the end of the other ``slices'' in FreeBSD, e.g. your D: drive might be /dev/sd0s5, your E: drive /dev/sd0s6, and so on. This example assumes, of course, that your extended partition is on SCSI drive 0. For IDE drives, substitute ``wd'' for ``sd'' appropriately. You otherwise mount extended partitions exactly like you would mount any other DOS drive, e.g.: mount -t msdos /dev/sd0s5 /dos_d - - Can I run MS-DOS binaries under FreeBSD? - - BSDI has donated their DOS emulator to the BSD world and - this has been ported to FreeBSD. - - There is also a (technically) nice application available in the - called pcemu - which allows you to run many basic MS-DOS text-mode binaries - by entirely emulating an 8088 CPU. - diff --git a/handbook/submitters.sgml b/handbook/submitters.sgml index 11ba9c300d..21881da580 100644 --- a/handbook/submitters.sgml +++ b/handbook/submitters.sgml @@ -1,3006 +1,3006 @@ - + Contributing to FreeBSD

Contributed by &a.jkh;.

So you want to contribute something to FreeBSD? That is great! We can always use the help, and FreeBSD is one of those systems that relies on the contributions of its user base in order to survive. Your contributions are not only appreciated, they are vital to FreeBSD's continued growth!

Contrary to what some people might also have you believe, you do not need to be a hot-shot programmer or a close personal friend of the FreeBSD core team in order to have your contributions accepted. The FreeBSD Project's development is done by a large and growing number of international contributors whose ages and areas of technical expertise vary greatly, and there is always more work to be done than there are people available to do it.

Since the FreeBSD project is responsible for an entire operating system environment (and its installation) rather than just a kernel or a few scattered utilities, our "TODO" list also spans a very wide range of tasks, from documentation, beta testing and presentation to highly specialized types of kernel development. No matter what your skill level, there is almost certainly something you can do to help the project!

Commercial entities engaged in FreeBSD-related enterprises are also encouraged to contact us. Need a special extension to make your product work? You will find us receptive to your requests, given that they are not too outlandish. Working on a value-added product? Please let us know! We may be able to work cooperatively on some aspect of it. The free software world is challenging a lot of existing assumptions about how software is developed, sold, and maintained throughout its life cycle, and we urge you to at least give it a second look. What Is Needed

The following list of tasks and sub-projects represents something of an amalgam of the various core team TODO lists and user requests we have collected over the last couple of months. Where possible, tasks have been ranked by degree of urgency. If you are interested in working on one of the tasks you see here, send mail to the coordinator listed by clicking on their names. If no coordinator has been appointed, maybe you would like to volunteer? High priority tasks

The following tasks are considered to be urgent, usually because they represent something that is badly broken or sorely needed: 3-stage boot issues. Overall coordination: &a.hackers

Do WinNT compatible drive tagging so that the 3rd stage can provide an accurate mapping of BIOS geometries for disks. Filesystem problems. Overall coordination: &a.fs Clean up and document the nullfs filesystem code. Coordinator: &a.eivind Fix the union file system. Coordinator: &a.dg Implement Int13 vm86 disk driver. Coordinator: &a.hackers New bus architecture. Overall coordination: &a.newbus

Port existing ISA drivers to new architecture. Move all interrupt-management code to appropriate parts of the bus drivers. Port PCI subsystem to new architecture. Coordinator: &a.dfr Figure out the right way to handle removable devices and then use that as a substrate on which PC-Card and CardBus support can be implemented. Resolve the probe/attach priority issue once and for all. Move any remaining buses over to the new architecture. Kernel issues. Overall coordination: &a.hackers

Fix the syscons ALT-Fn/vt switching hangs. Coordinator: &a.sos Add more pro-active security infrastructure. Overall coordination: &a.security Build something like Tripwire(TM) into the kernel, with a remote and local part. There are a number of cryptographic issues to getting this right; contact the coordinator for details. Coordinator: &a.eivind Make the entire kernel use suser() instead of comparing to 0. It is presently using about half of each. Coordinator: &a.eivind Split securelevels into different parts, to allow an administrator to throw away those privileges he can throw away. Setting the overall securelevel needs to have the same effect as now, obviously. Coordinator: &a.eivind Make it possible to upload a list of 'allowed programs' to BPF, and then block BPF from accepting other programs. This would allow BPF to be use e.g. for DHCP, without allowing an attacker to start snooping the local network. Update the security checker script. We should at least grab all the checks from the other BSD derivates, and add checks that a system with securelevel increased also have reasonable flags on the relevant parts. Coordinator: &a.eivind Add authorization infrastructure to the kernel, to allow different authorization policies. Part of this could be done by modifying 'suser()'. Coordinator: &a.eivind Add code to the NFS layer so you cannot chdir("..") out of a NFS partition. E.g.: /usr is a UFS partition with /usr/src NFS exported. Now it is possible to use the NFS file handle for /usr/src to get access to /usr. Medium priority tasks

The following tasks need to be done, but not with any particular urgency: Full KLD based driver support/Configuration Manager.

Write a configuration manager (in the 3rd stage boot?) that probes your hardware in a sane manner, keeps only the KLDs required for your hardware, etc. PCMCIA/PCCARD. Coordinators: &a.msmith and &a.phk Documentation! Reliable operation of the pcic driver (needs testing). Recognizer and handler for sio.c (mostly done). Recognizer and handler for ed.c (mostly done). Recognizer and handler for ep.c (mostly done). User-mode recognizer and handler (partially done). Advanced Power Management. Coordinators: &a.msmith and &a.phk APM sub-driver (mostly done). IDE/ATA disk sub-driver (partially done). syscons/pcvt sub-driver. Integration with the PCMCIA/PCCARD drivers (suspend/resume). Low priority tasks

The following tasks are purely cosmetic or represent such an investment of work that it is not likely that anyone will get them done anytime soon:

The first N items are from Terry Lambert <terry@lambert.org> NetWare Server (protected mode ODI driver) loader and subservices to allow the use of ODI card drivers supplied with network cards. The same thing for NDIS drivers and NetWare SCSI drivers. An "upgrade system" option that works on Linux boxes instead of just previous rev FreeBSD boxes. Symmetric Multiprocessing with kernel preemption (requires kernel preemption). A concerted effort at support for portable computers. This is somewhat handled by changing PCMCIA bridging rules and power management event handling. But there are things like detecting internal vs. external display and picking a different screen resolution based on that fact, not spinning down the disk if the machine is in dock, and allowing dock-based cards to disappear without affecting the machines ability to boot (same issue for PCMCIA). Smaller tasks

Most of the tasks listed in the previous sections require either a considerable investment of time or an in-depth knowledge of the FreeBSD kernel (or both). However, there are also many useful tasks which are suitable for "weekend hackers", or people without programming skills. If you run FreeBSD-current and have a good Internet connection, there is a machine current.freebsd.org which builds a full release once a day - every now and again, try and install the latest release from it and report any failures in the process. Read the freebsd-bugs mailing list. There might be a problem you can comment constructively on or with patches you can test. Or you could even try to fix one of the problems yourself. Read through the FAQ and Handbook periodically. If anything is badly explained, out of date or even just completely wrong, let us know. Even better, send us a fix (SGML is not difficult to learn, but there is no objection to ASCII submissions). Help translate FreeBSD documentation into your native language (if not already available) - just send an email to &a.doc asking if anyone is working on it. Note that you are not committing yourself to translating every single FreeBSD document by doing this - in fact, the documentation most in need of translation is the installation instructions. Read the freebsd-questions mailing list and &ng.misc occasionally (or even regularly). It can be very satisfying to share your expertise and help people solve their problems; sometimes you may even learn something new yourself! These forums can also be a source of ideas for things to work on. If you know of any bugfixes which have been successfully applied to -current but have not been merged into -stable after a decent interval (normally a couple of weeks), send the committer a polite reminder. Move contributed software to src/contrib in the source tree. Make sure code in src/contrib is up to date. Look for year 2000 bugs (and fix any you find!) Build the source tree (or just part of it) with extra warnings enabled and clean up the warnings. Fix warnings for ports which do deprecated things like using gets() or including malloc.h. If you have contributed any ports, send your patches back to the original author (this will make your life easier when they bring out the next version) Suggest further tasks for this list! How to Contribute

Contributions to the system generally fall into one or more of the following 6 categories: Bug reports and general commentary

An idea or suggestion of general technical interest should be mailed to the &a.hackers;. Likewise, people with an interest in such things (and a tolerance for a high volume of mail!) may subscribe to the hackers mailing list by sending mail to &a.majordomo;. See for more information about this and other mailing lists. If you find a bug or are submitting a specific change, please report it using the send-pr(1) program or its . Try to fill-in each field of the bug report. Unless they exceed 65KB, include any patches directly in the report. Consider compressing them and using uuencode(1) if they exceed 20KB. Upload very large submissions to . After filing a report, you should receive confirmation along with a tracking number. Keep this tracking number so that you can update us with details about the problem by sending mail to . Use the number as the message subject, e.g. "Re: kern/3377". Additional information for any bug report should be submitted this way. If you do not receive confirmation in a timely fashion (3 days to a week, depending on your email connection) or are, for some reason, unable to use the send-pr(1) command, then you may ask someone to file it for you by sending mail to the &a.bugs;. Changes to the documentation

Changes to the documentation are overseen by the &a.doc;. Send submissions and changes (even small ones are welcome!) using send-pr as described in . Changes to existing source code

An addition or change to the existing source code is a somewhat trickier affair and depends a lot on how far out of date you are with the current state of the core FreeBSD development. There is a special on-going release of FreeBSD known as ``FreeBSD-current'' which is made available in a variety of ways for the convenience of developers working actively on the system. See for more information about getting and using FreeBSD-current. Working from older sources unfortunately means that your changes may sometimes be too obsolete or too divergent for easy re-integration into FreeBSD. Chances of this can be minimized somewhat by subscribing to the &a.announce and the &a.current lists, where discussions on the current state of the system take place. Assuming that you can manage to secure fairly up-to-date sources to base your changes on, the next step is to produce a set of diffs to send to the FreeBSD maintainers. This is done with the diff(1) command, with the `context diff' form being preferred. For example: diff -c oldfile newfile or diff -c -r olddir newdir would generate such a set of context diffs for the given source file or directory hierarchy. See the man page for diff(1) for more details. Once you have a set of diffs (which you may test with the patch(1) command), you should submit them for inclusion with FreeBSD. Use the send-pr(1) program as described in . Do not just send the diffs to the &a.hackers; or they will get lost! We greatly appreciate your submission (this is a volunteer project!); because we are busy, we may not be able to address it immediately, but it will remain in the pr database until we do. If you feel it appropriate (e.g. you have added, deleted, or renamed files), bundle your changes into a tar file and run the uuencode(1) program on it. Shar archives are also welcome. If your change is of a potentially sensitive nature, e.g. you are unsure of copyright issues governing its further distribution or you are simply not ready to release it without a tighter review first, then you should send it to &a.core; directly rather than submitting it with send-pr(1). The core mailing list reaches a much smaller group of people who do much of the day-to-day work on FreeBSD. Note that this group is also very busy and so you should only send mail to them where it is truly necessary. Please refer to man 9 intro and man 9 style for some information on coding style. We would appreciate it if you were at least aware of this information before submitting code. New code or major value-added packages

In the rare case of a significant contribution of a large body work, or the addition of an important new feature to FreeBSD, it becomes almost always necessary to either send changes as uuencode'd tar files or upload them to our ftp site . When working with large amounts of code, the touchy subject of copyrights also invariably comes up. Acceptable copyrights for code included in FreeBSD are: The BSD copyright. This copyright is most preferred due to its ``no strings attached'' nature and general attractiveness to commercial enterprises. Far from discouraging such commercial use, the FreeBSD Project actively encourages such participation by commercial interests who might eventually be inclined to invest something of their own into FreeBSD. The GNU Public License, or ``GPL''. This license is not quite as popular with us due to the amount of extra effort demanded of anyone using the code for commercial purposes, but given the sheer quantity of GPL'd code we currently require (compiler, assembler, text formatter, etc) it would be silly to refuse additional contributions under this license. Code under the GPL also goes into a different part of the tree, that being /sys/gnu or /usr/src/gnu, and is therefore easily identifiable to anyone for whom the GPL presents a problem.

Contributions coming under any other type of copyright must be carefully reviewed before their inclusion into FreeBSD will be considered. Contributions for which particularly restrictive commercial copyrights apply are generally rejected, though the authors are always encouraged to make such changes available through their own channels. To place a ``BSD-style'' copyright on your work, include the following text at the very beginning of every source code file you wish to protect, replacing the text between the `%%' with the appropriate information. Copyright (c) %%proper_years_here%% %%your_name_here%%, %%your_state%% %%your_zip%%. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer as the first lines of this file unmodified. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. THIS SOFTWARE IS PROVIDED BY %%your_name_here%% ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL %%your_name_here%% BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. $Id$ For your convenience, a copy of this text can be found in /usr/share/examples/etc/bsd-style-copyright. Money, Hardware or Internet access

We are always very happy to accept donations to further the cause of the FreeBSD Project and, in a volunteer effort like ours, a little can go a long way! Donations of hardware are also very important to expanding our list of supported peripherals since we generally lack the funds to buy such items ourselves. Donating funds

While the FreeBSD Project is not a 501(c)(3) (charitable) corporation and hence cannot offer special tax incentives for any donations made, any such donations will be gratefully accepted on behalf of the project by FreeBSD, Inc.

FreeBSD, Inc. was founded in early 1995 by &a.jkh and &a.dg with the goal of furthering the aims of the FreeBSD Project and giving it a minimal corporate presence. Any and all funds donated (as well as any profits that may eventually be realized by FreeBSD, Inc.) will be used exclusively to further the project's goals. Please make any checks payable to FreeBSD, Inc., sent in care of the following address: FreeBSD, Inc. c/o Jordan Hubbard 4041 Pike Lane, suite #F. Concord CA, 94520 [currently using the Walnut Creek CDROM address until a PO box can be opened] Wire transfers may also be sent directly to: Bank Of America Concord Main Office P.O. Box 37176 San Francisco CA, 94137-5176 Routing #: 121-000-358 Account #: 01411-07441 (FreeBSD, Inc.) Any correspondence related to donations should be sent to , either via email or to the FreeBSD, Inc. postal address given above. If you do not wish to be listed in our section, please specify this when making your donation. Thanks! Donating hardware

Donations of hardware in any of the 3 following categories are also gladly accepted by the FreeBSD Project: General purpose hardware such as disk drives, memory or complete systems should be sent to the FreeBSD, Inc. address listed in the donating funds section. Hardware for which ongoing compliance testing is desired. We are currently trying to put together a testing lab of all components that FreeBSD supports so that proper regression testing can be done with each new release. We are still lacking many important pieces (network cards, motherboards, etc) and if you would like to make such a donation, please contact &a.dg for information on which items are still required. Hardware currently unsupported by FreeBSD for which you would like to see such support added. Please contact the &a.core; before sending such items as we will need to find a developer willing to take on the task before we can accept delivery of new hardware. Donating Internet access

We can always use new mirror sites for FTP, WWW or cvsup. If you would like to be such a mirror, please contact for more information. Donors Gallery

The FreeBSD Project is indebted to the following donors and would like to publically thank them here! Contributors to the central server project:

The following individuals and businesses made it possible for the FreeBSD Project to build a new central server machine to eventually replace freefall.freebsd.org by donating the following items: and his employer, , donated a Pentium Pro (P6) 200Mhz CPU donated a Tyan 1662 motherboard. of donated a Kingston ethernet controller. donated an NCR 53C875 SCSI controller card. of donated 128MB of memory, a 4 Gb disk drive and the case. Direct funding:

The following individuals and businesses have generously contributed direct funding to the project: Sean Eric Fagan Don Scott Wilde Robert T. Morris of of Japan (a portion of the profits from sales of their various FreeBSD CD-ROMs. donated a portion of their profits from Hajimete no FreeBSD (FreeBSD, Getting started) to the FreeBSD and XFree86 projects. donated a portion of their profits from several FreeBSD-related books to the FreeBSD project. has generously donated significant funding to the FreeBSD project. Hardware contributors:

The following individuals and businesses have generously contributed hardware for testing and device driver development/support: Walnut Creek CDROM for providing the Pentium P5-90 and 486/DX2-66 EISA/VL systems that are being used for our development work, to say nothing of the network access and other donations of hardware resources. TRW Financial Systems, Inc. provided 130 PCs, three 68 GB fileservers, twelve Ethernets, two routers and an ATM switch for debugging the diskless code. Dermot McDonnell donated the Toshiba XM3401B CDROM drive currently used in freefall. &a.chuck; contributed his floppy tape streamer for experimental work. Larry Altneu , and &a.wilko;, provided Wangtek and Archive QIC-02 tape drives in order to improve the wt driver. Ernst Winter contributed a 2.88 MB floppy drive to the project. This will hopefully increase the pressure for rewriting the floppy disk driver. ;-) sent one each of their DC-390, DC-390U and DC-390F FAST and ULTRA SCSI host adapter cards for regression testing of the NCR and AMD drivers with their cards. They are also to be applauded for making driver sources for free operating systems available from their FTP server . contributed not only a Symbios Sym8751S SCSI card, but also a set of data books, including one about the forthcoming Sym53c895 chip with Ultra-2 and LVD support, and the latest programming manual with information on how to safely use the advanced features of the latest Symbios SCSI chips. Thanks a lot! donated an FX120 12 speed Mitsumi CDROM drive for IDE CDROM driver development. Special contributors:

has donated almost more than we can say (see the document for more details). In particular, we would like to thank them for the original hardware used for freefall.FreeBSD.ORG, our primary development machine, and for thud.FreeBSD.ORG, a testing and build box. We are also indebted to them for funding various contributors over the years and providing us with unrestricted use of their T1 connection to the Internet. The has been patiently supporting &a.joerg; who has often preferred FreeBSD work over paywork, and used to fall back to their (quite expensive) EUnet Internet connection whenever his private connection became too slow or flakey to work with it... has contributed their DOS emulator code to the remaining BSD world, which is used in the dosemu command. Core Team Alumnus

The following people were members of the FreeBSD core team during the period indicated. We thank them for their past efforts in the service of the FreeBSD project!

In rough chronological order:

Guido van Rooij (1995 - 1999) John Dyson (1993 - 1998) Nate Williams (1992 - 1996) Rod Grimes (1992 - 1995) Andreas Schulz (1992 - 1995) Geoff Rehmet (1993 - 1995) Paul Richards (1992 - 1995) Scott Mace (1993 - 1994) Andrew Moore (1993 - 1994) Christoph Robitschko (1993 - 1994) J.T. Conklin (1992 - 1993) Derived Software Contributors

This software was originally derived from William F. Jolitz's 386BSD release 0.1, though almost none of the original 386BSD specific code remains. This software has been essentially re-implemented from the 4.4BSD-Lite release provided by the Computer Science Research Group (CSRG) at the University of California, Berkeley and associated academic contributors. There are also portions of NetBSD and OpenBSD that have been integrated into FreeBSD as well, and we would therefore like to thank all the contributors to NetBSD and OpenBSD for their work. Additional FreeBSD Contributors

(in alphabetical order by first name): ABURAYA Ryushirou AMAGAI Yoshiji Aaron Bornstein Aaron Smith Achim Patzner Ada T Lim Adam Baran Adam Glass Adam McDougall Ade Barkah Ade Barkah Adrian Colley Adrian Hall Adrian Mariano Adrian Steinmann Adrian T. Filipi-Martin Ajit Thyagarajan Akio Morita Akira SAWADA Akira Watanabe Akito Fujita Alain Kalker Alan Bawden Alan Cox Alec Wolman Aled Morris Alex Alex D. Chen Alex G. Bulushev Alex Le Heux Alex Nash Alexander B. Povolotsky Alexander Leidinger Alexandre Snarskii Alistair G. Crooks Allan Saddi Allen Campbell Amakawa Shuhei Amancio Hasty Amir Farah Amy Baron Anatoly A. Orehovsky Anatoly Vorobey Anders Nordby Anders Thulin Andras Olah Andre Albsmeier Andre Oppermann Andreas Haakh Andreas Kohout Andreas Lohr Andreas Schulz Andreas Wetzel Andreas Wrede Andres Vega Garcia Andrew Atrens Andrew Gillham Andrew Gordon Andrew Herbert Andrew J. Korty Andrew L. Moore Andrew McRae Andrew Stevenson Andrew Timonin Andrew V. Stesin Andrew Webster Andrey Zakhvatov Andy Farkas Andy Valencia Andy Whitcroft Angelo Turetta Anthony C. Chavez Anthony Yee-Hang Chan Anton Berezin Antti Kaipila Are Bryne Ari Suutari Arjan de Vet Arne Henrik Juul Assar Westerlund Atsushi Furuta Atsushi Murai Bakul Shah Barry Bierbauch Barry Lustig Ben Hutchinson Ben Jackson Ben Smithurst Ben Walter Benjamin Lewis Bernd Rosauer Bill Kish Bill Trost Blaz Zupan Bob Van Valzah Bob Willcox Boris Staeblow Boyd R. Faulkner Brad Karp Bradley Dunn Brandon Gillespie &a.wlloyd Bob Wilcox Boyd Faulkner Brent J. Nordquist Brett Lymn Brett Taylor Brian Campbell Brian Clapper Brian Cully Brian F. Feldman Brian Handy Brian Litzinger Brian McGovern Brian Moore Brian R. Haug Brian Somers Brian Tao Brion Moss Bruce A. Mah Bruce Albrecht Bruce Gingery Bruce J. Keeler Bruce Murphy Bruce Walter Carey Jones Carl Fongheiser Carl Mascott Casper Castor Fu Cejka Rudolf Chain Lee Charles Hannum Charles Henrich Charles Mott Charles Owens Chet Ramey Chia-liang Kao Chiharu Shibata Chip Norkus Choi Jun Ho Chris Csanady Chris Dabrowski Chris Dillon Chris Piazza Chris Shenton Chris Stenton Chris Timmons Chris Torek Christian Gusenbauer Christian Haury Christian Weisgerber Christoph P. Kukulies Christoph Robitschko Christoph Weber-Fahr Christopher G. Demetriou Christopher T. Johnson Chrisy Luke Chuck Hein Clive Lin Colman Reilly Conrad Sabatier Coranth Gryphon Cornelis van der Laan Cove Schneider Craig Leres Craig Loomis Craig Metz Craig Spannring Craig Struble Cristian Ferretti Curt Mayer Cy Schubert DI. Christian Gusenbauer Dai Ishijima Damian Hamill Dan Cross Dan Lukes Dan Nelson Dan Walters Daniel Baker Daniel M. Eischen Daniel O'Connor Daniel Poirot Daniel Rock Danny Egen Danny J. Zerkel Darren Reed Dave Adkins Dave Andersen Dave Blizzard Dave Bodenstab Dave Burgess Dave Chapeskie Dave Cornejo Dave Edmondson Dave Glowacki Dave Marquardt Dave Tweten David A. Adkins David A. Bader David Borman David Dawes David Filo David Greenman David Holland David Holloway David Horwitt David Hovemeyer David Jones David Kelly David Kulp David L. Nugent David Leonard David Malone David Muir Sharnoff David S. Miller David Wolfskill Dean Gaudet Dean Huxley Denis Fortin Dennis Glatting Denton Gentry Derek Inksetter Dima Sivachenko Dirk Froemberg Dirk Keunecke Dirk Nehrling Dmitry Khrustalev Dmitry Kohmanyuk Dom Mitchell Don Croyle &a.whiteside; Don Morrison Don Yuniskis Donald Maddox Doug Barton Douglas Ambrisko Douglas Carmichael Douglas Crosher Drew Derbyshire Duncan Barclay Dustin Sallings Eckart "Isegrim" Hofmann Ed Gold Ed Hudson Edward Wang Edwin Groothus Eiji-usagi-MATSUmoto ELISA Font Project Elmar Bartel Eric A. Griff Eric Blood Eric J. Chet Eric J. Haug Eric J. Schwertfeger Eric L. Hernes Eric P. Scott Eric Sprinkle Erich Stefan Boleyn Erik E. Rantapaa Erik H. Moe Ernst Winter Eugene M. Kim Eugene Radchenko Evan Champion Faried Nawaz Flemming Jacobsen Fong-Ching Liaw Francis M J Hsieh Frank Bartels Frank Chen Hsiung Chan Frank Durda IV Frank MacLachlan Frank Nobis Frank Volf Frank ten Wolde Frank van der Linden Fred Cawthorne Fred Gilham Fred Templin Frederick Earl Gray FUJIMOTO Kensaku FUJISHIMA Satsuki FURUSAWA Kazuhisa Gabor Kincses Gabor Zahemszky Garance A Drosehn Gareth McCaughan Gary A. Browning Gary Howland Gary J. Gary Kline Gaspar Chilingarov Gea-Suan Lin Geoff Rehmet Georg Wagner Gerard Roudier Gianmarco Giovannelli Gil Kloepfer Jr. Gilad Rom Ginga Kawaguti Giles Lean Glen Foster Glenn Johnson Godmar Back Goran Hammarback Gord Matzigkeit Graham Wheeler Greg A. Woods Greg Ansley Greg Troxel Greg Ungerer Gregory Bond Gregory D. Moncreaff Guy Harris Guy Helmer HAMADA Naoki HONDA Yasuhiro HOSOBUCHI Noriyuki Hannu Savolainen Hans Huebner Hans Petter Bieker Hans Zuidam Harlan Stenn Harold Barker Havard Eidnes Heikki Suonsivu Heiko W. Rupp Helmut F. Wirth Henrik Vestergaard Draboel Herb Peyerl Hideaki Ohmon Hidekazu Kuroki Hideki Yamamoto Hidetoshi Shimokawa Hideyuki Suzuki Hirayama Issei Hiroaki Sakai Hiroharu Tamaru Hironori Ikura Hiroshi Nishikawa Hiroya Tsubakimoto Hiroyuki NAKAJI Holger Veit Holm Tiffe Horance Chou Horihiro Kumagaio Horikawa Kazuo Hr.Ladavac Hubert Feyrer Hugh F. Mahon Hugh Mahon Hung-Chi Chu IMAI Takeshi IMAMURA Tomoaki Ian Dowse Ian Holland Ian Struble Ian Vaudrey Igor Khasilev Igor Roshchin Igor Sviridov Igor Vinokurov Ikuo Nakagawa Ilya V. Komarov Issei Suzuki Itsuro Saito J. Bryant J. David Lowe J. Han J. Hawk J.T. Conklin J.T. Jang Jack Jacob Bohn Lorensen Jagane D Sundar Jake Hamby James Clark James D. Stewart James Jegers James Raynard James T. Liu James da Silva et al Jan Conard Jan Koum Janick Taillandier Janusz Kokot Jarle Greipsland Jason Garman Jason Thorpe Jason Wright Jason Young Javier Martin Rueda Jay Fenlason Jaye Mathisen Jeff Bartig Jeff Forys Jeff Kletsky Jeffrey Evans Jeffrey Wheat Jens Schweikhardt Jeremy Allison Jeremy Chatfield Jeremy Lea Jeremy Prior Jeroen Ruigrok/Asmodai Jesse Rosenstock Jian-Da Li Jim Babb Jim Binkley Jim Carroll Jim Flowers Jim Leppek Jim Lowe Jim Mattson Jim Mercer Jim Mock Jim Wilson Jimbo Bahooli Jin Guojun Joachim Kuebart Joao Carlos Mendes Luis Jochen Pohl Joe "Marcus" Clarke Joe Abley Joe Jih-Shian Lu Joe Orthoefer Joe Traister Joel Faedi Joel Ray Holveck Joel Sutton Johan Granlund Johan Karlsson Johan Larsson Johann Tonsing Johannes Helander Johannes Stille John Baldwin John Beckett John Beukema John Brezak John Capo John F. Woods John Goerzen John Hay John Heidemann John Hood John Kohl John Lind John Mackin John P John Perry John Preisler John Rochester John Sadler John Saunders John W. DeBoskey John Wehle John Woods Jon Morgan Jonathan H N Chin Jonathan Hanna Jorge Goncalves Jorge M. Goncalves Jos Backus Jose M. Alcaide Josef Grosch Josef Karthauser Joseph Stein Josh Gilliam Josh Tiefenbach Joshua Peck Macdonald Juergen Lock Juha Inkari Jukka A. Ukkonen Julian Assange Julian Coleman Julian H. Stacey Julian Jenkins Junichi Satoh Junji SAKAI Junya WATANABE K.Higashino KUNISHIMA Takeo Kai Vorma Kaleb S. Keithley Kaneda Hiloshi Kapil Chowksey Karl Denninger Karl Dietz Karl Lehenbauer Kato Takenori Kauzo Horikawa Kawanobe Koh Kazuhiko Kiriyama Kazuo Horikawa Kees Jan Koster Keith Bostic Keith E. Walker Keith Moore Keith Sklower Ken Hornstein Ken Key Ken Mayer Kenji Saito Kenji Tomita Kenneth Furge Kenneth Monville Kenneth R. Westerback Kenneth Stailey Kent Talarico Kent Vander Velden Kentaro Inagaki Kevin Bracey Kevin Day Kevin Lahey Kevin Street Kevin Van Maren Kiroh HARADA Klaus Klein Klaus-J. Wolf Koichi Sato Kostya Lukin Kouichi Hirabayashi Kris Kennaway Kurt D. Zeilenga Kurt Olsen L. Jonas Olsson Lars Köller Larry Altneu Laurence Lopez Lee Cremeans Liang Tai-hwa Lon Willett Louis A. Mamakos Louis Mamakos Lucas James Lyndon Nerenberg M.C. Wong MANTANI Nobutaka MIHIRA Sanpei Yoshiro MITA Yoshio MITSUNAGA Noriaki MOROHOSHI Akihiko Magnus Enbom Mahesh Neelakanta Makoto MATSUSHITA Makoto WATANABE Malte Lance Manu Iyengar Marc Frajola Marc G. Fournier Marc Ramirez Marc Slemko Marc van Kempen Marcel Moolenaar Mario Sergio Fujikawa Ferreira Mark Andrews Mark Cammidge Mark Diekhans Mark Huizer Mark J. Taylor Mark Krentel Mark Mayo Mark Thompson Mark Tinguely Mark Treacy Mark Valentine Martin Birgmeier Martin Ibert Martin Kammerhofer Martin Renters Martti Kuparinen Masachika ISHIZUKA Mas.TAKEMURA Masafumi NAKANE Masahiro Sekiguchi Masanobu Saitoh Masanori Kanaoka Masanori Kiriake Masatoshi TAMURA Mats Lofkvist Matt Bartley Matt Thomas Matt White Matthew C. Mead Matthew Cashdollar Matthew Flatt Matthew Fuller Matthew Hunt Matthew N. Dodd Matthew Stein Matthias Pfaller Matthias Scheler Mattias Gronlund Mattias Pantzare Maurice Castro Max Euston Max Khon Maxim Bolotin Micha Class Michael Butler Michael Butschky Michael Clay Michael Elbel Michael Galassi Michael Hancock Michael Hohmuth Michael Perlman Michael Petry Michael Reifenberger Michael Searle Michal Listos Michio Karl Jinbo Miguel Angel Sagreras Mihoko Tanaka Mika Nystrom Mikael Hybsch Mikael Karpberg Mike Del Mike Durian Mike Durkin Mike E. Matsnev Mike Evans Mike Grupenhoff Mike Hibler Mike Karels Mike McGaughey Mike Meyer Mike Mitchell Mike Murphy Mike Peck Mike Spengler Mikhail A. Sokolov Mikhail Teterin Ming-I Hseh Mitsuru IWASAKI Monte Mitzelfelt Morgan Davis Mostyn Lewis Motoyuki Kasahara Motoyuki Konno Munechika Sumikawa Murray Stokely N.G.Smith NAGAO Tadaaki NAKAJI Hiroyuki NAKAMURA Kazushi NAKAMURA Motonori NIIMI Satoshi NOKUBI Hirotaka Nadav Eiron Nanbor Wang Naofumi Honda Naoki Hamada Narvi Nathan Dorfman Neal Fachan Neil Blakey-Milner Niall Smart Nick Barnes Nick Handel Nick Hibma Nick Hilliard Nick Sayer Nick Williams Nickolay N. Dudorov Niklas Hallqvist Nisha Talagala No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name No Name Nobuhiro Yasutomi Nobuyuki Koganemaru Norio Suzuki Noritaka Ishizumi Noriyuki Soda Oleg Sharoiko Oliver Breuninger Oliver Friedrichs Oliver Fromme Oliver Laumann Oliver Oberdorf Olof Johansson Osokin Sergey aka oZZ Pace Willisson Paco Rosich Palle Girgensohn Parag Patel Pascal Pederiva Pasvorn Boonmark Patrick Gardella Patrick Hausen Paul Antonov Paul F. Werkowski Paul Fox Paul Koch Paul Kranenburg Paul Mackerras Paul Popelka Paul S. LaFollette, Jr. Paul Saab Paul Sandys Paul T. Root Paul Vixie Paulo Menezes Paulo Menezes Pedro A M Vazquez Pedro Giffuni Pete Bentley Peter Childs Peter Cornelius Peter Haight Peter Hawkins Peter Jeremy Peter M. Chen Peter Much Peter Olsson Peter Philipp Peter Stubbs Phil Maker Phil Sutherland Phil Taylor Philip Musumeci Pierre Y. Dampure Pius Fischer Pomegranate Powerdog Industries R. Kym Horsell Rajesh Vaidheeswarran Ralf Friedl Randal S. Masutani Randall Hopper Randall W. Dean Randy Bush Reinier Bezuidenhout Remy Card Ricardas Cepas Richard Henderson Richard Hwang Richard J Kuhns Richard M. Neswold Richard Seaman, Jr. Richard Stallman Richard Straka Richard Tobin Richard Wackerbarth Richard Winkel Richard Wiwatowski Rick Macklem Rick Macklin Rob Austein Rob Mallory Rob Snow Robert Crowe Robert D. Thrush Robert Eckardt Robert Sanders Robert Sexton Robert Shady Robert Swindells Robert Watson Robert Withrow Robert Yoder Robin Carey Roger Hardiman Roland Jesse Ron Bickers Ron Lenk Ronald Kuehn Rudolf Cejka Ruslan Belkin Ruslan Ermilov Ruslan Shevchenko Russell L. Carter Russell Vincent Ryan Younce SANETO Takanori SAWADA Mizuki SUGIMURA Takashi SURANYI Peter Sakari Jalovaara Sam Hartman Samuel Lam Sander Vesik Sandro Sigala Sascha Blank Sascha Wildner Satoh Junichi Satoshi Taoka Scot Elliott Scot W. Hetzel Scott A. Kenney Scott Blachowicz Scott Burris Scott Hazen Mueller Scott Michel Scott Reynolds Sebastian Strollo Seigou TANIMURA Serge A. Babkin Serge V. Vakulenko Sergei Chechetkin Sergei S. Laskavy Sergey Gershtein Sergey Potapov Sergey Shkonda Sergey V.Dorokhov Sergio Lenzi Shaun Courtney Shawn M. Carey Sheldon Hearn Shigeyuki FUKUSHIMA Shigio Yamaguchi Shunsuke Akiyama Simon Simon Burge Simon J Gerraty Simon Marlow Simon Shapiro Sin'ichiro MIYATANI Slaven Rezic Soochon Radee Soren Dayton Soren Dossing Soren S. Jorvang Stefan Bethke Stefan Eggers Stefan Moeding Stefan Petri Stefan `Sec` Zehl Steinar Haug Stephane E. Potvin Stephane Legrand Stephen Clawson Stephen F. Combs Stephen Farrell Stephen Hocking Stephen J. Roznowski Stephen McKay Stephen Melvin Steve Bauer Steve Deering Steve Gerakines Steve Gericke Steve Piette Steve Schwarz Steven G. Kargl Steven H. Samorodin Steven McCanne Steven Plite Steven Wallace Stuart Henderson Sue Blake Sugiura Shiro Sujal Patel Sune Stjerneby Suzuki Yoshiaki Tadashi Kumano Taguchi Takeshi Takahashi Yoshihiro Takahiro Yugawa Takanori Watanabe Takashi Mega Takashi Uozu Takayuki Ariga Takeru NAIKI Takeshi Amaike Takeshi MUTOH Takeshi Ohashi Takeshi WATANABE Takuya SHIOZAKI Tatoku Ogaito Tatsumi HOSOKAWA Ted Buswell Ted Faber Ted Lemon Terry Lambert Terry Lee Tetsuya Furukawa Theo de Raadt Thomas Thomas D. Dean Thomas David Rivers Thomas G. McWilliams Thomas Gellekum Thomas Graichen Thomas König Thomas Ptacek Thomas Stromberg Thomas Valentino Crimi Thomas Wintergerst Þórður Ívarsson Tim Kientzle Tim Singletary Tim Wilkinson Timo J. Rinne Todd Miller Tom Tom Tom Gray - DCA Tom Hukins Tom Jobbins Tom Pusateri Tom Rush Tom Samplonius Tomohiko Kurahashi Tony Kimball Tony Li Tony Lynn Torbjorn Granlund Toshihiko ARAI Toshihiko SHIMOKAWA Toshihiro Kanda Toshiomi Moriki Trefor S. Trevor Blackwell URATA Shuichiro Ugo Paternostro Ulf Kieber Ulli Linzen Ustimenko Semen Uwe Arndt Vadim Chekan Vadim Kolontsov Vadim Mikhailov Van Jacobson Vanill I. Shu Vanilla Pooh Shu Vasily V. Grechishnikov Vasim Valejev Vernon J. Schryver Vic Abell Ville Eerola Vincent Poy Vincenzo Capuano Virgil Champlin Vladimir A. Jakovenko Vladimir Kushnir Vsevolod Lobko W. Gerald Hicks W. Richard Stevens Walt Howard Warren Toomey Wayne Scott Werner Griessl Wes Santee Wietse Venema Wilfredo Sanchez Wiljo Heinen Wilko Bulte Willem Jan Withagen William Jolitz William Liao Wojtek Pilorz Wolfgang Helbig Wolfgang Solfrank Wolfgang Stanglmeier Wu Ching-hong Yarema Yaroslav Terletsky Yen-Shuo Su Ying-Chieh Liao Yixin Jin Yoshiaki Uchikawa Yoshihiko OHTA Yoshihisa NAKAGAWA Yoshikazu Goto Yoshimasa Ohnishi Yoshishige Arai Yuichi MATSUTAKA Yujiro MIYATA Yukihiro Nakai Yusuke Nawano Yuval Yarom Yves Fonk Yves Fonk Zach Heilig Zahemszhky Gabor Zhong Ming-Xun arci der Mouse frf - Ege Rekk Ege Rekk 386BSD Patch Kit Patch Contributors

(in alphabetical order by first name): Adam Glass Adrian Hall Andrey A. Chernov Andrew Herbert Andrew Moore Andy Valencia Arne Henrik Juul Bakul Shah Barry Lustig Bob Wilcox Branko Lankester Brett Lymn Charles Hannum Chris G. Demetriou Chris Torek Christoph Robitschko Daniel Poirot Dave Burgess Dave Rivers David Dawes David Greenman Eric J. Haug Felix Gaehtgens Frank Maclachlan Gary A. Browning Gary Howland Geoff Rehmet Goran Hammarback Guido van Rooij Guy Harris Havard Eidnes Herb Peyerl Holger Veit Ishii Masahiro, R. Kym Horsell J.T. Conklin Jagane D Sundar James Clark James Jegers James W. Dolter James da Silva et al Jay Fenlason Jim Wilson Jörg Lohse Jörg Wunsch John Dyson - John Woods Jordan K. Hubbard Julian Elischer Julian Stacey Karl Dietz Karl Lehenbauer Keith Bostic Ken Hughes Kent Talarico Kevin Lahey Marc Frajola Mark Tinguely Martin Renters Michael Clay Michael Galassi Mike Durkin Naoki Hamada Nate Williams Nick Handel Pace Willisson Paul Kranenburg Paul Mackerras Paul Popelka Peter da Silva Phil Sutherland Poul-Henning Kamp Ralf Friedl Rick Macklem Robert D. Thrush Rodney W. Grimes Sascha Wildner Scott Burris Scott Reynolds Sean Eric Fagan Simon J Gerraty Stephen McKay Terry Lambert Terry Lee Tor Egge Warren Toomey Wiljo Heinen William Jolitz Wolfgang Solfrank Wolfgang Stanglmeier Yuval Yarom