diff --git a/handbook/basics.sgml b/handbook/basics.sgml index d9d0f05061..a09764e502 100644 --- a/handbook/basics.sgml +++ b/handbook/basics.sgml @@ -1,97 +1,96 @@ - + Unix Basics The online manual

The most comprehensive documentation on FreeBSD is in the form of man pages. Nearly every program on the system comes with a short reference manual - explaining the basic operation and various argument. + explaining the basic operation and various arguments. These manuals can be view with the man command. Use of the man command is simple: man command where command is the name of the command you wish to learn about. For example, to learn more about ls command type: % man ls

The online manual is divided up into numbered sections: User commands System calls and error numbers Functions in the C libraries Device drivers File formats Games and other diversions Miscellaneous information System maintenance and operation commands in some cases, the same topic may appear in more than one section of the on-line manual. For example, there is a chmod user command and a chmod() system call. In this case, you can tell the man command which - you want by specifying the section: + one you want by specifying the section: % man 1 chmod which will display the manual page for the user command chmod. References to a particular section of the on-line manual are traditionally placed - in paranthesis in written documentation; so + in parenthesis in written documentation, so chmod(1) refers to the chmod - user command, while chmod(2) - means the system call. + user command and chmod(2) + refers to the system call.

This is fine if you know the name of the command and - forgot how to use it, but what if you cannot recall the + simply wish to know how to use it, but what if you cannot recall the command name? You can use man to search for keywords in the command descriptions by using the -k switch: % man -k mail With this command you will be presented with a list of commands that have the keyword `mail' in their - descriptions. This is the same as the separate command - apropos. + descriptions. This is actually functionally equivalent to + using the apropos command. -

You are seeing all those fancy commands in - /usr/bin, but don't even have the silliest idea - what most of the names do actually stand for? Simply - do a +

So, you are looking at all those fancy commands in + /usr/bin but don't even have the faintest idea + what most of them actually do? Simply do a % cd /usr/bin; man -f * or % cd /usr/bin; whatis * - which is the same. + which does the same thing. GNU Info files

FreeBSD includes many applications and utilities produced by the Free Software Foundation (FSF). In addition to man pages, these programs come with more extensive hypertext documents called info files which can be viewed with the info command or, if you installed emacs, the info mode of emacs. To use the info(1) command, simply type: - % info For a brief - introduction, type h, and for a quick + % info. For a brief + introduction, type h. For a quick command reference, type ?. diff --git a/handbook/bibliography.sgml b/handbook/bibliography.sgml index 97603b6cef..91b7e2b6da 100644 --- a/handbook/bibliography.sgml +++ b/handbook/bibliography.sgml @@ -1,148 +1,148 @@ - + Bibliography

While the manual pages provide the definitive reference for individual pieces of the FreeBSD operating system, they are notorious for not illustrating how to put the pieces together to make the whole operating system run smoothly. For this, there is no substitute for a good - book on Unix system administration, and a good users' - manual. + book on Unix system administration and a good users' + manual. Users' guides

Computer Systems Research Group, UC Berkeley. 4.4BSD User's Reference Manual. O'Reilly & Associates, Inc., 1994. ISBN 1-56592-075-9 Computer Systems Research Group, UC Berkeley. 4.4BSD User's Supplementary Documents. O'Reilly & Associates, Inc., 1994. ISBN 1-56592-076-7 Unix in a Nutshell. O'Reilly & Associates, Inc., 1990. ISBN 093717520X Administrators' guides

Albitz, Paul and Liu, Cricket. DNS and BIND. O'Reilly & Associates, Inc., 1993. ISBN 1-56592-010-4 Computer Systems Research Group, UC Berkeley. 4.4BSD System Manager's Manual. O'Reilly & Associates, Inc., 1994. ISBN 1-56592-080-5 Costales, Brian, et al. Sendmail. O'Reilly & Associates, Inc., 1993. ISBN 1-56592-056-2 Frisch, Æleen. Essential System Administration. O'Reilly & Associates, Inc., 1993. ISBN 0-937175-80-3 Hunt, Craig. TCP/IP Network Administration. O'Reilly & Associates, Inc., 1992. ISBN 0-937175-82-X Nemeth, Evi. Unix System Administration Handbook. 2nd ed. Prentice Hall, 1995. ISBN 0131510517 Programmers' guides

Asente, Paul. X Window System Toolkit. Digital Press. ISBN 1-55558-051-3 Computer Systems Research Group, UC Berkeley. 4.4BSD Programmer's Reference Manual. O'Reilly & Associates, Inc., 1994. ISBN 1-56592-078-3 Computer Systems Research Group, UC Berkeley. 4.4BSD Programmer's Supplementary Documents. O'Reilly & Associates, Inc., 1994. ISBN 1-56592-079-1 Ellis, Margaret A. and Stroustrup, Bjarne. The Annotated C++ Reference Manual. Addison-Wesley, 1990. ISBN 0-201-51459-1 Harbison, Samuel P. and Steele, Guy L. Jr. C: A Reference Manual. 3rd ed. Prentice Hall, 1991. ISBN 0-13-110933-2 Jolitz, William. "Porting UNIX to the 386". Dr. Dobb's Journal. January 1991-July 1992. Leffler, Samuel J. The Design and implementation of the 4.3BSD UNIX operating system. Addison-Wesley, 1989. Plauger, P. J. The Standard C Library. Prentice Hall, 1992. ISBN 0-13-131509-9 Wells, Bill. "Writing Serial Drivers for UNIX". Dr. Dobb's Journal. 19(15), December 1994. pp68-71, 97-99. Hardware reference

Stanley, Tom. ISA System Architecture. 3rd ed. Reading, Mass. : Addison-Wesley, 1995. ISBN 0201409968 Stanley, Tom. PCI System Architecture. 3rd ed. Reading, Mass. : Addison-Wesley, 1995. ISBN 0201409933 Van Gilluwe, Frank. The Undocumented PC. Reading, Mass: Addison-Wesley Pub. Co., 1994. ISBN 0-201-62277-7 Magazines and journals

The C/C++ Users Journal. R&D Publications Inc. ISSN 1075-2838 diff --git a/handbook/boothelp.sgml b/handbook/boothelp.sgml index 78db5f6c83..4354092744 100644 --- a/handbook/boothelp.sgml +++ b/handbook/boothelp.sgml @@ -1,50 +1,50 @@ - + %authors; %sections; ]> FreeBSD Installation <author> <name></name> </author> <abstract>Welcome to FreeBSD! This guide describes the FreeBSD installation process. To navigate through the sections in this guide using the <bf>up</bf> and - <bf>down</bf> arrow keys to select a section you wish to + <bf>down</bf> arrow keys to select the section you wish to read. Then use the <bf>right arrow</bf> or the <bf>enter key</bf> to view the section. You can backtrack through sections you have read by using the <bf>left arrow</bf>. </abstract> <chapt><heading>General information</heading> &nutshell; &history; &relnotes; &install; &troubleshooting; &bibliography; &eresources; &hw; &contrib; </book> </linuxdoc> diff --git a/handbook/contrib.sgml b/handbook/contrib.sgml index 433fd489d5..1632dcd464 100644 --- a/handbook/contrib.sgml +++ b/handbook/contrib.sgml @@ -1,318 +1,314 @@ -<!-- $Id: contrib.sgml,v 1.39 1995-12-05 00:55:45 asami Exp $ --> +<!-- $Id: contrib.sgml,v 1.40 1995-12-11 15:09:08 jkh Exp $ --> <!-- The FreeBSD Documentation Project --> <chapt><heading>FreeBSD contributor list<label id="contrib"></heading> <sect><heading>Derived software contributors</heading> <p>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 from the 4.4 BSD Lite release provided by 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 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 endeavors. <sect><heading>Hardware contributors</heading> <p>A special thank-you to Walnut Creek CDROM for providing the Pentium P5-90 and 486/DX2-66 EISA/VL systems that are 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. TRW Financial Systems, Inc. provided 130 PCs, three 68 GB fileservers, twelve ethernets, two routers and an ATM switch for debugging the diskless code. They also keep a couple of FreeBSD hackers alive and busy. Thanks! Thanks also to Dermot McDonnell for his donation of a Toshiba XM3401B CDROM drive. It's been most useful! Thanks to Chuck Robey <chuckr@eng.umd.edu> who's been contributing his floppy tape streamer for experimental work. <sect><heading>The FreeBSD core team<label id="contrib:core"></heading> <p>(in alphabetical order by first name): <itemize> <item>Andrey A. Chernov <ache@FreeBSD.org> <item>Bruce Evans <bde@FreeBSD.org> <item>David Greenman <davidg@FreeBSD.org> <item>Garrett A. Wollman <wollman@FreeBSD.org> <item>Gary Palmer <gpalmer@FreeBSD.org> <item>Jörg Wunsch <joerg@FreeBSD.org> <item>John Dyson <dyson@FreeBSD.org> <item>Jordan K. Hubbard <jkh@FreeBSD.org> <item>Justin Gibbs <gibbs@FreeBSD.org> <item>Peter Wemm <peter@FreeBSD.org> <item>Poul-Henning Kamp <phk@FreeBSD.org> <item>Rich Murphey <rich@FreeBSD.org> <item>Satoshi Asami <asami@FreeBSD.org> <item>Søren Schmidt <sos@FreeBSD.org> </itemize> <sect><heading>Who is responsible for what</heading> <p><descrip> <tag/President/ Jordan K. Hubbard <jkh@FreeBSD.org> <tag/Principal Architect/ David Greenman <davidg@FreeBSD.org> <tag/Documentation/ John Fieber <jfieber@FreeBSD.org> <tag/Internationalization/ Andrey A. Chernov <ache@FreeBSD.org> <tag/Networking/ Garrett A. Wollman <wollman@FreeBSD.org> <tag/Postmaster/ Jonathan M. Bresler <jmb@FreeBSD.org> <tag/Public Relations/ Jordan Hubbard <jkh@FreeBSD.org> <tag/Release Coordinator/ Jordan Hubbard <jkh@FreeBSD.org> <tag/Source Repository Manager/ Peter Wemm <peter@FreeBSD.org> <tag/Ports Manager/ Satoshi Asami <asami@FreeBSD.org> <tag/System Administration/ Gary Palmer <gpalmer@FreeBSD.org> <tag/Webmasters/ John Fieber <jfieber@FreeBSD.org> and James L. Robinson <jlrobin@FreeBSD.org> <tag/XFree86 Project, Inc. Liason/ Rich Murphey <rich@FreeBSD.org> </descrip> <sect><heading>Additional FreeBSD contributors</heading> <p>(in alphabetical order by first name): <itemize> <item>Adam David <adam@veda.is> <item>Adam Glass <glass@postgres.berkeley.edu> <item>Adrian T. Filipi-Martin <atf3r@agate.cs.virginia.edu> <item>Akito Fujita <fujita@zoo.ncl.omron.co.jp> <item>Alain Kalker <A.C.P.M.Kalker@student.utwente.nl> <item>Andras Olah <olah@cs.utwente.nl> <item>Andreas Klemm <andreas@knobel.GUN.de> <item>Andrew Herbert <andrew@werple.apana.org.au> <item>Andrew Moore <alm@FreeBSD.org> <item>Anthony Yee-Hang Chan <yeehang@netcom.com> <item>Atsushi Murai <amurai@spec.co.jp> <item>Bill Fenner <fenner@parc.xerox.com> <item>Bill Paul <wpaul@FreeBSD.org> <item>Bob Wilcox <bob@obiwan.uucp> <item>Brian Tao <taob@gate.sinica.edu.tw> <item>Charles Hannum <mycroft@ai.mit.edu> <item>Chet Ramey <chet@odin.INS.CWRU.Edu> <item>Chris G. Demetriou <cgd@postgres.berkeley.edu> <item>Chris Provenzano <proven@athena.mit.edu> <item>Chris Stenton <jacs@gnome.co.uk> <item>Chris Torek <torek@ee.lbl.gov> <item>Christian Gusenbauer <cg@fimp01.fim.uni-linz.ac.at> <item>Christoph Robitschko <chmr@edvz.tu-graz.ac.at> <item>Chuck Hein <chein@cisco.com> <item>Chuck Robey <chuckr@Glue.umd.edu> <item>Cornelis van der Laan <nils@guru.ims.uni-stuttgart.de> <item>Craig Struble <cstruble@vt.edu> <item>Cristian Ferretti <cfs@riemann.mat.puc.cl> <item>Curt Mayer <curt@toad.com> <item>Danny J. Zerkel <dzerkel@feephi.phofarm.com> <item>Dave Burgess <burgess@hrd769.brooks.af.mil> <item>Dave Chapeskie <dchapes@zeus.leitch.com> <item>Dave Rivers <rivers@ponds.uucp> <item>David Dawes <dawes@physics.su.OZ.AU> <item>David O'Brien <obrien@cs.ucdavis.edu> <item>Dean Huxley <dean@fsa.ca> <item>Dirk Froemberg <dirk@hal.in-berlin.de> <item>Don Whiteside <dwhite@anshar.shadow.net> <item>Donald Burr <d_burr@ix.netcom.com> <item>Eric L. Hernes <erich@lodgenet.com> <item>Frank Bartels <knarf@camelot.de> <item>Frank Durda IV <bsdmail@nemesis.lonestar.org> <item>Frank Maclachlan <fpm@crash.cts.com> <item>Frank Nobis <fn@trinity.radio-do.de> <item>Gary A. Browning <gab10@griffcd.amdahl.com> <item>Gary Clark II <gclarkii@FreeBSD.ORG> <item>Gary Jennejohn <gj%pcs.dec.com@inet-gw-1.pa.dec.com> <item>Gene Stark <stark@cs.sunysb.edu> <item>Guido van Rooij <guido@gvr.win.tue.nl> <item>Havard Eidnes <Havard.Eidnes@runit.sintef.no> <item>Hideaki Ohmon <ohmon@sfc.keio.ac.jp> <item>Holger Veit <Holger.Veit@gmd.de> <item>Ishii Masahiro, R. Kym Horsell <item>J.T. Conklin <jtc@winsey.com> <item>James Clark <jjc@jclark.com> <item>James da Silva <jds@cs.umd.edu> et al <item>Janusz Kokot <janek@gaja.ipan.lublin.pl> <item>Javier Martin Rueda <jmrueda@diatel.upm.es> <item>Jean-Marc Zucconi <jmz@FreeBSD.ORG> <item>Jim Wilson <wilson@moria.cygnus.com> <item>Jonathan Bresler < jmb@FreeBSD.ORG> <item>Josh MacDonald <jmacd@uclink.berkeley.edu> <item>Juergen Lock <nox@jelal.hb.north.de> <item>Julian Elischer <julian@dialix.oz.au> <item>Julian Stacey <stacey@guug.de> (fallback: <julian@meepmeep.pcs.com>) <item>Keith Bostic <bostic@toe.CS.Berkeley.EDU> <item>Keith Moore <?> <item>Kirk McKusick <mckusick@mckusick.com> <item>Kurt Olsen <kurto@tiny.mcs.usu.edu> <item>L Jonas Olsson <ljo@po.cwru.edu> <item>Lars Fredriksen <fredriks@mcs.com> <item>Lucas James <Lucas.James@ldjpc.apana.org.au> <item>Marc Frajola <marc@dev.com> <item>Marc Ramirez <mrami@mramirez.sy.yale.edu <item>Marc van Kempen <wmbfmk@urc.tue.nl> <item>Mark Murray <mark@grondar.za> <item>Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu> <item>Martin Birgmeier <item>Martin Renters <martin@innovus.com> <item>Matt Thomas <thomas@lkg.dec.com> <item>Michael Elbel <me@freebsd.org> <item>Michael Smith <msmith@atrad.adelaide.edu.au> <item>Mike Pritchard <mpp@mpp.minn.net> <item>NIIMI Satoshi <sa2c@and.or.jp> <item>Nate Williams <nate@FreeBSD.org> <item>Nobuhiro Yasutomi <nobu@psrc.isac.co.jp> <item>Nobuyuki Koganemaru <kogane@kces.koganemaru.co.jp> <item>Ollivier Robert <roberto@FreeBSD.org> <item>Paul Kranenburg <pk@cs.few.eur.nl> <item>Paul Mackerras <paulus@cs.anu.edu.au> <item>Paul Richards <paul@FreeBSD.org> <item>Paul Traina <pst@cisco.com> <item>Peter Dufault <dufault@hda.com> <item>Peter Wemm <peter@haywire.DIALix.COM> <item>Philippe Charnier <charnier@lirmm.fr> <item>Richard Stallman <rms@gnu.ai.mit.edu> <item>Rob Shady <rls@id.net> <item>Rob Snow <rsnow@txdirect.net> <item>Rodney W. Grimes <rgrimes@FreeBSD.org> <item>Sascha Wildner <swildner@channelz.GUN.de> <item>Scott Blachowicz <scott@sabami.seaslug.org> <item>Scott Mace <smace@FreeBSD.org> <item>Sean Eric Fagan <sef@kithrup.com> <item>Serge V. Vakulenko <vak@zebub.msk.su> <item>Stefan Esser <se@MI.Uni-Koeln.DE> <item>Stephen McKay <syssgm@devetir.qld.gov.au> <item>Steve Gerakines <steve2@genesis.tiac.net> <item>Steve Passe <smp@csn.net> <item>Steven Wallace <swallace@ece.uci.edu> <item>Tatsumi Hosokawa <hosokawa@mt.cs.keio.ac.jp> <item>Terry Lee <terry@uivlsi.csl.uiuc.edu> <item>Theo Deraadt <deraadt@fsa.ca> <item>Thomas Gellekum <thomas@ghpc8.ihf.rwth-aachen.de> <item>Tom Samplonius <tom@misery.sdf.com> <item>Torbjorn Granlund <tege@matematik.su.se> <item>Torsten Blum <torstenb@FreeBSD.ORG> <item>Ugen J.S.Antsilevich <ugen@latte.WorldBank.org> <item>Werner Griessl <werner@btp1da.phy.uni-bayreuth.de> <item>Wolfgang Stanglmeier <wolf@kintaro.cologne.de> <item>Wolfram Schneider <wosch@cs.tu-berlin.de> <item>Yuval Yarom <yval@cs.huji.ac.il> <item>Yves Fonk <yves@cpcoup5.tn.tudelft.nl> </itemize> <sect><heading>386BSD Patch kit patch contributors</heading> <p>(in alphabetical order by first name): <itemize> <item>Adam Glass <glass@postgres.berkeley.edu> <item>Adrian Hall <adrian@ibmpcug.co.uk> <item>Andrey A. Chernov <ache@astral.msk.su> <item>Andrew Herbert <andrew@werple.apana.org.au> <item>Andrew Moore <alm@netcom.com> <item>Andy Valencia <ajv@csd.mot.com> <jtk@netcom.com> <item>Arne Henrik Juul <arnej@Lise.Unit.NO> <item>Bakul Shah <bvs@bitblocks.com> <item>Barry Lustig <barry@ictv.com> <item>Bob Wilcox <bob@obiwan.uucp> <item>Branko Lankester <item>Brett Lymn <blymn@mulga.awadi.com.AU> <item>Charles Hannum <mycroft@ai.mit.edu> <item>Chris G. Demetriou <cgd@postgres.berkeley.edu> <item>Chris Torek <torek@ee.lbl.gov> <item>Christoph Robitschko <chmr@edvz.tu-graz.ac.at> <item>Daniel Poirot <poirot@aio.jsc.nasa.gov> <item>Dave Burgess <burgess@hrd769.brooks.af.mil> <item>Dave Rivers <rivers@ponds.uucp> <item>David Dawes <dawes@physics.su.OZ.AU> <item>David Greenman <davidg@Root.COM> <item>Eric J. Haug <ejh@slustl.slu.edu> <item>Felix Gaehtgens <felix@escape.vsse.in-berlin.de> <item>Frank Maclachlan <fpm@crash.cts.com> <item>Gary A. Browning <gab10@griffcd.amdahl.com> <item>Geoff Rehmet <csgr@alpha.ru.ac.za> <item>Goran Hammarback <goran@astro.uu.se> <item>Guido van Rooij <guido@gvr.win.tue.nl> <item>Guy Harris <guy@auspex.com> <item>Havard Eidnes <Havard.Eidnes@runit.sintef.no> <item>Herb Peyerl <hpeyerl@novatel.cuc.ab.ca <item>Holger Veit <Holger.Veit@gmd.de> <item>Ishii Masahiro, R. Kym Horsell <item>J.T. Conklin <jtc@winsey.com> <item>Jagane D Sundar < jagane@netcom.com > <item>James Clark <jjc@jclark.com> <item>James Jegers <jimj@miller.cs.uwm.edu> <item>James W. Dolter <item>James da Silva <jds@cs.umd.edu> et al <item>Jay Fenlason <hack@datacube.com> <item>Jim Wilson <wilson@moria.cygnus.com> <item>Jörg Lohse <lohse@tech7.informatik.uni-hamburg.de> <item>Jörg Wunsch <joerg_wunsch@uriah.heep.sax.de> <item>John Dyson - <formerly dyson@ref.tfs.com> <item>John Polstra <jdp@polstra.com> <item>John Woods <jfw@eddie.mit.edu> <item>Jordan K. Hubbard <jkh@whisker.hubbard.ie> <item>Julian Elischer <julian@dialix.oz.au> <item>Julian Stacey <stacey@guug.de> (fallback: <julian@meepmeep.pcs.com>) <item>Karl Lehenbauer <karl@NeoSoft.com> <karl@one.neosoft.com> <item>Keith Bostic <bostic@toe.CS.Berkeley.EDU> <item>Ken Hughes <item>Kent Talarico <kent@shipwreck.tsoft.net> <item>Kevin Lahey <kml%rokkaku.UUCP@mathcs.emory.edu> <kml@mosquito.cis.ufl.edu> <item>Marc Frajola <marc@dev.com> <item>Mark Tinguely <tinguely@plains.nodak.edu> <tinguely@hookie.cs.ndsu.NoDak.edu> <item>Martin Renters <martin@innovus.com> <item>Michael Galassi <nerd@percival.rain.com> <item>Mike Durkin <mdurkin@tsoft.sf-bay.org> <item>Nate Williams <nate@bsd.coe.montana.edu> <item>Nick Handel <nhandel@NeoSoft.com> <nick@madhouse.neosoft.com> <item>Pace Willisson <pace@blitz.com> <item>Paul Kranenburg <pk@cs.few.eur.nl> <item>Paul Mackerras <paulus@cs.anu.edu.au> <item>Paul Popelka <paulp@uts.amdahl.com> <item>Peter da Silva <peter@NeoSoft.com> <item>Phil Sutherland <philsuth@mycroft.dialix.oz.au> <item>Ralf Friedl <friedl@informatik.uni-kl.de> <item>Rick Macklem <root@snowhite.cis.uoguelph.ca> <item>Robert D. Thrush <rd@phoenix.aii.com> <item>Rodney W. Grimes <rgrimes@cdrom.com> <item>Rog Egge <?> <item>Sascha Wildner <swildner@channelz.GUN.de> <item>Scott Burris <scott@pita.cns.ucla.edu> <item>Scott Reynolds <scott@clmqt.marquette.mi.us> <item>Sean Eric Fagan <sef@kithrup.com> <item>Simon J Gerraty <sjg@melb.bull.oz.au> <sjg@zen.void.oz.au> <item>Stephen McKay <syssgm@devetir.qld.gov.au> <item>Terry Lambert <terry@icarus.weber.edu> <item>Terry Lee <terry@uivlsi.csl.uiuc.edu> <item>Warren Toomey <wkt@csadfa.cs.adfa.oz.au> <item>Wiljo Heinen <wiljo@freeside.ki.open.de> <item>William Jolitz <withheld> <item>Wolfgang Solfrank <ws@tools.de> <item>Wolfgang Stanglmeier <wolf@dentaro.GUN.de> <item>Yuval Yarom <yval@cs.huji.ac.il> </itemize> - - Last, but not least, the release engineer would like to - thank: His Wife, for chocolate chip cookies, and some other - things. The DGB project @ TFS, for patience and tolerance. diff --git a/handbook/current.sgml b/handbook/current.sgml index 82b274795c..0bd4900b8d 100644 --- a/handbook/current.sgml +++ b/handbook/current.sgml @@ -1,175 +1,166 @@ -<!-- $Id: current.sgml,v 1.6 1995-10-16 09:01:52 jkh Exp $ --> +<!-- $Id: current.sgml,v 1.7 1995-12-11 15:09:10 jkh Exp $ --> <!-- The FreeBSD Documentation Project --> <chapt><heading>Staying current with FreeBSD<label id="current"></heading> <p><em>Contributed by &a.jkh;.</em> <!-- THE FREEBSD CURRENT POLICY -Last updated: $Date: 1995-10-16 09:01:52 $ +Last updated: $Date: 1995-12-11 15:09:10 $ -This document attempts to explain the rationale behind FreeBSD-current, -what you should expect should you decide to run it, and states some -prerequisites for making sure the process goes as smoothly as possible. +This document attempts to explain the rationale behind +FreeBSD-current, what you should expect should you decide to run it, +and states some prerequisites for making sure the process goes as +smoothly as possible. --> <sect><heading>What is FreeBSD-current?</heading> -<p>FreeBSD-current is, quite literally, nothing more than a daily snapshot of -the working sources for FreeBSD. These include work in progress, experimental -changes, and transitional mechanisms that may or may not be present in -the next official release of the software. While many of us compile -almost daily from FreeBSD-current sources, there are periods of time when -the sources are literally uncompilable. These problems are generally resolved -as expeditiously as possible, but whether or not FreeBSD-current sources bring -disaster or greatly desired functionality can literally be a matter of which -part of any given 24 hour period you grabbed them in! - -Under certain circumstances we will sometimes make binaries for parts of -FreeBSD-current available, but only because we're interested in getting -something tested, not because we're in the business of providing binary -releases of current. If we don't offer, please don't ask! It takes far -too much time to do this as a general task. +<p>FreeBSD-current is, quite literally, nothing more than a daily +snapshot of the working sources for FreeBSD. These include work in +progress, experimental changes and transitional mechanisms that may or +may not be present in the next official release of the software. +While many of us compile almost daily from FreeBSD-current sources, +there are periods of time when the sources are literally uncompilable. +These problems are generally resolved as expeditiously as possible, +but whether or not FreeBSD-current sources bring disaster or greatly +desired functionality can literally be a matter of which part of any +given 24 hour period you grabbed them in! + +Under certain circumstances we will sometimes make binaries for parts +of FreeBSD-current available, but only because we're interested in +getting something tested, not because we're in the business of +providing binary releases of current. If we don't offer, please don't +ask! It takes far too much time to do this as a general task. <sect><heading>Who needs FreeBSD-current?</heading> <p>FreeBSD-current is made generally available for 3 primary interest groups: <enum> - <item> Members of the FreeBSD group who are actively working on one - part or another of the source tree and for whom keeping `current' - is an absolute requirement. + <item> Members of the FreeBSD group who are actively working on some + part of the source tree and for whom keeping `current' is an + absolute requirement. - <item> Members of the FreeBSD group who are active ALPHA or BETA testers - and willing to spend time working through problems in order to + <item> Members of the FreeBSD group who are active testers, + willing to spend time working through problems in order to ensure that FreeBSD-current remains as sane as possible. These are also people who wish to make topical suggestions on changes and the general direction of FreeBSD. <item> Peripheral members of the FreeBSD (or some other) group who merely wish to keep an eye on things and use the current sources for reference purposes (e.g. for <em>reading</em>, not running). These people also make the occasional comment or contribute code. </enum> <sect><heading>What is FreeBSD-current <em>NOT</em>?</heading> <p><enum> - <item> A fast-track to getting pre-release bits because there's something - you heard was pretty cool in there and you want to be the first on + <item> A fast-track to getting pre-release bits because you heard there's + some cool new feature in there and you want to be the first on your block to have it. <item> A quick way of getting bug fixes. <item> In any way ``officially supported'' by us. We do our best to help people genuinely in one of the 3 ``legitimate'' FreeBSD-current categories, but we simply <em>do not have the time</em> to help every person who jumps into FreeBSD-current with more enthusiasm than knowledge of how to deal with experimental system software. This is not because we're mean and nasty people who don't like helping people out (we wouldn't even be doing FreeBSD if we were), it's literally because we can't answer - 400 messages a day <em>and</em> actually work on FreeBSD! I'm sure if - given the choice between having us answer lots of questions or - continue to improve FreeBSD, most of you would vote for us + 400 messages a day <em>and</em> actually work on FreeBSD! I'm sure + that, if given the choice between having us answer lots of questions or + continuing to improve FreeBSD, most of you would vote for us improving it. </enum> <sect><heading>Using FreeBSD-current</heading> <p><enum> <item> Join the freebsd-current and cvs-all mailing lists. This is not just a good idea, it's <em>essential</em>. If you aren't on freebsd-current, you - won't read the comments that people are making about the - current state of the system and thus will end up stumbling + won't see the comments that people are making about the + current state of the system and thus will probably end up stumbling over a lot of problems that others have already found and solved. Even more importantly, you will miss out on potentially critical information (e.g. ``Yo, Everybody! Before you rebuild <tt>/usr/src</tt>, you <em>must</em> rebuild the kernel or your system will crash horribly!"). The cvs-all mailing list will allow you to see the commit log - entry for each change as it's made. This can also contain - important information, and will let you know what parts of - the system are being actively changed. + entry for each change as it's made along with any pertinent + information on possible side-effects. To join these lists, send mail to `majordomo@FreeBSD.ORG' and say: <verb> subscribe current subscribe cvs-all </verb> In the body of your message. Optionally, you can also say `help' and Majordomo will send you full help on how to subscribe and unsubscribe to the various other mailing lists we support. <item> Grab the sources from ftp.FreeBSD.ORG. You can do this in three ways: <enum> <item> Using the CTM facility described below. Unless you have a good TCP/IP connection at a flat rate, this is the way to do it. <item> Use the CMU `sup' program (Software Update Protocol), also described below. This is the second most recommended method, since it allows you to grab the entire collection once and then only what's changed from then on. Many people run sup from cron and keep their sources up-to-date automatically. <item> Use ftp. The source tree for FreeBSD-current is always "exported" on: <verb> ftp.FreeBSD.ORG:~ftp/pub/FreeBSD/FreeBSD-current </verb> We use `wu-ftpd' which allows compressed/tar'd grabbing of whole trees. e.g. you see: <verb> usr.bin/lex </verb> You can do: <verb> ftp> cd usr.bin ftp> get lex.tar.Z </verb> And it will get the whole directory for you as a compressed tar file. </enum> <item> Essentially, if you need rapid on-demand access to the source and communications bandwidth is not a consideration, use sup or ftp. Otherwise, use CTM. <item> If you're grabbing the sources to run, and not just look at, then grab <em>all</em> of current, not just selected portions. The reason for this is that various parts of the source depend on - updates elsewhere and trying to compile just a subset is almost + updates elsewhere, and trying to compile just a subset is almost guaranteed to get you into trouble. <item> Before compiling current, read the Makefile in /usr/src - carefully. You'll see one-time targets like `bootstrapld' - which <em><bf>must</bf></em> be run as part of the upgrading process. Reading - freebsd-hackers will keep you up-to-date on other bootstrapping - procedures that sometimes become necessary as we move towards - the next release. + carefully. You should at least run a `make world' the first time + through as part of the upgrading process. + Reading freebsd-hackers will keep you up-to-date on other + bootstrapping procedures that sometimes become necessary as we move + towards the next release. <item> Be active! If you're running FreeBSD-current, we want to know what you have to say about it, especially if you have suggestions for enhancements or bug fixes. Suggestions with accompanying code are received most enthusiastically! </enum> - -<!-- -Thank you for taking the time to read this all the way through. We're -always very keen to remain "open" and share the fruits of our labor -with the widest possible audience, but sharing development sources has -always had certain pitfalls associated with it (which is why most -commercial organizations won't even consider it) and I want to make -sure that people at least come into this with their eyes open, and -don't make the leap unless they're good at working without a net! ---> diff --git a/handbook/eresources.sgml b/handbook/eresources.sgml index 153bd3d6ed..ef4d53638d 100644 --- a/handbook/eresources.sgml +++ b/handbook/eresources.sgml @@ -1,356 +1,355 @@ -<!-- $Id: eresources.sgml,v 1.16 1995-11-24 07:55:25 jkh Exp $ --> +<!-- $Id: eresources.sgml,v 1.17 1995-12-11 15:09:12 jkh Exp $ --> <!-- The FreeBSD Documentation Project --> <chapt> <heading>Resources on the Internet<label id="eresources"></heading> + <p><em>Contributed by &a.jkh;.</em> + <p>The rapid pace of FreeBSD progress makes print media impractical as a means for following the latest - developments. Electronic resources are the best, if not the - only way stay informed of the latest advances. Also, since - FreeBSD is a volunteer effort, the user community also serves - as the technical support department and invariably, - electronic mail and Usenet news are the most effective way of - getting technical problems resolved. - - Below, the most important points of contact with the FreeBSD - user community are outlined. If you are aware of other - resources not included, please send them to - <tt>doc@freebsd.org</tt> so they may be included. + developments. Electronic resources are the best, if not often the + only way stay informed of the latest advances. Since + FreeBSD is a volunteer effort, the user community itself also generally + serves as a `technical support department' of sorts, with electronic mail + and Usenet news being the most effective way of reaching that community. + + The most important points of contact with the FreeBSD + user community are outlined below. If you are aware of other + resources not mentioned here, please send them to + <tt>doc@freebsd.org</tt> so that they may also be included. <sect> <heading>Mailing lists<label id="eresources:mail"></heading> <p>Though many of the FreeBSD development members read USENET, we cannot always guarantee that we'll get to your questions in a timely fashion -(or at all) if you post them only to one of the comp.unix.bsd.* +(or at all) if you post them only to one of the comp.unix.bsd.freebsd.* groups. By addressing your questions to the appropriate mailing list you will reach both us and a concentrated FreeBSD audience, invariably assuring a better (or at least faster) response. -There are list charters at the bottom of this document. Please read -the list charter before joining a list. We must strive to -keep the signal to noise ratio of the lists high, especially in -the technical lists. +<p>The charters for the various lists are given at the bottom of this +document. Please read the charter before joining a list since we must +strive to keep the signal to noise ratio of the lists high, especially +in the technical ones. Archives are kept for all of the mailing lists and can be searched using the the <url url="http://www.freebsd.org/search.html" name="FreeBSD World Wide Web server">. The keyword searchable archive -offers an excellent way to find answers to frequently asked questions -and should be consulted before posting a question. +offers an excellent way of finding answers to frequently asked +questions and should be consulted before posting a question. <sect1><heading>List summary</heading> -<p><bf>General lists:</bf> The following are general lists that +<p><bf>General lists:</bf> The following are general lists which anyone is free to join: <verb> List Purpose ---------------------------------------------------------------------- -freebsd-announce Important events / milestones +freebsd-announce Important events and project milestones freebsd-bugs Bug reports -freebsd-chat Non technical items related to the community -freebsd-current Discussions about the use of FreeBSD-current +freebsd-chat Non-technical items related to the FreeBSD community +freebsd-current Discussion concerning the use of FreeBSD-current freebsd-isp Issues for Internet Service Providers using FreeBSD -freebsd-policy Policy issues and suggestions +freebsd-policy General policy issues and suggestions freebsd-questions User questions </verb> -<bf>Technical lists:</bf> The following are the technical lists. You should -read the charter carefully before joining them, and you should keep -your e-mail within the scope of the guidelines. +<bf>Technical lists:</bf> The following lists are for technical discussion. +You should read the charter carefully before joining one, keeping any +messages sent to a list within the scope of the guidelines. <verb> List Purpose ---------------------------------------------------------------------- freebsd-doc The FreeBSD Documentation project freebsd-fs Filesystems -freebsd-hackers General Technical discussions -freebsd-hardware General discussion of FreeBSD hardware -freebsd-multimedia Multimedia discussions -freebsd-platforms Porting to Non-Intel platforms -freebsd-ports Discussion of "ports" +freebsd-hackers General technical discussion +freebsd-hardware General discussion of hardware for running FreeBSD +freebsd-multimedia Multimedia discussion +freebsd-platforms Concerning ports to non-Intel architecture platforms +freebsd-ports Discussion of the ports collection freebsd-security Security issues -freebsd-scsi SCSI subsystem +freebsd-scsi The SCSI subsystem </verb> -<bf>Limited lists:</bf> The following are limited lists that you will need -approval to join. Even though access to these lists is controled, -anyone is free to send suggestions and comments to them. It is a +<bf>Limited lists:</bf> The following lists require approval to join, +though anyone is free to send suggestions and comments to them. It is a good idea establish a presence in the technical lists before asking to join one of these limited lists. <verb> List Purpose ---------------------------------------------------------------------- freebsd-admin Administrative issues freebsd-arch Architecture and design discussions freebsd-core FreeBSD core team freebsd-install Installation development freebsd-user-groups User group coordination </verb> -<bf>CVS lists:</bf> The following lists are for people seeing the log messages -for source changes in specific areas: +<bf>CVS lists:</bf> The following lists are for people interested in +seeing the log messages for changes to various areas of the source tree. <verb> List name Source area Area Description (source for) ---------------------------------------------------------------------- cvs-CVSROOT /usr/src/[A-Z]* Top level /usr/src file changes cvs-all /usr/src All changes to the tree (superset) cvs-bin /usr/src/bin System binaries cvs-etc /usr/src/etc System files cvs-games /usr/src/games Games cvs-gnu /usr/src/gnu GPL'd utilities cvs-include /usr/src/include Include files cvs-kerberosIV /usr/src/kerberosIV Kerberos encryption code cvs-lib /usr/src/lib System libraries cvs-libexec /usr/src/libexec System binaries cvs-ports /usr/ports Ported software cvs-sbin /usr/src/sbin System binaries cvs-share /usr/src/share System shared files cvs-sys /usr/src/sys Kernel cvs-usrbin /usr/src/usr.bin Use binaries cvs-usrsbin /usr/src/usr.sbin System binaries </verb> <sect1><heading>How to subscribe</heading> <p>All mailing lists live on <tt>FreeBSD.ORG</tt>, so to post to a -list you simply mail to <em>listname</em><tt>@FreeBSD.ORG</tt>. It -will then be redistributed to mailing list members throughout the -world. +given list you simply mail to <em>listname</em><tt>@FreeBSD.ORG</tt>. It +will then be redistributed to mailing list members world-wide. To subscribe to a list, send mail to: <tscreen><verb> majordomo@FreeBSD.ORG </verb></tscreen> And include the keyword <tscreen><verb> subscribe <listname> [<optional address>] </verb></tscreen> In the body of your message. For example, to subscribe yourself to freebsd-announce, you'd do: <tscreen><verb> % mail majordomo@FreeBSD.ORG subscribe freebsd-announce ^D </verb></tscreen> If you want to subscribe yourself under a different name, or submit a subscription request for a local mailing list (note: this is more efficient if you have several interested parties at one site, and highly appreciated by us!), you would do something like: <tscreen><verb> % mail majordomo@FreeBSD.ORG subscribe freebsd-announce local-announce@somesite.com ^D </verb></tscreen> Finally, it is also possible to unsubscribe yourself from a list, get a list of other list members or see the list of mailing lists again by sending other types of control messages to majordomo. For a complete list of available commands, do this: <tscreen><verb> % mail majordomo@FreeBSD.ORG help ^D </verb></tscreen> -Finally, we again request that you keep the technical mailing lists on -a technical track. If you're only interested in the "high points", -then it's suggested that you join freebsd-announce, which will contain -only infrequent traffic. +Again, we'd like to request that you keep discussion in the technical mailing +lists on a technical track. If you're only interested in the "high points" +then it's suggested that you join freebsd-announce, which is intended only +for infrequent traffic. <sect1><heading>List charters</heading> <p> <descrip> <tag/FREEBSD-ADMIN/ <em>Administrative issues</em><newline> <!-- XXX --> <tag/FREEBSD-ANNOUNCE/ <em>Important events / milestones</em><newline> This is the mailing list for people interested only in occasional announcements of significant freebsd events. This includes announcements about snapshots and other releases. It contains announcements of new FreeBSD capabilities. It may contain calls for volunteers etc. This is a low volume list. <tag/FREEBSD-ARCH/ <em>Architecture and design discussions</em><newline> This is the mailing list for people discussing FreeBSD architectural issues. It is a closed list, and not for general subscription. <tag/FREEBSD-BUGS/ <em>Bug reports</em><newline> This is the mailing list for reporting bugs in FreeBSD Whenever possible, bugs should be submitted using "send-pr". <tag/FREEBSD-CHAT/ <em>Non technical items related to the community</em><newline> This list contains the overflow from the other lists about non-technical, social information. It includes discussion about whether Jordan looks like a toon ferret or not, whether or not to type in capitals, who is drinking too much coffee, where the best beer is brewed, who is brewing beer in their basement, and so on. Occasional announcements of important events (such as upcoming parties, weddings, births, new jobs, etc) can be made to the technical lists, but the follow ups should be directed to this -chat list. <tag/FREEBSD-CORE/ <em>FreeBSD core team</em><newline> This is an internal mailing list for use by the core members. <tag/FREEBSD-CURRENT/ <em>Discussions about the use of FreeBSD-current</em><newline> This is the mailing list for users of freebsd-current. It includes warnings about new features coming out in -current that will affect the users, and instructions on steps that must be taken to remain -current. Anyone running "current" must subscribe to this list. <tag/FREEBSD-CURRENT-DIGEST/ <em>Discussions about the use of FreeBSD-current</em><newline> This is the digest version of the freebsd-current mailing list. The digest consists of all messages sent to freebsd-current bundled together and mailed out as a single message. The average digest size is about 40kB. <tag/FREEBSD-DOC/ <em>Documentation project</em><newline> This mailing list belongs to the FreeBSD Doc Project and is for the discussion of documentation related issues and projects. <tag/FREEBSD-FS/ <em>Filesystems</em><newline> Discussions concerning FreeBSD filesystems. <tag/FREEBSD-HACKERS/ <em>Technical discussions</em><newline> This is a forum for technical discussions related to FreeBSD. This is the primary technical mailing list. It is for individuals actively working on FreeBSD, to bring up problems or discuss alternative solutions. Individuals interested in following the technical discussion are also welcome. <tag/FREEBSD-HACKERS-DIGEST/ <em>Technical discussions</em><newline> This is the digest version of the freebsd-hackers mailing list. The digest consists of all messages sent to freebsd-hackers bundled together and mailed out as a single message. The average digest size is about 40kB. <tag/FREEBSD-HARDWARE/ <em>General discussion of FreeBSD hardware</em><newline> General discussion about the types of hardware that FreeBSD runs on, various problems and suggestions concerning what to buy or avoid. <tag/FREEBSD-INSTALL/ <em>Installation discussion</em><newline> This mailing list is for discussing FreeBSD installation development for the future releases. <tag/FREEBSD-ISP/ <em>Issues for Internet Service Providers</em><newline> This mailing list is for discussing topics relevant to Internet Serivce Providers (ISPs) using FreeBSD. <tag/FREEBSD-MULTIMEDIA/ <em>Multimedia discussions</em><newline> This is a forum about multimedia applications using FreeBSD. Discussion center around multimedia applications, their installation, their development and their support within FreeBSD <tag/FREEBSD-PLATFORMS/ <em>Porting to Non-Intel platforms</em><newline> Cross-platform freebsd issues, general discussion and proposals for non-Intel FreeBSD ports. <tag/FREEBSD-POLICY/ <em>Policy issues and suggestions</em><newline> This is a forum for policy discussions related to FreeBSD. This includes where FreeBSD is going, how to set up a consortium, whether or not and how to make FreeBSD pay for itself, how to attract more users, and so on. When a topic relates directly to FreeBSD but has little or no technical content then it should be sent to this list. <tag/FREEBSD-PORTS/ <em>Discussion of "ports"</em><newline> Discussions concerning FreeBSD's "ports collection" (/usr/ports), proposed ports, modifications to ports collection infrastructure and general coordination efforts. <tag/FREEBSD-QUESTIONS/ <em>User questions</em><newline> This is the mailing list for questions about FreeBSD. You should not send "how to" questions to the technical lists unless you consider the question to be pretty technical. <tag/FREEBSD-QUESTIONS-DIGEST/ <em>User questions</em><newline> This is the digest version of the freebsd-questions mailing list. The digest consists of all messages sent to freebsd-questions bundled together and mailed out as a single message. The average digest size is about 40kB. <tag/FREEBSD-SCSI/ <em>SCSI subsystem</em><newline> This is the mailing list for people working on the scsi subsystem for FreeBSD. <tag/FREEBSD-SECURITY/ <em>Security issues</em><newline> FreeBSD computer security issues (DES, Kerberos, known security holes and fixes, etc). <tag/FREEBSD-USER-GROUPS/ <em>User Group Coordination List</em><newline> This is the mailing list for the coordinators from each of the local area Users Groups to discuss matters with each other and a designated individual from the Core Team. This mail list should be limited to meeting synopsis and coordination of projects that span User Groups. </descrip> <sect> <heading>Usenet newsgroups<label id="eresources:news"></heading> <p>In addition to two FreeBSD specific newsgroups, there are many others in which FreeBSD is discussed or are otherwise relevant to FreeBSD users. <url url="http://minnie.cs.adfa.oz.au/BSD-info/bsdnews_search.html" name="Keyword searchable archives"> are available for some of these newsgroups from courtesy of Warren Toomey <tt><wkt@cs.adfa.oz.au></tt>. <sect1> <heading>BSD specific newsgroups</heading> <p><itemize> <item>comp.unix.bsd.freebsd.announce <item>comp.unix.bsd.freebsd.misc </itemize> <sect1> <heading>Other Unix newsgroups of interest</heading> <p><itemize> <item>comp.unix <item>comp.unix.questions <item>comp.unix.admin <item>comp.unix.programmer <item>comp.unix.shell <item>comp.unix.user-friendly <item>comp.security.unix <item>comp.sources.unix <item>comp.unix.advocacy <item>comp.unix.misc <item>comp.os.386bsd.announce <item>comp.os.386bsd.apps <item>comp.os.386bsd.bugs <item>comp.os.386bsd.development <item>comp.os.386bsd.misc <item>comp.os.386bsd.questions <item>comp.bugs.4bsd <item>comp.bugs.4bsd.ucb-fixes <item>comp.unix.bsd </itemize> <sect1> <heading>X-Window system</heading> <p><itemize> <item>comp.windows.x.i386unix <item>comp.windows.x <item>comp.windows.x.apps <item>comp.windows.x.announce <item>comp.windows.x.intrinsics <item>comp.windows.x.motif <item>comp.windows.x.pex <item>comp.emulators.ms-windows.wine </itemize> <sect> <heading>World Wide Web servers<label id="eresources:web"></heading> <p><itemize> <item><url url="http://www.freebsd.org/"></item> </itemize> </sect> diff --git a/handbook/hw.sgml b/handbook/hw.sgml index ed02e590e4..d408a73066 100644 --- a/handbook/hw.sgml +++ b/handbook/hw.sgml @@ -1,421 +1,422 @@ -<!-- $Id: hw.sgml,v 1.10 1995-12-03 00:17:57 jkh Exp $ --> +<!-- $Id: hw.sgml,v 1.11 1995-12-11 15:09:13 jkh Exp $ --> <!-- The FreeBSD Documentation Project --> <!-- <!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN"> --> <chapt><heading>PC Hardware compatibility<label id="hw"></heading> <p>Issues of hardware compatibility are among the most troublesome in the computer industry today and FreeBSD is by no means immune to trouble. In this respect, FreeBSD's advantage of being able to run on inexpensive commidity PC hardware is also its liability when it comes to support for the amazing variety of components on the market. While it would be impossible to provide a exhaustive listing of hardware that FreeBSD supports, this section serves as a catalog of the device drivers included with FreeBSD and the hardware each drivers supports. Where possible and appropriate, notes about specific products are included. As FreeBSD is a volunteer project without a funded testing department, we depend on you, the user, for much of the information contained in this catalog. If you have direct experience of hardware that does or does not work with FreeBSD, please let us know by sending email to <tt>doc@freebsd.org</tt>. Questions about supported hardware should be directed to <tt>questions@freebsd.org</tt> (see <ref id="eresources:mail" name="Mailing Lists"> for more information). When submitting information or asking a question, please remember to specify exactly what version of FreeBSD you are using and include as many details of your hardware as possible. <sect><heading>Sample Configurations<label id="hw:configs"></heading> <p>The following list of sample hardware configurations by no means constitutes an endorsement of a given hardware vendor or product by <em>The FreeBSD Project</em>. This information is provided only as a public service and merely catalogs some of the experiences that various individuals have had with different hardware combinations. Your mileage may vary. Slippery when wet. Beware of dog. <sect1><heading>Jordan's Picks</heading> <p>I have had fairly good luck building workstation and server configurations with the following components. I can't guarantee that you will too, nor that any of the companies here will remain "best buys" forever. I will try, when I can, to keep this list up-to-date but cannot obviously guarantee that it will be at any given time. <sect2><heading>Motherboards</heading> <p>The <htmlurl url="http://asustek.asus.com.tw/" name="ASUS"> <htmlurl url="http://asustek.asus.com.tw/FTP/ASUS/Info/Spec/pi-p55tp4xe.txt" name="P55TP4XE"> motherboard appears to be a good choice for mid-to-high range Pentium server and workstation systems. If you're really looking for performance, be also sure to get the <htmlurl url="http://asustek.asus.com.tw/Products/TB/mem-0002.html" name="pipelined burst cache module">. I feel that it's worth the extra cost. If you're looking for a 486 class motherboard, you might also investigate ASUS's <htmlurl url="http://asustek.asus.com.tw/FTP/ASUS/Info/Spec/pvi-486sp3.txt" name="486SP3G"> offering. NOTE: The Intel <htmlurl url="http://asustek.asus.com.tw/Products/TB/triton-intro.html" name="Triton"> chipset based motherboards do not offer memory parity logic, making it almost impossible to detect when a memory error has occurred. Those wishing to build highly fault-tolerant systems may therefore want to wait for Intel's newest generation of motherboards based on the Orion chipset or investigate ASUS's SiS chipset based motherboard, the <htmlurl url="http://asustek.asus.com.tw/FTP/ASUS/Info/Spec/pi-p55sp4.txt" name="P55SP4">. I have no personal experience with this motherboard, but have heard good things about it and will note that it has the advantage of being available <em>now</em>. <sect2><heading>Disk Controllers</heading> <p>This one is a bit trickier, and while I used to recommend the <htmlurl url="http://www.buslogic.com" name="Buslogic"> controllers unilaterally for everything from ISA to PCI, now I tend to lean towards the <htmlurl url="http://www.adaptec.com" name="Adaptec"> 1542CF for ISA, Buslogic Bt747c for EISA and Adaptec 2940 for PCI. I've currently heard nothing about Buslogic's new Bt-930 controller but would welcome any reports on its performance. <sect2><heading>Disk drives</heading> <p>In this particular game of russian roulette, I'll make few specific recommendations except to say "SCSI over IDE whenever you can afford it." Even in small desktop configurations, SCSI often makes more sense since it allows you to migrate drives from server to desktop as falling drive prices make it economical to do so. If you have more than one machine to administer then think of it not simply as storage, think of it as a food chain. <p>I do not currently see SCSI WIDE drives as a necessary expense unless you're putting together an NFS or NEWS server that will be doing a lot of multiuser disk I/O. <sect2><heading>Video Cards</heading> <p>If you can also afford to buy a commercial X server for $99 from <htmlurl url="http://www.xinside.com/" name="X Inside"> then I can heartily recommend the <htmlurl url="http://www.matrox.com/" name="Matrox"> <htmlurl url="http://www.matrox.com/mgaweb/brochure.htm" name="Millenium"> card. If free X servers are more to your liking, you certainly can't go wrong with one of <htmlurl url="http://www.nine.com/" name="Number 9's"> cards. Their S3 Vision 868 and 968 based cards (the 9FX series) are no slouches either, and are supported by <htmlurl url="http://www.xfree86.org" name="XFree86">'s S3 server. <sect2><heading>Monitors</heading> <p>I have had very good luck with the <htmlurl url="http://cons3.sel.sony.com/SEL/ccpg/display/ms17se2.html" name="Sony Multiscan 17SE monitors">, as have I with the Viewsonic offering in the same (trinitron) tube. For larger than 17", all I can recommend at the time of this writing is to not spend any less than U.S. $2,500 for a 21" monitor if that's what you really need. There are good monitors available in the >=20" range and there are also cheap monitors in the >=20" range. Unfortunately, none are both cheap and good! <sect2><heading>Networking</heading> <p>I can recommend the <htmlurl url="http://www.smc.com/" name="SMC"> Ultra 16 controller for any ISA application and the SMC EtherPower or Compex ENET32 cards for any serious PCI based networking. Both of the PCI cards are based around DEC's DC21041 ethernet controller chip and other cards using it, such as the Zynx ZX342 or DEC DE435, will generally work as well. <p>If you're looking for high-speed serial networking solutions, then <htmlurl url="http://www.digiboard.com/" name="Digi International"> makes the <htmlurl url="http://www.digiboard.com/prodprofiles/profiles-prices/arnetprofiles/sync570i.html" name="SYNC 570i"> series, with drivers now in FreeBSD-current. <htmlurl url="http://www.etinc.com" name="Emerging Technologies"> also manufactures a board with T1/E1 capabilities, using software they provide. <sect2><heading>Audio</heading> <p>I currently use the <htmlurl url="http://www.gravis.com/" name="Gravis"> Ultrasound MAX due to its high sound quality and full-duplex audio capabilities (dual DMA channels). Support for Windows NT and OS/2 is fairly anemic, however, so I'm not sure that I can recommend it as an all-around card for a machine that will be running both FreeBSD and NT or OS/2. In such a scenario, I might recommend the <htmlurl url="http://www.creaf.com/" name="Creative Labs"> AWE32 instead. <sect><heading>Core/Processing<label id="hw:core"></heading> <sect1><heading>Motherboards, busses, and chipsets</heading> <sect2><heading>* ISA</heading> <sect2><heading>* EISA</heading> <sect2><heading>* VLB</heading> <sect2><heading>PCI</heading> <p><em>Contributed by &a.rgrimes;.<newline>25 April 1995.</em></p> - <p>Of the Intel PCI chip sets the following is a list - of brokenness from worst to best and a short - description of brokenness.</p> + <p>Of the Intel PCI chip sets, the following list describes + various types of known-brokenness and the degree of + breakage, listed from worst to best. + </p> <p><descrip> <tag>Mercury:</tag> Cache coherency problems, especially if there are ISA bus masters behind the ISA to PCI bridge chip. Hardware flaw, only known work around is to turn the cache off. <tag>Saturn-I <em>(ie, 82424ZX at rev 0, 1 or 2)</em>:</tag> Write back cache coherency problems. Hardware flaw, only known work around is to set the external cache to write-through mode. Upgrade to Saturn-II. <tag>Saturn-II <em>(ie, 82424ZX at rev 3 or 4)</em>:</tag> Works fine, but many MB manufactures leave out the external dirty bit SRAM needed for write back operation. Work arounds are either run it in write through mode, or get the dirty bit SRAM installed. (I have these for the ASUS PCI/I-486SP3G rev 1.6 and later boards). <tag>Neptune:</tag> Can not run more than 2 bus master devices. Admitted Intel design flaw. Workarounds include do not run more than 2 bus masters, special hardware design to replace the PCI bus arbiter (appears on Intel Altair board and several other Intel server group MB's). And of course Intel's official answer, move to the Triton chip set, we ``fixed it there''. <tag>Triton:</tag> No known cache coherency or bus master problems, chip set does not implement parity checking. Workaround for parity issue. Wait for Triton-II. <tag>Triton-II:</tag> Unknown, not yet shipping. </descrip> </p> <sect1><heading>* CPUs/FPUs</heading> <sect1><heading>* Memory</heading> <sect1><heading>* BIOS</heading> <sect><heading>Input/Output Devices<label id="hw:io"></heading> <sect1><heading>* Video cards</heading> <sect1><heading>* Sound cards</heading> <sect1><heading>Serial ports and multiport cards</heading> <p>The <tt>sio</tt> driver provides support for NS8250-, NS16450-, NS16550 and NS16550A-based EIA RS-232C (CCITT V.24) communications interfaces. Several multiport cards are supported as well. See the <tt>sio(4)</tt> manual page for detailed technical documentation. <sect2><heading>Digiboard PC/8</heading> <p><em>Contributed by &a.awebster;.<newline>26 August 1995.</em> Here is a config snippet from a machine with digiboard PC/8 with 16550. It has 8 modems connected to these 8 lines, and they work just great. Do not forget to add <tt>options "COM_MULTIPORT"</tt> or it will not work very well! <tscreen><verb> device sio4 at isa? port 0x100 tty flags 0xb05 device sio5 at isa? port 0x108 tty flags 0xb05 device sio6 at isa? port 0x110 tty flags 0xb05 device sio7 at isa? port 0x118 tty flags 0xb05 device sio8 at isa? port 0x120 tty flags 0xb05 device sio9 at isa? port 0x128 tty flags 0xb05 device sio10 at isa? port 0x130 tty flags 0xb05 device sio11 at isa? port 0x138 tty flags 0xb05 irq 9 vector siointr </verb></tscreen> The trick in setting this up is that the MSB of the flags represent the last SIO port, in this case 11 so flags are 0xb05. <sect2><heading>Boca 16</heading> <p><em>Contributed by &a.whiteside;.<newline>26 August 1995.</em> The procedures to make a Boca 16 pord board with FreeBSD are pretty straighforward, but you will need a couple things to make it work: <enum> <item>You either need the kernel sources installed so you can recompile the necessary options or you will need someone else to compile it for you. The 2.0.5 default kernel does <bf>not</bf> come with multiport support enabled and you will need to add a device entry for each port anyways. </item> <item>Two, you will need to know the interrupt and IO setting for your Boca Board so you can set these options properly in the kernel.</item> </enum> One important note - the actual UART chips for the Boca 16 are in the connector box, not on the internal board itself. So if you have it unplugged, probes of those ports will fail. I have never tested booting with the box unplugged and plugging it back in, and I suggest you do not either. If you do not already have a custom kernel configuration file set up, refer to <ref id="kernelconfig" name="Kernel Configuration"> for general procedurs. The following are the specifics for the Boca 16 board and assume you are using the kernel name MYKERNEL and editing with vi. <enum> <item>Add the line <tscreen><verb> options "COM_MULTIPORT" </verb></tscreen> to the config file. </item> <item>Where the current <tt>device sio <em>xxx</em></tt> lines are, you will need to add 16 more devices. <em>Only the last device includes the interrupt vector for the board</em>. (See the <tt>sio(4)</tt> manual page for detail as to why.) The following example is for a Boca Board with an interrupt of 3, and a base IO address 100h. The IO address for Each port is +8 hexidecimal from the previous port, thus the 100h, 108h, 110h... addresses. <tscreen><verb> device sio1 at isa? port 0x100 tty flags 0x1005 device sio2 at isa? port 0x108 tty flags 0x1005 device sio3 at isa? port 0x110 tty flags 0x1005 device sio4 at isa? port 0x118 tty flags 0x1005 [...] device sio15 at isa? port 0x170 tty flags 0x1005 device sio16 at isa? port 0x178 tty flags 0x1005 irq 3 vector siointr </verb></tscreen> The flags entry <em>must</em> be changed from this example unless you are using the exact same sio assignments. Flags are set according to 0x<em>MYY</em> where <em>M</em> indicates the minor number of the master port (the last port on a Boca 16) and <em>YY</em> indicates if FIFO is enabled or disabled(enabled), IRQ sharing is used(yes) and if there is an AST/4 compatible IRQ control register(no). In this example, <tscreen><verb> flags 0x1005 </verb></tscreen> indicates that the master port is sio16. If I added another board and assigned sio17 through sio28, the flags for all 16 ports on <em>that</em> board would be 0x1C05, where 1C indicates the minor number of the master port. Do not change the 05 setting.</item> <item>Save and complete the kernel configuration, recompile, install and reboot. Presuming you have successfully installed the recompiled kernel and have it set to the correct address and IRQ, your boot message should indicate the successful probe of the Boca ports as follows: (obviously the sio numbers, IO and IRQ could be different) <tscreen><verb> sio1 at 0x100-0x107 flags 0x1005 on isa sio1: type 16550A (multiport) sio2 at 0x108-0x10f flags 0x1005 on isa sio2: type 16550A (multiport) sio3 at 0x110-0x117 flags 0x1005 on isa sio3: type 16550A (multiport) sio4 at 0x118-0x11f flags 0x1005 on isa sio4: type 16550A (multiport) sio5 at 0x120-0x127 flags 0x1005 on isa sio5: type 16550A (multiport) sio6 at 0x128-0x12f flags 0x1005 on isa sio6: type 16550A (multiport) sio7 at 0x130-0x137 flags 0x1005 on isa sio7: type 16550A (multiport) sio8 at 0x138-0x13f flags 0x1005 on isa sio8: type 16550A (multiport) sio9 at 0x140-0x147 flags 0x1005 on isa sio9: type 16550A (multiport) sio10 at 0x148-0x14f flags 0x1005 on isa sio10: type 16550A (multiport) sio11 at 0x150-0x157 flags 0x1005 on isa sio11: type 16550A (multiport) sio12 at 0x158-0x15f flags 0x1005 on isa sio12: type 16550A (multiport) sio13 at 0x160-0x167 flags 0x1005 on isa sio13: type 16550A (multiport) sio14 at 0x168-0x16f flags 0x1005 on isa sio14: type 16550A (multiport) sio15 at 0x170-0x177 flags 0x1005 on isa sio15: type 16550A (multiport) sio16 at 0x178-0x17f irq 3 flags 0x1005 on isa sio16: type 16550A (multiport master) </verb></tscreen> If the messages go by too fast to see, <tt>dmesg > more</tt> will show you the boot messages.</item> <item>Next, apprepriate entries in <tt>/dev</tt> for the devices must be made using the <tt>/dev/MAKEDEV</tt> script. After becoming root: <tscreen> # cd /dev<newline> # ./MAKEDEV tty1<newline> # ./MAKEDEV cua1<newline> <em>(everything in between)</em><newline> # ./MAKEDEV ttyg<newline> # ./MAKEDEV cuag </tscreen> If you do not want or need callout devices for some reason, you can dispense with making the <tt>cua*</tt> devices.</item> <item>If you want a quick and sloppy way to make sure the devices are working, you can simply plug a modem into each port and (as root) <tt>echo at > ttyd*</tt> for each device you have made. You <em>should</em> see the RX lights flash for each working port.</item> </enum> <sect1><heading>* Parallel ports</heading> <sect1><heading>* Modems</heading> <sect1><heading>* Network cards</heading> <sect1><heading>* Keyboards</heading> <sect1><heading>* Mice</heading> <sect1><heading>* Other</heading> <sect><heading>Storage Devices<label id="hw:storage"></heading> &esdi; &scsi; <sect1><heading>* Disk/tape controllers</heading> <sect2><heading>* SCSI</heading> <sect2><heading>* IDE</heading> <sect2><heading>* Floppy</heading> <sect1><heading>* Hard drives</heading> <sect1><heading>* Tape drives</heading> <sect1><heading>* CD-ROM drives</heading> <sect1><heading>* Other</heading> <sect1><heading>* Adding and reconfiguring disks</heading> <sect1><heading>* Tapes and backups</heading> <sect1><heading>* Serial ports</heading> <sect1><heading>* Sound cards</heading> <sect1><heading>* PCMCIA</heading> <sect1><heading>* Other<label id="hw:other"></heading>