Free find em all 1.0 software for linux

FindEmAll is another graphical find-and-grep tool.
Find Em All is inspired by XFCE-3s XFglob and Efinder which is part of the Equinox desktop environment.
Unfortunately XFglob is no longer included in XFCE and Efinder does not seem to work (at least for me), because it uses XFCEs glob command which is no longer available.
Main features:
- optional Perl-style regular expression syntax (grep -P)
- search for files owned by non-system user / group (find -nouser -nogroup)
- search files where the search pattern does not match
- exclude binary files from search
Files may be opened in your favorite editor by a double-click on an entry in the list of results. Right-clicking a file opens a context menu that allows to choose an arbitrary application to open this file.

FindIt NIX project is a clone of a great find-the-difference game.
FindItNIX is a clone of the Windows game FindItXP. The goal is to spot the 5 differences between 2 images within a certain amount of time. The quicker you find them, the higher the bonus will be.
FindItNIX features high scores compatible with those of the Windows version and over 1200 levels available on the Internet.
Enhancements:
- Implemented hack in Makefile so the program links to the libqt-2.x.x.so in stead of the 3.x libraries which cause an unknown problem. Until I fixed this, and qt-2.x.x is
- still on your system you wont have any problems compiling nymore.
- Some minor documentation updates.

imapbiff checks IMAP accounts for new mail. It uses images similar to those of the classic xbiff program. The project works similar to xbiff, except it is only used to check for new mail in IMAP accounts.

It is written in perl, and requires the Tk module for perl. It was written spefically to be docked in my fvwm2 button bar, as I could not find a simple xbiff like app that would do IMAP checks.

PHP EMS Tools project is a software for volunteer and small paid emergency medical services (EMS) organizations that provides crew scheduling, roster maintenance and printing, rig checks, maintenance reports, and other facilities in an easy-to-use Web-based package.

PHP EMS Tool is a software package for Emergency Medical Services (EMS) agencies. It allows you to maintain a monthly crew schedule, roster, record of apparatus checks, address book, count your members monthly hours, and more. It is designed to be installed on a server on the local network at your headquarters. It *can* be installed on an internet-based host, but this is not suggested, as security is very lax in the current version - it is designed to stop members from casually doing things they shouldnt, not to protect your server from the dangers of the Internet.

The current version incorporates a feature to allow the schedule, roster, and hours count to be visible from the Internet, when configured properly.

PHP EMS Tools is totally free, and open source. It is programmed in the PHP language, which most web servers support. To run PHP EMS Tools, you will need a web server (Apache recommended), the MySQL database server, PHP, and a few other pieces of software. PHP EMS Tools *should* run under any operating system that supports these packages, but is designed to be run under Linux (which is also 100% free and open source). To install PHP EMS Tools, you will need root access to the server, or will need to get the systems administrator to create a database and users for you.

File::Find::Parallel allows you to traverse a number of similar directories in parallel.

SYNOPSIS

use File::Find::Parallel;

my $ffp = File::Find::Parallel->new( qw( /foo /bar ) );

print "Union:n";
my $union = $ffp->any_iterator
print " $_n" while $_ = $union->();

print "Intersection:n";
my $inter = $ffp->all_iterator
print " $_n" while $_ = $inter->();

File::Find is the ideal tool for quickly scanning a single directory. But sometimes its nice to be able to perform operations on multiple similar directories in parallel. Perhaps you need to compare the contents of two directories or convert files that are shared in more than one directory into hard links.

This module manufactures iterators that visit each file and directory in either the union or the intersection of a number of directories. Hmm. What does that mean?

Given two directory trees like this

foo
foo/a
foo/b/c
foo/d

bar
bar/a
bar/b
bar/e

you can choose to work with the intersection of the two directory structures:
.
./a
./b

That is the subdirectories and files that the foo and bar share.
Alternately you can work with the union of the two directory structures:
.
./a
./b
./b/c
./d
./e

Still not clear? Well, if you wanted to do a recursive diff on the two directories youd iterate their union so you could report files that were present in foo but missing from bar and vice-versa.

If, on the other hand you wanted to scan the directories and find all the files that are common to all of them youd iterate their intersection and receive only files and directories that were present in all the directories being scanned.

The any_iterator and all_iterator are built on a more general purpose method: want_iterator. If, for example, you want to make links between files that are found in more than one directory you might get your iterator like this:

my $iter = $ffp->want_iterator( 2 );

The apparently magic 2 reflects the fact that if youre going to be making links you need at least two files. No matter how many directories you are iterating over in parallel you will only see files and directories that appear in at least two of those directories.

File::Find::Parallel can scan any number of directories at the same time. Heres an example (on Unix systems) that returns the list of all files and directories that are contained in all home directories.

use File::Glob :glob;
use File::Find::Parallel;

my $find = File::Find::Parallel->new( bsd_glob( /home/* ) );

my @common = ( );
my $iter = $find->all_iterator;
while ( defined my $obj = $iter->() ) {
push @common, $obj;
}

print "The following files are common to ",
"all directories below /home :n";

print " $_n" for @common;

For a complete concrete example of its use see lncopies in the bin subdirectory of this distribution.

Iterators

The iterator returned by any_iterator, all_iterator or want_iterator is a code reference. Call it to get the next file or directory. When all files and directories have been returned the iterator will return undef.

Once created an iterator is independent of the File::Find::Parallel object that created it. If the object goes out of scope and is destroyed during the life of the iterator it will still function normally.

You may have many active iterators for a single File::Find::Parallel object at any time.

File::Find::Similars is a Similar files locator.

SYNOPSIS

use File::Find::Similars;

File::Find::Similars->init(0, @ARGV);
similarity_check_name();

Similar-sized and similar-named files are picked as suspicious candidates of duplicated files.

What descirbes it better than a actual output. Sample suspicious duplicated files:

## =========
1574 PopupTest.java /home/tong/.../examples/chap10
1561 CardLayoutTest.java /home/tong/.../examples/chap1
1570 PopupButtonFrame.class /home/tong/.../examples/chap6

## =========
22984 BinderyHelloWorld.jpg /home/tong/...
17509 MacHelloWorld.gif /home/tong/...

The first column is the size of the file, 2nd the name, and 3rd the path. The motto for the listing is that, I would rather my program overkills (wrongly picking out suspicious ones) than neglects something that would cause me otherwise years to notice.
By default, File::Find::Similars(3) assumes that similar files within the same folder are OK. Hence you will not get duplicate warnings for generated files (like .o, .class or .aux, and .dvi files) or other file series.

Once you are sure that there are no duplications between folders and want File::Find::Similars(3) to scoop further, specify the first parameter as 1. This is very good to eliminate similar mp3 files within the same folder, or downloaded files from big sites where different packaging methods are used, e.g.:

## =========
66138 jdc-src.tar.gz .../ftp.ora.com/published/oreilly/java/javadc
147904 jdc-src.zip .../ftp.ora.com/published/oreilly/java/javadc

MP3::Find::Base is a base class for MP3::Find backends.

SYNOPSIS

package MyFinder;
use base MP3::Find::Base;

sub search {
my $self = shift;
my ($query, $dirs, $sort, $options) = @_;

# do something to find and sort the mp3s...
my @results = do_something(...);

return @results;
}

package main;
my $finder = MyFinder->new;

# see MP3::Find for details about %options
print "$_n" foreach $finder->find_mp3s(%options);

This is the base class for the classes that actually do the searching and sorting for MP3::Find.