Free bestix 2006 04 05 software for linux

BeaFanatIX is a mini Live CD Linux distribution. It was originally a remaster of BeatrIX but now uses a more recent Ubuntu core (more on that below). BeatrIX itself is partly on an old version of Ubuntu, but makes heavy use of Knoppix technologies. The common ancestor of all these distributions is Debian.

Whats the catch? Youll get a fully functional desktop operating system running off a standard or a mini (3", 8cm) CD-ROM (or CD-RW). The only thing your computer needs to be capable of is booting from CD - most modern machines can do that without any problem. Apart from using it as a Live CD, you can also install it to your hard drive as an independent operating system, so if you like it, put it on your hard drive and enjoy enhanced speed, usability and efficiency!

BeaFanatIX inherits some very useful features from the distributions it is based on:

Knoppix has excellent hardware recognition and comes with a usable installation script.
Ubuntu is geared towards the desktop and ease of use.

Debian gives you access to a vast amount of software packages ready for immediate use.
BeatrIX is highly portable and has been optimised to run even on older and less potent hardware - thats why Bea* (BeatrIX or BeaFanatIX) may be the best way to revive an old computer sitting useless in a corner of your attic!

BeaFanatIX, true to its BeatrIX roots, has been optimised to enable even a less experienced user to have a working desktop within minutes - work with documents, surf the web and communicate over the internet. Weve chosen a slightly different approach, though: While slimming down the ISO image even further, weve integrated a number of useful software packages without sacrificing key functionality - and without exceeding the size limitations for a mini Live CD.

Delta project assists users in minimizing "interesting" files, subject to a test of their "interestingness".
A common such situation is when attempting to isolate a small failure-inducing substring of a large input that causes a program to exhibit a bug.
The best way to understand how to use delta is with an example of its usage. Below is one example helpfully written up for me by Simon Goldsmith; read it first. For those wanting more, I also wrote a more detailed and harder to read document describing each tool: Using Delta.
Note that what follows is an example of using delta to minimize an input file to a program that reads programs, much as a compiler does. Note two features of file minimization that are present in the example.
Do a controlled experiment.
Below we dont just minimize a file that causes Oink to produce an error message, we minimize a file that causes gcc to accept AND oink to reject in a specific way. That is, the test delta does is a controlled experiment, where gcc is the control. Ignoring this aspect of the problem seems to be a frequent mistake of first time users.
Exploit nested structure.
One may minimize files of simpler syntax than C++ but really all files are interesting in the first place because they are in some language or another. Some simple configuration files are literally just a list of lines but most languages have some nested structure. Multidelta filters the input through the topformflat utility (included) to suppress any newlines past a particular nesting depth; this "explains" the nesting structure to the otherwise line-oriented delta utility (a brilliantly simple idea of Scott McPeaks).
If your input file language has no nesting structure, you can hack on multidelta to remove the filtration through topformflat or just use the raw delta program. If your language has a different nesting structure than C/C++, you can write your own multidelta and substitute it. A simple flex program should suffice; it need not be terribly accurate for delta to do well.
Enhancements:
- It is now much easier to stop delta.
- It catches signals and distinguishes them from return codes.
- It watches for the DELTA-STOP file at the same granularity as the tests are run.
- In multidelta, running the input file through cpp is off by default and can be turned on with the flag -cpp.

Alba-Experiment is an implementation of Gentoo over Solaris or Portage for Solaris.

Alba-Experiment is not a simple package management system, but has the ambition to transform a Solaris system to a full GNU-based development, build, and desktop environment.

Known Issues

Stage1.5 Release 2006.04.06

* problem with zlib: /usr/lib/libz.so is a GNU ld script, it should be a link

MMUSBAUDIO (formerly known as USBUA100) is a Linux kernel module device driver for the Roland / Edirol desktop audio devices.
It works with next devices:
UA-1EX
UM-1
UA-5
UA-100
SC-8850
The Advanced Linux Sound Architecture (ALSA) supports many USB audio devices. It is provided with most major distributions of Linux and is recommended in most cases. However, OSS compatibility is needed for some older (and simpler) applications and ALSA does not provide Open Sound System (OSS) backwards compatibility for 24-bit USB devices like the UA-5 that use 6 bytes per URB. Also, the ALSA programming interface is extremely complicated compared to the relatively rudamentary (and considerably less robust) OSS interface. Therefore, MMUSBAUDIO is provided as an alternative.
All of the supported devices use protocols similar to the USB-Audio and USB-MIDI standards. Therefore, MMUSBAUDIO should be relatively easy to upgrade for other devices.
Enhancements:
- Upgrade to support UA-1EX.
- Change mmusbaudio_find_audio_endpoints() to assign devices based on endpoint rather than simply using endpoints as signatures for device type. Needed since UA-1EX and UA-5 use different endpoint addresses.

lifstat is a small Linux utility that reads /proc/net/dev and reports input and output statistics for network interfaces.
Edit the Makefile to change PREFIX from the default /usr/local if you want.
$ make
($ su)
$ make instal
Enhancements:
- Multiple interfaces will be displayed by adding extra "-i interface" arguments.

rvi is a shell script that can give you an easy way of integrating RCS with your existing vim/vi work environment.

Simply use "rvi filename" instead of "vim filename", and the file will automatically be checked into revision control, and the changes you made after the edit will be displayed each time you finish editing.

Ever wanted to see what has changed to a configuration file?
Ever wanted to go back to where you where before some big change?
Ever wondered who changed your configuration files, and in what way?
Ever wanted the safety of knowing you can undo whatever changes you make to a config file?
Ever wanted to edit files in multi user environments without unknowingly overwriting others work?

rvi is a wrapper script which gives you an easy way of integrating RCS with your existing vim/vi work environment.

Simply use rvi filename instead of vim filename and the file will automatically be checked into revision control, and the changes you made after the edit will be displayed each time you finish editing. Eg:

reenen@tux$ rvi index.html
RCS/index.html,v --> index.html
revision 1.1 (locked)
done

... you edit the file here, and once done:

"index.html" 25L, 916C written
===================================================================
RCS file: RCS/index.html,v
retrieving revision 1.1
diff -u -r1.1 index.html
--- index.html 2006/02/09 09:59:14 1.1
+++ index.html 2006/02/09 10:00:57
@@ -1,6 +1,7 @@



+



RCS/index.html,v > added title.
>> .
done

... the changes are displayed and the new revision checked in.