Free xlassie 1.8 software for linux

XLassie is an enhanced version of XBiff. Support for POP3 or IMAP mailservers, ability to run a command when clicked on, written in straight xlib so memory usage is less, and it doesnt just tell you if you have new mail, but how many new messages you have. Extra support for both KDE and WindowMaker.
Main features:
- Counts the number of new messages you have
- Can query remote mail on a POP3 server or on an IMAP server
- Can count local mail with an mbox or a maildir style spool
- Uses less memory than XBiff, and just about every other X mail checker
- Can run a command when clicked on, and/or when new mail arrives
- Supports both the KDE and the WindowMaker applet protocols, in addition to running as a standard X application
- Support for qmail style maildir systems. Should work automatically if you have maildir setup properly. Or point xlassie to a directory instead of a file, and it will keep track of the number of files in it. Thanks to Pitt Murmann for inspiration.
- Backup font selection system. XLassie will try a list of builtin font names if it cant find the default font.

tmake provides a cross-platform makefile tool.
tmake is an easy-to-use tool from Trolltech to create and maintain makefiles for software projects. It can be a painful task to manage makefiles manually, especially if you develop for more than one platform or use more than one compiler. tmake automates and streamlines this process and lets you spend your valuable time on writing code, not makefiles.
Our main motivation for developing tmake was that we spent far too much time maintaining makefiles for Qt, our cross-platform GUI toolkit. Qt supports around 15 flavors of Unix, Microsoft Windows, and around 15 different C++ compilers. We looked at GNU autoconf, but it was Unix-specific and not flexible enough in our opinion. Our makefile system also had to deal with Qt meta object compiler (moc) issues. The moc program extracts meta information from C++ files and generates a C++ file with data tables etc. It takes extra work to add makefile rules for the moc and wanted to automate this task.
tmake is written in Perl and requires that you have installed perl version 5 or newer. Basic use of tmake requires no perl knowledge, but if you know perl you can extend tmake and write your own makefile templates.
Enhancements:
- Platform fixes for Tru64, Borland, Irix, HP-UX, AIX, UnixWare7 and Reliant UNIX
- Support for Intel C++
- Initial support for Qt/Embedded on FreeBSD

Mezzanine is a set of tools which simplify the management of software packages and collections of software packages.
It provides encapsulation for source and package management as well as a streamlined mechanism for making changes to these packages.
Enhancements:
- SCM functionality has been rewritten as implementations of a standard interface class.
- This will allow more seamless support of other SCM systems (e.g. Subversion).
- Dependencies on the "Meta" package, perhaps the worst thing ever to happen to CPAN, have been worked around, and this release allows for local mode operation on non-CPAN Perl archives on the filesystem.
- Spec files are now passed through RPMs own parser for improved macro expansion.
- Several new specgen templates were added, and many minor bugs fixed along the way.

tsocks provides transparent network access through a SOCKS version 4 or 5 proxy (usually on a firewall).

SOCKS servers are a form of proxy that are commonly used in firewalled LAN environments to allow access between networks, and often to the Internet. The problem is that most applications dont know how to gain access through SOCKS servers. This means that network based applications that dont understand SOCKS are very limited in networks they can reach. An example of this is simple telnet.

tsocks role is to allow these non SOCKS aware applications (e.g telnet, ssh, ftp etc) to use SOCKS without any modification. It does this by intercepting the calls that applications make to establish network connections and negotating them through a SOCKS server as necessary. If youre on a network firewalled from the internet with a SOCKS server for outside access, telnet cant use this server and thus cant telnet out to the Internet., sou you cannot get out.

tsocks is based on the shared library interceptor concept. Through use of the LD_PRELOAD environment variable or the /etc/ld.so.preload file tsocks is automatically loaded into the process space of every executed program. From there it overrides the normal connect() function by providing its own. Thus when an application calls connect() to establish a TCP connection it instead passes control to tsocks. tsocks determines if the connection needs to be made via a SOCKS server (by checking /etc/tsocks.conf) and negotiates the connection if so (through use of the real connect() function )

FSVS stands for "Fast System VerSioning", "File System VerSioning" or "Full System VerSioning".
You may think of it as some kind of tar or rsync with versioned storage.
A future capability will be to cope with local adjustments for different machines (using branching techniques), so that most of the space needed for the backup of system-files (/bin, /usr, ...) can be shared between machines.
Main features:
- initialize itself for operation (define target URL)
- commit to this URL (backup), with meta-data support (owner, group, mode, devices, symlinks)
- show the status, ie. which entries have changed, and what was changed (data or meta-data)
- update from this URL (restore), with meta-data support
- use advanced ignore patterns, eg. to ignore all virtual filesystems like /proc, /sys, /dev (if devfs), and so on. PCRE-expressions and recursive ignore patterns are possible, too.
- Re-Synchronize with the repository, ie. get list of files in repository, to commit all different files.

Socketpipe project connects over a TCP/IP socket a remote command specified to a local input generation command and/or a local output processing command.
The input and output of the remote command are appropriately redirected so that the remote commands input will come from the local input generation command and the remote commands output will be sent to the local output processing command.
The remote command is executed on the machine accessed through the login command. The socketpipe executable should be available through the execution path in the remote machine.
The braces used for delimiting the commands and their arguments should be space-separated and can be nested. This feature allows you to setup complex and efficient topologies of distributed communicating processes.
Although the initial socketpipe communication setup is performed through client-server intermediaries such as ssh(1) or rsh(1), the communication channel that socketpipe establishes is a direct socket connection between the local and the remote commands.
Without the use of socketpipe, when piping remote data through ssh(1) or rsh(1), each data block is read at the local end by the respective client, is sent to the remote daemon and written out again to the remote process.
The use of socketpipe removes the inefficiency of the multiple data copies and context switches and can in some cases provide dramatic throughput improvements. On the other hand, the confidentiality and integrity of the data passing through socketpipes data channel is not protected; socketpipe should therefore be used only within a confined LAN environment.
(The authentication process uses the protocol of the underlying login program and is no more or less vulnerable than using the program in isolation; ssh(1) remains secure, rsh(1) continues to be insecure.)
Enhancements:
- This version corrects a bug in the command parsing of the Windows version of socketpipe.