Free production planning software for linux

Flight Navigation Planner project is a tool for making flight plans based on known airports.

Flight Navigation Planner lets you make flight plans based on known airports, navaids, fixes, or cities.

You can use the sectional charts, wacs, or the vector/terrain planning charts.

It calculates headings, winds, time, and fuel. It features Airways-based Auto-Routing, Climb and Descent calculations (a/c type based), Fuel Stop Planning, Auto-Route around MOAS and Restricted Airspace, Hi-Res Weather Radar Overlay, Viewing of current sectional, wac, and IFR charts, the ability to see a route over TFRs, detailed nexrad radar overlays over your routes, Terrain Profiles with cloud ceilings, and the ability to upload flight plans to GPS.

Plan-B is a bootable Linux environment without the need for a hard drive, it runs entirely in ram or from the cd, based on a basic, stripped installation of Red Hat Linux and the fundamental workings of the SuperRescue CD. A list of tools and utilities are also included for projects such as:

* Forensics/Data Recovery
* System/Network Analysis and Security Scanning
* Temporary Network Device/Server
* IDS / NIDS System
* Network Status Report Creation

My reason for its creation came about due to finding other similar projects (SuperRescue CD, Biatchux (F.I.R.E.), Trinux, Knoppix) to be geared toward only a single area of the broad spectrum I was looking for. The first of which (by H. Peter Anvin, the author of Syslinux, Isolinux, and zisofs) was the only one close to the concept I had in mind which is why I chose it as the foundation for this cd. After not finding what I was really looking for, the "All-in-One", I decided the only way to get it was to build one myself.

MRTG::Config is a Perl module for parsing MRTG configuration files.

WARNING

This module, while reliable right now, is still in ALPHA stages of development... The API/methods may change. Behaviors of methods will almost certainly change. The internal structure of data will change, as will many other things.

I will try to always release working versions, but anyone who expects their code that uses this module to continue working shouldnt... until I remove this warning.

SYNOPSIS

Ever have the need to parse an MRTG config file? I have. I needed to parse lots and lots of them. Using the functions built-in to MRTG_lib was too slow, too complex, and used too much RAM and CPU time for my poor web server to handle - and the data structures MRTG_lib built were way more complex than I needed.

MRTG::Config can load and parse MRTG and MRTG-style confiuguration files very quickly, and the parsed directives, targets and values can be located, extracted, and manipulated through an OO interface.

This module is intended to focus on correctly parsing the format of an MRTG configuration, regardless of whether or not the directives and values, etc. are valid for MRTG. I am using both the parsing behavior of MRTG_libs readcfg() function and the description of the format on the MRTG website as my guidelines on how to correctly parse these configuration files. I am still a short way off that goal, but this module is currently being used in a production environment with great success!

PLEA FOR MERCY

I plan on adding to this documentation and making it better organized soon, but Im willing to answer questions directly in the mean time. Also, this is my first module, written in a hurry to appease some disgruntled engineers. I do plan on continuing to improve it, so any input, positive or negative is certainly welcome!

USAGE EXAMPLE

use MRTG::Config;

my $cfgFile = mrtg.cfg;
my $persist_file = mrtg.cfg.db;

my $mrtgCfg = new MRTG::Config;

$mrtgCfg->loadparse($cfgFile);

# Want to store the parsed data for use later or by
# another program?
$mrtgCfg->persist_file($persist_file);
$mrtgCfg->persist(1);

foreach my $tgtName (@{$mrtgCfg->targets()}) {
my $tgtCfg = $mrtgCfg->target($tgtName);
# Lets assume every target has a Title.
print $tgtCfg->{title} . "n";
}

# globals() has some, um, interesting things you
# should know. Please read about it below...
my $globalCfg = $mrtgCfg->globals();

# Lets assume WorkDir is set.
print $globalCfg->{workdir} . "n";

Mergence is a high performance, open source HL7integration engine and application platform. It was developed to fill the need for an open source, fully transactional healthcare integration system capable of handling millions of messages per day, and thousands of concurrent LLP connections. Mergence is based on Apache ServiceMix, a lightweight enterprise service bus which conforms to the JBI standard, and HAPI, an excellent opensource HL7v2 API. We plan to support HL7v3 in the next release.
Mergence is still in heavy development, and documentation is still lacking, but the current release is already production-ready if you dont mind working with some XML. We have a well-tested and solid core in place, which is fully usable. Development of an AJAX administration console is underway and is the main focus of the 2.0 release.
We hope to have more complete documentation available in the next week.
Main features:
- Fully open source, under the GNU General Public License
- Built on standards-based technologies.
- End-to-end persistence with global transactions so no message can ever be lost.
- High-throughput, asynchronous architecture.
- Message vault with encrypted storage (embedded or external DB).
- Flexible message routing and transformation.
- Scriptable using Groovy
- Extensive logging, monitoring, and alerting system.
- Supports active clustering.
- Many bundled connectors, and compatible with any ServiceMix JBI component.
- NIO TCP connectors which can support thousands of concurrent connections.
- Support for processing/transforming flat files of unlimited size.
- Hot deployment of new components and configurations.
- JBI extensions for easily developing new HL7 components.

Building Block ist the Open Source Content Management Software for your website. It is lightweight and has minimal hardware requirements.
At the same time it is powerful and delivers high performance. Building Blocks diversity allows you to create and manage professional web projects directly in your browser.
Enhancements:
- This initial release is stable and is recommended for production use on non-critical data.

mysqlrowcopy is a tool that generates insert statements from result sets. It produces output similar to what might result from running mysqldump on a single SELECT query.

This project helps eliminate some of the tedium of moving data between QA and production MySQL databases.

Build:

To build mysqlrowcopy, you should run:

./configure
make

A mysqlrowcopy and mysqlrowcopy.debug file are created. They have identical functionality, the .debug version simply has debugging symbols built in (for gdb).

Since mysqlrowcopy is probably going to be I/O bound with modest CPU and RAM usage, the only reason to even build a 64-bit version is to work around potential issues in dynamic linking 32-bit binaries against 64-bit libraries.

RECIPES

1. Migrating a MySQL user account reaper from QA server to a production server.

e.g. MySQL database server qa3.example.com to prod1.example.com:

$ mysqlrowcopy -h qa3.example.com
SELECT * FROM db WHERE User = "reaper" mysql db > reaper.sql
$ mysql -h prod1.example.com mysql < reaper.sql

You could of course simply pipe the output of mysqlrowcopy into mysql and skip the intermediate file.

(Dont forget to RELOAD PRIVILEGES afterwards)

2. Keep your test environment up to date. Populate it with production data every 24 hours. You could run this sequence from cron once a day:

$ mysqlrowcopy -h finance-db.example.com
SELECT * FROM stocks WHERE modified > DATE_SUB(NOW(),INTERVAL 24 HOUR)
finance stocks > day-stocks.sql

$ cat day-stocks.sql | mysql -h finance-test.example.com finance

3. Copy data between tables on different servers that have some similar fields.

Youve got common data in table Zip on a production database:

mysql> desc Zip;
+-------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------------+-------------+------+-----+---------+-------+
| ZIPCode | varchar(5) | | PRI | | |
| ZIPCodeType | char(1) | YES | | NULL | |
| City | varchar(32) | YES | | NULL | |
| CityType | char(1) | YES | | NULL | |
| State | varchar(32) | YES | | NULL | |
| StateCode | char(3) | YES | | NULL | |
| AreaCode | char(3) | YES | | NULL | |
| Latitude | varchar(12) | YES | | NULL | |
| Longitude | varchar(12) | YES | | NULL | |
+-------------+-------------+------+-----+---------+-------+
9 rows in set (0.00 sec)

And youve got table ZipPosition in a research database:

mysql> desc ZipPosition;
+-------------+-------------+------+-----+---------+-------+
| Field | Type | Null | Key | Default | Extra |
+-------------+-------------+------+-----+---------+-------+
| ZIPCode | varchar(5) | | | | |
| Latitude | varchar(12) | YES | | NULL | |
| Longitude | varchar(12) | YES | | NULL | |
+-------------+-------------+------+-----+---------+-------+
3 rows in set (0.00 sec)

You want to load data from production Zip into research ZipPosition.

$ mysqlrowcopy -h production SELECT ZIPCode,Latitude,Longitude common ZipPosition > pos.sql
$ cat pos.sql | mysql -h qa research

Note how we specify ZipPosition on the first line to tell mysqlrowcopy what the destination table is going to be.

LazyDragon Gnu/Linux is a Linux distro aimed at video and audio production. Unfortunatly their arent many distributions aimed specifically at Audio/Video editing and production.

So thats where LazyDragon comes in. Currently Chainsaw Linux is one of the only Distributions orientated towards media production, and you have to pay for it ( which should never be the case with Gnu/Linux).

LazyDragon Linux is free and always will be. LazyDragon is an unfunded , free production of free technologies . Only available free for download.