Bring forward doc changes from 2.2. Much will need changing for 3.0,

which is where this is headed, but it's better than the 2.2-SNAP
docs.
This commit is contained in:
jkh 1996-11-13 12:35:17 +00:00
parent ccc3a50f70
commit 7b067e2a3b
7 changed files with 943 additions and 589 deletions

File diff suppressed because it is too large Load Diff

View File

@ -2,7 +2,7 @@ DISTRIBUTION INFORMATION
------------------------
An ``X-'' prefixed before a distribution set means that the XFree86
3.1.2-S base distribution, libraries, manual pages, SVGA server and a
3.2 base distribution, libraries, manual pages, SVGA server and a
set of default fonts will be selected in addition to the set itself.
If you select such a set, you will also be presented with a set of
menus for customizing the selections to your desired X Window System
@ -23,7 +23,7 @@ Kern-Developer: As above, but with only kernel sources instead of
the complete source tree.
User: The base distribution, man pages, dictionary files and
the FreeBSD 1.x and 2.0 compatibility sets.
the FreeBSD 1.x, 2.0 and 2.1.x compatibility sets.
Minimal: Only the base distribution.

View File

@ -1,4 +1,4 @@
Hardware Documentation Guide: $Id: hardware.hlp,v 1.8 1996/08/23 07:56:04 jkh Exp $
Hardware Documentation Guide: $Id: hardware.hlp,v 1.9.2.1 1996/11/13 11:49:40 jkh Exp $
Contents last changed: July 4th, 1996
@ -102,7 +102,7 @@ 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)
vx0 dyn dyn n/a dyn
vx0 dyn dyn n/a dyn 3Com 3c590 / 3c595
ze0 300 5 dyn d8000 IBM/National Semiconductor
PCMCIA Ethernet Controller
zp0 300 10 dyn d8000 3Com PCMCIA Etherlink III
@ -113,8 +113,8 @@ zp0 300 10 dyn d8000 3Com PCMCIA Etherlink III
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
('-c' boot option) to reconfigure the kernel to match the way your
hardware is currently set (see the next section).
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.
@ -123,127 +123,150 @@ or reliably access the devices in your system.
2. Using UserConfig to change FreeBSD kernel settings
-- --------------------------------------------------
The UserConfig utility allows you to override various settings of
the FreeBSD kernel before the system has booted. This allows you to
make minor adjustments to the various drivers in the system without
necessarily having to recompile the kernel.
The FreeBSD kernel on the install floppy contains drivers for every
piece of hardware that could concievably 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.
UserConfig is activated by specifying the `-c' flag at the initial
boot prompt. For example:
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.
>> FreeBSD BOOT @ 0x10000: 640/7168 k of memory
Use hd(1,a)/kernel to boot sd0 when wd0 is also installed.
Usage: [[wd(0,a)]/kernel][-abcCdhrsv]
Use ? for file list or press Enter for defaults
Once FreeBSD is installed, it will remember the changes made using
UserConfig, so that they only need be made once.
Boot: -c
--
It is important to disable drivers that are not relevant to a system
in order to minimise the possibility of interference, which can cause
problems that are difficult to track down.
This command causes the system to boot the default kernel ("/kernel") and
the UserConfig utility to be started once the kernel is loaded into memory.
UserConfig features a commandline interface for users with serial
consoles or a need to type commands, and a fullscreen 'visual'
interface, which provides point-and-shoot configuration functionality.
The `-c' flag follows any of the other parameters you may need to provide
for the system to boot properly. For example, to boot off the second of
two SCSI drives installed and run UserConfig, you would type:
Here is a sample UserConfig screen shot in 'visual' mode:
Boot: sd(1,a)/kernel -c
-----------------
---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 :
As always, the kernel will report some information on your processor
and how much memory your system has. Then UserConfig will be invoked
and you will see the prompt:
config>
To see the list of commands that UserConfig accepts, you may type '?' and
press [ENTER]. The help message looks something like this:
Command Description
------- -----------
ls List currently configured devices
port <devname> <addr> Set device port (i/o address)
irq <devname> <number> Set device irq
drq <devname> <number> Set device drq (DMA Request)
iomem <devname> <addr> Set device maddr (memory address)
iosize <devname> <size> Set device memory size
flags <devname> <mask> Set device flags
enable <devname> Enable device
disable <devname> Disable device (will not be probed)
visual Go to visual mode
quit Exit this configuration utility
help This message
---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
You may alter nearly all of the default settings present in the FreeBSD
generic kernel. This includes reassigning IRQs, disabling troublesome
devices (or drivers that conflict with the hardware your system has),
setting special device flags, etc.
The screen is divided into four sections :
Since people's tastes in user interface design vary widely, we have
provided two different interfaces to the UserConfig utility. If you
type `visual' (or just `v') you will be placed in the "GUI" oriented device
attributes editor. If you're someone who's more at home with
command-line flavored interfaces then simply don't do that and use
the CLI commands directly. :-)
- 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.
Since the visual interface pretty much describes itself, we'll use the
more verbose command line interface while describing UserConfig in the
following examples.
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.
The most common use of UserConfig is to adjust or disable a driver
which is causing trouble. The "ls" command displays the current
settings for all the drivers present in the booted kernel, and once
you have located an entry of interest you may use the displayed device
name to change its settings or even disable the driver completely.
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.
For example, to change the memory address of network adapter 'ed0' to
the address 0xd4000, you would type
config> iomem ed0 0xd4000
-----------------
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.
To entirely disable a device driver you are not using, use the
"disable" command. In this example, you would disable device
`ie0' by typing:
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.
config> disable ie0
-----------
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.
You can use the "ls" command to verify your changes and correct
any other problems before continuing the boot process.
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.)
Once you are happy with a given configuration you may type: "quit"
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.
This will cause the kernel to boot with the new settings you
have chosen.
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.
Once you have a fully installed system (e.g. the `bin' distribution
has been successfully extracted), any changes you make in UserConfig
are permanently stored in the `/kernel' file on the root filesystem.
This action is performed by the `dset' utility, which will ensure that
these settings remain in effect until you replace the kernel with
a new one. If you do not want your changes to be permanently
stored like this, remove `dset' from the /etc/rc file before you
make any changes.
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.
If you accidentally change a setting for a device that you did not mean
to change, the safest thing to do is to reset the computer and start
over. Do not allow the boot to proceed (e.g. do not type "quit") with
bad settings as these may be permanently stored by dset and
leave your system in a state where it will no longer run properly.
To finish configuring a driver, press 'Q'.
We suggest as a general rule that you disable any drivers that are not
used by your particular hardware configuration. There are known problems
with certain device drivers (see section 4.0) that can cause conflicts
with other devices if they're also not disabled. You should move or
disable any device that resides at the same port or IRQ as a device
you actually have!
You can also remove drivers that are not needed by building yourself a
custom kernel that contains only the device drivers which your system
really needs (see section 6.0 of the FreeBSD.FAQ). If your system has
sufficient free disk space to store and compile the kernel sources,
this is the option we most highly recommend.
Sample UserConfig session
-------------------------
Here is a walkthrough of a sample use of UserConfig. The system in
question has an IDE disk, two serial ports, a single printer port, a
floppy drive and an NE2000 ethernet card set to I/O address 0x340 and
IRQ 10.
- At the 'config>' prompt, type 'v' and press Enter to activate
'visual' mode.
- The fullscreen mode comes up, with the highlight bar in the Active Drivers
area over the 'Storage' group, which is Collapsed. Press Enter to
Expand the group.
- Disable all of the drivers listed in this group except for the
"Floppy disk controller" and "IDE/ESDI/MFM disk controller" by
highlighting each in turn and pressing Del.
- Move to the 'Network' group, Expand it, and disable all of the drivers
except for 'ed0', the first of the
"NE1000,NE2000,3C503,WD/SMC80xx Ethernet adapters".
- Move to the 'Communications' group, Expand it and disable the 'lpt1' and
'lpt2' drivers.
- Disable the 'mse0' driver in the 'Input' group.
- Go back to the 'Network' group, highlight the 'ed0' driver, and press
Enter to configure it.
- Change the 'Port address' and 'IRQ number' fields to match the
configuration of the card, ie. 0x340 and 10 respectively.
- Press 'Q' to finish configuring the device, and then 'Q' again to
leave UserConfig. Answer 'yes' to save the changes and continue to boot
using the new configuration.
3. LINT - other possible configurations

View File

@ -1,25 +1,33 @@
-----------------------------------------
FreeBSD 2.2 --- SNAPSNOT Version , ,
FreeBSD 2.2 --- ALPHA Version , ,
----------------------------------------- /( )`
\ \___ / |
Welcome to the latest 2.2 SNAPSHOT release of /- _ `-/ '
FreeBSD! These 2.2 snapshots are done periodically (/\/ \ \ /\
along the way to 2.2-RELEASE (scheduled for release / / | ` \
sometime in the first quarter of '97) for testing O O ) / |
purposes and to provide early access to new 2.2 `-^--'`< '
features to those devlopers or hobbiests who have (_.) _ ) /
an interest in knowing more about what we're up to. `.___/` /
Welcome to the 2.2 ALPHA release of FreeBSD! /- _ `-/ '
This release preceeds our first full 2.2 release, (/\/ \ \ /\
which is scheduled for a late December / early / / | ` \
January release. Your testing of this release will O O ) / |
help to ensure that 2.2-RELEASE is of the highest `-^--'`< '
quality we can make it, and is much appreciated. (_.) _ ) /
`.___/` /
`-----' /
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 (see notes below). | |
\ / /\
Please also note that these SNAP releases are ______( (_ / \______/
EXPERIMENTAL in nature and not intended for the ,' ,-----' |
casual user or in production environments! `--{__________)
Please also note that ALPHA releases, as much ______( (_ / \______/
as we enjoy seeing them tested in serious ,' ,-----' |
situations, are not recommended for production `--{__________)
environments!
***** Final note: PLEASE also read the Hardware guide, which you will
find in the root directory of your distribution as HARDWARE.TXT. It
is also available in the Documentation submenu of the boot floppy, but
it's probably a good idea to read it before even getting that far. It
contains important checklist information on configuring your hardware
before starting the installation process. ****
What is FreeBSD? FreeBSD is an operating system based on 4.4 BSD Lite
for Intel, AMD, Cyrix or NexGen "x86" based PC hardware. It works
@ -36,7 +44,7 @@ researchers or folks who simply want to see how it all works.
A large collection of 3rd party ported software (the "ports
collection") is also provided to make it easier for you to obtain and
install all your favorite traditional UNIX utilities for FreeBSD.
Over 550 ports, from editors to programming languages to graphical
Over 600 ports, from editors to programming languages to graphical
applications, make FreeBSD a powerful and comprehensive operating
environment that extends far beyond what's provided by many commercial
versions of UNIX.

View File

@ -1,32 +1,34 @@
RELEASE NOTES
FreeBSD Release 2.2 SNAPSHOT
FreeBSD Release 2.2-ALPHA
0. What's new since 2.2-961014-SNAP?
This is an ALPHA release of FreeBSD 2.2-RELEASE and is aimed primarily
at release testers. Some parts of the documentation may not be updated
yet and should be reported if and when seen. Naturally, any installation
failures or crashes should also be reported ASAP by sending mail to
bugs@freebsd.org or using the send-pr command (those preferring a WEB based
interface can also see http://www.freebsd.org/send-pr.html).
0. What's new since 2.1.5-RELEASE
------------------------------------
Support for the SDL RISCom N2pci sync serial card.
0. What's new since 2.2-961006-SNAP?
------------------------------------
11th-hour bug in SYN attack protection code fixed [showstopper].
Support for Cyclades Cyclom-Y (multi-port async serial) PCI adaptors
as well as multiple controllers and the 32-Y (if you are currently using
the Cyclades serial adapter, you should re-make your /dev entries and
remove the old ones).
/usr/src/contrib now part of src dist selection (doh!) [showstopper].
Updated support for ethernet adaptors which use the DEC DC21X4X chipset.
Support for HP PC Lan+ cards (model numbers: 27247B and 27252A)
The 3COM 3c590 / 3c595 drivers have improved considerably.
You need only change your kernel settings *once* now, on initial startup
from the floppy. They will be preserved on the subsequently installed
kernel.
0. What's new since 2.2-960801-SNAP?
------------------------------------
Support for HP PC Lan+ cards (model numbers: 27247B and 27252A)
Update to gcc 2.7.2.1 & add support for weak symbols.
Many things moved/brought into /usr/src/contrib, updating and
@ -39,66 +41,6 @@ Update sgmlfmt to `instant'.
Protection against the widely reported SYN attack.
1. What's New since 2.1.0-RELEASE?
----------------------------------
A considerable number of changes to the VM system have been made
to increase the stability under certain types of load. If you
had panics under the last snapshot, try this one and see if they
persist.
The AHC driver now does considerably more in the way of handling errors
gracefully.
More cosmetic work on the installation, /stand/sysinstall now genuinely
useful after installation time (though still missing a man page - urk!).
Early support for APM (automated power management) and PCCARD
(formerly PCMCIA) features of laptops. Many PCCARD devices
are supported, from modems to ethernet cards to SCSI adaptors.
Adaptec AIC7850 support has been added.
The Yellow Pages (NIS) support has had many optimizations made
and no longer has portions copyright under the GPL.
Various VM system enhancements and a few bugs fixed (gzip'd binaries
now work again, for example).
The system installation tool has been revamped with slightly different
menu behavior and a number of bugs have been fixed. It's hoped that
this installation will be more intuitive for new users than previous
ones (feedback welcomed, of course).
The Intel EtherExpress Pro/100B PCI ethernet card is now supported.
The 3COM 3C590 and 3C595 ethernet cards are now supported.
The ARNET (now Digiboard) Sync 570i high-speed serial card is now supported.
The Linux emulation is now good enough to run the Linux version of
Netscape, with JAVA support (as well as a number of other Linux
utilities).
The Matrox Meteor frame grabber card is better supported.
It is now possible to burn CDROMs using the Plasmon or HP 4080i
CDR drives (see `wormcontrol(1)').
The pipe code has been substantially sped up, as have some components
of the VM system.
A /dev/random device (and associated "pool of entropy") has been added
for applications which require more unpredicatable sequences of random
numbers for security. See the random(4) man page for more info.
Early NFS v3 support (not enabled by default).
An early implementation of the Device Filesystem (devfs) is available
(see mount_devfs). Device switch tables are now also dynamically built.
Early IPX routing support.
2. Technical overview
---------------------
@ -107,7 +49,7 @@ for Intel i386/i486/Pentium (or compatible) based PC's. It is based
primarily on software from U.C. Berkeley's CSRG group, with some
enhancements from NetBSD, 386BSD, and the Free Software Foundation.
Since our release of FreeBSD 2.0 over a year ago, the performance,
Since our release of FreeBSD 2.0 almost 2 years ago, the performance,
feature set and stability of FreeBSD has improved dramatically. The
largest change is a revamped VM system with a merged VM/file buffer
cache that not only increases performance but reduces FreeBSD's memory
@ -123,11 +65,11 @@ heart and have attempted to provide what we hope is a more sane and
easily understood installation process. Your feedback on this
(constantly evolving) process is especially welcome!
In addition to the base distributions, FreeBSD offers a new ported
software collection with over 390 commonly sought-after programs. The
In addition to the base distributions, FreeBSD offers a ported
software collection with over 600 commonly sought-after programs. The
list of ports ranges from http (WWW) servers, to games, languages,
editors and almost everything in between. The entire ports collection
requires only 10MB of storage, all ports being expressed as "deltas"
requires only 6MB of storage, all ports being expressed as "deltas"
to their original sources. This makes it much easier for us to update
ports and greatly reduces the disk space demands made by the ports
collection. To compile a port, you simply change to the directory of
@ -263,6 +205,7 @@ 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 (not recommended due to driver instability)
Intel EtherExpress Pro/100B PCI Fast Ethernet
@ -343,7 +286,7 @@ LAST resort!
4.2. CDROM
FreeBSD 2.1-RELEASE and these 2.2 SNAPSHOT CDs may be ordered on CDROM from:
FreeBSD 2.1.6-RELEASE and 2.2-RELEASE CDs may be ordered on CDROM from:
Walnut Creek CDROM
4041 Pike Lane, Suite D
@ -351,21 +294,16 @@ FreeBSD 2.1-RELEASE and these 2.2 SNAPSHOT CDs may be ordered on CDROM from:
1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
Or via the internet from orders@cdrom.com or http://www.cdrom.com.
Their current catalog can be obtained via ftp as:
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 2.2-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription
FreeBSD 3.0-SNAP CDs are $29.95 or $14.95 with a FreeBSD-SNAP subscription
(-RELEASE and -SNAP subscriptions are entirely seperate). 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.
Walnut Creek CDROM also sells a full line of FreeBSD related
merchandise such as T-shirts ($14.95, available in "child", Large and
XL sizes), coffee mugs ($9.95), tattoos ($0.25 each) and posters
($3.00).
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
@ -383,7 +321,8 @@ 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. Bug reports
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
@ -482,29 +421,40 @@ The FreeBSD Development Team, excluding core team members
Thomas Gellekum <tg@FreeBSD.org>
Thomas Graichen <graichen@FreeBSD.org>
Rod Grimes <rgrimes@FreeBSD.org>
James FitzGibbon <jfitz@FreeBSD.org>
John Hay <jhay@FreeBSD.org>
Jeffrey Hsu <hsu@FreeBSD.org>
Ugen J.S. Antsilevich <ugen@FreeBSD.org>
Gary Jennejohn <gj@FreeBSD.org>
Andreas Klemm <andreas@FreeBSD.org>
Warner Losh <imp@FreeBSD.org>
L Jonas Olsson <ljo@FreeBSD.org>
Eric L. Hernes <erich@FreeBSD.org>
Scott Mace <smace@FreeBSD.org>
Atsushi Murai <amurai@FreeBSD.org>
Mark Murray <markm@FreeBSD.org>
Alex Nash <alex@FreeBSD.org>
Masafumi NAKANE <max@FreeBSD.org>
David E. O'Brien <obrien@FreeBSD.org>
Andras Olah <olah@FreeBSD.org>
Steve Passe <smp@FreeBSD.org>
Bill Paul <wpaul@FreeBSD.org>
Joshua Peck Macdonald <jmacd@FreeBSD.org>
John Polstra <jdp@FreeBSD.org>
Steve Price <steve@FreeBSD.org>
Mike Pritchard <mpp@FreeBSD.org>
Doug Rabson <dfr@FreeBSD.org>
James Raynard <jraynard@FreeBSD.org>
Geoff Rehmet <csgr@FreeBSD.org>
Martin Renters <martin@FreeBSD.org>
Paul Richards <paul@FreeBSD.org>
Ollivier Robert <roberto@FreeBSD.org>
Chuck Robey <chuckr@FreeBSD.org>
Dima Ruban <dima@FreeBSD.org>
Wolfram Schneider <wosch@FreeBSD.org>
Andreas Schulz <ats@FreeBSD.org>
Karl Strickland <karl@FreeBSD.org>
Michael Smith <msmith@FreeBSD.org>
Paul Traina <pst@FreeBSD.org>
Guido van Rooij <guido@FreeBSD.org>
Steven Wallace <swallace@FreeBSD.org>
@ -515,8 +465,8 @@ The FreeBSD Development Team, excluding core team members
Additional FreeBSD helpers and beta testers:
Coranth Gryphon Dave Rivers
Kaleb S. Keithley Michael Smith
Terry Lambert David Dawes
Kaleb S. Keithley Terry Lambert
David Dawes Don Lewis
Special mention to:
@ -544,4 +494,4 @@ We sincerely hope you enjoy this release of FreeBSD!
The FreeBSD Core Team
$Id: relnotes.hlp,v 1.16 1996/10/23 22:28:56 wosch Exp $
$Id: relnotes.hlp,v 1.17.2.1 1996/11/13 11:49:42 jkh Exp $

View File

@ -1,11 +1,11 @@
Welcome to the 2.1 (or 2.0.5) -> 2.1.6 upgrade procedure!
Welcome to the 2.1.x (or 2.0.5) -> 2.2 upgrade procedure!
It must first be said that this upgrade DOES NOT take a particularly
sophisticated approach to the upgrade problem, it being more a question
of providing what seemed "good enough" at the time. A truly polished
upgrade that deals properly with the broad spectrum of installed 2.0.5 / 2.1
systems would be nice to have, but until that gets written what you get is
this - the brute-force approach!
sophisticated approach to the upgrade problem, it being more a
question of providing what seemed "good enough" at the time. A truly
polished upgrade that deals properly with the broad spectrum of
installed 2.0.5 / 2.1 systems would be nice to have, but until that
gets written what you get is this - the brute-force approach!
What this upgrade will attempt to do is best summarized thusly:

View File

@ -2,7 +2,7 @@ DISTRIBUTION INFORMATION
------------------------
An ``X-'' prefixed before a distribution set means that the XFree86
3.1.2-S base distribution, libraries, manual pages, SVGA server and a
3.2 base distribution, libraries, manual pages, SVGA server and a
set of default fonts will be selected in addition to the set itself.
If you select such a set, you will also be presented with a set of
menus for customizing the selections to your desired X Window System
@ -23,7 +23,7 @@ Kern-Developer: As above, but with only kernel sources instead of
the complete source tree.
User: The base distribution, man pages, dictionary files and
the FreeBSD 1.x and 2.0 compatibility sets.
the FreeBSD 1.x, 2.0 and 2.1.x compatibility sets.
Minimal: Only the base distribution.