Web pages, may I introduce you to CVS. CVS, these are the web pages.
Yes, this is supposed to be a new top level in the repository. For the moment any changes to this area must be cleared by myself or Jordan. Once the kinks are worked out, the policy will probably be relaxed.
This commit is contained in:
commit
38df6f51c6
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=543
189 changed files with 30753 additions and 0 deletions
4
en/releases/2.0/Makefile
Normal file
4
en/releases/2.0/Makefile
Normal file
|
|
@ -0,0 +1,4 @@
|
|||
DOCS= announce.sgml credits.sgml install.sgml notes.sgml
|
||||
|
||||
.include "../../web.mk"
|
||||
|
||||
155
en/releases/2.0/announce.sgml
Normal file
155
en/releases/2.0/announce.sgml
Normal file
|
|
@ -0,0 +1,155 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$Date: 1996-09-24 17:45:54 $">
|
||||
<!ENTITY title "FreeBSD 2.0 Announcement">
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
]>
|
||||
<html>
|
||||
&header;
|
||||
|
||||
<p>
|
||||
To: announce@freefall.cdrom.com<br>
|
||||
Subject: 2.0 RELEASE is now available on ftp.freebsd.org!<br>
|
||||
Date: Tue, 22 Nov 1994 06:35:37 -0800<br>
|
||||
From: "Jordan K. Hubbard" <jkh@freefall.cdrom.com>
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The FreeBSD Project team is very pleased to announce their release of
|
||||
FreeBSD 2.0; a full 32 bit 4.4 BSD Lite based operating system for
|
||||
Intel PCs (i386, i486 and Pentium class).
|
||||
|
||||
<p>
|
||||
Since our first release of FreeBSD 1.0 some 18 months ago, FreeBSD has
|
||||
changed almost entirely. A new port from the Berkeley 4.4 code base
|
||||
was done, which brought the legal status of the system out of the
|
||||
shadows with the blessing of Novell (new owners of USL and UNIX). The
|
||||
port to 4.4 also brought in a host of new features, filesystems and
|
||||
enhanced driver support. With our new unencumbered code base, we have
|
||||
every reason to hope that we'll be able to release quality operating
|
||||
systems without further legal encumbrance for some time to come!
|
||||
|
||||
<p>
|
||||
FreeBSD 2.0 represents the culmination of almost 2 years of work and
|
||||
many thousands of man hours put in by an international development
|
||||
team. We hope you enjoy it!
|
||||
|
||||
<p>
|
||||
FreeBSD 2.0 also features an advanced installation that enables one to
|
||||
install from tape, CD, NFS or FTP over SLIP, ethernet or the parallel
|
||||
port, and DOS floppies or hard disk partitions. This is, we feel, our
|
||||
easiest to use installation yet! Many many suggestions from the
|
||||
previous 2.0 ALPHA release were incorporated, and RELEASE is now far
|
||||
less dangerous [we hope :-)]than ALPHA was!
|
||||
|
||||
<p>
|
||||
FreeBSD 2.0 also supports more friendly co-habitation with other
|
||||
operating systems, allowing you to easily mount DOS filesystems and
|
||||
install a multi-OS boot manager without having to leave the
|
||||
installation utility. All planned installation methods are now also
|
||||
supported. A trouble-shooting guide for those in, well, trouble may
|
||||
also be of help and is featured on the boot floppy.
|
||||
|
||||
<p>
|
||||
For more information on what's new with FreeBSD, or what general
|
||||
features it offers, we strongly suggest that you simply download our
|
||||
boot floppy and boot from it. You can easily read the release notes
|
||||
on it using a simple menu, and with no danger to the contents of your
|
||||
hard disk (unless you deliberately chose "proceed with installation",
|
||||
in which case your fate is in your own hands! :-).
|
||||
|
||||
<p>
|
||||
An upgrade path from ALPHA->RELEASE will also be provided shortly for
|
||||
the benefit of those who were kind enough to help us test the early
|
||||
snapshot of 2.0. Watch the announce list for its availability, or
|
||||
simply be impatient and extract the 2.0R bindist over your ALPHA one!
|
||||
:-)
|
||||
|
||||
<p>
|
||||
Those wishing to obtain this version of 2.0 on CDROM should contact
|
||||
our sponsors, Walnut Creek CDROM (info@cdrom.com) or any of the other
|
||||
CD vendors who will, no doubt, be doing their own releases.
|
||||
|
||||
<p>
|
||||
If you're currently running 1.x and are looking for an upgrade path,
|
||||
we're sorry to say that only full installations are supported at this
|
||||
time. Simply back up your password and user files before reinstalling
|
||||
from the 2.0 media, then bring them back. If public demand is high
|
||||
enough, and we can figure out a way of easily doing it, we'll offer
|
||||
something, but it should be understood that the differences between
|
||||
1.x and 2.0 are *large*, and it's not certain that we'll be able to do
|
||||
it at all.
|
||||
|
||||
<p>
|
||||
Those unable or unwilling to download the boot floppy may also get the
|
||||
release notes by mail - send mail to <info@FreeBSD.org> for an
|
||||
automated reply. Updated information will also be provided on a more
|
||||
or less continuous basis in our WEB pages:
|
||||
|
||||
http://www.freebsd.org
|
||||
|
||||
<p>
|
||||
FreeBSD 2.0 RELEASE is or will be available for ftp in the following
|
||||
locations:
|
||||
|
||||
<ul>
|
||||
<li>Primary ftp://ftp.freebsd.org/pub/FreeBSD/2.0-RELEASE
|
||||
<li>U.S-2 ftp://ftp.dataplex.net/pub/FreeBSD/2.0-RELEASE
|
||||
<li>U.S-3 ftp://kryten.atinc.com/pub/FreeBSD/2.0-RELEASE
|
||||
<li>U.S-4 ftp://ref.tfs.com/pub/FreeBSD/2.0-RELEASE
|
||||
<li>Taiwan ftp://netbsd.csie.nctu.edu.tw/pub/FreeBSD/2.0-RELEASE
|
||||
<li>Australia ftp://ftp.physics.usyd.edu.au/FreeBSD/2.0-RELEASE
|
||||
<li>France ftp://ftp.ibp.fr/pub/freeBSD/2.0-RELEASE
|
||||
<li>Finland ftp://nic.funet.fi:/pub/unix/FreeBSD/2.0-RELEASE
|
||||
<li>Russia ftp://ftp.kiae.su/FreeBSD/2.0-RELEASE
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
(Translated for the non-URL literate: FreeBSD is available for anonymous
|
||||
ftp on ftp.freebsd.org in the pub/FreeBSD/2.0-RELEASE directory)
|
||||
|
||||
<p>
|
||||
It will also, no doubt, be available on a number of mirror sites as
|
||||
soon as they pick it up. However, ftp.freebsd.org is on a T3 line and
|
||||
supports 300 simultaneous users (it's a FreeBSD machine :-), so it's
|
||||
unlikely that you'll have too much trouble getting it from this site
|
||||
until the mirrors do so.
|
||||
|
||||
<p>
|
||||
If you are directly Internet connected, it is also NOT necessary to
|
||||
load the bindist from this site! Simply download the 2 boot floppies,
|
||||
begin the installation, and select the FTP installation method - it
|
||||
will do the rest for you, transparently.
|
||||
|
||||
<p>
|
||||
Finally, we'd like to publically *thank* Walnut Creek CDROM, without
|
||||
whos continuing support and extreme generousity, we'd probably be long
|
||||
gone! They've been of immense help to us.
|
||||
|
||||
<p>
|
||||
Thanks must also go to Poul-Henning Kamp, our fearless and long
|
||||
suffering release engineer for 2.0. While all of us have sacrificed
|
||||
much sleep to the cause, he has a new wife but has somehow managed to
|
||||
do so as well! :-)
|
||||
|
||||
<p>
|
||||
And to all of our users (this is probably starting to sound like the
|
||||
academy awards :-), a similar thank you! We couldn't have done it
|
||||
without your constant flow of commentary, patches, donations of code
|
||||
and moral support. As corny as it sounds, we do it all for you folks!
|
||||
[Though the ego gratification is nice too :-)]
|
||||
|
||||
<p>
|
||||
Thanks to all, and we sincerely hope you enjoy this release!
|
||||
|
||||
<p>
|
||||
Comments, as always, to hackers@FreeBSD.org.
|
||||
|
||||
|
||||
<p>
|
||||
Jordan<br>
|
||||
[on behalf of the FreeBSD Project team]
|
||||
|
||||
&footer;
|
||||
</body>
|
||||
</html>
|
||||
210
en/releases/2.0/credits.sgml
Normal file
210
en/releases/2.0/credits.sgml
Normal file
|
|
@ -0,0 +1,210 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$Date: 1996-09-24 17:45:53 $">
|
||||
<!ENTITY title "FreeBSD 2.0 Credits">
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
]>
|
||||
<html>
|
||||
&header;
|
||||
|
||||
<pre>
|
||||
FreeBSD 2.0
|
||||
Contributor List
|
||||
|
||||
|
||||
|
||||
Derived Software Contributors:
|
||||
|
||||
This software was originally derived from William F. Jolitz's 386BSD
|
||||
release 0.1, though almost none of the original 386BSD specific code
|
||||
remains. This software has been essentially reimplemented on top of
|
||||
4.4 BSD Lite, from the Computer Science Research Group (CSRG) at
|
||||
the University of California, Berkeley and associated academic
|
||||
contributors.
|
||||
|
||||
There are also portions of NetBSD that have been integrated into FreeBSD
|
||||
as well, and we would therefore like to thank all the contributors
|
||||
to NetBSD for their work. Despite some occasionally rocky moments in
|
||||
the relations between the two groups, we both want essentially the same
|
||||
thing: More BSD based operating systems on people's computers! We
|
||||
wish the NetBSD group every success in their endevors.
|
||||
|
||||
|
||||
Hardware Contributors:
|
||||
|
||||
A special thank-you to Walnut Creek CDROM for providing the 486/DX2-66 EISA/VL
|
||||
system that is being used for our development work, to say nothing of
|
||||
the network access and other donations of hardware resources. It would have
|
||||
been impossible to do this release without their support.
|
||||
|
||||
Thanks also to Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
|
||||
drive. It's been most useful!
|
||||
|
||||
|
||||
The FreeBSD Core Team (in alphabetical order):
|
||||
|
||||
Andreas Schulz <ats@g386bsd.first.bmd.de>
|
||||
Andrew A. Chernov <ache@astral.msk.su>
|
||||
Bruce Evans <bde@FreeBSD.org>
|
||||
David Greenman <davidg@Root.COM>
|
||||
Garrett A. Wollman <wollman@freefall.cdrom.com>
|
||||
Gary Palmer <gpalmer@FreeBSD.org>
|
||||
Geoff Rehmet <csgr@cs.ru.ac.za>
|
||||
Jack Vogel <jackv@FreeBSD.org>
|
||||
John Dyson <dyson@implode.rain.com>
|
||||
Jordan K. Hubbard <jkh@FreeBSD.org>
|
||||
Paul Richards <paul@isl.cf.ac.uk>
|
||||
Poul-Henning Kamp <phk@FreeBSD.org>
|
||||
Rich Murphey <rich@lamprey.utmb.edu>
|
||||
Rodney W. Grimes <rgrimes@cdrom.com>
|
||||
Soren Schmidt <sos@FreeBSD.org>
|
||||
|
||||
|
||||
Additional FreeBSD Contributors (no particular order):
|
||||
|
||||
Adam Glass <glass@postgres.berkeley.edu>
|
||||
Andrew Herbert <andrew@werple.apana.org.au>
|
||||
Andrew Moore <alm@FreeBSD.org>
|
||||
Atsushi Murai <amurai@spec.co.jp>
|
||||
Bob Wilcox <bob@obiwan.uucp>
|
||||
Bruce Evans <bde@kralizec.zeta.org.au>
|
||||
Charles Hannum <mycroft@ai.mit.edu>
|
||||
Chris G. Demetriou <cgd@postgres.berkeley.edu>
|
||||
Chris Torek <torek@ee.lbl.gov>
|
||||
Christoph Robitschko <chmr@edvz.tu-graz.ac.at>
|
||||
Curt Mayer <curt@toad.com>
|
||||
Dave Burgess <burgess@hrd769.brooks.af.mil>
|
||||
Dave Rivers <rivers@ponds.uucp>
|
||||
David Dawes <dawes@physics.su.OZ.AU>
|
||||
Frank Maclachlan <fpm@crash.cts.com>
|
||||
Gary A. Browning <gab10@griffcd.amdahl.com>
|
||||
Gary Clark II <gclarkii@radon.gbdata.com>
|
||||
Guido van Rooij <guido@gvr.win.tue.nl>
|
||||
Havard Eidnes <Havard.Eidnes@runit.sintef.no>
|
||||
Holger Veit <Holger.Veit@gmd.de>
|
||||
Ishii Masahiro, R. Kym Horsell
|
||||
J.T. Conklin <jtc@winsey.com>
|
||||
James Clark <jjc@jclark.com>
|
||||
James da Silva <jds@cs.umd.edu> et al
|
||||
Jim Wilson <wilson@moria.cygnus.com>
|
||||
Joerg Wunsch <joerg_wunsch@uriah.sax.de>
|
||||
Julian Elischer <julian@dialix.oz.au>
|
||||
Julian Stacey <stacey@guug.de> <fallback: <julian@meepmeep.pcs.com>>
|
||||
Keith Bostic <bostic@toe.CS.Berkeley.EDU>
|
||||
Keith Moore <?>
|
||||
Marc Frajola <marc@escargot.rain.com>
|
||||
Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu>
|
||||
Martin Birgmeier
|
||||
Paul Kranenburg <pk@cs.few.eur.nl>
|
||||
Paul Mackerras <paulus@cs.anu.edu.au>
|
||||
Poul-Henning Kamp <phk@login.dkuug.dk>
|
||||
Rob Shady <rls@id.net>
|
||||
Sascha Wildner <swildner@channelz.GUN.de>
|
||||
Scott Mace <smace@FreeBSD.org>
|
||||
Sean Eric Fagan <sef@kithrup.com>
|
||||
Serge V. Vakulenko <vak@zebub.msk.su>
|
||||
Steven Wallace <swallace@ece.uci.edu>
|
||||
Søren Schmidt <sos@login.dkuug.dk>
|
||||
Terry Lee <terry@uivlsi.csl.uiuc.edu>
|
||||
Theo Deraadt <deraadt@fsa.ca>
|
||||
Ugen J.S.Antsilevich <ugen@NetVision.net.il>
|
||||
Yuval Yarom <yval@cs.huji.ac.il>
|
||||
|
||||
|
||||
386BSD Patch kit patch contributors (no particular order):
|
||||
|
||||
Adam Glass <glass@postgres.berkeley.edu>
|
||||
Adrian Hall <adrian@ibmpcug.co.uk>
|
||||
Andrew A. Chernov <ache@astral.msk.su>
|
||||
Andrew Herbert <andrew@werple.apana.org.au>
|
||||
Andrew Moore <alm@netcom.com>
|
||||
Andy Valencia <ajv@csd.mot.com> <jtk@netcom.com>
|
||||
Arne Henrik Juul <arnej@Lise.Unit.NO>
|
||||
Bakul Shah <bvs@bitblocks.com>
|
||||
Barry Lustig <barry@ictv.com>
|
||||
Bob Wilcox <bob@obiwan.uucp>
|
||||
Branko Lankester
|
||||
Brett Lymn <blymn@mulga.awadi.com.AU>
|
||||
Bruce Evans <bde@kralizec.zeta.org.au>
|
||||
Charles Hannum <mycroft@ai.mit.edu>
|
||||
Chris G. Demetriou <cgd@postgres.berkeley.edu>
|
||||
Chris Torek <torek@ee.lbl.gov>
|
||||
Christoph Robitschko <chmr@edvz.tu-graz.ac.at>
|
||||
Daniel Poirot <poirot@aio.jsc.nasa.gov>
|
||||
Dave Burgess <burgess@hrd769.brooks.af.mil>
|
||||
Dave Rivers <rivers@ponds.uucp>
|
||||
David Dawes <dawes@physics.su.OZ.AU>
|
||||
David Greenman <davidg@Root.COM>
|
||||
Eric J. Haug <ejh@slustl.slu.edu>
|
||||
Felix Gaehtgens <felix@escape.vsse.in-berlin.de>
|
||||
Frank Maclachlan <fpm@crash.cts.com>
|
||||
Gary A. Browning <gab10@griffcd.amdahl.com>
|
||||
Geoff Rehmet <csgr@alpha.ru.ac.za>
|
||||
Goran Hammarback <goran@astro.uu.se>
|
||||
Guido van Rooij <guido@gvr.win.tue.nl>
|
||||
Guy Harris <guy@auspex.com>
|
||||
Havard Eidnes <Havard.Eidnes@runit.sintef.no>
|
||||
Herb Peyerl <hpeyerl@novatel.cuc.ab.ca
|
||||
Holger Veit <Holger.Veit@gmd.de>
|
||||
Ishii Masahiro, R. Kym Horsell
|
||||
J.T. Conklin <jtc@winsey.com>
|
||||
Jagane D Sundar < jagane@netcom.com >
|
||||
James Clark <jjc@jclark.com>
|
||||
James Jegers <jimj@miller.cs.uwm.edu>
|
||||
James W. Dolter
|
||||
James da Silva <jds@cs.umd.edu> et al
|
||||
Jay Fenlason <hack@datacube.com>
|
||||
Jim Wilson <wilson@moria.cygnus.com>
|
||||
Joerg Lohse <lohse@tech7.informatik.uni-hamburg.de>
|
||||
Joerg Wunsch <joerg_wunsch@uriah.sax.de>
|
||||
John Dyson - <formerly dyson@ref.tfs.com>
|
||||
John Woods <jfw@eddie.mit.edu>
|
||||
Jordan K. Hubbard <jkh@whisker.hubbard.ie>
|
||||
Julian Elischer <julian@dialix.oz.au>
|
||||
Julian Stacey <stacey@guug.de> <fallback: <julian@meepmeep.pcs.com>>
|
||||
Karl Lehenbauer <karl@NeoSoft.com> <karl@one.neosoft.com>
|
||||
Keith Bostic <bostic@toe.CS.Berkeley.EDU>
|
||||
Ken Hughes
|
||||
Kent Talarico <kent@shipwreck.tsoft.net>
|
||||
Kevin Lahey <kml%rokkaku.UUCP@mathcs.emory.edu> <kml@mosquito.cis.ufl.edu>
|
||||
Marc Frajola <marc@escargot.rain.com>
|
||||
Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu>
|
||||
Martin Renters <martin@innovus.com>
|
||||
Michael Galassi <nerd@percival.rain.com>
|
||||
Mike Durkin <mdurkin@tsoft.sf-bay.org>
|
||||
Nate Williams <nate@bsd.coe.montana.edu>
|
||||
Nick Handel <nhandel@NeoSoft.com> <nick@madhouse.neosoft.com>
|
||||
Pace Willisson <pace@blitz.com>
|
||||
Paul Kranenburg <pk@cs.few.eur.nl>
|
||||
Paul Mackerras <paulus@cs.anu.edu.au>
|
||||
Paul Popelka <paulp@uts.amdahl.com>
|
||||
Peter da Silva <peter@NeoSoft.com>
|
||||
Phil Sutherland <philsuth@mycroft.dialix.oz.au>
|
||||
Poul-Henning Kamp <phk@login.dkuug.dk>
|
||||
Ralf Friedl <friedl@informatik.uni-kl.de>
|
||||
Rich Murphey <rich@lamprey.utmb.edu>
|
||||
Rick Macklem <root@snowhite.cis.uoguelph.ca>
|
||||
Robert D. Thrush <rd@phoenix.aii.com>
|
||||
Rodney W. Grimes <rgrimes@cdrom.com>
|
||||
Rog Egge <?>
|
||||
Sascha Wildner <swildner@channelz.GUN.de>
|
||||
Scott Burris <scott@pita.cns.ucla.edu>
|
||||
Scott Reynolds <scott@clmqt.marquette.mi.us>
|
||||
Sean Eric Fagan <sef@kithrup.com>
|
||||
Simon J Gerraty <sjg@melb.bull.oz.au> <sjg@zen.void.oz.au>
|
||||
Stephen McKay <robert@psych.psy.uq.oz.au>
|
||||
Terry Lambert <terry@icarus.weber.edu>
|
||||
Terry Lee <terry@uivlsi.csl.uiuc.edu>
|
||||
Warren Toomey <wkt@csadfa.cs.adfa.oz.au>
|
||||
Wiljo Heinen <wiljo@freeside.ki.open.de>
|
||||
William Jolitz <withheld>
|
||||
Wolfgang Solfrank <ws@tools.de>
|
||||
Wolfgang Stanglmeier <wolf@dentaro.GUN.de>
|
||||
Yuval Yarom <yval@cs.huji.ac.il>
|
||||
|
||||
Id: CONTRIB.FreeBSD,v 1.1 1994/11/18 12:03:25 jkh Exp
|
||||
</pre>
|
||||
|
||||
&footer;
|
||||
</body>
|
||||
</html>
|
||||
493
en/releases/2.0/install.sgml
Normal file
493
en/releases/2.0/install.sgml
Normal file
|
|
@ -0,0 +1,493 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$Date: 1996-09-24 17:45:54 $">
|
||||
<!ENTITY title "FreeBSD 2.0 Installation Guide">
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
]>
|
||||
<html>
|
||||
&header;
|
||||
|
||||
<pre>
|
||||
Welcome to FreeBSD 2.0, the complete 4.4 BSD Lite based OS for Intel (or
|
||||
compatible) based PCs.
|
||||
|
||||
There are several documents on the floppy and a couple of on-line help
|
||||
screens that will greatly assist you in installing your system as you go
|
||||
along. Nonetheless, initial user testing has shown that some of the
|
||||
terminology used may be difficult for newcomers to UN*X to understand, so
|
||||
we've prepared this step-by-step guide explaining a typical installation.
|
||||
You may find it useful to print this out and keep it handy as you go
|
||||
through the installation, or at least read through it once carefully so
|
||||
that some of the prompts and questions you encounter do not come as
|
||||
complete surprises.
|
||||
|
||||
Before you do anything, make two 1.44MB floppies from the two image files
|
||||
you'll find in the floppies/ directory - boot.flp and cpio.flp. If you're
|
||||
reading this under DOS, you can do it in 1 easy step, or 3 in case this
|
||||
doesn't (for some weird reason) work:
|
||||
|
||||
1. If you're reading this file after typing "go", simply ESC back out for
|
||||
a moment and select the "makeflp" batch file to make the two floppies.
|
||||
This will invoke the DOS formatter to format the floppies and then
|
||||
attempt to write the two disk images onto them. If this doesn't work,
|
||||
follow steps 2 through 4:
|
||||
|
||||
2. Use the DOS format command to format 2 NEW floppies. A lot of problems
|
||||
have been caused by people using old and defective floppies, and much
|
||||
grief can often be saved by simply using new, or at least trusted,
|
||||
media.
|
||||
|
||||
3. Insert the first floppy and type:
|
||||
|
||||
tools\dos-tool\rawrite floppies\boot.flp a:
|
||||
|
||||
4. Insert the second floppy and type
|
||||
|
||||
tools\dos-tool\rawrite floppies\cpio.flp a:
|
||||
|
||||
You're now prepared to boot from the boot floppy and begin the installation.
|
||||
|
||||
|
||||
The installation starts with the following screen:
|
||||
|
||||
+-------------------------- Welcome to FreeBSD! ---------------------------+
|
||||
| Use ALT-F2 and ALT-F1 to toggle between debugging |
|
||||
| information screen (ALT-F2) or this dialog screen (ALT-F1) |
|
||||
| |
|
||||
| Please select one of the following options: |
|
||||
| +----------------------------------------------------------------------+ |
|
||||
| | 1. README READ THIS FIRST. | |
|
||||
| | 2. Release Notes Read the 2.0 Release Notes (recommended). | |
|
||||
| | 3. Troubleshooting Read this in case of trouble. | |
|
||||
| | 4. Partitions and MBRs Verbose description of how these work. | |
|
||||
| | 5. COPYRIGHT Read FreeBSD Copyright Information. | |
|
||||
| | 6. Install Proceed with full installation. | |
|
||||
| | 7. Fixit Repair existing installation (`fixit' mode). | |
|
||||
| | 8. Quit Don't do anything, just reboot. | |
|
||||
| +----------------------------------------------------------------------+ |
|
||||
+--------------------------------------------------------------------------+
|
||||
| < OK > <Cancel> |
|
||||
+--------------------------------------------------------------------------+
|
||||
|
||||
|
||||
You can move the arrow keys up and down to highlight the various options,
|
||||
selecting an option by hitting return when its line is highlighted. You
|
||||
can also type the number of the option you want (1 - 7) and hit return.
|
||||
It's recommended that you read the README at a minimum, though the Release
|
||||
Notes are also helpful. This may seem a like a lot to read, but if you are
|
||||
new to FreeBSD then these notes are invaluable for explaining the system
|
||||
and are highly recommended.
|
||||
|
||||
When you're done reading docs, select Install (5) to proceed to the next
|
||||
screen.
|
||||
|
||||
This next screen is the disk editor screen, which looks like this:
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
FreeBSD 2.0-RELEASE Installation -- Diskspace editor
|
||||
|
||||
Disks Total FreeBSD |You should now assign some
|
||||
|space to root, swap, and
|
||||
0: sd0 2006 MB 0 MB |(optionally) /usr partitions
|
||||
1: sd1 496 MB 0 MB |Root (/) should be a minimum
|
||||
|of 18MB with a 30MB /usr
|
||||
Filesystems Type Size Action Mountpoint |or 50MB without a /usr.
|
||||
|Swap space should be a
|
||||
|minimum of 12MB or RAM * 2
|
||||
|Be sure to also (A)ssign a
|
||||
|mount point to each one or
|
||||
|it will NOT be enabled.
|
||||
|
|
||||
|We suggest that you invoke
|
||||
|(F)disk, (W)rite the bootcode
|
||||
|then (D)isklabel your disk.
|
||||
|If installing on a drive
|
||||
|other than 0, also read the
|
||||
|TROUBLESHOOTING doc first
|
||||
Commands available:
|
||||
(H)elp (T)utorial (F)disk (D)isklabel (P)roceed (Q)uit
|
||||
|
||||
Enter Command>
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
|
||||
As we can see, this system has two drives, sd0 and sd1. On an IDE system,
|
||||
these would show up as "wd0" and "wd1" (or, on a single drive system, just
|
||||
sd0 or wd0). We can see that neither of them has any space assigned to
|
||||
FreeBSD (they each show 0MB under the FreeBSD column), so we follow the
|
||||
instructions on the right hand side of the screen and invoke the (F)disk
|
||||
editor by typing `f':
|
||||
|
||||
Enter Command> F
|
||||
|
||||
We're now prompted with the drive number to (F)disk, so we enter 0 for
|
||||
the first drive:
|
||||
|
||||
Enter number of disk to Fdisk> 0
|
||||
|
||||
This now brings us to the FDISK editor screen, which looks like this:
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- FDISK
|
||||
|
||||
Disk: sd0 Geometry: 2006 Cyl * 32 Hd * 64 Sect = 2006Mb = 4108600 Sect
|
||||
|
||||
1 Boot?=No Type=Primary 'big' DOS (> 32MB)
|
||||
Phys=(c0/h1/s1..c299/h63/s32) Sector=(32..614399)
|
||||
Size=300 MB, 299 Cylinders + 31 Tracks + 32 Sectors
|
||||
|
||||
2 Unused
|
||||
|
||||
|
||||
3 Unused
|
||||
|
||||
|
||||
4 Unused
|
||||
|
||||
|
||||
Commands available:
|
||||
(H)elp (T)utorial (D)elete (E)dit (R)eread (W)rite MBR (Q)uit
|
||||
(U)se entire disk for FreeBSD (G)eometry Write MBR (B)ootcode
|
||||
Enter Command>
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
|
||||
We see that drive 0 has a DOS partition (also called a "slice" in FreeBSD
|
||||
parlance, to distinguish it from a FreeBSD partition) on it which is 300MB
|
||||
in size (don't worry if the numbers you see are much smaller than these - I
|
||||
have a pretty large 2.1GB disk! :-). Let's also say we want to allocate
|
||||
the rest to FreeBSD, so to do this we want to (E)dit one of the existing
|
||||
slices. We can see that 2, 3, and 4 are unused so let's pick the first
|
||||
unused one, which is 2 (if we wanted to replace an existing operating
|
||||
system slice with FreeBSD, we'd pick its number instead). We first type
|
||||
`E' to edit a slice entry:
|
||||
|
||||
Enter Command> E
|
||||
|
||||
And we're prompted for a slice to edit. We type 2:
|
||||
|
||||
Edit which Slice> 2
|
||||
|
||||
Now we're prompted for the size of the new slice, the default for which is
|
||||
all remaining space on the disk. Let's say that we don't want to allocate
|
||||
ALL the space on the disk, but want to reserve 400MB for some other future
|
||||
OS. The total amount of free space left is 1706MB, which is the default
|
||||
value selected for us, so we backspace over it and enter 1306:
|
||||
|
||||
Size of slice in MB> 1306
|
||||
|
||||
Now we're asked for the type of the slice. The type is what tells the PC
|
||||
what sort of slice this is. DOS primary slices are, for example, type 6.
|
||||
FreeBSD slices are type 0xa5 (hexadecimal). If we wanted to reserve space
|
||||
at this time for some other type of OS like Linux or OS/2, and we knew
|
||||
their slice type (0x82 for Linux and 0x0A for OS/2, just in case you're
|
||||
interested), we could also do that from this editor, but we're only
|
||||
interested in FreeBSD for now so we accept the default.
|
||||
|
||||
Type of slice (0xa5=FreeBSD)> 0xa5
|
||||
|
||||
The next prompt asks if we want to make this slice bootable by
|
||||
default, which we do so we accept the default:
|
||||
|
||||
Bootflag (0x80 for YES)> 0x80
|
||||
|
||||
At this point we come back to the main screen, which now shows a new entry
|
||||
for slice 2:
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- FDISK
|
||||
|
||||
Disk: sd0 Geometry: 2006 Cyl * 32 Hd * 64 Sect = 2006Mb = 4108600 Sect
|
||||
|
||||
1 Boot?=No Type=Primary 'big' DOS (> 32MB)
|
||||
Phys=(c0/h1/s1..c299/h63/s32) Sector=(32..614399)
|
||||
Size=300 MB, 299 Cylinders + 31 Tracks + 32 Sectors
|
||||
|
||||
2 Boot?=Yes Type=FreeBSD/NetBSD/386BSD
|
||||
Phys=(c300/h0/s1..c1023/h31/s0) Sector=(614400..3289087)
|
||||
Size=1306 MB, 1306 Cylinders
|
||||
|
||||
3 Unused
|
||||
|
||||
|
||||
|
||||
4 Unused
|
||||
|
||||
|
||||
|
||||
Commands available:
|
||||
(H)elp (T)utorial (D)elete (E)dit (R)eread (W)rite MBR (Q)uit
|
||||
(U)se entire disk for FreeBSD (G)eometry Write MBR (B)ootcode
|
||||
Enter Command>
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
|
||||
At this point we're happy with the slices on the first drive, so we type
|
||||
`w' to write the new information out. It also prompts to make *sure* we
|
||||
really want to do this, so we backspace over the default of `N' and type
|
||||
`y'<return>. And this point, we also can decide whether or not we want a
|
||||
"boot manager" installed. A boot manager is a little utility that prompts
|
||||
you for the operating system you want to boot every time you reset or power
|
||||
on your PC, and can be a very handy way of sharing your computer between
|
||||
FreeBSD and some other OS, like Linux or DOS. We decide that we want to
|
||||
have this feature, so we `b' to write the special MBR (B)ootcode out to the
|
||||
disk. This does not harm any of the other operating systems on the disk,
|
||||
as it's written to a special area. Now we exit this screen by typing `q',
|
||||
for (Q)uit.
|
||||
|
||||
This brings us back to the main prompt. If we wanted to allocate any
|
||||
additional slices on other drives, we also could re-invoke the (F)disk
|
||||
editor by typing `f' again and giving a different drive number at the
|
||||
prompt, but we'll assume for now that we've only got one disk and want to
|
||||
go on. Typing `d' now enters the (D)isklabel screen, which prompts us for
|
||||
the drive to write a disklabel onto, like the FDISK editor. We type `0'
|
||||
for the first drive and hit return. This brings us to the DISKLABEL editor
|
||||
screen, which looks like this:
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
FreeBSD 2.0-RELEASE Installation -- Diskspace editor -- DISKLABEL
|
||||
|
||||
Part Start End Blocks MB Type Action Mountpoint
|
||||
a 0 0 0 0 unused
|
||||
b 0 0 0 0 unused
|
||||
c 1433600 4108287 2674688 1306 unused <Entire FreeBSD slice>
|
||||
d 0 4108599 4108600 2006 unused <Entire Disk>
|
||||
e 0 0 0 0 unused
|
||||
f 0 0 0 0 unused
|
||||
g 0 0 0 0 unused
|
||||
h 32 614399 614368 300 MSDOS
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
|
||||
Total size: 2674688 blocks 1306Mb
|
||||
Space allocated: 0 blocks 0Mb
|
||||
|
||||
Commands available:
|
||||
(H)elp (T)utorial (E)dit (A)ssign (D)elete (R)eread (W)rite (Q)uit
|
||||
(P)reserve (S)lice
|
||||
Enter Command>
|
||||
|
||||
------------------------------------------------------------------------------
|
||||
|
||||
The BSD partitions, a - h, are FreeBSD's way of dividing up a physical
|
||||
slice into multiple file systems. Every FreeBSD system should have, at
|
||||
minimum, a root file system and a swap partition allocated. The root
|
||||
file system is called "/", and is generally put on partition `a' by
|
||||
convention. Swap partitions always go on `b', and the `c' and `d'
|
||||
partitions are special and point to the entire FreeBSD slice and the entire
|
||||
disk, respectively. `c' and `d' cannot and should not be allocated to
|
||||
actual file systems.
|
||||
|
||||
We also see that partition h points conveniently to the DOS slice,
|
||||
which we can also assign to a location in our file system hierarchy
|
||||
to conveniently share files between FreeBSD and DOS. More on this in
|
||||
a moment.
|
||||
|
||||
A typical file system layout might look like this:
|
||||
|
||||
/ 20MB
|
||||
swap 32MB
|
||||
/usr 120MB
|
||||
|
||||
/, or the root file system, contains system files and some temporary space.
|
||||
It should be at least 18MB in size, though a little extra doesn't hurt.
|
||||
Swap space is one of those "it never hurts to have too much" sorts of
|
||||
items, though if your system isn't too heavily used then it's probably not
|
||||
that important to have lots and lots of it. A good rule of thumb for swap
|
||||
is that you want a minimum of 12MB of it, and the overall calculation
|
||||
should be the amount of memory you have multiplied by two. That is to
|
||||
say that if you have 16MB of memory, then 32MB of swap is good.
|
||||
|
||||
If you've got several drives, you can also allocate some swap on each one
|
||||
and spread the load out a little. On my personal system, I've got 32MB of
|
||||
main memory and 64MB of swap on both drives for a total of 128MB of swap.
|
||||
This gives me 4X memory for total program swapping, which gives me the
|
||||
ability to run some pretty big programs! Emacs and the X Window System, in
|
||||
particular, can be real swap hogs.
|
||||
|
||||
In any case, we'll assume for the moment that we're still configuring the
|
||||
ideal system and we'll allocate 64MB of swap space, using the MEM * 2
|
||||
equation. If you only had 8MB of memory, you'd allocate 16MB of swap
|
||||
instead.
|
||||
|
||||
The second file system of importance is /usr, which contains further system
|
||||
binaries and all of the bundled user binaries. /usr should be at least
|
||||
80MB in size to hold all of the important binaries, though if you plan on
|
||||
having a big /usr/local or on loading the X Window System (also known as
|
||||
XFree86 3.1) distribution then you should either create separate
|
||||
file systems for them, or you should make /usr a lot bigger.
|
||||
|
||||
It's also possible to skip making /usr altogether and simply make a large
|
||||
root (/) file system. Since /usr fits "underneath" /, a missing /usr won't
|
||||
cause any problems if / is large enough to hold the contents for both. In
|
||||
any case, it's a user decision and tends to be driven by convention more
|
||||
than anything else. For the purposes of this installation guide, we'll
|
||||
assume a 200MB /usr, 100MB of space allocated for local binaries, which
|
||||
we'll mount on /usr/local, and the rest for user home directories, which
|
||||
we'll mount on /usr/users. Don't be put off by the size of these numbers!
|
||||
You can make a system fit into less space, but since we're dividing up the
|
||||
ideal 2GB dream disk, we might as well do it right! ;-)
|
||||
|
||||
Getting back to the relevant part of the DISKLABEL screen again, we remember
|
||||
that it looked like this:
|
||||
|
||||
Part Start End Blocks MB Type Action Mountpoint
|
||||
a 0 0 0 0 unused
|
||||
b 0 0 0 0 unused
|
||||
c 1433600 4108287 2674688 1306 unused <Entire FreeBSD slice>
|
||||
d 0 4108599 4108600 2006 unused <Entire Disk>
|
||||
e 0 0 0 0 unused
|
||||
f 0 0 0 0 unused
|
||||
g 0 0 0 0 unused
|
||||
h 32 614399 614368 300 MSDOS
|
||||
|
||||
So we'll first allocate some space on partition `a' for that root partition
|
||||
by typing `e', for (E)dit partition. This asks us which partition we want
|
||||
to change the size of, so we type `a':
|
||||
|
||||
Change size of which partition> a
|
||||
|
||||
And it prompts us for the amount of space, so we'll pick 20MB for a nice
|
||||
comfortable root file system:
|
||||
|
||||
Size of partition in MB> 20
|
||||
|
||||
Now we see the display change to:
|
||||
|
||||
Part Start End Blocks MB Type Action Mountpoint
|
||||
a 1433600 1474559 40960 20 4.2BSD
|
||||
...
|
||||
|
||||
The system shows us where the partition starts and stops and indicates that
|
||||
it's a 4.2BSD file system, which is correct (it's really a 4.4 BSD file
|
||||
system, in actuality, but the two are similar enough to share the same
|
||||
label).
|
||||
|
||||
We do the same for swap by typing `e' again and modify the `b' partition
|
||||
by filling in 64 for the size, to allocate 64MB of swap.
|
||||
|
||||
Finally, remembering that `c' and `d' are special, and not for our use, we
|
||||
change the size of `e' to 200 for our future /usr, `f' to 100 for our
|
||||
/usr/local, and `g' to the rest of the disk for /usr/users. When we're
|
||||
done, the top of the disklabel screen should look like this:
|
||||
|
||||
Part Start End Blocks MB Type Action Mountpoint
|
||||
a 1433600 1474559 40960 20 4.2BSD
|
||||
b 1474560 1605631 131072 64 swap
|
||||
c 1433600 4108287 2674688 1306 unused <Entire FreeBSD slice>
|
||||
d 0 4108599 4108600 2006 unused <Entire Disk>
|
||||
e 1605632 2015231 409600 200 4.2BSD
|
||||
f 2015232 2220031 204800 100 4.2BSD
|
||||
g 2220032 4108287 1888256 922 4.2BSD
|
||||
h 32 614399 614368 300 MSDOS
|
||||
|
||||
We left `h' alone, since we actually want to be able to share files with
|
||||
our DOS partition. At this point, we want to type `w' for (W)rite to write
|
||||
out the new size information to disk.
|
||||
|
||||
You probably also noticed by now that "/", "/usr" and the other file system
|
||||
names we've been talking about don't appear anywhere in the above list.
|
||||
Where are they? This brings us to the next stage, which is to (A)ssign the
|
||||
new partitions to actual file system mount points. A file system in
|
||||
FreeBSD doesn't actually appear anywhere until we "mount" it someplace, a
|
||||
convention from the old days when disks were actually large removable packs
|
||||
that a system operator physically mounted on a large washing-machine sized
|
||||
disk drive spindle! As you can see, not much has changed today! :-)
|
||||
|
||||
We'll proceed then by starting at the top with the first partition and
|
||||
assigning it to the root file system (/) by typing `a', for (A)ssign, and
|
||||
then typing `a' again, for partition a:
|
||||
|
||||
Assign which partition> a
|
||||
|
||||
When it asks us for the name of the mount point, we type /:
|
||||
|
||||
Directory mountpoint> /
|
||||
|
||||
And the display adjusts accordingly to show us the new state of affairs:
|
||||
|
||||
Part Start End Blocks MB Type Action Mountpoint
|
||||
a 1433600 1474559 40960 20 4.2BSD newfs /
|
||||
..
|
||||
|
||||
The Action field also now shows "newfs", which means that the partition
|
||||
will be created anew. For root file systems, this is the default and cannot
|
||||
be changed, but other partitions can be optionally "Preserved" by typing
|
||||
`p' for (P)reserve. There are very few situations in which we'd want to do
|
||||
this, but if, say, we were actually installing a disk from an older FreeBSD
|
||||
machine which we wanted to mount into our new system but NOT erase, we
|
||||
could do it this way. For now, let's assume that this is a new
|
||||
installation and we want all the file systems to be created from scratch.
|
||||
We thus go through and assign the rest of the file systems to their
|
||||
respective /usr, /usr/local and /usr/users mountpoints. We also assign the
|
||||
`b' partition, which doesn't take a mountpoint (and won't prompt for one
|
||||
when we (A)ssign it), but needs us to tell it that we're ready to use it
|
||||
for swap.
|
||||
|
||||
When we're done, the top of the screen should look something like this:
|
||||
|
||||
Part Start End Blocks MB Type Action Mountpoint
|
||||
a 1433600 1474559 40960 20 4.2BSD newfs /
|
||||
b 1474560 1605631 131072 64 swap swap swap
|
||||
c 1433600 4108287 2674688 1306 unused <Entire FreeBSD slice>
|
||||
d 0 4108599 4108600 2006 unused <Entire Disk>
|
||||
e 1605632 2015231 409600 200 4.2BSD newfs /usr
|
||||
f 2015232 2220031 204800 100 4.2BSD newfs /usr/local
|
||||
g 2220032 4108287 1888256 922 4.2BSD newfs /usr/users
|
||||
h 32 614399 614368 300 MSDOS
|
||||
|
||||
As a final bonus, we'll assign the DOS partition to be mounted on /dos. We
|
||||
do this with (A)ssign as we did the others, and we also notice that the
|
||||
system is smart enough to see that it's not a FreeBSD partition and we
|
||||
DON'T want to newfs it, we want to simply mount it:
|
||||
|
||||
h 32 614399 614368 300 MSDOS mount /dos
|
||||
|
||||
At this point, our system is all set up and ready to go!
|
||||
|
||||
We type `q' to go back to the main menu and then type `p' to (P)roceed to
|
||||
the next phase of installation.
|
||||
|
||||
We're now given one last chance to back out of the install, and we hit
|
||||
return if we're sure, otherwise we type <Tab> to select "No" and hit return
|
||||
to consider our settings again before going on.
|
||||
|
||||
The rest of the installation is pretty much self-explanatory. After the
|
||||
file systems are initially created and populated, you'll be prompted to
|
||||
reboot from the hard disk. Do so and provide the cpio floppy when asked.
|
||||
|
||||
When the initial flurry of welcome and informational prompts has died down,
|
||||
you'll come to a screen asking you to load one or more distributions. At
|
||||
the minimum, select "bindist" to load the basic system. If you're loading
|
||||
from other than CDROM media, follow the appropriate paths through the
|
||||
installation process.
|
||||
|
||||
If you're loading from CDROM, select CDROM as the media type and select the
|
||||
type of CDROM you've got (SCSI or Mitsumi). When it asks you for an
|
||||
installation subdirectory, simply hit return if you've got the 2.0 CD from
|
||||
Walnut Creek CDROM. You may select additional optional packages to load
|
||||
after the bindist extracts, provided that you've got the space for it. Use
|
||||
the "?diskfree" menu option from time to time to keep an eye on your free
|
||||
space. When you're done, you'll be asked a few more basic questions and
|
||||
then that's it! You've got FreeBSD on your hard disk.
|
||||
|
||||
If you should need to partition another drive or install other packages
|
||||
later, you may re-invoke the sysinstall program by typing /sbin/sysinstall.
|
||||
The same familiar prompts will then come up.
|
||||
|
||||
Good luck!
|
||||
|
||||
Jordan Hubbard
|
||||
for Walnut Creek CDROM
|
||||
and the FreeBSD Project.
|
||||
|
||||
|
||||
|
||||
</pre>
|
||||
|
||||
&footer;
|
||||
</body>
|
||||
</html>
|
||||
641
en/releases/2.0/notes.sgml
Normal file
641
en/releases/2.0/notes.sgml
Normal file
|
|
@ -0,0 +1,641 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY date "$Date: 1996-09-24 17:45:54 $">
|
||||
<!ENTITY title "FreeBSD 2.0 Release Notes">
|
||||
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
|
||||
]>
|
||||
<html>
|
||||
&header;
|
||||
|
||||
<pre>
|
||||
|
||||
RELEASE NOTES
|
||||
FreeBSD
|
||||
Release 2.0
|
||||
|
||||
1. Technical overview
|
||||
---------------------
|
||||
|
||||
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 first release of FreeBSD 1.0 some 18 months ago, FreeBSD
|
||||
has changed almost entirely. A new port from the Berkeley 4.4 code
|
||||
base was done, which brought the legal status of the system out of the
|
||||
shadows with the blessing of Novell (new owners of USL and UNIX). The
|
||||
port to 4.4 has also brought in a host of new features, filesystems
|
||||
and enhanced driver support. With our new unencumbered code base, we
|
||||
have every reason to hope that we'll be able to release quality
|
||||
operating systems without further legal encumbrance for some time to
|
||||
come!
|
||||
|
||||
FreeBSD 2.0 represents the culmination of almost 2 years of work and
|
||||
many thousands of man hours put in by an international development team.
|
||||
We hope you enjoy it!
|
||||
|
||||
Many packages have also been upgraded or added, such as XFree86 3.1,
|
||||
xview 3.2, elm, nntp, mh, InterViews and dozens of other miscellaneous
|
||||
utilities have been ported and are now available as add-ons. See the
|
||||
ports collection (or the package collection) for a complete summary.
|
||||
|
||||
For a list of contributors, please see the file "CONTRIB.FreeBSD",
|
||||
which should be bundled with your bindist distribution.
|
||||
|
||||
Also see the new "REGISTER.FreeBSD" file for information on registering
|
||||
with the "Free BSD user counter". We've also provided a list of who's
|
||||
responsible for what (so that you may query them directly) in the
|
||||
"ROSTER.FreeBSD" file; use of this file is encouraged to ensure faster
|
||||
resolution of any problems you may have!
|
||||
|
||||
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 auxilliary 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 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!
|
||||
|
||||
|
||||
1.1 What's new in 2.0?
|
||||
----------------------
|
||||
|
||||
4.4 Lite
|
||||
--------
|
||||
As previously stated, this release is based entirely on CSRG's
|
||||
latest (and last) BSD release - 4.4 Lite. This features a number
|
||||
of improvements over 4.2BSD (Net/2), not least of which are:
|
||||
|
||||
o Legal approval of Novell & U.C. Berkeley. After the settlement
|
||||
of the longstanding lawsuit between USL/UCB/Novell/BSDI, all
|
||||
parties were (strongly) encouraged to move to 4.4 Lite in order
|
||||
to avoid future legal entanglements. The fact that we've now done
|
||||
so should make this release much more attractive to potential
|
||||
commercial users.
|
||||
|
||||
o Many new filesystem types, such as stackable filesystems, union
|
||||
filesystems, "portals", kernfs, a simple log-structured filesystem, a
|
||||
new version of NFS (NQNFS), etc. While some of these new filesystems
|
||||
are also rather unpolished and will require significant additional
|
||||
work to be truly robust, they're a good start.
|
||||
|
||||
o 64bit offsets, allowing filesystems of up to 2^63 bytes in size.
|
||||
|
||||
o Further work towards full POSIX compliance.
|
||||
|
||||
IP multicast support
|
||||
--------------------
|
||||
The IP multicast support has been upgraded from the woefully ancient
|
||||
1.x code in 4.4-Lite to the most current and up-to-date 3.3 release
|
||||
from Steve D. and Ajit. The non-forwarding code is known to work (for
|
||||
some limited test cases). The multicast forwarder and user-mode
|
||||
multicast routing process are known to compile, but have not been
|
||||
significantly tested (hopefully this will happen before 2.0 release).
|
||||
|
||||
Owner: wollman
|
||||
Sources involved: sys/netinet, usr.sbin/mrouted
|
||||
|
||||
Loadable Kernel Modules
|
||||
-----------------------
|
||||
David Greenman incorporated NetBSD's port of Terry Lambert's loadable
|
||||
kernel module support. Garrett Wollman wrote the support for loadable
|
||||
file systems, and Søren Schmidt did the same for loadable execution
|
||||
classes.
|
||||
|
||||
Owner: core
|
||||
Sources involved: sys/kern, sbin/modload, sbin/modunload,
|
||||
usr.bin/modstat
|
||||
|
||||
|
||||
Loadable filesystems
|
||||
--------------------
|
||||
Most filesystems are now dynamically loadable on demand, with the
|
||||
exception of the UFS family (FFS, LFS, and MFS). With the exception
|
||||
of NFS, all such filesystems can be unloaded when all references are
|
||||
unmounted. To support this functionality, the getvfsbyname(3)
|
||||
family of functions has been added to the C library and the lsvfs(1)
|
||||
command provides the same information at the shell level. Be aware of
|
||||
the following current restrictions:
|
||||
|
||||
- /usr/bin may not reside on a dynamically loaded filesystem.
|
||||
- There must be a writable /tmp directory available
|
||||
before filesystems are loaded (moving / to the top of your
|
||||
/etc/fstab file will accomplish this).
|
||||
- Some of the more esoteric filesystems simply don't work when loaded
|
||||
dynamically (though they often don't work "static", either.)
|
||||
|
||||
Owner: wollman
|
||||
Sources involved: sys/*fs, lkm/*fs, usr.bin/lsvfs, lib/libc/gen
|
||||
|
||||
|
||||
S/Key
|
||||
-----
|
||||
Since version 1.1.5, FreeBSD has supported the S/Key one time password
|
||||
scheme. The version used is derived from the logdaemon package of Wietse
|
||||
Venema.
|
||||
Some of the features new in 2.0 are:
|
||||
- New access control table format to impose the use of S/Keys
|
||||
based on: hostname, ip address, port, username, group id.
|
||||
- S/Key support can be disabled by not having the access control
|
||||
table.
|
||||
The second item explains the absence of skey.access in the installed /etc.
|
||||
To enable S/Key support, create a file skey.access in /etc and fill it
|
||||
according to your needs. See also skey.access(5) and the example in
|
||||
/usr/share/examples/etc/skey.access.
|
||||
|
||||
Owner: pst, guido
|
||||
Sources involved: lib/libskey, usr.bin/key* (plus patches to others)
|
||||
|
||||
|
||||
TCP/IP over parallel (printer) port
|
||||
-----------------------------------
|
||||
You can now run TCP/IP over a standard LapLink(tm) cable, if both ends
|
||||
have an interrupt-driven printerport. The interface is named "lp0"
|
||||
where '0' is the same as the lpt# unit number. This is not compatible
|
||||
with PLIP. If you run NFS, try setting MTU to 9180, otherwise leave
|
||||
it at 1500 unless you have a good reason to change it. Speed varies
|
||||
with the CPU-type, with up to 70 kbyte/sec having been seen and 50
|
||||
kbyte/sec being the norm.
|
||||
|
||||
Owner: phk
|
||||
Sources involved: isa/lpt.c
|
||||
|
||||
|
||||
ProAudioSpectrum SCSI driver
|
||||
----------------------------
|
||||
If you have a PAS board with a CD-ROM, and the MS-DOS driver is called
|
||||
TSLCDR.SYS, then the "pas" driver should work on your card. You can
|
||||
attach disks, cdroms and tapes, but due to the nature of the hardware
|
||||
involved, the transfer rate is limited to < 690 kbyte/sec. For CD-ROM
|
||||
use, this is generally more than enough.
|
||||
|
||||
Owner: phk
|
||||
Sources involved: isa/pas.c
|
||||
|
||||
|
||||
Adaptec 2742/2842 SCSI driver
|
||||
-----------------------------
|
||||
Despite the non-cooperation of Adaptec in providing technical
|
||||
information, we now have a driver for the AHA-274x and AHA-284x
|
||||
series SCSI controller family. This driver uses the GPL'd
|
||||
Linux sequencer code, so until we find an alternative, this
|
||||
will be part of the kernel that requires source code to be
|
||||
distributed with it at all times. This shouldn't be a problem
|
||||
for any of FreeBSD's current users.
|
||||
|
||||
Owner: gibbs
|
||||
Sources involved: isa/aic7770.c sys/gnu/misc/*
|
||||
|
||||
|
||||
Gzip'd binaries
|
||||
----------------
|
||||
We have an experimental implementation for direct execution of gzip'ed
|
||||
binaries in this release. When enabled, it allows you to simply gzip
|
||||
your binaries, remove the '.gz' extension and make the file
|
||||
executable. There is a big speed and memory consumption penalty for
|
||||
doing this, but for laptop users it may be worthwhile. The maximum
|
||||
savings are generally around 10 Mb of disk space.
|
||||
|
||||
Owner: phk
|
||||
Sources involved: kern/imgact_gzip.c kern/inflate.c
|
||||
|
||||
|
||||
Diskless booting
|
||||
----------------
|
||||
|
||||
Diskless booting in 2.0 is much improved since 1.1.5. The
|
||||
boot-program is in src/sys/i386/boot/netboot, and can be run from an
|
||||
MSDOS system or burned into an EPROM. Local swapping is also
|
||||
possible. WD, SMC, 3COM and Novell ethernet cards are currently
|
||||
supported.
|
||||
|
||||
Owner: Martin Renters & phk
|
||||
Sources involved: i386/boot/netboot, sys/nfs/nfs_vfsops.h
|
||||
|
||||
|
||||
Device configuration database
|
||||
-----------------------------
|
||||
The kernel now keeps better track of which device drivers are active and
|
||||
where the devices are attached; this information is made available to
|
||||
user programs via the new sysctl(3) management interface. Current
|
||||
applications include lsdev(8), which lists the currently configured
|
||||
devices. In the future, we expect to use this code to automatically
|
||||
generate a configuration file for you at installation time.
|
||||
|
||||
Owner: wollman
|
||||
Sources involved: sys/i386, sys/scsi, sys/kern/kern_devconf.c,
|
||||
sys/sys/devconf.h, usr.sbin/lsdev
|
||||
|
||||
|
||||
Kernel management interface
|
||||
---------------------------
|
||||
With 4.4-Lite, we now have a better management interface for the endless
|
||||
series of kernel variables and parameters which were previously manipulated
|
||||
by reading and writing /dev/kmem. Many programs have been rewritten to
|
||||
use this interface, although many old-style programs still remain. Some
|
||||
variables which were never accessible before are now available through
|
||||
the sysctl(1) program. In addition to the standard 4.4BSD MIB variables,
|
||||
we have added support for YP/NIS domains (kern.domainname), controlling
|
||||
the update daemon (kern.update), retrieving the OS release date
|
||||
(kern.osreldate), determining the name of the booted kernel (kern.bootfile),
|
||||
and checking for hardware floating-point support (hw.floatingpoint).
|
||||
We have also added support to make management queries of devices and
|
||||
filesystems.
|
||||
|
||||
Owner: core
|
||||
Sources involved: sys, usr.bin/sysctl
|
||||
|
||||
|
||||
iBCS2 support
|
||||
-------------
|
||||
FreeBSD now supports running iBCS2 compatible binaries (currently
|
||||
SCO UNIX 3.2.2 & 3.2.4 and ISC 2.2 COFF format are supported).
|
||||
The iBCS2 emulator is in its early stages, but it is functional, we
|
||||
haven't been able to do exhaustive testing (lack of commercial apps),
|
||||
but almost all of SCO's 3.2.2 binaries are working, so is an old
|
||||
INFORMIX-2.10 for SCO. Further testing is nessesary to complete this
|
||||
project. There is also work under way for ELF & XOUT loaders, and
|
||||
most of the svr4 syscall wrappers have been written.
|
||||
|
||||
Owner: Soren Schmidt (sos) & Sean Eric Fagan (sef)
|
||||
Sources involved: sys/i386/ibcs2/* + misc kernel 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.
|
||||
|
||||
Following is a list of all currently known disk controllers and
|
||||
ethernet cards known to work with FreeBSD. Other configurations may
|
||||
very well work, and we have simply not received any indication of
|
||||
this.
|
||||
|
||||
|
||||
2.1. Disk Controllers
|
||||
|
||||
WD1003 (any generic MFM/RLL)
|
||||
WD1007 (any generic IDE/ESDI)
|
||||
[Note: the new Extended IDE controllers in newer PC's work, although no
|
||||
extended features are used.]
|
||||
|
||||
Adaptec 152x series ISA SCSI controllers
|
||||
Adaptec 154x series ISA SCSI controllers
|
||||
Adaptec 174x series EISA SCSI controller in standard and enhanced mode.
|
||||
Adaptec 2742/2842 series ISA/EISA 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, which is 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. Check your system/board documentation
|
||||
for more details.
|
||||
|
||||
[Note that Buslogic was formerly known as "Bustec"]
|
||||
Buslogic 545S & 545c
|
||||
Buslogic 445S/445c VLB SCSI controller
|
||||
Buslogic 742A, 747S, 747c EISA SCSI controller.
|
||||
Buslogic 946c PCI SCSI controller
|
||||
|
||||
NCR 53C810 and 53C825 PCI 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.
|
||||
|
||||
With all supported SCSI controllers, full support is provided for
|
||||
SCSI-I & SCSI-II peripherals, including Disks, tape drives (including
|
||||
DAT) and CD ROM drives. Note: This and the mcd driver (Mitsumi CDROM
|
||||
interface card) are the only way a CD ROM drive may be currently
|
||||
attached to a FreeBSD system; we do not support SoundBlaster
|
||||
(non-SCSI) CDROM interface, or other "non-SCSI" adapters. The
|
||||
ProAudio Spectrum SCSI and SoundBlaster SCSI controllers are
|
||||
supported.
|
||||
|
||||
Some controllers have limitations with the way they deal with >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 >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 or Adaptec
|
||||
1742A) 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.
|
||||
|
||||
|
||||
2.2. Ethernet cards
|
||||
|
||||
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.
|
||||
|
||||
DEC EtherWORKS III NICs (DE203, DE204, and DE205)
|
||||
DEC EtherWORKS II NICs (DE200, DE201, DE202, and DE422)
|
||||
|
||||
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 3C507 Etherlink 16/TP
|
||||
|
||||
3Com 3C509 and 3C579 Etherlink III
|
||||
|
||||
Toshiba ethernet cards
|
||||
|
||||
PCMCIA ethernet cards from IBM and National Semiconductor are also
|
||||
supported.
|
||||
|
||||
2.3. Misc
|
||||
|
||||
AST 4 port serial card using shared IRQ.
|
||||
|
||||
ARNET 8 port serial card using shared IRQ.
|
||||
|
||||
BOCA ATIO66 6 port serial card using shared IRQ.
|
||||
|
||||
STB 4 port card using shared IRQ.
|
||||
|
||||
Mitsumi (all models) CDROM interface and drive.
|
||||
|
||||
Soundblaster SCSI and ProAudio Spectrum SCSI CDROM interface and drive.
|
||||
|
||||
Adlib, Soundblaster, Soundblaster Pro, ProAudioSpectrum, Gravis UltraSound
|
||||
and Roland MPU-401 sound cards.
|
||||
|
||||
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.
|
||||
|
||||
|
||||
3. Obtaining FreeBSD.
|
||||
---------------------
|
||||
|
||||
You may obtain FreeBSD in a variety of ways:
|
||||
|
||||
1. FTP/Mail
|
||||
|
||||
You can ftp FreeBSD and any or all of its optional packages from
|
||||
`freebsd.cdrom.com' - the offical FreeBSD release site.
|
||||
|
||||
For other locations that mirror the FreeBSD software see the file
|
||||
MIRROR.SITES. Please ftp the distribution from the nearest site
|
||||
to you netwise.
|
||||
|
||||
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@decwrl.dec.com' - putting the keyword "help" in your message
|
||||
to get more information on how to fetch files from freebsd.cdrom.com.
|
||||
Note: This approach will end up sending many *tens of megabytes*
|
||||
through the mail, and should only be employed as an absolute LAST
|
||||
resort!
|
||||
|
||||
|
||||
2. CDROM
|
||||
|
||||
FreeBSD 2.0 may be ordered on CDROM from:
|
||||
|
||||
Walnut Creek CDROM
|
||||
4041 Pike Lane, Suite D
|
||||
Concord CA 94520
|
||||
1-800-786-9907, +1-510-674-0783, +1-510-674-0821 (fax)
|
||||
|
||||
Or via the internet from orders@cdrom.com. Their current catalog can
|
||||
be obtained via ftp as ftp.cdrom.com:/cdrom/catalog.
|
||||
|
||||
Cost is $39.95. Shipping (per order not per disc) is $5 in the US, Canada,
|
||||
or Mexico and $10.00 overseas. They accept Visa, Mastercard, American
|
||||
Express, and ship COD to 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.
|
||||
|
||||
Note that Walnut Creek CDROM does NOT provide technical support for FreeBSD,
|
||||
you need to contact the FreeBSD team for that. Please see section 5 for
|
||||
more information.
|
||||
|
||||
|
||||
4. Preparing for the installation.
|
||||
----------------------------------
|
||||
|
||||
1. Floppy Installation
|
||||
|
||||
If you must install from floppy disks, either due to space contraints
|
||||
on your hard disk or just because you enjoy doing things the hard
|
||||
way, you must first prepare some floppies for the install.
|
||||
|
||||
You will need either 10 1.44MB floppies or 12 1.2MB floppies to
|
||||
store just the bindist (binary distribution). These *must* be
|
||||
formatted using MS-DOS, using either the FORMAT command in MS-DOS
|
||||
or the File Manager in Microsoft Windows to prepare the floppies
|
||||
(though factory preformatted floppies will also well well, provided
|
||||
that they haven't been previously used for something else).
|
||||
|
||||
After you've formatted the floppy disks, you'll need to copy the
|
||||
files onto them. There are 56 total files for the bindist itself,
|
||||
plus three small files (CKSUMS, do_cksum.sh, and extract.sh) for
|
||||
the install program to use. ALL of these files must be copies onto
|
||||
the floppies. Each of the bindist files are named "bindist.??",
|
||||
where the "??" is replaced by the letter sequence aa through cd.
|
||||
Copy these files onto the floppies, placing the three small install
|
||||
files onto the final floppy. The order in which you copy the files
|
||||
to floppy is not important, but it makes labelling the disks easier
|
||||
if you go in some sort of alphabetical order.
|
||||
|
||||
After you've done this, the floppy disks are ready for the install
|
||||
program to use.
|
||||
|
||||
Later on, after you get the binary distribution installed and everything
|
||||
is going great, the same instructions will apply for the other
|
||||
distributions, such as the manpages distribution or the XFree86 distribution.
|
||||
The number of floppies required will, of course, change for bigger or
|
||||
smaller distributions.
|
||||
|
||||
|
||||
2. Hard Disk Installation
|
||||
|
||||
To prepare for installation from an MS-DOS partition, you should simply
|
||||
copy the files from the distribution into a directory with the same
|
||||
name as the distribution. For example, if you are preparing to
|
||||
install the bindist set, then make a directory on your C: drive named
|
||||
C:\BINDIST and copy the files there. This will allow the installation
|
||||
program to find the files automatically.
|
||||
|
||||
|
||||
3. QIC/SCSI Tape Installation.
|
||||
|
||||
Installing from tape is probably the easiest method, short of an
|
||||
on-line install using ftp or installing from a CDROM. The installation
|
||||
program expects the files to be simply tar'red onto the tape, so after
|
||||
getting all of the files for distribution you're interested in, simply
|
||||
tar them onto the tape with something like:
|
||||
|
||||
cd <where the *.?? files are>
|
||||
tar cvf /dev/rwt0 (or /dev/rst0) .
|
||||
|
||||
from a directory with just the distribution files in it. Make sure
|
||||
that you remember to put CKSUMS, do_cksum.sh, and extract.sh files
|
||||
in this directory as well!
|
||||
|
||||
If you wish to install multiple *dist releases from one tape, do the
|
||||
following:
|
||||
|
||||
1. cd to the parent directory of the distributions and put them on tape
|
||||
like so:
|
||||
tar cvf /dev/rwt0 (or /dev/rst0) bindist srcdist ...
|
||||
|
||||
2. Install the first distribution on the tape using the tape installation
|
||||
method as normal. Afterwards, *do not* erase the contents of the temporary
|
||||
directory. Get a shell with ESC-ESC and cd to the temporary directory
|
||||
yourself. For each additional *dist you want to load, cd to its
|
||||
subdirectory and type `sh ./extract.sh'.
|
||||
|
||||
|
||||
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. 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.
|
||||
|
||||
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:
|
||||
|
||||
bugs@FreeBSD.org
|
||||
|
||||
|
||||
Otherwise, for any questions or suggestions, please send mail to:
|
||||
|
||||
questions@FreeBSD.org
|
||||
|
||||
Additionally, being a volunteer effort, we are always happy to have
|
||||
extra hands willing to help - there are already far more enhancements
|
||||
to be done than we can ever manage to do by ourselves! To contact us
|
||||
on technical matters, or with offers of help, you may send mail to:
|
||||
|
||||
hackers@FreeBSD.org
|
||||
|
||||
Since these mailing lists can experience significant amounts of
|
||||
traffic, if you've got slow or expensive mail access and you're
|
||||
only interested in keeping up with significant FreeBSD events, you may
|
||||
find it preferable to subscribe to:
|
||||
|
||||
announce@FreeBSD.org
|
||||
|
||||
|
||||
All but the FreeBSD-bugs groups 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. It would be very difficult, if not
|
||||
impossible, to enumerate everyone who's contributed to FreeBSD, but
|
||||
nonetheless we shall try (in alphabetical order, of course). If your
|
||||
name is not mentioned, please be assured that its omission is entirely
|
||||
accidental.
|
||||
|
||||
|
||||
The Computer Systems Research Group (CSRG), U.C. Berkeley.
|
||||
|
||||
Bill Jolitz, for his extensive work with 386BSD.
|
||||
|
||||
The FreeBSD "core" team:
|
||||
|
||||
Andrew A. Chernov
|
||||
John Dyson
|
||||
Bruce Evans
|
||||
David Greenman
|
||||
Rodney W. Grimes
|
||||
Jordan K. Hubbard
|
||||
Poul-Henning Kamp
|
||||
Rich Murphey
|
||||
Gary Palmer
|
||||
Geoff Rehmet
|
||||
Paul Richards
|
||||
Soren Schmidt
|
||||
Andreas Schulz
|
||||
Jack Vogel
|
||||
Garrett A. Wollman
|
||||
|
||||
|
||||
Special mention to:
|
||||
|
||||
Robert Bruce and Jack Velte of Walnut Creek CDROM, without
|
||||
whose help (and continuing support) this release would never
|
||||
have been possible.
|
||||
|
||||
Dermot McDonnell for his donation of a Toshiba XM3401B CDROM
|
||||
drive.
|
||||
|
||||
The NetBSD group for their frequent assistance and commentary.
|
||||
|
||||
Additional FreeBSD helpers and beta testers:
|
||||
|
||||
J.T. Conklin Julian Elischer
|
||||
Sean Eric Fagan Jeffrey Hsu
|
||||
Terry Lambert L Jonas Olsson
|
||||
Chris Provenzano Dave Rivers
|
||||
Guido van Rooij Steven Wallace
|
||||
Atsushi Murai Scott Mace
|
||||
Andrew Moore Nate Williams
|
||||
|
||||
And everyone at Montana State University for their initial support.
|
||||
|
||||
|
||||
Thanks to everyone, especially those not mentioned, and we sincerely
|
||||
hope you enjoy this release of FreeBSD!
|
||||
|
||||
|
||||
The FreeBSD Core Team
|
||||
|
||||
Id: RELNOTES.FreeBSD,v 1.21 1994/12/02 20:27:11 jkh Exp
|
||||
|
||||
</pre>
|
||||
|
||||
&footer;
|
||||
</body>
|
||||
</html>
|
||||
Loading…
Add table
Add a link
Reference in a new issue