Free resources software for linux

itools is a collection of Python libraries which provides a wide range of capabilities.
itools includes an abstraction over directory and file resources, a search engine, type marshallers, datatype schemas, i18n support, URI handlers, a Web programming interface, a workflow interface, and support for data formats such as (X)HTML, XML, iCalendar, RSS 2.0, and XLIFF.
Packages:
itools.catalog
itools.datatypes
itools.gettext
itools.handlers
itools.html
itools.i18n
itools.ical
itools.resources
itools.rss
itools.schemas
itools.tmx
itools.uri
itools.web
itools.workflow
itools.xhtml
itools.xliff
itools.xml
Enhancements:
- The most important change of this release is the new mechanism to send email in the CMS.
- Now the message spool is persistent and messages are written to disk before being sent, which makes the system robust against crashes.
vA bunch of user interface improvements and bugfixes were made in the CMS, including the Tracker and the Wiki.

Crypt::OpenSSL::CA::Resources is a bibliography of documentations and tools that I found helpful for implementing X509 PKIs in Perl over all these years.

This package performs the cryptographic operations necessary to issue X509 certificates and certificate revocation lists (CRLs). It is implemented as a Perl wrapper around the popular OpenSSL library. All certificate and CRL extensions supported by OpenSSL are available, and then some.

guglhupf commons resource repository is a tool that manages dependencies between program resources (e.g., Java jar files).
guglhupf commons resource repository comes with a mechanism to download needed resources from a central repository and stores these resources in a local repository. This allows reuse of resources between different projects.
Main features:
- Central resource repository to share resources between multiple projects.
- Needed resource are downloaded and stored in a local repository.
- Dependencies between resources are solved.
- Setup the classpath with all needed resources (jars).
- Start java progams with the needed resources.
- Ant integration to setup the classpath.
- Modular ant build script support
- Eclipse classpath builder to setup the classpath in eclipse.

Resource::Loader is a Perl module to load different resources depending.

SYNOPSIS

use Resource::Loader;

$loader = Resource::Loader->new(
testing => 0,
verbose => 0,
cont => 0,
resources =>
[
{ name => never,
when => sub { 0 },
what => sub { die "this will never be loaded" },
},
{ name => sometimes 50%,
when => sub { int rand 2 > 0 },
what => sub { "sometimes was loaded. args: [@_]" },
whatargs => [ qw/foo bar baz/ ],
},
{ name => sometimes 66%,
when => sub { int rand @_ },
whenargs => [ 0, 1, 2 ],
what => sub { "sometimes was loaded. args: [@_]" },
whatargs => [ qw/foo bar baz/ ],
},
{ name => always,
when => sub { 1 },
what => sub { "always was loaded" },
},
],
);

$loaded = $loader->load;
$status = $loader->status;

Resource::Loader is simple at its core: You give it a list of resources. Each resource knows when it should be triggered and if its triggered, will run its code segment.

Both the when and the what are coderefs, so you can be as devious as you want in determining when a resource will be loaded and what, exactly, it does.

I originally wrote this to solve a simple problem but realized that the class is probably applicable to a whole slew of problems. I look forward to hearing to what devious ends you push this module. Really, send me an email - I love hearing about people using my toys.

TN3270RG is a TCP/IP TN3270 gateway that dynamically assigns resources to a connection from a pool of available addresses. Features include an easy to use web interface for management and a PostgreSQL database backend.
It is useful if you have a large number of machines connecting to a TN3270 host, but for whatever reason the host itself cannot assign resources from a pool. TN3270 will keep track of a pool of resources in a PostgreSQL database (should work with other databases as well) and dynamically allocate a resource to each connnection that goes through it.
Simply configure the daemon so it knows the address of the real TN3270 host, set the resource pool up using the web management software, and point your clients to the address of the gateway.
In the client configuration set your resource to what you have the replacement token set to (!_TN3270RG_RESOURCE_! by default) and when the daemon sees that resource go by, it will substitute the resource it has allocated for the connection and pass the rest of the data stream unaltered to the host.
TN3270 Resource Gateway project is designed to be fast and stable and should recover gracefully from most errors including unexpected disconnections and database errors. It is written in Perl and uses the POE framework.
Enhancements:
- This release uses Sys::Syslog (which is actively maintained and is included in the main Perl distribution).
- All Syslog calls have been updated to prevent a highly unlikely (but still possible) format string vulnerability.
- It cleanly exits from a SIGTERM with useful logging information.

Shezhu Resource Sharing System project is an application for scheduling and booking shared resources such as rooms and equipment.
The client only needs a modern Web browser.
It has a user friendly point and click interface, visual filters for making block/repeat bookings, concurrent users and double booking prevention, allows local site customization, and supports configurable academic term/semester blocks.
Main features:
- Portable - client only needs a modern web browser
- Point and Click - almost no typing required
- Intuitive - simple, obvious, consistent and user friendly
- Innovative - visual filters for making block/repeat bookings
- Powerful - concurrent users and double booking prevention
- Configurable - local site customization supported
- Useful - built in support for configurable academic term, semester and session blocks
- Free!
Requirements
In order to run or build the Shezhu Resource Sharing System you need some third-party software available on your machine.
Client
The client needs a modern web browser and the best browsers for this application are Firefox, Mozilla (including the Netscape branded equivalent and Gecko derivatives such as Galeon) and Microsoft Internet Explorer. The newest versions of all these browsers will work best. This application also works with the Konqueror and Opera browsers but these have some issues which may affect functionality. All browsers need JavaScript enabled. Any of these browsers may not work properly (or at all) depending on the operating system they are running under. Text based browsers (such as Lynx) are not supported.
For a comprehensive list of supported client browsers and operating systems refer to this browser compatibility chart from the most recent release of the application.
Server
The server needs recent versions of the Apache web server and the MySQL database server.
The server has only been tested on Redhat9 and FedoraCore3 Linux/i386 platforms although there is no specific reason why it should not work on other Linux platforms and distributions.
Development
Rebuilding this application from source requires a standard Unix development environment with the sh, make, cc, cpp, sed and awk utilities. Also required are RCS, Perl (5.6+) and the ImageMagick program. Also required is RPM to build a distribution. All these programs would probably come as standard in Linux distributions, other platforms may not have all of them by default.
Enhancements:
- This release adds support for Apache2 and multi-site installations, internal restructuring, a better installation tree, and improved access control management.

Storage Resource Broker is client-server middleware that provides a uniform interface for connecting to heterogeneous data resources over a network and accessing replicated data sets.
SRB, in conjunction with the Metadata Catalog (MCAT), provides a way to access data sets and resources based on their attributes and/or logical names rather than their names or physical locations.
Starting with SRB 2.1.1 we now have an install script, install.pl, that can do a complete Postgres, MCAT and SRB installation. See README.MCAT.INSTALL. With SRB 3.0.0, this script can run on Solaris too, as well as the original Linux and Mac OS X.
The SEA authentication system is no longer recommended; for the secure authentication use either the ENCRYPT1 form of MDAS_AUTH authentication, or GSI. It should be noted that if the SEA authentication scheme is to be used and if the SEA library (libsea.a) does not already exist on your build platform, the SEA software that can be downloaded at the
URL must be built first.
1) Build configuration.
This version uses the configure script to configure the build. Most of the configurable parameters for building the SRB server and client can be configured using the "./configure" script. Run "./configure --help" for more information.
All configurable parameters for building the SRB server and the client library, including those set by the configure script, are defined in the mk/mk.config.in file. (The configure script automatically generates a third file, mk/mk.config, using mk/mk.config.in as a
template.)
Those parameters that cannot be modified via the configure script (because flags for those parameters have not yet been implemented) are set by directly editing the mk/mk.config.in file prior to running "./configure". Comments in the mk/mk.config.in file make it clear whether or not a particular parameter can be set through the configure
script, and if so, how to do so.
NOTE: The configure script does a number of self tests before the configuration is carried out. One of the test it does is the compiler test which it assumes "gcc" as the default compiler. If "gcc" is not installed or if the test of "gcc" failed (which happened on an AIX platform), the configure script should be re-run with the env variable CC set to cc or other compilers. This will override the default in the compiler test.
If the configure script still failed, do the following:
a) cd SRB2_0_0rel
b) ./config.rescue
c) edit the mk/mk.config file
2) Configure examples
a) Non-MCAT-enabled server and client, type in
configure
This will configure the mk.config file to build a non-MCAT enabled
server and client with the default settings.
b) Non-MCAT-enabled server and client with java enabled, type in
configure --enable-javagui=yes --enable-jdkhome=/usr/local/apps/jdk1.4.1
where /usr/local/apps/jdk1.4.1 is the directory where the JAVA JDK 1.4.1
is installed.
c) MCAT-enabled server with Oracle 8.1.5 MCAT, type in
configure --enable-oramcat --enable-oraver=815
--enable-orahome=/usr/local/apps/oracle/product/8.1.7
where /usr/local/apps/oracle/product/8.1.7 is the Oracle home
directory.
2) Parameters in the mk/mk.config file
The SRB architecture supports multiple SRB servers running on various hosts. Each SRB server may be built with different options, as set by the configure script and/or defined in the mk/mk.config.in file. For example, the SRB server on host A may include the driver for accessing HPSS and the SRB server on host B may include the driver for accessing the Lobj stored in DB2, etc.
The parameters are self-explanatory through the comments given in this file. Some of the more important parameters are discussed below:
installDir - The absolute path of the SRB install directory.
PORTNAME - The OS platform of this SRB port. Currently, the SRB software runs on 8 platforms. i.e., valid PORTNAMEs are :
PORTNAME_solaris, PORTNAME_sunos, PORTNAME_linux, PORTNAME_osx,
PORTNAME_aix, PORTNAME_alpha, PORTNAME_c90 and PORTNAME_sgi.
SRB_LARGEFILE64 - defines whether the 64 bit file size is supported by the underlining driver of this SRB server. Current, 64 bit file size is supported by the ORTNAME_solaris, PORTNAME_aix, PORTNAME_linux and PORTNAME_c90 platforms.
ORAMCAT - defines that this SRB server being built is MDAS enabled and the MCAT is stored in Oracle DBMS. Normally, only one SRB server is MDAS enabled.
DB2MCAT - defines that this SRB server being built is MDAS enabled and the MCAT is stored in Oracle DBMS. Normally, only one SRB server is MDAS enabled.
NOTE : Both ORAMCAT and DB2MCAT cannot be defined at the same time.
ADDR_64BIT - defines whether to compile for 64 bits address. This option has only been tested for the the Solaris and Linux platforms.
PARA_OPR - defines whether this SRB server support parallel operation API.
MDAS_AUTH - defines whether the plain text and encrypted password MDAS authorization scheme will be supported. If used, the user/passwd pair registered with the MDAS catalog will be used to authenticate a user. Comment it out if the SRB server does not support MDAS authorization.
NOTE : A server can be built to support either MDAS_AUTH (plain or encrypted (ENCRYPT1)) or GSI_AUTH, or both.
SEA_AUTH - defines whether SEA authorization scheme will be supported. The software can be configured to support both SEA_AUTH and MDAS_AUTH. (SEA is no longer recommended.)
LIB_SEA - Is needed only if SEA_AUTH is defined. LIB_SEA specifies where the SEA client library is located.
GSI_AUTH - defines whether the GSI authentication scheme is supported. This is set when --enable-gsi-auth is included on the configure line.
NOTE : A server can be built to support either MDAS_AUTH or GSI_AUTH,
or both.
LIB_GSI_AUTH - Set by configure when --enable-gsi-auth is included (i.e. GSI_AUTH is defined). LIB_GSI_AUTH specifies where the GSI client libraries are located. The optional configure --enable-globus-location=path can also be used specify the parent
location of the GSI libaries, and will cause LIB_GSI_AUTH to be adjusted.
JAVA_GUI and javaDir - JAVA_GUI defines whether the srbBrowser should be built. javaDir specifies the directory where the JDK software is installed. (e.g. /usr/local/apps/Java). See README.srbBrowser for more details.
3) "cd" to the main SRB directory and type in "gmake clean" and then "gmake" to make the SRB software. The Makefile contains various options to make and clean all or a subset of the build.
- gmake --- build all.
- gmake clean --- clean all.
- gmake srb --- build only the SRB server and client.
- gmake clean_srb --- clean only the SRB server and client.
- gmake util --- build only the utilities (S commands). See README.utilities for more details.
- gmake clean_util --- clean only the utilities.
- gmake browser - build only the java srbBrowser GUI. See README.srbBrowser for more details.
- gmake clean_browser - clean only the java srbBrowser.
4) (Optional) Type in "gmake install" to install the software in the $(installDir) directory. This procedure installs the following modules in the $(installDir) directory:
bin/runsrb - The script that starts the SRB
bin/srbMaster2_0_0 - The frontend server.
bin/srbServer - The backend server (forked by the srbMaster1_0 for each client connection).
bin/libSrbClient.a - The client library.
data/hostAuthConfig - The optional (needed only if HOST_BASED_AUTH in the mk.config file is set) host based authorization configuration file.
data/mcatHost - This file identifies the host on which the MCAT enabled SRB server is running.
data/hostConfig - This is the optional SRB host configuration file. It is only needed when when you want to add aliases to your local hostName.
data/hpssCosConfig - This is the optional HPSS Class of Services configuration file. It is only needed if HPSS in the mk.config file is set.
data/hpssNodceAuth - The file contains authentication info for non-dce HPSS. It is only needed if the HPSS and NO_DCE flags in the mk.config file are set.
data/MdasConfig - The MDAS configuration file.
data/metadata.fkrel - This file defines the foreign key relationship between the MDAS catalog tables and is used internally by the SRB for query generation. This file should not be changed between releases.
data/LobjConfig - The database configuration file for the DB Large Object driver. Basically, it contains the userID and password for accessing each database server.
Enhancements:
- Three vulnerabilities that allow SRB users to read/write non-Vault files that are readable/writable by the the srbadmin user were fixed.
- A bug that causes the GridFTP driver to use the wrong credential to connect to GridFtp server was fixed.
- A file descriptor lock bug was fixed.
- Uploading files larger than 2 gigabytes into GridFtp resources now works.
- Timeout bugs that could arise when sending large numbers of files were fixed.
- A core dump problem for HPSS type resources involving parallel I/O on Linux servers was fixed.
- A new option -o was added to show collection ownership in SgetColl.