Free forever young alphaville software for linux

Magnificent Gunbright is an abstract shooter; destroy the black ball. An Abstract Shooter Developed For Ludum Dare in 48 Hours.

You are the flashy white blob at the bottom, with the clump of other white blobs following you around.

You have the ability to fire the blobs from your cloud at the flashy blob surrounded by a cloud of black blobs at the top of the screen.

If a black blob and white blob collide, both are destroyed. The object is to hit the evil flashy blob at the top of the screen to destroy it.

Falling from the top of the screen like rain is a steady supply of more blobs. If one of the blobs in your cloud touches a white blob that fell from the sky, even while shooting, the blob joins your cluster.

Falling from the bottom of the screen is black blobs, that your enemy can use to bulk himself up, as well. Blob rain does no damage to either party; you can tell that its rain and not bullets because rain travels away from you.

Use the arrow keys to move, and the space bar to shoot.

Once youve destroyed one evil black blob, you will face another, more powerful one! And so on forever until you eventually die.

Destroy the evil black blobs and save the League of Confederated Planets!

My Classifieds is a web-based implementation of online classifieds, similar to other classifieds or auction sites.
It displays all aspects of the classifieds and creates all of the files for you.
Admin just needs to specify the categories, colors, template, and a few other site-specific variables and preferences.
This is done through an intuitive manage script. The script supports email and deletion/modification of ads by users, as well as searching ads, and auto-delete after an admin-specified number of days.
The admin can also delete or edit ads, delete or ban users, and change users passwords.
My Classifieds also has an intuitive language module that is easy to edit.
Already supported are English, Spanish, Puerto Rican Spanish, Norwegian, Portuguese, Danish, and Dutch. Also available: MySQL version.
Main features:
- Post an unlimited number of ads.
- Admin can allow or disallow uploading of pictures and linking to pictures.
- Admin can specify how long an ad can remain before being automatically deleted, or specify forever.
- Admin can specify categories for the ads.
- Admin can delete users, ban users, and change users passwords.
- Admin can delete and edit ads.
- Admin can choose from one of our language modules, or create his own language module.
- Specify your own colors.
- Use your own template

Layer-7 Packet Classifier for Linux is a classifier for Linuxs Netfilter that identifies packets based on application layer data. It can classify packets as Kazaa, HTTP, Jabber, Citrix, Bittorrent, FTP, Gnucleus, eDonkey2000, etc., regardless of port. It complements existing classifiers that match on IP address, port numbers and so on.
Our intent is for l7-filter to be used in conjunction with Linux QoS to do bandwith arbitration ("packet shaping") or traffic accounting.
Main features:
- Patches for Linux 2.4 and 2.6
- Support for TCP, UDP and ICMP over IPv4
- Uses Netfilters connection tracking of FTP, IRC, etc
- Examines data across multiple packets
- Number of packets examined tunable on the fly through /proc
- Number of bytes examined tunable at module load time
- Distinguishes between new connections (those still being tested) and old unidentified connections
- Gives access to both Netfilter and QoS (rate limiting) features
- With the Netfilter "helper" match, you can distinguish between parent and child connections (e.g. ftp command/data)
Enhancements:
- Added man page.
- Added ./configure to check for libraries.
- Made patterns directory user selectable.
- Counts all packets now, not just those with application layer data. I think this is better because it avoids holding connections forever if they keep sending empty packets. On the other hand, now connections can evade l7-filter by sending a bunch of empty packets at the beginning. Perhaps a more complex approach may be necessary at some point.
- Made number of packets user selectable. Defaults to 10 (not 8).
- Organized pattern file parsing code better.
- Made buffer length user selectable. Made buffer dynamically allocated. It is now only kept when needed instead of for the whole life of the connection. Buffer is dumped to the screen (if in verbose mode) when (1) too many packets have passed without a match or (2) connection is closed without a match.
- Now checks for ip_conntrack_netlink module.
- Various tweaks.
Enhancements:
- Using only part of the Netfilter packet mark, defined by a bitmask, is now allowed.
- The configure script was improved.

IVJLogger project is a small library of classes and functions written in Java designed to assist you with your logging needs. "Why another logger?" you may ask. Well, the main purpose of it is keeping it simple.
Simplicity means less bugs, more extensibility, better performance, and happier users. Many loggers Ive seen out therer take forever to set up, I am not even talking about all the initialization code, and all the clean-up you have to do just to get them to log one line of code.
With IVJLogger you dont need any external files, no clean-up, and initialization code is as simple as instantiating an object.
Main features:
- Simplicity
- High performance - thanks to very efficient thread pool
- Less coding - one line to initialize, one line to log, no clean-up
- No external objects used - include the source with your project and youre ready to go
- Most recent JVM friendly - created and tested on Java 1.4.2 SE
- Cross-platform - well, Java kind of took care of that :)
- Thread-safe - multiple threads may use the same logger to log data simultaneously.

Acme::OneHundredNotOut is a raise of the bat, a tip of the hat.

I have just released my 100th module to CPAN, the first time that anyone has reached that target. As some of you may know, I am getting ready to go back to college and reinvent myself from being a programmer into being a missionary. I dont forsee that many more Perl modules coming out of this.

Of course, this doesnt mean that Im going to abjure usage of Perl forever; any time theres a computer and something I need automated, out will come the Swiss Army Chainsaw and the job will get done. In fact, we recently needed to manipulate some text from a mission handbook to translate it into Japanese, and Perl was there handling and collating all that.

But 100 modules is a convenient place to stop and take stock, and I hope that those of you who have benefitted from my modules, programs or writing about Perl will forgive me a certain spot of self-indulgence as I look back over my CPAN career, especially since I feel that the diversity of modules that Ive produced is a good indication of the diversity of what can be done with Perl.

Lets begin, then, with some humble beginnings, and then catch up on recent history.
The Embarrassing Past

Contrary to popular belief, I was not always a CPAN author. I started writing modules in 1998, immediately after reading the first edition of the Perl Cookbook - yes, you can blame Nat and Tom for all this. The first module that I released was Tie::DiscoveryHash, since Id just learnt about tied hashes. As with many of my modules, it was an integral part of another software project which I actually never finished, and now cant find.

The first module that I ever wrote (but, by a curious quirk of fate, precisely the fiftieth module I released) was called String::Tokeniser, which is still a reasonably handy way of getting an iterator over tokenising a string. (Someone recently released String::Tokenizer, which makes me laugh.) This too was for an abortive project, webperl, an application of Don Knuths WEB system of structured documentation to Perl. However, given the code quality of these two modules, its perhaps just as well that the projects never saw the light of day.

There are a few other modules Id rather like to forget, too. Devel::Pointer was a sick joke that went badly wrong - it allowed people to use pointers in Perl. Some people failed to notice that referring to memory locations directly in an extremely high-level language was a dangerous and silly thing to do, and actually used the damned thing, and I started getting requests for support for it. Then at some point in 2001, when I should really have known better, I developed an interest in Microsofts .NET and the C# language, which I still think is pretty neat; but I decided it might be a good idea to translate the Mono projects tokenizer and parser into Perl, ending up with C::Sharp. I never got around to doing the parser part, or indeed anything else with it, and so it died a lonely death in a dark corner of CPAN. GTK::HandyClist was my foray into programming graphical applications, which started and ended there.

Bundle::SDK::SIMON was actually the slides from a talk on my top ten favourite CPAN modules - except that this changes so quickly over time, it doesnt really make much sense any more.

Finally, Array::FileReader was an attempt to optimize a file access process. Unfortunately, my "optimization" ended up introducing more overheads than the naive solution. It all goes to show. Since then, Mark-Jason Dominus, another huge influence in the development of my CPAN career, has written Tie::File, which not only has a better name but is actually efficient too.

The Internals Phase

1999-2000 were disastrous years for me personally but magnificent years Perl-sonally. Stuck in a boring job and a tiny flat in the middle of Tokyo, I had plenty of time to get stuck into more Perl development. I felt that getting involved with perl5-porters would be a good way of gettting to know more about Perl, and so I needed a hobby horse - an issue of Perls development that I cared about. Since I was in Japan and working a lot with non-Latin text, Unicode support seemed a good thing to work on, and so Unicode::Decompose appeared, while I fixed up a substantial part of the post-5.6 core Unicode support.

Id recommend this way to anyone who wants to get more involved in the Perl community, although I was very lucky in terms of who else happened to be around at the time: Gurusamy Sarathy was extremely gracious in helping me turn my fledgling C code into something fit for the Perl core, and he also helped me understand the perl5-porters etiquette (yes, there was some at the time) and what makes a good patch, while Jarkko Hietaniemi was always good for suggestions of interesting things for keen people to work on. Seriously, get involved. If I can do it, anyone can.
Anyway, this fixation with understanding the Perl 5 internals, and especially the Perl 5 compiler, (due to yet another of my Perl influences, the great Malcolm Beattie) led to quite a torrent of modules, from ByteCache, an implementation of just-in-time compilation for Perl modules, through B::Flags and B::Tree to help visualising the Perl op tree, to uninit, B::Generate, optimizer and B::Utils for modifying it.

Perl About The House

Now we abandon chronological order somewhat and take a look at the various areas in which Ive used Perl. One of these areas has been the automation of everyday life: checking my bank balance with Finance::Bank::LloydsTSB (the first Perl module to interface to personal internet banking, no less) and my phone bill with a release of Tony Bowdens Data::BT::PhoneBill.

Finance::Bank::LloydsTSB was meant to go with Finance::QIF, my Quicken file parser, to produce another now-abandoned idea, a Perl finances manager. It seemed that Im only capable of producing modules, not full standalone applications - or at least, it seemed that way until I produced Bryar, my blogging software, based on the concepts from Rael Dornfests blosxom and beginning my adventures with Andy Wardleys Template Toolkit. Bryar also tuned me in to the Model-View-Controller framework idea, of which more later.

Another project I briefly played with was a personal robot, using the Sphinx/Festival speech handling and recognition modules from Cepstral and Kevin Lenzo. I didnt have X10, so I couldnt shout "lights" into the air in a wonderfully scifi way, but I could shout "mail" and have a summary of my inbox read to me, "news" to get the latest BBC news headlines, and "time" to hear the time. Of course, getting computers to tell the time nicely takes a little bit of work. I dont like "Its eleven oh-three pee em", since thats not what someone would say if you asked them the time. I wanted my robot to say "Its just after eleven", and thats what Time::Human does. Shame about the localisation.

Network FIFO project is a network object that provides data transfering tunnel across network in first in/first out manner.

Simply put,

fifo server file is: monotech_fifo.pl
This script require Net::Server::NonBlocking at least 4.1(you can grab from CPAN)

% perl monotech_fifo.pl < address > < port >

and itll show up like this:

[root@WongWai monotech_fifo]# perl monotech_fifo.pl 192.168.3.52 12000
Listen on 192.168.3.52:20005
Listen on 192.168.3.52:12000

12000 is the port in which the fifo resides.
20005 is the port in which backoffice management resides.

--------------------------------------------------

port 20005 in which the management control resides can be accessed by "admin.pl"

% perl admin.pl < address >

for example

perl admin.pl 192.168.3.52

itll show something like this:

message>

where you can type some commands and press enter

the commands are:

message>readers
message>flush

(flush is the command that read all socket buffer of the admin client socket)

to show all reader in the fifo, it is very useful when some reader is connection disconnected by his ISP or readers machine hangs, the fifo will hold his connection forever (It is because the monotech_fifo.pl doesnt set SO_KEEPALIVE and TCP_KEEPALIVE which will be fixed in the future)

and

message>kill_reader[tab]< fifo name >

to kill any connection of < fifo name >

This package is heavily used by my company, so it is likely reliable.