Polar POS is a point of sale system that integrates support for biometric readers, electronic shelf labels, RF terminals, time attendance, payroll, automatic ordering and re-ordering, price changes, inventory management, and promotions management. It uses the MATE desktop environment and provides additional security through checksums and sandboxing. Hardware from NCR, IBM, Datalogic, Honeywell, CherryPOS, AdvanPOS, Logic Hardware, and others are supported using OPOS drivers.
netwmpager is an enhanced version of the original netwmpager-1.11 program written around 2005 by Timo Hirvonen. It should be compliant with the EWMH (or NetWM) specifications. This version implements virtual desktops split into different viewports, into different desks, or both, while the earlier version only supported desks. As a consequence, netwmpager-2 should work with most window managers; it has been tested especially with compiz, fluxbox, and fvwm. It also has many parametrizable features, and it implements a convenient zoom.
Antony is an off-line and cross platform tool for organizing and sharing photos that makes it possible for a group of peers to keep a common photo, image, or picture collection current and synchronized. Users can tag images (year, event name, event place, or event type, photographer, people, comments). Images are stored in a local file system, and tags are stored in an SQLite database. To identify images, their MD5 sum is used, which makes it possible for users to merge collections. Images can be searched using tags, and images and metadata can be exported to a folder. A thumbnail representation and a zooming image viewer are provided.
tpe-lkm is a Linux kernel module implementing Trusted Path Execution, a security feature that denies users from executing programs that are not owned by root, or are writable. This closes the door on a whole category of exploits where a malicious user tries to execute his or her own code to hack the system. Since the module doesn't use any kind of ACLs, it works out of the box with no configuration. It isn't complicated to test or deploy to current production systems. The module also has a few other grsecurity-inspired features implemented as "extras".
DUST (Driver UpdateS Tool) is designed to "just work" for building kernel driver modules. The concept is similar to DKMS, though this has the benefit of being simpler, easier to test and use, and easier to integrate. DUST enables you to package up a driver pack, install it into the dust directory, and prepare for upgrading. Each driver pack has 3 components: an install file (populates a tree with stuff needed to build a working driver); the driver payload (tarball, zip file, etc.); and the update script, which will do nothing but copy the old driver kernel modules to a backup directory, build/install a new copy of the driver kernel, run depmod if needed, and mkinitramfs, mkinitrd, or dracut if needed. The install file is very trivial. It is easy to recode this as an RPM or deb. As long as it moves the driver payload and update script to the right location, you can use any mechanism to do this.