Free sanding discs software for linux

Intellidiscs is a Remake of Tron: Deadly Discs for the classic Intellivision console. Its also one of the few, if not the first, Tron freeware games that has nothing to do with light-cycles.

Basically, you run around in an arena fighting off bad guys with your disc. There are four different varieties of bad guy, and one of them has three different varieties of disc. More difficult enemies appear as your score increases, with the most difficult showing up if you can reach 1,000,000 points.

Bad guys enter through doors on the sides of the arena. You can jam these doors open by either hitting them with your disc, or by running into them. If you jam open doors that are opposite each other, you can run in one side and come out the other. This is very important to your survival.

If you jam enough doors, eventually a recognizer will be dispatched to fix them. If you can hit the recognizer when its eye is open, it will stop fixing the doors and leave the arena. Plus, you get lots of points for this.

You can take three hits before you die, and every hit makes you slower! You will eventually recover from damage, regaining your speed as well. Touching the recognizer kills you instantly, so dont do it.

Default controls are the familiar WASD to move, and the outer keys of numpad (1, 2, 3, 4, 6, 7, 8, 9, non-Mac users turn Num Lock on!) throw your disc in any of eight directions. If you press one of the throw keys while your disc is in flight, it will return to you. Discs are harmless when returning. If you move away from your disc as it is flying back, it will never catch up to you, you must stop and catch it. All of the controls can be changed from the main menu.

Inf sys is a SuperKaramba lm-sensors hddtemp theme.
3 color systems black, white and grey.
It shows:
- System Info
- Memory Load
- Disk Usage
- Fans/Temp

Chango is a system for cacheing MP3 files from multidisc cdrom drives. Since you cant actually mount different discs in the same physical device simultaneously, this software will cache the files you need off to a predetermined cache, so that all of the needed files will be available simultaneously.

This is how to configure it for your system;

Edit the drives.conf file in accordance to how your machine is set up. The included .conf file shows two drives, each holding a max of 4 discs.

/dev/cdrom0:/mnt/cdrom0:4
/dev/cdrom1:/mnt/cdrom1:4

I setup symlinks in /dev from /dev/cdrom0 to /dev/hdc and a second one from /dev/cdrom1 to /dev/hdd. Make sure these are read/execute by the user who will be running the software. I am using a RedHat distro, so all mounted devices will end up in /mnt. so, my /etc/fstab shows the following:

/dev/cdrom0 /mnt/cdrom0 iso9660 noauto,owner,ro 0 0
/dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,ro 0 0

So, by looking at both files, you should see that there is a corrolation between the two.

At this point, you should be able to mount /mnt/cdrom0 as whatever user will be running the script. As well, you should be able to change disks using eject -c 2 /dev/cdrom0 to swap disks.

Run the scandrives.pl script. perl scandrives.pl This will scan the CDs in the drives, and create the database files based on the mp3s. It should show you the directories it is working through as its working. If it notices that the cd is the same as the one it had already scanned, it will skip it. (This is so that if you change just one disc, you can re-run the app, and it will only do the full work on the new or changed discs.)

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.

Solaris::Disk::SVM::Graph is a Perl module for graph your Solaris Volume Manager configurations.

SYNOPSIS

my $graph = Solaris::Disk::SVM::Graph->new(
sourcedir => path/to/dir, # path to SVM config files,
# see Solaris::Disk::SVM for details
fontname => fontname,
fontsize => fontsize,
);

$graph->output(); # output the whole SVM config to svm.png

# output whole configuration
$graph->output(
output => /path/to/image.svg,
# format deduced from file name, if format
# is not present
format => png, # or anything accepted by GraphViz,
# extension will be appended to output filename
);

# output one device
$graph->output( objects => d10 ); # d10 object with sub-devices to d10.png

# output many devices on same graph
$graph->output( objects => [ d10, d11 ] );

# output one device specifying output file name & format
$graph->output(
objects => d10
output => /path/to/image.svg,
format => png,
);

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.

WarLinux is a linux distribution for Wardrivers.

It is available on disk and bootable CD. Its main intended use is for systems administrators that want to audit and evaluate thier wireless network installations.

Should be handy for wardriving also.