Stage 1: Move a bunch of docs out from under sysinstall and other - src

diff options


context:
space:
mode:

author	Jordan K. Hubbard <jkh@FreeBSD.org>	1998-11-03 03:21:09 +0000
committer	Jordan K. Hubbard <jkh@FreeBSD.org>	1998-11-03 03:21:09 +0000
commit	d7d6f7335d90517f9f0a1a69add52e6a3bf82602 (patch)
tree	e37351b16ad8fedb92ab8105e77fbf336c37770f /release/sysinstall
parent	58541533dd70f88309f214fef493dca646b0aa8f (diff)

Notes

Diffstat (limited to 'release/sysinstall')

-rw-r--r--

release/sysinstall/help/XF86.hlp

1580

-rw-r--r--

release/sysinstall/help/hardware.hlp

514

-rw-r--r--

release/sysinstall/help/install.hlp

513

-rw-r--r--

release/sysinstall/help/readme.hlp

110

-rw-r--r--

release/sysinstall/help/relnotes.hlp

514

-rw-r--r--

release/sysinstall/help/trouble.hlp

374

-rw-r--r--

release/sysinstall/help/upgrade.hlp

168

7 files changed, 0 insertions, 3773 deletions

diff --git a/release/sysinstall/help/XF86.hlp b/release/sysinstall/help/XF86.hlp
deleted file mode 100644
index 4757fb079c26..000000000000
--- a/release/sysinstall/help/XF86.hlp
+++ /dev/null

@@ -1,1580 +0,0 @@

- README for XFree86[tm] 3.3.2.3

- The XFree86 Project, Inc

- 20 July 1998

- Abstract

- XFree86 is a port of X11R6.3 that supports several Unix and Unix-like

- operating systems on Intel and other platforms. This release is a

- maintenance release, fixing bugs found in XFree86 3.3.1. The release

- is available as source patches against the X Consortium X11R6.3 code

- and the XFree86 3.3.1 release. Binary distributions for many archi-

- tectures are also available.

-[ FreeBSD Project Note: 3.3.2.3 is a security release relative to 3.3.2.

- Where 3.3.2 is referred to below, understand that "3.3.2.3" is actually

- being referred to. ]

-1. What's new in XFree86 3.3.2

-For a summary of new features in this release, please refer to the RELNOTES

-file. For a detailed list of changes, refer to the CHANGELOG file in the

-source distribution.

-2. Systems XFree86 has been tested on

-Note: Not all systems listed here have been tested with the current release.

- SVR4.0:

- o Esix: 4.0.3A, 4.0.4, 4.0.4.1

- o Microport: 2.2, 3.1, 4.1, 4.2

- o Dell: 2.1, 2.2, 2.2.1

- o UHC: 2.0, 3.6

- o Consensys: 1.2

- o MST: 4.0.3 (Load 2.07 and Load 3.02)

- o ISC: 4.0.3

- o AT&T: 2.1, 4.0

-README for XFree86[tm] 3.3.2

- o NCR: MP-RAS

- o SunSoft: Solaris x86 2.1, 2.4, 2.5, 2.5.1, 2.6

- o PANIX 5.0 for AT

- SVR4.2:

- o Consensys

- o Novell UnixWare

- SVR3:

- o ISC: 3.0, 4.0, 4.1

- Others:

- o NetBSD 1.0, 1.1, 1.2, 1.2.1, 1.3

- o OpenBSD 2.0, 2.1

- o FreeBSD 2.0.5, 2.1, 2.1.5, 2.1.6, 2.1.7, 2.1.7.1, 2.2, 2.2.1,

- 2.2.2, 2.2.5, 3.0-current

- o Linux (Intel x86, DEC Alpha/AXP and m68k)

- o LynxOS AT 2.3.0, 2.4.0, 2.5.0

- o LynxOS microSPARC 2.4.0, 2.5.0

- o LynxOS PowerPC 2.4.0, 2.5.0

- o OS/2 Warp 3 FP5/17/22, Warp 4 -/FP1

- PC98:

- o FreeBSD(98) 2.0.5, 2.1, 2.1.5, 2.1.7.1, 2.2, 2.2.1, 2.2.2,

- 2.2.5

- o NetBSD/pc98 (based on NetBSD 1.2, 1.2.1)

- o PANIX 5.0 for 98

- o Linux/98

-3. Supported video-card chip-sets

-At this time, XFree86 3.3.2 supports the following chipsets:

-README for XFree86[tm] 3.3.2

- Ark Logic

- ARK1000PV, ARK1000VL, ARK2000PV, ARK2000MT

- Alliance

- AP6422, AT24

- ATI

- 18800, 18800-1, 28800-2, 28800-4, 28800-5, 28800-6, 68800-3,

- 68800-6, 68800AX, 68800LX, 88800GX-C, 88800GX-D, 88800GX-E,

- 88800GX-F, 88800CX, 264CT, 264ET, 264VT, 264GT, 264VT-B, 264VT3,

- 264GT-B, 264GT3 (this list includes the Mach8, Mach32, Mach64, 3D

- Rage, 3D Rage II and 3D Rage Pro)

- Avance Logic

- ALG2101, ALG2228, ALG2301, ALG2302, ALG2308, ALG2401

- Chips & Technologies

- 65520, 65530, 65540, 65545, 65520, 65530, 65540, 65545, 65546,

- 65548, 65550, 65554, 65555, 68554, 64200, 64300

- Cirrus Logic

- CLGD5420, CLGD5422, CLGD5424, CLGD5426, CLGD5428, CLGD5429,

- CLGD5430, CLGD5434, CLGD5436, CLGD5440, CLGD5446, CLGD5462,

- CLGD5464, CLGD5465, CLGD5480, CLGD6205, CLGD6215, CLGD6225,

- CLGD6235, CLGD6410, CLGD6412, CLGD6420, CLGD6440, CLGD7541(*),

- CLGD7543(*), CLGD7548(*), CLGD7555(*)

- Digital Equipment Corporation

- TGA

- Compaq

- AVGA

- Genoa

- GVGA

- IBM

- 8514/A (and true clones), XGA-2

- IIT

- AGX-014, AGX-015, AGX-016

- Matrox

- MGA2064W (Millennium), MGA1064SG (Mystique and Mystique 220),

- MGA2164W (Millennium II PCI and AGP)

- MX

- MX68000(*), MX680010(*)

- NCR

- 77C22(*), 77C22E(*), 77C22E+(*)

- Number Nine

- I128 (series I and II), Revolution 3D (T2R)

-README for XFree86[tm] 3.3.2

- NVidia/SGS Thomson

- NV1, STG2000, RIVA128

- OAK

- OTI067, OTI077, OTI087

- RealTek

- RTG3106(*)

- S3

- 86C911, 86C924, 86C801, 86C805, 86C805i, 86C928, 86C864, 86C964,

- 86C732, 86C764, 86C765, 86C767, 86C775, 86C785, 86C868, 86C968,

- 86C325, 86C357, 86C375, 86C375, 86C385, 86C988, 86CM65, 86C260

- SiS

- 86C201, 86C202, 86C205

- Tseng

- ET3000, ET4000AX, ET4000/W32, ET4000/W32i, ET4000/W32p, ET6000,

- ET6100

- Trident

- TVGA8800CS, TVGA8900B, TVGA8900C, TVGA8900CL, TVGA9000, TVGA9000i,

- TVGA9100B, TVGA9200CXR, Cyber9320(*), TVGA9400CXi, TVGA9420,

- TGUI9420DGi, TGUI9430DGi, TGUI9440AGi, TGUI9660XGi, TGUI9680, Pro-

- Vidia 9682, ProVidia 9685(*), Cyber 9382, Cyber 9385, Cyber 9388,

- 3DImage975(PCI), 3DImage985(AGP), Cyber 9397, Cyber 9520

- Video 7/Headland Technologies

- HT216-32(*)

- Weitek

- P9000

- Western Digital/Paradise

- PVGA1

- Western Digital

- WD90C00, WD90C10, WD90C11, WD90C24, WD90C24A, WD90C30, WD90C31,

- WD90C33

-(*) Note, chips marked in this way have either limited support or the drivers

-for them are not actively maintained.

-All of the above are supported in both 256 color, and some are supported in

-mono and 16 color modes, and some are supported an higher color depths.

-Refer to the chipset-specific README files (currently for TGA, Matrox, Mach32,

-Mach64, NVidia, Oak, P9000, S3 (except ViRGE), S3 ViRGE, SiS, Video7, Western

-Digital, Tseng (W32), Tseng (all), AGX/XGA, ARK, ATI (SVGA server), Chips and

-Technologies, Cirrus, Trident) for more information about using those chipsets.

-The monochrome server also supports generic VGA cards, using 64k of video mem-

-ory in a single bank, the Hercules monochrome card, the Hyundai HGC1280, Sigma

-README for XFree86[tm] 3.3.2

-LaserView, Visa and Apollo monochrome cards.

-The VGA16 server supports memory banking with the ET4000, Trident, ATI, NCR,

-OAK and Cirrus 6420 chipsets allowing virtual display sizes up to about

-1600x1200 (with 1MB of video memory). For other chipsets the display size is

-limited to approximately 800x600.

-Notes: The Diamond SpeedStar 24 (and possibly some SpeedStar+) boards are NOT

-supported, even though they use the ET4000.

-The Weitek 9100 and 9130 chipsets are not supported (these are used on the Dia-

-mond Viper Pro and Viper SE boards). Most other Diamond boards will work with

-this release of XFree86. Diamond is actively supporting The XFree86 Project,

-Inc.

-3DLabs GLINT, Permedia and Permedia 2 support could unfortunately not be

-included in XFree86 3.3.2 since there are open issues regarding the documenta-

-tion and whether or not they were provided to us under NDA.

-S.u.S.E. will continue to make available binary only servers for these cards.

-These servers can be freely distributed just like XFree86, but sources cannot

-be made available. S.u.S.E. will continue to develop these servers and will

-continue to try to donate the code back to XFree86. For the time being S.u.S.E.

-will try to not only make Linux binaries available, but binaries for other

-platforms as well.

-Please contact x@suse.de with further questions. You can find the servers at

-http://www.suse.de/XSuSE/XSuSE_E.html

-4. Where to get more information

-Additional documentation is available in the XFree86(1), XF86Config(4/5),

-XF86_SVGA(1), XF86_Mono(1), XF86_VGA16(1), XF86_Accel(1), XF86Setup(1) and

-xvidtune(1) manual pages. In addition, several README files and tutorial docu-

-ments are provided. These are available in /usr/X11R6/lib/X11/doc in the

-binary distributions, and in xc/programs/Xserver/hw/xfree86/doc in the source

-distribution.

-The files QuickStart.doc and README.Config should be consulted for information

-on how to set up the XFree86 servers. All supplied documents, manual pages,

-and the XFree86 FAQ <URL:http://www.XFree86.org/FAQ> should be read before con-

-tacting the XFree86 team for assistance.

-Documentation on SVGA driver development can be found in the directory

-/usr/X11R6/lib/Server/VGADriverDoc in the binary distribution, and in the

-directory xc/programs/Xserver/hw/xfree86/VGADriverDoc in the source distribu-

-tion.

-If you are totally at a loss, you can contact the XFree86 Support Team at

-<XFree86@XFree86.Org>. Before doing so, please make sure that you are using

-the latest release of XFree86. Check the versions listed on

-ftp://ftp.xfree86.org/pub/XFree86.

-README for XFree86[tm] 3.3.2

-There is a Usenet news group comp.windows.x.i386unix that contains mostly dis-

-cussions about XFree86 and related topics. Many questions can be answered

-there.

-5. Thanks

-The XFree86 Project wants to express a special thanks to S.u.S.E. GmbH, Fuerth,

-Germany, for the long and successful cooperation over the last few years.

-S.u.S.E. GmbH at one point hired our Core Team member and Vice President Dirk

-Hohndel as an employee and allowed him to work more or less full time on

-XFree86 for almost nine months. S.u.S.E. continues to be a significant source

-of input and help to XFree86. This manifested itself in the XSuSE series of X

-servers that have all except for the GLINT server (due to unresolved legal

-issues) been integrated into XFree86 3.3.2.

-6. Credits

-XFree86 was originally put together by:

- o David Dawes <dawes@XFree86.org>

- o Glenn Lai <glenn@cs.utexas.edu>

- o Jim Tsillas <jtsilla@ccs.neu.edu>

- o David Wexelblat <dwex@XFree86.org>

-XFree86 support was integrated into the base X11R6 distribution by:

- o Stuart Anderson <anderson@metrolink.com>

- o Doug Anson <danson@lgc.com>

- o Gertjan Akkerman <akkerman@dutiba.twi.tudelft.nl>

- o Mike Bernson <mike@mbsun.mlb.org>

- o Robin Cutshaw <robin@XFree86.org>

- o David Dawes <dawes@XFree86.org>

- o Marc Evans <marc@XFree86.org>

- o Pascal Haible <haible@izfm.uni-stuttgart.de>

- o Matthieu Herrb <Matthieu.Herrb@laas.fr>

- o Dirk Hohndel <hohndel@XFree86.org>

- o David Holland <davidh@use.com>

-README for XFree86[tm] 3.3.2

- o Alan Hourihane <alanh@fairlite.demon.co.uk>

- o Jeffrey Hsu <hsu@soda.berkeley.edu>

- o Glenn Lai <glenn@cs.utexas.edu>

- o Ted Lemon <mellon@ncd.com>

- o Rich Murphey <rich@XFree86.org>

- o Hans Nasten <nasten@everyware.se>

- o Mark Snitily <mark@sgcs.com>

- o Randy Terbush <randyt@cse.unl.edu>

- o Jon Tombs <tombs@XFree86.org>

- o Kees Verstoep <versto@cs.vu.nl>

- o Paul Vixie <paul@vix.com>

- o Mark Weaver <Mark_Weaver@brown.edu>

- o David Wexelblat <dwex@XFree86.org>

- o Philip Wheatley <Philip.Wheatley@ColumbiaSC.NCR.COM>

- o Thomas Wolfram <wolf@prz.tu-berlin.de>

- o Orest Zborowski <orestz@eskimo.com>

- 386BSD, FreeBSD, NetBSD support by:

- o Rich Murphey <Rich@XFree86.org>

- NetBSD, OpenBSD support by:

- o Matthieu Herrb <Matthieu.Herrb.@laas.fr>

- Original 386BSD port by:

- o Pace Willison,

- o Amancio Hasty Jr <hasty@netcom.com>

- Mach 386 support by:

- o Robert Baron <Robert.Baron@ernst.mach.cs.cmu.edu>

- Linux support by:

- o Orest Zborowski <orestz@eskimo.com>

-README for XFree86[tm] 3.3.2

- SCO Unix support by:

- o David McCullough <davidm@stallion.oz.au>

- Amoeba support by:

- o Kees Verstoep <versto@cs.vu.nl>

- Minix-386 support by:

- o Philip Homburg <philip@cs.vu.nl>

- OSF/1 support by:

- o Marc Evans <Marc@XFree86.org>

- BSD/OS support by:

- o Hans Nasten <nasten@everyware.se>,

- o Paul Vixie <paul@vix.com>

- Solaris support by:

- o Doug Anson <danson@lgc.com>,

- o David Holland <davidh@use.com>

- ISC SVR3 support by:

- o Michael Rohleder <michael.rohleder@stadt-frankfurt.de>

- LynxOS support by:

- o Thomas Mueller <tmueller@sysgo.de>

- OS/2 support by:

- o Holger Veit <Holger.Veit@gmd.de>

- o Sebastien Marineau <s521936@aix1.uottawa.ca>

- Linux shared libraries by:

- o Orest Zborowski <orestz@eskimo.com>,

- o Dirk Hohndel <hohndel@XFree86.org>

- PC98 support by:

- o Toyonori Fujiura <toyo@ibbsal.or.jp>,

- o Hiroyuki Aizu <aizu@jaist.ac.jp>,

-README for XFree86[tm] 3.3.2

- o Tetsuya Kakefuda <kakefuda@tag.iijnet.or.jp>,

- o Takefumi Tsukada <tsuka@linkt.imasy.or.jp>,

- o H.Komatsuzaki,

- o Naoki Katsurakawa <katsura@prc.tsukuba.ac.jp>,

- o Shuichiro Urata <s-urata@nmit.tmg.nec.co.jp>,

- o Yasuyuki Kato <yasuyuki@acaets0.anritsu.co.jp>,

- o Michio Jinbo <karl@spnet.ne.jp>,

- o Tatsuya Koike <koiket@focus.rim.or.jp>,

- o Koichiro Suzuki <s-koichi@nims.nec.co.jp>,

- o Tsuyoshi Tamaki <tamaki@sail.t.u-tokyo.ac.jp>,

- o Isao Ohishi <ohishi@hf.rim.or.jp>,

- o Kohji Ohishi <atena@njk.co.jp>,

- o Shin'ichi Yairo <QZR00522@niftyserve.or.jp>,

- o Kazuo Ito <ft4k-itu@asahi-net.or.jp>,

- o Jun Sakuma <i931361@jks.is.tsukuba.ac.jp>,

- o Shuichi Ueno <uenos@ppp.bekkoame.or.jp>,

- o Ishida Kazuo <ishidakz@obp.cl.nec.co.jp>,

- o Takaaki Nomura <amadeus@yk.rim.or.jp>,

- o Tadaaki Nagao <nagao@cs.titech.ac.jp>,

- o Minoru Noda <mnoda@cv.tottori-u.ac.jp>,

- o Naofumi Honda <honda@Kururu.math.hokudai.ac.jp>,

- o Akio Morita <amorita@bird.scphys.kyoto-u.ac.jp>,

- o Takashi Sakamoto <sakamoto@yajima.kuis.kyoto-u.ac.jp>,

- o Yasuhiro Ichikawa <cs94006@mbox.sist.ac.jp>,

- o Kazunori Ueno <jagarl@creator.club.or.jp>,

- o Yasushi Suzuki <suz@d2.bs1.fc.nec.co.jp>,

- o Satoshi Kimura <KFB03633@niftyserve.or.jp>,

-README for XFree86[tm] 3.3.2

- o Kazuhiko Uno <Kazuhiko.Uno@softvision.co.jp>,

- o Tomiharu Takigami <takigami@elsd.mt.nec.co.jp>,

- o Tomomi Suzuki <suzuki@grelot.elec.ryukoku.ac.jp>,

- o Toshihiko Yagi <j2297222@ed.kagu.sut.ac.jp>,

- o Masato Yoshida (Contributor of PW805i support)

- Original accelerated code by:

- o Kevin Martin <martin@cs.unc.edu>,

- o Rik Faith <faith@cs.unc.edu>,

- o Jon Tombs <tombs@XFree86.org>

- XFree86 Acceleration Architecture (XAA) by:

- o Harm Hanemaayer <H.Hanemaayer@inter.nl.net>,

- S3 accelerated code by:

- o Jon Tombs <tombs@XFree86.org>,

- o Harald Koenig <koenig@tat.physik.uni-tuebingen.de>,

- o David Wexelblat <dwex@XFree86.org>,

- o David Dawes <dawes@XFree86.org>,

- o Robin Cutshaw <robin@XFree86.org>,

- o Amancio Hasty <hasty@netcom.com>,

- o Norbert Distler <Norbert.Distler@physik.tu-muenchen.de>,

- o Leonard N. Zubkoff <lnz@dandelion.com>,

- o Bernhard Bender <br@elsa.mhs.compuserve.com>,

- o Dirk Hohndel <hohndel@XFree86.org>,

- o Joe Moss <joe@XFree86.org>

- S3V accelerated code by:

- o Harald Koenig <koenig@tat.physik.uni-tuebingen.de>,

- o Kevin Brosius <Cobra@compuserve.com>

- o Berry Dijk <berry_dijk@tasking.nl>

-README for XFree86[tm] 3.3.2

- o Dirk Hohndel <hohndel@XFree86.org>

- o Huver Hu <huver@amgraf.com>

- o Dirk Vangestel <gesteld@sh.bel.alcatel.be>

- Mach32 accelerated code by:

- o Kevin Martin <martin@cs.unc.edu>,

- o Rik Faith <faith@cs.unc.edu>,

- o Mike Bernson <mike@mbsun.mlb.org>,

- o Mark Weaver <Mark_Weaver@brown.edu>,

- o Craig Groeschel <craig@metrolink.com>

- o Bryan Feir <jenora@istar.ca>

- Mach64 accelerated code by:

- o Kevin Martin <martin@cs.unc.edu>,

- Mach8, 8514 accelerated code by:

- o Kevin Martin <martin@cs.unc.edu>,

- o Rik Faith <faith@cs.unc.edu>,

- o Tiago Gons <tiago@comosjn.hobby.nl>,

- o Hans Nasten <nasten@everyware.se>,

- o Scott Laird <scott@laird.com>

- Cirrus accelerated code by:

- o Simon Cooper <scooper@vizlab.rutgers.edu>,

- o Harm Hanemaayer <H.Hanemaayer@inter.nl.net>,

- o Bill Reynolds <bill@goshawk.lanl.gov>,

- o Corin Anderson <corina@the4cs.com>

- Western Digital accelerated code by:

- o Mike Tierney <floyd@pepsi.eng.umd.edu>,

- o Bill Conn <conn@bnr.ca>

- P9000 accelerated code by:

-README for XFree86[tm] 3.3.2

- o Erik Nygren <nygren@mit.edu>,

- o Harry Langenbacher <harry@brain.jpl.nasa.gov>

- o Chris Mason <mason@mail.csh.rit.edu>

- o Henrik Harmsen <harmsen@eritel.se>

- AGX accelerated code by:

- o Henry Worth <haworth@wco.com>,

- Number Nine I128 driver by:

- o Robin Cutshaw <robin@XFree86.org>,

- ET4000/W32 accelerated code by:

- o Glenn Lai <glenn@cs.utexas.edu>,

- ET6000 SVGA and accelerated support (both based on the existing W32 code) by:

- o Koen Gadeyne <koen.gadeyne@barco.com>,

- Oak Technologies Inc. accelerated code by:

- o Jorge Delgado <ernar@dit.upm.es>,

- 16 color VGA server by:

- o Gertjan Akkerman <akkerman@dutiba.twi.tudelft.nl>

- 2 color VGA and non-VGA mono servers by:

- o Pascal Haible <haible@izfm.uni-stuttgart.de>

- ATI SVGA driver by:

- o Per Lindqvist <pgd@compuram.bbt.se> and Doug Evans

- <dje@cygnus.com>.

- o Ported to X11R5 by Rik Faith <faith@cs.unc.edu>.

- o Rewritten by Marc Aurele La France <tsi@ualberta.ca>

- WD90C24 support by:

- o Brad Bosch <brad@lachman.com>

- Trident SVGA driver by:

- o Alan Hourihane <alanh@fairlite.demon.co.uk>

-README for XFree86[tm] 3.3.2

- SiS SVGA driver by:

- o Alan Hourihane <alanh@fairlite.demon.co.uk>

- o Xavier Ducoin <xavier@rd.lectra.fr>

- DEC 21030 (TGA) server by:

- o Alan Hourihane <alanh@fairlite.demon.co.uk>

- o Harald Koenig <koenig@tat.physik.uni-tuebingen.de>

- NCR SVGA driver by:

- o Stuart Anderson <anderson@metrolink.com> with the permission

- of NCR Corporation

- Cirrus SVGA driver by:

- o Bill Reynolds <bill@goshawk.lanl.gov>,

- o Hank Dietz <hankd@ecn.purdue.edu>,

- o Simon Cooper <scooper@vizlab.rutgers.edu>,

- o Harm Hanemaayer <H.Hanemaayer@inter.nl.net>,

- o Corin Anderson <corina@the4cs.com>

- Cirrus CL64xx driver by:

- o Manfred Brands <mb@oceonics.nl>

- o Randy Hendry <randy@sgi.com>

- o Jeff Kirk <jeff@bambam.dsd.ES.COM>

- Compaq SVGA driver by:

- o Hans Oey <hans@mo.hobby.nl>

- o Ming Yu <yum@itp.ac.cn>

- o Gerry Toll <gtoll@tc.cornell.edu>

- Oak SVGA driver by:

- o Steve Goldman <sgoldman@encore.com>

- o Jorge Delgado <ernar@dit.upm.es>

- ARK Logic SVGA driver by:

-README for XFree86[tm] 3.3.2

- o Harm Hanemaayer <H.Hanemaayer@inter.nl.net>

- o Leon Bottou <bottou@laforia.ibp.fr>

- AL2101 SVGA driver by:

- o Paolo Severini <lendl@dist.dist.unige.it>

- Avance Logic ``ali'' SVGA driver by:

- o Ching-Tai Chiu <cchiu@netcom.com>

- Chips & Technologies SVGA driver by:

- o Regis Cridlig <cridlig@dmi.ens.fr>

- o Jon Block <block@frc.com>

- o Mike Hollick <hollick@graphics.cis.upenn.edu>

- o Nozomi Ytow

- o Egbert Eich <Egbert.Eich@Physik.TH-Darmstadt.DE>

- o David Bateman <dbateman@ee.uts.edu.au>

- o Xavier Ducoin <xavier@rd.lectra.fr>

- MX SVGA driver by:

- o Frank Dikker <dikker@cs.utwente.nl>

- Video7 SVGA driver by:

- o Craig Struble <cstruble@acm.vt.edu>

- RealTek SVGA driver by:

- o Peter Trattler <peter@sbox.tu-graz.ac.at>

- Apollo Mono driver by:

- o Hamish Coleman <hamish@zot.apana.org.au>

- Matrox SVGA driver by:

- o Guy Desbief <g.desbief@aix.pacwan.net>

- o Radoslaw Kapitan <kapitan@student.uci.agh.edu.pl>

- o Andrew Vanderstock <vanderaj@mail2.svhm.org.au>

- o Angsar Hockmann <Ansgar.Hockmann@hrz.uni-dortmund.de>

-README for XFree86[tm] 3.3.2

- o Michael Will <Michael.Will@student.uni-tuebingen.de>

- o Andrew Mileski <aem@ott.hookup.net>

- o Stephen Pitts <pitts2@memphisonline.com>

- o Dirk Hohndel <hohndel@XFree86.Org>

- o Leonard N. Zubkoff <lnz@dandelion.com>

- ViRGE SVGA driver by:

- o Sebastien Marineau <marineau@genie.uottawa.ca>,

- o Harald Koenig <koenig@tat.physik.uni-tuebingen.de>

- Linux/m68k Frame Buffer Device driver by:

- o Martin Schaller

- o Geert Uytterhoeven <Geert.Uytterhoeven@cs.kuleuven.ac.be>

- o Andreas Schwab <schwab@issan.informatik.uni-dortmund.de>

- o Guenther Kelleter <guenther@Pool.Informatik.RWTH-Aachen.de>

- Tseng ET4000 and ET6000 SVGA driver by:

- o [Unknown authors]

- o Dirk Hohndel <hohndel@XFree86.Org>

- o Koen Gadeyne <koen.gadeyne@barco.com>

- o ... and others

- XFree86-VidModeExtension and xvidtune client by:

- o Kaleb S. Keithley <kaleb@x.org>

- o David Dawes <dawes@XFree86.org>

- o Jon Tombs <tombs@XFree86.org>

- o Joe Moss <joe@XFree86.org>

- XFree86-Misc extension by:

- o Joe Moss <joe@XFree86.org>

- o David Dawes <dawes@XFree86.org>

- XFree86-DGA extension by:

-README for XFree86[tm] 3.3.2

- o Jon Tombs <tombs@XFree86.org>

- o Mark Vojkovich <mvojkovi@ucsd.edu>

- o Harm Hanemaayer <H.Hanemaayer@inter.nl.net>,

- o David Dawes <dawes@XFree86.org>

- XInput integration, devices and clients by:

- o Frederic Lepied <lepied@XFree86.Org> (XInput integration,

- Wacom tablet, Joystick and extended mouse devices, xsetpointer

- and xsetmode clients)

- o Patrick Lecoanet <lecoanet@cena.dgac.fr> (Elographics touch-

- screen device)

- o Steven Lang <tiger@tyger.org> (Summagraphics tablet device)

- Other contributors:

- o Joerg Wunsch <joerg_wunsch@uriah.sax.de> (ET3000 banked mono),

- o Thomas Dickey <dickey@clark.net> (xterm "new" model ANSI col-

- ors and VT220, VT520 emulation).

- o Eric Raymond <esr@snark.thyrsus.com> (new video mode documen-

- tation),

- o and an entire horde of beta-testers around the world!

-7. Contact information

-Ongoing development planning and support is coordinated by the XFree86 Core

-Team. At this time the Core Team consists of (in alphabetical order):

- o Robin Cutshaw <robin@XFree86.org>

- o David Dawes <dawes@XFree86.org>

- o Marc Evans <marc@XFree86.org>

- o Harm Hanemaayer <H.Hanemaayer@inter.nl.net>

- o Dirk Hohndel <hohndel@XFree86.org>

- o Harald Koenig <koenig@XFree86.org>

- o Rich Murphey <rich@XFree86.org>

- o Jon Tombs <tombs@XFree86.org>

-README for XFree86[tm] 3.3.2

- o David Wexelblat <dwex@XFree86.org>

-Mail sent to <Core@XFree86.org> will reach the core team. Please note that

-support questions should be sent to <XFree86@XFree86.org>.

-8. The XFree86 Project, Inc.

-The XFree86 Project, Inc, was founded to accomplish two major goals:

- 1. To provide a vehicle by which XFree86 can be represented in X Consortium,

- Inc, the organization responsible for the design, development, and

- release of The X Window System.

- 2. To provide some basic funding for acquisition of facilities for ongoing

- XFree86 development, largely to consist of new video hardware and basic

- computing facilities.

-The first of these was the primary motivation. We have held discussions with

-the X Consortium on and off for many months, attempting to find an avenue by

-which our loosely-organized free software project could be given a voice within

-the X Consortium. The bylaws of the Consortium would not recognize such an

-organization. After an initial investigation about funding, we decided to form

-our own corporation to provide the avenue we needed to meet the requirements of

-the X Consortium bylaws.

-By doing this, we were able to be involved in the beta-test interval for X11R6,

-and have contributed the majority of XFree86 to the X11R6 and X11R6.1 core

-release. The version of XFree86 in the initial X11R6 core is 3.0. The version

-of XFree86 in the current X11R6.3 release is 3.2.

-An additional benefit of this incorporation is that The XFree86 Project, Inc

-has obtained outside financial support for our work. This will hopefully give

-us the freedom to be more pro-active in obtaining new video hardware, and

-enable us to release better products more quickly, as we will be able to go and

-get what we need, and get it into the hands of the people who can do the work.

-The current Board of Directors and Officers of the The XFree86 Project, Inc,

-are:

- o David Dawes, President and Secretary

- o Dirk Hohndel, Vice-President

- o Glenn Lai, Director

- o Rich Murphey, Treasurer

- o Jim Tsillas, Director

- o Jon Tombs, Director

- o David Wexelblat, Director

-README for XFree86[tm] 3.3.2

-Email to <BOD@XFree86.org> reaches the board of directors.

-Our bylaws have been crafted in such a way to ensure that XFree86 is and always

-will be a free software project. There is no personal financial benefit to any

-member of the Core Team or any other XFree86 participant. All assets of the

-corporation remain with the corporation, and, in the event of the dissolution

-of the corporation, all assets will be turned over to the X Consortium, Inc.

-It is hoped that by doing this, our corporation will be merely a formalization

-of what we have been doing in the past, rather than something entirely new.

-As of March 1997, The XFree86 Project has revised its source/binary access and

-release policy. The main points of the new policy are:

- o There will be no more time-limited public binary-only beta releases.

- Instead we plan to increase the frequency of full public releases to about

- four releases per year.

- o The source access/use is divided into three categories:

- o End users. End users have access to only the source of full public

- releases. The main reason for this restriction is that our develop-

- ment code often contains code from other sources which cannot be

- released to the public immediately.

- o Active developers (members of the XFree86 ``developer team'').

- Active developers must formally become non-voting members of the

- XFree86 Project, and have full access to our internal development

- source. They are permitted to make time-limited binaries (in coordi-

- nation with the Core Team) of the servers they are actively working

- on available to external testers for specific testing.

- o Commercial members. Commercial members are non-voting members of The

- XFree86 Project who donate US$5000/year to the Project. Addition-

- ally, companies who contribute significantly to the development

- effort of XFree86 can be awarded commercial membership by the Core

- Team on a yearly bases. Commercial members can use the internal

- XFree86 development source for derived binary-only products providing

- that they take full responsibility for supporting the product, and

- don't call it ``XFree86'' (although the derivation of the product

- must be acknowledged in any accompanying documentation). Binary

- packages for the OSs we support which are simply compiled from our

- internal source without significant added value are explicitly NOT

- allowed.

-Here is a list of the organizations and individuals who have provided sponsor-

-ship to The XFree86 Project, Inc, either by financial contribution or by the

-donation of equipment and resources. The XFree86 Project, Inc gratefully

-acknowledges these contributions, and hopes that we can do justice to them by

-continuing to release high-quality free software for the betterment of the

-Internet community as a whole.

- o UUNET Communications Services, Inc. <URL:http://www.uu.net/>

-UUNET Communications Services, Inc, deserves special mention. This

-README for XFree86[tm] 3.3.2

-organization stepped forward and contributed the entire 1994 X Consortium mem-

-bership fee on a moment's notice. This single act ensured XFree86's involve-

-ment in X11R6.

- o GUUG -- 1st German Linux Congress

-Also deserving of special mention are the organizers and attendees of the 1st

-German Linux Congress in Heidelberg. Significant funding to The XFree86 Pro-

-ject has been provided from its proceeds.

- o AIB Software Corporation <URL:http://www.aib.com/>, Herndon, VA

- o Roland Alder, Armin Fessler, Patrick Seemann, Martin Wunderli

- o American Micro Group

- o ATI Technologies Inc <URL:http://www.atitech.ca/>

- o Andrew Burgess

- o Berkeley Software Design, Inc <URL:http://www.bsdi.com/>, Falls Church, VA

- o Caldera, Inc. <URL:http://www.caldera.com/>

- o Delix Computer GmbH <URL:http://www.delix.de/>, Stuttgart, Germany

- o The Destek Group, Inc. <URL:http://www.destek.net/Destek/>, Nashua, NH

- (formerly Synergytics)

- o Diamond Multimedia Systems, Inc. <URL:http://www.diamondmm.com/>

- o Digital Equipment Corporation <URL:http://www.digital.com/>

- o Elsa GmbH <URL:http://www.elsa.de/>, Aachen, Germany

- o Genoa Systems Corporation

- o Helius, Inc. <URL:http://www.helius.com/>

- o Hercules Computer Technology, Inc. <URL:http://www.hercules.com/>

- o Ralf Hockens

- o Dirk Hohndel

- o InfoMagic <URL:http://www.infomagic.com/>, Flagstaff, AZ

- o Daniel Kraemer

- o Epoch Networks, Inc. <URL:http://www.eni.net/>, Irvine, CA

- o Frank & Paige McCormick

-README for XFree86[tm] 3.3.2

- o Internet Labs, Inc.

- o Linux International

- o Linux Support Team, Erlangen, Germany

- o LunetIX Softfair <URL:http://www.lunetix.de>, Berlin, Germany

- o Morse Telecommunications <URL:http://www.morse.net>, Long Beach, NY

- o MELCO, Inc <URL:http://www.melcoinc.co.jp>

- o MIRO Computer Products AG, Braunschweig, Germany

- o Rich & Amy Murphey

- o NCR Corp <URL:http://www.ncr.com/>

- o Brett Neumeier

- o Number Nine, Lexington, MA

- o Kazuyuki Okamoto, Japan

- o Prime Time Freeware <URL:http://www.ptf.com/>, San Bruno, CA

- o Red Hat Software <URL:http://www.redhat.com/>, Chapel Hill, NC

- o Norbert Reithinger

- o SPEA Software AG, Starnberg, Germany

- o STB Systems

- o Clifford M Stein

- o Joel Storm

- o S.u.S.E. GmbH <URL:http://www.suse.de>, Fuerth, Germany

- o Tekelec Airtronic GmbH <URL:http://www.tekelec.com>, Muenchen, Germany

- o Jim Tsillas

- o Trans-Ameritech Enterprises, Inc., Santa Clara, CA

- o Unifix Software GmbH, Braunschweig, Germany

- o Vixie Enterprises <URL:http://www.vix.com/>, La Honda, CA

- o Walnut Creek CDROM <URL:http://www.cdrom.com/>, Concord, CA

- o Xtreme s.a.s. <URL:http://www.xfree86.org/xtreme>, Livorno, Italy

-README for XFree86[tm] 3.3.2

-The XFree86 Project, Inc, welcomes the additional contribution of funding

-and/or equipment. Such contributions should be tax-deductible; we will know

-for certain when the lawyers get finished with the papers. For more informa-

-tion, contact The XFree86 Project, Inc, at <BOD@XFree86.org>

-9. Source and binary archive sites

-Source patches are available to upgrade X11R6.3 PL2 from the X Consortium (now

-The Open Group) to XFree86 3.3.2. Binaries for many OSs are also available.

-The distribution is available from:

- o ftp://ftp.XFree86.org/pub/XFree86

-and the following mirror sites:

- o North America:

- o ftp://ftp2.XFree86.org/pub/XFree86 (source and binaries)

- o ftp://ftp.infomagic.com/pub/mirrors/XFree86-current (source and bina-

- ries)

- o ftp://ftp.rge.com/pub/X/XFree86 and http://www.rge.com/pub/X/XFree86

- (source and binaries)

- o ftp://ftp.varesearch.com/pub/mirrors/xfree86 (source and binaries)

- o ftp://ftp.cs.umn.edu/pub/XFree86 (source and binaries)

- o ftp://ftp.kernel.org/pub/mirrors/xfree86 (source and binaries)

- o Europe:

- o ftp://fvkma.tu-graz.ac.at/pub/XFree86 (source and binaries)

- o ftp://gd.tuwien.ac.at/hci/X11/XFree86 and

- http://gd.tuwien.ac.at/hci/X11/XFree86 (source and binaries)

- o ftp://ftp.fee.vutbr.cz/pub/XFree86 (source patches and binaries)

- o ftp://ftp.gwdg.de/pub/xfree86/XFree86 (source and binaries)

- o ftp://ftp.mpi-sb.mpg.de/pub/X/mirror/ftp.xfree86.org (source and

- binaries)

- o ftp://ftp.cs.tu-berlin.de/pub/X/XFree86 (source and binaries)

- o ftp://ftp.uni-erlangen.de/pub/Linux/MIRROR.xfree86 (source and Linux

- binaries)

- o ftp://ftp.uni-stuttgart.de/pub/X11/Xfree86 (source and binaries)

-README for XFree86[tm] 3.3.2

- o ftp://ftp.funet.fi/pub/X11/XFree86 (source and binaries)

- o ftp://ftp.ibp.fr/pub/X11/XFree86 (source and binaries)

- o ftp://ftp.unina.it/pub/XFree86 (source and binaries)

- o ftp://ftp.pvv.unit.no/pub/XFree86 (source and binaries)

- o ftp://sunsite.doc.ic.ac.uk/packages/XFree86 (source and binaries)

- o Asia/Australia:

- o ftp://x.physics.usyd.edu.au/pub/XFree86 (source and binaries)

- o ftp://ftp.netlab.is.tsukuba.ac.jp/pub/XFree86 (source and binaries)

- o ftp://ftp.iij.ad.jp/pub/X/XFree86/XFree86 (source and binaries)

- o ftp://ftp.kreonet.re.kr/pub/Linux/xfree86 (source and binaries)

-Ensure that you are getting XFree86 3.3.2 - some of these sites may archive

-older releases as well. Check the RELNOTES to find which files you need to

-take from the archive.

- Generated from XFree86: xc/programs/Xserver/hw/xfree86/doc/sgml/README.sgml,v 3.75.2.33 1998/02/28 15:49:46 robin Exp $

- $XConsortium: README.sgml /main/31 1996/10/28 05:43:24 kaleb $

-README for XFree86[tm] 3.3.2

- CONTENTS

-1. What's new in XFree86 3.3.2 .............................................. 1

-2. Systems XFree86 has been tested on ....................................... 1

-3. Supported video-card chip-sets ........................................... 2

-4. Where to get more information ............................................ 5

-5. Thanks ................................................................... 6

-6. Credits .................................................................. 6

-7. Contact information ..................................................... 16

-8. The XFree86 Project, Inc. ............................................... 17

-9. Source and binary archive sites ......................................... 21

- i

-$XFree86: xc/programs/Xserver/hw/xfree86/doc/README,v 3.76.2.28 1998/03/01 13:58:20 dawes Exp $

diff --git a/release/sysinstall/help/hardware.hlp b/release/sysinstall/help/hardware.hlp
deleted file mode 100644
index 4916da2f18c6..000000000000
--- a/release/sysinstall/help/hardware.hlp
+++ /dev/null

@@ -1,514 +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 3.0 framework.

-FreeBSD GENERIC kernel:

- Port IRQ DRQ IOMem Description

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

-fdc0 3f0 6 2 n/a Floppy disk controller

-wdc0 1f0 14 n/a n/a IDE/MFM/RLL disk controller

-wdc1 170 15 n/a n/a IDE/MFM/RLL disk controller

-adv0 n/a n/a n/a n/a AdvanSys ADP-9xx SCSI controller

-ncr0 n/a n/a n/a n/a NCR PCI SCSI controller

-bt0 330 dyn dyn dyn Buslogic SCSI controller

-uha0 330 dyn 6 dyn Ultrastore 14f

-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 SCSI

- controller

-amd0 n/a n/a n/a n/a Tekram DC-390(T) / AMD 53c974 PCI SCSI

-dpt n/a n/a n/a n/a DPT RAID SCSI controllers.

-nca0* 1f88 10 dyn dyn ProAudioSpectrum cards

-sea0* dyn 5 dyn c8000 Seagate ST01/02 8 bit controller

-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)

-lpt0 dyn 7 n/a n/a Printer Port 0

-lpt1 dyn dyn n/a n/a Printer Port 1

-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+

-eg0 310 5 dyn dyn 3Com 3C505

-ep0 300 10 dyn dyn 3Com 3C509

-ex0 dyn dyn dyn n/a Intel EtherExpress Pro/10 cards

-fe0 300 dyn n/a n/a Allied-Telesis AT1700, RE2000 and

- Fujitsu FMV-180 series cards.

-fxp0 dyn dyn n/a dyn Intel EtherExpress Pro/100B

-rl0 dyn dyn n/a dyn RealTek 8129/8139 fast ethernet

-tl0 dyn dyn n/a dyn TI TNET100 'ThunderLAN' cards.

-ie0 300 10 dyn d0000 AT&T StarLAN 10 and EN100;

- 3Com 3C507; NI5210

-ix0 300 10 dyn d0000 Intel EtherExpress cards

-ex0 dyn dyn dyn dyn Intel EtherExpress Pro/10 cards

-le0 300 5 dyn d0000 Digital Equipment EtherWorks

- 2 and EtherWorks 3

-lnc0 280 10 n/a dyn Lance/PCnet cards

- (Isolan, Novell NE2100, NE32-VL,

- some PCnet-PCI cards)

-vx0 dyn dyn n/a dyn 3Com 3c59x ((Fast) Etherlink III)

-xl0 dyn dyn n/a dyn 3Com 3c900, 3c905 and 3c905B

- ((Fast) Etherlink XL)

-cs0 0x300 dyn n/a n/a Crystal Semiconductor CS89x0-based

- cards.

-ze0 300 5 n/a d8000 IBM/National Semiconductor

- PCMCIA Ethernet Controller

-zp0 300 10 n/a d8000 3Com 3c589 Etherlink III

- PCMCIA Ethernet Controller

---- 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

-UserConfig, 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 :

- PCI :

----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 and EISA devices can be probed reliably, therefore they

-are not shown in the table above nor can their settings be changed

-using UserConfig. PCI drivers may be seen in the "PCI Devices" section

-in the Active Devices list, if you wish to check for their presence.

-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):

-ctx: Cortex-I frame grabber

-cx: Cronyx/Sigma multiport sync/async

-cy: Cyclades high-speed serial driver

-el: 3Com 3C501

-fea: DEV 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

-joy: Joystick

-labpc: National Instrument's Lab-PC and Lab-PC+

-meteor: Matrox Meteor frame-grabber card

-bktr: Brooktree Bt848 based frame-grabber cards.

-mpu: Roland MPU-401 stand-alone card

-mse: Microsoft, Logitech, ATI bus mouse ports

-mss: Microsoft Sound System

-nic: Dr Neuhaus NICCY 3008, 3009 & 5000 ISDN cards

-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 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

-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 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

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

-WD1003 (any generic MFM/RLL)

-WD1007 (any generic IDE/ESDI)

-IDE

-ATA

-Adaptec 1535 ISA SCSI controllers

-Adaptec 154x series ISA SCSI controllers

-Adaptec 174x series EISA SCSI controller in standard and enhanced mode.

-Adaptec 274X/284X/2940/3940 (Narrow/Wide/Twin) series ISA/EISA/PCI SCSI

-controllers.

-Adaptec AIC7850/AIC7895 on-board SCSI controllers.

-Support for the following controllers is rather weak:

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

-** Note: You cannot boot from the SoundBlaster cards as they have no

- on-board BIOS, such being necessary for mapping the boot device into the

- system BIOS I/O vectors. They're perfectly usable for external tapes,

- CDROMs, etc, however. The same goes for any other AIC-6x60 based card

- without a boot ROM. Some systems DO have a boot ROM, which is generally

- indicated by some sort of message when the system is first powered up

- or reset, and in such cases you *will* also be able to boot from them.

- Check your system/board documentation for more details.

-AdvanSys (Advanced Systems) ABP510/542/5150 ISA and ABP5140/5142 ISA PnP

-cards, ABP842/852 VLB cards, and ABP920/930/930U/930UA/950/960/960U/970/970U

-PCI cards.

-** Note: The ADP510/5140/5150 boards were shipped by HP with the 4020i

- CD-R drive but with NO BIOS, so these models cannot control boot devices

- though they can be used for any secondary SCSI device. Also note that the

- ABP5140/5142 boards were rebadged by SIIG as the "SpeedMaster i540/i542"

-Buslogic 545S & 545c

-Buslogic 445S/445c VLB SCSI controller

-Buslogic 742A, 747S, 747c EISA SCSI controller.

-Buslogic 946c PCI SCSI controller

-Buslogic 956c PCI SCSI controller

-SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI

-controllers:

- ASUS SC-200

- Data Technology DTC3130 (all variants)

- NCR cards (all)

- Symbios cards (all)

- Tekram DC390W, 390U and 390F

- Tyan S1365

-Tekram DC390 and DC390T controllers (maybe other cards based on the

-AMD 53c974 as well).

-NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.

-DTC 3290 EISA SCSI controller in 1542 emulation mode.

-UltraStor 14F, 24F and 34F SCSI controllers.

-Seagate ST01/02 SCSI controllers.

-Future Domain 8xx/950 series SCSI controllers.

-WD7000 SCSI controller.

-With all supported SCSI controllers, full support is provided for

-SCSI-I & SCSI-II peripherals, including Disks, tape drives (including

-DAT and 8mm Exabyte) and CD ROM drives.

-The following CD-ROM type systems are supported at this time:

-(cd) SCSI interface (also includes ProAudio Spectrum and

- SoundBlaster SCSI)

-(mcd) Mitsumi proprietary interface (all models, driver is rather stale)

-(matcd) Matsushita/Panasonic (Creative SoundBlaster) proprietary

- interface (562/563 models)

-(scd) Sony proprietary interface (all models)

-(wcd) ATAPI IDE interface.

-4.2. Network cards

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

-Allied-Telesis AT1700 and RE2000 cards

-AMD PCnet/PCI (79c970 & 53c974 or 79c974)

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

-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

-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

-Efficient ENI-155p ATM PCI

-FORE PCA-200E ATM PCI

-Fujitsu MB86960A/MB86965A

-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

-Isolan AT 4141-0 (16 bit)

-Isolink 4110 (8 bit)

-Novell NE1000, NE2000, and NE2100 ethernet interface.

-3Com 3C501 cards

-3Com 3C503 Etherlink II

-3Com 3c505 Etherlink/+

-3Com 3C507 Etherlink 16/TP

-3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B PCI and EISA

-(Fast) Etherlink III / (Fast) Etherlink XL

-Toshiba ethernet cards

-PCMCIA ethernet cards from IBM and National Semiconductor are also

-supported.

-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?

-4.3. 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)

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

-Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound

-and Roland MPU-401 sound cards.

-Connectix QuickCam

-Matrox Meteor Video frame grabber

-Creative Labs Video Spigot frame grabber

-Cortex1 frame grabber

-Various Frame grabbers based on Brooktree Bt848 chip.

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

-Floppy tape drives (some rather old models only, driver rather stale)

-FreeBSD currently does NOT support IBM's microchannel (MCA) bus.

diff --git a/release/sysinstall/help/install.hlp b/release/sysinstall/help/install.hlp
deleted file mode 100644
index dfc1697d56b0..000000000000
--- a/release/sysinstall/help/install.hlp
+++ /dev/null

@@ -1,513 +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 |

-| |

-| 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: Tue Mar 24 00:56:14 PST 1998

-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 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 requires a 386 or better processor to run (sorry, there is no

-support for '286 processors), 5 megs of RAM to install and 4 megs of

-ram to run. You will need at least 80 megs of free hard drive space.

-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 3 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 2.2.1 and later CDs support the "El Torrito" bootable

- CD standard. Simply put the installation CD in your CDROM drive

- and boot the system to begin installation.

- 2. If you have drivers which allow you to see your CDROM drive

- from from DOS, first disable any fancy memory managers you may

- have configured, change directory to the CDROM (E:\ in the example

- below) and then type this:

- E> install

- and you should boot directly into the FreeBSD installation.

- If either steps fail, please go on to step 3.

- 3. Build a FreeBSD boot floppy from the floppies/boot.flp

- file in a FreeBSD distribution. Either simply use the

- ``makeflp.bat'' script from DOS or read floppies/README.TXT

- for more information on creating bootable floppies under

- different operating systems. Then you simply boot

- from the floppy and you should go into 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 a boot floppy 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.

- 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

-"Novice" 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

-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

-And anyone else on your network will now be able to chose a Media type

-of FTP and type in: ``ftp://<machine with CDROM drive>'' after picking

-"Other" 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 boot floppy 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/rfd0

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

-IMPORTANT NOTE: Though you can do all of the above by hand if you

-really want to, all of it is much more easily accomplished now by

-Robert Nordier's "setup.exe" program. It will give you a menu of

-distribution choices, verify that you have enough free space and do

-all the copying to C:\FREEBSD for you automatically.

-Once you've copied the directories or run setup.exe and let it do all

-the work for you, you can simply launch the installation from DOS by

-running the install.bat script (NOTE: Some memory managers don't like

-this - disable QEMM or EMM386 if they're running before trying this)

-or making a boot floppy as described in section 0.1.

-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/rst0) dist1 .. dist2

-When you go to do the installation, you should also make sure that you

-leave enough room in some temporary directory (which you'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.5 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 (2.0R or later) 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 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 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 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.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 ``Other'' 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/2.2-RELEASE

- There are two FTP installation modes you can use:

- o FTP:

- For all FTP transfers, use the standard "Active" mode for

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

- For all FTP transfers, use "Passive" mode. This allows

- the user to pass through firewalls that do not allow

- incoming connections on random port addresses.

- NOTE: ACTIVE AND PASSIVE MODES ARE NOT THE SAME AS A `PROXY'

- CONNECTIONS, WHERE A PROXY FTP SERVER IS LISTENING ON A

- DIFFERENT PORT!

- In such instances, you should specify the URL as something like:

- ftp://foo.bar.com:1234/pub/FreeBSD

- Where "1234" is the port number of the proxy ftp server.

-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/sd0s5, your E:

-drive /dev/sd0s6, and so on. This example assumes, of course, that

-your extended partition is on SCSI drive 0. For IDE drives, substitute

-``wd'' for ``sd'' appropriately. You otherwise mount extended

-partitions exactly like you would mount any other DOS drive, e.g.:

-mount -t msdos /dev/sd0s5 /dos_d

-2.4 Can I run DOS binaries under FreeBSD?

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

-Ongoing work with BSDI's doscmd utility is bringing this much closer to

-being a reality in FreeBSD 3.0, 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 (provided as XFree86

-3.2) to operate.

----- End of Installation Guide ---

diff --git a/release/sysinstall/help/readme.hlp b/release/sysinstall/help/readme.hlp
deleted file mode 100644
index 5167040e2556..000000000000
--- a/release/sysinstall/help/readme.hlp
+++ /dev/null

@@ -1,110 +0,0 @@

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

- FreeBSD 3.0 --- SNAPSHOT Version , ,

- ----------------------------------------- /( )`

- \ \___ / |

-This is a binary snapshot of 3.0-current, the /- _ `-/ '

-(HEAD) branch which is currently moving towards (/\/ \ \ /\

-the follow-on release to 3.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 2.2.x is almost certainly your best bet.

-ROAD MAP:

- Most files here are also in the Documentation

- Menu of the boot floppy

- 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!*

- ERRATA.TXT Any late-breaking errata information for this

- release. On FTP sites, this file may be frequently

- updated so it's a good idea to check it first

- (the master copy is always on ftp.freebsd.org)

- before reporting problems

- HARDWARE.TXT Information about the configuration of the

- GENERIC kernel and supported hardware

- INSTALL.TXT How to make a new installation of FreeBSD

- on your PC using the data you see here

- UPGRADE.TXT How to upgrade an existing FreeBSD

- installation

- TROUBLE.TXT Troubleshooting information

-o For new installation instructions, see the INSTALL.TXT

- and HARDWARE.TXT files.

-o If you are upgrading from a previous FreeBSD version,

- please take a look at UPGRADE.TXT.

-o It is also important to check the ERRATA.TXT file for any

- late-breaking issues with this release. This file contains

- the latest information on upgrade, security or other problems

- which an administrator should be aware of.

-o Information regarding problems which arise after the CD

- is printed can be found at:

- ftp://ftp.freebsd.org/pub/FreeBSD/3.0-RELEASE/ERRATA.TXT

-For the most up-to-date software along the RELENG_2_2 branch

-(also known as -Stable) which is now proceeding onwards toward

-the release of FreeBSD 2.2.8, please install from:

- ftp://releng22.freebsd.org/pub/FreeBSD/

-Or for the latest 3.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/sysinstall/help/relnotes.hlp b/release/sysinstall/help/relnotes.hlp
deleted file mode 100644
index 0d50346a2b09..000000000000
--- a/release/sysinstall/help/relnotes.hlp
+++ /dev/null

@@ -1,514 +0,0 @@

- RELEASE NOTES

- FreeBSD Release 3.0-SNAP

-This is a 3.0-CURRENT release SNAPshot of FreeBSD, currently

-on its way to a follow-on release for 3.0 which was released

-on October 16th, 1998.

-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 3.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 3.0-current snapshots, you should always see:

- ftp://current.freebsd.org/pub/FreeBSD

-If you wish to get the latest post-3.0-RELEASE technology.

-Table of contents:

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

-1. What's new since 3.0-RELEASE

- 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 ATM

- 2.4 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. Acknowledgements

-1. What's new since 3.0-RELEASE

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

-All changes described here are unique to the 3.0 branch unless

-specifically marked as [MERGED] features.

-1.1. KERNEL CHANGES

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

-1.2. SECURITY FIXES

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

-1.3. USERLAND CHANGES

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

-2. Supported Configurations

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

-FreeBSD currently runs on a wide variety of ISA, VLB, EISA and PCI bus

-based PC's, ranging from 386sx to Pentium class machines (though the

-386sx is not recommended). Support for generic IDE or ESDI drive

-configurations, various SCSI controller, network and serial cards is

-also provided.

-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

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

-WD1003 (any generic MFM/RLL)

-WD1007 (any generic IDE/ESDI)

-IDE

-ATA

-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/2920/2940/2950/3940/3950 (Narrow/Wide/Twin) series

-EISA/VLB/PCI SCSI controllers.

-Adaptec AIC7850, AIC7880, AIC789x, on-board SCSI controllers.

-AdvanSys SCSI controllers (all models).

-Buslogic 545S & 545c

-Buslogic 445S/445c VLB SCSI controller

-Buslogic 742A, 747S, 747c EISA SCSI controller.

-Buslogic 946c PCI SCSI controller

-Buslogic 956c PCI SCSI controller

-DPT SCSI/RAID controllers (most variants).

-SymBios (formerly NCR) 53C810, 53C825, 53c860 and 53c875 PCI SCSI

-controllers:

- ASUS SC-200

- Data Technology DTC3130 (all variants)

- NCR cards (all)

- Symbios cards (all)

- Tekram DC390W, 390U and 390F

- Tyan S1365

-QLogic SCSI and Fibre Channel controllers.

-DTC 3290 EISA SCSI controller in 1542 emulation mode.

-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)

-(wcd) ATAPI IDE interface

-SCSI TAPE SUPPORT:

- The CAM SCSI tape driver doesn't yet handle older (and many times broken)

- tape drives very well. If you've got an older SCSI-1 tape drive, like an

- Exabyte 8200 or older QIC-type tape drive, it may not work properly with

- the CAM tape driver. This is obviously a known problem, and we're

- working on it.

- Newer tape drives that are mostly SCSI-2 compliant should work fine.

- e.g., DAT (DDS-1, 2 and 3), DLT, and newer Exabyte 8mm drives should

- work fine.

- If you want to find out if your particular tape drive is supported, the

- best way to find out is to try it!

-The following drivers were supported under the old SCSI subsystem, but are

-NOT YET supported under the new CAM SCSI subsystem:

- Tekram DC390 and DC390T controllers (maybe other cards based on the

- AMD 53c974 as well).

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

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

- [ Note: There is work-in-progress to port the AIC-6260/6360 and

- UltraStor drivers to the new CAM SCSI framework, but no estimates on

- when or if they will be completed. ]

-Unmaintained drivers, they might or might not work for your hardware:

- Floppy tape interface (Colorado/Mountain/Insight)

- (mcd) Mitsumi proprietary CD-ROM interface (all models)

-2.2. Ethernet cards

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

-Allied-Telesis AT1700 and RE2000 cards

-AMD PCnet/PCI (79c970 & 53c974 or 79c974)

-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

- 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

-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

-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

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

-3Com 3C501 cards

-3Com 3C503 Etherlink II

-3Com 3c505 Etherlink/+

-3Com 3C507 Etherlink 16/TP

-3Com 3C509, 3C579, 3C589 (PCMCIA), 3C590/592/595/900/905/905B PCI and EISA

-(Fast) Etherlink III / (Fast) Etherlink XL

-Toshiba ethernet cards

-Crystal Semiconductor CS89x0-based NICs, including:

- IBM Etherjet ISA

-PCMCIA ethernet cards from IBM and National Semiconductor are also

-supported.

-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 ATM

--------

- o ATM Host Interfaces

- - FORE Systems, Inc. PCA-200E ATM PCI Adapters

- - Efficient Networks, Inc. ENI-155p ATM PCI Adapters

- o ATM Signalling Protocols

- - The ATM Forum UNI 3.1 signalling protocol

- - The ATM Forum UNI 3.0 signalling protocol

- - The ATM Forum ILMI address registration

- - FORE Systems's proprietary SPANS signalling 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.4. 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.

-Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, Gravis UltraSound

-and Roland MPU-401 sound cards. (snd driver)

-Most ISA audio codecs manufactured by Crystal Semiconductors, OPTi, Creative

-Labs, Avance, Yamaha and ENSONIQ. (pcm 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 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.

-FreeBSD currently does NOT support IBM's microchannel (MCA) bus.

-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 3.0-RELEASE and 2.2.x-RELEASE CDs may be ordered on CDROM from:

- Walnut Creek CDROM

- 4041 Pike Lane, Suite D

- Concord CA 94520

- 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 2.2.x or 2.1.x (in some lesser number of cases) and some of the

-following issues may affect 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.

-In the case of using sources, there are simply two targets you need to

-be aware of: The standard ``world'' target, which will upgrade a 2.x

-system to 3.0, or the ``aout-to-elf'' target, which will both upgrade

-and convert the system to ELF binary format.

-In the case of using the binary upgrade option, the system will go

-straight to 3.0/ELF but also populate the /<basepath>/lib/aout

-directories for backwards compatibility with older binaries.

-In either case, going to ELF will mean that you'll have somewhat

-smaller binaries and access to a lot more compiler goodies which have

-been already been ported to other ELF environments (our older and

-somewhat crufty a.out format being largely unsupported by most other

-software projects), but on the downside you'll also have access to far

-fewer ports and packages since many of those have not been adapted to

-ELF yet. This will occur in time, but those who wish to retain access

-to the greatest number of packages and 3rd-party binaries should

-probably stick with a.out.

-The kernel is also still in a.out format at this time so that older

-LKMs and library interfaces can continue to work, but a full

-transition to ELF will occur at some point after 3.0-RELEASE. Those

-wishing to generate dynamic kernel components should therefore use the

-newer KLD mechanism rather than the older LKM format - the LKM format

-is not long for this world and will soon be unsupported!

-[ other important upgrading notes should go here]

-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

-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. Acknowledgements

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

-FreeBSD represents the cumulative work of many dozens, if not

-hundreds, 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 mention to:

- The donors listed at http://www.freebsd.org/handbook/donors.html

- Justin M. Seger <jseger@freebsd.org> for almost single-handedly

- converting the ports collection to ELF.

- Doug Rabson <dfr@freebsd.org> and John Birrell <jb@freebsd.org>

- for making FreeBSD/alpha happen and to the NetBSD project for

- substantial indirect aid.

- Peter Wemm <peter@freebsd.org> for the new kernel module system

- (with substantial aid from Doug Rabson).

- And to the many thousands of FreeBSD users and testers all over the

- world, without whom this release simply would not have been possible.

-We sincerely hope you enjoy this release of FreeBSD!

- The FreeBSD Project

diff --git a/release/sysinstall/help/trouble.hlp b/release/sysinstall/help/trouble.hlp
deleted file mode 100644
index ca374caa4d0a..000000000000
--- a/release/sysinstall/help/trouble.hlp
+++ /dev/null

@@ -1,374 +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 boot floppy, chose 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 console driver (sc0) to go into a special mode which works

- on the ThinkPads. Change the sc0 'Flags' to 0x10 in UserConfig and

- it should work fine. (Look in the Input Menu for 'Syscons Console

- Driver'.)

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

- st0(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/sd0a''.

-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 hangs during boot, right after the "fd0: [my floppy drive]"

- line.

-A: This is not actually a hang, simply a very LONG "wdc0" probe that

- often takes a long time to complete on certain systems (where there

- usually _isn't_ a WD controller). Be patient, your system will boot!

- To eliminate the problem, boot with the -c flag and eliminate the wdc0

- device, or compile a custom kernel.

-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. There's a workaround available now and it is enabled

- automatically if this chip is used on your system.

- For the details refer to the manual page of the disk driver (man 4 wd).

-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: Why does my CD-220E (rev 1.0D) IDE CD-ROM lock up the system when

- I use it?

-A: There are apparently firmware problems with this drive and,

- though a fix may soon be forthcoming, it should probably be avoided

- for now.

-[ Please send hardware tips for this Q&A section to jkh@freebsd.org ]

diff --git a/release/sysinstall/help/upgrade.hlp b/release/sysinstall/help/upgrade.hlp
deleted file mode 100644
index 8b7b893e2316..000000000000
--- a/release/sysinstall/help/upgrade.hlp
+++ /dev/null

@@ -1,168 +0,0 @@

-+===================== Upgrading FreeBSD ==========================+

-| |

-| 0.0 Preface |

-| 0.1 DISCLAIMER |

-| 0.2 IMPORTANT NOTE |

-| |

-| 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 NOTE

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

-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, host.conf, 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, 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, ie.

-# Device Mountpoint FStype Options Dump Pass#

-/dev/wd0s2b none swap sw 0 0

-/dev/wd0s2a / ufs rw 1 1

-/dev/wd0s2f /local0 ufs rw 1 1

-/dev/wd0s2e /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 "Upgrading FreeBSD from source"

-tutorial found at http://www.freebsd.org/docs.html. This method

-requires reliable network connectivity, extra disk space and spare time,

-but has advantages for networks and other more complex installations.