Free embedded software for linux

X-Bone dynamically deploys and manages Internet overlays to reduce their configuration effort and increase network component sharing.
X-Bone discovers, configures, and monitors network resources to create overlays over existing IP networks.
It uses two-layer IP-in-IP tunneled overlays and supports existing applications and unmodified routing, multicast, and DNS services in unmodified operating systems. X-Bone also support IPsec within overlays.
Enhancements:
- This is an integrated distribution of FreeBSD 4.9 with X-Bone 3.2, including utilities and dependencies installed and preconfigured.

Embedded Slackware is a software development kit for the automated creation of bootable embedded systems based on Slackware and Busybox. The focus is on i486 and ARM systems that use compact flash devices (handhelds and PC104 type boards). The distribution consists of a primary archive with tools, scripts, and documentation, and additional archives for the i486 and PXA250 binary components.
Enhancements:
- This update includes 2.4.34 and 2.6.20 embedded kernels.
- 44 easy-to-use burn scripts and runtime configurations are available.
- The distribution archive is an i486 working subset of the full distribution.
- The complete SDK consists of 5 base archives each for i486, uclibc_i486, pxa255, and uclibc_pxa255 architectures.
- Additional archives are also available for gcc, Wine, and Opie/Pixil LCD desktops.

2-Disk X window embedded Linux is a very efficient Linux/xwindows distribution, implementing a net centric operating environment and user friendly GUI
The distribution is intended to be a demonstration of Mungkie assiciates embedded appliance development environment, showing the sort of environment that can be created for small appliance GUI systems using less than 4Mb flash and 4Mb RAM.
The embedded development environment is based around a standard source tree containing all the required utilities for a standard POSIX unix implementation with a number of XML based GUI configuration and compilation tools. Simple GUI utilities are used to configure required components and set compilation options.
The distribution is targeted as a base for:
corporate users to reduce IT costs by deploying X terminals on old or low cost hardware
Or:
embedded OS for handhelds, settop boxes, or communications devices, with full support for bluetooth, wifi, internet, and MMS protocols
Or:
Hobbyist or small companies to develop specialist applications for cheap commodity hardware
Main features:
- kernel 2.0.x/2.2.x/2.4.x
- libc-2.1/libc5/uclibc,
- tcp/ip network support. full protocol stack for wifi, mms
- busybox 0.62,
- tinylogin 1.0,
- ppp, chat, some daemons, inetd, crond. dhcp client and server. iptables
- e3 editor,
- X window system 4.1 vesa
- VNC client
- merlin character recognition
- rdesktop remote windows client
- ssh
- Mungwm : a window manager
- Mungbrowse : a web browser
- Mungterm : a terminal program
- Mungames : a collection of 12 games
- Mungedit : a text editor
- Mungfile : embedded file manager
- NEW Evil bastard operator tools
- NEW Cheese dynamics context apropriation modeling
- NEW Mini Mung beans (beans of mung for all your network environment)
Enhancements:
- Script cleanups were done to the build system.
- Bugs were fixed concerning HTTPS access with the Mweb browser.

EmbedCover is a script for embedding album cover images in MP3 files. EmbedCover script will automatically look up the image associated to it in amaroK and embed this image in the file.

The MP3 file must have an ID3-V2 tag, otherwise the script will abort, and the file must be in your Collection.

It is recommended that you back up your MP3 file before using this script on it.

Although the script is designed not to harm your file, the operation is not reversible and should therefore be used with caution.

Future versions will also be able to remove embedded cover images from a file.

StreamDownloader is a Web interface to mplayer. It allows the user to record realaudio and other mplayer compatible streams from the net for personal use. Recordings can be scheduled, stopped, and downloaded.
This couple of scripts was written to download Real Audio streams from the net and listen them later.
Testing was done on my TurboSLUG (a Linux embedded box) and on a full Linux box.
This program is still alpha stage, and it is not intended to run on a public server, its just for personal use.
Language:
- Italian
- English

SQL::Statement::Embed can embed a SQL engine in a DBD or module.

SQL::Statement is designed to be easy to embed in other modules and to be especially easy to embed in DBI drivers. It provides a SQL Engine and the other module needs to then provide a data source and a storage mechanism. For example, the DBD::CSV module uses SQL::Statement as an embedded SQL engine by implementing a file-based data source and by using DBI as the user interface. Similarly DBD::Amazon uses SQL::Statement as its SQL engine, provides its own extensions to the supported SQL syntax, and uses on-the-fly searches of Amazon.com as its data source.

SQL::Statement is the basis for eight existing DBDs (DBI database drivers). If you have a new data source, you too can create a DBD without having to reinvent the SQL wheel. Its fun, its easy, become a DBD author today!

SQL::Statement can be also be embedded without DBI. Well explore that first since developing a DBD uses most of the same methods and techniques.

The role of SQL::Statement subclasses

SQL::Statement provides a SQL parsing and execution engine. It does not provide a data source or storage mechanism other than in-memory tables. The DBD::File module is a subclass of SQL::Statement that provides access to file-based storage mechanisms. Its quite possible to use things other than files as data souces, in which case we wouldnt use DBD::File, instead wed replace DBD::Files methods with our own. In the examples below, well use DBD::File, replacing only a few methods.

SQL::Statement provides SQL parsing and evaluation and DBD::File provides file-based storage. The only thing missing is a data source - what we actually want to store and query. As an example suppose we are going to create a subclass called Foo that will provide as a data source a simple file similar to a passwd file - one record per line, fields separated by colons, with only three fields "username, uid, gid".

Consider what needs to happen to perform a SELECT query on our Foo data:

* recieve a SQL string
* parse the SQL string into a request structure
* open the table(s) specified in the request
* define column names and postions for the table
* read rows from the table
* convert the rows from colon-separated format into perl arrays
* match the columns and rows against the requested selection criteria
* return requested rows and columns to the user

To perform operations like INSERT and DELETE, we also need to:

* convert rows from perl arrays into colon-separated format
* write rows
* delete rows

SQL::Statement takes care of all of the SQL parsing and evaluation. DBD::File takes care of file opening, reading, writing, and deleting. So the only things Foo is really responsible for are:

* define column names and postions for the table
* convert rows from colon-separated format into perl arrays
* convert rows from perl arrays into colon-separated format

In SQL::Statement subclasses these responsibilities are assigned to two objects, a ::Statement object is responsible for opening the table, defining the column names and positions, and for creating new ::Table objects. A ::Table object is responsible for reading, converting, writing, and deleting data.