Free system requirements lab software for linux

All System Info is a system info SuperKaramba theme. Simple english version...
It shows:
- System Info
- CPU usage
- Network Usage
- Memory Load
- HDD usage

system-tools-backends is a package for GNOME.

to extract the configuracion

backend --get

to restore the configuration from XML

backend --set < file.xml

KIWI Image System provides a complete operating system image solution for Linux supported hardware platforms as well as for virtualisation systems like Xen Qemu or VMware. The KIWI architecture was designed as a two level system. The first stage, based on a valid software package source, creates a so called physical extend according to the provided image description. The second stage creates from a required physical extend an operating system image. The result of the second stage is called a logical extend or short an image.
A normal installation process is starting from a given installation source and installs single pieces of software until the system is complete. During this process there may be manual user intervention required. However an operating system image represents an already completed installation encapsulated as a file and optionally includes the configuration for a specific task. Such an operating system starts working as soon as the image has been brought to a system storage device no matter if this is a volatile or non volatile storage. The process of creating an image takes place without user interaction.
This means all requirements of the encapsulated system has to be fulfilled before the image is created. According to this the so called image description tree stores all the information needed to create an image.
Main features:
- Distribution independent
- Support for virtualisation systems like Xen
- Support for deploying images over the network
- Support for VMware / Qemu images
- Support for USB-Stick systems
- Support for LiveCD/DVD systems
- Centralized image description based on XML
- Prebuild boot images for SUSE systems
- Prebuild PXE configuration usable with kiwi netboot images
- SUSE Linux on a 128MB flash card.. yes thats possible

The tcp_wrappers package allows you to monitor and filter incoming requests for the SYSTAT, FINGER, FTP, TELNET, RLOGIN, RSH, EXEC, TFTP, TALK, and other network services. It provides tiny daemon wrapper programs that can be installed without any changes to existing software or to existing configuration files. The wrappers report the name of the client host and of the requested service. The wrappers do not exchange information with the client or server applications, so it does not impose no overhead on the actual conversation between the client and server applications.
It supports both 4.3BSD-style sockets and System V.4-style TLI. Praise yourself lucky if you dont know what that means.
The package provides tiny daemon wrapper programs that can be installed without any changes to existing software or to existing configuration files. The wrappers report the name of the client host and of the requested service; the wrappers do not exchange information with the client or server applications, and impose no overhead on the actual
conversation between the client and server applications.
Optional features are: access control to restrict what systems can connect to what network daemons; client user name lookups with the RFC 931 etc. protocol; additional protection against hosts that pretend to have someone elses host name; additional protection against hosts that pretend to have someone elses host address.
The programs are very portable. Build procedures are provided for many common (and not so common) environments, and guidelines are provided in case your environment is not among them.
Requirements are that network daemons are spawned by a super server such as the inetd; a 4.3BSD-style socket programming interface and/or System V.4-style TLI programming interface; and the availability of a syslog(3) library and of a syslogd(8) daemon. The wrappers should run without modification on any system that satisfies these requirements. Workarounds have been implemented for several common bugs in systems software.
What to do if this is your first encounter with the wrapper programs: 1) read the tutorial sections for an introduction to the relevant concepts and terminology; 2) glance over the security feature sections in this document; 3) follow the installation instructions (easy or
advanced). I recommend that you first use the default security feature settings. Run the wrappers for a few days to become familiar with their logs, before doing anything drastic such as cutting off access or installing booby traps.
Enhancements:
- Improved the anti source-routing protection. The code in version 7.5 was not as strong as it could be, because I tried to be compatible with Linux. That was a mistake. Sorry for the inconvenience.
-
- The program no longer terminates case of a source-routed connection, making the IP-spoofing code more usable for long-running daemons.
-
- When syslogging DNS hostname problems, always stop after a limited number of characters.

JWebPresenter project is a bitmap-image based Web presenting system.
It can add a Web extension to your favorite presentation tool, such as PowerPoint, MagicPoint, or Impress.
This is useful in distance learning, meeting, conferencing, and other situations.
It uses bitmap images to avoid compatibility problems. Other features include platform independence and simplicity.
Main features:
- Bitmap image based presenting: Hence we have no compatibility problem related to character corruption, locale, font, ... You can (and you must) use an authoring tool (e.g., PowerPoint, OpenOffice, MagicPoint, etc) to create the slides, then export into images to be presented with JWebPresenter.
- Platform independent: Any system satisfying the requirements should be OK, including Linux PC, Windows PC, PDA Sharp Zaurus SL-C760 (JWebPresenter SS v1.0x).
- Simplicity: I believe simple thing should be done simply. JWebPresenter SS v1.2.1 package (tar.gz) is only 36KB, including source, pre-compiled binarary, document, sample, and a 18KB (uncompressed size) license called GPL!
- Protocol and Image format independent: All protocols and image formats supported by JRE (Java Runtime Enviroment) should be OK.
- Efficience: There is little overhead in JWebPresenter.

Erlang is a programming language designed at the Ericsson Computer Science Laboratory.
Open-source Erlang is being released to help encourage the spread of Erlang outside Ericsson.
Installation
When installed, the entire system, except for a small start-up script, resides in a single directory tree. The location of this directory tree can be chosen arbitrarily by the installer, and it does not need to be in the users $PATH.
The only requirements are that the file system where it is placed has enough free space, and that the users who run Erlang/OTP have read access to it. In the example below, the directory tree is assumed to be located at /usr/local/erlang, which is here called the top-level directory.
It is assumed that you have the compressed tar file, the name of which is < PREFIX >.tar.gz, where < PREFIX > is a string denoting the particular Erlang/OTP release, e.g. otp_LXA_11930_sunos5_R9B.
Wherever the string < PREFIX > is used below, it should be replaced by the actual name prefix of the compressed tar file.
The tape archive file does not have one single directory in which all other files are rooted. Therefore the tape archive file must be extracted into an empty (newly created) directory.
1. If the top-level directory does not already exist, create it:
mkdir /usr/local/erlang
2. Change the current directory to the top level directory:
cd /usr/local/erlang
3. Create the installation directory with an appropriate name. For example:
mkdir otp_r7b
4. Change to the installation directory, e.g.
cd otp_r7b
5. Assuming the compressed tar file resides in the directory ,. extract the compressed tar file into the current directory:
gunzip -c / .tar.gz | tar xfp -
6. Read the README file in the installation directory for last minute updates, before proceeding.
7. Run the Install script in the installation directory, with the absolute path of the installation directory as argument,
./Install /usr/local/erlang/otp_r7b
and supply answers to the prompts.
In most cases, there is a default answer in square brackets ([]). If the default is satisfactory, just press . In general you are only prompted for one thing:
- "Do you want to use a minimal system startup instead of the SASL startup?"
In a minimal system, only the Kernel and STDLIB applications are loaded and started. If the SASL startup is used, the SASL application is included as well. Normally, the minimal system is enough.
8. Make Erlang/OTP available for users, either by putting the path /usr/local/erlang/otp_r7b/bin in users $PATH variable, or link the executable /usr/local/erlang/otp_r7b/bin/erl accordingly, e.g.:
ln -s /usr/local/erlang/otp_r7b/bin/erl /usr/local/bin/erl
Enhancements:
- Among other things, SMP support was added.