Free build scripts software for linux

The vii-ppp-scripts are yet another set of ppp scripts. They feature handling multiple ISPs, autosetting DNS from ISP, ability to have a different resolv.conf for each connection, phone billing and chatscripts.
It is lacking of:
Graphical interface
Friendly set-up
Explicit multiple modem support
Main features:
- No need to set nameservers manually; either get them automatically from the ISP (/etc/ppp/dns-resolvconf-up) or use a local named (/etc/ppp/dns-named-up)
- Support for multiple ISPs; nameservers can be manually set separately for each if theyre not given (/etc/ppp/dns-resolvconf-up)
- More or less setup for UK ISP OneTel.Net already.
- pppd options file nicely set up for fast performance
- Customizable phone bill cost tracker, logged by user (/etc/ppp/ppp-connect)
- Nice chat scripts, showing what happened on error (/etc/ppp/dial)
- Initiating user can have programs executed when ppp comes up and goes down.

/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).

Scriptalicious Perl module can make scripts more delicious to SysAdmins.

SYNOPSIS

use Scriptalicious
-progname => "pu";

our $VERSION = "1.00";

my $url = ".";
getopt getconf("u|url" => $url);

run("echo", "doing something with $url");
my $output = capture("svn", "info", $url);

__END__

=head1 NAME

pu - an uncarved block of wood

=head1 SYNOPSIS

pu [options] arguments

=head1 DESCRIPTION

This scripts function is to be a blank example that many
great and simple scripts may be built upon.

Remember, you cannot carve rotten wood.

=head1 COMMAND LINE OPTIONS

=over

=item B< -h, --help >

Display a program usage screen and exit.

=item B< -V, --version >

Display program version and exit.

=item B< -v, --verbose >

Verbose command execution, displaying things like the
commands run, their output, etc.

=item B< -q, --quiet >

Suppress all normal program output; only display errors and
warnings.

=item B< -d, --debug >

Display output to help someone debug this script, not the
process going on.

=back

This module helps you write scripts that conform to best common practices, quickly. Just include the above as a template, and your script will accept all of the options that are included in the manual page, as well as summarising them when you use the -h option.

(Unfortunately, it is not possible to have a `use dependency automatically add structure to your POD yet, so you have to include the above manually. If you want your help message and Perldoc to be meaningful, that is.)

Shortcuts are provided to help you abort or die with various error conditions; all of which print the name of the program running (taken from $0 if not passed). The motive for this is that "small" scripts tend to just get written and forgotten; so, when you have a larger system that is built out of lots of these pieces it is sometimes guesswork figuring out which script a printed message comes from!

For instance, if your program is called with invalid arguments, you may simply call abort with a one-line message saying what the particular problem was. When the script is run, it will invite the person running the script to try to use the --help option, which gives them a summary and in turn invites them to read the Perldoc. So, it reads well in the source;

@ARGV and abort "unexpected arguments: @ARGV";
$file or abort "no filename supplied";

And in the output;

somescript: no filename supplied!
Try `somescript --help for a summary of options

On the other hand, if you call barf, then it is considered to be a hard run-time failure, and the invitation to read the --help page to get usage not given. Also, the messages are much tidier than you get with die et al.

open FOO, "<<less