Free borang spa 8 software for linux

Baghira is a native style for QT/KDE.

The name refers to the Panther of Kiplings famous Jungle Book (German spelling)

You will probably rather know the Disney version...

Basically its a perky imitation of Apples OSX look.

Installation:

tar -xjf baghira.tar.bz2
cd baghira/baghira
./configure --prefix=`kde-config --prefix` --disable-debug [--enable-final]
(!!!BEGINNERS: the direction of the accents is _important_ (top-left to bottom-right), the rectangular brackets mean [this is optional] - dont type them!!!)
make
and finally as root:
make install

GNU Parted is a program for creating, resizing, destroying, checking and copying partitions, and the file systems on them. This is useful for creating space for new operating systems, reorganising disk usage, copying data between hard disks and disk imaging.
Supported disk labels: raw access (useful for RAID and LVM), MS-DOS partition tables, Intel GPT partition tables, MIPS partition tables, PC98 partition tables, Sun and BSD disk labels and Macintosh partition maps.
Notes:
- For ext2, ext3 and reiserfs: the start of the partition must stay fixed.
- For ext2, ext3: the partition you copy to must be bigger or exactly the same size as the partition you copy from.
- For ext2 and ext3: the checking is limited to ensuring the resize and copy commands will be ok.
- For fat: the size of the new partition after resizing or copying is restricted by the cluster size. Parted can shrink the cluster size, so you can always shrink your partition. However, if you cant use FAT32 for some reason, you may not be able to grow your partition.
- Parted supports both FAT16 and FAT32. Parted can convert file systems between FAT16 and FAT32, if necessary.
- Reiserfs support is enabled if you install libreiserfs.

Workrave project can assists you in the recovery and prevention of Repetitive Strain Injury (RSI).
The program frequently alerts you to take micro-pauses, rest breaks and restricts you to your daily limit.
Please refer to the feature comparison for a complete list of features, and how the program performs with respect to other programs on the market. The program runs on GNU/Linux and Microsoft Windows.
Main features:
- Distributed: The program runs distributed on one or more PCs. All connected PCs share the same timing information. When the user switches computers, he still will be asked to pause on time.
- Server data collect: All programs in a network report user data detailing break information, mouse and keyboard usage to a central server. The data stored on this server may be analysed to detect user behaviour and, for example, take proactive measures.
- Applet: The program is able to show status information in an applet that is embeddable in the desktop panel or taskbar.
Enhancements:
- Eraldo Girardi translated Workrave into Italian.
- Better support for vertical applets on Unix.
- Tao WEI translated Workrave into simplified Chinese.
- Peter Tuharsky translated Workrave into Slovak.
- Prokopis Prokopidis translated Workrave into Greek.
- The status window used to appear empty, only to be resized and filled with the timers shortly thereafter. Now it appears right away in the proper size.
- The operation mode (normal/quiet/suspended) now persists across Workrave sessions.
- Enver Altin translated Workrave into Turkish.
- Masanobu Yokota translated Workrave into Japanese.
- Ivan Dimov translated Workrave into Bulgarian.
- ORY Mate translated Workrave into Hungarian.
- Fixed KDE sound events (Phuah Yee Keat)
- Fixed Gnome sound events
- Fixed negative mouse usage when date is changed.
- Fixed text color on Gnome themes with dark backgrounds (i.e. high contrast inverse)
- Gnome applets now support transparency.
- The datadir configuration option in workrave.ini can now be a relative path: [general] datadir=.Data This will store all Workrave data in the Data directory below the Workrave root directory. (Note the double backslash)
- Daily limit now properly resets when hibernated.

Darkbot is a very fast and small program written in C language which connects to IRC from an Unix or Windows operating system and automatically "talks" and responds to users questions.
Originally created by Jason Hamilton as an aid for help channels to answer repeated questions from its virtually unlimited database, it has became a very popular talking robot in a generic sense, being used all over IRC networks for different purposes and in 18 languages.
THe dfata can be dynamically added and changed but also can be changed offline, working in its database.
An extensive but easy-to-understand list of commands and features, including some channel operation functions and levels of protection, makes Darkbot a very flexible but somehow powerful and complex robot, with almost human conversations and reactions.
Enhancements:
- Removed an unneeded line in main.c, that was used to "hide" warnings on WIN32, which is a very bad idea.
- Changed check_dbtimers() so it ignores the CVS directory, which contains information for the CVS server. This fixes a situation that seems to have only presented itself in FreeBSD, where it thinks the CVS directory is a timer, and sends out random garble every few seconds.
- configure.ac and source/Makefile.am; very minor updates.
- Fixed randq, which I accidentally broke when adding the
- I switch. This also fixes some problems that turned upon FreeBSD.
- Fixed a warning that came up in permbans.c about mixing types when compiling on OS X. I changed %d on line 198 to %ud.
- configure now checks for clock_t.
- configure now automatically checks for snprintf, and uses a replacement if its not found.
- docs/INSTALL.txt is now INSTALL in the toplevel dir.
- Another thing for automake to stop complaining about.
- The original configure script is now located in the scripts directory, and is called "Setup".
- docs/contributors.txt is now called AUTHORS in the top level of the distribution. Another thing automake complains about. I also worked on the appearance of this file, hopefully it looks a little better now.
- README.txt in the toplevel is now called "README". Automake complains about this file also, if its not found.
- This file is now called ChangeLog, and has been moved to the toplevel distribution dir. The reason for this is that automake complains, if it cant find this file.
- configure now checks for the presence of windows.h, and defines WIN32, if its found. This removes the need to do "make win". Until I add the noconsole option again, you can run darkbot with no console by doing "./darkbot &" in your cygwin shell.
- The configure.ac file is not yet complete, and most of the definitions listed in config.h are not completely implemented into the code yet. If you have problems, please let me know, and these files will become completely implemented as demand is met.
- Included premade Makefiles and configure script.
- Added "make convertdb", which will compile the database conversion utility, which encrypts the passwords in your userlist.db file.
- I added a Makefile.am in the toplevel, and in the source directory. These files are used in conjunction with GNU Automake to produce a Makefile.
- Added Makefile.ams and configure.ac for autoconf/automake.

xbindkeys is a program that allows you to launch shell commands with your keyboard or your mouse under X Window.
xbindkeys links commands to keys or mouse buttons, using a configuration file. Its independant of the window manager and can capture all keyboard keys (ex: Power, Wake...).
usage: [--version|-V] [--defaults|-d] [--file|-f file] [--help|-h] [--display|-X display-name] [--vebose|-v] [--show|-s] [--key|-k] [--multikey|-mk] [--geometry|-g geom]
-V, --version Print version and exit
-d, --defaults Print a default rc file
-f, --file Use an alternative rc file
-h, --help This help!
-X, --display Set X display to use
-v, --verbose More information on xbindkeys when it run
-s, --show Show the actual keybinding
-k, --key Identify one key pressed
-mk, --multikey Identify multi key pressed
-g, --geometry size and position of window open with -k|-mk option
-n, --nodaemon dont start as daemon
Installation
Download the source (See the download section).
Open a text console (for example, xterm).
Change to the directory into which you downloaded the source.
cd source_download_directory
Uncompress the source :
tar xzvf xbindkeys-1.x.x.tar.gz
Change to the new directory (created by tar) :
cd xbindkeys-1.x.x
Compile the program :
make
Install the program (as root if necessary) :
su root
make install
exit
Configure the program :
see the Configuration section.
You can now use xbindkeys by typing :
xbindkeys &
or by loading it automatically when X starts up by adding the preceeding line to the file $HOME/.xsession.
On Mandrake (and maybe Redhat), this method doesnt works.
Instead you can use : Configuration -> Gnome -> Advanced -> Session -> Startup Programs on Mandrake
or Gnome menu -> Settings -> Session -> Session Properties on Redhat.
Enhancements:
- Correction of typos in the man page.
- An emphasis is made on the documentation about the Guile/Scheme configuration file (the preferred way for non-trivial configuration, and far more powerful than the default configuration file).

Benchmark is a Perl module with benchmark running times of Perl code.

SYNOPSIS

use Benchmark qw(:all) ;

timethis ($count, "code");

# Use Perl code in strings...
timethese($count, {
Name1 => ...code1...,
Name2 => ...code2...,
});

# ... or use subroutine references.
timethese($count, {
Name1 => sub { ...code1... },
Name2 => sub { ...code2... },
});

# cmpthese can be used both ways as well
cmpthese($count, {
Name1 => ...code1...,
Name2 => ...code2...,
});

cmpthese($count, {
Name1 => sub { ...code1... },
Name2 => sub { ...code2... },
});

# ...or in two stages
$results = timethese($count,
{
Name1 => sub { ...code1... },
Name2 => sub { ...code2... },
},
none
);
cmpthese( $results ) ;

$t = timeit($count, ...other code...)
print "$count loops of other code took:",timestr($t),"n";

$t = countit($time, ...other code...)
$count = $t->iters ;
print "$count loops of other code took:",timestr($t),"n";

# enable hires wallclock timing if possible
use Benchmark :hireswallclock;

The Benchmark module encapsulates a number of routines to help you figure out how long it takes to execute some code.

timethis - run a chunk of code several times
timethese - run several chunks of code several times
cmpthese - print results of timethese as a comparison chart
timeit - run a chunk of code and see how long it goes
countit - see how many times a chunk of code runs in a given time

DBAHelper project is a collection of scripts to ease the daily maintenance work of Oracle database administrators.
Examples are moving objects between tablespaces, analyzing schemata, and rebuilding invalid indices.
Enhancements:
- Some fixes to the Generate_createDB.sh.
- An RMAN framework has been added to simplify RMAN usage (requires 10g with Recovery Area enabled and properly sized to hold the backups).

B::Deparse is a Perl compiler backend to produce perl code.

SYNOPSIS

perl -MO=Deparse[,-d][,-fFILE][,-p][,-q][,-l] [,-sLETTERS][,-xLEVEL] prog.pl

B::Deparse is a backend module for the Perl compiler that generates perl source code, based on the internal compiled structure that perl itself creates after parsing a program. The output of B::Deparse wont be exactly the same as the original source, since perl doesnt keep track of comments or whitespace, and there isnt a one-to-one correspondence between perls syntactical constructions and their compiled form, but it will often be close. When you use the -p option, the output also includes parentheses even when they are not required by precedence, which can make it easy to see if perl is parsing your expressions the way you intended.

While B::Deparse goes to some lengths to try to figure out what your original program was doing, some parts of the language can still trip it up; it still fails even on some parts of Perls own test suite. If you encounter a failure other than the most common ones described in the BUGS section below, you can help contribute to B::Deparses ongoing development by submitting a bug report with a small example.

OPTIONS

As with all compiler backend options, these must follow directly after the -MO=Deparse, separated by a comma but not any white space.

-d

Output data values (when they appear as constants) using Data::Dumper. Without this option, B::Deparse will use some simple routines of its own for the same purpose. Currently, Data::Dumper is better for some kinds of data (such as complex structures with sharing and self-reference) while the built-in routines are better for others (such as odd floating-point values).

-fFILE

Normally, B::Deparse deparses the main code of a program, and all the subs defined in the same file. To include subs defined in other files, pass the -f option with the filename. You can pass the -f option several times, to include more than one secondary file. (Most of the time you dont want to use it at all.) You can also use this option to include subs which are defined in the scope of a #line directive with two parameters.

-l

Add #line declarations to the output based on the line and file locations of the original code.

-p

Print extra parentheses. Without this option, B::Deparse includes parentheses in its output only when they are needed, based on the structure of your program. With -p, it uses parentheses (almost) whenever they would be legal. This can be useful if you are used to LISP, or if you want to see how perl parses your input. If you say

if ($var & 0x7f == 65) {print "Gimme an A!"}
print ($which ? $a : $b), "n";
$name = $ENV{USER} or "Bob";
B::Deparse,-p will print
if (($var & 0)) {
print(Gimme an A!)
};
(print(($which ? $a : $b)), ???);
(($name = $ENV{USER}) or ???)

which probably isnt what you intended (the ??? is a sign that perl optimized away a constant value).

-P

Disable prototype checking. With this option, all function calls are deparsed as if no prototype was defined for them. In other words,

perl -MO=Deparse,-P -e sub foo (@) { 1 } foo @x

will print

sub foo (@) {
1;
}
&foo(@x);

making clear how the parameters are actually passed to foo.

-q

Expand double-quoted strings into the corresponding combinations of concatenation, uc, ucfirst, lc, lcfirst, quotemeta, and join. For instance, print

print "Hello, $world, @ladies, u$gentlemenE, uL$me!";

as

print Hello, . $world . , . join($", @ladies) . ,
. ucfirst($gentlemen) . , . ucfirst(lc $me . !);

Note that the expanded form represents the way perl handles such constructions internally -- this option actually turns off the reverse translation that B::Deparse usually does. On the other hand, note that $x = "$y" is not the same as $x = $y: the former makes the value of $y into a string before doing the assignment.

-sLETTERS

Tweak the style of B::Deparses output. The letters should follow directly after the s, with no space or punctuation. The following options are available:

C

Cuddle elsif, else, and continue blocks. For example, print

if (...) {
...
} else {
...
}
instead of
if (...) {
...
}
else {
...
}

The default is not to cuddle.

iNUMBER

Indent lines by multiples of NUMBER columns. The default is 4 columns.

T

Use tabs for each 8 columns of indent. The default is to use only spaces. For instance, if the style options are -si4T, a line thats indented 3 times will be preceded by one tab and four spaces; if the options were -si8T, the same line would be preceded by three tabs.

vSTRING.

Print STRING for the value of a constant that cant be determined because it was optimized away (mnemonic: this happens when a constant is used in void context). The end of the string is marked by a period. The string should be a valid perl expression, generally a constant. Note that unless its a number, it probably needs to be quoted, and on a command line quotes need to be protected from the shell. Some conventional values include 0, 1, 42, , foo, and Useless use of constant omitted (which may need to be -sv"Useless use of constant omitted." or something similar depending on your shell). The default is ???. If youre using B::Deparse on a module or other file thats required, you shouldnt use a value that evaluates to false, since the customary true constant at the end of a module will be in void context when the file is compiled as a main program.

-xLEVEL

Expand conventional syntax constructions into equivalent ones that expose their internal operation. LEVEL should be a digit, with higher values meaning more expansion. As with -q, this actually involves turning off special cases in B::Deparses normal operations.

If LEVEL is at least 3, for loops will be translated into equivalent while loops with continue blocks; for instance

for ($i = 0; $i < 10; ++$i) {
print $i;
}
turns into
$i = 0;
while ($i < 10) {
print $i;
} continue {
++$i
}

Note that in a few cases this translation cant be perfectly carried back into the source code -- if the loops initializer declares a my variable, for instance, it wont have the correct scope outside of the loop.

If LEVEL is at least 5, use declarations will be translated into BEGIN blocks containing calls to require and import; for instance,

use strict refs;
turns into
sub BEGIN {
require strict;
do {
strict->import(refs)
};
}
If LEVEL is at least 7, if statements will be translated into equivalent expressions using &&, ?: and do {}; for instance
print hi if $nice;
if ($nice) {
print hi;
}
if ($nice) {
print hi;
} else {
print bye;
}
turns into
$nice and print hi;
$nice and do { print hi };
$nice ? do { print hi } : do { print bye };

Long sequences of elsifs will turn into nested ternary operators, which B::Deparse doesnt know how to indent nicely.