Free unix commands software for linux

This is a collection of scripts which is used to manage the creation of Slackware packages. This framework is designed to make it easy to add packages to the collection and to easily tweak package parameters for testing and deployment.
The framework currently has a lot of parameters, and also has basic frameworks for CPAN packages. It is possible to add more frameworks and tweaks for other package networks as well, such as the PHP and Python archives, and these are in the works currently.
Enhancements:
- This marks the start of the new style of build scripts. These are much more modular, and have a consistent set of shell functions and variables which work in their defaults for most situations, and can be redefined by a package file to do special setup or other functions
- which some packages may require.

Proc::Command is a backtick that does not use the shell for Perl under Windows.

SYNOPSIS

use Proc::Command

@reponse = Proc::Command->command($command)
@reponse = Proc::Command->command($command, $trys)
@reponse = Proc::Command->command($command, $trys, $sleep)

use Proc::Command qw(command)

@reponse = command($command)
@reponse = command($command, $trys)
@reponse = command($command, $trys, $sleep)

Some Perls under Microsoft windows suffers disabilities over Unix Perls. One particular disability is a backtick without the console. Altough the Microsoft console, may be started without a window (start command with /b option or spawn program call), the Perl system command on windows usually creates a window. Creating a window causes immense user interface problem since it will randomly pop-up and take focus over the current window, erasing current entries into that window. Solutions such as "Proc::SafePipe" do not run on Perls for Window.

This module provides an answer by using the "open" command with a pipe to provide a backtick without a console that will run under Perls on Microsoft Windows.

Tux, of Math Command project is a math practice game for elementary school level children.

Like so many other Linux games, it stars Tux, the Linux Penguin.

Players must answer math equations to shoot down comets which are falling towards their cities.

It can run on Linux/UNIX, Win32, Mac, and BeOS.

GWCC allows users to execute network utilities (ping, nslookup, traceroute) and workstation commands (netstat, df, process grep) from a single tabbed window.
Welcome to GWCC.This program is designed to provide an easy to use interface to your Unix system. I dont know about you, but perform the same operations over-and-over day-after-day, and the command line provided via a terminal window ceases to be very useful once you want to start doing something with the information - like saving or printing it.
In addition to having to know all the flags for all the commands you want to use, you also have to scroll up-and-down the terminal window to retrace your steps and to cut-and-paste (what was that IP address again?).
So, i hope you will find my GTK/GNOME-based point-and-click application of some use in your daily computing activities. Please feel free to write to me with any suggestions you may have (see Contacting The Author below).
Main features:
- Complete preferences system (no need to edit any config files, or know flags)
- GNOME support (session management, dialogs, menus, etc.)
- LibGLADE support
- Saving and Printing of all output!
- Highly configurable command flags and program behaviour.

Unix::Conf::Bind8::DB::A is a Class representing A records.

METHODS

Methods specified here are overridden. They might or not be differnt from the derived ones. For other methods refer to the METHODS section for Unix::Conf::Bind8::DB::Record.

new ()

Arguments
LABEL => string,
CLASS => string, # IN|HS|CHAOS
TTL => string|number,
AUTH_NS => nameserver,
MAIL_ADDR => rp,
SERIAL => zone_serial_no # number
REFRESH => refresh,
RETRY => retry,
EXPIRE => expire,
MIN_TTL => min_ttl,
PARENT => reference, # to the DB object datastructure

Class constructor. Creates a new Unix::Conf::Bind8::DB::* object and returns it if successful, an Err object otherwise. Do not use this constructor directly. Use the Unix::Conf::Bind8::DB::new_* equivalent instead.

auth_ns ()

Arguments
auth_ns
Object method. Get/set the records auth_ns. If an argument is passed, the invocants auth_ns is set and true returned, on success, an Err object otherwise. If no argument is passed the invocants auth_ns is returned.

mail_addr ()

Arguments
mail_addr
Object method. Get/set the records mail_addr. If an argument is passed, the invocants mail_addr is set and true returned, on success, an Err object otherwise. If no argument is passed the invocants mail_addr is returned.

serial ()

Arguments
serial
Object method. Get/set the records serial. If an argument is passed, the invocants serial is set and true returned, on success, an Err object otherwise. If no argument is passed the invocants serial is returned.

refresh ()

Arguments
refresh
Object method. Get/set the records refresh. If an argument is passed, the invocants refresh is set and true returned, on success, an Err object otherwise. If no argument is passed the invocants refresh is returned.

retry ()

Arguments
retry
Object method. Get/set the records retry. If an argument is passed, the invocants retry is set and true returned, on success, an Err object otherwise. If no argument is passed the invocants retry is returned.

expire ()

Arguments
expire
Object method. Get/set the records expire. If an argument is passed, the invocants expire is set and true returned, on success, an Err object otherwise. If no argument is passed the invocants expire is returned.

min_ttl ()

Arguments
min_ttl
Object method. Get/set the records min_ttl. If an argument is passed, the invocants min_ttl is set and true returned, on success, an Err object otherwise. If no argument is passed the invocants min_ttl is returned.

acoc is a regular-expression based colour formatter for programs that display output on the command-line. It works as a wrapper around the target program, executing it and capturing the stdout stream. Optionally, stderr can be redirected to stdout, so that it, too, can be manipulated. acoc then applies matching rules to patterns in the output and applies colours to those matches.

Ever wondered why the output of your favourite UNIX/Linux commands is still displayed in black-and-white after all these years?

Ever had to search back through your scroll-buffer in search of gcc errors and salient information to tell you what went wrong with your programs execution?

acoc is a regular expression based colour formatter for programs that display output on the command-line. It works as a wrapper around the target program, executing it and capturing the stdout stream. Optionally, stderr can be redirected to stdout, so that it, too, can be manipulated.

acoc then applies matching rules to patterns in the output and applies colour sets to those matches. A picture is worth a thousand words, so look at the sample screenshots in the next section.

Configuration

The configuration files used by the program are /usr/local/etc/acoc.conf, /etc/acoc.conf and ~/acoc.conf. One or more of these must exist. A sample /etc/acoc.conf is supplied with some example matching rules.

Blank lines and those that begin with a # are ignored.

A program configuration stanza is introduced as follows:

[program_spec]

The square brackets are mandatory literal characters. Alternatively, the @ symbol may be used, to allow [ and ] to retain their usual semantics in program specs comprising a regular expression:

@program_spec@

program_spec is defined as one or more instances of the following component, separated by a comma:

invocation[/flags]

where invocation consists of the programs name (not including its directory path component) plus any initial arguments.

Alternatively, invocation may be a regular expression, which can be used to match multiple programs and/or command-line arguments in arbitrary order. Regular expressions are automatically anchored to the beginning of the command line.

flags, if present, is separated from invocation by a slash and consists of one or more of the following characters:

a
continue to attempt to find matching patterns after the first match has been found. By default, acoc will stop processing a line and display it after the first match has been found.
e
redirect the target programs stderr to stdout, allowing it, too, to be matched by rules
p
allocate a pseudo-terminal in which to run the target program

Some programs, such as ls(1), behave differently when their stdout is not connected to a tty. Use of this option will fool the target program into believing it is outputting to a tty, rather than a pipe to acoc.

Use of this flag requires Masahiro Tomitas Ruby/TPty library to be installed. Otherwise, the flag is silently ignored.

Note that the pseudo-terminal communication enabled by this flag is one-way only, from the target program to acoc. It is thus not possible to use acoc in combination with interactive programs, such as the interactive Ruby interpreter (irb).
t
apply colour formatting even if stdout is not a tty. By default, formatting is not applied if the output stream is not attached to a terminal.

Heres an example of a line that introduces a configuration stanza:

[rpm/ae,rpmbuild/ae]

which says to apply the following rules to the rpm and rpmbuild commands, attempt to apply all matching rules, and also apply those rules to the programs stderr stream.

Another example:

[ls/p]

This says to allocate a pseudo-terminal to ls(1), fooling it into believing that its output is being sent to a regular terminal instead of a pipe to acoc.

With this flag, the effect will be this:

$ ls
file1 file2 file3 file4 file5 file6

Without it, ls will detect that its stdout is connected to a pipe and behave accordingly:

$ ls
file1
file2
file3
file4
file5
file6

A third example:

[diff/t,rcsdiff/t,cvs diff/t,p4 diff/t]

This says that the rules that follow should be applied to all invocations of diff(1) and rcsdiff(1), as well as those invocations of cvs(1) and p4 that are followed by the argument diff.

Additionally, colouring should be applied even when stdout is not connected to a tty, so that the colours still show up when the output is displayed in a pager such as more(1) or less(1).

Yet another example:

/ps -.*(e.*f|f.*e)/

In this example, the ps(1) command will be matched, as long as the e and f options are both passed in either order.

An alternative way to write the above spec is:

@ps -.*[ef].*[ef]@

There are two things to note in this alternative:

1. @ has been used to delimit the spec, because [ and ] are required for the character lists in the regular expression.
2. While this form is less specific (in that it allows matches against duplicated command line options), it makes for considerably shorter specs if one wishes to test for the inclusion of a set of more than 2 or 3 command line flags. In the original form, one must manually list all of the possible permutations, which is equal to x! (factorial). For 3 command line flags, this is 6 permutations; for 4, it is 24, etc.

Heres one more example:

[tcpdump/r]

If this were placed in ~/.acoc.conf, it would remove any matching rules that had been installed for the diff command by either /etc/acoc.conf or /usr/local/etc/acoc.conf.

After defining the program name and operational flags, matching rules can be defined. These take the following form:

/regex/[flags] colour_spec

where regex is a Ruby-compatible regular expression. The delimiting / characters can be any character, as long as that character is not present in the regular expression itself. flags, if present, consists of one or more characters from the following list:

g
find every match on the line, not just the first. When using this flag, regex should not include parentheses.

colour_spec is defined as a comma-separated list of one or more colour_groups, which are defined as a plus-separated (+) list of one or more of the following:

* black
* blink
* blue
* bold
* clear
* concealed
* cyan
* dark
* green
* italic
* magenta
* negative
* on_black
* on_blue
* on_cyan
* on_green
* on_magenta
* on_red
* on_white
* on_yellow
* rapid_blink
* red
* reset
* strikethrough
* underline
* underscore
* white
* yellow

Examples of a colour_group are white+bold, black+on_white, etc. A complete colour_spec might look like this:

red+bold,white,yellow+bold,black+on_green

Except when using the g flag, each component of the regex that you wish to colour should be placed in parentheses. Text outside parentheses will be used for matching, but will not be coloured.

For example, examine the following:

/^(d+)foos*(w+)/

This will match a line that starts with more or one digits, followed by the string foo and any amount of white space, followed by one or more word characters. However, only the initial group of digits and the group of word characters will be coloured. The string foo and the white space that follows it will be used for matching, but will not be coloured.

Separated from the regex by white space is the colour_spec. Usually, you will include in this as many colours (separated by commas) as you have parenthesised expressions in the regex. However, its also permissible to have fewer. If, for example, you have three parenthesised expressions in the regex, but only two colours listed in the colour_spec, then the second colour will be used for colouring both the second and third matches.

If you have more colours listed in the colour_spec than there are parenthesised expressions in the regex, the surplus colours are ignored.

When using the g flag to perform a global match on the line, you may list as many colours as you want. The same rules apply here. If there are more matches than colours, the remaining matches will be coloured using the last colour listed. Surplus colours are ignored.