Free i spy software for linux

A Perl script which identifies new files on various FTP and Web sites.
Installation
Copy the program where you can acces it and do following commands:
cp i-spy /usr/local/bin/
Make sure the executable bit is set:
ls -l /usr/local/bin/i-spy
-rwxr-xr-x 1 root root 28568 Nov 22 11:36 /usr/local/bin/i-spy
if not, then set it:
$ chmod +x /usr/local/bin/i-spy
If you have perl installed elsewhere than /usr/local/bin, then create
a symbolic link:
$ cd /usr/local/bin
$ ln -s /usr/bin/perl
[or wherever you keep perl]
Now, copy the Log::File module into your Perl distributions site_perl
directory:
$ cp -r Log /usr/local/lib/perl5/site_perl/5.005/
[or wherever you keep site-specific perl modules]
You may also keep the Log::File module in the same directory as you
plan to use for your sites and logs.
Enhancements:
- Added support for browser agent masquerade
- Added support for Google News (Yum)
- Modernized examples

KSetiSpy is a KDE utility that monitors the progress of the SETI@home client, and displays all kinds of information about the work unit(s) being processed.
It uses the same interface as SETI Spy, a Windows program written by Roelof Engelbrecht.
The SETI@home project started in May 1999; its goal is to harness the power of distributed computing to analyze radio signals from space, for "the small but captivating possibility of detecting the faint murmur of a civilization beyond Earth".
To participate in this exciting project, all you have to do is to run the SETI@home client program. This program downloads a set of data (usually called "work unit") from the SETI@home servers, processes it on the local machine (using idle processing time that would otherwise go wasted), and then transmits the result back to the servers.
Over time, SETI@home participants people have become more and more interested in learning everything about the data contained in these work units and the computations done on them. To address these needs, several SETI@home monitoring add-on programs were developed. These extract interesting information from the SETI@home client and present it in a user-friendly way.
One of the most complete SETI@home monitoring tools available today is a Windows program named SETI Spy. KSetiSpy has been created with the intent of providing a version of SETI Spy for my favorite desktop environment (KDE). KSetiSpy borrows most of its user interface conventions from SETI Spy, so SETI Spy users will feel immediately at home with KSetiSpy.
KSetiSpy started as a programming experiment in KDE in June 2001, and has grown a lot since then, mainly to keep up with the ever-increasing feature set of its Windows counterpart. Like many open source projects, its basically the work of a single developer (that would be me), working on it on his spare time. Therefore advancement is not linear, and debugging is mostly left to the users (that would be you). If you run into a bug, please report it to Roberto Virga
Enhancements:
- fixed RA and Dec formatting
- fixed julian date conversion (was off by 6 hours - thanks to Bengt-Erik Soderstrom for reporting this)
- fixed constellation links (the P.A.S. re-organized their web site)

KBoincSpy is a KDE monitor and control utility for the BOINC client. KBoincSpy displays a lot of useful information about the computation of work units, such as the percent of work done, and estimates of the completion time and credits granted.
For some projects like SETI@home and ClimatePrediction.net, it also reports some interesting data about the content and significance of each work unit being analyzed.
It can be also used to control the behavior of the BOINC client, allowing the user to attach to (as well as detach from) projects, start/stop the computation, or suspend all network communications.
Its interface design was inspired by SETI Spy, a Windows monitoring utility for SETI@home Classic written by Roelof Engelbrecht.
The Berkeley Open Infrastructure for Network Computing is a software platform for distributed computing. It enables organizations who oversee scientific projects requiring extensive computing resources to easily set up and maintain a distributed computing infrastructure.
By downloading the BOINC distributed computing client, each of the hundreds of thousands of participants worldwide can select the scientific projects more to his/her liking and assign some computing resources to them.
Enhancements:
- This release focuses on reaching almost feature parity with the latest BOINC client from Berkeley (the 5.x series).
- Among the new features were an attach-to-project wizard, host and user statistics graphs, and Web links.
- This version also features new translations to eight languages. Precompiled packages are available for the x86 and x86-64 architecture versions of the Fedora, Gentoo, Mandriva, Slackware, and SuSE Linux distributions.

i.File is a file manager for Linux written for the Windows refugees that are arriving in Linux only to find that the state of the user interface is rather poor. I personally somewhat fall into this catagory, although more as a power user than the average Joe.
Both the leading file managers for KDE and Gnome are well... not to put too fine a point on it: crap. There are just not ready for everyday use by normal people, because of the untold number of bugs in the usability and function that are STILL there 3 years after they first infested Linux desktops.
Not that this project will start off any better, but my hope is that itll end far more successfully than the aforementioned software. i.File project is targetted at other developers in an attempt to get some help with bringing it up to speed. Enough of the basic code layout and implementation is done so that the user can see how things should work. And now its just time to fill in the blanks and bust those bugs.
Main features:
- Be fast. i.File doesnt load icons for every file by its mime type. Because that takes too long. All the algorithms are designed to make it fast. The use of hashtables is pervasive. At no point should "eye candy" ever take precedence over speed. Startup/shutdown time should be sub-second. Drag and drop should have latencies around 100ms at most.
- All views of the same inode (file/dir/etc) point back to the same object, thus when the object changes, all views of that automatically update.
- Network accesses and all other tasks that can take time should be threaded. There is no excuse for locking up the GUI thread while the application goes off to get some data.
- Be minimal. i.File is not a thumb nail viewer, or any other type of viewer. Applications do the viewing, not the file manager. Viewing tasks bloat up the file manager.
- Every file is typed with a mime type. This is marginally better than using a files extension to associate it with an application.
- The Win2k implementation of Windows Explorer is the basis for some of the user interface because it works, people are used to it, and its "the standard". And no the experiments with file manager UI in Linux didnt work. They suck badly, thats why there is i.File in the first place.

I-cons are easy to read, clear-looking and (allmost) configurable set of SuperKaramba themes, together making desktop look nice (i hope).

Each widget has a number of config options. From these, i would mention "3/4 size widget", which makes widget switch icons and texts sizes, so widget became 96px height, instead of 128px.

Also every widget has ability to get in "Nice mode", which causes informations more easy-to-read, eg. disk widget will show just percent of fullness or emptyness.

Theme gets icons from /usr/share/nuovext/... . Maybe you will have to change path. (I can only say this path works on Debian with KDE 3.5. If you are missing nuovext icons on Debian, apt yourself kde-icons-nuovext (it is in testing).)

Hope you like it, feel free to express your opinions & feelings.

i-Pony project is a lightweight pub/sub integration framework.
i-Pony is a lightweight pub/sub integration framework, focusing on messaging and connectivity.
Main features:
- The i-Pony framework is a lightweight kit to for developing integration applications.
- It is a publish and subscribe framework based on JGroups technology.
- Adapters can be distributed across the network.
- i-Pony has built in failover support for adapters.
- i-Pony adapters have guaranteed messaging.
- Adapters can be managed using JMX.
Enhancements:
- The first alpha release of the i-Pony integration adapter framework.
- There is currently no documention.
- i-Pony is a pub/sub adapter framework built on top of JGroups.
- It handles failover capability.
- I also has support for message recovery.
- Subscribers automatically get the messages they missed when they were not running.

Major Features:

1. JavaScript debugger for stepping through code one line at a time
2. Status bar icon shows you when there is an error in a web page
3. A console that shows errors from JavaScript and CSS
4. Log messages from JavaScript in your web page to the console (bye bye "alert debugging")
5. An JavaScript command line (no more "javascript:" in the URL bar)
6. Spy on XMLHttpRequest traffic
7. Inspect HTML source, computed style, events, layout and the DOM
   

Enhancements:

• Issue 1763: JavaScript exceptions on some pages [nsIStreamListener.onDataAvailable] and [nsIStreamListener.onStartRequest]
• Remove dubious script tooltip
• Issue 1282: Editing boolean var in watch panel changes it to a string

Requirements: Mozilla Firefox

PyNOVAS allows you to calculate the position and movement of the sun, moon, planets, and stars with great precision using Python.
PyNOVAS software is based on the NOVAS software used by United States Naval Office (USNO) to produce the Astronomical Almanac and MICA. Ephemerides are supplied by the Jet Propulsion Laboratory (JPL).
You can use this software for Celestial Navigation, and also as a basis for controlling astronomical equipment.
Enhancements:
- This beta release is based on swig 1.3.24 or higher and Python 2.3 or higher.
- It has more examples, including test.py, eclipse.py, and almanac.py