Free linux system administration software for linux

Linux Mobile System project (LMS) is a full Linux system whose support is the new USB Flash Memory Drives. The intention is to boot any PC with USB support with our system and therefore we will have every administration and analysis applications that we have selected, so we will not need install it. This way, always we will be able to get our Linux system ready to use in our pocket.
This project arose with the intention to study the Linux system of exhaustive way and simultaneously enjoy with it. The initial idea is to fuse two separated disciplines: the programming and the systems management. So well center our study in the denominated "system programming, as much networking level as at device level (drivers).
Main features:
- To initiate our Linux system from memories flash USB.
- The system will be a selection of common GNU tools in every system: disk diagnosis, memory, hardware, networks monitoring tools, etc.
- LMS Tux
- As far as possible well develop new tools and/or utilities with the objective to study deeply the underlying technology.
- The programming languages used will be C, C++, Python and Perl, without forget the system shell scripts.
- The resources minimization (disk space, memory...) isnt a functional objective of the developments.
LMSs main aim is to achieve a highly specialized distribution of GNU/Linux which can carried through the USB Flash Memory Drives. Once the distribution is ready in the USB device, it can be carried in your own pocket and you can start up any PC x86 with no need to install it directly in the PC.
The LMS system is aimed at the development of specific tasks such as network administration, security analysis of networks, and recovery and repair of host data, as well as all information exchange, which is what makes it different from other portable systems such as "live CDs". The main idea is to carry all the potency of Linux and our tools in our own pockets, ready to be used.

The main goal of the Linux Trustees project is to create an advanced permission management system for Linux. The solution proposed is mainly inspired by the approach taken by Novell Netware and the Java security API.

Special objects (called trustees) can be bound to every file or directory. The trustee object can be used to ensure that access to a file, directory, or directory with subdirectories is granted (or denied) to a certain user or group (or all except user or group).

Trustees are like POSIX ACLs, but trustee objects can affect entire subdirectory trees, while ACLs a single file. Trustees works with the 2.6 Linux kernel.

System Health Monitor for Linux is a handy python program that will setup your system to generate RRD Graphs of network interface traffic, system load, memory usage, disk space and inode usage and graphs of the number of running processes.

System Health Monitor features a user-friendly interactive configuration mode and auto-generated html pages. Just point your web server to the health_html directory to get an overview of the status of your machine. You can see examples of it in operation here on my machine and on KPLUG.org

System-7 Linux strives to set itself apart from other linux distros by tredding waters not offen attempted. These are the waters of package unity.

This means where most distros support 1 standard package format, System-7 will support most major pakage types including: rpm (.rpm), dpkg (.drb), and slackpack / pkgtools (.tgz).

System-7 will also sport a graphical installer based on group selections. With each group, the best possible speed and security settings will be pre-defined enabling this distro to be quickly deployed in any situation (from gaming to servers).

Linux Audio Backstop project is a system for automated scheduling of audio recording and playback in a broadcast environment.
It includes features for controlling external audio switcher devices by means of serial and TCP/IP commands, as well as the ability to record and playback relay closures by means of the line of digital GPIO cards manufactured by MeasurementComputing.
The Linux Audio Backstop runs on the popular GNU/Linux operating system. It is freely available under the GNU General Public License.
Main features:
- Record and Playback up to four feeds simultaneously.
- Programmable from any web browser.
- Supports capture and playout of up to twenty-four discrete relay closures.
- Very lightweight and efficient - a Pentium 1 system is capable of hosting a complete system
- Runs on the rock-solid GNU/Linux operating system.
- Totally free and open -- No dongles, unlock codes, software keys or other arbitrary limitations.

LibSysCTr is a utility library that can be used to intercept system call functions on a Linux system. Process monitoring and sandboxing are just two of the potential usages of LibSysCTr.

Internally the LibSysCTr library uses the ptrace(2) functionalities by monitoring and reporting events to the library caller.

The LibSysCTr is callback driven, that means that the user initializes the library with systr_init_library(), registers the system calls he wants to monitor with systr_trace_syscall(), and calls systr_run() to start receiving events in the form of callback invocation.

For each intercepted system call, two calls to the registered callback function are performed. One during the system call entry, before the system call iteself will be executed by the kernel, and one after the kernel has processed the system call (right before returning the userspace).

Utility functions are supplied to, retrieve information about the process, get/set the system call parameters, and read/write the monitored process address space.

The LibSysCTr library follows all threads and processes spawned by the traced task, by giving the caller the complete control over the whole monitored process hierarchy.

Installation:

The `configure shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile in each directory of the package.

It may also create one or more `.h files containing system-dependent definitions. Finally, it creates a shell script `config.status that you can run in the future to recreate the current configuration, and a file `config.log containing compiler output (useful mainly for debugging `configure).

It can also use an optional file (typically called `config.cache and enabled with `--cache-file=config.cache or simply `-C) that saves the results of its tests to speed up reconfiguring. (Caching is disabled by default to prevent problems with accidental use of stale cache files.)

If you need to do unusual things to compile the package, please try to figure out how `configure could check whether to do them, and mail diffs or instructions to the address given in the `README so they can be considered for the next release.

If you are using the cache, and at some point `config.cache contains results you dont want to keep, you may remove or edit it.

The file `configure.ac (or `configure.in) is used to create `configure by a program called `autoconf. You only need `configure.ac if you want to change it or regenerate `configure using a newer version of `autoconf.

The simplest way to compile this package is:

1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system.

If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.

Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.

2. Type `make to compile the package.

3. Optionally, type `make check to run any self-tests that come with the package.

4. Type `make install to install the programs and any data files and documentation.

5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean.

There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.

StrongBox is a next generation Linux-based operating system, incorporating tight version control, digital signatures, high security and built-in change management.
StrongBox represents a shift in the Linux paradigm. Moving away from monolithic systems where everything runs together, StrongBox is a fully modular Linux distribution.
It incorporates a small ram-based OS and toolset for administration and security functions, and then allows applications bundles, built using any Linux distribution, to run on top of it. Each of these bundles, running in a secure virtual context, has a large level of independence from the base OS.
This secure partitioning allows StrongBox to have some unique and powerful features. OS versioning, rollbacks, automated hardware detection, fault-tolerant boot process, easy migration from server-to-server, and the ability to incorporate other Linux distributions and existing installations are key features.
StrongBox gets its name from the high standard of security that it provides. Using virtual servers, digital signatures on all OS components, and a large number of read-only pieces in the OS, StrongBox is highly resistant to security breaches.
Also, it has virtual boot medium independence, meaning that it can run with little or no changes from CDRom, compact flash, USB, SCSI, etc. This makes StrongBox ideal for the secure deployment of embedded systems, computing clusters, enterprise Linux deployments, secure web servers, PBX systems, and kiosk systems.
Enhancements:
- makerpm and makedebian scripts greatly improved
- asteriskathome build script
- Improved usb authentication, and automatic key selection for USB keys
- Added a gcc, distcc, linux headers, and kernel source add-ons
- Unionfs, bind, vrenice, rpm, hashlimits subsystem
- Larger default config partition (12MB)
- dmraid support re-added (use dmraid kernel parameter on boot)
- Updated versions of all software