Free logical disk software for linux

Logical Desktop is a desktop environment. A "desktop environment" is a program that allows you to do many different things with your computer, but in a consistent way. Desktop environments can be seen as a "dogma" of how things should be done, and how they should look and feel.

Examples of desktop environments are KDE, Gnome, the Windows interface, etc.

In Logical Desktop, like in all desktop environments, you work by composing actions made of one verb and one or more objects (e.g. "Print" is the verb, and the objects are the printer, the files to print, and the program used for printing).

Logical Desktop is how you specify those things: 1) in any order 2) with automatic hiding of the things that dont make sense.

1. In any order: Logical Desktop enables you to specify your action with many possible styles of interaction (file-oriented, task-oriented, program-oriented, device-oriented). Logical Desktop can do that because it treats verbs and objects with complete symmetry and uniformity: you can select both verbs and objects, and in any order.

2. With automatic hiding: Logical Desktop is more intelligent than traditional systems because it hides the unnecessary things while you are composing the action. More precisely, Logical Desktop hides those verbs/files/devices/programs that make no sense with the current selection.
Combining this with the previous point (that you can select anything in any order), we obtain a very powerful mechanism: if you select a verb first, the objects that dont make sense with it are hidden; if you select an object first, the verbs that dont make sense with it are hidden.

LogicParser project is a simple parser for logical expressions.

This small application parses a logical expression and shows his tree representation (in a TreeView), along with its DOT format and PNG graph. It also calculate the result of the proposition based on given values.

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.

check_diskio project is a simple Nagios plugin to monitor disk I/O on Linux systems (2.4 and 2.6 kernels).

Usage:

usage:
-c crit critical
-w warn warning
-d device disk
-r initialize
-v verbose

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.

libogg is the bitstream and framing library for the Ogg project. libogg provides functions which are necessary to codec libraries like libvorbis.

Ogg codecs use octet vectors of raw, compressed data (packets). These compressed packets do not have any high-level structure or boundary information; strung together, they appear to be streams of random bytes with no landmarks.

Raw packets may be used directly by transport mechanisms that provide their own framing and packet-separation mechanisms (such as UDP datagrams).

For stream based storage (such as files) and transport (such as TCP streams or pipes), Vorbis and other future Ogg codecs use the Ogg bitstream format to provide framing/sync, sync recapture after error, landmarks during seeking, and enough information to properly separate data back into packets at the original packet boundaries without relying on decoding to find packet boundaries.

Raw packets are grouped and encoded into contiguous pages of structured bitstream data called logical bitstreams. A logical bitstream consists of pages, in order, belonging to a single codec instance.

Each page is a self contained entity (although it is possible that a packet may be split and encoded across one or more pages); that is, the page decode mechanism is designed to recognize, verify and handle single pages at a time from the overall bitstream.

Multiple logical bitstreams can be combined (with restrictions) into a single physical bitstream. A physical bitstream consists of multiple logical bitstreams multiplexed at the page level and may include a meta-header at the beginning of the multiplexed logical stream that serves as identification magic.

Whole pages are taken in order from multiple logical bitstreams and combined into a single physical stream of pages. The decoder reconstructs the original logical bitstreams from the physical bitstream by taking the pages in order from the physical bitstream and redirecting them into the appropriate logical decoding entity. The simplest physical bitstream is a single, unmultiplexed logical bitstream with no meta-header; this is referred to as a degenerate stream.

Ogg Logical Bitstream Framing discusses the page format of an Ogg bitstream, the packet coding process and logical bitstreams in detail. The remainder of this document specifies requirements for constructing finished, physical Ogg bitstreams.

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.