Free b software for linux

jE6-B project is an emulator of some of the functionality of the E6B Flight Computer.

This program was inspired by the similar application called Virtual E6-B written by Jesse Kempa. However that application does not seem to have been updated for some time and was based on Visual Basic, so is only for Windows (without emulation).

As I am a very keen Python user, I decided to write an Open Source Cross-Platform version of the features provided by this previous program in that language. This is my first open source project, so this program is very much a learning exercise for me. After a little playing with the various GUI toolkits available, I decided to write the program actually in Jython (a Java implementation of Python - see www.jython.org), which would make use of the Java Swing GUI toolset and also the cross-platform advantages offered by Java.

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.

B-Chat is a small application which allows you to chat on Battle.net.

It has no fancy GUI interface (yet :-), but I have plans for making it Gnome compliant.

However, at the moment it works pretty much like the regular UNIX telnet client, with the lines that are being sent and received mixed into eachother.

It can make it hard to read at times, but it serves my purpose.

I started work on this client because I wanted a way to chat with my friends on Battle.net while I was on Linux.

I really didnt feel like rebooting to Windows just to run TopazChat or ScumBot (I dont like Wine either :-), so I decided to code my own chat client.

The client is still in its early stages, so its very rough and may be hard to use. You have to supply the name o the Battle.net server that you are going to be connecting to. This will change in the future.

MySysop is a PHP tool with AJAX support for managing MySQL server settings and monitoring process, variables, and status.
Enhancements:
- This version has a prototype window for the dialog window, new stats, and minor bugfixes.

B::CC is Perl compilers optimized C translation backend.

SYNOPSIS

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

This compiler backend takes Perl source and generates C source code corresponding to the flow of your program. In other words, this backend is somewhat a "real" compiler in the sense that many people think about compilers. Note however that, currently, it is a very poor compiler in that although it generates (mostly, or at least sometimes) correct code, it performs relatively few optimisations. This will change as the compiler develops. The result is that running an executable compiled with this backend may start up more quickly than running the original Perl program (a feature shared by the C compiler backend--see B::C) and may also execute slightly faster. This is by no means a good optimising compiler--yet.

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.

-mModulename

Instead of generating source for a runnable executable, generate source for an XSUB module. The boot_Modulename function (which DynaLoader can look for) does the appropriate initialisation and runs the main part of the Perl source that is being compiled.

-D

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

-Dr

Writes debugging output to STDERR just as its about to write to the programs runtime (otherwise writes debugging info as comments in its C output).

-DO

Outputs each OP as its compiled

-Ds

Outputs the contents of the shadow stack at each OP

-Dp

Outputs the contents of the shadow pad of lexicals as its loaded for each sub or the main program.

-Dq

Outputs the name of each fake PP function in the queue as its about to process it.

-Dl

Output the filename and line number of each original line of Perl code as its processed (pp_nextstate).

-Dt

Outputs timing information of compilation stages.

-f

Force optimisations on or off one at a time.

-ffreetmps-each-bblock

Delays FREETMPS from the end of each statement to the end of the each basic block.

-ffreetmps-each-loop

Delays FREETMPS from the end of each statement to the end of the group of basic blocks forming a loop. At most one of the freetmps-each-* options can be used.

-fomit-taint

Omits generating code for handling perls tainting mechanism.

-On

Optimisation level (n = 0, 1, 2, ...). -O means -O1. Currently, -O1 sets -ffreetmps-each-bblock and -O2 sets -ffreetmps-each-loop.

B::Flags is a Perl module that provides a friendlier flags for B.

SYNOPSIS

use B::Flags;
print B::main_root->flagspv;
print B::main_root->privatepv;
print $some_b_sv_object->flagspv;

By default, $foo->flags when passed an object in the B class will produce a relatively meaningless number, which one would need to grovel through the Perl source code in order to do anything useful with.

This module adds flagspv to the SV and op classes and privatepv to the op classes, which makes them easier to understand.

Warning: This module is not guaranteed compatible with any version of Perl below 5.7.0; however, Id like to make it so compatible, so if it fails to compile, mail me. Theres probably an #ifdef I need to add somewhere...

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.