Ports Search

periscope is a subtitles searching module written in python that tries to find a correct match for a given video file. The goal behind periscope is that it will only return only correct subtitles so that you can simply relax and enjoy your video without having to double-check that the subtitles match your video before watching it. This is done by using as much info as available from your file and on the websites. Some websites allow you to use hash of the files, the size/length of the video or the exact file name. As a python module, periscope should be easily integrated in many projects that allow plugins to be written in python. The fact that the plugin is shared between all the applications means that separate application and their plugin (file browser, video player, media center application, ...) don't have to maintain the code to search, parse and download subtitles and the user preference about languages. The subtitles websites are handled as plugins.

Freenet6 is an IPv6 access service offered for free to the community. This service enables thousands of people from all over the world to experience the best solution for a smooth and incremental deployment of IPv6. Freenet6 users can get IPv6 connectivity from anywhere, including from behind any NAT device or from outside of their home network. On Freenet6, a single, permanent IPv6 address and a DNS name are assigned to each user, making their PC reachable from anywhere on the IPv6 internet. A full /48 prefix may also be assigned to a router, enabling the distribution of IPv6 connectivity to an entire network. Freenet 6 - Get Connected For Free! Instead of a Web interface, which is usually offered by traditional tunnel brokers, Freenet6 uses an innovative model based on a client/server architecture. The Gateway6 Client is software that usually runs on a PC and that implements the Tunnel Setup Protocol (TSP). The Gateway6 Client is used to automatically negotiate a configured tunnel between a PC or router and the Freenet6 tunnel broker, making IPv6 easy to install and maintain. The Gateway6 Client source code is licensed under the GPL. A commercial license is also available.

With the exponential growth of the Internet, a central Whois database that provides host and network information of systems connected to the Internet, and electronic mail (email) addresses of the users of those systems has proven to be very inefficient. The sheer size and effort needed to maintain a centralized database necessitates an alternate, decentralized approach to storing and retrieving this information. RWhois is a Directory Services protocol which extends and enhances the Whois concept in a hierarchical and scaleable fashion. It focuses on the distribution of "network objects"--the data representing Internet resources or people--and uses the inherently hierarchical nature of these network objects (domain names, Internet Protocol (IP) networks, email addresses) to more accurately discover the requested information. RWhois synthesizes concepts from other, established Internet protocols to create a more useful way to find resources across the Internet. The RWhois protocol and architecture derive a great deal of structure from the Domain Name System (DNS) [RFC 1034] and borrow directory service concepts from other directory service efforts, primarily [X.500]. The protocol is also influenced by earlier established Internet protocols, such as the Simple Mail Transport Protocol (SMTP) [RFC 821] for response codes.

Bytes::Random::Secure provides two interfaces for obtaining crypto-quality random bytes. The simple interface is built around plain functions. For greater control over the Random Number Generator's seeding, there is an Object Oriented interface that provides much more flexibility. The "functions" interface provides functions that can be used any time you need a string of a specific number of random bytes. The random bytes are available as simple strings, or as hex-digits, Quoted Printable, or MIME Base64. There are equivalent methods available from the OO interface, plus a few others. This module can be a drop-in replacement for Bytes::Random, with the primary enhancement of using a cryptographic-quality random number generator to create the random data. The random_bytes function emulates the user interface of Bytes::Random's function by the same name. But with Bytes::Random::Secure the random number generator comes from Math::Random::ISAAC, and is suitable for cryptographic purposes. The harder problem to solve is how to seed the generator. This module uses Crypt::Random::Seed to generate the initial seeds for Math::Random::ISAAC.

This is the UFS2 version of ffsrecov, heavily (and I do mean _heavily_) based on John-Mark Gurney's program of the same name. It does basically the same thing, only it's a little more resistant to crashes caused by bad pointers, offsets and the like, and it does a little more than his did. Don't contact him for problems with this program, it's definitely _my_ fault if it breaks. This program is not ready for prime time. It has some shortfalls, it has a bunch of new options that are mostly undocumented and the manpage could stand to be rewritten. One _good_ thing is that it now uses the libufs library and is therefore not as dependent on carrying around low-level code. On the other hand, it worked for me. Using this tool, I was able to recover almost all of a several-hundred-gigabyte file system that had been stomped by a misconfigured RAID controller. (That's why I wrote the thing in the first place, in fact.) With the right knowledge and a lot of patience, it is possible to recover most or all of a trashed file system, at least if it's not _too_ trashed. I'm releasing it under the Berkeley two-clause license in the hope that someone with more time will pick it up, polish it and make something a little more useful out of it. Frank Mayhar frank@exit.com

This script provides functionality for manipulating collections of configuration files which can be organised so as to alter the personality of a system. Initially, the "base" personality is established. This personality contains the "reference" copies of configuration files, and is used when creating new personalities. The files which are currently considered part of the system's personality are those contained in the base personality. A new personality is established by making a copy of the base personality under a new name. Each personality maintains a separate copy of all configuration files under /etc/personality. To install a new personality, the files currently in place are saved back to the current personality as indicated in /etc/personality/current, and the files for the new personality copied into place. The 'select' and 'menu' commands which perform these installations are implemented in such a fashion as to only require the tools available on the root filesystem, so that they may be invoked at the earliest stage during system startup.

U-Boot loader for BeagleBone and BeagleBone Black. To install this bootloader, copy the files MLO and bb-uboot.img to the FAT partition on an SD card or the eMMC. Normally this is partition 1, but different partitions can be set with U-Boot environment variables. 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 uboot.env on the FAT partition. * The DTB file name is chosen based on the board model and passed to ubldr using the fdtfile env variable. ubldr loads the DTB from /boot/dtb/ on the FreeBSD partition. * By default, it loads ELF ubldr from file bbubldr on the FAT partition to address 0x88000000, and launches it. Note: prefixing the boot files with 'bb' allows building images with boot bits for more than one board. For information about running FreeBSD on BeagleBone or BeagleBone Black, see https://wiki.freebsd.org/FreeBSD/arm/BeagleBone For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

U-Boot loader for Gumstix Duovero. To install this bootloader, copy the files MLO and u-boot.img to the FAT partition on an SD card. Normally this is partition 1, but different partitions can be set with U-Boot environment variables. 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 uboot.env on the FAT partition. * The DTB file name is passed to ubldr using the fdtfile env variable. The default is omap4-duovero-parlor.dtb for a Parlor expansion board. ubldr loads the DTB from /boot/dtb/ on the FreeBSD partition. (Not tested) * By default, it loads ELF ubldr from file ubldr on the FAT partition to address 0x88000000, and launches it. For information about running FreeBSD on Duovero, see https://wiki.freebsd.org/FreeBSD/arm/Duovero For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

U-Boot loader for Olimex A20 SOM EVB. 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 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