Free protection order software for linux

Quick Order provides an ordering system using Java Wireless HTTP Form.
It uses J2ME libraries to submit forms to an HTTP server running PHP and MySQL. It can run on any embedded device that supports Java Wireless, including mobile phones and Palm systems.
It is ideal for making orders in restaurants, point of sale (POS), etc. It supports English and Chinese Big 5 encoding.
Enhancements:
- PASP is used for the server-side language font.
- An HTTP POST method was added to the server.
- A vector is used to allow flexibility of ordered items.

As Plone does not offer this functionality yet, PloneFolderOrder is a solution that works in todays Plone sites. Once integrated into Plone, it will become obsolete for newer versions of Plone, but there are enough Plone sites that need this functionality today to justify this temporary solution.
The difference to other solutions that store order information inside content objects themselves, PloneFolderOder stores order information in Plone Folders (Therefore the name PloneFolderOrder). Storing content order in a Plone Folder is preferable, because when the ordering changes, you only have to change a single object, the Plone Folder itself. The only drawback is that content objects have to query their container to know their place in the order.
The order screen of Plone Folders contains the list of the folders content, and the user can order the content.
The standard Plone views, and most importantly the navigation tree, are respecting the order set by users.
It is a full-fledged Plone product, installable and uninstallable using the QuickInstaller Tool.
Enhancements:
- Bug Correction : restarting zope will not delete the method getParentFromFolder

Teriodic project is a training tool for the periodic table of the elements.

Starting from 1 (hydrogen), it quizzes the abreviations of each element in numerical order.

If you make a mistake, it shows you the next five elements and lets you start again from hydrogen.

Knowing the periodic table makes it possible to estimate what chemicals look like and how they react.

Zerotools project contains a set of tools to aid keeping virtual disks clean (by filling binary zero to those regions which are no longer in "use"). This is done on-the-fly or manually, depending on which tool suits the needs best.

In technical terms the on-the-fly mechanism uses LD_PRELOAD to wrap the unlink library call and zerounlink-wrapper provides a symlink based mechanism to target individual programs so that they will be run using the unlink wrapper. For comparison against other tools, please see the "Other solutions" section.

Please note that zerotools dont compete with various tools that rewrite file contents with "random" data in order to make data retrieval close to impossible. Do not use zerotools for this, or claim that they are good tools for this. Theyre not. (This text was added for people who only read introductions.)

Zerotools are Linux specific, implemented using C and licensed under GNU General Public License (v2). The tools are provided without a warranty of any kind, in the understanding that software bugs do exist and bad things can happen.

Bugs and limitations

There are no known bugs. Known to me at least. Bugs will be fixed based on intelligent reporting by end users or automatically if I have extra time. My email address is at the start of each source file should you feel the need to send patches.
Thread-protection is not yet tested properly. Neither is LFS-requirement (which means that zerotools might not be able to handle files over 2 GiB size on 32-bit architectures). Building or running zerotools on older Linux systems has not been attempted (but will be done as soon as older systems are installed in test environment). User participation in testing is also appreciated.

Testing has been done on many Linux distributions running kernels (2.4 and 2.6) and with glibc versions (2.3.2 to 2.5.3, with vendor patches, so this is advisory information only). Architectures that were tested are x86, x86_64, ia_64, and ppc (32-bit). Other architecture test results are welcome.

zerounlink and zerounlink-wrapper do not work with statically linked executables. This is a limitation in the technique and there are no workarounds (known to me).
One mis-feature exists in zerounlink: when checking whether a file should be zeroed or not, zerounlink doesnt take into account sparse files. If the file is sparse, it would make sense to overwrite only the parts of file which have non-zero content.

This means that zerounlink would have to read through all of the original file and search for the non-zero content first. This would also mean that instead of only writing to the unlinked file, zerounlink would have to read it in as well. This would cause extra I/O operations. Not sure whether special sparse-file support is worth the extra effort and complexity so this feature has not been implemented.

Drop me a note if you think you need it. (The reason for having this feature is to do with how most dynamic virtual disks are implemented. They will allocate real space when any data is written to an vdisk area, even if the writes consist of only binary zeroes. Its a bit silly, but thats how most of them work. This is the same reason why filling the filesystem with a file containing only binary zeroes (with dd or other tool) is not really a good solution to clean up the vdisk.)

When reporting bugs about listings on this web page, please include the listing number and line number of the problematic bit to speed up fixes. For other web-related fixes, try to include two to three word phrase which can be grepped with. Do not send diffs against xhtml.

Tone Deaf project is an online Karaoke game.

It allows users to both upload their own karaoke performances and download other users karaoke performances in order to rate them in various categories.

It uses oggenc to encode all performances before uploading them to the server.

The Prex project is an open source initiative to provide a portable real-time operating system for embedded systems.
This project originally started to make a royalty-free OS for mobile phones and PDA in order to spread open source movement to such proprietary OS field. And now, the project target has been shifted to the wider area of real-time and embedded systems.
Prex is designed specifically for small memory footprint platforms. It is written in C language based on traditional micro-kernel architecture. The Prex kernel provides only fundamental features for task, thread, memory, ipc, exception, and synchronization.
The other basic OS functions, process, file system, application loading, and networking, are provided by the user mode servers. In addition, Prex provides a POSIX emulation layer in order to reuse the existing applications.
Prex is an open source royalty-free OS for mobile phones and PDA.
This design allows system to perform both of the native real-time task and the generic *NIX process simultaneously without degrading the real-time performance. Furthermore, it helps the platform designer to construct OS by choosing suitable server tasks for their target requisition.
Prex is royalty-free software released under BSD License
Main features:
- Task and thread control: preemptive priority scheduling with 256 priority levels
- Memory management: virtual address mapping, shared memory, memory protection, with MMU
- IPC: synchronous message passing among threads, object name space in kernel
- Exception: framework for POSIX signal emulation
- Synchronization: semaphores, condition variables, and mutexes with priority inheritance
- Timers: sleep timers, alarm timers
- Interrupt: nested interrupt service routines, and prioritized interrupt service threads
- Device I/O: minimum synchronous I/O interface
- Real-time: low interrupt latency, high resolution timers, periodic timers, and scheduling quantum control
- Cross platform portability: well defined architecture dependent layer and driver-kernel interface
- Modular design: OS servers and BSP module separated from kernel
- Small memory footprint: kernel size < 25k bytes
- Low power consumption: control of processor idle state, support of DVS (Dynamic Voltage Scaling)
- Disk-less: on-core kernel, no memory page swapping
- Instantly available: minimal OS boot time, system suspend/resume, kernel warm restart
- File systems: VFS framework, RAM/FAT/Flash file systems optimized for embedded systems
- Networking: TCP/IP stack, BSD socket interface
- POSIX emulation: signal, process, file I/O, real-time extensions, pthread, etc
- Debug: event logging, GDB remote debug
Enhancements:
- A file system server was added. arfs, devfs, and ramfs are supported with this version.

Rubilicious project is a set of Del.icio.us bindings for Ruby.

Youll need to create an account at Delicious in order to use Rubilicious. An RDoc-generated API reference is in doc/, and some simple examples are in examples/.