Free 2.0 firmware software for linux

OpenPCD is a free and open RFID reader reference design platform. The OpenPCD firmware is software that runs in OpenPCDs AT91SAM7 ARM controller, and connects the RFID reader hardware (CL RC632 ASIC) with the Host PC via USB. The Firmware includes a custom USB device stack and drivers for the various embedded AT91SAM7 components. The firmware itself does not run on Linux, but it only works with a Linux host PC talking to it.
OpenPCD is a free hardware design for Proximity Coupling Devices (PCD) based on 13,56MHz communication. This device is able to screen informations from Proximity Integrated Circuit Cards (PICC) conforming to vendor-independent standards such as ISO 14443, ISO 15693 as well as proprietary protocols such as Mifare Classic. Contactless cards like these are for example used in the new electronic passports.
The intention of the OpenPCD project is to offer the users full hardware control of the RFID signal and to provide different output signals for screening the communication. With already existing Free Software from the OpenMRTD project for implementing the PCD side protocol stack of various RFID protocols, this project will happily extend the free toolchain around RFID verification.
Enhancements:
- This is the initial version of the firmware.
- It supports basic RFID reader functionality for the ISO14443A.

picoSQL project is the first Italian Open Source relational database management system.
The project of picoSQL was born in 1995. It was an ODBC driver for COBOL indexed files. It consisted of a DLL written in C++ on Windows 3.1 operating system. In the beginning the main effort was made in order to obtain a good compatibity with existing front-end (mainly the MS-Access, MS-Query and VisualBasic) and in order to see COBOL files as a normalized relational DB.
The obtained success concurs to develop ulteriorly the product, refining the query optimizer and implementing an extended SQL, to exclusion of the DDL (Data Description Language). A later version, called PicoDB, were devoloped on UNIX system in client/server architecture.
PicoSql is released under GPL license; it derives from PicoDB (that remains a Picosoft proprietary product) with the addition of some SQL-DDL statement (CREATE/DROP TABLE(INDEX) and excluding COBOL files compatibility). The C/C++ library that allow the database access from C/C++ programs using the ODBC 2.5 API is released under LGPL license; this allows to link the library with programs that are not under GPL.
PicoSQL can be used from Windows applications (like MS-ACCESS, MS-Query, VB etc.) in client/server modality using the ODBC driver picoSQLNet. It can moreover be used from appropriate Java programs through the JDBC driver comprised in the distribution. Finally it can be used from programs written in C and C++ through its set of ODBC 2.5 compliant API.
PicoSQL lacks at the moment of some common characteristics to the most common RDBMS (like the schema and catalogue concepts and the management of the user permissions who can be obtained anyway using the permissions of the host operating system) but they are just these lacks to make it particularly simple to install and to use and fast in the logons and the queries.
Installation:
The installation is particularly simple: if you have the binary distribution, is sufficient to extract the compressed files in one directory ( under Windows NT/2000/XP) and execute:
startTestDb.sh (Unix/Linux)
PicoSQL consists fundamentally in a program, picosqld, to activate through inetd (or xinetd) or picoserv. In such a way it becomes a net service binded to a port, that is to a entire number comprised between 1 and 65535; this number (as an example 6789) must always be specified on the command line of picosqld. As an example:
picosqld 6789
For the activation with inetd (or xinetd), you must see the relative documentation. picoserv is a simple program that replaces inetd, mainly for scopes of test or debugging: its usage is the following:
picoserv [-f] commandLine portNumber
In our case the activation of picosqld can be obtained with the following command line:
picoserv "picosqld 6789" 6789
To notice as the port number is specified two times, as an argument of picosqld and as an argument of picoserv.
When picosqld receive a connection request, it reads a configuration file to find the necessary informations. This file is a text file on Unix/Linux systems.
# Unix/Lunixthe file read for configuration is
$HOME/.picosql.ini
or, if this file is missing
/etc/picosql.ini
The file consists of sections and parameters. A section begins with the name of the section in square brackets and continues until the next section begins. Sections contain attributes of the form
name=value
The file is line-based - that is, each newline-terminated line represents either a comment, a section name or a parameter. Section and parameter names are not case sensitive. Only the first equals sign in a parameter is significant. Any line beginning with a semicolon (;) or a hash (#) character is ignored, as are lines containing only whitespace. Each section corresponds to a database and comprises information like user, password and DB location. In the following example there are two database declared, the former called picoSqlTest, is accessible by anyone while the latter, called rubrica is accessible only by user pico giving the appropriate password.
[picoSqlTest]
DataDirectory=/home/test.db
[rubrica]
DataDirectory=/home/rubrica.db
User=pico
Password=soft
PicoOdbcTrace=NO
SuspensiveLock=YES
; for picosql client only
server=localhost
port=6789
Enhancements:
- This version fixes a problem on authentication and a bug when the connection fails.

KCad is a screensaver for KDE 3, based on KCad 1.1 (a old screensaver for Kde 2.2). KCad is a KDE Control+Alt+Canc screensaver.

KCAD is a very simple screensaver for KDE. In fact, it may remind you of certain OTHER evil screensavers. This was designed so that you can "trick" your Boss (in the BOFH sense) into thinking that youre running Windows NT on your workstation/server, even if you are running (insert UNIX clone name here). By default, it looks very KDE-ish, but you can make it look more convincing by putting the following text into the file $HOME/.kde/share/config/kcad.kssrc.

Installation:

./configure --prefix=/path/to/kde --with-qt-includes=/path/to/qt-includes
make all
su
make install
exit


NOTE:
- KUbuntu prefix is /usr

WmG applet is a dockapp plugin for Gaim. That is, once the plugin is started a dockapp appears, which can be conviniently dragged to the windowmaker dock.
The dockapp shows the top 3 buddies from Gaim, sorted by whatever algorithm was selected in the Gaim preferences. Clicking either of the buddies causes a new conversation window to be created for that buddy (unless one already exists, in which case the existing one will be used).
Additionally, the dockapp features a scrolling message thingy, which displays events occurring, such as buddies logging on and off, becoming idle, going away or coming back.
WmG was selected as the name of this program, because WmGaim was already spoken for.
Version restrictions:
- Unloading the plugin unfortunately requires a restart of gaim.
- No protocol mini-icons are available for protocols other than msn and icq
Enhancements:
- This release fixes compilation issues with the latest Gaim betas, and introduces some graphical representation of buddy status for ICQ buddies.

HyperWRT is a power boost firmware for the Linksys WRT54G and WRT54GS router. HyperWRT goal is to add a limited set of features to the last Linksys firmware, extending its possibilities but staying close to the official firmware.
HyperWRT is based on Linksys 3.03.6 firmware for the WRT54G and Linksys 3.37.6 firmware for the WRT54GS.
HyperWRT will work on these hardware versions :
WRT54G : V1, V1.1, V2, V2.2, V3
WRT54GS : V1, V1.1, V2
Main features:
- Adjustable Transmit Power & Antenna Select
- 13 Wireless Channels
- Boot Wait flash protection
- Increased Port Forwarding & Triggering Fields
- Increased Qos Device & Application Fields
- Increased Access Restrictions Policies & Blocked Services Fields
- Command Shell
- Telnet Daemon
- Startup & Firewall Scripts
- Uptime

Umicons provides Icons for KDE!
I have convertet in many hours over 2500 icons for KDE.
There are many icons which arent used by KDE. Just take a look in the folders.
Many thanks to mattahan, the creator of the icons, for his agreement to convert this icons for KDE.
Window-Decoration and style is "Plastik".
Enhancements:
- Many, many new icons (the most are NOT used by KDE so look intothe folders for personal use).
- Now over 700 different icons. See the screenshots.
- 3 wallpapers included (also the one from my screenshots).

pBeans project is a Object/Relational (O/R) database mapping layer. It is designed to be simple to use and automated.
The idea is that you save time and effort by simply focusing on writing Java classes, and not worrying about maintenance of matching SQL scripts, schema evolution, XML based schemas, or generating code. The pBeans framework takes care of persisting JavaBeans with little assistance from the developer.
Main features:
- Automatic Table Creation and Schema Evolution- Tables corresponding to JavaBean classes are created on demand. Field types are based, by default, on JavaBean compile-time types. Field type changes and new fields are detected. Manually changing tables (user-managed mode) is also supported.
- Based on Annotated JavaBeans- You define a getter and setter for each bean property. Persisent bean classes only need to be tagged with a @PersistentClass annotation.
- Transitive Persistence- If object A is persisted and it refers to Persistent object B, then object B is automatically persisted. If Persistent object C also refers to B, and C is also persisted, the record for object B in the database is not duplicated.
- Instance Consistency- If you retrieve an object from persistent storage that is already known to exist in main memory, you get a reference to the object in main memory. (Garbage collection is allowed to happen via weak references.)
- Near-Zero Configuration- There is no need to define schemas or anything of the sort in a language other than Java, and there are no code generation steps of any kind. No XML or SQL need to be written, except the necessary to create a database and grant user permissions. However, you can instruct pBeans to let you manage database modifications manually.
- Database features- Transactions and auto-increment IDs (MySQL only) are now supported.
- Flexibility- Via annotations users are allowed to define their own table and field names, the name of the primary key, whether fields are nullable, whether tables are user-managed (not automatically modified), table indexes, unique or otherwise, whether unused fields should be deleted, whether a field is nullable, whether it is renamed from another field (to prevent loss of data when a property is renamed), etc.
- Servlet support- A pBeans store may be easily configured using servlet context parameters (see ServletAccess.)