Free ram software for linux

SuperRescue is a single very large bootable system-on-a-disk. Its based on the observation that the vast majority of systems allow you to do so much more than the minimal system.

Therefore, it isnt for everything, but for most desktop systems, it provides a much nicer rescue environment than your average rescue floppy.

It requires an i386 PC with 24 MB of RAM and a bootable CD-ROM. PCMCIA support is implemented but somewhat limited. It is based on RedHat 7. (Version 1 is based on RedHat 6.)

Quick and dirty perl script to allow you to log directly into games via GDM, making sure you have the maximum RAM and CPU time for the game.

It uses a simple XML config file to control its various options, and supports controlling driver settings for Nvidia cards. See the README for more info.

FoxTorrent is a Firefox extension that lets you stream torrents as they download, from your web browser, with zero configuration needed.
Main features:
Streaming Fast Delivery
- Watch video and listen to audio as it downloads.
Complete Firefox Integration
- Manage your torrent downloads from your browser window.
Windows, Mac, and Ubuntu Linux
- Consistent downloading experience across all three platforms.
Background Downloading
- Continues to work even after your browser window has been closed.
Low Resource Footprint
- Foxtorrent uses less than 8 MB of RAM, and doesnt hog bandwidth.
Configuration-Free
- Automatic support for NATs, uPNP, and firewalls, with no tinkering necessary.

UAE is a mostly complete software emulation of the hardware of the Commodore Amiga 500/1000/2000.
A Commodore Amiga, for those who dont know, is a 16/32 bit computer system based on the Motorola 680x0 CPU and a few specially designed custom chips that provide very good graphics and sound capabilities. Its first incarnation, the A1000, appeared in 1985, followed by the highly successful A500 and A2000 models.
UAE is written for Unixish systems; it is developed on a Linux machine but it should compile and run on any half-recent Unix-like operating system. It has also been ported to a wide variety of machines and operating systems, including DOS, Windows 95/NT, MacOS, RiscOS, BeOS and NextStep.
UAE is free software: you are welcome to distribute copies of it and/or modify it, under certain conditions. There is no warranty of any kind for UAE. For more details concerning these issues, please read the GNU General Public License, which describes the terms under which UAE is distributed.
Main features:
- A 68000/010/020/040 CPU, optionally a 68881 FPU
- OCS, ECS and AGA Graphics Chipset (including sprite-playfield collisions)
- Up to 2MB Chip RAM and up to 8MB Fast RAM, or 8MB Chip RAM without Fast RAM
- Up to 64MB Zorro III Fast RAM, independent of Chip RAM setting (68020+ only)
- Up to 1MB Slow RAM, for extended compatibility with problem software
- Up to 8MB of graphics card memory, usable by software that supports Picasso 96 compatible graphics cards
- 4 x 3.5" floppy disk drives (DF0:, DF1:, DF2: and DF3:). Its not possible to read Amiga disks, so these are emulated with disk files.
- A hard-disk: either a harddisk image file or part of the native filesystem
- Joystick support (with option of mapping joystick to numeric keypad)
- Mouse support
- Ability to run in various screen modes (for better display quality or better speed)
- Full stereo sound support, consisting of 4 x 8bit channels
- Simple parallel and serial port support. Note: the parallel port is not really implemented. Though its sufficient for printing.
- state-saving. you can save the state of your emulated Amiga and continue later on.
- some other things which dont work well enough to mention them here...

SPBLinux is a modular mini distribution that runs completely in RAM.
SPBLinux can be booted from USB, based on Busybox and Midnight Commander, optional with DirectFB and (since version 2.1) Mozilla; it is possible to create/modify own modules inside SPBLinux.
Main features:
- loads from USB storage or other boot devices
- runs in RAM; after bootup no access to boot device required
- modular:
- basic system fits on two 1.4 MB floppy disks (Linux 2.6 with midnight commander)
- all other components are added as addons: bz2 (and sqf) files in subfolders of folder spblinux on the boot device
- choice which addon subfolders are loaded is at boot time (grub menu and/or grub edit); command loadaddon allows to load addons manually when SPBLinux is running.
- SPBLinux can be built and modified inside SPBLinux
- the command changebz2 your_addon.bz2 opens the addon with midnight commander
- if the gentoo chroot environment is installed, programs can be emerged and compiled
- more information is in the SPBLinux Wiki
- targeted users:
- users who want to create their own customized system
- support and documentation:
- installation on fat formatted USB devices
- run SPBLinux and use the scrip makebootable
Enhancements:
- SPBLinux runs smoothly and fast inside coLinux:
- standard disclaimer: coLinux and the X server XMing are beta software and might crash your pc
- Scribus 1.23 compiled for Linux runs as as window of Windows XP (screenshot)
- (the package scribus-spb2-colinux-xp.zip contains all required components)
- english (default) and german user interface preconfigured
- access from SPBLinux to Windows by a shared folder
- user who want to make their own customized version of SPBLinux/coLinux can start with minimal-spb2-colinux-xp.zip
- SPBLinux, only textmode (if graphical programs are wanted the scribus package should be used as starting point)
- ssh daemon running (default root password is root)
- optional, access from SPBLinux to Windows by a shared folder

ftRTOS is another free and small realtime kernel for microcontrollers focused on minimal RAM usage. The "ft" prefix means femto, the next order after nano and pico.
Primarily this kernel is intended for MSP430 family of microcontrollers. Porting to another architectures is quite simple but on some architectures performance may degrade.
The source code is written in pure C. The preference is given to GCC as free software should be compiled with a free compiler. Assembly language is used only where it is unavoidable.
Main features:
- Minimal use of RAM. For example, on MSP430 in minimalistic configuration it is required only 6 bytes of RAM per task not including stack.
- Static definition of tasks and protected shared objects.
- Multiple levels of priority, fixed priority scheduling. By design, the number of levels is limited by the maximum number that unsigned char data type can hold.
- Preemptive or cooperative scheduling policy.
- Unlimited number of tasks by design.
- No idle task.
- Simplicity and clarity as a design philosophy.
Two approaches are used to achieve the main design goal: avoiding dynamic memory management and splitting all structures into two parts.
Dynamic memory management adds overhead to all memory blocks and requires some additional code. Without dynamic memory management it is impossible to dynamically create tasks and synchronization objects (more precisely, protected shared objects, PSO). But for tiny systems it is not a key feature. So, all tasks and PSOs are defined at compile time.
Splitting structures that describe tasks and PSO means that they have constant (ROMable) and variable parts. The first one contains static properties, such as priority, address of entry point, address of stack, etc. The variable part is placed in RAM and contains only those properties that require changes at run time.
It is necessary to note that such division requires frequent access to the flash/ROM and on some architectures it may lead to performance degradation. For example in AVR family the access to the flash memory is very painful.
The simplicity of kernel as a design philosophy obliges to implement only minimal set of functions and only those which are absolutely necessary. Theres only one global critical section which disables context switching. There are no functions to suspend and resume tasks (their appearance in user code tells that something wrong in software design). Only one type of PSO, namely queue, is used for communications between tasks.
However, sticking to minimalistic design leads to inflexibility. Therefore in addition to minimalistic design a list-based design has been implemented. The user can choose either. The differences and features will be explained later. Generally, list-based design increases the size of variable part of task structure (on MSP430 it becomes 12 bytes) but allows several waiting tasks on each side of PSO, the priority inversion problem is handled (the users choice) and other types of PSO may be implemented.

Iroffer is a software program that acts as a fileserver for IRC. It is similar to a FTP server or WEB server, but users can download files using the DCC protocol of IRC instead of a web browser.
Unlike similar programs, iroffer is not a script, it is a standalone executable written entirely in c from scratch with high transfer speed and effeciency in mind. iroffer has been found to transfer over 50MByte/sec over a gigabit ethernet connection.
Main features:
- extremely fast dcc transfers
- extremely low cpu usage, and reasonable ram usage
- supports dcc resume
- set max amount of transfers per hostnames
- supports virtual hosts
- bandwidth monitoring, shows last 2 minutes bandwidth average
- maximum bandwidth limiting
- auto-ignores flooders
System requirements:
- Windows/Linux