Free hitachi disk drives software for linux

As the name already suggests, ncdu is an NCurses version of the famous old du unix command.

NCurses Disk Usage provides a fast and easy interface to your harddrive. Where is your disk space going? Why is your home directory that large? ncdu can answer those questions for you in just a matter of seconds!

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.

FDMS-3 Ripper is a Perl program for extracting the tracks from the FDMS-3 filesystem. I recently bought a Fostex FD-8 multitrack hard disk recorder for recording music. It works great, but I was disappointed to discover that, although it uses a standard external SCSI hard disk, there was no way to "rip" the recorded tracks from the hard drive to my PC over the SCSI port. The alternatives were to use the analog-out to re-record each track using my soundcard (resulting in loss of quality and loss of synch between tracks), or buying a $500 ADAT card for my PC.

I decided that I would try to figure out a way to rip the music directly over the SCSI port. The FD-8 uses a proprietary Fostex filesystem, FDMS-3. I decided to hook it up to my PC and probed the drive. I was able to figure out the basic layout of the filesystem pretty quickly. Note: this is designed to hard disks formatted in the FDMS-3 "Mastering" mode, which stores the audio data in uncompressed format.

In order to use the program, you will need to take the hard disk that has the FDMS-3 filesystem on it and hook it up to your PC (mine is a SCSI drive -- dont know if this will work with one of the internal IDE drives you can hook up to the FD-8). Make sure that Linux can see the drive (dont try to mount it, though!). You might want to have a look at SCSI-2.4-HOWTO to get the drive recognized. My external hard disk is located at "/dev/sda", but yours could end up elsewhere.

Next, you need to make sure you have the following on your system: perl, sox and fileutils (for the "dd" utility). Security Warning Unfortunately, this program presents significant security issues, so be careful with it. The script needs to be able to access the hard disk directly, so you can either run it as root (not safe), or change the permissons for the hard disk device (in my case, "/dev/sda"). Run the program with "./fdms3rip /dev/sda" (substituting the actual location of your hard disk).

This will list all of the programs present on the hard disk. Then, run it again with the number of the program you want to fetch off the hard disk: "./fdms3rip /dev/sda 5" to get all of the recorded tracks for program number 5. After waiting a bit, you should now have a bunch of WAV files on your Linux machine. Warning This program will create and erase files with the names "dir" and "header" in the directory it is run from. It would be best to run this program from a clean directory, just to make sure there are no problems.

CDriveBack project is a backup system.
CDriveBacks design goal is to make a backup system so easy to use that the end users with no backup, eighty percent of XP Home users and thirty percent of home XP Professional users, take backups and can easily restore their system.
For example, backing up the C: drive to an area on the C: drive takes two steps:
- Boot the CDriveBack CD, when the first screen shows,
- Hit enter to backup the C: drive.
CDriveBack is:
- A Live CD, one that you can boot, requiring no installs, using,
- Linux 2.6.x, a recent version of the Linux operationg system, to run
- Dialog screens that manage backup files on your drives and
- Use DAR to backup the partition or drive to files, in turn using, when needed,
- Backing up older Windows drives as well as Linux formatted drives is built-in
- NTFS-3G, the NTFS Drive handling package. is used for NTFS drives.
Enhancements:
Bug fixes, all repaired:
- A full restore from a backup area with no differential backup files still asked for diff files with an akward message.
- Documentation dates and releases out of date.
- Startup session screen still referred to the release candidate.
Added:
- An optional "Force" setting for mounting NTFS disks from a Windows that is using chkdsk to always call the partition "dirty"

GliBench is a Gui based benchmarking tool to check your computers CPU and hard disk performance. The software is based on the benchmarks I developed for CliBench Mk III SMP a SMP enabled benchmark program for Win32.
There were several tries to port it to other architectures than Win32, but this was not that easy. So I decided to to a Linux port, based on the GTK toolkit with Gnome support, as Linux runs on almost every hardware around and GTK is quite easy to port to other OSs.
The CPU tests are all ported to ANSI C. They run fully multithreaded using posix threads. You can already use the program for benchmarking your hardware.
Enhancements:
- The application was completely rewritten for GTK+ 2.x and Glib 2.x.
- New stress tests and threaded I/O tests for benchmarking hard drives are available.
- Both console and GUI interfaces are available.

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).

Make CD-ROM Recovery makes a bootable (El Torito) disaster recovery image (CDrec.iso), including backups of the linux system to the same CD-ROM (or CD-RW) if space permits, or to a multi-volume CD-ROM set. Otherwise, the backups can be stored on another local disk, NFS disk or (remote) tape.

After a disaster (disk crash or system intrusion) the system can be booted from the CD-ROM and one can restore the complete system as it was (at the time mkCDrec was run) with the command /etc/recovery/start-restore.sh

Disk cloning (clone-dsk.sh script) allows one to restore a disk to another disk (the destination disk does not have to be of the same size as it calculates the partition layout itself). A thrid script, restore-fs.sh, will restore only one filesystem to a partition of your choice, and the user can choose with which filesystem the partition has to be formatted.

Linux 2.2.x, 2.4.x and 2.6.x kernels are supported, and if size of the kernel is not too big a boot floppy can be made, otherwise a 2.88 Mb boot floppy will be emulated on CD-ROM.

MkCDrec supports ext2 , ext3, minix, xfs , jfs, reiserfs file systems, LVM and software RAID (multiple devices). Each file system is backed up as a compressed tar archive (including the tar log). The compress program used is the users choice (compress, gzip, bzip2, lzop,...)

But there is more: msdos, fat, vfat and ntfs mounted partitions are recognized and are saved as compressed dumps (on CD, tape, etc.)
The user has the possibility to encrypt all backups with openssl if desired (see the Config.sh configuration file for more information).

To restore your system completely just boot from the first CD-ROM made by mkCDrec and type "/etc/recovery/start-restore.sh " to restore everything from CD. Automatic Disaster Recovery and One Button Disaster Recovery are supported by mkCDrec too.
With the clone-dsk.sh script one can restore selective a disk or partitions to another free disk.

mkCDrec supports IDE (inclusive ATA), SCSI disks, hardware RAID based disks (e.g. Compaq SMART2 Disk Array), LVM and software RAID. With an El-Torito CD-ROM you can boot from an IDE or SCSI based CD-ROM drive on IA32/64, powermac and x86_64 GNU/Linux based computer systems only.