Free for macintosh users please note that the filename must include the appropriate 3 letter extension software for linux

Vector Linux is a fast, small, Intel based Linux operating system for PC style computers. The creators of Vector Linux had a single credo: keep it simple, keep it small and let the end user decide what their operating system is going to be. What has evolved from this concept is perhaps the best little Linux operating system available anywhere.
For the casual computer user you have a lightening fast desktop with graphical programs to handle your daily activities from web surfing, sending and receiving email, chatting on ICQ or IRC to running an ftp server. The power user will be pleased because all the tools are there to compile their own programs, use the system as a server or perhaps the gateway for their home or office computer network.
Administrators will be equally as pleased because the small size and memory requirements of the operating system can be deployed on older machines maybe long forgotten.
Well here it is. we couldnt let the soho people have all the fun could we? This live-cd represents as close as possible VectorLinux 5.1 standard. It comes with kernel 2.6.15.3 udev-085 ndiswrapper 1.9, and everything else from standard, like icewm, fluxbox, and xfce4.
Please download and help us find some bugs to squash
We would like to thank all the developers, testers, The VectorLinux community, and the developer of linux-live scripts from www.linux-live.org.
Enhancements:
- The VectorLinux team is proud to announce the release of VectorLinux 5.8 Live CD and the first SOHO 5.8 alpha live CD and DVD. This is the final release for 5.8 standard GOLD live. The hard drive installer that has been problematic is fixed and should work well. The SOHO 5.8 alpha live comes in either CD or DVD editions. The DVD edition includes all that is in the SOHO 5.8 install release plus 62 additional language packs for KDE. The CD version has lost some functionality due to size constraints. The development tool chain and OpenOffice.org were removed.

Call Of Duty 2 Linux Multiplayer Server Code is a COD2 linux server.

!! IMPORTANT !!

Call of Duty 2 Linux Server is NOT SUPPORTED by Activision Customer Support. Please do not call with any questions related to this free beta product. There are other channels to aid you listed at the bottom of this document.

Introduction

This document explains how to install the Call of Duty 2 Linux server version 1.0. Installation from scratch and upgrading an existing installation are both covered.

Usage is very similar to Call of Duty and United Offensive... many of the console commands, command lines, and cvars are identical, so if you are comfortable maintaining dedicated servers for those games, you will find this process familiar.

MOD USERS: PLEASE READ...

It is recommended that any user modifications that have been installed to the Call of Duty 2 directory be removed before installing this package. These modifications are not supported by Activision and may not be compatible with some of the new features that are included. When installing or upgrading a server, if problems or unexpected behavior arise, your first step in troubleshooting should be to do a clean install with the original data files.

IF YOU HAVE A PROBLEM WITH "LIBSTDC++.SO.5" ...

(This is a frequent-enough problem to merit discussion in the introduction.)

If you are reading this, its probably because you tried to start your Linux server and saw this message:

./cod2_lnxded: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

COD2 is a C++ program built with gcc 3.3.4, which means it needs a system library specific to gcc 3.3. Older Linux systems wont have this installed, and were starting to see newer Linux distributions that dont have this either, since they are supplying an incompatible gcc 3.4 version. The good news is that you can drop the needed library into your system without breaking anything else.

Here is the library you need, if your Linux distribution doesnt supply it:

http://icculus.org/updates/cod/gcc3-libs.tar.bz2

You want to unpack that somewhere that the dynamic linker will see it (if you are sure it wont overwrite any files, you can even use /lib).

The brave can put it in the same directory as the game and run the server like this:

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:. ./cod2_lnxded

Now the server will start.

Upgrading from 1.0 to Linux 1.0a.

Just stop the game server, replace cod2_lnxded on your server with the version included in this package, and restart the game server. 1.0a is just a minor hotfix and requires no other code changes.

As the hotfix is Linux-specific there is no Windows version of 1.0a.

Installation From Scratch

- Get the retail Call of Duty 2 disc(s) (there may be multiple discs depending on what edition of the game you have obtained, or perhaps a single DVD-ROM disc).
- Copy the contents of disc ones "Setup/Data" directory to wherever you want to install the Call of Duty 2 Linux server. There should be a "localization.txt" file in the root of this directory, and a "Main" Subdirectory. Each additional disc should be opened and the contents of each "Data" folder should be copied over to the existing Main folder. When you have copied everything, the final installation size is around 3.5 gigabytes.
- Alternately, you may install on Windows and copy the installed game to your Linux system, but many will opt to skip this step since the data files are uncompressed and easily accessible on the discs. Final installation size is around 3.5 gigabytes.
- Unpack this archive in the root of the newly-copied tree, so "cod2_lnxded" is in the same directory as "localization.txt". Unlike the original Call of Duty, there are not seperate .so files like "game.mp.i386.so", so dont be concerned when you dont see them.
- Now, run the server:
cd /where/i/copied/callofduty2
./cod2_lnxded

- When you see "--- Common Initialization Complete ---", the game server has started, but you need to start a map before the server will accept connections. At this point, type:

map mp_leningrad

("mp_leningrad" being a given maps name).

- Now you should see your server in the in-game browser. You will now want to customize your server, but that is beyond the scope of this document.

https://addons.mozilla.org/en-US/firefox/downloads/file/14560/firefox_extension_backup_extension__febe_-4.0.5-fx.xpi

mod_urlscheme is an Apache 1.3/2.0/2.2 module that allows the Apache configuration author control over the scheme to use when constructing self-referential URLs.
Please note that this module is different from mod_scheme, which embeds the Tinyscheme interpreter into Apache. You can find that module here. I changed the name from mod_scheme to mod_urlscheme to avoid confusion.
The original module was only written to work on Apache 2.0. There is now also a version for Apache 1.3 + EAPI, although it wont work with stock 1.3. Please see the "Apache 1.3" section at the bottom of this page for details. The 2.0 module will work almost unchanged on Apache 2.2. There is a small naming change in the API that requires a slightly different version.
In several situations, Apache will attempt to construct a URL that will point to itself and will deliver the result to the client. The most notable occasion for this is when Apache is constructing a client redirect. This can for example happen when the client requests a URL that maps to a directory but doesnt include a trailing slash: Apache will send back a redirect to the same URL, but with a trailing slash appended. Other occasions include Redirect directives in the Apache configuration, or mod_proxy rewriting redirects coming from a backend server (when mod_proxy is functioning as a reverse proxy).
A self-referential URL has four distinct major components: the scheme, the hostname, the port number and the request URI, the latter including perhaps a query string and a fragment identifier. The combination of ServerName, UseCanonicalName and the use of the clients HTTP Host header allows an Apache administrator full control over the hostname and port number part of the generated URLs, but the scheme is up to Apache itself.
Normally, the scheme is always "http". A module such as mod_ssl will override this and set the scheme to "https" for those locations where it is active. But that doesnt help you when the Apache server is behind another server that will handle the HTTPS traffic for you. Imagine the following layered approach:
- The clients HTTPS request comes in to the first machine on port 443 (the default port for HTTPS). The first machine, which perhaps has dedicated hardware to speed up SSL processing, accepts the connection and provides for all the encryption/decryption. It forwards the decrypted request as a regular HTTP request to port 81 on the next machine.
- The second machine runs Apache. It will be listening on ports 80 and 81. It will receive the request from the first machine on port 81. The fact that its coming in on that port establishes the request as being secure, and Apache may provide different processing rules depending on whether the request is secure or not. (Of course, the Apache server should be behind a firewall, so a client cant connect to port 81 directly and circumvent the access controls.)
Now, if Apache for some reason needs to generate a redirect, the scheme on the redirect URL will be "http", because thats what Apache is serving. But that URL isnt valid on the outside: the scheme should be "https", so that the client will proceed to get the new URL from the same secure location.
One solution is to let the machine that handles the SSL work do the rewrite from http://www.example.com:81/ to https://www.example.com/. But that doesnt help you if the first machine is (for example) a dumb SSL tunnel that doesnt understand HTTP. In that case, Apache will need to be convinced its scheme is actually "https", not "http".
Thats where mod_urlscheme comes in.
Installation:
These instructions assume a Unix installation. For other systems, please consult the Apache documentation. mod_urlscheme is a very simple module that requires no special treatment. Simply put, if you can build mod_example from the stock Apache tree, then you can build mod_urlscheme as well.
Put the downloaded mod_urlscheme.c file in a temporary directory somewhere where you will compile it.
If you want to include mod_urlscheme as a static module in your Apache server, prepare your Apache source directory as per the Apache build instructions. When calling the ./configure command, include the option --with-module=experimental:/path/to/mod_urlscheme.c (for Apache 1.3: --add-module=/path/to/mod_urlscheme.c). You need to specify the full path to the source file after the colon. Then, proceed with the build instructions as you would normally. The module will be included in your Apache binary as a static module.
For a dynamic module, first install a full Apache distribution, including the apxs tool and the C headers. If you install from pre-packaged bundles, such as RPMs, you may need to separately install the development package. On RPM-based systems that usually means you need to have the httpd-devel package installed. You will also need a fully functional compiler suite installed.
Go to the directory where you put the mod_urlscheme.c file and run apxs -c mod_urlscheme.c. Refer to the Apache documentation to see if you need to specify more command line options for your system.
If the compile succeeded, you will now have a dynamic Apache module ready to use. You may need to look in the .libs subdirectory to find the actual mod_urlscheme.so file (under Unix, that is). Copy the module to the Apache module directory, which is the modules subdirectory of the server root (for Apache 1.3: the libexec subdirectory). Alternatively, you can put it in any other location; just make a note of where you put it, so you can refer to the location later on.

Kororaa project is a way of installing Gentoo Linux easily and quickly, similar to Gentoos "Stage3 with GRP packages" install.

Whats different?

For Kororaa we wrote an install script to go along with our install method which takes care of most of the manual configuring required under the Gentoo method;

The Kororaa build is derived from Bob Ps Stage 1/3 install method;

Also, we have pre-defined a wide suite of KDE based (and now also Gnome based) applications for your use and designed the entire system specifically for these;

We have also added a large number tweaks and automations along the way to assist in the Kororaa experience.

Whats the point of it?

I must state that I adore the manual Gentoo way of installing. In fact, I swore against an installer for Gentoo for a long time and this stance has not really changed. What I wanted however was a way to quickly re-produce a desktop installation for multiple machines. I also wanted a tool that I could give to friends who liked the idea of Gentoo but complained about the "compile time". I dont think that missing out on the Gentoo experience because of "compile time" is valid and so I wanted a way to introduce my friends to Gentoo without having to build their systems myself.

I cannot more strongly recommend the Gentoo install method if you are serious about learning both Gentoo and GNU/Linux in general. I owe Gentoo a lot - I played with Redhat* back in 1998 (thanks to Andrew Tridgell) but then fell into "RPM hell" and went around from distro to distro in a mad seething rage of desperation. Then I came across Gentoo 1.1 and it was love at first install.

So, if youre someone who doesnt want to wait to get a nicely configured Gentoo system, is so afraid of the standard install method that its stopping you from trying Gentoo at all, or youre a lazy pig then this method is for you!

Note: You can use our stage3, portage snapshot and packages together with the standard Gentoo "Stage3 GRP" install if you want to try it that way too!

What else?

The Kororaa system comes pre-configured for a Pentium3. We chose Pentium3 because most people should have an SSE capable processor by now.

This means it will run on any P3 Coppermine core and later, including AMD Athlon-XP, Athlon64/Opteron, Sempron etc and Intel Pentium 4, Pentium M, Xeon etc.

Please note it will NOT work on a system without SSE support.

As of Beta2 however, we have also released an AMD64 version, which will run on any AMD 64bit cpu including Athlon64, Sempron64 and Opteron.

If you want more optimisation, you can easily re-build your system with all the current apps and configuration by changing your make.conf and rebuilding world.

Please note the system is currently BETA, a bit "hacky" and could destroy your harddrive or something even more nasty like bowed legs and a crooked smile.

remoteMoin are a couple of XML-RPC plugins for MoinMoin adding some useful features making a automated usage of MoinMoin easier.
Installation:
Scripts
Installation of these mini-projects is straight-forward: Just put them in a directory in your path and make them executable.
Some mini-projects have prerequisites which are listed in the manual page. Make sure to have the prerequisites installed.
Perl modules
Perl modules are of course installed with the usual sequence of
gunzip < dist >.tar.gz
tar xvf < dist >.tar
cd < dist >
perl Makefile.PL
make
make test
make install
Emacs
Refer to the file itself how to embed the code into your Emacs environment.
MoinMoin
Some mini projects are plugins for MoinMoin and you must put them to the right directory in the plugin structure of your Wiki. For instance see installation instructions for parsers.
Other mini projects are regular scripts.
Please note that the current hoster of this site does not like .py files. Therefore they are extended by a .txt. Please strip the .txt before installation.
Enhancements:
- Adaptations for MoinMoin 1.5.4 (was 1.3.4).

Forecastfox is a Firefox extension to get international weather forecasts from AccuWeather.com, and display it in any toolbar or statusbar with this highly customizable and unobtrusive extension.

Why the switch from Weather.com to AccuWeather.com?

Several factors contributed to us switching our data provider from Weather.com to Accuweather.com. The "Terms of Use" for the feed from Weather.com, was very restrictive. It kept us from implementing some of the things we hope to implement. They had also warned us that they were changing the feed and that we were in breach of the license (25,000 users max on the public XOAP weather.com feed). They offered another feed we could use, which would have limited the amount of data we received. At the same time several companies were contacting us about using their data. Accuweather.com was the most responsive, and provided us with greatest flexibilty and room to grow.

Please note that version 0.7.5 and higher "pings" our server when it is installed or uninstalled. No information is sent other than what version is being installed or uninstalled, and on what program (Mozilla vs Firefox). We simply increment a value in a database everytime it gets pinged so that we can have a rough estimate of the number of Forecastfox users. You can see the statistic page that we use at http://forecastfox.ensolis.com/logs/status.php. By knowing how many users we have and how many users upgrade, we will have a better idea of what we need to work on. For example, we will know if we should spend time supporting Mozilla and Netscape, and if we need to support migrating/upgrading from early versions. Thank you for understanding.