Free block files software for linux

Block Rage will be a falling blocks game with detailed graphics and animated plasmatic backgrounds.
You will be able to challenge your friend in a 2-player hotseat mode! It is strongly inspired by a superb DOS classic.
At present, the game is fully playable, but theres no real graphics nor sounds and absolutely no music.
Enhancements:
- New tile graphics
- Enhanced 2-player screen
- Improved sound module
- Fixed caps lock handling
- Sets window caption
- Other fixes

Code::Blocks is a free C++ IDE built specifically to meet the most demanding needs of its users. The Code::Blocks project was designed, right from the start, to be extensible and configurable.
Built around a plugin framework, Code::Blocks can be extended with plugin DLLs. It includes a plugin wizard so you can compile your own plugins! (Free SDK downloaded separately)
Main features:
- Open Source! GPL2, no hidden costs.
- Cross-platform. Runs on Linux or Windows (uses wxWidgets).
- Made in GNU C++. No interpreted languages or proprietary libs needed.
- Comes in two presentations: Standalone, and MinGW bundle
- Devpack support (optional)
- Extensible thru plugins (SDK available in the downloads section)
- Multiple compiler support:
- GCC (MingW / Linux GCC)
- MSVC++
- Digital Mars
- Borland C++ 5.5
- Open Watcom
- Compiles directly or with makefiles
- Predefined project templates
- Custom template support
- Uses XML format for project files.
- Multi-target projects
- Workspaces support
- Imports MSVC projects and workspaces (NOTE: assembly code and inter-project dependencies not supported yet)
- Imports Dev-C++ projects
- Integrates with GDB for debugging
- Syntax highlighting, customizable and extensible
- Code folding for C++ and XML files.
- Tabbed interface
- Code completion plugin
- Class Browser
- Smart indent
- One-key swap between .h and .c/.cpp files
- Open files list for quick switching between files (optional)
- External customizable "Tools"
- To-do list management with different users

SYNOPSIS

Get the size for directory /etc/ with the block size of 1024 while following symbolic links:

my $obj = File::Size->new(
dir => /etc/,
blocksize => 1024,
followsymlinks => 1,
humanreadable => 1
);
print $obj->getsize(), "n";

File::Size is used to get the size of files and directories.

There are 6 methods you can use:

new

There are 4 optional hash values for the new() method:

dir

The directory you want the module to get the size for it. Default is current working directory.

blocksize

The blocksize for the output of getsize() method. default is 1 (output in bytes).

followsymlinks

If you want to follow symlinks for directories and files, use this option. The default is not to follow symlinks.

humanreadable

If you want output size in human readable format (e.g. 2048 -> 2.0K), set this option to 1.

You dont have to specify any of those options, which means this is okay:
print File::Size->new()->getsize(), " bytesn";

This is okay too:
print File::Size->new()->setdir( /etc/ )->setblocksize( 1024**2 )->getsize(), " MBn";

setdir

Used to set (or get - if called without parameters) the directory. Example: $obj->setdir( /etc/ );

setblocksize

Used to set (or get - if called without parameters) the block size. Example: $obj->setblocksize( 1024 );

setfollowsymlinks

Used to set if you want to follow symbolic links or not. If called without parmeters, returns the current state. Example: $obj->setfollowsymlinks( 1 );

sethumanreadable

Used to set (or get - if called without parameters) if you want human-readable output sizes. Example: $obj->sethumanreadable( 1 );

getsize

Used to calculate the total size of the directory. Prints output according to the block size you did or didnt specify.

RPM::Util::Files is a Perl module to generate %files list in RPM Specfile.

SYNOPSIS

use RPM::Util::Files;

my $util = RPM::Util::Files->new({
build_root => /var/tmp/some-package-version-root,
docs_filters => [
sub {
my $entry = shift;

return $entry =~ /manuals/;
}
],
config_filters => [
sub {
my $entry = shift;

return $entry =~ /.conf$/;
}
],
});

$util->make_files;
print $util->to_string;

This script blocks advertising banners on the Web. If you have a slow Internet connection, it will speed up your surfing, since the banners are not downloaded from the Internet at all.

Unlike most other similar solutions, BannerFilter does more than simply block advertising graphics. It also blocks advertising frames on a few sites, and automatically closes pop-up windows. A script can automatically download updated data files off the Web, and notify you when a new version is available.

FTimes is a system baselining and evidence collection tool. FTimess primary purpose is to gather and/or develop information about specified directories and files in a manner conducive to intrusion analysis.
FTimes is a lightweight tool in the sense that it doesnt need to be "installed" on a given system to work on that system, it is small enough to fit on a single floppy, and it provides only a command line interface.
Preserving records of all activity that occurs during a snapshot is important for intrusion analysis and evidence admissibility. For this reason, FTimes was designed to log four types of information: configuration settings, progress indicators, metrics, and errors. Output produced by FTimes is delimited text, and therefore, is easily assimilated by a wide variety of existing tools.
FTimes basically implements two general capabilities: file topography and string search. File topography is the process of mapping key attributes of directories and files on a given file system. String search is the process of digging through directories and files on a given file system while looking for a specific sequence of bytes. Respectively, these capabilities are referred to as map mode and dig mode.
FTimes supports two operating environments: workbench and client-server. In the workbench environment, the operator uses FTimes to do things such as examine evidence (e.g., a disk image or files from a compromised system), analyze snapshots for change, search for files that have specific attributes, verify file integrity, and so on. In the client-server environment, the focus shifts from what the operator can do locally to how the operator can efficiently monitor, manage, and aggregate snapshot data for many hosts. In the client-server environment, the primary goal is to move collected data from the host to a centralized system, known as an Integrity Server, in a secure and authenticated fashion. An Integrity Server is a hardened system that has been configured to handle FTimes GET, PING, and PUT HTTP/S requests.
The FTimes distribution contains a script called nph-ftimes.cgi that may be used in conjunction with a Web server to implement a public Integrity Server interface. Deeper topics such as the construction and internal mechanics of an Integrity Server are not addressed here.
Main features:
- FTimes is easy to use and fast! The rest is pure gravy...
- FTimes has been written in C and ported to many popular OSes such as AIX, BSDi, FreeBSD, HP-UX, Linux, Solaris, and Windows 98/ME/NT/2K/XP. FTimes does not require additional runtime support such as a script interpreter (e.g., Perl) or a Virtual Machine (e.g., JVM).
- FTimes does not need to be installed on the clients machine. In many cases it can be run from a floppy or CDROM. Because of this, FTimes can be configured such that it is minimally invasive to the target system. This is important when trying to collect evidence of an attack on a live system.
- FTimes has thorough logging. This helps to increase its credibility and admissibility as evidence because the log information can be used to determine the known or potential error rate of the tool under various conditions. FTimes logs four types of information: configuration settings, progress indicators, metrics, and errors.
- FTimes detects and encodes non-printable characters (e.g., white space, carriage returns, etc.) in filenames. This ensures that your view of the output is not artificially altered by the data you are looking at. The URL encoding scheme used also helps you to quickly focus in on anomalous filenames.
- FTimes detects and processes Alternate Data Streams (ADS) when running on Windows NT/2K/XP systems. This is quite useful in cases where the perpetrator has used Alternate Data Streams to hide tools and information.
- FTimes output is delimited ASCII, and therefore, is conducive to analysis. This output can be assimilated using standard database technology as well as a wide array of existing tools. This makes it more flexible than proprietary database schemes that are essentially opaque to the practitioner. Ultimately, this format yields better analysis results because the practitioner is able to manipulate data freely, and peers may independently verify analysis results. Again, this helps to strengthen its credibility and admissibility as evidence.
- FTimes can be deployed as an enterprise solution with all information being transmitted to and preserved on a hardened Integrity Server. This allows for centralized management of data, and avoids the problem of leaving data exposed on a clients system. Data stored on a clients system is vulnerable to malicious modification or destruction.
- FTimes natively supports client initiated HTTP/HTTPS uploads/downloads. This eliminates the need for boundary devices such as firewalls to have a special inbound connection rules. Furthermore, theres a good chance that existing boundary devices already support the required outbound communications path because it is the same as that needed to browse the Web.
- FTimes provides an efficient string search capability (a.k.a. dig mode). This is particularly useful in investigations when the practitioner has a profile of key words or byte strings that are likely to exist somewhere on the target system.
- FTimes optionally supports device file digging (block/character).
- FTimes output is configurable on a per attribute basis. This allows users to develop data in a way thats best suited to their needs.
- FTimes optionally produces directory hashes. This is a significant analysis advantage in situations where content rarely changes. The advantage is that one hash effectively represents the content of all directories and files contained in a given tree.
- FTimes optionally produces symlink hashes.
- FTimes optionally performs file typing via XMagic. When there are hundreds or thousands of unknown hashes, it is difficult to determine which files may have changed as a result of a malicious act. In these situations, type information can be used to categorize files and prioritize the order in which they are examined.
- FTimes has an extremely fast, tunable compare capability. This enables the practitioner to quickly analyze snapshots and determine change.
Enhancements:
Version 3.8.0 is a minor release of FTimes. Generally, code was cleaned up and refined as necessary. Several bugs have been fixed -- see the ChangeLog for details. This release includes support for SHA256 hashes, include/exclude filters, and a number of additional file systems (DATAPLOW_ZFS, NTFS-3G, NWCOMPAT, UDF). HashDig utilities have been updated to support SHA1 and SHA256 hashes, and the
following tools have been been added to the project:
ftimes-crv2dbi.pl, ftimes-dig2dbi.pl, hashdig-find.pl, and tarmap. Note that documentation is no longer built at release time, and that means your build system must include the necessary tools to create the documentation -- see the Requirements Section in README.INSTALL for additional details. Since SF officially discontinued compile farm support on 2007-02-08, this project is no longer able to build/test releases in the manner and scale that it did before. Unfortunately, this may result in platform-specific issues that go unnoticed until they are discovered by someone in the field.

Bio::NEXUS::DataBlock is a Perl module that represents the deprecated DATA Block in NEXUS file.

SYNOPSIS

$block_object = new Bio::NEXUS::DataBlock($type, $block, $verbose, $taxlabels_ref);

The DataBlock class represents the deprecated Data Block in a NEXUS file. Data Blocks are still used by some prominent programs, unfortunately, although they are essentially the same as a Characters Block and a Taxa Block combined. Data Blocks may be used as input, but are not output by the NEXPL library. For more information on Data Blocks, see the Characters Block documentation.

METHODS

new

Title : new
Usage : block_object = new Bio::NEXUS::CharactersBlock($block_type, $block, $verbose, $taxa);
Function: Creates a new Bio::NEXUS::CharactersBlock object
Returns : Bio::NEXUS::CharactersBlock object
Args : verbose flag (0 or 1), type (string) and the block to parse (string)