Free disks software for linux

disktypes purpose of disktype is to detect the content format of a disk or disk image. It knows about common file systems, partition tables, and boot codes.
The program is written in C and is designed to compile on any modern Unix flavour1. It is self-contained and in general works without special libraries or headers. Some system-dependent features can be used to gather additional information.
As of version 8, disktype knows about the following formats:
File systems:
- FAT12/FAT16/FAT32
- NTFS
- HPFS
- MFS, HFS, HFS Plus
- ISO9660
- UDF
- ext2/ext3
- Minix
- ReiserFS
- Reiser4
- Linux romfs
- Linux cramfs
- Linux squashfs
- UFS (some variations)
- SysV FS (some variations)
- JFS
- XFS
- Amiga FS/FFS
- BeOS BFS
- QNX4 FS
- 3DO CD-ROM FS
- Veritas VxFS
- Xbox DVD file system
Partitioning:
- DOS/PC style
- Apple
- Amiga "Rigid Disk"
- ATARI ST (AHDI3)
- BSD disklabel
- Linux RAID physical disks
- Linux LVM1 physical volumes
- Linux LVM2 physical volumes
- Solaris SPARC disklabel
- Solaris x86 disklabel (vtoc)
Other structures:
- Debian split floppy header
- Linux swap
Disk images:
- Raw CD image (.bin)
- Virtual PC hard disk image
- Apple UDIF disk image (limited)
Boot codes:
- LILO
- GRUB
- SYSLINUX
- ISOLINUX
- Linux kernel
- FreeBSD loader
- Sega Dreamcast (?)
Compression formats:
- gzip
- compress
- bzip2
Archive formats:
- tar
- cpio
- bar
- dump/restore
Enhancements:
- Added file systems: Amiga SFS.
- Added other structures: Linux cloop (detection only), EFI GPT, Windows/MS-DOS boot loader, BeOS boot loader.
- Improved file systems: Amiga FS/FFS, Amiga PFS, Linux squashfs.
- Improved other structures: Amiga "Rigid Disk" partitioning, LILO, ISO9660 El Torito.

wmdiskmon is a dockapp that monitors your disks usage in a portable way, using the POSIX command df -P.

Installation:

1. CONFIGURE THE SOURCES :

$ ./configure [options]

use ./configure --help for more informations on options.

2. COMPILE THE SOURCES :

$ make

3. INSTALL THE PROGRAM :

$ make install-strip

or, if you want a system-wide installation

$ su -c "make install-strip"

Disk Manager project is a simple filesystem configurator that allow you to:
- Automaticly detect new partitions at startup.
- Fully manage configuration of filesystem.
- Enable/disable write support for NTFS (need ntfs-3g installed).

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.

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.

Disc-O-Matic is a GTK+ CD/DVD-ROM archiving tool for mastering and burning multiple discs.

Disc-O-Matic can be used in situations where you have a lot of data that you wish to burn to discs (e.g. keeping an MP3 collection synchronized with a set of CD-RWs).

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,
);