Ports Search

szap-s2 is a command line channel zapping (i.e. tuning) utility similar to szap but including support for S2API a.k.a. DVB API version 5, which supports DVB-S2. When using szap-s2, one instructs it to change the channel to one of a list of channels supplied in a channels.conf type file. There is no manpage yet, but you can run szap-s2 without args to get a usage message. location of channel list file is ~/.szap/channels.conf one line of the szap channel file has the following format: name:frequency_MHz:polarization[coderate][delivery][modulation][rolloff]:sat_no:symbolrate:vpid:apid:service_id one line of the VDR channel file has the following format: name:frequency_MHz:polarization[coderate][delivery][modulation][rolloff]:sat_no:symbolrate:vpid:apid:tpid:?:service_id:?:?:?

The EXTended RECordings MENU plugin provides additional functions to VDR's recordings menu: * renaming recordings and directories * moving recordings and directories, also between different filesystems * adjustable display of recording's length, date and size * directories are always shown on top of the list * reworked layout using icons for showing the status of list entries (directory, new recording, moving recording/directory, cutting recording, dvd archiv entry) * extended recordings info menu, shows name, path, channel, size, lifetime and priority of the recording * free disk space is shown for the filesystem of the current directory * sorting by name or date, adjustable for each directory; type of sorting will be stored * ascending/descending sorting * extends VDR's '-r'-option commands with 'move' and 'rename' * functionality of the DVDArchive-patch (see below) * protecting recordings in co-work with the PIN-plugin * a cutter queue

ICMPINFO: icmpinfo is a tool for looking at the ICMP messages received on the running host. The source code comes from an heavily modified BSD ping source. USAGE: icmpinfo o Gives info about weird packets only [mainly icmp_unreachable]. icmpinfo -v o Gives info about all ICMP packets [that includes your own traceroutes...] except pings (icmp_echo_reply). icmpinfo -vv o To see pings too. icmpinfo -vvv o Will add an ascci/hexa dump of the packet. icmpinfo -n o Avoids name queries (faster, lighter). icmpinfo -p o Avoids port number to service name queries (faster, lighter). icmpinfo -s o Also decode the ip_src field which is the address of the interface receiving the packet. This option is not usefull for hosts with a single network interface. icmpinfo -l o Run like a daemon (forks) and output to SYSLOG. (It now checks that you are root for that)

Frontier::RPC implements UserLand Software's XML RPC (Remote Procedure Calls using Extensible Markup Language). Frontier::RPC includes both a client module for making requests to a server and a daemon module for implementing servers. Frontier::RPC uses RPC2 format messages. RPC client connections are made by creating instances of Frontier::Client objects that record the server name, and then issuing `call' requests that send a method name and parameters to the server. RPC daemons are mini-HTTP servers (using HTTP::Daemon from the `libwww' Perl module). Daemons are created by first defining the procedures you want to make available to RPC and then passing a list of those procedures as you create the Frontier::Daemon object. The Frontier::RPC2 module implements the encoding and decoding of XML RPC requests using the XML::Parser Perl module.

Is this module just like Net::FTP? No it is not! 1. It is a subclass and not a new class that uses Net::FTP underneath. That means the object is a normal Net::FTP object and has all the methods Net::FTP has. 2. It does not override Net::FTP methods (IE does not have methods the same name as Net::FTP) which means you don't have to sort through how the function differs from the standard version in the Net::FTP module. 3. Its waaaay simpler to use without a bunch of weird config stuff to cloud the issue, odd hard to remember arguments, obscure methods to replace valid existing ones that are part of Net::FTP, or new methods that are badly named (IE think "grep" on this one). There are other things as well. 4. It follows the paradigm of Perl name spaces, objects, and general good practice much better and in a way that is more intuitive and expandable.

viewglob is an utility designed to complement the Unix shell in graphical environments. It has two parts: 1. A tool that sits as a layer between the shell and X terminal, keeping track of the user's current directory and command line. 2. A graphical display which shows the layouts of directories referenced on the command line (including pwd). The display reveals the results of file globs and expansions as they are typed (hence the name), highlighting selected files and potential name completions. It can also be used as a surrogate terminal, where keystrokes typed in the display are passed to the shell. Files and directories can be double-clicked to insert their names and/or paths into the terminal.

On FreeBSD, it's possible to allow plain users to mount filesystems without using su or sudo. This is enabled via vfs.usermount sysctl. However, if file name conversion is used when mounting a filesystem, in most cases mount will fail with `mount_XXX: XXX_iconv: Operation not permitted denied' error. This is caused by the fact that character set conversion tables need to be loaded into kernel, but, apart from mounting, that's not allowed to plain users, because charset tables are large enough to initiate a denial of service by filling kernel memory with many tables. This utility allows you to load only specific charset tables into kernel, so usermounts with file name conversions won't fail and in the same time it's not possible to bring the system down by filling kernel memory.

chyves is a bhyve front-end manager. chyves manages type-2 virtualized guests by utilizing hardware virtualization on a base FreeBSD 10.3+ installation. On a base install, only FreeBSD guests can run. However, with the installation of sysutils/grub2-bhyve and sysutils/bhyve-firmware from ports or pkg, most other OSes can run as a guest, including Windows. See DEPENDENCIES section in the man page for more information. chyves is targeted for beginners as well as power users. Beginners should find chyves relatively easy to use with lots of documentation and demonstrations. While power users should find utility with features such as true ZFS clones, PCI passthrough, rapid execution against many guests, disk images, and snapshot reverted states on boot/reboot to name a few of the advanced features. The name 'chyves' is the pluralized, big endian alphabetic increment of bhyve. 'chyves' is pronounced like 'chives', part of the Allium genus. The onion is also in the Allium genus.

The Apache::ConfigParser module is used to load an Apache configuration file to allow programs to determine Apache's configuration directives and contexts. The resulting object contains a tree based structure using the Apache::ConfigParser::Directive class, which is a subclass of Tree::DAG_node, so all of the methods that enable tree based searches and modifications from Tree::DAG_Node are also available. The tree structure is used to represent the ability to nest sections, such as <VirtualHost>, <Directory>, etc. Apache does a great job of checking Apache configuration files for errors and this modules leaves most of that to Apache. This module does minimal configuration file checking. The module currently checks for: Start and end context names match The module checks if the start and end context names match. If the end context name does not match the start context name, then it is ignored. The module does not even check if the configuration contexts have valid names.

Ruby on Rails has a nice feature to create nested parameters that help with the organization of data in a form - parameters can be an arbitrarily deep nested structure. The way this structure is denoted is that when you construct a form the field names have a special syntax which is parsed. This plugin supports two syntaxes: dot notation <input name="foo.bar.gorch" /> subscript notation <input name="foo[bar][gorch]" /> When reading query parameters from $c->req you can now access all the items starting with "foo" as one entity using $c->req->param('foo');. Each subitem, denoted by either the dot or the square brackets, will be returned as a further deeper hashref.