doc/otherfiles/otherfiles.html - view

File: [LON-CAPA] / doc / otherfiles / Attic / otherfiles.html
Revision 1.7: download - view: text, annotated - select for diffs
Wed Oct 4 14:20:46 2000 UTC (23 years, 7 months ago) by harris41
Branches: MAIN
CVS tags: version_0_6_2, version_0_6, version_0_5_1, version_0_5, version_0_4, stable_2002_spring, stable_2002_july, stable_2002_april, stable_2001_fall, STABLE, HEAD

Had to fix link to anaconda interface documentation. -Scott

<HTML> <HEAD> <META NAME="GENERATOR" CONTENT="Scott Harrison and Emacs. Version 3.14159265358979"> <TITLE>LON-CAPA Auxiliary Software Package Files and Directories</TITLE> </HEAD> <BODY BGCOLOR=#FFFFFF> <H1>LON-CAPA Auxiliary Software Package Files and Directories</H1> Scott Harrison, September 2000 CVS location: doc/otherfiles This page shows applications and software packages which are secondary (yet still necessary) to the proper functioning of the LON-CAPA network code. <TABLE VALIGN=TOP> <TR VALIGN=TOP> <TD> <IMG HEIGHT=32 WIDTH=32 SRC="working.gif" ALT="working"> a "bug-free", working external software package </TD> <TD> <IMG HEIGHT=32 WIDTH=32 SRC="almostfixed.gif" ALT="almost fixed"> an external software package that is a little buggy and is being worked on </TD> <TD> <IMG HEIGHT=32 WIDTH=32 SRC="bug.gif" ALT="bug">an external software package that has a bug and is currently on the backburner (not being worked on) </TD> <TD> <IMG HEIGHT=32 WIDTH=32 SRC="notmade.gif" ALT="not made">an external software feature that has yet to be really developed, despite possible exploratory work (this may be added to an existing package, or may constitute a new package) </TD> </TR> </TABLE> <TABLE BORDER=2> <TR BGCOLOR=#000000 VALIGN=TOP> <TH>Status</TH> <TH>Name</TH> <TH>Description</TH> <TH>Note</TH> </TR> <TR VALIGN=TOP> <TD><IMG SRC="working.gif" ALT="working"></TD> <TD>krb4 <A HREF="krb4.html">[Synopsis]</A> <A HREF="LON-CAPA-krb4-3.1-1.i386.rpm">[RPM]</A></TD> <TD> From the original source web site: "Kerberos is a system for authenticating users and services on a network. It is built upon the assumption that the network is "unsafe". For example, data sent over the network can be eavesdropped and altered, and addresses can also be faked. Therefore they cannot be used for authentication purposes." </TD> <TD> Original source came from: http://www.pdc.kth.se/kth-krb/ krb4-0.10.1.tar There are good RPMs for kerberos version 5, however many educational institutions are only compatible with version 4 (and version 4 has its advantages). </TD> </TR> <TR VALIGN=TOP> <TD><IMG SRC="working.gif" ALT="working"></TD> <TD>mysql <A HREF="mysql.html">[Synopsis]</A> <A HREF="LON-CAPA-mysql-3.1-1.i386.rpm">[RPM]</A></TD> <TD>SQL database server</TD> <TD>Original source came from: http://www.mysql.com mysql-3.22.32.tar.gz </TD> </TR> <TR VALIGN=TOP> <TD><IMG SRC="working.gif" ALT="working"></TD> <TD>systemperl <A HREF="systemperl.html">[Synopsis]</A> <A HREF="LON-CAPA-systemperl-3.1-1.i386.rpm">[RPM]</A></TD> <TD>Various perl modules built from CPAN, but do not exist as well-supported RPMs. These modules implement important functionality as well as serving as APIs for system application resources (like kerberos and MySQL).</TD> <TD>These are the CPAN downloads (http://www.cpan.org/): <PRE> Crypt-DES-2.01.tar.gz Crypt-IDEA-1.01.tar.gz DBI-1.14.tar.gz Digest-MD5-2.12.tar.gz HTML-Parser-3.13.tar.gz IO-1.20.tar.gz Krb4-1.1.tar.gz MIME-Base64-2.11.tar.gz MIME-tools-5.316.tar.gz Msql-Mysql-modules-1.2215.tar.gz URI-1.09.tar.gz libnet-1.0703.tar.gz libwww-perl-5.48.tar.gz </PRE> </TD> </TR> <TR VALIGN=TOP> <TD><IMG SRC="working.gif" ALT="working"></TD> <TD>Minimal RPM set <A HREF="rpm_list.txt">[Synopsis]</A></TD> <TD> The set of RedHat standard 6.2 RPMs (including security upgrades) needed for correct functioning of the LON-CAPA server.</TD> <TD> http://www.redhat.com 6.2 plus upgraded packages </TD> </TR> <TR VALIGN=TOP> <TD><IMG SRC="working.gif" ALT="working"></TD> <TD>Developer RPM Set <A HREF="rpm_list.txt">[Synopsis]</A></TD> <TD>A superset of the Minimal RPM set which has RPMs useful for those developing a LON-CAPA server (X-windows, GNOME, various scripting and other utilities). </TD> <TD> http://www.redhat.com 6.2 plus upgraded packages </TD> </TR> <TR VALIGN=TOP> <TD><IMG SRC="almostfixed.gif" ALT="almost fixed"></TD> <TD>Installation/Upgrade/Reconfiguration <A HREF="../anaconda_interfaces/index.html">[Interface snapshots]</A></TD> <TD>A Python/TK interface set (orig. Redhat's "anaconda" package) is customized for LON-CAPA specific system maintenance and upgrade.</TD> <TD>Interfaces have been scripted. Need to bug-proof data storage and passing between interface screens as well as system file interactions.</TD> </TR> <TR VALIGN=TOP> <TD><IMG SRC="bug.gif" ALT="bug"></TD> <TD>Complete source-to-CD build</TD> <TD>Separate from external software package building. This step is done when 1 command will read, build, compile, package, and burn a CD based on: <UL> <LI>LON-CAPA base source code <LI>Operating System <LI>Operating System customizations </UL> in a well-documented working manner. </TD> <TD>A key step in all of this is to have all the LON-CAPA base source code automatically build into an RPM.</TD> </TR> <TR VALIGN=TOP> <TD><IMG SRC="notmade.gif" ALT="not made"></TD> <TD>System Initialization Configuration</TD> <TD>Start all needed modules and daemons upon system boot-up.</TD> <TD>Already have written a setuid-ed (runnable by 'www') /etc/rc.d/init.d/loncontrol script. Needs to be greatly perfected and enhanced. Should also continually recheck (and if needed) reinitialize SQL database.</TD> </TR> <TR VALIGN=TOP> <TD><IMG SRC="bug.gif" ALT="bug"></TD> <TD>System Monitoring</TD> <TD>Have the system perform self-diagnostics and post status reports (as well as reacting to "bad" things like zombies).</TD> <TD><TT>loncron</TT> has been used; we've been running it every three hours through crontab. Still some significant problems, including a slow start-up.</TD> </TR> <TR VALIGN=TOP> <TD><IMG SRC="bug.gif" ALT="bug"></TD> <TD>Database blocking</TD> <TD>Handle database requests through a separate parent-child daemon network layer.</TD> <TD><TT>lonsql</TT> has been written and implemented in some tests of <TT>loncron</TT>. SQL database requests have been working, but <TT>lonsql</TT> needs to be trained to assess database status better and work with the metadata layer more closely. In other words, this scheme works, but there's a lot left to do. </TD> </TR> </TABLE> </BODY> </HTML>