Free disk software for linux

Apple Disk Transfer ProDOS (or ADTPro for short) transfers diskettes and logical disk images between Apple ][-era computers and the modern world. If youre familiar with the original ADT, ADTPro extends ADTs reach by working with more logical disk formats, drive types, communications devices, and host operating systems.
Main features:
- Compatibility with any device ProDOS can read
- Compatibility with any Apple ][ (or clone) computer with 64k memory
- Compatibility with many logical disk image formats: .DSK, .PO, .NIB, 2IMG
- Server compatibility with original ADT client program
- Server compatibility with Windows, Mac OSX, Linux, and probably Solaris
- Ability to bootstrap an Apple ][ from bare metal over serial or cassette ports
- Ability to send floppies in "batch" mode without having to name each one
Server
The server program runs on a computer capable of running Java. Depending on how you want to connect to your Apple, you might also need a serial port and cables, an Uthernet card for your apple, or a couple of audio patch cables. The server offers a compact user interface that shows what communications are taking place between the host and the Apple ][.
The servers primary role is to send and receive disk images as requested from the client. But if you have recently acquired an Apple and a disk drive, and you have no software for it - youre in a bit of a tricky situation if you want to move software from the Internet all the way to your shiny new Apple. ADTPros server can help get you get bootstrapped.
Client
The client side runs on the Apple ][. It handles most of the user interaction. When choosing disks/volumes to transfer, anything that ProDOS can see is fair game. Transferring data occurs with a 20k buffer on the Apple, so all transfers are broken up into 20k chunks. A progress indicator shows how far it is into the current chunk, as well as a running count of the total progress.
Enhancements:
- This release has been enhanced with Jean-Marc Boutillon (Deckard)s FASTDSK fast Disk II reading routines.
- This results in a speed boost of 25%-33% for Disk II to host transfers.
- Bootstrapping operations have been reduced, as there is no longer a dependency on ProDOS BASIC.

Watsup is a system and process monitor for CPU, memory, page faults, disk IO, network IO.
Low overhead. GUI controls. Formatted report in window. Sample interval down to 0.1 secs. Choose font size. System resources: CPU (1-4), memory (free/used/cache), page faults (hard/soft), disk IO, network IO. Process resources: same + execution file name.
Main features:
- overhead is about 1/3 as much
- sample interval as low as 0.1 seconds is supported
- overall system and top process resources are shown on one page
- disk I/O, network I/O, and page fault rates can be monitored
- font can be made small (for display in a corner) or large (whole screen)
- the top N processes are displayed with minimal jumping around between samples
- (which makes it easier to watch one or a few processes)
- process ranking is a weighted sum of CPU, hard page faults, and disk I/O

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.

The ISO has multi-language support, and allows you to change the keyboard layout of your shell.

This version has Gpareted included.

Phasi project is another tool for system info written in PHP, with graphical report displaying several devices info, show memory status , SWAP use , and mounted disk partitions.
Main features:
- CPU Info
- Devices info
- Memory Status
- SWAP Status
- Disk partitions

GAG (initials, in spanish, of Graphical Boot Manager) is a Boot Manager program. GAGs loaded when the computer is turned on and allows you to choose the operating system you want to use.
Main features:
- Allows boot of up to 9 different operating systems.
- It can boot operating systems installed in primary and extended partitions on any available hard disk.
- Can be installed from nearly all operating systems.
- GAG doesnt need its own partition. It installs itself in the first track of the hard disk, wich is reserved for these kinds of programs. It can also be instaled on a floppy disk, without using the hard disk.
- It has a timer to boot a default operating system (selectable by the user).
- The configuration menu can be protected with a password.
- The program works in graphic mode (needs a VGA or better graphic card), and has a lot of icons.
- Hides the primary partitions which allows the user to have instaled more than one DOS and/or Windows in the same hard disk.
- Allows a password to be put on each operating system, denying access to non-authorized people.
- Allows the boot manager text to be translated to all languages.
- Can exchange disk drives, allowing to boot from the second, third... hard disk operating systems such as MS-DOS.
- Has the SafeBoot system, that allows to boot your hard disk even if GAG is accidentally overwrited.
- Supports a great variety of keyboards (QWERTY, AZERTY, QWERTZ and DVORAK keyboards).
- Fully support for hard disks up to 4 terabytes (4096 gigabytes).
- Full version and free software (distributed under GPL licence, with source code)
Enhancements:
- 4.8 didnt remember the keyboard type after installing which, in certain situations, prevented you from reconfiguring it from the Setup menu.

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.