os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Start 2.1-ifying these.

Browse source
This commit is contained in:
John Fieber 1995-10-30 16:18:55 +00:00
parent a594d4d583
commit 3ea2ead1f5
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/branches/RELENG_2_1_0/; revision=137
2 changed files with 121 additions and 43 deletions

72
handbook/install.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: install.sgml,v 1.9.2.3 1995-10-22 00:50:28 jfieber Exp $ -->
<!-- $Id: install.sgml,v 1.9.2.4 1995-10-30 16:18:52 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -41,7 +41,7 @@
(IRQ) and IO port addresses. </item>
<item>Download the <url
url="ftp://ftp.freebsd.org/pub/FreeBSD/2.0.5-RELEASE/UPDATES/boot.flp"
url="ftp://ftp.freebsd.org/pub/FreeBSD/2.1-RELEASE/floppies/boot.flp"
name="installation boot disk image"> file to your hard
drive, and be sure to tell your browser to
<em>save</em> rather than <em>display</em>.
@ -191,12 +191,13 @@ Boot:
between MS-DOS and FreeBSD.
<!-- XXX Status???
<bf>Can I mount my MS-DOS extended partitions?</bf>
This feature isn't in FreeBSD 2.0.5 but should be in 2.1.
We've laid all the groundwork for making this happen, now
we just need to do the last 1 percent of the work involved.
-->
<bf>Can I run MS-DOS binaries under FreeBSD?</bf>
@ -238,7 +239,6 @@ Boot:
<itemize>
<item>WD1003 (any generic MFM/RLL)
<item>WD1007 (any generic IDE/ESDI)
<item>WD7000
<item>IDE
<item>ATA
@ -246,7 +246,7 @@ Boot:
<item>Adaptec 154x series ISA SCSI controllers
<item>Adaptec 174x series EISA SCSI controller in
standard and enhanced mode.
<item>Adaptec 274X/284X/2940 <!-- 3940 (in 2.1) -->
<item>Adaptec 274x/284x/2940/3940
(Narrow/Wide/Twin)
series EISA/VLB/PCI SCSI controllers
<item>Adaptec
@ -275,7 +275,7 @@ Boot:
<item>Buslogic 956c PCI SCSI controller
<item>NCR 53C810 and 53C825 PCI SCSI controller.
<item>NCR5380/NCR53400 ("ProAudio Spectrum") SCSI controller.
<item>NCR5380/NCR53400 (``ProAudio Spectrum'') SCSI controller.
<item>DTC 3290 EISA SCSI controller in 1542 emulation mode.
@ -284,6 +284,9 @@ Boot:
<item>Seagate ST01/02 SCSI controllers.
<item>Future Domain 8xx/950 series SCSI controllers.
<item>WD7000 SCSI controllers.
</itemize>
With all supported SCSI controllers, full support is
@ -295,39 +298,23 @@ Boot:
time:
<itemize>
<item>Soundblaster SCSI and ProAudio Spectrum SCSI (cd)
<item>Mitsumi (all models) proprietary interface (mcd)
<item>Soundblaster SCSI and ProAudio Spectrum SCSI (<tt>cd</tt>)
<item>Mitsumi (all models) proprietary interface (<tt>mcd</tt>)
<item>Matsushita/Panasonic (Creative)
CR-562/CR-563 proprietary interface (matcd)
<item>Sony proprietary interface (scd)
CR-562/CR-563 proprietary interface (<tt>matcd</tt>)
<item>Sony proprietary interface (<tt>scd</tt>)
<item>ATAPI IDE interface
(experimental and should be considered ALPHA quality!)
(<tt>wcd</tt>)
</itemize>
<bf>Note:</bf> CD-Drives with IDE interfaces are not
supported at this time.
Some controllers have limitations with the way they
deal with &gt;16MB of memory, due to the fact that the
ISA bus only has a DMA address space of 24 bits. If
you do your arithmetic, you'll see that this makes it
impossible to do direct DMA to any address &gt;16MB.
This limitation is even true of some EISA controllers
(which are normally 32 bit) when they're configured to
emulate an ISA card, which they then do in *all*
respects. This problem is avoided entirely by IDE
controllers (which do not use DMA), true EISA
controllers (like the UltraStor, Adaptec 1742A or
Adaptec 2742) and most VLB (local bus) controllers. In
the cases where it's necessary, the system will use
"bounce buffers" to talk to the controller so that you
can still use more than 16Mb of memory without
difficulty.
<sect1><heading>Ethernet cards</heading>
<p>
<itemize>
<item>Allied-Telesis AT1700 and RE2000 cards
<item>SMC Elite 16 WD8013 ethernet interface, and
most other WD8003E, WD8003EBT, WD8003W, WD8013W,
WD8003S, WD8003SBT and WD8013EBT based clones. SMC
@ -338,7 +325,7 @@ Boot:
<item>DEC DC21140 based NICs (SMC???? DE???)
<item>DEC FDDI (DEFPA/DEFEA) NICs
<item>Fujitsu MB86960A family of NICs
<item>Fujitsu FMV-181 and FMV-182
<item>Intel EtherExpress
@ -363,6 +350,10 @@ Boot:
Semiconductor are also supported.
</itemize>
<p><em>Note:</em> FreeBSD does not currently suppport
PnP (plug-n-play) features present on some ethernet
cards. If your card has PnP, it should be disabled.
<sect1><heading>Miscellaneous devices</heading>
<p>
@ -387,7 +378,7 @@ Boot:
</itemize>
FreeBSD currently does NOT support IBM's microchannel
FreeBSD currently does not support IBM's microchannel
(MCA) bus, but support is apparently close to
materializing. Details will be posted as the situation
develops.
@ -401,8 +392,8 @@ Boot:
<sect1><heading>Before installing from CDROM</heading>
<p>If your CDROM is of an unsupported type, such as an
IDE CDROM, then please skip to section 2.3: MS-DOS
Preparation.
IDE CDROM, then please skip to <ref id="install:msdos"
name="MS-DOS Preparation">.
There is not a lot of preparatory work that needs to be
done to successfully install from one of Walnut Creek's
@ -487,7 +478,7 @@ Boot:
that.
<sect1><heading>Before installing from a MS-DOS partition</heading>
<sect1><heading>Before installing from a MS-DOS partition<label id="install:msdos"></heading>
<p>To prepare for installation from an MS-DOS partition,
copy the files from the distribution into a directory
@ -629,7 +620,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
In order for NFS installation to work, the server
must support "subdir mounts", e.g. if your FreeBSD
2.0.5 distribution directory lives on:
2.1 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
@ -647,7 +638,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
<p>FTP installation may be done from any mirror site
containing a reasonably up-to-date version of FreeBSD
2.0.5, a full menu of reasonable choices from almost
2.1, a full menu of reasonable choices from almost
anywhere in the world being provided by the FTP site
menu.
@ -658,11 +649,8 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
choice in that menu. A URL can also be a direct IP
address, so the following would work in the absence
of a name server: <tscreen>
ftp://192.216.222.4/pub/FreeBSD/2.0.5-RELEASE</tscreen>
ftp://192.216.222.4/pub/FreeBSD/2.1-RELEASE</tscreen>
<em><bf>NOTE:</bf> Substitute "ALPHA" for "RELEASE"
during the ALPHA test period!</em>
If you are installing through a firewall then you
should probably select ``Passive mode'' ftp, which is
the default. If you are talking to a server which

92
handbook/relnotes.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: relnotes.sgml,v 1.4.2.2 1995-10-22 00:50:33 jfieber Exp $ -->
<!-- $Id: relnotes.sgml,v 1.4.2.3 1995-10-30 16:18:55 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -7,6 +7,95 @@
-->
<sect><heading>About this release<label id="relnotes"></heading>
<p>FreeBSD is a freely available, full source 4.4 BSD
Lite based release 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 one year 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 footprint, making a 5MB configuration
a more acceptable minimum. Other enhancements include
full NIS client and server support, transaction TCP
support, dial-on-demand PPP, an improved SCSI
subsystem, early ISDN support, support for FDDI and
Fast Ethernet (100Mbit) adapters, improved support for
the Adaptec 2940 (WIDE and narrow) and many hundreds of
bug fixes.
We've also taken the comments and suggestions of many
of our users to 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 some 350 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'' to their original sources.
This makes it much easier for us to update ports, and
greatly reduces the disk space demands made by the
older 1.0 ports collection. To compile a port, you
simply change to the directory of the program you wish
to install, type make and let the system do the rest.
The full original distribution for each port you build
is retrieved dynamically off of CDROM or a local ftp
site, so you need only enough disk space to build the
ports you want. (Almost) every port is also provided
as a pre-compiled "package" which can be installed with
a simple command (pkg_add) by those who do not wish to
compile their own ports from source.
A number of additional documents which you may find
very helpful in the process of installing and using
FreeBSD may now also be found in the
<bf>/usr/share/doc</bf> directory. You may view the
manuals with any HTML capable browser with the
following URLs:
<descrip>
<tag>The FreeBSD handbook</tag>
<htmlurl url="file:/usr/share/doc/handbook/handbook.html">
<tag>The FreeBSD FAQ</tag>
<htmlurl url="file:/usr/share/doc/FAQ/freebsd-faq.html">
</descrip>
You can also visit the master (and most frequently
updated) copies at <htmlurl
url="http://www.freebsd.org"
name="http://www.freebsd.org">.
The core of FreeBSD does not contain DES code which
would inhibit its being exported outside the United
States. There is an add-on package to the core
distribution, for use only in the United States, that
contains the programs that normally use DES. The
auxiliary packages provided separately can be used by
anyone. A freely (from outside the U.S.) exportable
European distribution of DES for our non-U.S. users
also exists and is described in the <htmlurl
url="../FAQ/freebsd-faq.html" name="FreeBSD FAQ">.
If password security for FreeBSD is all you need, and
you have no requirement for copying encrypted passwords
from different hosts (Suns, DEC machines, etc) into
FreeBSD password entries, then FreeBSD's MD5 based
security may be all you require! We feel that our
default security model is more than a match for DES,
and without any messy export issues to deal with. If
you're outside (or even inside) the U.S., give it a
try!
<![ IGNORE [
<p>Since our first release of FreeBSD 1.0 nearly two
years ago, FreeBSD has changed dramatically. Since
release 2.0, FreeBSD has been based on the Berkeley BSD
@ -501,3 +590,4 @@
ask about them!
-->
]]>