File:  [LON-CAPA] / doc / hardware / hardware.html
Revision 1.4: download - view: text, annotated - select for diffs
Mon Feb 3 18:03:51 2003 UTC (21 years, 3 months ago) by harris41
Branches: MAIN
CVS tags: version_2_9_X, version_2_9_99_0, version_2_9_1, version_2_9_0, version_2_8_X, version_2_8_99_1, version_2_8_99_0, version_2_8_2, version_2_8_1, version_2_8_0, version_2_7_X, version_2_7_99_1, version_2_7_99_0, version_2_7_1, version_2_7_0, version_2_6_X, version_2_6_99_1, version_2_6_99_0, version_2_6_3, version_2_6_2, version_2_6_1, version_2_6_0, version_2_5_X, version_2_5_99_1, version_2_5_99_0, version_2_5_2, version_2_5_1, version_2_5_0, version_2_4_X, version_2_4_99_0, version_2_4_2, version_2_4_1, version_2_4_0, version_2_3_X, version_2_3_99_0, version_2_3_2, version_2_3_1, version_2_3_0, version_2_2_X, version_2_2_99_1, version_2_2_99_0, version_2_2_2, version_2_2_1, version_2_2_0, version_2_1_X, version_2_1_99_3, version_2_1_99_2, version_2_1_99_1, version_2_1_99_0, version_2_1_3, version_2_1_2, version_2_1_1, version_2_1_0, version_2_12_X, version_2_11_X, version_2_11_4_uiuc, version_2_11_4_msu, version_2_11_4, version_2_11_3_uiuc, version_2_11_3_msu, version_2_11_3, version_2_11_2_uiuc, version_2_11_2_msu, version_2_11_2_educog, version_2_11_2, version_2_11_1, version_2_11_0_RC3, version_2_11_0_RC2, version_2_11_0_RC1, version_2_11_0, version_2_10_X, version_2_10_1, version_2_10_0_RC2, version_2_10_0_RC1, version_2_10_0, version_2_0_X, version_2_0_99_1, version_2_0_2, version_2_0_1, version_2_0_0, version_1_99_3, version_1_99_2, version_1_99_1_tmcc, version_1_99_1, version_1_99_0_tmcc, version_1_99_0, version_1_3_X, version_1_3_3, version_1_3_2, version_1_3_1, version_1_3_0, version_1_2_X, version_1_2_99_1, version_1_2_99_0, version_1_2_1, version_1_2_0, version_1_1_X, version_1_1_99_5, version_1_1_99_4, version_1_1_99_3, version_1_1_99_2, version_1_1_99_1, version_1_1_99_0, version_1_1_3, version_1_1_2, version_1_1_1, version_1_1_0, version_1_0_99_3, version_1_0_99_2, version_1_0_99_1, version_1_0_99, version_1_0_3, version_1_0_2, version_1_0_1, version_1_0_0, version_0_99_5, version_0_99_4, version_0_99_3, version_0_99_2, version_0_99_1, version_0_99_0, loncapaMITrelate_1, language_hyphenation_merge, language_hyphenation, conference_2003, bz6209-base, bz6209, HEAD, GCI_3, GCI_2, GCI_1, BZ4492-merge, BZ4492-feature_horizontal_radioresponse, BZ4492-feature_Support_horizontal_radioresponse, BZ4492-Support_horizontal_radioresponse
best wishes to all.

<HTML>
<TITLE>LON-CAPA Hardware Compatibility</TITLE>
<H1>LON-CAPA Hardware Compatibility</H1>
<P>
Last updated: 10/23/2000
</P>
<H3>Hardware Requirements</H3>
<P>
There are 4 hardware requirements for the current LON-CAPA system.
<UL>
<LI>i586 (or greater) intel architecture computer
<LI>ethernet card
<LI>static IP connection
<LI>4 gigabytes (or greater) hard drive space
<LI>CD-ROM
<LI>64 megabytes (or greater) of RAM
<LI>all hardware (monitors, ethernet cards, CD-ROMs, motherboard) must
be compatible with RedHat Linux 6.2.  A vendor compatibility list is at
<A HREF="http://www.redhat.com/support/hardware/intel/62/rh6.2-hcl-i.ld.html">
http://www.redhat.com/support/hardware/intel/62/rh6.2-hcl-i.ld.html</A>.
</UL>
</P>
<P>
</P>
<H3>Frequently Asked Questions</H3>
<P>
<OL>
<LI><B>Why can't I run the LON-CAPA system on a Sun Microsystem, 
MacOS-X, Windows-NT, or a LINUX-based system other than RedHat 6.2?</B>
<BR>The short answer is you can run LON-CAPA on most any type of 
computer, but you shouldn't.  The software system of LON-CAPA has
been designed with security and performance in mind.  Unless you are
prepared to understand the configuration details of the LON-CAPA network
layer and security issues specific to your operating system and machine
architecture, you will not be able to run LON-CAPA.  In the long-term,
alternate scenarios of running the LON-CAPA system will add significant
administrative overhead in terms of LON-CAPA software upgrades.
<LI><B>What about firewall configurations?</B>
<BR>Firewall configurations are doable, but not recommended.
This requires detailed understanding of the LON-CAPA network layer, reduces
network connectivity, and may require reconfiguration upon new software
releases
<LI><B>What about load-balancing hardware configurations?</B>
<BR>The good news is that LON-CAPA supports its own load-balancing
of web-delivered content.  The only relevant hardware configuration
is a static IP address and ethernet connection.  LON-CAPA takes care
of the rest.  Load-balancing should not be implemented with
other hardware/software configurations since this would alter the logic
by which LON-CAPA distributes and disseminates resources. 
<LI><B>What about backup tape drives and CD-ROM burners?</B>
<BR>There currently is no defined system of backing up LON-CAPA resources.
It is, however, both easily doable and highly recommended.  Every machine's
/home/httpd/html/res directory should be periodically saved in entirety.
Additionally, you may wish to save other machine-specific configuration
files such as /etc/httpd/conf/access.conf (for a description of these
files, go to <A HREF="http://install.lon-capa.org/3.1/loncapafiles/loncapafiles.html">
http://install.lon-capa.org/3.1/loncapafiles/loncapafiles.html)</A>.  As far as HOW you
save this, via a tape-drive or CD-ROM, that is your currently your
judgement call.  For more information on backing up Linux-based systems,
read <A HREF="http://www.medstv.unimelb.edu.au/~pierre/backup/Backup-HOWTO.html">
http://www.medstv.unimelb.edu.au/~pierre/backup/Backup-HOWTO.html</A>.
</OL>
</P>
<H3>Notes</H3>
<P>
A monitor and other peripherals are not necessary for anything but
the installation process.  Their inclusion with your computer system
is dependent on what level of convenience you think they provide.
</P>
</BODY>
</HTML>

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
500 Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at root@localhost to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.