Free proguard 3.9 software for linux

SystemImager is software that automates Linux installs, software distribution, and production deployment.
SystemImager makes it easy to do automated installs (clones), software distribution, content or data distribution, configuration changes, and operating system updates to your network of Linux machines. You can even update from one Linux release version to another!
It can also be used to ensure safe production deployments. By saving your current production image before updating to your new production image, you have a highly reliable contingency mechanism. If the new production enviroment is found to be flawed, simply roll-back to the last production image with a simple update command!
Some typical environments include: Internet server farms, database server farms, high performance clusters, computer labs, and corporate desktop environments.
Whats New in 3.8.2 Stable Release:
- fixed a bug in the monitoring: REBOOTED state was not properly reported in some minimal image (without the command which)
- added "--config FILE" option to si_prepareclient and si_mkbootpackage (and removed from si_mkautoinstalldisk: the option must be used in commands that explicitly create an initrd.img from initrd_template)
- do not hard-code common patterns of exclusion in si_getimage (created the configuration file /etc/systemimager/getimage.exclude)
- si_getimage didnt stop correctly the rsync daemon in the golden client, using rsync over ssh for the image retrieval
Whats New in 3.9.2 Development Release:
- Added support for the PS3 architecture
- Improved support and compatibility with Debian (now deb packages can be automatically built from source using the new target "make deb")
- updated BOEL kernel to 2.6.21 (for i386 and x86_64)
- fixed a bug that broke si_mkautoinstalldisk
- free unused RAM of the initramfs (only with cpio initrd.img) after switching to tmpfs
- updated udev to udev_108-0ubuntu4
- support old versions of the BitTorrent client (better compatibilty with *Ubuntu)
- fixed a lib/lib64 bug with ppc64
- fixed a bug in si_monitor daemon that didnt start correctly when the directory /var/lock/systemimager was not present
- added missing manpages
- remount the filesystems in read-only before giving-up when the umount fails at the end of the installation
- create all the swap partitions before the other filesystems in the autoinstall script: this avoids potential OOM conditions that could occur during the filesystem creation
- removed unused coreutils package from initrd.img
- removed unmaintained package imagemanip
- removed deprecated command si_mkbootmedia

CentOS is an Enterprise-class Linux Distribution derived from sources freely provided to the public by a prominent North American Enterprise Linux vendor.
CentOS conforms fully with the upstream vendors redistribution policy and aims to be 100% binary compatible. (CentOS mainly changes packages to remove upstream vendor branding and artwork.) CentOS is free, however, we ask for a small contribution. CentOS is a project of the cAos Foundation.
CentOS is developed by a small but growing team of core developers. In turn the core developers are supported by an active user community including system administrators, network administrators, enterprise users, managers, core Linux contributors and Linux enthusiasts from around the world.
CentOS has numerous advantages over some of the other clone projects including: an active and growing user community, quickly rebuilt, tested, and QAed errata packages, an extensive mirror network, developers who are contactable and responsive, multiple free support avenues including IRC Chat, Mailing Lists, Forums, a dynamic FAQ. Commercial support is offered via a number of vendors.
CentOS exists to provide a free enterprise class computing platform to anyone who wishes to use it. CentOS 2 and 3 are fully compatible rebuilds of RHEL 2 and 3 respectively. CentOS 2 and 3 are reproduced from RHEL sources that are freely distributed by RedHat.
Redistributed packages and sources comply fully with RedHats redistribution requirements. CentOS 2 and 3 are designed for people who need an enterprise class OS without the cost, support, certification, or brand name of RedHat.
Main features:
- easy maintenance
- suitability for long term use in production environments
- friendly environment for users and package maintainers
- long-term support of the core
- active development
- community infrastructure
- open management
- open business model
- commercial support - offered by a partner vendor

Deb creator is a GTK wizard tool to build deb packages easily.

This software is based upon debhelper, dpkg-buildpackage, and other well tested tools. You can try to build simple package from source archive with some GNU-packaged software containing at least a Makefile and a configure script.

In the future this application will be able to perform advanced operation.

Note: you dont need any particular package building knowledge to use this.

libtiff library provides support for the Tag Image File Format (TIFF), a widely used format for storing image data. The latest version of the TIFF specification is available on-line in several different formats, as are a number of TIFF Technical Notes (TTNs).
Included in this software distribution is a library, libtiff, for reading and writing TIFF, a small collection of tools for doing simple manipulations of TIFF images on UNIX systems, and documentation on the library and tools.
A small assortment of TIFF-related software for UNIX that has been contributed by others is also included. The library, along with associated tool programs, should handle most of your needs for reading and writing TIFF images on 32- and 64-bit machines.
Whats New in 3.8.2 Stable Release:
- Along with several cleanups and bugfixes, this release fixes an important regression related to the JPEG-in-TIFF codec introduced in the previous release.

ProGuard is a free Java class file shrinker, optimizer, and obfuscator. ProGuard project can detect and remove unused classes, fields, methods, and attributes. It can then optimize bytecode and remove unused instructions.
Finally, it can rename the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
More compact jar files also means smaller storage requirements, faster transfer of applications across networks, faster loading, and smaller memory footprints.
ProGuards main advantage compared to other Java obfuscators is probably its compact template-based configuration. A few intuitive command line options or a simple configuration file are usually sufficient. For instance, the following configuration option preserves all applets in a jar:
-keep public class * extends java.applet.Applet
The user manual explains all available options and shows more examples of this powerful configuration style.
ProGuard is fast. It only takes seconds to process programs and libraries of several megabytes. The results section presents actual figures for a number of applications.
ProGuard is a command-line tool with an optional graphical user interface. It also comes with plugins for Ant and for the J2ME Wireless Toolkit.
ProGuard is a Java class file shrinker, optimizer, and obfuscator. The shrinking step detects and removes unused classes, fields, methods, and attributes. The optimization step analyzes and optimizes the bytecode of the methods. The obfuscation step renames the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
ProGuard can also be used to list unused fields and methods in an application, and to print out the internal structure of class files.
ProGuard typically reads the input jars (or wars, ears, zips, or directories). It then shrinks, optimizes, and obfuscates them. It then writes the results to one or more output jars (or wars, ears, zips, or directories). The input jars can optionally contain resource files. ProGuard copies all non-class resource files from the input jars to the output jars. Their names and contents remain unchanged.
ProGuard requires the library jars (or wars, ears, zips, or directories) of the input jars to be specified. It can then reconstruct class hierarchies and other class dependencies, which are necessary for proper shrinking, optimization, and obfuscation. The library jars themselves always remain unchanged. You should still put them in the class path of your final application.
In order to determine which code has to be preserved and which code can be discarded or obfuscated, you have to specify one or more entry points to your code. These entry points are typically classes with main methods, applets, midlets, etc.
- In the shrinking step, ProGuard starts from these seeds and recursively determines which classes and class members are used. All other classes and class members are discarded.
- In the optimization step, ProGuard further optimizes the code. Among other optimizations, classes and methods that are not entry points can be made final, and some methods may be inlined.
- In the obfuscation step, ProGuard renames classes and class members that are not entry points. In this entire process, keeping the entry points ensures that they can still be accessed by their original names.
Any classes or class members of your code that are created or invoked dynamically (that is, by name) have to be specified as entry points too. It is generally impossible to determine these cases automatically, but ProGuard will offer some suggestions if keeping some classes or class members appears necessary. For proper results, you should at least be somewhat familiar with the code that you are processing.
ProGuard does handle Class.forName("SomeClass") and SomeClass.class constructs automatically. The referenced classes are preserved in the shrinking phase, and the string arguments are properly replaced in the obfuscation phase. With variable string arguments, it is generally impossible to determine their possible values (they might be read from a configuration file, for instance).
However, as mentioned, ProGuard will note constructs like "(SomeClass)Class.forName(variable).newInstance()". These might be an indication that the class or interface SomeClass and/or its implementations may need to be preserved. You can then adapt your configuration accordingly.
Whats New in 3.9 Stable Release:
- This release fixes a number of bugs.
- Notably, ".class" constructs compiled in Java 6 are now handled correctly.
- The optimization step now avoids a possible division by 0 and correctly processes local variables with indices larger than 255.
- The documentation and examples have been updated.
Whats New in 4.0 Beta Development Release:
- Added preverifier for Java 6 and Java Micro Edition, with new option -dontpreverify.
- Added new option -target to modify java version of processed class files.
- Made -keep options more orthogonal and flexible, with option modifiers allowshrinking, allowoptimization, and allowobfuscation.
- Added support for configuration by means of annotations.
- Improved shrinking of unused annotations.
- Added check on modification times of input and output, to avoid unnecessary processing, with new option -forceprocessing.
- Added new options -flattenpackagehierarchy and -repackageclasses (replacing -defaultpackage) to control obfuscation of packages names.
- Added new options -adaptresourcefilenames and -adaptresourcefilecontents, with file filters, to update resource files corresponding to obfuscated class names.
- Now respecting naming rule for nested class names (EnclosingClass$InnerClass) in obfuscation step, if InnerClasses attributes or EnclosingMethod attributes are being kept.
- Added new inter-procedural optimizations: method inlining and propagation of constant fields, constant arguments, and constant return values.
- Added optimized local variable allocation.
- Added over 250 new peephole optimizations.
- Improved making classes and class members public or protected.
- Now printing notes on suspiciously unkept classes in parameters of specified methods.
- Now printing notes for class names that dont seem to be fully qualified.
- Added support for uppercase filename extensions.
- Rewritten class file I/O code.
- Updated documentation and examples.

Valknut project is a peer-2-peer file-sharing program (similar to Kazaa, Soulseek or eDonkey) that uses the Direct Connect protocol.
It is compatible with other DC clients, such as the original DC from Neomodus, and DC++.
Main features:
- open source
- multiplatform (Linux,Win32,OSX ...)
- multilanguage
- multihub connections
- multihub search
- multi-/chunkdownload (download one file from multiple sources at the same time)
- firewall support
- sounds
- favorite hub list
- online translator
- load/save search results
- autosearch new sources
- socks support for linux (http://www.inet.no/dante/)
- proxy support for hublists
- support bz2 share lists
- support xml share lists
- support ssl transfers
- support ssl hub connections (e.g. hub use sslproxy)
- support secure chat (not secure against "Man In The Middle Attack")
- chat emoticons
- tiger tree hash (TTH) support