Free clone scripts software for linux

/etc/net represents a new approach to Linux network configuration tasks. /etc/net Scripts is inspired by the limitations of traditional configuration subsystems.
/etc/net provides builtin support for configuration profiles, interface name management, removable device support, full iproute2 command set support, interface dependency resolution, and a QoS configuration framework.
/etc/net provides support for the following interface types: Ethernet, WiFi (WEP), IPv6/IPv6 tunnels, PSK IPSec tunnels, VLAN, PLIP, Ethernet bonding and bridging, traffic equalizer, Pent@NET, usbnet, and PPP.
Due to its modular design, support for new interface types can be added without overall design changes.
Enhancements:
- This release features mostly new features (ip6tables, ebtables, OpenVPN, and tun/tap) and some bugfixes (IP rules, wireless, firewall, and DVB).

Font::Scripts::AP is a Perl module for memory representation of a TTFBuilder Attachment Point database (APDB).

SYNOPSIS

use Font::Scripts::AP;
$ap = Font::Scripts::AP->read_font($ttf_file, $ap_file, %opts);
$ap->make_classes();

INSTANCE VARIABLES

cmap

Reference to the Microsoft cmap within the font.

font

Reference to a font structure. read_font will cause at least the post, cmap, loca, and name tables to be read in.

glyphs

An array of references to glyph data structures, indexed by glyphID. Stucture elements are:

uni

Unicode scalar value, if any, as specified in the APDB. (decimal integer)

gnum

Actual glyph ID from font.

post

Actual Postscript name from font.

Note: The uni, gnum and post values are based on the UID, GID, and PSName fields of the APDB. If there are descrepancies between the APDB and the fonts internal tables, then for calcuating the above three values, priority is given first to UID field, then PSName field, and finally GID.

glyph

Reference to glyph structure read from font.

line

Line number in APDB where glyph is defined.

points

A hash of references to attachment point structures for this glyph, keyed by attachment point type (aka name). Each AP structure contains

name

The name (type in TTFBuilder terminology) of the attachment point

x, y

X and Y coordinates for the attachment point

line

Line number in APDB where this point is defined.

components

Present if the glyph is a composite. Is a reference to an array of component structures. Each component structure includes:

bbox

comma separated list of bounding box coordinates, i.e., x1, y1, x2, y2

uni

Unicode scalar value, if any, of the component. (decimal integer)

Note: The following instance variables contain the actual text read from the APDB. If there are descrepancies between the APDB and the font, these values may differ from corresponding values given above. Therefore these values should not be used except for diagnostic purposes.

UID

Unicode scalar value, if any, as specified in the APDB. (string of hex digits)

PSName

Postscript name, if any, as specified in the APDB

GID

Glyph id, if any, as specified in the APDB

classes

Created by "make_classes", this is a hash keyed by class name returning an array of GIDs for glyphs that are in the class. Classes are identified by extensions (part after a .) on the post name of each glyph. For each such extension, two classes are defined. The first is the class of all glyphs that have that extension (class name is the extension). The second is the class of nominal glyphs corresponding to the glyphs with that extension (class name is the extension but with the prefix no_).

lists

Created by "make_classes", this is a hash keyed by attachment point name (as modified by "make_point") returning an array of GIDs for glyphs that have the given attachment point.

vecs

If defined, this variable will be updated by "make_classes". It is a hash, keyed by attachment point name (as modified by "make_point") returning a bit vec bit array, indexed by GID, each bit set to 1 if the corresponding glyph has the given attachment point.

ligclasses

Optionally created by make_classes if ligatures are requested and they exist. The base forms class is no_code while the ligatures are held in code.

WARNINGS

If -errorfh not set, this accumulates any warning or error messages encountered.

WARNINGS

Count of number fo warnings or errors encountered.

Rains PPP scripts are a set of tools that simplify the use and setup of pppd.
Features include connection time logging, a ppp-off that works right with more than one pppd running, dial-on-demand support for pppd 2.3.x., and more.
Another interesting feature is that the scripts keep track of your connect speed and time, and included is an mirc script to show connection status from a remote machine, as well as a shell script that works for *IX boxes.
Enhancements:
- Made TTL for dyn.db 60 seconds
- --bootup should have been --quiet in ppp-on
- Fixed POSTLOGINSTRING
- Now using low-ascii in the README and ppp-on
- Re-fixed permission problems on /etc/inet.status (I hope)
- Fixed more spelling/grammar

Destiney Scripts Lottery project is a powerball lottery number analyzer and quick picker.
Destiney Scripts Lottery script is a Web application that helps to pick your "lucky" Powerball Lottery numbers.
Random quick picks use statistical logic based on previous winning numbers to inversely weight the results for better "random" picks.
The latest winning Powerball results can be imported as well.
Main features:
- Automated Powerball quick pick.
- Weighted picks based on previous winning numbers
- Import system for latest winning numbers

IPTables Firewall Script contains two example firewall scripts "rc.firewall.iptables. Ive tried here to give some brief documentation for the IPTables firewall scripts contained in this directory. If youre not familiar with IPTables functionality and usage, then you may also want to check out some of the URLs listed at the top of the firewall scripts(HOWTOs, etc).

I hope you find these scripts useful, if you have any comments or suggestions please feel free to email me.

The Finishing Scripts for Cluster Installations handle specific post-installation configuration that might not be convienent nor possible using existing cluster installation methods.

The usual installation process is used to build a reasonably configured node, and the system then reboots into normal mode, achieves network visibility, and executes the finishing script.

The finishing script handles all of the finer details of installing packaged or non-packaged software, tweaking installation, setting host/net specific parameters/files, etc. It is controlled via a single, easily modified script.

Slackware Packaging Scripts provides a collection of scripts for simple automated Slackware packaging.

Slacktools is a collection of simple shell scripts that can be used to build most source tarballs into slackware packages.

They are probably the least advanced of any automated packaging system, but they work surprisingly well for source that supports the DESTDIR variable [correctly].

Scripts provided:

.backoutpkg
.slackconfig
.slackmake
.slackpack

Clone::More is a Perl module that can copy Perl data structures.

SYNOPSIS

use Clone::More qw( clone );

my $structure = [
{ key => value }
];

for my $set ( @$structure ) {
my $clone = clone( $set );

for ( keys %$clone ) {
print "Everything matches" if ( exists( $set->{$_} ) && $set->{$_} eq $clone->{$_} );
}
}

This is intended to act as a utility in order to natively clone data structures via a simple Perl interface. Will ensure that all references will be separated from the parent data strure, yet kept relative to the new structure (if need be).

Please take a look at the WARNINGS, GOTCHAS and FUTURE DEVELOPMENT sections, as resources to see if this module is fully capable of doing everything that you want it to do (and it will do most everything).