Ports Search

U-Boot loader for OrangePi One. To install this bootloader on an sdcard just do : dd if=/usr/local/share/u-boot/u-boot-boardname/u-boot-sunxi-with-spl.bin of=/path/to/sdcarddevice bs=1k seek=8 conv=notrunc,sync This version is patched so that: * ELF and API features are enabled. * The default environment is trimmed to just what's needed to boot. * The saveenv command writes to the file u-boot.env on the FAT partition. * The DTB file name is chosen based on the board model and passed to ubldr.bin using the fdtfile env variable. ubldr.bin loads the DTB from /boot/dtb/ on the FreeBSD partition. * By default, it loads PIE ubldr.bin from file ubldr.bin on the FAT partition to address 0x42000000, and launches it. For information about running FreeBSD on Allwinner boards, see https://wiki.freebsd.org/FreeBSD/arm/Allwinner For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

U-Boot loader for A13 Olinuxino. To install this bootloader on an sdcard just do : dd if=/usr/local/share/u-boot/u-boot-boardname/u-boot-sunxi-with-spl.bin of=/path/to/sdcarddevice bs=1k seek=8 conv=notrunc,sync This version is patched so that: * ELF and API features are enabled. * The default environment is trimmed to just what's needed to boot. * The saveenv command writes to the file u-boot.env on the FAT partition. * The DTB file name is chosen based on the board model and passed to ubldr.bin using the fdtfile env variable. ubldr.bin loads the DTB from /boot/dtb/ on the FreeBSD partition. * By default, it loads PIE ubldr.bin from file ubldr.bin on the FAT partition to address 0x42000000, and launches it. For information about running FreeBSD on Allwinner boards, see https://wiki.freebsd.org/FreeBSD/arm/Allwinner For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

U-Boot loader for Olinuxino Lime. To install this bootloader on an sdcard just do : dd if=/usr/local/share/u-boot/u-boot-boardname/u-boot-sunxi-with-spl.bin of=/path/to/sdcarddevice bs=1k seek=8 conv=notrunc,sync This version is patched so that: * ELF and API features are enabled. * The default environment is trimmed to just what's needed to boot. * The saveenv command writes to the file u-boot.env on the FAT partition. * The DTB file name is chosen based on the board model and passed to ubldr.bin using the fdtfile env variable. ubldr.bin loads the DTB from /boot/dtb/ on the FreeBSD partition. * By default, it loads PIE ubldr.bin from file ubldr.bin on the FAT partition to address 0x42000000, and launches it. For information about running FreeBSD on Allwinner boards, see https://wiki.freebsd.org/FreeBSD/arm/Allwinner For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

The objective of the package is to provide a fast and essential HTML check (esp. for CGI scripts where response time is important) to prevent a piece of user input HTML code from messing up the rest of a file, i.e., to minimize and localize any possible damage created by including a piece of user input HTML text in a dynamic document. HTMLQuickCheck checks for unmatched < and >, unmatched tags and improper nesting, which could ruin the rest of the document. Attributes and elements with optional end tags are not checked, as they should not cause disasters with any decent browsers (they should ignore any unrecognized tags and attributes according to the standard). A piece of HTML that passes HTMLQuickCheck may not necessarily be valid HTML, but it would be very unlikely to screw others but itself. A valid piece of HTML that doesn't pass the HTMLQuickCheck is however very likely to screw many browsers(which are obviously broken in terms of strict conformance). HTMLQuickCheck currently supports HTML 1.0, 2.x (draft), 3.0 (draft) and netscape extensions (1.1).

RDF.rb is a pure-Ruby library for working with Resource Description Framework (RDF) data. Features: * 100% pure Ruby with minimal dependencies and no bloat. * Fully compatible with RDF 1.1 specifications. * 100% free and unencumbered public domain software. * Provides a clean, well-designed RDF object model and related APIs. * Supports parsing and serializing N-Triples and N-Quads out of the box, with more serialization format support available through add-on extensions. * Includes in-memory graph and repository implementations, with more storage adapter support available through add-on extensions. * Implements basic graph pattern (BGP) query evaluation. * Plays nice with others: entirely contained in the RDF module, and does not modify any of Ruby's core classes or standard library. * Based entirely on Ruby's autoloading, meaning that you can generally make use of any one part of the library without needing to load up the rest. * Compatible with Ruby Ruby 2.x, Rubinius and JRuby 1.7+ (in Ruby 2.0 mode). * Performs auto-detection of input to select appropriate Reader class if one can not be determined from file characteristics.

Aewm is a modern, minimal window manager for X11. It is controlled entirely with the mouse, but contains no visible UI apart from window frames. It builds complex operations by chaining together primitives aewm does not try to do everything; there are plenty of better clients for defining hotkeys, menus, setting your background image, etc. Aewm makes it easy for you to keep the edges of the root window unobscured, so that you have essentially infinite space to click without having to aim (this principle is based on Fitts's Law). There is intentionally no panel or dock to get in the way. Aewm does not make decisions about where your windows should go. It can be used as an ordinary overlapping window manager, but is powerful enough to let you "tile" windows ad hoc if you prefer; maximizing space usage and removing overlaps are basic commands. You can also optionally take control of window mapping and change where windows will appear (including stacking and tiling) before they are actually shown. This port installs not only the window manager, but also the aemenu and aepanel applets. These provide a list of windows by title (vertically for aemenu, horizontally for aepanel) and a menu from which programs may be run.

This utility can be used to test performance of storage devices. First, one need to generate file with I/O operations: # set mediasize=`diskinfo /dev/<device> | awk '{print $3}'` # set sectorsize=`diskinfo /dev/<device> | awk '{print $2}'` # raidtest genfile -s $mediasize -S $sectorsize -n 50000 It will generate test which contains 50000 I/O requests with random size and random offset. Size is a multiple of sectorsize, but less than or equal to 128kB (maxium size of I/O request). I/O request type (READ or WRITE) is random as well. All test data are stored in 'raidtest.data' file in current working directory. To run test, one should type: # raidtest test -d /dev/<device> -n 10 This command will read test data from 'raidtest.data' file, run 10 processes which will be used to send requests to the given device in parallel. When test is finished you will see statistics: Bytes per second: <x> Requests per second: <y> If you compare performance of two storage devices, use the same data file! usage: raidtest genfile [-frw] <-s mediasize> [-S sectorsize] <-n nrequests> [file] raidtest test [-Rrw] <-d device> [-n processes] [file] where: -d device path to tested device -f if raidtest.data file or specified file already exists, remove it and create new one -n nrequests number of requests to generate -n processes number of processes to run -r generate/run only READ requests -R generate random data for write requests -s size of destination device -S sector size of destination device -w generate/run only WRITE requests file path to the data file instead of default 'raidtest.data'

This qjail version only supports the RELEASE-10.x series of releases. Qjail [ q = quick ] is a 4th generation wrapper for the basic chroot jail system that includes security and performance enhancements. Plus a new level of "user friendliness" enhancements dealing with deploying just a few jails or large scale jail environments consisting of 100's of jails. Qjail uses the jail(8) jail.conf method. This provides the ability to enable the following options on a per-jail basis. exec.fib, securelevel, allow.sysvipc, devfs_rulesets, allow.raw_sockets, allow.quotas, allow.mount.nullfs, allow.mount.tmpfs, allow.mount.zfs, vnet.interface, and vnet. The vnet option gives a jail its own network stack using the experimental vimage kernel module. The vnet option has only been tested on i386 and amd64 equipment. Qjail requires no knowledge of the jail command usage. It uses "nullfs" for read-only system executables, sharing one copy of them with all the jails. Uses "mdconfig" to create sparse image jails. Sparse image jails provide a method to limit the total disk space a jail can consume, while only occupying the physical disk space of the sum size of the files in the image jail. Ability to assign ip address with their network device name, so aliases are auto created on jail start and auto removed on jail stop. Ability to create "ZONE"s of identical qjail systems, each with their own group of jails. Ability to designate a portion of the jail name as a group prefix so the command being executed will apply to only those jail names matching that prefix. Qjail has been incorporated into the Finch open source project, see http://dreamcat4.github.io/finch/ for details.