Free scsi software for linux

Scsiaddgui application provides a graphical user interface for the Scsiadd utility, which allows you to add or remove SCSI devices without having to reboot.

Sysinfo application displays system and computer information.
Main features:
- System: Linux distribution release, GNOME version, Kernel version, Gcc version, Xorg version, hostname.
- CPU: Vendor identification, model name, frequency, level2 cache, bogomips, model numbers, flags.
- Memory: Total system memory RAM, free memory, swap space total & free, cached, active, inactive memory.
- Storage: IDE interface, all IDE devices(disks, cd/dvd roms), SCSI devices.
- Partitions: IDE & SCSI device partition sizes

KnoSciences is a Knoppix bootable CD with a collection of GNU/Linux software, automatic hardware detection, and support for many graphics cards, sound cards, SCSI and USB devices and other peripherals. KnoSciences is not necessary to install anything.
Sciences SoftwareMain features:
Workstation software
- Evince
- FileRunner
- Firefox
- Gimp
- Gnumeric
- Kate
- Krusader
- Lyx
- NVU
- OpenOffice
- Rox-filer
- Scite
- Scribus
- Texmacs
- VLC media player
- VNC
- Xfce4
- XMMS
- Xpdf
Java software
- Edugraphe
- Geogebra
- Geonext
- JasTEX
- Java C.a.R
- NonEuclid
- NumericalChameleon
- Mathoscope
- Optikal
- Populus
- XLogo
Mathematical Software
- Xabacus
- Declic (french)
- Dr Geo
- Geomview
- Xeukleides
- Galculator
- Geg
- Giac/Xcas
- Gnuplot
- Grace
- Graphthing
- Kali
- Kseg
- Maxima
- PARI/GP
- Scilab
- Yacas
- XaoS
Sciences Software
- Audacity
- Chemeq
- Chemtool
- Dozzzaqueux (french)
- Formol
- Ghemical
- GNUcap
- GPeriodic
- KStars
- LibComedi
- Open Babel
- OptGeo (french)
- Oregano
- TkGate
- PyMOL
Systeme Software
- CUPS - Common Unix Printing
- Debian
- GCC (gcc & g++)
- KNOPPIX
- Perl
- Python
- QTParted
- TCC
- Xsane
- knoppix-installer

Swecha LiveCD is a bootable CD with the freedom to copy it and give it away to anyone.

It contains a collection of GNU/Linux Telugu localised software, automatic hardware detection, and support for many graphics cards, sound cards, SCSI and USB devices and other peripherals.

Swecha LiveCD can be used as a Telugu GNU/Linux demo, educational CD, rescue system, or adapted for other requirements. It is not necessary to install anything.

AFROS Live CD is a bootable CD with a small collection of GNU/Linux software, ARAnyM and the AFROS. AFROS Live CD boots and runs completely from CD, does not write anything to the harddrive and so is safe to try out. It is meant as a demo version of ARAnyM/AFROS. It is not the dreamed Installation CD of ARAnyM yet (although it could be modified to work so).

The underlying Linux kernel and related software provide the CD autoboot, automatic hardware detection, and support for many graphics cards, sound cards, SCSI and USB devices and other peripherals. ARAnyM plus AFROS provide our familiar and favourite TOS/FreeMiNT/GEM operating environment. Its all integrated seamlessly and after PowerOn boots straight to the Teradesk (GEM desktop).

AFROS Live CD is distributed in the form of a CD ISO image which is the usual way of distributing CDs electronically. The ISO image file can be burnt on a CD-R/RW and so youll get an exact copy of the AFROS Live CD I created on my machine.

AFROS Live CD configuration:

fVDI resolution and/or color depth change: open up the C:FVDI.SYS (double click it and select Edit), locate the "01r aranym.sys mode 800x600x16@72" line, comment it out and uncomment one of the other prepared lines (or just make up your own). Then reboot the AFROS.

The ARAnyM Config GUI is unfinished yet so changes to ARAnyM config must be done outside of ARAnyM in the .aranym/config file. When you quit ARAnyM you should be able to edit the file with one of the supplied GNU/Linux editors (in the future this shouldnt be necessary as I am working on the Config GUI as you read this).

DSL site (AFROS Live CD is based on the DSL) might give you some hints about preserving the changes youve made to the AFROS disk image or ARAnyM configuration (you might also want to read File Restoration -> HowTo in the X11 desktop). Note that this is untested by me and might be dangerous. Try it on your own risk only.

mpt-status is a query tool for accessing the running configuration and status of LSI SCSI HBAs. mpt-status is a heavily modified version of the original mpt-status-1.0 tool written by Matt Braithwaite.
It allows you to monitor the health and status of your RAID setup. Currently supported and tested HBAs are the LSI 1030 SCSI RAID storage controller and LSI SAS1064 SCSI RAID storage controller.
Since the tool uses the MPI (message passing interface), chances are high that the basic information regarding RAID status will be available for all LSI-based controllers.
Enhancements:
- This is the first release with proper 64-bit support and mostly clean interface querying.
- The mpt-status(8) man page has been added.
- Preliminary work has been done on integrating S.M.A.R.T information in the report output.
- This would allow one to monitor for failing hardware and preemptively replace it without business interruption.
- This information can be queried via the --newstyle/-n parameter.
- The new style parameter also provides you with the percentage status of the synchronization after a degradation.

Rocks Cluster is a complete "cluster on a CD" solution for x86 and IA64 Red Hat Linux COTS clusters.
Building a Rocks cluster does not require any experience in clustering, yet a cluster architect will find a flexible and programmatic way to redesign the entire software stack just below the surface (appropriately hidden from the majority of users).
Although Rocks includes the tools expected from any clustering software stack (PBS, Maui, GM support, Ganglia, etc), it is unique in its simplicity of installation.
From a hardware component and raw processing power perspective, commodity clusters are phenomenal price/performance compute engines. However, if a scalable ``cluster management strategy is not adopted, the favorable economics of clusters are offset by the additional on-going personnel costs involved to ``care and feed for the machine. The complexity of cluster management (e.g., determining if all nodes have a consistent set of software) often overwhelms part-time cluster administrators, who are usually domain application scientists. When this occurs, machine state is forced to either of two extremes: the cluster is not stable due to configuration problems, or software becomes stale, security holes abound, and known software bugs remain unpatched.
While earlier clustering toolkits expend a great deal of effort (i.e., software) to compare configurations of nodes, Rocks makes complete Operating System (OS) installation on a node the basic management tool. With attention to complete automation of this process, it becomes faster to reinstall all nodes to a known configuration than it is to determine if nodes were out of synchronization in the first place. Unlike a users desktop, the OS on a cluster node is considered to be soft state that can be changed and/or updated rapidly.
This is clearly more heavywieght than the philosophy of configuration management tools [Cfengine] that perform exhaustive examination and parity checking of an installed OS. At first glance, it seems wrong to reinstall the OS when a configuration parameter needs to be changed. Indeed, for a single node this might seem too severe. However, this approach scales exceptionally well, making it a preferred mode for even a modest-sized cluster. Because the OS can be installed from scratch in a short period of time, different (and perhaps incompatible) application-specific configurations can easily be installed on nodes. In addition, this structure insures any upgrade will not interfere with actively running jobs.
One of the key ingredients of Rocks is a robust mechanism to produce customized distributions (with security patches pre-applied) that define the complete set of software for a particular node. A cluster may require several node types including compute nodes, frontend nodes file servers, and monitoring nodes. Each of these roles requires a specialized software set. Within a distribution, different node types are defined with a machine specific Red Hat Kickstart file, made from a Rocks Kickstart Graph.
A Kickstart file is a text-based description of all the software packages and software configuration to be deployed on a node. The Rocks Kickstart Graph is an XML-based tree structure used to define RedHat Kickstart files. By using a graph, Rocks can efficiently define node types without duplicating shared components. Similiar to mammalian species sharing 80% of their genes, Rocks node types share much of their software set. The Rocks Kickstart Graph easily defines the differences between node types without duplicating the description of their similarities. See the Bibliography section for papers that describe the design of this structure in more depth.
By leveraging this installation technology, we can abstract out many of the hardware differences and allow the Kickstart process to autodetect the correct hardware modules to load (e.g., disk subsystem type: SCSI, IDE, integrated RAID adapter; Ethernet interfaces; and high-speed network interfaces). Further, we benefit from the robust and rich support that commercial Linux distributions must have to be viable in todays rapidly advancing marketplace.
Wherever possible, Rocks uses automatic methods to determine configuration differences. Yet, because clusters are unified machines, there are a few services that require ``global knowledge of the machine -- e.g., a listing of all compute nodes for the hosts database and queuing system. Rocks uses an SQL database to store the definitions of these global configurations and then generates database reports to create service-specific configuration files (e.g., DHCP configuration file, /etc/hosts, and PBS nodes file).
Enhancements:
- Rocks v4.3 is released for i386 and x86_64 CPU architectures. New features: Rocks command line - initial release of the Rocks command line which facilitates non-SQL administrative access to the database; PXE First - hosts can now be configured in BIOS with a boot order of CD, PXE, hard disk. Enhancements: based on CentOS 4.5 and all updates as of July 4, 2007; Anaconda installer updated to 10.1.1.63; performance improvement when building torrent files for the Avalanche Installer; database indirects, more flexibility with Rocks variables; Globus updated to gt4.0.4 with web services....