Ports Search

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.