Ports Search

A simple, intuitive C++ library to handle JSON serialized data.

This is the last version that handles both the 8.x and 9.x install media formats. 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 jail environments consisting of 100's of jails. Qjail requires no knowledge of the jail command usage. It uses "nullfs" for read-only system binaries, 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.

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.

This qjail version only supports RELEASE-11.0 and newer. 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.

tolua++ is an extended version of tolua, a tool to integrate C/C++ code with Lua. tolua++ includes new features oriented to c++ such as: * Support for std::string as a basic type (this can be turned off by a command line option). * Support for class templates As well as other features and bugfixes. tolua is a tool that greatly simplifies the integration of C/C++ code with Lua. Based on a cleaned header file (or extracts from real header files), tolua automatically generates the binding code to access C/C++ features from Lua. Using Lua API and tag method facilities, tolua maps C/C++ constants, external variables, functions, classes, and methods to Lua.

This is a utility that implements ECM extraction from MPEG-2 TS stream and MULTI2 decoding specified in ARIB STD-B25 (an ISDB conditional access system used in Japan). PC/SC interface is used for extracting Ks key from a B-CAS card.

A-A-P is an Open Source build tool. It does everything that make does in a better way. Includes Internet access for uploading and downloading files. Integrated CVS support: obtain a module from a CVS server and check changes into a CVS server. Can be used to build programs, maintain web sites, distribute software, download and install an application, etc.

The program forwards all IMAP traffic between the client and the server, but keeps the connection to the server alive after the client logs out. When the same user attempts to log in again, the proxy will use the cached username/password pair to authenticate the client, and tie the new client to the old server connection (which was kept alive). Lasse L. Johnsen lasse@freebsdcluster.org

DocBook W3C XML Schema.

Fractal Flames are algorithmically generated images and animations. The shape of each image is specified by a long string of numbers - a genetic code of sorts. You can create your own flames with the Apophysis interactive designer (for windows), Qosmic (for Linux), or Oxidizer (for Mac OS X), or Apophysis-J (cross- platform in Java). Or you can use the Electric Sheep distributed screen saver to join the collective evolution of animated fractal flames.