Free for last software for linux

Data is fetched from audioscrobbler web services. In this version it shows nine views: top artists, top tracks, top albums, systems recomendations and recent tracks, etc. Data is updated every five minutes or clicking on refresh button.

Use: First write your last.fm user name on the input box and click the apply button. After a moment, use arrows button for select the view.

amaroK Last.fm tags script fetches your tags from Last.fm for artists, albums, and tracks. It stores them as id3v2 COMM tags in your music files and appends them to the comment for the given track in amaroKs collection where they can be used to contruct smart playlists.

So far this script only fetches your tags, it doesnt syncronize changes you make locally back to Last.fm. Probably this feature should wait until the implementation of "labels" which is coming in amaroK 1.5.

Also so far it is only possible to fetch tags for a selection within a playlist. The other context sub-menus just provide helpful messages saying that this feature isnt implimented yet.

As usual this software comes with no warrenty, it might eat your lunch, etc.. That said it works for me.

I owe a large debt of gratitude to Miguel Angel Alvarez whoes amaroK Replaygain script served as the skeleton of this one. Thanks Miguel!

LastBASH project is a console/terminal based Last.fm player. Although the default Last.fm player is a great one, it also is a graphical one and it could be somewhat inadequate for the die-hard terminal users, like some people I know.
LastBASH tries to find its place among the other Last.fm players, filling this gap: the missing console player.
Basically, it is no more than a TUI frontend, written in Bash. It displays the information of the current playing track, keeps a history of the played tracks and allows the user to perform some actions on the current track, such as love, skip or ban.
To listen to Last.fm, you can use any player capable of mp3 streaming (such as MPlayer, mpg123, XMMS and so on) by opening the M3U playlist that LastBASH saves on connecting. But the recommended way is to use the LastBASH frontend features and let it run some compatible player in background (MPlayer or mpg123), that you can control through the same user interface. This way you need to have only one console open to listen and control Last.fm.
Main features:
- authentication using the md5 password encryption
- retrieves the metadata of the current playing track and displays it (artist, album, track name, track duration)
- keeps a history of last played tracks
- allows you to control the Last.fm station, by issuing the love, skip and ban commands
- optionally, it can run a backend player (such as MPlayer or mpg123), which you can control through the same interface, or lets you choose any external player you wish (capable of playing mp3 streams)
Usage
Please see the Install page for quick instructions about how to install and launch LastBASH. You must have a compatible terminal (linux or xterm are supported at the moment) and, if you wish to use the backend player, you should have MPlayer. For now.
After you have donwloaded, extracted and installed the program, run it. You do not need to pass any command line parameters, at least at first start.
lastbash
It will ask your Last.fm username and password. You should have one. If not, hmmm... go and create an account on Last.fm
Then, the program will try to connect. If it succeeds, it will save a playlist in ~/.lastbash/playlist.m3u, for you to open with some external player, if you dont want to use the backend it provides.
If you have MPlayer (for the moment, this is the backend), it will start playing. If not, you will have to tell LastBASH not to try to run it by creating the ~/.lastbash/config file and adding this line:
USE_PLAYER="n"
Then, open your mp3 player, load the above-mentioned playlist and start playing. LastBASH will show you the current playing track and will keep a history of last played tracks. Enjoy!
Enhancements:
- This release adds debug mode toggling directly from the interface, adds more remote commands, checks the validity of data passed in the commandline, displays detailed station changing errors, fixes player integration (especially the "quit" sequence), includes the man page and the configuration file, saves the current meta information to a file, shows a better help message, and uses getopts for parsing the commandline parameters.

SDL for AmigaOS 4.0 project is a port of SDL, the Simple Directmedia Layer, for AmigaOS 4.0 SDL is a popular open-source API for games and other software that need low-level access to video and audio hardware and input devices.

SDL was created and is maintained by Sam Lantinga, but has had a legion of contributors of the years (see SDL credits). The AmigaOS 4.0 port was created originally by Thomas and Hans Joerg Frieden, but for the last two years has largely been the work of me, Richard Drummond.

Other contributors include Juergen Schober (who developed the audio layer). You can find may OS4.0 applications built with SDL at os4depot.net and some that I have built on my Amiga Stuff page.

WM Workload is a workload average monitor (the number of process trying to use the CPU concurrently in the last minute).

This project is a modification of wmnetload. wmworkload is a dirty hack on wmnetload. A few structures are still on ifstats.h.

Just type "make" and then copy the binary "wmworkload" to your favorite DockApp directory.

wmworkload requires libDockApp to run

JFlag project is a RTS-like game with multiple play modes.
JFlag is an RTS-like game with multiple play modes (capture the flag, last man standing, etc.).
Main features:
- Network game, up to 9 players
- Gameplay based on XML files, so *everything* is easily customizable
- Random map generation
- And many more..

Erlang is a programming language designed at the Ericsson Computer Science Laboratory.
Open-source Erlang is being released to help encourage the spread of Erlang outside Ericsson.
Installation
When installed, the entire system, except for a small start-up script, resides in a single directory tree. The location of this directory tree can be chosen arbitrarily by the installer, and it does not need to be in the users $PATH.
The only requirements are that the file system where it is placed has enough free space, and that the users who run Erlang/OTP have read access to it. In the example below, the directory tree is assumed to be located at /usr/local/erlang, which is here called the top-level directory.
It is assumed that you have the compressed tar file, the name of which is < PREFIX >.tar.gz, where < PREFIX > is a string denoting the particular Erlang/OTP release, e.g. otp_LXA_11930_sunos5_R9B.
Wherever the string < PREFIX > is used below, it should be replaced by the actual name prefix of the compressed tar file.
The tape archive file does not have one single directory in which all other files are rooted. Therefore the tape archive file must be extracted into an empty (newly created) directory.
1. If the top-level directory does not already exist, create it:
mkdir /usr/local/erlang
2. Change the current directory to the top level directory:
cd /usr/local/erlang
3. Create the installation directory with an appropriate name. For example:
mkdir otp_r7b
4. Change to the installation directory, e.g.
cd otp_r7b
5. Assuming the compressed tar file resides in the directory ,. extract the compressed tar file into the current directory:
gunzip -c / .tar.gz | tar xfp -
6. Read the README file in the installation directory for last minute updates, before proceeding.
7. Run the Install script in the installation directory, with the absolute path of the installation directory as argument,
./Install /usr/local/erlang/otp_r7b
and supply answers to the prompts.
In most cases, there is a default answer in square brackets ([]). If the default is satisfactory, just press . In general you are only prompted for one thing:
- "Do you want to use a minimal system startup instead of the SASL startup?"
In a minimal system, only the Kernel and STDLIB applications are loaded and started. If the SASL startup is used, the SASL application is included as well. Normally, the minimal system is enough.
8. Make Erlang/OTP available for users, either by putting the path /usr/local/erlang/otp_r7b/bin in users $PATH variable, or link the executable /usr/local/erlang/otp_r7b/bin/erl accordingly, e.g.:
ln -s /usr/local/erlang/otp_r7b/bin/erl /usr/local/bin/erl
Enhancements:
- Among other things, SMP support was added.