Free pain software for linux

Downloader for X is a Linux/Unix userfriendly program with nice X interface to download files from the Internet. It supports both FTP and HTTP protocols, supports resuming (of course if server side supports it) and makes downloading files from internet easy. Downloader for X is an analogue for Linux/Unix of such famous applications for Windows as ReGet, Go!Zilla and GetRight.
Of course this program is not a copy of any of programs above. Downloader for X was written from scratch by me in the hope to decrease a pain of downloading many files from Internet even on really bad modem lines. But if you are happy owner of T1 connection then D4X is for you too because It can use this bandwidth completely! And this is not a end of the list of Downloader for Xs features!
Not completed list of key features:
- Supporting both FTP and HTTP protocols as well as HTTP and FTP proxy servers. SOCKS5 support is also included! Authentication on the proxy servers is supported too.
-The Program keep the logs of all download sessions that allows advanced user to monitor problems manualy according information from these logs.
- It allows users to manage their downloads in real time. User can pause, continue, move in queue, add new downloads and remove downloads manualy. User also can allow to remove completed or failed downloads automatically by the program.
- Recursive downloading via FTP as well as via HTTP is supported. Powerful Filters-manager allow advanced user to specify files which must to be downloaded and files which must to be skipped. Wildcards are supported for FTP downloads too.
- Ability to download in more than one connection per time. Usualy downloading using number of connections increases speed of downloading up to 300% and even more!
- Supporting of so called `Persistent connections increases speed of downloading due much less amount of `standing connection stages. With this feature D4X uses connections to the servers many times. Persistent connections over HTTP are supported automaticaly but persistent connections over FTP can be turned on by user (Do not send QUIT command option of FTP settings).
- Ability to limit download speed of separate file as well as for the whole program allows modem user browse through the Web and download files at the same time.
- Built-in Scheduller, URL-manager and Automatically adding allow advaced user to simplify managing downloads by various criterias.
- Multiqueued design, ability to run without X interface, ability to manage D4X via command line and many other features will satisfy anybody who find a time to learn this program.

Drupal is a powerful web content management system that allows an individual or community of users to easily publish and maintain a website. Drupal has a large community suporting it that has created many modules for common tasks that you would want to perform on a website. Drupal Content Management System JumpBox bundles Drupal version 5.1.

WHY USE A JUMPBOX

Its Simple

Open Source applications are great. The applications are powerful, inexpensive and get the job done. But installing and configuring those applications can be a pain. A JumpBox delivers Open Source applications in a way that makes them simple to try, run and operate.

Its Quick

Actually downloading a JumpBox will take the most time. Once thats done, youre just a few minutes from having a working application that can serve multiple users.

Its Portable

A JumpBox collects the application, application dependancies and all application data into a single bundle that can easily be moved from one computer to another. This allows you to start running the application on your desktop and then as usage grows move it to a server without needing to reinstall or reconfigure. Plus with support for Mac OS X, Windows and Linux you can even move the application between platforms with little effort.

Its Safe

Manually installing Open Source applications not only takes a lot of time and effort, but when youre done its still left to you to figure out how to protect the data the application manages. With a JumpBox its easy to add automatic backups of the entire state of the application.

Its Virtual

A JumpBox application is a virtual appliance that bundles the open source application and all its runtime dependancies into a single package that runs on top of virtualization software from VMWare, Parallels or Xen. This means all JumpBox applications automatically gain the benefits of traditional server virtualization and can be dropped into existing virtualization infrastructure when available.

Its Comfortable

JumpBox provides a consistent runtime environment for all applications that we bundle. The applications may differ considerably, but their installation and operation will be familiar no matter which JumpBox you choose.

DokuWiki is a simple, clean and easy to use wiki system that allows collaborative editing of a web site. Its focused on creating documentation for developer teams, workgroups and small companies. DokuWiki Wiki JumpBox bundles DokuWiki version 2007.05.24

WHY USE A JUMPBOX

Its Simple

Open Source applications are great. The applications are powerful, inexpensive and get the job done. But installing and configuring those applications can be a pain. A JumpBox delivers Open Source applications in a way that makes them simple to try, run and operate.

Its Quick

Actually downloading a JumpBox will take the most time. Once thats done, youre just a few minutes from having a working application that can serve multiple users.

Its Portable

A JumpBox collects the application, application dependancies and all application data into a single bundle that can easily be moved from one computer to another. This allows you to start running the application on your desktop and then as usage grows move it to a server without needing to reinstall or reconfigure. Plus with support for Mac OS X, Windows and Linux you can even move the application between platforms with little effort.

Its Safe

Manually installing Open Source applications not only takes a lot of time and effort, but when youre done its still left to you to figure out how to protect the data the application manages. With a JumpBox its easy to add automatic backups of the entire state of the application.

Its Virtual

A JumpBox application is a virtual appliance that bundles the open source application and all its runtime dependancies into a single package that runs on top of virtualization software from VMWare, Parallels or Xen. This means all JumpBox applications automatically gain the benefits of traditional server virtualization and can be dropped into existing virtualization infrastructure when available.

Its Comfortable

JumpBox provides a consistent runtime environment for all applications that we bundle. The applications may differ considerably, but their installation and operation will be familiar no matter which JumpBox you choose.

MediaWiki is a powerful wiki engine originally developed for the Wikipedia project and now deployed on many sites around the world. This JumpBox includes MediaWiki version 1.9.3.

A JumpBox is a virtual appliance that bundles a server based application along with all of its dependancies (database, operating system, libraries and management interface) into a single pre-configured unit. This makes deploying that application drop dead simple and gives you a working application in minutes for what would normally take hours.

WHY USE A JUMPBOX

Its Simple

Open Source applications are great. The applications are powerful, inexpensive and get the job done. But installing and configuring those applications can be a pain. A JumpBox delivers Open Source applications in a way that makes them simple to try, run and operate.

Its Quick

Actually downloading a JumpBox will take the most time. Once thats done, youre just a few minutes from having a working application that can serve multiple users.

Its Portable

A JumpBox collects the application, application dependancies and all application data into a single bundle that can easily be moved from one computer to another. This allows you to start running the application on your desktop and then as usage grows move it to a server without needing to reinstall or reconfigure. Plus with support for Mac OS X, Windows and Linux you can even move the application between platforms with little effort.

Its Safe

Manually installing Open Source applications not only takes a lot of time and effort, but when youre done its still left to you to figure out how to protect the data the application manages. With a JumpBox its easy to add automatic backups of the entire state of the application.

Its Virtual

A JumpBox application is a virtual appliance that bundles the open source application and all its runtime dependancies into a single package that runs on top of virtualization software from VMWare, Parallels or Xen. This means all JumpBox applications automatically gain the benefits of traditional server virtualization and can be dropped into existing virtualization infrastructure when available.

Its Comfortable

JumpBox provides a consistent runtime environment for all applications that we bundle. The applications may differ considerably, but their installation and operation will be familiar no matter which JumpBox you choose.

OpenScientist is an integration of open source products working together to do scientific visualization and data analysis, in particular for high energy physics (HEP).
The project is definitely NOT one million lines of intricated and unnecessary complicated home made code reinventing everything.
Motivations
Experiments in high energy and nuclear physics need to be at the edge of computing technologies but at the same time have to face a very long life time (LHC experiments are going to be a matter of decades). This involves that the software must be organized in a way that permits to include or discard some technologies in an easy way without having to recode everything at each change of a piece.
For data analysis, the HEP community had used the CERN/PAW tool for years. Whilst this program had been used and is probably still used by hundred of physicists in the world, it is not any more maintained by the lab that created and promoted it : CERN. This lab had not been able to establish long term collaborative software engineering plans in order to have a technical follow up of this program and analysis tools in general. (What is astounding, is that the same people that were behind CERN/PAW come now with another tool (ROOT) which has exactly the same engineering defects).
OpenScientist is first of all an architecture trying to handle the problem differently to avoid upseting huge software phase transitions in the future. The key points of the system are the modularity and the openness. See the Languages, Coarse graining architecture, and The file formats intrinsic pain section for more about the technical choices and design.
Enhancements:
- An HDF5 driver was introduced in BatchLab.
- The build system was replaced with obuild.
- Support for CoinPython was added.
- Initial support was added for both Qt4 and SDL.
- Examples were added.
- Assorted code cleanups and speedups were done.

Module::Install::Philosophy Perl module contains the concepts behind Module::Install.

SYNOPSIS

This document describes the personal philosophy behind the creation of CPAN::MakeMaker (the predecessor of Module::Install). The views expressed here belong to Brian Ingerson; if they are not of interest to you, you can safely ignore this document.

The above is obviously a mutation of the monumental speech by great Martin Luther King (http://web66.coled.umn.edu/new/MLK/MLK.html). While the contexts are vastly different, I feel that there are some serious parallelisms.
The CPAN has become a place that is not free of injustice. This situation has arisen not out of directed oppression, but from a failure of our community to keep its tools sharp. It is the culmination of many small decisions made in the name of practicality. This is a sad state for an institution that was created to allow all interested people to contribute equally to the best of their ability.

This assertion is rooted in my personal experience as an author. When I created my first Perl module, Inline.pm, I knew that I had done something important. But how was I to make a dent in vast Perl community?

As a complete unknown in the Perl community, my voice did not travel far. I repeatedly tried to get even an acknowledgment from the gurus familiar with XS. No success. I resorted to sending messages with ridiculous subjects to modules@perl.org. (http://www.xray.mpe.mpg.de/mailing-lists/modules/2000-08/msg00078.html) No response. Through sheer determination and shameless self-promotion I eventually got the word out, and I hope the world is a slightly better place for it.
Since then, Inline has won awards and I have had the privilege to meet almost all of Perls finest. But I still remember the pain of starting out, and want to help invite more people into this wonderful world.

One thing I have learned from experience is that the Perl community (and throw in the Python and Ruby people as well) is a small drop in the vast ocean of programming. Its a giant pot of Java out there; and a sea of C. Perl may not be the biggest fish, but with some care and cunning we could become a much bigger school.

These are the current problems that I see with CPAN and the core modules:

New Modules dont help Older Perls
If I were to guess what percent of all Perl5 installations were at the current release level (5.8.0 in October 2002) I would say 3-5%. That may even be generous. Id say that over 40% of installations might still be at 5.005 or earlier.
The biggest problem with adding a module to the core is that it only helps a small subset of Perl users for a long long time. Worse yet, a good module author will still probably avoid using the core additions as prerequisites, because they want their new module to work as well on 5.005 as on 5.8.
CPAN::MakeMaker should be able to help in this regard. For example, instead of putting Inline.pm into the core for 5.9, I can now effectively get it into the core for every version of Perl that Inline supports.
Author Exclusiveness
Not just anybody can get a module into the core. It seems you have to know people in high places. If I were a brilliant new talent with a great new module, it would have a harder time getting the ear of the pumpking, then if I were, say, Damian Conway. In fact, I probably wouldnt even know where to start.
Reduced Competition
One comment Ive heard from some very good Perl programmers is "Everything important has already been done". Their feeling is that even though a module is suboptimal, it would be a waste of time to write a competing module. Who would use it instead of the one already in the core?
When I write a competing module, I know that I have to make it at least twice as good as the existing one to even get noticed. Thats not a bad thing, but should everybody be forced into that situation?
For example, lets say that you have created a really useful CGI script. Lets also say that it makes use of your own CGI::Special module, because CGI.pm doesnt meet your needs. Even though your script might be generally useful and worth sharing, the fact that it requires a non-standard module can only negatively affect its acceptance. Trying to get general acceptance for the superior CGI::Special module will be harder still.
Core modules are assumed by the general public to be "Best of Breed". While this may be true for some modules at some point in time, it keeps talented people from attempting to "breed" something better.
Core Bloat
Every time we add a module to the core it gets bigger and bigger. And we cant ever remove modules from the core, once theyve been added.
If I had my druthers, wed remove all modules from the core that werent necessary for either running Perl or installing modules. Of course, wed need to set things up so that installing modules was so easy, that it could be done on the fly if necessary. Is this easily accomplishable? Nope. Is it impossible? Nope. We have the best language in the world to help us do it!
Maintenance Bitrot
Believe it or not, Perl authors can sometimes acquire a "Life Beyond Perl". They get families or new hobbies or even hit by a bus. (This would be a "Death Beyond Perl".) The fact is, that once somebody writes a piece of code and shares it with the world, they are expected to maintain it for all time.
That is being generous. There are others that think that once their module has become popular or made it into the core, they dont need to keep fixing and improving it. I have personally been guilty of this sin.
And then theres the Damian Conway Effect. This plagues the exceptional authors who are so innovative and prolific they simply dont have time to maintain everything they have written.

I initially formalized these opinions at the YAPC (Yet Another Perl Conference) in June 2001. Since then I have been trying to think of technological solutions to fix these social problems.

One idea was dubbed NAPC. NAPC is CPAN backwards. It is a large system of precompiled modules that can be installed on the fly, with the goal of reducing the number of modules in the core. NAPC hasnt got started yet. Id still like to do it someday, but its a big problem with a lot of issues.

CPAN::MakeMaker (and now Module::Install) on the other hand, is simple and ultimately flexible. It should work with all of the existing CPAN processes without requiring any changes from them. And new features can be continuously added. Even though it doesnt scratch all of my philosophical CPAN itches, its a good start.

Math::ODE Perl module allows you to solve N-th Order Ordinary Differential Equations with as little pain as possible.

Currently, only IVPs (initial value problems) are supported, but native support for BVPs (boundary value problems) may be added in the future. To solve N-th order equations, you must first turn it into a system of N first order equations, as in MATLAB.