Free started out hustlin end up ballin lyrics software for linux

Amarok letras.mus.br lyrics is an amaroK script to get lyrics from http://letras.mus.br.

Fixed a small bug that made it skip the first line of the lyrc.

Many thanks to www.letras.mus.br for providing their service.

jamendAmarokLyrics is a lyrics plugin for Amarok that can fetch Lyrics from http://jamendo.com, where there is plenty of free creative commons music!

Panzis Lyrics is a collection of amaroK lyrics plugins.
Panzis Lyrics amaroK-script requires amaroK 1.4 and pyKDE!
Contens:
- Local Lyrics, see also: http://www.kde-apps.org/content/show.php?content=37981
- Lyrix.at
- Leos Lyrics

editLyrics is an amarok script add, modify and edit lyrics. Just click on a track, and select "edit this lyric!" to get a full power editor!

If lyrics are already cached, you can modify it, or you can just write from zero (well, not exactly from zero, you will find the artist and trackname on the top).

Crossroads is a load balance and failover utility for TCP-based services.
Crossroads Load Balancer is a daemon program running in userspace and features extensive configurability, polling of backends using "wakeup calls", detailed status reporting, "hooks" for special actions when backend calls fail, and more.
It is service-independent; it is usable for HTTP(S), SSH, SMTP, DNS, etc.
Crossroads is a daemon that basically accepts TCP connections at preconfigured ports, and given a list of back ends distributes each incoming connection, so that a client process is served.
Additionally, crossroads maintains an internal administration of the back end connectivity: if a back end isnt usable, then the client request is handled using another back end. Crossroads will then periodically check whether a previously not usable back end has come to life yet. Also, crossroads can select back ends by estimating the load, so that balancing is achieved.
Using this approach, crossroads serves as load balancer and fail over utility. Crossroads will very likely not be as reliable as hardware based balancers, since it always will require a server to run on. This server, in turn, may become a new Single Point of Failure (SPOS). However, in situations where cost efficiency is an issue, crossroads may be a good choice.
Furthermore, crossroads can be deployed in situations where a hardware based balancing already exists and augmenting service reliability is needed. Or, crossroads may be run off a diskless system, which again improves reliability of the underlying hardware.
This document describes how to use crossroads, how to configure it in order to increase the reliability of your systems, and how to compile the program from its sources. This document is also available in PDF format.
Usage:
Crossroads is started from the commandline, and highly depends on /etc/crossroads.conf (the default configuration file). It supports a number of flags (e.g., to overrule the location of the configuration file). The actual usage information is always obtained by typing crossroads without any arguments. Crossroads then displays the allowed arguments.
This section shows the basic usage.
- crossroads start and crossroads stop are typical actions that are run from system startup scripts. The meaning is self-explanatory.
- crossroad status reports on each running service. Per service, the state of each back end is reported.
- crossroads tell service backend state is a command line way of telling crossroads that a given back end, of a given service, is in a given state. Normally crossroads maintains state information itself, but by using crossroads tell, a back end can be e.g. taken off line for servicing.
- crossroads services reports on the configured services. In contrast to crossroads status, this option only shows whats configured -- not whats up and running. Therefore, crossroads services doesnt report on back end states.
- crossroads sampleconf shows a sample configuration on screen. A good way of quicky viewing the configuration file syntax, or of getting a start for your own configuration /etc/crossroads.conf.

Console Xine Front End (CXFE) is an extremely simple front end for Xine. It is meant to be comfortable for people used to MPlayer.

So why not just use MPlayer?

While MPlayer is an excellent movie player, its dvd playback capabilties has been lacking for a long time. Besides, choice is a good thing :-) To tell the truth, CXFE was mainly created as another movie player for MMS.

Current command line parameters:

-vo < driver > Set video out driver (dxr3/xv/xshm/fb)
-ao < driver > Set audio out driver (alsa/oss)
-i < driver > Set control driver (lirc) Keyboard is enabled at all times)
-fs Start cxfe in fullscreen
< mrl > Valid xine MRL (ex: dvd:/) Up to 1000 MRLs are allowed
-v Prints cxfe version and exits
-d Start cxfe with deinterlacing plugins on
-p Specify custom deinterlacing plugin to use
--help Prints this help

Example: cxfe -vo xv -ao alsa -i lirc -dev /dev/dvd dvd:/)

Amarok Full Screen provides a full screen front end for Amarok.

The look can be changed by custom THEMES.