Free mb software for linux

iptables accounting monster (iam) is a traffic reporting tool for iptables. Currently it can generate daily reports in plain text and HTML format. It can also create summaries (month or year) of these daily reports.

While looking for a traffic reporting tool, I didnt find something that i looked for. So I started to write iam, which:

is free software
works with Linux 2.4 iptables
is written in Python, a readable language (i.e. not perl, awk or shell script)
is secure (i.e. only be root where you need to be root)
doesnt depend on a specific web server or database server
can generate reports for routers or servers
can generate reports in plain text or HTML format
can calculate costs for traffic (currently only price per MB, but bulk discounts should be included soon)

TiEmu is an emulator of Texas Instruments hand-helds (TI89/92/92+/V200). TiEmu is full-featured with a graphical debugger.
Main features:
- support TI89, TI89 Titanium, TI92, TI92+ and V200PLT hand-helds
- full-featured graphical debugger (source, memory, breakpoints, traps, vectors, stack, trace, ...)
- debugger supports : run, step in, step over, step out, run to cursor
- ability to load/save the emulator state
- file linkport emulation (direct loading of files)
- works with 1/2/4 MB ROMs, 128 or 256 KB RAM
- emulate HW1, HW2, and HW3
- can run from ROM dumps or FLASH upgrades
- automatic ROM version/model detection
- constrast emulated (try [Alt] + [+] & [-])
- pretty fast emulation engine
- sreenshot of LCD and/or calculator in several images format (JPG/PNG/ICO)
- TI keyboard useable directly from PC keyboard or with the mouse on the skin
- archive memory support as well as ghost spaces
- full emulation of HW1/2/3 protection (stealth I/O)
- no buggy MC68000 SR & nbcd (TiEmu cant be detected as VTi : you have true emulation)
- 4-level and 7/8-level grayscale support (thx Kevin !) for both HW1 and HW2/3
- the letter keys are aliased to produce their respective letters. No need to press the Alpha key, just type (TI89).
- keyboard mapping and menu shortcuts are fully VTi-compatible
- keyboard mapping can be customized thru keymaps files
Version restrictions:
- linkport emulation has not been tested with USB cable yet
- no debugger while sending/receiving a file to/from the virtual calculator
- no linkport logging capabilities yet

WARNING:
This program is designed to heavily load CPU chips. Undercooled, overclocked or otherwise weak systems may fail causing data loss (filesystem corruption) and possibly permanent damage to electronic components. Nor will it catch all flaws.
USE AT YOUR OWN RISK

CPU testing utilities in optimized assembler for maximum loading P6 (Intel Pentium Pro/II/III and Celeron TM), AMD K7 (Athlon/Duron/Thunderbird TM) AMD K6, and Intel P5 Pentium chips. This is free software, copyright but freely licenced under the GNU Public Licence copyleft.

These programs are designed to load x86 CPUs as heavily as possible for the purposes of system testing. They have been optimized for different processors. FPU and ALU instructions are coded an assembler endless loop. They do not test every instruction. The goal has been to maximize heat production from the CPU, putting stress on the CPU itself, cooling system, motherboard (especially voltage regulators) and power supply
(likely cause of burnBX/MMX errors).

burnP5 is optimized for Intel Pentium w&w/o MMX processors
P6 is for Intel PentiumPro, PentiumII&III and Celeron CPUs
K6 is for AMD K6 processors
K7 is for AMD Athlon/Duron processors
MMX is to test cache/memory interfaces on all CPUs with MMX
BX is an alternate cache/memory test for Intel CPUs

TO USE: root priviliges are NOT required. It has been designed for ELF Linux, but also tested under FreeBSD. and a.out. Burn Testing is best done from a ramdisk distribution (tomsrtbt) or with filesystems unmounted or mounted read-only.

untar the source in a convenient directory:
`tar zxf cpuburn`

compile excutables
`make`

run desired program in background [ _repeat_ for SMP]:
`burnP6 || echo $? &`

Monitor progress of cpuburn by `ps`. When finished, `kill` the burn* process(es). If you have temperature probes (fingers) or the lm-sensors package, you can check your CPU temperature and/or system voltages.

If an error occurs in calculations, it will be preserved, and the program will terminate with error code 254 for an integer/memory error, and error code 255 for a FP/MMX error. Error checking happens every 10-40 sec for burnP6/K6/K7 and I havent seen any CPU errors in testing [lockups occur first]. burnBX and burnMMX check for error every 512 MB (4-10 sec), and error termination is frequently seen, lockups are rarer.

burnBX and burnMMX are essentially very intense RAM testers. They can also take an optional parameter indicating the RAM size to be tested:

A = 2 kB E = 32 kB I = 512 kB M = 8 MB
B = 4 F = 64 J = 1 MB N = 16
C = 8 G = 128 K = 2 O = 32
D = 16 H = 256 L = 4 P = 64

`burnBX L` (4 MB) and `burnMMX F` (64 kB) are the default sizes. A-E mostly test L1 cache, F-H test L2 cache, and H-P force their way to RAM. But even A-E will have some cacheline writeouts to RAM.

In spite of its name, burnBX can be run on any chipset [RAM controller] and tests alot more than the RAM controller. Unfortunately, burnBX is not optimal on AMD processors. burnMMX is preferable for any CPU that has an MMX unit.

burnBX/MMX needs about 72 MB of total RAM + swap to start (not necessarily free), but doesnt use this much unless you request it. They will throw a `Sig 11` if you dont have enough swap.

If you dont want to add more, you can adjust the .bss section downward as indicated in the source comments. They can also test swap, and at least on my system, I can run 2*`burnBX 8` with 128 MB SDRAM with some use of swap, but no excessive thrashing[seeks]. YMMV.

If sub-spec, your system may lock up after 2-10 minutes. It shouldnt. burn* are just an unpriviliged user processes. But it probably means your CPU is undercooled, most likely no thermal grease or other interface material between CPU & heatsink. Or some other deficiency. A power cycle should reset the system. But you should fix it.

MINIX 3 is a new open-source operating system designed to be highly reliable and secure. This project is based somewhat on previous versions of MINIX, but is fundamentally different in many key ways.
MINIX 1 and 2 were intended as teaching tools; MINIX 3 adds the new goal of being usable as a serious system on resource-limited and embedded computers and for applications requiring high reliability.
This new OS is extremely small, with the part that runs in kernel mode under 4000 lines of executable code. The parts that run in user mode are divided into small modules, well insulated from one another.
For example, each device driver runs as a separate user-mode process so a bug in a driver (by far the biggest source of bugs in any operating system), cannot bring down the entire OS.
In fact, most of the time when a driver crashes it is automatically replaced without requiring any user intervention, without requiring rebooting, and without affecting running programs. These features, the tiny amount of kernel code, and other aspects greatly enhance system reliability.
MINIX 3 is initially targeted at the following areas:
- Applications where very high reliability is required
- Single-chip, small-RAM, low-power, $100 laptop for Third-World children
- Embedded systems (e.g., cameras, DVD recorders, cell phones)
- Applications where the GPL is too restrictive (MINIX 3 uses a BSD-type license)
- Education (e.g., operating systems courses at universities)
Main features:
- POSIX compliant
- Networking with TCP/IP
- Two ANSI C compilers (ACK and gcc)
- Over 300 UNIX programs
- Many improvements since V2
- Full multiuser and multiprogramming
- Support for memory up to 4 GB
- Device drivers run as user processes
- Full C source code supplied
- Runs on 386, 486, Pentium, etc.
To run MINIX 3, you need a PC driven by a 386, 486, or Pentium CPU or compatible. The standard configuration requires 16 MB of RAM. An 8-MB version is also available, but it is slower due to a smaller buffer cache. Since the distribution comes on a live CD, you can test it without allocating any hard disk space, but for a hard disk installation, 200 MB is needed as a minimum, 400 MB minimum if you want all the sources.

m0n0wall is a project aimed at creating a complete, embedded firewall software package that, when used together with an embedded PC, provides all the important features of commercial firewall boxes (including ease of use) at a fraction of the price (free software).
m0n0wall is based on a bare-bones version of FreeBSD, along with a web server, PHP and a few other utilities. The entire system configuration of m0n0wall is stored in one single XML text file to keep things transparent.
m0n0wall is probably the first UNIX system that has its boot-time configuration done with PHP, rather than the usual shell scripts, and that has the entire system configuration stored in XML format.
Main features:
- web interface (supports SSL)
- serial console interface for recovery
- set LAN IP address
- reset password
- restore factory defaults
- reboot system
- wireless support (access point with PRISM-II/2.5/3 cards, BSS/IBSS with other cards including Cisco)
- captive portal
- 802.1Q VLAN support
- stateful packet filtering
- block/pass rules
- logging
- NAT/PAT (including 1:1)
- DHCP client, PPPoE, PPTP and Telstra BigPond Cable support on the WAN interface
- IPsec VPN tunnels (IKE; with support for hardware crypto cards and mobile clients)
- PPTP VPN (with RADIUS server support)
- static routes
- DHCP server
- caching DNS forwarder
- DynDNS client
- SNMP agent
- traffic shaper
- SVG-based traffic grapher
- firmware upgrade through the web browser
- Wake on LAN client
- configuration backup/restore
- host/network aliases
Enhancements:
- added voucher support to captive portal (mwiget); wireless LAN improvements; allow dashes in alias names; added hidden option to disable auto-generation of PPTP rules on WAN; fixed ATA hard disk spin down feature; ipfilter TCP window scaling bug fix; synced with changes from 1.23 branch; increased mfsroot size to 14 MB (from 13 MB); updated base system to FreeBSD 6.2-RELEASE-p6; updated PHP to 4.4.7, ipsec-tools to 0.6.7, isc-dhcpd to 3.0.5, Dnsmasq to 2.39; added kernel patch for fragment bug in ipfilter; modified kernel patch to handle ipnat+dummynet in ip_input....

grml-small is a bootable CD (Live-CD) based on Knoppix and Debian. grml-small includes a collection of GNU/Linux software for system administrators and provides automatic hardware detection.

Whereas grml (without the -small) provides more than about 2.1GiB of software on a 700MB-ISO, grml-small is a very small rescue system for systemadministrators.

It is not necessary to install anything to a harddisk, you dont even need a harddisk to run it. Due to on-the-fly decompression grml-small includes about 150 MB of software and still fits on a business card CD-ROM or USB device with 50MB.

Initial release of grml-small, a very small version of the grml-system. Notice that there are several hacks to reduce the ISO-size, so you wont find for example documentation and manpages on the ISO.

grml-small provides support for booting via USB, see http://wiki.grml.org/doku.php?id=usb for details.

Kernel is based on vanilla kernel 2.6.12 including several patches (MPPC/MPPE, Reiser4, Squashfs,...) but compared with the normal grml system the kernel features have been reduced. See http://grml.org/kernel/ for more details.

MP-MPICH provides a Multi-platform MPI implementation.

MP-MICH is a Multi-platform uniform MPI implementation, based on MPICH and SCI-MPICH, resulting in a high performance, consistent MPI across both ethernet and SCI networks in a hybrid environment. There is a single, standardized source tree for all platforms. It is compliant with the MPI-1 standard.

MP-MPICH uses one common source tree for this purpose. It has a new device for Windows NT/2000/2003 to communicate via sockets, and an adapted shared memory device for SMP systems. Additionally, MP-MPICH is a superset of SCI-MPICH, that means that it includes another new device to support direct communication via a fast SCI interconnect. With SCI-MPICH, inter-process message latencies for small messages (for processes running on separate nodes) below 4 us are achieved, and the current measured maximum inter-node (PingPong-)bandwidth is at about 310 MB/s.

In fact, the development of MP-MPICH started when the first release of SCI-MPICH was finished. This release was designed for Solaris and Linux, but since it uses our SMI library which is also available for Windows NT, we thought it would be fun to port SCI-MPICH to NT. The initial port took only 4 hours and we were up and running with SCI-MPICH for NT. The additional/modified devices which are necessary to use MPICH on NT without these extremely fast SCI boards required more time to develop.