o Update my "tips" section of the handbook.
o Create the goals section at last using some text of mine which James Raynard dug up someplace. :)
This commit is contained in:
parent
486905a044
commit
c884462e86
@ -1,9 +1,25 @@
|
||||
<!-- $Id$ -->
|
||||
<!-- $Id: goals.sgml,v 1.1 1995/12/07 13:22:13 jkh Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect><heading>FreeBSD Project goals<label id="goals"></heading>
|
||||
|
||||
<p><em>Contributed by &a.jkh;</em>.
|
||||
|
||||
<p><em>Note: This section is under construction.</em>
|
||||
<p>The goals of the FreeBSD Project are to provide software that may
|
||||
be used for any purpose and without strings attached. Many of us
|
||||
have a significant investment in the code (and project) and would
|
||||
certainly not mind a little financial renumeration now and then,
|
||||
but we're definitely not prepared to insist on it. We believe
|
||||
that our first and foremost "mission" is to provide code to any
|
||||
and all comers, and for whatever purpose, so that the code gets
|
||||
the widest possible use and provides the widest possible benefit.
|
||||
This is, I believe, one of the most fundamental goals of Free
|
||||
Software and one that we enthusiastically support.
|
||||
|
||||
<p>That code in our source tree which falls under the GNU Public License
|
||||
(GPL) or GNU Library Public License (GLPL) comes with slightly more
|
||||
strings attached, though at least on the side of enforced
|
||||
access rather than the usual opposite. Due to the additional
|
||||
complexities that can evolve in the commercial use of GPL software,
|
||||
we do, however, endeavor to replace such software with submissions
|
||||
under the more relaxed BSD copyright whenever possible.
|
||||
|
@ -1,4 +1,4 @@
|
||||
<!-- $Id: hw.sgml,v 1.30 1996/07/03 21:22:16 jfieber Exp $ -->
|
||||
<!-- $Id: hw.sgml,v 1.31 1996/07/12 16:18:50 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -54,17 +54,14 @@ Slippery when wet. Beware of dog.
|
||||
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.
|
||||
also investigate ASUS's <htmlurl url="http://asustek.asus.com.tw/FTP/ASUS/Info/Spec/pvi-486sp3.txt" name="486SP3G"> offering (Note: These have become
|
||||
increasingly hard to get as ASUS apparently no longer manufactures them).
|
||||
|
||||
NOTE: The Intel <htmlurl url="http://asustek.asus.com.tw/Products/TB/triton-intro.html" name="Triton"> chip-set 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 chip-set or investigate ASUS's SiS chip-set 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 and have heard mixed reports - some say it's a fine MB, others
|
||||
say that it's measurably slower than the Triton. The only undisputed
|
||||
advantage it offers is being available <em>now</em>.
|
||||
has occurred. Those wishing to build more fault-tolerant systems should
|
||||
therefore buy one of the newer Triton II based motherboards, which offer
|
||||
both better performance and parity checking.
|
||||
|
||||
<sect2><heading>Disk Controllers</heading>
|
||||
<p>This one is a bit trickier, and while I used to recommend the
|
||||
@ -133,7 +130,9 @@ Slippery when wet. Beware of dog.
|
||||
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.
|
||||
will generally work as well. For 100Mbit networking, either the
|
||||
SMC SMC9332DST 10/100MB or Intel EtherExpress Pro/100B cards will do
|
||||
a fine job.
|
||||
|
||||
<sect2><heading>Serial</heading>
|
||||
<p>If you're looking for high-speed serial networking solutions, then
|
||||
|
Loading…
Reference in New Issue
Block a user