Free 2.3.0 wow patch software for linux

The Exim DSN patch adds delivery status notification support to Exim 4.xx.

DSN Support for Exim. This patch allows Exim 4.xx to support the sending of email Delivery Status Notifications.

KPowersave Icon Patch is intended for KPowersave 0.6.2

This patch changes the way of displaying power state for KPowersave. Using this patch you can better theme KPowersave, by using a series of pixmaps.

Installation instructions:

>>> Patch the sources

1. Copy the patch file in the parent folder of KPowersave sources.
2. Cd into KPowersave
3. issue: patch -Np1 -i ../kpowersave-icon.patch

>>> Compile the sources

>>> Copy the icons

After instalation, you wont get any icons for displaying battery state.
You have to copy them to your theme folder.
Copy the iconset in the THEME_FOLDER/22x22/actions/

You can use this theme for start:

http://www.kde-look.org/content/show.php?content=28287

rssh is a restricted shell for use with OpenSSH, allowing only scp and/or sftp. rssh project now also includes support for rdist, rsync, and cvs.
For example, if you have a server which you only want to allow users to copy files off of via scp, without providing shell access, you can use rssh to do that.
hough rssh is written to work with OpenSSH, it will probably work with other implementations of SSH. Also, rssh is written and tested on Linux systems, but should compile cleanly and work on any POSIX.2-compliant system. It is verified to work on the following platforms:
A wide variety of Linux distributions, on IA32 and IA64 hardware
Compaq Tru64 Unix
Solaris 2.x - 8 (under certain conditions -- see the security link)
AIX 5.1
HP/UX 11.00 (PA-RISC)
HP/UX 11.22 (IA64)
Irix 6.5
Currently, it does not work on (at least most of) the *BSDs, nor on OS X. They lack the wordexp() function, which rssh uses for command line argument expansion. Until they have such a function (which is defined by POSIX.2), or until I get bored enough to write a replacement, rssh will not work with the BSDs out of the box.
Update, 7 Jun 2003: Jacques A. Vidrine reports that FreeBSD 5.0 now has the wordexp() function, and rssh compiles cleanly on it, though he has not tested it. I still do not have any confirmation that it will work on FreeBSD 5, but it seems like a safe bet. I have received reports that other operating environments are also adding support for wordexp(), and rssh should work on all of those platforms, too.
If youre on a BSD system without the wordexp() function, you could work around this by obtaining a copy of the wordexp() functions code from, say, glibc2, and creating your own wordexp.h header. Compile wordexp.c manually, and link it against the other .o files. I have no intention of doing any work to facilitate that, though, so youre on your own.
If you have success using rssh with some other implementation of SSH, or using it on other platforms, feel free to send e-mail to the rssh mailing list to let me know. If you have problems compiling or installing rssh on your favorite platform, please send me the complete configure output, and any compilation errors generated.
Enhancements:
- This release fixes a design flaw in rssh_chroot_helper that allowed local users with full shell access to gain root privileges.

PyDNS project provides a module for performing DNS queries from python applications.

Im making this release because there hasnt been a release in a heck of a long time, and it probably deserves one. Id also like to do a substantial refactor of some of the guts of the code, and this is likely to break any code that uses the existing interface. So this will be a release for people who are using the existing API...

There are several known bugs/unfinished bits

- processing of AXFR results is not done yet.
- doesnt do IPv6 DNS requests (type AAAA)
- docs, aside from this file
- all sorts of other stuff that Ive probably forgotten.
- MacOS support for discovering nameservers
- the API that I evolved some time ago is pretty ugly. Im going to re-do it, designed this time.

KDELirc Improved (patch) adds some different new features to improve kdelirc usability. Above all i added On Screen Display, using Konversation and Amarok codebase. When some key is pressed on the remote, its shown through OSD on your desktop, and mode changing is advertised too.
I also added an option to allow mode changing with one key only, instead of binding one key for each mode. A new DCOP method now allows to suspend and resume key binding for the remote (dcop irkick IRKick setEnabled true/false).
Enhancements:
- Removed Konversation OSD, using Amarok one instead (improved, with images and translucency support).
- Now showing icon for mode change, for better visual recognition.
- Also showing a little icon for the keypress, so indicating what mode is in use.
- Added an option to select a different font for mode change and key press.
- Added dcop call to show osd text through dcop.

iBATIS project provides a very simple and flexible means of moving data between your Java and .NET objects and a relationaldatabase. Use the full power of real SQL without a single line of JDBC or ADO.NET code!

The Data Mapper framework (a.k.a. SQL Maps) will help to significantly reduce the amount of Java and .NET code that is normally neededto access a relational database. This framework maps classes to SQL statements using a very simple XML descriptor. Simplicity is the biggest advantage of iBATIS over other frameworks and object relational mapping tools.

To use iBATIS you need only be familiar with your own application domain objects (basic JavaBeans or .NET classes), XML, and SQL. There is very little else to learn. There is no complex scheme required to join tables or execute complex queries. Using iBATIS you have the full power of real SQL at your fingertips. The iBATIS Data Mapper framework can map nearly any database to any object model and is very tolerant of legacy designs, or even bad designs. This is all achieved without special database tables, peer objects or code generation.

iBATIS Data Access Objects

iBATIS Data Access Objects is an abstraction layer that hides the details of your persistence solution and provides a common API to therest of your application.
When developing robust Java and .NET applications, it is often a good idea to isolate the specifics of your persistence implementationbehind a common API. Data Access Objects allow you to create simple components that provide access to your data withoutrevealing the specifics of the implementation to the rest of your application.

Using DAOs you can allow your application tobe dynamically configured to use different persistence mechanisms. If you have a complex application with a number of differentdatabases and persistence approaches involved, DAOs can help you create a consistent API for the rest of your application.

For Java users, the Data Access Objects framework is bundled as part of the iBATIS Database Layer, which includes the SQL Maps Framework. Although packaged together, the DAO Framework is completely independent and can be used without SQL Maps. .NET users can download the DataAccess framework seperately from the DataMapper framework.