Ports Search

More and more people are posting binary files to usenet these days. Because of limitations in the type data that usenet can accommodate, binaries must be encoded into text, and because binary files are commonly very large relative to text files usenet was designed to handle, they frequently must be broken up into pieces. aub, which stands for "assemble usenet binaries", automates the reassembly process for you. aub determines whether or not any new binaries have appeared in selected newsgroups since the last time it was run, and if so, retrieves, organizes and decodes them, depositing them in a configurable location. This process requires no human intervention once aub has been configured. aub also keeps track of binaries which it has seen some, but not all, of the pieces of. It remembers how to find these old pieces, so that when new, previously missing pieces arrive at your site, it will build the entire binary the next time it is run. It also remembers which binaries it has already seen all of the pieces of already, so that it does not waste time rebuilding the same binaries over and over again. run: ``aub -M | more'' for the long form documentation, or ``aub -m | more'' for the short form.

GSview is a graphical interface for Ghostscript. (Ghostscript is an interpreter for the PostScript page description language used by laser printers.) For documents following the Adobe PostScript Document Structuring Conventions, GSview allows selected pages to be viewed or printed. Features include: * Display and print PostScript and PDF files. * View pages in arbitrary order (Next, Previous, Goto). * Page size and Orientation are automatically selected from DSC comments or can be selected using the menu. * Print selected pages using Ghostscript. * Convert pages to bitmap, PDF or PostScript. * Selectable display resolution, depth, alpha. * Single button zoom. * Extract selected pages to another file. * Copy display bitmap to clipboard, and save clipboard bitmap as BMP file. * Add bitmap or user preview to EPS file (Interchange, TIFF or Windows Metafile) * Graphically select and show bounding box for EPS file. * Extract bitmap preview or PostScript from DOS EPS file. * Extract text or search for text. * Can read gzip and bzip2 compressed PostScript and PDF files. * On-line help. * English, Catalan, Dutch, French, German, Greek, Italian, Russian, Slovak, Spanish and Swedish languages.

Sst can be used to connect to SSL-encrypted network ser- vices or it can be used as an SSL front-end to network servers. Sst can be used interactively, or in an inetd setting, or it can be embedded inside other programs (eg. Amanda). One of the main goals of sst is to be as basic as possible so in most non-embedded cases sst uses netcat to setup the networking I/O. Sst uses a socketpair(2) pipe to stay in contact with its netcat child process. In this way sst only has to concern itself with file descriptors. In the embedded mode sst expects the parent program to set up the networking I/O and to provide the appropriate file descriptors. In embedded client mode ("-c"), clear data is read from (or written to) stdin (fildes 0) and SSL- encrypted data is read from (or written to) stdout (fildes 1). In embedded server mode ("-s"), SSL-encrypted data is read from (or written to) stdin and clear data read from (or written to) stdout.

libretto-config - Libretto BIOS Setting Program The `libretto-config' is a utility program to configure the BIOS setting of the mini notebook computer, Toshiba Libretto. Changes to the setting are immediately done, so rebooting is not necessary. I don't know whether these programs work on any other machines but Libretto. In case of Toshiba's notebook machines, some function may work. *** Disclaimer ***************************************************** The information used to write these programs was obtained by analyzing Libretto individually, not provided by Toshiba. Therefore, they might contain fatal bugs and might cause damages to your Libretto. You can use them freely but the authors are not responsible for the programs. Redistribution of the programs are not restricted, but you must attach this caution and the source. ******************************************************************** The original program were written by Mr. Iizuka (PXN02133@niftyserve.or.jp), which rewrite the CMOS setting directly. Mr. Nomura (GBB00111@niftyserve.or.jp) have extended the program to support SMI and BIOS calling. Thanks. I, Ishioka, combined programs to the package. If you have any troubles, bug reports, or requests, please notify me.

U-Boot loader for SolidRun Cubox-i and Hummingboard. Install the u-boot.imx file onto the boot disk using: dd if=u-boot.imx of=/dev/whatever bs=1k oseek=1 conv=sync The U-Boot built by this port expects the first 1MB of the boot media to be reserved for the U-Boot executable and saved environment. The u-boot.imx file begins at an offset of 1K from the start of the boot disk. The U-Boot environment area begins at an offset of 512K. This version is patched so that: * ELF and API features are enabled to support ubldr. The sources for this port were originally obtained from commit e4bc4c3ebe at https://github.com/SolidRun/u-boot-imx6 which appears to be a highly modified fork of the stock U-Boot 2013.10 release. As of this writing, the changes in this fork have not been rolled back into upstream U-Boot. 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 Utilite and Utilite Pro Install the cm-fx6-firmware file onto the boot disk using: dd if=cm-fx6-firmware of=/dev/whatever bs=1k skip=1 seek=1 oflag=dsync The U-Boot built by this port expects the first 1MB of the boot media to be reserved for the U-Boot executable and saved environment. The firmware file begins at an offset of 1K from the start of the boot disk. The U-Boot environment area begins at an offset of 512K. This version is patched so that: * ELF and API features are enabled to support ubldr. * A single U-Boot image supports Utilite and Utilite Pro. * When the selected board has multiple SD or MMC devices available, the mmc0 device in U-Boot (and thus the disk0 device in loader(8)) will be whichever device U-Boot was loaded from by the ROM bootloader routines. The sources for this port are based on stock U-Boot 2015.07 with patches provided by CompuLab at: http://www.compulab.co.il/wp-content/uploads/2015/10/u-boot-2015.07.tar.bz2 For general information about U-Boot see WWW: http://www.denx.de/wiki/U-Boot

This module strips scripting constructs out of HTML, leaving as much non-scripting markup in place as possible. This allows web applications to display HTML originating from an untrusted source without introducing XSS (cross site scripting) vulnerabilities. You will probably use HTML::StripScripts::Parser rather than using this module directly. The process is based on whitelists of tags, attributes and attribute values. This approach is the most secure against disguised scripting constructs hidden in malicious HTML documents. As well as removing scripting constructs, this module ensures that there is a matching end for each start tag, and that the tags are properly nested. Previously, in order to customise the output, you needed to subclass HTML::StripScripts and override methods. Now, most customisation can be done through the Rules option provided to new(). (See examples/declaration/ and examples/tags/ for cases where subclassing is necessary.) The HTML document must be parsed into start tags, end tags and text before it can be filtered by this module. Use either HTML::StripScripts::Parser or HTML::StripScripts::Regex instead if you want to input an unparsed HTML document.

The LWP::Protocol::https module provide support for using https schemed URLs with LWP. This module is a plug-in to the LWP protocol handling, so you don't use it directly. Once the module is installed LWP is able to access sites using HTTP over SSL/TLS. If hostname verification is requested by LWP::UserAgent's ssl_opts, and neither SSL_ca_file nor SSL_ca_path is set, then SSL_ca_file is implied to be the one provided by Mozilla::CA. If the Mozilla::CA module isn't available SSL requests will fail. Either install this module, set up an alternative SSL_ca_file or disable hostname verification. This module used to be bundled with the libwww-perl, but it was unbundled in v6.02 in order to be able to declare its dependencies properly for the CPAN tool-chain. Applications that need https support can just declare their dependency on LWP::Protocol::https and will no longer need to know what underlying modules to install.

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'