Free to promote software for linux

Script Promotion Wizard is a free online tool you can add to your web site or use on your local server to add your script to script directories.
Since an automated solution to script promotion is probably impossible due to the lack of a standard submission process for script directories, we came up with what we think is the next best thing.
Main features:
- Easy to install. Just unzip and upload, or if youre using it on a local server, just unzip!
- Save program profiles for later use.
- Completely customizable! Add new scripts to promote through simple XML interface.
- Add new script directories to the Script Promotion Wizard by adding a simple entry into an XML file.
- Copying and pasting values into the online forms is as easy as we could possibly make it. You only have to click, copy, click and paste. No messy highlighting required.
- Best of all, Script Promotion Wizard is completely free!

Bio::Root::Object is a core Perl 5 object.

SYNOPSIS

# Use this module as the root of your inheritance tree.
Object Creation
require Bio::Root::Object;

$dad = new Bio::Root::Object();
$son = new Bio::Root::Object(-name => Junior,
-parent => $dad,
-make => full);
See the new() method for a complete description of parameters. See also the USAGE section .

Bio::Root::Object attempts to encapsulate the "core" Perl5 object: What are the key data and behaviors ALL (or at least most) Perl5 objects should have?
Rationale

Use of Bio::Root::Object.pm within the Bioperl framework facilitates operational consistency across the different modules defined within the Bio:: namespace. Not all objects need to derive from Bio::Root::Object.pm. However, when generating lots of different types of potentially complex objects which should all conform to a set of basic expectations, this module may be handy.

At the very least, this module saves you from re-writing the new() method for each module you develop. It also permits consistent and robust handling of -tag => value method arguments via the Bio::Root::RootI::_rearrange() method and provides a object-oriented way handle exceptions and warnings via the Bio::Root::Root::throw() and Bio::Root::Root::warn() methods.

See the APPENDIX section for some other handy methods.

Fault-Tolerant Objects

A major motivation for this module was to promote the creation of robust, fault-tolerant Perl5 objects. The Bio::Root::Root::throw() method relies on Perls built-in eval{}/die exception mechanism to generate fatal exceptions. The data comprising an exception is managed by the Bio::Root::Err.pm module, which essentially allows the data thrown by a die() event to be wrapped into an object that can be easily examined and possibly re-thrown.

The intent here is three-fold:

1 Detailed error reporting.
Allow objects to report detailed information about the error condition (who, what, where, why, how).
2 Handle complex errors in objects.
The goal is to make it relatively painless to detect and handle the wide variety of errors possible with a complex Perl object. Perls error handling mechanism is a might clunky when it comes to handling complex errors within complex objects, but it is improving.
3 Efficient & easy exception handling.
To enable robust exception handling without incurring a significant performance penalty in the resulting code. Ideally, exception handling code should be transparent to the cpu until and unless an exception arises.

These goals may at times be at odds and we are not claiming to have achieved the perfect balance. Ultimately, we want self- sufficient object-oriented systems able to deal with their own errors. This area should improve as the module, and Perl, evolve. One possible modification might be to utilize Graham Barrs Error.pm module or Torsten Ekedahls Experimental::Exception.pm module (see "Other Exception Modules").

Technologies such as these may eventually be incorporated into future releases of Perl. The exception handling used by Bio::Root::Object.pm can be expected to change as Perls exception handling mechanism evolves.

TERMINOLOGY NOTE: In this discussion and elsewhere in this module, the terms "Exception" and "Error" are used interchangeably to mean "something unexpected occurred" either as a result of incorrect user input or faulty internal processing.

MySQL PHP to PostgreSQL is an application that takes a php page that uses mysql calls and changes them into PostgreSQL calls.
This allows any website (if it converts properly) that was written in PHP for MySQL to run as a website written to run on PostgreSQL.
- Step 1: Download and uncompress
To uncompress simply type: tar xvzf mysqlphp2postgres.tar.gz
If youre on a non-GNU system you might have to type: gzip -dc mysqlphp2postgres.tar.gz | tar xvf -
- Step 2: Compile
To compile simply type: make
If youre on a non-GNU system youll have to edit the make file to change the compiler to cc instead of gcc
- Step 3: Install
Type: make install
This will simply copy the binary file to /usr/local/bin/
- Step 4: Convert
Type: mysqlphp2postgres inputfile.php outputfile.php
The input file is the php page that uses mysql. The outfile is the page you want to create. You will probably need to tell mysqlphp2postgres the name of the postgreSQL database since mysql_select_db doesnt translate. You can do this by using a -d switch. So if, for example, the database youre connecting to is called blah, you could type: mysqlphp2postgres -d blah inputfile.php outputfile.php
Problems:
I have had the following problems from using this program:
MySQL has a lot more functions in PHP than PostgreSQL that do more things. I havent had a problem with any unsupported functions in my programs, but someone probably will. If you want to help write code for this to support those functions (if thats even possible) feel free to help.
Enhancements:
- Fixed some stuff.
- Cleaned up some code.
- This program now produces code optomized for PHP 4.1.0 and above.

Booting Ubuntu To RAM is an article aims to document the process of creating a customized Ubuntu that loads an image from the hard disk to RAM, then boots an entire Ubuntu session out of RAM. It is intended for intermediate to advanced Ubuntu users who are familiar with the shell, and may have limited experience customizing the livecd (LiveCDCustomization) and shell scripting. We will customize a LiveCD and copy it to the hard drive, and make a few modifications to bootup scripts so that it copies to RAM via our good friend tmpfs.
WARNING: The author asserts that this procedure works for him, but cannot guarantee that this procedure works for anyone else. Although this procedure is meant to be 100% safe, it is feasible that there may be mistakes, or a chance of misunderstanding the instructions in a manner that causes loss of data. Please make a backup and do not attempt on mission critical systems. Read through this article thoroughly, and do not attempt if you do not comprehend or feel comfortable about any of the instructions!
CAUTION: I hope this is intuitively obvious, but Ill humor you and state it bluntly: Changes you make under the live session are NOT saved and WILL BE LOST when you reboot or shut down. Dont save anything important to the "home directory" and expect it to still be around! If you want to save data permanently, mount a permanent medium (such as your hard drive), plug in a thumbdrive, or use some network functionality built into Ubuntu to save your data to a non-volatile destination.
There are many cases where one would like to boot Ubuntu to RAM:
- Performance: The desktop performance is dramatically improved. A 400MB squashed filesystem in RAM, that holds 1200MB of data, is read back on a 1.6GHz Core Duo in about 3 seconds, including decompression time.
- Power, Noise, Durability: Although modern hard disks dont use much power compared to other system components, this may still be important for some. In laptops, hard disks are often the noisiest components, so this setup can reduce system noise. With the hard disk spun down, a laptop can potentially withstand greater shocks without damage.
- Abrupt poweroff: Since the hard disk is only momentarily used in read-only mode during boot, then never touched again, there are few or no negative consequences of an abrupt poweroff. If a system is used where power is inconsistent, or the system is regularly used in a context where fast shutoffs are required, this is very handy.
- Privacy: Anything you do in this session are lost when you reboot or power off. This is great for kiosks or other systems where permanent modification are not desired. (Note that by default the livecd user has full sudo access, so potentially a malicious user can still make permanent changes by mounting the hard drive and following this HOWTO)

Add to Noatun playlist is a service menu that can add files to the Noatun players playlist.

Test::LectroTest is a Perl module with easy, automatic, specification-based tests.

SYNOPSIS

#!/usr/bin/perl -w

use MyModule; # contains code we want to test
use Test::LectroTest;

Property {
##[ x "my_function output is non-negative" ;

Property { ... }, name => "yet another property" ;

# more properties to check here

This module provides a simple (yet full featured) interface to LectroTest, an automated, specification-based testing system for Perl. To use it, declare properties that specify the expected behavior of your software. LectroTest then checks your software to see whether those properties hold.
Declare properties using the Property function, which takes a block of code and promotes it to a Test::LectroTest::Property:

Property {
##[ x "my_function output is non-negative" ;

The first part of the block must contain a generator-binding declaration. For example:

##[ x<<less