Free built by software for linux

Build it Fast (BIF) is a PHP Framework. It contains several classes that help you develop complex Web applications in a short amount of time.

It brings the concept of the widget to Web development. It features Cascade Skins and transparent session management.

Its meant to make PHP programers life much easier, and making better web applications.

Boost.Build is a system for large project software construction, which is simple to use and powerfull. Boost.Build project is an onging project to rewrite Boost.Build, improving design and making it more extensible.
Main features:
- Simple and high level target description language. In most cases name of target and list of sources is enough.
- Variant builds. You can build with your choice of basic variants (e.g. debug, release, profile...), toolsets (e.g. gcc and msvc) and specific properties (e.g. inlining off) from a single command invocation.
- Portability. ``Feature Normalization allows to fine-tune targets independently from the toolset used, and modular toolset descriptions are employed to generate actual build instructions.
- Multi-project builds. Several projects can be combined and built together, with dependencies correctly tracked. Typically, the setting (like include paths and defines) needed to use other project will be handled automatically.
- Extensibility. New file types and tools can be easily added
Enhancements:
- Support was added for several new tools, including the Qt4 library.
- An "indirect requirement" feature was added.
- Several improvements were made in the "install" target.
- The --build-dir, --debug-building, and --clean-all command line options were added.
- Numerous bugs were fixed, and interface improvements were done.

Firewall by Jim is a firewall that takes advantage of tcp_wrappers information to block users. I got tired of the firewall scripts out there not doing what I wanted them to.. I wanted a firewall that was flexible to use, but did its job. I wanted one that could be configured to any circumstance easily without changing the script itself. That is why I designed my firewall to use simple text files for configuration ease.

I have built in mutlple mean of protection into the firewall itself. Of the most notable is the hacker, trojan, spam, and blacklist capabilities.

The hacker protection will prevent the outside world from running unwanted commands. If you choose to enable this function.

The hacker protection will prevent the outside world from running unwanted commands. The trojan protection has two different levels. Standard and Intensive. The standard protection only protections from known linux and unix trojans. Where as the intensive will protect from all known trojans from windows, linux, and unix based.

The spam protection will block any IP address which is in list, from sending mail to your SMTP server.

The blacklist protection will block total communications to a site. I have also included a blacklist update script which will pull blacklist information from http://www.dshield.org .

nobel is a small ANSI C boolean expression parsing library and program for projects that need boolean expression parsing support built in, but bigger tools are overkill in size or options.

Java::Build::JVM is a Perl module that starts one JVM for compiling.

SYNOPSIS

use Java::Build::JVM;

my $compiler = Java::Build::JVM->getCompiler();
$compiler->destination("some/path");

$compiler->classpath("some/pathto/jar.jar:some/other/path/javas");
$compiler->append_to_classpath("something/to/add/to/previous/path");

$compiler->compile([ qw(list.java of.java programs.java) ]);

This class starts a single JVM which it then helps you contact for compiling tasks. This is the most important feature of the popular Ant build tool. Using this class, you can effectively replace Ant, and its notoriously unmaintainable build.xml files, with Perl scripts. Most Ant tasks are already built in to Perl with far more flexibility than Ant provides.

To obtain a compiler, use this module, then call getCompiler. It has that name to prevent conflicts with the Java new keyword.

Once you have a compiler, you may change the destination of subsequent compiles from the location of the source files to a directory of your choice using the destination method. You can create or append to a classpath with the classpath or append_to_classpath methods. Note that your CLASSPATH environment variable still works in its usual way.

Finally, once you have the destination and classpath set, you can compile a list of files by passing them to the compile method. Note that they need to be in an array reference (if you dont know what that means, put the list in square brackets).

Note that you must have tools.jar in your CLASSPATH when you run your script. Without that, JVM.pm will not be able use Inline::Java. The classpath you use inside the script may be the same or different than your environment variable, depending on how you use the classpath and append_to_classpath methods.
Since Sun has, in its finite wisdom, chosen to deprecate the compiling methods that javac uses, there will be one warning for each time you call compile. It will say something like this:

Note: sun.tools.javac.Main has been deprecated.
1 warning

This warning is not a problem in Java 1.4.

bandwidthd tracks usage of TCP/IP network subnets and builds HTML files with graphs to display network utilization. Charts are built by individual IP to show their utilization over 2, 8, 45, and 400 day periods. It color codes HTTP, HTTPS, TCP, UDP, ICMP, VPN, and P2P traffic.
BandwidthD runs on most platforms including windows. For unix nex libraries are only required: libpcap, libgl and libpng.
Most of the info youre looking for is on the SourceForge project page. At SourceForge we keep all new releases, the bug tracker and the support forums.
Bandwidthd now produces output in 2 ways. The first is as a standalone application that produces static html and png output every 200 seconds. The second is as a sensor that transmits its data to a backend database which is then reported on by dynamic php pages. The visual output of both is simular, but the database driven system allows for searching, filtering, multiple sensors and custom reports.
Enhancements:
- Big Feature - Added optional postgresql database logging mode and php for dynamic graph creation from databases. Great for big sites, multiple sensors with very low overhead collect traffic statistics and log them to database. Graphs are created when a user visits the page instead of burning CPU cycles night and day. Logging/Multiple sensor support is completed.
- Big Feature - Implemented auto conf
- Ported to and compiles on:
- ix86 Fedora Core 2
- ix86 Solaris 9
- ix86 OpenBSD 3.4
- ix86 Debian 2.2
- ix86 FreeBSD 4.8
- AMD64 Fedora Core 3
- PPC MaxOsX 10.2
- ix86 Microsoft Windows
- Changed default interval to 200 seconds to save ram and cpu power
- Huge performance gain in graphing engine due to bug fix (Peak Send and Total Sent strings font operations were being done to each graphic almost 1000 times instead of just 1)
- Removed need of Sys V IPC shared memeory
- log rotation on all logs implemented - secondary logs rotate every RANGE?/RANGE1 HUPs
- Added syslog support, removed all printfs except a few early errors, closed stdin, stdout, and stderr before beginning capture loop
- Bandwidthd collects the pids of its children and distributes HUP and TERM signals when issued to the first process
- Changed yy parser name to bdconfig_ to avoid a bug in BSD
- Added some semi-colons to conf.y to fix BSD flex/bison compatability bug
- Fixed bug that caused memory corruption when ram datastore had data on more than IP_NUM ips.
- Fixed some longs that missed being converted to unsigned long long.
- Fixed bug in CDF recovery that would cause bandwidthd to ignore some CDF logs during recovery
- Bandwidthd now checks for ./etc/bandwidthd.conf, and if it doesnt exist it checks for
- /usr/local/bandwidthd/etc/bandwidthd.conf, if that exists it will htdir("/usr/local/bandwidthd")
- Fixed problem that caused bandwidthd to sit and never create graphs if graph is set to false do not store data in ram, do not fork unless output_cdf is true log names changed to be consistent so all logs could be rotated with same function

Module::Build::JSAN is a Perl module to build JavaScript modules for JSAN.

SYNOPSIS

use Module::Build::JSAN;

my $build = Module::Build::JSAN->new(
module_name => Foo-Bar,
license => perl,
dist_author => Joe Developer ,
dist_abstract => Say something pithy here,
dist_version => 0.02,
keywords => [qw(Foo Bar pithyness)],
build_requires => {
Test.Simple => 0.20,
},
requires => {
JSAN => 0.10,
Baz-Quux => 0.02,
},
);

$build->create_build_script;

This is a developer aid for creating JSAN distributions. Please use the example given in the SYNOPSIS to create distributions.

Module::Build::TestReporter is a Perl module to help users report test failures.

SYNOPSIS

use Module::Build::TestReporter;
my $build = Module::Build::TestReporter->new(
# normal Module::Build code here
);

# or, in your own M::B subclass

package My::Module::Build;

use Class::Roles does => Module::Build::TestReporter;

# your code as usual

Shipping test suites with your code is a good thing, as it helps your users know that your code works as you expect on your systems and it allows you better debugging information if things break in environments where you havent yet tested your code. However, it can be tedious and tricky to convince your users to send you the appropriate failure information.

Module::Build::TestReporter extends and enhances Module::Build to collect information on test failures and the Perl environment for users to send to you. Rather than walking them through running tests in verbose mode on the phone, in IRC, or via e-mail, use this module alongside your usual Module::Build build process and it will gather this information in case of failure.