Free visualize disk usage software for linux

Example NAT usage is a little script to show a NAT usage example.

Sample:

#----------------------#
# Variable Definitions #
#----------------------#

EXT=eth0
INT=eth1

# "Masquerading" Example
PRIV_NETS="128.111.1.1 128.111.185.0/255.255.255.0"
MASQ_NET=192.168.1.0/255.255.255.0

# "General SNAT" Example
MAP_FROM=192.168.1.0/255.255.255.0
MAP_TO=128.111.185.30-128.111.185.42

# "Redirection" Example
INTERNAL_IP=10.10.1.1

# "Port Forwarding" Example
EXTERNAL_IP=128.111.1.200
NEWS_SERVER=10.10.1.38
MAIL_SERVER=10.10.1.69

# "Load Balancing" Example
VIRTUAL_SERVER=news.sblug.com
SERVER_RANGE=10.10.1.9-10.10.1.15

#-------------#
# NAT Section #
#-------------#

#
# Flush previous rules
#

iptables -t nat -F


#
# Masquerading
#

# Masquerading for outgoing connections, except privileged nets are exempt
for NET in $PRIV_NETS ; do
iptables -t nat -A POSTROUTING -d $NET -o $EXT -j ACCEPT
done
iptables -t nat -A POSTROUTING -s $MASQ_NET -o $EXT -j MASQUERADE


#
# General SNAT
#

# Internal computers w/ private ips "borrow" public ips of other internal computers to ssh out
iptables -t nat -A POSTROUTING -s $MAP_FROM -o $EXT -p tcp --dport ssh -j SNAT --to-source $MAP_TO
iptables -t nat -A POSTROUTING -s $MAP_FROM -o $EXT -p udp --dport ssh -j SNAT --to-source $MAP_TO


#
# Redirection
#

# Redirect internal net http traffic through squid proxy, but allow direct access to local web server
iptables -t nat -A PREROUTING -i $INT -d ! $INTERNAL_IP -p tcp --dport www -j REDIRECT --to-port 8080


#
# Port Forwarding
#

# Forward gateway port 7000 to news server and gateway port 8000 to pop mail server
iptables -t nat -A PREROUTING -d $EXTERNAL_IP -p tcp --dport 7000 -j DNAT --to-dest $NEWS_SERVER:nntp
iptables -t nat -A PREROUTING -d $EXTERNAL_IP -p tcp --dport 8000 -j DNAT --to-dest $MAIL_SERVER:pop3

#
# Load Balancing
#

# Basic load balancing by redirecting nntp requests to any of several local news servers
iptables -t nat -A PREROUTING -d $VIRTUAL_SERVER -p tcp --dport nntp -j DNAT --to-dest $SERVER_RANGE

Super Grub Disk is a bootable floppy or CDROM that is oriented towards system rescue, specifically for repairing the booting process.

Super Grub Disk is simply a Grub Disk with a lot of useful menus.

It can activate partitions, boot partitions, boot MBRs, boot your former OS (Linux or another one) by loading menu.lst from your hard disk, automatically restore Grub on your MBR, swap hard disks in the BIOS, and boot from any available disk device.

Super Grub Disk project has multi-language support, and allows you to change the keyboard layout of your shell.

AppleII::Disk is a Perl module for block-level access to Apple II disk image files.

SYNOPSIS

use AppleII::Disk;
my $disk = AppleII::Disk->new(image.dsk);
my $data = $disk->read_block(1); # Read block 1
$disk->write_block(1, $data); # And write it back :-)

AppleII::Disk provides block-level access to the Apple II disk image files used by most Apple II emulators. (For information about Apple II emulators, try the Apple II Emulator Page at http://www.ecnet.net/users/mumbv/pages/apple2.shtml.) For a higher-level interface, use the AppleII::ProDOS module.
AppleII::Disk provides the following methods:

$disk = AppleII::Disk->new($filename, [$mode])

Constructs a new AppleII::Disk object. $filename is the name of the image file. The optional $mode is a string specifying how to open the image. It can consist of the following characters (case sensitive):

r Allow reads (this is actually ignored; you can always read)
w Allow writes
d Disk image is in DOS 3.3 order
p Disk image is in ProDOS order

If you dont specify d or p, then the format is guessed from the filename. .PO and .HDV files are ProDOS order, and anything else is assumed to be DOS 3.3 order.

If you specify w to allow writes, then the image file is created if it doesnt already exist.

$size = $disk->blocks([$newsize])

Gets or sets the size of the disk in blocks. $newsize is the new size of the disk in blocks. If $newsize is omitted, then the size is not changed. Returns the size of the disk image in blocks.

This refers to the logical size of the disk image. Blocks outside the physical size of the disk image read as all zeros. Writing to such a block will expand the image file.

When you create a new image file, you must use blocks to set its size before writing to it.

$contents = $disk->read_block($block)

Reads one block from the disk image. $block is the block number to read.
$contents = $disk->read_blocks(@blocks)

Reads a sequence of blocks from the disk image. @blocks is a reference to an array of block numbers. As a special case, block 0 cannot be read by this method. Instead, it returns a block full of 0 bytes. This is how sparse files are implemented. If you want to read the actual contents of block 0, you must call $disk->read_block(0) directly.

$contents = $disk->read_sector($track, $sector)

Reads one sector from the disk image. $track is the track number, and $sector is the DOS 3.3 logical sector number. This is currently implemented only for DOS 3.3 order images.

$disk->fully_allocate()

Expands the the physical size of the disk image file to match the logical size of the disk image. It will be expanded as a sparse file if the filesystem containing the image file supports sparse files.

$disk->write_block($block, $contents, [$pad])

Writes one block to the disk image. $block is the block number to write. $contents is the data to write. The optional $pad is a character to pad the block with (out to 512 bytes). If $pad is omitted or null, then $contents must be exactly 512 bytes.

$disk->write_blocks(@blocks, $contents, [$pad])

Writes a sequence of blocks to the disk image. @blocks is a reference to an array of block numbers to write. $contents is the data to write. It is broken up into 512 byte chunks and written to the blocks. The optional $pad is a character to pad the data with (out to a multiple of 512 bytes). If $pad is omitted or null, then $contents must be exactly 512 bytes times the number of blocks.

As a special case, block 0 cannot be written by this method. Instead, that block of $contents is just skipped. This is how sparse files are implemented. If you want to write the contents of block 0, you must call $disk->write_block directly.

$disk->write_sector($track, $sector, $contents, [$pad])

Writes one sector to the disk image. $track is the track number, and $sector is the DOS 3.3 logical sector number. $contents is the data to write. The optional $pad is a character to pad the sector with (out to 256 bytes). If $pad is omitted or null, then $contents must be exactly 256 bytes. This is currently implemented only for DOS 3.3 order images.

$padded = AppleII::Disk::pad_block($data, [$pad, [$length]])

Pads $data out to $length bytes with $pad. Returns the padded string; the original is not altered. Dies if $data is longer than $length. The default $pad is " ", and the default $length is 512 bytes.

If $pad is the null string (not undef), just checks to make sure that $data is exactly $length bytes and returns the original string. Dies if $data is not exactly $length bytes.

pad_block is a subroutine, not a method, and is not exported. You probably dont need to call it directly anyway, because the write_XXX methods will call it for you.

Ice Sound Manager was designed to ease the management of sound events, sound themes, and the IceSound server in the IceWM environment under Linux/Unix. It is also intended to be an improvement upon the noble, but primitive icesndcfg.
The main improvements over icesndcfg include a support for sound event "themes", more comprehensive help, easy management and configuration of the IceSound server, a cleaner GUI interface, automatic starting of the IceSound server, and a more conservative approach to disk space usage. In addition, Ice Sound Manager includes a built-in "Setup" program which runs the first time you run Ice Sound Manager.
The application is written in Python (making it more easily ported across various platforms and architectures) and uses GTK through the PyGTK libraries. This application is available in both .tar.bz2, RPM, and static binary (for people without Python/PyGtk).
Please note that the tar.gz file does NOT need to be compiled (this is python, remember). System requirements are as follows: Python 2.2, PyGTK-2 1.9.9/2.0.0, IceWM (or IceWM-Gnome) 1.2.0 or better - with the IceSound Server executable (generally called, icesound or icesound-gnome). IceWM version 1.2.6 or better is highly recommended.
NONE of the following is required: Gnome, Gnome libs, or PyGnome (python-gnome). This application has NOT been tested with earlier versions of Python, IceWM, PyGTK, and IceSound Server. I cant say that it wont work with earlier versions, but I certainly cant say that it will. This application has NO dependencies on Gnome. 8-)
This software is distributed under the GPL license (included in the documentation and source code): Its free and open source for all legal and NON-commerical use, copying, modification, and redistribution, provided all of the authors credits are left in-tact and unmodified. This software is distributed AS-IS, with no warranty whatsoever. Copyright (c) 2002-2004 Erica Andrews (PhrozenSmoke[at]yahoo.com). All rights reserved.
Ice Sound Manager has been designed and tested in the following environment(s): Mandrake 8.1, SuSe 8.1, Kernel 2.4.8 / 2.4.19, Glibc 2.2.4 / 2.2.5, XFree86 4.0.1 - 4.3.0, Python 2.2 - 2.2.1, PyGtk 0.6.9/PyGtk-2 2.0.0, Gtk version 1.2.8-4-1.2.10, Gtk+2 version 2.0.6, IceWM 1.0.9 - 1.2.15, IceWM-Gnome 1.0.9 / 1.2.2, with both icesound and icesound-gnome sound server executables. The test computers (3) were all Pentium 1, ranging in memory from 64MB to 256MB - nothing spectacular. It should run well on very old computers.
Requierments:
- Access to a Bash shell (very important), Python (2.2 or better), PyGtk-2 (1.9.9/2.0.0 or better), and Gtk+ 2.0.6 or better - neither Gnome nor PyGnome is required. (IceWMCP versions 2.5 and earlier require Gtk+1 and PyGtk-1 0.6.9) Repeat: IceWM requires NOTHING gnome-related.
- Also, your version of PyGtk should have the Gdk-Pixbuf modules on your system. Please run ALL IceWMCP programs from a BASH shell: Using other shells such as ksh, pdksh, csh, tcsh, etc. is likely to cause problems. If your IceWMCP programs have trouble launching other applications, it is most likely because you are using something other than a Bash (/bin/bash) shell. Run the programs from Bash...period! If you attempt to run the application and get ANY kind of error that says something like "Import Error", it means YOU do not have all the necessary Python libraries installed or do not have them installed correctly: This is NOT a bug, so do not file a bug report when you dont have the necessary software properly installed. Getting Python and PyGtk and getting them setup right is YOUR business. DO NOT ask for help installing Python, PyGtk, or GdkPixbuf. I recommend you get them from: http://speakeasy.rpmfind.net. If you are using a Python version lower than 2.2 and are too lazy to upgrade, use the "binary" distribution of IceWM Control Panel, or dont bother at all. NOTE: These requirements apply only to the standard pure-python version of IceWM Control Panel. Compiled, binary copies of IceWM Control Panel are stand-alone executables that do NOT require Python or PyGtk.
- Disk space requirements: The standard, pure-Python version of IceWM Control Panel uses approximately 1.75-2.2 MB of disk space - very small! The compiled, binary version of IceWM Control Panel uses about 3.7 MB of disk space. Yes, the binary version is large, so people too lazy or impatient to install Python and PyGtk properly and choose to use the stand-alone binary version will pay with disk space. At last check, the Hardware (or System) plug-in uses about 1.9 MB of disk space (most of it being the hardware ID data file).

All System Info is a system info SuperKaramba theme. Simple english version...
It shows:
- System Info
- CPU usage
- Network Usage
- Memory Load
- HDD usage