Free lynns legacy 1.1 software for linux

Lynns Legacy is an action-adventure game. Lynn the mercenary is on a quest to figure who tried to kill her and why.

Follow Lynn the mercenary as she recollects the mysterious mission that nearly took her life. Travel through multiple overworld areas, (forest, towns, desert, mountains) and boldly step into uncharted dimensions in search of memory!

We have always dreamed of DOOM sources being released! How much days have we been talking about the features wed put in it.

In the middle of 1997, we heard a rumour that the sources of DOOM would be released. Some months later the miracle happened: during December 1997, id Software made the full source code of DOOM public.

KEEP THE BEST OF DOOM: Simple and fast. We wont add a thousands options that complicate the game and make the deathmatch slow down.
NO CHANGE TO THE GAMEPLAY: At least there will be an original gameplay mode.
USER FRIENDLY AND AIMED AT THE PLAYERS: We do Legacy for the people who PLAY and enjoy DOOM today. We wont make an adventure game out of DOOM, damn!
NO CHEATS IN MULTIPLAYER.

The syncopt script and its associated work practices are yet another approach to the standard sysadmin problem of keeping multiple machines software installations up to date.
It is independent of the vendors packaging scheme and thus you can use either your vendors system or syncopt, or both!
The core notion is that the install is done once on a central machine and then syncopt takes care of attaching that to every client, often via cron.
- easy to use
- flexible enough to permit control of what is installed locally on a machine and what is served remotely from a central server (for disc space or other reasons)
- keep out of the way of the ``vendors namespace, to avoid treading on the vendors install and conversely to protect our additions from damage by vendor upgrades and patches.
Main features:
lightweight
- If a package is not to be installed local to a client then the burden is usually just two symlinks on the client.
optional
- You can install packages with syncopt or with the vendors packaging scheme, or both!
permits trial installs
- Under syncopt you can install multiple versions of the same package for trial or legacy purposes.
centralised
- The default package version is controlled by a symlink on the master host; change that and all the clients will follow suit next time they run syncopt.
customisable
- Clients can control which packages are local and also override which version is their default for a given package.
Using
Local Package Install
As a consequence, to make an instance of something local to a client machine (lets call it pkg, release version), remove the local symlink:
$ rm /opt/pkg-version
Make a stub directory:
$ mkdir /opt/pkg-version
Alternatively, just edit the .syncopt file and add this line:
pkg-version local
Run syncopt:
$ syncopt -x
That syncs everything. You can just do the new package like this:
$ syncopt -x pkg pkg-version
which syncs the generic (unversioned) link and the version specific local directory.
Undoing a Local Package Install
To make a once-local copy remote, remove the local copy:
$ rm -rf /opt/pkg-version
Also, if you edited the .syncopt file as above, remove that line.
Run syncopt:
$ syncopt -x pkg pkg-version
Bringing a Client into Sync after a New Package Install
To set up a new clients /opt directory after a fresh install:
$ mkdir /opt # if necessary
$ syncopt -x
/opt/.syncopt
The behaviour deduced from the presence or absence of a directory can be overridden with the /opt/.syncopt file, which contains line of the form:
pkg version
to make version the default package version on this particular machine, or
pkg local
to force a package to be local on this machine, or
pkg-version local
to make a particular version local, or
pkg nosync
to not run syncopt on it at all.

FLAT::Legacy::FA::RE is a regular expression base class.

SYNOPSIS

use FLAT::Legacy::FA::RE;
use FLAT::Legacy::FA::NFA;
my $re = RE->new();
$re->set_re(a|b|(hi)*);
my $nfa = $re->to_nfa();
print $nfa->info(); # see stuff on NFA
my $dfa = $nfa->to_dfa();
print $dfa->info(); # see stuff on DFA
my @removed = $dfa->minimize();
print $dfa->info(); # see stuff on minimized DFA
print "Removed ".($#removed+1)." statesn";

This module implements a regular expression parser, and supports the conversion of a RE to a deterministic finite automata. A homegrown recursive descent parser is used to build the parse tree, and the method used to conver the regular expression to a DFA uses no intermediate NFA.
Recursive Descent-safe Regex Grammar:

R -> O

O -> CO

O -> | CO | epsilon

C -> SC

C -> .SC | epsilon

S -> LS

S -> *S | epsilon

L -> a | b | c |..| 0 | 1 | 2 |..| (R) | epsilon

Terminal symbols: a,b,c,..,z,0,1,2,..,9,|,*,(,)

NOTE: Concatenation operator, ., is not a terminal symbol and should not be included in the regex

FAQ: Q: Does this support Perl regular expressions?
A: No, just the regular expression using the terminal symbols listed above.

ifstat is a tool to report network interface bandwith just like vmstat/iostat do for other system counters. It can monitor local interfaces by polling the kernel counters, or remote hosts interfaces using SNMP.
fstat gathers these statistics from the kernel internal counters, which is highly operating system dependent.
Right now, the following systems are supported:
Linux >= 2.2.0 (through /proc/net/dev file).
FreeBSD >= 2.2 (using the ifmib(4) interface).
Solaris >= 5.6 (using the kstat(3K) interface).
IRIX and OpenBSD (using the SIOCGIFDATA ioctl).
NetBSD and Darwin (using the route(4) sysctl interface).
Other BSDs (using the kvm(3) interface).
Digital Unix (OSF/1), Tru64, and Aix (using the legacy kmem interface).
HP-UX (using the DPLI streams interface).
Win32 native or through Cygwin (using the GetIfTable call).
If the net-snmp (or ucd-snmp) library is available, ifstat can use it to gather statistics from remote equipments (hosts, routers, switches...) or even the local host if a SNMP daemon is running.
ifstats functionnalities can as a static application. To use it, you just have to pass --enable-library while configuring ifstat.
Enhancements:
- Digital Unix (OSF/1) and Tru64 support.
- AIX support (tested on AIX v4.3).
- HP-UX support with DLPI streams interface. (sample code contributed by Jean-Marc Saffroy )
- Win32 support (native or with cygwin) with GetIfTable interface. (sample code contributed by Alexandre Raclot )
- Use net-snmp-config if present to find out SNMP flags.

Gajim is a Jabber client written in PyGTK.
Gajim does not require GNOME to run, eventhough it exists with it nicely. Gajim is released under the GNU General Public License.
Main features:
- Tabbed chat windows
- Groupchat support (with MUC protocol)
- Emoticons, URL grabber
- Systray icon
- TLS & GPG support (with SSL legacy support)
- Transport Registration support
- Service Discovery including Nodes
- Multiple accounts support
- Gajim is available in English, French, German, Russian, Spanish, Polish, Portugese, Greek and Bulgarian

Iguana is designed as a base for the provision of operating system (OS) services for embedded systems. Among others, it provides the underlying OS for Wombat, our version of paravirtualised Linux designed to provide legacy support for embedded systems.

Iguana runs on top of the L4 microkernel, presently the Version 4 API as implemented by L4Ka::Pistachio. L4/Iguana is designed to support a painless transition to the new security-oriented API being developed for L4.

While it borrows many ideas from the Mungi operating system, Iguanas target domain of embedded systems requires a different approach to a number of issues. The main characteristics of Iguanas design are:

- Iguana complements, rather than hides the underlying L4 API. It provides services virtually every OS environment requires, such as memory and protection management, and a device driver framework;
- the memory and cache footprints of Iguana are kept small;
- low-overhead sharing of data is supported;
- Iguana supports the separation of protection and translation, by encouraging a non-overlapping address-space layout. This means that Iguana-based systems can be readily deployed on processors without virtual memory, and can also obtain the best possible performance on the ARM7 and ARM9 cores widely used in embedded systems.

The Secure Remote Password protocol is the core technology behind the Stanford SRP Authentication Project. The Project is an Open Source initiative that integrates secure password authentication into existing networking applications.
The Projects primary purpose is to improve password security by making strong password authentication technology a standard part of deployed real-world systems. This is accomplished by making this technology an easy-to-use, hassle-free alternative to weak and vulnerable legacy password authentication schemes. SRP makes these objectives possible because it offers a unique combination of password security, user convenience, and freedom from restrictive licenses.
This site serves as the semi-official home of the SRP distribution, which contains secure versions of Telnet and FTP. In addition, it contains links to a number of SRP-related projects, products (both commercial and non-commercial), and research on the Web.
SRP is a secure password-based authentication and key-exchange protocol. It solves the problem of authenticating clients to servers securely, in cases where the user of the client software must memorize a small secret (like a password) and carries no other secret information, and where the server carries a verifier for each user, which allows it to authenticate the client but which, if compromised, would not allow the attacker to impersonate the client. In addition, SRP exchanges a cryptographically-strong secret as a byproduct of successful authentication, which enables the two parties to communicate securely.
Enhancements:
- (telnet) Security fixes for vulnerabilities:
- CAN-2005-0468 Multiple Telnet Client env_opt_add() Buffer Overflow Vulnerability
- CAN-2005-0469 Multiple Telnet Client slc_add_reply() Buffer Overflow Vulnerability
- (libsrp) Change default group parameter test strategy to accept only parameters on the built-in list. Fix originally suggested by Bodo Moeller, University of Calgary.
- (libsrp) Fixed big in BigIntegerCmpInt when built against OpenSSL.
- (telnet) Use header file to declare errno when available.
- (all) Added support for GNU crypto (gcrypt).