Free b 1.8 software for linux

Oak::Web::HTML::B is B HTML Tag.

HIERARCHY

Oak::Object
Oak::Persistent
Oak::Component
Oak::Web::Visual
Oak::Web::HTML::PhraseElement
Oak::Web::HTML::B

PROPERTIES

The Oak::Web::HTML::B object has the following properties:
caption

The text inside the tag

All other defined by W3C.

This component will use all the available properties following the rules of HTML4.01

Blam is a tool that helps you keep track of the growing number of news feeds distributed as RSS. Blam lets you subscribe to any number of feeds and provides an easy to use and clean interface to stay up to date.
Enhancements:
- Support for RSS and RDF feeds
- Very easy to use interface
- Print the news entries you like
- Automatically update the feeds at regular intervals

B::C is Perl compilers C backend.

SYNOPSIS

perl -MO=C[,OPTIONS] foo.pl

This compiler backend takes Perl source and generates C source code corresponding to the internal structures that perl uses to run your program. When the generated C source is compiled and run, it cuts out the time which perl would have taken to load and parse your program into its internal semi-compiled form. That means that compiling with this backend will not help improve the runtime execution speed of your program but may improve the start-up time. Depending on the environment in which your program runs this may be either a help or a hindrance.

OPTIONS

If there are any non-option arguments, they are taken to be names of objects to be saved (probably doesnt work properly yet). Without extra arguments, it saves the main program.

-ofilename

Output to filename instead of STDOUT

-v

Verbose compilation (currently gives a few compilation statistics).

--

Force end of options

-uPackname

Force apparently unused subs from package Packname to be compiled. This allows programs to use eval "foo()" even when sub foo is never seen to be used at compile time. The down side is that any subs which really are never used also have code generated. This option is necessary, for example, if you have a signal handler foo which you initialise with $SIG{BAR} = "foo". A better fix, though, is just to change it to $SIG{BAR} = &foo. You can have multiple -u options. The compiler tries to figure out which packages may possibly have subs in which need compiling but the current version doesnt do it very well. In particular, it is confused by nested packages (i.e. of the form A::B) where package A does not contain any subs.

-D

Debug options (concatenated or separate flags like perl -D).

-Do

OPs, prints each OP as its processed

-Dc

COPs, prints COPs as processed (incl. file & line num)

-DA

prints AV information on saving

-DC

prints CV information on saving

-DM

prints MAGIC information on saving

-f

Force options/optimisations on or off one at a time. You can explicitly disable an option using -fno-option. All options default to disabled.

-fcog

Copy-on-grow: PVs declared and initialised statically.

-fsave-data

Save package::DATA filehandles ( only available with PerlIO ).

-fppaddr

Optimize the initialization of op_ppaddr.

-fwarn-sv

Optimize the initialization of cop_warnings.

-fuse-script-name

Use the script name instead of the program name as $0.

-fsave-sig-hash

Save compile-time modifications to the %SIG hash.

-On

Optimisation level (n = 0, 1, 2, ...). -O means -O1.

-O0

Disable all optimizations.

-O1

Enable -fcog.

-O2

Enable -fppaddr, -fwarn-sv.

-llimit

Some C compilers impose an arbitrary limit on the length of string constants (e.g. 2048 characters for Microsoft Visual C++). The -llimit options tells the C backend not to generate string literals exceeding that limit.

Plan/B is a network aware file backup system specifically designed to make the backup of files from multiple machines to a variety of devices simple.
The system provides features such as comprehensive reporting, the ability to use CDROM (and soon DVD) drives across the network, as well as centralised management.
Plan/B can be deployed on Windows and Linux systems.
Main features:
General
- Backup anything, to anywhere: You can use any kind of device that plasticine knows about (currently CDROM, Local disk, Network share, FTP device) as either a source or destination. There is no limitation (as there is in DataArmour).
- Multiple sources, Multiple Destinations: A backup may source its files from multiple machines and devices. The destinations for a backup job can also be any number of machines or devices. Thus it is now easy to have a single set of files (documents, code or other important assets) copied to more than one location using a single job. No need to clone a job anymore!
- Multi-Platform: As the system is written in Java, it will work with any machine for which there is a VM (this is true for the backup server and agents). The administration console can be run on either a Linux or Windows machine (when SWT, the GUI framework used for the console matures on OsX, the console will be able to run on that OS as well)
- Volume spanning: If any removable destination is out of space, then it is possible to request the next volume during the backup process. A good example of this is backup to multiple CDs. Plasticine supports both the spanning of single files across multiple media, and also the saving of complete files across different media. In the first case, a large file can be split across two volumes. In the second case, only complete files are written to any volume (obviously, if the file is larger than the size of the volume, it will have to be split up).
- Flexible selection: A single job can backup whatever is deemed important to the user. The files to backup are specified by rules, which can be as simple as include everything, and complex as include all word documents, all excel spreadsheets under my docs directory, and everything NOT ending in .bak under the data directory
- Flexible scheduler: Jobs can be run whenever you like. The current scheduling implementation takes on a form very similar to Cron, but other implementations are easily added. The important point here is that the process of deciding when a backup should be run is completely separated from anything else about the backup job. This is a change from DataArmour, where the scheduling (specifically, the weekly incremental backup job scheduling) is fixed to run on a Monday, with a full backup occurring every week. In Plasticine, user defined schedules are possible.
- Statistics: The system emits various statistics while in operation, including current progress of various jobs, jobs in the run queue, current load, and recent logged events.
Enterprise
- Reliable:The remote agents are resilient to network failure. If a server cannot be contacted, they will move into a discovery mode until the server is back up. No configuration is required!
- Painless installation: The system is very easy to install - just run the included windows installer and tell it what kind of install you want. All services are configured automatically.
- Administration Console: The backup server is a separate process, which is administered via a GUI console. The console can be run from any machine, and can control and manage the settings for the backup server and any client. That means you can configure everything from one place.
Enhancements:
- This release added an option to specify that the destination location should be deleted prior to the backup occuring.
- It also added an option to copy full folders and specify whether or not to create an absolute or relative backup.
- Completion was sped up by detaching the email sending from the job completion process.
- Warnings are now used to log more in the reports for situations that are not necessarily fatal.
- When adding a source or destination, the file browser is now automatically opened for you.
- It is now possible to have multiple email recipients for a backup report.

xbindkeys is a program that allows you to launch shell commands with your keyboard or your mouse under X Window.
xbindkeys links commands to keys or mouse buttons, using a configuration file. Its independant of the window manager and can capture all keyboard keys (ex: Power, Wake...).
usage: [--version|-V] [--defaults|-d] [--file|-f file] [--help|-h] [--display|-X display-name] [--vebose|-v] [--show|-s] [--key|-k] [--multikey|-mk] [--geometry|-g geom]
-V, --version Print version and exit
-d, --defaults Print a default rc file
-f, --file Use an alternative rc file
-h, --help This help!
-X, --display Set X display to use
-v, --verbose More information on xbindkeys when it run
-s, --show Show the actual keybinding
-k, --key Identify one key pressed
-mk, --multikey Identify multi key pressed
-g, --geometry size and position of window open with -k|-mk option
-n, --nodaemon dont start as daemon
Installation
Download the source (See the download section).
Open a text console (for example, xterm).
Change to the directory into which you downloaded the source.
cd source_download_directory
Uncompress the source :
tar xzvf xbindkeys-1.x.x.tar.gz
Change to the new directory (created by tar) :
cd xbindkeys-1.x.x
Compile the program :
make
Install the program (as root if necessary) :
su root
make install
exit
Configure the program :
see the Configuration section.
You can now use xbindkeys by typing :
xbindkeys &
or by loading it automatically when X starts up by adding the preceeding line to the file $HOME/.xsession.
On Mandrake (and maybe Redhat), this method doesnt works.
Instead you can use : Configuration -> Gnome -> Advanced -> Session -> Startup Programs on Mandrake
or Gnome menu -> Settings -> Session -> Session Properties on Redhat.
Enhancements:
- Correction of typos in the man page.
- An emphasis is made on the documentation about the Guile/Scheme configuration file (the preferred way for non-trivial configuration, and far more powerful than the default configuration file).

B::Lint module contains Perl lint.

SYNOPSIS

perl -MO=Lint[,OPTIONS] foo.pl

The B::Lint module is equivalent to an extended version of the -w option of perl. It is named after the program lint which carries out a similar process for C programs.

OPTIONS AND LINT CHECKS

Option words are separated by commas (not whitespace) and follow the usual conventions of compiler backend options. Following any options (indicated by a leading -) come lint check arguments. Each such argument (apart from the special all and none options) is a word representing one possible lint check (turning on that check) or is no-foo (turning off that check). Before processing the check arguments, a standard list of checks is turned on. Later options override earlier ones. Available options are:

magic-diamond

Produces a warning whenever the magic readline is used. Internally it uses perls two-argument open which itself treats filenames with special characters specially. This could allow interestingly named files to have unexpected effects when reading.

% touch rm *|
% perl -pe 1

The above creates a file named rm *|. When perl opens it with it actually executes the shell program rm *. This makes dangerous to use carelessly.

context

Produces a warning whenever an array is used in an implicit scalar context. For example, both of the lines

$foo = length(@bar);
$foo = @bar;

will elicit a warning. Using an explicit scalar() silences the warning. For example,

$foo = scalar(@bar);

implicit-read and implicit-write

These options produce a warning whenever an operation implicitly reads or (respectively) writes to one of Perls special variables. For example, implicit-read will warn about these:

/foo/;

and implicit-write will warn about these:

s/foo/bar/;

Both implicit-read and implicit-write warn about this:

for (@a) { ... }

bare-subs

This option warns whenever a bareword is implicitly quoted, but is also the name of a subroutine in the current package. Typical mistakes that it will trap are:

use constant foo => bar;
@a = ( foo => 1 );
$b{foo} = 2;

Neither of these will do what a naive user would expect.

dollar-underscore

This option warns whenever $_ is used either explicitly anywhere or as the implicit argument of a print statement.

private-names

This option warns on each use of any variable, subroutine or method name that lives in a non-current package but begins with an underscore ("_"). Warnings arent issued for the special case of the single character name "_" by itself (e.g. $_ and @_).

undefined-subs

This option warns whenever an undefined subroutine is invoked. This option will only catch explicitly invoked subroutines such as foo() and not indirect invocations such as &$subref() or $obj->meth(). Note that some programs or modules delay definition of subs until runtime by means of the AUTOLOAD mechanism.

regexp-variables

This option warns whenever one of the regexp variables $`, $& or $ is used. Any occurrence of any of these variables in your program can slow your whole program down. See perlre for details.

all

Turn all warnings on.

none

Turn all warnings off.

mod_ldap is a synthesis of two older LDAP modules.