Free hiv entry and exit points software for linux

Last Exit is a player for the LastFM radio station.
It has most of the useful features that the official player has including
- Stream support
- Station searching
- Tagging
- Journalling
- Access to subscriber features
It also has more powerful searches for stations including Neighbours personal stations, users stations and fan stations.

AtExit is a Perl module that can perform exit processing for a program or object.

SYNOPSIS

use AtExit;

sub cleanup {
my @args = @_;
print "cleanup() executing: args = @argsn";
}

## Register subroutines to be called when this program exits

$_ = atexit(&cleanup, "This call was registered first");
print "first call to atexit() returned $_n";

$_ = atexit("cleanup", "This call was registered second");
print "second call to atexit() returned $_n";

$_ = atexit("cleanup", "This call shouldve been unregistered by rmexit");
rmexit($_) or warn "couldnt unregister exit-sub $_!";

if (@ARGV == 0) {
## Register subroutines to be called when this lexical scope is exited
my $scope1 = AtExit->new( &cleanup, "Scope 1, Callback 1" );
{
## Do the same for this nested scope
my $scope2 = AtExit->new;
$_ = $scope2->atexit( &cleanup, "Scope 2, Callback 1" );
$scope1->atexit( &cleanup, "Scope 1, Callback 2");
$scope2->atexit( &cleanup, "Scope 2, Callback 2" );
$scope2->rmexit($_) or warn "couldnt unregister exit-sub $_!";

print "*** Leaving Scope 2 ***n";
}
print "*** Finished Scope 2 ***n";
print "*** Leaving Scope 1 ***n";
}
print "*** Finished Scope 1 ***n" if (@ARGV == 0);

END {
print "*** Now performing program-exit processing ***n";
}

The AtExit module provides ANSI-C style exit processing modeled after the atexit function in the standard C library (see atexit(3C)). Various exit processing routines may be registered by calling atexit and passing it the desired subroutine along with any desired arguments. Then, at program-exit time, the subroutines registered with atexit are invoked with their given arguments in the reverse order of registration (last one registered is invoked first). Registering the same subroutine more than once will cause that subroutine to be invoked once for each registration.

An AtExit object can be created in any scope. When invoked as a function, atexit registers callbacks to be executed at program-exit time. But when invoked as an object-method (using the $object->method_name syntax), callbacks registered with an AtExit object are executed at object-destruction time! The rules for order of execution of the registered subroutines are the same for objects during object-destruction, as for the program during program-termination.

The atexit function/method should be passed a subroutine name or reference, optionally followed by the list of arguments with which to invoke it at program/object exit time. Anonymous subroutine references passed to atexit act as "closures" (which are described in perlref). If a subroutine name is specified (as opposed to a subroutine reference) then, unless the subroutine name has an explicit package prefix, it is assumed to be the name of a subroutine in the callers current package. A reference to the specified subroutine is obtained, and, if invocation arguments were specified, it is "wrapped up" in a closure which invokes the subroutine with the specified arguments. The resulting subroutine reference is added to the front of the list of exit-handling subroutines for the program (atexit) or the AtExit object ($exitObject->atexit) and the reference is then returned to the caller (just in case you might want to unregister it later using rmexit. If the given subroutine could not be registered, then the value zero is returned.

The rmexit function/method should be passed one or more subroutine references, each of which was returned by a previous call to atexit. For each argument given, rmexit will look in the list of exit-handling subroutines for the program (rmexit) or the AtExit object ($exitObject->rmexit) and remove the first matching entry from the list. If no arguments are given, then all program or object exit-handlers are unregistered! The value returned will be the number of subroutines that were successfully unregistered.

At object destruction time, the DESTROY{} subroutine in the AtExit module iterates over the subroutine references in the AtExit object and invokes each one in turn (each subroutine is removed from the front of the queue immediately before it is invoked). At program-exit time, the END{} block in the AtExit module iterates over the subroutines in the array returned by the exit_subs method and invokes each one in turn (each subroutine is removed from the front of the queue immediately before it is invoked). Note that in both cases (program-exit, and object-destruction) the subroutines in this queue are invoked in first-to-last order (the reverse order in which they were registered with atexit).

audit package contains the user-space utilities for creating audit rules. As well as for storing and searching the audit records generate by the audit subsystem in the Linux 2.6 kernel.
Usage:
Examples usage of utilities:
General:
Window 1:
./auditd
Window 2 (you dont have to have the daemon running to try this, but
enabled has to be 1):
./auditctl -s
./auditctl -a entry,always -S open
ls
./auditctl -d entry,always -S open
Identity tracking:
./auditctl -a exit,always -S all -F loginuid=2000
./auditctl -L 2000,"test uid"
Enhancements:
- Updates were made to system-config-audit. auditctl was updated to better handle watching of directories with older kernels.
- Memory leaks and an invalid free in auditd were fixed along with interpretations in auparse.

Data::ICal::Entry::TimeZone is a Perl module to represents a time zone definition in an iCalendar file.

SYNOPSIS

my $vtimezone = Data::ICal::Entry::TimeZone->new();
$vtimezone->add_properties(
tzid => "US-Eastern",
tzurl => "http://zones.stds_r_us.net/tz/US-Eastern"
);

$vtimezone->add_entry($daylight); # daylight/ standard not yet implemented
$vtimezone->add_entry($standard); # :-(

$calendar->add_entry($vtimezone);

A Data::ICal::Entry::TimeZone object represents the declaration of a time zone in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.

This module is not yet useful, because every time zone declaration needs to contain at least one STANDARD or DAYLIGHT component, and these have not yet been implemented.

CDK4AVR stands for Cross Development Kit for Atmels AVR RISC processor serie and should support your development with a comprehensive Assembler and C development environment for even this processor familie under Linux. It will present only free of fee tools, so you can use it without risks. Further you will find some useful OS projects and related sample code all arround AVRs inside of the example packages.
CDK4AVR collects all programms and development tools in one directory (/opt/cdk4avr) and will try to present an easy to admin installation.
My intention for CDK4AVR is / was to provide a full featurd tool chain distribution of all the free accessible resources, because the most stuff is scattered to the wide of the whole Internet and only compileable by wizards or professions.
Installation:
Each package will be provided as RPM only. It is not necessary to install all packages,but you have to install the base package cdk-avr-base every time you want to use another package. Here is an example for a typical GNU development environment:
[user@host]$ rpm -hiv cdk-avr-base-0.3-20031111.i386.rpm
[user@host]$ rpm -hiv cdk-avr-binutils-2.14-20030906.i386.rpm
[user@host]$ rpm -hiv cdk-avr-gcc-3.3.2-20031021.i386.rpm
[user@host]$ rpm -hiv cdk-avr-gcc-c++-3.3.2-20031021.i386.rpm
[user@host]$ rpm -hiv cdk-avr-gcc-colorgcc-3.3.2-20031021.i386.rpm
[user@host]$ rpm -hiv cdk-avr-libc-1.0.2-20040229.noarch.rpm
[user@host]$ rpm -hiv cdk-avr-gdb-6.0-20031019.i386.rpm
[user@host]$ rpm -hiv cdk-avr-simulavr-0.1.2.20040304cvs-20040304.i386.rpm
[user@host]$ rpm -hiv cdk-avr-avarice-2.2-20040229.i386.rpm
[user@host]$ rpm -hiv cdk-avr-uisp-20040207cvs-20040304.i386.rpm
[user@host]$ rpm -hiv cdk-avr-avrdude-4.3.0-20040229.i386.rpm
Base package -- is needed every time you will use any CDK4AVR package.
NOTE: Users of base packages with version 0.2 and prior have to update to latest version. There was a damaged (t)csh startup script. As a result of an buggy %preun script in previous packages you have to update in two cycles:
[user@host]$ rpm -hUv cdk-nios-base-0.3-20031111.i386.rpm
[user@host]$ rpm -hUv --force cdk-nios-base-0.3-20031111.i386.rpm
Enhancements:
- There are minor feature enhancements in AVR-Ada 0.4.1.
- As a result, the packeges for binutils and gcc/gnat were rebuilt.
- There are new packages for the AVR-Ada run time system and related examples.

Tina POS is a point of sales application designed for touch screens.

Tina POS supports ESC/POS ticket printers, customer displays, and barcode readers.

Its multi-user and has a great backoffice with a product entry form, reports, and charts.

Data::ICal::Entry::Journal is a Perl module that represents a journal entry in an iCalendar file.

SYNOPSIS

my $vjournal = Data::ICal::Entry::Journal->new();
$vjournal->add_properties(
summary => "Minutes of my party",
description => "I cried because I wanted to.",
# Dat*e*::ICal is not a typo here
dtstart => Date::ICal->new( epoch => time )->ical,
);

$calendar->add_entry($vjournal);

A Data::ICal::Entry::Journal object represents a single journal entry in an iCalendar file. (Note that the iCalendar RFC refers to entries as "components".) It is a subclass of Data::ICal::Entry and accepts all of its methods.