Free hacks software for linux

Enhancements

• Spread out comet origination
• Sync kcometen4.desktop translations with KDE 4.2.4
• Remove resize hack; bug fixed in KDE 4.2.3
• Clean up how the config changes interact with the preview
• Small fixes to CMakeLists.txt files

Requirements:

• KDE 4.x

ProFTPD developed out of the desire to have a secure and configurable FTP server, and out of a real admiration for the Apache web server.
There are currently a very limited number of FTP servers running on Unix (or Unix-like) hosts. The most commonly used server is wu-ftpd. While wu-ftpd provides excellent performance and is generally a good product, it lacks numerous features found in newer Win32 FTP servers and has a poor security history.
Many people, including the developers who work on ProFTPD, have spent a great deal of time fixing bugs and hacking features into wu-ftpd. Unfortunately, it quickly became clear that a complete redesign was necessary in order to implement the configurability and features desired.
ProFTPD is not a hack based on any other server, its an independent source tree from the ground up. A number of well known and high traffic sites use ProFTPD.

DragonFly is an Linux operating system and environment designed to be the logical continuation of the FreeBSD-4.x OS series. These operating systems belong in the same class as Linux in that they are based on UNIX ideals and APIs. DragonFly is a fork in the path, so to speak, giving the BSD base an opportunity to grow in an entirely new direction from the one taken in the FreeBSD-5 series.

It is our belief that the correct choice of features and algorithms can yield the potential for excellent scalability, robustness, and debuggability in a number of broad system categories. Not just for SMP or NUMA, but for everything from a single-node UP system to a massively clustered system. It is our belief that a fairly simple but wide-ranging set of goals will lay the groundwork for future growth.

The existing BSD cores, including FreeBSD-5, are still primarily based on models which could at best be called strained as they are applied to modern systems. The true innovation has given way to basically just laying on hacks to add features, such as encrypted disks and security layering that in a better environment could be developed at far less cost and with far greater flexibility.

We also believe that it is important to provide API solutions which allow reasonable backwards and forwards version compatibility, at least between userland and the kernel, in a mix-and-match environment. If one considers the situation from the ultimate in clustering... secure anonymous system clustering over the internet, the necessity of having properly specified APIs becomes apparent.

Finally, we believe that a fully integrated and feature-full upgrade mechanism should exist to allow end users and system operators of all walks of life to easily maintain their systems. Debian Linux has shown us the way, but it is possible to do better.

DragonFly is going to be a multi-year project at the very least. Achieving our goal set will require a great deal of groundwork just to reposition existing mechanisms to fit the new models. The goals link will take you to a more detailed description of what we hope to accomplish.

1.2.0 is our second major DragonFly release and the first one which we have created a separate CVS branch for. DragonFlys policy is to only commit bug fixes to release branches.

This release represents a significant milestone in our efforts to improve the kernel infrastructure. DragonFly is still running under the Big Giant Lock, but this will probably be the last release where that is the case.

The greatest progress has been made in the network subsystem. The TCP stack is now almost fully threaded (and will likely be the first subsystem we remove the BGL from in coming months). The TCP stack now fully supports the SACK protocol and a large number of bug and performance fixes have gone in, especially in regard to GigE performance over LANs.

The namecache has been completely rewritten and is now considered to be production-ready with this release. The rewrite will greatly simplify future filesystem work and is a necessary precursor for our ultimate goal of creating a clusterable OS.

This will be last release that uses GCC 2.95.x as the default compiler. Both GCC 3.4.x and GCC 2.95.x are supported in this release through the use of the CCVER environment variable (gcc2 or gcc34). GCC 2.95.x is to be retired soon due to its lack of TLS support. The current development branch will soon start depending heavily on TLS support and __thread both within the kernel and in libc and other libraries. This release fully supports TLS segments for programs compiled with gcc-3.4.x.

It goes without saying that this release is far more stable then our 1.0A release. A huge number of bug fixes, performance improvements, and design changes have been made since the 1.0A release.

goblinhackis a rogue-like game with ASCII graphics, OpenGL, and smooth scrolling.
Goblins hoard in their foul, dark hole, Plotting and digging and hating all things, Theyll gnash on your bones and eat you whole, And deliver your soul to the Goblin King.
Enhancements:
- This release adds animated black, white, and amethyst dragons, jelly molds, evil blobs, knee gnashers, fractal lakes, fate points, acid weapons, fire/cold/acid proof armour, and many bugfixes.

GNOME Power Manager gets all information from HAL using information from org.freedesktop.Hal. GNOME Power Manager does not do independent probing for data, it relies on HAL, in this way it can stay very lightweight and uncomplicated. GNOME Power Manager goal is to be architecture neutral and free of polling and other hacks.
Power management in Linux sucks. Depending if you are running a PPC or i386 PC the different power management facilities are vastly different. To get your machine to suspend on lid press is already possible, but is difficult to know what config files to modify.
To get your LCD screen brightness set to 50% when you remove the AC Adapter of your laptop is probably possible with a clever little Perl script, but is not something that comes ready configured on a standard Linux distro.
Any of these things need the user to become the super-user to do the action. This needs to change before Linux is accepted as a contender for the corporate desktop.
Main features:
- Laptop batteries
- AC Adapters
- APC UPSs
- SynCE PDAs
- Logitech Wireless Mice
- Logitech Wireless Keyboards
GNOME Power Manager owns the session D-BUS service net.sf.GnomePower and runs a session daemon (i.e. once per logged in user) and optionally displays battery status and low battery notifications.
The session daemon is very resource friendly. Other than the initial coldplug, it uses internal caching for all the power devices, so no additional lookups are needed for each update event. It will only update the displayed icon on a powerState change, but will update the tooltip on every percentage change. It should use *very little* CPU and memory.

XScreensaver program waits until the keyboard and mouse have been idle for a period, and then runs a graphics demo chosen at random. XScreenSaver turns off as soon as there is any mouse or keyboard activity.
It can also lock the screen (immediately, after a longer idle period, or on demand.) xscreensaver consists of two parts: xscreensaver itself (the ``driver or ``daemon), which detects idleness and does locking; and the many graphics demos that are launched by xscreensaver.
Any X program that can draw on the root window can be used with xscreensaver, regardless of how that program is written, or what language it is written in, or what libraries it uses. The xscreensaver daemon takes care of detecting when the user is idle, locking, and checking passwords and all the other book-keeping; all the other programs need to do is draw.
The benefit that xscreensaver has over the combination of the xlock and xautolock programs is the ease with which new graphics hacks can be installed. You dont need to recompile (or even re-run) the xscreensaver program to add a new display mode, you just change a config file.
Enhancements:
- New cwaves, glcells, m6502, and voronoi hacks were added.
- Updates were made to bsod and webcollage.
- A possible crash with PAM USB dongle authentication was fixed.

CGI::Kwiki::New is the default new wiki generator for CGI::Kwiki.

A Wiki is a website that allows its users to add pages, and edit any existing pages. It is one of the most popular forms of web collaboration. If you are new to wiki, visit http://c2.com/cgi/wiki?WelcomeVisitors which is possibly the oldest wiki, and has lots of information about how wikis work.

There are dozens of wiki implementations in the world, and many of those are written in Perl. As is common with many Perl hacks, they are rarely modular, and almost never released on CPAN. One major exception is CGI::Wiki. This is a wiki framework that is extensible and is actively maintained.

Another exception is this module, CGI::Kwiki. CGI::Kwiki focuses on simplicity and extensibility. You can create a new kwiki website with a single command. The module has no prerequisite modules, except the ones that ship with Perl. It doesnt require a database backend, although it could be made to use one. The default kwiki behaviour is fairly full featured, and includes support for html tables. Any behaviour of the kwiki can be customized, without much trouble.

SPECIAL FEATURES

CGI::Kwiki will come with some fancy addons not found in most wiki implementations. This comes with the promise that they will not interfere with the sheer simplicity of the default kwiki interface.

Check http://http://www.kwiki.org/index.cgi?KwikiFeatures from time to time to see what hot features have been added.

Kwiki Slide Show

You can create an entire PowerPoint-like slideshow, in a single kwiki page. There is Javascript magic for advancing slides, etc. See the sample page KwikiSlideShow.

EXTENDING

CGI::Kwiki is completely Object Oriented. You can easily override every last behaviour by subclassing one of its class modules and overriding one or more methods. This is generally accomplished in just a few lines of Perl.

The best way to describe this is with an example. Start with the config file. The default config file is called "config.yaml". It contains a set of lines like this:

config_class: CGI::Kwiki::Config
driver_class: CGI::Kwiki::Driver
cgi_class: CGI::Kwiki::CGI
cookie_class: CGI::Kwiki::Cookie
database_class: CGI::Kwiki::Database
metadata_class: CGI::Kwiki::Metadata
display_class: CGI::Kwiki::Display
edit_class: CGI::Kwiki::Edit
formatter_class: CGI::Kwiki::Formatter
template_class: CGI::Kwiki::Template
search_class: CGI::Kwiki::Search
changes_class: CGI::Kwiki::Changes
prefs_class: CGI::Kwiki::Prefs
pages_class: CGI::Kwiki::Pages
slides_class: CGI::Kwiki::Slides
javascript_class: CGI::Kwiki::Javascript
style_class: CGI::Kwiki::Style
scripts_class: CGI::Kwiki::Scripts

This is a list of all the classes that make up the kwiki. You can change anyone of them to be a class of your own.

Lets say that you wanted to change the BOLD format indicator from "*bold*" to bold. You just need to override the "bold()" method of the Formatter class. Start by changing "config.yaml".

formatter_class: MyKwikiFormatter

Then write a module called "MyKwikiFormatter.pm". You can put this module right in your kwiki installation directory if you want. The module might look like this:

package MyKwikiFormatter;
use base CGI::Kwiki::Formatter;

sub bold {
my ($self, $text) = @_;
$text =~ s!(.*?)!$1!g;
return $text;
}

1;

Not too hard, eh? You can change all aspects of CGI::Kwiki like this, from the database storage to the search engine, to the main driver code. If you come up with a set of classes that you want to share with the world, just package them up as a distribution and put them on CPAN.

By the way, you can even change the configuration file format from the YAML default. If you wanted to use say, XML, just call the file "config.xml" and write a module called "CGI::Kwiki::Config_xml".

K5expire is a tool to complement a Kerberos/LDAP server combination.
It checks all kerberos principals per user in LDAP for password and/or account expiration and sends E-mails to the owner if they will expire in a preconfigured amount of time.
It started as a hack to emulate the behavior of expiration found in pam_unix and Windows, but I believe this method to be less intrusive because it does not delay the login process.
Enhancements:
- Support for XMLSensor output was added.