d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

In a sudden burst of energy (perhaps it was that last mocha), attempt

Browse Source 
to update the release docs to more current information.
This commit is contained in:
jkh 2000-02-09 06:33:49 +00:00
parent 7c91491218
commit 1ef9626771
5 changed files with 45 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
release/texts/ABOUT.TXT
View File

@ -15,7 +15,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 2000 ports, from editors to programming languages to graphical
Over 3000 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.

10
release/texts/FLOPPIES.TXT
View File

@ -32,14 +32,14 @@ work well, depending on your hardware and operating system environment
(different versions of UNIX have totally different names for the
floppy drive - neat, huh? :-).
If you're on an ALPHA machine which netboots its floppy images or
you have a 2.88MB or LS-120 floppy capable of taking a 2.88MB image
If you're on an ALPHA machine which can network-boot its floppy images
or you have a 2.88MB or LS-120 floppy capable of taking a 2.88MB image
on an x86 machine, you may still wish to use the older (but now
twice as large) boot.flp image which we also provide. That contains
the contents of kern.flp and mfsroot.flp on a single floppy,
essentially, and can be used in all of the above scenarios as well
as a handy boot image for those mastering "El Torito" bootable CD
images. See the mkisofs(1) command for more information.
essentially. This file should also be used as the boot file for those
mastering "El Torito" bootable CD images. See the mkisofs(1) command
for more information.
Going to two installation boot floppies is a step we definitely
would have rather avoided but we simply no longer could due to

17
release/texts/LAYOUT.TXT
View File

@ -9,13 +9,16 @@ HARDWARE.TXT compat1x info src tools
INSTALL.TXT compat20 dict manpages packages
README.TXT compat21 des doc
RELNOTES.TXT compat22 floppies ports
XF86333
XF86336
If you want to do a CDROM, FTP or NFS installation from this
distribution directory, all you need to do is make a 1.44MB floppy
from the floppies/boot.flp image file (see floppies/README.TXT for
instructions on how to do this), boot it and follow the instructions.
See INSTALL.TXT for more information.
distribution directory, all you need to do is make the 1.44MB boot
floppies from the floppies directory (see floppies/README.TXT for
instructions on how to do this), boot them and follow the instructions.
The rest of the data needed during the installation will be obtained
automatically based on your selections. If you've never installed
FreeBSD before, you also want to read the INSTALL.TXT file for
instructions.
If you're trying to do some other type of installation or are merely
curious about how a distribution is organized, what follows is a more
@ -24,7 +27,7 @@ thorough description of each item in more detail:
1. The *.TXT files obviously contain documentation (this file is
LAYOUT.TXT) and should be read before starting an installation.
2. The XF86333 directory contains the XFree86 project's 3.3.3.1 release and
2. The XF86336 directory contains the XFree86 project's 3.3.6 release and
consists of a series of gzip'd tar files which contain each component
of the XFree86 distribution.
@ -49,7 +52,7 @@ thorough description of each item in more detail:
command.
The ports collection may be installed like any other distribution
and requires about 50MB unpacked. More information on the ports
and requires about 100MB unpacked. More information on the ports
collection may be obtained from http://www.freebsd.org/ports or
locally from ``file:/usr/share/doc/handbook'' if you've installed
the doc distribution.

55
release/texts/README.TXT
View File

@ -35,57 +35,52 @@ business with FreeBSD than in playing with the cutting edge of
technology, however, then 3.x is almost certainly your best bet.
ROAD MAP:
Most files here are also in the Documentation
Menu of the boot floppy
Most information here is also available from the Documentation menu
during installation.
ERRATA.TXT Please read this file! It will tell you where to look
for the latest information on problems which have been
found and fixed in this release.
ERRATA.TXT Read this file! It will tell you where to look for the
latest information on problems which have been found and
fixed since this release was created (and may bite you).
README.TXT This file
ABOUT.TXT All about FreeBSD, including contact information
RELNOTES.TXT Release Notes - what's new & different in this
release
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!*
LAYOUT.TXT Information about the layout of the release directory.
If you are installing from floppies, it is especially
important that you read this section!
HARDWARE.TXT Information about the configuration of the
GENERIC kernel and supported hardware
HARDWARE.TXT Information about the configuration of the GENERIC kernel
and supported hardware. New installers should read this
file.
INSTALL.TXT How to make a new installation of FreeBSD
on your PC using the data you see here
INSTALL.TXT Installation instructions - new installers should read this.
UPGRADE.TXT How to upgrade an existing FreeBSD
installation
UPGRADE.TXT Upgrading an existing FreeBSD installation
TROUBLE.TXT Troubleshooting information
TROUBLE.TXT General troubleshooting information
o For new installation instructions, see the INSTALL.TXT
and HARDWARE.TXT files.
o It is, again, very important to check the ERRATA.TXT file for any
late-breaking issues with this release. If you don't read the ERRATA,
you will probably fall right into the same problems that have already
been reported (and fixed as noted in the ERRATA).
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
that an administrator should be aware of.
If you're a developer/hobbiest and not interested in QA'd releases
so much as simply keeping up to date on the latest FreeBSD technology,
you can also install one of our "snapshot" releases.
For the most up-to-date software along the RELENG_3 branch
(also known as 3.4-stable) which is now proceeding onwards toward
the release of FreeBSD 3.5, please install from:
(also known as 3.4-stable), now proceeding towards the release
of FreeBSD 3.5, please install your snapshots from from:
ftp://releng3.freebsd.org/pub/FreeBSD/
Or for the latest 4.0-Current (HEAD branch) snapshot releases,
For the latest 4.0-current (HEAD branch) snapshot releases,
please install from:
ftp://current.freebsd.org/pub/FreeBSD

8
release/texts/TROUBLE.TXT
View File

@ -19,10 +19,10 @@ 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, choose the "Fixit" item
and insert the fixit floppy or CDROM when asked. You will then be
placed into a shell with a wide variety of commands available (in the
/stand and /mnt2/stand directories) for checking, repairing and
To invoke fixit, simply boot the kern.flp floppy, choose the "Fixit"
item and insert the fixit floppy or CDROM when asked. You will then
be placed into a shell with a wide variety of commands available (in
the /stand and /mnt2/stand directories) for checking, repairing and
examining file systems and their contents. Some UNIX administration
experience *is* required to use the fixit option!