version 1.1, 2000/04/26 18:17:10
|
version 1.2, 2000/05/23 16:33:28
|
Line 32 and securely <B>communicating potential
|
Line 32 and securely <B>communicating potential
|
LON-CAPA server machine. |
LON-CAPA server machine. |
<P> |
<P> |
This document is the functional model description which describes the computations |
This document is the functional model description which describes the computations |
and their expected results necessary to manage packaging and filesystem management |
and expected results necessary to manage packaging and filesystem management |
for LON-CAPA both now and in the future in a manner that is <B>synchronous</B> |
for LON-CAPA both now and in the future in a manner that is <B>synchronous</B> |
with software development, installations, and upgrades. Promulgation of coding |
with software development, installations, and upgrades. Promulgation of coding |
changes, version control, and maintaining a handle on security and network optimization |
changes, version control, and maintaining a handle on security and network optimization |
Line 49 management.
|
Line 49 management.
|
<BR>Red Hat Package Manager. A system to manage software applications (packages). This system tracks package |
<BR>Red Hat Package Manager. A system to manage software applications (packages). This system tracks package |
interdependencies, configuration files, and file alterations. The RPM packaging system can (and probably should) reside on a different |
interdependencies, configuration files, and file alterations. The RPM packaging system can (and probably should) reside on a different |
computer than the central file repository computer. The RPM packaging system should probably be on a computer |
computer than the central file repository computer. The RPM packaging system should probably be on a computer |
accessible to the |
accessible to programmers involved with system development. |
<LI><B>LCIC</B> |
<LI><B>LCIC</B> |
<BR>LON-CAPA Integrity Check. A script-based system which analyzes a computer to determine the RPM composition |
<BR>LON-CAPA Integrity Check. A script-based system which analyzes a computer to determine the RPM composition |
(missing or contrastingly extraneous RPMs), extraneous files which do not belong to any RPM, and RPM file |
(missing or contrastingly extraneous RPMs), extraneous files which do not belong to any RPM, and RPM file |
Line 233 other computers in the software developm
|
Line 233 other computers in the software developm
|
</UL> |
</UL> |
<P> |
<P> |
<LI><B>What are the specifics associated with the process LON_CAPA_update_RPM_build_tree?</B> |
<LI><B>What are the specifics associated with the process LON_CAPA_update_RPM_build_tree?</B> |
<BR>This process checkouts LON-CAPA directories and files. This process reads from the <TT>packaging/file_map.txt</TT>. |
<BR>This process checkouts LON-CAPA directories and files. This process reads from the <TT>packaging/file_map.txt</TT> and the |
This process reads RPM <TT>.spec</TT> template files to set up the two LON-CAPA RPMs (LON-CAPA-base and LON-CAPA-auxiliary). |
<TT>packaging/permissions.txt</TT> file. This process reads RPM <TT>.spec</TT> template files to set up the two LON-CAPA RPMs (LON-CAPA-base and LON-CAPA-auxiliary). |
These updated RPMs are placed into a pool of RPMs from which to generate the customized RedHat installation/upgrade CD. |
These updated RPMs are placed into a pool of RPMs from which to generate the customized RedHat installation/upgrade CD. |
A 'comps' file is generated to customize the grouping of packages on the CD image. The CD image is written and made accessible |
A 'comps' file is generated to customize the grouping of packages on the CD image. The CD image is written and made accessible |
on the web. |
on the web. |
Line 271 institution.
|
Line 271 institution.
|
[configuration settings that need to be saved?] |
[configuration settings that need to be saved?] |
[description of file and what it does] |
[description of file and what it does] |
</PRE> |
</PRE> |
|
<P> |
|
<LI><B>What is the correct format for the <TT>packaging/permissions.txt</TT> file?</B> |
|
<BR>Every line refers to a file or directory to install/upgrade on a LON-CAPA system. There are four/five fields to each line which are space-separated. |
|
File listing: |
|
<PRE> |
|
[octal mode] |
|
[user to own file] |
|
[group to own file] |
|
[file name] |
|
</PRE> |
|
Directory listing: |
|
<PRE> |
|
[octal mode] |
|
[user to own file] |
|
[group to own file] |
|
DIR |
|
[file name] |
|
</PRE> |
<UL> |
<UL> |
<LI><TT>[computer-type]</TT> - a list of capitalized letters indicating which computer-types this file is to be installed on. P=main packaging computer. A=LON-CAPA software development access server. L=LON-CAPA software development library server. C=central CVS file repository computer. PAL means this file is to be installed on the main packaging computer and the software development library and access servers. P means this file is to be installed on just the main packaging computer. AL means the file is to be installed on just the software development library and access servers. |
<LI><TT>[computer-type]</TT> - a list of capitalized letters indicating which computer-types this file is to be installed on. P=main packaging computer. A=LON-CAPA software development access server. L=LON-CAPA software development library server. C=central CVS file repository computer. PAL means this file is to be installed on the main packaging computer and the software development library and access servers. P means this file is to be installed on just the main packaging computer. AL means the file is to be installed on just the software development library and access servers. |
<LI><TT>[file location on CVS repository]</TT> - the file location on the CVS repository. For example, <TT>/loncom/htpasswd</TT>, <TT>loncom/startup.pl</TT>, and |
<LI><TT>[file location on CVS repository]</TT> - the file location on the CVS repository. For example, <TT>/loncom/htpasswd</TT>, <TT>loncom/startup.pl</TT>, and |