Free started to software for linux

RemoteBuddy project allows people to help their friends fix their computer issues by remote access.

RemoteBuddy is easy to use and works with almost any firewall configuration.

Just follow the simple steps to below to get started.

mroovca stats is a Web site statistics generator with various functions and tables. mroovca stats is simple, configurable, and provides an administrative interface.
It can measure statistics concerning the client browser, geolocalization, connection type, and referers. It can also recognize Polish towns.
In 2001 ive started to write my own version of web-site(s) statisics, since that time i had to change my name, changed from flat-file to datadase and finally rewrite whole code to be more flexible.
To work with databases it uses "dbx" functions module from PHP. At this moment its tested only with MySQL and prepared to work with this db engine. But in close future i will provide installer, updater and support for other database engines.
But its not end. im working for more enchancements and statistics including tables, charts, maps, etc.
Just download, extract from archive, configure and use it!!
Main features:
- easy instller/updater (for versions >=0.4.4)
- language support - english and polish at this time
- prepared for work with more than one websites/accounts
- root panel for adding and removing accounts
- admin panel for accounts
- all accounts have their own password
- access for viewing stats for all or on passowrd
- showing stats with or without reloads
- timezone correction
- excluded hosts or (sub)domains

Streamripper started as a way to separate tracks via Shoutcasts title-streaming feature. This has now been expanded into a much more generic feature, where part of the program only tries to "hint" at where one track starts and another ends, thus allowing a mp3 decoding engine to scan for a silent mark, which is used to find an exact track separation.
Streamripper was started sometime back in early 2000. Streamripper started as a way to separate tracks via Shoutcasts title-streaming feature. This has now been expanded into a much more generic feature, where part of the program only tries to "hint" at where one track starts and another ends, thus allowing a mp3 decoding engine to scan for a silent mark, which is used to find an exact track separation.
This is not surprising because portability was a constant consideration during development.Streamripper is now part of the FreeBSD standard distribution, mentioned in the Linux MP3 HOWTO, known to compile on many platforms such as Linux, Windows, FreeBSD, BeOS, OS/2.
With the emergence of file sharing protocols such as Napster, Gnutella, and now Mojonation and Freenet, the average Internet user can download nearly any mp3 he wants in a matter of no time, but many times people dont know what they want. Streamripper allows you to download an entire station of music. Many of these mp3 radio stations only play certain genres, so you can now download an entire collection of goa/trance music, an entire collection of jazz, punk rock, whatever you want.
Enhancements:
- Fix bug where external program wasnt being killed when reconnecting.

[COPYRGHT=1]

You may recall that in 1997, Netscape embarked on a project to rewrite Navigator/Communicator in Java. This project (code named "Xena," but sometimes referred to by the press as "Javagator") was cancelled before completion.

Grendel is the mail-news portion of the Xena project written in Java. Its goal is to be a true cross-platform application with a feature set that satisfies the poweruser.

Grendel was originally developed as a part of the "Javagator" project at Netscape. This project was cancelled before completion after 3 years of development. After the source for Grendel was released other people started to work toward completing it for about another 2 years. The original release was therefore incomplete.

The build system is currently being redone to use Apache Ant instead of Makefiles. The easiest way to compile Grendel in its current state is to grab a copy of JCreator and create a Grendel project in the directory and compile it. A lot of test files are currently being separated out into different directories so if a certain file isnt compiling nicely, its probably because its a broken test file that can be deleted from your tree safely.

Were also in the process of moving Grendel from its own XML format to a Mozilla-friendly XUL format using the MozCreator Java XUL Parser API. Wed also like to contain all resources into one easy to manage resource folder instead of dumping them all over the source tree.

Why have Grendel when we have Thunderbird?

A primary goal with Grendel is restoring the libraries contained in the email client to full state as well as providing a working email program. Having a Java port of many of the Mozilla libraries from C++ to Java would be very valuable to many projects. The code has a lot of potential and having the Mozilla platform available for Java programmers can be a invaluable resource for Java programmers wishing to utilize email features easily. Its Java design eliminates some of the problems of a C++ design like Thunderbird. For example, Java has garbage collection and no restriction of language features in order to maintain cross-platform compatibility (like with C++ and lack of feature usage like templates for compatibility).

The Prex project is an open source initiative to provide a portable real-time operating system for embedded systems.
This project originally started to make a royalty-free OS for mobile phones and PDA in order to spread open source movement to such proprietary OS field. And now, the project target has been shifted to the wider area of real-time and embedded systems.
Prex is designed specifically for small memory footprint platforms. It is written in C language based on traditional micro-kernel architecture. The Prex kernel provides only fundamental features for task, thread, memory, ipc, exception, and synchronization.
The other basic OS functions, process, file system, application loading, and networking, are provided by the user mode servers. In addition, Prex provides a POSIX emulation layer in order to reuse the existing applications.
Prex is an open source royalty-free OS for mobile phones and PDA.
This design allows system to perform both of the native real-time task and the generic *NIX process simultaneously without degrading the real-time performance. Furthermore, it helps the platform designer to construct OS by choosing suitable server tasks for their target requisition.
Prex is royalty-free software released under BSD License
Main features:
- Task and thread control: preemptive priority scheduling with 256 priority levels
- Memory management: virtual address mapping, shared memory, memory protection, with MMU
- IPC: synchronous message passing among threads, object name space in kernel
- Exception: framework for POSIX signal emulation
- Synchronization: semaphores, condition variables, and mutexes with priority inheritance
- Timers: sleep timers, alarm timers
- Interrupt: nested interrupt service routines, and prioritized interrupt service threads
- Device I/O: minimum synchronous I/O interface
- Real-time: low interrupt latency, high resolution timers, periodic timers, and scheduling quantum control
- Cross platform portability: well defined architecture dependent layer and driver-kernel interface
- Modular design: OS servers and BSP module separated from kernel
- Small memory footprint: kernel size < 25k bytes
- Low power consumption: control of processor idle state, support of DVS (Dynamic Voltage Scaling)
- Disk-less: on-core kernel, no memory page swapping
- Instantly available: minimal OS boot time, system suspend/resume, kernel warm restart
- File systems: VFS framework, RAM/FAT/Flash file systems optimized for embedded systems
- Networking: TCP/IP stack, BSD socket interface
- POSIX emulation: signal, process, file I/O, real-time extensions, pthread, etc
- Debug: event logging, GDB remote debug
Enhancements:
- A file system server was added. arfs, devfs, and ramfs are supported with this version.

Java::Import::Design is the design of the Java::Import Module.

MOTIVATIONS

The original motivation for writing this module came out of a project I was working on during my previous employment. We had built a system in which a major part was implimented using EJBs on a J2EE server. In addition, we had a large component of the system, that already existed, and was written in Perl. We did not want to scrap our Perl work but it was becoming more tedious to maintain two implimentations as more and more things were being added to the system.

So, we decided that the major pieces of business logic would reside on the J2EE server and the Perl would be modified to make calls to the server. After some time and experimentation we began to realize that the memory footprint as well as the amount of time needed to make calls to the server using existing Perl to Java integration sulutions were just not acceptable. We therefore set out to find some other way. We tried all sorts of things but in the end we couldnt find anything that met our requirements and therefore decided to keep the origional system of doing things.

While at that job we never did find a suitable way to integrate our two systems. However, the problem still haunted me. It wasnt until the end of my career at that company that I saw an announcement for Googles first Summer of Code. It just so happened that as Google was announcing their brand new program that I had begun to play with the GNU GCJ suite of Java tools and came up with the idea of taking advantage of their ability to natively compile Java code for use with Perl. This may not have been a new idea but I couldnt find anything that would help me so I decided to write and submit a proposal to Google. Well, I was accepted and you now have Java::Import.

When I began to work on this project I started by creating my own namespace instead of stepping on the toes of the other existing Java/Perl integration project, Inline::Java. I did this primarily because I wanted a clean slate on which I could fully explore the nuances of GCJ, in particular its CNI interface. As I worked my module started to evolve into its own beast and at that point it seemed locigal to keep my own namespace. It is not my intention to replace Inline::Java and I still think that in te future much of the work I have done can be used by Inline::Java as an option to use GCJ specific functionality.