diff options
| author | bmah <bmah@FreeBSD.org> | 2001-05-25 18:01:34 +0000 |
|---|---|---|
| committer | bmah <bmah@FreeBSD.org> | 2001-05-25 18:01:34 +0000 |
| commit | d9a12d0566b7d6c4822930fba53d7052e31c5d0b (patch) | |
| tree | 025cce997350ac9f55eb378ca499f97cad1dc441 /release | |
| parent | 9590b221cbf4b26a2d1a86e484367aaa960db515 (diff) | |
| download | FreeBSD-src-d9a12d0566b7d6c4822930fba53d7052e31c5d0b.zip FreeBSD-src-d9a12d0566b7d6c4822930fba53d7052e31c5d0b.tar.gz | |
RELNOTESng is now the default for -CURRENT release builds. (Floppy
images get TXT renderings only; CDROM and FTP areas get TXT and HTML.)
Remove the old *.TXT release documentation files, as they
have been subsumed into RELNOTESng. The new layout will greatly
facilitate their maintenence and help keep them internally consistent.
Diffstat (limited to 'release')
| -rw-r--r-- | release/Makefile | 93 | ||||
| -rw-r--r-- | release/texts/ABOUT.TXT | 215 | ||||
| -rw-r--r-- | release/texts/ERRATA.TXT | 30 | ||||
| -rw-r--r-- | release/texts/FLOPPIES.TXT | 57 | ||||
| -rw-r--r-- | release/texts/HARDWARE.TXT | 1083 | ||||
| -rw-r--r-- | release/texts/LAYOUT.TXT | 101 | ||||
| -rw-r--r-- | release/texts/README.TXT | 105 | ||||
| -rw-r--r-- | release/texts/TROUBLE.TXT | 383 | ||||
| -rw-r--r-- | release/texts/UPGRADE.TXT | 179 | ||||
| -rw-r--r-- | release/texts/alpha/HARDWARE.TXT | 1892 | ||||
| -rw-r--r-- | release/texts/alpha/INSTALL.TXT | 448 | ||||
| -rw-r--r-- | release/texts/alpha/RELNOTES.TXT | 1713 | ||||
| -rw-r--r-- | release/texts/i386/INSTALL.TXT | 545 | ||||
| -rw-r--r-- | release/texts/i386/RELNOTES.TXT | 2028 |
14 files changed, 33 insertions, 8839 deletions
diff --git a/release/Makefile b/release/Makefile index fbb407b..80b2500 100644 --- a/release/Makefile +++ b/release/Makefile @@ -73,11 +73,14 @@ OBJFORMAT?= elf #NODOC= YES #NOPORTS= YES -# RELNOTESng can be enabled be uncommenting the following variable -# definition. It depends on having ports and docs enabled for this +# RELNOTESng can be disabled by uncommenting the following variable +# definition. RELNOTESng depends on having ports enabled for this # release build. -#RELNOTESNG= YES -#RELNOTESNG_LANG= en_US.ISO_8859-1 +#NORELNOTES= YES + +# Uncomment and modify this definition if you want the release notes +# and other release documentation in a language other than English. +#RELNOTES_LANG= en_US.ISO_8859-1 # As an alternative to installing the entire ports collection (which # can take a huge amount of time, in particular on slower disks), @@ -95,8 +98,9 @@ NOPORTSATALL= YES .endif .endif -# Set ALLLANG=no if you want the release documentation to be -# in English only. +# Set ALLLANG=no if you want the documentation (e.g. Handbook, FAQ) to be +# in English only. The language for the release notes is controlled +# by the RELNOTES_LANG variable above. ALLLANG?= yes DOCPORTS= textproc/docproj # Set this to wherever the distfiles required by ${DOCPORTS} live. @@ -105,12 +109,9 @@ DOCDISTFILES?= ${.CURDIR}/../../ports/distfiles # on the boot floppy. WARNING: Breaks on some Athlon (K7) motherboards. AUTO_KEYBOARD_DETECT?= 0 -.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES" +.if !defined(NORELNOTES) DIST_DOCS_ARCH_INDEP= readme errata DIST_DOCS_ARCH_DEP= installation relnotes hardware -.else -DIST_DOCS= ABOUT.TXT ERRATA.TXT LAYOUT.TXT README.TXT HARDWARE.TXT \ - RELNOTES.TXT TROUBLE.TXT UPGRADE.TXT INSTALL.TXT .endif # Things which without too much trouble can be considered variables @@ -219,7 +220,7 @@ EXTRAS= cdrom.1 ftp.1 .if !defined(NODOC) DOCREL= doc.1 -.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES" +.if !defined(NORELNOTES) DOCREL+= doc.2 .endif .endif @@ -239,9 +240,9 @@ rerelease release: @echo "unset NOPORTS, or set at least DOMINIMALDOCPORTS to YES!" @exit 1 .endif -.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES" && defined(NODOC) - @echo "Ports and docs are required for building RELNOTESng. Either" - @echo "unset RELNOTESNG or unset both NOPORTS and NODOC!" +.if !defined(NORELNOTES) && defined(NODOC) + @echo "Docs are required for building the release notes. Either" + @echo "set NORELNOTES or unset NODOC!" @exit 1 .endif .if make(release) @@ -356,13 +357,13 @@ rerelease release: .if defined(NOSRC) echo "export NOSRC=${NOSRC}" >> ${CHROOTDIR}/mk .endif -.if defined(RELNOTESNG) - echo "export RELNOTESNG=${RELNOTESNG}" >> ${CHROOTDIR}/mk +.if defined(NORELNOTES) + echo "export NORELNOTES=${NORELNOTES}" >> ${CHROOTDIR}/mk .endif -.if defined(RELNOTESNG_LANG) - echo "export RELNOTESNG_LANG=${RELNOTESNG_LANG}" >> ${CHROOTDIR}/mk +.if defined(RELNOTES_LANG) + echo "export RELNOTES_LANG=${RELNOTES_LANG}" >> ${CHROOTDIR}/mk .else - echo "export RELNOTESNG_LANG=en_US.ISO_8859-1" >> ${CHROOTDIR}/mk + echo "export RELNOTES_LANG=en_US.ISO_8859-1" >> ${CHROOTDIR}/mk .endif .if defined(NOSHARED) echo "export NOSHARED=${NOSHARED}" >> ${CHROOTDIR}/mk @@ -616,22 +617,14 @@ release.8: write_mfs_in_kernel ln ${RD}/mfsfd/stand/etc/services ${RD}/mfsfd/etc/services ln ${RD}/mfsfd/stand/etc/netconfig ${RD}/mfsfd/etc/netconfig gzip -9c ${.CURDIR}/../COPYRIGHT > ${RD}/mfsfd/stand/help/COPYRIGHT.hlp.gz -.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES" +.if !defined(NORELNOTES) @for i in ${DIST_DOCS_ARCH_INDEP}; do \ - gzip -9c ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/article.txt > ${RD}/mfsfd/stand/help/`echo $${i} | tr 'a-z' 'A-Z'`.TXT.gz; \ + gzip -9c ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/article.txt > ${RD}/mfsfd/stand/help/`echo $${i} | tr 'a-z' 'A-Z'`.TXT.gz; \ done @for i in ${DIST_DOCS_ARCH_DEP}; do \ - gzip -9c ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/${MACHINE_ARCH}/article.txt > ${RD}/mfsfd/stand/help/`echo $${i} | tr 'a-z' 'A-Z'`.TXT.gz; \ + gzip -9c ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/${MACHINE_ARCH}/article.txt > ${RD}/mfsfd/stand/help/`echo $${i} | tr 'a-z' 'A-Z'`.TXT.gz; \ done @mv ${RD}/mfsfd/stand/help/INSTALLATION.TXT.gz ${RD}/mfsfd/stand/help/INSTALL.TXT.gz -.else - @for i in README.TXT RELNOTES.TXT INSTALL.TXT UPGRADE.TXT HARDWARE.TXT; do \ - if [ -f ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ]; then \ - gzip -9c ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} > ${RD}/mfsfd/stand/help/$${i}.gz; \ - else \ - gzip -9c ${.CURDIR}/texts/$${i} > ${RD}/mfsfd/stand/help/$${i}.gz; \ - fi; \ - done .endif -test -f ${.CURDIR}/install.cfg && cp ${.CURDIR}/install.cfg ${RD}/mfsfd @mkdir -p ${RD}/mfsfd/boot @@ -714,27 +707,17 @@ ftp.1: -@ln -s . ${FD}/${BUILDNAME} @cd ${RD} && find floppies -print | cpio -dumpl ${FD} @cd ${RD}/dists && find . -print | cpio -dumpl ${FD} -.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES" +.if !defined(NORELNOTES) @for i in ${DIST_DOCS_ARCH_INDEP}; do \ - cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/article.txt ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \ - cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/article.html ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \ + cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/article.txt ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \ + cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/article.html ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \ done @for i in ${DIST_DOCS_ARCH_DEP}; do \ - cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/${MACHINE_ARCH}/article.txt ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \ - cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/${MACHINE_ARCH}/article.html ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \ + cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/${MACHINE_ARCH}/article.txt ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \ + cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/${MACHINE_ARCH}/article.html ${FD}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \ done @mv ${FD}/INSTALLATION.TXT ${FD}/INSTALL.TXT @mv ${FD}/INSTALLATION.HTM ${FD}/INSTALL.HTM -.else - @for i in ${DIST_DOCS}; do \ - if [ -f ${.CURDIR}/texts/$${i} ]; then \ - cp ${.CURDIR}/texts/$${i} ${FD}; \ - fi; \ - if [ -f ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ]; then \ - echo "=== Platform specifics for ${MACHINE_ARCH}" >> ${FD}/$${i}; \ - cat ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} >> ${FD}/$${i}; \ - fi; \ - done .endif @echo "CD_VERSION = ${BUILDNAME}" > ${FD}/cdrom.inf .if !defined(NOPORTS) @@ -763,27 +746,17 @@ cdrom.1: @cp ${.CURDIR}/fixit.profile ${CD_DISC2}/.profile @echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC1}/cdrom.inf @echo "CD_VERSION = ${BUILDNAME}" > ${CD_DISC2}/cdrom.inf -.if defined(RELNOTESNG) && ${RELNOTESNG} == "YES" +.if !defined(NORELNOTES) @for i in ${DIST_DOCS_ARCH_INDEP}; do \ - cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/article.txt ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \ - cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/article.html ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \ + cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/article.txt ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \ + cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/article.html ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \ done @for i in ${DIST_DOCS_ARCH_DEP}; do \ - cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/${MACHINE_ARCH}/article.txt ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \ - cp ${.CURDIR}/doc/${RELNOTESNG_LANG}/$$i/${MACHINE_ARCH}/article.html ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \ + cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/${MACHINE_ARCH}/article.txt ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.TXT; \ + cp ${.CURDIR}/doc/${RELNOTES_LANG}/$$i/${MACHINE_ARCH}/article.html ${CD_DISC1}/`echo $${i} | tr 'a-z' 'A-Z'`.HTM; \ done @mv ${CD_DISC1}/INSTALLATION.TXT ${CD_DISC1}/INSTALL.TXT @mv ${CD_DISC1}/INSTALLATION.HTM ${CD_DISC1}/INSTALL.HTM -.else - @for i in ${DIST_DOCS}; do \ - if [ -f ${.CURDIR}/texts/$${i} ]; then \ - cp ${.CURDIR}/texts/$${i} ${CD_DISC1}; \ - fi; \ - if [ -f ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} ]; then \ - echo "=== Platform specifics for ${MACHINE_ARCH}" >> ${CD_DISC1}/$${i}; \ - cat ${.CURDIR}/texts/${MACHINE_ARCH}/$${i} >> ${CD_DISC1}/$${i}; \ - fi; \ - done .endif .if ${MACHINE_ARCH} == "alpha" @echo "Setting up Alpha CD disc1 for booting" diff --git a/release/texts/ABOUT.TXT b/release/texts/ABOUT.TXT deleted file mode 100644 index 53a9172..0000000 --- a/release/texts/ABOUT.TXT +++ /dev/null @@ -1,215 +0,0 @@ -o About FreeBSD: - -What is FreeBSD? FreeBSD is an operating system based on 4.4 BSD Lite -for Intel, AMD, Cyrix or NexGen "x86" based PC hardware and Compaq -(formerly DEC) Alpha computers. It works with a very wide variety of PC -peripherals and configurations and can be used for everything from -software development to Internet Service Provision. - -This release of FreeBSD contains everything you need to run such a -system, including full source code for everything. With the source -distribution installed you can literally recompile the entire system -from scratch with one command, making it ideal for students, -researchers or folks who simply want to see how it all works. - -A large collection of 3rd party ported software (the "ports -collection") is also provided to make it easier for you to obtain and -install all your favorite traditional UNIX utilities for FreeBSD. -Over 5000 ports, from editors to programming languages to graphical -applications, make FreeBSD a powerful and comprehensive operating -environment that extends far beyond what's provided by many commercial -versions of UNIX. - -For more documentation on this system it is recommended that you -purchase The Complete FreeBSD, available from local bookstores -and from the FreeBSD Mall (http://www.freebsdmall.com), as well -as the 4.4BSD Document Set from O'Reilly Associates and the USENIX -Association, ISBN 1-56592-082-1. We have no connection with O'Reilly, -we're just satisfied customers! - -If you're new to FreeBSD then you should also read EVERYTHING listed -in the Documentation menu on the boot floppy. It may seem like a lot -to read, but you should at least acquaint yourself with the types of -information available should you later get stuck. Once the system is -installed, you can also revisit this menu and use a WEB browser to -read the installed FAQ (Frequently Asked Questions) and Handbook HTML -documentation sets for FreeBSD. You can also use the browser to visit -other WEB sites on the net (such as http://www.freebsd.org) if you -have an Internet connection. - -NOTE: If you read no other documentation before installing a given -version of FreeBSD, you should at least by all means *READ THE ERRATA* -for that release so that you don't stumble over problems which have -already been found and fixed. The ERRATA.TXT file accompanying your -release (it should be right next to this file) is obviously already -out of date by definition, but other copies are kept updated on the -net and should be consulted as the "current errata" for your release -(this is also what your ERRATA.TXT file says, by the way). These -other copies of the errata are located at: - - 1. http://www.freebsd.org/releases/ - - 2. ftp://ftp.freebsd.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT - (and any sites which keep up-to-date mirrors of this location). - - -DISCLAIMER: While FreeBSD does its best to safeguard against -accidental loss of data, it's still more than possible to WIPE OUT -YOUR ENTIRE DISK with this installation! Please do not proceed to the -final FreeBSD installation menu unless you've adequately backed up any -important data first! We really mean it! - - -o E-mail addresses and tech support info: - -For general questions, please send email to : - - freebsd-questions@FreeBSD.org - -Please also have patience if your questions are not answered right -away - this mailing list is staffed purely by volunteers and they also -have real life schedules to contend with. Questions which are asked -intelligently (e.g. not "My system doesn't work! What's wrong!?") -also stand a far greater chance of being answered. If your question -does not contain enough information to allow the responder to generate -a meaningful answer, they generally won't. - -Bug reports submitted with the send-pr command are also logged and -tracked in our bugs database, and you'll be kept informed of any -changes in status during the life of the bug (or feature request). - -Technical comments on this release should be sent (in English!) to: - - freebsd-hackers@FreeBSD.org - -Bug reports should be sent using the `send-pr' command or the Web page -at http://www.freebsd.org/send-pr.html. If you cannot use either of -these two methods, you may also send mail to: - - freebsd-bugs@FreeBSD.org - - -PLEASE ALSO BE SURE TO INDICATE WHICH VERSION OF FREEBSD YOU'RE -RUNNING IN ANY BUG REPORTS OR QUESTIONS! - -Sorry for the caps, but you'd be amazed at how many times people -forget this and there are many different release versions of FreeBSD -out there now. It's imperative that we know what you're running so -that we tell if you're suffering from a bug which has already been -fixed. - - -o WWW Resources: - -Our WEB site, http://www.freebsd.org, is also a very good source for -updated information and provides a number of advanced documentation -searching facilities. If you wish to use Netscape as your browser, -several versions may be found in the ports collection under -/usr/ports/www if you've installed the ports collection on your -machine (always a good idea). - -Several other non-commercial browsers are also available in -/usr/ports/www and may be compiled and installed in the same fashion. -Many are also available as pre-compiled packages - see the Packages -entry in the Configuration menu for more details. - -The Handbook and FAQ are also available as on-line documents in -/usr/share/doc and can be read using the ``file:/usr/share/doc'' -syntax in any HTML capable browser. - - -o Distributions: - -A typical FreeBSD distribution directory looks like this: - -ABOUT.TXT bin compat3x games proflibs -HARDWARE.TXT compat1x info src tools -INSTALL.TXT compat20 dict manpages packages -README.TXT compat21 des doc -RELNOTES.TXT compat22 floppies ports -XF86336 - -If you want to do a CDROM, FTP or NFS installation from this -distribution directory, all you need to do is make a pair of 1.44MB -floppies from the floppies/kern.flp and floppies/mfsroot.flp image -files (see floppies/README.TXT for instructions on how to do this), -boot it and follow the instructions. - -If you're trying to do some other type of installation, or are just -curious about how the distribution is organized in general, what -follows is a more thorough description of each item in more detail: - -The *.TXT files obviously contain documentation (ABOUT.TXT being what -you're reading now). - -The XF86336 directory contains the XFree86 project's 3.3.6 release and -consists of a series of gzip'd tar files which contain each component -of the XFree86 distribution. - -The bin, dict, des, doc, games, info, manpages, proflibs, and src -directories contain the primary distribution components of FreeBSD -itself and are split into smaller files for easy packing onto floppies -(should that be necessary). - -The compat1x, compat20, compat21, compat22, and compat3x directories -contain distributions for compatibility with older releases and are -distributed as single gzip'd tar files - they can be installed during -release time or later by running their `install.sh' scripts. - -A typical distribution (we'll use the info distribution as an example) -looks like this: - -CHECKSUM.MD5 info.ab info.ad info.inf install.sh -info.aa info.ac info.ae info.mtree - -The CHECKSUM.MD5 file contains MD5 signatures for each file, should -data corruption be suspected, and is purely for reference - it is not -used by the actual installation and does not need to be copied with -the rest of the distribution files. The info.a* files are split, -gzip'd tar files, the contents of which can be viewed by doing: - - cat info.a* | tar tvzf - - -During installation, they are automatically concatenated and extracted -by the installation procedure. - -The info.inf file is also necessary since it is read by the installation -program in order to figure out how many pieces to look for when fetching and -concatenating the distribution. When putting distributions onto floppies, -the .inf file MUST occupy the first floppy of each distribution set! - -The info.mtree file is another non-essential file which is provided -for user reference. It contains the MD5 signatures of the *unpacked* -distribution files and can be later used with the mtree(1) program -to verify the installation permissions and checksums against any possible -modifications to the file. When used with the bin distribution, this can -be an excellent way of detecting trojan horse attacks on your system. - -Finally, the install.sh file is for use by those who want to install the -distribution after installation time. To install the info distribution from -CDROM after a system was installed, for example, you'd do: - - cd /cdrom/info - sh install.sh - -And that's all there is to it! Each distribution contains its own -install.sh file for this. - - -The floppies subdirectory contains the floppy installation images and -the floppies/README.TXT file should be read for further information -on them. - -The packages and ports directories contain the FreeBSD packages and -ports collections. Packages may be installed from the packages directory -by running the sysinstall utility with the argument ``configPackages'' -or by feeding the individual filenames to the pkg_add(1) command. - -The ports collection may be installed like any other distribution -and requires about 100MB unpacked. More information on the ports collection -may be obtained from http://www.freebsd.org/ports or locally from -file:/usr/share/doc/handbook if you've installed the doc distribution. - -Last of all, the tools directory contains various DOS tools for -discovering disk geometries, installing boot managers and the like. -It is purely optional and provided only for user convenience. diff --git a/release/texts/ERRATA.TXT b/release/texts/ERRATA.TXT deleted file mode 100644 index 72f0096..0000000 --- a/release/texts/ERRATA.TXT +++ /dev/null @@ -1,30 +0,0 @@ -If you read no other documentation before installing this -version of FreeBSD, you should at least by all means *READ -THE ERRATA* for this release so that you don't stumble over -problems which have already been found and fixed. This ERRATA.TXT -file is obviously already out of date by definition, but other -copies are kept updated on the net and should be consulted as -the "current errata" for your release. These other copies of -the errata are located at: - - 1. http://www.freebsd.org/releases/ - - 2. ftp://ftp.freebsd.org/pub/FreeBSD/releases/<your-release>/ERRATA.TXT - (and any sites which keep up-to-date mirrors of this location). - -Any changes to this file are also automatically emailed to: - - freebsd-current@freebsd.org - -For all CERT security advisories, see: - - ftp://ftp.freebsd.org/pub/FreeBSD/CERT/ - -For the latest security incident information. - ----- Security Advisories: - -Current active security advisories: None - ----- System Update Information: - diff --git a/release/texts/FLOPPIES.TXT b/release/texts/FLOPPIES.TXT deleted file mode 100644 index 4a60e5c..0000000 --- a/release/texts/FLOPPIES.TXT +++ /dev/null @@ -1,57 +0,0 @@ -For a normal CDROM or network installation, all you need to copy onto -actual floppies from this directory are the kern.flp and mfsroot.flp -images (for 1.44MB floppies). - -Get two blank, freshly formatted floppies and image copy kern.flp -onto one and mfsroot.flp onto the other. These images are NOT DOS -files! You cannot simply copy them to a DOS or UFS floppy as -regular files, you need to "image" copy them to the floppy with -fdimage.exe under DOS (see the tools/ directory on your CDROM or -FreeBSD FTP mirror) or the `dd' command in UNIX. - -For example: - -To create the kern floppy image from DOS, you'd do something like -this: - -C> fdimage kern.flp a: - -Assuming that you'd copied fdimage.exe and kern.flp into a directory -somewhere. You would do the same for mfsroot.flp, of course. - -If you're creating the boot floppy from a UNIX machine, you may find -that one of the following: - - dd if=floppies/kern.flp of=/dev/fd0 - dd if=floppies/kern.flp of=/dev/rfd0 - dd if=floppies/kern.flp of=/dev/floppy - -work well, depending on your hardware and operating system environment -(different versions of UNIX have totally different names for the -floppy drive - neat, huh? :-). - -If you're on an ALPHA machine which can network-boot its floppy images -or you have a 2.88MB or LS-120 floppy capable of taking a 2.88MB image -on an x86 machine, you may still wish to use the older (but now -twice as large) boot.flp image which we also provide. That contains -the contents of kern.flp and mfsroot.flp on a single floppy, -essentially. This file should also be used as the boot file for those -mastering "El Torito" bootable CD images. See the mkisofs(1) command -for more information. - -Going to two installation boot floppies is a step we definitely -would have rather avoided but we simply no longer could due to -general code bloat and FreeBSD's many new device drivers in GENERIC. - -One positive side-effect of this new organizational scheme, however, -is that it also allows one to easily make one's own kern or MFS -floppies should a need to customize some aspect of the installation -process or use a custom kernel for an otherwise unsupported piece of -hardware arise. As long as the kernel is compiled with -``options MFS'' and ``options MFS_ROOT'', it will properly look for -and boot an mfsroot.flp image in memory when run (see how the -/boot/loader.rc file in kern.flp does its thing). The mfsroot.flp -image is also just a gzip'd filesystem image which is used as root, -something which can be made rather easily using mdconfig(8). -If none of that makes any sense to you then don't worry about it - -just use the kern.flp and mfsroot.flp images as described above. diff --git a/release/texts/HARDWARE.TXT b/release/texts/HARDWARE.TXT deleted file mode 100644 index 16d9f61..0000000 --- a/release/texts/HARDWARE.TXT +++ /dev/null @@ -1,1083 +0,0 @@ -Table of Contents ------------------ -0. Document Conventions -1. Default Configuration (GENERIC kernel) -2. Using UserConfig to change FreeBSD kernel settings -3. LINT - other possible configurations -4. Supported Hardware - -See TROUBLE.TXT for Q&A on known hardware problems. - -========================================================================= - -0. Document Conventions --- -------------------- - -We have `underlined' text which represents user input with `-' symbols -throughout this document to differentiate it from the machine output. - -1. Default (GENERIC) Configuration --- ------------------------------- - -The following table contains a list of all of the devices that are -present in the GENERIC kernel. This is the essential part of the -operating system that is placed in your root partition during the -installation process. A compressed version of the GENERIC kernel is -also used on the installation floppy diskette and DOS boot image. - -The table describes the various parameters used by the driver to -communicate with the hardware in your system. There are four -parameters in the table, though not all are used by each and every -device: - - Port The starting I/O port used by the device, shown in hexadecimal. - - IOMem The lowest (or starting) memory address used by the device, - also shown in hexadecimal. - - IRQ The interrupt the device uses to alert the driver to an event, - given in decimal. - - DRQ The DMA (direct memory access) channel the device uses to move - data to and from main memory, also given in decimal. - -If an entry in the table has `n/a' for a value then it means that the -parameter in question does not apply to that device. A value of `dyn' -means that the correct value should be determined automatically by the -kernel when the system boots and that you don't need to worry about -it. - -If an entry is marked with an *, it means that support is currently -not available for it but should be back as soon as someone converts -the driver to work within the new 4.0 framework. - -FreeBSD GENERIC kernel: - - Port IRQ DRQ IOMem Description - ---- --- --- ----- --------------------------------- -fdc0 3f0 6 2 n/a Floppy disk controller -ata0 170 14 n/a n/a ATA/ATAPI controller -ata1 170 15 n/a n/a ATA/ATAPI controller -atadisk0 n/a n/a n/a n/a ATA disk drives -atapicd0 n/a n/a n/a n/a ATAPI CDROM drives -atapifd0 n/a n/a n/a n/a ATAPI floppy drives -atapist0 n/a n/a n/a n/a ATAPI tape drives - -adv0 n/a n/a n/a n/a AdvanSys Narrow SCSI controllers -adw0 n/a n/a n/a n/a AdvanSys Wide SCSI controllers -amd0 n/a n/a n/a n/a AMD 53C974 (Tekram DC390(T)) -ncr0 n/a n/a n/a n/a NCR PCI SCSI controller -bt0 330 dyn dyn dyn Buslogic SCSI controller -aha0 330 dyn 5 dyn Adaptec 154x/1535 SCSI controller -ahb0 dyn dyn dyn dyn Adaptec 174x SCSI controller -ahc0 dyn dyn dyn dyn Adaptec 274x/284x/294x SCSI controller -aic0 340 11 dyn dyn Adaptec 152x/AIC-6360/AIC-6260 SCSI - controller -isp0 dyn dyn dyn dyn QLogic 10X0, 1240 Ultra SCSI, 1080/1280 - Ultra2 SCSI, 12160 Ultra3 SCSI, 2X00 - Fibre Channel SCSI controller -dpt0 dyn dyn n/a n/a DPT RAID SCSI controllers -amr0 dyn dyn n/a n/a AMI MegaRAID controllers -mlx0 dyn dyn n/a dyn Mylex DAC960 RAID controllers -twe0 dyn dyn n/a n/a 3ware Escalade RAID controllers -asr0 dyn dyn dyn dyn DPT SmartRaid V, VI, and - Adaptec SCSI RAID -mly0 dyn dyn dyn dyn Mylex AcceleRAID/eXtremeRAID -aac dyn dyn dyn dyn Adaptec FSA family PCI SCSI RAID -ncv dyn dyn n/a n/a NCR 53C500 based PC-Card SCSI -nsp dyn dyn n/a dyn Workbit Ninja SCSI-3 based PC-Card SCSI -stg dyn dyn n/a n/a TMC 18C30/50 based ISA/PC-Card SCSI - -wt0 300 5 1 dyn Wangtek and Archive QIC-02/QIC-36 - -psm0 60 12 n/a n/a PS/2 Mouse - -mcd0 300 10 n/a n/a Mitsumi CD-ROM -matcd0 230 n/a n/a n/a Matsushita/Panasonic CD-ROM -scd0 230 n/a n/a n/a Sony CD-ROM - -sio0 3f8 4 n/a n/a Serial Port 0 (COM1) -sio1 2f8 3 n/a n/a Serial Port 1 (COM2) - -ppc0 dyn 7 n/a n/a Printer ports - -dc0 n/a n/a n/a n/a DEC/Intel 21143 cards and workalikes -de0 n/a n/a n/a n/a DEC DC21x40 PCI based cards - (including 21140 100bT cards) -ed0 280 10 dyn d8000 WD & SMC 80xx; Novell NE1000 & - NE2000; 3Com 3C503; HP PC Lan+ -ep0 300 10 dyn dyn 3Com 3C509, 3C529, 3C556, 3C562D, - 3C563D, 3C572, 3C574X, 3C579, 3C589 -ex0 dyn dyn dyn n/a Intel EtherExpress Pro/10 cards -fe0 300 dyn n/a n/a Allied-Telesyn AT1700, RE2000 and - Fujitsu FMV-180 series cards. -fxp0 dyn dyn n/a dyn Intel EtherExpress Pro/100B and - Intel PRO/100+ Management Adapter -ie0 300 10 dyn d0000 AT&T StarLAN 10 and EN100; - 3Com 3C507; NI5210; - Intel EtherExpress (8/16,16[TP]) cards -lnc0 280 10 n/a dyn Lance/PCnet cards - (Isolan, Novell NE2100, NE32-VL, - some PCnet-PCI cards) -nge0 dyn dyn n/a dyn NatSemi DP83820 gigabit ethernet -pcn0 dyn dyn n/a dyn AMD PCnet/FAST, PCnet/FAST+, - PCnet/FAST III, PCnet/PRO, PCnet/Home, - and HomePNA cards -rl0 dyn dyn n/a dyn RealTek 8129/8139 Fast Ethernet -sf0 dyn dyn n/a dyn Adaptec AIC-6915 Fast Ethernet -sis0 dyn dyn n/a dyn SiS 900/SiS 7016 Fast Ethernet -sn0 0x300 10 n/a n/a SMC 91xx Ethernet -sk0 dyn dyn n/a dyn SysKonnect gigabit ethernet -ste0 dyn dyn n/a dyn Sundance ST201 Fast Ethernet -ti0 dyn dyn n/a dyn Alteon Tigon 1 & 2 gigabit ethernet -tl0 dyn dyn n/a dyn TI TNET100 'ThunderLAN' cards. -tx0 dyn dyn n/a dyn SMC 9432 'Epic' Fast Ethernet -wb0 dyn dyn n/a dyn Winbond W89C840F PCI based cards. -vr0 dyn dyn n/a dyn VIA VT3043/VT86C100A PCI based cards. -vx0 dyn dyn n/a dyn 3Com 3c59x ((Fast) Etherlink III) -xe0 dyn dyn n/a dyn Xircom CreditCard adapters(16bit) -xl0 dyn dyn n/a dyn 3Com 3c900, 3c905, 3c905B, 3c905C, - 3c980, 3cSOHO100 ((Fast) Etherlink XL) -cs0 0x300 dyn n/a n/a Crystal Semiconductor CS89x0-based - cards. ---- End of table --- - - -If the hardware in your computer is not set to the same settings as -those shown in the table and the item in conflict is not marked 'dyn', -you will have to either reconfigure your hardware or use UserConfig -to reconfigure the kernel to match the way your hardware is currently set -(see the next section). - -If the settings do not match, the kernel may be unable to locate -or reliably access the devices in your system. - - -2. Using UserConfig to change FreeBSD kernel settings --- -------------------------------------------------- - -The FreeBSD kernel on the install floppy contains drivers for every -piece of hardware that could conceivably be used to install the rest -of the system with. Unfortunately, PC hardware being what it is, some -of these devices can be difficult to detect accurately, and for some, -the process of detecting another can cause irreversible confusion. - -To make this process easier, FreeBSD provides UserConfig. With this -tool the user can configure and disable device drivers before -the kernel is loaded, avoiding potential conflicts, and eliminating -the need to reconfigure hardware to suit the default driver settings. - -Once FreeBSD is installed, it will remember the changes made using -UserConfig, so that they only need be made once. - -It is important to disable drivers that are not relevant to a system -in order to minimize the possibility of interference, which can cause -problems that are difficult to track down. - -UserConfig features a command line interface for users with serial -consoles or a need to type commands, and a full screen 'visual' -interface, which provides point-and-shoot configuration functionality. - -Here is a sample UserConfig screen shot in 'visual' mode: - ----Active Drivers---------------------------10 Conflicts------Dev---IRQ--Port-- - Storage : (Collapsed) - Network : - NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed0 5 0x280 - NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters CONF ed1 5 0x300 - Communications : (Collapsed) - Input : (Collapsed) - Multimedia : ----Inactive Drivers-------------------------------------------Dev-------------- - Storage : - Network : (Collapsed) - Communications : - Input : - Multimedia : - - ----Parameters-for-device-ed0--------------------------------------------------- - Port address : 0x280 Memory address : 0xd8000 - IRQ number : 5 Memory size : 0x2000 - Flags : 0x0000 -------------------------------------------------------------------------------- - IO Port address (Hexadecimal, 0x1-0x2000) - [TAB] Change fields [Q] Save device parameters - - - The screen is divided into four sections : - - - Active Drivers. Listed here are the device drivers that are currently - enabled, and their basic parameters. - - Inactive Drivers. These drivers are present, but are disabled. - - Parameter edit field. This area is used for editing driver parameters. - - Help area. Keystroke help is displayed here. - -One of the Active and Inactive lists is always in use, and the current -entry in the list will be shown with a highlight bar. If there are -more entries in a list than can be shown, it will scroll. The bar can -be moved up and down using the cursor keys, and moved between lists -with the TAB key. - -Drivers in the Active list may be marked "CONF". This indicates that -one or more of their parameters conflicts with another device, and -indicates a potential for problems. The total number of conflicts is -displayed at the top of the screen. - -As a general rule, conflicts should be avoided, either by disabling -conflicting devices that are not present in the system, or by altering -their configuration so that they match the installed hardware. - -In the list areas, drivers are grouped by their basic function. -Groups can be 'Collapsed' to simplify the display (this is the default -state for all groups). If a group is collapsed, it will be shown with -'(Collapsed)' in the list, as above. To Expand a Collapsed group, -position the highlight bar over the group heading and press Enter. To -Collapse it again, repeat the process. - -When a device driver in the Active list is highlighted, its full -parameters are displayed in the Parameter edit area. Note that not -all drivers use all possible parameters, and some hardware supported -by drivers may not use all the parameters the driver supports. - -To disable a driver, go to the Active list, Expand the group it is in, -highlight the driver and press Del. The driver will move to its group -in the Inactive list. (If the group is collapsed or off the screen, -you may not see the driver in its new location.) - -To enable a driver, go to the Inactive list, Expand the group it is -in, highlight the driver and press Enter. The highlight will move to -the Active list, and the driver you have just enabled will be -highlighted, ready to be configured. - -To configure a driver, go to the Active list, Expand the group it is -in, highlight the driver and press Enter. The cursor will move to the -Parameter edit area, and the device's parameters may be edited. - -While editing parameters, the TAB and cursor keys can be used to move -between fields. Most numeric values (except IRQ) are entered in -hexadecimal, as indicated by the '0x' at the beginning of the field. -The allowable values for a given field are show in the Key Help area -when the field is active. - -To finish configuring a driver, press 'Q'. - -Note that PCI, Microchannel and EISA devices can be probed reliably, -therefore they are not shown in the table above nor can their settings -be changed using UserConfig. - - -3. LINT - other possible configurations --- ------------------------------------ - -The following drivers are not in the GENERIC kernel but remain -available to those who do not mind compiling a custom kernel (see -section 6 of FreeBSD.FAQ). The LINT configuration file -(/sys/i386/conf/LINT) also contains prototype entries for just about -every device supported by FreeBSD and is a good general reference. - -The device names and a short description of each are listed below. The port -numbers, etc, are not meaningful here since you will need to compile a -custom kernel to gain access to these devices anyway and can thus -adjust the addresses to match the hardware in your computer in the process. -The LINT file contains prototype entries for all of the below which you -can easily cut-and-paste into your own file (or simply copy LINT and edit -it to taste): - -ata: Alternate high-performance driver for IDE controllers -ctx: Cortex-I frame grabber -cx: Cronyx/Sigma multiport sync/async -cy: Cyclades high-speed serial driver -el: 3Com 3C501 -fea: DEC DEFEA EISA FDDI adapter -fpa: DEC DEFPA PCI FDDI adapter -gp: National Instruments AT-GPIB and AT-GPIB/TNT board -gsc: Genius GS-4500 hand scanner -gus: Gravis Ultrasound - Ultrasound, Ultrasound 16, Ultrasound MAX -gusxvi: Gravis Ultrasound 16-bit PCM -hea: Efficient ENI-155p ATM PCI adapter -hfa: FORE PCA-200E ATM PCI adapter -ifpi: isdn4bsd AVM Fritz!card PCI driver -ifpnp: isdn4bsd AVM Fritz!card PnP driver -ihfc: isdn4bsd Cologne Chip HFC ISA driver -isic: isdn4bsd Siemens/Infineon ISDN chipset driver (ISAC+HSCX/IPAC) -iwic: isdn4bsd Winbond W6692 PCI ISDN chip driver -iavc: isdn4bsd AVM B1 and AVM T1 active CAPI-based ISDN cards -joy: Joystick -labpc: National Instrument's Lab-PC and Lab-PC+ -meteor: Matrox Meteor frame-grabber card -bktr: Brooktree Bt848 / Bt 878 based frame-grabber cards. -mpu: Roland MPU-401 stand-alone card -mse: Microsoft, Logitech, ATI bus mouse ports -mss: Microsoft Sound System -opl: Yamaha OPL-2 and OPL-3 FM - SB, SB Pro, SB 16, ProAudioSpectrum -pas: ProAudioSpectrum PCM and MIDI -pca: PCM audio ("/dev/audio") through your PC speaker -pcm: PCM audio on most modern PCI/ISA audio codecs -psm: PS/2 mouse port -rc: RISCom/8 multiport card -sb: SoundBlaster PCM - SoundBlaster, SB Pro, SB16, ProAudioSpectrum -sbmidi: SoundBlaster 16 MIDI interface -sbxvi: SoundBlaster 16 -si: Specialix SI/XIO/SX (old and enhanced ISA, PCI, EISA) serial -sym: Alternate high-performance driver for NCR/LSI Logic SCSI controllers -spigot: Creative Labs Video Spigot video-acquisition board -uart: Stand-alone 6850 UART for MIDI -wds: Western Digital WD7000 IDE - ---- end of list --- - - -4. Supported Hardware --- ------------------ - -FreeBSD currently runs on a wide variety of ISA, VLB, EISA, -Microchannel 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. - -What follows is a list of all peripherals currently known to work with -FreeBSD. Other configurations may also work, we have simply not as yet -received confirmation of this. - - -4.1. Disk Controllers ----- ---------------- - -IDE -ATA controllers: - Acerlabs Aladdin - AMD 756 - CMD 646 - CMD 648 ATA66 - CMD 649 ATA100 - Cypress 82C693 - Cyrex 5530 - HighPoint HPT366 - HighPoint HPT370 - Intel PIIX - Intel PIIX3 - Intel PIIX4 - Intel ICH - Intel ICH2 - Promise ATA100 OEM chip (pdc20265) - Promise Fasttrak-33 - Promise Fasttrak-66 - Promise Fasttrak-100 - Promise Ultra-33 - Promise Ultra-66 - Promise Ultra-100 - ServerWorks ROSB4 ATA33 - SiS 5591 - VIA 82C586 - VIA 82C686a - VIA 82C686b - -WD1003 (any generic MFM/RLL - obsolete) -WD1007 (any generic ESDI - obsolete) -* Note: now that the wd driver has been replaced by the ata driver framework, -which does not have bad144 support, the true MFM/RLL/ESDI drives/adapters -have become obsolete. - -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/2920C/294x/2950/19160/29160/3940/3950/39160 - Narrow/Wide/Twin series EISA/VLB/PCI SCSI controllers. -Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. -Adaptec 1510 series ISA SCSI controllers (not for bootable devices) -Adaptec 152x series ISA SCSI controllers -Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x -and SoundBlaster SCSI cards. - -Adaptec 2100S, 3200S, and 3400S SCSI RAID controllers. -Adaptec 2400A ATA-100 RAID controller. - -Adaptec FSA family RAID controllers: - Adaptec AAC-2622 - Adaptec AAC-364 - Adaptec AAC-3642 - Dell PERC 2/QC - Dell PERC 2/Si - Dell PERC 3/Di - Dell PERC 3/QC - Dell PERC 3/Si - HP NetRAID-4M - -AdvanSys SCSI controllers (all models). - -BusLogic MultiMaster controllers: - -[ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] - -BusLogic MultiMaster "W" Series Host Adapters: - BT-948, BT-958, BT-958D -BusLogic MultiMaster "C" Series Host Adapters: - BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, - BT-540CF -BusLogic MultiMaster "S" Series Host Adapters: - BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, - BT-542B -BusLogic MultiMaster "A" Series Host Adapters: - BT-742A, BT-542B - -AMI FastDisk controllers that are true BusLogic MultiMaster clones are also -supported. - -DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and -SmartRAID IV SCSI/RAID controllers. - -DPT SmartRAID V and VI SCSI RAID controllers: - PM1554, PM2554, PM2654, PM2865, PM2754, PM3755, PM3757 - -AMI MegaRAID Express and Enterprise family RAID controllers: - MegaRAID Series 418 - MegaRAID Enterprise 1200 (Series 428) - MegaRAID Enterprise 1300 (Series 434) - MegaRAID Enterprise 1400 (Series 438) - MegaRAID Enterprise 1500 (Series 467) - MegaRAID Enterprise 1600 (Series 471) - MegaRAID Elite 1500 (Series 467) - MegaRAID Elite 1600 (Series 493) - MegaRAID Express 100 (Series 466WS) - MegaRAID Express 200 (Series 466) - MegaRAID Express 300 (Series 490) - MegaRAID Express 500 (Series 475) - Dell PERC - Dell PERC 2/SC - Dell PERC 2/DC - Dell PERC 3/DCL - HP NetRAID-1si - HP NetRAID-3si - HP Embedded NetRAID -Booting from these controllers is supported. - -Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x -firmware: - DAC960P - DAC960PD - DAC960PDU - DAC960PL - DAC960PJ - DAC960PG - AcceleRAID 150 - AcceleRAID 250 - eXtremeRAID 1100 -This list includes controllers sold by Digital/Compaq in Alpha systems -in the StorageWorks family, eg. KZPSC, KZPAC. EISA adaptes are not -supported. - -Mylex PCI to SCSI RAID controllers with 6.x firmware: - AcceleRAID 160 - AcceleRAID 170 - AcceleRAID 352 - eXtremeRAID 2000 - eXtremeRAID 3000 -Compatible Mylex controllers not listed should work, but have not been -verified. - -3ware Escalade ATA RAID controllers. All members of the 5000, -6000, and 7000 series are supported. - -Qlogic Controllers and variants: - Qlogic 1020, 1040 SCSI and Ultra SCSI host adapters - Qlogic 1240 dual Ultra SCSI controllers - Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD controllers - Qlogic 12160 Ultra3 LVD controllers - Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI controllers - Performance Technology SBS440 ISP1000 variants - Performance Technology SBS450 ISP1040 variants - Performance Technology SBS470 ISP2100 variants - Antares Microsystems P-0033 ISP2100 variants - -LSI/SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C825, 53C825a, -53C860, 53C875, 53C875a, 53C876, 53C885, 53C895, 53C895a, 53C896, -53C1010-33, 53C1010-66, 53C1000, 53C1000R PCI SCSI controllers, -either embedded on mainboard, or on add-on boards: - ASUS SC-200, SC-896 - Data Technology DTC3130 (all variants) - DawiControl DC2976UW - Diamond FirePort (all) - NCR cards (all) - Symbios cards (all) - Tekram DC390W, 390U, 390F, 390U2B, 390U2W, 390U3D and 390U3W - Tyan S1365 - -NCR 53C500 based PC-Card SCSI host adapters: - IO DATA PCSC-DV - KME KXLC002(TAXAN ICD-400PN, etc.), KXLC004 - Macnica Miracle SCSI-II mPS110 - Media Intelligent MSC-110, MSC-200 - NEC PC-9801N-J03R - New Media Corporation BASICS SCSI - Qlogic Fast SCSI - RATOC REX-9530, REX-5572 (as SCSI only) - -TMC 18C30, 18C50 based ISA/PC-Card SCSI host adapters: - Future Domain SCSI2GO - IBM SCSI PCMCIA Card - ICM PSC-2401 SCSI - Melco IFC-SC - RATOC REX-5536, REX-5536AM, REX-5536M, REX-9836A - -DTC 3290 EISA SCSI controller in 1542 emulation mode. - -Tekram DC390 and DC390T controllers (maybe other cards based on the -AMD 53c974 as well). - -Workbit Ninja SCSI-3 based PC-Card SCSI host adapters: - Alpha-Data AD-PCS201 - IO DATA CBSC16 - -With all supported SCSI controllers, full support is provided for -SCSI-I & SCSI-II peripherals, including hard disks, optical disks, -tape drives (including DAT and 8mm Exabyte), medium changers, processor -target devices and CDROM drives. WORM devices that support CDROM commands -are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW -writing support is provided by cdrecord, which is in the ports tree. - -The following CD-ROM type systems are supported at this time: -(cd) SCSI interface (also includes SoundBlaster SCSI) -(matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary - interface (562/563 models) -(scd) Sony proprietary interface (all models) -(acd) ATAPI IDE interface - -Unmaintained drivers, they might or might not work for your hardware: -NatSemi DP83820 gigabit ethernet -(mcd) Mitsumi proprietary CD-ROM interface (all models) - -4.2. Network cards ----- ------------- - -Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec -AIC-6915 Fast Ethernet controller chip, including the following: - ANA-62011 64-bit single port 10/100baseTX adapter - ANA-62022 64-bit dual port 10/100baseTX adapter - ANA-62044 64-bit quad port 10/100baseTX adapter - ANA-69011 32-bit single port 10/100baseTX adapter - ANA-62020 64-bit single port 100baseFX adapter - -Allied-Telesyn AT1700 and RE2000 cards - -Alteon Networks PCI gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 -chipsets, including the following: - 3Com 3c985-SX (Tigon 1 and 2) - Alteon AceNIC (Tigon 1 and 2) - Alteon AceNIC 1000baseT (Tigon 2) - DEC/Compaq EtherWORKS 1000 - Farallon PN9000SX - NEC Gigabit Ethernet - Netgear GA620 (Tigon 2) - Netgear GA620T (Tigon 2, 1000baseT) - Silicon Graphics Gigabit Ethernet - Asante PCI 1000BASE-SX Gigabit Ethernet Adapter - Asante GigaNIX1000T Gigabit Ethernet Adapter - -AMD PCnet/PCI (79c970 & 53c974 or 79c974) -AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, HomePCI, and HomePNA. - -SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, -WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT -based clones. SMC Elite Ultra is also supported. - -RealTek 8129/8139 Fast Ethernet NICs including the following: - Accton "Cheetah" EN1207D (MPX 5030/5038; RealTek 8139 clone) - Allied Telesyn AT2550 - Allied Telesyn AT2500TX - Genius GF100TXR (RTL8139) - KTX-9130TX 10/100 Fast Ethernet - NDC Communications NE100TX-E - Netronix Inc. EA-1210 NetEther 10/100 - OvisLink LEF-8129TX - OvisLink LEF-8139TX - SMC EZ Card 10/100 PCI 1211-TX - -Lite-On 82c168/82c169 PNIC Fast Ethernet NICs including the following: - Kingston KNE110TX - LinkSys EtherFast LNE100TX - Matrox FastNIC 10/100 - NetGear FA310-TX Rev. D1 - -Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs - Accton EN1217 (98715A) - Adico AE310TX (98715A) - Compex RL100-TX - CNet Pro120A (98713 or 98713A) - CNet Pro120B (98715) - NDC Communications SFA100A (98713A) - SVEC PN102TX (98713) - -Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs including the following: - LinkSys EtherFast LNE100TX Version 2 - -Winbond W89C840F Fast Ethernet NICs including the following: - Trendware TE100-PCIE - -VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" Fast Ethernet -NICs including the following: - AOpen/Acer ALN-320 - D-Link DFE-530TX - Hawking Technologies PN102TX - -Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs - -National Semiconductor DP83815 Fast Ethernet NICs including the following: - NetGear FA311-TX - NetGear FA312-TX - -National Semiconductor DP83820 and DP83821 Gigabit Ethernet NICs including -the following: - D-Link DGE-500T - SMC EZ Card 1000 (SMC9462TX) - Asante FriendlyNet GigaNIC 1000TA and 1000TPC - Addtron AEG320T - -Sundance Technologies ST201 PCI Fast Ethernet NICs including -the following: - D-Link DFE-550TX - -SysKonnect SK-984x PCI gigabit Ethernet cards including the following: - SK-9841 1000baseLX single mode fiber, single port - SK-9842 1000baseLX single mode fiber, dual port - SK-9843 1000baseSX multimode fiber, single port - SK-9844 1000baseSX multimode fiber, dual port - SK-9821 1000baseT copper, single port - SK-9822 1000baseT copper, dual port - -Texas Instruments ThunderLAN PCI NICs, including the following: - Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port - Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP - Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC - Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP - Racore 8165 10/100baseTX - Racore 8148 10baseT/100baseTX/100baseFX multi-personality - -ADMtek Inc. AL981-based PCI Fast Ethernet NICs - -ADMtek Inc. AN985-based PCI Fast Ethernet NICs including the following: - LinkSys EtherFast LNE100TX v4.0/4.1 - -ADMtek Inc. AN986-based USB Ethernet NICs including the following: - Billionton USB100 - D-Link DSB-650TX - LinkSys USB100TX - Melco Inc. LUA-TX - SMC 2202USB - -CATC USB-EL1210A-based USB Ethernet NICs including the following: - Belkin F5U011 - Belkin F5U111 - CATC Netmate - CATC Netmate II - -Kawasaki LSI KL5KUSB101B-based USB Ethernet NICs including -the following: - 3Com 3c19250 - ADS Technologies USB-10BT - ATen UC10T - Corega USB-T - D-Link DSB-650 - Entrega NET-USB-E45 - LinkSys USB10T - Netgear EA101 - Peracom USB Ethernet Adapter - SMC 2102USB - SMC 2104USB - -ASIX Electronics AX88140A PCI NICs, including the following: - Alfa Inc. GFC2204 - CNet Pro110B - -DEC EtherWORKS III NICs (DE203, DE204, and DE205) -DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) -DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc) -DEC FDDI (DEFPA/DEFEA) NICs - -DEC/Intel 21143 based Fast Ethernet NICs, including the following: - DEC DE500-BA - Compaq Presario 7900 series built-in Ethernet - D-Link DFE-570TX - Kingston KNE100TX - LinkSys EtherFast 10/100 Instant GigaDrive built-in Ethernet - -Davicom DM9100 and DM9102 PCI Fast Ethernet NICs, including the -following: - Jaton Corporation XPressNet - -Efficient ENI-155p ATM PCI - -FORE PCA-200E ATM PCI - -Fujitsu MB86960A/MB86965A, including the following: - CONTEC C-NET(PC)C Ethernet - Eiger Labs EPX-10BT - Fujitsu FMV-J182, FMV-J182A, MBH10302, MBH10303 Ethernet PCMCIA - Fujitsu Towa LA501 Ethernet - HITACHI HT-4840-11 - NextCom J Link NC5310 - RATOC REX-5588, REX-9822, REX-4886, REX-R280 - TDK LAK-CD021, LAK-CD021A, LAK-CD021BX - -HP PC Lan+ cards (model numbers: 27247B and 27252A). - -Intel EtherExpress (not recommended due to driver instability) -Intel EtherExpress Pro/10 -Intel EtherExpress Pro/100B PCI Fast Ethernet -Intel PRO/100+ Management Adapter -Intel Gigabit Ethernet (PRO/1000, PRO1000/F, PRO1000/T) - -Isolan AT 4141-0 (16 bit) -Isolink 4110 (8 bit) - -Novell NE1000, NE2000, and NE2100 Ethernet interface. -PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, -Winbond W89C940, Surecom NE-34, VIA VT86C926, etc. - -3Com 3C501 cards - -3Com 3C503 Etherlink II - -3Com 3C507 Etherlink 16/TP - -3Com 3C509, 3C529, 3C556, 3C562D, 3C563D, 3C572, 3C574X, 3C579, -3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA), -3C590/592/595/900/905/905B/905C PCI, -3C556-556B MiniPCI, -3C575TX/575B/XFE575BT/575C/656/656B/656C Cardbus, -and EISA (Fast) Etherlink III / (Fast) Etherlink XL - -3Com 3c980/3c980B/3c980C Fast Etherlink XL server adapter - -3Com 3cSOHO100-TX OfficeConnect adapter - -3Com 3c450-TX HomeConnect adapter - -NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards, -including the following: - AR-P500 Ethernet card - Accton EN2212/EN2216/UE2216(OEM) - Allied Telesis CentreCOM LA100-PCM_V2 - AmbiCom 10BaseT card - BayNetworks NETGEAR FA410TXC Fast Ethernet - CNet BC40 adapter - COREGA Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD - Compex Net-A adapter - CyQ've ELA-010 - D-Link DE-650/660 - Danpex EN-6200P2 - ELECOM Laneed LD-CDL/TX - IO DATA PCLA/TE, PCET/TX, PCET/TX-R - IBM Creditcard Ethernet I/II - IC-CARD Ethernet/IC-CARD+ Ethernet - Linksys EC2T/PCMPC100,EtherFast 10/100 PC Card (PCMPC100 V2) - Melco LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX - NDC Ethernet Instant-Link - National Semiconductor InfoMover NE4100 - Network Everywhere Ethernet 10BaseT PC Card - Planex FNW-3600-T - Socket LP-E - Surecom EtherPerfect EP-427 - TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card - Telecom Device SuperSocket RE450T - -Megahertz X-Jack Ethernet PC-Card CC-10BT - -Xircom X3201 (Cardbus) based Ethernet cards, -including the following: - IBM EtherJet Cardbus Adapter - Intel PRO/100 Mobile Cardbus (versions that uses the X3201 chipset) - Xircom Cardbus Realport - Xircom Cardbus Ethernet 10/100 - Xircom Cardbus Ethernet II 10/100 - -Xircom CreditCard adapters(16bit) and workalikes - Accton EN2226/Fast EtherCard (16-bit verison) - Compaq Netelligent 10/100 PC Card - Intel EtherExpress PRO/100 Mobile Adapter (16-bit verison) - Xircom 10/100 Network PC Card adapter. - Xircom Realport card + modem(Ethernet part) - Xircom CreditCard Ethernet 10/100 - Xircom CreditCard 10Base-T "CreditCard Ethernet Adaptor IIps" (PS-CE2-10) - Xircom CreditCard Ethernet 10/100 + modem (Ethernet part) - -National Semiconductor DP8393X (SONIC) Ethernet cards - NEC PC-9801-83, -84, -103, and -104 - NEC PC-9801N-25 and -J02R - - -4.3. USB ----- --- - -A range of USB peripherals are supported. Owing to the generic nature -of most USB devices, with some exceptions any device of a given class -will be supported even if not explicitly listed here. - -USB keyboards. - -USB mice. - -USB printers and USB to parallel printer conversion cables. - -USB hubs. - -USB Ethernet controllers. - - -USB Host Controllers: - ALi Aladdin-V. - AMD-756. - CMD Tech 670 & 673. - Intel 82371SB (PIIX3). - Intel 82371AB and EB chipsets (PIIX4). - NEC uPD 9210. - OPTi 82C861 (FireLink). - SiS 5571. - VIA 83C572 USB. - and any other UHCI or OHCI compliant motherboard chipset (no exceptions - known). - - -PCI plug-in USB host controllers: - ADS Electronics PCI plug-in card (2 ports). - Entrega PCI plug-in card (4 ports). - - -Specific devices reported to be working (see above for USB Ethernet devices -supported): - -Floppy drives/Hard disks/CDROMs/Zip drives/etc: - Iomega USB Zip 100Mb (primitive support still). - Matshita CF-VFDU03 floppy drive. - Microtech USB-SCSI-HD 50 USB to SCSI cable. - Panasonic floppy drive. - Y-E Data floppy drive (720/1.44/2.88Mb). - -Hubs: - Andromeda hub. - MacAlly self powered hub (4 ports). - NEC hub. - -Keyboards: - Apple iMac keyboard. - BTC BTC7935 keyboard with PS/2 mouse port. - Cherry G81-3504 keyboard. - Logitech M2452 keyboard. - MacAlly iKey keyboard. - Microsoft keyboard. - -Mice: - Agiler Mouse 29UO. - Apple iMac Mouse. - Belkin Mouse. - Chic mouse. - Cypress mouse. - Genius Niche mouse. - Kensington Mouse-in-a-Box. - Logitech wheel mouse (3 buttons). - Logitech PS/2 / USB mouse (3 buttons). - MacAlly mouse (3 buttons). - Microsoft IntelliMouse (3 buttons). - Trust Ami Mouse (3 buttons). - -Printer Adapters: - ATen parallel printer adapter. - Belkin F5U002 parallel printer adapter. - Entrega USB-to-parallel printer adapter. - -Modems: - 3Com 5605 - Metricom Ricochet GS USB wireless modem - -Scanners (through SANE): - Perfection 636U - HP ScanJet 4100C, 5200C, 6300C - -Miscalleneous: - ActiveWire I/O Board. - -4.4. ISDN ----- ---- - -Note: only European DSS1 [Q.921/Q.931] protocol supported for passive cards, - any national ISDN protocol supported by active ISDN card microcode. - -AcerISDN P10 ISA PnP (experimental) - -Asuscom ISDNlink 128K PnP -ASUSCOM P-IN100-ST-D (and other Winbond W6692 based cards) - -AVM A1 -AVM Fritz!Card classic -AVM Fritz!Card PnP -AVM Fritz!Card PCI - -AVM B1 ISA (tested with V2.0) -AVM B1 PCI (tested with V4.0) -AVM T1 - -Creatix ISDN-S0/8 -Creatix ISDN-S0/16 -Creatix ISDN-S0 PnP - -Dr.Neuhaus Niccy 1008 -Dr.Neuhaus Niccy 1016 -Dr.Neuhaus Niccy GO@ (ISA PnP) - -Eicon Diehl DIVA 2.0 and 2.02 - -ELSA QuickStep 1000pro ISA -ELSA MicroLink ISDN/PCI (same as ELSA QuickStep 1000pro PCI) -ELSA PCC-16 - -ITK ix1 Micro ( < V.3, non-PnP version ) - -Sagem Cybermod (ISA PnP) - -Sedlbauer Win Speed - -Siemens I-Surf 2.0 - -TELEINT ISDN SPEED No.1 (experimental) - -Teles S0/8 -Teles S0/16 -Teles S0/16.3 -Teles S0/16.3 PnP -Teles 16.3c ISA PnP (experimental) - - -4.5. Misc ----- ---- - -AST 4 port serial card using shared IRQ. - -ARNET 8 port serial card using shared IRQ. -ARNET (now Digiboard) Sync 570/i high-speed serial. - -Boca BB1004 4-Port serial card (Modems NOT supported) -Boca IOAT66 6-Port serial card (Modems supported) -Boca BB1008 8-Port serial card (Modems NOT supported) -Boca BB2016 16-Port serial card (Modems supported) - -Comtrol Rocketport card. - -Cyclades Cyclom-y Serial Board. - -STB 4 port card using shared IRQ. - -SDL Communications Riscom/8 Serial Board. -SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. - -Specialix SI/XIO/SX multiport serial cards, with both the older -SIHOST2.x and the new "enhanced" (transputer based, aka JET) host cards. -ISA, EISA and PCI are supported. - -Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, -ONboard 4/16 and Brumby. - -HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. - -Bus mice - -PS/2 mice - -Standard PC Joystick - -X-10 power controllers - -GPIB and Transputer drivers. - -Genius and Mustek hand scanners. - -Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed -(2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes -3COM 3crwe737A AirConnect Wireless LAN PC Card -Addtron AWA100 -Cabletron RoamAbout 802.11 DS -Compaq WL100 -Corega KK Wireless LAN PCC-11, PCCA-11 -Laneed Wireless card -ELECOM Air@Hawk/LD-WL11/PCC -Farallon Skyline 11Mbps Wireless -ICOM SL-1100 -IO Data WN-B11/PCM -Melco Airconnect WLI-PCM-L11 -NCR WaveLAN/IEEE 802.11 -NEC Wireless Card CMZ-RT-WP, PC-WL/11C, PK-WL001 -PLANEX GeoWave/GW-NS110 -TDK LAK-CD011WL -Note: the ISA versions of these adapters are actually PCMCIA cards -combined with an ISA to PCMCIA bridge card, so both kinds of devices -work with the same driver. - -Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA, -PCI and ISA adapters are all supported. -Cisco Systems Aironet 340 Series (includes 340, 341, and 342 models) -11Mbps 802.11 wireless NIC - -Webgear Aviator 2.4GHz wireless adapters - -Toshiba Mobile HDD MEHDD20A (Type II) - -Panasonic Flash ATA BN-040ABP3 - -Hewlett Packard M820e (CD-writer) - -FAX-Modem/PC-Card -Melco IGM-PCM56K/IGM-PCM56KH -Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal) - -PHS Data Commuincation Card/PC-Card -NTT DoCoMo P-in Comp@ct -Panasonic KX-PH405 -SII MC-P200 - - -4.6. Microchannel ----- ------------ - -Experimental support for Microchannel systems is new in FreeBSD 4.0 - -Drivers with support for Microchannel peripherals are: - -aha: Adaptec AHA-1640 SCSI controller -bt: Buslogic BT-640A and Storage Dimensions SDC3211 SCSI controllers -ep: 3Com 3C529 network adapter - - -4.7. Multimedia ----- ---------- - -Soundcards supported by newpcm: - -Advance Asound 100, 110 and Logic ALS120 -C-Media CMI-8x38 -Crystal Semiconductor CS461x/462x/428x -Crystal Semiconductor CS4281 -ENSONIQ AudioPCI ES1370/1371 -ESS ES1868, ES1869, ES1879 and ES1888 -ESS Maestro-1, Maestro-2, and Maestro-2E -ESS Maestro-3/Allegro -ForteMedia fm801 -Gravis UltraSound MAX/PnP -MSS/WSS Compatible DSPs -NeoMagic 256AV/ZX -OPTi 931/82C931 -S3 Sonicvibes -SoundBlaster, Soundblaster Pro, Soundblaster AWE-32, Soundblaster AWE-64 -Trident 4DWave DX/NX -VIA Technologies VT82C686A -Yamaha DS1 and DS1e - -NOTE: Due to licensing restrictions, the Maestro3/Allegro driver -cannot be compiled into the kernel. To use this driver, add the -following line to /boot/loader.conf: - - maestro3_load="YES" - -Matrox Meteor Video frame grabber -Creative Labs Video Spigot frame grabber -Cortex1 frame grabber -Various Frame grabbers based on Brooktree Bt848 and Bt878 chip. diff --git a/release/texts/LAYOUT.TXT b/release/texts/LAYOUT.TXT deleted file mode 100644 index c97298e..0000000 --- a/release/texts/LAYOUT.TXT +++ /dev/null @@ -1,101 +0,0 @@ -=================== -Distribution format -=================== - -A typical FreeBSD distribution directory looks something like this: - -ABOUT.TXT bin compat3x games proflibs -HARDWARE.TXT compat1x info src tools -INSTALL.TXT compat20 dict manpages packages -README.TXT compat21 crypto doc -RELNOTES.TXT compat22 floppies ports -XF86336 - -If you want to do a CDROM, FTP or NFS installation from this -distribution directory, all you need to do is make the 1.44MB boot -floppies from the floppies directory (see floppies/README.TXT for -instructions on how to do this), boot them and follow the instructions. -The rest of the data needed during the installation will be obtained -automatically based on your selections. If you've never installed -FreeBSD before, you also want to read the INSTALL.TXT file for -instructions. - -If you're trying to do some other type of installation or are merely -curious about how a distribution is organized, what follows is a more -thorough description of each item in more detail: - -1. The *.TXT files obviously contain documentation (this file is - LAYOUT.TXT) and should be read before starting an installation. - -2. The XF86336 directory contains the XFree86 project's 3.3.6 release and - consists of a series of gzip'd tar files which contain each component - of the XFree86 distribution. - -3. The bin, dict, crypto, doc, games, info, manpages, proflibs, and src - directories contain the primary distribution components of FreeBSD - itself and are split into smaller files for easy packing onto floppies - (should that be necessary). - -4. The compat1x, compat20, compat21, compat22, and compat3x directories - contain distributions for compatibility with older releases and are - distributed as single gzip'd tar files - they can be installed during - release time or later by running their `install.sh' scripts. - -5. The floppies subdirectory also contains the floppy installation images - and the floppies/README.TXT file should be read for further - information on using them. - -6. The packages and ports directories contain the FreeBSD packages and - ports collections. Packages may be installed from the packages - directory by running the command: ``sysinstall configPackages'' - or by feeding individual filenames in packages/ to the pkg_add(1) - command. - - The ports collection may be installed like any other distribution - and requires about 100MB unpacked. More information on the ports - collection may be obtained from http://www.freebsd.org/ports or - locally from ``file:/usr/share/doc/handbook'' if you've installed - the doc distribution. - -7. Last of all, the tools directory contains various DOS tools for - discovering disk geometries, installing boot managers and the like. - It is purely optional and provided only for user convenience. - -A typical distribution (we'll use the info distribution as an example) -looks like this internally: - -CHECKSUM.MD5 info.ab info.ad info.inf install.sh -info.aa info.ac info.ae info.mtree - -The CHECKSUM.MD5 file contains MD5 signatures for each file, should -data corruption be suspected, and is purely for reference. It is not -used by the actual installation and does not need to be copied with -the rest of the distribution files. The info.a* files are split, -gzip'd tar files, the contents of which can be viewed by doing: - - cat info.a* | tar tvzf - - -During installation, they are automatically concatenated and extracted -by the installation procedure. - -The info.inf file is also necessary since it is read by the installation -program in order to figure out how many pieces to look for when fetching and -concatenating the distribution. When putting distributions onto floppies, -the .inf file MUST occupy the first floppy of each distribution set! - -The info.mtree file is another non-essential file which is provided -for user reference. It contains the MD5 signatures of the *unpacked* -distribution files and can be later used with the mtree(1) program -to verify the installation permissions and checksums against any possible -modifications to the file. When used with the bin distribution, this can -be an excellent way of detecting trojan horse attacks on your system. - -Finally, the install.sh file is for use by those who want to install the -distribution after installation time. To install the info distribution from -CDROM after a system was installed, for example, you'd do: - - cd /cdrom/info - sh install.sh - -And that's all there is to it! Each distribution contains its own -install.sh file for this. diff --git a/release/texts/README.TXT b/release/texts/README.TXT deleted file mode 100644 index 7f4fefc..0000000 --- a/release/texts/README.TXT +++ /dev/null @@ -1,105 +0,0 @@ - ----------------------------------------- - FreeBSD 5.0 --- SNAPSHOT Version , , - ----------------------------------------- /( )` - \ \___ / | -This is a binary snapshot of 5.0-current, the /- _ `-/ ' -(HEAD) branch which is currently moving towards (/\/ \ \ /\ -the release of 5.0. / / | ` \ - O O ) / | - `-^--'`< ' - (_.) _ ) / - `.___/` / - `-----' / -Feedback or offers to help with anything <----. __ / __ \ -you see in this release are most welcome <----|====O)))==) \) /==== -and should be sent to one of the approp- <----' `--' `.__,' \ -riate mailing lists - please see the | | -ABOUT.TXT file for more information. \ / /\ - ______( (_ / \______/ - ,' ,-----' | - `--{__________) - -TARGET AUDIENCE: ----------------- -This release is aimed primarily at early-adopters and the various -other folks who want to get involved with the ongoing development -of FreeBSD and are willing to deal with a few bumps in the road. -We do our best to ensure that each snapshot works as advertised, -but tracking -current is a process which frequently has its off -days. - -If you're both technically proficient and know exactly what you're -getting into here (e.g. you've been following -current) then this -snapshot is probably for you. If you're more interested in doing -business with FreeBSD than in playing with the cutting edge of -technology, however, then 3.x or 4.x is almost certainly your best -bet. - - -Most information here is also available from the Documentation menu -during installation. - - ERRATA.TXT Read this file! It will tell you where to look for the - latest information on problems which have been found and - fixed since this release was created (and may bite you). - - README.TXT This file - - ABOUT.TXT All about FreeBSD, including contact information - - RELNOTES.TXT Release Notes - what's new & different in this release - - LAYOUT.TXT Information about the layout of the release directory. - If you are installing from floppies, it is especially - important that you read this section! - - HARDWARE.TXT Information about the configuration of the GENERIC kernel - and supported hardware. New installers should read this - file. - - INSTALL.TXT Installation instructions - new installers should read this. - - UPGRADE.TXT Upgrading an existing FreeBSD installation - - TROUBLE.TXT General troubleshooting information - - -o It is, again, very important to check the ERRATA.TXT file for any - late-breaking issues with this release. If you don't read the ERRATA, - you will probably fall right into the same problems that have already - been reported (and fixed as noted in the ERRATA). - - -If you're a developer/hobbiest and not interested in QA'd releases -so much as simply keeping up to date on the latest FreeBSD technology, -you can also install one of our "snapshot" releases. - -For the most up-to-date software along the RELENG_3 branch -(also known as 3.5-stable), please install your snapshots from: - - ftp://releng3.freebsd.org/pub/FreeBSD/ - -For the most up-to-date software along the RELENG_4 branch -(also known as 4.0-stable), now proceeding towards the release -of FreeBSD 4.1, please install your snapshots from: - - ftp://releng4.freebsd.org/pub/FreeBSD/ - -For the latest 5.0-current (HEAD branch) snapshot releases, -please install from: - - ftp://current.freebsd.org/pub/FreeBSD - -If you plan to run either -Stable or -Current you MUST be -subscribed to the appropriate mailing list, either -freebsd-stable or freebsd-current. For information on -subscribing to either list (or both), send an e-mail to -majordomo@freebsd.org with the following in the body, not -the subject, of the letter as appropriate: - -subscribe freebsd-stable -subscribe freebsd-current -end - -We hope you enjoy using FreeBSD as much as we enjoyed -creating it! diff --git a/release/texts/TROUBLE.TXT b/release/texts/TROUBLE.TXT deleted file mode 100644 index 312c6c3..0000000 --- a/release/texts/TROUBLE.TXT +++ /dev/null @@ -1,383 +0,0 @@ -=============== -Troubleshooting -=============== - - Table of Contents: - - Repairing an Existing FreeBSD Installation - - Common Installation Problems, Q&A - - Common Hardware Problems, Q&A - -Repairing an Existing FreeBSD Installation ------------------------------------------- - -FreeBSD releases 2.2.1 and later feature a "Fixit" option in the top -menu of the boot floppy. To use it, you will also need either a -fixit.flp image floppy, generated in the same fashion as the boot -floppy, or the 2nd CDROM from Walnut Creek CDROM's FreeBSD -distribution. - -To invoke fixit, simply boot the kern.flp floppy, choose the "Fixit" -item and insert the fixit floppy or CDROM when asked. You will then -be placed into a shell with a wide variety of commands available (in -the /stand and /mnt2/stand directories) for checking, repairing and -examining file systems and their contents. Some UNIX administration -experience *is* required to use the fixit option! - -Common Installation Problems, Q&A ---------------------------------- - -Q: 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 wd1s1a - panic: cannot mount root - - What is wrong? What can I do? - -Q: What is this 'bios_drive:interface(unit,partition)kernel_name' thing - that is displayed with the boot help? - -A: 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 wd0 and wd2. - - FreeBSD is on BIOS disk 1, of type 'wd' and the FreeBSD disk number - is 2, so you would say: - - 1:wd(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. - -Q: 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. - -A: 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 work- - station 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. - - -Known Hardware Problems, Q & A ------------------------------- - -Q: mcd0 keeps thinking that it has found a device and this stops my Intel - EtherExpress card from working. - -A: Use the UserConfig utility (see HARDWARE.TXT) and disable the probing of - the mcd0 and mcd1 devices. Generally speaking, you should only leave - the devices that you will be using enabled in your kernel. - - -Q: FreeBSD claims to support the 3Com PCMCIA card, but my card isn't - recognized when it's plugged into my laptop. - -A: There are a couple of possible problems. First of all, FreeBSD does - not support multi-function cards, so if you have a combo - ethernet/modem card (such as the 3C562), it won't work. The - default driver for the 3C589 card was written just like all of the - other drivers in FreeBSD, and depend on the card's own configuration - data stored in NVRAM to work. You must correctly configure FreeBSD's - driver to match the IRQ, port, and IOMEM stored in NVRAM. - Unfortunately, the only program capable of reading them is the - 3COM supplied DOS program. This program must be run on a absolutely - clean system (no other drivers must be running), and the program will - whine about CARD-Services not being found, but it will continue. - This is necessary to read the NVRAM values. You want to know the - IRQ, port, and IOMEM values (the latter is called the CIS tuple by - 3COM). The first two can be set in the program, the third is - un-settable, and can only be read. Once you have these values, set - them in UserConfig and your card will be recognized. - - -Q: FreeBSD finds my PCMCIA network card, but no packets appear to - be sent even though it claims to be working. - -A: Many PCMCIA cards have the ability to use either the 10-Base2 (BNC) - or 10-BaseT connectors for connecting to the network. The driver is - unable to 'auto-select' the correct connector, so you must tell it - which connector to use. In order to switch between the two - connectors, the link flags must be set. Depending on the model of - the card, '-link0 link1' or 'link0 -link1' will choose the correct - network connector. You can set these in sysinstall by using the - 'Extra options to ifconfig:' field in the network setup screen. - - -Q: The system finds my ed network card, but I keep getting device - timeout errors. - -A: Your card is probably on a different IRQ from what is specified in the - kernel configuration. 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 `?' in the IRQ field of your kernel - config file. - - Either move the jumper on the card to a hard configuration setting - (altering the kernel settings if necessary), or specify the IRQ as - `-1' in UserConfig or `?' in your kernel config file. 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. - - -Q: I have a Matsushita/Panasonic drive but it isn't recognized by the - system. - -A: Make certain that the I/O port that the matcd driver is set to is - correct for the host interface card you have. (Some SoundBlaster DOS - drivers report a hardware I/O port address for the CD-ROM interface - that is 0x10 lower than it really is.) - - If you are unable to determine the settings for the card by examining - the board or documentation, you can use UserConfig to change the 'port' - address (I/O port) to -1 and start the system. This setting causes the - driver to look at a number of I/O ports that various manufacturers - use for their Matsushita/Panasonic/Creative CD-ROM interfaces. - Once the driver locates the address, you should run UserConfig again - and specify the correct address. Leaving the 'port' parameter set to -1 - increases the amount of time that it takes the system to boot, and - this could interfere with other devices. - - The double-speed Matsushita CR-562 and CR-563 are the only drives - that are supported. - - -Q: I booted the install floppy on my IBM ThinkPad (tm) laptop, and the - keyboard is all messed up. - -A: Older IBM laptops use a non-standard keyboard controller, so you must - tell the keyboard driver (atkbd0) to go into a special mode which works - on the ThinkPads. Change the atkbd0 'Flags' to 0x4 in UserConfig and - it should work fine. (Look in the Input Menu for 'Keyboard'.) - - -Q: When I try to boot the install floppy, I see the following message - and nothing seems to be happening. I cannot enter anything from - the keyboard either. - - Keyboard: no - -A: Due to lack of space, full support for old XT/AT (84-key) keyboards - is no longer available in the bootblocks. Some notebook computers may - also have this type of keyboard. If you are still using this kind of - hardware, you will see the above message appears when you boot from - the CD-ROM or an install floppy. - - As soon as you see this message, hit the space bar, and you will see - the prompt: - - >> FreeBSD/i386 BOOT - Default: x:xx(x,x)/boot/loader - boot: - - Then enter `-Dh', and things should proceed normally. - - -Q: I have a Matsushita/Panasonic CR-522, a Matsushita/Panasonic CR-523 or - a TEAC CD55a drive, but it is not recognized even when the correct I/O - port is set. - -A: These CD-ROM drives are currently not supported by FreeBSD. The command - sets for these drives are not compatible with the double-speed CR-562 - and CR-563 drives. - - The single-speed CR-522 and CR-523 drives can be identified by their - use of a CD-caddy. - - -Q: I'm trying to install from a tape drive but all I get is something like: - sa0(aha0:1:0) NOT READY csi 40,0,0,0 - on the screen. Help! - -A: There's a limitation in the current sysinstall that the tape MUST - be in the drive while sysinstall is started or it won't be detected. - Try again with the tape in the drive the whole time. - - -Q: I've installed FreeBSD onto my system, but it hangs when booting from - the hard drive with the message: ``Changing root to /dev/da0a''. - -A: This problem may occur in a system with a 3com 3c509 Ethernet adaptor. - The ep0 device driver appears to be sensitive to probes for other - devices that also use address 0x300. Boot your FreeBSD system by power - cycling the machine (turn off and on). At the ``Boot:'' prompt specify - the ``-c''. This will invoke UserConfig (see Section 1. above). Use - the ``disable'' command to disable the device probes for all devices - at address 0x300 except the ep0 driver. On exit, your machine should - successfully boot FreeBSD. - - -Q: My system can not find my Intel EtherExpress 16 card. - -A: You must set your Intel EtherExpress 16 card to be memory mapped at - address 0xD0000, and set the amount of mapped memory to 32K using - the Intel supplied softset.exe program. - - -Q: When installing on an EISA HP Netserver, my on-board AIC-7xxx - SCSI controller isn't detected. - -A: This is a known problem, and will hopefully be fixed in the future. - In order to get your system installed at all, boot with the -c - option into UserConfig, but _don't_ use the pretty visual mode but - the plain old CLI mode. Type - - eisa 12 - quit - - there at the prompt. (Instead of `quit', you might also type - `visual', and continue the rest of the configuration session in - visual mode.) While it's recommended to compile a custom kernel, - dset(8) now also understands to save this value. - - Refer to the FAQ topic 3.16 for an explanation of the problem, and - for how to continue. Remember that you can find the FAQ on your - local system in /usr/share/doc/FAQ, provided you have installed the - `doc' distribution. - - -Q: I have a Panasonic AL-N1 or Rios Chandler Pentium machine and I find - that the system hangs before ever getting into the installation - now. - -A: Your machine doesn't like the new i586_copyout and i586_copyin code - for some reason. To disable this, boot the installation boot floppy - and when it comes to the very first menu (the choice to drop into - kernel UserConfig mode or not) choose the command-line interface - ("expert mode") version and type the following at it: - - flags npx0 1 - - Then proceed normally to boot. This will be saved into your kernel, - so you only need to do it once. - - -Q: I have this CMD640 IDE controller that is said to be broken. - -A: Yes, it is. FreeBSD does not support this controller except through - the legacy 'wdc' driver. - - -Q: On a Compaq Aero notebook, I get the message "No floppy devices found! - Please check ..." when trying to install from floppy. - -A: With Compaq being always a little different from other systems, they - do not announce their floppy drive in the CMOS RAM of an Aero notebook. - Therefore, the floppy disk driver assumes there is no drive configured. - Go to the UserConfig screen, and set the Flags value of the fdc0 device - to 0x1. This pretends the existence of the first floppy drive (as a - 1.44 MB drive) to the driver without asking the CMOS at all. - - -Q: When I go to boot my Intel AL440LX ("Atlanta") -based system from the - hard disk the first time, it stops with a "Read Error" message. - -A: There appears to be a bug in the BIOS on at least some of these boards, - this bug results in the FreeBSD bootloader thinking that it is booting - from a floppy disk. - This is only a problem if you are not using the BootEasy boot manager. - Slice the disk in 'compatible' mode and install BootEasy during the - FreeBSD installation to avoid the bug, or upgrade the BIOS (see Intel's - website for details). - -Q: When installing on an Dell Poweredge XE, Dell proprietary RAID controller - DSA (Dell SCSI Array) isn't recognized. - -A: Configure DSA to use AHA-1540 emulation using EISA configuration utility. - After that FreeBSD detects DSA as Adaptec AHA-1540 SCSI controller, with - irq 11 and port 340. Under emulation mode system will use DSA RAID disks, - but you cannot use DSA specific features such as watching RAID health. - - -Q: My Ethernet adapter is detected as an AMD PCnet-FAST (or similar) but - it doesn't work. (Eg. onboard Ethernet on IBM Netfinity 5xxx or 7xxx) - -A: The 'lnc' driver is currently faulty, and will often not work correctly - with the PCnet-FAST and PCnet-FAST+. You need to install a different - Ethernet adapter. - - -Q: I have an IBM EtherJet PCI card, it is detected by the 'fxp' driver - correctly, but the lights on the card don't come on and it doesn't - connect to the network. - -A: We don't understand why this happens. Neither do IBM (we asked them). - The card is a standard Intel EtherExpress Pro/100 with an IBM label - on it, and these cards normally work just fine. You may see these - symptoms only in some IBM Netfinity servers. The only solution is to - install a different Ethernet adapter. - - -Q: When I configure the network during installation on an IBM Netfinity - 3500, the system freezes. - -A: There is a problem with the onboard Ethernet in the Netfinity 3500 - which we have not been able to identify at this time. It may be - related to the SMP features of the system being misconfigured. You - will have to install another Ethernet adapter and avoid attempting - to configure the onboard adapter at any time. - -Q: When I install onto a drive managed by a Mylex PCI RAID controller, - the system fails to boot (eg. with a "read error" message). - -A: There is a bug in the Mylex driver which results in it ignoring - the '8GB' geometry mode setting in the BIOS. Use the 2GB mode - instead. - -[ Please send hardware tips for this Q&A section to jkh@freebsd.org ] diff --git a/release/texts/UPGRADE.TXT b/release/texts/UPGRADE.TXT deleted file mode 100644 index 5c8f445..0000000 --- a/release/texts/UPGRADE.TXT +++ /dev/null @@ -1,179 +0,0 @@ -+===================== Upgrading FreeBSD ==========================+ -| | -| 0.0 Preface | -| 0.1 DISCLAIMER | -| 0.2 IMPORTANT NOTES | -| | -| 1.0 Introduction | -| 1.1 Upgrade Overview | -| | -| 2.0 Procedure | -| 2.1 Backup | -| 2.2 Mount Filesystems | -| 2.3 Select Distributions | -| 2.4 After Installation | -| | -| 3.0 Alternative Upgrade Techniques | -| | -+=====================================================================+ - -0.1 DISCLAIMER ---- ---------- - -While the FreeBSD upgrade procedure does its best to safeguard against -accidental loss of data, it is still more than possible to WIPE OUT YOUR -ENTIRE DISK with this installation! Please do not accept the final -confirmation request unless you have adequately backed up any important -data files. - -0.2 IMPORTANT NOTES ---- --------------- - -These notes assume that you are using the version of sysinstall supplied -with the version of FreeBSD to which you intend to upgrade. Using a -mismatched version of sysinstall is almost guaranteed to cause problems -and has been known to leave systems in an unusable state. The most -commonly made mistake in this regard is the use of an old copy of -/stand/sysinstall from an existing installation to upgrade to a newer -version of FreeBSD. This is NOT recommended. You should instead boot -from the installation media to do an upgrade. - -Furthermore, if you are upgrading from FreeBSD 2.2.5 or earlier, see -section 2.4 for important details regarding changes to the /etc/fstab -file required during the upgrade procedure. - -1.0 Introduction ---- ------------ - -The upgrade procedure replaces distributions selected by the user -with those corresponding to the new FreeBSD release. It preserves -standard system configuration data, as well as user data, installed -packages and other software. - -Administrators contemplating an upgrade are encouraged to study this -document in its entirety before commencing an upgrade. Failure to do so -may result in a failed upgrade or loss of data. - -1.1 Upgrade Overview ---- ---------------- -Upgrading of a distribution is performed by extracting the new version of -the component over the top of the previous version. Files belonging to -the old distribution are not deleted. - -System configuration is preserved by retaining and restoring the -previous version of the following files: - - Xaccel.ini, adduser.conf, aliases, aliases.db, amd.map, crontab, - csh.cshrc, csh.login, csh.logout, daily, disktab, dm.conf, exports, - fbtab, fstab, ftpusers, gettytab, gnats, group, hosts, hosts.equiv, - hosts.lpd, inetd.conf, kerberosIV, localtime, login.access, - mail.rc, make.conf, manpath.config, master.passwd, mib.txt, modems, - monthly, motd, namedb, networks, nsswitch.conf, passwd, phones, - ppp, printcap, profile, protocols, pwd.db, rc, rc.firewall, - rc.i386, rc.local, rc.network, rc.conf, remote, resolv.conf, rmt, - security, sendmail.cf, services, shells, skeykeys, spwd.db, - supfile, syslog.conf, termcap, ttys, uucp, weekly - -The versions of these files which correspond to the new version are -moved to /etc/upgrade/. The system administrator may peruse these new -versions and merge components as desired. Note that many of these files -are interdependent, and the best merge procedure is to copy all -site-specific data from the current files into the new. - -During the upgrade procedure, the administrator is prompted for a -location into which all files from /etc/ are saved. In the event that -local modifications have been made to other files, they may be -subsequently retrieved from this location. - -2.0 Procedure ---- --------- - -This section details the upgrade procedure. Particular attention is -given to items which substantially differ from a normal installation. - -2.1 Backup ---- ------ - -User data and system configuration should be backed up before -upgrading. While the upgrade procedure does its best to prevent -accidental mistakes, it is possible to partially or completely destroy -data and configuration information. - -2.2 Mount Filesystems ---- ----------------- - -The disklabel editor is entered with the nominated disk's filesystem -devices listed. Prior to commencing the upgrade, the administrator -should make a note of the device names and corresponding mountpoints. -These mountpoints should be entered here. DO NOT set the 'newfs flag' -for any filesystems, as this will cause data loss. - -2.3 Select Distributions ---- -------------------- - -When selecting distributions, there are no constraints on which must be -selected. As a general rule, the 'bin' distribution should be selected -for an update, and the 'man' distribution if manpages are already -installed. Other distributions may be selected beyond those originally -installed if the administrator wishes to add additional functionality. - -2.4 After Installation ---- ------------------ - -Once the installation procedure has completed, the administrator is -prompted to examine the new configuration files. At this point, checks -should be made to ensure that the system configuration is valid. In -particular, the /etc/rc.conf and /etc/fstab files should be checked. - -Read the following, but DO NOT update /etc/fstab as described below -until the new system has booted correctly. The upgrade procedure -replaces the previous FreeBSD kernel with a GENERIC kernel, and a custom -kernel may need to be generated to suit the local system configuration. - -IMPORTANT NOTE: -============== -FreeBSD 2.2.6 introduced a change in the naming of the device from -which the root filesystem is mounted. This change affects all systems, -however user intervention is only required for systems undergoing an -upgrade installation from a version prior to FreeBSD 2.2.6. - -Previously, the root filesystem was always mounted from the -compatibility slice, while other partitions on the same disk were -mounted from their true slice. This might, for example, have resulted -in an /etc/fstab file like: - -# Device Mountpoint FStype Options Dump Pass# -/dev/wd0s2b none swap sw 0 0 -/dev/wd0a / ufs rw 1 1 -/dev/wd0s2f /local0 ufs rw 1 1 -/dev/wd0s2e /usr ufs rw 1 1 - -For FreeBSD 2.2.6 and later, this format changes so that the device for -'/' is consistent with others. Also, the driver for the ATA-drives has -changed from wd(4) to ad(4), so the new file could look something like: - -# Device Mountpoint FStype Options Dump Pass# -/dev/ad0s2b none swap sw 0 0 -/dev/ad0s2a / ufs rw 1 1 -/dev/ad0s2f /local0 ufs rw 1 1 -/dev/ad0s2e /usr ufs rw 1 1 - - -If /etc/fstab is not updated manually in this case, the system will -issue a warning message whenever / is mounted (normally at startup) -indicating the change that must be made. In addition, trouble may be -experienced if the root filesystem is not correctly unmounted, whereby -the root filesystem will not be marked clean at the next reboot. - -This change should be made as soon as the upgraded system has been -successfully rebooted. - -3.0 Alternative Upgrade Techniques ---- ------------------------------ - -Those interested in an upgrade method that allows more flexibility and -sophistication should take a look at the "The Cutting Edge" chapter in the -Handbook (http://www.FreeBSD.org/docs/en/books/handbook/cutting-edge.html) -which describes how to upgrade FreeBSD from the source code. This method -requires reliable network connectivity, extra disk space and spare time, -but has advantages for networks and other more complex installations. diff --git a/release/texts/alpha/HARDWARE.TXT b/release/texts/alpha/HARDWARE.TXT deleted file mode 100644 index 5f29acb..0000000 --- a/release/texts/alpha/HARDWARE.TXT +++ /dev/null @@ -1,1892 +0,0 @@ - FreeBSD/alpha Hardware Information - ================================== - -This file is maintained by Wilko Bulte <wilko@freebsd.org> - -Additions, corrections and constructive criticism are invited. In -particular information on system quirks is more than welcome. - - -Overview --------- - -This document tries to provide a starting point for those who want to start -running FreeBSD on an Alpha-based machine. It is aimed at providing -background information on the various hardware designs. It is not a -replacement for the systems manuals. - -The information is structured as follows: - -- general hardware requirements to run FreeBSD on Alpha. -- system specific information for each of the systems/boards supported - by FreeBSD/alpha. -- information on expansion boards for FreeBSD/alpha, including things - that differ from what is in the generic supported hardware list. - -Note: you will see references to DEC, Digital Equipment Corporation and -Compaq used more or less interchangeably. Now that Compaq has acquired Digital -Equipment it would be more correct to refer to Compaq-only. - - -In general, what do you need to run FreeBSD/alpha? --------------------------------------------------- - -Obviously you will need an Alpha machine that FreeBSD/alpha knows about. -Alpha machines are NOT like PCs. There are considerable differences -between the various chip sets and mainboard designs. This means that a kernel -needs to know the intimate details of a particular machine before it can run -on it. Throwing some odd GENERIC kernel at unknown hardware is almost -guaranteed to fail miserably. - -For a machine even to be considered for FreeBSD use please make sure it has -the SRM console firmware installed. Or at least make sure that SRM console -firmware is available for this particular machine type. If FreeBSD does not -currently support your machine type, there is a good chance that this will -change at some point in time, assuming SRM is available. - -Machines with the ARC or AlphaBIOS console firmware were intended for -WindowsNT. Some of them have SRM firmware available in the system ROMs -which you only have to select (via an ARC or AlphaBIOS menu). In other cases -you will have to re-flash the ROMs with SRM code. Check on -http://ftp.digital.com/pub/DEC/Alpha/firmware to see what is available -for your particular system. In any case: no SRM -> no FreeBSD (or NetBSD, -OpenBSD, Tru64 Unix or OpenVMS for that matter). With the demise of -WindowsNT/alpha a lot of former NT boxes are sold on the second hand -market. They have little or no trade-in value when they are NT-only from the -console perspective. So, be suspicious if the price appears too good. - -Known non-SRM machines are: - Digital XL series - Digital XLT series - Samsung PC164UX - Samsung 164B - -To complicate things a bit further: Digital used to have so called -'white-box' Alpha machines destined as NT-only and 'blue-box' Alpha machines -destined for OpenVMS and Digital Unix. These names are based on the color -of the cabinets, 'FrostWhite' and 'TopGunBlue' respectively. -Although you could put the SRM console on the whitebox, OpenVMS and Digital -Unix will refuse to boot on them. FreeBSD in post-4.0R will run on both the -white and the blue-box variants. Before someone asks: the white ones had a -rather different (read: cheaper) price tag. - -As part of the SRM you will get the so called OSF/1 PAL code (OSF/1 being the -initial name of Digital's Unix offering on Alpha). The PAL code can be thought -of as a software abstraction layer between the hardware and the operating -system. It uses normal CPU instruction plus a handful of privileged -instructions specific for PAL use. PAL is not microcode by the way. -The ARC firmware contains a different PAL code, geared towards WinNT and in -no way suitable for use by FreeBSD (or more generic: Unix or OpenVMS). -Before someone asks: Linux/alpha brings its own PAL code, allowing it to -boot on ARC & AlphaBIOS. There are various reasons why this is not a -very good idea in the eyes of the *BSD folks. I don't want to go into -details here. - -There is another pitfall ahead: you will need a disk adapter that the SRM -console recognizes in order to be able to boot from your disk. What is -acceptable to SRM as a boot adapter is unfortunately system and SRM version -dependent. For older PCI based machines this means you will need either -a NCR/Symbios 53C810 based adapter, or a Qlogic 1020/1040 based adapter. -Some machines come with a SCSI chip embedded on the mainboard. Newer machine -designs and SRM versions will be able to work with later SCSI chips/adapters. -Check out the machine specific info below. Please note that the rest -of this discussion only refers to Symbios chips, this is meant to include -the older chips that still have NCR stamped on them. Symbios bought the NCR -designs. - -The problem might bite those who have machines that started their lives as -WinNT boxes. The ARC or AlphaBIOS knows about *other* adapter types that it -can boot from than the SRM. For example you can boot from an Adaptec 2940UW -with ARC but (generally) not with SRM. Some newer machine types have introduced -Adaptec boot support. Please consult the machine specific section for details. - -Some adapters that cannot be booted from work fine for data-only disks. -The differences between SRM and ARC could also get you pre-packaged -IDE CDROMs and hard drives in some (former NT) systems. -SRM versions exist (depends on the machine type) that can boot -from IDE disks and CDROMs. Check the machine specific section for details. - -FreeBSD/alpha 4.0 and later can be booted from the distribution CDROM. -Earlier versions needed booting from a 2-floppy set. - -If you don't have/want a local disk drive you can boot via the Ethernet. -This assumes a Ethernet adapter/chip that is recognized by the SRM. -Generally speaking this boils down to either a 21040 or 21142 or 21143 -based Ethernet interface. Older machines / SRM versions may not recognize -the 21142 / 21143 Fast Ethernet chips, you are limited to using 10Mbit -Ethernet for net booting those machines. Non-DEC cards based on said chips will -generally (but are not guaranteed to) work. Note that Intel took over the -21x4x chips when it bought Digital Semiconductor. So you might see an Intel -logo on them these days. Recent machine designs have SRM support for -Intel 8255x Ethernet chips. - -Alpha machines can be run with SRM on a graphics console or on -a serial console. ARC can be run on a serial consoles if need be. VT100 -emulation with 8 bit controls should at least allow you to switch from -ARC to SRM mode without having to install a graphics card first. - -If you want to run your Alpha without a monitor/graphics card -just don't connect a keyboard/mouse to the machine. Instead hook -up a serial terminal[emulator] to serial port #1. The SRM will -talk 9600N81 to you. This can be really practical for debugging purposes. -Beware: some/most (?) SRMs will also present you with a console prompt at -serial port #2. The booting kernel, however, will display the boot messages -on serial port #1 and will also put the console there. This can be extremely -confusing. - -Most PCI based Alphas can use ordinary PC-type VGA cards. The SRM contains -enough smarts to make that work. It does not, however, mean that each and -every PCI VGA card out on the street will work in an Alpha machine. Things -like S3 Trio64, Mach64, and Matrox Millennium generally work. Old ET4000 -based ISA cards have also worked for me. But ask around first before buying. -Please note that TGA cards are not supported as FreeBSD console display cards. - -Most PCI devices from the PC-world will also work in FreeBSD/alpha PCI-based -machines. Check the /sys/alpha/conf/GENERIC file for the latest word on -this. Be careful to check the appropriate machine type's discussion -in case you want to use PCI cards that have PCI bridge chips on them. -In some cases you might encounter problems with PCI cards not handling -PCI parity correctly. This can lead to panics. PCI parity checking can be -disabled using the following SRM command: SET PCI_PARITY OFF. This is not -a FreeBSD problem, all operating systems running on Alpha hardware will -need this workaround. - -If your system (also) contains EISA expansion slots you will need to run -the EISA Configuration Utility (ECU) after you have installed EISA cards -or have upgraded your console firmware. - -Parallel ports that can be found on most Alpha machines are supported. - -For Alpha CPUs you will find multiple generations. The original Alpha -design is the 21064. It was produced in a chip process called MOS4, -chips made in this process are nicknamed EV4. Newer CPUs are 21164, 21264 -etc. You will see designations like EV4S, EV45, EV5, EV56, EV6, EV67. -The EVs with double digit numbers are slightly improved versions. For example -EV45 has an improved FPU and 16 kByte on-chip separate I & D caches compared -to the EV4 on which it is based. Rule of thumb: the higher the digit -immediately following 'EV' the more desirable (read: faster / more modern). - -For memory you want at least 32 Mbytes. I have had FreeBSD/alpha run on a -16 Mbyte system but you will not like that. Kernel build times halved when -going to 32 Mbytes. Note that the SRM steals 2Mbyte from the total system -memory (and keeps it). For more serious use >= 64Mbyte is recommended. - -While on the subject of memory: pay close attention to the type of memory -your machine uses. There are very different memory configurations and -requirements for the various machines. - -Final word: I expect the above to sound a bit daunting to the first-time -Alpha user. Don't be daunted too much. And do feel free to ask questions. - - -System specific information ---------------------------- - -Below is an overview of the hardware that FreeBSD/alpha runs on. -This list will definitely grow, a look in /sys/alpha/conf/GENERIC -can be enlightening. Alpha machines are often best known by their project -code name. When known these are listed below in (). - -* -* AXPpci33 ("NoName") -* -The NoName is a baby-AT mainboard based on the 21066 LCA (Low Cost Alpha) -processor. It was originally designed for OEM-use. The LCA chip includes -almost all of the logic to drive a PCI bus and the memory subsystem. -All of this makes for a low-priced design. - -Due to the limited memory interface the system is not particularly -fast in case of cache misses. As long as you stay inside the on-chip cache -the CPU is comparable to a 21064 (first generation Alpha). These boards -should be very cheap to obtain these days (even here in the Netherlands -they were sold new for US$ 25). - -Features: -- 21066 Alpha CPU at 166 MHz or 21066A CPU at 233MHz - (21068 CPUs are also possible, but are even slower. Never seen/used one) -- memory bus: 64 bits -- on-board Bcache / L2 cache: 0, 256k or 1 Mbyte (uses DIL chips) -- PS/2 mouse & keyboard port OR 5pin DIN keyboard (2 mainboard models) -- memory: PS/2 style 72 pin 36 bit Fast Page Mode SIMMs, - 70ns or better, - installed in pairs of 2, - 4 SIMM sockets - uses ECC -- 512kB Flash ROM for the console code. -- 2x 16550A serial ports, 1x parallel port, floppy interface -- 1x embedded IDE interface -- expansion: 3 32 bit PCI slots (1 shared with ISA) - 5 ISA slots (1 shared with PCI) -- embedded Fast SCSI using a Symbios 53C810 chip - -SRM: -NoNames can either have SRM *or* ARC console firmware in their Flash ROM. -The Flash ROM is not big enough to hold both ARC and SRM at the same time -and allow software selection of alternate console code. But you need -SRM-only anyway. - -Cache: -Cache for the NoNames are 15 or 20 ns DIL chips. For a 256 kByte cache you -want to check your junked 486 mainboard. Chips for a 1 Mbyte cache are a rarer -breed unfortunately. Getting at least a 256kByte cache is recommended -performance wise. Cache-less they are really slow. - -Power: -The NoName mainboard has a PC/AT-standard power connector. It also has -a power connector for 3.3 Volts. No need to rush out to get -a new power supply. The 3.3 Volts is only needed in case you run 3.3 Volts -PCI expansion boards. - -IDE: -The IDE interface is supported by FreeBSD and requires a line in the -kernel configuration file as follows: - - device ata0 at isa? port IO_WD1 irq 14 - -The SRM console unfortunately cannot boot from IDE disks. - -Memory: -Make sure you use true 36 bit SIMMs, and only FPM (Fast Page Mode). EDO RAM -or SIMMs with fake parity *will not work* (the board uses the 4 extra bits -for ECC!). 33 bit FPM SIMMs will for the same reason not work either. - -Keyboard/mouse: -Given the choice, get the PS/2-variant mainboard. Apart from giving you a -mouse port as bonus it is directly supported by Tru64 Unix in case you ever -want/need to run it. The "DIN-plug"-variant should work OK for FreeBSD. - -The OEM manual is recommended reading. -See ftp://ftp.digital.com/pub/DEC/axppci/design_guide.ps - -The kernel configuration file for a NoName kernel must contain: - options DEC_AXPPCI_33 - cpu EV4 - - -* -* Universal Desktop Box (UDB or "Multia") -* - -Note: Multia can be either Intel or Alpha CPU based. We assume Alpha based - ones here for obvious reasons. - -Multia is a small desktop box intended as a sort of personal workstation. -They come in a considerable number of variations, check closely what you -get. - -Features: -- 21066 Alpha CPU at 166 MHz or 21066A CPU at 233MHz -- memory bus: 64 bits -- on-board Bcache / L2 cache: COAST-like 256 kByte cache module - 233MHz models have 512kByte of cache - 166MHz models have soldered-on 256kB caches -- PS/2 mouse & keyboard port -- memory: PS/2 style 72 pin 36 bit Fast Page Mode SIMMs, - 70ns or better, - installed in pairs of 2, - 4 SIMM sockets - uses ECC -- 2x 16550A serial ports, 1x parallel port, floppy interface -- Intel 82378ZB PCI to ISA bridge -- 1x embedded 21040 based 10Mbit Ethernet, AUI or 10base2 connector -- expansion: 1 32 bit PCI slot, 2 PCMCIA slots -- on-board Crystal CS4231 or AD1848 sound chip -- embedded Fast SCSI using a Symbios 53C810 chip on the PCI riser card - -SRM/ARC: -Multia has enough Flash ROM to store both SRM and ARC code at the same time -and allow software selection of one of them. - -Expansion: -Multia has only one 32 bit PCI slot for expansion, and it is only -suitable for a small form factor PCI card too. In sacrificing the PCI slot -space you can mount a 3.5" hard disk drive. Mounting stuff may have come -with your Multia. Adding a 3.5" disk is not a recommended upgrade due to -the limited power rating of the power supply and the extremely marginal -cooling of the system box. Don't! - -Multia also has 2 PCMCIA expansion slots. These are currently unsupported. - -CPU: -The CPU might or might not be socketed, check before considering CPU upgrade -hacks. The low-end Multias have a soldered-in CPU. - -Graphics: -It comes with a TGA based graphics on-board. Which is not suitable for -console use with FreeBSD. Which means you will have to run it using a -serial console. Note that the boot of the installation disk will appear -to work fine using the TGA console, but then switches to using the -serial port. This is even mentioned during by installer (but never read -by the human doing the install..). Your keyboard appears dead from that point -on. - -Serial: -Multia has 2 serial ports but routes both of them to the outside world -on a single 25 pin sub-D connector. The Multia FAQ explains how to -build your own Y-cable to allow both ports to be used. - -Floppy: -Although the Multia SRM supports booting from floppy this is problematic. -Typical errors look like "*** Soft Error - Error #10 - FDC: Data overrun or -underrun". This is not a FreeBSD problem, it is a SRM problem. The best -available workaround to install FreeBSD is to boot from a SCSI CDROM. - -Sound: -Works fine using pcm driver and a line in the kernel configuration file as -follows for the Crystal CS4231 chip: - - device pcm0 at isa? port 0x530 irq 9 drq 3 flags 0x15 - -I have not yet been successful in getting my Multia with the AD1848 to -play any sound. - -While verifying playback I was reminded of the lack of CPU power of the 166MHz -CPU: MP3 only plays acceptable using 22kHz down-sampling. - -Hot: -Multias are somewhat notorious for dying of heat strokes. The very compact -box does not really allow cooling air access very well. Please use the -Multia on its vertical stand, don't put it horizontally ('pizza style'). -Replacing the fan with something which pushes around more air is -recommended. Beware of PCI cards with high power consumption. -If your system has died you might want to check on the Multia-Heat-Death -pages at the NetBSD web-site http://www.netbsd.org - -IDE: -The Intel 82378ZB PCI to ISA bridge enables the use of an IDE disk. This -requires a line in the kernel configuration file as follows: - - device ata0 at isa? port IO_WD1 irq 14 - -The IDE connector pin spacing is thought for 2.5" laptop disks. A 3.5" -IDE disk would not fit in the case anyway. At least not without sacrificing -your only PCI slot. - -The SRM console does not know how to boot from IDE disks unfortunately. - -SCSI: -In case you want to change the internal hard drive: the internal flat cable -running from the PCI riser board to the 2.5" (!!) hard drive has a finer pitch -than the standard SCSI flat cables. Otherwise it would not fit on the 2.5" -drives. There are also riser cards that have a standard-pitch SCSI cable -attached to it, which will fit an ordinary SCSI disk. - -Again, I recommend against trying to cram a replacement hard disk inside. Use -the external SCSI connector and put your disk in an external enclosure. -Multias run hot enough as-is. In most cases you will have the external high -density 50pin SCSI connector but some Multia models came without disk and -may lack the connector. Something to check before buying one. - -The kernel configuration file for a Multia kernel must contain: - options DEC_AXPPCI_33 - cpu EV4 - -More info: -Recommended reading on Multia can be found at - http://www.netbsd.org/Ports/alpha/multiafaq.html - http://www.brouhaha.com/~eric/computers/udb.html - -* -* Personal Workstation ("Miata") -* - -The Miata is a small tower machine intended to be put under a desk. There -are multiple Miata variants. The original Miata is the MX5 model. Because -it suffers from a number of hardware design flaws a redesign was performed, -yielding the MiataGL. Unfortunately the boxes are quite indistinguishable. -An easy check is to see if the back of the machine sports two -USB connectors. If yes, it is a MiataGL. - -System designations look like "Personal Workstation 433a". Personal -Workstation, being a bit of a mouthful, is often abbreviated to PWS. -This means it has a 433 MHz CPU, and started life as a WinNT workstation -(the trailing 'a'). Systems designated from day 1 to run Tru64 -Unix or OpenVMS will sport '433au'. WinNT-Miatas are likely -to come pre-configured with an IDE CDROM drive. So, in general systems -are named like PWS[433,500,600]a[u]. - -There was also a Miata model with a special CPU cooling system by Kryotech. -That one has a different enclosure. - -Features: - -- 21164A EV56 Alpha CPU, at 433, 500 or 600MHz -- 21174 Core Logic ("Pyxis") chip set -- on-board Bcache / L3 cache: 0, 2 or 4 Mbytes (uses a cache module) -- memory bus: 128 bits wide, ECC protected -- memory: Miata uses unbuffered SDRAMs, - installed in pairs of 2, - 6 DIMM sockets - 1.5 Gbytes max -- on-board Fast Ethernet based on: - - MX5 uses a 21142 or 21143 Ethernet chip dependent on the version of the - PCI riser card - - MiataGL has a 21143 chip - - the bulkhead can be 10/100 UTP, or 10 UTP/BNC -- 2x on-board [E]IDE based on: - - MX5: CMD646 - - MiataGL: Cypress 82C693 -- 1x Ultra-Wide SCSI Qlogic 1040 [MiataGL only] -- expansion: 2 64-bit PCI slots - 3 32-bit PCI slots (behind a DEC PCI-PCI bridge chip) - 3 ISA slots (physically shared with the 32 bit PCI slots, via - an Intel 82378IB PCI to ISA bridge chip) -- 2x 16550A serial port -- 1x parallel port -- PS/2 keyboard & mouse port -- USB interface [MiataGL only] -- embedded sound based on an ESS1888 chip - -CPU mainboard and PCI 'riser' board: -The Miata logic is divided into two printed circuit boards. -The lower board in the bottom of the machine has the PCI -and ISA slots and things like the sound chip etc. The top board -has the CPU, the Pyxis chip, memory etc. Note that MX5 and the MiataGL use -a different PCI riser board. This means that you cannot just upgrade to -a MiataGL CPU board (with the newer Pyxis chip) but that you will also need -a different riser board. Apparently an MX5 riser with a MiataGL CPU board -will work but it is definitely not a supported or tested configuration. -Everything else (cabinet, wiring etc etc) is identical for MX5 and MiataGL. - -DMA bug: -MX5 has problems with DMA via the 2 64-bit PCI slots when this DMA -crosses a page boundary. The 32 bit slots don't have this problem because the -PCI-PCI bridge chip does not allow the offending transfers. The SRM code -knows about the problem and refuses to start the system if there is a PCI -card in one of the 64bit slots that it does not know about. Cards that are -'known good' to the SRM are allowed to be used in the 64bit slots. - -If you want to fool the SRM you can type "set pci_device_override" at -the SRM prompt. Just don't complain if your data mysteriously gets mangled. - -The complete command is: - - set pci_device_override <vendor_id><device_id> - e.g. set pci_device_override 88c15333 - -A more radical approach is to use: - - set pci_device_override -1 - -This disables PCI ID checking altogether, so that you can stick in any -random PCI card without its ID getting checked. For this to work you need -a sufficiently new SRM in your Miata. Again: do this on your own -risk. - -The kernel reports it when it sees a buggy Pyxis chip: -Sep 16 18:39:43 miata /kernel: cia0: Pyxis, pass 1 -Sep 16 18:39:43 miata /kernel: cia0: extended capabilities: 1<BWEN> -Sep 16 18:39:43 miata /kernel: cia0: WARNING: Pyxis pass 1 DMA bug; no -bets... - -A MiataGL probes as: -Jan 3 12:22:32 miata /kernel: cia0: Pyxis, pass 1 -Jan 3 12:22:32 miata /kernel: cia0: extended capabilities: 1<BWEN> -Jan 3 12:22:32 miata /kernel: pcib0: <2117x PCI host bus adapter> on cia0 - -MiataGL does not have the DMA problems of the MX5. PCI cards that make -the MX5 SRM choke when installed in the 64bit slots are accepted without -problems by the MiataGL SRM. - -The latest mainboard revisions of MX5 contain a hardware workaround for the -bug. The SRM does not know about the ECO and will complain about unknown cards -as before. So does the FreeBSD kernel by the way. - -EIDE: -The Miata SRM can boot from IDE CDROM drives. Hard disk boot is known to work -for both MiataGL and MX5 disks, so you can root FreeBSD from an IDE disk. Speeds -on MX5 are around 14 Mbytes/sec assuming a suitable drive. The CMD646 chip will -support up to WDMA2 mode as the silicon is too buggy for use with UDMA. - -PCI-PCI bridge: -The MiataGL has a faster PCI-PCI bridge chip on the PCI riser card than -some of the MX5 riser card versions. Some of the MX5 risers have the *same* -chip as the MiataGL. All in all there is a lot of variation. - -Not all VGA cards will work behind the PCI-PCI bridge. This manifests itself -as no video at all. Workaround is to put the VGA card 'before' the bridge, -in one of the 64 bit PCI slots. - -Sound: -Both MX5 and MiataGL have an on-board sound chip, an ESS1888. It emulates -a SoundBlaster and can be enabled by putting - - device pcm0 - device sbc0 - -in your kernel configuration file. - -Cache: -in case your Miata has the optional cache board installed make sure -it is firmly seated. A slightly loose cache has been observed to cause -weird crashes (not surprising obviously, but maybe not so obvious when -troubleshooting). The cache module is identical between MX5 and MiataGL. - -Installing a 2Mb cache module achieves, apart from a 10-15% speed increase -(based on buildworld elapsed time), a *decrease* for PCI DMA read bandwidth -from 64bit PCI cards. A benchmark on a 64-bit Myrinet card resulted in -a decrease from 149 Mbytes/sec to 115 Mbytes/sec. Something to keep in -mind when doing really high speed things with 64 bit PCI adapters. - -Keyboard: -If you experience SRM errors like "ERROR: scancode 0xa3 not supported -on PCXAL" after halting FreeBSD you should update your SRM firmware -to V7.2-1 or later. This SRM version is first available on the Firmware -Update CD V5.7, or on http://www.compaq.com The problem is fixed on both -Miata MX5 and Miata GL. - -USB: -Supported by FreeBSD 4.1 and later. - -Power: -Disconnect the power cord before dismantling the machine, the soft-power -switch keeps part of the logic powered even when the machine is switched -off. - -The kernel configuration file for a Miata kernel must contain: - options DEC_ST550 - cpu EV5 - -* -* DEC3000 family (the "Bird" machines) -* - -The DEC3000 series were among the first Alpha machines ever produced. They -are based on an I/O bus called the Turbo Channel (TC) bus. These -machines are built like tanks (watch your back). - -DEC3000 can be subdivided in DEC3000/500-class and DEC3000/300-class. -The DEC3000/500-class is the early high-end workstation/server Alpha family. -Servers use serial consoles, workstations have graphics tubes. -DEC3000/300-class is the lower-cost workstation class. - -DEC3000/500-class are quite fast (considering their age) thanks to the -good memory design. DEC3000/300 is crippled compared to DEC3000/500 because -of its much narrower memory bus. - -They are called 'Birds' because their internal DEC code names were bird -names: - - DEC3000/400 Sandpiper 133MHz CPU, desktop - DEC3000/500 Flamingo 150MHz CPU, floor standing - DEC3000/500X Hot Pink 200MHz CPU, floor standing - DEC3000/600 Sandpiper+ 175MHz CPU, desktop - DEC3000/700, Sandpiper45 225MHz CPU, floor standing - DEC3000/800, Flamingo Ultra 200MHz CPU, floor standing - DEC3000/900, Flamingo45 275MHz CPU, floor standing - - DEC3000/300 Pelican 150MHz CPU, desktop, 2 TC slots - DEC3000/300X Pelican+ 175MHz CPU, desktop, 2 TC slots - DEC3000/300LX Pelican+ 125MHz CPU, desktop, 2 TC slots - DEC3000/300L 100MHz CPU, desktop, no TC slots - - -Features: -- 21064 CPU (100 to 200 MHz) - 21064A CPU (225 to 275 MHz) -- memory bus: 256 bit, with ECC [DEC3000/500-class] - 64 bit, with ECC [DEC3000/300-class] -- memory: - proprietary 100pin SIMMs - installed in sets of 8 [DEC3000/500-class] - - PS/2 style 72pin 36 bit FPM SIMMs, 70ns or better - used in pairs of 2 [DEC3000/300-class] -- Bcache / L2 cache: varying sizes, 512 kB to 2 Mbyte -- built-in 10Mbit Ethernet based on a Lance 7990 chip, AUI and UTP -- one or two SCSI buses based on a NCR53C94 or a NCR53CF94-2 chip -- 2 serial ports based on Zilog 8530 (one usable as a serial console) -- embedded ISDN interface -- on-board 8 bit sound -- 8 bit graphics on-board [some models] or via a TC card [some other models] - -SCSI: -Currently DEC3000 machines can only be used diskless on FreeBSD/alpha. The -reason for this is that the SCSI drivers needed for the TC SCSI adapters -were not brought into CAM that the recent FreeBSD versions use. TC option -cards for single (PMAZ-A) or dual fast SCSI (PMAZC-AA) are also available. -And currently have no drivers on FreeBSD either. - -DEC3000/300 has 5Mbytes/sec SCSI on-board. This bus is used for both internal -and external devices. DEC3000/500 has 2 SCSI buses. One is for internal -devices only, the other one is for external devices only. - -Floppy devices found in the DEC3000s are attached to the SCSI bus (via a -bridge card). This makes it possible to boot from them using the same device -names as ordinary SCSI hard-disks (>>> BOOT DKA300 for example). - -Expansion: -The 3000/300 series has a half-speed TurboChannel compared to the other -3000 machines. Some TC expansion cards have troubles with the half-speed -bus. Caveat emptor. - -ISDN interface: -ISDN does not work on FreeBSD. - -Memory: -DEC3000/300-class uses standard 36 bit, 72 pin Fast Page Mode SIMMs. -EDO SIMMs, 32 or 33 bit SIMMs all will not work in Pelicans. -For 32Mbyte SIMMs to work on the DEC3000/300-class the presence detect -bits/pins of the SIMM must correspond to what the machine expects. If they -don't, the SIMM is 'seen' as a 8 Mbyte SIMM. 8 Mbyte and 32 Mbyte SIMMs can -be mixed, as long as the pairs themselves are identical. - -When you find yourself in need of fixing 32Mbyte SIMMs that lack correct -presence bits the following info might be of use: - -There are four presence detection bits on PS/2 SIMMs. Two of -the bits indicate the access time. The other two indicate the memory size. - -At one end of the SIMM there are two rows of four solder pads. One -row is connected to Vss (GND) and the other is connected to pins -67 (PRD1), 68 (PRD2), 69 (PRD3), 70 (PRD4). - -If you bridge a pair of pads with a small resistor or a drop of -solder you ground that particular bit. - - PRD1 PRD2 mem. size - ----------------------------- - GND GND 4 or 64 Mbyte - Open GND 2 or 32 Mbyte - GND Open 1 or 16 Mbyte - Open Open 8 Mbyte - - PRD3 PRD4 access time - ------------------------------ - GND GND 50 or 100 nsec - Open GND 80 nsec - GND Open 70 nsec - Open Open 60 nsec - -DEC3000/500-class can use 2, 4, 8, 16 and 32 Mbyte 100pin SIMMs. -Note that the maximum memory size varies from system to system, -desktop machines have sacrificed box size for less memory SIMM sockets. -Given enough sockets and enough SIMMs you can get to 512 Mbytes maximum. -This is one of the main differences between floor standing and desktop -machines, the latter have far less SIMM sockets. - -Sound: -The sound hardware is not supported on any of the Birds. - -Graphics: -The is no X-Windows version available for the TC machines. -DEC3000/300 needs a serial console. DEC3000/500-class might -work with a graphical console. I ran mine with a serial console so I cannot -verify this. - -Birds can be obtained from surplus sales etc. As they are not PCI -based they are no longer actively maintained. TC expansion boards can -be difficult to obtain these days and support for them is not too good -unless you write/debug the code yourself. Programming information for TC -boards is hard to find. Birds are recommended only if a. you can get them -cheap and b. if you prepared to work on the code to support them better. - -For the DEC3000/[4-9]00 series machines the kernel config file must -contain: - options DEC_3000_500 - cpu EV4 - -For the DEC3000/300 ("Pelican") machines the kernel config file must -contain: - options DEC_3000_300 - cpu EV4 - -* -*Evaluation Board 64plus ("EB64+"), Aspen Alpine -* - -In its attempts to popularize the Alpha CPU DEC produced a number of so -called Evaluation Boards. The EB64+ family boards have the following feature -set: - -- 21064 or 21064A CPU, 150 to 275MHz -- memory bus: 128 bit -- memory: PS/2 style 72 pin 33 bit Fast Page Mode SIMMs, - 70ns or better, - installed in sets of 4 - 8 SIMM sockets - uses parity -- Bcache / L2 cache: 512 kByte, 1 Mbyte or 2 Mbytes -- 21072 ("APECS") chip set -- Intel 82378ZB PCI to ISA bridge chip ('Saturn') -- dual 16550A serial ports -- Symbios 53C810 Fast-SCSI -- embedded 10 Mbit Ethernet -- 2 PCI slots -- 3 ISA slots - -Aspen Alpine: -Aspen Alpine is slightly different, but is close enough to the EB64+ to -run an EB64+ SRM EPROM (mine did..). The Aspen Alpine does not have -an embedded Ethernet, has 3 instead of 2 PCI slots. It comes with 2 Mbytes -of cache already soldered onto the mainboard. It has jumpers to select -the use of 60, 70 or 80ns SIMM speeds. - -Memory: -36 bits SIMMs work fine, 3 bits simply remain unused. - -SRM: -The SRM console code is housed in an UV-erasable EPROM. No easy flash SRM -upgrades for the EB64+ The latest SRM version available for EB64+ is quite -ancient anyway. - -SCSI: -The EB64+ SRM can boot both 53C810 and Qlogic1040 SCSI adapters. Pitfall for -the Qlogic is that the firmware that is down-loaded by the SRM onto the -Qlogic chip is very old. There are no updates for the EB64+ SRM available. -So you are stuck with old Qlogic bits too. I have had quite some problems -when I wanted to use Ultra-SCSI drives on the Alpine with Qlogic. The -FreeBSD/alpha kernel can be compiled to include a much newer Qlogic firmware -revision. This is not the default because it adds hundreds of kBytes worth -of bloat to the kernel. In FreeBSD 4.1 and later the isp firmware is contained -in a kernel loadable module. All of this might mean that you need to use a -non-Qlogic adapter to boot from. - -For the EB64+ class machines the kernel config file must contain: - options DEC_EB64PLUS - cpu EV4 - -* -* Evaluation Board 164 ("EB164, PC164, PC164LX, PC164SX") family -* - -EB164 is a newer design evaluation board, based on the 21164A CPU. This -design has been used to 'spin off' multiple variations, some of which are -used by OEM manufacturers/assembly shops. Samsung did its own PC164LX -which has only 32 bit PCI, whereas the Digital variant has 64 bit PCI. - -Features: -- 21164A, multiple speed variants [EB164, PC164, PC164LX] - 21164PC [only on PC164SX] -- 21174 (Alcor) chip set -- Bcache / L3 cache: EB164 uses special cache-SIMMs -- memory bus: 128 bit / 256 bit -- memory: PS/2 style SIMMs in sets of 4 or 8, - 36 bit, Fast Page Mode, uses ECC, [EB164 and PC164] - SDRAM DIMMs in sets of 2, uses ECC [PC164SX and PC164LX] -- dual 16550A serial ports -- PS/2 style keyboard & mouse -- floppy controller -- parallel port -- 32 bits PCI -- 64 bits PCI [some models] -- ISA slots via an Intel 82378ZB PCI to ISA bridge chip - -Memory: -Using 8 SIMMs for a 256bit wide memory can yield interesting speedups over -a 4 SIMM/128bit wide memory. Obviously all 8 SIMMs must be of the same type -to make this work. The system must be explicitly setup to use the -8 SIMM memory arrangement. You must have 8 SIMMs, 4 SIMMs distributed -over 2 banks does not work. - -SCSI: -The SRM can boot from Qlogic 10xx boards or the Symbios 53C810[A]. - -Newer Symbios 810 revisions like the Symbios 810AE are not recognized by -the SRM on PC164. PC164 SRM does not appear to recognize a Symbios 53C895 -based host adapter (tested with a Tekram DC-390U2W). On the other hand -some no-name Symbios 53C985 board has been reported to work. - -Cards like the Tekram DC-390F (Symbios875 based) have been confirmed to -work fine on the PC164. Unfortunately this seems to be dependent on the -actual version of the chip/board. - -Symbios 53C825[a] will also work as boot adapter. Diamond FirePort, although -based on Symbios chips, is not bootable by the PC164SX SRM. -PC164SX is reported to boot fine with Symbios825, Symbios875 and Symbios876 -based cards. In addition, Adaptec 2940U and 2940UW are reported to work for -booting (verified on SRM V5.7-1). Adaptec 2930U2 and 2940U2[W] do not work. - -LX and SX with SRM firmware version 5.8 or later can boot from Adaptec -2940-series adapters. - -In summary: this family of machines is 'blessed' with a challenging -compatibility as far as SCSI adapters go. - -SRM quirks: -PC164 the SRM sometimes seems to loose its variable settings. -"For PC164, current superstition says that, to avoid losing settings, -you want to first downgrade to SRM 4.x and then upgrade to a 5.x" -One sample error that was observed was: "ERROR: ISA table corrupt!". -A sequence of a downgrade to SRM4.9, an 'isacfg -init' and an 'init' -made the problem go away. Some PC164 owners report they have never seen -the problem. - -On PC164SX the AlphaBIOS allows you a selection to select 'SRM' to -be used as console on the next power up. This selection does not appear to -have any effect. In other words, you will get to the AlphaBIOS regardless -of what you select. The fix is to reflash the console ROM with the SRM -code for PC164SX. This will overwrite the AlphaBIOS and will get you the -SRM console you desire. The SRM code can be found on the Compaq Web site. - -IDE: -PC164 can boot from IDE disks assuming your SRM version is recent enough. - -Power: -EB164 needs a power supply that supplies 3.3 Volts. PC164 does not implement -the PS_ON signal that ATX power supplies need to switch on. A simple switch -pulling this signal to ground fixes this problem. - -For the EB164 class machines the kernel config file must contain: - options DEC_EB164 - cpu EV5 - - -* -* AlphaStation 200 ("Mustang") and 400 ("Avanti") series -* - -The Digital AlphaStation 200 and 400 series systems are early PCI based -workstations for the lower end. The 200 and 250 series is a desktop box, the -400 series is a desk-side mini-tower. - -Features: -- 21064 or 21064A CPU at speeds of 166 to 333 MHz -- DECchip 21071-AA (core logic chip-set) consisting of: - Cache/memory controller (one 21071-CA chip) - PCI interface (one 21071-DA chip) - Data path (two 21071-BA chips) -- Bcache / L2 cache: 512 Kbytes (200 and 400 series) - 2048KBytes (250 series) -- memory bus: 64 bit -- memory: 8 to 384 MBytes of RAM, - 70 ns or better Fast Page DRAM, - in three pairs (200 and 400 series) - in two quads, so banks of four. (250 series) - uses parity -- PS/2 keyboard and mouse port -- two 16550 serial ports -- parallel port -- floppy disk interface -- 32 bit PCI expansion slots (3 for 400 series, 2 for 200 & 250 series) -- ISA expansion slots (4 for 400 series, 2 for 200 & 250 series) - (some ISA/PCI slots are physically shared) -- embedded 21040-based Ethernet (200 & 250 series) -- embedded Symbios 53c810 Fast SCSI-2 chip -- Intel 82378IB ("Saturn") PCI-ISA bridge chip -- graphics is embedded TGA or PCI VGA (model dependent) -- 16 bit sound (on 200 & 250 series) - -Memory: -the system uses parity memory SIMMs, but it does not need 36 bit wide SIMMs. -33 bit wide SIMMs are sufficient, 36 bit SIMMs are acceptable too. EDO or 32 -bit SIMMs will not work. 4, 8, 16, 32 and 64 Mbyte SIMMs are supported. - -Sound: -The AS200 & AS250 sound hardware is reported to work OK assuming you have -the following line in your kernel config file: - - device pcm0 at isa? port 0x530 irq 9 drq 0 flags 0x10011 - -SCSI: -AlphaStation 200 & 250 series has an automatic SCSI terminator. This means that -as soon as you plug a cable onto the external SCSI connector the internal -terminator of the system is disabled. It also means that you should not -leave unterminated cables plugged into the machine. - -AlphaStation 400 series have an SRM variable that controls termination. In -case you have external SCSI devices connected you must set this SRM -variable using: "set control_scsi_term external". If only internal SCSI devices -are present use: "set control_scsi_term internal" - -For the AlphaStation-[24][05]00 machines the kernel config file must contain: - options DEC_2100_A50 - cpu EV4 - - -* -* AlphaStation 500 and 600 ("Alcor" & "Maverick" for EV5, "Bret" for EV56) -* -AS500 and 600 were the high-end EV5 / PCI based workstations. EV6 based -machines have in the meantime taken their place as front runners. AS500 is -a desktop in a dark blue case (TopGun blue), AS600 is a sturdy desk-side box. -AS600 has a nice LCD panel to observe the early stages of SRM startup. - -Features: -- 21164 EV5 CPU at 266, 300, 333, 366, 400, 433, 466, or 500 MHz (AS500) - at 266, 300 or 333 MHz (AS600) -- 21171 or 21172 (Alcor) core logic chip-set -- cache: 2 or 4 Mb L3 / Bcache (AS600 at 266 MHz) - 4 Mb L3 / Bcache (AS600 at 300 MHz) - 2 or 8 Mb L3 / Bcache (8 Mb on 500 MHz version only) - 2 to 16 Mb L3 / Bcache (AS600; 3 cache-SIMM slots) -- memory bus: 256 bits, uses ECC -- memory: AS500: industry standard 8 byte wide DIMMs - 8 DIMM slots - installed in sets of 4, - maximum memory is 1 Gb (512 Mb max on 333 MHz CPUs) - uses ECC - AS600: industry standard 36 bit Fast Page Mode SIMMs - 32 SIMM slots, - installed in sets of 8, - maximum memory is 1 Gb - uses ECC -- Qlogic 1020 based wide SCSI bus (1 bus/chip for AS500, 2 for AS600) -- 21040 based 10 Mbit Ethernet adapter with both Thinwire and UTP connectors -- expansion: AS500: 3 32-bit PCI slots - 1 64-bit PCI slot - AS600: 2 32-bit PCI slot - 3 64-bit PCI slots - 1 PCI/EISA physically shared slot - 3 EISA slots - 1 PCI and 1 EISA slot are occupied by default -- 21050 PCI-to-PCI bridge chip -- Intel 82375EB PCI-EISA bridge (AS600 only) -- 2 16550A serial ports -- 1 parallel port -- 16 bit audio Windows Sound System, - in dedicated slot (AS500) - in EISA slot (AS600, this is an ISA card) -- PS/2 keyboard and mouse port - -SCSI: -Early machines had Fast SCSI interfaces, later ones are Ultra SCSI capable. -AS500 shares its single SCSI bus with internal and external devices. For a -Fast SCSI bus you are limited to 1.8 meters bus length external to the box. -+++ This is what some DEC docs suggest. Did they ever go Ultra? - -AS600 has one Qlogic chip dedicated to the internal devices whereas the -other one is dedicated to external SCSI devices. - -Memory: -In AS500 DIMMs are installed in sets of 4, in 'physically interleaved' -layout. So, a bank of 4 DIMMs is *not* 4 adjacent DIMMs! - -In AS600 the memory SIMMs are placed onto two memory daughter cards. SIMMs -are installed in sets of 8. Both memory daughter cards must be populated -identical. - -PCI: -AS600 has a peculiarity for its PCI slots. AS600 (or rather the PCI -expansion card containing the SCSI adapters) does not allow I/O port -mapping, therefore all devices behind it must use memory mapping. -If you have problems getting the SCSI adapters to work, add the following -option to /boot/loader.rc: - - set isp_mem_map=0xff - -This may need to be typed at the boot loader prompt before booting the -installation kernel. - -For the AlphaStation-[56]00 machines the kernel config file must contain: - options DEC_KN20AA - cpu EV5 - -* -* AlphaServer 1000 ("Mikasa"), 1000A ("Noritake") and 800 -* -The AlphaServer 1000 and 800 range of machines is aimed as departmental servers. -They come in quite some variations in packaging and mainboard/cpu. Generally -speaking there are 21064 (EV4) CPU based machines and 21164 (EV5) based -ones. The CPU is on a daughter card, and the type of CPU (EV4 or EV5) must -match the mainboard in use. AlphaServer 800 is a much smaller mini tower -case, it lacks the StorageWorks SCSI hot-plug chassis. The main difference -between AS1000 and AS1000A is that AS1000A has 7 PCI slots whereas AS1000 -only has 3 PCI slots and has EISA slots instead. AS800 with an EV5/400 MHz -CPU was later re-branded as a DIGITAL Server 3300[R], AS800 with an EV5/500 MHz -CPU was later re-branded as a DIGITAL Server 3305[R]. - -Features: -- 21064 EV4[5] CPU at 200, 233 or 266 MHz - 21164 EV5[6] CPU at 300, 333 or 400 MHz (or 500 MHz for AS800 only) -- cache: -- memory bus: 128 bit with ECC -- memory: - AS1000[A]-systems: - Use 72pin 36 bit Fast Page Mode SIMMs, 70ns or better - 16 or 20 SIMM slots - max memory is 1 Gb - uses ECC - AS800: - Uses ECC EDO DIMMs. -- embedded VGA (on some mainboard models) -- expansion: - 3 PCI, 2 EISA, 1 64-bit PCI/EISA combo (AS800) - 7 PCI, 2 EISA (AS1000A) - 2 PCI, 1 EISA/PCI, 7 EISA (AS1000) -- embedded SCSI based on Symbios 810 [AS1000] or Qlogic 1020 [AS1000A] - -Box: -AS1000 based machines come in multiple boxes. Floor standing, rack-mount, -with or without StorageWorks SCSI chassis etc. The electronics are the -same. - -Memory: - AS1000-systems: - All EV4 based machines use standard PS/2 style 36 bit 72pin SIMMs in sets - of 5. The fifth SIMM is used for ECC. - All EV5 based machines use standard PS/2 style 36 bit 72pin SIMMs in sets - of 4. The ECC is done based on the 4 extra bits per SIMM (4 bits out of 36). - The EV5 mainboards have 16 SIMM slots, the EV4 mainboards have 20 slots. - - AS800: - Uses DIMMs in sets of 4. DIMM installation must start in slots marked - bank 0. A bank is four physically adjacent slots. The biggest size DIMMs - must be installed in bank 0 in case 2 banks of different DIMM sizes are - used. Max memory size is 2Gb. Note that these are EDO DIMMs, not SDRAM. - -Console: -The AS1000/800 are somewhat stubborn when it comes to serial -consoles. They need >>> SET CONSOLE SERIAL before they go for -a serial console. Pulling the keyboard from the machine is not sufficient, -like it is on most other Alpha models. Going back to a graphical console -needs >>> SET CONSOLE GRAPHICS at the serial console. - -SCSI: -For AS800 you want to check if your Ultra-Wide SCSI is indeed in Ultra mode. -This can be done using the EEROMCFG.EXE utility that is on the Firmware -Upgrade CDROM. - -For the AlphaServer1000/1000A/800 machines the kernel config file must contain: - options DEC_1000A - cpu EV4 # depends on the CPU model installed - cpu EV5 # depends on the CPU model installed - -* -* DS10/VS10/XP900 ("Webbrick") / XP1000 ("Monet") / DS10L ("Slate") -* -Webbrick and Monet are high performance workstations/servers based on the -EV6 CPU and the Tsunami chipset. Tsunami is also used in much higher-end -systems and as such has plenty of performance to offer. DS10, VS10 and XP900 -are different names for essentially the same system. The difference are the -software and options that are supported. DS10L is a DS10 based machine in a 1U -high rackmount enclosure. DS10L is intended for ISPs and for HPTC clusters -(e.g. Beowulf). - -Monet has, by 1999 standards, *stunning* (the words of a satisfied -user) memory and I/O system bandwidth. - -** Webbrick / Slate - -Features: -- 21264 EV6 CPU at 466 MHz -- L2 / Bcache: 2MB, ECC protected -- memory bus: 128 bit via crossbar, 1.3GB/sec to memory -- memory: industry standard 200 pin 83 MHz buffered ECC SDRAM DIMMs - 4 DIMM slots (2 for DS10L) - installed in pairs of 2 - max memory is 2 Gb (1Gb for DS10L) -- 21271 Core Logic chipset ("Tsunami") -- 2 on-board 21143 Fast Ethernet controllers -- AcerLabs M5237 (Aladdin-V) USB controller -- AcerLabs M1533 PCI-ISA bridge -- AcerLabs Aladdin ATA-33 controller -- embedded dual EIDE -- expansion: 3 64-bit PCI slots - 1 32-bit PCI slots - DS10L has a single 64bit PCI slot -- 2x 16550A serial ports -- 1x parallel port -- 2x USB -- PS/2 keyboard & mouse port - -Power: -The system has a smart power controller. This means that parts of the system -remain powered when it is switched off (like an ATX-style PC power supply). -Before servicing the machine remove the power cord. - -Case: -Webbrick is shipped in a desktop-style case similar to the older 21164 -"Maverick" workstations but which offers much better access to -components. If you intend to build a farm you can rackmount them in a 19" -rack, they are 3U high. Slate is 1U high but has only one PCI slot. - -Memory: -DS10 has 4 DIMM slots. DIMMs are installed as pairs. Please note that -DIMM pairs are not installed in adjacent DIMM sockets but rather physically -interleaved. DIMM sizes of 32, 64, 128, 256 and 512 Mbytes are supported. - -When 2 pairs of identical-sized DIMMs are installed DS10 will use memory -interleaving for higher performance. DS10L, which has only 2 DIMM slots cannot -do interleaving. - -SCSI: -Starting with SRM firmware version 5.9 you can boot from Adaptec 2940-series -adapters in addition to the usual set of Qlogic and Symbios/NCR adapters. - -EIDE: -The base model comes with a FUJITSU 9.5GB ATA disk as its boot device. -FreeBSD/alpha works just fine using EIDE disks on Webbrick. DS10 has 2 IDE -interfaces on the mainboard. - -Expansion: -On the PCI bus 32 and 64 bit cards are supported, in 3.3V and 5V variants. - -USB: -Is supported in FreeBSD 4.1 and later. - -The kernel config file must contain: - options DEC_ST6600 - cpu EV5 - -Contrary to expectation there is no 'cpu EV6' defined for inclusion in the -kernel config file. The 'cpu EV5' is mandatory to keep config(8) happy. - -** Monet - -Features: -- 21264 EV6 at 500 MHz - 21264 EV67 at 500 or 667 MHz (XP1000G, codenamed Brisbane) - CPU is mounted on a daughter-card which is field-upgradable -- L2 / Bcache: 4MB, ECC protected -- memory bus: 256 bit -- memory: 128 or 256 Mbytes 100 MHz (PC100) 168 pin JEDEC standard, - registered ECC SDRAM DIMMs -- 21271 Core Logic chip-set ("Tsunami") -- 1 on-board 21143 Ethernet controller -- Cypress 82C693 USB controller -- Cypress 82C693 PCI-ISA bridge -- Cypress 82C693 controller -- expansion: 2 independent PCI buses, driven by high-speed I/O - channels called 'hoses': - hose 0: (the upper 3 slots) - 2 64-bit PCI slots - 1 32-bit PCI slot - hose 1: (the bottom 2 slots) - 2 32-bit PCI slots (behind a 21154 PCI-PCI bridge) - 2 of the 64-bit PCI slots are for full-length cards - all of the 32-bit PCI slots are for short cards - 1 of the 32-bit PCI slots is physically shared with an ISA slot - all PCI slots run at 33MHz -- 1x Ultra-Wide SCSI port based on a Qlogic 1040 chip -- 2x 16550A serial port -- 1x parallel port -- PS/2 keyboard & mouse port -- embedded 16-bit ESS ES1888 sound chip -- 2x USB -- graphics options: ELSA Gloria Synergy or DEC/Compaq PowerStorm 3D - accelerator cards - -Case: -Monet is housed in a mini-tower like enclosure quite similar to the Miata -box. - -SCSI: -The on-board Qlogic UW-SCSI chip supports up to 4 internal devices. There is -no external connector for the on-board SCSI. - -Memory: -For 500 MHz CPUs 83 MHz DIMMs will do. Compaq specifies PC100 DIMMs for -all CPU speeds. DIMMs are installed in sets of 4, starting with the -DIMM slots marked '0'. Memory capacity is max 4 Gb. -DIMMs are installed 'physically interleaved', note the markings of the -slots. Memory bandwidth of Monet is twice that of Webbrick. The DIMMs live -on the CPU daughter-card. Note that the system uses ECC RAM so you need DIMMs -with 72 bits (not the PC-class 64 bit DIMMs) - -EIDE: -Is usable / bootable for system disk so FreeBSD can be rooted on an EIDE -disk. Although the Cypress chip has potential for 2 EIDE channels Monet uses -only one of them. - -USB: -If you experience problems trying to use the USB interface please check if -the SRM variable "usb_enable" is set to "on". You can change this by -performing: "set usb_enable on" at the SRM >>> prompt. - -Expansion caveats: -- Don't try to use Symbios-chip based SCSI adapters in the PCI slots -connected to hose 1. There is a not-yet-found FreeBSD bug that prevents this -from working correctly. -- Not all VGA cards will work behind the PCI-PCI bridge (so in slots 4 & 5). -Only cards that implement VGA-legacy addressing correctly will work. Workaround -is to put the VGA card 'before' the bridge. - -Sound: -The sound chip is not currently supported with FreeBSD. There is work in -progress in this area. - -The kernel config file must contain: - options DEC_ST6600 - cpu EV5 - -Contrary to expectation there is no 'cpu EV6' defined for inclusion in the -kernel config file. The 'cpu EV5' is mandatory to keep config(8) happy. - -** DS20/DS20E ("Goldrush"): - -Features: -- 21264 EV6 CPU at 500 or 670 MHz -- dual CPU capable machine -- L2 / Bcache: 4 Mbytes per CPU -- memory bus: dual 256 bit wide with crossbar switch -- memory: SDRAM DIMMs - installed in sets of 4 - uses ECC - 16 DIMM slots - max. 4Gb -- 21271 Core Logic chip-set ("Tsunami") -- embedded Adaptec ? Wide Ultra SCSI -- expansion: 2 independent PCI buses, driven by high-speed I/O - channels called 'hoses' - 6 64-bit PCI slots (3 per hose) - 1 ISA slot - -Console: -DS20 needs >>> SET CONSOLE SERIAL before it goes for a serial console. -Pulling the keyboard from the machine is not sufficient. Going back to a -graphical console needs >>> SET CONSOLE GRAPHICS at the serial console. -Confusing is the fact that you will get SRM console output on the graphics -console with the console set to serial, but when FreeBSD boots it honors -the CONSOLE variable setting and all the boot messages as well as the -login prompt will go to the serial port. - -Case: -DS20 is housed in a fat cube-like enclosure. The enclosure also -contains a StorageWorks SCSI hot-swap shelf for a maximum of 7 3.5" SCSI -devices. DS20E is a sleeker case, without the StorageWorks shelf. - -Embedded SCSI: -The embedded Adaptec SCSI chip on DS20 is disabled and is therefore -not usable under FreeBSD. - -Starting with SRM firmware version 5.9 you can boot from Adaptec 2940-series -adapters in addition to the usual set of Qlogic and Symbios/NCR adapters. -This unfortunately does not include the embedded Adaptec SCSI chips. - -Memory: -If you are using banks of DIMMs of different sizes the biggest DIMMs should -be installed in the DIMM slots marked '0' on the mainboard. The DIMM slots -should be filled 'in order' so after bank 0 install in bank 1 and so on. - -Expansion: -Don't try to use Symbios-chip based SCSI adapters in the PCI slots -connected to hose 1. There is a not-yet-found FreeBSD bug that prevents this -from working correctly. DS20 ships by default with a Symbios on hose 1 so you -have to move this card before you can install/boot FreeBSD on it. - -The kernel config file must contain: - options DEC_ST6600 - cpu EV5 - -Contrary to expectation there is no 'cpu EV6' defined for inclusion in the -kernel config file. The 'cpu EV5' is mandatory to keep config(8) happy. - -** AlphaPC 264DP / UP2000 - -Features: -- 21264 EV6 CPU at 670 MHz -- dual CPU capable -- L2 / Bcache: 4 Mbytes per CPU -- memory bus: 256 bit -- memory: SDRAM DIMMs - installed in sets of 4 - uses ECC - 16 DIMM slots - max. 4Gb -- 21272 Core Logic chip-set ("Tsunami") -- embedded Adaptec AIC7890/91 Wide Ultra SCSI -- 2x embedded IDE based on Cypress 82C693 chips -- embedded USB via Cypress 82C693 -- expansion: 2 independent PCI buses driven by high-speed I/O - channels called 'hoses' - 6 64-bit PCI slots (3 per hose) - 1 ISA slot - -Memory: -A maximum of 2Gb memory is supported by FreeBSD. - -Embedded SCSI: -The on-board Adaptec is not bootable but works with FreeBSD 4.0 and later -as a datadisk-only SCSI bus. - -Embedded IDE: -Busmaster DMA is supported on the first IDE interface only. - -The kernel config file must contain: - options DEC_ST6600 - cpu EV5 - -Contrary to expectation there is no 'cpu EV6' defined for inclusion in the -kernel config file. The 'cpu EV5' is mandatory to keep config(8) happy. - -* -* AlphaServer 2000 ("DemiSable"), 2100 ("Sable"), 2100A ("Lynx") -* - -The AlphaServer 2[01]00 machines are aimed as departmental servers. -This is medium iron, not a hobbyist system. These are multi-CPU machines, -up to 2 CPUs (AS2000) or 4 CPUs (2100[A]) can be installed. -Both floor-standing and 19" rackmount boxes exist. Rackmount variations have -different numbers of I/O expansion slots, different max number of CPUs and -different maximum memory size. Some of the boxes come with an integral -StorageWorks shelf to house hot-swap SCSI disks. There was an upgrade program -available to convert your Sable machine into a Lynx by swapping the -I/O backplane (the C-bus backplane remains). CPU upgrades were available -as well. - -Features: -- 21064 EV4[5] CPU[s] at 200, 233, 275 MHz -- 21164 EV5[6] CPU[s]s at 250, 300, 375, 400 MHz -- cache: varies in size with the CPU model; 1, 4 or 8Mbyte per CPU -- embedded floppy controller driving a 2.88 Mbytes drive -- embedded 10Mbit 21040 Ethernet [AS2100 only] -- 2 serial ports -- 1 parallel port -- PS/2 style keyboard & mouse port - -NOTE: Lynx support is currently flagged as experimental due to lack of - testing / test hardware. - -CPU: -The CPUs spec-ed as 200 MHz are in reality running at 190 MHz. Maximum -number of CPUs is 4. All CPUs must be of the same type/speed. - -If any of the processors are ever marked as failed, they will -remain marked as failed even after they have been replaced (or reseated) -until you issue the command 'clear_error all' on the SRM console and -power-cycle the machine. This may be true for other modules (IO and memory) -as well, but it has not been verified. - -Memory: -The machines use dedicated memory boards. These boards live on a 128 bit -C-bus shared with the CPU boards. DemiSable supports up to 1Gb, Sable up -to 2Gb. One of the memory bus slots can either hold a CPU or a memory card. -A 4 CPU machine can have a maximum of 2 memory boards. - -Some memory board modules house SIMMs. These are called SIMM carriers. -There are also memory modules that have soldered-on memory chips -instead of SIMMs. These are called 'flat memory modules'. - -SIMM boards are used in sets of eight 72-pin 36 bit FPM memory of 70ns -or faster. SIMM types supported are 1Mb x36 bit (4 Mbyte) and 4Mb x36 -bit (16 Mbyte). Each memory board can house 4 banks of SIMMs. SIMM -sizes can not be mixed on a single memory board. The first memory -module must be filled with SIMMs before starting to fill the next -memory module. Note that the spacing between the slots is not that -big, so make sure your SIMMs fit physically (before buying them..) - -Console: -Both Lynx and Sable are somewhat stubborn when it comes to serial -consoles. They need >>> SET CONSOLE SERIAL before they go for -a serial console. Pulling the keyboard from the machine is not sufficient, -like it is on most other Alpha models. Going back to a graphical console -needs >>> SET CONSOLE GRAPHICS at the serial console. On Lynx keep the -VGA card in one of the primary PCI slots. - -The machines are equipped with a small OCP (Operator Control Panel) LCD -screen. On this screen the self-test messages are displayed during system -initialization. You can put your own little text there by using the SRM: ->>> SET OCP_TEXT "FreeBSD" - -The SRM >>> SHOW FRU command produces an overview of your configuration -with module serial numbers, hardware revisions and error log counts. - -Embedded SCSI: -Both Sable, DemiSable and Lynx have Symbios 810 based Fast SCSI on-board. -Check if it is set to Fast SCSI speed by >>> SHOW PKA0_FAST. If set to -1 it is negotiating for Fast speeds. >>> SET PKA0_FAST 1 enables Fast -speeds. - -Internal disk storage: -AS2100[A] come equipped with a StorageWorks 7 slot SCSI cage. A second cage -can be added inside the cabinet. AS2000 has a single 7 slot SCSI cage, -which cannot be expanded with an additional one. Note that the slot -locations in these cages map differently to SCSI IDs compared to the -standard StorageWorks shelves. Slot IDs from top to bottom -are 0, 4, 1, 5, 2, 6, 3 when using a single bus configuration. The cage -can also be set to provide two independent SCSI buses. This is used for -embedded RAID controllers like the KZPSC (Mylex DAC960). Slot ID assignments -for split bus are, from top to bottom: 0A, 0B, 1A, 1B, 2A, 2B, 3A, 3B. -Where A and B signify a SCSI bus. In a single bus configuration the -terminator module on the back of the SCSI cage is on the TOP. The jumper -module is on the BOTTOM. For split bus operation these two modules are -reversed. The terminator can be distinguished from the jumper by noting the -chips on the terminator. The jumper does not have any active components on -it. - -Expansion: -DemiSable has 7 EISA slots and 3 PCI slots. Sable has 8 EISA and 3 PCI -slots. Lynx, being newer, has 8 PCI and 3 EISA slots. The Lynx PCI slots -are grouped in sets of 4. The 4 PCI slots closest to the CPU/memory -slots are the primary slots, so logically before the PCI bridge chip. -Note that contrary to expectation the primary PCI slots are the highest -numbered ones (PCI4 - PCI7). - -Make sure you run the EISA Configuration Utility (from floppy) when -adding/change expansion cards in EISA slots or after upgrading your -console firmware. This is done by inserting the ECU floppy and typing -RUNECU at the SRM >>> prompt. - - NOTE: EISA slots are currently unsupported, but the Compaq Qvision - EISA VGA adapter is treated as an ISA device. It therefore - works OK as a console. - -A special Extended I/O module for use on the C-bus was planned-for. -Whether they ever saw daylight is unknown. In any case FreeBSD has never -been verified with an ExtIO module. - -Power: -The machines can be equipped with redundant power supplies. Note that -the enclosure is equipped with interlock switches that switch off power -when the enclosure is opened. The system's cooling fans are speed -controlled. When the machine has more than 2 CPUs and more than 1 memory -board dual power supplies are mandatory. - -The kernel config file must contain: - options DEC_2100_A500 - cpu EV4 - cpu EV5 - -* -* AlphaServer 4100 ("Rawhide") -* - -The AlphaServer 4100 machine is aimed as an enterprise server. -Expect a 30" high pedestal cabinet or alternatively the same system box in a -19" rack. This is medium iron, not a hobbyist system. -These are multi-CPU machines, up to 4 CPUs can be in a single -machine. Basic disk storage is housed in one or two StorageWorks shelves -at the bottom of the pedestal. The Rawhides intended for the NT market are -designated DIGITAL Server 7300 (5/400 CPU), DIGITAL Server 7305 (5/533 CPU). -A trailing R on the part-number means a rackmount variant. - -Features: -- 21164 EV5 CPUs at 266, 300 MHz - 21164A EV56 CPUs at 400, 466, 533, 600 and 666 Mhz -- cache: 4 Mbytes per CPU (EV5 300 MHz was also available cache-less) - 8 Mbytes (EV5 600Mhz only) -- memory bus: 128 bit with ECC -- embedded floppy controller -- 2 serial ports -- 1 parallel port -- PS/2 style keyboard & mouse port - -Memory: -Rawhide uses a maximum of 8 RAM modules. These modules are used in pairs -and supply 72 bits to the bus (this includes ECC bits). Memory can be EDO -RAM or synchronous DRAM. A fully populated Rawhide has 4 pairs of memory -modules. Given the choice use SDRAM for best performance. The highest -capacity memory board must be in memory slot 0. A mix of memory board sizes -is allowed. A mix of EDO and SDRAM is also reported as working (assuming you -don't try to mix EDO and SDRAM in one module pair). - -Embedded SCSI: -Rawhide has an embedded Symbios 810 Fast SCSI bus. - -Expansion: -Rawhides are available with a 8 64-bit PCI / 3 EISA slot expansion backplanes -(called 'Saddle' modules). There are 2 separate PCI buses, PCI0 and PCI1. -PCI0 has 1 dedicated PCI slot and (shared) 3 PCI/EISA slots. PCI0 also has a -PCI/EISA bridge that drives things like the serial and parallel ports, -keyboard/mouse etc. PCI1 has 4 PCI slots and an Symbios 810 SCSI chip. VGA -console cards must be installed in a slot connected to PCI0. - -The current implementation has problems in handling PCI bridges. There is -currently a limited fix in place which allows for single level, single device -PCI bridges. The fix allows for the Digital supplied Qlogic SCSI card which -sits behind a 21054 PCI bridge chip. - - NOTE: EISA slots are currently unsupported, but the Compaq Qvision - EISA VGA adapter is treated as an ISA device. It therefore - works OK as a console. - -Power: -The system employs an I2C based power controller system. If you want to be -sure all power is removed from the system pull the mains cables from the -system. - -The kernel config file must contain: - options DEC_KN300 - cpu EV5 - -* -* AlphaServer 1200 ("Tincup") and AlphaStation 1200 ("DaVinci") -* - -The AlphaServer 1200 machine is the successor to the AlphaServer 1000A. -It uses the same enclosure the 1000A uses, but the logic is based on the -AlphaServer 4000 design. These are multi-CPU machines, up to 2 CPUs can -be in a single machine. Basic disk storage is housed in a StorageWorks shelves -The AS1200 intended for the NT market are designated DIGITAL Server 5300 -(5/400 CPU) and DIGITAL Server 5305 (5/533 CPU). - -Features: -- 21164A EV56 CPUs at 400 or 533 Mhz -- cache: 4 Mbytes per CPU -- memory bus: 128 bit with ECC - DIMM memory on two memory daughter boards -- embedded floppy controller -- 2 serial ports -- 1 parallel port -- PS/2 style keyboard & mouse port - -Memory: -AS1200 uses 2 memory daughter cards. On each of these cards are 8 DIMM slots. -DIMMs must be installed in pairs. The maximum memory size is 4 Gbytes. -Slots must be filled in order and slot 0 must contain the largest size -DIMM if different sized DIMMs are used. AS1200 employs fixed starting -addresses for DIMMs, each DIMM pair starts at a 512 Mbyte boundary. -This means that if DIMMs smaller than 256 Mbyte are used the system's -physical memory map will contain 'holes'. Supported DIMM sizes are 64 Mbytes -and 256 Mbytes. The DIMMs are 72 bit SDRAM based, as the system employs ECC. - -Embedded SCSI: -AS1200 has an embedded Symbios 810 Fast SCSI bus. - -Expansion: -AS1200 has 5 64-bit PCI slots, one 1 32-bit PCI slot and one EISA slot -(which is physically shared with one of the 64-bit PCI slots). -There are 2 separate PCI buses, PCI0 and PCI1. PCI0 has the 32-bit PCI -slot and the 2 top-most 64-bit PCI slots. PCI0 also has an Intel 82375EB -PCI/EISA bridge that drives things like the serial and parallel ports, -keyboard/mouse etc. PCI1 has 4 64-bit PCI slots and an Symbios 810 SCSI chip. -VGA console cards must be installed in a slot connected to PCI0. - -Power: -The system employs an I2C based power controller system. If you want to be -sure all power is removed from the system pull the mains cables from the -system. Tincup uses dual power supplies in load-sharing mode and not -as a redundancy pair. - -The kernel config file must contain: - options DEC_KN300 - cpu EV5 - -* -* AlphaServer 8200 and 8400 ("TurboLaser") -* -The AlphaServer 8200 and 8400 machines are aimed as enterprise servers. -Expect a tall 19" cabinet (8200) or fat (8400) 19" rack. This is big iron, -not a hobbyist system. These are multi-CPU machines, up to 12 CPUs can be in -a single machine. The TurboLaser System Bus (TLSB) allows 9 nodes on the -AS8400 and 5 nodes on the AS8200. TLSB is 256 bit data, 40 bit address -allowing 2.1 Gbytes/sec. Nodes on the TLSB can be CPUs, memory or I/O. A -maximum of 3 I/O ports are supported on a TLSB. Basic disk storage is housed -in a StorageWorks shelf. - -Features: -- 21164 EV5 CPUs at up to 467 MHz - 21264 EV67 CPUs at up to 625 MHz - one or two CPUs per CPU module -- cache: 4Mbytes per CPU -- memory bus: 256 bit with ECC -- memory: - uses big memory modules that plug into the TLSB, which in turn - hold special SIMM modules. - memory modules come in varying sizes, up to 2 Gbytes a piece. - uses ECC (8 bites per 64 bits of data) - 7 modules max for AS8400, 3 modules max for AS8200 - maximum memory is 14 Gbytes -- expansion: - 3 system 'I/O ports' that allow up to 12 I/O channels - each I/O channel can connect to XMI, Futurebus+ or PCI boxes - -Memory: -FreeBSD supports (and has been tested with) up to 2 Gbytes of memory on -TurboLaser. - -Expansion: -Only PCI expansion is supported on FreeBSD. XMI or Futurebus+ (which -are AS8400 only) are both unsupported. - -The I/O port modules are designated KFTIA or KFTHA. The I/O port modules -supply so called 'hoses' that connect to up to 4 (KFTHA) PCI buses or 1 -PCI bus (KFTIA). KFTIA has embedded dual 10baseT Ethernet, single FDDI, -3 SCSI Fast Wide Differential SCSI buses and a single Fast Wide Single Ended -SCSI bus. The FWSE SCSI is intended for the systems CDROM. - -KFTHA can drive via each of its 4 hoses a DWLPA or DWLPB box. The DWLPx -house a 12 slots 32 bit PCI backplane. Physically the 12 slots are 3 4-slot -buses but to the software it appears as a single 12 slots PCI bus. A fully -expanded AS8x00 can have 3 (I/O ports) times 4 (hoses) times 12 (PCI -slots/DWLPx) = 144 PCI slots. The maximum bandwidth per KFTHA is 500 -Mbytes/second. DWLPA can also house 8 EISA cards, 2 slots are PCI-only, 2 -slots are EISA only. Of the 12 slots 2 are always occupied by an I/O and -connector module. - -For best performance distribute high bandwidth (FibreChannel, Gigabit Ethernet) -over multiple hoses and/or multiple KFTHA/KFTIA. - -Currently PCI expansion cards containing PCI bridges are not usable. Don't -use them at this time. - -Embedded SCSI: -The single ended SCSI bus on the KFTIA will turn up as the fourth (!) -SCSI bus. The 3 differential SCSI buses of the KFTIA precede it. - -Console: -AS8x00 are generally run with serial consoles. Some newer machines might -have a graphical console of some sorts but FreeBSD has only been tested on -a serial console. - -For serial console usage either change /etc/ttys to have: - - console "/usr/libexec/getty std.9600" unknown on secure - -as the console entry, or add - - zs0 "/usr/libexec/getty std.9600" unknown on secure - -and make the zs node: - - mknod /dev/zs0 c 135 0 - -For the AlphaServer 8x00 machines the kernel config file must -contain: - options DEC_KN8AE # Alpha 8200/8400 (Turbolaser) - cpu EV5 - -* -* Alpha Processor Inc. UP1000 -* - -The UP1000 is an ATX mainboard based on the 21264a CPU which itself lives in -a Slot B module. It is normally housed in a ATX [mini]tower enclosure. - -Features: -- 21264a Alpha CPU at 600 or 700 MHz in a Slot B module (includes cooling fans) -- memory bus: 128 bits to the L2 cache, 64 bits from Slot B to the AMD-751 -- on-board Bcache / L2 cache: 2Mb (600Mhz) or 4Mb (700Mhz) cache -- AMD AMD-751 ('Irongate') system controller chip -- Acer Labs M1543C PCI-ISA bridge controller / super-IO chip -- PS/2 mouse & keyboard port -- memory: 168-pin PC100 unbuffered SDRAM DIMMS - 3 DIMM slots - DIMM sizes supported are 64, 128 or 256 Mb in size -- 2x 16550A serial port -- 1x ECP/EPP parallel port -- floppy interface -- 2x embedded Ultra DMA33 IDE interface -- 2x USB port -- expansion: 4 32 bit PCI slots - 2 ISA slots - 1 AGP slot - -Slot B: -Slot B is a box-like enclosure that houses a daughter-board for the CPU and -cache. It has 2 small fans for cooling. Loud ones too.. - -Memory: -The machine needs ECC capable DIMMs, so 72 bit ones. This does not appear to -be documented in the UP1000 docs. The system accesses the serial EEPROM on -the DIMMs via the SM bus. Note that if only a single DIMM is used it must be -installed in slot *2*. This is a bit counter-intuitive. - -Power -The UP1000 needs a 400Watt ATX power supply according to the manufacturer. -This might be a bit overly conservative/pessimistic judging from the power -consumption of the board & cpu. But as always you will have to take your -expansion cards and peripherals into account. The M1543C chip contains power -management functionality & temperature monitoring (via I2C / SM bus). - -Console -Chances are that your UP1000 comes by default with AlphaBios only. The SRM -console firmware is available from the Alpha Processor Inc. website. It is -currently available in a beta version which was successfully used during the -port of FreeBSD to the UP1000. - -EIDE: -The embedded Ultra DMA EIDE ports are bootable by the SRM console. - -SCSI: -UP1000 SRM can boot off an Adaptec 294x adapter. Under high I/O load conditions -machine lockups have been observed using the Adaptec 294x. A Symbios 875 -based card works just fine, using either the ncr or sym driver. The sym driver -is the newest and most actively maintained one. Most likely other cards -based on the Symbios chips that the sym driver supports will work as well. - -USB: -Is disabled by the SRM console and has not (yet) been tested with FreeBSD. - -For the UP1000 the kernel config file must contain: - cpu EV5 - options API_UP1000 # UP1000, UP1100 (Nautilus) - -* -* Alpha Processor Inc. UP1100 -* - -The UP1100 is an ATX mainboard based on the 21264a CPU running at 600 MHz. -It is normally housed in a ATX [mini]tower enclosure. - -Features: -- 21264a Alpha EV6 CPU at 600 or 700 MHz -- memory bus: 100MHz 64-bit (PC-100 SDRAM) - 800 MB/s memory bandwidth -- on-board Bcache / L2 cache: 2Mb -- AMD AMD-751 ('Irongate') system controller chip -- Acer Labs M1535D PCI-ISA bridge controller / super-IO chip -- PS/2 mouse & keyboard port -- memory: 168-pin PC100 unbuffered SDRAM DIMMS - 3 DIMM slots - DIMM sizes supported are 64, 128 or 256 Mb in size -- 2x 16550A serial port -- 1x ECP/EPP parallel port -- floppy interface -- 2x embedded Ultra DMA66 IDE interface -- 2x USB port -- expansion: 3 32 bit PCI slots - 1 AGP2x slot - -Console: -SRM console code comes standard with the UP1100. The SRM lives in 2Mbytes of -flash ROM. - -Memory: -The machine needs ECC capable DIMMs, so 72 bit ones. This does not appear to -be documented in the UP1100 docs. The system accesses the serial EEPROM on -the DIMMs via the SM bus. Note that if only a single DIMM is used it must be -installed in slot *2*. This is a bit counter-intuitive. - -Power -The UP1100 needs a 400Watt ATX power supply according to the manufacturer. -This might be a bit overly conservative/pessimistic judging from the power -consumption of the board & cpu. But as always you will have to take your -expansion cards and peripherals into account. The M1535D chip contains power -management functionality & temperature monitoring (via I2C / SM bus using -a LM75 thermal sensor). - -Network: -The UP1100 has an on-board 21143 10/100Mbit Ethernet interface. - -Sound: -The UP1100 is equipped with a SoundBlaster compatible audio interface. -Whether this works with FreeBSD is as of yet unknown. - -EIDE: -The embedded Ultra DMA EIDE ports are bootable by the SRM console. - -USB: -The UP1100 has 3 USB ports, 2 going external and one connected to the -AGP port. - -For the UP1100 the kernel config file must contain: - cpu EV5 - options API_UP1000 # UP1000, UP1100 (Nautilus) - -* -* Alpha Processor Inc. CS20 -* - -The CS20 is a 19", 1U high rackmount server based on the 21264[ab] CPU. It can -have a maximum of 2 CPUs. - -Features: -- 21264a Alpha CPU at 667 MHz or 21264b 833 MHz (max. 2 CPUs) -- memory bus: 100MHz 256-bit wide -- 21271 Core Logic chipset ("Tsunami") -- Acer Labs M1533 PCI-ISA bridge controller / super-IO chip -- PS/2 mouse & keyboard port -- memory: 168-pin PC100 PLL buffered/registered SDRAM DIMMS - 8 DIMM slots - uses ECC memory - min 256 Mbytes / max 2 Gbytes of memory -- 2x 16550A serial port -- 1x ECP/EPP parallel port -- ALI M1543C Ultra DMA66 IDE interface -- embedded dual Intel 82559 10/100Mbit Ethernet -- embedded Symbios 53C1000 Ultra160 SCSI controller -- expansion: 2 64 bit PCI slots (2/3 length) - -Console: -SRM console code comes standard with the CS20. The SRM lives in 2Mbytes of -flash ROM. - -Memory: -The CS20 needs ECC capable DIMMs. Note that it uses *buffered* DIMMs. - -Monitoring: -The CS20 has an I2C based internal monitoring system for things like -temperature, fans, voltages etc. The I2C also supports 'wake on LAN'. - -Expansion: -Each PCI slot is connected to it's own independent PCI bus on the Tsunami. - -EIDE: -The embedded Ultra DMA EIDE ports are bootable by the SRM console. - -Disks: -The CS20 has an embedded slim-line IDE CD drive. There is a front-accessible -bay for a 1" high 3.5" SCSI hard-disk drive with SCA connector. - -Note that there is no floppy disk drive (or a connector to add one). - -The kernel config file must contain: - options DEC_ST6600 - cpu EV5 - -Contrary to expectation there is no 'cpu EV6' defined for inclusion in the -kernel config file. The 'cpu EV5' is mandatory to keep config(8) happy. - -Supported hardware overview ---------------------------- - -Word of caution: the installed base for FreeBSD/alpha is not nearly as large -as for FreeBSD/Intel. This means that the enormous variation of PCI/ISA -expansion cards out there has much less chance of having been tested on -alpha than on Intel. This is not to imply they are doomed to fail, just that -the chance of running into something never tested before is much greater. -GENERIC contains things that are known to work on Alpha only. - -- Expansion buses: PCI and ISA are fully supported. Turbo Channel is not -in GENERIC and has limited support (see the relevant machine model info). -The MCA bus is not supported. The EISA bus is not supported for use with -EISA expansion cards as the EISA support code is lacking. ISA cards in EISA -slots are reported to work. The Compaq Qvision EISA VGA card is driven in -ISA mode and works OK as a console. - -- Floppy drives: 1.44 Mbyte and 1.2 Mbyte floppy drives are supported. -2.88Mbyte drives sometimes found in Alpha machines are supported up to -1.44Mbyte. - -- ATA / ATAPI (IDE): are supported via the ata driver framework. As most -people run their Alphas with SCSI disks it is not as well tested as SCSI. Be -aware of boot-ability restrictions for IDE disks. See the machine specific -information. - -- SCSI: full support via the CAM layer for Adaptec 2940x (AIC7xxx -chip-based), Qlogic family and Symbios. Be aware of the machine-specific -boot-ability issues for the various adapter types. - -- FibreChannel: the Qlogic QL2x00 FibreChannel host adapters are fully -supported. - -- Ethernet: if you want to boot your Alpha over the Ethernet you will -obviously need an Ethernet card that the SRM console recognizes. This -generally means you need a board with an 21x4x Ethernet chip as that is -what Digital used. These chips are driven by the FreeBSD 'de' (older driver) -or 'dc' (newer driver). Some new SRM versions are known to recognize the -Intel 8255x Ethernet chips as driven by the FreeBSD 'fxp' driver. But beware: -the 'fxp' driver is reported not to work correctly with FreeBSD/alpha (although -it works excellently on FreeBSD/x86). - -- FDDI: DEC DEFPA PCI FDDI network adapters are supported on alpha. - -- graphics console/keyboard/mouse: in general the SRM console emulates -a VGA-compatibility mode on PCI VGA cards. This is, however, not guaranteed -to work by Compaq/DEC for each and every card type out there. When the SRM -thinks the VGA is acceptable FreeBSD will be able to use it. The console driver -works just like on a FreeBSD/intel machine. The TGA video graphics which -is embedded on for example Multia does *not* work with FreeBSD. TGA based -PCI cards are also *not* supported. Please note that VESA modes are not -supported on Alpha, so that leaves you with 80x25 consoles - -- serial ports: the 'PC standard' serial ports found on most Alphas are -supported. For TurboChannel machines the serial ports are also supported. - -- ISDN (i4b): is not supported on FreeBSD/alpha - -Acknowledgments ----------------- - -In compiling this file I used multiple information sources, but -http://www.netbsd.org proved to be an invaluable source of information. -If it wasn't for NetBSD/alpha there probably would not be a FreeBSD/alpha -in the first place. - -People who kindly helped me create this document: - -- Nick Maniscalco <nmanisca@vt.edu> -- Andrew Gallatin <gallatin@cs.duke.edu> -- Christian Weisgerber <naddy@mips.rhein-neckar.de> -- David O'Brien <obrien@NUXI.com> -- Wim Lemmers, ex-Compaq -- Matthew Jacob <mjacob@feral.com> -- Eric Schnoebelen <eric@cirr.com> -- Chuck Robey <chuckr@picnic.mat.net> -- Mike Smith <msmith@FreeBSD.ORG> -- Peter Jeremy <peter.jeremy@alcatel.com.au> -- Dolf de Waal <l.j.de.waal@kader.hobby.nl> -- Wouter Brackman, Compaq -- Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp> -- Peter van Dijk <petervd@vuurwerk.nl> -- Lodewijk van den Berg, Compaq diff --git a/release/texts/alpha/INSTALL.TXT b/release/texts/alpha/INSTALL.TXT deleted file mode 100644 index bf1db32..0000000 --- a/release/texts/alpha/INSTALL.TXT +++ /dev/null @@ -1,448 +0,0 @@ -+===================== Installing FreeBSD ==========================+ -| | -| Table of Contents: | -| | -| 0.0 Quick Start: | -| 0.1 Installing FreeBSD from CDROM or the Internet. | -| | -| 1.0 Detail on various installation types: | -| 1.1 Installing from a network CDROM | -| 1.2 Installing from Floppies | -| 1.3 Installing from QIC/SCSI tape | -| 1.4 Installing over a network using NFS or FTP | -| 1.4.1 NFS Installation tips | -| 1.4.2 FTP Installation tips | -| | -+=====================================================================+ - -Author: Jordan K. Hubbard -Last updated: Fri Mar 16 14:47:31 PST 2001 - -0.0 Quick Start ---- ----------- - -This manual documents the process of making a new installation of -FreeBSD on your machine. If you are upgrading from a previous -release of FreeBSD, please see the file UPGRADE.TXT for important -information on upgrading. If you are not familiar with configuring -hardware for FreeBSD, you should also read the HARDWARE.TXT file - -it contains important information which may save you a lot of grief. - -If you're new to FreeBSD then you should also read EVERYTHING listed -in the Documentation menu on the boot floppy. It may seem like a lot -to read, but the time you spend now reading the documents will be made -up many times over because you were adequately prepared. Also, you will -know the types of information available should you get stuck later. -Once the system is installed, you can also revisit this menu and use a -WEB browser to read the installed FAQ (Frequently Asked Questions) and -Handbook HTML documentation sets for FreeBSD. You can also use the -browser to visit other WEB sites on the net (like http://www.freebsd.org) -if you have an Internet connection. See ABOUT.TXT for more information -on the resources available to you. - -The best laid plans sometimes go awry, so if you run into trouble take a -look at TROUBLE.TXT which contains valuable troubleshooting information. - -DISCLAIMER: While FreeBSD does its best to safeguard against -accidental loss of data, it's still more than possible to WIPE OUT -YOUR ENTIRE DISK with this installation! Please do not proceed to the -final FreeBSD installation menu unless you've adequately backed up any -important data first! We really mean it! - -FreeBSD/alpha supports the alpha platforms described in HARDWARE.TXT - -You will need a dedicated disk for FreeBSD/alpha. It is not possible -to share a disk with another operating system at this time. This disk -will need to be attached to a SCSI controller which is supported by -the SRM firmware or an IDE disk assuming the SRM in your machine -supports booting from IDE disks. - -Your root filesystem MUST be the first partition (partition a) on the -disk to be bootable. - -You will need the SRM console firmware for your platform. In some -cases, it is possible to switch between AlphaBIOS (or ARC) firmware -and SRM. In others it will be necessary to download new firmware from -the vendor's Website. - -0.1 Installing FreeBSD from CDROM or the Internet ---- --------------------------------------------- - -The easiest type of installation is from CD. If you have a supported -CDROM drive and a FreeBSD installation CD from Walnut Creek CDROM, you -can boot FreeBSD directly from the CDROM. Insert the CDROM into the -drive and type the following command to start the installation: - - >>>boot dka0 (or whatever device your CDROM drive is) - -Alternatively you can boot the installation from floppy disk. You -should start the installation by building a set of FreeBSD boot floppy -from the files floppies/kern.flp and floppies/mfsroot.flp using the -instructions found in floppies/README.TXT. From the SRM console prompt -(>>>), just insert the kern.flp floppy and type the following command -to start the installation: - - >>>boot dva0 - -Insert the mfsroot.flp floppy when prompted and you will end up at the -first screen of the install program. - -If you don't have a CDROM and would like to simply install over the -net using PPP, slip or a dedicated connection, simply fetch the -<FreeBSD-release>/floppies/kern.flp and mfsroot.flp files from: - - ftp://ftp.freebsd.org/pub/FreeBSD - -or one of its many mirrors (http://www.freebsd.org/handbook/mirrors.html) -and follow step 3 above. You should also read the floppies/README.TXT -file as it contains important information for downloaders. - -Once you have a boot floppy made, please go to section 1.4 of this -document for additional tips on installing via FTP or NFS. - - -1.0 Detail on various installation types ---- ------------------------------------ - -Once you've gotten yourself to the initial installation screen -somehow, you should be able to follow the various menu prompts and go -from there. If you've never used the FreeBSD installation before, you -are also encouraged to read some of the documentation in the the -Documentation submenu as well as the general "Usage" instructions on -the first menu. - - REMEMBER: If you get stuck at a screen, hit F1 for the online - documentation for that section. - -If you've never installed FreeBSD before, or even if you have, the -"Standard" installation mode is the most recommended since it makes sure -that you'll visit all the various important checklist items along the -way. If you're much more comfortable with the FreeBSD installation -process and know _exactly_ what you want to do, use the Express or -Custom installation options. If you're upgrading an existing system, -use the Upgrade option. - -The FreeBSD installer supports the direct use of floppy, DOS, tape, -CDROM, FTP, NFS and UFS partitions as installation media, further tips -on installing from each type of media listed below. - -Once the install procedure has finished, you will be able to start -FreeBSD/alpha by typing something like this to the SRM prompt: - - >>>boot dkc0 - -This instructs the firmware to boot the specified disk. To find the -SRM names of disks in your machine, use the show device command: - - >>>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 - - -This example is from a Digital Personal Workstation 433au and shows -three disks attached to the machine. The first is a CDROM called dka0 -and the other two are disks and are called dkc0 and dkc100 -repectively. - -You can specify which kernel file to load and what boot options to use -with the -file and -flags options to boot, e.g.: - - >>>boot -file kernel.old -flags s - -To make FreeBSD/alpha boot automatically, use these commands: - - >>>set boot_osflags a - >>>set bootdef_dev dkc0 - >>>set auto_action BOOT - - -1.1 Installing from a network CDROM ---- ------------------------------- - -If you simply wish to install from a local CDROM drive then see the -Quick Start section. If you don't have a CDROM drive on your system -and wish to use a FreeBSD distribution CD in the CDROM drive of -another system to which you have network connectivity, there are -several ways of going about it: - -1. If you would be able to FTP install FreeBSD directly from the CDROM - drive in some FreeBSD machine, it's quite easy: You simply add the - following line to the password file (using the vipw command): - - ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin - - Warning: This may allow anyone on the local network (or Internet) to - make "anonymous FTP" connections to this machine, which may not be - desirable. - - On the machine on which you are running the install, go to the "Options" - menu and set "Release Name" to "any". You may then choose a Media - type of FTP and type in: ``ftp://<machine with CDROM drive>'' after - picking "URL" in the ftp sites menu. - -2. If you would rather use NFS to export the CDROM directly to the - machine(s) you'll be installing from, you need to first add an - entry to the /etc/exports file (on the machine with the CDROM drive) - which looks something like this: - - /cdrom -ro ziggy.foo.com - - To allow the machine "ziggy.foo.com" to mount the CDROM directly - via NFS during installation. The machine with the CDROM must also - be configured as an NFS server, of course, and if you're not sure how - to do that then an NFS installation is probably not the best choice - for you unless you're willing to read up on rc.conf(5) and configure - things appropriately. Assuming that this part goes smoothly, you - should be able to enter: <cdrom-host>:/cdrom as the path for an NFS - installation when the target machine is installed. - - -1.2 Installing from Floppies ---- ------------------------ - -If you must install from floppy disks, either due to unsupported -hardware or just because you enjoy doing things the hard way, you must -first prepare some floppies for the install. - -First, make a set of boot floppies as described in floppies/README.TXT. - -Second, read the file LAYOUT.TXT and pay special attention to the -"Distribution format" section since it describes which files you're -going to need to put onto floppy and which you can safely skip. - -Next you will need, at minimum, as many 1.44MB floppies as it takes to -hold all files in the bin (binary distribution) directory. If you're -preparing these floppies under DOS, then THESE floppies *must* be -formatted using the MS-DOS FORMAT command. If you're using Windows, -use the Windows File Manager format command. - -Don't 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'm taking such special care to mention it here! - -If you're creating the floppies from another FreeBSD machine, a format -is still not a bad idea though you don't need to put a DOS filesystem -on each floppy. You can use the `disklabel' and `newfs' commands to -put a UFS filesystem on a floppy, as the following sequence of -commands illustrates: - - fdformat -f 1440 fd0.1440 - disklabel -w -r fd0.1440 floppy3 - newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0 - -After you've formatted the floppies for DOS or UFS, you'll 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've got all the distributions you want -packed up in this fashion. Each distribution should go into its own -subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, -a:\bin\bin.ab, ... - -IMPORTANT NOTE: The bin.inf file also needs to go on the first floppy -of the bin 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. When putting distributions onto -floppies, the <distname>.inf file MUST occupy the first floppy of each -distribution set! - -Once you come to the Media screen of the install, select "Floppy" and -you'll be prompted for the rest. - - -1.3 Installing from QIC/SCSI Tape ---- ----------------------------- - -When installing from tape, the installation program expects the files -to be simply tar'ed onto it, so after fetching all of the files for -the distributions you're interested in, simply tar them onto the tape -with a command something like this: - - cd /where/you/have/your/dists - tar cvf /dev/rwt0 (or /dev/rsa0) 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'll be allowed -to choose) to accommodate the FULL contents of the tape you've -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. - -SPECIAL 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. - -Now create a boot floppy as described in section 0.1 and proceed with -the installation. - - -1.4 Installing over a network using FTP or NFS ---- ------------------------------------------ - -After making a boot floppy as described in the first section, you can -load the rest of the installation over a network using one of 3 types -of connections: - - Serial port: SLIP / PPP - Parallel port: PLIP (using ``laplink'' style cable) - Ethernet: A standard Ethernet controller (including - certain PCCARD devices). - -Serial Port ------------ - -SLIP support is rather primitive, and is limited primarily to -hard-wired links, such as a serial cable running between two -computers. The link must be hard-wired because the SLIP installation -doesn't currently offer a dialing capability. If you need to dial out -with a modem or otherwise dialog with the link before connecting to -it, then I recommend that the PPP utility be used instead. - -If you're using PPP, make sure that you have your Internet Service -Provider's IP address and DNS information handy as you'll need to know -it fairly early in the installation process. You may also need to -know your own IP address, though PPP supports dynamic address -negotiation and may be able to pick up this information directly from -your ISP if they support it. - -You will also need to know how to use the various "AT commands" for -dialing out with your particular brand of modem as the PPP dialer -provides only a very simple terminal emulator. - - -Parallel Port -------------- - -If a hard-wired connection to another FreeBSD or Linux machine is -available, you might also consider installing over a "laplink" -style parallel port cable. The data rate over the parallel port -is much higher than what is typically possible over a serial line -(up to 50k/sec), thus resulting in a quicker installation. It's not -typically necessary to use "real" IP addresses when using a -point-to-point parallel cable in this way and you can generally just -use RFC 1918 style addresses for the ends of the link (e.g. 10.0.0.1, -10.0.0.2, etc). - -IMPORTANT NOTE: If you use a Linux machine rather than a FreeBSD -machine as your PLIP peer, you will also have to specify "link0" in -the TCP/IP setup screen's ``extra options for ifconfig'' field. - - -Ethernet --------- - -FreeBSD supports most common Ethernet cards, a table of supported -cards (and their required settings) being provided as part of the -FreeBSD Hardware Guide (see the Documentation menu on the boot floppy -or the top level directory of the CDROM). - -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 are appropriate to -your particular network setup. If you will be referring to other -hosts by name rather than IP address, you'll also need a name server -and possibly the address of a gateway (if you're using PPP, it's your -provider's IP address) to use in talking to it. - -If you do not know the answers to these questions then you should -really probably talk to your system administrator _first_ before -trying this type of installation! Using a randomly chosen IP address -or netmask on a live network will almost certainly get you shot at -dawn. - -Once you have a network connection of some sort working, the -installation can continue over NFS or FTP. - - -1.4.1 NFS installation tips ------ --------------------- - - 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 and Linux 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 also support - "subdir mounts", e.g. if your FreeBSD 2.2 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's likely that you don't have this - properly enabled! - - -1.4.2 FTP Installation tips ------ --------------------- - - FTP installation may be done from any mirror site containing a - reasonably up-to-date version of FreeBSD. A full menu of - reasonable choices for almost any location in the world is - provided in the FTP site menu during installation. - - 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 ``URL'' choice in that menu. A URL can - contain a hostname or an IP address, so the following would - work in the absence of a name server: - - ftp://192.216.191.11/pub/FreeBSD - - There are three FTP installation modes you can use: - - o FTP: - - This method uses the standard "Active" mode for file - transfers which allows the server to initiate a connection - to the client. This will not work through most firewalls - but will often work best with older FTP servers that do - not support passive mode. If your connection hangs with - passive mode, try this one! - - o FTP Passive: - - This sets the FTP "Passive" mode which prevents the - server from opening connections to the client. This - option is best for users to pass through firewalls that - do not allow incoming connections on random port - addresses. - - o FTP via an HTTP proxy: - - This option instructs FreeBSD to use HTTP to connect to a - proxy for all FTP operations. The proxy will translate - the requests and send them to the FTP server. This - allows the user to pass through firewalls that do not - allow FTP at all, but offer an HTTP proxy. You must - specify the hostname of the proxy in addition to the FTP - server. - - In the rare case that you have an FTP proxy that does not go - through HTTP, you can specify the URL as something like : - - ftp://foo.bar.com:1234/pub/FreeBSD - - Where "1234" is the port number of the proxy ftp server. - - ----- End of Installation Guide --- diff --git a/release/texts/alpha/RELNOTES.TXT b/release/texts/alpha/RELNOTES.TXT deleted file mode 100644 index 0409864..0000000 --- a/release/texts/alpha/RELNOTES.TXT +++ /dev/null @@ -1,1713 +0,0 @@ - RELEASE NOTES - FreeBSD Release 5.0-SNAP - (alpha Architecture) - -This is a 5.0-CURRENT release SNAPshot of FreeBSD, an active -development branch which will produce its first release in late -2001. Those features which have also been back-ported to -the 4.x-stable branch (the next release for which will be 4.3) -are marked [MERGED]. - -Any installation failures or crashes should be reported by using the -send-pr command (those preferring a Web-based interface can also see -http://www.FreeBSD.org/send-pr.html). - -For information about FreeBSD and the layout of the 5.0-RELEASE -directory (especially if you're installing from floppies!), see -ABOUT.TXT. For installation instructions, see the INSTALL.TXT and -HARDWARE.TXT files. - -For the latest of these 5.0-current snapshots, you should always see: - - ftp://current.FreeBSD.org/pub/FreeBSD - -If you wish to get the latest post-4.x-RELEASE technology. - -Table of contents: ------------------- -1. What's new since the 4.0/5.0 branch - 1.1 KERNEL CHANGES - 1.2 SECURITY FIXES - 1.3 USERLAND CHANGES - -2. Supported Configurations - 2.1 Disk Controllers - 2.2 Ethernet cards - 2.3 FDDI - 2.4 ATM - 2.5 Misc - -3. Obtaining FreeBSD - 3.1 FTP/Mail - 3.2 CDROM - -4. Upgrading from previous releases of FreeBSD - -5. Reporting problems, making suggestions, submitting code - -6. Acknowledgments - - -1. What's new since the 4.0/5.0 branch --------------------------------------- -All changes described here are unique to the 5.0 branch unless -specifically marked as [MERGED] features. - - -1.1. KERNEL CHANGES -------------------- - -A new event notification facility called kqueue was added to the -FreeBSD kernel. This is a new interface which is able to replace -poll/select, offering improved performance, as well as the ability -to report many different types of events. Support for monitoring -changes in sockets, pipes, fifos, and files are present, as well as -for signals and processes. [MERGED] - -Support for named extended attributes was added to the FreeBSD kernel. -This allows the kernel, and appropriately privileged userland -processes, to tag files and directories with attribute data. Extended -attributes were added to support the TrustedBSD Project, in particular -ACLs, capability data, and mandatory access control labels (see -/usr/src/sys/ufs/ufs/README.extattr for details). - -POSIX.1b Shared Memory Objects are now supported. The implementation -uses regular files, but automatically enables the MAP_NOSYNC flag -when they are mmap(2)ed. [MERGED] - -Added support for PCI Ethernet adapters based on the National Semiconductor -DP83815 chipset, including the NetGear FA312-TX. - -Due to a licensing change, softupdates have been integrated into the -main portion of the kernel source tree. As a consequence, softupdates -are now available with the GENERIC kernel. [MERGED] - -When running with softupdates, statfs(2) and df(1) will track the -number of blocks and files that are committed to being freed. - -ipfilter has been updated to 3.4.16. [MERGED] - -The tap driver, a virtual Ethernet device driver for bridged -configurations, has been added. [MERGED] - -accept_filters, a kernel feature to reduce overheads when accepting -and reading new connections on listening sockets, has been added. -[MERGED] - -The ata(4) driver now has support for ATA100 controllers. In -addition, it now supports the ServerWorks ROSB4 ATA33 chipset, the CMD -648 ATA66 and CMD 649 ATA100 chipsets, and the Cyrix 5530. [MERGED] - -To provide more flexible configuration, the various options for the -ata(4) driver are now boot loader tunables, rather than kernel -configure-time options. [MERGED] - -The ata(4) driver now has support for tagged queuing, which is -enabled by the hw.ata.tags loader tunable. [MERGED] - -The ata(4) driver now has support for ATA "pseudo" RAID controllers as -the Promise Fasttrak and HighPoint HPT370 controllers. [MERGED] - -AlphaServer 1200 ("Tincup") has been tested and works OK. Currently it does -not want to boot from CD or floppy but a transplanted disk that was -installed on another Alpha works well. [MERGED] - -The ti(4) driver now supports the Alteon AceNIC 1000baseT Gigabit -Ethernet and Netgear GA620T 1000baseT Gigabit cards. [MERGED] - -SMP support has been largely reworked, incorporating code from BSD/OS -5.0. One of the main features of SMPng ("SMP Next Generation") is to -allow more processes to run in kernel, without the need for spin locks -that can dramatically reduce the efficiency of multiple processors. -Interrupt handlers now have contexts associated with them that allow -them to be blocked, which reduces the need to lock out interrupts. - -SMP support for the Alpha is now operational. - -The kernel and modules have been moved to the directory /boot/kernel, -so they can be easily manipulated together. The boot loader has been -updated to make this change as seamless as possible. - -A filesystem snapshot capability has been added to FFS. Details can -be found in /usr/src/sys/ufs/ffs/README.snapshot. - -Softupdates for FFS have received some bug fixes and enhancements. - -A bug in FFS that could cause superblock corruption on very large -filesystems has been corrected. [MERGED] - -The ng_mppc(4) and ng_bridge(4) node types have been added to the -netgraph subsystem. The ng_ether(4) node is now dynamically loadable. -Miscellaneous bug fixes and enhancements have also been made. [MERGED] - -The pcn(4) driver, which supports the AMD PCnet/FAST, PCnet/FAST+, -PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA adapters, has been added. -Although these cards are already supported by the lnc(4) driver, the pcn -driver runs these chips in 32-bit mode and uses the RX alignment feature to -achieve zero-copy receive. This driver is also machine-independent, -so it will work on both the i386 and alpha platforms. The lnc driver -is still needed to support non-PCI cards. [MERGED] - -The ed(4) driver is now also supported on the Alpha. - -A bug in the ed(4) driver that could cause panics with very short -packets and BPF or bridging active has been fixed. - -The pcm(4) driver now supports the ESS Solo 1, Maestro-1, Maestro-2, -and Maestro-2e; Forte Media fm801, ESS Maestro-2e, and VIA -Technologies VT82C686A sound card/chipsets, and has received some -other updates. Separate drivers for the SoundBlaster 8 and -Soundblaster 16 now replace an older, unified driver. A driver for -the CMedia CMI8338/CMI8738 sound chips has been added. A driver for -the CS4281 sound chip has been added. [MERGED] - -A driver for the ESS Maestro-3/Allegro has been added, however due to -licensing restrictions, it cannot be compiled into the kernel. -[MERGED] To use this driver, add the following line to -/boot/loader.conf: - - snd_maestro3_load="YES" - -Replace the PQ_*CACHE options with a single PQ_CACHESIZE option to be -set to the cache size in kilobytes. The old options are still -supported for backwards compatibility. [MERGED] - -The ahc(4) driver has been updated. Among various improvements are -improved compatibility with chips in "RAID Port" mode and systems with -AAA and ARO cards installed, as well as performance improvements. -Some bugs were also fixed, including a rare hang on Ultra2/U160 -controllers. [MERGED] - -ACPI support has been merged in from the FreeBSD-ACPI project. - -devfs(5), which allows entries in the /dev directory to be built -automatically and supports more flexible attachment of devices, has -been largely reworked. devfs(5) is now enabled by default, and is -disabled by the NODEVFS kernel option. - -Write combining for crashdumps has been implemented. This feature -is useful when write caching is disabled on both SCSI and IDE disks, -where large memory dumps could take up to an hour to complete. [MERGED] - -The bktr(4) driver has been updated to 2.15. New tuner types have -been added, and improvements to the KLD module and to memory -allocation have been made. [MERGED] - -The bktr(4) driver has been updated to 2.17. This fixes bugs in devfs -when unloading and reloading, and syncs with some NetBSD -changes. [MERGED] - -The bktr(4) driver has been updated to 2.18. This adds support for -new Hauppauge Model 44xxx WinTV Cards (the ones with no audio mux). - -Extremely large swap areas (>67 GB) no longer panic the system. - -The Inode Filesystem (IFS) has been added; more information can be -found in /usr/src/sys/ufs/ifs/README. - -The cd(4) driver now has support for write operations. This allows -writing to DVD-RAM, PD and similar drives that probe as CD devices. -Note that change affects only random-access writeable devices, not -sequential-only writeable devices such as CD-R drives, which are -supported by cdrecord. [MERGED] - -The ISO-9660 filesystem now has a hook that supports a loadable -character conversion routine. The sysutils/cd9660_unicode port -contains a set of common conversions. [MERGED] - -Support for threads under Linux emulation has been added. - -The an(4) driver for Cisco Aironet cards now supports Wired Equivalent -Privacy (WEP) encryption, settable via ancontrol(8). [MERGED] - -A new netgraph node type ng_one2many(4) for multiplexing and -demultiplexing packets over multiple links has been added. [MERGED] - -The DEC3000-series support has been removed from the mfsroot floppy image -so that it fits on a 1.44Mbyte floppy again. As DEC3000 is currently -only usable diskless this should not cause any problems. - -For the same reason SLIP has been removed from the mfsroot image as well. - -Support for AlphaServer 2100A ('Lynx') has been added. - -netgraph(4) has received some updates. - -sbufs, null-terminated string data structures, and their associated -support routines, have been added to the kernel. Details are in -sbuf(9). - -The vinum(4) volume manager has received some bug fixes and enhancements. - -ICMP ECHO and TSTAMP replies are now rate limited. TCP RSTs generated -due to packets sent to open and unopen ports are now limited by -separate counters. Each rate limiting queue now has its own -description. - -ICMP UNREACH_FILTER_PROHIB messages can now RST TCP connections in the -SYN_SENT state if the correct sequence numbers are sent back, as -controlled by the net.inet.tcp.icmp_may_rst sysctl. [MERGED] - -TCP has received some bug fixes for its delayed ACK behavior. [MERGED] - -TCP now supports the NewReno modification to the TCP Fast Recovery -algorithm. This behavior can be controlled via the -net.inet.tcp.newreno sysctl variable. [MERGED] - -TCP now uses a more aggressive timeout for initial SYN segments; this -allows initial connection attempts to be dropped much faster. [MERGED] - -The TCP_COMPAT_42 kernel option has been removed. - -A new sysctl net.inet.ip.check_interface, which is on by default, -causes IP to verify that an incoming packet arrives on an interface -that has an address matching the packet's destination address. [MERGED] - -PECOFF (WIN32 Execution file format) support has been added. - -kernfs(5) is obsolete and has been retired. - -md(4), the memory disk device, has had the functionality of vn(4) -incorporated into it. md(4) devices can now be configured by -mdconfig(8). vn(4) has been removed. - -The ray(4) driver, which supports the Webgear Aviator wireless network -cards, has been committed. The operation of ray(4) interfaces can be -modified by raycontrol(8). [MERGED] - -FDDI networking using Digital Equipment DEFPA PCI FDDI adapters is now -supported. - -A new API has been added for sound cards with hardware volume -control. - -A new sysctl 'net.link.ether.inet.log_arp_wrong_iface' to controls the -suppression of logging when ARP replies arrive on the wrong -interface. [MERGED] - -A bug in the NFS client that caused bogus access times with -O_EXCL|O_CREAT opens was fixed. [MERGED] - -Client-side NFS locks have been implemented. - -The bug that made certain CDROM drives fail to attach when connected -to a SCSI card driven by 'isp' has been fixed. [MERGED] - -Condition variables have now been implemented in the FreeBSD kernel. -See condvar(9) for more details. - -The "make buildkernel" target now gets the name of the -configuration(s) to build from the KERNCONF variable, not KERNEL. It -is no longer required, in some cases, for a "buildworld" to precede a -"buildkernel". (The buildworld is still required when upgrading across -major releases, across binutil upgrades and when config changes -version.) - -The API UP1100 mainboard has been verified to work OK. - -bridge(4) and dummynet(4) have received some enhancements and bug fixes. - -The API CS20 1U high server has been verified to work OK. - -ipfw(8) has a new feature ("me") that allows for packet matching on -interfaces with dynamically-changing IP addresses. [MERGED] - -The isp(4) driver has been updated. [MERGED] - -The isp(4) driver now supports target mode for Qlogic SCSI cards, -including Ultra2 and Ultra3 and dual bus cards. - -The ida disk driver now has crashdump support. [MERGED] - -The random(4) device has been rewritten to use the Yarrow algorithm. -It harvests entropy from a variety of interrupt sources, including the -console devices, Ethernet and point-to-point network interfaces, and -mass-storage devices. Entropy from the random(4) device is now -periodically saved to files in /var/db/entropy. - -Kernel code has been added that allows older generation Alpha CPUs -(EV4 and EV5) to emulate instructions of the newer Alpha CPU -generations. This enables the use of binary-only programs like Adobe -Acrobat 4 on EV4 and EV5. - -The fxp(4) driver now requires a "device miibus" entry in the kernel -configuration file. [MERGED] - -A new NFS hash function (based on the Fowler/Noll/Vo hash algorithm) -has been implemented to improve NFS performance by increasing the -efficiency of the nfsnode hash tables. [MERGED] - -The syscons(4) driver now supports keyboard-controlled pasting, by -default bound to Shift-Insert. - -Support for file system Access Control Lists (ACLs) has been -introduced, allowing more fine-grained control of discretionary access -control on files and directories. This support was integrated from -the TrustedBSD Project. More details can be found in -/usr/src/sys/ufs/ufs/README.acls. - -The CAM error recovery code has been updated. - -The directory layout preference algorithm for FFS has been changed to -improve its speed on large filesystems. - -The wx(4) driver now supports the Intel PRO1000-F and PRO1000-T -(10/100/1000) adapters. [MERGED] - -The labpc(4) driver has been removed due to bitrot. - -Added support for PCI Gigabit Ethernet adapters based on the National -Semiconductor DP83820 and DP83821 gigabit ethernet controller chips, -including the D-Link DGE-500T, SMC EZ Card 1000 (SMC9462TX), -Asante FriendlyNet GigaNIC 1000TA and 1000TPC and Addtron AEG320T. - -The USER_LDT kernel option is now activated by default. - -A new digi(4) driver has been added to support PCI Xr-based and ISA -Xem Digiboard cards. A new digictl program is (mainly) used to -re-initialise cards that have external port modules attached such as -the PC/Xem. - - -1.2. SECURITY FIXES -------------------- - -sysinstall(8) now allows the user to select one of three "security -profiles" at install-time. These profiles enable different levels of -system security by enabling or disabling various system services in -rc.conf(5) on new installs. [MERGED] - -A bug in which malformed ELF executable images can hang the system has -been fixed (see security advisory FreeBSD-SA-00:41). [MERGED] - -A security hole in Linux emulation was fixed (see security advisory -FreeBSD-SA-00:42). [MERGED] - -rlogind(8), rshd(8), and fingerd(8) are now disabled by default in -/etc/inetd.conf. This only affects new installations. [MERGED] - -String-handling library calls in many programs were fixed to reduce -the possibility of buffer overflow-related exploits. [MERGED] - -TCP now uses stronger randomness in choosing its initial sequence -numbers (see security advisory FreeBSD-SA-00:52). [MERGED] - -Several buffer overflows in tcpdump(1) were corrected (see security -advisory FreeBSD-SA-00:61). [MERGED] - -A security hole in top(1) was corrected (see security advisory -FreeBSD-SA-00:62). [MERGED] - -A potential security hole caused by an off-by-one-error in -gethostbyname(3) has been fixed (see security advisory -FreeBSD-SA-00:63). [MERGED] - -A potential buffer overflow in the ncurses(3X) library, which could -cause arbitrary code to be run from within systat(1), has been corrected -(see security advisory FreeBSD-SA-00:68). [MERGED] - -A vulnerability in telnetd(8) that could cause it to consume large -amounts of server resources has been fixed (see security advisory -FreeBSD-SA-00:69). [MERGED] - -The "nat deny_incoming" command in ppp(8) now works correctly (see -security advisory FreeBSD-SA-00:70). [MERGED] - -A vulnerability in csh(1)/tcsh(1) temporary files that could allow -overwriting of arbitrary user-writable files has been closed (see -security advisory FreeBSD-SA-00:76). [MERGED] - -The ssh(1) binary is no longer SUID root by default. - -Some fixes were applied to the Kerberos IV implementation related to -environment variables, a possible buffer overrun, and overwriting -ticket files. [MERGED] - -telnet(1) now does a better job of sanitizing its environment. [MERGED] - -Several vulnerabilities in procfs(4) were fixed (see security advisory -FreeBSD-SA-00:77). [MERGED] - -A bug in OpenSSH in which a server was unable to disable ssh-agent or -X11 forwarding was fixed (see security advisory FreeBSD-SA-01:01). -[MERGED] - -A bug in ipfw(8) and ipfw6(8) in which inbound TCP segments could -incorrectly be treated as being part of an "established" connection -has been fixed (see security advisory FreeBSD-SA-01:08). [MERGED] - -A bug in crontab(8) that could allow users to read any file on the -system in valid crontab(5) syntax has been fixed (see security -advisory FreeBSD-SA-01:09). [MERGED] - -A vulnerability in inetd(8) that could allow read-access to the -initial 16 bytes of wheel-accessible files has been fixed (see -security advisory FreeBSD-SA-01:11). [MERGED] - -A bug in periodic(8) that used insecure temporary files has been -corrected (see security advisory FreeBSD-SA-01:12). [MERGED] - -A bug in sort(1) in which an attacker might be able to cause it to -abort processing has been fixed (see security advisory -FreeBSD-SA-01:13). [MERGED] - -To fix a remotely-exploitable buffer overflow, BIND has been updated -to 8.2.3 (see security advisory FreeBSD-SA-01:18). [MERGED] - -OpenSSH now has code to prevent (instead of just mitigating through -connection limits) an attack that can lead to guessing the server key -(not host key) by regenerating the server key when an RSA failure is -detected (see security advisory FreeBSD-SA-01:24). [MERGED] - -A number of programs have had output formatting strings corrected so -as to reduce the risk of vulnerabilities. [MERGED] - -A number of programs that use temporary files now do so more -securely. [MERGED] - -A bug in ICMP that could cause an attacker to disrupt TCP and UDP -"sessions" has been corrected. [MERGED] - -A bug in timed(8), which caused it to crash if sent certain malformed -packets, has been corrected (see security advisory -FreeBSD-SA-01:28). [MERGED] - -A bug in rwhod(8), which caused it to crash if sent certain malformed -packets, has been corrected (see security advisory -FreeBSD-SA-01:29). [MERGED] - -A security hole in FreeBSD's FFS and EXT2FS implementations, which -allowed a race condition that could cause users to have unauthorized -access to data, has been fixed (see security advisory -FreeBSD-SA-01:30). [MERGED] - -A remotely-exploitable vulnerability in ntpd(8) has been closed (see -security advisory FreeBSD-SA-01:31). [MERGED] - -A security hole in IPFilter's fragment cache has been closed (see -security advisory FreeBSD-SA-01:32). [MERGED] - -Buffer overflows in glob(3), which could cause arbitrary code to be -run on an FTP server, have been closed. In addition, to prevent some -forms of DOS attacks, glob(3) now allows specification of a limit on -the number of pathname matches it will return. ftpd(8) now uses this -feature (see security advisory FreeBSD-SA-01:33). [MERGED] - -Initial sequence numbers in TCP are more thoroughly randomized, using -an algorithm obtained from OpenBSD (see security advisory -FreeBSD-SA-01:39). [MERGED] - - -1.3. USERLAND CHANGES ---------------------- - -cdcontrol(1) now supports a "cdid" command, which calculates and -displays the CD serial number, using the same algorithm used by the CDDB -database. [MERGED] - -mtree(8) now includes support for a file listing pathnames to be excluded -when creating and verifying prototypes. This makes it easier to use -mtree as a part of an intrusion-detection system. [MERGED] - -OpenSSL has been upgraded to 0.9.6. [MERGED] - -OpenSSL now has support for machine-dependent ASM optimizations, -activated by the new MACHINE_CPU Makefile variable. [MERGED] - -The OPIE one-time-password suite has been updated to 2.32. [MERGED] - -OpenSSH has been upgraded to 2.1.0, which provides support for the -SSH2 protocol, including DSA keys. Therefore, OpenSSH users in the US -no longer need to rely on the restrictively-licensed RSAREF toolkit -which is required to handle RSA keys. OpenSSH 2.1 interoperates well -with other SSH2 clients and servers, including the ssh2 port. See -http://www.openssh.com for more details. [MERGED] - -OpenSSH can now authenticate using OPIE passwords in SSH1 mode. -Support is not yet available in SSH2 mode. [MERGED] - -OpenSSH has been upgraded to 2.2.0. ssh-add(1) and ssh-agent(1) can now -handle DSA keys. An sftp server interoperable with ssh.com clients -and others has been added. scp(1) can now handle files >2GB. -Interoperability with other ssh2 clients/servers has been improved. A -new feature to limit the number of outstanding unauthenticated ssh -connections in sshd has been added. [MERGED] - -OpenSSH has been upgraded to 2.3.0. This version adds support for the -Rijndael encryption algorithm. [MERGED] - -PAM support for OpenSSH has been added. - -A long-standing bug in SSH, which sometimes resulted in a dropped -session when an X11-forwarded client was closed, was fixed. - -Kerberos compatability has been added to OpenSSH. [MERGED] - -OpenSSH has been modified to be more resistant to traffic analysis by -requiring that "non-echoed" characters are still echoed back in a null -packet, as well as by padding passwords sent so as not to hint at -password lengths. [MERGED] - -OpenSSH now has a "VersionAddendum" configuration setting for sshd(8) -to allow changing the part of the OpenSSH version string after the -main version number. - -OpenSSH has been updated to version 2.9, which adds two new programs, -sftp(1) and ssh-keyscan(1). Among the various enhancements: The -default protocol is now v2, rekeying of existing SSH sessions is now -supported, and an experimental SOCKS4 proxy has been added to the -ssh(1) client. - -Support for USB devices was added to the GENERIC kernel and to the -installation programs to support USB devices out of the box. Note that -SRM does not support USB devices at the moment, so you must still use -an AT keyboard if you are not using a serial console. [MERGED] - -The csh(1) shell has been replaced by tcsh(1), although it can still -be run as csh(1). tcsh has been updated to version 6.10. [MERGED] - -The more(1) command has been replaced by less(1), although it can still -be run as more(1). [MERGED] - -ls(1) can produce colorized listings with the -G flag (and appropriate -terminal support). [MERGED] - -sendmail upgraded from version 8.9.3 to version 8.11.3. Important changes -include: new default file locations (see -/usr/src/contrib/sendmail/cf/README); newaliases is limited to root and -trusted users; STARTTLS encryption; and the MSA port (587) is turned on by -default. See /usr/src/contrib/sendmail/RELEASE_NOTES for more -information. [MERGED] - -mail.local(8) is no longer installed as a set-user-id binary. If you are -using a /etc/mail/sendmail.cf from the default sendmail.cf included with -FreeBSD any time after 3.1.0, you are fine. If you are using a -hand-configured sendmail.cf and mail.local for delivery, check to make sure -the F=S flag is set on the Mlocal line. Those with .mc files who need to -add the flag can do so by adding the following line to their your .mc file -and regenerating the sendmail.cf file: - MODIFY_MAILER_FLAGS(`LOCAL', `+S')dnl -Note that FEATURE(`local_lmtp') already does this. [MERGED] - -The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY -commands. [MERGED] - -vacation(1) has been updated to use the version included with -sendmail. [MERGED] - -The sendmail(8) configuration building tools are installed in -/usr/share/sendmail/cf/. [MERGED] - -New make.conf options: SENDMAIL_MC and SENDMAIL_ADDITIONAL_MC. See -/etc/defaults/make.conf for more information. [MERGED] - -The Makefile in /etc/mail now supports: the new SENDMAIL_MC make.conf -option; the ability to build .cf files from .mc files; generalized map -rebuilding; rebuilding the aliases file; and the ability to stop, start, -and restart sendmail. [MERGED] - -sysinstall(8) now properly preserves /etc/mail during a binary -upgrade. [MERGED] - -awk has been upgraded from gawk-3.0.4 to gawk-3.0.6. This fixes a number -of non-critical bugs and includes a few performance tweaks. [MERGED] - -routed(8) has been updated to version 2.22. [MERGED] - -The truncate(1) utility, which truncates or extends the length -of files, has been added. [MERGED] - -syslogd(8) can take a -n option to disable DNS queries for every -request. [MERGED] - -kenv(1), a command to dump the kernel environment, has been added. -[MERGED] - -The behavior of periodic(8) is now controlled by /etc/defaults/periodic.conf -and /etc/periodic.conf. [MERGED] - -logger(1) can now send messages directly to a remote syslog. [MERGED] - -which(1) is now a C program, rather than a Perl script. - -killall(1) is now a C program, rather than a Perl script. As a -result, killall's -m option now uses the regular expression syntax of -regex(3), rather than that of perl(1). [MERGED] - -killall(1) now allows non-root users to kill SUID root processes that -they started. - -finger(1) now has the ability to support fingering aliases, via the -finger.conf(5) file. [MERGED] - -finger(1) now has support for a .pubkey file. - -nsswitch support has been merged from NetBSD. By creating an -nsswitch.conf(5) file, FreeBSD can be configured so that various -databases such as passwd(5) and group(5) can be looked up using flat -files, NIS, or Hesiod. The old hosts.conf(5) file is no longer used. - -sshd X11Forwarding is now turned on by default on server (any risk is -to the client, where it is already disabled by default). - -RSA Security has waived all patent rights to the RSA algorithm (two -weeks before the patent was due to expire). As a result, the native -OpenSSL implementation of the RSA algorithm is now activated by -default, and the rsaref port and librsaUSA are no longer -required for USA residents. [MERGED] - -sshd is now enabled by default on new installs. [MERGED] - -perl has been updated to version 5.6.0. - -Binutils have been upgraded to 2.10.1. [MERGED] - -libreadline has been upgraded to 4.2. - -The ifconfig(8) command can set the link-layer address of an interface. -[MERGED] - -ifconfig(8) can now accept addresses in slash/CIDR notation. [MERGED] - -setproctitle(3) has been moved from libutil to libc. [MERGED] - -chio(1) now has the ability to specify elements by volume tag instead -of by their physical location as well as the ability to return an -element to its previous location. [MERGED] - -sed(1) now takes a -E option for extended regular expression -support. [MERGED] - -ln(1) now takes an -i option to request user confirmation before -overwriting an existing file. [MERGED] - -ln(1) now takes a -h option to avoid following a target that is a -link, with a -n option for compatability with other implementations. [MERGED] - -Version numbers of installed packages have a new (backward-compatible) -syntax, which supports the "PORTREVISION" and "PORTEPOCH" variables in -ports collection makefiles. These changes help keep track of changes -in the ports collection entries such as security patches or -FreeBSD-specific updates, which aren't reflected in the original, -third-party software distributions. pkg_version(1) can now compare -these new-style version numbers. [MERGED] - -CVS has been updated to 1.11. [MERGED] - -libpcap has been updated to 0.6.2. - -tcpdump has been updated to 3.6.2. - -User-land ppp(8) has received a number of updates and bug fixes. [MERGED] - -To improve performance and disk utilization, the "ports skeletons" in -the FreeBSD Ports Collection have been restructured. Installed ports -and packages should not be affected. [MERGED] - -make(1) has gained the :C/// (regexp substitution), :L (lowercase), -and :U (uppercase) variable modifiers. These were added to reduce the -differences between the FreeBSD and OpenBSD/NetBSD make programs. [MERGED] - -Bugs in make(1), among which include broken null suffix behavior, bad -assumptions about current directory permissions, and potential buffer -overflows, have been fixed. [MERGED] - -fsck wrappers have been imported; this feature provides infrastructure -for fsck(8) to work on different types of filesystems (analogous to -mount(8) and mount_*(8)). - -The behavior of fsck(8) when dealing with various passes (a la -/etc/fstab) has been modified to accomodate multiple-disk filesystems. - -ncurses has been updated to ncurses-5.2-20010512. - -gperf has been updated to 2.7.2. [MERGED] - -style.perl.7, a style guide for Perl code in the FreeBSD base system, -has been added. - -The ISC library from the BIND distribution is now built as -libisc. [MERGED] - -The "in use" percentage metric displayed by netstat(1) now really -reflects the percentage of network mbufs used. [MERGED] - -netstat(1) now has a -W flag that tells it not to truncate addresses, -even if they're too long for the column they're printed in. [MERGED] - -netstat(1) now keeps track of input and output packets on a -per-address basis for each interface. [MERGED] - -sockstat(1) now has -c and -l flags for listing connected and -listening sockets, respectively. [MERGED] - -mergemaster(8) has gained some new features, has been cleaned up -somewhat, and is now more cross-platform friendly. - -mergemaster(8) now sources an /etc/mergemaster.rc file and also -prompts the user to run recommended commands (such as "newaliases") as -needed. [MERGED] - -The compiler chain now uses the FSF-supplied C/C++ runtime -initialization code. This change brings about better compatibility -with code generated from the various egcs and gcc ports, as well as -the stock public FSF source. [MERGED] - -The threads library has gained some signal handling changes, bug -fixes, and performance enhancements (including zero system call thread -switching). gdb(1) thread support has been updated to match these -changes. [MERGED] - -chflags(1) has moved from /usr/bin to /bin. - -Use of the CSMG_* macros no longer require inclusion of <sys/param.h>. - -IP Filter is now supported by the rc.conf(5) boot-time configuration -and initialization. [MERGED] - -The lastlogin(1) utility, which prints the last login time of each -user, has been imported from NetBSD. [MERGED] - -newfs(8) now implements write combining, which can make creation of -new filesystems up to seven times faster. [MERGED] - -newfs(8) now takes a -U option to enable softupdates on a new filesystem. - -The default number of cylinders per group in newfs(8) is now 22, up from 16. - -A number of buffer overflows in config(8) have been fixed. [MERGED] - -pwd(1) can now double as realpath(1), a program to resolve pathnames -to their underlying physical paths. [MERGED] - -file(1) has been contribify-ed, and updated to version 3.35. - -stty(1) now has support for an "erase2" control character, so that -both "delete" and "backspace" can be used to erase characters. [MERGED] - -The ibcs2(8), linux(8), osf1(8), and svr4(8) scripts, whose sole -purpose was to load emulation kernel modules, have been removed. The -kernel module system will automatically load them as needed to fulfill -dependencies. - -top(1) will now use the full width of its tty. - -groff(1) and its related utilities have been updated to FSF version -1.17. This import brings in a new mdoc(7) macro package, which -removes many of the limitations of its predecessor. [MERGED] - -A number of cleanups and enhancements have been applied to the PCI -subsystem. /usr/share/misc/pci_vendors now contains a vendor/device -database, which can be used by pciconf(8). - -indent(1) has gained some new formatting options. [MERGED] - -sysinstall now uses some more intuitive defaults thanks to some new -dialog support functions. [MERGED] - -The default root partition in sysinstall is now 100MB on the i386 and -120MB on the alpha. - -gcc has been updated to 2.95.3. [MERGED] - -Shortly after the receipt of a SIGINFO signal (normally control-T from -the controlling tty), fsck_ffs will now output a line indicating the -current phase number and progress information relevant to the current -phase. [MERGED] - -fsck(8) and fsck_ffs(8) now support background filesystem checks to -mounted FFS filesystems with the -B option (softupdates must be -enabled on these filesystems). The -F flag now determines whether a -specified filesystem needs foreground checking. - -fsck(8) now has support for foreground (-F) and background (-B) -checks. Traditionally, fsck(8) is invoked before the filesystems are -mounted and all checks are done to completion at that time. If -background checking is available, fsck(8) is invoked twice. It is -first invoked at the traditional time, before the filesystems are -mounted, with the -F flag to do checking on all the filesystems that -cannot do background checking. It is then invoked a second time, -after the system has completed going multiuser, with the -B flag to do -checking on all the filesystems that can do background checking. -Unlike the foreground checking, the background checking is started -asynchonously so that other system activity can proceed even on the -filesystems that are being checked. - -Catching up with most other network utilities in the base system, -lpr(1), lpd(8), syslogd(8), and logger(1) are now all IPv6-capable. -[MERGED] - -rm(1) -v now displays the entire pathname of a file being -removed. [MERGED] - -lpr(1), lpq(1), and lpd(8) have received a few minor -enhancements. [MERGED] - -pkg_update(1), a utility to update installed packages and update their -dependencies, has been added. [MERGED] - -pkg_info(1) now supports globbing against names of installed packages. -The -G option disables this behavior, and the -x option causes regular -expression matching instead of shell globbing. [MERGED] - -If the first argument fo ancontrol(8) or wicontrol(8) doesn't start -with a "-", it is assumed to be an interface. - -rdist(1) has been retired. - -Kerberos IV has been updated to 1.0.5. [MERGED] - -Heimdal has been updated to 0.3e. [MERGED] - -ppp(8) has gained the tcpmssfixup option, which adjusts outgoing TCP -SYN packets so that the maximum receive segment size is no larger than -allowed by the interface MTU. - -libcrypt and libdescrypt have been unified to provide a configurable -password authentication hash library. Both the md5 and des hash methods -are provided unless the des hash is specifically compiled out. - -passwd(1) and pw(8) now select the passwd hash algorithm at run time. See -the "passwd_format" attribute in /etc/login.conf. - -In preparation for meeting SUSv2/POSIX <sys/select.h> requirements, -'struct selinfo' and related functions have been moved to -<sys/selinfo.h>. - -gcc now uses a unified libgcc rather than a separate one for threaded -and non-threaded programs. /usr/lib/libgcc_r.a can be removed. [MERGED] - -syslogd(8) now supports a "LOG_CONSOLE" facility (disabled by -default), which can be used to log /dev/console output. [MERGED] - -rpcgen now uses /usr/bin/cpp (as on NetBSD), not /usr/libexec/cpp. - -Boot-time syscons configuration was moved to a machine-independent -rc.syscons. [MERGED] - -burncd(8) now supports a -m option for multisession mode (the default -behavior now is to close disks as single-session). A -l option to -take a list of image files from a filename was also added; '-' can be -used as a filename for stdin. [MERGED] - -dmesg(8) now has a -a option to show the entire message buffer, -including syslog records and /dev/console output. [MERGED] - -In /etc/ssh/sshd_config, the ConnectionsPerPeriod parameter has been -deprecated in favor of MaxStartups. [MERGED] - -cdcontrol(1) now uses the CDROM environment variable to pick a default -device. [MERGED] - -sysctl(8) now supports a -N option to print out variable names only. - -All packages and ports now contain an "origin" directive, which makes -it easier for programs like pkg_version(1) to determine the directory -from which a package was built. [MERGED] - -sysinstall(8) now lives in /usr/sbin, which simplifies the installation -process. The sysinstall(8) manpage is also installed in a more -consistent fashion now. - -config(8) is now better about converting various warnings that should -have been errors into actual fatal errors with an exit code. This -ensures that that 'make buildkernel' doesn't quietly ignore them and -build a bogus kernel without a human to read the errors. [MERGED] - -pkg_create(1) and pkg_add(1) can now work with packages that have -been compressed using bzip2(1). pkg_add(1) will use the -PACKAGEROOT environment variable to determine a mirror site for new -packages. [MERGED] - -pkg_info(1) can now accept a -g flag for verifying an installed -package against its recorded checksums (to see if it's been modified -post-installation). Naturally, this mechanism is only as secure as -the contents of /var/db/pkg if it's to be used for auditing -purposes. [MERGED] - -pkg_version(1) now has a version number comparison routine that -corresponds to the Porters Handbook. It also has a -t option for -testing address comparisons. [MERGED] - -libc is now thread-safe by default; libc_r contains only thread functions. - -find(1) now takes the -empty flag, which returns true if a file or -directory is empty. [MERGED] - -find(1) now takes the -iname and -ipath primaries for case-insensitive -matches, and the -regexp and -iregexp primaries for regular-expression -matches. The -E flag now enables extended regular -expressions. [MERGED] - -find(1) now has the -anewer, -cnewer, -mnewer, -okdir, and --newer[acm][acmt] primaries for comparisons of file timestamps. [MERGED] - -tftpd(8) now takes the -c and -C options, which allow the server to -chroot(2) based on the IP address of the connecting client. tftp(1) -and tftpd(8) can now transfer files larger than 65535 blocks. [MERGED] - -vidcontrol(1) now accepts a -g parameter to select custom text -geometry in the VESA_800x600 raster text mode. [MERGED] - -ldconfig(8) now checks directory ownerships and permissions for -greater security; these checks can be disabled with the -i -flag. [MERGED] - -The rfork_thread(3) library call has been added as a helper function -to rfork(2). Using this function should avoid the need to implement -complex stack swap code. [MERGED] - -Significant additions have been made to internationalization support; -FreeBSD now has complete locale support for the LC_MONETARY, -LC_NUMERIC, and LC_MESSAGES categories. A number of applications have -been updated to take advantage of this support. - -A compat4x distribution has been added for compatibility with FreeBSD -4-STABLE. - -The compat3x distribution has been updated to include libraries -present in FreeBSD 3.5.1-RELEASE. [MERGED] - -savecore(8) now supports a -k option to prevent clearing a crash dump -after saving it. It also attempts to avoid writing large stretches of -zeros to crash dump files to save space and time. [MERGED] - -When requested to delete multiple packages, pkg_delete(1) will now -attempt to remove them in dependency order rather than the order -specified on the command line. [MERGED] - -pkg_delete(1) now can perform glob/regexp matching of package names. -In addition, it supports the -a option for removing all packages and -the -i option for rm(1)-style interactive confirmation. [MERGED] - -tar(1) now supports the TAR_RSH variable, principally to enable the -use of ssh(1) as a transport. [MERGED] - -disklabel(8) now supports partition sizes expressed in kilobytes, -megabytes, or gigabytes, in addition to sectors. [MERGED] - -The pseudo-random number generator implemented by rand(3) has been -improved to provide less biased results. - -login(1) now exports environment variables set by PAM -modules. [MERGED] - -PAM support has been added for account management and sessions. - -Linux PAM has been updated to 0.75. - -The following PAM modules have been added: pam_krb5, pam_nologin, -pam_rootok, pam_wheel. - -wall(1) now supports a -g flag to write a message to all users of a -given group. - -The new CPUTYPE make.conf variable controls the compilation of -processor-specific optimizations in various pieces of code such as -OpenSSL. [MERGED] - -The default value for the CVS_RSH variable (used by cvs(1)) is now -ssh, rather than rsh. [MERGED] - -bc has been updated from 1.04 to 1.06. [MERGED] - -ipfstat(8) now supports the -t option to turn on a top(1)-like -display. [MERGED] - -The dreaded 'going nowhere without my init' bug that manifested itself -while installing on hardware that had labeled disks connected (e.g. -with Tru64 on it) has been fixed. [MERGED] - -pkg_sign(1) and pkg_check(1) have been added to digitally sign and -verify the signatures on binary package files. [MERGED] - -/usr/src/share/examples/BSD_daemon/ now contains a scalable Beastie -graphic. [MERGED] - -dump(8) now supports inheritance of the "nodump" flag down a -hierarchy. [MERGED] - -The ISC DHCP client has been updated to 2.0pl5. [MERGED] - -split(1) now has the ability to split a file longer than 2GB. [MERGED] - -tail(1) now has the ability to work on files longer than 2GB. [MERGED] - -units(1) has received some updates and bugfixes. [MERGED] - -As part of an ongoing process, many manual pages were improved, both -in terms of their formatting markup and in their content. [MERGED] - -pkg_create(1) now records dependencies in dependency order rather than -in the order specified on the command line. This improves the -functioning of "pkg_add -r". [MERGED] - -"lprm -" now works for remote printer queues. [MERGED] - -ftpd(8) now supports a -r flag for read-only mode and a -E flag to -disable EPSV. It also has some fixes to reduce information leakage -and the ability to specify compile-time port ranges. [MERGED] - -ping(8) now supports a -m option to set the TTL of outgoing -packets. [MERGED] - -A version of Transport Independent RPC (TI-RPC) has been imported. - -rpcbind(8) has replaced portmap(8). - -NFS now works over IPv6. - -lockd has been imported from NetBSD. - -rc(8) now has an framework for handling dependencies between -rc.conf(5) variables. [MERGED] - -rc(8) now deletes all non-directory files in /var/run and -/var/spool/lock at boot time. - -The setfacl(1) and getfacl(1) commands have been added to manage -file system Access Control Lists. - -ee(1) editor has been updated to 1.4.2. - -The default TCP port range used by libfetch for passive FTP retrievals -has changed; this affects the behavior of fetch(1), which has gained the --U option to restore the old behavior. [MERGED] - -atacontrol(8) has been added to control various aspects of the ata(4) -driver. - -libcrypt now has support for Blowfish password hashing. - -The functions from libposix1e have been integrated into libc. - -GNATS has been updated to 3.113. [MERGED] - -BSDPAN, a collection of modules that provides tighter integration of -Perl into the FreeBSD Ports Collection, has been added. - -vidcontrol(1) now allows the user to omit the font size specification -when loading a font, and has some better error-handling. - -ip6fw(8) now has the ability to use a preprocessor and use the -q (quiet) -flag when reading from a file. [MERGED] - -devinfo, a simple tool to print the device tree and resource usage by -devices, has been added. - -A new kernel option, "options REGRESSION", enables interfaces and -functionality intended for use during correctness and regression -testing. - -fmtcheck(3), a function for checking consistency of format string -arguments, has been added. - -nl(1), a line numbering filter program, has been added. - -c89(1) has been converted from a shell script to a binary executable, -fixing some minor bugs. - -pax(1) has received a number of enhancements, including cpio(1) -functionality, tar compatability enhancements, and a number of bug -fixes. - -Ukranian language support has been added to the FreeBSD console. - -The performance of the ELF dynamic linker has been improved. [MERGED] - -fdread(1), a program to read data from floppy disks, has been added. -It is designed to provide a means of recovering at least some data -from bad media, and to obviate for a complex invocation of dd(1). - -xargs(1) now supports a -J replstr option that allows the user to tell -xargs to insert the data read from standard input at a specific point -in the command line arguments rather than at the end. - -apmd(8) now supports monitoring of the battery state via the -apm_battery configuration directive. - -telnet(1) now does autologin and encryption by default; a new -y -option turns off encryption. - -The Forth Inspired Command Language used in the boot loader has been -updated to 2.05. - - -2. Supported Configurations ---------------------------- - -For an extensive overview of supported Alpha machines/mainboards please refer -to the HARDWARE.TXT file. - -2.1. Disk Controllers ---------------------- -IDE -ATA - -Adaptec 1535 ISA SCSI controllers -Adaptec 154x series ISA SCSI controllers -Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. - -AdvanSys SCSI controllers (all models). - -BusLogic MultiMaster controllers: - -[ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] - -BusLogic MultiMaster "W" Series Host Adapters: - BT-948, BT-958, BT-958D -BusLogic MultiMaster "C" Series Host Adapters: - BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, - BT-540CF -BusLogic MultiMaster "S" Series Host Adapters: - BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, - BT-542B -BusLogic MultiMaster "A" Series Host Adapters: - BT-742A, BT-542B - -AMI FastDisk controllers that are true BusLogic MultiMaster clones are also -supported. - -DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and -SmartRAID IV SCSI/RAID controllers are supported. The DPT SmartRAID/CACHE V -is not yet supported. - -AMI MegaRAID Express and Enterprise family RAID controllers: - MegaRAID Series 418 - MegaRAID Enterprise 1200 (Series 428) - MegaRAID Enterprise 1300 (Series 434) - MegaRAID Enterprise 1400 (Series 438) - MegaRAID Enterprise 1500 (Series 467) - MegaRAID Enterprise 1600 (Series 471) - MegaRAID Elite 1500 (Series 467) - MegaRAID Elite 1600 (Series 493) - MegaRAID Express 100 (Series 466WS) - MegaRAID Express 200 (Series 466) - MegaRAID Express 300 (Series 490) - MegaRAID Express 500 (Series 475) - Dell PERC - Dell PERC 2/SC - Dell PERC 2/DC - Dell PERC 3/DCL - HP NetRAID-1si - HP NetRAID-3si - HP Embedded NetRAID -Booting from these controllers is supported, but not possible due to -SRM limitations. - -Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x -firmware: - DAC960P - DAC960PD - DAC960PDU - DAC960PL - DAC960PJ - DAC960PG - AcceleRAID 150 - AcceleRAID 250 - eXtremeRAID 1100 -This list includes controllers sold by Digital/Compaq in Alpha systems -in the StorageWorks family, eg. KZPSC, KZPAC. Booting from these -controllers is supported when recognised by SRM (typically Digital/ -Compaq models only, and only in systems where they are supported). -EISA adapters are not supported. - -SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, -53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: - ASUS SC-200 - Data Technology DTC3130 (all variants) - Diamond FirePort (all) - NCR cards (all) - Symbios cards (all) - Tekram DC390W, 390U and 390F - Tyan S1365 - -Qlogic Controllers and variants: - Qlogic 1020, 1040 SCSI and Ultra SCSI host adapters - Qlogic 1240 dual Ultra SCSI controllers - Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD controllers - Qlogic 12160 Ultra3 LVD controllers - Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI controllers - Performance Technology SBS440 ISP1000 variants - Performance Technology SBS450 ISP1040 variants - Performance Technology SBS470 ISP2100 variants - Antares Microsystems P-0033 ISP2100 variants - -With all supported SCSI controllers, full support is provided for -SCSI-I & SCSI-II peripherals, including hard disks, optical disks, -tape drives (including DAT and 8mm Exabyte), medium changers, processor -target devices and CDROM drives. WORM devices that support CDROM commands -are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW -writing support is provided by cdrecord, which is in the ports tree. - -The following CD-ROM type systems are supported at this time: -(cd) SCSI interface -(acd) ATAPI IDE interface - -2.2. Ethernet cards -------------------- - -Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec -AIC-6915 Fast Ethernet controller chip, including the following: - ANA-62011 64-bit single port 10/100baseTX adapter - ANA-62022 64-bit dual port 10/100baseTX adapter - ANA-62044 64-bit quad port 10/100baseTX adapter - ANA-69011 32-bit single port 10/100baseTX adapter - ANA-62020 64-bit single port 100baseFX adapter - -Allied-Telesis AT1700 and RE2000 cards - -Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 -chipsets, including the following: - Alteon AceNIC (Tigon 1 and 2) - 3Com 3c985-SX (Tigon 1 and 2) - Netgear GA620 (Tigon 2) - Silicon Graphics Gigabit Ethernet - DEC/Compaq EtherWORKS 1000 - NEC Gigabit Ethernet - Farallon PN9000SX - Asante PCI 1000BASE-SX Gigabit Ethernet Adapter - Asante GigaNIX1000T Gigabit Ethernet Adapter - -AMD PCnet/PCI (79c970 & 53c974 or 79c974) -AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, -PCnet/Home, and HomePNA. - -SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, -WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT -based clones. SMC Elite Ultra. SMC Etherpower II. - -RealTek 8129/8139 Fast Ethernet NICs including the following: - Allied Telesyn AT2550 - Allied Telesyn AT2500TX - Genius GF100TXR (RTL8139) - NDC Communications NE100TX-E - OvisLink LEF-8129TX - OvisLink LEF-8139TX - Netronix Inc. EA-1210 NetEther 10/100 - KTX-9130TX 10/100 Fast Ethernet - Accton "Cheetah" EN1207D (MPX 5030/5038; RealTek 8139 clone) - SMC EZ Card 10/100 PCI 1211-TX - -Lite-On 82c168/82c169 PNIC Fast Ethernet NICs including the following: - LinkSys EtherFast LNE100TX - NetGear FA310-TX Rev. D1 - Matrox FastNIC 10/100 - Kingston KNE110TX - -Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs - Accton EN1217 (98715A) - Adico AE310TX (98715A) - Compex RL100-TX - CNet Pro120A (98713 or 98713A) - CNet Pro120B (98715) - NDC Communications SFA100A (98713A) - SVEC PN102TX (98713) - -Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs including the following: - LinkSys EtherFast LNE100TX Version 2 - -Winbond W89C840F Fast Ethernet NICs including the following: - Trendware TE100-PCIE - -VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" Fast Ethernet -NICs including the following: - Hawking Technologies PN102TX - D-Link DFE-530TX - AOpen/Acer ALN-320 - -Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs - -National Semiconductor DP83815 Fast Ethernet NICs including the following: - NetGear FA311-TX - NetGear FA312-TX - -National Semiconductor DP83820 and DP83821 Gigabit Ethernet NICs including -the following: - D-Link DGE-500T - SMC EZ Card 1000 (SMC9462TX) - Asante FriendlyNet GigaNIC 1000TA and 1000TPC - Addtron AEG320T - -Sundance Technologies ST201 PCI Fast Ethernet NICs including -the following: - D-Link DFE-550TX - -SysKonnect SK-984x PCI Gigabit Ethernet cards including the following: - SK-9841 1000baseLX single mode fiber, single port - SK-9842 1000baseLX single mode fiber, dual port - SK-9843 1000baseSX multimode fiber, single port - SK-9844 1000baseSX multimode fiber, dual port - SK-9821 1000baseT copper, single port - SK-9822 1000baseT copper, dual port - -Texas Instruments ThunderLAN PCI NICs, including the following: - Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port - Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP - Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC - Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP - Racore 8165 10/100baseTX - Racore 8148 10baseT/100baseTX/100baseFX multi-personality - -ADMtek Inc. AL981-based PCI Fast Ethernet NICs -ADMtek Inc. AN985-based PCI Fast Ethernet NICs -ADMtek Inc. AN986-based USB Ethernet NICs including the following: - LinkSys USB100TX - Billionton USB100 - Melco Inc. LUA-TX - D-Link DSB-650TX - SMC 2202USB - -CATC USB-EL1210A-based USB Ethernet NICs including the following: - CATC Netmate - CATC Netmate II - Belkin F5U111 - -Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs including -the following: - LinkSys USB10T - Entrega NET-USB-E45 - Peracom USB Ethernet Adapter - 3Com 3c19250 - ADS Technologies USB-10BT - ATen UC10T - Netgear EA101 - D-Link DSB-650 - SMC 2102USB - SMC 2104USB - Corega USB-T - -ASIX Electronics AX88140A PCI NICs, including the following: - Alfa Inc. GFC2204 - CNet Pro110B - -DEC EtherWORKS III NICs (DE203, DE204, and DE205) -DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422) -DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc) - -DEC/Intel 21143 based Fast Ethernet NICs, including the following: - DEC DE500-BA - Compaq Presario 7900 series built-in Ethernet - D-Link DFE-570TX - Kingston KNE100TX - LinkSys EtherFast 10/100 Instant GigaDrive built-in Ethernet - -Davicom DM9100 and DM9102 PCI Fast Ethernet NICs, including the -following: - Jaton Corporation XpressNet - -Fujitsu MB86960A/MB86965A - -HP PC Lan+ cards (model numbers: 27247B and 27252A). - -Intel EtherExpress 16 -Intel EtherExpress Pro/10 -Intel EtherExpress Pro/100B PCI Fast Ethernet - -Isolan AT 4141-0 (16 bit) -Isolink 4110 (8 bit) - -Novell NE1000, NE2000, and NE2100 Ethernet interface. - -PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, -Winbond W89C940, Surecom NE-34, VIA VT86C926. - -3Com 3C501 cards - -3Com 3C503 Etherlink II - -3Com 3c505 Etherlink/+ - -3Com 3C507 Etherlink 16/TP - -3Com 3C509, 3C579, 3C590/592/595/900/905/905B/905C PCI -(Fast) Etherlink III / (Fast) Etherlink XL - -3Com 3c980/3c980B Fast Etherlink XL server adapter - -3Com 3cSOHO100-TX OfficeConnect adapter - -Toshiba Ethernet cards - -Crystal Semiconductor CS89x0-based NICs, including: - IBM Etherjet ISA - -Note that NO token ring cards are supported at this time as we're -still waiting for someone to donate a driver for one of them. Any -takers? - - -2.3. FDDI ---------- - -Digital Equipment DEFPA PCI adapters are supported., - - -2.4. ATM --------- - - o ATM Host Interfaces - - FORE Systems, Inc. PCA-200E ATM PCI Adapters - - Efficient Networks, Inc. ENI-155p ATM PCI Adapters - - o ATM Signaling Protocols - - The ATM Forum UNI 3.1 signaling protocol - - The ATM Forum UNI 3.0 signaling protocol - - The ATM Forum ILMI address registration - - FORE Systems' proprietary SPANS signaling protocol - - Permanent Virtual Channels (PVCs) - - o IETF "Classical IP and ARP over ATM" model - - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5" - - RFC 1577, "Classical IP and ARP over ATM" - - RFC 1626, "Default IP MTU for use over ATM AAL5" - - RFC 1755, "ATM Signaling Support for IP over ATM" - - RFC 2225, "Classical IP and ARP over ATM" - - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, - "A Distributed ATMARP Service Using SCSP" - - o ATM Sockets interface - - -2.5. Misc ---------- - -AST 4 port serial card using shared IRQ. - -ARNET 8 port serial card using shared IRQ. -ARNET (now Digiboard) Sync 570/i high-speed serial. - -Boca BB1004 4-Port serial card (Modems NOT supported) -Boca IOAT66 6-Port serial card (Modems supported) -Boca BB1008 8-Port serial card (Modems NOT supported) -Boca BB2016 16-Port serial card (Modems supported) - -Comtrol Rocketport card. - -Cyclades Cyclom-y Serial Board. - -STB 4 port card using shared IRQ. - -SDL Communications Riscom/8 Serial Board. -SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. - -Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, -ONboard 4/16 and Brumby. - -Specialix SI/XIO/SX ISA, PCI serial expansion cards/modules. - -Advance Asound 100, 110 and Logic ALS120 -Crystal Semiconductor CS461x/462x/428x -ENSONIQ AudioPCI ES1370/1371 -ESS ES1868, ES1869, ES1879 and ES1888 -ESS Maestro-1, Maestro-2, and Maestro-2E -ForteMedia fm801 -Gravis UltraSound MAX/PnP -MSS/WSS Compatible DSPs -NeoMagic 256AV/ZX -OPTi 931/82C931 -SoundBlaster, Soundblaster Pro, Soundblaster AWE-32, Soundblaster AWE-64 -Trident 4DWave DX/NX -VIA Technologies VT82C686A -Yamaha DS1 and DS1e -(newpcm driver) - -Connectix QuickCam -Matrox Meteor Video frame grabber -Creative Labs Video Spigot frame grabber -Cortex1 frame grabber -Hauppauge Wincast/TV boards (PCI) -STB TV PCI -Intel Smart Video Recorder III -Various Frame grabbers based on Brooktree Bt848 / Bt878 chip. - -HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. - -PS/2 mice - -Standard PC Joystick - -X-10 power controllers - -GPIB and Transputer drivers. - -Genius and Mustek hand scanners. - -Xilinx XC6200 based reconfigurable hardware cards compatible with -the HOT1 from Virtual Computers (www.vcc.com) - -Support for Dave Mills experimental Loran-C receiver. - -Lucent Technologies WaveLAN/IEEE 802.11 ISA standard speed -(2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes -(NCR WaveLAN/IEEE 802.11, Cabletron RoamAbout 802.11 DS). Note: the -ISA versions of these adapters are actually PCMCIA cards combined with -an ISA to PCMCIA bridge card, so both kinds of devices work with -the same driver. - -Aironet 4500/4800 series 802.11 wireless adapters. The PCI and ISA -models are supported for the Alpha architecture. - -3. Obtaining FreeBSD --------------------- - -You may obtain FreeBSD in a variety of ways: - -3.1. FTP/Mail -------------- - -You can ftp FreeBSD and any or all of its optional packages from -`ftp.FreeBSD.org' - the official FreeBSD release site. - -For other locations that mirror the FreeBSD software see the file -MIRROR.SITES. Please ftp the distribution from the site closest (in -networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to -become an official mirror site. - -If you do not have access to the Internet and electronic mail is your -only recourse, then you may still fetch the files by sending mail to -`ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message -to get more information on how to fetch files using this mechanism. -Please do note, however, that this will end up sending many *tens of -megabytes* through the mail and should only be employed as an absolute -LAST resort! - - -3.2. CDROM ----------- - -FreeBSD 4.x-RELEASE and 3.x-RELEASE CDs may be ordered on CDROM from: - - BSDi / Walnut Creek CDROM - 4041 Pike Lane, Suite D - Concord CA 94520 - USA - +1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) - -Or via the Internet from orders@cdrom.com or http://www.cdrom.com. -Their current catalog can be obtained via ftp from: - - ftp://ftp.cdrom.com/cdrom/catalog - -Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. -FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a -FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely -separate). With a subscription, you will automatically receive updates as -they are released. Your credit card will be billed when each disk is -shipped and you may cancel your subscription at any time without further -obligation. - -Shipping (per order not per disc) is $5 in the US, Canada or Mexico -and $9.00 overseas. They accept Visa, Mastercard, Discover, American -Express or checks in U.S. Dollars and ship COD within the United -States. California residents please add 8.25% sales tax. - -Should you be dissatisfied for any reason, the CD comes with an -unconditional return policy. - - -4. Upgrading from previous releases of FreeBSD ----------------------------------------------- - -If you're upgrading from a previous release of FreeBSD, most likely -it's 3.0 and there may be some issues affecting you, depending -of course on your chosen method of upgrading. There are two popular -ways of upgrading FreeBSD distributions: - - o Using sources, via /usr/src - o Using sysinstall's (binary) upgrade option. - -Please read the UPGRADE.TXT file for more information, preferably -before beginning an upgrade. - - -5. Reporting problems, making suggestions, submitting code. ------------------------------------------------------------ -Your suggestions, bug reports and contributions of code are always -valued - please do not hesitate to report any problems you may find -(preferably with a fix attached, if you can!). - -The preferred method to submit bug reports from a machine with -Internet mail connectivity is to use the send-pr command or use the CGI -script at http://www.FreeBSD.org/send-pr.html. Bug reports -will be dutifully filed by our faithful bugfiler program and you can -be sure that we'll do our best to respond to all reported bugs as soon -as possible. Bugs filed in this way are also visible on our WEB site -in the support section and are therefore valuable both as bug reports -and as "signposts" for other users concerning potential problems to -watch out for. - -If, for some reason, you are unable to use the send-pr command to -submit a bug report, you can try to send it to: - - freebsd-bugs@FreeBSD.org - -Note that send-pr itself is a shell script that should be easy to move -even onto a totally different system. We much prefer if you could use -this interface, since it make it easier to keep track of the problem -reports. However, before submitting, please try to make sure whether -the problem might have already been fixed since. - - -Otherwise, for any questions or tech support issues, please send mail to: - - freebsd-questions@FreeBSD.org - - -If you're tracking the -current development efforts, you should -definitely join the -current mailing list, in order to keep abreast -of recent developments and changes that may affect the way you -use and maintain the system: - - freebsd-current@FreeBSD.org - - -Additionally, being a volunteer effort, we are always happy to have -extra hands willing to help - there are already far more desired -enhancements than we'll ever be able to manage by ourselves! To -contact us on technical matters, or with offers of help, please send -mail to: - - freebsd-hackers@FreeBSD.org - - -Please note that these mailing lists can experience *significant* -amounts of traffic and if you have slow or expensive mail access and -are only interested in keeping up with significant FreeBSD events, you -may find it preferable to subscribe instead to: - - freebsd-announce@FreeBSD.org - - -All of the mailing lists can be freely joined by anyone wishing -to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword -`help' on a line by itself somewhere in the body of the message. This -will give you more information on joining the various lists, accessing -archives, etc. There are a number of mailing lists targeted at -special interest groups not mentioned here, so send mail to majordomo -and ask about them! - - -6. Acknowledgments ------------------- - -FreeBSD represents the cumulative work of many hundreds, if not -thousands, of individuals from around the world who have worked very -hard to bring you this release. For a complete list of FreeBSD -project staffers, please see: - - http://www.FreeBSD.org/handbook/staff.html - -or, if you've loaded the doc distribution: - - file:/usr/share/doc/handbook/staff.html - -Special thanks also go to the many thousands of FreeBSD users and testers -all over the world, without whom this release simply would not have been -possible. - - The FreeBSD Project - -$FreeBSD$ diff --git a/release/texts/i386/INSTALL.TXT b/release/texts/i386/INSTALL.TXT deleted file mode 100644 index 2b4b487..0000000 --- a/release/texts/i386/INSTALL.TXT +++ /dev/null @@ -1,545 +0,0 @@ -+===================== Installing FreeBSD ==========================+ -| | -| Table of Contents: | -| | -| 0.0 Quick Start: | -| 0.1 Installing FreeBSD from CDROM or the Internet. | -| | -| 1.0 Detail on various installation types: | -| 1.1 Installing from a network CDROM | -| 1.2 Installing from Floppies | -| 1.3 Installing from a DOS partition | -| 1.4 Installing from QIC/SCSI tape | -| 1.5 Installing over a network using NFS or FTP | -| 1.5.1 NFS Installation tips | -| 1.5.2 FTP Installation tips | -| 1.6 Tips for Serial Console Users | -| | -| 2.0 DOS User's Q&A section. | -| 2.1 How do I make space for FreeBSD? | -| 2.2 Can I use compressed DOS filesystems from FreeBSD? | -| 2.3 Can I use DOS extended partitions? | -| 2.4 Can I run DOS executables under FreeBSD? | -| | -+=====================================================================+ - -Author: Jordan K. Hubbard -Last updated: Fri Mar 16 14:47:31 PST 2001 - -0.0 Quick Start ---- ----------- - -This manual documents the process of making a new installation of -FreeBSD on your machine. If you are upgrading from a previous -release of FreeBSD, please see the file UPGRADE.TXT for important -information on upgrading. If you are not familiar with configuring -PC hardware for FreeBSD, you should also read the HARDWARE.TXT file - -it contains important information which may save you a lot of grief. - -If you're new to FreeBSD then you should also read EVERYTHING listed -in the Documentation menu of the installer. It may seem like a lot -to read, but the time you spend now reading the documents will be made -up many times over because you were adequately prepared. Also, you will -know the types of information available should you get stuck later. -Once the system is installed, you can also revisit this menu and use a -WEB browser to read the installed FAQ (Frequently Asked Questions) and -Handbook HTML documentation sets for FreeBSD. You can also use the -browser to visit other WEB sites on the net (like http://www.freebsd.org) -if you have an Internet connection. See ABOUT.TXT for more information -on the resources available to you. - -The best laid plans sometimes go awry, so if you run into trouble take a -look at TROUBLE.TXT which contains valuable troubleshooting information. -You should also read ERRATA.TXT before installing and follow the pointers -there carefully since this will stop you from falling over any problems -which have reported in the interim for your particular release. - -DISCLAIMER: While FreeBSD does its best to safeguard against -accidental loss of data, it's still more than possible to WIPE OUT -YOUR ENTIRE DISK with this installation if you make a mistake! Please -do not proceed to the final FreeBSD installation menu unless you've -adequately backed up any important data first! We really mean it! - -FreeBSD requires a 386 or better processor to run (sorry, there is no -support for '286 processors) and at least 5 megs of RAM to install -and 4 megs of RAM to run. You will need at least 100MB of free hard -drive space for the most minimal installation. See below for ways of -shrinking existing DOS partitions in order to install FreeBSD. - - -0.1 Installing FreeBSD from CDROM or the Internet ---- --------------------------------------------- - -The easiest type of installation is from CD. If you have a supported -CDROM drive and a FreeBSD installation CD from Walnut Creek CDROM, -there are 2 ways of starting the installation from it: - - 1. If your system supports bootable CDROM media (usually an option - which can be selectively enabled in the controller's setup menu - or in the PC BIOS for some systems) and you have it enabled, - FreeBSD supports the "El Torrito" bootable CD standard. Simply - put the installation CD in your CDROM drive and boot the system - to begin installation. - - 2. Build a set of FreeBSD boot floppies from the floppies/ - directory in every FreeBSD distribution. Either simply use the - ``makeflp.bat'' script from DOS or read floppies/README.TXT - for more information on creating the bootable floppies under - different operating systems. Then you simply boot from the - first floppy and you should soon be in the FreeBSD installation. - -If you don't have a CDROM and would like to simply install over the -net using PPP, slip or a dedicated connection, simply fetch the -<FreeBSD-release>/floppies/boot.flp file from: - - ftp://ftp.freebsd.org/pub/FreeBSD - -or one of its many mirrors (http://www.freebsd.org/handbook/mirrors.html) -and follow step 3 above. You should also read the floppies/README.TXT -file as it contains important information for downloaders. - -Once you have your boot floppies made, please go to section 1.5 of this -document for additional tips on installing via FTP or NFS. - - -1.0 Detail on various installation types ---- ------------------------------------ - -Once you've gotten yourself to the initial installation screen somehow, -you should be able to follow the various menu prompts and go from there. -If you've never used the FreeBSD installation before, you are also -encouraged to read some of the documentation in the the Documentation -submenu as well as the general "Usage" instructions on the first menu. - - NOTE: If you get stuck at a screen, hit the F1 key for online - documentation relevant to that specific section. - -If you've never installed FreeBSD before, or even if you have, the -"Standard" installation mode is the most recommended since it makes sure -that you'll visit all the various important checklist items along the -way. If you're much more comfortable with the FreeBSD installation -process and know _exactly_ what you want to do, use the Express or -Custom installation options. If you're upgrading an existing system, -use the Upgrade option. - -The FreeBSD installer supports the direct use of floppy, DOS, tape, -CDROM, FTP, NFS and UFS partitions as installation media, further tips -on installing from each type of media listed below. - - -1.1 Installing from a network CDROM ---- ------------------------------- - -If you simply wish to install from a local CDROM drive then see the -Quick Start section. If you don't have a CDROM drive on your system -and wish to use a FreeBSD distribution CD in the CDROM drive of -another system to which you have network connectivity, there are also -several ways of going about it: - -1. If you would be able to FTP install FreeBSD directly from the CDROM - drive in some FreeBSD machine, it's quite easy: You simply add the - following line to the password file (using the vipw command): - - ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin - - Warning: This may allow anyone on the local network (or Internet) to - make "anonymous FTP" connections to this machine, which may not be - desirable. - - On the machine on which you are running the install, go to the "Options" - menu and set "Release Name" to "any". You may then choose a Media - type of FTP and type in: ``ftp://<machine with CDROM drive>'' after - picking "URL" in the ftp sites menu. - -2. If you would rather use NFS to export the CDROM directly to the - machine(s) you'll be installing from, you need to first add an - entry to the /etc/exports file (on the machine with the CDROM drive) - which looks something like this: - - /cdrom -ro ziggy.foo.com - - To allow the machine "ziggy.foo.com" to mount the CDROM directly - via NFS during installation. The machine with the CDROM must also - be configured as an NFS server, of course, and if you're not sure how - to do that then an NFS installation is probably not the best choice - for you unless you're willing to read up on rc.conf(5) and configure - things appropriately. Assuming that this part goes smoothly, you - should be able to enter: cdrom-host:/cdrom as the path for an NFS - installation when the target machine is installed, e.g. wiggy:/cdrom - - -1.2 Installing from Floppies ---- ------------------------ - -If you must install from floppy disks, either due to unsupported -hardware or just because you enjoy doing things the hard way, you must -first prepare some floppies for the install. - -First, make your boot floppies as described in floppies/README.TXT - -Second, read the file LAYOUT.TXT and pay special attention to the -"Distribution format" section since it describes which files you're -going to need to put onto floppy and which you can safely skip. - -Next you will need, at minimum, as many 1.44MB floppies as it takes to -hold all files in the bin (binary distribution) directory. If you're -preparing these floppies under DOS, then THESE floppies *must* be -formatted using the MS-DOS FORMAT command. If you're using Windows, -use the Windows File Manager format command. - -Don't 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'm taking such special care to mention it here! - -If you're creating the floppies from another FreeBSD machine, a format -is still not a bad idea though you don't need to put a DOS filesystem -on each floppy. You can use the `disklabel' and `newfs' commands to -put a UFS filesystem on a floppy, as the following sequence of -commands illustrates: - - fdformat -f 1440 fd0.1440 - disklabel -w -r fd0.1440 floppy3 - newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0 - -After you've formatted the floppies for DOS or UFS, you'll 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've got all the distributions you want -packed up in this fashion. Each distribution should go into its own -subdirectory on the floppy, e.g.: a:\bin\bin.inf, a:\bin\bin.aa, -a:\bin\bin.ab, ... - -IMPORTANT NOTE: The bin.inf file also needs to go on the first floppy -of the bin 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. When putting distributions onto -floppies, the <distname>.inf file MUST occupy the first floppy of each -distribution set! This is also covered in ABOUT.TXT - -Once you come to the Media screen of the install, select "Floppy" and -you'll be prompted for the rest. - - -1.3 Installing from a DOS partition ---- ------------------------------- - -To prepare for installation from an MS-DOS partition you should simply -copy the files from the distribution into a directory called -"FREEBSD" on the Primary DOS partition ("Drive C:"). For example, to do -a minimal installation of FreeBSD from DOS using files copied from the -CDROM, you might do something like this: - - C:\> MD C:\FREEBSD - C:\> XCOPY /S E:\BIN C:\FREEBSD\BIN - -Assuming that `E:' was where your CD was mounted. - -For as many `DISTS' as you wish to install from DOS (and you have free -space for), install each one in a directory under `C:\FREEBSD' - the -BIN dist is only the minimal requirement. - -Once you've copied the directories, you can simply launch the installation -from floppies as normal and select "DOS" as your media type when the time -comes. - - -1.4 Installing from QIC/SCSI Tape ---- ----------------------------- - -When installing from tape, the installation program expects the files -to be simply tar'ed onto it, so after fetching all of the files for -the distributions you're interested in, simply tar them onto the tape -with a command something like this: - - cd /where/you/have/your/dists - tar cvf /dev/rwt0 (or /dev/rsa0) 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'll be allowed -to choose) to accommodate the FULL contents of the tape you've -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. - -SPECIAL NOTE: When going to do the installation, the tape must be in -the drive *before* booting from the boot floppies. The installation -"probe" may otherwise fail to find it. - -Now create a boot floppy as described in section 0.1 and proceed with -the installation. - - -1.5 Installing over a network using FTP or NFS ---- ------------------------------------------ - -After making the boot floppies as described in the first section, you can -load the rest of the installation over a network using one of 3 types -of connections: - - Serial port: SLIP / PPP - Parallel port: PLIP (using ``laplink'' style cable) - Ethernet: A standard Ethernet controller (including - certain PCCARD devices). - -Serial Port ------------ - -SLIP support is rather primitive, and is limited primarily to -hard-wired links, such as a serial cable running between two -computers. The link must be hard-wired because the SLIP installation -doesn't currently offer a dialing capability. If you need to dial out -with a modem or otherwise dialog with the link before connecting to -it, then I recommend that the PPP utility be used instead. - -If you're using PPP, make sure that you have your Internet Service -Provider's IP address and DNS information handy as you'll need to know -it fairly early in the installation process. You may also need to -know your own IP address, though PPP supports dynamic address -negotiation and may be able to pick up this information directly from -your ISP if they support it. - -You will also need to know how to use the various "AT commands" for -dialing out with your particular brand of modem as the PPP dialer -provides only a very simple terminal emulator. - - -Parallel Port -------------- - -If a hard-wired connection to another FreeBSD or Linux machine is -available, you might also consider installing over a "laplink" style -parallel port cable. The data rate over the parallel port is much -higher than what is typically possible over a serial line (up to -50k/sec), thus resulting in a quicker installation. It's not -typically necessary to use "real" IP addresses when using a -point-to-point parallel cable in this way and you can generally just -use RFC 1918 style addresses for the ends of the link (e.g. 10.0.0.1, -10.0.0.2, etc). - -IMPORTANT NOTE: If you use a Linux machine rather than a FreeBSD -machine as your PLIP peer, you will also have to specify "link0" in -the TCP/IP setup screen's ``extra options for ifconfig'' field in -order to be compatible with Linux's slightly different PLIP protocol. - - -Ethernet --------- - -FreeBSD supports most common PC Ethernet cards, a table of supported -cards (and their required settings) being provided as part of the -FreeBSD Hardware Guide (see the Documentation menu on the boot floppy -or the top level directory of the CDROM). If you are using one of the -supported PCMCIA Ethernet cards, also be sure that it's 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 are appropriate to -your particular network setup. If you will be referring to other -hosts by name rather than IP address, you'll also need a name server -and possibly the address of a gateway (if you're using PPP, it's your -provider's IP address) to use in talking to it. If you want to install -by FTP via an HTTP proxy (see below), you will also need the proxy's -address. - -If you do not know the answers to these questions then you should -really probably talk to your system administrator _first_ before -trying this type of installation! Using a randomly chosen IP address -or netmask on a live network will almost certainly get you shot at -dawn. - -Once you have a network connection of some sort working, the -installation can continue over NFS or FTP. - - -1.5.1 NFS installation tips ------ --------------------- - - 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 and Linux 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 also support - "subdir mounts", e.g. if your FreeBSD distribution directory lives - on: wiggy:/usr/archive/stuff/FreeBSD - Then wiggy 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's likely that you don't have this - properly enabled! - - -1.5.2 FTP Installation tips ------ --------------------- - - FTP installation may be done from any mirror site containing a - reasonably up-to-date version of FreeBSD. A full menu of - reasonable choices for almost any location in the world is - provided in the FTP site menu during installation. - - 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 ``URL'' choice in that menu. A URL can - contain a hostname or an IP address, so the following would - work in the absence of a name server: - - ftp://192.216.191.11/pub/FreeBSD - - There are three FTP installation modes you can use: - - o FTP: - - This method uses the standard "Active" mode for file - transfers which allows the server to initiate a connection - to the client. This will not work through most firewalls - but will often work best with older FTP servers that do - not support passive mode. If your connection hangs with - passive mode, try this one! - - o FTP Passive: - - This sets the FTP "Passive" mode which prevents the - server from opening connections to the client. This - option is best for users to pass through firewalls that - do not allow incoming connections on random port - addresses. - - o FTP via an HTTP proxy: - - This option instructs FreeBSD to use HTTP to connect to a - proxy for all FTP operations. The proxy will translate - the requests and send them to the FTP server. This - allows the user to pass through firewalls that do not - allow FTP at all, but offer an HTTP proxy. You must - specify the hostname of the proxy in addition to the FTP - server. - - In the rare case that you have an FTP proxy that does not go - through HTTP, you can specify the URL as something like : - - ftp://foo.bar.com:1234/pub/FreeBSD - - Where "1234" is the port number of the proxy ftp server. - - -1.6 Tips for Serial Console Users ---- ----------------------------- - -If you'd like to install FreeBSD on a machine using just a serial -port (e.g. you don't have or wish to use a VGA card), please follow -these steps. - - 1. Connect some sort of ANSI (vt100) compatible terminal or terminal - emulation program to the COM1 port of the PC you are installing - FreeBSD onto. - - 2. Unplug the keyboard (yes, that's correct!) and then try to boot - from floppy or the installation CDROM, depending on the type of - installation media you have, with the keyboard unplugged. - - 3. If you don't get any output on your serial console, plug - the keyboard in again and wait for some beeps. If you are - booting from the CDROM, proceed to Step 5 as soon as you hear - the beep. - - 4. For a floppy boot, the first beep means to remove the - kern.flp floppy and insert the mfsroot.flp floppy, after - which you should press enter and wait for another beep. - - 5. Hit the space bar, then enter - - boot -h - - and you should now definitely be seeing everything on the - serial port. If that still doesn't work, check your serial - cabling as well as the settings on your terminal emulation - program or actual terminal device. It should be set for - 9600 baud, 8 bits, no parity. - - -2.0 DOS user's Question and Answer section ---- -------------------------------------- - -2.1 Help! I have no space! Do I need to delete everything first? ---- -------------------------------------------------------------- - -If your machine is already running 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/ subdirectory on the FreeBSD -CDROM or on the various FreeBSD ftp sites, to be quite useful. - -FIPS allows you to split an existing DOS partition into two pieces, -preserving the original partition and allowing you to install onto the -second free piece. You first "defrag" your 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 partition. Also note -that FIPS will create the second partition as a "clone" of the first, -so you'll actually see that you now have two DOS Primary partitions -where you formerly had one. Don't be alarmed! You can simply delete -the extra DOS Primary partition (making sure it's the right one by -examining its size! :) - -NOTE: FIPS does NOT currently work with FAT32 or VFAT style partitions -as used by newer versions of Windows 95. To split up such a partition, -you will need a commercial product such as Partition Magic 3.0. Sorry, -but this is just the breaks if you've got a Windows partition hogging -your whole disk and you don't want to reinstall from scratch. - -2.2 Can I use compressed 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 as you will probably regret it greatly! - -It is probably better to create another uncompressed DOS extended -partition and use this for communications between DOS and FreeBSD if -such is your desire. - - -2.3 Can I mount my 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/da0s5, your E: -drive /dev/da0s6, and so on. This example assumes, of course, that -your extended partition is on SCSI drive 0. For IDE drives, substitute -``ad'' for ``da'' appropriately. You otherwise mount extended -partitions exactly like you would mount any other DOS drive, e.g.: - -mount -t msdos /dev/da0s5 /dos_d - - -2.4 Can I run DOS binaries under FreeBSD? ---- ------------------------------------- - -Ongoing work with BSDI's doscmd utility will suffice in many cases, -though it still has some rough edges. If you're interested in working -on this, please send mail to emulation@FreeBSD.org and indicate that -you're interested in joining this ongoing effort! - -There is also a neat utility called "pcemu" in the ports collection -which emulates an 8088 and enough BIOS services to run DOS text mode -applications. It requires the X Window System (XFree86) to operate. - ----- End of Installation Guide --- diff --git a/release/texts/i386/RELNOTES.TXT b/release/texts/i386/RELNOTES.TXT deleted file mode 100644 index 2e3fbb9..0000000 --- a/release/texts/i386/RELNOTES.TXT +++ /dev/null @@ -1,2028 +0,0 @@ - RELEASE NOTES - FreeBSD Release 5.0-SNAP - (i386 Architecture) - -This is a 5.0-CURRENT release SNAPshot of FreeBSD, an active -development branch which will produce its first release in late -2001. Those features which have also been back-ported to -the 4.x-stable branch (the next release for which will be 4.3) -are marked [MERGED]. - -Any installation failures or crashes should be reported by using the -send-pr command (those preferring a Web-based interface can also see -http://www.FreeBSD.org/send-pr.html). - -For information about FreeBSD and the layout of the 5.0-RELEASE -directory (especially if you're installing from floppies!), see -ABOUT.TXT. For installation instructions, see the INSTALL.TXT and -HARDWARE.TXT files. - -For the latest of these 5.0-current snapshots, you should always see: - - ftp://current.FreeBSD.org/pub/FreeBSD - -If you wish to get the latest post-4.x-RELEASE technology. - -Table of contents: ------------------- -1. What's new since the 4.0/5.0 branch - 1.1 KERNEL CHANGES - 1.2 SECURITY FIXES - 1.3 USERLAND CHANGES - -2. Supported Configurations - 2.1 Disk Controllers - 2.2 Ethernet cards - 2.3 FDDI - 2.4 ATM - 2.5 Misc - -3. Obtaining FreeBSD - 3.1 FTP/Mail - 3.2 CDROM - -4. Upgrading from previous releases of FreeBSD - -5. Reporting problems, making suggestions, submitting code - -6. Acknowledgments - - -1. What's new since the 4.0/5.0 branch --------------------------------------- -All changes described here are unique to the 5.0 branch unless -specifically marked as [MERGED] features. - - -1.1. KERNEL CHANGES -------------------- - -A new event notification facility called kqueue was added to the -FreeBSD kernel. This is a new interface which is able to replace -poll/select, offering improved performance, as well as the ability -to report many different types of events. Support for monitoring -changes in sockets, pipes, fifos, and files are present, as well as -for signals and processes. [MERGED] - -Support for named extended attributes was added to the FreeBSD kernel. -This allows the kernel, and appropriately privileged userland processes, -to tag files and directories with attribute data. Extended attributes -were added to support the TrustedBSD Project, in particular ACLs, -capability data, and mandatory access control labels (see -/usr/src/sys/ufs/ufs/README.extattr for details). - -Support for Intel's Wired for Management 2.0 (PXE) was added to -the FreeBSD boot loader. Due to API differences, the older PXE -versions are not supported. This allow network booting using DHCP. [MERGED] - -POSIX.1b Shared Memory Objects are now supported. The implementation -uses regular files, but automatically enables the MAP_NOSYNC flag -when they are mmap(2)ed. [MERGED] - -Added support for PCI Ethernet adapters based on the National Semiconductor -DP83815 chipset, including the NetGear FA312-TX. - -Due to a licensing change, softupdates have been integrated into the -main portion of the kernel source tree. As a consequence, softupdates -are now available with the GENERIC kernel. [MERGED] - -When running with softupdates, statfs(2) and df(1) will track the -number of blocks and files that are committed to being freed. - -A driver for AGP hardware has been added. [MERGED] - -ipfilter has been updated to 3.4.16. [MERGED] - -Various fixes and improvements to the IPv6 code have been merged in -from the KAME project, including significantly-improved IPSEC -functionality. [MERGED] - -twe 3ware ATA RAID driver added. [MERGED] - -The tap driver, a virtual Ethernet device driver for bridged -configurations, has been added. [MERGED] - -accept_filters, a kernel feature to reduce overheads when accepting -and reading new connections on listening sockets, has been added. -[MERGED] - -The ata(4) driver now has support for ATA100 controllers. In -addition, it now supports the ServerWorks ROSB4 ATA33 chipset, the CMD -648 ATA66 and CMD 649 ATA100 chipsets, and the Cyrix 5530. [MERGED] - -To provide more flexible configuration, the various options for the -ata(4) driver are now boot loader tunables, rather than kernel -configure-time options. [MERGED] - -The ata(4) driver now has support for tagged queuing, which is -enabled by the hw.ata.tags loader tunable. [MERGED] - -The ata(4) driver now has support for ATA "pseudo" RAID controllers as -the Promise Fasttrak and HighPoint HPT370 controllers. [MERGED] - -The ti(4) driver now supports the Alteon AceNIC 1000baseT Gigabit -Ethernet and Netgear GA620T 1000baseT Gigabit cards. [MERGED] - -The mly(4) driver, for Mylex PCI to SCSI AccelRAID and eXtremeRAID -controllers with firmware 6.x and later, has been added. [MERGED] - -The asr(4) driver, which provides support for the Adaptec SCSI RAID -controller family, as well as the DPT SmartRAID V and VI families, has -been added. [MERGED] - -SMP support has been largely reworked, incorporating code from BSD/OS -5.0. One of the main features of SMPng ("SMP Next Generation") is to -allow more processes to run in kernel, without the need for spin locks -that can dramatically reduce the efficiency of multiple processors. -Interrupt handlers now have contexts associated with them that allow -them to be blocked, which reduces the need to lock out interrupts. - -The xl(4) driver now supports the 3Com 3C556 and 3C556B MiniPCI -adapters used on some laptops. [MERGED] - -The kernel and modules have been moved to the directory /boot/kernel, -so they can be easily manipulated together. The boot loader has been -updated to make this change as seamless as possible. - -A filesystem snapshot capability has been added to FFS. Details can -be found in /usr/src/sys/ufs/ffs/README.snapshot. - -Softupdates for FFS have received some bug fixes and enhancements. - -A bug in FFS that could cause superblock corruption on very large -filesystems has been corrected. [MERGED] - -Support for the Adaptec FSA family of PCI-SCSI RAID controllers has -been added, in the form of the aac(4) driver. [MERGED] - -The ng_mppc(4) and ng_bridge(4) node types have been added to the -netgraph subsystem. The ng_ether(4) node is now dynamically loadable. -Miscellaneous bug fixes and enhancements have also been made. [MERGED] - -The pcn(4) driver, which supports the AMD PCnet/FAST, PCnet/FAST+, -PCnet/FAST III, PCnet/PRO, PCnet/Home, and HomePNA adapters, has been added. -Although these cards are already supported by the lnc(4) driver, the pcn -driver runs these chips in 32-bit mode and uses the RX alignment feature to -achieve zero-copy receive. This driver is also machine-independent, -so it will work on both the i386 and alpha platforms. The lnc driver -is still needed to support non-PCI cards. [MERGED] - -A bug in the ed(4) driver that could cause panics with very short -packets and BPF or bridging active has been fixed. [MERGED] - -The i386 boot loader now has support for a "nullconsole" console type, -for use on systems with neither a video console nor a serial -port. [MERGED] - -The pcm(4) driver now supports the ESS Solo 1, Maestro-1, Maestro-2, -and Maestro-2e; Forte Media fm801, ESS Maestro-2e, and VIA -Technologies VT82C686A sound card/chipsets, and has received some -other updates. Separate drivers for the SoundBlaster 8 and -Soundblaster 16 now replace an older, unified driver. A driver for -the CMedia CMI8338/CMI8738 sound chips has been added. A driver for -the CS4281 sound chip has been added. A driver for the S3 Sonicvibes -chipset has been added. [MERGED] - -A driver for the Advance Logic ALS4000 has been added. - -A driver for the ESS Maestro-3/Allegro has been added, however due to -licensing restrictions, it cannot be compiled into the kernel. -[MERGED] To use this driver, add the following line to -/boot/loader.conf: - - snd_maestro3_load="YES" - -Replace the PQ_*CACHE options with a single PQ_CACHESIZE option to be -set to the cache size in kilobytes. The old options are still -supported for backwards compatibility. [MERGED] - -The NCPU, NAPIC, NBUS, and NIN kernel configuration options, -for configuring SMP kernels, have been removed. NCPU is now set to a -maximum of 16, and the other, aforementioned options are now dynamic. -[MERGED] - -The ahc(4) driver has been updated. Among various improvements are -improved compatibility with chips in "RAID Port" mode and systems with -AAA and ARO cards installed, as well as performance improvements. -Some bugs were also fixed, including a rare hang on Ultra2/U160 -controllers. [MERGED] - -ACPI support has been merged in from the FreeBSD-ACPI project. - -isdn4bsd has been updated to version 0.96.00 - -The ihfc(4) driver for supporting Cologne Chip Designs HFC devices -under isdn4bsd has been added. - -The itjc(4) driver for supporting NETjet-S / Teles PCI-TJ under -isdn4bsd has been added. - -Experimental support for the Eicon.Diehl DIVA 2.0 and 2.02 ISA PnP -ISDN cards has been added to the isic(4) isdn4bsd driver. - -Active CAPI-based ISDN cards manufacured by AVM are now supported -using the i4bcapi(4) and the iavc(4) driver. The supported cards -are the AVM B1 PCI and AVM B1 ISA Basic Rate cards and the AVM T1 -Primary Rate cards. - -Support for Fujitsu MB86960A/MB86965A based Ethernet PC-Cards is back. -[MERGED] - -devfs(5), which allows entries in the /dev directory to be built -automatically and supports more flexible attachment of devices, has -been largely reworked. devfs(5) is now enabled by default, and is -disabled by the NODEVFS kernel option. - -Preliminary Cardbus support under NEWCARD has been added. This supports -TI113X, TI12XX, TI125X, Ricoh 5C46/5C47, Topic 95/97/100 and -Cirrus Logic PD683X bridges. 16-bit PC Card support under this is not yet -functional. - -Write combining for crashdumps has been implemented. This feature -is useful when write caching is disabled on both SCSI and IDE disks, -where large memory dumps could take up to an hour to complete. [MERGED] - -The bktr(4) driver has been updated to 2.15. New tuner types have -been added, and improvements to the KLD module and to memory -allocation have been made. [MERGED] - -The bktr(4) driver has been updated to 2.17. This fixes bugs in devfs -when unloading and reloading, and syncs with some NetBSD -changes. [MERGED] - -The bktr(4) driver has been updated to 2.18. This adds support for -new Hauppauge Model 44xxx WinTV Cards (the ones with no audio mux). - -Extremely large swap areas (>67 GB) no longer panic the system. - -The snc(4) driver for the National Semiconductor DP8393X (SONIC) -Ethernet controller. Currently, this driver is only used on the PC-98 -architecture. [MERGED] - -The ich(4) driver for the Intel 82801AA (ICH) SMBus controller and -compatibles has been added. [MERGED] - -The Inode Filesystem (IFS) has been added; more information can be -found in /usr/src/sys/ufs/ifs/README. - -The uscanner(4) driver for basic USB scanner support using SANE. See -the SANE home page for supported scanners. HP ScanJet 4100C, 5200C -and 6300C are known to be working. - -The umodem(4) driver for USB modems. Supported so far is only the -3Com 5605 and Metricom Ricochet GS wireless USB modems. - -The ncv, nsp, and stg drivers have been ported from NetBSD/pc98. -They supports NCR 53C50 / Workbit Ninja SCSI-3 / TMC 18C30, 18C50 -based PC-Card/ISA SCSI controllers. [MERGED] - -The cd(4) driver now has support for write operations. This allows -writing to DVD-RAM, PD and similar drives that probe as CD devices. -Note that change affects only random-access writeable devices, not -sequential-only writeable devices such as CD-R drives, which are -supported by cdrecord. [MERGED] - -The ISO-9660 filesystem now has a hook that supports a loadable -character conversion routine. The sysutils/cd9660_unicode port -contains a set of common conversions. [MERGED] - -The an(4) driver for Cisco Aironet cards now supports Wired Equivalent -Privacy (WEP) encryption, settable via ancontrol(8). [MERGED] - -The pcm(4) audio driver is now compiled into the GENERIC kernel by -default. - -The pccard driver and pccardc(8) now support multiple "beep types" -upon card insertion and removal. [MERGED] - -The spic(4) driver, which provides access to the jog dial device on -some Sony laptops, has been added. - -A new netgraph node type ng_one2many(4) for multiplexing and -demultiplexing packets over multiple links has been added. [MERGED] - -A number of cleanups and enhancements have been applied to the PCI -subsystem. /usr/share/misc/pci_vendors now contains a vendor/device -database, which can be used by pciconf(8). - -netgraph(4) has received some updates. - -sbufs, null-terminated string data structures, and their associated -support routines, have been added to the kernel. Details are in -sbuf(9). - -The el(4) driver can now be loaded as a module. - -The vinum(4) volume manager has received some bug fixes and enhancements. - -ICMP ECHO and TSTAMP replies are now rate limited. TCP RSTs generated -due to packets sent to open and unopen ports are now limited by -separate counters. Each rate limiting queue now has its own -description. - -ICMP UNREACH_FILTER_PROHIB messages can now RST TCP connections in the -SYN_SENT state if the correct sequence numbers are sent back, as -controlled by the net.inet.tcp.icmp_may_rst sysctl. [MERGED] - -TCP has received some bug fixes for its delayed ACK behavior. [MERGED] - -TCP now supports the NewReno modification to the TCP Fast Recovery -algorithm. This behavior can be controlled via the -net.inet.tcp.newreno sysctl variable. [MERGED] - -TCP now uses a more aggressive timeout for initial SYN segments; this -allows initial connection attempts to be dropped much faster. [MERGED] - -The TCP_COMPAT_42 kernel option has been removed. - -A new sysctl net.inet.ip.check_interface, which is on by default, -causes IP to verify that an incoming packet arrives on an interface -that has an address matching the packet's destination address. [MERGED] - -PECOFF (WIN32 Execution file format) support has been added. - -kernfs(5) is obsolete and has been retired. - -md(4), the memory disk device, has had the functionality of vn(4) -incorporated into it. md(4) devices can now be configured by -mdconfig(8). vn(4) has been removed. - -The ray(4) driver, which supports the Webgear Aviator wireless network -cards, has been committed. The operation of ray(4) interfaces can be -modified by raycontrol(8). [MERGED] - -Linksys Fast Ethernet PCCARD cards supported by the ed(4) driver now -require the addition of flag 0x80000 to their config line in -pccard.conf(5). This flag is not optional. These Linksys cards will -not be recognized without it. [MERGED] - -A new API has been added for sound cards with hardware volume -control. - -The VESA S3 linear framebuffer driver has been added. - -A new sysctl 'net.link.ether.inet.log_arp_wrong_iface' to controls the -suppression of logging when ARP replies arrive on the wrong -interface. [MERGED] - -A bug in the NFS client that caused bogus access times with -O_EXCL|O_CREAT opens was fixed. [MERGED] - -Client-side NFS locks have been implemented. - -Support for the 80386 processor has been removed from the GENERIC -kernel, as this code seriously pessimizes performance on other ia32 -processors. - -The I386_CPU kernel option to support the 80386 processor is now mutually -exclusive with support for other ia32 processors; this should slightly -improve performance on the 80386 due to the elimination of runtime -processor type checks. - -Custom kernels that will run on the 80386 can still be built by changing -the cpu options in the kernel configuration file to only include I386_CPU. - -Condition variables have now been implemented in the FreeBSD kernel. -See condvar(9) for more details. - -The "make buildkernel" target now gets the name of the -configuration(s) to build from the KERNCONF variable, not KERNEL. It -is no longer required, in some cases, for a "buildworld" to precede a -"buildkernel". (The buildworld is still required when upgrading across -major releases, across binutil upgrades and when config changes -version.) - -bridge(4) and dummynet(4) have received some enhancements and bug fixes. - -ipfw(8) has a new feature ("me") that allows for packet matching on -interfaces with dynamically-changing IP addresses. [MERGED] - -The isp(4) driver has been updated. [MERGED] - -The isp(4) driver now supports target mode for Qlogic SCSI cards, -including Ultra2 and Ultra3 and dual bus cards. - -The ida disk driver now has crashdump support. [MERGED] - -The random(4) device has been rewritten to use the Yarrow algorithm. -It harvests entropy from a variety of interrupt sources, including the -console devices, Ethernet and point-to-point network interfaces, and -mass-storage devices. Entropy from the random(4) device is now -periodically saved to files in /var/db/entropy. - -The fxp(4) driver now requires a "device miibus" entry in the kernel -configuration file. [MERGED] - -A new NFS hash function (based on the Fowler/Noll/Vo hash algorithm) -has been implemented to improve NFS performance by increasing the -efficiency of the nfsnode hash tables. [MERGED] - -The syscons(4) driver now supports keyboard-controlled pasting, by -default bound to Shift-Insert. - -Support for file system Access Control Lists (ACLs) has been -introduced, allowing more fine-grained control of discretionary access -control on files and directories. This support was integrated from -the TrustedBSD Project. More details can be found in -/usr/src/sys/ufs/ufs/README.acls. - -The CAM error recovery code has been updated. - -The directory layout preference algorithm for FFS has been changed to -improve its speed on large filesystems. - -The wx(4) driver now supports the Intel PRO1000-F and PRO1000-T -(10/100/1000) adapters. [MERGED] - -The labpc(4) driver has been removed due to bitrot. - -A new kernel option, "options REGRESSION", enables interfaces and -functionality intended for use during correctness and regression -testing. - -smbfs (CIFS) support in kernel has been added. - -Added support for PCI Gigabit Ethernet adapters based on the National -Semiconductor DP83820 and DP83821 gigabit ethernet controller chips, -including the D-Link DGE-500T, SMC EZ Card 1000 (SMC9462TX), -Asante FriendlyNet GigaNIC 1000TA and 1000TPC and Addtron AEG320T. - -The USER_LDT kernel option is now activated by default. - -A new ddb command "show pcpu" lists some of the per-CPU data. - -A new digi(4) driver has been added to support PCI Xr-based and ISA -Xem Digiboard cards. A new digictl program is (mainly) used to -re-initialise cards that have external port modules attached such as -the PC/Xem. - - -1.2. SECURITY FIXES -------------------- - -sysinstall(8) now allows the user to select one of three "security -profiles" at install-time. These profiles enable different levels of -system security by enabling or disabling various system services in -rc.conf(5) on new installs. [MERGED] - -A bug in which malformed ELF executable images can hang the system has -been fixed (see security advisory FreeBSD-SA-00:41). [MERGED] - -A security hole in Linux emulation was fixed (see security advisory -FreeBSD-SA-00:42). [MERGED] - -rlogind(8), rshd(8), and fingerd(8) are now disabled by default in -/etc/inetd.conf. This only affects new installations. [MERGED] - -String-handling library calls in many programs were fixed to reduce the -possibility of buffer overflow-related exploits. [MERGED] - -TCP now uses stronger randomness in choosing its initial sequence -numbers (see security advisory FreeBSD-SA-00:52). [MERGED] - -Several buffer overflows in tcpdump(1) were corrected (see security -advisory FreeBSD-SA-00:61). [MERGED] - -A security hole in top(1) was corrected (see security advisory -FreeBSD-SA-00:62). [MERGED] - -A potential security hole caused by an off-by-one-error in -gethostbyname(3) has been fixed (see security advisory -FreeBSD-SA-00:63). [MERGED] - -A potential buffer overflow in the ncurses(3X) library, which could -cause arbitrary code to be run from within systat(1), has been corrected -(see security advisory FreeBSD-SA-00:68). [MERGED] - -A vulnerability in telnetd(8) that could cause it to consume large -amounts of server resources has been fixed (see security advisory -FreeBSD-SA-00:69). [MERGED] - -The "nat deny_incoming" command in ppp(8) now works correctly (see -security advisory FreeBSD-SA-00:70). [MERGED] - -A vulnerability in csh(1)/tcsh(1) temporary files that could allow -overwriting of arbitrary user-writable files has been closed (see -security advisory FreeBSD-SA-00:76). [MERGED] - -The ssh(1) binary is no longer SUID root by default. - -Some fixes were applied to the Kerberos IV implementation related to -environment variables, a possible buffer overrun, and overwriting -ticket files. [MERGED] - -telnet(1) now does a better job of sanitizing its environment. [MERGED] - -Several vulnerabilities in procfs(4) were fixed (see security advisory -FreeBSD-SA-00:77). [MERGED] - -A bug in OpenSSH in which a server was unable to disable ssh-agent or -X11 forwarding was fixed (see security advisory FreeBSD-SA-01:01). -[MERGED] - -A bug in ipfw(8) and ipfw6(8) in which inbound TCP segments could -incorrectly be treated as being part of an "established" connection -has been fixed (see security advisory FreeBSD-SA-01:08). [MERGED] - -A bug in crontab(8) that could allow users to read any file on the -system in valid crontab(5) syntax has been fixed (see security -advisory FreeBSD-SA-01:09). [MERGED] - -A vulnerability in inetd(8) that could allow read-access to the -initial 16 bytes of wheel-accessible files has been fixed (see -security advisory FreeBSD-SA-01:11). [MERGED] - -A bug in periodic(8) that used insecure temporary files has been -corrected (see security advisory FreeBSD-SA-01:12). [MERGED] - -A bug in sort(1) in which an attacker might be able to cause it to -abort processing has been fixed (see security advisory -FreeBSD-SA-01:13). [MERGED] - -To fix a remotely-exploitable buffer overflow, BIND has been updated -to 8.2.3 (see security advisory FreeBSD-SA-01:18). [MERGED] - -OpenSSH now has code to prevent (instead of just mitigating through -connection limits) an attack that can lead to guessing the server key -(not host key) by regenerating the server key when an RSA failure is -detected (see security advisory FreeBSD-SA-01:24). [MERGED] - -A number of programs have had output formatting strings corrected so -as to reduce the risk of vulnerabilities. [MERGED] - -A number of programs that use temporary files now do so more -securely. [MERGED] - -A bug in ICMP that could cause an attacker to disrupt TCP and UDP -"sessions" has been corrected. [MERGED] - -A bug in timed(8), which caused it to crash if sent certain malformed -packets, has been corrected (see security advisory -FreeBSD-SA-01:28). [MERGED] - -A bug in rwhod(8), which caused it to crash if sent certain malformed -packets, has been corrected (see security advisory -FreeBSD-SA-01:29). [MERGED] - -A security hole in FreeBSD's FFS and EXT2FS implementations, which -allowed a race condition that could cause users to have unauthorized -access to data, has been fixed (see security advisory -FreeBSD-SA-01:30). [MERGED] - -A remotely-exploitable vulnerability in ntpd(8) has been closed (see -security advisory FreeBSD-SA-01:31). [MERGED] - -A security hole in IPFilter's fragment cache has been closed (see -security advisory FreeBSD-SA-01:32). [MERGED] - -Buffer overflows in glob(3), which could cause arbitrary code to be -run on an FTP server, have been closed. In addition, to prevent some -forms of DOS attacks, glob(3) now allows specification of a limit on -the number of pathname matches it will return. ftpd(8) now uses this -feature (see security advisory FreeBSD-SA-01:33). [MERGED] - -Initial sequence numbers in TCP are more thoroughly randomized, using -an algorithm obtained from OpenBSD (see security advisory -FreeBSD-SA-01:39). [MERGED] - - -1.3. USERLAND CHANGES ---------------------- - -cdcontrol(1) now supports a "cdid" command, which calculates and -displays the CD serial number, using the same algorithm used by the CDDB -database. [MERGED] - -mtree(8) now includes support for a file listing pathnames to be excluded -when creating and verifying prototypes. This makes it easier to use -mtree as a part of an intrusion-detection system. [MERGED] - -OpenSSL has been upgraded to 0.9.6. [MERGED] - -OpenSSL now has support for machine-dependent ASM optimizations, -activated by the new MACHINE_CPU Makefile variable. [MERGED] - -The OPIE one-time-password suite has been updated to 2.32. [MERGED] - -OpenSSH has been upgraded to 2.1.0, which provides support for the -SSH2 protocol, including DSA keys. Therefore, OpenSSH users in the US -no longer need to rely on the restrictively-licensed RSAREF toolkit -which is required to handle RSA keys. OpenSSH 2.1 interoperates well -with other SSH2 clients and servers, including the ssh2 port. See -http://www.openssh.com for more details. [MERGED] - -OpenSSH can now authenticate using OPIE passwords in SSH1 mode. -Support is not yet available in SSH2 mode. [MERGED] - -OpenSSH has been upgraded to 2.2.0. ssh-add(1) and ssh-agent(1) can now -handle DSA keys. An sftp server interoperable with ssh.com clients -and others has been added. scp(1) can now handle files >2GB. -Interoperability with other ssh2 clients/servers has been improved. A -new feature to limit the number of outstanding unauthenticated ssh -connections in sshd has been added. [MERGED] - -OpenSSH has been upgraded to 2.3.0. This version adds support for the -Rijndael encryption algorithm. [MERGED] - -PAM support for OpenSSH has been added. - -A long-standing bug in SSH, which sometimes resulted in a dropped -session when an X11-forwarded client was closed, was fixed. - -Kerberos compatability has been added to OpenSSH. [MERGED] - -OpenSSH has been modified to be more resistant to traffic analysis by -requiring that "non-echoed" characters are still echoed back in a null -packet, as well as by padding passwords sent so as not to hint at -password lengths. [MERGED] - -OpenSSH now has a "VersionAddendum" configuration setting for sshd(8) -to allow changing the part of the OpenSSH version string after the -main version number. - -OpenSSH has been updated to version 2.9, which adds two new programs, -sftp(1) and ssh-keyscan(1). Among the various enhancements: The -default protocol is now v2, rekeying of existing SSH sessions is now -supported, and an experimental SOCKS4 proxy has been added to the -ssh(1) client. - -Support for USB devices was added to the GENERIC kernel and to the -installation programs to support USB devices out of the box. Note that -an AT keyboard must still be used during the initial install, but it -should work fine afterwards. [MERGED] - -The entire i386 bootstrap was revamped to support automatic detection and -use of the Enhanced Disk Drive BIOS extensions to support booting beyond -the 1023rd cylinder. As part of this change, the FreeBSD boot manager -(boot0) was increased from 1 sector in size (512 bytes), to 2 sectors in -length (1024 bytes). As a result, several userland changes were made to -cope with MBR boot loaders of varying sizes. [MERGED] - -The csh(1) shell has been replaced by tcsh(1), although it can still -be run as csh(1). tcsh has been updated to version 6.10. [MERGED] - -The more(1) command has been replaced by less(1), although it can still -be run as more(1). [MERGED] - -ls(1) can produce colorized listings with the -G flag (and appropriate -terminal support). [MERGED] - -libalias(3) and natd(8) now support RFC 2391 (Load Sharing using IP -Network Address Translation), as well as new translation options. -[MERGED] - -FreeBSD can now be installed over an IPv6-only network. [MERGED] - -sendmail upgraded from version 8.9.3 to version 8.11.3. Important changes -include: new default file locations (see -/usr/src/contrib/sendmail/cf/README); newaliases is limited to root and -trusted users; STARTTLS encryption; and the MSA port (587) is turned on by -default. See /usr/src/contrib/sendmail/RELEASE_NOTES for more -information. [MERGED] - -mail.local(8) is no longer installed as a set-user-id binary. If you are -using a /etc/mail/sendmail.cf from the default sendmail.cf included with -FreeBSD any time after 3.1.0, you are fine. If you are using a -hand-configured sendmail.cf and mail.local for delivery, check to make sure -the F=S flag is set on the Mlocal line. Those with .mc files who need to -add the flag can do so by adding the following line to their your .mc file -and regenerating the sendmail.cf file: - MODIFY_MAILER_FLAGS(`LOCAL', `+S')dnl -Note that FEATURE(`local_lmtp') already does this. [MERGED] - -The default /etc/mail/sendmail.cf disables the SMTP EXPN and VRFY -commands. [MERGED] - -vacation(1) has been updated to use the version included with -sendmail. [MERGED] - -The sendmail(8) configuration building tools are installed in -/usr/share/sendmail/cf/. [MERGED] - -New make.conf options: SENDMAIL_MC and SENDMAIL_ADDITIONAL_MC. See -/etc/defaults/make.conf for more information. [MERGED] - -The Makefile in /etc/mail now supports: the new SENDMAIL_MC make.conf -option; the ability to build .cf files from .mc files; generalized map -rebuilding; rebuilding the aliases file; and the ability to stop, start, -and restart sendmail. [MERGED] - -sysinstall(8) now properly preserves /etc/mail during a binary -upgrade. [MERGED] - -awk has been upgraded from gawk-3.0.4 to gawk-3.0.6. This fixes a number -of non-critical bugs and includes a few performance tweaks. [MERGED] - -routed(8) has been updated to version 2.22. [MERGED] - -The truncate(1) utility, which truncates or extends the length -of files, has been added. [MERGED] - -syslogd(8) can take a -n option to disable DNS queries for every -request. [MERGED] - -kenv(1), a command to dump the kernel environment, has been added. -[MERGED] - -The behavior of periodic(8) is now controlled by /etc/defaults/periodic.conf -and /etc/periodic.conf. [MERGED] - -boot98cfg(8), a PC-98 boot manager installation and configuration -utility, has been added. [MERGED] - -logger(1) can now send messages directly to a remote syslog. [MERGED] - -GDB now supports hardware watchpoints (using the kernel's debug register -support that has been introduced in FreeBSD 4.0). [MERGED] - -which(1) is now a C program, rather than a Perl script. - -killall(1) is now a C program, rather than a Perl script. As a -result, killall's -m option now uses the regular expression syntax of -regex(3), rather than that of perl(1). [MERGED] - -killall(1) now allows non-root users to kill SUID root processes that -they started. - -finger(1) now has the ability to support fingering aliases, via the -finger.conf(5) file. [MERGED] - -finger(1) now has support for a .pubkey file. - -nsswitch support has been merged from NetBSD. By creating an -nsswitch.conf(5) file, FreeBSD can be configured so that various -databases such as passwd(5) and group(5) can be looked up using flat -files, NIS, or Hesiod. The old hosts.conf(5) file is no longer used. - -sshd X11Forwarding is now turned on by default on server (any risk is -to the client, where it is already disabled by default). - -RSA Security has waived all patent rights to the RSA algorithm (two -weeks before the patent was due to expire). As a result, the native -OpenSSL implementation of the RSA algorithm is now activated by -default, and the rsaref port and librsaUSA are no longer -required for USA residents. [MERGED] - -sshd is now enabled by default on new installs. [MERGED] - -perl has been updated to version 5.6.0. - -Binutils have been upgraded to 2.10.1. [MERGED] - -libreadline has been upgraded to 4.2. - -The ifconfig(8) command can set the link-layer address of an interface. -[MERGED] - -ifconfig(8) can now accept addresses in slash/CIDR notation. [MERGED] - -setproctitle(3) has been moved from libutil to libc. [MERGED] - -chio(1) now has the ability to specify elements by volume tag instead -of by their physical location as well as the ability to return an -element to its previous location. [MERGED] - -sed(1) now takes a -E option for extended regular expression -support. [MERGED] - -ln(1) now takes an -i option to request user confirmation before -overwriting an existing file. [MERGED] - -ln(1) now takes a -h option to avoid following a target that is a -link, with a -n option for compatability with other implementations. [MERGED] - -Version numbers of installed packages have a new (backward-compatible) -syntax, which supports the "PORTREVISION" and "PORTEPOCH" variables in -ports collection makefiles. These changes help keep track of changes -in the ports collection entries such as security patches or -FreeBSD-specific updates, which aren't reflected in the original, -third-party software distributions. pkg_version(1) can now compare -these new-style version numbers. [MERGED] - -CVS has been updated to 1.11. [MERGED] - -libpcap has been updated to 0.6.2. - -tcpdump has been updated to 3.6.2. - -User-land ppp(8) has received a number of updates and bug fixes. [MERGED] - -To improve performance and disk utilization, the "ports skeletons" in -the FreeBSD Ports Collection have been restructured. Installed ports -and packages should not be affected. [MERGED] - -make(1) has gained the :C/// (regexp substitution), :L (lowercase), -and :U (uppercase) variable modifiers. These were added to reduce the -differences between the FreeBSD and OpenBSD/NetBSD make programs. [MERGED] - -Bugs in make(1), among which include broken null suffix behavior, bad -assumptions about current directory permissions, and potential buffer -overflows, have been fixed. [MERGED] - -fsck wrappers have been imported; this feature provides infrastructure -for fsck(8) to work on different types of filesystems (analogous to -mount(8) and mount_*(8)). - -The behavior of fsck(8) when dealing with various passes (a la -/etc/fstab) has been modified to accomodate multiple-disk filesystems. - -ncurses has been updated to ncurses-5.2-20010512. - -gperf has been updated to 2.7.2. [MERGED] - -style.perl.7, a style guide for Perl code in the FreeBSD base system, -has been added. - -The ISC library from the BIND distribution is now built as -libisc. [MERGED] - -The "in use" percentage metric displayed by netstat(1) now really -reflects the percentage of network mbufs used. [MERGED] - -netstat(1) now has a -W flag that tells it not to truncate addresses, -even if they're too long for the column they're printed in. [MERGED] - -netstat(1) now keeps track of input and output packets on a -per-address basis for each interface. [MERGED] - -sockstat(1) now has -c and -l flags for listing connected and -listening sockets, respectively. [MERGED] - -mergemaster(8) has gained some new features, has been cleaned up -somewhat, and is now more cross-platform friendly. - -mergemaster(8) now sources an /etc/mergemaster.rc file and also -prompts the user to run recommended commands (such as "newaliases") as -needed. [MERGED] - -The compiler chain now uses the FSF-supplied C/C++ runtime -initialization code. This change brings about better compatibility -with code generated from the various egcs and gcc ports, as well as -the stock public FSF source. [MERGED] - -The threads library has gained some signal handling changes, bug -fixes, and performance enhancements (including zero system call thread -switching). gdb(1) thread support has been updated to match these -changes. [MERGED] - -chflags(1) has moved from /usr/bin to /bin. - -Use of the CSMG_* macros no longer require inclusion of <sys/param.h>. - -IP Filter is now supported by the rc.conf(5) boot-time configuration -and initialization. [MERGED] - -The lastlogin(1) utility, which prints the last login time of each -user, has been imported from NetBSD. [MERGED] - -newfs(8) now implements write combining, which can make creation of -new filesystems up to seven times faster. [MERGED] - -newfs(8) now takes a -U option to enable softupdates on a new filesystem. - -The default number of cylinders per group in newfs(8) is now 22, up from 16. - -A number of buffer overflows in config(8) have been fixed. [MERGED] - -pwd(1) can now double as realpath(1), a program to resolve pathnames -to their underlying physical paths. [MERGED] - -file(1) has been contribify-ed, and updated to version 3.35. - -stty(1) now has support for an "erase2" control character, so that -both "delete" and "backspace" can be used to erase characters. [MERGED] - -The ibcs2(8), linux(8), osf1(8), and svr4(8) scripts, whose sole -purpose was to load emulation kernel modules, have been removed. The -kernel module system will automatically load them as needed to fulfill -dependencies. - -top(1) will now use the full width of its tty. - -groff(1) and its related utilities have been updated to FSF version -1.17. This import brings in a new mdoc(7) macro package, which -removes many of the limitations of its predecessor. [MERGED] - -growfs(8), a utility for growing FFS filesystems, has been added. -ffsinfo(8), a utility for dump all the meta-information of an existing -filesystem, has also been added. - -indent(1) has gained some new formatting options. [MERGED] - -sysinstall now uses some more intuitive defaults thanks to some new -dialog support functions. [MERGED] - -The default root partition in sysinstall is now 100MB on the i386 and -120MB on the alpha. - -gcc has been updated to 2.95.3. [MERGED] - -Shortly after the receipt of a SIGINFO signal (normally control-T from -the controlling tty), fsck_ffs will now output a line indicating the -current phase number and progress information relevant to the current -phase. [MERGED] - -fsck(8) and fsck_ffs(8) now support background filesystem checks to -mounted FFS filesystems with the -B option (softupdates must be -enabled on these filesystems). The -F flag now determines whether a -specified filesystem needs foreground checking. - -fsck(8) now has support for foreground (-F) and background (-B) -checks. Traditionally, fsck(8) is invoked before the filesystems are -mounted and all checks are done to completion at that time. If -background checking is available, fsck(8) is invoked twice. It is -first invoked at the traditional time, before the filesystems are -mounted, with the -F flag to do checking on all the filesystems that -cannot do background checking. It is then invoked a second time, -after the system has completed going multiuser, with the -B flag to do -checking on all the filesystems that can do background checking. -Unlike the foreground checking, the background checking is started -asynchonously so that other system activity can proceed even on the -filesystems that are being checked. - -Catching up with most other network utilities in the base system, -lpr(1), lpd(8), syslogd(8), and logger(1) are now all IPv6-capable. -[MERGED] - -libdisk can now do install-time configuration of the i386 boot0 boot -loader. [MERGED] - -rm(1) -v now displays the entire pathname of a file being -removed. [MERGED] - -lpr(1), lpq(1), and lpd(8) have received a few minor -enhancements. [MERGED] - -pkg_update(1), a utility to update installed packages and update their -dependencies, has been added. [MERGED] - -pkg_info(1) now supports globbing against names of installed packages. -The -G option disables this behavior, and the -x option causes regular -expression matching instead of shell globbing. [MERGED] - -If the first argument fo ancontrol(8) or wicontrol(8) doesn't start -with a "-", it is assumed to be an interface. - -rdist(1) has been retired. - -Kerberos IV has been updated to 1.0.5. [MERGED] - -Heimdal has been updated to 0.3e. [MERGED] - -ppp(8) has gained the tcpmssfixup option, which adjusts outgoing TCP -SYN packets so that the maximum receive segment size is no larger than -allowed by the interface MTU. - -libcrypt and libdescrypt have been unified to provide a configurable -password authentication hash library. Both the md5 and des hash methods -are provided unless the des hash is specifically compiled out. - -passwd(1) and pw(8) now select the passwd hash algorithm at run time. See -the "passwd_format" attribute in /etc/login.conf. - -In preparation for meeting SUSv2/POSIX <sys/select.h> requirements, -'struct selinfo' and related functions have been moved to -<sys/selinfo.h>. - -gcc now uses a unified libgcc rather than a separate one for threaded -and non-threaded programs. /usr/lib/libgcc_r.a can be removed. [MERGED] - -syslogd(8) now supports a "LOG_CONSOLE" facility (disabled by -default), which can be used to log /dev/console output. [MERGED] - -rpcgen now uses /usr/bin/cpp (as on NetBSD), not /usr/libexec/cpp. - -Boot-time syscons configuration was moved to a machine-independent -rc.syscons. [MERGED] - -burncd(8) now supports a -m option for multisession mode (the default -behavior now is to close disks as single-session). A -l option to -take a list of image files from a filename was also added; '-' can be -used as a filename for stdin. [MERGED] - -dmesg(8) now has a -a option to show the entire message buffer, -including syslog records and /dev/console output. [MERGED] - -In /etc/ssh/sshd_config, the ConnectionsPerPeriod parameter has been -deprecated in favor of MaxStartups. [MERGED] - -cdcontrol(1) now uses the CDROM environment variable to pick a default -device. [MERGED] - -sysctl(8) now supports a -N option to print out variable names only. - -All packages and ports now contain an "origin" directive, which makes -it easier for programs like pkg_version(1) to determine the directory -from which a package was built. [MERGED] - -sysinstall(8) now lives in /usr/sbin, which simplifies the installation -process. The sysinstall(8) manpage is also installed in a more -consistent fashion now. - -config(8) is now better about converting various warnings that should -have been errors into actual fatal errors with an exit code. This -ensures that that 'make buildkernel' doesn't quietly ignore them and -build a bogus kernel without a human to read the errors. [MERGED] - -pkg_create(1) and pkg_add(1) can now work with packages that have -been compressed using bzip2(1). pkg_add(1) will use the -PACKAGEROOT environment variable to determine a mirror site for new -packages. [MERGED] - -pkg_info(1) can now accept a -g flag for verifying an installed -package against its recorded checksums (to see if it's been modified -post-installation). Naturally, this mechanism is only as secure as -the contents of /var/db/pkg if it's to be used for auditing -purposes. [MERGED] - -pkg_version(1) now has a version number comparison routine that -corresponds to the Porters Handbook. It also has a -t option for -testing address comparisons. [MERGED] - -libc is now thread-safe by default; libc_r contains only thread functions. - -find(1) now takes the -empty flag, which returns true if a file or -directory is empty. [MERGED] - -find(1) now takes the -iname and -ipath primaries for case-insensitive -matches, and the -regexp and -iregexp primaries for regular-expression -matches. The -E flag now enables extended regular -expressions. [MERGED] - -find(1) now has the -anewer, -cnewer, -mnewer, -okdir, and --newer[acm][acmt] primaries for comparisons of file timestamps. [MERGED] - -tftpd(8) now takes the -c and -C options, which allow the server to -chroot(2) based on the IP address of the connecting client. tftp(1) -and tftpd(8) can now transfer files larger than 65535 blocks. [MERGED] - -vidcontrol(1) now accepts a -g parameter to select custom text -geometry in the VESA_800x600 raster text mode. [MERGED] - -ldconfig(8) now checks directory ownerships and permissions for -greater security; these checks can be disabled with the -i -flag. [MERGED] - -The rfork_thread(3) library call has been added as a helper function -to rfork(2). Using this function should avoid the need to implement -complex stack swap code. [MERGED] - -Significant additions have been made to internationalization support; -FreeBSD now has complete locale support for the LC_MONETARY, -LC_NUMERIC, and LC_MESSAGES categories. A number of applications have -been updated to take advantage of this support. - -A compat4x distribution has been added for compatibility with FreeBSD -4-STABLE. - -The compat3x distribution has been updated to include libraries -present in FreeBSD 3.5.1-RELEASE. [MERGED] - -savecore(8) now supports a -k option to prevent clearing a crash dump -after saving it. It also attempts to avoid writing large stretches of -zeros to crash dump files to save space and time. [MERGED] - -When requested to delete multiple packages, pkg_delete(1) will now -attempt to remove them in dependency order rather than the order -specified on the command line. [MERGED] - -pkg_delete(1) now can perform glob/regexp matching of package names. -In addition, it supports the -a option for removing all packages and -the -i option for rm(1)-style interactive confirmation. [MERGED] - -tar(1) now supports the TAR_RSH variable, principally to enable the -use of ssh(1) as a transport. [MERGED] - -disklabel(8) now supports partition sizes expressed in kilobytes, -megabytes, or gigabytes, in addition to sectors. [MERGED] - -The pseudo-random number generator implemented by rand(3) has been -improved to provide less biased results. - -login(1) now exports environment variables set by PAM -modules. [MERGED] - -PAM support has been added for account management and sessions. - -Linux PAM has been updated to 0.75. - -The following PAM modules have been added: pam_krb5, pam_nologin, -pam_rootok, pam_wheel. - -wall(1) now supports a -g flag to write a message to all users of a -given group. - -The new CPUTYPE make.conf variable controls the compilation of -processor-specific optimizations in various pieces of code such as -OpenSSL. [MERGED] - -The default value for the CVS_RSH variable (used by cvs(1)) is now -ssh, rather than rsh. [MERGED] - -bc has been updated from 1.04 to 1.06. [MERGED] - -ipfstat(8) now supports the -t option to turn on a top(1)-like -display. [MERGED] - -pkg_sign(1) and pkg_check(1) have been added to digitally sign and -verify the signatures on binary package files. [MERGED] - -/usr/src/share/examples/BSD_daemon/ now contains a scalable Beastie -graphic. [MERGED] - -dump(8) now supports inheritance of the "nodump" flag down a -hierarchy. [MERGED] - -The ISC DHCP client has been updated to 2.0pl5. [MERGED] - -split(1) now has the ability to split a file longer than 2GB. [MERGED] - -tail(1) now has the ability to work on files longer than 2GB. [MERGED] - -units(1) has received some updates and bugfixes. [MERGED] - -As part of an ongoing process, many manual pages were improved, both -in terms of their formatting markup and in their content. [MERGED] - -pkg_create(1) now records dependencies in dependency order rather than -in the order specified on the command line. This improves the -functioning of "pkg_add -r". [MERGED] - -"lprm -" now works for remote printer queues. [MERGED] - -ftpd(8) now supports a -r flag for read-only mode and a -E flag to -disable EPSV. It also has some fixes to reduce information leakage -and the ability to specify compile-time port ranges. [MERGED] - -ping(8) now supports a -m option to set the TTL of outgoing -packets. [MERGED] - -A version of Transport Independent RPC (TI-RPC) has been imported. - -rpcbind(8) has replaced portmap(8). - -NFS now works over IPv6. - -lockd has been imported from NetBSD. - -rc(8) now has an framework for handling dependencies between -rc.conf(5) variables. [MERGED] - -rc(8) now deletes all non-directory files in /var/run and -/var/spool/lock at boot time. - -The setfacl(1) and getfacl(1) commands have been added to manage -file system Access Control Lists. - -ee(1) editor has been updated to 1.4.2. - -The default TCP port range used by libfetch for passive FTP retrievals -has changed; this affects the behavior of fetch(1), which has gained the --U option to restore the old behavior. [MERGED] - -atacontrol(8) has been added to control various aspects of the ata(4) -driver. - -libcrypt now has support for Blowfish password hashing. - -The functions from libposix1e have been integrated into libc. - -GNATS has been updated to 3.113. [MERGED] - -BSDPAN, a collection of modules that provides tighter integration of -Perl into the FreeBSD Ports Collection, has been added. - -vidcontrol(1) now allows the user to omit the font size specification -when loading a font, and has some better error-handling. - -ip6fw(8) now has the ability to use a preprocessor and use the -q (quiet) -flag when reading from a file. [MERGED] - -devinfo, a simple tool to print the device tree and resource usage by -devices, has been added. - -fmtcheck(3), a function for checking consistency of format string -arguments, has been added. - -nl(1), a line numbering filter program, has been added. - -c89(1) has been converted from a shell script to a binary executable, -fixing some minor bugs. - -pax(1) has received a number of enhancements, including cpio(1) -functionality, tar compatability enhancements, and a number of bug -fixes. - -Ukranian language support has been added to the FreeBSD console. - -The performance of the ELF dynamic linker has been improved. [MERGED] - -fdread(1), a program to read data from floppy disks, has been added. -It is designed to provide a means of recovering at least some data -from bad media, and to obviate for a complex invocation of dd(1). - -xargs(1) now supports a -J replstr option that allows the user to tell -xargs to insert the data read from standard input at a specific point -in the command line arguments rather than at the end. - -apmd(8) now supports monitoring of the battery state via the -apm_battery configuration directive. - -telnet(1) now does autologin and encryption by default; a new -y -option turns off encryption. - -The Forth Inspired Command Language used in the boot loader has been -updated to 2.05. - - -2. Supported Configurations ---------------------------- - -FreeBSD currently runs on a wide variety of ISA, VLB, EISA, MCA 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. - -What follows is a list of all peripherals currently known to work with -FreeBSD. Other configurations may also work, we have simply not as yet -received confirmation of this. - -2.1. Disk Controllers ---------------------- -IDE -ATA - -Adaptec 1535 ISA SCSI controllers -Adaptec 154x series ISA SCSI controllers -Adaptec 164x series MCA SCSI controllers -Adaptec 174x series EISA SCSI controller in standard and enhanced mode. -Adaptec 274X/284X/2920C/294x/2950/3940/3950 (Narrow/Wide/Twin) series -EISA/VLB/PCI SCSI controllers. -Adaptec AIC7850, AIC7860, AIC7880, AIC789x, on-board SCSI controllers. -Adaptec 1510 series ISA SCSI controllers (not for bootable devices) -Adaptec 152x series ISA SCSI controllers -Adaptec AIC-6260 and AIC-6360 based boards, which includes the AHA-152x -and SoundBlaster SCSI cards. - -Adaptec 2100S, 2400A, 3200S, and 3400S SCSI RAID controllers. - -Adaptec FSA family RAID controllers: - Adaptec AAC-2622 - Adaptec AAC-364 - Adaptec AAC-3642 - Dell PERC 2/QC - Dell PERC 2/Si - Dell PERC 3/Di - Dell PERC 3/QC - Dell PERC 3/Si - HP NetRAID-4M - -AdvanSys SCSI controllers (all models). - -BusLogic MultiMaster controllers: - -[ Please note that BusLogic/Mylex "Flashpoint" adapters are NOT yet supported ] - -BusLogic MultiMaster "W" Series Host Adapters: - BT-948, BT-958, BT-958D -BusLogic MultiMaster "C" Series Host Adapters: - BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, BT-757C, BT-757CD, BT-545C, - BT-540CF -BusLogic MultiMaster "S" Series Host Adapters: - BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, BT-545S, BT-542D, BT-742A, - BT-542B -BusLogic MultiMaster "A" Series Host Adapters: - BT-742A, BT-542B - -AMI FastDisk controllers that are true BusLogic MultiMaster clones are also -supported. - -The Buslogic/Bustek BT-640 and Storage Dimensions SDC3211B and SDC3211F -Microchannel (MCA) bus adapters are also supported. - -DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, SmartCACHE IV and -SmartRAID IV SCSI/RAID controllers. - -DPT SmartRAID V and VI SCSI RAID controllers: - PM1554, PM2554, PM2654, PM2865, PM2754, PM3755, PM3757 - -AMI MegaRAID Express and Enterprise family RAID controllers: - MegaRAID Series 418 - MegaRAID Enterprise 1200 (Series 428) - MegaRAID Enterprise 1300 (Series 434) - MegaRAID Enterprise 1400 (Series 438) - MegaRAID Enterprise 1500 (Series 467) - MegaRAID Enterprise 1600 (Series 471) - MegaRAID Elite 1500 (Series 467) - MegaRAID Elite 1600 (Series 493) - MegaRAID Express 100 (Series 466WS) - MegaRAID Express 200 (Series 466) - MegaRAID Express 300 (Series 490) - MegaRAID Express 500 (Series 475) - Dell PERC - Dell PERC 2/SC - Dell PERC 2/DC - Dell PERC 3/DCL - HP NetRAID-1si - HP NetRAID-3si - HP Embedded NetRAID -Booting from these controllers is supported. - -Mylex DAC960 and DAC1100 RAID controllers with 2.x, 3.x, 4.x and 5.x -firmware: - DAC960P - DAC960PD - DAC960PDU - DAC960PL - DAC960PJ - DAC960PG - AcceleRAID 150 - AcceleRAID 250 - eXtremeRAID 1100 -Booting from these controllers is supported. EISA adapters are not -supported. - -Mylex PCI to SCSI RAID controllers with 6.x firmware: - AcceleRAID 160 - AcceleRAID 170 - AcceleRAID 352 - eXtremeRAID 2000 - eXtremeRAID 3000 -Compatible Mylex controllers not listed should work, but have not been -verified. - -3ware Escalade ATA RAID controllers. All members of the 5000, -6000, and 7000 series are supported. - -SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, 53C825a, -53C860, 53C875, 53C875j, 53C885, 53C895 and 53C896 PCI SCSI controllers: - ASUS SC-200 - Data Technology DTC3130 (all variants) - Diamond FirePort (all) - NCR cards (all) - Symbios cards (all) - Tekram DC390W, 390U and 390F - Tyan S1365 - -NCR 53C500 based PC-Card SCSI host adapters: - IO DATA PCSC-DV - KME KXLC002(TAXAN ICD-400PN, etc.), KXLC004 - Macnica Miracle SCSI-II mPS110 - Media Intelligent MSC-110, MSC-200 - NEC PC-9801N-J03R - New Media Corporation BASICS SCSI - Qlogic Fast SCSI - RATOC REX-9530, REX-5572 (as SCSI only) - -TMC 18C30, 18C50 based ISA/PC-Card SCSI host adapters: - Future Domain SCSI2GO - IBM SCSI PCMCIA Card - ICM PSC-2401 SCSI - Melco IFC-SC - RATOC REX-5536, REX-5536AM, REX-5536M, REX-9836A - -Qlogic Controllers and variants: - Qlogic 1020, 1040 SCSI and Ultra SCSI host adapters - Qlogic 1240 dual Ultra SCSI controllers - Qlogic 1080 Ultra2 LVD and 1280 Dual Ultra2 LVD controllers - Qlogic 12160 Ultra3 LVD controllers - Qlogic 2100 and Qlogic 2200 Fibre Channel SCSI controllers - Performance Technology SBS440 ISP1000 variants - Performance Technology SBS450 ISP1040 variants - Performance Technology SBS470 ISP2100 variants - Antares Microsystems P-0033 ISP2100 variants - -DTC 3290 EISA SCSI controller in 1542 emulation mode. - -Workbit Ninja SCSI-3 based PC-Card SCSI host adapters: - Alpha-Data AD-PCS201 - IO DATA CBSC16 - -With all supported SCSI controllers, full support is provided for -SCSI-I & SCSI-II peripherals, including hard disks, optical disks, -tape drives (including DAT and 8mm Exabyte), medium changers, processor -target devices and CDROM drives. WORM devices that support CDROM commands -are supported for read-only access by the CDROM driver. WORM/CD-R/CD-RW -writing support is provided by cdrecord, which is in the ports tree. - -The following CD-ROM type systems are supported at this time: -(cd) SCSI interface (also includes ProAudio Spectrum and - SoundBlaster SCSI) -(matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary - interface (562/563 models) -(scd) Sony proprietary interface (all models) -(acd) ATAPI IDE interface - -The following drivers were supported under the old SCSI subsystem, but are -NOT YET supported under the new CAM SCSI subsystem: - - NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller. - - UltraStor 14F, 24F and 34F SCSI controllers. - - Seagate ST01/02 SCSI controllers. - - Future Domain 8xx/950 series SCSI controllers. - - WD7000 SCSI controller. - - [ Note: There is work-in-progress to port the UltraStor driver to - the new CAM SCSI framework, but no estimates on when or if it will - be completed. ] - -Unmaintained drivers, they might or might not work for your hardware: - - (mcd) Mitsumi proprietary CD-ROM interface (all models) - - -2.2. Ethernet cards -------------------- - -Adaptec Duralink PCI Fast Ethernet adapters based on the Adaptec -AIC-6915 Fast Ethernet controller chip, including the following: - ANA-62011 64-bit single port 10/100baseTX adapter - ANA-62022 64-bit dual port 10/100baseTX adapter - ANA-62044 64-bit quad port 10/100baseTX adapter - ANA-69011 32-bit single port 10/100baseTX adapter - ANA-62020 64-bit single port 100baseFX adapter - -Allied-Telesis AT1700 and RE2000 cards - -Alteon Networks PCI Gigabit Ethernet NICs based on the Tigon 1 and Tigon 2 -chipsets, including the following: - Alteon AceNIC (Tigon 1 and 2) - 3Com 3c985-SX (Tigon 1 and 2) - Netgear GA620 (Tigon 2) - Silicon Graphics Gigabit Ethernet - DEC/Compaq EtherWORKS 1000 - NEC Gigabit Ethernet - Farallon PN9000SX - Asante PCI 1000BASE-SX Gigabit Ethernet Adapter - Asante GigaNIX1000T Gigabit Ethernet Adapter - -AMD PCnet/PCI (79c970 & 53c974 or 79c974) -AMD PCnet/FAST, PCnet/FAST+, PCnet/FAST III, PCnet/PRO, -PCnet/Home, and HomePNA. - -SMC Elite 16 WD8013 Ethernet interface, and most other WD8003E, -WD8003EBT, WD8003W, WD8013W, WD8003S, WD8003SBT and WD8013EBT -based clones. SMC Elite Ultra. SMC Etherpower II. - -RealTek 8129/8139 Fast Ethernet NICs including the following: - Allied Telesyn AT2550 - Allied Telesyn AT2500TX - Genius GF100TXR (RTL8139) - NDC Communications NE100TX-E - OvisLink LEF-8129TX - OvisLink LEF-8139TX - Netronix Inc. EA-1210 NetEther 10/100 - KTX-9130TX 10/100 Fast Ethernet - Accton "Cheetah" EN1207D (MPX 5030/5038; RealTek 8139 clone) - SMC EZ Card 10/100 PCI 1211-TX - -Lite-On 82c168/82c169 PNIC Fast Ethernet NICs including the following: - LinkSys EtherFast LNE100TX - NetGear FA310-TX Rev. D1 - Matrox FastNIC 10/100 - Kingston KNE110TX - -Macronix 98713, 98713A, 98715, 98715A and 98725 Fast Ethernet NICs - Accton EN1217 (98715A) - Adico AE310TX (98715A) - Compex RL100-TX - CNet Pro120A (98713 or 98713A) - CNet Pro120B (98715) - NDC Communications SFA100A (98713A) - SVEC PN102TX (98713) - -Macronix/Lite-On PNIC II LC82C115 Fast Ethernet NICs including the following: - LinkSys EtherFast LNE100TX Version 2 - -Winbond W89C840F Fast Ethernet NICs including the following: - Trendware TE100-PCIE - -VIA Technologies VT3043 "Rhine I" and VT86C100A "Rhine II" Fast Ethernet -NICs including the following: - Hawking Technologies PN102TX - D-Link DFE-530TX - AOpen/Acer ALN-320 - -Silicon Integrated Systems SiS 900 and SiS 7016 PCI Fast Ethernet NICs - -National Semiconductor DP83815 Fast Ethernet NICs including the following: - NetGear FA311-TX - NetGear FA312-TX - -National Semiconductor DP83820 and DP83821 Gigabit Ethernet NICs including -the following: - D-Link DGE-500T - SMC EZ Card 1000 (SMC9462TX) - Asante FriendlyNet GigaNIC 1000TA and 1000TPC - Addtron AEG320T - -Sundance Technologies ST201 PCI Fast Ethernet NICs including -the following: - D-Link DFE-550TX - -SysKonnect SK-984x PCI Gigabit Ethernet cards including the following: - SK-9841 1000baseLX single mode fiber, single port - SK-9842 1000baseLX single mode fiber, dual port - SK-9843 1000baseSX multimode fiber, single port - SK-9844 1000baseSX multimode fiber, dual port - SK-9821 1000baseT copper, single port - SK-9822 1000baseT copper, dual port - -Texas Instruments ThunderLAN PCI NICs, including the following: - Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port - Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP - Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC - Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX UTP - Racore 8165 10/100baseTX - Racore 8148 10baseT/100baseTX/100baseFX multi-personality - -ADMtek Inc. AL981-based PCI Fast Ethernet NICs -ADMtek Inc. AN985-based PCI Fast Ethernet NICs -ADMtek Inc. AN986-based USB Ethernet NICs including the following: - LinkSys USB100TX - Billionton USB100 - Melco Inc. LUA-TX - D-Link DSB-650TX - SMC 2202USB - -CATC USB-EL1210A-based USB Ethernet NICs including the following: - CATC Netmate - CATC Netmate II - Belkin F5U111 - -Kawasaki LSI KU5KUSB101B-based USB Ethernet NICs including -the following: - LinkSys USB10T - Entrega NET-USB-E45 - Peracom USB Ethernet Adapter - 3Com 3c19250 - ADS Technologies USB-10BT - ATen UC10T - Netgear EA101 - D-Link DSB-650 - SMC 2102USB - SMC 2104USB - Corega USB-T - -ASIX Electronics AX88140A PCI NICs, including the following: - Alfa Inc. GFC2204 - CNet Pro110B - -DEC DC21040, DC21041, or DC21140 based NICs (SMC Etherpower 8432T, DE245, etc) - -DEC/Intel 21143 based Fast Ethernet NICs, including the following: - DEC DE500-BA - Compaq Presario 7900 series built-in Ethernet - D-Link DFE-570TX - Kingston KNE100TX - LinkSys EtherFast 10/100 Instant GigaDrive built-in Ethernet - -Davicom DM9100 and DM9102 PCI Fast Ethernet NICs, including the -following: - Jaton Corporation XpressNet - -Fujitsu MB86960A/MB86965A, including the following: - CONTEC C-NET(PC)C Ethernet - Eiger Labs EPX-10BT - Fujitsu FMV-J182, FMV-J182A, MBH10302, MBH10303 Ethernet PCMCIA - Fujitsu Towa LA501 Ethernet - HITACHI HT-4840-11 - NextCom J Link NC5310 - RATOC REX-5588, REX-9822, REX-4886, REX-R280 - TDK LAK-CD021, LAK-CD021A, LAK-CD021BX - -HP PC Lan+ cards (model numbers: 27247B and 27252A). - -Intel EtherExpress 16 -Intel EtherExpress Pro/10 -Intel EtherExpress Pro/100B PCI Fast Ethernet -Intel InBusiness 10/100 PCI Network Adapter -Intel PRO/100+ Management Adapter - -Isolan AT 4141-0 (16 bit) -Isolink 4110 (8 bit) - -Novell NE1000, NE2000, and NE2100 Ethernet interface. - -PCI network cards emulating the NE2000: RealTek 8029, NetVin 5000, -Winbond W89C940, Surecom NE-34, VIA VT86C926. - -3Com 3C501 cards - -3Com 3C503 Etherlink II - -3Com 3c505 Etherlink/+ - -3Com 3C507 Etherlink 16/TP - -3Com 3C509, 3C529 (MCA), 3C579, -3C589/589B/589C/589D/589E/XE589ET/574TX/574B (PC-card/PCMCIA), -3C590/592/595/900/905/905B/905C PCI, -3C556/556B MiniPCI, -3C575TX/575B/XFE575BT/575C/656/656B/656C Cardbus, -and EISA (Fast) Etherlink III / (Fast) Etherlink XL - -3Com 3c980/3c980B Fast Etherlink XL server adapter - -3Com 3cSOHO100-TX OfficeConnect adapter - -Crystal Semiconductor CS89x0-based NICs, including: - IBM Etherjet ISA - -NE2000 compatible PC-Card (PCMCIA) Ethernet/FastEthernet cards, -including the following: - AR-P500 Ethernet card - Accton EN2212/EN2216/UE2216(OEM) - Allied Telesis CentreCOM LA100-PCM_V2 - AmbiCom 10BaseT card - BayNetworks NETGEAR FA410TXC Fast Ethernet - CNet BC40 adapter - COREGA Ether PCC-T/EtherII PCC-T/FEther PCC-TXF/PCC-TXD - Compex Net-A adapter - CyQ've ELA-010 - D-Link DE-650/660 - Danpex EN-6200P2 - ELECOM Laneed LD-CDL/TX - IO DATA PCLATE,PCET/TX-R - IBM Creditcard Ethernet I/II - IC-CARD Ethernet/IC-CARD+ Ethernet - Linksys EC2T/PCMPC100,EtherFast 10/100 PC Card (PCMPC100 V2) - Melco LPC-T/LPC2-T/LPC2-CLT/LPC2-TX/LPC3-TX/LPC3-CLX - NDC Ethernet Instant-Link - National Semiconductor InfoMover NE4100 - Network Everywhere Ethernet 10BaseT PC Card - Planex FNW-3600-T - Socket LP-E - Surecom EtherPerfect EP-427 - TDK LAK-CD031,Grey Cell GCS2000 Ethernet Card - Telecom Device SuperSocket RE450T - -Megahertz X-Jack Ethernet PC-Card CC-10BT - -Xircom X3201 (Cardbus) based Ethernet cards, -including the following: - IBM EtherJet Cardbus Adapter - Intel PRO/100 Mobile Cardbus (versions that uses the X3201 chipset) - Xircom Cardbus Realport - Xircom Cardbus Ethernet 10/100 - Xircom Cardbus Ethernet II 10/100 - -Xircom CreditCard adapters(16bit) and workalikes - Accton EN2226/Fast EtherCard (16-bit verison) - Compaq Netelligent 10/100 PC Card - Intel EtherExpress PRO/100 Mobile Adapter (16-bit verison) - Xircom 10/100 Network PC Card adapter. - Xircom Realport card + modem(Ethernet part) - Xircom CreditCard Ethernet 10/100 - Xircom CreditCard 10Base-T "CreditCard Ethernet Adaptor IIps" (PS-CE2-10) - Xircom CreditCard Ethernet 10/100 + modem (Ethernet part) - -National Semiconductor DP8393X (SONIC) Ethernet cards - NEC PC-9801-83, -84, -103, and -104 - NEC PC-9801N-25 and -J02R - - -2.3. FDDI ---------- - -DEC FDDI (DEFPA/DEFEA) NICs - - -2.4. ATM --------- - - o ATM Host Interfaces - - FORE Systems, Inc. PCA-200E ATM PCI Adapters - - Efficient Networks, Inc. ENI-155p ATM PCI Adapters - - o ATM Signaling Protocols - - The ATM Forum UNI 3.1 signaling protocol - - The ATM Forum UNI 3.0 signaling protocol - - The ATM Forum ILMI address registration - - FORE Systems' proprietary SPANS signaling protocol - - Permanent Virtual Channels (PVCs) - - o IETF "Classical IP and ARP over ATM" model - - RFC 1483, "Multiprotocol Encapsulation over ATM Adaptation Layer 5" - - RFC 1577, "Classical IP and ARP over ATM" - - RFC 1626, "Default IP MTU for use over ATM AAL5" - - RFC 1755, "ATM Signaling Support for IP over ATM" - - RFC 2225, "Classical IP and ARP over ATM" - - RFC 2334, "Server Cache Synchronization Protocol (SCSP)" - - Internet Draft draft-ietf-ion-scsp-atmarp-00.txt, - "A Distributed ATMARP Service Using SCSP" - - o ATM Sockets interface - - -2.5. Misc ---------- - -AST 4 port serial card using shared IRQ. - -ARNET 8 port serial card using shared IRQ. -ARNET (now Digiboard) Sync 570/i high-speed serial. - -Boca BB1004 4-Port serial card (Modems NOT supported) -Boca IOAT66 6-Port serial card (Modems supported) -Boca BB1008 8-Port serial card (Modems NOT supported) -Boca BB2016 16-Port serial card (Modems supported) - -Comtrol Rocketport card. - -Cyclades Cyclom-y Serial Board. - -STB 4 port card using shared IRQ. - -SDL Communications Riscom/8 Serial Board. -SDL Communications RISCom/N2 and N2pci high-speed sync serial boards. - -Stallion multiport serial boards: EasyIO, EasyConnection 8/32 & 8/64, -ONboard 4/16 and Brumby. - -Specialix SI/XIO/SX ISA, EISA and PCI serial expansion cards/modules. - -Advance Asound 100, 110 and Logic ALS120, ALS4000 -C-Media CMI-8x38 -Crystal Semiconductor CS461x/462x/428x -Crystal Semiconductor CS4281 -ENSONIQ AudioPCI ES1370/1371 -ESS ES1868, ES1869, ES1879 and ES1888 -ESS Maestro-1, Maestro-2, and Maestro-2E -ESS Maestro-3/Allegro -ForteMedia fm801 -Gravis UltraSound MAX/PnP -MSS/WSS Compatible DSPs -NeoMagic 256AV/ZX -OPTi 931/82C931 -S3 Sonicvibes -SoundBlaster, Soundblaster Pro, Soundblaster AWE-32, Soundblaster AWE-64 -Trident 4DWave DX/NX -VIA Technologies VT82C686A -Yamaha DS1 and DS1e -(newpcm driver) - -Connectix QuickCam -Matrox Meteor Video frame grabber -Creative Labs Video Spigot frame grabber -Cortex1 frame grabber -Hauppauge Wincast/TV boards (PCI) -STB TV PCI -Intel Smart Video Recorder III -Various Frame grabbers based on Brooktree Bt848 / Bt878 chip. - -HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R drives. - -PS/2 mice - -Standard PC Joystick - -X-10 power controllers - -GPIB and Transputer drivers. - -Genius and Mustek hand scanners. - -Xilinx XC6200 based reconfigurable hardware cards compatible with -the HOT1 from Virtual Computers (www.vcc.com) - -Support for Dave Mills experimental Loran-C receiver. - -Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA standard speed -(2Mbps) and turbo speed (6Mbps) wireless network adapters and workalikes -NCR WaveLAN/IEEE 802.11 -3COM 3crwe737A AirConnect Wireless LAN PC Card -Addtron AWA100 -Cabletron RoamAbout 802.11 DS -Compaq WL100 -Corega KK Wireless LAN PCC-11, PCCA-11 -Laneed Wireless card -ELECOM Air@Hawk/LD-WL11/PCC -Farallon Skyline 11Mbps Wireless -ICOM SL-1100 -IO Data WN-B11/PCM -Melco Airconnect WLI-PCM-L11 -NEC Wireless Card CMZ-RT-WP, PC-WL/11C, PK-WL001 -PLANEX GeoWave/GW-NS110 -TDK LAK-CD011WL -Note: the ISA versions of these adapters are actually PCMCIA cards -combined with an ISA to PCMCIA bridge card, so both kinds of devices -work with the same driver. - -Aironet 4500/4800 series 802.11 wireless adapters. The PCMCIA, -PCI and ISA adapters are all supported. -Cisco Systems Aironet 340 Series (includes 340, 341, and 342 models) -11Mbps 802.11 wireless NIC - -Webgear Aviator 2.4GHz wireless adapters. - -AcerISDN P10 ISA PnP (experimental) -Asuscom ISDNlink 128K ISA -AVM A1 -AVM Fritz!Card classic -AVM Fritz!Card PnP -AVM Fritz!Card PCI -Creatix ISDN-S0 -Creatix ISDN-S0 P&P -Dr. Neuhaus Niccy Go@ and compatibles -Dynalink IS64PH -ELSA PCC-16 -ELSA QuickStep 1000pro ISA -ELSA MicroLink ISDN/PCI -ELSA QuickStep 1000pro PCI -ITK ix1 Micro ( < V.3, non-PnP version ) -Sedlbauer Win Speed -Siemens I-Surf 2.0 -TELEINT ISDN SPEED No.1 (experimental) -Teles S0/8 -Teles S0/16 -Teles S0/16.3 -Teles S0/16.3 PnP -Teles 16.3c ISA PnP (experimental) -USRobotics Sportster ISDN TA intern -Winbond W6692 based PCI cards - -Toshiba Mobile HDD MEHDD20A (Type II) - -Panasonic Flash ATA BN-040ABP3 - -Hewlett Packard M820e (CD-writer) - -FAX-Modem/PC-Card -Melco IGM-PCM56K/IGM-PCM56KH -Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD terminal) - -PHS Data Communication Card/PC-Card -NTT DoCoMo P-in Comp@ct -Panasonic KX-PH405 -SII MC-P200 - - -3. Obtaining FreeBSD --------------------- - -You may obtain FreeBSD in a variety of ways: - - -3.1. FTP/Mail -------------- - -You can ftp FreeBSD and any or all of its optional packages from -`ftp.FreeBSD.org' - the official FreeBSD release site. - -For other locations that mirror the FreeBSD software see the file -MIRROR.SITES. Please ftp the distribution from the site closest (in -networking terms) to you. Additional mirror sites are always welcome! -Contact freebsd-admin@FreeBSD.org for more details if you'd like to -become an official mirror site. - -If you do not have access to the Internet and electronic mail is your -only recourse, then you may still fetch the files by sending mail to -`ftpmail@ftpmail.vix.com' - putting the keyword "help" in your message -to get more information on how to fetch files using this mechanism. -Please do note, however, that this will end up sending many *tens of -megabytes* through the mail and should only be employed as an absolute -LAST resort! - - -3.2. CDROM ----------- - -FreeBSD 4.x-RELEASE and 3.x-RELEASE CDs may be ordered on CDROM from: - - BSDi / Walnut Creek CDROM - 4041 Pike Lane, Suite D - Concord CA 94520 - USA - +1-800-786-9907, +1-925-674-0783, +1-925-674-0821 (FAX) - -Or via the Internet from orders@cdrom.com or http://www.cdrom.com. -Their current catalog can be obtained via ftp from: - - ftp://ftp.cdrom.com/cdrom/catalog - -Cost per -RELEASE CD is $39.95 or $24.95 with a FreeBSD subscription. -FreeBSD SNAPshot CDs, when available, are $39.95 or $14.95 with a -FreeBSD-SNAP subscription (-RELEASE and -SNAP subscriptions are entirely -separate). With a subscription, you will automatically receive updates as -they are released. Your credit card will be billed when each disk is -shipped and you may cancel your subscription at any time without further -obligation. - -Shipping (per order not per disc) is $5 in the US, Canada or Mexico -and $9.00 overseas. They accept Visa, Mastercard, Discover, American -Express or checks in U.S. Dollars and ship COD within the United -States. California residents please add 8.25% sales tax. - -Should you be dissatisfied for any reason, the CD comes with an -unconditional return policy. - - -4. Upgrading from previous releases of FreeBSD ----------------------------------------------- - -If you're upgrading from a previous release of FreeBSD, most likely -it's 3.0 and there may be some issues affecting you, depending -of course on your chosen method of upgrading. There are two popular -ways of upgrading FreeBSD distributions: - - o Using sources, via /usr/src - o Using sysinstall's (binary) upgrade option. - -Please read the UPGRADE.TXT file for more information, preferably -before beginning an upgrade. - - -5. Reporting problems, making suggestions, submitting code. ------------------------------------------------------------ -Your suggestions, bug reports and contributions of code are always -valued - please do not hesitate to report any problems you may find -(preferably with a fix attached, if you can!). - -The preferred method to submit bug reports from a machine with -Internet mail connectivity is to use the send-pr command or use the CGI -script at http://www.FreeBSD.org/send-pr.html. Bug reports -will be dutifully filed by our faithful bugfiler program and you can -be sure that we'll do our best to respond to all reported bugs as soon -as possible. Bugs filed in this way are also visible on our WEB site -in the support section and are therefore valuable both as bug reports -and as "signposts" for other users concerning potential problems to -watch out for. - -If, for some reason, you are unable to use the send-pr command to -submit a bug report, you can try to send it to: - - freebsd-bugs@FreeBSD.org - -Note that send-pr itself is a shell script that should be easy to move -even onto a totally different system. We much prefer if you could use -this interface, since it make it easier to keep track of the problem -reports. However, before submitting, please try to make sure whether -the problem might have already been fixed since. - - -Otherwise, for any questions or tech support issues, please send mail to: - - freebsd-questions@FreeBSD.org - - -If you're tracking the -current development efforts, you should -definitely join the -current mailing list, in order to keep abreast -of recent developments and changes that may affect the way you -use and maintain the system: - - freebsd-current@FreeBSD.org - - -Additionally, being a volunteer effort, we are always happy to have -extra hands willing to help - there are already far more desired -enhancements than we'll ever be able to manage by ourselves! To -contact us on technical matters, or with offers of help, please send -mail to: - - freebsd-hackers@FreeBSD.org - - -Please note that these mailing lists can experience *significant* -amounts of traffic and if you have slow or expensive mail access and -are only interested in keeping up with significant FreeBSD events, you -may find it preferable to subscribe instead to: - - freebsd-announce@FreeBSD.org - - -All of the mailing lists can be freely joined by anyone wishing -to do so. Send mail to MajorDomo@FreeBSD.org and include the keyword -`help' on a line by itself somewhere in the body of the message. This -will give you more information on joining the various lists, accessing -archives, etc. There are a number of mailing lists targeted at -special interest groups not mentioned here, so send mail to majordomo -and ask about them! - - -6. Acknowledgments ------------------- - -FreeBSD represents the cumulative work of many hundreds, if not -thousands, of individuals from around the world who have worked very -hard to bring you this release. For a complete list of FreeBSD -project staffers, please see: - - http://www.FreeBSD.org/handbook/staff.html - -or, if you've loaded the doc distribution: - - file:/usr/share/doc/handbook/staff.html - -Special thanks also go to the many thousands of FreeBSD users and testers -all over the world, without whom this release simply would not have been -possible. - - The FreeBSD Project - -$FreeBSD$ |
